RE: Managing Duplicate Software

["Lynam, Martin" <Martin_Lynam@xxxxxxxx>]

Al:

What about the DSPOBJD (Display Object Description) command. Use of this
command allows creation od an *OUTFILE that may then be analyzed. Say that
you want to report instances of custom versions of BPCS names. Say that your
virgin programs are in library BPCSO and the custom code is in BPCSUSRO.
Also assume that there are a number of other program object libraries
beginning with BPCSxxxx that you don't want to include (this would prevent
you from wild-carding the library name in he command). You would execute the
DSPOBJD command twice: once with a *REPLACE option to the output file name,
and a second time with an *ADD option. For example:
    
        ===> DSPOBJD OBJ(BPCSO/*ALL) OBJTYPE(*PGM) OUTPUT(*OUTFILE)
OUTFILE(MYLIBR/PGMDATA) OUTMBR(*FIRST *REPLACE)


The second execution will add the information from the BPCSUSRO library:
    
        ===> DSPOBJD OBJ(BPCSUSRO/*ALL) OBJTYPE(*PGM) OUTPUT(*OUTFILE)
OUTFILE(MYLIBR/PGMDATA) OUTMBR(*FIRST *ADD)


The output file will be created if it does not exist. It will be cleared if
it does exist prior to population unless the *ADD option is specified.

Marty Lynam
Creative Management Concepts
713-522-2271

> -----Original Message-----
> From: MacWheel99@aol.com [SMTP:MacWheel99@aol.com]
> Sent: Thursday, March 04, 1999 12:09 PM
> To:   BPCS Users Mailing List
> Subject:      Managing Duplicate Software
> 
> from Al Macintyre
> 
> Is there a straightforward *OUTFILE to Query which could inventory
> duplications and/or what add-on tools are worthwhile seeking that aid disk
> management MIS responsibilities which must be common to most every BPCS
> installation?
> 
> 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.
> 
> One approach might be a query report:
> List duplicates with same naming - source & execution objects in multiple
> libraries - include last used, changed, saved, type, size, to catch
> irregularities, substring according to naming conventions
> 
> But this challenge cannot be unique to us - there may be better solutions
> out
> there.
> 
> Al Macintyre
> BPCS 405 CD = approx 25-30 users
> AS/436 V3R7 soon to V4R3
> +---
> | 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
> +---
+---
| 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
+---