The following paragraphs briefly describe DFSMS concepts and constructs, and how DFSMS and CA Disk work together. For more information about DFSMS concepts and constructs, see the IBM manual MVS/ESA Storage Administration Reference.
The DFSMS concept as developed by IBM uses ISMF, DFP 3.x, or DFSMS x.x as a base. The items that can attach to the base includes: a security package, a data manager, a data mover, and a sort program. A main component of IBM's DFP 3.x or DFSMS x.x is the Storage Management Subsystem (SMS). All attached items interact with DFP 3.x through the SMS. CA Disk, in the role of data manager and data mover, uses a System Program Interface (SPI) to interact with SMS.
SMS invokes Automatic Class Selection (ACS) routines during the creation of new data sets. SMS uses ACS routines to assign SMS constructs to a data set at allocation time. SMS constructs work as criteria for managing the data set during its life-cycle from initial creation to final disposition. The CA Disk SPI provides a way to request SMS construct information and apply ACS rules to allow CA Disk to manage and move data sets.
The four SMS constructs and their definitions are:
A list of allocation attributes that the system uses for allocation of data sets.
A list of storage performance and availability attributes.
A list of data set archive, backup, and retention attributes that can be used to manage storage at a data set level.
A list of real DASD volumes (pool), or a list of volumes that no longer reside on a system but end-users continue to reference (dummy).
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|