Tivoli IBM Tivoli Monitoring


Version 6.1.0

Problem Determination Guide

GC32-9458-00
 Tivoli IBM Tivoli Monitoring
®


Version 6.1.0

Problem Determination Guide

GC32-9458-00
 Note
Before using this information and the product it supports, read the information in Appendix F, “Notices,” on page 239.

First Edition (November 2005)

This edition applies to IBM Tivoli Monitoring 1st Edition and to all subsequent releases and modifications until
otherwise indicated in new editions.
© Copyright International Business Machines Corporation 2005. All rights reserved.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
About this guide . . . . . . . . . . vii OS Agent does not install and a message
Who should read this guide . . . . . . . . . vii indicates it was already installed . . . . . . 27
Publications . . . . . . . . . . . . . . vii An IBM Tivoli Monitoring 6.1 upgraded agent is
IBM Tivoli Monitoring library . . . . . . . vii not configured to point to the same Tivoli
Accessing terminology online . . . . . . . viii Enterprise Monitoring Server as it was before
Accessing publications online . . . . . . . viii upgrading the agent . . . . . . . . . . 29
Ordering publications . . . . . . . . . . ix After upgrading to IBM Tivoli Monitoring V6.1,
Accessibility . . . . . . . . . . . . . . ix the link to the Queue Statistics workspace in the
Tivoli technical training . . . . . . . . . . ix navigation tree is incorrect . . . . . . . . 29
Support information . . . . . . . . . . . ix Some rows do not display in an upgraded table 29
Conventions used in this guide . . . . . . . . ix Tivoli Enterprise Monitoring Server and Tivoli
Typeface conventions . . . . . . . . . . x Enterprise Portal Server automatically start after
Tivoli command syntax . . . . . . . . . . x running Application Support Installer . . . . 29
Errors occur during installation of Event IBM
Chapter 1. Introduction to problem Tivoli Monitoring Event Forwarding tool . . . 30
Windows installation problems and resolutions . . 30
determination . . . . . . . . . . . . 1 When running the setup.exe, an unknown
Sources of problem determination information . . . 1 publisher error message displays . . . . . . 30
Collecting data . . . . . . . . . . . . . 1 The error "Could not open DNS registry key"
Problem classification . . . . . . . . . . . 4 occurs . . . . . . . . . . . . . . . 30
Finding release notes . . . . . . . . . . . 4 Agent not connecting to Tivoli Enterprise
Viewing Technotes . . . . . . . . . . . 4 Monitoring Server . . . . . . . . . . . 30
Creating an e-mail subscription to Technotes. . . 4 InstallShield displays the error "1607: Unable to
install InstallShield Scripting Runtime" during
Chapter 2. Diagnostic tools . . . . . . 7 installation on Windows from a
Trace logging . . . . . . . . . . . . . . 7 network-mounted drive . . . . . . . . . 30
Installation log files . . . . . . . . . . . 10 Installation on a Windows 2003 server fails with
Upgrading from Tivoli Distributed Monitoring Error Number: 0x80040707 . . . . . . . . 31
log file . . . . . . . . . . . . . . . 11 Upgrade tool deploys agent to the wrong
Reading RAS1 logs . . . . . . . . . . . 12 directory . . . . . . . . . . . . . . 31
Setting traces . . . . . . . . . . . . . 13 UNIX-based system installation problems and
Using the IBM Tivoli Monitoring Service Console . 19 resolutions. . . . . . . . . . . . . . . 31
Starting the IBM Tivoli Monitoring Service Failed to attach to the DB2 instance db2inst1
Console. . . . . . . . . . . . . . . 19 ERROR: Unable to create TEPS, return code = 3 . 31
Blocking access to the IBM Tivoli Monitoring Silent install on UNIX-based systems of Tivoli
Service Console . . . . . . . . . . . . 21 Enterprise Monitoring Server returns an
Displaying tasks in the command prompt . . . . 22 encryption key setting error . . . . . . . . 32
Clearing the JAR cache . . . . . . . . . . 23 The error "Unexpected Signal: 4 occurred at
Using the UAGENT application . . . . . . . 23 PC=0xFEC3FDE4" occurs during installation . . 32
DPLOG . . . . . . . . . . . . . . . 23 Installation of the IBM Tivoli Monitoring on the
ACTION workspace . . . . . . . . . . 24 Linux S390 R2.6 64-bit operating system fails
with the message "LINUX MONITORING
Chapter 3. Installation and AGENT V610Rnnn unable to install agent" where
configuration troubleshooting . . . . . 25 nnn is the release number . . . . . . . . 32
Frequently asked questions . . . . . . . . . 25 The Unix OS agent (ux) version 350 does not
General installation frequently asked questions 25 start on AIX 5.3 after upgrading other agents to
Windows installation frequently asked questions 26 version 6.1.0 . . . . . . . . . . . . . 33
UNIX-based systems installation frequently asked Troubleshooting z/OS-based installations . . . . 33
questions . . . . . . . . . . . . . . 26 IBM Tivoli Monitoring z/OS initialization
General installation problems and resolutions . . . 27 checklist . . . . . . . . . . . . . . 33
Incorrect behavior after an uninstallation and z/OS-based installations problems and
re-installation . . . . . . . . . . . . . 27 resolutions. . . . . . . . . . . . . . 40
The agent installation log on the endpoint Uninstallation problems and workarounds . . . . 45
indicates that error AMXUT7502E occurred . . . 27 Removing a failed installation on Windows . . . 45
Incorrect behavior after an uninstallation and
reinstallation . . . . . . . . . . . . . 49

© Copyright IBM Corp. 2005 iii

 IBM Tivoli Data Warehouse database does not The Tivoli Enterprise Portal displays erratic sorting
uninstall . . . . . . . . . . . . . . 49 behavior when removing more than one managed
The agent installation log on the endpoint system simultaneously. . . . . . . . . . . 62
indicates that error AMXUT7512E occurred . . . 49 Multiple events that occur at the same time are
loaded too slowly . . . . . . . . . . . . 62
Chapter 4. Connectivity Desktop client performs poorly after installing
troubleshooting . . . . . . . . . . . 51 Language Packs for IBM Tivoli Monitoring V6.1. . . 62
Existing OMEGAMON product imagery displays
The Tivoli Enterprise Portal Server does not start
after upgrading to IBM Tivoli Monitoring V6.1 . . 63
after installation . . . . . . . . . . . . . 51
Cannot log in to the Tivoli Enterprise Portal . . . 51
Cannot connect to Tivoli Enterprise Portal Server . . 52 Chapter 6. Tivoli Enterprise Portal
Cannot launch the Tivoli Enterprise Portal on an XP Server troubleshooting . . . . . . . . 65
computer after installation with the message Tivoli Enterprise Portal Server performance is slow 65
KFWITM215E . . . . . . . . . . . . . 54 Corba user exception is included in the Tivoli
Tivoli Enterprise Portal Server is initializing and is Enterprise Portal Server log when creating situations 65
not ready for communications . . . . . . . . 55
Tivoli Enterprise Portal Server lost contact with the Chapter 7. Tivoli Enterprise Monitoring
Tivoli Enterprise Monitoring Server and is Server troubleshooting . . . . . . . . 67
attempting to reconnect . . . . . . . . . . 55
Troubleshooting Tivoli Enterprise Monitoring Server
Tivoli Enterprise Portal Server is unavailable . . . 55
problems on distributed systems . . . . . . . 67
Tivoli Enterprise Portal Server is not reconnecting 55
Remote Tivoli Enterprise Monitoring Server lost
Cannot reconnect to the Tivoli Enterprise
connection to the hub Tivoli Enterprise
Monitoring Server . . . . . . . . . . . . 55
Monitoring Server and all agents display offline . 67
Tivoli Enterprise Portal Server cannot connect to the
The addSystem command fails with error
Tivoli Enterprise Monitoring Server private interface 56
message KUICCR099E . . . . . . . . . . 67
The listSystems command consumes high CPU in
Chapter 5. Tivoli Enterprise Portal enterprise environments . . . . . . . . . 68
troubleshooting . . . . . . . . . . . 57 The configureSystem command does not return
Cannot launch the Tivoli Enterprise Portal help . . 57 an informational error when incorrect parameters
Help index and search text entry fields are disabled 57 are specified . . . . . . . . . . . . . 68
On Linux, IBM Tivoli Enterprise Monitoring Agent Log indicates Hub Tivoli Enterprise Monitoring
topics do not display in the Help Contents or Index Servers are down when they are up . . . . . 68
tabs . . . . . . . . . . . . . . . . . 57 Tivoli Enterprise Monitoring Server does not
Tivoli Enterprise Portal Navigator items are listed in release memory after running a large SQL query . 69
an unexpected order . . . . . . . . . . . 58 Tivoli Enterprise Monitoring Server aborts
HEAPDUMPs and JAVACore files are placed on the unexpectedly when exiting the telnet session
desktops when running Tivoli Enterprise Portal in used to start it . . . . . . . . . . . . 69
browser mode . . . . . . . . . . . . . 58 Troubleshooting Tivoli Enterprise Monitoring Server
Java errors occur with the IBM V1.4.2 JRE . . . . 58 problems on z/OS systems . . . . . . . . . 69
Tivoli Enterprise Portal has high memory usage and The Tivoli Enterprise Monitoring Server start task
poor response time . . . . . . . . . . . . 58 (CANSDSST default) encountered error message
Tivoli Enterprise Portal has high memory usage . . 59 'KLVST044 LOADLIST MEMBER NOT FOUND
Data is not returned to the Tivoli Enterprise Portal IN RKANPAR DATASET (KDSLLIST) KppLLIST
client . . . . . . . . . . . . . . . . 60 KLVST001 CANDLE ENGINE INITIALIZATION
DirectDraw thread loops infinitely causing poor ERROR(S), ABEND U0012' in the RKLVLOG at
Tivoli Enterprise Portal performance . . . . . . 60 startup . . . . . . . . . . . . . . . 70
Workflow Editor is disabled and the following tools Cannot encrypt text. A call to CSNBSYE failed.
do not display: Event Console, Graphic View, Edit Cannot encrypt contents of keyfile . . . . . . 70
Navigator View (Navigator view toolbar). . . . . 60 The error ″KLVST005 MVS JOBSTEP
Situations are not firing . . . . . . . . . . 61 AUTHORIZATION REQUIRED KLVST001
kshsoap client fails because of missing libraries on CANDLE ENGINE INITIALIZATION ERROR(S),
UNIX-based systems . . . . . . . . . . . 61 ABEND U0012 CSV019I - Required module
Category and Message field of the universal KLVSTWTO not accessed, it is not APF
message does not accept DBCS . . . . . . . . 61 Authorized (RKANMODL) CSV028I - ABEND
An error occurs when remotely removing an 306-0C″ occurs in the z/OS Tivoli Enterprise
instance on Windows . . . . . . . . . . . 61 Monitoring Server RKLVLOG during startup . . 71
Agents display offline in the Tivoli Enterprise Portal The error ″KLVSQ000 carved mode in effect for
but still fire situations and the agent logs are report extended storage″ occurred in the RKLVLOG
that they are running . . . . . . . . . . . 62 during startup . . . . . . . . . . . . 71

iv IBM Tivoli Monitoring: Problem Determination Guide

 Error message 'KDSMA013 OPEN VTAM for Universal Agent-emitted traps are not received
VDM1APPL failed with status 8' occurs in the by third-party SNMP Manager . . . . . . . 86
Tivoli Enterprise Monitoring Server start task The NETWORK workspace is empty . . . . . 87
(CANSDSST default) . . . . . . . . . . 71 A MIB workspace is not showing expected data 87
Take Action > Manage Start or Take Action >
Chapter 8. Tivoli Enterprise Monitoring Manage Stop is not working . . . . . . . . 87
Agent troubleshooting . . . . . . . . 73 The SNMP Data Provider does not start with
IBM Tivoli Universal Agent . . . . . . . . 87
Agent deploy operations are not completing before
You do not see the TakeAction options . . . . 88
the TIMEOUT expires . . . . . . . . . . . 73
A managed system for a MIB application does
The createnode command fails to connect to a
not come online as expected . . . . . . . . 88
UNIX-based systems target system . . . . . . 74
The NETSUMMARY workspace does not show
addBundles command times out adding UNIX
expected data . . . . . . . . . . . . . 88
bundles to Windows depot . . . . . . . . . 74
A MIB workspace displays empty when you
createNode command fails . . . . . . . . . 75
expect to see data . . . . . . . . . . . 88
An agent does not display in the Tivoli Enterprise
Portal or in the output from the listSystems
command . . . . . . . . . . . . . . . 76 Chapter 10. Database troubleshooting 89
UNIX-based systems Log agent was deployed, Data loss prevention . . . . . . . . . . . 89
configured, and started but returns the Backing up the database for recovery purposes 89
KFWITM290E error . . . . . . . . . . . . 76 Restoring the original database contents . . . . 89
KDY1024E error displays when configuring the Tivoli Enterprise Portal Server user ID . . . . . 89
run-as user name for an agent . . . . . . . . 76 Tivoli Enterprise Portal Server cannot connect to the
Viewdepot did not return any information . . . . 76 database . . . . . . . . . . . . . . . 90
New agents do not display in the Tivoli Enterprise Data did not migrate from the Microsoft SQL Server
Portal navigator . . . . . . . . . . . . . 76 database to the DB2 Universal Database . . . . . 91
An agent does not start on a Solaris system . . . 77 Database contents are incorrect after installation . . 91
An agent displays unavailable in the Tivoli The error SQL0443N with 'SYSIBM:CLI:-805' occurs
Enterprise Portal. . . . . . . . . . . . . 77 after upgrading to DB2 UDB Version 8.1 Fix Pack 10 92
Some rows do not display in an upgraded table . . 92
Chapter 9. Universal Agent Historical data is not warehoused . . . . . . . 93
Historical data for logs is incorrect . . . . . . 93
troubleshooting . . . . . . . . . . . 79 Too much historical data is collected . . . . . . 93
Preliminary Universal Agent problem determination 79 Warehouse Proxy agent failed to export data . . . 93
Universal Agent does not start . . . . . . . . 79 There are ORACLE or DB2 errors in the khdras1.log
The sysxlogins report is empty in the file . . . . . . . . . . . . . . . . . 94
TIVOLI_DATA_WAREHOUSE ODBC application . . 80 SQL0552N "ITMUSER" does not have the privilege
Universal Agent console program fails to connect . 81 to perform operation ″CREATE BUFFERPOOL″
Previously defined situations display in the Tivoli SQLSTATE=42502 . . . . . . . . . . . . 94
Enterprise Portal with a Problem or Error status . . 82
All Universal Agent-emitted traps display with the
same severity . . . . . . . . . . . . . . 82
Chapter 11. IBM Tivoli Enterprise
The Managed system version suffix increases . . . 82 Console event synchronization
Tivoli Enterprise Portal column headings are troubleshooting . . . . . . . . . . . 95
missing for a Universal Agent application . . . . 82 Preliminary IBM Tivoli Enterprise Console event
Tivoli Enterprise Portal charts and graphs do not synchronization problem determination . . . . . 95
work for numeric data . . . . . . . . . . . 83 T/EC ITM Synchronization Tasks . . . . . . . 95
kumstrap and kumsnetd processes do not start . . 83 Changing the TCP/IP timeout setting on your event
The Universal Agent stops functioning if the system server . . . . . . . . . . . . . . . . 95
IP address changes while it is running . . . . . 84 IBM Tivoli Enterprise Console task timeout expires
'Unable to get attribute name for while in process . . . . . . . . . . . . . 96
tablename/column' error occurs in the Tivoli Situations are not forwarded from Tivoli Enterprise
Enterprise Monitoring Server log after creating a a Monitoring Server to the Tivoli Enterprise Console
situation . . . . . . . . . . . . . . . 84 server . . . . . . . . . . . . . . . . 96
SNMP data provider problems . . . . . . . . 85 Situation Events have an UNKNOWN severity in
SNMP-MANAGER Trap workspace is the Tivoli Enterprise Console . . . . . . . . 99
unavailable in many columns . . . . . . . 85 Forwarded IBM Tivoli Enterprise Console events
The TRAP workspace does not display expected display with the PARSING_FAILED status in the
traps. . . . . . . . . . . . . . . . 85 IBM Tivoli Enterprise Console reception log . . . 99
SNMP metafiles are imported but MIB data The IBM Tivoli Enterprise Console is disabled . . 102
collection is not working . . . . . . . . . 85

Contents v
The IBM Tivoli Enterprise Console does not Appendix C. Environment variables 113
indicate that a situation event was acknowledged Tivoli Enterprise Portal Server environment
or closed . . . . . . . . . . . . . . . 103 variables . . . . . . . . . . . . . . . 113
TEC_ITM_OM_Situation_Sync_Error events occur 105 Tivoli Enterprise Monitoring Server environment
Receiving error message when running the Rule variables . . . . . . . . . . . . . . . 113
Check Utility with the -cd and -rd options . . . 105 Universal Agent environment variables . . . . . 113
Expected impacted rules are not displayed when IBM Tivoli Data Warehouse environment variables 114
entering multiple event classes with class attributes 106 Tivoli Enterprise Monitoring Agent deploy
The wrules_check command fails . . . . . . . 106 environment variables . . . . . . . . . . 117
The NetView menus are unavailable. . . . . . 107
Errors occur during installation of IBM Tivoli Appendix D. Support information . . . 119
Enterprise Console event synchronization . . . . 107
Searching knowledge bases . . . . . . . . . 119
The IBM Tivoli Enterprise Console does not
Searching the information center . . . . . . 119
display in a workspace after logging off and
Searching the Internet . . . . . . . . . 119
logging on the Tivoli Enterprise Portal . . . . . 107
Obtaining fixes . . . . . . . . . . . . . 120
The Tivoli Enterprise Portal stops when attempting
Receiving weekly support updates . . . . . . 120
to launch the IBM Tivoli Enterprise Console behind
Contacting IBM Software Support . . . . . . 120
a router . . . . . . . . . . . . . . . 107
Determining the business impact . . . . . . 121
The error 'ECO2029E: Failed to connect to
Describing problems and gathering information 122
http://servername:port_number/cgi-
Submitting problems . . . . . . . . . . 122
bin/tec_help.pl.' occurs after clicking the
Information button on the IBM Tivoli Enterprise
Console. . . . . . . . . . . . . . . . 108 Appendix E. Understanding
Situations return to acknowledged . . . . . . 108 informational, warning, and error
messages . . . . . . . . . . . . . 123
Appendix A. IBM Tivoli Monitoring
product codes . . . . . . . . . . . 109 Appendix F. Notices . . . . . . . . 239
Trademarks . . . . . . . . . . . . . . 241
Appendix B. IBM Tivoli Monitoring
processes . . . . . . . . . . . . . 111 Index . . . . . . . . . . . . . . . 243

vi IBM Tivoli Monitoring: Problem Determination Guide

About this guide
This guide provides problem determination and resolution information for the
issues most commonly encountered with the IBM® Tivoli® Monitoring. You can use
this guide in conjunction with the other books in the IBM Tivoli Monitoring V6.1.0
library “IBM Tivoli Monitoring library” on page vii.

Who should read this guide

This book is for system administrators. It explains the concepts you should know
to resolve issues with IBM Tivoli Monitoring V6.1. Readers should be familiar with
the following:
v Importing, installing, and managing IBM Tivoli Monitoring
v System administration on the systems where you plan to install IBM Tivoli
Monitoring components and which you plan to monitor using the product
v IBM Tivoli Enterprise Console
v IBM Tivoli Data Warehouse
v IBM DB2® databases

Publications
This section lists publications in the IBM Tivoli Monitoring library. It also describes
how to access Tivoli publications online and how to order Tivoli publications.

IBM Tivoli Monitoring library

The following documents provide information about the IBM Tivoli Monitoring
product:
v Introducing IBM Tivoli Monitoring, GI11-4071
Introduces the components of IBM Tivoli Monitoring and compares the concepts
and function of IBM Tivoli Monitoring to Distributed Monitoring.
v IBM Tivoli Monitoring: Upgrading from Tivoli Distributed Monitoring, GC32-9462
Provides information about how to upgrade from Tivoli Distributed Monitoring.
v IBM Tivoli Monitoring Installation and Setup Guide, GC32-9407
Provides information about installing and setting up IBM Tivoli Monitoring and
upgrading from Candle® OMEGAMON® version 350 or 360.
v IBM Tivoli Monitoring User’s Guide, SC32-9409
Complements the Tivoli Enterprise Portal online help. The guide provides
hands-on lessons and detailed instructions for all Tivoli Enterprise Portal
features.
v IBM Tivoli Monitoring Administrator’s Guide, SC32-9408
Describes the support tasks and functions required for the Tivoli Enterprise
Portal Server and clients, including Tivoli Enterprise Portal user administration.
v IBM Tivoli Monitoring Problem Determination Guide, GC32-9458
Provides information and messages to assist users with troubleshooting
problems with the software.
v Exploring IBM Tivoli Monitoring, SC32-1803

© Copyright IBM Corp. 2005 vii

 Provides a series of exercises that help users explore IBM Tivoli Monitoring.
After completing the activities in this workbook, users will have installed and
configured their environment, explored both the graphical and command line
interfaces of the product, used several of the new features in this release of IBM
Tivoli Monitoring (such as creating a monitor based on a custom script), and
worked with several monitoring agents.
v IBM Tivoli Universal Agent User’s Guide, SC32-9459
Introduces you to the IBM Tivoli Universal Agent, an agent of IBM Tivoli
Monitoring. The IBM Tivoli Universal Agent enables you to use the monitoring
and automation capabilities of IBM Tivoli Monitoring to monitor any type of
data you collect.
v IBM Tivoli Universal Agent API and Command Programming Reference Guide,
SC32-9461
Explains the procedures for implementing the IBM Tivoli Universal Agent APIs
and provides descriptions, syntax, and return status codes for the API calls and
command-line interface commands.
v Configuring IBM Tivoli Enterprise Monitoring Server on z/OS, SC32-9463
Describes how to configure and customize the Tivoli Enterprise™ Monitoring
Server running on z/OS®.
v IBM Tivoli Monitoring: IBM Tivoli Monitoring 5.x Endpoint Agent User’s Guide
The IBM Tivoli Monitoring 5.x Endpoint Agent extends the capabilities of IBM
Tivoli Monitoring V5.1.2. It enables data collected by deployed IBM Tivoli
Monitoring V5.1.2 endpoints to be displayed in the Tivoli Enterprise Portal and
stored in Tivoli Data Warehouse.

Accessing terminology online

The Tivoli Software Glossary includes definitions for many of the technical terms
related to Tivoli software. The Tivoli Software Glossary is available at the following
Tivoli software library Web site:

http://www.ibm.com/software/tivoli/library

The IBM Terminology Web site consolidates the terminology from IBM product
libraries in one convenient location. You can access the Terminology Web site at the
following Web address:

http://www.ibm.com/ibm/terminology

Accessing publications online

The documentation CD contains the publications that are in the product library.
The format of the publications is PDF, HTML, or both.

IBM posts publications for this and all other Tivoli products, as they become
available and whenever they are updated, to the Tivoli software information center
Web site. Access the Tivoli software information center by first going to the Tivoli
software library at the following Web address:

http://www.ibm.com/software/tivoli/library/

Scroll down and click the Product manuals link. In the Tivoli Technical Product
Documents Alphabetical Listing window, click M to access all of the IBM Tivoli
Monitoring product manuals.

viii IBM Tivoli Monitoring: Problem Determination Guide

 Note: If you print PDF documents on other than letter-sized paper, set the option
in the File → Print window that allows Adobe Reader to print letter-sized
pages on your local paper.

The IBM Software Support Web site provides the latest information about known
product limitations and resolutions in the form of technotes for your product. You
can view this information at the following Web site:

http://www.ibm.com/software/support

Ordering publications
You can order many Tivoli publications online at the following Web site:

http://www.elink.ibmlink.ibm.com/public/applications/
publications/cgibin/pbi.cgi

You can also order by telephone by calling one of these numbers:

v In the United States: 800-879-2755
v In Canada: 800-426-4968

In other countries, contact your software account representative to order Tivoli

publications.

Accessibility
Accessibility features help users with a physical disability, such as restricted
mobility or limited vision, to use software products successfully. With this product,
you can use assistive technologies to hear and navigate the interface. You can also
use the keyboard instead of the mouse to operate most features of the graphical
user interface.

For additional information, see the Accessibility Appendix in the Tivoli Enterprise
Portal User’s Guide.

Tivoli technical training

For Tivoli technical training information, refer to the following IBM Tivoli
Education Web site:

http://www.ibm.com/software/tivoli/education/

Support information
Appendix D, “Support information,” on page 119 describes the following options
for obtaining support for IBM products:
v “Searching knowledge bases” on page 119
v “Obtaining fixes” on page 120
v “Contacting IBM Software Support” on page 120

Conventions used in this guide

This guide uses several conventions for special terms and actions.

About this guide ix

 Typeface conventions
This guide uses the following typeface conventions:
Bold
v Lowercase commands and mixed case commands that are otherwise
difficult to distinguish from surrounding text
v Interface controls (check boxes, push buttons, radio buttons, spin
buttons, fields, folders, icons, list boxes, items inside list boxes,
multicolumn lists, containers, menu choices, menu names, tabs, property
sheets), labels (such as Tip:, and Operating system considerations:)
v Keywords and parameters in text
Italic
v Words defined in text
v Emphasis of words (for example, ″Use the word that to introduce a
restrictive clause.″)
v New terms in text (except in a definition list)
v Variables and values you must provide
Monospace
v Code and other examples
v File names, programming keywords, and other elements that are difficult
to distinguish from surrounding text
v Message text and prompts addressed to the user
v Text that the user must type
v Values for arguments or command options

Tivoli command syntax

The following special characters define Tivoli command syntax:
[] Identifies elements that are optional. Required elements do not have
brackets around them.
... Indicates that you can specify multiple values for the previous element.
Separate multiple values by a space, unless otherwise directed by
command information.
If the ellipsis for an element follows a closing bracket, use the syntax
within the brackets to specify multiple values. For example, to specify two
administrators for the option [–a admin]..., use –a admin1 –a admin2.
If the ellipsis for an element is within the brackets, use the syntax of the
last element to specify multiple values. For example, to specify two hosts
for the option [–h host...], use –h host1 host2.
| Indicates mutually exclusive information. You can use the element on
either the left or right of the vertical bar.
{} Delimits a set of mutually exclusive elements when a command requires
one of them. Brackets ([ ]) are around elements that are optional.

In addition to the special characters, Tivoli command syntax uses the typeface
conventions described in “Typeface conventions.” The following examples illustrate
the typeface conventions used in Tivoli command syntax:
v itmcmd agent [-l ][ -h install_dir ] [ -o instance ] [ -p option ] [-c] [-s] start|stop
{pc|all}

x IBM Tivoli Monitoring: Problem Determination Guide

 The start|stop and {pc|all} parameters are the only required parameters for the
itmcmd agent command. The brackets around the -l, -h, -o, -p, -c, and -s
parameters indicate that they are optional. The braces around {pc|all} indicate
that you must either specify a product code (pc) or choose to start or stop all
components. Refer to the IBM Tivoli Monitoring Installation and Setup Guide or the
IBM Tivoli Monitoring Administrator’s Guide for more information.
v wchkdb [–o outfile] [–u] [–x] {–f infile | –i | object...}
The –f, –i, and object elements are mutually exclusive. Braces that surround
elements indicate that you are including a required element. If you specify the
object argument, you can specify more than one object. See the Tivoli Management
Framework Reference Manual for more information.

About this guide xi

xii IBM Tivoli Monitoring: Problem Determination Guide
Chapter 1. Introduction to problem determination
This guide helps you to decide where to begin looking for causes when you have a
problem with IBM Tivoli Monitoring. Usually, you start with a symptom, or set of
symptoms, and trace them back to their cause. This process is called problem
determination. Problem determination is not the same as problem solving, although
during the process of problem determination, you can obtain enough information
to solve a problem. Examples of situations where this can happen include:
v End-user errors
v Application programming errors
v System programming errors, such as in resource definitions
However, you might not always be able to solve a problem yourself after
determining its cause. For example, a performance problem might be caused by a
limitation of your hardware. If you are unable to solve a problem on your own,
contact IBM Software Support for a solution.

Sources of problem determination information

The primary troubleshooting feature is logging. Logging refers to the text messages
and trace data generated by the software. Messages and trace data are sent to an
output destination, such as a console screen or a file.

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. See
Appendix E, “Understanding informational, warning, and error messages,” on
page 123 for message information.

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. See the Chapter 2, “Diagnostic tools,” on page 7
for more information about tracing.

Collecting data
If you have a problem that you are unable to solve using the information in this
guide, gather the following information that relates to the problem and contact
IBM Software Support for further assistance.
v Monitored application file as specified on the SOURCE FILE statement, if
applicable.
v Appropriate IBM Tivoli Monitoring RAS1 trace output.
v Description of the operation scenario that led to the problem.
v Incorrect output, such as Tivoli Enterprise Portal screen prints or a description of
what you observed, if applicable.
v Log files
Collect logs from failing systems. You can collect all logs or logs of a certain type
such as, RAS (reliability, availability, and serviceability) trace logs or message
logs.

© Copyright IBM Corp. 2005 1

 v Application information:
– Version number and patch level
– Sample application data file (if monitoring a file)
v Operating system version number and patch level
v Messages and other information displayed on the screen
v Version number of the following members of the monitoring environment:
– IBM Tivoli Monitoring. Also provide the patch level, if available.
– Monitoring Agent version number
– Tivoli Enterprise Portal. Select About Tivoli Enterprise Portal ... from the
Help menu.

Note: The version number of the Tivoli Enterprise Portal and the Tivoli
Enterprise Portal server must always be synchronized.
v Screen captures of incorrect output, if any.
v If the systems stops on Windows, collect the drwtsn32.log and user.dmp files if
available. The drwtsn32.log and user.dmp files are located in
\Documents and Settings\All Users\Documents\DrWatson
1. Enter the following command at the command prompt to enable Dr. Watson
as default debugger:
drwtsn32 –i
2. Enter the following command at the command prompt to open the Dr.
Watson configuration dialog:
drwtsn32

2 IBM Tivoli Monitoring: Problem Determination Guide

 3. Set the Crash dump Type to FULL.
4. Remove the check from the Dump Symbol Table box.
5. Place a check in the Dump all Thread Contexts box.
6. Place a check in the Create Crash Dump File box.
v If the system stops on UNIX-based systems, collect the core dump file from
install_home/bin directory, where install_home is the directory path where you
installed the monitoring agent.

Chapter 1. Introduction to problem determination 3

Problem classification
The first task in problem determination is to determine the origin of the problem,
or which component or function is experiencing a problem. To assist you in
determining the origin of the problem, collect documentation at the time of the
error. You might experience problems with IBM Tivoli Monitoring in the following
areas:
v Installation
v Upgrading
v Configuration
v Connectivity
v Tivoli Enterprise Portal
v Tivoli Enterprise Portal Server
v Tivoli Enterprise Monitoring Server
v Tivoli Enterprise Monitoring Agent deployment
v Databases
v IBM Tivoli Data Warehouse
v Universal Agent
v IBM Tivoli Enterprise Console

Finding release notes

You can find release note information online by viewing IBM Technotes. Technotes
replace the Release Notes manual for this product. Technotes are short documents
that cover a single topic. You can search the Technotes collection for common
problems and solutions, as well as known limitations and workarounds. Technotes
are continuously updated to provide current product information.

The following two procedures describe how to view Technotes and subscribe to
have future Technotes e-mailed to you. Alternatively, you can watch demos of
these procedures at the following Web site:

http://www-306.ibm.com/software/support/sitetours.html

Viewing Technotes
Perform the following actions to access Technotes for this product:
1. Launch the IBM Software Support Web site:
http://www.ibm.com/software/support
2. In the Products A - Z field, select the product name to open the
product-specific support site.
For this product, select I > IBM Tivoli Monitoring..
3. In the Self help field, click Technotes.
4. Scroll through the Technotes, or you can optionally type a search term to refine
the displayed data.
For tips on refining your search, click Search tips.

Creating an e-mail subscription to Technotes

You can subscribe to e-mail notification about product tips and newly published
fixes through My support, a personalized portal that enables you to:
v Specify the products for which you want to receive notifications

4 IBM Tivoli Monitoring: Problem Determination Guide

v Choose from flashes, downloads, and Technotes
v Receive an e-mail update in your inbox
Perform the following actions to subscribe to My support e-mails:
1. Launch an IBM support Web site such as the following site:

http://www.ibm.com/support/us/
2. Click My support in the upper-right corner of the page.
3. If you have not yet registered, click register in the upper-right corner of the
support page to create your user ID and password.
4. Sign in to My support.
5. On the My support page, click Edit profile.
6. Select a product family and continue setting your preferences to specify the
information you want in your e-mails.
7. Click Submit.

Chapter 1. Introduction to problem determination 5

6 IBM Tivoli Monitoring: Problem Determination Guide
Chapter 2. Diagnostic tools
IBM Tivoli Monitoring provides several tools for diagnosing problems. The
primary diagnostic tool of IBM Tivoli Monitoring is logging. Logging refers to the
text messages and trace data generated by the software. Messages and trace data
are sent to an output destination, such as a console screen or a file.

Trace logging
Trace logs capture information about the operating environment when component
software fails to operate as intended. The principal log type is the reliability,
availability, and serviceability (RAS) trace log. RAS logs are in the English
language only. The RAS trace log mechanism is available on the Tivoli Enterprise
Monitoring Server, the Tivoli Enterprise Portal Server, and the monitoring agent.
By default, the logs are stored in the installation path for IBM Tivoli Monitoring.
IBM Software Support uses the information captured by trace logs to trace a
problem to its source or to determine why an error occurred. The default
configuration for tracing, such as whether tracing is enabled or disabled and trace
level, depends on the source of the tracing. You can choose how many files to keep
when the log rolls. If you cannot find the log files you need, restart the system and
try again. This section includes instructions for configuring trace logging.

Table 1 lists the location of the log files directories.

Table 1. Location of log files on the Tivoli Enterprise Monitoring Server
Component Windows UNIX-based systems
Tivoli Enterprise install_dir\logs install_dir/logs/
Portal Server hostname_PC_timestamp.log

where:
install_dir
Specifies the directory where Tivoli Enterprise
Portal Server was installed.
hostname
Specifies the name of the system hosting the
product.
PC Specifies the product code. cq for the Tivoli
Enterprise Portal Server. See Appendix A, “IBM
Tivoli Monitoring product codes,” on page 109 for
a list of product codes.
timestamp
A decimal representation of the time at which the
process was started.
Tivoli Enterprise C:\Documents and Settings\ None.
Portal browser Administrator\
client Application Data\
Java\Deployment\
log\plugin142.trace

© Copyright IBM Corp. 2005 7

Table 1. Location of log files on the Tivoli Enterprise Monitoring Server (continued)
Component Windows UNIX-based systems
Tivoli Enterprise install_dir\CNP\kcjerror.log install_dir/logs/
Portal desktop install_dir\CNP\kcjras1.log hostname_PC_timestamp.log
client
where:
install_dir
Specifies the directory where Tivoli Enterprise
Portal Server was installed.
hostname
Specifies the name of the system hosting the
product.
PC Specifies the product code. cq for the Tivoli
Enterprise Portal Server. See Appendix A, “IBM
Tivoli Monitoring product codes,” on page 109 for
a list of product codes.
timestamp
A decimal representation of the time at which the
process was started.
Tivoli Enterprise install_dir\logs\hostname_PC_ install_dir/logs/hostname_PC_timestamp.log
Monitoring HEXtimestamp-nn.log
Server where:
where: install_dir
Specifies the directory where Tivoli Enterprise
install_dir
Portal Server was installed.
Specifies the directory
where Tivoli Enterprise hostname
Monitoring Server was Specifies the name of the system hosting the
installed. product.
PC Specifies the product code. PC Specifies the product code. cq for the Tivoli
ms for Tivoli Enterprise Enterprise Portal Server. See Appendix A, “IBM
Monitoring Server Tivoli Monitoring product codes,” on page 109 for
a list of product codes.
HEXtimestamp
A hexadecimal timestamp
representation of the time A decimal representation of the time at which the
at which the process was process was started.
started.
nn Represents the circular
sequence in which logs are
rotated. Ranges from 1-5,
by default, though the first
is always retained, since it
includes configuration
parameters.

8 IBM Tivoli Monitoring: Problem Determination Guide

Table 1. Location of log files on the Tivoli Enterprise Monitoring Server (continued)
Component Windows UNIX-based systems
Tivoli Enterprise install_dir\logs\hostname_PC_ install_dir/logs/hostname_PC_timestamp.log
Monitoring HEXtimestamp-nn.log
Agents where:
where: install_dir
install_dir Specifies the directory where Tivoli Enterprise
Specifies the directory Portal Server was installed.
where Tivoli Enterprise hostname
Monitoring Agent was Specifies the name of the system hosting the
installed. product.
PC Specifies the product PC Specifies the product code. cq for the Tivoli
codes, for example, um for Enterprise Portal Server. See Appendix A, “IBM
Universal Agent or nt for Tivoli Monitoring product codes,” on page 109 for
Windows. a list of product codes.
HEXtimestamp timestamp
A hexadecimal A decimal representation of the time at which the
representation of the time process was started.
at which the process was
started.
nn Represents the circular
sequence in which logs are
rotated. Ranges from 1-5,
by default, though the first
is always retained, since it
includes configuration
parameters.
IBM Tivoli install_dir\logs\hostname_PC_ Not supported.
Warehouse Proxy timestamp.log
agent
where
PC Specifies the product code.
hd is the product code for
the IBM Tivoli Warehouse
Proxy agent
IBM Tivoli The Summarization and Pruning Agent uses C-based RAS1 tracing, Java-based RAS1 tracing and
Summarization Java-based internal tracing. By default, Summarization and Pruning Agent trace data is written
and Pruning to a file in the logs subdirectory.
agent
install_dir\logs\hostname_PC_ install_dir/logs/hostname_PC_
HEXtimestamp-nn.log HEXtimestamp-nn.log
install_dir\logs\hos tname_PC_ install_dir/logs/hostname_PC_ras1java_
ras1java_HEXtimestamp-nn.log HEXtimestamp-nn.log
install_dir\logs\hostname_PC_ install_dir/logs/hostname_PC_java_
java_HEXtimestamp-nn.log HEXtimestamp-nn.log
where:
install_dir
Specifies the directory where Tivoli Enterprise Monitoring Agent was installed.
PC Specifies the product codes, for example, sy for IBM Tivoli Summarization and Pruning
agent.
HEXtimestamp
A hexadecimal representation of the time at which the process was started.
nn Represents the circular sequence in which logs are rotated. Ranges from 1-5, by default,
though the first is always retained, since it includes configuration parameters.

Chapter 2. Diagnostic tools 9

Table 1. Location of log files on the Tivoli Enterprise Monitoring Server (continued)
Component Windows UNIX-based systems
IBM Tivoli install_dir\logs\hostname_PC_ install_dir/logs/hostname_PC_timestamp.log
Enterprise HEXtimestamp-nn.log install_dir/logs/hostname_PC_HEXtimestamp-nn.log
Console Event
Forwarder where: where:

install_dir install_dir
Specifies the directory Specifies the directory where Tivoli Enterprise
where Tivoli Enterprise Portal Server was installed.
Monitoring Server was hostname
installed. Specifies the name of the system hosting the
PC Specifies the product code. product.
ms for Tivoli Enterprise PC Specifies the product code. cq for the Tivoli
Monitoring Server Enterprise Portal Server. See Appendix A, “IBM
HEXtimestamp Tivoli Monitoring product codes,” on page 109 for
A hexadecimal a list of product codes.
representation of the time timestamp
at which the process was A decimal representation of the time at which the
started. process was started.
nn Represents the circular
sequence in which logs are
rotated. Ranges from 1-5,
by default, though the first
is always retained, since it
includes configuration
parameters.
IBM Tivoli c:\tmp\itmsynch\logs\ /tmp/itmsynch/logs/synch_
Enterprise synch_trace.log trace.log
Console Situation c:\tmp\itmsynch\logs\ tmp/itmsynch/logs/synch_
Update synch_msg.log msg.log
Forwarder
Note: IBM Tivoli Enterprise Console Situation Update Forwarder logs are created on the IBM
Tivoli Enterprise Console server.

The log files are managed as follows:

v On Windows, the log file is overwritten each time agent starts. There is no
automated method to archive previous RAS1 log files.
v On UNIX-based systems, the log file name includes a time stamp. The
UNIX-based systems RAS1 log files are stored in the /logs directory. The
following is an example of a log files name that includes the time stamp:
f50pa2b_ux_1112097194.log

Note: When you communicate with IBM Software Support, you must capture and
send the RAS1 log that matches any problem occurrence that you report.

Installation log files

The following table lists and describes the log files created during installations.

10 IBM Tivoli Monitoring: Problem Determination Guide

Table 2. Installation log files
Windows UNIX-based systems

v ITM_HOME\InstallITM\Abort<Product_name><date_timestamp>.log $CANDLEHOME/logs/candle_
installation.log
This log is created if an abort occurs for either a first time install or
a modification of previous installation of IBM Tivoli Monitoring.
v ITM_HOME\InstallITM\<Product_name>_<timestamp>.log
This log is created during a normal clean installation.
v ITM_HOME\InstallITM\MOD_<Product_name>timestamp.log
This log is created if you modify an existing product specified with
the PC, or when adding or deleting components.
where:
Product_name
Specifies the product name. IBM Tivoli Monitoring 20050923
1815.log is the log file name for the IBM Tivoli Monitoring
installation CD.
timestamp
A decimal representation of the time at which the process was
started.

You can find a log for uninstallation on Windows in the root directory where the
product was installed:
Uninstall<PC><date_timestamp>.log

Upgrading from Tivoli Distributed Monitoring log file

All upgrade actions performed by the IBM Tivoli Monitoring Upgrade Toolkit are
recorded in a central log with an associated user ID and a time stamp. Upgrade
actions taken outside of the Upgrade Toolkit are not recorded in the log. The
detailed results from running the Upgrade Toolkit are recorded in a log file.
Table 3. Upgrading from Tivoli Distributed Monitoring log file
Windows UNIX-based systems
$DBDIR/AMX/logs/log_tool_ $DBDIR/AMX/logs/log_tool_
timestamp.log timestamp.log

where:
$DBDIR
The Tivoli Management Environment Framework environment variable
that specifies the directory where the Object Repository (odb.bdb) is
located.
tool Specifies the IBM Tivoli Monitoring Upgrade Toolkit tool: witmscantmr,
witmassess, or witmupgrade.
timestamp
Specifies a time stamp that includes data and time of execution.

For example: log_witmscantmr_20050721_15_30_15.log

The log file name displays when the Upgrade Toolkit tool completes the upgrade
operation. Each time a Upgrade Toolkit tool runs, its generates a new log file that

Chapter 2. Diagnostic tools 11

 is never reused by any tool. The contents of the log file conform to the Tivoli
Message Standard XML logging format. The following example is an excerpt from
an Upgrade Toolkit tool log file:
<Message Id="AMXUT2504I" Severity="INFO">
<Time Millis="1121977824199"> 2005.07.21 15:30:24.199 CST </Time>
<Server Format="IP">YFELDMA1.austin.ibm.com</Server>
<ProductId>AMXAMX</ProductId>
<Component>ScanTMR</Component>
</Component>1</ProductInstance>
<LogText><![CDATA[AMXUT2504I The software is creating a new baseline file
C:\PROGRA~1\Tivoli\db\YFELDMA1.db\AMX\shared\analyze\scans\
1889259234.xml.]];
</LogText>
<TranslationInfo Type="JAVA"
Catalog="com.ibm.opmt.utils.messages.MigrationManager_
msgs"
MsgKey="AMXUT2504I"><Param>
<![CDATA[C:\PROGRA~1\Tivoli\db\YFELDMA1.db\AMX\shared\analyze\scans\
1889259234.xml]];
</Parm></TranslationInfo>
<Principal></Principal>
</Message>

Reading RAS1 logs

This section provides an example of the Universal Agent RAS1 trace logs. By
default, the Universal Agent RAS1 trace log lists the following details about the
health of an ODBC data provider application:
v Whether the ODBC tables come online during startup.
v Whether the ODBC table data is collected.
v Errors with the ODBC-related status messages, including informational messages
about when each ODBC connection completes.
v Errors that occur during ODBC data provider data retrieval, including errors in
the ODBC driver code.
v Independent Software Vendor (ISV) API errors. (The Universal Agent makes API
calls to the ISV ODBC driver to implement the connections and SQL select
statements.)

The following RAS1 log excerpt lists ODBC status messages using default tracing:
KUMP_ProcessStartUpConfig") Loading metafile
<f:\candle\cma\metafiles\TIVOLI_DATA_WAREHOUSE.mdl>
from startup config file
f:\candle\CMA\WORK\KUMPCNFG_INST1
"DCHserver::dp_register") Application TIVOLI_DATA_WAREHOUSE
successfully registered"KUMP_ProcessStartUpConfig")
1 application metafile(s) processed from startup
config
file f:\candle\CMA\WORK\KUMPCNFG_INST1
"KUMP_StartDataProvider") Starting ODBC Data Provider...
"KUMP_WaitODBCsourceReadyForMonitor")
Reusing connection handle for ODBC source
TIVOLI_DATA_WAREHOUSE table <syscharsets>
"KUMP_ODBCserver") Successfully connected to ODBC source
TIVOLI_DATA_WAREHOUSE table <syscharsets>
"KUMP_WaitODBCsourceReadyForMonitor") Reusing connection handle
for ODBC source TIVOLI_DATA_WAREHOUSE table <syscomments>

The Reusing connection handle messages indicates the ODBC provider is reusing
resource to conserve memory. The ODBC data provider allocates a connection for
each metafile with multiple attribute groups that connect to the same data source

12 IBM Tivoli Monitoring: Problem Determination Guide

 using the same user ID and password combination. Each SQL Select statement that
is run for the various attribute groups shares the same connection handle.

The following is an excerpt from later in the same log:

userDataList::calculateChecksum") Initial creation of catalog/attribute tables for
applName <Tivoli_Data_Warehouse>
"KUMP_ODBCserver") ODBC source <Tivoli_Data_Warehouse> table <syscharsets> is now
online to the data provider
"KUMP_ODBCserver") ODBC source <Tivoli_Data_Warehouse> table <syscacheobjects>
is now online to the data provider
"KUMP_ODBCserver") ODBC source <Tivoli_Data_Warehouse> table <syscomments>
is now online to the data provider"

Setting traces
When you encounter an error with IBM Tivoli Monitoring that requires contacting
IBM Software Support, you might be asked to submit a copy of the error log. The
error log is part of the trace diagnostic tool in Tivoli Enterprise Portal. It is set to
log errors, and you can set other parameters for collecting specific details.

Setting the trace option for the Tivoli Enterprise Portal client
trace
A log file is created automatically the first time you start Tivoli Enterprise Portal,
and is named install_dir\cnp\logs\kcjras1.log. This log file contains all of the
RAS1 tracing for the Tivoli Enterprise Portal client. Whenever you start a new
work session, the log file is purged and rewritten for the current work session. If
you want to preserve the log file from the last work session, you must rename it or
copy it to another directory before starting Tivoli Enterprise Portal again. The
kcj.log file contains errors generated by the Sun Java™ libraries used in the Tivoli
Enterprise Portal client.

To set the trace options:

1. From the Tivoli Enterprise Portal menu, select File > Trace Options.

2. Select a trace class from the list or as instructed by IBM Software Support (such
as UNIT:Workspace ALL):

Chapter 2. Diagnostic tools 13

 ALL provides data for all classes. Use the setting temporarily, because it
generates large amounts of data.
ERROR logs internal error conditions. This setting provides the minimum level
of tracing, with little resource overhead, and ensures that program failures will
be caught and detailed.
NONE turns off the error log so no data is collected.
3. Click OK to close the window and turn on logging.

Setting the trace option for the Tivoli Enterprise Portal Server
trace
You must set the trace options for the Tivoli Enterprise Portal Server through
Manage Tivoli Enterprise Services. Before you set the trace options for the Tivoli
Enterprise Portal Server, determine the trace string. The trace string specifies the
trace setting. Set trace options for the Tivoli Enterprise Portal Server when you
start the Tivoli Enterprise Portal Server. The log file continues to grow until you
either turn off the trace or recycle the Tivoli Enterprise Portal Server.
1. On the computer where the Tivoli Enterprise Portal Server is installed, click
Start > Programs > IBM Tivoli Monitoring > Manage Tivoli Enterprise
Services.
2. Right-click the Tivoli Enterprise Portal Server service.
3. Select Advanced > Edit Trace Parms to display the Trace Parameters window.
4. Select the RAS1 filters. The default setting is ERROR
5. Accept the defaults for the rest of the fields.
6. Click OK to set the new trace options.
7. Click Yes to recycle the service.

Setting the trace option for the Tivoli Enterprise Monitoring

Server trace
1. On the computer where the Tivoli Enterprise Monitoring Server is installed,
select Start > Programs > Tivoli Monitoring Services > Manage Tivoli
Enterprise Services.
2. Right-click the Tivoli Enterprise Monitoring Server service.
3. Select Advanced > Edit Trace Parms to display the Trace Parameters window.
4. Select the RAS1 filters. The default setting is ERROR
5. Accept the defaults for the rest of the fields.
6. Click OK to set the new trace options.
7. Click Yes to recycle the service.

Setting the trace option for the Agent Deploy tool

1. On the computer where the Tivoli Enterprise Monitoring Server is installed,
select Start > Programs > Tivoli Monitoring Services > Manage Tivoli
Enterprise Services.
2. Right-click the Tivoli Enterprise Monitoring Server service.
3. Select Advanced > Edit Trace Parms to display the Trace Parameters window.
4. Type (UNIT:kdy all) in the Enter RAS1 Filters field.
5. Accept the defaults for the rest of the fields.
6. Click OK to set the new trace options.
7. Click Yes to recycle the service.

14 IBM Tivoli Monitoring: Problem Determination Guide

Setting the trace option for the IBM Tivoli Universal Agent
Use the IBM Tivoli Universal Agent trace facility to diagnose problems with the
Universal Agent. The Universal Agent uses RAS1 tracing. By default, Universal
Agent trace data is written to a file in the logs subdirectory. The default RAS1 trace
level is ERROR for all Universal Agent components and modules. On Windows,
Tivoli Monitoring Services overwrites the kumras1.log each time the Universal
Agent starts and there is no method for archiving previous RAS1 log files.
Therefore, you must obtain the RAS1 log that matches the problem occurrence
before contacting IBM Software Support. You can set tracing options for individual
Universal Agent components and modules in the KUMENV file on Windows or
the um.ini file on UNIX-based systems.

RAS1 supports pattern matching. For example, (UNIT:kums options) traces all
SNMP data provider modules because they all begin with kums. Detailed RAS1
tracing can degrade Universal Agent performance due to high CPU usage and I/O
overhead. Therefore, set the Universal Agent RAS1 tracing to KBB_RAS1=ERROR after
problem diagnosis. If a module produces excessive error messages and fills the
RAS1 log, set (UNIT:modulename None) to suppress the module until you resolve the
errors. If you discover an old Windows RAS1 log file, the KBB_RAS1 environment
was erased or commented out in the KUMENV file, add KBB_RAS1=ERROR to the
install_dir\logs\hostname_um_timestamp.log to reactivate Universal Agent RAS1
tracing.

Set the IBM Tivoli Universal Agent trace from Manage Tivoli Enterprise Services:
1. Right-click the Universal Agent.
2. Select Advanced > Edit Trace Parms.
3. Select the RAS1 filters. The default setting is ERROR
4. Accept the defaults for the rest of the fields.
5. Click OK to set the new trace options.
6. Click Yes to recycle the service.

Setting the trace option for the Warehouse Proxy agent

1. On the computer where the Tivoli Enterprise Monitoring Server is installed,
select Start > Programs > Tivoli Monitoring Services > Manage Tivoli
Enterprise Services.
2. Right-click Warehouse Proxy.
3. Select Advanced > Edit Trace Parms.
4. Select the RAS1 filters. The default setting is ERROR.
5. Accept the defaults for the rest of the fields.
6. Click OK to set the new trace options.
7. Click Yes to recycle the service.

Setting the trace option for the IBM Tivoli Summarization and
Pruning Agent
Use the IBM Tivoli Universal Agent trace facility to diagnose problems with the
Summarization and Pruning Agent. See “Setting the trace option for the IBM Tivoli
Universal Agent” on page 15. The Summarization and Pruning Agent uses C-based
RAS1 tracing, Java-based RAS1 tracing and Java-based internal tracing. By default,
Summarization and Pruning Agent trace data is written to a file in the logs
subdirectory. The default RAS1 trace level is ERROR for all Summarization and
Pruning Agent components and modules.

Chapter 2. Diagnostic tools 15

 The following trace options are available for the IBM Tivoli Summarization and
Pruning Agent:
KBB_RAS1=ERROR
Trace general errors. KBB_RAS1=ERROR Affects the content of the C-based
RAS1 tracing (hostname_sy_HEXtimestamp-nn.log).
KBB_RAS1=ERROR (UNIT:ksz ALL)
Trace agent startup. Affects the content of the C-based RAS1 tracing
(hostname_sy_HEXtimestamp-nn.log).
KBB_RAS1=ERROR (COMP:com.tivoli.twh.ksy ALL)
Minimum level trace for summarization. Affects the content of the
Java-based RAS1 tracing (hostname_sy_ras1java_timestamp-nn.log).
KBB_RAS1=ERROR (UNIT:ksy1 ALL)
Medium level trace for summarization. Affects the content of the
Java-based internal tracing (hostname_sy_java_timestamp-n.log)
KBB_RAS1=ERROR (UNIT:ksy2 ALL)
Connection level trace for summarization. Affects the content of the
Java-based internal tracing (hostname_sy_java_timestamp-n.log)
KBB_RAS1=ERROR (UNIT:ksy3 ALL)
Statement level trace for summarization. Affects the content of the
Java-based internal tracing (hostname_sy_java_timestamp-n.log).
KBB_RAS1=ERROR (UNIT:ksy4 ALL)
ResultSet level trace for summarization. Affects the content of the
Java-based internal tracing (hostname_sy_java_timestamp-n.log).
KBB_RAS1=ERROR (UNIT:ksy5 ALL)
Column value level trace for summarization. Affects the content of the
Java-based internal tracing (hostname_sy_java_timestamp-n.log).
KBB_RAS1=ERROR (UNIT:ksysql ALL)
Traces top 10 SQL statements for summarization. Affects the content of the
Java-based internal tracing (hostname_sy_java_timestamp-n.log).
Notes:
1. The following settings: (UNIT:ksy3 ALL) or (UNIT:ksy4 ALL) or (UNIT:ksy5
ALL) produce a high volume of trace output.
2. By default, the Java-based internal trace (hostname_sy_java_timestamp-n.log)
wraps at 5 files, and each file contains 300000 lines. To change the defaults, use
the following settings in the KSYENV (Windows) or sy.ini (Unix) files:
KSZ_JAVA_ARGS=-Dibm.tdw.maxNumberDetailTraceFiles=<A>
-Dibm.tdw.maxLinesForDetailTraceFile=<B>

where:
<A> Specifies the maximum number of Java-based internal trace files that
can exist at any one time for a single launch
<B> Specifies the maximum number of lines per Java-based internal trace
file.

16 IBM Tivoli Monitoring: Problem Determination Guide

 Setting the trace option for the IBM Tivoli Monitoring upgrade
toolkit
Table 4. Setting the trace option for the IBM Tivoli Monitoring upgrade toolkit
Trace optionaction Instructions
Endpoint tracing Run the following command to setting log_threshold=3 or higher on an endpoint and enable
endpoint tracing:
wep ep set_config log_threshold=3

Traces are written to lcfd.log on the endpoint in $LCF_DATDIR.

Tracing in a test A Boolean value of TRUE or FALSE default. The default is FALSE.
environment.
Run the following command from a Tivoli Management Environment command prompt to
enable tracing:idlcall oid _set_debug TRUE

where:
oid Specifies the object ID of the Upgrade Manager object.
Run the wlookup Framework command to locate the Upgrade Manager object ID in the Tivoli
Management Environment:
wlookup -a | grep Upgrade

Note: Setting the trace value to TRUE sets all Upgrade Toolkit tools to TRUE, affecting all
users running Upgrade Toolkit tools.

A trace file named trace_tool_timestamp.log is created in the $DBDIR/AMX/trace/ directory in

XML format, with tool being ’witmscantmr’, ’witmassess’, and ’witmupgrade’, and timestamp
a time stamp that includes data and time of execution. Each record in this log contains a time
stamp and message. Additionally, these tools inherit Framework FFTC mechanisms such as
wtrace and odstat for transaction and method stack traces. See the Tivoli management
Framework documentation for more information about the commands.
OS Agent tracing OS Agent tracing is enabled at a minimum level by default. Agent tracing levels can be
adjusted with agent specific settings. Logs are stored in install_dir\installITM\ on
Windows agents or install_dir/logs/ on UNIX-based systems agents. These logs follow the
RAS1 log format.

Setting the trace option for the IBM Tivoli Monitoring event
forwarding
If your monitoring environment is configured for the IBM Tivoli Monitoring event
forwarding, you can forward situation events to the IBM Tivoli Enterprise Console,
and view events on the event server through the Tivoli Enterprise Portal. If you
want to forward situation events to and view updates from IBM Tivoli Enterprise
Console in the Tivoli Enterprise Portal, you can set the trace for the event
forwarder on the Tivoli Enterprise Monitoring Server.

Use the IBM Tivoli Monitoring event forwarding trace facility to diagnose
problems with the IBM Tivoli Monitoring event forwarding. The IBM Tivoli
Monitoring event forwarding trace facility uses RAS1 tracing. The IBM Tivoli
Monitoring event forwarding is set during installation. The acceptable values
include:
v STATE
v DETAIL
v ALL
The default trace value is STATE. If you change the trace level, you must restart
the Tivoli Enterprise Monitoring Server for the change to take effect.

Chapter 2. Diagnostic tools 17

 Use the following instructions to set the trace levels:

On Windows:
1. From Manage Tivoli Enterprise Services, right-click the Tivoli Enterprise
Monitoring Server.
2. Click Advanced > Edit trace parms.
3. Under Enter RAS1 Filter add UNIT:kfaot trc_class
where:
trc_class
Specifies STATE, DETAIL or ALL which produces increasingly more
trace information.
4. The default log file location is C:\IBM\ITM\CMS\logs\KMSRAS1.LOG, change if
necessary.
5. Click OK to set the trace.
6. Recycle the Tivoli Enterprise Monitoring Server for the trace to take effect.

On UNIX-based systems:
1. Edit install_dir/config/hostname_ms_hostname.config
where:
install_dir
Specifies the install directory of Tivoli Enterprise Monitoring Server.
hostname
Specifies the host name value supplied during install.
2. Add (UNIT:kfaot trc_class) to the line KBB_RAS1=’ERROR’
where:
trc_class
Specifies one of the following levels of trace detail:
v STATE - minimum detail.
v DETAIL - medium detail.
v ALL - maximum detail.
For example, ’KBB_RAS1=’ERROR (UNIT:kfaot STATE)’
3. Save the file.
4. Recycle Tivoli Enterprise Monitoring Server for the trace to take effect.
5. The Tivoli Enterprise Monitoring Server log can be found in
install_dir/logs/hostname_ms_nnnnnnn.log where is a time stamp. There
might be multiple files with different time stamps in the logs directory.

Setting the trace option for the IBM Tivoli Enterprise Console
Situation Update Forwarder
If your monitoring environment is configured for the IBM Tivoli Enterprise
Console, you can forward situation events to the Tivoli Enterprise Console event
server. You can also view events on the event server through the Tivoli Enterprise
Portal. If you want to forward situation events to and view updates from IBM
Tivoli Enterprise Console in the Tivoli Enterprise Portal, you can set the trace for
the Situation Update Forwarder on the IBM Tivoli Enterprise Console event server.
The default trace setting is low. You can edit the trace setting using the sitconfig
command.
$BINDIR/TME/TEC/OM_TEC/bin/sitconfig.sh update
fileName=configuration_file_name logLevel=trace_level

18 IBM Tivoli Monitoring: Problem Determination Guide

 where:
configuration_file_name
The filename of the actively loaded configuration file as indicated by the
situpdate.properties file.
trace_level
Specifies the level of trace as low, med, or verbose.

Use the IBM Tivoli Enterprise Console Situation Update Forwarder trace facility to
diagnose problems with the IBM Tivoli Enterprise Console Situation Update
Forwarder. The trace for the IBM Tivoli Enterprise Console Situation Update
Forwarder is set during installation. The acceptable values include:
v low
v med
v verbose
The default trace value is low. If you change the trace level after the Situation
Update Forwarder is started, you must restart the Situation Update Forwarder for
the change to take effect. There are two trace files:
synch_trace.log
is always created.
synch_msg.log
is created if an error occurs while running the Situation Update Forwarder.

Run the following command to set the trace levels:

$BINDIR/TME/TEC/OM_TEC/bin/sitconfig.sh update
fileName=configuration_file_name logLevel=trace_level

where:
configuration_file_name
The filename of the actively loaded configuration file as indicated by the
situpdate.properties file.
trace_level
Specifies the level of trace as low, med, or verbose.

Using the IBM Tivoli Monitoring Service Console

The IBM Tivoli Monitoring Service Console enables you to read logs and turn on
traces for remote product diagnostics and configuration. The IBM Tivoli
Monitoring Service Console is uniquely identified by its service point name. All
IBM Tivoli Monitoring Service Consoles for a host are linked and presented on the
IBM Tivoli Monitoring Service Index for that host. Point a browser to the HTTP
port 1920 on a specific host (for example, http://goby:1920) to launch the IBM
Tivoli Monitoring Service Index. You can also launch the Service console can also
be launched with the https protocol by connecting via the https protocol and port
3661. You can perform operations on a specific IBM Tivoli Monitoring process by
selecting the IBM Tivoli Monitoring Service Console associated with a service point
name.

Starting the IBM Tivoli Monitoring Service Console

Use the following procedure to start the IBM Tivoli Monitoring Service Console.
1. Start Internet Explorer V5 or higher.

Chapter 2. Diagnostic tools 19

 2. In the Address field, type the URL for the Tivoli Enterprise Portal browser
client installed on your Web server.
The URL for the Tivoli Monitoring Services Web server is
http://hostname:1920
hostname
Specifies the computer where the Tivoli Enterprise Portal Server was
installed. If the IBM Tivoli Monitoring Service Console is not displayed,
a system administrator might have blocked access to it. See “Blocking
access to the IBM Tivoli Monitoring Service Console” on page 21.

3. Click the IBM Tivoli Monitoring Service Console link associated with the
desired process (service point name).
4. When the log in window opens, click OK.

20 IBM Tivoli Monitoring: Problem Determination Guide

 In secure environments, you need a valid user ID and password to proceed.
Upon successful login, the IBM Tivoli Monitoring Service Console opens with
three areas:
v Header
v Command Results
v Command Field
You can now issue IBM Tivoli Monitoring Service Console commands in the
command input area. For a list available commands, type a question mark (?)
and click Submit.

Blocking access to the IBM Tivoli Monitoring Service Console

The Tivoli Monitoring Services integral Web server is installed automatically with
the Tivoli Enterprise Portal Server and enables users to access the IBM Tivoli
Monitoring Technology Service Console. You can prevent users from accessing the
IBM Tivoli Monitoring Technology Service Console that is available through the
integral Web server (http://computer_name:1920). To block access to the IBM Tivoli
Monitoring Technology Service Console, disable the integral Web server. However,
if you disable the integral Web server, you must install a third party Web server on
the Tivoli Enterprise Portal Server computer to access the images and style sheets
for the graphic view and edit the application parameters at every desktop client.
1. From the Windows desktop select Start > Run >
2. Type regedit.
3. Open the Tivoli Enterprise Portal Server Environment folder:
HKEY_LOCAL_computer\SOFTWARE\Tivoli Monitoring Services\KFW\Tivoli
Enterprise Portal Server\KFWSRV\Environment
4. Locate the KDC_FAMILIES in the right frame and add a space and type the
following at the end of the line: http_server:n
Example:
IP PORT:1918 SNA use:n IP.PIPE use:n http_server:n
5. Install a third party Web server on each computer where you installed the
Tivoli Enterprise Portal desktop client:
a. From the Windows desktop select Start > Programs > Tivoli Monitoring
Services > Manage Tivoli Enterprise Services.
b. Right-click Tivoli Enterprise Portal desktop and select Reconfigure from
the menu.
c. In the list of parameters that opens, double-click cnp.http.url.DataBus to
open the Edit Tivoli Enterprise Portal Parm window.
d. Type the URL to the external Web server and to the cnps.ior file in the
candle\cnb directory.
For example, if the Web server name is myWeb.hostname.com and its
document root was configured to be \candle\cnb, the value to type is:
http://myWeb.hostname.com/cnps.ior
e. Check In Use and click OK.

Chapter 2. Diagnostic tools 21

Displaying tasks in the command prompt
The Tivoli Enterprise Portal Server has an option to display the tasks at the
command prompt. This is used primarily with IBM Software Support for gathering
diagnostic information.

1. From your Windows desktop, select Start > Programs > Tivoli Monitoring
Services > Manage Tivoli Enterprise Services.
2. Right-click Tivoli Enterprise Monitoring Server, then select Change Startup
from the menu.
3. Check Allow Service to Interact with Desktop.

22 IBM Tivoli Monitoring: Problem Determination Guide

Clearing the JAR cache
If you encounter problems, IBM Software Support might instruct you to uninstall
and to clear the JAR cache.
1. If Tivoli Enterprise Portal is running, exit by closing the browser window.
2. Start the Java Plug-in.
Additional Information: You can find the Java Plug-in in Start > Settings >
Control Panel. To start it, double-click the Java Plug-in icon. Your Windows
desktop might have a shortcut to the Java Plug-in (1.4.2).
3. In the Java Plug-in Control Panel window, select the Cache tab and click Clear
JAR Cache.

4. When a message indicates the JAR cache is cleared, click OK.

If you want to start Tivoli Enterprise Portal browser mode again, restart
Internet Explorer and type the URL for Tivoli Enterprise Portal. The Java
Extension Installation progress bar shows as each Java archive file is
downloaded. Upon completion, the logon window opens and prompt you to
enter a user ID.

Using the UAGENT application

The UAGENT application is a diagnostic tool to help solve problems you might
experience with the IBM Tivoli Universal Agent. Every Universal Agent data
provider automatically activates an application called UAGENT, which includes
the DPLOG and ACTION workspaces.

DPLOG
The DPLOG is a pure event table in that it maintains only the most recent 100
rows, unless overridden by the KUMA_MAX_EVENT_ENTRIES environment
variable. The DPLOG contains informational and error messages about the status
of a data provider that indicate:
v If a metafile was validated successfully.
v If a metafile failed validation (which means the application will not come
online).
v If a data source was available at startup

Chapter 2. Diagnostic tools 23

 v Which console ports and socket listening ports were used or unavailable.
v When monitoring started and stopped for a data source.
v When monitoring switched from one file to another.
v When an API or socket client program connected and disconnected.
The DPLOG also records other actions including metafile refreshes. The two most
common Universal Agent problem symptoms are:
v One or more managed systems do not come online.
v The managed systems are online but the workspaces are empty.
Use the UAGENT application workspaces as one of the first tools to diagnose a
Universal Agent problem. You might find the solutions for both problems in the
appropriate DPLOG. The ODBC data provider also includes a DPLOG message
indicating when monitoring started for every attribute group listed in every ODBC
metafile.

ACTION workspace
Whenever a Take Action command is issued or a Reflex Action fires, an entry is
added to the ACTION workspace. The Action table is keyed and ActionID is the
Key attribute. The Action table rows have a time-to-live value of 30 minutes.
Unlike the DPLOG which is data provider-specific, the ACTION table is shared by
all data providers. If you run multiple data providers, the ACTION workspace
under every UAGENT application contains the same rows.

The Action_Result can indicate what happened to a particular Take Action

command. For example, if Universal Agent reflex actions fire faster than one per
second, the ACTION workspace temporarily stops recording the results. Recording
resumes after several minutes if the action rate slows down.

24 IBM Tivoli Monitoring: Problem Determination Guide

Chapter 3. Installation and configuration troubleshooting
This chapter contains the following sections, which provide information about
problems that might occur during installation, upgrading from previous versions,
and uninstallation of the product and product components:
v “Frequently asked questions” on page 25
v “General installation problems and resolutions” on page 27
v “Windows installation problems and resolutions” on page 30
v “UNIX-based system installation problems and resolutions” on page 31
v “Troubleshooting z/OS-based installations” on page 33
v “Uninstallation problems and workarounds” on page 45

Frequently asked questions

General installation frequently asked questions

The following table lists general installation frequently asked questions.
Table 5. General frequently asked questions
Question Answer
Are fixpacks required if a user Fixpacks for CNP196 are delivered as each monitoring agent is migrated to IBM
migrates Candle monitoring Tivoli Monitoring.
agent to IBM Tivoli Monitoring. Note: The IBM Tivoli Monitoring download image or CD provides application
fixpacks for the monitoring agents that are installed from that CD (for example,
the agents for operating systems such as Windows, Linux, UNIX, and i5/OS).
The migration software for other agents is located on the download image or
CDs for that specific monitoring agent, such as the agents for database
applications.If you do not migrate the monitoring agent to IBM Tivoli
Monitoring, the agent continues to work. However, you must migrate to have all
the functionality that IBM Tivoli Monitoring offers.
Do presentation files and The migration from version 350 to IBM Tivoli Monitoring handles export of the
customized OMEGAMON DE presentation files and the customized OMEGAMON DE screens.
screens for Candle monitoring
agents need to be migrated to a
new zLinux system.
Does the warehouse migration No. You must back up the old warehouse database and the new warehouse
tool have a rollback function? database before running the warehouse migration tool to prevent loss of data.
For more information about running the warehouse migration tool, see the IBM
Tivoli Monitoring Installation and Setup Guide.
What if the migration tool fails? Because you backed up the source database, you can refer to the
WAREHOUSEMIGLOG table to determine which tables migrated successfully. If
you want to restart without re-migrating the successfully migrated tables, you
delete the tables that were completely migrated in the source database. Also,
delete all the data that was incompletely exported in the last tables: use the
writetime column to distinguish old data from new data.

© Copyright IBM Corp. 2005 25

 Windows installation frequently asked questions
Table 6. Windows installation frequently asked questions
Question Answer
How can I determine if Windows If the sysadmin account that you use to log on to Tivoli Enterprise Portal is not
Security logging is on? a Windows Administrator, you do not see the security log.

Windows security logging is not turned on by default. Normally, data is not

collected in the security log unless the Windows administrator turns it on. The
Record Count = 0 in the Windows monitored logs report confirm that security
logging is not turned on.
How can I diagnose problems 1. Click on Start > Programs > Tivoli Monitoring > Manage Tivoli Enterprise
with product browse settings? Services to display the Manage Tivoli Enterprise Services window.
2. Right-click the Windows agent and select Browse Settings. A text window
displays.
3. Click Save As and save the information in the text file. If requested, you can
forward this file to IBM Software Support for analysis.

UNIX-based systems installation frequently asked questions

Table 7. Frequently asked questions for UNIX-based systems installation
Problem Solution
The product was installed as root. If you installed and started the agent as root, the files do not have correct
Without re-installing the product, permissions, so the result is unpredictable. For this reason, do not use root ID
how can I change from root to either to install or start the UNIX-based systems agents. Create a user ID with
another ID? all the authority and permissions to install, run or use any other ID other than
root.

As root, run the command UnSetRoot , which is located under

install_dir/bin/ directory. This script resets all the files under the install_dir
directory, owned by root.
UnSetRoot [ -h CANDLEHOME ] userID

After executing the above script, run ″SetPerm″ command, which is located
under install_dir/bin/ directory. This command sets root permission for
certain UNIX-based systems agent files.
Where can I set Go to install_dir/config and edit the corresponding .ini file. Set the
KDCB0_HOSTNAME? KDCB0_HOSTNAME parameter followed by the IP address. If you use Multiple
network interface cards (NICs), give the Primary IP address of the Network
Interface.
How can I set the trace option to Add the following in the agent .ini file. For an example if it is KUX agent, add
capture any abends (core files)? the following line in install_dir/config/ux.ini file
KBB_SIG1=trace –dumpoff
In an environment of 50 servers Is it not necessary to change all the other UNIX-based systems agents for
with at least one agent per server, IP:PIPE. You have to configure only the agent, which connects to the Tivoli
a new agent (vt) was installed Enterprise Monitoring Server through a firewall. However, you must configure
outside the firewall. The new the Tivoli Enterprise Monitoring Server for IP.PIPE communication.
agent must be configured on
Tivoli Enterprise Monitoring While configuring the agent, which communicate through the firewall, you get
Server for IP.PIPE communication. the following options:
Is it necessary to change all the v Does the agent connect through a firewall? [YES or NO] (Default is: NO)
other UNIX-based systems agents v IP.PIPE Port Number (Default is: 1918)
for IP:PIPE?
v Enter name of KDC_PARTITION (Default is: null)

26 IBM Tivoli Monitoring: Problem Determination Guide

Table 7. Frequently asked questions for UNIX-based systems installation (continued)
Problem Solution
Does SNMP need to be turned on If you are communicating only through Tivoli Enterprise Monitoring Server you
to monitor UNIX-based systems do not need SNMP. However, if you are sending traps to the emitter through the
host? The monitoring server is Tivoli CA uni-center or HP Open-view, SNMP is required.
running WINNT4.0 and
monitoring agent is running on
HPUX?

General installation problems and resolutions

This section describes general installation problems and resolutions.

Incorrect behavior after an uninstallation and re-installation

You might experience incorrect behavior if you uninstall then reinstall the product
without rebooting. For example, you might experience the following problems:
v Inability to create trace logs.
v Agents do not start.
v Agents data is corrupt.
Reboot the system to resolve the problems.

The agent installation log on the endpoint indicates that error

AMXUT7502E occurred
The error AMXUT7512E might occur when running the Distributed Monitoring
Upgrade Toolkit. The agent was not installed for one of the following reasons:
v There is another installation in progress that cannot complete until the computer
is restarted.
–OR–
v You are attempting to install a component that is already installed.
Refer to the lcfd.log on the endpoint and the agent installation log as listed in
Table 8 to determine the exact cause of the problem.
Table 8. lcfd log file
Windows UNIX-based systems
install_dir/Install/Abort IBM Tivoli Monitoring install_dir/logs/candle_installation.log
timeStamp.log

Contact IBM Software Support if you cannot install the agent.

OS Agent does not install and a message indicates it was

already installed
The file status.properties, located in $DBDIR/AMX/data/ is not deleted when you
uninstall the Upgrade Toolkit. The Upgrade Toolkit refers to the old
status.properties file that contains information indicating there the OS Agent was
installed. You might experience this problem if you do the following in the order
listed:
1. Upgrade an endpoint.
2. Uninstall the Upgrade Toolkit.
3. Clean the endpoint manually.

Chapter 3. Installation and configuration troubleshooting 27

 4. Reinstall the Upgrade Toolkit.
5. Attempt to upgrade the endpoint you previously upgrade in 1 on page 27.
use the following steps to verify that information in the status.properties file is
causing this problem:
1. Open the status.properties,
2. Look for an entry like the following example:
#Copyright IBM Corporation 2005 #Wed Sep 14 15:54:43 CDT 2005 @Endpoint\:
\:east@EndpointClass\:TMF_Endpoint\:\:Endpoint=COMPLETE @Monitor\:Coast\
:120401@Threshold\:critical=COMPLETE

In this example, the status of the endpoint "east" is COMPLETE, which

indicates that it was upgraded successfully. The witmupgrade command does
not upgrade any item with the COMPLETE status and reports that it was
already upgraded.

To upgrade the endpoint, the status for the endpoint ″east″ must be the
INCOMPLETE, such as in the following example:
@Endpoint\:\:east@EndpointClass\:TMF_Endpoint\:\:Endpoint=INCOMPLETE

The only way to change the endpoint status in the status.properties file to
INCOMPLETE is to perform a rollback on the upgrade of the item. See the IBM
Tivoli Monitoring: Upgrading from Tivoli Distributed Monitoring.

Rolling back the upgrade

You can use the rollback option (–r option) of the witmupgrade command to
remove the new IBM Tivoli Monitoring resources that you created. This is a
necessary step if you want to repeat the test scenario. Rolling back the upgrade for
the test scenario removes the Windows OS monitoring agent from the Windows
endpoint and also removes the new situations and managed system list.

Follow these steps to roll back the upgrade:

1. Change to the $DBDIR/AMX/shared/analyze directory:
cd $DBDIR/AMX/shared/analyze
2. Type the following command to roll back the upgrade:
witmupgrade -x profilemanagers/DM_TEST_PM.xml -r -f scans/baseline.xml

where:
-x profilemanagers/DM_TEST_PM.xml
Specifies the name and location of the output file that resulted from the
assessment of the DM_TEST_PM profile manager.
-r Indicates that the purpose of this command is to perform a rollback.
-f scans/baseline.xml
Specifies the name and location of the baseline file to use as input for
this command.
3. Restart the Windows endpoint.
The rollback option can also be used to roll back an endpoint upgrade or a profile
upgrade independently. By rolling back the profile manager upgrade, you roll back
all upgrades (profile manager, profile, and endpoint) in one step.

28 IBM Tivoli Monitoring: Problem Determination Guide

 ″SQL1_OpenRequest status = 79″ return code occurs during
when upgrading an agent
The return code SQL1_OpenRequest status = 79 occurs in the agent log when the
application support is added during an upgrade. This return code results from an
attempt to delete a table entry that does not exist in the table. When you add
application support for a V6.1 agent, the return code is expected behavior because
the agent application support data does not exist in the table.

An IBM Tivoli Monitoring 6.1 upgraded agent is not configured

to point to the same Tivoli Enterprise Monitoring Server as it
was before upgrading the agent
During upgrade of agents from OMEGAMON 350 to IBM Tivoli Monitoring 6.1,
the OMEGAMON 350 agent specific Tivoli Enterprise Monitoring Server
configuration data does not persist to the upgraded IBM Tivoli Monitoring 6.1
agent. The upgraded agents are configured to use the agent default settings. Do
the following to change the default settings configured for OMEGAMON 350:
1. Right-click an agent in the Manage Tivoli Enterprise Monitoring Services
2. Select Set defaults for all agents ...

After upgrading to IBM Tivoli Monitoring V6.1, the link to the

Queue Statistics workspace in the navigation tree is incorrect
The link to the Queue Statistics workspace in the navigation tree opens the Open
Queue Handles workspace instead of the Queue Statistics workspace. Use the
following steps to correct the link:
1. Open the Queue Statistics workspace from the navigation tree.
2. Ensure that Queue Statistics workspace opened instead of the Open Queue
Handles workspace.
3. From the Tivoli Enterprise Portal select Edit > Properties.
4. Place a check in the Assign as default for this Navigator Item box.

Some rows do not display in an upgraded table

You might not see all tables after upgrading the Warehouse Proxy to IBM Tivoli
Monitoring V6.1 because some tables might be corrupted. Do the following to find
the errors that occurred during the upgrade:
1. Edit the KHDRAS1_Mig_Detail.log file.
2. Search for the word EXCEPTION.
The KHD_MAX_ROWS_SKIPPED_PER_TABLE environment variable allows you
to skip bad data. KHD_MAX_ROWS_SKIPPED_PER_TABLE indicates the number
of rows per table to skip to migrate if the data that needs to be inserted is
incorrect. When this number is reached, migration of the table is aborted.

Tivoli Enterprise Monitoring Server and Tivoli Enterprise

Portal Server automatically start after running Application
Support Installer
After running the Application Support Installer the Tivoli Enterprise Monitoring
Server and Tivoli Enterprise Portal automatically start, even if they were not
running before the install. The behavior is harmless and there is no workaround
currently.

Chapter 3. Installation and configuration troubleshooting 29

 Errors occur during installation of Event IBM Tivoli Monitoring
Event Forwarding tool
The product functions normally in spite of the error. Check the installation log for
more details.
One or more errors occured during the replacement of files (tecSyncAllFile1)
with files (tecSyncAllFile1).
Refer to install log for more details.
One or more errors occured during the replacement of files (tecSyncAllFile2)
with files (tecSyncAllFile)1.
Refer to install log for more details.
One or more errors occured during the replacement of files (tecSyncAllFile3)
with files (tecSyncAllFile1).
Refer to install log for more details.
.
.
.

Windows installation problems and resolutions

When running the setup.exe, an unknown publisher error

message displays
If you run the setup.exe from a network drive on Windows, a window displays
with the following message:
File Download - Security Warning
The Publisher could not be verified.
Are you sure you want to run this software?

Selecting Cancel closes the window and the installation cannot complete. To install
the software without this problem, map the network drive and run the setup.exe
file from a DOS prompt.

The error "Could not open DNS registry key" occurs

This message is informational an no action is required. The Windows agent reports
the fact that it could not find a registry entry for the DNS Server Event Log,
indicating that the DNS Server Event Log is not installed. You can stop all
situations and recycle the Tivoli Enterprise Monitoring Server with no situations in
ACTIVATE AT STARTUP to prevent this message being written to the trace log.

Agent not connecting to Tivoli Enterprise Monitoring Server

If you find a message similar to ″Unable to find running TEMS on CT_CMSLIST″
in the Log file, the Agent is not connecting to the Tivoli Enterprise Monitoring
Server. Confirm the following to ensure connectivity:
v Multiple network interface cards (NICs) exist on the system.
v If multiple NICs exist on the system, determine which one is configured for the
monitoring server. Ensure that you specify the correct hostname and port for
communication in the IBM Tivoli Monitoring environment.

InstallShield displays the error "1607: Unable to install

InstallShield Scripting Runtime" during installation on
Windows from a network-mounted drive
When running setup.exe on Windows from a network mounted drive, the
following error occurs:

30 IBM Tivoli Monitoring: Problem Determination Guide

 InstallShield: 1607: Unable to install InstallShield Scripting Runtime.

This is an InstallShield limitation. You cannot install the product from the specified
network drive. Try installing from another network drive. Install the product from
a local drive if you continue to receive the error.

Installation on a Windows 2003 server fails with Error Number:

0x80040707
The following error can occur while installing IBM Tivoli Monitoring V6.1 on a
Windows 2003 Server:

This error can occur for the following reasons:

1. Windows Service Pack 1 (or higher) is not installed.
2. Windows Installer 3.1 (KB893803) is not installed.
KB893803 is included in SP1. You must install Windows Service Pack 1 or higher
or the KB893803 individual update. You can download the update from
www.windowsupdate.com.

Upgrade tool deploys agent to the wrong directory

The baseline XML file used for Tivoli Distributed Monitoring upgrade contains
attributes that specify an installation directory for OS monitoring agents on Tivoli
endpoints. When an endpoint is upgraded, the Upgrade tool normally deploys the
OS monitoring agent to the specified directory on the endpoint. However, if the
CANDLE_HOME environment variable is already set on a Windows endpoint, the
Upgrade tool deploys the monitoring agent to the directory specified by the
environment variable, even if a different directory is specified in the baseline file.
The CANDLE_HOME environment variable is already set if any IBM Tivoli
Monitoring V6.1 component is already installed on the endpoint.

UNIX-based system installation problems and resolutions

This chapter describes known problems related to installation and uninstallation
that might occur with IBM Tivoli Monitoring.

Failed to attach to the DB2 instance db2inst1 ERROR: Unable

to create TEPS, return code = 3
While installing a Tivoli Enterprise Portal Server on a UNIX based system and
using a DB2 database, the following error message is displayed (where db2inst1 is
the supplied name of the DB2 instance):
Failed to attach to the DB2 instance db2inst1
ERROR: Unable to create TEPS, return code = 3

Chapter 3. Installation and configuration troubleshooting 31

 Ensure that the DB2 instance is started by running the db2start command as the
instance user:
$ su - db2inst1
$ db2start

Silent install on UNIX-based systems of Tivoli Enterprise

Monitoring Server returns an encryption key setting error
The following errors occurs if you attempt a silent install on UNIX-based systems
or UNIX-based systems and the encryption key is not exactly 32 characters.
Exception in thread "main" candle.kjr.util.CryptoFailedException:
CRYERR_INVALID_KEY_LENGTH
at candle.kjr.util.CRYPTO.validateKeyLength(CRYPTO.java:911)
at candle.kjr.util.CRYPTO.setKey(CRYPTO.java:452)
at ITMinstall.gskSetkey.<init>(gskSetkey.java:179)
at ITMinstall.gskSetkey.main(gskSetkey.java:26)

Set the encryption key parameter in the silent install file to exactly 32 characters as
in the following example:
INSTALL_ENCRYPTION_KEY=IBMTivoliOMEGAMONEncrytionKey61

The error "Unexpected Signal: 4 occurred at

PC=0xFEC3FDE4" occurs during installation
A Java VM heap dump occurs during installation, which uses the JRE. Use the
following steps to resolve the problem:
1. In a terminal window, run the following command to display the Java
command:
java -version
2. Determine where the Java executable is located by running:
which java
3. Rename or uninstall the Java executable.

Note: This effects any other applications which depend on Java. Be sure that it
is safe to do so. If unsure just rename the Java executable.
4. Run the following command again to ensure that the java executable is not
found in the path:
which java
5. Install the product.

Installation of the IBM Tivoli Monitoring on the Linux S390

R2.6 64-bit operating system fails with the message "LINUX
MONITORING AGENT V610Rnnn unable to install agent"
where nnn is the release number
Perform the following steps to resolve this problem before running the installation
again:
1. Run the following command before running any installation or configuration
command for the agent:
export JAVA_COMPILER=NONE
2. Install the s390x.rpm RPM (Red Hat Package Manager) files, in addition to the
s90.rpm files, located in the CD ISO images for Red Hat As 4.0 s390x:
v compat-libstdc++-295-2......s390x.rpm

32 IBM Tivoli Monitoring: Problem Determination Guide

 v compat-libstdc++-33-3.......s390x.rpm
It requires the two s390x.rpm files, in addition to the s390.rpm files. You can
obtain the required RPM files from the CD for Red Hat As 4.0 s390x.

The Unix OS agent (ux) version 350 does not start on AIX 5.3
after upgrading other agents to version 6.1.0
Do one of the following to enable UNIX OS agent (ux) version 350:
v Upgrade the Unix OS agent to version 6.1.0.
–OR–
v Add the following line to the uxaix513.ver file in the $CANDLEHOME/registry:
runArch = aix533

Troubleshooting z/OS-based installations

This section describes some problems you might experience with z/OS-based
installations, including problems you can resolve with the Installation and
Configuration Assistance Tool (ICAT). It includes the following sections:
v “IBM Tivoli Monitoring z/OS initialization checklist” on page 33
v “z/OS-based installations problems and resolutions” on page 40

IBM Tivoli Monitoring z/OS initialization checklist

Use the IBM Tivoli Monitoring z/OS initialization checklist to troubleshoot
problems with your IBM Tivoli Monitoring installation on z/OS. The IBM Tivoli
Monitoring z/OS initialization checklist includes the following sections:
v “Tivoli Monitoring Services Engine initialization” on page 33
v “RAS1 service initialization” on page 34
v “TCP/IP service initialization” on page 34
v “SNA service initialization” on page 36
v “The Server list” on page 37
v “Local Location Broker service initialization” on page 38
v “Global Location Broker service initialization” on page 39
v “Tivoli Enterprise Monitoring Server hub availability” on page 40

Tivoli Monitoring Services Engine initialization

Tivoli Monitoring Services Engine is a collection of basic Operating System and
Communication service routines built specifically for the OS/390 and z/OS
Operating environments. All IBM Tivoli Monitoring address spaces load and
employ the services of Tivoli Monitoring Services Engine.

Initializing the Tivoli Monitoring Services Engine service: Tivoli Monitoring

Services Engine successful initialization is noted by message KLVIN408 IBM
OMEGAMON PLATFORM ENGINE VERSION 400 READY. There are two classes
of Tivoli Monitoring Services Engine initialization failures:
v Failures that result from unsupported Tivoli Monitoring Services Engine startup
parameters. For example: User abend U0012
v Failures that result from protocol initialization failures. For example: User abend
U0200

Repairing Tivoli Monitoring Services Engine initialization failures: For U0012

Abends, invalid Engine STARTUP parameters, examine and correct the parameters
pointed to by the RKLVIN DD statement of the started task JCL. Most often, U0012

Chapter 3. Installation and configuration troubleshooting 33

 Abend failures can be resolved by backing out the last change made to the Tivoli
Monitoring Services Engine startup parameters. For U0200 Abends, the root cause
of the protocol failures must be remedied. These failures are covered in “TCP/IP
service initialization” on page 34 and “SNA service initialization” on page 36.

RAS1 service initialization

The Reliability, Availability and Servicability (RAS1) service refers to the RAS1
building block (Basic Services component) used for diagnostic tracing. Nearly all
diagnostic information for IBM Tivoli Monitoring is delivered via the RAS1 (trace)
component. This component is configured in member KBBENV of RKANPAR
using the KBB_RAS1 environment variable. Often, customers redirect the
initialization member via CT/Engine INITLIST processing. INITLIST processing is
always echoed to the RKLVLOG with the KLVIN411 message. The following shows
an example of a typical KBBENV override to KDSENV
KLVIN410 INITLIST MEMBER KDSINIT BEING PROCESSED
KLVIN411 KLVINNAM=KDSINNAM
KLVIN411 KLVINTB=KDSINTB
KLVIN411 KLVINVLG=KDSINVLG
KLVIN411 KLVINNAF=KDSINNAF
KLVIN411 KLVINVPO=KDSINVPO
KLVIN411 KLVINSTG=KDSINSTG
KLVIN411 KLVINVAM=KDSINVAM
KLVIN411 KBBENV=KDSENV

In this instance, configuration of KBB_RAS1 must display in member KDSENV of

RKANPAR.

TCP/IP service initialization

TCP/IP service is Transmission Control Protocol. TCP/IP provides end-to-end
connectivity for application-layer codes such as telnet, FTP, and the IBM Tivoli
Monitoring Server, Tivoli Enterprise Portal Server, and the Tivoli Enterprise
Monitoring Agents.

Initializing the TCP/IP service: TCP/IP services for this address space are
available if any of the following messages are present:
"KDE1I_OpenTransportProvider") Transport opened: socket/ip.tcp
"KDE1I_OpenTransportProvider") Transport opened: socket/ip.pipe
"KDE1I_OpenTransportProvider") Transport opened: socket/ip.udp

These messages are only displayed when KDC_DEBUG=Y is active in the

environment; KDC_DEBUG=Y must be added to member KDSENV of RKANPAR
(or the appropriate initialization member) to obtain the level of tracing required to
have these messages echoed to the RAS1 log. IF KDC_DEBUG=Y is set and if none
of these messages are in the log, then initialization of the TCP/IP service failed.

Repairing TCP/IP service initialization failures: Use the following steps to

ensure the TCP/IP transport service is available:

Note: Failure at any of the following prevents the TCP/IP service from initializing
in the address space.
1. Ensure the INITAPI service is successful. See “The INITAPI call” on page 34.
2. Ensure the Name Resolution is successful. See “Name Resolution” on page 35.
3. Ensure the first SEND ran without error. See “The First SEND” on page 36.

The INITAPI call

IBM’s implementation of TCP/IP requires that an address space perform an
INITAPI before issueing an TCP/IP service request. The INITAPI establishes a

34 IBM Tivoli Monitoring: Problem Determination Guide

communication pipe between the TCP/IP and the OMEGAMON Platform address
space. The INITAPI identifies the TCP/IP stack to be used by name. The TCP/IP
stack name used in the INITAPI is configured in the KLXINTCP member of
RKANPAR. This step must complete successfully. An INITAPI failure is fatal: no
TCP/IP services are available to the address space.

Confirming that the INITAPI call was successful: The following messages
indicate a successful INITAPI:
KLXIN001 HPNS INTERFACE AVAILABLE
KLXIN001 SOCKET INTERFACE TO TCPIPL AVAILABLE

Repairing the INITAPI call failures: Most of INITAPI failures are the result of
the wrong name specified in KLXINTCP. The following is a classic example of an
INITAPI failure:
KLVIN405 STARTUP MODULE: KLXINTCP, SEQUENCE(1), USING RKANPAR MEMBER KLXINTCP
KLXIN001 TCP/IP CONFIGURATION: TCP/IP_USERID=TCPIPG
KLXIN003 TCP/IP INTERFACE INITIALIZED
KLXIN009 SOCKET INTERFACE TO TCPIPG UNAVAILABLE: RC(FFFFFFFF) ERRNO(000003F3)
KLXIN004 TCP/IP INTERFACE NOT OPENED: RC(4)

Notice that the INITAPI failure is characterized by a return code of (-1) and an
ERRNO value, in this case X’3F3’ or decimal 1011. ERRNO-s have names. These
names are found in TCPERRNO.H and decimal 1011 is EIBMBADTCPNAME. The
most common INTIAPI ERRNOs are EMVSINITIAL (156),
EIBMBADTCPNAME(1011), and no-name(10218).

Reasons for INITAPI failures inlcude:

v The name specified in KLXINTCP is wrong. TCP/IP_USERID is selected based
on the specification for TCPIPJOBNAME found in the file pointed to by
SYSTCPD in the TCP/IP started task JCL. The default (if no TCPIPJOBNAME
exists) is TCPIP. There exists field documentation on the RACF procedure. These
two items should be checked first.
v The started task name does not have RACF authority for the OMVS segment.
All address spaces must be given RACF (or ACF2) permission for the OMVS
segment to use TCP/IP services. Failure to grant this permission (which is
granted to the started task name) can result in INITAPI failures.
v MAXPROCUSER has been exceeded. For MAXPROCUSER problems, you can
use console operator command SETOMVS MAXPROCUSER=xxx to increase the
current MAXPROCUSER value (as seen by D OMVS,O).

Name Resolution
IBM Tivoli Monitoring V6.1 depends on IBM’s HPNS EZASMI getaddrinfo and
EZASMI getnameinfo calls for resolver services. These calls are used to find the
symbolic name and dotted-decimal IP address of the default network interface for
the z/OS image. A failure in either EZASMI call results in failure to initialize the
TCP/IP service for the z/OS address space.

Confirming that the Name Resolution calls are successful: The following
message indicates Name Resolution was successful:
kdebprc.c,661,"interface_discovery") IPV4 interface list: ’SYSL’
9.42.46.26: source=hostname:0, seq=0, flags=0441

In this example, the interface ’SYSL’ is found and source=hostname indicates that
the hostname SYSL was successfully resolved to an IP address.

Chapter 3. Installation and configuration troubleshooting 35

 Repairing the Name Resolution failures: The following messages illustrate a
Name Resolution failure:
kdebprc.c,661,"interface_discovery") IPV4 interface list: ’WINMVS2C’
9.20.138.199: source=GE1, seq=0, flags=0441
kdebprc.c,214,"register_string") Unable to resolve interface address: WINMVS2C

In the messages above, the absence of source=hostname indicates an interface was

discovered but the name is not resolvable to an address. Typically, this error results
when the z/OS image does not contain a TCP/IP resolver setup file that provides
either GLOBAL or DEFAULT configuration data. Consequently, native z/OS
address spaces are not enabled for name resolution by default. By adding a DD
statement for SYSTCPD to the started task JCL of the IBM Tivoli Monitoring task
(pointing to a usable file in USER.PARMLIB(TCPDATA)), resolver support can be
enabled.

The following messages illustrate a varient of name resolution failure:

kdebprc.c,661,"interface_discovery") IPV6 interface list: ’NULL’
"KDE1I_OpenTransportProvider") Status 1DE00048=KDE1_STC_NOINTERFACESREGISTERED

The messages above indicate that no (IPV6) interface is registered. This can also
result in TCP/IP service initialization failure for the IBM Tivoli Monitoring address
space. The absence of an interface can only be fixed by the z/OS TCP/IP
administrator.

The First SEND

This section provides information about confirming whether or not First SEND
was successful as well as how to repair failures in the First SEND.

Confirming that he First SEND was successful: The sequence of the following
communication messages indicate the first SEND operation (an lb__lookup RPC
request) and the first RECEIVE operation:
"KDCR0_Send") request FFFF/0.0 (200): ip.pipe:#9.42.46.26[1918]
"KDCR0_InboundPacket") response FFFE/0.0 (320): ip.pipe:#9.42.46.26[1918]
"KDCL_GetBinding") Using LLB at ip.pipe:#9.42.46.26[1918]

When the first network I/O is successful, the response indicates link and transport
connectivity with the hub computer.

Repairing the failures in the First SEND: There are two consideration specific to
OS/390 and z/OS platforms:
v RACF permission to the started task for the OMVS segment
v Presence of the well known port on the TCP/IP Port List.
The RACF permission problem might not be detected until the failure of the first
network I/O. The ″KDCR0_Send″ request fails with Errno 2: EACCESS. This
failure can occur with the first use of the started task name.

A similar problem results in EACCESS: the well-known port is defined on the

TCP/IP port list. ISPF Option 6, ″netstat portlist″ confirms the presence of the
well-known port in the TCP/IP reserved port list. The well-known port should not
be on this list.

SNA service initialization

IBM Tivoli Monitoring Address Spaces can configure be configured to use SNA
exclusively, or in conjunction with TCP/IP, as a transport service. This
configuration is done in the environment member (xxxENV) of RKANPAR. If SNA

36 IBM Tivoli Monitoring: Problem Determination Guide

services are viewed as optional, then removal of KDCFC_ALIAS, KDCFC_MODE,
and KDCFC_TPNAME from the xxxENV member of RKANPAR will effectively
disable use of SNA.

Initializing the SNA: The following messages are printed in the RAS1/
RKLVLOG when the local SNA configuration is processed from the XXXENV
member of RKANPAR:
kbbssge.c,52,"BSS1_GetEnv") KDCFP_ALIAS=KDCFC_ALIAS=KLXBS_ALIAS="ASIAGLB"
kbbssge.c,52,"BSS1_GetEnv") KDCFP_TPNAME=KDCFC_TPNAME=KLXBS_TPNAME="SNASOCKETS"
kbbssge.c,52,"BSS1_GetEnv") KDCFP_MODE=KDCFC_MODE=KLXBS_MODE="CANCTDCS"
kdes1rp.c,140,"getEnv") AF_SNA configuration: Alias(ASIAGLB) Mode(CANCTDCS)
TpName(SNASOCKETS)

KDCFC_ALIAS identifies the APPL definition of the Independent Logical Unit to

be used in this process. KDCFC_MODE identifies the LOGMODE name, the same
name found in the LOGMODE specification of the KDCFC_Alias APPL definition.
KDCFC_TPNAME is the Transaction Processing Name. The message which
indicates the LOCALLU is operational (the configuration is good) is the ″transport
opened″ message:
kde1otp.c,118,"KDE1I_OpenTransportProvider") Transport opened: com1/sna.pipe

Repairing SNA initialization failures: There following lists the reasons for SNA
initialization failures:
v The ILU configured for use is not available to the application. The ACBNAME
(or APPLNAME) is properly defined in SYS1.VTAMLST but not in the
connectable state (CONCT). The ACB must be varied ACTIVE to NET prior to
Omegamon Platform Address Space startup. The MVS command to verify the
state of the ACB is ″D NET, ID=acbname,E″ .
v The ILU is available but not a valid LU6.2 definition. In this case, the is a
KBBCM001 message with an SNA sense code found in the RAS1/RKLVLOG.
Diagnose the 8-byte SNA sense code (typically, 087Dnnnn) using the ″SNA
Formats and Protocol″ manual.
v The LOGMODE is not a valid LU6.2 LOGMODE, or the LOGMODE and
MODETAB specification associated with the ILU definition are not the same, by
name, on both systems hosting the endpoints. This is most likely the case for
SNA session establishment hangs. The message in the RKLVLOG is ″Receive
XID pending: NULL″, and it is followed by another RPC timeout message.

The Server list

IBM Tivoli Monitoring processes build and query a list of possible Tivoli Enterprise
Monitoring Server hub addresses, called the Server list. This server list contains
local (LLB) and global (GLB) entries. The LLB entries of the Server list are derived.
The GLB entries of the Server list are built from the content of the KDCSSITE
member of RKANPAR. Shown below are two server lists. The first Server List is
for a Tivoli Enterprise Monitoring Server hub, the second Server List is for a
remote Tivoli Enterprise Monitoring Server. See the following example:
(Server list for a HUB CMS)
LLB entry 1 is ip:#10.248.16.1.1918.
LLB entry 2 is sna:#ATOOEN01.K10DSLB.CANCTDCS.SNASOCKETS.135.
GLB entry 1 is ip:#10.248.16.1.1918.
GLB entry 2 is sna:#ATOOEN01.K10DSLB.CANCTDCS.SNASOCKETS.135.
GLB entry 3 is ip:#10.248.16.1.1918.
GLB entry 4 is sna:#ATOOEN01.K10DSLB.CANCTDCS.SNASOCKETS.135.
(Server list for a REMOTE CMS)
LLB entry 1 is ip:#10.248.17.2.1918.
LLB entry 2 is sna:#ATOOEN01.K20DSLB.CANCTDCS.SNASOCKETS.135.
GLB entry 1 is ip:#10.248.16.1.1918.

Chapter 3. Installation and configuration troubleshooting 37

 GLB entry 2 is sna:#ATOOEN01.K10DSDS.CANCTDCS.SNASOCKETS.135.
GLB entry 3 is ip:#10.248.17.2.1918.
GLB entry 4 is sna:#ATOOEN01.K20DSLB.CANCTDCS.SNASOCKETS.135.

Confirming the Server list is correct: In general, the first half of the GLB server
list always points to the Tivoli Enterprise Monitoring Server hub. The first half of
the GLB entries in the Server list are taken from member KDCSSITE of RKANPAR.
If the LLB entries are derived (implicitly) and the GLB entries are explicitly
configured in the KDCSSITE member, you can diagnose and repair the errors in
KDCSSITE.
v The number of LLB entries must be half the number of GLB entries. If this is not
the case, then there might be a mismatch between the number of transports
services configured to this Tivoli Enterprise Monitoring Server (the
KDC_FAMILIES environment variable) versus the number of transports
configured for the hub Tivoli Enterprise Monitoring Server (KDCSSITE).
v For a hub Tivoli Enterprise Monitoring Server, each LLB entry must be identical
to the corresponding GLB entry in the Server list. As in the Server list for a hub
Tivoli Enterprise Monitoring Server example, LLB entry 1 is the same as GLB
entry 1 and LLB entry 2 is the same as GLB entry 2.
v For a remote Tivoli Enterprise Monitoring Server, the opposite is true: each LLB
entry must be different than the corresponding GLB entry in the Server list. As
in the example (Server list for a REMOTE Tivoli Enterprise Monitoring Server),
LLB entry 1 is different than GLB entry 1, LLB entry 2 is different than GLB
entry 2.

Repairing errors in the Server list: Errors in SNA initialization might be name
mismatches. Examine the LLB entries and the GLB entries for the Omegamon
Platform address space for typographical errors. The VTAM network ID is victim
of frequent error. Typically the VTAM network ID (the first component of the SNA
socket address, ATOOEN01 in the example above) is the same for ALL entries.
While it CAN differ, typically, it does not. A difference between the LLB VTAM net
ID and the GLB VTAM net ID is often an error in member KDCSSITE of
RKANPAR.

Local Location Broker service initialization

An intrinsic part of Remote Procedure Call architecture is the location broker. RPC
servers (callers of rpc__listen) publish their service and the address of this service
in a location broker. RPC clients (callers of rpc__sar) use the location broker to
obtain the address of a server prior to making a call to that server. Use of the
location broker is well-defined by the the lb__lookup() Remote Procedure Call. It is
also appropriate to mention that there are two types of location brokers: the local
location broker (LLB) and the global location broker (GLB). There is one local
location broker for every RPC server (The Tivoli Enterprise Monitoring Server has
it’s own LLB. The Tivoli Enterprise Monitoring Agent, the Warehouse Proxy agent,
and the Tivoli Enterprise Portal Server all have their own instance of a LLB.) RPC
servers, by definition, publish the service offered and address of this service in
their local location broker.

Confirming the Local Location Broker service initialized: The bind messages in
the RKLVLOG indicate the success or failure of the LLB service initialization. One
of two message IDs prefix the LLB status messages, depending on how the LLB
service was started. KDSNC007 is the message prefix issued on successful LLB
process initialization when the LLB is started internally by the Tivoli Enterprise
Monitoring Server.

38 IBM Tivoli Monitoring: Problem Determination Guide

 KDSNC004 Bind of local location broker complete= ip.pipe:#9.42.46.26.21343.
KDSNC004 Bind of local location broker complete= ip:#9.42.46.26.21343.
KDSNC004 Bind of local location broker complete= sna:
(USCACO01.VWCTHLB.CANCTDCS.SNASOCKETS).135.
KDSNC007 Local Location Broker is active

Repairing errors in Local Location Broker service initialization: Bind failures

due to insufficient authorization are reported with Errno. 2 (EACCESS)o the Local
Location Broker (as the name LOCAL implies) is done with a local socket address.
The bind fails for the following reasons:
v Insufficient authorization
v The address is unavailable
(32645848-E8E45647:kdebnws.c,64,"KDEB_NewSocket")
Status 1DE00000=KDE1_STC_CANTBIND.
(3265B3F0-E8E45647:kdebnws.c,84,"KDEB_NewSocket")
<0x176A97D4,0x10> BSD bind details:
Family 2, Socket 0, Status 1DE00000, Errno 2.
00000000 00022EE1 00000000 00000000 00000000 .................
(326B1EA8-E8E45647:kdcsuse.c,98,"KDCS_UseFamily") status=1c010005,
"cant bind socket",
ncs/KDC1_STC_CANT_BIND
2001.252 04:42:41 KDC00008 Unable to create location server, status 1C010005

Bind failures due to address-in-use:

(3ACDB600-DEB3B73F:kdebnws.c,62,"KDEB_NewSocket") Status 1DE00030=KDE1_STC_
ENDPOINTINUSE
(3ACF5028-DEB3B73F:kdcsuse.c,99,"KDCS_UseFamily") status=1c010005, "cant bind
socket", ncs/KDC1_STC_CANT_BIND

Bind failure due to address-in-use but not fatal:

(1CF7B1F8-E6D9D743:kdcsuse.c,99,"KDCS_UseFamily") status=1c010005, "cant bind
socket", ncs/KDC1_STC_CANT_BIND
KDSNC007 Local Location Broker is active

If the bind failure is due to EADDRINUSE but the Broker service is started, the
error might not be fatal. Determine whether or not the bind of this IBM Tivoli
Monitoring address space was to the LLB in that address space. In some instances,
an address space can bind to the LLB of another address space. This can only
occur in the same system image. If the bind failure is fatal, then another process on
this system image has the ’well-known’ port. Bind failures due to insufficient
authorization are fixed by granting RACF permission for the OMVS segment to the
Omegamon Platform started task name.

Global Location Broker service initialization

The Global Location Broker (GLB) differs from the Local Location Brokers in one
important respect other than the name: there is only one GLB for the domain or
enterprise. By definition, there will be only one Local Location Broker which points
to the Global Location Broker for the domain. The RPC server LLB which points to
the GLB (and there will be only one of these in an enterprise) is, by definition, the
hub. The important thing to remember from all this discussion of local and global
brokers is this: For a process to locate the Tivoli Enterprise Monitoring Server hub,
the process must query (issue lb__lookup() RPC requests to) the list of candidate
Global Location Brokers in order as specified in the global site text file (glb_site.txt
on distributed platforms and the KDCSSITE member of RKANPAR for OS/390 and
z/OS platforms). Below are the product communication messages which
enumerate the candidate GLB list (GLB entry 1, GLB entry 2, etc):

Chapter 3. Installation and configuration troubleshooting 39

 GLB entry 1 is ip.pipe:#9.42.46.26.21343.
GLB entry 2 is ip:#9.42.46.26.21343.
GLB entry 3 is sna:(USCACO01.VWCTHLB.CANCTDCS.SNASOCKETS).135.
GLB entry 4 is ip.pipe:#9.42.46.26.21343.
GLB entry 5 is ip:#9.42.46.26.21343.
GLB entry 6 is sna:(USCACO01.VWCTHLB.CANCTDCS.SNASOCKETS).135.

Connectivity between the Omegamon/XE and Tivoli Enterprise Monitoring Server

address space fails if this list is incorrect. The GLB entries display in the order in
which they are configured in the global site text file. Additionally, the address of
the local platform is appended to this list. This is an RPC architecture requirement.
It allows the local platform to be queried when the GLB list has been exhausted
and no hub is found.

Confirming the Global Location Broker service initialized: The bind messages in
the RKLVLOG indicate the success or failure of the GLB service initialization. A
message ID prefixes the GLB status messages and indicates how the GLB service
was started. KDSNC008 is the message prefix issued on successful GLB process
initialization when the LLB is started internally by the Tivoli Enterprise Monitoring
Server.
Bind of global location broker complete= ip.pipe:#9.42.46.26.21343.
Bind of global location broker complete= ip:#9.42.46.26.21343.
Bind of global location broker complete= sna:
(USCACO01.VWCTHLB.CANCTDCS.SNASOCKETS).135.
Global Location Broker is active

Repairing errors in Global Location Broker service initialization: GLB service

failures occur because there are errors in member KDCSSITE of RKANPAR. Each
socket address in KDCSSITE is assumed to be the socket address of the Tivoli
Enterprise Monitoring Server hub. If noen of the entries in the KDCSSITE file are
the correct socket address of the Tivoli Enterprise Monitoring Server hub, this
process initialization fails.

Tivoli Enterprise Monitoring Server hub availability

The following message indicates the Tivoli Enterprise Monitoring Server hub is
available:
ko4locbr.cpp,731,"Mgr::locateEverbody") lbLookupHub returned error <0>,
ip<ip:#9.42.46.26.21343>
sna<> pipe <ip.pipe:#9.42.46.26.21343.>

Do the following if the Tivoli Enterprise Monitoring Server hub is not available:
v Review the RAS1 log for the Tivoli Enterprise Monitoring Server to ensure it
properly correctly.
v Review network topology to ensure Firewall policy does not prohibit connection
initiation from the Tivoli Enterprise Monitoring Server hub.
v Review ″Transport opened″ on the Tivoli Enterprise Monitoring Server to ensure
at least one transport service is common between it and this Tivoli Enterprise
Monitoring address space.

z/OS-based installations problems and resolutions

This section describes problems that might occur with a z/OS-based installation.

How do you customize the following Tivoli Enterprise Monitoring

Server configuration values using the Configuration tool?
You can increase the following storage-related parameters if IBM Software Support
personnel instructs you to do so:

40 IBM Tivoli Monitoring: Problem Determination Guide

v Web Services SOAP Server
v startup console messages
v communications trace
v storage detail logging and associated intervals
v minimum extended storage
v primary and extended maximum storage request size
v language locale
v persistent datastore parameters
Use the following steps to increase the storage-related parameters:
1. From the Configure the Tivoli Enterprise Monitoring Server main menu,
select the Specify configuration values option.
2. On the next panel, press F5=Advanced to open the Specify Advanced
Configuration Values panel. The next panel includes the following options:
v Enable OMEGAMON SOAP Server (applicable to a Hub Tivoli Enterprise
Monitoring Server only)
v Enable startup console messages
v Enable communications trace
v Enable storage detail logging and associated intervals
v Specify the Virtual IP Address (VIPA) type
v Specify the minimum extended storage
v Specify the primary and extended maximum storage request size
v Specify the language locale for globalization
v Specify the persistent datastore parameters
3. Customize the fields with the preferred values in the Specify Advanced
Configuration Values.
4. Select the Create runtime members option to regenerate the "DS#3xxxx Create
runtime members" job from the Configure the Tivoli Enterprise Monitoring
Server main menu.
5. Submit the job and check for good condition codes.
6. Recycle the Tivoli Enterprise Monitoring Server.

'DATA SET NOT FOUND' JCL error occurs when submitting the
DS#3xxxx Tivoli Enterprise Monitoring Server 'Create runtime
members' job.
Ensure the following:
v The pp#1xxxx RTE Build job successfully ran for this RTE. To perform the RTE
Build job,
1. Place the B option next to the RTE on the KCIPRTE RTE main menu to
instruct Configuration tool generates the pp#1xxxx mRTE Build job.
2. Ensure that the RTE Build job contains allocations for the
&rvhilev.&rte.RKDS* and &rvhilev.&rte.RK* runtime libraries.
3. Submit the RTE Build job.
v The Tivoli Enterprise Monitoring Server in this RTE field is set to Y on the
RTE Update panel if the RTE Build job does not contain &rvhilev.&rte.RKDS*
libraries. If you must edit the field, regenerate the RTE Build job.
Refer to the IBM Tivoli Monitoring Installation and Setup Guide manual for more
information about configuring a z/OS Tivoli Enterprise Monitoring Server and the
RTE Build job.

Chapter 3. Installation and configuration troubleshooting 41

 The error 'CMSLIST NOT ALLOWED' occurs on the 'Specify
Advanced Configuration Values' panel when Tivoli Enterprise
Monitoring Server type equals hub.
The F10=CMSLIST key from the Specify Advanced Configuration Values panel is
only applicable to a remote Tivoli Enterprise Monitoring Server. This PF Key
allows the remote Tivoli Enterprise Monitoring Server to select a hub Tivoli
Enterprise Monitoring Server to which it can connect. The F10=CMSLIST function
key is unavailable to a hub Tivoli Enterprise Monitoring Server. Go to the previous
Specify Configuration Values panel to verify what type of Tivoli Enterprise
Monitoring Server you are configuring

The 'Enter required field' error occurs for the 'Global location
broker applid of Hub' or the 'Network ID of Hub' VTAM-related
fields
On the Specify Configuration - Hub Values for Remote Tivoli Enterprise
Monitoring Server panel, the message ″Enter required field″ occurs although the
remote z/OS Tivoli Enterprise Monitoring Server connects to the Hub Tivoli
Enterprise Monitoring Server through IP protocols. If you are configuring a remote
z/OS-based Tivoli Enterprise Monitoring Server that connects to a non-z/OS Hub
Tivoli Enterprise Monitoring Server via the IP or IPPIPE communication protocol,
use the following steps as a resolution:
1. On the Specify Configuration - Hub Values for Remote Tivoli Enterprise
Monitoring Server panel, enter any value in the following fields:
v Global location broker applid of Hub. For example, enter default
″CTDDSLB″ if this VTAM APPLID is not used.
v Network ID of Hub. For example, enter the NETID value from
SYS1.VTAMLST(ATCSTRnn)).

Note: Neither of these values adversely affect the connection for the remote
Tivoli Enterprise Monitoring Server.
2. From the Configure the Tivoli Enterprise Monitoring Server main menu,
select the Specify communication protocols option.
3. On the Specify communication protocols panel, specify the IP protocols of
choice and ensure. Specify SNA.PIPE as one of the protocols that the remote
Tivoli Enterprise Monitoring Server uses for connection.
4. Navigate forward to specify the communication protocols values for the
selected protocols.
5. From the Configure the Tivoli Enterprise Monitoring Server main menu,
select the Create runtime members option to generate the DS#3xxxx Create
runtime members job.
6. Submit the job and check for good condition codes.
7. From the Configure the Tivoli Enterprise Monitoring Server main menu,
select the Complete the configuration option.
8. Review the remaining tasks to finish the configuration of the product before
starting the Tivoli Enterprise Monitoring Server.

The pp#Mxxxx Tivoli Enterprise Monitoring Server migration job

generated by the Configuration tool ended with a condition
code=08.
The JCL used to upgrade an existing RTE to ITM V6.1 level must perform several
steps to ensure the existing data is not lost nor corrupted. The batch job stops
processing data in the event of an error, such as insufficient DASD. The batch job
is not submitted a second time but three batch job are created that can be used to

42 IBM Tivoli Monitoring: Problem Determination Guide

restore the data to its original state. Therefore, the upgrade JCL can be submitted
to run and start from the beginning to allow for conditions that initially caused the
problem to be corrected. Based on what step was running when the failure
occurred, you might need to run one or more of the following jobs in RKANSAM:
v KDSRSTRO
v KDSRSTRN
v KDSRSTRV

Use the following VSAM migration steps:

1. Run RNMEVSAM/ALLCVSAM step to:
v Rename the previous version’s VSAM file to a backup VSAM name.
v Allocate the new V610 VSAM file based on the new format.

Note: This step applies to VSAM files containing data that do not need to be
converted.
–OR–Edit and submit KDSRSTRN to restore to files to the original state.
2. Run KDSRCONV step to:
v Allocate the new V610 VSAM libraries using temporary XKDS* VSAM
names.
v REPRO the previous version VSAM file data (RKDS*) to flat file.
v Convert the fields to ASCII and resize columns accordingly. REPRO the
converted flat file to the new XKDS* VSAM libraries.
v Write out the output from the conversion.
–OR–Edit and submit KDSRSTRV to restore a file to original state.
3. Run RNMEEIBO step to rename the previous version’s VSAM files (RKDS*) to
backup VSAM names (BKDS*) if the KDSRCONV step is successful.
–OR–Edit and submit KDSRSTRO to restore file to original state.
4. Run RNMEEIBN step to rename the new V610 XKDS* VSAM libraries to the
runtime RKDS* VSAM names if the RNMEEIBO step is successful.
–OR–Edit and submit KDSRSTRN to restore to original state.

Note: By default the restore jobs runs against all of the processed datasets. The
comments section of these jobs detail that some of the datasets can be
commented out depending on the time and nature of the failure
experienced. For instance, only 4 of 7 datasets were renamed during
RNEVSAM, so only those 4 must be restored to their original names. If
you are not certain which job to run or what datasets to comment out in
these jobs, contact IBM Software Support.

The Tivoli Enterprise Monitoring Server starts normally in a

system without the Integrated Cryptographic Service Facility but
does not connect to the Tivoli Enterprise Portal Server
Although Integrated Cryptographic Service Facility (ICSF) provides robust
password encryption, you are not required to use it as it can affect compatibility
with the z/OS OMEGAMON monitoring products. Perform the following steps so
that the Tivoli Enterprise Portal Server can connect to the Tivoli Enterprise
Monitoring Server:
v During configuration:
1. Select Configure the Tivoli Enterprise Monitoring Server > Specify
configuration values > Integrated Cryptographic Service Facility (ICSF)
installed?

Chapter 3. Installation and configuration troubleshooting 43

 2. Specify N in the on the Integrated Cryptographic Service Facility (ICSF)
installed? panel.
v After the Tivoli Enterprise Monitoring Server configuration is complete and it is
running:
1. The Tivoli Enterprise Portal Server configuration must be modified to use an
older, less robust encoding algorithm. Edit the kfwenf file in
install_dir\CNPS, where install_dir is C:\IBM\ITM by default in a text editor.
2. In a line by itself, type the text USE_EGG1_FLAG=1
3. Save the document and exit.
4. Stop the Tivoli Enterprise Portal Server, if it is running, then start it.

On a system with one or more existing OMEGAMON monitoring

environments, the global CSI is corrupt and cannot be used for
installing a new version
Use the following steps manually merge existing datasets with IBM Tivoli
Monitoring V6.1 datasets only after IBM Software Support instructs you to do so:
1. Backup the following datasets:
v Runtime
v Target
v INSTDATA
v INSTDATW
v INSTJOBS
v INSTLIB
v INSTLIBW
v INSTQLCK
v INSTSTAT

Note: You must backup the specified datasets.

2. After installing the product on a new CSI, refer to the Program Directory
document to verify that the datasets contain enough allocated space for the
new libraries.
3. From the ISPF panel 3.3 or a JCL batch job, copy the contents of the new
modified Target libraries in Table 9 to their counterparts in the old Target
libraries, ensuring that like-named members are replaced.
Table 9. Modified target libraries
TKANCMD
TKANCUS
TKANDATV
TKANHENU
TKANMAC
TKANMOD
TKANMODL
TKANPAR
TKANPENU
TKANSAM
TKCIINST
TKNSLOCL

44 IBM Tivoli Monitoring: Problem Determination Guide

 4. Manually delete obsolete datasets listed in Table 10 from TKANMODL that
interfere with operation of new version of Tivoli Enterprise Monitoring Server
on z/OS.
Table 10. TKANMODL obsolete members
KLXABIND
KLXACLOS
KLXAHBAD
KLXAHBNM
KLXAINIT
KLXAINTE
KLXAOPEN
KLXAPEER
KLXARECV
KLXASELF
KLXASEND
KLXASLIH
KLXAWAIT
KLXAXDAT
KLXAXTPL
KLXI@INT
KLXI@IUC
KLXIDESP

Uninstallation problems and workarounds

This section provides information about how to troubleshoot an uninstallation.

Removing a failed installation on Windows

The following sections describe the process for removing a release that is partially
installed and cannot be removed by using the Add and Remove Programs tool.
The following topics are discussed:
Table 11. Removing a failed installation on Windows
Goal Where to find information
Remove a failed installation from computer “Removing a failed first time installation”
that has never had IBM Tivoli Monitoring or
Candle OMEGAMON installed.
Remove a failed installation from a “Removing a failed upgrade” on page 46
computer that you were trying to upgrade
from Candle OMEGAMON.

Removing a failed first time installation

Use the following steps to remove a partially installed IBM Tivoli Monitoring
installation:

Chapter 3. Installation and configuration troubleshooting 45

 1. Ensure that there is no entry in the Add and Remove Programs tool for the
component that you attempted to install. If there is an entry, use that entry to
uninstall the product. If there is no entry, proceed to the next step.
2. Open the Windows Explorer and navigate to the IBM Tivoli Monitoring
installation directory (C:\IBM\ITM by default).
3. Launch the Manage Tivoli Enterprise Monitoring Services utility by
double-clicking the KinConfg.exe file located in either the Install or InstallITM
subdirectory.
4. If any agents, the portal server, or the monitoring server are listed in the
Manage Tivoli Enterprise Monitoring Services window, right-click each and
click Advanced > Unconfigure. Repeat this step for all components that are
listed. Close the Manage Tivoli Enterprise Monitoring Services utility.
5. Open the Windows Control Panel.
6. Double-click Administrative Tools and then double-click Services.
7. Verify that all related IBM Tivoli Monitoring services have been removed.
These services match those listed in the Manage Tivoli Enterprise Monitoring
Services window.
8. Open the Registry Editor by clicking Start → Run and typing regedt32. Click
OK.
9. Expand the key HKEY_LOCAL_MACHINE registry key.
10. Expand the SOFTWARE registry key.
11. Expand the Candle registry key and record any sub-keys that are present. If
the Candle key does not exist, proceed to step 15.
12. Expand the OMEGAMON registry key under the Candle key and record the
content of the OMEGAMON key values.
13. Delete the Candle registry key and all sub-keys.
On Windows XP, you can right-click the Candle registry key and click Delete.
14. Close the Registry Editor.
15. Open the Windows Explorer and find the IBM Tivoli Monitoring installation
location on your system. The default value is C:\IBM\ITM.
16. Delete this directory and all subdirectories.
17. Remove the IBM Tivoli Monitoring bookmark from the Start menu:
a. Click Start from the Windows desktop to display the Start menu items.
b. Click Programs.
c. Right-click IBM Tivoli Monitoring to display the bookmark menu options.
d. Click Delete to remove the IBM Tivoli Monitoring bookmark from the
Windows desktop start menu.
You can now install IBM Tivoli Monitoring.

Removing a failed upgrade

To remove a failed upgrade, first ensure that there is no entry in the Add and
Remove Programs tool for the new component you are attempting to install. If
there is an entry, use that entry to uninstall the product. If there is no entry, use the
following steps to remove the failed upgrade.

The first step to removing a failed upgrade is to determine where the install failed:
either before the files were copied or after the files were copied. For GUI
installations, the files are copied after you click Next on the Start Copying Files
window. If you performed a silent installation, look for a pair of entries separated
by a blank line:

46 IBM Tivoli Monitoring: Problem Determination Guide

FirstUIBefore exiting to file copy
FirstUIAfter entry after file copy

If neither exist, then the installation failed before the files were copied. See
“Installation failed before files were copied.”

If both entries exist, the installation failed after the files were copied. See
“Installation failed after files were copied”

Installation failed before files were copied: Check to see if the entry for your
previous installation exists in the Add and Remove Programs tool. If it does not
exist, follow the instructions in “Removing a failed first time installation” on page
45. Your previous installation is too corrupt to use and must be completely
removed. You must either completely reinstall the previous release and then
upgrade to IBM Tivoli Monitoring or just install IBM Tivoli Monitoring without
attempting to upgrade.

If the entry exists in the Add and Remove Programs tool, you can still use your
existing Candle OMEGAMON installation. Launch Manage Candle Services to start
all components.

Installation failed after files were copied: If your installation failed after the files
were copied, your current installation has been corrupted by the partial installation
of IBM Tivoli Monitoring. You must either completely reinstall the previous release
and then upgrade to IBM Tivoli Monitoring or just install IBM Tivoli Monitoring
without attempting to upgrade.

Check the Add and Remove Programs tool to see if either your previously
installed Candle OMEGAMON or IBM Tivoli Monitoring is available.

If neither are available, see “Neither products are available in the Add and Remove
Programs tool.”

If one is available see “One product is available in the Add and Remove Programs
tool” on page 48.

If both are available, “Both products are available in the Add and Remove
Programs tool” on page 49.

Neither products are available in the Add and Remove Programs tool: Use the following
steps if neither Candle OMEGAMON or IBM Tivoli Monitoring exists in the Add
and Remove Programs tool:
1. Open the Windows Explorer and navigate to the IBM Tivoli Monitoring
installation directory. By default, the installation location is
C:\IBM\ITM\Install, C:\IBM\ITM\InstallITM, C:\Candle\Install, or
C:\Candle\InstallITM.
2. Launch the Manage Tivoli Enterprise Monitoring Services utility by
double-clicking the KinConfg.exe file located in either the Install or InstallITM
subdirectory. Launch the KinConfg.exe from the InstallITM directory if
possible.
3. If any agents, the portal server, or the monitoring server are listed in the
Manage Tivoli Enterprise Monitoring Services window, right-click each and
click Advanced > Unconfigure. Repeat this step for all components that are
listed. Close the Manage Tivoli Enterprise Monitoring Services utility.
4. Open the Windows Control Panel.

Chapter 3. Installation and configuration troubleshooting 47

 5. Double-click Administrative Tools and then double-click Services.
6. Verify that all related Candle OMEGAMON and IBM Tivoli Monitoring
services have been removed. These services match those listed in the Manage
Tivoli Enterprise Monitoring Services window.
7. Open the Registry Editor by clicking Start → Run and typing regedt32. Click
OK.
8. Expand the key HKEY_LOCAL_MACHINE registry key.
9. Expand the SOFTWARE registry key.
10. Expand the Candle registry key and record any sub-keys that are present. If
the Candle key does not exist, proceed to step 14.
11. Expand the OMEGAMON registry key under the Candle key and record the
content of the OMEGAMON key values.
12. Delete the Candle registry key and all sub-keys.
On Windows XP, you can right-click the Candle registry key and click Delete.
13. Close the Registry Editor.
14. Open the Windows Explorer and find the Candle OMEGAMON and IBM
Tivoli Monitoring installation directories. The default value for Candle
OMEGAMON is C:\Candle; the default value for IBM Tivoli Monitoring is
C:\IBM\ITM.
15. Delete this directory and all subdirectories.
16. Use the steps in “Verifying the uninstallation” on page 49 to verify that you
successfully removed the failed upgrade.
17. Remove the IBM Tivoli Monitoring bookmark from the Start menu:
a. Click Start from the Windows desktop to display the Start menu items.
b. Click Programs.
c. Right-click IBM Tivoli Monitoring to display the bookmark menu options.
d. Click Delete to remove the IBM Tivoli Monitoring bookmark from the
Windows desktop start menu.

One product is available in the Add and Remove Programs tool: Use the following
steps if an entry for either Candle OMEGAMON or IBM Tivoli Monitoring exists
in the Add and Remove Programs tool:
1. Attempt to uninstall both releases from the Add and Remove Programs entry.
2. If this is successful, proceed to “Verifying the uninstallation” on page 49.
3. If this is not successful and the entry has been removed from the Add and
Remove Programs tool, see “Neither products are available in the Add and
Remove Programs tool” on page 47.
4. If the entry is still present in the Add and Remove Programs tool, copy the
KINWIINS.VER file (from the \WINDOWS\VERFILES\KINWIINS.VER
directory on the installation CD) to the <itm_installdir>\Install\Ver directory,
where <itm_installdir> is the IBM Tivoli Monitoring installation directory.
Delete the KINWIINSMSTR.VER file from this directory if it exists.

Note: You might need to create the Install\Ver subdirectory if it is does not
exist.
5. Attempt to uninstall the release again. If it fails again, contact IBM Software
Support for assistance.

48 IBM Tivoli Monitoring: Problem Determination Guide

 Both products are available in the Add and Remove Programs tool: Use the following
steps if both the Candle OMEGAMON or IBM Tivoli Monitoring entries exist in
the Add and Remove Programs tool:
1. Uninstall IBM Tivoli Monitoring through the Add and Remove Programs tool.
2. Uninstall Candle OMEGAMON through the Add and Remove Programs tool.
3. Proceed to “Verifying the uninstallation.”

Verifying the uninstallation: Use the following steps to verify that you successfully
removed the failed installation:
1. Verify that the installation home directory and all contents have been removed.
2. Open the Registry Editor by clicking Start → Run and typing regedt32. Click
OK.
3. Expand the key HKEY_LOCAL_MACHINE registry key.
4. Expand the SOFTWARE registry key.
5. Verify that the Candle registry key and all sub-keys have been removed from
HKEY_LOCAL_MACHINE\SOFTWARE.

You are now ready to install IBM Tivoli Monitoring.

Incorrect behavior after an uninstallation and reinstallation

You might experience incorrect behavior if you uninstall then reinstall the product
without restarting the system. For example, you might experience the following
problems:
v Inability to create trace logs.
v Agents do not start.
v Agents data is corrupt.
Restart the system to resolve the problems.

IBM Tivoli Data Warehouse database does not uninstall

When you uninstall IBM Tivoli Monitoring, the IBM Tivoli Data Warehouse
database is not removed and the ODBC data source exists. You must remove the
IBM Tivoli Data Warehouse database and the ODBC manually.

The agent installation log on the endpoint indicates that error

AMXUT7512E occurred
The error AMXUT7512E might occur when running the Distributed Monitoring
Upgrade Toolkit. The agent was not uninstalled for one of the following reasons:
v There is another uninstallation in progress that cannot complete until the
computer is restarted.
–OR–
v The uninstallation requires stopping a process that is currently in use by a
another component.
Refer to the lcfd.log on the endpoint and agent installation log as listed in
Table 12 to determine the exact cause of the problem.
Table 12. Installation logs
Windows UNIX-based systems
install_Dir/Install/Abort IBM Tivoli install_Dir/logs/candle_installation.log
Monitoring timeStamp.log

Chapter 3. Installation and configuration troubleshooting 49

 You can manually uninstall the operating system agent by running the command
for your platform as listed in Table 13:
Table 13. Uninstall OS command
Windows UNIX-based systems
LCF_BINDIR\\..\\TME\\ITMUpgrade LCF_BINDIR/../TME/ITMUpgrade/
\\ITMUpgradeManager\\setup. ITMUpgradeManager/uninstall.sh

Contact IBM Software Support if you cannot uninstall the agent.

50 IBM Tivoli Monitoring: Problem Determination Guide

Chapter 4. Connectivity troubleshooting
This section provides descriptions of and resolutions for problems you might
experience with connectivity, including logging in, passwords, and communication
among IBM Tivoli Monitoring components. Tivoli Enterprise Portal monitors the
connections between server and client and server and host data sources
continuously. When Tivoli Enterprise Portal detects a connection error it can repair
the error and your client session can resume unaffected. Use the information in
this section to diagnose and recover from connectivity problems.

If you are running the Tivoli Enterprise Monitoring Server on z/OS, see
“Troubleshooting z/OS-based installations” on page 33 for information about
configuration problems affect connectivity.

The Tivoli Enterprise Portal Server does not start after installation
Check the following log files for messages that indicate why the Tivoli Enterprise
Portal Server did not start:
Table 14. The Tivoli Enterprise Portal Server does not start after installation
Log file For messages that indicate . . .
kfwras1.log A failure during upgrade.
The Tivoli Enterprise Monitoring ServerTivoli Enterprise
Monitoring Server hub did not connect.
install_dir\cnps\sqllib\migrate.log Any error.

Cannot log in to the Tivoli Enterprise Portal

The following table provides resolutions for problems logging in to the Tivoli
Enterprise Portal.
Table 15. Cannot log in to the Tivoli Enterprise Portal
Problem Resolution
User authorization failed v The user ID and password are correct.
-OR- v The Tivoli Enterprise Monitoring Server started.
KFWITM215E: Unable to process v The user is defined in the Tivoli Enterprise Portal Server.
logon request v The Tivoli Enterprise Portal Server database is running.
v The TEPS or TEPS2 data sources are configured.
v Security validation is active on the Hub Tivoli Enterprise Monitoring
Server.

If you still cannot log in, refer to c:\ibm\itm\cnps\logs\kfwras1.log. If you

are still unable to log in, contact IBM Software Support.
An error message displays in the Recycle the Tivoli Enterprise Portal Server.
status bar of the Logon window.
If the status bar displays the Start the Tivoli Enterprise Monitoring Server.
Validating User Credentials message
continuously, the Tivoli Enterprise
Monitoring Server stopped.

© Copyright IBM Corp. 2005 51

Table 15. Cannot log in to the Tivoli Enterprise Portal (continued)
Problem Resolution
If you select Security: Validate User Use the following steps to configure the monitoring server security setting:
for the Tivoli Enterprise Monitoring 1. In the Manage Tivoli Enterprise Monitoring Services window, right-click
Server configuration during the monitoring server.
installation you cannot login to the
2. Click Reconfigure (on Windows) or Configure (on UNIX).
Tivoli Enterprise Portal.
3. Click OK on the first configuration window.
4. Clear Security: Validate User and click OK.

Cannot connect to Tivoli Enterprise Portal Server

Before performing any of the following problem determination steps, verify that
the connection problems are not the result of firewall settings. The following table
provides resolutions for problems logging in to the Tivoli Enterprise Portal Server.
Table 16. Cannot connect to Tivoli Enterprise Portal Server
Problem Resolution
KFWITM001W Unable to 1. Check the kfw1ras.log for details if an attempt to log in fails with message
connect to Tivoli KFWITM001W. The kfw1ras.log can list any of the following messages that
Enterprise Portal Server
indicate a reason for the failure:
v SQL1224N A database agent could not be started to service a request,
or was terminated as a result of a database system shutdown or a
force command.
v SQL1226N The maximum number of client connections are already
KFWITM215E Unable to started. SQLSTATE=57030
process logon request
Both messages SQL1224N and SQL1226N occur when the Tivoli Enterprise
Portal Server attempts to validate the user ID entered in the browser.
2. Restart the database.
3. Attempt the login again.

52 IBM Tivoli Monitoring: Problem Determination Guide

Table 16. Cannot connect to Tivoli Enterprise Portal Server (continued)
Problem Resolution
A remote Tivoli Enterprise A remote Tivoli Enterprise Portal client login dialog does not connect to a Tivoli
Portal client does not connect to Enterprise Portal Server hosted on a UNIX-based system, but the following are
a UNIX-based system Tivoli true:
Enterprise Portal Server with v A local Tivoli Enterprise Portal client connects to the Tivoli Enterprise Portal
the error message: Server.
KFWITM001W Unable to connect v You can ping the Tivoli Enterprise Portal Server computer from the remote
to Tivoli Enterprise Portal computer.
Server
v A Web browser can remotely connect to http://host_name:1920 to get to the
service links, assuming the default service port of 1920 was used during
installation.
The hostname might not resolve to the correct IP address on the local Tivoli
Enterprise Portal Server host. To confirm that the hostname resolves to the correct
IP address, run the following command from the host on which the Tivoli
Enterprise Portal Server was installed:
ping hostname

–OR–
ping -s hostname

The ping command displays the IP address of the computer it pings. Ensure that
the IP address is the same as the one to which the remote Tivoli Enterprise Portal
client is attempting to connect. For example, if your Tivoli Enterprise Portal Server
is located on a host with the hostname tepshost, and the host's /etc/hosts file
includes an entry similar to the following:
127.0.0.1 localhost.localdomain localhost tepshost
Running ping tepshost displays an IP address of 127.0.0.1, which is the address
of the local loopback network interface and the reason a remote computer cannot
connect to it. In this case, you must update the /etc/hosts file to give tepshost its
own entry, as in the following example:
127.0.0.1 localhost.localdomain localhost
192.168.0.9 tepshost

Tivoli Enterprise Portal client 1. Select Start > Programs > Tivoli Monitoring Services > Manage Tivoli
cannot find Tivoli Enterprise Enterprise Services.
Portal Server
2. Check that the Tivoli Enterprise Portal Server service is running and, if not,
restart it.
3. If the Tivoli Enterprise Portal Server is started, see the KFWRAS1.LOG for any
errors reported by the Tivoli Enterprise Portal Server application.
When the server starts, an “event ID 1: KFW0001 - Tivoli Enterprise Portal
Server (Tivoli Enterprise Portal Server) startup complete” information entry is
logged.
If you see an error entry, double-click the item to see the description.

Chapter 4. Connectivity troubleshooting 53

Table 16. Cannot connect to Tivoli Enterprise Portal Server (continued)
Problem Resolution
Cannot connect to the Tivoli Do the following to determine if the Tivoli Enterprise Portal Server stopped and
Enterprise Portal Server because restart it:
it stopped. 1. On the computer where the Tivoli Enterprise Portal Server is installed, select
Start > Programs > IBM Tivoli Monitoring Services > Manage IBM Services.
2. Optional: Right-click the Tivoli Enterprise Portal Server entry and select
Change Startup from the menu.
3. In the window that opens, select System Account and place a check in the
Allow Service to Interact with Desktop box.
4. Click OK to open a command prompt window when the Tivoli Enterprise
Portal Server is started. Internal Tivoli Enterprise Portal Server commands
display in the command prompt window.
5. Verify that the Tivoli Enterprise Portal Server service is started. The Tivoli
Enterprise Portal Server is started when the following messages display:
KfwCMWServer: <timestamp>: ********* Waiting for requests *********
kfwservices: <timestamp>: Starting Service: <Configuration v1.0>
kfwservices: <timestamp>: Starting Service: <Situation v1.0>
kfwservices: <timestamp>: Starting Service: <Automation v1.0>
kfwservices: <timestamp>: Starting Service: <Startup Complete v1.0>
kfwservices: <timestamp>: ********* Waiting for requests *********
6. Do one of the following:
v If it is stopped, start the Tivoli Enterprise Portal Server.
v If it is started, recycle the Tivoli Enterprise Portal Server.
If you are running the Tivoli Do the following on the computer where the Tivoli Enterprise Portal Server is
Enterprise Portal in browser installed:
mode and reaching the Tivoli 1. In Manage Tivoli Enterprise Services, right-click the Tivoli Enterprise Portal –
Enterprise Portal Server across Browser service and select Reconfigure from the menu.
network, the network system
2. In the Launch URL field, change host name in
might not be able to resolve the
http://hostname:1920///cnp/client to the IP address of the Tivoli Enterprise
host name.
Portal Serverto specify the numerical address, for example:
http://10.21.2.166:1920///cnp/client.
3. Click OK.
4. Start Tivoli Enterprise Portal browser mode using the IP address instead of the
host name.
5. If you are still unable to connect, contact IBM Software Support.

Cannot launch the Tivoli Enterprise Portal on an XP computer after

installation with the message KFWITM215E
The message KFWITM215E: Unable to process logon request occurs. A firewall
setting on the client computer prevents the Tivoli Enterprise Portal client from
connecting to the Tivoli Enterprise Monitoring Server. Set the IBM JVM (Java
launcher) as a trusted program to allow the Tivoli Enterprise Portal client to
connect to the Tivoli Enterprise Monitoring Server. You might need to include the
IBM Java program in the programs section of your firewall software and include
the IP addresses of other Tivoli Monitoring Services components in the access
control for the firewall.

54 IBM Tivoli Monitoring: Problem Determination Guide

Tivoli Enterprise Portal Server is initializing and is not ready for
communications
If you attempt to start Tivoli Enterprise Portal just after starting the Tivoli
Enterprise Portal Server, the Tivoli Enterprise Portal Server is not ready for
requests from the client until initialization and kfwservices.exe, is fully started. The
Tivoli Enterprise Portal Server is not ready for requests from the client until its
process, kfwservices.exe is fully started. Keep the Logon window open and click
OK after waiting a moment or two.

Tivoli Enterprise Portal Server lost contact with the Tivoli Enterprise
Monitoring Server and is attempting to reconnect
This message displays when the Tivoli Enterprise Portal Server lost its connection
to the Tivoli Enterprise Monitoring Server, usually because the Tivoli Enterprise
Monitoring Server stopped or is recycling. See also
KFW_CMW_RECYCLE_DELAY.

Tivoli Enterprise Portal Server is unavailable

When a message indicates the server is unavailable, suspend further interactions
until a message indicates the server is available unless you decide to end the
current Tivoli Enterprise Portal session. When the Tivoli Enterprise Portal Server is
available again, your client session is automatically reconnected and you can
resume normal interactions. If the server is available and the client has not
reconnected after three to five minutes, exit the browser, restart the browser, and
restart a Tivoli Enterprise Portal client session.

Tivoli Enterprise Portal Server is not reconnecting

If the Tivoli Enterprise Portal Server does not reconnect, recycle the Tivoli
Enterprise Monitoring Server and restart the Tivoli Enterprise Portal Server.

Cannot reconnect to the Tivoli Enterprise Monitoring Server

This message displays after the Tivoli Enterprise Monitoring Server goes down and
attempts to reconnect. The Tivoli Enterprise Portal client attempts to log on once
again to the Tivoli Enterprise Portal Server session. After a successful logon, the
Tivoli Enterprise Portal client compares the Tivoli Enterprise Portal user authorities
that were in effect when the original logon occurred with the current Tivoli
Enterprise Portal user authorities. If any permission is different, you must restart
the client session to ensure all components are synchronized with your user
permissions. Changes to user permissions include navigator view assignment
differences since the last logon.

If you want to apply new permissions for other users immediately, make all
necessary changes and recycle the Tivoli Enterprise Monitoring Server. When the
Tivoli Enterprise Monitoring Server recycle is complete, each user is reconnected
and their user ID validated. If there were changes to their profiles, users must
restart the Tivoli Enterprise Portal client session. The Tivoli Enterprise Portal client
session doe snot to be restarted if no changes were made to their profiles.

Chapter 4. Connectivity troubleshooting 55

Tivoli Enterprise Portal Server cannot connect to the Tivoli Enterprise
Monitoring Server private interface
If the Tivoli Enterprise Monitoring Server is installed on an AIX server with a
public and a private interface, the Tivoli Enterprise Portal Server cannot connect to
the Tivoli Enterprise Monitoring Server. There are two environment variables you
can set to control which interfaces to publish. For IPV4 use
KDEB_INTERFACELIST, for IPV6 use KDEB_INTERFACELIST_IPV6. In either
address family, you can set those variables to set, restrict, or add to the interfaces
in use.
Table 17. Control interface publishing
Interface control Environment variable
To set specific interfaces KDEB_INTERFACELIST=ip4addr-1 ... ip4addr-n
for consideration: KDEB_INTERFACELIST_IPV6=ip6addr-1 ... ip6addr-n
To remove interfaces from KDEB_INTERFACELIST...=-ip4addr-1 ... -ip4addr-n
consideration: KDEB_INTERFACELIST_IPV6=ip6addr-1 ... ip6addr-n
To add interfaces for KDEB_INTERFACELIST=+ ip4addr-1 ... ip4addr-n
consideration: KDEB_INTERFACELIST_IPV6=+ ip6addr-1 ...ip6addr-n
where:
ip4addr
Specifies either a symbolic network name, or a raw form dotted decimal network address.
ip6addr
Specifies either a symbolic network name, or a raw form colon-separated hex digit network address.
Note: The plus sign must stand alone.

56 IBM Tivoli Monitoring: Problem Determination Guide

Chapter 5. Tivoli Enterprise Portal troubleshooting
This chapter describes problem you might experience with the Tivoli Enterprise
Portal.

Cannot launch the Tivoli Enterprise Portal help

The Tivoli Enterprise Portal help might not display for the following reasons:
Popup blocker
If the browser toolbar has a popup blocker running, the help does not
open whether you select Contents > Index from the Tivoli Enterprise
Portal Help menu or click Help in a window. Turn off the popup blocker.
Internet Explorer shortcut keys the same for Tivoli Enterprise Portal
Some Tivoli Enterprise Portal shortcut keys are also used by Internet
Explorer. If you are using the browser client and press F1 to open the
Tivoli Enterprise Portal help, help for Internet Explorer displays instead.
Select Contents and Index from the Tivoli Enterprise Portal Help menu.
JavaScript not enabled in Microsoft Internet Explorer
JavaScript might not be enabled in Microsoft Internet Explorer. See the
Microsoft Knowledge Base Article 236846 for troubleshooting information.

http://support.microsoft.com/default.aspx?scid=kb;en-us;236846

Help index and search text entry fields are disabled

For some reason, your browser is unable to load the Java applets necessary to
enable the Index and Search fields, and is rendering the help in Pure HTML. If you
view Tivoli Enterprise Portal help with Internet Explorer use the following steps to
resolve this problem:
1. From the Internet Explorer browser toolbar go to Tools > Internet Options >
Advanced > Java (IBM).
2. Clear the Use Java version 1.4.2 for <applet> (requires restart) check box.
If the help index and search text entry fields are still disabled after clearing the
Use Java version 1.4.2 for <applet> (requires restart) check box, see “On Linux,
IBM Tivoli Enterprise Monitoring Agent topics do not display in the Help Contents
or Index tabs” on page 57.

On Linux, IBM Tivoli Enterprise Monitoring Agent topics do not display

in the Help Contents or Index tabs
You can see the Tivoli Enterprise Portal help topics in the Contents tab, but none
for your installed monitoring agents. Change your default browser to Internet
Explorer or complete the following steps:
1. If the help is open, close the browser window.
2. On the computer where the Tivoli Enterprise Portal Server is installed, locate
the contents.htm file:
Windows:
<install_dir>\cnb\classes\candle\fw\resources\help

© Copyright IBM Corp. 2005 57

 UNIX-based systems:
Linux: <install_dir>/cnb/classes/candle/fw/resources/help
3. Rename contents.htm to contents.bak.
4. Rename contents_dhtml.htm to contents.htm.

Tivoli Enterprise Portal Navigator items are listed in an unexpected

order
When expanding items in the Tivoli Enterprise Portal Navigator, parent items
might list child items in an unexpected order. Navigator items are ordered
internally on the Tivoli Enterprise Portal Server and therefore might not reflect a
logical ordering in any particular language. Use the More... indicator at the end of
the branch of child items to append them until you locate a the item you need.

HEAPDUMPs and JAVACore files are placed on the desktops when

running Tivoli Enterprise Portal in browser mode
The Tivoli Enterprise Portal client uses the IBM Java Plug-in, which is
automatically installed on your computer with the Tivoli Enterprise Portal. You
might need to adjust the IBM Java Plug-in properties if your computer often
receives HEAPDUMPs and JAVACore files, an out-of-memory condition, when you
are logged on. This is more likely to occur in large managed enterprises. You do
not need to change the Java Runtime parameters if IBM Java 1.4.2 was the last
version installed.
1. Open the Windows Control Panel.
2. Double-click Java Plug-in for IBM Java version 1.4.2.
Additional Information: If you have multiple Java Plug-ins, Click the About tab
to verify that you have the properties for the right plug-in. The correct version
is 1.4.2. The correct entry in the Cache or Certificates tab lists IBM in the path
or in the signed certificate.
3. Click the Advanced tab.
4. Select the IBM JRE 1.4.2 from the Java Runtime Environment list.
5. In the Java Runtime Parameters field, enter -Xms128m -Xmx256m.
6. Click Apply.

Java errors occur with the IBM V1.4.2 JRE

If you experience any problems using the IBM 1.4.2 JRE use the version shipped
with IBM Tivoli Monitoring V6.1.

Tivoli Enterprise Portal has high memory usage and poor response
time
The amount of Java memory used by the Tivoli Enterprise Portal increases with the
size of the monitored environment. If the maximum Java heap size setting is too
low, the amount of time spent by the JVM performing garbage collection can
become excessive, resulting in high CPU utilization and poor response time.
Verbose garbage collection (GC) data can be used to determine if excessive garbage
collection occurs. If the percentage of time spent performing garbage collection is
greater than 5%, increase the maximum Java heap size (the -Xmx parameter) to
provide more memory and reduce garbage collection activity. For more information
about collecting verbose GC data and Java heap tuning parameter changes, refer to

58 IBM Tivoli Monitoring: Problem Determination Guide

 the IBM Developer Kit and Runtime Environment, Java 2 Technology Edition,
Version 1.4.2 Diagnostics Guide (SC34-6358-01), which is available from
http://www.ibm.com/developerworks/java/jdk/diagnosis/. Use the following
steps to increase the maximum Java heap size.
Tivoli Enterprise Portal browser client
Edit the Java heap parameters using the Java Plug-in Control Panel. Before
you change the values for the Java Plug-in, consider that any changes
affect all Java applications that use the Java Plug-in. See "Preparing your
Tivoli Enterprise Portal environment" in the IBM Tivoli Monitoring
Administrator’s Guide for more information.
1. Open the Windows Control Panel.
2. Double-click Java Plug-in for IBM Java V1.4.2 (or right-click and select
Open). If you have multiple Java Plug-ins, check that you have the
properties for the right plug-in opened: The About tab shows V1.4.2,
and the Cache or Certificates tab shows IBM in the path or in the
signed certificate.
3. In the Advanced tab, select the IBM JRE 1.4.2 from the Java Runtime
Environment list.
4. In the Java Runtime Parameters field, enter -Xms128m -Xmx256m.
5. Click Apply.
Tivoli Enterprise Portal desktop client
Edit the cnp.bat file in install_dir\CNP to change edit the Java heap
parameters.

Tivoli Enterprise Portal has high memory usage

The amount of Java memory used by the Tivoli Enterprise Portal depends on the
size of the monitored environment. The largest component of the memory usage is
for the Java heap, which contains both short-term and long-term data. When a
memory request cannot be satisfied from free Java heap storage, ″garbage
collection″ is performed to reclaim free memory. There are many Java heap tuning
parameters for IBM Java run-time environments that can be used to influence
garbage collection and memory management. Notable among these are the
minimum free percentage (-Xminf) and maximum free percentage (-Xmaxf)
parameters. IBM Java documentation provides the following descriptions:
-Xminf<number>
A floating point number, 0 through 1, that specifies the minimum free heap
size percentage. The heap grows if the free space is below the specified
amount. The default is .3 (that is 30%).
-Xmaxf<number>
A floating point number between 0 and 1, which specifies the maximum
percentage of free space in the heap. The default is 0.6, or 60%. When this
value is set to 0, heap contraction is a constant activity. With a value of 1,
the heap never contracts.

You can lower the amount of free space maintained in the Java heap at the expense
of higher CPU utilization and longer response time by setting the minimum free
and maximum free percentages to lower values.
Default values:
-Xminf0.30 –Xmaxf0.60
Consider the following values:
-Xminf0.15 –Xmaxf0.30

Chapter 5. Tivoli Enterprise Portal troubleshooting 59

 The IBM Java documentation warns that setting these values too low can cause
poor Java performance. For more information on Java heap tuning parameters,
refer to the IBM Developer Kit and Runtime Environment, Java 2 Technology
Edition, Version 1.4.2 Diagnostics Guide (SC34-6358-01), which is available from
http://www.ibm.com/developerworks/java/jdk/diagnosis/.

Data is not returned to the Tivoli Enterprise Portal client

Do the following to ensure that data can return to the Tivoli Enterprise Portal
client:
v Ensure that the Tivoli Enterprise Monitoring Agent is online.
v Verify that all the application-related files were installed with the Tivoli
Enterprise Portal Server.
v Check the kfwras1.log for errors.
v Set the following trace option in the KFWENV file:
(UNIT:ctsql INPUT)

DirectDraw thread loops infinitely causing poor Tivoli Enterprise Portal

performance
Java uses DirectDraw by default but VMWare does not support DirectDraw.
Perform the following steps for both desktop and browser clients from Manage
Tivoli Enterprise Monitoring Services to set Java Runtime not to use DirectDraw
for graphic rendering:
1. Right-click Tivoli Enterprise Portal.
2. Select Advanced > Edit Variables . . .
3. Double-click the line with sun.java2d.noddraw to open the Edit Tivoli
Enterprise Portal Parm window.
4. Ensure the value is true.
5. Click the In Use box so to place a check-mark in the box.
6. Click OK to close the window.
7. Click OK to close the configuration window.

Workflow Editor is disabled and the following tools do not display:

Event Console, Graphic View, Edit Navigator View (Navigator view
toolbar).
If you did not enable Manage Tivoli Enterprise Services during installation, the
Workflow Editor is disabled and the following tools do not display:
v Event Console
v Graphic View
v Edit Navigator View (Navigator view toolbar)
1. On the computer where the Tivoli Enterprise Portal Server is installed, select
Start > Programs > Tivoli Monitoring Services > Manage Tivoli Enterprise
Services.
2. Right-click the Tivoli Enterprise Portal Server service, point to Licensing and
select Tivoli Enterprise Portal Server from the menu.
3. In the Tivoli Enterprise Portal Service License window, enter the new license
key if one was issued.
4. Check Enable Tivoli Monitoring Services.

60 IBM Tivoli Monitoring: Problem Determination Guide

 5. Click OK.
When you click OK, the server stops and a message in Tivoli Enterprise Portal
says the server is unavailable. If you do not close the client work session, after
the server has been started again (next step), another message says your Tivoli
Enterprise Portal permissions have changed and prompts you to restart.
6. Restart the Tivoli Enterprise Portal Server and, after startup is complete, restart
the Tivoli Enterprise Portal client.

Situations are not firing

Do the following to determine why situations are not firing in the Tivoli Enterprise
Portal:
v Confirm the situation is firing in the event console.
v Ensure that the situation was distributed.
v Verify whether the situation is associated with a node in the Tivoli Enterprise
Portal Navigator.
v Ensure that the situation condition is true.
v Check the operations log of the agent.

kshsoap client fails because of missing libraries on UNIX-based

systems
On UNIX-based systems, the CandleSoapClient shell script calls kshsoap binary
from inside, while sourcing the environment. You don not need to run the kshsoap
binary, as required on a Windows platform.

Category and Message field of the universal message does not accept
DBCS
To record a DBCS IBM Tivoli Monitoring V6.1 universal message when a situation
is true, following these steps on Tivoli Enterprise Portal client:
1. Open the situation editor.
2. Select a situation.
3. Select the Action tab.
4. Check Universal Message button.
5. Move the cursor to Message or Category text field.
6. Enable Input Method (IM) for DBCS.
7. Type a key to input DBCS.
However, at step 7, nothing is set into the text field because the text field does not
accept double byte characters (DBCS). Disable the Input Method and input only
single byte characters (SBCS).

An error occurs when remotely removing an instance on Windows

The following log shows an error occurs when remotely removing an instance on
Windows.
(4300DFC2.0000-828:kbbssge.c,52,"BSS1_GetEnv") KBB_RAS1="ERROR ^>
C:\IBM\ITM\tmaitm6\logs\KNTRAS1.LOG"
(4300DFC2.0001-828:kbbssge.c,52,"BSS1_GetEnv") CANDLE_HOME="C:\IBM\ITM"
(4300DFCE.0000-828:kdytasks.cpp,1063,
"runCommand") Bad return code (3221225477) from command

Chapter 5. Tivoli Enterprise Portal troubleshooting 61

 "C:\IBM\ITM\TMAITM6\kdy_xa.exe -r DB2:FROBERTS:UD
-pc ud" (4300DFCE.0001-828:kdytasks.cpp,1066,"runCommand")
STDOUT [0 characters] is: (4300DFCE.0002-828:kdytasks.cpp,1069,
"runCommand") STDERR [76 characters] is: Error line(391): Unable to delete file:
C:\IBM\ITM\tmaitm6\KUDCMA_DB2.exe
(4300DFCE.0003-828:kdytasks.cpp,3291,"setConfig") KDY1008E Received bad return code
[3221225477] from two-way translator
command [C:\IBM\ITM\TMAITM6\kdy_xa.exe -r DB2:FROBERTS:UD -pc ud]
(4300E020.0000-864:knt10agt.cpp,243,"getBinaryPath")
Error retrieving binary path for process ID 8.
(4300E021.0000-864:knt10agt.cpp,243,"getBinaryPath")
Error retrieving binary path for process ID 8

This error can occur when the Tivoli Enterprise Monitoring Server is restarted and
the agent displays offline even though its running because the agent did not
register a heartbeat yet.

Agents display offline in the Tivoli Enterprise Portal but still fire
situations and the agent logs are report that they are running
This error can occur if the agent names in the group identified contained
embedded spaces. Agent names cannot contain embedded spaces. Edit the agent
names to remove the spaces. The CTIRA_HOSTNAME environment variable on
the agents must include a specific definition for correct agent host names.

The Tivoli Enterprise Portal displays erratic sorting behavior when

removing more than one managed system simultaneously
The Tivoli Enterprise Portal display erratic sorting behavior when you remove
multiple managed systems at the same time after clicking Remove Offline
Systems menu item from the Managed System Status view. Allow the display to
finish updating before attempting another operation.

Multiple events that occur at the same time are loaded too slowly
Manually set the variable KFW_CMW_EVENT_SLEEP in cq.ini on Linux or
kfwenv on Windows to less than 10 seconds:
KFW_CMW_EVENT_SLEEP=5

Desktop client performs poorly after installing Language Packs for IBM
Tivoli Monitoring V6.1.
Some configuration settings for the IBM Tivoli Monitoring Warehouse database can
cause performance degradation. Perform the following steps from a db2cmd
prompt to correct the DB2 settings:
1. Check the Health Monitor configuration:
db2 get dbm config | find /I "health"
2. Turn the Health Monitor off:
db2 update dbm config using HEALTH_MON OFF
3. Determine what databases IBM Tivoli Monitoring connects to:
db2 list application
4. Check system buffer pool settings on CNPS and PROXYWH databases:
a. db2 connect to CNPS db2 select * from SYSIBM.SYSBUFFERPOOLS
b. db2 connect reset
c. db2 connect to PROXYWH

62 IBM Tivoli Monitoring: Problem Determination Guide

 d. db2 select * from SYSIBM.SYSBUFFERPOOLS

(Must be a value of 250.)

5. Adjust buffer pool settings that are too high:

Note: You must be connected to that database.

db2 alter bufferpool ibmdefaultbp size 250
6. Disconnect all applications:
db2 force application all
7. Stop DB2:
db2stop
8. Start DB2:
db2start
9. Recycle Tivoli Enterprise Portal Server service.

Existing OMEGAMON product imagery displays after upgrading to IBM

Tivoli Monitoring V6.1
Existing OMEGAMON product imagery displays after upgrading because there it
was cached on the client browser. Use the following steps to correct the problem:
1. Close all browser instances.
2. Clear the browser cache.
3. Reload the Tivoli Enterprise Portal browser client.
4. Verify the correct images display.

Chapter 5. Tivoli Enterprise Portal troubleshooting 63

64 IBM Tivoli Monitoring: Problem Determination Guide
Chapter 6. Tivoli Enterprise Portal Server troubleshooting
This chapter describes problems that might occur with the Tivoli Enterprise Portal
Server. If you do find the resolution to a problem you experience with the Tivoli
Enterprise Portal Server in this chapter, see Chapter 4, “Connectivity
troubleshooting,” on page 51.

Tivoli Enterprise Portal Server performance is slow

If you want to increase the performance of your portal server and you are not
concerned about security, you can disable Secure Socket Layer data encryption on
the portal server. If you do not want to use Secure Socket Layer communication
between IBM Tivoli Monitoring components and the Tivoli Enterprise Portal server,
use the following steps to disable it:
1. In Manage Tivoli Enterprise Services, right-click Tivoli Enterprise Portal server.
2. Click Advanced > Edit ENV file.
3. Find the following line:
kfw_interface_cnps_ssl=Y
4. Change the Y to N.
5. Save the file and exit.
6. Click Yes when you are asked if you want to recycle the service.

Corba user exception is included in the Tivoli Enterprise Portal Server

log when creating situations
When a user creates a new situation, the situation name must be unique. To verify
that the new name is unique, the software attempts to access a situation by the
new name. If the situation is found, then the name is already used and the user
must select a new name. If the request fails, then the name is not already used.
The failure to find the situation name is reflected in the log as the CORBA
exception. The CORBA user exception indicates that the name is unique.

© Copyright IBM Corp. 2005 65

66 IBM Tivoli Monitoring: Problem Determination Guide
Chapter 7. Tivoli Enterprise Monitoring Server troubleshooting
This section describes problems that might occur with the Tivoli Enterprise
Monitoring Server and provides resolutions to recover from those problems. It
includes the following sections:
v “Troubleshooting Tivoli Enterprise Monitoring Server problems on distributed
systems” on page 67.
v “Troubleshooting Tivoli Enterprise Monitoring Server problems on z/OS
systems” on page 69.

Troubleshooting Tivoli Enterprise Monitoring Server problems on

distributed systems
The problems described in this section might occur on distributed systems. For
information about configuring the Tivoli Enterprise Monitoring Server, refer to the
IBM Tivoli Monitoring Installation and Setup Guide .

Remote Tivoli Enterprise Monitoring Server lost connection to

the hub Tivoli Enterprise Monitoring Server and all agents
display offline
Check the log for error messages in the RAS1 trace log that indicate timestamp
problems such as Ignoring invalid lastTimeStamp. This error occurs because you
synchronized the time on the hub and remote Tivoli Enterprise Monitoring Server
with another time server. Restart the Tivoli Enterprise Monitoring Server
experiencing the errors because timers and POSIX (timed waits, for example)
depend on reliable system time.

The addSystem command fails with error message

KUICCR099E
The KUICCR099E error occurs when at least one incorrect parameters was
specified. When adding managed systems with the addSystem command, ensure
that you
v Specify the correct product code. Product codes are case-sensitive.
v Specify a correct node that is online. You can run the listsSystems command to
verify that the node is online.
v Specify correct properties.
tacmd addSystem {-t|--type} TYPE
[{{-n|--node} MANAGED-OS} |
{{-d|--dir|--directory} NODEDIR}}} ]
[{-i|--imagePath} IMAGEPATH]
[{-p|--property|--properties} NAME=VALUE ...]

where:
-t|--type
Specifies the type of managed system to add to the monitoring system. You
can specify a managed system type name or its associated two-character
code. Use viewDepot to display a list of correct managed system types.

© Copyright IBM Corp. 2005 67

 -n|--node
Specifies the node to start. A node is identified by the managed operating
system that it contains.
MANAGED-OS
Specifies a correct managed operating systems.
-d|--dir|--directory} NODEDIR
Specified the correct name of the directory that contains the node
components, including the OS agent. This syntax is only correct when the
node is on the local machine.
-i|--imagePath
Specified the correct directory that contains agent install images.
-p|--property|--properties
Specifies one or more NAME=VALUE pairs that identify configuration
properties of the new system and their values. Run the
describeSystemType command to determine correct values for the
properties.

The listSystems command consumes high CPU in enterprise

environments
In enterprise environments with many managed systems, high CPU consumption
is expected behavior for the listSytems command.

The configureSystem command does not return an

informational error when incorrect parameters are specified
Verify that you specify correct input for the system name and properties when
running the configureSystem command.

Log indicates Hub Tivoli Enterprise Monitoring Servers are

down when they are up
The statusPut process fails periodically, resulting in an incorrect hub status. This
condition is harmless and does not cause any operational change by the software.
The following is an example of the log:
Tue Jun 14 04:27:01 2005 KO41039 Error in request sqlRequest. Status= 1103.
Reason= 1103.
(42AEA2E5.0011-6:ko4sndrq.cpp,855,"IBInterface_sqlRequest") Distributed request
failed
(42AEA2E5.0012-6:ko4state.cpp,3519,"IBInterface_sendInsert") send insert has no
request handle error
(42AEA2E5.0013-6:ko4ibput.cpp,1407,"IBInterface:insertProcessing")
General error <1103>
(42AEA2E5.0014-6:ko4ibput.cpp,1657,"IBInterface::put_sList")
table put error <1103>
(42AEA2E5.0015-6:ko4ibstr.cpp,1139,"IBStream::insertDef") IB Err: 1103
(42AEA2E5.0016-6:ko4crtsq.cpp,5547,"IBInterface_refreshIB") Hub is not there
(42AEA2E5.0017-6:ko4crtsq.cpp,5547,"IBInterface_refreshIB") Hub is not there
(42AEA2E5.0018-6:ko4crtsq.cpp,5547,"IBInterface_refreshIB") Hub is not there
(42AEA2E5.0019-6:ko4crtsq.cpp,5547,"IBInterface_refreshIB") Hub is not there
(42AEA2E5.001A-6:ko4crtsq.cpp,5547,"IBInterface_refreshIB") Hub is not there
Tue Jun 14 04:27:01 2005 KO41034 Monitoring for situation UADVISOR_OMUNX_SP2OS
ended.
(42AEA2E5.001B-6:ko4crtsq.cpp,5547,"IBInterface_refreshIB") Hub is not there
Tue Jun 14 04:27:01 2005 KO41036 Monitoring for situation UADVISOR_OMUNX_SP2OS
started.
(42AEA3C3.0000-6:kdssqrun.c,2995,"Fetch") QueryRowset error. status 302
Tue Jun 14 04:30:43 2005 KO41039 Error in request Notify. Status= 1105.

68 IBM Tivoli Monitoring: Problem Determination Guide

 Reason= 302.
(42AEA3C3.0001-6:ko4async.cpp,4744,"IBInterface::completeRequest") Close failed
request <55BE90>
(42AEA53C.0000-6:ko4ibstr.cpp,1090,"IBStream::insertDef")
Ret code 155 indicates hub connection lost.
Attempting to switch hubs o
r reconnect.
(42AEA53C.0001-6:kdcgbin.c,118,"KDCG_Bind") Using GLB at ip:#9.48.157.26[1918]
(42AEA53D.0000-6:ko4crtsq.cpp,6456,"IBInterface::restartAllObjects")
No access list records changed
(42AEA53D.0001-6:ko4mxque.cpp,97,"MutexQueue::~MutexQueue") Reply store <FcO798B8>
still associated with request <503D98>: info.re
ply <FC0798B8> info.oType <5546> info.oName <INSERTO4SRV.TNODESTS> info.sitName
<*noname*>
info.reqState <-1> info.physicalIO <1>
info.logIt <0> info.reqGen <412>
Tue Jun 14 04:37:01 2005 KO41034 Monitoring for situation UADVISOR_OMUNX_SP2OS
ended.
Tue Jun 14 04:37:02 2005 KO41036 Monitoring for situation UADVISOR_OMUNX_SP2OS
started.
(42AEA61B.0000-6:kdssqrun.c,2995,"Fetch") QueryRowset error. status 302
Tue Jun 14 04:40:43 2005 KO41039 Error in request Notify. Status= 1105.
Reason= 302.
(42AEA61B.0001-6:ko4async.cpp,4744,"IBInterface::completeRequest")
Close failed request <61D5E0>

Tivoli Enterprise Monitoring Server does not release memory

after running a large SQL query
Running a query for data beyond a 24-hour period consumes high CPU and
memory because the data is not stored on the server and must be retrieved from
the endpoints. All users might experience low system performance while a large
amount of data is retrieved from endpoints.

Tivoli Enterprise Monitoring Server aborts unexpectedly when

exiting the telnet session used to start it
A UNIX-based systems Tivoli Enterprise Monitoring Server aborts unexpectedly
when exiting the telnet session used to start it, either from the client or the
command line. If you start the Tivoli Enterprise Monitoring Server from a Bourne
shell, the Tivoli Enterprise Monitoring Server session terminates when you exit the
telnet session. Do the following so you can exit the telnet session without shutting
down the Tivoli Enterprise Monitoring Server.
1. Enter the Korn shell (ksh).
2. Start Tivoli Enterprise Monitoring Server.

Troubleshooting Tivoli Enterprise Monitoring Server problems on z/OS

systems
This section includes describes problems you might experience with Tivoli
Enterprise Monitoring Server on z/OS and provides resolutions. It covers problems
that occur during run-time that you can resolve with the Installation and
Configuration Assistance Tool (ICAT). For more information about configuring the
Tivoli Enterprise Monitoring Server on z/OS, refer to the Configuring Tivoli
Enterprise Monitoring Server on z/OS manual.

Chapter 7. Tivoli Enterprise Monitoring Server troubleshooting 69

 The Tivoli Enterprise Monitoring Server start task (CANSDSST
default) encountered error message 'KLVST044 LOADLIST
MEMBER NOT FOUND IN RKANPAR DATASET (KDSLLIST)
KppLLIST KLVST001 CANDLE ENGINE INITIALIZATION
ERROR(S), ABEND U0012' in the RKLVLOG at startup
The Tivoli Enterprise Monitoring Server start task (CANSDSST default)
encountered error message ″KLVST044 LOADLIST MEMBER NOT FOUND IN
RKANPAR DATASET (KDSLLIST) KppLLIST KLVST001 CANDLE ENGINE
INITIALIZATION ERROR(S), ABEND U0012″ in the RKLVLOG at startup. Ensure
the following conditions:
v The pp#2xxxx RTE Load job ran successfully for this RTE:
1. To perform the RTE Load, place the L option next to the RTE on the
KCIPRTE RTE main menu. The Configuration tool generates the pp#2xxxx
RTE Load job.
2. Submit the RTE Load job. The RTE Load job populates the &rhilev.&RTE.RK*
runtime libraries by copying required elements from the SMP/E target
high-level qualifiers (&thilev.TK*).
v If the RTE Load job was performed, then the job references the &thilev.TK*
SMP/E target datasets from where the members are copied. Ensure the datasets
are correct SMP/E target datasets where &svhilev.CSI is installed.
v If the RTE Load job does not reference any &thilev.TK* SMP/E target datasets or
generates an incomplete RTE Load job, then ensure that the Configuration tool
references the correct SMP/E target high-level qualifiers. The Configuration tool
only generates appropriate IEBCOPY TK*-->RK* steps for SMP/E target datasets
that it can access.

Use the following steps to ensure that the Configuration tool references the correct
SMP/E target high-level qualifiers:
1. From the Configuration tool main menu, select Install products or
maintenance > Set up product or maintenance environment >Specify
environment information.
2. Verify that the values for the high-level qualifiers are correct. If the high level
qualifiers values are not the correct, use the following steps to unlock the
SMP/E high-level qualifiers:
a. Run &shilev.INSTLIB.
b. On the Installation tool main menu, select Services and utilities > Unlock
SMP/E high-level qualifiers.
c. Specify Y on the Unlock SMP/E high-level qualifiers? field.
d. Edit the high-level qualifier modifications on the Specify installation
environment information panel.
3. Go to the RTE main menu and regenerate the RTE Load job.

Cannot encrypt text. A call to CSNBSYE failed. Cannot encrypt

contents of keyfile
On the Specify configuration values option on the ″Configure the Tivoli
Enterprise Monitoring Server main menu, you can provide the Integrated
Cryptographic Service Facility (ICSF)-related values for password encryption.
These values generate the KAES256 step in the Tivoli Enterprise Monitoring Server
″Create runtime members″ job. To create the encryption key file (KAES256) in the
&rte.RKANPAR library. If within this step, the error occurs, this message indicates

70 IBM Tivoli Monitoring: Problem Determination Guide

 that ICSF is not configured correctly in your system. Consult with your system
administrator. Refer to the Configuring Tivoli Enterprise Monitoring Server on z/OS
manual for more information about configuring a z/OS Tivoli Enterprise
Monitoring Server and the security-related information.

The error ″KLVST005 MVS JOBSTEP AUTHORIZATION

REQUIRED KLVST001 CANDLE ENGINE INITIALIZATION
ERROR(S), ABEND U0012 CSV019I - Required module
KLVSTWTO not accessed, it is not APF Authorized
(RKANMODL) CSV028I - ABEND 306-0C″ occurs in the z/OS
Tivoli Enterprise Monitoring Server RKLVLOG during startup
Ensure that the load libraries, including RKANMOD and RKANMODL are
correctly APF-authorized. Additionally, in the Configuration tool Complete the
configuration step, specify that any runtime libraries concatenated in the STEPLIB
DDNAME and in the RKANMODL DDNAME of the Tivoli Enterprise Monitoring
Server started task must be APF-authorized.

The error ″KLVSQ000 carved mode in effect for extended

storage″ occurred in the RKLVLOG during startup
You can increase the MINIMUM() storage settings in the &rhilev.&rte.
RKANPAR(KDSSYNSIN) member if IBM Support personnel instructs you to do so.
The default value for the MINIMUM() parameter is MINIMUM(150000,X). Use the
following steps to increase this value or any other storage-related parameters:
1. On the Configure the Tivoli Enterprise Monitoring Server main menu, select
the Specify configuration values option.
2. On the next panel, navigate to the F5=Advanced key.
3. Do the following on the Specify Advanced Configuration Values:
v Edit the Minimum extended storage field to 300000 K.
v Edit the Maximum storage request size fields to 16 (Primary) and 23
(Extended).
4. On the Configure the Tivoli Enterprise Monitoring Server main menu, select
the Create runtime members option to generate the DS#3xxxx Create runtime
members job. Submit the job and verify good condition codes.
5. Recycle the Tivoli Enterprise Monitoring Server.

Error message 'KDSMA013 OPEN VTAM for VDM1APPL failed

with status 8' occurs in the Tivoli Enterprise Monitoring
Server start task (CANSDSST default)
Error message ″KDSMA013 and the task ends in ″ABEND=S000 U0200
REASON=00000000 KDSMA003 Tivoli Enterprise Monitoring Server data collection
server ended successfully″. Ensure the following:
1. The KDS_VTAMID= parameter exists in the &rhilev.&rte.RKANPAR(KDSENV)
member. If it does not exist, then ensure that the Tivoli Enterprise Monitoring
Server is configured correctly. Refer to the ″Configuring Tivoli Enterprise
Monitoring Server on z/OS manual for more information about configuring a
z/OS Tivoli Enterprise Monitoring Server.
2. If the KDS_VTAMID= VTAM APPLID exists, ensure that the Tivoli Enterprise
Monitoring Server VTAM major node is activated correctly.

Chapter 7. Tivoli Enterprise Monitoring Server troubleshooting 71

 For more information, review the Complete the configuration option on the
Configure the Tivoli Enterprise Monitoring Server main menu.

72 IBM Tivoli Monitoring: Problem Determination Guide

Chapter 8. Tivoli Enterprise Monitoring Agent troubleshooting
This chapter describes problems you might experiences with the Tivoli Enterprise
Monitoring Agent deploy tool and Tivoli Enterprise Monitoring Agents. If you do
not find the resolution to a problem you experience with a Tivoli Enterprise
Monitoring Agent, refer to the agent-specific user guide listed in “IBM Tivoli
Monitoring library” on page vii section of this book.

Agent deploy operations are not completing before the TIMEOUT

expires
When running agent deploy operations, TIMEOUTs can occur because of slow
network connections or slow hardware. The agent deploy operations can complete
if you increase the TIMEOUT value. Some operations can complete even after a
timeout is returned.
Table 18. Resolutions for agent deploy operations that TIMEOUT
Problem Resolution
KDY0014E Increase the Tivoli Enterprise Monitoring Server timeout value to 1200
message seconds (TIMEOUT=1200). The default is 600 seconds.

On Windows: installation_dir\CMS\KBBENV.

On UNIX-based systems: installation_dir\host_name_ms_Tivoli

Enterprise Monitoring Server_ID.config.
KDY1009E Increase the OS agent timeout to 600 seconds (TIMEOUT=600). The
KDY1017E default is 300 seconds.
KDY1018E
KDY1022E On Windows: installation_dir\CMS\KNTENV.
KDY1025E
KDY1030E On UNIX-based systems: installation_dir\ux.ini. On Linux, set it in
KDY1033E installation_dir\lz.ini. The value must be set in seconds:

A system error Increase value for the TACMD_TIMEOUT environment variable to 30

occurs when minutes. (TIMEOUT=30). The default is five minutes.
running a tacmd
command. On Windows:

Enter the following command:

set TACMD_TIMEOUT=30

UNIX-based systems:

Enter the following command:

export TACMD_TIMEOUT=30
A failure occurs The Tivoli Enterprise Portal Server times out waiting for deployment
when deploying action to complete. The default timeout is 600 seconds. You can change
an agent from the the timeout setting to KFW_SQL1_ASYNC_NOTIFY_MAX_WAIT in
Tivoli Enterprise kfwenv:
Portal. KFW_SQL1_ASYNC_NOTIFY_MAX_WAIT=1000
KUICCN068E Increase the timeout value in seconds by adding ″-o TIMEOUT=3600″
error when to the createnode command.
running tacmd
createnode.

© Copyright IBM Corp. 2005 73

The createnode command fails to connect to a UNIX-based systems
target system
If you run the createnode command on a machine with only sshd running, you
must configure the sshd to allow password authentication. Do the following steps
to enable password authentication:
1. Edit the /etc/ss/sshd_config file on the target computer.
2. Locate the following line:
PasswordAuthentication no
3. Change the no to yes and save the file.
4. Restart the daemon.

Note: If you are using private key authentication in your environment, you do
not need to set SSH to permit password authentication.

If the createnode command fails to connect after enabling password authentication,

run the following command with each protocol (ssh, rexec, rsh) specified explicitly
with the -h parameter to determine which protocol is used for the connection
attempt:
createnode -h [{ssh|rexec|rsh}://]host[:port] ...

Errors are logged in $CANDLEHOME/logs/trace_cn.log.

addBundles command times out adding UNIX bundles to Windows

depot
When using the addBundles command to add UNIX bundles to a Windows depot,
the command might time out. The default timeout is 300 seconds (5 minutes). The
following message is returned after successful execution:
KUICAB022I: The following bundles were successfully added to the
C:\IBM\ITM\CMS\depot\depot

If the addBundles command times out, this message is not returned. Set the
TIMEOUT environment variable to more than 300 before running the addBundles
command. For example:
#set TIMEOUT=600

You can also reset the TIMEOUT after the command times out. Run the
removeBundles command to remove any complete or partial bundles that were
added to the depot before the command timed out. Then run the addBundles
command.

74 IBM Tivoli Monitoring: Problem Determination Guide

createNode command fails
Table 19 on page 75 provides information to help you recover when the createNode
command fails.
Table 19. createNode command fails
Symptom Resolution
The createNode Because tacmd on UNIX and Linux is a wrapper script for the
command fails on a createNode command, the character ″\″ is removed from the
Windows OS agent command. Specify the path with the ″-d″ option using either ″/″ or
from a UNIX or ″\\\\″ when you deploy a Windows OS agent from a UNIX/Linux
Linux host when host. The following examples display the correct usage to install the
using the ″-d″ option Windows OS agent in the path C:\ITM61\WIN\OSAgent:
and ″\″ as the path
Windows
separator.
C:/ITM61/Win/OSAgent
UNIX or Linux
c:\\\\ITM61\\\\Win\\\\OSAgent
createNode On Windows systems, ensure that there are no trisvc* services
command fails on running. If there are trisvc* services running, stop them and remove
Windows system. them. The trisvc binary is used to run remote executions on
Windows. Ordinarily it is automatically removed after an operation,
but in rare cases, that removal fails and the existence of the service
might cause subsequent operations to fail. Run the installation
again, adding --option JLOG_LEVEL=DEBUG_MAX to the command
string to increase the amount of debugging information in the trace
log by a significant amount. After the operation completes, examine
the trace log for messages that indicate a reason for the failure. If
access to the target computer is available, run the installation again,
adding --option AUTOCLEAN=NO to the command string. On the
remote system, examine the contents of the ~CSRI0 directory in the
system temporary directory searching for information that indicates
the reason for the failure. When the investigation is complete, all
~CSRI# directories must be completely removed.
createNode The createNode command fails and there are errors in the
command fails with $CANDLEHOME/logs/trace_cn.log file. There might be a corrupt
return code: 2. or inconsistent IBM Tivoli Monitoring software depot.
The agent installation appears to have failed.
Return code: "2" (0 was expected)

Remove all software from depot directory, recreate the depot, and
deploy the OS agent again.
createNode on a Determine if Server Message Block (SMB) signing is required on the
Windows system target system by looking at the following security setting:
fails to connect with 1. From a Windows start menu, select Program Files > Control
the KUICCN035E Panel > Administrative Tools > Local Security Policy Under
message. Local Policies > Security Options.
2. Ensure the following Security Settings are disabled:
v Server: Digitally sign communication (always)
v Client: Digitally sign communication (always)
If the system belongs to a domain and these settings are defined
at the domain level, you must change them in the Domain
Security Policy.
Note: Disabling these settings reduces the security of the SMB
protocol. See http://support.microsoft.com/?kbid=887429 for more
information about SMB signing.

Chapter 8. Tivoli Enterprise Monitoring Agent troubleshooting 75

An agent does not display in the Tivoli Enterprise Portal or in the
output from the listSystems command
If an agent has a node name that consists of more than 32 characters, the OS Agent
and the monitoring agent (for example the Universal Agent or UNIX-based
systems Log Agent) have same node name, for example
″vision90.tivlab.austin.ibm.com:K, and only one of the agents displays in Tivoli
Enterprise Portal and in the output from the listsystems CLI command.
1. Edit $CANDLEHOME/config/<agent>.ini
2. Add the following statement to the <agent>.ini file:
CTIRA_HOSTNAME=<unique_name>

where:
unique_name
Specifies a unique name that consists of less than 32 characters.
3. Save the <agent>.ini file
4. Stop the agent.
5. Start the agent.

UNIX-based systems Log agent was deployed, configured, and started

but returns the KFWITM290E error
The Tivoli Enterprise Portal Server is timing out waiting for deployment action to
complete. The default timeout is 600 seconds. You can change the timeout setting
to KFW_SQL1_ASYNC_NOTIFY_MAX_WAIT in kfwenv.
KFW_SQL1_ASYNC_NOTIFY_MAX_WAIT=1000

KDY1024E error displays when configuring the run-as user name for
an agent
The error message KDY1024E displays when configuring the run-as user name for
an agent when the UNIX-based systems monitoring agent was installed as a
non-root user. For UNIX-based systems, you can only configure the run-as user
name if the UNIX-based systems/UNIX-based systems monitoring agent was
installed using the root user. In this case, leave the entry for the run-as user blank
or set the run-as user to the same user ID used to install the UNIX-based systems
monitoring agent.

Viewdepot did not return any information

A depot was not found. Ensure that the depot was set correctly.

New agents do not display in the Tivoli Enterprise Portal navigator

The Tivoli Enterprise Portal navigator does not update automatically when an
agent is installed or uninstalled from to the managed system. You must refresh the
navigator to display changes. Do the following to refresh the navigator from the
Tivoli Enterprise Portal menu:
v Press the F5 key on your keyboard.
–OR–

76 IBM Tivoli Monitoring: Problem Determination Guide

 v Click View > Refresh.

An agent does not start on a Solaris system

The log shows error messages such as the following:
(42D58E75.001B-1:kglcry.c,204,"checkICCStatus") ICC error detected
(42D58E75.001C-1:kglcry.c,172,"printICCStatus") majRC=2, minRC=3, mode=0
(42D58E75.001D-1:kglcry.c,174,"printICCStatus") desc=Unable to load
/icc/osslib/libcrypto.so.0.9.7
(42D58E75.001E-1:kglcry.c,2196,"initializeICC") ICC attachment failed

These log messages indicate that you are running the IBM Tivoli Monitoring agent
on Solaris 2.9 hardware, which is not supported. Install the IBM Tivoli Monitoring
agent on Solaris 2.10 hardware.

An agent displays unavailable in the Tivoli Enterprise Portal

The agent is not online. Do the following to ensure the agent is online:
v Check the agent log for data communication errors.
v Check the managed system status in the Tivoli Enterprise Portal.
v Ensure that the agent process started.
v Check the Tivoli Enterprise Monitoring Server kfwras1.log for errors.
v Check the Tivoli Enterprise Portal Server kfwras1.log.

Chapter 8. Tivoli Enterprise Monitoring Agent troubleshooting 77

78 IBM Tivoli Monitoring: Problem Determination Guide
Chapter 9. Universal Agent troubleshooting
This chapter describes problems that might occur with the Universal Agent.

Preliminary Universal Agent problem determination

Correct operation of the IBM Tivoli Monitoring requires correct application data
definitions, environment variables, and Tivoli Enterprise Monitoring Server and
Tivoli Enterprise Portal configuration. Many problems are caused by incorrectly
formatted data or data interpretation. Therefore, begin Universal Agent problem
determination with the data provider.

Before troubleshooting a problem with the Universal Agent, review the following
list of fundamental Universal Agent problem determination tasks.
v Validate the metafiles using the console command VALIDATE. Review the
validation messages and report. Resolve all identified errors and warnings.
Because the IBM Tivoli Monitoring calls the same validation subroutines when it
loads a metafile, it encounters the same problems as the KUMPCON VALIDATE
program.
v Verify that the first three characters of the application name defined in the APPL
statement of the metafile are unique throughout the enterprise.
v Verify that the sequence of data fields on the data record matches the listed
sequence of attributes in the metafile. In addition, ensure that the attribute type
and the maximum data value size correspond to the actual application data
values.
v Verify that the actual data fields are delimited exactly as specified in the
delimiter specification of the ATTRIBUTES statement. If the delimiter is specified
as NONE, ensure that defined attribute value sizes exactly match the data values
on the application data record.
v For FILE Data Providers, verify that only one file source (SOURCE FILE
statement) is specified for each attribute group (NAME statement) or that you
used ManagedSystemName to distinguish the sources.
v For SOCK Data Providers, verify that you have the correct socket source host
name (SOURCE SOCK) specified for the application.
v Examine the UAGENT DPLOG report in Tivoli Enterprise Portal. It might
include messages that provide clear indications concerning data provider
operation and the data source disposition.

Universal Agent does not start

The Universal Agent did not allocate its DCH port 1919 for one of the following
reasons:

© Copyright IBM Corp. 2005 79

Table 20. Universal Agent does not start
Problem Explanation
Another Universal Agent The following are the last messages that display in the Universal Agent RAS1 log.
process is running on the same kum0sock.c,110,"KUM0_OpenLocalSocket") bind failed for local address
system and the other Universal UDP socket 512, port=1919, = error=10048 kum0sock.c,110,
Agent was not shut down. "KUM0_OpenLocalSocket") bind failed for local address TCP
socket 512, port=1919, error=10048 kumdsock.cpp,964,
"ipcSock::allocateDCHport") Error: Could not open TCP/UDP
sockets bound to universal agent DCH port 1919
kumdsock.cpp,965,"ipcSock::allocateDCHport")
Determine if another copy of
Universal Agent is already active on this system. Exiting...
There is a non-Universal Agent
process running on the same
Note: In the RAS1 log above, the Winsock error code 10048 indicates the ″Address
system and the Universal
is in use″. On UNIX-based systems platforms, the equivalent ″Address in use″
Agent was not shut down.
error code is usually 125. Run netstat –a for more information about port usage
on the local system.Stop the other process if it is not required. If the other process
is required, set KUMA_DCH_PORT=nnnnn in the KUMENV or um.ini file. The
environment variable causes the Universal Agent to allocate a different DCH port
during startup.
An incorrect value for the The following error messages display in the Universal Agent RAS1 log if an
variable KDCB0_HOSTNAME incorrect value is specified for the host name of the Tivoli Enterprise Portal Server
was specified. running on a different machine:
kbbssge.c,52,"BSS1_GetEnv") KDCB0_HOSTNAME="10.6.43.96"
kum0sock.c,132,"KUM0_OpenLocalSocket") bind failed for local address \
UDP socket 456, port=0, error=10049
kumdsock.cpp,1648,"ipcSock::IPCClient") Error: _sockUDP[-1] error=0
kumdipc.cpp,134,"DCHipc::startup") Error: IPCClient failed.
kumdsock.cpp,185,"ipcSock::ipcSock") Error: startup failed. _sockError=1
kumdsock.cpp,190,"ipcSock::ipcSock") Error: _sockError=1
kum0sock.c,132,"KUM0_OpenLocalSocket") bind failed for local address UDP \
socket 488, port=1919, error=10049
kum0sock.c,132,"KUM0_OpenLocalSocket") bind failed for local address TCP \
socket 488, port=1919, error=10049
kumdsock.cpp,1009,"ipcSock::allocateDCHport") Error: Could not open TCP \
UDP sockets bound to Universal Agent DCH port 1919, UDP Errno: 10049, TCP \
Error: 10049. Exiting...

10049 is a Winsock error code meaning ″Address not available″ and is a result of
Universal Agent attempting to bind to an IP address that’s not on the local system.
Specify the correct value for the KDCB0_HOSTNAME variable.

The sysxlogins report is empty in the TIVOLI_DATA_WAREHOUSE

ODBC application
Use the steps to determine why the sysxlogins report is empty in the
TIVOLI_DATA_WAREHOUSE ODBC application.
1. Check the UAGENT DPLOG for the ODBC DP for error messages.
2. Resolve any errors. If there are no error messages, the log indicates that
monitoring started for the sysxlogins table.
3. Verify that other attribute groups for this metafile display data.
If other attribute groups display data, the connection to the data source is
performing as expected and only the sysxlogins report is having the problem.
4. Check the RAS1 log for error messages pertaining to the sysxlogins attribute
group, including message that state data was not found for key attributes srvid
and sid.

80 IBM Tivoli Monitoring: Problem Determination Guide

 The following example shows that indexed key attributes srvid and sid are not
defined with a value. Therefore all four rows in the attribute group table were
skipped, resulting in error an empty sysxlogins report.
***** No ODBC table data found for key attribute <srvid> row #1
in attribute group <sysxlogins>, skipping this row...
***** No ODBC table data found for key attribute <srvid> row #2
in attribute group <sysxlogins>, skipping this row...
***** No ODBC table data found for key attribute <srvid> row #3
in attribute group <sysxlogins>, skipping this row...
***** No ODBC table data found for key attribute <sid> row #4
in attribute group <sysxlogins>, skipping this row...
5. Check the sysxlogins attribute group in the generated
TIVOLI_DATA_WAREHOUSE metafile for the following data:
//NAME sysxlogins K 300 @System table
//SOURCE ODBC ’Tivoli Data Warehouse’ user=sa pswd=tivoli
//SQL Select * from dbo.sysxlogins
//ATTRIBUTES
srvid C 999999 KEY
sid D 88 KAY ATOMIC
xstatus C 999999
xdate1 D 24
xdate2 D 128 KAY ATOMIC
password D 256
dbid C 999999

Note: When ODBC metafile generation occurs, every column defined in the
catalog as indexed receives the KEY specification in the associated
Universal Agent attribute. KEY attributes in any Universal Agent
metafile must have a correct value or the row is not sent to the data
server. The srvid and sid columns are not correctly defined as indexed
because they often do not contain a value.
6. Remove the KEY specifications for these two attributes and refresh the metafile.
The table can maintain the KEY designation because there is another attribute
in sysxlogins marked as KEY.

Universal Agent console program fails to connect

The Universal Agent console interface, implemented with the um_console shell
script on Unix and and the kumpcon program on Windows, requires a successful
socket connection to the main Universal Agent process. The following error
message can occur whenever you issue a Universal Agent console command or a
Distributed Monitoring Upgrade Toolkit command:
KUMPS005E Unable to connect to console command server on myhost[7700]

This error can occur for the following reasons:

v Universal Agent is not currently running.
v An alternate instance of Universal Agent is running. Alternate instances do not
use the default console server listening port number of 7700. Instead, the first
alternate instance uses 8700, the next instance uses 9700, and so on. To target the
correct alternate instance, set the KUMP_DPCONSOLE_PORT environment
variable. See the following example:
KUMP_DPCONSOLE_PORT=8700
kumpcon import monitor.mdl
v There is a firewall on the system that blocks the socket connection between the
Universal Agent console program and the Universal Agent process. If all port
communications on the system require explicit permission, then the kumpcon
program must be granted access to the console server listening port.

Chapter 9. Universal Agent troubleshooting 81

Previously defined situations display in the Tivoli Enterprise Portal
with a Problem or Error status
Situations with a problem or error status are most likely the result of running
um_cleanup, which deletes the Tivoli Enterprise Portal Server catalog and attribute
files and the Tivoli Enterprise Portal Server ODI files for all Universal Agent
applications. When the Tivoli Enterprise Portal Server and Tivoli Enterprise Portal
server are recycled, they detect situations with no corresponding definition files.
These situations are flagged as a problem until the application definition files are
regenerated and uploaded again to the Tivoli Enterprise Portal Server and Tivoli
Enterprise Portal Server.

All Universal Agent-emitted traps display with the same severity

Many different policy-generated traps are sent by Universal Agent to a 3rd party
SNMP Manager product, but all the traps show up with the same severity and it’s
not the severity specified in the policy definition. Turn on the Universal Agent
environment variable KUMP_TRAP_USE_POLICY_SEVERITY:
KUMP_TRAP_USE_POLICY_SEVERITY=Y

The Managed system version suffix increases

Each time the Universal Agent is restarted, the managed system version suffix for
an application is incremented even though the metafile has not changed. There are
two metafiles activated that have the same three-character application prefix. If the
metafiles are activated one after the other, the Universal Agent determines that the
three-character application was modified and registers a new version suffix and
upload new CAT, ATR, and ODI files.

Tivoli Enterprise Portal column headings are missing for a Universal

Agent application
A Universal Agent application is online to Tivoli Enterprise Portal but all of its
column headings are missing in the application workspace.

The Universal Agent-generated CAT, ATR, and ODI files were not uploaded to the
Tivoli Enterprise Portal Server and Tivoli Enterprise Portal Server directories. The
most current and accurate copies of these definition files are in Universal Agent’s
work directory. If necessary, you can copy or FTP these files from the work
directory to the appropriate Tivoli Enterprise Portal Server and Tivoli Enterprise
Portal Server directories.

A variation of this problem is that some of the column headings display but not all
of them, or the column headings are incorrect. This could indicate old or
out-of-synch CAT, ATR, and ODI files in the Tivoli Enterprise Portal Server and
Tivoli Enterprise Portal Server directories. Again, you can always synchronize these
files by copying them from the Universal Agent work directory and recycling the
Tivoli Enterprise Portal Server and Tivoli Enterprise Portal Server.

Another possible explanation is that Universal Agent is connected to a remote

Tivoli Enterprise Portal Server, and the Universal Agent-generated CAT and ATR
files for the application didn’t get propagated to the hub Tivoli Enterprise Portal
Server. Tivoli Enterprise Portal Server only queries the hub Tivoli Enterprise Portal
Server, so it’s unable to retrieve the data rows. Copy or FTP the Universal

82 IBM Tivoli Monitoring: Problem Determination Guide

 Agent-generated CAT and ATR files from the remote Tivoli Enterprise Portal
Server to the hub Tivoli Enterprise Portal Server.

Tivoli Enterprise Portal charts and graphs do not work for numeric
data
Tivoli Enterprise Portal charts and graphs for a Universal Agent application are
empty even though the attributes are defined as ″N″ in the Universal Agent
metafile. The Universal Agent ″N″ attribute type means DisplayNumeric. It is a
string representation of a numeric attribute that can include non-numeric
characters, such as a floating point number or a large number with comma
separators. A DisplayNumeric attribute is a string in the ODI file and is not eligible
for Tivoli Enterprise Portal charting and graphing. If you want to use a Universal
Agent attribute in a chart or graph, define the attribute in the metafile as a true
numeric attribute, for example:
v C for Counter
v G for Gauge

kumstrap and kumsnetd processes do not start

After running itmcmd agent start um on UNIX-based systems, the following error
messages display:
elsun02% itmcmd agent start um
itmcmd agent : installer level 350 / 552.
itmcmd agent : running sol25 jre.
Starting agent . . .
Note: Universal agent process kumsnetd did not start.
NOte: UNiversal agent process kumstrap did not start.
Agent Started . . .

When you check the Universal Agent RAS1 log file, the following messages
display at the bottom:
-16:kum0sock.c,132,"KUM0_OpenLocalSocket") bind failed for local address
UDP socket 71, port=162, error=13
-F:kumsrcfg.c,73,"KUMS_ReadNetConfigFromExt")
Network configuration file /control1/dbisk/
candleUa410/sol276/um/work/KUMSNETS open failed,
ErrorText <No such file or directory>. \
Load network configuration bypassed
-18:kbbssge.c,52,"BSS1_GetEnv") KUMP_SNMP_NET_DISCOVER_ENTERPRISE="N"
Network configuration discovery tasks started.
-17:kumsrcfg.c,267,"KUMS_ReadRouterConfigFromExt") Router configuration
file /control1/dbisk/ candleUa410/sol276/um/work/KUMSROUT open failed,
ErrorText <No such file or directory>. \
Load router configuration bypassed 17:kumsrcfg.c,294,
"KUMS_ReadRouterConfigFromExt") 0 router record(s) loaded from router
configuration file /control1/dbisk/candleUa410/sol276/um/work/KUMSROUT
-19:kbbssge.c,52,"BSS1_GetEnv") KUMP_SNMP_MANAGE_LOCAL_NETWORK="N"
-16:kumsplst.c,167,"KUMS_PrepareListenSNMPtrap") *****
Unable to open SNMP trap listen port
-16:kumsplst.c,193,"KUMS_PrepareListenSNMPtrap")
Note: Determine if another SNMP Manager \
process is active on this system.
Monitoring of SNMP traps disabled. No trap receiving port or API available.
Insufficient process authority for executing ICMP procedures.
-17:kum0sock.c,132,"KUM0_OpenLocalSocket") bind failed for local address
UDP socket 71, port=520, error=13
-17:kumslrtu.c,148,"KUMS_ListenRouterUpdates")
***** unable to open socket with router \
well-known port-17:kum0sock.c,132,"KUM0_OpenLocalSocket")

Chapter 9. Universal Agent troubleshooting 83

 bind failed for local address UDP socket 73, \
port=520, error=13
-17:kumslrtu.c,148,"KUMS_ListenRouterUpdates")
***** unable to open socket with router well-known port

The error=13 indicates a permission failure. The Universal Agent was not started
with a root ID so the trap receiving and router/network discovery processes did
not acquire the low-numbered ports needed. The kuma610 continues to run
without those two processes.

Note: The kumstrap and kumsnetd processes are required only if you configured
the SNMP data provider on a UNIX-based system with the following
environment variables specified:
v KUMP_SNMP_MONITOR_TRAP=Y
v KUMP_SNMP_NET_DISCOVERY=Y
You can correct the authorization problem either by doing one of the following:
v Start the Universal Agent with a root ID.
–OR–
v Use the SetPerm script in the /bin directory to grant root access to the kumstrap
and kumsnetd binaries.
If you use the SetPerm script to grant root access to kumstrap and kumsnetd,
you do not need to start Universal Agent with a root ID for the two processes to
start successfully. Because the kumsnetd process has the necessary root authority
to acquire port 520, you can ignore the following error messages in the Universal
Agent RAS1 log file:
kum0sock.c,134,"KUM0_OpenLocalSocket") bind failed for local address UDP
socket 67, port=520, errno=13
kumslrtu.c,148,"KUMS_ListenRouterUpdates") ***** unable to open socket with
router well-known port

The Universal Agent stops functioning if the system IP address

changes while it is running
If a network connection failure occurs and the UA system is assigned a different IP
address after the reconnection, UA will stop processing new input data because of
socket bind failures. Recycle the Universal Agent so that it uses the new IP
address.

'Unable to get attribute name for tablename/column' error occurs in

the Tivoli Enterprise Monitoring Server log after creating a a situation
After creating a situation for Universal Data Provider to fire event, the following
error occurs in the Tivoli Enterprise Monitoring Server log file:
(4320916A.0049-F60:kfaottev.c,1572,"Translate_ResultBuffer")
Unable to get attribute name for tablename/column <UAG524400.UA4>. Ignored.

The Tivoli Enterprise Monitoring Server log messages are harmless for Universal
Agent applications because of the time lag between the issuing of the messages
and when the Universal Agent-uploaded attribute files are stored at the Tivoli
Enterprise Monitoring Server. However, if these messages occur for other agent
applications, they can indicate that the agent attribute files were not installed on
the Tivoli Enterprise Monitoring Server.

84 IBM Tivoli Monitoring: Problem Determination Guide

SNMP data provider problems
This section describes symptoms and tips for diagnosing SNMP data provider
problems.

SNMP-MANAGER Trap workspace is unavailable in many

columns
Every Independent Software Vendor (ISV) product that emits a trap to the SNMP
DP must have a Type 2 and Type 3 record with a unique enterprise OID defined in
Universal Agent trapcnfg file in Universal Agent work directory. When a trap is
received, the SNMP data provider looks up the trap enterprise OID value, generic
trap number, and specific trap number in the trapcnfg. The trap definition values
received by the SNMP data provider must match the definitions in the trapcnfg
file. If the SNMP data provider does not find a match for the values in the
trapcnfg, it sets the status of the trap as ″Unavailable″ in the SNMP-MANAGER
Trap table attributes. Although the traps are received, they display the
″Unavailable″ status in the SNMP-MANAGER Trap workspace.

The following example shows an intelliWatch trap definition:

intelliWatch-Monitor {1.3.6.1.4.1.1983.1.1}
(Type 2)
criticalAlarm {1.3.6.1.4.1.1983.1.1} 6 1 A 1 0 "Status Events” (Type 3)

where:
1983 Specifies the Enterprise OID.
6 Specifies generic trap number.
1 Specifies the specific trap number.

Define the correct traps values in the trapcnfg file in the Universal Agent work
directory.

The TRAP workspace does not display expected traps

For the SNMP to receive traps from SNMP agents, the trap destination list of the
monitoring agent must include the host name or IP address of the host on which
the Data Provider resides. Configuration of SNMP agents varies from monitoring
agent to monitoring agent. Refer to your SNMP monitoring agent documentation.

If you are not receiving traps ensure that:

v SNMP is in the list of data providers being started
v The host of the SNMP Data Provider is configured to receive traps
v Agents are configured to send traps to the host of the SNMP data provider.
v That the trap listener started successfully by checking the UAGENT DPLOG
workspace for the SNMP Data Provider
v KUMP_SNMP_MONITOR_TRAP is not set to N
v You add the trap description data to the file trapcnfg if a trap field shows
UNAVAILABLE,

SNMP metafiles are imported but MIB data collection is not

working
The MIB application workspaces are empty after initiating MIB data collection
(Take Action > Monitor Start).

Chapter 9. Universal Agent troubleshooting 85

Table 21. MIB data collection is not working
Problem Resolution
The community name was not specified correctly for the Use an MIB browser or freeware utility such as snmputil
SNMP agent. to retrieve MIB variables from this SNMP agent to
determine the source of the problem.
The SNMP agent is not responding to any SNMP Get
requests.
The MIB OIDs on the SNMP agent host do not match the
OIDs specified in the Universal Agent metafile.
The agent does not respond to basic SNMP Get requests All SNMP agents support the MIB2 OIDs such as
from Universal Agent. SysName and SysLocation. Use the rfc1213 metafile to
establish a baseline of functionality. Use the Universal
Agent RFC1213_mib-2.mdl to collect MIB-2 data from the
agent to verify that the SNMP agent responds to basic
SNMP Get requests from Universal Agent.

Universal Agent-emitted traps are not received by third-party

SNMP Manager
The policies are configured to emit SNMP traps, but the traps do not display in the
receiving system console. Use the following table to determine the source of this
problem.
Table 22. Universal Agent-emitted traps are not received by third-party SNMP Manager
Symptom Explanation
There are error Error messages indicate why the policy is not being driven, for
messages in the example:
Universal Agent RAS1 kumaeagt.cpp,154,"kum_kumact_agent::TakeSample")
log in the Error: could not find terminator in
kumaeagt.cpp <Local_Time.Day_Of_Week> = ’02’ AND Local_Time.Day_Of_Week <=
module. ’06’ AND Local_Time.
Time>= ’053000’ AND Local_Time.Hours <= ’21’ AND
Queue_Statistics.Current_Depth >= 12800 \
AND STRSCAN(QMQUEUES.QNAME, ’ACK’) = 0;> tok1 @NULL tok2
@NULL tok3 @NULL attrValTemp <>

The kumaeagt.cpp module implements Universal Agent’s Alert

Emitter probe. Any error messages in this module might indicate
that the policy request never got to the Universal Agent module
that sends the traps.
There are no error If the Universal Agent RAS1 log has no error messages, check
messages in the whether there are error messages in the Tivoli Enterprise
Universal Agent RAS1 Monitoring Server log. If there are errors that report a duplicate
log but the traps are CAT and ATR files, there might be a name conflict with other
not received. installed IBM Tivoli Monitoring emitters.
Search for errors In an MVS-based Tivoli Enterprise Portal Server, a "cmd failed"
showing policies reason code indicates the KUMATR and KUMCAT files are
ending with a "cmd missing from RKANDATV.
failed" reason code.

86 IBM Tivoli Monitoring: Problem Determination Guide

 Table 22. Universal Agent-emitted traps are not received by third-party SNMP
Manager (continued)
Symptom Explanation
If the Universal Agent A firewall might prevent communication between the machine
RAS1 log contains where Universal Agent is running and the machine where the
"SNMP trap emitted SNMP Manager product is running.
to destinations(s) ..."
Security rules might filter, block, or divert SNMP traps.
messages, but the
traps do not display Configuration steps might be required on the SNMP Manager
on the 3rd party product so that it can receive and display the Universal Agent
SNMP Manager traps.
console. The SNMP Manager product might have a log file that indicates
whether it receives or rejects the Universal Agent traps.
If the host name of the Universal Agent SNMP Data Provider is
added as a trap destination, the Universal Agent Emitter traps do
not display in the SNMP-MANAGER Trap workspace.

The NETWORK workspace is empty

Ensure the following:
v The host where the SNMP Data Provider is running is TCP/IP configured.
v You can ping the default router/gateway from the host of the SNMP Data
Provider.
v You have initiated network discovery using Take Action > Manage Start.

A MIB workspace is not showing expected data

For MIB workspaces to display data, you must initiate data collection using the
Monitor Start option of the Take Action feature. If you are still not receiving data:
v Ensure that the correct metafile was loaded.
v Confirm that the correct target monitoring agent nodes were specified in the
Monitor Start window, separated by commas.
v Confirm that the node and correct community name were entered in brackets.
The following example displays correct formatting if the SNMP community
name of the target is not the default (public) nor specified by
KUMP_SNMP_NET_COMMUNITY, and there is no entry in the KUMSCOMM
file:
{athens IBM}

Take Action > Manage Start or Take Action > Manage Stop is
not working
Ensure the following for the Manage Start and Manage Stop Take Action to work:
v The address is correct if you entered the network address manually (rather than
selecting it in the NETSUMMARY workspace).
v The destination managed system you specified when distributing the action is
host name:SNMP-MANAGERNN.

The SNMP Data Provider does not start with IBM Tivoli
Universal Agent
Ensure you included SNMP as a value for environment variable
KUMA_STARTUP_DP.

Chapter 9. Universal Agent troubleshooting 87

 You do not see the TakeAction options
Seed the Tivoli Enterprise Monitoring Server with KUM.SQL and restart the Tivoli
Enterprise Monitoring Server and Tivoli Enterprise Portal sessions.

A managed system for a MIB application does not come

online as expected
Ensure that you imported the application metafile either through the console
command IMPORT or updating your KUMPCNFG file. Check your DPLOG
workspace in the application UAGENT for error messages regarding the importing
of the metafile.

The NETSUMMARY workspace does not show expected data

Ensure that you can ping the default gateway or router from the host running the
SNMP Data Provider.

A MIB workspace displays empty when you expect to see data

A MIB workspace displays empty if the community name used for the SNMP
query was not the correct one for a particular SNMP monitoring agent.

To determine that a MIB workspace is empty as a result of an invalid community

name, monitor for the Authentication failure trap from the SNMP monitoring
agent. Assuming the SNMP monitoring agent is configured to generate traps to the
host running the SNMP DP, you can browse your SNMP-MANAGER TRAP
workspace to look for Authentication failure traps (Generic trap number 4).

88 IBM Tivoli Monitoring: Problem Determination Guide

Chapter 10. Database troubleshooting
This chapter provides information you need to solve problems you might
experience with the database. It covers data loss prevention information and
descriptions of common problems and appropriate resolutions. It also addresses
issues you might experience with the IBM Tivoli Data Warehouse and Warehouse
Proxy agent.

Data loss prevention

This section provides information about utilities you can use to back up and
restore databases.

Backing up the database for recovery purposes

You can use the following utilities to back up the database:
Table 23. Utilities for backing up the database
migrate- The migrate-export.bat utility backs up the entire database by writing its
export.bat contents as insert statements to a flat file called saveexport.sql located in
install_dir\cnps\sqllib. It can also be used to move the contents of the
database from one database instance to another. You might use this utility to
move the contents of the database from one windows server to another.
migrate- This utility is used to read the contents of the saveexport .sql file created in
import.bat the migrate-export process and insert them back into the database. This
utility can be used to recover the database. It reads the contents in the
install_dir\cnps\sqllib\saveexport.sql and rebuilds the database tables and
contents. You can also use the migrate-import.bat to move the contents of
the database to another windows server running the database.
1. Run migrate-export.bat
2. Copy the saveexport.sql file from the old Tivoli Enterprise Portal Server
to the new Tivoli Enterprise Portal Server into the install_dir\cnps\sqllib
directory.
3. Run migrate-import.bat to read and build the database tables and
contents on the new machine.

Restoring the original database contents

The migrate-clean.bat utility cleans the contents of the database. Use the
migrate-clean.bat file with caution. You must backup the database before running
the migrate-clean.bat file or you lose all customization of the database. When you
restart the Tivoli Enterprise Monitoring Server, the database is restored to its
original state after installation. This is a quick way to reset the database back to its
original state. After running this bat file and restarting the Tivoli Enterprise
Monitoring Server server, the original content provided by IBM Tivoli Monitoring
is restored to the database.

Tivoli Enterprise Portal Server user ID

The database requires the following user IDs:

© Copyright IBM Corp. 2005 89

 db2admin
This ID is added when you install the database and is required by the
product installer when you configure the Tivoli Enterprise Portal Server
data source.
TEPS This ID is added during installation for creating the Tivoli Enterprise Portal
Server data source.

If the Windows Local Security Settings are enabled for long or complex passwords,
ensure your password meets those syntax requirements for these IDs. If your
Windows environment requires you to change passwords regularly do the
following to change the Tivoli Enterprise Portal Server database user account
password.

Note: The following instructions do not apply in UNIX-based systems.

1. On the computer where the Tivoli Enterprise Portal Server is installed, be sure
you are logged on to Windows with an ID having administrator authority.
2. From your Windows desktop, select Start > Programs > Tivoli Monitoring
Services > Manage Tivoli Enterprise Services.
3. Right-click the Tivoli Enterprise Portal Server and select Advanced > Utilities >
Build Tivoli Enterprise Portal Server Database from the menu.
4. Click DB2 to open the Tivoli Enterprise Portal Server Data Source Config
Parameters window.
5. Enter the Admin Password.
6. Enter the new Database Password for the Tivoli Enterprise Portal Server
Database User ID.

Tivoli Enterprise Portal Server cannot connect to the database

If an error message displays indicating the connection failed for security reasons,
the end user is logged in to the server with a userid with administrator authority,
but is logged into the local domain instead of locally on the machine. The user
does not have authority to create a data source and register with windows, or the
authority to create a windows user account. Continue installing the software, using
the following steps to resolve the error:
1. When the install completes, log off the current Windows user session and log
in with using the db2admin userid.
2. Run install_dir\installITM\DB2DataSource.exe from Windows Explorer or a
command prompt. You can run this program again, even if one or more of the
tasks completed the first time it ran.
3. Start the Tivoli Enterprise Monitoring Server after the software indicates the
Tivoli Enterprise Portal Server configuration was successful.

If the Tivoli Enterprise Portal installation is complete but it does not start, the data
source might not be defined. Go to the install_dir\cnps\kfwras1.log file. If error
messages similar to the following are present in the log, the data source was not
defined.
[IBM][ODBC Driver Manager]
Data source name not found and no default driver specified.

Use the follow steps verify whether or not the data source was created and resolve
the problem:
1. Open the ODBC datasource window: Start > Settings > Control Panel >
Administrative tools and double-click the Data Sources (ODBC) .

90 IBM Tivoli Monitoring: Problem Determination Guide

 2. Verify that the Tivoli Enterprise Monitoring Server IBM DB2 ODBC DRIVER
datasource is defined.
3. If the IBM DB2 ODBC DRIVER data source is not present, run the
install_dir\installITM\DB2DataSource.exe file.
4. Read the error messages after running the program.
5. If the error is security related or mentions incorrect user IDs or passwords, log
in to the windows server with the db2admin user account and run the
db2datasource program.

If the password for db2admin changes, the logon information for the services must
also change, otherwise the Tivoli Enterprise Portal Server database does not start
because the DB2 processes cannot logon. Use the following steps to resolve this
problem:
1. From a Windows desktop, select Start > Control Panel > Administrative Tools
> Services
2. Scan the column on the right for the value .\db2admin
3. Do the following for each .\db2admin value:
a. Open the Properties window.
b. Select the Log On tab.
c. Type the new password for the user.

Data did not migrate from the Microsoft SQL Server database to the
DB2 Universal Database
You can run the movefrom-m2i.bat located in the install_dir\cnps directory to
recover the contents of the Universal Database. The movefrom-m2i.bat utility
creates a flat file from the SQL server database contents and imports into the
Universal Database. The movefrom-m2i.bat utility runs during the installation of
the Tivoli Enterprise Portal when the option to migrate from Microsoft SQL Server
to the Universal Database is selected but can also be used after installation or
routine Tivoli Enterprise Portal usage. This migration utility can fail if the Tivoli
Enterprise Portal userid and password do not have the correct authority to connect
to the Tivoli Enterprise Monitoring Server Universal Database. The
movefrom-m2i.bat requires that the Microsoft SQL server database is on the same
Windows platform as the Tivoli Enterprise Monitoring Server server and the new
Universal Database installation. Use this utility only after migration problems and
before customizing Tivoli Enterprise Monitoring Server. The movefrom-m2i.bat is
only used to migrate the contents of Microsoft SQL Sever to Universal Database.

Database contents are incorrect after installation

You can run the movefrom-m2i.bat located in the install_dir\cnps directory to
recover the contents of the database. The movefrom-m2i.bat utility creates a flat file
from the SQL server database contents and imports into the Universal Database.
The movefrom-m2i.bat utility runs during the installation of the Tivoli Enterprise
Portal when the option to migrate from Microsoft SQL Server to the Universal
Database is selected but can also be used after installation or routine Tivoli
Enterprise Portal usage. This migration utility can fail if the Tivoli Enterprise Portal
userid and password do not have the correct authority to connect to the Tivoli
Enterprise Monitoring Server Universal Database. The movefrom-m2i.bat requires
that the Microsoft SQL server database is on the same Windows platform as the
Tivoli Enterprise Monitoring Server server and the new Universal Database
installation. Use this utility only after migration problems and before customizing

Chapter 10. Database troubleshooting 91

 Tivoli Enterprise Monitoring Server. The movefrom-m2i.bat is only used to migrate
the contents of Microsoft SQL Sever to Universal Database.

The error SQL0443N with 'SYSIBM:CLI:-805' occurs after upgrading to

DB2 UDB Version 8.1 Fix Pack 10
An error occurs with the SQLTables if the database was created before applying
IBM DB2 V8.1 FixPack 10 (also known as Version 8.2 Fix Pack 3), you encounter an
SQL0443N error if you run a DB2 Call Level Interface (CLI) catalog function (such
as SQLTables(), SQLColumns(), or SQLStatistics()). The following is an example of
the error in a log:
(430F82BD.0000-3C4:khdxodbc.cpp,319,"initializeDatabase") Connection with
Datasource "ITM Warehouse" successful
(430F82BD.0001-3C4:khdxbase.cpp,250,"setError") Error 20/3/-443(FFFFFE45)/0
executing SQLTables
(430F82BD.0002-3C4:khdxbase.cpp,266,"setError") Error "[IBM][CLI Driver][DB2/NT]
SQL0443N Routine "SYSIBM.SQLTABLES" (specific name "TABLES") has returned an
error SQLSTATE with diagnostic text "SYSIBM:CLI:-805". SQLSTATE=38553
+430F82BD.0002 "

Bind the db2schema.bnd file against each database to resolve this error. Run the
following command from a DB2 command prompt:
1. db2 connect to dbname (Warehouse Database)
where:
dbname
Specifies the name of a database to which you want to bind the
utilities, or the Warehouse Database name.
2. DB2 bind path_name
where:
path_name
Specifies the full path name of the directory where the bind files are
located, usually sqllib/bnd.
The following examples shows the rebinding commands from the
c:\SQLLIB\bnd>DB2 directory:
c:\SQLLIB\bnd>DB2 connect to dbname (Warehouse Database)
c:\SQLLIB\bnd>DB2 bind @db2ubind.lst blocking all grant public
c:\SQLLIB\bnd>DB2 bind @db2cli.lst blocking all grant public
c:\SQLLIB\bnd>DB2 bind db2schema.bnd blocking all grant public

Some rows do not display in an upgraded table

You might not see all rows after upgrading the Warehouse Proxy agent to IBM
Tivoli Monitoring V6.1 because some tables might be corrupted. Do the following
to find the errors that occurred during the upgrade:
1. Edit the KHDRAS1_Mig_Detail.log file.
2. Search for the word EXCEPTION.
The KHD_MAX_ROWS_SKIPPED_PER_TABLE environment variable in the
KHDENV_MIG file allows you to skip bad data. Use
KHD_MAX_ROWS_SKIPPED_PER_TABLE to specify the number of rows per table
to skip to migrate if the data that needs to be inserted is incorrect. When this
number is reached, migration of the table is aborted.

92 IBM Tivoli Monitoring: Problem Determination Guide

Historical data is not warehoused
Check the following Warehouse Proxy agent logs for errors that indicate why
historical data is not warehoused:
v Windows Event Log (all critical errors)
v WHProxy Agent RAS1 Log.
v Operations Log
The Warehouse Proxy agent contains an audit trail for each export written to the
warehouse database. You can also check the database table called
WAREHOUSELOG as it contains the same information as the logs.

Historical data for logs is incorrect

If there are duplicate or missing rows in a table, incorrect historical data is
collected for logs, such as managed system or situation status. Correct the incorrect
rows to ensure reliable logs.

Too much historical data is collected

The Summarization and Pruning agent is responsible for generating and storing
summarized data, and pruning the data based on information that is stored in the
IBM Tivoli Data Warehouse. The data in the IBM Tivoli Data Warehouse is a
historical record of activity and conditions in your enterprise. The size of
summarization data that is collected depends on the following criteria:
v The number of agents collecting data
v The number of table collected per agent
v The size of the table (number and size of columns)
v The collection interval (for example 5, 10, 15 or minutes)
Pruning data is deleting old data automatically, rather than manually. To reduce
the data that is collected, limit the size of your database tables by regularly
pruning old data from the IBM Tivoli Data Warehouse. If you installed the
Summarization and Pruning agent, your configuration settings are set to default
values. You can view the current values in the History Collection Configuration
window. Refer to "Changing configuration settings using the History Collection
Configuration window in the Tivoli Enterprise Portal" in the IBM Tivoli Monitoring
Administrator’s Guide for instructions.

If you need to install the Summarization and Pruning agent, see the IBM Tivoli
Monitoring Installation and Setup Guide. There you can find information for
environment-wide capacity planning. You can find agent-specific capacity planning
information in the user guide for the specific Tivoli Enterprise Monitoring Agent.

Warehouse Proxy agent failed to export data

The ODBC connection enables the Warehouse Proxy agent to export data to the
warehouse database. The WAREHOUSELOG table lets you know how many
exports succeeded and how many failed because of an ODBC error or a TIMEOUT
issue. See the IBM Tivoli Monitoring Installation and Setup Guide for more
information about the WAREHOUSELOG table and configuring the Warehouse
Proxy agent.

Chapter 10. Database troubleshooting 93

There are ORACLE or DB2 errors in the khdras1.log file
The following errors can occur in the khdras1.log if the globalization system
environment variable is not set correctly:
ORACLE error: [Oracle][ODBC][Ora]ORA-01461: can bind a LONG value only
for insert into a LONG column
1. Set the environment variable
NLS_LANG=AMERICAN_AMERICA.AL32UTF8 as a system
environment on the Windows computer on which the Warehouse Proxy
is installed.
2. Restart the Windows computer so that the Warehouse Proxy windows
service recognizes the change.
DB2 error: SQL0302N The value of a host variable in the EXECUTE or OPEN
statement is too large for its corresponding use. SQLSTATE=22003 sqlstate =
22003
1. Set the environment variable DB2CODEPAGE=1208 as a system
environment on the Windows computer where the Warehouse Proxy is
installed.
2. Restart the Windows computer so that the Warehouse Proxy windows
service recognizes the change.

SQL0552N "ITMUSER" does not have the privilege to perform

operation ″CREATE BUFFERPOOL″ SQLSTATE=42502
If the Warehouse database user does not have the correct permission, the following
error can occur:
(42ED71FA.0000-E4C:khdxbase.cpp,250,"setError")
Error 20/3/-552(FFFFFDD8)/0 executing SQLExecute
(42ED71FA.0001-E4C:khdxbase.cpp,266,"setError")
Error "[IBM][CLI Driver][DB2/NT] SQL0552N "ITMUSER" does not have
the privilege to perform operation "CREATE BUFFERPOOL" SQLSTATE=42502

When you configure a DB2 Warehouse Proxy connection from the Manage Tivoli
Enterprise Monitoring Services utility using the Configure DB2 Datasource for
Warehouse window, the user ID the Warehouse Proxy uses to connect to the
warehouse database must have SYSADM permission. SYSADM permission is
required to create an 8K Tablespace and Bufferpool.
Windows
If the database is on Windows, the user must be a member of the local
Administrators group.
UNIX-based system
If the database is on Linux or UNIX user must belong to the SYSADM
group.
1. Log in as the DB2 instance owner (usually ″su - db2inst1″),
2. Run the following command to determine the group that the
UNIX-based system user must belong.
db2 get dbm cfg | grep SYSADM

94 IBM Tivoli Monitoring: Problem Determination Guide

Chapter 11. IBM Tivoli Enterprise Console event
synchronization troubleshooting
This section provides descriptions of and resolutions for problems you might
experience with IBM Tivoli Enterprise Console event synchronization, including
the forwarding situations and the Rules Check Utility.

Preliminary IBM Tivoli Enterprise Console event synchronization

problem determination
Before troubleshooting a problem with IBM Tivoli Enterprise Console event
synchronization, review the following list of fundamental IBM Tivoli Enterprise
Console event synchronization problem determination tasks:
v Before you install the IBM Tivoli Enterprise Console event synchronization on
Windows and import event forwarding functionality into an existing rule base
with an absolute path, you must copy setupwin32.exe to the local drive on
which the rule base resides to import the IBM Tivoli Enterprise Console event
synchronization functionality into that rule base. Launch the copied
setupwin32.exe to start IBM Tivoli Enterprise Console event synchronization
installation.
v Use the IBM Tivoli Enterprise Console Java Console to make any configuration
changes to consoles and associated operator and event groups.
v Connect to a different IBM Tivoli Enterprise Console server using the embedded
viewer:
– From the desktop client:
1. Log off the Tivoli Enterprise Portal.
2. Log on the Tivoli Enterprise Portal.
3. Log into a different IBM Tivoli Enterprise Console server.
– From the browser client:
Recycle the browser.
v For a listing of product messages, refer to the Appendix E, “Understanding
informational, warning, and error messages,” on page 123.

T/EC ITM Synchronization Tasks

By default, all situation events that originate from a recycled Tivoli Enterprise
Monitoring Server are CLOSED. As a result, you do not need to run any of the
three tasks that reside in the T/EC ITM Synchronization Task Library.

Changing the TCP/IP timeout setting on your event server

If the Situation Update Forwarder cannot reach a monitoring server to send an
update, depending on the TCP/IP settings for the computer where your event
server is running, it could be up to 15 minutes before the Situation Update
Forwarder tries to connect to the monitoring server again. This might occur if your
event server is running on an AIX, Solaris, or HP-UX computer.

Use the following steps to change the TCP/IP timeout for your computer.

© Copyright IBM Corp. 2005 95

 On AIX, run the following command:
no -o tcp_keepinit=<timeout_value>

where <timeout_value> is the length of the timeout period, in half seconds. To

configure a timeout of 30 seconds, set the <timeout_value> value to 60.

On Solaris and HP-UX, run the following command:

ndd -set /dev/tcp tcp_ip_abort_cinterval <timeout_value>

where <timeout_value> is the length of the timeout period, in milliseconds. To

configure a timeout of 30 seconds, set the <timeout_value> value to 30000.

IBM Tivoli Enterprise Console task timeout expires while in process

Some tasks like ″Close_All_Reset_Events″ can require up to an hour to complete,
depending on the number of events processed. The task continues processing in
the background if the timeout expires, however, the task output does not display.
You do not need to run the task again. You can increase the task timeout value on
task panel to prevent the task from timing out.

Situations are not forwarded from Tivoli Enterprise Monitoring Server

to the Tivoli Enterprise Console server
Table 24 on page 96 provides troubleshooting information for when Tivoli
Enterprise Monitoring Server does not forward situations to the Tivoli Enterprise
Console server:
Table 24. Troubleshooting when situations are not forwarded
Problem Resolution
The IBM Tivoli Enterprise See ″Configuring IBM Tivoli Enterprise Console integration″ in the IBM Tivoli
Console Event Integration Monitoring Administrator’s Guide
Facility is not enabled or
configured correctly.

96 IBM Tivoli Monitoring: Problem Determination Guide

Table 24. Troubleshooting when situations are not forwarded (continued)
Problem Resolution
The correct values are not Edit the following parameters in the om_tec.config to specify the correct
specified for connection to the information for connection to the Tivoli Enterprise Console server:
Tivoli Enterprise Console server
ServerLocation
in the om_tec.config file.
Specifies the host name or IP address of IBM Tivoli Enterprise Console
server.
ServerPort
Specifies the IBM Tivoli Enterprise Console server listening port. Specify
0 if the IBM Tivoli Enterprise Console server uses port mapper.
v On a Windows system:
1. Click Start > Programs > IBM Tivoli Monitoring > Manage Tivoli
Enterprise Monitoring Services.
2. Right-click Tivoli Enterprise Monitoring Server >Advanced.
3. Select Edit EIF configuration to open the om_tec.config file in Notepad.
4. Specify the correct parameters and save the file.
v On a UNIX-based systems system:
1. cd/opt/IBM/ITM/tables/hubname/TECLIB
where:
hubname
Specifies the name of the hub monitoring server.
2. Open the om_tec.config file in a text editor.
3. Specify the correct parameters and save the file.
where:
hubname
Specifies the name of the hub monitoring server.

Chapter 11. IBM Tivoli Enterprise Console event synchronization troubleshooting 97

Table 24. Troubleshooting when situations are not forwarded (continued)
Problem Resolution
Events are filtered out based on Edit the om_tec.config file in the following locations:
the parameter values in the v On a windows system: c:\ibm\itm\cms\TECLIB.
om_tec.config file.
v On UNIX-based systems: /opt/IBM/ITM/tableshostname/TECLIB.
where:

/opt/IBM/ITM is the default location where the Tivoli Enterprise Monitoring

Server is installed and the host name is the value supplied during the Tivoli
Enterprise Monitoring Server configuration.
v On a Windows system:
1. Click Start > Programs > IBM Tivoli Monitoring > Manage Tivoli
Enterprise Monitoring Services.
2. Right-click Tivoli Enterprise Monitoring Server >Advanced.
3. Select Edit EIF configuration to open the om_tec.config file in Notepad.
4. Examine the FilterMode: and Filter: statements.
5. Specify the appropriate filter statements.
– See the IBM Tivoli Monitoring Administrator’s Guide for the supported EIF
configuration parameters
– Also see the Tivoli Event Integration Facility, Version 3.9 reference manual
SC32-1241 for more details.
v On a UNIX-based systems system:
1. cd /opt/IBM/ITM/tables/hubname/TECLIB
where:
hubname
Specifies the name of the hub monitoring server.
2. Open the om_tec.config file in a text editor.
3. Examine the FilterMode: and Filter: statements.
4. Specify the appropriate filter statements.
– See the IBM Tivoli Monitoring Administrator’s Guide for the supported EIF
configuration parameters
– Also see the Tivoli Event Integration Facility, Version 3.9 reference manual
SC32-1241 for more details.

98 IBM Tivoli Monitoring: Problem Determination Guide

Table 24. Troubleshooting when situations are not forwarded (continued)
Problem Resolution
Events are cached because the 1. Check the cache files to determine if events are cached on the Tivoli
target IBM Tivoli Enterprise Enterprise Monitoring Server. The cache files are located in the TECLIB
Console server is not currently directory on Tivoli Enterprise Monitoring Server:
running.
v Windows:
/IBM/ITM/cms/TECLIB
v UNIX-based systems:
/opt/IBM/ITM/tables/hubname/TECLIB
where:
hubname
Specifies the name of the hub monitoring server.
2. Run the wstartesvr command to restart the IBM Tivoli Enterprise Console
server from a Tivoli sourced environment.
3. Run the wstatesvr [-S server] command on the IBM Tivoli Enterprise
Console server to check the status of an event server.
where:
-S server
Specifies the name of an event server in name registry format. The
default server is the local event server. To indicate a remote server,
specify @EventServer#tmr, where tmr is the name of a Tivoli region.
Refer to the IBM Tivoli Enterprise Console documentation for more
information about checking the status of the IBM Tivoli Enterprise Console
server.

See “Trace logging” on page 7 for more information about tracing for IBM Tivoli
Enterprise Console forwarding.

Situation Events have an UNKNOWN severity in the Tivoli Enterprise

Console
If a situation was not mapped to a specific severity in the tecserver.txt file in
TECLIB directory, then IBM Tivoli Enterprise Console event synchronization
forwards these situation events to Tivoli Enterprise Console with an UNKNOWN
severity.

You can determine the event severity by checking the following:

v The situation SITINFO field.
v The severity keyword if the situation name was defined in tecserver.txt.
See the section "Defining event severities from forwarded IBM Tivoli Monitoring
situations" in the IBM Tivoli Monitoring Administrator’s Guide .

Forwarded IBM Tivoli Enterprise Console events display with the

PARSING_FAILED status in the IBM Tivoli Enterprise Console
reception log
The following table lists possible causes and resolutions for the PARSING_FAILED
status:

Chapter 11. IBM Tivoli Enterprise Console event synchronization troubleshooting 99

Table 25. Forwarded events display with the PARSING_FAILED status
Problem Resolution
The IBM Tivoli Enterprise Reinstall the IBM Tivoli Enterprise Console event synchronization functionality. See the
Console event IBM Tivoli Monitoring Installation and Setup Guide for instructions.
synchronization was not
installed or was not
installed correctly.
The expected rule base Actively load the expected rule base. You can run the following command from the IBM
was not loaded. Tivoli Enterprise Console event server to load a rule base:
wrb -loadrb rule_base

where:
rule_base
The name of the rule base to load.
This makes rule_base the currently active rule base on the event server. The rule base
must already be defined at the server, and any event class specification files and rule
files in the directory must be valid. The loaded rule base replaces all event class
specifications and rules currently defined at the server. Only one rule base can be active
at a time. Loading another rule base overwrites the currently active rule base.
Note:
Notes:
1. If you do not compile the rule base before attempting to load it, you get an error
message.
2. You must stop and restart the TEC server for changes to the rule base to be active.
Use the following commands:
v wstopesvr [-S server]
v wstartesvr [-S server]
See the IBM Tivoli Enterprise Console documentation for more information about
loading rule bases, including the IBM Tivoli Enterprise Console Command and Task
Reference.

100 IBM Tivoli Monitoring: Problem Determination Guide

Table 25. Forwarded events display with the PARSING_FAILED status (continued)
Problem Resolution
There are missing BAROC The BAROC files are located in the TECLIB directories on Tivoli Enterprise Monitoring
files that must be Server:
imported to support the v Windows:
IBM Tivoli Monitoring
/IBM/ITM/cms/TECLIB
V6.1 events.
v UNIX-based systems:
/opt/IBM/ITM/tables/hubname/TECLIB
where:
hubname
Specifies the name of the hub server.

You can run the following command from the IBM Tivoli Enterprise Console event
server to import a BAROC file (a file of event class specifications into a rule base),
appending it to the end of the class specifications unless otherwise specified with
arguments:
wrb -imprbclass class_file [-encoding encoding ]
[-before class_file |
-after class_file] [-force] rule_base

where:
class_file
Specifies the name of the class file to import. This must be a path to BAROC
file.
rule_base
The name of the rule base to receive the imported class set.
-after class_file
Specifies the name of the class file after which the imported class file is to be
placed.
-before class_file
Specifies the name of the class file before which the imported class file is to be
placed.
-encoding encoding
Specifies the character encoding of the class file. If this option is not specified,
a class file being imported into a rule base is opened in UTF-8 character
encoding.
-force Imports the class file even if it can cause rule base inconsistency.
An error message is displayed if the class set file contains syntax errors, references to
nonexistent event classes or enumerations, or if duplicate event classes or enumeration
are defined. If the classes in a class file are derived from classes in another file, import
the class files into the rule base in an order that preserves the inheritance structure. For
example, if class file B.baroc contains classes that are derived from class file A.baroc,
you must import class file A.baroc first.

For any changes you make to the rule base to take affect you must complete the
following steps:
v Recompile the rule base
v Load the rule base
v Stop the Tivoli Enterprise Console server
v Restart the Tivoli Enterprise Console server
Refer to the IBM Tivoli Monitoring Administrator's Guide for information about changing
the omegamon.rls file.

See the IBM Tivoli Enterprise Console Command and Task Reference, V3.9.0 for more
information about importing class files into rule bases.
Chapter 11. IBM Tivoli Enterprise Console event synchronization troubleshooting 101
The IBM Tivoli Enterprise Console is disabled
The Tivoli Enterprise Console relies on the Tivoli Management Framework for
common services, including communications. If the console loses contact with
Tivoli Management Framework, no new events are added to the view. Do the
following to enable event reporting:
1. Reestablish contact between Tivoli Enterprise Console and IBM Tivoli
Monitoring.
2. Log off the Tivoli Enterprise Portal.

Note: If you use Tivoli Enterprise Portal browser client, you must also close
and restart the Web browser.
3. Log in to the Tivoli Enterprise Portal again to enable the Tivoli Enterprise
Console view to resume event reporting.

102 IBM Tivoli Monitoring: Problem Determination Guide

The IBM Tivoli Enterprise Console does not indicate that a situation
event was acknowledged or closed
Table 26. Situation event was not acknowledged or closed
Problem Resolution
The omegamon.rls rule set Run the following commands from the IBM Tivoli Enterprise Console event server
was not imported in the to import a rule set into a rule base:
currently loaded rule base. 1. wrb -imprbrule rule_file [-encoding encoding ] [-force] rule_base
where:
rule_base
The name of the rule base in which the rule pack lives.
rule_file
The file name of the rule set to import to the rule base. This must be a
path to a rule set file (with a file extension of .rls).
-encoding encoding
Specifies the character encoding of the class file. If this option is not
specified, a class file being imported into a rule base is opened in UTF-8
character encoding.
-force Adds the rule set to the rule base even if a rule references a non-existent
event class
2. wrb -imptgtrule {rule_set | rule_pack} [{-before | -after} {rule_set |
rule_pack}] target rule_base
where:
rule_base
The name of the rule base that contains the rule base target.
rule_pack
The name of the rule pack to import. The rule pack must have been
imported into the rule base first.
rule_set
The name of the rule set to import. The rule set must have been
imported into the rule base first.
target The name of the rule base target to receive the imported rule set or rule
pack. You must have first created the target with the -crttarget
command option.
-after rule_set | rule_pack
Specifies the name of the rule set or rule pack after which the imported
rule set or rule pack should be located.
-before rule_set | rule_pack
Specifies the name of the rule set or rule pack before which the
imported rule set or rule pack should be located.

For any changes you make to the rule base to take affect you must complete the
following steps:
v Recompile the rule base
v Load the rule base
v Stop the Tivoli Enterprise Console server
v Restart the Tivoli Enterprise Console server
Refer to the IBM Tivoli Monitoring Administrator's Guide for information about
changing the omegamon.rls file.

Chapter 11. IBM Tivoli Enterprise Console event synchronization troubleshooting 103
Table 26. Situation event was not acknowledged or closed (continued)
Problem Resolution
The events are not cached in The location of the cache file is specified during installation. The default locations
the expected location. are as follows:
v On Windows: C:\tmp\TME\TEC\OM_TEC\persistence
v On UNIX-based systems: /var/TME/TEC/OM_TEC/persistence
The value of fileLocation is defined in the active configuration file as indicated by the
situpdate.properties file in the following locations:
v On Windows: C:\Program Files\TME\TEC\OM_TEC\etc
v On UNIX-based systems :/etc/TME/TEC/OM_TEC

You can edit the location of the cache file by running the sitconfig.sh script. Refer to
the IBM Tivoli Monitoring Administrator's Guide for sitconfig.sh script usage.
The IBM Tivoli Enterprise To use event forwarding, you must start the Situation Update Forwarder. This
Console Situation Update process is started automatically when the event server starts. To start the process
Forwarder is not currently manually, change to the $BINDIR/TME/TEC/OM_TEC/bin directory and run the
running. following command:

On Windows:
startSUF.cmd

On UNIX-based systems:
startSUF.sh

To stop the process, run the stopSUF.sh command (stopSUF.cmd on Windows) in the
same directory.
Note: If the Situation Update Forwarder process stops abnormally, run the
stopSUF.sh (stopSUF.cmd on Windows) command before restarting the process.
The correct Tivoli Enterprise 1. Ensure the event cms_hostname attribute includes a fully qualified host name for
Monitoring Server the computer where the monitoring server is running. The monitoring server
information is not defined for hostname must match the hostname recorded in events coming from this
the updated events in the monitoring server.
cms_hostname attribute.
2. Ensure user validation is enabled on Tivoli Enterprise Monitoring Server and the
correct userid and password information is specified for the Tivoli Enterprise
Monitoring Server.
3. Run the sitconfsvruser.sh script to update the configuration for the Tivoli
Enterprise Monitoring Server. Refer to the IBM Tivoli Monitoring Administrator's
Guide for more information.
There is a communication Run the test.sh command on UNIX based systems or the test.cmd on Windows to
problem between IBM Tivoli determine if there is a communication problem between IBM Tivoli Enterprise
Enterprise Console server and Console server and Tivoli Enterprise Monitoring Server.
Tivoli Enterprise Monitoring
Server. Refer to Chapter 4, “Connectivity troubleshooting,” on page 51 for additional
information about solving connectivity problems.
The expected server ports Ports 3661 and 1920 must be available. Run the test.sh command on UNIX based
3661 and 1920 are not systems or the test.cmd on Windows to determine if there is a communication
currently open on the Tivoli problem between IBM Tivoli Enterprise Console server and Tivoli Enterprise
Enterprise Monitoring Server. Monitoring Server.

Refer to Chapter 4, “Connectivity troubleshooting,” on page 51 for additional

information about solving connectivity problems.

104 IBM Tivoli Monitoring: Problem Determination Guide

Table 26. Situation event was not acknowledged or closed (continued)
Problem Resolution
There a firewall between You might need to include the IP addresses of other IBM Tivoli Monitoring
Tivoli Enterprise Monitoring components in the access control for the firewall. Refer to Chapter 4, “Connectivity
Server and Tivoli Enterprise troubleshooting,” on page 51 for additional information about solving connectivity
Console that is blocking problems.
communication over certain
ports.

TEC_ITM_OM_Situation_Sync_Error events occur

TEC_ITM_OM_Situation_Sync_Error events occur if there is a Tivoli Enterprise
Console server communication problem or if you need to increase the rules cache.
Table 27. Reasons for the TEC_ITM_OM_Situation_Sync_Error event
Problem Resolution
IOException is generated. Verify that the network connections are up and running, the SOAP server is running
There is no connectivity with and receiving requests, and the ports 3661 and 1920 on the Tivoli Enterprise
SOAP. Monitoring Server machine are open. Use the following steps to determine why the
error occurred:
Logon Validation Failure is 1. Ensure that the userid and password configured for the Tivoli Enterprise
returned by the SOAP server. Monitoring Server serverid on the event server during installation is correct. Run
the sitconfsvruser.sh script to update the configuration for the Tivoli Enterprise
Fatal Error is returned by the Monitoring Server. Refer to the IBM Tivoli Monitoring Administrator's Guide for
SOAP server. more information.
2. Run the test.sh command on UNIX based systems or the test.cmd on Windows
The connection to the SOAP to determine if there is a communication problem between IBM Tivoli Enterprise
server repeatedly times out Console server and Tivoli Enterprise Monitoring Server.
because of broken 3. If the SOAP Server is running and receiving requests, initiate a CT_GET request
communication, network for the SOAP server from the Web client.
outage or the SOAP server is
down. See the "Tivoli Enterprise Monitoring Web services" appendix in the IBM Tivoli
Monitoring Administrator's Guide for more information.
The event message indicates Increase the size of the rules cache using the Tivoli desktop or the wsetesvrcfg
reset, resurface, or command. Refer to the IBM Tivoli Enterprise Console Command and Task Reference for
acknowledge action failed. more information and the "Configuring Tivoli Enterprise Console integration" section
The original event was not in in the IBM Tivoli Monitoring Administrator's Guide for more information.
the Tivoli Enterprise Console
rules cache.

Receiving error message when running the Rule Check Utility with the
-cd and -rd options
Ensure the class definitions in the TEC_CLASSES directory that you specified with
the -cd option include the supporting classes for all rule sets defined in the rule
base directory specified by the by -rd option.
Table 28. Rule Base directory and BAROC event class definition directory
Option Description
-rd Used to specify a directory containing the rulesets (*.rls) to be checked. If not provided, the TEC_RULES
subdirectory for the actively loaded rule base is used by default.

Chapter 11. IBM Tivoli Enterprise Console event synchronization troubleshooting 105
Table 28. Rule Base directory and BAROC event class definition directory (continued)
Option Description
-cd Used to specify a directory containing the BAROC event class definitions files (*.baroc) to be used as
input. If not provided the TEC_CLASSES subdirectory for the actively loaded rule base is used by
default.

The following lists the syntax for the Rule Check Utility:

wrules_check {[-h] | [-v] | [-rd rules_directory] [-cd baroc_classes_directory]

{class[,attribute,attribute...] [:classN,attributeN,attributeN] | [-f class_file]} [-of
output_file]}

For more information about the Rules Check Utility, refer to the IBM Tivoli
Monitoring Administrator’s Guide.

Expected impacted rules are not displayed when entering multiple

event classes with class attributes
Ensure you input ran the Rules Check Utility command with the correct options:

wrules_check {[-h] | [-v] | [-rd rules_directory] [-cd baroc_classes_directory]

{class[,attribute,attribute...] [:classN,attributeN,attributeN] | [-f class_file]} [-of
output_file]}

For more information about the Rules Check Utility, refer to the Tivoli Enterprise
Portal Administrator’s Guide.

The wrules_check command fails

When you run the wrules_check without specifying the –cd and –rd options, you
must have permission to run the wrb subcommands. Run the wrules_check
command with the –cd and –rd options or refer to the IBM Tivoli Enterprise
Console documentation for more information about running the wrb
subcommands.

The following lists the syntax for the Rule Check Utility:

wrules_check {[-h] | [-v] | [-rd rules_directory] [-cd baroc_classes_directory]

{class[,attribute,attribute...][:classN,attributeN,attributeN] | [-f class_file]} [-of
output_file]}
Table 29. Rule Base directory and BAROC event class definition directory
Option Description
-rd Used to specify a directory containing the rulesets (*.rls) to be checked. If not provided, the TEC_RULES
subdirectory for the actively loaded rule base is used by default.
-cd Used to specify a directory containing the BAROC event class definitions files (*.baroc) to be used as
input. If not provided the TEC_CLASSES subdirectory for the actively loaded rule base is used by
default.

For more information about the Rules Check Utility, refer to the Tivoli Enterprise
Portal Administrator’s Guide.

106 IBM Tivoli Monitoring: Problem Determination Guide

The NetView menus are unavailable
Ensure the NetView console or Web console are installed on the Tivoli Enterprise
Portal machine and that the NVWC_HOME or NV_DRIVE variables are set
correctly.

Errors occur during installation of IBM Tivoli Enterprise Console event

synchronization
When installation is complete, the results are written to the
itm_tec_event_sync_install.log file located in the following directories:
v Windows:
The itm_tec_event_sync_install.log file is created in the directory defined by the
%TEMP% environment variable. To determine where this directory is defined for
the current command line window, run the following command:
echo %TEMP%
v UNIX-based systems:
The itm_tec_event_sync_install.log file is always created in the /tmp directory.
The following error is harmless and there is currently no resolution:
One or more errors occured during the replacement of files (tecSyncAllFile1)
with files (tecSyncAllFile1).
Refer to install log for more details.
One or more errors occured during the replacement of files (tecSyncAllFile2)
with files (tecSyncAllFile)1.
Refer to install log for more details.
One or more errors occured during the replacement of files (tecSyncAllFile3)
with files (tecSyncAllFile1).
Refer to install log for more details.
.
.
.

The IBM Tivoli Enterprise Console does not display in a workspace

after logging off and logging on the Tivoli Enterprise Portal
Recycle the Tivoli Enterprise Portal browser so the Tivoli Enterprise Portal can
display the IBM Tivoli Enterprise Console in a workspace.

The Tivoli Enterprise Portal stops when attempting to launch the IBM
Tivoli Enterprise Console behind a router
After a two-minute timeout, the following message might display when you try to
add a IBM Tivoli Enterprise Console to a Tivoli Enterprise Portal client that is
behind a router:
The RDBMS cannot be reached.

During the timeout period the Tivoli Enterprise Portal client seems hung. To avoid
this problem, the Tivoli Management Framework Administrator must enable
communications based on the host name rather than the IP address. Use the
following steps to prevent this problem:
1. On the IBM Tivoli Enterprise Console Server on which you are logged in, set
the single_port_bdt and set_iom_by_name Tivoli Management Framework
settings to TRUE by running the following commands on the IBM Tivoli
Enterprise Console Server:

Chapter 11. IBM Tivoli Enterprise Console event synchronization troubleshooting 107
 odadmin single_port_bdt TRUE all
odadmin set_iom_by_name TRUE all
2. Run the following command to recycle the object dispatchers:
odadmin reexec all

Refer to the Tivoli Management Framework Reference Manual for more information
about the odadmin command.

The error 'ECO2029E: Failed to connect to

http://servername:port_number/cgi-bin/tec_help.pl.' occurs after
clicking the Information button on the IBM Tivoli Enterprise Console.
Error ECO2029E occurs because the spider Web Server provided with the IBM
Tivoli Enterprise Console Server does not automatically start. To start the spider
Web Server, run the wstarthttpd command on the IBM Tivoli Enterprise Console
that you are logged in to. After the wstarthttpd command completes, the
information button works. Refer to the IBM Tivoli Enterprise Console 3.9 Installation
Guide for more information about the wstarthttpd command.

Situations return to acknowledged

The default action of the omegamon.rls rule set is to reject acknowledgement
expirations that are received from the Tivoli Enterprise Monitoring Server, and to
then acknowledge the situation again on the Tivoli Enterprise Monitoring Server.
This action of the omegamon.rls rule set might be changed to accept
acknowledgement expirations from the Tivoli Enterprise Monitoring Server, and
therefore leave the situation open in the Tivoli Enterprise Monitoring Server. Refer
to the IBM Tivoli Monitoring Administrator’s Guide for information on changing
parameters of the omegamon.rls rule set.

108 IBM Tivoli Monitoring: Problem Determination Guide

Appendix A. IBM Tivoli Monitoring product codes
The following table lists the product codes that identify the different IBM Tivoli
Monitoring components and agents. Use these codes when running commands.
Table 30. IBM Tivoli Monitoring product codes
Component Product code
Active Directory monitoring agent 3z
Alert Adapter for AF/REMOTE a2
Alert Adapter for Tivoli Enterprise Console tv
Alert Emitter for Tivoli Enterprise Console vt
DB2 monitoring agent ud
Endpoint monitoring agent tm
i5/OS monitoring agent a4
Linux OS monitoring agent lz
Microsoft Exchange Server monitoring agent ex
Microsoft SQL Server monitoring agent oq
Oracle monitoring agent or
Sybase Server monitoring agent oy
Tivoli Enterprise Monitoring Server ms
IBM Tivoli Enterprise Console it
Tivoli Enterprise Portal browser client cw
Tivoli Enterprise Portal desktop client cj
Tivoli Enterprise Portal Server cq
Universal Agent um
UNIX Log Alert monitoring agent ul
UNIX OS monitoring agent ux
Warehouse Proxy hd
Summarization and Pruning Agent sy
Windows OS monitoring agent nt

© Copyright IBM Corp. 2005 109

110 IBM Tivoli Monitoring: Problem Determination Guide
Appendix B. IBM Tivoli Monitoring processes
The following table lists the processes according to operating system platform and
IBM Tivoli Monitoring component.
Table 31. IBM Tivoli Monitoring processes by operating system
Component Windows UNIX-based systems
Tivoli Enterprise Monitoring cms.exe cms start
Server kdsmain.exe kdsmain
Tivoli Enterprise Portal KfwServices.exe N/A
Server
Unix agent N/A kuxagent
Linux agent N/A N/A
Windows agent kntcma.exe N/A
Universal agent kuma610.exe kuma610
Log Alert agent N/A kulagent
Warehouse proxy agent khdxprto.exe N/A
Summarization and Pruning ksy610.exe ksy610 console
Agent

© Copyright IBM Corp. 2005 111

112 IBM Tivoli Monitoring: Problem Determination Guide
Appendix C. Environment variables
This appendix lists IBM Tivoli Monitoring environment variables that you can
customize.

Tivoli Enterprise Portal Server environment variables

The following tables lists Tivoli Enterprise Portal Server environment variables.
Table 32. Tivoli Enterprise Portal Server environment variables
Variable Useful for . . .
KFW_MIGRATE_VERBOSE Records the migration activities to the migrate log file.
KFW_SQL_VERBOSE Records actions by the Tivoli Enterprise Portal Server in the log file.
KFW_MIGRATE_CMS Causes initial migration of managed objects and user IDs from the monitoring
server the first time the Tivoli Enterprise Portal Server starts after installation.
DSUSER1 Lists the databases available for a query.
KFW_REPORT_TERM_ Specifies the point where a historical request selects from short-term or long-term
BREAK_POINT history data.

Tivoli Enterprise Monitoring Server environment variables

The following tables lists Tivoli Enterprise Monitoring Server environment
variables.
Table 33. Tivoli Enterprise Monitoring Server environment variables
Variable Purpose
KGL_TRC1 Whether to enable the error log.
KDS_CATLGLIB Specifies the catalog library.
KDS_RULELIB Specifies the rule library.
CMS_EXTERNALBROKERS Wether there are internal brokers.
NLS1_LOCALEDIR The directory of the locale file.
KDH_SERVICEPOINT The service point.
CANDLE_HOME The directory where the product was installed.

Universal Agent environment variables

The following tables lists environment variables you can set to customize tracing
for the Universal Agent.
Table 34. Universal Agent environment variables
Variable Purpose
Diagnosing communications or connectivity problems
between Universal Agent and the Tivoli Enterprise Portal
KDC_DEBUG Server

© Copyright IBM Corp. 2005 113

Table 34. Universal Agent environment variables (continued)
Variable Purpose
KUMA_VERBOSE Tracing a Universal Agent API client program. This
variable must be set on the machine where the API client
program is executing, not where Universal Agent is
running)

Example: KUMP_API_VERBOSE=Y dpapi.log.

The KUMP_API_VERBOSE option is valuable when

debugging an API program that communicates with the
Universal Agent API data provider.
KUMA_DCH_TRAPEMIT SNMP Emitter tracing. Use to display emitted traps in
the UAGENT Action report.
KUMP_ODBC_DEBUG ODBC Data Provider tracing.
KUMP_HTTP_DEBUG HTTP Data Provider tracing.
KUMP_SCRIPT_DEBUG Script Data Provider tracing.
KUMP_SNMP_DEBUG_TRAP SNMP Data Provider tracing. All of the debug
KUMP_SNMP_DEBUG_DISCOVERY_ROUTE environment variables listed default to No. As an
KUMP_SNMP_DEBUG_DISCOVERY_NETWORK example, if you use the SNMP Data Provider and have
KUMP_SNMP_DEBUG_MIB_MANAGER problems collecting MIB data, you set these two
KUMP_SNMP_DEBUG_MIB_IO environment variables:
KUMP_SNMP_DEBUG_MIB_MANAGER=Y
KUMP_SNMP_DEBUG_MIB_IO=Y
KBB_RAS1=ERROR (UNIT:kumpfile Error State Detail Detailed File Data Provider tracing.
Flow Metrics) (UNIT:kumpdcmf ALL)
KBB_RAS1=ERROR (UNIT:kumpsosr ALL) Detailed API or Socket Data Provider tracing.
(UNIT:kumpspst ALL) (UNIT:kumpscku ALL)
(UNIT:kumpstcp ALL) (UNIT:kumplpba ALL)
KBB_RAS1=ERROR (UNIT:kumamain ALL) Problems involving managed system online/offline
processing.
KBB_RAS1=ERROR (UNIT:kumpdpda Error Output) Incorrect report data.
(UNIT:kumpmd2a Error Detail)
KBB_RAS1=ERROR METRICS Problems involving Universal Agent memory usage.

IBM Tivoli Data Warehouse environment variables

The following IBM Tivoli Data Warehouse parameters can be changed in the
KHDENV_MIG file to customize tracing for the warehouse upgrade tool.
Table 35. IBM Tivoli Data Warehouse environment variables
Variable Purpose
KHD_MAX_ROWS_SKIPPED_PER_TABLE Specifies the maximum number of rows per table that can be
skipped during an upgrade. Rows with incorrect data are skipped
until the maximum specified number is reached. When this number
of rows are skipped, the migration of the table is aborted.
KHD_MAX_ROWS_PER_TRANSACTIONS Specifies how many rows are committed at each insert of data.
KHD_CNP_SERVER_HOST Specifies the name of the CNP server.
KHD_CNP_SERVER_PORT Specifies the port used by the CNP server.
KHD_SOURCE_DATABASE_SCHEMA Specifies the owner or schema of the Candle tables in the source
database.

114 IBM Tivoli Monitoring: Problem Determination Guide

Table 35. IBM Tivoli Data Warehouse environment variables (continued)
Variable Purpose
KHD_SOURCE_JDBC_DRIVER Specifies the JDBC driver used to connect to the source database.
KHD_SOURCE_URL Specifies the URL to connect to the source database
KHD_SOURCE_DATABASE_USER Specifies the user to connect to the source database.
KHD_SOURCE_DATABASE_PASSWORD Specifies the password to connect to the source database.
KHD_TARGET_JDBC_DRIVER Specifies the JDBC driver used to connect to the target database
KHD_TARGET _URL Specifies the URL to connect to the target database
KHD_TARGET _DATABASE_SCHEMA Specifies the owner or schema of the Candle tables in the target
database
KHD_TARGET _DATABASE_USER Specifies the user to connect to the target database
KHD_TARGET _DATABASE_PASSWORD Specifies the password to connect to the target database

The following Warehouse Proxy agent parameters can be changed in the KHDENV
file to customize tracing for the Warehouse Proxy agent.
Table 36. Warehouse proxy environment variables
Variable Purpose
KHD_CNX_WAIT_ENABLE A time to wait before a retry. Default is Y. Changing this variable to N does not
wait before retries. Setting this variable to N can generate a large log file if the
tests to the database fail at each retry.
KHD_CNX_WAIT The time in minutes to wait before trying to reconnect. Default is 10 minutes.
KHD_QUEUE_LENGTH The length of the KHD work queue. This is an integer that identifies the
maximum number of export work requests that can be placed on the work
queue before the queue starts rejecting requests. The default value of
KHD_QUEUE_LENGTH is 1000. Setting this value to 0 means the queue length
has no limit.
KHD_EXPORT_THREADS The number of worker threads exporting data to the database. The default value
is 10.
KHD_CNX_POOL_SIZE The total number of preinitialized ODBC connection objects available to the
work queue export threads. The default value is 3.
CTIRA_NCSLISTEN The number of RPC threads.
KHD_STATUSTIMEOUT The time in seconds set by default to 900s = 15 minutes. An export request on
the application agent is resent if a status is not received from the Warehouse
Proxy agent before the timeout expires.
KHD_SRV_STATUSTIMEOUT The time in seconds set by default to 600s = 10 minutes. Set
KHD_SRV_STATUSTIMEOUT less than KHD_STATUSTIMEOUT by at least 60
seconds.

Table 37 lists the Summarization and Pruning agent parameters that you can edit
in the KSYENV file to customize tracing for the Summarization and Pruning agent.
Table 37. Summarization and Pruning agent environment variables
Variable Purpose
KSY_WAREHOUSE_URL The Warehouse Database Connection JDBC URL.
KSY_WAREHOUSE_DRIVER The Warehouse Database Connection JDBC Driver.
KSY_WAREHOUSE_SCHEMA The Warehouse Database Connection Schema.
KSY_WAREHOUSE_USER The Warehouse Database Connection User (encrypted).

Appendix C. Environment variables 115

Table 37. Summarization and Pruning agent environment variables (continued)
Variable Purpose
KSY_WAREHOUSE_PASSWORD The Warehouse Database Connection Password (encrypted).
KSY_TIMEZONE_IND Time zone indicator. AGENT specifies use the time zone offset of the
agent. WAREHOUSE specifies use the time zone offset of the
warehouse .
KSY_START_OF_WEEK_DAY Start of the week day, for example: 0 = Sunday 1 = Monday.
KSY_SHIFTS_ENABLED Shift periods. Only two shifts are allowed. If shifts are enabled, each
hour (0-23) must be specified once.
KSY_SHIFT1_HOURS A comma-separated list of hour numbers for the shift.
KSY_SHIFT2_HOURS A comma-separated list of hour numbers for the shift.
KSY_VACATIONS_ENABLED Whether or not vacation are enabled with Y or N.
KSY_WEEKENDS_AS_VACATIONS Whether or not weekends are vacation with Y or N.
KSY_VACATION_DAYS Vacation days in a comma-separated list of days in YYYYMMDD
format.
KSY_MAX_ROWS_PER_ TRANSACTION Maximum rows per database transaction.
KSY_EVERY_N_DAYS How often to run the schedule in days (number).
KSY_HOUR_TO_RUN The hour of the day to run (number).
KSY_HOUR_AM_PM Whether to run in the AM or PM (AM/PM).
KSY_MINUTE_TO_RUN The minute of the day to run (number).
KSY_CNP_SERVER_HOST Tivoli Enterprise Portal Server connection default host.
KSY_CNP_SERVER_PORT Tivoli Enterprise Portal Server connection default port.
KSY_HOUR_AGE_UNITS The minimum age of data for hourly data in hours before aggregation
is done.
KSY_DAY_AGE_UNITS The minimum age of data for daily data in days before aggregation is
done.
KSY_USE_DEFAULTS Enable default collection, aggregation and pruning.
KSY_DEFAULT_ COLLECTION_ Default collection interval. Can be 5,15,30 or 60 and is in minutes.
INTERVAL
KSY_DEFAULT_ Default collection location. Can be A (agent) or S (server).
COLLECTION_LOCATION
KSY_DEFAULT_ Default warehouse interval. Can be 1 or 24 and is in hours.
WAREHOUSE_INTERVAL
KSY_DEFAULT_AGGREGATION Default aggregation. A list of values in comma-separated format.
Allowed values: hour, day, week, month, quarter, year.
KSY_DEFAULT_PRUNING Default pruning. A list of values comma-separated format. The format
is: <aggUNIT>.<numberPruningUnits>.<pruningUnit>

where:
aggUnit
Is raw, hour, day, week, month, quarter, or year.
numberPruneUnits
Is a number.
pruningUnit
Is day, month, or year.

116 IBM Tivoli Monitoring: Problem Determination Guide

Table 37. Summarization and Pruning agent environment variables (continued)
Variable Purpose
KSY_MAX_WORKER_THREADS Maximum number of simultaneous worker threads. Default is 1.
Recommended value is the number of processors on your server minus
1.
KSZ_JAVA_ARGS Java arguments.

Tivoli Enterprise Monitoring Agent deploy environment variables

The following Tivoli Enterprise Monitoring Server parameters can be changed in
the KBBENV file:
Table 38. Tivoli Enterprise Monitoring Agent deploy environment variables
Variable Purpose
DEPOTHOME Specifies the root directory of the agent depot on the file system.
DEPLOYQUEUESIZE Specifies the maximum number of requests that the request queue on the agent
deployment controller.
DEPLOYTHREADPOOLSIZE Specifies the number of threads that are available to the deployment controller.
DATACHUNKSIZE Specifies the size of the data chunk that will be passed to RPC for transfer.
AGENTDEPOT An OS agent parameter. Determines the location on the agent host where agent
bundles will be transferred.
TIMEOUT Specifies the time in seconds that Agent Deployment tool has to complete a task.
If the tool does not complete in the task in the time specified by the TIMEOUT
value, the task is terminated. The default value is 600 seconds.

Appendix C. Environment variables 117

118 IBM Tivoli Monitoring: Problem Determination Guide
Appendix D. Support information
If you have a problem with your IBM software, you have the following options for
obtaining support for IBM software products:
v “Searching knowledge bases”
v “Obtaining fixes” on page 120
v “Receiving weekly support updates” on page 120
v “Contacting IBM Software Support” on page 120

Searching knowledge bases

You can search the available knowledge bases to determine whether your problem
was already encountered and is already documented.

Searching the information center

Note: If you print PDF documents on other than letter-sized paper, set the option
in the File > Print window that allows Adobe Reader to print letter-sized
pages on your local paper.

The documentation CD contains the publications that are in the product library.
The format of the publications is PDF, HTML, or both.

IBM posts publications for this and all other Tivoli products, as they become
available and whenever they are updated, to the Tivoli software information center
Web site. Access the Tivoli software information center by first going to the Tivoli
software library at the following Web address:

http://publib.boulder.ibm.com/tividd/td/tdprodlist.html

Scroll down and click the Product manuals link. In the Tivoli Technical Product
Documents Alphabetical Listing window, click M to access all of the IBM Tivoli
Monitoring product manuals.

Searching the Internet

If you cannot find an answer to your question in the information center, search the
Internet for the latest, most complete information that might help you resolve your
problem.

The IBM Software Support Web site provides the latest information about known
product limitations and resolutions in the form of technotes for your product. You
can view this information at the following Web site:

http://www.ibm.com/software/support

To search for information about IBM products through the Internet (for example,
on Google), be sure to consider the following types of documentation:
v IBM technotes
v IBM downloads
v IBM Redbooks™

© Copyright IBM Corp. 2005 119

 v IBM developerWorks®
v Forums and newsgroups

Obtaining fixes
A product fix might be available to resolve your problem. To determine what fixes
are available for your IBM software product, follow these steps:
1. Go to the Software support Web site at
http://www.ibm.com/software/support.
2. Click the Download tab.
3. Select the operating system in the Operating system menu.
4. Type search terms in the Enter search terms field.
5. As appropriate, use other search options to further define your search.
6. Click Search.
7. From the list of downloads returned by your search, click the name of a fix to
read the description of the fix and to optionally download the fix.

For more information about the types of fixes that are available, see the IBM
Software Support Handbook at
http://techsupport.services.ibm.com/guides/handbook.html.

Receiving weekly support updates

To receive weekly e-mail notifications about fixes and other software support news,
follow these steps:
1. Go to the IBM Software Support Web site at
http://www.ibm.com/software/support.
2. Click My account in the upper right corner of the page.
3. Click Subscribe to IBM e-news. (If you have already subscribed and want to
modify your subscription preferences, click Modify subscriptions and follow
the instructions on screen.)
4. Follow the instructions on screen to provide the following data:
v Your personal contact information.
v Your areas of interest.
v The types of subscriptions and regional versions that you want to receive.
5. Review the subscription confirmation to confirm your settings.

Contacting IBM Software Support

IBM Software Support provides assistance with product defects.

Before contacting IBM Software Support, your company must have an active IBM
software maintenance contract, and you must be authorized to submit problems to
IBM. The type of software maintenance contract that you need depends on the
type of product you have:
v For IBM distributed software products (including, but not limited to, Tivoli,
Lotus®, and Rational® products, as well as DB2 and WebSphere® products that
run on Windows®, or UNIX® operating systems), enroll in Passport Advantage®
in one of the following ways:
Online
Go to the Passport Advantage Web site at

120 IBM Tivoli Monitoring: Problem Determination Guide

 http://www.lotus.com/services/passport.nsf/
WebDocs/Passport_Advantage_Home and click How to Enroll.
By phone
For the phone number to call in your country, go to the IBM Software
Support Web site at
http://techsupport.services.ibm.com/guides/contacts.html and click the
name of your geographic region.
v For customers with Subscription and Support (S & S) contracts, go to the
Software Service Request Web site at
https://techsupport.services.ibm.com/ssr/login.
v For customers with IBMLink™, CATIA, Linux®, S/390®, iSeries™, pSeries®,
zSeries®, and other support agreements, go to the IBM Support Line Web site at
http://www.ibm.com/services/us/index.wss/so/its/a1000030/dt006.
v For IBM eServer™ software products (including, but not limited to, DB2 and
WebSphere products that run in zSeries, pSeries, and iSeries environments), you
can purchase a software maintenance agreement by working directly with an
IBM sales representative or an IBM Business Partner. For more information
about support for eServer software products, go to the IBM Technical Support
Advantage Web site at http://www.ibm.com/servers/eserver/techsupport.html.

If you are not sure what type of software maintenance contract you need, call
1-800-IBMSERV (1-800-426-7378) in the United States. From other countries, go to
the contacts page of the IBM Software Support Handbook on the Web at
http://techsupport.services.ibm.com/guides/contacts.html and click the name of
your geographic region for phone numbers of people who provide support for
your location.

To contact IBM Software support, follow these steps:

1. “Determining the business impact”
2. “Describing problems and gathering information” on page 122
3. “Submitting problems” on page 122

Determining the business impact

When you report a problem to IBM, you are asked to supply a severity level.
Therefore, you need to understand and assess the business impact of the problem
that you are reporting. Use the following criteria:
Severity 1
The problem has a critical business impact. You are unable to use the
program, resulting in a critical impact on operations. This condition
requires an immediate solution.
Severity 2
The problem has a significant business impact. The program is usable, but
it is severely limited.
Severity 3
The problem has some business impact. The program is usable, but less
significant features (not critical to operations) are unavailable.
Severity 4
The problem has minimal business impact. The problem causes little impact
on operations, or a reasonable circumvention to the problem was
implemented.

Appendix D. Support information 121

 Describing problems and gathering information
When describing a problem to IBM, be as specific as possible. Include all relevant
background information so that IBM Software Support specialists can help you
solve the problem efficiently. To save time, know the answers to these questions:
v What software versions were you running when the problem occurred?
v Do you have logs, traces, and messages that are related to the problem
symptoms? IBM Software Support is likely to ask for this information.
v Can you re-create the problem? If so, what steps were performed to re-create the
problem?
v Did you make any changes to the system? For example, did you make changes
to the hardware, operating system, networking software, and so on.
v Are you currently using a resolution for the problem? If so, be prepared to
explain the resolution when you report the problem.

Submitting problems
You can submit your problem to IBM Software Support in one of two ways:
Online
Click Submit and track problems on the IBM Software Support site
athttp://www.ibm.com/software/support/probsub.html. Type your
information into the appropriate problem submission form.
By phone
For the phone number to call in your country, go to the contacts page of
the IBM Software Support Handbook at
http://techsupport.services.ibm.com/guides/contacts.html and click the
name of your geographic region.

If the problem you submit is for a software defect or for missing or inaccurate
documentation, IBM Software Support creates an Authorized Program Analysis
Report (APAR). The APAR describes the problem in detail. Whenever possible,
IBM Software Support provides a resolution that you can implement until the
APAR is resolved and a fix is delivered. IBM publishes resolved APARs on the
Software Support Web site daily, so that other users who experience the same
problem can benefit from the same resolution.

122 IBM Tivoli Monitoring: Problem Determination Guide

Appendix E. Understanding informational, warning, and error
messages
This chapter introduces message logging and explains how to gather information
from those logs.

Message logging refers to the text and numeric messages created by IBM Tivoli
Monitoring. These messages relay information about how the system or application
is performing and can alert you to exceptional conditions when they occur.
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:
v Follow the instructions listed in the detail window of the message, if this is
included in the message.
v Consult the message details listed in this chapter to see what action you can take
to correct the problem.
v 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.

© Copyright IBM Corp. 2005 123

AMXUT0000I • AMXUT0014E

AMXUT0000I The command completed. AMXUT0007I Port is incorrect

Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

AMXUT0001E The operating system platform is not AMXUT0008I The command completed successfully.
supported. Refer to
LOG_NAME
Explanation: The operating system platform is
for more information.
deprecated or might be supported in the future.
Explanation: No additional information is available
Operator response: Wait for operating system
for this message.
platform support or run the program with a currently
supported operating system platform on the host.
AMXUT0009E The command did not complete. Refer
to the
AMXUT0002E A parse exception occurred on line
LOG_NAME
LINE_NUMBER of file FILE_NAME.
for more information.
Explanation: The XML file contains an error at the
Explanation: No additional information is available
specified line number.
for this message.
Operator response: Ensure that the XML file conforms
to the schema listed in the file header and try the
AMXUT0010W The command completed with
operation again.
warnings. Refer to the
LOG_NAME
AMXUT0003E A SAX exception occurred while log for more information.
parsing an XML file specified by the
Explanation: No additional information is available
user.
for this message.
Explanation: Either the parser was not found or is
corrupt.
AMXUT0011E The command did not complete. An
Operator response: The SAX parser has encountered a unknown unrecoverable error was
severe problem. Verify that the xercesImpl.jar and encountered while running the CLIs.
xmlParserAPIs.jar files are correct and not corrupted. Refer to the
LOG_NAME
log for more information and contact
AMXUT0004E The program cannot use the IBM Software Support.
FILE_NAME file.
Explanation: No additional information is available
Explanation: An I/O exception occurred while for this message.
reading the specified XML file because either the file or
access permission to the file does not exist.
AMXUT0012I SOAP logon validation failed.
Operator response: Verify that the file and access
permission to the file exists and try the operation again. Explanation: No additional information is available
for this message.
AMXUT0005E The XML schema SCHEMA_NAME
cannot be read. AMXUT0013E The command did not complete.
Explanation: The schema specified in XML file is not Explanation: Either the command was manually
supported. terminated by the user or an unexpected error occurred
with the software while attempting to process your
Operator response: Edit the XML file to include a request. The software terminated and cannot recover.
supported schema and try the operation again.
Operator response: If the command was not manually
terminated by the user, contact IBM Software Support.
AMXUT0006I The host name is unknown.
Explanation: No additional information is available AMXUT0014E The software cannot obtain the
for this message. current working directory from the
operating system.
Explanation: An unexpected error occurred with the
software while attempting to process your request. The

124 IBM Tivoli Monitoring: Problem Determination Guide

 AMXUT0015E • AMXUT2501E

software terminated and cannot recover.

AMXUT0049E The Java path is not correct.
Operator response: Contact IBM Software Support.
Explanation: The command could not continue
because the Java executable could not be run from the
AMXUT0015E The command did not complete on path specified, the version is not supported, or the
the specified computer. vendor is not supported.
Explanation: The command can is correct on the Operator response: Run the witmjavapath command
Tivoli management region host computer only. to update the path specified to a supported version of
Java. The supported versions of Java are the Java for
Operator response: Verify that the Tivoli management Tivoli included with TME and 1.4.x IBM JREs. Verify
region oserv server is running, log into that computer, that the access rights to run the Java executable are also
and run the command. correct.

AMXUT0016I The software is processing the current AMXUT0050E The Java path JAVA_PATH is not
request. correct.
Explanation: No additional information is available Explanation: The Java executable could not be run
for this message. from the path specified.
Operator response: Run the witmjavapath command
AMXUT0017E The NAME XML file was not saved. to update the path specified to a supported version of
Explanation: The directory in which the software Java. Verify that the access rights to run the Java
attempted to save the file does not exist and was not executable are also correct.
created because the user does not have permission to
create the specified directory. AMXUT0051E The Java version specified is not
Operator response: Verify that permission for the user correct. The Java version must be 1.3.x
to create a directory exists and try saving the XML file or greater. For full functionality the
again. version of Java must be 1.4.2.
Explanation: The tools require a JRE version that is at
AMXUT0018E The software cannot run the least 1.3.0. If situation association is desired, the JRE
command. must be 1.4.2.

Explanation: You do not have permission required to Operator response: Run the witmjavapath command
run the specified command. to update the path specified to a supported version of
Java. Verify that the access rights to run the Java
Administrator Response: Contact the Tivoli executable are also correct.
management region server administrator to acquire
authorization to run the command.
AMXUT0052I The java path has been verified and
stored.
AMXUT0019E The operation was not completed.
Explanation: No additional information is available
Explanation: The system does not have enough for this message.
memory to complete the operation.
Operator response: Contact IBM Software Support. AMXUT0055I The current java path is defined as
JAVA_PATH.
AMXUT0020W All files were not removed. Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
AMXUT2501E The baseline file BASE_FILENAME is
AMXUT0021W A termination signal for this tool was not accessible.
received. The tool is busy removing Explanation: The program cannot access the baseline
temporary files and will exit upon file because it is not in the specified location or the
completion. access to the file is not permitted.
Explanation: No additional information is available Operator response: Verify that the file exists in the
for this message. specified location and the correct access rights exists for
the file.

Appendix E. Understanding informational, warning, and error messages 125

AMXUT2502E • AMXUT2516I

AMXUT2502E The temporary data file AMXUT2509I Distributed Monitoring was not
TEMP_FILENAME was not created. installed on the endpoint ENDPOINT
and will be excluded from the baseline.
Explanation: Access to the directory in which the
program attempted to create the file was denied or Explanation: No additional information is available
there is not enough space in the directory to create the for this message.
file.
Operator response: Verify that the permissions to AMXUT2510I The EP_PLATFORM platform for the
access the specified directory exist and the directory endpoint ENDPOINT is not supported.
has enough available space to create the file. The endpoint was excluded from the
baseline.
AMXUT2503E The program cannot access the Explanation: No additional information is available
temporary data file TEMP_FILENAME. for this message.
Explanation: The program cannot access the specified
file. AMXUT2511W The gateway GATEWAY for the
endpointENDPOINT was not included
Operator response: Verify that directory access rights
in the baseline.
exist for reading the specified file and try the operation
again. Explanation: No additional information is available
for this message.
AMXUT2504I The software is creating a new
baseline file TEMP_FILENAME. AMXUT2512I The endpoint ENDPOINT has
Distributed Monitoring installed and
Explanation: No additional information is available
was included in the baseline.
for this message.
Explanation: No additional information is available
for this message.
AMXUT2505I The software is collecting the new
infrastructure deployment status using
the baseline file TEMP_FILENAME. AMXUT2513W The number of parameters for the
line LINEIN is incorrect and was
Explanation: No additional information is available
discarded. The endpoint was excluded
for this message.
from the baseline.
Explanation: No additional information is available
AMXUT2506E The baseline file BASE_FILENAME
for this message.
was not created.
Explanation: An error occurred while attempting to
AMXUT2514I The software is processing the
write the baseline file.
gateway data file: GW_FILE.
Operator response: Verify that directory access rights
Explanation: No additional information is available
exist for the directory and the directory contains
for this message.
enough available space for the file. Contact IBM
Software Support if the problem still exists after
following these suggestions. AMXUT2515I Distributed Monitoring is installed on
gateway Gateway and the gateway was
included in the baseline.
AMXUT2507E The baseline file BASE_FILENAME
was not created. Explanation: No additional information is available
for this message.
Explanation: The program terminated abnormally
while attempting to write the baseline file.
AMXUT2516I Distributed Monitoring is not installed
Operator response: Contact IBM Software Support.
on gateway Gateway or this gateway is
not valid or available. Therefore the
AMXUT2508I Processing the endpoint data file: gateway was excluded from the
EP_FILE. baseline.

Explanation: No additional information is available Explanation: No additional information is available

for this message. for this message.

126 IBM Tivoli Monitoring: Problem Determination Guide

 AMXUT2517W • AMXUT2530E

AMXUT2517W The line LINEIN has the incorrect AMXUT2523I Creating a new hub element in the
number of parameters and was baseline.
discarded. The gateway was excluded
Explanation: No additional information is available
from the baseline.
for this message.
Explanation: No additional information is available
for this message.
AMXUT2524I Adding the gateway GATEWAY
requires the creation of a new hub
AMXUT2518E The program cannot read the element in the baseline to accommodate
PROP_FILENAME file. the required additional remote servers.
A new hub element was created.
Explanation: The program cannot read the scale
factors from the properties file within the ScanTmr.jar Explanation: No additional information is available
file because the file was modified or the program does for this message.
not have permission to access the file.
Operator response: Verify that the file was not AMXUT2525I Creating a new remote server element
modified and that permission to access the file exists. in the baseline for the gateway
Contact IBM Software Support if the file was not GATEWAY.
modified and the appropriate access rights exist.
Explanation: No additional information is available
for this message.
AMXUT2519I The IP address IPADDRESS was not
resolved to a host name. The IP address
AMXUT2526I The number of endpoints per remote
was recorded in the baseline file in
server was exceeded for gateway
place of the host name.
GATEWAY. A new remote server
Explanation: No additional information is available element was created.
for this message.
Explanation: No additional information is available
for this message.
AMXUT2520I The software is converting the Tivoli
management region data into a new
AMXUT2527I The software is adding an OS agent
infrastructure deployment model using
element to the baseline for the Endpoint
the baseline file.
endpoint.
Explanation: No additional information is available
Explanation: No additional information is available
for this message.
for this message.

AMXUT2521I The calculated number of remote

AMXUT2528I The software is writing the new
servers scale factor for the gateway
deployment infrastructure to the
GATEWAY is NUM_SERVERS and the
baseline file BASE_FILENAME.
scale factor for the calculated number of
endpoints per remote server is Explanation: No additional information is available
NUM_EPS for this message.
Explanation: No additional information is available
for this message. AMXUT2529I The software is converting Tivoli
management region TMR_NAME data
into the new deployment model.
AMXUT2522W The calculated number of remote
servers for the GATEWAYgateway Explanation: No additional information is available
exceeds the maximum number of remote for this message.
server per hub. The maximum number
is MAX_NUM_EPS.
AMXUT2530E The output file was not created in the
Explanation: No additional information is available OUTPUT_FILE_PATH.
for this message.
Explanation: Permission to write the file to the
specified directory does not exist.
Operator response: Acquire permission to write to the
specified directory and try the creating the file again.

Appendix E. Understanding informational, warning, and error messages 127

AMXUT2531E • AMXUT2700E

server is correct and try the operation again.

AMXUT2531E Cannot connect to the Tivoli
Enterprise Portal Server.
AMXUT2538I The number of gateways with
Explanation: The Java version or the specified host
Distributed Monitoring is
name, user name, or password is incorrect.
TOTAL_DMGW.
Operator response: Verify that the correct host name,
Explanation: No additional information is available
user name or password and try the operation again. In
for this message.
addition, the JRE version must be IBM JAVA version
1.4.x. Use the witmjavapath command to verify the
version of Java. AMXUT2539I The gateway GATEWAY contains
TOTAL_DMEP endpoints with
Distributed Monitoring.
AMXUT2532E Unable to connect to the SOAP sever.
Explanation: No additional information is available
Explanation: The specified host name is incorrect or
for this message.
SOAP server is not enabled.
Operator response: Verify that the host name is
AMXUT2540E The baseline file BASELINE was not
correct and the SOAP is enabled before attempting the
created because it already exists.
operation again.
Explanation: You attempted to create a baseline file
using the witmscantmr -c command. The file was not
AMXUT2533W Cannot verify that the Hub exists.
created because it already exists and cannot not be
Explanation: The host name is not correct or the Hub overwritten.
is not deployed.
Operator response: If you want to create a new
Operator response: Verify that the correct host name baseline file, remove or rename the specified baseline
and the Hub is deployed before attempting the file or use the following command to validate the
operation again. deployment of the contents of the baseline file:
witmscantmr -v [-f <filename>.xml]
AMXUT2534W The OS agent connected to the Hub
was not found.
AMXUT2541E User or Pass for SOAP server SOAP is
Explanation: The specified OS agent name is incorrect null or empty.
or is not deployed.
Explanation: An attempt to make a connection to the
Operator response: Verify that the correct OS agent SOAP server was not successful.
host name and the OS agent is deployed before
Operator response: Verify that baseline file has the
attempting the operation again.
User/Pass filled in.

AMXUT2535W OS agent was not found.

AMXUT2600I The results of the witmscantmr
Explanation: The specified OS agent host name is command were saved to the file:
incorrect or is not deployed. BASELINE.
Operator response: Verify that the OS agent host Explanation: No additional information is available
name is correct and the OS agent is deployed before for this message.
attempting the operation again.
AMXUT2614I The software is processing the event
AMXUT2536W The remote server was not found. server data file: GW_FILE.
Explanation: The remote server is not running or the Explanation: No additional information is available
specified host name is incorrect. for this message.
Operator response: Verify that the Remote Server host
name is correct and that the Remote Server is running. AMXUT2700E An unexpected exception occurred
while attempting to get a list of
EventServer objects.
AMXUT2537E The hub management server was not
found. Explanation: The Tivoli Management Framework
returned an unexpected exception when a request was
Explanation: An attempt to make a connection to the
made to obtain the list of EventServer objects. The
SOAP server was not successful.
software terminated and cannot recover.
Operator response: Verify that the name of the SOAP

128 IBM Tivoli Monitoring: Problem Determination Guide

 AMXUT2701E • AMXUT5012W

Operator response: Contact IBM Software Support.

AMXUT5004I The assess tool is loading the baseline
file name into memory.
AMXUT2701E The software was unable to obtain
Explanation: No additional information is available
the list of Tivoli gateway servers.
for this message.
Explanation: The software requested a list of gateway
servers in order to obtain the current list of endpoints.
AMXUT5005I The assess tool is loading all the
The are no gateways defined on this region. Therefore,
mapping files stored in dir into memory.
the execution of the command terminated.
Explanation: No additional information is available
Operator response: The command must be executed
for this message.
in a supported 3-tier environment.

AMXUT5006I The assess tool is starting to assess the

AMXUT2702E An unexpected exception occurred
resources.
while attempting to get a list of
Gateway objects. Explanation: No additional information is available
for this message.
Explanation: The Tivoli Management Framework
returned an unexpected exception when a request was
made to obtain the list of Gateway objects. The AMXUT5007I All resources are assessed. Processing
software terminated and cannot recover. is complete.
Operator response: Contact IBM Software Support. Explanation: No additional information is available
for this message.
AMXUT4000I
NAME AMXUT5008I The assess tool is assessing resource
witmjavapath name of type type.
SYNOPSIS
Explanation: No additional information is available
[{path | -? }]
for this message.
WHERE:
pathThe path of the Java executable to
be stored. AMXUT5009I The assess tool is assessing
-?Prints the witmjavapath help message. sub-resource name belonging to resource
Executing the command without type.
parameters will return the
current Java path. Explanation: No additional information is available
for this message.
Explanation: No additional information is available
for this message.
AMXUT5010W The monitor mon that belongs to the
Sentry profile prof cannot be upgraded
AMXUT5001E The resource file name was not parsed. because it is deprecated.
Explanation: The specified resource file is not Explanation: No additional information is available
formatted correctly. for this message.
Operator response: Call IBM Software Support.
AMXUT5011W The endpoint class class cannot be
upgraded because it is deprecated.
AMXUT5002E The resource file name was not found.
Explanation: No additional information is available
Explanation: The specified resource file does not exist
for this message.
or cannot be read.
Operator response: Contact IBM Software Support.
AMXUT5012W The monitor mon cannot be upgraded
because it is not member of the Tivoli
AMXUT5003I The assess tool is loading the monitoring collection coll.
resources to assess in the Tivoli
Explanation: No additional information is available
management region environment from
for this message.
the temporary filename .
Explanation: No additional information is available
for this message.

Appendix E. Understanding informational, warning, and error messages 129

AMXUT5013E • AMXUT5024E

Level 3 Support: Assist the customer with running the

AMXUT5013E The resource typename of the type type
idlcall command manually.
was not assessed.
Explanation: This resource information was not
AMXUT5019W Expected mapping files were not
assessed because a Distributed Monitoring engine is
found in the directory name. This might
not running, a managed node is unavailable, or
indicate that they were unintentionally
resource information was not exchanged in an
removed. Restore the files from the
interconnected region.
installation CD.
Operator response: If the resource is an endpoint,
Explanation: No additional information is available
verify that the endpoint is available from the current
for this message.
Tivoli management region and that the Distributed
Monitoring engine is running on the endpoint.
AMXUT5020W The profile name does not contain the
If the resource is a profile or a profile manager, verify
monitors in the collections you specified
that the managed node hosting the resource is
with the -a option. The XML output file
available.
does not include the specified monitors.
If the resource resides in an interconnected region,
Explanation: No additional information is available
verify that all the resources were exchanged.
for this message.

AMXUT5014W The sub-resource name of the

AMXUT5021W Windows NT is not supported. Use
resource type was not assessed because
the Windows 2000 monitoring family.
the application was not specified with
the command line -a option. Explanation: No additional information is available
for this message.
Explanation: No additional information is available
for this message.
AMXUT5022E The specified monitoring collection is
not supported.
AMXUT5015I The assessment output of the name
resource was saved as filename. Explanation: The monitoring collection specified using
the -a option in the assess tool is an unsupported
Explanation: No additional information is available
monitoring collection and cannot be used.
for this message.
Operator response: Specify a supported monitoring
collection and run the assess tool again.
AMXUT5016I The result of the assessment is stored
in the following files:
AMXUT5023E The endpoint ep was not assessed.
Explanation: No additional information is available
for this message. Explanation: The endpoint properties label and
operating system version were not found.
AMXUT5017E The custom monitor name of collection Operator response: Verify that the endpoint is
coll was not assessed. running and connected to a gateway. Verify that the
gateway to which the endpoint is connected is running.
Explanation: The software cannot determine whether
If the endpoint resides in a different region than the
the monitor type is string or numeric because an error
gateway, verify that the two regions are connected and
occurred while parsing the monitor’s Capability
required resources were exchanged.
Specification Language data.
Operator response: Contact IBM Software Support.
AMXUT5024E The endpoint ep was not assessed.
Level 3 Support: Assist the customer with running the The endpoint class name is unsupported
mcsl command manually. to be migrated in the interp platform.
Explanation: The specified endpoint class was not
AMXUT5018E The custom monitor name of collection assessed because is not supported in this platform. This
coll was not assessed. error can also occur if the corresponding mapping file
is missing.
Explanation: The software cannot determine whether
the monitor implementation is a monitor program or Operator response: Try to assess an endpoint running
script because an error occurred while parsing the in a supported platform. If you believe that this
monitor’s Capability Specification Language data. endpoint is running in a supported platform, restore
the mapping file to its default directory.
Operator response: Contact IBM Software Support.

130 IBM Tivoli Monitoring: Problem Determination Guide

 AMXUT5025E • AMXUT5036E

AMXUT5025E The command failed because the AMXUT5032E The endpoint name was not assessed.
specified syntax is incorrect.
Explanation: The endpoint is not responding.
Explanation: A resource was specified more than once
Operator response: Verify that the endpoint is
in the command line interface.
running and that the gateway that owns the specified
Operator response: Remove the duplicate resource endpoint is running.
from the command and try again
AMXUT5033E The profile name was not assessed.
AMXUT5026W The specified resource "name" is not
Explanation: The specified profile data was not
of the expected type "type".
retrieved.
The assess tool will ignore this resource
and will not assess it. Operator response: Verify that the profile is accessible
by the current Tivoli management region. If the profile
Explanation: No additional information is available
resides on an interconnected region, verify that the
for this message.
regions are connected and exchange the SentryProfile
resources between the regions. The profile may be
AMXUT5027E The specified resources were not locked if the profile is currently being edited. If the
assessed because the command inlcuded profile is being edited, save the changes to the profile
incorrect syntax. before attempting to assess this profile again.
Explanation: The -r option cannot be specified with
the -e, -p, nor -pm options. AMXUT5034E The profile manager name was not
assessed.
Operator response: Correct the command syntax to
specify resources to assess and try again. Explanation: The profile manager data was not
available.
AMXUT5028E The command failed because the Operator response: Verify that the profile manager is
specified syntax is incorrect. accessible to the current Tivoli management region. If
the profile manager resides in an interconnected region,
Explanation: The -r option can be specified only one
verify that the regions are connected and exchange the
time.
ProfileManager resources between the regions. If you
Operator response: Correct the syntax, specifying the are running the assess tool in an interconnected Tivoli
-r option one time, and run the command again. management region that follows the hub-spoke
architecture and the profiles inside this profile manager
are not locally accessible, use the flatten option.
AMXUT5029E The command failed because the
specified syntax is incorrect.
AMXUT5035E The Agent Config Descriptor file name
Explanation: The -f option can be specified only one is unavailable.
time.
Explanation: The program was unable to access the
Operator response: Correct the syntax, specifying the Agent Config Descriptor file.
-f option one time, and run the command again.
Operator response: Verify that the file exists in the
specified location and the correct access rights exists for
AMXUT5030E The command failed because incorrect the file. The Agent Config Descriptor file is created
parameters were specified. during installation. If you cannot locate the file, call
Explanation: The resource file specified with the -r IBM Software Support for a copy.
option cannot be read or is formatted incorrectly.
Operator response: Verify that the resource file AMXUT5036E The Agent Config Descriptor file name
specified with the -r option exists and is formatted was not parsed.
correctly and run the command again. Explanation: The program was unable to parse the
specified file because it was changed or contains
AMXUT5031W The gateway name is down. incorrect data.
Endpoints attached to this gateway Operator response: The Agent Config Descriptor file
cannot be assessed. is created during installation. If you cannot locate the
Explanation: No additional information is available file, call IBM Software Support for a copy.
for this message.

Appendix E. Understanding informational, warning, and error messages 131

AMXUT5037E • AMXUT5047E

AMXUT5037E The command failed because the AMXUT5043W The situation name from Profile prof
specified syntax is incorrect. contains a formula dependent on
information stored in the subscribers to
Explanation: An incorrect value was specified with
this Profile’s enclosing Profile Manager.
the -o option.
This profile will only be successfully
Operator response: Correct the syntax, specifying a upgraded if it’s part of the assessment
correct value with the -o option. and upgrade of its enclosing Profile
Manager.
AMXUT5038W The profile manager name does not Explanation: No additional information is available
contain any Sentry profiles. It cannot be for this message.
assessed.
Explanation: No additional information is available AMXUT5044E The Profile Manager pm was not
for this message. assessed.
Explanation: The Profile Manager doesn’t have any
AMXUT5039W The endpoint subscriber name cannot subscribers. Yet it encloses some Profiles that have
be assessed because the Distributed situations with formulae dependent on information that
Monitoring engine was not found can only be obtained from potential subscribers to this
running on the endpoint. If you are Profile Manager.
certain the endpoint is running on the
Operator response: Subscribe at least one subscriber
Distributed Monitoring engine, update
to this Profile Manager and try again.
the baseline file used in this assessment
to reflect the correct status of this
endpoint. AMXUT5045W None of the subscribers to the Profile
Manager prof match the application type
Explanation: No additional information is available
of the monitors in some of its Profiles.
for this message.
Explanation: No additional information is available
for this message.
AMXUT5040W The monitor name was not found in
any mapping file. The assess tool
assumes that this is a custom monitor. AMXUT5046E The Situation sit was not assessed.
Explanation: No additional information is available Explanation: This situation have formulae dependent
for this message. on information that can only be obtained from
subscribers to its enclosing Profile Manager. This
information couldn’t be obtained from the subscribers
AMXUT5041W Nothing to assess. The assess tool
beacuse of a unexpected error.
will exit now.
Operator response: Contact IBM Software Support for
Explanation: No additional information is available
instructions on how to use the TME command
for this message.
IDLCALL.

AMXUT5042E The endpoint name was not assessed.

AMXUT5047E The Assess tool could not contact the
Explanation: The operating system release of the Endpoint ep.
endpoint’s host is not supported.
Explanation: The Assess tool could not retrieve this
Operator response: The operating system release is Endpoint’s list of environment variables (Target
not supported at this time. Upgrade the release of this Environments).
endpoint’s host operating system to a supported
Operator response: This usually means the Endpoint
release. This error can also appear if the OS release
in question is down or unresponsive. The Assess tool
could not be determined for this endpoint. If you
will continue the assessment ignoring this Endpoint’s
believe the endpoint’s OS release is supported, contact
Target Environment. However, the operator needs to
IBM Software Support.
make sure the Endpoint is up and running.

132 IBM Tivoli Monitoring: Problem Determination Guide

 AMXUT5048W • AMXUT7003E

AMXUT5048W The assess tool found that the AMXUT5052W The specified endpoint "name" is not
monitor mon is configured to send Tivoli responsive.
Enterprise Console (TEC) events to The assess tool will ignore this endpoint
multiple servers. IBM Tivoli Monitoring and will not assess it.
6.1 doesn’t support this configuration.
Explanation: No additional information is available
Only the first defined TEC server
for this message.
named server will be used in the
assessment.
AMXUT5053I The assess tool is checking each
Explanation: No additional information is available
endpoint specified for responsiveness.
for this message.
This may take a while. Please wait...
Explanation: No additional information is available
AMXUT5049W The assess tool found that the
for this message.
monitor mon is configured to send Tivoli
Enterprise Console (TEC) events to a
server named server. The tool was AMXUT5054W The specified endpoint "name" is not
unable to translate the server name into subscribed to some of the Profile
the proper address format using the user Managers being assessed. Since this
specified information obtained from the endpoint is used as a filter, this may
baseline infrastructure files. Events will result in Profile Manager assessment
not be forwarded to the server unless files with no subscribers.
the EventServerList elements have been
updated in the baseline files. The Explanation: No additional information is available
format of the address should be for this message.
IPaddress:port or Hostname:port.
Explanation: No additional information is available AMXUT5055W The specified profile "name" is not a
for this message. member of some of the Profile
Managers being assessed. Since this
profile is used as a filter, this may result
AMXUT5050E The assess tool encountered an in Profile Manager assessment files with
incorrect resource and terminated. no profiles.
Explanation: A resource was specified which can not Explanation: No additional information is available
be assessed because either the type of resource was for this message.
incorrect or the resource did not include Distributed
Monitoring resources.
AMXUT7001E The resource file was not found.
Operator response: Review the messages above and
remove any resource which was determined to be Explanation: The resource file was not passed into the
incorrect before attempting the command again. program.
Operator response: Call IBM Software Support.
AMXUT5051W The assess tool found that the profile
prof with OID oid has not been AMXUT7002E The resource file name was not parsed.
distributed to endpoint ep. This profile
contains custom monitors, and when Explanation: The resource file is not formatted
upgraded, the corresponding situations correctly.
will fail to run properly on this Operator response: Call IBM Software Support.
endpoint’s Universal Agent. Please
distribute this profile to this endpoint,
and then re-assess and re-upgrade this AMXUT7003E You cannot connect to the server name
endpoint so the Universal Agent can with the userid id and the password
pick up the changes. password.

Explanation: No additional information is available Explanation: The specified user cannot connect to the
for this message. Tivoli Enterprise Monitoring Server because the
password is incorrect or the user does not have
authority to connect to the server.
Operator response: Refer to the output file for error
messages for more information regarding the state of
the Tivoli Enterprise Monitoring Server SOAP

Appendix E. Understanding informational, warning, and error messages 133

AMXUT7004E • AMXUT7016E

connection. The service is not running or the specified Operator response: Specify a correct file and re-run
URL is incorrect. the command.

AMXUT7004E The specified URL is incorrect. AMXUT7011E The program did not create the file
BASE_FILENAME.
Explanation: The URL for the SOAP connection that
was attempted is not a well formed URL. Explanation: An error occurred while attempting to
write the upgrade-specified output file.
Administrator Response: Verify that the host name
and port specified in the baseline file is correct. Operator response: Contact IBM Software Support.

AMXUT7005E The specified server cannot contact AMXUT7012E The profile P_NAME containing
SOAP service. monitor M_NAMEwas not cleaned.
Explanation: The SOAP service is not running. Explanation: The disable_criterion idlcall did not send
a successful return code.
Administrator Response: Verify that the SOAP service
is running on the server and try the connection again. Operator response: Run idlcall PROFILE_OID
disable_criterion MONITOR_ID or disable the profile
within the Tivoli management region interface.
AMXUT7006E The situation name cannot be added.
Explanation: The situation was not added to the list of
AMXUT7013E The profile manager NAMEwas not
situations to be processed
cleaned.
Operator response: Call IBM Software Support.
Explanation: The endpoint or profile contained in the
profile manager failed to finish cleaning. Since the
AMXUT7007E The situations cannot be processed. cleanup command is not destructive the endpoint or
profile continues to run.
Explanation: SOAP entries for situations, managed
system lists, and application agents cannot be created if Operator response: Check the log for the endpoint or
a SOAP server connection does not exist. profile that failed to finish cleaning. After you
determine which endpoint or profile was not cleaned,
Administrator Response: Verify that the SOAP service run idlcall PROFILE_OID disable_criterion
is running on the hub server specified in the baseline MONITOR_ID to disable a profile or wdisprb -z "*" "*"
file. If the SOAP service is not running, configure the [Application| "*" for all] ENDPOINT_NAME to disable
hub Tivoli Enterprise Monitoring Server to accept an endpoint.
SOAP connections.

AMXUT7014E The NAME endpoint was not cleaned.

AMXUT7008E The endpoint name was not created.
Explanation: The wdisprb command did not send a
Explanation: The endpoint was not created because successful return code.
the idlcall did not exit.
Operator response: Run wdisprb -z "*" "*"
Operator response: Call IBM Software Support. [Application| "*" for all] ENDPOINT_NAME
Level 3 Support: Assist the customer with using the
installOSAgent IDL call manually. AMXUT7015E The managed system listname was not
added.
AMXUT7009E Endpoint name was not removed. Explanation: The managed system list was not added
Explanation: The endpoint was not removed because to the managed system lists to be processed.
the idlcall did not exit. Operator response: Call IBM Software Support.
Operator response: Call IBM Software Support Level 3 Support: This exception is not used but exists
Level 3 Support: Assist the user with using the if the event that implementation changes.
uninstallOSAgent IDL call manually.
AMXUT7016E The managed system lists were not
AMXUT7010E The upgrade was canceled because the processed.
correct baseline file was not specified. Explanation: The managed system lists were not
Explanation: The baseline file was not found with the processed because there is no connection to the Tivoli
-f flag or in the $DBDir/AMX/shared/analyze/scans Enterprise Monitoring Server server.
directory. Administrator Response: Verify that the SOAP service

134 IBM Tivoli Monitoring: Problem Determination Guide

 AMXUT7017E • AMXUT7052I

is running on the hub server specified in the baseline

AMXUT7023W Situations will not be associated
file. If the SOAP service is not running, configure your
with objects in the navigation tree
hub Tivoli Enterprise Monitoring Server to accept
because the Java version or Java vendor
SOAP connections.
are not compatiable with this feature.
The Java version was found to be version
AMXUT7017E The application app was not installed and the vendor was found to vendor. The
on the endpoint NAME. required version is 1.4.2 and the vendor
must be IBM Corporation.
Explanation: The installation of the application agent
on the specified endpoint did not send a correct return Explanation: No additional information is available
code. for this message.
Operator response: Manually install the application
from the Tivoli Enterprise Portal console. AMXUT7024W The portal server version could not
be connected with. Situation association
will not be possible.
AMXUT7018E The application app was not removed
from the endpoint NAME. Explanation: No additional information is available
for this message.
Explanation: The uninstallation of the application
agent from the specified endpoint did not send a
correct return code. AMXUT7025W The situation situation is unable to
be associated with the object object.
Operator response: Manually uninstall the application Association will need to be done
from the Tivoli Enterprise Portal. manually.
Explanation: No additional information is available
AMXUT7019W The upgrade tool cannot connect to for this message.
the SOAP service using SSL (HTTPS). A
connection with the same port and URL
over HTTP will be attempted. AMXUT7026I The situation situation has been
associated with the object object.
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
AMXUT7020E An SSL connection was not
established because IBMJSSE was not AMXUT7050W A correct profile, endpoint, or
found profile manager to upgrade was not
found in the list of files specified on the
Explanation: IBMJSSE specifies how to make an SSL command line.
connection. HTTP or HTTPS connections are not
attempted to protect data. Explanation: No additional information is available
for this message.
Operator response: Verify that the JAR ibmjsse.jar is
located in the $DBDIR/generic_unix/TME/ITM
Upgrade/ITMUpgradeManager/java/java_includes AMXUT7051I An error occurred when writing the
directory and that the file is readable. names of files created during the
upgrade process. Although all files were
created, the returned list might be
AMXUT7021W The SOAP server server failed to incomplete.
connect times times. No more attempts to
connect to the server will be made. Explanation: No additional information is available
for this message.
Explanation: No additional information is available
for this message.
AMXUT7052I The file name was found in the
directory dirname and will be used with
AMXUT7022W The managed system system could the witmupgrade command.
not be added to the managed system list
list because the managed system list Explanation: No additional information is available
type is not supported or not known. for this message.
Explanation: No additional information is available
for this message.

Appendix E. Understanding informational, warning, and error messages 135

AMXUT7053E • AMXUT7105I

the file will be updated. If recycling is not an option

AMXUT7053E The file name was not processed
run the following: 1) Bring up IE browser 2) Type the
because it was not found.
following URL
Explanation: No additional information is available (http://your_tems_hostname:1920///cms/soap/
for this message. kshhsoap.htm) and hit ENTER. 3) Paste the following
SOAP payload in the PayLoad (XML) box and click
"Make SOAP Request"
AMXUT7054W The software did not find a correct
absolute path from the relative path sysadmin
name specified.
O4SRV.UTCTIME
Explanation: No additional information is available
SELECT RESPONSE FROM SYSTEM.DSCMD WHERE
for this message.
SYSTEM.PARMA
COMMAND
AMXUT7055E The Tivoli Enterprise Monitoring
Server name in the baseline file is not START KFAOMTEC.KFAOTMGR,,REFRESH TYPE=EIF
defined.
, 80);(
Explanation: The Tivoli Enterprise Monitoring Server
name in the baseline file is not defined, server name is
required so the endpoint can be deployed on the AMXUT7100I The situation name was added.
correct server. Explanation: No additional information is available
Operator response: Type in the Tivoli Enterprise for this message.
Monitoring Server name in the baseline file.
AMXUT7101I The situation name was not added
AMXUT7056E The value for the installDir attribute because it already exists.
contains a blank character. The Explanation: No additional information is available
installDir is install_dir. for this message.
Explanation: The installation directory specified in the
baseline xml file includes a blank character which is AMXUT7102I The situation name was deployed to
not supported by the installation program. the target target.
Operator response: Update the installdir attribute in Explanation: No additional information is available
the baseline xml file by removing any blank spaces for this message.
from the installation directory path.

AMXUT7103I The situation name was removed.

AMXUT7075I Processing endpoint: EP_NAME.
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.

AMXUT7104I The situation name was not removed

AMXUT7076I Processing profile: PROF_NAME. because it does not exist.
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

AMXUT7077I Processing profile manager: AMXUT7105I The file name specifies an object that
PM_NAME. cannot be processed.
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

AMXUT7078E Failed to reload the TEC forwarding

components on the server. The hub
server must be recycled before TEC
event will be sent.
Explanation: The call to refresh the TEC forwarding
files has failed because the SOAP call did not complete.
Operator response: Recycle the TEMS manually and

136 IBM Tivoli Monitoring: Problem Determination Guide

 AMXUT7106I • AMXUT7162W

AMXUT7106I The name situation was not deployed AMXUT7155I The target environment was removed
to the specified target target because the for the application appname and the
target does not exist. This is not an error profile profname on the endpoint epname.
unless the specific target has already
Explanation: No additional information is available
been created on the Tivoli Enterprise
for this message.
Management Server. This message will
be displayed if the resources being
upgraded do not include both UNIX and AMXUT7156W The target environment was not
Linux endpoints. This message will also removed from the application appname
be displayed if the profile manager and the profile profname on the endpoint
containing this profile has not been epname.
upgraded and the specific target
mentioned above has not already been Explanation: No additional information is available
created. In the later two scenarios, the for this message.
displaying of this message does not
indicate an error has actually occurred AMXUT7157I The target script was created for the
but instead indicates some additional profile profilename containing
resources might still need to be monitorname monitor type of type.
upgraded.
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.

AMXUT7158W The target script was not created for

AMXUT7150I The endpoint name was deployed to the profile profilename containing the
the target server target . monitor monitorname of the type type.
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

AMXUT7151I The endpoint name of the product AMXUT7159I The target script was removed for
product type was deployed to the target profile profilename containing the
target server. monitor monitorname of type type.
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

AMXUT7152I The endpoint name of the product AMXUT7160W The script for the profile profilename
product type was removed from the containing the monitor monitorname of
target server target. type typewas not removed.
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

AMXUT7153I The target environment was created AMXUT7161I A target environment was created for
for the application appname and the profile profilename on the endpoint
profile profname on the endpoint epname . epname . If the profile profilename
Explanation: No additional information is available contained custom scripts and was
for this message. already upgraded, you must upgrade the
profile again on the epname endpoint.

AMXUT7154W The target environment was not Explanation: No additional information is available
created for the application appname and for this message.
the profile profname on the endpoint
epname. AMXUT7162W The temp file filename was not created
Explanation: No additional information is available for the inline script scriptname.
for this message. Explanation: No additional information is available
for this message.

Appendix E. Understanding informational, warning, and error messages 137

AMXUT7163W • AMXUT7255W

AMXUT7163W The endpoint specified epname was AMXUT7202I The endpoint name was disabled.
not found in the included baseline files.
Explanation: No additional information is available
Verify that the source attribute in the
for this message.
baseline and assess file match for the
epname endpoint.
AMXUT7250W The upgrade tool was manually
Explanation: No additional information is available
stopped. The next task to be processed
for this message.
by the upgrade command would have
name.
AMXUT7164W Event forwarding was not set for the
Explanation: No additional information is available
situation situation on the Tivoli
for this message.
Enterprise Monitoring Server endpoint
endpoint.
AMXUT7251W The upgrade tool was manually
Explanation: No additional information is available
stopped. The next task to be processed
for this message.
by the upgrade command was to resolve
the managed system name for the ip
AMXUT7165I Event forwarding was set for the address ip.
situation situation on the Tivoli
Explanation: No additional information is available
Enterprise Monitoring Server endpoint
for this message.
endpoint.
Explanation: No additional information is available
AMXUT7252W The upgrade tool was manually
for this message.
stopped. The next task to be processed
by the upgrade command was to install
AMXUT7166W The situation situation cannot be or remove the operating system agent
added because it contains attributes that for the endpoint epname.
are defined when the dm37x.mdl
Explanation: No additional information is available
meta-file is loaded. This happens the
for this message.
first time an endpoint is successfully
upgraded and the universal agent is
running. The situation can be upgraded AMXUT7253W The upgrade tool was manually
after a single endpoint is successfully stopped. The next task to be processed
upgraded and the universal agent is by the upgrade command was to install
started. or remove an application agent on the
system sysname.
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
AMXUT7167I The endpoint name was downgraded
from the target server target. Reboot this AMXUT7254W The upgrade tool was manually
host before attempting to upgrade again. stopped. The next task to be processed
by the upgrade command was to create
Explanation: No additional information is available
or remove the managed system lists.
for this message.
Explanation: No additional information is available
for this message.
AMXUT7200I The profile PROFILE_NAME that
contains the monitor MONITOR_NAME
was disabled successfully. AMXUT7255W The upgrade tool was manually
stopped. The next task to be processed
Explanation: No additional information is available
by the upgrade command was to create
for this message.
or remove situations.
Explanation: No additional information is available
AMXUT7201I The profile manager name was
for this message.
disabled.
Explanation: No additional information is available
for this message.

138 IBM Tivoli Monitoring: Problem Determination Guide

 AMXUT7256W • AMXUT7511I

AMXUT7256W Monitor monname does not have any AMXUT7505E The agent was not configured.
thresholds.
Explanation: An error occurred with the kinconfg
Explanation: No additional information is available utility.
for this message.
Operator response: Refer to the log files in
$CANDLE_HOME/logs for details. Contact IBM
AMXUT7257W Monitor mon1name is deprecated. Software Support if you cannot resolve the error.
Explanation: No additional information is available
for this message. AMXUT7506E The agent was not started.
Explanation: An error occurred with the kinconfg
AMXUT7500E The agent was not installed. utility.
Explanation: The target Tivoli Enterprise Monitoring Operator response: Refer to the log files in
Server was not specified. $CANDLE_HOME/logs for details. Contact IBM
Software Support if you cannot resolve the error.
Operator response: Specify a target server and try
installing the agent again.
AMXUT7507I Run the setup utility manually from
the agent host in
AMXUT7501E The agent was not installed.
CANDLE_HOME\\INSTALL to
Explanation: An agent install file does not exist or uninstall the OS monitoring agent.
cannot be opened.
Explanation: No additional information is available
Operator response: Verify that the target file system for this message.
has the required available space and that you have
write permission before attempting to install the agent
AMXUT7508W The specified monitor was not
again.
upgraded because it is deprecated.
Explanation: No additional information is available
AMXUT7502E The agent was not installed.
for this message.
Explanation: The agent installation log on the
endpoint, indicates that an error occurred.
AMXUT7509W The specified application was not
Operator response: Review the agent installation log upgraded because it is deprecated.
and the lcfd.log on the endpoint for more information.
Explanation: No additional information is available
On Windows, the installation log is located under
for this message.
installDir/Install/Abort IBM Tivoli Monitoring
timeStamp.log. On UNIX, the log is located under
installDir/logs/candle_installation.log. Contact IBM AMXUT7510E The agent was not uninstalled
Software Support if you cannot resolve the error. correctly.
Explanation: The agent registry file still exists.
AMXUT7503E The agent was not installed.
Operator response: Remove registry files manually
Explanation: The installation file was not copied to from install_dir/registry/ux*.ver on UNIX or
the $CANDLE_HOME/VER/ directory. instal_dir\\install\\ver\\KNTWICMA.ver on
Windows.
Operator response: Refer to the log files in
$CANDLE_HOME/logs for details. Contact IBM
Software Support if you cannot resolve the error. AMXUT7511I To complete the rollback, run
%LCF_BINDIR%\\..\\TME\\ITM
Upgrade\\ITMUpgradeManager
AMXUT7504E The agent was not installed.
\\setup on the endpoint to uninstall the
Explanation: The agent was not installed because the Windows Server Monitoring agent
bundle was not unpacked. manually.
Operator response: Verify that the target file system Explanation: No additional information is available
has the required available space to install the agent and for this message.
try the installation again.

Appendix E. Understanding informational, warning, and error messages 139

AMXUT7512E • AMXUT7520W

2. Verify that the connectivity to the endpoint is

AMXUT7512E The agent was not uninstalled
working and try again.
correctly.
3. Verify that there is enough disk space on the
Explanation: The uninstallation engine returned a
endpoint in the LCF directory to copy the installation
non-zero value.
image.
Operator response: Review the agent installation log
4. See the lcfd.log on the endpoint for additional
and the lcfd.log on the endpoint for more information.
details.
On Windows, the installation log is located under
installDir/Install/Abort IBM Tivoli Monitoring 5. If the above suggestions do not resolve the problem,
timeStamp.log. On UNIX, the log is located under contact IBM Software Support.
installDir/logs/candle_installation.log. To manually
uninstall the operating system agent:
AMXUT7516I The operating system agent is already
For UNIX, run . installed.
$LCF_BINDIR/../TME/ITMUpgrade/ITM Explanation: No additional information is available
UpgradeManager/uninstall.sh for this message.
For Windows, run
AMXUT7517E The agent was not uninstalled.
%LCF_BINDIR%\\..\\TME\\ITM Upgrade\\ITM
UpgradeManager\\setup. Explanation: The software cannot create or read silent
uninstall file.
AMXUT7513E The agent was not uninstalled Operator response: Manually uninstall the operating
correctly. system agent.
Explanation: An error occurred when attempting the For UNIX, run
downcall.
$LCF_BINDIR/../TME/ITM Upgrade/
Operator response: Uninstall the operating system ITMUpgradeManager/uninstall.sh
agent manually.
For Windows, run
For UNIX, run $LCF_BINDIR/../TME/ITM
Upgrade/ITMUpgradeManager/uninstall.sh %LCF_BINDIR%\\..\\TME\\ITM Upgrade\\
ITMUpgradeManager\\setup.exe
For Windows run %LCF_BINDIR%\\..\\TME\\ITM
Upgrade\\ITMUpgradeManager\\setup
AMXUT7518E A custom script was not upgraded on
one or more agents.
AMXUT7514E The agent was not uninstalled.
Explanation: An error occurred during an attempt to
Explanation: Registry files deploy the script.
$CANDLE_HOME/registry/ux*.ver do not exist.
Operator response: Contact IBM Software Support.
Operator response: Uninstall the operating system
agent manually.
AMXUT7519I There are no upgrade endpoints
For UNIX, run $LCF_BINDIR/../TME/ITM running the specified script.
Upgrade/ITMUpgradeManager/uninstall.sh
Explanation: No additional information is available
For Windows, run %LCF_BINDIR%\\..\\TME\\ITM for this message.
Upgrade\\ITMUpgradeManager\\setup.exe
AMXUT7520W One or more endpoints did not
AMXUT7515E The agent was not installed. upgrade the specified script. Verify each
endpoint subscriber of the profile is
Explanation: An error occurred during an attempt to
correct and available before running the
downcall.
command again.
Operator response: There are several causes for this
Explanation: No additional information is available
error:
for this message.
1. Verify that you have installed the OS Agent support
for the platform INTERP where you are trying to
deploy this agent. Linux and UNIX support are
distributed as patches to the base Upgrade Tools
installable image.

140 IBM Tivoli Monitoring: Problem Determination Guide

 AMXUT7521E • AMXUT7530E

AMXUT7521E The operating system agent was not AMXUT7527E The custom monitor was not
created. upgraded.
Explanation: The specified endpoint for the operating Explanation: An implementation does not exist for the
system agent was not found. target Tivoli endpoint platform.
Operator response: Specify a correct endpoint name in Operator response: Add support in the monitor
the infrastructure file. definition in CSL (Custom Script Language) for the
target platform and try upgrading the custom monitor
The default is
again.
$DBDIR/$AVA/shared/analyze/scans/<tmroid>.xml.
The default is defined in the source attribute of the
AMXUT7528E The custom monitor was not
operating system agent element.
upgraded.
The endpoint format is Endpoint: <name>
Explanation: The metadata file dm37x.mdl was not
where <name> specifies a correct endpoint name. refreshed.
Operator response: Run the kumpcon command with
AMXUT7522E The endpoint program was not the dm37x.mdl file on the agent.
started.
On Windows systems, change to the
Explanation: The current user cannot start the %INSTALL%\\TMAITM6 directory and run the
endpoint program. following command:
Operator response: Verify that the correct user kumpcon REFRESH %INSTALL%\\TMAITM6\\
mappings are in place so that the user can run metafiles\\dm37x\\dm37x.mdl,
endpoint programs on the specified endpoint.
where:
%INSTALL% Specifies the path name of the IBM Tivoli
AMXUT7523E The agent cannot be installed.
Monitoring 6.1 installation.
Explanation: The endpoint cache does not have
On UNIX systems, change to
enough space for the agent install bundle.
$INSTALL/$PLATFORM/um/bin and run the
Operator response: Increase the endpoint cache to 250 following command:
MB so you can install the agent install bundle. From
kumpcon REFRESH $INSTALL/$PLATFORM/
the Tivoli management region, run the following
um/metafiles/dm37x/dm37x.mdl,
command:
where:
wep $ep set_config cache_limit=250000000
$INSTALL Specifies the path of the IBM Tivoli
Monitoring 6.1 installation.
AMXUT7524W Windows NT is not supported. Use
the Windows 2000 monitoring family. $PLATFORM Specifies the platform identifier of the
agent.
Explanation: No additional information is available
for this message.
AMXUT7529E The environment settings were not
mined.
AMXUT7525E The custom script was not deployed.
Explanation: An environment file was not created in
Explanation: The Universal Agent work path or
$DBDIR/AMX/data/environments.
metafile was not determined.
Operator response: Verify that the user running the
Operator response: Verify that CANDLE_HOME is
specified command has access to the
defined in the environment settings and restart the IBM
$DBDIR/AMX/data/environments directory and try
Tivoli endpoint.
the operation again.

AMXUT7526E The custom script was not deployed.

AMXUT7530E The custom script was not removed.
Explanation: A file was not copied to the Universal
Explanation: The Universal Agent work path or
Agent work path or metafile path.
metafile path was not determined.
Operator response: Verify that the Universal Agent
Operator response: Remove the script manually from
work path and metafile path exist and that write
the $KUMP_META_PATH/dm37x/dm37x.mdl file and
permission exists for the root user.
run the kumpcon command to refresh.

Appendix E. Understanding informational, warning, and error messages 141

AMXUT7531E • AMXUT7545I

AMXUT7531E Event forwarding was not set for the AMXUT7536W A parameter passed to the current
situation. custom script ends with a back slash (\).
The value of the parameter is PARAM.
Explanation: An error occurred when attempting the
The back slash character is replaced
downcall.
with a forward slash (/).
Operator response: Manually edit the files
Explanation: No additional information is available
tecserver.txt for the specified Tivoli Enterprise Console
for this message.
server and om_tec.config for event forwarding
enablement. The files reside on the Tivoli Enterprise
Monitoring Server in AMXUT7537E The agent was not stopped.
%CANDLE_HOME%\\CMS\\TECLIB\\ on Windows
Explanation: An error occurred with the kinconfg
and in
utility on Windows or the CandleAgent utility on
$CANDLE_HOME/$PLATFORM/tables/TECLIB/ on
UNIX.
UNIX.
Operator response: Refer to the log files in
%CANDLE_HOME%\\install on Windows or
AMXUT7532E Event forwarding was not set for the
$CANDLEHOME/logs on UNIX for details. Contact
situation.
IBM Software Support if you cannot resolve the error.
Explanation: Registry files
$CANDLE_HOME/registry/ms*.ver do not exist.
AMXUT7538E Unable to determine the available
Operator response: Manually edit the files amout of free space on the device
tecserver.txt for the Tivoli Enterprise Console server ITM6.1 will be installed on.
specification and om_tec.config for event forwarding
Explanation: The specified install dir in the baseline
enablement. The files reside on the Tivoli Enterprise
file is not able to be checked for freespace.
Monitoring Server in
%CANDLE_HOME%\\CMS\\TECLIB\\ on Windows Operator response: Verify that df may be run on Unix
and $CANDLE_HOME/$PLATFORM/tables/TECLIB/ or ntfsinfo on Windows.
on UNIX.
AMXUT7539E The amount of free space in the
AMXUT7533E Event forwarding was not set for the $LCF_BINDIR is in adequate for install.
situation.
Explanation: The agent images are copied to the
Explanation: The TECconfig file does not exist or $LCF_BINDIR before install and there is not enough
cannot be opened. free space to copy these images.
Operator response: Verify that the target file system Operator response: The documentation specifies the
has the required available space and that you have amount of free space needed for each agent.
write permission before attempting to enable event
forwarding.
AMXUT7540E The amount of free space in the
specified install dir is in adequate for
AMXUT7534I Event forwarding was set for the install.
situation. Restart the Tivoli Enterprise
Monitoring Server to activate the Explanation: There is not enough free space on the
changes. specified install dir to run the install.

Explanation: No additional information is available Operator response: The documentation specifies the
for this message. amount of free space needed for each agent.

AMXUT7535W Event forwarding was not set up for AMXUT7545I During an attempt to rollback agents
the situation since a Tivoli Enterprise on an endpoint, the upgrade tool has
Monitoring Server endpoint was not determined either the agents have
defined in the infrastructure file. already been uninstalled or the agents
were not previously installed. Therefore,
Explanation: No additional information is available the tool will not attempt to uninstall the
for this message. agents.
Explanation: No additional information is available
for this message.

142 IBM Tivoli Monitoring: Problem Determination Guide

 AMXUT7550W • KDY0001E

AMXUT7550W The value PARAM for the encoding ECO3202I rules impacted by outside operator:
attribute is incorrect. UTF-8 is used as
Explanation: No additional information is available
the default.
for this message.
Explanation: No additional information is available
for this message.
ECO3205E The software cannot execute the
specified command.
AMXUT7551W The deployed agent for the host
Explanation: The utility cannot run without the
PARAM did not connect to its
required missing arguments.
corresponding Management Server. This
could happen if the wrong network Operator response: Provide the required arguments
protocol was specified in the Baseline and try again.
file, or because of the presence of
network firewalls.
ECO3206E The command did not run because the
Explanation: No additional information is available incorrect argument incorrect_argument
for this message. was provided.
Explanation: The utility requires correct arguments.
AMXUT7554E The Universal Agent was not
uninstalled. Operator response: Verify the correct arguments and
try the operation again.
Explanation: Registry files
$CANDLE_HOME/registry/um*.ver do not exist. The
agent may have been uninstalled previuosly or was ECO3207I rule check utility version version_number
never installed. Explanation: No additional information is available
Operator response: If the Universal Agent was not for this message.
already uninstalled, uninstall it manually.
For UNIX, run $LCF_BINDIR/../TME/ITM ECO3208E The output file OUTPUT_NAMEwas not
Upgrade/ITMUpgradeManager/uninstall.sh created.

For Windows, run %LCF_BINDIR%\\..\\TME\\ITM Explanation: The directory specified to save the file in
Upgrade\\ITMUpgradeManager\\setup.exe does not exist and was not created because you do not
have permission to write to the directory.

AMXUT7565W Event forwarding was not set up for Operator response: Verify that you have permissions
the situation since the hub_installDir to write to the specified directory and try creating the
was not defined in the infrastructure file again.
file.
Explanation: No additional information is available ECO3209I baroc_file_name has the following classes
for this message. with multiple inheritance:
Explanation: No additional information is available
AMXUT7700I The result of the command is stored in for this message.
the following files:
Explanation: No additional information is available ECO3210I invalid classes and attributes:
for this message. Explanation: No additional information is available
for this message.
ECO3200I rules impacted by class:
Explanation: No additional information is available KDY0001E The maximum number of concurrent
for this message. deployment requests was exceeded.
Explanation: The server only allows the number of
ECO3201I no rule impacted. concurrent deployment requests configured in
KBBENV.
Explanation: No additional information is available
for this message. Operator response: Try deployment request again
later after other requests have completed.

Appendix E. Understanding informational, warning, and error messages 143

KDY0002E • KDY0013E

KDY0002E A Tivoli Enterprise Management Server KDY0008E The file file was not transferred to target
error occurred while trying to complete from cms.
the deployment request.
Explanation: A file on the agent bundle depot was not
Explanation: The Tivoli Enterprise Management read because the file was not written to the target or
Server is not operational or not configured properly. there was a communication problem with the target
system.
Administrator Response: Check the Tivoli Enterprise
Management Server log for more details. Verify that the Operator response: Check the Tivoli Enterprise
server is operational and configured properly. Management Server log for more details. Verify the
agent bundle depot installation and communication
with the target system.
KDY0003E The agent bundleproduct is already
deployed to target.
KDY0009E The agent bundle product does not
Explanation: An agent bundle cannot be deployed if it
support the operating system version of
is already deployed.
target.
Operator response: Specify another target or uninstall
Explanation: The specified agent bundle was not
the agent bundle and try again.
deployed because it is not supported on the target or
the correct agent bundle was not installed on the agent
KDY0004E The agent bundleproduct is missing the bundle depot.
prerequisite prereq which is not in the
Administrator Response: Verify that the correct agent
agent bundle depot on cms.
bundle was installed on the agent bundle depot.
Explanation: The prerequisite agent bundle is not
present in the agent bundle depot.
KDY0010E The agent bundle product was not found
Administrator Response: Check the Tivoli Enterprise in the agent bundle depot on cms.
Management Server log for more details. Verify that the
Explanation: The agent bundle specified for
prerequisite is available in the agent bundle depot. Try
deployment is not installed on the agent bundle depot
installing the prerequisite separately.
for the target operating system.
Administrator Response: Install the agent bundle on
KDY0005E The agent bundle product is missing the
the agent bundle depot.
prerequisite prereq which was not be
installed on target.
KDY0011E The agent bundle product is not installed
Explanation: An error occurred during an attempt to
on target.
install the specified prerequisite.
Explanation: The agent bundle was not uninstalled
Administrator Response: Check the Tivoli Enterprise
because it was not installed.
Management Server log for more details. Try installing
the prerequisite separately. Operator response: Specify an agent bundle that is
installed on the target system or specify a different
target.
KDY0006E The agent bundle product does not have
the prerequisiteprereq that was not
installed on target. KDY0012E The target target is incorrect or is offline.
Explanation: Automatic prerequisite installation was Explanation: The command did not complete because
disabled by the user. the value for the target is incorrect or the target is
offline.
Operator response: Enable automatic prerequisite
installation and try again. Operator response: Check the Tivoli Enterprise
Management Server log for more details. Specify a
correct value for the target or make sure all agents are
KDY0007E The agent bundle product has a missing
online and try the operation again.
prerequisite prereq.
Explanation: The prerequisite agent bundle was not
KDY0013E The version version of the agent bundle
automatically installed because it requires configuration
product was not found in the agent
which cannot be performed automatically.
bundle depot on cms.
Operator response: Install the prerequisite separately.
Explanation: The agent bundle specified for
deployment is not installed on the agent bundle depot
for the target operating system.

144 IBM Tivoli Monitoring: Problem Determination Guide

 KDY0014E • KDY1012E

Administrator Response: Verify that the version of the product code and the default translator was also not
agent bundle specified is correct and install the it on found.
the agent bundle depot.
Operator response: Call IBM Support.

KDY0014E A timeout occurred while waiting for an

KDY1008E The agent action action failed for
agent task to complete on system.
product code productCode. The return
Explanation: The agent task did not complete within code returnCode was received for the
the configured time out period. command command .
Administrator Response: Verify that the target system Explanation: The specified return code was received
is online. Increase the time out value and try the from the two way translator.
operation again.
Operator response: Call IBM Support.

KDY1001E The agent received incorrect SQL.

KDY1009E The agent action action failed for the
Explanation: The COMMAND column is a required product code productCode. The command
parameter and was not specified. command did not start.
Operator response: Call IBM Support. Explanation: The new process for the two-way
translator did not start.
KDY1002E The agent received incorrect SQL. Operator response: Call IBM Support.
Explanation: The TRANSID column was not specified
and is a required parameter. KDY1010E The agent deployment action failed.
Operator response: Call IBM Support. Explanation: An agent depot directory was not
specified for the agent.
KDY1003E The agent received incorrect SQL. Administrator Response: Ensure that the
AGENTDEPOT value is set to a correct directory within
Explanation: The PRODUCT column was not
the Windows/Unix/Linux agent configuration files.
specified and is a required parameter.
Operator response: Call IBM Support.
KDY1011E Configuration for the Universal Agent
was not set. The tag tag was not found
KDY1004E The agent received incorrect SQL. in the configuration file configFile.
Explanation: The CONTEXT column was not specified Explanation: The specified tag for the universal agent
and is a required parameter. metafile directory was not found in the specified
configuration file.
Operator response: Call IBM Support.
Administrator Response: Create the metafile directory
tag within the specified configuration file and verify
KDY1005E The agent received incorrect SQL. that it points to the directory where universal agent
Explanation: The TARGETMSN column was not metafiles are stored.
specified and is a required parameter.
Operator response: Call IBM Support. KDY1012E The configuration for Universal Agent
was not set. The tag tag was not found
in configuration file configFile.
KDY1006E The agent received incorrect SQL. The
agent does not support the command Explanation: The specified tag for the universal agent
command. work directory was not found in the specified
configuration file.
Explanation: Tthe agent does not support the
specified command. Administrator Response: Create the work directory
tag within the specified configuration file and verify
Operator response: Call IBM Support. that it points to the directory where universal agent
work files are stored. The default storage location of
KDY1007E Agent action action failed for product the universal agent work files is
code productCode. $CANDLEHOME/TMAITM6/work.

Explanation: The agent action failed because the

two-way translator was not found for the specified

Appendix E. Understanding informational, warning, and error messages 145

KDY1013E • KDY1023E

KDY1013E The configuration for universal agent KDY1018E The command command did not start
was not set. The tag tag was not found when configuring the universal agent.
in configuration file configFile.
Explanation: A new process for the kumpcon
Explanation: The specified tag for the universal agent command to import the mdl file was not started.
resource bundle directory was not found in the
Operator response: Call IBM Support.
specified configuration file.
Administrator Response: Create the resource bundle
KDY1019E The deployment operation failed
directory tag within the specified configuration file and
because the product code prodcode is not
verify that it points to the directory where the universal
installed on this endpoint.
agent resource bundle files are stored. The default
storage location of the universal agent resource bundle Explanation: The specified product was not found on
files is $CANDLEHOME/TMAITM6/rb. the endpoint.
Administrator Response: Install the specified product
KDY1014E The MDL file mdlfile as not copied to on the endpoint and try the deployment operation
universal agent metafile directory again.
metafiledir.
Explanation: The MDL file was not copied from the KDY1020E The universal agent was not configured
depot directory to the metafile directory because because the file configFile for the
permission or enough disk space to copy the file does instance instance was not found.
not exist.
Explanation: The universal agent configuration file for
Administrator Response: Verify that the metafile the specified instance was not found.
directory has the correct permissions and that there is
enough disk space to create the MDL file in the Administrator Response: Verify that the specified
metafile directory. universal agent instance exists on the target agent, that
the configuration file exists for this instance, and that
you have permission to access the configuration file.
KDY1015E The script file scriptfile was not copied to
the universal agent scripts directory
scriptsfiledir. KDY1021E The universal agent was not configured
because the work directory workdir by
Explanation: The file was not copied from the depot the tag tag in the configuration file
directory to the scripts directory because permission or configfile is not correct.
enough disk space to copy the file does not exist.
Explanation: The specified tag for the universal agent
Administrator Response: Verify that the scripts work directory is incorrect because it does not include
directory has the correct permissions and that there is directory separators.
enough disk space to create the MDL file in the meta
files directory. Administrator Response: Verify that the specified
work directory tag points to the directory where
universal agent work files are stored. The default
KDY1016E The MDL file mdlfile was not imported. location of the work files is
$CANDLEHOME/TMAITM6/work.
Explanation: The universal agent kumpcon command
delivered a return code during an attempt to import
the MDL file. KDY1022E The command command did not start
when configuring the universal agent.
Administrator Response: Correct the MDL file on a
universal agent and import the MDL file manually Explanation: A new process for the kumpcon
using kumpcon or um_console. If the MDL file fails to command to get the dp type did not start.
import, call IBM Support.
Operator response: Call IBM Support.

KDY1017E The command command did not start

when configuring the universal agent. KDY1023E The universal agent was not configured
with the MDL filemdlfile.
Explanation: A new process for the kumpcon
command to delete the mdl file was not started. Explanation: The data provider type was not
determined from the specified MDL file.
Operator response: Call IBM Support.
Administrator Response: Verify that the MDL file
includes the correct data provider SOURCE statement
and try the configuration again.

146 IBM Tivoli Monitoring: Problem Determination Guide

 KDY1024E • KFAIT0001E

KDY1024E The command command did not start or KDY1030E The agent was not installed because the
stop agent. command command did not start.
Explanation: The command returned a return code. Explanation: A new process for the specified
command did not start.
Operator response: Call IBM Support.
Operator response: Call IBM Support.
KDY1025E The command command to start or stop
the agent did not complete. KDY1031E The agent installation command
installcmdreturned a the return code
Explanation: A new process for the specified
returncode .
command did start.
Explanation: The agent was not installed because
Operator response: Call IBM Support.
there is not enough disk space on the server or you do
not have permission to install the agent.
KDY1026E The software is configuring the
Administrator Response: After verifying that there is
universal agent instance instance.
enough disk space and that you have permission to
Explanation: Universal agent instance failed to start. install the agent, check the installation log files and call
IBM Support.
Administrator Response: Start the agent instance
manually. Call IBM Support if you cannot start the
agent instance manually. KDY1032E The agent uninstall command
installcmdreturned the returncode return
code.
KDY1027E Configuring universal agent instance (
optional ) instance. Explanation: The agent was not uninstalled.
Explanation: Universal agent instance failed to stop. Administrator Response: Refer the uninstall log files
for details and call IBM Support.
Administrator Response: Stop the agent instance
manually. Call IBM Support if you cannot manually
stop the agent instance manually.. KDY1033E The agent was not uninstalled because
the command command did not start.
KDY1028E The universal agent was not updated Explanation: A new process for the specified
because the configuration file configFile command did not start.
does not include the startup parameters
Operator response: Call IBM Support.
startupParms.
Explanation: The universal agent was not updated
KDY1034E The architecture for product code
because the disk does not have enough space for the
productCode was not found.
update, access to the configuration file was denied, or
the format of the specified configuration file is Explanation: The product represented by the specified
incorrect. product code was not installed.
Administrator Response: After verifying that there is Operator response: Verify that the product
enough disk space to create another copy of the represented by the specified product code is installed
configuration file and that permission to save the file and call IBM Support.
exists, call IBM Support.
KFAIT0001E An non-numeric value was specified for
KDY1029E The agent received incorrect SQL the configuration parameter
because the VERSION column was not parameter_name . The value specified was
specified. parameter_value. The default value for the
parameter is used.
Explanation: The VERSION is a required parameter to
upgrade the agent. Explanation: Configuration parameters must be
specified only with numeric values.
Operator response: Call IBM Support.
Administrator Response: Correct the value for the
parameter in the configuration file and restart the
situation update forwarder to use the non-default
value.

Appendix E. Understanding informational, warning, and error messages 147

KFAIT0002E • KFAIT0013E

KFAIT0002E The lineline specified in the KFAIT0008E The error exception_message occurred.
configuration file file_name is incorrect.
Explanation: The running file was not created because
Explanation: The parameter in the specified the specified error occurred.
configuration file was specified in the incorrect format.
Administrator Response: Consult the log file
Administrator Response: Specify the correct format synch_trace.log for the error details. Make any required
for this value in the situation event configuration file. changes indicated by the log file and try to create the
running file again.
KFAIT0003E The exception_messageerror message was
received while the software attempted to KFAIT0009E The exception message exception_message
read the configuration data from occurred.
file_name.
Explanation: An error was received while attempting
Explanation: The error occurred while the software to create the stop file. The situation update forwarder
attempted to parse the specified configuration file. cannot be stopped without creating the stop file.
Administrator Response: Refer to the log file for Administrator Response: Consult the log file
details about the error. synch_trace.log for the error. Make any required
changes indicated by the log file and try to create the
stop file again.
KFAIT0004E The error exception_message occurred
while closing the configuration file.
KFAIT0010E The error message exception_message
Explanation: See message.
occurred.
Administrator Response: Consult the log file for the
Explanation: The specified error was received while
error.
attempting to close the cache file. Information about the
location of processing in the cache file cannot be
KFAIT0005E The cache_path cache file directory does persisted.
not exist. The situation update
Administrator Response: Consult the log file for error
forwarder cannot be started.
details before attempting to close the cache file again.
Explanation: The cache file does not exist or the
specified path to the file is incorrect.
KFAIT0011E The error message exception_message
Administrator Response: Create the cache file occurred when trying to delete the
directory or specify a different path to the cache file cache_file cache file.
directory, and restart the situation update forwarder.
Explanation: An error occured wrhile attempting to
delete the cache file.
KFAIT0006E The password file for the Tivoli
Administrator Response: Consult the log file
Enterprise Monitoring Server
synch_trace.log for details before attempting to delete
server_name does not exist.
the cache file again.
Explanation: A password is not used.
Administrator Response: Run the following command KFAIT0012E The exception_message error occurred
to generate the password file and then restart the while attempting to send the
SituationUpdateForwarder program: event_update event update to the Tivoli
Enterprise Monitoring Server.
$BINDIR/TME/TEC/OM_TEC/bin/sitconfsvruser.sh
update serverid=svrid_value userid=userid_value Explanation: The Tivoli Enterprise Monitoring Server
password=password_value did not receive the specified event update.
Administrator Response: Consult the log file
KFAIT0007E The exception_message error message was synch_trace.log for the error.
received while attempting to delete the
stop file.
KFAIT0013E The error_message logon error occurred
Explanation: The stop file was not deleted. while sending an event update to the
Tivoli Enterprise Monitoring Server.
Administrator Response: Refer the log file
synch_trace.log for error detail and try to delete the Explanation: The situation update forwarder did not
stop file again. process an event update.
Administrator Response: Verify the configured user

148 IBM Tivoli Monitoring: Problem Determination Guide

 KFAIT0014E • KFAIT0026I

name and password for the Tivoli Enterprise

KFAIT0020I The exception_message error occurred
Monitoring Server and try the operation again.
while parsing the event event.
Explanation: No additional information is available
KFAIT0014E The error message error_messageoccurred.
for this message.
The situation update forwarder was
unable to process an event update.
KFAIT0021I An error exception_message occurred
Explanation: A fatal XML parsing error occurred
while reading the cache file cache_file.
during an attempt to send an event update to the Tivoli
Enterprise Monitoring Server. Explanation: No additional information is available
for this message.
Administrator Response: Restart the
SituationUpdateForwarder program and verify the
connection with the destination Tivoli Enterprise KFAIT0022I The exception_message error occurred
Monitoring Server while closing the cache file cache_file.
Explanation: No additional information is available
KFAIT0015I The error_messageerror occurred during for this message.
an attempt to send an event update to
the Tivoli Enterprise Monitoring Server.
KFAIT0023E The Tivoli Enterprise Monitoring Server
Explanation: No additional information is available is not available to process event
for this message. updates.
Explanation: The Tivoli Enterprise Monitoring Server
KFAIT0016E The exception_message error occurred is unavailable because either the network or server is
while processing the event event update down.
response from the Tivoli Enterprise
Administrator Response: Start the Tivoli Enterprise
Monitoring Server.
Monitoring Server web services.
Explanation: The event update did not complete
because the response from the Tivoli Enterprise
KFAIT0024E The error exception_message occurred
Monitoring Server was not processed. The event is
while sending an event update to the
considered to be sent.
Tivoli Enterprise Monitoring Server.
Administrator Response:
Explanation: The Tivoli Enterprise Monitoring Server
is unavailable because either the network or server is
KFAIT0017E The exception_message error occurred down or the Tivoli Enterprise Monitoring Server host in
while processing a SOAP document the SOAP URL was not configured correctly. Attempt to
from the Tivoli Enterprise Monitoring connect to the Tivoli Enterprise Monitoring Server will
Server. continue.
Explanation: This error occurred because there was an Administrator Response: Verify that the network or
error instantiating the SOAPDocument which indicates server is up and that the Tivoli Enterprise Monitoring
an environmental error that must be corrected. Server host in the SOAP URL was configured correctly.
Administrator Response: Restart the
SituationUpdateForwarder program and verify the KFAIT0025I The exception_messageerror occurred
connection with the destination Tivoli Enterprise while renaming the cache file cache_file .
Monitoring Server.
Explanation: No additional information is available
for this message.
KFAIT0018I The exception_message error occurred
while processing a cache file.
KFAIT0026I The exception_message error occurred
Explanation: No additional information is available while opening the last processed cache
for this message. file.
Explanation: No additional information is available
KFAIT0019I The event event is not in the correct for this message.
format and will be ignored.
Explanation: No additional information is available
for this message.

Appendix E. Understanding informational, warning, and error messages 149

KFAIT0027I • KFAIT0037E

KFAIT0027I The exception_message error was received KFAIT0034E Access is denied because an incorrect
while opening the cache file cache_file. user name or password was provided.
Explanation: No additional information is available Explanation: The user name and password supplied
for this message. are not correct or the user does not have authority to
access the file.
KFAIT0028I The exception_message error occurred Administrator Response: Verify the correct user name
while getting the oldest cache file. and password, ensuring correct spelling. Also verify
that caps lock is turned off. If you verified that you
Explanation: No additional information is available
supplied the correct user name and password, contact
for this message.
your Tivoli Enterprise Console Administrator.

KFAIT0029I The exception_message error occurred

KFAIT0034E The error message exception_message
while calculating the CRC value of the
occurred while generating the
cache file.
TEC_ITM_OM_Situation_Sync_Error
Explanation: No additional information is available event for server.
for this message.
Explanation: See message.
Administrator Response: The Tivoli Enterprise
KFAIT0030W The situation update forwarder failed
Monitoring Server cannot be contacted. Verify that it is
to send an event update over a secure
running to ensure synchronization.
HTTPS connection. A non-secure HTTP
connection will be used.
KFAIT0035E Access is denied because an incorrect
Explanation: No additional information is available
user name or password was provided.
for this message.
Explanation: he user name and password supplied are
not correct or the user does not have authority to
KFAIT0031E The exception_message error occurred
access the file.
while initializing the SOAP connection.
Administrator Response: Verify the correct user name
Explanation: The SOAP connection with the
and password, ensuring correct spelling. Also verify
destination Tivoli Enterprise Monitoring Server was not
that caps lock is turned off. If you verified that you
established.
supplied the correct user name and password, contact
Administrator Response: Verify the connection with your Tivoli Enterprise Console Administrator.
the destination Tivoli Enterprise Monitoring Server and
restart the SituationUpdateForwarder program.
KFAIT0036E Communication Failure
Explanation: [DEV: what entities failed to
KFAIT0032I The exception_messageerror occurred
communicate? What operation was the user attempting
during an attempt to update the running
when this error occurred?]
file. Consult the log file synch_trace.log
for error details. Administrator Response: Verify the correct host name
and port number of the Tivoli Enterprise Console
Explanation: No additional information is available
server. Also verify that remote login is allowed by the
for this message.
destination oserv. Consult the log file for the exception.
If required, please contact your Tivoli Enterprise
KFAIT0033E The error message exception_message Console Administrator.
occurred because the server
configuration file file does not exist.
KFAIT0037E The event group associated with this
Explanation: The specified configuration file was not viewer no longer exists.
found and is required.
Explanation: [DEV: what operation was the user
Administrator Response: Configure the user name attempting when this error occurred? What is the name
and password for the destination Tivoli Enterprise of the device or component in which the error
Monitoring Server using the sitconfsvruser.sh script. occurred?]
Then restart the SituationUpdateForwarder program.
Administrator Response: Contact your Tivoli
Enterprise Console Administrator to recreate the event
group and to verify that you have authority to access
the specified console.

150 IBM Tivoli Monitoring: Problem Determination Guide

 KFAIT0101E • KFWITM010I

KFAIT0101E The configuration file file_name does not KFWITM002W Attribute definitions are not
exist. available: query cannot be edited.
Explanation: The specified configuration file does not Explanation: No additional information is available
exist. for this message.
Administrator Response: Use the add option to create
the file . KFWITM003I No items were found for the selected
group.
KFAIT0102E The directory dir_name was not created. Explanation: No additional information is available
for this message.
Explanation: The specified directory was not created.
Administrator Response: Check the permissions.
KFWITM004W No attributes were found. Situations
and queries cannot be created at this
KFAIT0103I The file file_name already exists. The level.
new file was named new_file_name.
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KFWITM005W Selection is limited to VALUE_0
KFAIT0104E The entry for server server_id already additional items.
exists in the configuration file.
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KFWITM006I Validating user credentials.
KFAIT0105I The entry for server_id was created
Explanation: No additional information is available
successfully.
for this message.
Explanation: No additional information is available
for this message.
KFWITM007W The Tivoli Enterprise Portal Server
has lost contact with the Tivoli
KFAIT0106E The entry for server server_id does not Enterprise Management Server, and is
exist in the configuration file. attempting to reconnect.
Explanation: See message. Explanation: No additional information is available
for this message.
Administrator Response:

KFWITM008W The Tivoli Enterprise Portal Server

KFAIT0107I The entry for server_id was updated has lost contact with the TEMS.
successfully.
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.

KFWITM009I The Tivoli Enterprise Portal Server is

KFAIT0108I The entry for server_id was deleted still being initialized and
successfully. is not ready for communications.
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KFWITM001W Unable to connect to Tivoli KFWITM010I Tivoli Enterprise Portal Server not
Enterprise Portal Server. ready.
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

Appendix E. Understanding informational, warning, and error messages 151

KFWITM011E • KFWITM027E

KFWITM011E No latitude or longitude at this KFWITM019W Managed System List: VALUE_0 is

location empty, it will be deleted. Select Yes to
delete or No to change.
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KFWITM012I Latitude = VALUE_0 degrees,
Longitude = VALUE_1 degrees KFWITM020E The name specified for the situation
is incorrect.
Explanation: No additional information is available
for this message. Explanation: The following list describes the naming
convention for correct situation names:
KFWITM013W The expiration time for this 1. The situation name must include 31 characters or
acknowledgment has passed. A new less.
acknowledgement will be created. 2. The situation name must begin with an alphabetic
Press " Yes " to create the new character (a-z, A-Z).
Acknowledgement or " No " to cancel 3. The situation name can contain any alphabetic,
the request. numeric (0-9) or underscore (_) character.
Explanation: No additional information is available 4. The situation name must end with an alphabetic or
for this message. numeric character.
Operator response: Specify a valid situation name and
KFWITM014W This acknowledgment will expire try the operation again.
within VALUE_0 minutes.
Press " Yes " to create the new
KFWITM021E The Situation Formula is empty
Acknowledgement or " No " to change
the expiration time or interval. Explanation: No additional information is available
for this message.
Explanation: No additional information is available
for this message.
KFWITM023W Incorrect or unknown attribute
referenced in action text:
KFWITM015E The acknowledgement expiration
time cannot be in the past. Explanation: No additional information is available
for this message.
Explanation: No additional information is available
for this message.
KFWITM024I VALUE_0 Navigator update pending
KFWITM016E The event is closed and can no longer Explanation: No additional information is available
be acknowledged. for this message.
Explanation: No additional information is available
for this message. KFWITM025I VALUE_0 Navigator updates pending
Explanation: No additional information is available
KFWITM017I Please wait while Acknowledgement for this message.
data is retrieved.
Explanation: No additional information is available KFWITM026W Apply pending updates
for this message.
Explanation: No additional information is available
for this message.
KFWITM018W The Managed System List Definition
was changed. Do you want to save the
changes? KFWITM027E The managed system list VALUE_0
already exists. Type another managed
Explanation: No additional information is available system list.
for this message.
Explanation: No additional information is available
for this message.

152 IBM Tivoli Monitoring: Problem Determination Guide

 KFWITM028W • KFWITM044E

KFWITM028W Are you sure you want to delete this KFWITM036W The situation you are editing was
query? changed. Would you like to save those
Warning: This will affect any changes?
workspaces that use this query.
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KFWITM037W User information has changed, do
KFWITM029E The query definition is incorrect and you want to save the changes?
cannot be saved.
Explanation: No additional information is available
Explanation: You are trying to save a query definition for this message.
that is not correct.
Operator response: Verify the correct query definitions KFWITM038E User ID cannot have leading or
and try the operation again. imbedded blanks.
Explanation: No additional information is available
KFWITM030E The specified SQL statement is not for this message.
supported by the Tivoli Enterprise
Portal.
KFWITM039E User ID already exists, try another
Only SELECT statements are supported.
Explanation: No additional information is available
Explanation: No additional information is available
for this message.
for this message.

KFWITM040I Please wait while User Information is

KFWITM031W SORT BY and GROUP BY are not
retrieved from the Server.
supported together.
Please select only one of them. Explanation: No additional information is available
for this message.
Explanation: No additional information is available
for this message.
KFWITM041E You cannot remove your own User
entry.
KFWITM032W At least one attribute has to be
selected. Explanation: No additional information is available
for this message.
Explanation: No additional information is available
for this message.
KFWITM042E You cannot remove the Default User
entry.
KFWITM033W Aggregate functions have to be used
together with GROUP BY. Explanation: No additional information is available
for this message.
Explanation: No additional information is available
for this message.
KFWITM043E The selected user ID was not found
in the user database. Specify a valid
KFWITM034W Note that use of certain advanced
user ID and try the operation again.
query options will make this query
ineligible for historical use. Explanation: No additional information is available
for this message.
Explanation: No additional information is available
for this message.
KFWITM044E The changes were not saved because
the existing record could was not found.
KFWITM035E The count for First Last function is
incorrect. Explanation: No additional information is available
Type a positive integer (1, 2, 3...). for this message.
Explanation: No additional information is available
for this message.

Appendix E. Understanding informational, warning, and error messages 153

KFWITM045E • KFWITM061I

KFWITM045E An error occurred because the allowed KFWITM052E The Display Item Feature cannot be
applications list was empty. used with this Situation because
it includes attributes from more than
Explanation: No additional information is available
one Group: VALUE_0
for this message.
and VALUE_1 .
Explanation: No additional information is available
KFWITM046E The Display Item Feature cannot be
for this message.
used with this Situation because
no Application Attribute Group was
selected for this Situation KFWITM053I VALUE_0 is the assigned Root for
Navigator View: VALUE_1 .
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KFWITM047E The Display Item Feature cannot be
used with this Situation because KFWITM054I Retrieving Navigator View..
no attributes are eligible for use as a
Explanation: No additional information is available
Display Item
for this message.
in group: VALUE_0 .
Explanation: No additional information is available
KFWITM055I Saving Navigator View...
for this message.
Explanation: No additional information is available
for this message.
KFWITM048E The Display Item Feature cannot be
used with this Situation because
this Situation is Correlated across KFWITM056E Topology name exists. Type another
Managed Systems name name.
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KFWITM049E The situation condition contains a KFWITM057W No editable Navigator Views are
column available.
function (MIN, MAX, COUNT, AVG, Do you wish to create a new one?
SUM, etc).
Display Item selection is not allowed Explanation: No additional information is available
when the condition for this message.
contains a column function.
Explanation: No additional information is available KFWITM058W Are you sure you want to delete the
for this message. VALUE_0 Navigator VALUE_1 ?
Explanation: No additional information is available
KFWITM050E The Display Item Feature cannot be for this message.
used with this Situation because
no condition has been defined for this KFWITM059W Delete Navigator VALUE_0
Situation. Display Item
selection requires a Situation condition Explanation: No additional information is available
to be defined. for this message.

Explanation: No additional information is available

for this message. KFWITM060I Enter a name for the Navigator view
Explanation: No additional information is available
KFWITM051E The Display Item Feature cannot be for this message.
used with this Situation because
you can only use Attributes from KFWITM061I Enter a description of the Navigator
Groups that return multiple rows. view
Attribute Group VALUE_0 is not a
multi-row Group. Explanation: No additional information is available
for this message.
Explanation: No additional information is available
for this message.

154 IBM Tivoli Monitoring: Problem Determination Guide

 KFWITM062W • KFWITM080I

KFWITM062W Are you sure you want to delete KFWITM071E Collection status request for <
situation VALUE_0 ? VALUE_0 > at < VALUE_1 > failed:
VALUE_2
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KFWITM063W Are you sure you want to delete
Managed System List VALUE_0 ? KFWITM072I Determining collection status of <
* Warning * VALUE_0 > at < VALUE_1 >...
This will affect any situations or
Explanation: No additional information is available
policies that use this distribution.
for this message.
Explanation: No additional information is available
for this message.
KFWITM073I Configuring product < VALUE_0 > ...
Explanation: No additional information is available
KFWITM064I Adding permission: VALUE_0 , will
for this message.
also add the following permissions:
Explanation: No additional information is available
KFWITM074E Configuration request for < VALUE_0
for this message.
> failed: VALUE_1
Explanation: No additional information is available
KFWITM065I Removing permission: VALUE_0 , will
for this message.
also remove the following permissions:
Explanation: No additional information is available
KFWITM075I Determining collection configuration
for this message.
of < VALUE_0 > ...
Explanation: No additional information is available
KFWITM066W The launch definition you were
for this message.
editing has changed. Would you like to
save those changes?
KFWITM076I Unconfiguring product < VALUE_0 >
Explanation: No additional information is available
...
for this message.
Explanation: No additional information is available
for this message.
KFWITM067E The launch definitions name is
incorrect. It cannot be empty and must
not exceed 64 characters. KFWITM077E Unconfiguration request for <
VALUE_0 > failed: VALUE_1
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KFWITM068E The launch definitions target cannot
be empty. KFWITM078I Starting or Stopping History
Collection for product < VALUE_0 > ...
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KFWITM069E The definition you selected could not
be launched because of error: VALUE_0 . KFWITM079E Start or Stop of History Collection for
< VALUE_0 > failed: VALUE_1
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KFWITM070E There were no substitutable items
found for this item. KFWITM080I Rebuilding View...
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

Appendix E. Understanding informational, warning, and error messages 155

KFWITM081E • KFWITM099E

KFWITM081E The link target was not be found. KFWITM090E You are not authorized for this View.
The link definition might be incorrect
Explanation: No additional information is available
or the target might be transient.
for this message.
Explanation: No additional information is available
for this message.
KFWITM091E View not available at this time.
Explanation: No additional information is available
KFWITM082I Please select a leaf node from the
for this message.
tree.
Explanation: No additional information is available
KFWITM092W Are you sure you want to exit Tivoli
for this message.
Enterprise Portal?
Explanation: No additional information is available
KFWITM083W Default link is disabled for the
for this message.
selected object; please verify link and
link anchor definitions.
KFWITM093I Server Available.
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KFWITM084E Default link could not be found.
Verify link and link anchor definitions. KFWITM094W The TEP Client has lost contact with
the Tivoli Enterprise Portal Server.
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KFWITM085W Default link is not enabled here.
KFWITM095W If client is non-responsive, request
Explanation: No additional information is available
retry might be in progress.
for this message.
Explanation: No additional information is available
for this message.
KFWITM086I Please wait while Properties Panel is
loaded...
KFWITM096I Tivoli Enterprise Portal Server is
Explanation: No additional information is available
offline.
for this message.
Explanation: No additional information is available
for this message.
KFWITM087I Please wait while Query Selection
Tree is prepared...
KFWITM097W Tivoli Enterprise Portal Server is
Explanation: No additional information is available
waiting for TEMS. Refresh Now to
for this message.
update status.
Explanation: No additional information is available
KFWITM088W Additional Topology Information
for this message.
not available at this time.
The network configuration might be
changing at this time. Please try again KFWITM098I Reconnect Authorization Failed.
later
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KFWITM099E
KFWITM089W Status Display / View or Modify The user credentials originally used to
Authority Require. logon to Tivoli Enterprise Portal are no
longer valid.
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.

156 IBM Tivoli Monitoring: Problem Determination Guide

 KFWITM100W • KFWITM118I

KFWITM100W KFWITM109I Wait until VALUE_0 is False

Your Tivoli Enterprise Portal
Explanation: No additional information is available
Permissions have changed, you must
for this message.
restart the Tivoli Enterprise Portal
Client.
KFWITM110I : retrieving workflow definitions from
Explanation: No additional information is available
server.
for this message.
Explanation: No additional information is available
for this message.
KFWITM101I Select workspace link button to view
event results.
KFWITM111I : launching Workflow Editor Dialog ...
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KFWITM102I Select workspace link button to view
event results for: VALUE_0 KFWITM112I : loading panel definition.
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KFWITM103E KFWITM113I : building document controller.

Please contact your Tivoli Enterprise
Portal System Administrator. Explanation: No additional information is available
for this message.
Explanation: No additional information is available
for this message.
KFWITM114I : completing panel construction.

KFWITM104E The requested operation has failed: Explanation: No additional information is available
VALUE_0 for this message.

Explanation: No additional information is available

for this message. KFWITM115E Initialization failure
Explanation: No additional information is available
KFWITM105W Save changes to policy: VALUE_0 ? for this message.

Explanation: No additional information is available

for this message. KFWITM116W Background worker thread is still
running.
<Wait> for thread to complete and
KFWITM106W Validate changes to workflow of continue with termination or
VALUE_0 ? <Cancel> termination?
Only validated changes can be saved.
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.

KFWITM117I : workflow validation in progress

KFWITM107I Please wait while Workflow Dialog is
constructed. Explanation: No additional information is available
for this message.
Explanation: No additional information is available
for this message.
KFWITM118I : opening workflow for policy
VALUE_0
KFWITM108I Wait until VALUE_0 is True
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.

Appendix E. Understanding informational, warning, and error messages 157

KFWITM119I • KFWITM140W

KFWITM119I Opening workflow for policy KFWITM130W Delete the selected policies?
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KFWITM120E Error: unable to download workflow KFWITM131I : deleting selected policies

rules: VALUE_0
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KFWITM132I Deleting the policy
KFWITM121W Warning: Error encountered while
Explanation: No additional information is available
rendering workflow for policy
for this message.
Explanation: No additional information is available
for this message.
KFWITM133E Error: problem encountered during
deletion of policy : VALUE_0
KFWITM122E Error: unable to retrieve workflow for
Explanation: No additional information is available
policy
for this message.
Explanation: No additional information is available
for this message.
KFWITM134I Starting the policy
Explanation: No additional information is available
KFWITM123E Error: request to render workflow on
for this message.
EDT failed: VALUE_0
Explanation: No additional information is available
KFWITM135I Stopping the policy
for this message.
Explanation: No additional information is available
for this message.
KFWITM124I : validating modified workflows
Explanation: No additional information is available
KFWITM136I : sending request to server
for this message.
Explanation: No additional information is available
for this message.
KFWITM125I : committing changes to server
Explanation: No additional information is available
KFWITM137E Could not obtain distribution of
for this message.
policy VALUE_0
Explanation: No additional information is available
KFWITM126I Saving the policy
for this message.
Explanation: No additional information is available
for this message.
KFWITM138E Error: unable to start policy: VALUE_0
Explanation: No additional information is available
KFWITM127I : adding new policy
for this message.
Explanation: No additional information is available
for this message.
KFWITM139E Error: unable to stop policy: VALUE_0
Explanation: No additional information is available
KFWITM128I : copying the policy
for this message.
Explanation: No additional information is available
for this message.
KFWITM140W VALUE_0 is a new policy and must
be saved before it can be started or
KFWITM129W Delete the selected policy? stopped.
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

158 IBM Tivoli Monitoring: Problem Determination Guide

 KFWITM141I • KFWITM159I

KFWITM141I Validating workflow KFWITM151E < VALUE_0 > : < VALUE_1 > cannot
run:
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KFWITM142W Workflow must contain at least one
activity KFWITM152W multiple choice target of < VALUE_0
>
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KFWITM143E < VALUE_0 > : < VALUE_1 > :
requires one or more VALUE_2 successor KFWITM153E conflicting link types for < VALUE_0
activities. >: " VALUE_1 " cf." VALUE_2 "
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KFWITM144E VALUE_0 incorrect. A correlated KFWITM154W Empty Workflow window cannot be

policy must start with <Wait for closed.
Situation> activities. If no longer needed, please delete the
policy.
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KFWITM145E Unknown error occurred: VALUE_0
KFWITM155W No workflow has yet been validated
Explanation: No additional information is available
for this policy.
for this message.
The workflow must be validated before
the window can be closed.
KFWITM146E Validation failed for workflow
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KFWITM156E Cannot edit version < VALUE_0 >
KFWITM147E A link already exists between these 2 workflow with version < VALUE_1 >
activities. editor.

Explanation: No additional information is available Explanation: No additional information is available

for this message. for this message.

KFWITM148E An activity cannot be connected to a KFWITM157E Unable to determine activity version

predecessor activity.
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KFWITM158E Activity version exceeds TEMS
KFWITM149E < VALUE_0 > : < VALUE_1 >: requires version
resource VALUE_2
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KFWITM159I Element name can contain
KFWITM150E < VALUE_0 > : < VALUE_1 >: requires alphanumerics and underscores.
resources VALUE_2
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.

Appendix E. Understanding informational, warning, and error messages 159

KFWITM160I • KFWITM177W

KFWITM160I Element name must start with KFWITM169E Error: Can \ ’t create new instance of
alphabetic or underscore. VALUE_0 : VALUE_1
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KFWITM161I Single asterisk is valid only as an KFWITM170W A policy name must:

element placeholder. a) Start with a letter,
b) Contain only letters, numbers, and
Explanation: No additional information is available
underscores,
for this message.
c) End with a letter or number,
d) be less than 32 characters.
KFWITM162E !!! ERROR !!!
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KFWITM171E The chosen name already exists.
KFWITM163I XML tag is valid
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KFWITM172W What is the category, severity and
KFWITM164I The policy \ ’s distribution has been text of the Universal Message?
cleared because the
Explanation: No additional information is available
correlation mode has been changed to
for this message.
Logical Application;
such policies can only be distributed to
Logical Application Groups, (Managed KFWITM173W What is the action to be executed?
System Lists).
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KFWITM174W On which target must the action be
KFWITM165W Exit without saving changes? executed?
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KFWITM166E Error: incorrect value for column \ KFWITM175W Over which activity \ ’s results must
VALUE_0 \ this activity iterate?
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KFWITM167E Error: Can \ ’t save policy < VALUE_0 KFWITM176W No substitutions specified from
> : class VALUE_1 does not implement iteration activity
ObjectToPropertyInterface
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KFWITM177W Which activity \ ’s data provides the
KFWITM168E Error: Can \ ’t save policy < VALUE_0 target agent of this command?
> : VALUE_1
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.

160 IBM Tivoli Monitoring: Problem Determination Guide

 KFWITM178I • KFWITM196W

KFWITM178I Click to hide version detail KFWITM188W Do you want to save the changes
you made to VALUE_0 ?
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KFWITM179I Click to display version details
KFWITM189E Workplace Initialization Failure
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KFWITM180W Back-leveled client
KFWITM190W The Subrange you were editing has
Explanation: No additional information is available
changed. Would you like to save those
for this message.
changes?
Explanation: No additional information is available
KFWITM181W Unsupported feature: version <
for this message.
VALUE_0 >.
Explanation: No additional information is available
KFWITM191W Are you sure you want to delete this
for this message.
Subrange?
Explanation: No additional information is available
KFWITM182W Select to open workflow. Use
for this message.
Alt+Click to preserve current
split-window sizing
KFWITM192E The Subrange name you entered
Explanation: No additional information is available
exists already. Please enter a new one.
for this message.
Explanation: No additional information is available
for this message.
KFWITM183W Feature not supported by TEMS or
Editor
KFWITM193W The Subrange name can not be
Explanation: No additional information is available
empty.
for this message.
Explanation: No additional information is available
for this message.
KFWITM184I Saving Workspace...
Explanation: No additional information is available
KFWITM194E Minimum or Maximum value is
for this message.
incorrect:
1) Maximum value must be greater than
KFWITM185W This workspace has been marked as the minimum,
read-only and cannot be modified. 2) Value must be within valid integer
Do you want to create and save a new range.
workspace with your changes?
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KFWITM195W The Global Sound settings will be
KFWITM186W Are you sure you want to delete the applied
current workspace? immediately. Are you sure?
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KFWITM187W Are you sure you want to delete the KFWITM196W The sound filename is incorrect.
current workspace and restore the
Explanation: No additional information is available
original?
for this message.
Explanation: No additional information is available
for this message.

Appendix E. Understanding informational, warning, and error messages 161

KFWITM197W • KFWITM217E

KFWITM197W User has no assigned Navigator KFWITM208E Invalid Password

Views.
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KFWITM209E Authorization failed - Password
KFWITM198E Failed to create Static Analysis Tool Expired
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KFWITM199W Pattern validation failed KFWITM210W Password Expired

Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KFWITM200E Problem displaying data. Please see KFWITM211E Authorization failed - Password
trace log for details. Revoked
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KFWITM201I Do not show this message again. KFWITM212W Password Revoked

Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KFWITM202I Operation might be delayed. KFWITM213E Authorization failed - Invalid

Credentials
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KFWITM203I Loading Workplace...
KFWITM214W Invalid Credentials
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KFWITM204I Loading Workspace definition...
KFWITM215E Unable to process logon request
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KFWITM205E Authorization failed - Invalid Id
KFWITM216I Please wait while VALUE_0
Explanation: No additional information is available
definitions are retrieved from the
for this message.
Server.
Explanation: No additional information is available
KFWITM206E Invalid Id
for this message.
Explanation: No additional information is available
for this message.
KFWITM217E Property based problem.
Explanation: No additional information is available
KFWITM207E Authorization failed - Invalid
for this message.
Password
Explanation: No additional information is available
for this message.

162 IBM Tivoli Monitoring: Problem Determination Guide

 KFWITM218E • KFWITM235E

KFWITM218E Request failed during cleanup. KFWITM228W There are currently no actions for
this item.
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KFWITM219E Request failed during creation.
KFWITM229I To change workspace properties,
Explanation: No additional information is available
select a workspace view from the list at
for this message.
the left. The tree represents all the
workspace view types and the specific
KFWITM220E Request failed during execution. views associated with the current
workspace.
Explanation: No additional information is available To select a view, simply select a node in
for this message. the tree representing the specific view
you wish to
KFWITM221E Requested implementation inspect or modify.
unavailable. Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KFWITM230W Query has been deleted: VALUE_0
KFWITM222E Request was incorrect. Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KFWITM231I To select a new query, simply select
KFWITM223E Results of request are incorrect. the desired query node from the tree on
the left and press the OK button below.
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.

KFWITM224I Server unavailable.

KFWITM232W Expression syntax is not supported.
Explanation: No additional information is available Query definition is not editable.
for this message.
Explanation: No additional information is available
for this message.
KFWITM225W Results of request are not yet
available.
KFWITM233E Your user id does not have
Explanation: No additional information is available permission to modify queries.
for this message.
Explanation: No additional information is available
for this message.
KFWITM226W Starting or stopping Policies on
TEMS: VALUE_0
will affect the operation of the Policies KFWITM234W Query is not editable. Use Create
on all Another to make an editable copy.
Managed Systems connected to that Explanation: No additional information is available
TEMS. for this message.
Do you wish to continue?
Explanation: No additional information is available KFWITM235E Unable to assign Situation: VALUE_0
for this message. .
Explanation: No additional information is available
KFWITM227I VALUE_0 VALUE_1 VALUE_2 . for this message.
Explanation: No additional information is available
for this message.

Appendix E. Understanding informational, warning, and error messages 163

KFWITM236I • KFWITM255E

KFWITM236I Situation has been assigned: VALUE_0 KFWITM246E Unable to stop Situation: VALUE_0 .
.
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KFWITM247I Situation has been stopped: VALUE_0
KFWITM237E Unable to delete Situation: VALUE_0 . .
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KFWITM238I Situation has been deleted: VALUE_0 . KFWITM248E Unable to unassign Situation:
VALUE_0 .
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KFWITM239E Situation: VALUE_0 , already exists,
please enter another name KFWITM249I Situation has been unassigned:
VALUE_0 .
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KFWITM240E Error encountered trying to load a
Situation Definition. KFWITM250E Host incorrect, contains blanks or is
null
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KFWITM241W Expression syntax not yet supported,
only state and distribution are editable. KFWITM251E Port incorrect, must be numeric
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KFWITM242E A Predicate with the function: KFWITM252E Minutes incorrect, valid range is
VALUE_0 cannot be pasted into the 0-44640
formula at this time.
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KFWITM253E Script name incorrect
KFWITM243E Too many predicates, only VALUE_0
Explanation: No additional information is available
are allowed.
for this message.
Explanation: No additional information is available
for this message.
KFWITM254W Script already exists. Do you want to
replace it?
KFWITM244E Unable to start Situation: VALUE_0 .
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KFWITM255E Timeout seconds incorrect
KFWITM245I Situation has been started: VALUE_0 .
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.

164 IBM Tivoli Monitoring: Problem Determination Guide

 KFWITM256W • KFWITM268I

KFWITM256W Save changes to script: VALUE_0 KFWITM263I Distribution of a Correlated Situation

is limited to the Tivoli Enterprise
Explanation: No additional information is available
Monitoring Server hub.
for this message.
Explanation: No additional information is available
for this message.
KFWITM257E User authorization has failed
Explanation: No additional information is available
KFWITM264E The command might contain
for this message.
internationalized characters that are not
supported by the selected agent. Edit
KFWITM258E A single Situation cannot consist of the command or select a different agent.
only one Situation condition.
Explanation: Older agents do not support
Explanation: No additional information is available internationalized characters. They support only
for this message. standard ASCII characters. Either the command string
contains an internationalized character, or one of the
embedded attributes supports internationalized
KFWITM259W The situations embedded in the characters.
current situation will be distributed to
the managed systems listed below. Operator response: Upgrade the target agent to a
version which has globalization support.
Explanation: No additional information is available
for this message.
KFWITM265E The following embedded Situations
are not found in the database:
KFWITM260I Click OK to complete the
redistribution. Click Cancel to cancel Explanation: The list of Situation names in this
the operation. message represent Situations that have been referenced
by the Situation you are trying to save. These Situations
Explanation: No additional information is available are no longer available in the database.
for this message.
Operator response: You must remove the incorrect
references from the Situation you are currently editing.
KFWITM261E Object object was not deleted because
it is referred to by other objects. The
names of these objects are listed below. KFWITM266E Embedded Situations referenced not
Use the Copy button to make a text found in the database.
copy of the object names in this list.
Explanation: At least one Situations refered to in this
Explanation: The specified object was not deleted Situation has not been found int the database.
because other situations or policies need the object to
Operator response: You must remove the incorrect
perform normally. Situations or policies that reference
references from the Situation you are currently editing.
deleted objects fail. The situation dialog displays the
list of affected objects.
KFWITM267E One or more selected attributes use
Operator response: Remove references to the specified
internationalized characters that are not
object listed in the dialog and try deleting the object
supported by the selected emitter target.
again.
Please select different attributes or
select a different emitter target.
KFWITM262I Current distribution prevents
Explanation: Older agents do not support
inclusion of an Action specification.
internationalized characters. They support only
Explanation: The ability to perform an action when a standard ASCII characters. Such an agent cannot be
Situation is true is not allowed if any of the Managed used as the emitter target for attributes that support
Systems that the Situation is distributed to does not internationalized characters.
support the Situation Automation feature.
Operator response: Upgrade the emitter target agent
Operator response: If you want to be able to take an to a version which has globalization support.
action with this Situation, you must remove the
Managed System(s) that do not support Situation
KFWITM268I The certificate’s signer is not trusted:
Action from the assigned distribution list of the
Situation. Explanation: No additional information is available
for this message.

Appendix E. Understanding informational, warning, and error messages 165

KFWITM269I • KFWITM286E

KFWITM269I Be very careful when accepting KFWITM280I Basic constraints are violated
certificates signed by untrusted
Explanation: No additional information is available
certificate authorities.
for this message.
Explanation: No additional information is available
for this message.
KFWITM281I Certificate is not trusted
Explanation: No additional information is available
KFWITM270I The certificate has the following
for this message.
problem:
Explanation: No additional information is available
KFWITM282E The time span time specified must be
for this message.
between 1 hour and 32 years.
Explanation: If you select the Last radio button to
KFWITM271I Valid from:
specify a time span range, the Last text field must
Explanation: No additional information is available contain a numeric value between 1 and 99999.
for this message.
Operator response: Specify a number between 1 and
99999, and click Ok.
KFWITM272I Valid to:
Explanation: No additional information is available KFWITM283E The value specified in the Start Time
for this message. field must precede the value in the End
Time field.
KFWITM273I Issued By: Explanation: If you select the Custom radiobutton to
specify a timespan, the start date/time specified must
Explanation: No additional information is available
be before the end date/time specified.
for this message.
Operator response: Update the start and end time
values so the Start Time precedes the End Time, and
KFWITM274I Issued for:
press Ok.
Explanation: No additional information is available
for this message.
KFWITM284I Server Available through SSL
connection.
KFWITM275I Certificate is expired
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KFWITM285I IBM Confidential OCO Source
KFWITM276I Certificate is not yet valid Materials 5724-C04 Copyright IBM Corp.
2005 The source code for this program is
Explanation: No additional information is available not published or otherwise divested of
for this message. its trade secrets, irrespective of what has
been deposited with the U.S. Copyright
KFWITM277I Certificate is not issued for this host Office.

Explanation: No additional information is available Explanation: No additional information is available

for this message. for this message.

KFWITM278I Issuer and subject don’t match in KFWITM286E The pruning interval specified must
chain be a number between 1 and 99999.

Explanation: No additional information is available Explanation: If you select to prune, the interval must
for this message. be a numeric value between 1 and 99999.
Operator response: Specify a number between 1 and
KFWITM279I Signature chain is incorrect 99999, and press Ok.

Explanation: No additional information is available

for this message.

166 IBM Tivoli Monitoring: Problem Determination Guide

 KFWITM288E • KFWITM306I

KFWITM288E The action was not saved because the KFWITM296I Use space bar to activate
specified action action_name name is
Explanation: No additional information is available
already assigned to the application_name
for this message.
application.
Explanation: Two actions within the same application
KFWITM297I Use arrow keys and spacebar to switch
cannot have the same name. Two actions can have the
tabs.
same name only if they belong to different applications.
Explanation: No additional information is available
Operator response: Specify a unique name for the
for this message.
action.

KFWITM298I Tabular data

KFWITM289E The specified workspace name
already exists. Explanation: No additional information is available
for this message.
Explanation: No additional information is available
for this message.
KFWITM299I Notepad text entry area
KFWITM289I Are you sure you want to remove this Explanation: No additional information is available
view? for this message.
Explanation: No additional information is available
for this message. KFWITM300I Enter notepad text here.
Explanation: No additional information is available
KFWITM290E An unexpected error occurred. The for this message.
current task was cancelled.
Explanation: A error occurred and was logged. KFWITM301I Increase scroll button
Operator response: Attempt to perform the task again. Explanation: No additional information is available
for this message.
KFWITM291E An agent configuration schema was
not found. KFWITM302I Click or use spacebar to increase scroll
value
Explanation: No configuration schema was found for
the monitoring product that was selected. Explanation: No additional information is available
for this message.
Operator response: The agent bundle was not
installed on the Tivoli Enterprise Portal Server.
KFWITM303I Navigator arranged into a tree
hierarchy.
KFWITM292I Product branding image
Explanation: No additional information is available
Explanation: No additional information is available
for this message.
for this message.

KFWITM304I Name
KFWITM293I Horizontal scrollbar
Explanation: No additional information is available
Explanation: No additional information is available
for this message.
for this message.

KFWITM305I Description
KFWITM294I Vertical scrollbar
Explanation: No additional information is available
Explanation: No additional information is available
for this message.
for this message.

KFWITM306I The name of the query.

KFWITM295I Use arrow keys to adjust position.
Explanation: No additional information is available
Explanation: No additional information is available
for this message.
for this message.

Appendix E. Understanding informational, warning, and error messages 167

KFWITM307I • KFWITM328I

KFWITM307I The description of the query. KFWITM318I View port

Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KFWITM308I Formula KFWITM319I Destination systems

Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KFWITM309I Formula area KFWITM320I List of destinations

Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KFWITM310I Text area KFWITM321I Build VALUE_0

Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KFWITM311I Enter text KFWITM322I Version VALUE_0

Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KFWITM312I Press spacebar to toggle. KFWITM323I Tabbed panel

Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KFWITM313I Press spacebar to activate. KFWITM324I Decrease scroll button

Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KFWITM314I Choice KFWITM325I Click or use spacebar to decrease scroll

value
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KFWITM315I Select from the list.
KFWITM326I Navigator view
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KFWITM316I Slider control
KFWITM327I Back history
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KFWITM317I Scroll Pane
KFWITM328I Click or use spacebar to view
Explanation: No additional information is available
workspace history
for this message.
Explanation: No additional information is available
for this message.

168 IBM Tivoli Monitoring: Problem Determination Guide

 KFWITM329I • KFWITM342E

of affected users. Use the User Administration tool to

KFWITM329I Forward history
assign a different Navigator View to each of them and
Explanation: No additional information is available then delete the Navigator View that is no longer
for this message. needed.

KFWITM330E No message was found for the KFWITM337I Enter a name for the Navigator item
message ID VALUE_0.
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KFWITM338I Enter a description of the Navigator
KFWITM331E The message bundle could not be item
loaded to resolve message ID VALUE_0.
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KFWITM340I Resolving host DNS names
KFWITM332E Enter a valid user account for the
Explanation: No additional information is available
system on which this managed system
for this message.
will run.
Explanation: No additional information is available
KFWITM341E The selected action was not
for this message.
completed because a management agent
(ITM 6.1 operating system agent) was
KFWITM333E Enter the password for the user not found on the target computer.
account. If a management agent is installed on
the computer but is offline, start the
Explanation: No additional information is available
management agent and try again.
for this message.
Explanation: Agent management actions require a
running management agent. The ITM 6.1 operating
KFWITM334E The password and the confirmed
system agents serve as management agents and are
password do not match.
responsible for dispatching and executing management
Explanation: No additional information is available actions. Therefore, an operating system agent must be
for this message. running on the computer for which the action was
taken.
KFWITM335W The columns listed below for the Operator response: Install an ITM 6.1 operating
situation formula have no conditions system agent on the target computer. If an ITM 6.1
defined, and will be removed from the operating system agent is already installed but is offline
definition: and not visible in the Tivoli Enterprise Portal client,
start the operating system agent and try again.
Explanation: Due to the dynamic filtering of Situation
Conditions, Situation Distribution choices, and other
components of Situation Definitions, any columns that KFWITM342E The selected action was not
do not have conditions specified in them will be completed because the management
removed from the Condition Table before any other agent (operating system agent) is not
Situation Editor dialog page can be opened. running.
Start the operating system agent and try
the action again.
KFWITM336E Could not delete VALUE_0 because
one or more Explanation: A running ITM 6.1 operating system
users have it defined as their only agent is required on the computer for which the action
Navigator View. was taken. The operating system agents serve as
See client trace log for list of users. management agents and are responsible for dispatching
and executing management actions.
Explanation: The referenced Navigator View is in use
by one or more users for whom it is defined as their Operator response: Start the ITM 6.1 operating system
only Navigator View. The deletion has been rejected agent on the target computer. Install an ITM 6.1
because if it had been allowed, those users would no operating system agent on the target machine and try
longer have access to the product. the operation again.
Operator response: The client trace log shows the list

Appendix E. Understanding informational, warning, and error messages 169

KFWITM343I • KJRITM006E

KFWITM343I The navigator item you are expanding KFWITM351I The <VALUE_0> product has not been
contains VALUE_0 subitems. You may installed on the TEP server.
limit the number of subitems displayed.
Explanation:
Explanation: No additional information is available
Operator response: Install the product and try again.
for this message.

KFWITM352E A <VALUE_0> emitter activity

KFWITM344E You must use a whole number greater
requires situation attributes. Please first
than zero.
add one or more situation activities to
Explanation: No additional information is available the workflow.
for this message.
Explanation:
Operator response: Install the product and try again.
KFWITM345E A metafile is required.
Explanation: No additional information is available
KFWITM353I Please wait while the Managed
for this message.
Systems and Managed System Lists are
retrieved.
KFWITM346E The situation formula is too large.
Explanation:
Please clear contents of at least one
formula cell. Operator response:
Explanation: No additional information is available
for this message. KJRITM001I Link Wizard - Define New Link(
VALUE_0 )
KFWITM347E Navigator view is empty Explanation: No additional information is available
for this message.
Explanation: No additional information is available
for this message.
KJRITM002I Link Wizard - Edit Link( VALUE_0 )
KFWITM348E The Tivoli Enterprise Portal has not Explanation: No additional information is available
been configured to connect to a Tivoli for this message.
Enterprise Portal Server.
Configure the hostname of a TEP server
to use and try again. KJRITM003I Select value to assign to property when
link is activated
Explanation: Before using TEP it must be configured
to connect to a TEP server. This can be done using the Explanation: No additional information is available
CandleConfig CLI or choosing Configure on TEP from for this message.
Tivoli Enterprise Services.
Operator response: Fix the configuration and try KJRITM004I Select property to receive value when
again. link is activated
Explanation: No additional information is available
KFWITM349E No emitter targets found for emitter for this message.
type <VALUE_0>.
Explanation: KJRITM005I Select target to display when link is
activated
Operator response: Fix the emitter targets and try
again. Explanation: No additional information is available
for this message.

KFWITM350E Parameter <VALUE_0> is missing.

KJRITM006E Syntax Error
Explanation:
Explanation: No additional information is available
Operator response: Fix the parameter and try again. for this message.

170 IBM Tivoli Monitoring: Problem Determination Guide

 KJRITM007I • KJRITM025E

KJRITM007I Close the window KJRITM016E Incorrect Latitude and Longitude (or
Zip Code)
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KJRITM008W Close the window, discarding
changes KJRITM017W No image file is associated with
image alias:
Explanation: No additional information is available
\ ’ \ ’ VALUE_0 \ ’ \ ’ .
for this message.
Would you like to associate one now?
Explanation: No additional information is available
KJRITM009I Values available for insertion into text
for this message.
Explanation: No additional information is available
for this message.
KJRITM018I Click here to calibrate map
Explanation: No additional information is available
KJRITM010I Select coordinate system
for this message.
Explanation: No additional information is available
for this message.
KJRITM019E File could not be exctracted
Explanation: No additional information is available
KJRITM011I Enter Latitude and Longitude (or Zip
for this message.
Code) of the first point and click OK,
then click that point inside ANY corner
box KJRITM020W File ended prematurely
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KJRITM012I Enter Latitude and Longitude (or Zip KJRITM021E Incorrect width or height
Code) of the final point and click OK,
Explanation: No additional information is available
then click that point in the OPPOSITE
for this message.
corner box
Explanation: No additional information is available
KJRITM022E Unable to launch browser
for this message.
Explanation: No additional information is available
for this message.
KJRITM013W Calibration cancelled
Explanation: No additional information is available
KJRITM023E Browser is not defined
for this message.
Explanation: No additional information is available
for this message.
KJRITM014W Calibration completed.
North: VALUE_0
South: VALUE_1 KJRITM024E The specified cryptographic type is
East: VALUE_2 incorrect.
West: VALUE_3
Apply this calibration? Explanation: No additional information is available
for this message.
Explanation: No additional information is available
for this message.
KJRITM025E The specified key source is incorrect.

KJRITM015E Illogical calibration coordinates. Explanation: No additional information is available

Calibration cancelled. for this message.

Explanation: No additional information is available

for this message.

Appendix E. Understanding informational, warning, and error messages 171

KJRITM026E • KJRITM045E

KJRITM026E Cannot find and load cryptographic KJRITM036E The cipher-text byte array cannot be
algorithm. Base64 encoded into a string.
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KJRITM027E Cannot locate the key-store directory KJRITM037E The encoded cipher-text string cannot
or read key files within it. be Base64 decoded into a byte array.
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KJRITM028E Cannot read key material from the key KJRITM038E The key specified to be written to the
file. key file is the wrong length.
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KJRITM029E Cannot write key material to the key KJRITM039E Encryption of a zero length plain-text
file. byte array was attempted.
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KJRITM030E The key material to be written to the KJRITM040E Decryption of a zero length cipher-text
key file cannot be encrypted. string was attempted.
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KJRITM031E The encrypted key material read from KJRITM041E The specified cryptographic type is
the key file cannot be decrypted. unavailable.
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KJRITM032E The key material stored within the KJRITM042E The specified property file is not
key file is incorrect. found.
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KJRITM033E The cipher-text’s ID tag prefix is KJRITM043E The specified property file cannot be
missing. read.
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KJRITM034E The plain-text byte array cannot be KJRITM044E The specified property value cannot
encrypted. be UTF-8 encoded.
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KJRITM035E The cipher-text byte array cannot be KJRITM045E The specified property file cannot be
decrypted. written.
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

172 IBM Tivoli Monitoring: Problem Determination Guide

 KJRITM046E • KUIC00001E

KJRITM046E Incorrect arguments input to encode KJRITM054I Press spacebar to toggle.

property CLI.
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KJRITM055I Press spacebar to activate.
KJRITM047E The link name link_name is not unique
Explanation: No additional information is available
in this launching context. Choose
for this message.
another name for the link.
Explanation: The link names must be unique within
KJRITM056I Choice
the current launching context to prevent links with the
same name from displaying in the same context menu. Explanation: No additional information is available
for this message.
Operator response: Change the name of the current
link.
KJRITM057I Select from the list.
KJRITM048E A value is required for link_name Explanation: No additional information is available
for this message.
Explanation: This field requires a value.
Operator response: Type an appropriate value into the
KJRITM058I Slider control
field.
Explanation: No additional information is available
for this message.
KJRITM049E The confirmation does not match for
link_name.
KJRITM059I Scroll Pane
Explanation: The confirmation value does not match
the value of the first input field. Explanation: No additional information is available
for this message.
Operator response: Type the same value into the
confirmation field as the first input field.
KJRITM060I View port
KJRITM050E The value must be an integer for Explanation: No additional information is available
link_name. for this message.
Explanation: The input field accepts only integer
values. KJRITM061I Destination systems
Operator response: Type an integer value into the Explanation: No additional information is available
input field. for this message.

KJRITM051I Tabular data KJRITM062I List of destinations

Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KJRITM052I Text area KUIC00001E KUIC00001E: The host name is not

specified.
Explanation: No additional information is available
for this message. Explanation: You must specify the -s option with a
host name or address. Optionally, you can specify
PROTOCOL and PORT as
KJRITM053I Enter text
[PROTOCOL://]HOST[:PORT].
Explanation: No additional information is available
Operator response: Specify the correct host name or
for this message.
address and try the operation again.

Appendix E. Understanding informational, warning, and error messages 173

KUIC00002E • KUIC02003E

KUIC00002E KUIC00002E: An incorrect protocol KUIC00010E KUIC00010E: The specified time out time
protocol was specified. is incorrect.
Explanation: You must specify a correct protocol to Explanation: You cannot login with the specified time
login. out.
Operator response: Provide the correct protocol, for Operator response: Specify a time out between 1 to
example, https:// or http://. 1440 and log in again.

KUIC00003E KUIC00003E: You cannot login to the KUIC01001I KUIC01001I: user already logged off the
server server. server server.
Explanation: The specified server name is incorrect. Explanation: No additional information is available
for this message.
Operator response: Specify the correct server name
and login again.
KUIC01002I KUIC01002I: user logged off of the server
server.
KUIC00004I Username?
Explanation: No additional information is available
Explanation: No additional information is available
for this message.
for this message.

KUIC02001E KUIC02001E: The command did not

KUIC00005I Password?
complete because the parm option is
Explanation: No additional information is available incorrect.
for this message.
Explanation: You specified incorrect syntax for the
command.
KUIC00006E KUIC00006E: The specified user name
Operator response: Before you run the command
or password is incorrect.
again, run the help command to determine the correct
Explanation: You are not logged in because you options:
specified an incorrect user name or password or you do tacmd help | ? {command}
not have permission to log in. where:
{command} specifies the command you ran with
Operator response: Verify the correct user name and incorrect syntax.
password and that you have permission to log in.

KUIC02002E KUIC02002E: The argument for the parm

KUIC00007I KUIC00007I: User user logged into option is missing.
server on server.
Explanation: The specified option requires at least one
Explanation: No additional information is available argument.
for this message.
Operator response: Before you run the command
again, run the help command to determine the correct
KUIC00008W KUIC00008W: The connection you are options:
using is not secure. tacmd help| ? {command}
Explanation: No additional information is available where:
for this message. {command} specifies the command you ran with
incorrect syntax.

KUIC00009E KUIC00009E: The specified port number

port is incorrect. KUIC02003E KUIC02003E: The parm option in the
command is not recognized.
Explanation: You cannot log in with the specified port
number. The default is 1920 for http and 3661 for https. Explanation: The command cannot be run with
specified option.
Operator response: Specify a port number between 1
to 65536 and log in again. Operator response: Before you run the command
again, run the following help command to determine
the correct options:
tacmd help | ? {command}
where:

174 IBM Tivoli Monitoring: Problem Determination Guide

 KUIC02004E • KUIC02021E

{command} specifies the command you ran with

KUIC02015E KUIC02015E: The correct user name and
incorrect syntax.
password were not provided.
Explanation: You must provide your user name and
KUIC02004E KUIC02004E: The parm command is not
password.
recognized.
Operator response: Run the login command and then
Explanation: The specified command is not a correct
try the operation again.
command.
Operator response: Before you run the command
KUIC02016E KUIC02016E: You did not specify a
again, run the help command to determine the correct
command.
commands:
tacmd help | ? Explanation: You must specify a command to
complete an operation.
KUIC02005E KUIC02005E: The command did not Operator response: Before you run the command
complete because required options were again, run the help command to determine the correct
not provided. commands:
tacmd help | ?
Explanation: You must run the command with
required options.
KUIC02017E KUIC02017E: A system error occurred.
Operator response: Before you run the command
again, run the help command to determine the correct Explanation: The shared library name and function
options: name were not specified in the command’s input
tacmd help | ? {command} validation file.
where:
Administrator Response: Contact IBM Software
{command} specifies the command you ran with
Support.
incorrect syntax.

KUIC02018E KUIC02018E: The name shared library

KUIC02011E KUIC02011E: The file_name file is not
file was not loaded.
available.
Explanation: The command cannot complete without
Explanation: The file you are trying to read is
the specified library file.
unavailable either because it is corrupt or does not exist
in the specified directory. Administrator Response: Confirm that the shared
library exists and is readable. If it does not exist, you
Operator response: Verify that the file exists and that
might need to install function on the computer or
it is readable.
server in order to support the specified command.
Contact IBM Software Support if the shared library file
KUIC02012E KUIC02012E: You already logged out. exists and is readable.
Explanation: No additional information is available
for this message. KUIC02019E KUIC02019E: You already logged out.
Explanation: No additional information is available
KUIC02013E KUIC02013E: The software did not run for this message.
the command because of a internal
system error. Contact the system
KUIC02020E KUIC02020E: The environment variable
administrator.
name is unavailable.
Explanation: No additional information is available
Explanation: The above environment variable is
for this message.
required to proceed.
Administrator Response: Contact the system
KUIC02014E KUIC02014E: A server communication
administrator.
error occurred.
Explanation: The command did not complete because
KUIC02021E KUIC02021E: The file file_name is empty.
there is a server communication problem with the
Tivoli Enterprise Monitoring Server. Explanation: This file does not contain data.
Operator response: Run the login command to Operator response: Confirm that the file exists and is
confirm that the server is available. readable. If the file does exist and is readable, contact
IBM Software Support.

Appendix E. Understanding informational, warning, and error messages 175

KUICAB001E • KUICAB005E

correctly set by default on the server to indicate the

KUICAB001E KUICAB001E: The binArch
primary installtion location of IBM Tivoli Monitoring.
environment variable must be set before
Currently, the variables that are used are
running this command.
CANDLEHOME on UNIX and Linux systems, and
Explanation: The architecture type specific to your CANDLE_HOME on Windows systems.
system must be set. This variable is not set on the
current server.For UNIX and Linux systems, this
KUICAB004E KUICAB004E: The server installation
directory is a subdirectory of the primary installation
location indicated by the candlehome
location of the server. The primary location of an IBM
environment variable does not appear to
Tivoli Monitoring server is indicated by the
be a directory: envval.
CANDLEHOME environment variable.
Explanation: The primary location of an IBM Tivoli
Operator response: Establish this variable for your
Monitoring server is indicated by an environment
system, indicating the platform architecture of this
variable that is specific to your system. Currently, that
server.
is CANDLEHOME on UNIX and Linux systems, and
CANDLE_HOME on Windows systems. This variable
KUICAB002E KUICAB002E: The candlehome was set incorrectly on this server, and is not referencing
environment variable must be set before a directory.
running this command.
Operator response: Correct the appropriate
Explanation: The primary location of an IBM Tivoli environment variable that is specific to your system,
Monitoring server is indicated by an environment indicating the primary installation directory of this
variable that is specific to your system. Currently, this server. Currently, the variables that are used are
is CANDLEHOME on UNIX and Linux systems, and CANDLEHOME on UNIX and Linux systems, and
CANDLE_HOME on Windows systems. This variable is CANDLE_HOME on Windows systems.
not set on the current server.
Administrator Response: Verify that the appropriate
Operator response: Establish the appropriate environment variable that is specific to your system is
environment variable that is specific for your system, correctly set by default on the server to indicate the
indicating the primary installation location of this primary installation directory of IBM Tivoli Monitoring.
server. Currently, the variables that are used are Currently, the variables that are used are
CANDLEHOME on UNIX and Linux systems, and CANDLEHOME on UNIX and Linux systems, and
CANDLE_HOME on Windows systems. CANDLE_HOME on Windows systems.
Administrator Response: Verify that the appropriate
environment variable that is specific for your system is KUICAB005E KUICAB005E: The location of the jar
correctly set by default on the server to indicate the files directory needed by createNode
primary installation location of IBM Tivoli Monitoring. was not found: envval.
Currently, the variables that are used are
Explanation: Several jar files are needed by
CANDLEHOME on UNIX and Linux systems, and
createNode, and are expected to be found in a specific
CANDLE_HOME on Windows systems.
location on each server. The jar files location was not
found on this server.
KUICAB003E KUICAB003E: The server installation
Administrator Response: Locate the
location envval indicated by the
candlehome environment variable does jars
not exist.
directory on the server that contains
Explanation: The primary location of an IBM Tivoli
Monitoring server is indicated by an environment createnode.jar
variable that is specific to your system. Currently, this
is CANDLEHOME on UNIX and Linux systems, and , along with several other jar files. Copy that directory
CANDLE_HOME on Windows systems. This variable and all of its contents to the expected location. This
was set incorrectly on this server. location varies by system as follows:
v On UNIX/Linux systems:
Operator response: Correct the appropriate
$CANDLEHOME/platform/kui/jars/
environment variable that is specific to your system,
indicating the primary installation location of this v On Windows systems:
server. Currently, the variables that are used are %CANDLE_HOME%\CLI\jars\
CANDLEHOME on UNIX and Linux sysgtems, and
CANDLE_HOME on Windows systems.
Administrator Response: Verify that the appropriate
environment variable that is specific to your system is

176 IBM Tivoli Monitoring: Problem Determination Guide

 KUICAB006E • KUICAB024I

KUICAB006E KUICAB006E: The required jar file KUICAB017E KUICAB017E: The directory
jarfile was not found in the expected IMAGEPATH does not exist.
location.
Explanation: No additional information is available
Explanation: Several jar files are needed by for this message.
createNode, and are expected to be found in a specific
location on each server. However, that location is
KUICAB018E KUICAB018E: The directory
missing at least one of the expected jar files on this
IMAGEPATH contains no bundles.
server.
Explanation: No additional information is available
Administrator Response: Locate the
for this message.
jars

directory on the server and verify that it contains all of KUICAB019E KUICAB019E: The directory
the required jar files. Perform a search on the server for IMAGEPATH contains no bundles
the referenced missing jar file, then copy it to the matching the product(s), platform(s),
appropriate location. and/or version(s) specified. There are no
bundles to add.
v On UNIX/Linux systems:
$CANDLEHOME/platform/kui/jars/ Explanation: No additional information is available
v On Windows systems: for this message.
%CANDLE_HOME%\CLI\jars\
KUICAB020I KUICAB020I: Adding bundles to the
KUICAB007E KUICAB007E: The path for DEPOTPATH depot. The time required
DEPOTHOME depotHome was not to complete this operation depends on
found. the number and size of the added
bundles.
Explanation: The specified path to the depot is
incorrect or does not exist. Explanation: No additional information is available
for this message.
Operator response: If the variable DEPOTHOME was
specified within the KBBENV file then change the
value of this variable to correct path to the depot. If KUICAB021I KUICAB021I: The specified bundles in
DEPOTHOME was not specified within KBBENV file, the IMAGEPATH directory already exist
call IBM Software Support. in the DEPOTPATH depot. There are no
bundles to add.
Administrator Response: If the variable
DEPOTHOME was specified within the KBBENV file, Explanation: No additional information is available
change the value of DEPOTHOME to correct path to for this message.
the depot. If DEPOTHOME was not specified within
KBBENV file, call IBM Software Support. KUICAB022I KUICAB022I: The following bundles
were successfully added to the
KUICAB008E KUICAB008E: The path to the DEPOTPATH depot:
DEPOTHOME directory was not found. Explanation: No additional information is available
Explanation: The specified value of the DEPOTHOME for this message.
variable was not found.
Operator response: Verify the location of the depot KUICAB023I KUICAB023I: Are you sure you want to
and specify the correct location as the value for add the following bundles from the
DEPOTHOME in the KBBENV file. DEPOTPATH depot?

Administrator Response: Verify the location of the Explanation: No additional information is available
depot and specify this location as the value for for this message.
DEPOTHOME in the KBBENV file.
KUICAB024I KUICAB024I: Enter Y for yes or N for
KUICAB010E KUICAB010E: The addbundles no:
command did not complete. Refer to the Explanation: No additional information is available
following returned error: for this message.
ERRORTEXT
Explanation: No additional information is available
for this message.

Appendix E. Understanding informational, warning, and error messages 177

KUICAB025E • KUICAR012E

KUICAB025E KUICAB025E: RESPONSE is not a KUICAR006I KUICAR006I: The product type TYPE
correct response. Enter Y for yes or N on HOSTNAME is now being managed.
for no:
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KUICAR007I KUICAR007: Are you sure you want to
KUICAR001E KUICAR001E: The managed system update the management configuration
was not added because incorrect syntax for MANAGEDSYSTEM with the given
was specified. property values? Type Y for yes or N for
no:
Explanation: You must specify -t/--type option when
running the addSystem command. Explanation: No additional information is available
for this message.
Operator response: Run the viewDepot command to
view a list of available products. Verify the correct
managed system type and run the addSystem KUICAR008E KUICAR008E: The managed system
command again. was not added because the node was
not specified.
KUICAR002E KUICAR002E: You are not logged in. Explanation: You must specify the node with the
-n/--node option to identify the node to start. A node is
Explanation: You must log into the server from which
identified by the managed system that it contains.
you run the addSystem command to use the -n option.
Operator response: Run the listSystems -t UX NT LZ
Operator response: Log into the server from which
command to view a list of available nodes. Verify the
you want run the addSystem command or run the
node and try adding the managed system again.
addSystem command using the -d option to specify the
directory containing the node components.
KUICAR009E KUICAR009E: NODE is not a node
name.
KUICAR003E KUICAR003E: The managed system
MANAGEDSYSTEM was not found by Explanation: The addSystems command did not
the server HOST. complete because the -n options specified an incorrect
node name. A node is identified by the managed
Explanation: The specified managed system was not
system that it contains.
found on the node.
Operator response: Run the listSystems -t UX NT LZ
Operator response: Use the listSystems command to
command to view a list of available nodes. Verify the
list known managed systems on a node. Verify the
node and try adding the managed system again.
managed system and try adding the managed system
again.
KUICAR010I KUICAR010I: The agent type TYPE is
being deployed.
KUICAR004E KUICAR004E: The addSystem
command did not complete because the Explanation: No additional information is available
-p option was not specified. for this message.
Explanation: You must specify one or more
configuration properties and their values that identify KUICAR011E KUICAR011E: You must specify the
the managed system you are adding. UACONFIG option to configure a
Universal Agent.
Operator response: Specify the properties with the -p
option and run the addSystem command again. The Explanation: No additional information is available
syntax for specifying properties is [{-p | [property | for this message.
--properties} NAME=VALUE . . .]
KUICAR012E KUICAR012E: The value of the
KUICAR005I KUICAR005: Are you sure you want to RESTART parameter must either be Y or
update the management configuration N.
for MANAGEDSYSTEM from the
Explanation: No additional information is available
FILENAME file? Type Y for yes or N for
for this message.
no:
Explanation: No additional information is available
for this message.

178 IBM Tivoli Monitoring: Problem Determination Guide

 KUICAR013E • KUICCN005I

KUICAR013E KUICAR013E: The parameter PARAM KUICAR099E KUICAR099E: The addSystem

is not a correct option for Universal command did not complete because a
Agent configuration. system error occurred.
Explanation: No additional information is available Explanation: An unexpected error occurred.
for this message.
Operator response: Refer to the log for details and
contact the system administrator.
KUICAR014E KUICAR014E: The KEYNAME was not
deployed.
KUICCN001I Initializing required services...
Explanation: You cannot add a node using the
Explanation: No additional information is available
addSystem command. Use the addSystem command
for this message.
managed systems.
Operator response: Run the installNode command to
KUICCN002I Beginning the installation and
install or add a node.
configuration process...
Explanation: No additional information is available
KUICAR015E KUICAR015E: KEYNAME is not a
for this message.
correct key name. Key names must be
qualified.
KUICCN003E The --VALUE_0 and the --VALUE_1
Explanation: No additional information is available
options are duplicates. Use one or the
for this message.
other, but not both.
Explanation: When specifying options, it is necessary
KUICAR016E KUICAR016E: The TYPE agent could
to specify any unique, atomic option just one time. If
not be added because node NODE is
more than one instance of any particular option is
offline.
specified, it is not possible to know which instance of
Explanation: No additional information is available the option should be used.
for this message.
Operator response: Examine the duplicates and
remove the instance that is not needed. Look for
KUICAR017E KUICAR017E: The TYPE agent could occurrences where a command alias might have been
not be added to node NODE because the used, because this makes it less obvious that any
server could not locate any version of duplication has occurred.
the agent in the CMS depot. Use the
viewDepot command to list the contents
KUICCN004E A login ID was provided with no
of a depot.
password, and the --force flag is
Explanation: No additional information is available preventing prompting for a password.
for this message.
Explanation: The
--force
KUICAR018E KUICAR018E: The property PARAM is
not a valid configuration property. flag was used in a situation where additional
Explanation: No additional information is available information is required in order to perform the
for this message. operation.
Operator response: Either avoid using the
KUICAR019E KUICAR019E: The INSTANCE --force
property cannot have an empty value.
Explanation: No additional information is available flag for this operation, or explicitly provide the needed
for this message. password.

KUICAR020E KUICAR020E: The addSystem KUICCN005I Enter the password for VALUE_0.
command did not complete because a Explanation: No additional information is available
deployment error occurred. Refer to the for this message.
following error returned from the
server:
Explanation: No additional information is available
for this message.

Appendix E. Understanding informational, warning, and error messages 179

KUICCN006E • KUICCN012E

If you can not verify the parameters, use the default

KUICCN006E The password can not be blank.
settings. On Windows systems, it is also possible that
Explanation: Empty passwords are not allowed. some type of port problem occurred. Try checking the
output of netstat and look for any anomalies.
Operator response: Specify a password. If the targeted
host does not have a password, supply one, or use a
different connection protocol. For example, SSH using a KUICCN010E The host name of the local host was
private key. not determined.
Explanation: The host name of this server could not
KUICCN007E The temporary directory on this host be determined. This is typically an indication of a
was not determined. networking problem that might cause this program to
malfunction.
Explanation: The local, system temporary directory for
the local host is required in order for this operation to Administrator Response: Verify that there are no
proceed. For example, on UNIX systems this is problems with the network, such as any name servers
/tmp that can be in use. Check the hosts file and verify that
it is correctly populated. Verify that the local network
, and on Windows systems: settings are correct and valid. For example, on UNIX
systems, this can mean checking the contents of the
C:\WINNT\Temp
/etc/resolv.conf
, or
file. On Windows systems, check the TCP/IP settings.
C:\WINDOW\Temp

. KUICCN011E A command-line options parsing error

has occurred.
Administrator Response: Create a standard temporary
directory on this host, if it does not exist. On Windows Explanation: Some unexpected input was provided as
systems, if the temporary directory does exist, verify an option to this program and that input is causing a
that the problem. The supported options are: [{-h|--host}
[{smb|ssh|rexec|rsh}://]HOST[:PORT]] \\
TEMP
[{-u|--username} USERNAME [{-w|--password}
PASSWORD]] \\ [{-o|--option|--options}
system environment variable is set correctly to that
NAME=VALUE ...] \\ [{-d|--dir|--directory}
temporary directory location.
NODEDIR] \\ [{-i|--imagePath} IMAGEPATH] \\
[{-p|--property|--properties} NAME=VALUE ...] \\
KUICCN008E Trace logging on this host could not [{-f|--force}].
be established.
Operator response: Examine the input passed to this
Explanation: The logging facility used by this program and look for anything illegal or not valid. If
program did not configure or launch properly, or both. something illegal or not valid is found, correct the error
Without trace logging, it is difficult to troubleshoot any and run the program again.
problems that can occur.
Administrator Response: Verify that valid, custom KUICCN012E There was syntax that is not valid.
logging configuration parameters have been specified. There is an unrecognized option,
If there is any doubt, try using just the default settings. VALUE_0 provided.
On Windows systems it is possible that some type of
Explanation: An unsupported option, that is not valid,
port problem occurred. Try checking the output of
was provided to this program.
netstat and look for any anomalies.
Operator response: Only use options for this program
that are explicitly supported. The supported options
KUICCN009E Trace logging for the remote
are: [{-h|--host}
communications subsystem on this host
[{smb|ssh|rexec|rsh}://]HOST[:PORT]] \\
could not be established.
[{-u|--username} USERNAME [{-w|--password}
Explanation: The logging facility for the remote PASSWORD]] \\ [{-o|--option|--options}
communications library used by this program did not NAME=VALUE ...] \\ [{-d|--dir|--directory}
configure or launch properly, or both. Without trace NODEDIR] \\ [{-i|--imagePath} IMAGEPATH] \\
logging, it is difficult to troubleshoot any remote [{-p|--property|--properties} NAME=VALUE ...] \\
communications problems that can occur. [{-f|--force}].
Administrator Response: Verify that only valid,
custom logging configuration parameters are specified.

180 IBM Tivoli Monitoring: Problem Determination Guide

 KUICCN013E • KUICCN020E

KUICCN013E A property specification that is not KUICCN017E The Host specification VALUE_0 could
valid was detected. There is a missing not be resolved on the network. It can
name in VALUE_0. not be verified to be valid.
The expected property specification
Explanation: The specified host name or IP address
syntax is <NAME>=<VALUE>.
could not be verified to be valid. This can be an
Explanation: A configuration property was specified, indication of a networking problem that might cause
but no name was provided. Without a name, it is not this program to malfunction.
possible to know how to apply any specified value to
Operator response: Verify that there are no typing
the installation operation.
errors in the host specification.
Operator response: Specify an appropriate name with
Administrator Response: Verify that there are no
every property specification. For example, the expected
problems with the network, such as any name servers
syntax is
that can be in use. Check the hosts file and verify that
--property <NAME>=<VALUE> it is correctly populated. Verify that the local network
settings are correct and valid. For example, on UNIX
. systems this might mean checking the contents of the
/etc/resolv.conf
KUICCN014E A property specification that is not
valid was detected. There is a missing file. On Windows systems, check the TCP/IP settings.
value in VALUE_0.
The expected property specification
KUICCN018E An property specification that is not
syntax is <NAME>=<VALUE>.
valid was detected. You must use a
Explanation: A configuration property was specified, positive integer: VALUE_0.
but no value was provided. Without a value, it is not
Explanation: A configuration property was specified
possible to know what was intended for any specified
that has a value that is not valid for the associated
name.
name. Some property names support only specific data
Operator response: Specify an appropriate value with types or data ranges. The name that was used for this
every property specification. For example, the expected invocation requires positive integers, and can not use
syntax is: anything else.
--property <NAME>=<VALUE>. Operator response: Change the value to a positive
integer. Always use positive integers with this
. Some examples of valid property names are: KEY and particular name.
SERVER.

KUICCN019E An option with a specification that is

KUICCN015E An property specification that is not not valid was detected: VALUE_0.
valid was detected. There is an The syntax for the expected option
unsupported name in VALUE_0. specification is <NAME>=<VALUE>.
Explanation: A configuration property was specified, Explanation: A configuration option was specified that
but the provided name was not recognized. used an unexpected, unsupported format. The format
Operator response: Only use property specifications that was used is causing problems.
that are known to be supported. You must specify Administrator Response: Only specify options using
NAME=VALUE pairs. Some examples of valid property the supported syntax of
names are: KEY and SERVER.
<NAME>=<VALUE>

KUICCN016E A property specification that is not , where the name is a valid, supported name, and the
valid was detected. There is an value is appropriate and valid for that particular name.
unsupported value in VALUE_0.
The accepted values are: VALUE_1.
KUICCN020E An option specification that is not
Explanation: A configuration property was specified valid was detected. There is a missing
that has a value that is not valid for the associated name in VALUE_0.
name. Some property names support only specific data The syntax for the expected option
types or data ranges. specification is <NAME>=<VALUE>.
Operator response: Specify a value that is suitable for Explanation: A configuration option was specified, but
the name that is being used. no name was provided. Without a name, it is not

Appendix E. Understanding informational, warning, and error messages 181

KUICCN021E • KUICCN028E

possible to know how to apply any specified value to

KUICCN024E A port that is not valid was specified
the installation operation.
for connecting to host VALUE_0.
Operator response: Specify an appropriate name with
Explanation: An port value that is not valid was
every option specification. For example, the expected
specified, so a connection to the host could not be
syntax is
established.
--option <NAME>=<VALUE>
Operator response: Replace the port specification with
. a valid port. Port numbers must be positive integers.

KUICCN021E An option specification that is not KUICCN025E VALUE_0 option requires a numeric
valid was detected. There is a missing value. The value VALUE_1 is
value in VALUE_0. non-numeric.
The expected option specification syntax Explanation: A configuration option was specified
is <NAME>=<VALUE>. with a non-numeric value, where a numeric value is
Explanation: A configuration option was specified, but required.
no value was provided. Without a value, it is not Operator response: Provide a valid, numeric value for
possible to know what was intended for any specified the specified option. If a positive integer is required,
name. provide a positive integer.
Operator response: Specify an appropriate value with
every option specification. For example, the expected KUICCN026E The logs directory could not be
syntax is identified on VALUE_0.
--option <NAME>=<VALUE>
Explanation: The logging directory for the local server
could not be found in the expected location.
.
Administrator Response: Verify that the expected
logging directory exists. If it does not exist, create it.
KUICCN022E An unsupported protocol was
specified in VALUE_0. v On UNIX systems: $CANDLEHOME/CMS/logs/
The supported protocols are:VALUE_1. v On Windows systems:
%CANDLE_HOME%\CMS\logs\
Explanation: There is a finite set of protocols currently
supported by this program. The protocol that was
specified is not one of them. KUICCN027E The depot directory could not be
identified on VALUE_0.
Operator response: Only specify protocols that are
currently supported. Explanation: The depot directory for the local server
could not be found in the expected location.
KUICCN023E The value VALUE_0 could not be Administrator Response: Verify that the expected
resolved on the network. It can not be depot directory exists. If not, find its current location,
verified to be valid. and make a copy, or symbolic link on a UNIX system,
to the expected location.
Explanation: The specified target host name could not
be verified to be valid. This is typically an indication of v On a UNIX system: $CANDLEHOME/CMS/depot/
a networking problem that can cause this program to v On a Windows system:
malfunction. %CANDLE_HOME%\CMS\depot\
Administrator Response: Verify that there are no
problems with the network, such as any name servers KUICCN028E The silent response file for agent
that might be in use. Check the hosts file and verify VALUE_0 could not be found in
that it is correctly populated. Verify that the local VALUE_1.
network settings are correct and valid. For example, on
Explanation: The default silent installation responses
UNIX systems, this might mean checking the contents
file could not be found with the OS agent installation
of the
image in the depot. This file is required.
/etc/resolv.conf
file Administrator Response: Create a new silent
installation response file named
. On Windows systems, check the TCP/IP settings. silent.txt

in the platform-specific OS agent image directory in the

depot. This is either KNT, KLZ, or KUX.

182 IBM Tivoli Monitoring: Problem Determination Guide

 KUICCN029E • KUICCN034E

KUICCN029E The silent response file for the agent KUICCN033E When specifying a password, a user
could not be read: VALUE_0" name or login must also be provided.
Explanation: The default silent installation responses Explanation: A password was provided, but without a
file was found in the depot, but could not be opened user name or login, there is no way that it can be used
and read. to establish a connection to the target host.
Administrator Response: Verify that the permissions Operator response: Use
on the file allow reading by this program. Also, for --username
operating systems that support file locking by default,
such as Windows systems and HP-UX systems, verify to specify a user name that is valid on the target host,
that the file is not locked by another process. and has valid specified password.

KUICCN030E The specified timeout number is not KUICCN034E Unable to connect to host VALUE_0
valid: VALUE_0. using the provided credentials on the
Explanation: The timeout that was specified is not following protocol(s): VALUE_1.
valid. Timeout values must be specified as positive Explanation: An attempt was made to connect to the
integers, representing the maximum number of seconds target host using the provided credentials, but that
to allow the installation to run before reporting a attempt failed.
failure.
Operator response: Verify that the provided
Operator response: Specify a positive integer value for credentials are valid. For example, if a user name and
the timeout value, or use the default value. password were provided, make sure that the user name
is valid on the target host, and that the specified
KUICCN031E Some type of complete, authorized password is correct for that user. If you continue to
credentials must be provided for host have problems, consider trying alternate connection
VALUE_0. approaches if possible, such as SSH.

Explanation: No authorization credentials were Examine the trace logs for more information. If
provided, and that information is required to establish necessary, increase the tracing levels to produce more
a connection to the target host, even if that is the local output in the logs.
host. Examples of authorization credentials are user Administrator Response: Make sure that the access
name, password, SSH key file, and SSH passphrase. method being used is appropriate for the target host.
Operator response: Provide the appropriate For example, if a user name and password were used,
credentials that are required to establish a connection make sure that user account exists on the host, and
the target host. uses the specified password. If SSH was used, make
sure the SSH daemon or service is running on the
target host. If SSH was used with a key file approach,
KUICCN032E When specifying an SSH private key make sure the key being used is valid, and has been
file, a user name must be provided. properly added to the
Explanation: Connections established with SSH using authorized_keys
a key instead of a password, still require a login ID.
Without this identification, the remote SSH daemon or file for the user account on the target host.
service does not know in what context to validate the
key. For example, the SSH daemon or service needs to In general, this program needs some form of access to
check the the target host(s) in order to establish a connection and
authorized_keys2 be successful. If sufficient security measures are in
place, they might block this program’s access, too.
file under the home directory of the specified user Verify that any intervening firewalls are configured in a
name or login. manner that allows this program to be successful by
one of its available communication protocols, for
Operator response: Use example, SMB, SSH, REXEC, RSH. It is equally
--username important that those services be active and configured
to allow the remote connection.
to specify a user name that is valid on the target host.
Examine the trace logs for more information. If
necessary, increase the tracing levels to produce more
output in the logs.

Appendix E. Understanding informational, warning, and error messages 183

KUICCN035E • KUICCN040E

input/output problems for this program. If so, schedule

KUICCN035E Unable to connect to host VALUE_0
the node creation at a time when there is less disk
using the provided credentials on the
activity. Also verify that access to the file system being
following protocol(s): VALUE_1.
written to, or read from, has not become compromised.
Explanation: An attempt was made to connect to the On Windows systems, when using non-SSH access, the
target host using the provided credentials, but that administrative share for the drive being used must be
attempt failed. available; for example: C$.
Operator response: Verify that the provided
credentials are valid. For example, if a user name and KUICCN037E The authorization information
password were provided, make sure that the user name provided was rejected by host VALUE_0
is valid on the target host, and that the specified on the following protocol(s): VALUE_1.
password is correct for that user. If you continue to
Explanation: An authorization error occurred while
have problems, consider trying alternate connection
attempting to connect to the target host. The provided
approaches if possible, such as SSH.
credentials might not be valid.
Examine the trace logs for more information. If
Operator response: Provide authorization credentials
necessary, increase the tracing levels to produce more
that are valid for the host being targeted. The means of
output in the logs.
providing the valid authorization credentials are:
Administrator Response: Ensure that the access --username=<LOGIN_ID>, --password=<PASSWORD>
method being used is appropriate for the target host. or <PASSWORD_FILE>,
For example, if a user name and password were used, --keyfile=<SSH_PRIVATE_KEY_FILE> and
ensure that user account exists on the host, and uses --passphrase=SSH_PASSPHRASE, if you provided a
the specified password. If SSH was used, ensure the passphrase. If you have provided a user name, but no
SSH daemon or service is running on the target host. If password, the program interactively prompts you for
SSH was used with a key file approach, ensure the key your password.
being used is valid and has been properly added to the
authorized_keys KUICCN038E A failure occurred while attempting
to connect to host VALUE_0 on the
file for the user account on the target host. following protocol(s): VALUE_1.

In general, this program needs some form of access to Explanation: An unrecognized connection error
the target host(s) in order to establish a connection and occurred with the target host.
be successful. If sufficient security measures are in Operator response: Review all of the options provided
place, they can block this program’s access, too. Verify to this program and verify that they are all valid and
that any intervening firewalls are configured in a accurate. Examine the trace logs to determine if any
manner that allows this program to be successful by more information is available. Consider increasing the
one of its available communication protocols, for tracing level, then trying to connect again. This should
example, SMB, SSH, REXEC, RSH. It is equally maximize log information.
important that these services be active, and configured
to allow the remote connection. Administrator Response: Verify that the protocol(s)
being used to access the target system are active and
Examine the trace logs for more information. If available. Ensure that there are no firewall restrictions
necessary, increase the tracing levels to produce more blocking this program.
output in the logs.
KUICCN039I Attempting to connect to host VALUE_0
KUICCN036E A communication failure occurred ...
with host VALUE_0 on the following Explanation: No additional information is available
protocol(s): VALUE_1. for this message.
Explanation: An input/output error occurred with or
on the remote host. This is most often the result of KUICCN040E The IP address of host VALUE_0 was
some type of file read/write error. not resolved.
Operator response: Try the operation again in a few Explanation: The specified target host could not be
minutes. These types of problems can be caused by an resolved on the network.
abundance of disk activity on the target host. If that
activity is given enough time to subside, the Operator response: Verify that the specified host was
input/output problems might disappear. typed correctly. If an IP address was specified, be
aware that only IPv4 addresses are currently supported.
Administrator Response: Determine if there is a lot of
disk activity on the target host that can be causing Administrator Response: Verify that there are no

184 IBM Tivoli Monitoring: Problem Determination Guide

 KUICCN041E • KUICCN046E

problems with the network, such as any name servers this case, the error occurred while the operating system
that might be in use. Check the hosts file and verify information for the target host was being retrieved.
that it is correctly populated. Verify that the local
Operator response: Try the operation again in a few
network settings are correct and valid. For example, on
minutes. Connection errors are typically temporary.
UNIX systems this might mean checking the contents
of the Administrator Response: Verify that local security
/etc/resolv.conf settings on the target host are not interfering with the
connection. Verify that the network is working
file. On Windows systems, check the TCP/IP settings. correctly, and that a firewall is not adding errors.
Connection errors are typically temporary, so persistent
occurrences can be a sign of a reliability issue
KUICCN041E The IP address of the local host was somewhere in the system.
not resolved.
Explanation: The local host’s name could not be KUICCN045E An error occurred that resulted in a
resolved on the network. bad or missing agent file on host
Administrator Response: Verify that there are no VALUE_0.
problems with the network, such as any name servers Explanation: While distributing the agent installation
that might be in use. Check the hosts file and verify image to the target host, an error occurred that resulted
that it is correctly populated. Verify that the local in one or more missing files. Without a complete
network settings are correct and valid. For example, on installation image on the target host, this operation can
UNIX systems, this might mean checking the contents not continue.
of the
Operator response: Try the operation again in a few
/etc/resolv.conf
minutes. This type of error is most often the result of
either a connection error or an input/output error. Both
file. On Windows systems, check the TCP/IP settings. of these errors are typically temporary.
Administrator Response: Verify that local security
KUICCN042E Current Java security settings do not settings on the target host are not interfering with the
allow the host name of the local host to connection. Verify that the network is working
be determined. correctly, and that a firewall is not adding errors.
Explanation: The current security settings for the Java Determine if there is a lot of disk activity on the target
virtual machine being used to run this program do not host that can be causing input/output problems for this
allow the local host’s name to be resolved. program. If so, schedule the node creation at a time
Administrator Response: Modify the security settings when there is less disk activity. Also verify that access
for the Java virtual machine to allow host name to the file system being written to, or read from, has
lookups. This typically requires modification of the not become compromised. On Windows systems, when
checkConnect settings. using non-SSH access, the administrative share for the
drive being used must be available; for example, C$.

KUICCN043E Current Java security settings do not These types of errors are typically temporary, so
allow the host name of the target host to persistent occurrences can be a sign of a reliability issue
be determined. somewhere in the system.

Explanation: The current security settings for the Java

virtual machine being used to run this program do not KUICCN046E An input/output failure occurred with
allow the target host’s name to be resolved. host VALUE_0 during the distribution of
the agent installation image.
Administrator Response: Modify the security settings
for the Java virtual machine to allow host name Explanation: An input/output error occurred with or
lookups. This typically requires modification of the on the remote host. This is most often the result of
checkConnect settings. some sort of file read/write error. This error means that
the agent installation image can not be trusted.

KUICCN044E A connection error occurred while Operator response: Try the operation again in a few
attempting to obtain the type of the minutes. These types of problems are sometimes caused
operating system on host VALUE_0. by an abundance of disk activity on the target host. If
that activity is given enough time to subside, the
Explanation: Connection errors can occur at any time, input/output problems might disappear.
and typically result from a socket or port error
occurring on the remote host, but occasionally can Administrator Response: Determine if there is a lot of
occur due to a network interruption of some kind. In disk activity on the target host that can be causing
input/output problems for this program. If so, schedule

Appendix E. Understanding informational, warning, and error messages 185

KUICCN047E • KUICCN052E

the node creation at a time when there is less disk occurring on the remote host, but occasionally can
activity. Also verify that access to the file system being occur due to a network interruption of some kind. In
written to, or read from, has not become compromised. this case, the error occurred while the updated silent
On Windows systems, when using non-SSH access, the installation response file was being distributed to the
administrative share for the drive being used must be target host.
available; for example, C$.
Operator response: Try the operation again in a few
minutes. Connection errors are typically temporary.
KUICCN047E A connection error occurred while
Administrator Response: Verify that local security
distributing the updated silent
settings on the target host are not interfering with the
installation responses file to host
connection. Verify that the network is working
VALUE_0.
correctly, and that a firewall is not adding errors.
Explanation: Connection errors occur at any time, and Connection errors are typically temporary, so persistent
typically result from a socket or port error occurring on occurrences can be a sign of a reliability issue
the remote host, but occasionally can occur due to a somewhere in the system.
network interruption of some kind. In this case, the
error has prevented the modified installation responses
KUICCN050I Distributing file VALUE_0 of
from being made available on the target host.
VALUE_1VALUE_2...
Operator response: Try the operation again in a few
Explanation: No additional information is available
minutes. Connection errors are typically temporary.
for this message.
Administrator Response: Verify that local security
settings on the target host are not interfering with the
KUICCN051E The connection to host VALUE_0 was
connection. Verify that the network is working
lost while the node creation command
correctly, and that a firewall is not adding errors.
was running.
Connection errors are typically temporary, so persistent
occurrences can be a sign of a reliability issue Explanation: Connection errors can occur at any time,
somewhere in the system. and typically result from a socket or port error
occurring on the remote host, but occasionally can
occur due to a network interruption of some kind. In
KUICCN048E An input/output failure occurred with
this case, the error occurred while the installation
host VALUE_0 during the distribution of
program was executing.
the updated silent installation responses
file. Operator response: Try the operation again in a few
minutes. Connection errors are typically temporary.
Explanation: An input/output error occurred with or
on the remote host. This is most often the result of Administrator Response: Verify that local security
some sort of file read/write error. This error has settings on the target host are not interfering with the
prevented the modified installation responses from connection. Verify that the network is working
being made available on the target host. correctly, and that a firewall is not adding errors.
Connection errors are typically temporary, so persistent
Operator response: Try the operation again in a few
occurrences can be a sign of a reliability issue
minutes. These types of problems are sometimes caused
somewhere in the system.
by an abundance of disk activity on the target host. If
that activity is given enough time to subside, the
input/output problems might disappear. KUICCN052E The installation file was not found on
host "VALUE_0".
Administrator Response: Determine if there is a lot of
disk activity on the target host that can be causing Explanation: The executable file that is needed to
input/output problems for this program. If so, schedule invoke the agent installation was not found on the
the node creation at a time when there is less disk target host.
activity. Also verify that access to the file system being
written to, or read from, has not become compromised. Administrator Response: Verify that the needed file
On a Windows system, when using non-SSH access, the actually exists in the source depot image, and is
administrative share for the drive being used must be defined in the appropriate descriptor file. On Windows
available; for example, C$. systems, this file is typically
setup.exe
KUICCN049E The connection to host "VALUE_0"
, and on UNIX systems, the file is
was lost during the agent installation
response file distribution. install.sh

Explanation: Connection errors can occur at any time,

and typically result from a socket or port error

186 IBM Tivoli Monitoring: Problem Determination Guide

 KUICCN053E • KUICCN059E

. If necessary, increase the current trace level, run the

KUICCN056E The node on host VALUE_0 was not
operation again, then examine the trace log to obtain
created. Examine trace log VALUE_1 for
more information.
more details.
Explanation: The installation of the agent stopped on
KUICCN053E An input/output error occurred with
the target host. This is a failure that occurs very early
host VALUE_0 while the node creation
in the installation process, and is indicative of a
command was running.
fundamental problem in the installation, as opposed to
Explanation: An input/output error occurred with or a configuration problem.
on the remote host. This is most often the result of
Operator response: Examine the trace logs to
some type of file read/write error. In this case, the
determine if enough information is available to find the
error occurred while the installation program was
exact cause of the failure. If necessary, increase the
running.
tracing level, then try the installation again. When the
Operator response: Try the operation again in a few cause of the failure has been determined, correct it, and
minutes. These types of problems are sometimes caused perform the installation again.
by an abundance of disk activity on the target host, and
are typically temporary. If that activity is given enough
KUICCN057I The node creation on host VALUE_0
time to subside, the input/output problems might
was successful.
disappear.
Explanation: No additional information is available
Administrator Response: Determine if there is a lot of
for this message.
disk activity on the target host that can be causing
input/output problems for this program. If so, schedule
the node creation at a time when there is less disk KUICCN058E The node on host VALUE_0 was not
activity. Also verify that access to the file system being configured correctly.
written to, or read from, has not become compromised.
Explanation: The installation process is broken down
On a Windows system, when using non-SSH access, the
into three phases:
administrative share for the drive being used must be
available; for example, C$. 1. Install: all files are copied to the appropriate
location
2. Configuration: this includes specifying a protocol, a
KUICCN054E An error occurred on host VALUE_0
server to connect to, and so on
while the node creation command was
running. 3. Launch: the agent is started

Explanation: An unrecognized error occurred with the In this case, the agent might have suffered a failure in
target host during the installation process. The error is the second step, and was not properly configured.
not one of the errors that are most common for this Operator response: Verify that all specified
type of operation. configuration parameters used to create the node are
Operator response: Examine the trace logs to valid. Examine the trace logs to determine if enough
determine if any more information is available. information is available to determine the exact cause of
Consider increasing the tracing level, then trying the the failure. If necessary, increase the tracing level, then
installation again. This should maximize log try the installation again. When the cause of the failure
information. has been determined, correct it, and perform the
installation again.
Administrator Response: Verify that the target system
is still running, and that the network is functioning
normally. KUICCN059E The node on host VALUE_0 did not
launch.

KUICCN055E The node on host VALUE_0 was not Explanation: The installation process is broken down
created. Examine trace log VALUE_1 for into three phases:
more details. 1. Install: all files are copied to the appropriate
location
Explanation: The installation of the agent failed on the
target host. 2. Configuration: this includes specifying a protocol, a
server to connect to, and so on
Operator response: Examine the trace logs to
3. Launch: the agent is started
determine if enough information is available to
determine the exact cause of the failure. If necessary, In this case, the agent might have failed in the third
increase the tracing level, then try the installation again. step, and was not started properly.
When the cause of the failure has been determined,
correct it, and perform the installation again. Operator response: Verify that all specified

Appendix E. Understanding informational, warning, and error messages 187

KUICCN060E • KUICCN067E

configuration parameters used to create the node are the installation image is copied and run.
valid. Examine the trace logs to determine if enough
Administrator Response: Verify that the system
information is available to determine the exact cause of
temporary directory on the target host has write access.
the failure. If necessary, increase the tracing level, then
Verify that the administrative share for the drive
try the installation again. When the cause of the failure
hosting the temporary directory has not been disabled.
has been determined, correct it, and perform the
If it has been disabled, WIN/SMB access is not
installation again.
possible, and an alternate connection protocol is
required. such as SSH.
KUICCN060E The connection to host VALUE_0 was
lost during the retrieval of file VALUE_1.
KUICCN063E A unique, temporary directory in
Explanation: Connection errors can occur at any time, VALUE_1 on host VALUE_0was not
and typically result from a socket or port error created.
occurring on the remote host, but occasionally can
Explanation: This program failed to create a
occur due to a network interruption of some kind. In
temporary working directory on the target host, where
this case, the error occurred while attempting to read a
the installation image is copied and run.
file on the target host and return its contents to this
server. Administrator Response: Check the permissions for
the system temporary directory on the target host.
Operator response: Try the operation again in a few
Verify that it has write access.
minutes. Connection errors are typically temporary.
Administrator Response: Verify that local security
KUICCN064E An appropriate installation image for
settings on the target host are not interfering with the
the target platform, VALUE_0, could not
connection. Verify that the network is working
be found on the local server.
correctly, and that a firewall is not adding errors.
Connection errors are typically temporary, so persistent Explanation: The installation image needed for the
occurrences might be a sign of a reliability issue target host could not be found in the local depot.
somewhere in the system.
Administrator Response: Ensure that the depot has
been populated with all the images necessary to
KUICCN061E An input/output error occurred with support the platforms that are in use.
host VALUE_0 while the node creation
command was running.
KUICCN065I The node creation operation was a
Explanation: An input/output error occurred with or success.
on the remote host. This is most often the result of
some sort of file read/write error. In this case, the error Explanation: No additional information is available
occurred while attempting to read a file on the target for this message.
host and return its contents to this server.
Operator response: Try the operation again in a few KUICCN066E A local, updated copy of the silent
minutes. These types of problems are sometimes caused installation response file template could
by an abundance of disk activity on the target host, and not be created.
are typically temporary. If that activity is given enough Explanation: The template silent installation response
time to subside, the input/output problems might file, located in the depot, is loaded and updated with
disappear. the configuration changes that are needed. as specified
Administrator Response: Determine if there is a lot of by command-line options. These updated response files
disk activity on the target host that can be causing must be copied to a new, temporary file, that can be
input/output problems for this program. If so, schedule distributed to the target host. The creation of this local,
the node creation at a time when there is less disk temporary file failed.
activity. Also verify that access to the file system being Administrator Response: Check the local system
written to, or read from, has not become compromised, temporary directory and verify that write permission is
On Windows systems, when using non-SSH access, the in place to allow this program to create files.
administrative share for the drive being used must be
available; for example, C$.
KUICCN067E The specified SSH private key file can
not be used.
KUICCN062E A unique, temporary directory
inVALUE_1 on host VALUE_0was not Explanation: The SSH key file specified for use in
created. connecting to the target machine is unusable. Examine
the trace log for more information. The most probable
Explanation: This program failed to create a causes are that the file does not exist, or that its
temporary working directory on the target host, where

188 IBM Tivoli Monitoring: Problem Determination Guide

 KUICCN068E • KUICCN104E

permissions do not allow it to be opened and read. Administrator Response: Verify that the appropriate
environment variable that is specific for your system is
Operator response: Verify that the location of the SSH
correctly set by default on the server to indicate the
key file was typed correctly, and that it exists in the
primary installation location of IBM Tivoli Monitoring.
specified location. Verify that the permissions on the
Currently, the variables that are used are
file allow it to be accessed by the user account where
CANDLEHOME on UNIX and Linux systems, and
you are currently logged in.
CANDLE_HOME on Windows systems.

KUICCN068E The node creation operation did not

KUICCN103E The server installation location
complete within the specified time limit
indicated by the candlehome environment
of VALUE_0 seconds. The time limit was
variable does not exist: envval.
exceeded while VALUE_1.
Explanation: The primary location of an IBM Tivoli
Explanation: The maximum amount of time allotted
Monitoring server is indicated by an environment
for this node creation operation was exceeded before
variable that is specific to your system. Currently, this
the operation completed.
is CANDLEHOME on UNIX and Linux systems, and
Operator response: Increase the time limit by using CANDLE_HOME on Windows systems. This variable
the was set incorrectly on this server.
--option Operator response: Correct the appropriate
environment variable that is specific to your system,
flag with the indicating the primary installation location of this
timeout server. Currently, the variables that are used are
CANDLEHOME on UNIX and Linux sysgtems, and
option. For example, CANDLE_HOME on Windows systems.
--option timeout=3600 Administrator Response: Verify that the appropriate
environment variable that is specific to your system is
. The timeout value represents the maximum number correctly set by default on the server to indicate the
of seconds allowed for the current node creation primary installation location of IBM Tivoli Monitoring.
operation to continue. Currently, the variables that are used are
CANDLEHOME on UNIX and Linux systems, and
CANDLE_HOME on Windows systems.
KUICCN069E The agent was not created because the
prerequisite product code product_code
version version was not found in the KUICCN104E The server installation location
depot. indicated by the candlehome environment
variable does not appear to be a
Explanation: All required prerequisites must exist in directory: envval.
the depot before you can create a new agent using the
tacmd createnode command. Explanation: The primary location of an IBM Tivoli
Monitoring server is indicated by an environment
Administrator Response: Run the installation again, variable that is specific to your system. Currently, that
selecting the specified product to be packaged for is CANDLEHOME on UNIX and Linux systems, and
deployment. Then create the new agent using the CANDLE_HOME on Windows systems. This variable
tacmd createnode command. was set incorrectly on this server, and is not referencing
a directory.
KUICCN102E The candlehome environment variable Operator response: Correct the appropriate
must be set before running this environment variable that is specific to your system,
command. indicating the primary installation directory of this
Explanation: The primary location of an IBM Tivoli server. Currently, the variables that are used are
Monitoring server is indicated by an environment CANDLEHOME on UNIX and Linux systems, and
variable that is specific to your system. Currently, this CANDLE_HOME on Windows systems.
is CANDLEHOME on UNIX and Linux systems, and Administrator Response: Verify that the appropriate
CANDLE_HOME on Windows systems. This variable is environment variable that is specific to your system is
not set on the current server. correctly set by default on the server to indicate the
Operator response: Establish the appropriate primary installation directory of IBM Tivoli Monitoring.
environment variable that is specific for your system, Currently, the variables that are used are
indicating the primary installation location of this CANDLEHOME on UNIX and Linux systems, and
server. Currently, the variables that are used are CANDLE_HOME on Windows systems.
CANDLEHOME on UNIX and Linux systems, and
CANDLE_HOME on Windows systems.

Appendix E. Understanding informational, warning, and error messages 189

KUICCN105E • KUICCP009I

KUICCN105E The location of the jar files directory KUICCN108E The path to the DEPOTHOME
needed by createNode could not be directory was not found.
found: envval.
Explanation: The specified value of the DEPOTHOME
Explanation: Several jar files are needed by variable was not found.
createNode, and are expected to be found in a specific
Operator response: Verify the location of the depot
location on each server. However, that location could
and specify the correct location as the value for
not be found on this server.
DEPOTHOME in the KBBENV file.
Administrator Response: Locate the
Administrator Response: Verify the location of the
jars depot and specify this location as the value for
DEPOTHOME in the KBBENV file.
directory on the server that contains
createnode.jar
KUICCP001E KUICCP001E: Incorrect syntax. The
-p|--property cannot be specified with
, along with several other jar files. Copy that directory the -r|--remove option.
and all of its contents to the expected location. This
location varies by system as follows: Explanation: No additional information is available
v On UNIX/Linux systems: for this message.
$CANDLEHOME/platform/kui/jars/
v On Windows systems: KUICCP002E KUICCP002E: Incorrect syntax. The
%CANDLE_HOME%\CLI\jars\ -p|--property option must be specified
unless the -r|--remove option is
specified.
KUICCN106E The required jar file, jarfile, could not
be found in the expected location. Explanation: No additional information is available
for this message.
Explanation: Several jar files are needed by
createNode, and are expected to be found in a specific
location on each server. However, that location is KUICCP003E KUICCP003E: Incorrect syntax. The
missing at least one of the expected jar files on this -s|--datasource option must be
server. specified.
Administrator Response: Locate the Explanation: No additional information is available
jars for this message.

directory on the server and verify that it contains all of KUICCP007I KUICCP007I: The portal server
the required jar files. Perform a search on the server for configuration file CONFIGFILE was
the referenced missing jar file, then copy it to the updated to remove the DATASOURCE
appropriate location. datasource.
v On UNIX/Linux systems: Explanation: No additional information is available
$CANDLEHOME/platform/kui/jars/ for this message.
v On Windows systems:
%CANDLE_HOME%\CLI\jars\
KUICCP008E KUICCP008E: An error occurred while
attempting to remove the DATASOURCE
KUICCN107E The path for DEPOTHOME depotHome datasource from the portal server
was not found. configuration file CONFIGFILE. The
datasource does not exist.
Explanation: The specified path to the depot is
incorrect or does not exist . Explanation: No additional information is available
for this message.
Operator response: If the variable DEPOTHOME was
specified within the KBBENV file then change the
value of this variable to correct path to the depot. If KUICCP009I KUICRA009: Are you sure you want to
DEPOTHOME was not specified within KBBENV file, remove the DATASOURCE datasource
call IBM Support. from the portal server configuration file
CONFIGFILE ?
Administrator Response: If the variable
Enter Y for yes or N for no:
DEPOTHOME was specified within the KBBENV file,
change the value of DEPOTHOME to correct path to Explanation: No additional information is available
the depot. If DEPOTHOME was not specified within for this message.
KBBENV file, call IBM Support.

190 IBM Tivoli Monitoring: Problem Determination Guide

 KUICCP010I • KUICCP020E

Enter Y for yes or N for no:

KUICCP010I KUICCP010I: The DATASOURCE
datasource in the portal server Explanation: No additional information is available
configuration file CONFIGFILE was for this message.
updated with the following properties:
PROPERTIES
KUICCP016E KUICCP016E: RESPONSE is not a
Explanation: No additional information is available correct response. Enter Y for yes or N
for this message. for no:
Explanation: No additional information is available
KUICCP011E KUICCP011E: An error occurred while for this message.
attempting to update the DATASOURCE
datasource from the portal server
configuration file CONFIGFILE. KUICCP017E KUICCP017E: An error occurred while
attempting to create the DATASOURCE
Explanation: The datasource was not updated because datasource in the portal server
the configuration file could not be written. configuration file CONFIGFILE.
Operator response: Ensure that the file permissions Explanation: The datasource was not created because
for the configuration file allow it to be written and that the configuration file already contains the maximum
there is adequate disk space available. Then run the number of datasource entries.
command again.
Operator response: Delete one or more datasources
and run the command again, or modify an existing
KUICCP012I KUICRA012: Are you sure you want to datasource instead of creating a new one.
update the DATASOURCE datasource in
the portal server configuration file
DIRECTORY with the following KUICCP018E KUICCP018E: The command could not
properties? execute on the local system because the
PROPERTIES ENVVARNAME environment variable is
Enter Y for yes or N for no: not set.

Explanation: No additional information is available Explanation: No additional information is available

for this message. for this message.

KUICCP013I KUICCP013I: The DATASOURCE KUICCP019E KUICCP019E: An error occurred while

datasource in the portal server attempting to remove the DATASOURCE
configuration file CONFIGFILE has been datasource from the portal server
created with the following properties: configuration file CONFIGFILE.
PROPERTIES Explanation: The datasource could not be removed
Explanation: No additional information is available because the configuration file could not be written.
for this message. Operator response: Ensure that the file permissions
for the configuration file allow it to be written and that
KUICCP014E KUICCP014E: An error occurred while there is adequate disk space available, then run the
attempting to create the DATASOURCE command again.
datasource from the portal server
configuration file CONFIGFILE. KUICCP020E KUICCP020E: The command could not
Explanation: The datasource was not created because execute on the local system because the
the configuration file could not be written. CONFIGFILE configuration file could
not be read.
Operator response: Ensure that the file permissions
for the configuration file allow it to be written and that Explanation: The configuration file could not be
there is adequate disk space available, then run the opened for reading.
command again. Operator response: Ensure that the configuration file
exists in the specified location and the attributes for the
KUICCP015I KUICRA015: Are you sure you want to file allow it to be read.
create the DATASOURCE datasource in
the portal server configuration file
CONFIGFILE with the following
properties?
PROPERTIES

Appendix E. Understanding informational, warning, and error messages 191

KUICCP021E • KUICCP033E

KUICCP021E KUICCP021E: Incorrect Syntax. The KUICCP028I KUICRA028: Are you sure you want to
property PROPERTY is malformed. update the DATASOURCE datasource in
the portal server configuration file
Explanation: Properties must be in the form
DIRECTORY and the Windows Registry
KEY=VALUE to add or update the property, or KEY=
with the following properties?
to remove the property.
PROPERTIES
Operator response: Specify the property using the Enter Y for yes or N for no:
correct syntax and run the command again.
Explanation: No additional information is available
for this message.
KUICCP022I KUICCP022I: The DATASOURCE
datasource in the portal server
KUICCP029I KUICCP029I: The DATASOURCE
configuration file CONFIGFILE was not
datasource in the Windows Registry has
updated because no changes to the
been created with the following
existing configuration were necessary.
properties:
Explanation: No additional information is available PROPERTIES
for this message.
Explanation: No additional information is available
for this message.
KUICCP023I KUICCP023I: The Windows Registry
was updated to remove the
KUICCP030E KUICCP030E: An error occurred while
DATASOURCE datasource.
attempting to create the DATASOURCE
Explanation: No additional information is available datasource in the Windows Registry.
for this message.
Explanation: The datasource was not created because
the Windows Registry could not be written.
KUICCP024E KUICCP024E: An error occurred while
Operator response:
attempting to remove the DATASOURCE
datasource from the Windows Registry.
The datasource does not exist. KUICCP031I KUICRA031: Are you sure you want to
create the DATASOURCE datasource in
Explanation: No additional information is available
the portal server configuration file
for this message.
DIRECTORY and the Windows Registry
with the following properties?
KUICCP025I KUICRA025: Are you sure you want to PROPERTIES
remove the DATASOURCE datasource Enter Y for yes or N for no:
from the from the portal server
Explanation: No additional information is available
configuration file CONFIGFILE and the
for this message.
Windows Registry?
Enter Y for yes or N for no:
KUICCP032I KUICCP032I: The DATASOURCE
Explanation: No additional information is available
datasource in the portal server
for this message.
configuration file CONFIGFILE and the
Windows Registry was not updated
KUICCP026I KUICCP026I: The DATASOURCE because no changes to the existing
datasource in the Windows Registry was configuration were necessary.
updated with the following properties:
Explanation: No additional information is available
PROPERTIES
for this message.
Explanation: No additional information is available
for this message.
KUICCP033E KUICCP033E: An error occurred while
attempting to remove the DATASOURCE
KUICCP027E KUICCP027E: An error occurred while datasource from the Windows Registry.
attempting to update the DATASOURCE
Explanation: No additional information is available
datasource in the Windows Registry.
for this message.
Explanation: The datasource was not updated because
the Windows Registry could not be written.
Operator response:

192 IBM Tivoli Monitoring: Problem Determination Guide

 KUICCP034E • KUICCR007I

2. Run the configuresystem command again to

KUICCP034E KUICCP034E: An error occurred while
configure the manage system.
attempting to create the DATASOURCE
datasource in the Windows Registry.
KUICCR003E KUICCR003E: The managed system
Explanation: The datasource was not created because
MANAGEDSYSTEM was not found by
the Windows Registry already contains the maximum
server the HOST.
number of datasource entries.
Explanation: The specified managed system was not
Operator response: Delete one or more datasources
configured because the server did not find it.
and run the command again, or modify an existing
datasource instead of creating a new one. Operator response: Run the following listSystems
command to list the existing managed systems in the
node:
KUICCP035E KUICCP035E: An error occurred while
tacmd listSystems [{{-n|--node} MANAGED-OS} |
attempting to retrieve the DATASOURCE
{{-d|--dir|--directory} NODEDIR}]
datasource from the portal server
configuration file CONFIGFILE. The
datasource does not exist. KUICCR004E KUICCR004E: The managed system
was not configured because
Explanation: No additional information is available
configuration parameters were not
for this message.
specified.
Explanation: You must specify configuration
KUICCP036E KUICCP036E: Incorrect syntax. The
parameters with he -p option when running the
-v|--view option cannot be used with
configuresystem command.
the -f|--force, -r|--remove, or
-p|--property|--properties options. Operator response: Include the -p option to specify
configuration parameters when you run the
Explanation: No additional information is available
configuresystem command again.
for this message.

KUICCR005E KUICCR005E: Are you sure you want

KUICCP099E KUICCP099E: The command did not
to update the management configuration
complete because of a system error.
for MANAGEDSYSTEM from the
Refer to the log for details and contact
FILENAME file? Enter Y for yes or N for
the system administrator.
no:
Explanation: No additional information is available
Explanation: No additional information is available
for this message.
for this message.

KUICCR001E KUICCR001E: The configuresystem

KUICCR005E KUICCR005E: The base situation
command did not complete because a
sitname does not exist on server on
managed system was not specified.
host_name.
Explanation: You must run the use the
Explanation: The specified base situation does not
configuresystem command with the -m option to
exist on server to create a new situation.
specify a managed system name.
Operator response: Specify an existing base situation
Operator response: Run the listSystems command to
on the server and try the operation again.
view a list of managed systems.

KUICCR006I KUICCR006I: The management

KUICCR002E KUICCR002E: The configuresystem
configuration for MANAGEDSYSTEM
command did not complete because you
was updated.
are not logged in.
Explanation: No additional information is available
Explanation: You must login to the server from which
for this message.
you want to run the configuresystem command.
Operator response:
KUICCR007I KUICCR007: Are you sure you want to
1. Use the following command to login: update the management configuration
tacmd login {-s|--server} for MANAGEDSYSTEM with the given
{[PROTOCOL://]HOST[:PORT]} property values? Enter Y for yes or N
[{-u|--username} USERNAME [{-p|--password} for no:
PASSWORD]] [{-t|--timeout} TIMEOUT]

Appendix E. Understanding informational, warning, and error messages 193

KUICCR008I • KUICCS001E

Explanation: No additional information is available

KUICCR016E KUICCR016E: RESPONSE is not a
for this message.
valid response. Enter Y for yes or N for
no:
KUICCR008I KUICCR008I: The management
Explanation: No additional information is available
configuration for MANAGEDSYSTEM
for this message.
was updated.
Explanation: No additional information is available
KUICCR017E KUICCR017E: MANAGEDSYSTEM
for this message.
could not be configured, either because
it is offline or because the node that
KUICCR009E KUICCR009E: The node manages it is offline, not installed, or
MANAGEDSYSTEM cannot be not configured to use the server that you
configured because nodes are not are logged into. Ensure that both the
configurable. agent and its managing node are online,
and run the command again.
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KUICCR010I KUICCR010I: Configuring
MANAGEDSYSTEM KUICCR018E KUICCR018E: The property PARAM is
not a valid configuration property.
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KUICCR011E KUICCR011E: UACONFIG is a
required parameter to configure a KUICCR019E KUICCR019E: The INSTANCE
Universal Agent. property cannot have an empty value.
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KUICCR012E KUICCR012E: The value of the KUICCR020E KUICCR020E: The configureSystem

RESTART parameter must be Y or N. command did not complete because an
error occurred. Refer to the following
Explanation: No additional information is available error returned from the server:
for this message.
Explanation: No additional information is available
for this message.
KUICCR013E KUICCR013E: The parameter PARAM
is not a valid parameter for Universal
Agent configuration. KUICCR099E KUICCR099E: The configuresystem
command cannot complete because a
Explanation: No additional information is available system error occurred.
for this message.
Explanation: An unexpected system error occurred.
KUICCR014I KUICCR014I: Configuring agent Operator response: Refer to the log file for more
MANAGEDSYSTEM. information and contact the system administrator.
Explanation: No additional information is available
for this message. KUICCS001E KUICCS001E: The situation was not
created because -b BASENAME was not
specified.
KUICCR015E KUICCR015E: KEYNAME is not a valid
key name. Key names must be Explanation: You must specify the -b BASENAME
qualified. option when you create a situation.
Explanation: No additional information is available Operator response: Specify -b BASENAME.
for this message.

194 IBM Tivoli Monitoring: Problem Determination Guide

 KUICCS002E • KUICCS018E

running the command again.

KUICCS002E KUICCS002E: The command did not
complete because the -p parameter was
not specified correctly. KUICCS009E KUICCS009E: The situation was not
created because sitname already exists on
Explanation: You must specify the -p option with one
the server host_name.
or more NAME=VALUE pairs.
Explanation: You specified the name of an already
Operator response: Specify -p with one or more
existing situation. The new situation name must be
NAME=VALUE pairs and try the operation again.
unique on the server.
Operator response: Specify a new situation name that
KUICCS003E KUICCS003E: You are not logged in.
does not already exists on the specified server and try
Explanation: You must log in with the login command creating the new situation again.
before running the createsit command.
Operator response: Log in to the server and try KUICCS010I KUICCS010I: The situation sit_name was
running the command again. created on the server on host_name.
Explanation: No additional information is available
KUICCS004E KUICCS004E: The situation sitname for this message.
already exists on host_name server.
Explanation: The specified situation already exists on KUICCS015E KUICCS015E: The situation was not
server. created because you attempted to
specify situation properties when
Operator response: Specify a new situation name and
importing a situation definition.
try the operation again.
Explanation: When creating situations by importing
situation definitions with the -i option, you cannot
KUICCS005I KUICCS005I: The situation sit_name was
specify situation properties with the -p option.
created on the server on host_name.
Operator response: Run the following command to
Explanation: No additional information is available
create a situation by importing definitions:
for this message.
tacmd createsit {-i | import} FILENAME]

KUICCS006E KUICCS006E: The situation was not

KUICCS016E KUICCS016E: The specified value for
created because you did not specify
the property INTERVAL is incorrect.
either the -s or the -i option.
Specify a correct value for INTERVAL in
Explanation: You must specify a new situation name the following format with positive
or the name of an existing situation when creating a numbers: XXX/XXXXXX
situation.
Explanation: No additional information is available
Operator response: Specify the -s option for a new for this message.
situation or the -i option to import a situation
definition and try the creating the situation again.
KUICCS017E KUICCS017E: The situation was not
created because the file file_name was
KUICCS007E KUICCS007E: The situation was not not processed.
created because the import file specified
Explanation: The file you specified for importing
is incorrect.
situation definitions was not processed because it
Explanation: The file you specified from which to contains incorrect data.
import situation definitions has incorrect data or the
Operator response: Verify that the file contains correct
file does not exist.
data and try creating the situation again.
Operator response: Verify the import file name and
that it contains correct data and try to create the
KUICCS018E KUICCS018E: The situation sit_name
situation again.
was not created.
Explanation: You attempted to create a situation with
KUICCS008E KUICCS008E: You are not logged in.
incorrect data in the input fields.
Explanation: You must log in with the login command
Operator response: Specify the correct data for the
before running createsit command.
input fields and try creating the situation again.
Operator response: Log in to the server and try

Appendix E. Understanding informational, warning, and error messages 195

KUICCS019E • KUICDR005E

KUICCS019E KUICCS019E: The specified property KUICDR001E KUICDR001E: The describesystemtype

name is incorrect. command did not complete because the
agent type was not specified.
Explanation: A new situation can not be created with
an incorrect property name. Explanation: You must specify the managed system
type you want to update. The manage system type is
Operator response: Specify a correct property name.
specified by a 2 character string.
Examples include:
DESC/DESCRIPTION Operator response: Run the viewDepot command to
INTERVAL list managed system types. Verify the manage system
FORMULA and specify the agent type with the -t or --type option
DISTRIBUTION when running the describesystemtype command again.
ADVICE
ACTION
KUICDR002E KUICDR002E: The describesystemtype
RUNONSTART
command did not complete because you
are not logged in.
KUICCS022E KUICCS022E: The specified value for
Explanation: You must login to the server from which
the FORMULA property is incorrect.
you want to run the describesystemtype command.
Explanation: You must specify a value for the
Operator response:
FORMULA property when creating a new situation.
1. Use the following command to login:
Operator response: Specify a correct value for tacmd login {-s|--server}
FORMULA. {[PROTOCOL://]HOST[:PORT]}
[{-u|--username} USERNAME [{-p|--password}
KUICCS023E KUICCS023E: The specified value for PASSWORD]]
the ACTION property is incorrect. [{-t|--timeout} TIMEOUT]
2. Run the describesystemtype command again.
Explanation: A new situation can not be created with
no value for the ACTION property.
KUICDR003E KUICDR003E: The describesystemtype
Operator response: Specify a correct value for
command did not complete.
ACTION.
Explanation: You must specify the -h option with the
describesystemtype command.
KUICCS024E KUICCS024E: The specified value for
the RUNONSTART property is Operator response: Specify the -h option when you
incorrect. run the describesystemtype command again.
Explanation: A new situation can not be created with
incorrect value for the RUNONSTART property. KUICDR004E KUICDR004E: The describesystemtype
command did not complete.
Operator response: Specify YES or NO as the value
for the RUNONSTART property. Explanation: You can only run the describesystemtype
from a Tivoli Enterprise Monitoring Server that
contains a depot.
KUICCS025I KUICCS025I: The situation name was
truncated to 31 characters. Operator response: Run the describesystemtype from
a Tivoli Enterprise Monitoring Server that contains a
Explanation: No additional information is available
depot.
for this message.

KUICDR005E KUICDR005E: The depot does not

KUICCS099E KUICCS099E: The situation was not
contain a package for the TYPE product
created because an error occurred.
type.
Explanation: An unexpected system error occurred.
Explanation: You must specify a managed system
Administrator Response: Refer to the log for details with the -t or --type when running the
about the error. Correct the error and try the operation describesystemtype command.
again or contact system administrator.
Operator response: Run the following viewDepot
command to list the contents of the depot:
tacmd viewDepot [ {{-i|--imagePath} IMAGEPATH} |
{{-j|--depot} DEPOT}]

196 IBM Tivoli Monitoring: Problem Determination Guide

 KUICDR006E • KUICES004I

KUICDR006E KUICDR006E: The depot does not KUICDS002E KUICDS002E: The command did not
contain the PLATFORM platform in the complete because you are not logged in.
TYPE package. Run the following
Explanation: You must log in to run the specified
viewDepot command to list the contents
command.
of the depot:
tacmd viewDepot [ {{-i|--imagePath} Operator response: Log in with the correct user name
IMAGEPATH} | {{-j|--depot} DEPOT}] and password and run the command again.
Explanation: No additional information is available
for this message. KUICDS003E KUICDS003E: The situation sitname
does not exist on server server.
KUICDR007E KUICDR007E: The depot does not Explanation: The specified situation was not found on
contain versions for the PLATFORM the server because it does not exist or the name was
platform in the TYPE package. Run the misspelled.
following viewDepot command to list
the contents of the depot: Operator response: Verify the correct spelling of the
tacmd viewDepot [ {{-i|--imagePath} situation name and try to delete it again.
IMAGEPATH} | {{-j|--depot} DEPOT}]
Explanation: No additional information is available KUICDS004I Are you sure you want to delete the
for this message. situation sitname? Type Y for yes. Type
N for no.

KUICDR008E KUICDR008E: The depot does not Explanation: No additional information is available
contain the VERSION version for the for this message.
PLATFORM platform in the TYPE
package. Run the following viewDepot KUICDS005I KUICDS005I: The situation sitname was
command to list the contents of the deleted from the server name.
depot:
tacmd viewDepot Explanation: No additional information is available
[ {{-i|--imagePath} IMAGEPATH} | for this message.
{{-j|--depot} DEPOT}]
Explanation: No additional information is available KUICES001E KUICES001E: An error occurred because
for this message. the -p option was not specified.
Explanation: The -p parameter must be specified with
KUICDR009I KUICDR009I: The latest version of the one or more NAME=VALUE pairs.
PLATFORM platform in the TYPE Operator response: Specify -p with one or more
package does not contain configuration name=value pairs.
information or the package is corrupt.
Explanation: No additional information is available KUICES002E KUICES002E: You must the login before
for this message. running this command.
Explanation: No additional information is available
KUICDR010I KUICDR010I: The version VERSION for this message.
of the PLATFORM platform in the TYPE
package contains does not contain
configuration information or the KUICES003E KUICES003E: Situation sitname does not
package is corrupt. exist on server on host_name. Specify a
situation name that exists on the server.
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.

KUICDS001E KUICDS001E: The situation was not

deleted because the situation name was KUICES004I Are you sure you want to update the
not specified. sit_name situation? ( Y - yes or N - no):

Explanation: You must specify the name of the Explanation: No additional information is available
situation you want to delete. for this message.

Operator response: Specify the situation name with

the -s SITNAME to delete the situation.

Appendix E. Understanding informational, warning, and error messages 197

KUICES005I • KUICKA002E

Explanation: No additional information is available

KUICES005I KUICES005I: The situation sit_name was
for this message.
updated on server host_name .
Explanation: No additional information is available
KUICES020I Enter Y for yes or N for no:
for this message.
Explanation: No additional information is available
for this message.
KUICES006E KUICES006E: You must specify either
the a -s or the -l option.
KUICES022E KUICES022E: An incorrect value was
Explanation: No additional information is available
specified for property FORMULA.
for this message.
Provide a correct value for FORMULA.
Explanation: No additional information is available
KUICES007E KUICES007E: The specified situation
for this message.
definition in the file is incorrect. Check
the definition of the situation in the
file. KUICES023E KUICES023E: An incorrect value for
property ACTION was specified.
Explanation: No additional information is available
Provide a correct value for ACTION.
for this message.
Explanation: No additional information is available
for this message.
KUICES008I KUICES008I: The situation definition in
file_name was updated.
KUICES024E KUICES024E: An incorrect value for
Explanation: No additional information is available
property RUNONSTART was specified.
for this message.
Specify either YES or NO as value for
RUNONSTART.
KUICES009E KUICES009E: Situation sit_name was not
Explanation: No additional information is available
updated because a system error
for this message.
occurred.
Explanation: Incorrect data for the input fields was
KUICES099E KUICES099E: The command did not
specified.
complete because of a system error.
Operator response: Provide appropriate data for the Check the logs and contact the system
input fields. administrator.
Explanation: No additional information is available
KUICES010E KUICES010E: The file file_name was not for this message.
processed because it contains incorrect
data. Correct the contents of the file and
KUICKA001E KUICKA001E: The stopagent
try again.
command did not complete because you
Explanation: No additional information is available are not logged in.
for this message.
Explanation: You must log in before running the
stopagent with the -n option.
KUICES016E KUICES016E: An incorrect value was
Operator response: Log in with the login command
specified for the property INTERVAL.
and run the stopagent command again, specifying the
Provide a correct value for INTERVAL
-n option.
in XX/XXXXXX format with no negative
numbers.
KUICKA002E KUICKA002E: The stopagent
Explanation: No additional information is available
command did not complete because
for this message.
required options were not specified.
Explanation: In order to use the -n|--node option
KUICES019E KUICES019E: An incorrect property
when stopping the agent from the command line, you
name was specified. Provide the correct
must also use the -t|--type option.
property name, for example,
DESC/DESCRIPTION, INTERVAL, Operator response: Run the stopagent command
FORMULA, again, specifying one or more agent type(s) with the
DISTRIBUTION,ADVICE,ACTION, or -t|--type option, and specifying a node with the
RUNONSTART. -n|--node option.

198 IBM Tivoli Monitoring: Problem Determination Guide

 KUICKA003E • KUICKA019E

KUICKA003E KUICKA003E: You must log in with KUICKA013E KUICKA013E: The agent product code
the login command before using the -n PRODUCTCODE is not known by server
option. on HOST.
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KUICKA004E KUICKA004E: Node NODE is not KUICKA014I KUICKA014I: The AGENTCODE agent
known by the server on HOST. Use the managing system(s)
listSystems command to view a list of MANAGEDSYSTEMLIST is already
known managed systems. stopped.
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KUICKA005E KUICKA005E: The managed system KUICKA015I KUICKA015I: All AGENTCODE agents
MANAGEDSYSTEM is not known by the on the local system were stopped.
server on HOST. Use the listSystems
Explanation: No additional information is available
command to view a list of known
for this message.
managed systems.
Explanation: No additional information is available
KUICKA016E KUICKA016E: A problem was
for this message.
encountered while stopping the
AGENTCODE agent or agents on the
KUICKA006I KUICKA006I: Are you sure you want local system. See the agent log to
to stop the AGENTCODE agent that determine the source of the problem.
manages SYSTEMLIST ?
Explanation: No additional information is available
Enter Y for yes or N for no:
for this message.
Explanation: No additional information is available
for this message.
KUICKA017E KUICKA017E: The AGENTCODE agent
or agents could not be stopped on the
KUICKA007I KUICKA007I: Stopping AGENTCODE local system because the CANDLEHOME
agent(s). environment variable is not set.
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KUICKA008I KUICKA008I: AGENTCODE KUICKA018I KUICKA018I: Do you want to stop all

successfully stopped on NODE. AGENTCODE agents on the local
System(s) MANAGEDSYSTEMLIST are system?
no longer being managed. Enter Y for yes or N for no:
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KUICKA009E KUICKA009E: A problem occurred KUICKA019E KUICKA019E: OS Agent

while stopping AGENTCODE - refer to MANAGEDSYSTEM was not stopped.
the following error returned from the Do not use the -n|--node or -m|--system
server: options when stopping local OS agents.
Use only the -t|--type option when
Explanation: No additional information is available
stopping local OS agents. Run tacmd
for this message.
stopagent -t AGENTCODE to stop the
OS Agent locally.
KUICKA010E KUICKA010E: The -n|--node and
Explanation: No additional information is available
-t|--type options cannot be used with
for this message.
the -m|--system option.
Explanation: No additional information is available
for this message.

Appendix E. Understanding informational, warning, and error messages 199

KUICKA020I • KUICLB004E

CANDLE_HOME on Windows systems. This variable is

KUICKA020I KUICKA020I: RESPONSE is not a
not set on the current server.
correct response. Enter Y for yes or N
for no: Operator response: Establish the appropriate
environment variable that is specific for yoursystem,
Explanation: No additional information is available
indicating the primary installation location of this
for this message.
server. Currently, the variables that are used are
CANDLEHOME on UNIX and Linux systems, and
KUICKA021E KUICKA021E: MANAGEDSYSTEM CANDLE_HOME on Windows systems.
was not stopped because the NODE
Administrator Response: Verify that the appropriate
node that manages it is offline.
environment variable that is specific for your system is
Explanation: No additional information is available correctly set by default on the server to indicate the
for this message. primary installation location of IBM Tivoli Monitoring.
Currently, the variables that are used are
CANDLEHOME on UNIX and Linux systems, and
KUICKA022E KUICKA022E: The
CANDLE_HOME on Windows systems.
MANAGEDSYSTEM was stopped
because there were no nodes were
found on the same system. KUICLB003E KUICLB003E: The server installation
location envval indicated by the
Explanation: A managed system cannot be stopped
candlehome environment variable does
unless it has a node, or OS agent, installed on the same
not exist.
machine as the managed system. The node must be
configured with the hostname and port number of the Explanation: The primary location of an IBM Tivoli
server that you are currently logged into. Monitoring server is indicated by an environment
variable that is specific to your system. Currently, this
Operator response: Log into the machine where the
is CANDLEHOME on UNIX and Linux systems, and
managed system resides and attempt to stop the agent
CANDLE_HOME on Windows systems. This variable
locally, install and start the appropriate node on the
was set incorrectly on this server.
same machine as the managed system, or reconfigure
the node. Operator response: Correct the appropriate
environment variable that is specific to your system,
indicating the primary installation location of this
KUICKA099E KUICKA099E: Cannot run the
server. Currently, the variables that are used are
command because of a system error.
CANDLEHOME on UNIX and Linux sysgtems, and
Contact the system administrator.
CANDLE_HOME on Windows systems.
Explanation: No additional information is available
Administrator Response: Verify that the appropriate
for this message.
environment variable that is specific to your system is
correctly set by default on the server to indicate the
KUICLB001E KUICLB001E: You must set the binArch primary installation location of IBM Tivoli Monitoring.
environment variable before running Currently, the variables that are used are
the listbundles command. CANDLEHOME on UNIX and Linux systems, and
CANDLE_HOME on Windows systems.
Explanation: The architecture type specific to your
system must be set. This variable is not set on the
current server. For UNIX and Linux systems, this KUICLB004E KUICLB004E: The server installation
directory is a subdirectory of the primary installation location indicated by the candlehome
location of the server. The primary location of an IBM environment variable does not appear to
Tivoli Monitoring server is indicated by the be a directory: envval.
CANDLEHOME environment variable.
Explanation: The primary location of an IBM Tivoli
Operator response: Establish this variable for your Monitoring server is indicated by an environment
system, indicating the platform architecture of this variable that is specific to your system. Currently, that
server. is CANDLEHOME on UNIX and Linux systems, and
CANDLE_HOME on Windows systems. This variable
was set incorrectly on this server and does not
KUICLB002E KUICLB002E: The candlehome reference a directory.
environment variable must be set before
running this command. Operator response: Correct the appropriate
environment variable that is specific to your system,
Explanation: The primary location of an IBM Tivoli indicating the primary installation directory of this
Monitoring server is indicated by an environment server. Currently, the variables that are used are
variable that is specific to your system. Currently, this CANDLEHOME on UNIX and Linux systems, and
is CANDLEHOME on UNIX and Linux systems, and

200 IBM Tivoli Monitoring: Problem Determination Guide

 KUICLB005E • KUICLB019E

CANDLE_HOME on Windows systems.

KUICLB007E KUICLB007E: The path for
Administrator Response: Verify that the appropriate DEPOTHOME depotHome was not
environment variable that is specific to your system is found.
correctly set by default on the server to indicate the
Explanation: The specified path to the depot is
primary installation directory of IBM Tivoli Monitoring.
incorrect or does not exist.
Currently, the variables that are used are
CANDLEHOME on UNIX and Linux systems, and Operator response: If the variable DEPOTHOME was
CANDLE_HOME on Windows systems. specified within the KBBENV file then change the
value of this variable to correct path to the depot. If
DEPOTHOME was not specified within KBBENV file,
KUICLB005E KUICLB005E: The location of the jar
call IBM Software Support.
files directory needed by createNode
was not found: envval. Administrator Response: If the variable
DEPOTHOME was specified within the KBBENV file,
Explanation: Several jar files are needed by
change the value of DEPOTHOME to correct path to
createNode, and are expected to be found in a specific
the depot. If DEPOTHOME was not specified within
location on each server. The location was not found on
KBBENV file, call IBM Software Support.
this server.
Administrator Response: Locate the
KUICLB008E KUICLB008E: The path to the
jars DEPOTHOME directory was not found.

directory on the server that contains Explanation: The specified value of the DEPOTHOME
variable was not found.
createnode.jar
Operator response: Verify the location of the depot
, along with several other jar files. Copy that directory and specify the correct location as the value for
and all of its contents to the expected location. This DEPOTHOME in the KBBENV file.
location varies by system as follows: Administrator Response: Verify the location of the
v On UNIX/Linux systems: depot and specify this location as the value for
$CANDLEHOME/platform/kui/jars/ DEPOTHOME in the KBBENV file.
v On Windows systems:
%CANDLE_HOME%\CLI\jars\ KUICLB010E KUICLB010E: The addbundles
command did not complete. Refer to the
KUICLB006E KUICLB006E: The required jar file following returned error:
jarfile was not found in the expected ERRORTEXT
location. Explanation: No additional information is available
Explanation: Several jar files are needed by for this message.
createNode, and are expected to be found in a specific
location on each server. However, that location is KUICLB017E KUICLB017E: The directory
missing at least one of the expected jar files on this IMAGEPATH does not exist.
server.
Explanation: No additional information is available
Administrator Response: Locate the for this message.
jars
KUICLB018E KUICLB018E: The directory
directory on the server and verify that it contains all of
IMAGEPATH contains no bundles.
the required jar files. Perform a search on the server for
the referenced missing jar file, then copy it to the Explanation: No additional information is available
appropriate location. for this message.
v On UNIX/Linux systems:
$CANDLEHOME/platform/kui/jars/ KUICLB019E KUICLB019E: The directory
v On Windows systems: IMAGEPATH contains no bundles
%CANDLE_HOME%\CLI\jars\ matching the product(s), platform(s),
and/or version(s) specified.
Explanation: No additional information is available
for this message.

Appendix E. Understanding informational, warning, and error messages 201

KUICLR001E • KUICRA002E

KUICLR001E KUICLR001E: You are not logged in. KUICLS003E KUICLS003E: The specified option type
parm1 in the listSit command is
Explanation: You must log into the server from which
incorrect.
you are trying to run the listsystem command. Use the
following command to log in: Explanation: The listSit command did not list
tacmd login {-s|--server} situations because an incorrect type was specified with
{[PROTOCOL://]HOST[:PORT]} the -t option.
[{-u|--username} USERNAME [{-p|--password}
Operator response: Run the listSit command again
PASSWORD]]
specifying the correct managed system type.
[{-t|--timeout} TIMEOUT]

KUICLS004E KUICLS004E: There is no

KUICLR002I KUICLR002I: There were no systems
communication with the Tivoli
that match the type PRODUCTCODE.
Enterprise Monitoring Server.
Explanation: No additional information is available
Explanation: The listSit command did not complete
for this message.
because the specified managed system cannot
communication with the Tivoli Enterprise Monitoring
KUICLR004E KUICLR004E: The server on HOST Server.
cannot find the node NODE
Operator response: Start the Tivoli Enterprise
Explanation: Run the listSystems -t UX NT LZ Monitoring Server and try running the listSit command
command to list the existing nodes. again.

KUICLR099E KUICVN099E: The kuilistnodes did KUICLS005E KUICLS005E: The managed system
not complete because a system error parm1 does not exist.
occurred. Contact the system
Explanation: The listSit command did not complete
administrator.
because specified the managed system is incorrect.
Explanation: No additional information is available
Operator response: Verify the correct managed system
for this message.
name and run the listSit command again.

KUICLR099E KUICLR099E: The command did not

KUICLS006E KUICLS006E: There are no situations on
complete because of a system error.
the managed system or managed system
Refer to the log for details and contact
type parm1 .
the system administrator.
Explanation: The listSit command did not list the
Explanation: No additional information is available
situation because the specified managed system or
for this message.
managed system type does not contain situations.
Operator response: Specify the correct managed
KUICLS001E KUICLS001E: You are not logged in.
system or managed system type with the -m or -t
Explanation: You must login before running the listSit option and run the listSit command again.
command.
Operator response: Log in to the management server KUICRA001E KUICRA001E: The restartagent
using the login command and run the listSit command command did not complete because you
again. are not logged in.
Explanation: You must log in before running the
KUICLS002E KUICLS002E: The listSit command did restartagent with the -n option.
not list situation because the option -t
Operator response: Log in with the login command
and -m were both specified.
run the restartagent command again, specifying the -n
Explanation: An incorrect combination of command option command.
line option was entered.
Operator response: Run the listSit command KUICRA002E KUICRA002E: The restartagent
specifying either the -t or -m option. command did not complete because
required options were not specified.
Explanation: You must also use the -t|--type option to
use the -n|--node option when restarting the agent
from the command line.

202 IBM Tivoli Monitoring: Problem Determination Guide

 KUICRA003E • KUICRA018I

Operator response: Run the restartagent command

KUICRA009E KUICRA009E: A problem occurred
again, specifying one or more agent type(s) with the
while restarting AGENTCODE - refer to
-t|--type option, and specifying a node with the
the following error returned from the
-n|--node option.
server:
Explanation: No additional information is available
KUICRA003E KUICRA003E: The restartagent
for this message.
command did not complete because you
are not logged in to the managed system
that hosts the specified node. KUICRA010E KUICRA010E: The restartagent
command did not complete because
Explanation: You must log in to the managed system
incorrect options were specified.
before specifying the node on which to restart the
agent. Explanation: The -n|--node and -t|--type options
cannot be used with the -m|--system option.
Operator response: Log into the managed system that
hosts the agents you want to restart. Run the Operator response: Run the restartagent command
restartagent command again, specifying the node with again, specifying a managed system with the -m option
the -n option. or specify an agent type with the -t option and a node
with the -n option.
KUICRA004E KUICRA004E: The node NODE was
not found on the server on HOST. KUICRA013E KUICRA013E: Agent product code
PRODUCTCODE is not known by server
Explanation: Run the listSystems command to view a
on HOST.
list of known managed systems.
Explanation: No additional information is available
Operator response: Verify the node and managed
for this message.
system and run the restartagent command again.

KUICRA015I KUICRA015I: All AGENTCODE agents

KUICRA005E KUICRA005E: The managed system
on the local system were restarted.
MANAGEDSYSTEMwas not found on
the server on HOST. Explanation: No additional information is available
for this message.
Explanation: Run the listSystems command to view a
list of known managed systems.
KUICRA016E KUICRA016E: A problem occurred
Operator response: Verify the managed system name
while restarting the AGENTCODE agents
and run the restartagent command again.
on the local system. Refer to the agent
log to determine the source of the
KUICRA006I KUICRA006I: Are you sure you want problem.
to restart the AGENTCODE agent that
Explanation: No additional information is available
manages SYSTEMLIST ?
for this message.
Enter Y for yes or N for no:
Explanation: No additional information is available
KUICRA017E KUICRA017E: The AGENTCODE
for this message.
agents were not restarted on the local
system because the CANDLEHOME
KUICRA007I KUICRA007I: Restarting AGENTCODE environment variable is not set.
agent(s).
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KUICRA018I KUICRA018I: Do you want to restart
KUICRA008I KUICRA008I: AGENTCODE was all AGENTCODE agents on the local
restarted on node NODE and is system?
managing system(s) MANAGEDSYSTEM. Enter Y for yes or N for no:
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

Appendix E. Understanding informational, warning, and error messages 203

KUICRA019E • KUICRB003E

location of the server. The primary location of an IBM

KUICRA019E KUICRA019E: The OS agent
Tivoli Monitoring server is indicated by the
MANAGEDSYSTEM did not restart
CANDLEHOME environment variable.
remotely. Run tacmd restartagent -t
AGENTCODE -n from the system where Operator response: Establish this variable for your
the OS agent exists to restart the agent system, indicating the platform architecture of this
from the command line. Use the server.
-t|--type option and the -n|--node
option when restarting the agent from
the command line. You cannot specify KUICRB002E KUICRB002E: The candlehome
the product code for an OS agent when environment variable must be set before
specifying the -t and -n option. running this command.

Explanation: No additional information is available Explanation: The primary location of an IBM Tivoli
for this message. Monitoring server is indicated by an environment
variable that is specific to your system. Currently, this
is CANDLEHOME on UNIX and Linux systems, and
KUICRA020I KUICRA020I: RESPONSE is not a CANDLE_HOME on Windows systems. This variable is
correct response. Enter Y for yes or N not set on the current server.
for no:
Operator response: Establish the appropriate
Explanation: No additional information is available environment variable that is specific for your system,
for this message. indicating the primary installation location of this
server. Currently, the variables that are used are
CANDLEHOME on UNIX and Linux systems, and
KUICRA021E KUICRA021E: MANAGEDSYSTEM was
CANDLE_HOME on Windows systems.
not restarted because the NODE node
that manages it is offline. Administrator Response: Verify that the appropriate
environment variable that is specific for your system is
Explanation: No additional information is available
correctly set by default on the server to indicate the
for this message.
primary installation location of IBM Tivoli Monitoring.
Currently, the variables that are used are
KUICRA022E KUICRA022E: MANAGEDSYSTEM was CANDLEHOME on UNIX and Linux systems, and
not restarted because there were no CANDLE_HOME on Windows systems.
nodes found on that managed system.
Explanation: You cannot restart a managed system KUICRB003E KUICRB003E: The server installation
unless it has a node or OS agent installed on the same location indicated by the candlehome
server as the managed system. The node must be environment variable does not exist:
configured with the hostname and port number of the envval.
server that you are currently logged into.
Explanation: The primary location of an IBM Tivoli
Operator response: Log into the machine where the Monitoring server is indicated by an environment
managed system is located and stop the agent locally, variable that is specific to your system. Currently, this
install and start the appropriate node on the same is CANDLEHOME on UNIX and Linux systems, and
machine as the managed system, or re-configure the CANDLE_HOME on Windows systems. This variable
node. was set incorrectly on this server.
Operator response: Correct the appropriate
KUICRA099E KUICRA099E: The restartagent environment variable that is specific to your system,
command did not complete because of a indicating the primary installation location of this
system error. server. Currently, the variables that are used are
CANDLEHOME on UNIX and Linux sysgtems, and
Explanation: An unexpected error occurred.
CANDLE_HOME on Windows systems.
Operator response: Refer to the log for details and
Administrator Response: Verify that the appropriate
contact the system administrator.
environment variable that is specific to your system is
correctly set by default on the server to indicate the
KUICRB001E KUICRB001E: The binArch primary installation location of IBM Tivoli Monitoring.
environment variable must be set before Currently, the variables that are used are
running this command. CANDLEHOME on UNIX and Linux systems, and
CANDLE_HOME on Windows systems.
Explanation: The architecture type specific to your
system must be set. This variable is not set on the
current server. For UNIX and Linux systems, this
directory is a subdirectory of the primary installation

204 IBM Tivoli Monitoring: Problem Determination Guide

 KUICRB004E • KUICRB017E

Administrator Response: Locate the

KUICRB004E KUICRB004E: The server installation
location envval indicated by the jars
candlehome environment variable is not a
directory. directory on the server and verify that it contains all of
the required jar files. Perform a search on the server for
Explanation: The primary location of an IBM Tivoli the referenced missing jar file, then copy it to the
Monitoring server is indicated by an environment appropriate location.
variable that is specific to your system. Currently, that
is CANDLEHOME on UNIX and Linux systems, and v On UNIX/Linux systems:
CANDLE_HOME on Windows systems. This variable $CANDLEHOME/platform/kui/jars/
was set incorrectly on this server, and is not referencing v On Windows systems:
a directory. %CANDLE_HOME%\CLI\jars\
Operator response: Correct the appropriate
environment variable that is specific to your system, KUICRB007E KUICRB007E: The path for
indicating the primary installation directory of this DEPOTHOME depotHome was not
server. Currently, the variables that are used are found.
CANDLEHOME on UNIX and Linux systems, and
Explanation: The specified path to the depot is
CANDLE_HOME on Windows systems.
incorrect or does not exist.
Administrator Response: Verify that the appropriate
Operator response: If the variable DEPOTHOME was
environment variable that is specific to your system is
specified within the KBBENV file then change the
correctly set by default on the server to indicate the
value of this variable to correct path to the depot. If
primary installation directory of IBM Tivoli Monitoring.
DEPOTHOME was not specified within KBBENV file,
Currently, the variables that are used are
call IBM Support.
CANDLEHOME on UNIX and Linux systems, and
CANDLE_HOME on Windows systems. Administrator Response: If the variable
DEPOTHOME was specified within the KBBENV file,
change the value of DEPOTHOME to correct path to
KUICRB005E KUICRB005E: The createNode
the depot. If DEPOTHOME was not specified within
command cannot find the wjar files
KBBENV file, call IBM Support.
directory in envval.
Explanation: Several jar files are needed by
KUICRB008E KUICRB008E: The path to the
createNode, and are expected to be found in a specific
DEPOTHOME directory was not found.
location on each server. The jar file cannot be found on
this server. Explanation: The specified value of the DEPOTHOME
variable was not found.
Administrator Response: Locate the
jars Operator response: Verify the location of the depot
and specify the correct location as the value for
directory on the server that contains DEPOTHOME in the KBBENV file.
createnode.jar Administrator Response: Verify the location of the
depot and specify this location as the value for
, along with several other jar files. Copy that directory DEPOTHOME in the KBBENV file.
and all of its contents to the expected location. This
location varies by system as follows: KUICRB010E KUICRB010E: The removebundles
v On UNIX/Linux systems: command did not complete. Refer to the
$CANDLEHOME/platform/kui/jars/ following returned error:
v On Windows systems: ERRORTEXT
%CANDLE_HOME%\CLI\jars\ Explanation: No additional information is available
for this message.
KUICRB006E KUICRB006E: The required jar file
jarfile was not found in the expected KUICRB017E KUICRB017E: The directory
location. IMAGEPATH does not exist.
Explanation: Several jar files are needed by Explanation: No additional information is available
createNode, and are expected to be found in a specific for this message.
location on each server. The specified location is
missing at least one of the expected jar files on this
server.

Appendix E. Understanding informational, warning, and error messages 205

KUICRB018E • KUICSA007I

KUICRB018E KUICRB018E: The directory KUICSA001E KUICSA001E: You are not logged in.
IMAGEPATH contains no bundles. You must log in to use the -n option.
Explanation: No additional information is available Explanation:
for this message.
Operator response:

KUICRB019E KUICRB019E: The directory

KUICSA002E KUICSA002E: The startagent command
IMAGEPATH contains no bundles
did not complete because required
matching the product(s), platform(s),
options were not specified.
and/or version(s) specified. There are no
bundles to remove. Explanation: You must also use the -t|--type option to
use the -n|--node option when starting the agent from
Explanation: No additional information is available
the command line.
for this message.
Operator response: Run the startagent command
again, specifying one or more agent type or types with
KUICRB020I KUICRB020I: Removing bundles from
the -t|--type option, and specifying a node with the
the DEPOTPATH depot.
-n|--node option.
Explanation: No additional information is available
for this message.
KUICSA003E KUICSA003E: You are not logged in.
You must run the login command before
KUICRB021I KUICRB021I: The specified bundles in using the -n option.
the IMAGEPATH directory were not
Explanation: No additional information is available
found in the DEPOTPATH depot. There
for this message.
are no bundles to remove.
Explanation: No additional information is available
KUICSA004E KUICSA004E: Node NODE is not
for this message.
known by server on HOST. Use the
listSystems command to view a list of
KUICRB022I KUICRB022I: The following bundles known managed systems.
were successfully removed from the
Explanation: No additional information is available
DEPOTPATH depot:
for this message.
Explanation: No additional information is available
for this message.
KUICSA005E KUICSA005E: Managed system
MANAGEDSYSTEM is not known by
KUICRB023I KUICRB023I: Are you sure you want to server on HOST. Use the listSystems
remove the following bundles from the command to view a list of known
DEPOTPATH depot? managed systems.
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KUICRB024I KUICRB024I: Enter Y for yes or N for KUICSA006I KUICSA006I: Are you sure you want to
no: start the AGENTCODE agent that
manages SYSTEMLIST ?
Explanation: No additional information is available
Enter Y for yes or N for no:
for this message.
Explanation: No additional information is available
for this message.
KUICRB025E KUICRB025E: RESPONSE is not a
correct response. Enter Y for yes or N
for no: KUICSA007I KUICSA007I: Starting AGENTCODE
agent or agents.
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.

206 IBM Tivoli Monitoring: Problem Determination Guide

 KUICSA008I • KUICSA023W

KUICSA008I KUICSA008I: AGENTCODE was KUICSA018I KUICSA018I: Do you want to start all
successfully started on node NODE and AGENTCODE agents on the local
is managing system or systems system?
MANAGEDSYSTEM. Enter Y for yes or N for no:
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KUICSA009E KUICSA009E: A problem occurred KUICSA019E KUICSA019E: OS Agent

while starting AGENTCODE - refer to MANAGEDSYSTEM cannot be started
the following error returned from the remotely. Execute tacmd startagent -t
server: AGENTCODE from the system where
the OS Agent resides to start the agent
Explanation: No additional information is available
from the command line.
for this message.
Explanation: No additional information is available
for this message.
KUICSA010E KUICSA010E: The -n|--node and
-t|--type options cannot be used with
the -m|--system option. KUICSA020I KUICSA020I: RESPONSE is not a correct
response. Enter Y for yes or N for no:
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KUICSA013E KUICSA013E: Agent product code
PRODUCTCODE is not known by server KUICSA021E KUICSA021E: MANAGEDSYSTEM was
on HOST. not started because the NODE node is
offline.
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KUICSA014I KUICSA014I: The AGENTCODE agent
managing system or systems KUICSA022E KUICSA022E: MANAGEDSYSTEM was
MANAGEDSYSTEMLIST is already not started because there were no nodes
started. found on the same system.
Explanation: No additional information is available Explanation: A managed system cannot be started
for this message. unless it has a node, or OS agent, installed on the same
machine as the managed system. The node must be
configured with the hostname and port number of the
KUICSA015I KUICSA015I: All AGENTCODE agents
server that you are currently logged into.
on the local system were started.
Operator response: Log in to the machine where the
Explanation: No additional information is available
managed system resides and attempt to stop the agent
for this message.
locally, install and start the appropriate node on the
same machine as the managed system, or reconfigure
KUICSA016E KUICSA016E: An error occurred while the node.
starting the AGENTCODE agent or
agents on the local system. See the
KUICSA023W KUICSA023W: The agent type code
agent log to determine the source of the
AGENTCODE is not correct for
problem.
OSPLATFORM.
Explanation: No additional information is available
Explanation: The agent type code selected is not
for this message.
correct for this OS platform.
Operator response: Verify that the agent type you
KUICSA017E KUICSA017E: The AGENTCODE agent
specified is correct.
or agents were not started on the local
system because the CANDLEHOME
environment variable is not set.
Explanation: No additional information is available
for this message.

Appendix E. Understanding informational, warning, and error messages 207

KUICSA023W • KUICUA012I

Explanation: No additional information is available

KUICSA023W KUICSA023W: The agent type code
for this message.
AGENTCODE is not correct for
OSPLATFORM.
KUICUA006E KUICUA006E: Cannot locate any
Explanation: The agent type code selected is not
version of the TYPE management agent
correct for this OS platform.
in the CMS depot. Use the viewDepot
Operator response: Check the agent type you have command to list the contents of a depot.
chosen to ensure that its correct.
Explanation: No additional information is available
for this message.
KUICSA023W KUICSA023W: The agent type code
AGENTCODE is not correct for
KUICUA007I KUICUA007I: Are you sure you want
OSPLATFORM.
to update the TYPE agents that manage
Explanation: The agent type code selected is not SYSTEMLIST to the latest version?
correct for this OS platform. Updating these agents stops any that are
running, applies the changes, and
Operator response: Check the agent type you have
restarts them.
chosen to ensure that its correct.
Enter Y for yes or N for no:
Explanation: No additional information is available
KUICSA099E KUICSA099E: The did not complete
for this message.
because of a system error. Contact the
system administrator.
KUICUA008E KUICUA008E: An error occurred while
Explanation: No additional information is available
updating the TYPE agents on HOST. See
for this message.
the agent log to determine the source of
the problem.
KUICUA001E KUICUA001E: You must specify
Explanation: No additional information is available
-t/--type option.
for this message.
Explanation: No additional information is available
for this message.
KUICUA009I KUICUA009E: The TYPE agents were
updated.
KUICUA002E KUICUA002E: You are not logged in.
Explanation: No additional information is available
You must log in with the login
for this message.
command to use the updateAgent
command.
KUICUA010E KUICUA010E: Node NODE on system
Explanation: No additional information is available
HOSTNAME does not have any TYPE
for this message.
agents installed.
Explanation: No additional information is available
KUICUA003E KUICUA003E: You must specify the
for this message.
-n/--node option.
Explanation: No additional information is available
KUICUA011I KUICUA011I: Updating the TYPE
for this message.
agents.
Explanation: No additional information is available
KUICUA004E KUICUA004E: The node NODE was
for this message.
not found by the server on HOST. Use
the listSystems command to view a list
of known managed systems. KUICUA012I KUICUA012I: Are you sure you want
to update the TYPE agents that manage
Explanation: No additional information is available
SYSTEMLIST to version VERSION?
for this message.
Updating these agents stops any that are
running, applies the changes, and
KUICUA005E KUICUA005E: Cannot locate version restarts them.
VERSION of the TYPE management Enter Y for yes or N for no:
agent in the CMS depot. Use the
Explanation: No additional information is available
viewDepot command to list the contents
for this message.
of a depot.

208 IBM Tivoli Monitoring: Problem Determination Guide

 KUICUA013E • KUICVA016E

KUICUA013E KUICUA013E: RESPONSE is not a KUICVA005E KUICVA005E: The managed system

correct response. Enter Y for yes or N MANAGEDSYSTEM is not known by
for no: server on HOST. Use the listSystems
command to view a list of known
Explanation: No additional information is available
managed systems.
for this message.
Explanation: No additional information is available
for this message.
KUICUA014E KUICUA014E: The
MANAGEDSYSTEM was not updated
because the NODE node that manages it KUICVA006E KUICVA006E: You must also specify
is offline. the -n option when using the -t option.
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KUICUA015E KUICUA015E: The updateAgent KUICVA007E KUICVA007E: The -n|--node and

command did not complete because an -t|--type options cannot be used with
error occurred. Refer to the following the -m|--system option.
error returned from the server:
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KUICVA013E KUICVA013E: Agent product code
KUICUA099E KUICUA099E: The command did not PRODUCTCODE is not known by server
complete because of a system error. on HOST.
Contact the system administrator.
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KUICVA014E KUICVA014E: The managed system
KUICVA001E KUICVA001E: You are not logged in. MANAGEDSYSTEM cannot be viewed
You must log in with the login because it is a management server, not
command to use the -n option. an agent.
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KUICVA002E KUICVA002E: You must specify the -m KUICVA015E KUICVA015E: The agent
or -t option. MANAGEDSYSTEM cannot be viewed,
because the node that manages the
Explanation: No additional information is available
agent is offline, because the node that
for this message.
manages it is not configured for the
server you are logged into, or because
KUICVA003E KUICVA003E: You must log in with there is no node installed local to the
the login command before using the -n agent. The node for this agent must be
option. online in order to retrieve the
configuration data for the agent.
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KUICVA004E KUICVA004E: Node NODE is not
known by server on HOST. Use the KUICVA016E KUICVA016E: The viewAgent
listSystems command to view a list of command did not complete because an
known managed systems. error occurred retrieving the agent
configuration from the server. Refer to
Explanation: No additional information is available the following error returned from the
for this message. server:
Explanation: No additional information is available
for this message.

Appendix E. Understanding informational, warning, and error messages 209

KUICVA099E • KUICVS001E

KUICVA099E KUICVA099E: The command did not KUICVN002I KUICVN002I: The server HOST does
complete because of system error. not contain nodes.
Contact the system administrator.
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KUICVN003I KUICVD003I: There are no
KUICVD001E KUICVD001E: You must log in with components installed on the node
the login command before using this NODENAME on the server HOST.
command.
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KUICVN004E KUICVN004E: You must specify a
KUICVD002E KUICVD002E: Depot DEPOTNAME value for the -n/--node option when
does not exist. Specify a correct depot running the viewnode command.
name.
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KUICVN005E KUICVN005E: The viewnode
KUICVD003I KUICVD003I: The depot is empty. command did not complete because the
CANDLEHOME environment variable is
Explanation: No additional information is available
not set.
for this message.
Explanation: No additional information is available
for this message.
KUICVD099E KUICVD099E: The command did not
complete because a system error
occurred. Contact the system KUICVN006E KUICVN006E: The viewnode
administrator. command did not complete because the
command COMMAND did not run.
Explanation: No additional information is available
for this message. Explanation: The -d|--directory option must specify
the fully-qualified or relative path to the Candle home
directory.
KUICVN001E KUICVN001E: You are not logged in.
Run the kuilogin command before Operator response: Run the viewnode command
running the kuilistnodes command. again, specifying the Candle home directory using the
-d|--directory, or run tacmd help viewnode to view
Explanation: No additional information is available
usage options.
for this message.

KUICVN099E KUICVN099E: The viewnode

KUICVN001E KUICVN001E: You are not logged in.
command did not complete because a
Run the login command before running
system error occurred. Contact the
the viewnode command.
system administrator.
Explanation: No additional information is available
Explanation: No additional information is available
for this message.
for this message.

KUICVN002E KUICVN002E: The node NODENAME

KUICVS001E KUICVS001E: The viewsit command
was not found on the server HOST. Run
did not complete because it specified an
the listSystems -t UX NT LZ command
incorrect option.
to list existing nodes.
Explanation: The situation name cannot display
Explanation: No additional information is available
because it was not specified in the correct format.
for this message.
Operator response: Verify the correct options and
situation name and run the following command:
tacmd viewSit {-s|--situation} SITNAME [{-e|--export}
[FILENAME] ]

210 IBM Tivoli Monitoring: Problem Determination Guide

 KUICVS002E • KUMPA011E

KUICVS002E KUICVS002E: The viewSit command KUMPA002E Input parameter is invalid {0}
did not complete because you are not
Explanation: No additional information is available
logged in.
for this message.
Explanation: You must run the login command on the
server from which you are trying to view situations.
KUMPA003E Required input parameter not specified
Operator response: Run the following login command
Explanation: No additional information is available
before running the viewsit command:
for this message.
tacmd login {-s|--server}
{[PROTOCOL://]HOST[:PORT]} [{-u|--username}
USERNAME KUMPA004E Startup configuration error
[{-p|--password} PASSWORD] [{-t|--timeout}
TIMEOUT] Explanation: No additional information is available
for this message.

KUICVS003E KUICVS003E: The situation SITNAME

does not exist on the server KUMPA005E Unsupported startup configuration
HOSTNAME. specified

Explanation: The specified situation cannot display Explanation: No additional information is available
because it was not found on the server. for this message.

Operator response: Verify the correct situation name

and that it exists on the specified server, then run the KUMPA006E Unable to obtain main control block
viewSit command again. storage
Explanation: No additional information is available
KUICVS004I KUICVS004I: The Situation SITNAME for this message.
was exported to FILENAME .
Explanation: No additional information is available KUMPA007E Unable to obtain data transport buffer
for this message. storage
Explanation: No additional information is available
KUICVS005E KUICVS005E: The file filename was not for this message.
created.
Explanation: You do not have permission to create a KUMPA008E Local machine host name cannot be
file. resolved to IP address

Operator response: Contact the system administrator Explanation: No additional information is available
to request permission to create files. for this message.

KUICVS006E KUICVS006E: The file filename was not KUMPA009E Local Winsock/RPC initialization failed,
created. errno {0}

Explanation: A system error occurred because the file Explanation: No additional information is available
is corrupt. for this message.

Administrator Response: Refer to the log for more

details. KUMPA010W DP API server inactive
Explanation: No additional information is available
KUMPA000I Function completed successfully for this message.

Explanation: No additional information is available

for this message. KUMPA011E API request timed out or API DP server
inactive at {0}

KUMPA001E Input handle is invalid Explanation: No additional information is available

for this message.
Explanation: No additional information is available
for this message.

Appendix E. Understanding informational, warning, and error messages 211

KUMPA012E • KUMPA041E

KUMPA012E Unable to obtain API handle storage KUMPA032E dp_Define metafile specification error
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KUMPA013E API request logic sequence error KUMPA033W dp_Define application already known
to agent or in use by another DP
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KUMPA014E Required input parameter not specified
KUMPA034E dp_Redefine application currently not
Explanation: No additional information is available
defined
for this message.
Explanation: No additional information is available
for this message.
KUMPA020E dp_ShowMessage no message id
specified
KUMPA035E dp_Redefine metafile not found
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KUMPA021I dp_Ping successful
KUMPA036E dp_Redefine metafile specification error
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KUMPA022E dp_Ping failed
KUMPA037W dp_Redefine application already
Explanation: No additional information is available
known to agent or in use by another DP
for this message.
Explanation: No additional information is available
for this message.
KUMPA023E dp_Ping to API DP server error {0}
Explanation: No additional information is available
KUMPA038E dp_SetSourceName input name missing
for this message.
or invalid
Explanation: No additional information is available
KUMPA024E dp_OpenSession input handle contains
for this message.
active connection
Explanation: No additional information is available
KUMPA039E dp_SetSourceName input name
for this message.
processing failed
Explanation: No additional information is available
KUMPA025E dp_OpenSession connection failed to
for this message.
target API DP server at {0}
Explanation: No additional information is available
KUMPA040E Input buffer pointer is invalid
for this message.
Explanation: No additional information is available
for this message.
KUMPA030W dp_Define application already
defined to DP
KUMPA041E Input buffer was not allocated to the
Explanation: No additional information is available
active handle provided
for this message.
Explanation: No additional information is available
for this message.
KUMPA031E dp_Define metafile not found
Explanation: No additional information is available
for this message.

212 IBM Tivoli Monitoring: Problem Determination Guide

 KUMPA042E • KUMPA072E

KUMPA042E Input buffer storage was not allocated KUMPA053E dp_BeginInput API server application
by dp_AllocateBuffer API initialization unsuccessful
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KUMPA043E dp_AllocateBuffer input parameter is KUMPA054E dp_BeginInput API server application

invalid registration with DCH unsuccessful
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KUMPA044E dp_AllocateBuffer failed because of KUMPA055E dp_EndInput rejected. dp_BeginInput

insufficient storage not performed or dp_EndInput already
completed
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KUMPA045W dp_FormatBufferData detects no
input data. Nothing formatted KUMPA056E Ambiguous dp_End Input rejected.
None or more than one active dp_Begin
Explanation: No additional information is available
Input outstanding without sufficient
for this message.
qualifying input parameter
Explanation: No additional information is available
KUMPA046E dp_FormatBufferData input data size is
for this message.
invalid
Explanation: No additional information is available
KUMPA057W dp_EndInput specified application is
for this message.
not active. dp_BeginInput was not
performed
KUMPA047E dp_FormatBufferData insufficient room
Explanation: No additional information is available
remains in buffer to contain formatted
for this message.
input data
Explanation: No additional information is available
KUMPA058E dp_EndInput API server application
for this message.
unregistration with DCH unsuccessful
Explanation: No additional information is available
KUMPA050E dp_BeginInput requires application
for this message.
name and attribute group parameter
specifications
KUMPA070E dp_Input application inactive
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KUMPA051E dp_BeginInput specified application not
found KUMPA071E None or more than one active
application outstanding. API target is
Explanation: No additional information is available
ambiguous without qualification
for this message.
Explanation: No additional information is available
for this message.
KUMPA052E dp_BeginInput specified attribute group
not found
KUMPA072E dp_Input data transfer I/O error
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.

Appendix E. Understanding informational, warning, and error messages 213

KUMPA073E • KUMPG003I

KUMPA073E dp_Input input buffer contains no data KUMPA090E API client is incompatible and
unsupported by the active API DP
Explanation: No additional information is available
server
for this message.
Explanation: No additional information is available
for this message.
KUMPA074E dp_Input input buffer is invalid
Explanation: No additional information is available
KUMPA091E API DP server unable to allocate source
for this message.
control block storage
Explanation: No additional information is available
KUMPA075E dp_Input local transport setup
for this message.
unsuccessful
Explanation: No additional information is available
KUMPA092E API DP server unable to send
for this message.
application data to DCH, input data
discarded
KUMPA076W dp_Input data truncated to maximum
Explanation: No additional information is available
buffer size 2048
for this message.
Explanation: No additional information is available
for this message.
KUMPA093E API DP server detected data field format
error in input data record
KUMPA080I dp_RecvReply no data available to
Explanation: No additional information is available
receive
for this message.
Explanation: No additional information is available
for this message.
KUMPA094E API DP server detected processing state
logic error
KUMPA081E dp_ReceiveRequest input buffer size
Explanation: No additional information is available
invalid.
for this message.
Explanation: No additional information is available
for this message.
KUMPA100E KUMPAxx Invalid message code
Explanation: No additional information is available
KUMPA082I dp_ReceiveRequest no activity request
for this message.
outstanding.
Explanation: No additional information is available
KUMPG000I Metafile generation completed
for this message.
successfully
Explanation: No additional information is available
KUMPA083W dp_ReceiveRequest received request
for this message.
data truncated to input buffer size.
Explanation: No additional information is available
KUMPG001E Definition Error: File not found {0}
for this message.
Explanation: No additional information is available
for this message.
KUMPA084W dp_SendRequestResult data truncated
to supported maximum.
KUMPG002E Input Error: {0} is not a defined ODBC
Explanation: No additional information is available
data source. Unable to generate metafile.
for this message.
Explanation: No additional information is available
for this message.
KUMPA085W dp_SendRequestResult request not
found or no longer outstanding.
KUMPG003I Using ODBC data source: {0}
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.

214 IBM Tivoli Monitoring: Problem Determination Guide

 KUMPG004E • KUMPG022I

KUMPG004E Processing Error: Unable to determine KUMPG014E Input Error: Failed to locate {0} in
path for output metafile stored procedure catalog. Unable to
generate metafile.
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KUMPG005I Generating metafile: {0}
KUMPG015W No columns were found for table {0}.
Explanation: No additional information is available
Skipping generation of this table.
for this message.
Explanation: No additional information is available
for this message.
KUMPG006E Unable to connect to ODBC data
source <{0}>, generate process
terminating... KUMPG016I Finished collecting table information for
a total of {0} tables...
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KUMPG007E Unable to allocate environment
handle for ODBC data source: {0} KUMPG017I KUMPG17I Finished collecting column
information for {0} tables...
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KUMPG008E Unable to allocate connection handle
for ODBC data source: {0} KUMPG018W Warning: Default maximum of 64
NAME statements exceeded, use
Explanation: No additional information is available
KUMA_ MAX_ ATTRGROUPS_
for this message.
PER_APPL to override or split up
metafile.
KUMPG009E Unable to open output metafile, errno
Explanation: No additional information is available
{0}
for this message.
Explanation: No additional information is available
for this message.
KUMPG019W Warning: Default maximum of 63
attributes exceeded in {0} table.
KUMPG010I Writing metafile record {0}
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KUMPG020I ODBC Metafile Generation Utility
KUMPG011W Warning: {0} already exists. OK to
Explanation: No additional information is available
replace? <Y/N>
for this message.
Explanation: No additional information is available
for this message.
KUMPG021I Indicate which type of tables to include
in the generated metafile.
KUMPG012I Metafile generation cancelled for {0}
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KUMPG022I Select one or more of the following:
KUMPG013I Using stored procedure name: {0}
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.

Appendix E. Understanding informational, warning, and error messages 215

KUMPG023I • KUMPG043I

KUMPG023I 1) Include user tables KUMPG034E No valid table types specified.

Metafile generation cancelled.
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KUMPG024I 2) Include system tables
KUMPG035W Invalid selection number {0} ignored.
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KUMPG025I 3) Include views
KUMPG036E Input Error: ODBC data source is not
Explanation: No additional information is available
the first parameter. Unable to generate
for this message.
metafile.
Explanation: No additional information is available
KUMPG026I 4) All of the above
for this message.
Explanation: No additional information is available
for this message.
KUMPG037W Warning: PSWD= parameter without
associated USER= is ignored.
KUMPG027I Enter a number (or numbers) or type ’q’
Explanation: No additional information is available
to quit metafile generation.
for this message.
Explanation: No additional information is available
for this message.
KUMPG038I Do you want to pattern match on
particular user tables? <Y/N>
KUMPG028I If you enter more than one number,
Explanation: No additional information is available
separate the numbers by a comma.
for this message.
Explanation: No additional information is available
for this message.
KUMPG039I Do you want to pattern match on
particular system tables? <Y/N>
KUMPG029I Type your selection(s) here:
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KUMPG040I Do you want to pattern match on
KUMPG030I Metafile generation cancelled for ODBC particular views? <Y/N>
data source: {0}
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KUMPG041I Specify beginning pattern matching
KUMPG031I User tables will be included. characters for user tables:

Explanation: No additional information is available Explanation: No additional information is available

for this message. for this message.

KUMPG032I System tables will be included. KUMPG042I Specify beginning pattern matching
characters for system tables:
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KUMPG033I Views will be included.
KUMPG043I Specify beginning pattern matching
Explanation: No additional information is available characters for views:
for this message.
Explanation: No additional information is available
for this message.

216 IBM Tivoli Monitoring: Problem Determination Guide

 KUMPG044I • KUMPL004I

KUMPG044I Only generating user tables beginning KUMPG054E {0} is not a defined database in the
with: {0} data source
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KUMPG045I Only generating system tables KUMPG055E Verify that server, userid and
beginning with: {0} password values are correct
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KUMPG046I Only generating views beginning with: KUMPG056W Warning: Total attribute size of 8192
{0} exceeded in {0} table.
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KUMPG047I No matching tables found for ODBC KUMPG057E Connection error message: {0}
data source: {0}
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KUMPG058E Internal processing error
KUMPG048I Is there a specific database to use?
Explanation: No additional information is available
<Y/N>
for this message.
Explanation: No additional information is available
for this message.
KUMPL000I {0} DP ready
Explanation: No additional information is available
KUMPG049I Enter database name:
for this message.
Explanation: No additional information is available
for this message.
KUMPL001I {0} DP shutdown completed
Explanation: No additional information is available
KUMPG050I Is there a specific server to use? <Y/N>
for this message.
Explanation: No additional information is available
for this message.
KUMPL002I {0} DP console interface active on port
{1}
KUMPG051I Enter server name:
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KUMPL003I {0} DP console interface inactive
KUMPG052I Tables will be generated for database:
Explanation: No additional information is available
{0}
for this message.
Explanation: No additional information is available
for this message.
KUMPL004I Metafile {0} validation successful.
Application {1} loaded.
KUMPG053E Driver does not support connection to
Explanation: No additional information is available
specific database: {0}
for this message.
Explanation: No additional information is available
for this message.

Appendix E. Understanding informational, warning, and error messages 217

KUMPL005E • KUMPL024I

KUMPL005E Metafile {0} validation failed. KUMPL016I Monitoring for file {0} started. Attribute
group <{1}>, Interval {2} seconds, Mode
Explanation: No additional information is available
{3}, Delimiter {4}
for this message.
Explanation: No additional information is available
for this message.
KUMPL006I Delete command for
metafile/application {0} received.
KUMPL017I Monitoring for file {0} completed.
Explanation: No additional information is available
Attribute group <{1}>.
for this message.
Explanation: No additional information is available
for this message.
KUMPL007I Metafile {0} found.
Explanation: No additional information is available
KUMPL018W File {0} does not exist. Monitoring
for this message.
delayed for attribute group <{1}>,
waiting for file creation...
KUMPL008I Application {0} found.
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KUMPL019W File {0} contains no valid data record.
KUMPL009E {0} metafile or application not defined. Monitoring delayed for attribute group
<{1}>, waiting for data...
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KUMPL010I Existing application {0} deleted.
KUMPL020I {0} DP started. Listening on port {1}
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KUMPL011I Import command for
metafile/application {0} received. KUMPL021I New TCP connection accepted from {0}
address {1} port {2} bound to application
Explanation: No additional information is available {3} attribute group {4}
for this message.
Explanation: No additional information is available
for this message.
KUMPL012W Application {0} already registered
with agent.
KUMPL022E New TCP connection from {0} rejected.
Explanation: No additional information is available Dynamic inbound connection without
for this message. metafile specification or SOURCE not
unique.
KUMPL013I Refresh command for Explanation: No additional information is available
metafile/application {0} received. for this message.
Explanation: No additional information is available
for this message. KUMPL023E New TCP connection from {0} rejected.
{1} application contains no matching
KUMPL014I Shutdown command received. SOURCE specification for origination {2}

Explanation: No additional information is available Explanation: No additional information is available

for this message. for this message.

KUMPL015I Existing data definitions for application KUMPL024I {0} session disconnect received from {1}
{0} accepted by command request port {2}. Application {3} attribute group
{4} management ended.
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.

218 IBM Tivoli Monitoring: Problem Determination Guide

 KUMPL025I • KUMPL042I

KUMPL025I dp_OpenSession completed from KUMPL034I dp_BeginInput failed for application {0}
location {0}. attribute group {1} from location {2}.
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KUMPL026I dp_CloseSession completed for location KUMPL035I dp_EndInput completed for application
{0}. {0} attribute group {1} from location {2}.
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KUMPL027I dp_Define for metafile/application {0} KUMPL036I DP Statistic: {0}.

received.
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KUMPL037E DP metafile server {0} listen failed,
KUMPL028I dp_Redefine for metafile/application {0} Errno {1}. Server initialization
received. unsuccessful.
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KUMPL029E New UDP connection from {0} rejected. KUMPL038E DP metafile server initialization failed.
{1} application contains no matching Metafile server is already active on the
SOURCE specification for origination {2} same system.
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KUMPL030E New {0} connection from {1} rejected. {2} KUMPL039I DP metafile server initialization
metafile definition error successful. Ready for request.
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KUMPL031I New UDP session accepted from {0} KUMPL040I New DP client connection accepted from
address {1} port {2} bound to application {0} address {1} port {2}
{3} attribute group {4}
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KUMPL041I DP client {0} from address {1} port {2}
KUMPL032I UDP inactivity time expired. Session disconnected from metafile server.
disconnect for {0} port {1}. Application
Explanation: No additional information is available
{2} attribute group {3} management
for this message.
ended.
Explanation: No additional information is available
KUMPL042I DP client {0} request for metafile {1}
for this message.
received.
Explanation: No additional information is available
KUMPL033I dp_BeginInput successful for
for this message.
application {0} attribute group {1} from
location {2}.
Explanation: No additional information is available
for this message.

Appendix E. Understanding informational, warning, and error messages 219

KUMPL043I • KUMPL060I

KUMPL043I DP metafile server processing KUMPL052W Contact metafile server {0}

completed. unsuccessful. Automatic connection
retry every {1} seconds.
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KUMPL044I Metafile {0} request successfully
completed. {1} records sent to client DP KUMPL053E {0} DP cannot open file {1} for
at {2}. monitoring. Unrecoverable errno {2}.
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KUMPL045E Metafile {0} request from {1} failed. File KUMPL054E File {0} deleted / no longer exists.
not found. Monitoring reset. Waiting for file
re-creation...
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KUMPL046E Metafile service client startup error.
Remote metafile service unavailable. KUMPL055I Agent and DP successfully
resynchronized. Monitor for file {0}
Explanation: No additional information is available
resumed.
for this message.
Explanation: No additional information is available
for this message.
KUMPL047E Connection to metafile server {0} port {1}
cannot be processed. Remote metafile
service unavailable. KUMPL056E New {0} connection from {1} rejected. No
Explicit Application Association record
Explanation: No additional information is available
found or SOURCE not unique
for this message.
Explanation: No additional information is available
for this message.
KUMPL048I Metafile service client successfully
connected to server at {0}. Ready for
request. KUMPL057I Metafile {0} validation successful.
Application {1} already registered to
Explanation: No additional information is available
agent by other DP. {2} NOT auto loaded.
for this message.
Explanation: No additional information is available
for this message.
KUMPL049E Metafile service client startup error. No
storage for request work area.
KUMPL058E Unable to clear file {0}. File COPY
Explanation: No additional information is available
CLEAR option reset to NO CLEAR.
for this message.
Explanation: No additional information is available
for this message.
KUMPL050I Metafile server disconnected. Automatic
reconnect initiated.
KUMPL059I {0} DP automation server active
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KUMPL051E Metafile server send failed for metafile
{0}. Insufficient storage. KUMPL060I {0} {1} automation activity completed,
status {2}
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.

220 IBM Tivoli Monitoring: Problem Determination Guide

 KUMPL061I • KUMPL081I

KUMPL061I {0} {1} automation activity completed, KUMPL070I Generate command for metafile {0}
status {2}, result [{3}] received.
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KUMPL062I {0} {1} automation activity beginning for KUMPL074I TCP connection outage detected. Session
command [{2}] parameter [{3}] at location disconnect for {0} port {1}. Application
{4} <{2}> attribute group <{3}> management
ended.
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KUMPL063E {0} {1} automation activity {2} not
performed. Data source {3} offline KUMPL075I File {0} switched or re-creation detected.
Restart file monitoring from the
Explanation: No additional information is available
beginning of the file.
for this message.
Explanation: No additional information is available
for this message.
KUMPL064I {0} {1} remote automation activity
beginning for command [{2}] parameter
[{3}] at location {4} KUMPL076I Monitoring switched from file {0} to
new file {1}.
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KUMPL065I Situation {0} filter add dispatched to {1}.
Rule[{2}]. KUMPL077W Unable to obtain enough storage.
Attribute summarization process
Explanation: No additional information is available
stopped for attribute group <{0}>. Retry
for this message.
with shorter summary interval.
Explanation: No additional information is available
KUMPL066I Situation {0} filter delete dispatched to
for this message.
{1}.
Explanation: No additional information is available
KUMPL078I HTTP DP client task active
for this message.
Explanation: No additional information is available
for this message.
KUMPL067I Report request dispatched to {0}.
Explanation: No additional information is available
KUMPL079I HTTP DP client task ended
for this message.
Explanation: No additional information is available
for this message.
KUMPL068E Unable to open configuration file {0}.
No metafiles will be loaded at startup
KUMPL080I {0} DP manager task active
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KUMPL069W Changing AttrType U to D for
attribute {0} in metafile {1} because KUMPL081I {0} DP manager task ended
server does not support Unicode data
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.

Appendix E. Understanding informational, warning, and error messages 221

KUMPL082I • KUMPL116I

KUMPL082I URL Add performed for {0} KUMPL107I SNMP trap monitor tasks not started per
request.
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KUMPL083I URL Remove performed for {0}
KUMPL108I SNMP management for MIB enterprise
Explanation: No additional information is available
{0} attribute group <{1}> started.
for this message.
Explanation: No additional information is available
for this message.
KUMPL084I Monitoring started for URL {0} User {1}
Interval {2} seconds
KUMPL109I SNMP management for MIB enterprise
Explanation: No additional information is available
{0} attribute group <{1}> ended.
for this message.
Explanation: No additional information is available
for this message.
KUMPL085I Monitoring stopped for URL {0} User {1}
Explanation: No additional information is available
KUMPL110I MIB data collection start request for
for this message.
agent: {0}
Explanation: No additional information is available
KUMPL101I Monitoring of SNMP traps enabled. {0}
for this message.
Explanation: No additional information is available
for this message.
KUMPL111I MIB data collection stop request for
agent: {0}
KUMPL102I Trap configuration definitions loaded
Explanation: No additional information is available
from file {0}
for this message.
Explanation: No additional information is available
for this message.
KUMPL112I SNMP management of network {0}
started.
KUMPL103I Monitoring of SNMP traps disabled. No
Explanation: No additional information is available
trap receiving port or API available.
for this message.
Explanation: No additional information is available
for this message.
KUMPL113I SNMP management of network {0}
ended.
KUMPL104I Network configuration discovery tasks
Explanation: No additional information is available
started.
for this message.
Explanation: No additional information is available
for this message.
KUMPL114I Managed Node List <{0}> has been
activated.
KUMPL105E Insufficient process authority for
Explanation: No additional information is available
executing ICMP procedures.
for this message.
Explanation: No additional information is available
for this message.
KUMPL115E Unable to activate Managed Node List:
{0}
KUMPL106I Network discovery tasks not started per
Explanation: No additional information is available
request.
for this message.
Explanation: No additional information is available
for this message.
KUMPL116I Monitoring for Managed Node List
<{0}> has been stopped.
Explanation: No additional information is available
for this message.

222 IBM Tivoli Monitoring: Problem Determination Guide

 KUMPL117E • KUMPS005E

KUMPL117E Unable to load trap configuration file {0} KUMPL131I Script <{0}> contains no valid data
record. Monitoring delayed for attribute
Explanation: No additional information is available
group {1}...
for this message.
Explanation: No additional information is available
for this message.
KUMPL120I ODBC source <{0}> does not exist or is
not accessible. Monitoring delayed for
attribute group <{1}>. KUMPL132E {0} DP cannot open file <{1}> for script
execution. Unrecoverable errno {2}.
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KUMPL121E ODBC source <{0}> does not exist or is
not accessible. Not waiting for source to KUMPL133I Monitoring for script {0} started.
become available. Monitoring failed. SourceName <{1}> Attribute group
<{2}>, Interval {3} seconds
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KUMPL122E ODBC DP cannot open source <{0}>
attribute group <{1}> for monitoring. KUMPL134I Monitoring for script {0} stopped.
errno {2}. Attribute group <{1}>.
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KUMPL123E ODBC DP cannot connect to source KUMPS001I Console input accepted.

<{0}> attribute group <{1}>. Monitoring
Explanation: No additional information is available
failed.
for this message.
Explanation: No additional information is available
for this message.
KUMPS002I Enter console command <Application
name or Metafile name or file name>
KUMPL124I Monitoring started for ODBC source
Explanation: No additional information is available
<{0}> attribute group <{1}>.
for this message.
Explanation: No additional information is available
for this message.
KUMPS003I Nothing entered. Please enter prompted
input.
KUMPL125I Monitoring stopped for ODBC source
Explanation: No additional information is available
<{0}> attribute group <{1}>.
for this message.
Explanation: No additional information is available
for this message.
KUMPS004E Interprocess communication unavailable
for console command server.
KUMPL126E Failed to retrieve data for source <{0}>
Explanation: No additional information is available
attribute group <{1}>, errno {2}.
for this message.
Explanation: No additional information is available
for this message.
KUMPS005E Unable to connect to console command
server on {0}
KUMPL130I Script <{0}> does not exist. Monitoring
Explanation: The most likely explanation is that
delayed for attribute group {1}, waiting
Universal Agent is not currently running.
for script creation...
Operator response:
Explanation: No additional information is available
for this message.

Appendix E. Understanding informational, warning, and error messages 223

KUMPS006E • KUMPS027I

KUMPS006E Input console command invalid. KUMPS017I Delete successful.

Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KUMPS007I Enter Application name or Metafile KUMPS018I DP shutdown completed.

name
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KUMPS019I DP shutdown failed, return code {0}
KUMPS008W Console to DP communication
Explanation: No additional information is available
unsuccessful. Command not processed.
for this message.
Explanation: No additional information is available
for this message.
KUMPS020I Import successfully completed for {0}
Explanation: No additional information is available
KUMPS009E Console to DP communication timed
for this message.
out. Retry, if DP is active.
Explanation: No additional information is available
KUMPS021I {0} already defined. Use REFRESH
for this message.
command to reload data definition.
Explanation: No additional information is available
KUMPS010I Console command return code {0}
for this message.
Explanation: No additional information is available
for this message.
KUMPS022I Import failed, return code {0}
Explanation: No additional information is available
KUMPS011I Active application definitions:
for this message.
Explanation: No additional information is available
for this message.
KUMPS023E Refresh failed. Specified application or
metafile not defined to selected DP.
KUMPS012I No application defined.
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KUMPS024E Refresh failed. Specification error.
KUMPS013E Delete failed. Specified application or
Explanation: No additional information is available
metafile not defined to selected DP.
for this message.
Explanation: No additional information is available
for this message.
KUMPS025I Confirm <Yes/No> to refresh {0}
Explanation: No additional information is available
KUMPS014E Delete failed. Logic error.
for this message.
Explanation: No additional information is available
for this message.
KUMPS026I Refresh cancelled for {0}
Explanation: No additional information is available
KUMPS015I Confirm <Yes/No> to delete {0}
for this message.
Explanation: No additional information is available
for this message.
KUMPS027I Refresh successful.
Explanation: No additional information is available
KUMPS016I Delete cancelled for {0}
for this message.
Explanation: No additional information is available
for this message.

224 IBM Tivoli Monitoring: Problem Determination Guide

 KUMPS028E • KUMPS048I

KUMPS028E {0} not defined. KUMPS039I Removing refreshed application

definition...
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KUMPS029I Defined application specification:
KUMPS040I Refresh cancelled.
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KUMPS030I Confirm <Yes/No> to shutdown DP
KUMPS041I Command in progress ...
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KUMPS031I Shutdown command cancelled.
KUMPS042W Command rejected. Console command
Explanation: No additional information is available
is still in progress. Active command is
for this message.
{0}
Explanation: No additional information is available
KUMPS032I Select an active DP:
for this message.
Explanation: No additional information is available
for this message.
KUMPS043E Command failed. Metafile not found.
Explanation: No additional information is available
KUMPS033E Invalid selection. Select a DP listed
for this message.
above:
Explanation: No additional information is available
KUMPS044E Load SNMP traps configuration
for this message.
command rejected by Non-SNMP DP.
Explanation: No additional information is available
KUMPS034E Import failed. Metafile definition error.
for this message.
Explanation: No additional information is available
for this message.
KUMPS045I Load SNMP traps configuration
command successful.
KUMPS035I Application already known to agent.
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KUMPS046E Load SNMP traps configuration
KUMPS036I Confirm <Yes/No> to accept existing command failed.
data definition for {0}
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KUMPS047E Command failed. SNMP trap
KUMPS037I Removing imported application configuration file not found.
definition...
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KUMPS048I Target DP set to {0}
KUMPS038I Import cancelled.
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.

Appendix E. Understanding informational, warning, and error messages 225

KUMPS049I • KUMPS068E

KUMPS049I Enter target DP name KUMPS059E Load SNMP managed node list
command failed.
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KUMPS050W SNMP application definition
incomplete. Application registration KUMPS060E Load SNMP managed node list file not
bypassed by Non-SNMP DP. found.
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KUMPS051E Load SNMP agent community name KUMPS061I Enter list file name
command rejected by Non-SNMP DP.
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KUMPS062I Enter metafile file name
KUMPS052I Load SNMP agent community name
Explanation: No additional information is available
command successful.
for this message.
Explanation: No additional information is available
for this message.
KUMPS063E Command not supported for packaged
product configuration.
KUMPS053W Load SNMP agent community name
Explanation: No additional information is available
command failed.
for this message.
Explanation: No additional information is available
for this message.
KUMPS064E Receive buffer too small for console
reply data.
KUMPS054W Load SNMP network name command
Explanation: No additional information is available
rejected by Non-SNMP DP.
for this message.
Explanation: No additional information is available
for this message.
KUMPS065I Do you wish to Import or Refresh this
metafile? <Import/Refresh/Cancel>
KUMPS055I Load SNMP network name command
Explanation: No additional information is available
successful.
for this message.
Explanation: No additional information is available
for this message.
KUMPS066I Import/Refresh cancelled for {0}
Explanation: No additional information is available
KUMPS056E Load SNMP network name command
for this message.
failed.
Explanation: No additional information is available
KUMPS067E Import failed. DP mismatch.
for this message.
Explanation: No additional information is available
for this message.
KUMPS057W Load SNMP managed node list
command rejected by Non-SNMP DP.
KUMPS068E Refresh failed. DP mismatch.
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KUMPS058I Load SNMP managed node list
command successful.
Explanation: No additional information is available
for this message.

226 IBM Tivoli Monitoring: Problem Determination Guide

 KUMPS069E • KUMPS097I

KUMPS069E Import failed. Same APPL name being KUMPS083E Error: {0} is not a valid console
used in another metafile. command
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KUMPS070E Refresh failed. Same APPL name being KUMPS084I Selecting {0} DP based on metafile type
used in another metafile.
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KUMPS090I Usage:
KUMPS071E Import failed. No valid APPL statement
Explanation: No additional information is available
found.
for this message.
Explanation: No additional information is available
for this message.
KUMPS091I kumpcon Delete [metafile name |
application name]
KUMPS072E Refresh failed. No valid APPL statement
Explanation: No additional information is available
found.
for this message.
Explanation: No additional information is available
for this message.
KUMPS092I Import [metafile name | application
name]
KUMPS073E Import failed. No valid NAME
Explanation: No additional information is available
statement found.
for this message.
Explanation: No additional information is available
for this message.
KUMPS093I Refresh [metafile name | application
name]
KUMPS074E Refresh failed. No valid NAME
Explanation: No additional information is available
statement found.
for this message.
Explanation: No additional information is available
for this message.
KUMPS094I Show [metafile name | application
name]
KUMPS075E Generate metafile function not
Explanation: No additional information is available
supported on this platform.
for this message.
Explanation: No additional information is available
for this message.
KUMPS095I Unpack [metafile name]
Explanation: No additional information is available
KUMPS076I Enter ODBC data source name and
for this message.
optional user= and pswd= parameters
Explanation: No additional information is available
KUMPS096I Validate [metafile name]
for this message.
Explanation: No additional information is available
for this message.
KUMPS081E Product specification initialization failed
Explanation: No additional information is available
KUMPS097I Generate [ODBC source name user=
for this message.
pswd=]
Explanation: No additional information is available
KUMPS082E Error: Too many parameters being
for this message.
supplied to console command: {0}
Explanation: No additional information is available
for this message.

Appendix E. Understanding informational, warning, and error messages 227

KUMPS098I • KUMPV012W

KUMPS098I List KUMPV004E Specification Error: NAME statement

not found or out of sequence in metafile
Explanation: No additional information is available
{0}
for this message.
Explanation: No additional information is available
for this message.
KUMPS099I LoadComm
Explanation: No additional information is available
KUMPV005E Specification Error: No attribute(s)
for this message.
found for APPL statement in metafile {0}
Explanation: No additional information is available
KUMPS100I LoadName
for this message.
Explanation: No additional information is available
for this message.
KUMPV006E Processing Error: Unable to copy
defined attributes to all SOURCEs, {0}
KUMPS101I LoadList [List file name]
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KUMPV007E Specification Error: Incomplete
KUMPS102I Trapcnfg attribute definition, {0}
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KUMPS103I Set Target DP name KUMPV008E Processing Error: Application

registration with agent failed for {0}
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KUMPS104I SHUTdown [Immed]
KUMPV009W Data Warning: Data value exceeds
Explanation: No additional information is available specification maximum. Specification
for this message. maximum in effect. {0}
Explanation: No additional information is available
KUMPV000I Validation completed successfully for this message.
Explanation: No additional information is available
for this message. KUMPV010E Application registration with agent
failed. Application already known to
KUMPV001E Definition Error: File not found {0} agent. {0}

Explanation: No additional information is available Explanation: No additional information is available

for this message. for this message.

KUMPV002E Specification Error: Only one KUMPV011W Data Warning: Negative COUNTER
application allowed in a metafile, {0} type input value forced to zero from {0}.

Explanation: No additional information is available Explanation: No additional information is available

for this message. for this message.

KUMPV003E Specification Error: Valid APPL KUMPV012W Data Warning: Non-Numeric input
statement not found in metafile {0} value forced to zero from {0}.

Explanation: No additional information is available Explanation: No additional information is available

for this message. for this message.

228 IBM Tivoli Monitoring: Problem Determination Guide

 KUMPV013E • KUMPV031E

KUMPV013E Data Error: Invalid SWITCH type KUMPV022E Metafile name input parameter
input value forced to OFF (0) from {0}. required
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KUMPV014W Data Warning: Invalid TIME type KUMPV023W Specification Warning: Commas not
input value forced to zero from {0}. allowed in ENUM list. Ignored
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KUMPV015W Specification Warning: Duplicate KUMPV024I Metafile with default extension assumed
attribute found in attribute group. - {0}
Delete duplicate: {0}
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KUMPV025I Processing input metafile {0}
KUMPV016W Specification Warning: Duplicate
Explanation: No additional information is available
attribute found of different type. Name
for this message.
changed to {0}
Explanation: No additional information is available
KUMPV026I Processing record {0}
for this message.
Explanation: No additional information is available
for this message.
KUMPV017E Specification Error: SNMP statement
rejected. Duplicate or it is not first
metafile record. KUMPV027I Blank input record skipped
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KUMPV018E Specification Error: SNMP attribute KUMPV028W Specification Warning: Replaced

ignored. No OID defined. invalid character(s) with _ in attribute
name: {0}
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KUMPV019E Specification Error: Attribute
definition found after LAST (Z) type KUMPV029W Specification Warning: NAME
attribute, ignored. {0} statement value truncated to default
maximum size of {0}
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KUMPV020W Server does not support Unicode
data, changing AttrType U to D for KUMPV030E Specification Error: Application name
attribute {0} size is less than minimum
three-character requirement - {0}
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KUMPV021E Processing Error: Program startup
initialization failed KUMPV031E Specification Error: Default maximum
of 63 attributes exceeded, use
Explanation: No additional information is available
KIB_MAXCOLS to override or split up
for this message.
attribute group: {0}

Appendix E. Understanding informational, warning, and error messages 229

KUMPV032W • KUMPV048E

Explanation: No additional information is available

KUMPV040E Specification Error: Invalid attribute
for this message.
type, {0}
Explanation: No additional information is available
KUMPV032W Specification Warning: Application
for this message.
name size greater than maximum.
Truncated to - {0}
KUMPV041E Specification Error: No data size
Explanation: No additional information is available
specification for Display, Record, or
for this message.
Object type attribute, ignored
Explanation: No additional information is available
KUMPV033E Specification Error: Statement
for this message.
bypassed until next NAME statement -
{0}
KUMPV042E Specification Error: Incomplete SOCK
Explanation: No additional information is available
SOURCE statement, ignored
for this message.
Explanation: No additional information is available
for this message.
KUMPV034E Specification Error: Statement
bypassed until next APPL statement - {0}
KUMPV043E Specification Error: No attribute group
Explanation: No additional information is available
name specified on NAME statement
for this message.
Explanation: No additional information is available
for this message.
KUMPV035W Processing Warning: Existing
application specification assumed.
Metafile already defined - {0} KUMPV044W Specification Warning: Attribute
group name truncated to {0}
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KUMPV036E Specification Error: More than one
FILE SOURCE per NAME statement, KUMPV045W Specification Warning: Invalid data
ignored type specified. POLL data assumed
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KUMPV037E Specification Error: Invalid SOURCE KUMPV046W Specification Warning: TTL not
statement, ignored specified. Default value assumed. {0}
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KUMPV038E Specification Error: No application KUMPV047W Specification Warning: COPY mode

name specified on APPL statement invalid for EVENT type FILE SOURCE.
TAIL mode in effect
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KUMPV039E Specification Error: Incomplete
attribute specification, ignored KUMPV048E Specification Error: Short or Long data
type only valid for attribute group
Explanation: No additional information is available
without delimiter, ignored
for this message.
Explanation: No additional information is available
for this message.

230 IBM Tivoli Monitoring: Problem Determination Guide

 KUMPV049W • KUMPV065E

KUMPV049W Specification Warning: Invalid SOCK KUMPV057E Specification Error: Application

SOURCE code type, ASCII default rejected. Total attribute data size
assumed. exceeded maximum supported limit of
8192 for attribute group {0}.
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KUMPV050W Specification Warning: Sample
frequency interval resets to default KUMPV058W Specification Warning: Table
minimum. sampling interval too small. Default
minimum value assumed. {0}
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KUMPV051W Specification Warning: Event
frequency interval resets to default KUMPV059W Specification Warning: KEY
minimum. specification for attribute in non-KEY
attribute group, ignored.
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KUMPV052W Specification Warning: ATTRIBUTES
statement delimiter characters not KUMPV060E Specification Error: SNMP MIB
enclosed by quotes. Assumed delimiter attribute OID is invalid or unsupported.
{0} {0}
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KUMPV053E Specification Error: Customer KUMPV061W Specification Warning: ATOMIC

application name beginning with Tivoli specification for numeric attribute,
reserved character K is not supported. changing to non-ATOMIC.
{0}
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KUMPV062E Specification Error: Application name
KUMPV054W Specification Warning: Display or begins with Tivoli reserved name. {0}
Numeric data type maximum length
Explanation: No additional information is available
changed to maximum of 4000 from {0}.
for this message.
Explanation: No additional information is available
for this message.
KUMPV063E Specification Error: Attribute formula
definition invalid. {0}
KUMPV055E Specification Error: NAME statement
Explanation: No additional information is available
encountered without attribute definition
for this message.
of previous NAME statement. Ignored.
Explanation: No additional information is available
KUMPV064E Specification Error: CONFIRM
for this message.
statement specification invalid. {0}
Explanation: No additional information is available
KUMPV056E Specification Error: SOURCE host
for this message.
name cannot be resolved to address.
SOURCE specification ignored. {0}
KUMPV065E Specification Error: CANDLE
Explanation: No additional information is available
statement rejected. Duplicate or it is not
for this message.
first metafile record.
Explanation: No additional information is available
for this message.

Appendix E. Understanding informational, warning, and error messages 231

KUMPV066E • KUMPV083E

KUMPV066E Specification Error: Invalid attribute KUMPV075W Specification Warning: Invalid

filter keyword, must be +FILTER or attribute filter syntax, logic operation
-FILTER must be the same. OR in effect
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KUMPV067E Specification Error: Invalid attribute KUMPV076E Specification Error: Invalid attribute
filter syntax, must be enclosed in {}. {0} filter syntax, SCAN or MATCH filter
invalid for numeric attributes
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KUMPV068E Specification Error: Invalid attribute
filter syntax, must be enclosed in (). {0} KUMPV077E Specification Error: Invalid attribute
filter syntax, NUMBER filter invalid for
Explanation: No additional information is available
display type attributes
for this message.
Explanation: No additional information is available
for this message.
KUMPV069E Specification Error: Invalid attribute
filter syntax, undefined type {0}
KUMPV078E Specification Error: Same APPL name
Explanation: No additional information is available
already defined in another metafile.
for this message.
Request ignored. Duplicate application.
{0}
KUMPV070E Specification Error: Invalid attribute
Explanation: No additional information is available
filter syntax, offset specification {0}
for this message.
Explanation: No additional information is available
for this message.
KUMPV079E Specification Error: FILE specification
pattern invalid syntax. {0}
KUMPV071E Specification Error: Invalid attribute
Explanation: No additional information is available
filter syntax, offset larger than data size.
for this message.
{0}
Explanation: No additional information is available
KUMPV080E Specification Error: FILE specification
for this message.
pattern file extension definition invalid.
{0}
KUMPV072E Specification Error: Invalid attribute
Explanation: No additional information is available
filter syntax, compare string longer than
for this message.
data size. {0}
Explanation: No additional information is available
KUMPV081E Specification Error: FILE specification
for this message.
pattern contains invalid definition. {0}
Explanation: No additional information is available
KUMPV073W Specification Warning: Non-ASCII
for this message.
file name found but metafile not saved
in UTF-8 format.
KUMPV082E Specification Error: Attribute-specific
Explanation: No additional information is available
delimiter definition invalid. {0}
for this message.
Explanation: No additional information is available
for this message.
KUMPV074W Specification Warning: Invalid
attribute filter syntax, invalid logic
operation. OR assumed. {0} KUMPV083E Specification Error: Duplicate
INTERNAL OUTPUT statements for the
Explanation: No additional information is available
same destination {0}.
for this message.
Explanation: No additional information is available
for this message.

232 IBM Tivoli Monitoring: Problem Determination Guide

 KUMPV084E • KUMPV101E

KUMPV084E Specification Error: Invalid KUMPV093W Specification Warning: SUMMARY

INTERNAL statement type {0}. interval too large. Reset to default
maximum from {0}.
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KUMPV085E Specification Error: Incomplete
INTERNAL statement definition. KUMPV094I Metafile unpack successful to output
file {0}.
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KUMPV086E DPLOG registration failed. Report
Unavailable. KUMPV095E Metafile unpack failed.
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KUMPV087E POST DP unable to register dpPost KUMPV096E Specification Error: Required SNMP
application with Agent. Job ended. attributes Agent_Info and Agent_Name
missing from SNMP attribute group {0}.
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KUMPV088E Validation unsuccessful
KUMPV097E Specification Error: ODBC Data
Explanation: No additional information is available
Source Name required.
for this message.
Explanation: No additional information is available
for this message.
KUMPV089E Same type DP is already active in the
system. DP startup ended.
KUMPV098E Specification Error: First parameter in
Explanation: No additional information is available
//SQL statement must be SELECT or
for this message.
PROC=.
Explanation: No additional information is available
KUMPV090I Application metafile validation report
for this message.
saved in file {0}.
Explanation: No additional information is available
KUMPV099W Specification Warning: //SQL
for this message.
statement ignored in non-ODBC
metafile.
KUMPV091W Specification Warning: SUMMARY
Explanation: No additional information is available
attribute group defined without key
for this message.
attribute. Summarize by timestamp for
{0}.
KUMPV100E Specification Error: //SQL PROC=
Explanation: No additional information is available
statement missing stored procedure
for this message.
name.
Explanation: No additional information is available
KUMPV092E Specification Error: Total by summary
for this message.
specified for non-numeric attribute.
SUM specification ignored.
KUMPV101E Specification Error: ODBC metafiles
Explanation: No additional information is available
require a valid //SQL statement.
for this message.
Explanation: No additional information is available
for this message.

Appendix E. Understanding informational, warning, and error messages 233

KUMPV102E • KUMPV122W

KUMPV102E Specification Error: //SQL Select KUMPV110E Specification Error: APPL name
statement exceeds maximum length, contains non-ASCII characters.
statement ignored.
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KUMPV111E Specification Error: Non-ASCII
KUMPV103E Specification Error: //SQL Select characters detected in //NAME statement
statement missing FROM keyword, value: {0}.
statement ignored.
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KUMPV112E Specification Error: Non-ASCII
KUMPV104E Specification Error: //SQL PROC characters detected in //SOURCE
statement exceeds maximum length, statement value: {0}.
statement ignored.
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KUMPV113E Specification Error: Non-ASCII
KUMPV105E Specification Error: //SQL PROC characters detected in local host name.
statement missing close quote, statement SOURCE statement specification
ignored. ignored: {0}.
Explanation: No additional information is available Explanation: No additional information is available
for this message. for this message.

KUMPV106W Specification Warning: ODBC source KUMPV114W Specification Warning: Non-ASCII

statement contains invalid MaxRows characters detected in
value, using default value of {0}. ManagedSystemName parameter.
ManagedSystemName specification
Explanation: No additional information is available
ignored: {0}
for this message.
Explanation: No additional information is available
for this message.
KUMPV107W Specification Warning: Duplicate
//SQL statement ignored.
KUMPV120E KUMPV120 Reserved for
Explanation: No additional information is available
KUMP_MetaFile_Found
for this message.
Explanation: No additional information is available
for this message.
KUMPV108W Specification Warning: Invisible
ODBC tables require a sample interval,
using default value of {0}. KUMPV121E KUMPV121 Reserved for
KUMP_META_DP_Mismatch
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.
KUMPV109W Specification Warning: Pure event
ODBC tables require a sample interval, KUMPV122W Specification Warning: RECORDSET
using default value of {0}. count too large. Reset to default
maximum of {0}.
Explanation: No additional information is available
for this message. Explanation: No additional information is available
for this message.

234 IBM Tivoli Monitoring: Problem Determination Guide

 KUMPV123W • KUMPV138W

KUMPV123W Specification Warning: Default KUMPV131W Specification Warning: Invalid

maximum of 64 NAME statements attribute PRECISION definition
exceeded, use KUMA_MAX_ ignored. {0}
ATTRGROUPS_PER_APPL to override
Explanation: No additional information is available
or split up metafile.
for this message.
Explanation: No additional information is available
for this message.
KUMPV132W Specification Warning: Invalid
attribute SCALE definition ignored. {0}
KUMPV124E Specification Error: Maximum of 256
Explanation: No additional information is available
NAME statements exceeded.
for this message.
Explanation: No additional information is available
for this message.
KUMPV133W Specification Warning: PRECISION
value too large. Maximum specification
KUMPV125E Specification Error: Found duplicate in effect. {0}
attribute group name {0}
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KUMPV134W Specification Warning: SCALE value
KUMPV126W Specification Warning: TailByCount too large. Maximum specification in
value parameter not specified. TAIL effect. {0}
mode in effect.
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KUMPV135W Specification Warning: SCALE value
KUMPV127W Specification Warning: Invalid not allowed for non-numeric attribute -
TailByCount value specified. TAIL mode {0}
in effect.
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KUMPV136W Specification Warning: More than one
KUMPV128W Specification Warning: TailByCount attribute found in table that contains
value exceeds maximum of 5000. TAIL RECORD type attribute
mode in effect.
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KUMPV137W Specification Warning: Multiple
KUMPV129W Specification Warning: Multiple SOURCE statements require the
mode parameters not supported. Extra ManagedSystemName parameter
parameter ignored - {0}
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.
KUMPV138W Specification Warning: Double quotes
KUMPV130W Specification Warning: Invalid not supported around SCRIPT file
attribute CAPTION definition ignored. name, use single quotes instead
{0}
Explanation: No additional information is available
Explanation: No additional information is available for this message.
for this message.

Appendix E. Understanding informational, warning, and error messages 235

KUMPV140E • KUMPV156W

keyword and refresh the metafile or recycle the

KUMPV140E Specification Error: SCRIPT file name
Universal Agent.
required.
Explanation: No additional information is available
KUMPV154W Specification Warning: Invalid
for this message.
WHEN keyword. The value for WHEN
should be one of the following
KUMPV150W Specification Warning: Invalid warehouse enablement options: R, H, D,
keyword ignored. {0} W, M, Q, Y.
Explanation: A syntax error was found processing the Explanation: The APPL statement has an invalid value
specified line in the metafile. Verify that the keyword is specified for the WHEN keyword.
followed by a space, or a list of space-separated values
Operator response: Verify that the WHEN keyword is
enclosed in curly braces. For example, AGTYP{AVG
specified using valid warehouse enablement options.
MAX} or AGTIM AGPRF{MIN}.
The value for WHEN should be one of the following:
Operator response: The keyword is ignored and R, H, D, W, M, Q, Y. For example, WHEN{R}.
processing of the metafile continues. Correct the invalid
keyword and refresh the metafile or recycle the
KUMPV155W Specification Warning: Invalid
Universal Agent.
OPTION keyword. The value for
OPTION should be one of the
KUMPV151W Specification Warning: Warehouse following: TYPE=, FONT=,
key value too large, ignored. {0} PRIMARYKEY=,
NONUMBERGROUPING, ALIGNLEFT,
Explanation: The WHKEY value is invalid. Verify that
ALIGNRIGHT, ALIGNCENTER,
the WHKEY keyword is a valid numeric value and
HISTORICALTIMESTAMP.
enclosed in curly braces. The warehouse key should be
a numeric value between 0 and 99. For example, Explanation: The value for the OPTION keyword is
WHKEY{0}. invalid. The OPTION keyword should specify a valid
option that is enclosed in curly braces. The valid
Operator response: The keyword is ignored and
options are TYPE=, FONT=, PRIMARYKEY=,
processing of the metafile continues. Correct the invalid
NONUMBERGROUPING, ALIGNLEFT, ALIGNRIGHT,
keyword and refresh the metafile or recycle the
ALIGNCENTER, HISTORICALTIMESTAMP. For
Universal Agent.
example, OPTION{PRIMARYKEY=1}.
Operator response: The keyword is ignored and
KUMPV152W Specification Warning: Invalid
processing of the metafile continues. Correct the invalid
AGTYP keyword. Valid aggregation
keyword and refresh the metafile or recycle the
types are AVG, MIN, MAX, SUM, TOT,
Universal Agent.
EAR, LAT, HI, LOW.
Explanation: The value for the AGTYP keyword is
KUMPV156W Specification Warning: Invalid
invalid. The AGTYP keyword should specify a list of
BEHAV keyword. The value for BEHAV
aggregation types that are space separated and
should be one of the following:
enclosed in curly braces. The valid aggregation types
GAUGE, STATE, COUNT, PROPERTY,
are AVG, MIN, MAX, SUM, TOT, EAR, LAT, HI, LOW.
SAMPLECOUNT, PEAK, LOW.
For example, AGTYP{AVG MIN MAX}.
Explanation: The value for the BEHAV keyword is
Operator response: The keyword is ignored and
invalid. The BEHAV keyword should specify a valid
processing of the metafile continues. Correct the invalid
behavior that is enclosed in curly braces. The valid
keyword and refresh the metafile or recycle the
behaviors are GAUGE, STATE, COUNT, PROPERTY,
Universal Agent.
SAMPLECOUNT, PEAK, LOW. For example,
BEHAV{GAUGE}.
KUMPV153W Specification Warning: Invalid
Operator response: The keyword is ignored and
AGPRF keyword. Aggregation
processing of the metafile continues. Correct the invalid
preference should list aggregation type
keyword and refresh the metafile or recycle the
specified with AGTYP keyword.
Universal Agent.
Explanation: The value for the AGPRF keyword is
invalid. The aggregation preference should list one of
the aggregation types specified with the AGTYP
keyword. For example, AGPRF{AVG}.
Operator response: The keyword is ignored and
processing of the metafile continues. Correct the invalid

236 IBM Tivoli Monitoring: Problem Determination Guide

 KUMPV157W • KUMPV599E

attempting the operation again:

KUMPV157W Specification Warning: WHEN
keyword found after application help 1. Install the resource bundle message files in the
text. WHEN keyword ignored. directory in which the Universal Agent opens them.
2. Uninstall the Universal Agent software and reinstall
Explanation: No additional information is available
it.
for this message.

KUMPV158W Specification Warning: BEHAV

keyword must be used with numeric
attribute type, such as C or G. BEHAV
keyword ignored.
Explanation: No additional information is available
for this message.

KUMPV159W Specification Warning: AGTIM

keyword must be used with Time
attribute type. AGTIM keyword
ignored.
Explanation: No additional information is available
for this message.

KUMPV160W Specification Warning:

PRIMARYKEY value is non-numeric.
PRIMARYKEY parameter ignored.
Explanation: No additional information is available
for this message.

KUMPV161W Specification Warning:

PRIMARYKEY value is outside the
range of legal values. PRIMARYKEY
parameter ignored.
Explanation: No additional information is available
for this message.

KUMPV162W Specification Warning:

HISTORICALTIMESTAMP keyword
must be used with Time attribute type.
HISTORICALTIMESTAMP keyword
ignored.
Explanation: No additional information is available
for this message.

KUMPV170E Internal processing error

Explanation: No additional information is available
for this message.

KUMPV599E The message resource bundle file was

not opened.
Explanation: The Universal Agent did not find the file
that contains the messages because the installation of
the Universal Agent is incomplete. This message is
printed only in English.
Operator response: Do one of the following before

Appendix E. Understanding informational, warning, and error messages 237

238 IBM Tivoli Monitoring: Problem Determination Guide
Appendix F. Notices
This information was developed for products and services offered in the U.S.A.
IBM might not offer the products, services, or features discussed in this document
in other countries. Consult your local IBM representative for information about the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service might be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right
might be used instead. However, it is the user’s responsibility to evaluate and
verify the operation of any non-IBM product, program, or service.

IBM might have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not give you
any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing

IBM Corporation
North Castle Drive
Armonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM
Intellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia Corporation

Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS

PUBLICATION ″AS IS″ WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certain

transactions, therefore, this statement might not apply to you.

This information could include technical inaccuracies or typographical errors.

Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM might make improvements or
changes in the product(s) or the program(s) described in this publication at any
time without notice.

Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those Web
sites. The materials at those Web sites are not part of the materials for this IBM
product and use of those Web sites is at your own risk.

© Copyright IBM Corp. 2005 239

 IBM might use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact:

IBM Corporation
2Z4A/101
11400 Burnet Road
Austin, TX 78758 U.S.A.

Such information might be available, subject to appropriate terms and conditions,

including in some cases payment of a fee.

The licensed program described in this document and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program License Agreement or any equivalent agreement
between us.

Any performance data contained herein was determined in a controlled

environment. Therefore, the results obtained in other operating environments
might vary significantly. Some measurements might have been made on
development-level systems and there is no guarantee that these measurements will
be the same on generally available systems. Furthermore, some measurement
might have been estimated through extrapolation. Actual results might vary. Users
of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of

those products, their published announcements or other publicly available sources.
IBM has not tested those products and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products.

All statements regarding IBM’s future direction or intent are subject to change or
withdrawal without notice, and represent goals and objectives only.

This information is for planning purposes only. The information herein is subject to
change before the products described become available.

This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which

illustrate programming techniques on various operating systems. You might copy,
modify, and distribute these sample programs in any form without payment to
IBM, for the purposes of developing, using, marketing or distributing application
programs conforming to the application programming interface for the operating
system for which the sample programs are written. These examples have not been

240 IBM Tivoli Monitoring: Problem Determination Guide

 thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply
reliability, serviceability, or function of these programs. You might copy, modify,
and distribute these sample programs in any form without payment to IBM for the
purposes of developing, using, marketing, or distributing application programs
conforming to IBM’s application programming interfaces.

If you are viewing this information in softcopy form, the photographs and color
illustrations might not appear.

Trademarks
IBM, the IBM logo, IBMLink, AIX®, Candle, Candle Management Workstation®,
CT®, DB2, developerWorks, eServer, iSeries, Lotus, MVS™ Notes®, OMEGAMON,
OS/390®, OS/400®, Passport Advantage, pSeries, Rational, Redbooks, S/390, Tivoli,
the Tivoli logo, Tivoli Enterprise Console®, VTAM®, WebSphere, z/OS, and zSeries
are trademarks or registered trademarks of International Business Machines
Corporation in the United States, other countries, or both.

Microsoft®, and Windows are registered trademarks of Microsoft Corporation in

the United States, other countries, or both.

Java™ and all Java-based trademarks and logos are trademarks or registered
trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

Linux is a trademark of Linus Torvalds in the United States, other countries, or

both.

UNIX is a registered trademark of The Open Group in the United States and other
countries.

Other company, product, and service names might be trademarks or service marks
of others.

Appendix F. Notices 241

242 IBM Tivoli Monitoring: Problem Determination Guide
Index
Special characters conventions
typeface x
Tivoli Management Framework Reference Manual 108 Corba user exception 65
CPU consumption, high 68
createnode command 74
A createNode command 75
abends (core files), capturing 26 CT_CMSLIST 30
accessibility ix customer support
addSystem command 67 See support
agent
displays offline 62
not available 77 D
not starting on a Solaris system 77 data
Agent deploy prevent losing 89
Timeout 73 data, helpful types of 1
agent not uninstalling 49 database
agents backing up the 89
display offline 67 recovering the 89
not displaying in the navigator 76 restoring the 89
AMXUT7502E 27 DB2 UDB
AMXUT7512E error 49 user ID 89
Application Support Installer 29 DBCS
not accepted 61
diagnostic tool
B ACTION workspace 24
books diagnostic tools
feedback on vii DPLOG 23
online vii UAGENT application
ordering vii ACTION workspace 23
see publications viii DPLOG 23
browser mode DirectDraw thread loops 60
clear JAR cache 57 DNS registry key 30
help not displaying in 57 Dr. Watson 2
uninstall procedure 23
browser problems 26
E
ECO2029E 108
C education
clear JAR cache 57 see Tivoli technical training ix
client enable Tivoli Monitoring Services 60
logon error messages 51 encryption key setting error 32
set trace options 13 error
cmwras1.log 14 ECO2029E 108
command Error
wrules_check 106 0x80040707 31
command prompt Could not open DNS registry key 30
display tasks in the 22 error message
commands Failed connection to Tivoli Enterprise Portal Server 52
special characters x Reconnect Authorization Failed 55
syntax x Tivoli Enterprise Portal client cannot find Tivoli Enterprise
configureSystem 68 Portal Server 53
connectivity 52 Tivoli Enterprise Portal Server is not reconnecting 55
Connectivity errors
Tivoli Enterprise Portal on XP 54 Rule Check Utility 105
Tivoli Enterprise Portal Server lost contact with the Tivoli event
Enterprise Monitoring Server 55 Omegamon_Generic 99
connectivity problems 51 event forwarder 17
console mode Event IBM Tivoli Monitoring Event Forwarding tool error 30
Tivoli Enterprise Portal Server 22 events
contacting support 120 PARSING_FAILED status 99

© Copyright IBM Corp. 2005 243

events (continued) JRE 32, 58
TEC_ITM_OM_Situation_Sync_Error 105

K
F KDCB0_HOSTNAME 26
Failed to attach to the DB2 instance db2inst1 31 KDY1024E 76
FAQ KFW_CMW_RECYCLE_DELAY 55
see Frequently asked questions 25 KFWENV 60
firewall 82, 87 KFWITM215E 54
fixes, obtaining 120 KFWITM290E 76
Fixpack kfwras1.log 14
CNP196 25 KHD_MAX_ROWS_SKIPPED_PER_TABLE 29
Frequently asked questions 25 KHDRAS1_Mig_Detail.log 92
UNIX-based systems installation 26 khdras1.log
Windows installation 26 ORACLE or DB2 errors in the 94
KLVSQ000 71
KLVST005 71
G knowledge bases for support 119
kshsoap client fails 61
glossary, Tivoli Software viii
KUICCR099E 67
kumsnetd 83
kumstrap 83
H
HEAPDUMPs 58
help not displaying 57
Historical data
L
lcfd.log 27
incorrect 93
legal notices 239
not warehoused 93
library, IBM Tivoli Monitoring vii
too much 93
LINUX MONITORING AGENT V610Rnnn unable to install
agent 32
Linuz installation error 32
I listsystems command 76
IBM Software Support listSystems command 68
See support log
IBM Tivoli Data Warehouse database does not uninstall 49 turn on Tivoli Enterprise Portal Server trace 14
IBM Tivoli Enterprise Console Log agent
events not acknowledged 103 UNIX-based system 76
is disabled 102 logging
IBM Tivoli Enterprise Console event forwarder 17 built-in features 1
IBM Tivoli Monitoring Installation and Setup Guide 25 logon
IBM Tivoli Monitoring library vii error messages 51
IBM Tivoli Monitoring Service Console 19 logs 7
blocking access to the 21 agent 9
IBM Tivoli Monitoring Technology Service Console 19 Agent Deploy tool trace 14
IBM Tivoli Universal Agent 15 IBM Tivoli Enterprise Console 10
IBM V1.4.2 JRE errors 58 IBM Tivoli Enterprise Console Situation Update
information centers for support 119 Forwarder 18
installation IBM Tivoli Enterprise Console trace 17
problems 31 IBM Tivoli Monitoring upgrade toolkit 17
removing a failed Windows 45 IBM Tivoli Universal Agent trace 15
Installation incorrect, Tivoli Enterprise Monitoring Server 68
problems 25 RAS1 12
troubleshooting problems 25 reading 12
InstallShield error 30 Tivoli Enterprise Monitoring Server 7, 8, 10
instance, removing remotely 61 Tivoli Enterprise Portal browser client 7
Integrated Cryptographic Service Facility 70 Tivoli Enterprise Portal desktop client 8
Internet Tivoli Enterprise Portal Server 7
for product support 119 turn on client trace 13
IP:PIPE 26, 27 UNIX-based system 7
Upgrading from Tivoli Distributed Monitoring 11
Warehouse Proxy agent 9
J Warehouse Proxy trace 15
where to find 7
JAR cache
Windows 7
clearing the 23
Java VM heap dump 32
JAVACore 58

244 IBM Tivoli Monitoring: Problem Determination Guide

M R
Managed system 82 release notes 4
manuals Rule Check Utility error 105
feedback on vii rules
online vii not display 106
ordering vii Rules Check Utility 106
see publications viii
memory usage, high 58, 59
memory use, Tivoli Enterprise Monitoring Server 69
message 53
S
security
Tivoli Enterprise Portal Server has lost contact... 55
Windows local 90
Tivoli Enterprise Portal Server is still being initialized... 55
service console 19
Unable to process log on... 51
see IBM Tivoli Monitoring Service Console 21
User authorization has failed 51
Silent install error 32
messages
Situation Update Forwarder 18
built-in features 1
situations
MIB data collection 85
defined 82
MIB workspace 87, 88
not forwarded 96
MVS
Situations not firing 61
Tivoli Enterprise Monitoring Server 70
SNMP metafiles 85
SNMP-MANAGER Trap workspace 85
SQL0443N 92
N support
NETSUMMARY workspace 88 about 119
NetView menus contacting 120
unavailable 107 describing problems 122
network interface cards 30 determining business impact of problems 121
NETWORK workspace 87 information centers for 119
knowledge bases for 119
obtaining fixes 120
O on Internet 119
submitting problems 122
odadmin command 108
weekly update option 120
online publications
Support, IBM Software ix
accessing viii
SYSIBM:CLI:-805 92
for support 119
sysxlogins report 80
ordering publications vii, ix

P T
Take Action
performance problems 58, 59
Manage Start 87
popup blocker 57
Manage Stop 87
private interface 56
Take Action command 24
problem determination
TakeAction 88
built-in features 1
task
describing problems 122
IBM Tivoli Enterprise Console 96
determining business impact 121
TEC_ITM_OM_Situation_Sync_Error 105
information centers for 119
Technotes
knowledge bases for 119
subscribe to 4
submitting problems 122
viewing 4
problem determination features 1
Tecnhotes 4
problems, types of 4
terminology viii
process
Tivoli Enterprise Monitoring Server
send commands to a IBM Tivoli Monitoring
not releasing memory 69
Technology 19
Tivoli Enterprise Monitoring Server on distributed
publications
problems 67
accessing online viii
Tivoli Enterprise Monitoring Server on z/OS
feedback on vii
problems 69
for support 119
Tivoli Enterprise Monitoring Server private interface 56
online vii
Tivoli Enterprise Portal
ordering vii, ix
charts and graphs 83
Data is not returned to the 60
erratic sorting behavior 62
Q Tivoli Enterprise Portal help
Questions 25 cannot search 61
Queue Statistics workspace 29 problem 61

Index 245
Tivoli Enterprise Portal performance 58, 59
Tivoli Enterprise Portal Server
W
failed connection 52 Warehouse database
slow performance of the 65 user permission 94
turn on trace 14 warehouse migration tool 25
Tivoli Enterprise Portal Server does not start 51 Warehouse Proxy
Tivoli Monitoring Services rows not present after upgrade 29
enable 60 Warehouse Proxy agent 15, 92
Tivoli software information center viii failed to export data 93
Tivoli technical training ix WAREHOUSEMIGLOG table 25
TIVOLI_DATA_WAREHOUSE ODBC application 80 weekly update support option 120
tools, used to diagnose problems 7 window
trace 7 Java(TM) Plug-in Control Panel 23
Agent Deploy tool trace 14 Logon 51
IBM Tivoli Enterprise Console Situation Update Trace Options 13
Forwarder 18 Windows
IBM Tivoli Enterprise Console trace 17 Frequently asked questions 26
IBM Tivoli Monitoring upgrade toolkit 17 Local Security Settings 90
IBM Tivoli Universal Agent trace 15 Security logging 26
setting 13 user ID 89
setting a client 13 Workflows
Warehouse Proxy trace 15 enable Tivoli Monitoring Services 60
trace logs 7 wrules_check 106
trademarks 241
training, Tivoli technical ix
TRAP workspace 85 Z
Troubelshooting zOS
SNMP data provider 85 Tivoli Enterprise Monitoring Server 70
troubleshooting
browser mode 57
connectivity 51
IBM Tivoli Monitoring Technology Service Console for 19
logon error messages 51
setting a trace 13
Troubleshooting
IBM Tivoli Enterprise Console event synchronization
problems 95
Tivoli Enterprise Monitoring Agent deploy 73
Tivoli Enterprise Monitoring Server 67
Tivoli Enterprise Monitoring Server on distributed 67
Tivoli Enterprise Monitoring Server on z/OS 69
Tivoli Enterprise Portal 57
Tivoli Enterprise Portal Server problems 65
Universal Agent problems 79
Windows 30
typeface conventions x

U
UAGENT application 23
Unable to create TEPS, return code = 3 31
Unexpected Signal: 4 occurred at PC=0xFEC3FDE4 32
Unhandled Exception 31
uninstallation
problems 45
Universal Agent
does not start 79
traps 82
upgrade toolkit 17
user ID
failed user authorization 51

V
Viewdepot command 76
VMWare 60

246 IBM Tivoli Monitoring: Problem Determination Guide




Printed in USA

GC32-9458-00