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

["Aaron Bartell" <albartell@xxxxxxxxx>]

Are you recompiling the program inbetween calls?  You need to refresh the
SEP each time after a compile.  If that doesn't work you will need to
completely shut down WDSC and restart it.  I have the same issue where if I
do a SEP debug at let's say 8am and then don't do another till 9am, it
doesn't pick up the SEP, even if I refresh and/or re-add the SEP.  I have
even tried stopping and restarting the debug servers with no success.
Completely restarting WDSC is the only thing that fixes it.

HTH,
Aaron Bartell
http://mowyourlawn.com

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On
Behalf Of Andy Devine
Sent: Friday, February 08, 2008 3:15 PM
To: WDSCI-L@xxxxxxxxxxxx
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