Even if there are no performance hits, using a *NEW activation group is just bad practice, IMO. If your memory allocation strategy within a procedure/program is so complex that it is difficult to determine where to put the %DEALLOC you need to redesigned the process.
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Aaron Bartell
Sent: Monday, August 18, 2008 7:29 AM
To: RPG programming on the AS400 / iSeries
Subject: Re: Dynamically allocated tables and %DEALLOC
But how expensive is it *really*? I am wondering if it is one of those
things where hardware has progressed to the point where it isn't as
noticeable anymore. Note I am not saying don't program for efficiencies,
but I do think about programmer debugging cryptic issues vs. taking certain
defaults to gard ones self.
Has somebody done some performance tests on this so we have more concrete
On Mon, Aug 18, 2008 at 7:13 AM, <vhamberg@xxxxxxxxxxx> wrote:
Using *NEW adds its own set of problems - mostly in performance - because
it is relatively expensive to start a new AG. It IS an easier way to manage
things, sometimes, but it is probably better to be sure you deallocate all
memory yourself that you have allocated.
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
NOTICE: This electronic mail transmission may contain confidential information and is intended only for the person(s) named. Any use, copying, or disclosure by any other person is strictly prohibited. If you have received this transmission in error, please notify the sender via e-mail.