In application code - probably no problem as whatever resources used will be tracked by the system and freed.
In system code mucho problems possible, since one would not free resources if one expects to retry - and these resources may not be associated by the system with the failed unit of work. On Fri, 30 Nov 2018 10:47:00 -0600 Paul Schuster <[email protected]> wrote: :>Hello: :> :>The manual MVS Programming: Assembler Services :>Guide Chapter 8. Providing recovery explains that an ESTAE that is called with the SDWACLUP bit on can only percolate (SETRP RC=0). It further explains that if you do attempt a retry (SETRP RC=4) , the retry will be ignored. :> :>I was testing with an ESTAE that gets control with the SDWACLUP bit on, and the routine does attempt a retry (SETRP RC=4) but it indeed was ignored, with no other apparent adverse impact. :> :>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. :> :>I did change my specific ESTAE to exit SETRP RC=0 when the SDWACLUP bit is on. :> :>Thank you for any insight you can provide. :> :>Paul :> :>---------------------------------------------------------------------- :>For IBM-MAIN subscribe / signoff / archive access instructions, :>send email to [email protected] with the message: INFO IBM-MAIN -- Binyamin Dissen <[email protected]> http://www.dissensoftware.com Director, Dissen Software, Bar & Grill - Israel Should you use the mailblocks package and expect a response from me, you should preauthorize the dissensoftware.com domain. I very rarely bother responding to challenge/response systems, especially those from irresponsible companies. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
