Re: Key List in 'D" spec

["Scott Klement" <infosys@xxxxxxxxxxxx>]

Rick,

This was a huge thread a month or two ago on this list.

One of the reasons that keylists remain in C-specs is that you
can place an element of an array on your KFLD statement, which
you wouldn't be able to do if you used D-specs.

Eventually the discussion boiled down to an argument between whether
keylists should stay the way they are, or if they should be eliminated
in favor of simply listing the fields you want to use on your
CHAIN/SETLL/SETGT/READE statement directly.

Something along the lines of:

C    (Cust:Order:Date)  CHAIN   ORDERFILE

instead of:

C    CusOrdDate    KLIST
C                  KFLD                      Cust
C                  KFLD                      Order
C                  KFLD                      Date
C    CusOrdDate    CHAIN        ORDERFILE

Not sure if/when they'll implement this new strategy, but sooner or
later they'll probably have us vote on it :)



rbrightman@amclog.com wrote:
>
> Does anybody know why RPG designers don't have 'key lists' in 'D'
>  specs? It
> seems to me that 'C' specs should only have "active" commands in the
>  Key list
> (KLIST) is a dead command.
>
> Rick,       Atlanta
>
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---