After JDBC upgrade to 3.50.JC1 onwards, customer who are using Multibyte codeset might received error such as : "FAILED: Fetch statement failed: Encoding or code set not supported. " error -79783
Error message: "FAILED: Fetch statement failed: Encoding or code set not supported. "
JDBC version 3.50.JC1 introduced the following APAR:
JDBC DRIVER ALLOWS INSERTION OF INVALID CHARACTERS FOR CHARACTER SET.
While the behavior for this APAR is correct, it might lead to problems for those customers who use Native Multibyte data on the application side but store them into en_us locale on the server side.
In some case, for customer who are using zh_tw.big5 locale on the server side; but stored illegal characters in the table will also be effected.
Diagnosing the problem
Error message happened right after upgrade.
Resolving the problem
Since version JDBC 3.50.JC5, user can set a flag IFX_USE_STRENC to switch to old style of encoding.
Here's an example on how to use it: