Re: Debugging.

Hands down, I like the debugger in WDSC better.  It's integrated.  It 
includes the outline view.  It doesn't require switching between tools. 
You can set breakpoints when editing in the source and they'll be active 
when debugging.  The list could go on.

The big thing to understand is the debugger launch configurations.  Once 
you understand these, you'll love the debugger.  Most of the time, I open 
the debug perspective.  Then I click on the drop-down triangle next to the 
bug icon.  From there I select 'Debug...'.   Then I generally use the 
iSeries debug job option.  Right-click and choose new.  Specify a name for 
the debug launch configuration, then specify the job-name and user-id. 
With a batch job you can specify '*' for the job-number (just be sure the 
batch job is submitted on hold).  With an interactive job, specify the 
actual job-number.  Add the program to be debugged in the box at the 
bottom.  Make sure 'Step into' is checked.  Check 'Update production 
files' as appropriate. Then click 'Debug'.

There may be other things which need to be done from time-to-time, but 
that covers about 90% of my debugging needs.

Even better, use Service Entry Points (SEP).  These make life *sooo* easy. 
 There should be a lot of posts in the archives about using SEPs.

wdsci-l-bounces@xxxxxxxxxxxx wrote on 12/07/2006 01:24:22 PM:

date: Thu, 7 Dec 2006 12:19:48 -0600
from: "Turnidge, Dave" <DTurnidge@xxxxxxxxxxxxxxxxxxxx>
subject: [WDSCI-L] Debugging.

I am now to the point of attempting to tackle debugging in WDSC. All of
the instructions I read were very confusing. I called IBM to get some
help there - and was led to Help/Cheat Sheets. Unfortunately, the cheat
sheet titled, "Debugging a 5250 RPG or Cobol application" was out of
date, and the instructions didn't match WDSC menus, etc.

I called back, and we started playing with WDSC, not making much headway
when the IBM'r said that he preferred using the Graphical Debug
interface. He led me through iSeries Navigator to this completely
different debugging method.

I would like to use whatever is the "best" debugger available to me. 

What do you use, and why do you consider it better than the alternative.
And, what's the best way to learn it?

Thank you,

Dave