2. PLANNING › 2.4 CA MICS Considerations › 2.4.3 CA MICS Considerations (VCC-HFS)

2.4.3 CA MICS Considerations (VCC-HFS)

The CA MICS Space Collector Option (VCC) can collect
directory and file information for file systems that reside
on z/OS.

If collection of USS file systems information is desired, a
separate sample job VCCRUNH is provided in
sharedprefix.MICS.CNTL data set.

This batch job can run simultaneously with the standard
VCCRUN job.  The records produced for the file systems follow
the standards for creating SMF records and can be written to
the ddname VCCDATA.  This information can be fed into the CA
MICS DAILY job by concatenating it to the VCCDATA generated
by the standard VCCRUN job, if SMF recording is not
specified.  If this is not done, VCC HFS scan data will be
lost.

The VCC SMF record number for HFS data must match the SMF
record number specified for non-VSAM and VSAM VCC data.  If
the VCC SMF record number for HFS, VSAM and non-VSAM data
changes (the default is 198), VCA must be made aware of this
change.  If this is not done,
VCC-HFS data will be lost.

To implement a change to the VCC SMF record number for HFS
(even if you do not specify SMF recording), perform the
following steps:

    1. Edit sharedprefix.MICS.GENLIB(VCAGENIN)

    2. Add or modify the SMF record number in the
       INPUTSOURCE statement

    3. Submit sharedprefix.MICS.CNTL(VCACGEN).

Once processed by the CA MICS Space Analyzer Option, the
information about file systems can be used in the following
CA MICS Management Support Applications:

    o CA MICS Accounting and Chargeback Option (Not
      Recommended)

    o CA MICS StorageMate Option

Runtime parameters allow for the reduction of the information
provided for the file systems.  Specific file systems or
volumes may be excluded from data collection.

Because file systems are logically unavailable to VCC if they
are not mounted on any z/OS system, VCC should run on z/OS
images where mounted.