Re: EXPORTing procedures

[Alan Campin <alan0307d@xxxxxxxxx>]

A Main Procedure is only for a Program call. It is a Program entrance.
There is nothing to Export.

If you want this procedure to called you will need to make it a service
program and use NOMAIN.

Note also that *NEW is dangerous. If this program is called many times, a
huge overhead.

On Thu, Nov 12, 2020 at 10:18 AM Brian Parkins <goodprophet.bp@xxxxxxxxx>
wrote:

> Here's a puzzle. Does anyone have a good explanation? I have a source
> member containing two procedures - the main (entry) procedure and a
> subprocedure (PROC2). The main procedure calls the subprocedure.
>
> If I code this as a Cycle Main program, all works well. Example:
>
> **Free
> Ctl-Opt DftActGrp(*No) ActGrp(*New);
> // Main Entry procedure
> Dcl-PR Proc2;
> End-PR;
> Dsply 'In main Proc' '*REQUESTER';
> Proc2();
> *InLR = *On;
> Return;
> Dcl-Proc Proc2;
> // Internal subprocedure
>    Dsply 'In Proc2' '*REQUESTER';
> End-Proc;
>
> If I code this as a Linear Main program, PROC2 requires the EXPORT
> keyword, e.g.
>
> **Free
> Ctl-Opt DftActGrp(*No) ActGrp(*New) Main(Proc1);
> Dcl-Proc Proc1;
> // Main Entry procedure
>    Dcl-PR Proc2;
>    End-PR;
>    Dsply 'In main Proc' '*REQUESTER';
>    Proc2();
>    Return;
> End-Proc;
> Dcl-Proc Proc2 Export;
> // Internal subprocedure
>    Dsply 'In Proc2' '*REQUESTER';
> End-Proc;
>
> (The source will compile but the Bind step fails without the EXPORT
> keyword - "No definition was found for reference PROC2 in *MODULE".)
> Why is the EXPORT keyword required?  (I've not been able to find any
> clear explanation in the manual - tell me what I'm missing.)
>
> FOOTNOTE: If I modified the coding of the second example and EXPORTed
> PROC1, I could then create a *SRVPGM which did /not/ require PROC2 to be
> EXPORTED.  Odd!
>
> Brian.
> --
> This is the RPG programming on IBM i (RPG400-L) mailing list
> To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/rpg400-l.
>
> Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: https://amazon.midrange.com