Sorry wrong list maybe. Sending to RPG list.
-----Message d'origine-----
De : midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] De la part de David FOXWELL
Envoyé : vendredi 23 janvier 2009 10:03
À : Midrange Systems Technical Discussion
Objet : 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 KNOW these should be in service programs. But for now...
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 M1 in his BNDDIR. He finds that he cannot compile the program when he installs, although he had no problems when compiling in his isolated environment.
Programmer 2 only now finds that he must add the necessary modules to his own BNDDIR to be able to create pgm2.
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 the whole lot of modules in it?
Does the compiler only use what it needs from the BNDDIR. Isn't it similar to having one PF as a data dictionary for using REFFLD in DDS?
David FOXWELL
Service Informatique
Tél : 03 90 23 91 63
david.foxwell@xxxxxxxxx<mailto:david.foxwe@xxxxxxxxx>
P Pensez à l'environnement avant d'imprimer ce message
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at
http://archive.midrange.com/midrange-l.
midrange.com
