JDBC Driver for SQL/MX Programmer's Reference

Using Character Encoding Sets and
SQL Databases
If your application uses Java character encoding sets and accesses SQL databases, consider the
change in the JDBC/MX V31 and V32 drivers' support of multibyte character sets and how the
change might affect your application.
The JDBC/MX driver now supports the reading and writing of CHAR, VARCHAR,
VARCHAR_LONG, and VARCHAR_WITH_LENGTH data types that utilize a double-byte
character set. The double-byte character sets supported by JDBC/MX are ISO88591, UCS2,
KANJI, and KSC5601.
Previously, String type column data was always encoded using the default character set
encoding, which was typically ISO88591, but KANJI and KSC5061 were also supported.
Now the JDBC/MX driver encodes and decodes String data types as a function of the associated
character set name for the particular SQL table column independent of the default encoding. For
the currently supported character sets, see Multibyte Character Set (MBCS) Support.
Location Change for Installed Files
With the JDBC/MX V30 driver, the driver software was installed to the default location of the
/usr/tandem/java_public_lib directory, which was the public library directory for
NonStop Server for Java 4.
Now for the V31 and V32 products, the JDBC/MX driver must be installed in its own space.
For the current installation location for the JDBC/MX driver, see JDBC/MX Driver File
Locations.
Version of NonStop Server for Java
JDBC/MX requires a version of NonStop Server for Java as follows:
JDBC/MX V30 requires NonStop Server for Java 3.1.1 or subsequent 3.x release
(product number T0083)
●
JDBC/MX V31 requires version 1 of the NonStop Server for Java 4 (product number
T2766), which is based on J2SE SDK 1.4.1 ).
●
JDBC/ MX V32 requires version 2 of the NonStop Server for Java 4 (product number
T2766), which is based on J2SE SDK 1.4.2.
●