Re: Debugging v7.0 SEP will not stop in second call to program.

Your problem has nothing to do with COBOL. The same holds true for RPG or
any other language running on the OS. A service entry point will only
trigger debugging the first time the program is activated. From then on,
you have to step through the program (including stepping out of it into
the calling program) to continue debugging. This means the calling
program has to be compiled for debugging, also.

It's a limitation of the service entry points. I've wrestled with the
same problem many times--both in COBOL and RPG.

wdsci-l-bounces@xxxxxxxxxxxx wrote on 02/08/2008 04:33:32 PM:

date: Fri, 8 Feb 2008 15:14:36 -0600
from: "Andy Devine" <andyd@xxxxxxxxxxx>
subject: [WDSCI-L] Debugging v7.0 SEP will not stop in second call to
program.

The following is condensed version of a COBOL program.



PROCEDURE DIVISON.

CALL 'programname'

MOVE

MOVE

IF

Whatever

CALL 'programname' (same name as first call)



I can set a SEP on 'programname' and WDSC will stop and pull up DEBUG
session. I can look at variables, setup breakpoints, and do whatever I

need

to do. After I leave first call I would expect to stop at second call

(with

SEP) to the program, but WDSC does not stop. The originating programs

ends.

Has anyone seen this situation?



Andy Devine

800-707-6422 Ext 843

andyd@xxxxxxxxxxx