RE: Connection Pooling - Activation Groups

Nope it is not guaranteed.
For that you have to do some session ID management.
Some people use a cookie, others use a hidden field in the HTML form.
This session ID is used for "Persistent CGI". 

-Bob Cozzi
www.iSeriesTV.com
Ask your Manager to watch iSeriesTV.com


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On
Behalf Of Buck
Sent: Wednesday, September 06, 2006 10:30 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: Connection Pooling - Activation Groups

When the CGI program returns, the A/G remains in memory. 
If another CGI request comes in (from the original 
client or another one) and that same CGI job is called
upon to process this new request, then A/G and
therefore the program is already in memory, 
and starts running.

Is there a guarantee that all CGI requests will be served by the same 
job?  In other words, is it possible for OS/400 to start multiple jobs, 
and therefore have multiple AGs?

This is crucial if one intends to use the AG to store state between CGI 
requests.  It sounds like the OP is tweaking performance, in which case 
it's a moot point how many jobs OS/400 creates to service CGI requests.

   --buck