RE: Subprocedure Question

On Thu, 2005-09-01 at 23:13, Scott Klement wrote:
> > If the service program runs in *CALLER, then each calling program has 
> > its own copy of the file handles and such and they should not interfere 
> > with one another.
> 
> *CALLER doesn't provide this.  *CALLER means it runs in the caller's 
> activation group -- if the callers all use the same named group, you'll 
> still have the same conflicts you would've had if the srvpgm's ran in 
> those groups.

Scott (as always) is absolutely correct, and I thought I had included
this in my message yesterday, but I was really in a hurry trying to get
out of the office.  

It takes *CALLER in conjunction with the program having its own ACTGRP
to ensure this behavior.  Personally, I don't design with one big
activation group, its always seemed to defeat the purpose to me.  For
programs that aren't called frequently, I tend to use *NEW.  For
programs that are called a lot (like CGI programs), I use named
activation groups that are the same name as the program.  For service
programs, I always use *CALLER unless I specifically wish to include
sharing behavior between programs.

Joel Cochran
http://www.rpgnext.com