MIMIX supports database trigger replication using one of the following ways:
-
Using IBM i trigger support to prevent the triggers from firing on the target system and replicating the trigger-induced modifications. This is the behavior for new data groups created with shipped default values for the Create Data Group Definition (CRTDGDFN) command.
-
Ignoring trigger-induced modifications found in the replication stream and allowing the triggers to fire on the target system.
User journal replication processes determine which method to use from the following elements of the file entry options (FEOPT) parameter specified in the data group definition and data group file entries.
-
Disable triggers during apply
-
Process trigger entries
On the Create Data Group Definition (CRTDGDFN) command, both elements have the shipped default value of *YES, which prevents triggers from firing on the target system and replicates the journal entries for trigger-induced modifications.
In data groups that use multithreaded database apply processing, both trigger elements of the FEOPT parameter in the data group require the value *YES, and both elements of the FEOPT parameter in data group file entries require the value *DGDFT. A conversion to single-threaded apply processing is required to change these values.
In data groups that use single-threaded database apply processing, you can change the values of the trigger elements in the data group using the Change Data Group Definition (CHGDGDFN) command. If you already have a trigger solution in place you can continue to use that implementation or you can use the MIMIX trigger support. You can also specify values for these elements of the FEOPT parameter on a data group file entry to enable trigger processing for a specific file. Values specified for this parameter in the file entry will override the values for the data group.