IBM Tivoli Monitoring, Version 6.3

Introduction to messages

This guide documents messages for the distributed and z/OS®-based components of the IBM® Tivoli® Monitoring Version product, such as the Tivoli Enterprise Portal Server, the Tivoli Universal Agent, Tivoli Enterprise Monitoring Server (both on distributed platforms and on z/OS), OMNIMON Base, and the Tivoli Monitoring Services/Engine (TMS/engine).

You can use this guide in conjunction with IBM Tivoli Monitoring: Problem Determination Guide and the other books in the IBM Tivoli Monitoring library to better understand messages that you receive while running IBM Tivoli Monitoring. A complete list of IBM Tivoli Monitoring books is found in the IBM Tivoli Monitoring and OMEGAMON XE: Documentation Guide (SC23-8816-00).

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 listed in this chapter 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 book contains three 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 Tool	KCI
Installation and Configuration	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
Tivoli Enterprise Console®	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
Tivoli Enterprise Monitoring Server	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, OB, OM
OMNIMON Base	Coupling facility	KCN
Persistent data store	None	KPD
*Documented in the IBM Tivoli Monitoring: Upgrading from IBM Tivoli Monitoring V5.1.2.

Feedback