No I didn’t have the module marked reentrent reusable In this instance Robb Scott link to IPCS helped me out
However I have a general request from the group I’m not a software co I only have zdpt I don’t have $10,000 lying around to buy XDC However with the tools at my disposal I get there albeit slower On Mon, Jun 8, 2026 at 5:26 PM Michael Stein <[email protected]> wrote: > On Mon, Jun 08, 2026 at 04:35:02PM -0400, Joseph Reichman wrote: > > I looked at the new second TCB and tcbtbp and rbstab1 was 1E so I think > > this is an svrb and RBOPSW points to CSVRBENQ > > https://www.ibm.com/docs/en/zos/2.2.0?topic=information-rb-mapping > > 10 (A) BITSTRING 1 - RBSTAB1 > > .... 1... RBWAITP INDICATES THAT AN ECB IS POINTING AT THE RB > .... ..1. RBATNXIT THIS IRB IS AN ATTENTION IRB ICB444 > > ATTENTION routine is waiting? > > Why are you trying to test authorized multitask code under TSO test? > > Older message... > > Date: Sun, 7 Dec 2025 07:32:26 -0800 > From: Michael Stein <[email protected]> > To: IBM Mainframe Discussion List <[email protected]> > Subject: Re: Debug tool debugging a estae / recovery routine > > On Wed, Dec 03, 2025 at 08:12:08PM -0500, Joseph Reichman wrote: > > 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 > > I wouldn't trust TSO TEST not to muck up things in testing an ESTAE > and TSO TEST is not the "only solution". > > I'd write some minimal code to do/assist in the testing. Possiblities > include: > . code to dump out areas of storage (just hex or formated?) > . private trace table to track code path (and print/format code) > . possibly using CS to allow for multiple tasks > . record TCB RB cpu tod info? > Keep in mind that these can be reused to help test other things > in the future so the effort isn't just for this case... > > I'd start out crude versions of the above (minimal) but "next time" > I needed them they might get improved etc.. > > There's a lot to be said for just diagnosing some errors with just > SYSUDUMP output avoiding TSO TEST altering things from the point of > failure. Also the system trace table can be useful. > > > ---------------------------------------------------------------------- > 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
