> > I suppose a final job-step to do the DEQ with COND=EVEN would not always do > > the trick. As I recall there are some types of abends that flush the job > > including steps with COND=EVEN, right? > > > > > Very true. My favorite: S40D with a nice message about the initiator being > terminated at end of memory. The S40D, IIRC, was caused by exhausting the > LSQA. So the initiator couldn't do an GETMAINs in order to terminate > properly. The real fun is that RTM did NOT get control and so _all_ the > DSNs which were allocated to the job remained "allocated" (well, ENQUEUEd) > until we IPL'd. Thankfully, that only happened once, about 7 years ago. Of > course, I now know how to do a directed DEQ (not available at the time) to > eliminate an ENQ that I "don't like". <grin/>
In addition its task termination resource manager, which did not execute because of the 40D abnormal memory termination, GRS has a memory termination resource manager which should have executed and released ENQs held by the terminating address space. Jim Mulder z/OS System Test IBM Corp. Poughkeepsie, NY ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
