Re: What bugs you about KLISTs in RPG IV?

["R. Bruce Hoffman, Jr." <rbruceh@xxxxxxx>]

boldt@ca.ibm.com wrote:
> 
> 1) What are  the top three things that bug you about programming
>    compound keys in RPG?

# 1. Having to code them.  In COBOL we just specify that they are
externally-described-key and the copy statement takes care of the rest.

# 2.  See above.

# 3.  See #2.


> 
> 2) Would KLISTs in D-Specs fix any of those things?
> 

No.

> 3) What would make compound keys easier in RPG?
> 

See answers to first question.

Maybe something like:

      D extKeyList     KL       extfile([lib/]file[.member])

Then either I could use the prefix to set them off from the actual
fields in the record if I chose to.



> 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          *
> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

-- 
===========================================================
R. Bruce Hoffman, Jr.
 -- IBM Certified AS/400 Professional System Administrator
 -- IBM Certified AS/400 Professional Network Administrator

"The sum of all human knowledge is a fixed constant.
    It's the population that keeps growing!"
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* 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          *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *