z/OS DFSMS Using Data Sets
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Example 2: Allocate a System-Managed Key-Sequenced Data Set Using Keywords

z/OS DFSMS Using Data Sets
SC23-6855-00

The following example shows allocating a system-managed key-sequenced data set:

   //DDNAME   DD   DSNAME=KSDATA,DISP=(NEW,KEEP),
   //              DATACLAS=STANDARD,STORCLAS=FAST,
   //              MGMTCLAS=STANDARD
Explanation of Keywords:
  • DSNAME specifies the data set name.
  • DISP specifies that a new data set is to be allocated in this step and that the data set is to be kept on the volume if this step terminates normally. Because a system-managed data set is being allocated, all dispositions are valid for VSAM data sets; however, UNCATLG is ignored.
  • DATACLAS specifies a data class for the new data set. If SMS is not active, the system syntax ignores DATACLAS. SMS also ignores the DATACLAS keyword if you specify it for an existing data set, or a data set that SMS does not support.

    This keyword is optional. If you do not specify DATACLAS for the new data set and your storage administrator has provided an ACS routine, the ACS routine can select a data class for the data set.

  • STORCLAS specifies a storage class for the new data set. If SMS is not active, the system syntax ignores STORCLAS. SMS also ignores the STORCLAS keyword if you specify it for an existing data set.

    This keyword is optional. If you do not specify STORCLAS for the new data set and your storage administrator has provided an ACS routine, the ACS routine can select a storage class for the data set.

  • MGMTCLAS specifies a management class for the new data set. If SMS is not active, the system syntax ignores MGMTCLAS. SMS also ignores the MGMTCLAS keyword if you specify it for an existing data set.

    This keyword is optional. If you do not specify MGMTCLAS for the new data set and your storage administrator has provided an ACS routine, the ACS routine can select a management class for the data set.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014