When you allocate or define a data set to use SMS, you specify your data set requirements by using a data class, a storage class, and a management class. Typically, you do not need to specify these classes because a storage administrator has set up automatic class selection (ACS) routines to determine which classes to use for a data set.
Your storage administrator defines the attributes of each class in an SMS configuration. An SMS configuration is a complete set of definitions, ACS routines, and other system information SMS uses to manage your data sets. The definitions group data sets according to common characteristics. As you allocate new data sets, the ACS routines assign those characteristics. With the information contained in the SMS configuration, SMS manages your data sets most effectively with a knowledgeable use of the available hardware. See z/OS DFSMSdfp Storage Administration for information about using SMS classes and managing data sets and volumes.
The Storage Management Subsystem (SMS) can manage tape data sets on native volumes in a tape library and on the logical volumes in a Virtual Tape Server (VTS). DFSMSrmm provides some services for the stacked volumes contained in a Virtual Tape Server. See z/OS DFSMSrmm Implementation and Customization Guide.
Table 1 lists the storage management functions and products you can use with system-managed and non-system-managed data sets. For details, see z/OS DFSMSdfp Storage Administration.
Activity Allocation | Non-System-Managed Data | System-Managed Data |
---|---|---|
Data placement | JCL, storage pools | ACS, storage groups |
Allocation control | Software user installation exits | ACS |
Allocation authorization, definition | RACF3, JCL, IDCAMS, TSO/E, DYNALLOC | RACF3, data class, JCL, IDCAMS, TSO/E, DYNALLOC |
|
|
|
Access authorization | RACF3 | RACF3 |
Read/write performance, availability | Manual placement, JCL, DFSMSdss1, DFSMShsm2 | Management and storage class |
Access method access to UNIX byte stream | JCL (PATH=) or dynamic allocation equivalent | JCL (PATH=) or dynamic allocation equivalent |
|
|
|
Backup | DFSMShsm2, DFSMSdss1, utilities | Management class |
Expiration | JCL | Management class |
Release unused space | DFSMSdss1, JCL | Management class, JCL |
Deletion | DFSMShsm2, JCL, utilities | Management class, JCL |
Migration | DFSMShsm2 | Data and management class, JCL |
Notes:
|
Direct data sets (BDAM) can be system-managed but if a program uses OPTCD=A, the program might become dependent on where the data set is on the disk. For example, the program might record the cylinder and head numbers in a data set. Such a data set should not be migrated or moved. You can specify a management class that prevents automatic migration.
Tape volumes in a system-managed tape library can be managed as system-managed storage classes.