IBM Support

JR27396: ENHANCEMENTS MADE TO JDBC UNIVERSAL DRIVER TO SUPPORT ZOS CLIENT RE-ROUTE FEATURE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • This APAR will provide enhancements to the DB2 for z/OS client
    re-route feature to the JDBC Universal driver.
    .
    With sysplex routing off, the driver will attempt to connect to
    an alternate member if the primary member fails.  However, the
    server list returned from the alternate member will not contain
    the primary member (if the primary member is still down at the
    time the connection is made to the alternate member) thus when
    the alternate member goes down, the driver is not able to
    re-route back to the primary member even if the primary member
    is back up.  Enhancements have been to the JDBC Universal driver
    as it now has more ways to re-route the connection to an
    available member.
    .
    In addition, special registers were not re-established following
    a connection re-route.  Enhancements have been made such that
    the driver will attempt to re-establish special register
    settings, and a reason code returned with the client re-route
    exception (-4498) indicates whether special registers are
    successfully re-established.
    .
       -4498 A connection failed but has been re-established. The
    host name or IP address is <host-name> and the service name or
    port number is <port>.  Special registers modification
    indicator: rc.
    .
       Explanation: host-name and port indicate the data source at
    which the connection is reestablished.  rc indicates whether
    SQL statements that set special register values were executed
    again:
    .
       1 - SQL statements that set special register values were
    executed again.
       2 - Some SQL statements that set special register values may
    have been executed again.
    .
    For client reroute against DB2 for z/OS&#65449; servers, special
    register values that were set after the last commit point are
    not re-established.
    .
    The application is rolled back to the previous commit point.
    

Local fix

Problem summary

  • Users Affected:  DB2 JCC users
    Problem Description:
    This APAR will provide enhancements to the DB2 for z/OS client
    re-route feature to the JDBC Universal driver.
    

Problem conclusion

  • First fixed in DB2 UDB Version 9.1, Fixpak 4
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR27396

  • Reported component name

    DB2 CEE WINDOWS

  • Reported component ID

    5765F3001

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2007-09-05

  • Closed date

    2009-11-09

  • Last modified date

    2009-11-09

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

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

Fix information

  • Fixed component name

    DB2 CEE WINDOWS

  • Fixed component ID

    5765F3001

Applicable component levels

  • R910 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":"910","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
12 October 2021