RE: V5R3M0 Performance Issues

Small correction, old query engine is CQE (Classic Query Engine).  New query
engine is SQE (SQL Query Engine).
I don't see how access path can be considered old.  Did you perhaps
encounter an issue with access path size (*MAX4GB vs *MAX1TB)?  Or in CQE
engine you were encountering query optimizer time-out due to large number of
indexes over the files?

Elvis B.

-----Original Message-----
Subject: Re: V5R3M0 Performance Issues

I know from upgrading to 5.3 that we did run into alot of issues with the
change to cqe engine for the queries (sql). I'm not sure how your app is
running but we did find that with the change to cqe if you are running sql
statements over logicals with include or omits in it, the queries will tank
unless you tell the optomizer to use the old query engine (sqe). The other
issue that we hit it large files with access paths that were "old", you cant
telll that they are but if you do a chglf and just take the option to force
the access path rebuild that helped alot. 
 
Not sure if it helps you, but thought I'd mention it