Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Why is the Toolbox JDBC returning EBCDIC characters to my Java program?

April 26, 2017characters EBCDIC Java JDBC program returning Toolbox

0

Posted

Why is the Toolbox JDBC returning EBCDIC characters to my Java program?

2 Answers

0

Posted

Normally, the Toolbox JDBC driver will translate EBCDIC characters to Unicode Strings automatically. If it appears to be returning untranslated EBCDIC characters instead, then it is likely that the field in the i5/OS database is tagged with CCSID 65535. The Toolbox JDBC driver recognizes this CCSID as a field that should not be translated. To avoid this behavior, tag fields on the i5/OS that you want to be translated, with a valid CCSID. Alternately, you can set the “translate binary” connection property to “true”, which instructs the JDBC driver to translate all fields, including those tagged with CCSID 65535.

0

Posted

Normally, the Toolbox JDBC driver will translate EBCDIC characters to Unicode Strings automatically. If it appears to be returning untranslated EBCDIC characters instead, then it is likely that the field in the IBM i database is tagged with CCSID 65535. The Toolbox JDBC driver recognizes this CCSID as a field that should not be translated. To avoid this behavior, tag fields on the IBM i that you want to be translated, with a valid CCSID. Alternately, you can set the “translate binary” connection property to “true”, which instructs the JDBC driver to translate all fields, including those tagged with CCSID 65535.