Re: Activation groups - named vs. *NEW

Hi, Joe:

I don't believe that a *SRVPGM creates a new activation group,
but perhaps if the *SRVPGM has ACTGRP(*CALLER) and
the caller happens to have ACTGRP(*NEW), this might happen?

I recommend the use of "named" activation groups for use with
service programs; for example, say you have a *SRVPGM named
"XYZ", then you can specify ACTGRP(XYZ), and the system will
automatically create this "named" activation group the first time you
invoke this service program, and you can decide when you want to
"clean it up" with "RCLACTGRP ACTGRP(XYZ)", or it will get
cleaned up automatically at "end of job" (eg. when you sign off).

Regards,

Mark S. Waterbury

----- Original Message -----
From: "Joe Pluta" <joepluta@PlutaBrothers.com>
To: <midrange-l@midrange.com>
Sent: Sunday, September 22, 2002 8:56 AM
Subject: RE: Activation groups - named vs. *NEW


> > From: Joe Pluta
> >
> > I'd be interested to know from anybody at IBM whether this is indeed the
> > case: do server programs such as the host servers create a *NEW
> > AG for each
> > request?
>
> Along these lines, is there a unique ID associated with an AG that can be
> accessed from an API somewhere?  That way I could run my own tests to see
if
> OS/400 indeed creates a new AG for each request, as I suspect.
>
> Joe
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>