On Sun, 23 Mar 2025 at 11:46, Joseph Reichman < [email protected]> wrote:
> > When one is running inder TEST and you entered TEST > 'MY.USER.LOADLIB(MYPROG)' > > After hitting <enter> you are at location +0 > > Then you do L 21C.? pointing to the current TCB address that TCB is not > the program being debugged TCB that is TEST's TCB correct > Right. In theory TEST could fake this out, as it does for some other things, but it can't hope to catch every TCB pointer. So it shows you what's actually there. > The program being debugged TCB can be seen by doing a LISTTCB without any > parameters > Right. Because the LISTTCB subcommand is defined to do that, i.e. it knows what TCB was running (or will be running) when you issue a GO subcommand, and shows you that info. Same for LISTPSW and perhaps some other subcommands - they won't show you the internal TCB structure of TEST itself. My questions if all these are correct how do you get the program current > TCB talking into consideration the program is running under test > > I looked at tcbback and it was 0's I looked at the next tcb tcbtcb at +74 > and it was 0's > Are you asking how your running program should get its own TCB address? If so, just load the address from 21C as usual. Your program will get its own TCB address - not what you see when you use a TEST subcommand to list that address. Is there any way to get this address from a program when your program is > running under TEST > Or are you looking for a TEST subcommand to give you the address of your program's TCB? I think you already know how to do this with LISTTCB. But maybe I'm not understanding your questions. Tony H. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
