RE: Permormance question?

There's more than one way to handle this.  If it's a program that's mostly
called by other programs, *NEW is a bad choice.  Depending on resource
scoping, I'd probably go with *CALLER as the first choice.

As far as performance is concerned, a dynamic call that ends with LR off
isn't a lot slower than a static call.  My inclination, if it's a program
that's called by a variety of other programs would be to make it a service
program or a module in a larger service program.

There was an interesting thread a few weeks ago on the pros and cons of
named activation groups vs the "anonymous" *NEW.  *NEW definitely has its
place.

> -----Original Message-----
> From: PatrickConner@parkdalemills.com
> [mailto:PatrickConner@parkdalemills.com]
> Sent: Thursday, August 23, 2001 8:01 AM
> To: rpg400-l@midrange.com
> Subject: Re: Permormance question?
>
>
>
> To answer you best we probably need more information about your
> 400/iSeries. OS Version? How strapped are you for resources?
> However, I agree with Buck's advice. Convert it and keep an
> original. Then
> compare the two.
>
> I have a follow up question for the group.
> If this guy converts and compiles using ActGrp(*New) on the
> program being
> called, will that not have the effect of causing the
> application to run
> slower.
> He needs to assign an activation group, such as QILE, to get
> the better
> performance. Right?
> Or better yet make both the calling program and the called
> program modules
> of one program. Correct?
>
> Patrick Conner
> www.ConnecTown.com
> (828) 244-0822
>
>