Re: External procedure call returns a value. Does it need to be a service program?

On 14-Aug-2015 10:19 -0600, Dan wrote:

My first time in a *long* time developing a program that returns a
value to the calling program. Not quite connecting the dots.

d WrapText2 PR 12288 EXTPROC('UTPARSER')
d UnfText 8192 Varying Const Options(*VarSize)
d LineLen 5 0 Const
d LineBreak1 10 Varying Const Options(*NoPass)
d LineBreak2 10 Varying Const Options(*NoPass)

(I first tried EXTPGM instead of EXTPROC, but it got flagged with
RNF3755 "The EXTPGM keyword is not allowed when a return value is
specified.")

Using EXTPROC, there are no errors in the compiler, but the
compile/bind step fails with CPD5D02 "Definition not found for symbol
'UTPARSER'."

Per supervisor, we're trying to avoid having to use a binding
directory.

Ideas / advice appreciated.

As the message implies, a return value is not an option with a program, only with a procedure.

Even so, there is no need to use a Binding Directory (BNDDIR). Just specify a module name, or better [IMO], specify a service program name [into which the module was packaged] on the Create Program (CRTPGM) command invocation; e.g. use the Bind Service Program (BNDSRVPGM) parameter. The External Procedure (EXTPROC) will be found by the binder [during the binding phase, located in the specified service program name] without the use\specification of any binding directories [per defaulted or explicitly specified BNDDIR(*NONE) of the CRTPGM].