IBM Support

PK93065: JCC CLIENTS EXPERIENCE INCORRECT SQLID (-204) ON CONNECTION REUSE WHEN UTILIZING A DB2 LUW GATEWAY

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • DB2DDF DDFL09 defect pk93065 dpk93065
    JCC clients (only JCC) may experience incorrect SQLID
    (SQLCODE204) on connection reuse
    if connecting to DB2 z server through a DB2
    LUW gateway and they are using the same userid and password on
    the connection reuse and they connect within 3 minutes of the
    first connection. See apar PQ99707.
    This special processing for PQ99707 may result
    in the current SQLID not being reset to the primary authid
    when using a gateway for JCC clients. This applies only
    to JCC clients that are connecting through a DB2
    LUW gateway.
    
    Additional keywords and symptoms:
    ****************************************
    DB2DDF 5740XYR00 SQLID JCC
    SQLCODE204 -204 SQL0204N SQL204N SRCN204
    

Local fix

  • JCC clients can avoid the problem by bypassing the DB2 LUW
    gateway and connecting directly to the DB2 z server.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All Distributed Data Facility (DDF) users.   *
    *                 Specifically where remote client systems     *
    *                 using the IBM Data Server Driver for SQLJ    *
    *                 and JDBC access data at a DB2 for z/OS       *
    *                 server via a DB2/LUW gateway server.         *
    ****************************************************************
    * PROBLEM DESCRIPTION: Remote client systems using the IBM     *
    *                      Data Server Driver for SQLJ and JDBC    *
    *                      access data at a DB2 for z/OS server    *
    *                      via a DB2/LUW gateway, but incorrectly  *
    *                      receive SQLCODE -204.                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When a remote client system uses the IBM Data Server driver for
    SQLJ and JDBC to access a DB2 for z/OS server, DB2 gives
    special consideration (for the benefit of performance) by
    skipping the authentication process if the connection is being
    reused with the same security credentials that DB2 successfully
    authenticated for the prior use. However, in this case the
    remote client system connected to DB2 via a DB2/LUW gateway,
    and DB2 failed to recognize that it cannot honor the same JDBC
    performance support to the DB2/LUW gateway.
    Because DB2 failed to recognize the DB2/LUW gateway, DB2
    incorrectly bypassed the authentication process when the
    connection from the DB2/LUW gateway was reused. As a result,
    residual information from the prior use of the connection, such
    as special registers, may be used by the current user of the
    connection and this may lead to unpredictable results.
    In this case, the prior user of the connection had set the
    current SQLID special register to some specific value. The
    connection was then reused and the new user of the connection
    inherited the residual current SQLID value which ultimately led
    DB2 to incorrectly return an SQLCODE -204 because DB2 was
    unable to locate a table object with the incorrect SQLID.
    

Problem conclusion

  • DB2 for z/OS has been changed to correctly identify the
    adjacent remote partner's product level with respect to the
    performance support feature (which is currently available to
    JDBC clients only).
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK93065

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    810

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-08-04

  • Closed date

    2009-09-18

  • Last modified date

    2009-11-04

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

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

    UK50268 UK50269

Modules/Macros

  • DSNDDPSB DSNLTACC DSNLTCM1 DSNLTEXC DSNLTRB1
    DSNLTSEC
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • R810 PSY UK50268

       UP09/10/06 P F910

  • R910 PSY UK50269

       UP09/10/06 P F910

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.



Document information

More support for: DB2 for z/OS

Software version: 8.0

Reference #: PK93065

Modified date: 04 November 2009


Translate this page: