OMEGAMON attributes not arriving at OMEGAMON Data Broker or PDS
Symptoms
The address space where an OMEGAMON® collection task is running (typically, the monitoring agent address space) is missing one or both of the following expected messages for a table (attribute group):- KPQH037I
- Reports that the collection task has written attributes to the OMEGAMON persistent data store (PDS).
- KPQH038I
- Reports that the collection task has sent attributes to OMEGAMON Data Broker.
Causes
- The historical data collection for this table might not be correctly configured in OMEGAMON.
- The table might not be correctly specified in the OMEGAMON Data Provider collection configuration member, RKANPARU(KAYOPEN).
- The monitoring agent might require additional configuration to collect this table.
Resolving the problem
- Check that the historical data collection for this table has been created and activated (distributed).
- Check that there is a corresponding entry in RKANPARU(KAYOPEN) for this table. Check that the entry selects the collection interval specified for the collection.
- Check whether the monitoring agent requires additional configuration to collect this table. For
details, see the monitoring agent documentation.
Some examples (not comprehensive):
- If the issue is not resolved, contact IBM Software Support.