2. PLANNING › 2.4 CA MICS Considerations › 2.4.2 CA MICS Considerations (VCC-DFHSM)

2.4.2 CA MICS Considerations (VCC-DFHSM)

The "production" run of VCC that collects data for primary
DASD from VTOCs and catalogs can be extended to collect data
for inactive data sets and backup versions through use of the
DFHSM Inventory part of the CA MICS Space Analyzer Option.
This provides a VCC collection module to obtain information
about objects under the direct control of DFHSM.

The SMF-like records emanating from the VCC-DFHSM interface
are written to either ddname VCCHSM (or SMF) and will be fed
into the CA MICS DAILY job, in particular, the DAY095 step
that will organize the VCC-DFHSM data into several different
DFHSM files.  These DFHSM files can later be reported on with
the user-written SAS programs, or MICF.  These same DFHSM
files will also be used as inputs to these CA MICS Management
Support Applications:

    o CA MICS Accounting and Chargeback
    o CA MICS StorageMate

Run-time parameters allow VCC to collect only HSM data (HSM=Y
with VTOCSUBT=0) or everything in the same run.  The
important consideration in a shared-DASD environment is to
collect DFHSM data only once per day from only one SYSID.
See the IBM publication SH35-0084-4 or above, DFHSM
Installation and Customization Guide, for information about
DFHSM operation in a shared-DASD environment.  Chapter 3 of
this guide discusses each HSM-related option in greater
detail.

The DFHSM data created by VCC must be created before the
CA MICS DAILY run in order to allow enough time for a rerun
in case there are problems.  If the DFHSM data goes to SMF
and VCC cannot be rerun before CA MICS daily processing, this
batch of HSM data would be treated as an incomplete
inventory.

If the VCC SMF record number for DFHSM data changes (the
default is 197), VCA must be made aware of this fact at the
time the change is made.  If this is not done, VCC-DFHSM data
will be lost.

To inform CA MICS about a change in the VCC SMF record number
for DFHSM (even if you log records to the VCCHSM file and not
to the SYS1.MANx structures), you must change the INPUTSOURCE
value in sharedprefix.MICS.GENLIB(HSMGENIN) and run HSMCGEN.