Funny, I thought it was much better.
In particular, the ability to start the debug and set the breakpoint and
exit. Then you can just call your application by any means. STRISDB requires
me to jump through hoops to start a program. 
Also, function keys are a lot cleaner

-----Original Message-----
From: Jim Waymire []
Sent: Thursday, November 11, 1999 7:00 AM
To: Gary Monnier;
Subject: Re: Debug

Thanks for the input.  I got that to work, but just couldn't believe that
the debug utility for ILE would be so far behind the debug utility for
RPGIII, i.e., strisdb.  Is there a better way or product out there?
Jim Waymire

-----Original Message-----
From: Gary Monnier <
<> >
To: <>  < <> >
Cc: <>  < <> >
Date: Wednesday, November 10, 1999 2:56 PM
Subject: Re: Debug

I'm assuming you want to bebug an ILE RPG program.  The first thing you need
to do is ensure you have keyword DEBUG(*Yes) in your  H-spec(s).  Next step
is to compile your program with the debug parameter of your choice (My
preference is *ALL).  After  that, all you have to is use the STRDBG
command.   STRDBG will present  you with a listing you can then set
breakpoints for.  Once you've set your breakpoints press F3 or F12 to exit.
Now execute your program.  It's that simple.
Use all the steps  mentioned above, except step 1, to debug ILE CL programs.

-----Original Message-----
From: Jim Waymire <
<> >
To: <>  < <> >
Date: 10 November 1999 02:33
Subject: Debug

Trying to do and ILE program with date calculations.  How do i run
interactive debug on an ile pgm?        
Jim Waymire

| This is the Midrange System Mailing List!
| To submit a new message, send your mail to
| To subscribe to this list send email to
| To unsubscribe from this list send email to
| Questions should be directed to the list owner/operator:

This thread ...

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

This mailing list archive is Copyright 1997-2020 by 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].