Miklos Szigetvari <[EMAIL PROTECTED]> wrote on 05/15/2008 01:05:01 PM:
> Rick Fochtman wrote: > > > --------------------<snip>-------------------- > > When an address space terminates normally, RCT simply detaches the > > dump task. The 33E abend is normal and expected. > > > > When you run the application as a batch job, ending the job does not > > terminate the initiator address space. > > --------------------<unsnip>------------------ > > Wouldn't it be easier, and more efficient, to have RCT signal the dump > > task so it could go through normal termination, rather than generating > > an abend and going through all the related processing, including SLIP? > > Maybe it's a dumb question, but it seems to me that a little > > coordination via WAIT/POST could do the trick very nicely. > > > > Considering all the control blocks already related to the address > > space, one more ECB can't be that hard to define. > > I agree with this 100% > > It turned out, the original problem was a HASP310 "TERMINATED AT END > OF MEMORY" condition, and as I seen the X33E traps and the HASP310 > explanation, > I thought the S33E abend is the responsible for "TERMINATED AT END OF > MEMORY". > Currently I have no idea who is responsible for HASP310 HASP310 indicates that the job failed due to abnormal memory termination. This should be preceeded by an IEF402I message. 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: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
