BNDDIR problem

[David FOXWELL <David.FOXWELL@xxxxxxxxx>]

Hi everyone,

I need to resolve a compile problem in our "change management system".

Programmer 1 takes pgm A for modification.
Programmer  2 takes pgm B for modification.

Programmer 2 adds a module M1 to the BNDDIR of pgm B.
Programmer 2 installs his modifications and the CMS finds that pgm A also needs M1 and adds it to the BNDDIR of pgm A so that it will compile.

This is a problem caused by the complete non-use of SRVPGM, which will change in the future, but when, I do not know.

Later, programmer 1 installs his modifications. He could have modified his copy of pgm A's BNDDIR. We want to be able to fusion programmer 1's BNDDIR with the BNDDIR of pgm A in production, as it has been modified since programmer 1 started his modification.

As an alternative to writing a procedure to compare BNDDIR's, is having only one BNDDIR with all modules that export listed in that BNDDIR an option? There are currently 3500 such modules on our system.

TIA