|
To: wdsci-l@xxxxxxxxxxxx
From: MichaelQuigley@xxxxxxxxxx
Date: Mon, 21 Sep 2009 08:30:46 -0400
Subject: Re: [WDSCI-L] debugging in WDSC
Are you debugging via a SEP (Service Entry Point)? If not, that might
work. The problem happens when the program ends the first time, the
debugger doesn't know it will be called again so your debug session
terminates and the system takes the job out of being "serviced" by your
debug session. Even setting a SEP might not always work on repeated calls
if the timing of the calls comes too quickly--the first debug won't have
completed and released the job when the program is called a second time.
This used to be a problem and I don't know if it was ever addressed.
What we usually do when trying to debug repeated calls to a program is
start debugging on the main program and step into the desired program.
Then it should be able to stop at your breakpoint every time.
wdsci-l-bounces@xxxxxxxxxxxx wrote on 09/19/2009 01:00:03 PM:
----- Message from johnny wiggo <johnny_wiggo@xxxxxxxxxxx> on Sat,--
19 Sep 2009 01:21:26 +0800 -----
To:
<wdsci-l@xxxxxxxxxxxx>
Subject:
Re: [WDSCI-L] debugging in WDSC
I set a breakpoint in the called programfirst time it stops at the
breakpoint and at the beginning of the program.
when i hit the breakpoint i do resume.
at the second call to the program in the same job it doesnt stop in
the program like (STRDBG) does!
I saw that someone was asking the same question 2006 but there was
no answer to question is to work this way or can you work around it?
This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.
As an Amazon Associate we earn from qualifying purchases.
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.