SQL query results in CPI432F

["Dennis Lovelady" <iseries@xxxxxxxxxxxx>]

I have a somewhat complex query that resulted in CPI432F (suggested access
path, essentially).  This query joins two files, and the suggestion is to
add an index over the first file (TAPTC) using keys of TCER and TCSTGE.

 

I then created a DDS-based logical over the TAPTC file using the suggested
keys since there are other applications that can take advantage of this.
Then I ran my query again.

 

Oddly, the same message appears in the joblog (with debug active), and the
same suggestion of TCER and TCSTGE.  Is this an expected behavior at V5R3?
I don't think I've run into it before.   (Note: I did ensure that the file I
created actually exists, and that it's over the right table, and so on.  In
fact, it is listed as the second "access path considered" in CPI432C
message.)

 

Thanks,

Dennis E. Lovelady
AIM: delovelady      MSN: fastcounter@xxxxxxxxxxxx
 <http://www.linkedin.com/in/dennislovelady>
www.linkedin.com/in/dennislovelady --
"Everything is funny as long as it is happening to somebody else."
       - Will Rogers