Control Statements
Control Statements (for Experienced)
Summary
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
- Utility Control Statements
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 |
|
SYSUT1 or anyname1 DD |
|
SYSUT2 or anyname2 DD |
|
SYSUT3 DD |
|
SYSUT4 DD |
|
SYSIN DD |
|
Utility Control Statements -
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. |