IEBGENER uses the following input:

• An input data set, which contains the data that is to be copied, edited, converted into a partitioned data set or PDSE, or converted into members to be merged into an existing data set. The input is either a sequential data set or a member of a partitioned data set or PDSE.
• A control data set, which contains utility control statements. The control data set is required if editing is to be performed or if the output data set is to be a partitioned data set or PDSE.
• The PARM parameter on the JCL EXEC statement or the dynamic invocation equivalent.

IEBGENER produces the following output:

• An output data set, which can be either sequential, including large format sequential, or partitioned. The output data set can be either a new data set (created during the current job step) or an existing data set. It can be a sequential data set or a PDS or PDSE that will be expanded. If a partitioned data set or PDSE is created, it is a new member with a new directory entry. None of the information is copied from the previous directory entry. The same sequential data set cannot be used as both the input and output data set. The output sequential data set cannot be any of the input data sets in a sequential concatenation.
• A message data set, which contains informational messages (for example, the contents of utility control statements) and any error messages.

Message IEC507D will be issued twice when adding data or members to an existing data set which has an unexpired expiration date. This occurs because the input and output data sets are opened twice.

Related reading :

• For information about the messages issued by the IEBGENER utility, see z/OS MVS System Messages, Vol 7 (IEB-IEE).
• For information about IEBGENER return codes, see Invoking Utility Programs from an Application Program.
• for information about the JCL EXEC statement, see EXEC Statement.