I would think I would have to allocate the ISPF panel library and other ISPF libraries as well Thanks
> On Feb 12, 2025, at 7:04 PM, Peter Van Dyke > <[email protected]> wrote: > > z/OS Debugger does support debugging of non-LE programs, including > Assembler. You will need to change the CLIST to CALL the program > EQANMDBG and allocate a data set to the EQANMDBG DD which contains data > such as the name of the program to be debugged and options for the > debugger. For more information see: > https://www.ibm.com/docs/en/debug-for-zos/17.0?topic=environment-passing-parameters-eqanmdbg > > > I hope that helps. > > Peter Van Dyke > >> On Thu, 13 Feb 2025 at 01:41, Joseph Reichman < >> [email protected]> wrote: >> >> I think I need to include all that LE stuff ( don’t think there is another >> way ) >> >> That’s makes everything really messy >> >> Thanks >> >> Get Outlook for iOS<https://aka.ms/o0ukef> >> ________________________________ >> From: IBM Mainframe Discussion List <[email protected]> on behalf >> of Seymour J Metz <[email protected]> >> Sent: Wednesday, February 12, 2025 11:51:26 AM >> To: [email protected] <[email protected]> >> Subject: Re: Using debug tool to debug program called in a clist >> >> I would naively expect CEExxxxx to be part of or require LE. >> >> You can invoke the debug tool in several different ways, including IDz, >> but I'm not sure how to target a program called from within a clist. Have >> you considered calling the debug tool from the clist? >> >> -- >> Shmuel (Seymour J.) Metz >> http://mason.gmu.edu/~smetz3 >> עַם יִשְׂרָאֵל חַי >> נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר >> >> >> >> ________________________________________ >> From: IBM Mainframe Discussion List <[email protected]> on behalf >> of Joseph Reichman <[email protected]> >> Sent: Wednesday, February 12, 2025 11:30 AM >> To: [email protected] >> Subject: Using debug tool to debug program called in a clist >> >> External Message: Use Caution >> >> >> Hi >> >> I have a program called in a clist using the TSO call command >> >> Sometime after the initialization of my program >> >> I try to link or basr to ceetest >> >> I allocate the files that I need SEQAMOD the debug tool load library >> >> Debug tool user source file >> >> It keeps on abending at offset +4 >> >> Frustrated I put the program under tso test >> >> I made a breakpoint at the BASR to CEETEST >> >> Looking at the first instruction of CEETEST >> >> I loads into register 15 from some offset off of register 12 >> >> This seems like LE >> >> Do I need CEENTRY and dsa regs and all that set up to use CEETEST >> >> Wondering if there is another way to debug this under debug tool >> >> Thanks >> >> ---------------------------------------------------------------------- >> 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 >> >> ---------------------------------------------------------------------- >> 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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
