On Thu, 2006-03-23 at 12:04 -0600, Terry Linsley wrote: > Is there a straight forward method of determining if an enclave is > dependant? Would an example of one be when a DB2 utility spawns multiple > threads to build an index during a table load or recovery?
RMFIII has an indicator - I think that's what twigged me to go find out what the hell a dependent enclave was. PP isn't any help. I'd be *REAL* surprised if any have surfaced in your environment unless it was the home-grown stuff - ours was, although not Java. We had a small local batch job that did some DB2 log analysis - this is where the dep enclave came from. Ops noticed it (apparently) wasn't doing anything, and reset the job. Still wasn't doing anything, but the shop stopped - no prod batch was going anywhere. Eventually I got a call. The dependant enclave came along for the ride, and was consuming a full engine - out of 3. At 2.10, this was *very* hard to track down. Ops got kicked (again) for using reset. Even these episodes aren't enough to cause a change of mind about mandatory logon on the consoles. Shane ... ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
