SYSUT2 DD Statement

The output data set for IEBGENER, as specified in SYSUT2, can contain fixed, variable, undefined, or variable spanned records (except partitioned data sets or PDSEs, which cannot contain variable spanned records). IEBGENER can reblock records if you specify a new maximum block length on the SYSUT2 DD statement. If you are reblocking fixed-length or variable-length records, keys can be retained only if you supply an exit routine to retain them. You cannot retain keys when you reblock variable spanned records.

If the output data set is on a card punch or a printer (not a spooled data set), you must specify DCB information on the SYSUT2 DD statement.

When the data set is on DASD or tape and record format and logical record length are not specified in the JCL for the output data set, and the data class does not supply them, values for each are copied from the input data set. Logical record length is not copied if the RECFM is undefined.

Note: If you are using IEBGENER with an SMF dump data set, IEBGENER can truncate your data. The SMF dump program, IFASMFDP, creates a data set with a logical record length larger than IEBGENER allows. Thus, IEBGENER will truncate the data set to a logical record length of 32␠760, resulting in a loss of 7 bytes. If you do not have actual data in those 7 bytes, you will lose nothing in the truncation. However, care should be taken in using IEBGENER with the SMF dump program.

The output block size need not be specified, if logical record length and record format are specified or available for the input data set. The EXEC statement input data set, and output device type affect the output block size (when not specified). If the output device type is tape or dummy, the block size can exceed 32␠760 bytes. If you specify BLKSIZE, then SDB in the PARM value on the EXEC statement will have no effect.

The output logical record length must be specified when editing is to be performed and the record format is fixed blocked, variable spanned or variable blocked spanned.

A partitioned data set or PDSE cannot be produced if an input or output data set contains spanned records.

Table 1 shows the effect of the availability of RECFM, LRECL, and BLKSIZE in the SYSUT2 DD statement.

Table 1. Effect of output DD statements. "Available" means that you coded it or that the value is in the data set label or data class.
RECFM	LRECL	BLKSIZE	Result
Available	Available	Available	All are used.
Available	Available	Omitted	Block size is determined by the system.
Available	Omitted	Available	LRECL is copied from the input unless RECFM is undefined. The specified RECFM and BLKSIZE are used.
Available	Omitted	Omitted	LRECL is copied from the input unless RECFM is undefined. The BLKSIZE is copied from the input unless it is too large for the device; in that case, the system determines an optimal BLKSIZE.
Omitted	Available	Available	RECFM is copied from the input. The specified LRECL and BLKSIZE are used.
Omitted	Available	Omitted	RECFM is copied from the input. The specified LRECL is used. BLKSIZE is determined by system.
Omitted	Omitted	Available	RECFM and LRECL are copied from the input, but LRECL is not copied if RECFM is undefined.
Omitted	Omitted	Omitted	All three are copied unless BLKSIZE is too large for the device. In that case, the system determines an optimal BLKSIZE.

Related reading: For a description of SDB, see EXEC Statement.