This topic describes the conditions when trigger and application
programs are not under commitment control.
If both programs do not run under commitment control, any error in a trigger
program leaves files in the state that exists when the error occurs. No rollback
occurs.
If the trigger program does not run under commitment control and the application
program does run under commitment control, all changes from the trigger program
are committed when either:
- A commit operation is performed in the trigger program.
- The activation group ends. In the normal case, an implicit commit is performed
when the activation group ends. However, if an abnormal system failure occurs,
a rollback is performed.