Re: Triggers, Activation Groups, Performance

> What I would suggest for your trigger program is leaving LR off, and
> compiling it to use AG *CALLER.  That way if you do start using
> AGs (more than just QILE for everything) performance should be
> retained.


I would think that this method would be worse because
   o  Programs running in the Default Activation Group would cause your
       ILE program to load in that AG.
   o  You could potentially have several instances of the trigger program
       loaded (PAG portion of the program).
   o  The trigger program is actually part of your database implementation,
       therefore it is not part of your application.

I have not really seen any reason to use multiple AGs. Very few people
actually use many different options, so they are the only ones who need
to "cleanup" their AGs. Most people use a relatively small number of
programs, but they do "go in" and "leave" those programs many times
throughout the day. Their performance is actually improved due to the
AG being left intact. On the other hand, I see multiple AGs as another
thing to manage. The last two clients that I've been at are very similar
in this aspect. The next client may be different and operate better under
multiple AGs. I don't see this as a "one size fits all" concept.

I have used *NEW in the past because I had a process that needed to
be isolated that used commitment control. Coding the CL as *NEW
and the RPGs as *CALLER worked great.

Joe Teff


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---