Debugging Blues

["dnitke" <dnitke@xxxxxxxxxxxxxxx>]

    Hey All,

In the past few weeks I have done alot of debugging using WDSCi. Now dont get me wrong, I have always used the debugger but never put it through its paces until recently. What I have found is there are a several things that either I dont understand and are doing wrong or just dont work.  See below for a couple of issues I have run into.

1. Debugging (Servicing the Job) ends after the program runs once. This is annoying considering if I do a STRSRVJOB in 5250 and STRDBG it will catch multiple calls to my program. This is really important for API's and I know SEP will work for this but currently I'm on a PC that wont do SEP and then what if your debugging RPGIII. Here is the scenerio I'm doing just as an FYI:

Program A calls Program B
Program C calls Program B
Program D calls Program B --- want to debug this call

*** al three calls happen with one user event on the web application and if I debug program B servicing the QZDASOINIT job it works great but in WDSCi only the first call hits after that no.

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.

Like I said it maybe that I'm not doing the process right and invite any suggestions but currently I have had to use the 5250 (god help me) and relearn all the cryptic commands:)

Thanks
Don N.