Messages

Each component involved in OMEGAMON® Data Provider writes messages that describe activity or errors.

Message location and prefix by component

Component Message location Message prefix
Data source: OMEGAMON monitoring agents

Other data sources: see the separate documentation for that software

 RKLVLOG output data set of the corresponding job for the agent.

For example, for attributes from IBM Z® OMEGAMON AI for z/OS®: the monitoring server job (default job name: OMEGDS).

 KAYL, KPQD, KPQH
OMEGAMON Data Broker SYSPRINT output data set of the Zowe™ cross-memory server job that runs OMEGAMON Data Broker or, for some messages, the z/OS system log.

The Zowe cross-memory server also writes its own messages, with the prefix ZWES. For details, see the message descriptions in the Zowe documentation.

 KAYB
OMEGAMON Data Connect STDOUT file.

If you are running OMEGAMON Data Connect as a z/OS job: the STDOUT output data set of that job.

 KAYC

Message format

Each OMEGAMON Data Provider message begins with an identifier in the following format:

KAYxnnnns

or

KPQxnnns

where:

KAYx
Identifies the origin of the message as one of the following components:
KAYL
OMEGAMON historical collection task. See also KPQx.
KAYB
OMEGAMON Data Broker.
KAYC
OMEGAMON Data Connect.
KPQx
Identifies the origin of the message as a historical collection task (x: D or H).
nnnn or nnn
4-digit or 3-digit message identification number.
s
Severity of the message:
I
Informational.
W
Warning to alert you to a possible error condition.
E
Error.

The documentation for each message includes the following information:

Explanation
Describes what the message text means, why the message occurred, and what its variables represent.
System action
Describes what the system will do in response to the event that triggered this message.
User response
Describes whether a response is necessary, what the appropriate response is, and how the response will affect the system or program.