As I suspected, it was QZDAPKG database host server sql package (seen this
before).
You'd think that system would unconditionally rebuild QZDAPKG after the OS
upgrade, since all access plans stored in the package ought to be
invalidated by the OS upgrade.
Elvis
Celebrating 11-Years of SQL Performance Excellence on IBM i, i5/OS and
OS/400
www.centerfieldtechnology.com
-----Original Message-----
Subject: RE: Debugging ODBC
This resolved it, even though we're running V5R4 and not V5R3.
IBM reference number: 86256ED90061C0CE
http://tinyurl.com/5o2mmp
http://www-1.ibm.com/support/docview.wss?rs=0&dc=DB520&dc=D900&q1=cpd4392+AN
D+AS400SUMXXYYZZRCH&uid=nas1d24edca172557f5686256ed90061c0ce&loc=en_US&cs=UT
F-8&lang=all
Rob Berendt
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
