No, I have no jobs with MSGW. The called program is clean, no abends. Just
for kicks I took out the screen process with same results. I hit F8 to
resume from first call and WDSC does not pick up on second call.
Andy.
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On
Behalf Of Aaron Bartell
Sent: Friday, February 08, 2008 4:09 PM
To: 'Websphere Development Studio Client for iSeries'
Subject: Re: [WDSCI-L] Debugging v7.0 SEP will not stop insecond callto
program.
Another thing I have found when testing programs with "bugs" is that doing a
Terminate doesn't end the job like one would think. It simply terminates
the debug session, but releases the job to continue running the remainder of
it's code. That can sometimes amount to a job in MSGW status, and the
second time you go in to start the debug it doesn't start up because of the
MSGW job. Do you have any familiar MSGW jobs?
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:59 PM
To: 'Websphere Development Studio Client for iSeries'
Subject: Re: [WDSCI-L] Debugging v7.0 SEP will not stop in second callto
program.
No, I'm not recompiling between calls and I learned the hard way to remove
SEP before recompiling and then reset SEP. I tried shutting down WDSC and
tried again with same result. Like I expected. I have never been able to
get WDSC to stop on second call to program.
I should mention something that I did not before: The called program is
displaying a screen (DDS).
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On
Behalf Of Aaron Bartell
Sent: Friday, February 08, 2008 3:34 PM
To: 'Websphere Development Studio Client for iSeries'
Subject: Re: [WDSCI-L] Debugging v7.0 SEP will not stop in second callto
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
