Re: Chain vs SetLL/ReadE

With the exception of unique keys, how can you retrieve all the records
that matches you key fields using chain?

"Chandra Krieg" <chandrak@xxxxxxxxxxxxxx> wrote in message
news:<mailman.7780.1220362560.2545.rpg400-l@xxxxxxxxxxxx>...
Hello all,

I have been told that the preferred method of random record retrieval is
to use the SetLL, then do a ReadE and check for the %EOF indicator.

Why is this preferred over using a Chain with %found or even checking
for %Equal on the SetLL before reading the file? I have been told that
the Chain doesn't do what I'm expecting it to but I've never had issues
in the past.

I have read the archive posts and found opinions on the subject but no
concrete explenation as to why. As with some of the posts I don't
understand why you would want to readE the file if the SetLL didn't find
an %equal match or why if you plan to read the file a chain isn't
appropriate.

I'm being told to use the following code instead of a Chain.

SetLL (KeyFields) FIleName;
ReadE (KeyFields FIleName;
DoW Not %EOF(FIleName);
do my stuff
ReadE (KeyFields) FileName;
EndDo;

Any explanations would be helpful!