ibm tivoli monitoring for business...
TRANSCRIPT
-
IBM
Tivoli
Monitoring
for
Business
Integration
Problem
Determination
Guide
5.1.1
SC32-1404-00
���
-
IBM
Tivoli
Monitoring
for
Business
Integration
Problem
Determination
Guide
5.1.1
SC32-1404-00
���
-
Note
Before
using
this
information
and
the
product
it
supports,
read
the
information
in
“Notices”
on
page
247.
First
Edition
(November
2003)
This
edition
applies
to
Version
5.1.1
of
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
MQ
and
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
InterChange
Server
and
to
all
subsequent
releases
and
modifications
until
otherwise
indicated
in
new
editions.
This
edition
applies
to
Version
5.1.0
of
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
MQ
and
to
all
subsequent
releases
and
modifications
until
otherwise
indicated
in
new
editions.
©
Copyright
International
Business
Machines
Corporation
2003.
All
rights
reserved.
US
Government
Users
Restricted
Rights
—
Use,
duplication
or
disclosure
restricted
by
GSA
ADP
Schedule
Contract
with
IBM
Corp.
-
Contents
Tables
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. v
About
this
guide
.
.
.
.
.
.
.
.
.
. vii
Who
should
read
this
guide
.
.
.
.
.
.
.
.
. vii
Publications
.
.
.
.
.
.
.
.
.
.
.
.
.
. vii
IBM
Tivoli
Monitoring
for
Business
Integration
library
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. vii
Prerequisite
publications
.
.
.
.
.
.
.
.
. ix
Related
publications
.
.
.
.
.
.
.
.
.
. ix
Accessing
publications
online
.
.
.
.
.
.
. ix
Ordering
publications
.
.
.
.
.
.
.
.
.
. x
Accessibility
.
.
.
.
.
.
.
.
.
.
.
.
.
. x
Contacting
software
support
.
.
.
.
.
.
.
.
. x
Conventions
used
in
this
guide
.
.
.
.
.
.
.
. xi
Typeface
conventions
.
.
.
.
.
.
.
.
.
. xi
Operating
system-dependent
variables
and
paths
xi
Tivoli
command
syntax
.
.
.
.
.
.
.
.
. xii
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
Proxy-mode
z/OS-specific
installation
and
configuration
problems
.
.
.
.
.
.
.
.
.
.
. 5
Resolving
installer
problems
.
.
.
.
.
.
.
.
. 6
Testing
endpoint
connectivity
.
.
.
.
.
.
.
.
. 9
Chapter
3.
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
MQ
troubleshooting
.
.
.
.
.
.
.
.
.
.
. 11
General
problems
.
.
.
.
.
.
.
.
.
.
.
. 11
Message
Manager
problems
.
.
.
.
.
.
.
.
. 13
Proxy
mode
z/OS
endpoint
problems
.
.
.
.
. 14
Resource
model
problems
.
.
.
.
.
.
.
.
. 15
Tasks
problems
.
.
.
.
.
.
.
.
.
.
.
.
. 16
Tivoli
Enterprise
Console
problems
.
.
.
.
.
. 16
Tivoli
Inventory
problems
.
.
.
.
.
.
.
.
. 17
Upgrade
problems
.
.
.
.
.
.
.
.
.
.
.
. 17
Workflow
problems
.
.
.
.
.
.
.
.
.
.
.
. 19
Chapter
4.
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
MQ
Integrator
troubleshooting
.
.
.
.
.
. 21
General
problems
.
.
.
.
.
.
.
.
.
.
.
. 21
Performance
database
server
(PerfDB)
problems
.
. 21
Resource
model
problems
.
.
.
.
.
.
.
.
. 22
Task
problems
.
.
.
.
.
.
.
.
.
.
.
.
. 22
Tivoli
Enterprise
Console
problems
.
.
.
.
.
. 23
Upgrade
problems
.
.
.
.
.
.
.
.
.
.
.
. 25
Proxy-mode
z/OS
problems
.
.
.
.
.
.
.
.
. 26
Chapter
5.
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
InterChange
Server
troubleshooting
.
. 29
Chapter
6.
Tivoli
Business
Systems
Manager
integration
troubleshooting
.
. 31
Chapter
7.
Debugging
information
.
.
. 37
Gathering
trace
information
for
IBM
Software
Support
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 37
Object
trace
information
.
.
.
.
.
.
.
.
. 37
Gateway
and
endpoint
trace
information
.
.
. 38
Adapter
trace
information
.
.
.
.
.
.
.
. 38
Trace
files
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 39
Viewing
trace
files
.
.
.
.
.
.
.
.
.
.
. 40
IBM
Tivoli
Monitoring
for
Business
Integration
installer
trace
files
.
.
.
.
.
.
.
.
.
.
. 40
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
MQ
trace
files
.
.
.
.
.
.
.
. 41
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
MQ
Integrator
trace
files
.
.
.
.
. 45
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
InterChange
Server
trace
files
.
.
. 49
Chapter
8.
Understanding
informational,
warning,
and
error
messages
.
.
.
.
.
.
.
.
.
.
.
.
. 53
Message
format
.
.
.
.
.
.
.
.
.
.
.
.
. 53
Component
messages
.
.
.
.
.
.
.
.
.
.
. 54
Installer
messages
.
.
.
.
.
.
.
.
.
.
. 55
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
MQ
messages
.
.
.
.
.
.
.
.
. 71
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
MQ
Integrator
messages
.
.
.
.
. 150
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
InterChange
Server
messages
.
.
. 210
Notices
.
.
.
.
.
.
.
.
.
.
.
.
.
. 247
Trademarks
.
.
.
.
.
.
.
.
.
.
.
.
.
. 248
Index
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 249
iii
-
iv
IBM
Tivoli
Monitoring
for
Business
Integration:
Problem
Determination
Guide
-
Tables
1.
Common
installation
problems
and
workarounds
.
.
.
.
.
.
.
.
.
.
.
. 3
2.
Proxy-mode
z/OS-specific
installation
and
configuration
problems
.
.
.
.
.
.
.
.
. 5
3.
Status
icons
and
options
for
the
Step
List
panel
of
the
installer
.
.
.
.
.
.
.
.
.
.
.
. 7
4.
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
MQ
general
problems
and
workarounds
.
.
.
.
.
.
.
.
.
.
.
. 11
5.
Message
Manager
problems
and
workarounds
13
6.
Proxy
mode
z/OS
endpoint
problems
and
workarounds
.
.
.
.
.
.
.
.
.
.
.
. 14
7.
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
MQ
resource
model
problems
and
workarounds
.
.
.
.
.
.
. 15
8.
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
MQ
Tivoli
Enterprise
Console
problems
and
workarounds
.
.
.
. 16
9.
Tivoli
Inventory
problems
and
workarounds
17
10.
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
MQ
upgrade
problems
and
workarounds
.
.
.
.
.
.
.
.
.
. 17
11.
Workflow
problems
and
workarounds
.
.
. 20
12.
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
MQ
Integrator
general
problems
and
workarounds
.
.
.
.
.
.
. 21
13.
Performance
database
server
(PerfDB)
problems
.
.
.
.
.
.
.
.
.
.
.
.
. 21
14.
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
MQ
Integrator
resource
model
problems
and
workarounds
.
.
.
.
. 22
15.
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
MQ
Integrator
task
problems
and
workarounds
.
.
.
.
.
.
. 23
16.
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
MQ
Integrator
Tivoli
Enterprise
Console
problems
and
workarounds
23
17.
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
MQ
Integrator
upgrade
problems
and
workarounds
.
.
.
. 25
18.
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
MQ
Integrator
z/OS
problems
and
workarounds
.
.
.
.
.
.
. 26
19.
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
InterChange
Server
problems
and
workarounds
.
.
.
.
.
.
. 29
20.
Tivoli
Business
Systems
Manager
integration
problems
and
workarounds
.
.
.
.
.
.
. 31
21.
Installer
trace
files
and
descriptions
.
.
.
. 41
22.
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
MQ
trace
file
naming
conventions
.
.
.
.
.
.
.
.
.
.
.
. 42
23.
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
MQ
trace
files
that
do
not
follow
trace
file
naming
conventions
.
.
. 42
24.
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
MQ
proxy–mode
z/OS
trace
files
.
.
.
.
.
.
.
.
.
.
.
.
. 44
25.
Workflow
trace
files
and
default
logging
settings
.
.
.
.
.
.
.
.
.
.
.
.
.
. 44
26.
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
MQ
tasks
and
their
corresponding
trace
files.
.
.
.
.
.
.
.
. 45
27.
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
MQ
Integrator
resource
model
trace
files
.
.
.
.
.
.
.
.
.
.
. 47
28.
MQSI
event
adapters
and
their
corresponding
trace
files.
.
.
.
.
.
.
.
.
.
.
.
.
. 48
29.
Miscellaneous
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
MQ
Integrator
trace
files.
.
.
.
.
.
.
.
.
. 48
30.
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
InterChange
Server
task
trace
files
.
.
.
.
.
.
.
.
.
.
.
. 49
31.
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
InterChange
Server
data
provider
trace
files
.
.
.
.
.
.
.
. 50
32.
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
InterChange
Server
miscellaneous
trace
files
.
.
.
.
.
.
.
. 51
v
-
vi
IBM
Tivoli
Monitoring
for
Business
Integration:
Problem
Determination
Guide
-
About
this
guide
The
IBM
Tivoli
Monitoring
for
Business
Integration
Problem
Determination
Guide
provides
information
about
problems
that
might
occur
with
each
of
the
IBM®
Tivoli®
Monitoring
for
Business
Integration
components:
v
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere®
MQ
v
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
MQ
Integrator
v
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
InterChange
Server
Who
should
read
this
guide
This
guide
is
for
system
administrators
who
monitor
and
manage
WebSphere
MQ,
WebSphere
MQ
Workflow,
WebSphere
MQ
Integrator,
and
WebSphere
InterChange
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
MQ
v
IBM
WebSphere
MQ
Workflow
v
IBM
WebSphere
MQ
Integrator
v
IBM
WebSphere
InterChange
Server
v
Tivoli
Enterprise™
Data
Warehouse
v
IBM
Tivoli
Enterprise
Console®
v
IBM
Tivoli
Business
Systems
Manager
(optional)
Publications
This
section
lists
publications
in
the
IBM
Tivoli
Monitoring
for
Business
Integration
library
and
related
documents.
It
also
describes
how
to
access
Tivoli
publications
online
and
how
to
order
Tivoli
publications.
IBM
Tivoli
Monitoring
for
Business
Integration
library
The
following
documents
are
available
in
the
IBM
Tivoli
Monitoring
for
Business
Integration
library:
IBM
Tivoli
Monitoring
for
Business
Integration
v
IBM
Tivoli
Monitoring
for
Business
Integration:
Readme
FIrst,
SC32–1439
Provides
information
on
where
to
find
all
of
the
IBM
Tivoli
Monitoring
for
Business
Integration
documentation,
including
the
titles
and
locations
of
all
documentation.
v
IBM
Tivoli
Monitoring
for
Business
Integration
Installation
and
Setup
Guide,
SC32–1402
vii
-
Provides
information
about
installing
each
of
the
IBM
Tivoli
Monitoring
for
Business
Integration
components.
v
IBM
Tivoli
Monitoring
for
Business
Integration
User’s
Guide,
SC32–1403
Provides
information
about
how
to
use
each
IBM
Tivoli
Monitoring
for
Business
Integration
component
to
manage
resources.
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
MQ
v
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
MQ
Reference
Guide,
SC32–1405
Provides
information
about
the
tasks
and
resource
models
that
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
MQ
provides.
v
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
MQ
Warehouse
Enablement
Pack
Implementation
Guide,
SC32–1407
Provides
information
that
helps
users
deploy
and
use
Tivoli
Enterprise
Data
Warehouse
with
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
MQ.
v
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
MQ
Workflow
Warehouse
Enablement
Pack
Implementation
Guide,
SC32–1409
Provides
information
that
helps
users
deploy
and
use
Tivoli
Enterprise
Data
Warehouse
with
the
Workflow
function
in
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
MQ.
v
Program
Directory
for
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
MQ
for
z/OS,
GI11-4234-01
Provides
information
about
installing
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
MQ
for
z/OS
systems
in
proxy
mode
or
native
mode.
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
MQ
Integrator
v
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
MQ
Integrator
Reference
Guide,
SC23–4708
Provides
information
about
the
resource
models,
tasks,
and
commands
that
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
MQ
Integrator
provides.
v
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
MQ
Integrator
Warehouse
Enablement
Pack
Implementation
Guide,
SC09–7784
Provides
information
that
helps
users
deploy
and
use
Tivoli
Enterprise
Data
Warehouse
with
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
MQ
Integrator.
v
Program
Directory
for
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
MQ
Integrator
for
z/OS,
GI11-4235
Provides
information
about
installing
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
MQ
Integrator
for
z/OS.
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
InterChange
Server
v
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
Interchange
Server
Reference
Guide
,
SC32–1408
Provides
information
about
the
tasks
and
resource
models
that
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
InterChange
Server
provides.
v
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
Interchange
Server
Warehouse
Enablement
Pack
Implementation
Guide,
SC32–1406
Provides
information
that
helps
users
deploy
and
use
Tivoli
Enterprise
Data
Warehouse
with
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
InterChange
Server.
viii
IBM
Tivoli
Monitoring
for
Business
Integration:
Problem
Determination
Guide
-
Prerequisite
publications
To
use
the
information
in
this
guide
effectively,
you
must
have
some
prerequisite
knowledge,
which
you
can
get
from
the
following
guides:
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,
Version
1.1.0,
SC32-1391.
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
Software
Installation
Service
User’s
Guide
v
Tivoli
Inventory
User’s
Guide
v
Tivoli
Management
Framework
User’s
Guide
v
Tivoli
Enterprise
Installation
Guide,
GC32–0395
v
Tivoli
Management
Framework
Reference
Manual
v
Tivoli
Software
Distribution
User’s
Guide
v
Tivoli
Software
Distribution
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
IBM
WebSphere
MQ
product
documentation
v
IBM
WebSphere
MQ
Integrator
product
documentation
v
IBM
WebSphere
InterChange
Server
product
documentation
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
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
the
following
Web
site:
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.
About
this
guide
ix
http://publib.boulder.ibm.com/tividd/glossary/termsmst04.htm
-
IBM
posts
publications
for
this
and
all
other
Tivoli
products,
as
they
become
available
and
whenever
they
are
updated,
to
the
Tivoli
software
information
center
Web
site.
Access
the
Tivoli
software
information
center
by
first
going
to
the
Tivoli
software
library
at
the
following
Web
address:
http://www.ibm.com/software/tivoli/library/
Scroll
down
and
click
the
Product
manuals
link.
In
the
Tivoli
Technical
Product
Documents
Alphabetical
Listing
window,
click
IBM
Tivoli
Monitoring
for
Business
Integration
to
access
all
of
the
IBM
Tivoli
Monitoring
product
manuals.
Note:
Note:
If
you
print
PDF
documents
on
other
than
letter-sized
paper,
set
the
option
in
the
File
→
Print
window
that
allows
Adobe
Reader
to
print
letter-sized
pages
on
your
local
paper.
The
IBM
Software
Support
Web
site
provides
the
latest
information
about
known
product
limitations
and
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:
x
IBM
Tivoli
Monitoring
for
Business
Integration:
Problem
Determination
Guide
http://www.ibm.com/software/tivoli/library/http://www-3.ibm.com/software/supporthttp://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgihttp://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgihttp://www.ibm.com/software/tivoli/order-lit/http://www.ibm.com/software/sysmgmt/products/support/
-
http://techsupport.services.ibm.com/guides/handbook.html
The
guide
provides
information
about
how
to
contact
IBM
Software
Support,
depending
on
the
severity
of
your
problem,
and
the
following
information:
v
Registration
and
eligibility
v
Telephone
numbers,
depending
on
the
country
in
which
you
are
located
v
Information
you
must
have
before
contacting
IBM
Software
Support
Conventions
used
in
this
guide
This
guide
uses
several
conventions
for
special
terms
and
actions,
and
operating
system-dependent
commands
and
paths.
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)
and
labels
(such
as
Tip:,
and
Operating
system
considerations:)
v
Keywords
and
parameters
in
text
Italic
v
Words
defined
in
text
v
Emphasis
of
words
(words
as
words)
v
New
terms
in
text
(except
in
a
definition
list)
v
Variables
and
values
you
must
provide
Monospace
v
Examples
and
code
examples
v
File
names,
programming
keywords,
and
other
elements
that
are
difficult
to
distinguish
from
surrounding
text
v
Message
text
and
prompts
addressed
to
the
user
v
Text
that
the
user
must
type
v
Values
for
arguments
or
command
options
Operating
system-dependent
variables
and
paths
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.
Note:
If
you
are
using
the
bash
shell
on
a
Windows
system,
you
can
use
the
UNIX
conventions.
About
this
guide
xi
http://techsupport.services.ibm.com/guides/handbook.html
-
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
xi.
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.
xii
IBM
Tivoli
Monitoring
for
Business
Integration:
Problem
Determination
Guide
-
Chapter
1.
Introduction
to
problem
determination
This
problem
determination
guide
explains
how
to
troubleshoot
IBM
Tivoli
Monitoring
for
Business
Integration.
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.
Product
overview
IBM
Tivoli
Monitoring
for
Business
Integration
enables
systems
administrators
to
configure,
monitor,
and
manage
WebSphere
MQ
(including
Workflow),
WebSphere
Interchange
Server,
and
WebSphere
MQ
Integrator
resources
across
distributed
and
z/OS
systems
from
a
central
console.
IBM
Tivoli
Monitoring
for
Business
Integration
incorporates
best
practices
in
monitoring
WebSphere
MQ,
WebSphere
Interchange
Server,
and
WebSphere
MQ
Integrator
resources,
providing
root
cause
analysis
of
problems
and
corrective
action
for
quick
problem
resolution.
IBM
Tivoli
Monitoring
for
Business
Integration
also
provides
the
capability
to
use
Tivoli
Enterprise
Console
and
Tivoli
Business
Systems
Manager
to
monitor
events
from
your
resources.
There
are
three
components
to
IBM
Tivoli
Monitoring
for
Business
Integration:
v
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
MQ
v
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
MQ
Integrator
v
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
InterChange
Server
Built-in
problem
determination
features
The
primary
troubleshooting
feature
in
IBM
Tivoli
Monitoring
for
Business
Integration
is
logging.
Logging
refers
to
the
text
messages
and
trace
data
generated
by
IBM
Tivoli
Monitoring
for
Business
Integration.
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
7,
“Debugging
information,”
on
page
37
for
more
information.
1
-
Problem
classification
For
the
purposes
of
this
document,
problems
and
workarounds
are
presented
by
component:
v
Installation
v
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
MQ
v
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
MQ
Integrator
v
IBM
Tivoli
Monitoring
for
Business
Integration:
WebSphere
InterChange
Server
v
Tivoli
Business
Systems
Manager
integration
2
IBM
Tivoli
Monitoring
for
Business
Integration:
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.
See
the
IBM
Tivoli
Monitoring
for
Business
Integration
Installation
and
Setup
Guide
for
additional
information
about
installation.
Common
installation
problems
and
workarounds
The
following
problems
might
occur
when
you
install
and
set
up
IBM
Tivoli
Monitoring
for
Business
Integration.
Table
1.
Common
installation
problems
and
workarounds
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.
These
systems
are
unable
to
process
the
Rock
Ridge
extensions
used
to
burn
the
IBM
Tivoli
Monitoring
for
Business
Integration
CDs.
You
must
change
how
the
operating
system
mounts
CDs.
See
the
Hewlett-Packard
Company
Web
site
for
information.
The
Patch
Database
in
the
Hewlett-Packard
IT
Resource
Center
has
information
for
some
versions.
When
you
run
the
installer
on
UNIX,
a
Java™
exception
message
like
the
following
might
be
displayed
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.
You
might
see
the
following
error
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.
The
depot
directory
contains
all
the
files
required
for
installation.
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.
3
-
Table
1.
Common
installation
problems
and
workarounds
(continued)
Problem
Workaround
The
Browse
option
in
the
installer
panels
requires
a
long
time
period
to
launch
the
file
selection
dialog
box.
This
problem
occurs
when
the
computer
has
multiple
file
systems
mounted.
The
installer
verifies
connectivity
with
each
file
system
before
presenting
the
dialog
box.
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.
This
problem
occurs
when
you
click
Browse
while
the
CD-ROM
drive
is
empty.
After
the
problem
occurs,
you
cannot
resolve
the
problem
by
inserting
a
CD
into
the
drive.
Type
the
path
of
the
target
file
system
in
the
text
box
to
directly
access
the
CD.
Avoid
the
problem
in
subsequent
installer
panels
by
making
sure
a
CD
is
in
the
CD-ROM
drive
before
you
click
Browse.
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.
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
Business
Integration.
This
requirement
applies
to
the
Tivoli
management
region
server
and
all
managed
nodes
and
endpoints
in
the
Tivoli
environment.
You
can
obtain
this
file
from
Microsoft®
or
on
the
product
CD
for
Windows
NT®
or
Windows
2000
in
all
language
versions
of
these
operating
systems.
The
kbdus.dll
file
must
be
in
the
%SystemRoot%\system32
directory.
The
installer
reports
failure
of
installation
of
language
support
packs
for
the
Tivoli
Management
Framework,
Version
4.1
component
of
the
product.
After
installation
is
complete,
manually
install
the
language
pack
or
packs
for
Tivoli
Management
Framework,
Version
4.1.
Use
the
Tivoli
desktop
or
winstall
command,
as
described
in
the
IBM
Tivoli
Monitoring
for
Business
Integration
Installation
and
Setup
Guide.
4
IBM
Tivoli
Monitoring
for
Business
Integration:
Problem
Determination
Guide
-
Table
1.
Common
installation
problems
and
workarounds
(continued)
Problem
Workaround
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
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.
Proxy-mode
z/OS-specific
installation
and
configuration
problems
The
following
problems
might
occur
when
you
install
IBM
Tivoli
Monitoring
for
Business
Integration
on
z/OS
systems.
Table
2.
Proxy-mode
z/OS-specific
installation
and
configuration
problems
Problem
Workaround
When
you
run
the
hostcmd
″mvs
d
a,l″
command,
you
might
receive
the
FRWSL0007E
message
and
an
IhsiSend
return
code
of
5.
TSERVER
is
not
started
or
has
stopped.
On
the
Tivoli
Business
Systems
Manager
task
server,
run
the
tserver
start
command
from
the
TDS\EventService\TDS
directory.
When
you
run
the
hostcmd
″mvs
d
a,l″
command,
you
might
receive
an
IhsiSend
return
code
of
8006.
The
NetConv
command
was
not
run
from
the
NetView
Operator
NCCF
console,
or
the
NetConv
session
was
stopped.
Restart
the
NetConv
session.
Also,
ensure
that
the
CNMTAMEL
task
was
started.
If
necessary,
restart
the
CNMTAMEL
task
from
the
NetView
Operator
NCCF
console
and
rerun
the
NetConv
command.
When
you
run
the
hostcmd
″mvs
d
a,l″
-h
host_name
command,
you
might
receive
an
IhsiSend
return
code
of
8007.
NetView
does
not
recognize
the
value
for
host_name.
Check
the
spelling
of
the
name.
Ensure
that
the
host
name
is
defined
on
the
focal
point
system.
(A
focal
point
system
is
an
instance
of
IBM
Tivoli
NetView
for
z/OS
that
enables
Tivoli
communication
with
multiple
z/OS
systems.)
Ensure
that
you
can
successfully
run
a
ping
command
against
host_name
from
the
computer
where
the
task
server
is
running.
When
you
run
the
hostcmd
″mvs
d
a,l″
command,
you
might
receive
an
IhsiSend
return
code
of
8004.
The
NetView
Operator
is
no
longer
logged
on
to
NetView,
or
the
password
is
incorrect.
Verify
that
the
NetView
Operator
is
logged
on.
Use
the
hostcmdoper
-s
command
to
display
the
NetView
Operator
name.
Rerun
the
hostcmdoper
command
with
the
-u
and
-p
parameters
to
redefine
the
NetView
Operator
ID
and
password.
Chapter
2.
Installation
problem
determination
5
-
Table
2.
Proxy-mode
z/OS-specific
installation
and
configuration
problems
(continued)
Problem
Workaround
When
you
run
the
hostcmd
″netvasis
pipe
unix
pwd|corr
10|cons″
command,
you
might
not
receive
the
expected
output
after
10
seconds.
The
CorrWait
timeout
value
might
be
too
low.
Try
increasing
the
corr
value
to
20
or
30.
When
you
run
the
hostcmd
″netvasis
pipe
unix
pwd|corr
20|cons″
command,
you
might
receive
an
immediate
response
that
does
not
include
the
expected
output.
The
NetView
UNIX
Command
Server
might
not
have
been
started,
or
it
was
stopped.
Run
the
start
unixserv=*
command
from
the
NetView
Command
Facility
console
(called
NCCF).
Resolving
installer
problems
Objective
To
resolve
or
work
around
common
problems
that
can
arise
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
installations,
described
in
the
IBM
Tivoli
Monitoring
for
Business
Integration
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
Business
Integration
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.
Additional
information:
If
you
click
Cancel
without
allowing
the
currently
running
process
to
finish,
the
system
might
remain
in
an
unpredictable
state.
6
IBM
Tivoli
Monitoring
for
Business
Integration:
Problem
Determination
Guide
-
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
3
shows
the
status
icons
and
options
in
the
Detail
window:
Table
3.
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.
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
clicking
Execute
(see
description
below).
If
you
defer
a
step
before
it
is
run
(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
Runs
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.
Chapter
2.
Installation
problem
determination
7
-
Table
3.
Status
icons
and
options
for
the
Step
List
panel
of
the
installer
(continued)
Name
Icon
Value
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.
v
Message
logs:
Have
the
following
resources
available
for
IBM
Software
Support
in
case
of
installation
errors
–
The
message
log
in
the
following
directory:
tivoli/depot/DeployEngine/logs/deploy.log.
IBM
Software
Support
uses
this
file
to
determine
the
source
of
problems.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.
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
3
on
page
7
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,
run
the
steps
that
you
deferred.
Additional
information:
For
example,
you
can
successfully
run
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
to
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.
8
IBM
Tivoli
Monitoring
for
Business
Integration:
Problem
Determination
Guide
-
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:
Additional
information:
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
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
Business
Integration
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.
c.
Analyze
the
installation
logs.
See
Chapter
7,
“Debugging
information,”
on
page
37
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
Business
Integration
endpoints
it
manages.
The
endpoint
is
software
that
you
install
on
a
Business
Integration
server
to
enable
communication.
On
z/OS:
This
procedure
can
confirm
whether
communications
are
failing
at
the
endpoint.
When
you
test
connectivity
on
z/OS
systems,
you
must
consider
the
flow
of
information
in
the
Tivoli
environment.
For
Monitoring
for
WebSphere
MQ
for
z/OS
systems
see
the
IBM
Tivoli
Monitoring
for
Business
Integration
User’s
Guide
for
details
regarding
the
flow
of
information.
Required
authorization
On
UNIX,
the
user
who
installs
the
managed
nodes
must
have
root
privileges.
On
Windows,
the
user
who
installs
the
product
must
have
membership
in
the
Administrators
group.
Before
you
begin
None
Chapter
2.
Installation
problem
determination
9
-
When
you
finish
If
endpoint
connectivity
problems
continue,
you
might
need
to
reinstall
your
endpoint.
See
the
Tivoli
Management
Framework
documentation
for
additional
information.
Procedure
Command
line:
1.
Access
the
Tivoli
environment.
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
view_version
where
is
the
name
of
a
specific
endpoint
on
a
Business
Integrator
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
single
version
number,
the
endpoint
software
must
be
restarted.
You
can
manually
restart
the
endpoint
on
that
server
as
follows:
v
On
Windows
systems:
a.
Run
the
following
command
to
stop
lcfd,
the
process
of
the
endpoint:
net
stop
lcfd
b.
Run
the
following
command
to
start
the
lcfd
process:
net
start
lcfd
v
On
UNIX
systems:
a.
Use
the
following
command
to
identify
the
lcfd
process:
ps
-ef
|
grep
lcfd
b.
Kill
this
process
using
a
command
like
the
following:
kill
-9
where
is
the
ID
of
the
process.
c.
Use
the
following
command
to
set
the
required
environment
variables:
.
/etc/Tivoli/lcf//lcf_env.sh
d.
Use
the
following
command
to
restart
the
lcfd
process:
$LCF_BINDIR/lcfd.sh
6.
Monitor
the