Correct. The debug data is the internal stuff required to be able to set breakpoints, display variable contents, run traces (anyone still do that?), and dump a program. It's sufficient for the old debug line commands, but doesn't provide the source code information needed by RDi. That's what DBGVIEW(*SOURCE) or DBGVIEW(*LISTING) provide.
Dave Shaw
________________________________
From: Buck Calabro <kc2hiz@xxxxxxxxx>
To: wdsci-l@xxxxxxxxxxxx
Sent: Wednesday, August 28, 2013 3:17 PM
Subject: Re: [WDSCI-L] RPGLE SEP Debugging of a program that has many functions
I *think* the 'debug data = yes' is different to the DBGVIEW setting
that was in effect at the time the module was compiled. Which is to say
that it'll say yes even if you have DBGVIEW(*STMT) (the default).
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2026 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.
midrange.com
