Or you could force a normal ABEND of some kind and address stop with a tracing/debugging system, such as XDC, on the first instruction in your ESTAE routine. Then alter the contents of R0 so that your test for no SDWA will be successful and see if your code to handle that condition (immediately percolate is a very good idea of what your code should do) works correctly.
Bill Fairchild -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Chris Craddock Sent: Wednesday, July 20, 2011 9:24 AM To: IBM-MAIN@bama.ua.edu Subject: Re: ESTAE testing question On Wed, Jul 20, 2011 at 10:18 AM, Paul Schuster <pgs4ibmm...@pacbell.net>wrote: > Hello: > > The manual 'z/OS V1R12.0 MVS Assembler Services Guide' has this statement: > "The case where an SDWA is not provided is rare." > > Is there a way to force this kind of condition in order to actually > test an ESTAE that is tripped with this condition? > That's not a good plan. The only time you won't get an SDWA is in cases of storage exhaustion and a likely cause of that is error recursion due to "creative" recovery efforts. The safest thing to do in that case is to immediately percolate. -- This email might be from the artist formerly known as CC (or not) You be the judge. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
