Key structure on the File specification

Let me start out by stating the problem I am trying to address.  That is, 
SQL currently does not support the concept of the combination of a VIEW 
and an INDEX into a single logical file like DDS does.  Now I'll delve a 
little into the details.

Granted having external keys on the File specification was a big 
improvement over RPG II.  Now, I wonder what it would take to modify the 
language a little to allow our own key data structure and let the access 
path at the time find the best index to use?  For example, I create a VIEW 
that only contains certain fields.  And previously I created several 
INDEXes over various access paths.

Now in my RPG I want to specify that VIEW but I want to still access it 
using Native RPG and not SQL.  By SQL definition the VIEW will not have a 
key.  And if you access it via SQL it will find the best INDEX.  However 
if I define that VIEW in my RPG and tell it I want to access it by key it 
tells me to 'dirt' in my hat and pull it down over my ears.  Maybe a 
KEYFLD(field1: field2: field3) keyword on the file specification would 
work?

Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin