t l ibm tivoli monitoring for network...
TRANSCRIPT
-
Tivoli® IBM
Tivoli
Monitoring
for
Network
Performance
Messages
and
Troubleshooting
Version
2
Release
1
SC31-6366-00
���
-
Tivoli® IBM
Tivoli
Monitoring
for
Network
Performance
Messages
and
Troubleshooting
Version
2
Release
1
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
Who
Should
Read
This
Guide
.
.
.
.
.
.
.
. v
Product
Publications
.
.
.
.
.
.
.
.
.
.
.
. v
IBM
Tivoli
Monitoring
for
Network
Performance
library
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. v
Related
publications
.
.
.
.
.
.
.
.
.
. vi
IBM
Tivoli
Monitoring
for
Network
Performance
information
.
.
.
.
.
.
.
. vi
IBM
z/OS
Operating
Systems
publications
.
. vi
IBM
z/OS
Communications
Server
publications
.
.
.
.
.
.
.
.
.
.
.
. vi
IBM
WebSphere
Application
Server
publications
.
.
.
.
.
.
.
.
.
.
.
. vi
IBM
DB2
publications
.
.
.
.
.
.
.
.
. vi
Tivoli
Data
Warehouse
publications
.
.
.
. vii
NetView
Integrated
TCP/IP
Services
Component
publications
.
.
.
.
.
.
.
. vii
Terminology
.
.
.
.
.
.
.
.
.
.
.
. vii
Accessing
publications
online
.
.
.
.
.
.
. vii
Ordering
publications
.
.
.
.
.
.
.
.
.
. vii
Accessibility
.
.
.
.
.
.
.
.
.
.
.
.
.
. viii
Contacting
software
support
.
.
.
.
.
.
.
. viii
Conventions
used
in
this
guide
.
.
.
.
.
.
. viii
Typeface
conventions
.
.
.
.
.
.
.
.
.
. viii
Operating
System-Dependent
variables
and
paths
ix
Chapter
1.
Introduction
.
.
.
.
.
.
.
. 1
Chapter
2.
Message
Overview
.
.
.
.
. 3
Sources
of
Messages
.
.
.
.
.
.
.
.
.
.
.
. 3
Message
Format
.
.
.
.
.
.
.
.
.
.
.
.
. 3
Message
Help
.
.
.
.
.
.
.
.
.
.
.
.
.
. 4
Displaying
Message
Help
by
Clicking
a
Hyperlink
Message
Number
.
.
.
.
.
.
.
.
.
.
.
. 5
Accessing
the
Message
Index
.
.
.
.
.
.
.
. 5
Chapter
3.
Messages
.
.
.
.
.
.
.
.
. 7
Chapter
4.
Troubleshooting
Overview
39
Troubleshooting
Responsibilities
for
the
Network
Systems
Programmer
.
.
.
.
.
.
.
.
.
.
. 41
Troubleshooting
Responsibilities
for
the
Network
Operator
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 41
Troubleshooting
Responsibilities
for
the
Capacity
Planner
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 42
Chapter
5.
Classifying,
Documenting,
and
Reporting
Problems
.
.
.
.
.
.
. 43
Classifying
Problems
.
.
.
.
.
.
.
.
.
.
. 43
ABEND
or
COREDUMP
.
.
.
.
.
.
.
.
. 43
z/OS
Abends
.
.
.
.
.
.
.
.
.
.
.
. 43
AIX
Application
Core
Dumps
.
.
.
.
.
. 44
DOC
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 44
INCORROUT
.
.
.
.
.
.
.
.
.
.
.
.
. 45
MSG
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 45
PERFM
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 46
Documenting
and
Reporting
Problems
.
.
.
.
. 47
Documenting
any
Problem
.
.
.
.
.
.
.
. 47
Documenting
ABEND
Problems
.
.
.
.
.
. 49
Out
of
Memory
Errors
in
Java
Processes
.
.
. 58
Documenting
DOC
Problems
.
.
.
.
.
.
. 58
Documenting
INCORROUT
Problems
.
.
.
. 59
Documenting
PERFM
Problems
.
.
.
.
.
. 60
Diagnosing
Problems
.
.
.
.
.
.
.
.
.
.
. 61
Finding
Solutions
.
.
.
.
.
.
.
.
.
.
. 61
Working
with
IBM
Customer
Support
.
.
.
. 61
Using
Keywords
.
.
.
.
.
.
.
.
.
.
.
. 62
Building
a
Keyword
String
.
.
.
.
.
.
.
. 62
Filling
Out
and
Submitting
the
Problem
Management
Report
.
.
.
.
.
.
.
.
. 64
Chapter
6.
Diagnostic
Tools
.
.
.
.
.
. 65
Monitor
Component
.
.
.
.
.
.
.
.
.
.
. 65
Message
Logs,
Trace
Logs,
and
Configuration
XML
File
.
.
.
.
.
.
.
.
.
.
.
.
.
. 65
Tivoli
Common
Directory
.
.
.
.
.
.
.
. 65
Types
of
Messages
and
Trace
Logs
.
.
.
.
. 65
Monitor
Logs
and
Serviceability
Script
Locations
.
.
.
.
.
.
.
.
.
.
.
.
. 66
Configuration
XML
File
.
.
.
.
.
.
.
. 67
Message
and
Trace
Log
Names
.
.
.
.
.
. 67
Message
Log
Format
.
.
.
.
.
.
.
.
. 68
Trace
Log
Format
.
.
.
.
.
.
.
.
.
. 68
Trace
Levels
.
.
.
.
.
.
.
.
.
.
.
. 70
Using
the
Command
Line
Interface
for
Trace
Settings
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 70
Dump
Types
.
.
.
.
.
.
.
.
.
.
.
.
. 71
Web
Application
.
.
.
.
.
.
.
.
.
.
.
.
. 72
Installation
Logs
.
.
.
.
.
.
.
.
.
.
.
. 72
Message
and
Trace
Logs
.
.
.
.
.
.
.
.
. 73
Message
and
Trace
Log
Locations
.
.
.
.
.
. 74
Message
and
Trace
Log
Formats
.
.
.
.
.
. 74
Web
Application
Trace
Components
.
.
.
.
. 74
Audit
Message
.
.
.
.
.
.
.
.
.
.
.
. 76
IBM
Tivoli
Data
Warehouse
.
.
.
.
.
.
.
.
. 76
Serviceability
Tools
.
.
.
.
.
.
.
.
.
.
.
. 76
Log
XML
Viewer
.
.
.
.
.
.
.
.
.
.
. 76
Monitor
Documentation
Collection
Script
.
.
. 76
WebSphere
Application
Server
Collector
Tool
.
. 76
Chapter
7.
Resolving
Problems
.
.
.
. 77
ABEND
X'0D6'
on
Monitor
Initialization
.
.
.
.
. 78
ABENDX'DC3',
X'EC3'
in
WebSphere
Application
Server
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 78
None
of
the
Selected
Portfolio
Items
Display
Data
78
Some
of
the
Selected
Portfolio
Items
Display
Data
79
Data
from
Previous
Collection
Periods
is
Missing
.
. 79
Graphs
are
Missing
Titles
and
Labels
Only
on
z/OS
Systems
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 80
©
Copyright
IBM
Corp.
2004
iii
-
Graphs
Do
Not
Generate
on
the
z/OS
System
.
.
. 81
Graphs
Do
Not
Generate
on
the
AIX
System
.
.
. 81
When
You
Sign
On
to
the
User
Interface,
You
are
not
Provided
the
Proper
Authority
.
.
.
.
.
. 82
LTPA
Token
Expired
.
.
.
.
.
.
.
.
.
.
. 82
Message
FNPU004E
is
Received
.
.
.
.
.
.
. 82
DB2
Deadlock
Occurs
While
Running
an
Extract,
Transform,
and
Load
Process
.
.
.
.
.
.
.
. 83
The
Connection
between
WebSphere
Application
Server
and
the
Monitor
is
Refused
.
.
.
.
.
.
. 83
Report
Draws
but
No
Graph
or
Chart
is
Displayed
83
Row
Set
Not
Found
Error
is
Received
.
.
.
.
. 83
Warehouse
Enablement
Pack
Installation
Does
Not
Complete
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 84
Error
in
the
TWH-CDW_DATA.generic
File
.
.
.
. 84
Web
Browser
Error
Message
.
.
.
.
.
.
.
.
. 84
Unexpected
Web
application
User
Interface
Results
84
Known
Exceptions
.
.
.
.
.
.
.
.
.
.
.
. 84
Appendix
A.
Log
XML
Viewer
.
.
.
.
. 87
Overview
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 87
Packaging
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 87
Installing
the
Log
XML
Viewer
.
.
.
.
.
.
.
. 87
Installing
on
a
z/OS
System
.
.
.
.
.
.
.
. 87
Installing
on
a
Distributed
System
.
.
.
.
.
. 88
Uninstalling
on
a
Distributed
System
.
.
.
.
. 88
Using
the
Log
XML
Viewer
.
.
.
.
.
.
.
.
. 88
Using
the
Wrapper
Script
.
.
.
.
.
.
.
.
. 88
Query
String
Terminology
.
.
.
.
.
.
.
. 89
Using
JVM
Directly
.
.
.
.
.
.
.
.
.
.
. 89
Query
String
Syntax
.
.
.
.
.
.
.
.
.
. 90
Filter
Predicate
.
.
.
.
.
.
.
.
.
.
.
. 92
Conditional
Operators
Used
in
Filter
Predicate
Expressions
.
.
.
.
.
.
.
.
.
.
.
. 92
Boolean
Operators
.
.
.
.
.
.
.
.
.
. 92
True
Keyword
.
.
.
.
.
.
.
.
.
.
. 92
Examples
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 92
Error
Handling
.
.
.
.
.
.
.
.
.
.
.
.
. 93
Troubleshooting
.
.
.
.
.
.
.
.
.
.
.
.
. 93
Boolean
Operators
Require
Parentheses
.
.
.
. 93
Using
Quotation
Marks
in
the
Query
String
.
. 93
File
Names
with
Spaces
.
.
.
.
.
.
.
.
. 94
Enabling
Log
XML
Viewer
Tracing
.
.
.
.
. 94
Appendix
B.
The
itmnp.properties
File
95
Notices
.
.
.
.
.
.
.
.
.
.
.
.
.
. 99
Programming
Interfaces
.
.
.
.
.
.
.
.
.
. 100
Trademarks
.
.
.
.
.
.
.
.
.
.
.
.
.
. 100
Index
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 101
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
http://www.ibm.com/software/tivoli/products/monitor-net-performance/http://www.ibm.com/software/tivoli/products/monitor-net-performance/http://www.ibm.com/software/tivoli/products/monitor-net-performance/http://www.ibm.com/servers/eserver/zseries/zos/bkserv/http://www.ibm.com/servers/s390/os390/bkserv/http://www.ibm.com/software/webservers/appserv/library/http://www-306.ibm.com/software/data/db2/
-
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.ibm.com/software/data/db2/library/http://publib.boulder.ibm.com/tividd/td/TivoliDataWarehouse1.2.htmlhttp://publib.boulder.ibm.com/tividd/td/NetView7.1.4.htmlhttp://www.ibm.com/software/tivoli/library/http://www.ibm.com/software/tivoli/library/
-
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
http://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgihttp://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgihttp://www.ibm.com/software/tivoli/order-lit/http://www.ibm.com/software/support/http://techsupport.services.ibm.com/guides/handbook.html
-
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.logv
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
-
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.
Figure
1.
An
error
message
displayed
in
the
work
area.
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
DB2®
UNIVERSAL
DRIVER.
Explanation:
The
Tivoli
Monitoring
for
Network
Performance
monitor
cannot
find
a
DB2
type
4
driver
in
its
classpath.
Programmer
Response:
Verify
that
the
db2j.jar
file
is
in
the
lib
directory
of
the
Tivoli
Monitoring
for
Network
Performance
monitor
base
installation
directory.
FNPD002E
THE
MONITOR
CANNOT
LOAD
THE
DB2
APPLICATION
DRIVER.
Explanation:
The
Tivoli
Monitoring
for
Network
Performance
monitor
cannot
find
a
DB2
type
2
driver
in
its
classpath.
Programmer
Response:
Verify
that
the
db2j.jar
file
is
in
the
lib
directory
of
the
Tivoli
Monitoring
for
Network
Performance
monitor
base
installation
directory.
Verify
that
the
db2client
has
been
properly
set
up.
FNPD003E
AN
ERROR
OCCURRED
CONNECTING
TO
THE
CLOUDSCAPE
DATABASE.
Explanation:
The
Tivoli
Monitoring
for
Network
Performance
monitor
was
not
able
to
create
a
connection
to
the
Cloudscape™
database.
Programmer
Response:
Check
the
drive
where
the
Cloudscape
database
is
located
to
see
if
there
is
enough
disk
space.
The
Cloudscape
database
location
is
defined
in
the
itmnp.properties
file
by
the
DBCacheDirectory
property.
If
the
error
persists,
try
removing
dbcache
and
restarting
the
monitor.
Any
measurements
stored
in
the
dbcache
will
be
lost.
FNPD004I
THE
CLOUDSCAPE
DATABASE
IS
BEING
DISABLED
BECAUSE
A
CONNECTION
CANNOT
BE
ESTABLISHED.
Explanation:
The
Cloudscape
database
was
disabled
because
the
enable
Cloudscape
property
in
the
itmnp.properties
file
was
set
to
NO.
FNPD005E
AN
ERROR
OCCURRED
WHILE
INITIALIZING
THE
CLOUDSCAPE
DATABASE.
Explanation:
An
unknown
error
occurred
while
initializing
the
Cloudscape
database.
Programmer
Response:
Check
the
drive
where
the
Cloudscape
database
is
located
to
see
if
there
is
enough
disk
space.
The
Cloudscape
database
location
is
defined
in
the
itmnp.properties
file
by
the
DBCacheDirectory
property.
Verify
that
the
db2j.jar
file
is
in
the
lib
directory
of
the
Tivoli
Monitoring
for
Network
Performance
monitor
base
installation
directory.
If
the
error
persists,
try
removing
dbcache
and
restarting
the
monitor.
Any
measurements
stored
in
the
dbcache
will
be
lost.
FNPD006E
AN
ERROR
OCCURRED
WHILE
INITIALIZING
DATABASE
CONNECTIVITY.
THE
MONITOR
EXITS.
Explanation:
A
critical
error
occurred
while
the
Tivoli
Monitoring
for
Network
Performance
monitor
was
running
database
initialization
routines.
Operator
Response:
You
might
receive
other
messages
that
will
help
determine
what
caused
this
error.
DB2
might
have
been
stopped.
Verify
that
DB2
is
active,
and
if
it
has
been
stopped
and
started,
then
start
the
monitor
again.
Programmer
Response:
Examine
the
monitor
trace
logs
for
further
information.
FNPD007I
DATABASE
INFORMATION
FOR
THREAD:
threadName
DATABASE
PRODUCT
NAME:
DatabaseProductName
DATABASE
PRODUCT
VERSION:
DatabaseProductVersion.
Explanation:
This
message
is
issued
when
the
different
monitor
processes
connect
to
the
database.
The
product
name
and
version
of
the
database
to
which
the
Tivoli
Monitoring
for
Network
Performance
monitor
is
connecting,
and
the
thread
name
is
displayed.
©
Copyright
IBM
Corp.
2004
7
-
FNPD008E
THE
CONNECTION
TO
DB2
HAS
BEEN
INTERRUPTED.
THE
MONITOR
IS
ATTEMPTING
TO
RESTORE
THE
CONNECTION.
Explanation:
DB2
might
have
stopped
or
another
DB2
error
occurred.
A
network
resource
failure
might
have
occurred.
Operator
Response:
If
the
connection
is
restored,
message
FNPD009I
is
received,
and
no
action
is
necessary.
Ensure
that
the
DB2
database
is
running
and
is
accessible
from
the
host
where
the
Tivoli
Monitoring
for
NetWork
Performance
monitor
resides.
FNPD009I
THE
CONNECTION
TO
DB2
HAS
BEEN
RESTORED.
Explanation:
The
Tivoli
Monitoring
for
Network
Performance
monitor
has
established
a
new
connection
to
the
DB2
database.
FNPD010I
THE
CONNECTION
TO
THE
CLOUDSCAPE
DATABASE
HAS
BEEN
RESTORED.
Explanation:
The
Tivoli
Monitoring
for
Network
Performance
monitor
has
established
a
new
connection
to
the
Cloudscape
database.
FNPD011E
THE
MONITOR
DISCOVERED
DATABASE
CACHE
PROPERTIES
THAT
ARE
NOT
VALID.
DBCACHETIMEOUT:
DBCacheTimeout
DBCACHEROWLIMIT:
DBCacheRowLimit
DBCACHEDIRECTORY:
DBCacheDirectory
Explanation:
The
Tivoli
Monitoring
for
Network
Performance
monitor
read
database
cache
properties
from
the
itmnp.properties
file.
One
or
more
of
the
properties
is
not
valid.
Programmer
Response:
Ensure
that
the
database
cache
properties
in
the
itmnp.properties
file
meet
the
stated
requirements:
v
DBCacheDirectory
cannot
be
empty.
v
DBCacheTimeout
must
be
greater
than
0.
v
DBCacheRowLimit
must
be
greater
than
0.
FNPI0001E
The
object
object_name
is
not
defined.
Explanation:
An
object
in
WebSphere
Application
Server
returned
a
null
value
during
an
installation
or
uninstall
process.
Administrator
Response:
Contact
IBM
customer
support.
FNPI0002I
The
resource
named
resource_name
is
already
defined.
Explanation:
A
resource
with
the
same
name
as
the
resource
you
are
attempting
to
create
is
currently
configured
within
WebSphere
Application
Server.
The
IBM
Tivoli
Monitoring
for
Network
Performance
product
might
already
be
installed.
Administrator
Response:
Perform
the
uninstall
process,
then
the
installation.
The
resource
might
have
been
previously
created
manually.
If
that
situation
is
correct,
then
the
resource
must
be
removed
manually
using
WebSphere
administrative
console.
FNPI0003I
Creating
resource
resource_name.
Explanation:
The
IBM
Tivoli
Monitoring
for
Network
Performance
resource
is
being
configured
within
WebSphere
Application
Server.
FNPI0004I
Created
resource
resource_name.
Explanation:
The
resource
was
successfully
configured
within
WebSphere
Application
Server.
FNPI0005E
The
resource
resource_name
was
not
created.
Explanation:
An
error
was
detected
during
the
creation
of
the
resource.
Administrator
Response:
Contact
IBM
customer
support.
FNPI0006I
Removing
resource
resource_name.
Explanation:
The
Tivoli
Monitoring
for
Network
Performance
resource
is
being
removed
from
WebSphere
Application
Server.
FNPI0007I
Removed
resource
resource_name.
Explanation:
The
Tivoli
Monitoring
for
Network
Performance
resource
has
been
successfully
removed
from
WebSphere
Application
Server.
FNPI0008E
The
resource
resource_name
could
not
be
found.
Explanation:
The
resource,
that
was
to
be
removed
by
the
Tivoli
Monitoring
for
Network
Performance
uninstall
process,
could
not
be
found
in
WebSphere
Application
Server.
Administrator
Response:
This
resource
might
have
been
previously
removed
by
the
Tivoli
Monitoring
for
Network
Performance
uninstall
process
or
manually
through
the
WebSphere
Administrative
Console.
Contact
IBM
customer
support.
FNPD008E
•
FNPI0008E
8
IBM
Tivoli
Monitoring
for
Network
Performance:
Messages
and
Troubleshooting
-
FNPI0009I
Begin
the
configuration_name
configuration.
Explanation:
A
configuration
process
has
started
for
the
modification
of
resources
in
WebSphere
Application
Server.
FNPI0010I
Installing
the
itmnp21
application.
Explanation:
The
itmnp21
application
Enterprise
Archive
(EAR)
file
is
being
configured
and
deployed
within
WebSphere
Application
Server.
FNPI0011I
The
itmnp21
application
has
been
successfully
installed.
Explanation:
The
itmnp21
application
has
been
successfully
installed
in
WebSphere
Application
Server.
FNPI0012E
The
itmnp21
application
has
not
been
installed.
Explanation:
An
error
was
detected
during
the
Tivoli
Monitoring
for
Network
Performance
installation
while
attempting
to
deploy
the
itmnp21
application
Enterprise
Archive
(EAR)
file
within
WebSphere
Application
Server.
Administrator
Response:
Review
all
the
messages
generated
by
the
WebSphere
environment
after
message
FNPI0010I
is
displayed.
These
messages
are
from
WebSphere
administrative
wsadmin
program
processing
and
might
indicate
specific
reasons
for
the
installation
failure.
Some
common
reasons
for
an
unsuccessful
itmnp21
application
installation
are:
v
The
/tmp
filesystem
space
is
insufficient
to
expand
the
itmnp21.ear
file
components.
v
WebSphere
filesystem
space
is
insufficient
to
expand
the
itmnp21.ear
file
components.
v
The
user
ID
that
was
used
to
perform
the
installation
does
not
have
the
necessary
authority
to
access
WebSphere
directories.
v
WebSphere
Application
Server
name
specified
during
the
setup
for
the
installation
is
not
a
valid
server
name.
It
is
either
the
server
name
that
was
given
as
the
field
input
value
specified
during
the
installation
on
AIX
in
the
installation
wizard
panel
or
the
environment
variable
that
was
used
in
setting
up
the
itmnp.env
z/OS
file.
v
There
are
underlying
connection
problems
in
the
WebSphere
environment
that
inhibits
the
discovery
of
WebSphere
Application
Server,
which
is
the
targeted
application
server
name
for
the
itmnp21
binary
files.
v
The
save
action
took
too
long
to
finish
its
processing
and
caused
WebSphere
to
time
out.
v
The
itmnp21
application
is
already
installed.
If
the
problem
persists,
contact
IBM
customer
support.
FNPI0013I
Uninstalling
the
itmnp21
application.
Explanation:
The
itmnp21
application
EAR
file
is
being
uninstalled
from
WebSphere
Application
Server.
FNPI0014I
The
itmnp21
application
has
been
successfully
uninstalled.
Explanation:
The
itmnp21
application
was
uninstalled
and
removed
from
WebSphere
Application
Server.
FNPI0015I
The
itmnp21
application
was
not
found.
Explanation:
An
attempt
to
remove
the
itmnp21
application
from
WebSphere
Application
Server
failed
during
the
uninstall
process.
Administrator
Response:
The
itmnp21
application
might
have
already
been
removed
from
WebSphere
Application
Server.
If
not,
contact
IBM
customer
support.
FNPI0016I
Only
the
invocation
was
tested.
No
action
is
taken.
Explanation:
A
test
option
was
selected
for
the
itmnp.sh
script
option.
No
configuration
updates
were
made
in
WebSphere
Application
Server.
FNPI0017I
Saving
the
itmnp21
configuration.
Explanation:
The
itmnp21
application
configuration
information
is
being
saved
in
WebSphere
Application
Server.
FNPI0018I
The
itmnp21
application
configuration
that
was
saved
to
the
master
configuration
was
successful.
Explanation:
The
itmnp21
application
configuration
information
was
saved
in
WebSphere
Application
Server.
FNPI0019E
The
AdminConfig
save
action
caused
an
exception
return_code.
Explanation:
An
error
occurred
in
WebSphere
Application
Server
while
saving
the
itmnp21
application
into
the
master
configuration.
Administrator
Response:
The
possible
reasons
for
an
exception
error
are:
v
WebSphere
filesystem
space
is
insufficient
to
save
the
deployed
itmnp21.ear
file
components.
v
An
inconsistency
or
conflicts
exists
in
WebSphere
XML
resource
files
that
will
prohibit
the
saving
of
certain
modifications
made
during
the
installation
process.
FNPI0009I
•
FNPI0019E
Chapter
3.
Messages
9
-
v
The
modifications
were
made
manually
and
saved
through
the
WebSphere
Administrative
Console
while
the
Tivoli
Monitoring
for
Network
Performance
installation
processing
was
running.
v
The
save
action
took
too
long
to
finish
its
processing
and
caused
WebSphere
to
timeout.
Contact
IBM
customer
support.
FNPI0020I
Starting
itmnp21
configuration
processing.
Explanation:
The
Jacl
script
invocation
for
the
itmnp21
application
has
started.
FNPI0021I
paramflag:
parameter_flag
Explanation:
The
parameter
option
flag
was
passed
to
the
Jacl
script
from
the
shell
script.
FNPI0022I
param:
parameter_value
Explanation:
The
parameter
associated
with
the
parameter
flag
was
passed
to
the
Jacl
script
from
the
shell
script.
FNPI0023I
The
JMS
server
has
not
been
installed
or
configured
with
the
WebSphere
component.
No
configuration
will
be
performed
for
the
internal
JMS
server
queues.
Explanation:
The
WebSphere
component,
internal
Java™
Message
Service
(JMS)
server,
has
not
been
installed.
The
installation
continues.
Administrator
Response:
Install
the
WebSphere
internal
JMS
server
component.
FNPI0024W
The
HTTP
Transport
port_number
is
already
defined
with
a
non
Tivoli
Monitoring
for
Network
Performance
SSL
configuration
repertoire
ssl_repertoire.
The
installation
process
must
stop.
Explanation:
The
installation
cannot
continue
because
the
specified
port
value
is
already
defined
and
cannot
be
created
by
the
Secure
Sockets
Layer
(SSL)
configuration
process.
Administrator
Response:
Change
the
port
value
to
a
non
existing
Hypertext
Transfer
Protocol
(HTTP)
Transport
number.
FNPI0025E
The
completeObjectName
MBean
is
not
available
for
the
WebSphere
Application
Server
app_server
on
node
node_name.
Explanation:
The
Java
Management
Extensions
(JMX)
management
MBean
is
NULL
for
object
completeObjectName.
The
WebSphere
Application
Server
has
not
been
started
or
is
not
running
on
a
node
name.
Administrator
Response:
Check
the
options
for
the
WebSphere
Application
Server
and
node
number
that
were
previously
specified.
Verify
that
your
WebSphere
environment
does
not
have
MBean
discovery
problems.
It
could
result
in
a
failed
completeObjectName
query.
For
a
Network
Deployment
configuration,
verify
that
the
Deployment
Manager
can
reach
the
specified
WebSphere
Application
Server.
If
the
problem
persists,
contact
IBM
customer
support.
FNPI0026I
The
current
global
security
enabled
state
is
gs_state
and
the
WebSphere
security
related
configuration
settings
have
been
made.
The
global
security
enabled
state
has
not
been
altered.
Explanation:
The
global
security
state
was
not
changed
by
the
installation
process.
FNPI0027I
The
WebSphere
and
Tivoli
Monitoring
for
Network
Performance
security
settings
validity
check
is
being
done.
Explanation:
The
installation
process
begins
the
security
configuration
steps
checking
for
existing
HTTP
Transport
definitions,
Federal
Information
Processing
Standard
(FIPS)
state,
and
other
possible
conflicts
before
creating
security
objects
related
to
the
Tivoli
Monitoring
for
Network
Performance
Web
application.
FNPI0028W
The
FIPS
setting
is
currently
enabled.
The
FIPS
activation
is
not
compatible
with
the
SSL
configuration
that
is
enabled
for
the
itmnp21
application.
Disable
FIPS
in
the
WebSphere
administrative
console
after
the
installation
process
completes.
Explanation:
The
Federal
Information
Processing
Standard
(FIPS)
activation
caused
the
itmnp21
application
to
fail
in
its
ability
to
communicate
because
the
Secure
Sockets
Layer
(SSL)
data
encryption
method
used
by
the
Tivoli
Monitoring
for
Network
Performance
Web
application
is
not
FIPS-approved.
Administrator
Response:
Clear
the
FIPS
check
box
on
the
Global
Security
page
in
WebSphere
Administrative
Console.
Then
stop
and
start
WebSphere
Application
Server.
FNPI0029I
The
FIPS
object
is
not
available
to
query.
The
installation
process
is
unable
to
check
the
current
FIPS
state.
Explanation:
The
Federal
Information
Processing
Standard
(FIPS)
object
for
the
global
security
custom
FNPI0020I
•
FNPI0029I
10
IBM
Tivoli
Monitoring
for
Network
Performance:
Messages
and
Troubleshooting
-
properties
in
WebSphere
environment
has
returned
a
null
value
during
the
security
setting
validation
phase
of
the
Tivoli
Monitoring
for
Network
Performance
Web
application
installation
process.
Administrator
Response:
If
the
FIPS
setting
is
enabled
on
the
Global
Security
page
in
WebSphere
Administrative
Console,
clear
the
FIPS
check
box.
Then,
stop
and
start
WebSphere
Application
Server.
FNPI0100I
Tivoli
Monitoring
for
Network
Performance
processing
has
started.
Explanation:
The
invocation
of
the
shell
script,
which
starts
the
installation
or
uninstall
process,
has
begun.
FNPI0101E
The
operating
system
os_name
is
not
supported.
Explanation:
An
installation
of
the
Tivoli
Monitoring
for
Network
Performance
Web
application
has
been
attempted
on
an
unsupported
operating
system.
The
UNIX
shell
script
can
only
be
run
on
the
z/OS
UNIX
System
Services
(USS)
system.
FNPI0103I
Only
the
following
options
are
possible:
install,
uninstall,
and
test.
Explanation:
An
option
for
the
itmnp.sh
shell
script
was
specified
that
is
not
a
valid
option.
Select
one
of
the
appropriate
valid
arguments
for
the
itmnp.sh
command
and
try
again.
FNPI0106I
The
itmnp21
Web
application
uninstall
process
has
started.
Explanation:
The
uninstall
option
that
was
specified
for
the
itmnp.sh
shell
script
argument
has
started.
FNPI0107I
The
itmnp21
Web
application
test
has
started.
Explanation:
The
test
option
that
was
specified
for
the
itmnp.sh
shell
script
agrument
has
started.
The
following
tests
are
performed:
v
The
Simple
Object
Access
Protocol
(SOAP)
provider
connection
is
validated.
v
The
user
ID
and
password
settings
are
authenticated.
v
WebSphere
Application
Server
is
determined
to
have
started
and
is
open.
v
The
viability
of
the
client
scripting
process
and
environment
are
checked.
v
The
validation
of
Jacl
scripting
arguments
is
performed.
FNPI0108I
The
itmnp21
Web
application
configuration
and
installation
has
started.
Explanation:
The
configuration
and
installation
option
that
was
specified
for
the
itmnp.sh
shell
script
agrument
has
started.
FNPI0109E
The
WebSphere
Configuration
Error
return
code
is
return_code.
All
processing
has
stopped.
Explanation:
An
error
occurred
during
the
installation
or
uninstall
processing
of
the
Tivoli
Monitoring
for
Network
Performance
Web
application
within
the
WebSphere
environment.
The
return
code
is
from
the
WebSphere
client
scripting
the
wsadmin
process.
Any
configurations
or
changes
that
were
made
during
the
installation
or
uninstall
processes
have
not
been
saved
to
the
WebSphere
master
configuration
repository.
Administrator
Response:
The
possible
reasons
for
the
configuration
error
are:
v
WebSphere
Jacl
script
interpreter
detected
a
syntax
error
in
the
itmnp.jacl
file
and
stopped
all
processing.
v
The
previous
errors
that
were
discovered
during
the
installation
or
uninstall
process
that
generated
other
WebSphere
environment
or
Tivoli
Monitoring
for
Network
Performance
specific
messages.
It
is
possible
that
one
of
the
following
messages
might
have
been
previously
generated:
v
FNPI0001E
v
FNPI0002I
v
FNPI0005E
v
FNPI0008E
v
FNPI0012E
v
FNPI0019E
v
FNPI0025E
For
further
information,
consult
the
message
help
for
any
FNPI
message
type
that
you
might
have
previously
seen
before
the
message,
FNPI0109E.
Contact
IBM
customer
support.
FNPI0112I
The
installation
is
complete.
You
must
recycle
the
WebSphere
Application
Server
app_server
before
running
the
Tivoli
Monitoring
for
Network
Performance
Web
application.
Explanation:
The
installation
process
has
been
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
FNPI0100I
•
FNPI0112I
Chapter
3.
Messages
11
-
Server,
the
itmnp21
application
automatically
starts.
FNPI0113I
Checking
the
minimum
space
requirements
for
itmnp21
application
installation:
space_tmp
Kb
space
available
for
tmp_fs
tmp
filesystem
tmp_min
Kb
is
the
recommended
minimum
space_was
Kb
space
available
for
was_fs
WebSphere
filesystem
was_min
Kb
is
the
recommended
minimum.
Explanation:
A
query
is
made
for
the
temporary
and
WebSphere
filesystem
minimum
space
requirements
before
the
installation
process
starts.
FNPI0114I
The
itmnp.env
runtime
environment
file
has
been
created.
Edit
this
file
with
your
customized
settings
and
then
run
the
itmnp.sh
script
again.
Explanation:
Initially,
when
the
itmnp.sh
shell
script
is
run,
the
itmnp.env
file
is
created,
which
is
configured
with
default
values.
The
itmnp.env
file
must
be
customized
for
the
installation
and
configuration
options
before
you
attempt
to
run
the
itmnp.sh
install
process.
For
information
about
customization
of
the
environment
setting
in
the
itmnp.env
file,
see
the
IBM
Tivoli
Monitoring
for
Network
Performance:
Planning,
Installation,
and
Configuration
chapter
about
installing
the
Web
application
on
the
z/OS
operating
system.
Administrator
Response:
Edit
the
itmnp.env
file
and
run
the
itmnp.sh
command
again.
FNPI0117I
The
current
itmnp.env
file
is
not
the
latest
level.
The
itmnp.env
file
has
been
moved
to
the
temporary
file
env_saved_file_name.
Use
the
env_saved_file_name
file
as
a
reference
for
the
new
itmnp.env
file.
Explanation:
The
installation
or
uninstall
process
of
a
new
level
of
code
is
being
attempted
and
the
itmnp.sh
shell
script
has
detected
an
incompatible
level
for
the
itmnp.env
environment
file.
All
processing
has
stopped.
A
new
itmnp.env
file
has
been
created
with
the
current
default
values.
The
itmnp.env
file
that
was
previously
used
was
backed
up
and
saved
under
another
file
name
which
uses
a
time
stamp
for
uniqueness.
Administrator
Response:
Edit
the
itmnp.env
file
and
run
the
itmnp.sh
command
again.
FNPI0118W
The
minimum
space
for
file_system
filesystem
is
not
available
for
the
itmnp21
installation.
The
z/OS
primary
allocation
space
is
insufficient;
however,
there
might
be
enough
space
available
in
the
secondary
extents.
To
continue
the
installation,
click
Enter.
To
end
the
installation,
type
1
and
click
Enter.
Explanation:
The
file
system
that
is
associated
with
tmp_fs
or
the
file
system
that
is
associated
with
WebSphere
environment
does
not
meet
the
minimum
recommended
requirements
to
complete
the
installation
of
the
itmnp21
Web
application.
The
deployment
of
the
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
completes
and
most
space
in
WebSphere
environment
will
be
available
at
the
end
of
the
installation
process;
however,
approximately
30
MB
of
file
allocation
space
in
WebSphere
environment
will
still
be
permanently
used
until
the
the
itmnp21
Web