RE: Static and non-static variables in subprocedures

I think what Kurt is saying he wants is a static variable for the life of
the subprocedure no mater which activation group calls it. 
To do this your subprocedure would need to be in a service program which has
it's own named activation group. The service program would then be isolated
and the value of the static variable within the subprocedure would be
"static" for the life of the service program's activation group.

Duane  

-----Original Message-----
From: Wilt, Charles [mailto:CWilt@xxxxxxxxxxxx]
Sent: Wednesday, August 03, 2005 7:59 AM
To: RPG programming on the AS400 / iSeries
Subject: RE: Static and non-static variables in subprocedures


Kurt,

Not sure I understand your question.

A persistent local variable is made by declaring the variable STATIC.


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

> -----Original Message-----
> From: rpg400-l-bounces@xxxxxxxxxxxx
> [mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Kurt Anderson
> Sent: Wednesday, August 03, 2005 8:45 AM
> To: RPG programming on the AS400 / iSeries
> Subject: Static and non-static variables in subprocedures
> 
> 
> It's my understanding that a variable in a subprocedure gets
> re-initialized every time the subprocedure is called.  If a 
> variable in
> a subprocedure is coded as Static, then that variable persists for the
> life of the current activation group.
> 
> Is there a way to make local variables persist for the duration of the
> program object it was initialized in without regard to the activation
> group (meaning w/o saying specify actgrp *New)?  We're not an 
> activation
> group shop (aside from QILE) at the moment.
> 
> 
> Kurt Anderson
> Application Developer
> Highsmith Inc
> 
> -- 
> 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,
> visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.
> 
>