Re: Trigger's and Rollback's

Pete,

In a message dated 97-06-08 00:36:11 EDT, you write:

> >> 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. 

We don't use journaling, let alone commitment control, in my present
environment.  The triggers (with the exception of some recent problems that
require a 3.1 PTF) work fine...

JMHO,

Dean Asmussen
Enterprise Systems Consulting, Inc.
Fuquay-Varina, NC  USA
E-Mail:  DAsmussen@AOL.COM

"In America, anyone can become President.  That's one of the risks you take."
-- Adlai Stephenson
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* 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   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *