RE: IF NOT %FOUND

To answer your question... yes, you need to qualify %eof and %found on the file. Otherwise, you end up with issues like you outlined below when reading other files.

Not sure if that may even cross over to %loopup or others.

-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of SReeves@xxxxxxxxxxxxxxxxxx
Sent: Monday, November 11, 2019 1:50 PM
To: rpg400-l@xxxxxxxxxxxxxxxxxx
Subject: IF NOT %FOUND

So this bug came up in a pretty old program that I'm surprised that it
hasn't been an issue before today. My question is, when DOU %EOF and If
NOT %FOUND is used, without specifying a file, is always just using the
last read file?
Below is most the relevant code. The previous programmer didn't specify
the filename on the commands. Adding 'FILE1' to them fixed the issue, so
it is technically solved, but I just want to better understand myself why
it wasn't working.

In this case FILE1 had two matching records for the key. The first record
processed okay, it goes down to the end of the DO loop and the next record
is read. *(I ran it in debug so I know the program found it. It
immedially went back up to the top of the do loop, and then on 'IF NOT
%FOUND' it came up as not found, which surprised me as FILE1 was the last
file to be read and it did find the next record. Am I misunderstanding
something? Again, the program worked fine adding the proper file to the
command.


C KEY1 SETLL FILE1
C KEY1 READE FILE1
C DOU %EOF
C IF NOT %FOUND
...
C ELSE
...
C KEY2 CHAIN FILE2
...
C KEY3 SETLL KEY3
C KEY3 READE KEY3
...
C ELSE
C KEY1 READE FILE1
C ENDDO



Shane