RE: size of activation group

My questions:

 >> 1) Does it cause problems when I keep this COMMONAG during the job's
life with this static storage of 11 Mb and of course the ODPs for about 40
files loaded ?

The best advice I've heard from the Rochester experts in recent years has
been that the OS is now so good at optimizing virtual memory usage, that
most of the time we do more harm by worrying and fixing than if we leave it
alone.  I have never heard of AG size being an issue.  The system will deal
with it.

 >> 2) Do activation groups have a size limit ?

Not aware of one, but I guess there must be one somewhere - but I doubt I'll
ever hit it in my lifetime.

 >> 3) Are there any other problems that I do not foresee?

The usual one is that of course the files used by the SPs remain open for
the life of the job.  Only you can tell whether this is a problem.

In terms of performance, understand that there is a small performance
penalty paid on each call to the SP routines.  If they are called millions
of times there is the potential that you will use more horsepower than you
save by avoiding firing them up in *New AGs.  Of course it is spread out
over the life of the application so it has less impact on the user than the
all-at-once effect of firing up the SP.  Since I don't know what your usage
patterns are .....  The fact that *New doesn't cause you a performance
problem probably means you've got more than enough horsepower available to
not worry about it.

Net - don't sweat it unless experience indicates a problem.

Jon Paris
Partner400

www.Partner400.com
www.RPGWorld.com