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

On 8/14/2015 12:19 PM, Dan wrote:

I'm re-writing your note to start with this:

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

I think supervisor is making a mistake. Binding directories help
simplify my life considerably; without them I have to manually supply
all the pieces /parts for every mainline program I compile. Does
supervisor give a reason?

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.")

OK. You can't use EXTPGM unless UTPARSER is actually a *PGM object.
Can you do a DSPPGM UTPARSER? If it is a program, what does the
parameter list look like?

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

Without a binding directory you will need to specify the service program
that holds UTPARSER yourself. That assumes that UTPARSER is already a
subprocedure packaged in a *SRVPGM object.