×
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.
Xuan,
I have tried setting a line breakpoint inside called program the
first time a SEP in encountered. Then hit F8 to resume and WDSC does NOT
stop at line breakpoint on second call to program.
Does this work for you?
Thanks.
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On
Behalf Of Xuan Chen
Sent: Friday, February 08, 2008 9:03 PM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] Debugging v7.0 SEP will not stop in second callto
program.
Andy,
SEP is not a regular line breakpoint. It is a mechanism used to put a job
under debug easily. The debug session will be trigged when the program
(or module or procedure) where this breakpoint set is executed AND if the
job (running this program) has not been under debug yet. That is why the
first CALL, a debug session is invoked. But for the second CALL, since
this job has already under debug, and SEP is not really a line breakpoint,
your COBOL program will just run to completion.
You may need to set a line breakpoint in the called program when you first
stop there.
Thanks,
Xuan Chen, Problem Determination Tools for iSeries
(905) 413-3769 T/L 313-3769
xuanchen@xxxxxxxxxx
"Andy Devine" <andyd@xxxxxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
02/08/2008 04: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
As an Amazon Associate we earn from qualifying purchases.
This thread ...
Re: Debugging v7.0 SEP will not stop insecond callto program., (continued)
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.