× 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: What bugs you about KLISTs in RPG IV?
  • From: "Hatzenbeler, Tim" <thatzenbeler@xxxxxxxxxxxxx>
  • Date: Wed, 16 Jun 1999 13:29:01 -0700

        snip.... 
> Something like:
> 
> cf    if chain(FILE: key1: key2) = -1
> cf  .... handle "not found" or "error" here...
> cf    else
> cf  ...  normal processing here ...
> cf    endif
> 
> I know that you can do something similar with BIFs, but this would
> (in my opinion) be even more elegant.
> 
> Scott Klement
> Information Systems Manager
> Klement's Sausage Co, Inc.
> 
        -----

        I agree with this suggestion 100% and and would even go as far as to
say....
        cf    if chain(FILE: key1: key2) 
        cf  ..... we found the record
        cf    else
        cf  ...  record not found..
        cf    endif

        change the result of the 'found chain' into a TRUE value....
        Tim Hatzenbeler


* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the RPG/400 Discussion Mailing List!  To submit a new         *
* message, send your mail to "RPG400-L@midrange.com".  To unsubscribe   *
* from this list send email to MAJORDOMO@midrange.com and specify       *
* 'unsubscribe RPG400-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.