Re: Doing something wrong with a reade and Qualified DS

On 11/17/2014 11:38 AM, RPGLIST wrote:

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?

Not that I've encountered. If I were to run across this, I'd put a
DUMP(A) right after the DOW (and then SETON LR and LEAVE). The dump
will show you exactly what was read and then you can compare it to what
is in the file.

--

--buck

'I had nothing to offer anybody except my own confusion' - Jack Kerouac
--
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.