To Rob Scott's (as usual) wise response, I will add this: Is your ESTAE(X) routine even getting control? Put a WTO at the very beginning of your recovery routine to tell you that your routine got control. And beware that WTO may alter some registers that your recovery routine may need, such as R0, R1, R14, and R15.
Bill Fairchild ----- Original Message ----- From: "Micheal Butz" <[email protected]> To: [email protected] Sent: Wednesday, August 27, 2014 4:47:13 AM Subject: Re: Recovery routines It is declared as authorized in IKJTSOxx what is the significance of that I'll research it thanks Sent from my iPhone > On Aug 27, 2014, at 5:25 AM, Rob Scott <[email protected]> wrote: > > This is where you need to do some elimination of certain factors : > > (1) Does your ESTAE actually work? > Test it by doing a link to a dummy program and forcing that dummy program to > abend > > (2) Is it related to the TSO command environment? > Test this by using "TSO dummy" and re-test using the dummy program from (1) > > (3) Is there something special about the TSO command processor? > For example, is it declared in AUTHxxx in IKJTSOxx ? (If so - this explains > your problem) > > (4) Is it related to ISPF services > Add some ISPF services to your dummy program and re-test > > > > Rob Scott > Lead Developer > Rocket Software > 77 Fourth Avenue . Suite 100 . Waltham . MA 02451-1468 . USA > Tel: +1.781.684.2305 > Email: [email protected] > Web: www.rocketsoftware.com > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Micheal Butz > Sent: 27 August 2014 00:54 > To: [email protected] > Subject: Re: Recovery routines > > It was a TSO command processor > Which I execute from within > ISPF With following syntax > TSO CMDPGM > > > > Sent from my iPhone > >>> On Aug 26, 2014, at 7:39 PM, Walt Farrell <[email protected]> wrote: >>> >>> On Tue, 26 Aug 2014 18:02:01 -0400, Micheal Butz <[email protected]> >>> wrote: >>> >>> It hasn't retried >>> >>> I establish an estaex in the begining >>> Of My program then load another program >>> The second program gets a S0C4 >>> I get an ISP message re a S0C4 and the program ends my routine >>> Never has a chance to examine >>> It point is if everything is still under the same TCB/RB I should get >>> control >> >> What did your program invoke? What makes you think it's under the same >> TCB/RB? If the program you invoked abended, and did not retry, and your >> ESTAEX routine did not get control, that should indicate either that you did >> not set it up properly, or that the routine you invoked was not, in fact, >> under your TCB/RB. >> >> So what was the routine? If it's something ISPF-based, as seems likely from >> "I get an ISP message" you need to be aware that many ISPF services run >> under the ISPF main task, not under one of the ISPF subtasks, where your >> program is likely to be running. >> >> If you tell us exactly what you did that failed, we may be able to tell you >> the proper recovery (if any). >> >> -- >> Walt >> >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to [email protected] with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ================================ > Rocket Software, Inc. and subsidiaries ■ 77 Fourth Avenue, Waltham MA 02451 ■ > +1 800.966.3270 ■ +1 781.577.4321 > Unsubscribe From Commercial Email – [email protected] > Manage Your Subscription Preferences - > http://info.rocketsoftware.com/GlobalSubscriptionManagementEmailFooter_SubscriptionCenter.html > > Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy > ================================ > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
