× 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.



Setting on LR means nothing in a Main cycle program. It does not cause
initialization or anything else.

On Thu, Nov 11, 2010 at 12:57 PM, Kurt Anderson <
kurt.anderson@xxxxxxxxxxxxxx> wrote:

So it sounds like an important piece of information to gather from this
thread is that if you are converting a program to have the MAIN H-spec,
leave the *INLR = *On; line in the program so variables are initialized as
they always have been (for the life of said program).

I'm glad this thread was brought up, it has got me thinking and I've
identified some programs that get called thousands of times in an activation
group.

Thanks,
Kurt

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Barbara Morris
Sent: Thursday, November 11, 2010 11:55 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: More on global declarations in RPG IV

On 2010/11/11 12:08 PM, Alan Campin wrote:
Global just means static storage. It never goes away.

You can have static storage in a subprocedure that is not global. So
TRUE : all global storage is static storage
FALSE: all static storage is global storage


An interesting question that maybe Barbara can answer is when does the
static storage go away when a program using the main keyword ends.
...
So the question becomes when does the storage get released?


The static storage gets released when the activation group ends.

RPG has three types of modules:
- cycle main (main procedure uses the RPG cycle)
- linear main (main procedure does not use the RPG cycle)
- NOMAIN - there is no main procedure

A linear-main module has much more in common with a NOMAIN module
- no cycle - *INLR doesn't any special meaning
- no implicit closing of files
- no implicit unlocking of data areas than with a cycle-main module
- has a program-entry procedure

I know that static storage does not go away when a program using the
main keyword ends.

When a DFTACTGRP(*NO) cycle-main program sets on LR, its static storage
does not get released. Instead, the static storage gets reinitialized by
RPG when the main procedure gets called again.
--
This is the RPG programming on the IBM i / System i (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.

--
This is the RPG programming on the IBM i / System i (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.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.