|
On Tue, 2008-09-02 at 08:34 -0500, Chandra Krieg wrote:
Hello all,use the SetLL, then do a ReadE and check for the %EOF indicator.
I have been told that the preferred method of random record retrieval is to
%Equal on the SetLL before reading the file? I have been told that the Chain
Why is this preferred over using a Chain with %found or even checking for
doesn't do what I'm expecting it to but I've never had issues in the past.
concrete explenation as to why. As with some of the posts I don't understand
I have read the archive posts and found opinions on the subject but no
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;
Well, I can imagine that it might be deemed a bit simpler to avoid
having both a CHAIN and a READE for one file in one chunk of code. But
my own taste would be to have only one READE, even at the cost of two
more lines of code.
SetLL (KeyFields) FileName;
DoW 0=0;
ReadE (KeyFields) FileName;
if %eof( FileName );
leave;
endIf;
do my stuff
EndDo;
Hope I do not sound too much like a broken record.
Cheers,
Terry.
Any explanations would be helpful!
TIA!
Chandra Krieg
i5 Programmer/Analyst
RateWatch
(P) 1.800.348.1831 ext 311
(F) 1.920.568.1403
www.rate-watch.com
--
This is the RPG programming on the AS400 / 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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.