Re: What bugs you about KLISTs in RPG IV?

[DAsmussen@xxxxxxx]

Hans,

In a message dated 6/15/99 11:05:20 AM Eastern Daylight Time, 
boldt@ca.ibm.com writes:

<<snip>>
> 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?

Sounds great to me, as it would be very similar to the CASE tool used with 
BPCS.  Roughly translated to RPG, it would read like:

chain mastfile,*eq,custno,acctno,date (where *eq is equal key and can be 
replaced with *ne for next equal or *pv for previous equal).

I prefer this file/key approach for clarity, as opposed to having the key 
first.  Of course, using the same KLIST for multiple reads of the same file 
would result in a smaller object, n'est pas?  Hopefully the optimizer would 
rectify this situation at compile time...

Thanks!

Dean Asmussen
Enterprise Systems Consulting, Inc.
Fuquay-Varina, NC  USA
E-mail:  DAsmussen@aol.com

"My father always told me, 'Find a job you love and you'll never have to work 
a day in your life.'" -- Jim Fox
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* 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          *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *