Valid for
Replicat
Description
Use TMFEXCEPTIONS when the application performs multiple operations on the same record within the same transaction. Certain application scenarios can cause out-of-order records in the TMF audit trail within a given transaction:
An insert on a record can occur in the audit trail before a delete on the same primary key, even though the application performed the delete first, followed by the insert (resulting in a duplicate record condition when the insert is performed)
An update can occur in the audit trail before the insert on the same primary key (resulting in a missing record error when the update is performed)
TMFEXCEPTIONS resolves these conditions.
In the event of a duplicate insert, TMFEXCEPTIONS saves the duplicated insert until the end of the transaction. If a delete with the same primary key is subsequently encountered, the delete is performed, then the saved insert is performed.
In the event of a missing update record, TMFEXCEPTIONS saves the missing update until the end of the transaction. If an insert with the same primary key is subsequently encountered, the insert is performed, then the saved update is performed.
Use NOTMFEXCEPTIONS to turn off the exception processing.
TMFEXCEPTIONS cannot be used with INSERTMISSINGUPDATES.
Default
NOTMFEXCEPTIONS
Syntax
TMFEXCEPTIONS | NOTMFEXCEPTIONS
Example
This example turns on TMFEXCEPTIONS for ORDERS but toggles it off for any MAP statements that are defined later.
TMFEXCEPTIONS MAP $DATA1.SQLDAT.ORDERS, TARGET $DATA1.MASTER.ORDERS; NOTMFEXCEPTIONS