× 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.



FWIW, my opinion is that, if you (can) have non-unique keys, and the rest 
of the record does matter, you need to avoid CHAIN, and code a READE loop 
instead.

Peter Colpaert
Application Developer
PLI - IT - Kontich, Belgium
-----
Yoda of Borg are we.  Futile is resistance, assimilated will you be.
-----



Arjen Drieënhuizen <Arjen.Drieenhuizen@xxxxxxxxx> 
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
01/03/2007 08:09
Please respond to
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>


To
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>
cc

Subject
RE: CHAIN Versus SETLL and READ When Data Needed






I agree, I did run into some strange situations with non-unique keys and
CHAIN, is it the oldest or the newest record that gets read first, and 
does
it leave the other records with the same key untouched?? While by
SETLL/SETGT this isn't an issue.


Just a thought

Arjen

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.