|
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. > -----Original Message----- > From: Lisa.Abney@sensient-tech.com [SMTP:Lisa.Abney@sensient-tech.com] > Sent: Wednesday, July 18, 2001 3:16 PM > To: RPG400-L@midrange.com > Subject: Re: re. Access Groups and Threads > > > 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? > > > +--- > | 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 > +--- ************************************************************************************************************************************************************************************************************ This message originates from Lincare Holdings Inc. It contains information which maybe confidential or privileged and is intended only for the individual or entity named above. It is prohibited for anyone else to disclose, copy, distribute or use the contents of this message. All personal messages express views solely of the sender, which are not to be attributed to Lincare Holdings Inc., and may not be copied or distributed without this disclaimer. If you received this message in error, please notify us immediately at MailAdmin@lincare.com or (800) 284-2006. ************************************************************************************************************************************************************************************************************ +--- | 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 +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.