RE: Managing Duplicate Software

[zieske@xxxxxxxxxxxxxxxxxx]

Just my two cents. I fight like mad to prevent the splitting of a logical into a
separate library from the physical. Having the two in different libraries can
create all sorts of ugly situations from back-up and restore problems to
unnecessary limitations with crtdupobj. And sooner or later a logical gets
created that points to the wrong library. I don't know how many times I've had
to fix the situation where logicalX points to production, but logicalY for the
same file in the library list points to test. The system has gone to Hades and
nobody has a clue why. Source is a different matter, by all means keep your
source in separate libraries. Just keep the created logicals in the same library
with the physical to limit potential operational problems. "DSPOBJD 'logical'
*file *service" tells you whether the logical was created from BPCSRCM, BPCSSSA,
BPCSPTF, etc., so you know who owns the logical


+---
| 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
+---