IBM Support

PH01614: V12 AUTOBIND HAPPENS UNEXPECTEDLY.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Db2 V12 autobind happens unexpectedly.
    The primary symptom is an excessive number of (unneeded)
    autobinds which may be experienced as a performance
    degradation or may go unnoticed.  A secondary symptom may
    be timeouts or deadlocks against bind locks. ZSA2
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All Db2 users                                                *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Running a package bound with COMMIT                          *
    * duration could experience unexpected                         *
    * autobind. There could be other                               *
    * unexpected problem when executing a                          *
    * package                                                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply corrective PTF when available                          *
    ****************************************************************
    Db2 has the following code bugs,
    1. When locating a package bound with
       rel(COMMIT)could go to wrong code path.
    2. error handling code is missing
       making Db2 think that the package was
       successfully allocated where in fact that was not the case.
    
    This can result in Db2 incorrectly thinking that an autobind
    operation is needed. If that is the case, customers can expect
    a high number of QTAUTOBA (number of automatic bind attempts
    of a package) but a low number of QTPKABND (number of
    successful automatic bind package operations)
    

Problem conclusion

  • Db2 has been changed such that the correct code path is
    accessed to run a package bound with release(COMMIT) and
    Db2 error handling code is added.
    

Temporary fix

  • *********
    * HIPER *
    *********
    

Comments

APAR Information

  • APAR number

    PH01614

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    C10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-08-14

  • Closed date

    2018-08-28

  • Last modified date

    2018-09-04

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

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

    UI58169

Modules/Macros

  • DSNGEFLC
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RC10 PSY UI58169

       UP18/08/31 P F808 ¢

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":"12.0","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":"12.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
04 September 2018