Re: Query optimizer tells me to build an access path thatalready exists

Bill, Steve, Jack and Clare,

Thanks.  I never would have guessed.   I was always under the assumption
that, under the covers, Physical and Logical file indices were more or less
just like thier SQL brethren (other than the obvious differences between a
view and an index, which still confuses me a little).

Steve - even if I had the sql product, I think storing create, alter or any
other design elements in a source file and running them from there with
runsqlstm is a good idea.  It's self documenting and all and it makes it
easier to duplicate work for identical libraries and such.

This is decidedly an 'old school' shop.  I will attempt to get the powers
that be to look more towards SQL for database design, but I won't promise
anything.

Thanks for the heads up everybody!

Rick

------original message-----------
Rick,
I believe I saw a posting from Kent Milligan (IBM's DB2/400 guru)
recently on the comp.sys.ibm.as400.misc usenet group recommending
to create indexes for performance enhancement in cases like yours.

The SQL product is not required to create indexes -
you can use RUNSQLSTM or an *QMQRY
to create indexes.

Steve Landess
Austin, Texas
(512) 423-0935