Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Defining Data Classes to Simplify Data Set Allocations z/OS DFSMS Implementing System-Managed Storage SC23-6849-00 |
|
A data class defines what the data looks like and contains attributes that correspond to parameters that can be coded on JCL DD statements, TSO ALLOCATE commands, or requests for dynamic allocation. It is a collection of allocation and space attributes used to create a data set. You define data classes for data sets that have similar attributes. When end users allocate a data set and refer to a data class, SMS allocates the data set using the attribute values of its associated data class, with the exception of override Data Class attribute. In that case, only the Data Class space attributes will be used. Figure 1, Figure 2, Figure 3 and Figure 4 show examples of the ISMF Data Class Define panel, with the attributes used to allocate an extended format, VSAM key-sequenced data set (KSDS). Related Reading: For detailed descriptions of the data class attributes listed on the Data Class Define panel, see z/OS DFSMSdfp Storage Administration. You
can use Figure 1 to define record and space
attributes.
Figure 1. Data
Class Define Panel, Page 1
You
can specify additional volume and VSAM attributes on the second panel,
shown in Figure 2.
Figure 2. Data Class Define Panel, Page 2
On this panel, you can specify the following attributes for a data
class:
Use page 4 of the ISMF Data Class Define panel, shown
in Figure 3, to further modify data classes.
Figure 3. Data Class Define
Panel, Page 4
Use page 6 of the ISMF Data Class Define panel, shown in Figure 4, to specify whether to assign attributes for VSAM record-level sharing (RLS) to system-managed data sets. You can specify whether the data set is eligible for backup-while-open processing and whether the data set is recoverable. You can specify the name of the forward recovery log stream. You can also specify the size of VSAM RLS data that is cached in the CF cache structure that is defined to DFSMS. You can also specify whether SMSVSAM is allowed to use 64-bit addressable virtual storage for its data buffers, moving them above the 2 gigabyte bar. Figure 4. Data
Class Define Panel, Page 6
You can develop data classes as you migrate permanent data to system-managed storage, or you can defer this until after most permanent data has been migrated. First, have users externally specify the keyword DATACLAS to select these data classes. Later, you can further automate by assigning them in your ACS routines. This latter level of automation requires a plan to identify specific data set types by interrogating the values of ACS variables. A simple example is the ACS variable, &LLQ, which represents the data set's low-level qualifier. Data classes can assist you in enforcing standards for data set allocation. The need to maintain MVS™ or DFSMSdfp installation exits that enforce allocation standards might be eliminated by using the data class ACS routine facilities. All keywords on the JCL DD statement, TSO ALLOCATE command, or dynamic allocation are passed to your data class ACS routine to help you determine how to allocate the data set. You can issue a warning message to your users if their allocation violates standards, such as specifying a specific volume or not using a secondary allocation request. Or, you can fail an allocation by setting a non-zero return code in your data class ACS routine. DFSMSdfp enables you to include any ACS variable in the informational messages you create. You can override a data class attribute using JCL or dynamic allocation parameters. However, overriding a subparameter of a parameter can override ALL of the subparameters for that parameter. For example, SPACE=(TRK,(1)) in JCL can cause primary, secondary, and directory quantities, as well as AVGREC and AVGUNIT, in the data class to be overridden. However, if you also specify DSNTYPE=PDS, the directory quantity is taken from the data class. If you want the data class to supply the default value of a parameter, do not specify a value for that parameter in the JCL or dynamic allocation. Users cannot override the data class attributes of dynamically allocated data sets if you use the IEFDB401 user exit. By default, SMS cannot change values that are explicitly specified because doing so would alter the original meaning and intent of the allocation. The default for the 'override space' attribute in Data Class is NO, but you can use this attribute to allow SMS to change explicitly specified values. |
Copyright IBM Corporation 1990, 2014
|