Re: Newbie: debug a program running in batch

On 11/3/2016 4:13 PM,
MichaelQuigley@xxxxxxxxxx wrote:

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

Yes, that's what I intended to say.

(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).

Yes, that dialogue box pops up. Ignoring it (leaving it unacknowledged)
does NOT stop the batch job from continuing on.

Then there usually isn't sufficient time to reset everything and
have the SEP fire on the next call.

Now that's an interesting difference.

With 'Terminate debug on completion' selected,
I set a conditional breakpoint on the first CALL.
Reached it, added some variables to the monitor and F8 to continue to
the end.
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.

My original test scenario only had a pair of CALLs in the CLP. When I
ran this test with 5, I could never see CALL 3, 4, or 5. I'd probably
debug the calling program and breakpoint the CALL.

Weird.