Previous Topic: Pattern Masking ExamplesNext Topic: How to Code ACS Rules to Affect Tape Processing


Defining SMS Management Classes for Tape Data Sets

This section shows how you can use CA TLMS to complement System Managed Storage (SMS) in a z/OS environment. You will see how to modify SMS Automatic Class Selection (ACS) routines to define a SMS management class for TAPE files with or without a Storage Group of TAPE defined. By assigning an SMS Management Class to a tape file, CA TLMS can determine scratch subpools, assign file retention, and enforce SMS Management Class retention limits.

Note: The only requirement is that SMS must be active and the CA TLMS option, SMS, is set to YES in TLMSIPO. This implementation of SMS does not require that DFSMS 1.1 or higher be installed.

Requests to the SMS Subsystem Interface are sent by CA TLMS to obtain the definition of a Management Class and to invoke the Data Class, Storage Class and Management Class routines. A Data Class and Storage Class must be assigned to invoke the SMS Management Class ACS routine.

Once a Management Class is returned, it is stored in the VMF. The Management Class is saved in the field xxSMSMGT in the Data Set record. The Data Class and Storage Class names are not saved. The Management Class can be manually changed using UPD vvvvvv MGMTCLAS=.

SMS ACS Services are invoked:

The SMS data may be used by TRS User Exit to set retention.