IBM Support

PH11373: DB2 OR IRLM ABENDS RESULTING IN SUBSYSTEM TERMINATION BECAUSE OF STORAGE OVERLAY

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • DB2 may terminate after ABND=04E-00E2000D,LOC=DSNSLD1.DSNSFBK
    or IRLM may terminate with ABENDS0C4 in DXRRL400 when ECSA
    storage for Notify message gets overwritten after the request
    has been cancelled.
    Additional keywords: DB2OVRLAY/K SMCOVERLAY ZSA45
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Db2 for z/OS V11 and V12 users.              *
    ****************************************************************
    * PROBLEM DESCRIPTION: ABND=04E-00E2000D in DSNSFBK, or        *
    *                      ABENDS0C4 in DXRRL400 resulting from    *
    *                      ECSA storage overlay.                   *
    ****************************************************************
    * RECOMMENDATION: Apply corrective PTF when available.         *
    ****************************************************************
    Cancelling a thread running in Db2 which had a Notify request
    sent to IRLM, may result in common storage corruption if the
    request got suspended in IRLM. Db2 Cancel recovery code could
    return the notify message storage back to a storage pool for
    reuse while IRLM may still be processing the request and
    could end up either abending or overwriting the notify message
    storage data. This may result in other threads reusing that
    common storage to receive abends in different locations.
    
    This problem applies to Db2 threads that have been Soft
    Cancelled (i.e. ABEND04E RC00E50013) as well as those
    cancelled via a CANCEL THREAD command.
    

Problem conclusion

  • This APAR closes a timing window with Notify request processing
    in IRLM and thread being cancelled. Db2 will not release the
    Notify message storage (RLPVDATA) in the cancel recovery PRR
    code if the thread was suspended in IRLM. Instead, this storage
    will be released when the thread goes through de-allocation.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH11373

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-04-23

  • Closed date

    2019-07-02

  • Last modified date

    2019-09-23

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

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

    UI64038 UI64041

Modules/Macros

  •    DSNTLDU  DSNTLLDS DSNTLLOC DSNTLQRY
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RB10 PSY UI64041

       UP19/07/20 P F907

  • RC10 PSY UI64038

       UP19/07/17 P F907

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:
23 September 2019