We have them - no problems with it, except for one that most folks won't
run into. When you use DB monitor, if your outfile is truncated from the
right (not all fields used), there is a nasty bug. APAR is SE10502 - they
know what to fix but no PTF yet. This applies only to queries processed
with the new engine. At the moment, you prevent this by setting QQRYDEGREE
to something that assumes using SMP (*IO, *OPTIMIZE), or use CHGQRYA to do
the same in an individual job.
The PTF is part of the process of bringing more and more function into the
new query engine. The Enhancements Redpiece at the listed site helps
understand what it can do now. There's also the info APAR II13486.
At 10:13 AM 6/12/2003 -0500, you wrote:
Anyone put these on and noticed some drastic stuff; pro or con?
o DB2 UDB for iSeries SQL Performance PTFs