× 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: Re: CHAIN vs. SETLL (was Re: DOW vs DOU)
  • From: Mark Lazarus <mlazarus@xxxxxxxx>
  • Date: Thu, 05 Jun 1997 20:49:58 -0400 (Eastern Daylight Time)

Dave,

>I think the bug still exists on S/36 compatible RPG.  It caused me
>headaches to figure this out. It was not pretty when users complained
>that few checks for the client never showed up on the screen.   I even
>complained to IBM.  Of course, "it was working as designed" was the
>classic response.  The best way for non-unique key files is still READE
>instead of CHAIN.  My personal preferance is a SETLL followed by a READ
>in a DOW (let us not start that again).

 What is the bug?  Since the the RPG II doesn't support KLISTs, a full key
is necessary in order to make the READE work.

 -mark

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *


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.