Define a relative record data set with expiration date beyond 1999: Example 10

In this example, an entry-sequenced cluster is defined specifying an expiration date beyond the year 1999, using the TO parameter.

//DEFCLU8  JOB    ...
//STEP1   EXEC   PGM=IDCAMS
//SYSPRINT DD     SYSOUT=A
//SYSIN    DD     *
     DEFINE CLUSTER -
           (NAME(EXAMPLE.RRDS1) -
           RECORDSIZE(100 100) -
           VOLUMES(VSER01) -
           TRACKS(10 5) -
           NUMBERED -
           TO(2015012) ) -
         CATALOG(USERCAT)
/*

The DEFINE CLUSTER command builds a cluster entry and a data entry to define the relative record cluster, EXAMPLE.RRDS1, in the user catalog, USERCAT. The DEFINE CLUSTER command allocates ten tracks for the cluster's use. The expiration date is set to January 12, 2015. The parameters are:

NAME specifies that the cluster's name is EXAMPLE.RRDS1.
RECORDSIZE specifies that the records are fixed-length, 100-byte records. Average and maximum record length must be equal for a fixed-length relative record data set, but not equal for a variable-length RRDS.
VOLUMES specifies that the cluster is to reside on volume VSER01.
TRACKS specifies that ten tracks are allocated for the cluster. When the cluster is extended, it is to be extended in increments of five tracks.
NUMBERED specifies that the cluster's data organization is to be relative record.
TO specifies that the retention period is set to expire January 12, 2015. Note that the year (2015) is specified as a four-digit number and concatenated with the day (012). A four-digit year must be specified when the expiration date is beyond 1999. The retention period could also have been set by using the FOR parameter, followed by the number of days the cluster is to be retained.
CATALOG specifies that the cluster is to be defined in a user catalog, USERCAT.