Re: Default activation groups

Ah ... When you use DFTACTGRP(*YES) - the worst named option in the history of the platform - you are basically saying "please build this as an OPM program - or at least one that pretends to be OPM".

As a result there should basically be no issues with anything. All scoping etc. should be the same as if you had coded the new stuff as an OPM program.

On Feb 22, 2021, at 5:26 PM, 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