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

Just a quick note that I'm trying the suggestions here, although I'm
quickly gathering that the service program is the way to go here. I may
need to do it the supervisor's way, and then do it with a service program,
then show her the two options.

Not sure this utility will see much use outside of the program I am
including it in, but it's generic enough, and there are a lot of long
strings defined in our database that need to be cut down for printing and
EDI, so I can't help but think there's a lot of potential usage.

(Buck, the RNF3755 is a syntax error. EXTPGM keyword and return length on
the PR line not allowed.)

I'll report back how this resolves. Thanks for everyone's advice!

- Dan

On Fri, Aug 14, 2015 at 12:19 PM, Dan <dan27649@xxxxxxxxx> 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.

- Dan