IBM Support

PI76344: 0C4-00000038,LOC=DSNXGRDS.DSNX9EOM+01716 WHEN WLM ADDRESS SPACE WENT TO EOM

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • 0c4-00000038,loc=dsnxgrds.dsnx9eom+01716 when WLM address space
    went to EOM
    
    V11 abend ABND=0C4-00000004 LOC=DSNXGRDS.DSNX9EOM+0E56
    
    
    Additional keywords and symptoms:
    ********************************
    0C4-4 DSNXGRDS.DSNX9EOM+0E56
    DSNX9EOM OFFSET0E56
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: DB2 10 and 11 for z/OS                       *
    *                 users of stored procedures and               *
    *                 User Defined Functions (UDFs).               *
    ****************************************************************
    * PROBLEM DESCRIPTION: When WLM application address space      *
    *                      went to EOM (End of Memory), the        *
    *                      following abend may happen:             *
    *                      0C4-00000038,                           *
    *                      LOC=DSNXGRDS.DSNX9EOM+01716             *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When the WLM address space goes to EOM, an 0C4 abend may occur
    during the EOM processing. This is due to a timing window where
    one of the DB2 control blocks may already be freed but it is
    still referenced in the EOM processing without checking whether
    the pointer points to the control block is zero or not. This
    would result in the 0C4 abend.
    

Problem conclusion

  • The code in the stored procedure/UDF EOM processing has
    been modified to check the validity of the pointer before
    referencing the fields in the control block.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI76344

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-02-09

  • Closed date

    2017-03-30

  • Last modified date

    2018-01-22

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

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

    UI46030 UI46031

Modules/Macros

  •    DSNX9EOM
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UI46030

       UP17/04/14 P F704

  • RB10 PSY UI46031

       UP17/04/14 P F704

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:
22 January 2018