PK83037: HIGH CPU OMPE SERVER WHEN AUTODETECT = YES KO2XSYS2+2082 OR 2086 ABEND0C4-4

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When the OMPE server is configured with AUTODETECT = YES and
  attaching to a DATA SHARING GROUP, the OMPE server may
  experience high CPU after the agent task is started.  The loop
  is caused by a recursive program check involving an
  ABEND0C4-4 KO2XSYS2+2082 or KO2XSYS2+2086, both offsets involve
  an incorrect value in R7.  KO2XSYS2 is at the PK73189 level.
  KO2XSYS2+2082 on a 5870700C     involves a (LOAD) instruction,
  KO2XSYS2+2086 on a D5037004A7BC involves a (CLC)  instruction.
  Since the RMVT pointer to the z/OS DB2 RMVT in the Omegamon
  control block $TCA is zeros, KO2XSYS2 ABENDs trying to access
  values base on the RMVT.  The real problem is that KO2XSYS2
  shouldn't have been called in this case, it expects that
  pointer and other pointer to DB2 control blocks to be valid.
  

Local fix

• Set AUTODETECT=NO and specify target DB2's to monitor in
  OMPEMSTR.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
  *                 users of component:                          *
  *                 -   PE Server subtask                        *
  *                 -   The component that transfers DB2         *
  *                     monitoring data collected by the         *
  *                     OMEGAMON collector to the TEMA           *
  ****************************************************************
  * PROBLEM DESCRIPTION: A PE Server subtask is started for an   *
  *                      autodetected Group Attach name of a     *
  *                      Data Sharing Group. When a Tivoli       *
  *                      Enterprise Monitoring Agent (Agent)     *
  *                      connects to this PE Server subtask, the *
  *                      Agent might enter a loop and cause high *
  *                      CPU consumption or abend with S0C4.     *
  *                                                              *
  ****************************************************************
  * RECOMMENDATION: Apply this PTF                               *
  ****************************************************************
  PROBLEM SUMMARY:
  When the OMEGAMON Collector PE Server subtask is configured with
  option AUTODETECT activated and a member of a Data Sharing Group
  (DSG) is active, a PE Server subtask is started and connects to
  the Group Attach name of the DSG. In this case the set up of the
  PE Server subtask is not correct. When a Tivoli Enterprise
  Monitoring Agent (Agent) connects to this PE Server subtask, the
  Agent might enter a loop and cause high CPU consumption or
  abend with S0C4.
  
  
  PROBLEM CONCLUSION:
  With option AUTODETECT activated a PE Server subtask will be
  started to monitor a local member of a Data Sharing Group (DSG)
  only if it can explicitely connect to the specific DB2
  subsystem. Autodetected Group Attach names of a DSG are ignored.
  

Problem conclusion

• With option AUTODETECT activated a PE Server subtask will be
  started to monitor a local member of a Data Sharing Group (DSG)
  only if it can explicitely connect to the specific DB2
  subsystem. Autodetected Group Attach names of a DSG are ignored.
  
   The service level of the
   OMEGAMON collector PE Server subtask
   FPEV0000I  DATA SERVER INITIALIZATION
   FPEV0114I  PTF BUILD IS 09.188
  
  KEYWORDS :
  GROUP ATTACH HIGH CPU D5 AGENT KO2ACONB ABEND 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:

  PK93393

Modules/Macros

• DUMM9KO2
  

Fix information

• Fixed component name

  OM XE DB2PE/PM

• Fixed component ID

  5655OPE00

Applicable component levels

• R410 PSN UK41864

     UP09/07/22 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.