Not quite sure I follow this discussion
For many years not setting on LR but doing RETURN, left the routine
open, all the variables with whatever values at the point of exiting the
routine, left all the files open etc, so that if you called the routine
again, it started up pretty much as it left off at the Return statement.
We're using this approach for a set of calls driven by a call sequence
file. Only thing to be careful of is to do Unlocks on any update files
in routines called but not setting LR. Otherwise a subsequent call to
another routine updating same file may get into record lock condition
Also be aware that *INZSR won't execute on subsequent calls to a non-LR
routine
Dave
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of James H. H. Lampert
Sent: 21 November 2013 22:12
To: RPG programming on the IBM i (AS/400 and iSeries)
Subject: Re: INLR no longer required?
On 11/21/13 1:17 PM, Englander, Douglas wrote:
We are on V7R1. I just compiled a program that did not reference LR
anywhere. It compiled. I ran it, and it does not stop.
I should think that would be a problem: "does not stop" implies that it
keeps running indefinitely. The last time I checked, a Cycle program
(and all RPG programs are implicitly Cycle programs, whether they
actually ride it or not, unless they explicitly disable The Cycle) that
doesn't, at some point, set LR runs inside an endless loop.
--
JHHL
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/rpg400-l.
midrange.com
