step by step trace 4 ISPF dialog called assembler program

Lynne · New User Joined: 15 Jan 2015 Posts: 98 Location: USA

Is there any way to use step by step trace (IBM debugging tool) for assembler program called by a rexx exec in an ISPF dialog?

I use this all the time to debug assembler programs executed in JCL, but.. has anyone done this to debug an assembler program called in an ISPF dialog?

if not, is the only way to debug an assembler program called in a dialog is by looking at dumps when it bombs?

Pedro · Posted: Wed Dec 14, 2022 1:34 am

Several years ago, I used Rational Developer for Z to debug, but if I recall correctly, they are somewhat similar to Debug Tool.

But there are a couple of methods... I provided the TCPIP address of the debugger when I compiled the program. And then the program 'phoned home' when it was executed. The program does not know that it executes in TSO vs. batch... it still executes the same.

Can you describe how your batch debug is setup?

Lynne · New User Joined: 15 Jan 2015 Posts: 98 Location: USA

here is the code I use for batch debug

don.leahy · Posted: Wed Dec 14, 2022 7:24 am

You have to add the debug datasets to the ISPF procedure (REXX or CLIST). If unfamiliar with this, read up on the TSO command ALLOC.

Or you can allocate them separately to your TSO session before starting up the ISPF function that runs your program.

Lynne · New User Joined: 15 Jan 2015 Posts: 98 Location: USA

then SELECT EQANMDBG instead of your normal program, right?

ok. I saw something like that described in the debug manual, for programs like cobol, pl1 - but very little about assem.

the ISPF SELECT of a program has a PARM parameter, but I'm using it to pass a DSN Name already. so.. better to allocate all this first.

Lynne · New User Joined: 15 Jan 2015 Posts: 98 Location: USA

I coded something up, but probably missed something. but, as I'm starting the Christmas holidays, I will pick this back up in 2023. and post when I get it working.

Thanks for your help.

Lynne · New User Joined: 15 Jan 2015 Posts: 98 Location: USA

I finally got back to this. I set up the debug allocations like I do in JCL (with DDs) - and I trace the rexx exec and see all the allocations are done - no errors, but when it gets to debug - it keeps telling me it can't find the program.

I've checked the name , the loadlib - everything is there. When I run the exec without the debug setup, it has no problem finding my program bcz it abends a ways in the program, so it is executing some instructions in my asm program.

Why can't Debug find YBALRD3 when Rexx without debug can?

so, here is my linkdeck:

Pedro · Posted: Wed Jan 11, 2023 12:32 pm

In your first example, you do not have LIBDEF ISPLLIB... please explain where your loadlib data set is allocated.

In the second example, you do have LIBDEF ISPLLIB, but that is used only for ISPF initiated calls. PGM(EQANMDBG) will not call your program through ISPF.

I think what you need is to use the TSOLIB command prior to starting ISPF to add your loadlib to the MVS search order. Another alternative is to concatenate your loadlib to the ISPLLIB allocation prior to starting ISPF.

Lynne · New User Joined: 15 Jan 2015 Posts: 98 Location: USA

This function is part of an ISPF application XXXX that I wrote - which does several functions for a group of application programmers working on a specific project.

in the first example, the one that works, the exec that brings up the application XXXX has this to assign my loadlib to ISPLLIB:

Lynne · New User Joined: 15 Jan 2015 Posts: 98 Location: USA

Pedro · Posted: Thu Jan 12, 2023 1:57 am

re: "or adding it to my logon proc before I got to ISPF"

Most users do not have authority to update the logon proc. My suggestion was to append your private data set to whatever is already there. *

Do something like this before starting ISPF:

Lynne · New User Joined: 15 Jan 2015 Posts: 98 Location: USA

Thank you. I always learn something new from you. I knew what you meant - I know systems does not want you messing around with logon procs they set up for everyone else. and with good reason. I'm fine with that.

but I have a rexx exec that I execute after I log into tso and before I call ISPF. That's what I meant by "my logon proc".

I spent today going thru what I did with a fine tooth comb, and found a bug in a new procedure I was using. I ended up creating my own libraries for everything, making sure what I thought I was creating was there. And ended up cleaning up a rexx exec I call right after logging in to TSO in addition to adding my loadlib to ISPLLIB at logon time.

and, I actually got to STEP by STEP trace from the REXX Exec. .after I added the loadlib to my logon rexx and I fixed the other 2 problems I found with another group's procedures.

but now it is telling me that the DEBUG has no LANGX code - even though I set up my own assembler jcl to created ADATA and run the debug program to create the LANGX that debugger uses. I decided to call it a day.

I will go thru the debug manual and figure out what I set up wrong. but.. I was just glad to finally get step by step trace up from REXX.

So, thanks for your help. When I get everything working, I will post it, as I could not find much on setting this up in rexx.

thanks again.

Lynne · New User Joined: 15 Jan 2015 Posts: 98 Location: USA

Pedro, if you look at the linkdeck for YBALRD3, you will see an INCLUDE for a system load module libary - which includes ISPLINK and ISPEXEC. in this ASM program, instead of dynamically calling ISPLINK and ISPEXEC, it does a call to these programs -like this:

IBM man desc

which is why I had to do the extra include when assembling these programs.

I don't know why the original programmers did it this way, (instead of using LINK EP=) but.. it is that way throughout this package. So that's why i just created the linkdeck like they did for the original package.

but I think this one include is why I can't go any further with DEBUG. it keeps saying it can't display the instructions because the compile for debug is wrong.

When I looked in the debug manuals for some instruction on how to do this, they talk about LLA and using EQALOAD to allocate this library (but no examples or syntax that I could find).

so I added allocating the System Load Library PDS with a TSO allocate statement. brought up debug.. but same problem.

I keep getting this:

Pedro · Posted: Fri Jan 13, 2023 7:29 am

I have never used Debugtool, but I took a peek at the manuals.

Please try this in your DBGIN2 file.

Lynne · New User Joined: 15 Jan 2015 Posts: 98 Location: USA

I will try that, but I think that is the default. The top command is usually the default.

Lynne · New User Joined: 15 Jan 2015 Posts: 98 Location: USA

found my stupid error. after doing some more reading, I realized I could read the LOG in debug, and did that (zoomlog). and it told me 2 LDD statements were wrong. so, I looked and looked, and realized I hadn't put the ending ';' on each LDD statment. What confused me what the error message saying that the compile options were wrong.. so, I kept looking there.

fixed that and tried again. I then got errors saying that it couldn't find my programs on my userid.EQALANGX pds. so, it must be defaulting that somewhere - bcz I did specifify where the language files should go. Will find out about that later. Might look up a lot of debug info later. a LOT of options in Debug.

but.. it did start stepping thru my program. so.. that is great, because i can finally figure out the problem in this program.

So, thanks again, Pedro for helping me.

Pedro · Posted: Sat Jan 14, 2023 3:52 am

You are welcome!

Lynne · New User Joined: 15 Jan 2015 Posts: 98 Location: USA

Solution: What worked for me that enabled me to use IBM Step by Step Trace to trace an Assembler program called by an ISPF dialog application REXX exec:

The original call to the assembler program is this instruction:
"SELECT PGM(YBALRD3) PARM("t$clog")"

I comment that out in the following code and add these statements which will call IBM Debug (EQANMDBG), and tell it to execute my program in step by step mode: