> What's interesting is that the Init & Tuning Reference manual says: > > If started tasks or batch jobs that create non-reusable ASIDs end > enough times, they will exhaust all available ASIDs and an IPL will be > required. When IPLing is not an acceptable option, determine which > programs caused the problems and fix them. For methods that prevent > running out of ASIDs, see z/OS MVS Programming: Extended > Addressability Guide. > > Perhaps IBM DB2 should take this advice.
It has -NOTHING- to do with negligence on the part of DB2 development!!! This is a system integrity issue. There is nothing the DB2 folks could do that would change the outcome. The real issue is that people insist on starting and stopping DB2 (and other XM server) address spaces like they are just any old job. When a cross-memory server address space terminates the address space NUMBER (i.e. the ASID) -MUST- be marked non-reusable until all possible connectors have also terminated. In practice, for such address spaces that means until the next IPL. So stopping DB2 (and similar) product server address spaces is a very bad idea. And frankly, its utterly unnecessary. You can leave them up until hell freezes over. They are designed to support more or less continuous operation. Doing something else simply invites problems. If I go to my Dr and say "When I do this it hurts" he generally says "then don't do that". Sage advice. CC ---------------------------------------------------------------------- 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
