RE: Ending a program from within a procedure

> -----Original Message-----
> From: rpg400-l-bounces@xxxxxxxxxxxx
> [mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Tony Carolla
> Sent: Tuesday, July 26, 2005 7:14 PM
> To: RPG programming on the AS400 / iSeries
> Subject: Re: Ending a program from within a procedure
> 
> 
> On 7/26/05, Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx> wrote:
> > 
> > A *NEW activation group ends as soon as the program that 
> created it ends.
> > So, if you compile your RPG program with ACTGRP(*NEW), the 
> activation
> > group (and everything in it) will be destroyed when your 
> program does a
> > RETURN (no matter if LR is on or off)
> > 
> > That's why everything gets cleaned up when you haven't turned LR on.
> 
> 
> That makes sense. I can see where using ACTGRP(*NEW) is bad 
> for programs 
> that are called multiple times (once per record, etc). 
> 
> Let me ask you this. If you have a program, say an inquiry 
> program. This is 
> called by a user, and is an interactive inquiry, that 
> optionally generates a 
> printout. A user may call this program several times in a 
> day, but it would 
> never be called repeatedly, in a loop. If I create this program using 
> ACTGRP(*NEW), each time the user exits the program, cleanup 
> of open files, 
> storage, etc. is automatic, and occurs regardless of LR. If I 
> create the 
> program in a named activation group, then will subsequent 
> calls to the 
> program perform better than subsequent calls to a 
> ACTGRP(*NEW) program? 
> 

Technically, yes.  But not enough that your user will ever notice.


Charles Wilt
--
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121