IBM Support

JR31251: IBM DB2 DRIVER FOR JDBC AND SQLJ (JCC) IS NOT ABLE TO SPECIFY ALTERNATE UNICODE CODEPAGE CONVERTER.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • IBM DB2 Driver for JDBC and SQLJ (Jcc driver) is not able to
    specify alternate Unicode codepage converter bacause the driver
    uses codepage converters included in Java runtime instead of
    codepage conversion tables included in DB2 LUW product.
    DB2 JDBC Type 2 Driver (CLI-based Legacy driver) is able to use
    alternate Unicode conversion tables for CCSID 943/5039, 954,
    5026/5035.
    This APAR addresses the compatibility issue by the following new
    global properties.
    .
    Property name           Type    Possible values
    ----------------------- ------- -----------------------
    db2.jcc.ccsid930Mapping Integer 1: Jcc will use Cp930
                                    2: Jcc will use Cp930A
    ----------------------- ------- -----------------------
    db2.jcc.ccsid939Mapping Integer 1: Jcc will use Cp939
                                    2: Jcc will use Cp939A
    ----------------------- ------- -----------------------
    db2.jcc.ccsid943Mapping Integer 1: Jcc will use Cp943C
                                    2: Jcc will use MS932
    ----------------------- ------- -----------------------
    db2.jcc.ccsid954Mapping Integer 1: Jcc will use Cp33722
                                    2: Jcc will use Cp33722A
    The default value for the properties is 1.
    Please note that users need to make sure that the Java virtual
    machine supports alternate converters befor using these
    properties.
    

Local fix

Problem summary

  • Users affected:
    Users who use IBM DB2 Driver for JDBC and SQLJ (com.ibm.jcc.*).
    .
    Problem Description:
    IBM DB2 Driver for JDBC and SQLJ (Jcc driver) is not able to
    specify alternate Unicode codepage converter bacause the driver
    uses codepage converters included in Java runtime instead of
    codepage conversion tables included in DB2 LUW product.
    DB2 JDBC Type 2 Driver (CLI-based Legacy driver) is able to use
    alternate Unicode conversion tables for CCSID 943/5039, 954,
    5026/5035.
    .
    Problem Summary:
    This APAR addresses the compatibility issue by new jcc
    global properties.
    

Problem conclusion

Temporary fix

Comments

  • The new global properties will be available in V9.7 orlater.
    

APAR Information

  • APAR number

    JR31251

  • Reported component name

    DB2 UDB ESE WIN

  • Reported component ID

    5765F4101

  • Reported release

    950

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-12-02

  • Closed date

    2009-05-07

  • Last modified date

    2009-05-07

  • APAR is sysrouted FROM one or more of the following:

    JR31242

  • APAR is sysrouted TO one or more of the following:

Modules/Macros

  • ENGN_JCC
    

Fix information

Applicable component levels

  • R950 PSN

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"950","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
12 October 2021