Invalid characters returned from DB2 on AS400 instead of Greek data with Connect for ODBC DB2 WP driver for a field/column with CCSID 37

Jun 30, 2015
Knowledge

Title

URL Name

Invalid-characters-returned-from-DB2-on-AS400-instead-of-Greek-data-with-Connect-for-ODBC-DB2-WP-driver-for-a-field-column-with-CCSID-37

Article Number

000174017

Environment

Product: Connect64 for ODBC driver for DB2 Version:7.1 OS: Solaris SPARC 10 (64 bit) Database: DB2 V5R4M0 on AS/400 Application: Not application specific

Question/Problem Description

Invalid characters returned from DB2 on AS400 instead of Greek data with Connect for ODBC DB2 WP driver for a field/column with CCSID 37

Steps to Reproduce

Clarifying Information

The application is UTF8.
DB2 code page is 875( Greek EBCDIC)
The database column/field (DRDL01) for which Greek Data is expected to be returned has a CCSID 37 which corresponds to latin-1 character set

When the odbc.ini file has the following setting, invalid characters are returned
CharacterSetFor65535=10
IANAAppCodePage=10
(These are the setting for Greek EDCDIC 875)
All characters appear as invalid for DRDL01 field
User-added image

When the odbc.ini file has the following setting, Latin characters are returned
CharacterSetFor65535=2028
IANAAppCodePage=2028
(These are the setting for Latin EDCDIC 37)

When trying to connect to the DB2 database in a native manner, valid Greek characters are returned

Error Message

Defect Number

Enhancement Number

Cause

Snoop logs confirm that the server is describing the column with CCSID37. The data is the characters that exist in 37 Latin EBCDIC and they just don't map to the same characters as 875 Greek EBCDIC

Resolution

There are no options to override the CCSID returned by the server that the driver uses to convert character data unless the CCSID is 65535.

If the CCSID for DRDL01 field can be changed to 65535 or 875 then greek characters will be returned if CharacterSetFor65535=10 and IANAAppCodePage=10 in the odbc.ini

Since the ccsid for DRDL01 field cannot be changed and set to any other value [ either 65535 or 875 ] , it is expected that latin-1 character set will be returned when CharacterSetFor65535=2028 and IANAAppCodePage=2028 in the odbc.ini and invalid characters will be returned when CharacterSetFor65535=10 and IANAAppCodePage=10.

Workaround

Use the native method to retrieve the Greek Characters from the field

Notes

There is no direct way [ just by changing the IANAAppCodePage and CharacterSetfor65535 setting in the odbc.ini] to obtain Greek characters using the Data Direct Connect for ODBC DB2 Wire Protocol driver when the CCSID for the field is set to 37.

The suggestions below can be tried to retrieve Greek characters for DRDL01 field , but they are not guaranteed to work :
a] Find a way to alter the CCSID in the field definition on the server.
b] Fetch the data as SQL_C_BINARY so that no character conversion will occur.
c] Try CASTing the column to a different character set like : CAST( DRDL01as CHAR (30) CCSID 65535 )

Keyword Phrase

Last Modified Date

6/30/2015 9:29 PM

Invalid characters returned from DB2 on AS400 instead of Greek data with Connect for ODBC DB2 WP driver for a field/column with CCSID 37

Files(0)

Was this article helpful?

Was this article helpful?

Invalid characters returned from DB2 on AS400 instead of Greek data with Connect for ODBC DB2 WP driver for a field/column with CCSID 37

Information

Related Articles