Debugger Goodies
August 29, 2007
I was playing around with the integrated iSeries debugger in WDSC the other night and stumbled across two features I’d never noticed before and thought I’d share them here. In the Breakpoints view you can specify different ways to group breakpoints by selecting Group By > HowYouWantToGroup from the views pull down menu (that’s the upside down triangle). For example, if you are debugging a multi-tiered application and have some RPG, Java and JSP breakpoints, you could select Group By > Breakpoint Types to see them categorized by type. Here is an example:
The other feature is you can add multiple renderings to the memory view for a single field. When monitoring memory (right click on field and select Monitor Memory > Rendering) you see a list of all fields on the left side and when you select a field you see it’s memory on the right side with the rendering you selected when you added the field to the view. However you can add additional renderings by clicking on the plus sign in the top right corner of the view (there are two plus signs in the view, one adds additional fields and the other adds additional renderings for the selected field).
Background: the memory view shows the contents of memory for that field. If you select Hex then you see the raw bits. A rendering takes those raw bits and displays them as a data type; as EBCDIC for example. You can add your own renderings for Java and I believe there is a way to do this for RPG and COBOL. I’ll post that once I figure it out.
Even as a technical team lead on WDSC, I continually learning new things the tools can do. Paul Tuohy said in his keynote at this years TUG TEC conference, playing is one of the best ways to learn. I couldn’t agree more!

March 11, 2008 at 4:23 pm
In Debug I can not get a break point with a condition to stop when the condition is met. Is there a trick to this? I use Add a Line Breakpoint to set it up
Line [YCOMEACC.RPGLE:118] [conditional: SAV_AGNT = '10000000']