Hi Scott -

>Use *NEW & *CALLER.   When used correctly (which is easy to to) they yield
>the same performance as named groups.  They're more efficient on memory.
>They don't leave overrides laying around that can randomly affect other
>jobs.  They don't create the maintenance nightmare of named groups.
>They're easier to use, and a better solution.

Right on!  I've been using true ILE for a couple of years now with a bunch
of service programs and stuff.  I've yet to see a need for anything besides
*NEW and *CALLER.

The one statement you made that I would take exception to is:
>They don't leave overrides laying around that can randomly affect other
>jobs.
Overrides inside of a named activation group aren't going to affect any
other activation group, much less another job.

Ken
http://www.ke9nr.org/
Opinions expressed are my own and do not necessarily represent the views of
my employer or anyone in their right mind.



This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2026 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.