PK93393: 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

• PK93393 is a forward fit of R410 Omegamon APAR PK83037.
  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 ABEND0C4 can occur at two offsets (at the PK87219 level)
  in R420:
  KO2XSYS2+296C on a 5870700C     involves a (LOAD) instruction,
  KO2XSYS2+2086 on a D5037004A6C8 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 RMVT
  pointer and other pointers 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 D5 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 D5 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.
  
  KEYWORDS: GROUP-ATTACH HIGH-CPU D5 AGENT KO2ACONB ABENDS0C4
  

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.
  
  KEYWORDS: GROUP-ATTACH HIGH-CPU D5 AGENT KO2ACONB ABENDS0C4
  

Temporary fix

Comments

APAR Information

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

  PK83037

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

  UK49185

Modules/Macros

• DGOVMSTR DGOVRSFI DGOZCAF
  

Fix information

• Fixed component name

  OM XE DB2PE/PM

• Fixed component ID

  5655OPE00

Applicable component levels

• R420 PSY UK49185

     UP09/08/26 P F908

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.