Re: dynamic program CALLS

["James W. Kilgore" <qappdsn@xxxxxxx>]

Richard Baird wrote:

> >
> >
> >Vernon Hamberg wrote:
> >
> >> I suspect every call to a CLP requires reinitialization—along the lines of
> >> turning on *INLR in RPG.
> >>
> >
> >That's sort of what I've accepted (heard it before), but it made me
> curious of
> >the purpose of the RETURN code.
> >
> >If it doesn't return without ending, the best I've been able to figure out is
> >that it is preferred to a GOTO to a labeled ENDPGM.
> >
> >But then again, this "common knowledge" may be unfounded.  I'm sure that
> someone
> >on this list will set us straight. :)
>
> to me, that is EXACTLY the purpose of RETURN.   It exits the program
> WITHOUT closing.   Very handy, IMO if the program is called multiple
> times in a single job - of course, you have to make sure you initialize
> variables where appropriate.
>

When I posted my response to Vernon, I was referring to CL RETURN.  I've 
noticed a
couple of responses about RPG RETRN.  It appears that CL RETURN does not 
function
the same as RPG RETRN with LR off.  It's not that big of a deal, I'm hard 
pressed
to think of a time where I do many repetitive calls to CL, while I do to RPG.

BTW,  I got slammed once way back when, for using a call to CL to *CAT a
city,state,zip string on a S/38 during a check run, thinking that CL RETURN 
would
reduce overhead on the call.  At the time RPG  didn't have a CAT function and
man-o-man the finger wagging that went on for that one!  At the time, I would 
like
to have had the time to have done a dedicated system test on 1200 calls (number 
of
Payroll checks written) vs the array manipulation required to do the same.  I've
always had a hunch that the calls were no worse and cleaner code.

P.S. the S/38 was so new that the local SE's didn't even know what to do with
them.  Everyone was so ingrained in S/34 mode of thinking.  Oh yes...the long
hours, late nights, stacks of manuals...wait a minute!  Don't tell me 
development
is a recursive loop =:-o



+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---