PK54600: DGOVM000+027640, DB2 TERMINATION, BAD ECB POST

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Problem occurred during STOP DB2 MODE(FORCE).
  Logrec shows several ABEND04F prior to DB2 termination
  rc00E80140.
  ABENDA78 ABEND0C4 ABEND202 (POST)
  SA78 RC1C FPEV0552S
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
  *                 users of component                           *
  *                 - PE Server                                  *
  ****************************************************************
  * PROBLEM DESCRIPTION: When the OMEGAMON Server subtask        *
  *                      PESERVER is monitoring a DB2 subsystem  *
  *                      and the DB2 subsystem is stopped, the   *
  *                      DB2 tasks might terminate abnormal      *
  *                      with ABEND S04F because a bad DB2       *
  *                      termination ECB provided by PESERVER is *
  *                      posted.                                 *
  *                      When PESERVER Snapshot History          *
  *                      monitoring is running and a system or   *
  *                      I/O error is detected while snapshot    *
  *                      data are written to the Snapshot        *
  *                      History VSAM data set, the Snapshot     *
  *                      History subtask might terminate         *
  *                      abnormal with ABEND SA78 and S0C4.      *
  ****************************************************************
  * RECOMMENDATION: Apply this PTF                               *
  ****************************************************************
  PROBLEM SUMMARY:
  When the OMEGAMON Server subtask PESERVER is monitoring a DB2
  subsystem and the DB2 subsystem is stopped, the DB2 tasks might
  terminate abnormal with ABEND S04F because a bad DB2 termination
  ECB provided by PESERVER is posted.
  When PESERVER Snapshot History monitoring is running and a
  system or I/O error is detected while snapshot data are written
  to the Snapshot History VSAM data set, the Snapshot History
  subtask might terminate abnormal with ABEND SA78 and S0C4.
  
  PROBLEM CONCLUSION:
  The PESERVER code has been corrected to adequately handle the
  DB2 start and stop ECB and I/O errors during write operation to
  the Snapshot History data set.
  
  KEYWORDS:
  DB2 TERMINATION ABEND S04F REASON 00E80140 DGOVHM00 SA78 S0C4
  

Problem conclusion

• The PESERVER code has been corrected to adequately handle the
  DB2 start and stop ECB and I/O errors during write operation to
  the Snapshot History data set.
  
  KEYWORDS:
  DB2 TERMINATION ABEND S04F REASON 00E80140 DGOVHM00 SA78 S0C4
  

Temporary fix

Comments

APAR Information

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

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

  UK32878 014PC3Ÿ 014PC3Ÿ UK32879 014PC3Ÿ

Modules/Macros

•    DGO@DB2I DGOVCCP  DGOVDB2I DGOVEE00 DGOVHMS1
  DGOVHM00 DGOVMSTR DGOVM000
  

Fix information

• Fixed component name

  OM XE DB2PE/PM

• Fixed component ID

  5655OPE00

Applicable component levels

• R310 PSY UK32878

     UP08/01/11 P F801

• R410 PSY UK32879

     UP08/01/11 P F801

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.