They dropped it before I came on board, so he's stuck with the less capable debuggers.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 עַם יִשְׂרָאֵל חַי נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר ________________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Steve Thompson <[email protected]> Sent: Thursday, December 4, 2025 10:09 AM To: [email protected] <[email protected]> Subject: Re: Debug tool debugging a estae / recovery routine External Message: Use Caution Probably not what you want to hear, but z/XDC really handles tracing and break points much better than IBM's Debugger, TSO TEST, TEST AUTH, etc. Steve Thompson On 12/3/2025 8:12 PM, Joseph Reichman wrote: > I did a lot of research and there is maybe one or two lines on estate in > debug tool user and reference manual > > I was hoping some one would see this and say they have used debug tool to > debug an Estae recovery but at this point TSO TEST seems to be the only > solution > >> On Dec 3, 2025, at 6:50 PM, Jon Perryman <[email protected]> wrote: >> >> On Wed, 3 Dec 2025 10:52:47 +0200, Binyamin Dissen >> <[email protected]> wrote: >> >>> :>When I did a submit with this string get a >>> :>s0c4 before anything is displayed at the screen the reason code 11 >>> >>> (E)SPIE gets control first. >>> TRAP(OFF,NOSPIE) >> Mentioning ESPIE will only confuse things. While I know nothing about IBM >> debugger, Joseph told us that his ESTAE displays the S0C4 before IBM Debug >> gets control when using TRAP(OFF). Either SPIE called his ESTAE or SPIE >> percolated the S0C4. We don't know what the debugger displayed once it got >> control so it may have given a clue. >> >>> :>it is by my setrp rc=0 in my recovery routine >> SETRP RC=0 does nothing more than set the return code in the recovery >> routine and continues with the next instruction in ESTAE. Joseph can debug >> this once he has the debugger working with his ESTAE. >> >> ---------------------------------------------------------------------- >> 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
