×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
what timing! there's been an ongoing discussion about this on
systeminetwork forums
http://forums.systeminetwork.com/isnetforums/showthread.php?t=52004
Barbara Morris gave some good insight on this thread.
Thanks,
Tommy Holden
From:
Chandra Krieg <chandrak@xxxxxxxxxxxxxx>
To:
"'rpg400-l@xxxxxxxxxxxx'" <rpg400-l@xxxxxxxxxxxx>
Date:
09/02/2008 08:37 AM
Subject:
Chain vs SetLL/ReadE
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!
TIA!
Chandra Krieg
i5 Programmer/Analyst
RateWatch
(P) 1.800.348.1831 ext 311
(F) 1.920.568.1403
www.rate-watch.com
midrange.com
