You can specify the character set to use in your application by setting the CHARSET driver property. If you do not set the CHARSET property:
For JCONNECT_VERSION = 2, jConnect uses iso_1 as the default character set.
For JCONNECT_VERSION = 3, and later, jConnect uses the default character set of the database, and adjusts automatically to perform any necessary conversions on the client side.
For jConnect versions starting with 6.05, if jConnect cannot successfully convert the user data to the negotiated charset, it will send unconverted unicode characters to the server, if the server supports the unicode characters, else it will throw an exception.
You can also use the -J charset command line option for the IsqlApp application to specify a character set.
To determine which character sets are installed on your Adaptive Server, issue the following SQL query on your server:
select name from syscharsets go
For the PureConverter class, if the designated CHARSET does not work with the client Java Virtual Machine (VM), the connection fails with a SQLException, indicating that you must set CHARSET to a character set that is supported by both Adaptive Server and the client.
When the TruncationConverter class is used, character truncation is applied regardless of whether the designated CHARSET is 7-bit ASCII or not. Therefore, if your application needs to handle non-ascii data (for instance any asian languages), you should not use TruncationConverter, as this causes data corruption.
