Trigger's and Rollback's

>> I have a client that is having problems keeping 2 files in sync.
His goal is mirror of the primary file. Everything is fine until
a rollback is done. The file is journaled and under commitment control.
He's running 3.2 and his programs are OPM not ILE. <<

Kirk,

As I understand it, the main thing is that the trigger must A) be in the
same activation group as the programs that process the transaction, and
B) must have commitment control enabled for the access paths that are
updated by the trigger. The trigger's commitment status (on or off)
should match that of the job. Trigger programs should not execute a
commit or rollback. If a trigger needs to abort an update, it should
signal the application by sending an escape message, which the
application can monitor and handle. 

With RPG4, you can condition commitment control on RPG files. There's an
indicator that you can set or reset that determines if it's on or not.
As long as you're not running in a mixed environment (you're all OPM),
your trigger will always be in the same activation group as the rest of
the job, 'cause there is only one. In a mixed environment, you can
specify ACTGRP(*CALLER), which will place the ILE trigger in the correct
activation group - same as the OPM programs, but don't use CALLB, and
especially don't use service programs The program will compile, and work
fine when you test it, but will break in production because required
system support may not always be available (at least that was my
experience under V3R1 - been there, done that).

hth
Pete


--
 - Pete Hall peteh@earth.inwave.com
http://www.inwave.com/~peteh/

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *