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 > <[email protected]> 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. > > Peter > > From: IBM Mainframe Discussion List <[email protected]> On Behalf Of > Joseph Reichman > Sent: Wednesday, September 13, 2023 12:52 PM > To: [email protected] > Subject: Re: Commands from systsin > > > > Let me explain I’m only doing this for testing purposes > > > > I am writing a subsystem so normally the function routines would be in global > > > > But I want to debug the function routine under TEST/TESTAUTH > > > > So the subsystem initialization routine is going to create the SSVT routine > by address > > > > But I need that address to be valid when I later on in the same TSO Session > but under a new invocation of TESTAUTH invoke the function > > Under second invocation of TEST/TESTAUTH > > > > I have this address which I saved wrote down from the first > > And in second invocation before I issue IEFSSREQ I’ll do a AT 1EF37980. ( the > address is just an example ) > > > > Makes sense ? > > > >>> On Sep 13, 2023, at 12:19 PM, Seymour J Metz <[email protected]> wrote: >> >> > >> I advise against it. > >> > >> ________________________________________ > >> From: IBM Mainframe Discussion List <[email protected]> on behalf of >> Joseph Reichman <[email protected]> > >> Sent: Wednesday, September 13, 2023 11:12 AM > >> To: [email protected] > >> Subject: Re: Commands from systsin > >> > >> Seems then the only to do what I want is schedule an IRB with the TCB being >> IKJEFT01 > >> > >> ? > >> > >>> On Sep 13, 2023, at 11:09 AM, Seymour J Metz <[email protected]> wrote: > >>> > >>> The modules are deleted from storage when the command complete, as part of >>> task cleanup. > >>> > >>> ________________________________________ > >>> From: IBM Mainframe Discussion List <[email protected]> on behalf of >>> Joseph Reichman <[email protected]> > >>> Sent: Wednesday, September 13, 2023 10:10 AM > >>> To: [email protected] > >>> Subject: Commands from systsin > >>> > >>> Hi > >>> > >>> I have a number of program that I would like to stay resident in the job >>> pack are of my tso session > >>> > >>> So I run a command from systsin in my tso session that command all it does >>> is loads > >>> A few load modules and wto s the address > >>> Will they remain in core until I log off > >>> > >>> I mean I’m assuming the would run under job step TCB IKJEFT01 > >>> > >>> And therefore stay in the job pack are till I log off > >>> Am I correct ? > > -- > > This message and any attachments are intended only for the use of the > addressee and may contain information that is privileged and confidential. If > the reader of the message is not the intended recipient or an authorized > representative of the intended recipient, you are hereby notified that any > dissemination of this communication is strictly prohibited. If you have > received this communication in error, please notify us immediately by e-mail > and delete the message and any attachments from your system. > > > ---------------------------------------------------------------------- > 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
