Function Restrictions

When UPDATE=INPLACE is specified:

The SYSUT2 DD statement is not coded.
The PARM parameter of the EXEC statement must imply or specify MOD.
The NUMBER detail statement can be used to specify a renumbering operation.
Data statements can be used to specify replacement information only.
One CHANGE function statement and one UPDATE=INPLACE parameter are permitted per job step.
No functions other than replacement, renumbering, and header label modification (via the LABEL statement) can be specified.
Unless the entire data set is renumbered, only replaced records are listed.
System status information cannot be changed.

When REPRO is specified, the ADD statement can be used in the same job step only if both SYSUT1 and SYSUT2 are partitioned data sets or PDSEs; otherwise, unpredictable results can occur.

Within an existing logical record, the data in the field defined by the COLUMN parameter is replaced by data from a subsequent data statement, as follows:

IEBUPDTE matches a sequence number of a data statement with a sequence number of an existing logical record. In this manner, the COLUMN specification is applied to a specific logical record.
The information in the field within the data statement replaces the information in the field within the existing logical record. For example, COLUMN=40 indicates that columns 40 through 80 (assuming 80-byte logical records) of a subsequent data statement are to be used as replacement data for columns 40 through 80 of a logical record identified by a matching sequence number. (A sequence number in an existing logical record or data statement need not be within the defined field.)

The COLUMN specification applies to the entire function, with the exception of:

Logical records deleted by a subsequent DELETE detail statement.
Subsequent data statements not having a matching sequence number for an existing logical record.
Data statements containing information to be inserted in the place of a deleted logical record or records.

Table 1 shows the use of NEW, MEMBER, and NAME parameters for different input and output data set organizations.

Table 1. NEW, MEMBER and NAME parameters of the function statements
Input Data Set Organization	Output Data Set Organization	Parameter Combinations
None	Partitioned or PDSE (New)	With each ADD function statement, use NAME to assign a name for each member to be placed in the data set.
Partitioned or PDSE	Partitioned or PDSE	With an ADD function statement, use NAME to specify the name of the member to be placed in the data set defined by the SYSUT2 DD statement. If an additional name is required, an ALIAS statement can also be used. With a CHANGE, REPL, or REPRO function statement, use NAME to specify the name of the member within the data set defined by the SYSUT1 DD statement. If a different or additional name is desired for the member in the data set defined by the SYSUT2 DD statement, use an ALIAS statement also.
Partitioned or PDSE	Sequential	With any function statement, use NAME to specify the name of the member in the data set defined by the SYSUT1 DD statement. Use NEW=PS to specify the change in organization from partitioned to sequential. (The name and file sequence number, if any, assigned to the output master data set are specified in the SYSUT2 DD statement.)
Sequential	Partitioned or PDSE	With applicable function statement, use MEMBER to assign a name to the member to be placed in the data set defined by the SYSUT2 DD statement. Use NEW=PO to specify the change in organization from sequential to partitioned.