*MODULEs are bound by copy, *SRVPGMs are bound by reference.

Kevin Bucknum <Kevin@xxxxxxxxxxxxxxxxxxx> wrote: The API you probably want to use is QBNLPGMI. Bryan Meyers has a good
example of using it in his program at
http://www.bmeyers.net/resources/anzilepgm.php (which probably does
exactly what you are looking for anyways). But I'm confused as to why
you think that adding modules to a BNDDIR will bind them by copy and
uses up disk space. I know that there are certain instances where even
though you have a module in a BNDDIR that it will bind by copy, but I
thought that was the unusual case. Maybe someone else can expound on
that piece.

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of David FOXWELL
Sent: Thursday, August 07, 2008 2:58 AM
To: RPG programming on the AS400 / iSeries
Subject: RE: Question about service programs


As a preliminary to my "go forward plan" as Mark put it, I'd like to be
able to determine how many times the same module is bound by copy to a
program. I'd like to be able to have an idea as to how much memory we
could save. We have one big module that is frequently modified by calls
to procedures in new modules. As this big module is bound to many
programs, such a modification involves adding the new module to all the
BNDDIR of all the programs that bind in the big module. If I understand
correctly, that means every time a new module is added, it is copied as
many times as there are programs that find themselves bound to the big
module. To make things worse, more and more programs are binding in this
big module. The disk space is decreasing therefore exponentially.

Now in DSPPGM, I can't get the results into a file. Anyone help out here

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