>only TESTAUTH let’s you debug code with PSW bit 15 being 0 Obviously you haven't tried z/XDC.
>All I want is to debug a program that was preloaded under a different TCB Have you considered using CSVDYLPA to load in into dynamic LPA? Probably overkill for your purposes, but you can do it so that it will stay after task termination. -- Tom Marchant On Wed, 13 Sep 2023 15:10:19 -0400, Joseph Reichman <reichman...@gmail.com> wrote: >First off tried it only TESTAUTH let’s you debug code with PSW bit 15 being 0 > >Not really sure what not being a good idea that is usually reserved for moving >using non standard code into production as other problems will pop up > >All I want is to debug a program that was preloaded under a different TCB >after I get the kinks out I’ll have LOADTOGLOBAL=YES > >> On Sep 13, 2023, at 3:04 PM, Farley, Peter >> <0000031df298a9da-dmarc-requ...@listserv.ua.edu> wrote: >> >> I agree with other posters that your suggested solution is not a good idea. >> >> If you have the HLASM Toolkit product licensed on your system you can use >> the ASMIDF debugger to remotely debug batch jobs from a VTAM session, but >> using ASMIDF requires that pre-established VTAM APPL’s and LU’s are defined >> by your VTAM/network team. >> >> I have used it to debug assembler code and it is a pretty reasonable >> debugging tool (not as good as z/XDC, but reasonable nonetheless, and IMHO >> better than TSO TEST) IFF you can get your network team to set up the VTAM >> APPL’s and LU’s for you. It’s all documented in the install/reference >> manual for the HLASM Toolkit. >> >> IIRC, ASMIDF even has the ability to debug authorized code, but check the >> manual to be sure. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
