ILE questions: activation groups, rpg-cgi, classic web server.

 > If you use the default activation group, static binding and binding
directories are not supported.  This also means CALLB and CALLP aren't
supported,

There are two problems with this statement.  First, if you specify the
DFTACTGRP *YES _compiler_ directive they are not supported.  (Darn it I wish
that compiler option had a more meaningful name like CRTFAKEOPMPGM (Create
Fake OPM Program) or something 'cos that is effectively what it does.)
While it is not a good idea, there is nothing to prevent an ILE program from
running in the default AG.  Second point - CALLP means "Call with Prototype"
and is perfectly acceptable in a DFTACTGRP(*YES) program as long as the
proto references a program (EXTPGM keyword).

 > You can also use *CALLER to use the caller's activation group, but if the
caller's activation group is the default activation group, static binding,
callp, callb, etc. won't work.

This is just not true as I mentioned above.  It is not the recommended
approach but it works just fine.

As to the use of *NEW vs. a named AG.  I tend to think of *NEW as being
useful for the menu level.  When the operator finishes with the function in
question and backs out of the menu, the resources get cleared up.  Even then
if they are going to reuse that same functional area again later in the day
I would go for a named AG and do my own clean-up.

Jon Paris
Partner400