Re: re. Access Groups and Threads

Hi Lisa -

>From John Taylor's post ...
>
><snip some stuff ...>
>
>>For newbies - stick with *new. You'll never get confused by AG's that
>don't
>>get reclaimed, and you won't accidentally create two applications running
>in
>>the same named AG that were not designed to do so.
>
>While I don't claim to know much at all about AG's, I have been to quite a
>few classes by quite a few different people who did seem to know a lot, and
>the rule I always heard was that, until you learn a lot more, always use
>QILE as the default activation group.  This puts everything in one group,
>rather than each job into a new group.
>
>Can someone else that uses AG's comment on what John said about using *new?

I agree with John.  I *never* use named activation groups (including not
using QILE).  All new RPG IV programs that I create use standard H-specs
from /copy members and are either *NEW or *CALLER.  I have three /copy
members for H-specs called HNEW, HCALLER, and HSRVPGM.  It should be fairly
obvious what their respective purposes are! <G>

Ken
Southern Wine and Spirits of Nevada, Inc.
Opinions expressed are my own and do not necessarily represent the views of
my employer or anyone in their right mind.

+---
| 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
+---