RE: CHAIN Versus SETLL and READ When Data Needed

[Peter.Colpaert@xxxxxxxxx]

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