On 11/30/2018 8:47 AM, Paul Schuster wrote:
So my question is this: aside from ‘completeness/code purity’, is there anything to worry about if an ESTAE attempts a ‘retry’ even though the ‘SDWACLUP’ bit is on? I can envision that the recovery routine itself may have different logic based on whether the ‘SDWACLUP’ bit is on or off.
In general, no harm comes from doing RC=4 when SDWACLUP is on. Very simple code might do it every time.
More complex -- particularly authorized -- code might need to know the difference. For example, you might have a resource that *must* be cleaned up before your address space goes down. In the SDWACLUP OFF case, you would not clean up that resource prior to SETRP RC=4. (You would clean it up at shutdown time -- perhaps hours later.) However, in the SDWACLUP ON case (e.g., you have been canceled or forced), you would clean up that important resource before issuing SDUMP and percolating with SETRP RC=0 (or 4).
Of course, you can also use RESMGR to ensure important resources get cleaned up.
-- Phoenix Software International Edward E. Jaffe 831 Parkview Drive North El Segundo, CA 90245 https://www.phoenixsoftware.com/ -------------------------------------------------------------------------------- This e-mail message, including any attachments, appended messages and the information contained therein, is for the sole use of the intended recipient(s). If you are not an intended recipient or have otherwise received this email message in error, any use, dissemination, distribution, review, storage or copying of this e-mail message and the information contained therein is strictly prohibited. If you are not an intended recipient, please contact the sender by reply e-mail and destroy all copies of this email message and do not otherwise utilize or retain this email message or any or all of the information contained therein. Although this email message and any attachments or appended messages are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by the sender for any loss or damage arising in any way from its opening or use. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
