JDBC Type 4 Driver Programmer's Reference for SQL/MX Release 3.2 (H06.25+, J06.14+)

information about column data types and character sets, see the HP NonStop SQL/MX Release
3.2 Reference Manual.
Controlling String Literal Conversion by Using the Character-Set Properties
The Type 4 driver provides character-set mapping properties. These properties allow you to explicitly
define the translation of internal SQL/MX database character-set formats to and from the Java
string Unicode (UnicodeBigUnmarked) encoding.
The Type 4 driver provides the following character-set mapping properties using key values as
follows:
Default ValueKey
ISO88591_1ISO88591
SJISKANJI
EUC_KRKSC5601
A description of these character sets appears in the following table, which summarizes the character
sets supported by SQL/MX.
Table 2 Corresponding SQL/MX Character Sets and Java Encoding Sets
Description
Corresponding JavaEncoding
Set—Canonical Name for java.io and
java.lang APISQL/MX Character Set
Single-character, 8- bit, character set for
character-data type. ISO88591 supports
ISO88591_1ISO88591
English and other Western European
languages.
The multi-byte character set widely used on
Japanese mainframes. KANJI is composed
SJISKANJI
for a single-byte character set and a
double-byte character set. It is a subset of
Shift JIS (the double character portion).
KANJI encoding is big-endian.
NOTE: KAJNI is supported in SQL/MP
tables only.
Double-character character set required on
systems used by government and banking
EUC_KRKSC5601
within Korea. KSC5601 encoding is
big-endian.
NOTE: KSC5601 is supported in
SQL/MP tables only.
For more information on these properties, see the following:
• “ISO88591” (page 42)
• “KANJI” (page 42)
• “KSC5601” (page 42)
Using the Character-Set Properties
The java.sql.PreparedStatement class contains the methods setString() and
setCharacterStream(). These methods take a String parameter and Reader parameter,
respectively.
Internationalization (I18N) Support 29