PM03898: KO2XSYS2 OFFSET +20FE RECURSIVE ABENDS0C4 HIGH CPU RECOVERY LOOP

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Recoverable (repeating) ABEND0C4 in KO2XSYS2+20FE at PK73189
  level.
  
  With AUTODETECT=Y, the high CPU persists and the views showed no
  data, not getting any DB2 data in the TEP workspaces.
  
  The RMVT pointer in the TCAE is zeros. This is causing
  recoverable (repeating) abends in module XSYS and routine
  SYTRACST routine.
  
  FYI.
  -ICPU  TCB(*) HOT
   +<.:  %CPU UTILIZATION (TCB)
  |----+---20---+---40---+---60---+---80---+---100
   +  55 009C8848 KO2ACONB  98.72
  |===========================================>
   +  29 009AE7D0 FPEZPMS     .58 |>
   +  43 009CF118 FPEZPMS     .25 |>
   +  52 009CFBF8 FPEVDB2I    .16 |>
   +  35 009B47F0 DGOVHM00    .16 |>
   +  38 009CE488 FPEVDB2I    .09 |>
   +  13 009D5970 DGOVMSTR    .01 |>
   +  50 009C4088 DGOVUM00    .00 |
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
  *                 users of component:                          *
  *                 -   OMEGAMON collector                       *
  *                 -   The component that transfers DB2         *
  *                     monitoring data collected by the         *
  *                     OMEGAMON collector to the TEMA           *
  *                 -   Classic Interface                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: Intermittent HIGH CPU condition when    *
  *                      connected to a Remote DB2 subsystem.    *
  ****************************************************************
  * RECOMMENDATION: Apply this PTF                               *
  *                                                              *
  ****************************************************************
  PROBLEM SUMMARY:
  1. Common collector connection to a remote DB2 causes High CPU
  conditions.
  2. DB2 subsystem "not active" condition causes error recovery
  loop
  
  PROBLEM CONCLUSION:
  1. Common Collector will not establish a remote DB2 connection.
  2. Correct the IFNODB2 process to properly handle a DB2 SSN
  which is currently terminating.
  

Problem conclusion

• 1. Common Collector will not establish a remote DB2 connection.
  2. Correct the IFNODB2 process to properly handle a DB2 SSN
  which is currently terminating.
  
  KEYWORDS : DB2 CONNECTION  DB2 SSN HIGH CPU REMOTE DB2
  

Temporary fix

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

Comments

APAR Information

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

  PK98483

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

  UK58083

Modules/Macros

• KO2HSVPB KO2OCMCB KO2OINTB KO2ORCVB
  

Fix information

• Fixed component name

  OM XE DB2PE/PM

• Fixed component ID

  5655OPE00

Applicable component levels

• R420 PSY UK58083

     UP10/07/01 P F006

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.