Don,
Yea, I can put SEP or breakpoint before call and then step into. I
was trying to avoid this, because the program I'm calling is displaying a
screen. This screen can be called from several different places in a
program or called from several different programs. I'm trying to set and
stop one place instead many places.
Thanks for the input.
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On
Behalf Of dnitke
Sent: Sunday, February 10, 2008 8:48 AM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] Debugging v7.0 SEP will not stop in second callto
program.
Sorry about replying to myself but saw the response about stepping into the
program instead of relying on the SEP. Thats a good point for which I will
try the next time I'm debugging since it sort of makes sense the SEP is a
one shot deal. Notice I said sort of:)
Don N.
----------------------------------------
From: "dnitke" <dnitke@xxxxxxxxxxxxxxx>
Sent: Sunday, February 10, 2008 6:38 AM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] Debugging v7.0 SEP will not stop in second call to
program.
Hey Guys,
This happens to me as well and dont remember the exact details I got a
response saying that SEP has delay issues so by the time your SEP program is
called a second time (mine was in a loop reading through work file records)
it doesnt catch. Dont know if IBM is aware and dont know if it can be fixed.
I delayed my process to make it work and that seemed to help but wasnt full
proof.
Don N.
----------------------------------------
From: "Aaron Bartell"
Sent: Friday, February 08, 2008 1:35 PM
To: "'Websphere Development Studio Client for iSeries'"
Subject: Re: [WDSCI-L] Debugging v7.0 SEP will not stop in second call to
program.
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
midrange.com
