Re: Newbie: debug a program running in batch

"WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx> wrote on 11/03/2016 03:14:11 PM:

----- Message from Buck Calabro <kc2hiz@xxxxxxxxx> on Thu, 3 Nov
2016 15:12:51 -0400 -----

To:

wdsci-l@xxxxxxxxxxxx

Subject:

Re: [WDSCI-L] Newbie: debug a program running in batch

On 11/3/2016 1:53 PM, Dan wrote:

I wonder how much of the issue can be attributed to Eclipse vs. IBM.

So, I guess my cheat sheet for debugging in RDi is:
1) Exit RDi
2) Delete workspace
3) Start RDi
4) Set the SEP(s), ensuring correct object library and user ID
5) On the i, start a brand new job, ensuring correct library list (or
qualify your program call)

I don't do anything like that, and never did.

I don't have this problem either. I use a workflow not exactly the same,
but similar to Buck's.

. . .
. . .
. . .

Even with all that, I find I'm still having problems. It appears that

the

first call to PGMA is "caught" by the debugger (I have a breakpoint

set at

the first executable statement), but subsequent calls to PGMA in the

same

CL program stream are not. I just now confirmed this by debugging in

the

green screen, which works properly. I've wasted most of my day

getting to

this point. Not happy.

Preferences > Run/Debug > IBM i Debug

Select the option to 'Terminate debug session on program completion' and
RDi will click that red button for you when the first CALL ends (and
every one after as well).

Are sure that that's not backwards Buck?

I find that checking it terminates the debug when the program is complete
(and I believe you are then presented with the dialog telling you the
program terminated as someone else previously stated--I don't recall for
certain). Then there usually isn't sufficient time to reset everything and
have the SEP fire on the next call.

Unchecking it leaves the debugger active and will let you step into the CL
which called the program with the SEP set. The caveat is that it won't
stop the program when it enters it the next time because your debug
session is active. Although, you can set a breakpoint and it will stop at
it on the next call to the program.

The other option is to debug the CL which calls the RPG/COBOL/etc. Then
step into the program you really want to debug. Have a breakpoint set at
an appropriate place and execution will stop so you can do what you want
to.

About the only 'change' I had to make to my workflow to accommodate the
SEP debugger was to click the 'Refresh' after a compile. That's it. I
haven't used green screen debug in maybe 10 years and literally the only
code I work on is green screen RPG.

+1 I don't know if I would remember how to debug with the green screen.

Michael Quigley
Computer Services
The Way International
www.TheWay.org