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



Wow.  I just wrote two ten line programs that initialize a one byte
character variable ten times.

The RPGIII program compiled *srcdbg is 49152 bytes, compiled vanilla 40960
bytes.  The RPGIV program compiled debug view *all is 98304 bytes.

Sounds like something that you can't ignore completely.  OTOH, what we do
with in house mailing list processing has a more dramatic effect on disk use
than the proverbial infinite number of monkeys, uh programmers, could have.

> -----Original Message-----
> From: Bob Cozzi [mailto:cozzi@rpgiv.com]
> Sent: Thursday, June 13, 2002 10:19 AM
> To: rpg400-l@midrange.com
> Subject: RE: **Debug options**
>
>
> Originally, RPG IV program objects were at least 4 times the
> size of the
> equivalent RPG III program object.
> That was in 1995 when DASD was low volume and expensive.
> Today, they've bettered that ratio a bit, but you still will
> end up with
> an RPG IV program nearly double the size of the RPG III
> equivalent. And
> that's after you omit debug info and then remove observability.
>
> If DASD isn't an issue (as it isn't in many installations today) don't
> waste your time worrying about it. If you're at 95% of DASD
> utilization,
> and most of your DASD use is in application programs written
> in RPG IV,
> then you can worry about it.
>
> Bob Cozzi
>


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.