× 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: "Leland, David" <dleland@xxxxxxxxxx>
  • Date: Tue, 15 Jun 1999 10:56:47 -0500

I like this idea a LOT!  We would definitely take advantage of this.

Dave

> ----------
> From:         boldt@ca.ibm.com[SMTP:boldt@ca.ibm.com]
> Reply To:     RPG400-L@midrange.com
> Sent:         Tuesday, June 15, 1999 8:50 AM
> To:   RPG400-L@midrange.com
> Subject:      RE: What bugs you about KLISTs in RPG IV?
> 
> 
> 
> Thanks for your input on this issue!
> 
> Here's a bit more background:  We understand fully why people
> want to be able to define KLISTs in D-Specs.   However, while
> a KLIST does define a klist name, the key fields are somewhat
> awkward on the D-Spec.  For example, although you can  define
> fields on the KFLD opcode, you can also  code indexed arrays,
> which are not allowed today in positions 7-21 of the D-Spec.
> 
> Someone raised the idea of a "KLIST Data Structure".  That is
> an interesting idea which I'll pursue further.   But, I don't
> think it would be able  to fully replace the functionality of
> of the KLIST.
> 
> One person came close to another idea that we've been playing
> with here in the lab.  As you know, there are rumors floating
> around about a new free-format calc spec.  Let's assume for a
> moment  that these rumors are true.  This would give new ways
> to enhance old opcodes.  The main thing  that has bothered me
> about KLISTs is that they are necessary at all! If we weren't
> limited to 14 chars in Factor 1, we would be able to list the
> keys directly in the CHAIN opcode.  Imagine for a moment:
> 
>      cf   chain (custno: acctno: date) mastfile
> 
> or even:
> 
>      cf  chain (prodno: 'X' + subcode(n+14)) mastfile
> 
> In other words, full expressions coded directly as key fields
> for the keyed I/O operations!
> 
> So todays questions are:  Would you take advantage of this if
> available?  Would you still use KLISTs?
> 
> Cheers!  Hans
> 
> Hans Boldt, ILE RPG Development, IBM Toronto Lab, boldt@ca.ibm.com
> 
> 
> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
> * *
> * 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
> *
> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
> * *
> 
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* 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 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.