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



SETLL does set the %EQUAL indicator if there is a record with the
specified key (i.e. there is actually something to for a subsequent READE
operation to find).


-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Booth
Martin
Sent: Tuesday, December 08, 2015 2:40 PM
To: RPG programming on the IBM i (AS/400 and iSeries)
<rpg400-l@xxxxxxxxxxxx>
Subject: Re: Possible intereting SETLL behavior

Is there confusion between SETLL and SETLT? Should SetLowerLimits affect
the %found indicator? My understanding of SETLL is that the file marker is
positioned at a point just below the requested Limit but no attempt is
made by that instruction to read a record?

On 12/8/2015 1:28 PM, Vernon Hamberg wrote:
...
It does still seem odd that SETLL 0 file; for an arrival-sequence file
sets %found() to *off - there ARE records whose RRN > 0 (18 of them in
the file I'm reading), and this satisfies the definition of SETLL,
unless there is some unspoken special processing here.

Vern

--
This is the RPG programming on the IBM i (AS/400 and 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 thread ...

Follow-Ups:
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.