× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



>From the web stuff I've been doing, I adopted the following standard;

Named activation groups ALWAYS - never *NEW - according to the little
chart made by IBM about performance & the HTTP server, named activation
groups were 30% faster then *NEW activation groups.

Andrew Borts / Webmaster
Seta Corporation
6400 East Rogers Circle
Boca Raton, FL 33499

E-mail: Andrewb@setacorporation.com
Corporate web site http://www.setacorporation.com
E-Commerce web site http://www.palmbeachjewelry.com
                              http://www.myfreeitems.com
Voice: 561-994-2660 Ext. 2211 / Fax: 561-997-0774

-----Original Message-----
From: Joe Pluta [mailto:joepluta@PlutaBrothers.com]
Sent: Friday, December 28, 2001 5:45 PM
To: rpg400-l@midrange.com
Subject: RE: RPG ILE and *INLR

> From: Chris Rehm
>
> Yeah, in that light it becomes predictable, and really expected
> behavior. The addition of the PAG in between caller/callee is a fun
new
> twist. It is a great thing, though. *CALLER PAG gives faster
performance
> but you better know what you're doing. It is just another layer of the
> RETRN or LR question.

What happens is that I don't have to worry about regstering all my
subprocedures and then manually shutting them down, provided I am
willing to
deal with activation boundaries.  In my case, the reason for not setting
on
LR was performance, and at shutdown I didn't do anything, so I really am
best off using a *NEW activation group.  I never thought I would use
*NEW,
but it makes sense to me now.

If I break my job up into discrete work units, then each work unit is a
main
program with activation group *NEW.  My job stream is a series of calls
to
those work units.  Once each work unit is finished, all the
subprocedures
are flushed and memory is cleaned up for the next work unit.  This is
not a
bad model.  The only issue is if I need to make non-bound calls, at
which
point I have to decide whether the subprogram being called is part of
this
work unit (AG *CALLER) or its own unit (AG *NEW).

Old dogs can occasionally kick off the fleas and learn a new trick or
two
<grin>.

Joe


_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing
list
To post a message email: RPG400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
or email: RPG400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.


As an Amazon Associate we earn from qualifying purchases.

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-2024 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.