Re: 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?