I'd check the definition of the key fields you're using, compared to the
file. You're probably getting a fail on the SETLL, but you're not checking
it, and then the READE is not registering an %EOF, because whatever record
its on is greater than the way it interprets the key, so it doesn't trip
the indicator behind the scenes.
From: "RPGLIST" <rpglist@xxxxxxxxxxx>
To: rpg400-l@xxxxxxxxxxxx
Date: 11/17/2014 12:32 PM
Subject: Doing something wrong with a reade and Qualified DS
Sent by: "RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxx>
This is so simple but I'm running into a problem that I for the life of me
can't see.
I have a procedure where I'm reading through a file by doing a setll and
then a reade, same as I've done thousands of times, but this time it says
I've found the record when I've verified its not there...
Here is the relevant code:
Setll (xCmlPro:xCmlTrl) LdPrp;
Reade (xCmlPro:xCmlTrl) LdPrp LdPrpDs;
Dow not %Eof(LdPrp);
... - It executes this everytime even when we don't find a record.
Reade (xCmlPro:xCmlTrl) LdPrp LdPrpDs;
Enddo;
...
Is there something different about doing this in a procedure with a data
structure that I'm missing?
Dutch
--
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
