4. INSTALLATION › 4.1 Installation Overview › 4.1.1 Distribution Materials › 4.1.1.1 Installation Checklist

4.1.1.1 Installation Checklist

This checklist is ONLY for completing the installation of VCC
on a host system where CA MICS is already installed.

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.  This can be done using one of the
following methods:

    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.

    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.

       IMPORTANT:  If you create your own link-edit to move
       the VCC load modules, you must remember to make sure
       that these modules are:

              1.  Link-edited with the RENT,REUS attributes.
                  If the VCCGWA and VCCGWB modules are being
                  link-edited, then they must be done so
                  without the RENT,REUS attributes.

              2.  Link-edited specifying SETCODE AC(1) for
                  VCC module VCCNTRL.

              3.  Link-edited specifying SETCODE AC(1) for
                  VCC module VCCMAIN.

____  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 specification 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 sites, it is essential that you record
VCC data in a data set other than SMF.  This will eliminate
the problem of the z/OS SMF data sets filling up quickly and
causing system-wide degradation due to SMF buffer shortages.

Use member VCCALLOC in sharedprefix.MICS.CNTL to allocate the
VCC operational data sets.

VCC requires the VCCHSM data set only if HSM=Y is coded in
VCC.PARMS.  If you are writing HSM data directly to the
VCCHSM data set, you should allocate a large data set as
shown in the example below.  If you are using SMF as the
recording source for HSM data, the file will be used as a
work file and you need to allocate only a few tracks. If the
data set is omitted, VCC will not process HSM data and issue
a return code 8 for this step.

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


____  4.  Set up the VCC operational JCL.

Members VCCRUN and VCCRUNH in library sharedprefix.MICS.CNTL
contain sample VCC operational JCL.  Use this JCL as a model
for 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.