If members being repaired have unique keys, active triggers, or constraints, special care should be taken. An updated or insert repair action that results in one or more duplicate key exceptions automatically results in the deletion of records with duplicate keys.
If triggers are enabled, any compare or repair action causes the applicable trigger to be invoked. Triggers should be disabled if this action is not desired by the user. When a compare is specified, read triggers are invoked as records are read. If repair action is specified, update, insert, and delete triggers are invoked as records are repaired.
Table 69 describes the interaction of triggers with CMPFILDTA repair and active processing.
Attention: If an attempt is made to use one of the unsupported situations listed in Table 69, the job that invokes the trigger will end abruptly. You will see a CEE0200 information message in the job log shortly before the job ends. You may also see an MCH2004 message. |
Trigger type |
Trigger activation group (ACTGRP) |
CMPFILDTA - Repair on system (REPAIR) |
CMPFILDTA - Process while active (ACTIVE) |
CMPFILDTA support |
---|---|---|---|---|
Read |
*NEW |
Any value |
Any value |
Not supported |
Read |
NAMED or *CALLER |
Any value |
Any value |
Supported |
Update, insert, and delete |
*NEW |
*NONE |
Any value |
Supported |
Update, insert, and delete |
*NEW |
Any value other than *NONE |
*NO |
Not supported |
Update, insert, and delete |
*NEW |
Any value other than *NONE |
*YES |
Supported |
Update, insert, and delete |
NAMED or *CALLER |
Any value |
Any value |
Supported |