Re: Newbie: debug a program running in batch

"WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx> wrote on 11/04/2016 01:00:02 PM:

----- Message from Dan <dan27649@xxxxxxxxx> on Thu, 3 Nov 2016 17:
04:41 -0400 -----

To:

"Rational Developer for IBM i / Websphere Development Studio Client
for System i & iSeries" <wdsci-l@xxxxxxxxxxxx>

Subject:

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

...
Get the dialogue box telling me the program terminated - I ignored
it. The batch job kept running and SEP stopped at the first
statement of the program.

F8 to resume/run.
Breaks on my condition.
F8 to resume to the end.

The batch job keeps running, and I don't get any further SEP breaks.

Buck, I'm not entirely sure, but did you just replicate the problem I

was

having?

- Dan

Buck/Dan,

It all depends on timing. When the program completes and you've check the
RDi preference 'Terminate the debug session on program completion', RDi
(and the IBM i) break down the connection and reset things. If--make that
***IF*** there's enough time before the job calls the program with the SEP
set again, the SEP will trigger and you'll get to debug the call in RDi.
But if there isn't time, you're SOL (sorely outta luck--got to keep the
list clean). In Buck's scenario, there was enough time between the first
call and second call, but after that everything was already in main
storage and the job called the program too quickly to trigger the SEP
again.

This is why I uncheck 'Terminate debug session on program completion' and
set a break point in the program. Then the job being serviced, continues
in debug mode. When the breakpoint (which you've set) is hit, program
execution will stop (i.e., wait for the debugger) and you'll get to do
whatever debugging is needed.

If you leave 'Terminate debug session.....' checked, it's a roll of the
dice whether the job will reenter debug mode.

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