Re: Debugging Blues

Don,

If you look at 'Run' on the menu bar, you can see that:

F5 = Step Into
F6 = Step Over

What you need is 'Step Into.' When you press F6, it's telling the
debugger you want to step over the call and to the next statement in the
current program.

HTH,
Michael Quigley
AS/400 Programming Section
The Way International
www.TheWay.org

wdsci-l-bounces@xxxxxxxxxxxx wrote on 03/11/2008 01:00:03 PM:

----- Message from "dnitke" <dnitke@xxxxxxxxxxxxxxx> on Tue, 11 Mar
2008 07:13:44 -0700 -----

To:

<wdsci-l@xxxxxxxxxxxx>

Subject:

[WDSCI-L] Debugging Blues

. . .
. . .
. . .

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.