Re: sep only breaks on the first call to program

IIRC, there are two cases when this can happen:

1) There's a preference (which I can't remember where it's at right now)
which terminates the debug session when the program finishes executing.

2) The subsequent calls to the program happen sooner than the system can
completely terminate the previous debugging.

The easiest way I know to fix it is to debug the calling CL (or whatever
kind of program the caller is). Then you can step into the program you
really want to debug. When that program completes, your debug session is
still active so it should stop at your breakpoints whenever they are
encountered. If I can find the preference, I'll post an update. I just
don't recall where it's set right now.

To debug the calling program (which sounds like it's OPM, you'll have to
set up a run configuration for an 'iSeries Debug Job.'

wdsci-l-bounces@xxxxxxxxxxxx wrote on 10/19/2010 03:37:54 PM:

On 10/19/2010 2:14 AM, David FOXWELL wrote:

Hi,

I have an RPGIII that is called in a SBMJOB. It makes regular calls to

an ILE RPG that I'm trying to debug. I set up my break points, the

program

stops on the first call. When I click Resume (F8) I get the program
terminated message. That's correct, the program has terminated and

control

has returned to the RPGIII, but what when the ILE gets called again, SEP

does not react. How can I debug this program without STRSRVJOB and

STRDBG?