Be careful when running trigger programs in another activation group than the program that fired the trigger!
Why? If you are working under commitment control, the default commitment scope in the STRCMTCTL command is *ACTGRP! In this way if an error occurs and you want to do a rollback, the rollback works only in the same activation group!
In this way Trigger Programs should always be generated with Activation Group *CALLER.
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: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Mark Waterbury
Sent: Dienstag, 23. Februar 2021 05:26
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Default activation groups
Alan,
I suggest that for a trigger that may be fired from OPM or ILE (*CALLER or named) AGs, you may want to create the trigger program in its own named activation group -- you can just make the ACTGRP(name) equal to the name of the trigger program.
That way, the first time the trigger "fires" (gets invoked), the system will automatically create the new named AG, and it will hang around until "end of job."
Hope that helps,
Mark S. Waterbury
On Monday, February 22, 2021, 5:26:58 PM EST, Alan Cassidy <cfuture@xxxxxxxxxxx> wrote:
I should have asked this question more clearly, specifically.
Given an OPM-RPG program A, is there a gotcha with calling program B compiled with DFTACTGRP(*YES)? I need to capture changes to a certain file for certain values and instead of modifying old RPG3 code I'd like to call an RPGLE program to handle something like a data queue pipe to another process that checks for changes and sends an email.
Thing is I need to catch changes to two values in a file, and I'm looking at triggers because records get updated, deleted, and/or inserted by about 15 programs, They run in the gamut of AG'S: OPM-RPG, RPGLE-*DFTACTGRP, *CALLER, *NEW, and QILE. (these programs will be part of a comprehensive modernization strategy they are planning that includes the activation group issues.)
there is time pressure to clear a backed-up queue of requests. But I don't want any gotchas of course.
aec
On 2/21/2021 1:44 PM, Jon Paris wrote:
We covered this topic (and related issues) in 2004 in an article
called "The Seven Deadly Sins of ILE" - you can find it
herehttps://authory.com/JonParisAndSusanGantner/The-Seven-Deadly-Sins-
of-ILE
<https://authory.com/JonParisAndSusanGantner/The-Seven-Deadly-Sins-of-
ILE>
Jon Paris
On Feb 21, 2021, at 12:10 PM, Alan Cassidy<cfuture@xxxxxxxxxxx> wrote:
Can somebody share the differences between the two different activation groups?
Specifically, is there any gotchas if one OPM program A called an RPGLE program B compiled with DFTACTGRP(*YES) ?
aec
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing list To post a message email:MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:https://lists.midrange.com/mailman/listinfo/midrange-l
or email:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
athttps://archive.midrange.com/midrange-l.
Please contactsupport@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 Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-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 Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-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
midrange.com
