Re: re. Access Groups and Threads

> I can see that by limiting the scope of overrides to an activation group
> can protect Exit programs from being inadvertently affected.
> I have long ago avoided overrides as a general rule, and controlled file
> access by the proper set up of library lists.  So AGs are not much
> use to me.  I also think that AGs named at compile time are very
> inflexible.  Have you or anyone actually used NAMED AGs.

I think that's a good point. I feel that it would be greatly preferable to
name AGs on the fly. On the other hand, it may be that this is an attempt to
(in some way) mimic the "package" model used in Java. Allowing for scope of
access of a coded object to be limited its package.

In this case, the concept is really to allow coders to define AGs based on a
finite set of environments we want running on our systems and then to
specify that some applications are written to run in a specific one of those
environs.

> Frank Kolmann
Chris Rehm
javadisciple@earthlink.net
If you believe that the best technology wins the
marketplace, you haven't been paying attention.


+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---