×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Kind of some shoot from the hip stuff.
I'm not that familiar with connection strings when connecting from DB2 on
IBM i to other platforms. I know that there's often some ODBC parameter
when going the other way, like "Translate 65535 data" or some such thing.
Many of us (in the USA) have changed our QCCSID system value from 65535 to
37. Often midday without any disruption. IDK if CHGJOB with
Country or region ID . . . . . . CNTRYID US
Coded character set ID . . . . . CCSID 37
would be a valid test. Gut says yes.
Chuck Pence has raised some concerns in the past about this and you can
search the archives, but again, many have done the CHGSYSVAL thing and are
running fat dumb and happy.
There is a CCSID clause you can specify on each column when you create the
table on IBM i.
There is also a CCSID clause when you CAST. That may be useful when
casting from the CCSID on the remote to the CCSID you want in DB2.
Rob Berendt
This mailing list archive is Copyright 1997-2024 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
