Wingy,

You want the job? I'm TERRIBLE with languages!

Joe B

No just the American slang dialect and of course techno-speak.

joeb

Example of techno speak:

Based on your latest email it looks like we may have some scope creep with PRJ0648. The DB2 instances don't appear to be using the optimizer correctly and are creating fragmental threads that are confusing the scheduler. You may want to create some fake index key logic to fool the optimizer into forcing partial index scans instead of full table scans. You may also want to look at the join logic and see if you can change any of the predicate qualifiers to indexed table joins. Although this is outside the parameters in the design document I don't see how we can not handle the table locks created by this issue any other way except maybe by creating materialized query tables. But that will require almost an entire rewrite plus requests for temporary tablespace. I realize this means a comprehensive modification of the design doc but to assign the needed man hours it must be done this way to allow scheduling and assignment of resources thru TeamTrack.

end techno speak

My day and welcome to it......



joeb