I have a number of CSECT in my main module I always do a link eploc= to every CSECT First thing I do at every CSECT is establish An Estae passing parms such CSECT name And retry address I also always use the same base register And have a branch around eyecatcher of CSECT name and date
In my standard recovery which I use for all my code if don’t find a sdwaname I do chain the rb comparing the CSECT name to the CDENAME I do check if it’s a major or minor CDE since in my code it’s typically minor This seems to work when I have gotten abends and by work I mean I have eventually been able to retrieve my registers I also delete the Estae on the way out if the CSECT I didn’t see this method in any IBM books Or share So I am asking Peter yourself if it’s good practice > On Aug 17, 2022, at 10:28 AM, Seymour J Metz <[email protected]> wrote: > > Is "the user's code" only the code that did the ESTAE or also the subroutine > that it called? > > > -- > Shmuel (Seymour J.) Metz > http://mason.gmu.edu/~smetz3 > > ________________________________________ > From: IBM Mainframe Discussion List [[email protected]] on behalf of > Joseph Reichman [[email protected]] > Sent: Wednesday, August 17, 2022 10:08 AM > To: [email protected] > Subject: Re: clarification on SDWAEPA. (was ...SWDAEPA) > > Seymour > > I understand my point being that when sdwaname is not present and sdwarbad is > > The registers at offset X’18’ of the SDWA are not yours > Neither is the abending PSW > > To get as close as possible to the users code to the abend is chaining the rb > from sdwarbad > > A good idea > >> On Aug 17, 2022, at 9:37 AM, Seymour J Metz <[email protected]> wrote: >> >> Are Mr. Ng's excellent SHARE presentations available online? They are, of >> course, not official, but they can be exceedingly helpful. >> >> Are there redbooks on diagnosis? >> >> >> -- >> Shmuel (Seymour J.) Metz >> http://mason.gmu.edu/~smetz3 >> >> ________________________________________ >> From: IBM Mainframe Discussion List [[email protected]] on behalf of >> Peter Relson [[email protected]] >> Sent: Wednesday, August 17, 2022 8:51 AM >> To: [email protected] >> Subject: Re: clarification on SDWAEPA. (was ...SWDAEPA) >> >> <snip> Where can I find a definitive write-up on how ESTAE recovery works >> and how to use it?</snip> >> >> The doc is the doc. Whether it is "definitive" is up to you to decide. >> Since there is no single "right way" to write a recovery routine, whether >> ESTAE-type or FRR, it borders on impossible to provide something definitive >> regarding "how to use it". There are tips, there are considerations, etc. It >> depends on what you want to accomplish. >> >> Aside from the assembler (and authorized assembler) services reference(s) >> for the relevant macros, the guidance is in the authorized assembler >> services guide's "Providing recovery" section. >> >> Perhaps you can share some of what you found difficult to understand (and/or >> what you found missing) so that the information can be improved. >> Maybe you have specific questions that are not addressed. >> >> Peter Relson >> z/OS Core Technology Design >> >> >> ---------------------------------------------------------------------- >> 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 > > ---------------------------------------------------------------------- > 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
