On Fri, Aug 1, 2008 at 10:09 AM, Jon Paris <Jon.Paris@xxxxxxxxxxxxxx> wrote:

On 1-Aug-08, at 9:09 AM, rpg400-l-request@xxxxxxxxxxxx wrote:

I believe I was told that shared activation groups was an idea that
never went anywhere - no way to set - no way to use. Unfortunately
it is displayed on DSPPGM and DSPSRVPGM, I think.

I can't recall details right now, but the notion of shared AGs was
incorporated into the original ILE design and was implemented for
system code with the notion that it might be available for user code
at a later date.

In practice IBM's own internal experiences with using them were so
disastrous that most (all?) code that used them was changed to avoid
them as quickly as possible.

my guess is there would have to be some sort of built in queuing of
calls so that only 1 job was running code and accessing statics of the
shared activation group at a time.

dont multiple threads of a job share the same activation group? If
so, the concurrency needs of multiple threads sharing the activation
group of a srvpgm are similar to those of multiple jobs also sharing
an activation group.

there is also THREAD(*SERIALIZE) that can be specified for an RPG
module. If concurrent access was a problem for jobs sharing an
activation group, would this more recent feature of RPG have solved
it?

-Steve

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].