RE: When to use Return vs. *INLR = *ON

I use Return in the subprogram when the calling program will call it *many*
times in the job.  Usually this is a batch job.  Usually, when I code a
program like this, I default it to Return, but provide an extra parameter
that tells it whether to seton LR or not; when the calling program is
finished, I set this "seton LR" parameter and call the subprogram, which
determines that it now sets on *inLR and gets out without doing anything
else.

- Dan Bale
(I am *NOT* "Dale"
http://archive.midrange.com/midrange-l/200105/msg00281.html )
SAMSA, Inc.
989-790-0507
DBale@SAMSA.com <mailto:DBale@SAMSA.com>
  Quiquid latine dictum sit altum viditur.
  (Whatever is said in Latin seems profound.)

-----Original Message-----
From: rpg400-l-admin@midrange.com [mailto:rpg400-l-admin@midrange.com]On
Behalf Of Wills, Mike N. (TC)
Sent: Thursday, April 18, 2002 12:32 PM
To: 'rpg400-l@midrange.com'
Subject: When to use Return vs. *INLR = *ON


I am writing a program that kind of acts like an exit program to another
program. I am wondering if I should do a return or set *INLR = *ON. When do
you use one over the other?