RE: Activation group for an AFTER external database trigger...

... but may be sometime you want to use commitment control!
So you should be prepared

Mit freundlichen Grüßen / Best regards

Birgitta Hauser


"Shoot for the moon, even if you miss, you'll land among the stars." (Les Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them and keeping them!"
„Train people well enough so they can leave, treat them well enough so they don't want to.“ (Richard Branson)


-----Original Message-----
From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Robert Rogerson
Sent: Mittwoch, 4. November 2020 18:58
To: RPG programming on IBM i <rpg400-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Activation group for an AFTER external database trigger...

Thanks Alan and Birgitta, to clarify we do not use commitment control.

@Alan if *NEW is used isn't this creating a new activation group each time the trigger is fired? Isn't this adding additional overhead.
@Birgitta, If *CALLER is used then is the activation group (the activation group that *caller refers to) the activation group of the program which caused the program to fire?
For example if PGMA runs in a named activation grp (ACTGRP_A) and updates a record in the file causing the trigger to fire. IF *caller is specified for the trigger then does the trigger run in ACTGRP_A?

Thanks,

Rob

On Wed, Nov 4, 2020 at 11:50 AM Alan Campin <alan0307d@xxxxxxxxx> wrote:

That is assuming you are using Commitment Control and who on the IBM i
uses commitment control? Almost none. If I was wanting to roll back
changes, I would simply use a Before Trigger and monitor for an error
to inform the user that the update did not occur. My opinion only.

The one scenario that I have run into where *Caller was mandatory is
an update coming from an external job (A PC job). The trigger call is
from the OS and the OS is running in default activation group.


On Wed, Nov 4, 2020 at 8:33 AM Birgitta Hauser
<Hauser@xxxxxxxxxxxxxxx>
wrote:

A Trigger Program should always run in the *CALLER activation group!
Why? If you are working with commitment control, the default
commitment scope is *ACTGRP, i.e. a COMMIT and/or ROLLBACK will only
work properly within the same activation group.

Mit freundlichen Grüßen / Best regards

Birgitta Hauser


"Shoot for the moon, even if you miss, you'll land among the stars."
(Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not
training

them

and keeping them!"
„Train people well enough so they can leave, treat them well enough
so

they

don't want to.“ (Richard Branson)


-----Original Message-----
From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Robert Rogerson
Sent: Mittwoch, 4. November 2020 17:23
To: RPG programming on the IBM i (AS/400 and iSeries)
<rpg400-l@xxxxxxxxxxxxxxxxxx>
Subject: Activation group for an AFTER external database trigger...

Hi All, I've been trying find how to define the activation group on
an external (RPG) database trigger.
Should I be using ctl-opt actgrp(*new) orctl-opt actgrp(*caller)?

If anyone knows of a link to a reference that would be great too.

Thanks,

Rob
--
This is the RPG programming on IBM i (RPG400-L) mailing list To post
a message email: RPG400-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
related questions.

Help support midrange.com by shopping at amazon.com with our
affiliate
link:
https://amazon.midrange.com

--
This is the RPG programming on IBM i (RPG400-L) mailing list To post
a message email: RPG400-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
related questions.

Help support midrange.com by shopping at amazon.com with our
affiliate
link: https://amazon.midrange.com

--
This is the RPG programming on IBM i (RPG400-L) mailing list To post a
message email: RPG400-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
related questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

--
This is the RPG programming on IBM i (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com