IBM Support

OMEGAMON Messaging high cpu

Question & Answer


Question

Why is my OMEGAMON Messaging on z/OS agent using so much CPU?

Answer

There is an issue that results in high CPU when the framework vector table holding events is too small. This can occur when an agent is monitoring many queue managers and the event table fills up.

RESOLUTION: Change KMQSYSIN member in hilev.rkanparu to add EVENTS(9)

This increases the size of the events table to make it large enough to hold the outstanding timers for all the monitored queue managers.

Below is a description of the keyword and its meaning:

EVENTS specifies the size of the MVS EVENTS tables used by ITM/Engine.

Syntax

EVENTS(8 | nn) Parameters

where nn is the number of entries in the MVS EVENTS table used by the CT/Engine dispatcher, specified as a power of 2. The default of 8 requests 256 entries.

The EVENTS table contains entries for "external" (MVS) ECBs. Each entry is active just for the length of time it is waiting to be posted.

Aimee Benfield - OMEGAMON Support

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SS5G2P","label":"IBM OMEGAMON for Messaging for z\/OS"},"Platform":[{"code":"PF035","label":"z\/OS"}],"Component":"","Version":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
16 February 2018

UID

dwa1370347