RE: SQL query results in CPI432F

What happens if you create a SQL index? Same message? Also, I seem to
remember that sometimes the optimizer "times out" and does not have the
time
to examine every index, so it can advise an already created index (at
least,
this seems to apply to the Index Advisor in Visual Explain)

Same thing happens after:
CREATE INDEX lib/TAPTALTC9
ON lib/TAPTC
(TCER, TCSTGE, TCEN, TCDTH)

(Oddly, it took as long to create this index as it did to create the LF even
though the LF still existed at the time.)

If this were due to timeout, would the newly-created index appear in the
list of "considered access paths?" (CPI432C) It does in fact. Rejected for
reason 5.

It was a matter of curiosity - there are plenty of other reasons this
particular SQL will operate inefficiently. Now my interest is in whether we
should pursue some PTF at V5R3 for this, or it it's expected under certain
(what?) circumstances.

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"If living conditions don't stop improving in this country, we're going to
run out of humble beginnings for our great men."
-- Russell P. Askue