To
prepare for and implement a storage management policy, you perform
these steps:
- Prepare
for SMS, as described in Preparing for the Storage Management Subsystem.
This includes:
- Allocating control data sets, which contains information used
by SMS.
- Defining SMS as trusted to RACF, which generally allows the SMS
address space to bypass RACF authorization checking and to successfully
access the SMS configuration data sets. For more information, refer
to Defining SMS as trusted to RACF.
- Modifying and creating SYS1.PARMLIB members to identify SMS to
all the systems in the SMS complex. These new members take effect
when you IPL.
- Establishing
access to the ISMF Primary Option Menu for Storage Administrators,
which is shown in Figure 1. This
is the final preparation step.
- Define the base configuration, which identifies the systems within
the SMS complex. See Creating the base configuration.
- Define the
SMS classes and storage groups that you want SMS to assign to your
data sets and objects, and the data sets that you want to assign to
your aggregate groups. See Defining storage groups, Defining management classes, Defining storage classes, Defining storage classes, Defining aggregate groups and Defining aggregate groups. Define optical libraries and drives
and tape libraries, if you have them. See z/OS DFSMS OAM Planning, Installation, and Storage Administration Guide for Object Support and z/OS DFSMS OAM Planning, Installation, and Storage Administration Guide for Tape Libraries.
- Define ACS routines to assign the SMS classes and storage groups.
Then test the routines. See Defining ACS routines.
- Validate the ACS routines individually to check for errors. You
should then validate the entire SMS configuration to check for errors
that exist among its related parts.
- Activate the valid SMS configuration. See Activating Storage Management Subsystem configurations.