nope...until v6.1 views are unkeyed.
Even in release 6.1 views cannot have any key.
In release 6.1 SQL indexes now can have where conditions (just as
select/omit clauses in DDS described logical files)
It is also possible to add new (calculated) fields to an index.
CREATE INDEX MySchema/MyIndXX ON MySchema/MyTable
(Year(MyDate) AS DATEYEAR ASC, Upper(Col2) as UpperCol2 ASC, Col3
WHERE Status in ('01', '07', '22', '47');
These indexes can be used by the query optimizer for executing SQL
statement, but they also can be used like any DDS described logical with
Mit freundlichen Grüßen / Best regards
"Shoot for the moon, even if you miss, you'll land among the stars." (Les
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and loosing them? Not training them
and keeping them!"
[mailto:midrange-l-bounces@xxxxxxxxxxxx] Im Auftrag von
Gesendet: Tuesday, 23. September 2008 17:43
An: Midrange Systems Technical Discussion
Cc: Midrange Systems Technical Discussion; midrange-l-bounces@xxxxxxxxxxxx
Betreff: Re: Setting a key field on a view
nope...until v6.1 views are unkeyed. in order to do a "chain" to the data
in the view you'll have to use embedded SQL.
"Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
09/23/2008 10:40 AM
Setting a key field on a view
I am creating an SQL view for a file that strips out the spaces in a
particular field. My question is if there is a why to set a key on that
view so a person can still CHAIN the file. We are on V5R3.