CLI, ODBC, JDBC, and SQLJ programs in a DBCS environment

JDBC and SQLJ programs access Db2® using the CLI/ODBC driver and therefore use the same configuration file (db2cli.ini). If you run Java™ programs that access a Db2 database system in a DBCS environment, add appropriate PATCH1 and PATCH2 parameter values to the db2cli.ini configuration file.
PATCH1 = 65536
Forces the driver to manually insert a "G" in front of character literals that are in fact graphic literals. This PATCH1 value should always be set when working in a double-byte environment.
PATCH1 = 64
Forces the driver to NULL terminate graphic output strings. This PATCH1 value is needed by Microsoft Access in a double-byte environment. If you need to use this PATCH1 value as well, you would add the two values together (64+65536 = 65600) and set PATCH1=65600. See following note 2 for more information about specifying multiple PATCH1 values.
PATCH2 = 7
Forces the driver to map all graphic column data types to char column data type. This PATCH2 value is needed in a double-byte environment.
PATCH2 = 10
Should only be used in an EUC (Extended UNIX Code) environment. This PATCH2 value ensures that the CLI driver provides data for character variables (CHAR, VARCHAR, and so on) in the proper format for the JDBC driver. The data in these character types will not be usable in JDBC without this setting.
Note:
  1. Each of these keywords is set in each database-specific stanza of the db2cli.ini file. If you want to set them for multiple databases, repeat them for each database stanza in db2cli.ini.
  2. To set multiple PATCH1 values, add the individual values and use the sum. To set PATCH1 to both 64 and 65536, set PATCH1=65600 (64+65536). If you already have other PATCH1 values set, replace the existing number with the sum of the existing number and the new PATCH1 values that you want to add.
  3. To set multiple PATCH2 values, specify them in a comma delimited string (unlike the PATCH1 option). To set PATCH2 values 1 and 7, set PATCH2="1,7".