I have EXEC PGM=EQANMDBG,PARM=(pgm,
'TEST(...)/parm')
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
עַם יִשְׂרָאֵל חַי
נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר
________________________________________
From: IBM Mainframe Discussion List <[email protected]> on behalf of
Peter Van Dyke <[email protected]>
Sent: Tuesday, July 8, 2025 2:56 AM
To: [email protected] <[email protected]>
Subject: Re: Driving debugger from IDz
External Message: Use Caution
For non-LE programs you have to execute the z/OS Debugger program EQANMDBG
and specify the name of your non-LE program and a TEST option to invoke the
debugger using the EQANMDBG DD.
Here's example JCL:
//RUNASM EXEC PGM=EQANMDBG,PARM='123,ABC'
//EQANMDBG DD *
ASMPGM,TEST(,EQACMD,,DBMDT%USERID:)
//EQACMD DD *
SET LDD ALL;
LDD ASMPGM;
//EQADEBUG DD DISP=SHR,DSN=MYHLQ.EQALANGX
The data set for the EQADEBUG DD is a PDS/E containing members with
EQALANGX data used by the debugger to debug your assembler programs. These
members are created using the EQALANGX utility to convert SYSADATA for your
assembler programs to EQALANGX data. Here's information on using EQALANGX:
https://www.ibm.com/docs/en/debug-for-zos/17.0.x?topic=program-creating-eqalangx-file-assembler
The LDD (LOADDEBUGDATA) command specified in the EQACMD DD is run when the
debug session starts and it automatically loads the EQALANGX debug
information for the assembler program ASMPGM.
The record specified with the EQANMDBG DD provides the name of the non-LE
assembler program (ASMPGM) followed by an LE TEST runtime option. The DBMDT
sub-option requests to invoke the debug session in an Eclipse client (e.g.
IDz). Following the % character is the ID of the user who has connected
from IDz to z/OS using the remote systems explorer. DBMDT requires the
Debug Manager started task to be running on the z/OS LPAR.
If the Debug Manager STC is not available you could try replacing
'DBMDT%USERID:' with 'TCPIP&123.45.67.89%8001:' where 123.45.67.89 is the
IP address of the workstation running the IDz client and 8001 is the
(default) port the debugger in IDz is using to listen for connections. Be
aware that firewalls might stop the connection between z/OS and the
workstation.
I hope that helps.
Peter Van Dyke
On Tue, 8 Jul 2025 at 09:43, Seymour J Metz <[email protected]> wrote:
> I don't get a prompt, just what looks like a stack trace. This is for an
> HLASM program that is not LE enabled, so TEST(foo) is in the PARM.
>
> Due to e-mail security I can't send the actual JCL or screenshots beyond
> the IRS network.
>
> --
> Shmuel (Seymour J.) Metz
> http://mason.gmu.edu/~smetz3
> עַם יִשְׂרָאֵל חַי
> נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר
>
>
>
>
> ________________________________________
> From: IBM Mainframe Discussion List <[email protected]> on behalf
> of Peter Van Dyke <[email protected]>
> Sent: Monday, July 7, 2025 8:45 PM
> To: [email protected] <[email protected]>
> Subject: Re: Driving debugger from IDz
>
>
> External Message: Use Caution
>
>
> Hi,
>
> The following training module on debugging COBOL in IDz made by Jonathan
> Sayles might help. It is part of a training course on using IDz:
>
> https://community.ibm.com/community/user/viewdocument/idzadfz-and-zod-debugger?CommunityKey=d9405c44-16cb-4b11-99b6-49d9225fc7c6&tab=librarydocuments
>
>
> Peter Van Dyke
>
>
> On Tue, 8 Jul 2025 at 00:01, Seymour J Metz <[email protected]> wrote:
>
> > I've been able to connect to IDz from the debugger, but I haven't been
> > able to enter any debug commands. I've tried the Debug and Debug Console
> > perspectives. Do I need initial command in my debug job? Does the term
> > "full screen" include IDz, or only 3270? Is there a presentation on
> driving
> > the debugger from IDz after the connection?
> >
> > Thanks.
> >
> > --
> > Shmuel (Seymour J.) Metz
> > http://mason.gmu.edu/~smetz3
> > עַם יִשְׂרָאֵל חַי
> > נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר
> >
> >
> >
> > ----------------------------------------------------------------------
> > 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
