Cache Management › Static Cache Management › Setting up Static Cache Management › SMS Managed Cache

SMS Managed Cache

For a SMS-managed cache, you must define a SMS storage class and storage group containing the appropriate number of DASD volumes you calculated in the section Determining the Number of Static Cache DASD Volumes. The storage class name is used during the customization process to generate the appropriate IDCAMS DEFINE statements to create the static cache LDSs. These LDSs will have a cluster name of PREFIX.VVE.LDSnnnnn and a data component name of PREFIX.VVE.LDSnnnnn.DATA where nnnnn is a number between 00001 and 65535.

The sample ACS routine changes all assume the following:

• The CA Vtape DSN prefix defined during customization is the default value of CAVTAPE1.
• The storage class defined for use by CA Vtape is SCVTAPE.
• The storage group defined for use by CA Vtape is SGVTAPE.

The following sample shows a storage class ACS change based on the previous assumptions:

IF &DSN = CAVTAPE1.VVE.LDS* THEN DO
     SET &STORCLAS = 'SCVTAPE'         
     EXIT CODE(0)
     END 

The following sample shows a storage group ACS change based on the previous assumptions:

IF &STORCLAS = 'SCVTAPE' THEN DO
     SET &STORGRP = 'SGVTAPE'         
     EXIT CODE(0)
     END 

When using SMS to manage the allocation of the static cache LDSs, a management class that backs up or migrates the cache LDSs should not be assigned to the allocations. These LDSs need to remain on DASD where CA Vtape can access them immediately. Migrating them will cause virtual mount delays.

Alternately, a do nothing management class can be defined and assigned to the LDSs. A do nothing management class would be one that has EXPIRE AFTER DAYS NON-USAGE set to NOLIMIT, EXPIRE AFTER DATE/DAYS set to NOLIMIT, CMD/AUTO MIGRATE set to NONE, ADM/USER BACKUP set to NONE, and AUTO BACKUP set to NO.