7. PARAMETERS › 7.2 VTS Component Parameters › 7.2.3 VTS Component Unit Level Parameters › 7.2.3.3 VTS Peer-to-peer Libraries (VTSCMPID)

7.2.3.3 VTS Peer-to-peer Libraries (VTSCMPID)

This section is applicable for sites that have IBM VTS
peer-to-peer systems.  It explains how to populate
prefix.MICS.PARMS(VTSCMPID) and how to use the VTSUTIL
utility job to assist in updating VTSCMPID.

If you use any IBM composite peer-to-peer VTS libraries, you
must explicitly define the relationship between each
composite library and the corresponding UI and secondary
distributed VTS libraries.

o A utility job, prefix.MICS.CNTL(VTSUTIL) is provided that
  processes SMF type 94 records, determines the
  composite/UI/secondary library relationships, and updates a
  temporary member: prefix.MICS.PARMS(VTSTMPID).

o The CA MICS administrator reviews VTSTMPID, and can copy
  the composite/UI/secondary library ID values to the working
  member: prefix.MICS.PARMS(VTSCMPID).

o After updating prefix.MICS.PARMS(VTSCMPID), the component
  generation job, prefix.MICS.PARMS(VTSPGEN) must be executed
  to create the SAS FORMATS used during daily update
  processing to update data elements related to peer-to-peer
  VTS associations.

By default, the VTS Component DAY096 daily update step will
abend if an IBM composite, UI, or secondary library is
encountered in the raw data that is not listed in the
VTSCMPID member.  Alternatively, if an UNKNOWNVTSID REJECT
statement is specified in prefix.MICS.PARMS(VTSOPS), data
from unknown IBM VTS composite/UI/secondary libraries will be
rejected rather than forcing an abend.

Units that only process StorageTek data or only process data
from IBM standalone distributed VTS libraries can execute
without updating the sample VTSCMPID member found in
prefix.MICS.PARMS.  It is not necessary to execute the
VTSUTIL utility job if IBM peer-to-peer composite VTS
libraries are not used at your site.

The following sections describe how to use the VTSUTIL
utility job and how to customize the VTSCMPID member.

   1 - Executing the VTSUTIL Utility Job
   2 - Customizing the VTSCMPID Member