I'd call it bad form, but that's about it.
From: Robert Rogerson [mailto:rogersonra@xxxxxxxxx]
Sent: Friday, November 10, 2017 2:29 PM
To: RPG programming on the IBM i / System i <rpg400-l@xxxxxxxxxxxx>
Subject: Setting on *inlr in a service program's module..
Is there anything wrong with setting on *inlr in a module in a service
program? I never do this, I just code a return. But I'm reviewing a
colleagues code and I honestly don't know if it's wrong to set on *inlr, or
if it doesn't make a difference.
The procedure in question has 3 files which are defined a static. My
understanding is that by coding static the file(s) are opened when the
procedure is first called and remain open until explicitly closed or the
activation group ends. So by setting on *inlr in the procedure is this
going to close the file(s) which would defeat the purpose of coding the
files as static?
I'm not sure if it is a bad practice to set on *lnlr in a subprocedure or
it doesn't really have any affect on performance.
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
Please contact support@xxxxxxxxxxxx for any subscription related
Help support midrange.com by shopping at amazon.com with our affiliate