MOD – Modify object

The MOD action modifies existing objects.

The MOD action allows you to modify existing objects. If MOD is specified in the H_ACT_REQ field of a row, the existing data definitions in the Output Manager database will be updated and replaced with the modified data definitions in BJTDATA. The MOD action maintains database integrity by updating all cross-table links if necessary.

All of the fields in the extract record (excluding header fields and the ROWID field) will be rewritten in the database even if some or all of them were not changed manually.

Note: When DEL or MOD action is specified, UBU uses the H_ROWID field value to identify which object must be deleted or modified. Therefore, it is strongly recommended not to change H_ROWID in the flat file, because it may cause deletion/modification of false-target object. If you are not sure that H_ROWID is kept unchanged from the time of original extract, re-extract the data and work only with new extraction.

Because the H_ROWID field is ignored for ADD operations, it can contain any value for ADD operations.

Do not use the same flat file used in an ADD operation for a MOD or DEL operation, for the H_ROWID field may change after an ADD operation.
Note: When modifying a parent selector rule, ensure that any edits made to the selection criteria of a parent selector rule are still compatible with any existing linked child subselector rules. The selection criteria of subselector rules must be derivative of the selection criteria of their parent selector rules. If you attempt to make modifications to the parent selector rule that would result in orphaning its child subselector rules, error messages will be issued and processing will terminate. The error messages will indicate the field values of the child subselector rule that are inconsistent with the selection criteria of the parent selector rule.

The format of UBU files used for MOD must be in PREP4CLON(NO).