× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: lifetime of a static variable
  • From: pytel@xxxxxxxxxx
  • Date: Wed, 15 Nov 2000 17:36:33 -0600
  • Importance: Normal



> Does this mean that the static storage from a program remains allocated
> until its activation group ends?

Yes.

Every activation group will have it's own copy of static variables.
If you have module in *SRVPGM defined as *CALLER, then for every activation
group which calls this module, there will be a separate copy of static
variables for this module. This creates an isolation between activation
groups.
The idea of activation group is to have many applications in the same job
at the same time, but still isolated.

In theory these copies of static variables can take up a lot of space - if
you create lots of named activation groups, each calling the same module
with *CALLER, and never end activation groups.

    Alexei Pytel



Joel Fritz <JFritz@sharperimage.com>@midrange.com on 11/15/2000 03:40:45 PM

Please respond to RPG400-L@midrange.com

Sent by:  owner-rpg400-l@midrange.com


To:   "'RPG400-L@midrange.com'" <RPG400-L@midrange.com>
cc:
Subject:  RE: lifetime of a static variable



Does this mean that the static storage from a program remains allocated
until its activation group ends?  Suppose you use *caller most of the time
and actually call the programs from programs in the default activation
group.  Are there potential unpleasant consequences?  It sounds like you
could encounter something similar to the DOS/Windows problem with memory
leaks.

> -----Original Message-----
> From: pytel@us.ibm.com [mailto:pytel@us.ibm.com]
> Sent: Wednesday, November 15, 2000 11:07 AM
> To: RPG400-L@midrange.com
> Subject: RE: lifetime of a static variable
>
>
>
> Think of it as a generalization of a concept of "main program".
> For ILE "main program" is activation group.
> Most of resources in ILE are scoped to activation group -
> static storage,
> heap storage, open files etc. etc.
>
>     Alexei Pytel
>
>
>
>
+---
| 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
+---



+---
| 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
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.