The way I used to do this, way back in the 70s, before I wrote XDC, is I had an associated command string containing a DISPLAY command (I think) whose argument was an address expression that chained up from the PSA, all the way through the current TCB, then through to the second newest RB and to its stored PSW's instruction address.
I believe I used an l as the formatting operand. This mickey mouse was one of the reasons I started writing XDC forty or so years ago. I was appalled by some of the hoops that TSO TEST made me jump through! I said I could do better! And I have. Dave Cole On Tue, Feb 19, 2019, 5:22 PM Joseph Reichman <reichman...@gmail.com wrote: > Hi > > > > I am trying to trace a program flow > > By issuing the following AT statement > > > > AT +0:+100 I would also like to see the corresponding instruction whenever > it hits breakpoint, the sub command L +0:+100 I would list the entire range > of instructions Anyway to list just the instruction it stopped on. > > > > Thanks > > > > > > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
