From Windows 2000, I'm using the Client Access ODBC Driver (32-bit), Version 7.0 to fetch the data from DB2/400. The data is encoded with EBCDIC scheme, but the driver converts the data into ASCII format. I'm getting corrupted data. What can I do to solve this problem?
You'll want to look at the CCSID value for your character columns. In general, character columns should not be set to 65535. The CCSID system value should also not be 65535, it should be set to value corresponding to your language idd.
MORE INFORMATION ON THIS TOPIC
Search400.com's targeted search engine: Get relevant information on DB2/400.
The Best Web Links: tips, tutorials and more.
Check out this Search400.com Featured Topic: Database issues resolved
Dig Deeper on DB2 UDB (universal databases)
Related Q&A from Kent Milligan
To solve the SQL error -321 on IBM i6.1, use the new values statement to overcome the error. If you are using an older release, declare a cursor ... Continue Reading
When working with DB2 files with columns that have both short and long names, there is no option choose which column names are returned via ODBC ... Continue Reading
When developing tables in a parent-child relationship, use a primary key and a foreign key along with a unique ID to make your database easier to ... Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.