Re: V5R3 Performance Issue

<snip>
any chance a logical view has been deleted that the sql used, or
that the select or order by in the sql stmt has changed? Perhaps
not a v5r3 issue? Did anything change in your memory pools?
Settings for cache?
</snip>

I would agree with the comment.  Put these up in debug and watch the query
engine results.  Also, at DB group 4 there are some busted PTFs that
primarily are for restoring objects but I have also seen systems that have
SQL statements abort, and then gobble up massive amounts of Temporary
Storage.  Causes immense fault/page rates in the *MACHINE pool.  Only way I
know of to clear it is an IPL.   Check the temp storage with WRKSYSSTS  It
shows up in unprotected used.  If that is high, there may be a correlation.

Another issue is make sure you are now using the SQE query engine.  There
is a fine Redbook on the topic.  "Preparing for and Tuning the V5R2 SQL
Query Engine on DB2 Universal
Database for iSeries"   -  SG24-6598-00.  Check that out as well.  Lots of
great ways to use the graphical interface to DB/2 to get it really running
well.


Jim Oberholtzer
Senior Solutions Architect
Computech Resources, Inc.