IBM Support

PH52584: EXPLAIN MAY FAILS VIA JDBC, POSSIBLY B/C OF X'00' IN SQLID

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When SQLID has a trailing x'00' rather than blank, EXPLAIN seems
    to use this data to find the explain table set. And this
    apparently prevents EXPLAIN (possibly other functions as well)
    from working properly. Please refer to closing text for further
    information.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All Distributed Data Facility (DDF) users.                   *
    * Specifically users of TLS Client                             *
    * Certificate Authorization accessing Db2                      *
    * for z/OS server configured with Broadcom                     *
    * ACF2.                                                        *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * An application connecting to Db2 for                         *
    * z/OS server receives SQLCODE -219 for                        *
    * an SQL EXPLAIN statement.                                    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply corrective PTF when available                          *
    ****************************************************************
    A remote application connects using client certificate
    authorization to a Db2 for z/OS server configured with Broadcom
    ACF2. The application issues an SQL EXPLAIN which fails with
    SQLCODE -219.
    When Db2 queries the AT-TLS information for the connection,
    ACF2 returned a null terminated string for the userid
    associated with the client certificate. Db2 did not process the
    null terminated userid correctly and this value was copied to
    CURRENT SQLID and subsequently CURRENT SCHEMA special
    registers. The null terminated CURRENT SQLID / CURRENT SCHEMA
    values caused the EXPLAIN statement to fail with SQLCODE -219
    because Db2 could not correctly resolve the schema of the
    explain tables.
    NOTE: This issue can affect any SQL statements containing
    unqualified object references and can result in other errors
    such as SQLCODE -204.
    

Problem conclusion

  • Db2 has been changed to correctly pad CURRENT SQLID and CURRENT
    SCHEMA with blanks when a userid associated with a client
    certificate is null terminated.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH52584

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    C10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2023-02-14

  • Closed date

    2023-03-31

  • Last modified date

    2023-05-03

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

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

    UI91237 UI91238

Modules/Macros

  • DSNLIRCA
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RC10 PSY UI91237

       UP23/04/08 P F304

  • RD10 PSY UI91238

       UP23/04/08 P F304

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"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"12.0","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
03 May 2023