2. PLANNING › 2.4 CA MICS Considerations › 2.4.1 CA MICS Considerations (VCC)

2.4.1 CA MICS Considerations (VCC)

VCC is intended to be run once per day to collect data for
CA MICS applications. The SMF-like records written to the
ddname VCCDATA (or SMF) will be fed into the CA MICS DAILY
job, in particular, the CA MICS DAY090 step, which will
organize the VCC data into several different VCA files.
These VCA files can later be reported on with the VCA
reporting facility and SAS.  These same VCA files will also
be used as inputs to the following CA MICS Management Support
Applications:

    o CA MICS Accounting and Chargeback
    o CA MICS Capacity Planner
    o CA MICS StorageMate

Run-time parameters allow VCC to collect only volume level
statistics (DATAINFO=N) or catalog status of VTOC data sets
(CATCHECK=Y).  These runs should be distinctly different from
the normal production use of VCC.  For DATAINFO=N
applications where only one record per VOLSER is produced,
the probable audience for any reports produced from this data
is the storage administration staff, because accounting
applications are impossible without data set information.
Accordingly, it is important that you set up this type of VCC
application with VCCDATA and VCCNTROL files that are
different from the production run.  CATCHECK processing, on
the other hand, could use the same VCCDATA and VCCNTROL files
as the production use of VCC but should be scheduled
infrequently due to processing time requirements.  Chapter 3
discusses these options in greater detail.

VCC must be run well before the CA MICS DAILY job in order to
allow enough time for a rerun in case there are problems.  If
VCC data goes to SMF and VCC cannot be rerun before CA MICS
daily processing, only those data sets on volumes that were
COMPLETELY processed by VCC before the problems occurred will
be handled by CA MICS.

If the VCC SMF record number changes (the default is 198),
the CA MICS Space Analyzer Option must be made aware of this
fact at the time the change is made.  If this is not done,
VCC data will be lost.

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