IEBGENER Control Statements

IEBGENER - Introduction IEBGENER - GENERATE

Advertisements


IEBGENER needs job and utility control statements.

The job control statements run IEBGENER to complete the task.

The utility control statements control the functions of IEBGENER.

  • Job Control Statements
  • Utility Control Statements

Let’s discuss about each one in detail.


Job Control Statements


StatementUsage
JOB Starts the job.
EXEC Starts IEBCOPY.
SYSPRINT DD Defines a sequential data set or spool used for listing control statements and messages.
SYSUT1 or anyname1 DD Defines a PDS or unload data set for input.
The unload data set can be basic format, large format, extended format, compressed format or tape.
PDS or Unload data set reside on DASD or tape or any other device supported by the QSAM access method.
SYSUT2 or anyname2 DD Defines a PDS or unload data set for output.
The unload data set is a sequential data set that was created as the result of an unload operation.
PDS or Unload data set reside on DASD or tape or any other device supported by the QSAM access method.
SYSUT3 DD Defines a temp data set.
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.
SYSUT4 is used when there is no space in virtual storage for the output data set directory.
SYSIN DD Defines the optional control data set.

Utility Control Statements


Any utility output generation is controlled by its corresponding control statements.

IEBGENER also has its own control statements.

If no utility control statements are included, the entire input data set will be copied sequentially.

If providing exit routines, an EXITS statement is required.

A continuation line must start in columns 4 to 16.

A nonblank continuation line in column 72 is optional.

IEBGENER - Introduction IEBGENER - GENERATE

Advertisements