Hey Paul,
The first scenerio yes the second no. I do set break points in my SQLRPGLE programs and it doesnt stop again. The reason seems to be that the debug ends giving the message box that the program has ended and never catches again unless I restart the debug job.
Don
----------------------------------------
From: "Bailey Paul" <paul.bailey@xxxxxxxxx>
Sent: Tuesday, March 11, 2008 7:56 AM
To: "Websphere Development Studio Client for iSeries" <wdsci-l@xxxxxxxxxxxx>
Subject: Re: [WDSCI-L] Debugging Blues
Hi,
Something I worked out when debugging SQLRPGLE procedures was that you
needed to set a breakpoint when your debugee source first presented
itself in the WDSC debug perspective. If you didn't, the procedure would
never stop again. (Or it seems that way to me.)
Also, if you have an OPM CL program between two RPGLE programs (i.e. A
calls B which calls C, where B is CL and A&C are RPGLE), you can not
debug the second RPGLE program more than once (Unless you reset the
service entry point.) I don't know why, and I didn't get a response from
this list when I reported it sometime back. We converted the CLs to
CLLEs to get past this little problem.
Do either of these situations look like yours?
Best regards,
Paul
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Adam Glauser
Sent: 11 March 2008 14:24
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] Debugging Blues
dnitke wrote:
Program A calls Program B
Program C calls Program B
Program D calls Program B --- want to debug this call
2. Adding new programs to a run in WDSCi debugger doesnt seem to work.
Take the above scenerio; I then thought hey I will start debugging
Program D and add Program B afterwards because if I add it from the get
go it will catch the first call and I'm screwed. So I start the debug
with only Program D. Hit F6 to the call then change the properties to
add Program B, hit F6 and the program never comes up like 5250 showing
the source until the actual abend occurs (problem I'm fixing) which is
way into the processing of the program.
If I follow your meaning, a workaround would be to set a breakpoint on
the call to Program B from program D, then when you hit that breakpoint
to a 'step into' to start debugging program B.
midrange.com
