Re: the word 'static'

[Mel Rothman <mel@xxxxxxxxxxxxxx>]

The following text, copied from the "static keyword section of the 
RPG IV Reference Manual, succinctly explains the relationships 
between global, static, and automatic.

"The STATIC keyword specifies that the data item is to be stored in
static 
storage, and thereby hold its value across calls to the procedure in
which 
it is defined. The keyword can only be used within a subprocedure. All 
global fields are static.

"The data item is initialized when the program or service program it is 
contained in is first activated. It is not reinitialized again, even if 
reinitialization occurs for global definitions as part of normal cycle 
processing. 

"If STATIC is not specified, then any locally defined data item is
stored 
in automatic storage. Data stored in automatic storage is initialized at 
the beginning of every call. When a procedure is called recursively, 
each invocation gets its own copy of the storage."

Mel Rothman
iSeries Custom Technology Center
Rochester, Minnesota



"Stone, Brad V (TC)" wrote:
> 
> Subprocedure one sets on *in50, calls itself, *in50 is still on.  To me,
> that's static, whether it's global or local makes no difference in this
> case.
> 
> Brad
> 
> > -----Original Message-----
> > From: Buck Calabro [mailto:Buck.Calabro@commsoft.net]
> > Sent: Monday, June 04, 2001 11:09 AM
> > To: RPG400-L@midrange.com
> > Subject: RE: the word 'static'
> >
> >
> > >I've always considered Indicators to be contained in a spot
> > in memory for
> > >each job, and there is only one indicator memory area for
> > that entire job.
> >
> > Not by job, but by program.  If I do:
> >
> > PGM1
> >   SETON 50
> >   CALL PGM2
> >
> >   PGM2
> >     IF *IN50...
> >     * indicator 50 is off here, despite what happened in PGM1
> >
> > Of course with ILE the concept of "program" might need to be
> > revisited.
> >
> > Buck
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---