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.
As long as your code does whatever it needs to do, based on understanding
that retry will or will not happen, it is fine always to tell RTM to
retry.
Peter Relson
z/OS Core Technology Design0
--
For IBM-MAIN subscribe / signof
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 whe
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
