Re: Managing Duplicate Software

Al,

While this doesn't directly answer your question, let me tell you how I do 
things
here.  Software version management is handled through the library list.  It goes
something like this for the users.

Site specific mods.
General mods.
BPCS PTF.
BPCS Std.

In accordance with SSA's recommendations, QGPL and QTEMP are lower than these.
The trick we pull off is to put QGPL and QTEMP higher than these for the
programming staff.  We copy the troublesome code into QGPL, make mods, compile,
test.  This doesn't affect the users at all because they are running the
"original" version because it is higher in the list.  When we are satisfied with
the modifications, we move it back to either the general mods or specific mods
libraries.

Bill



MacWheel99@aol.com wrote:

> My scenario =
>
> SSA provides original, then fixes ... sometimes several BMR, PTF which we put
> earlier in library list
> We sometimes copy source to test library, which eventually finds its way to
> implemented modification.
> I also sometimes have backup version of what modification looked like before
> pile on more mods.
> When there is uncertainty that a change will work right, we need the backout
> version, but once everything is working fine I tend to forget about that
> mountain of multiple redundant no longer used old copies that have an impact
> on disk space.

+---
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to BPCS-L@midrange.com.
| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: dasmussen@aol.com
+---