× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

> . . . 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).


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2023 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.