Chris, "Carbon-based recovery analysis routine"
And "..that offer a point and shoot shortcut to your next unplanned IPL" Two good chortles in two days ! -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Craddock, Chris Sent: 19 July 2005 11:53 To: IBM-MAIN@BAMA.UA.EDU Subject: Re: STAE/ESTAE > The purpose of a recovery routine is to recover from a > situations that you have otherwise not programmatically not catered to. That's only one of the things a recovery routine is for. The primary purpose is to collect diagnostic information so that a carbon-based recovery analysis routine can figure out what went wrong and fix the application so it won't happen again. If its possible to safely retry to somewhere (without step 1 above) then that's a bonus. > If no such recovery is possible, i.e. a request cannot be retried, > you cannot figure out what is going on in the first place or manual > intervention is required, you abend. In essence if you cannot recover > or plain ignore what happened, you abend. NO! You collect diagnostic information and then you percolate control back to RTM with RC=0 which means "I give up". There is no point in abending in a recovery routine. You're already under the control of RTM's tender mercies. That said, there's no great harm in it either. RTM is quite prepared to deal with recovery routines that abend. That happens all the time and often enough without the recovery routine even issuing SVC D :o) CC ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
