ibm tivoli monitoring for web infrastructure: websphere
TRANSCRIPT
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
Problem
Determination
Guide
Version
5.1.2
SC32-1425-00
���
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
Problem
Determination
Guide
Version
5.1.2
SC32-1425-00
���
Note
Before
using
this
information
and
the
product
it
supports,
read
the
information
in
“Notices”
on
page
109.
First
Edition
(November
2003)
This
edition
applies
to
the
5.1.2
version
of
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere®
Application
Server
and
to
all
subsequent
releases
and
modifications
until
otherwise
indicated
in
new
editions.
©
Copyright
International
Business
Machines
Corporation
2003.
All
rights
reserved.
Note
to
U.S.
Government
Users
Restricted
Rights
--
Use,
duplication
or
disclosure
restricted
by
GSA
ADP
Schedule
Contract
with
IBM
Corp.
Contents
About
this
guide
.
.
.
.
.
.
.
.
.
.
. v
Who
should
read
this
guide
.
.
.
.
.
.
.
.
. v
Publications
.
.
.
.
.
.
.
.
.
.
.
.
.
. v
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
library
.
.
.
.
. v
Prerequisite
publications
.
.
.
.
.
.
.
.
. vi
Related
publications
.
.
.
.
.
.
.
.
.
. vi
Accessing
publications
online
.
.
.
.
.
.
. vi
Ordering
publications
.
.
.
.
.
.
.
.
.
. vii
Accessibility
.
.
.
.
.
.
.
.
.
.
.
.
.
. vii
Contacting
software
support
.
.
.
.
.
.
.
. vii
Conventions
used
in
this
guide
.
.
.
.
.
.
. viii
Terminology
.
.
.
.
.
.
.
.
.
.
.
.
. viii
Typeface
conventions
.
.
.
.
.
.
.
.
.
. viii
Operating
system-dependent
variables
and
paths
ix
Tivoli
command
syntax
.
.
.
.
.
.
.
.
. ix
Chapter
1.
Introduction
to
problem
determination
.
.
.
.
.
.
.
.
.
.
.
. 1
Product
overview
.
.
.
.
.
.
.
.
.
.
.
.
. 1
Built-in
problem
determination
features
.
.
.
.
. 1
Problem
classification
.
.
.
.
.
.
.
.
.
.
. 2
Chapter
2.
Installation
problem
determination
.
.
.
.
.
.
.
.
.
.
.
. 3
Common
installation
problems
and
workarounds
.
. 3
Resolving
installer
problems
.
.
.
.
.
.
.
.
. 6
Testing
endpoint
connectivity
.
.
.
.
.
.
.
.
. 9
Cleaning
up
and
removing
endpoints
.
.
.
.
. 10
Chapter
3.
Problems
and
workarounds
15
General
problems
.
.
.
.
.
.
.
.
.
.
.
. 15
General
proxy
mode
z/OS
problem
determination
17
General
resource
model
problem
determination
.
. 19
Proxy
mode
z/OS-related
resource
model
problem
determination
.
.
.
.
.
.
.
.
.
.
.
.
. 26
Proxy
mode
z/OS
status
resource
model
problem
determination
.
.
.
.
.
.
.
.
.
.
.
. 27
Proxy
mode
z/OS
non-status
resource
model
problem
determination
.
.
.
.
.
.
.
.
. 28
Administration
server-related
resource
model
problems
.
.
.
.
.
.
.
.
.
.
.
.
.
. 29
NetView-related
resource
model
problems
.
.
. 30
Application
server-related
resource
model
problems
.
.
.
.
.
.
.
.
.
.
.
.
.
. 30
Proxy
mode
z/OS
Data
Collector-related
resource
model
problems
.
.
.
.
.
.
.
.
.
.
.
. 31
Endpoint-related
resource
model
problems
.
.
. 33
Tasks
problem
determination
.
.
.
.
.
.
.
. 34
Discover_WebSphere_Resources
task
problem
determination
.
.
.
.
.
.
.
.
.
.
.
. 37
Tivoli
Enterprise
Console
problem
determination
.
. 41
Tivoli
Enterprise
Data
Warehouse
problem
determination
.
.
.
.
.
.
.
.
.
.
.
.
. 42
Chapter
4.
Debugging
information
.
.
. 47
Gathering
trace
information
for
IBM
Software
Support
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 47
Object
trace
information
.
.
.
.
.
.
.
.
. 47
Gateway
and
endpoint
trace
information
.
.
. 48
Adapter
trace
information
.
.
.
.
.
.
.
. 48
Gathering
local
log
files
for
IBM
Software
Support
.
.
.
.
.
.
.
.
.
.
.
.
.
. 49
Gathering
proxy
mode
z/OS
log
files
for
IBM
Software
Support
.
.
.
.
.
.
.
.
.
.
. 49
Log
file
information
.
.
.
.
.
.
.
.
.
.
. 50
Installation
log
files
.
.
.
.
.
.
.
.
.
.
. 50
General
log
files
.
.
.
.
.
.
.
.
.
.
.
. 50
Task
log
files
.
.
.
.
.
.
.
.
.
.
.
.
. 51
Tivoli
Enterprise
Data
Warehouse
log
files
.
.
. 51
Resource
model
log
files
.
.
.
.
.
.
.
.
. 51
Log
files
for
proxy
mode
z/OS
systems
.
.
.
. 52
AutoTrace
information
.
.
.
.
.
.
.
.
.
.
. 53
Initializing
autotrace
.
.
.
.
.
.
.
.
.
. 53
Gathering
AutoTrace
information
.
.
.
.
.
. 53
Chapter
5.
Understanding
warning
and
error
messages
.
.
.
.
.
.
.
.
.
.
. 55
Message
format
.
.
.
.
.
.
.
.
.
.
.
.
. 55
IBM
Tivoli
Monitoring
for
Web
Infrastructure
installer
messages
.
.
.
.
.
.
.
.
.
.
.
. 56
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
Messages
.
.
.
. 72
Proxy
mode
z/OS-specific
messages
.
.
.
.
.
. 104
Informational
messages
.
.
.
.
.
.
.
.
. 104
Warning
messages
.
.
.
.
.
.
.
.
.
.
. 106
Non–fatal
error
messages
.
.
.
.
.
.
.
. 106
Fatal
error
messages
.
.
.
.
.
.
.
.
.
. 107
Notices
.
.
.
.
.
.
.
.
.
.
.
.
.
. 109
Trademarks
.
.
.
.
.
.
.
.
.
.
.
.
.
. 110
Index
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 111
iii
iv
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
About
this
guide
The
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
Problem
Determination
Guide
provides
information
about
troubleshooting
and
fixing
problems
that
might
occur
with
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server.
Who
should
read
this
guide
This
guide
is
for
system
administrators
who
monitor
and
manage
IBM
WebSphere
Application
Server
resources.
Readers
should
be
familiar
with
the
following
topics:
v
Viewing
and
working
with
trace
log
files
v
Tivoli
management
software
v
UNIX
operating
systems
v
Windows
operating
systems
v
z/OS
operating
systems
v
IBM
WebSphere
Application
Server
v
Tivoli
Enterprise
Data
Warehouse
(optional)
v
IBM
Tivoli
Enterprise
Console
(optional)
v
IBM
Tivoli
Business
Systems
Manager
(optional)
Publications
This
section
lists
publications
in
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
library
and
any
other
related
documents.
It
also
describes
how
to
access
Tivoli
publications
online,
how
to
order
Tivoli
publications,
and
how
to
submit
comments
on
Tivoli
publications.
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
library
The
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
library
contains
the
following
publications:
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure
Installation
and
Setup
Guide,
GC23-4719
Provides
information
about
installing
and
setting
up
IBM
Tivoli
Monitoring
for
Web
Infrastructure.
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
User’s
Guide,
SC23-4705
Provides
information
about
setting
up
and
using
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
to
manage
your
IBM
WebSphere
Application
Server
resources.
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure
Reference
Guide,
GC23-4720
Provides
detailed
programming
information
about
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
resource
models,
tasks,
and
commands.
v
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
Warehouse
Enablement
Pack
Implementation
Guide,
SC09-7783
Provides
information
about
installing
and
using
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Applicationn
Server
Warehouse
Enablement
Pack.
Prerequisite
publications
To
use
the
information
in
this
book
effectively,
you
must
have
some
prerequisite
knowledge
of
IBM
Tivoli
Monitoring,
which
you
can
get
from
the
following
books:
v
IBM
Tivoli
Monitoring
User’s
Guide,
SC23-4567
Provides
an
overview
of
IBM
Tivoli
Monitoring,
especially
of
resource
models.
It
also
describes
how
to
use
the
user
interface.
v
IBM
Tivoli
Monitoring
Resource
Model
Builder
User’s
Guide,
SC23-5678
Describes
using
the
IBM
Tivoli
Monitoring
Resource
Model
Builder
to
create
and
customize
resource
models.
Related
publications
The
following
documents
also
provide
useful
information:
v
Tivoli
Management
Framework
User’s
Guide
v
Tivoli
Enterprise
Installation
Guide
v
Tivoli
Management
Framework
Reference
Manual
v
Tivoli
Enterprise
Console
Event
Integration
Facility
User’s
Guide
v
Tivoli
Enterprise
Console
Reference
Manual
v
Tivoli
Enterprise
Console
Rule
Builder’s
Guide
v
Tivoli
NetView
for
z/OS
product
documentation
v
Tivoli
Business
Systems
Manager
product
documentation
v
TSO/E
REXX
Reference
v
Tivoli
Enterprise
Data
Warehouse
product
documentation
v
IBM
Tivoli
Monitoring
product
documentation
v
Road
Map
for
the
Typical
Installation
Option
of
IBM
Tivoli
Monitoring
Products,
GI11-0959-00
v
Road
Map
for
Enabling
Tivoli
Enterprise
Data
Warehouse
for
IBM
Tivoli
Monitoring
Products
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
http://publib.boulder.ibm.com/tividd/glossary/termsmst04.htm
Accessing
publications
online
The
documentation
CD
contains
the
publications
that
are
in
the
product
library.
The
format
of
the
publications
is
PDF,
HTML,
or
both.
Refer
to
the
readme
file
on
the
CD
for
instructions
on
how
to
access
the
documentation.
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/
vi
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
Scroll
down
and
click
the
Product
manuals
link.
In
the
Tivoli
Technical
Product
Documents
Alphabetical
Listing
window,
click
M
to
access
all
of
the
IBM
Tivoli
Monitoring
product
manuals.
Note:
Note:
If
you
documents
on
other
than
letter-sized
paper,
set
the
option
in
the
File
→
window
that
allows
Adobe
Reader
to
letter-sized
pages
on
your
local
paper.
The
IBM
Tivoli
Software
Support
Web
site
provides
the
latest
information
about
known
product
limitations
and
workarounds
for
your
product.
You
can
view
this
information
at
the
following
Web
site:
http://www-3.ibm.com/software/support
Ordering
publications
You
can
order
many
Tivoli
publications
online
at
the
following
Web
site:
http://www.elink.ibmlink.ibm.com/public/applications/publications/
cgibin/pbi.cgi
You
can
also
order
by
telephone
by
calling
one
of
these
numbers:
v
In
the
United
States:
800-879-2755
v
In
Canada:
800-426-4968
In
other
countries,
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
most
features
of
the
graphical
user
interface.
For
additional
information,
see
the
Accessibility
Appendix
in
the
user’s
guide
for
this
product.
Contacting
software
support
If
you
have
a
problem
with
any
Tivoli
product,
refer
to
the
following
IBM
Tivoli
Software
Support
Web
site:
http://www.ibm.com/software/sysmgmt/products/support/
If
you
want
to
contact
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
About
this
guide
vii
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,
and
operating
system-dependent
commands
and
paths.
Terminology
The
following
terms
are
used
throughout
this
document:
distributed
Refers
to
supported
operating
systems
that
use
the
Tivoli
Management
Framework
architecture.
local
Refers
to
an
endpoint
on
any
non-z/OS
platform,
such
as
Windows,
AIX,
or
Linux.
Local
endpoints
have
IBM
WebSphere
Application
Server
running
on
the
system,
while
z/OS
proxy
endpoints
do
not.
node
In
the
Tivoli
environment,
a
node
refers
to
any
managed
resource
with
Tivoli
Management
Framework
installed.
In
the
WebSphere
environment,
the
term
node
refers
to
the
IBM
WebSphere
deployment
managers,
node
agents,
and
application
servers.
In
this
document,
unless
specifically
indicated,
the
Tivoli
environment
definition
of
node
is
used.
UNIX
Refers
to
AIX,
HP-UX,
Linux,
and
Solaris
operating
systems.
Windows
Refers
to
Microsoft
Windows
NT
and
Windows
2000.
z/OS
Refers
to
z/OS
and
OS/390
operating
systems.
Typeface
conventions
This
guide
uses
the
following
typeface
conventions:
Bold
v
Lowercase
commands
and
mixed
case
commands
that
are
otherwise
difficult
to
distinguish
from
surrounding
text
v
Interface
controls
(check
boxes,
push
buttons,
radio
buttons,
spin
buttons,
fields,
folders,
icons,
list
boxes,
items
inside
list
boxes,
multicolumn
lists,
containers,
menu
choices,
menu
names,
tabs,
property
sheets),
labels
(such
as
Tip:,
and
Operating
system
considerations:)
v
Keywords
and
parameters
in
text
Italic
v
Words
defined
in
text
v
Emphasis
of
words
(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
viii
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
Operating
system-dependent
variables
and
paths
The
publications
in
this
library
use
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.
Tivoli
command
syntax
The
following
special
characters
define
Tivoli
command
syntax:
[
]
Identifies
elements
that
are
optional.
Required
elements
do
not
have
brackets
around
them.
...
Indicates
that
you
can
specify
multiple
values
for
the
previous
element.
Separate
multiple
values
by
a
space,
unless
otherwise
directed
by
command
information.
If
the
ellipsis
for
an
element
follows
a
closing
bracket,
use
the
syntax
within
the
brackets
to
specify
multiple
values.
For
example,
to
specify
two
administrators
for
the
option
[–a
admin]...,
use
–a
admin1
–a
admin2.
If
the
ellipsis
for
an
element
is
within
the
brackets,
use
the
syntax
of
the
last
element
to
specify
multiple
values.
For
example,
to
specify
two
hosts
for
the
option
[–h
host...],
use
–h
host1
host2.
|
Indicates
mutually
exclusive
information.
You
can
use
the
element
on
either
the
left
or
right
of
the
vertical
bar.
{
}
Delimits
a
set
of
mutually
exclusive
elements
when
a
command
requires
one
of
them.
Brackets
([
])
are
around
elements
that
are
optional.
In
addition
to
the
special
characters,
Tivoli
command
syntax
uses
the
typeface
conventions
described
in
“Typeface
conventions”
on
page
viii.
The
following
examples
illustrate
the
typeface
conventions
used
in
Tivoli
command
syntax:
v
wcrtpr
[–a
admin]...
[–s
region]
[–m
resource]...
name
The
name
argument
is
the
only
required
element
for
the
wcrtpr
command.
The
brackets
around
the
options
indicate
they
are
optional.
The
ellipsis
after
the
–a
admin
resource
option
means
that
you
can
specify
multiple
administrators
multiple
times.
The
ellipsis
after
the
–m
resource
option
means
that
you
can
specify
multiple
resources
multiple
times.v
wchkdb
[–o
outfile]
[–u]
[–x]
{–f
infile
|
–i
|
object...}
The
–f,
–i,
and
object
elements
are
mutually
exclusive.
Braces
that
surround
elements
indicate
that
you
are
including
a
required
element.
If
you
specify
the
object
argument,
you
can
specify
more
than
one
object.
About
this
guide
ix
x
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
Chapter
1.
Introduction
to
problem
determination
This
problem
determination
guide
explains
how
to
troubleshoot
the
IBM
WebSphere
Application
Server
component
of
IBM
Tivoli
Monitoring
for
Web
Infrastructure.
Troubleshooting,
or
problem
determination,
is
the
process
of
determining
why
a
certain
product
is
malfunctioning.
This
chapter
introduces
troubleshooting
as
a
high-level
concept
and
then
relates
it
back
to
the
product.
If
you
have
a
problem
that
you
are
unable
to
solve
using
the
information
in
this
guide,
contact
IBM
Software
Support
for
further
assistance.
Before
contacting
IBM
Software
Support
about
a
problem
you
are
experiencing
with
this
product,
gather
the
following
information
that
relates
to
the
problem:
v
Log
files
v
IBM
WebSphere
Application
Server
version
v
Tivoli
management
region
server
version
v
Operating
system
v
Adapter
files
v
Framework
information
v
Messages
Product
overview
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
enables
systems
administrators
to
configure,
monitor,
and
manage
IBM
WebSphere
Application
Server
resources
across
distributed
and
z/OS
systems
from
a
central
console.
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
incorporates
best
practices
in
monitoring
Web
server
resources,
providing
root
cause
analysis
of
problems
and
corrective
action
for
quick
problem
resolution.
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
also
provides
the
capability
to
use
Tivoli
Enterprise
Console
and
Tivoli
Business
Systems
Manager
to
monitor
events
from
your
resources.
Built-in
problem
determination
features
The
primary
troubleshooting
feature
in
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
is
logging.
Logging
refers
to
the
text
messages
and
trace
data
generated
by
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server.
Messages
and
data
are
sent
to
an
output
destination,
such
as
a
console
screen
or
a
file.
Typically,
text
messages
relay
information
about
a
system
or
application’s
state
and
performance.
Messages
also
alert
the
system
administrator
to
exceptional
conditions
when
they
occur.
Trace
data
captures
transient
information
about
the
current
operating
environment
when
a
component
or
application
fails
to
operate
as
designed.
IBM
Software
Support
personnel
use
the
captured
trace
information
to
determine
the
source
of
an
error
or
unexpected
condition.
See
Chapter
4,
“Debugging
information,”
on
page
47
for
more
information.
1
Problem
classification
The
following
types
of
problems
might
occur
with
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
v
Installation
and
configuration
v
General
usage
and
operation
v
Proxy-mode
z/OS
operation
v
Resource
model
v
Tasks
v
Tivoli
Enterprise
Console
v
Tivoli
Enterprise
Data
Warehouse
This
guide
provides
symptom
descriptions
and
detailed
workarounds
for
these
problems,
as
well
as
describing
the
logging
capabilities
of
the
product.
2
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
Chapter
2.
Installation
problem
determination
This
chapter
explains
how
to
troubleshoot
problems
that
occur
during
the
installation
process
and
how
to
perform
recovery
actions.
Note:
The
installation
problem
determination
contained
in
this
guide
addresses
only
installations
using
the
Rapid
Deployment
Assistant.
Common
installation
problems
and
workarounds
The
following
problems
mignht
occur
when
you
install
and
set
up
or
uninstall
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server.
Table
1.
Common
installation
problems
and
workarounds
Problem
Workaround
General
installation
problems
In
the
Step
List
panel
of
the
installer
you
might
see
the
following
message
box
when
installation
of
the
Tivoli
desktop
software
begins:
″String
variable
is
not
large
enough
for
string.
Check
string
declarations.
Error
401.″.
Click
OK
to
continue
the
installation.
After
installation,
if
you
are
unable
to
launch
the
Tivoli
desktop,
run
the
installation
program
that
is
found
in
the
following
directory
path
of
the
Tivoli
Management
Framework,
Upgrade
from
Version
3.7,
Revision
B
to
Version
3.7.1
installation
CD:
PC\DESKTOP\DISK1\SETUP.EXE.
Note:
This
does
not
apply
to
UNIX
systems.
You
might
see
the
following
message
during
installation:
″This
program
must
run
on
the
TMR
server.″
This
error
occurs
when
an
installation
of
Tivoli
Management
Framework
existed
previously
on
the
target
computer
and
was
not
completely
uninstalled.
An
incomplete
uninstallation
leaves
the
script
that
sets
up
the
Tivoli
environment,
setup_env.sh
on
UNIX
and
setup_env.cmd
on
Windows.
When
the
installer
detects
this
file,
it
assumes
that
the
Tivoli
Management
Framework
is
already
installed
and
installation
fails.
1.
Click
OK.
The
installer
prompts
you
to
end
the
installation.
2.
Click
Finish.
3.
Delete
the
temporary
depot
directory
created
by
the
installer.
4.
Delete
the
environment
setup
file
from
the
following
directory:
v
On
UNIX:
/etc/Tivoli
v
On
Windows:
%SystemRoot%\system32\drivers\etc\Tivoli
5.
Start
the
installation
process
again.
The
Browse
option
in
the
installer
panels
requires
a
long
time
period
to
launch
the
file
selection
window.
This
problem
occurs
when
the
computer
has
multiple
file
systems
mounted.
The
installer
verifies
connectivity
with
each
file
system
before
presenting
the
window.
Minimize
the
number
of
file
systems
mounted
on
the
computer.
—OR—
Type
the
path
of
the
target
file
system
in
the
text
box
to
directly
access
that
file
system.
The
Browse
option
in
the
installer
panels
fails
to
display
a
CD-ROM
drive.
The
problem
occurs
when
you
click
Browse
while
the
CD-ROM
drive
is
empty.
After
the
problem
occurs,
you
cannot
resolve
it
by
inserting
a
CD
into
the
drive.
Type
the
path
of
the
target
file
system
in
the
text
box
to
directly
access
that
file
system.
When
you
run
the
installer
on
UNIX,
a
Java
exception
message
like
the
following
might
display
in
the
terminal
session
used
to
launch
the
installer:
Exception
occurred
during
event
dispatching:
java.lang.NullPointerException...
You
can
ignore
this
exception.
The
installer
continues
to
run.
3
Table
1.
Common
installation
problems
and
workarounds
(continued)
Problem
Workaround
When
you
run
the
installer
in
an
interconnected
Tivoli
management
region,
the
installation
stops
if
you
try
to
install
the
software
on
another
Tivoli
management
region
computer.
Mount
the
installation
media
in
the
CD-ROM
drive
of
the
Tivoli
management
region
computer
on
which
you
are
installing
the
product.
Some
HP-UX
operating
systems
might
fail
to
find
long
file
names
on
the
installation
CDs
for
this
product.
These
systems
cannot
process
the
Rock
Ridge
extensions
that
are
used
to
write
the
product
CDs.
Change
how
you
mount
the
CDs.
In
many
cases,
you
can
use
the
pfs_mount
command
to
mount
the
CD.
See
the
Hewlett-Packard
Company
Web
site
for
information.
The
Patch
Database
in
the
Hewlett-Packard
IT
Resource
Center
has
information
for
some
operating
system
versions.
The
release
notes
for
HP-UX
10.x
systems
also
provide
information.
Internationalization
problems
Language
Settings:
In
non-English
operating
systems,
characters
might
become
illegible.
Try
to
resolve
illegible
characters
by
changing
the
locale
settings
of
the
operating
system
of
the
Tivoli
Management
Region
server.
Many
operating
systems
that
use
double-byte
character
sets,
such
as
Chinese,
have
variable
locale
settings.
If
you
adjust
the
locale
settings
in
the
Tivoli
Management
Region
server
you
might
resolve
this
error.
For
example,
a
Chinese
operating
system
might
have
multiple
locale
variants
that
you
can
try
until
you
find
one
that
works
for
the
target
language.
However,
not
all
operating
systems
have
variable
locale
settings.
See
the
documentation
for
your
operating
system
to
learn
about
its
capabilities.
Language
Settings:
The
system
can
generate
an
error
regarding
a
missing
dynamic
Link
Library
that
Tivoli
requires.
For
a
non-English
Tivoli
environment,
you
must
install
the
kbdus.dll
file
before
installing
IBM
Tivoli
Monitoring
for
Web
Infrastructure.
You
can
obtain
this
file
from
Microsoft
or
on
the
product
CDs
for
Windows
NT
or
Windows
2000
in
all
language
versions
of
these
operating
systems.
The
kbdus.dll
file
must
reside
in
the
%SystemRoot%\system32
directory.
The
installer
reports
failure
of
installation
of
language
support
packs
for
Tivoli
Management
Framework,
Version
3.7.1
or
4.1.
After
installation
is
complete,
manually
install
the
language
pack
or
packs
for
Tivoli
Management
Framework,
Version
3.7.1
or
4.1.
Use
the
Tivoli
desktop
or
winstall
command,
as
described
in
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure
Installation
and
Setup
Guide.
When
you
run
the
installer
on
HP-UX
systems
in
the
Traditional
Chinese
locale,
the
installer
might
fail
to
display
text
if
required
fonts
are
not
available.
Hewlett-Packard
Company
recommends
that
specific
patches
be
installed
for
double-byte
character
set
(DBCS)
locales
for
the
Hewlett-Packard
Java
runtime
environment,
Version
1.3.1,
to
work:
v
Common:
PHSS_25091
(for
11.0)
or
PHSS_25092
(for
11i)
v
Japanese:
PHSS_26972
(for
11.0)
or
PHSS_26971
(for
11i)
v
Korean:
PHSS_26974
(for
11.0)
or
PHSS_26973
(for
11i)
v
Simplified
Chinese:
PHSS_26976
(for
11.0)
or
PHSS_24975
(for
11i)
v
Traditional
Chinese:
PHSS_24937
(for
11.0)
or
PHSS_26977
(for
11i)
If
you
install
patches
required
by
the
Hewlett-Packard
Company
and
the
problem
persists,
run
the
installer
in
English.
4
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
Table
1.
Common
installation
problems
and
workarounds
(continued)
Problem
Workaround
Uninstallation
problems
When
uninstalling
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
with
interconnected
Tivoli
management
region
servers,
you
might
see
the
following
messages:
Removing
ITMWAS
from
the
entire
TMR....
(
this
could
take
a
few
minutes
)
Creating
Task...
Running
Task...
(
this
could
take
a
few
minutes
)
################################################
Task
Name:
uninstall_task
Task
Endpoint:
<managed_node_name>
(ManagedNode)
Return
Code:
0
------Standard
Output------
{
USER_EXCEPTION
SysAdminException::ExExists
{
"Exception:UserException:SysAdminException::
ExException:SysAdminException::ExInvalid:
SysAdminException::ExExists"
"TNR_errors"
5
"The
resource
cache
for
\"%7$s\"
is
not
empty."
1066665179
{
0
}
"WSApplicationServer"
}}{
USER_EXCEPTION
SysAdminException::ExExists
{
"Exception:UserException:SysAdminException::
ExException:SysAdminException::ExInvalid:Sys
AdminException::ExExists"
"TNR_errors"
5
"The
resource
cache
for
\"%7$s\"
is
not
empty."
1066665179
{
0
}
"WSAdministrationServer"}}
{
USER_EXCEPTION
SysAdminException::ExExists
{
Exception:UserException:SysAdminException::
ExException:SysAdminException::ExInvalid:
SysAdminException::ExExists"
"TNR_errors"
5
"The
resource
cache
for
\"%7$s\"
is
not
empty."
1066665179
{
0
}
"IWSApplicationServer"}}
-----Standard
Error
Output------
##################################################
Cleaning
up...
wuninst
complete.
Ignore
the
USER_EXCEPTION.
When
using
the
wuninst
ITMWAS
<managed_node>
–rmfiles
command
to
uninstall
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server,
you
might
receive
the
following
error
message:
FRWOG0040E
A
failure
was
detected
by
the
oserv
daemon:
FRWOG0040E
Transaction
Error
Error
in
$DBDIR/IZY/logs/trace_itmwas_uninstall_prod.log
+
wdel
@PolicyRegion:<Policy
Region
Name>
FRWSL0002E
An
invalid
internal
parameter
found:
FRWOG0006E
named
resource
already
exists
Please
refer
to
the
TME
10
Framework
Planning
and
Installation
Guide,
"TME
Maintenance
and
Troubleshooting"
for
details
on
diagnosing
internal
errors
or
contact
your
Software
Support
provider.
This
might
occur
if
you
create
a
policy
region
under
the
Monitoring
for
WebSphere
Application
Server
policy
region,
then
create
a
profile
manager
in
this
new
policy
region.
The
uninstall
command
removes
only
profile
managers
directly
under
the
Monitoring
for
WebSphere
Application
Server
policy
region.
Because
the
profile
manager
is
not
deleted
under
the
new
policy
region,
the
command
to
delete
the
policy
region
fails
because
the
policy
region
is
not
empty.
Manually
delete
the
profile
managers
and
policy
region,
including
the
Monitoring
for
WebSphere
Application
Server
policy
region.
Then
run
wdel
@ProductInfo:ITMWAS
wchkdb
-u
Chapter
2.
Installation
problem
determination
5
Resolving
installer
problems
Objective
To
resolve
or
work
around
common
problems
that
can
occur
during
an
installation.
Background
information
This
procedure
describes
actions
you
can
take
in
the
Step
List
panel
of
the
installer.
The
Step
List
provides
detailed
information
about
the
progress
of
installation.
This
panel
is
displayed
near
the
end
of
the
installation
process,
when
the
installer
is
processing
all
your
configuration
settings.
Double-click
any
step
in
the
Step
List
panel
to
see
information
on
the
step
in
the
Detail
window:
v
The
software
that
you
are
installing
and
configuring
v
The
installation
status
of
the
current
step
v
A
short
description
of
the
step
v
Messages
and
error
resolution
options
in
case
of
a
warning
or
step
failure.
Required
authorization
On
UNIX,
the
user
who
installs
the
product
must
have
root
privileges.
On
Windows,
the
user
who
installs
the
product
must
have
membership
in
the
Administrators
group.
Before
you
begin
Use
the
installer
to
start
one
of
the
following
types
of
installation,
described
in
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure
Installation
and
Setup
Guide:
v
Typical
installation
v
Evaluation
installation
While
you
work
with
the
installer,
you
can
use
the
options
described
in
this
procedure
to
work
around
and
resolve
problems.
When
you
finish
Complete
the
installation
of
the
product,
as
described
in
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure
Installation
and
Setup
Guide.
Procedure
1.
(Optional)
If
you
want
to
cancel
the
installation
while
the
Step
List
is
running,
perform
the
following
steps:
a.
Click
Stop
and
allow
the
process
that
is
currently
running
to
finish.
If
you
click
Cancel
without
allowing
the
currently
running
process
to
finish,
the
system
might
remain
in
an
unpredictable
state.
b.
Click
Cancel
to
stop
the
installation
and
close
the
installer.
c.
Delete
the
temporary
depot
directory
created
by
the
installer.2.
(Optional)
Double-click
any
item
in
the
Step
List
to
see
details
and
to
set
processing
instructions
for
that
step
in
the
Detail
window.
Table
2
shows
the
status
icons
and
options
in
the
Detail
window:
Table
2.
Status
icons
and
options
for
the
Step
List
panel
of
the
installer
Name
Icon
Value
Status
icons
in
the
Step
List
Pending
None
The
step
has
not
been
run
yet.
6
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
Table
2.
Status
icons
and
options
for
the
Step
List
panel
of
the
installer
(continued)
Name
Icon
Value
Passed
The
step
completed
successfully.
Passed_Reboot
The
step
completed
successfully
and
you
must
reboot
the
system.
This
status
causes
the
installer
to
prompt
you
to
restart
the
computer.
Passed_Warning
The
step
completed
with
one
or
more
warnings.
For
example,
the
installer
might
warn
you
to
restart
computers
on
which
you
installed
the
Web
Health
Console.
Otherwise,
the
console
is
not
activated.
The
installer
might
also
list
warnings
from
the
installation
logs
of
the
Tivoli
Management
Framework.
You
can
consult
the
documentation
that
comes
on
the
installation
CDs
for
Tivoli
Management
Framework
for
information
on
this
type
of
warning.
Failed
The
step
failed.
This
procedure
describes
how
to
analyze
and
handle
failed
steps.
Deferred
The
step
was
postponed.
This
icon
is
displayed
after
you
defer
a
step
in
the
Detail
window,
as
described
near
the
end
of
the
installation
procedure.
See
the
description
of
Defer
in
this
table
for
more
information.
Locked
The
step
will
be
skipped
because
it
is
dependent
on
a
previous
step
that
has
been
deferred.
The
only
way
a
locked
step
can
be
unlocked
is
to
enable
(or
″un-defer″)
all
steps
on
which
the
locked
step
is
dependent.
To
see
a
list
of
these
dependencies,
double-click
the
locked
step
and
read
the
error
message
in
its
Detail
window.
Breakpoint
The
step
was
placed
in
breakpoint
mode.
The
installer
stops
processing
steps
at
the
breakpoint.
You
can
check
progress
and
change
settings,
if
necessary.
Options
Defer/Enable
Postpones
the
step
to
a
later
time.
If
a
step
has
failed,
you
can,
as
a
last
resort,
defer
the
step.
After
that,
the
only
way
to
reactivate
that
step
is
by
pressing
Execute
(see
description
below).
If
you
defer
a
step
before
it
is
executed
(such
as
when
it
has
a
″Pending″
status),
you
can
enable
the
step.
The
Defer
option
turns
into
Enable,
allowing
you
to
return
its
status
from
″Deferred″
to
″Pending.″
If
subsequent
steps
are
dependent
on
a
deferred
step,
they
will
automatically
be
locked.
A
locked
step
cannot
be
run.
For
instance,
if
you
defer
a
step
for
creating
a
managed
node,
all
other
steps
that
install
to
that
managed
node
would
be
locked,
since
they
are
dependent
upon
its
creation.
These
locked
steps
would
only
be
reset
when
the
deferred
step
changes
status.
Toggle
Breakpoint
Activate
or
Deactivate
the
breakpoint.
If
you
activate
the
breakpoint,
the
automatic
installation
process
is
interrupted
when
it
reaches
that
step
and
you
are
asked
for
input.
If
you
want
the
installer
to
pause
after
specific
steps
are
complete,
activate
a
breakpoint
on
the
subsequent
step.
For
example,
you
can
set
a
breakpoint
to
enable
installation
of
proxy
endpoints.
OK
Returns
to
the
previous
window.
Execute
Executes
a
deferred
step
that
occurs
prior
to
the
current
step.
After
the
completion
of
the
deferred
step,
any
locked
steps
that
were
dependent
on
this
step
change
to
the
″Pending″
status.
Click
Run
Steps
on
the
Step
List
to
run
the
subsequent
steps.
Change
Enables
you
to
make
the
following
types
of
change:
v
Change
the
user
ID
or
password.
v
Change
the
destination
directory
for
the
creation
of
a
managed
node
or
endpoint.
Note:
Some
steps
do
not
have
Change
as
an
active
option.
Steps
that
do
have
Change
as
an
option
include
managed
node
and
endpoint
creation.
3.
Respond
to
the
Step
List’s
error,
event,
or
action
prompts
that
might
be
displayed.
Chapter
2.
Installation
problem
determination
7
v
Message
logs:
Consult
the
following
resources
in
case
of
installation
errors
–
The
message
log
in
the
following
directory:
tivoli/depot/DeployEngine/logs/deploy.log.
Software
Support
uses
this
file
to
determine
the
source
of
problems.
–
See
the
Tivoli
Enterprise
Installation
Guide
that
comes
with
Tivoli
Management
Framework,
Version
3.7.1
or
4.1,
for
complete
troubleshooting
analysis.v
Warnings:
The
step
might
complete
with
one
or
more
warnings.
For
example,
the
installer
might
warn
you
to
restart
computers
on
which
you
installed
the
Web
Health
Console.
Otherwise,
the
console
is
not
activated.
The
installer
might
also
list
warnings
from
the
installation
logs
of
the
Tivoli
Management
Framework.
You
can
consult
the
documentation
that
comes
on
the
installation
CDs
for
Tivoli
Management
Framework
for
information
on
this
type
of
warning.
Also
see
Table
16
on
page
50.
v
Change
value
operations:
Perform
the
following
steps
any
time
you
become
aware
of
a
user
name
or
password
error:
a.
Double-click
the
step
in
which
an
error
occurs
to
display
the
Detail
window.
b.
Click
Change
to
display
the
Change
Value
window.
c.
Enter
the
new
value
in
the
Change
Value
window
for
user
ID,
password,
and
destination
directory,
as
needed.
d.
Click
OK.4.
If
a
Change
Value
operation
fails,
perform
the
following
steps:
a.
See
Table
2
on
page
6
for
a
description
of
the
proper
use
of
Defer.
b.
Click
Defer
in
the
Step
Detail
window.
c.
Allow
the
installer
to
finish
processing
the
Step
List.5.
If
you
have
made
changes
that
permit
the
successful
execution
of
deferred
steps,
execute
the
steps
that
you
deferred.
For
example,
you
can
successfully
execute
a
deferred
step
after
this
sequence
of
events:
Event
1:
The
installer
initially
failed
to
create
a
managed
node
on
a
computer
because
the
target
computer
was
down.
Event
2:
You
defer
the
step
so
that
installation
can
continue
while
the
target
computer
is
restarting.
Event
3:
The
installer
finishes
processing
the
Step
List
and
the
target
computer
for
the
managed
node
finishes
restarting.
Perform
the
deferred
steps
as
follows:
a.
Double-click
the
first
deferred
step
in
the
Step
List
to
display
the
Detail
window.
b.
Click
Execute.
c.
Double-click
the
next
deferred
step
in
the
Step
List
to
display
the
Detail
window.
d.
Click
Execute.
e.
Continue
executing
the
deferred
steps
in
sequence
until
all
steps
are
complete.6.
If
failed
steps
remain
in
the
Step
List,
perform
the
following
steps:
8
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
The
installation
can
be
successful
even
when
deferred
steps
exist
or
when
optional
steps
fail
or
generate
warnings.
For
example,
the
creation
of
the
Tivoli
Management
Environment
and
installation
of
the
product
is
successful
when
the
following
optional
steps
fail:
v
Creation
of
managed
nodes
or
endpoints
v
Installation
of
the
Web
Health
Console
For
these
types
of
failures,
the
installer
does
not
display
a
completion
window
or
other
options,
but
the
installation
is
successful.
You
can
exit
the
installer
and
begin
to
run
the
product.
Resolve
failed
steps
and
warnings
as
follows:
a.
Click
Cancel
to
dismiss
the
user
interface
of
the
installer.
b.
If
possible,
resolve
conditions
that
prevented
failed
steps
or
caused
warnings.
For
example,
resolve
network
connectivity
problems.
Also,
be
sure
the
prerequisite
conditions
exist
on
the
computers
on
which
failure
occurred,
as
described
in
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure
Installation
and
Setup
Guide.
You
might
be
able
to
use
the
procedures
in
the
Tivoli
Enterprise
Installation
Guide
that
comes
with
the
Tivoli
Management
Framework
software
to
manually
complete
failed
steps,
such
as
the
installation
of
managed
nodes
and
endpoints.
See
the
the
Tivoli
Information
Center
for
the
newest
version
of
the
Limitations
and
Workarounds
Supplement
for
each
component
to
find
all
possible
solutions
to
step
failure.
c.
Analyze
the
installation
logs.
See
Table
16
on
page
50
for
further
information.
Testing
endpoint
connectivity
Objective
To
test
whether
the
Tivoli
Management
Region
server
can
communicate
with
a
specific
endpoint.
Background
information
The
Tivoli
server
must
be
able
to
communicate
with
the
endpoints
it
manages.
The
endpoint
(Lightweight
Client
Agent)
is
software
you
install
on
a
machine
where
the
Web
server
(Apache
HTTP
Server,
Internet
Information
Server,
iPlanet
Web
Server,
IBM
WebSphere
Application
Server,
WebLogic
Server)
is
installed
to
enable
communication
with
the
Tivoli
managed
nodes.
Required
authorization
role
On
UNIX,
the
user
who
installs
the
product
must
have
root
privileges.
On
Windows,
the
user
who
installs
the
product
must
have
membership
in
the
Administrators
group.
Before
you
begin
None
When
you
finish
If
endpoint
connectivity
problems
continue,
see
“Cleaning
up
and
removing
endpoints”
on
page
10.
Procedure
This
procedure
can
be
performed
only
from
the
command
line.
Command
line:
1.
Access
the
Tivoli
Environment
as
described
in
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure
Installation
and
Setup
Guide.
Chapter
2.
Installation
problem
determination
9
2.
Run
the
ping
command
from
the
Tivoli
server
to
confirm
that
the
endpoint
is
accessible
over
the
network.
If
you
receive
connection
or
timeout
errors,
stop
at
this
point
and
contact
your
network
administrator
for
help.
3.
If
you
do
not
know
the
name
of
the
endpoint,
run
the
following
command
on
the
Tivoli
server
to
see
a
list
of
all
endpoints
that
are
connected
to
the
server:
wlookup
-a
-r
Endpoint
4.
Run
the
following
command
on
the
Tivoli
Management
Region
server:
wadminep
<ep_name>
view_version
where
<ep_name>
is
the
name
of
a
specific
endpoint
on
an
IBM
Tivoli
Monitoring
for
Web
Infrastructure
server.
See
the
list
generated
in
Step
3
to
obtain
the
names
of
endpoints.
5.
If
you
receive
a
message
other
than
one
containing
a
version
number,
the
endpoint
software
must
be
restarted.
You
can
manually
restart
the
endpoint
on
that
server
by
doing
the
following
steps
on
the
endpoint
system:
v
On
Windows
systems:
a.
Run
the
following
command
on
the
endpoint
to
stop
lcfd,
the
process
of
the
endpoint:
net
stop
lcfd
b.
Run
the
following
command
on
the
endpoint
to
start
the
lcfd
process:
net
start
lcfd
v
On
UNIX
systems:
a.
Set
the
environment
using
the
following
command:
.
/etc/Tivoli/lcf/<endpoint_number>/lcf_env.sh
b.
Use
the
following
command
to
stop
the
endpoint
processes:
$LCF_DATDIR/lcfd.sh
stop
c.
Use
the
following
command
to
restart
the
endpoint
process:
$LCF_DATDIR/lcfd.sh
v
On
OS/400
systems:
Start
and
stop
the
endpoint
using
the
following
commands:
STRTMEEPT
ENDMEEPT
See
the
Tivoli
Management
Framework
Reference
Guide
for
more
information.6.
Monitor
the
state
of
the
endpoint
you
have
just
restarted
from
a
Web
browser
using
the
following
URL:
http://<host>:<ep_port>
where
<host>
is
the
name
of
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure
server
host
and
<ep_port>
is
the
name
of
the
port
that
you
assigned
for
endpoint
transactions
in
the
Tivoli
server.
The
value
of
Status
for
the
endpoint
must
be
running.
Cleaning
up
and
removing
endpoints
Objective
To
clean
up
the
endpoint
process
and
remove
endpoint
files
from
the
Tivoli
environment.
10
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
Background
information
You
use
clean
up
and
remove
an
endpoint
after
you
complete
the
diagnostic
tests
listed
in
“Testing
endpoint
connectivity”
on
page
9.
Those
tests
can
confirm
that
the
endpoint
is
not
working.
The
endpoint
process
runs
at
all
times
on
an
IBM
Tivoli
Monitoring
for
Web
Infrastructure
server
host.
Removal
of
the
agent
requires
three
actions
that
this
procedure
describes:
v
Stopping
the
endpoint
service
v
Erasing
the
endpoint
directories
and
files
on
the
client
computer
v
Removing
startup
statements
from
system
configuration
files
on
the
client
computer
The
endpoint
installation
wizard
is
described
in
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure
Installation
and
Setup
Guide.
On
a
partitioned
IBM
Tivoli
Monitoring
for
Web
Infrastructure
server
that
runs
in
a
Windows
environment,
each
partition
runs
a
separate
copy
of
the
endpoint.
When
you
uninstall
a
endpoint,
you
must
identify
the
specific
agent
that
you
want
to
uninstall.
Note:
The
following
procedure
assumes
that
IBM
Tivoli
Monitoring
for
Web
Infrastructure
objects
have
either
been
deleted
or
not
yet
created.
Required
authorization
role
The
installation
routine
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure
creates
the
Tivoli
administrator
who
is
authorized
to
perform
this
procedure.
Other
administrators
must
have
the
senior
role
to
perform
this
operation.
On
UNIX,
the
user
must
have
root
privileges.
On
Windows,
the
user
must
have
membership
in
the
Administrators
group.
Before
you
begin
Complete
the
tests
described
in
“Testing
endpoint
connectivity”
on
page
9.
When
you
finish
If
you
used
this
procedure
to
resolve
a
communications
error
with
an
IBM
Tivoli
Monitoring
for
Web
Infrastructure
server
endpoint,
perform
the
following
steps
to
re-install
the
endpoint
software:
1.
Install
a
new
endpoint
as
described
in
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure
Installation
and
Setup
Guide.
Note:
If
you
re-use
the
original
name
of
the
endpoint,
wait
15
minutes
before
you
perform
this
step
to
ensure
that
no
process
is
referencing
the
name.
2.
Verify
the
new
endpoint
you
installed
as
described
in
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure
Installation
and
Setup
Guide.
Procedure
This
procedure
can
be
done
from
the
command
line
only.
Command
line:
Note:
The
directories
specified
in
the
following
procedure
reflect
the
default
locations.
Your
installation
might
differ.
1.
Log
on
to
the
Tivoli
Management
Region
server.
Chapter
2.
Installation
problem
determination
11
2.
Access
a
command
prompt
window.
3.
Start
the
command
line
interface
as
described
in
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure
Installation
and
Setup
Guide.
4.
Run
the
following
command
on
the
Tivoli
server
to
delete
the
endpoint
object
from
the
Tivoli
database:
wdelep
<endpoint_name>
where
<endpoint_name>
is
the
name
of
the
endpoint
that
you
assigned
when
you
created
the
endpoint.
5.
Log
on
to
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure
server
endpoint.
6.
Stop
the
endpoint
as
follows:
v
On
Windows,
stop
and
remove
the
endpoint
service
by
entering
the
following
command
on
one
line:
%SystemDrive%\Tivoli\lcf\bin\w32-ix86\mrt\lcfd
-r
"lcfd"
where
%SystemDrive%\Tivoli\lcf
is
the
default
path
where
an
endpoint
is
installed
and
″lcfd″
is
the
default
service
name.
v
On
UNIX,
use
one
of
the
following
methods.
–
Setup
the
Tivoli
environment
by
running
the
following
command:
.
/etc/Tivoli/lcf/<endpoint_number>/lcf_env.sh
where
<endpoint_number>
is
the
number
for
the
endpoint.
–
Enter
the
$LCF_DATDIR/lcfd.sh
stop
command.
7.
(Windows
only)
Run
the
following
command
to
remove
the
Tivoli
tool
that
tracks
connection
statistics:
%SystemDrive%\Tivoli\lcf\bin\w32-ix86\mrt\lcfep
-s
If
you
used
the
InstallShield
endpoint
installation
option
on
Windows,
you
do
not
need
to
perform
this
procedure.
Run
the
uninst.bat
located
in
the
endpoint
installation
directory.
For
example,
if
you
used
the
default
installation
directory
for
your
endpoint
installation,
run
the
following
command:
%SystemRoot%\Tivoli\lcv\<endpoint_number>\lcf_env.cmd
%LCFROOT%\uninst.bat
where
%SystemRoot%
is
the
environment
variable
for
system
drive.
8.
Remove
the
endpoint
installation
directory
and
subdirectories
from
the
following
default
locations:
v
On
UNIX:
the
directory
specified
by
the
$LCFROOT
variable
v
On
Windows:
the
directory
specified
by
the
%LCFROOT%
environment
variable
9.
Remove
the
endpoint
environment
directory,
including
its
subdirectories
and
files
from
the
following
default
locations:
v
On
UNIX:
/etc/Tivoli/lcf
<endpoint_number>
v
On
Windows:
%SystemRoot%\Tivoli\lcf
<endpoint_number>10.
Remove
the
endpoint
startup
item
in
one
of
the
following
locations:
v
On
AIX:
/etc/inittab
(You
must
use
the
following
removal
command:
/etc/rmitab
rctma1)
v
On
HP-UX:
/sbin/init.d/lcfd1.sh
v
On
Solaris:
/etc/init.d/lcfd1.rc
12
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
v
On
Windows:
(No
action
necessary.
The
endpoint
startup
item
is
the
Tivoli
Endpoint
service,
and
the
command
in
Step
6
automatically
removed
it.)11.
(AIX
only)
Remove
the
/etc/rc.tma1
and
/etc/inittab.before.tma1
files.
12.
(Solaris
and
HP-UX
only)
Remove
the
following
symbolic
links:
v
On
Solaris:
–
/etc/rc0.d/K50Tivoli_lcf1
–
/etc/rc1.d/K50Tivoli_lcf1
–
/etc/rc2.d/K50Tivoli_lcf1
–
/etc/rc3.d/S99Tivoli_lcf1v
On
HP-UX:
–
/sbin/rc0.d/K100Tivoli_lcf1
–
/sbin/rc1.d/K100Tivoli_lcf1
–
/sbin/rc2.d/K100Tivoli_lcf1
–
/sbin/rc3.d/S500Tivoli_lcf113.
Remove
the
userlink.htm
file
from
the
following
location:
v
On
UNIX:
/etc/Tivoli/*/userlink.htm
v
On
Windows:
%SystemDrive%\etc\tivoli\c\userlink.htm
Chapter
2.
Installation
problem
determination
13
14
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
Chapter
3.
Problems
and
workarounds
The
following
sections
provide
symptoms
and
workarounds
for
problems
that
might
occur
with
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server.
The
following
topics
are
discussed:
v
“General
problems”
v
“General
proxy
mode
z/OS
problem
determination”
on
page
17
v
“General
resource
model
problem
determination”
on
page
19
v
“Proxy
mode
z/OS-related
resource
model
problem
determination”
on
page
26
v
“Tasks
problem
determination”
on
page
34
v
“Tivoli
Enterprise
Console
problem
determination”
on
page
41
v
“Tivoli
Enterprise
Data
Warehouse
problem
determination”
on
page
42
General
problems
The
following
table
contains
a
list
of
general
problems
that
might
occur
with
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server.
Table
3.
General
problems
and
solutions
Problem
Solution
You
cannot
use
the
same
system
as
both
a
local
(non-z/OS)
and
a
proxy
mode
z/OS
endpoint.
None
This
product
attaches
to
WebSphere
for
z/OS
through
the
JVM
Profiler
Interface
(JVMPI).
The
interface
is
limited
to
attaching
at
most
one
product
to
WebSphere
for
z/OS.
None.
For
additional
information
about
the
JVMPI,
see
Sun’s
Java
Web
site.
The
OS
Type
attribute
for
IBM
WebSphere
Application
Server
Version
5
resources
discovered
through
deployment
managers,
including
the
deployment
manager
itself,
is
″UNKNOWN.″
Due
to
performance
issues,
the
OS
Type
for
these
resources
is
not
retrieved.
When
trying
to
stop
an
enterprise
application,
if
either
the
node
agent
or
the
application
server
are
down,
you
receive
the
following
message:
IZY1233I
The
enterprise
application
<application_name>
is
already
stopped.
The
enterprise
application
is
not
stopped.
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
cannot
communicate
with
the
enterprise
application
because
the
node
agent
or
the
application
server
is
not
running.
Start
the
node
agent
or
application
server
and
try
to
stop
the
enterprise
application
again.
15
Table
3.
General
problems
and
solutions
(continued)
Problem
Solution
You
receive
events
from
the
5.1.0
version
of
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
Tivoli
Enterprise
Console
event
adapter,
even
though
you
have
upgraded
to
the
5.1.1
version.
You
might
also
see
an
extra
Java
process
running
on
your
system.
You
did
not
stop
the
5.1.0
version
of
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
Tivoli
Enterprise
Console
event
adapter
before
you
installed
or
upgraded
the
5.1.1
version
of
the
event
adapter.
Use
the
following
steps
to
correct
this
problem:
v
Source
in
the
itmwas_tecadapter_src
file
on
the
endpoint.
This
file
is
located
in
the
$LCF_BINDIR/../../generic_unix/TME/WSAPPSVR/utils
directory.
This
file
contains
the
port
number
(EVENT_ADAPTER_PORT)
that
the
event
adapter
uses
to
listen
for
requests.
v
Run
the
following
command
to
stop
the
event
adapter
on
the
endpoint:
$LCF_DATDIR/../TME/WSAPPSVR/utils/wsepmprobe
\
127.0.0.1
"$EVENT_ADAPTER_PORT"
STOP
You
receive
the
following
message:
Stopping
ITMWAS
event
adapter
server
If
you
receive
the
following
message,
the
event
adapter
was
already
stopped:
-1
Unable
to
connect
128
In
an
interconnected
Tivoli
management
region,
if
different
Tivoli
management
region
servers
discover
or
create
the
same
object,
when
the
Send_WebSphere_Discovery_Events_to_TBSM
task
is
run,
the
output
shows
that
the
object
event
was
sent
to
Tivoli
Business
Systems
Manager,
but
only
one
object
is
displayed
in
the
Tivoli
Business
Systems
Manager
console.
None,
this
is
a
Tivoli
Business
Systems
Manager
limitation.
When
running
a
task
on
Tivoli
Business
Systems
Manager
with
an
incorrect
permission
set,
you
might
receive
the
following
message:
Command
execution
completed.
FRWSL:0024
A
failure
was
detected
by
the
oserv
daemon:
o_errs:0040
Transaction
Error
If
you
receive
this
message,
check
the
permissions
of
your
Tivoli
Management
Framework
setup.
On
the
Tivoli
Business
Systems
Manager
console,
a
previously
discovered
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
object
that
you
delete
and
recreate
is
not
displayed
correctly,
even
though
you
ran
the
Send_WebSphere_Discovery_Events_to_TBSM
task.
The
original
object
is
marked
as
deleted,
but
the
new
object
does
not
exist.
This
problem
might
occur
if
you
delete
and
recreate
an
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
object
and
run
the
Send_WebSphere_Discovery_Events_to_TBSM
task
after
you
have
already
run
the
Send_WebSphere_Discovery_Events_to_TBSM
task.
This
can
be
caused
by
a
timing
problem
in
the
sequence
of
events.
Run
the
Send_WebSphere_Discovery_Events_to_TBSM
task
once
more.
An
IWSApplicationServer
object
cannot
be
used
to
start,
stop,
or
list
a
clustered
application.
None
16
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
Table
3.
General
problems
and
solutions
(continued)
Problem
Solution
The
List_Enterprise_Applications
task
returns
a
status
of
″Running″
for
a
clustered
application
while
the
administration
console
shows
the
status
of
the
clustered
application
as
″Partial
Start″
and
the
status
of
the
cluster
itself
as
″Partial
Stop.″
This
behavior
occurs
when
one
or
more
application
servers
in
the
cluster
is
not
running.
Check
the
status
of
the
individual
application
servers
and
restart
any
stopped
servers.
The
List_Enterprise_Applications
task
returns
a
status
of
Running
when
pieces
of
the
enterprise
application
are
running
but
others
are
stopped.
For
enterprise
applications
deployed
in
IBM
WebSphere,
you
can
deploy
pieces
of
the
application
on
different
application
servers.
For
example,
the
EJBs
can
be
deployed
on
server1
and
the
servlets
on
server2.
When
monitoring
IBM
WebSphere
Version
5,
a
status
of
Running,
Stopped,
Partial
Start,
and
Partial
Stop
is
returned
based
on
if
the
application
is
totally
running,
totally
stopped,
or
only
partially
running
(for
example,
the
servlets
are
running
on
server2,
but
the
EJBs
are
stopped
on
server1).
However,
for
IBM
WebSphere
Versions
4
and
3.5,
you
cannot
query
individual
pieces
of
the
application,
meaning
Partial
Start/Stop
status
for
these
IBM
WebSphere
versions
cannot
be
returned.
If
some
pieces
are
still
running,
while
others
are
stopped,
a
status
of
Running
is
returned.
You
might
see
messages
related
to
missing
dependencies,
such
as
patches,
even
though
you
have
all
the
required
dependencies
installed.
The
message
also
might
state
that
a
required
file
cannot
be
found.
This
can
occur
if
you
install
required
dependencies
(such
as
Tivoli
Enterprise
Console)
or
patches
to
the
required
dependencies
after
installing
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server.
To
fix
this,
run
the
following
script:
$BINDIR/../generic_unix/TME/WSAPPSVR/itmwas_tool_dep.sh
Notes:
1.
On
Windows
systems,
you
must
run
this
script
from
the
bash
shell.
2.
Depending
on
the
problem,
you
might
need
to
re-initialize
the
object
in
order
to
push
the
newly
linked
dependencies
to
the
endpoint.
Security-related
WebSphere
messages
appear
in
trace
logs.
—OR—
You
have
trouble
restarting
the
Tivoli
Enterprise
Console
adapter
and
resource
models.
Ensure
that
you
have
the
latest
IBM
WebSphere
PTFs
installed.
The
policy
region
name
does
not
display
correctly
on
the
Tivoli
Business
System
Manager
console.
Do
not
use
the
double-byte
characters
for
the
policy
region
name.
General
proxy
mode
z/OS
problem
determination
The
following
table
contains
problems
that
might
occur
with
proxy
mode
z/OS
endpoints.
Chapter
3.
Problems
and
workarounds
17
Table
4.
Proxy
mode
z/OS
systems
problems
and
solutions
Problem
Solution
The
Discover_WebSphere_Resources
task
or
any
of
the
tasks
has
an
error
communicating
with
WebSphere
for
z/OS.
You
might
receive
a
message
similar
to
the
following:
IZY1177E
WebSphere
System
Management
CD390CFG
call
returned
error
code
4
while
running
command
createconversation.
A
failure
of
listconversation
or
createconversation
prevents
tasks
from
working
properly.
Most
tasks
create
a
temporary
conversation
or
list
an
existing
conversation
that
is
used
to
query
information
about
the
server
configuration.
Perform
the
following
actions:
v
Ensure
that
the
IBM
WebSphere
Application
Server
management
servers
are
running.
There
are
four
management
servers,
each
with
one
or
more
server
instances:
–
CBDAEMON
–
CBINTFRP
–
CBNAMING
–
CBSYSMGT
If
these
servers
are
not
working
properly,
the
status
tasks
return
a
status
of
″unknown″
and
other
tasks
cannot
carry
out
their
function.
If
you
recently
restarted
one
of
these
servers,
listconversation
or
createconversation
fails
until
the
server
is
completely
up.
Check
the
status
of
these
servers
with
the
WebSphere
System
Management
Operations
user
interface.
v
Ensure
that
the
user
ID
that
started
the
NETCONV
connection
to
the
endpoint
is
defined
as
a
WebSphere
administrator.
v
Rerun
the
task.
Often,
a
task
that
fails
with
this
error
completes
successfully
on
the
second
attempt,
even
if
there
is
no
obvious
change
in
the
status
of
the
server.
The
Check_Administration_Server_Status
task
returns
the
status
″unknown″
when
the
IBM
WebSphere
application
server
system
management
daemons
are
actually
running.
See
the
previous
solution.
The
Discover_WebSphere_Resources
task
or
any
of
the
tasks
has
an
error
communicating
with
WebSphere
for
z/OS.
The
following
message
is
displayed:
IZY1177E
WebSphere
System
Management
CB390CFG
call
returned
error
code
4
while
running
command
deleteconversation.
A
temporary
conversation,
created
to
obtain
information
about
the
server
configuration,
could
not
be
deleted.
The
task
does
not
fail,
but
an
unused,
uncommitted
conversation
remains
in
the
IBM
WebSphere
Application
Server
database.
Use
the
WebSphere
System
Management
Administration
User
Interface
to
delete
this
temporary
conversation.
A
task
returns
one
of
the
following
messages:
IZY1209E
The
System
Management
Interface
is
not
available.
or
IZY1210E
The
most
common
causes
are
that
the
administration
server
is
down
or
that
the
user
ID
issuing
the
command
does
not
have
the
proper
authority
to
use
the
interface.
Perform
the
following
actions
v
Ensure
that
the
CBDAEMON,
CBINTFRP,
CBNAMING,
and
CBSYSMGT
servers
are
running.
v
Ensure
that
the
user
or
users
defined
to
Tivoli
Business
Systems
Management
Event
Enablement
have
the
authority
to
run
WebSphere
System
Management
APIs.
v
Check
the
task
trace
log
located
in
the
/var/itmwas/trace
directory.
v
Try
to
run
the
IBM
WebSphere
Application
Server
system
management
user
interface
Operations
program
with
the
user
ID
that
has
the
NETCONV
connection.
Because
proxy
mode
z/OS
systems
rely
on
communication
with
proxy
endpoints
to
run
successfully,
you
can
experience
a
number
of
problems
if
one
component
or
your
entire
connection
fails.
The
following
table
lists
the
behavior
that
you
might
18
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
see
if
various
components
stop
functioning.
Table
5.
Behavior
related
to
failed
proxy
mode
z/OS
components
Component
that
is
not
functioning
Result
Data
Collector
Deltas
are
reset;
other
metrics
are
not
reset.
All
of
IBM
WebSphere
Application
Server
All
metrics
are
cleared,
resource
models
return
a
status
of
″Failing
54″
except
for
the
status
resource
models,
which
report
″down.″
Application
server
The
WebSphereAS
Application
Server
Status
resource
model
and
Check_Application_Server_Status
task
report
that
the
server
is
down.
All
metrics
are
cleared
and
resource
models
return
a
status
of
″Failing
54.″
The
WebSphereAS
Administration
Server
Status
resource
model
is
unaffected.
IBM
Tivoli
Monitoring
engine
The
z/OS
Data
Collector
continues
to
collect
data.
Increments
over
intervals
where
the
engine
is
down
are
lost.
Resource
models
restart
and
show
activity
when
the
engine
restarts.
Resource
model
reporting
resumes
after
two
monitoring
cycles
have
occurred.
NETCONV
connection
between
the
host
and
the
endpoint
Status
resource
models
return
a
status
of
″Failing
54″;
other
resource
models
continue
as
long
as
the
Data
Collector
is
running.
TCP/IP
connection
between
the
Data
Collector
and
the
endpoint
Status
resource
models
continue,
other
resource
models
return
a
status
of
″Failing
54″
and
the
Data
Collector
continues
to
run.
When
the
connection
is
restored,
resource
model
reporting
resumes
after
two
monitoring
cycles
have
occurred.
All
of
TCP/IP
on
the
proxy
mode
z/OS
system
All
resource
models
return
a
status
of
″Failing
54″;
metrics
are
reset
when
TCP/IP
is
restarted;
the
Data
Collector
does
not
receive
data.
After
TCP/IP
is
restarted,
if
IBM
WebSphere
Application
Server
was
running,
any
accumulated
data
is
collected;
if
IBM
WebSphere
Application
Server
was
also
down,
no
data
is
collected.
Proxy
mode
z/OS
system
All
metrics
are
cleared;
all
resource
models
return
a
status
of
″Failing
54″;
data
does
not
change
for
intervals
with
no
communication
before
the
outage
is
recognized.
Server
region
within
an
application
loses
connection
with
the
Data
Collector
Metrics
continue;
resource
models
might
or
might
not
show
spikes.
General
resource
model
problem
determination
The
following
table
contains
problems
that
might
occur
with
resource
models.
For
resource
model
problems
specific
to
proxy
mode
z/OS
systems,
see
“Proxy
mode
z/OS-related
resource
model
problem
determination”
on
page
26.
Chapter
3.
Problems
and
workarounds
19
Table
6.
Resource
model
problems
and
solutions
Problem
Solution
Resource
models
that
monitor
EJBs,
Web
applications,
or
servlets,
(such
as
the
WebSphereAS
EJB
or
WebSphereAS
HTTP
Sessions
resource
model)
stop
working
(Failing
54)
if
you
restart
all
associated
enterprise
applications.
This
is
an
IBM
WebSphere
Application
Server
Version
5
limitation.
Stopping
and
restarting
all
enterprise
applications
causes
the
PMI
metrics
monitoring
levels
to
reset
to
none.
Restart
the
application
server.
This
restores
the
previous
settings
for
PMI
monitoring.
For
resource
model
indications,
if
you
click
Tasks
(Action
List)
and
from
the
Libraries
panel,
select
WebSphere
Application
Server
Utility
Tasks,
two
″Upgraded
Task″
tasks
are
displayed.
You
cannot
use
these
tasks
from
this
panel.
Ignore
these
tasks.
A
resource
model
fails
to
start
but
no
event
is
reported
to
Tivoli
Enterprise
Console.
Tivoli
Enterprise
Console
events
are
not
generated
when
a
resource
model
fails
to
start;
they
are
generated
when
there
is
a
problem
or
change
in
a
resource
being
monitored.
Problems
that
occur
with
the
resource
model
itself
are
reported
in
the
IBM
Tivoli
Monitoring
Web
Health
Console.
On
an
AIX
endpoint,
the
WebSphereAS
Administration
Server
Status
resource
model
fails
with
a
NetView
error
similar
to
the
following:
IZY1186E
Host
name
"<host_name>"
could
not
be
converted
to
a
NetView
domain
name.
There
is
a
conflict
between
the
AIX
endpoint
and
the
version
of
Java
Virtual
Machine
(JVM)
installed
on
the
system.
On
the
AIX
endpoint
where
the
IBM
Tivoli
Monitoring
engine
is
running,
set
the
LDR_CNTRL
environment
variable
in
the
engine_launcher
script
to
″LDR_CNTRL=MAXDATA=0x70000000.″
The
engine_launcher
script
is
located,
by
default,
in
the
$LCF_DATDIR/LCFNEW/Tmw2k/Unix/bin
directory.
20
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
Table
6.
Resource
model
problems
and
solutions
(continued)
Problem
Solution
You
receive
the
″Failing
54″
error
code
in
the
Web
Health
Console.
An
error
occurred
collecting
metrics
from
the
application
server;
the
IBM
WebSphere
administration
server
or
application
server
might
be
down,
performance
monitoring
is
not
enabled
for
this
resource,
or
there
are
no
instances
of
this
resource
on
this
application
server.
Check
the
status
of
the
administration
and
application
servers
and
restart
if
necessary.
To
check
the
status
of
the
application
server,
view
the
results
of
the
WebSphereAS_ApplicationServerStatus
resource
model
in
the
Web
Health
Console.
You
can
also
run
the
wdmlseng
–e
<endpoint>
–verbose
command.
If
the
application
server
is
running,
you
can
determine
the
status
of
PMI
data
using
the
Resource
Analyzer
(in
IBM
WebSphere
Application
Server
Version
4)
or
the
Tivoli
Performance
Viewer
(in
IBM
WebSphere
Application
Server
Version
5).
Browse
the
tree
for
the
resource
being
monitored.
If
the
tool
shows
a
pop-up
that
indicates
the
PMI
is
not
turned
on,
turn
it
on.
Note:
You
can
also
use
this
method
to
determine
whether
the
resource
is
available
on
the
application
server.
Activate
performance
monitoring.
If
there
are
no
instances
of
this
resource
on
the
server,
either
remove
the
resource
model
from
the
profile
or
unsubscribe
the
object
from
the
profile
manager.
Notes:
1.
The
WebSphereAS_DynamicCache_12
resource
model
goes
into
the
″Failing
54″
state
if
there
are
no
application
using
dynamic
cache.
Use
Tivoli
Performance
Viewer
to
check
if
″Dynamic
Caching″
metrics
are
available.
2.
The
WebSphereAS_J2CConnector_12
resource
model
goes
into
the
″Failing
54″
state
if
there
are
no
J2C
Connection
Factories
installed.
Use
Tivoli
Performance
Viewer
to
check
if
″JCA
Connection
Pools″
metrics
are
available.
3.
The
WebSphereAS_Resource_Use
resource
model
goes
into
the
″Failing
54″
state
if
the
server
log
root
is
no
longer
valid.
See
the
solution
for
the
″The
Resource
Use
resource
model
returns
Failing
54″
problem
in
this
table.
For
proxy
mode
z/OS
systems,
you
might
receive
this
error
if
no
activity
has
occurred
for
the
resource
model
during
the
monitoring
cycle.
See
“Proxy
mode
z/OS-related
resource
model
problem
determination”
on
page
26
for
more
details.
Chapter
3.
Problems
and
workarounds
21
Table
6.
Resource
model
problems
and
solutions
(continued)
Problem
Solution
The
IBM
Tivoli
Monitoring
engine
is
not
available.
Refer
to
the
IBM
Tivoli
Monitoring
documentation
for
additional
assistance.
1.
Verify
that
the
IBM
Tivoli
Monitoring
engine
is
not
available
by
using
the
wdmlseng
command
or
through
the
Web
Health
Console.
2.
For
Windows
endpoints:
a.
Open
the
Task
Manager
to
see
if
the
m12javaprovider.exe
process
is
running.
b.
If
it
is
not
running:
1)
From
a
command
window
on
the
Tivoli
management
region
server,
source
the
Tivoli
environment,
as
described
in
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure
Installation
and
Setup
Guide.
2)
Restart
the
engine
by
executing
the
following
command:
wdmcmd
-restart
-e
endpoint_name
where
endpoint_name
is
the
name
of
the
endpoint.
c.
If
it
is
running,
use
the
Task
Manager
to
end
the
m12javaprovider.exe
manually
and
then
restart
the
engine
as
described
above.
3.
For
UNIX
or
OS/400
endpoints:
a.
If
it
is
not
running:
From
a
command
window
on
the
Tivoli
management
region
server,
source
the
Tivoli
environment.
Restart
the
engine
by
executing
the
following
command:
wdmcmd
-restart
-e
endpoint_name
where
endpoint_name
is
the
name
of
the
endpoint.
b.
If
it
is
running:
1)
Stop
the
engine
by
executing
the
following
command:
wdmcmd
-stop
endpoint_name
2)
Restart
the
engine
as
described
above.
22
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
Table
6.
Resource
model
problems
and
solutions
(continued)
Problem
Solution
You
distribute
a
monitoring
profile
and
it
is
not
showing
up
on
the
Web
Health
Console.
Refer
to
the
IBM
Tivoli
Monitoring
documentation
for
additional
assistance.
Determine
if
the
distribution
was
interrupted
by
running
the
following
command:
wmdist
-I
repeatername
Note:
Running
this
command
clears
all
distributions.If
the
output
shows
that
the
distribution
was
interrupted,
you
can
clear
the
distribution
in
the
following
ways:
1.
Stop
the
gateway
on
which
the
repeater
resides
by
running
the
following
command:
wgateway
gateway_name
stop
where
gateway_name
is
the
name
of
the
gateway.
2.
Clear
the
repeater
by
running
the
following
command:
wmdist
-B
repeatername
If
this
is
not
successful,
use
the
following
commands
to
delete
temporary
files:
cd
’wtemp’
rm
./states/*
rm
./depot/*
3.
Restart
the
gateway/repeater
by
running
the
following
command:
wgateway
gateway_name
start
where
gateway_name
is
the
name
of
the
gateway.
4.
Redistribute
the
profile.
If
this
does
not
work,
use
the
List
Trace
Logs
task
to
determine
if
the
trace_WebSphereAS_Ilt.log
exists.
If
the
log
file
does
not
exist,
stop
the
IBM
Tivoli
Monitoring
engine
and
run
the
IBM
Tivoli
Monitoring
task
DMLinkJRE
as
specified
in
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure
Installation
and
Setup
Guide.
Restart
the
engine
If
the
trace_WebSphereAS_Ilt.log
file
exists,
view
the
contents
to
see
if
it
is
using
the
IBM
WebSphere
Application
Server
JRE.
You
see
a
″Not
Compiled″
status
for
a
resource
model
on
the
Web
health
Console.
On
a
Windows
endpoint,
this
occurs
when
you
do
not
have
Windows
Script
Host,
Version
5.6,
installed.
Run
the
cscript
command
from
the
command
prompt
to
verify
the
version
of
Windows
Script
Host.
If
it
is
not
Version
5.6,
you
can
download
it
from
the
Microsoft
Web
site.
Chapter
3.
Problems
and
workarounds
23
Table
6.
Resource
model
problems
and
solutions
(continued)
Problem
Solution
You
see
a
″Missed
PreReq″
status
for
a
resource
model
on
the
Web
health
Console.
OR
Resource
models
go
into
the
Error
state.
You
probably
have
not
run
the
DMLinkJRE
command.
Run
the
DMLinkJRE
command
as
specified
in
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure
Installation
and
Setup
Guide.
If
this
problem
occurs
after
the
resource
model
has
already
run
successfully,
restart
the
IBM
Tivoli
Monitoring
engine
on
the
endpoint.
You
can
restart
the
engine
from
the
Web
Health
Console
or
from
the
command
line
(with
the
wdmcdmd
restart
–e
<endpoint>
command).
For
Windows
systems,
you
can
use
the
IBM
Tivoli
Monitoring
wdmcheckprereq
-e
<endpoint>
command
to
verify
that
you
have
the
required
IBM
Tivoli
Monitoring
prerequisites
installed
A
resource
model
fails.
The
state
of
the
resource
model
is
″Error.″
Restart
the
IBM
Tivoli
Monitoring
engine
on
the
endpoint.
You
can
restart
the
engine
from
the
Web
Health
Console
or
from
the
command
line
(with
the
wdmcdmd
restart
–e
<endpoint>
command).
The
resource
models
write
trace
messages
in
one
of
the
following
files
on
the
endpoint:
v
For
UNIX:
$LCF_DATDIR/LCFNEW/AMW/log/trace_dmxengine.log
v
For
Windows:
%LCF_DATDIR%\LCFNEW\Tmw2k\Tmw2k.log
The
statements
preceding
the
resource
model
aborting
message
in
the
trace
file
should
contain
information
about
why
the
resource
model
failed.
For
more
information,
refer
to
the
IBM
Tivoli
Monitoring
User’s
Guide.
The
resource
model
status
alternates
between
″Failing
54″
and
″Running.″
When
the
IBM
WebSphere
administration
server
or
application
server
is
down,
no
performance
information
can
be
retrieved
for
that
resource,
so
the
resource
models
that
report
performance
information
report
″Failing
54.″
The
IBM
Tivoli
Monitoring
engine
will
automatically
retry
the
resource
model
every
three
minutes.
After
reporting
the
failure,
the
engine
returns
the
status
to
″Running″
on
the
Windows
platform.
The
status
will
alternate
between
″Running″
and
″Failing
54″
until
the
problem
is
resolved.
See
“Proxy
mode
z/OS-related
resource
model
problem
determination”
on
page
26
for
more
details.
See
the
solution
to
the
″You
receive
the
″Failing
54″
error
code
in
the
Web
Health
Console″
problem.
Non-key
attributes
in
the
events
sent
to
Tivoli
Enterprise
Console
do
not
reflect
the
current
values
as
displayed
in
the
IBM
Tivoli
Monitoring
Web
Health
Console.
Because
the
Web
Health
Console
displays
real-time
data
and
Tivoli
Enterprise
Console
provides
a
snapshot
of
the
data
at
the
time
the
event
was
generated,
it
is
possible
for
the
information
in
the
events
to
be
out
of
sync
with
the
information
displayed
on
the
Web
Health
Console.
24
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
Table
6.
Resource
model
problems
and
solutions
(continued)
Problem
Solution
The
IBM
WebSphere
administration
server
is
running
but
the
resource
model
says
it
is
down.
If
WebSphere
security
is
enabled,
verify
that
the
properties
file
was
specified
when
the
WSAdministrationServer
was
created.
If
you
see
ConnectionLost
exceptions
and
WebSphere
security
is
enabled,
execute
the
wwebsphere
-g
command
to
determine
if
WebSphere
Security
Enabled
is
TRUE
and
the
WebSphere
Security
Properties
File
is
correctly
identified.
If
this
is
wrong,
you
must
unsubscribe
the
objects,
delete
them
and
recreate
them
with
the
correct
information.
Note:
This
applies
only
to
IBM
WebSphere
Application
Server
versions
3
and
4.
You
receive
the
″Failing
160″
error
code
in
the
Web
Health
Console
or
in
the
output
from
the
wdmlseng
command.
WebSphereAS_Transactions_10
Resource
model
should
not
be
used
to
monitor
IBM
WebSphere
Application
Server
3.5.6
systems
since
transaction
metrics
are
not
supported
by
IBM
WebSphere
Application
Server
3.5.6.
If
only
IBM
WebSphere
Application
Servers
3.5.6
application
servers
are
subscribed
to
the
profile,
the
resource
model
should
be
deleted
from
the
profile
and
the
profile
redistributed.
Otherwise,
the
message
can
be
ignored.
This
message
is
also
generated
by
the
WebSphereAS_DynamicCache
resource
model
if
it
is
distributed
to
any
version
of
IBM
WebSphere
Application
Server
prior
to
version
5.
You
receive
the
″150″
error
code
in
the
Web
Health
Console
or
in
the
output
from
the
wdmlseng
command.
The
WebSphereAS_ApplicationServerStatus
resource
model
returns
the
150
error
code
if
it
is
distributed
to
the
wrong
type
of
object,
such
as
an
administration
server.
You
receive
the
″151″
error
code
in
the
Web
Health
Console
or
in
the
output
from
the
wdmlseng
command.
The
WebSphereAS_AdministrationServerStatus
resource
model
returns
the
151
error
code
if
it
is
distributed
to
the
wrong
type
of
object,
such
as
an
application
server.
Chapter
3.
Problems
and
workarounds
25
Table
6.
Resource
model
problems
and
solutions
(continued)
Problem
Solution
The
Resource
Use
resource
model
returns
Failing
54.
The
Resource
Use
resource
model
uses
information
found
in
the
application
server
logfile
directory.
This
logfile
is
saved
as
an
attribute
for
the
server
object.
If
the
value
is
not
set
or
is
incorrect,
the
resource
model
does
not
run
properly.
For
IBM
WebSphere
Application
Server
versions
3.5
and
4,
if
the
object
was
created
prior
to
the
installation
of
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
5.1.2
or
was
created
using
the
GUI
or
command
line,
run
the
following
script
to
set
the
logfile
directory
attribute
for
the
object:
$BINDIR/../generic_unix/TME/WSAPPSVR/tasks/
itmwas_set_serverlogroot.sh
<app_server_label>
<log_install_dir>/tracefile
where
<app_server_label>
is
the
label
for
the
application
server
and
<log_install_dir>
is
the
installation
directory.
You
must
include
″tracefile″
in
this
path.
For
IBM
WebSphere
Application
Server
version
5,
if
the
value
determined
by
the
discovery
process
or
input
from
the
user
was
incorrect,
you
can
use
the
same
script
to
update
the
logfile
location.
The
resource
model
uses
the
<server>.pid
file.
Use
the
following
command
to
update
the
logfile
location:
$BINDIR/../generic_unix/TME/WSAPPSVR/tasks/
itmwas_set_serverlogroot.sh
<app_server_label>
<log_install_dir>/AppServer/logs/<server>
where
<server>
is
the
name
of
the
server.
Messages
for
resource
models,
such
as
Tivoli
Enterprise
Console
events,
appear
in
English,
even
though
non-English
language
packs
are
installed.
Use
the
wdmrm
-addcat
command
to
apply
language
pack
message
catalogs
to
resource
models.
See
the
IBM
Tivoli
Monitoring
documentation
for
more
information
about
running
this
command.
For
information
about
the
resource
model
error
codes
reported
in
the
IBM
Tivoli
Monitoring
Web
Health
Console,
see
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure
Reference
Guide.
Proxy
mode
z/OS-related
resource
model
problem
determination
In
addition
to
the
problems
listed
above,
resource
models
running
against
proxy
mode
z/OS
systems
might
encounter
additional
problems
related
to
the
acquisition
of
monitoring
data.
This
section
provides
additional
information
for
debugging
resource
model
problems.
To
determine
the
cause
of
a
problem
that
affects
the
acquisition
of
data
(such
as
″Failing
54″
or
″ERROR″
codes),
verify
that
the
communication
paths
between
the
IBM
WebSphere
Application
Server
system
on
the
proxy
mode
z/OS
system
and
the
proxy
endpoint
are
properly
configured.
Several
log
and
trace
files
are
referred
to
throughout
this
section,
such
as
a
resource
model
log
file
trace_dmxengine.log.
For
information
about
these
files,
see
“Log
file
information”
on
page
50.
26
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
Proxy
mode
z/OS
status
resource
model
problem
determination
If
you
experience
problems
with
status-related
resource
models
(such
as
WebSphereAS
Administration
Server
Status)
running
against
proxy
mode
z/OS
systems,
check
the
following
things:
v
Ensure
that
the
IBM
WebSphere
administration
server
is
running.
To
verify
that
the
administration
server
is
running
on
the
proxy
mode
z/OS
system,
perform
the
following
steps:
–
Confirm
that
the
IBM
WebSphere
Application
Server
daemons
are
running
by
running
the
following
command
from
the
z/OS
operator’s
console:
d
a,l
In
the
list
of
daemons,
look
for
the
four
IBM
WebSphere
Application
Server
daemons:
DAEMON01,
INTFRP01,
NAMING01,
and
SYSMGT01.
Note:
These
are
the
default
daemon
names.
These
names
might
be
different
for
your
installation.
–
Confirm
that
the
Workload
Manager
is
permitting
the
server
to
start
by
running
the
following
command:
d
wlm,applenv=*
Check
the
status
for
CBINTFRP,
CBNAMING,
and
CBSYSMGT.v
Ensure
that
the
NETCONV
session
is
active
and
properly
configured:
1.
Perform
the
following
steps
on
the
endpoint:
a.
View
the
ILT
log
and
look
for
any
IZY
messages
that
indicate
an
error.
b.
From
a
Tivoli
command
prompt,
change
to
$BINDIR/TDS/EventService/bin
and
run
the
following
commands:
Note:
If
the
endpoint
is
a
Windows
system,
you
must
first
invoke
the
bash
shell../hostcmdoper
-s
/hostcmd
"MVS
d
a,l"
/hostcmd
"netvasis
pipe
unix
hostname
|
corrwait
15
|
console"
netstat
If
you
see
any
of
the
following,
see
“NetView-related
resource
model
problems”
on
page
30:
–
An
IZY
message
in
the
ILT
log
file
–
No
operators
show
up
after
you
run
the
hostcmdoper
function
–
Listed
operators
are
not
authorized
user
IDs
(for
NetView,
OMVS,
and
IBM
WebSphere
Application
Server
administrators)
–
The
hostcmd
command
returns
an
error
–
cnmenuix
does
not
appear
in
the
list
of
active
jobs
–
An
established
connection
does
exist
to
the
proxy
mode
z/OS
system
on
port
40202.
Perform
the
following
steps
on
the
proxy
mode
z/OS
system:
–
Determine
if
the
NETCONV
session
is
running
by
running
the
following
command
from
a
NetView
operator:
netconv
action=list
opid=all
Chapter
3.
Problems
and
workarounds
27
You
should
see
a
line
of
output
that
indicates
that
the
proxy
mode
z/OS
system
is
communicating
with
the
endpoint.
If
you
do
not
see
this
line,
see
“NetView-related
resource
model
problems”
on
page
30.
–
Look
for
error
messages
on
the
z/OS
operator
console
related
to
cnmeunix.
Proxy
mode
z/OS
non-status
resource
model
problem
determination
If
you
experience
problems
with
non-status-related
resource
models
(such
as
WebSphereAS
EJB)
running
against
proxy
mode
z/OS
systems,
check
the
following
things:
v
Ensure
that
the
IBM
WebSphere
application
server
is
running.
The
application
server
must
be
running
in
order
to
collect
performance
metrics.
To
verify
that
the
application
server
is
running
on
the
proxy
mode
z/OS
system,
perform
the
following
steps:
–
Confirm
that
the
Workload
Manager
is
permitting
the
server
to
start
by
running
the
following
command:
d
wlm,applenv=*
–
Check
the
application
server
instance’s
server
(such
as
BBOASR2S)
region
job
log
for
the
″open
for
business″
string
(produced
in
the
log
when
the
server
completes
its
initialization)
or
a
Java
error.
If
the
application
server
is
not
running,
see
“Application
server-related
resource
model
problems”
on
page
30.
v
Ensure
that
the
z/OS
Data
Collector
is
running,
collecting
data,
and
forwarding
that
data
to
the
endpoint.
The
Data
Collector
forwards
data
for
a
server
only
when
the
application
server
has
progressed
sufficiently
in
the
start
up
process.
To
verify
that
the
Data
Collector
is
running
and
connected
to
the
various
application
servers
and
endpoints,
perform
the
following
steps
on
the
proxy
mode
z/OS
system:
–
Confirm
that
the
Data
Collector
is
running
by
running
the
following
command
from
the
z/OS
operator’s
console:
d
a,l
A
list
of
jobs
is
displayed.
If
the
Data
Collector
was
started
from
the
JCL
or
as
a
started
task,
the
job
name
is
ITDSRV.
If
the
Data
Collector
was
started
in
OMVS,
the
job
name
is
the
ID
of
the
user
who
started
it
followed
by
a
two
digit
number.
–
Confirm
that
the
z/OS
Data
Collector
is
communicating
with
the
server
regions
by
running
the
following
command:
netstat
-P
<port>
where
<port>
is
the
number
of
the
port
specified
by
the
com.ibm.tivoli.ws390.collector.port
statement
in
the
itmwas.conf
configuration
file
in
the
/var/itmwas/cfg
directory.
The
default
port
is
31173.
You
should
see
a
line
that
contains
a
listen
state
on
the
local
socket
of
0.0.0.0..31173,
along
with
the
job
name
associated
with
the
program
that
is
using
the
socket.
For
each
application
server
that
is
running
and
that
has
completed
its
startup,
you
should
see
a
pair
of
lines
in
the
″established″
state.
If
you
run
the
netstat
command
again
after
5
minutes,
the
connection
number
shown
for
the
connection
should
remain
the
same.
28
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
–
Confirm
that
the
z/OS
Data
Collector
is
communicating
with
the
endpoint
by
running
the
following
command:
netstat
-P
<port>
where
<port>
is
the
number
of
the
port
specified
by
the
com.ibm.tivoli.ws390.endpoint.port
statement
in
the
itmwas.conf
configuration
file
in
the
/var/itmwas/cfg
directory.
The
default
port
is
31174.
When
resource
models
are
running
and
application
server
are
connected
to
the
Data
Collector,
a
connection
exists
to
the
endpoint
to
send
the
gathered
information.
If
you
run
the
netstat
command
again
after
5
minutes,
the
connection
number
shown
for
the
connection
should
remain
the
same.
–
Confirm
that
the
endpoint
is
listening
on
the
proper
port
for
communication
from
the
proxy
mode
z/OS
system
by
running
the
netstat
command.
You
should
see
a
line
in
listen
state
related
to
the
port
specified
by
the
com.ibm.tivoli.ws390.endpoint.port
statement
in
the
itmwas.conf
configuration
file
in
the
$LCF_DATDIR/LCFNEW/Tmw2k/Unix/Classes/WebSphereAS
directory.
The
default
port
is
31174.
–
View
the
z/OS
Data
Collector
log
file
on
the
proxy
mode
z/OS
system
and
look
for
any
ERROR
log
entries.
If
the
z/OS
Data
Collector
is
not
running,
not
connected
to
the
application
servers
and
the
endpoint,
or
continuously
obtaining
new
connections
to
the
application
servers
or
endpoint,
see
“Proxy
mode
z/OS
Data
Collector-related
resource
model
problems”
on
page
31.
v
Ensure
that
endpoint-related
resource
models
are
running
and
properly
configured.
Check
the
following
things:
–
If
the
endpoint
is
on
a
Windows
system
and
the
resource
model
status
shows
″ERROR,″
check
the
resource
model
log
file
for
error
40004.
For
example:
Warning:
Unexpected
code
is
been
returned
by
WMI
during
enumerating
unsorted
instancies
of
the
class
WebSphereAS_ApplicationServer_11,
alias
of
CIM
class
Servlet_11,
model
WebSphereAS_WebApps_10,
return
code
40004
–
Verify
that
there
are
no
ERRORs
listed
in
the
ILT
log
file.
–
Verify
that
there
are
no
problems
in
the
resource
model
log
file.
–
If
the
endpoint
is
on
a
Windows
system,
verify
in
the
Windows
Task
Manager
(on
the
Process
tab)
that
the
m12JavaProvider
is
running
continuously
using
the
same
PID.
The
PID
value
should
remain
the
same
over
the
course
of
the
shortest
cycle
time
of
the
running
resource
models.
If
endpoint
problems
are
indicated,
see
“Endpoint-related
resource
model
problems”
on
page
33.
Administration
server-related
resource
model
problems
The
following
table
lists
potential
IBM
WebSphere
administration
server–related
resource
model
problems
and
solutions:
Table
7.
Proxy
mode
z/OS
resource
model
problems
related
to
the
IBM
WebSphere
administration
server
Problem
Solution
The
administration
server
is
not
running.
The
server
must
be
running
for
the
resource
models
to
obtain
status
data
about
associated
application
servers.
Restart
the
administration
server.
Chapter
3.
Problems
and
workarounds
29
Table
7.
Proxy
mode
z/OS
resource
model
problems
related
to
the
IBM
WebSphere
administration
server
(continued)
Problem
Solution
The
administration
server
is
not
running
on
the
primary
proxy
mode
z/OS
system
through
which
resources
are
being
monitored.
The
resource
models
connect,
using
NETCONV,
to
a
single
proxy
mode
z/OS
system
where
IBM
WebSphere
Application
Server
APIs
are
used
to
obtain
data.
If
the
administration
server
on
this
proxy
mode
z/OS
system
is
not
running,
all
administration
server
appear
to
be
down
or
in
a
″Failing
54″
state
and
associated
application
servers
have
a
status
of
″Unknown.″
Restart
the
administration
server.
The
administration
server
does
not
start
and
the
Workload
Manager
shows
that
the
server
is
stopped.
If
the
administration
server
was
stopped
by
the
Workload
Manager
because
of
a
recurring
error
that
is
now
fixed,
use
the
Workload
Manager
v
wlm,applenv=<server_name>,resume
command
to
permit
the
server
to
come
up.
NetView-related
resource
model
problems
The
following
table
lists
potential
NetView–related
resource
model
problems
and
solutions:
Table
8.
Proxy
mode
z/OS
resource
model
problems
related
to
NetView
Problem
Solution
An
IZY
error
message
appears
in
the
ILT
log
file.
See
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure
Reference
Guide
for
a
description
of
the
error
and
the
steps
to
take
to
resolve
the
problem.
NetView
operators
are
not
defined
on
the
endpoint.
Define
the
NetView
operator.
See
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure
Installation
and
Setup
Guide
for
information.
An
unauthorized
operator
ID
is
listed.
Give
the
operator
the
required
authorization.
See
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure
Installation
and
Setup
Guide
for
information.
cnmeunix
is
not
running
From
the
NetView
login,
run
the
following
command:
start
unixserv=*
NETCONV
is
not
communicating
with
the
endpoint
or
netstat
does
not
show
an
established
connection.
Start
communication
between
the
task
server
and
the
proxy
mode
z/OS
system.
See
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure
Installation
and
Setup
Guide
for
information.
An
error
occurred
on
the
hostcmd
function.
See
the
Tivoli
Business
Systems
Management
product
documentation
for
information
about
the
″IHSxxxx″
messages.
BPXI040I
messages
related
to
the
cnmeunix
job
appear
on
the
z/OS
operator
console.
NetView
is
receiving
status
queries
at
too
high
of
a
rate.
Existing
cnmeunix
processes
are
not
able
to
keep
up
with
the
requests
and
will
start
to
cause
Failing
54
errors
in
the
resource
models.
Change
the
cycle
time
for
the
administration
server
and
application
server
status
resource
models.
Application
server-related
resource
model
problems
The
following
table
lists
potential
IBM
WebSphere
application
server–related
resource
model
problems
and
solutions:
30
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
Table
9.
Proxy
mode
z/OS
resource
model
problems
related
to
the
IBM
WebSphere
application
server
Problem
Solution
Java
errors
appear
in
the
log
file
Verify
that
the
correct
level
of
Java
is
installed.
If
it
is
not,
install
the
correct
level
and
restart
the
application
servers.
Verify
the
configuration
statements
added
for
this
product
to
the
application
server’s
configuration.
If
they
are
not
correct
then
correct
them
by
running
the
/usr/lpp/itmwas/V5R1M1/scripts/itmwasAppServerUpdate
script
and/or
using
the
IBM
WebSphere
for
proxy
mode
z/OS
Administration
client.
The
application
server
does
not
start
and
the
Workload
Manager
shows
that
the
server
is
stopped.
If
the
application
server
was
stopped
by
the
Workload
Manager
because
of
a
recurring
error
that
is
now
fixed,
use
the
Workload
Manager
v
wlm,applenv=<server_name>,resume
command
to
permit
the
server
to
come
up.
Verify
that
the
correct
version
and
service
level
of
IBM
WebSphere
Application
Server
is
installed.
If
it
is
not,
install
the
correct
version
and
service
level.
Proxy
mode
z/OS
Data
Collector-related
resource
model
problems
The
following
table
lists
potential
z/OS
Data
Collector–related
resource
model
problems
and
solutions:
Table
10.
Proxy
mode
z/OS
resource
model
problems
related
to
the
Data
Collector
Problem
Solution
The
z/OS
Data
Collector
is
not
started.
If
the
z/OS
Data
Collector
was
never
started,
start
it.
If
the
z/OS
Data
Collector
was
started
from
JCL,
verify
in
the
job
log
that
the
JCL
was
properly
tailored
for
the
system.
If
JCL
is
not
correct,
correct
it
and
restart
the
collector.
Look
in
the
z/OS
Data
Collector
log
file
and
verify
that
no
Java
errors
occurred.
Specifically,
look
for
errors
related
to
the
Java
level
or
class
path
problems
caused
by
incorrectly
tailoring
the
collectorStart
script
or
the
JCL.
If
they
are
not
correct,
correct
them
and
restart
the
Data
Collector.
z/OS
Data
Collector
is
not
listening
on
the
specified
collector
port.
Verify
that
the
itmwas.conf
file
exists
in
the
/var/itmwas/cfg
directory.
If
it
does
not,
copy
the
file
from
the
/usr/lpp/itmwas/V5R1M1/etc
directory
and
tailor
it
for
the
system.
Refer
to
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure
Installation
and
Setup
Guide
for
more
information.
Verify
that
the
itmwas.conf
file
in
the
/var/itmwas/cfg
directory
is
accessible
to
the
z/OS
Data
Collector
with
the
correct
permissions
in
the
directory
and
for
the
file.
If
it
is
not
accessible,
correct
the
permissions
and
restart
the
Data
Collector
and
the
IBM
WebSphere
Application
Server
server
regions.
Verify
that
the
z/OS
Data
Collector
port
is
specified
by
the
com.ibm.tivoli.ws390.collector.port
statement
in
the
itmwas.conf
configuration
file
in
the
/var/itmwas/cfg
directory.
If
it
is
not
correct,
correct
it
and
restart
the
Data
Collector
and
the
application
servers.
Chapter
3.
Problems
and
workarounds
31
Table
10.
Proxy
mode
z/OS
resource
model
problems
related
to
the
Data
Collector
(continued)
Problem
Solution
z/OS
Data
Collector
is
listening
on
the
collector
port
but
application
servers
are
not
connected.
Verify
that
the
itmwas.conf
file
in
the
/var/itmwas/cfg
directory
is
accessible
to
the
Data
Collector
and
the
IBM
WebSphere
Application
Server
server
regions
with
the
correct
permissions
in
the
directory
and
for
the
file.
If
it
is
not
accessible,
correct
the
permissions
and
restart
the
Data
Collector
and
the
application
servers.
On
a
sysplex,
verify
that
the
ITMWASSSK
file
exists
in
the
/var/itmwas
directory
on
the
systems
where
the
monitored
application
servers
are
running.
If
not,
copy
the
file
to
the
system
missing
the
file
with
adequate
permissions
and
restart
the
application
server
on
that
system.
An
application
server
continuously
connects
to
the
z/OS
Data
Collector
and
closes
the
connection.
If
you
applied
a
service
that
affects
the
z/OS
Data
Collector
while
a
related
application
server
is
running,
an
old
version
of
a
code
is
being
used
to
communicate
with
the
z/OS
Data
Collector.
The
connection
is
being
severed
because
the
error
is
detected.
Restart
the
application
server.
z/OS
Data
Collector
is
not
connected
to
the
endpoint
on
the
endpoint
port.
Verify
that
the
itmwas.conf
file
in
the
/var/itmwas/cfg
directory
is
accessible
to
the
z/OS
Data
Collector
with
the
correct
permissions
in
the
directory
and
for
the
file.
If
it
is
not
accessible,
correct
the
permissions
and
restart
the
Data
Collector
and
the
IBM
WebSphere
Application
Server
server
regions.
Verify
that
the
endpoint
port
was
specified
on
the
com.ibm.tivoli.ws390.endpoint.port
statement
in
the
itmwas.conf
configuration
file
in
the
/var/itmwas/cfg
directory.
If
it
is
not
correct,
correct
it
and
restart
the
Data
Collector.
Verify
that
the
endpoint
host
name
was
correctly
specified
com.ibm.tivoli.ws390.endpoint.hostname
statement
in
the
itmwas.conf
configuration
file
in
the
/var/itmwas/cfg
directory.
If
it
is
not
correct,
correct
it
and
restart
the
Data
Collector.
Verify
that
the
endpoint
listening
port
was
correctly
specified
in
the
com.ibm.tivoli.ws390.endpoint.port
statement
on
the
itmwas.conf
configuration
file
in
the
$LCF_DATDIR/LCFNEW/Tmw2k/Unix/Classes/WebSphereAS
directory
on
the
endpoint.
If
it
is
not
correct,
correct
it
and
restart
the
endpoint.
On
the
endpoint,
view
the
ILT
log
file
and
look
for
log
entries
related
to
jsse
or
SSL.
If
log
entries
exist,
verify
that
the
correct
Java
JRE
is
linked
using
DMLinkJRE.
The
JRE
directories
should
not
contain
ibmjsse.jar
or
ibmjceprovider.jar.
If
these
files
exist
in
the
JRE,
consult
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure
Installation
and
Setup
Guide
for
the
correct
linking
of
the
Java
JRE.
Verify
that
proxy
mode
z/OS-related
resource
models
are
running
on
the
endpoint
using
wdmlseng
–e
<endpoint_name>
command.
The
z/OS
Data
Collector
cannot
connect
to
the
endpoint
if
the
proxy
mode
z/OS
related
resource
models
are
not
running.
If
resource
models
are
not
running
due
to
an
error,
see
the
“Endpoint-related
resource
model
problems”
on
page
33.
32
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
Table
10.
Proxy
mode
z/OS
resource
model
problems
related
to
the
Data
Collector
(continued)
Problem
Solution
z/OS
Data
Collector
continuously
connects
to
endpoint
and
closes
the
connection.
The
updated
on
the
systems
might
not
have
completed
correctly.
Update
the
two
systems.
On
the
endpoint,
verify
that
the
ITMWASSSK
file
exists
in
the
$LCF_DATDIR
directory.
If
not,
run
the
Discover_WebSphere_Resources
task
or
the
Check_Adminstration_Server_Status
task
against
the
Administration
Server
object,
or
copy
the
file
to
the
endpoint
from
the
/var/itmwas
directory
to
the
$LCF_DATDIR
directory.
This
file
must
be
transferred
as
an
ASCII
file
so
that
its
contents
are
appropriate
for
the
code
page
of
the
endpoint.
If
the
file
does
not
exist
on
the
proxy
mode
z/OS
system,
make
sure
it
does
not
exist
on
the
endpoint
system
either,
then
run
the
Discover_WebSphere_Resources
task
or
the
Check_Adminstration_Server_Status
task
against
the
Administration
Server
object.
Endpoint-related
resource
model
problems
The
following
table
lists
potential
endpoint–related
resource
model
problems
and
solutions:
Table
11.
Proxy
mode
z/OS
resource
model
problems
related
to
the
endpoint
Problem
Solution
Resource
model
log
file
shows
error
40004
The
m12JavaProvider
process
is
detecting
that
the
ILT
is
taking
too
long
to
respond.
The
z/OS
ILT
can
take
up
to
10
minutes
for
the
initial
response
depending
upon
system
load.
Increase
the
WMI
timeout
in
Windows
registry
by
adding
or
increasing
the
size
of
the
DWORD
key
″EnumInstWMITimeOut″
at
the
location
HKEY_LOCAL_MACHINE\SOFTWARE\Tivoli\Tmw,
specifying
a
value
of
600000
for
the
timeout
to
be
used
for
any
WMI
instances
enumeration.
m12JavaProvider
PID
value
is
changing.
The
m12JavaProvider
process
is
detecting
that
the
resource
models
are
not
requesting
data
within
a
timeout
interval
(default
100
seconds).
The
m12JavaProvider
is
being
stopped
until
the
resource
model
contacts
it
at
the
next
cycle
time.
The
z/OS
ILT
saves
state
related
data
under
the
m12JavaProvider
process.
Either
run
a
resource
model
(e.g.
JVM
Runtime)
with
a
shorter
cycle
time
than
the
current
timeout
interval
to
prevent
the
timeout
or
increase
the
timeout
interval
in
the
Windows
registry
by
adding
or
increasing
the
size
of
the
DWORD
key
″m12TimeOut″
at
the
location
HKEY_LOCAL_MACHINE\SOFTWARE\Tivoli\Tmw,
specifying
a
value
of
in
milliseconds
that
is
greater
than
the
shortest
resource
model
cycle
time.
Chapter
3.
Problems
and
workarounds
33
Table
11.
Proxy
mode
z/OS
resource
model
problems
related
to
the
endpoint
(continued)
Problem
Solution
ILT
log
shows
Severity=″ERROR″
log
entries.
If
the
log
entry
is
an
exception
and
the
exception
is
″java.util.NoSuchElementException″
or
the
stack
trace
shown
in
the
log
entry
includes
″GetMetrics,″
a
proxy
mode
z/OS
resource
model
has
been
built
and
distributed
to
a
non-z/OS
object.
Distribute
the
resource
model
to
the
correct
object
type.
If
the
log
has
an
entry
with
message
ITD00300F,
a
subsequent
log
entry
will
show
an
exception.
If
the
exception
states
that
the
socket
name
is
already
in
use,
another
program
is
using
the
port
that
the
endpoint
is
configured
to
listen
for
communication
from
the
z/OS
Data
Collector.
One
cause
of
this
is
running
more
than
one
copy
of
the
DMEngine
at
a
time.
Either
stop
the
other
program
or
change
the
port
specified
in
the
com.ibm.tivoli.ws390.endpoint.port
statement
on
the
itmwas.conf
configuration
file
in
the
$LCF_DATDIR/LCFNEW/Tmw2k/Unix/Classes/WebSphereAS
directory
on
the
endpoint.
The
surrounding
log
entries
should
indicate
the
cause
of
the
problem;
correct
the
problem.
Tasks
problem
determination
The
following
table
lists
general
task
problems
that
might
occur.
Table
12.
Task
problems
and
solutions
Problem
Solution
When
running
a
task
against
an
object,
you
receive
the
following
type
of
error:
wscp.bat
command
not
found.
This
is
an
example
of
the
error
that
is
displayed
for
Windows
systems.
Ensure
that
the
right
type
of
object
was
created.
For
example,
if
you
create
a
WSApplicationServer
object
to
represent
an
IBM
WebSphere
Application
Server
Version
5
application
server,
you
cannot
run
tasks
against
it.
You
must
create
the
correct
Tivoli
object
to
represent
your
IBM
WebSphere
Application
Server
resources.
For
this
example,
you
must
create
an
IWSApplicationServer
object.
Delete
the
existing
object
and
create
a
new
object
for
the
resource.
For
more
information
about
creating
objects,
see
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
User’s
Guide.
34
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
Table
12.
Task
problems
and
solutions
(continued)
Problem
Solution
When
a
task
fails,
you
might
receive
the
following
error:
endpoint_name(Endpoint):
The
task
failed
to
execute.
endpoint_name(Endpoint):
Insufficient
roles
for
executing
the
task
on
endpoint_name
endpoint.
You
might
also
receive
a
message
that
states
that
you
have
no
permission.
The
following
message
is
an
example
of
the
message
received
if
you
try
to
run
the
Discover_WebSphere_Resources
task
without
sufficient
permission:
bn3c4(ManagedNode):
The
task
failed
to
execute.
bn3c4(ManagedNode):
no
permission
for
’WebSphere
Application
Server
Utility
Tasks/Discover
WebSphere
Resources’
for
operation
of
’run_task’
Ensure
that
you
assigned
the
resource
roles
to
the
administrator
running
the
task.
See
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
User’s
Guide
for
more
information.
After
you
assign
the
resource
roles,
immediately
stop
and
start
the
Tivoli
desktop
so
the
assigned
roles
take
effect.
The
List_Trace_Logs
task,
when
run
from
the
Tivoli
desktop,
displays
the
contents
of
the
new
log
created
by
the
task
rather
than
the
log
for
the
endpoint
or
managed
node
that
you
have
selected.
Note:
This
applies
only
to
the
trace_itmwas_list_was_trace_logs_<number>.log
on
the
endpoint.
On
the
managed
node,
this
problem
occurs
with
the
following
log
files:
v
trace_waspac_tivoli_lobs_cb_<number>.log
v
trace_waspac_admin_cb_<object_label>_<number>.log
None
The
Administration
server
does
not
stop
after
running
the
Stop_Administration_Server
task
immediately
after
starting
the
server.
IBM
WebSphere
Application
Server
uses
a
nanny
process
to
ensure
that
the
Administration
server
successfully
starts.
If
you
start
the
Administration
server
and
then
stop
it
using
a
task,
the
Administration
server
might
not
stop.
To
stop
the
Administration
server
soon
after
starting
it,
you
must
wait
several
minutes
to
ensure
that
the
nanny
process
completes.
Then
you
can
stop
the
Administration
server.
If
you
have
a
Windows
Tivoli
management
region
server
and
HP-UX
or
Solaris
endpoints,
when
you
run
administration
tasks
from
the
GUI,
you
might
see
an
error
″Could
not
set
locale
correctly″
in
the
stderr
section
of
the
output.
Set
the
following
environment
variable
on
your
Windows
Tivoli
management
region
server:
LANG=C.
After
you
set
the
environment
variable,
stop
and
restart
your
Tivoli
desktop.
The
″C″
is
for
English.
If
you
have
a
different
locale
setting,
this
might
not
fix
the
problem.
See
the
Tivoli
Management
Framework
documentation
for
more
information.
When
running
application
server
tasks,
you
receive
a
message
saying
the
IBM
WebSphere
administration
server
isn’t
running
even
though
it
is.
This
problem
might
occur
if
you
are
using
a
non-default
port,
with
or
without
WebSphere
security
enabled.
Check
the
sas.wscp.props
file
and
ensure
that
the
following
line
is
present:
wscp.hostPort=<port>
See
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
User’s
Guide
for
more
information.
Note:
This
problem
only
applies
to
IBM
WebSphere
Application
Server
versions
3.5
and
4.
Chapter
3.
Problems
and
workarounds
35
Table
12.
Task
problems
and
solutions
(continued)
Problem
Solution
You
might
see
a
file
sharing
violation
when
trying
to
delete
the
trace_WebSphereAS_Iltx.log
files
in
the
$LCF_DATDIR/LCFNEW/IZY/LOGS
directory.
This
occurs
if
the
IBM
Tivoli
Monitoring
engine
is
still
running
while
you
try
to
delete
the
files.
You
must
stop
or
kill
the
engine
before
deleting
the
log
files.
On
Windows:
1.
From
the
Tivoli
management
region
server,
issue
the
following
command:
wdmcmd
-stop
e
endpoint_name
where
endpoint_name
is
the
name
of
the
endpoint
where
you
are
trying
delete
log
files.
2.
On
the
endpoint,
open
an
MS-DOS
prompt
and
issue
the
following
command:
net
stop
winmgmt
3.
On
the
endpoint,
open
the
Task
Manager.
If
you
still
see
the
m12javaprovider
process
running
in
the
Task
Manager,
then
end
the
process
manually.
On
UNIX:
1.
Issue
the
following
command:
wdmcmd
-stop
-e
endpoint_name
where
endpoint_name
is
the
name
of
the
endpoint
where
you
want
to
delete
log
files.
2.
Run
the
following
command
to
see
if
the
IBM
Tivoli
Monitoring
engine
is
still
running:
ps
-ef
|
grep
dmunix
3.
If
the
engine
is
still
running,
stop
it
manually.
Once
the
IBM
Tivoli
Monitoring
engine
is
stopped,
you
can
delete
the
trace_WebSphereAS_Iltx.log
files.
Then,
restart
the
IBM
Tivoli
Monitoring
engine.
You
might
see
a
file
sharing
violation
when
trying
to
delete
the
trace_WebSphereAS_tecAdapter.log
file
in
the
$LCF_DATDIR/LCFNEW/IZY/logs
directory.
This
occurs
if
the
IBM
WebSphere
Application
Server
Tivoli
Enterprise
Console
adapter
is
running
while
messages
are
being
sent
to
the
file.
You
must
stop
the
IBM
WebSphere
Application
Server
Tivoli
Enterprise
Console
adapter
before
deleting
the
file.
Run
the
Stop_WebSphere_TEC_Adapter
task
against
the
server
machine
that
contains
the
log
file.
Delete
the
log
file.
Restart
the
adapter
by
running
the
Start_WebSphere_TEC_Adapter
task.
36
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
Table
12.
Task
problems
and
solutions
(continued)
Problem
Solution
You
receive
the
following
error
when
running
a
task:
ctv07067
(ManagedNode):
The
task
failed
to
execute.
ctv07067
(ManagedNode):
FRWTD0026E
The
task
failed
to
complete
execution
before
the
timeout
period
expired.
The
task
might
have
completed
successfully,
but
the
timeout
value
was
insufficient.
To
see
the
output
of
the
task
displayed
upon
task
completion,
increase
the
timeout
value
for
the
task
and
run
the
task
again.
If
the
systems
where
your
servers
are
running
are
slow,
you
might
need
to
increase
the
timeout
execution
parameter
for
some
of
the
tasks.
The
default
timeout
for
tasks
is
set
to
60
seconds.
You
can
change
this
default
value
on
the
Execute
Task
window.
For
tasks
initiated
from
server
icons,
the
default
timeout
is
the
timeout
for
the
gateway.
To
change
the
default
timeout
at
the
gateway,
use
the
following
command:
wgateway
<gateway_name>
set_session_timeout
<timeout>
where
<gateway_name>
is
the
name
of
the
gateway,
and
<timeout>
is
the
new
timeout
value,
such
as
900.
Operational
tasks
started
from
the
Tivoli
Business
Systems
Manager
console
fail
on
Tivoli
Management
Framework
Version
4.1.
The
Tivoli
Management
Framework
remote
client
login
is
set
to
″version_2.″
Run
the
following
command
on
the
managed
node
to
resolve
this
problem:
odadmin
set_allow_rconnect
TRUE
1
When
you
run
the
DMLinkJre
task
and
link
to
the
IBM
WebSphere
JRE,
you
might
receive
the
following
message:
Warning:
Uncertified
JRE
build
version
Use
the
DMLinkJRE
task
to
link
to
the
JRE
supplied
by
IBM
Tivoli
Monitoring.
See
the
IBM
Tivoli
Monitoring
documentation
for
information.
Discover_WebSphere_Resources
task
problem
determination
The
following
table
lists
problems
that
might
occur
when
you
run
the
Discover_WebSphere_Resources
task.
Chapter
3.
Problems
and
workarounds
37
Table
13.
Discover_WebSphere_Resources
task
problems
and
solutions
Point
of
Failure
Problem
Solution
Managed
node
The
Discover_WebSphere_Resources
task
fails
with
the
following
message:
IZY1143I
The
Discover
WebSphere
Resources
task
will
stop
because
no
endpoints
were
selected.
You
must
specify
endpoints
on
which
to
run
the
Discover_WebSphere_Resources
task.
See
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
User’s
Guide
for
more
information.
Running
the
Discover_WebSphere_Resources
task
from
the
command
line
fails
with
the
following
message:
IZY1143I
The
Discover
WebSphere
Resources
task
will
stop
because
no
endpoints
were
selected.
even
though
you
specified
endpoints
for
the
task.
Ensure
that
the
path
names
you
supply
are
UNIX-style
names,
such
as
c:/WebSphere/AppServer
instead
of
c:\WebSphere\AppServer.
OSERV
error
Run
the
following
command
to
determine
whether
or
not
you
can
communicate
with
the
endpoint:
wadminep
<endpoint_name>
view_version
where
<endpoint_name>
is
the
name
of
the
endpoint.
Check
the
Tivoli
Management
Framework
endpoint
and
gateway
logs
for
more
information.
See
the
Tivoli
Management
Framework
Reference
Manual
for
information
about
these
logs.
38
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
Table
13.
Discover_WebSphere_Resources
task
problems
and
solutions
(continued)
Point
of
Failure
Problem
Solution
Endpoint
Discovery
did
not
subscribe
the
application
server
to
a
profile
manager.
Subscribe
the
application
server
to
the
appropriate
profile
manager.
You
receive
the
following
message:
IZY1159E
Endpoint
<endpoint>
will
not
be
discovered
due
to
failure
calling
dependency
init.
Ensure
that
your
gateway
is
running.
Run
the
following
command
to
determine
whether
or
not
you
can
communicate
with
the
endpoint:
wadminep
<endpoint_name>
view_version
where
<endpoint_name>
is
the
name
of
the
endpoint.
Check
the
gateway
to
ensure
that
the
code
is
installed
on
the
gateway:
v
Check
the
space
on
the
endpoint.
v
Check
the
permission
on
the
endpoint
directory
structure.
v
Check
the
$root_user
idmap
and
make
sure
that
the
user
is
valid
for
the
endpoint.
You
receive
the
following
message:
IZY1240E
Cannot
establish
a
connection
to
the
server
on
endpoint
<endpoint_name>
This
can
occur
when
the
application
server
or
deployment
manager
is
not
started
or
the
connector
port
is
incorrect.
The
targeted
process
is
identified
by
the
installation
path
and
the
connector
port
value.
If
the
targeted
process
is
the
primary
application
server
in
an
IBM
WebSphere
Application
Server
base
installation
(typically
server1),
verify
that
the
server
is
started.
If
the
server
has
a
non-default
SOAP
port
configured,
verify
that
the
correct
connector
port
is
being
specified.
If
the
targeted
process
is
the
deployment
manager
in
an
IBM
WebSphere
Application
Server
Network
Deployment
installation
(typically
dmgr),
verify
that
the
deployment
manager
is
started.
If
the
deployment
manager
is
configured
to
use
a
non-default
SOAP
port,
verify
that
the
correct
port
is
specified.
If
WebSphere
global
security
is
enabled
on
the
targeted
process,
ensure
that
the
provided
user
name
and
password
are
correct
for
the
targeted
process.
See
the
WebSphere
InfoCenter
for
additional
information
about
configuring
communication
with
a
secure
server.
You
receive
the
following
exception:
EXCEPTION
FRWSL0005E
A
communications
failure
occurred:
FRWOG0014E
destination
dispatcher
unavailable
Run
the
following
command
to
determine
whether
or
not
you
can
communicate
with
the
endpoint:
wadminep
<endpoint_name>
view_version
where
<endpoint_name>
is
the
name
of
the
endpoint.
Chapter
3.
Problems
and
workarounds
39
Table
13.
Discover_WebSphere_Resources
task
problems
and
solutions
(continued)
Point
of
Failure
Problem
Solution
Endpoint
(cont.)
Authorization
or
authentication
failed
When
discovering
an
IBM
WebSphere
Application
Server
version
3.5
or
4
endpoint,
be
sure
to
put
the
sas
properties
file
in
the
Security
Properties
File
field
of
the
Configure
Task
Parameters
window.
Ensure
that
the
IBM
WebSphere
administration
server
is
running.
For
IBM
WebSphere
Version
4,
verify
that
you
have
correctly
entered
the
user
name,
password,
and
login
source
(properties)
in
the
sas.wscp.props
file.
Verify
that
the
password
in
your
sas.wscp.props
file
is
plain
text,
not
encrypted.
See
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
User’s
Guide
for
more
information
about
the
sas.wscp.props
file.
For
IBM
WebSphere
Version
5,
the
user
name
and
password
are
part
of
the
object
that
is
stored
on
the
Tivoli
Management
Region
either
as
part
of
the
discovery
task
or
edited
through
the
update
function
for
the
object.
You
receive
the
following
message:
/tmp/aaaeUoaMa[##]:
./XMLConfigItmwas.sh:
not
found.
or
IZY1164E
Error
creating
WebSphere
XML
output.
Make
sure
the
adminserver
is
up
and
running.
If
WebSphere
global
security
is
enabled,
check
that
the
client
properties
file
specified
for
the
Discover
WebSphere
Resources
task
has
the
correct
entries
for
com.ibm.CORBA.loginUserid
and
com.ibm.CORBA.loginPasword.
See
log
file
for
details.
Check
the
installation
path
that
you
specified
for
the
IBM
WebSphere
Application
Server.
It
should
be
$WAS_HOME.
You
might
have
entered
a
valid
path,
but
it
is
not
the
$WAS_HOME
path.
Discover_WebSphere_Resources
worked
but
the
port
number
on
objects
is
not
correct.
If
your
system
PATH
is
set
with
$WAS_HOME,
the
Discover_WebSphere_Resources
task
will
work
if
you
entered
a
path
that
exists
on
the
endpoint
but
is
not
$WAS_HOME.
However,
the
objects
created
might
not
be
configured
correctly.
You
can
validate
the
WSAdministrationServer
and
WSApplicationServer
objects
created
for
the
endpoint
using
the
wwebsphere
-g
command.
Review
the
/trace_itmwas_discover_endpoint.log
file
in
the
$LCF_DATDIR/LCFNEW/IZY/logs
directory
to
be
sure
there
are
no
errors.
You
can
also
delete
the
created
objects
for
the
endpoint
and
rerun
the
Discover_WebSphere_Resources
task.
40
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
Table
13.
Discover_WebSphere_Resources
task
problems
and
solutions
(continued)
Point
of
Failure
Problem
Solution
Endpoint
(cont.)
Data
was
not
received
because
the
connection
timed
out.
net_recv:
timeout
(NNN
seconds)
waiting
to
receive
from
<ip_address>+<port>
Increase
the
gateway
timeout:
1.
Run
the
following
command
to
see
the
current
setting:
wgateway
<gateway_name>
2.
Run
the
following
command
to
increase
the
gateway
session
timeout:
wgateway
<gateway_name>
set_session_timeout
nn
The
task
processing
on
the
endpoint
is
taking
longer
to
complete
than
the
gateway
timeout.
The
task
will
complete,
but
you
will
not
see
the
results
in
the
output
window.
You
can
check
each
created
object
manually
with
the
wwebsphere
–g
command.
Review
the
/trace_itmwas_discover_endpoint.log
file
in
the
$LCF_DATDIR/LCFNEW/IZY/logs
directory
for
errors,
or
delete
the
created
objects
for
the
endpoint
and
rerun
the
Discover_WebSphere_Resources
task.
Tivoli
Enterprise
Console
problem
determination
The
following
table
contains
problems
that
might
occur
with
Tivoli
Enterprise
Console.
Table
14.
Tivoli
Enterprise
Console
problems
and
solutions
Problem
Solution
The
rolling
port
function
does
not
work
for
multiple
endpoint
connections.
If
you
are
running
a
Tivoli
Enterprise
Console
adapter
against
a
particular
object
(deployment
manager,
node
agent,
or
application
server)
on
a
given
port,
and
you
want
to
start
another
Tivoli
Enterprise
Console
adapter
on
the
same
endpoint
against
the
same
object,
you
must
explicitly
specify
a
port
other
than
the
one
being
used
by
the
adapter
already
running.
If
you
provide
the
same
port
that
is
used
by
a
running
Tivoli
Enterprise
Console
adapter,
you
will
receive
a
message
saying
that
the
adapter
is
already
running.
When
you
are
configuring
the
event
adapter,
entering
a
port
number
that
is
being
used
by
one
of
the
WebSphere
servers
might
cause
the
Tivoli
Enterprise
Console
adapter
to
hang.
Specify
a
port
that
is
currently
not
being
used.
You
receive
the
following
message:
IZY1125E
The
event
adapter
did
not
start
or
is
still
starting.
Possible
reasons
include:
1-
The
IBM
WebSphere
resource
is
not
running.
2
-
A
free
port
could
not
be
found
for
use.
3
-
The
Tivoli
endpoint
machine
may
be
experiencing
performance
problems
preventing
the
event
adapter
from
starting
in
a
timely
manner.
The
Tivoli
Enterprise
Console
adapter
might
have
started
but
didn’t
start
within
the
40
second
limit
the
Start
WebSphere
TEC
Adapter
task
waits.
Check
the
Tivoli
Enterprise
Console
to
see
if
the
TEC
Adapter
Started
event
was
sent
or
run
the
WebSphere_TEC_Adapter_Configuration
task
to
check
the
adapter
status.
You
see
PARSING_FAILED
for
fqhostname
when
issuing
a
wtdumprl
on
the
event
server.
The
Tmw2k.baroc
file
needs
to
be
updated
in
the
current
rule
base.
IBM
Tivoli
Monitoring
Fix
Pack
05
added
a
new
slot,
fqhostname.
Chapter
3.
Problems
and
workarounds
41
Table
14.
Tivoli
Enterprise
Console
problems
and
solutions
(continued)
Problem
Solution
Events
are
not
displayed
in
the
event
console.
Check
the
following:
v
Ensure
that
the
event
server
is
operational.
v
Ensure
the
configuration
for
the
Event
Server
host
name
and
port
are
correct.
v
Ensure
that
the
event
adapter
is
running.
v
Ensure
that
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
classes
and
rules
are
installed
and
configured
on
the
event
server.
1.
Run
the
wrb
–lscurrb
command
to
display
the
name
of
the
active
rule
base.
2.
Run
the
wrb
–lsrbclass
rulebase_name
command
to
list
the
defined
event
classes.
rulebase_name
is
the
name
of
the
current
active
rule
base,
returned
by
the
wrb
–lscurrb
command.
Ensure
that
the
ITMWAS_Event,
ITMWAS_TEC_Adapter_Event,
and
WebSphereAS_Monitor_Event
classes
are
defined.
3.
Run
the
wrb
–lsrbrules
rulebase_name
command
to
list
the
defined
rules.
Ensure
that
the
itmwas_events.rls
and
itmwas_monitor.rls
rule
set
files
are
defined.
4.
If
the
required
classes
or
rules
are
not
defined,
run
the
Configure
Event
Server
task
to
define
the
classes
and
rules.
v
Ensure
that
events
are
being
received
at
the
event
server.
To
do
this,
run
the
wtdumprl
command
on
the
event
server
to
display
the
events
in
the
reception
log
on
the
event
server.
v
The
events
are
being
received
at
the
event
server
but
have
a
parsing_failed
message.
This
occurs
if
you
have
not
run
the
Configure
Event
Server
task.
Run
the
task
to
load
the
definitions
for
the
IBM
WebSphere
Application
Server
events
into
the
event
server.
v
Ensure
that
the
IBM
Tivoli
Monitoring
profile
was
enabled
to
forward
events.
See
the
Tivoli
Enterprise
Console
Reference
Manual
for
information
about
the
commands
mentioned
above.
Tivoli
Enterprise
Data
Warehouse
problem
determination
The
following
table
contains
problems
that
might
occur
with
Tivoli
Enterprise
Data
Warehouse.
42
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
Table
15.
Tivoli
Enterprise
Data
Warehouse
problems
and
solutions
Problem
Solution
Data
is
not
rolled
into
the
TWH_CDW
database.
Error
messages
are
generated
when
running
the
IBM
Tivoli
Monitoring
Warehouse
Enablement
Pack
process.
The
following
error
messages
appear
in
the
ERROR_MSG
column
of
the
AMX.stage_inst_comp_pac_ex
exception
tables:
Some
keys
are
missing
for
this
comptyp_cd
Some
properties
used
for
the
comp_nm
are
missing
for
this
comptyp_cd
Note:
To
generate
these
tables,
run
the
List_AMX_exceptions
bat
file
in
the
$TWH_TOPDIR\apps\amx\v511\misc\tools
directory.
Data
logged
by
prior
versions
of
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
is
not
compatible
with
data
logged
by
version
5.1.2.
Any
data
collected
with
prior
versions
must
be
processed
by
the
prior
version’s
Warehouse
Enablement
Pack
before
you
install
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
Version
5.1.2
Warehouse
Enablement
Pack:
1.
Restore
the
previous
version
of
the
Warehouse
Enablement
Pack
by
uninstalling
the
fixpack_v1102.
2.
Run
the
IBM
Tivoli
Monitoring
Warehouse
Enablement
Pack
and
the
Version
5.1.1
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
Warehouse
Enablement
Pack
to
rollup
all
existing
information
in
the
operational
(RIM)
database.
3.
Reinstall
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
Version
5.1.2
Warehouse
Enablement
Pack.
Data
is
not
rolled
into
the
TWH_CDW
database
when
you
run
the
IBM
Tivoli
Monitoring
Warehouse
Enablement
Pack
process.
The
following
exceptions
are
generated:
In
the
AMX.STATE_INST_COMP_PAC_EX
exception
table,
for
the
WebShereASNode.Name
property:
Property
not
defined
for
that
PAC.
In
the
AMX.STAGE_CATERGORIES_EX
exception
table,
for
the
WebSphereASNode.PolicyRegion,
WebSphereASNode.OSType,
WebSphereASNode.WasVersion,
and
WebSphereASApplicationSErver.ClusterName
properties:
The
attribute
for
that
component
for
that
PAC
is
not
declared
in
the
metadata.
In
the
AMX.STAGE_METRICS_EX
exception
table,
for
the
Percent_CPU_Utilization,
Process_Size,
Average_JDBC_Response_Time,
Percent_Missed,
Session_Request_Errors,
and
Average_J2C_Use_Time
properties:
Metric
name
not
defined
for
that
PAC.
You
have
not
installed
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
Version
5.1.2
Warehouse
Enablement
Pack.
Install
this
Warehouse
Enablement
Pack
(fixpack_v1102)
and
its
prerequisites.
When
running
some
summary
reports,
you
receive
the
following
messages:
FWP1851E
java.lang.NullPointerException
and
CDWRP0035E
The
following
exception
occurred
during
report
table
creations:
null.
Apply
the
Tivoli
Enterprise
Data
Warehouse
fix
pack
1.1–TDW-0013LA
on
the
system
where
your
Tivoli
Enterprise
Data
Warehouse
reporting
interface
(RPI)
is
installed.
Chapter
3.
Problems
and
workarounds
43
Table
15.
Tivoli
Enterprise
Data
Warehouse
problems
and
solutions
(continued)
Problem
Solution
No
data
in
the
reports.
In
the
case
of
summary
reports,
the
report
is
empty
or
you
receive
the
following
message:
DWRB0022E
No
records
were
found
for
this
report.
This
occurs
when
there
is
no
data
in
the
IZY
Monitoring
for
WebSphere
Application
Server
data
mart
for
the
time
frame
specified
in
the
report.
This
can
be
caused
in
the
following
situations.
v
You
have
not
run
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
Warehouse
Enablement
Pack
processes.
See
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
Warehouse
Enablement
Guide.
v
You
have
not
installed
the
IBM
Tivoli
Monitoring,
Warehouse
Enabling
Pack
and
have
not
successfully
uploaded
data
to
the
central
data
warehouse.
See
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure
Installation
and
Setup
Guide.
v
No
data
is
being
collected
in
the
RIM
database.
–
Resource
model
logging
is
not
enabled.
See
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
User’s
Guide
for
information.
–
You
have
not
installed
and
configured
the
IBM
Tivoli
Monitoring
Tivoli
Enterprise
Data
Warehouse
support
on
the
Tivoli
management
region
server.
See
the
IBM
Tivoli
Monitoring
User’s
Guide
You
see
the
following
error
in
the
TWHApp.log
file:
(F)
CDWIC0022E
Failure
detected
during
SQL
script
executionfor
Database
(TWH_MART).
Return
code
was
(4)
Check
messages
in
DB2
log
(twh_ibm_db2_runlog.log),
Removing
TMP
script.
Exiting...
And
the
following
error
in
the
twh_ibm_db2_runlog.log
file:
DECLARE
global
temporary
TABLE
Prune_Mart_Control(
Table_Name
VARCHAR(120)
NOT
DB21034E
The
command
was
processed
as
an
SQL
statement
because
it
was
not
a
valid
Command
Line
Processor
command.
During
SQL
processing
it
returned:
SQL0286N
A
default
table
space
could
not
be
found
with
a
page
size
of
at
least
"4096"
that
authorization
ID
"DB2"
is
authorized
to
use.
SQLSTATE=42727
See
the
″Product
Notes
and
Limitations″
section
of
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
Version
5.1.2
Warehouse
Enablement
Pack,
Version
1.1.0.2
Implementation
Guide.
General
errors
occur
while
installing
and
using
Tivoli
Enterprise
Data
Warehouse
See
the
″Troubleshooting″
chapter
in
the
Installing
and
Configuring
Tivoli
Enterprise
Data
Warehouse,
Version
1,
Release
1
guide
for
more
information.
Errors
occur
when
logging
data.
If
you
are
going
to
log
data
in
Tivoli
Enterprise
Data
Warehouse,
do
not
use
an
apostrophe
(’)
in
the
name
of
your
policy
region.
44
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
Table
15.
Tivoli
Enterprise
Data
Warehouse
problems
and
solutions
(continued)
Problem
Solution
The
length
of
some
of
the
Tivoli
Enterprise
Data
Warehouse
translated
components
conflict
with
the
name
length
limitation
of
Tivoli
Service
Level
Advisor
offering
component.
For
example,
the
translation
of
components
″IBM
WebSphere
Administration
Server″
and
″IBM
WebSphere
Transaction
manager″
cause
a
problem.
On
the
Tivoli
Service
Level
Advisor
Create
Offering
Component
window
of
the
IBM
Console,
when
the
″IBM
WebSphere
Administration
Server″
resource
is
selected,
its
Japanese
translated
message
is
placed
on
the
component
name
by
default.
When
you
click
Complete
without
changing
this
name,
you
receive
an
error
message
that
30
characters
name
is
encoded
to
62
byte
length
string
and
the
limit
of
this
field
is
48
byte.
When
you
create
a
Tivoli
Service
Level
Advisor
offering
component,
modify
its
name
not
to
exceed
the
Tivoli
Service
Level
Advisor
limit
of
48
bytes.
When
you
use
only
double-byte
character
set
(DBCS)
characters,
you
can
only
use
up
to
16
characters
because
one
DBCS
character
translates
into
three
bytes
in
UTF-8.
If
you
use
only
English
characters
you
can
use
up
to
48
characters.
Chapter
3.
Problems
and
workarounds
45
46
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
Chapter
4.
Debugging
information
The
following
sections
provide
information
that
might
be
helpful
for
debugging
any
problems
that
occur.
The
following
topics
are
discussed:
v
“Gathering
trace
information
for
IBM
Software
Support”
v
“Log
file
information”
on
page
50
v
“AutoTrace
information”
on
page
53
v
“Gathering
local
log
files
for
IBM
Software
Support”
on
page
49
v
“Gathering
proxy
mode
z/OS
log
files
for
IBM
Software
Support”
on
page
49
Gathering
trace
information
for
IBM
Software
Support
If
a
problem
occurs
that
you
cannot
solve
using
the
information
in
this
guide,
you
might
need
to
contact
IBM®
Software
Support
for
assistance.
IBM
Software
Support
might
ask
you
to
collect
additional
diagnostic
information.
The
following
sections
discuss
gathering
this
information:
v
“Object
trace
information”
v
“Gateway
and
endpoint
trace
information”
on
page
48
v
“Adapter
trace
information”
on
page
48
v
Object
trace
information
Object
trace
information
is
used
to
diagnose
Tivoli®
object
problems.
This
information
is
collected
using
one
of
the
following
commands:
odstat
or
wtrace
and
odadmin.
For
complete
information
about
these
commands,
see
the
Tivoli
Management
Framework
documentation.
odstat
odstat
is
a
Tivoli
command
that
reports
a
recent
history
of
method
calls
on
a
managed
node.
To
gather
this
information,
run
the
following
command,
directing
the
output
to
a
file:
odstat
>
<filename>.log
If
you
are
collecting
information
for
different
objects,
you
might
need
to
run
this
command
on
one
or
more
managed
nodes
in
your
Tivoli
region.
wtrace
and
odadmin
wtrace
is
a
Tivoli
command
that
reports
information
that
is
recorded
by
internal
method
traces.
The
wtrace
command
works
in
concert
with
the
odadmin
command
to
enable
and
report
the
internal
trace
information.
Like
odstat,
these
commands
must
be
run
on
each
managed
node
for
which
you
want
to
gather
detailed
diagnostic
information.
Use
the
odadmin
command
to
set
the
trace
options
required.
The
following
example
shows
the
trace
options
that
are
usually
required:
odadmin
trace
objcalls
all
You
must
run
the
odadmin
command
before
running
the
wtrace
command.
47
To
report
the
collected
information,
run
the
wtrace
command
with
the
following
options,
directing
the
output
to
a
file:
wtrace
-jk
$DBDIR
>
<filename>.log
$DBDIR
is
the
Tivoli
database
directory,
which
you
can
set
by
sourcing
your
Tivoli
environment.
Gateway
and
endpoint
trace
information
When
you
experience
problems
with
endpoints,
you
might
need
to
gather
diagnostic
information
from
the
endpoint
as
well
as
the
gateway
that
manages
the
endpoint.
The
following
sections
provide
information
about
enabling
higher
levels
of
tracing
and
the
files
that
contain
this
additional
tracing
information.
Gateway
traces
Gateway
tracing
is
enabled
with
the
wgateway
command.
This
command
enables
you
to
set
trace
levels
from
1
(minimum)
to
8
(maximum).
For
diagnosing
problems,
you
might
need
to
set
the
trace
level
to
8.
You
can
enable
gateway
tracing
from
any
system
in
your
Tivoli
region,
but
you
can
only
access
the
resulting
log
files
from
the
system
on
which
the
gateway
resides.
In
the
following
example,
the
gateway
trace
level
for
the
″tmr-gw″
gateway
is
set
to
the
maximum,
or
8:
wgateway
tmr-gw
set_debug_level
8
wgateway
tmr-gw
restart
The
gateway
trace
information
is
written
to
$DBDIR/gatelog
file
on
the
managed
node.
Note:
When
the
maximum
level
of
tracing
is
enabled,
the
gatelog
file
can
quickly
get
very
large.
After
you
get
the
information
you
need
to
diagnose
your
problem,
return
the
trace
level
to
1
and
restart
the
gateway.
Endpoint
traces
Endpoint
tracing
is
enabled
by
editing
the
$LCF_DATDIR/lcfd.cfg
file
on
the
endpoint.
To
change
the
trace
level,
change
the
log_threshold
line
to
″log_threshold=3.″
You
must
restart
the
lcfd
process
for
the
change
to
take
effect.
Endpoint
tracing
is
written
to
the
$LCF_DATDIR/lcfd.log
file.
Adapter
trace
information
The
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
Tivoli
Enterprise
Console
event
adapter
uses
JLog
to
log
execution
information.
You
have
the
following
logging
options:
ALL
Logs
all
system
actions.
ERROR
Logs
only
error
conditions.
This
is
the
default
value.
To
change
the
logging
level,
perform
the
following
steps:
1.
Open
the
itmcsLog.properties
file,
which
is
located
in
the
$LCF_DATDIR/LCFNEW/ITM/PACS
directory.
2.
Change
itmcsLogger.trc.level
as
follows:
itmcsLogger.trc.level=ALL
48
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
3.
Stop
and
restart
the
event
adapter.
The
event
adapter
writes
trace
information
to
the
trace_WebSphereAS_tecAdapter__<x>.log
file,
located
in
the
$LCF_DATDIR/LCFNEW/IZY/logs
directory.
Gathering
local
log
files
for
IBM
Software
Support
In
certain
situations,
Software
Support
might
request
that
you
send
log
files
with
your
problem
report.
Use
the
IBM
Tivoli
Monitoring
Component
Services
witmcollectsupportdata
command
to
gather
the
log
files
located
on
local
systems
into
an
XML
file
that
you
can
send
to
Software
Support.
You
can
also
use
the
List_Trace_Logs
task
to
collect
specific
log
files.
Gathering
proxy
mode
z/OS
log
files
for
IBM
Software
Support
Some
of
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
log
files
are
located
on
the
local
endpoints
or
proxy
endpoints.
However,
for
proxy
mode
z/OS
systems,
additional
log
files
are
written
to
the
proxy
mode
z/OS
system
itself.
If
you
have
a
problem
running
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
on
your
proxy
mode
z/OS
systems,
gather
the
following
log
file
information
that
Software
Support
needs.
1.
The
contents
of
the
/var/itmwas
directory
and
subdirectories
on
the
affected
system
or
systems,
compressed
into
a
.tar
file.
FTP
this
.tar
file
to
IBM
as
a
binary
file.
2.
The
current.env
file
for
any
application
server
affected
by
the
problem
3.
If
the
Data
Collector
is
running
as
a
started
task,
output
from
the
ITDSRV
started
task:
v
Spool
output
v
Files
as
specified
in
the
JCL
(such
as
stdout,
stderr,
javaout.txt)4.
If
the
Data
Collector
is
running
as
a
USS
process,
any
output
from
the
process
5.
The
JES
job
log
for
any
application
server
affected
by
the
problem
6.
If
there
are
related
error
messages
on
the
console,
the
console
log
file
7.
The
following
Java
trace
information:
v
JAVADUMP.<date>.<time>.<processID>.txt
v
CEEDUMP.<date>.<time>.<processID>
v
HPIDUMP.<date>.<time>.<processID>.txt
v
IEATDUMP
(MVS
dataset
name:
<userID>.SYSTDUMP.<date>.T<time>
The
first
three
files
above
are
located
in
the
same
directory,
based
on
the
following
order:
a.
The
directory
specified
by
the
_CEE_DMPTARG
environment
variable
b.
The
current
directory,
if
it
is
not
root
(/)
or
a
read-only
directory
c.
The
directory
specified
by
the
TMPDIR
environment
variable
d.
The
/tmp
directory
The
IEATDUMP
file
is
written
to
the
dataset
of
the
user
ID
under
which
the
process
runs.
You
can
configure
this
dataset
using
the
JAVA_DUMP_TDUMP_PATTERN
environment
variable,
which
has
the
following
syntax:
%s.JVM.TDUMP.&JOBNAME.D&YYMMDD.T&HHMMSS
Chapter
4.
Debugging
information
49
Log
file
information
Knowing
file
names,
file
contents,
and
where
to
look
for
information,
such
as
task
output
and
log
files,
can
often
be
the
key
to
solving
a
problem.
The
following
sections
provide
information
about
the
log
files
created
by
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server.
Installation
log
files
The
installer
prompts
you
when
errors
occur.
The
last
entry
in
a
log
file
often
corresponds
to
the
event
that
caused
the
error.
In
some
cases,
the
installer
guides
you
to
resolution
of
the
problem.
In
other
cases,
you
can
defer
a
step
in
the
list
and
resolve
it
later.
If
you
encounter
installation
errors,
see
the
details
in
the
logs
that
are
automatically
created
in
the
directories
listed
in
Table
16.
If
you
need
help,
contact
Software
Support
staff
and
send
the
installation
log
file.
Table
16.
Error
logs
and
descriptions
Log
file
name
Location
Description
deploy.log
/tivoli/depot/DeployEngine/logs/deploy.log
Lists
the
events
for
the
installation
of
the
Tivoli
Management
Environment.
See
the
Tivoli
Enterprise
Installation
Guide
that
comes
with
Tivoli
Management
Framework
Version
3.7.1
or
4.1
for
further
information
on
this
set
of
errors.
IZYInstall.log
See
the
Tivoli
temporary
directory.
Find
this
directory
as
follows:
1.
Access
the
Tivoli
command
line
environment.
2.
Run
wtemp
to
display
the
directory
path.
Lists
the
events
for
the
installation
of
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure.
BAMinstall.log
The
temporary
($TEMP
or
%TEMP%)
directories
that
are
defined
for
your
operating
system.
Lists
the
events
that
the
installer
generates.
izy_after.sh.log
izy_before.sh.log
tmp_core_afterscript.log
twh_app_patcher.cfg.done
twh_ibm_db2_wpack_patch_runlog.log
twh_install_props.cfg
twh_install_wpack_patcher.log
Tivoli
Enterprise
Data
Warehouse
installation
path
($TWH_TOPDIR\apps\izy\v110\install\logs
\patch_1.1.0.2)
Lists
the
events
that
occur
during
the
installation
of
the
files
that
enable
Tivoli
Enterprise
Data
Warehouse.
Note:
If
the
installation
fails
before
this
directory
structure
is
created,
the
logs
are
in
the
directory
specified
by
the
%TMPDIR%
environment
variable.
General
log
files
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
writes
log
files
to
endpoints
and
Tivoli
management
region
servers
or
gateways.
50
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
The
location
of
the
log
files
on
the
endpoint
is
$LCFDAT_DIR/LCFNEW/IZY/logs.
The
location
of
the
log
files
on
the
Tivoli
management
region
server
or
gateway
is
$DBDIR/IZY/logs.
Trace
file
information
is
kept
in
a
configurable
number
of
rotating
log
files.
The
log
file
names
follow
the
format
<filename>__<n>.log,
where
<filename>
is
the
name
of
the
individual
file,
and
<n>
is
a
number,
1,
2,
or
3.
By
default,
the
trace
files
roll
each
time
you
run
the
task.
This
means
that
when
you
run
a
task,
the
trace
information
from
<filename>__1.log
is
copied
into
a
new
file,
<filename>__2.log
and
from
there
into
<filename>__3.log.
The
<filename>__1.log
file
always
contains
the
most
recent
logged
information.
Note:
Task
log
files
roll
each
time
the
task
is
run.
For
information
about
viewing
these
log
files
from
the
Tivoli
desktop,
see
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
User’s
Guide.
Task
log
files
The
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
tasks
write
logs
to
the
$LCF_DATDIR/LCFNEW/IZY/logs
directory.
For
the
names
of
the
log
files
created
by
the
tasks,
see
the
task
descriptions
in
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure
Reference
Guide.
For
proxy
mode
z/OS
systems,
task
log
files
are
written
to
the
/var/itmwas/trace
directory.
For
information
about
viewing
these
log
files
from
the
Tivoli
desktop,
see
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
User’s
Guide.
Tivoli
Enterprise
Data
Warehouse
log
files
Tivoli
Enterprise
Data
Warehouse
log
files
are
written
to
the
Tivoli
Enterprise
Data
Warehouse
server
machine
in
the
DB2
logging
directory.
On
Windows,
the
default
directory
is
SQLLIB\logging.
The
log
file
names
start
with
IZY
and
match
the
Tivoli
Enterprise
Data
Warehouse
process
step.
Resource
model
log
files
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
resource
models
log
information
to
the
IBM
Tivoli
Monitoring
logs,
which
are
in
the
$LCF_DATDIR/LCFNEW/AMW/logs/trace_dmxengine.log
on
UNIX
and
in
the
$LCF_DATDIR/LCFNEW/Tmw2k/tmw2k.log
on
Windows.
Base
IBM
Tivoli
Monitoring
engine
and
resource
model
logging
information
is
collected
in
the
$LCF_DATDIR/LCFNEW/AMW/logs
directory.
The
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
tasks
do
not
control
these
logs.
You
can
use
the
IBM
Tivoli
Monitoring
wdmtrceng
command
to
set
the
level
of
tracing
for
IBM
Tivoli
Monitoring.
See
the
IBM
Tivoli
Monitoring
documentation
for
more
information.
The
code
that
retrieves
the
performance
information
for
the
resource
models,
the
ILT,
creates
log
files
on
the
endpoint
in
the
$LCF_DATDIR/LCFNEW/IZY/logs
directory.
Two
sets
of
log
files
are
created:
Chapter
4.
Debugging
information
51
Table
17.
Resource
model
log
files
ILT-specific,
relating
to
IBM
Tivoli
Monitoring
trace_WebSphereAS_Ilt.log,
trace_WebSphereAS_Ilt1.log,
and
trace_WebSphereAS_Ilt2.log
Data
provider
instance
log
files
for
the
version
of
IBM
WebSphere
Application
Server
trace_WebSphereAS_Ilt-remote<version>.log,
trace_WebSphereAS_Ilt-remote<version>1.log,
and
trace_WebSphereAS_Ilt-remote<version>2.log,
where
<version>
is
the
IBM
WebSphere
Application
Server
version
The
most
current
trace
log
files
are
trace_WebSphereAS_ILT.log
and
trace_WebSphereAS_ILT-remote<version>.log;
the
other
files
are
used
for
cycling
the
most
current
log.
The
level
of
logging
is
determined
by
the
itmcsLogger.trc.level
property
in
the
$LCF_DATDIR/LCFNEW/ITM/PACS/itmcsLog.Properties
file
on
the
endpoint.
The
default
setting
is
ERROR,
only
error
conditions
will
be
logged.
If
there
is
a
problem,
Software
Support
might
ask
you
to
change
this
to
ALL.
For
example:
itmcsLogger.trc.level=ALL
The
following
fields
in
the
itmcsLog.Properties
file
are
used
to
control
the
level
of
tracing:
itmcsFileHandler.maxFileSize=1024
The
maximum
size
for
each
log
file,
in
kilobytes.
The
default
value
is
1024
K.
itmcsFileHanlder.maxFiles=3
The
maximum
number
of
log
files
to
maintain.
The
default
value
is
3.
itmcsLogger.trc.level=[ERROR|INFO|ALL]
The
level
of
tracing.
You
have
the
following
options:
ERROR
Logs
only
errors.
This
is
the
default
value.
INFO
Shows
a
flow
of
the
system.
ALL
Logs
all
system
actions.
Log
files
for
proxy
mode
z/OS
systems
The
Data
Collector
writes
log
files
on
proxy
mode
z/OS
systems
to
the
/var/itmwas/log
directory
by
default.
The
files
are
named
ITD<date><version>.log
and
ITD<date><version>.trc.
These
log
files
are
ASCII
and
XML
format.
The
log
file
has
a
maximum
size
of
1
MB,
and
seven
days
of
log
files
are
retained.
The
plugin
writes
log
and
trace
files
on
proxy
mode
z/OS
systems
to
/var/itmwas/log/<sysplex>/<server>/<instance>
by
default.
The
log
files
are
named
ITDPlugin<asid><date>.log,
where
<asid>
is
the
Address
Space
ID
of
the
JVM
running
an
application
server
instance.
The
trace
file
is
named
ITDPlugin<asid><date>.trace.
These
files
are
also
in
ASCII
and
XML
format,
with
a
maximum
file
size
of
1
MB.
Seven
days
of
log
files
are
retained.
The
trace
file
size
is
limited
to
50
K.
To
view
the
files
you
can
either
use
the
supplied
LogViewer
tool
or
you
can
convert
them
into
a
readable
format.
The
latter
option
applies
to
.trc
files.
To
use
the
LogViewer
to
convert
log
files
into
a
readable
format
(EBCEDID
text),
change
to
the
/usr/lpp/itmwas/V5R1M1/tools
directory
and
run
the
following
command:
52
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
./viewer.sh
-s
text
/var/itmwas/log/<file_name>
where
<file_name>
is
the
name
of
the
log
file
that
you
want
to
convert.
If
the
log
file
is
in
a
directory
other
than
the
default
directory,
specify
the
full
path
to
the
file
instead
of
using
/var/itmwas/log.
This
command
produces
the
converted
messages
as
standard
output
and
displays
them
on
the
screen.
You
can
also
redirect
these
messages
to
a
file
by
specifying
a
file
name.
For
additional
information
about
the
LogViewer,
see
the
readme
file
located
in
the
/usr/lpp/itmwas/V5R1M1/tools
directory.
To
convert
the
.trc
log
files
located
in
/var/itmwas/log
into
a
readable
format
(EBCEDID
text),
run
the
following
command:
iconv
-f
iso8859-1
-t
ibm-1047
<file_name>
where
<file_name>
is
the
name
of
the
log
file
that
you
want
to
convert.
This
command
produces
the
converted
messages
as
standard
output
and
displays
them
on
the
screen.
You
can
also
redirect
these
messages
to
a
file
by
specifying
a
file
name.
AutoTrace
information
AutoTrace
is
installed
by
IBM
Tivoli
Monitoring
and
is
initialized
to
collect
trace
information
for
IBM
Tivoli
Monitoring
Web
Infrastructure:
WebSphere
Application
Server
on
each
managed
node
when
the
product
is
installed.
IBM
Tivoli
Monitoring
Web
Infrastructure:
WebSphere
Application
Server
generates
AutoTrace
information
only
on
the
managed
nodes
on
which
the
product
is
installed.
No
AutoTrace
information
for
IBM
Tivoli
Monitoring
Web
Infrastructure:
WebSphere
Application
Server
is
generated
on
the
endpoints.
The
following
sections
provide
information
about
AutoTrace.
The
following
topics
are
discussed:
v
Initializing
autotrace
v
Gathering
information
to
send
to
Software
Support
Initializing
autotrace
To
verify
that
AutoTrace
is
initialized
and
enabled
for
IBM
Tivoli
Monitoring
Web
Infrastructure:
WebSphere
Application
Server,
execute
the
following
command
at
a
Tivoli
sourced
prompt
on
the
Tivoli
management
region
server
or
managed
node
where
you
want
to
capture
AutoTrace
information″
$
atctl
product
When
AutoTrace
is
initialized
and
tracing,
you
see
output
similar
to
the
following:
#
prod
name
home
49420013
TMWAS
/tivoli/<hostname>.db/IZY/logs
Gathering
AutoTrace
information
To
capture
a
snapshot
of
the
Autotrace
channel
information
to
a
file
for
IBM
Tivoli
Monitoring
Web
Infrastructure:
WebSphere
Application
Server,
execute
the
following
command
at
a
Tivoli
sourced
prompt
on
the
relevant
Tivoli
management
region
server
or
managed
node.
$
atctl
snap
13
Chapter
4.
Debugging
information
53
The
number
13
stands
for
the
default
AutoTrace
channel
in
use
by
IBM
Tivoli
Monitoring
Web
Infrastructure:
WebSphere
Application
Server.
A
1
MB
file
named
snap13_0.at
is
created
as
the
output
of
the
previous
command.
You
can
submit
this
file
to
Software
Support
if
requested.
Additional
snapshots
taken
in
the
same
directory
using
the
above
command
create
files
named
snap13_x,
where
x
is
a
unique
number.
Each
snap
resets
the
trace
channel
to
zero
to
allow
for
the
accumulation
of
more
trace
information.
54
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
Chapter
5.
Understanding
warning
and
error
messages
This
chapter
introduces
message
logging
and
explains
how
to
gather
information
from
those
logs.
Message
logging
refers
to
the
text
and
numeric
messages
created
by
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server.
These
messages
relay
information
about
how
the
system
or
application
is
performing
and
can
alert
you
to
exceptional
conditions
when
they
occur.
Messages
are
sent
to
an
output
destination,
such
as
a
file,
database,
or
console
screen.
There
are
three
types
of
messages:
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure
installer
messages
v
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
messages
that
are
common
to
all
endpoints
(local
and
z/OS)
v
z/OS-specific
messages
If
you
receive
a
warning
or
error
message,
you
can
do
one
of
the
following.
v
Follow
the
instructions
listed
in
the
Detail
window
of
the
message,
if
this
is
included
in
the
message.
v
Consult
the
message
details
listed
in
this
chapter
to
see
what
action
you
can
take
to
correct
the
problem.
v
Consult
the
message
log
for
message
ID
and
text,
time
and
date
of
the
message,
as
well
as
other
data
you
can
use
to
diagnose
the
problem.
Message
format
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
messages
have
the
following
format:
Message
ID
and
text
Explanation
Operator
Response
The
message
ID
has
the
following
format:
CCC####<severity>
where
CCC
A
prefix
that
indicates
component
to
which
the
message
applies.
Can
be
one
of
the
following:
DNO
IBM
Tivoli
Monitoring
for
Web
Infrastructure
installer
messages
IZY
General
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
messages
ITD
Proxy
mode
z/OS
messages
####
The
number
of
the
message.
<severity>
Indicates
the
severity
of
the
message.
There
are
three
levels
of
severity:
I
Informational
messages
provide
feedback
about
something
that
55
happened
in
the
product
or
system
that
might
be
important.
These
messages
can
provide
guidance
when
you
are
requesting
a
specific
action
from
the
product.
Informational
messages
are
not
documented
in
this
guide.
W
Warning
messages
call
your
attention
to
an
exception
condition.
The
condition
might
not
be
an
error
but
could
cause
problems
if
not
resolved.
E
Error
messages
indicate
that
an
action
cannot
be
completed
because
of
a
user
or
system
error.
These
messages
require
user
response.
F
Fatal
message
indicate
that
an
action
occurred
from
which
the
system
cannot
recover.
These
messages
are
specific
to
proxy
mode
z/OS
systems.
The
Text
of
the
message
provides
a
general
statement
regarding
the
problem
or
condition
that
occurred.
The
Explanation
provides
additional
information
about
the
message
and
what
might
have
caused
the
condition.
The
Operator
Response
provides
recommended
actions
to
take
in
response
to
the
condition,
particularly
for
error
messages
(messages
with
the
″E″
suffix).
Note:
Many
message
texts
and
explanations
contain
variables,
such
as
the
specific
name
of
a
server
or
application.
Those
variables
are
represented
in
this
guide
as
symbols,
such
as
″&1.″
Actual
messages
contain
values
for
these
variables.
IBM
Tivoli
Monitoring
for
Web
Infrastructure
installer
messages
The
installer
can
generate
the
following
general
messages.
DNO1000E
Plugin
creation
failed
%s
Explanation:
The
installer
builds
the
Step
List
panel
from
your
settings.
Each
step
is
represented
by
a
plugin
module.
If
the
information
needed
for
a
step
is
corrupt,
this
message
appears.
Contact
Level
3
IBM
Software
Support.
DNO1001E
The
following
plugin
failed:
Explanation:
The
installer
builds
the
Step
List
panel
from
your
settings.
Each
step
is
represented
by
a
plugin
module.
If
the
information
needed
for
a
step
is
corrupt,
this
message
appears.
Contact
Level
3
IBM
Software
Support.
DNO1051E
Unable
to
find
the
XML
model
file
Explanation:
The
XML
model
file
deployConfig.xml
should
exist
under
the
<depot>/deployEngine
directory.
DNO1052E
Process
model
error
--
Explanation:
The
installer
cannot
locate
the
deployConfig.xml
file.
Check
the
deploy.ini
file
(in
/etc
on
UNIX;
in
%SystemRoot%
on
Windows.
DNO1053E
Unable
to
delete
session:
Explanation:
The
installer
attempted
and
failed
to
delete
the
<depot>/deployEngine/var/session
directory.
56
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
DNO1151E
Unable
to
get
the
step
to
run
Explanation:
This
message
might
result
from
a
software
problem.
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
DNO1154E
Unable
to
update
the
status
of
the
step
Explanation:
This
message
might
result
from
a
software
problem.
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
DNO1155E
Unable
to
run
the
GenericPlugin.RebootPlugin
Explanation:
This
Windows
error
possibly
occurred
because
a
change
to
the
Registry
failed.
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
DNO1200E
Unable
to
find
the
required
model
in
the
repository
Explanation:
The
deployConfig.xml
file
does
not
exist
in
<depot>/deployEngine/var/models.
Try
restarting.
If
the
problem
persists,
contact
IBM
Software
Support.
DNO1201E
An
error
occurred
during
the
creation
of
the
model
repository
directory
Explanation:
A
system
error
can
cause
this
message
to
display
during
creation
of
the
directory
<depot>/deployEngine/var/models
in
your
depot.
Check
disk
space
and
file
permissions.
If
the
problem
persists,
contact
IBM
Software
Support.
DNO1202E
The
required
model
file
does
not
exist
Explanation:
The
deployConfig.xml
file
does
not
exist
in
<depot>/deployEngine/var/models.
Try
restarting.
If
the
problem
persists,
contact
IBM
Software
Support.
DNO1203E
Unable
to
copy
the
file
in
the
model
repository
Explanation:
An
error
occurred
during
an
attempt
to
copy
the
file
<depot>/deployEngine/deployConfig.xml
to
the
directory
<depot>/deployEngine/var/models.
Check
disk
space
and
file
permissions.
If
the
problem
persists,
contact
IBM
Software
Support.
DNO1204E
An
error
occurred:
unable
to
delete
the
file:
Explanation:
An
error
occurred
during
an
attempt
to
delete
the
file
<depot>/deployEngine/var/models/deployConfig.xml.
Check
file
permissions.
If
the
problem
persists,
contact
IBM
Software
Support.
DNO1205E
An
error
occurred
during
file
deletion
Explanation:
An
error
occurred
during
an
attempt
to
delete
the
file
<depot>/deployEngine/var/models/deployConfig.xml.
Check
file
permissions.
Contact
IBM
Software
Support
if
problem
cannot
be
fixed.
DNO1250E
Unable
to
create
plugin
object
of
type
%s
Explanation:
This
message
might
result
from
a
software
problem.
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
Chapter
5.
Understanding
warning
and
error
messages
57
DNO1300E
Error
updating
%s
Explanation:
An
error
occurred
during
an
attempt
to
update
%s,
which
is
the
full
path
to
the
file
containing
all
search
paths
for
your
install
images.
Check
file
permissions
for
this
file.
DNO1350E
The
home
directory
for
the
following
session
already
exists
:
Explanation:
The
<depot>/deployEngine/var/session
directory
was
created
previously
and
this
was
not
expected.
Delete
this
directory
and
restart
the
installer
by
running
<depot>/restart.bat
(on
UNIX
run
<depot>/restart.sh).
DNO1351E
Unable
to
create
a
home
directory
for
the
session
:
Explanation:
The
installer
cannot
create
the
<depot>/deployEngine/var/session
directory.
Check
file
permissions
and
disk
space.
DNO1352E
Unable
to
create
SessionStatus.p
file
of
the
session
:
Explanation:
The
installer
cannot
create
the
file
<depot>/deployEngine/var/session/SessionStatus.p.
Check
file
permissions
and
disk
space.
DNO1353E
Unable
to
find
the
session:
Explanation:
Problem
locating
directory
<depot>/deployEngine/var/session.
Contact
IBM
Software
Support.
DNO1355E
Unable
to
access
the
SessionStatus.p
file
of
session:
Explanation:
The
installer
cannot
read
the
file
<depot>/deployEngine/var/session/SessionStatus.p.
Check
file
permissions
and
disk
space.
DNO1356E
Unable
to
find
the
home
directory
for
the
session
:
Explanation:
Problem
locating
directory
<depot>/deployEngine/var/session.
Contact
IBM
Software
Support.
DNO1357E
Unable
to
delete
the
home
directory
for
the
session:
Explanation:
The
installer
cannot
delete
the
directory
<depot>/deployEngine/var/session.
Check
file
permissions
and
disk
space.
DNO1358E
Error
open
log
file
of
step:
Explanation:
The
installer
cannot
read
the
file
<depot>/deployEngine/var/session/Step_nnnn/Step_nnnn.log
(where
nnnn
is
the
number
of
the
current
step).
Check
file
permissions.
DNO1359E
Unable
to
find
the
plugin
input
file
:
Explanation:
This
message
might
result
from
a
software
problem.
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
DNO1361E
The
session
is
not
in
begin
sessionID:
Explanation:
This
message
might
result
from
a
software
problem.
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
58
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
DNO1362E
The
step
home
directory
for
the
following
step
already
exists:
Explanation:
This
error
might
occur
because
of
a
corrupted
directory:
<depot>/deployEngine/var/session.
Delete
this
directory
and
restart
the
installer.
DNO1363E
Unable
to
create
the
step
home
directory
for
the
session:
Explanation:
The
installer
cannot
create
the
directory
<depot>/deployEngine/var/session.
Check
file
permissions
and
disk
space.
DNO1364E
Unable
to
copy
the
pluginInput
file
:
Explanation:
The
installer
cannot
create
the
XML
file
under
<depot>/deployEngine/var/session/Step_nnnn
(where
nnnn
is
the
number
of
the
current
step).
Check
file
permissions
and
disk
space.
DNO1365E
Unable
to
access
Step_xxxx.p
file
:
Explanation:
This
message
might
result
from
a
software
problem.
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
DNO1366E
Unable
to
update
the
SessionStatus.p
file
of
the
session
:
Explanation:
This
message
might
result
from
a
software
problem.
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
DNO1371E
Found
step
status
for
:
Explanation:
No
error
has
occurred.
No
action
is
necessary.
DNO1372E
Unable
to
find
step
:
Explanation:
This
message
might
result
from
a
software
problem.
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
DNO1900E
Rapid
Deployment
Assistant
incorrectly
installed.
Missing
or
invalid
deploy.ini
file.
Explanation:
The
file
deploy.ini
could
not
be
found
in
its
usual
location.
On
Windows,
it
is
located
in
the
system
root
directory.
The
directory
c:\WINNT
is
used
as
a
default
if
the
installer
cannot
resolve
the
root
directory
from
the
system
variables.
On
UNIX
systems,
the
file
should
be
located
in
the
/etc
directory.
Make
sure
the
file
exists
in
the
proper
directory.
The
contents
of
the
file
point
to
the
location
of
the
deployEngine
directory
located
in
the
temporary
depot
directory.
For
example,
the
file
might
contain
the
following
statement:
[Deploy]
H:\Tivoli\depot\deployEngine
H:\Tivoli\depot
becomes
the
default
depot
directory
when
the
installer
begins.
If
the
problem
cannot
be
corrected,
contact
IBM
Software
Support.
DNO1903E
Be
sure
to
load
a
valid
model.
Explanation:
An
attempt
was
made
to
load
an
invalid
XML
model.
Please
select
a
valid
XML
model
to
continue.
DNO1903Ebis
You
have
tried
to
load
an
invalid
model,
please
try
again.
Explanation:
An
attempt
was
made
to
load
an
invalid
XML
model.
Please
select
a
valid
XML
model
to
continue.
Chapter
5.
Understanding
warning
and
error
messages
59
DNO1904E
An
error
occurred
during
the
model
registration.
Ensure
you
have
the
required
disk
permissions
and
select
a
model
again.
Explanation:
An
error
has
occurred
in
registering
the
XML
model
that
describes
the
installation.
Ensure
that
enough
disk
space
is
available
and
the
current
user
has
the
correct
file
permissions.
If
the
problem
persists,
contact
IBM
Software
Support.
DNO1905E
The
session
could
not
be
opened
because
the
following
error
occurred:
{0}
(return
code:
{1}).
Select
another
model
to
continue.
Explanation:
An
error
has
occurred
in
parsing
the
XML
model
describing
the
installation.
Try
to
run
the
installation
a
second
time.
If
it
still
fails,
contact
IBM
Software
Support.
DNO1906E
Unable
to
get
status
information
for
step
{0}.
Explanation:
The
installer
cannot
retrieve
the
status
of
the
last
executed
step.
Contact
IBM
Software
Support.
DNO1907E
The
step
could
not
be
deferred
because
the
following
error
occurred:
{0}
(return
code:
{1}).
Explanation:
The
installer
cannot
defer
the
step.
Try
to
defer
the
step
again.
If
deferral
fails
again,
contact
IBM
Software
Support.
DNO1908E
A
fatal
error
occurred.
Error
message:
{0}
Explanation:
An
installer
command
has
failed.
If
the
failure
occur
before
or
after
the
Step
List
runs,
contact
IBM
Software
Support.
If
the
failure
occurs
while
the
Step
List
runs,
try
to
rerun
the
current
step.
If
it
fails
again,
contact
IBM
Software
Support.
DNO1909W
Are
you
sure
you
want
to
exit
the
application?
Explanation:
Click
OK
to
confirm
that
you
want
to
exit
the
installation
process.
DNO2001E
Reboot
failed
Explanation:
The
installer
cannot
reboot
the
local
computer.
Reboot
the
computer
through
normal
means.
If
the
installer
does
not
automatically
restart
after
the
reboot
operation,
run
the
reboot.bat
file
in
the
depot
directory.
DNO2054E
Tivoli
user
account
tmersrvd
cannot
be
created.
Explanation:
A
system
error
has
occurred
on
a
Windows
computer.
Make
sure
that
proper
Administrator
authority
exists
for
the
user
who
is
currently
logged
on.
DNO2055E
This
step
is
required
only
on
Windows
operating
systems.
Explanation:
This
message
might
result
from
a
software
problem.
Defer
the
step
and
continue.
Report
the
problem
to
IBM
Software
Support.
DNO2056E
The
kbdus.dll
is
a
prerequisite
for
the
Tivoli
Management
Framework
installation.
Install
it
before
proceeding.
Explanation:
The
file
%SystemRoot%\System32\kbdus.dll
was
not
found.
This
U.S.
keyboard
DLL
is
necessary
for
a
complete
installation
on
Windows.
The
DLL
is
available
from
Microsoft
and
also
comes
on
the
installation
CDs
for
Windows.
DNO2057E
Installation
failed.
Explanation:
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
You
can
find
further
information
in
/tmp/tivoli.cinstall
(%Dbdir%\tmp\tivoli.cinstall
on
Windows).
Also,
check
the
install.cfg.error
file
in
the
same
directory,
if
it
has
been
generated.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
60
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
DNO2059E
Installation
failed:
directory
dbdir
already
exists.
Explanation:
This
error
occurs
in
the
rare
case
of
an
unsuccessful
cleanup
of
remnants
of
an
old
Tivoli
installation.
Specifically,
an
attempt
to
rename
an
old
$DBDIR
failed.
DNO2060E
Installation
failed:
directory
bindir
already
exists.
Explanation:
This
error
occurs
in
the
rare
case
of
an
unsuccessful
cleanup
of
remnants
of
an
old
Tivoli
installation.
Specifically,
an
attempt
to
rename
an
old
$DBDIR
failed.
DNO2061E
Installation
failed:
unable
to
create
silent
install
setup
file.
Explanation:
The
installer
could
not
create
the
%SystemRoot%\setup_tmf.iss
file.
Check
disk
space
and
file
accessibility.
DNO2062E
Installation
failed:
unable
to
create
the
installation
directory.
Explanation:
The
installer
could
not
create
the
destination
directory.
Check
disk
space
and
file
accessibility.
DNO2063E
Installation
failed:
unable
to
install
Tivoli
Management
Framework
pre-installation
files.
Explanation:
The
installer
could
not
execute
WPREINSTALL.SH.
Check
disk
space
and
file
accessibility.
DNO2064E
Installation
failed:
some
or
all
installation
parameters
are
missing.
Explanation:
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
You
might
have
to
restart
the
Typical
or
Evaluation
installation
process
to
make
sure
all
parameters
are
filled
in.
DNO2065E
Installation
failed:
unable
to
find
Tivoli
Management
Framework
binary
files.
Explanation:
The
binary
files
needed
for
this
installation
cannot
be
found
in
the
depot
search
path.
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
DNO2066E
Warning:
unable
to
check
that
the
installation
succeeded.
Explanation:
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
the
name
of
the
error
file
that
is
missing.
DNO2067E
The
Tivoli
Object
Dispatcher
service
could
not
be
started.
Explanation:
The
oserv
daemon
did
not
start
during
installation.
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
You
can
find
further
information
in
/tmp/tivoli.cinstall
(%Dbdir%\tmp\tivoli.cinstall
on
Windows).
Also,
check
the
install.cfg.error
file
in
the
same
directory,
if
it
has
been
generated.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
DNO2070E
Installation
failed:
encryption
set
failed
Explanation:
The
installation
had
a
problem
with
message
encryption.
You
can
find
further
information
in
/tmp/tivoli.cinstall
(%Dbdir%\tmp\tivoli.cinstall
on
Windows).
Also,
check
the
install.cfg.error
file
in
the
same
directory,
if
it
has
been
generated.
DNO2071E
Installation
failed:
unable
to
set
the
Tivoli
Management
Region
Server
name
Explanation:
The
installation
had
a
problem
updating
the
Tivoli
database.
You
can
find
further
information
in
/tmp/tivoli.cinstall
(%Dbdir%\tmp\tivoli.sinstall
on
Windows).
Also,
check
the
install.cfg.error
file
in
the
same
directory,
if
it
has
been
generated.
Chapter
5.
Understanding
warning
and
error
messages
61
DNO2072E
Installation
failed:
unable
to
set
the
installation
password.
Explanation:
This
problem
normally
occurs
only
if
you
specify
an
installation
password.
Tivoli
recommends
that
you
do
not
set
an
installation
password
until
later.
DNO2073E
Installation
failed:
some
or
all
installation
parameters
are
missing.
Explanation:
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
more
details.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
You
might
have
to
restart
the
Typical
or
Evaluation
installation
process
to
make
sure
all
parameters
are
filled
in.
DNO2074E
Desktop
Installation
failed:
unable
to
create
silent
install
setup
file.
Explanation:
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
more
details.
This
step
can
be
deferred
without
affecting
subsequent
steps.
DNO2075E
Unable
to
install
Tivoli
Desktop
on
this
operating
system.
Explanation:
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
more
details.
This
step
can
be
deferred
without
affecting
subsequent
steps.
DNO2076E
Unable
to
set
Tivoli
environment.
Explanation:
The
installer
attempted
to
set
up
the
Tivoli
environment
and
failed.
To
manually
set
up
the
Tivoli
environment
you
run
a
script
on
UNIX
--
/etc/Tivoli/setup_env.sh
--
or
a
command
on
Windows
--
%SystemRoot%\System32\drivers\etc\Tivoli\setup_env.cmd.
DNO2077E
Desktop
Installation
failed.
Will
not
affect
remaining
install.
Please
create
Desktop
through
Framework
cd:
PC\\DESKTOP\\DISK1\\SETUP.EXE.
Explanation:
Defer
the
step
and
continue.
Install
the
optional
Desktop
interface
after
installation
is
complete.
The
installation
executable
for
this
interface
is
located
in
the
following
path
on
the
Tivoli
Management
Framework
installation
CDs:
PC\\DESKTOP\\DISK1\\SETUP.EXE
DNO2078E
Installation
failed:
unable
to
find
Desktop
binary
files.
Explanation:
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
DNO2079E
The
Tivoli
Management
Framework
installed
on
this
machine
is
not
supported
by
the
rapid
Deployment
Tool.
Explanation:
The
operating
system
of
the
local
computer
is
not
compatible
with
the
Tivoli
Framework
installation.
See
the
system
requirements
section
of
the
installation
and
setup
guide
to
see
a
list
of
supported
operating
systems.
DNO2080E
Installation
failed:
Unable
to
create
the
RapidDeployment
directory
under
the
$BINDIR
directory.
Explanation:
An
attempt
to
make
the
directory
RapidDeployment
under
the
destination
directory
was
unsuccessful.
Check
disk
space
and
file
permissions.
DNO2084E
Installation
failed:
Not
enough
disk
space.
Explanation:
The
file
system
or
partition
for
the
destination
directory
of
the
target
computer
is
too
small.
Allocate
more
disk
space
for
this
directory
and
rerun
the
step.
62
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
DNO2085E
Installation
failed:
Problem
encountered.
Explanation:
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
You
can
find
further
information
in
/tmp/tivoli.sinstall
(%Dbdir%\tmp\tivoli.sinstall
on
Windows).
Also,
check
the
install.cfg.error
file
in
the
same
directory,
if
it
has
been
generated.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
DNO2086E
Installation
failed:
Fatal
error.
Explanation:
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
You
can
find
further
information
in
/tmp/tivoli.sinstall
(%Dbdir%\tmp\tivoli.sinstall
on
Windows).
Also,
check
the
install.cfg.error
file
in
the
same
directory,
if
it
has
been
generated.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
DNO2087E
Installation
failed:
unable
to
find
the
output
file
tivoli.sinstall
Explanation:
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
You
can
find
further
information
in
/tmp/tivoli.sinstall
(%Dbdir%\tmp\tivoli.sinstall
on
Windows).
Also,
check
the
install.cfg.error
file
in
the
same
directory,
if
it
has
been
generated.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
DNO2104E
Installation
failed.
Explanation:
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
You
can
find
further
information
in
/tmp/tivoli.cinstall
(%Dbdir%\tmp\tivoli.cinstall
on
Windows).
Also,
check
the
install.cfg.error
file
in
the
same
directory,
if
it
has
been
generated.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
DNO2106E
Installation
failed:
unable
to
find
the
output
file
tivoli.cinstall
Explanation:
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
You
can
find
further
information
in
/tmp/tivoli.cinstall
(%Dbdir%\tmp\tivoli.cinstall
on
Windows).
Also,
check
the
install.cfg.error
file
in
the
same
directory,
if
it
has
been
generated.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
DNO2107E
Installation
failed:
incorrect
return
code.
Explanation:
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
You
can
find
further
information
in
/tmp/tivoli.cinstall
(%Dbdir%\tmp\tivoli.cinstall
on
Windows).
Also,
check
the
install.cfg.error
file
in
the
same
directory,
if
it
has
been
generated.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
DNO2108E
Installation
failed:
insufficient
disk
space.
You
may
change
the
destination
directory
via
the
Change
button.
Explanation:
The
file
system
or
partition
for
the
destination
directory
of
the
target
computer
is
too
small.
Allocate
more
disk
space
for
this
directory,
or
use
Change
in
the
Detail
window
to
change
the
destination
directory.
DNO2109E
Installation
failed:
installation
error
occurred.
Explanation:
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
You
can
find
further
information
in
/tmp/tivoli.cinstall
(%Dbdir%\tmp\tivoli.cinstall
on
Windows).
Also,
check
the
install.cfg.error
file
in
the
same
directory,
if
it
has
been
generated.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
Chapter
5.
Understanding
warning
and
error
messages
63
DNO2110E
Installation
failed:
communication
problem
occurred.
Explanation:
Possible
network
problem.
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
You
can
find
further
information
in
/tmp/tivoli.cinstall
(%Dbdir%\tmp\tivoli.cinstall
on
Windows).
Also,
there
is
possibly
a
XXXInstall.log
file
in
the
same
directory,
where
XXX
is
the
product
ID.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
DNO2111E
Installation
failed:
there
is
nothing
to
install.
Explanation:
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
You
can
find
further
information
in
/tmp/tivoli.cinstall
(%Dbdir%\tmp\tivoli.cinstall
on
Windows).
Also,
there
is
possibly
a
XXXInstall.log
file
in
the
same
directory,
where
XXX
is
the
product
ID.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
DNO2112E
Installation
failed:
unable
to
access
the
system.
Explanation:
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
Make
sure
proper
network
communications
are
established
between
computers.
If
necessary,
click
Change
in
the
Detail
window
to
provide
a
new,
valid
login
and
password.
DNO2113E
Installation
failed:
unable
to
recognize
the
Interp
type.
Explanation:
The
operating
system
for
the
local
computer
is
not
compatible
with
the
Tivoli
Management
Framework
installation.
See
the
system
requirements
section
of
the
installation
and
setup
guide
to
see
a
list
of
supported
operating
systems.
DNO2114E
Installation
failed:
the
managed
node
oserv
would
not
start.
Explanation:
The
following
message
was
received
during
the
installation
process:
Object
Dispatcher
service
could
not
be
started.
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
You
can
find
further
information
in
/tmp/tivoli.cinstall
(%Dbdir%\tmp\tivoli.cinstall
on
Windows).
Also,
check
the
install.cfg.error
file
in
the
same
directory,
if
it
has
been
generated.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
DNO2116E
Installation
failed:
incorrect
encryption,
or
installation
password.
Explanation:
This
error
arises
when
an
installation
password
was
previously
set,
and
then
the
wrong
one
was
provided
during
this
installation
step.
Also,
it
is
possible
that
the
installer
had
a
problem
with
message
encryption.
You
can
find
further
information
in
/tmp/tivoli.cinstall
(%Dbdir%\tmp\tivoli.cinstall
on
Windows).
DNO2117E
Installation
failed:
Managed
Node
is
not
registered.
Explanation:
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
This
error
usually
means
that
a
fatal
error
occurred
late
in
the
installation
process,
preventing
the
managed
node’s
name
from
being
entered
into
the
Tivoli
Registry.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
DNO2118E
Installation
failed:
some
or
all
installation
parameters
are
missing.
Explanation:
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
You
might
have
to
restart
the
Typical
or
Evaluation
installation
process
to
make
sure
all
parameters
are
filled
in.
DNO2119E
Installation
failed:
unable
find
Tivoli
Management
Framework
binary
files.
Explanation:
The
.IND
file
is
the
index
file
that
accompanies
and
defines
the
installation
binary
files.
The
installer
cannot
find
this
file.
You
can
find
the
file
somewhere
in
the
temporary
depot
directory.
64
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
DNO2120E
Installation
halted:
Managed
node
was
rebooted,
but
it
is
not
active.
Explanation:
The
Windows
managed
node
creation
required
a
reboot.
After
this
reboot,
the
computer
is
not
responding
to
a
ping
command
within
the
allotted
time
period.
DNO2152E
Gateway
creation
failed.
Explanation:
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
DNO2153E
Gateway
creation
failed:
incorrect
return
code.
Explanation:
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
DNO2154E
Gateway
creation
failed:
unable
to
access
the
system.
Explanation:
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
Make
sure
proper
network
communications
are
established
between
computers.
If
necessary,
click
Change
in
the
Detail
window
to
provide
a
new,
valid
login
and
password.
DNO2155E
Unable
to
create
the
gateway:
some
or
all
installation
parameters
are
missing.
Explanation:
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
You
might
have
to
restart
the
Typical
or
Evaluation
installation
process
to
make
sure
all
parameters
are
filled
in.
DNO2156E
Gateway
creation
failed:
invalid
port
number.
Explanation:
The
default
port
number
for
a
gateway
is
9494.
Certain
rules
apply
to
alternative
port
numbers.
For
example,
the
port
number
must
be
unique
on
the
target
computer.
You
might
have
to
restart
the
Typical
or
Evaluation
installation
process
to
make
sure
all
parameters
are
filled
in.
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
DNO2157E
Unable
to
find
the
Managed
Node
selected
as
gateway.
Explanation:
This
message
might
result
from
a
software
problem.
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
DNO2202E
Installation
failed.
Explanation:
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
DNO2203E
Installation
failed:
incorrect
return
code.
Explanation:
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
Chapter
5.
Understanding
warning
and
error
messages
65
DNO2204E
Installation
failed:
unable
to
access
the
system.
Explanation:
Make
sure
proper
network
communications
are
established
between
computers.
If
necessary,
click
Change
in
the
Detail
window
to
provide
a
new,
valid
login
and
password.
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
DNO2205E
Installation
failed:
some
or
all
installation
parameters
are
missing.
Explanation:
You
might
have
to
restart
the
Typical
or
Evaluation
installation
process
to
make
sure
all
parameters
are
filled
in.
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
DNO2206E
Installation
failed:
invalid
port
number.
Explanation:
The
port
number
for
an
endpoint
is
typically
9495.
Certain
rules
apply
to
alternative
port
numbers.
For
example,
the
port
number
must
be
unique
on
the
target
computer.
You
might
have
to
restart
the
Typical
or
Evaluation
installation
process
to
make
sure
all
parameters
are
filled
in.
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
DNO2207E
The
endpoint
proxy
%s
is
not
connected
to
its
gateway.
Explanation:
An
error
occurred
because
the
endpoint
proxy
named
%s
is
not
connected
to
its
gateway.
This
error
can
occur
during
the
installation
of
Windows
NT
endpoints.
Be
sure
that
the
referenced
proxy
endpoint
is
up
and
running.
Use
the
following
command
to
check
endpoint
status:
wep
<endpoint>
status
DNO2208E
Installation
failed:
Unable
to
upgrade
the
endpoint
proxy
%s
to
version
95.
Explanation:
An
attempt
to
run
the
wadminep
<endpoint>
upgrade
command
failed.
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
DNO2253E
Installation
failed:
unable
to
run
the
required
command.
Explanation:
A
problem
was
encountered
running
the
install
command.
This
message
might
result
from
a
software
problem.
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
DNO2254E
Installation
failed:
unable
to
find
the
IND
file.
Explanation:
The
.IND
file
is
the
index
file
that
accompanies
and
defines
the
installation
binary
files.
The
installer
cannot
find
this
file.
You
can
find
the
file
somewhere
in
the
temporary
depot
directory.
DNO2255E
Installation
failed:
unable
to
retrieve
information
from
Tivoli
database.
Explanation:
The
Tivoli
oserv
daemon
might
not
be
running.
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
You
can
find
further
information
in
/tmp/tivoli.cinstall
(%Dbdir%\tmp\tivoli.cinstall
on
Windows).
Also,
there
is
possibly
a
XXXInstall.log
file
in
the
same
directory,
where
XXX
is
the
product
ID.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
66
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
DNO2256E
Installation
failed:
unable
to
find
the
target
Managed
Node.
Explanation:
Make
sure
proper
network
communications
are
established
between
computers.
If
necessary,
click
Change
in
the
Detail
window
to
provide
a
new,
valid
login
and
password.
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
DNO2257E
Installation
failed:
incorrect
return
code.
Explanation:
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
You
can
find
further
information
in
/tmp/tivoli.cinstall
(%Dbdir%\tmp\tivoli.cinstall
on
Windows).
Also,
check
the
install.cfg.error
file
in
the
same
directory,
if
it
has
been
generated.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
DNO2258E
Installation
failed:
unable
to
access
the
tivoli.cinstall
output
file.
Explanation:
The
installer
normally
generates
the
tivoli.cinstall
file
after
creation
of
a
managed
node.
The
file
is
placed
in
the
/tmp
directory
in
UNIX,
or
in
the
%Dbdir%\tmp
directory
in
Windows.
There
is
a
possible
disk
access
problem.
DNO2259E
Installation
failed:
insufficient
disk
space.
Explanation:
The
file
system
or
partition
for
the
destination
directory
of
the
target
computer
is
too
small.
Allocate
more
disk
space
for
this
directory
and
rerun
the
step.
DNO2260E
An
error
occurred.
The
installation
failed.
Explanation:
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
You
can
find
further
information
in
/tmp/tivoli.cinstall
(%Dbdir%\tmp\tivoli.cinstall
on
Windows).
Also,
check
the
install.cfg.error
file
in
the
same
directory,
if
it
has
been
generated.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
DNO2261E
Installation
failed:
communication
problem
occurred.
Explanation:
Possible
network
problem.
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
You
can
find
further
information
in
/tmp/tivoli.cinstall
(%Dbdir%\tmp\tivoli.cinstall
on
Windows).
Also,
there
is
possibly
a
XXXInstall.log
file
in
the
same
directory,
where
XXX
is
the
product
ID.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
DNO2262E
Installation
failed:
there
is
nothing
to
install.
Explanation:
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
You
can
find
further
information
in
/tmp/tivoli.cinstall
(%Dbdir%\tmp\tivoli.cinstall
on
Windows).
Also,
there
is
possibly
a
XXXInstall.log
file
in
the
same
directory,
where
XXX
is
the
product
ID.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
DNO2263E
Installation
failed:
unable
to
access
the
system.
Explanation:
Make
sure
proper
network
communications
are
established
between
computers.
If
necessary,
click
Change
in
the
Detail
window
to
provide
a
new,
valid
login
and
password.
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
DNO2264E
Installation
failed:
unable
to
recognize
the
Interp
type.
Explanation:
The
operating
system
of
the
local
computer
is
not
compatible
with
the
Tivoli
Framework
installation.
See
the
system
requirements
section
of
the
installation
and
setup
guide
to
see
a
list
of
supported
operating
systems.
Chapter
5.
Understanding
warning
and
error
messages
67
DNO2265E
Installation
failed:
the
managed
node
oserv
would
not
start.
Explanation:
The
following
message
was
received
during
the
installation
process:
Object
Dispatcher
service
could
not
be
started..
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
You
can
find
further
information
in
/tmp/tivoli.cinstall
(%Dbdir%\tmp\tivoli.cinstall
on
Windows).
Also,
check
the
install.cfg.error
file
in
the
same
directory,
if
it
has
been
generated.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
DNO2266E
Installation
failed:
incorrect
encryption
or
installation
password.
Explanation:
This
error
arises
when
an
installation
password
was
previously
set,
and
then
the
wrong
one
was
provided
during
this
installation
step.
Also,
it
is
possible
that
the
installer
had
a
problem
with
message
encryption.
You
can
find
further
information
in
/tmp/tivoli.cinstall
(%Dbdir%\tmp\tivoli.cinstall
on
Windows).
DNO2267E
Installation
failed:
required
parameters
are
missing.
Explanation:
You
might
have
to
restart
the
Typical
or
Evaluation
installation
process
to
make
sure
all
parameters
are
filled
in.
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
DNO2268E
Installation
failed:
unable
to
find
IND
binary
files.
Explanation:
The
.IND
file
is
the
index
file
that
accompanies
and
defines
the
installation
binary
files.
The
installer
cannot
find
this
file.
You
can
find
the
file
somewhere
in
the
temporary
depot
directory.
DNO2269E
Installation
failed:
the
description
does
not
match
the
IND
file.
Explanation:
The
.IND
file
is
the
index
file
that
accompanies
and
defines
the
installation
binary
files.
The
installer
found
this
file
but
the
description
in
its
first
line
does
not
match
what
was
expected.
The
correct
.IND
file
should
be
somewhere
in
the
depot.
DNO2270E
Installation
failed:
see
log
files
for
details.
Explanation:
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
You
can
find
further
information
in
/tmp/tivoli.cinstall
(%Dbdir%\tmp\tivoli.cinstall
on
Windows).
Also,
check
the
install.cfg.error
file
in
the
same
directory,
if
it
has
been
generated.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
DNO2271E
Installation
failed:
product
patch
is
required.
Explanation:
This
message
might
result
from
a
software
problem.
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
DNO2272E
Installation
failed:
product
patch
is
required.
Explanation:
This
message
might
result
from
a
software
problem.
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
DNO2273E
Install
Failed:
Cannot
reexec
Tivoli
Management
Region.
Explanation:
The
installer
ran
the
odadmin
reexec
all
command
and
the
oserv
daemon
did
not
correctly
recycle.
If
you
are
unable
to
restart
the
oserv
daemon,
contact
IBM
Software
Support.
68
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
DNO2302E
Configuration
failed:
incorrect
return
code.
Explanation:
You
might
have
to
restart
the
Typical
or
Evaluation
installation
process
to
make
sure
all
parameters
are
filled
in.
Typically,
a
configuration
step
can
be
deferred
without
affecting
the
installation
of
other
products.
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
DNO2303E
Configuration
failed:
there
is
not
anything
to
configure.
Explanation:
This
message
might
result
from
a
software
problem.
Defer
the
step
and
continue.
Report
the
problem
to
IBM
Software
Support.
DNO2304E
Configuration
failed:
some
or
all
configuration
parameters
are
missing.
Explanation:
You
might
have
to
restart
the
Typical
or
Evaluation
installation
process
to
make
sure
all
parameters
are
filled
in.
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
DNO2453E
Installation
failed:
unable
to
run
the
required
command.
Explanation:
A
problem
was
encountered
running
the
install
command.
This
message
might
result
from
a
software
problem.
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
DNO2454E
Installation
failed:
unable
to
find
the
IND
file.
Explanation:
The
.IND
file
is
the
index
file
that
accompanies
and
defines
the
installation
binary
files.
The
installer
cannot
find
this
file.
You
can
find
the
file
somewhere
in
the
temporary
depot
directory.
DNO2455E
Installation
failed:
unable
to
retrieve
information
from
Tivoli
database.
Explanation:
It
is
possible
that
the
Tivoli
oserv
daemon
is
not
running.
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
You
can
find
further
information
in
/tmp/tivoli.cinstall
(%Dbdir%\tmp\tivoli.cinstall
on
Windows).
Also,
there
is
possibly
a
XXXInstall.log
file
in
the
same
directory,
where
XXX
is
the
product
ID.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
DNO2456E
Installation
failed:
unable
to
find
the
target
Managed
Node.
Explanation:
Make
sure
proper
network
communications
are
established
between
computers.
If
necessary,
click
Change
in
the
Detail
window
to
provide
a
new,
valid
login
and
password.
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
DNO2457E
Installation
failed:
incorrect
return
code.
Explanation:
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
You
can
find
further
information
in
/tmp/tivoli.cinstall
(%Dbdir%\tmp\tivoli.cinstall
on
Windows).
Also,
there
is
possibly
a
XXXInstall.log
file
in
the
same
directory,
where
XXX
is
the
product
ID.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
DNO2458E
Installation
failed:
unable
to
access
the
tivoli.cinstall
output
file.
Explanation:
The
installer
normally
generates
the
tivoli.cinstall
file
after
creation
of
a
Managed
Node.
The
file
is
placed
in
the
/tmp
directory
in
UNIX,
or
in
the
%Dbdir%\tmp
directory
in
Windows.
There
is
a
possible
disk
access
problem.
Chapter
5.
Understanding
warning
and
error
messages
69
DNO2459E
Installation
failed:
insufficient
disk
space.
Explanation:
The
file
system
or
partition
for
the
destination
directory
of
the
target
computer
is
too
small.
Allocate
more
disk
space
for
this
directory
and
rerun
the
step.
DNO2460E
An
error
occurred.
The
installation
failed.
Explanation:
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
You
can
find
further
information
in
/tmp/tivoli.cinstall
(%Dbdir%\tmp\tivoli.cinstall
on
Windows).
Also,
check
the
install.cfg.error
file
in
the
same
directory,
if
it
has
been
generated.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
DNO2461E
Installation
failed:
communication
problem
occurred.
Explanation:
Possible
network
problem.
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
You
can
find
further
information
in
/tmp/tivoli.cinstall
(%Dbdir%\tmp\tivoli.cinstall
on
Windows).
Also,
there
is
possibly
a
XXXInstall.log
file
in
the
same
directory,
where
XXX
is
the
product
ID.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
DNO2462E
Installation
failed:
there
is
nothing
to
install.
Explanation:
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
You
can
find
further
information
in
/tmp/tivoli.cinstall
(%Dbdir%\tmp\tivoli.cinstall
on
Windows).
Also,
there
is
possibly
a
XXXInstall.log
file
in
the
same
directory,
where
XXX
is
the
product
ID.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
DNO2463E
Installation
failed:
unable
to
access
the
system.
Explanation:
Make
sure
proper
network
communications
are
established
between
computers.
If
necessary,
click
Change
in
the
Detail
window
to
provide
a
new,
valid
login
and
password.
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
DNO2464E
Installation
failed:
unable
to
recognize
the
Interp
type.
Explanation:
The
operating
system
of
the
local
computer
is
not
compatible
with
the
Tivoli
Framework
installation.
See
the
system
requirements
section
of
the
installation
and
setup
guide
to
see
a
list
of
supported
operating
systems.
DNO2465E
Installation
failed:
the
managed
node
oserv
would
not
start.
Explanation:
The
following
message
was
received
during
the
installation
process:
Object
Dispatcher
service
could
not
be
started.
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
You
can
find
further
information
in
/tmp/tivoli.cinstall
(%Dbdir%\tmp\tivoli.cinstall
on
Windows).
Also,
check
the
install.cfg.error
file
in
the
same
directory,
if
it
has
been
generated.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
DNO2466E
Installation
failed:
incorrect
encryption
or
installation
password.
Explanation:
It
is
possible
that
the
installer
had
a
problem
with
message
encryption.
More
probably,
an
installation
password
was
previously
set,
and
then
the
wrong
one
was
provided
during
this
installation
step.
You
can
find
further
information
in
/tmp/tivoli.cinstall
(%Dbdir%\tmp\tivoli.cinstall
on
Windows).
DNO2467E
Installation
failed:
required
parameters
are
missing.
Explanation:
You
might
have
to
restart
the
Typical
or
Evaluation
installation
process
to
make
sure
all
parameters
are
filled
in.
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
70
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
DNO2468E
Installation
failed:
unable
to
find
IND
binary
files.
Explanation:
The
.IND
file
is
the
index
file
that
accompanies
and
defines
the
installation
binary
files.
The
installer
cannot
find
this
file.
You
can
find
the
file
somewhere
in
the
temporary
depot
directory.
DNO2469E
Installation
failed:
the
description
does
not
match
the
IND
file.
Explanation:
The
.IND
file
is
the
index
file
that
accompanies
and
defines
the
installation
binary
files.
The
installer
found
this
file
but
the
description
in
its
first
line
does
not
match
what
was
expected.
You
should
be
able
to
find
all
required
.IND
files
somewhere
in
the
depot.
DNO2470E
Installation
failed:
see
log
files
for
details.
Explanation:
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
You
can
find
further
information
in
/tmp/tivoli.cinstall
(%Dbdir%\tmp\tivoli.cinstall
on
Windows).
Also,
check
the
install.cfg.error
file
in
the
same
directory,
if
it
has
been
generated.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
DNO2473E
Install
Failed:
Cannot
reexec
Tivoli
Management
Region.
Explanation:
The
installer
ran
the
odadmin
reexec
all
command
and
the
oserv
daemon
did
not
correctly
recycle.
If
you
are
unable
to
restart
the
oserv
daemon
manually,
contact
IBM
Software
Support.
DNO2474E
No
hostname
provided
by
user
data
Explanation:
This
message
might
result
from
a
software
problem.
Defer
the
step
and
continue.
Report
the
problem
to
IBM
Software
Support.
DNO2475E
No
log
information
provided.
Probable
install
failure.
Explanation:
Check
the
<depot>/deployEngine/logs/deploy.log
file
for
information
about
the
problem.
The
end
of
the
log
file
contains
the
most
recently
logged
information.
You
can
find
further
information
in
/tmp/tivoli.cinstall
(%Dbdir%\tmp\tivoli.cinstall
on
Windows).
Also,
there
is
possibly
a
XXXInstall.log
file
in
the
same
directory,
where
XXX
is
the
product
ID.
If
necessary,
ask
IBM
Software
Support
to
help
you
resolve
the
problem.
DNO3000E
WRONG_MACHINE=This
program
must
run
on
the
Tivoli
Management
Region
server.
Explanation:
You
must
run
the
installer
on
a
Tivoli
Management
Region
server.
If
you
are
running
the
installer
on
the
host
computer
for
the
Tivoli
Management
Region
server,
make
sure
the
Tivoli
Object
Dispatcher
service
or
daemon
is
started
and
rerun
the
installation
program.
If
you
are
not
running
the
installer
on
the
host
computer
for
the
Tivoli
Management
Region
server,
rerun
the
installer
on
the
computer.
DNO3001E
TME_TOO_OLD=The
Tivoli
Management
Framework
product
installed
on
this
Tivoli
Management
Region
is
older
than
3.7.
You
must
upgrade
to
at
least
3.7
to
use
this
tool.
Explanation:
The
minimum
level
of
the
Tivoli
Management
Environment
must
be
version
3.7.
Manually
upgrade
the
Framework
to
version
3.7
then
proceed
with
the
installation.
See
the
manual
installation
instructions
in
the
installation
and
setup
guide
for
this
product.
DNO3002E
NOT_ADMINID=The
current
userid
does
not
have
the
proper
roles.
Logon
to
a
Tivoli
administrator
userid
with
admin,
super,
install_client,
and
install_product
roles.
Explanation:
The
user
ID
under
which
the
installer
runs
must
have
the
privileges
of
a
Tivoli
Administrator
user
ID.
Log
on
to
a
user
ID
that
has
admin,
super,
install_client,
and
install_product
roles
to
run
the
installer.
Chapter
5.
Understanding
warning
and
error
messages
71
DNO3003E
DISCOVERY_FAILED=Discovery
of
the
current
Tivoli
environment
failed.
The
installation
wizard
cannot
continue.
Explanation:
The
installer
cannot
continue
because
of
a
condition
that
has
already
been
logged.
If
there
has
not
been
an
error
message
displayed,
examine
the
log
for
the
error
condition.
Correct
it
and
rerun
the
installer.
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
Messages
IZY1001E
Task
failed
Explanation:
The
task
failed.
Operator
Response:
Check
the
error
log
for
the
task,
correct
any
problems,
if
possible,
and
run
the
task
again.
IZY1003E
This
task
must
be
run
on
an
endpoint.
Explanation:
An
attempt
was
made
to
run
the
task
on
a
machine
that
is
not
a
Tivoli
endpoint.
Operator
Response:
Run
the
task
again,
specifying
an
endpoint
as
the
target
for
the
task.
IZY1005E
This
task
must
be
run
against
a
managed
node.
Explanation:
An
attempt
was
made
to
run
the
task
on
a
machine
that
is
a
Tivoli
endpoint.
Operator
Response:
Run
the
task
again,
specifying
a
managed
node
as
the
target
for
the
task.
IZY1054E
The
following
error
occurred
while
deleting
debug
logs
on
%1$s:
Explanation:
An
error
occurred
while
deleting
debug
logs
on
%1$s.
One
or
more
logs
may
not
have
been
deleted.
Operator
Response:
Check
the
task
output,
correct
the
problems,
and
run
the
task
again.
IZY1066E
Version
%1$s
is
not
a
supported
version
of
IBM
WebSphere
Application
Server.
Explanation:
The
%1$s
version
of
IBM
WebSphere
Application
Server
is
not
supported.
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
is
supported
with
IBM
WebSphere
Application
Server
versions
4.x.x.
IZY1069E
The
security
properties
file
%1$s
was
not
found.
Explanation:
The
security
properties
file
%1$s
was
not
found.
The
file
might
have
been
moved
or
deleted
from
the
system.
Operator
Response:
Restore
the
file,
if
possible,
and
run
the
task
again.
IZY1073E
A
stop
was
issued
for
the
event
adapter
and
it
failed
with
return
code
%1$s
Explanation:
A
request
was
made
to
stop
the
event
adapter.
That
attempt
failed.
The
return
code
%1$s
has
additional
information
as
to
the
cause
of
this
failure.
IZY1078E
IBM
WebSphere
Application
Server
was
not
found
in
%1$s.
Specify
the
correct
path
and
run
the
configuration
task
again.
Explanation:
The
configuration
task
requires
the
path
for
IBM
WebSphere
Application
Server.
The
installation
path
%1$s
does
not
exist
on
the
endpoint.
The
task
is
unable
to
continue
processing
since
it
cannot
determine
sufficient
IBM
WebSphere
Application
Server
information.
The
directory
might
have
been
deleted
or
IBM
WebSphere
Application
Server
might
have
been
removed
from
the
machine.
Operator
Response:
Check
that
IBM
WebSphere
Application
Server
is
installed
and
that
the
directory
exists.
If
the
IZY1001E
•
IZY1078E
72
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
directory
does
not
exist,
reinstall
the
IBM
WebSphere
Application
Server
components.
If
the
directory
does
exist,
contact
IBM
Software
Support.
IZY1082E
Error
obtaining
status
for
server
%1$s:
%2$s.
Explanation:
An
error
occurred
while
attempting
to
obtain
the
status
for
server
%1$s.
The
error
was
%2$s.
Operator
Response:
Check
the
error
log
for
the
task,
correct
any
problems,
if
possible,
and
run
the
task
again.
Contact
IBM
Software
Support
if
the
problem
persists.
IZY1083E
Some
files
or
directories
might
not
have
been
deleted
from
%1$s.
Explanation:
An
error
occurred
while
deleting
files
or
directories
from
%1$s.
Operator
Response:
Check
the
error
log
for
the
task,
correct
any
problems
if
possible,
and
run
the
task
again.
Contact
IBM
Software
Support
if
the
problem
persists.
IZY1085E
IBM
WebSphere
Application
Server
is
not
installed
or
is
not
installed
in
the
location
specified.
Explanation:
The
task
was
unable
to
locate
the
IBM
WebSphere
Application
Server
installation
directory.
IBM
WebSphere
Application
Server
must
be
installed
on
the
endpoint
for
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
to
monitor
its
status.
Operator
Response:
If
IBM
WebSphere
Application
Server
is
installed
on
the
endpoint
and
the
installation
directory
is
correct,
contact
IBM
Software
Support.
Check
that
IBM
WebSphere
Application
Server
is
installed
and
that
the
installation
directory
exists.
If
IBM
WebSphere
Application
Server
is
not
installed
on
the
endpoint,
reinstall
the
IBM
WebSphere
Application
Server
components.
If
IBM
WebSphere
Application
Server
is
installed,
the
installation
directory
that
you
specified
when
you
created
the
IBM
WebSphere
administration
server
object
might
not
be
correct.
Recreate
the
IBM
WebSphere
administration
server
object
and
specify
the
correct
installation
directory.
IZY1086E
Checked
location:
%1$s
Explanation:
No
additional
help
is
available
for
this
message.
IZY1087E
The
event
adapter
is
not
installed.
The
Configure
WebSphere
TEC
Adapter
task
must
be
run
to
install
it.
Explanation:
This
task
requires
that
the
event
adapter
is
installed.
Operator
Response:
Run
the
Configure
WebSphere
TEC
Adapter
task
to
configure
and
deploy
the
event
adapter
and
run
this
task
again.
IZY1090E
Error
obtaining
data:
%1$s
Explanation:
An
error
occurred
during
an
attempt
to
obtain
data.
The
error
is
%1$s.
Operator
Response:
Check
the
error
log
for
this
task,
correct
any
problems,
if
possible,
and
run
the
task
again.
Contact
IBM
Software
Support
if
the
problem
persists.
IZY1092W
The
Adapter
Configuration
Facility
is
not
installed.
Events
cannot
be
forwarded
to
the
event
server.
Explanation:
The
Adapter
Configuration
Facility
is
required
to
forward
events
to
the
event
server.
Operator
Response:
Install
the
Adapter
Configuration
Facility
and
run
the
task
again.
If
the
Adapter
Configuration
Facility
is
installed
and
correctly
configured,
contact
IBM
Software
Support.
IZY1095E
An
error
occurred
starting
IBM
WebSphere
administration
server
%2$s:
%1$s
Explanation:
An
error
occurred
while
starting
the
administration
server.
The
error
is
%1$s.
Operator
Response:
Check
the
error
logs
for
the
Start
Administration
Server
task,
correct
any
problems,
if
possible,
and
run
the
task
again.
Contact
Tivoli
Customer
Service
if
the
problem
persists.
IZY1082E
•
IZY1095E
Chapter
5.
Understanding
warning
and
error
messages
73
IZY1098E
An
error
occurred
stopping
the
IBM
WebSphere
administration
server
%2$s:
%1$s
Explanation:
An
error
occurred
while
stopping
the
administration
server.
The
error
is
%1$.
Check
the
error
logs
for
the
Stop
Administration
Server
task,
correct
the
problems,
if
possible,
and
run
the
task
again.
Contact
Tivoli
Customer
Service
if
the
problem
persists.
Operator
Response:
Check
the
error
logs
for
the
Stop
Administration
Server
task,
correct
the
problems,
if
possible,
and
run
the
task
again.
Contact
Tivoli
Customer
Service
if
the
problem
persists.
IZY1101E
The
server
%1$s
was
not
started:
%2$s.
If
you
are
starting
an
application
server
in
a
5.0
Network
Deployment
configuration
ensure
the
node
agent
is
started
before
you
attempt
to
start
the
application
server.
Explanation:
An
error
occurred
while
starting
the
%1$s
server.
The
error
is
%2$s.
Operator
Response:
Check
the
error
log
for
the
task,
correct
the
problems,
if
possible,
and
run
the
task
again.
IZY1102E
The
server
%1$s
was
not
stopped:
%2$s
Explanation:
An
error
occurred
while
stopping
the
%1$s
server.
The
error
is
%2$s.
Operator
Response:
Check
the
error
log
for
the
task,
correct
the
problems,
if
possible,
and
run
the
task
again.
IZY1110E
The
specified
%1$s
managed
node
name
to
forward
events
is
not
valid.
Explanation:
The
managed
node
name
specified
is
not
valid
because
it
contains
blank
spaces.
Operator
Response:
Run
the
task
again,
specifying
a
managed
node
name
that
does
not
contain
blank
spaces.
IZY1113E
An
error
occurred
while
obtaining
data.
The
Integration
Server
is
not
running.
Explanation:
This
task
requires
that
the
integration
server
be
running.
Operator
Response:
Start
the
integration
server
and
run
the
task
again.
IZY1114E
The
application
server
%1$s
is
not
running
or
unreachable.
If
you
are
starting
an
application
in
a
5.0
Network
Deployment
configuration
ensure
the
node
agent
is
started
before
you
attempt
to
start
the
application.
Explanation:
This
task
requires
that
the
application
server
be
running.
Operator
Response:
Start
the
application
server
%1$s
and
run
the
task
again.
IZY1115E
An
error
occurred
while
obtaining
data.
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
is
unable
to
communicate
with
the
management
server.
Verify
the
security
settings
for
the
management
server.
Explanation:
An
error
occurred
while
communicating
with
the
IBM
WebSphere
management
server.
The
security
settings
for
the
management
server
might
be
set
incorrectly.
Operator
Response:
Check
these
security
settings
and
run
the
task
again.
Contact
IBM
Software
Support
if
the
problem
persists.
IZY1120E
An
error
occurred
while
obtaining
data
because
the
IBM
WebSphere
administration
server
%1$s
is
not
running.
Explanation:
An
error
occurred
while
communicating
with
the
administration
server.
The
administration
server
is
not
running.
Operator
Response:
Start
the
administration
server
and
run
the
task
again.
IZY1098E
•
IZY1120E
74
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
IZY1121E
An
error
occurred
while
starting
the
application
server
because
the
IBM
WebSphere
administration
server
is
not
running.
Explanation:
An
error
occurred
while
starting
the
application
server
because
the
IBM
WebSphere
administration
server
is
not
running.
The
IBM
WebSphere
administration
server
with
which
the
application
server
is
associated
must
be
running
in
order
to
start
the
application
server.
Operator
Response:
Start
the
administration
server
and
run
the
task
again.
IZY1122E
An
error
occurred
while
stopping
the
application
server
because
the
IBM
WebSphere
administration
server
is
not
running.
Explanation:
An
error
occurred
while
stopping
the
application
server
because
the
IBM
WebSphere
administration
server
is
not
running.
The
IBM
WebSphere
administration
server
with
which
the
application
server
is
associated
must
be
running
in
order
to
stop
the
application
server.
Operator
Response:
Start
the
administration
server
and
run
the
task
again.
IZY1125E
The
event
adapter
did
not
start
or
is
still
starting.
Possible
reasons
include:
1-
The
IBM
WebSphere
resource
is
not
running.
2
-
A
free
port
could
not
be
found
for
use.
3
-
The
Tivoli
endpoint
machine
may
be
experiencing
performance
problems
preventing
the
event
adapter
from
starting
in
a
timely
manner.
Explanation:
An
error
occurred
starting
the
event
adapter.
Operator
Response:
Ensure
that
the
IBM
WebSphere
resource
is
running
and
that
the
port
number
is
not
already
in
use.
Check
the
trace_WebSphereAS_tecAdapter.log
file
for
errors
and
run
the
task
again.
If
the
Tivoli
endpoint
is
experiencing
performance
problems
wait
a
few
minutes
and
check
the
TEC
console
for
the
presence
of
an
event
indicating
the
event
adapter
has
started.
Contact
IBM
Software
Support
if
the
problem
persists.
IZY1126E
No
valid
consoles
were
found.
Explanation:
No
valid
consoles
were
found.
Operator
Response:
Ensure
that
there
are
valid
consoles
and
run
the
task
again.
IZY1141E
The
policy
region
name
is
required.
Explanation:
No
additional
help
is
available
for
this
message.
IZY1142E
The
IBM
WebSphere
Application
Server
installation
path
is
required.
Explanation:
The
IBM
WebSphere
Application
Server
installation
path
is
required.
Operator
Response:
Run
the
task
again,
specifying
the
IBM
WebSphere
Application
Server
installation
path.
IZY1145E
This
task
requires
a
WSApplicationServer
object
type.
Explanation:
The
task
requires
an
IBM
WebSphere
application
server
(WSApplicationServer)
object.
Operator
Response:
Run
the
task
again,
specifying
an
application
server
object.
IZY1146E
The
task
requires
a
WSAdministrationServer
object
type.
Explanation:
The
task
requires
an
IBM
WebSphere
administration
server
(WSAdministrationServer)
object.
Operator
Response:
Run
the
task
again,
specifying
an
administration
server
object.
IZY1121E
•
IZY1146E
Chapter
5.
Understanding
warning
and
error
messages
75
IZY1159E
Endpoint
%1$s
will
not
be
discovered
due
to
failure
calling
dependency
init.
Explanation:
An
error
occurred
while
discovering
endpoint
%1$s
because
dependency
init
could
not
be
called.
It
is
likely
the
Tivoli
roles
are
insufficient,
or
there
is
communication
trouble
with
the
endpoint.
IZY1162E
Run
the
task
against
a
valid
target:
%1$s.
Explanation:
The
task
was
run
against
an
incorrect
object.
This
task
must
be
run
against:
%1$s.
Operator
Response:
Run
the
task
again,
specifying
a
valid
object.
IZY1163E
The
required
dependency
file
%1$s
was
not
found.
Explanation:
Verify
that
file
%1$s
is
available.
If
the
problem
persists
please
contact
IBM
Software
Support.
IZY1164E
Error
creating
WebSphere
XML
output.
Make
sure
the
administration
server
is
up
and
running.
If
WebSphere
global
security
is
enabled,
check
that
the
client
properties
file
specified
for
the
Discover
WebSphere
Resources
task
has
the
correct
entries
for
com.ibm.CORBA.loginUserid
and
com.ibm.CORBA.loginPasword.
See
log
file
for
details.
Explanation:
The
Discover_WebSphere_Resources
task
encountered
an
error
while
trying
to
obtain
XML
configuration
information
from
IBM
WebSphere
Application
Server
on
the
endpoint.
Make
sure
the
administration
server
is
up
and
running.
If
WebSphere
global
security
is
enabled,
check
that
the
client
properties
file
specified
for
the
Discover_WebSphere_Resources
task
has
the
correct
entries
for
com.ibm.CORBA.loginUserid
and
com.ibm.CORBA.loginPasword.
Check
the
error
log,
trace_itmwas_discover_endpoint.log,
for
more
information
about
the
error.
Operator
Response:
Make
sure
the
administration
server
is
up
and
running.
If
WebSphere
global
security
is
enabled,
check
that
the
client
properties
file
specified
for
the
Discover
WebSphere
Resources
task
has
the
correct
entries
for
com.ibm.CORBA.loginUserid
and
com.ibm.CORBA.loginPasword.
IZY1165E
This
endpoint
has
an
unsupported
WebSphere
version
%1$s.
The
Discover
WebSphere
Resources
task
will
stop.
Explanation:
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
supports
version
4.x.x.
of
IBM
WebSphere
Application
Server.
The
endpoint
you
selected
needs
to
be
updated
before
it
can
be
managed
using
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server.
IZY1166E
Cannot
find
file
%1$s.
The
Discover
WebSphere
Resources
task
will
stop.
Explanation:
The
Discover
WebSphere
Resources
task
cannot
locate
the
security
properties
file
you
specified.
The
file
might
have
been
moved
to
a
different
directory
or
removed
from
the
system.
IZY1167E
Cannot
find
directory
%1$s.
The
Discover
WebSphere
Resources
task
will
stop.
Explanation:
The
Discover
WebSphere
Resources
task
cannot
locate
the
IBM
WebSphere
Application
Server
installation
directory
on
this
endpoint.
Operator
Response:
Ensure
that
IBM
WebSphere
Application
Server
is
installed
on
the
endpoint
and
that
the
installation
path
that
you
specified
is
correct.
If
IBM
WebSphere
Application
Server
is
not
installed
on
the
endpoint,
install
it.
Run
the
Discover
WebSphere
Resources
task
again,
specifying
the
full
path
to
the
installation
directory.
If
this
problem
persists,
contact
IBM
Software
Support.
IZY1168E
The
required
%1$s
Tivoli
Business
Systems
Manager
file
was
not
found.
Explanation:
A
required
%1$s
Tivoli
Business
Systems
Manager
file
was
not
found
on
the
system.
Operator
Response:
Ensure
that
Tivoli
Business
Systems
Manager
is
installed
on
the
Tivoli
Enterprise
Console
system.
If
it
is
not,
reinstall
Tivoli
Business
Systems
Manager.
IZY1159E
•
IZY1168E
76
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
IZY1169E
Error
adding
subscriber
%1$s
Explanation:
No
additional
help
is
available
for
this
message.
IZY1170E
Policy
region
%1$s
does
not
exist.
It
is
required
as
a
destination
for
application
servers
created
by
the
Discover
WebSphere
Resources
task.
Explanation:
Create
a
″WebSphere
Application
Servers″
policy
region
and
run
the
task
again.
IZY1171E
Managed
node
name
%1$s
does
not
exist.
It
must
match
one
of
the
managed
nodes
listed
by
the
command
wlookup
-ar
ManagedNode
Explanation:
No
additional
help
is
available
for
this
message.
IZY1172E
You
have
indicated
that
the
node
name
is
different
than
the
host
name
for
this
endpoint.
Node
name
%1$s
was
not
found
in
the
WebSphere
domain.
Explanation:
No
additional
help
is
available
for
this
message.
IZY1173E
Run
the
task
against
a
managed
node
or
endpoint.
Explanation:
The
task
was
run
against
an
incorrect
object.
This
task
must
be
run
against
a
managed
node
or
endpoint.
Operator
Response:
Run
the
task
again,
specifying
a
valid
object.
IZY1176E
Temporary
WebSphere
Application
Server
conversation
%1$s
could
not
be
created.
Explanation:
A
temporary
conversation
is
used
to
gather
configuration
information
from
IBM
WebSphere
Application
Server.
The
conversation
is
never
committed
or
activated,
but
is
created,
used
to
gather
information
about
the
IBM
WebSphere
Application
Server
configuration,
and
then
deleted.
Since
the
conversation
could
not
be
created,
no
information
could
be
retrieved
about
the
server
configuration.
WebSphere
Systems
Management
Server
instances
might
not
be
running
on
the
system
you
specified
or
IBM
WebSphere
Application
Server
might
not
be
configured
correctly.
IZY1177E
WebSphere
System
Management
%3$s
call
returned
error
code
%1$s
while
running
command
%2$s.
Explanation:
WebSphere
System
Management
API
program
%3$s
was
used
to
invoke
the
command
%2$s.
Since
this
API
returned
an
error,
the
IBM
WebSphere
Application
Server
operation
could
not
be
completed.
IZY1178E
Cannot
find
z/OS
directory
%1$s.
The
Discover
WebSphere
Resources
task
will
stop.
Explanation:
The
Discover
WebSphere
Resources
task
cannot
locate
the
IBM
WebSphere
Application
Server
installation
directory
on
the
z/OS
host.
Operator
Response:
Ensure
that
IBM
WebSphere
Application
Server
for
z/OS
and
OS/390
is
installed
and
that
the
installation
path
that
you
specified
is
correct.
Run
the
Discover
WebSphere
Resources
task
again,
specifying
the
full
path
to
the
installation
directory.
IZY1179E
The
System
Management
Scripting
API
could
not
be
found
at
the
WebSphere
installation
path
%1$s.
Explanation:
The
bin
directory
under
the
IBM
WebSphere
Application
Server
installation
path
%1$s
does
not
contain
the
CB390CFG
program,
which
is
used
to
gather
configuration
information
about
IBM
WebSphere
Application
Server.
Operator
Response:
Correct
the
installation
path
and
run
the
Discover
WebSphere
Resources
task
again.
IZY1169E
•
IZY1179E
Chapter
5.
Understanding
warning
and
error
messages
77
IZY1180E
OS/390
or
z/OS
host
specified
incorrectly.
Explanation:
You
must
either
specify
both
the
host
name
and
the
host
type
or
you
must
specify
neither.
If
you
do
not
specify
a
host
name
and
type,
the
task
runs
on
the
host
where
the
NETCONV
connection
was
established.
Operator
Response:
Specify
both
the
host
name
and
the
host
type
or
specify
neither.
IZY1181E
Incorrect
host
protocol
specified.
Explanation:
The
protocol
to
reach
the
host
must
be
″-h″
for
IP
host
name
or
″-d″
for
SNA
domain
name.
IZY1182E
A
command
issued
to
z/OS
through
the
NETCONV
connection
failed
with
return
code
%1$s.
Explanation:
Information
is
retrieved
and
operations
are
performed
on
the
z/OS
system
by
issuing
commands
through
a
connection
that
is
established
from
NetView
for
z/OS
using
the
NETCONV
command.
Errors
in
the
commands
themselves
are
represented
by
return
codes
from
1
to
200.
Errors
in
the
connection
or
in
the
process
of
invoking
the
commands
are
represented
by
return
codes
above
200.
Previous
messages
in
the
output
will
give
more
details
about
the
error.
IZY1185E
itmwas_zosutils.sh
not
found.
Explanation:
Utility
functions
were
not
found.
This
is
a
result
of
running
the
task
against
a
non-WebSphere
Application
Server
object.
Operator
Response:
Run
the
task
against
a
valid
component.
IZY1186E
Host
name
"&1"
could
not
be
converted
to
a
NetView
domain
name
Explanation:
The
Tivoli
Business
Services
Manager
Task
Manager
could
not
convert
the
IP
host
name
to
a
NetView
domain
name.
Operator
Response:
Before
communications
can
be
established,
the
IP
host
name
must
first
be
converted
to
the
domain
name.
v
Verify
that
the
IP
host
name
is
correct.
v
Verify
that
IP
host
name
is
known
to
NetView.
v
Verify
that
the
NetView
Operator’s
password
is
correct
IZY1187E
Unable
to
communicate
with
NetView
at
"&1"
Explanation:
The
Tivoli
Business
Services
Manager
Task
Manager
could
not
communicate
with
the
NetView
Operator.
Operator
Response:
v
Verify
communications
by
stopping
and
restarting
the
NETCONV
session.
v
Verify
that
a
NETCONV
command
has
been
issued
at
the
NetView
Operator’s
console
and
that
it
was
successful.
v
Verify
that
the
NetView
Operator
ID
and
password
have
been
defined
to
the
Tivoli
Business
Services
Manager
Task
Manager
using
its
hostcmdoper
command.
IZY1189E
An
error
has
occurred
issuing
this
command
on
USS:
"&1"
Explanation:
On
the
z/OS
session,
UNIX
System
Services
(USS)
did
not
execute
the
command.
See
message
IZY1190E
for
return
code
information.
Operator
Response:
See
message
IZY1190E
for
return
code
information.
IZY1190E
NetView
Pipes
has
returned
this
error
code:
"&1"
Explanation:
On
the
z/OS
session,
UNIX
System
Services
(USS)
did
not
execute
the
command
identified
in
message
IZY1189E.
This
message
was
returned
from
UNIX
System
Services.
IZY1180E
•
IZY1190E
78
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
Operator
Response:
Refer
to
Tivoli
NetView
for
z/OS
Customization:
Using
Pipes,
for
a
description
of
the
return
codes.
IZY1191E
UNIXSERV
is
not
started
on
NetView
operator
at
"&1"
Explanation:
The
command
did
not
complete
successfully.
To
send
commands
to
UNIX
System
Services
(USS),
the
NetView
Operator
must
already
be
communicating
with
USS.
Operator
Response:
To
start
communications
with
USS,
use
the
NetView
NCCF
command.
For
information
on
the
Start
(NCCF)
command,
refer
to
the
Tivoli
NetView
for
z/OS
Command
Reference.
IZY1192E
Tivoli
Business
Systems
Manager
task
server
has
not
been
started.
Explanation:
The
Tivoli
Business
Systems
Manager
task
server
is
not
running.
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
uses
the
Tivoli
Business
Systems
Manager
task
server
to
communicate
with
NetView
on
z/OS.
Operator
Response:
Start
the
Tivoli
Business
Systems
Manager
task
server.
Refer
to
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
User’s
Guide
for
instructions
on
starting
the
Tivoli
Business
Systems
Manager
task
server.
IZY1193E
Cannot
find
setup_env.sh.
Explanation:
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
could
not
determine
the
location
of
the
Tivoli
Business
Systems
Manager
task
server.
Operator
Response:
v
Verify
that
the
task
was
run
against
an
endpoint
where
the
Tivoli
Business
Systems
Manager
task
server
is
installed.
If
the
setup_env.sh
file
is
not
located
in
the
default
installation
directory,
the
TSERVER_ETC
environment
variable
must
be
set
to
identify
the
location
of
the
setup_env.sh
file
used
by
the
Tivoli
Business
Systems
Manager
task
server.
On
Windows,
the
default
location
is
%windir%\system32\drivers\etc\Tivoli.
On
UNIX
systems,
the
default
location
is
/etc/Tivoli.
v
Verify
that
the
Tivoli
Business
Systems
Manager
task
server
has
been
installed
on
the
endpoint.
IZY1194E
Error
communicating
with
z/OS
at
"&1"
Explanation:
The
MVS
command
issued
may
not
have
completed
successfully.
Operator
Response:
Verify
that
communications
with
the
z/OS
component
are
functioning.
For
more
information
on
communicating
with
the
z/OS
component,
refer
to
Tivoli
NetView
for
z/OS
Command
Reference
for
a
description
of
the
Start
(NCCF)
command.
IZY1195E
NetView
operator
logged
off
or
bad
password.
Explanation:
The
Tivoli
Business
Systems
Manager
task
server
requires
both
a
NetView
Operator
ID
and
the
Operator’s
password
to
communicate
with
the
NetView
Operator.
The
NetView
Operator
ID
and
password
used
is
undefined,
incorrect,
or
has
expired.
Operator
Response:
Redefine
the
NetView
Operator
ID
and
password.
For
information
on
using
the
hostopercmd
to
define
a
NetView
Operator
ID
and
an
Operator
password
used
by
the
Tivoli
Business
Systems
Manager
task
server
to
communicate
with
NetView,
refer
to
the
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide.
IZY1196E
Could
not
find
hostcmd
on
the
endpoint.
Explanation:
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
could
not
locate
the
processor
for
the
hostcmd.
Operator
Response:
Verify
the
Tivoli
Business
Systems
Manager
task
server
is
installed
and
running.
If
installation
of
the
Tivoli
Business
Systems
Manager
task
server
is
required,
refer
to
the
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide
for
the
installation
instructions.
IZY1191E
•
IZY1196E
Chapter
5.
Understanding
warning
and
error
messages
79
IZY1197E
NetView
Operator
ID
is
not
authorized
USS
user
ID
on
"&1"
Explanation:
The
NetView
Operator
ID
used
does
not
have
authorization.
The
NetView
Operator
ID
used
is
either
not
defined
with
a
UID
of
0
or
is
incorrect.
Operator
Response:
Verify
the
User
ID
defined
to
USS
is
the
same
name
as
the
NetView
Operator
ID
and
it
was
defined
a
UID
of
0.
IZY1198E
No
cross-domain
session
with
"&1"
Explanation:
Communications
between
a
remote
NetView
from
the
focal
NetView
could
not
be
established.
Operator
Response:
Verify
the
name
of
the
remote
NetView.
Verify
a
cross-domain
session
has
been
established
between
the
two
hosts.
IZY1199E
NetView
Operator
ID
must
have
a
UID
of
0
on
"&1"
Explanation:
The
NetView
Operator
ID
used
does
not
have
the
proper
system-level
authorization.
Operator
Response:
Verify
the
NetView
Operator
ID
has
been
defined
with
a
UID
of
0.
IZY1200E
NetView
CORRWAIT
timeout
on
"&1".
Explanation:
The
command
did
not
complete
within
the
expected
time.
IZY1201E
The
NetView
Domain
Name
is
too
long.
Explanation:
The
NetView
Domain
Name
must
be
no
longer
than
5
characters.
Operator
Response:
Verify
the
spelling
of
the
NetView
domain
name
and
try
again.
If
this
is
really
a
TCP/IP
name,
ensure
that
the
TCP/IP
check
box
is
checked.
IZY1202E
The
Tivoli
Business
Systems
Manager
task
server
completed
with
return
code
=
"&1".
Explanation:
The
Tivoli
Business
Systems
Manager
task
server
unexpectedly
completed
with
a
non-zero
return
code.
Operator
Response:
Contact
IBM
Software
Support.
IZY1203E
The
response
from
NetView
is
greater
than
3700
bytes.
This
can
cause
problems
on
Windows
platforms.
Explanation:
Decrease
the
length
of
response
or
contact
IBM
Software
Support.
IZY1205E
WebSphere
for
z/OS
administration
servers
cannot
be
started
or
stopped
from
IBM
Tivoli
Monitoring
for
Web
Infrastructure.
Explanation:
The
administration
server
object
represents
one
or
more
WebSphere
for
z/OS
system
management
server
instances.
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
cannot
start
and
stop
systems
management
server
instances.
IZY1206E
A
shared
secret
value
for
z/OS
authentication
could
not
be
generated
and
written
to
the
z/OS
file
%1$s.
Explanation:
An
attempt
to
generate
a
secret
value
and
write
it
into
z/OS
HFS
directory
/var/itmwas
failed.
As
performance
metrics
are
collected
for
WebSphere
Application
Server
for
z/OS,
they
are
sent
to
the
resource
models
on
the
endpoint
over
a
TCP
connection.
The
z/OS
system
is
authenticated
by
the
endpoint
before
its
metrics
are
accepted.
The
authentication
mechanism
depends
on
an
identical
secret
value
known
by
both
the
endpoint
and
the
z/OS
system.
If
a
secret
value
is
not
already
in
place
on
the
endpoint,
the
Discover
WebSphere
Resources
task
and
the
Check
Administration
Server
Status
task
will
generate
a
secret
value
and
distribute
it
to
the
z/OS
system
over
the
NetView
NETCONV
connection.
Operator
Response:
Ensure
the
directory
permissions
for
/var/itmwas
allow
the
user
making
the
NetView
NETCONV
connection
to
create
files
in
that
directory.
IZY1197E
•
IZY1206E
80
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
IZY1207E
A
shared
secret
value
for
z/OS
authentication
could
not
be
written
to
the
endpoint
file
%1$s.
Explanation:
The
secret
value
was
generated
but
could
not
be
saved
in
a
file
on
the
endpoint
system.
As
performance
metrics
are
collected
for
WebSphere
Application
Server
for
z/OS,
they
are
sent
to
the
resource
models
on
the
endpoint
over
a
TCP
connection.
The
z/OS
system
is
authenticated
by
the
endpoint
before
its
metrics
are
accepted.
The
authentication
mechanism
depends
on
an
identical
secret
value
known
by
both
the
endpoint
and
the
z/OS
system.
If
a
secret
value
is
not
already
in
place
on
the
endpoint,
the
Discover
WebSphere
Resources
task
and
the
Check
Administration
Server
Status
task
will
generate
a
secret
value
and
distribute
it
to
the
z/OS
system
over
the
NetView
NETCONV
connection.
IZY1209E
The
System
Management
Interface
is
not
available.
Explanation:
A
WebSphere
System
Management
API
program
returned
an
error
while
issuing
a
command.
The
exact
cause
of
the
error
could
not
be
determined.
The
most
common
causes
are
listed
in
message
IZY1210E,
which
always
follows
this
message.
IZY1210E
The
most
common
causes
are
that
the
administration
server
is
down
or
that
the
user
ID
issuing
the
command
does
not
have
the
proper
authority
to
use
the
interface.
Explanation:
A
WebSphere
System
Management
API
program
returned
an
error
while
issuing
a
command
and
the
exact
cause
of
the
error
could
not
be
determined.
IZY1211E
This
task
can
only
be
run
against
z/OS
WebSphere
Application
Servers.
Explanation:
An
attempt
was
made
to
run
this
task
against
a
non-z/OS
WebSphere
Application
Server.
Operator
Response:
Run
the
task
again,
specifying
a
z/OS
WebSphere
Application
Server.
IZY1213E
The
event
adapter
did
not
start
or
is
still
starting.
Possible
reasons
include:
1-
ITDEVTAD
is
not
in
the
proclib
concatenation
2
-
There
is
a
syntax
error
in
one
of
the
configuration
files.
Explanation:
An
error
occurred
starting
the
event
adapter.
Operator
Response:
Ensure
that
ITDEVTAD
is
in
a
PDS
that
is
in
the
proclib
concatenation.
Check
the
trace_WebSphereAS_tecAdapter.log
file
on
the
endpoint
for
errors
and
run
the
task
again.
Contact
IBM
Software
Support
if
the
problem
persists.
IZY1214E
The
application
server
instance
%1$s
was
not
found.
Explanation:
The
IBM
WebSphere
Application
Server
for
z/OS
API
was
called
to
start,
stop,
or
get
status
from
an
application
server
instance,
and
that
API
failed.
The
server
name
or
server
instance
may
have
been
entered
incorrectly,
or
a
Tivoli
application
server
object
may
reference
a
server
instance
that
no
longer
exists.
Operator
Response:
If
a
Tivoli
object
contains
an
incorrect
server
or
server
instance
name,
it
must
be
deleted
and
recreated
by
running
the
Discover
WebSphere
Resources
task
or
creating
a
new
WSApplicationServer
object.
IZY1215E
Version
%1$s
is
not
a
supported
version
of
IBM
WebSphere
Application
Server
for
z/OS.
Explanation:
The
%1$s
version
of
IBM
WebSphere
Application
Server
for
z/OS
is
not
supported.
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
is
supported
with
IBM
WebSphere
Application
Server
version
4.0.1.
IZY1216E
This
task
requires
a
IWSDeploymentManager
object
type.
Explanation:
The
task
requires
an
IBM
WebSphere
Deployment
Manager
(IWSDeploymentManager)
object.
Operator
Response:
Run
the
task
again,
specifying
a
deployment
manager
object.
IZY1207E
•
IZY1216E
Chapter
5.
Understanding
warning
and
error
messages
81
IZY1217E
This
task
requires
a
IWSNodeAgent
object
type.
Explanation:
The
task
requires
an
IBM
WebSphere
Node
Agent
(IWSNodeAgent)
object.
Operator
Response:
Run
the
task
again,
specifying
a
node
agent
object.
IZY1218E
This
task
requires
a
WSApplicationServer
or
IWSApplicationServer
object
type.
Explanation:
The
task
requires
an
IBM
WebSphere
Application
Server
(WSApplicationServer,
IWSApplicationServer)
object.
Operator
Response:
Run
the
task
again,
specifying
an
application
server
object.
IZY1222E
Enterprise
Application
was
not
specified.
Explanation:
An
attempt
was
made
to
start
or
stop
an
enterprise
application
and
an
application
was
not
specified.
Operator
Response:
Rerun
the
task
specifying
the
application
to
start
or
stop.
IZY1225E
The
enterprise
application
%1$s
was
not
stopped:
%2$s
Explanation:
An
error
occurred
while
stopping
the
%1$s
application.
The
error
is
%2$s.
Operator
Response:
Check
the
error
log
for
the
task,
correct
the
problems,
if
possible,
and
run
the
task
again.
IZY1226E
The
enterprise
application
%1$s
was
not
started:
%2$s
Explanation:
An
error
occurred
while
starting
the
%1$s
application.
The
error
is
%2$s.
Operator
Response:
Check
the
error
log
for
the
task,
correct
the
problems,
if
possible,
and
run
the
task
again.
IZY1227E
This
task
requires
a
IWSApplicationServer
object
type.
Explanation:
The
task
requires
an
IBM
WebSphere
Application
Server
(IWSApplicationServer)
object.
Operator
Response:
Run
the
task
again,
specifying
an
application
server
object.
IZY1229E
Cannot
find
WebSphere
application
directory
%1$s.
The
Discover
WebSphere
Resources
task
will
stop.
Explanation:
The
Discover
WebSphere
Resources
task
cannot
locate
the
directory
that
contains
the
ear
files
for
installed
WebSphere
applications.
The
location
of
these
files
is
required
in
order
for
product
relationship
discovery
to
occur.
The
discover
process
was
halted.
IZY1230E
Cannot
connect
to
the
management
server
because
the
server
is
down
or
the
connector
port
is
incorrect.
Explanation:
The
task
scripting
client
cannot
connect
to
the
deployment
manager
or
application
management
server.
Possible
reasons
are
the
server
is
not
started
or
the
connector
port
is
incorrect.
Operator
Response:
Verify
the
deployment
manager
or
application
server
is
started
and
the
SOAP
port
is
correctly
set.
IZY1231W
This
task
requires
an
enterprise
application
be
specified.
Explanation:
The
task
requires
an
enterprise
application
be
specified.
Run
the
task
again,
specifying
an
enterprise
application.
Operator
Response:
Run
the
task
again,
specifying
an
enterprise
application.
IZY1217E
•
IZY1231W
82
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
IZY1234W
The
enterprise
application
%1$s
is
not
installed.
Explanation:
No
additional
help
is
available
for
this
message.
IZY1235E
The
enterprise
application
%1$s
did
not
start.
Check
the
application
server
logs.
Explanation:
An
error
occurred
while
starting
the
%1$s
application.
Operator
Response:
Check
the
application
server
log,
correct
the
problems,
if
possible,
and
run
the
task
again.
IZY1238E
WebSphere
for
z/OS
enterprise
applications
cannot
be
listed,
started
or
stopped
from
IBM
Tivoli
Monitoring
for
Web
Infrastructure.
Explanation:
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
cannot
list,
start
and
stop
enterprise
applications.
IZY1239E
The
task
cannot
be
run
against
an
application
server
that
has
been
federated.
Explanation:
The
task
cannot
be
run
against
an
application
that
has
been
federated.
IZY1240E
Cannot
establish
a
connection
to
the
server
on
endpoint
%1$s.
Possible
reasons
are
the
application
server
or
deployment
manager
is
not
started
or
the
connector
port
is
incorrect.
If
WebSphere
global
security
it
enabled,
ensure
that
the
provided
user
name
and
password
are
correct.
Refer
to
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
User’s
Guide
for
help
with
this
task
when
WebSphere
global
security
is
enabled.
Explanation:
The
client
cannot
connect
to
the
application
server
or
deployment
manager.
Possible
reasons
are
the
application
server
or
deployment
manager
is
not
started
or
the
connector
port
is
incorrect.
If
WebSphere
global
security
it
enabled,
ensure
that
the
provided
user
name
and
password
are
correct.
Refer
to
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
User’s
Guide
for
help
with
this
task
when
WebSphere
global
security
is
enabled.
Operator
Response:
Verify
that
the
application
server
or
deployment
manager
is
started
and
the
correct
SOAP
or
RMI
port
has
been
specified.
Verify
that
the
connector
port
value
specified
is
the
one
in
use
by
the
targeted
IBM
WebSphere
Application
Server
managed
process.
Try
using
the
SOAP_CONNECTOR_ADDRESS
value
for
the
primary
application
server
(usually
server1),
located
in
the
serverindex.xml
file
on
the
IBM
WebSphere
Application
Server
host
system.
IZY1243E
Failed
to
create
object
%1$s.
Verify
that
the
lcf
daemon
on
the
target
endpoint
is
installed,
running
and
able
to
communicate
with
the
Tivoli
management
region
server.
Explanation:
Ensure
the
lcf
daemon
process
is
installed
and
running
on
the
targeted
endpoint
system
before
re-executing
the
task.
Executing
wep
<ep_name>
status
from
a
Tivoli
sourced
prompt
on
the
Tivoli
management
region
server
results
in
the
message
″<ep_name>
is
alive″
if
the
lcf
daemon
is
installed
and
running.
IZY1246W
File
"%1$s"
is
not
found.
Explanation:
The
requested
log
file
was
not
found.
IZY1247E
The
application
server
%1$s
on
node
%2$s
is
not
running
or
unreachable.
If
you
are
starting
an
application
in
a
5.0
Network
Deployment
configuration
ensure
the
node
agent
is
started
before
you
attempt
to
start
the
application.
Explanation:
This
task
requires
that
the
application
server
be
running.
Operator
Response:
Start
the
application
server
%1$s
on
node
%2$s
and
run
the
task
again.
IZY1234W
•
IZY1247E
Chapter
5.
Understanding
warning
and
error
messages
83
IZY1252E
Unable
to
obtain
LCF
directory
from
endpoint
%1$s.
Verify
that
the
lcf
daemon
is
running
and
accessible
on
the
endpoint
in
question.
Explanation:
Unable
to
obtain
the
LCF
directory
from
endpoint.
The
LCF_DIR
variable
could
not
be
retrieved
from
the
endpoint.
Verify
that
the
lcf
daemon
is
running
and
accessible
on
the
endpoint
in
question.
Operator
Response:
Unable
to
obtain
the
LCF
directory
from
endpoint.
The
LCF_DIR
variable
could
not
be
retrieved
from
the
endpoint.
Verify
that
the
lcf
daemon
is
running
and
accessible
on
the
endpoint
in
question.
IZY1253E
The
Configure_Metrics_Gathering
task
was
unable
to
get
a
log
file
handle.
Explanation:
The
Configure_Metrics_Gathering
task
could
not
get
a
logger
object
from
IBM
Tivoli
Monitoring
for
Component
Services.
Operator
Response:
Check
the
arguments
and
run
the
task
again.
IZY1254E
The
Configure_Metrics_Gathering
task
was
unable
to
create
the
following
directory:
%1$s.
Explanation:
The
Configure_Metrics_Gathering
task
attempted
to
create
the
directory,
%1$s,
but
was
unable
to
do
so.
Operator
Response:
Ensure
that
the
userid
under
which
the
task
was
run
has
the
appropriate
permission
to
create
the
specified
directory.
IZY1255E
The
Configure_Metrics_Gathering
task
was
unable
to
copy
%1$s
to
%2$s.
Explanation:
The
Configure_Metrics_Gathering
task
attempted
to
copy
%1$s
to
%2$s,
but
was
unable
to
do
so.
Operator
Response:
Ensure
that
the
userid
under
which
the
task
was
run
has
the
appropriate
permission
to
copy
the
file.
IZY1256E
The
Configure_Metrics_Gathering
task
was
unable
to
read
the
current
configuration
in
%1$s.
Explanation:
The
Configure_Metrics_Gathering
task
attempted
to
read
the
current
configuration
from
%1$s,
but
was
unable
to
do
so.
Operator
Response:
Ensure
that
the
userid
under
which
the
task
was
run
has
the
appropriate
permission
to
read
the
file.
IZY1257E
The
Configure_Metrics_Gathering
task
was
unable
to
update
the
configuration
in
%1$s.
Explanation:
The
Configure_Metrics_Gathering
task
attempted
to
update
the
configuration
in
%1$s,
but
was
unable
to
do
so.
Operator
Response:
Ensure
that
the
userid
under
which
the
task
was
run
has
the
appropriate
permission
to
write
the
file.
IZY1258E
The
Configure_Metrics_Gathering
was
unable
to
update
the
current
PMI
configuration.
Explanation:
The
Configure_Metrics_Gathering
task
attempted
to
update
the
PMI
configuration
with
these
settings
$1%s,
but
was
unable
to
do
so.
Operator
Response:
Ensure
that
the
userid
from
which
the
task
was
run
has
authority
to
update
WebSphere
configuration
settings.
IZY1259E
A
shared
secret
value
for
z/OS
authentication
could
not
be
generated
and
written
to
the
z/OS
file
%1$s.
Explanation:
An
attempt
to
generate
a
secret
value
and
write
it
into
z/OS
HFS
directory
/var/itmwas
failed.
As
performance
metrics
are
collected
for
WebSphere
Application
Server
for
z/OS,
they
are
sent
to
the
resource
models
on
the
endpoint
over
a
TCP
connection.
The
connection
is
authenticated
by
the
endpoint
before
its
metrics
are
accepted.
The
authentication
mechanism
depends
on
an
identical
secret
value
known
by
both
the
endpoint
and
the
z/OS
system.
IZY1252E
•
IZY1259E
84
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
Operator
Response:
Ensure
the
directory
permissions
for
/var/itmwas
allow
the
user
running
the
task
to
create
files
in
that
directory.
IZY1260E
The
Configure_Metrics_Gathering
task
could
not
continue
because
the
arguments
were
incorrect.
Explanation:
The
Configure_Metrics_Gathering
task
received
incorrect
arguments.
Operator
Response:
Check
the
Reference
Guide
for
information
on
the
correct
set
of
arguments.
IZY1261E
Node
name
%1$s
was
not
found
in
the
WebSphere
domain.
The
Tivoli
object
was
created
with
an
invalid
node
name.
Explanation:
No
additional
help
is
available
for
this
message.
IZY1263W
The
application
%1$s
did
not
start.
Possible
reasons
include:
1-
The
enterprise
application
has
a
space
in
the
name
2
-
The
enterprise
application
is
clustered.
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
requires
WebSphere
Application
Server
5.0.1
or
greater
to
support
applications
with
a
space
in
the
name
or
clustered
applications.
Explanation:
An
error
occurred
while
starting
the
%1$s
application.
WebSphere
Application
Server
5.0.1
or
greater
is
required
for
clustered
enterprise
application
management
or
applications
with
a
space
in
the
name.
Operator
Response:
WebSphere
Application
Server
5.0.1
or
greater
is
required
for
clustered
enterprise
application
management
or
applications
with
a
space
in
the
name.
IZY1264W
The
application
%1$s
did
not
stop.
Possible
reasons
include:
1-
The
enterprise
application
has
a
space
in
the
name
2
-
The
enterprise
application
is
clustered.
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
requires
WebSphere
Application
Server
5.0.1
or
greater
to
support
applications
with
a
space
in
the
name
or
clustered
applications.
Explanation:
An
error
occurred
while
starting
the
%1$s
application.
WebSphere
Application
Server
5.0.1
or
greater
is
required
for
clustered
enterprise
application
management
or
applications
with
a
space
in
the
name.
Operator
Response:
WebSphere
Application
Server
5.0.1
or
greater
is
required
for
clustered
enterprise
application
management
or
applications
with
a
space
in
the
name.
IZY1266W
The
enterprise
application
%1$s
was
partially
started.
One
or
more
target
application
servers
were
not
available.
Explanation:
One
or
more
target
application
servers
were
not
started.
Modules
on
these
application
servers
did
not
start.
Operator
Response:
Start
all
the
target
application
servers
associated
with
this
application.
In
a
Network
Deployment
configuration
ensure
the
node
agents
are
started.
IZY1270E
The
Configure_Metrics_Gathering
task
cannot
disable
by
level.
Explanation:
The
level
flag
cannot
appear
when
the
function
is
DISABLE.
IZY1272E
Environment
not
set;
make
sure
setup_env.sh
or
setup_env.cmd
has
been
run.
Explanation:
The
Tivoli
environment
must
be
set
for
this
task
to
execute.
Be
sure
to
run
setup_env.sh
or
setup_env.cmd
to
set
the
BINDIR
environment
variable.
Operator
Response:
On
Windows,
execute
setup_env.cmd.
The
default
location
is
%windir%\system32\drivers\etc\Tivoli.
On
UNIX
systems,
execute
setup_env.sh.
The
default
location
is
/etc/Tivoli.
IZY1260E
•
IZY1272E
Chapter
5.
Understanding
warning
and
error
messages
85
IZY1274E
Could
not
find
object
with
label
%1$s
for
class
%2$s
Explanation:
A
WebSphere
Application
Server
object
could
not
be
found
with
the
name
of
the
label
specified.
Operator
Response:
Invoke
the
command
again,
and
specify
a
valid
WebSphere
Application
Server
object
label.
IZY1276W
Server
Log
Root
currently
not
set
Explanation:
No
value
is
currently
set
for
the
server
log
root
attribute
for
the
object
specified.
This
value
is
used
by
the
Application
Server
Resource
Use
resource
model.
If
the
value
is
not
set,
the
resource
model
will
not
execute
properly.
For
WebSphere
Application
Servers
3.5.x
and
4.0.x
servers,
the
path
must
be
set
to
the
path
where
the
trace
log
file
is
located.
For
example,
/websphere/logs/tracefile.
For
WebSphere
Application
Servers
5.x,
the
path
must
be
set
to
the
path
were
the
<server
name>.pid
file
is
located.
For
example,
/websphere/logs/server1.
IZY1278E
Error
setting
Server
Log
Root,
rc=%1$s
Explanation:
For
WebSphere
Application
Servers
3.5.x
and
4.0.x,
the
return
code
listed
is
from
making
an
idlcall
with
the
update_context
method.
For
WebSphere
Application
Servers
5.x,
the
return
code
listed
is
from
making
an
idlcall
with
the
_set_WASServerLogRoot
method.
Operator
Response:
Look
up
the
error
code.
If
unable
to
determine
the
cause,
contact
IBM
Software
Support.
IZY1279E
Unable
to
resolve
the
fully
qualified
hostname
for
an
endpoint
address.
Verify
that
the
network
connection
is
functioning
properly
and
that
a
valid
Domain
Name
Server
is
configured
for
TCP/IP.
If
the
Discover_WebSphere_Resources
task
was
targeting
a
Deployment
Manager,
the
hostname
resolution
problem
should
be
fixed
in
order
for
the
task
to
succeed.
Explanation:
Verify
that
the
Tivoli
management
region
server
or
managed
node
is
network
attached
and
that
the
network
connection
is
functioning
properly.
Verify
that
a
valid
Domain
Name
Server
is
configured
and
accessible
via
TCP/IP.
If
the
Discover_WebSphere_Resources
task
was
targeting
a
Deployment
Manager,
the
host
name
resolution
problem
should
be
fixed
in
order
for
the
task
to
succeed.
Operator
Response:
Verify
that
the
Tivoli
management
region
server
or
managed
node
is
network
attached
and
that
the
network
connection
is
functioning
properly.
Verify
that
a
valid
Domain
Name
Server
is
configured
and
accessible
via
TCP/IP.
If
the
Discover_WebSphere_Resources
task
was
targeting
a
Deployment
Manager,
the
host
name
resolution
problem
should
be
fixed
in
order
for
the
task
to
succeed.
IZY1280E
A
connection
was
established
to
a
WebSphere
Application
Server
admin
service
located
at
a
WebSphere
Application
Server
product
install
path
other
than
the
specified
or
default
product
install
path.
Please
verify
that
the
connector
port
value
for
the
targeted
WebSphere
Application
Server
managed
process
matches
the
value
in
use
by
the
managed
process
at
either
the
specified
or
default
product
installation
path.
Explanation:
Verify
that
the
connector
port
value
specified
is
the
one
in
use
by
the
targeted
WebSphere
Application
Server
managed
process.
Try
using
the
SOAP_CONNECTOR_ADDRESS
value
for
the
primary
application
server
(normally
server1)
located
in
the
serverindex.xml
file
on
the
WAS
host
system.
Operator
Response:
Verify
that
the
connector
port
value
specified
is
the
one
in
use
by
the
targeted
WebSphere
Application
Server
managed
process.
Try
using
the
SOAP_CONNECTOR_ADDRESS
value
for
the
primary
application
server
(normally
server1)
located
in
the
serverindex.xml
file
on
the
WAS
host
system.
IZY1447E
Host
name
"%7$s"
is
not
valid.
Explanation:
The
host
name
%7$s
is
not
valid.
Operator
Response:
Run
the
task
or
command
again,
specifying
a
valid
host
name.
IZY1448E
Administration
port
"%7$s"
is
not
valid.
Explanation:
The
administration
port
is
not
valid.
Operator
Response:
Run
the
task
or
command
again,
specifying
a
valid
administration
port.
IZY1274E
•
IZY1448E
86
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
IZY1449E
The
IBM
WebSphere
Application
Server
version
is
required.
Explanation:
The
IBM
WebSphere
Application
Server
version
is
required.
Operator
Response:
Run
the
task
or
command
again,
specifying
the
IBM
WebSphere
Application
Server
version.
IZY1450E
The
IBM
WebSphere
Application
Server
version
"%7$s"
is
not
valid.
Explanation:
The
IBM
WebSphere
Application
Server
version
is
not
valid.
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
IBM
WebSphere
Application
Server
is
supported
with
IBM
WebSphere
Application
Server
versions
4.x.x.
IZY1451E
The
IBM
WebSphere
Application
security
flag
is
required.
Explanation:
The
IBM
WebSphere
Application
Server
security
flag
is
required.
Operator
Response:
Run
the
task
or
command
again,
specifying
the
security
flag.
IZY1452E
The
IBM
WebSphere
Application
Server
security
flag,"%7$s",
is
not
valid.
Explanation:
The
IBM
WebSphere
Application
Server
security
flag,
%7$s,
is
not
valid.
Operator
Response:
Run
the
task
or
command
again,
specifying
a
valid
security
flag.
IZY1453E
The
IBM
WebSphere
Application
Server
property
file
name
is
required.
Explanation:
The
IBM
WebSphere
Application
Server
property
file
name
is
required.
Operator
Response:
Run
the
task
or
command
again,
specifying
the
property
file
name.
IZY1454E
The
IBM
WebSphere
Application
Server
property
file
"%7$s"
is
not
valid.
Explanation:
The
IBM
WebSphere
Application
Server
property
file
is
not
valid.
Operator
Response:
Run
the
task
or
command
again,
specifying
a
valid
property
file.
IZY1455E
The
IBM
WebSphere
Application
Server
installation
path
is
required.
Explanation:
The
IBM
WebSphere
Application
Server
installation
path
is
required.
Operator
Response:
Run
the
task
or
command
again,
specifying
the
IBM
WebSphere
Application
Server
installation
path.
IZY1456E
The
IBM
WebSphere
Application
Server
installation
path
"%7$s"
is
not
valid.
Explanation:
The
installation
path
%7$s
does
not
exist
on
the
endpoint.
The
task
is
unable
to
continue
processing
since
it
cannot
determine
sufficient
IBM
WebSphere
Application
Server
information.
The
directory
might
have
been
deleted
or
IBM
WebSphere
Application
Server
might
have
been
removed
from
the
machine.
Operator
Response:
Check
that
IBM
WebSphere
Application
Server
is
installed
and
that
the
directory
exists.
If
the
directory
does
not
exist,
reinstall
the
IBM
WebSphere
Application
Server
components.
If
the
directory
does
exist,
contact
IBM
Software
Support.
IZY1457E
The
IBM
WebSphere
Application
Server
operating
system
type
is
required.
Explanation:
You
must
specify
the
operating
system
for
the
IBM
WebSphere
Application
Server.
Operator
Response:
Run
the
task
or
command
again,
specifying
the
operating
system
type.
IZY1449E
•
IZY1457E
Chapter
5.
Understanding
warning
and
error
messages
87
IZY1458E
The
IBM
WebSphere
Application
Server
operating
system
"%7$s"
is
not
valid.
Explanation:
The
operating
system
for
the
IBM
WebSphere
Application
Server
is
not
valid.
Operator
Response:
Run
the
task
again,
specifying
an
endpoint
with
a
valid
operating
system.
IZY1459E
The
IBM
WebSphere
Application
Server
node
name
is
required.
Explanation:
The
IBM
WebSphere
Application
Server
node
name
is
required.
Operator
Response:
Run
the
task
or
command
again,
specifying
a
valid
IBM
WebSphere
Application
Server
node
name.
IZY1460E
The
IBM
WebSphere
Application
Server
node
name
"%7$s"
is
not
valid.
Explanation:
The
IBM
WebSphere
Application
Server
node
name
specified
is
not
valid.
Operator
Response:
Run
the
task
or
command
again,
specifying
a
valid
IBM
WebSphere
Application
Server
node
name.
IZY1461E
The
IBM
WebSphere
Application
Server
name
is
required.
Explanation:
The
IBM
WebSphere
Application
Server
name
is
required.
Operator
Response:
Run
the
task
or
command
again,
specifying
the
name
of
the
IBM
WebSphere
Application
Server.
IZY1468E
The
fully
qualified
host
name
is
required.
Explanation:
The
fully
qualified
host
name
is
required.
Operator
Response:
Run
the
task
or
command
again,
specifying
the
fully
qualified
host
name.
IZY1485E
The
sysplex
name
is
required
when
the
object
being
created
represents
a
server
on
WebSphere
for
z/OS.
Explanation:
The
z/OS
sysplex
name
is
required.
This
should
be
the
same
as
the
sysplex
name
configured
in
WebSphere
for
z/OS.
Operator
Response:
Run
the
task
or
command
again,
specifying
a
valid
IBM
WebSphere
Application
Server
sysplex
name.
IZY1486E
The
system
name
as
configured
in
IBM
WebSphere
Application
Server
is
required
when
the
object
being
created
represents
a
server
on
WebSphere
for
z/OS.
Explanation:
The
z/OS
system
name
is
required.
This
should
be
the
same
as
the
system
name
configured
in
WebSphere
for
z/OS.
Operator
Response:
Run
the
task
or
command
again,
specifying
a
valid
z/OS
system
name.
If
the
IBM
WebSphere
Application
Server
instance
being
monitored
is
installed
on
the
endpoint,
then
leave
the
z/OS
Application
Server
Instance
Name
and
the
z/OS
System
Name
blank.
IZY1487E
The
name
of
the
host
running
WebSphere
for
z/OS
must
be
specified
and
the
type
of
host
name
must
be
selected.
Explanation:
The
WebSphere
Application
Server
focal
point
is
the
z/OS
host
that
is
contacted
to
query
information
from
or
perform
operations
on
WebSphere
for
z/OS.
IZY1488E
%7$s
is
not
a
valid
protocol.
Valid
values
are
IP
and
SNA.
Explanation:
A
valid
value
must
be
specified.
Operator
Response:
Specify
″IP″
if
NetView
for
z/OS
uses
TCP/IP
to
contact
the
WebSphere
Application
Server
focal
point
host.
Specify
″SNA″
if
NetView
for
z/OS
uses
Systems
Network
Architecture
(SNA)
to
reach
the
host.
IZY1458E
•
IZY1488E
88
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
IZY1490E
The
server
instance
name
is
required
when
the
object
being
created
represents
a
server
on
WebSphere
for
z/OS.
Explanation:
This
is
the
name
of
the
WebSphere
for
z/OS
server
instance.
Operator
Response:
If
the
WebSphere
Application
Server
instance
being
monitored
is
installed
on
the
endpoint,
leave
the
z/OS
Application
Server
Instance
Name
and
the
z/OS
System
Name
blank.
IZY1491E
The
fully
qualified
host
name
of
the
endpoint
is
required.
Explanation:
The
fully
qualified
host
name
of
the
endpoint
is
required.
Operator
Response:
Run
the
task
or
command
again,
specifying
the
fully
qualified
endpoint
host
name.
IZY1492E
Choose
’Local’
if
IBM
WebSphere
Application
Server
is
installed
on
the
endpoint
or
’z/OS’
if
IBM
WebSphere
Application
Server
is
running
on
a
z/OS
system.
Explanation:
IBM
WebSphere
Application
Server
can
be
installed
and
running
locally
on
the
endpoint
specified,
or
it
can
be
running
on
a
z/OS
host.
Operator
Response:
Specify
where
the
instance
of
IBM
WebSphere
Application
Server
that
you
want
to
monitor
is
installed.
IZY1493E
The
sysplex
name
(the
-j
option)
is
required
when
the
object
being
created
represents
a
server
on
WebSphere
for
z/OS.
It
is
used
as
the
node
name,
so
the
-t
option
should
not
be
specified.
Explanation:
The
z/OS
sysplex
name
is
required.
This
should
be
the
same
as
the
sysplex
name
configured
in
WebSphere
for
z/OS.
Operator
Response:
Run
the
task
or
command
again,
specifying
a
valid
IBM
WebSphere
Application
Server
sysplex
name.
IZY1494E
The
name
of
the
host
running
WebSphere
for
z/OS
(-f
option)
must
be
specified.
The
type
of
the
host
name
should
be
specified
with
the
-n
option
(type
IP
is
the
default).
Explanation:
The
WebSphere
Application
Server
focal
point
is
the
z/OS
host
that
is
contacted
to
query
information
from
or
perform
operations
on
the
WebSphere
Application
Server
for
z/OS.
IZY1495E
The
sysplex
or
z/OS
host
name
must
not
be
specified
when
the
operating
system
is
not
’zos’.
Explanation:
The
sysplex
applies
only
to
z/OS
systems.
The
focal
point
host
identifies
a
z/OS
host
that
is
running
WebSphere
for
z/OS.
Operator
Response:
Neither
option
should
be
specified
when
IBM
WebSphere
Application
Server
is
installed
on
the
endpoint
and
is
not
on
z/OS.
IZY1496E
You
must
specify
a
user
id
and
password
or
disable
security.
Explanation:
One
of
these
two
actions
must
be
done
in
order
to
update
the
WebSphere
Object.
Operator
Response:
Specify
the
user
id
or
password
or
disable
WebSphere
security
so
a
userid
and
password
are
not
needed.
IZY1499E
The
attribute
%1$s
was
not
updated.
Explanation:
An
error
occurred
while
attempting
to
update
an
attribute.
The
new
value
was
not
stored.
Operator
Response:
Refer
to
the
trace_itmwas_update_attributes_cb.log
file
to
determine
what
exception
the
idlcall
command
generated
when
it
called
the
_set_xxxxx
method.
If
there
is
an
exception,
it
might
indicate
why
the
idlcall
command
returned
a
non-zero
return
code.
Resolve
the
exception
and
try
the
operation
again.
If
the
problem
persists
please
contact
IBM
Software
Support.
IZY1490E
•
IZY1499E
Chapter
5.
Understanding
warning
and
error
messages
89
IZY1500E
You
specified
more
than
one
operation.
The
following
lists
the
specified
operations:
[]
Explanation:
Only
one
operation
can
be
specified.
Operator
Response:
Specify
only
one
operation.
IZY1501E
You
specified
the
following
incorrect
parameters:
[]
Explanation:
You
must
specify
valid
parameters.
Operator
Response:
Specify
valid
parameters.
IZY1502E
You
specified
the
following
extra
arguments:
[]
Explanation:
No
additional
help
is
available
for
this
message.
IZY1503E
The
specified
command
is
missing
parameters.
The
following
lists
the
command
specified:
[]
Explanation:
No
additional
help
is
available
for
this
message.
IZY1504E
wwebsphere
is
the
command
line
interface
to
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure,
IBM
WebSphere
Application
Server
Product.
Create
WebSphere
Object
Operations
----------------------------------
wwebsphere
-CreateDeployMgr
wwebsphere
-CreateNodeAgent
wwebsphere
-CreateAppServer
wwebsphere
-c
View
WebSphere
Object
Attributes
-----------------------------------
wwebsphere
-g
Delete
a
WebSphere
Object
-----------------------------------
wwebsphere
-d
For
more
detailed
usage
information,
enter
one
of
the
above
commands
Example:
wwebsphere
-CreateDeployMgr
Explanation:
No
additional
help
is
available
for
this
message.
IZY1505E
Create
a
WebSphere
Deployment
Manager
object.
usage:
wwebsphere
-CreateDeployMgr
[ATTRIBUTE_FLAGS]...
required
attribute
flags:
-cellName
<cell_name>
Cell
name
for
Deployment
Manager
-nodeName
<websphere_node_name>
Node
name
for
Deployment
Manager
-version
<websphere_version>
WebSphere
product
version
(e.g.
5.0.1)
-rootDirectory
<websphere_install_path>
Full
path
to
the
WebSphere
Network
Deployment
product
installation
(e.g.
/usr/WebSphere/DeploymentManager)
-hostname
<fully_qualified_host_name>
Fully
qualified
host
name
for
system
on
which
the
WebSphere
managed
resource
resides
-endpoint
<endpoint_label>
Tivoli
endpoint
name
on
which
the
WebSphere
managed
resource
resides
-policyRegion
<policy_region>
Tivoli
policy
region
in
this
Tivoli
region
that
this
object
IZY1500E
•
IZY1505E
90
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
should
be
placed
in
optional
attribute
flags:
-user
name
<websphere_username>
Valid
user
name
for
current
WebSphere
User
Registry
-password
<websphere_password>
Valid
password
for
provided
user
name
-port
<connector_port>
Connector
port
address
for
Deployment
Manager
-connectType
<connect_type>
The
preferred
protocol
for
JMX
communication
over
the
port
specified
with
the
-port
flag.
Specify
SOAP.
The
default
value
is
SOAP
-osType
<os_type>
Operating
system
type
that
the
WebSphere
managed
resource
is
running
under.
Enter
a
descriptive
label
of
your
choice
or
don’t
specify
this
option
flag.
-mnName
<mnName>
Target
managed
node
in
the
Tivoli
region
for
this
object
Explanation:
No
additional
help
is
available
for
this
message.
IZY1506E
Create
a
WebSphere
Node
Agent
object.
usage:
wwebsphere
-CreateNodeAgent
[ATTRIBUTE_FLAGS]...
required
attribute
flags:
-deployMgr
<deployment_manager_label>
TME
object
label
of
the
Deployment
Manager
object
associated
with
this
managed
resource.
This
label
should
be
provided
in
the
form
of
DeploymentMgr@<cellName>@<nodeName>
-nodeName
<websphere_node_name>
Node
name
for
this
Node
Agent
-version
<websphere_version>
WebSphere
product
version
(e.g.
5.0.1)
-rootDirectory
<websphere_install_path>
Full
path
to
the
WebSphere
Application
Server
product
installation
directory
(e.g.
/usr/WebSphere/ApplicationServer)
-hostname
<fully_qualified_host_name>
Fully
qualified
host
name
for
system
on
which
the
WebSphere
managed
resource
resides
-endpoint
<endpoint_label>
Tivoli
endpoint
name
on
which
the
WebSphere
managed
resource
resides
optional
attribute
flags:
-policyRegion
<policy_region>
Tivoli
policy
region
in
this
Tivoli
region
that
this
object
should
be
placed
in.
If
not
provided,
this
object
will
be
placed
in
the
parent
DeploymentManager’s
policy
region.
-user
name
<websphere_username>
Valid
user
name
for
current
WebSphere
User
Registry
-password
<websphere_password>
Valid
password
for
provided
user
name
-port
<connector_port>
Connector
port
address
for
Node
Agent
-connectType
<connect_type>
The
preferred
protocol
for
JMX
communication
over
the
port
specified
with
the
-port
flag.
Specify
SOAP.
The
default
value
is
SOAP
-osType
<os_type>
Operating
system
type
that
the
WebSphere
managed
resource
is
running
under.
Enter
a
descriptive
label
of
your
choice
or
don’t
specify
this
option
flag.
IZY1506E
Chapter
5.
Understanding
warning
and
error
messages
91
-mnName
<mnName>
Target
managed
node
in
the
Tivoli
region
for
this
object
Explanation:
No
additional
help
is
available
for
this
message.
IZY1507E
Create
a
WebSphere
Application
Server
object.
usage:
wwebsphere
-CreateAppServer
[ATTRIBUTE_FLAGS]...
required
attribute
flags:
-serverName
<server_name>
Name
of
WebSphere
Application
Server
-cellName
<cell_name>
Cell
name
for
this
Application
Server
-nodeName
<websphere_node_name>
Node
name
for
this
Application
Server
-version
<websphere_version>
WebSphere
product
version
(e.g.
5.0.1)
-rootDirectory
<websphere_install_path>
Full
path
to
the
WebSphere
Application
Server
product
installation
(e.g.
/usr/WebSphere/ApplicationServer)
-hostname
<fully_qualified_host_name>
Fully
qualified
host
name
for
system
on
which
the
WebSphere
managed
resource
resides
-endpoint
<endpoint_label>
Tivoli
endpoint
name
on
which
the
WebSphere
managed
resource
resides
optional
attribute
flags:
-policyRegion
<policy_region>
Tivoli
policy
region
in
this
Tivoli
region
that
this
non-federated
Application
Server
object
should
be
placed
in
If
omitted,
the
default
is
’WebSphere
Application
Servers’
policy
region.
This
option
flag
is
ignored
when
the
-nodeAgent
option
flag
is
used.
Explanation:
No
additional
help
is
available
for
this
message.
IZY1508E
-clusterName
<websphere_cluster_name>
The
WebSphere
cluster
name
if
this
application
server
is
a
cluster
member.
If
omitted,
the
default
is
STANDALONE
-serverLogRoot
<websphere_server_log_root>
The
log
directory
for
this
WebSphere
application
server.
If
omitted,
the
default
is
<websphere_install_path>/logs/<server_name>
-nodeAgent
<node_agent_label>
TME
object
label
of
the
Node
Agent
object
associated
with
this
managed
resource.
This
label
should
be
provided
in
the
form
of
NodeAgent@<cellName>@<nodeName>
-express
{TRUE
|
FALSE}
Specify
TRUE
if
this
Application
Server
is
operating
in
a
WebSphere
Application
Server
Express
product
environment
If
omitted,
the
default
is
FALSE
-hasWebModule
{TRUE
|
FALSE}
If
TRUE,
this
Application
Server
is
using
the
web
module
and
is
capable
of
hosting
servlets.
If
omitted,
the
default
is
TRUE
-hasEJBModule
{TRUE
|
FALSE}
If
TRUE,
this
Application
Server
is
using
the
Enterprise
Java
Beans
module
and
is
capable
of
hosting
EJB’s.
If
omitted,
the
default
is
TRUE
-user
name
<websphere_username>
Valid
user
name
for
current
WebSphere
User
Registry
IZY1507E
•
IZY1508E
92
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
-password
<websphere_password>
Valid
password
for
provided
user
name
-port
<connector_port>
Connector
port
address
for
Application
Server
-connectType
<connect_type>
The
preferred
protocol
for
JMX
communication
over
the
port
specified
with
the
-port
flag.
Specify
SOAP.
The
default
value
is
SOAP
-osType
<os_type>
Operating
system
type
that
the
WebSphere
managed
resource
is
running
under.
Enter
a
descriptive
label
of
your
choice
or
don’t
specify
this
option
flag.
-mnName
<mnName>
Target
managed
node
in
the
Tivoli
region
for
this
object
Explanation:
No
additional
help
is
available
for
this
message.
IZY1509E
WebSphere
server
name
"%7$s"
is
not
valid.
Explanation:
The
WebSphere
server
name
%7$s
is
not
valid.
Run
the
task
or
command
again,
specifying
a
valid
WebSphere
server
name.
Operator
Response:
IZY1510E
The
WebSphere
node
name
is
required.
Explanation:
The
WebSphere
node
name
is
required.
Operator
Response:
Run
the
task
or
command
again,
specifying
the
WebSphere
node
name.
IZY1511E
WebSphere
node
name
"%7$s"
is
not
valid.
Explanation:
The
WebSphere
node
name
%7$s
is
not
valid.
Operator
Response:
Run
the
task
or
command
again,
specifying
a
valid
WebSphere
node
name.
IZY1512E
The
WebSphere
cell
name
is
required.
Explanation:
The
WebSphere
cell
name
is
required.
Operator
Response:
Run
the
task
or
command
again,
specifying
the
WebSphere
cell
name.
IZY1513E
WebSphere
cell
name
"%7$s"
is
not
valid.
Explanation:
The
WebSphere
cell
name
%7$s
is
not
valid.
Operator
Response:
Run
the
task
or
command
again,
specifying
a
valid
WebSphere
cell
name.
IZY1514E
Failed
to
create
the
WebSphere
Application
Server
object
().
The
object
already
exists.
Explanation:
The
specified
WebSphere
Application
Server
already
exists.
IZY1517E
You
did
not
enter
a
valid
parameter
value()
for
the
boolean
parameter.
Explanation:
You
must
enter
a
valid
parameter
value
for
the
boolean
parameter.
Operator
Response:
Enter
a
valid
parameter.
IZY1509E
•
IZY1517E
Chapter
5.
Understanding
warning
and
error
messages
93
IZY1518E
The
Deployment
Manager
Tivoli
label
is
required.
Explanation:
The
Deployment
Manager
Tivoli
label
is
required.
Operator
Response:
Run
the
task
or
command
again,
specifying
the
WebSphere
cell
name.
IZY1519E
The
WebSphere
server
name
is
required.
Explanation:
The
WebSphere
server
name
is
required.
Operator
Response:
Run
the
task
or
command
again,
specifying
the
WebSphere
server
name.
IZY1528E
usage:
wwebsphere
-c
-h
fully_qualified_host_name
-e
endpoint_name
-p
policy_region
[-m
managed_node]
-t
node_name
[-u
admin_port_number]
-v
websphere_version
[-w
websphere_security_enabled
-x
websphere_security_properties_file]
-y
websphere_install_path
[-z
os_type]
\n\n
OR
\n\nwwebsphere
-c
-h
fully_qualified_endpoint_host_name
-e
endpoint_name
-p
policy_region
[-m
managed_node]
-v
websphere_version
[-y
websphere_install_path]
-z
zos
-j
zos_sysplex
-f
zos_was_focal_point
[-n
zos_was_focal_point_protocol]
\n\n
OR
\n\nwwebsphere
-c
-a
app_server_name
-b
admin_server_label
-e
endpoint_name
[-r
has_web_module]
[-s
has_ejb_module]
[-m
managed_node]
\n\n
OR
\n\nwwebsphere
-c
-a
app_server_and_instance_names
-b
admin_server_label
-e
endpoint_name
[-r
has_web_module]
[-s
has_ejb_module]
[-m
managed_node]
[-j
zos_system]
Explanation:
The
wwebsphere
command
with
the
-c
parameter
is
used
to
create
IBM
WebSphere
Application
Server
objects.
This
message
provides
the
correct
syntax
to
create
an
IBM
WebSphere
application
server
object.
IZY1529E
You
must
select
a
node
agent
to
be
associated
with
this
application
server
or
not
use
Network
Deployment
for
this
application
server.
Explanation:
Select
a
node
agent
to
update
the
WebSphere
Object,
or
select
No
Network
Deployment
so
an
associated
node
agent
is
not
required.
Operator
Response:
You
must
either
select
a
node
agent
or
select
No
Network
Deployment.
IZY1532E
A
request
was
made
to
list
the
attributes
for
all
the
objects
with
the
resource
type
of
().
Please
re-try
the
command,
this
time
specifying
one
resource
type
from
the
set
{
IWSDeploymentManager,
IWSNodeAgent,
IWSApplicationServer,
WSAdministrationServer,
WSApplicationServer
}.
Explanation:
An
incorrect
resource
type
was
specified
when
trying
to
list
the
attributes
for
all
objects
of
that
type.
Please
re-try
the
command,
this
time
specifying
one
resource
type
from
the
set
{
IWSDeploymentManager,
IWSNodeAgent,
IWSApplicationServer,
WSAdministrationServer,
WSApplicationServer
}.
Operator
Response:
Re-try
the
command
specifying
a
valid
resource
type
name.
IZY1624E
Port
number
%1$s
is
not
valid;
must
be
between
1
and
65535.
Explanation:
This
task
requires
that
the
port
number
be
in
the
range
1
to
65535.
Operator
Response:
Run
the
task
again,
specifying
a
port
number
in
the
range
of
1
to
65535.
IZY1625E
Task
failed.
Explanation:
The
task
failed
to
complete
successfully.
Operator
Response:
Check
additional
task
messages.
Correct
any
problems
and
run
the
task
again.
IZY1627E
This
task
is
only
supported
on
Windows
endpoints.
Explanation:
The
service
must
be
installed
on
a
Microsoft
Windows
NT
or
Windows
2000
endpoint.
Operator
Response:
Run
the
task
again,
specifying
a
Windows
NT
or
Windows
2000
endpoint.
IZY1518E
•
IZY1627E
94
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
IZY1634E
A
valid
host
name
is
required
when
run
against
an
endpoint.
Explanation:
You
did
not
specify
a
host
name.
Operator
Response:
Run
the
task
again,
specifying
a
host
name.
IZY1638E
Only
LCF
endpoints
are
supported.
Explanation:
The
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
IBM
WebSphere
Application
Server
task
was
deployed
to
a
Tivoli
managed
node
or
gateway.
This
task
can
only
be
deployed
to
Tivoli
endpoints.
Operator
Response:
Run
the
task
again,
specifying
a
Tivoli
endpoint
as
the
target
of
the
task.
IZY1640E
IBM
WebSphere
Application
Server
registry
path
not
found.
Explanation:
The
registry
path
does
not
exist
on
the
UNIX
endpoint.
The
discovery
task
is
unable
to
continue
processing
because
it
cannot
determine
sufficient
IBM
WebSphere
Application
Server
information.
The
directory
might
have
been
deleted
or
IBM
WebSphere
Application
Server
might
have
been
removed
from
the
system.
Operator
Response:
Ensure
that
IBM
WebSphere
Application
Server
is
installed
and
that
the
directory
exists.
If
the
directory
does
not
exist,
reinstall
the
IBM
WebSphere
Application
Server
components.
If
the
directory
does
exist,
contact
IBM
Software
Support.
IZY1746W
Unable
to
create
object
"%1$s".
Explanation:
During
IBM
WebSphere
Application
Server
component
discovery,
a
non-zero
return
code
was
returned
from
the
call
to
define
the
IBM
WebSphere
Application
Server
component
to
Tivoli.
This
message
can
occur
if
the
component
is
already
defined
to
Tivoli.
Operator
Response:
Check
additional
messages.
If
the
component
was
already
defined
to
Tivoli,
no
further
action
is
required.
If
the
component
was
not
already
defined
to
Tivoli,
save
the
discovery
task
log
and
contact
IBM
Software
Support.
IZY1755W
Error
getting
IP
address
for
host
name
"%1$s",
using
"0.0.0.0".
Explanation:
The
task
could
not
resolve
the
IP
address
of
the
target
system’s
host
name.
A
default
IP
address
is
being
used.
Operator
Response:
If
the
default
IP
address
is
not
correct,
correct
the
target
system
so
that
the
nslookup
command
returns
a
valid
IP
address
for
host
name
%1$s,
then
uninstall
and
reinstall
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
IBM
WebSphere
Application
Server
event
adapter.
IZY1804E
USS_BINDIR
must
be
defined
on
OS/390.
Explanation:
No
additional
help
is
available
for
this
message.
IZY1805E
Cannot
find
setup_env.sh.
Explanation:
No
additional
help
is
available
for
this
message.
IZY1808E
Unexpected
error
from
an
idlcall:
"%1$s"
Explanation:
No
additional
help
is
available
for
this
message.
IZY1819E
Module
IHSMDSCV
not
installed
on
host
"%1$s"
Explanation:
No
additional
help
is
available
for
this
message.
IZY1634E
•
IZY1819E
Chapter
5.
Understanding
warning
and
error
messages
95
IZY1820E
No
SSID
for
Queue
Manager
"%1$s"
for
broker
"%2$s"
on
host
"%3$s"
Explanation:
No
additional
help
is
available
for
this
message.
IZY1821W
No
object
created
for
"%1$s"
Explanation:
No
additional
help
is
available
for
this
message.
IZY1827W
No
members
discovered,
nothing
will
be
done.
Explanation:
No
additional
help
is
available
for
this
message.
IZY2001E
A
file
must
be
selected.
Explanation:
You
requested
to
retrieve
or
delete
a
log
file,
but
you
did
not
select
a
file
name.
Operator
Response:
Select
a
file
name
and
run
the
request
again.
IZY2003W
An
error
occurred
while
deleting
file
"%1$s".
Explanation:
A
request
was
made
to
delete
the
specified
log
file.
An
error
occurred
during
processing.
This
message
is
followed
by
an
error
log
of
the
delete
function.
Operator
Response:
Examine
the
error
log
to
determine
the
cause
of
the
failure
and
run
the
task
again.
IZY2023W
Stopping
administration
server.
Explanation:
A
request
was
made
to
stop
an
IBM
WebSphere
administration
server.
IZY2024W
Stopping
application
server.
Explanation:
A
request
was
made
to
stop
an
IBM
WebSphere
application
server.
IZY2025W
Stopping
deployment
manager.
Explanation:
A
request
was
made
to
stop
an
IBM
WebSphere
deployment
manager.
IZY2026W
Stopping
node
agent.
Explanation:
A
request
was
made
to
stop
an
IBM
WebSphere
node
agent.
IZY2051E
Unrecognized
callback
request:
%1$s.
Explanation:
An
internal
error
occurred.
Operator
Response:
Contact
IBM
Software
Support.
IZY2052E
No
implementation
for
callback
request
%1$s.
Explanation:
An
internal
error
occurred.
The
specified
callback
request
requires
an
implementation
script
that
cannot
be
found.
Operator
Response:
Examine
subsequent
error
messages
to
determine
the
file
name
needed
and
its
location.
If
possible,
replace
the
file
from
a
backup
copy.
If
this
problem
occurred
immediately
after
product
installation,
contact
IBM
Software
Support.
IZY2053E
File
"%1$s"
not
found.
Explanation:
Additional
information
for
message
IZY2052E.
Operator
Response:
Refer
to
message
IZY2052E.
IZY1820E
•
IZY2053E
96
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
IZY2054E
Searching
in
directory
"%1$s".
Explanation:
Additional
information
for
message
IZY2052E.
Operator
Response:
Refer
to
message
IZY2052E.
IZY2056E
An
error
occurred
while
running
task
"%1$s"
from
library
"%2$s".
Explanation:
An
error
occurred
while
running
%1$s
from
library
%2$s.
If
Tivoli
logging
is
enabled,
the
log
file
associated
with
this
callback
is
displayed.
Operator
Response:
Ensure
that
Tivoli
logging
is
enabled.
Check
the
log
file
for
wruntask
errors.
The
referenced
error
will
be
near
the
end
of
the
log
file.
If
this
is
not
an
environment
problem,
save
the
log
file
and
contact
IBM
Software
Support.
IZY2057E
Incorrect
object
type
%1$s.
Explanation:
A
callback
function
was
called
in
the
context
of
an
object
of
type
%1$s.
This
object
type
is
not
supported
by
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
callbacks.
Ensure
that
Tivoli
logging
is
enabled.
Save
the
log
file
associated
with
this
callback.
Contact
IBM
Software
Support.
IZY2066E
An
error
occurred
while
posting
dialog
"%1$s".
Explanation:
An
error
occurred
while
posting
a
callback
dialog.
If
Tivoli
logging
is
enabled,
the
log
file
associated
with
this
callback
is
displayed.
Operator
Response:
Ensure
that
Tivoli
logging
is
enabled.
Check
the
log
file
for
wpostdialog
errors.
The
referenced
error
will
be
near
the
end
of
the
log
file.
If
this
is
not
an
environment
problem,
save
the
log
file
and
contact
IBM
Software
Support.
IZY2067E
The
witmcsdispout
utility
could
not
open
file
"%1$s".
Explanation:
The
witmcsdispout
utility
was
called
with
a
request
to
the
contents
of
file
%1$s,
but
the
file
could
not
be
opened.
Operator
Response:
Ensure
that
Tivoli
logging
is
enabled.
Check
the
log
file
associated
with
this
callback
request
to
determine
the
log
file
name
passed
to
the
witmcsdispout.
Determine
if
there
was
an
environment
error
associated
with
the
file.
Try
rerunning
the
callback
request.
If
the
problem
persists,
contact
IBM
Software
Support.
IZY2071E
An
internal
error
occurred
while
displaying
output.
Explanation:
An
internal
error
occurred
while
displaying
output.
The
expected
output
could
not
be
displayed.
Operator
Response:
Ensure
that
Tivoli
logging
is
enabled.
The
log
file
associated
with
this
call
will
be
displayed.
Check
for
errors
associated
with
the
call
to
command
name.
The
referenced
error
will
be
near
the
end
of
the
log.
Correct
errors
if
possible
and
run
the
request
again.
If
the
problem
persists,
contact
IBM
Software
Support.
IZY2074E
Configuration
Manager
choice
not
selected.
Explanation:
When
assigning
component
membership,
one
of
the
Configuration
Manager
choices
must
be
selected.
Operator
Response:
Run
the
request
again,
selecting
a
Configuration
Manager
choice
for
membership
assignment.
IZY2100E
An
IBM
WebSphere
administration
server
name
is
required.
Explanation:
You
must
specify
the
administration
server
name
when
you
create
a
WSAdministrationServer
object.
Operator
Response:
Run
the
task
or
command
again,
specifying
the
administration
server
name.
IZY2054E
•
IZY2100E
Chapter
5.
Understanding
warning
and
error
messages
97
IZY2103E
The
IBM
WebSphere
administration
server
port
is
required.
Explanation:
You
must
specify
the
administration
server
port
when
you
create
a
WSAdministrationServer
object.
Operator
Response:
Run
the
task
or
command
again,
specifying
the
administration
server
port.
IZY2104E
Tivoli
endpoint
must
be
selected.
Explanation:
When
you
create
a
WSAdministrationServer
object,
you
must
specify
the
Tivoli
endpoint
on
which
the
IBM
WebSphere
Application
Server
object
is
running.
Operator
Response:
Run
the
task
or
command
again,
specifying
the
Tivoli
endpoint
on
which
the
IBM
WebSphere
Application
Server
is
running.
IZY2106E
Endpoint
name
"%7$s"
was
not
found
as
a
Tivoli
endpoint.
Explanation:
The
value
specified
in
%7$s
is
not
a
valid
Tivoli
endpoint.
When
you
create
an
object,
you
must
specify
a
valid
Tivoli
endpoint.
Operator
Response:
Run
the
task
again,
specifying
a
valid
Tivoli
endpoint.
IZY2107E
Unable
to
start
an
internal
transaction.
Explanation:
An
internal
error
occurred
while
starting
a
Tivoli
transaction
during
the
creation
of
a
WSAdministrationServer
or
WSApplicationServer
object.
Operator
Response:
Check
the
Tivoli
server’s
performance.
Run
the
command
again.
If
the
problem
persists,
contact
IBM
Software
Support.
IZY2108E
An
internal
transaction
ended
unsuccessfully.
Explanation:
An
internal
error
occurred
while
starting
a
Tivoli
transaction
during
the
creation
of
a
WSAdministrationServer
or
WSApplicationServer
object.
Operator
Response:
Check
the
Tivoli
server’s
performance.
Run
the
command
again.
If
the
problem
persists,
contact
IBM
Software
Support.
IZY2109E
Managed
node
"%1$s"
is
not
valid.
Explanation:
The
value
specified
as
%1$s
is
not
a
valid
Tivoli
managed
node.
Operator
Response:
Run
the
task
or
command
again,
specifying
a
valid
Tivoli
managed
node
to
host
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
IBM
WebSphere
Application
Server
object.
To
create
the
object
on
the
default
gateway,
do
not
specify
a
managed
node.
IZY2111E
Unable
to
get
the
host
name
for
endpoint
"%7$s".
Explanation:
During
the
creation
of
a
WSAdministrationServer
or
WSApplicationServer
object,
the
function
was
unable
to
determine
the
host
name
associated
with
Tivoli
endpoint
%1$s.
Operator
Response:
Ensure
that
the
endpoint
is
up
and
operational.
Try
running
other
tasks
to
the
endpoint.
Correct
any
problems
with
the
endpoint.
If
the
problem
persists,
contact
IBM
Software
Support.
IZY2112E
Exception:
%1$s
Explanation:
An
internal
processing
error
occurred
during
the
creation
of
a
WSAdministrationServer
or
WSApplicationServer
object.
This
error
is
a
Tivoli
exception.
Detailed
information
about
the
exception
is
provided
in
%1$s.
Operator
Response:
Correct
the
cause
of
the
exception,
if
possible,
and
run
the
command
again.
If
the
problem
persists,
contact
IBM
Software
Support.
IZY2103E
•
IZY2112E
98
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
IZY2115E
The
managed
node
name
"%7$s"
was
not
found
as
a
Tivoli
managed
node.
Explanation:
The
value
specifies
as
%7$s
is
not
a
valid
Tivoli
managed
node.
Operator
Response:
Run
the
task
or
command
again,
specifying
a
valid
Tivoli
managed
node
to
host
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
object.
To
create
the
object
on
the
default
gateway,
do
not
specify
a
managed
node
name.
IZY2117E
witmcsdispout
must
be
run
within
a
Tivoli
callback
context.
Explanation:
The
witmcsdispout
command
is
a
Tivoli
internal
command
that
was
invoked
from
an
incorrect
context.
Operator
Response:
If
this
command
is
being
issued
from
Tivoli-supplied
code,
contact
IBM
Software
Support.
IZY2119E
wwaspacdispconf
must
be
run
within
a
Tivoli
callback
context.
Explanation:
The
wwaspacdispconf
command
is
a
Tivoli
internal
command
that
was
invoked
from
an
incorrect
context.
Operator
Response:
If
this
command
is
being
issued
from
Tivoli-supplied
code,
contact
IBM
Software
Support.
IZY2471W
An
error
occurred
while
deleting
a
file
or
files.
Explanation:
No
additional
help
is
available
for
this
message.
IZY2473W
Deleting
trace
log
file
on
host
"%1$s".
Explanation:
The
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
IBM
WebSphere
Application
Server
trace
log
files
are
being
deleted
on
the
%1$s
host.
IZY2474E
The
IBM
WebSphere
administration
server
label
"%1$s"
is
not
valid.
Explanation:
The
specified
administration
server
label,
%1$s,
is
not
valid.
Operator
Response:
Run
the
task
or
command
again,
specifying
a
valid
administration
label.
If
the
label
specified
is
correct
and
you
received
this
message,
contact
IBM
Software
Support.
IZY2475E
usage:
%7$s
-c
-h
fully_qualified_host_name
-e
endpoint_name
-p
policy_region
[-m
managed_node]
-t
node_name
[-u
admin_port_number]
-v
websphere_version
[-w
websphere_security_enabled
-x
websphere_security_properties_file]
-y
websphere_install_path
[-z
os_type]
\n\n
OR
\n\n%7$s
-c
-h
fully_qualified_endpoint_host_name
-e
endpoint_name
-p
policy_region
[-m
managed_node]
-v
websphere_version
[-y
websphere_install_path]
-z
zos
-j
zos_sysplex
-f
zos_was_focal_point
[-n
zos_was_focal_point_protocol]
\n\n
OR
\n\n%7$s
-c
-a
app_server_name
-b
admin_server_label
-e
endpoint_name
[-r
has_web_module]
[-s
has_ejb_module]
[-m
managed_node]
\n\n
OR
\n\n%7$s
-c
-a
app_server_and_instance_names
-b
admin_server_label
-e
endpoint_name
[-r
has_web_module]
[-s
has_ejb_module]
[-m
managed_node]
[-j
zos_system]
Explanation:
The
wwebsphere
command
with
the
-c
parameter
is
used
to
create
IBM
WebSphere
Application
Server
objects.
This
message
provides
the
correct
syntax
to
create
an
IBM
WebSphere
application
server
object.
IZY2476E
The
IBM
WebSphere
Application
Server
object
labeled
"%1$s"
was
not
found
in
the
Tivoli
region.
Explanation:
The
IBM
WebSphere
Application
Server
object,
%1$s,
was
not
found
in
the
Tivoli
region.
Operator
Response:
Ensure
that
the
object
is
defined
in
the
region.
If
it
is
not,
define
the
object
and
run
the
task
again.
IZY2115E
•
IZY2476E
Chapter
5.
Understanding
warning
and
error
messages
99
IZY2477E
usage:
The
first
flag
that
was
specified
to
the
%7$s
command
must
be
one
of
-c,
-d
or
-g.
Explanation:
The
first
flag
used
with
the
%7$s
command
must
be
either
-c,
-d,
or
-g.
Operator
Response:
Run
the
command
again,
specifying
-c
to
create
an
object,
-d
to
delete
an
object,
or
-g
to
retrieve
information
about
an
object.
IZY2478E
The
installed
product
label
"%7$s"
was
not
found.
AutoTrace
has
not
been
automatically
initialized.
Explanation:
Information
for
the
program
product
%7$s
could
not
be
found.
In
order
for
AutoTrace
to
initialize
automatically,
the
product
%7$s
must
already
be
installed.
IZY2479E
Unable
to
remove
WSAdministrationServer
object
"%7$s".
Remove
WSApplicationServer
objects
associated
with
this
object
first.
Explanation:
Application
server
objects
associated
with
the
%7$s
Administration
server
object
still
exist.
Operator
Response:
Remove
all
Application
server
objects
associated
with
this
Administration
server
object
and
try
the
operation
again.
IZY3000E
"%7$s"
is
not
a
policy
region.
Explanation:
This
task
requires
a
policy
region.
Operator
Response:
Run
the
task
again,
specifying
a
policy
region.
IZY3004E
Unable
to
create
the
administration
server
"%7$s"
in
the
specified
policy
region.
Explanation:
The
task
encountered
errors
while
attempting
to
create
the
IBM
WebSphere
administration
server
object
(WSAdministrationServer)
in
the
specified
policy
region.
The
policy
region
might
not
exist
or
might
not
be
valid.
Operator
Response:
Ensure
that
the
WSAdministrationServer
resource
type
is
a
managed
resource
for
the
target
policy
region.
Verify
that
the
policy
region
exists
and
that
the
name
is
valid.
If
it
is
not
valid,
run
the
task
again,
specifying
a
different
policy
region.
If
the
policy
region
is
valid
and
the
task
still
fails,
contact
IBM
Software
Support.
IZY3005E
The
creation
of
administration
server
"%7$s"
failed.
Explanation:
The
task
or
command
failed
to
create
the
administration
server
%7$s.
Operator
Response:
Check
the
error
logs
for
the
task
or
command,
correct
any
problems,
if
possible,
and
run
the
task
or
command
again.
IZY3008E
Application
server
creation
failed.
Explanation:
The
creation
of
the
application
server
object
failed.
Operator
Response:
Check
the
error
log
for
the
task
or
command,
correct
any
problems,
and
run
the
task
or
command
again.
IZY3010E
Unable
to
create
the
application
server
managed
resource
in
the
specified
policy
region.
Explanation:
The
task
could
not
create
the
application
server
in
the
policy
region
specified.
Operator
Response:
Ensure
that
the
new
object’s
resource
type
is
a
managed
resource
for
the
target
policy
region.
Verify
that
the
policy
region
exists
and
that
the
name
is
valid.
Check
the
error
logs
from
the
task
or
command,
correct
any
problems,
and
run
the
task
or
command
again.
Contact
IBM
Software
Support
if
the
problem
persists.
IZY3465E
The
endpoint
name
is
required.
Explanation:
The
endpoint
name
is
required
to
run
this
task
or
command.
Operator
Response:
Run
the
task
or
command
again,
specifying
the
endpoint
name.
IZY2477E
•
IZY3465E
100
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
IZY3466E
The
IBM
WebSphere
administration
server
name
"s%7$s"
is
not
valid.
Explanation:
The
WebSphere
administration
server
name
specified
is
not
valid.
Operator
Response:
Run
the
task
or
command
again,
specifying
a
valid
IBM
WebSphere
Application
Server.
IZY9002E
The
Configure
Event
Server
task
cannot
locate
rules
file
%1$s.
Explanation:
The
Configure
Event
Server
task
requires
a
set
of
rules
files
to
complete
successfully.
File
%1
was
not
found.
Rules
files
are
installed
during
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
installation.
Search
the
directory
in
which
the
product
was
installed
to
determine
if
the
file
was
moved
or
deleted.
Restore
the
file
and
run
the
Configure
Event
Server
task
again.
Contact
IBM
Software
Support
if
the
problem
persists.
IZY9003E
The
Configure
Event
Server
task
cannot
locate
script
file
%1$s.
Explanation:
The
Configure
Event
Server
task
requires
a
set
of
event
script
files
to
complete
successfully.
File
%1$s
was
not
found.
Required
script
files
are
installed
during
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
installation.
Search
the
directory
in
which
the
product
was
installed
to
determine
if
the
file
was
moved
or
deleted.
Restore
the
file
and
run
the
Configure
Event
Server
task
again.
Contact
IBM
Software
Support
if
the
problem
persists.
IZY9004E
Rule
base
%1$s
does
not
exist.
Explanation:
An
attempt
was
made
to
update
rule
base
%1,
which
does
not
exist.
Run
the
wlsrb
command
to
list
the
set
of
existing
rule
bases.
Run
the
Configure
Event
Server
task
again,
specifying
an
existing
rule
base
as
the
rule
base
to
update.
IZY9005E
Source
rule
base
%1$s
does
not
exist.
Explanation:
An
attempt
was
made
to
create
a
new
rule
base,
initializing
it
with
the
contents
of
rule
base
%1$s,
which
does
not
exist.
Run
the
wlsrb
command
to
determine
the
set
of
existing
rule
bases.
Run
the
Configure
Event
Server
task
again,
specifying
an
existing
rule
base
as
the
source
from
which
to
initialize
the
new
rule
base.
IZY9007E
Error
occurred
creating
path
%1$s.
Explanation:
An
error
occurred
creating
the
rule
base
path
%1$s.
Check
the
Configure
Event
Server
task
log
for
errors.
Correct
errors
if
possible
and
run
the
Configure
Event
Server
task
again.
Contact
IBM
Software
Support
if
the
problem
persists.
IZY9011E
The
rule
base
%1$s
did
not
compile
successfully.
Explanation:
The
Configure
Event
Server
task
issues
this
message
in
one
of
the
following
situations:
v
When
it
discovers
compilation
errors
in
an
existing
rule
base
while
updating
or
copying
an
existing
rule
base.
Determine
the
reason
for
compilation
errors
in
the
rule
base
and
correct
them.
When
you
correct
the
errors,
run
the
Configure
Event
Server
task
again.
--OR--
v
After
adding
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
classes
and
rules
to
the
rule
base.
Save
the
Configure
Event
Server
task
log
and
contact
IBM
Software
Support.
IZY3466E
•
IZY9011E
Chapter
5.
Understanding
warning
and
error
messages
101
IZY9013E
An
error
occurred
while
creating
the
rule
base
%1$s
in
%2$s.
Explanation:
An
error
occurred
while
trying
to
create
rule
base
%1
in
directory
%2.
Check
the
Configure
Event
Server
task
log
for
errors.
Correct
the
errors
if
possible
and
run
the
task
again.
Contact
IBM
Software
Support
if
the
problem
persists.
IZY9015E
An
error
occurred
while
copying
rule
base
%1$s
to
%2$s.
Explanation:
An
error
occurred
while
initializing
new
rule
base
%2$s
with
the
contents
of
rule
base
%1$s.
Check
the
Configure
Event
Server
task
log
for
errors.
Correct
the
errors
and
run
the
task
again.
Contact
IBM
Software
Support
if
the
problem
persists.
IZY9017E
An
error
occurred
while
importing
the
classes
in
file
%1$s
into
rule
base
%2$s.
Explanation:
An
error
occurred
while
importing
the
event
classes
in
file
%1$s
into
rule
base
%2$s.
Check
the
Configure
Event
Server
task
log
for
errors.
Correct
the
errors
and
run
the
task
again.
Contact
IBM
Software
Support
if
the
problem
persists.
IZY9020E
An
error
occurred
while
creating
event
source
%1$s.
Explanation:
An
error
occurred
while
creating
event
source
%1.
Check
the
Configure
Event
Server
task
log
for
errors.
Correct
the
errors
if
possible
and
the
run
task
again.
Contact
IBM
Software
Support
if
the
problem
persists.
IZY9023E
An
error
occurred
while
deleting
event
source
%1$s.
Explanation:
An
error
occurred
while
deleting
event
source
%1.
Check
the
Configure
Event
Server
task
log
for
errors.
Correct
the
errors
and
run
the
task
again.
Contact
IBM
Software
Support
if
the
problem
persists.
IZY9025E
An
error
occurred
while
loading
rule
base
%1$s.
Explanation:
An
error
occurred
while
loading
rule
base
%1$
into
the
event
server.
Check
the
Configure
Event
Server
task
log
for
errors.
Correct
the
errors
if
possible
and
run
the
task
again.
Contact
IBM
Software
Support
if
the
problem
persists.
IZY9032E
The
event
server
did
not
start.
Explanation:
An
error
occurred
while
trying
to
start
the
event
server.
Check
the
Configure
Event
Server
task
log
for
errors.
Correct
the
errors
and
run
the
task
again.
Contact
IBM
Software
Support
if
the
problem
persists.
IZY9033E
The
event
server
did
not
stop.
Explanation:
An
error
occurred
while
stopping
the
event
server.
Check
the
Configure
Event
Server
task
log
for
errors.
Correct
the
errors
and
run
the
task
again.
Contact
IBM
Software
Support
if
the
problem
persists.
IZY9034E
You
must
run
the
Configure
Event
Server
task
on
the
event
server.
Explanation:
The
Configure
Event
Server
task
was
run
on
a
machine
that
is
not
an
event
server.
This
task
only
runs
on
an
event
server
machine.
Do
one
of
the
following:
v
Run
the
Configure
Event
Server
task,
specifying
an
event
server
as
the
target
of
the
task
execution.
--OR--
v
Run
the
Configure
Event
Server
job
in
the
ITMWAS
task
libraries.
IZY9036E
Rule
base
directory
%1$s
does
not
exist.
Explanation:
While
the
Configure
Event
Server
task
was
updating
event
forwarding
information,
it
discovered
that
the
directory
%1$s
associated
with
the
rule
base
does
not
exist.
Check
the
Configure
Event
Server
task
log
for
errors.
Correct
the
errors
and
run
the
task
again.
Contact
IBM
Software
Support
if
the
problem
persists.
IZY9013E
•
IZY9036E
102
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
IZY9037E
Incorrect
parameters
were
used
while
running
the
Configure
Event
Server
task.
Explanation:
You
ran
the
Configure
Event
Server
with
incorrect
parameters
or
while
using
the
wruntask
command.
The
Configure
Event
Server
task
is
supported
for
use
from
the
Tivoli
desktop
only.
Run
the
Configure
Event
Server
task
from
the
Tivoli
desktop
using
the
ITMWAS
task
libraries.
IZY9038E
Cannot
locate
baroc
file
%1$s.
Explanation:
The
Configure
Event
Server
task
requires
a
set
of
baroc
files
to
complete
successfully.
File
%1$s
was
not
found.
Required
baroc
files
are
installed
during
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
installation.
Determine
if
the
file
was
moved
or
deleted.
Restore
the
file,
if
necessary,
from
the
product
CD
and
run
the
Configure
Event
Server
task
again.
Contact
IBM
Software
Support
if
the
problem
persists.
IZY9040E
Rule
base
%1$s
already
exists.
Explanation:
This
message
occurs
when
you
attempt
to
create
a
rule
base
that
already
exists.
v
To
create
a
new
rule
base,
run
the
Configure
Event
Server
task
again,
specifying
a
rule
base
name
that
does
not
currently
exist.
--OR--
v
If
you
want
to
update
the
existing
rule
base
%1$s,
select
Update.
IZY9041E
The
Configure
Event
Server
task
received
incorrect
request:
%1$s.
Explanation:
The
Configure
Event
Server
task
received
an
incorrect
request.
This
error
occurs
only
while
running
the
task
with
the
wruntask
command.
You
must
run
the
Configure
Event
Server
task
from
the
Tivoli
desktop
using
the
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
task
libraries.
IZY9042E
Rule
base
path
%1$s
is
not
allowed
to
have
blanks.
Explanation:
The
rule
base
path
is
incorrect
because
it
contains
blanks.
Run
the
Configure
Event
Server
task
again,
specifying
a
rule
base
path
name
without
blanks.
IZY9044E
An
error
occurred
importing
rules
in
file
%1$s
into
rule
base
%2$s.
Explanation:
An
error
occurred
importing
the
event
rules
in
file
%1$s
into
rule
base
%2$s.
Check
the
Configure
Event
Server
task
log
for
errors.
Correct
the
errors
and
run
the
task
again.
Contact
IBM
Software
Support
if
the
problem
persists.
IZY9048E
Cannot
locate
icon
file
%1$s.
Explanation:
The
Configure
Event
Server
task
requires
icon
files
that
are
normally
installed
with
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
to
complete
successfully.
Icon
file
%1$s
was
not
found.
Determine
if
the
file
was
moved
or
deleted.
Restore
the
file,
from
the
product
if
necessary,
and
run
the
Configure
Event
Server
task
again.
Contact
IBM
Software
Support
if
the
problem
persists.
IZY9049E
This
task
must
be
run
against
the
Tivoli
Enterprise
Console
event
server.
Explanation:
You
are
running
the
Configure
Event
Server
task
against
a
target
that
is
not
a
Tivoli
Enterprise
Console
event
server.
Run
the
Configure
Event
Server
task
against
the
Tivoli
Enterprise
Console
event
server.
IZY9050E
The
Default
rule
base
is
read-only
and
cannot
be
updated.
Explanation:
An
attempt
was
made
to
run
the
Configure
Event
Server
task
and
update
the
Default
rule
base.
This
rule
base
is
read-only
and
cannot
be
updated.
Run
the
wlsrb
command
to
list
the
set
of
existing
rule
bases.
Rerun
the
Configure
Event
Server
task
specifying
a
different
existing
rule
base
as
the
rule
base
to
update.
IZY9037E
•
IZY9050E
Chapter
5.
Understanding
warning
and
error
messages
103
IZY9051E
New
Rule
Base
Name
was
not
specified.
Explanation:
An
attempt
was
made
to
create
a
new
rule
base
but
the
New
Rule
Base
Name
was
not
specified.
Rerun
the
Configure
Event
Server
task
specifying
a
name
for
the
new
rule
base.
IZY9054E
New
Rule
Base
Path
was
not
specified.
Explanation:
An
attempt
was
made
to
create
a
new
rule
base
but
the
New
Rule
Base
Path
was
not
specified.
Rerun
the
Configure
Event
Server
task
specifying
a
path
for
the
new
rule
base.
IZY9055E
Rule
Base
was
not
specified.
Explanation:
An
attempt
was
made
to
update
an
existing
rule
base
or
create
a
new
rule
base
from
an
existing
one
and
a
Rule
Base
was
not
specified.
Rerun
the
Configure
Event
Server
task
specifying
the
rule
base
to
be
updated
or
copied.
IZY9056E
Event
server
not
installed.
Explanation:
An
attempt
was
made
to
configure
the
event
server
when
a
Tivoli
Enterprise
Console
event
server
has
not
been
installed.
Install
the
Tivoli
Enterprise
Console
event
server
then
rerun
the
Configure
Event
Server
task.
Proxy
mode
z/OS-specific
messages
There
are
four
types
of
proxy
mode
z/OS-specific
messages:
v
Informational
v
Warning
v
Non-fatal
v
Fatal
Informational
messages
The
following
messages
are
informational
only.
You
do
not
need
to
take
any
action
in
response
to
these
messages.
ITD0001I
The
Proxy390
update
interval
was
set
to
{0}
milliseconds.
Explanation:
The
metrics
data
collected
on
the
z/OS
image
will
be
pushed
to
the
endpoint
approximately
every
{0}
seconds.
ITD0002I
Client
number
{0}
initiated
a
connection.
Explanation:
A
new
connection
was
received
by
either
the
ProxyILT
or
Proxy390
server
loop.
{0}
is
an
accession
number
used
to
identify
the
client.
ITD0003I
The
receiver
thread
is
now
accepting
incoming
connections.
Explanation:
The
ProxyILT
or
Proxy390
server
loop
is
operational.
ITD0004I
The
Proxy
server
is
shutting
down.
Explanation:
The
ProxyILT
or
Proxy390
server
loop
is
terminating.
IZY9051E
•
ITD0004I
104
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
ITD0005I
Metrics
data
will
now
be
sent
to
the
endpoint.
Explanation:
The
timer
causing
metrics
data
to
be
pushed
has
fired.
ITD0006I
Thread
created
for
data
exchange
with
client
{0}.
Explanation:
The
thread
associated
with
a
data
receiver
(Proxy390,
ProxyILT)
has
been
created
and
is
now
running.
ITD0007I
Client
{0}
belongs
to
IBM
WebSphere
Application
Server
instance
{1}.
Explanation:
Client
number
{0}
has
identified
itself
as
{1}.
{0}
is
the
client’s
accession
number.
{1}
is
a
string
identifying
the
IBM
WebSphere
Application
Server
instance.
ITD00008I
New
metrics
data
received
from
client
{1}:{0}.
Explanation:
Client
number
{0}
belonging
to
instance
{1}
has
sent
new
deltas.
{0}
is
the
client’s
accession
number.
{1}
is
a
string
identifying
the
IBM
WebSphere
Application
Server
instance.
ITD00009I
The
connection
from
client
{1}:{0}
has
been
closed.
Explanation:
The
connection
from
client
{0}
has
been
terminated.
{0}
is
the
client’s
accession
number.
ITD00010I
Metrics
for
{0}
are
no
longer
available
(due
to
disconnection
of
or
explicit
instructions
from
client
{1}).
Explanation:
Either
the
connection
from
client
{0}
has
been
terminated
and
client
{1}
was
the
last
client
providing
metrics
data
for
the
server
instance,
or
client
{0}
has
directed
that
metrics
for
{1}
be
flushed.
ITD00011I
Thread
created
for
data
exchange
with
client
{0}
is
terminating.
Explanation:
The
thread
associated
with
a
receiver
is
terminating.
ITD00012I
A
Thread
has
been
created
for
metrics
data
collection
and
forwarding.
Explanation:
The
IBM
WebSphere
Application
Server
plugin
sending
metrics
data
to
the
Collector
has
started.
ITD00013I
Metrics
collection
thread
sending
data
to
Proxy390
(Collector).
Explanation:
The
IBM
WebSphere
Application
Server
plugin
thread
has
fired
on
a
minor
(condense
data
but
do
not
send
yet)
cycle.
ITD00014I
Metrics
collection
thread
sending
data
to
Proxy390
(Collector).
Explanation:
The
IBM
WebSphere
Application
Server
plugin
thread
has
fired
on
a
major
(send
data)
cycle.
ITD00015I
The
Thread
created
for
metrics
data
collection
is
terminating.
Explanation:
The
IBM
WebSphere
Application
Server
plugin
thread
is
shutting
down.
ITD9001I
The
ITMWAS
event
adapter
has
started
and
is
sending
events
to
the
event
server.
Explanation:
The
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
event
adapter
is
running.
ITD9002I
The
ITMWAS
event
adapter
is
shutting
down
and
is
no
longer
sending
events
to
the
event
server.
Explanation:
The
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server
event
adapter
is
not
running.
ITD0005I
•
ITD9002I
Chapter
5.
Understanding
warning
and
error
messages
105
Warning
messages
The
following
messages
are
warning
messages.
Warning
messages
are
issued
for
minor
aberrations
in
internal
state.
Warnings
might
accompany
limited
degradations
of
functionality,
in
which
you
might
need
to
restart
Proxy390
or
endpoint
monitors.
Warnings
are
only
issued
for
non-fatal
errors.
ITD00100W
Recoverable
internal
error:
the
agent
for
client
{0}
could
not
be
located.
Explanation:
The
agent
forwarding
metrics
data
to
an
endpoint
was
not
found.
{0}
is
the
client’s
accession
number.
ITD00101W
Recoverable
internal
error:
the
metrics
for
{0}
could
not
be
sent.
Explanation:
An
error
occurred
that
prevented
sending
updated
metrics.
{0}
is
a
string
identifying
the
IBM
WebSphere
Application
Server
instance,
either
by
client
accession
number
or
instance
locative.
ITD00102W
Recoverable
internal
error:
client
{0}
has
closed
the
connection
abruptly.
The
exception
below
contains
additional
information.
Explanation:
The
connection
from
client
{0}
has
been
terminated
ABRUPTLY.
{0}
is
the
client’s
accession
number.
This
might
occur
prior
to
the
client
having
identified
the
IBM
WebSphere
Application
Server
instance
to
which
it
belongs,
so
only
the
accession
number
is
reported.
ITD00303F
Could
not
find
the
serialized
registry
for
server
{0},
instance
{1}
in
{2}.
Explanation:
Could
not
find
the
serialized
registry
for
the
specified
server
{0}
Server
Name
{1}
Instance
Name
{2}
File
Non–fatal
error
messages
The
following
messages
are
non-fatal
errors.
Non-fatal
messages
are
issued
for
major,
semi-recoverable
aberrations
in
internal
state.
After
you
identify
the
root
cause
of
the
problem
and
repair
it,
you
might
need
to
restart
Proxy390
or
endpoint
monitors.
These
errors
do
not
generally
result
directly
in
system
shutdown
but
might
be
precursors
to
a
generalized
failure.
ITD00200E
The
connection
to
client
{0}
is
corrupt.
The
exception
below
contains
additional
information.
Explanation:
The
connection
between
two
communicating
entities
has
been
corrupted.
Generalized
cause.
{0}
is
the
client
accession
number.
ITD00201E
An
attempt
to
establish
communication
with
{0}
has
failed.
The
exception
below
contains
additional
information.
Explanation:
Proxy390
could
not
connect
to
a
ProxyILT
at
the
expected
host.
ITD00202E
The
authentication
key
file
ITMWASSSK
was
not
found.
Explanation:
The
Authentication
file
ITMWASSSK
was
not
found
in
the
appropriate
directory
(/var/itmwas
on
z/OS
and
$LCF_DATDIR
on
distributed).
ITD00100W
•
ITD00202E
106
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
ITD00203E
The
authentication
handshake
failed
to
complete.
Explanation:
The
Authentication
handshake
failed.
This
could
mean
that
the
client
and
the
server
do
not
share
the
same
authentication
key.
ITD00204E
Invalid
modify
command:
{0}
Explanation:
You
entered
an
invalid
modify
command.
ITD00205E
Error
processing
operator
input
Explanation:
There
was
an
error
reading
the
console
command.
ITD00206E
Protocol
version
mismatch:
{0}
Explanation:
The
serialized
data
structures
are
drawn
from
different
versions.
Fatal
error
messages
The
following
messages
are
fatal
errors.
Fatal
error
messages
are
issued
for
major,
unrecoverable
aberrations
in
internal
state.
After
you
identify
the
root
cause
of
the
problem
and
repair
it,
you
might
need
to
restart
Proxy390
or
endpoint
monitors.
ITD00300F
Could
not
create
socket
on
port
{0}
for
serving.
Explanation:
Creation
of
the
communications
port
failed,
terminator
side.
{0}
is
the
port
number
that
could
not
be
claimed.
ITD00301F
A
Security
violation
was
detected
that
prevents
operation.
The
exception
below
contains
additional
information.
Explanation:
A
general
Security
violation
was
detected
that
prevents
function.
ITD00302F
The
connection
to
client
{0}
is
corrupt.
A
version
mismatch
is
the
likely
cause.
The
exception
below
contains
additional
information.
Explanation:
The
connection
between
two
communicating
entities
has
been
corrupted.
This
indicates
a
generalized
systems
failure,
perhaps
due
to
incompatible
versions
of
the
software
in
deployment.
{0}
is
the
client
accession
number.
ITD00303F
A
connection
to
host
{0},
port
{1}
could
not
be
established.
Explanation:
Creation
of
the
communications
port
failed,
initiator
side.
ITD00203E
•
ITD00303F
Chapter
5.
Understanding
warning
and
error
messages
107
108
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
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.
109
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.
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.
Trademarks
are
trademarks
or
registered
trademarks
of
International
Business
Systems
in
the
United
States,
other
countries,
or
both.
Microsoft,
Windows,
and
Windows
NT
are
trademarks
of
Microsoft
Corporation
in
the
United
States,
other
countries,
or
both.
Java
and
all
Java-based
trademarks
are
trademarks
of
Sun
Microsystems,
Inc.
in
the
United
States,
other
countries,
or
both.
UNIX
is
a
registered
trademark
of
The
Open
Group
in
the
United
States
and
other
countries.
Other
company,
product,
and
service
names
may
be
trademarks
or
service
marks
of
others.
110
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
Index
Special
characters/etc/rmitab
rctmal
command
12
Aaccessibility
vii
AutoTrace
53
gathering
information
for
IBM
Software
Support
53
initializing
53
Bbooks
see
publications
v,
vi
built-in
problem
determination
features
1
Ccommands
/etc/rmitab
rctmal
12
lcf_env.sh
10
lcfd.sh
10
net
start
10
net
stop
10
ps
10
special
characters
ix
syntax
ix
wadminep
10,
12
wdelep
12
wlookup
10
wping
9
communication
problems
with
z/OS
systems
19
connectivitytesting
endpoint
9
conventionstypeface
viii
customer
supportsee
software
support
vii
DData
Collectorresource
model-related
problems
31
debugginglog
files
50
deploy.log
file
50
directory
names,
notation
ix
Discover_WebSphere_Resources
problems
37
discovery
problems
37
Eendpoints
removing
10
endpoints
(continued)stopping
11
testing
connectivity
of
9
environment
variables,
notation
ix
Ffiles
deploy.log
50
Ggathering
information
1
general
problems
15
IIBM
Software
Supportgathering
information
for
1
gathering
local
files
for
49
gathering
proxy
mode
z/OS
files
for
49
installationendpoint
connectivity
9
general
problems
3
internationalization
problems
4
log
file
50
message
log
files
8
messages
56
problems
and
workarounds
3
removing
endpoints
10
resolving
installer
problems
6
Step
List
6
uninstallation
problems
5
installermessages
56
Step
List
6
installer
problems
6
introduction
1
Llcf_env.sh
command
10
lcf.sh
command
10
lcfd,
endpoint
processstopping
with
net
stop
command
10
log
files
47,
50
changing
the
trace
settings
for
resource
models
52
gathering
for
IBM
Software
Support
49
general
50
proxy
mode
z/OS
52
resource
models
51
tasks
51
Tivoli
Enterprise
Data
Warehouse
51
logging
1
LogViewer
52
Mmanuals
see
publications
v,
vi
message
files
47
messages
1
format
55
general
messages
72
overview
55
proxy
mode
z/OS
fatal
error
107
proxy
mode
z/OS
informational
104
proxy
mode
z/OS
non-fatal
106
proxy
mode
z/OS
warning
106
proxy
mode
z/OS-specific
messages
104
severity
55
Nnet
start
command
10
net
stop
command
10
notationenvironment
variables
ix
path
names
ix
typeface
ix
Oonline
publicationsaccessing
vi
ordering
publications
vii
Ppath
names,
notation
ix
problem
determinationTivoli
Enterprise
Console
events
not
displayed
42
Tivoli
Enterprise
Data
Warehouse
51
problems
and
workarounds
15
product
overview
1
proxy
mode
z/OS
endpointsadministration
server-related
resource
model
problems
29
application
server-related
resource
model
problems
30
communication
problems
19
Data
Collector-related
resource
model
problems
31
endpoint-related
resource
model
problems
33
fatal
error
messages
107
general
problems
17
informational
messages
104
log
files
52
LogViewer
52
messages
104
NetView-related
resource
model
problems
30
111
proxy
mode
z/OS
endpoints
(continued)non-status
resource
model
problems
28
non–fatal
messages
106
resource
model
problems
26
status
resource
model
problems
27
warning
messages
106
proxy
mode
z/OS
log
files
52
proxy
mode
z/OS-specific
messages
104
ps
command
10
publications
v
accessing
online
vi
ordering
vii
Rremoving
endpoint
process
and
files
11
resolving
installer
problems
6
resource
model
log
files
51
resource
modelsgeneral
problems
19
log
files
51,
52
NetView
problems
30
proxy
mode
z/OS
administration
server
problems
29
proxy
mode
z/OS
endpoint
problems
33
proxy
mode
z/OS-related
problems
26
proxy-mode
z/OS
application
server
problems
30
trace
settings,
changing
52
z/OS
Data
Collector
problems
31
Ssoftware
support,
contacting
vii
status
resource
model
problems
for
proxy
mode
z/OS
27
Step
List
6
stopping
endpoint
process
11
Ttask
log
files
51
tasksDiscover_WebSphere_Resources
problems
37
general
problems
34
log
files
51
Tivoli
Enterprise
Consoleevents
not
displayed
42
Tivoli
Enterprise
Console
problems
41
Tivoli
Enterprise
Data
Warehouselog
files
51
problem
determination
42
Tivoli
Enterprise
Data
Warehouse
problems
42
Tivoli
software
information
center
vi
trace
files
47
typeface
conventions
viii
Uuninstallation
problems
3
upgrade
problems
3
Vvariables,
notation
for
ix
Wwadminep
command
10,
12
wdelep
command
12
wlookup
command
10
wping
command
9
112
IBM
Tivoli
Monitoring
for
Web
Infrastructure:
WebSphere
Application
Server:
Problem
Determination
Guide
����
Printed
in
USA
SC32-1425-00