Re: ILE RPG CGI and Activation Groups

Hi Mike,

I have a CGI programs that run in a named activation group, and I don't seem to have any trouble recompiling them and getting the new version??

With a *SRVPGM I do have that problem... the old *SRVPGM keeps being used even though I've provided a new one. But, with a *PGM object, I don't seem to have this problem. It seems to pick up the changes just fine. ( Now that you mention it, this really surprises me... how could that be? But... I assure you, I've been testing my code incrementally, adding more logic, running it again, making changes, running it again, etc, and it seems to work just fine. I'm not restarting the instance! )

Of course, you might find that it makes sense to use ACTGRP(*NEW) while you're developing and testing your program, and switch it to a named actgrp for the final QA testing and deployment. That way, you WILL get a fresh copy on every call during testing....

But, for me, a named actgrp where I don't reclaim seems to pick up the changes just fine...


Mike Cunningham wrote:

Thanks Scott, from another perspective on this, if I wanted to be
able to recompile the app for some logic changes in the middle of the
day, and that app was in a named activation group and was loaded, the
new version would not be used for that activation until the HTTP
server was shutdown. Any new activation group would load the new
version. Do I have this right? The same as in the old model if LR was
left OFF on a RETURN. That user keeps using the old application
version and new users would get the new version. Difference in CGI
world being that a user is the HTTP subsystem job, which could be
servicing many many browser requests, not the browser user making the
request. And in CGI world since there are multiple CGI jobs in the
HTTP subsystem one request from "user A" could hit the old versions
of the app and the next request from "user A" could hit the new
version of the app (assuming no persistence is setup).