Re: EOF

I too, protect myself from maintenance pgmrs with my own indicator, and
since I do not like to hard-code a filename, I use unqualified %EOF().
And I only use the format name, so my EOF is still not qualified.  And I
am still protecting my code.

Hard-coding File names in calcs reduces flexibility.
So later if I want to change Logical LF1 to LF101 with different
selection later, I do not have to change the calcs too.

Read Fmt1
Fmt1EOF = %EOF

Read Fmt2
Fmt2EOF = %EOF

Read Fmt3
Fmt3EOF = %EOF

As long as there are no other file I/Os between the reads done in the

SELECT and the %EOF test, it should work
as you expect. At least till someone comes along and adds a file I/O!

I prefer to use my own indicator.  This will produce a considerably

more stable application.

Coding for readability (and modularization) is a huge time saver.
To not care is to shoot yourself in the foot later, imo.

--
This is the RPG programming on the IBM i / System i (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.