We ran into a similar problem that apparently started when we upgraded from
5.2 to 5.3. The issue is explained in an IBM document 29290926
http://www-912.ibm.com/s_dir/slkbase.NSF/0/9ea41ee0c6099d1e86256caa006e4b59?
OpenDocument in more detail, but I have a ticket open with IBM and their
recommended fix is to change the system value QCCSID from 65535 to 37. We
are going to be testing this fix today, and I will email the group with our
finding.
Larry
Larry Ketzes | Senior iSeries System Administrator | AIG / ALICO - American
Life Insurance Company
One ALICO Plaza, 600 N. King Street, AMIS | Wilmington, DE 19801 | *:
302.594.2146 | 7: 302.830.4524| *: larry.ketzes@xxxxxxx
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Urbanek, Marty
Sent: Friday, July 27, 2007 8:16 AM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: V5R4 and ODBC
Mary,
I don't know what release you were on before, but somewhere in the last
few releases they made it where you can't have CCSID 65535 any more for
ODBC/JDBC. Could be your sysval QCCSID.
-Marty
------------------------------
date: Thu, 26 Jul 2007 19:38:59 -0400
from: "Mary Kern" <mtkern@xxxxxxxxxxxxxxxxxxx>
subject: V5R4 and ODBC
I have a PC (web based) application that uses ODBC to connect to a table
on
our iSeries and then send emails using the data in that table. I used
it
Friday during the day. I installed V5R4 on Friday night. Saturday I
could
not connect to the table. I?ve upgraded the ODBC driver on the server
to
V5R4 (at least I installed iSeries Access V5R4 that included the ODBC
driver
and I assume it upgraded the ODBC driver). I built a new system DSN
after
the V5R4 install. Still cannot connect.
Does anyone know what I might have to do to allow this application to
use
the tables in this library?
Thanks!
Mary
midrange.com
