Rick Fochtman wrote:
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.
I doubt it would be easier or more efficient. And, in the midst of an abnormal termination scenario, it might not even work!
Why is anyone suddenly concerned about this decades-old, benign behavior of displaying X33E when an address space terminates? Personally, I *like* to see the X33E SLIP message. It tells me something *extremely* useful -- namely the ASID of the address space that just terminated! Clearly, one man's information is another man's clutter...
There are at least a dozen expected abend conditions with SLIP A=NODUMP defined in IEASLP00. If you're not happy with those settings, you can delete them or redefine them to specify different actions. Specifically, for the case being described in this thread, the following commands will suppress the IEA989I message for any S33E abend s going forward:
SLIP DEL,ID=X33E SLIP SET,C=33E,ID=X33E,A=IGNORE,END -- Edward E Jaffe Phoenix Software International, Inc 5200 W Century Blvd, Suite 800 Los Angeles, CA 90045 310-338-0400 x318 [EMAIL PROTECTED] http://www.phoenixsoftware.com/ ---------------------------------------------------------------------- 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
