On 9 December 2013 20:40, Micheal Butz <[email protected]> wrote:
> TEST "MYLOADLIB(MYPROG)" > What TCB is associated with MYPROG Its own. > Or since this running under TSO > II is not the same as batch where exec pgm=MYPROG is the job step TCB That is also true without TEST in the picture. > Maybe there is only a RB for MYPROG I'm sure TEST ATTACHes your program. But really, why do you care about this? If you want to see what your program's TCB looked like when it last ran, use TEST's LISTTCB command, as someone else already suggested. The same goes for LISTPSW. You can list data in storage with LIST, and I believe the only time that won't match reality is if you list an instruction that has a breakpoint on it. If you have multiple TCBs under TEST, you may run into some trouble. There are circumstance where a TCB can be dispatched without TEST's awareness (perhaps if an IRB is involved - I don't remember how I have provoked this in the past). Then you may get the strange TEST message "TCB IS ACTIVE", and usually your debugging session will go downhill from there. Tony H.
