×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Tom,
Yea, I have placed a SEP on originating program and line breakpoints
on both calls. WDSC will stop at breakpoints and I can step into called
programs. This is the only way I can figure out to get what I need.
Problem (see reply to Xuan e-mail) is: I could possible be setting many
breakpoints and maybe more than one program.
Thanks for the input.
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On
Behalf Of qsrvbas@xxxxxxxxxxxx
Sent: Friday, February 08, 2008 5:53 PM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] Debugging v7.0 SEP will notstop insecond callto
program.
Andy Devine wrote:
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.
Just to cover all possibilities, do you have a breakpoint on the
second CALL statement? This is purely to ensure that the second CALL
actually happens during debugging and some obscure bug isn't
bypassing it.
It had to be asked. (From personal experience...)
Tom Liotta
midrange.com
