On Sat, 15 Apr 2017 22:06:39 GMT "[email protected]" <[email protected]> wrote:
:>I'm looking for a good example Of an Associated Recovery Routine to :>be used as with a PC Stacking Routine. . :>I have read some Share Presentations and of course the standard IBM :>Publications, but have not been able to locate a good sample :>Associated Recovery Routine for PC Stacking Routine. :>I understand an AAR is like an ESTAE. :>I also understand that the AAR is specified on the ETDEF or SETDEF macro :>for the respective PC Service Routine. . :>Usually When an ESTAE is created a Retry Routine can be specified :>in the ESTAE Recovery Routine. :>When It comes to a PC Stacking Routine, what exactly and I retrying ? The recovery routine address is specified by the ETDEF as you specify above. The retry routine would be specified, as with ESTAEX, via SETRP. . :>Once the program has abended, I basically want to take a DUMP, free up :>resources and return to the issuer of the PC Routine with some indication :>the transaction failed. Just as you would in an ESTAE. Just that the SDWAPARM comes from the stack entry. If you need a parm, you must use MSTA to specify the data. : :>If the PC routine incurs, 0C1 or 0C7, re-executing the same instructions :>would not correct the issue. Makes sense. :>In some examples of an ESTAE that I have seen, the Retry Routine :>Cancels the Out-Standing ESTAE. Should that be done for a an ARR with PC Service Routine ? I do not believe that it is possible to cancel the ARR from within the recovery/retry routine, or in the PC routine in general. Your retry routine can set footprint information in the MSTA area to indicate to not recurse. . :>So what Exactly should a Retry Routine try to accomplish in an Associated :>Recovery Routine (ARR) ? As an ESTAE. -- 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
