If you are using the Microsoft(R) XP operating system (2600) configured to use the NETBIOS protocol with the DB2 family of products, you need to obtain a hotfix from Microsoft. Contact Microsoft with the Knowledge Base article number Q317437.
2The Windows XP Home Edition operating system is supported only 2by DB2 UDB Personal Edition products.
The Windows XP Professional operating system is supported by the following DB2 products:
The Microsoft Japanese Windows Shift-JIS code page is registered as the 6IBM coded character set identifier (CCSID) 943. However, the Shift-JIS code 6page on HP-UX platform is registered as CCSID 5039. CCSID 5039 contains characters 6in the Japanese Industry Standard (JIS) only, and does not have any vendor 6defined characters. You can use a DB2 UDB database of CCSID 5039 on HP-UX 6to store Shift-JIS characters, but there will be code page conversion between 6CCSID 5039 and CCSID 943. When using Microsoft ODBC applications, you might 6encounter a problem when converting data in CCSID 5039 to Unicode, due to 6differences between IBM's code page conversion table and Microsoft's code 6page conversion table.
6The following list of characters, when converted from CCSID 5039 to Unicode, 6will result in different code points depending on which conversion table is 6used (IBM or Microsoft). For these characters, the IBM conversion table conforms 6to the Japanese Industry Standard JISX0208 and JISX0221.
6 6| Shift-JIS code point (character name) | 6IBM primary code point (Unicode name) | 6Microsoft primary code point (Unicode name) | 6
|---|---|---|
| X'815C' (EM dash) | 6U+2014 (EM dash) | 6U+2015 (Horizontal bar) | 6
| X'8160' (Wave dash) | 6U+301C (Wave dash) | 6U+FF5E (Fullwidth tilde) | 6
| X'8161' (Double vertical line) | 6U+2016 (Double vertical line) | 6U+2225 (Parallel to) | 6
| X'817C' (Minus sign) | 6U+2212 (Minus sign) | 6U+FF0D (Fullwidth hyphen-minus) | 6
For example, the character EM dash with the CCSID 5039 code point of X'815C' 6is converted to the Unicode code point U+2014 when using the IBM conversion 6table, but is converted to U+2015 when using the Microsoft conversion table. 6This can create potential problems for Microsoft ODBC applications because 6they would treat U+2014 as an invalid code point. To avoid these potential 6problems, DB2 UDB provides the alternate Microsoft conversion table from CCSID 65039 to Unicode, in addition to the default IBM conversion table. You need 6to replace the default IBM conversion table with the alternate Microsoft conversion 6table. Note that the default IBM conversion table from Unicode to CCSID 5039 6matches the Microsoft version.
6 6 6When you convert from CCSID 5039 to Unicode, the DB2 UDB default code page 6conversion table is used. If you want to use a different version of the conversion 6table, such as the Microsoft version, you must manually replace the default 6conversion table (.cnv) file.
6Before replacing the existing code page conversion table file in the sqllib/conv directory, you should back up the file 6in case you want to change it back. On UNIX and Linux, the sqllib/conv directory is linked to the DB2 UDB installation path.
For conversion table replacement to be effective, every DB2 UDB client 6that connects to the same database must have its conversion table changed. 6Otherwise, the different clients might store the same character using different 6code points.
To replace the DB2 UDB default conversion table for converting from CCSID 65039 to Unicode, follow these steps:
6The IBM coded character set identifier (CCSID) for the Japanese EUC code 6page is registered as CCSID 954. CCSID 954 is a common encoding for Japanese 6UNIX and Linux platforms. When using Microsoft ODBC applications to connect 6to a DB2 UDB database of CCSID 954, you might encounter a problem when converting 6data from CCSID 954 to Unicode. The potential problem is due to differences 6between IBM's code page conversion table and Microsoft's code page conversion 6table. The IBM conversion table conforms to the character names as specified 6in the Japanese Industry Standard (JIS) JISX0208, JISX0212, and JISX0221.
6The following characters, when converted from CCSID 954 to Unicode, will 6result in different code points depending on whether the IBM or Microsoft 6conversion table is used.
6 6| EUC-JP code point (character name) | 6IBM primary code point (Unicode name) | 6Microsoft primary code point (Unicode name) | 6
|---|---|---|
| X'A1BD' (EM dash) | 6U+2014 (EM Dash) | 6U+2015 (Horizontal Bar) | 6
| X'A1C1' (Wave dash) | 6U+301C (Wave Dash) | 6U+FF5E (Fullwidth Tilde) | 6
| X'A1C2' (Double vertical line) | 6U+2016 (Double vertical line) | 6U+2225 (Parallel To) | 6
| X'A1DD' (Minus sign) | 6U+2212 (Minus sign) | 6U+FF0D (Fullwidth hyphen-minus) | 6
| X'8FA2C3' (Broken bar) | 6U+00A6 (Broken bar) | 6U+FFE4 (Fullwidth broken bar) | 6
For example, the character EM dash with the CCSID 954 code point of X'A1BD' 6is converted to the Unicode code point U+2014 when using the IBM conversion 6table, but is converted to U+2015 when using the Microsoft conversion table. 6Due to this difference of conversion mapping, you might have two different 6code points for the same character in a DB2 UDB Unicode database, or in a 6graphic column of a DB2 UDB 954 database. This can create potential problems 6for Microsoft ODBC applications because they would treat U+2014 as an invalid 6code point. To avoid these potential problems, DB2 UDB provides the alternate 6Microsoft conversion table from CCSID 954 to Unicode, in addition to the default 6IBM conversion table. You need to replace the default IBM conversion table 6with the alternate Microsoft conversion table. Note that the default IBM conversion 6table from Unicode to CCSID 954 matches the Microsoft version.
6 6 6When you convert from CCSID 954 to Unicode, the DB2 UDB default code page 6conversion table is used. If you want to use a different version of the conversion 6table, such as the Microsoft version, you must manually replace the default 6conversion table (.cnv) file.
6Before replacing the existing code page conversion table file in the sqllib/conv directory, you should back up the file 6in case you want to change it back. On UNIX and Linux, the sqllib/conv directory is linked to the install path of DB2 UDB.
For this to be effective, every DB2 UDB client that connects to the same 6CCSID 954 database must have its conversion table changed. If your client 6is Japanese Windows, whose ANSI code page is Shift-JIS (CCSID 943), you will 6also need to change the DB2 default conversion tables between CCSID 943 and 6Unicode to the Microsoft version. Otherwise, the different clients might store 6the same character using different code points.
To replace the DB2 UDB default conversion table for converting from CCSID 6954 to Unicode, follow these steps:
6To replace the DB2 UDB default conversion tables for converting between 6CCSID 943 and Unicode, follow these steps:
6When using the Microsoft Japanese Windows Shift-JIS code page that is registered 7as the IBM coded character set identifier (CCSID) 943, you might encounter 7the following two problems when converting characters between CCSID 943 and 7Unicode. The potential problem is due to differences between the IBM and Microsoft 7code page conversion tables. To avoid these potential problems, DB2 UDB provides 7the alternate Microsoft conversion tables between CCSID 943 and Unicode, in 7addition to the default IBM conversion tables.
7For historical reasons, over 300 characters in the CCSID 943 code page 7are represented by two or three code points each. The use of input method 7editors (IMEs) and code page conversion tables cause only one of these equivalent 7code points to be entered. For example, the lower case character for Roman 7numeral one 'i' has two equivalent code points: X'EEEF' and 7X'FA40'. Microsoft Windows IMEs always generate X'FA40' when 'i' 7is entered. In general, IBM and Microsoft use the same primary code point 7to represent the character, except for the following 13 characters:
7 7| Character name (Unicode code point) | 7IBM primary Shift-JIS code point | 7Microsoft primary Shift-JIS code point | 7
|---|---|---|
| Roman numeral one (U+2160) | 7X'FA4A' | 7X'8754' | 7
| Roman numeral two (U+2161) | 7X'FA4B' | 7X'8755' | 7
| Roman numeral three (U+2162) | 7X'FA4C' | 7X'8756' | 7
| Roman numeral four (U+2163) | 7X'FA4D' | 7X'8757' | 7
| Roman numeral five (U+2164) | 7X'FA4E' | 7X'8758' | 7
| Roman numeral six (U+2165) | 7X'FA4F' | 7X'8759' | 7
| Roman numeral seven (U+2166) | 7X'FA50' | 7X'875A' | 7
| Roman numeral eight (U+2167) | 7X'FA51' | 7X'875B' | 7
| Roman numeral nine (U+2168) | 7X'FA52' | 7X'875C' | 7
| Roman numeral ten (U+2169) | 7X'FA53' | 7X'875D' | 7
| Parenthesized ideograph stock (U+3231) | 7X'FA58' | 7X'FA58' | 7
| Numero sign (U+2116) | 7X'FA59' | 7X'8782' | 7
| Telephone sign (U+2121) | 7X'FA5A' | 7X'8754' | 7
IBM products such as DB2 UDB primarily use IBM code points, such as X'FA4A' 7to present the upper case Roman numeral one 'I', but Microsoft products 7use X'8754' to represent the same character. An Microsoft ODBC application 7can insert the 'I' character as X'8754' into a DB2 UDB database 7of CCSID 943, and the DB2 UDB Control Center can insert the same character 7as X'FA4A' into the same CCSID 943 database. However, ODBC applications 7can find only those rows that have 'I' encoded as X'8754', 7and DB2 UDB Control Center can locate only those rows that have 'I' 7encoded as X'FA4A'. To enable DB2 UDB Control Center to select 'I' 7as X'8754', you need to replace the default IBM conversion tables 7between CCSID 943 and Unicode with the alternate Microsoft conversion tables.
The following list of characters, when converted from CCSID 943 to Unicode, 7will result in different code points depending on whether the IBM conversion 7table or the Microsoft conversion table is used. For these characters, the 7IBM conversion table conforms to the Japanese Industry Standard JISX0208, 7JISX0212, and JISX0221.
| Shift-JIS code point (character name) | 7IBM primary code point (Unicode name) | 7Microsoft primary code point (Unicode name) | 7
|---|---|---|
| X'815C' (EM dash) | 7U+2014 (EM dash) | 7U+2015 (Horizontal bar) | 7
| X'8160' (Wave dash) | 7U+301C (Wave dash) | 7U+FF5E (Fullwidth tilde) | 7
| X'8161' (Double vertical line) | 7U+2016 (Double vertical line) | 7U+2225 (Parallel to) | 7
| X'817C' (Minus sign) | 7U+2212 (Minus sign) | 7U+FF0D (Fullwidth hyphen-minus) | 7
| X'FA55' (Broken bar) | 7U+00A6 (Broken bar) | 7U+FFE4 (Fullwidth broken bar) | 7
For example, the character EM dash with the CCSID 943 code point of X'815C' 7is converted to the Unicode code point U+2014 when using the IBM conversion 7table. However, it is converted to U+2015 when using the Microsoft conversion 7table. Due to this difference of conversion mapping, you might have two different 7code points for the same character in a DB2 UDB Unicode database. This can 7create potential problems for Microsoft ODBC applications because they would 7treat U+2014 as an invalid code point. To avoid this potential problem, you 7need to replace the default IBM conversion tables between CCSID 943 and Unicode 7with the alternate Microsoft conversion tables.
7The use of the alternate Microsoft conversion tables between CCSID 943 7and Unicode should be restricted to closed environments, where the DB2 UDB 7clients and the DB2 UDB databases all have a code page of CCSID 943 and are 7all using the same alternate Microsoft conversion tables. If you have a DB2 7UDB client using the default IBM conversion tables, and another DB2 UDB client 7using the alternate Microsoft conversion tables, and both clients are inserting 7data to the same DB2 UDB database of CCSID 943, the same character may be 7stored as different code points in the database.
7 7 7When you convert between CCSID 943 and Unicode, the DB2 Universal Database 7(DB2 UDB) default code page conversion tables are used. If you want to use 7a different version of the conversion tables, such as the Microsoft version, 7you must manually replace the default conversion table (.cnv) files.
7Before replacing the existing code page conversion table files in the sqllib/conv directory, you should back up the files 7in case you want to change them back. On UNIX, sqllib/conv is linked to the DB2 UDB installation path.
For conversion table replacement to be effective, every DB2 UDB client 7that connects to the same database must have its conversion table changed. 7 Otherwise the different clients might store the same character using different 7code points.
To replace the DB2 UDB default conversion tables for converting characters 7between CCSID 943 and Unicode:
7Despite being mentioned in the documentation, the MVS(TM) operating system is no longer supported by DB2 Universal Database. MVS has been replaced with z/OS.
5 5 5DB2 UDB Version 8.1.4 and above for AIX Versions 4.3.3 and 5.1 and above 5require installation of the AIX C++ Version 6 Runtime libraries on your AIX 5system. Download the March 2003 C++ Runtime PTF update from the following 5Web site:
5 5| http://www-1.ibm.com/support/docview.wss?rs=0&q=xlC.rte&uid=swg24004427&loc=en_US&cs=utf-8&cc=us&lang=en | 5
Follow the installation instructions given at the previously listed Web 5site before using DB2 Version 8.1.4 or later.
Backup and restore operations to and from multiple tape devices might not work if you are using the Linux 390 operating system.
2 2 2When accessing the Development Center on UNIX with Hummingbird(R) Exceed, 2the XTEST extension version 2.2 must be enabled before you can move and dock 2views by dragging their title bars within the Development Center.
2To enable the XTEST extension:
2