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



My recommendation. 

SetLL(SomeKey) File;
DoU 0 = 1;
  Read (File);
  If %Eof(File) or
    SomeKey <> KeyField;
    Leave;
  EndIf;
  // Do something
EndDo;

Was told by IBM to never use a READE, always use a READ. From a Common 
conference years ago.  

-----Original Message-----
From: Paul Morgan [mailto:pmorgan@xxxxxxxxxxxxxx]
Sent: Tuesday, March 29, 2005 9:39 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: Chain doesn't set %EOF


Why doesn't a failed CHAIN (which sets off %FOUND) also set on %EOF?  I can
code a read loop as:

SetLL ( SomeKey) File;
ReadE ( SomeKey ) File;
DoW Not %Eof( File );
   // do something
   ReadE ( SomeKey ) File;
EndDo;

Rather that doing a SetLL/ReadE combo to start the loop it used to be
shorthand to code a Chain with:

Chain ( SomeKey ) File;
DoW Not %Eof( File );
   // do something
   ReadE ( SomeKey ) File;
EndDo;

except Chain doesn't fiddle with %EOF so this won't work.

Could do this with RPGIII.  You could put the same indicator for the CHAIN
NotFound indicator position and ReadE EndOfFile indicator position.  Any
possibility of getting Chain to set the %EOF indicator as well as the %FOUND
indicator?  Or would that break existing code?

Paul

-- 
Paul Morgan
Senior Programmer Analyst - Retail
J. Jill Group
100 Birch Pond Drive, PO Box 2009
Tilton, NH 03276-2009
Phone: (603) 266-2117
Fax:   (603) 266-2333








As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.