Re: Procedure Binding in CL

[Scott Klement <midrange-l@xxxxxxxxxxxxxxxx>]

Dave,

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.

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.

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

-SK


On 3/16/18 9:32 AM, dlclark@xxxxxxxxxxxxxxxx wrote:
>          Since in RPG/ILE the CALLP op code can be used with external
> programs (via prototype), does anybody think it would be a good idea to
> add a parameter to the CL/ILE CALLPRC command so that it could also
> support external programs?  Would anybody vote for that RFE?
>
> CALLPRC ... EXTPGM(*YES) /* with a default of *NO for backward
> compatibility +
>                              and mutually exclusive of the RTNVAR parameter
> */
>
>          In the meantime, I decided to stick with CALL in my CL and to
> change the target CL to detect blanks passed in these optional parameters
> and, if found, use the same defaults as if the parameter had been omitted
> altogether.  The target CL has been in use for years so changing it to a
> service program at this point would be too disruptive.
>
>          Thanks, all.
>
> Sincerely,
>
> Dave Clark