Triggers and commitment control

["J Michael Smith" <Michael.Smith3@xxxxxxxx>]

This is a multi-part message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
Below is an excert from the archives.

A proposed trigger program will send a transaction to a non-AS400 system(the 
goal is to keep two databases in sync).

I am looking for help in designing a methodology that will allow me to 
"recover" the transaction send to the non-AS400 system if a ROLLBACK occurs?

Any ideas would be appreciated.

Michael Smith

At 14:05 09/02/98 -0500, Bradley V. Stone wrote:

>Quick question.

>If I'm using commitment control on a file that has a trigger attached to

>it on the *ADD *AFTER option, when does the trigger fire? On the WRITE

>or on the COMMIT? If I Rollback, is the trigger fired?

Brad,

It fires on the WRITE. IBM recommends that commitment control for files updated

by a trigger should be the same as the file to which the trigger is attached.

When the job executes a commit, the trigger's changes are committed also. BTW,

they also recommend that commit and rollback never be performed by the trigger

itself.

Pete Hall