IBM Support

PI22578: ABEND0C4 DSNVDTA FOLLOWING -RECOVER INDOUBT COMMAND. DB2 TERMINATES WITH RC00E50731

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A -RECOVER INDOUBT command can leave a FREE ACE control block
    on the DB2 MSTR ACE chain.  This can result in repeated
    ABEND0C4 abends in DSNVDTA under the monitor task.  This can
    also cause DB2 to terminate with RC00E50731.
    DB2TERM DB2ABTERM
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All Version 11 users of DB2 for zOS.         *
    ****************************************************************
    * PROBLEM DESCRIPTION: ABEND0C4 in DSNVDTA followed by         *
    *                      MSGDSNV509I DSNVMON DB2 MSTR INTERNAL   *
    *                      MONITOR STOPPING and DB2 termination    *
    *                      with RC00E50731 after a -RECOVER        *
    *                      INDOUBT command was issued.             *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    A -RECOVER INDOUBT command was issued to resolve an INDOUBT
    UR from an allied address space (ie. IMS, CICS) before DB2
    was recycled.  While completing thread termination for the
    INDOUBT UR, an invalid pointer was passed on the TERM
    requests resulting in a FREE ACE being left on the DB2
    MSTR ACE chain.  This caused multiple ABEND0C4s in DSNVDTA
    under the DSNVMON monitor task.  After an ABEND/RETRY limit
    was exceeded, MSGDSNV509I DSNVMON - DB2 MSTR INTERNAL MONITOR
    STOPPING was issued and DB2 terminated with RC00E50731.
    This problem does not occur if DB2 is recycled before
    issuing the -RECOVER INDOUBT command, or if INDOUBT resolution
    is done when the Commit Coordinator reconnects to DB2.
    Also, this problem does not apply for Distributed
    Server (DDF DBAT) threads.
    

Problem conclusion

  • The incorrect parameter passing in DSN3RIM0 has been
    corrected.
    

Temporary fix

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

Comments

APAR Information

  • APAR number

    PI22578

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-07-23

  • Closed date

    2014-08-08

  • Last modified date

    2014-09-03

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

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

    UI20372

Modules/Macros

  • DSN3RIM0
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RB10 PSY UI20372

       UP14/08/25 P F408

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

Document Information

Modified date:
03 September 2014