Introduction to messages

This documentation includes messages for the z/OS®-based components of the IBM® OMEGAMON products and Tivoli® Management Services, such as the Tivoli Enterprise Portal Server, the Tivoli Enterprise Monitoring Server, OMNIMON Base, and the Tivoli Monitoring Services:Engine (TMS:Engine).

Message logging refers to the text and numeric messages created by Tivoli Management Services components and IBM Tivoli OMEGAMON® monitoring agents. These messages relay information about how the system or application is performing and can alert you to exceptional conditions when they occur. Typically, text messages relay information about the state and performance of a system or application. Messages also alert the system administrator to exceptional conditions when they occur. Consult the explanation and operator response associated with the displayed messages to determine the cause of the failure.

Messages are sent to an output destination, such as a file, database, or console screen. Messages are internationalized based on the locale of the originator. If you receive a warning or error message, you can do one of the following:
  • Follow the instructions listed in the detail window of the message, if this is included in the message.
  • Consult the message details in this documentation to see what action you can take to correct the problem.
  • Consult the message log for message ID and text, time and date of the message, as well as other data you can use to diagnose the problem.

Trace data capture transient information about the current operating environment when a component or application fails to operate as designed. IBM Software Support personnel use the captured trace information to determine the source of an error or unexpected condition.

This documentation contains the following types of messages:
Table 1 shows the message prefixes associated with the various components and subcomponents of the Tivoli Management Services environment.
Table 1. Prefixes associated with various Tivoli Management Services components
Component Subcomponent (optional) Associated prefix
Distributed Monitoring product None AMX
Db2® application agent* None KUD*
i5/OS agent* None KA4 *
IBM Tivoli Monitoring Hot standby feature KQM
Link wizard KJR
Remote deployment KDY
Storage allocation and alert. Situations and take action commands. KFA
Server shutdown KMS
Situation, data queues, and policies. Startup processing. Configuration errors. Global directory server. KO4
User interface (both the tacmd command line and displayed messages) and the import and exports of policies and situations. KUI
Installation and Configuration Configuration Manager or PARMGEN KCI, KOB
UNIX Installation KCI
Monitoring agents None KRA
MSSQL application agent* None KOQ*
Migration Toolkit command line and graphical user interfaces None AMK
OMEGAVIEW None KLM, KOS, KSD
Oracle application agent* None KOR*
SAP application agent* None KSA*
Sybase application agent* None KOY*
Tivoli Enterprise Console Rules Check Utility ECO
Forwarding of situation updates from the TEC Event server back to the hub Tivoli Enterprise Monitoring Server KFAIT
Tivoli Enterprise Monitoring Server All platforms KDC, KDS, KFA. KMS. KO4, KQM
TMS:Engine (z/OS only) KBB, KDH, KLB, KLE, KLU, KLV, KLX
Tivoli Enterprise Portal Server None KFW
Tivoli Universal Agent None KUM
UNIX OS agent* None KUX
Windows OS agent* None KNT
z/OS-only components
Classic OMEGAMON None IA, IN, LSC
OMEGAMON Base None CI, CND, CS, CT, KOB, OB, OM
OMEGAMON Enhanced 3270 User Interface None KOB
OMNIMON Base Coupling facility KCN
Persistent data store None KPD, KPQ
*Documented in the IBM Tivoli Monitoring: Upgrading from IBM Tivoli Monitoring V5.1.2.