IBM Support

PK87487: DGOVHMTC+1CC ABEND0C4-4

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • ABEND0C4-4 DGOVHMTC+1CC (at PK76667 level) on a 50EBF008 (Store)
    instruction.  R11 and R15 were both zeros.  A corrupt Snapshot
    History dataset led to the program check, but nonetheless
    Snapshot History Manager shouldn't ABEND when it tries to load
    a corrupt dataset.
    Also seen at the time of the error:
    IEA995I SYMPTOM DUMP OUTPUT  249
    SYSTEM COMPLETION CODE=0C4  REASON CODE=00000004
     TIME=16.43.45  SEQ=36924  CPU=0000  ASID=00A2
     PSW AT TIME OF ERROR  078D0000   8F91B108  ILC 4  INTC 04
       ACTIVE LOAD MODULE   ADDRESS=0F90B888   OFFSET=0000F880800
       NAME=DGOVHM00
       DATA AT PSW  0F91B102 - 000150EB  F0085810  A0505800
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
    *                 users of component                           *
    *                 - PE Server subtask                          *
    ****************************************************************
    * PROBLEM DESCRIPTION: When the OMEGAMON Collector PE Server   *
    *                      subtask initializes the function        *
    *                      Snapshot History, an already existing   *
    *                      Snapshot History data set is read to    *
    *                      build the table of contents. Reading a  *
    *                      corrupted data set can cause an ABEND   *
    *                      S0C4-004 in module DGOVHM00 at offset   *
    *                      0000F8D0 or others. After Snapshot      *
    *                      History abends, the PE Server subtask   *
    *                      tries to restart the Snapshot History   *
    *                      Manager subtask which fails again       *
    *                      because it tries to read the same       *
    *                      corrupted data set.                     *
    ****************************************************************
    * RECOMMENDATION: Apply this PTF                               *
    ****************************************************************
    PROBLEM SUMMARY:
    During initialization of the Snapshot History Manager an already
    existing Snapshot History data set is read to build the table of
    contents. When corrupted data are read, the processing of the
    data can cause an ABEND S0C4 in load module DGOVHM00. The PE
    Server subtask tries to recover once and therefore restarts the
    Snapshot History Manager. The same corrupted data are read again
    and cause the same ABEND S0C4.
    
    PROBLEM CONCLUSION:
    When the Snapshot History data set is read, the data are checked
    for consistency before they are processed to build the table of
    contents. When inconsistencies are detected, the Snapshot
    History data set is renamed and a new Snapshot History data set
    is allocated to continue the collection of Snapshot History
    data.
    
    KEYWORDS: ABEND S0C4-004 DGOVHM00 SNAPSHOT HISTORY
    

Problem conclusion

  • When the Snapshot History data set is read, the data are checked
    for consistency before they are processed to build the table of
    contents. When inconsistencies are detected, the Snapshot
    History data set is renamed and a new Snapshot History data set
    is allocated to continue the collection of Snapshot History
    data.
    
    KEYWORDS: ABEND S0C4-004 DGOVHM00 SNAPSHOT HISTORY
    

Temporary fix

  • Stop the PE Server subtask, rename an inconsistent Snapshot
    History data set manually and restart the PE Server subtask.
    

Comments

APAR Information

  • APAR number

    PK87487

  • Reported component name

    OM XE DB2PE/PM

  • Reported component ID

    5655OPE00

  • Reported release

    410

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-05-28

  • Closed date

    2009-06-23

  • Last modified date

    2009-08-03

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

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

Modules/Macros

  • DUMM9KO2
    

Fix information

  • Fixed component name

    OM XE DB2PE/PM

  • Fixed component ID

    5655OPE00

Applicable component levels

  • R410 PSY UK47671

       UP09/07/07 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":"SSAV2B","label":"IBM Db2 Buffer Pool Analyzer for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"410","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCT4H5","label":"IBM Tivoli OMEGAMON XE for Db2 PE \/ PM \/ BPA"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"410","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
03 August 2009