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

So, I created two modules, then used CRTPGM. Testing the resulting
program, it goes into some kind of loop as it enters the WrapText2
procedure. That's a guess, because I set a breakpoint in both modules, the
first in the calling module right on the statement that calls the
procedure, the second at the first executable statement in the called
module. I stepped from the first breakpoint, but the debug view hasn't
changed, there are no errors in the job log, the job's display stack shows
the called procedure active at statement 2100000001 (which I have no clue
what that corresponds to in my source), and the job's CPU time is
climbing. File I/O is at a standstill.

I guess the resolution is becoming more and more apparent. I'm trying to
get this working before EOD in a few hours, so, service program it is.

- Dan

On Fri, Aug 14, 2015 at 1:31 PM, Dan <dan27649@xxxxxxxxx> wrote:

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