DSNB Data Control Statement

Utilities › TMSAGGR Utility—Maintain Data Set Name Blocks › Control Statement Specification › DSNB Data Control Statement

DSNB Data Control Statement

DSNB data control statements generate DSNBs for secondary files on a volume. No DSNBs can currently be associated with the volume. For example, if you need to provide DSNB information for File 5, and the Volume record currently references the DSNBs associated with files 2 through 4, these DSNBs must be purged with TMSAGGR and the entire chain rebuilt.

DSNB data control statements must follow the VOL control statement and must be in file sequence order beginning with the DSNB data for File 2. For multivolume, multi-data set tape aggregates, all associated DSNB data control statements must follow one single VOL control statement. Keyword F1STVSN may be used to define the structure of the aggregate if not all data sets begin on the same volume. The DSNBs must be chained to the volume specified on the VOL control statement or to subsequent volumes of the chain. If F1STVSN is not used, all generated DSNBs are chained to the volume from the VOL control statement.

The requirements and restrictions for a DSNB data control statement are:

A DSNB data control statement can consist of several keywords. The first keyword should begin in position 1.
Continuation of a DSNB data control statement is indicated by placing a nonblank character in position 72, or if the SCAN=xx parameter was specified, xx indicates the position for a continuation character. Keywords placed on continued lines should begin in position 16 and not exceed position 71, or xx-1.
A keyword and its value (keyword=value) must not span two control statements.
All data entered to construct a DSNB must be in one control statement. Continuations must be used until all required data for a DSNB is present in the control statement.
Each DSNB data control statement must contain a data set name and an expiration date.
Each DSNB keyword can be used only once per DSNB data control statement.
HEXZEROS is not supported as a symbolic value to direct that a field be set to hexadecimal zeros.

The format for the DSNB data control statement is:

   1                16                                              72

keyword=value,keyword=value                                         *
              keyword=value

Control Statement Definition

The following keywords can be specified:

DSN or D

Is the data set name to be associated with the DSNB. Each DSNB data control statement must contain the DSN keyword. Data set names that contain special characters must be properly delimited. This keyword is required for each DSNB data control statement.

For example, a data set name of BACKUP.#WKLY must be enclosed by characters whose EBCDIC numeric value is less than the numeric value of the character A (+,!,*,%,?,#,@,",=), such as DSN='BACKUP.#WKLY' or DSN=*BACKUP.#WKLY*

EXPDT or E

Specifies the data set expiration date. Value is a 10-character field in preferred date format or Julian date format (yyyy/ddd). Expiration date types should not be mixed on a tape volume. CA 1 expiration date keywords should not be mixed with Julian dates or other CA 1 expiration date keywords. If more than one type of expiration date is found in a volume, a warning message is issued if MIXEXP is set to WARNING (the default) in the TMOOPTxx member of hlq.CTAPOPTN. This keyword is required for each DSNB data control statement.

Important! CA 1 controls the expiration of tapes based on the EXPDT for File 1. When adding DSNBs to a volume, keep in mind that if a numerically higher EXPDT value is used for a DSNB, the Volume record for File 1 is updated with this higher value.

CJOB or J

Is used to enter the creating job name into the DSNB. If omitted, the job name for the TMSAGGR execution is used.

CSTEP

Is used to enter the creating step name into the DSNB. If omitted, TMSAGGR is used as the default value.

CDATE or C

Specifies the date of data set creation in preferred date format or Julian date format. If omitted, the date of the current execution is used as the default value.

CPGM

Used to enter the creating program into the DSNB. If omitted, the field is left blank.

CTIME

Is used to enter the data set creation time into the DSNB. This field is a four-position numeric field in the form hhmm. If omitted, the current execution time is used as the default value.

BLKSIZE

Specifies the data set block size in the DSNB. This field, if used, must contain from one to five digits. If omitted, zero is assigned.

BLKCNT

Specifies the number of record blocks in the data set. Value must be a numeric field from one to six digits. If omitted, zero is the default.

LRECL

Specifies the data set logical record length in the DSNB. If this keyword is used, value must be a numeric field from one to five digits. The default value is zero.

RECFM

Specifies the data set record format in the DSNB. Value is a field which contains two hexadecimal characters. The default value is 00.

F1STVSN

Can be used for multivolume, multi-data set aggregates and specifies the volume where the data set begins. Value must be a valid VOLSER out of the multivolume chain. The F1STVSN values of all DSNBs must be in volume sequence order, beginning with the volume specified on the VOL control statement or a subsequent volume of the chain.

If omitted, the default value is the F1STVSN value of the previous DSNB. For the first DSNB, the default value is the volume from the VOL control statement.

The following example shows how the DSNBs for files 2, 3 and 4 of volume 100000 are allocated to the Volume record.

1              16                                                   72

VOL 100000
DSN=TMS.PRODOTT2,EXPDT=DDMMMYYYY,C=DDMMMYYYY,                       *
               CJOB=ABCGTMC
DSN=TMS.PRODOTT3,EXPDT=DDMMMYYYY,C=DDMMMYYYY,                       *
               CJOB=ABCGTMC
DSN=TMS.PRODOTT4,EXPDT=DDMMMYYYY,C=DDMMMYYYY,                       *
               CJOB=ABCGTMC