Re: Regarding retrieving source from modules -- 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.



 >> My only convert with compiling with DBGVIEW(*LIST) or (*ALL) is the
executable size increase.

Unlike PC (and other software) there is no increase in executable size for a
program with debug data.  Debug information is only brought into memory when the
program is being debugged.  The only reason for removing it is to reduce DASD
occupancy or (if you are a software vendor) to stop customers from seeing how
truly horrible your code is <vbg>

The only increase is in DASD usage for the compiled program - this can be
reduced (to less than the corresponding OPM program size in some cases) by
compressing the observability information using CPROBJ.


+---
| 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-2025 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.