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



In 20+ years of RPG programming I've never used SETLL and HI at all.  If
I've wanted to position to a key that might be after the record I want then
I've always used SETGT instead.

Jonathan

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Mike Waite
Sent: 12 May 2006 09:25
To: rpg400-l@xxxxxxxxxxxx
Subject: SETLL and No Record condition

How often do people use SETLL and HI/%FOUND, rather than the more usual 
EQ/%EQUAL?

I've only ever it once, when positioning a file using a best-guess 
starting date (see below).  But I suspect I should be using it more 
often...


Mike


 
  *. 1 ...+... 2 ...+... 3 ...+... 4 ...+... 5 ...+... 6 ...+... 7 ...+.
  * 
  * Use the date sequence audit file to get the order no. start point 
  * - trap future date (just pick last record as best starting point) 
  * 
 C     #Key40        setll     oep40kl2                           99 
 C                   if        %found 
 C     l#cono        reade     oep40kl2 
 C                   else 
 C     l#cono        readpe    oep40kl2 
 C                   endif 
  * 
  * Key for Orders 
  * company code, starting date cyymmdd 
 C     #Key40        klist 
 C                   kfld                    l#cono 
 C                   kfld                    StrDate 

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.