IBM Support

PK41236: DB2 Z/OS SYSPLEX SUPPORT FOR IBM DATA SERVER DRIVER FOR JDBC AND SQLJ WITH KEEPDYNAMIC=YES SPECIFIED

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • DB2DDF DDFL09 DB2INACTIVE defect pk41236 dpk41236
    ZIIP/K D/T2096 D/T2094 D/T2817 D/T2818
    DB2 z/OS Sysplex support for IBM Data Server Driver for JDBC
    and SQLJ Type4 client applications with KeepDynamic=Yes and
    enableSysplexWLB=true specified.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All Distributed Data Facility (DDF) users.   *
    *                 Specifically where the IBM Data Server       *
    *                 Driver for JDBC and SQLJ (version 3.51.x/    *
    *                 4.1.x or better) type 4 connectivity, with   *
    *                 the "keepDynamic" and "enableSysplexWLB"     *
    *                 DB2BaseDataSource properties enabled, are    *
    *                 used to access a DB2 for z/OS data           *
    *                 sharing group.                               *
    ****************************************************************
    * PROBLEM DESCRIPTION: The following conditions are reported:  *
    *                       . DB2 for z/OS server support for IBM  *
    *                         Data Server Driver for JDBC and SQLJ *
    *                         type 4 connectivity with             *
    *                         "keepDynamic" and "enableSysplexWLB" *
    *                         DB2BaseDataSource properties         *
    *                         enabled.                             *
    *                       . During Stop DDF quiesce processing   *
    *                         at a DB2 for z/OS V8 system, remote  *
    *                         client connections may not be        *
    *                         terminated properly. This causes     *
    *                         remote client connections to hang.   *
    *                       . Some IBM Data Server Drivers for     *
    *                         JDBC and SQLJ clients connecting to  *
    *                         a DB2 for z/OS data sharing group    *
    *                         may not benefit from z/OS V1R9.0     *
    *                         (or better) WLM sysplex routing      *
    *                         services with zIIP awareness.        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The following conditions are reported:
     . The IBM Data Server Driver for JDBC and SQLJ Type 4 client
       systems (version 3.51.x/4.1.x or better) has a feature which
       supports the specification of the datasource properties
       "keepDynamic" and "enableSysplexWLB" to be enabled for
       connections to a DB2 for z/OS data sharing group. DB2 z/OS
       must be enhanced to support this client feature.
     . During Stop DDF quiesce processing at a DB2 for z/OS V8
       system, if a combination of active and inactive server
       threads are detected, DB2 will attempt to terminate the
       inactive server threads and Stop DDF quiesce processing will
       wait (suspend) until the last remaining active server thread
       completes before Stop DDF processing completes. In this
       situation, during DB2 server thread deallocation processing
       (for those inactive server threads that are being terminated
       by DB2), DB2 fails to immediately close the connection
       between the server and the client. As a result, the remote
       client connection may remain connected with the server (for
       an indefinite period of time) until Stop DDF processing
       completes.
        NOTE: This problem only occurs at a DB2 for z/OS V8 system.
          It does not occur at a DB2 9 for z/OS (or better) system
          because certain specific (DB2 9 for z/OS) internal design
          changes related to Stop DDF processing prevents this
          problem from occurring.
     . When an IBM Data Server Driver for JDBC and SQLJ client
       connects to a DB2 for z/OS data sharing group using the DB2
       member's location alias name and its specific IP address,
       the client may not benefit from receiving a sysplex routing
       server list with weights that may account for the presence
       of zIIP specialty engines if the DB2 data sharing group is
       running at z/OS V1R9.0 or better.
    

Problem conclusion

Temporary fix

Comments

  • The following changes have been made:
     . DB2 for z/OS has been enhanced to provide the necessary
       support for the IBM Data Server Driver for JDBC and SQLJ
       Type 4 client systems when both the "keepDynamic" and
       "enableSysplexWLB" datasource properties are enabled.
        NOTE: This APAR only affects those remote client
         applications which enable both the IBM Data Server Driver
         for JDBC and SQLJ "keepDynamic" and "enableSysplexWLB"
         datasource properties. All others are not affected.
     . DB2 for z/OS has been changed to ensure the proper
       termination of the server connection with the remote
       client during server thread deallocation processing.
     . DB2 for z/OS sysplex routing server list processing has been
       changed to always return a sysplex routing server list that
       considers CPU and zIIP weights if DB2 is running at
       z/OS V1R9.0 or better.
    ž**** PE09/06/29 FIX IN ERROR. SEE APAR PK89820  FOR DESCRIPTION
    

APAR Information

  • APAR number

    PK41236

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    810

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2007-03-14

  • Closed date

    2008-10-16

  • Last modified date

    2011-07-21

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

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

    UK40814 UK40815

Modules/Macros

  • DSNDDPSB DSNLAGNT DSNLQCTL DSNLSSST DSNLTACC
    DSNLTCM1 DSNLTEXC DSNLTRB1 DSNLZS00
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • R810 PSY UK40814

       UP08/11/01 P F810

  • R910 PSY UK40815

       UP08/11/01 P F810

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
21 July 2011