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

Leaving with a simply "GOBACK"

Setting breakpoint on "GOBACK". It stops of the first execution of first
call, but still ignores the second call.

Thanks.

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On
Behalf Of smorrison@xxxxxxxxxxxxxxxxxxx
Sent: Friday, February 08, 2008 3:33 PM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] Debugging v7.0 SEP will not stop in second callto
program.

How are you leaving the first program? Does anything change if you set a
breakpoint on the last statement in the program and click on the execute
next statement (down arrow button)?

Steve

Steven Morrison
Fidelity Express





"Andy Devine" <andyd@xxxxxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
02/08/2008 03:14 PM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
<WDSCI-L@xxxxxxxxxxxx>
cc

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