Triggers can execute distributed transactions under the control of Adabas Transaction Manager. Refer to the documentation for the Adabas System Coordinator to find out how to configure the System Coordinator for a trigger environment.

If your application causes participating triggers to be fired, and you require a distributed transaction to include changes made by both the application program and the participating trigger, you must ensure that the very first change command (store, delete or update) of the distributed transaction is issued by the application program, not by the trigger. This is necessary because the originating client must be the root of the distributed transaction, not the transient proxy trigger.