Uncertain on CHAIN vs. SETLL/READE -- RPG400-L

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

Subject: Uncertain on CHAIN vs. SETLL/READE
From: James Lampert <jamesl@xxxxxxxxxxxxxxxxx>
Date: Fri, 09 Jan 2009 17:10:48 -0800
List-archive: <http://archive.midrange.com/rpg400-l>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: RPG programming on the IBM i / System i <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

I know that a SETLL with only the leading keyfield, followed by a READE with that same keyfield, is guaranteed to come back with the first record with that leading key.

But is that also true of a CHAIN with just the leading keyfield?

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Uncertain on CHAIN vs. SETLL/READE , jdavis
Re: Uncertain on CHAIN vs. SETLL/READE , Joe . Maguire
Re: Uncertain on CHAIN vs. SETLL/READE , Simon Coulter

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.