Filter
Top Products
80 Storage Management with DB2 for OS/390
8.5.2.4 Contingency Time Frame
Limit the amount of data converted at a particular time, so if problems are
experienced, the situation can be recovered or backed out.
8.5.3 SMS Implementation
The storage administrator performs the implementation of SMS, using ISMF to
update the ACS routines. However, it is normally the DB2 administrator who is
closely involved with the planning and positioning of data. An outline of activities
required are listed below:
• Definition of Data Classes
This is optional, although it is usually recommended that Data Classes be
assigned. Even though it is not saved for non SMS managed data sets, the
allocation attributes in the Data Class are used to allocate the data set.
• Definition of Storage Classes
Data sets must have a Storage Class to qualify for SMS management.
Here GUARANTEED SPACE is specified, along with availability,
performance, and accessibility characteristics.
• Definition of Management Classes
This is used for migration to level 1 and level 2 with or without backup, and
indicates if there should be no HSM management (backup or migration). It
also includes expiration of data sets and space release/compaction.
• Definition of Storage Groups
The Storage Group contains volumes that satisfy the service requirements
of the data sets allocated to them. They can handle more than one type of
data. Separate Storage Groups should be defined for production
tablespaces, active logs, other production data, and non-production data.
• Policy Documentation
The storage administrator defines policies that include:
• Data set naming conventions
• Volume naming conventions
• Restrictions on use of volumes
• The mapping of DB2 STOGROUPS with SMS Storage Groups
• Use of Data Classes
• Use of GUARANTEED SPACE parameter
• Use of Storage Classes
• Use of Management Classes
• ACS Routines
The storage administrator uses the agreed policies to implement DB2 data
under the control of SMS. This should be a documented procedure that
includes:
• Taking copies of the SMS control data set (ACDS, SCDS), and the
source of the ACS routines prior to updating, for back out purposes
• Adding the relevant code for the DB2 data to the ACS routines