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

>>
>> What do you mean by "run out of memory"?  Wouldn't all resources allocated
>> by the program be released, and the *new activation group be deleted, when
>> the CGI program ended?
>>
>> Nathan M. Andelin
>> www.relational-data.com
>>
>
>I looked it up and apparently I'm wrong.  It was so long ago that I can't be
>sure of the reason for using named (as opposed to *new) activation groups
>but I thought it was that the system wasn't releasing resources.

If program A calls program B where B is compiled with activation group *new,
then when program B ends, the activation group B was running in ends.  If
program B is in a named activation group, when program B ends the activation
group remains open until it is ended by one of three ways: 1) the job ends
2)You reclaim the activation group using RCLACTGRP or 3) use CEETREC API to
reclaim activation group.

The benefit of using *new is that activation groups are cleaned up
automatically when programs end.  The advantage of using named activation
groups is the activation group remains open while you job is running along
with all the resources within it.  This can be a real advantage in
performance if the program gets called multiple times within the job.
There are advantages to using names activation groups such as sharing
open data paths.

Seth Shields
Julius Blum Inc.