DBGVIEW and program size

[Buck Calabro <buck.calabro@xxxxxxxxxxxxxxxxx>]

Brian wrote:

>> What advantages does DBGVIEW(*ALL) have over DBGVIEW(*LIST)?

>*ALL allows you to choose your preferred view (source, copy or 
>compile listing representation) during the debug session, using 
>F15.  *LIST limits your view to compile listing only.  However, the 
>former will increase the size of the *PGM object size.

Taking a stab at an engineering approach, here is a smattering of data from
my own experimentation.  V4R4

Small sockets program using mostly C functions.  DFTACTGRP(*NO) ACTGRP(QILE)
Indent(*none), DEBUG in header
*NONE           *SOURCE         *LIST           *ALL
122880          172032                  225280          225280
                40%                     31%             0%

Medium program converted from RPG III (subroutines) to RPG IV (subroutines
and procedures)  Compiled with DFTACTGRP(*NO) ACTGRP(QILE) bnddir(qc2le),
DEBUG in header
*NONE           *SOURCE         *LIST           *ALL
544768          659456                  962560          983040
                21%                     46%             2%

Large interactive RPG IV program converted from RPG III - no procedures.
Compiled with dftactgrp(*no) actgrp(qile) indent(*none)
*NONE           *SOURCE         *LIST           *ALL
323584          401408                  516096          528384 - no DEBUG in
header
327680          401408                  516096          528384 - DEBUG in
header
                24%                     29%             2%

Buck Calabro


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