I have been using since 6.1 and have not had any issues. It leaves a
lot of garbage out of the programs although the static storage is
still sky high. Still cannot figure out why a RPG/ILE program using
the MAIN keyword, a single procedure doing nothing and NOUNREF used
with no debugging information needs 4k of static storage. The same
thing in a C program needs 270 bytes.

On Fri, Apr 6, 2012 at 8:56 AM, Jeff Crosby <jlcrosby@xxxxxxxxxxxxxxxx> wrote:
I haven't experimented with this yet, but it occurs to me that with V7's
option RPG will be doing much the same thing as SQL. Both have to have
to the base record buffer - the difference being that RPG has always
unloaded the
individual fields into their storage locations. With NOUNREF only those
fields that
are actually used will be retrieved.

Somehow, though I've been on 7.1 for a long time (and this was available on
6.1), I somehow missed this NOUNREF option.

Is there any downside to making NOUNREF the default?  I have read you can't
debug a variable that's not used in the program if NOUNREF is specified,
but if the variable isn't used I'm not sure how often one would need to see
the value when it isn't even used . . .

Jeff Crosby
VP Information Systems
UniPro FoodService/Dilgard
P.O. Box 13369
Ft. Wayne, IN 46868-3369

The opinions expressed are my own and not necessarily the opinion of my
company.  Unless I say so.
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.

This thread ...


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

This mailing list archive is Copyright 1997-2020 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].