Control Statements ^{(for Experienced)}

For basic information, go through the Control Statements (for Beginners)

IEBGENER utility has two types of statements to perform the task, and those are -

Job Control Statements -

The job control statements are required to run IEBGENER to complete the task. Those are -

Statement	Usage
JOB	Starts JOB execution.
EXEC	Starts executing the IEBGENER utility.
SYSPRINT DD	The mandatory data set and should code with IEBGENER. Used for listing control statements and messages. The target can be a sequential data set or spool.
SYSUT1 or anyname1 DD	The mandatory data set and should code with IEBGENER. Defines a PDS or unload data set for input. The unload data set can be basic, large, extended, compressed, or tape. PDS or Unload data set resides on DASD, tape, or any other device supported by the QSAM access method.
SYSUT2 or anyname2 DD	The mandatory data set and should code with IEBGENER. Defines a PDS or unload data set for output. The unload data set is a sequential data set created as the result of an unload operation. PDS or Unload data set resides on DASD, tape, or any other device supported by the QSAM access method.
SYSUT3 DD	Defines a temp data set and is optional. SYSUT3 is used when there is no space in virtual storage for some or all of the current input data set directory entries.
SYSUT4 DD	Defines a temp data set and is optional. SYSUT4 is used when there is no space in virtual storage for the output data set directory.
SYSIN DD	The mandatory control data set and control statements in it are optional. This is where we can code all the utility control statements. If no control statements adding, use SYSIN DD DUMMY.

Any utility output creation is controlled by its corresponding control statements. IEBGENER also has its own control statements.

The utility control statements control the functions of IEBGENER.

Notes -

If no utility control statements are included, the entire input data set gets copied sequentially.
A continuation line must start in columns 4 to 16.
A nonblank continuation line in column 72 is optional.

The IEBGENER utility control statements are -

Statement	Usage
GENERATE	The GENERATE statement should appear as the first statement in IEBGENER utility statements.
EXITS	The EXITS statement is used to identify exit routines IEBGENER to use.
LABELS	The LABELS statement is used to decide whether the labels are to copied or not to the output data set.
MEMBER	MEMBER statement specifies the member name or member alias of a PDS or PDSE that is to be created for storing output.
RECORD	The RECORD statement defines a record group to supply editing information.