Re: Debugging RPT programs -- RPG400-L

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

Mike,

We use RPT a lot.  For debugging we just use the line numbers from the compile
spool file and use STRDBG.

It's a minor inconvenience to compile but not a major job.

Mike.Barton@ecsoft.co.uk wrote:

> >To debug RPT programs you have to recompile them specifying *SOURCE on the
> >RPTOPT parameter and naming the source something different on the
> >OUTFILE/OUTMBR parameters so as not to overwrite the original.  This creates
> >an expanded source member with the /COPY's included.  Then you need to point
> >to your new source member on the SRCMBR parameter of the STRISDB command.
>

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

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