Re: MAIN and LR

Hi Barbara

So to clarify about initialization - and I did look at the reference and programmer's guide just now - when using MAIN, the extra initialization for the cycle doesn't happen. You can't even HAVE an *INZSR, as I understand.

I assume that data declared in the MAIN subprocedure is initialized every time it is called, unless declared as STATIC.

So what happens with global data? If running in *DFTACTGRP? Or is that not possible with a linear-main module? I did see the section on module initialization, with the subtopic on global data. But it wasn't clear what happens with global data when there is no cycle initialization.

Maybe, too, this is a stimulus to avoiding global data and passing it along in parameters from the MAIN subprocedure, eh?

I have to find a few minutes to try out some stuff, I can see that!

Thanks
Vern

On 9/25/2012 7:16 PM, Barbara Morris wrote:

On 2012/9/25 1:49 AM, Vernon Hamberg wrote:

Help me out here - I've always thought leaving *INLR *OFF means that on
another call to the program, variables will have the values they had
when the program ended before. Is this different with the MAIN keyword -
remember, we don't compile to 7.1 (blushing!).

Vern, you're right about how *INLR works for what's now called a
cycle-main module. (And was formerly just not called a NOMAIN module.)

With the MAIN keyword, you have something very similar to a NOMAIN
module, but the MAIN keyword indicates which of your subprocedures will
be the program-entry procedure. The main procedure is called a
linear-main procedure (running from beginning to end) rather than a
cycle-main procedure (running the RPG cycle).

Cycle-main:
/free
dsply 'hello';
return;

Linear-main:
H main(mypgm)
P mypgm b
/free
dsply 'hello';
// return opcode not needed
/end-free
P e