Tivoli IBM Tivoli Monitoring for Network Performance


Version 2 Release 1

Messages and Troubleshooting

SC31-6366-00
 Tivoli IBM Tivoli Monitoring for Network Performance
®


Version 2 Release 1

Messages and Troubleshooting

SC31-6366-00
For notices, see “Notices” on page 99.

First Edition June 2004

This edition applies to Version 2, release 1, modification 0 of IBM Tivoli Monitoring for Network Performance,
(Product Number 5698-FNP) and to all subsequent releases and modifications until otherwise indicated in new
editions
© Copyright International Business Machines Corporation 2004. All rights reserved.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
Preface . . . . . . . . . . . . . . . v MSG. . . . . . . . . . . . . . . . 45
Who Should Read This Guide . . . . . . . . v PERFM . . . . . . . . . . . . . . . 46
Product Publications . . . . . . . . . . . . v Documenting and Reporting Problems . . . . . 47
IBM Tivoli Monitoring for Network Performance Documenting any Problem . . . . . . . . 47
library . . . . . . . . . . . . . . . v Documenting ABEND Problems . . . . . . 49
Related publications . . . . . . . . . . vi Out of Memory Errors in Java Processes . . . 58
IBM Tivoli Monitoring for Network Documenting DOC Problems . . . . . . . 58
Performance information . . . . . . . . vi Documenting INCORROUT Problems . . . . 59
IBM z/OS Operating Systems publications . . vi Documenting PERFM Problems . . . . . . 60
IBM z/OS Communications Server Diagnosing Problems . . . . . . . . . . . 61
publications . . . . . . . . . . . . vi Finding Solutions . . . . . . . . . . . 61
IBM WebSphere Application Server Working with IBM Customer Support . . . . 61
publications . . . . . . . . . . . . vi Using Keywords . . . . . . . . . . . . 62
IBM DB2 publications . . . . . . . . . vi Building a Keyword String . . . . . . . . 62
Tivoli Data Warehouse publications . . . . vii Filling Out and Submitting the Problem
NetView Integrated TCP/IP Services Management Report . . . . . . . . . 64
Component publications . . . . . . . . vii
Terminology . . . . . . . . . . . . vii Chapter 6. Diagnostic Tools . . . . . . 65
Accessing publications online . . . . . . . vii Monitor Component . . . . . . . . . . . 65
Ordering publications . . . . . . . . . . vii Message Logs, Trace Logs, and Configuration
Accessibility . . . . . . . . . . . . . . viii XML File . . . . . . . . . . . . . . 65
Contacting software support . . . . . . . . viii Tivoli Common Directory . . . . . . . . 65
Conventions used in this guide . . . . . . . viii Types of Messages and Trace Logs . . . . . 65
Typeface conventions . . . . . . . . . . viii Monitor Logs and Serviceability Script
Operating System-Dependent variables and paths ix Locations . . . . . . . . . . . . . 66
Configuration XML File . . . . . . . . 67
Chapter 1. Introduction . . . . . . . . 1 Message and Trace Log Names . . . . . . 67
Message Log Format . . . . . . . . . 68
Chapter 2. Message Overview . . . . . 3 Trace Log Format . . . . . . . . . . 68
Trace Levels . . . . . . . . . . . . 70
Sources of Messages . . . . . . . . . . . . 3
Using the Command Line Interface for Trace
Message Format . . . . . . . . . . . . . 3
Settings . . . . . . . . . . . . . . . 70
Message Help . . . . . . . . . . . . . . 4
Dump Types . . . . . . . . . . . . . 71
Displaying Message Help by Clicking a Hyperlink
Web Application . . . . . . . . . . . . . 72
Message Number . . . . . . . . . . . . 5
Installation Logs . . . . . . . . . . . . 72
Accessing the Message Index . . . . . . . . 5
Message and Trace Logs . . . . . . . . . 73
Message and Trace Log Locations . . . . . . 74
Chapter 3. Messages . . . . . . . . . 7 Message and Trace Log Formats . . . . . . 74
Web Application Trace Components . . . . . 74
Chapter 4. Troubleshooting Overview 39 Audit Message . . . . . . . . . . . . 76
Troubleshooting Responsibilities for the Network IBM Tivoli Data Warehouse . . . . . . . . . 76
Systems Programmer . . . . . . . . . . . 41 Serviceability Tools . . . . . . . . . . . . 76
Troubleshooting Responsibilities for the Network Log XML Viewer . . . . . . . . . . . 76
Operator . . . . . . . . . . . . . . . 41 Monitor Documentation Collection Script . . . 76
Troubleshooting Responsibilities for the Capacity WebSphere Application Server Collector Tool . . 76
Planner . . . . . . . . . . . . . . . . 42
Chapter 7. Resolving Problems . . . . 77
Chapter 5. Classifying, Documenting, ABEND X'0D6' on Monitor Initialization . . . . . 78
and Reporting Problems . . . . . . . 43 ABENDX'DC3', X'EC3' in WebSphere Application
Classifying Problems . . . . . . . . . . . 43 Server . . . . . . . . . . . . . . . . 78
ABEND or COREDUMP . . . . . . . . . 43 None of the Selected Portfolio Items Display Data 78
z/OS Abends . . . . . . . . . . . . 43 Some of the Selected Portfolio Items Display Data 79
AIX Application Core Dumps . . . . . . 44 Data from Previous Collection Periods is Missing . . 79
DOC . . . . . . . . . . . . . . . 44 Graphs are Missing Titles and Labels Only on z/OS
INCORROUT . . . . . . . . . . . . . 45 Systems . . . . . . . . . . . . . . . 80

© Copyright IBM Corp. 2004 iii

Graphs Do Not Generate on the z/OS System . . . 81 Using the Log XML Viewer . . . . . . . . . 88
Graphs Do Not Generate on the AIX System . . . 81 Using the Wrapper Script . . . . . . . . . 88
When You Sign On to the User Interface, You are Query String Terminology . . . . . . . . 89
not Provided the Proper Authority . . . . . . 82 Using JVM Directly . . . . . . . . . . . 89
LTPA Token Expired . . . . . . . . . . . 82 Query String Syntax . . . . . . . . . . 90
Message FNPU004E is Received . . . . . . . 82 Filter Predicate . . . . . . . . . . . . 92
DB2 Deadlock Occurs While Running an Extract, Conditional Operators Used in Filter Predicate
Transform, and Load Process . . . . . . . . 83 Expressions . . . . . . . . . . . . 92
The Connection between WebSphere Application Boolean Operators . . . . . . . . . . 92
Server and the Monitor is Refused . . . . . . . 83 True Keyword . . . . . . . . . . . 92
Report Draws but No Graph or Chart is Displayed 83 Examples . . . . . . . . . . . . . . . 92
Row Set Not Found Error is Received . . . . . 83 Error Handling . . . . . . . . . . . . . 93
Warehouse Enablement Pack Installation Does Not Troubleshooting . . . . . . . . . . . . . 93
Complete . . . . . . . . . . . . . . . 84 Boolean Operators Require Parentheses . . . . 93
Error in the TWH-CDW_DATA.generic File. . . . 84 Using Quotation Marks in the Query String . . 93
Web Browser Error Message . . . . . . . . . 84 File Names with Spaces . . . . . . . . . 94
Unexpected Web application User Interface Results 84 Enabling Log XML Viewer Tracing . . . . . 94
Known Exceptions . . . . . . . . . . . . 84
Appendix B. The itmnp.properties File 95
Appendix A. Log XML Viewer . . . . . 87
Overview . . . . . . . . . . . . . . . 87 Notices . . . . . . . . . . . . . . 99
Packaging . . . . . . . . . . . . . . . 87 Programming Interfaces . . . . . . . . . . 100
Installing the Log XML Viewer . . . . . . . . 87 Trademarks . . . . . . . . . . . . . . 100
Installing on a z/OS System . . . . . . . . 87
Installing on a Distributed System . . . . . . 88
Index . . . . . . . . . . . . . . . 101
Uninstalling on a Distributed System . . . . . 88

iv IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting

Preface
The IBM® Tivoli® Monitoring for Network Performance product monitors the
performance of networks and systems in an enterprise environment. The IBM Tivoli
Monitoring for Network Performance: Messages and Troubleshooting Guide provides
information about messages and troubleshooting techniques to help in using the
IBM Tivoli Monitoring for Network Performance product.

Who Should Read This Guide

This guide is for network systems administrators who are responsible for ensuring
the availability of network resources.
v Planning for and overseeing product installation
v Troubleshooting system and performance problems
v Analyzing performance data for problem determination
v Providing historical performance data for trend analysis
v Supervising and training network operators

Readers should be familiar with the following topics:

v The z/OS® operating system and its associated concepts
v The AIX® operating system and its associated concepts
v UNIX® System Services TCP/IP
v Performance monitoring concepts

Product Publications
This section lists publications in the IBM Tivoli Monitoring for Network
Performance library and related documents. It also describes how to access Tivoli
publications online and how to order Tivoli publications.

IBM Tivoli Monitoring for Network Performance library

The following documents are available in the IBM Tivoli Monitoring for Network
Performance library:
v Planning, Installation, and Configuration for IBM Tivoli Monitoring for Network
Performance , SC31-6363-00
Provides network systems administrators the information to effectively plan for
the introduction of the product into their enterprise. This book also provides the
information to install the product into a WebSphere® Application Server
environment and configure other components in your enterprise to work with
the product.
v IBM Tivoli Monitoring for Network Performance Operator Guide, SC31-6365-00
Contains information about tasks that operators commonly perform.
v IBM Tivoli Monitoring for Network Performance Administrator Guide, SC31-6364-00
Contains information about tasks that administrators commonly perform.
v IBM Tivoli Monitoring for Network Performance Messages and Troubleshooting Guide,
SC31-6366
Contains a catalog of all messages and their explanations, plus additional
troubleshooting information to help you diagnose problems.

© Copyright IBM Corp. 2004 v

 v Tuning IBM Tivoli Monitoring for Network Performance, SC31-6363-00
Provides guidance for making IBM Tivoli Monitoring for Network Performance
run at peak performance in your environment, available at this Web address:
http://www.ibm.com/software/tivoli/products/monitor-net-performance/
v IBM Tivoli Monitoring for Network Performance Readme, GI10-3255-00
Contains late-breaking information about installing and using the product. This
information corrects and supersedes documentation in the product package.
Revised versions of this document might be available at this Web address:
http://www.ibm.com/software/tivoli/products/monitor-net-performance/
v IBM Tivoli Monitoring for Network PerformanceVersion 2.1 Warehouse Enablement
Pack, Version 1.1.0.0 Implementation Guide for Tivoli Data Warehouse, Version 1.2,
SC31-6793-00
Describes how to use this warehouse enablement pack to extract data from IBM
Tivoli Monitoring database and load it into the Tivoli Data Warehouse database.

Related publications
The documents listed in this section also provide useful information.

IBM Tivoli Monitoring for Network Performance information

You can find additional product information on the IBM Tivoli Monitoring for
Network Performance Web site:

http://www.ibm.com/software/tivoli/products/monitor-net-performance/

IBM z/OS Operating Systems publications

The IBM Tivoli Monitoring for Network Performance monitor component runs on
UNIX System Services (USS), which is part of the z/OS operating system. You can
view the publications that support this product at the following Web site:

http://www.ibm.com/servers/eserver/zseries/zos/bkserv/

IBM z/OS Communications Server publications

Much of the information displayed by the IBM Tivoli Monitoring for Network
Performance Web application is retrieved from IBM z/OS Communications Server.
You can view the publications that support this product at the following Web site:

http://www.ibm.com/servers/s390/os390/bkserv/

IBM WebSphere Application Server publications

WebSphere Application Server hosts the Tivoli Monitoring for Network
Performance Web application and provides Secure Sockets Layer (SSL) security for
several components. Complete information about WebSphere Application Server is
available from the information center installed with the product. You can also view
the WebSphere Application Server information center at the following Web site:

http://www.ibm.com/software/webservers/appserv/library/

IBM DB2 publications

You can view the publications that support this product on the following Web site:

http://www-306.ibm.com/software/data/db2/

vi IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting

 If you are running DB2 Universal Database™ Enterprise Server Edition Version 8
Release 1, you can view the publications that support this product on the following
Web site:

http://www.ibm.com/software/data/db2/library/

Tivoli Data Warehouse publications

Tivoli Data Warehouse provides the long-term data repository for IBM Tivoli
Monitoring for Network Performance. You can view the publications that support
this product on the following Web site:

http://publib.boulder.ibm.com/tividd/td/TivoliDataWarehouse1.2.html

NetView Integrated TCP/IP Services Component publications

IBM Tivoli Monitoring for Network Performance uses the NetView Integrated
TCP/IP Services Component to perform autodiscovery of IP resources in your
enterprise. You can view the publications that support this product on the
following Web site:

http://publib.boulder.ibm.com/tividd/td/NetView7.1.4.html

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

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

Access the glossary by clicking the Glossary link on the left pane of the Tivoli
software library window.

Accessing publications online

The product media contains the publications that are in the product library. The
formats of the publications are PDF, BookManager®, and HTML. To access the
publications using a Web browser, open the infocenter.html file. The file is in the
appropriate publications directory on the product CD.

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 the IBM Tivoli Monitoring for
Network Performance link to access the product library at the Tivoli software
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.

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

Preface vii
 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, see the following Web site for a list of telephone numbers:

http://www.ibm.com/software/tivoli/order-lit/

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 all features of the graphical user
interface.

For additional information, see the Accessibility appendix in IBM Tivoli Monitoring
for Network Performance Planning, Installation, and Configuration Guide.

Contacting software support

Before contacting IBM Software Support with a problem, refer to the IBM Software
Support site by accessing the following Web address:

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

To access Tivoli support, click the Tivoli support link at the bottom right of the
page.

If you want to contact IBM Software Support, see the IBM Software Support Guide at
the following Web site:

http://techsupport.services.ibm.com/guides/handbook.html

The guide provides information about how to contact IBM Software Support,
depending on the severity of your problem, and the following information:
v Registration and eligibility
v Telephone numbers, depending on the country in which you are located
v Information you must have before contacting IBM Software Support

Conventions used in this guide

This guide uses several conventions for special terms and actions, operating
system-dependent commands and paths, and margin graphics.

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

viii IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting
 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 (words as words)
v New terms in text (except in a definition list)
v Variables and values you must provide
Monospace
v Examples and code 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

Operating System-Dependent variables and paths

This guide uses the UNIX convention for specifying environment variables and for
directory notation.

When using the Windows® command line, replace $variable with %variable% for
environment variables and replace each forward slash (/) with a backslash (\) in
directory paths. The names of environment variables are not always the same in
Windows and UNIX. For example, %TEMP% in Windows is equivalent to $tmp in
UNIX.

Note: If you are using the bash shell on a Windows system, you can use the UNIX
conventions.

Preface ix
x IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting
Chapter 1. Introduction
IBM Tivoli Monitoring for Network Performance monitors the performance of
networks and systems in your enterprise. Performance data from all monitored
systems is stored in a central database. This data is displayed by the Tivoli
Monitoring for Network Performance Web application and is also used as input for
report generation using Tivoli Data Warehouse. Tivoli Monitoring for Network
Performance meets your daily tactical needs as well as your long-term strategic
systems management goals, providing an effective way to gain control of
mission-critical network resources, performance issues, and workload distributions.

Tivoli Monitoring for Network Performance provides for the timely analysis of
performance related metrics such as response time, traffic flow, and system
workload. Using the Tivoli Monitoring for Network Performance Web application,
operators can monitor the performance of the network in an effort to anticipate
problems and resolve them before they occur. The performance data can be used to
detect bottlenecks and other potential problems, which eliminates the need for
network systems programmers to manually scan through extensive amounts of
performance data.

© Copyright IBM Corp. 2004 1

2 IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting
Chapter 2. Message Overview
This chapter is an overview of the messages for the IBM Tivoli Monitoring for
Network Performance product. It describes the source of messages, message
formats, and the Web application message help.

Sources of Messages
The source of messages in Tivoli Monitoring for Network Performance are
generated from certain related components and the product itself.

The following components can generate messages:

v WebSphere Application Server messages that are related to errors running the
Tivoli Monitoring for Network Performance Web application are:
– displayed on the WebSphere Administrative Console
– written to the WebSphere Application Server logs
The default log for the WebSphere Application Server address space on z/OS
is SYSPRINT.
The default logs for the WebSphere Application Server on the AIX system are:
- trace.log
- SystemOut.log
- SystemErr.log
v Messages that are related to the automatic discovery of resources by the
NetView Integrated TCP/IP Services Component are displayed in the NetView
Integrated TCP/IP Services Component product message area.
v Messages related to receiving events generated by Tivoli Monitoring for
Network Performance are found in the message areas and logs for Tivoli
NetView® for z/OS or the IBM Tivoli Enterprise Console® product.

Tivoli Monitoring for Network Performance also generates its own messages, and
these messages can be found in the following locations:
v The message status bar of the WebSphere Application Server on the WebSphere
Administrative Console.
v The z/OS system console or in SYSLOG.
v The message logs.
v The Tivoli Monitoring for Network Performance user interface.

Message Format
A message contains the following information:
v A message ID, for example, FNPxnnnz ,
FNP Is the identifier for messages generated by the Tivoli Monitoring for
Network Performance program.
x Indicates what component generated the message, as follows:
D Database messages.
I Installation messages.

© Copyright IBM Corp. 2004 3

 M General monitor messages.
T Monitor messages issued while collecting data from z/OS
Communication Server network management interfaces. The
monitor process that issues these messages is called the data
collection server.
U User interface messages.
W Tivoli Monitoring for Network Performance WebSphere
component messages.
nnn Is the message number.
z Is a one-letter message type.
I Informational messages, which typically do not require
administrator or operator actions.
W Warning messages, which typically require actions.
E Error messages, which indicate a problem that you must resolve
before normal operation can continue.
v Message text and variables

Message Help
In the browser-based interface, you can use message help by clicking a hyperlink
message number or by opening the Task Assistant and using the Message Index.

4 IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting

Figure 1. An error message displayed in the work area.

Displaying Message Help by Clicking a Hyperlink Message

Number
When a message is displayed on your work area, the message includes the
following hyperlinks:
v The message number, for example, FNPU075E. To display the help information for
a message, click the message number.
v The Close Message indicator. To close the message, click the Close Message
hyperlink.

Accessing the Message Index

To access the messages from the Message Index, do the following:
1. Click the Show or Hide Task Assistant (?) icon on the title bar of the work
area. To close the Task Assistant, click the icon again.
2. Click the Message Index icon (the three speech bubble with the exclamation
point in the Task Assistant action bar).
3. Expand the Message Index.
4. Expand FNP, which is the message prefix for Tivoli Monitoring for Network
Performance.

Chapter 2. Message Overview 5

 5. Select the message number from the navigation tree of message numbers or
type the message number in the field and click Enter.

Note: Message Help is only provided for Tivoli Monitoring for Network
Performance messages starting with the prefix letters of FNPU and FNPW. Refer to
the following chapter for information on other Tivoli Monitoring for Network
Performance messages.

6 IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting

Chapter 3. Messages
FNPD001E THE MONITOR CANNOT LOAD THE FNPD005E AN ERROR OCCURRED WHILE
DB2® UNIVERSAL DRIVER. INITIALIZING THE CLOUDSCAPE
DATABASE.
Explanation: The Tivoli Monitoring for Network
Performance monitor cannot find a DB2 type 4 driver Explanation: An unknown error occurred while
in its classpath. initializing the Cloudscape database.
Programmer Response: Verify that the db2j.jar file is Programmer Response: Check the drive where the
in the lib directory of the Tivoli Monitoring for Cloudscape database is located to see if there is enough
Network Performance monitor base installation disk space. The Cloudscape database location is defined
directory. in the itmnp.properties file by the DBCacheDirectory
property.
FNPD002E THE MONITOR CANNOT LOAD THE Verify that the db2j.jar file is in the lib directory of the
DB2 APPLICATION DRIVER. Tivoli Monitoring for Network Performance monitor
base installation directory. If the error persists, try
Explanation: The Tivoli Monitoring for Network
removing dbcache and restarting the monitor. Any
Performance monitor cannot find a DB2 type 2 driver
measurements stored in the dbcache will be lost.
in its classpath.
Programmer Response: Verify that the db2j.jar file is
FNPD006E AN ERROR OCCURRED WHILE
in the lib directory of the Tivoli Monitoring for
INITIALIZING DATABASE
Network Performance monitor base installation
CONNECTIVITY. THE MONITOR
directory. Verify that the db2client has been properly
EXITS.
set up.
Explanation: A critical error occurred while the Tivoli
Monitoring for Network Performance monitor was
FNPD003E AN ERROR OCCURRED
running database initialization routines.
CONNECTING TO THE CLOUDSCAPE
DATABASE. Operator Response: You might receive other messages
that will help determine what caused this error. DB2
Explanation: The Tivoli Monitoring for Network
might have been stopped. Verify that DB2 is active, and
Performance monitor was not able to create a
if it has been stopped and started, then start the
connection to the Cloudscape™ database.
monitor again.
Programmer Response: Check the drive where the
Programmer Response: Examine the monitor trace
Cloudscape database is located to see if there is enough
logs for further information.
disk space. The Cloudscape database location is defined
in the itmnp.properties file by the DBCacheDirectory
property. FNPD007I DATABASE INFORMATION FOR
THREAD: threadName DATABASE
If the error persists, try removing dbcache and
PRODUCT NAME: DatabaseProductName
restarting the monitor. Any measurements stored in the
DATABASE PRODUCT VERSION:
dbcache will be lost.
DatabaseProductVersion.
Explanation: This message is issued when the
FNPD004I THE CLOUDSCAPE DATABASE IS
different monitor processes connect to the database.
BEING DISABLED BECAUSE A
The product name and version of the database to
CONNECTION CANNOT BE
which the Tivoli Monitoring for Network Performance
ESTABLISHED.
monitor is connecting, and the thread name is
Explanation: The Cloudscape database was disabled displayed.
because the enable Cloudscape property in the
itmnp.properties file was set to NO.

© Copyright IBM Corp. 2004 7

FNPD008E • FNPI0008E

FNPD008E THE CONNECTION TO DB2 HAS FNPI0002I The resource named resource_name is
BEEN INTERRUPTED. THE MONITOR already defined.
IS ATTEMPTING TO RESTORE THE
Explanation: A resource with the same name as the
CONNECTION.
resource you are attempting to create is currently
Explanation: DB2 might have stopped or another DB2 configured within WebSphere Application Server.
error occurred. A network resource failure might have
The IBM Tivoli Monitoring for Network Performance
occurred.
product might already be installed.
Operator Response: If the connection is restored,
Administrator Response: Perform the uninstall
message FNPD009I is received, and no action is
process, then the installation. The resource might have
necessary. Ensure that the DB2 database is running and
been previously created manually. If that situation is
is accessible from the host where the Tivoli Monitoring
correct, then the resource must be removed manually
for NetWork Performance monitor resides.
using WebSphere administrative console.

FNPD009I THE CONNECTION TO DB2 HAS

FNPI0003I Creating resource resource_name.
BEEN RESTORED.
Explanation: The IBM Tivoli Monitoring for Network
Explanation: The Tivoli Monitoring for Network
Performance resource is being configured within
Performance monitor has established a new connection
WebSphere Application Server.
to the DB2 database.

FNPI0004I Created resource resource_name.

FNPD010I THE CONNECTION TO THE
CLOUDSCAPE DATABASE HAS BEEN Explanation: The resource was successfully configured
RESTORED. within WebSphere Application Server.
Explanation: The Tivoli Monitoring for Network
Performance monitor has established a new connection FNPI0005E The resource resource_name was not
to the Cloudscape database. created.
Explanation: An error was detected during the
FNPD011E THE MONITOR DISCOVERED creation of the resource.
DATABASE CACHE PROPERTIES
THAT ARE NOT VALID. Administrator Response: Contact IBM customer
DBCACHETIMEOUT: DBCacheTimeout support.
DBCACHEROWLIMIT:
DBCacheRowLimit FNPI0006I Removing resource resource_name.
DBCACHEDIRECTORY:
DBCacheDirectory Explanation: The Tivoli Monitoring for Network
Performance resource is being removed from
Explanation: The Tivoli Monitoring for Network WebSphere Application Server.
Performance monitor read database cache properties
from the itmnp.properties file. One or more of the
properties is not valid. FNPI0007I Removed resource resource_name.

Programmer Response: Ensure that the database Explanation: The Tivoli Monitoring for Network
cache properties in the itmnp.properties file meet the Performance resource has been successfully removed
stated requirements: from WebSphere Application Server.
v DBCacheDirectory cannot be empty.
v DBCacheTimeout must be greater than 0. FNPI0008E The resource resource_name could not be
found.
v DBCacheRowLimit must be greater than 0.
Explanation: The resource, that was to be removed by
the Tivoli Monitoring for Network Performance
FNPI0001E The object object_name is not defined.
uninstall process, could not be found in WebSphere
Explanation: An object in WebSphere Application Application Server.
Server returned a null value during an installation or
Administrator Response: This resource might have
uninstall process.
been previously removed by the Tivoli Monitoring for
Administrator Response: Contact IBM customer Network Performance uninstall process or manually
support. through the WebSphere Administrative Console.
Contact IBM customer support.

8 IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting

 FNPI0009I • FNPI0019E

If the problem persists, contact IBM customer support.

FNPI0009I Begin the configuration_name
configuration.
FNPI0013I Uninstalling the itmnp21 application.
Explanation: A configuration process has started for
the modification of resources in WebSphere Application Explanation: The itmnp21 application EAR file is
Server. being uninstalled from WebSphere Application Server.

FNPI0010I Installing the itmnp21 application. FNPI0014I The itmnp21 application has been
successfully uninstalled.
Explanation: The itmnp21 application Enterprise
Archive (EAR) file is being configured and deployed Explanation: The itmnp21 application was uninstalled
within WebSphere Application Server. and removed from WebSphere Application Server.

FNPI0011I The itmnp21 application has been FNPI0015I The itmnp21 application was not found.
successfully installed.
Explanation: An attempt to remove the itmnp21
Explanation: The itmnp21 application has been application from WebSphere Application Server failed
successfully installed in WebSphere Application Server. during the uninstall process.
Administrator Response: The itmnp21 application
FNPI0012E The itmnp21 application has not been might have already been removed from WebSphere
installed. Application Server. If not, contact IBM customer
support.
Explanation: An error was detected during the Tivoli
Monitoring for Network Performance installation while
attempting to deploy the itmnp21 application FNPI0016I Only the invocation was tested. No
Enterprise Archive (EAR) file within WebSphere action is taken.
Application Server.
Explanation: A test option was selected for the
Administrator Response: Review all the messages itmnp.sh script option. No configuration updates were
generated by the WebSphere environment after made in WebSphere Application Server.
message FNPI0010I is displayed. These messages are
from WebSphere administrative wsadmin program
processing and might indicate specific reasons for the FNPI0017I Saving the itmnp21 configuration.
installation failure. Explanation: The itmnp21 application configuration
Some common reasons for an unsuccessful itmnp21 information is being saved in WebSphere Application
application installation are: Server.
v The /tmp filesystem space is insufficient to expand
the itmnp21.ear file components. FNPI0018I The itmnp21 application configuration
v WebSphere filesystem space is insufficient to expand that was saved to the master
the itmnp21.ear file components. configuration was successful.
v The user ID that was used to perform the installation Explanation: The itmnp21 application configuration
does not have the necessary authority to access information was saved in WebSphere Application
WebSphere directories. Server.
v WebSphere Application Server name specified during
the setup for the installation is not a valid server FNPI0019E The AdminConfig save action caused an
name. It is either the server name that was given as exception return_code.
the field input value specified during the installation
on AIX in the installation wizard panel or the Explanation: An error occurred in WebSphere
environment variable that was used in setting up the Application Server while saving the itmnp21
itmnp.env z/OS file. application into the master configuration.
v There are underlying connection problems in the Administrator Response: The possible reasons for an
WebSphere environment that inhibits the discovery exception error are:
of WebSphere Application Server, which is the v WebSphere filesystem space is insufficient to save the
targeted application server name for the itmnp21 deployed itmnp21.ear file components.
binary files.
v An inconsistency or conflicts exists in WebSphere
v The save action took too long to finish its processing XML resource files that will prohibit the saving of
and caused WebSphere to time out. certain modifications made during the installation
v The itmnp21 application is already installed. process.

Chapter 3. Messages 9
FNPI0020I • FNPI0029I

v The modifications were made manually and saved completeObjectName. The WebSphere Application
through the WebSphere Administrative Console Server has not been started or is not running on a node
while the Tivoli Monitoring for Network name.
Performance installation processing was running.
Administrator Response: Check the options for the
v The save action took too long to finish its processing WebSphere Application Server and node number that
and caused WebSphere to timeout. were previously specified.

Contact IBM customer support. Verify that your WebSphere environment does not have
MBean discovery problems. It could result in a failed
completeObjectName query.
FNPI0020I Starting itmnp21 configuration
processing. For a Network Deployment configuration, verify that
the Deployment Manager can reach the specified
Explanation: The Jacl script invocation for the itmnp21 WebSphere Application Server. If the problem persists,
application has started. contact IBM customer support.

FNPI0021I paramflag: parameter_flag FNPI0026I The current global security enabled state
Explanation: The parameter option flag was passed to is gs_state and the WebSphere security
the Jacl script from the shell script. related configuration settings have been
made. The global security enabled state
has not been altered.
FNPI0022I param: parameter_value
Explanation: The global security state was not
Explanation: The parameter associated with the changed by the installation process.
parameter flag was passed to the Jacl script from the
shell script.
FNPI0027I The WebSphere and Tivoli Monitoring
for Network Performance security
FNPI0023I The JMS server has not been installed settings validity check is being done.
or configured with the WebSphere
component. No configuration will be Explanation: The installation process begins the
performed for the internal JMS server security configuration steps checking for existing HTTP
queues. Transport definitions, Federal Information Processing
Standard (FIPS) state, and other possible conflicts
Explanation: The WebSphere component, internal before creating security objects related to the Tivoli
Java™ Message Service (JMS) server, has not been Monitoring for Network Performance Web application.
installed. The installation continues.
Administrator Response: Install the WebSphere FNPI0028W The FIPS setting is currently enabled.
internal JMS server component. The FIPS activation is not compatible
with the SSL configuration that is
enabled for the itmnp21 application.
FNPI0024W The HTTP Transport port_number is
Disable FIPS in the WebSphere
already defined with a non Tivoli
administrative console after the
Monitoring for Network Performance
installation process completes.
SSL configuration repertoire
ssl_repertoire. The installation process Explanation: The Federal Information Processing
must stop. Standard (FIPS) activation caused the itmnp21
application to fail in its ability to communicate because
Explanation: The installation cannot continue because
the Secure Sockets Layer (SSL) data encryption method
the specified port value is already defined and cannot
used by the Tivoli Monitoring for Network
be created by the Secure Sockets Layer (SSL)
Performance Web application is not FIPS-approved.
configuration process.
Administrator Response: Clear the FIPS check box on
Administrator Response: Change the port value to a
the Global Security page in WebSphere Administrative
non existing Hypertext Transfer Protocol (HTTP)
Console. Then stop and start WebSphere Application
Transport number.
Server.

FNPI0025E The completeObjectName MBean is not

FNPI0029I The FIPS object is not available to
available for the WebSphere Application
query. The installation process is unable
Server app_server on node node_name.
to check the current FIPS state.
Explanation: The Java Management Extensions (JMX)
Explanation: The Federal Information Processing
management MBean is NULL for object
Standard (FIPS) object for the global security custom

10 IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting

 FNPI0100I • FNPI0112I

properties in WebSphere environment has returned a

FNPI0108I The itmnp21 Web application
null value during the security setting validation phase
configuration and installation has
of the Tivoli Monitoring for Network Performance Web
started.
application installation process.
Explanation: The configuration and installation option
Administrator Response: If the FIPS setting is enabled
that was specified for the itmnp.sh shell script
on the Global Security page in WebSphere
agrument has started.
Administrative Console, clear the FIPS check box.
Then, stop and start WebSphere Application Server.
FNPI0109E The WebSphere Configuration Error
return code is return_code. All processing
FNPI0100I Tivoli Monitoring for Network
has stopped.
Performance processing has started.
Explanation: An error occurred during the installation
Explanation: The invocation of the shell script, which
or uninstall processing of the Tivoli Monitoring for
starts the installation or uninstall process, has begun.
Network Performance Web application within the
WebSphere environment. The return code is from the
FNPI0101E The operating system os_name is not WebSphere client scripting the wsadmin process. Any
supported. configurations or changes that were made during the
installation or uninstall processes have not been saved
Explanation: An installation of the Tivoli Monitoring to the WebSphere master configuration repository.
for Network Performance Web application has been
attempted on an unsupported operating system. The Administrator Response: The possible reasons for the
UNIX shell script can only be run on the z/OS UNIX configuration error are:
System Services (USS) system. v WebSphere Jacl script interpreter detected a syntax
error in the itmnp.jacl file and stopped all processing.
FNPI0103I Only the following options are possible: v The previous errors that were discovered during the
install, uninstall, and test. installation or uninstall process that generated other
WebSphere environment or Tivoli Monitoring for
Explanation: An option for the itmnp.sh shell script Network Performance specific messages.
was specified that is not a valid option. Select one of
the appropriate valid arguments for the itmnp.sh
It is possible that one of the following messages might
command and try again.
have been previously generated:
v FNPI0001E
FNPI0106I The itmnp21 Web application uninstall
v FNPI0002I
process has started.
v FNPI0005E
Explanation: The uninstall option that was specified
v FNPI0008E
for the itmnp.sh shell script argument has started.
v FNPI0012E
v FNPI0019E
FNPI0107I The itmnp21 Web application test has
started. v FNPI0025E

Explanation: The test option that was specified for the For further information, consult the message help for
itmnp.sh shell script agrument has started. any FNPI message type that you might have previously
The following tests are performed: seen before the message, FNPI0109E.
v The Simple Object Access Protocol (SOAP) provider
Contact IBM customer support.
connection is validated.
v The user ID and password settings are authenticated.
FNPI0112I The installation is complete. You must
v WebSphere Application Server is determined to have
recycle the WebSphere Application
started and is open.
Server app_server before running the
v The viability of the client scripting process and Tivoli Monitoring for Network
environment are checked. Performance Web application.
v The validation of Jacl scripting arguments is
Explanation: The installation process has been
performed.
successfully completed and all changes have been
saved in the WebSphere master configuration
repository. Certain configuration changes made during
the installation process are not available until the
WebSphere Application Server is recycled (stopped and
started). When you start the WebSphere Application

Chapter 3. Messages 11
FNPI0113I • FNPI0120I

Server, the itmnp21 application automatically starts.

FNPI0118W The minimum space for file_system
filesystem is not available for the
FNPI0113I Checking the minimum space itmnp21 installation. The z/OS primary
requirements for itmnp21 application allocation space is insufficient; however,
installation: space_tmp Kb space there might be enough space available
available for tmp_fs tmp filesystem in the secondary extents. To continue
tmp_min Kb is the recommended the installation, click Enter. To end the
minimum space_was Kb space available installation, type 1 and click Enter.
for was_fs WebSphere filesystem
Explanation: The file system that is associated with
was_min Kb is the recommended
tmp_fs or the file system that is associated with
minimum.
WebSphere environment does not meet the minimum
Explanation: A query is made for the temporary and recommended requirements to complete the installation
WebSphere filesystem minimum space requirements of the itmnp21 Web application. The deployment of the
before the installation process starts. itmnp21.ear file binary files will take space in both file
systems during the installation process. The tmp_fs file
system space will be available when the installation
FNPI0114I The itmnp.env runtime environment file completes and most space in WebSphere environment
has been created. Edit this file with will be available at the end of the installation process;
your customized settings and then run however, approximately 30 MB of file allocation space
the itmnp.sh script again. in WebSphere environment will still be permanently
Explanation: Initially, when the itmnp.sh shell script is used until the the itmnp21 Web application is
run, the itmnp.env file is created, which is configured uninstalled.
with default values. The itmnp.env file must be Administrator Response: Before continuing with the
customized for the installation and configuration installation, verify there is space available in the
options before you attempt to run the itmnp.sh install secondary extents for this hierarchical file system (HFS)
process. mounted file system that would be adequate to make
For information about customization of the up the difference between what was reported available
environment setting in the itmnp.env file, see the IBM in the previous message, FNPI0113I and what was
Tivoli Monitoring for Network Performance: Planning, recommended as the minimum amount of space.
Installation, and Configuration chapter about installing
the Web application on the z/OS operating system. FNPI0119E The SSL JKS file jks_file does not exist.
Administrator Response: Edit the itmnp.env file and All processing has stopped.
run the itmnp.sh command again. Explanation: An installation file is missing that is
needed to complete the installation process. The
FNPI0117I The current itmnp.env file is not the installation cannot continue without this file. The
latest level. The itmnp.env file has been installation process stops.
moved to the temporary file Administrator Response: The missing SSL Java Key
env_saved_file_name. Use the Store (JKS) file is part of the Tivoli Monitoring for
env_saved_file_name file as a reference for Network Performance installation packaging file set.
the new itmnp.env file. The two SSL JKS files that are shipped are included
Explanation: The installation or uninstall process of a with the rest of the following installation specific files:
new level of code is being attempted and the itmnp.sh v itmnpServerKeyStore.jks
shell script has detected an incompatible level for the v itmnpServerTrustStore.jks
itmnp.env environment file. All processing has stopped.
A new itmnp.env file has been created with the current
One or both of these files are missing. Check for prior
default values. The itmnp.env file that was previously
warning or error messages that might have been
used was backed up and saved under another file
generated before the installation process started.
name which uses a time stamp for uniqueness.
Administrator Response: Edit the itmnp.env file and Contact IBM customer support.
run the itmnp.sh command again.
FNPI0120I Stop the WebSphere Application Server
app_server.
Explanation: This option was selected during the
installation wizard sequence of steps to request a
recycle of the WebSphere Application Server after a
successful installation. The initial action by the

12 IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting

 FNPI0121I • FNPI0131E

installation wizard is to stop the WebSphere no value is provided, then the wsadmin value is used
Application Server. for the password.

FNPI0121I Start the WebSphere Application Server FNPI0126I Enter your password again to confirm
app_server. your password.
Explanation: This option was selected during the Explanation: You have been prompted to type your
installation wizard sequence of steps to request a WebSphere administrator password, WASADMIN_PASSWORD
recycle of the WebSphere Application Server after a environment variable, again so that the itmnp.sh shell
successful installation. The installation wizard starts the script can verify the accuracy of your entry.
WebSphere Application Server after it stopped.
FNPI0127E The WebSphere administrator password
FNPI0122W The minimum recommended space is not valid. The installation process
requirements have not been met. The ends.
installation process stops.
Explanation: The WebSphere administrator password,
Explanation: This action is the result of a previous WASADMIN_PASSWORD environment variable, is not valid
action in response to message FNPI0118W. If you elect to because the first value entered does not match the
end the installation process, the running of the subsequent entry. The installation or uninstall process
itmnp.sh shell script will end. cannot continue without the correct value for this
password setting. The itmnp.sh shell script exits.
FNPI0123I start: start_process_time option: option
install dir: install_dir OS: operating_system FNPI0128I Enter your DB2 user ID. If the field is
UI: userid itmnp21.ear: EAR file spec build left blank, the db2admin default value
level: build_level itmnp.env ver: is used.
env_version app install:
Explanation: If the itmnp.env file environment
start_app_install_time exit reason:
variable setting,DB2USER, is left blank, you will be
exit_reason end: end_process_time
prompted to enter the value during the start of the
Explanation: This is an information history log used itmnp.sh shell script installation or uninstall process. If
by service as an aid in problem determination. This no value is provided, then the db2admin is used for the
data can be useful in reviewing the current state of the user ID.
Web application by examining option, build level, and
exit reason variables. For example, determination can
FNPI0129I Enter your DB2 password. If the field is
be made as to whether or not the itmnp21.ear file was
left blank, the db2admin default value
successfully deployed within WebSphere Application
is used.
Server, uninstalled, or if the last action resulted in a
processing error. Also, date and time stamp of the Explanation: If the itmnp.env file environment
itmnp21.ear file and build level will help in variable setting,DB2PASSWD, is left blank, you are
understanding the exact level of code that has been prompted to enter the value during the start of
installed. itmnp.sh shell script installation or uninstall process. If
no value is provided, then the db2admin value is used
for the password.
FNPI0124I Enter your WebSphere administrator
user ID. If the field is left blank, the
wsadmin default value is used. FNPI0130I Enter your DB2 password again to
confirm your password.
Explanation: If the itmnp.env file, WASADMIN_USERNAME
environment variable setting, is left blank, you are Explanation: You have been prompted to type your
prompted to enter the value during the start of DB2 password, DB2PASSWD environment variable setting,
itmnp.sh shell script installation or uninstall process. If again so that the itmnp.sh shell script can verify its
no value is provided, then the wsadmin value is used accuracy.
for the user name.
FNPI0131E The DB2 password is not valid. The
FNPI0125I Enter your WebSphere administrator installation process ends.
password. If the field is left blank, the
wsadmin default value is used. Explanation: The DB2 password, DB2PASSWD
environment variable setting, is not valid because the
Explanation: If the itmnp.env file, WASADMIN_PASSWORD first value that was entered does not match the
environment variable setting is left blank, you are subsequent entry. The installation or uninstall process
prompted to enter the value during the start of cannot continue until the correct value for this
itmnp.sh shell script installation or uninstall process. If

Chapter 3. Messages 13
FNPI0132I • FNPI0336I

password setting is entered. The itmnp.sh shell script v The Tivoli Monitoring for Network Performance
exits. database has been created.

FNPI0132I Tivoli Monitoring for Network FNPI0201E The DB2 profile db2_profile_name does
Performance processing has finished. not exist.
Explanation: This is the end of the shell script Explanation: The Tivoli Monitoring for Network
invocation, which started the installation or uninstall Performance installation process cannot find the
process. db2_profile_name file that it needs to continue the
database creation. All processing ends and the database
is not created.
FNPI0133I The migration of User Roles is
complete. Administrator Response: Verify that DB2 is installed.
Also, verify the DB2 instance owner user name
Explanation: The previous settings for the itmnp21
specified for the installation is correct. If problem
deployed Web application User Roles were saved and
persists, contact IBM customer support.
now copied for this instance of the itmnp21.ear
installation.
FNPI0202E The creation of the Tivoli Monitoring
for Network Performance database
FNPI0134I Verify that your User Roles for
failed.
ItscAllAuthority are valid.
Explanation: Some reasons that could cause this
Explanation: Your secure monitor setting and User
message to be displayed are:
Roles settings for ItscAllAuthority might no longer be
valid. Verify that your AllAuthenticated and Everyone v The DB2 create database command failed.
settings are correct. v The DB2 connection failed.
v The import of sql file statements into the database
FNPI0135I The User Roles have been saved. schema failed.
v The db2start command failed.
Explanation: The previously defined User Roles
settings for the itmnp21 Web deployment have been Administrator Response: Verify that DB2 is installed.
saved in the WebSphere Application Server temp Also, verify the DB2 instance owner user name
directory before they are uninstalled. The User Role specified for the installation is correct. If problem
settings are contained within the ibm-application- persists, contact IBM customer support.
bnd.xmi file and are included in the deployed
itmnp21.ear file deployed binary files.
FNPI0335I You must select at least one option from
The next installation of the Tivoli Monitoring for the installation wizard.
Network Performance Web application will use these
Explanation: The installation wizard cannot continue
same settings for the User Roles settings, which are
until you select at least one option for the installation.
contained in the ibm-application-bnd.xmi file.
Administrator Response: Select an option and click
Next .
FNPI0200I The db2_processing_information.
Explanation: This message can display a variety of
FNPI0336I The language support cannot be
information concerning the state of the Tivoli
installed by itself unless component_name
Monitoring for Network Performance database creation
has been previously installed.
process.
Explanation: You cannot install language support if
Some information in this message is similar to the
you are not installing the Tivoli Monitoring for
following:
Network Performance Web application at the same time
v Database creation started. or in a previous installation.
v End the DB2 instance.
If you want to install only language support, then
v Connect to the database. Tivoli Monitoring Network Performance must have
v Disconnect from DB2 database. already been installed on your system. Select the
v Importing SQL tables to build the database schema. Language Support source file that you would like to
install. The default setting is the Language Support
v Importing the itm_np_dll file to build the database
source file included with the installation program. If
schema.
you have acquired a different Language Support source
v Drop the database. file, select that source file for the installation.
v Uncatalog the database.
Administrator Response: Complete the installation of

14 IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting

 FNPI0337I • FNPI0350I

the Tivoli Monitoring for Network Performance Web Administrator Response: Uninstall the Tivoli
application or complete the installation at the same Monitoring for Network Performance Web application
time as the language support installation. before installing it again.

FNPI0337I The Language Support source file is a FNPI0344I You must supply a valid password.
required field. Enter the location of the
Explanation: The password you supplied was not
Language Support source file.
valid. You must supply a valid password when you are
Explanation: The installation wizard needs to locate prompted.
the Language Support source file. This file is usually
Administrator Response: Enter a valid password.
located on the Tivoli Monitoring for Network
Performance installation media.
FNPI0345I You must supply a valid user ID.
Administrator Response: Enter or browse to the
location of the Language Support source file and click Explanation: The user ID you supplied was not valid.
Next. You must supply a valid user ID when prompted.
Administrator Response: Enter a valid user ID.
FNPI0338I This Language Support source file is not
valid. Enter a valid Language Support
source file. FNPI0346I You must supply a valid user ID and
password.
Explanation: The Language Support source file you
supplied is not valid. Explanation: The user ID and password are not valid.
You must supply a valid user ID and a valid password
Administrator Response: Enter a valid Language when prompted.
support source file.
Administrator Response: Enter a valid user ID and
password.
FNPI0339I You must select at least one language.
Explanation: You did not make a language support FNPI0347I You must supply a valid database name.
selection.
Explanation: The database name you supplied was
Administrator Response: Select one or more language not valid.
locales and click Next.
Administrator Response: Enter a valid database
name.
FNPI0340I The Tivoli Common Directory is being
created.
FNPI0348I You must supply valid port numbers.
Explanation: See message. The port numbers must be unique.
Explanation: The port numbers you supplied are not
FNPI0341I Cleaning up the Tivoli Common valid.
Directory log files.
Administrator Response: Enter valid port numbers.
Explanation: The installation and uninstall log files The port numbers must be unique.
from the Tivoli Common Directory are being removed
or cleaned up from your system.
FNPI0349I You must supply a valid DB2 port
number.
FNPI0342I Performing post-uninstallation steps.
Explanation: The DB2 port number you supplied was
Explanation: The installation wizard is uninstalling not valid.
the selected language support files.
Administrator Response: Enter a valid DB2 port
number. Examine your /etc/services file entry for this
FNPI0343I The Tivoli Monitoring for Network port specification.
Performance Web application has
already been installed. Uninstall the
Web application before installing it FNPI0350I You must supply a valid DB2 node
again. name.

Explanation: You attempted the installation of the Explanation: The DB2 node name was not valid.
Tivoli Monitoring for Network Performance Web Administrator Response: Enter a valid DB2 node
application over a previous installation. name. This is the node name used for DB2
communication to your database.

Chapter 3. Messages 15
FNPI0351I • FNPM005E

FNPI0351I You must supply a valid DB2 port FNPM002E THE MONITOR CANNOT action
number and node name. TRACE LOGGING INFORMATION
FROM THE Z/OS COMMUNICATIONS
Explanation: The DB2 port number and node name
SERVER DATA COLLECTION SERVER.
are not valid.
CODE: code_location
Administrator Response: Enter a valid DB2 port
Explanation: The monitor cannot connect to the data
number. Examine your /etc/services file entry for this
collection server to set or retrieve trace logging
port specification. Enter a valid DB2 node name. This is
information. The trace facility might not have
the node name used for DB2 communication to your
initialized successfully. The data collection server or the
database.
TCP/IP stack might not be active.
The value for action can be SET™ or GET.
FNPI0352E An error occurred during the installation
process. Examine the itmnp_install.log The code_location identifies the location within the
file for detailed message information. monitor code where this message is issued. It is used
by IBM customer support.
Explanation: The installation wizard has been notified
that an error was detected while installing and Operator Response: Verify that a TCP/IP stack is
configuring resources within WebSphere environment. active. Verify that the data collection server is active.
More detailed information is located in the Verify whether trace logging was initialized. See
itmnp_install.log file, which is located in the bin message FNPM010E, which indicates that trace logging
subdirectory of your specified installation location for was not initialized.
the Tivoli Monitoring for Network Performance
product. The default location is the
FNPM003E AN INTERNAL ERROR OCCURRED.
/opt/IBM/ITMNP21/bin directory.
CODE: code_location
Administrator Response: Examine the
Explanation: The monitor detected a condition that
itmnp_install.log file, correct the problem, and run the
should not occur.
installation program again. If problem persists, contact
IBM customer support. The code_location identifies the location within the
monitor code where this message is issued. It is used
by IBM customer support.
FNPI0353E An error occurred during uninstall
processing. Examine the Programmer Response: Contact IBM customer
itmnp_install.log file for detailed support.
message information.
Explanation: The installation wizard has been notified FNPM004E AN INTERNAL ERROR OCCURRED:
that an error was detected while installing and code_location
configuring resources within the WebSphere
environment. More detailed information concerning this Explanation: The monitor detected a condition that
problem is located in the itmnp_install.log file, which should not occur. The monitor failed to issue a
resides in the bin subdirectory of your specified message.
installation location for the IBM Tivoli Monitoring for The code_location identifies the location within the
Network Performance product. The default location is monitor code where this message is issued. It is used
/opt/IBM/ITMNP21/bin. by IBM customer support.
Administrator Response: Examine the Programmer Response: Contact IBM customer
itmnp_install.log file, correct the problem, and run the support.
installation program again. If problem persists, contact
IBM customer support.
FNPM005E MEMORY CANNOT BE ALLOCATED.

FNPM001I THE MONITOR IS INITIALIZING Explanation: The monitor attempted to allocate

WITH build_level BUILD LEVEL, os_arch memory but was not successful. The current data
ARCHITECTURE, os_name OPERATING collection task cannot be completed. The monitor
SYSTEM VERSION os.version. restarts the data collection task at the next time
interval.
Explanation: The monitor is initializing. This message
includes the current build level, which is a unique Programmer Response: Verify that the TSO region
string representing when the monitor was created. This size or MAXASSIZE, for the user ID running the
information is useful in the diagnosis of problems. The monitor, is set according to the guidelines in the
os_arch indicates the platform or architecture the Planning, Installation, and Configuration for IBM Tivoli
monitor is running on 390. Monitoring for Network Performance Guide. If you are

16 IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting

 FNPM006E • FNPM012E

running the monitor as a started procedure, consider Messages and Codes for a description of errno (displayed
increasing the region size. in decimal) and errnoJr codes.

FNPM006E THE MONITOR CANNOT ACCEPT A FNPM009E A LOG FILE PROPERTY SPECIFIED IN
CONNECTION ON THE server_port file_name IS NOT VALID:
SERVER PORT. property_key=property_value
FUNCTION=c_library_function
Explanation: The value of a message or trace log
ERRNO=errno ERRNOJR=0xerrnoJr
property in the file_name file is not valid. The value is
CODE: internal_code
ignored.
Explanation: The monitor attempted to accept a
Programmer Response: Verify that the message or
connection from an internal process but was not
trace log properties specified in the file_name file are
successful. The monitor uses two ports for the internal
valid. You must specify a valid, positive number for
processes. The first port, defined by the CSAPIport
maxFiles and maxFileSize. You must specify one of the
property in the itmnp.properties file, is used to handle
following for level: DEBUG_MIN, DEBUG_MID or
new requests to collect data. The second
DEBUG_MAX.
port,CSAPIport +1, is used when a trace level change is
requested. The server_port identifies what function was
attempted, but could not be performed. The monitor FNPM010E THE LOGGING FACILITY CANNOT
attempts to accept additional requests. The monitor BE INITIALIZED. CODE: code_location
attempts to restart data collection automatically.
Explanation: The monitor was not successful in
Operator Response: If you issued a command to initializing the message and trace logging facility. The
change the monitor trace level, try the command again. monitor continues without message or trace logging.
If that is unsuccessful, stop the command line interface
(CLI), and restart it. An attempt to read the itmnp.properties file might have
failed. An attempt to open the logging toolkit might
See the z/OS C/C++ Run-Time Library Reference for the have failed. An attempt to set the location of the
function list of expected errno (displayed as decimal) message or trace files might have failed. An attempt to
codes. create a message or trace log might have failed.
The code_location identifies the location within the
FNPM007E DATA CANNOT BE RECEIVED ON A monitor code where this message is issued. It is used
SOCKET. ERRNO=errno by IBM customer support.
ERRNOJR=0xerrnoJr CODE: code_location
Programmer Response: Verify that the
Explanation: The monitor attempted to read data on a /etc/itmnp/itmnp.properties file exists and that the
socket but was not successful. monitor has permission to read the file.
The code_location identifies the location within the
monitor code where this message is issued. It is used FNPM011E THE file_name FILE CANNOT BE READ;
by IBM customer support. THE DEFAULT VALUE FOR THE
TIVOLI COMMON DIRECTORY,
Operator Response: Verify that the TCP/IP stack is
tivoli_common_dir, WILL BE USED.
running.
Explanation: The monitor was not successful in
Programmer Response: See z/OS UNIX System Services
reading the file_name file. The monitor uses the default
Messages and Codes for a description of errno(displayed
value, tivoli_common_dir, for the Tivoli Common
in decimal) and errnoJr codes.
Directory.
Programmer Response: Verify that the file_name file
FNPM008E DATA CANNOT BE SENT ON A
exists and that the monitor has permission to read the
SOCKET. ERRNO=errno
file.
ERRNOJR=0xerrnoJr. CODE: code_location
Explanation: The monitor failed to send data on a
FNPM012E THE TIVOLI COMMON DIRECTORY
socket.
WAS NOT FOUND IN THE file_name
The code_location identifies the location within the FILE; THE DEFAULT VALUE,
monitor code where this message is issued. It is used tivoli_common_dir, WILL BE USED.
by IBM customer support.
Explanation: The monitor did not find the Tivoli
Operator Response: Verify that the TCP/IP stack is Common Directory specified in the file_name file. The
running. monitor uses the default value, tivoli_common_dir for
the Tivoli Common Directory.
Programmer Response: See z/OS UNIX System Services

Chapter 3. Messages 17
FNPM013E • FNPM021E

Programmer Response: Verify that the log.properties

FNPM017E THE file_name PROPERTY FILE
file contains the tivoli_common_dir property.
CANNOT BE LOADED.
Explanation: The monitor was unable to load the
FNPM013E A DUMP IS BEING REQUESTED FOR
file_name property file. This property file is required for
name COMPONENT. COMPLETION
the monitor to run.
CODE = X’completion_code’ REASON
CODE = X’reason_code’ Programmer Response: Verify that the
itmnp.properties file is in the /etc/itmnp directory.
Explanation: The monitor encountered an error. The
SVC dump was requested. The first digits of the
hexadecimal completion code are the system FNPM018E THE install_dir_key VARIABLE WAS
completion code and the last three are the user NOT SET. THE MONITOR WILL USE
completion code. THE DEFAULT INSTALL DIRECTORY:
default_install_dir
Operator Response: Notify your system programmer.
Explanation: The install_dir_key variable was not set.
Programmer Response: Investigate the reason for the
This variable is set by the itmnpMonitor.sh shell script
ABEND that caused the SVC dump.
and is required by the monitor. The monitor will use
the default installation directory, default_install_dir.
FNPM014E THE SVC DUMP FOR THE name
Operator Response: Stop and then start the Tivoli
COMPONENT HAS COMPLETED.
Monitoring for Network Performance monitor, after the
RETURN CODE = X’return_code’,
install_dir_key has been corrected in itmnpMonitor.sh.
REASON CODE = X’reason_code’
shell script.
Explanation: The SVC dump has completed and is
Programmer Response: Verify that the Tivoli
expected to be written to a dump data set. The
Monitoring for Network Performance monitor was
return_code and reason_code codes are from the SDUMP
started with the correct startup script. Verify that the
macro. The SDUMP macro return and reason codes are
install_dir_key is set in the itmnpMonitor.sh shell script.
documented in the z/OS MVS™ Programming:
Authorized Assembler Services Reference guide.
FNPM019E THE required_property PROPERTY WAS
Operator Response: Notify your system programmer.
NOT FOUND.
Programmer Response: Investigate the reason for the
Explanation: The Tivoli Monitoring for Network
ABEND that caused the SVC dump.
Performance monitor was unable to read the
required_property property from the itmnp.properties
FNPM015E THE TCP/IP STACK IS NOT file.
AVAILABLE.
Programmer Response: Verify that the required
Explanation: The monitor cannot collect or store data property is set in the itmnp.properties file.
without the TCP/IP stack. The monitor will start or
continue data collection when the TCP/IP stack is
FNPM020E A CRITICAL ERROR OCCURRED. THE
available.
MONITOR WILL EXIT.
Operator Response: Start the TCP/IP stack.
Explanation: The Tivoli Monitoring for Network
Performance monitor encountered a critical error.
FNPM016W SOME TRACE AND MESSAGE
Programmer Response: Investigate the causes for the
LOGGING CANNOT BE INITIALIZED.
critical error. Examine the z/OS system console and
THE MONITOR WILL CONTINUE
SYSLOG for more messages related to this problem.
WITH REDUCED TRACE AND
Examine the monitor message and trace logs for more
MESSAGE LOGGING.
information.
Explanation: The monitor was not able to successfully
initialize all message and trace logging functions. The
FNPM021E THE directory DIRECTORY SPECIFIED
monitor continues to initialize with reduced message or
BY THE property_key PROPERTY
trace logging.
CANNOT BE ACCESSED.
Programmer Response: Investigate the reason for
Explanation: The Tivoli Monitoring for Network
reduced message or trace logging. View the z/OS
Performance monitor must have write access to the
system console or SYSLOG for additional messages.
directory directory.
Programmer Response: Change the value of the
property_key property in the log.properties file or

18 IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting

 FNPM022I • FNPM030E

change the directory permissions so that the monitor is in the /etc/ibm/tivoli/common/cfg directory or the
can write to the directory. user defined override.

FNPM022I THE MONITOR INITIALIZATION IS FNPM027E The directory directory_name does not
COMPLETE. exist.
Explanation: The Tivoli Monitoring for Network Explanation: The itmnpPostMon.sh script attempted
Performance monitor has completed the initialization to copy files from the default directory, but the default
routines. The monitor starts collecting data when a directory does not exist.
configuration is received and successfully loaded. See
Administrator Response: Edit the itmnpPostMon.sh
message FNPM025I .
script and modify the entry for ITMNP_INSTALL_PATH to
point to the directory where the Tivoli Monitoring for
FNPM023E THE MONITOR RECEIVED AN Network Performance monitor code is installed.
INCORRECT CONFIGURATION.
Explanation: The Tivoli Monitoring for Network FNPM028E Unable to write access the directory
Performance monitor received a configuration that was directory_name.
not valid.
Explanation: The itmnpPostMon.sh script attempted
Programmer Response: Contact IBM customer to write access the specified directory but was not
support. successful.
Administrator Response: Verify that the current user
FNPM024E THE MONITOR RECEIVED AN ID has adequate permission to write access the
EMPTY CONFIGURATION. specified directory. The itmnpPostMon.sh script must
run by a user with root authority.
Explanation: The Tivoli Monitoring for Network
Performance monitor received an empty configuration.
The empty configuration is ignored and the monitor FNPM029E The user user_id is not defined in the
continues collecting data according to the current Unix System Services system.
configuration.
Explanation: The itmnpPostMon.sh script attempted
Programmer Response: Examine the WebSphere to use the specified user ID, but it is not defined to
Application Server logs to determine why it sent the UNIX System Services (USS).
Tivoli Monitoring for Network Performance monitor a
Administrator Response: Verify that the Job Control
configuration with no data. Correct any problems and
Language (JCL) jobs, FNPDEFID and FNPUAUTH, are
deploy the monitor configuration.
defined with the user IDs that have been run on the
system. Verify that the itmnpPostMon.sh script has
FNPM025I THE MONITOR RECEIVED AND been updated to reflect the user IDs that are defined in
SUCCESSFULLY LOADED A NEW the JCL jobs.
CONFIGURATION WITH DateGenerated
DATE.
FNPM030E The monitor setup failed to complete
Explanation: The Tivoli Monitoring for Network successfully.
Performance monitor received a new configuration
Explanation: The itmnpPostMon.sh script completed
from the WebSphere Application Server. The monitor
with errors.
successfully loaded the new configuration. The existing
configuration was replaced. Administrator Response: Verify that prior to running
this script, the Job Control Language (JCL) jobs
Programmer Response: No action is required.
FNPDEFID and FNPUAUTH were run and that the
Examine the configuration received by the monitor in
user ID and group defined in the JCL files match the
the logging directory.
definition for the user ID and group in the
itmnpPostMon.sh script.
FNPM026I THE MONITOR IS USING THE
Verify that the itmnpPostMon.sh script is being run by
DEFAULT LOGGING DIRECTORY:
a user with root authority.
default_logging_directory
This script can be run multiple times without causing
Explanation: The monitor was unable to load the
harm to the environment.
required log.properties file and is now using the
default logging directory.
Programmer Response: Verify that log.properties file

Chapter 3. Messages 19
FNPT002E • FNPT008E

active. Verify that the z/OS Communications Server

FNPT002E THE bad_data_type DATA TYPE FOUND
data collection server is active.
FOR THE THRESHOLD OR REARM
VALUE DOES NOT MATCH THE
expected_data_type DATA TYPE IN THE FNPT006E THE MONITOR CANNOT SEND A
DATA MODEL. REQUEST TO THE DATA
COLLECTION SERVER. CODE:
Explanation: The monitor detected a condition that
internal_code
should not occur. A threshold or rearm value in the
monitor definition was not the expected data type. Explanation: The monitor definition specifies a
collection of z/OS Communications Server data, but
Programmer Response: Contact IBM customer
the monitor cannot send a request for data to the data
support.
collection server. The data collection server or the
TCP/IP stack might not be active.
FNPT003W NO DATA WAS COLLECTED FROM
The monitor attempts to connect to the data collection
THE TCP/IP JOB NAMED
server once every interval as long as the monitor
tcpip_job_name BECAUSE NO VALID
definition is scheduled to collect this data.
DATA CATEGORIES WERE DEFINED.
Operator Response: Verify that a TCP/IP stack is
Explanation: The monitor attempted to collect data
active. Verify that the data collection server is active.
but did not find any valid z/OS Communications
Server data collection categories in the current monitor
definition. FNPT007E MEMORY CANNOT BE ALLOCATED.
Administrator Response: Verify that the monitor Explanation: The monitor attempted to allocate
definition specified in the Tivoli Monitoring for memory but was not successful.
Network Performance Web application includes z/OS
Communications Server data collection categories for Programmer Response: Verify that the TSO region
the tcpip_job_name specified in the message. size or MAXASSIZE, for the user ID running the
monitor, is set according to the guidelines in the
Programmer Response: Verify that the installed Planning, Installation, and Configuration for IBM Tivoli
versions of Tivoli Monitoring for Network Performance Monitoring for Network Performance Guide. If you are
monitor component and Web application are running the monitor as a started procedure, consider
compatible. increasing the region size, if possible.

FNPT004E THE VALUE FOR THE property_key FNPT008E THE SNAMGMT INTERFACE
PROPERTY IS NOT VALID. CANNOT BE INITIALIZED. CODE:
VALUE=property_value code_location
Explanation: The value specified in the Explanation: The monitor attempted to initialize the
itmnp.properties file for the property_key property is not SNAMGMT network management interface in
valid. The value for the CSAPIport property must be a preparation for collecting CSM, EE or HPR data. The
valid, positive number. The default ports of 1670 and initialization was not successful.
1671 are used.
The code_location identifies the location within the
Programmer Response: Specify a positive number for monitor code where this message is issued. It is used
the CSAPIport property in the itmnp.properties file or, by IBM customer support.
if the default ports of 1670 and 1671 are acceptable,
remove the CSAPIport property. Operator Response: Verify that the SNAMGMT
network management interface is active.

FNPT005E THE MONITOR CANNOT CONNECT Issue the DISPLAY NET,VTAMOPTS,OPTION=SNAMGMT

TO THE DATA COLLECTION SERVER. command to determine if the SNAMGMT interface is
CODE: internal_code active.

Explanation: The monitor definition specifies the Programmer Response: Verify that the user ID
collection of z/OS Communications Server data, but running the monitor is authorized to use the
the monitor cannot connect to the data collection SNAMGMT network management interface.
server. The data collection server or the TCP/IP stack
might not be active.
The monitor attempts to connect to the data collection
server once every interval as long as the monitor
definition is scheduled to collect this data.
Operator Response: Verify that a TCP/IP stack is

20 IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting

 FNPT009E • FNPT014E

Server ended the connection.

FNPT009E THE netmgmt_interface INTERFACE
CANNOT BE INITIALIZED WITH THE The monitor attempted to initialize a z/OS
tcpip_job_name JOB NAME. CODE: Communications Server network management interface
code_location for a TCP/IP stack in preparation for collecting z/OS
Communications Server data. The initialization was not
Explanation: The program attempted to initialize a
successful. The network management interfaces that
z/OS Communications Server network management
might have been stopped are as follows:
interface for a TCP/IP stack to prepare for collecting
z/OS Communications Server data. The initialization SMFService
was not successful. The network management
interfaces that can be initialized are as follows: Collects TN3270 data or FTP data, or both.

SMFService TCPCONNService

Collects TN3270 data or FTP data, or both. Collects FTP data.

TCPCONNService The code_location identifies the location within the

Collects FTP data. monitor code where this message is issued. It is used
by IBM customer support.
The code_location identifies the location within the Operator Response: Verify that the network
monitor code where this message is issued. It is used management interface is active for the TCP/IP stack.
by IBM customer support.
Programmer Response: Verify that the user ID
Operator Response: Verify that the network running the monitor is authorized to use the network
management interface is active for the TCP/IP stack. management interface on the TCP/IP stack.
Issue the DISPLAY TCPIP,tcpipproc,NETSTAT,CONFIG
command to determine which network management FNPT012E THE REQUEST FOR data_type DATA
interfaces are active. FAILED WITH RETURN CODE
return_code AND REASON CODE
Programmer Response: Verify that the user ID
reason_code. CODE: code_location
running the program is authorized to use the network
management interface on the TCP/IP stack. Explanation: The z/OS Communications Server
reported a request that was not valid for the
Communication Storage Manager, Enterprise Extender,
FNPT010W THE Z/OS COMMUNICATIONS
or High-Performance Routing data on the SNAMGMT
SERVER STOPPED THE SNAMGMT
network management interface. The requested data
INTERFACE. CODE: code_location
cannot be collected.
Explanation: The monitor attempted to communicate
The expected return_code is:
using the SNAMGMT network management interface,
but the z/OS Communications Server ended the 121 (EINVAL)
connection.
A request for z/OS Communications Server
code_location identifies the location within the monitor data was not valid.
code where this message is issued. It is used by IBM
customer support. The code_location identifies the location within the
Operator Response: Activate the SNAMGMT monitor code where this message is issued. It is used
interface, using the MODIFY by IBM customer support.
vtamproc,VTAMOPTS,SNAMGMT=YES command. Programmer Response: Verify that the installed
Programmer Response: Verify that the user ID versions of Tivoli Monitoring for Network Performance
running the monitor is authorized to use the and z/OS Communications Server are compatible.
SNAMGMT network management interface.
FNPT014E A RECORD IS MISSING IN THE
FNPT011W THE Z/OS COMMUNICATIONS RESPONSE RECEIVED FROM THE
SERVER STOPPED THE Z/OS COMMUNICATIONS SERVER
netmgmt_interface NETWORK INTERFACE
MANAGEMENT INTERFACE WITH Explanation: The monitor received a response from
tcpip_job_name. CODE: code_location the z/OS Communications Server network
Explanation: The monitor attempted to communicate management interface. The response is missing a
using the z/OS Communications Server network required record. The Enterprise Extender connection
management interface, but the z/OS Communications data was received and stored, but some Enterprise
Extender connection details cannot be stored. The

Chapter 3. Messages 21
FNPT015I • FNPT023E

monitor continues processing.

FNPT019E THE DATA COLLECTION SERVER
Programmer Response: Verify that the installed CANNOT JOIN A CHILD THREAD.
versions of Tivoli Monitoring for Network Performance THE SERVER CONTINUES
and z/OS Communications Server are compatible. COLLECTING DATA.
Explanation: The monitor that collects data from
FNPT015I THE DATA COLLECTION SERVER IS Communications Server for z/OS network management
INITIALIZED AND READY TO interfaces received an error while attempting to join a
COLLECT DATA child thread. Data collection continues.
Explanation: The program that collects data from Programmer Response: Investigate the reason for the
z/OS Communications Server network management join failure. View the trace logs for additional
interfaces has been initialized successfully. The process information.
is ready to collect z/OS Communications Server data.
FNPT020I THE DATA COLLECTION SERVER
FNPT016I THE DATA COLLECTION SERVER RECEIVED A REQUEST TO STOP
HAS COMPLETED PROCESSING
Explanation: The data collection server frees the
Explanation: The program that collects data from resources and exit.
z/OS Communications Server network management
interfaces has completed processing and ended
FNPT021E THE INTERNAL CONNECTIONS TO
normally.
THE DATA COLLECTION SERVER
HAVE EXCEEDED THE MAXIMUM
FNPT017E THE DATA COLLECTION SERVER NUMBER. THE NEW CONNECTION
INITIALIZATION WAS NOT WAS CLOSED.
SUCCESSFUL. CODE: internal_code
Explanation: The data collection server received a
Explanation: The monitor that collects data from z/OS request for a new internal connection when it already
Communications Server network management had the maximum number of open internal
interfaces was not initialized successfully. The monitor connections.
failed to bind to the CSAPIport port or to initialize
The process continues collecting the z/OS
internal control blocks. The process exits.
Communications Server data for the existing clients.
The code_location identifies the location within the The new connection was closed.
monitor code where this message is issued. It is used
Programmer Response: Verify that all connections to
by IBM customer support.
the two ports specified by the CSAPIport in the
Operator Response: The problem might be temporary. itmnp.properties file are local connections between the
Stop and start the monitor again. monitor processes.

Programmer Response: Verify that the CSAPIport port The netstat conn from TSO or netstat -c command
is not being used by another application or that it is from UNIX System Services could be used to display
not reserved. The port can be reserved in the TCP/IP active connections.
profile or one of the BPXPRMxx members.
Verify that the region size for the monitor is large FNPT022I NO DATA WAS RECEIVED ON THE
enough. SOCKET.
Explanation: The data collection server received no
FNPT018W THE DATA COLLECTION SERVER data on an internal connection. The resources for this
CANNOT INITIALIZE LOGGING. internal connection will be released. The data collection
INITIALIZATION CONTINUES server continues collecting data for other internal
WITHOUT TRACE OR MESSAGE connections.
LOGGING.
Explanation: The data collection server was not able FNPT023E THE IP_address_or_host_name CANNOT
to successfully initialize the message and trace logging BE RESOLVED.
facility. The monitor continues initializing without
Explanation: A GETHOSTBYNAME or
message or trace logging capabilities.
GETHOSTBYADDR request failed for the specified IP
Programmer Response: Investigate the reason for address or host name.
reduced message or trace logging. View the z/OS
Operator Response: Verify that the TCP/IP stack that
SYSLOG for additional messages.
owns the host name or IP address is active.

22 IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting

 FNPT024E • FNPT027E

Programmer Response: Verify that the host name or Communications Server network management data was
IP address is valid on this system. The host name or IP closed, and resources were released. The monitor will
address is specified in the monitor definition on the continue to collect data at the next interval.
Tivoli Monitoring for Network Performance Web
The code_location identifies the location within the
application; ensure that the host name or IP address is
monitor code where this message is issued. It is used
correct in the monitor definition.
by IBM customer support.
Programmer Response: Verify that the installed
FNPT024E THE TCP/IP JOB NAME CANNOT BE
versions of Tivoli Monitoring for Network Performance
DETERMINED FROM
and z/OS Communications Server are compatible.
IP_address_or_host_name.
Explanation: The monitor definition contains an IP
FNPT027E A RESPONSE WAS RECEIVED FOR
address, a host name or both for one or more local
data_type DATA FROM tcpip_job_nm
TCP/IP stacks. If the IP address is provided, the
WITH ERRNO=errnoAND
monitor uses the IP address; if not, the monitor uses
ERRNOJR=0xerrnoJr. CODE: code_location
the host name.
Explanation: The z/OS Communications Server
This message is issued when the monitor cannot
network management interface rejected a request for
retrieve the TCP/IP job name, using the specified IP
data with the indicated errno and errnoJr codes. The
address or host name.
monitor currently cannot collect this data. The monitor
Operator Response: Verify that the TCP/IP stack is continues attempting to collect data based on the
active. monitor definition.
Programmer Response: Verify that the IP address or The expected errno codes are as follows:
host name is valid on this system. The host name or IP
111 (EACCES)
address is specified in the monitor definition on Tivoli
Monitoring for Network Performance Web application; The caller is not authorized.
ensure that the host name or IP address is correct in the
monitor definition. 112 (EAGAIN)
The target TCP/IP stack was not active.
FNPT025E THE DATA RECEIVED ON 118 (EFAULT)
netmgmt_interface INTERFACE FROM
tcpip_job_name WAS NOT COMPLETE. Storage provided as part of the data request
CODE: code_location cannot be accessed.

Explanation: The data collection server received data 121 (EINVAL)

that was not complete. The File Transfer Protocol (FTP) A request for z/OS Communications Server
or TN3270 data cannot be collected. The interface to the data was not valid.
z/OS Communications Server network management
data was closed, and resources were released. The data 1158 (ETCPERR)
collection server attempts to establish this data An unexpected error occurred while z/OS
collection again. Communications Server was attempting to
The code_location identifies the location within the retrieve the requested data.
monitor code where this message is issued. It is used
by IBM customer support. The code_location identifies the location within the
monitor code where this message is issued. It is used
Operator Response: Notify the system programmer if by IBM customer support.
the problem persists.
Operator Response: Verify that the TCP/IP stack is
Programmer Response: Verify that the installed active.
versions of Tivoli Monitoring for Network Performance
and z/OS Communications Server are compatible. Programmer Response: For the EACCES code, verify
that the data collection server is authorized program
facility (APF) authorized.
FNPT026E THE DATA RECEIVED ON
netmgmt_interface INTERFACE FROM For the EFAULT, EINVAL or ETCPERR codes, contact
tcpip_job_name WAS NOT VALID. IBM customer support.
CODE: code_location.
See the z/OS UNIX System Services Messages and Codes
Explanation: The monitor that collects data from z/OS for errno (displayed in decimal) and errnoJr codes.
Communications Server network management
interfaces received data that is not valid. The data
cannot be collected. The interface to z/OS

Chapter 3. Messages 23
FNPT028E • FNPT032E

The code_location identifies the location within the

FNPT028E THE netmgmt_interface INTERFACE IN
monitor code where this message is issued. It is used
THE interface_path PATH CANNOT BE
by IBM customer support.
INITIALIZED. ERRNO=errno AND
ERRNOJR=0xerrnoJr. CODE: Programmer Response: For the EACCES code, verify
code_location. that the data collection server is authorized program
facility (APF) authorized.
Explanation: An attempt to initialize the z/OS
Communications Server network management interface For the EILSEQ code, verify that the data collection
was not successful for the identified reason. server is allocated sufficient resources and assigned a
high enough dispatching priority to collect the data
The code_location identifies the location within the
requested.
monitor code where this message is issued. It is used
by IBM customer support. For the EBADF, EFAULT and EINVAL codes, contact
IBM customer support.
Operator Response: Verify that the TCP/IP stack is
active. Verify that the z/OS Communications Server See the z/OS UNIX System Services Messages and Codes
network management interface is active. Issue the for errno (displayed in decimal) and errnoJr codes.
DISPLAY NET,VTAMOPTS,OPTION=SNAMGMT
command for the SNAMGMT interface. Issue the
DISPLAY TCPIP,tcpip_procname,NETSTAT,CONFIG FNPT030E THE HIGH-PERFORMANCE
command for the network monitoring interfaces. ROUTING CONNECTION DATA
CANNOT BE STORED.
Programmer Response: Verify that the user ID
running the monitor is authorized to access the z/OS Explanation: The monitor received a response from
Communications Server network management the SNAMGMT network management interface. The
interface. response is missing required information such that the
High-Performance Routing connection data cannot be
See z/OS UNIX System Services Messages and Codes for stored. The monitor continues attempting to collect
errno (displayed in decimal) and errnoJr codes. data as specified in the monitor definition.
Programmer Response: Verify that the installed
FNPT029E AN ERROR OCCURRED IN versions of Tivoli Monitoring for Network Performance
RETRIEVING DATA ON THE and z/OS Communications Server are compatible.
netmgmt_interface INTERFACE, WITH
ERRNO=errno AND
ERRNOJR=0xerrnoJr. CODE: FNPT031E A REQUEST FOR data_type DATA
code_location. RECEIVED AN UNKNOWN RECORD
ON THE SNAMGMT INTERFACE.
Explanation: An attempt to retrieve data from a z/OS CODE: code_location
Communications Server network management interface
failed. The expected errno codes are as follows: Explanation: In the response to a request for
Communication Storage Manager, Enterprise Extender,
111 (EACCES) or High-Performance Routing data, the monitor
received a data record of an unknown type on the
The data collection server is not APF
SNAMGMT network management interface. The
authorized.
unknown record in this request has been ignored. Any
113 (EBADF) data preceding the unknown record has been stored.
The token provided to locate a buffer is not a The code_location identifies the location within the
valid token. monitor code where this message is issued. It is used
by IBM customer support.
118 (EFAULT)
Programmer Response: Verify that the installed
Storage provided as part of the data request
versions of Tivoli Monitoring for Network Performance
cannot be accessed.
and z/OS Communications Server are compatible.
121 (EINVAL)
The token provided to locate a buffer does not FNPT032E AN UNKNOWN RECORD TYPE WAS
specify a valid data buffer. RECEIVED FROM A netmgmt_interface
INTERFACE FROM tcpip_job_name.
147 (EILSEQ) CODE: code_location
The data buffer described by token has been Explanation: The monitor received an unknown type
overwritten and is no longer available. data record while waiting for FTP or TN3270 data. The
record is discarded and the monitor continues to
process.

24 IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting

 FNPU001E • FNPU008E

The code_location identifies the location within the is functioning properly and that the Tivoli Monitoring
monitor code where this message is issued. It is used for Network Performance database exists and was
by IBM customer support. created successfully. Contact IBM customer support if
the problem persists.
Programmer Response: Verify that the installed
versions of Tivoli Monitoring for Network Performance
and z/OS Communications Server are compatible. FNPU005E A failure occurred while attempting to
transmit the command command to
system system_name.
FNPU001E The value in the field_name field defines
a duplicate community name. Explanation: The command can be:
Explanation: The community name you specified v Suspend Monitor
already exists in the community name list. The entry v Resume Monitor
field in error is marked with a red indicator. v Deploy Configuration
Administrator Response: Type a unique, valid Administrator Response: See the WebSphere
community name and click OK. Click Cancel to use the Application Server error log for more information.
existing community name list.

FNPU006E You must specify a monitor location.

FNPU002I No monitors are currently configured.
Explanation: A monitor location is defined by the
Explanation: You attempted to display the list of system name and IP address (or host name). You must
configured monitors but there are none and the list is specify a monitor location to continue to the next step
empty. in the configuration wizard.
Administrator Response: Use the monitor Administrator Response: Type a valid monitor
configuration wizards to create monitor definitions for location and complete the remaining steps in the
each of the systems that you want to monitor. You can configuration wizard.
then view or modify the monitor configurations using
the Manage Monitor Configurations function from the
portfolio. FNPU007I The following table contains the list of
monitors that will be affected if you
delete monitor definition monitor_def.
FNPU003E A failure occurred while attempting to Click OK to delete the monitor
communicate with the monitor running definition or Cancel to keep the monitor
on system system_name. The command definition.
command is not issued.
Explanation: You have requested to delete a monitor
Explanation: The command that you are attempting to definition. If you delete this monitor definition, it will
send to the monitor cannot be sent because there is a be removed from all current monitor configurations.
problem communicating with the system where the Configuration changes are not implemented by the
monitor is running. The command can be: monitor until the configuration is redeployed to the
v Suspend Monitor monitor or until the monitor is restarted.
v Resume Monitor Administrator Response: Click OK inside the
v Deploy Configuration message box to delete the monitor definition or Cancel
v Ping inside the message box to keep the monitor definition.
v Trace Route
FNPU008E You must select a performance metric.
Administrator Response: See the WebSphere
Application Server error log for more information. Explanation: Before you can continue with graphing,
you must select a performance metric.
FNPU004E A failure occurred while trying to access Operator Response: If you are graphing multiple
the database for read or write metrics, select one or more performance metrics and
operations. continue graphing. If you are graphing multiple
resources, select a single performance metric and
Explanation: There is a problem with the connection
continue graphing.
between the WebSphere Application Server product
and the DB2 product or there is a database error.
Operator Response: Retry the operation. Contact your
network administrator if the problem persists.
Administrator Response: Verify that the DB2 product

Chapter 3. Messages 25
FNPU009E • FNPU016I

FNPU009E Errors occurred while removing stack FNPU014W A definition_type definition named
stack_name from the list. save_name already exists. Modify the
definition name or click Next or
Explanation: An internal error occurred while trying
Autoconfigure to overwrite the existing
to remove a TCP/IP stack from the TCP/IP stack list.
definition.
Administrator Response: Click Cancel to close the
Explanation: A definition by this name already exists.
configuration wizard. This is an unrecoverable error.
If this name is being used by other monitor definitions,
Contact IBM customer support.
the list of affected monitor definitions is displayed. If
you modify the existing saved definition, your changes
FNPU010E You must specify at least one TCP/IP will be applied to all of the monitor definitions using
stack. the specified definition name. The definition type can
be:
Explanation: Before you can continue to the next step
in the configuration wizard, you must specify at least v Data Attribute Set
one TCP/IP stack for each monitored system. A v MIB Data
TCP/IP stack is identified by its IP address or host v Schedule
name.
v Thresholds
Administrator Response: Type one or more valid
TCP/IP stack names and complete the remaining steps The name of the definition is the name entered in the
in the configuration wizard. Save As field.
Administrator Response: Click Next or
FNPU011E Errors occurred while removing resource Autoconfigure to overwrite the existing definition, or
resource_name from the resource list. provide a new name and click Next or Autoconfigure
to continue. You will proceed to the next step in the
Explanation: See message.
wizard if you click Next. If you click Autoconfigure
Administrator Response: Click Cancel to close the you will proceed directly to the Save Monitor
configuration wizard. This is an unrecoverable error. Definition screen.
Contact IBM customer support.
FNPU015E You cannot save a definition with a
FNPU012I The SmartSet or wildcard specification name of IBM Supplied Values.
pattern cannot be resolved.
Explanation: IBM provides an initial set of
Explanation: A SmartSet or an IP address or host configuration values named IBM Supplied Values. This
name wildcard string cannot be resolved by a DNS should be used as a starting point for determining the
query. specific configuration values for your environment. You
can change this initial set of values, save them by
Administrator Response: A SmartSet name or name, and optionally set them as your default values.
wildcard specification cannot be not resolved. Enter IP When saving by name, you must use a name other
addresses or fully qualified host names if possible. than IBM Supplied Values.
Administrator Response: Choose a name other than
FNPU013E You must specify at least one resource. IBM Supplied Values and save the definition.
Explanation: You must specify at least one resource
for each monitored system in order to continue to the FNPU016I A favorite graph titled graph_title already
next step in the configuration wizard. A resource is exists. Click OK to overwrite the
identified by its IP address or host name or SmartSet. existing favorite graph or Cancel to
You can use a wildcard specification to automatically enter a unique title for the favorite
resolve one or more resources. graph.
Administrator Response: Type one or more valid Explanation: A favorite graph with this title already
resources and complete the remaining steps in the exists. If you overwrite the existing favorite graph, the
configuration wizard. existing favorite graph is deleted from the database and
the new favorite graph is added.
Operator Response: Click OK inside the message box
to overwrite the existing favorite graph or click Cancel
inside the message box and enter a unique title for the
favorite graph.

26 IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting

 FNPU017W • FNPU026E

v MIB Data
FNPU017W A monitor definition named monitor_def
already exists. Modify the monitor v Monitors
definition name or click Next to v Schedule
overwrite the existing monitor v Thresholds
definition.
Administrator Response: Click Cancel to close the
Explanation: See message. configuration wizard. This is an unrecoverable error.
Administrator Response: Click Next to overwrite the Contact IBM customer support.
existing monitor definition, or provide a new monitor
definition name and then click Next to continue. FNPU023E A non-numeric value was specified for
the field_name field for metric
FNPU018E A value must be specified for the metric_name.
required field_name field. Explanation: The value provided for the specified
Explanation: A value is required for the specified field must be numeric. The entry field in error is
field. The entry field in error is marked with a red marked with a red indicator.
indicator. Administrator Response: Type a valid value in the
Operator Response: Type a valid value in the entry entry field and click OK.
field and click OK.
FNPU024E A threshold value is required when a
FNPU019E The value in the field_name field rearm value is specified for metric
contains non-numeric characters. metric_name.

Explanation: Only numeric values are valid for this Explanation: The entry field in error is marked with a
entry field. The entry field in error is marked with a red indicator.
red indicator. Administrator Response: Type a valid threshold value
Operator Response: Type a valid value in the entry in the entry field and click OK.
field and click OK.
FNPU025E A threshold value is required when you
FNPU020E An error occurred while validating the have specified to generate an event for
value in the field_name field. metric metric_name.

Explanation: The entry field cannot be validated due Explanation: An event is generated when a threshold
to an internal error. is crossed. You must specify a threshold value in order
to generate an event. The entry field in error is marked
Operator Response: If you are using a configuration with a red indicator.
wizard, click Cancel to close the wizard. This is an
unrecoverable error. Contact IBM customer support. Administrator Response: Type a valid threshold value
in the entry field and click OK.

FNPU021E You must specify at least one data

attribute to collect. FNPU026E The rearm value must be
comparison_operator the threshold value
Explanation: Data attributes describe the type of data for metric metric_name.
to monitor. You must specify at least one data attribute
for each monitored system in order to continue to the Explanation: When a threshold value for a particular
next step in the configuration wizard. metric is crossed, the network operator can be alerted
by an event. The associated rearm value determines
Administrator Response: Select one or more data when to generate an event to notify the network
attributes and complete the remaining steps in the operator that the problem has been resolved. The
configuration wizard. threshold and rearm values that were specified for this
metric are incompatible, making it impossible to
FNPU022E This monitor definition cannot be generate an event to notify the network operator that
saved. The information provided for the the problem was resolved. The entry field in error is
definition_type definition is no longer marked with a red indicator.
available. Administrator Response: Type a valid threshold and
Explanation: Configuration information has been lost. rearm value in the entry field and click OK.
The monitor definition cannot be saved. The monitor
definition type can be:
v Data Attribute Set

Chapter 3. Messages 27
FNPU027E • FNPU036E

FNPU027E An error occurred while attempting to FNPU032E The value in the field_name field is too
modify the threshold value for long. The maximum length allowed is
metric_name. maximum_length characters.
Explanation: An internal error occurred while Explanation: The entry field in error is marked with a
attempting to modify an existing threshold value. red indicator.
Administrator Response: Click Cancel to close the Operator Response: Type a valid value in the entry
configuration wizard. This is an unrecoverable error. field and click OK.
Contact IBM customer support.
FNPU033E The value in the field_name field does
FNPU028I There are no favorite graphs to view. not contain a valid IP address or host
name.
Explanation: You attempted to display the list of
saved favorite graphs but there are none. The list of Explanation: The IP address or host name that you
saved favorite graphs in the table is empty. You must entered is not valid. If you entered a host name, Tivoli
save a favorite graph before you can view a favorite Monitoring for Network Performance has issued a DNS
graph. query from the WebSphere server to resolve it but the
DNS query failed. The entry field in error is marked
Operator Response: To save a favorite graph, select
with a red indicator.
one or more resources from an operator view and click
Graph Metrics or Graph Multiple Resources. Once the Administrator Response: Type a valid IP address or
graph is displayed, click Save as Favorite Graph... to fully qualified host name and click OK. If you entered
save the graph as a favorite. After the graph is saved, a host name and it could not be resolved, enter the IP
you can return to View Favorite Graphs. Click Refresh address of the resource.
Now to refresh the table and view the favorite graph.
FNPU034E The interval value exceeds the time
FNPU029E You must specify at least one schedule range.
item.
Explanation: The interval value is greater than the
Explanation: A schedule defines when and how often amount of time between the start time and date and
the monitor collects data. You must specify a schedule the end time and date. The entry field in error is
for each monitored system in order to continue to the marked with a red indicator.
next step in the configuration wizard.
Administrator Response: Type a valid interval value
Administrator Response: Create a new schedule or and click OK.
select an existing schedule and complete the remaining
steps in the configuration wizard.
FNPU035E The time range exceeds one year.
Explanation: The time range specified by the start
FNPU030E The end time and date precede the start
time and date and the end time and date exceeds one
time and date.
year.
Explanation: The start time and date must precede the
Administrator Response: Change the start time and
end time and date.
date or end time and date to represent a valid time
Operator Response: Change the start time and date or range.
end time and date to represent a valid time range.
FNPU036E The value in the field_name field defines
FNPU031E The value in the field_name field must be a duplicate monitor name.
in the minimum_value to maximum_value
Explanation: The monitor location you specified
range.
already exists in the monitor location list. The entry
Explanation: The value entered for the field was either field containing the duplicate name is marked with a
less than the minimum value allowed or greater than red indicator.
the maximum value allowed. The entry field in error is
Administrator Response: Enter unique, valid values
marked with a red indicator.
for the monitor you want to define and click OK or
Operator Response: Type a valid value in the entry click Cancel to use the existing monitor location list.
field and click OK.

28 IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting

 FNPU037E • FNPU045E

Administrator Response: Click OK inside the

FNPU037E The value in the field_name field defines
message box to confirm the purge request or click
a duplicate TCP/IP stack name.
Cancel inside the message box to cancel the purge
Explanation: A TCP/IP stack name can be specified request. If the purge request is confirmed, message
by an IP address or a host name. The TCP/IP stack FNPU042I is displayed at the top of the page to indicate
name you specified already exists in the TCP/IP stack that the purge request was sent.
list. The entry field containing the duplicate stack name
is marked with a red indicator.
FNPU042I The purge request was sent. Check the
Administrator Response: Type a unique, valid value WebSphere Application Server log to
for the TCP/IP stack name and click OK or click verify that the purge request completed
Cancel to use the existing TCP/IP stack list. successfully.
Explanation: This message indicates that the purge
FNPU038E The value in the field_name field defines request was sent. This does not imply that the data has
a duplicate resource name. been purged successfully. If you choose to check for
ETL completion before issuing the purge request, and
Explanation: The resource name you specified already
the data you are attempting to purge has not already
exists in the resource list. The entry field containing the
been aggregated into Tivoli Data Warehouse, the purge
duplicate resource name is marked with a red indicator.
request was not issued.
Administrator Response: Type a unique, valid value
Administrator Response: Verify the completion of the
for the resource name and click OK or click Cancel to
purge request in the WebSphere Application Server log.
use the existing resource list.

FNPU043E The value in the field_name field is not

FNPU039E A numeric value less than zero was
valid.
specified for the field_name field for
metric metric_name. Explanation: The value entered for the specified field
contains one or more characters that are not allowed
Explanation: The value provided for the specified
for this entry field. The entry field in error is marked
field must be a number which is greater than or equal
with a red indicator.
to zero. The entry field in error is marked with a red
indicator. Operator Response: Type a valid value in the entry
field and click OK.
Administrator Response: Type a valid value in the
entry field and click OK.
FNPU044E A non-integer value was specified for
the field_name field for metric metric
FNPU040E The schedule item is not valid or is in
name.
conflict with the existing schedule.
Explanation: The value provided for the specified
Explanation: The combination of values for start time,
field must be an integer. The entry field in error is
start day, end time, end day, and interval are not valid,
marked with a red indicator.
or the schedule item that you are attempting to add
conflicts with one or more existing schedule items. Administrator Response: Type a valid value in the
entry field and click OK.
Administrator Response: Verify that the start time,
start day, end time, end day, and interval are valid. If
you are attempting to add a schedule item to an FNPU045E The values in the field_name1 and
existing schedule, ensure that it does not overlap with field_name2 fields define a duplicate
existing schedule items. Type a valid schedule item and event receiver.
click OK or click Cancel to use an existing schedule.
Explanation: An event receiver with these values
already exists. The duplicate entry fields are marked
FNPU041I Click OK to purge all data older than with a red indicator.
num_days days or Cancel to cancel the
Administrator Response: Type a unique, valid value
purge request.
for the event receiver you want to define and click OK
Explanation: You have requested an immediate purge or click Cancel to use the existing event receiver list.
of all data older than the specified number of days to
retain data. The number of days to retain data and the
check box value indicating ETL completion will be used
when the purge request is issued. All fields on the page
are validated. The value in the Purge Time field will be
ignored and the purge request will be sent immediately.
You must confirm or cancel the purge request.

Chapter 3. Messages 29
FNPU046E • FNPU056I

FNPU046E The value in the field_name field is not FNPU051I The configuration wizard used to view
valid because it contains spaces. or modify the config_name configuration
is currently open.
Explanation: Spaces are not allowed for this entry
field. The entry field in error is marked with a red Explanation: Only one occurrence of a wizard can be
indicator. in use at a time. You have attempted to use a wizard
while another occurrence of the wizard is already in
Operator Response: Type a valid value for the entry
use.
field and click OK.
Administrator Response: Close or finish working on
the existing monitor definition so the configuration
FNPU047E The value in the field_name field
wizard is no longer in use. View/Modify the monitor
contains non-alphanumeric characters.
definition.
Explanation: Only alphanumeric values are valid for
this entry field. The entry field in error is marked with
FNPU052E The smartset_name SmartSet is not found
a red indicator.
in the database.
Operator Response: Type a valid value in the entry
Explanation: The SmartSet you provided is not in the
field and click OK.
database. Check that you are using the appropriate
name.
FNPU048I You cannot modify Run-time
Administrator Response: Query the database for
Preferences or configurations when
SmartSets and replace with an appropriate name.
signed on in browse mode. If you need
to make Run-time Preference or
configuration changes, sign off and sign FNPU053I A graph or table cannot be generated.
on again to obtain full access to the The database does not contain
configuration database. performance data for the specified time
range.
Explanation: Multiple administrators can be signed on
at any given time but only one administrator can have Explanation: Performance data was not found in the
full access to the configuration database to create and database for the specified time range for any of the
modify Run-time Preferences or configuration data. selected resources and performance metrics.
Administrator Response: Sign off and sign on again Operator Response: Ensure that you are collecting
with full access to modify the Run-time Preference or data for the resources and metrics you are attempting
configuration. to graph and that the data was collected within the
specified time range.
FNPU049I You cannot save configuration changes
when signed on in browse mode. User FNPU054I Click OK to delete the selected favorite
user_name currently has full access to the graphs or Cancel to cancel the request.
configuration database.
Explanation: You have selected one or more favorite
Explanation: Multiple administrators can be signed on graphs and requested they be removed. If you click
at any given time but only one administrator can have OK, the selected graphs are removed from the table
full access to the configuration database to create and and deleted from the database. If you click Cancel, the
modify configuration data. graphs are not removed.
Administrator Response: Contact the administrator Operator Response: Click OK inside the message box
that has full access to the configuration database. Once to delete the selected favorite graphs from the database.
this administrator has signed off, you can sign off and Click Cancel inside the message box to cancel the
sign on again to obtain full access to the configuration request.
database.
FNPU056I You have signed on with full access to
FNPU050E No results were found for the given the configuration database. Your existing
search criteria. full access browser session has been
converted to browse mode.
Explanation: No matches were found when searching
the database using the specified search criteria. Explanation: Multiple administrators can be signed on
at any given time but only one administrator can have
Administrator Response: Modify the search criteria
full access to the configuration database to create and
and search the database again.
modify configuration data. You are currently signed on
from another browser session as an administrator with
full access. You now have full access to the database to

30 IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting

 FNPU057I • FNPU064E

make configuration changes from this browser session Administrator Response: For each system, you must
and your access on the previous browser session has specify at least one stack to monitor. Click Next and
been changed to browse mode. complete the remaining steps in the configuration
wizard.
Administrator Response: You now have full access to
the configuration database from this browser session.
Your existing session has been converted to browse FNPU061I A graph or table cannot be generated.
mode. The database does not contain
performance data for all of the selected
resources for the specified time range.
FNPU057I You have requested full access to the
configuration database. Only one Explanation: Performance data was not found in the
administrator is allowed full access to database for all of the selected resources for the
the configuration database to make specified time range.
configuration changes. User user_ID
Operator Response: Ensure that you are collecting
currently has full access to the
data for all of the resources you are attempting to
configuration database. You have been
graph and that the data was collected within the
signed on in browse mode.
specified time range.
Explanation: Multiple administrators can be signed on
at any given time but only one administrator can have
FNPU062E A graph or table cannot be generated.
full access to the configuration database to create and
The java.awt classes cannot access the
modify configuration data. Another administrator is
X11 native libraries.
currently signed on with full access to the configuration
database. You have been signed on in browse mode. Explanation: The WebSphere Application Server
You do not have full access to the database to modify cannot access the X11 native libraries. These libraries
the configuration. are necessary to generate a graph or table.
Administrator Response: If you need to make Operator Response: If you start your Web Application
configuration changes, ask the administrator who has Server remotely without first setting the DISPLAY
full access to the configuration database to sign off so environment variable you will consistently see this
you can sign on and create or modify the configuration. failure. The default value is DISPLAY=:0.0. For
example, if you telnet into an AIX server to start the
Web Application Server, you must first issue a
FNPU058E The specified start time and date is
command appropriate for the shell to set the DISPLAY
equal to the specified end time and
environment. The command can be:
date.
v export DISPLAY=:0.0
Explanation: The start time and date cannot be equal
v setenv DISPLAY :0.0
to the end time and date.
v DISPLAY=:0.0
Operator Response: Change the start time and date or
end time and date to represent a valid time range.
FNPU063E The value in the field_name field does
not contain a valid IP address.
FNPU059I A graph or table cannot be generated.
The database does not contain Explanation: The entry field in error is marked with a
performance data for all of the selected red indicator.
performance metrics for the specified Administrator Response: Type a valid IP address and
time range. click OK.
Explanation: Performance data was not found in the
database for all of the selected performance metrics for FNPU064E The value in the field_name field does
the specified time range. not contain a valid host name.
Operator Response: Ensure that you are collecting Explanation: The entry field in error is marked with a
data for all of the metrics you are attempting to graph red indicator.
and that the data was collected within the specified
time range. Administrator Response: Type a valid host name and
click OK.
FNPU060E You must specify at least one stack for
each defined monitor.
Explanation: You must specify a stack for each
monitored system in order to continue to the next step
in the configuration wizard.

Chapter 3. Messages 31
FNPU065E • FNPU069E

v 5 indicates an RFC 792 port unreachable message

FNPU065E A command_name command cannot be
was received from the network
issued because the Tivoli Monitoring for
Network Performance monitor cannot v 6 indicates an RFC 792 fragmentation needed and DF
open a socket. set message was received from the network
v 7 indicates an RFC 792 source route failed message
Explanation: See message.
was received from the network
Operator Response: See the monitor log for more v 8 indicates an RFC 792 destination network unknown
information. message was received from the network
v 9 indicates an RFC 792 destination host unknown
FNPU066E A command_name command cannot be message was received from the network
issued because the Tivoli Monitoring for v 10 indicates an RFC 792 source host isolated message
Network Performance monitor cannot was received from the network
resolve the target host name to an IP
v 11 indicates an RFC 792 communication with
address.
destination network is administratively prohibited
Explanation: See message. message was received from the network
Operator Response: See the monitor log for more v 12 indicates an RFC 792 communication with
information. Alternatively, issue the command using destination host is administratively prohibited
the IP address of the target host. message was received from the network
v 13 indicates an RFC 792 destination network
unreachable for type of service message was received
FNPU067E A command_name command cannot be
from the network
issued because the Tivoli Monitoring for
Network Performance monitor cannot v 14 indicates an RFC 792 destination host unreachable
reserve the necessary system resources. for type of service message was received from the
network
Explanation: See message.
v 15 indicates an RFC 1812 communication
Operator Response: See the monitor log for more administratively prohibited message was received
information. from the network
v 16 indicates an RFC 1812 host precedence violation
FNPU068E A command_name command cannot be message was received from the network
issued from the Tivoli Monitoring for v 17 indicates an RFC 1812 precedence cutoff in effect
Network Performance monitor. message was received from the network
Explanation: See message. v 18 indicates an RFC 792 source quench message was
received from the network
Operator Response: See the monitor log for more v 19 indicates an RFC 792 redirect datagram for the
information. network (or subnet) message was received from the
network
FNPU069E A command_name command failed with v 20 indicates an RFC 792 redirect datagram for the
error code error_code. host message was received from the network
Explanation: The Tivoli Monitoring for Network v 21 indicates an RFC 792 redirect datagram for the
Performance monitor attempted to issue a Ping or type of service and network message was received
TraceRoute command. The Internet Control Message from the network
Protocol (ICMP) is used when issuing these commands. v 22 indicates an RFC 792 redirect datagram for the
The following list includes the error codes and type of service and host message was received from
descriptions documented by the Internet Engineering the network
Task Force (IETF). See the following list to find the v 24 indicates an RFC 792 fragment reassembly time
error code that the monitor received when it attempted exceeded message was received from the network
to issue the command.
v 25 indicates an RFC 792 parameter problem message
v 1 indicates a time-out occurred before the network was received from the network
returned the response
v 2 indicates an RFC 792 network unreachable message Operator Response: The error code indicates a specific
was received from the network failure that occurred in your network when the monitor
attempted to issue a Ping or TraceRoute command.
v 3 indicates an RFC 792 host unreachable message Contact your network administrator.
was received from the network
v 4 indicates an RFC 792 protocol unreachable message
was received from the network

32 IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting

 FNPU070E • FNPU076I

have issued the command and it failed due to a

FNPU070E The value in the field_name field is not
timeout error. The command can be one of the
valid because it contains consecutive
following:
imbedded spaces.
v Ping
Explanation: Consecutive imbedded spaces are not
v Traceroute
allowed for this entry field. The entry field in error is
marked with a red indicator. Operator Response: Verify that the IP address is
correct and retry the command. Contact your network
Operator Response: Type a valid value in the entry
administrator if the problem persists.
field and click OK.
Administrator Response: Determine if the monitor is
running. The monitor must be running to issue
FNPU071I Click Append to add the results of this
commands. If the monitor is running, refer to the
database search to the list of previous
monitor log to determine why the command failed.
matches or click Replace to replace the
existing list with the results of this
database search. FNPU075E You have specified a monitor location
that conflicts with an existing monitor
Explanation: You have requested an additional search
in the database. The existing monitor
of the database. The results of this search will be
location is Sysplex Name = sysplex_name,
displayed in the table below. You have the choice of
System Name = system_name, Host Name
appending to the existing results or replacing the
or IP Address = resource_name.
existing results with the results of this search.
Explanation: The monitor location specified by the
Administrator Response: Click Append to append to
input field values conflicts with a monitor which
the existing results or Replace to replace the current
already exists in the database.
results.
Administrator Response: Change the conflicting fields
to correspond to the monitor currently defined in the
FNPU072E A non-integer value was specified for
database. If you want to use the specified values, go to
the field_name field.
the Manage Monitor Configurations page and delete
Explanation: The value provided for the specified the conflicting monitor.
field must be an integer. The entry field in error is
marked with a red indicator.
FNPU076I Detailed information for the selected
Operator Response: Type a valid value for the entry resource, session or connection is not
field and click OK. available.
Explanation: Detailed information for the specified
FNPU073I The community name list must contain resource, session or connection was not found in the
at least one community name. The database. This data might have been purged from the
default value for community name has database.
been added to the list. Click OK to use
Operator Response: You cannot access data that has
the default community name or modify
already been purged from the database. If you want to
the list to specify one or more
see more recent data related to the selected resource,
community names.
session or connection, close the Details page and click
Explanation: You attempted to save an empty Refresh Now on the screen where you made your
community name list. original selection. Select the resource, session or
connection and click Details to view the most recent
Administrator Response: Click OK to save the default
detailed data. Or, you can use the graphing function to
community name or modify the list to specify one or
view previously collected data that resides in the
more community names. Click Cancel if you do not
database. If the item you originally selected is no
want to save these changes to the community name list.
longer available in the refreshed table, the data related
to the selected item has been purged from the database
FNPU074E The request to issue a command and is no longer available for display.
command to IP address IP_address from
the monitor on system system_name has
failed. A timeout occurred before a
command response could be received.
Explanation: The command was sent to the specified
monitor but a command response was not received
before a timeout occurred. The monitor may not be
running on the specified system or the monitor might

Chapter 3. Messages 33
FNPU077E • FNPU082I

stamp has not changed, it is possible that the command

FNPU077E You have entered a user name or
is still being processed or the command did not
password that is not valid. User names
complete successfully.
and passwords are case sensitive. Please
verify the user name and password and Administrator Response: Verify the completion of the
try again. command in the WebSphere Application Server log.
Explanation: The application was unable to
authenticate the user name and password. FNPU080E A failure occurred while attempting to
communicate with the Tivoli Monitoring
Operator Response: Verify the user name and
for Network Performance servlet
password and try again. Contact your network
application running on system
administrator if the problem persists.
system_name.
Administrator Response: Check that the user name
Explanation: There is a problem with the connection
and password are defined properly in the product you
between the Tivoli Monitoring for Network
are using for authentication and that the password is
Performance portlet application and the Tivoli
not expired. Check the WebSphere security setup to
Monitoring for Network Performance servlet
ensure that the user name is mapped to a role that is
application.
supported by the Tivoli Monitoring for Network
Performance Web application. Operator Response: Verify that the Tivoli Monitoring
for Network Performance servlet application is running
and is functioning properly.
FNPU078I One or more of the resources you
selected could not be resolved by the
domain name server. FNPU081E The value specified for year in the
field_name field is not valid. The value
Explanation: Tivoli Monitoring for Network
for year must be 2004 or later.
Performance has issued a DNS query from the
WebSphere server to resolve the host name and IP Explanation: See message.
address data for the resources that you have selected.
One or more of the addresses could not be resolved. Operator Response: Type a valid value in the entry
For successful DNS queries, the resolved IP address is field and click OK.
displayed in the Resolved Name field. Otherwise, the
Resolved Name field will be blank. If the monitor FNPU082I AUDIT - User: user_name, Mode:
using this monitor configuration uses a different access_mode, Action: user_action,
domain name server, the monitor might be able to Additional Information: audit_information
successfully resolve the addresses for the selected
resources. Explanation: This message contains information that
can be used to track the actions performed by users
Administrator Response: Check that the IP addresses that are associated with the role of administrator. Valid
or host names of the resources are valid. Enter IP values for access mode are Browse Mode or Full
addresses or fully qualified host names if possible. Access. Actions that are tracked include Sign On, Sign
Continue to the next step of the wizard once you have Off, and any actions that are taken to modify the
verified the IP addresses and host names. product runtime preferences and monitoring
characteristics. Environment characteristics such as
FNPU079I The command command was sent to build level, server name, browser level and operating
system system_name. Check the system of the system where the browser is running will
WebSphere Application Server log to be provided in the Additional Information field if it is
verify that the command completed available.
successfully. Administrator Response: None.
Explanation: The command will be sent to the
systems that have been selected. The command can be:
v Suspend Monitor
v Resume Monitor
v Deploy Configuration

This message indicates that the command was sent.

This does not imply that the command was
successfully executed. The Manage Monitors Overview
screen is not refreshed automatically. If you click
Refresh Now and the monitor status or deploy time

34 IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting

 FNPU083I • FNPW020I

IBM Tivoli Monitoring for Network Performance Planning,

FNPU083I The monitor for system system_name has
Installation and Configuration for more details regarding
been selected for deletion. If you want
this setting.
the monitor to stop collecting data, you
must suspend the monitor or deploy an
empty monitor configuration to the FNPW001I An object of type_classname type named
monitor before deleting this monitor object_name was created.
from the resource database. Click OK to
delete the monitor from the resource Explanation: An object was created.
database or click Cancel to keep the Administrator Response: No action is required.
monitor in the resource database.
Explanation: You have requested to delete a monitor FNPW002I An object of type_classname type named
from the resource database. If you delete this monitor object_name was removed.
from the database, it will be removed from the list of
managed monitors. Explanation: An object was removed from the
database.
Administrator Response: Click OK inside the
message box to delete the monitor from the resource Administrator Response: No action is required.
database or Cancel to keep the monitor in the resource
database. FNPW003I The database connection between
WebSphere Application Server and
FNPU084I The monitor for system system_name Tivoli Monitoring for Network
currently has no monitor definitions. If Performance was initialized successfully.
you deploy an empty configuration to Explanation: The system has initialized successfully.
this monitor, the monitor will stop WebSphere Application Server has started.
collecting data. Click OK to deploy an
empty configuration to the monitor or Administrator Response: No action is required.
click Cancel if you want the monitor to
continue collecting data using the FNPW004E The database connection between
existing deployed monitor WebSphere Application Server and
configuration. Tivoli Monitoring for Network
Explanation: You have requested to deploy an empty Performance was not initialized
configuration to a monitor. Once the monitor receives successfully. An exception_detail exception
this configuration, it will stop collecting data. The has occurred.
monitor will not collect data until a new monitor Explanation: The Tivoli Monitoring for Network
configuration is deployed. Performance WebSphere Application Server component
Administrator Response: Click OK inside the could not initialize or access the database.
message box to deploy the empty configuration or Operator Response: Notify your WebSphere
Cancel if you want the monitor to continue collecting administrator.
data using the existing deployed monitor configuration.
Administrator Response: This message typically
indicates a definition problem in the WebSphere
FNPU085I User user_name is already signed on Application Server related to Java Database
from another browser session. You must Connectivity (JDBC) providers, data sources, or
sign off from that session before you database definitions.Use the WebSphere Administrative
can sign on here. Console to diagnose and resolve the problem.
Explanation: The IBM Tivoli Monitoring for Network
Performance Web application is configured to allow FNPW020I The network data from the NetView
only one browser session per user. An active session Integrated TCP/IP Services Component
already exists for the user. on netview_host was received by Tivoli
Operator Response: Sign off from the currently active Monitoring for Network Performance.
session and sign on again. Contact your network Explanation: The NetView Integrated TCP/IP Services
administrator if you require access from multiple initialized and sent data to synchronize the network
browser sessions. topology to Tivoli Monitoring for Network
Administrator Response: The IBM Tivoli Monitoring Performance. There should always be a FNPW021I
for Network Performance Web application is configured message corresponding to every FNPW020I message. If
to allow only one browser session per user. This option you do not receive the corresponding message, look for
was set when the IBM Tivoli Monitoring for Network other error messages in the WebSphere Application
Performance Web application was installed. Refer to the Server log.

Chapter 3. Messages 35
FNPW021I • FNPW900I

Administrator Response: No action is required. stopped. Review the log and use the WebSphere
Administrative Console to diagnose and resolve
definition problems. See your database administrator
FNPW021I Tivoli Monitoring for Network
for other system conditions.
Performance successfully processed
network initialization data from the
netview_host NetView Integrated TCP/IP FNPW801E An error occurred trying to start the
Services Component, processed Tivoli Monitoring for Network
node_count network nodes, interface_count Performance purge utility. The purge
network interfaces, and subnet_count utility is not active and will not purge
subnetwork entries. data from your database.
Explanation: Tivoli Monitoring for Network Explanation: The purge utility was unable to start due
Performance has successfully processed information to an unknown reason. See the WebSphere Application
from the NetView Integrated TCP/IP Service log for more information and correct the problem.
Component.
Administrator Response: See the corresponding
Administrator Response: No action is required. exception, fix the problem, and restart the Tivoli
Monitoring for Network Performance Web application
from the WebSphere Administrative Console.
FNPW022I Tivoli Monitoring for Network
Performance successfully received
network update data from the FNPW802I The Tivoli Monitoring for Network
netview_host NetView Integrated TCP/IP Performance purge utility is beginning
Services Component. to purge data from the Tivoli
Monitoring for Network Performance
Explanation: The NetView Integrated TCP/IP Services
database.
Component has detected a change in the network
topology and sent data to synchronize this information Explanation: This data is being purged from the
with Tivoli Monitoring for Network Performance. There database.
should always be a FNPW023I message corresponding to
Administrator Response: Check the log files for the
every FNPW022I message. If you do not receive the
message FNPW803I , which indicates completion.
corresponding message, look for other error messages
in the WebSphere Application Server log.
FNPW803I The Tivoli Monitoring for Network
Administrator Response: No action is required.
Performance purge utility has completed
purging data from the Tivoli Monitoring
FNPW023I Tivoli Monitoring for Network for Network Performance database.
Performance successfully processed
Explanation: Data has been purged from the database.
network update data from the
netview_host NetView Integrated TCP/IP Administrator Response: No action is required.
Services Component, processed
node_count network nodes, interface_count
network interfaces, and subnet_count FNPW804E The Tivoli Monitoring for Network
subnetwork entries. Performance purge utility encountered
an error trying to purge the database.
Explanation: Tivoli Monitoring for Network
Performance has successfully processed information Explanation: See message.
from the NetView Integrated TCP/IP Services Administrator Response: Review the WebSphere
Component. Application Server log for other exception messages.
Administrator Response: No action is required. This can indicate a problem with database connectivity,
or other unexpected conditions. Resolve any problems
and issue the purge command again to purge the data.
FNPW800E A problem was detected while trying to The expired records that could not be processed are
establish a connection to the database. removed by the next purge process.
Explanation: A connection to the database could not
be established. There is additional exception FNPW900I A failure occurred while attempting to
information in the WebSphere Application Server log. communicate with the monitor_name
monitor. See the error log for more
Administrator Response: This message typically
information.
indicates a definition problem in WebSphere
Application Server related to Java Database Explanation: Communication with the monitor was
Connectivity (JDBC) providers, data sources, or not established. This could be caused by the monitor
database definitions, or the database system has been

36 IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting

 FNPW901E • FNPW946E

not being started, or a networking problem.

FNPW941E A configuration for monitor_name
Administrator Response: Make certain the monitor is monitor was not found.
running. Verify connectivity between the WebSphere
Explanation: The monitor might have been started
Application Server and the monitor.
prior to a configuration becoming available.
Administrator Response: Provide a configuration for
FNPW901E A failure occurred while attempting to
the monitor.
send data to monitor_name monitor. A
proper response was not received.
FNPW942I A configuration for monitor_name
Explanation: A connection to the monitor was
monitor was successfully sent to the
established, but a response from the monitor that is not
monitor.
valid was received.
Explanation: The monitor was restarted, or the
Administrator Response: Check the monitor log for
configuration for the monitor was updated, which
possible errors.
caused it to be sent to the monitor.
Administrator Response: No action is required.
FNPW902E A failure occurred while attempting to
add the security security_provider_name
provider. SSL encryption is not properly FNPW943I A resume command for monitor_name
initialized. monitor was successfully sent to the
monitor.
Explanation: The Secure Sockets Layer (SSL) security
provider could not be added. Explanation: An operator has requested that a
suspended monitor be restarted and the command to
Administrator Response: Check the monitor and
do so has been successfully sent.
WebSphere Application Server logs for more
information. Administrator Response: No action is required.

FNPW903E A failure occurred while attempting to FNPW944I A suspend command for monitor_name
initialize SSL encryption. monitor was successfully sent to the
monitor.
Explanation: An Secure Sockets Layer (SSL)
connection to the monitor could not be properly Explanation: An operator has requested that a
initialized. monitor be suspended and the command to do so has
been successfully sent.
Administrator Response: Check the monitor and
WebSphere Application Server logs for more Administrator Response: No action is required.
information. Make sure that the client certificates from
the monitor have been properly imported into the
FNPW945I A response to a real-time polling
WebSphere TrustStore. Verify that the WebSphere client
request has been received. The request
certificate has been properly imported into the monitor
identifier is request_identifier.
TrustStore.
Explanation: A real-time response has been received
from a monitor.
FNPW940E A failure occurred while attempting to
transmit the configuration to the Administrator Response: No action is required.
monitor_name monitor.
Explanation: The communication with the monitor has FNPW946E An error occurred while looking up a
not been established. This could be caused by the WebSphere Application Server resource.
monitor not being started or a networking problem. See
the WebSphere Application Server error log for more Explanation: A naming error occurred while the
information. monitor was looking up a WebSphere Application
Server resource. This could be caused by the resource
Administrator Response: Verify that the monitor is being incorrectly named at the time of installation or
running. If it is not, start the monitor. If the monitor is the WebSphere JNDI server not operating properly.
running, then a networking problem might exist.
Administrator Response: Verify that WebSphere
Application Server has properly started the JNDI
server. See the WebSphere Application Server log for
more information.

Chapter 3. Messages 37
FNPW947I • FNPW948E

FNPW947I A notification has been received that

monitor_name monitor is requesting
configuration updates.
Explanation: The monitor has contacted the
WebSphere Application Server and is requesting that
configuration updates be sent now.
Administrator Response: No action is required.

FNPW948E A configuration was successfully sent to

monitor_name monitor but the monitor
reported an internal error.
Explanation: A configuration was successfully
transferred to the monitor, but the monitor reported an
error. This could be caused by a configuration error or
an error that occurred on the monitor.
Administrator Response: See the monitor log for
details.

38 IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting

Chapter 4. Troubleshooting Overview
This chapter provides an overview on troubleshooting problems that you might
encounter in the IBM Tivoli Monitoring for Network Performance environment.

The upcoming chapters can assist you in:

v Classifying the type of problem.
v Determining which product is in error.
v Determining which component of Tivoli Monitoring for Network Performance is
in error.
v Collecting information about a problem.
v Reporting a problem to IBM customer support.

The following diagnostic tools are also available with Tivoli Monitoring for
Network Performance.
v Message and trace logs
v Log XML Viewer for the monitor message and trace logs
v SVC dumps for the monitor

The environment in which this product operates is displayed on Figure 2 on page

40.

© Copyright IBM Corp. 2004 39

Figure 2. Tivoli Monitoring for Network Performance integrated environment

If you need additional information about the components of this product, see the
Planning, Installation, and Configuration for IBM Tivoli Monitoring for Network
Performance Guide.

There are three users of Tivoli Monitoring for Network Performance:

v The network systems programmer is the overall administrator for Tivoli Monitoring
for Network Performance and is responsible for configuring and deploying the
product. For more information about the role and responsibilities of the network
administrator, see the IBM Tivoli Monitoring for Network Performance Administrator
Guide.
v The network operator is responsible for the daily operations of the network. The
network operator is mainly concerned with the health of the network resources
being monitored. For more information about the operator’s role and
responsibilities of the network operator, see the IBM Tivoli Monitoring for Network
Performance Operator Guide.
v The capacity planner is responsible for understanding the extent to which
network resources are being utilized, with the goal of anticipating the need to
allocate resources and distribute workload. Capacity planners customize
predefined reports about resource usage and trends using the Crystal Reporting
product. How to create reports is documented in the Tivoli Data Warehouse

40 IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting

 documentation. For more information about the role and responsibilities of the
capacity planner, see the IBM Tivoli Monitoring for Network Performance
Administrator Guide.

There are tools available for each of these users to help diagnose and troubleshoot
problems encountered within Tivoli Monitoring for Network Performance.
However, the majority of the troubleshooting is the responsibility of the network
systems programmer.

Troubleshooting Responsibilities for the Network Systems

Programmer
As a network systems programmer you are responsible for troubleshooting the
problems that you might encounter with Tivoli Monitoring for Network
Performance. Because Tivoli Monitoring for Network Performance interfaces with
other products, for example, IBM WebSphere Application Server and the DB2
product, you need to work closely with other network systems programmers or
system administrators in troubleshooting your problems.

These are some problems that might need troubleshooting:

v Data is not being collected by the monitor
v Data is missing or data is displayed incorrectly on the Tivoli Monitoring for
Network Performance user interface
v Error messages are generated when running the monitor or Web application
v DB2 errors that occur as a result of running Tivoli Monitoring for Network
Performance
v WebSphere Application Server errors that occur as a result of running Tivoli
Monitoring for Network Performance

Use the information in the following chapters as a guide to troubleshooting your

problems. The following tools are available to assist you with troubleshooting
problems:
v SVC dumps
v Monitor message and trace logs
v WebSphere Application Server logs
v DB2 messages
v z/OS SYSLOG

Troubleshooting Responsibilities for the Network Operator

As a network operator you receive messages on the Tivoli Monitoring for Network
Performance user interface. The message help is provided by the Task Assistant
function. Use the message help to resolve a problem before contacting the network
systems programmer. For information on message help, see Chapter 2, “Message
Overview,” on page 3.

You can also encounter problems, for example, Error 500, incorrect data, or slow
response time when monitoring network performance from the Tivoli Monitoring
for Network Performance user interface. The remaining chapters in this book
explain what to do in the event that these types of problems occur. Work with the
network systems programmer to do further problem determination.

Chapter 4. Troubleshooting Overview 41

Troubleshooting Responsibilities for the Capacity Planner
As a capacity planner you can experience problems while generating reports for
Tivoli Monitoring for Network Performance. If you are having problems generating
a report, a report is missing data or the report is not properly formatted, these
could be the source of the problem:
v Data in the Tivoli Monitoring for Network Performance database
v Tivoli Data Warehouse and data mart
v Enterprise Crystal reporting
v Extract, transform and load (ETL) process

Try to isolate the problem to a particular product, and follow the troubleshooting
procedures for that product. You might need to work with your network systems
programmer to do further problem determination.

42 IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting

Chapter 5. Classifying, Documenting, and Reporting Problems
Classifying Problems
When a problem occurs in an IBM Tivoli Monitoring for Network Performance
component, look at the symptoms described in this chapter to decide which type
of problem occurred. The symptoms for each of the five problem types have a
name that is synonymous with its keyword. Keywords are described in
“Diagnosing Problems” on page 61.

When you decide what the problem keyword is, you can use it to develop a
keyword string. See “Diagnosing Problems” on page 61 for information about the
keyword string.

This section describes the symptoms for ABEND or COREDUMP, DOC,

INCORROUT, MSG, and PERFM problems. The symptoms described can apply to
any Tivoli Monitoring for Network Performance component.
Notes:
1. If the symptoms do not match any of the problem types described in these
topics, see “Documenting any Problem” on page 47 to describe the problem.
2. The Tivoli Monitoring for Network Performance Web application runs on either
the z/OS or AIX operating system. This chapter outlines information by
operating system, if applicable. If a section does not contain separate z/OS and
AIX information, then the operating system is not a factor.
3. Reference information about the products that interface with the Tivoli
Monitoring for Network Performance component is provided and you are
referred to the documentation for the other product.

ABEND or COREDUMP
The ABEND or COREDUMP symptoms apply to the following Tivoli Monitoring
for Network Performance components:
v Monitor
v Web application

z/OS Abends
Choose the ABEND keyword when one or more of the following symptoms occur:
Monitor
v A z/OS ABEND message is displayed at the system console. The
message that contains the abend code is found in the SYSLOG.
v The message FNPM013E is displayed, which indicates that the monitor
abended.
Web application
WebSphere Application Server SVC dump is generated.
Monitor or Web application
v The message IEA822I is displayed, which indicates that a Java
Transaction Dump is generated.
v A Language Environment® Dump, CEEDUMP is generated.
v A JAVADUMP is generated.

© Copyright IBM Corp. 2004 43

 v Out of Memory signal is received. You can receive one or more Java
dumps depending on the JAVA_DUMP_OPTS you have enabled.
v A DB2 SVC dump is received.

These are the classifications for abend problems:

User abend codes
Tivoli Monitoring for Network Performance does not issue any user
abends. However, other products or z/OS components can issue user
abends because of a problem with Tivoli Monitoring for Network
Performance.
System abend codes
System abend codes result from such actions as issuing a system program
call (PC) instruction in a program with an incorrect PC number.
Program check abend problems are hardware-detected error conditions. For
example, a branch or store to an address that is incorrect, or an attempt to
run an instruction that is incorrect (ABENDS0C4) or (ABENDS0C1).

AIX Application Core Dumps

Choose the COREDUMP keyword when one or more of the following symptoms
occurs:
WebSphere Application Server
The WebSphere Application Server spontaneously stopped. Look for a Java
thread dump file. The Java virtual machine (JVM) creates the file in the
product directory structure, with a name similar to javacore<number>.txt.
DB2
The DB2 product ended unexpectedly. A core file is generated by the
operating system. The DB2 core files are located in the path
$HOME/sqllib/db2dump/core_directory, where core_directory is the core
path directory name.

If you have categorized your problem as an ABEND OR COREDUMP, see

“Documenting ABEND Problems” on page 49.

Categories See this information

System abend codes z/OS MVS System Codes
WebSphere Application Server (z/OS) abend WebSphere Application Server for z/OS
codes Troubleshooting
DB2 abend codes (z/OS) z/OS MVS System Codes
WebSphere Application Server (AIX) code IBM WebSphere Application Server
dump information Troubleshooting
DB2 (AIX) COREDUMP information DB2 Information Center
JAVA_DUMP_OPTS, JAVADUMP, and JAVA IBM Developer Kit, Runtime Environment, Java
transaction dump 2 Technology Edition, Version 1.3.1 Diagnostic
Guide

DOC
Choose the DOC keyword when one or more of the following symptoms is true
for the documentation or online help:

44 IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting

 v It contains incomplete or inaccurate information about installation, operation,
customization, messages, or diagnosis.
v It is inconsistent in describing the use of a program function.

Report these problems to IBM customer support only if the documentation

problem affects the operation or use of the Tivoli Monitoring for Network
Performance program.

If you have categorized your problem as a documentation problem, see

“Documenting DOC Problems” on page 58.

INCORROUT
Choose the INCORROUT keyword when one of the following symptoms occurs:
v For all Tivoli Monitoring for Network Performance components:
– Errors in the message or trace logs
v For the monitor:
– No data is received for any portfolio item on the Tivoli Monitoring for
Network Performance Web application.
– Data is received for some of the portfolio items on the Tivoli Monitoring for
Network Performance Web application.
– Data is not being collected according to the Configured Monitor schedule.
– Data is missing or incorrect when you view the Tivoli Monitoring for
Network Performance Web application.
– An error message is received on the z/OS system console indicating a failure.
v For the Web application:
– Error 500 - Internal Server Error is received.
– Problems occur reading or writing to the DB2 database. See message
FNPU004E.
– The WebSphere Application Server times out while you are using the Tivoli
Monitoring for Network Performance Web application.
– Connection problems between WebSphere Application Server and the
monitor.
v For problems with IBM Tivoli Monitoring for Network Performance extract,
transform, and load (ETL) process:
– The ETLs fail or do not complete.
– The ETL does not run at scheduled time.
– The Tivoli Monitoring for Network Performance report draws, but no graph
or chart is present

If you have categorized your problem as an incorrect output problem, see

“Documenting INCORROUT Problems” on page 59.

MSG
A problem can cause a message to be displayed at the system console or on the
Web application. Choose the MSG keyword when one or more of the following
symptoms occur:
v The message that is received is not the expected response or indicates an error
condition.

Chapter 5. Classifying, Documenting, and Reporting Problems 45

 v The message is issued with an incorrect format (misspelled words or unprintable
characters in the message), or the message is not displayed as it is documented
in the Task Assistant or in this guide.
Each message issued by Tivoli Monitoring for Network Performance is in the
FNPxnnnz format.

Note:

If one of the following situations occur, see “Documenting INCORROUT

Problems” on page 59 for information about documenting INCORROUT problems.
v A message contains incorrect data.
v A message is issued under conditions that normally would not cause the
message to be issued.
v The message indicates missing data.

If the message describes an abend, see “Documenting ABEND Problems” on page

49.

Categories See this information

Web application and monitor messages Chapter 3, “Messages,” on page 7

PERFM
Choose the PERFM keyword if performance is not as expected. Performance
problems can occur because one or more of the following conditions exist:
v Processor utilization is increased.
– The sampling interval for a monitor definition should be 5 minutes or more.
– Verify that the monitor is not collecting unnecessary network information.
v Response time on the Tivoli Monitoring for Network Performance Web
application is slow. The pages are slow to draw or display data.
– Ensure that the machine running WebSphere Application Server and the DB2
product meets the hardware and software configurations.
v Data displayed in the Tivoli Monitoring for Network Performance Web
application is delayed or different from what is actually displayed on the
monitored host.
– Check the value of the dbcache. If it is large, there could be possible lag time
in what is displayed on the Tivoli Monitoring for Network Performance Web
application.

Performance can be adversely affected by:

v Enabling tracing on WebSphere Application Server.
v Changing the monitor trace level from DEBUG_MIN to DEBUG_MAX.

If you have categorized your problem as a performance problem, see

“Documenting PERFM Problems” on page 60.

Categories See this information

Tuning information IBM Tivoli Monitoring for Network Performance
Planning, Installation, and Configuration Guide
and Tuning IBM Tivoli Monitoring for Network
Performance

46 IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting

Documenting and Reporting Problems
IBM customer support is the first point of contact for Tivoli Monitoring for
Network Performance customers who need help with a program problem after
their installation is complete. Each type of problem requires specific
documentation. Although you might not know your problem type, gather the basic
information described in the following section before calling IBM customer
support.

Also, check Chapter 7, “Resolving Problems,” on page 77 to see if your problem

matches any of the symptoms described there.

Documenting any Problem

For all problems, including those for which you cannot identify the type, the
information gathered should include the following items:

h The Tivoli Monitoring for Network Performance component ID number,

FMID, release number, and Recommended Service Upgrade (RSU) level

Record the Tivoli Monitoring for Network Performance component ID number, the
function modifier identification (FMID), and build level of the current program.
The build level for the Tivoli Monitoring for Network Performance Web
application is located on the bottom left-hand corner of the Welcome page. The
build level for the monitor is displayed on the z/OS system console, in message
FNPM001I, when the monitor is started. It can also be found in the monitor message
log (msg_fnp_monitor.log). The build level is also on the command line interface
(CLI) main menu.

h Recently applied Tivoli Monitoring for Network Performance maintenance,

for example, a program temporary fix (PTF) or an authorized program analysis
report (APAR) or a fix pack

Record any recently applied Tivoli Monitoring for Network Performance

maintenance, such as PTFs, APAR fixes or fix packs.

h The scenario leading to the problem

Research the scenario leading to the problem, including what was done before the
problem occurred. Record the exact steps taken, including the following:
v What was the first indication of the problem?
v What were you trying to do?
v What should have happened?
v What actually did happen?
v Has the function worked before?
v Can you recreate the problem?

h Monitor logs and Configuration XML File

Use the monitor_doc_coll.sh script to collect all of the monitor logs from each
system that might have contributed to the problem. This includes the configuration
XML file, message logs, and trace logs.

h WebSphere Application Server message and trace logs

Chapter 5. Classifying, Documenting, and Reporting Problems 47

 Collect WebSphere Application Server message and trace logs. These can contain
information about the Tivoli Monitoring for Network Performance Web
application.

h z/OS SYSLOG

Locate and save a copy of the system log before and during the error. The system
log is the data set that stores job-related information, operational data, descriptions
of unusual occurrences, commands, and messages.

h AIX system log (if applicable and active)

If you are running your WebSphere Application Server and the DB2 product on the
AIX system, locate and save the AIX SYSLOG. It is typically located in the
/var/spool/syslog directory.

h The itmnp.properties file

The itmnp.properties file is located in the /etc/itmnp directory. The

monitor_doc_coll.sh script collects this file.

h The itmnp.env file

Locate and save this file. You customized this file before you installed the Tivoli
Monitoring for Network Performance Web application. Clear the following
applicable passwords before you send this file.
v DB2PASSWD=xxxxxx
v WASADMIN_PASSWORD=xxxxxx
v LDAP_SERVERPW=xxxxx

h The itmnp_install.env file (AIX system)

Locate and save this file. To locate this file, change to the bin directory of your
installation path for the Web application installation files on your AIX system. You
can locate the exact installation path by looking at the last occurrence of the install
dir: statement in the /tmp/itmnp.log file. See IBM Tivoli Monitoring for Network
Performance Planning, Installation, and Configuration Guide for more information on
the itmnp_install.env file.

h The itmnp_install.log (AIX system)

Locate and save this file. To locate this file, change to the bin directory of your
installation path for the Web application installation files on your AIX system. You
can locate the exact installation path by looking at the last occurrence of the install
dir: statement in the /tmp/itmnp.log file. See IBM Tivoli Monitoring for Network
Performance Planning, Installation, and Configuration Guide for more information on
the itmnp_install.log file.

h The itmnp.log file

Locate and save this file. It was created initially when you attempted the
installation of the Tivoli Monitoring for Network Performance Web application. On
z/OS, this file is located in the directory where the itmnp21zos.tar file was
untarred. On your AIX system, this file is located in the /tmp/itmnp.log file.

48 IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting

 h The file that contains the installation messages, if any

If you piped your output of the Tivoli Monitoring for Network Performance Web
application installation to a file, you must locate and save that file.

h Screen captures from the Tivoli Monitoring for Network Performance Web
application

Provide screen captures from the Tivoli Monitoring for Network Performance Web
application if they provide pertinent information about the problem.

h Dumps (if applicable)

If available, provide any or all of the following dumps:

v SVC
v Java Transaction
v CEEDUMPs
v JAVADUMPs

h MQSeries® error and FFDC logs on an AIX system, if applicable

Locate and save the MQSeries logs. The default directory is /var/mqm/log.

h Logs for the NetView TCP/IP services component (ITSC), if applicable

Locate and save the ITSC logs. The default directory is /usr/OV/log.

h Tivoli Data Warehouse logs, if applicable

Locate and save the Tivoli Data Warehouse logs.

Categories See this information

ITSC logs IBM Tivoli NetView User’s Guide
Tivoli Data Warehouse logs Installing and Configuring Tivoli Data
Warehouse

Documenting ABEND Problems

To obtain the information you need before reporting abend problems to IBM
customer support, collect the information indicated in the following list:

h Any Problem Checklist information

All applicable information in the list under “Documenting any Problem” on page
47.

h The abend code

The abend code can be located in the following places:

v In the ABEND message that is displayed at the system console
v In the FNPM013E message that is issued when a dump is captured for the monitor
v In a message in the SYSLOG

Chapter 5. Classifying, Documenting, and Reporting Problems 49

 The abend code might be an abend code for another product. If information about
the location of an abend in this chapter or the chapter on resolving problems does
not reference a problem with Tivoli Monitoring for Network Performance, follow
the process of the other product documentation for abends.

h An unformatted dump of the abend

If an SVC dump occurs, save the dump data set (for example, SYS1.DUMP). The
terms dump data set and unformatted dump refer to the unchanged data set of the
dump. The unformatted dump is the data required by IBM customer support.

You can view the dump data set, without altering it, by using an interactive dump
viewing utility, for example, Interactive Problem Control System (IPCS).

h A core file

If a COREDUMP occurs, locate and save the core file in a permanent location. The
WebSphere Application Server core files are found in the WebSphere Application
Server product directory structure, with a name similar to javacore<number>.txt.
The DB2 core files are located in the path
$HOME/sqllib/db2dump/core_directory, where core_directory is the core path
directory name.

h CEEDUMP or JAVADUMP

If a CEEDUMP or JAVADUMP occurs, locate and save the CEEDUMP or

JAVADUMP file. See page 54 or 56 for the location of the file.

hInformation about the location of the abend

Because Tivoli Monitoring for Network Performance interfaces with many different
products, you must determine which product actually abended. Select one of the
following procedures to determine the location of the abend:
v You received a monitor SVC dump. Follow the steps on page 50.
v You received a Java Transaction dump. Follow the steps on page53.
v You received a CEEDUMP. Follow the steps on page 54.
v You received a JAVADUMP. Follow the steps on page 56.

h Finding abend information with a monitor signal handler dump

Use the IPCS dump-formatting utility to format the dump.

1. From the IPCS Browse Option Pointer window or the IPCS storage window,
issue the subcommand:
IPCS SUMMARY FORMAT
This subcommand will display the general purpose registers at the time the
data was dumped.
2. Issue the FIND command to find the Request Block (RB) where the SVC
dump was issued:
F 00020033

50 IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting

PRB: 006E2E00
-0020 XSB...... 7FFFEE10 FLAGS2... 80 RTPSW1... 00000000 00000000 RTPSW2... 00000000 05F0A000
-0008 FLAGS1... 02000001 WLIC..... 00020033
+0000 RSV...... 00000000 00000000 SZSTAB... 00110082 CDE.00BC0B90 OPSW...078C1400 8D80AF44
+0018 SQE...... 00000000 LINK..... 006E26E0
+0020 GPR0-3... 00000000 7F53EAB0 00000048 82173AB8
+0030 GPR4-7... 006FF098 0D4F0540 0DA7F006 0DA7F290
+0040 GPR8-11.. 00000001 025B773C 7F53EAB0 0DA7F1FC
+0050 GPR12-15. 025B7088 00006628 00000001 0DA7F290

3. The next Request Block should be the SVRB containing the registers at the
time the signal handler dump was issued. Record the address in GPR13. In
this example it is x’DA1CDD0’.

SVRB: 006FDB90
-0020 XSB...... 7FFFC638 FLAGS2... 80 RTPSW1... 00000000 00000000 RTPSW2... 00000000 00000000
-0008 FLAGS1... 02000007 WLIC..... 0002003C
+0000 RSV...... 00000000 00000000 SZSTAB... 001ED022 CDE......00000000 OPSW...070C5000 840336
+0018 Q........ 00000000 LINK..... 006E2E00
+0020 GPR0-3... 0DA1CF15 0DA1CED0 0D81CA01 0DA06600
+0030 GPR4-7... 0DA63040 0D80B30A 0DA1CF14 0DA1CEC6
+0040 GPR8-11.. 0DA63048 0DA1CF15 00000000 00000001
+0050 GPR12-15. 0D80AC18 0DA1CDD0 8D80AF2A 00000000

4. Issue the FIND command to locate the TCB that abended:

FIND TCB: PREV
Record the TCB address. In this example, it is x’6E26E0’.

TCB: 006E26E0
+0000 RBP...... 006FDB90 PIE...... 01FC16E0 DEB...... 00000000 TIO...006CCFE8 CMP....00000000
+0014 TRN...... 40000000 MSS...... 7FFB9BE0 PKF...... 80 FLGS..01008000 00 LMP....FF
+0023 DSP...... FF LLS...... 00000000 JLB...... 00000000 JPQ...... 00000000

5. From the IPCS Storage window, LIST the storage address in GPR13,
(x’DA1CDD0’).
0DA1CDD0 00000000 0DA62F38 00000000 00000000 | .....w.......... |
Go to offset x’4’ into GPR13, the previous save area pointer, and list that
address. For example,
L DA62F38.

0DA62F38 10404040 0DA62E80 | . .w.. |

0DA62F40 0DA1CDD0 8D80D684 0D80AC18 0D942558 | .~.}..Od.....m.. |
0DA62F50 0DA62FD0 8DA63040 0D80D2B2 0DA06600 | .w.}.w. ..K..... |
0DA62F60 0D81C688 0D944BF0 0D81CACC 0DA63048 | .aFh.m.0.a...w.. |
0DA62F70 0DA6304C 00000000 85F74CC0 0DA5DAC0 | .w.<....e7<{.v.{ |
6. Go to offset x’44’ into the previous save area pointer from step 5 and list this
address. This is GPR12. In this example, this is x’DA5DAC0’.
This is the Common Anchor Area (CAA). The first word should contain
x’00000800’. If the word does not contain this value, go to step 11.
v Go to offset x’2D8’ into the CAA. If the word contains zeroes, go to step 11.
If the word is non-zero, issue the LIST command to list this address. This
should be the Common Information Block (CIB). There should be an
eye-catcher (control block id) of the CIB at this storage location.
v Go to offset x’4C’into the CIB. If the word contains zeroes, go to step to
step 11. If the word is non-zero, list this address. This should be the
Language Environment Machine State Block (ZMCH). There should be an

Chapter 5. Classifying, Documenting, and Reporting Problems 51

 eye-catcher of the ZMCH at this storage location as in the following
example.

0DA5C578 E9D4C3C8 02000001 | ZMCH.... |

0DA5C580 0D942558 0DA5F240 0DA072E8 0D80FA1A | .m...v2 ...Y.... |
0DA5C590 0D81CB27 0D944BF0 0D81C688 000001F6 | .a...m.0.aFh...6 |
0DA5C5A0 0D81CB27 0D81CB27 0D81CB27 85F74CC0 | .a...a...a..e7<{ |
0DA5C5B0 0DA5DAC0 0DA5F1A8 8D80FF10 0D867A30 | .v.{.v1y.....f:. |
0DA5C5C0 078D0400 8D867A54 00020001 00000001 | .....f:......... |

The GPRs 0-15 start at x’8’ into the ZMCH. The Program Status Word (PSW)
at the time of the abend is at offset x’4C’ in the ZMCH. The Extended PSW
interrupt code is at offset x’52’ in the ZMCH. In this case, it is x’0001’,
indicating a x’0C1’ abend occurred.
For more information on the ZMCH, see z/OS Language Environment Vendor
Interfaces.
7. List the address in the second word of the PSW. In this example, this is
x’D867A54’. Record this address.
8. Issue the FIND command for COMPILED ON:
F ’COMPILED ON’
If you find this string, record the address of the string and the module name
prior to COMPILED ON. Also record the PTF level. The module name in this
example is cs390_UDPTable. The address of the string in this example is
x’D869ED0’.

0D869ED0 00000C18 00000000 83A2F3F9 F06DE4C4 | ........cs390_UD |

0D869EE0 D7E38182 938540C3 D6D4D7C9 D3C5C440 | PTable COMPILED |
0D869EF0 D6D540C1 979940F1 F140F2F0 F0F440C1 | ON Apr 11 2004 A |
0D869F00 E340F0F2 7AF1F47A F3F440C6 C9E7D3C5 | T 02:14:34 FIXLE |
0D869F10 E5C5D37E D5D66DD7 E3C6E240 00000000 | VEL=NO_PTFS .... |

9. Issue the FIND previous command for 2004 or greater.

F 2004 PREV
Look for a string similar to 20040411021434010200. If you find this string,
record the address of this string. In the following example, the string address
is x’D8670C0’.
0D8670C0 F2F0F0F4 F0F4F1F1 F0F2F1F4 F3F4F0F1 | 2004041102143401 |
0D8670D0 F0F2F0F0 00000000 47F0F022 01C3C5C5 | 0200.....00..CEE |
10. If the PSW is located between the addresses recorded in the last two steps,
then this is probably an abend in Tivoli Monitoring for Network Performance.
11. To provide traceback information, issue the following command:
IPCS VERBX LEDATA ’TCB(tcbaddr) CEEDUMP’
The tcbaddr is the TCB address you recorded in Step 4.
In the following example, you can see that the process_get function , took the
abend.

52 IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting

TCB(6E26E0) CEEDUMP
********************************************************************************

LANGUAGE ENVIRONMENT DATA

********************************************************************************

Language Environment Product 04 V01 R04.00

Information for enclave main

Information for thread 0DB5A2000000000C

PCB Address: 0D907F08

Traceback:

DSA Addr Program Unit PU Addr PU Offset Entry E Addr E Offset Load Mod Status
0DA1CDD0 0D80AC18 -0D80AC1A .FNPMSDMP 04/11/04 AT 02.09 NO_PTFS
0D80AC18 -0D80AC1A SUBPOOL2 Call
0DA62F38 0D80D278 +0000040A sig_sdump 0D80D278 +0000040A SUBPOOL2 Call
0DA62E80 05F74E20 -00000106 CEEPGTFN 05F74CC0 +0000005A CEEPLPKA Call
0DA62820 05B31128 +000007EC __zerros 05B31128 +000007EC CEEEV003 Call
0DA5FC88 CEEHDSP 05EA5520 +00000C0E CEEHDSP 05EA5520 +00000C0E CEEPLPKA Call
0DA5F1A8 0D80F9E0 +00058072 process_get 0D80F9E0 +00058072 SUBPOOL2 Exception
0DA5F0B8 0D811578 +00000292 process_client_request
0D811578 +00000292 SUBPOOL2 Call
0DA5EFB0 0D814BC0 +00000D3E process_client_send
0D814BC0 +00000D3E SUBPOOL2 Call
0DA5EEB8 0D817C20 +000001E2 process_client
D817C20 +000001E2 SUBPOOL2 Call
0DA5EB90 0D816B60 +0000075A child_csapi_server
0D816B60 +0000075A SUBPOOL2 Call
0DA5EAD8 05F74E20 -00000106 CEEPGTFN 05F74CC0 +0000005A CEEPLPKA Call
7F527E38 CEEOPCMM 00BA6618 +00000932 CEEOPCMM 00BA6618 +00000932 CEEBINIT Call

hFinding abend information with a Java Transaction Dump

Use the IPCS dump-formatting utility to format the dump.

1. From the IPCS Browse Option Pointer window or the IPCS storage window,
issue the following subcommand:
IPCS SUMMARY FORMAT
This will display the major control blocks for the address space in error. Go to
the end of this display to the TCB SUMMARY. Look in the CMP column for the
TCB that abended. Note the abend code and the TCB address.
In the following example, TCB 6C3638 took a x’0C4’ abend.

Chapter 5. Classifying, Documenting, and Reporting Problems 53

 * * * * T C B S U M M A R Y * * * *

JOB ROOT5 ASID 0047 ASCB 00F91400 FWDP 00F42700 BWDP 00FB0B00 PAGE 00000003
TCB AT CMP NTC OTC LTC TCB BACK PAGE
006FE0A8 00000000 00000000 00000000 006FFD90 006FC0E0 00000000 00000004
006FC0E0 00000000 00000000 006FE0A8 00000000 006FFD90 006FE0A8 00000001
006FFD90 00000000 006FC0E0 006FE0A8 006F8680 006F8680 006FC0E0 00000002
006F8680 00000000 00000000 006FFD90 006F80C8 006F80C8 006FFD90 00000003
006F80C8 00000000 00000000 006F8680 006DFE88 006DFE88 006F8680 00000004
006DFE88 00000000 00000000 006F80C8 006C2E88 006DF9B8 006F80C8 00000004
006DF9B8 00000000 00000000 006DFE88 00000000 006DF728 006DFE88 00000001
006DF728 00000000 006DF9B8 006DFE88 00000000 006DF498 006DF9B8 00000002
006DF498 00000000 006DF728 006DFE88 00000000 006DF128 006DF728 00000003
006DF128 00000000 006DF498 006DFE88 00000000 006C9E88 006DF498 00000004
006C9E88 00000000 006DF128 006DFE88 00000000 006C9BF8 006DF128 00000004
006C9BF8 00000000 006C9E88 006DFE88 00000000 006C9968 006C9E88 00000001
006C9968 00000000 006C9BF8 006DFE88 00000000 006C97D0 006C9BF8 00000002
006C97D0 00000000 006C9968 006DFE88 00000000 006C9540 006C9968 00000003
006C9540 00000000 006C97D0 006DFE88 00000000 006C92B0 006C97D0 00000004
006C92B0 00000000 006C9540 006DFE88 00000000 006C9020 006C9540 00000004
006C9020 00000000 006C92B0 006DFE88 00000000 006C7D90 006C92B0 00000001
006C7D90 00000000 006C9020 006DFE88 00000000 006C7740 006C9020 00000002
006C7740 00000000 006C7D90 006DFE88 00000000 006C74B0 006C7D90 00000003
006C74B0 00000000 006C7740 006DFE88 00000000 006C7180 006C7740 00000004
006C7180 00000000 006C74B0 006DFE88 00000000 006C4E88 006C74B0 00000004
006C4E88 00000000 006C7180 006DFE88 00000000 006C4BF8 006C7180 00000001
006C4BF8 00000000 006C4E88 006DFE88 00000000 006C4968 006C4E88 00000002
006C4968 00000000 006C4BF8 006DFE88 00000000 006C47D0 006C4BF8 00000003
006C47D0 00000000 006C4968 006DFE88 00000000 006C44B8 006C4968 00000004
006C44B8 00000000 006C47D0 006DFE88 00000000 006C4228 006C47D0 00000004
006C4228 00000000 006C44B8 006DFE88 00000000 006C3E88 006C44B8 00000001
006C3E88 00000000 006C4228 006DFE88 00000000 006C3CF0 006C4228 00000002
006C3CF0 00000000 006C3E88 006DFE88 00000000 006C3A60 006C3E88 00000003
006C3A60 00000000 006C3CF0 006DFE88 00000000 006C38C8 006C3CF0 00000004
006C38C8 00000000 006C3A60 006DFE88 00000000 006C3638 006C3A60 00000004
006C3638 940C4000 006C38C8 006DFE88 00000000 006C33A8 006C38C8 00000001
006C33A8 00000000 006C3638 006DFE88 00000000 006C3118 006C3638 00000002
006C3118 00000000 006C33A8 006DFE88 00000000 006C2E88 006C33A8 00000003
006C2E88 00000000 006C3118 006DFE88 00000000 00000000 006C3118 00000004

Record the TCB address.

2. Determine the module in error using the steps on page 50, with the following
exceptions, starting at step 2 in the ″Finding abend information with a monitor
signal handler dump″ section on page 50.
v Record the address of GPR12 from the SVRB in Step 3 on page 51, instead of
GPR13. GPR12 is the address of the CAA. See Step 6.
v Skip step 5.

hFinding abend information in a CEEDUMP

The Language Environment dump generates output of data and storage from the
Language Environment run-time environment on an enclave basis.

Under z/OS UNIX System Services, if the application is running in an address

space created as a result of a fork(), spawn(), spawnp(), vfork(), or one of the exec
family of functions, then the CEEDUMP is placed in the hierarchical file system
(HFS) in one of the following directories in the specified order:
1. The directory found in the _CEE_DMPTARG environment variable.
2. The current working directory, if this is not the root directory (/), and the
directory is write accessible.

54 IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting

 3. The directory found in the TMPDIR environment variable (indicates the
location of a temporary directory if it is not /tmp) .
4. The /tmp directory.

Using the following example, which is only part of a CEEDUMP, you can see that
function ping_4_390 in 390icmp.c took the exception. Further examination of the
traceback information, tells you that the itmnp code is being run
(Java_com_tivoli_itmnp_monitor_icmp_ICMP_ping). It is very likely that the abend
is in the Tivoli Monitoring for Network Performance code.

Traceback:
DSA Addr Program Unit PU Addr PU Offset Entry E Addr E Offset Load Mod Status
18F45308 CEEHDSP 05F4ABF0 +000048A6 CEEHDSP 05F4ABF0 +000048A6 CEEPLPKA Call
18F44800 ./390icmp.c 1F3DDC58 +552B9A14 ping_4_390 1F3DDC58 +552B9A14 *PATHNAM Exception
18F44730 ./libicmp.c 1F3CC0D8 +0000011C Java_com_tivoli_itmnp_monitor_icmp_ICMP_ping
1F3CC0D8 +0000011C *PATHNAM Call
18F44630 com/tivoli/itmnp/monitor/icmp/ICMP.java
1ED70460 +00000140 com/tivoli/itmnp/monitor/icmp/ICMP.ping(Ljava/lang/Str
1ED70460 +00000140 Call
18F44500 7CD2AED8 +00000534 mmipSelectInvokeJavaMethod
7CD2AED8 +00000534 *PATHNAM Call
18F44408 7CD2AFC0 +0000044C mmipSelectInvokeSynchronizedJavaMethod
7CD2AFC0 +0000044C *PATHNAM Call
18F442F8 7CD2AED8 +00000534 mmipSelectInvokeJavaMethod
7CD2AED8 +00000534 *PATHNAM Call
18F44228 7CD2A958 +00000AB4 INVOKDMY 7CD2A958 +00000AB4 *PATHNAM Call
18F44158 7CD29E18 +00000096 EXECJAVA 7CD29E18 +00000096 *PATHNAM Call
18F440A8 /u/sovbld/cm131s/cm131s-20031114/src/jvm/pfm/xe/mmi/mmi_supp
7CD4A4D0 +000000EC mmipExecuteJava
7CD4A4D0 +000000EC *PATHNAM Call
18F43F78 /u/sovbld/cm131s/cm131s-20031114/src/jvm/sov/xe/common/run.c
7CD50860 +000004D0 xeRunDynamicMethod
7CD50860 +000004D0 *PATHNAM Call
18F43EC8 /u/sovbld/cm131s/cm131s-20031114/src/jvm/sov/ci/jvm.c
7CAD1960 +000000E0 threadRT0 7CAD1960 +000000E0 *PATHNAM Call
18F43E18 /u/sovbld/cm131s/cm131s-20031114/src/jvm/sov/xm/thr.c
7CD716B0 +000001F0 xmExecuteThread
7CD716B0 +000001F0 *PATHNAM Call
18F43D70 /u/sovbld/cm131s/cm131s-20031114/src/jvm/pfm/xe/common/xe_th
7CD5C8E0 +0000006C threadStart 7CD5C8E0 +0000006C *PATHNAM Call
18F43C08 /u/sovbld/cm131s/cm131s-20031114/src/hpi/pfm/threads_utils.c
7C92F3D0 +00000A38 ThreadUtils_Shell
7C92F3D0 +00000A38 *PATHNAM Call
18F43B50 05B8C910 +0000001A @@GETFN 05B8C868 +000000C2 CEEEV003 Call
7F3F8E78 CEEOPCMM 00BB1BD8 +00000914 CEEOPCMM 00BB1BD8 +00000914 CEEBINIT Call

Using the following Condition Information for Active Routines, you can see that a
x'0C4' abend occurred (Interruption Code ....004). From this information, you can
build a symptom string to search the IBM support database.

Chapter 5. Classifying, Documenting, and Reporting Problems 55

Condition Information for Active Routines
Condition Information for ./390icmp.c (DSA address 18F44800)
CIB Address: 18F45C48
Current Condition:
CEE3204S The system detected a protection exception (System Completion Code=0C4).
Original Condition:
CEE3204S The system detected a protection exception (System Completion Code=0C4).
Location:
Program Unit: ./390icmp.c
Entry: ping_4_390
Statement: Offset: +552B9A14
Machine State:
ILC..... 0000 Interruption Code..... 0004
PSW..... 078D0400 F469766C
GPR0..... 61622E72 GPR1..... 18F44898 GPR2..... 0000001F GPR3..... 1F3DDC92
GPR4..... 18F446EC GPR5..... 18D8FEE0 GPR6..... 1F3E0598 GPR7..... 1F381028
GPR8..... 00000020 GPR9..... 00000020 GPR10.... 18F446EC GPR11.... 1ED70680
GPR12.... 18F42B38 GPR13.... 18F44800 GPR14.... 9F3DDF66 GPR15.... 7469766C
FPC...... 00480000
FPR0..... 3F854888 2F0E0A85 FPR1..... 3F827A20 578E5C4F
FPR2..... 3F817ACC 4EF88B97 FPR3..... 00000000 00000000
FPR4..... 412E8480 00000000 FPR5..... 00000000 00000000
FPR6..... 3FD99999 80000000 FPR7..... 00000000 00000000
FPR8..... 00000000 00000000 FPR9..... 00000000 00000000
FPR10.... 00000000 00000000 FPR11.... 00000000 00000000
FPR12.... 00000000 00000000 FPR13.... 00000000 00000000
FPR14.... 00000000 00000000 FPR15.... 00000000 00000000

For more information on CEEDUMPs, see z/OS Language Environment Debugging

Guide.

hFinding abend information in a JAVADUMP

The JAVADUMP produces files that contain diagnostic information related to the
JVM and a Java application captured at a point during run-time. For example, the
information can relate to the operating system, the application environment,
threads, native stack, locks, and memory.

The JVM checks each of the following locations for existence and write accessible
permission, and stores the JAVADUMP in the first location available. You must
have enough free disk space for the JAVADUMP file to be written correctly.
1. The location specified by the IBM_JAVACOREDIR environment variable if set
(_CEE_DMPTARG on z/OS.)
2. The current working directory of the JVM processes
3. The location specified by the TMPDIR environment variable, if set

Use the following example, which is only part of a JAVADUMP, to get current
thread details. The last routine to have control before signal handling received
control is ping_4_390. A further examination from the traceback shows that Tivoli
Monitoring for Network Performance code is involved. From this information, you
can build a symptom string to search the IBM database.

56 IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting

"WorkerThread-7" (sys_thread_t:1f381248)

Native Thread State: USER RUNNING

Native Stack Data: base: 18f43e08 top: 0 pointer: 18fc3e08 used(e70bc1f8) free(18fc3e08)

Monitors Held: (not implemented)

Native Stack

------------

ame Entry Name Statement ID

/u/sovbld/cm131s/cm131s-20031114/src/xhpi/pfm/xhpi.c Diagnostics 1889

/u/sovbld/cm131s/cm131s-20031114/src/jvm/sov/dg/dg_javacore.c dgGenerateJavacore 495
/u/sovbld/cm131s/cm131s-20031114/src/jvm/sov/dg/dg_dump.c dgDumpHandler 269
/u/sovbld/cm131s/cm131s-20031114/src/jvm/sov/xm/exc.c abortJVM 427
/u/sovbld/cm131s/cm131s-20031114/src/jvm/sov/xm/signals.c panicSignalHandler 271
/u/sovbld/cm131s/cm131s-20031114/src/hpi/pfm/exception_md.c sysSignalCatchHandler 169
/u/sovbld/cm131s/cm131s-20031114/src/hpi/pfm/interrupt_md.c userSignalHandler 344
/u/sovbld/cm131s/cm131s-20031114/src/hpi/pfm/interrupt_md.c intrDispatch 779
@@GETFN

__zerros

CEEHDSP CEEHDSP

CEEHDSP CEEHDSP

./390icmp.c ping_4_390

./libicmp.c Java_com_tivoli_itmnp_monitor_icmp_ICMP_ping 1043

com/tivoli/itmnp/monitor/icmp/ICMP.java com/tivoli/itmnp/monitor/icmp/ICMP.ping(Ljava/lang/String;
mmipSelectInvokeJavaMethod

mmipSelectInvokeSynchronizedJavaMethod

mmipSelectInvokeJavaMethod

INVOKDMY

EXECJAVA

/u/sovbld/cm131s/cm131s-20031114/src/jvm/pfm/xe/mmi/mmi_support.c mmipExecuteJava
/u/sovbld/cm131s/cm131s-20031114/src/jvm/sov/xe/common/run.c xeRunDynamicMethod 892
/u/sovbld/cm131s/cm131s-20031114/src/jvm/sov/ci/jvm.c threadRT0 339
/u/sovbld/cm131s/cm131s-20031114/src/jvm/sov/xm/thr.c xmExecuteThread 1473
/u/sovbld/cm131s/cm131s-20031114/src/jvm/pfm/xe/common/xe_thread_md.c threadSta
/u/sovbld/cm131s/cm131s-20031114/src/hpi/pfm/threads_utils.c ThreadUtils_Shell 952
@@GETFN
CEEOPCMM CEEOPCMM

For more information on JAVADUMP, see IBM Developer Kit and Runtime
Environment, Java 2 Technology Edition, Version 1.3.1 Diagnostic Guide.

The following example is the keyword string used to perform a database search for
the abend in ″Finding abend information with a monitor signal handler dump″ on
page50.

Chapter 5. Classifying, Documenting, and Reporting Problems 57

 compid ABEND0C1 cs390_UDPTable
DUMP
compid Specifies the Tivoli Monitoring for Network Performance
component ID number.
ABEND Specifies the type of problem.
0C1 Specifies the abend code.
cs390_UDPTable
Specifies the module containing the ABEND.

If the abend is from a failure, the keyword is ABENDxxx, where xxx is the abend
code in hexadecimal, for example, ABEND0C4, ABEND604, or ABEND13E. Typical
user abends are documented by ABENDUxxxx, where xxxx, is the abend code in
decimal. If you have no information on how to recover from or prevent the abend,
continue gathering documentation.

Out of Memory Errors in Java Processes

Memory problems can occur in the Java process through the following
mechanisms:
v A native (C/C++) memory leak that causes increased usage of the LE HEAP,
which can be viewed as excessive usage of Subpool 2, Key 8 or storage, and an
excessive Working Set Size of the process address space.
v A Java object leak in the Java-managed heap. The leak is caused by
programming errors in the application or the middleware. These object leaks
cause an increase in the amount of live data that remains after a garbage
collection cycle has been completed.

You might see an Out of Memory error for the Tivoli Monitoring for Network
Performance monitor when you first try to run it if your region size or
MAXASSIZE is not large enough. See IBM Tivoli Monitoring for Network Performance
Planning, Installation, and Configuration Guide for recommendations on the region
size and MAXASSIZE for the monitor.

When an Out of Memory problem occurs with Tivoli Monitoring for Network
Performance, collect any dumps that you received when the error occurred. If you
did not receive an SVC dump when the Out of Memory condition occurred, wait
for another occurrence of the problem to collect your problem documentation. You
will need to monitor the Tivoli Monitoring for Network Performance monitor
component for storage growth. Perform an SVC console dump of the monitor
address spaces and forward them to IBM customer support for further analysis.

See IBM Developer Kit and Runtime Environment, Java 2 Technology Edition, Version
1.3.1 Diagnostic Guide for information on setting environment variables for Java
dumps and debugging Out of Memory errors.

Categories See this information

Using IPCS z/OS MVS IPCS Commands

Documenting DOC Problems

If you encountered a problem with Tivoli Monitoring for Network Performance
Web application documentation, collect the information indicated in the following
list before calling IBM customer support:

h Any Problem Checklist information

58 IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting

 All applicable information in the list under “Documenting any Problem” on page
47.

h The order number and revision level of the manual or the Tivoli Monitoring
for Network Performance Web application page

Identify the order number and revision level of the manual. The manual numbers
are displayed on the back cover in the form xxxx-xxxx-y, where xxxx-xxxx is the
order number and y is a 1- or 2-digit revision number.

Identify the Tivoli Monitoring for Network Performance Web application page on
which you encountered a problem. Include the sequence of pages you used to get
to the failing page. If possible, provide a screen capture.

h The location of the error in the manual or the Tivoli Monitoring for Network
Performance Web application page

Locate the pages in the document or the pages that contain incorrect or incomplete
information, and write a description of the problem.

Report a documentation problem to IBM customer support only if the problem

affects the operation of the Tivoli Monitoring for Network Performance Web
application, or if the problem involves online help.

Documenting INCORROUT Problems

If your system is encountering incorrect output problems, gather the information
indicated in the following list before calling IBM customer support:

h “Any Problem Checklist” information

All applicable information in the list under “Documenting any Problem” on page
47.

h The specific output that is incorrect

Record the output that is incorrect.

h The expected output

Record how the output differs from what was expected. Answer the following
questions:
v Is all or part of the output missing?
v Is the output duplicated?
v Is there more output than expected?
v Is the information inaccurate?

If you are having problems with data not displaying on the Tivoli Monitoring for
Network Performance user interface see Chapter 7, “Resolving Problems,” on page
77 and sections, ″None of the Selected Portfolio Items Display Data″ and ″Some of the
Selected Portfolio Items Display Data.″

h Monitor Message and Trace Logs

Examine the Tivoli Monitoring for Network Performance monitor message and
trace logs. Messages or trace entries can indicate a problem that you can resolve.

Chapter 5. Classifying, Documenting, and Reporting Problems 59

 The trace logs can also indicate an exception. Not all exceptions are problems.
However, if the exception contains an SQL exception or SQL error, find the SQL
error code in the appropriate DB2 manual.

h WebSphere Application Server log and SystemOut and SystemErr logs

Examine the WebSphere Application Server logs to determine if there are messages,
errors, or exceptions. The WebSphere Application logs can indicate a problem with
a configuration parameter.

hDB2 Error Messages

Record any DB2 error messages that occurred at the time of the problem. If error
messages occurred, see the DB2 for z/OS and OS/390® Messages and Codes for
information to collect for DB2 problems.

h Problems with Reports

Record any information received on Crystal Management Console for the problem
report.

After collecting all of the required documentation, report the problem to IBM
customer support.

Categories See this information

MVS DUMP command z/OS MVS System Commands
Reporting a problem to IBM customer “Documenting any Problem” on page 47
support

Documenting PERFM Problems

If your system is encountering performance problems, collect the information
indicated in the following list before calling IBM customer support:

h Any Problem Checklist information

All applicable information in the list under “Documenting any Problem” on page
47.

h Local conditions, modifications, and user code

Record any modifications to your system or your network. Performance problems

can be related to system and networking constraints.

h Description of the operation attempted, the results expected, and the results
received

Record the actual performance, the expected performance, and the source of
information for the expected performance. If a document is the source of expected
performance information, note the order number and page number of the
document or the Web site.

h The size and type of operating environment, and the number of devices being
monitored

60 IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting

 Record information describing your Tivoli Monitoring for Network Performance
operating environment and include the following:
v The number of monitors that you have configured
v How many TCP/IP stacks each monitor is monitoring
v The Configuration XML file, fnp_config.xml
v Your collection interval or intervals for the monitors
v The operating system on which your Tivoli Monitoring for Network
Performance WebSphere Application Server is running
v The number of resources on which the monitor can be collecting data

hResource Measurement Facility (RMF) Data

Collect screen captures of the RMF™ ARD windows. After collecting all of the
required documentation, report the problem to IBM customer support.

Categories See this information

Performance Tuning IBM Tivoli Monitoring for Network
Performance
RMF z/OS Resource Measurement Facility library
Reporting a problem to IBM customer “Documenting any Problem” on page 47
support

Diagnosing Problems
To begin diagnostic procedures for problems that might occur in the Tivoli
Monitoring for Network Performance program or any of its components, you must
first understand the methods that can help you define and solve a problem or
document and report the problem to IBM customer support.

Finding Solutions
If you have the IBM Information/Access program, you can search the RETAIN®
database, on the basis of a keyword string, to find similar problems and their
solutions.

Working with IBM Customer Support

If it is necessary to call IBM customer support, collect the appropriate information.
When you call IBM customer support, a dispatcher asks for customer identification
information, such as your account name, access code, and program license number.
You and the dispatcher determine the type of help that you need. The dispatcher
assigns a problem number and places your call in a queue for a representative of
IBM customer support.

The representative uses the information from the worksheet to form a keyword
string and search a database containing symptoms and resolutions for problems.
This database also contains information on problems currently under investigation.
The representative might ask you for additional information to produce other
keywords that can help locate and solve the problem.

If the representative finds a similar problem description in the database, a solution

is probably available. The keyword string can be varied to widen or narrow the
search for similar problems.

Chapter 5. Classifying, Documenting, and Reporting Problems 61

 If the search does not produce a solution, the representative verifies that you have
the necessary information to discuss the problem with a specialist. Your call is then
placed in a queue accessed by IBM customer support specialists.

The IBM customer support specialist helps you refine keyword strings and
conducts additional searches of the database.

In general, IBM customer support can solve most problems, but in cases when no
solution is found, the problem is sent to an IBM customer support specialist. If the
specialist cannot find a solution, and if the problem is a new one, the specialist can
enter an authorized program analysis report (APAR) into the RETAIN database. An
APAR is a request for a correction in the program.

A number is assigned to your APAR. If you are asked to send documentation

about your problem to IBM customer support, write the APAR number in the
upper right corner of each piece of documentation.

The APAR and other types of documentation enable the program specialist to
examine the problem in more detail and develop a solution. If this solution is a
coding change, it is put into a program temporary fix (PTF) and sent to you. All
information about the solution is entered into the RETAIN database. This
procedure keeps the database current with problem descriptions and solutions and
makes the information available for future searches.

If you want more information on building a keyword string, see “Building a

Keyword String” on page 62.

Using Keywords
Each problem type has an associated keyword. The keyword is used as a general
identifier and to search the RETAIN database. If you have access to the RETAIN
database, you can search it. Otherwise, you can provide IBM customer support
with the keyword and they do the search. In searching the RETAIN database, you
can determine whether:
v Your particular problem has already been reported
v There is a bypass for your problem
v Your problem has been solved
v A solution already exists for your problem

An accurate and precise search string produces usable results. A string search
contains the following:
v The keyword that represents your problem type
v The level of the Tivoli Monitoring for Network Performance product
v Additional symptoms of the problem

If you proceed through all five classifications and cannot match your problem to
any of those described, see “Documenting any Problem” on page 47.

Building a Keyword String

A keyword string is a set of descriptive words that you use to identify a problem. A
keyword is a word or abbreviation that describes one part of a program failure.
These keywords can be used to search for solutions in the RETAIN database. Use
keywords in a string to completely describe the problem. A search string can
contain any keyword that represents your problem type, information about the
level of Tivoli Monitoring for Network Performance you are using, and additional

62 IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting

symptoms of the problem. For example, if the failure is an abnormal end (abend)
of a task, the keyword that is used is ABEND. Other problems have the following
keywords:
v DOC
v INCORROUT
v MSG
v PERFM

The following table can be used to develop a keyword string:

Table 1. How to Develop a Keyword String
Description or Type of Keyword Example of a
Type of Keyword Value Use Keyword String
Component The component Find all reported 5698FNP00 monitor
Identification identification problems with the
number for the Tivoli Monitoring for
product. The Network
component ID Performance product
number for Tivoli or one of its
Monitoring for components.
Network
Performance is
5698FNP00.
Failure v ABEND Refine your search to ABENDxxx, where xxx
v DOC just that type of is the abend or
v INCORROUT failure for Tivoli completion code (for
v MSG Monitoring for example, 0C1)
v PERFM Network
Performance or one
of its components.
Symptom Details about the Refine your search cs390_UDPTable is the
failure. gradually Tivoli Monitoring for
is(combining the Network Performance
symptom keywords module that abended.
in various ways) so
that you receive all
problems
descriptions that
might match your
problem.
Dependency Program or device Helps reduce the DATA COLLECTION
dependent keywords number of problem
that define the descriptions you
environment in need to examine.
which the problem
occurred

For example, if there is an abend in the cs390_UDPTable module in the monitor

component of Tivoli Monitoring for Network Performance product, enter the
following keyword string:
5698FNP00 ABENDxxx MONITOR cs390_UPDTable DATA COLLECTION
5698FNP00
Component ID for the program
ABEND
Type of problem

Chapter 5. Classifying, Documenting, and Reporting Problems 63

 xxx Abend or completion code number
MONITOR
Component of Tivoli Monitoring for Network Performance
cs390_UDPTable
Module that abended
DATA COLLECTION
Component within the monitor component that abended

Filling Out and Submitting the Problem Management Report

To fill out the problem management report (PMR), refer to the following IBM
customer support Web site:

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

Click Electronic Support Services to submit a PMR to IBM customer support.

64 IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting

Chapter 6. Diagnostic Tools
This chapter contains information about diagnostic tools that are available to help
you solve problems with IBM Tivoli Monitoring for Network Performance.
Serviceability tools are available for the following components:
v Monitor component
v Web application
v IBM Tivoli Data Warehouse

Monitor Component
The monitor component of the Tivoli Monitoring for Network Performance
program generates message logs, trace logs, a configuration XML file, and
supervisor call (SVC) dumps. The message logs contain documented messages that
can be found in Chapter 3, “Messages,” on page 7 of this guide. Many of the
messages for the monitor component are seen on your z/OS system console. The
trace logs contain diagnostic information that can be used to diagnose problems.
The information in the trace logs is not documented.

Note: Any other references to monitor logs in this chapter refers to the message
logs, trace logs, and the configuration XML file.

Message Logs, Trace Logs, and Configuration XML File

The message logs, trace logs, and configuration file generated by the monitor
component contain information that can be useful in pinpointing problems. All
logs and configuration files are stored on the same system on which they are
created. Because the monitor component currently runs on UNIX System Services
under z/OS, these files are located in UNIX System Services. The location of these
files is determined by the Tivoli Common Directory.

Tivoli Common Directory

The Tivoli Common Directory is a central location on a system used by Tivoli
applications. It holds serviceability-related files, such as logs and serviceability
scripts. The default location of the Tivoli Common Directory for the Tivoli
Monitoring for Network Performance monitor component is the
/var/ibm/tivoli/common directory.

The location of the Tivoli Common Directory is specified in the log.properties

configuration file. This configuration file is located in the
/etc/ibm/tivoli/common/cfg directory. You can modify the log.properties
configuration file.

Note: If you change the location of the log files for Tivoli Monitoring for Network
Performance, you change the location of the log files for all Tivoli applications that
use the Tivoli Common Directory.

Types of Messages and Trace Logs

The types of message and trace log files are:
v monitor
v monitorc (includes launcher)
v monitorCLI

© Copyright IBM Corp. 2004 65

 These correspond to the processes that run under UNIX System Services when the
monitor component is running. The first two processes should always be present.
Table 2. Monitor Processes
Monitor Processes Description
$JAVA_HOME/bin/java Monitor daemon
Note: To determine if you are looking at the
correct process for the monitor daemon, look
for itmnp in the path name.
$INSTALL_DIR/bin/monitor_cs390 CS/390 portion of the monitor
$INSTALL_DIR/bin/launcher Watchdog daemon
$INSTALL_DIR/bin/itmnpMonitor.sh cli Command line interface

$INSTALL_DIR and $JAVA_HOME

Are specified in the itmnpMonitor.sh script.

The itmnp.properties file contains configuration parameters for the message and
trace logs. This file is located in the /etc/itmnp directory in UNIX System Services.
The following properties are used to define the number and size of the message
and trace logs. For more information about these parameters, see the
itmnp.properties file.

message.maxFileSize
message.Java.maxFileSize
message.CLI.maxFileSize
message.C.maxFileSize
message.maxFiles
message.Java.maxFiles
message.CLI.maxFiles
message.C.maxFiles

trace.maxFileSize
trace.Java.maxFileSize
trace.CLI.maxFileSize
trace.C.maxFileSize
trace.maxFiles
trace.Java.maxFiles
trace.CLI.maxFiles
trace.C.maxFiles

Monitor Logs and Serviceability Script Locations

The locations for the Tivoli Monitoring for Network Performance monitor logs and
serviceability scripts are as follows:

tivoli_common_dir/FNP/logs
tivoli_common_dir/FNP/scripts
tivoli_common_dir
Is the location of the Tivoli Common Directory.
FNP Is the product ID for the Tivoli Monitoring for Network Performance
product.
logs Is the directory that contains the message logs, trace logs, and
configuration XML file.
scripts Is the directory that contains any serviceability scripts.

66 IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting

Configuration XML File
The configuration XML file is a schema that tells the monitor component what data
should be collected. The configuration XML file that is generated is based on your
configuration for the Tivoli Monitoring for Network Performance Web application.

The configuration XML file, fnp_config.xml, is the latest configuration XML file
that the monitor has received from WebSphere Application Server. It is stored in
the same directory as the log files. The beginning of the configuration XML file is
as follows:
<?xml version="1.0"?>
<PollerConfigurationDocument>

Message and Trace Log Names

There are three sets of message and trace logs for the monitor component.

If you only define one message log, then your message log names are:

msg_fnp_monitor.log
msg_fnp_monitorc.log
msg_fnp_monitorCLI.log

If you define more than one message log (maxFiles greater than 1), the following
occurs when the message log reaches the size limit:

Let nameX.log designate any of the preceding message log names, for example,
msg_fnp_monitor.log. Starting with the oldest message log nameX.log, it moves that
log to nameX+1.log, except when the oldest message log is nameX< maxFiles>. log,
then it starts with nameX-1.

For example, with maxFiles=3, msg_fnp_monitor.log becomes

msg_fnp_monitor1.log, msg_fnp_monitor1.log becomes msg_fnp_monitor2.log, and
so on up to msg_fnp_monitor3.log. When the msg_fnp_monitor.log reaches the size
limit, then the msg_fnp_monitor3.log is deleted and all files are moved up by one
and a new empty msg_fnp_monitor.log is created.

If you only define one trace log, then your trace log names are:

trace_fnp_monitor.log
trace_fnp_monitorc.log
trace_fnp_monitorCLI.log

If you define more than one trace log (maxFiles greater than 1), the following
occurs when the trace log reaches the size limit:

Let nameX.log designate any of the preceding trace log names, for example,
trace_fnp_monitor.log. Starting with the oldest trace log nameX.log, it moves that
log to nameX+1.log, except when the oldest trace log is nameX< maxFiles>.log, then
it starts with nameX-1.

For example, with maxFiles=3, trace_fnp_monitor.log becomes trace_fnp_monitor1.

log, trace_fnp_monitor1.log becomes trace_fnp_monitor2.log, and so on up to
trace_fnp_monitor3.log. When the trace_fnp_monitor.log reaches the size limit, then
trace_fnp_monitor3.log is deleted and all files are moved up by one and a new
empty trace_fnp_monitor.log is created.

To set the maximum sizes for message and trace logs, use the itmnp.properties file.

Chapter 6. Diagnostic Tools 67

 Message Log Format
The format for an entry in the message log is similar to the following:
<Message Id="FNPT015I" Severity="INFO">
<Time Millis="1084224191659">2004-05-10 17:23:11.659-01:00</Time>
<Server Format="IP">NMPIPL12</Server>
<ProductId>FNP</ProductId>
<Component>Monitor CS390 - Base</Component>
<LogText><<![CDATA[FNPT015I|THE DATA COLLECTION SERVER IS INITIALIZED AND READY TO
COLLECT DATA}}></LogText>
<LogAttribs><Key>organization</Key><Value>IBM</Value></LogAttribs>
<TranslationInfo Type="XPG4" Catalog="FnpMonCMessages" MsgKey="115" SetId="1">
</TranslationInfo>
</Message>
Message
Indicates the message identifier and the severity of the message: INFO for
informational messages, WARNING for warning messages, and ERROR for
error messages.
Time Indicates the time the log was produced, represented as the number of
milliseconds since 12:00 a.m. January 1, 1970, and as the date specified in
Coordinated Universal Time (UTC).
Server Format
Specifies the name of the server on whose behalf the message was logged.
ProductId
Specifies the name of the product that logged the message. This is the
prefix FNP for Tivoli Monitoring for Network Performance.
Component
Specifies the name of the component within the product that logged the
message.
LogText
Specifies the actual message text.
LogAttribs
Specifies key-value pairs.
TranslationInfo
Specifies which translation file was used.

Trace Log Format

The format for an entry in the monitorc trace log file is similar to the following:
<Trace Level="MIN">
<Time Millis="1084224175321">2004-05-10 17:22:55.321-01:00</Time>
<Server Format="IP">nmpipl12</Server>
<ProductId>FNP</ProductId>
<Component>launcher daemon</Component>
<LogText><![CDATA[Launcher permissions: ruid: 0. euid: 0 ]]></LogText>
<LogAttribs><Key>organization</Key><Value>IBM</Value></LogAttribs>
<Source FileName="./launcher.c" Method="main" Line="1517"/>
<Thread>10500880</Thread>
<Process>16777307</Process>
</Trace>
Trace Is the container for all information about the trace entry and also indicates
the level of the trace: MIN for minimum, MID for medium, and MAX for
maximum.
Time Indicates the time the trace was produced, represented as the number of
milliseconds since 12:00 a.m. January 1, 1970, and as the date specified in
Coordinated Universal Time (UTC).

68 IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting

Server Format
Specifies the name of the server on whose behalf the message was logged.
ProductId
Specifies the name of the product that logged the message. This is the
prefix FNP for Tivoli Monitoring for Network Performance.
Component
Specifies the name of the component within the product that logged the
message.
LogText
Specifies the text of the trace entry.
LogAttribs
Specifies key-value pairs.
Source FileName
Specifies the name of the source file where the trace entry was logged.
Method
Specifies the function where the trace entry was logged.
Line Specifies the line number in the source file where the trace entry was
logged.
Thread
Specifies the thread identifier for the process that logged the trace entry.
Process
Specifies the process identifier that logged the trace entry.

The format for an entry in the monitor or CLI trace log file is similar to the
following example:
<Trace Level="MIN">
<Time Millis="1082308393845">2004-04-18 13:13:13.845-05:00</Time>
<Server Format="IP">nmpipl12.newyork.myco.com</Server>
<ProductId>FNP</ProductId>
<Component>Database Layer</Component>
<Product Instance>nmpipl12.newyork.myco.com</Product Instance>
<LogText><![CDATA[WorkerThread-7 for LowPriorityPool operating on CS390MsmtQueue
has a cache size of: 67 ]]></LogText>
<LogAttribs><Key>organization</Key><Value>IBM</Value></LogAttribs>
<Source FileName="com.tivoli.itmnp.monitor.database.DBUtility"/>
<Thread>WorkerThread-7 for LowPriorityPool</Thread>
<Principal>ROOT</Principal>
</Trace>
Trace Is the container for all information about the trace entry and also indicates
the level of the trace: MIN for minimum, MID for medium, and MAX for
maximum.
Time Indicates the time the trace was produced, represented as the number of
milliseconds since 12:00 a.m. January 1, 1970, and as the date specified in
Coordinated Universal Time (UTC).
Server Format
Specifies the name of the server on whose behalf the message was logged.
ProductId
Specifies the name of the product that logged the message. This is the
message prefix FNP for Tivoli Monitoring for Network Performance.

Chapter 6. Diagnostic Tools 69

 Component
Specifies the name of the component within the product that logged the
message.
ProductInstance
Host name of the system where the monitor resides.
LogText
Specifies the text of the trace entry.
LogAttribs
Specifies key-value pairs.
Source FileName
Specifies the name of the source file where the trace entry was logged.
Thread
Specifies the thread identifier for the process that logged the trace entry.
Principal
User ID that started the monitor.

Trace Levels
You can specify three levels of detail for tracing for IBM Tivoli Monitoring for
Network Performance. The more detailed information you trace, the faster the
trace logs wrap. Configure the trace levels in the itmnp.properties file or with the
monitor command line interface (CLI). In the itmnp.properties file, change the
monitor.trace.level value.

Note: If you change this value in the itmnp.properties file, you must stop and start
the monitor for the new trace level to take affect.

The valid levels for trace are as follows:

DEBUG_MIN
Indicates minimum debug tracing, which captures severe errors, internal
errors, and exception information.
DEBUG_MID
Indicates medium debug tracing, which captures component flows, state
changes, and storage allocation and deallocation.
DEBUG_MAX
Indicates maximum debug tracing, which captures module entry and exit
for all modules except commonly used functions such as service routines,
data (for example, the display of control blocks and data received from
other components), and trace points for debugging complex operations.

Using the Command Line Interface for Trace Settings

Use the command line interface (CLI) to see your current trace settings and to
specify more granularity in the tracing. To use the CLI, enter the following
command at the command prompt:
$INSTALL_DIR/bin/itmnpMonitor.sh cli

Where:

$INSTALL_DIR is specified in the itmnpMonitor.sh script.

The main menu of the command line interface is displayed:

70 IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting

 Main Menu
Current status: Running
Configuration last loaded: Tue Jan 15 14:38:37 EST 2004
Build level: Tue Jan 20 23:10:00 2004
1) Change trace logging levels
2) Suspend collection of all measurements
3) Resume collection of all measurements
4) Exit
Type your selection number: 1

If you enter 1, you see the following menu:

Main Menu
Current State:Running
Configuration last loaded:Thu Jan 15 14:38:37 EST 2004
Tue Jan 20 23:10:00 2004
1)Change trace logging levels
2)Suspend collection of all measurements
3)Resume collection of all measurements
4)Exit
Type your selection number:1

Change Trace Logger Levels Menu

1) All loggers
2) CS390 Data Layer DEBUG_MIN
3) CS390 Layer DEBUG_MIN
4) CS390 Socket Data Layer DEBUG_MIN
5) Command Line Interface DEBUG_MIN
6) Database Layer DEBUG_MIN
7) ICMP Layer DEBUG_MIN
8) JMX Layer DEBUG_MIN
9) Monitor Base Code DEBUG_MIN
10) Monitor CS390 - Base DEBUG_MIN
11) Monitor CS390 - CSM Storage DEBUG_MIN
12) Monitor CS390 - EE and HPR DEBUG_MIN
13) Monitor CS390 - FTP and TN3270 DEBUG_MIN
14) Monitor CS390 - Hash table DEBUG_MIN
15) Monitor CS390 - SNA Management DEBUG_MIN
16) Monitor CS390 - TCP Applications DEBUG_MIN
17) Monitor CS390 - TCP Connections DEBUG_MIN
18) Monitor CS390 - TCP Storage DEBUG_MIN
19) Monitor CS390 - UDP Endpoints DEBUG_MIN
20) Monitor Services Code DEBUG_MIN
21) Monitor utilities DEBUG_MIN
22) Monitor utilities - Socket DEBUG_MIN
23) SNMP Layer DEBUG_MIN
24) Return to previous menu

On this menu, you can select 1 to change the level for all trace components, or you
can select one of the other numbers to change the level for a specific trace
component.

Note: The DEBUG_MIN level is the default setting for all trace components. Leave
DEBUG_MIN as your default setting for all components. If you are having a
problem with a particular component, you might want to change the trace level for
that component to get more information about the problem you are seeing.
However, you should change these settings only when directed to do so by IBM
customer support.

Dump Types
When the monitor application abends, an SVC dump is created. When the abend
occurs, you can receive multiple dumps; that is, one or more of the following:

Chapter 6. Diagnostic Tools 71

 v The CEEDUMP is a file that is written to the hierarchical file system (HFS) for
the monitor, which is a dump of the run-time environment for the language
environment and is generated by the CEE3DMP callable service. All output from
CEE3DMP is written to the default ddname variable for CEEDUMP. For more
information, see z/OS Language Environment Debugging Guide.
v The JAVADUMP is a text file written to the HFS for the monitor and is produced
when the Java Virtual Machine (JVM) ends unexpectedly because of an
operating system signal or when a user enters a reserved key-combination (for
example, Ctrl-C on a UNIX system). The JAVADUMP attempts to summarize the
state of the JVM at the instant the signal occurred. The code that creates
JAVADUMP is part of the JVM. You can control it by using environment
variables and runtime switches. For more information, see the IBM Developer Kit
and Runtime Environment, Java 2 Technology Edition, Version 1.3.1 Diagnostics Guide.
v The Java Transaction dump is an unformatted SVC dump that occurs when a
fatal crash occurs in the JVM, or Java Native Interface (JNI) code that is running
in the Java process. A crash is more strictly defined on z/OS as a program check
that is handled by z/OS UNIX System Services as a fatal signal. For example,
SIGSEGV for PIC4, 10 or 11 or SIGILL for PIC1. For more information, see the
IBM Developer Kit and Runtime Environment, Java 2 Technology Edition, Version 1.3.1
Diagnostics Guide
v The monitor signal handler dump is an SVC dump that is issued when fatal
signals occur in the portions of the monitor code that are running in a z/OS
Language Environment enclave. You see the following sequence of messages
when a Monitor Signal Handler dump is being generated:
FNPM013E A DUMP IS BEING REQUESTED FOR name COMPONENT. COMPLETION
CODE = X’completion_code’ REASON CODE = X’reason_code’.
FNPM014E THE SVC DUMP FOR THE name COMPONENT HAS COMPLETED.
RETURN CODE = X’return_code’,REASON CODE = X’reason_code’.
The title of the monitor signal handler dump looks similar to this example:
DUMP00 TITLE=FNMPSDMP MONITOR
SVC DUMP FOR THE DATA COLLECTION COMPONENT.
COMPLETION CODE = X’0C1000’
DUMP TAKEN TIME=12.53.26 DATE=04/12/2004
The Java Transaction dump and monitor signal handler dumps are SVC dumps.
They can be viewed with the MVS Interactive Problem Control System (IPCS),
which is a tool provided with the MVS system to aid in analyzing dump data.
You can use IPCS to format and analyze dumps and traces produced by the
MVS system, other program products, and applications that run on the MVS
system. For more information, see the z/OS MVS Interactive Problem Control
System (IPCS) User’s Guide.

Web Application
The Web application generates messages and trace entries at installation time and
at run-time. The messages for the installation and run-time procedures are in
Chapter 3, “Messages,” on page 7. The trace entries contain diagnostic information
that can be used to diagnose your problems. The information in the trace entry is
not documented.

Installation Logs
The installation procedure for the Tivoli Monitoring for Network Performance Web
application generates messages and log files that help you troubleshoot installation
problems. The following messages and logs are generated:
v The itmnp.log file

72 IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting

 Contains a history of each install or uninstall attempt for the Tivoli Monitoring
for Network Performance Web application. Here is an example of the entry
written for a successful installation:
FNPI0123I: <<< ITMNP Information Log Entry >>>
start: ** Tue Mar 30 17:10:06 EST 2004 **
option: install
OS: OS/390
UI: WSADMIN
itmnp21.ear: 8566606 Mar 27 00:25
build level: 200403262357
itmnp.env ver: v2.1.0.0.56
app install: ** Tue Mar 30 17:10:21 EST 2004 **
exit reason: processing complete
end: ** Tue Mar 30 17:25:48 EST 2004 **
On z/OS, this file is located in the directory where the imtnp21zos.tar file was
untarred. On your AIX system, this file is located in the /tmp/itmnp.log file.
v The messages written to the UNIX System Services console (z/OS only)
These messages document what is being done during the installation process.
The error messages are also written to the UNIX System Services console. You
can pipe the output from the Tivoli Monitoring for Network Performance install
script, itmnp.sh, to a file.
v The itmnp_install. log file
The line by line output from the installation of the Web application (AIX system
only).
To locate this file, change to the bin directory of your installation path for the
Web application installation files on your AIX system. You can locate the exact
installation path by looking at the last occurrence of the install dir:statement in
the /tmp/itmnp.log file. See IBM Tivoli Monitoring for Network Performance
Planning, Installation, and Configuration Guide for more information on the
itmnp_install.log file.

There is also a trace flag that is an option in the Install Shield MultiPlatform and
z/OS installations. The trace flag is called INSTALL_TRACE on z/OS, and the
default setting is OFF. When the flag is set to ON, the installation entry, exit, and
API data that is specific to Tivoli Monitoring for Network Performance is traced.
On AIX systems, you select the Enable Trace check box during the ISMP
installation. The trace output is written to the wsadmin.traceout file. On z/OS, this
file is located in the directory where you untarred the itmnp21zos.tar file. On your
AIX system, this file is located in the bin directory of your installation path for the
Web application installation files.

Message and Trace Logs

The Tivoli Monitoring for Network Performance Web application uses the JRas
extensions to log messages and diagnostic trace entries. The JRas extensions are
based on the IBM JRas logging toolkit. The WebSphere Application Server uses
JRas also.

The message and trace entries generated by the Tivoli Monitoring for Network
Performance Web application contain information that can be useful in identifying
problems.

Not every message that is displayed on the Tivoli Monitoring for Network
Performance user interface is logged. Only messages that contain information
pertaining to the processing of the Web application or that indicate a problem are
logged. Messages that indicate a value that is not valid, for example, a character

Chapter 6. Diagnostic Tools 73

 being entered when a number should be entered, are not logged. These messages
are not considered important enough to be displayed on the WebSphere
Administrative Console Message status bar.

By default, no tracing is enabled for the Tivoli Monitoring for Network

Performance Web application. Tracing under WebSphere Application Server can
have serious performance implications. Information on tracing the Tivoli
Monitoring for Network Performance Web application is explained in detail in
“Web Application Trace Components.”

Message and Trace Log Locations

The location of the WebSphere Application Server message and trace logs is not
only configurable, but different depending on your operating system. The
following default locations are for messages and trace entries in the z/OS and AIX
operating systems:
v On z/OS systems, Tivoli Monitoring for Network Performance Web application
messages and trace entries are located in SYSPRINT for the servant region
address space. You also see some messages on the z/OS system console and in
SYSLOG.
v On AIX systems, the default WebSphere Application Server diagnostic trace log
file is ${SERVER_LOG_ROOT}/trace.log. The Tivoli Monitoring for Network
Performance trace entries are written to this file. The Tivoli Monitoring for
Network Performance messages are written to either the SystemOut.log or
SystemErr.log files under the WebSphere Application Server root directory.

Message and Trace Log Formats

The following example is a Tivoli Monitoring for Network Performance Web
application message from a z/OS operating system.
Trace: 2004/04/17 22:00:03.558 01 t=6D2B00 c=UNK key=P8 (13007002)
FunctionName: purgeDB
SourceId: com.tivoli.itmnp.ui.gui.admin.purge.PurgeUtilityThread
Category: AUDIT
Extended Message:FNPW803I The Tivoli Monitoring for Network Performance
purge utility has completed purging data from the Tivoli Monitoring for Network
Performance database.

The following example is a Tivoli Monitoring for Network Performance Web

application trace entry from a z/OS operating system.
Trace: 2004/04/18 15:02:46.684 01 t=6CEA18 c=142.A key=P8 (13007002)
FunctionName: handleOutput
SourceId: com.tivoli.itmnp.ui.gui.console.FnpSuperServlet
Category: ENTRY
ExtendedMessage: Entry
Trace: 2004/04/18 15:02:46.685 01 t=6CEA18 c=142.A key=P8 (13007002)
FunctionName: handleOutput
SourceId: com.tivoli.itmnp.ui.gui.console.FnpSuperServlet
Category: EXIT
ExtendedMessage: Exit

Web Application Trace Components

The trace component names for the Tivoli Monitoring for Network Performance
Web application are the following:

ItmnpWas
v Traces the code that stores and retrieves configuration information and
customization settings to and from the DB2 database.

74 IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting

v Traces the code that retrieves the performance monitoring data for display on
the Operator user interface.
v Traces the Purge Utility, which deletes aged out performance data.

ItmnpMainUI

Traces user interface servlets and utilities associated with the servlets.

ItmnpOperatorUI
v Traces the user interface code that displays the performance monitoring data
gathered by Tivoli Monitoring for Network Performance.
v Traces the User Preferences settings.
v Traces the Run Diagnostics functions.

ItmnpAdminUI
v Traces the user interface code that is used to create and manage monitor
configurations.
v Traces the user interface code used for Run-time Preferences settings.

ItmnpJMXConnector

Traces code used to communicate with other components, for example, the monitor
and the NetView TCP/IP services component.

You can select either all, event, entryExit, or debug when enabling the Tivoli
Monitoring for Network Performance Web application trace components.

You can turn on tracing for the Tivoli Monitoring for Network Performance Web
application through the WebSphere Administrative Console.

To enable tracing on the z/OS system:

1. From the WebSphere Administrative Console left-hand navigation tree, select
Troubleshooting > Logs and Trace.
2. Click the Runtime tab.
3. Click Modify. Select your trace settings.
You can select one of the following:
v All
v Event
v Debug
v entryExit
For example, you might select ItmnpAdminUI=all=enabled to trace everything
for this component.
4. After you specify the trace setting, click Apply. The trace settings are in effect.

To enable tracing on the AIX system:

From the WebSphere Administrative Console left-hand navigation tree, select

Troubleshooting > Logs and Trace > Diagnostic Trace Service. Specify your trace
settings as previously discussed.

See IBM Tivoli Monitoring for Network Performance Planning, Installation, and
Configuration Guide for recommendations of the number and size of trace files.

Chapter 6. Diagnostic Tools 75

 Audit Message
The Web application issues a message that can be used for audit purposes. This
message is issued whenever any user, with a network systems operator or
administrator role, signs on or signs off. In addition, this same audit message is
also issued whenever an network systems administrator performs a command
against a monitor or an action, which causes changes in the database content. The
message is written to the WebSphere log. When running WebSphere Application
Server on a z/OS system, the message is also written to the z/OS SYSLOG, and
can be automated. The message is FNPU082I.

IBM Tivoli Data Warehouse

Performance data stored in the DB2 database is summarized and aggregated into
the IBM Tivoli Data Warehouse where it can be used to generate performance
reports. You can use Crystal Enterprise, which is provided as part of Tivoli Data
Warehouse, to generate reports from this data.

For information on troubleshooting problems with Tivoli Data Warehouse, see

Tivoli Data Warehouse Messages.

Serviceability Tools
Serviceability tools include:
v Log XML Viewer.
v Monitor documentation collection script.
v WebSphere Application Server Collector Tool.

Log XML Viewer

A Log XML viewer is provided with Tivoli Monitoring for Network Performance
for formatting the log and configuration files. Distributed and z/OS versions of
this tool are provided. See Appendix A, “Log XML Viewer,” on page 87 for more
information on the Log XML Viewer.

Monitor Documentation Collection Script

The monitor_doc_coll.sh script is provided with Tivoli Monitoring for Network
Performance for collecting all the monitor diagnostic files and bundling them so
that they can be sent to IBM customer support when a problem is encountered.

WebSphere Application Server Collector Tool

The WebSphere Application Server collector tool gathers information about your
WebSphere Application Server installation and packages it in a Java archive (JAR)
file that you can send to IBM customer support to assist in determining and
analyzing your problem. The information in the JAR file includes logs, property
files, configuration files, operating system and Java data, and the presence and
level of each software prerequisite.

For more information on the collector tool, see the WebSphere Application Server
information centers.

76 IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting

Chapter 7. Resolving Problems
Use the following table to locate examples of the problems you might encounter
when using the IBM Tivoli Monitoring for Network Performance program. Follow
these steps to use the table:
1. Locate your problem using the first two columns.
2. Navigate to the indicated page for a description of the problem and the steps
for correcting the problem.
3. Follow the steps to correct your problem.

If you are unable to solve your problem by using the following examples, follow
the instructions in “Classifying Problems” on page 43 and “Documenting and
Reporting Problems” on page 47 before contacting IBM customer support. The
following table can help you find information about a particular problem category:
Table 3. Problem categories and symptoms
Category Symptom Page
ABEND Abend X'0D6' on monitor initialization 78
Abend X’EC3’, X’DC3’ in WebSphere Application Server 78
No data on None of the selected portfolio items display data. 78
the user
Some of the selected portfolio items display data. 79
interface
Data from previous collection periods is missing. 79
Graphs are missing titles and labels only on z/OS 80
systems.
Graphs do not generate on the z/OS system. 81
Graphs do not generate on the AIX system. 81
Security When you sign on to the user interface, you are not 82
provided the proper authority.
LTPA token expired 82
Database Message FNPU004E is received. 82
DB2 deadlock occurs while running an extract, transform 83
and load process.
Connectivity The connection between WebSphere Application Server 83
and the monitor is refused.
Reports Report draws, but no graph or chart is displayed. 83
Row Set Not Found error is received. 83
Tivoli Data The Warehouse Enablement Pack installation does not 84
Warehouse complete.
Error in TWH–CDW_Data. generic file. 84
Web Web Browser Error Message 84
Browser
Unexpected Web application User Interface Results 84
Exceptions Known exceptions 84

© Copyright IBM Corp. 2004 77

ABEND X'0D6' on Monitor Initialization
If you installed the monitor component on z/OS Version 1, Release 4 system and
the required z/OS Communication Server PTFs have not been applied to this
system, a X'0D6' abend might occur when the monitor is started.

Install the required z/OS Communications Server PTFs. These are documented in
the IBM Tivoli Monitoring for Network Performance: Planning, Installation, and
Configuration Guide.

ABENDX'DC3', X'EC3' in WebSphere Application Server

The X’DC3’ and X’EC3’ abend codes are often caused by a timeout with a Web
application. A reason code accompanies the abend code. Look up the reason code
in the WebSphere Application Server for z/OS Troubleshooting Guide.

If the Tivoli Monitoring for Network Performance Web application is not

responding and WebSphere Application Server times out, do these steps:
v Verify that the timeout values specified in the IBM Tivoli Monitoring for Network
Performance: Planning, Installation, and Configuration Guide are set.
v Review the WebSphere Application Server logs for errors related to Tivoli
Monitoring for Network Performance.

None of the Selected Portfolio Items Display Data

You might successfully configure one or more monitors with the Tivoli Monitoring
for Network Performance Web application, start the monitor, and still not see data
in any of the selected portfolio items.

The following items can help you determine why no data is being received:
v Message FNPT027E is received with errno=111
The monitor code is not APF authorized and must be authorized to
communicate with z/OS Communications Server.
v Verify that the itmnpPostMon.sh script ran successfully, and that the monitor is
running under the user specified in the script.
v Verify that OSNMPD is started and that the subagent is active. Also, verify that
OSNMPD is configured for SNMPv2.
v Verify that the community name specified in the SNMP section of the Run-time
Preferences of the Tivoli Monitoring for Network Performance Web application,
the community name specified on the SACONFIG statement in the TCP/IP
profile, and the community name specified in the OSNMPD configuration are all
the same.
v Verify that the required z/OS Communications Server PTFs have been applied
to your system. Refer to prerequisites appendix in the IBM Tivoli Monitoring for
Network Performance: Planning, Installation, and Configuration Guide for more
information about these PTFs.
v Verify that the NETMONITOR statement has been coded in the TCP/IP profile
with SMFS and TCPCONNS specified.
v Verify that the bindJDBC.sh script ran. Refer to the chapter about installing the
Web application on z/OS in the IBM Tivoli Monitoring for Network Performance:
Planning, Installation, and Configuration Guide for more information.

78 IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting

 v Verify that the user ID and password for the DB2 database are correct. If
encryption is specified in the itmnp.properties file, then the database must use
the same type of encryption.
v Verify that the schedule for your monitor is currently active. If not, change the
schedule and deploy the monitor.
v Verify that there are no errors in the itmnp.properties files. There are some
instances where the monitor starts, but a configuration is not received by the
monitor. You can verify if the correct configuration has been received by:
– Looking for message FNPM025I on your z/OS system console or in SYSLOG.
– Verifying the date of your fnp_config.xml file.
If the monitor has not successfully received your configuration, verify the
following:
– Ensure that the monitor_hostname and WAS_hostname properties have
correct values. If they do not match, no errors are seen in the monitor logs.
The monitor will show as active under Manage Monitor Configurations on
the user interface, but no data is seen.
– Ensure that the WAS_httpport property value matches the MONITOR_PORT
value specified in the itmnp.env. file. If they do not match, an error is seen in
one of the trace_fnp_monitor.log files. The monitor might start, and if so, the
Manager Monitor Configurations on the user interface will show it as active.
Most other errors in the itmnp.properties file will cause the monitor to abruptly
end. The Errors are displayed in the monitor logs.

Some of the Selected Portfolio Items Display Data

There can be cases where you do not see data for every selected portfolio item.
Here are some of those cases:
v No SNMP data is received, but TCP/IP data is received. For example, if you see
data when you select View TCP Stacks > Connection Throughput and Traffic,
but you do not see data when you select View Interface Data > Status.
– Verify that OSNMPD is started and that the subagent is active. Also verify
that OSNMPD is configured for SNMPv2.
– Verify that the community name specified in the SNMP section of the
Run-time Preferences in the Tivoli Monitoring for Network Performance Web
application, the community name specified on the SACONFIG statement in
the TCP/IP profile, and the community name specified in the OSNMPD
configuration are all the same.
v No Memory or HPR and EE data is received.
– Verify that the SNAMGMT network management interface is active. Issue the
following command to activate the interface:
MODIFY <vtamproc>,VTAMOPTS,SNAMGMT=YES
v No TCP data is received. Verify that the NETMONITOR statement in your
TCP/IP profile has SMFS and TCPCONNS coded in it.

Data from Previous Collection Periods is Missing

You might need to generate a graph or table that contains data from a previous
collection period to understand the source of a problem. Use the graph function in
Tivoli Monitoring for Network Performance.

Chapter 7. Resolving Problems 79

 A graph or table is not generated if data from previous collection periods is not
found in the database for the specified graph time range. You might receive one of
the following messages:
v If informational message FNPU053I is issued, the database does not contain
performance data for the specified time range for any of the selected resources
and performance metrics.
v If informational message FNPU059I is issued, the database does not contain
performance data for all of the selected performance metrics for the specified
time range.
v If informational message FNPU061I is issued, the database does not contain
performance data for all of the selected resources for the specified time range.

Verify that the specified graph time range is correct and that data was collected
within the specified time range for the resources and metrics you are attempting to
graph.

If you generate a graph or table, but data from previous collection periods is still
missing, do the following:
v Verify the specified graph time range is correct. The graph time range consists of
a start time and date and an end time and date. Selected metrics that were
collected during this time range are included in the graph.
v Verify that data was collected within the specified time range for the resources
and metrics you are attempting to graph.
v Contact your network systems programmer to verify that the missing data was
not purged. The network systems programmer can define database purge
preferences, for example, the number of days to retain data in the database, the
time of day the daily purge occurs, and whether the purge is dependent upon
completion of the extract, transform, and load (ETL) process.

For more information, see the ″Defining Database Purge Preferences″ section in the
Tivoli Monitoring for Network Performance Administrator Guide.

Graphs are Missing Titles and Labels Only on z/OS Systems

On the z/OS system, the graphics driver, which is part of the PJA Toolkit library, is
required to generate graphs on the Tivoli Monitoring for Network Performance
user interface. If you do not install the graphics driver properly, no graphs are
generated.

A reason why graphs might be missing titles and labels is that the required key
value pairs in the WebSphere Administrative Console are not specified correctly.

Do the following to verify that you have the required key value pairs:
1. From the WebSphere Administrative Console, click Servers > Application
Servers > <server name> >Process Definition > Servant > Java Virtual
Machine > Custom Properties.
Verify the following key value pairs:
v The java.awt.fonts keyword specifies the directory where FnpThonburi.ttf is
located.
v The directory permissions on the directory specified by the java.awt.fonts
keyword are 755.
v The file permissions on FnpThonburi.ttf are also 755.
v The java2d.font.usePlatformFont keyword is set to true.

80 IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting

 A common mistake is to not type correctly the java2d.font.usePlatformFont and
type it as java2d.font.userPlatformFont.

See IBM Tivoli Monitoring for Network Performance: Planning, Installation, and
Configuration Guide for instructions on installing the graphics driver.

Graphs Do Not Generate on the z/OS System

A reason why graphs might not generate on the z/OS system is that the required
parameters in the WebSphere Administrative Console are not specified correctly.

Do the following to verify that you have the required parameters:

1. From the WebSphere Administrative Console, click Servers > Application
Servers > <server name> >Process Definition > Servant > Java Virtual
Machine.
Verify the following parameters:
v The Generic JVM Arguments contain the string, Xbootclasspath/p:
<pja_home_directory>/lib/pja.jar file.
v The pja_home_directory parameter specifies a directory that contains the
pja.jar file.
v The directory permissions on the directory specified by the
pja_home_directory parameter is 755.
v The file permissions on pja.jar file are also 755.
2. From the WebSphere Administrative Console, click Servers > Application
Servers > <serve name> >Process Definition > Servant > Java Virtual
Machine > Custom Properties.
Verify the following parameters:
v The awt.toolkit keyword is set to com.eteks.awt.PJAToolkit.
v The java.awt.graphicsenv keyword is set to
com.eteks.java2d.PJAGraphicsEnvironment.
v The user.home keyword is set to the directory where the lib/pja.jar file is
located.

See IBM Tivoli Monitoring for Network Performance: Planning, Installation, and
Configuration Guide for instructions on installing the graphics driver.

Graphs Do Not Generate on the AIX System

A graph might not generate because the java.awt classes used by the WebSphere
Application Server cannot reference the X11 native libraries. These libraries are
necessary to generate a graph.

If you start your Web Application Server remotely without first setting the
DISPLAY environment variable you consistently see this failure. The default value
is DISPLAY=:0.0. For example, if you use telnet command to remotely access an
AIX server to start the Web Application Server, you must first issue a command
appropriate for the shell to set the DISPLAY environment. The command can be:

export DISPLAY=:0.0

setenv DISPLAY :0.0

DISPLAY=:0.0

Chapter 7. Resolving Problems 81

 An alternative method to setting the DISPLAY environment variable is to start the
WebSphere Application Server using the itmnp_was.sh script which sets the
DISPLAY environment variable to the default value.

When You Sign On to the User Interface, You are not Provided the
Proper Authority
If you sign on to the Tivoli Monitoring for Network Performance user interface
with administrator authority, but you are only give browse authority, see the IBM
Tivoli Monitoring for Network Performance: Planning, Installation, and Configuration
Guide for information about mapping users to roles.

If you sign on to the Tivoli Monitoring for Network Performance user interface
with administrator authority and select Full Access, but you are only give browse
authority, see the IBM Tivoli Monitoring for Network Performance: Planning,
Installation, and Configuration Guide about enabling cookies on your Web browser
and for setting up your database.

LTPA Token Expired

If you receive a message in the WebSphere Application trace logs indicating that
your LTPA token has expired, delete the cookies on your Web browser.

Message FNPU004E is Received

Message FNPU004E is issued on the Tivoli Monitoring for Network Performance
user interface stating that you cannot read or write to the database. There are
many reasons this can occur. The first step in debugging this problem is to check
the WebSphere Application Server logs for error messages and exceptions. The
errors recorded in the log might provide a clue as to which of the following items
is the problem:
v The DB2 program is not active.
v The ITMNP_DB_LOCATION_NAME specified in the itmnp.env file is incorrect.
v The DB2USER and DB2PASSWD specified in the itmnp.env file are incorrect
v The DB2SQLJPROPERTIES WebSphere Application Server variable was not
entered in all uppercase letters or the path that this variable specified is
incorrect.
v The error message: DB2 JDBC Driver was unable to load the DLL db2os390j2 is
received in the WebSphere Application Server SYSPRINT log on the z/OS
system. WebSphere Application Server does not have access to the DB2 data sets.
See the IBM Tivoli Monitoring for Network Performance: Planning, Installation, and
Configuration Guide for information on making DB2 libraries available to
WebSphere Application Server.
v The JDBC level is not correct. See the prerequisites appendix of the IBM Tivoli
Monitoring for Network Performance: Planning, Installation, and Configuration Guide
for information about supported JDBC levels.
v An exception occurred reading or writing from the database. Retrieve the SQL
error from the WebSphere Application Server log(s) or monitor logs and
determine the cause of the failure.
v An MCWrapper Managed connection exception is received.
– If the MCWrapper Managed connection exception is received, followed by
reason code 00F30034, issue this command again:
GRANT EXECUTE ON PLAN DSNJDBC TO PUBLIC

82 IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting

 See the IBM Tivoli Monitoring for Network Performance: Planning, Installation,
and Configuration Guide for information about running this command.
– If the MCWrapper exception is received without a reason code, then JMS is
not configured correctly. This should not cause any problems.

DB2 Deadlock Occurs While Running an Extract, Transform, and Load

Process
If you are running an extract, transform, and load (ETL) process when the Tivoli
Monitoring for Network Performance product is running the purge utility, or when
an ETL is running while other database maintenance is being done, the following
can occur:
v DB2 deadlock.
v Reports might not be generated or they might have incorrect data.

The ETL and purge utility are best scheduled to run:

v Far enough apart (different times) so they are not running at the same time.
v When only a few users are using the Tivoli Monitoring for Network
Performance user interface.
v When the Tivoli Monitoring for Network Performance monitors are not
collecting data.

The Connection between WebSphere Application Server and the

Monitor is Refused
If your connection is refused between WebSphere Application Server and the
monitor, do the following:
v Verify that the monitor host and the host or machine where the Tivoli
Monitoring for Network Performance Web application resides can communicate.
v Verify that the ports you specified in the itmnp.properties file for local_httpport
and WAS_httpport are different.
v Verify that the ports you specified in the itmnp.properties file for local_httpport
and WAS_httpport are available and not in use by another application or
reserved.

Report Draws but No Graph or Chart is Displayed

If your Tivoli Monitoring for Network Performance report draws on the Crystal
Enterprise Console, but no graph or chart is displayed, one or more of the
following might have occurred:
v The ETL for putting data into Tivoli Data Warehouse was not run.
v No source data was collected.
v The selection criteria were not met.

Row Set Not Found Error is Received

If you received the Row Set Not Found error when attempting to view a Tivoli
Monitoring for Network Performance report, there are some additional
configuration steps you must do.

Chapter 7. Resolving Problems 83

 You must configure the user ID and password on the Crystal Management Console
for each report you want to view. The configuration must be done for each
translated report.

Additionally, if you are running Tivoli Data Warehouse on the z/OS system, you
need to configure the database name and alias on the Crystal Management Console
for each report you want to view. The configuration must be done for each
translated report.

Warehouse Enablement Pack Installation Does Not Complete

If the Warehouse Enablement Pack installation does not complete, verify that there
is enough space on the volume, or volumes, that you specified for your DB2
database. A timeout does not occur. Free up space on the specified volume or
volumes and the installation will complete.

Error in the TWH-CDW_DATA.generic File

An error in the TWH-CDW_DATA.generic file can occur during the Warehouse
Enablement Pack installation when the Central Data Warehouse and the Data Mart
are located on a z/OS system. Define a temporary database table to resolve this
problem. Refer to the Tivoli Data Warehouse documentation for instructions on
defining the temporary database table.

Web Browser Error Message

If you receive this message while navigating User Preferences or Graph
Preferences on the Tivoli for Network Performance user interface, using Microsoft
Internet Explorer, Version 6.0:
v Error: ’document.FnpConsole.Preferences.Panel.autoRefreshCheckBox’is null
or not an object is received.
Select Tools > Internet Options > Advanced and clear the selection named
Display a notification about every script error.

Unexpected Web application User Interface Results

Click Refresh to resolve any of the following symptoms with the Tivoli Monitoring
for Network Performance Web application on Mozilla with an AIX system:
v The task bar shows tasks, but there are no windows open for those tasks.
v The task bar shows no tasks, but there are windows open.
v The processing bar is displayed for more than five minutes. The page is
displayed after you click Refresh if it truly exists.
v A blank page is seen for more than five minutes. The page is displayed after you
click Refresh if it truly exists.

Known Exceptions
The monitor component of Tivoli Monitoring for Network Performance provides
exceptions. You might see exceptions, similar to the following examples, in your
monitor trace logs. These exceptions do not indicate a problem. The LogText and
Exception portion of the trace entries are listed:
v Exceptions at DEBUG_MIN trace level
– LogText medPriSchedThr has been interrupted while waiting for work

84 IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting

 – Exception java.lang.InterruptedException: JVMLK007: operation
interrupted
v Exceptions at DEBUG_MID trace level
– LogText SQLException while testing Cloudscape table size.
MESSAGE: Table ’SNMP_EXPR_DATA’ does not exist.
SQL_STATE: 42X05
Error Code (a.k.a. ErrorCode): 20000
– Exception ERROR 42X05: Table ’SNMP_EXPR_DATA’ does not exist
You will also see this exception for tables ICMP_RTT_MSMT and
CS390_MSMT.
– LogText nmpipl12.newyork.myco.com:1009691741 - Data needed to evaluate
expression AVG_IP_RESP_TM is missing.Divide operator was unable to evaluate.
Argument is null
leftHandSide values: null
rightHandSide values: com.tivoli.itmnp.monitor.collection.expression.math.
Constant value: 1000
– Exception com.tivoli.itmnp.monitor.collection.expression.math.
OperatorNotInitializedException: Divide operator was unable to evaluate.
Argument is null.
leftHandSide values: null
rightHandSide values: com.tivoli.itmnp.monitor.collection.expression.math.
Constant value: 1000

Chapter 7. Resolving Problems 85

86 IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting
Appendix A. Log XML Viewer
This appendix describes how to install and use the Log XML viewer, Version 2.1.3.

Overview
Tivoli applications support a common XML format for logging messages and
traces, which is called LOG XML. The Log XML viewer processes logs that are in
the LOG XML format.

These are some of the ways the viewer can filter messages and traces:
v Time window
v Severity
v Thread ID
v Component

The viewer can correlate messages and traces produced by different products and
convert the logged messages into ASCII or HTML files for presentation. Visual cues
are associated with error and warning messages

The viewer is a Java program, which requires Java Virtual Machine (JVM) 1.2.2 or
later. Distributed and z/OS versions of the Log XML Viewer are provided with
Tivoli Monitoring for Network Performance. The distributed version comes with
an installation wizard to aid in your installation.

Packaging
The Log XML Viewer is provided on the Tivoli Monitoring for Network
Performance distribution media. The viewer can be found in the LogViewer folder.
Within the LogViewer folder are Distributed and zOS folders. The distributed
viewer is packaged in the Logxml_2.1.3.zip file. The zOS viewer is packaged in the
logviewer.390.tar file.

Installing the Log XML Viewer

You can run the Log XML Viewer on z/OS under UNIX Systems Services or on a
distributed system. If you want to run the viewer on z/OS, follow the instructions
under ″Installing on a z/OS System.″ If you want to run the viewer on a
distributed system, follow the instructions under ″Installing on a Distributed
System.″

The Log XML viewer is provided in the logviewer.390.tar file. It requires JVM,
version 1.2.2 or later.

Installing on a z/OS System

File Transfer Protocol (FTP) the logviewer.390.tar file to a directory in UNIX System
Services on z/OS. Then issue the following command:

tar -xvf logviewer.390.tar

© Copyright IBM Corp. 2004 87

 Add the location of the viewer installation and JAVA executable to your PATH
environment variable. Give the viewer.sh execute permissions with the command
in the directory where the viewer is installed:

chmod +x viewer.sh

Installing on a Distributed System

To run the interactive install use the command:

java -cp setup.jar run

To run the console install, use the command:

java -cp setup.jar run -console

To run the silent install, use the command:

java -cp setup.jar run -silent -P bean5.installLocation=<location>

The variable, <location> is replaced with a directory.

Add the location of the viewer installation and JAVA executable to your PATH
environment variable. For UNIX systems, give the viewer.sh execute permissions
with the command in the directory where the viewer is installed:

chmod +x viewer.sh

Uninstalling on a Distributed System

To remove the viewer, run the uninstall program. The uninstall program is
provided in the uninstall.jar file, which is located in the _uninst directory, a
subdirectory of the installation location. It requires a JVM version 1.2.2 or later. To
run the interactive uninstall program use the command:

java -cp uninstall.jar run

Using the Log XML Viewer

Run the viewer by using the provided wrapper script (recommended) or by calling
Java directly.

Using the Wrapper Script

To use the wrapper script, the viewer (shell) or viewer.bat file must be in your
PATH environment variable. The script determines the location and uses that
information to set the CLASSPATH and VIEWER_HOME environment variables.

If you are running on a UNIX environment, replace viewer with viewer.sh any
time that viewer is referenced.
viewer [(-q query_string) | (-f filename)]
[-s (text | html)]
[-h]
input.xml [input.xml*]
–q Specifies a query string. Either –q or –f can be specified, but not both. For
information, see “Query String Syntax” on page 90.

88 IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting

 –f Specifies a file that contains a query string. Either –q or –f can be specified,
but not both. For more information, see “Query String Syntax” on page 90.
–s Specifies the type of output, either text or HTML, which is the default
setting. The HTML output is in UTF-8 encoding. The text output is in the
default encoding of the console where the command was issued.
–h Prints the command usage statement.
input.xml
Specifies the name of a log XML input file. If several input files are
specified, the log and trace records are merged based on the time stamps.

Query String Terminology

Use the following query string terms to define the content and format of your
viewer output.
Table 4. Query string terminology
Term Definition
query string A string provided by the user, which defines
what is in the output, and the format of that
output.
log record A single coherent entry in the log file. The
log record contains several fields, for
example, time, server, logText. A log should
describe activities of the user, or the visible
behavior of the program .
trace record A single coherent entry in the trace file.
Similar to the log record. A trace record
describes the internal activity of the
application. Trace is of interest to a systems
programmer, however not generally of any
use to the end user.
column header This term is from database terminology.
Each log or trace record contains multiple
fields. The term column header is used to
refer to these items.
filter predicate An expression which the viewer uses to
determine if a particular record is present in
the output. Contrast this term with column
header, which describes a field within the
record.

Using JVM Directly

To use the Java virtual machine (JVM) directly, the CLASSPATH environment
variable must include the jlog.jar, viewer.jar, regex4j.jar, and xerces.jar files, and the
PATH environment variable must include the Java location.
java -DVIEWER_HOME=stylesheet_location
[-DTRACE=DEBUG_MIN]
[-DSHOWTITLE=TRUE]
-cp "viewer.jar:jlog.jar:xercesImpl.jar:xmlparserAPIs.jar:regex4j.jar"
com.tivoli.log.viewer.Cli
[(-q query_string) | (-f filename)]
[-s (text | html)]
[-h]
input.xml [input.xml*]

Appendix A. Log XML Viewer 89

 –DVIEWER_HOME
Is a system property that defines the location of the stylesheet (.css) files.
The stylesheet files are embedded in the HTML file.
–DTRACE
Is a system property that defines the level of tracing. Valid values are
DEBUG_MIN, which is the default value, DEBUG_MID, and
DEBUG_MAX.
–DSHOWTITLE
Is a system property that directs the HTML formatter to include or omit
the title. Valid values are TRUE (include the default setting) or FALSE
(omit). The title consists of a list of input file names, separated by commas.
–cp viewer.jar:jlog.jar:xercesImpl.jar:xmlparserAPIs.jar:regex4j.jar
Indicates to the JVM a list of JAR files that are required for the viewer,
separated by colons (UNIX) or semicolons (for DOS). If the required JAR
files are not in the current directory, you must specify the full path for each
JAR file, rather than just the file name. In this UNIX system example, the
required JAR files are in the current directory, so the full path is not
specified:
-cp
"viewer.jar:jlog.jar:xercesImpl.jar:xmlparserAPIs.jar:regex4j.jar"
com.tivoli.log.viewer.Cli
Indicates the Java class.
–q Specifies a query string. Either –q or –f can be specified, but not both.
–f Specifies a file that contains a query string. Either –q or –f can be specified,
but not both.
–s Specifies the type of output, either text or HTML, which is the default
setting. The HTML output is in UTF-8 encoding. The text output is in the
default encoding of the console where the command was issued.
–h Prints the command usage statement.
input.xml
Specifies the name of a log XML input file. If several input files are
specified, the log and trace records are merged based on the time stamps.

Query String Syntax

A query string defines the content and format of the viewer output. The syntax for
a query string is as follows:
select column [,column] where Filter_Predicate
select Is a reserved word.
column Specifies the elements (fields) of a log or trace record that are to be
displayed in the output. The column names are as follows; they are not
case sensitive:

Note: The time stamp is always displayed in the output for each record. It
is the only field that takes a numeric argument (long integer), all other
fields are strings.
all Selection of all columns.
default
The default columns are Time, Severity, Message Id, LogText, Server,
Product Id, Component, and Product Instance.

90 IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting

Element
Indicates the string, either Message or Trace.
Time A string, which displays the local time.
Millis A long integer, indicates the time in milliseconds.
Server A string, which displays the name or IP address.
ServerFormat
A string, for example, TCP/IP.
Client A string
ProductId
A unique three-letter string that identifies the product.
Component
A string
ProductInstance
A string
LogText
A string
SourceFile
A string that displays the name of the source file where the event was
generated.
SourceMethod
A string that displays the name of the method that generated the event.
SourceLine
A string that displays the line number where the event was generated.
CorrelationId
A string
Principal
A string
Process
A string
Thread
A string
Exception
A string
MessageId
A string
TraceLevel
A string
Severity
A string
LogAttribs
Space separated key value pairs.
where Is a reserved word
Filter Predicate
Is an expression, or the reserved word true, that is used by the viewer to

Appendix A. Log XML Viewer 91

 determine which records are to be presented in the output. For more
information, see “Filter Predicate.”

The default query string is as follows:

select default where true

Filter Predicate
A filter predicate can be an expression or the reserved word true.

Conditional Operators Used in Filter Predicate Expressions

The following conditional operators can be used in filter predicate expressions:
= Equal
> Greater than
< Less than
>= Greater than or equal to
<= Less than or equal to
<> Not equal to
MATCH
Is a powerful, pattern matching operator that you can use to select log or
trace records using regular expression syntax. This operator is
implemented using the regex4j regular expression engine from
alphaWorks® (http://www.alphaworks.ibm.com/tech/regex4j). If strings
containing special characters or spaces are used in the regular expression,
they must be enclosed in single quotation marks.

Boolean Operators
The Boolean operators OR and AND can be used to join two expressions. The
format is as follows, with parentheses required around each expression:
(expression) AND (expression)

True Keyword
The keyword true is a complete filter expression. When it is specified, filtering is
disabled, and every log and trace record is displayed in the output.

Examples
The following query displays in HTML format the default field list for all message
and trace records. The output is sent to the sample.html file.
viewer sample.xml > sample.html

The following query displays all fields with a correlation ID of 12. The output is
sent to stdout.
viewer -q"select all where CorrelationId = 12" -stext sample.xml

The following example displays all fields with a time stamp of less than
1007067881373. The time stamp column (Millis) is the only one that takes a
numeric argument instead of a string. Output is in text format, written to stdout.
viewer -q"select all where Millis < 1007067881373" -stext sample.xml

The following example displays only the server and product ID, where the Boolean
expression is met. Since Boolean operators are being used, parentheses are needed

92 IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting

 to indicate the order of operator evaluation. Input is being merged from the
sample1.xm, sample2.xml, and sample3.xml files.
java -DVIEWER_HOME="./" -DTRACE="DEBUG_MAX" com.tivoli.log.viewer.Cli -q"select
server,ProductId where (messageid MATCH ’FRWEP00[10-45]’) AND ((server = ’joe’) OR
(severity = ’ERROR’))" sample1.xml sample2.xml sample3.xml

The following example illustrates filtering on a log attribute. The output contains
log records that have a log attribute with the name FNG and the value 123.
viewer -q"select default where LogAttribs MATCH ’FNG=123’" sample.xml

Error Handling
The viewer verifies query strings and stops processing if a query string is not
valid. It also validates the column labels. The viewer validates each command line
argument and stops processing if an argument value that is not valid is specified.
If an input log XML file is corrupted, the viewer does not attempt to read input
from that file; however, any other input files are processed. The Log XML Viewer
does not check input files against the PDLog.dtd, because, if a file has an entry
that is not specified in PDLog.dtd, the entry is ignored. The opening and closing
<PDLog> tags are not required in the input file because the viewer inserts these
into the input files.

Troubleshooting

Boolean Operators Require Parentheses

The following example demonstrates the strictness of Boolean expressions:
viewer -q"select default where (server=’joe’) AND (element=’trace’) AND
(messageID=’FRWEP0001E’)"

It results in the following error:

2002.04.10 14:52:19.755 com.tivoli.log.viewer.QueryTree labels Tivoli IVR 1 log
viewer jrowlan2.dev.tivoli.com IP IVR0019E unexpected character after query: AND

The solution is to ensure that each Boolean expression has the form (expression)
AND (expression) by changing the example to the following:
viewer -q"select default where ((server=’joe’) AND (element=’trace’)) AND
(messageID=’FRWEP0001E’)"

Using Quotation Marks in the Query String

The following example attempts a query using the match operator, but the query
string is not delimited by double quotation marks:
viewer.sh -qselect default where logText match ^get *.xml

This results in the following error:

2002.03.29 14:21:47.014 com.tivoli.log.viewer.QueryTree labels Tivoli IVR 1 log
viewer jrowlan2.dev.tivoli.com IP IVR0017E missing column label

When a query is incomplete, the viewer issues an error to indicate which

component of the query string is missing. In this example, the viewer expects a
column label but the string ends. Without double quotation marks around the
query string, this shell provides each word of the query in a different argument,
resulting in a query argument that is not valid.

Adding double quotation marks around the query string as follows:

Appendix A. Log XML Viewer 93

 viewer.sh -q"select default where logText match ^get" *.xml

results in the following error:

2002.03.29 14:18:53.423 (null) main Tivoli IVR 1 log viewer jrowlan2.dev.tivoli.com
IP IVR0021E Invalid character ^ found in query string.

The query syntax allows values to be enclosed in single quotation marks. This
signals to the viewer that what is inside the single quotation marks is a value that
does not need parsing. In this case, single quotation marks must be used to
prevent the viewer from reporting an error, as follows:
viewer.sh -q"select default where logText match ’^get’" *.xml

Note: Single quotation marks are also needed around a term when the term
contains spaces.

File Names with Spaces

Occasionally, directory names and file names have spaces. The fact that the viewer
can accept space separated file names can cause problems.

For example, if you type the following command, the viewer interprets a b/c as
two files (a and b/c)
viewer a b/c

To specify a file named c in subdirectory a b, you must use double quotation

marks around a b/c as follows:
viewer "a b/c"

Enabling Log XML Viewer Tracing

To enable tracing for the viewer, use the Java trace system property . This needs to
be passed on the Java command line before the class name is given. To enable
tracing, edit the viewer script (viewer.bat or viewer.sh), or run the command
without the using the script. For example, if the CLASSPATH has xerces.jar,
regex4j.jar, viewer.jar, and jlog.jar, enter the following command:
java -Dtrace=DEBUG_MAX com.tivoli.log.viewer.Cli sample.xml

A file with the name logViewerTrace.log is created in the current directory. To view
this file with the viewer, first rename the file to prevent the viewer from going into
a loop.

94 IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting

Appendix B. The itmnp.properties File
The itmnp.properties file contains definitions for the properties used in Tivoli
Monitoring for Network Performance.

A message log (or trace log) is defined here as a set of files that contain message
(or trace) data. A message file (or trace file) is defined here as a single file that
contains message (or trace) data. You can control the amount of storage required
for the message and trace log files with the maxFiles and maxFileSize properties.
During problem diagnosis, IBM customer support might request that you set a
different logging level in order to increase the amount of trace data collected.

You must have sufficient storage for the maxFiles and maxFileSize values that you
specify. These files are created under the Tivoli Common Directory. The location of
Tivoli Common Directory is specified in the
/etc/ibm/tivoli/common/cfg/log.properties file. You should verify that the mount
point containing the Tivoli Common Directory has sufficient free space for the
trace and message logs.

The following table contains itmnp.properties file values for the trace settings of
the Tivoli Monitoring for Network Performance monitor component.
Table 5. The itmnp.properties file values for messages and trace logs
Property Explanation Default Value
monitor.trace.level The logging level for the DEBUG_MIN
trace logs. This controls Note: Change this value
how much trace data is only if directed by IBM
collected. Typically, you customer support.
should run with
DEBUG_MIN to collect the
minimum level of trace
data). The possible values
are:
v DEBUG_MIN
v DEBUG_MID
v DEBUG_MAX
trace.maxFiles The maximum number of trace.maxFiles=4
trace files that can exist at
one time. When the monitor
closes a full trace file, it
ensures that no more than
the maximum number
exists by deleting the oldest
trace file before creating a
new trace file. The default
value is 4 files. The value
must be a number greater
than zero.
Note: When maxFiles is
set to 1, the value for
maxFileSize is ignored. The
monitor will write message
and trace entries until the
disk partition is full.

© Copyright IBM Corp. 2004 95

 Table 5. The itmnp.properties file values for messages and trace logs (continued)
trace.Java.maxFiles, The maximum number of None
trace.CLI.maxFiles, trace files that can exist for
trace.C.maxFiles the indicated trace log
(Java, CLI or C) at one time.
The default value for the
individual trace log is the
value for trace.maxFiles (as
specified or its default
value). The value must be a
number greater than zero.
trace.maxFileSize The maximum size (in trace.maxFileSize=1024
kilobytes) each trace file can
contain before the monitor
closes the old trace log and
creates a new trace log. The
default value is 1024
kilobytes (1024000 bytes).
The value must be a
number greater than zero.
Note: The maximum size
(in kilobytes) each trace file
can contain for the
indicated trace log (Java,
CLI or C). The default
value for the individual
trace log is the value for
trace.maxFileSize (as
specified or its default
value). The value must be a
number greater than zero.
trace.Java.maxFileSize, The maximum size (in None
trace.CLI.maxFileSize, kilobytes) that each trace
trace.C.maxFileSize file can contain for the
indicated trace log (Java,
CLI or C). The default
value for the individual
trace log is the value for
trace.maxFileSize (as
specified or its default
value). The value must be a
number greater than zero.

96 IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting

Table 5. The itmnp.properties file values for messages and trace logs (continued)
message.maxFiles The maximum number of message.maxFiles=4
message files that can exist
at one time. When the
monitor closes a full
message file, it ensures that
no more than the maximum
number exists by deleting
the oldest message file
before creating a new
message file. The default
value is 4. The value must
be a number greater than
zero.
Note: When maxFiles is set
to 1, the value for
maxFileSize is ignored. The
monitor writes message and
trace entries until the disk
partition is full.
message.Java.maxFiles, The maximum number of None
message.CLI.maxFiles, message files that can exist
message.C.maxFiles for the indicated message
log (Java, CLI or C) at one
time. The default value for
the individual message log
is the value for
message.maxFiles (as
specified or its default
value). The value must be a
number greater than zero.
message.maxFileSize The maximum size (in message.maxFileSize=1024
kilobytes) each message file
can contain before the
monitor closes a full
message log and creates a
new message log. The
default value is 1024
kilobytes (1024000 bytes).
The value must be a
number greater than zero.
Note: The maximum size
(in kilobytes) each message
file can contain for the
indicated message log (Java,
CLI or C). The default
value for the individual
message log is the value for
message.maxFileSize (as
specified or its default
value). The value must be a
number greater than a zero.

Appendix B. The itmnp.properties File 97

 Table 5. The itmnp.properties file values for messages and trace logs (continued)
message.Java.maxFileSize, The maximum size (in None
message.CLI.maxFileSize, kilobytes) each message file
message.C.maxFileSize may contain for the
indicated message log (Java,
CLI or C). The default
value for the individual
message log is the value for
message.maxFileSize (as
specified or its default
value). The value must be a
number greater than a zero.

98 IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting

Notices
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in
other countries. Consult your local IBM representative for information on 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 may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
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 may 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 may make improvements
and/or changes in the product(s) and/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. 2004 99

 IBM may 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 may 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.

Programming Interfaces
This publication documents no intended Programming Interfaces that allow the
customer to write programs to obtain services of IBM Tivoli Monitoring for
Network Performance.

Trademarks
IBM, the IBM logo, AIX, DB2, IBMLink™, Tivoli, the Tivoli logo, Tivoli Enterprise
Console, TME®, WebSphere, and z/OS are trademarks or registered trademarks of
International Business Machines 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.

Microsoft® and Windows NT® are registered trademarks of Microsoft Corporation

in the United States, other countries, or both.

SET and the SET Logo are trademarks owned by SET Secure Electronic Transaction
LLC.

UNIX is a registered trademark of The Open Group in the United States and other
countries.

Other company, product, and service names may be trademarks or service marks
of others.

100 IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting
Index
Special characters COREDUMP 43
Crystal Enterprise Professional 39
error handling
command line argument
$INSTALL_DIR 70 Crystal Management Console 59, 83 PDLog.dtd 93
cs390_UDPTable 58 query strings 93
customer support exceptions
A see software support viii DEBUG_MID trace level 84
ABEND 43 DEBUG_MIN trace level 84
abend (abnormal end) exec functions 54
diagnostic procedure 49 D Extract, transform and load (ETL) 39
extract, transform, and load (ETL) 83
documenting procedure 49 data mart 39
reporting procedure 49 eye-catcher (control block id) 51
DB2 messages 39
abend 0D6 DB2 SVC dump 43
monitor initialization 78 DB2PASSWD 82
abend EC3, DC3 DB2SQLJPROPERTIES 82 F
WebSphere 78 DB2USER 82 filter predicate expressions 92
ABEND or CORE DUMP keyword 43 dbcache cache 46 conditional operators, used 92
abend problem classifications default logs on AIX system fnp_config.xml 67
system abend codes 44 SystemErr.log 3 fork() 54
user abend codes 44 SystemOut.log 3
accessibility viii trace.log 3
administrator authority
full access 82
describing a problem 62
diagnostic tools 39, 65
H
AIX Application Core Dumps HEAP storage mechanism 58
installation logs
keyword (COREDUMP) 44 hierarchical file system (HFS) 54
itmnp_install.log 72
AIX system log 48 hyperlink message help 3
itmnp.log 72
authorized program analysis report messages written to UNIX System
(APAR) 62 Services console 72
directory names, notation ix I
disability viii IBM Software Support specialist 62
B DISPLAY environment 81 IBM Tivoli Enterprise Console 3
books DOC 43 IBM Tivoli Monitoring for Network
see publications v, vii documentation Performance product 1
Boolean expressions keyword (DOC) 44 incorrect output
parentheses 93 documenting a problem diagnostic procedure 59
Boolean operators authorized program analysis report documenting procedure 59
quotation marks 92 (APAR) 47 keyword (INCORROUT) 45
require parentheses 92 build level 47 reporting procedure 59
component ID number 47 INCORROUT 43
documentation 58 Information/Access IBM licensed
C documenting procedure 60
FMID (function monitor ID) 47
program 61
Interactive Problem Control System
capacity planner 1 incorrect output 59 (IPCS) 49
CEEDUMP 48 out of memory 58 ITMNP_DB_LOCATION_NAME 82
classifying a problem performance 60 itmnp.env file 48
building a keyword string 62 program temporary fix (PTF) 47 itmnp.log file 48
describing a problem 62 Recommended Service Upgrade (RSU) itmnp.properties file 48
RETAIN database 62 level 47 trace settings
search string 62 release number 47 monitor 95
classifying problems 43 reporting procedure 59, 60
command line interface (CLI) 70 documenting an ABEND problem 49
Common Anchor Area (CAA) 51
Common Information Block (CIB) 51
documenting problems 47
dump data set 49
J
compid 58 Java Transaction Dump 43
Condition Information for Active Java virtual machine (JVM) 44
Routines 55 CLASSPATH 89
configuration XML file 67 E jlog.jar, viewer.jar, regex4j.jar,
Configuration XML file environment variables xerces.jar 89
fnp_config.xml 60 CLASSPATH 88 PATH 89
conventions VIEWER_HOME 88 using 89
typeface viii environment variables, notation ix java.awt classes 81
Coordinated Universal Time (UTC) 68 JAVADUMP 48

© Copyright IBM Corp. 2004 101

JDBC level 82 monitor process problem categories (continued)
JVM dump 49 message and trace logs 67 exceptions
JVM,version 1.2.2 87 monitor signal handler dump 49 known 77
monitor_doc_coll.sh script 48, 76 no data user interface
Mozilla 84 collection periods 77
K MSG 43 graphs 77
selected portfolio items 77
key value pairs
reports
directory permissions 80
file permissions 80 N no graph or chart 77
row set not found error 77
java.awt.fonts 80 NETMONITOR 79
security
java2d.font.usePlatformFont 80 NetView Integrated TCP/IP Services
LTPA token expired 77
keyboard viii Component 3
no proper authority 77
keyword 62 NetView management console
Tivoli Data Warehouse
INCORROUT (incorrect output) 45 (NMC) 62
TWH–CDW_Data. generic file 77
MSG (message) 45 network operator 1
Warehouse Enablement Pack
PERFM (performance) 46 network systems programmer 1
installation 77
keyword string 62 notation
Web browser
keywords 43 environment variables ix
error message 77
path names ix
unexpected results 77
typeface ix
property
L message.maxFiles 95
Language Environment Machine State message.maxFileSize
Block (ZMCH) 51 O Tivoli Common Directory 95
local_httpport 83 OC1 58 monitor.trace.level 95
location online publications trace.maxFiles 95
log file directory 67 accessing vii trace.maxFileSize 95
Log XML viewer 76 ordering publications vii publications v
installation 87 OSNMPD 79 accessing online vii
Java program 87 Out of Memory signal 43 ordering vii
wrapper script 87 purge utility 83
Log XML Viewer
installation 87 P
Log XML Viewer tracing
enabling 94
packaging Q
distribution media 87 query string
LogViewer folder 87
Java archive (JAR) file 76 terminology
Logxml_2.1.3.zip file 87
logviewer.390.tar file 87 column header 89
PATH 89 filter predicate 89
path names, notation ix log record 89
M PERFM 43 trace record 89
manual, problem with 58 performance data query string syntax 90
manuals IBM Tivoli Data Warehouse 76
see publications v, vii response time 1
MCWrapper 82
message and trace logs 39
system workload 1
traffic flow 1
R
related components 3
Web application performance problem
report generation
generated 73 diagnostic procedure 60
Crystal Enterprise 76
Message Index 3 documenting procedure 60
reporting a problem
message keyword (MSG) 45 keyword (PERFM)
Information/Access IBM licensed
message log processor utilization 46
program 61
format 68 reporting procedure 60
searching the database for a
message source PJA Toolkit library 80
solution 61
format 3 problem
software support database, searching
message.C.maxFiles 95 classifying
solutions 61
message.CLI.maxFiles 95 describing a problem 62
reporting problems 47
message.Java.maxFiles 95 documenting
reports 39
messages and logs documentation 58
Request Block (RB) 49
itmnp.log file 72 reporting 61
resolving problems
messages to UNIX System Services problem categories
ABEND 78
console 72 ABEND
connectivity
monitor component ABEND 0D6 77
no connection, WebSphere
configuration XML file 65 Abend EC3, DC3 77
Application Server and
message logs 65 connectivity
monitor 78
SVC dumps 65 connection refused 77
database
trace logs 65 database
corruption on AIX 78
monitor logs 66 DB2 deadlock 77
Message FNPU004E 77

102 IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting
resolving problems (continued)
database (continued)
T V
DB2 deadlock occurs while tables valid levels
running ETL 78 CS390_MSM 84 DEBUG__MAX 70
message FNPU004E 78 ICMP_RTT_MSMT 84 DEBUG_MID 70
historical data, none 78 TCB Summary 53 DEBUG_MIN 70
no data displayed on user TCP/IP stacks 60 values
interface 78 TCPCONNS 79 monitor.trace.level 70
reporting telnet command 81 variables, notation for ix
draws but no graph or chart is Tivoli Common Directory vfork() 54
displayed 78 log.properties configuration file 65 viewer.bat file 88
security, no authority monitor component 65
LTPA token expired 78 Tivoli Data Warehouse 1
Tivoli Data Warehouse Tivoli Monitoring for Network
Performance Web application 1
W
WEP installation does not WAS_httpport 83
respond 78 Tivoli NetView for z/OS 3
Web application
resource measurement facility (RMF) 60 Tivoli Software Information Center vii
JRas extensions
RETAIN database 62 tivoli_common_dir/FNP/logs 66
JRas logging toolkit 72
tivoli_common_dir/FNP/scripts 66
WebSphere Administrative Console 3
trace component names
WebSphere Application Server collector
ItmnpAdminUI 74
S ItmnpJMXConnector 74
tool 76
screen captures 48 WebSphere Application Server message
ItmnpMainUI 74
script locations and trace logs
ItmnpOperatorUI 74
monitor logs 66 AIX
ItmnpWas 74
serviceability scripts 66 configure 74
trace levels
search string 62 location 74
configure
searching the database for a solution 61 z/OS 74
itmnp.properties file 70
service level agreements (SLAs) 1 wrapper script 88
monitor CLI 70
Serviceability tools MAX for maximum 69
IBM Tivoli Data Warehouse 65 MID for medium 69
log XML viewer 76 MIN for minimum 69 X
Monitor component 65 trace log X11 native libraries 81
Monitor documentation collection format 68 XML format
script 76 monitorc trace log file 68 logging
Web application 65 trace log format messages 87
WebSphere Application Server message 74 traces 87
Collector Tool 76 trace entry 74 XML log viewer 39
SMFS 79 trace.C.maxFiles 95
SNAMGMT network management trace.CLI.maxFiles 95
interface 79
SNMP data 79
trace.Java.maxFiles 95
troubleshooting 39
Z
SNMPV2. 79 z/OS ABEND 43
file names
software support spaces 94
contacting viii viewer tracing 94
software support database, searching true keyword 92
solutions 61 typeface conventions viii
spawn() 54 types of dumps
spawnp() 54 CEEDUMP 71
SVC dumps 39 Java transaction 71
SVRB 49 JAVADUMP 71
symptom Monitor Signal Handler 71
DB2 44 types of message and trace log files
documentation problem CLI 65
keyword (DOC) 44 launcher 65
errors in message or trace logs monitor 65
keyword (INCORROUT) 45 monitorc 65
message
keyword (MSG) 45
performance problem 46
response time 46
U
WebSphere 44 U4039 SLIP dump 49
symptoms 77 unformatted dump 49
SYSLOG system log 3 user interface 3
SYSPRINT 3 users 39
SYSPRINT log 82

Index 103
104 IBM Tivoli Monitoring for Network Performance: Messages and Troubleshooting



Printed in USA

SC31-6366-00
Spine information:

IBM Tivoli Monitoring for Network Performance Version 2 Release 1 Messages and Troubleshooting