Substatements of MODIFY-ELEMENT for text members

These substatements make changes to text members. They are read from the statement stream until the END-MODIFY substatement is encountered.

Overview of LMSCONV substatements

Statement	Function
ADD-RECORD	Add records
END-MODIFY	End modification
REMOVE-RECORD	Remove records

Table 11: MODIFY-ELEMENT substatement for text members

Standard SDF statements are also permitted as substatements.

Only member records with lengths <= 251 are processed. Longer records will be truncated. In this case, LMSCONV issues a warning.

Definition of record identification for textual members

Record identification may be a record number or a record ID.

Record no.:

The record number indicates the relative position of the member record in relation to the beginning of the member. If the record number specified is greater than the member’s highest record number, the changes continue after the last member record, i.e. records are appended to the member.

Record ID:

The location and length of the record ID are specified by means of the INPUT-RECORD-ID operand (see the MODIFY-ELEMENT statement). This is why it is not permissible to specify a record ID in substatements except when INPUT-RECORD-ID has a value other than *NONE. If specified, a record ID must have the length declared in INPUT-RECORD-ID. Only leading zeros may be omitted. If the record ID does not occur in the input member, the changes are inserted in front of the first record with a higher record ID.

Record numbers and record IDs may be mixed within substatements. In substatements and data records, they must always be specified in ascending order.

If an error is detected in interactive mode, the correction must be terminated with END-MODIFY and then restarted. After an ADD-RECORD substatement, an *END must also be entered.