Re: triggers within commit cycles

["R. Bruce Hoffman, Jr." <rbruceh@xxxxxxxxxxxxx>]

-----Original Message-----
From: Charly Jones <charly301@hotmail.com>
To: midrange-l@midrange.com <midrange-l@midrange.com>
Date: Monday, August 20, 2001 5:41 PM
Subject: Re: triggers within commit cycles


>>if your trigger executes as part of the transaction,
>>then any IO that it does can be covered by the commitment cycle.
>
>Thanks Bruce,
>
>So how do I tell the trigger program to be a part
>of the commitment cycle, or not?  Is this on the
>Add Physical File Trigger command or is it a
>compile option, or what?
>
>Thanks for your help. This is a new area for me.


no problemo...

see Pete's and Buck's answers. In addition to Pete's answer about the
activation group, you can use activation groups to isolate the IO done by
the trigger to another commit cycle and out of the triggering commit cycle.

That's the main thing that activation groups are for. Resource isolation.

===========================================================
R. Bruce Hoffman, Jr.
 -- IBM Certified Specialist - AS/400 Administrator
 -- IBM Certified Specialist - RPG IV Developer

"America is the land that fought for freedom and then
  began passing laws to get rid of it."

     - Alfred E. Neuman