Re: Activation Groups/SQL Suggestions

Buck wrote:

The point of multiple activation groups is to allow for multiple applications to co-exist; to let the A/R point to customer 100 and let order entry point to customer 50 at the same time.

I don't know that the ILE designers would agree with this assessment. Named activation groups certainly allow this behavior, but *NEW and *CALLER do not. *NEW and *CALLER are designed for control boundaries, and it makes it much easier to percolate exceptions out of an application boundary. As you rightly pointed out it's a design decision which to use where.

Once you start moving towards "object oriented" service programs (e.g., a Customer SP that completely encapsulates all access to the customer master file) then you may find yourself wanting to use the capability of a named activation group to segregate one application from another. In that scenario the SP could hold all the data for a specific customer and would return it as needed, and it might make sense for OE to look at one customer and AR another.

Even then, though, I think the situation where for a single user each application is looking at a single, different master record is a very small percentage; most of the times those applications are all looking at the same master, or one application is looking at multiple records. In those cases, segregating by AG isn't going to be much help.

Anyway, it's something to consider during your application architecture stage.

Joe