Rory,
In my eyes retaining the differentiation between "not open/is open" and "level check" is pretty huge. If I OPEN and ignore all errors, including level checks, that makes the program bug prone. If for some reason I'm running into a level check error - I want the program to either bomb (or be handled - although in my environment I simply let it bomb).
So while I never check for anything except for "is this file open or closed," I am implicitly allowing level checks to occur.
I guess I think this is a pretty big deal in a program and shouldn't to be hand-waived.
-Kurt
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Rory Hewitt
Sent: Thursday, February 04, 2010 11:41 AM
To: RPG programming on the IBM i / System i
Subject: Re: OPEN in RPGIII
Vern,
The ability to test whether a file is open - that is a very good
justification to move this program to ILE.
I would have thought this is an incredibly *minor* reason to move to ILE.
After all, as David has discovered, putting an indicator on the RPGIII OPEN
statement avoids an error anway. Adding your own flag to check this is also
easy.
Frankly, knowing whether a file is already open is something I rarely (if
ever) make use of, unless I know that the procedure in which the OPEN is
coded will be called thousands of times, where, I guess, a 'failed' OPEN
plus the exception check it causes (which is caught be the indicator or
whatever) might make a hit on performance.
All that said, I would run CVTRPGSRC on it.
Rory
On Thu, Feb 4, 2010 at 4:47 AM, Vern Hamberg <vhamberg@xxxxxxxxxxx> wrote:
David
If you can't convert, you can't do it. To do this, you have to convert.
The CVTRPGSRC is easy to run, is it policy never to use ILE? The ability
to test whether a file is open - that is a very good justification to
move this program to ILE. CVTRPGSRC does a minimal conversion, still
looks like OPM with wider columns.
Bon chance!
Vern
midrange.com
