RE: Activation groups for beginners

Not having used commitment control, I am not familiar with those issues.  I
did originally use *CALLER and ran into problems with triggers being fired
from OPM programs.  Usually the error messages were completely non-sensical,
but throwing up a clear dividing wall (a named activation group) seemed to
always fix the problem.  Perhaps that was the sledge-hammer method of fix
(kinda like rebooting...).

So, I guess it just depends on your environment....that's what's good about
these discussions. Finding out how things function in other environments.

> -----Original Message-----
> From: John Taylor [SMTP:jtaylor@rpg2java.com]
> Sent: Wednesday, March 06, 2002 10:35 AM
> To:   rpg400-l@midrange.com
> Subject:      Re: Activation groups for beginners
>
> Nelson,
>
> It's specifically the behaviour of the trigger within a commitment control
> environment that made me question your decision. With the trigger running
> in
> a separate NAG, you're forced to use a *JOB level commitment scope -
> something that may be undesirable from the perspective of the overall
> application. At the very least, it forces the programmer to remember to
> change the commitment definition scope on every STRCMTCTL statement (the
> default is *ACTGRP).
>
> Without a compelling reason to use a NAG, I would recommend that triggers
> be
> compiled to run in *CALLER.
>
>
> Regards,
>
> John Taylor
>
> ----- Original Message -----
> From: "Smith, Nelson" <NSmith@lincare.com>
> To: <rpg400-l@midrange.com>
> Sent: Wednesday, March 06, 2002 8:19 AM
> Subject: RE: Activation groups for beginners
>
>
> > Just ease of recognition.  Could just as easily have been QILE.
> >
> > The important point is that it is a separate named activation group.
> You
> > definitely would not want to use *NEW here due to the overhead of
> building
> > and destroying the activation group on EACH record that is triggered.
> > *CALLER may get flaky if the triggering program is OPM, although I'm not
> > real clear on the implications when Data Management gets in between the
> the
> > triggering program and the trigger.  The stack listings I've looked at
> would
> > seem to indicate that the actual trigger calling routines from Data
> > Management run in *dftactgrp (although that may be just coming forward
> from
> > the triggering program, I'm not sure).
>
>
> _______________________________________________
> This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
> To post a message email: RPG400-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
> or email: RPG400-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.


************************************************************************************************************************************************************************************************************
This message originates from Lincare Holdings Inc. It contains information 
which maybe confidential or privileged and is intended only for the individual 
or entity named above.
It is prohibited for anyone else to disclose, copy, distribute or use the 
contents of this message.
All personal messages express views solely of the sender, which are not to be 
attributed to Lincare Holdings Inc., and may not be copied or distributed 
without this disclaimer.
If you received this message in error, please notify us immediately at 
MailAdmin@lincare.com or (800) 284-2006.
************************************************************************************************************************************************************************************************************