IBM Support

PH46306: DB2 MONITOR THREADS SYSTEM PROFILE WITH FILTERING CRITERIA OF AUTHID DOES NOT HONOR THE ATTRIBUTE3 VALUE

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • Db2 dsn_system_profile function MONITOR THREADS with a filtering
    criteria of AUTHID does not honor attribute3 value to allow
    queueing.
    Additional keywords and symptoms:
    **********************************
    This is the v13 apar for v12 apar PH42546.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All Distributed Data Facility (DDF) users.                   *
    * Specifically those that use profiles to                      *
    * monitor threads for remote TCP/IP access                     *
    * to a Db2 13 for z/OS server.                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * ATTRIBUTE3 column value of zero is not                       *
    * being honored for MONITOR THREADS                            *
    * profiles.                                                    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply corrective PTF when available                          *
    ****************************************************************
    A Db2 system profile is configured to MONITOR THREADS with an
    ATTRIBUTE1 column value of EXCEPTION and ATTRIBUTE3 column
    (queuing threshold) value of zero. For this profile, when
    the exception threshold is exceeded, the thread should not be
    allowed to wait (queue) and should be rejected by Db2.
    However, when an inactive connection receives an SQL request,
    and that request exceeds the profile exception threshold, Db2
    incorrectly allows the SQL request to wait even though
    ATTRIBUTE3 contains a value of zero.
    

Problem conclusion

  • Db2 13 for z/OS has been changed to honor the ATTRIBUTE3
    column value of zero for SQL requests from inactive
    connections, and reject the connection when this profile
    exception event occurs.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH46306

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    D10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-05-10

  • Closed date

    2022-05-24

  • Last modified date

    2022-06-01

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

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

    UI80682

Modules/Macros

  • DSNLQDIS
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

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

Document Information

Modified date:
06 July 2022