|
>Thanks for your input on this issue! ... >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? All I care about is not being required to match attributes in my key list (however it's coded) to the file's keys. If Query will allow me to use a 10 character field to chain to an 8 character key, padding with blanks as appropriate, why can't RPG? > >Cheers! Hans > >Hans Boldt, ILE RPG Development, IBM Toronto Lab, boldt@ca.ibm.com > > Charlie Massoglia, Massoglia Technical Consulting, Inc. PO Box 1065, Okemos, MI 48854, USA 517-676-9700 Fax: 517-676-1006 EMAIL: cmassoglia@voyager.net * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * 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 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.