I found the following in the Authorized Service Guide: When the system gives control to the recovery routines defined with the TERM=YES parameter as a result of the above errors [operator cancel, etc.], the system takes the following actions: - Sets the SDWACLUP bit - Gives control to all such routines in LIFO order - Does not enter any ESTAI routine previously suppressed by a return code of 16, or any previously entered recovery routine that requested percolation - Ignores any request for retry.
That implies to me that - Ed is on the right track with the SDWACLUP bit. I suspect it just does not honor my turning it off (as Gregory Shriver notes as I am writing this). - "Gives control to all such routines..." says to me that only TERM=YES routines are eligible in the percolation progression. - I know it didn't work when I pointed at a retry routine with its own ABEND macro. My *impression* was that the retry was honored but the ABEND was ignored, but I must be mistaken. It probably did not retry as operator cancel is not retryable. Am I correct that you apparently can't issue an ABEND macro (effectively) in a recovery routine? That must be well-known or documented? You can't effectively "change" an ABEND from one code to another? Charles ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
