Export (0) Print
Expand All

ANSI Code Page Support Using the ODBC Driver for DB2

IBM DB2 Universal Database for Windows NT and IBM DB2 Universal Database for AIX are frequently configured to use ANSI code pages, for example ANSI 1253 (Greek). Host Integration Server 2000 includes support for some ANSI code pages for purposes of ANSI-to-UNICODE-to-ANSI conversions when using the OLE DB Provider for DB2 or the ODBC Driver for DB2. These ANSI code pages can be used when accessing IBM DB2 Universal Database on Windows NT and IBM DB2 ON AIX (not all of these ANSI code pages are supported on IBM DB2 Universal Database for AIX).

The following table shows the ANSI character code set identifiers (CCSIDs) supported by ODBC Driver for DB2 in Host Integration Server 2000.

Microsoft Display NameMicrosoft NLS Code PageIBM CCSIDComments
ANSI - Arabic12561256On Windows NT 4.0, support for this NLS Code Page is installed using the arabic.inf file from the Language Pack.
ANSI - Baltic12571257On Windows NT 4.0, support for this NLS Code Page is installed using the european.inf file from the Language Pack.
ANSI - Cyrillic12511251On Windows NT 4.0, support for this NLS Code Page is installed using the cyrillic.inf file from the Language Pack.
ANSI - Central Europe12501250On Windows NT 4.0, support for this NLS Code Page is installed using the european.inf file from the Language Pack.
ANSI - Greek12531253On Windows NT 4.0, support for this NLS Code Page is installed using the greek.inf file from the Language Pack.
ANSI - Hebrew12551255On Windows NT 4.0, support for this NLS Code Page is installed using the hebrew.inf file from the Language Pack.
ANSI - Latin I12521252Support for this codepage is normally installed as part of the operating system on Windows 2000, Windows NT, Windows 98, and Windows 95.
On Windows NT 4.0, support for this NLS Code Page is installed using the us_eng.inf file from the Language Pack.
ANSI - Turkish12541254On Windows NT 4.0, support for this NLS Code Page is installed using the turkish.inf file from the Language Pack.
ANSI/OEM - Japanese Shift JIS932932On Windows NT 4.0, support for this NLS Code Page is installed using the japanese.inf file from the Language Pack.
ANSI/OEM - Korean949949On Windows NT 4.0, support for this NLS Code Page is installed using the korean.inf file from the Language Pack.
ANSI/OEM - Simplified Chinese GBK936936On Windows NT 4.0, support for this NLS Code Page is installed using the exchsrvr.inf file from the Language Pack.
ANSI/OEM - Thai874874On Windows NT 4.0, support for this NLS Code Page is installed using the thai.inf file from the Language Pack.
ANSI/OEM - Traditional Chinese Big5950950On Windows NT 4.0, support for this NLS Code Page is installed using the tchinese.inf file from the Language Pack.
ANSI/OEM - Viet Nam12581258On Windows NT 4.0, support for this NLS Code Page is installed using the vietnam.inf file from the Language Pack.

The Microsoft Display Name is the name found in the Windows 2000 or Windows NT definitions for these NLS files. The Microsoft NLS Code Page column represents the code page number that is registered and associated with an ANSI-to-UNICODE NLS resource file. The Microsoft NLS number should be set as the Host CCSID when configuring data sources when using the ODBC Driver for DB2. When setting the Host CCSID or PC Code Page parameter using a connection string, the Microsoft NLS number should be used for this parameter.

The IBM CCSID column represents the CCSID given to the ANSI code page in IBM publications, which for these supported ANSI CCSIDs are the same as the Microsoft CCSID values. IBM lists their ANSI support in publications by referencing the display name which for these ANSI code pages is the same as the Microsoft display name. The ODBC Driver for DB2 does not recognize or display the IBM CCSID values when configuring data sources. The ODBC Driver for DB2 maps the Microsoft NLS numbers to ANSI NLS files which correspond with the appropriate IBM CCSID numbers. The Microsoft ODBC Driver for DB2 passes the corresponding IBM CCSID to the DB2 system at run time even though you configure the driver to use the Microsoft NLS number.

These are the only ANSI pages currently supported by the ODBC Driver for DB2 in Host Integration Server 2000 and in SNA Server 4.0 with Service Pack 3 or later. IBM supports additional ANSI pages, however, the ANSI code pages listed in the table above are the only cases where the Microsoft NLS pages and IBM ANSI code pages (CCSIDs) match.

Show:
© 2014 Microsoft