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


  1.  Home
  2. RPG400-L
  3. December 2015

Re: CHAIN not found and subsequent READ - docs wrong?

On Fri, Dec 18, 2015 at 12:36 PM, Doug Davie <dougdavie@xxxxxxxxx> wrote:
Maybe the proper wording should be:

*..the file specified in factor 2 must be repositioned (for example, by a
CHAIN or SETLL operation) before a subsequent read operation can be done *
*accurately **on that file....*

Or some other word that means you can do it, but the results may not be
what you expect.

Right. The manual is usually careful to point out such cases, and does
so in clinical, precise terminology. It doesn't say "you can't do a
[high or low indicator] LOOKUP on an array that isn't sorted", for
example. It says instead that the LOOKUP "can produce unexpected
results".

So the same should go for CHAIN. Whether folks want to call the docs
confusing, misleading, wrong, incomplete, or whatever, I definitely
consider this a doc bug.

John Y.

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.