RE: re. Access Groups and Threads

[Joel Fritz <JFritz@xxxxxxxxxxxxxxxx>]

Hmm...this is getting interesting.

The way I see it, there are two types of activation groups--OPM and named.
OPM, or default, is the place where RCLRSC works.  QILE is a named
activation group as are the ones created by the *NEW option.  I kind of like
the idea of using *NEW when you want resources scoped to something like a
job stream.  It also avoids the brute force reclamation of your activation
group by someone else.

Seems to me that what John and Scott are suggesting (and I'm over
simplifying) is that the program that kicks off the process can be created
*NEW and all the ones that follow be created *CALLER.  Makes sense to me.   

In all fairness, just about the only use I make of named activation groups
is for programs that call service programs.  Things seem to work out better
that way.  I'm not sure it's a good idea to have _everything_ running in
QILE or any other single named activation group.  
   
-----Original Message-----
From: Smith, Nelson [mailto:NSmith@lincare.com]
Sent: Wednesday, July 18, 2001 1:45 PM
To: 'RPG400-L@midrange.com'
Subject: RE: re. Access Groups and Threads


For a one shot program, *NEW is not too bad.  The benefits are that it
automatically cleans up behind itself.  The drawback is the overhead of
creating the activation group.

Where you don't want to use it is in any situation where it is called
repeatedly, like in a looping batch process or on a trigger program.  The
overhead of the building-running-deleting process can kill you.

I usually use QILE as the default for programs and *CALLER for service
programs.   I use a Named activation group only where I intentionally want
to take advantage of some of it capabilities, like scoping overrides.  

Small gotcha to note: If you want to do a RCLACTGRP on a named activation
group, you need to be out of it at time you run that command, i.e. back to
the program that called the program with a named activation group. It's also
highly recommended that you don't do a RCLACTGRP *ELIGIBLE in a program
because there's no telling what you are wiping out.  I only use it during
debugging sessions.

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---