4. INSTALLATION › 4.1 Installation Overview › 4.1.3 Installation Details › 4.1.3.1 Installation Checklist for CA MICS Sites

4.1.3.1 Installation Checklist for CA MICS Sites

This checklist is ONLY for completing the installation of VCC
on a host system where CA MICS is already installed. If you
are installing VCC in a standalone environment, outside of
the CA MICS system, follow the checklist in Section 4.1.3.2.


Installation Checklist

____  1.  Copy the VCC load modules to an authorized library.

This step involves copying the VCC load modules into an
APF-authorized library.  The recommended method is this:

    o  Use VCCCOPY in sharedprefix.MICS.CNTL. This invokes
       IEBCOPY with a complete list of VCC modules.  The
       BLKSIZE of the APF-authorized library must be at least
       as large as the BLKSIZE of sharedprefix.MICS.LOAD.

Alternatively, you could do this:

    o  Use the SAS PDSCOPY facility to copy the VCC load
       modules to an authorized library.  PDSCOPY will do any
       reblocking that is necessary.  VCCCOPY contains the
       complete list of modules.

____  2.  Create the VCC run-time parameter data set.

We suggest that the VCC run-time parameters be kept in the
sharedprefix.MICS.PARMS library.  Refer to Chapter 3 for
details on VCC parameter specifications before you attempt to
create the VCC parameter data set.  The parameters specify
the DASD devices and VSAM catalogs that are to be scanned.
Other specifications include:

    o  SMF record number(s)
    o  VCC recording medium (SMF or to a data set)
    o  VCC tuning parameters
    o  Inclusion or exclusion of data sets


____  3.  Allocate the VCC operational data sets.

If the number of DASD volumes and data sets VCC will be
recording is small, you may use SMF recording.  Otherwise,
due to the speed at which VCC runs and the amount of data
generated at larger data centers, it is essential that you
record VCC data in a data set other than SMF.  This will
eliminate the problem of the SMF MAN files filling up quickly
and causing system-wide degradation due to SMF buffer
shortages.

Use sample JCL member VCCALLOC in sharedprefix.MICS.CNTL as a
model in allocating the VCC operational data sets.

See Chapter 2 of this guide, Planning, for information
regarding the amount of data generated by VCC.  This will
help you determine the correct space assignments for the
VCCDATA and VCCHSM data sets.


____  4.  Set up the VCC operational JCL.

Members VCCRUN and VCCRUNH in library sharedprefix.MICS.CNTL
contain sample VCC operational JCL.  Use these
members as models in constructing your VCC job streams.

VCC is now installed and ready to run.  Refer to Chapter 3,
Usage Guidelines, to determine the criteria for when to run
VCC and how to determine what data to collect.