Re: Correct use of STATIC variables

Well, not exactly, Joep - it says that static storage in ILE programs OTHER than the default activation group are not affected by RCLRSC. It does say this about OPM and ILE in default activation group -

For an original program model (OPM) program, its static storage will be reclaimed. For a user state Integrated Language Environment (ILE) program, its static storage will be marked so that it will be re-initialized on the next call.

So in this case, the end result is the same - although ILE in this circumstance has not reclaimed that storage, so the static storage doesn't have to be reinitialized, as I understand it.

Of course, this documentation does suggest that RCLRSC should not be used much, especially as a way to avoid careful use of resources in a program, such as open files and scope and all that.

Static storage in a non-default AG is not reclaimed.

HTH
Vern

J.Beckeringh@xxxxxxxxxxxxxxxxxxxxxxxxxx wrote:

David,

RCLRSC does not affect static storage of ILE programs (<
http://publib.boulder.ibm.com/infocenter/iseries/v6r1m0/index.jsp?topic=/cl/rclrsc.htm

).

If you have declared variables STATIC, then you must have a reason to do so and thus should know when the scope of your variable ends. If the static storage belongs to a program, you might consider initialising on entering the program if you want the scope to be the call level.

Joep Beckeringh

David FOXWELL
What is the normal manner to initialize such variables between program calls? Without using activation group *NEW. Currently, it seems we are relying on a CLP that issues a RCLRSC.

Thanks.