Re: DBGVIEW *ALL Question

[Jim Langston <jlangston@xxxxxxxxxxxxxxxx>]

I looked at the size of a compiled program, then looked at the size of
the same program comiled with *LIST, *SOURCE, *ALL etc...

If you give *NONE the file is rather small, but once you put just about
any meaningful information into the pgm with debug view, the size jumps,
then stays about the same for all the options.  The size difference between
a program compiled with *LIST and *ALL was miniscual.  There was
a jump between *NONE and *LIST, but looking at the size, and looking
at my DASD, and realizing I am taking up all my DASD with data, not
compiled programs, I optioned to make *ALL the default for compiling
programs.

If I remember correctly, I think it about doubles the size of programs.
But, compiled programs are rather small to begin with, so it's not actually
that much space at all.

Regards,

Jim Langston

Douglas Handy wrote:

> Bill,
>
> >Meaning, will it slow down the system if all programs
> >start being compiled like that,
>
> No, unless you normally run in debug mode. :)  The debug info is
> stored in separate pages, so is not even loaded in memory unless run
> under debug..  A pretty neat design.
>
> >and will it use up a lot more space?
>
> It will take more space, but I wouldn't call it "a lot more".  On the
> systems I work on, the % of DASD used by application program libraries
> is fairly trivial compared to the % consumed by data.  So even if each
> program takes "a lot more space" than the same program without the
> debug info, the overall effect on the system is not "a lot more".
>
> YMMV.
>
> Personally, I like having the debug info available, but use *LIST as
> my default.
>
> Doug

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