Re: Procedure Binding in CL

"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 03/19/2018
10:20:45 PM:

I'm not understanding the benefit of using CALLPRC with EXTPGM(*YES) vs
the regular CALL command that we've always used for external programs.

The benefit is that CALLPRC supports *OMIT while CALL does not.

Are you thinking that you'd want to code something like EXTPGM(&EXT) so
you can change it at run-time? If so, I don't think that'd work, since
the binding needs to be known at bind-time.

Currently, yes. But that is what the addition of the EXTPGM
parameter is all about. It would remove the compile-time binding
requirement just like the RPG/ILE compiler does when the EXTPGM keyword is
specified in a prototype. I know this is true because I can successfully
compile RPG/ILE programs that use the EXTPGM keyword even when the target
program does not exist, yet.

Aside from that possibility, I'm not sure what advantage this would

have?


Frankly, I don't understand why so many of the people on this list
just don't get what this request is all about -- no matter how many times
I've explained it. Thankfully, some do and have made good suggestions.
So, as I mentioned, I've amended the RFE to ask for *OMIT support on the
CALL command. So, that should remove all the confusion for those who just
don't get it.


Sincerely,

Dave Clark