3. USAGE GUIDELINES › 3.1 Setting Up VCC for Operation › 3.1.4 Scheduling Considerations with CA MICS and DFHSM › 3.1.4.2 Weekly Collection of Catalog Status (CATCHECK)

3.1.4.2 Weekly Collection of Catalog Status (CATCHECK)

This approach illustrates another variation in the set of
VCCPARMS keywords that fulfills special operational needs and
assists the storage administrator in identifying problem data
sets.

Let's assume you would find it useful to choose one VCC run
per week to examine the catalog status of VTOC data sets.
The CATCHECK=Y option will perform this check but it is not
worth the extra processing incurred to perform this extra
function every day.  Therefore, every week or two, perhaps on
a weekend night, it is useful to add the CATCHECK function to
your production run.

A "weekly" VCC PROC for catalog check processing should take
the following into consideration:

    o  The "production" VCCDATA and VCCNTROL data sets can be
       used, because this is essentially the same data
       collection process as the "production" run.

    o  If HSM=Y is requested in "production", it should be
       retained in this "weekly" run too.

    o  Serialization of the VTOCs is not allowed during
       CATCHECK processing.  You may want to reduce the level
       of VSAM and VTOC subtasking in the "weekly" run too.
       Expect longer run times for the job but the same
       magnitude of records written to VCCDATA.

    o  Be aware that the LOCATE done by VCC with the CATCHECK
       option will be subject to the variety of ways
       enterprises can connect user catalogs and share DASD
       in today's complex environments.

       For example, you may want to consider the use of
       carefully selected EXCLUDEVOL lists when running with
       CATCHECK=Y.  For example, if the IPL volume for SYSB
       is online and shared with SYSA, all SYS1. data sets
       cataloged in the master catalog on SYSB will be
       accessible by VCC but naturally, LOCATE processing
       will indicate that these SYS1. data sets are
       cataloged to a different volume.

       Therefore, if each weekend you presented your
       production VCC run with a VCCPARMS setup that
       requested CATCHECK=Y and EXCLUDEVOL=(RESBRS), you
       should know that the DURATION for all data sets on
       that EXCLUDED volume will be properly adjusted when
       the next VCC run in production performs the scan of
       RESBRS.  This is because the control file (VCCNTROL)
       is not updated if a volume is EXCLUDED.  In this way,
       if the normal span of time between scans is
       approximately 24 hours, this will be adjusted on a
       volume basis to (approximately) 48 hours if a volume
       is EXCLUDED for a day.