ibm tivoli service level advisor:...
TRANSCRIPT
-
IBM
Tivoli
Service
Level
Advisor
Messages
Version
2.1
SC32-1250-01
-
IBM
Tivoli
Service
Level
Advisor
Messages
Version
2.1
SC32-1250-01
-
Second
Edition
(September
2004)
This
edition
applies
to
Version
2.1
of
IBM
Tivoli
Service
Level
Advisor
(program
number
5724C40)
and
to
all
subsequent
releases
and
modifications
until
otherwise
indicated
in
new
editions.
Copyright
International
Business
Machines
Corporation
2002,
2004.
All
rights
reserved.
US
Government
Users
Restricted
Rights
Use,
duplication
or
disclosure
restricted
by
GSA
ADP
Schedule
Contract
with
IBM
Corp.
-
Contents
Preface
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. v
Who
should
read
this
guide
.
.
.
.
.
.
.
.
. v
Publications
.
.
.
.
.
.
.
.
.
.
.
.
.
. v
IBM
Tivoli
Service
Level
Advisor
library
.
.
.
. v
IBM
DB2
Universal
Database
Enterprise
Edition
library
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. vi
Tivoli
Data
Warehouse
library
.
.
.
.
.
.
. vi
Warehouse
Enablement
Packs
.
.
.
.
.
.
. vi
IBM
WebSphere
Application
Server
library
.
.
. vii
SLM
Administrative
Console
Information
.
.
. vii
Related
publications
.
.
.
.
.
.
.
.
.
. vii
Accessing
Publications
Online
.
.
.
.
.
.
.
. vii
Ordering
publications
.
.
.
.
.
.
.
.
.
.
. vii
Accessibility
.
.
.
.
.
.
.
.
.
.
.
.
.
. viii
Tivoli
technical
training
.
.
.
.
.
.
.
.
.
. viii
Contacting
IBM
Software
Support
.
.
.
.
.
. viii
Determine
the
business
impact
of
your
problem
ix
Describe
your
problem
and
gather
background
information
.
.
.
.
.
.
.
.
.
.
.
.
. ix
Submit
your
problem
to
IBM
Software
Support
. ix
Searching
knowledge
bases
.
.
.
.
.
.
.
. x
Obtaining
fixes
.
.
.
.
.
.
.
.
.
.
.
. x
Updating
support
information
.
.
.
.
.
.
. x
Participating
in
newsgroups
.
.
.
.
.
.
.
.
. xi
Conventions
used
in
this
guide
.
.
.
.
.
.
.
. xii
Typeface
conventions
.
.
.
.
.
.
.
.
.
. xii
Operating
system-dependent
variables
and
paths
xii
Messages
for
IBM
Tivoli
Service
Level
Advisor
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 1
Appendix.
Notices
.
.
.
.
.
.
.
.
. 175
Trademarks
.
.
.
.
.
.
.
.
.
.
.
.
.
. 176
Copyright
IBM
Corp.
2002,
2004
iii
-
iv
IBM
Tivoli
Service
Level
Advisor:
Messages
-
Preface
This
document
provides
a
listing
of
messages
that
accompany
IBM
Tivoli
Service
Level
Advisor.
Use
this
guide
for
details
and
recovery
actions
related
to
informational,
warning,
and
error
messages
that
you
may
receive
while
using
the
product.
Who
should
read
this
guide
This
document
is
written
for
systems
administrators
and
Tivoli
Professional
Services
personnel
who
need
additional
information
on
messages
that
are
displayed
during
the
installation
and
regular
use
of
IBM
Tivoli
Service
Level
Advisor.
Publications
This
section
lists
publications
in
the
IBM
Tivoli
Service
Level
Advisor
library
and
other
related
documents.
It
also
describes
how
to
access
Tivoli
publications
online,
and
how
to
order
Tivoli
publications.
IBM
Tivoli
Service
Level
Advisor
library
Product
information
for
using
IBM
Tivoli
Service
Level
Advisor
is
found
in
the
/tsladocs
directory
on
the
IBM
Tivoli
Service
Level
Advisor
Documentation
CD,
in
PDF
and
HTML
formats.
Inserting
the
Documentation
CD
into
a
machine
using
the
Windows
operating
system
automatically
launches
the
Tivoli
Software
Information
Center,
from
which
you
can
access
any
of
the
available
documentation
in
softcopy
form.
The
following
documents
are
available
in
the
IBM
Tivoli
Service
Level
Advisor
library:
v
A
Read
Me
First
document
that
provides
a
starting
point
to
help
you
become
oriented
with
the
set
of
IBM
products
that
support
the
overall
SLM
solution,
and
some
quick
instructions
on
what
documentation
to
refer
to
as
you
begin
your
installation
of
IBM
Tivoli
Service
Level
Advisor
and
its
supporting
applications.
v
Release
Notes,
SC09-7777
This
document
provides
late-breaking
information,
such
as
problems
and
workarounds,
and
patch
availability.
v
Getting
Started,
SC32-0834
This
document
introduces
you
to
IBM
Tivoli
Service
Level
Advisor
and
provides
information
about
planning,
installing,
and
configuring
IBM
Tivoli
Service
Level
Advisor
to
run
in
your
Tivoli
enterprise
environment.
v
Managing
Service
Level
Agreements,
SC32-1247
This
document
provides
information
about
creating
and
managing
schedules,
offerings,
customers,
and
realms,
and
associating
these
elements
with
selected
resources
in
your
enterprise
environment
to
develop
service
level
agreements
(SLAs)
between
your
organization
and
customers
who
depend
on
your
enterprise
for
agreed
upon
levels
of
service.
This
document
is
designed
to
be
used
by
administrators,
service
offering
specialists,
and
service
level
agreement
specialists
who
are
responsible
for
creating
and
managing
SLAs.
v
SLM
Reports,
SC32-1248
This
document
provides
information
about
generating
and
viewing
Web-based
SLM
reports
for
IBM
Tivoli
Service
Level
Advisor,
based
on
the
evaluation
and
trend
analysis
results
of
the
data
that
is
extracted
from
the
Tivoli
Data
Warehouse
database.
Additional
information
is
provided
so
that
you
or
your
customer
can
integrate
SLM
reports
into
the
customer
Web
site,
including
examples
of
how
you
can
customize
various
display
features.
Copyright
IBM
Corp.
2002,
2004
v
-
v
Administrators
Guide,
SC32-0835
This
document
provides
information
about
the
administrative
tasks
you
can
perform
using
IBM
Tivoli
Service
Level
Advisor
to
configure
your
SLM
environment,
and
perform
various
administrative
functions
that
support
IBM
Tivoli
Service
Level
Advisor,
such
as
backup
and
restore
operations,
and
user
definition
and
authorization.
v
Command
Reference,
SC32-0833
This
document
provides
information
on
command
line
interface
(CLI)
commands
available
for
displaying
certain
conditions
and
states
inside
IBM
Tivoli
Service
Level
Advisor,
and
for
performing
various
configuration
tasks
using
the
scmd
command.
Additional
utilities
that
provide
other
specific
functions
are
also
described.
v
Messages,
SC32-1250
This
document
provides
information
on
messages
that
might
be
displayed
while
using
the
IBM
Tivoli
Service
Level
Advisor
product.
It
provides
additional
explanations
for
messages
and
instructions
on
what
to
do
to
recover
from
errors.
v
Troubleshooting,
SC32-1249
This
document
provides
information
on
resolving
problems
that
you
might
encounter
during
installation
and
configuration,
as
well
as
resolving
administrative
problems
that
might
arise
during
typical
operation
of
the
product.
Information
about
message
and
trace
logging
is
also
provided.
v
Online
user
assistance
for
IBM
Tivoli
Service
Level
Advisor
The
online
user
assistance
provides
integrated
online
help
topics
for
all
IBM
Tivoli
Service
Level
Advisor
administrative
tasks
that
are
performed
using
the
SLM
Administrative
Console.
Online
user
assistance
is
displayed
in
the
Task
Assistant
portion
of
the
SLM
Administrative
Console.
Specific
information
about
performing
IBM
Tivoli
Service
Level
Advisor
tasks
is
documented
only
in
this
online
user
assistance.
When
new
products
are
installed
that
run
in
the
SLM
Administrative
Console,
corresponding
online
help
topics
are
also
installed
and
integrated
into
the
existing
information
base.
In
addition,
refer
to
the
following
IBM
Tivoli
Service
Level
Advisor
Web
site
for
support
information
and
software
updates
on
IBM
Tivoli
Service
Level
Advisor
and
supported
warehouse
packs
and
downloadable
interim
fix
software:
http://www.ibm.com/software/sysmgmt/products/support
/IBMTivoliServiceLevelAdvisor.html
IBM
DB2
Universal
Database
Enterprise
Edition
library
The
publications
required
to
support
IBM
DB2
Universal
Database
Enterprise
Edition
are
available
on
the
IBM
DB2
Universal
Database
Enterprise
Edition
CD,
or
from
this
IBM
Web
site:
http://www.ibm.com/software/data/db2/udb
Tivoli
Data
Warehouse
library
IBM
Tivoli
Service
Level
Advisor
requires
Tivoli
Data
Warehouse
to
be
installed
in
your
enterprise,
to
serve
as
the
data
repository
for
Tivoli
performance
and
availability
monitoring
applications
that
provide
data
for
service
level
management.
See
the
following
documentation
on
the
Tivoli
Data
Warehouse
Documentation
CD
included
with
IBM
Tivoli
Service
Level
Advisor:
v
Installing
and
Configuring
Tivoli
Data
Warehouse
v
Enabling
an
Application
for
Tivoli
Data
Warehouse
v
Tivoli
Data
Warehouse
Release
Notes
Warehouse
Enablement
Packs
Warehouse
enablement
packs
(also
referred
to
as
warehouse
packs)
are
the
interfaces
that
load
and
transform
data
collected
by
source
applications
into
Tivoli
Data
Warehouse,
and
from
Tivoli
Data
vi
IBM
Tivoli
Service
Level
Advisor:
Messages
http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliServiceLevelAdvisor.htmlhttp://www.ibm.com/software/sysmgmt/products/support/IBMTivoliServiceLevelAdvisor.htmlhttp://www.ibm.com/software/data/db2/udb
-
Warehouse
to
other
target
applications
that
use
the
data
to
generate
reports
and
perform
analyses.
Refer
to
the
Release
Notes
for
IBM
Tivoli
Service
Level
Advisor
for
the
online
location
of
the
latest
warehouse
pack
information.
IBM
WebSphere
Application
Server
library
IBM
Tivoli
Service
Level
Advisor
uses
IBM
WebSphere
Application
Server
as
the
basis
for
the
SLM
Administration
Server
and
SLM
Reports
functions.
Getting
Started
provides
introductory
information
on
installing
IBM
WebSphere
Application
Server
and
integrating
it
with
IBM
Tivoli
Service
Level
Advisor.
See
the
official
documentation
provided
on
the
IBM
WebSphere
Application
Server
product
media
included
with
IBM
Tivoli
Service
Level
Advisor
for
additional
information,
and
also
refer
to
the
latest
IBM
WebSphere
Application
Server
product
information
online
at
the
following
Web
site:
http://www.ibm.com/software/webservers/appserv/was/library
SLM
Administrative
Console
Information
IBM
Tivoli
Service
Level
Advisor
provides
the
SLM
Administrative
Console,
a
Web-based
Administration
Server
graphical
user
interface
(GUI)
that
runs
in
the
IBM
WebSphere
environment,
from
which
you
can
create
and
manage
schedules,
offerings,
customers,
realms,
and
SLAs.
Information
on
the
use
of
the
SLM
Administrative
Console
and
tasks
related
to
creating
and
managing
SLAs
are
described
in
detail
in
Managing
Service
Level
Agreements.
User
assistance
for
the
SLM
Administrative
Console
is
available
in
the
Task
Assistant
online
help
function.
Related
publications
The
following
documents
also
provide
useful
information:
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
Access
the
glossary
by
clicking
the
Glossary
link
on
the
left
pane
of
the
Tivoli
software
library
window.
Accessing
Publications
Online
In
addition
to
the
Documentation
CD
that
is
shipped
with
IBM
Tivoli
Service
Level
Advisor,
you
can
also
access
these
publications
online.
IBM
posts
publications
for
this
and
all
other
Tivoli
products,
as
they
become
available
and
whenever
they
are
updated,
to
the
Tivoli
software
information
center
Web
site.
Access
the
Tivoli
software
information
center
by
first
going
to
the
Tivoli
software
library
at
the
following
Web
address:
http://www.ibm.com/software/tivoli/library
Scroll
down
and
click
the
Product
manuals
link.
In
the
Tivoli
Technical
Product
Documents
Alphabetical
Listing
window,
click
the
IBM
Tivoli
Service
Level
Advisor
link
to
access
the
product
library
at
the
Tivoli
software
information
center.
Note:
If
you
print
PDF
documents
on
other
than
letter-sized
paper,
set
the
option
in
the
File
>
Print
window
that
allows
Adobe
Reader
to
print
letter-sized
pages
on
your
local
paper.
Ordering
publications
You
can
order
many
Tivoli
publications
online
at
the
following
Web
site:
http://www.elink.ibmlink.ibm.com/public/applications/publications
/cgibin/pbi.cgi
You
can
also
order
by
telephone
by
calling
one
of
these
numbers:
Preface
vii
http://www.ibm.com/software/webservers/appserv/was/libraryhttp://publib.boulder.ibm.com/tividd/glossary/termsmst04.htmhttp://www.ibm.com/software/tivoli/libraryhttp://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgihttp://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgi
-
v
In
the
United
States:
800-879-2755
v
In
Canada:
800-426-4968
In
other
countries,
see
the
following
Web
site
for
a
list
of
telephone
numbers:
http://www.ibm.com/software/tivoli/order-lit/
Accessibility
Accessibility
features
help
users
with
a
physical
disability,
such
as
restricted
mobility
or
limited
vision,
to
use
software
products
successfully.
With
this
product,
you
can
use
assistive
technologies
to
hear
and
navigate
the
interface.You
can
also
use
the
keyboard
instead
of
the
mouse
to
operate
all
features
of
the
graphical
user
interface.
Tivoli
technical
training
For
Tivoli
technical
training
information,
refer
to
the
following
IBM
Tivoli
Education
Web
site:
http://www.ibm.com/software/tivoli/education
Contacting
IBM
Software
Support
IBM
Software
Support
provides
assistance
with
product
defects.
Before
contacting
IBM
Software
Support,
your
company
must
have
an
active
IBM
software
maintenance
contract,
and
you
must
be
authorized
to
submit
problems
to
IBM.
The
type
of
software
maintenance
contract
that
you
need
depends
on
the
type
of
product
you
have:
v
For
IBM
distributed
software
products
(including,
but
not
limited
to,
Tivoli,
Lotus,
and
Rational
products,
as
well
as
DB2
and
WebSphere
products
that
run
on
Windows
or
UNIX
operating
systems),
enroll
in
Passport
Advantage
in
one
of
the
following
ways:
Online:
Go
to
the
following
Passport
Advantage
Web
page
and
click
How
to
Enroll:
http://www.lotus.com/services/passport.nsf/WebDocs
/Passport_Advantage_Home
By
phone:
For
the
phone
number
to
call
in
your
country,
go
to
the
following
IBM
Software
Support
Web
site
and
click
the
name
of
your
geographic
region:
http://techsupport.services.ibm.com/guides/contacts.html
v
For
IBM
eServer
software
products
(including,
but
not
limited
to,
DB2
and
WebSphere
products
that
run
in
zSeries,
pSeries,
and
iSeries
environments),
you
can
purchase
a
software
maintenance
agreement
by
working
directly
with
an
IBM
sales
representative
or
an
IBM
Business
Partner.
For
more
information
about
support
for
eServer
software
products,
go
to
the
IBM
Technical
Support
Advantage
Web
page:
http://www.ibm.com/servers/eserver/techsupport.html
If
you
are
not
sure
what
type
of
software
maintenance
contract
you
need,
call
1-800-IBMSERV
(1-800-426-7378)
in
the
United
States
or,
from
other
countries,
go
to
the
contacts
page
of
the
following
IBM
Software
Support
Handbook
on
the
Web
and
click
the
name
of
your
geographic
region
for
phone
numbers
of
people
who
provide
support
for
your
location:
http://techsupport.services.ibm.com/guides/contacts.html
Follow
the
steps
in
this
topic
to
contact
IBM
Software
Support:
1.
Determine
the
business
impact
of
your
problem.
2.
Describe
your
problem
and
gather
background
information.
3.
Submit
your
problem
to
IBM
Software
Support.
viii
IBM
Tivoli
Service
Level
Advisor:
Messages
http://www.ibm.com/software/tivoli/order-lit/http://www.ibm.com/software/tivoli/educationhttp://www.lotus.com/services/passport.nsf/WebDocs/Passport_Advantage_Homehttp://www.lotus.com/services/passport.nsf/WebDocs/Passport_Advantage_Homehttp://techsupport.services.ibm.com/guides/contacts.htmlhttp://www.ibm.com/servers/eserver/techsupport.htmlhttp://techsupport.services.ibm.com/guides/contacts.html
-
Determine
the
business
impact
of
your
problem
When
you
report
a
problem
to
IBM,
you
are
asked
to
supply
a
severity
level.
Therefore,
you
need
to
understand
and
assess
the
business
impact
of
the
problem
you
are
reporting.
Use
the
following
criteria
to
decide
on
an
appropriate
severity
level
for
your
problem:
Severity
1
Critical
business
impact:
You
are
unable
to
use
the
program,
resulting
in
a
critical
impact
on
operations.
This
condition
requires
an
immediate
solution.
Severity
2
Significant
business
impact:
The
program
is
usable
but
is
severely
limited.
Severity
3
Some
business
impact:
The
program
is
usable
with
less
significant
features
(not
critical
to
operations)
unavailable.
Severity
4
Minimal
business
impact:
The
problem
causes
little
impact
on
operations,
or
a
reasonable
circumvention
to
the
problem
has
been
implemented.
Describe
your
problem
and
gather
background
information
When
explaining
a
problem
to
IBM,
be
as
specific
as
possible.
Include
all
relevant
background
information
so
that
IBM
Software
Support
specialists
can
help
you
solve
the
problem
efficiently.
To
save
time,
know
the
answers
to
these
questions:
v
What
software
versions
were
you
running
when
the
problem
occurred?
v
Do
you
have
logs,
traces,
and
messages
that
are
related
to
the
problem
symptoms?
IBM
Software
Support
is
likely
to
ask
for
this
information.
v
Can
the
problem
be
recreated?
If
so,
what
steps
led
to
the
failure?
v
Have
any
changes
been
made
to
the
system?
(For
example,
hardware,
operating
system,
networking
software,
and
so
on.)
v
Are
you
currently
using
a
workaround
for
this
problem?
If
so,
please
be
prepared
to
explain
it
when
you
report
the
problem.
Submit
your
problem
to
IBM
Software
Support
You
can
submit
your
problem
in
one
of
two
ways:
v
Online:
Go
to
the
Submit
and
track
problems
page
on
the
IBM
Software
Support
site:
http://www.ibm.com/software/support/probsub.html
Enter
your
information
into
the
appropriate
problem
submission
tool.
v
Do
you
have
logs,
traces,
and
messages
that
are
related
to
the
problem
symptoms?
IBM
Software
Support
is
likely
to
ask
for
this
information.
v
Can
the
problem
be
recreated?
If
so,
what
steps
led
to
the
failure?
v
Have
any
changes
been
made
to
the
system?
(For
example,
hardware,
operating
system,
networking
software,
and
so
on.)
v
Are
you
currently
using
a
workaround
for
this
problem?
If
so,
please
be
prepared
to
explain
it
when
you
report
the
problem.
If
the
problem
you
submit
is
for
a
software
defect
or
for
missing
or
inaccurate
documentation,
IBM
Software
Support
creates
an
Authorized
Program
Analysis
Report
(APAR).
The
APAR
describes
the
problem
in
detail.
Whenever
possible,
IBM
Software
Support
provides
a
workaround
for
you
to
implement
until
the
APAR
is
resolved
and
a
fix
is
delivered.
IBM
publishes
resolved
APARs
on
the
IBM
product
support
Web
pages
daily,
so
that
other
users
who
experience
the
same
problem
can
benefit
from
the
same
resolutions.
For
more
information
about
problem
resolution,
see
Searching
knowledge
bases
on
page
x
and
Obtaining
fixes
on
page
x.
Preface
ix
http://www.ibm.com/software/support/probsub.html
-
Searching
knowledge
bases
If
you
have
a
problem
with
your
IBM
software,
you
want
it
resolved
quickly.
Begin
by
searching
the
available
knowledge
bases
to
determine
whether
the
resolution
to
your
problem
is
already
documented.
Search
the
information
center
on
your
local
system
or
network
IBM
provides
extensive
documentation
that
can
be
installed
on
your
local
machine
or
on
an
intranet
server.
You
can
use
the
search
function
of
this
information
center
to
query
conceptual
information,
instructions
for
completing
tasks,
reference
information,
and
support
documents.
Tip:
Update
your
information
center
with
the
latest
support
information.
Search
the
Internet
If
you
cannot
find
an
answer
to
your
question
in
the
information
center,
search
the
Internet
for
the
latest,
most
complete
information
that
might
help
you
resolve
your
problem.
To
search
multiple
Internet
resources
for
your
product,
expand
the
product
folder
in
the
navigation
frame
to
the
left
and
select
Support
on
the
Web.
From
this
topic,
you
can
search
a
variety
of
resources
including:
v
IBM
technotes
v
IBM
downloads
v
IBM
Redbooks
v
IBM
DeveloperWorks
v
Forums
and
newsgroups
v
Google
Obtaining
fixes
A
product
fix
might
be
available
to
resolve
your
problem.
You
can
determine
what
fixes
are
available
for
your
IBM
software
product
by
checking
the
product
support
Web
site:
1.
Go
to
the
IBM
Software
Support
Web
site:
http://www.ibm.com/software/support
2.
Under
Products
A
-
Z,
select
your
product
name.
This
opens
a
product-specific
support
site.
3.
Under
Self
help,
follow
the
link
to
All
Updates,
where
you
find
a
list
of
fixes,
fix
packs,
and
other
service
updates
for
your
product.
For
tips
on
refining
your
search,
click
Search
tips.
4.
Click
the
name
of
a
fix
to
read
the
description
and
optionally
download
the
fix.
To
receive
weekly
e-mail
notifications
about
fixes
and
other
news
about
IBM
products,
follow
these
steps:
1.
From
the
support
page
for
any
IBM
product,
click
My
support
in
the
upper-right
corner
of
the
page.
2.
If
you
have
already
registered,
skip
to
the
next
step.
If
you
have
not
registered,
click
register
in
the
upper-right
corner
of
the
support
page
to
establish
your
user
ID
and
password.
3.
Sign
in
to
My
support.
4.
On
the
My
support
page,
click
Edit
profiles
in
the
left
navigation
pane,
and
scroll
to
Select
Mail
Preferences.
Select
a
product
family
and
select
the
appropriate
boxes
for
the
type
of
information
you
want.
5.
Click
Submit.
6.
For
e-mail
notification
for
other
products,
repeat
Steps
4
and
5.
For
more
information
about
types
of
fixes,
see
the
Software
Support
Handbook:
http://techsupport.services.ibm.com/guides/handbook.html
Updating
support
information
Information
centers
typically
include
one
or
more
support
information
plug-ins.
These
plug-ins
add
IBM
technotes
and
other
support
documents
to
the
information
center.
The
following
steps
describe
how
to
update
your
support
information
plug-ins:
x
IBM
Tivoli
Service
Level
Advisor:
Messages
http://www.ibm.com/software/supporthttp://techsupport.services.ibm.com/guides/handbook.html
-
1.
Go
to
the
IBM
Software
Support
Web
site:
http://www.ibm.com/software/support
2.
Under
Products
A
-
Z,
select
your
product
name.
This
opens
a
product-specific
support
site.
3.
Under
Search
support
for
this
product,
type
the
keyword
phrase:
com.ibm.support.
Select
the
Download
check
box,
and
click
Submit.
4.
Check
the
search
results
for
updates
to
support
information
plug-ins.
All
support
information
plug-ins
follow
the
naming
convention,
com.ibm.support.product.doc.
If
an
update
is
available,
select
it
from
the
list
and
view
the
download
instructions.
5.
Save
the
attached
zip
file
to
a
temporary
location
on
your
hard
drive.
6.
Unzip
the
downloaded
file,
making
sure
that
you
retain
the
subfolders.
7.
From
the
location
where
you
unzipped
the
file,
copy
the
support
information
plug-in
folder
to
your
Eclipse
plug-ins
folder.
For
example,
if
your
IBM
software
product
is
installed
at
c:\IBM\WebSphere\,
copy
the
updated
plug-in
folder
(com.ibm.support.product.doc)
to
c:\IBM\WebSphere\eclipse\plugins.
8.
To
see
the
updated
support
information,
start
the
information
center
(or
shut
it
down
and
restart
it),
and
expand
the
Support
information
node
in
the
navigation
tree.
Participating
in
newsgroups
User
groups
provide
software
professionals
with
a
forum
for
communicating
ideas,
technical
expertise,
and
experiences
related
to
the
product.
They
are
located
on
the
Internet,
and
are
available
using
standard
news
reader
programs.
These
groups
are
primarily
intended
for
user-to-user
communication,
and
are
not
a
replacement
for
formal
support.
If
you
use
Mozilla
as
your
browser,
complete
the
following
instructions
to
access
a
newsgroup:
1.
Open
a
Mozilla
browser
window.
2.
From
the
Edit
menu,
click
Preferences.
The
Preferences
window
is
displayed.
3.
In
the
Category
view,
click
Mail
&
Newsgroups
to
display
the
Mail
&
Newsgroups
settings.
4.
Select
the
Use
Mozilla
mail
as
the
default
mail
application
check
box.
5.
Click
OK.
6.
Close
your
Mozilla
browser
and
then
open
it
again.
7.
Cut
and
paste
the
newsgroup
address
of
a
product
into
the
browser
Address
field,
and
press
Enter
to
open
the
newsgroup.
If
you
use
Microsoft
Internet
Explorer
as
your
browser,
complete
the
following
instructions
to
access
a
newsgroup:
1.
Open
an
Internet
Explorer
browser.
2.
From
the
Tools
menu,
click
Internet
Options.
3.
On
the
Internet
Options
window,
click
the
Programs
tab.
4.
In
the
Newsgroups
list,
click
the
Down
Arrow
and
then
click
Outlook
Express.
5.
Click
OK.
6.
Close
your
Internet
Explorer
browser
and
then
open
it
again.
7.
Cut
and
paste
the
newsgroup
address
of
a
product
into
the
browser
Address
field,
and
press
Enter
to
open
the
newsgroup.
You
can
find
information
on
Tivoli
Data
Warehouse
by
accessing
the
following
newsgroup:
news://news.software.ibm.com/ibm.software.tivoli.enterprise-data-warehouse
You
can
find
information
on
IBM
Tivoli
Service
Level
Advisor
by
accessing
the
following
newsgroup:
news://news.software.ibm.com/ibm.software.tivoli.service-level-advisor
Preface
xi
http://www.ibm.com/software/supportnews://news.software.ibm.com/ibm.software.tivoli.enterprise-data-warehousenews://news.software.ibm.com/ibm.software.tivoli.service-level-advisor
-
You
can
find
information
on
IBM
DB2
by
accessing
the
following
newsgroup:
news://news.software.ibm.com/ibm.software.db2
You
can
find
information
on
IBM
WebSphere
Application
Server
by
accessing
the
following
newsgroup:
news://news.software.ibm.com/ibm.software.websphere.application-server
Conventions
used
in
this
guide
This
guide
uses
several
conventions
for
special
terms
and
actions,
operating
system-dependent
commands
and
paths,
and
margin
graphics.
Typeface
conventions
This
guide
uses
the
following
typeface
conventions:
Bold
v
Lowercase
commands
and
mixed
case
commands
that
are
otherwise
difficult
to
distinguish
from
surrounding
text
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
Citations
(titles
of
books,
diskettes,
and
CDs)
v
Words
defined
in
text
v
Emphasis
of
words
(words
as
words)
v
New
terms
in
text
(except
in
a
definition
list)
v
Variables
and
values
you
must
provide
Monospace
v
Examples
and
code
examples
v
File
names,
programming
keywords,
and
other
elements
that
are
difficult
to
distinguish
from
surrounding
text
v
Message
text
and
prompts
addressed
to
the
user
v
Text
that
the
user
must
type
v
Values
for
arguments
or
command
options
Operating
system-dependent
variables
and
paths
This
guide
uses
the
UNIX
convention
for
specifying
environment
variables
and
for
directory
notation.
When
using
the
Windows
command
line,
replace
$variable
with
%
variable%
for
environment
variables
and
replace
each
forward
slash
(/)
with
a
backslash
(
\)
in
directory
paths.
The
names
of
environment
variables
are
not
always
the
same
in
Windows
and
UNIX.
For
example,
%TEMP%
in
Windows
is
equivalent
to
$tmp
in
UNIX.
Note:
If
you
are
using
the
bash
shell
on
a
Windows
system,
you
can
use
the
UNIX
conventions.
xii
IBM
Tivoli
Service
Level
Advisor:
Messages
news://news.software.ibm.com/ibm.software.db2news://news.software.ibm.com/ibm.software.websphere.application-server
-
Messages
for
IBM
Tivoli
Service
Level
Advisor
DYKAL0001I
The
server
will
be
constructed
using
the
following
properties:
Property
List
Explanation:
No
additional
information
is
available
for
this
message.
DYKAL0002I
The
server
is
named
Name
Explanation:
No
additional
information
is
available
for
this
message.
DYKAL0003E
The
host
name
of
the
machine,
Name,
could
not
be
found.
This
may
be
an
invalid
name,
or
the
server
might
not
be
functional.
Explanation:
The
server
could
not
obtain
the
host
name
of
the
machine.
The
host
name
is
necessary
for
configuration
and
runtime
purposes.
Operator
Response:
Verify
that
the
machine
has
a
host
name
that
is
valid.
On
most
platforms,
this
can
be
done
with
the
hostname
command.
If
the
machine
has
a
valid
host
name
and
the
problem
persists,
contact
Tivoli
Customer
Support
for
further
assistance.
DYKAL0004E
Method
Method
name
is
not
available
to
server
Name.
Explanation:
An
internal
error
has
occurred.
An
unsupported
function
was
attempted
on
the
server.
Operator
Response:
The
server
might
have
been
improperly
configured.
Contact
Tivoli
Customer
Support
for
further
instructions.
Level
3
Support:
This
usually
indicates
that
some
form
of
server
functionality
was
attempted
on
a
GUI
or
SERVLET
adapter
layer.
For
instance,
firing
a
non
SLA
event.
The
error
is
likely
a
programming
error
and
needs
to
be
traced
to
the
caller
for
resolution.
DYKAL0005E
SLA
request
Customer
order
ID
could
not
be
delivered
because
the
SLM
Server
Name
could
not
be
located
on
port
Port.
Verify
that
the
SLM
Server
is
running
and
that
network
communication
is
possible.
Explanation:
The
remote
connection
between
the
SLM
Administration
Server
and
the
remote
SLM
Server
could
not
be
established
to
submit
an
SLA
request.
Operator
Response:
Verify
that
the
remote
SLM
Server
is
running
by
executing
the
following
CLI
command
on
the
referenced
server:
scmd
slm
getstatus.
If
the
SLM
Server
is
running
and
is
operational,
verify
there
is
network
communication
from
the
machine
running
the
SLM
Administration
Server
to
the
remote
SLM
Server
by
using
the
ping
command.
Then,
see
the
Administrators
Guide
documentation
on
server
customization
and
verify
that
the
ports
used
for
remote
communication
on
both
the
SLM
Administration
Server
and
the
SLM
Server
match.
If
the
problem
persists,
contact
Tivoli
Customer
Support
for
further
instructions.
See
also:
The
Administrators
Guide
and
the
Command
Reference
for
more
information
on
setting
server
communication
ports.
DYKAL0006E
SLA
request
Customer
order
ID
could
not
be
delivered
to
the
remote
SLM
Server
Name
on
port
Port
because
a
communication
error
occurred.
See
the
nested
exception
for
details
on
the
error.
Explanation:
The
SLA
request
could
not
be
passed
from
the
Administration
GUIs
to
the
remote
SLM
Server.
Operator
Response:
Verify
that
the
remote
SLM
Server
is
running
by
executing
the
following
CLI
command
on
the
referenced
server:
scmd
slm
getstatus.
If
the
SLM
Server
is
running
and
is
operational,
verify
there
is
network
communication
from
the
machine
running
the
SLM
Administration
Server
to
the
remote
SLM
Server
by
using
the
ping
command.
Then,
see
the
Administrators
Guide
documentation
on
server
customization
and
verify
that
the
ports
used
for
remote
communication
on
both
the
SLM
Administration
Server
and
the
SLM
Server
match.
If
the
problem
persists,
contact
Tivoli
Customer
Support
for
further
instructions.
See
also:
The
Administrators
Guide
and
the
Command
Reference
for
more
information
on
setting
remote
communication
ports.
DYKAL0007E
The
server
cannot
be
launched
because
it
is
not
currently
in
the
Stopped
state.
Explanation:
The
server
must
be
in
the
stopped
state
in
order
to
be
launched.
It
might
currently
be
in
the
running,
starting,
or
stopping
state.
Operator
Response:
Verify
the
current
state
of
the
server
using
the
CLI
command:
scmd
slm
getstatus.
If
the
server
is
in
the
running
or
starting
state,
it
cannot
be
launched
again.
If
the
server
is
stopping,
then
wait
until
the
shutdown
is
complete
before
attempting
to
launch
it
again.
See
also:
The
Command
Reference
for
more
information
on
the
referenced
CLI
command.
Copyright
IBM
Corp.
2002,
2004
1
-
DYKAL0008E
The
server
cannot
be
shut
down
because
it
is
not
currently
in
the
Running
state.
Explanation:
The
server
must
be
in
the
running
state
in
order
to
be
shut
down.
Operator
Response:
Verify
the
current
state
of
the
server
using
the
CLI
command:
scmd
slm
getstatus.
Take
appropriate
action
depending
on
the
current
state.
If
the
server
is
starting,
wait
for
the
startup
sequence
to
complete
and
for
the
server
to
be
in
the
running
state
before
attempting
to
shut
it
down.
If
the
server
is
stopping,
then
shutdown
has
already
been
requested
and
a
second
shutdown
is
not
valid.
See
also:
The
Command
Reference
for
more
information
on
the
referenced
CLI
command.
DYKAL0009E
The
server
host
name
Name
is
not
a
fully
qualified
host
name.
Please
ensure
that
this
machine
is
known
by
the
fully
qualified
host
name.
Explanation:
The
host
name
returned
by
the
operating
system
is
not
fully
qualified.
This
is
a
requirement
for
executing
server
code.
Operator
Response:
Verify
that
the
machine
has
a
fully
qualified
host
name.
On
Windows
ensure
that
the
proper
DNS
suffix
is
specified
in
network
properties.
On
UNIX
platforms
see
the
/etc/nsswitch.conf
file
and
ensure
that
the
DNS
server
is
listed
first.
If
the
problem
persists
consult
operating
system
documentation
for
resolution.
Contact
Tivoli
Customer
Support
if
all
other
solutions
fail.
DYKAL0010E
Event
listener
Name
cannot
be
added
as
a
listener
because
it
is
not
a
Service
Component.
Only
Service
Components
can
register
to
receive
events.
Explanation:
An
internal
server
error
has
occurred.
Operator
Response:
Contact
Tivoli
Customer
Support
for
further
instructions.
Level
3
Support:
This
error
should
never
occur
in
the
field.
In
this
case,
a
component
has
attempted
to
register
as
a
listener
of
an
event,
but
does
not
implement
the
IServiceComponent
interface.
This
interface
must
be
implemented
if
the
component
will
be
receiving
events.
DYKAL0011E
An
event
listener
has
been
requested
to
be
removed,
but
does
not
exist
in
the
current
list
of
event
listeners.
Explanation:
An
internal
server
error
has
occurred.
Operator
Response:
Contact
Tivoli
Customer
Support
for
further
instructions.
DYKAL0012E
No
listeners
were
available
for
event
delivery.
Explanation:
An
internal
server
event
could
not
be
delivered
because
no
listeners
of
the
event
were
registered.
This
could
indicate
that
there
has
been
a
component
failure.
Operator
Response:
Verify
that
the
server
is
up
and
all
components
are
operational
by
using
the
following
CLI
command:
scmd
slm
getstatus.
Check
the
log
for
any
component
failure
errors
and
see
the
respective
operator
responses
for
further
instructions.
If
the
problem
persists,
contact
Tivoli
Customer
Support
for
further
instructions.
Level
3
Support:
This
error
will
typically
occur
if
a
component
has
not
started
successfully
and
added
itself
as
a
listener
of
the
particular
event.
Look
through
the
log
file
for
any
component
failures
and
use
the
scmd
slm
getstatus
command
to
ensure
that
all
components
are
running.
See
also:
The
Command
Reference
for
more
information
on
the
referenced
CLI
command.
DYKAL0013E
An
attempted
multicast
delivery
of
an
event
to
a
single
listener
instance
failed
with
error:Name.
Explanation:
An
internal
server
event
could
not
be
delivered
because
an
unexpected
error
occurred
during
delivery.
This
could
indicate
that
there
has
been
a
component
failure.
Operator
Response:
Verify
that
the
server
is
up
and
all
components
are
operational
by
using
the
following
CLI
command:
scmd
slm
getstatus.
Check
the
log
for
any
component
failure
errors
and
see
the
respective
operator
responses
for
further
instructions.
If
the
problem
persists,
contact
Tivoli
Customer
Support
for
further
instructions.
See
also:
The
Command
Reference
for
more
information
on
the
referenced
CLI
command.
DYKAL0014E
An
attempted
delivery
of
a
multicast
event
failed
for
all
listeners.
Explanation:
An
internal
server
event
could
not
be
delivered
to
any
listeners
because
an
unexpected
error
occurred
during
delivery.
This
message
is
typically
preceded
by
multiple
DYKAL0013E
errors
for
each
individual
failed
delivery
of
the
multicast
event
to
each
registered
listener.
Operator
Response:
Verify
that
the
server
is
up
and
operational
by
using
the
following
CLI
command:
scmd
slm
getstatus.
Check
the
error
log
for
other
DYKAL0013E
errors
for
more
information
on
the
failure.
If
the
problem
persists,
contact
Tivoli
Customer
Support
for
further
instructions.
See
also:
The
Command
Reference
for
more
information
DYKAL0008E
DYKAL0014E
2
IBM
Tivoli
Service
Level
Advisor:
Messages
-
on
the
referenced
CLI
command.
DYKAL0015E
An
attempted
delivery
of
a
multicast
event
failed
for
Number
of
Number
listeners.
Explanation:
An
internal
server
event
could
only
be
delivered
to
a
subset
of
the
event
listeners
registered.
This
message
is
typically
preceded
by
multiple
DYKAL0013E
errors
for
each
individual
failed
delivery
of
the
multicase
event.
Operator
Response:
Verify
that
the
server
is
up
and
operational
by
using
the
following
CLI
command:
scmd
slm
getstatus.
Check
the
error
log
for
other
DYKAL0013E
errors
for
more
information
on
the
failure.
If
the
problem
persists,
contact
Tivoli
Customer
Support
for
further
instructions.
See
also:
The
Command
Reference
for
more
information
on
the
referenced
CLI
command.
DYKAL0016E
An
attempted
delivery
of
a
unicast
event
to
listener
Name
failed
with
error:Error
text.
Explanation:
An
internal
server
event
could
not
be
delivered
to
the
named
listener.
If
an
error
message
with
ID
DYKAL0017E
is
not
received,
then
the
event
was
successfully
delivered
to
another
registered
listener
(which
meets
the
critera
of
unicast
events),
indicating
that
the
server
is
still
functioning
properly.
However,
the
referenced
error
should
be
investigated
to
verify
that
all
components
in
the
system
are
functioning
properly.
Operator
Response:
Verify
that
the
server
is
up
and
operational
by
using
the
following
CLI
command:
scmd
slm
getstatus.
Check
the
log
for
a
corresponding
DYKAL0017E
message.
If
both
messages
are
found,
then
the
server
is
not
functioning
properly.
Investigate
the
log
for
further
messages
relating
to
component
failure
and
see
the
respective
operator
responses
for
further
instructions.
If
a
corresponding
DYKAL0017E
is
not
found,
then
the
message
was
delivered
successfully
although
one
of
the
listeners
might
have
failed.
In
this
case
the
server
is
still
processing
properly,
but
the
logs
should
be
investigated
for
the
root
cause
of
this
message.
If
the
problem
persists,
contact
Tivoli
Customer
Support
for
further
instructions.
See
also:
The
Command
Reference
for
more
information
on
the
referenced
CLI
command.
DYKAL0017E
An
attempted
delivery
of
a
unicast
event
failed
for
all
listeners(Error
text).
Explanation:
An
internal
server
event
could
not
be
delivered
to
any
listeners
because
an
unexpected
error
occurred
during
delivery.
This
message
is
typically
preceded
by
multiple
DYKAL0016E
errors
for
each
failed
delivery
to
each
registered
listener.
Operator
Response:
Verify
that
the
server
is
up
and
operational
by
using
the
following
CLI
command:
scmd
slm
getstatus.
Check
the
error
log
for
other
DYKAL0016E
errors
for
more
information
on
the
failure.
If
the
problem
persists,
contact
Tivoli
Customer
Support
for
further
instructions.
See
also:
The
Command
Reference
for
more
information
on
the
referenced
CLI
command.
DYKAL0018W
An
event
is
being
delivered,
but
it
is
unknown
if
it
is
a
unicast
or
multicast
event
type.
It
will
be
treated
and
delivered
as
a
unicast
event.
Explanation:
An
event
was
passed
that
did
not
have
a
type.
It
will
be
treated
as
a
unicast
event,
but
might
have
been
intended
to
be
a
multicast
event.
Operator
Response:
Report
this
condition
to
Tivoli
Customer
Support.
DYKAL0019E
An
error
occurred
while
creating
the
FFDC
Tracer.
Explanation:
An
unexpected
error
occured
creating
the
FFDC
Tracer.
No
First
Failure
Data
capture
log
will
be
available.
Operator
Response:
See
the
accompanying
stack
trace
for
further
details.
DYKAL0020E
A
list
of
SLA
requests
could
not
be
delivered
because
the
remote
SLM
Server
Name
could
not
be
located
on
port
Port.
Verify
that
the
SLM
Server
is
running
and
that
network
communication
is
possible.
(SLAs:
Customer
Order
List)
Explanation:
The
remote
connection
between
the
SLM
Administration
Server
and
the
remote
SLM
Server
could
not
be
established
to
submit
a
list
of
SLA
requests.
Operator
Response:
Verify
that
the
remote
SLM
Server
is
running
by
executing
the
following
CLI
command
on
the
referenced
server:
scmd
slm
getstatus.
If
the
SLM
Server
is
running
and
is
operational,
verify
there
is
network
communication
from
the
machine
running
the
SLM
Administration
Server
to
the
remote
SLM
Server
by
using
the
ping
command.
Then,
see
the
Administrators
Guide
documentation
on
server
customization
and
verify
that
the
ports
used
for
remote
communication
on
both
the
SLM
Administration
Server
and
the
SLM
Server
match.
If
the
problem
persists,
contact
Tivoli
Customer
Support
for
further
instructions.
See
also:
The
Administrators
Guide
and
the
Command
Reference
for
more
information
on
setting
server
communication
ports.
DYKAL0015E
DYKAL0020E
Messages
for
IBM
Tivoli
Service
Level
Advisor
3
-
DYKAL0021E
A
list
of
SLA
requests
could
not
be
delivered
to
the
remote
SLM
Server
Name
on
port
Port
because
a
communication
error
occurred.
See
the
nested
exception
for
details
on
the
error.
(SLAs:
Customer
Order
List
)
Explanation:
The
list
of
SLA
requests
could
not
be
passed
from
the
SLM
Administration
Server
to
the
remote
SLM
Server.
Operator
Response:
Verify
that
the
remote
SLM
Server
is
running
by
executing
the
following
CLI
command
on
the
referenced
server:
scmd
slm
getstatus.
If
the
SLM
Server
is
running
and
is
operational,
verify
there
is
network
communication
from
the
machine
running
the
SLM
Administration
Server
to
the
remote
SLM
Server
by
using
the
ping
command.
Then,
see
the
Administrators
Guide
documentation
on
server
customization
and
verify
that
the
ports
used
for
remote
communication
on
both
the
SLM
Administration
Server
and
the
SLM
Server
match.
If
the
problem
persists,
contact
Tivoli
Customer
Support
for
further
instructions.
See
also:
The
Administrators
Guide
and
the
Command
Reference
for
more
information
on
setting
remote
communication
ports.
DYKAL0022E
A
multicast
event
was
passed
for
synchronous
unicast
delivery.
This
is
not
supported.
Explanation:
An
internal
server
error
has
occurred.
Operator
Response:
Contact
Tivoli
Customer
Support
for
further
instructions.
DYKAL0023E
Normal
event
delivery
is
not
supported
by
event
handler
EventHandlerType.
Explanation:
An
internal
server
error
has
occurred.
Operator
Response:
Contact
Tivoli
Customer
Support
for
further
instructions.
DYKAL0024E
Synchronous
event
delivery
is
not
supported
by
event
handler
EventHandlerType.
Explanation:
An
internal
server
error
has
occurred.
Operator
Response:
Contact
Tivoli
Customer
Support
for
further
instructions.
DYKAL0025E
A
trend
data
request
could
not
be
delivered
because
the
remote
SLM
Server
Name
could
not
be
located
on
port
Port.
Verify
that
the
remote
SLM
Server
is
running
and
that
network
communication
is
possible.
Explanation:
The
remote
connection
between
the
SLM
Report
Server
and
the
remote
SLM
Server
could
not
be
established
to
query
trend
data.
Operator
Response:
Verify
that
the
remote
SLM
Server
is
running
by
executing
the
following
CLI
command
on
the
referenced
server:
scmd
slm
getstatus.
If
the
SLM
Server
is
running
and
is
operational,
verify
there
is
network
communication
from
the
machine
running
the
SLM
Report
Server
to
the
remote
SLM
Server
by
using
the
ping
command.
Then,
see
the
Administrators
Guide
documentation
on
server
customization
and
verify
that
the
ports
used
for
remote
communication
on
both
the
SLM
Report
Server
and
the
SLM
Server
match.
If
the
problem
persists,
contact
Tivoli
Customer
Support
for
further
instructions.
See
also:
The
Administrators
Guide
and
the
Command
Reference
for
more
information
on
setting
server
communication
ports.
DYKAL0026E
A
trend
data
request
could
not
be
delivered
to
the
remote
SLM
Server
Name
on
port
Port
because
a
communication
error
occurred.
See
the
nested
exception
for
details
on
the
error.
Explanation:
The
trend
data
request
could
not
be
passed
from
the
SLM
Report
Server
to
the
remote
SLM
Server.
Operator
Response:
Verify
that
the
remote
SLM
Server
is
running
by
executing
the
following
CLI
command
on
the
referenced
server:
scmd
slm
getstatus.
If
the
SLM
Server
is
running
and
is
operational,
verify
there
is
network
communication
from
the
machine
running
the
SLM
Report
Server
to
the
remote
SLM
Server
by
using
the
ping
command.
Then,
see
the
Administrators
Guide
documentation
on
server
customization
and
verify
that
the
ports
used
for
remote
communication
on
both
the
SLM
Report
Server
and
the
SLM
Server
match.
If
the
problem
persists,
contact
Tivoli
Customer
Support
for
further
instructions.
See
also:
The
Administrators
Guide
and
the
Command
Reference
for
more
information
on
setting
remote
communication
ports.
DYKAL0040I
Using
JVM
version
Version
from
Vendor.
Explanation:
No
additional
information
is
available
for
this
message.
DYKAL0021E
DYKAL0040I
4
IBM
Tivoli
Service
Level
Advisor:
Messages
-
DYKAL0041I
Using
JVM
Full
Version
Explanation:
No
additional
information
is
available
for
this
message.
DYKAL0042I
Using
operating
system
OS
Name
version
Version.
Explanation:
No
additional
information
is
available
for
this
message.
DYKAL0050E
CLI
registration
or
deregistration
failed
because
the
CLI
component
cannot
be
found.
Explanation:
A
CLI
bundle
could
not
be
registered
or
deregistered
because
the
CLI
service
could
not
be
found.
This
might
indicate
an
internal
server
error.
Operator
Response:
Verify
that
the
server
is
up
and
operational
by
using
the
following
CLI
command:
scmd
slm
getstatus.
Check
the
log
for
any
component
failures
relating
to
the
CLI
service
and
follow
the
respective
operator
response.
If
the
problem
persists,
contact
Tivoli
Customer
Support
for
further
instructions.
Level
3
Support:
It
is
rare
that
the
CLI
registration
or
deregistration
functions
would
fail.
This
failure
would
typically
indicate
2
possible
errors:
1.
The
configuration
for
the
CLI
component
is
either
missing
or
corrupted.
Check
this
by
examining
the
configuration
information
in
the
SLM_BASEDIR/cfg/default
tree
under
node
com/tivoli/managed/spi/ADAPTER_NAME
/cm/CLI/1.
Ensure
that
the
clasname
in
the
.properties
file
is
correct.
2.
The
jar
file
containing
the
CLI
code
(spi.jar)
is
missing
or
cannot
be
read.
Ensure
that
spi.jar
is
in
the
SLM_BASEDIR/jars
directory,
that
it
is
readable,
and
that
it
is
added
to
the
classpath
at
launch
time
(look
for
message
DYKAL0100I
in
the
log).
See
also:
The
Command
Reference
for
more
information
on
the
referenced
CLI
commands.
DYKAL0051W
Multiple
instances
of
the
CLI
component
were
found.
Explanation:
An
internal
error
occurred
while
registering
or
deregistering
a
CLI
bundle.
Multiple
instances
of
the
CLI
service
were
found.
Operator
Response:
There
should
only
be
a
single
instance
of
the
CLI
service.
Report
this
behavior
to
Tivoli
Customer
Support.
Level
3
Support:
It
is
rare
that
the
multiple
occurrences
of
a
component
would
be
found.
If
this
happens
check
the
configuration
information
in
the
SLM_BASEDIR/cfg/default
tree
under
node
com/tivoli/managed/spi/ADAPTER_NAME/cm/CLI
and
ensure
that
there
is
only
a
single
node.
If
multiple
node
names
exist,
then
investigate
why
this
has
occurred.
DYKAL0052E
The
requested
data
source
could
not
be
located
because
the
data
source
component
cannot
be
found.
Explanation:
A
component
has
requested
a
data
source,
but
the
data
source
service
could
not
be
found
in
the
list
of
known
components.
Operator
Response:
Verify
that
the
server
is
up
and
operational
by
using
the
following
CLI
command:
scmd
slm
getstatus.
Check
the
log
for
any
component
failures
relating
to
the
data
source
service
and
follow
the
respective
operator
response.
If
the
problem
persists,
contact
Tivoli
Customer
Support
for
further
instructions.
See
also:
The
Command
Reference
for
more
information
on
the
referenced
CLI
commands.
DYKAL0053W
Multiple
instances
of
the
data
source
component
were
found.
Explanation:
An
internal
error
occurred
when
a
component
requested
a
data
source.
Multiple
instances
of
the
data
source
service
were
found.
Operator
Response:
There
should
only
be
a
single
instance
of
the
data