|
-----Original Message-----On
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
Behalf Of David FOXWELLKNOW
Sent: Friday, January 23, 2009 4:06 AM
To: RPG programming on the IBM i / System i
Subject: Binding directory question
Hi,
All our modules are bound by copy.
When a module is modified, all programs using that module are rebound
automatically by our installation tool.
This is causing more and more headaches, as more and more modules become
bound by lots of programmes.
Each program uses a binding directory of the same name. The same modules
often end up duplicated in the BNDDIR. Some are even in EVERY BNDDIR. I
these should be in service programs. But for now...M1
Problem :
Programmer 1 adds a call from module M1 to a new module M2. He adds M2 to
BNDDIR of Pgm1, compiles and installs.
Programmer 2 is working in an isolated environment on Pgm2 that also has
in his BNDDIR. He finds that he cannot compile the program when heinstalls,
although he had no problems when compiling in his isolated environment.own
Programmer 2 only now finds that he must add the necessary modules to his
BNDDIR to be able to create pgm2.the
My question :
Given that we continue to bind exclusively by copy, what would happen if,
instead of a BNDDIR for each program, we made one huge BNDDIR and shoved
whole lot of modules in it?to
Does the compiler only use what it needs from the BNDDIR. Isn't it similar
having one PF as a data dictionary for using REFFLD in DDS?list
Thanks
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing
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.
As an Amazon Associate we earn from qualifying purchases.
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.