RE: Debugging MI code

> . . . you can add a breakpoint at an mi instruction:
>   addbkp   '/000e'
>
> variables can be displayed using DSPPGMVAR by refering to their ODT
> number
>   dsppgmvar  '/005d'


Which is to say, you use the OPM debugger, not the ILE debugger (don't
worry, the system knows which debugger to invoke from a STRDBG command),
and unless you insert named breakpoints in the source, you need to use the
"instruction number" column of the compilation listing to figure out where
to ADDBKP. Which is to say, save your latest compilation listing as a
debugging reference.

Oh, and you shouldn't need to refer to variables by their ODT numbers; the
names work fine for me, and I've never even tried referring to a variable
by its ODT number.

And it's much easier than it looks (unlike trying to debug an ILE C
program with the ILE debugger, which is much harder than it looks).

--
JHHL