Upload
others
View
0
Download
0
Embed Size (px)
Citation preview
Note
Before
using
this
information
and
the
product
it
supports,
read
the
information
in
“Notices”
on
page
271.
October
2004
This
edition
applies
to
Version
3,
Release
1
of
IBM
Tivoli
Business
Systems
Manager
and
to
all
subsequent
releases
and
modifications
until
otherwise
indicated
in
new
editions.
©
Copyright
International
Business
Machines
Corporation
2000,
2004.
All
rights
reserved.
US
Government
Users
Restricted
Rights
–
Use,
duplication
or
disclosure
restricted
by
GSA
ADP
Schedule
Contract
with
IBM
Corp.
Contents
About
this
guide
.
.
.
.
.
.
.
.
.
.
. v
Publications
.
.
.
.
.
.
.
.
.
.
.
.
.
. v
IBM
Tivoli
Business
Systems
Manager
library
.
. v
Related
publications
.
.
.
.
.
.
.
.
.
. vi
Accessing
publications
online
.
.
.
.
.
.
. vi
Ordering
publications
.
.
.
.
.
.
.
.
.
. vii
Accessibility
.
.
.
.
.
.
.
.
.
.
.
.
.
. vii
Tivoli
technical
training
.
.
.
.
.
.
.
.
.
. vii
Support
information
.
.
.
.
.
.
.
.
.
.
. vii
Participating
in
newsgroups
.
.
.
.
.
.
.
. viii
Conventions
used
in
this
guide
.
.
.
.
.
.
. viii
Typeface
conventions
.
.
.
.
.
.
.
.
.
. viii
Operating
system-dependent
variables
and
paths
ix
Terminology
.
.
.
.
.
.
.
.
.
.
.
.
.
. ix
Chapter
1.
Source/390
Messages
-
GTM0001I
-
GTM8665E
.
.
.
.
.
.
.
. 1
Chapter
2.
Agent
Listener
Messages
GTMAL0001I
-
GTMAL0031E
.
.
.
.
. 81
Chapter
3.
Automated
Business
System
Messages
-
GTMAB1001E
-
GTMAB1048E
.
.
.
.
.
.
.
.
.
.
.
. 87
Chapter
4.
Intelligent
Monitoring
for
BMC
PATROL
Messages
-
GTMIP0001E
-
GTMIP0020E,
GTMIP0002W
-
GTMIP0010W
.
.
.
.
.
.
.
.
.
.
.
. 95
Chapter
5.
CICSPlex
SM
Data
Source
Messages
-
GTMCP0001E
-
GTMCP5024I
.
.
.
.
.
.
.
.
.
.
.
. 99
Chapter
6.
Command
Line
Interface
Messages
-
GTMCI0001I
-
GTMCI0145E,
GTMDC0010E
and
GTMDC0011E
.
.
.
.
.
.
.
.
.
.
. 111
Chapter
7.
Common
Listener
Messages
-
GTMCL5200I
-
GTMCL6000E
.
.
.
.
.
.
.
.
.
.
. 119
Chapter
8.
DB2
Feed
Messages
-
GTMDB1001I
-
GTMDB1006W
.
.
.
. 125
Chapter
9.
EDI
Messages
-
GTMED0001
-
GTMSA108
.
.
.
.
.
. 127
Chapter
10.
EIF
Sender
Service
Messages
GTMES0001I
-
GTMES7011I
. 135
Chapter
11.
Executive
Dashboard
Messages
-
GTMEV5200I,
GTMEV5201E
and
GTMXV0001E
-
GTMXV1002E
.
.
.
.
.
.
.
.
.
.
. 139
Chapter
12.
Health
Monitor
Service
Messages
GTMHM0001E
-
GTMHM0005I
.
.
.
.
.
.
.
.
.
.
. 141
Chapter
13.
Intelligent
Monitoring
for
HP
OpenView
Messages
GTMFLCI000E
-
GTMFLCI308E
.
.
.
. 143
Chapter
14.
IHS
Messages
-
IHS307E
-
IHS829I,
IHS0561I
.
.
.
.
.
.
.
.
.
. 149
Chapter
15.
IMS
Feed
Messages
-
GTMIM1001I
-
GTMIM1006W
.
.
.
.
. 187
Chapter
16.
Console
Messages
-
GTMJC0502I
-
GTMJC9191I
.
.
.
.
. 189
Chapter
17.
Intelligent
Monitoring
for
NetIQ
AppManager
Message
-
GTMIA0001E
.
.
.
.
.
.
.
.
.
.
.
. 223
Chapter
18.
Percentage-based
Threshold
Messages
-
GTMPT1000E
-
GTMPE1302E
.
.
.
.
.
.
.
.
.
.
. 225
Chapter
19.
Program
Exit
Messages
-
GTMPE1000I
-
GTMPE2008E
.
.
.
.
. 229
Chapter
20.
Resource
Level
Propagation
Messages
-
GTMPR1001E
-
GTMPR1009E
.
.
.
.
.
.
.
.
.
.
. 233
Chapter
21.
Resource
Object
Data
Manager
Messages
-
GTMRO0100E
-
GTMRO0112E
.
.
.
.
.
.
.
.
.
.
. 235
Chapter
22.
Unicenter
TNG
Messages
-
GTMIT0001E
-
GTMIT0005E
.
.
.
.
. 239
©
Copyright
IBM
Corp.
2000,
2004
iii
Chapter
23.
Utility
Messages
-
GTMTU1001E
-
GTMTU5336E
.
.
.
. 241
Chapter
24.
Web
Console
Messages
-
GTMWC1002I
-
GTMWC3088E
.
.
.
. 249
Chapter
25.
WebSphere
for
OS/390
Messages
-
GTMWS001E
-
GTMWS008E
.
.
.
.
.
.
.
.
.
.
.
. 257
Chapter
26.
ASG-Zeke
Messages
-
GTMZE0002I
-
GTMZE0014E
.
.
.
.
. 259
Appendix
A.
SQL
Messages
.
.
.
.
. 261
Appendix
B.
Summary
of
Messages
Used
for
Automation
.
.
.
.
.
.
.
. 263
New
Messages
.
.
.
.
.
.
.
.
.
.
.
.
. 263
Changed
Messages
.
.
.
.
.
.
.
.
.
.
. 264
Deleted
Messages
.
.
.
.
.
.
.
.
.
.
.
. 265
Support
information
.
.
.
.
.
.
.
. 267
Searching
knowledge
bases
.
.
.
.
.
.
.
.
. 267
Search
the
information
center
on
your
local
system
or
network
.
.
.
.
.
.
.
.
.
.
. 267
Search
the
Internet
.
.
.
.
.
.
.
.
.
. 267
Obtaining
fixes
.
.
.
.
.
.
.
.
.
.
.
.
. 267
Contacting
IBM
Software
Support
.
.
.
.
.
. 268
Determine
the
business
impact
of
your
problem
269
Describe
your
problem
and
gather
background
information
.
.
.
.
.
.
.
.
.
.
.
.
. 269
Submit
your
problem
to
IBM
Software
Support
269
Notices
.
.
.
.
.
.
.
.
.
.
.
.
.
. 271
Trademarks
.
.
.
.
.
.
.
.
.
.
.
.
.
. 272
iv
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
About
this
guide
IBM®
Tivoli®
Business
Systems
Manager
is
an
enterprise
management
product
that
monitors
the
data
processing
resources
that
are
critical
to
a
business
application.
It
enables
end-to-end
monitoring
of
systems,
subsystems,
applications,
and
other
resources
in
your
enterprise,
from
z/OS®
systems
to
distributed
systems.
Tivoli
Business
Systems
Manager
provides
your
operations
and
support
organizations,
application
owners,
and
management
with
a
view
of
the
system
components
as
they
relate
to
your
overall
business.
Publications
This
section
lists
publications
in
the
Tivoli
Business
Systems
Manager
library
and
related
documents.
It
also
describes
how
to
access
Tivoli
publications
online
and
how
to
order
Tivoli
publications.
IBM
Tivoli
Business
Systems
Manager
library
This
following
publications
are
in
the
IBM
Tivoli
Business
Systems
Manager
library:
v
IBM
Tivoli
Business
Systems
Manager
Planning
Guide,
SC32-9088,
provides
an
introduction
to
the
Tivoli
Business
Systems
Manager
product.
It
also
contains
planning
and
design
information
to
consider
when
implementing
a
Tivoli
Business
Systems
Manager
solution.
This
document
is
written
for
network
planners,
system
designers,
systems
administrators,
and
others
who
are
responsible
for
planning
and
implementing
the
product.
v
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide,
SC32-9089,
provides
the
installation
and
configuration
tasks
necessary
for
the
implementation
of
Tivoli
Business
Systems
Manager.
This
document
is
written
for
system
administrators
and
others
who
are
responsible
for
installing
and
configuring
Tivoli
Business
Systems
Manager.
v
IBM
Tivoli
Business
Systems
Manager
Introducing
the
Consoles,
SC32-9086,
provides
an
introduction
to
the
Tivoli
Business
Systems
Manager
console,
Web
console,
executive
dashboard,
and
the
reporting
system.
This
document
is
written
for
operators
and
administrators.
v
IBM
Tivoli
Business
Systems
Manager
Administrator’s
Guide,
SC32-9085,
describes
administrative
tasks
for
Tivoli
Business
Systems
Manager.
This
document
is
written
for
system
administrators
and
others
who
perform
administrative
tasks
for
Tivoli
Business
Systems
Manager.
v
IBM
Tivoli
Business
Systems
Manager
Problem
and
Change
Management
Integration
Guide,
SC32-9130,
describes
how
to
write
request
processors
to
enable
the
problem,
change,
and
automatic
ticket
integration
function
provided
with
Tivoli
Business
Systems
Manager
to
work
with
problem
and
change
management
applications.
This
document
is
written
for
system
programmers.
v
IBM
Tivoli
Business
Systems
Manager
Command
Reference,
SC32-1243,
describes
the
commands
available
for
use
with
Tivoli
Business
Systems
Manager.
This
document
is
written
for
system
administrators
and
others
who
run
commands
and
scripts
for
Tivoli
Business
Systems
Manager.
©
Copyright
IBM
Corp.
2000,
2004
v
v
IBM
Tivoli
Business
Systems
Manager
Message
Reference,
SC32-9087,
describes
the
messages
for
Tivoli
Business
Systems
Manager.
This
document
is
written
for
system
programmers,
network
planners,
operations
managers,
system
designers,
system
administrators,
network
operators,
and
others
who
need
message
information
for
Tivoli
Business
Systems
Manager.
v
IBM
Tivoli
Business
Systems
Manager
Troubleshooting
Guide,
SC32-9084,
describes
troubleshooting
tasks
to
diagnose
problems
with
Tivoli
Business
Systems
Manager.
This
document
is
written
for
system
administrators
and
others
who
perform
diagnostic
tasks
for
Tivoli
Business
Systems
Manager.
v
IBM
Tivoli
Business
Systems
Manager
Release
Notes,
GI11-4029,
describes
what
is
new
for
this
release
of
the
Tivoli
Business
Systems
Manager
product.
v
IBM
Tivoli
Business
Systems
Manager
Guide
for
Warehouse
Pack,
Version
3.1.0.0,
using
Tivoli
Data
Warehouse,
Version
1.2,
SC32-9114,
describes
how
to
use
the
warehouse
enablement
pack
to
extract
data
from
the
Tivoli
Business
Systems
Manager
database
and
load
it
into
the
Tivoli
Data
Warehouse
database,
where
it
can
be
accessed
using
reporting
and
data
analysis
tools.
This
document
is
written
for
administrators
and
others
who
plan
for
and
install
the
warehouse
pack,
use
and
maintain
the
warehouse
pack
and
its
reports,
or
create
new
reports.
An
index
is
provided
for
searching
the
Tivoli
Business
Systems
Manager
library.
If
you
have
Adobe
Acrobat
on
your
system,
you
can
use
the
Search
command
to
locate
specific
text
in
the
library.
For
more
information
about
using
the
index
to
search
the
library,
see
the
online
help
for
Acrobat.
Related
publications
The
Tivoli
Software
Glossary
includes
definitions
for
many
of
the
technical
terms
related
to
Tivoli
software.
The
Tivoli
Software
Glossary
is
available
at
the
following
Tivoli
software
library
Web
site:
http://www.ibm.com/software/tivoli/library/
Access
the
glossary
by
clicking
the
Glossary
link
on
the
left
pane
of
the
Tivoli
software
library
window.
Accessing
publications
online
The
documentation
CD
contains
the
publications
that
are
in
the
product
library.
The
format
of
the
publications
is
and
HTML.
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
Tivoli
Business
Systems
Manager
link
to
access
the
product
library
at
the
Tivoli
software
information
center.
vi
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
Note:
If
you
documents
on
other
than
letter-sized
paper,
set
the
option
in
the
File
→
window
that
allows
Adobe
Reader
to
letter-sized
pages
on
your
local
paper.
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
all
features
of
the
graphical
user
interface.
For
information
about
installing
the
Tivoli
Business
Systems
Manager
product
using
the
built-in
screen
reader,
see
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide.
For
information
about
the
shortcut
keys
that
can
be
used
with
the
Tivoli
Business
Systems
Manager
console,
see
the
Accessibility
appendix
in
IBM
Tivoli
Business
Systems
Manager
Introducing
the
Consoles.
Tivoli
technical
training
For
Tivoli
technical
training
information,
refer
to
the
following
IBM
Tivoli
Education
Web
site:
http://www.ibm.com/software/tivoli/education
Support
information
If
you
have
a
problem
with
your
IBM
software,
you
want
to
resolve
it
quickly.
IBM
provides
the
following
ways
for
you
to
obtain
the
support
you
need:
v
Searching
knowledge
bases:
You
can
search
across
a
large
collection
of
known
problems
and
workarounds,
Technotes,
and
other
information.
v
Obtaining
fixes:
You
can
locate
the
latest
fixes
that
are
already
available
for
your
product.
v
Contacting
IBM
Software
Support:
If
you
still
cannot
solve
your
problem,
and
you
need
to
work
with
someone
from
IBM,
you
can
use
a
variety
of
ways
to
contact
IBM
Software
Support.
For
more
information
about
these
three
ways
of
resolving
problems,
see
“Support
information”
on
page
267.
About
this
guide
vii
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.
To
access
a
newsgroup,
use
the
instructions
appropriate
for
your
browser.
IBM
Tivoli
Business
Systems
Manager:
news://news.software.ibm.com/ibm.software.tivoli.business-systems-manager
IBM
Tivoli
Enterprise
Console®:
news://news.software.ibm.com/ibm.software.tivoli.enterprise-console
IBM
Tivoli
Service
Level
Advisor:
news://news.software.ibm.com/ibm.software.tivoli.service-level-advisor
IBM
Tivoli
Switch
Analyzer:
news://news.software.ibm.com/ibm.software.tivoli.switch-analyzer
IBM
Tivoli
NetView®
for
UNIX®
and
IBM
Tivoli
NetView
for
Windows®:
news://news.software.ibm.com/ibm.software.tivoli.netview-unix-windows
IBM
Tivoli
NetView
for
z/OS:
news://news.software.ibm.com/ibm.software.netview
Conventions
used
in
this
guide
This
guide
uses
several
conventions
for
special
terms
and
actions
and
for
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),
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)
viii
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
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.
Terminology
For
a
list
of
terms
and
definitions
for
Tivoli
and
other
IBM
products,
refer
to
the
IBM
terminology
Web
site:
http://www.ibm.com/ibm/terminology/
For
brevity
and
readability,
the
term
Tivoli
NetView
for
z/OS
refers
to
both
the
Tivoli
NetView
for
z/OS
product
and
the
Tivoli
NetView
for
OS/390®
product.
About
this
guide
ix
Chapter
1.
Source/390
Messages
-
GTM0001I
-
GTM8665E
The
following
messages
are
issued
by
the
components
that
make
up
the
source/390
services
on
z/OS
mainframe
systems.
These
include
the
source/390
object
pump,
source/390
object
server,
and
source/390
data
space.
Some
of
the
following
messages
are
issued
from
other
address
spaces
that
use
the
source/390
components.
GTM0001I
TBSM
INITIALIZATION
STARTED
date
time
Explanation:
The
application
level
code
within
the
source/390
object
pump
started
initialization.
Message
Variables:
date
-
The
current
date
time
-
The
current
time
System
Action:
Processing
continues.
GTM0002I
SYSTEM
WAS
IPL’D
ON
date1
date
AT
time
Explanation:
The
source/390
object
pump
displays
the
date
and
time
the
system
was
last
IPL’ed.
Message
Variables:
date1
-
The
date
in
the
form
mm/dd/yyyy
date
-
The
date
in
the
form
mmddyy
time
-
The
time
in
the
form
hh:mm:ss
System
Action:
Processing
continues.
GTM0003I
TBSM
IS
RUNNING
ON
SYSTEM
smfid
Explanation:
The
source/390
object
pump
displays
the
SMFID
of
the
system
on
which
it
is
running.
Message
Variables:
smfid
-
The
SMFID
of
the
MVS™
image
on
which
the
source/390
object
pump
is
running.
System
Action:
Processing
continues.
GTM0008E
PLEASE
SEE
SYSLOG.
REPLY
OK
TO
THIS
MESSAGE
TBSM
INITIALIZATION
FAILED
Explanation:
An
error
occurred
during
source/390
object
pump
initialization.
A
previous
message
describes
the
cause
of
the
failure.
System
Action:
The
source/390
object
pump
stops.
User
Response:
Reply
OK
to
the
outstanding
WTOR.
Contact
the
administrator.
Administrator
Response:
Check
the
messages
in
the
system
log
to
resolve
the
cause
of
the
error.
Restart
the
source/390
object
pump.
GTM0009E
TBSM
INITIALIZATION
IS
TERMINATED.
TERMINATION
RETURN
CODE
=
return_code
Explanation:
An
error
occurred
during
source/390
object
pump
initialization.
A
previous
message
describes
the
cause
of
the
failure.
Message
Variables:
return_code
-
The
return
code
from
the
function
that
failed
System
Action:
The
source/390
object
pump
stops.
Administrator
Response:
Reply
OK
to
the
outstanding
WTOR.
Contact
the
administrator.
Administrator
Response:
Check
the
messages
in
the
system
log
to
resolve
the
cause
of
the
error.
Restart
the
source/390
object
pump.
GTM00010E
error_text
Explanation:
An
error
occurred
and
the
text
of
the
message
describes
the
error.
The
source/390
object
pump
is
unable
to
determine
the
source/390
object
server
state
or
unable
to
query
the
parameter
variable
that
is
indicated.
Message
Variables:
error_text
-
The
text
is
one
of
the
following
messages:
v
UNABLE
TO
DETERMINE
SERVER
STATE
v
UNABLE
TO
QUERY
PARAMETER
parm_variable
System
Action:
The
source/390
object
pump
stops.
Administrator
Response:
Check
the
messages
in
the
system
log
to
resolve
the
cause
of
the
error.
Restart
the
source/390
object
pump.
If
the
error
continues,
contact
IBM
Software
Support.
GTM0100I
INVALID
VALIDATION
TYPE:
value
Explanation:
The
validation
value
of
the
PARM_VAL.n
was
incorrectly
coded.
Message
Variables:
value
-
The
validation
parameter
from
the
PARM_VAL.n
startup
parameter
©
Copyright
IBM
Corp.
2000,
2004
1
System
Action:
The
source/390
object
pump
stops.
Administrator
Response:
Check
the
messages
in
the
system
log
to
resolve
the
cause
of
the
error.
Restart
the
source/390
object
pump.
GTM0101I
FOR
PARAMETER
:
parameter
Explanation:
This
is
a
continuation
of
the
GTM0100I
message.
Message
Variables:
parameter
-
The
parameter
name
that
is
in
error
GTM0104I
INVALID
OBJECT
TYPE
ID
type
PASSED
TO
pgm
AT
INITIALIZATION
Explanation:
An
object
type
that
was
not
valid
was
received
from
Windows
in
the
global
shared
variable
registration
data.
The
valid
object
types
are
as
follows:
ENT
Defines
the
global
variable
for
the
enterprise
COMP
Defines
the
global
variable
for
the
complex
LPAR
Defines
the
global
variable
for
the
LPAR
MACH
Defines
the
global
variable
for
the
machine
OS
Defines
the
global
variable
for
the
operating
system
Message
Variables:
type
-
The
object
ID
that
was
not
valid
pgm
-
The
program
name
of
the
global
shared
variable
registration
data
System
Action:
Processing
continues.
Administrator
Response:
Check
the
messages
in
the
system
log
to
resolve
the
cause
of
the
error.
Restart
the
source/390
object
pump.
GTM0108E
SEVERE
ERROR
RESETTING
SHARED
VARIABLE
POOL,
RC
=
return_code
Explanation:
The
deletion
of
all
initialization-shared
variables
did
not
successfully
complete.
Additional
information
is
in
the
following
message.
Message
Variables:
return_code
-
The
return
code
from
the
shared
variable
delete
operation
System
Action:
Processing
continues.
Administrator
Response:
Check
the
messages
in
the
system
log
to
resolve
the
cause
of
the
error.
Restart
the
source/390
object
pump.
GTM0109E
SHARED
VARIABLE
POOL
MAYBE
UNUSABLE
Explanation:
This
is
a
continuation
of
the
GTM0108E
message.
GTM0110E
ERROR
WRITING
SHARED
VARIABLE
variable_name
IN
pgm
Explanation:
An
error
occurred
writing
the
shared
variable
program
to
the
global
pool.
Refer
to
the
GTM0111E
message.
Message
Variables:
variable_name
-
The
name
of
variable
being
written
pgm
-
The
name
of
program
writing
the
variable
System
Action:
The
source/390
object
pump
stops.
Administrator
Response:
Check
the
messages
in
the
system
log
and
the
AOPLOG
log
to
see
why
the
function
failed.
Resolve
the
cause
of
the
error
and
restart
the
source/390
object
pump.
Contact
IBM
Software
Support.
GTM0111E
RC
=
return_code
INITIALIZATION
PROCESSING
HAS
BEEN
TERMINATED
Explanation:
The
return
code
from
the
error
described
by
the
GTM0110E
message
is
displayed.
If
the
return
code
is
16,
an
error
message
is
displayed
in
the
AOPOUT
log
file.
Message
Variables:
return_code
-
The
return
code
from
the
error
described
by
the
GTM0110E
message
GTM0112E
ERROR
READING
SHARED
VARIABLE
variable_name
IN
pgm
Explanation:
An
error
occurred
reading
the
shared
variable
from
the
global
pool.
Message
Variables:
variable_name
-
The
name
of
variable
being
read
pgm-
The
name
of
program
reading
the
variable
System
Action:
The
source/390
object
pump
stops.
Administrator
Response:
Check
the
messages
in
the
system
log
and
the
AOPLOG
log
to
see
why
the
function
failed.
Resolve
the
cause
of
the
error
and
restart
the
source/390
object
pump.
Contact
IBM
Software
Support.
GTM0113E
RC
=
return_code
INITIALIZATION
PROCESSING
HAS
BEEN
TERMINATED
Explanation:
The
return
code
from
the
error
described
by
the
GTM0112E
message
is
displayed.
If
the
return
code
is
16,
an
error
message
is
displayed
in
the
AOPOUT
log
file.
Message
Variables:
return_code
-
The
return
code
of
the
error
described
by
the
GTM0112E
message
2
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
GTM0116E
ERROR
PROCESSING
SYSTEM
VARIABLE
variable_name
IN
pgm
Explanation:
An
error
occurred
setting
the
@ACLOGSW
global
variable
while
processing
a
SET
LOG
ON
or
SET
LOG
OFF
command.
Refer
to
the
GTM0117E
message.
Message
Variables:
variable_name
-
The
name
of
the
variable
being
read
pgm
-
The
name
of
the
program
reading
the
variable
System
Action:
Processing
of
the
command
stops.
Administrator
Response:
Review
the
source/390
object
pump
job
log
and
AOPLOG
output
to
see
if
there
are
any
related
messages
that
might
indicate
why
the
function
failed.
Contact
IBM
Software
Support.
GTM0117E
PROCESSING
HAS
BEEN
TERMINATED
Explanation:
Indicates
that
processing
ended
for
the
SET
LOG
ON
or
SET
LOG
OFF
command.
This
message
follows
the
GTM0116E
message.
System
Action:
Processing
of
the
command
stops.
Administrator
Response:
Check
the
messages
in
the
system
log
and
the
AOPLOG
log
to
see
why
the
function
failed.
Resolve
the
cause
of
the
error
and
restart
the
source/390
object
pump.
Contact
IBM
Software
Support.
GTM0120E
VALIDITY
CHECK
FAILED
FOR
PARM:
object_type
IN
pgm
Explanation:
During
initialization,
the
SMFID
value
and
the
OS
name
in
the
parameter
file
did
not
agree.
Additional
information
can
be
found
in
the
GTM0121E,
GTM0122E,
GTM0123E,
or
GTM0124E
messages.
Message
Variables:
object_type
-
The
object
type,
for
example,
an
operating
system
pgm
-
The
REXX
initialization
program
System
Action:
Processing
of
the
command
might
stop.
The
GTM0123E
or
GTM0124I
message
indicates
the
action
of
the
source/390
object
pump.
Administrator
Response:
Correct
the
member
in
the
parameter
file
and
restart
the
source/390
object
pump.
GTM0121E
DATASET
NAME
IS
dataset_name
Explanation:
This
is
a
continuation
of
the
GTM0120E
message.
Message
Variables:
dataset_name
-
The
name
of
the
parameter
library
GTM0122E
PARM
FILE
VALUE
IS:
smfid_parm,
SYSTEM
VALUE
IS:
smfid
Explanation:
This
is
a
continuation
of
the
GTM0120E
message.
Message
Variables:
smfid_parm
-
The
value
of
the
SMFID
in
the
parameter
file
smfid
-
The
value
of
the
SMFID
from
the
system
variable
GTM0123E
PROCESSING
HAS
TERMINATED
Explanation:
This
is
a
continuation
of
the
GTM0120E
message.
GTM0124I
PROCESSING
IS
CONTINUING
Explanation:
This
is
a
continuation
of
the
GTM0120E
message.
GTM0130E
VALIDITY
CHECK
FAILED
FOR
PARM:
parameter
IN
pgm
Explanation:
Indicates
that
the
data
for
the
source/390
object
pump
startup
parameter
is
not
in
the
correct
format.
Refer
to
the
GTM0131E
message.
Message
Variables:
parameter
-
The
name
of
parameter
pgm
-
The
name
of
program
reading
the
parameter
System
Action:
The
source/390
object
pump
stops.
Administrator
Response:
Check
the
messages
in
the
system
log
to
resolve
the
cause
of
the
error.
Restart
the
source/390
object
pump.
If
the
error
continues,
contact
IBM
Software
Support.
GTM0131E
PARM
VALUE
IS:
data,
ERROR
IS:
error_text
Explanation:
This
is
a
continuation
of
the
GTM0130E
message
and
displays
the
parameter
data
and
reason
for
the
error.
Message
Variables:
data
-
The
data
that
is
in
error
error_text
-
The
description
of
the
error
GTM0200E
INVALID
RETURN
CODE
FROM
GTMRX014
-
FUNCTION
=
OBJSRV,
RETURN
CODE
=
return_code,
CALLER
=
caller_pgm
Explanation:
The
GTMRX014
REXX
EXEC
returned
a
return
code
that
was
not
valid
during
source/390
object
pump
initialization
or
shut
down.
The
GTMRX014
program
is
started
during
log
on
processing
of
the
3270
OMEGAMON®
sessions.
Message
Variables:
return_code
-
The
return
code
from
the
GTMRX014
program
Chapter
1.
Source/390
Messages
-
GTM0001I
-
GTM8665E
3
caller_pgm
-
The
REXX
EXEC
which
called
the
GTMRX014
program
Administrator
Response:
Check
the
AOPLOG
and
AOPOUT
log
files
for
any
messages
that
might
indicate
why
the
logon
or
logoff
processing
programs
returned
an
error.
Resolve
the
cause
of
the
error
and
try
establishing
the
session
again.
If
the
error
continues,
contact
IBM
Software
Support.
GTM0210E
AN
ERROR
error_type
OCCURRED
IN
PROGRAM
pgm
ON
LINE:
error_line
Explanation:
A
run
time
error
occurred
in
the
GTMRX014
REXX
EXEC.
This
error
occurred
during
the
logon
or
logoff
processing
of
a
3270
OMEGAMON
session.
Message
Variables:
error_type
-
The
type
of
error
pgm
-
The
GTMRX014
program
error_line
-
The
line
number
of
the
REXX
EXEC
that
caused
the
error
System
Action:
Processing
continues.
The
Tivoli
OMEGAMON
session
manager
is
not
initialized.
Administrator
Response:
Check
the
AOPLOG
and
AOPOUT
log
files
for
any
messages
that
might
indicate
why
the
GTMRX014
program
returned
an
error.
Resolve
the
cause
of
the
error
and
try
to
establish
the
session
again.
If
the
error
continues,
contact
IBM
Software
Support.
GTM0211E
THE
SOURCE
LINE
IS:
error_text
Explanation:
The
source
line
associated
with
the
error
described
by
the
GTM0210E
message
is
displayed.
Message
Variables:
error_text
-
The
source
line
in
the
GTMRX014
REXX
EXEC
where
the
error
occurred
GTM0220I
TBSM
LOG
ON
PROCESSING
INITIALIZATION
STARTED
Explanation:
The
source/390
object
pump
is
starting
the
processing
of
OMEGAMON
3270
sessions.
System
Action:
Processing
continues.
GTM0222E
INVALID
LOGON
TYPE
SPECIFIED:
Explanation:
The
source/390
object
pump
received
a
non-valid
session
type
when
attempting
to
establish
a
3270
session
with
Tivoli
OMEGAMON.
System
Action:
Processing
continues.
The
session
is
not
connected.
Administrator
Response:
Refer
to
the
GTM0223E
message,
which
describes
the
parameters
that
are
not
valid.
Determine
why
the
non-valid
session
type
was
sent
for
the
logon
request.
Resolve
the
cause
of
the
error
and
try
to
establish
the
session
again.
If
the
error
continues,
contact
IBM
Software
Support.
GTM0223E
TYPE
=
session_type,
NAME
=
session_name,
APPLID
=
applid
Explanation:
This
is
a
continuation
of
the
GTM0222E
message.
The
non-valid
session
parameters
received
by
the
source/390
object
pump
from
Windows
are
displayed.
Message
Variables:
session_type
-
The
type
of
session
received
session_name
-
The
name
of
the
session
applid
-
The
VTAM®
application
ID
of
the
target
application
GTM0225E
BAD
RETURN
CODE
FROM
LOGON
REQUEST,
RC
=
return_code
Explanation:
A
logon
request
to
a
3270
application
failed.
Message
Variables:
return_code
-
The
return
code
from
the
logon
request
System
Action:
Processing
continues.
The
source/390
object
pump
did
not
log
on
to
Tivoli
OMEGAMON.
Administrator
Response:
Refer
to
the
GTM0226E
message
for
further
information
about
the
logon
request.
Determine
why
the
logon
request
might
have
failed.
For
example,
the
Tivoli
OMEGAMON
monitor
might
not
be
active.
Resolve
the
cause
of
the
error
and
try
to
establish
the
session
again.
GTM0226E
TYPE
=
session_type,
NAME
=
session_name,
APPLID
=
applid
Explanation:
This
is
a
continuation
of
the
GTM0225E
message.
The
session
type,
the
session
name,
and
the
VTAM
application
ID
that
failed
to
log
on
is
displayed.
Message
Variables:
session_type
-
The
type
of
session
received
session_name
-
The
name
of
the
session
applid
-
The
VTAM
application
ID
of
the
target
application
GTM0228E
ERROR
action
SHARED
VARIABLE
variable_name
IN
pgm
RC
=
return_code
Explanation:
An
error
occurred
retrieving
or
setting
a
global
shared
variable.
This
message
is
issued
during
the
logon
or
logoff
processing
of
a
3270
OMEGAMON
session.
Message
Variables:
action
-
The
action,
which
is
either
SETTING
or
GETTING
variable_name
-
The
variable
name
pgm
-
The
name
of
the
program
issuing
the
message
4
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
return_code
-
The
return
code
from
the
variable
service
System
Action:
Processing
continues.
The
source/390
object
pump
did
not
log
on
to
Tivoli
OMEGAMON.
Administrator
Response:
Check
the
AOPLOG
and
AOPOUT
log
files
for
any
messages
that
might
indicate
this
failure.
Resolve
the
cause
of
the
error
and
restart
the
source/390
object
pump.
If
the
error
continues,
contact
IBM
Software
Support.
GTM0236I
TBSM
SESSION
LOGOFF
PROCESSING
action
Explanation:
Logoff
processing
started
or
ended
for
a
3270
OMEGAMON
session.
Message
Variables:
action
-
The
action,
which
is
either
STARTED
or
ENDED
System
Action:
Processing
continues.
GTM0238I
BAD
RETURN
CODE
FROM
LOGOFF
REQUEST,
RC
=
return_code
Explanation:
Logoff
processing
for
a
3270
OMEGAMON
session
failed.
Message
Variables:
return_code
-
The
return
code
from
the
logoff
request
System
Action:
Processing
continues.
Administrator
Response:
Refer
to
the
GTM0239I
message
for
further
information
about
the
session
that
received
the
error.
Check
the
AOPLOG
and
AOPOUT
log
files
for
any
messages
that
might
indicate
why
the
logoff
processing
failed.
Resolve
the
cause
of
the
error
and
try
logging
on
and
off
the
same
session
again.
If
the
error
continues,
contact
IBM
Software
Support.
GTM0239I
SESSION
ID
=
session_name,
TYPE
=
session_type
-
SESSION
might
NOT
HAVE
BEEN
ACTIVE
Explanation:
Additional
information
is
displayed
about
the
logoff
failure
listed
in
the
GTM0238I
message.
Message
Variables:
session_name
-
The
session
ID
name
session_type
-
The
type
of
session
GTM0240E
INVALID
FUNCTION
function
PASSED
TO
pgm
Explanation:
The
GTMRX014
REXX
EXEC
was
passed
a
function
that
was
not
valid.
Message
Variables:
function
-
The
function
that
was
passed
to
the
GTMRX014
REXX
EXEC
pgm
-
The
GTMRX014
REXX
EXEC
System
Action:
Processing
continues.
The
source/390
object
pump
session
manager
is
not
initialized.
Administrator
Response:
Collect
the
messages
from
the
system
log
and
the
AOPLOG
log.
Contact
IBM
Software
Support.
GTM0241E
VALID
FUNCTIONS
ARE
START,
STOP,
QUERY,
LOG
ON,
LOG
OFF
Explanation:
This
is
a
continuation
of
the
GTM0240E
message
and
lists
the
valid
functions
that
can
be
passed
to
the
GTMRX014
REXX
EXEC.
GTM0242I
SESSNAME
TYPE
APPLID
INTERVAL
STATUS
Explanation:
This
is
part
of
a
multiline
message
from
the
QUERY
LOGONS
command.
System
Action:
Processing
continues.
GTM0243I
session_name,
session_type,
applid,
interval,
session_status
Explanation:
This
is
part
of
a
multiline
message
from
the
QUERY
LOGONS
command.
Message
Variables:
session_name
-
The
session
name
session_type
-
The
session
type
applid
-
The
VTAM
application
ID
interval
-
The
polling
interval
in
the
format
hh:mm:ss
session_status
-
The
session
status
GTM0244I
session_count
SESSIONS
LISTED
Explanation:
This
is
part
of
a
multiline
message
from
the
QUERY
LOGONS
command.
Message
Variables:
session_count
-
The
number
of
sessions
listed
by
the
command
GTM0246E
CONNECTION
TO
OMEGAMON
HAS
FAILED
Explanation:
A
3270
session
to
a
Tivoli
OMEGAMON
application
failed.
System
Action:
Processing
continues.
The
session
is
not
connected.
Administrator
Response:
Refer
to
the
GTM0247E
message
for
details
of
the
session
that
failed.
The
Tivoli
OMEGAMON
monitor
might
have
shut
down.
Check
the
messages
in
the
system
log
and
the
AOPLOG
log
to
determine
why
the
session
might
have
failed.
Resolve
the
cause
of
the
error
and
try
to
establish
the
connection
again.
Chapter
1.
Source/390
Messages
-
GTM0001I
-
GTM8665E
5
GTM0247E
SESSION
NAME
=
session_name,
SESSION
TYPE
=
session_type
Explanation:
The
information
about
the
failed
3270
OMEGAMON
session
is
displayed.
Message
Variables:
session_name
-
The
session
name
session_type
-
The
type
of
session
System
Action:
Processing
continues.
The
session
is
not
connected.
Administrator
Response:
The
Tivoli
OMEGAMON
monitor
might
have
shut
down.
Check
the
messages
in
the
system
log
and
the
AOPLOG
log
to
determine
why
the
session
might
have
failed.
Resolve
the
cause
of
the
error
and
try
to
establish
the
connection
again.
GTM0300I
INVALID
RETURN
CODE
FROM
@AEVNTMG
-
RETURN
CODE
=
return_code
Explanation:
The
GTMRX013
REXX
EXEC
issued
a
nonzero
return
code
during
source/390
object
pump
startup
or
shut
down.
Message
Variables:
return_code
-
The
return
code
received
from
the
GTMRX013
REXX
EXEC
System
Action:
The
source/390
object
pump
is
not
ready
to
process
events.
Administrator
Response:
Review
the
console,
AOPLOG,
and
AOPOUT
logs
for
any
messages
that
might
indicate
why
the
function
failed.
If
the
error
occurred
during
startup,
you
might
need
to
restart
the
source/390
object
pump.
If
the
error
occurred
during
shutdown,
you
might
need
to
issue
the
STOP
command
again
to
stop
the
source/390
object
pump.
If
the
error
continues,
contact
IBM
Software
Support.
GTM0400I
INVALID
RETURN
CODE
FROM
@ACCCMDS
-
RETURN
CODE
=
return_code
Explanation:
During
source/390
object
pump
initialization
or
shutdown,
the
command
processor
GTMRX003
REXX
EXEC
issued
a
nonzero
return
code.
Message
Variables:
return_code
-
The
return
code
from
the
GTMRX003
REXX
EXEC
System
Action:
Processing
continues.
The
command
facility
is
not
started.
Administrator
Response:
Check
the
messages
in
the
AOPLOG
and
AOPOUT
log
files.
Resolve
the
cause
of
the
error
and
restart
the
source/390
object
pump.
If
the
error
continues,
contact
IBM
Software
Support.
GTM0910E
AN
ERROR
error_type
OCCURRED
IN
PROGRAM
pgm
ON
LINE:
error_line
Explanation:
A
run
time
error
occurred
in
the
GTMRX004
REXX
EXEC.
The
error
occurred
during
source/390
object
pump
initialization.
Message
Variables:
error_type
-
The
type
of
error
pgm
-
The
GTMRX004
REXX
EXEC
error_line
-
The
line
number
of
the
REXX
EXEC
that
caused
the
error
System
Action:
Processing
continues.
The
source/390
object
pump
is
not
available.
Administrator
Response:
Check
the
AOPLOG
and
AOPOUT
log
files
for
any
messages
that
might
indicate
why
the
GTMRX004
program
returned
an
error.
Resolve
the
cause
of
the
error
and
restart
the
source/390
object
pump.
If
the
error
continues,
contact
IBM
Software
Support.
GTM0911E
THE
SOURCE
LINE
IS:
error_text
Explanation:
The
source
line
associated
with
the
error
described
by
the
GTM0910E
message
is
displayed.
Message
Variables:
error_text
-
The
source
of
the
line
in
error
GTM0990I
TBSM
INITIALIZATION
COMPLETED
Explanation:
The
source/390
object
pump
initialization
completed.
The
source/390
object
pump
is
ready
to
process
registration
data
from
the
Windows
operating
system.
System
Action:
Processing
continues.
GTM1001I
TBSM
EVENT
MANAGER
INITIALIZATION
STARTED
Explanation:
The
event
manager
initialization
started.
System
Action:
Processing
continues.
GTM1010E
AN
ERROR
error_type
OCCURRED
IN
PROGRAM
pgm
ON
LINE:
error_line
Explanation:
An
error
occurred
in
the
event
manager
GTMRX013
REXX
EXEC.
Message
Variables:
error_type
-
The
type
of
error
pgm
-
The
GTMRX013
REXX
EXEC
error_line
-
The
line
number
of
the
REXX
EXEC
that
caused
the
error
System
Action:
Processing
continues.
The
source/390
object
pump
is
not
available
to
process
events.
Administrator
Response:
Check
the
AOPLOG
and
AOPOUT
log
files
for
any
messages
that
might
indicate
why
the
GTMRX013
program
failed.
Resolve
the
cause
6
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
of
the
error
and
restart
the
source/390
object
pump.
If
the
error
continues,
contact
IBM
Software
Support.
GTM1011E
THE
SOURCE
LINE
IS:
error_text
Explanation:
The
source
line
associated
with
the
error
described
by
the
GTM1010E
message
text
is
displayed.
Message
Variables:
error_text
-
The
source
of
the
line
in
the
GTMRX013
REXX
EXEC
where
the
error
occurred
GTM1030E
ERROR
GETTING
SHARED
VARIABLE
variable_name
IN
pgm
RC
=
return_code
Explanation:
An
error
occurred
while
retrieving
the
global
variable
name
in
the
program
listed.
Message
Variables:
variable_name
-
The
name
of
the
variable
being
retrieved
pgm
-
The
name
of
the
program
issuing
the
message
return_code
-
The
return
code
from
the
GBLVGET
function
System
Action:
Processing
continues.
The
source/390
object
pump
is
not
available
to
process
events.
Administrator
Response:
Check
the
AOPLOG
and
AOPOUT
log
files
for
any
messages
that
might
be
related
to
this
error.
Issue
the
source/390
object
pump
SHOW
VARS
command
to
display
the
variable
name
that
had
the
error
to
verify
that
it
exists.
Resolve
the
cause
of
the
error
and
restart
the
source/390
object
pump.
If
the
error
continues,
contact
IBM
Software
Support.
GTM1050E
INVALID
FUNCTION
function
PASSED
TO
GTMRX013
Explanation:
The
GTMRX013
REXX
EXEC
was
called
with
a
function
that
was
not
valid.
Message
Variables:
function
-
The
name
of
the
function
System
Action:
Processing
continues.
The
source/390
object
pump
is
not
available
to
process
events.
Administrator
Response:
Check
the
AOPLOG
and
AOPOUT
log
files
for
any
messages
that
might
be
related
to
this
error.
If
the
error
continues,
contact
IBM
Software
Support.
GTM1051E
VALID
FUNCTIONS
ARE
START,
STOP,
QUERY
Explanation:
This
is
a
continuation
of
the
GTM1050E
message
and
lists
the
valid
functions
that
can
be
passed
to
the
GTMRX013
REXX
EXEC.
GTM1060E
INVALID
SUBFUNCTION
PASSED
TO
GTMRX013
Explanation:
A
sub
function
that
was
not
valid
was
passed
to
the
GTMRX013
REXX
EXEC.
Refer
to
the
GTM1061E
message
text,
which
lists
the
function
and
sub
function
routine
names.
System
Action:
Processing
continues.
The
source/390
object
pump
is
not
available
to
process
events.
Administrator
Response:
Check
the
AOPLOG
and
AOPOUT
log
files
for
any
messages
that
might
be
related
to
this
error.
If
the
error
continues,
contact
IBM
Software
Support.
GTM1061E
FUNCTION
=
function
SUBFUNCTION
=
subfunction
Explanation:
This
is
a
continuation
of
the
GTM1060E
message
and
lists
the
function
and
sub
function
passed
to
the
GTMRX013
REXX
EXEC.
Message
Variables:
function
-
The
name
of
the
function
subfunction
-
The
name
of
the
sub
function
GTM1591I
TBSM
EVENT
MANAGER
TERMINATING
Explanation:
The
source/390
object
pump
is
shutting
down
in
response
to
a
STOP
command.
System
Action:
Processing
continues.
GTM1610E
AN
ERROR
error_type
OCCURRED
IN
PROGRAM
pgm
ON
LINE:error_line
Explanation:
An
error
occurred
in
the
named
REXX
EXEC.
Message
Variables:
error_type
-
The
error
type
pgm
-
The
name
of
the
program
issuing
the
message
error_line-
The
line
number
of
the
REXX
EXEC
that
caused
the
error
System
Action:
Processing
continues.
Administrator
Response:
Check
the
AOPLOG
and
AOPOUT
log
files
for
any
messages
that
might
indicate
why
the
error
occurred.
Resolve
the
cause
of
the
error
and
restart
the
source/390
object
pump.
If
the
error
continues,
contact
IBM
Software
Support.
GTM1611E
THE
SOURCE
LINE
IS:
error_text
Explanation:
The
source
line
associated
with
the
error
described
by
the
GTM1610E
message
is
displayed.
Message
Variables:
error_text
-
The
source
of
the
line
in
error
Chapter
1.
Source/390
Messages
-
GTM0001I
-
GTM8665E
7
GTM1620I
OBJECT
PUMP
TO
OBJECT
SERVER
HANDSHAKE
STARTED
Explanation:
The
source/390
object
pump
is
detecting
the
source/390
object
server
address
space.
System
Action:
Processing
continues.
GTM1630I
OBJECT
PUMP
TO
OBJECT
SERVER
HANDSHAKE
ENDED
Explanation:
The
source/390
object
pump
is
ending
its
monitoring
of
the
source/390
object
server
address
space.
System
Action:
Processing
continues.
GTM1640E
INVALID
FUNCTION
function
PASSED
TO
GTMRX019
Explanation:
A
function
was
passed
to
the
GTMRX019
REXX
EXEC
that
was
not
valid.
Message
Variables:
function
-
The
name
of
the
function
that
was
passed
System
Action:
Processing
continues.
Administrator
Response:
Check
the
AOPLOG
and
AOPOUT
log
files
for
any
messages
that
might
indicate
why
the
error
occurred.
If
the
error
continues,
contact
IBM
Software
Support.
GTM1641E
VALID
FUNCTIONS
ARE
START,
STOP,
QUERY,
FAILURE,
TAKEOVER,
INFORM
Explanation:
This
is
a
continuation
of
the
GTM1640E
message
and
lists
the
valid
functions
that
can
be
passed
to
the
GTMRX019
REXX
EXEC.
GTM1655I
RESTART
OF
THE
OBJECT
SERVER
jobname
-
JOBNAME
type
WAS
SUCCESSFUL
Explanation:
The
source/390
object
server
was
stopped
and
successfully
restarted.
Message
Variables:
jobname
-
The
type
of
source/390
object
server
type
-
The
job
name
of
the
source/390
object
server
GTM1660E
FAILURE
PROCESSING
CALLED
WITH
INVALID
MSGID
msgid
MESSAGE
IGNORED
AND
PROCESSING
CONTINUES
Explanation:
The
source/390
object
pump
detected
that
the
source/390
object
server
is
ending
or
failed,
but
is
unable
to
determine
the
actual
condition.
Message
Variables:
msgid
-
The
ID
of
the
message
trapped
by
the
source/390
object
pump
System
Action:
Processing
continues.
Administrator
Response:
Check
the
messages
in
the
system
log
that
might
be
related
to
this
error.
Determine
why
the
source/390
object
server
is
ending.
If
required,
restart
the
source/390
object
server
and
pump.
GTM1680E
ERROR
READING
SHARED
VARIABLE
variable_name
IN
pgm
Explanation:
An
error
occurred
reading
the
shared
variable
specified
in
the
GTMRX019
program.
Message
Variables:
variable_name
-
The
name
of
the
variable
being
read
pgm
-
The
GTMRX019
program
System
Action:
Processing
continues.
Administrator
Response:
Check
the
messages
in
the
AOPLOG
and
AOPOUT
log
files
that
might
be
related
to
this
error.
Refer
to
the
GTM1681E
message
to
identify
the
return
code
related
to
this
error.
Resolve
the
cause
of
the
error
and
restart
the
source/390
object
pump.
If
the
error
continues,
contact
IBM
Software
Support.
GTM1681E
RC
return_code
PROCESSING
TERMINATED
Explanation:
The
return
code
from
the
read
failure
indicated
by
the
GTM1680E
message
is
displayed.
Message
Variables:
return_code
-
The
return
code
from
the
variable
get
routine
System
Action:
The
source/390
is
not
able
to
process
events.
Administrator
Response:
Check
the
messages
in
the
AOPLOG
and
AOPOUT
log
files
that
might
be
related
to
this
error.
Resolve
the
cause
of
the
error
and
restart
the
source/390
object
pump.
If
the
error
continues,
contact
IBM
Software
Support.
GTM1682E
ERROR
READING
GLOBAL
VARIABLE
variable_name
IN
pgm
Explanation:
An
error
occurred
reading
the
global
variable
from
the
variable
pool
specified
in
the
GTMRX019
REXX
EXEC.
Message
Variables:
variable_name
-
The
name
of
the
variable
being
read
pgm
-
The
GTMRX019
REXX
EXEC
System
Action:
The
source/390
is
not
able
to
process
events.
Administrator
Response:
Check
the
messages
in
the
system
log
and
the
AOPLOG
log
that
might
be
related
to
this
error.
Resolve
the
cause
of
the
error
and
restart
the
source/390
object
pump.
If
the
error
continues,
8
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
contact
IBM
Software
Support.
GTM1683E
RC
return_code
ATTEMPTED
RESTART
OF
jobname
TERMINATED
Explanation:
While
processing
a
shutdown
of
the
source/390
object
server,
the
source/390
object
pump
received
the
error
specified
in
the
GTM1682E
message
text.
Message
Variables:
return_code
-
The
return
code
from
the
error
listed
in
the
GTM1682E
message
jobname
-
The
job
name
of
the
source/390
object
server
address
space
System
Action:
The
source/390
shuts
down.
Administrator
Response:
Check
the
messages
in
the
AOPLOG
log
that
might
be
related
to
this
error.
Resolve
the
cause
of
the
error
and
restart
the
source/390
object
pump.
If
the
error
continues,
contact
IBM
Software
Support.
GTM1687E
OBJECT
SERVER
OUTSTANDING
VTAM
REPLY
IS
NOT
AVAILABLE
Explanation:
The
source/390
object
pump
detected
that
the
source/390
object
server
lost
the
connection
to
Tivoli
Business
Systems
Manager.
The
source/390
object
pump
is
attempting
to
restart
the
connection
but
the
WTOR
reply
number
could
not
be
found
for
the
source/390
object
server.
System
Action:
Processing
continues.
Administrator
Response:
The
outstanding
VTAM
reply
might
have
been
removed
from
the
console,
but
might
still
be
outstanding.
Issue
the
MVS
D
R,L
operator
command
to
view
any
outstanding
requests.
Reply
to
the
command
appropriately.
If
the
WTOR
cannot
be
found,
then
restart
the
source/390
object
server.
GTM1688E
PLEASE
STOP
AND
RESTART
jobname
Explanation:
This
is
a
continuation
message
for
the
GTM1687E
message.
Message
Variables:
jobname
-
The
source/390
object
server
job
name
GTM1690E
OBJECT
SERVER
ADDRESS
SPACE
HAS
ABENDED
-
JOBNAME
=
jobname
Explanation:
The
source/390
object
pump
detected
that
there
was
an
abend
of
the
source/390
object
server
address
space.
Message
Variables:
jobname
-
The
source/390
object
server
job
name
System
Action:
Processing
continues.
The
source/390
object
server
shuts
down.
Administrator
Response:
Check
the
messages
in
the
system
log
to
determine
why
the
abend
of
the
source/390
object
server
address
space
occurred.
Correct
the
problem
and
restart
the
source/390
object
server.
If
the
problem
continues,
contact
IBM
Software
Support.
GTM1691E
RC
=
return_code
REASON
CODE
=
reason_code
Explanation:
The
return
and
reason
codes
associated
with
the
GTM1690E
message
are
displayed.
Message
Variables:
return_code
-
The
return
code
reason_code
-
The
reason
code
System
Action:
Processing
continues.
The
source/390
object
server
shuts
down.
Administrator
Response:
Check
the
messages
in
the
system
log
to
determine
why
the
abend
of
the
source/390
object
server
address
space
occurred.
Correct
the
problem
and
restart
the
source/390
object
server.
If
the
problem
continues,
contact
IBM
Software
Support.
GTM1692E
RESTART
FOR
OBJECT
SERVER
ADDRESS
SPACE
jobname
NOT
ATTEMPTED
Explanation:
The
source/390
object
pump
detected
that
there
was
an
abend
of
the
source/390
object
server
address
space.
The
object
pump
will
not
attempt
to
restart
the
source/390
object
server.
The
abend
code
is
listed
in
the
GTM1693E
message
text.
Message
Variables:
jobname
-
The
source/390
object
server
address
space
name
System
Action:
The
source/390
object
server
shuts
down.
Administrator
Response:
Check
the
messages
in
the
system
log
to
determine
why
the
abend
of
the
source/390
object
server
address
space
occurred.
Correct
the
problem
and
restart
the
source/390
object
server.
If
the
problem
continues,
contact
IBM
Software
Support
GTM1693E
SYSTEM
COMPLETION
CODE
IS
=
abend_code
Explanation:
The
abend
code
associated
with
the
GTM1692E
message
is
displayed.
Message
Variables:
abend_code
-
The
abend
code
System
Action:
The
source/390
object
server
shuts
down.
Administrator
Response:
Check
the
messages
in
the
system
log
to
determine
why
the
source/390
object
server
address
space
received
an
X22
or
0C4
abend.
Correct
the
problem
and
restart
the
source/390
object
Chapter
1.
Source/390
Messages
-
GTM0001I
-
GTM8665E
9
server.
The
abends
are
as
follows:
v
X22
Abend
-
Resolve
the
issue
as
appropriately
described
in
IBM
System
Messages
and
Codes.
v
0C4
Abend
-
If
the
problem
continues,
contact
IBM
Software
Support.
GTM1695I
THE
OBJECT
SERVER
ADDRESS
SPACE
jobname
HAS
TERMINATED
Explanation:
The
source/390
object
pump
detected
that
the
source/390
object
server
ended.
Message
Variables:
jobname
-
The
source/390
object
server
job
name
GTM1696E
THE
OBJECT
SERVER
ADDRESS
SPACE
jobname
HAS
LOST
ITS
VTAM
CONVERSATION
Explanation:
The
source/390
object
pump
detected
that
the
source/390
object
server
lost
its
VTAM
connection
to
Tivoli
Business
Systems
Manager.
Message
Variables:
jobname
-
The
source/390
object
server
job
name
System
Action:
Processing
continues.
The
source/390
object
server
is
waiting
to
establish
the
connection
again.
Administrator
Response:
Check
the
messages
in
the
system
log
to
determine
why
the
source/390
object
server
lost
communication.
Correct
the
problem
and
restart
the
source/390
object
server.
If
the
problem
continues,
contact
IBM
Software
Support.
GTM1697E
A
RESTART
WILL
BE
ATTEMPTED
IN
number
MINUTES
Explanation:
The
source/390
object
pump
detected
that
the
source/390
object
server
lost
its
VTAM
connection
to
Tivoli
Business
Systems
Manager.
The
source/390
object
pump
attempts
to
establish
the
connection
again
on
the
next
time
interval
specified
in
minutes.
Message
Variables:
number
-
The
number
of
minutes
until
the
source/390
object
pump
attempts
to
establish
the
connection
again
System
Action:
Processing
continues.
Administrator
Response:
Check
the
messages
in
the
system
log
to
determine
why
the
source/390
object
server
lost
communication.
Correct
the
problem
and
restart
the
source/390
object
server.
If
the
problem
continues,
contact
IBM
Software
Support.
GTM1698I
A
STOP
COMMAND
HAS
BEEN
ISSUED
FOR
THE
OBJECT
SERVER
ADDRESS
SPACE
jobname
Explanation:
The
source/390
object
server
was
requested
to
shut
down.
Message
Variables:
jobname
-
The
job
name
of
the
source/390
object
server
System
Action:
The
source/390
object
server
shuts
down.
GTM1699I
A
CANCEL
COMMAND
HAS
BEEN
ISSUED
FOR
THE
OBJECT
SERVER
ADDRESS
SPACE
jobname
Explanation:
A
cancel
command
for
the
source/390
object
server
was
issued
from
the
console.
Message
Variables:
jobname
-
The
job
name
of
the
source/390
object
server
System
Action:
The
source/390
object
server
shuts
down.
Administrator
Response:
Determine
why
the
source/390
object
server
was
cancelled.
GTM1700I
OBJECT
PUMP
VALIDATION
MODULE
HAS
BEGUN
PROCESSING
Explanation:
The
source/390
object
pump
received
control
statements
from
Tivoli
Business
Systems
Manager.
System
Action:
Processing
continues.
GTM1705I
OBJECT
PUMP
VALIDATION
MODULE
HAS
ENDED
PROCESSING
Explanation:
The
source/390
object
pump
completed
the
processing
of
all
received
data.
System
Action:
Processing
continues.
GTM1710E
ERROR
request
SHARED
VARIABLE
variable_name
IN
pgm
RC
=
return_code
Explanation:
There
was
an
error
using
a
shared
variable
associated
with
a
console
trap.
Message
Variables:
request
-
The
variable
request
function
variable_name
-
The
shared
variable
name
pgm
-
The
name
of
REXX
EXEC
program
issuing
the
message
return_code
-
The
return
code
System
Action:
Processing
continues.
The
trap
does
not
complete.
Administrator
Response:
Check
the
messages
in
the
system
log
and
the
AOPLOG
log
to
see
why
the
10
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
function
failed.
The
processing
of
the
event
is
stopped.
Resolve
the
cause
of
the
error
and
restart
the
source/390
object
pump.
If
the
error
continues,
contact
IBM
Software
Support.
GTM1711E
INITIALIZATION
PROCESSING
HAS
BEEN
TERMINATED
Explanation:
This
is
a
continuation
of
the
GTM1710E
message.
GTM1715I
THE
END
OF
BLOCK
INDICATOR
(~)
WAS
MISSING
-
Explanation:
A
single
record
was
read
by
the
source/390
object
pump
and
did
not
contain
an
end-of-record
indicator
(~)
character.
System
Action:
Processing
continues.
The
event
message
is
not
processed.
Administrator
Response:
Contact
IBM
Software
Support.
GTM1716I
PROCESSING
CONTINUES
Explanation:
This
is
a
continuation
of
the
GTM1715I
message.
GTM1717I
text
Explanation:
This
is
a
continuation
of
the
GTM1715I
message.
Message
Variables:
text
-
The
entire
record
received
from
Tivoli
Business
Systems
Manager
GTM1720E
ERROR
OCCURRED
CALLING
THE
OBJECT
SERVER.
RETURN
CODE
=
return_code
Explanation:
An
error
occurred
while
attempting
to
write
a
record
to
the
source/390
object
server
queue
by
the
source/390
object
pump.
The
source/390
object
server
did
not
receive
the
information
described
in
the
GTM1721E
message
text.
Message
Variables:
return_code
-
The
return
code
of
the
error
that
occurred
during
an
attempted
write
to
the
source/390
object
server
queue
System
Action:
Processing
continues.
The
event
message
was
not
shipped
to
Tivoli
Business
Systems
Manager.
Administrator
Response:
Check
the
messages
in
the
system
log
and
the
AOPLOG
log
to
determine
the
cause
of
the
error.
The
record
is
not
written
to
the
source/390
object
server.
Resolve
the
cause
of
the
error
and
restart
the
source/390
object
server
and
pump.
If
the
problem
continues,
contact
IBM
Software
Support.
GTM1721E
DATA
ITEM
IS:
text
Explanation:
This
is
a
continuation
of
the
GTM1720E
message.
Message
Variables:
text
-
The
record
that
was
not
written
to
the
source/390
object
server
GTM1722E
PROCESSING
FOR
THIS
DATA
ELEMENT
HAS
BEEN
TERMINATED
Explanation:
This
is
a
continuation
of
the
GTM1720E
message.
GTM1760E
MISSING
NATIVE
KEY
FOR
resource_type
SHARED
VARIABLE
Explanation:
A
high-level
resource
type
(ENT,
COMP,
MACH,
LPAR,
or
OS)
is
not
properly
defined
to
the
source/390
object
pump.
The
resource
is
missing
its
database
key.
Message
Variables:
resource_type
-
The
high
level
resource
type
System
Action:
Processing
continues.
The
source/390
object
pump
is
not
properly
started
to
collect
events.
Administrator
Response:
The
environment
is
not
set
up
correctly.
Determine
why
the
native
key
for
the
object
is
missing.
No
other
data
is
processed
until
this
situation
is
corrected.
If
the
problem
continues,
contact
IBM
Software
Support.
GTM1761E
PROCESSING
IS
BEING
TERMINATED
FOR
DATA
JUST
RECEIVED
Explanation:
This
is
a
continuation
of
the
GTM1760E
message.
GTM1770I
ALL
REQUIRED
SHARED
VARIABLES
HAVE
BEEN
REGISTERED,
PROCESSING
CONTINUES
Explanation:
The
shared
variables
required
for
the
start
up
procedure
have
been
successfully
created.
Additional
registration
data
can
now
be
processed.
System
Action:
Processing
continues.
GTM1780I
OBJECT
PUMP/OBJECT
SERVER
IS
REQUESTING
OBJECTS
Explanation:
The
source/390
object
pump,
by
way
of
the
source/390
object
server,
is
requesting
that
Tivoli
Business
Systems
Manager
forward
registration
information.
System
Action:
Processing
continues.
Chapter
1.
Source/390
Messages
-
GTM0001I
-
GTM8665E
11
GTM1785I
ALL
REQUIRED
SHARED
VARIABLES
HAVE
NOT
BEEN
RECEIVED
IN
THE
REQUESTED
INTERVAL
Explanation:
The
REGISTRATION_WAIT_TIME
parameter
was
specified
to
the
source/390
object
pump
and
shared
variables
required
for
the
registration
process
were
not
received
within
the
time
specified.
System
Action:
The
source/390
object
pump
continues
to
wait
for
the
shared
variables.
Administrator
Response:
Determine
why
the
source/390
object
pump
did
not
receive
the
shared
variables.
Check
that
the
source/390
object
server
is
communicating
correctly
and
that
all
the
required
services
are
active
on
the
Tivoli
Business
Systems
Manager
servers.
Consider
restarting
the
object
pump.
GTM1786E
REGISTRATION
RETRY
LIMIT
EXCEEDED.
Explanation:
The
REGISTRATION_TIMEOUT=RETRY
parameter
was
specified
and
the
object
pump
retried
the
number
of
times
indicated
by
the
REGISTRATION_RETRY_LIMIT
parameter
without
receiving
the
shared
variables
from
Tivoli
Business
Systems
Manager.
System
Action:
The
source/390
object
pump
issues
the
GTM1787E
message.
Administrator
Response:
Determine
why
the
source/390
object
pump
did
not
receive
the
shared
variables.
Check
that
the
source/390
object
server
is
communicating
correctly
and
that
all
the
required
services
are
active
on
the
Tivoli
Business
Systems
Manager
servers.
Consider
restarting
the
object
pump.
GTM1787E
REPLY
’SHUT’
TO
SHUTDOWN;
’WAIT’
TO
CONTINUE
WAITING
Explanation:
See
the
explanation
for
the
GTM1786E
message
to
determine
whether
you
want
to
stop
the
source/390
object
pump.
System
Action:
The
source/390
object
pump
waits
for
a
response
on
the
system
console
or
for
the
shared
variables
to
be
sent
from
Tivoli
Business
Systems
Manager.
Administrator
Response:
Respond
to
the
message
on
the
system
console
with
either
SHUT
to
stop
the
object
pump,
or
WAIT
to
continue
to
wait
for
the
shared
variables.
GTM1788I
REPLY
WAS
NOT
’SHUT’
OR
’WAIT’
Explanation:
The
GTM1787E
message
was
issued,
but
the
response
to
it
was
not
one
of
the
allowable
values.
System
Action:
The
source/390
object
pump
issues
the
GTM1787E
message
again.
Administrator
Response:
Respond
to
the
message
on
the
system
console
with
either
SHUT
to
stop
the
object
pump,
or
WAIT
to
continue
to
wait
for
the
shared
variables.
GTM1790E
RECEIVED
OBJECT
DATA
BEFORE
SHARED
VARIABLES
HAVE
BEEN
BUILT
Explanation:
Registration
data
was
received
before
the
high-level
resource
types
(ENT,
COMP,
MACH,
LPAR,
or
OS)
were
properly
defined
to
the
source/390
object
pump.
System
Action:
Processing
continues.
Administrator
Response:
Contact
IBM
Software
Support.
GTM1800E
INVALID
RETURN
CODE
FROM
pgm_called
-
FUNCTION
=
function,
RETURN
CODE
=
return_code,
CALLER
=
pgm
Explanation:
There
was
an
unsuccessful
call
to
a
REXX
EXEC
specified
in
the
program
that
was
called.
Message
Variables:
pgm_called
-
The
REXX
EXEC
program
that
was
called
function
-
The
passed
variable;
typically
START
or
STOP
return_code
-
The
return
code
from
the
call
pgm
-
The
REXX
EXEC
issuing
the
call
System
Action:
Processing
continues.
Administrator
Response:
Check
the
messages
in
the
AOPLOG
and
AOPOUT
log
files
that
might
be
related
to
this
error.
Resolve
the
cause
of
the
error
and
restart
the
source/390
object
pump.
If
the
error
continues,
contact
IBM
Software
Support.
GTM1805E
FIRST
RECORD
IN
QUEUE
IS
NULL
Explanation:
On
a
READ
request
of
the
source/390
object
server
queue
by
the
source/390
object
pump,
a
null
record
was
discovered.
System
Action:
Processing
continues.
Administrator
Response:
An
event
message
being
shipped
is
not
formatted
correctly.
A
generated
event
record
containing
only
a
control
statement
termination
character
(~)
can
cause
this
error.
Contact
IBM
Software
Support.
GTM1810E
RECORD
IS
NULL
-
LAST
VALID
RECORD
WAS...
Explanation:
On
a
READ
request
(other
than
the
first
initial
READ
request)
from
the
source/390
object
server
queue
by
the
source/390
object
pump,
a
null
record
was
discovered
on
the
server
queue.
12
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
See
the
GTM1811E
message
text
for
known
information
about
the
previous
record
in
the
stack.
System
Action:
Processing
continues.
Administrator
Response:
An
event
message
being
shipped
is
not
formatted
correctly.
Possibly
a
generated
event
record
containing
only
a
control
statement
termination
character
(~)
can
cause
this
error.
Contact
IBM
Software
Support.
GTM1811E
previous_event_msg
Explanation:
This
is
a
continuation
of
the
GTM1810E
message.
Message
Variables:
previous_event_msg
-
The
event
message
preceding
the
null
record
GTM1815E
UNRECOGNIZABLE
DATA
FROM
OBJECT
SERVER
-
BAD
FORMAT
OR
ACTION
CODE
Explanation:
This
is
a
continuation
of
the
GTM1810E
message.
The
format
or
action
codes
received
on
a
registration
message
are
not
supported.
The
registration
message
is
not
processed
by
the
source/390
object
pump.
The
registration
message
is
displayed
in
the
GTM1816E
message
text.
GTM1816E
error_text
Explanation:
This
is
a
continuation
of
the
GTM1810E
message.
Message
Variables:
error_text
-
The
registration
message
that
was
not
valid
GTM1820E
UNEXPECTED
DATA
TYPE
VALUE
OR
CONTINUATION
(\)
WAS
FOUND
IN
RECORD
Explanation:
An
unsupported
data
type
associated
with
a
data
value
was
found
in
the
data
record
received
from
Tivoli
Business
Systems
Manager.
Each
value
in
the
record
is
defined
with
a
specific
data
type
indicating
the
type
of
data
that
immediately
follows.
The
registration
message
containing
the
non-valid
data
type
is
not
processed
by
the
source/390
object
pump.
System
Action:
Processing
continues.
Administrator
Response:
Contact
IBM
Software
Support.
GTM1821E
error_type
error_text
Explanation:
This
is
a
continuation
of
the
GTM1820E
message.
Message
Variables:
error_type
-
The
data
type
and
value
that
was
not
valid
error_text
-
The
entire
record
containing
the
data
type
that
was
not
valid
GTM1825I
VALID
BUT
UNEXPECTED
FORMAT/ACTION
TYPE
WAS
FOUND
IN
RECORD
Explanation:
The
source/390
object
pump
received
a
non-valid
format
type
or
a
non-valid
data
type
value
for
the
type
of
object
to
be
registered.
System
Action:
The
registration
message
is
not
processed,
but
processing
continues.
The
registration
message
is
displayed
in
the
GTM1826I
message
text.
Administrator
Response:
Contact
IBM
Software
Support.
GTM1826I
error_type
error_text
Explanation:
This
is
a
continuation
of
the
GTM1825I
message.
Message
Variables:
error_type
-
The
format
or
action
type
that
was
not
valid
error_text
-
The
entire
record
containing
the
code
that
was
not
valid
GTM1835E
INVALID
OR
UNEXPECTED
name
=
error_value
Explanation:
A
value
associated
with
a
data
type
was
not
valid.
Message
Variables:
name
-
The
name
of
the
data
type
error_value
-
The
value
that
was
not
valid
System
Action:
Processing
continues.
Administrator
Response:
Contact
IBM
Software
Support.
GTM1836E
error_text
Explanation:
This
is
a
continuation
of
the
GTM1835E
message.
Message
Variables:
error_text
-
The
registration
message
containing
the
data
type
that
was
not
valid
GTM1840E
MISSING
DATA.
SEE
NULL
FIELD
BELOW
FOR
MISSING
VALUE:
Explanation:
A
registration
message
was
received
without
a
value
in
a
mandatory
field.
System
Action:
The
registration
message
is
not
processed
by
the
source/390
object
pump.
Processing
continues.
Administrator
Response:
Contact
IBM
Software
Support.
Chapter
1.
Source/390
Messages
-
GTM0001I
-
GTM8665E
13
GTM1841E
OBJECT
ID
=
object_id
NATIVE
KEY
=
value
Explanation:
This
is
a
continuation
of
the
GTM1840E
message.
Message
Variables:
object_id
-
A
valid
object
ID
or
a
problem
null
value
value
-
A
valid
10
character
native
key
for
the
object
or
a
problem
null
value
GTM1842E
OBJECT
NAME
=
object_name
Explanation:
This
is
a
continuation
of
the
GTM1840E
message.
Message
Variables:
object_name
-
A
valid
object
name
or
a
problem
null
value
GTM1843E
error_text
Explanation:
This
is
a
continuation
of
the
GTM1840E
message.
Message
Variables:
error_text
-
The
registration
message
containing
the
missing
data
GTM1845E
UNACCEPTABLE
RECORDS
EXCEEDED
TOLERANCE
Explanation:
The
number
of
records
in
error
received
by
the
source/390
object
pump
that
exceeded
the
tolerance
count
or
error
tolerance
percentage.
System
Action:
Processing
continues.
Administrator
Response:
Determine
why
there
are
an
excessive
amount
of
unacceptable
records
attempting
to
get
registered
by
the
source/390
object
pump.
Either
the
data
was
improperly
generated
from
the
database
or
there
was
data
not
aligned
during
the
communications
phase.
If
the
problem
continues,
contact
IBM
Software
Support.
GTM1846E
UNACCEPTABLE
TOLERANCE
COUNT
=
number
Explanation:
This
is
a
continuation
of
the
GTM1845E
message.
Message
Variables:
number
-
The
threshold
count
for
errors
tolerated
by
the
source/390
object
pump
GTM1847E
UNACCEPTABLE
TOLERANCE
PERCENT
=
percent
Explanation:
This
is
a
continuation
of
the
GTM1845E
message.
Message
Variables:
percent
-
The
threshold
percentage
of
unacceptable
records
versus
acceptable
records
tolerated
by
the
source/390
object
pump
GTM1848E
GOOD
REC
COUNT
=
number;
ERROR
REC
COUNT
=
error_number
Explanation:
This
is
a
continuation
of
the
GTM1845E
message.
Message
Variables:
number
-
The
number
of
acceptable
records
processed
by
the
source/390
object
pump
error_number
-
The
number
of
error
records
processed
by
the
source/390
object
pump
GTM1849E
PROCESSING
IS
BEING
TERMINATED
Explanation:
This
is
a
continuation
of
the
GTM1845E
message.
GTM1850E
WILDCARD
(*)
IS
NOT
ACCEPTABLE
FOR
MONITOR/RE-DISCOVER
OPERATION
Explanation:
A
wildcard
character
was
used
in
the
object
name
value
for
an
object
monitor
request.
A
wildcard
cannot
be
used
for
this
type
of
operation.
System
Action:
Processing
continues.
Administrator
Response:
Contact
IBM
Software
Support.
GTM1851E
OR
CHILD
AUTO-DISCOVER
(TRAN,
FILE,
LU,
DB
CONN)
Explanation:
This
is
a
continuation
of
the
GTM1850E
message.
Also,
child
object
names
cannot
contain
a
wildcard
for
the
specified
object
types
TRAN,
FILE,
LU,
DB,
and
CONN.
GTM1852E
OBJECT
ID
=
object_id
NATIVE
KEY
=
value
Explanation:
This
is
a
continuation
of
the
GTM1850E
message.
Message
Variables:
object_id
-
A
valid
object
ID,
such
as
CICS®,
STC,
or
IMS™
value
-
A
valid
10
character
native
key
for
the
object
ID
GTM1853E
OBJECT
NAME
=
name
Explanation:
This
is
a
continuation
of
the
GTM1850E
message.
Message
Variables:
name
-
The
name
of
the
resource
GTM1854E
error_text
Explanation:
This
is
a
continuation
of
the
GTM1850E
message.
Message
Variables:
error_text
-
The
registration
14
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
message
containing
the
object
name
with
the
wildcard
GTM1855E
THE
TRAP
NAME
EXCEEDED
24
CHARACTERS
Explanation:
A
console
trap
name
was
generated
and
exceeded
24
characters
in
length.
The
source/390
object
pump
did
not
generate
the
trap.
System
Action:
Processing
continues.
Administrator
Response:
The
trap
name
that
failed
is
included
in
the
GTM1856E
message
text.
Determine
if
it
was
generated
based
on
a
source/390
object
pump
keyword
or
sent
from
Tivoli
Business
Systems
Manager.
If
the
trap
generated
was
derived
from
one
of
the
source/390
object
pump
keywords,
such
as
SA390,
then
correct
this
error.
If
this
error
is
generated
as
a
result
of
a
registration
message,
then
contact
IBM
Software
Support.
GTM1856E
TRAP
NAME
=
trap_name
Explanation:
This
is
a
continuation
of
the
GTM1855E
message.
Message
Variables:
trap_name
-
The
composed
trap
name
that
was
not
valid
GTM1857E
trap_text
Explanation:
This
is
a
continuation
of
the
GTM1855E
message.
Message
Variables:
trap_text
-
The
trap
text
associated
with
the
trap
name
GTM1860E
UNACCEPTABLE
ACTION
TYPE
RECEIVED:
action_type
Explanation:
The
source/390
object
pump
for
processing
received
an
action
type
that
was
not
valid.
The
action
types
indicate
operations
such
as
monitoring
and
autodiscovery.
Message
Variables:
action_type
-
The
action
type
that
was
not
valid
System
Action:
Processing
continues.
Administrator
Response:
Contact
IBM
Software
Support.
GTM1861E
OBJECT
TYPE
ID
=
object_id
Explanation:
This
is
a
continuation
of
the
GTM1860E
message.
Message
Variables:
object_id
-
A
valid
object
ID,
such
as
CICS,
STC,
or
IMS
GTM1862E
OBJECT
NAME
=
object_name
Explanation:
This
is
a
continuation
of
the
GTM1860E
message.
Message
Variables:
object_id
-
The
object
name
associated
with
the
non-valid
action
type
and
object
ID
GTM1865E
OMEGAMON
LOG
ON
RECEIVED
FOR
OS
NAME:
OS_name
Explanation:
A
Tivoli
OMEGAMON
logon
request
was
received
by
one
operating
system
with
the
results
being
directed
to
another
operating
system.
This
transaction
is
not
acceptable
because
exceptions
could
be
posted
to
an
incorrect
operating
system.
The
source/390
object
pump
rejects
the
logon
request.
Message
Variables:
OS_name
-
The
name
of
the
operating
system
that
would
receive
the
exceptions
for
the
Tivoli
OMEGAMON
session
System
Action:
Processing
continues.
The
session
is
not
connected.
Administrator
Response:
Verify
the
configuration
matches
the
logon
connections
by
the
source/390
object
pump
to
the
Tivoli
OMEGAMON
programs
and
that
they
are
established
on
the
target
operating
systems.
If
this
error
continues,
contact
IBM
Software
Support.
GTM1866E
THIS
PROCESSOR
IS
OS
NAME:
OS_name
Explanation:
This
is
a
continuation
of
the
GTM1865E
message.
Message
Variables:
OS_name
-
The
name
of
the
operating
system
that
received
the
Tivoli
OMEGAMON
logon
request
GTM1867E
LOGON
REQUEST
WILL
NOT
BE
PROCESSED
Explanation:
This
is
a
continuation
of
the
GTM1865E
message.
GTM1900I
OBJECT
PUMP/OBJECT
SERVER
HAS
ENDED
PROCESSING
Explanation:
The
record
or
batch
of
records
sent
to
the
source/390
object
pump
for
processing
is
completed.
GTM1905E
MESSAGE
DATA
OUT
OF
SEQUENCE
OR
AN
EXPECTED...
Explanation:
A
registration
record
that
was
received
is
not
well
formed.
System
Action:
Processing
continues.
Administrator
Response:
Contact
IBM
Software
Support.
Chapter
1.
Source/390
Messages
-
GTM0001I
-
GTM8665E
15
GTM1906E
CONTINUATION
(\)
WAS
NOT
RECEIVED
-
EXPECTED
DATA
PATTERN
IS...
Explanation:
This
is
a
continuation
of
the
GTM1905E
message.
GTM1907E
46MESSAGE\46MESSAGE\
46MESSAGE
Explanation:
This
is
a
continuation
of
the
GTM1905E
message.
GTM1908E
ALSO,
MESSAGE
DATA
MUST
BE
LAST
DATA
IN
REC
Explanation:
This
is
a
continuation
of
the
GTM1905E
message.
GTM1909E
error_text
Explanation:
This
is
a
continuation
of
the
GTM1905E
message.
Message
Variables:
error_text
-
The
registration
record
that
is
in
error
GTM1910E
STATE/MESSAGE
DATA
OUT
OF
SEQUENCE
OR
AN
EXPECTED
Explanation:
State
and
Message
data
types
(45
and
46,
respectively)
must
be
the
last
data
types
in
a
record
requesting
object
monitoring
and
must
follow
the
pattern
of
State-Message-State-Message-State-Message.
System
Action:
Processing
continues.
Administrator
Response:
See
the
messages
that
accompany
this
message.
If
necessary,
contact
IBM
Software
Support.
GTM1911E
CONTINUATION
(\)
WAS
NOT
RECEIVED
-
EXPECTED
DATA
PATTERN
IS
Explanation:
This
is
a
continuation
of
the
GTM1910E
message.
Administrator
Response:
A
back-slash
character
(\)
might
be
missing
at
the
end
of
a
state
or
message
value.
See
the
acceptable
pattern
in
the
text
of
the
GTM1912E
message.
GTM1912E
45STATE\46MESSAGE\45STATE\
46MESSAGE
Explanation:
This
is
a
continuation
of
the
GTM1910E
message.
Administrator
Response:
The
pattern
for
State
and
Message
values
should
be
as
defined
in
this
message.
The
following
is
an
example:
\45ACTIVE\46IEF403I\45INACTIVE\46IEF404I...
GTM1913E
ALSO,
STATE
AND
MESSAGE
DATA
MUST
BE
LAST
DATA
IN
REC
Explanation:
This
is
a
continuation
of
the
GTM1910E
message.
Administrator
Response:
The
combination
of
State
and
Message
patterns
must
be
at
the
end
of
the
record.
No
other
data
types
are
accepted
after
this
pattern.
GTM1914E
error_text
Explanation:
This
is
a
continuation
of
the
GTM1910E
message.
Message
Variables:
error_text
-
The
registration
message
GTM1915E
NO
MATCHING
MESSAGE
TYPE
FOR
STATE
OR
(\)
MISSING
Explanation:
The
State
and
Message
data
types
(45
and
46,
respectively)
must
be
the
last
data
types
in
a
record
for
monitoring
and
must
follow
the
pattern
of
State-Message-State-Message-State-Message.
State
and
Message
fields
must
be
separated
by
a
backslash.
A
data
type
of
46
(Message)
was
probably
missing
in
the
record
displayed
in
the
GTM1916E
message
text.
System
Action:
Processing
continues.
Administrator
Response:
Contact
IBM
Software
Support.
GTM1916E
msg_type
Explanation:
This
is
a
continuation
of
the
GTM1915E
message.
Message
Variables:
msg_type
-
The
registration
message
GTM1917E
46MESSAGE\46MESSAGE\
46MESSAGE
Explanation:
This
is
a
continuation
of
the
GTM1915E
message.
GTM1918E
ALSO,
MESSAGE
DATA
MUST
BE
LAST
DATA
IN
REC
Explanation:
This
is
a
continuation
of
the
GTM1915E
message.
GTM1919E
error_text
Explanation:
This
is
a
continuation
of
the
GTM1915E
message.
Message
Variables:
error_text
-
The
record
that
is
in
error
16
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
GTM1920E
NO
DATA
VALUE
FOR
field_type
TYPE
data_type
Explanation:
No
data
value
was
found
for
a
State
or
Message
data
type.
Message
Variables:
field_type
-
Indicates
whether
the
missing
value
is
for
a
State
or
a
Message
field
data_type
-
Indicates
the
data
type
for
the
missing
value.
A
State
is
represented
as
data
type
(45)
and
a
Message
is
(46)
System
Action:
Processing
continues.
Administrator
Response:
Contact
IBM
Software
Support.
GTM1921E
error_text
Explanation:
This
is
a
continuation
of
the
GTM1920E
message.
Message
Variables:
error_text
-
The
registration
record
GTM1925E
SUSPECT
THIS
PROGRAM
WAS
MODIFIED
-
THE
VALUE
FOR
Explanation:
The
REXX
EXEC
GTMRX020
program
was
changed
and
is
not
accepting
the
normal
state
and
message
combination.
System
Action:
Processing
continues.
Administrator
Response:
Contact
IBM
Software
Support.
GTM1926E
EXPECTED
DATA
VALUE
CAN
ONLY
BE
45
OR
46
-
CHECK
PROGRAM
Explanation:
This
is
a
continuation
of
the
GTM1925E
message.
GTM1930E
AN
OBJECT
FOR
keyword
WAS
RECEIVED
WITHOUT
STATES
OR
MESSAGES
Explanation:
A
record
for
some
form
of
monitoring
was
received
that
did
not
contain
States
or
Messages
to
monitor.
Message
Variables:
keyword
-
The
name
of
the
keyword,
which
can
be
MONITORING,
REDISCOVER,
SET_UP_IND,
or
MESSAGE_TRAP
System
Action:
Processing
continues.
Administrator
Response:
Contact
IBM
Software
Support.
GTM1931E
error_text
Explanation:
This
is
a
continuation
of
the
GTM1930E
message.
Message
Variables:
error_text
-
The
registration
message
GTM1935E
THE
OBJECT
NAME
EQUALS
THE
OBJECT
SERVER
JOB
NAME
Explanation:
A
trap
for
monitoring
the
source/390
object
server
STC
cannot
be
created.
During
initialization
of
the
mainframe
components,
special
traps
for
monitoring
the
source/390
object
server
are
generated
and
should
not
be
overwritten.
System
Action:
Processing
continues.
Administrator
Response:
Remove
the
object
from
the
database
that
has
the
same
name
as
that
of
the
Object
Server
Started
Task.
Restart
the
source/390
object
pump.
GTM1936E
OBJECT
NAME
=
object_name
Explanation:
This
is
a
continuation
of
the
GTM1935E
message.
Message
Variables:
object_name
-
The
name
of
the
object
requesting
monitoring.
This
is
also
the
source/390
object
server
job
name.
GTM1937E
RECORD
=
error_text
Explanation:
This
is
a
continuation
of
the
GTM1935E
message.
Message
Variables:
error_text
-
The
registration
record
GTM1938E
THIS
COULD
CAUSE
AN
INTERNAL
TBSM
MONITORING
FAILURE
Explanation:
This
is
a
continuation
of
the
GTM1935E
message.
GTM1939E
PLEASE
SEE
THE
MESSAGES
AND
CODES
MANUAL
FOR
MORE
DETAIL
Explanation:
This
is
a
continuation
of
the
GTM1935E
message.
GTM1940I
VALIDATION
MODULE
INVOKED
NO
DATA
RECEIVED
Explanation:
The
source/390
object
pump
was
instructed
to
read
the
source/390
object
pump
data
queue
but
no
data
was
found.
This
could
be
caused
by
a
tilde
character
(~)
missing
at
the
end
of
the
record
that
was
forwarded
from
Tivoli
Business
Systems
Manager.
Another
possibility
is
that
a
non-English
character
was
received
in
place
of
the
tilde
character.
Chapter
1.
Source/390
Messages
-
GTM0001I
-
GTM8665E
17
System
Action:
Processing
continues.
Administrator
Response:
If
a
console
code
page
other
then
437
is
being
used
on
the
Tivoli
Business
Systems
Manager
servers,
review
the
comments
in
the
cconv.tbl
file
in
the
TivoliManager\Lang\language
id
directory.
The
console
code
page
can
be
determined
using
the
SetConsoleCodePage
command.
Issue
SetConsoleCodePage
from
a
DOS
command
prompt
and
note
the
value
of
the
current
console
code
page.
GTM1955I
A
SHUTDOWN
HAS
BEEN
REQUESTED
-
SYSTEM
TERMINATING
Explanation:
The
source/390
object
pump
was
instructed
to
shut
down.
All
events
ended
normally.
System
Action:
The
source/390
tasks
are
shut
down.
GTM1960E
UNKNOWN
SUB-FUNCTION
RECEIVED
FROM
A
PASSED
ARGUMENT
Explanation:
An
unknown
sub
function
value
was
passed
to
the
GTMRX018
program.
The
valid
sub
functions
are
JOB,
CYLCE,
STATUSA,
STATUSI,
CHILD_DISCOVER,ID,
REQUEST_OBJECTS,
and
SHIP_MESSAGE.
System
Action:
Processing
continues.
GTM1961E
EXPECTED
FORMAT
OF
ARGUMENT
(FUNCTION
SUB-FUNCTION)
Explanation:
This
is
a
continuation
of
the
GTM1960E
message.
GTM1962E
ARGUMENT
=
error_text
Explanation:
This
is
a
continuation
of
the
GTM1960E
message.
Message
Variables:
error_text
-
The
argument
that
was
passed
to
the
GTMRX018
program.
The
first
two
fields
represent
the
FUNCTION
and
SUB-FUNCTION.
GTM1965E
ERROR
PROCESSING
SYSTEM
VARIABLE
variable_name
IN
pgm
Explanation:
An
error
occurred
retrieving
the
job
name
of
the
source/390
object
pump
from
the
system
variable
pool.
Message
Variables:
variable_name
-
The
variable
name,
which
is
SYS_AOPJOBNAME
pgm
-
The
REXX
EXEC
GTMRX018
program
System
Action:
The
source/390
task
is
shut
down.
Administrator
Response:
Check
the
system
messages
and
the
AOPLOG
log
to
see
if
there
are
any
related
messages
that
might
indicate
why
the
function
failed.
The
source/390
pump
initialization
is
shut
down.
Resolve
the
cause
of
the
error
and
restart
the
source/390
object
pump.
If
the
problem
continues,
contact
IBM
Software
Support.
GTM1966E
PROCESSING
HAS
BEEN
TERMINATED
Explanation:
This
is
a
continuation
of
the
GTM1965E
message.
GTM1970E
THERE
CAN
ONLY
BE
ONE
TDQ/BATCH
CYCLE
MESSAGE
(TYPE
46)
IN
THE
RECORD
Explanation:
The
source/390
object
pump
received
a
single
request
to
capture
more
than
one
generic
message
related
to
batch/TDQ
processing.
Only
one
generic
message
(data
type
46)
can
be
coded
in
a
request.
System
Action:
Processing
continues.
Administrator
Response:
Contact
IBM
Software
Support.
GTM1971E
error_text
Explanation:
This
is
a
continuation
of
the
GTM1970E
message.
Message
Variables:
error_text
-
The
TDQ/BATCH
CYCLE
message
in
error
GTM1975E
MISSING
DATA.
SEE
NULL
FIELD
BELOW
FOR
MISSING
VALUE:
Explanation:
The
creation
of
a
console
trap
for
a
TDQ
or
Batch
Cycle
message
is
missing
a
key
value.
System
Action:
Processing
continues.
Administrator
Response:
Contact
IBM
Software
Support.
GTM1976E
OBJECT
ID
=
object_id
SET
UP
INDICATOR
=
value
Explanation:
This
is
a
continuation
of
the
GTM1975E
message.
Message
Variables:
object_id
-
The
value
of
the
object
ID
or
a
NULL
value
value
-
The
value
of
the
set-up-indicator
(expected
to
be
TDQ)
or
a
NULL
value
GTM1977E
MESSAGE-ID
=
msgid
Explanation:
This
is
a
continuation
of
the
GTM1975E
message.
Message
Variables:
msgid
-
The
value
of
the
message
ID
to
be
trapped
or
a
NULL
value
18
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
GTM1978E
error_text
Explanation:
This
is
a
continuation
of
the
GTM1975E
message.
Message
Variables:
error_text
-
The
registration
message
that
contains
the
error
GTM1980E
THERE
CAN
ONLY
BE
ONE
TIME
DURATION
CODE
data_type
IN
THE
RECORD
Explanation:
There
was
more
than
one
start
or
stop
time
duration
value
for
a
TDQ
or
Batch
Cycle
record.
Message
Variables:
data_type
-
The
data
type
in
error.
Data
type
68
is
the
start
time
for
trap
collection
and
data
type
69
is
the
stop
time
for
trap
collection.
System
Action:
Processing
continues.
Administrator
Response:
Contact
IBM
Software
Support.
GTM1981E
error_text
Explanation:
This
is
a
continuation
of
the
GTM1980E
message.
Message
Variables:
error_text
-
The
registration
record
that
contains
the
error
GTM1985E
BATCH
JOB
SUBMISSION
FAILED,
UNABLE
TO
LOCATE
jobname
Explanation:
The
READMEM
function
failed
in
the
GTMRXJOB
job.
The
batch
job
is
not
submitted.
Message
Variables:
jobname
-
The
PDS
member
containing
the
job
name
cannot
be
located.
System
Action:
Processing
continues.
Administrator
Response:
Verify
that
the
batch
job
exists
in
the
library
of
the
source/390
object
pump
where
batch
jobs
might
be
submitted.
If
the
batch
job
exists
and
the
batch
job
fails
to
be
submitted,
check
the
resources
under
JES2
to
ensure
there
are
internal
readers
available.
Submit
the
batch
job
again.
GTM1986E
BATCH
JOB
SUBMISSION
FAILED,
INVALID
JCL
RECORD
LENGTH
record_length
Explanation:
A
record
that
is
read
from
the
READMEM
function
to
retrieve
a
JCL
record
is
too
long.
The
batch
job
is
not
submitted.
Message
Variables:
record_length
-
The
length
of
a
JCL
record
System
Action:
Processing
continues.
Administrator
Response:
Verify
that
the
JCL
records
are
80
characters
in
length
and
submit
the
batch
job
again.
GTM2010E
INVALID
NUMBER
OF
ARGUMENTS
PASSED
TO
MESSAGE
MANAGER:
Explanation:
The
Message
Manager
REXX
EXEC
GTMRX016
program
received
a
request
to
generate
a
message,
but
the
request
did
not
contain
the
proper
number
of
arguments.
System
Action:
Processing
continues.
Administrator
Response:
Contact
IBM
Software
Support.
GTM2011E
NUMBER
OF
ARGUMENTS
=
number
Explanation:
This
is
a
continuation
of
the
GTM2010E
message.
Message
Variables:
number
-
The
number
of
arguments
received
by
the
Message
Manager
GTMRX016
program
GTM2012E
CORRECT
NUMBER
OF
ARGUMENTS
>=
2
OR
<=
8
Explanation:
This
is
a
continuation
of
the
GTM2010E
message.
GTM2013E
CALLING
PROGRAM
NAME
IS
SET
TO
pgm
Explanation:
This
is
a
continuation
of
the
GTM2010E
message.
Message
Variables:
pgm
-
The
name
of
the
REXX
EXEC
calling
the
Message
Manager
GTMRX016
program
GTM2080E
A
SYNTAX
ERROR
OCCURRED
WHICH
MIGHT
BE
DUE
TO
AN
INVALID
MESSAGE
ID
Explanation:
The
Message
Manager
REXX
EXEC
GTMRX016.
program
received
a
request
to
generate
a
message
for
a
message
ID
that
is
not
valid
or
is
undefined.
System
Action:
Processing
continues.
Administrator
Response:
Contact
IBM
Software
Support.
GTM2081E
THE
MESSAGE
ID
=
msgid
Explanation:
This
is
a
continuation
of
the
GTM2080E
message.
Message
Variables:
msgid
-
The
message
ID
being
sent
to
the
GTMRX016
program
Chapter
1.
Source/390
Messages
-
GTM0001I
-
GTM8665E
19
GTM2082E
THIS
PROCESS
WAS
STOPPED
ON
LINE:
error_line
Explanation:
This
is
a
continuation
of
the
GTM2080E
message.
Message
Variables:
error_line
-
The
line
number
where
processing
stopped
GTM2083E
THE
SOURCE
LINE
IS:
source_line
Explanation:
This
is
a
continuation
of
the
GTM2080E
message.
Message
Variables:
source_line
-
The
source
line
where
processing
stopped
GTM2084E
THIS
PROGRAM
IS:
pgm
THE
CALLING
PROGRAM
IS:
pgm_called
Explanation:
This
is
a
continuation
of
the
GTM2080E
message.
Message
Variables:
pgm
-
The
name
of
the
REXX
program
that
encountered
the
syntax
error
pgm_called
-
The
name
of
the
REXX
program
that
called
the
program
in
error
GTM2085E
THIS
PROCESS
WAS
HALTED
ON
LINE:
error_line
Explanation:
The
GTMRX016
module
encountered
a
halt
error
and
cannot
programmatically
correct
it.
Message
Variables:
error_line
-
The
line
number
in
the
GTMRX016
module
System
Action:
Processing
continues.
Administrator
Response:
Contact
IBM
Software
Support.
GTM2086E
THE
SOURCE
LINE
IS:
error_text
Explanation:
This
is
a
continuation
of
the
GTM2085E
message.
Message
Variables:
error_text
-
This
is
the
source
line
that
encountered
the
error
in
the
GTMRX016
module
GTM2087E
THIS
PROGRAM
IS:pgm,
THE
CALLING
PROGRAM
IS:
pgm_called
Explanation:
This
is
a
continuation
of
the
GTM2085E
message.
Message
Variables:
pgm
-
The
name
of
the
program
that
encountered
the
error
pgm_called
-
The
name
of
the
program
that
called
the
program
in
error
GTM2088E
AN
ERROR
OCCURRED
ON
LINE:
error_line
Explanation:
A
program
encountered
an
error.
Message
Variables:
error_line
-
The
program
line
number
of
the
program
that
encountered
the
error
System
Action:
Processing
continues.
Administrator
Response:
Contact
IBM
Software
Support.
GTM2089E
THE
SOURCE
LINE
IS:
error_text
Explanation:
This
is
a
continuation
of
the
GTM2088E
message.
Message
Variables:
error_text
-
This
is
the
source
code
that
encountered
the
error
GTM2090E
THIS
PROGRAM
IS:
pgm,
THE
CALLING
PROGRAM
IS:
pgm_called
Explanation:
This
is
a
continuation
of
the
GTM2088E
message.
Message
Variables:
pgm
-
The
program
in
error
pgm_called
-
The
program
that
called
the
program
in
error
GTM2100E
ERROR
DETERMINING
LOG
FILE
NAME.
LOGGING
IS
DISABLED
Explanation:
The
name
of
the
log
file
cannot
be
retrieved.
System
Action:
Processing
continues.
Administrator
Response:
Contact
IBM
Software
Support.
GTM2101I
LOG
PROCESSING
IS
AVAILABLE.
DDNAME
=
ddname
Explanation:
The
log
file
is
operational.
Message
Variables:
ddname
-
The
DD
name
associated
with
the
log
file
System
Action:
Processing
continues.
GTM2102I
DSNAME
=
dsname
Explanation:
This
is
a
continuation
of
the
GTM2101I
message.
Message
Variables:
dsname
-
The
data
set
name
of
the
log
file
20
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
GTM2103E
UNABLE
TO
DETERMINE
LENGTH
OF
LOG
RECORD
-
LOGGING
IS
DISABLED
Explanation:
The
logical
record
length
of
the
log
file
cannot
be
determined.
Logging
is
disabled
but
processing
continues.
System
Action:
Processing
continues.
Administrator
Response:
Check
the
log
file
to
make
sure
it
is
available.
Verify
the
log
file
is
cataloged
and
the
DASD
volume
used
is
online.
If
the
problem
continues,
contact
IBM
Software
Support.
GTM2104I
THE
LOG
WILL
BE
CLOSED
AND
OPENED
ON
THE
FOLLOWING
INTERVAL:
time_interval
Explanation:
To
prevent
the
loss
of
data,
the
log
file
is
closed
and
reallocated
based
on
the
interval
described
at
the
end
of
this
message.
Message
Variables:
time_interval
-
The
time
interval
in
hh:mm:ss
System
Action:
Processing
continues.
GTM2110E
COULD
NOT
ALLOCATE
THE
LOG
FILE
ddname
Explanation:
The
log
file
cannot
be
allocated.
Message
Variables:
ddname
-
The
DD
name
of
the
log
file
that
cannot
be
allocated
System
Action:
Processing
stops.
Administrator
Response:
Determine
why
the
log
file
cannot
be
allocated.
Resolve
the
cause
of
the
error
and
restart
the
source/390
object
pump.
If
the
error
continues,
contact
IBM
Software
Support.
GTM2111E
FILE
NAME
IS
dsname
Explanation:
This
is
a
continuation
of
the
GTM2110E
message.
Message
Variables:
dsname
-
The
data
set
name
of
the
log
file
that
could
not
be
allocated
GTM2112E
RETURN
CODE
=
return_code
-
LOGGING
IS
HALTED
Explanation:
This
is
a
continuation
of
the
GTM2110E
message.
Message
Variables:
return_code
-
The
return
code
from
the
allocation
attempt
GTM2120E
COULD
NOT
OPEN
THE
LOG
FILE
ddname
Explanation:
The
log
file
for
the
source/390
object
pump
could
not
be
opened
and
the
log
data
is
not
processed.
Message
Variables:
ddname
-
The
DD
name
of
the
file
allocated
to
the
log
System
Action:
Processing
continues.
Administrator
Response:
Determine
why
the
log
file
cannot
be
opened.
Resolve
the
cause
of
the
error
and
restart
the
source/390
object
pump.
If
the
error
continues,
contact
IBM
Software
Support.
GTM2121E
FILE
NAME
IS
dsname
Explanation:
This
is
a
continuation
of
the
GTM2120E
message.
Message
Variables:
dsname
-
The
data
set
name
of
the
log
file
that
could
not
be
opened
GTM2122E
RETURN
CODE
=
return_code
-
LOGGING
IS
HALTED
Explanation:
This
is
a
continuation
of
the
GTM2120E
message.
Message
Variables:
return_code
-
The
return
code
from
the
open
failure
GTM2130E
COULD
NOT
WRITE
TO
THE
LOG
FILE
ddname
Explanation:
The
log
file
could
not
be
written
for
the
source/390
object
pump.
Message
Variables:
ddname
-
The
DD
name
of
the
log
file
that
was
allocated
and
opened
System
Action:
Processing
continues.
Administrator
Response:
Determine
why
the
log
file
cannot
be
written
to.
Resolve
the
cause
of
the
error
and
restart
the
source/390
object
pump.
If
the
error
continues,
contact
IBM
Software
Support.
GTM2131E
FILE
NAME
CAN
BE
FOUND
IN
MESSAGE
GTM210I
Explanation:
This
is
a
continuation
of
the
GTM2130E
message.
The
data
set
name
for
the
log
file
can
be
found
in
the
GTM210I
message
text.
GTM2132E
RETURN
CODE
=
return_code
LOGGING
IS
HALTED
Explanation:
This
is
a
continuation
of
the
GTM2130E
message.
Message
Variables:
return_code
-
The
return
code
associated
with
the
write
error
on
the
log
file
Chapter
1.
Source/390
Messages
-
GTM0001I
-
GTM8665E
21
GTM2140I
COULD
NOT
CLOSE
THE
LOG
FILE
RETURN
CODE=return_code
Explanation:
The
log
file
for
the
source/390
object
pump
could
not
be
closed
after
use.
Message
Variables:
return_code
-
This
is
the
return
code
from
the
attempted
close
operation
of
the
log
file
System
Action:
Processing
continues.
Administrator
Response:
Determine
why
the
log
file
cannot
be
closed.
Resolve
the
cause
of
the
error
and
restart
the
source/390
object
pump.
If
the
error
continues,
contact
IBM
Software
Support.
GTM2141I
FILE
NAME
CAN
BE
FOUND
IN
PREVIOUS
MESSAGE
GTM210I
Explanation:
This
is
a
continuation
of
the
GTM2140I
message.
The
data
set
name
can
be
found
in
the
GTM2101I
message
text.
GTM2150I
COULD
NOT
FREE
THE
LOG
FILE
-
RETURN
CODE=return_code
Explanation:
The
source/390
object
pump
log
file
could
not
be
dynamically
freed
after
it
was
closed.
Message
Variables:
return_code
-
The
return
code
from
the
attempt
System
Action:
Processing
continues.
Administrator
Response:
Determine
why
the
log
file
cannot
be
freed.
Resolve
the
cause
of
the
error
and
restart
the
source/390
object
pump.
If
the
error
continues,
contact
IBM
Software
Support.
GTM2151I
FILE
NAME
CAN
BE
FOUND
IN
PREVIOUS
MESSAGE
GTM2101
Explanation:
This
is
a
continuation
of
the
GTM2150I
message.
The
data
set
name
of
the
file
not
freed
can
be
found
in
the
GTM2101
message
text.
GTM2155I
LOG
PROCESSING
HAS
BEEN
TERMINATED
Explanation:
The
source/390
object
pump
shut
down
and
the
logging
is
stopped.
System
Action:
Processing
continues.
GTM2160I
INVALID
FUNCTION
function
PASSED
TO
pgm
Explanation:
A
function
name
that
was
not
valid
was
passed
to
the
GTMRX006
program.
Message
Variables:
function
-
The
value
of
the
function
that
was
not
valid
pgm
-
The
name
of
the
REXX
program
System
Action:
Processing
continues.
Administrator
Response:
Contact
IBM
Software
Support.
GTM2161I
VALID
FUNCTIONS
ARE
INIT,
SHUT
OR
LOG
Explanation:
This
is
a
continuation
of
the
GTM2160I
message.
GTM2170E
ERROR
WRITING
SHARED
VARIABLE
variable_name
IN
pgm
Explanation:
The
source/390
object
pump
is
not
able
to
set
the
shared
variable.
Message
Variables:
variable_name
-
The
name
of
the
shared
variable
pgm
-
The
name
of
the
program
attempting
to
set
the
variable
System
Action:
Processing
continues.
Administrator
Response:
Increase
the
region
parameter
and
restart
the
source/390
object
pump.
If
the
error
continues,
contact
IBM
Software
Support.
GTM2171E
RC
=
return_code
INITIALIZATION
PROCESSING
HAS
BEEN
TERMINATED
Explanation:
This
is
a
continuation
of
the
GTM2170E
message.
Message
Variables:
return_code
-
The
return
code
associated
with
the
SET
variable
write
failure
GTM2175E
ERROR
request
SHARED
VARIABLE
variable_name
IN
pgm
RC
=
return_code
Explanation:
The
source/390
object
pump
logging
facility
encountered
an
error
in
processing
the
shared
variable
name.
Message
Variables:
request
-
Either
GETTING
or
PUTTING,
which
indicates
reading
or
writing
variable_name
-
The
name
of
the
shared
variable
that
could
not
be
read
or
written
pgm
-
The
name
of
the
REXX
program
where
the
error
occurred
return_code
-
The
return
code
from
the
read
or
write
failure
System
Action:
Processing
continues.
Administrator
Response:
Increase
the
region
parameter
and
restart
the
source/390
object
pump.
If
the
error
continues,
contact
IBM
Software
Support.
22
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
GTM2190E
AN
ERROR
error_type
OCCURRED
IN
PROGRAM
pgm
ON
LINE:
error_line
Explanation:
This
is
a
global
message
used
when
a
REXX
program
encounters
a
program
error.
Message
Variables:
error_type
-
The
type
of
error,
such
as
syntax
pgm
-
The
name
of
the
REXX
program
where
the
error
occurred
error_line
-
The
line
number
in
the
program
where
the
error
occurred
System
Action:
Processing
continues.
Administrator
Response:
Check
the
system
messages
and
the
AOPLOG
log
to
see
if
there
are
any
related
messages
that
might
indicate
why
the
function
failed.
Resolve
the
cause
of
the
error
and
restart
the
source/390
object
pump.
If
the
problem
continues,
contact
IBM
Software
Support.
GTM2191E
THE
SOURCE
LINE
IS:
error_text
Explanation:
This
is
a
continuation
of
the
GTM2190E
message.
Message
Variables:
error_text
-
The
source
line
that
was
in
error
GTM2710E
AN
ERROR
error_type
OCCURRED
IN
PROGRAM
pgm
ON
LINE:
error_line
Explanation:
This
is
a
global
message
utilized
when
a
REXX
program
encounters
a
program
error.
Message
Variables:
error_type
-
The
type
of
error,
such
as
syntax
pgm
-
The
name
of
the
REXX
program
error_line
-
The
line
number
in
the
program
where
the
error
occurred
System
Action:
Processing
continues.
Administrator
Response:
Check
the
system
messages
and
the
AOPLOG
log
to
see
if
there
are
any
related
messages
that
might
indicate
why
the
function
failed.
Resolve
the
cause
of
the
error
and
restart
the
source/390
object
pump.
If
the
problem
continues,
contact
IBM
Software
Support.
GTM2711E
THE
SOURCE
LINE
IS:
error_text
Explanation:
This
is
a
continuation
of
the
GTM2710E
message.
Message
Variables:
error_text
-
The
source
line
where
the
error
occurred
GTM4007I
LOG
DATASET
PARAMETER
MISSING,
PARM=parameter
Explanation:
The
source/390
object
server
task
is
started
without
the
LOG1
or
LOG2
data
sets
specified.
Message
Variables:
parameter
-
Indicates
the
log
parameter
that
is
missing
System
Action:
Processing
continues.
Logging
is
not
attempted.
Administrator
Response:
Correct
the
data
set
name
parameter
in
error.
GTM4010I
TBSM
INITIALIZATION
COMPLETED
Explanation:
The
source/390
object
server
initialization
completed.
System
Action:
Processing
continues.
GTM4030I
INTERFACE
ESTABLISHED,
CONSOLE
COMMUNICATION
AVAILABLE
Explanation:
The
source/390
object
server
MODIFY
command
interface
is
now
available.
System
Action:
Processing
continues.
The
address
space
is
now
able
to
receive
MODIFY
commands.
GTM4032I
STOP
COMMAND
RECEIVED,
TBSM
TERMINATING
Explanation:
The
source/390
object
server
received
a
stop
command
and
is
ending.
System
Action:
The
address
space
begins
the
shutdown
process.
GTM4033I
OBJECT
SERVER
SENSED,
SERVER
name
Explanation:
The
source/390
object
server
detected
the
source/390
data
space
address
space.
Message
Variables:
name
-
The
name
of
the
source/390
data
space
address
space
System
Action:
Processing
continues.
GTM4084E
ADDRESS
SPACE
NOT
APF
AUTHORIZED,
TBSM
TERMINATING
Explanation:
The
source/390
object
server
is
not
APF
authorized.
System
Action:
The
address
space
shuts
down.
Administrator
Response:
APF
authorize
all
the
libraries
in
the
STEPLIB
DD
statement
of
the
source/390
object
server
JCL.
Chapter
1.
Source/390
Messages
-
GTM0001I
-
GTM8665E
23
GTM4085E
INVALID
DATASPACE
ORIGIN
FOUND,
TBSM
TERMINATING
Explanation:
The
source/390
object
server
found
that
the
data
space
was
not
correctly
initialized
or
was
corrupted.
System
Action:
The
address
space
shuts
down.
Administrator
Response:
Restart
the
data
space
and
source/390
object
server.
If
the
problem
continues,
contact
IBM
Software
Support.
GTM4087E
SERVER
ADDRESS
SPACE
NOT
STARTED,
TBSM
TERMINATING
Explanation:
The
source/390
object
server
could
not
locate
the
data
space
address
space.
System
Action:
The
address
space
shuts
down.
Administrator
Response:
Ensure
that
the
data
space
address
space
is
fully
initialized
on
the
same
z/OS
image
before
starting
the
source/390
object
server.
GTM4088E
RETURN
FROM
CIB
FREE,
R15=return_code
Explanation:
An
error
occurred
in
the
source/390
object
server
when
issuing
a
QEDIT
macro
instruction.
Message
Variables:
return_code
-
The
return
code
System
Action:
The
address
space
shuts
down.
Administrator
Response:
Determine
why
the
QEDIT
macro
failed.
If
necessary,
contact
IBM
Software
Support.
GTM4089E
OPEN
FAILED
FOR
ACC1PARM,
TBSM
TERMINATING,
RETURN
CODE(R15)=return_code
Explanation:
An
error
occurred
in
the
source/390
object
server
when
opening
the
ACC1PARM
data
set.
Message
Variables:
return_code
-
The
return
code
from
the
OPEN
macro
System
Action:
The
address
space
shuts
down.
Administrator
Response:
Determine
why
the
OPEN
macro
failed.
For
further
details,
refer
to
the
DFSMS/MVS®
Macro
Instructions
Data
Sets
document.
If
necessary,
contact
IBM
Software
Support.
GTM4090E
INSUFFICIENT
VIRTUAL
STORAGE,
MEMBER=name,
TBSM
TERMINATING,
RETURN
CODE
(R15)=return_code,
REASON
CODE
(R0)=reason_code
Explanation:
An
error
occurred
in
the
source/390
object
server
while
locating
a
member
in
the
ACC1PARM
data
set.
Message
Variables:
name
-
The
member
name
return_code
-
The
return
code
from
the
FIND
macro
reason_code
-
The
reason
code
from
the
FIND
macro
System
Action:
The
address
space
shuts
down.
Administrator
Response:
Determine
why
the
FIND
macro
failed.
Increase
the
region
size
of
the
source/390
object
server
address
space.
If
necessary,
contact
IBM
Software
Support.
GTM4091E
PERMANENT
I/O
ERROR
IN
PARM
DATASET,
TBSM
TERMINATING,
RETURN
CODE
(R15)=return_code,
REASON
CODE
(R0)=reason_code
Explanation:
A
permanent
IO
error
occurred
in
the
source/390
object
server
while
locating
a
member
in
the
ACC1PARM
data
set.
Message
Variables:
return_code
-
The
return
code
from
the
FIND
macro
reason_code
-
The
reason
code
from
the
FIND
macro
System
Action:
The
address
space
shuts
down.
Administrator
Response:
Determine
why
the
FIND
macro
failed.
For
further
details,
refer
to
the
DFSMS/MVS
Macro
Instructions
Data
Sets
document.
If
necessary,
contact
IBM
Software
Support.
GTM4092E
FIND
MACRO
FAILED
FOR
MEMBER
name,
TBSM
TERMINATING,
RETURN
CODE
(R15)=return_code,
REASON
CODE
(R0)=reason_code
Explanation:
An
error
occurred
in
the
source/390
object
server
when
issuing
the
FIND
macro
for
member
p1
against
the
ACC1PARM
data
set.
Message
Variables:
name
-
The
member
name
return_code
-
The
return
code
from
the
FIND
macro
reason_code
-
The
reason
code
from
the
FIND
macro
System
Action:
The
address
space
shuts
down.
Administrator
Response:
Determine
why
the
FIND
macro
failed.
For
further
details,
refer
to
the
DFSMS/MVS
Macro
Instructions
Data
Sets
document.
If
necessary,
contact
IBM
Software
Support.
GTM4093E
PARM
MEMBER
name
NOT
FOUND,
TBSM
TERMINATING,
RETURN
CODE
(R15)=return_code,
REASON
CODE
(R0)=reason_code
Explanation:
The
parameter
member
name
was
not
found
in
the
ACC1PARM
library.
Message
Variables:
name
-
The
member
name
return_code
-
The
return
code
from
the
FIND
macro
24
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
reason_code
-
The
reason
code
from
the
FIND
macro
System
Action:
The
address
space
shuts
down.
Administrator
Response:
Determine
why
the
member
was
not
found.
Verify
that
the
parameter
members
are
in
the
correct
library.
For
further
details,
refer
to
the
services
manual
in
the
z/OS
DFSMS/MVS
library.
If
necessary,
contact
IBM
Software
Support.
GTM4094E
TIOT
ADDRESS
INVALID,
ADDRESS=address,
TBSM
TERMINATING
Explanation:
The
Task
Input
Output
Table
(TIOT)
address
returned
by
the
extract
macro
was
zero.
The
source/390
object
server
is
unable
to
locate
the
TIOT.
System
Action:
address
-
The
TIOT
address
name
returned
by
the
EXTRACT
macro
Administrator
Response:
Determine
why
the
TIOT
address
was
zero.
If
necessary,
contact
IBM
Software
Support.
GTM4095E
MODULE
name
NOT
LOADED,
TBSM
TERMINATING
Explanation:
The
source/390
object
server
was
unable
to
load
the
named
module.
Message
Variables:
name
-
The
module
name
System
Action:
The
address
space
shuts
down.
Administrator
Response:
Determine
why
the
source/390
object
server
was
unable
to
load
the
specified
module.
Validate
that
the
STEPLIB
DD
concatenation
contains
the
SGTMMODS
library.
This
might
be
an
installation
problem.
If
necessary,
contact
IBM
Software
Support.
GTM4110I
name
USING
ID
id
Explanation:
The
ID
characters
from
the
ACC1IDxx
DD
card
are
displayed.
The
default
ID
value
is
01
if
no
ACC1IDxx
DD
card
is
found.
The
source/390
object
pump,
data
space,
and
source/390
object
server
must
all
use
the
same
ID
characters
in
order
to
locate
each
other.
Message
Variables:
name
-
The
address
space
name,
which
is
the
job
or
started
task
name
id
-
The
ID
characters
System
Action:
Processing
continues.
GTM4120E
ACC1XMCM:
XCOM
COMMUNICATION
AREA
NOT
ESTABLISHED
Explanation:
The
source/390
object
pump
or
source/390
object
server
was
unable
to
initialize
the
communication
area
between
the
source/390
object
pump
and
source/390
object
server.
System
Action:
Processing
continues.
Administrator
Response:
Determine
why
Tivoli
Business
Systems
Manager
was
unable
to
initialize
the
communications
area.
If
necessary,
contact
IBM
Software
Support.
GTM4121E
ACC1XMCM:
NAME/TOKEN
CREATE
FAILED
FOR
XCOM
AREA
RC=return_code
Explanation:
The
source/390
object
pump
or
source/390
object
server
was
unable
to
create
the
name
token
associated
with
the
communication
area
between
the
source/390
object
pump
and
source/390
object
server.
Message
Variables:
return_code
-
The
return
code
from
the
call
to
the
IEANTCR
macro
System
Action:
The
address
space
shuts
down.
Administrator
Response:
Determine
why
the
call
to
the
IEANTCR
macro
failed.
Refer
to
the
services
manual
in
the
z/OS
MVS
library.
If
necessary,
contact
IBM
Software
Support.
GTM4123E
ACC1XMCM:
RESMGR
ADD
FOR
XCOM
COMMUNICATION
FAILED
RC=return_code
Explanation:
The
source/390
object
pump
or
source/390
object
server
was
unable
to
create
the
resource
manager
associated
with
the
communication
area
between
the
source/390
object
pump
and
source/390
object
server.
Message
Variables:
return_code
-
The
return
code
from
the
RESMGR
ADD
call
System
Action:
The
address
space
shuts
down.
Administrator
Response:
Determine
why
the
RESMGR
ADD
macro
failed.
Refer
to
the
services
manual
in
the
z/OS
MVS
library.
If
necessary,
contact
IBM
Software
Support.
GTM4124E
ACC1XMCM
RESMGR
ROUTINE
LOAD
FAILED
FOR
ACC1XRSM
RC=return_code
Explanation:
The
source/390
object
pump
or
source/390
object
server
was
unable
to
load
the
resource
manager,
GTMACC52
associated
with
the
communication
area
between
the
source/390
object
pump
and
source/390
object
server.
Message
Variables:
return_code
-
The
return
code
from
the
LOAD
macro
System
Action:
The
address
space
shuts
down.
Administrator
Response:
Determine
why
the
load
of
the
GTMACC52
program
failed.
Validate
that
the
Chapter
1.
Source/390
Messages
-
GTM0001I
-
GTM8665E
25
STEPLIB
DD
concatenation
contains
the
SGTMMODS
library.
This
might
be
an
installation
problem.
If
necessary
contact
IBM
Software
Support.
GTM4125E
ACC1XMCM:
LINK
FAILED
TO
ACC1ID
RC=return_code
Explanation:
The
source/390
object
pump
or
source/390
object
server
was
unable
to
link
to
the
ID
module,
GTMACC19.
Message
Variables:
return_code
-
The
return
code
from
the
LINK
macro
System
Action:
The
address
space
shuts
down.
Administrator
Response:
Determine
why
the
load
of
the
GTMACC19
program
failed.
Validate
that
the
STEPLIB
DD
concatenation
contains
the
SGTMMODS
library.
This
might
be
an
installation
problem.
If
necessary
contact
IBM
Software
Support.
GTM4126E
ADDRESS
SPACE
TYPE
IS
NOT
VALID
Explanation:
The
z/OS
task
issuing
this
error
cannot
identify
the
type
of
task
running.
System
Action:
The
address
space
shuts
down.
Administrator
Response:
This
is
an
internal
error.
If
necessary
contact
IBM
Software
Support.
GTM4200I
ALLOCATION
SUCCESSFUL,
DDNAME=ddname,
S99ERROR=error_text
S99INFO=reason_code,
DSNAME=dsname
Explanation:
The
specified
data
set
was
allocated
to
the
named
DD
name
using
the
SVC
99
(DYNALLOC)
service.
Message
Variables:
ddname
-
The
DD
name
error_text
-
The
error
information
from
the
SVC
99
call
reason_code
-
The
reason
code
from
the
SVC
99
call
dsname
-
The
data
set
name
that
was
allocated
System
Action:
Processing
continues.
GTM4207E
FREE
FAILED,
DDNAME=ddname,
RC=return_code,
S99ERROR=error_text,
S99INFO=reason_code
Explanation:
Deallocation
of
the
specified
DD
name
failed.
The
message
displays
return
code
information
from
the
SVC
99
(DYNALLOC)
macro.
Message
Variables:
ddname
-
The
DD
name
return_code
-
The
return
code
from
the
SVC
99
call
error_text
-
The
error
information
from
the
SVC
99
call
reason_code
-
The
reason
code
from
the
SVC
99
call
System
Action:
Processing
continues.
Administrator
Response:
Determine
why
the
deallocation
failed.
Refer
to
the
services
manual
in
the
z/OS
MVS
library
for
a
description
of
the
DYNALLOC
return
codes.
If
necessary,
contact
IBM
Software
Support.
GTM4208E
ALLOCATION
ERROR,
DDNAME=ddname,
RC=return_code,
S9ERROR=error_text,
S99INFO=reason_code,
DSNAME=dsname
Explanation:
Allocation
of
the
specified
data
set
failed.
The
message
displays
return
code
information
from
the
SVC
99
(DYNALLOC)
macro.
Message
Variables:
ddname
-
The
DD
name
return_code
-
The
return
code
from
the
SVC
99
call
error_text
-
Error
information
from
the
SVC
99
call
reason_code
-
The
reason
code
from
the
SVC
99
call
dsname
-
The
data
set
name
being
allocated
System
Action:
Processing
continues.
Administrator
Response:
Determine
why
the
allocation
failed.
Refer
to
the
services
manual
in
the
z/OS
MVS
library
for
a
description
of
the
DYNALLOC
return
codes.
If
necessary,
contact
IBM
Software
Support.
GTM4209E
INVALID
FUNCTION
PASSED
TO
ALLOCATE,
FUNCTION=function_code
Explanation:
A
request
was
made
to
the
dynamic
allocation
module
that
was
not
valid.
Message
Variables:
function_code
-
The
hexadecimal
function
code
that
was
passed
System
Action:
The
address
space
shuts
down.
Administrator
Response:
This
is
an
internal
error.
Contact
IBM
Software
Support.
GTM4219E
MODULE
name
NOT
LOADED.
TBSM
TERMINATING
Explanation:
Tivoli
Business
Systems
Manager
was
unable
to
load
the
specified
module.
Processing
ends.
Message
Variables:
name
-
The
module
name
System
Action:
The
address
space
shuts
down.
Administrator
Response:
Determine
why
the
module
cannot
be
loaded.
Validate
that
the
STEPLIB
DD
concatenation
contains
the
SGTMMODS
library.
This
might
be
an
installation
problem.
If
necessary,
contact
IBM
Software
Support.
26
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
GTM4300I
ACC1TERM
IN
CONTROL
Explanation:
The
source/390
object
server
ending
module
is
stopping
the
source/390
object
server.
System
Action:
The
address
space
shuts
down.
GTM4303W
LATCHES
NOT
PURGED,
LATCH
PURGE
RC=return_code,
TERMINATION
CONTINUING
Explanation:
No
latches
were
found
during
the
stopping
of
the
source/390
object
server.
Message
Variables:
return_code
-
The
return
code
System
Action:
The
shutdown
process
continues.
Administrator
Response:
Contact
IBM
Software
Support.
GTM4439E
CELL
FREE
FAILED,
CELL
ADDR=address,
RC=return_code
Explanation:
An
error
occurred
during
the
call
to
the
CSRPFRE
macro
to
release
a
cell
in
the
data
space.
Message
Variables:
address
-
The
address
of
the
cell
being
released
return_code
-
The
return
code
from
the
call
to
the
CSRPFRE
macro
System
Action:
Processing
continues,
but
results
are
unpredictable.
Administrator
Response:
Determine
why
the
call
to
the
CSRPFRE
macro
failed.
Refer
to
the
services
manual
in
the
z/OS
MVS
library.
If
necessary,
contact
IBM
Software
Support.
GTM4459E
CELL
GET
FAILED,
RC=return_code
Explanation:
An
error
occurred
during
the
call
to
the
CSRPGET
macro
to
obtain
a
cell
in
the
data
space.
Message
Variables:
return_code
-
The
return
code
from
the
call
to
the
CSRPGET
macro
System
Action:
Processing
continues,
but
results
are
unpredictable.
Administrator
Response:
Determine
why
the
call
to
the
CSRPGET
macro
failed.
Refer
to
the
services
manual
in
the
z/OS
MVS
library.
If
necessary,
contact
IBM
Software
Support.
GTM4485I
QUEUE
queue
HAS
EXCEEDED
percent
PERCENT
OF
CAPACITY
Explanation:
A
queue
exceeded
the
threshold
value
to
which
it
is
assigned.
This
message
is
initially
issued
when
a
queue
reaches
50%
of
capacity
and
again
when
the
queue
reaches
60%.
This
is
usually
an
indication
that
the
communication
between
the
source/390
object
server
and
the
MVS
Listener
component
on
Windows
is
not
functioning
correctly.
Message
Variables:
queue
-
The
name
of
the
queue
being
reported
upon
percent
-
The
current
percentage
value
being
exceeded,
which
is
either
50
or
60
System
Action:
Processing
continues.
When
the
queue
reaches
100%,
new
records
cannot
be
added
to
the
queue
and
are
discarded.
Administrator
Response:
Check
the
source/390
object
server
job
log
and
look
for
messages
that
indicate
a
problem
with
the
communication.
GTM4486W
QUEUE
queue
HAS
EXCEEDED
percent
PERCENT
OF
CAPACITY
Explanation:
A
queue
exceeded
the
threshold
value
to
which
it
is
assigned.
This
message
is
initially
issued
when
a
queue
reaches
70%
of
capacity
and
again
when
the
queue
reaches
80%
and
90%.
This
is
usually
an
indication
that
the
communication
between
the
source/390
object
server
and
the
MVS
Listener
component
on
Windows
is
not
functioning
correctly.
This
message
indicates
that
the
situation
is
approaching
a
point
where
data
can
be
lost.
Message
Variables:
queue
-
The
name
of
the
queue
being
reported
upon
percent
-
The
current
percentage
value
being
exceeded,
which
is
either
70,
80,
or
90
System
Action:
Processing
continues.
When
the
queue
reaches
100%,
new
records
cannot
be
added
to
the
queue
and
are
discarded.
Administrator
Response:
Check
the
source/390
object
server
job
log
and
look
for
messages
that
indicate
a
problem
with
the
communication.
GTM4495E
SUBSEQUENT
RECORDS
TO
QID=queue
WILL
BE
DISCARDED
Explanation:
This
message
is
issued
subsequent
to
message
GTM4499E,
which
indicates
that
a
queue
became
full.
This
message
indicates
data
will
be
lost.
This
is
usually
an
indication
that
the
communication
between
the
source/390
object
server
and
the
MVS
Listener
component
on
Windows
is
not
functioning
correctly.
Message
Variables:
queue
-
The
name
of
the
queue
being
reported
upon.
System
Action:
No
further
records
can
be
added
to
the
queue
until
the
condition
is
resolved.
Administrator
Response:
Check
the
source/390
object
server
job
log
and
look
for
messages
that
indicate
a
problem
with
the
communication.
Chapter
1.
Source/390
Messages
-
GTM0001I
-
GTM8665E
27
GTM4497E
INVALID
QUEUE
FOUND
ADDR=address,
ALERT=alert,
HEADER=data
Explanation:
When
accessing
a
queue,
the
issuing
address
space
found
that
the
queue
header
was
not
correctly
initialized.
Message
Variables:
address
-
The
address
of
the
queue
header
in
the
data
space
alert
-
The
ALERT
of
the
queue
in
the
data
space
data
-
The
current
data
in
the
queue
header
eye
catcher
System
Action:
Processing
continues,
but
results
are
unpredictable.
Administrator
Response:
Determine
why
the
queue
was
not
initialized.
Typically,
there
was
a
restart
of
the
data
space
and
the
address
space
that
creates
the
required
queue
has
not
yet
been
started.
If
necessary,
contact
IBM
Software
Support.
GTM4498E
INVALID
CELL
ADDRESS
RECEIVED
ADDRESS=address,
ALERT=alert
Explanation:
When
accessing
a
cell
in
a
queue,
the
issuing
address
space
found
that
the
cell
header
was
not
correctly
initialized.
Message
Variables:
address
-
The
address
of
the
cell
header
in
the
data
space
alert
-
The
ALERT
of
the
cell
in
the
data
space
System
Action:
Processing
continues,
but
results
are
unpredictable.
Administrator
Response:
Determine
why
the
queue
was
not
initialized.
Typically,
there
was
a
restart
of
the
data
space
and
the
address
space
that
creates
the
required
queue
has
not
yet
been
started.
If
necessary,
contact
IBM
Software
Support.
GTM4499E
QUEUE
FULL,
ID=queue_name
Q
ADDRESS=queue_header
ALERT=alert,
DATA=address
Explanation:
When
adding
a
cell
to
the
specified
queue,
the
issuing
address
space
found
that
the
queue
was
full.
Message
Variables:
queue_name
-
Name
of
the
queue
that
is
full
queue_header
-
The
address
of
the
queue
header
in
the
data
space
alert
-
The
ALERT
of
the
cell
in
the
data
space
address
-
The
address
of
the
cell
that
was
being
added
System
Action:
No
more
records
can
be
written
to
the
queue
until
a
subsequent
GTM4515I
message
is
issued.
Administrator
Response:
Increase
the
queue
size
for
the
specified
queue.
Start
the
source/390
mainframe
components
again
for
the
queue
size
change
to
become
effective.
If
the
problem
continues,
contact
IBM
Software
Support.
GTM4515I
QUEUE
queue
IS
NOW
AVAILABLE,
RECORDS
LOST
=number
Explanation:
This
message
is
issued
as
a
result
of
a
queue
full
condition
being
resolved.
This
occurs
by
default
when
the
queue
utilization
is
below
40%
of
total
capacity
or
as
a
result
of
a
QUEUE
RESET
command.
Message
Variables:
queue
-
The
name
of
the
queue
being
reported
upon
number
-
The
number
of
records
that
were
discarded
as
a
result
of
the
queue
full
condition
System
Action:
The
queue
full
condition
is
resolved
and
subsequent
records
might
be
added
to
the
queue.
GTM4519E
INVALID
QUEUE
FOUND
ADDR=address,
ALERT=alert,
HEADER=data
Explanation:
When
accessing
a
queue,
the
issuing
address
space
found
that
the
queue
header
was
not
correctly
initialized.
Message
Variables:
address
-
The
address
of
the
queue
header
in
the
data
space
alert
-
The
ALERT
of
the
queue
in
the
data
space
data
-
The
current
data
in
the
queue
header
eye
catcher
System
Action:
Processing
continues,
but
results
are
unpredictable.
Administrator
Response:
Determine
why
the
queue
was
not
initialized.
Typically,
there
was
a
restart
of
the
data
space
and
the
address
space
that
creates
the
required
queue
has
not
yet
been
started.
If
necessary,
contact
IBM
Software
Support.
GTM4522W
INVALID
QUEUE
SIZE
ENCOUNTERED,
TYPE=queue_name,
VALUE=value,
DEFAULTING
TO
default_value
BLOCK(S)
Explanation:
When
initializing
a
queue,
the
issuing
address
space
found
that
the
queue
size
specification
was
not
valid.
Message
Variables:
queue_name
-
The
queue
name
value
-
The
value
input
default_value
-
The
default
value
used
System
Action:
Processing
continues.
The
queue
size
used
to
create
the
queue
is
the
default
value.
Administrator
Response:
Correct
the
parameter
value
for
the
specified
queue
size.
If
necessary,
contact
IBM
Software
Support.
28
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
GTM4538E
STORAGE
OBTAIN
FAILED,
QUEUE
NOT
ALLOCATED,
RC=return_code
Explanation:
When
initializing
a
queue,
a
GETMAIN
macro
for
the
queue
storage
failed.
Message
Variables:
return_code
-
The
return
code
from
STORAGE
OBTAIN
System
Action:
Processing
continues,
but
results
are
unpredictable.
Administrator
Response:
Determine
why
the
GETMAIN
macro
failed.
If
necessary,
increase
the
region
size
of
the
data
space
or
reduce
the
queue
size.
Contact
IBM
Software
Support.
GTM4539E
INVALID
QUEUE
TYPE
REQUESTED,
QTYPE=queue_type
Explanation:
When
initializing
a
queue,
the
ACC1QCRE
program
was
called
with
an
queue
type
that
was
not
valid.
Message
Variables:
queue_type
-
The
queue
type
indicator
that
was
passed.
System
Action:
Processing
continues,
but
results
are
unpredictable.
Administrator
Response:
This
is
an
internal
error.
Contact
IBM
Software
Support.
GTM4559E
INVALID
NULL
DATA
LENGTH
SUPPLIED
Explanation:
A
call
was
made
to
the
ACC1QLPT
program
with
a
zero
length
data
element.
System
Action:
Processing
continues,
but
results
are
unpredictable.
Administrator
Response:
This
is
an
internal
error.
Contact
IBM
Software
Support.
GTM4575E
BUFFER
STORAGE
UNAVAILABLE,
LENGTH
REQUESTED=length
Explanation:
While
retrieving
a
record
from
a
queue,
the
source/390
queue
get
program
was
unable
to
obtain
sufficient
storage
to
hold
the
record.
Message
Variables:
length
-
The
length
of
the
storage
requested
System
Action:
Processing
continues,
but
results
are
unpredictable.
Administrator
Response:
The
error
indicates
that
the
source/390
object
pump
exhausted
the
virtual
storage
to
which
it
is
available.
Use
the
region
parameter
of
the
EXEC
JCL
card
to
increase
the
amount
of
virtual
storage
available.
If
the
problem
continues,
contact
IBM
Software
Support.
GTM4576E
CONTINUATION
CELL
NULL,
CELLADDR=cell_address,
QADDR=queue_address,
SEQUENCE
DATA=cell_size
Explanation:
While
retrieving
a
record
from
a
queue
that
spanned
multiple
cells
within
the
data
space,
the
source/390
queue
get
program
found
that
the
current
cell
indicated
there
was
a
continuation
cell,
but
the
next
cell
address
was
zero.
Message
Variables:
cell_address
-
The
address
of
the
cell
in
the
data
space
queue_address
-
The
address
of
the
queue
in
the
data
space
cell_size
-
The
cell
size
field
from
the
last
cell
processed
System
Action:
Processing
continues,
but
results
are
unpredictable.
Administrator
Response:
This
is
an
internal
error.
Contact
IBM
Software
Support.
GTM4577E
CELL
LENGTH
ERROR,
CELLADDR=cell_address
QADDR=queue_address,
SEQUENCE
DATA=field,
LENGTH=length
Explanation:
While
retrieving
a
record
from
a
queue
that
spanned
multiple
cells
within
the
data
space,
the
source/390
queue
get
program
found
a
cell
that
had
an
incorrect
data
length
specified.
Message
Variables:
cell_address
-
The
address
of
the
cell
in
the
data
space
queue_address
-
The
address
of
the
queue
in
the
data
space
field
-
The
sequence
field
from
the
cell
length
-
The
length
of
data
within
the
cell
System
Action:
Processing
continues,
but
results
are
unpredictable.
Administrator
Response:
This
is
an
internal
error.
Contact
IBM
Software
Support.
GTM4578E
CELL
OUT
OF
SEQUENCE,
CELLADDR=cell_address
QADDR=queue_address
SEQUENCE
DATA=field
EXPECTING=seq_number
Explanation:
While
retrieving
a
record
from
a
queue
that
spanned
multiple
cells
within
the
data
space,
the
source/390
queue
get
program
found
a
cell
that
had
an
incorrect
sequence
number.
Message
Variables:
cell_address
-
The
address
of
the
cell
in
the
data
space
queue_address
-
The
address
of
the
queue
in
the
data
space
Chapter
1.
Source/390
Messages
-
GTM0001I
-
GTM8665E
29
field
-
The
sequence
field
from
the
cell
seq_number
-
The
expected
sequence
number
System
Action:
Processing
continues,
but
results
are
unpredictable.
Administrator
Response:
This
is
an
internal
error.
Contact
IBM
Software
Support.
GTM4579E
INVALID
CELL
ADDRESS
FOUND,
CELLADDR=cell_address
QADDR=queue_address
Explanation:
While
retrieving
a
record
from
a
queue
that
spanned
multiple
cells
within
the
data
space,
the
source/390
queue
get
program
found
a
cell
that
had
an
incorrect
header.
Message
Variables:
cell_address
-
The
address
of
the
cell
in
the
data
space
queue_address
-
The
address
of
the
queue
in
the
data
space
System
Action:
Processing
continues,
but
results
are
unpredictable.
Administrator
Response:
This
is
an
internal
error.
Contact
IBM
Software
Support.
GTM4600I
EXTENDED
RECOVERY
ENVIRONMENT
ESTABLISHED
Explanation:
The
issuing
address
space
successfully
created
the
automatic
recovery
environment.
System
Action:
Processing
continues.
GTM4601I
STANDBY
ADDRESS
SPACE
WAITING
FOR
TAKEOVER
FROM
address_space
Explanation:
The
issuing
address
space
detected
that
it
is
running
as
a
backup
to
the
current
active
address
space
and
is
standing
by
to
take
over
processing
if
the
active
address
space
should
fail.
Message
Variables:
address_space
-
The
name
of
the
matching
active
address
space
System
Action:
Initialization
of
the
standby
address
space
waits
for
either
a
takeover
or
a
shutdown
request.
GTM4602I
SHUTDOWN
OF
STANDBY
ADDRESS
SPACE
REQUESTED
Explanation:
The
active
address
space
is
ending
and
a
request
was
sent
for
the
standby
address
space
to
shutdown.
System
Action:
The
standby
address
space
shuts
down.
GTM4603I
TAKEOVER
BY
STANDBY
ADDRESS
SPACE
REQUESTED
Explanation:
The
active
address
space
requested
that
the
standby
address
space
take
over
its
operation.
This
can
be
initiated
either
by
an
operator
command
or
automatically
if
the
active
address
space
abends.
System
Action:
The
standby
address
space
resumes
initialization
and
assumes
the
role
of
the
primary
address
space.
Administrator
Response:
Determine
if
this
takeover
should
have
occurred.
If
the
original
active
address
space
abended,
determine
why.
If
necessary,
contact
IBM
Software
Support.
GTM4604I
SWITCH
TO
STANDBY
ADDRESS
SPACE
REQUESTED
Explanation:
The
active
address
space
requested
that
the
standby
address
space
take
over
its
operation.
This
can
be
initiated
by
an
operator
command.
System
Action:
The
standby
address
space
resumes
initialization
and
assumes
the
role
of
the
primary
address
space.
The
primary
address
space
shuts
down.
GTM4605I
DUPLICATE
STANDBY
ADDRESS
SPACE
standby_name
IS
CURRENTLY
WAITING
FOR
ADDRESS
SPACE
active_name
Explanation:
A
second
standby
address
space
started.
Only
one
standby
address
space
can
be
active.
The
second
instance
ends.
Message
Variables:
standby_name
-
The
current
standby
address
space
active_name
-
The
current
active
address
space
name
System
Action:
The
address
space
shuts
down.
Administrator
Response:
Determine
why
the
second
standby
address
space
was
started.
GTM4608E
UNABLE
TO
LOAD
RESOURCE
MANAGER
INTO
ECSA
RC=return_code
Explanation:
The
issuing
address
space
was
unable
to
load
the
extended
recovery
resource
manager,
AOPXRRSM,
into
Extended
Common
System
Area
(ECSA)
storage.
Message
Variables:
return_code
-
The
return
code
from
the
LOAD
macro
System
Action:
The
address
space
shuts
down.
Administrator
Response:
Determine
why
the
module
cannot
be
loaded.
Validate
that
the
STEPLIB
DD
concatenation
contains
the
SGTMMODS
library.
This
might
be
an
installation
problem.
If
necessary,
contact
IBM
Software
Support.
30
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
GTM4609E
NAME
TOKEN
CREATE
FOR
STANDBY
ADDRESS
SPACE
FAILED.
RC=return_code
Explanation:
The
issuing
address
space
was
unable
to
create
the
name
token
associated
with
the
address
space
when
in
standby
mode.
Message
Variables:
return_code
-
The
return
code
from
the
call
to
the
IEANTCR
macro
System
Action:
The
address
space
shuts
down.
Administrator
Response:
Determine
why
the
call
to
the
IEANTCR
macro
failed.
Refer
to
the
services
manual
in
the
z/OS
MVS
library.
If
necessary,
contact
IBM
Software
Support.
GTM4610E
INVALID
POST
CODE
RECEIVED,
CODE=return_code
Explanation:
The
standby
recovery
manager
in
the
issuing
address
space
was
unable
to
determine
the
reason
for
the
request.
The
action
shutdowns
by
default.
Message
Variables:
return_code
-
The
value
from
the
ECB
on
which
the
recovery
manager
was
waiting
System
Action:
Processing
continues,
but
results
are
unpredictable.
Administrator
Response:
This
is
an
internal
error.
Contact
IBM
Software
Support.
GTM4611E
NAME
TOKEN
CREATE
FOR
PRIMARY
ADDRESS
SPACE
FAILED.
RC=return_code
Explanation:
The
issuing
address
space
was
unable
to
create
the
name
token
associated
with
the
address
space
when
in
primary
mode.
Message
Variables:
return_code
-
The
return
code
from
the
call
to
the
IEANTCR
macro
System
Action:
The
address
space
shuts
down.
Administrator
Response:
Determine
why
the
call
to
the
IEANTCR
macro
failed.
Refer
to
the
services
manual
in
the
z/OS
MVS
library.
If
necessary,
contact
IBM
Software
Support.
GTM4612E
NAME
TOKEN
CREATE
FOR
RESOURCE
MANAGER
FAILED.
RC=return_code
Explanation:
The
issuing
address
space
was
unable
to
create
the
name
token
associated
with
the
recovery
resource
manager
for
the
address
space.
Message
Variables:
return_code
-
The
return
code
from
the
call
to
the
IEANTCR
macro
System
Action:
The
address
space
shuts
down.
Administrator
Response:
Determine
why
the
call
to
the
IEANTCR
macro
failed.
Refer
to
the
services
manual
in
the
z/OS
MVS
library.
If
necessary,
contact
IBM
Software
Support.
GTM4613E
RESOURCE
MANAGER
CREATE
FAILED.
RC=return_code
Explanation:
The
issuing
address
space
was
unable
to
create
the
recovery
resource
manager
for
the
address
space.
Message
Variables:
return_code
-
The
return
code
from
the
RESMGR
ADD
macro
System
Action:
The
address
space
shuts
down.
Administrator
Response:
Determine
why
the
resource
manager
add
macro
failed.
Refer
to
the
services
manual
in
the
z/OS
MVS
library.
If
necessary,
contact
IBM
Software
Support.
GTM4614E
UNABLE
TO
LOAD
RESOURCE
MANAGER
INTO
ECSA
Explanation:
The
issuing
address
space
was
unable
to
load
the
recovery
resource
manager
into
Extended
Common
System
Area
(ECSA).
System
Action:
The
address
space
shuts
down.
Administrator
Response:
Determine
why
the
resource
manager
load
failed.
If
necessary,
contact
IBM
Software
Support.
GTM4615E
UNABLE
TO
OBTAIN
ECSA
STORAGE
FOR
RESOURCE
MANAGER
Explanation:
The
issuing
address
space
was
unable
to
obtain
storage
in
Extended
Common
System
Area
(ECSA)
to
hold
the
recovery
resource
manager.
System
Action:
The
address
space
shuts
down.
Administrator
Response:
Determine
why
the
resource
manager
load
failed.
If
necessary,
contact
IBM
Software
Support.
GTM4616E
AMODE
INVALID
FOR
MODULE
AOPXRRSM
Explanation:
The
recovery
manager
for
the
issuing
address
space
determined
that
the
resource
recovery
manager
module,
AOPXRRSM,
is
not
link-edited
as
AMODE
31.
System
Action:
The
address
space
shuts
down.
Administrator
Response:
Determine
why
the
AOPXRRSM
module
is
link
edited
incorrectly.
If
necessary,
contact
IBM
Software
Support.
Chapter
1.
Source/390
Messages
-
GTM0001I
-
GTM8665E
31
GTM4617E
UNABLE
TO
LOAD
RESOURCE
MANAGER
Explanation:
The
issuing
address
space
was
unable
to
load
the
AOPXRRSM
resource
recovery
manager
module.
System
Action:
The
address
space
shuts
down.
Administrator
Response:
Determine
why
the
AOPXRRSM
module
could
not
be
loaded.
If
necessary,
contact
IBM
Software
Support.
GTM4618E
LOAD
OF
MODULE
module_name
FAILED,
RC=return_code
Explanation:
The
issuing
address
space
was
unable
to
load
the
specified
module.
Message
Variables:
module_name
-
The
module
name
return_code
-
The
return
code
from
the
LOAD
macro
System
Action:
The
address
space
shuts
down.
Administrator
Response:
Determine
why
the
specified
module
could
not
be
loaded.
If
necessary,
contact
IBM
Software
Support.
GTM4619E
UNABLE
TO
OBTAIN
WORKING
STORAGE
Explanation:
The
recovery
manager
in
the
issuing
address
space
was
unable
to
obtain
working
storage.
System
Action:
The
address
space
shuts
down.
Administrator
Response:
The
error
indicates
that
the
source/390
object
pump
exhausted
the
virtual
storage
to
which
it
is
available.
Use
the
region
parameter
of
the
EXEC
JCL
card
to
increase
the
amount
of
virtual
storage
available.
If
the
problem
continues,
contact
IBM
Software
Support.
GTM4620I
EXTENDED
RECOVERY
ENVIRONMENT
SUCCESSFULLY
REMOVED
Explanation:
The
recovery
manager
successfully
ended.
System
Action:
The
address
space
shuts
down.
GTM4628E
LOAD
OF
MODULE
module_name
FAILED,
RC=return_code
Explanation:
The
issuing
address
space
was
unable
to
load
the
specified
module.
Message
Variables:
module_name
-
The
module
name
return_code
-
The
return
code
from
the
LOAD
macro
System
Action:
The
address
space
shuts
down.
Administrator
Response:
Determine
why
the
specified
module
could
not
be
loaded.
If
necessary,
contact
IBM
Software
Support.
GTM4629E
UNABLE
TO
OBTAIN
WORKING
STORAGE
Explanation:
The
recovery
manager
shutdown
module
in
the
issuing
address
space
was
unable
to
obtain
working
storage.
System
Action:
The
address
space
shuts
down.
Administrator
Response:
The
error
indicates
that
the
source/390
object
pump
exhausted
the
virtual
storage
to
which
it
is
available.
Use
the
region
parameter
of
the
EXEC
JCL
card
to
increase
the
amount
of
virtual
storage
available.
If
the
problem
continues,
contact
IBM
Software
Support.
GTM4996E
name
NOT
LOADED,
TBSM
TERMINATING
Explanation:
The
issuing
address
space
was
unable
to
load
the
specified
message
module.
Message
Variables:
name
-
The
name
of
the
message
module
that
was
not
loaded
System
Action:
The
address
space
shuts
down.
Administrator
Response:
Determine
why
the
specified
message
module
could
not
be
loaded.
Validate
that
the
SGTMMODS
library
is
in
the
STEPLIB
concatenation.
If
necessary,
contact
IBM
Software
Support.
GTM4997W
FREEMAIN
FAILED,
MODULE=ACC1WTO
Explanation:
A
FREEMAIN
macro
failed
in
the
ACC1WTO
module.
System
Action:
Processing
continues.
Administrator
Response:
Determine
why
the
FREEMAIN
macro
failed.
If
necessary,
contact
IBM
Software
Support.
GTM4998W
MESSAGE
number
IS
MISSING
Explanation:
The
specified
message
number
was
not
found
in
the
message
module.
Message
Variables:
number
-
The
message
number
that
was
not
found
System
Action:
Processing
continues.
Administrator
Response:
This
is
an
internal
error.
Contact
IBM
Software
Support.
32
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
GTM4999W
MESSAGE
number
IS
INVALID
Explanation:
The
specified
message
number
is
not
numeric.
Message
Variables:
number
-
The
message
number
that
was
not
valid
System
Action:
Processing
continues.
Administrator
Response:
This
is
an
internal
error.
Contact
IBM
Software
Support.
GTM5000I
DATA
SPACE
INITIALIZATION
STARTING
Explanation:
Data
space
initialization
is
starting.
System
Action:
Processing
continues.
GTM5002I
PROCESSING
PARMLIB
MEMBER:
name
Explanation:
The
data
space
is
processing
the
specified
initialization
member
from
the
parameter
data
set.
Message
Variables:
name
-
The
member
name
System
Action:
Processing
continues.
GTM5005I
INVALID
PARM
PASSED,
PROCESSING
CONTINUING,
PARM=parameter
Explanation:
The
specified
parameter
for
the
data
space
was
not
valid.
Message
Variables:
parameter
-
The
parameter
in
error
System
Action:
Processing
continues.
Administrator
Response:
Correct
or
remove
the
parameter
that
was
not
valid.
Refer
to
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide
for
more
information.
If
necessary,
contact
IBM
Software
Support.
GTM5010I
TBSM
data_space
INITIALIZATION
COMPLETE
Explanation:
The
specified
address
space
completed
its
initialization.
Message
Variables:
data_space
-
Specifies
the
data
space
or
source/390
object
server
System
Action:
Processing
continues.
GTM5030I
MODIFY
INTERFACE
ESTABLISHED,
CONSOLE
COMMUNICATION
AVAILABLE
Explanation:
The
data
space
is
ready
to
accept
modify
and
stop
commands.
System
Action:
Processing
continues.
GTM5031I
COMMAND
ACCEPTED:
text
Explanation:
The
command
entered
was
accepted.
Message
Variables:
text
-
The
command
text
System
Action:
Processing
continues.
GTM5040I
OBJECT
SERVER
TERMINATION
COMPLETE,
RC=return_code
Explanation:
The
data
space
ended
with
the
specified
return
code.
Message
Variables:
return_code
-
The
return
code
System
Action:
The
source/390
data
space
shuts
down.
GTM5084E
ADDRESS
SPACE
NOT
APF
AUTHORIZED,
DATA
SPACE
SERVER
TERMINATING
Explanation:
The
data
space
is
not
running
APF
authorized.
Execution
ends.
System
Action:
The
source/390
data
space
shuts
down.
Administrator
Response:
Check
that
all
the
load
libraries
in
the
STEPLIB
concatenation
are
APF
authorized.
If
necessary,
contact
IBM
Software
Support.
GTM5087E
MODULE:
module_name
NOT
LOADED,
OBJECT
SERVER
TERMINATING
Explanation:
The
specified
module
could
not
be
loaded.
Message
Variables:
module_name
-
The
module
name
System
Action:
The
source/390
data
space
shuts
down.
Administrator
Response:
Determine
why
the
module
could
not
be
loaded.
Validate
that
the
SGTMMODS
library
is
in
the
STEPLIB
concatenation.
If
necessary,
contact
IBM
Software
Support.
GTM5088E
RETURN
FROM
CIB
FREE,
R15=return_code
Explanation:
The
return
code
from
the
QEDIT
macro
to
release
the
CIB
associated
with
a
MODIFY
or
STOP
command
was
not
zero.
Execution
continues.
Message
Variables:
return_code
-
The
return
code
from
the
QEDIT
macro
System
Action:
Processing
continues.
Administrator
Response:
Determine
why
the
QEDIT
macro
issued
the
return
code.
Refer
to
the
services
Chapter
1.
Source/390
Messages
-
GTM0001I
-
GTM8665E
33
manual
in
the
z/OS
MVS
library.
If
necessary,
contact
IBM
Software
Support.
GTM5089E
OPEN
FAILED
FOR
ACC1PARM,
OBJECT
SERVER
TERMINATING,
RETURN
CODE
(15)=return_code
Explanation:
The
OPEN
macro
of
the
ACC1PARM
DD
failed.
Message
Variables:
return_code
-
The
return
code
from
the
OPEN
macro
System
Action:
The
source/390
data
space
shuts
down.
Administrator
Response:
Determine
why
the
OPEN
macro
failed.
Refer
to
the
DFSMS/MVS
Macro
Instructions
for
Data
Sets
document.
If
necessary,
contact
IBM
Software
Support.
GTM5090E
INSUFFICIENT
VIRTUAL
STORAGE,
MEMBER=name,
TBSM
TERMINATING,
RETURN
CODE
(R15)=return_code,
REASON
CODE
(R0)=reason_code
Explanation:
While
processing
the
ACC1PARM
parameter
library,
the
FIND
macro
returned
an
error.
Message
Variables:
name
-
The
member
name
being
processed
return_code
-
The
return
code
from
the
FIND
macro
reason_code
-
The
reason
code
from
the
FIND
macro
System
Action:
The
source/390
data
space
shuts
down.
Administrator
Response:
Determine
why
the
FIND
macro
failed.
Refer
to
the
DFSMS/MVS
Macro
Instructions
for
Data
Sets
document.
If
necessary,
contact
IBM
Software
Support.
GTM5091E
PERMANENT
I/O
ERROR
IN
PARM
DATASET,
TBSM
TERMINATING,
RETURN
CODE
(R15)=return_code,
REASON
CODE
(R0)=reason_code
Explanation:
While
processing
the
ACC1PARM
parameter
library,
the
FIND
macro
returned
an
error.
Message
Variables:
return_code
-
The
return
code
from
the
FIND
macro
reason_code
-
The
reason
code
from
the
FIND
macro
System
Action:
Processing
continues.
Administrator
Response:
Determine
why
the
FIND
macro
failed.
Refer
to
the
DFSMS/MVS
Macro
Instructions
for
Data
Sets
document.
If
necessary,
contact
IBM
Software
Support.
GTM5092E
FIND
MACRO
FAILED
FOR
MEMBER
member_name,
DATA
SPACE
SERVER
TERMINATING,
RETURN
CODE
(15)=return_code,
REASON
CODE
(0)=reason_code
Explanation:
While
processing
the
ACC1PARM
parameter
library,
the
FIND
macro
returned
an
error.
Message
Variables:
member_name
-
The
member
name
being
processed
return_code
-
The
return
code
from
the
FIND
macro
reason_code
-
The
reason
code
from
the
FIND
macro
System
Action:
The
source/390
data
space
shuts
down.
Administrator
Response:
Determine
why
the
FIND
macro
failed.
Refer
to
the
DFSMS/MVS
Macro
Instructions
for
Data
Sets
document.
If
necessary,
contact
IBM
Software
Support.
GTM5093E
PARM
MEMBER
member_name
NOT
FOUND,
OBJECT
SERVER
TERMINATING,
R15=return_code,
R0=reason_code
Explanation:
While
processing
the
ACC1PARM
parameter
library,
the
FIND
macro
could
not
locate
the
indicated
member
name.
Message
Variables:
member_name
-
The
member
name
being
processed
return_code
-
The
return
code
from
the
FIND
macro
reason_code
-
The
reason
code
from
the
FIND
macro
System
Action:
The
source/390
data
space
shuts
down.
Administrator
Response:
Determine
why
the
member
name
was
not
found.
Verify
that
the
value
specified
on
the
PARM
statement
for
the
GTMDSPC
program
is
the
name
of
a
member
in
the
library
pointed
to
by
the
ACC1PARM
DD
statement.
Refer
to
the
DFSMS/MVS
Macro
Instructions
for
Data
Sets
document.
If
necessary,
contact
IBM
Software
Support.
GTM5094E
TIOT
ADDRESS
INVALID,
ADDRESS=address,
OBJECT
SERVER
TERMINATING
Explanation:
The
TIOT
address
returned
by
the
EXTRACT
macro
was
zero.
Message
Variables:
address
-
The
address
returned
System
Action:
The
source/390
data
space
shuts
down.
Administrator
Response:
Contact
IBM
Software
Support.
34
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
GTM5095E
MODULE
module_name
NOT
LOADED
TBSM
TERMINATING
Explanation:
The
specified
module
could
not
be
loaded.
The
address
space
stops.
Message
Variables:
module_name
-
The
module
name
System
Action:
The
source/390
data
space
shuts
down.
Administrator
Response:
Determine
why
the
module
could
not
be
loaded.
Validate
that
the
SGTMMODS
library
is
contained
in
the
STEPLIB
concatenation.
If
necessary,
contact
IBM
Software
Support.
GTM5096E
ACC1PARM
DD
STATEMENT
MISSING
OBJECT
SERVER
TERMINATING
Explanation:
The
ACC1PARM
parameter
library
DD
is
missing.
The
address
space
ends.
System
Action:
The
source/390
data
space
shuts
down.
Administrator
Response:
Determine
why
the
ACC1PARM
DD
could
not
be
located.
If
necessary,
contact
IBM
Software
Support.
GTM5098W
DEFAULT
PARM
MEMBER
NOT
ENTERED,
DEFAULTING
TO
MEMBER:
SYSIN
Explanation:
A
member
name
parameter
was
not
entered
on
the
data
space
EXEC
JCL
statement.
The
default
member
name
of
SYSIN
is
used.
System
Action:
The
source/390
data
space
shuts
down.
Administrator
Response:
Specify
a
member
name
on
the
EXEC
JCL
statement
for
the
data
space
if
you
want
to
use
a
member
name
other
than
SYSIN
for
the
data
space
startup
parameters.
GTM5099W
PARM
TOO
LONG,
FORCING
LENGTH
OF
8
Explanation:
A
member
name
parameter
on
the
EXEC
JCL
statement
was
longer
than
eight
characters.
System
Action:
The
parameter
is
truncated
to
eight
characters
Administrator
Response:
Correct
the
member
name
parameter
on
the
EXEC
JCL
statement
in
the
data
space
startup
JCL.
GTM5101I
DATA
SPACE
CREATED,
SIZE=size,
ORIGIN=address
Explanation:
The
data
space
was
successfully
created.
Message
Variables:
size
-
The
size
of
the
data
space
in
bytes
address
-
The
original
address
of
the
data
space
System
Action:
Processing
continues.
GTM5114E
DATASPACE
SIZE
NOT
ENTERED,
DEFAULTING
TO
size
BYTES
Explanation:
The
data
space
size
was
not
specified
in
the
input
parameters.
Message
Variables:
size
-
The
default
size
used
for
the
data
space
System
Action:
The
default
size
is
used.
Administrator
Response:
Specify
the
data
space
size
(in
bytes)
in
the
data
space
input
parameters
if
you
want
to
use
a
value
other
than
the
default
size.
Refer
to
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide
for
more
information.
GTM5115E
INVALID
DATASPACE
SIZE
ENCOUNTERED,
VALUE=size,
DEFAULTING
TO
default_size
BYTES
Explanation:
The
data
space
size
specified
in
the
input
parameters
is
not
valid.
The
default
value
is
used.
Message
Variables:
size
-
The
data
space
size
entered
default_size
-
The
default
size
used
for
the
data
space
System
Action:
The
default
size
is
used.
Administrator
Response:
Correct
the
data
space
size
entered
in
the
input
parameters.
Refer
to
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide
for
more
information.
GTM5116E
DATASPACE
CREATE
FAILED,
RC=return_code,
SERVER
TERMINATING
Explanation:
The
DSPSERV
CREATE
macro
used
to
create
the
data
space
issued
a
return
code
other
than
zero.
Message
Variables:
return_code
-
The
return
code
from
DSPSERV
CREATE
macro
System
Action:
The
source/390
data
space
shuts
down.
Administrator
Response:
Determine
why
the
data
space
create
macro
failed.
Refer
to
the
services
manual
in
the
z/OS
MVS
library.
If
necessary,
contact
IBM
Software
Support.
Chapter
1.
Source/390
Messages
-
GTM0001I
-
GTM8665E
35
GTM5117E
ALESERV
FAILED,
RC=return_code,
OBJECT
SERVER
TERMINATING
Explanation:
The
ALESERV
ADD
macro
used
to
create
the
data
space
issued
a
return
code
other
than
zero.
Message
Variables:
return_code
-
The
return
code
from
the
ALESERV
ADD
macro
System
Action:
The
source/390
data
space
shuts
down.
Administrator
Response:
Determine
why
the
macro
call
failed.
Refer
to
the
services
manual
in
the
z/OS
MVS
library.
If
necessary,
contact
IBM
Software
Support.
GTM5118E
NAME/TOKEN
CREATE
FAILED,
RC=return_code
OBJECT
SERVER
TERMINATING
Explanation:
The
call
to
the
IEANTCR
macro
to
create
the
name
token
associated
with
the
data
space
failed.
Message
Variables:
return_code
-
The
return
code
from
the
call
to
the
IEANTCR
name
token
create
routine
System
Action:
The
source/390
data
space
shuts
down.
Administrator
Response:
Determine
why
the
call
to
the
IEANTCR
macro
failed.
Refer
to
the
services
manual
in
the
z/OS
MVS
library.
If
necessary,
contact
IBM
Software
Support.
GTM5119E
SYSEVENT
FAILED,
RC=return_code,
OBJECT
SERVER
TERMINATING
Explanation:
The
SYSEVENT
TRANSWAP
macro
issued
a
return
code
other
than
zero
during
an
attempt
to
be
in
a
non-swappable
state.
Message
Variables:
return_code
-
The
return
code
from
the
SYSEVENT
macro
System
Action:
The
source/390
data
space
shuts
down.
Administrator
Response:
Determine
why
the
call
to
the
SYSEVENT
macro
failed.
Refer
to
the
services
manual
in
the
z/OS
MVS
library.
If
necessary,
contact
IBM
Software
Support.
GTM5120I
OBJECT
SERVER
DISCONNECTED
FROM
DATASPACE
Explanation:
The
data
space
address
space
disconnected
from
the
data
space.
This
message
is
issued
during
the
shutdown
of
the
source/390
object
server.
System
Action:
The
source/390
data
space
shuts
down.
GTM5121I
DATA
SPACE
DELETED
Explanation:
The
data
space
address
space
deleted
the
data
space.
System
Action:
The
source/390
data
space
shuts
down.
GTM5127E
DATA
SPACE
NOT
DELETED,
RC=return_code,
DATASPACE
WILL
BE
DELETED
AT
ADDRESS
SPACE
TERMINATION,
SHUTDOWN
CONTINUING
Explanation:
The
data
space
delete
macro
failed.
Message
Variables:
return_code
-
The
return
code
from
the
DSPSERV
DELETE
macro
System
Action:
The
source/390
data
space
shuts
down.
Administrator
Response:
Determine
why
the
data
space
delete
macro
failed.
Refer
to
the
services
manual
in
the
z/OS
MVS
library.
If
necessary,
contact
IBM
Software
Support.
GTM5128E
ALESERV
DELETE
FAILED,
SERVER
STILL
CONNECTED,
RC=return_code,
SHUTDOWN
CONTINUING
Explanation:
While
deleting
the
data
space,
the
ALESERV
DELETE
macro
issued
a
return
code
other
than
zero.
Message
Variables:
return_code
-
The
return
code
from
ALESERV
DELETE
macro
System
Action:
The
source/390
data
space
shuts
down.
Administrator
Response:
Determine
why
the
data
space
delete
routine
failed.
Refer
to
the
services
manual
in
the
z/OS
MVS
library.
If
necessary,
contact
IBM
Software
Support.
GTM5129E
CLIENT
jobname
STILL
ACTIVE,
OBJECT
SERVER
WILL
NOT
SHUT
DOWN
UNTIL
ALL
CLIENTS
ARE
TERMINATED
Explanation:
An
attempt
was
made
to
stop
the
data
space
while
either
the
source/390
object
server
or
source/390
object
pump
was
still
active.
Message
Variables:
jobname
-
The
job
name
of
address
space
that
was
found
active
System
Action:
The
shutdown
request
is
ignored.
Administrator
Response:
Ensure
that
the
source/390
object
pump
and
object
server
are
both
stopped
before
attempting
to
shut
down
the
data
space
address
space.
36
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
GTM5156E
CELL
POOL
EXTEND
FAILED,
RC=return_code
Explanation:
The
call
to
create
the
cell
pool
extent
within
the
data
space
failed.
Message
Variables:
return_code
-
The
return
code
from
the
call
to
the
CSRPEXP
macro
System
Action:
The
source/390
data
space
shuts
down.
Administrator
Response:
Determine
why
the
call
to
the
CSRPEXP
macro
failed.
Refer
to
the
services
manual
in
the
z/OS
MVS
library.
If
necessary,
contact
IBM
Software
Support.
GTM5157E
INVALID
QUEUE
SIZE
ENCOUNTERED,
TYPE=queue_type
VALUE=value,
DEFAULTING
TO
default_value
BLOCKS
Explanation:
The
queue
size
parameter
for
the
specified
queue
is
not
valid.
Message
Variables:
queue_type-
The
queue
type
value-
The
value
entered
default_value
-
The
default
value
used
System
Action:
Processing
continues.
The
default
value
is
used.
Administrator
Response:
Correct
the
queue
size
parameter
for
the
specified
queue.
Refer
to
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide
for
more
information
about
source/390
object
server
startup
parameters.
If
necessary,
contact
IBM
Software
Support.
GTM5158W
QUEUE
SIZE
NOT
ENTERED,
TYPE=queue_type
DEFAULTING
TO
default_value
BLOCKS
Explanation:
A
queue
size
parameter
was
not
entered
for
the
specified
queue.
The
default
size
is
entered.
Message
Variables:
queue_type
-
The
queue
type
default_value
-
The
default
value
used
System
Action:
Processing
continues.
The
default
value
is
used.
Administrator
Response:
Correct
the
queue
size
parameter
for
the
specified
queue.
Refer
to
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide
for
more
information
about
source/390
object
server
startup
parameters.
If
necessary,
contact
IBM
Software
Support.
GTM5159E
CELL
POOL
CREATE
FAILED,
RC=return_code
Explanation:
The
call
to
the
CSRPBLD
macro
to
create
the
cell
pool
failed.
Message
Variables:
return_code
-
The
return
code
from
the
call
to
the
CSRPBLD
macro
System
Action:
The
source/390
data
space
shuts
down.
Administrator
Response:
Determine
why
the
call
to
the
CSRPBLD
macro
failed.
Refer
to
the
services
manual
in
the
z/OS
MVS
library.
If
necessary,
contact
IBM
Software
Support.
GTM5161I
IPL
SENSED
Explanation:
This
is
the
first
time
the
address
space
ran
with
this
ACC1ID
DD
card
setting
since
the
last
IPL.
System
Action:
Processing
continues.
GTM5175E
NAME/TOKEN
CREATE
FAILED,
RC=return_code
TOKEN=name
PROCESSING
CONTINUING,
MULTIPLE
LINKAGE
INDEXES
WILL
BE
CREATED
Explanation:
The
call
to
the
IEANTCR
macro
to
create
the
name
token
associated
with
the
linkage
index
for
the
data
space
failed.
Because
the
linkage
index
information
could
not
be
saved,
each
execution
of
the
data
space
will
use
an
additional
linkage
index
from
those
available.
Message
Variables:
return_code
-
The
return
code
from
the
call
to
the
IEANTCR
macro
name
-
The
token
name
that
was
being
created
System
Action:
Processing
continues.
Administrator
Response:
Determine
why
the
call
to
the
IEANTCR
macro
failed.
Refer
to
the
services
manual
in
the
z/OS
MVS
library.
If
necessary,
contact
IBM
Software
Support.
GTM5176E
LXRES
FAILED,
RC=
return_code,
OBJECT
SERVER
TERMINATING
Explanation:
The
system
was
unable
to
create
a
system
linkage
index
for
the
data
space.
Message
Variables:
return_code
-
The
return
code
from
the
LXRES
macro
System
Action:
The
source/390
object
server
shuts
down.
Administrator
Response:
Determine
why
the
LXRES
macro
failed.
Refer
to
the
services
manual
in
the
z/OS
MVS
library.
If
necessary,
contact
IBM
Software
Support.
Chapter
1.
Source/390
Messages
-
GTM0001I
-
GTM8665E
37
GTM5177E
AXSET
FAILED,
RC=return_code,
OBJECT
SERVER
TERMINATING
Explanation:
The
system
was
unable
to
set
the
authorization
index
for
the
data
space.
Message
Variables:
return_code
-
The
return
code
from
the
AXSET
macro
System
Action:
The
source/390
object
server
shuts
down.
Administrator
Response:
Determine
why
the
AXSET
macro
failed.
Refer
to
the
services
manual
in
the
z/OS
MVS
library.
If
necessary,
contact
IBM
Software
Support.
GTM5178E
ETCON
FAILED,
RC=return_code,
OBJECT
SERVER
TERMINATING
Explanation:
The
system
was
unable
to
connect
the
entry
table
for
the
data
space
to
the
linkage
index.
Message
Variables:
return_code
-
The
return
code
from
the
ETCON
macro
System
Action:
The
source/390
object
server
shuts
down.
Administrator
Response:
Determine
why
the
ETCON
macro
failed.
Refer
to
the
services
manual
in
the
z/OS
MVS
library.
If
necessary,
contact
IBM
Software
Support.
GTM5179E
ETCRE
FAILED,
RC=return_code,
OBJECT
SERVER
TERMINATING
Explanation:
The
system
was
unable
to
create
the
entry
table
for
the
data
space.
Message
Variables:
return_code
-
The
return
code
from
the
ETCRE
macro
System
Action:
The
source/390
object
server
shuts
down.
Administrator
Response:
Determine
why
the
ETCRE
macro
failed.
Refer
to
the
services
manual
in
the
z/OS
MVS
library.
If
necessary,
contact
IBM
Software
Support.
GTM5199E
LATCH
SET
CREATE
FAILED,
RC=return_code,
OBJECT
SERVER
TERMINATING
Explanation:
The
system
was
unable
to
create
the
latch
set
associated
with
the
cells
in
the
data
space.
Message
Variables:
return_code
-
The
return
code
from
the
call
to
the
ISGLCRT
macro
System
Action:
The
source/390
object
server
shuts
down.
Administrator
Response:
Determine
why
the
ISGLCRT
macro
failed.
Refer
to
the
services
manual
in
the
z/OS
MVS
library.
If
necessary,
contact
IBM
Software
Support.
GTM5300I
ACC1DTRM,
SERVER
TERMINATION,
IN
CONTROL
Explanation:
The
data
space
address
space
is
ending.
System
Action:
The
source/390
object
server
continues
to
shut
down.
GTM5399E
DATASPACE
DELETE
FAILED,
RC=return_code
Explanation:
The
data
space
ACC1DSDE
delete
module
issued
a
return
code
other
than
zero.
Message
Variables:
return_code
-
The
return
code
from
the
ACC1DSDE
module
System
Action:
Processing
continues.
Administrator
Response:
Determine
why
the
data
space
delete
routine
failed.
Examine
the
source/390
data
space
output
for
prior
messages.
If
necessary,
contact
IBM
Software
Support.
GTM6000I
OBJECT
PUMP
INITIALIZATION
STARTING
Explanation:
The
batch
registration
pump
started.
System
Action:
Processing
continues.
GTM6001I
OBJECT
PUMP
CSA
ALLOCATED
AT:
address
Explanation:
Specifies
the
address
of
the
batch
pump
common
area.
Message
Variables:
address
-
The
batch
pump
common
area
address
System
Action:
Processing
continues.
GTM6033I
OBJECT
SERVER
SENSED,
SERVER=name
Explanation:
Specifies
the
name
of
the
data
space
address
space.
Message
Variables:
name
-
The
source/390
object
server
name
System
Action:
Processing
continues.
GTM6036I
EXECUTING
AS
SHADOW
PUMP
Explanation:
The
batch
pump
detected
the
main
source/390
object
pump
and
is
running
as
a
secondary
shadow
source/390
object
pump.
System
Action:
Processing
continues.
38
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
GTM6041I
CONNECTION
TO
DATASPACE
SUCCESSFUL,
SERVER=name,
START
DATE=date,
START
TIME=time
Explanation:
The
batch
pump
connected
to
the
data
space.
Message
Variables:
name
-
The
data
space
address
space
name
date
-
The
date
the
data
space
started
time
-
The
time
the
data
space
started
System
Action:
Processing
continues.
GTM6044E
DATASPACE
NOT
FOUND,
TBSM
TERMINATING
Explanation:
The
batch
pump
could
not
locate
the
corresponding
data
space.
System
Action:
The
source/390
batch
pump
stops.
Administrator
Response:
Check
that
the
source/390
data
space
is
running
and
that
it
is
using
the
same
ACC1ID
DD
card,
if
used,
as
the
source/390
batch
pump.
If
necessary,
contact
IBM
Software
Support.
GTM6085E
INVALID
ORIGIN
FOUND,
ORIGIN=data,
ADDRESS=address,
ALERT=alert
Explanation:
The
batch
pump
located
the
data
space,
but
the
data
space
storage
was
not
correctly
initialized.
Message
Variables:
data
-
The
data
at
the
data
space
origin
address
-
The
address
of
the
origin
alert
-
The
alert
for
the
data
space
origin
System
Action:
The
source/390
batch
pump
stops.
Administrator
Response:
Determine
why
the
data
space
initialization
had
not
completed.
If
necessary,
contact
IBM
Software
Support.
GTM6095E
MODULE
module_name
NOT
LOADED
TBSM
TERMINATING
Explanation:
The
batch
pump
could
not
load
the
named
module.
Message
Variables:
module_name
-
The
name
of
the
module
System
Action:
The
source/390
batch
pump
stops.
Administrator
Response:
Determine
why
the
module
could
not
be
loaded.
If
necessary,
contact
IBM
Software
Support.
GTM6114E
IEANTRT
NOT
LOADED,
ACC1TSQP
TERMINATING
Explanation:
The
batch
pump
could
not
load
the
IEANTRT
module.
Administrator
Response:
Determine
why
the
module
could
not
be
loaded.
If
necessary,
contact
IBM
Software
Support.
GTM6115E
NAME/TOKEN
RETRIEVE
FAILED,
ACC1TSQP
TERMINATED
Explanation:
The
batch
pump
could
not
retrieve
the
name
token
for
the
data
space.
System
Action:
The
source/390
batch
pump
stops.
Administrator
Response:
Determine
why
the
name
token
could
not
be
located.
Check
that
the
data
space
is
running
and
using
the
same
ACC1ID
DD
card,
if
used.
If
necessary,
contact
IBM
Software
Support.
GTM6116E
NO
DATA
PASSED,
PROCESS
TERMINATING,
DATA
NOT
QUEUED
Explanation:
No
data
was
passed
to
the
ACC1TSQP
queue
routine
by
the
batch
pump
REXX
EXEC.
Administrator
Response:
Determine
why
there
was
no
data.
If
necessary,
contact
IBM
Software
Support.
GTM6119E
NO
ALERT
PASSED,
PROCESS
TERMINATING,
DATA
NOT
QUEUED
Explanation:
The
source/390
batch
pump
queue
put
routine
could
not
find
an
ALERT
for
the
data
space
in
the
name
token
associated
with
the
data
space.
System
Action:
The
source/390
batch
pump
stops.
Administrator
Response:
Determine
why
the
ALERT
was
missing.
If
necessary,
contact
IBM
Software
Support.
GTM7036I
REGTRACE
IS
status
Explanation:
The
current
status
of
the
REGTRACE
option
when
the
parameter
is
not
specified.
Message
Variables:
status
-
The
current
status,
which
is
ON
of
OFF
System
Action:
Processing
continues.
GTM7037W
INVALID
COMMAND
ENTERED,
COMMAND=command
Explanation:
The
source/390
object
server
did
not
recognize
the
command
that
was
entered.
Message
Variables:
command
-
The
name
of
the
command
Chapter
1.
Source/390
Messages
-
GTM0001I
-
GTM8665E
39
System
Action:
Processing
continues.
The
command
is
not
processed.
Administrator
Response:
Correct
the
command
and
enter
it
again.
For
more
information,
refer
to
the
IBM
Tivoli
Business
Systems
Manager
Command
Reference.
GTM7064E
LOG
RECORD
LENGTH
IS
INVALID,
LENGTH=length
Explanation:
The
record
length
for
the
data
set
is
not
large
enough
to
receive
the
data
event
message
received
from
the
source/390
object
pump
task.
Message
Variables:
length
-
The
length
of
the
event
message
that
failed
to
be
written
to
the
log
file
System
Action:
Logging
ends.
Administrator
Response:
Create
a
log
file
with
an
LRECL
size
larger
than
indicated
in
the
message.
For
more
information
refer
to
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide.
GTM7065E
OPEN
FILE
ERROR
FOR
LOG
DATASET,
DSNAME=dsname
Explanation:
The
LOG
data
set
is
unable
to
be
open.
Message
Variables:
dsname
-
The
data
set
name
that
could
not
be
opened
System
Action:
Logging
ends.
Administrator
Response:
Determine
why
the
data
set
cannot
be
opened.
Correct
the
problem
and
restart
the
source/390
object
server.
GTM7066I
LOGGING
IS
NOT
ACTIVE
Explanation:
The
LOG
service
function
for
the
source/390
object
server
is
disabled
and
not
used.
The
LOG
parameters
are
not
specified
or
used
correctly.
System
Action:
Logging
ends.
Administrator
Response:
Correct
the
LOG
parameters
and
data
sets.
For
more
information,
refer
to
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide.
Restart
the
source/390
object
server.
GTM7067E
CLOSE
FILE
ERROR
FOR
LOG
DATASET,
DSNAME=dsname
Explanation:
The
active
LOG
data
set
failed
to
close
during
log
switching.
The
data
sets
for
LOG1
and
LOG2
switch
automatically
when
the
active
LOG
fills
up
or
is
manually
switched
when
the
LOGSWITCH
command
is
issued.
Message
Variables:
dsname
-
The
LOG
data
set
that
failed
to
close
System
Action:
Logging
ends.
Administrator
Response:
Determine
why
the
data
set
did
not
close.
Correct
the
problem
and
restart
the
source/390
object
server.
GTM7070I
GTMLOG
MGR
TERMINATED
Explanation:
The
source/390
object
server
ended
the
log
service
task
manager
during
shutdown
processing.
System
Action:
The
log
task
shuts
down.
Logging
ends.
GTM7120I
LOG
SWITCH
ACKNOWLEDGED
Explanation:
The
LOGSWITCH
command
was
received.
System
Action:
The
source/390
object
server
switches
from
the
active
log
to
the
inactive
log.
GTM7137E
INVALID
QUEUE
FOUND,
QADDR=queue_address,
HEADER
DATA=data
Explanation:
The
source/390
object
server
LOGSWITCH
command
processor
found
that
the
source/390
object
server
LOG
queue
was
not
valid.
Message
Variables:
queue_address
-
The
queue
address
data
-
The
data
from
the
queue
header
System
Action:
Processing
continues,
but
results
are
unpredictable.
Administrator
Response:
Determine
why
the
log
queue
is
not
available.
Try
restarting
all
source/390
address
spaces.
If
necessary,
contact
IBM
Software
Support.
GTM7138E
ERROR
OCCURRED
ON
QPUT
TO
LOGQ,
QADDR=queue_address,
RC=return_code
Explanation:
An
error
occurred
while
writing
to
the
source/390
object
server
log
queue.
Message
Variables:
queue_address
-
The
queue
address
return_code
-
The
return
code
from
the
QPUT
routine
System
Action:
Processing
continues,
but
results
are
unpredictable.
Administrator
Response:
Determine
why
the
log
queue
is
not
available.
Try
restarting
all
source/390
address
spaces.
If
necessary,
contact
IBM
Software
Support.
GTM7139E
INVALID
CELL
ACQUIRED,
CELLADDR=address,
CELL
HEADER=data
Explanation:
The
source/390
object
server
LOGSWITCH
command
processor
found
that
a
cell
in
40
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
the
data
space
was
not
valid.
Message
Variables:
address
-
The
cell
address
data
-
The
data
in
the
cell
header
System
Action:
Processing
continues,
but
results
are
unpredictable.
Administrator
Response:
Determine
why
the
log
queue
is
not
available.
Try
restarting
all
source/390
address
spaces.
If
necessary,
contact
IBM
Software
Support.
GTM7140I
LOG
SWITCH
PROCESSING
IN
CONTROL
Explanation:
The
source/390
object
server
LOGSWITCH
command
is
being
processed
System
Action:
Processing
continues.
GTM7141I
LOG
SWITCH
SUCCESSFUL,
NOW
LOGGING
TO:
dsname
Explanation:
The
source/390
object
server
is
now
logging
to
the
specified
data
set.
Message
Variables:
dsname
-
The
data
set
name
System
Action:
Processing
continues.
GTM7142I
SWITCHING
FROM:
current_dsname
TO:
active_dsname
Explanation:
The
source/390
object
server
is
switching
logging
from
the
current
active
data
set
to
the
new
active
data
set.
Message
Variables:
current_dsname
-
The
current
active
data
set
name
active_dsname
-
The
new
active
data
set
name
System
Action:
Processing
continues.
GTM7145I
EIF
INTERFACE
NOT
AVAILABLE
Explanation:
An
EIF
command
was
issued
to
the
source/390
object
server,
but
the
EIF
interface
was
not
enabled
in
the
source/390
object
server.
System
Action:
Processing
continues,
but
results
are
unpredictable.
Administrator
Response:
Determine
if
the
Tivoli
Enterprise
Console
EIF
interface
should
be
active
in
the
source/390
object
server.
If
so,
then
add
the
required
DD
statements
to
the
source/390
object
server
or
determine
why
the
interface
was
not
enabled
during
source/390
object
server
initialization.
GTM7146I
EIF
INTERFACE
ALREADY
status
Explanation:
The
EIF
START
or
EIF
STOP
command
to
the
source/390
object
server
was
issued,
but
the
interface
is
already
started
or
stopped.
Message
Variables:
status
-
The
current
status
of
the
interface,
which
is
either
STARTED
or
STOPPED
System
Action:
Processing
continues,
but
results
are
unpredictable.
GTM7147I
EIF
INTERFACE
status
Explanation:
The
EIF
START
or
EIF
STOP
command
to
the
source/390
object
server
was
issued.
Message
Variables:
status
-
The
status
of
the
interface,
which
is
either
STARTED
or
STOPPED
System
Action:
Processing
continues,
but
results
are
unpredictable.
GTM7148I
EIF
INTERFACE
IS
status
Explanation:
The
EIF
STATUS
command
was
entered
to
the
source/390
object
server.
Message
Variables:
status
-
The
current
status
of
the
interface,
which
is
either
STARTED,
STOPPED,
or
HALTED
System
Action:
Processing
continues.
Administrator
Response:
Determine
if
the
current
status
is
correct.
If
the
status
is
HALTED,
determine
why
the
EIF
interface
was
unable
to
build
the
select
table
from
the
GTMEIFSL
DD
input
by
viewing
console
messages
and
the
output
of
the
GTMEIFSP
DD.
Administrator
Response:
EIF
CONNECTION
STATUS
IS:
AVAILABLE
|
UNAVAILABLE
|
UNKNOWN
Explanation:
The
EIF
STATUS
command
was
entered
to
the
source/390
object
server.
The
message
shows
the
last
know
state
of
the
connection
to
the
Tivoli
Enterprise
Console
server.
A
status
of
AVAILABLE
indicates
that
the
last
record
was
successfully
sent
to
Tivoli
Enterprise
Console.
A
status
of
UNAVAILABLE
indicates
that
the
last
attempt
to
send
an
event
to
Tivoli
Enterprise
Console
failed.
A
status
of
UNKNOWN
indicates
that
no
records
have
yet
been
sent
to
the
Tivoli
Enterprise
Console
by
way
of
the
EIF
interface.
System
Action:
Processing
continues.
Administrator
Response:
If
the
status
is
UNAVAILABLE,
determine
why
the
event
was
not
sent
to
Tivoli
Enterprise
Console
by
reviewing
the
console
and
SYSOUT
logs.
Chapter
1.
Source/390
Messages
-
GTM0001I
-
GTM8665E
41
Administrator
Response:
EIF
LOG
STATUS
IS:
YES
|
NO
Explanation:
The
operator
entered
the
EIF
STATUS
or
EIF
LOG
command
to
the
source/390
object
server.
The
message
shows
the
current
setting
of
the
EIF
LOG
option.
YES
indicates
that
Tivoli
Enterprise
Console
events
and
the
return
code
from
the
EIF
call
are
displayed
in
the
system
log
file.
NO
indicates
that
logging
of
events
and
return
codes
is
not
done.
System
Action:
Processing
Continues
Administrator
Response:
If
required,
use
the
EIF
LOG
command
to
change
the
current
setting
of
the
LOG
option
for
Tivoli
Enterprise
Console
events.
Administrator
Response:
TOTAL
RECORDS
SELECTED:
number
Explanation:
The
EIF
STATUS
command
was
entered
to
the
source/390
object
server.
The
message
shows
the
total
number
of
records
selected
for
sending
to
Tivoli
Enterprise
Console
as
Tivoli
Enterprise
Console
events.
Message
Variables:
number
-
The
number
of
records
that
were
selected
to
send
to
Tivoli
Enterprise
Console
System
Action:
Processing
continues.
Administrator
Response:
RECORDS
SENT:
total_number
Explanation:
The
EIF
STATUS
command
was
entered
to
the
source/390
object
server.
The
message
shows
the
total
number
of
Tivoli
Enterprise
Console
event
records
sent
to
Tivoli
Enterprise
Console.
Message
Variables:
total_number
-
The
total
number
of
Tivoli
Enterprise
Console
event
records
that
were
successfully
sent
System
Action:
Processing
continues.
Administrator
Response:
RECORDS
FAILED:
total_number
Explanation:
The
EIF
STATUS
command
was
entered
to
the
source/390
object
server.
The
message
shows
the
total
number
of
Tivoli
Enterprise
Console
event
records
that
were
not
sent.
Message
Variables:
total_number
-
The
total
number
of
Tivoli
Enterprise
Console
event
records
that
were
not
sent
System
Action:
Processing
continues
Administrator
Response:
If
this
number
is
other
than
zero,
determine
why
the
events
records
to
be
sent
to
Tivoli
Enterprise
Console
server
of
the
Tivoli
Business
Systems
Manager
and
Tivoli
Enterprise
Console
failed.
Review
the
SYSLOG
and
SYSOUT
output
of
the
source/390
object
server
for
any
messages
that
might
indicate
the
cause
of
the
failure.
GTM7149E
EIF
STATUS
IS
HALTED
CANNOT
CHANGE
Explanation:
The
EIF
START
or
EIF
STOP
command
was
issued
against
the
source/390
object
server,
but
the
previous
attempt
to
initialize
the
EIF
interface
failed.
The
interface
was
marked
as
halted.
System
Action:
Processing
continues.
The
EIF
interface
status
is
unchanged.
Administrator
Response:
Determine
why
the
EIF
interface
did
not
initialize
by
reviewing
the
SYSLOG
and
SYSOUT
output
of
the
source/390
object
server.
GTM7150I
EIF
INTERFACE
REFRESHED
Explanation:
The
EIF
REFRESH
command
was
issued
against
the
source/390
object
server.
The
EIF
select
table
was
successfully
rebuilt.
System
Action:
Processing
continues.
GTM7151E
EIF
INTERFACE
REFRESH
FAILED
INTERFACE
HALTED
Explanation:
The
EIF
REFRESH
command
was
issued
to
the
source/390
object
server.
The
rebuild
of
the
Tivoli
Enterprise
Console
EIF
interface
select
table
failed.
System
Action:
The
interface
is
marked
as
halted
and
is
unavailable
until
the
error
is
corrected
and
the
select
table
successfully
rebuilt.
Administrator
Response:
Review
the
SYSLOG
and
SYSOUT
output
to
determine
why
the
interface
failed
to
build
the
select
table.
Correct
any
errors
in
the
select
table
input
and
reissue
the
EIF
REFRESH
command.
GTM7152E
UNABLE
TO
LOAD
GTMEIF01
CANNOT
REFRESH
EIF
INTERFACE
Explanation:
The
EIF
REFRESH
command
was
issued
to
the
source/390
object
server.
The
interface
was
unable
to
load
the
GTMEIF01
program.
The
interface
select
table
cannot
be
refreshed.
System
Action:
The
interface
select
table
cannot
be
refreshed.
Administrator
Response:
Review
the
SYSLOG
and
SYSOUT
output
to
determine
why
the
interface
was
unable
to
load
the
GTMEIF01
program.
Correct
the
error
and
reissue
the
REFRESH
command.
GTM7153I
event
Explanation:
This
message
is
issued
when
EIF_LOG=YES
is
coded
in
the
source/390
object
server
startup
parameters.
The
message
contains
the
Tivoli
Enterprise
Console
event
that
is
sent
to
Tivoli
Enterprise
Console
using
the
EIF
interface.
42
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
Message
Variables:
event
-
The
Tivoli
Enterprise
Console
event
System
Action:
Processing
continues.
GTM7154I
EIF
RETURN
CODE=return_code
Explanation:
This
message
is
issued
when
EIF_LOG=YES
is
coded
in
the
source/390
object
server
startup
parameters.
The
message
shows
the
return
code
from
the
call
to
the
EIF
interface
to
send
the
event
to
Tivoli
Enterprise
Console.
Message
Variables:
return_code
-
The
return
code
from
the
call
to
the
EIF
interface
System
Action:
Processing
continues.
GTM7155I
OPEN
ERROR
FOR
DDNAME
ddname
Explanation:
While
building
the
select
table
for
the
Tivoli
Enterprise
Console
EIF
interface,
the
interface
was
unable
to
open
the
specified
DD
name.
Message
Variables:
ddname
-
The
DD
name,
which
is
either
GTMEIFSP
or
GTMEIFSL
System
Action:
The
source/390
object
server
address
space
shuts
down.
Administrator
Response:
Review
the
SYSLOG
and
SYSOUT
output
to
determine
why
the
interface
was
unable
to
open
the
specified
DD
name.
Correct
the
error
and
issue
the
EIF
REFRESH
command
to
rebuild
the
select
table.
Refer
to
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide
for
more
information.
GTM7180I
TRACE
STATUS
CHANGED,
TRACE=status
Explanation:
The
source/390
object
server
trace
status
is
changed.
Message
Variables:
status
-
The
new
trace
status
System
Action:
Processing
continues
with
the
new
trace
status.
GTM7190E
GTF
OPTION
MUST
BE
START,
STOP
OR
STATUS
Explanation:
The
option
entered
with
the
GTF
command
was
not
recognized.
System
Action:
The
command
is
not
processed.
Administrator
Response:
Enter
the
command
again
with
the
correct
option.
Refer
to
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide
for
more
information
about
the
GTF
command.
GTM7191I
GTF
TRACE
STATUS
IS
status
Explanation:
This
is
the
current
status
of
the
GTF
interface
within
the
address
space,
or
the
resulting
status
after
the
GTF
START
or
GTF
STOP
command
was
issued.
Message
Variables:
status
-
The
status,
which
is
either
STARTED
or
STOPPED
System
Action:
Processing
continues
with
the
new
trace
status.
GTM7400I
TBSM
APPC
MGR:
INITIALIZATION
IN
PROGRESS
Explanation:
The
APPC
LU
6.2
communications
manager
within
the
object
server
is
initializing.
System
Action:
Processing
continues.
GTM7401E
TBSM
APPC
MGR:
GETMAIN
FAILED
FOR
type
Explanation:
A
GETMAIN
macro
for
the
specified
storage
failed
within
the
APPC
LU
6.2
communications
manager.
Message
Variables:
type
-
The
type
of
storage
that
was
being
obtained
System
Action:
Communication
between
the
source/390
object
server
and
Windows
is
not
possible.
Administrator
Response:
The
error
indicates
that
the
source/390
object
pump
exhausted
the
virtual
storage
to
which
it
was
available.
Use
the
region
parameter
of
the
EXEC
JCL
card
to
increase
the
amount
of
virtual
storage
available.
If
the
problem
continues,
contact
IBM
Software
Support.
GTM7402E
TBSM
APPC
MGR:
VTAM
APPLID
MISSING
IN
TBSM
CSA
Explanation:
The
VTAM
application
ID
for
the
APPC
LU
6.2
communications
manager
was
not
found.
System
Action:
The
source/390
object
server
shuts
down.
Administrator
Response:
Add
the
VTAM
application
ID
for
the
APPC
manager
to
the
source/390
object
server
startup
parameters
in
the
REMOTE_APPLID=name
parameter.
If
necessary,
contact
IBM
Software
Support.
GTM7403E
TBSM
APPC
MGR:
VTAM
MODCB
FAILED
FOR
name
Explanation:
A
VTAM
MODCB
macro
failed
for
the
specified
control
block
type.
Message
Variables:
name
-
The
control
block
name
that
was
being
modified
Chapter
1.
Source/390
Messages
-
GTM0001I
-
GTM8665E
43
System
Action:
The
source/390
object
server
shuts
down.
Administrator
Response:
Contact
IBM
Software
Support.
GTM7404I
TBSM
APPC
MGR:
OPENING
VTAM
APPLID
applid
Explanation:
The
source/390
object
server
communications
manager
is
opening
the
specified
VTAM
application
ID.
Message
Variables:
applid
-
The
name
of
the
VTAM
application
ID
System
Action:
Processing
continues.
GTM7405E
TBSM
APPC
MGR:
VTAM
OPEN
FAILED,
RC=return_code
Explanation:
The
source/390
object
server
was
unable
to
open
the
VTAM
application
ID
as
indicated
by
the
REMOTE_APPLID
parameter.
Message
Variables:
return_code
-
The
error
code
from
the
VTAM
OPEN
macro
instruction
System
Action:
Communication
between
the
source/390
object
server
and
the
Windows
components
did
not
initialize.
Administrator
Response:
Determine
if
the
application
ID
defined
in
the
REMOTE_APPLID
parameter
is
defined
to
VTAM
and
available
for
use
by
the
source/390
object
server.
Refer
to
the
section
on
the
OPEN
macro
instruction
in
the
SNA
Programming
Guide
for
information
about
the
return
codes
from
the
VTAM
OPEN
macro
instruction.
Start
the
source/390
object
server
again.
GTM7406I
TBSM
APPC
MGR:
SESSIONS.
TOTAL=total,
WINNERS=total_winners,
LOSERS=total_losers
Explanation:
The
source/390
object
server
communications
manager
established
a
session
with
the
partner
LU.
Message
Variables:
total
-
The
total
number
of
sessions
available
total_winners
-
The
number
of
contention
winner
sessions
that
are
currently
active
total_losers
-
The
number
of
contention
loser
sessions
that
are
currently
active
System
Action:
Processing
continues.
Administrator
Response:
Check
that
there
is
at
least
one
contention
winner
and
one
contention
loser
session
active.
If
not,
review
the
VTAM
application
ID
definition
for
the
APPC
manager
and
partner
LU.
If
necessary,
contact
IBM
Software
Support.
GTM7408E
TBSM
APPC
MGR:
UNABLE
TO
LOAD
SERVICE
PROGRAM
pgm
Explanation:
The
source/390
object
server
communications
manager
is
unable
to
load
the
specified
service
program.
Message
Variables:
pgm
-
The
name
of
the
service
program
that
could
not
be
loaded
System
Action:
Communication
between
the
source/390
object
server
and
Windows
components
did
not
initialize.
Administrator
Response:
Determine
why
the
specified
program
could
not
be
loaded.
Validate
that
the
SGTMMODS
library
is
in
the
STEPLIB
concatenation.
If
necessary,
contact
IBM
Software
Support.
GTM7409E
TBSM
APPC
MGR:
SERVICE
PGM
pgm
ISSUED
ALLOCATE
WHEN
ALREADY
IN
SESSION
Explanation:
The
specified
communication
service
program
attempted
to
allocate
a
session
with
the
partner
LU
while
it
was
already
in
session.
Message
Variables:
pgm
-
The
name
of
the
service
program
that
issued
the
ALLOCATE
request
System
Action:
Communication
between
the
source/390
object
server
and
the
Windows
operating
system
is
not
possible.
Administrator
Response:
Contact
IBM
Software
Support.
GTM7410E
TBSM
APPC
MGR:
SERVICE
PGM
pgm
ISSUED
SEND
WHEN
NOT
IN
SEND
STATE
Explanation:
The
specified
APPC
communications
service
program
attempted
to
issue
a
SEND
request
when
it
was
not
in
the
send
state.
Message
Variables:
pgm
-
The
name
of
the
service
program
that
issued
the
SEND
request
System
Action:
Communication
between
the
source/390
object
server
and
the
Windows
operating
system
is
not
possible.
Administrator
Response:
Contact
IBM
Software
Support.
GTM7411E
TBSM
APPC
MGR:
DATA
BUFFER
GETMAIN
FAILED
FOR
SERVICE
PROGRAM
pgm
Explanation:
A
GETMAIN
macro
for
a
data
buffer
failed
for
the
service
program
specified.
Message
Variables:
pgm
-
The
name
of
the
service
program
for
which
the
GETMAIN
macro
failed
System
Action:
Communication
between
the
44
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
source/390
object
server
and
the
Windows
operating
system
is
not
possible.
Administrator
Response:
This
error
indicates
that
the
source/390
object
pump
exhausted
the
virtual
storage
to
which
it
was
available.
Use
the
region
parameter
of
the
EXEC
JCL
card
to
increase
the
amount
of
virtual
storage
available.
If
the
problem
continues,
contact
IBM
Software
Support.
GTM7412E
TBSM
APPC
MGR:
SERVICE
PGM
pgm
ISSUED
RECEIVE
WHEN
NOT
IN
SESSION
Explanation:
The
specified
service
program
issued
a
receive
request
but
it
was
not
in
session
with
the
partner
LU.
Message
Variables:
pgm
-
The
name
of
the
service
program
that
issued
the
receive
request
System
Action:
Processing
continues,
but
results
are
unpredictable.
Administrator
Response:
Contact
IBM
Software
Support.
GTM7413E
TBSM
APPC
MGR:
SERVICE
PGM
pgm
PASSED
A
BAD
WAIT
LIST
Explanation:
The
specified
service
program
passed
a
wait
list
that
was
not
valid
to
the
APPC
communications
manager.
Message
Variables:
pgm
-
The
name
of
the
service
program
that
issued
the
wait
request
System
Action:
Processing
continues,
but
results
are
unpredictable.
Administrator
Response:
Contact
IBM
Software
Support.
GTM7414E
TBSM
:parameter
PARAMETER
IS
NOT
SPECIFIED
Explanation:
The
remote
application
ID
or
local
LU
name
indicated
by
parameter
is
not
specified
in
the
startup
parameters
for
the
source/390
object
server.
Message
Variables:
parameter
-
Either
REMOTE_APPLID
or
LOCAL_LUNAME
System
Action:
The
source/390
object
server
ends.
Administrator
Response:
Add
the
REMOTE_APPLID
and
LOCAL_LUNAME
keywords
that
are
required
to
be
used
for
the
LU
6.2
connection.
Refer
to
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide.
GTM7422E
TBSM
APPC
MGR:
STIMERM
FAILED.
CANCELLING
WAIT
FOR
CONNECTION
Explanation:
A
STIMREM
macro
failed
while
waiting
for
a
connection
to
the
partner
LU.
System
Action:
Processing
continues.
The
APPC
communications
manager
ends
the
wait
for
a
connection
process.
Administrator
Response:
Determine
why
the
STIMERM
micro
failed.
If
necessary,
contact
IBM
Software
Support.
GTM7423E
TBSM
APPC
MGR:
PROGRAM
pgm
DETECTED
AN
INVALID
OR
BAD
CMCB
Explanation:
The
specified
service
program
could
not
correctly
map
the
Communications
Manager
Control
Block
(CMCB).
Message
Variables:
pgm
-
The
name
of
the
service
program
System
Action:
Processing
continues,
but
results
are
unpredictable.
Administrator
Response:
This
represents
a
service
level
mismatch
between
the
APPC
communications
manager
and
the
service
program.
Validate
that
the
SGTMMODS
library
is
in
the
STEPLIB
concatenation.
If
the
problem
continues,
contact
IBM
Software
Support.
GTM7424I
TBSM
APPC
MGR:
INITIALIZING
PROGRAM
pgm
Explanation:
The
APPC
communications
manager
is
initializing
the
specified
service
program.
Message
Variables:
pgm
-
The
name
of
the
service
program
System
Action:
Processing
continues.
GTM7425I
TBSM
APPC
MGR:
PROGRAM
pgm
HAS
ENDED
Explanation:
The
APPC
communications
manager
detected
that
the
specified
service
program
ended.
Message
Variables:
pgm
-
The
name
of
the
service
program
System
Action:
Processing
continues.
Administrator
Response:
Other
than
the
source/390
object
server
ending,
the
service
APPC
service
programs
usually
should
not
end.
Determine
if
the
session
was
lost
to
the
partner
LU.
If
necessary,
contact
IBM
Software
Support.
Chapter
1.
Source/390
Messages
-
GTM0001I
-
GTM8665E
45
GTM7426I
TBSM
APPC
MGR:
PROGRAM
pgm
IGNORED
SHUTDOWN
REQUEST
TERMINATION
FORCED
Explanation:
The
APPC
communications
manager
detected
that
the
specified
service
program
ignored
a
shutdown
request.
The
APPC
communications
manager
ends
the
service
program.
Message
Variables:
pgm
-
The
name
of
the
service
program
System
Action:
Processing
continues,
but
results
are
unpredictable.
Administrator
Response:
Contact
IBM
Software
Support.
GTM7427I
TBSM
APPC
MGR:
CANCELLING
VTAM
REQUEST
FOR
PROGRAM
pgm
Explanation:
The
APPC
communications
manager
detected
that
a
VTAM
request
other
than
SEND
was
in
progress
for
the
specified
service
program
when
the
shutdown
request
was
received.
The
VTAM
request
is
cancelled.
Message
Variables:
pgm
-
The
name
of
the
service
program
System
Action:
Processing
continues,
but
results
are
unpredictable.
GTM7428I
TBSM
APPC
MGR:
SESSION
LIMITS
(WINNERS)
REACHED
FOR
PROGRAM
pgm
Explanation:
The
APPC
communications
manager
detected
that
the
specified
service
program
issued
an
ALLOCATE
but
there
are
no
more
contention
winner
sessions
available.
Message
Variables:
pgm
-
The
name
of
the
service
program
System
Action:
The
session
is
not
allocated.
Processing
continues,
but
results
are
unpredictable.
Administrator
Response:
If
this
is
the
first
session
request
from
the
source/390
object
server,
then
check
that
the
VTAM
application
ID
definition
for
the
source/390
object
server
APPLID
and
partner
LU
are
correct.
If
necessary,
contact
IBM
Software
Support.
GTM7429E
TBSM
APPC
MGR:
PROGRAM
pgm
ISSUED
ALLOCATE
WITH
BLANK
NAME
OPERAND
Explanation:
The
APPC
communications
manager
detected
that
the
specified
service
program
issued
an
ALLOCATE
but
that
the
process
name
parameter
is
missing.
Message
Variables:
pgm
-
The
name
of
the
service
program
System
Action:
The
session
is
not
allocated.
Processing
continues,
but
results
are
unpredictable.
Administrator
Response:
Contact
IBM
Software
Support.
GTM7430I
TBSM
APPC
MGR:
RECEIVED
FMH5
HAD
ZERO
LENGTH
PROCESS
NAME,
FMH5
REJECTED
Explanation:
The
APPC
communications
manager
received
an
FMH5
from
the
partner
LU
to
initiate
a
session
but
the
process
name
within
the
FMH5
was
missing.
Administrator
Response:
Consider
using
VTAM
trace
facilities
to
determine
the
origin
of
the
non-valid
FMH5
request.
If
the
problem
continues,
contact
IBM
Software
Support.
GTM7493I
TBSM
APPC
MGR:
TERMINATION
IN
PROGRESS
Explanation:
The
APPC
communications
manager
received
a
shutdown
command
and
is
terminating.
System
Action:
The
shutdown
process
continues.
GTM7494E
TBSM
APPC
MGR:
function
RTNCD=return_code
FDBK2=reason_code
FOR
PROGRAM
pgm
Explanation:
The
APPC
communications
manager
received
an
error
from
the
specified
VTAM
APPC
function.
Message
Variables:
function
-
The
function
name
being
issued
return_code
-
The
return
code
from
the
function
reason_code
-
The
reason
code
from
the
function
(FDBK2)
pgm
-
The
name
of
the
service
program
that
requested
the
function
System
Action:
Processing
continues,
but
the
results
are
unpredictable.
Administrator
Response:
Try
to
determine
why
the
request
failed.
Refer
to
the
appropriate
manual
in
the
IBM
SNA
library
for
more
information.
If
the
problem
continues,
contact
IBM
Software
Support.
GTM7495E
TBSM
APPC
MGR:
function
RTNCD=return_code
FDBK2=reason_code
FOR
PROGRAM
pgm
Explanation:
The
APPC
communications
manager
received
an
error
from
the
specified
VTAM
APPC
function.
Message
Variables:
function
-
The
function
name
being
issued
46
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
return_code
-
The
return
code
from
the
function
RPL
(RPL6RCPR)
reason_code-
The
reason
code
from
the
function
RPL
(RPL6RCSC)
pgm
-
The
name
of
the
service
program
that
requested
the
function
System
Action:
Processing
continues,
but
the
results
are
unpredictable.
Administrator
Response:
Try
to
determine
why
the
request
failed.
Refer
to
the
appropriate
manual
in
the
IBM
SNA
library
for
more
information.
If
the
problem
continues,
contact
IBM
Software
Support.
GTM7496E
TBSM
APPC
MGR:
function
RTNCD=return_code
FDBK2=reason_code
Explanation:
The
APPC
communications
manager
received
an
error
from
the
specified
VTAM
APPC
function.
Message
Variables:
function
-
The
function
name
being
issued
return_code
-
The
return
code
from
the
function
reason_code
-
The
reason
code
from
the
function
System
Action:
Processing
continues,
but
the
results
are
unpredictable.
Administrator
Response:
Try
to
determine
why
the
request
failed.
Refer
to
the
appropriate
manual
in
the
IBM
SNA
library
for
more
information.
If
the
problem
continues,
contact
IBM
Software
Support.
GTM7497E
TBSM
APPC
MGR:
function
RCPRI=return_code
RCSEC=reason_code
Explanation:
The
APPC
communications
manager
received
an
error
from
the
specified
VTAM
APPC
function.
Message
Variables:
function
-
The
function
name
being
issued
return_code
-
The
return
code
from
the
function
RPL
(RPL6RCPR)
reason_code
-
The
reason
code
from
the
function
RPL
(RPL6RCSC)
System
Action:
Processing
continues,
but
the
results
are
unpredictable.
Administrator
Response:
Try
to
determine
why
the
request
failed.
Refer
to
the
appropriate
manual
in
the
IBM
SNA
library
for
more
information.
If
the
problem
continues,
contact
IBM
Software
Support.
GTM7498I
TBSM
APPC
MGR:
CLOSING
VTAM
ACB
Explanation:
The
APPC
communications
manager
is
closing
the
VTAM
ACB
System
Action:
The
VTAM
ACB
is
closed.
Communication
in
no
longer
possible.
GTM7499I
TBSM
APPC
MGR
:
TERMINATED
Explanation:
The
APPC
communications
manager
ended.
This
message
is
issued
during
the
shutdown
of
the
source/390
object
pump.
System
Action:
Processing
continues.
GTM7500I
INITIALIZATION
IN
PROGRESS
Explanation:
The
source/390
object
pump
address
space
is
starting.
System
Action:
Processing
continues.
GTM7501I
RUNNING
INITIAL
REXX
EXEC:
pgm
Explanation:
The
initial
REXX
EXEC
that
is
run
first
when
the
source/390
object
pump
address
space
is
started.
Message
Variables:
pgm
-
The
name
of
the
REXX
EXEC
program
System
Action:
Processing
continues.
GTM7502E
GETMAIN
FAILED
FOR
name
Explanation:
There
is
insufficient
storage
for
GETMAIN
processing.
Message
Variables:
name
-
The
name
of
the
storage
area
that
was
unable
to
be
obtained
System
Action:
Processing
continues,
but
the
results
are
unpredictable.
Administrator
Response:
This
error
indicates
that
the
source/390
object
pump
exhausted
the
virtual
storage
to
which
it
is
available.
Use
the
region
parameter
of
the
EXEC
JCL
card
to
increase
the
amount
of
virtual
storage
available.
If
the
problem
continues,
contact
IBM
Software
Support.
GTM7503E
LOAD
FAILED
FOR
module_name
Explanation:
The
module
is
unable
to
be
loaded
into
memory.
Message
Variables:
module_name
-
The
module
name
that
cannot
be
loaded
System
Action:
Processing
continues.
Administrator
Response:
Determine
why
the
module
cannot
be
loaded.
Validate
that
the
STEPLIB
DD
concatenation
contains
the
SGTMMODS
library.
This
Chapter
1.
Source/390
Messages
-
GTM0001I
-
GTM8665E
47
might
be
an
installation
problem.
If
necessary,
contact
IBM
Software
Support.
GTM7505E
NOT
RUNNING
AUTHORIZED
Explanation:
The
source/390
object
pump
address
space
is
not
running
APF
authorized.
System
Action:
The
source/390
object
pump
stops.
Administrator
Response:
Verify
that
the
load
libraries
used
in
the
STEPLIB
concatenation
of
the
source/390
object
pump
address
space
are
APF
authorized.
GTM7506E
SYSEVENT
TRANSWAP
FAILED,
RC=return_code
Explanation:
The
source/390
object
pump
address
space
is
unable
to
run
the
Non-Swappable
procedure.
Message
Variables:
return_code
-
The
return
code
from
the
SYSEVENT
macro
System
Action:
The
source/390
object
pump
stops.
Administrator
Response:
Determine
why
the
source/390
object
pump
address
space
cannot
run
the
Non-Swappable
procedure.
Refer
to
the
services
manual
in
the
z/OS
MVS
library.
If
necessary,
contact
IBM
Software
Support.
GTM7507I
UNABLE
TO
LOCATE
OBJECT
SERVER
Explanation:
The
source/390
object
pump
address
space
is
started
with
the
request
to
connect
to
the
source/390
data
space.
The
source/390
data
space
that
is
to
be
used
is
not
running.
System
Action:
Processing
continues.
Administrator
Response:
The
source/390
data
space
should
be
started
first,
prior
to
starting
the
source/390
object
server
and
source/390
object
pump
address
spaces.
GTM7508I
OBJECT
SERVER
DETECTED,
JOBNAME=jobname
Explanation:
The
source/390
object
pump
address
space
found
the
data
space
that
is
to
be
used.
Message
Variables:
jobname
-
The
job
name
of
the
source/390
data
space
System
Action:
Processing
continues.
GTM7509E
ALREADY
EXECUTING,
JOBNAME=jobname
Explanation:
A
second
copy
of
the
source/390
object
pump
address
space
is
attempting
to
use
the
same
data
space.
This
is
an
internal
error.
Message
Variables:
jobname
-
The
job
name
of
the
source/390
data
space
System
Action:
The
source/390
object
pump
stops.
Administrator
Response:
Contact
IBM
Software
Support.
GTM7510E
UNABLE
TO
LOCATE
TIOT
Explanation:
The
TIOT
control
block
cannot
be
obtained.
This
is
an
internal
error.
System
Action:
The
source/390
object
pump
stops.
Administrator
Response:
Contact
IBM
Software
Support.
GTM7511E
UNABLE
TO
CREATE
NAME
TOKEN,
RC=return_code
Explanation:
The
name
token
used
for
cross
memory
support
cannot
be
created.
Message
Variables:
return_code
-
The
return
code
from
a
call
to
IEANTCT
System
Action:
Processing
continues.
Administrator
Response:
Determine
the
cause
of
the
failure
to
create
the
name
token.
Refer
to
the
services
manual
in
the
z/OS
MVS
library.
If
the
problem
continues
contact
IBM
Software
Support.
GTM7513E
INVALID
ORIGIN
DETECTED
IN
SERVER
Explanation:
The
source/390
object
pump
address
space
detected
a
data
space
that
might
be
corrupted.
System
Action:
The
source/390
object
pump
address
space
shuts
down.
Administrator
Response:
Restart
the
three
address
spaces
in
the
proper
order;
the
source/390
object
pump,
object
server,
and
the
data
space.
If
the
problem
continues,
contact
IBM
Software
Support.
GTM7514E
UNABLE
TO
ESTABLISH
CONSOLE
COMMUNICATIONS,
RC=return_code
Explanation:
The
source/390
object
pump
address
space
is
not
initialized
with
console
communication
support.
The
MODIFY
command
cannot
be
used
from
a
z/OS
console
to
issue
a
command
for
the
source/390
object
pump
address
space.
Message
Variables:
return_code
-
The
return
code
from
the
QEDIT
macro
System
Action:
The
source/390
object
pump
address
space
shuts
down.
Administrator
Response:
Investigate
the
return
code
reported
by
the
QEDIT
macro.
Refer
to
the
services
48
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
manual
in
the
z/OS
MVS
library.
Contact
IBM
Software
Support
if
the
problem
cannot
be
resolved.
GTM7517I
CMD=text
Explanation:
The
modify
command
was
issued
from
the
z/OS
console.
Message
Variables:
text
-
The
text
of
the
command
System
Action:
Processing
continues.
GTM7520I
AOPLOG
LOG
OUTPUT
NOT
AVAILABLE
Explanation:
The
AOPLOG
DD
name
is
not
specified
in
the
JCL
of
the
Tivoli
Business
Systems
Manager
procedure.
System
Action:
Processing
continues.
Administrator
Response:
Apply
the
AOPLOG
DD
name
in
the
JCL
of
the
Tivoli
Business
Systems
Manager.
GTM7521I
AOPSYSIN
OPEN
FAILURE,
USING
DEFAULT
SETTINGS
Explanation:
The
AOPSYSIN
DD
name
is
unable
to
open
the
file
containing
the
source/390
object
pump
startup
parameters.
The
default
settings
are
used.
System
Action:
Processing
continues.
Administrator
Response:
If
any
of
the
source/390
object
pump
parameters
require
changing,
a
file
referenced
by
the
AOPSYSIN
DD
name
is
required
to
be
used.
Refer
to
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide.
GTM7524I
VTAM
3270
SERVICES
ARE
NOT
AVAILABLE
Explanation:
The
source/390
object
pump
TERMINAL_PREFIX
or
NUMBER_OF_TERMINALS
parameters
are
not
valid.
The
3270
interface
is
not
usable.
System
Action:
Processing
continues.
Some
data
might
be
unavailable.
Administrator
Response:
Refer
to
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide
about
how
to
configure
the
keywords
for
the
TERMINAL_PREFIX
and
NUMBER_OF_TERMINALS
operands.
GTM7525E
VTAM
SHOWCB
FAILED
FOR
function,
RC=return_code
Explanation:
During
initialization
of
the
Tivoli
Business
Systems
Manager
3270
interface,
an
error
occurred
on
the
SHOWCB
function
for
the
area
identified
in
the
$P1
operand.
The
Tivoli
Business
Systems
Manager
3270
interface
is
not
usable.
Message
Variables:
function
-
The
SHOWCB
function
did
not
successfully
obtain
the
area
specified
return_code
-
The
return
code
returned
from
the
SHOWCB
function
call
System
Action:
Processing
continues.
Some
data
might
be
unavailable.
Administrator
Response:
Refer
to
the
appropriate
manual
in
the
SNA
Programming
library
for
more
information
on
the
return
codes
from
the
SHOWCB
function.
Also,
refer
to
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide
about
how
to
setup
the
Tivoli
Business
Systems
Manager
3270
interface.
If
necessary,
contact
IBM
Software
Support.
GTM7526E
VTAM
function
FAILED
FOR
block,
R15=return_code,
R0=reason_code
Explanation:
The
VTAM
function
indicated
in
block
did
not
successfully
complete
when
attempting
to
establish
a
3270
session.
Tivoli
Business
Systems
Manager
cannot
log
on
to
any
3270
applications.
Message
Variables:
function
-
The
GENCB
VTAM
function
did
not
successfully
create
the
area
specified
in
block
block
-
The
ACB
block
that
was
not
generated
return_code
-
The
return
code
returned
from
the
GENCB
function
call
reason_code
-
The
reason
code
returned
from
the
GENCB
function
call.
System
Action:
Processing
continues.
Some
data
might
be
unavailable.
Administrator
Response:
Refer
to
the
appropriate
manual
in
the
SNA
Programming
library
for
more
information
on
the
return
codes
from
the
SHOWCB
function.
Also,
refer
to
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide
about
how
to
setup
the
Tivoli
Business
Systems
Manager
3270
interface.
If
necessary,
contact
IBM
Software
Support.
GTM7527E
VTAM
function
FAILED
FOR
block
R15=return_code
Explanation:
The
VTAM
function
indicated
in
block
did
not
successfully
complete
when
attempting
to
establish
a
3270
session.
Tivoli
Business
Systems
Manager
cannot
logon
to
any
3270
applications.
Message
Variables:
function
-
The
GENCB
VTAM
function
did
not
successfully
create
the
area
specified
in
the
block
block
-
The
VTAM
control
block
that
was
not
generated
return_code
-
The
return
code
that
is
returned
from
the
GENCB
function
call
Chapter
1.
Source/390
Messages
-
GTM0001I
-
GTM8665E
49
System
Action:
Processing
continues.
Some
data
is
unavailable.
Administrator
Response:
Refer
to
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide
about
how
to
setup
the
3270
interface.
If
necessary,
contact
IBM
Software
Support.
GTM7528E
VTAM
OPEN
FAILED
RC=return_code
FOR
LU
name
Explanation:
VTAM
failed
to
open
the
ACB
on
behalf
of
the
session.
Message
Variables:
return_code
-
The
return
code
value
returned
from
the
OPEN
ACB
call
name
-
The
LU
name
representing
the
logical
terminal
for
this
3270
session
System
Action:
Processing
continues.
Some
data
is
unavailable.
Administrator
Response:
Refer
to
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide
about
how
to
setup
the
Tivoli
Business
Systems
Manager
3270
interface.
If
necessary,
contact
IBM
Software
Support.
GTM7529E
PVI
MESSAGE:
error
Explanation:
An
error
occurred
on
behalf
of
the
active
3270
session.
Message
Variables:
error
-
Identifies
the
error
that
occurred
System
Action:
Processing
continues.
Some
data
is
unavailable.
Administrator
Response:
Depending
on
the
error
message
returned,
take
the
appropriate
action.
Refer
to
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide
about
how
to
use
the
Tivoli
Business
Systems
Manager
3270
interface.
If
necessary,
contact
IBM
Software
Support.
GTM7530I
AOPLEXSY
ATTACH
FOR
SESSION
name
FAILED
Explanation:
The
Tivoli
Business
Systems
Manager
AOPLEXSY
manager
is
not
able
to
initialize
on
behalf
of
the
3270
session.
Message
Variables:
name
-
The
3270
session
name
System
Action:
The
session
was
not
connected.
Administrator
Response:
Contact
IBM
Software
Support.
GTM7531E
AOPLEXSY
NOT
VALID
FOR
SESSION
name
Explanation:
The
session
type
used
on
behalf
of
the
Tivoli
Business
Systems
Manager
3270
session
is
not
supported.
This
is
an
internal
error.
Message
Variables:
name
-
The
session
name.
AOPLEXSY
sessions
are
supported
for
the
following
products:
v
Tivoli
OMEGAMON
XE
v
Tivoli
OMEGAMON
XE
for
CICS
v
Tivoli
OMEGAMON
XE
for
DB2®
v
Tivoli
OMEGAMON
XE
for
IMS
v
Tivoli
OMEGAMON
XE
for
MVS
System
Action:
The
session
is
closed.
Administrator
Response:
Contact
IBM
Software
Support.
GTM7532I
VTAM
SESSION
ENDED
-
name
Explanation:
The
Tivoli
Business
Systems
Manager
3270
session
is
logged
off.
Message
Variables:
name
-
The
session
name
that
ended
System
Action:
Processing
continues.
GTM7534E
EDI
CROSS
MEMORY
INIT
ERROR
CODE
code
Explanation:
The
cross
memory
resources
required
for
the
EDI
interface
cannot
initialize.
Users
of
the
EDI
exit
services
are
not
usable.
Message
Variables:
code
-
The
code
indicating
the
cross
memory
resource
that
did
not
initialize.
The
values
are
as
follows:
X'01'
LXCREATE
X'02'
LXTOKEN
X'03'
ETCREATE
X'04'
ETCONNECT
X'05'
PCTOKEN
System
Action:
Processing
continues.
The
Tivoli
Business
Systems
Manager
is
unable
to
receive
events
from
EDI
sources.
Administrator
Response:
Contact
IBM
Software
Support.
GTM7535E
INVALID
COMMAND:
text
Explanation:
A
command
was
issued
with
the
MVS
MODIFY
command
from
an
MVS
console
and
the
command
is
not
supported.
Message
Variables:
text
-
The
command
text
that
was
issued
System
Action:
Processing
continues.
50
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
Administrator
Response:
Refer
to
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide
for
the
valid
commands
that
are
supported
by
Tivoli
Business
Systems
Manager.
Issue
the
command
again.
GTM7536E
EXEC
NAME
MISSING
FROM
REFRESH
COMMAND
Explanation:
The
REFRESH
command
was
issued
without
providing
an
EXEC
name.
System
Action:
Processing
continues.
Administrator
Response:
Reissue
the
command
again
providing
the
EXEC
name.
Refer
to
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide
for
more
information
about
the
REFRESH
command.
GTM7537E
REFRESH
NOT
VALID
WHEN
EXEC_REFRESH=YES
Message
Variables:
The
REFRESH
command
is
issued
for
an
EXEC
while
Tivoli
Business
Systems
Manager
is
running
with
EXEC_REFRESH=YES.
EXECs
cannot
be
refreshed
when
Tivoli
Business
Systems
Manager
is
configured
with
this
setting
on.
System
Action:
Processing
continues.
Administrator
Response:
Refer
to
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide
for
more
information
about
the
REFRESH
command.
GTM7538I
EXEC
name
NOT
LOADED,
NOT
REFRESHED
Explanation:
The
REFRESH
command
is
issued
for
an
EXEC
that
was
not
previously
loaded
and
Tivoli
Business
Systems
Manager
is
configured
to
run
with
EXEC_REFRESH=NO.
Message
Variables:
name
-
The
name
of
the
EXEC
System
Action:
Processing
continues.
Administrator
Response:
Run
the
executable
from
Tivoli
Business
Systems
Manager
to
enable
the
EXEC
to
be
loaded.
If
the
EXEC
is
changed,
use
the
REFRESH
command
to
reload
the
new
copy.
Refer
to
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide
for
more
information
about
the
REFRESH
command.
GTM7539I
EXEC
name
REFRESHED
Explanation:
The
specified
EXEC
was
successfully
refreshed
by
the
REFRESH
command.
Message
Variables:
name
-
The
name
of
the
EXEC
System
Action:
Processing
continues.
GTM7540E
REXX
ENVIRONMENT
CREATE
FAILED,
RC=return_code,
REASON=reason_code
Explanation:
The
REXX
environment
is
not
created.
Message
Variables:
return_code
-
The
return
code
returned
from
the
call
to
IRXINIT
used
to
create
the
REXX
environment
reason_code
-
The
reason
code
returned
from
the
call
to
IRXINIT
System
Action:
Processing
continues,
but
the
results
are
unpredictable.
Administrator
Response:
Contact
IBM
Software
Support.
GTM7541E
REXX
HOST
ENVIRONMENT
CREATE
FAILED,
RC=return_code
Explanation:
The
REXX
AOP
host
command
environment
is
not
created.
Message
Variables:
return_code
-
The
return
code
returned
from
the
call
to
IRXSUBCM
used
to
create
the
REXX
host
command
environment
System
Action:
Processing
continues,
but
the
results
are
unpredictable.
Administrator
Response:
Contact
IBM
Software
Support.
GTM7542E
REXX
VAR
SET
RC=return_code,
VAR=name
Explanation:
The
local
REXX
variable
specified
cannot
be
used.
Message
Variables:
return_code
-
The
return
code
from
the
call
to
IRXEXCOM
name
-
The
name
of
the
local
REXX
variable
System
Action:
Processing
continues,
but
the
results
are
unpredictable.
Administrator
Response:
Contact
IBM
Software
Support.
GTM7545E
name
SUBSYSTEM
INITIALIZED
Explanation:
The
subsystem
interface
successfully
initialized.
Message
Variables:
name
-
The
name
of
the
Tivoli
Business
Systems
Manager
subsystem
System
Action:
Processing
continues.
Chapter
1.
Source/390
Messages
-
GTM0001I
-
GTM8665E
51
GTM7546E
name
SUBSYSTEM
INITIALIZATION
FAILED
Explanation:
The
Tivoli
Business
Systems
Manager
subsystem
is
not
initialized
and
cannot
be
used.
Message
Variables:
name
-
The
name
of
the
Tivoli
Business
Systems
Manager
subsystem
Administrator
Response:
Review
the
console
log
for
additional
messages
that
might
indicate
why
the
subsystem
initialization
failed.
If
necessary,
contact
IBM
Software
Support.
GTM7547I
name
SUBSYSTEM
QUIESCING
Explanation:
The
Tivoli
Business
Systems
Manager
subsystem
is
in
process
of
shutting
down.
Message
Variables:
name
-
The
name
of
the
Tivoli
Business
Systems
Manager
subsystem
System
Action:
The
subsystem
starts
the
shutdown
process.
GTM7548I
name:
SUBSYSTEM
COMMUNICATION
ENDED
Explanation:
The
Tivoli
Business
Systems
Manager
subsystem
communication
is
stopped.
Message
Variables:
name
-
The
name
of
the
subsystem
System
Action:
The
subsystem
stops.
GTM7550E
name:
LINK
TO
module_name
FAILED
Explanation:
The
module
named
could
not
be
linked
to
during
subsystem
initialization.
This
is
an
internal
error.
Message
Variables:
name
-
The
name
of
the
Tivoli
Business
Systems
Manager
subsystem
module_name
-
The
module
name
that
could
not
be
linked
during
the
initialization
System
Action:
The
subsystem
ends.
Some
source/390
commands
might
not
be
available.
Administrator
Response:
Contact
IBM
Software
Support.
GTM7551E
name:
IEFSSI
function
ERROR,
RC=return_code
REASON=reason_code
Explanation:
The
IEFSSI
function
failed
with
errors
during
subsystem
initialization.
Message
Variables:
name
-
The
name
of
the
Tivoli
Business
Systems
Manager
subsystem
function
-
The
function
call
used
on
the
IEFSSI
service
return_code
-
The
return
code
returned
from
the
IEFSSI
function
call
reason_code
-
The
reason
code
returned
from
the
IEFSSI
function
call
System
Action:
The
subsystem
ends.
Some
source/390
commands
might
not
be
available.
Administrator
Response:
Determine
the
reason
for
the
failure.
Refer
to
the
appropriate
manual
in
the
z/OS
MVS
library
for
more
information.
If
the
problem
continues,
contact
IBM
Software
Support.
GTM7552E
name:
IEFSSVT
function
ERROR,
RC=return_code
REASON=reason_code
Explanation:
The
IEFSSVT
function
failed
with
errors
during
dynamic
subsystem
initialization.
Message
Variables:
name
-
The
name
of
the
Tivoli
Business
Systems
Manager
subsystem
function
-
The
function
call
used
on
the
IEFSSVT
service
return_code
-
The
return
code
returned
from
the
IEFSSVT
function
call
reason_code
-
The
reason
code
returned
from
the
IEFSSVT
function
call
System
Action:
The
subsystem
ends.
Some
source/390
commands
might
not
be
available.
Administrator
Response:
Determine
the
reason
for
the
failure.
Refer
to
the
appropriate
manual
in
the
z/OS
MVS
library
for
more
information.
If
the
problem
continues,
contact
IBM
Software
Support.
GTM7553E
name:
AOPAUTH
DD
OPEN
ERROR
Explanation:
The
source/390
object
pump
was
unable
to
open
the
AOPAUTH
library
during
subsystem
initialization.
Message
Variables:
name
-
The
name
of
the
Tivoli
Business
Systems
Manager
subsystem
System
Action:
The
subsystem
ends.
Some
source/390
commands
might
not
be
available.
Administrator
Response:
Verify
that
the
Tivoli
Business
Systems
Manager
load
library
is
referenced
by
the
AOPAUTH
DD
name.
If
the
problem
continues,
contact
IBM
Software
Support.
GTM7554E
name
LOAD
FAILED
FOR
module_name:
value
Explanation:
The
module
name
cannot
be
loaded
during
the
subsystem
initialization.
Message
Variables:
name
-
The
name
of
the
Tivoli
Business
Systems
Manager
subsystem
module_name
-
The
module
name
that
could
not
be
loaded
value
-
A
numerical
reference
value
indicating
which
occurrence
of
the
LOAD
macro
failed
52
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
System
Action:
The
subsystem
ends.
Some
source/390
commands
might
not
be
available.
Administrator
Response:
Verify
that
the
Tivoli
Business
Systems
Manager
load
library
is
referenced
by
the
AOPAUTH
DD
name.
If
the
problem
continues,
contact
IBM
Software
Support.
GTM7555E
name:
MODULE
module_name
NOT
AMODE
31
Explanation:
The
named
module
is
not
link-edited
with
addressing
mode
31.
This
indicates
a
problem
with
the
installation
of
source/390
components.
Message
Variables:
name
-
The
name
of
the
Tivoli
Business
Systems
Manager
subsystem
module_name
-
The
name
of
the
module
in
error
System
Action:
The
subsystem
ends.
Some
source/390
commands
might
not
be
available.
Administrator
Response:
Determine
why
the
module
has
the
incorrect
addressing
mode
(AMODE).
Check
to
see
if
the
application
was
installed
correctly.
If
necessary,
contact
IBM
Software
Support.
GTM7556E
name:
IEFSSREQ
value
R15=return_code
SSOBRETN=return_code
SFDA_RC=return_code
Explanation:
An
IEFSSREQ
error
occurred
while
processing
a
subsystem
request.
Message
Variables:
name
-
The
name
of
the
Tivoli
Business
Systems
Manager
subsystem
value
-
The
function
request
for
the
IEFSSREQ
service
return_code
-
The
return
code
returned
from
the
IEFSSREQ
service
return_code
-
The
return
code
value
provided
in
the
SSOB
area
return_code
-
The
return
code
value
provided
in
the
SFDA
area
System
Action:
The
subsystem
ends.
Some
source/390
commands
might
not
be
available.
Administrator
Response:
For
SFDA_RC
values
of
16
or
20,
check
that
a
copy
of
the
source/390
object
pump
is
not
already
running
with
the
same
subsystem
name.
If
the
source/390
object
pump
is
not
running,
check
that
the
last
execution
ended
without
errors.
You
can
run
the
source/390
object
pump
with
a
different
subsystem
name
or
you
can
use
the
AOPUTIL
utility
in
the
SGTMMODS
library
to
reset
the
subsystem.
If
necessary,
contact
IBM
Software
Support.
GTM7557E
name:
IEFSSREQ
function
R15=return_code
SSOBRETN=value
Explanation:
An
IEFSSREQ
error
occurred
during
subsystem
termination
processing.
Message
Variables:
name
-
The
name
of
the
Tivoli
Business
Systems
Manager
subsystem
function
-
The
function
request
made
to
the
subsystem
return_code
-
The
return
code
returned
from
the
requested
service
value
-
The
return
code
value
provided
in
the
SSOB
area
System
Action:
The
subsystem
ends.
Some
source/390
commands
might
not
be
available.
Administrator
Response:
Determine
why
the
RESMGR
request
failed.
For
more
information,
refer
to
the
appropriate
manual
in
the
z/OS
MVS
library.
If
necessary,
contact
IBM
Software
Support.
GTM7558E
name:
module_name
RESMGR
ADD
RC=return_code
Explanation:
The
resource
manager
add
request
failed.
The
subsystem
is
ended.
Message
Variables:
name
-
The
name
of
the
Tivoli
Business
Systems
Manager
subsystem
module_name
-
The
module
name
of
the
resource
manager
return_code
-
The
return
code
from
the
RESMGR
ADD
macro
System
Action:
The
subsystem
ends.
Some
source/390
commands
might
not
be
available.
Administrator
Response:
Determine
why
the
RESMGR
request
failed.
For
more
information,
refer
to
the
appropriate
manual
in
the
z/OS
MVS
library.
If
necessary,
contact
IBM
Software
Support.
GTM7559E
name:
module_name
CALL
FAILED.
DECIMAL
RC=rc.
Explanation:
A
call
to
the
NAME
TOKEN
service
failed
during
the
system
initialization.
Message
Variables:
name
-
The
name
of
the
Tivoli
Business
Systems
Manager
subsystem
module_name
-
The
module
name
that
failed
return_code
-
The
decimal
return
code
from
the
module
that
failed
System
Action:
The
source/390
object
pump
shuts
down.
Administrator
Response:
Keep
all
logs
and
contact
IBM
Software
Support.
Chapter
1.
Source/390
Messages
-
GTM0001I
-
GTM8665E
53
GTM7560I
name
MAX
THREADS
REACHED,
REPLY
1
-
9
TO
INCREASE,
0
TO
IGNORE
Explanation:
The
maximum
number
of
threads
allowed
to
be
processed
concurrently
was
reached
within
the
Tivoli
Business
Systems
Manager
subsystem
interface.
There
are
no
more
available
threads
to
process
any
further
commands
using
the
Tivoli
Business
Systems
Manager
subsystem.
Message
Variables:
name
-
The
name
of
the
Tivoli
Business
Systems
Manager
subsystem
System
Action:
Processing
stops
while
waiting
for
a
response.
Administrator
Response:
To
increase
the
number
of
available
threads,
reply
with
a
number
in
the
range
1–9.
To
cancel
this
message
now
and
suppress
it
in
the
future,
reply
0
(zero).
If
you
reply
with
a
value
in
the
range
1–9
and
this
message
continues
to
appear,
then
it
indicates
there
is
a
problem
with
the
Tivoli
Business
Systems
Manager
subsystem
interface.
If
possible,
obtain
a
system
dump
(SDUMP)
of
the
source/390
object
pump
address
space,
including
the
CSA
-
ATA=(CSA,
RGN,
LSQA,
PSA)
parameters.
Refer
to
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide
for
more
information
about
the
SUBSYSTEM_MAXTHREADS
operand.
GTM7561I
name:
REPLY
TO
ACC7560I
MUST
BE
NUMERIC,
0-9
Explanation:
The
reply
to
message
GTM7560I
must
be
a
single
numeric
digit
in
the
range
0–9.
Message
Variables:
name
-
The
name
of
the
Tivoli
Business
Systems
Manager
subsystem
System
Action:
The
GTM7560I
message
is
issued
again.
Administrator
Response:
Correct
the
reply
to
the
GTM7560I
message.
GTM7562I
name:
THREAD
LIMITREACHED
(100)
Explanation:
The
number
of
threads
processing
simultaneously
within
the
Tivoli
Business
Systems
Manager
subsystem
reached
100.
This
is
the
absolute
maximum
allowed
by
the
subsystem.
Message
Variables:
name
-
The
name
of
the
subsystem
System
Action:
Processing
continues,
but
no
new
threads
are
attached.
Some
data
can
be
lost.
Administrator
Response:
Obtain
a
system
dump
of
the
source/390
object
pump
address
space,
including
the
CSA
using
the
SDUMP
SDATA=(CSA,
RGN,
PSA,
LSQA
parameters.
Contact
IBM
Software
Support.
GTM7563E
DATA
TYPE
MISSING
FROM
SHOW
COMMAND
Explanation:
The
data
type
operand
is
not
provided
on
the
SHOW
command.
System
Action:
The
command
is
not
processed.
Administrator
Response:
Reissue
the
SHOW
command
with
a
supported
data
type
operand.
Refer
to
the
IBM
Tivoli
Business
Systems
Manager
Command
Reference
for
more
information
about
the
SHOW
command.
GTM7564E
type
IS
INVALID
FOR
SHOW
COMMAND
Explanation:
The
data
type
operand
used
on
the
SHOW
command
is
not
supported.
Message
Variables:
type
-
The
data
type
entered
System
Action:
The
command
is
not
processed.
Administrator
Response:
Reissue
the
SHOW
command
with
a
supported
data
type
operand.
Refer
to
the
IBM
Tivoli
Business
Systems
Manager
Command
Reference
for
more
information
about
the
SHOW
command.
GTM7565E
error_text
Explanation:
This
is
the
error
message
returned
from
the
SHOW
TRAPS
command.
Message
Variables:
error_text
-
The
error
message
text
System
Action:
The
command
is
not
processed.
Administrator
Response:
Depending
on
the
error
message
received
from
issuing
the
SHOW
TRAPS
command,
take
appropriate
action.
If
necessary,
contact
IBM
Software
Support.
GTM7566E
TRAP
MANAGER
IS
NOT
ACTIVE
Explanation:
The
Tivoli
Business
Systems
Manager
Trap
Manager
interface
is
not
available.
The
SHOW
TRAPS
command
cannot
be
run.
System
Action:
Processing
continues.
Many
functions
of
source/390
might
not
be
available.
Administrator
Response:
If
the
source/390
object
pump
is
shutting
down,
no
action
is
necessary.
If
this
is
not
the
reason,
contact
IBM
Software
Support.
GTM7567I
text
Explanation:
This
displays
the
output
from
the
SHOW
command
Message
Variables:
text
-
The
display
line
text
54
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
System
Action:
Processing
continues.
GTM7568E
PVI
MANAGER
IS
NOT
ACTIVE
Explanation:
The
Tivoli
Business
Systems
Manager
Programmable
VTAM
interface
is
not
available.
The
SHOW
SESSIONS
command
cannot
be
issued.
System
Action:
Processing
continues.
Some
functions,
such
as
Tivoli
OMEGAMON
monitoring,
might
not
be
available.
Administrator
Response:
If
the
source/390
object
pump
is
shutting
down,
no
action
is
necessary.
If
this
is
not
the
reason,
contact
IBM
Software
Support.
GTM7570I
text
Explanation:
This
is
the
output
from
the
SHOW
TRAPS
command.
Message
Variables:
text
-
The
display
line
text
System
Action:
Processing
continues.
GTM7571E
AOPDAY
STIMERM
SET
FAILED,
RC=return_code
Explanation:
The
STIMERM
macro
failed
in
the
AOPDAY
change
of
day
program.
Message
Variables:
return_code
-
The
return
code
returned
from
the
STIMERM
service
System
Action:
Processing
continues.
Administrator
Response:
Determine
why
the
STIMERM
macro
failed.
For
more
information,
refer
to
the
appropriate
manual
in
the
z/OS
MVS
library.
If
necessary,
contact
IBM
Software
Support.
GTM7574I
LOGSCREENS
IS
state
Explanation:
The
3270
screens
retrieved
from
each
active
session
are
written
to
the
AOPLOG
log,
depending
on
if
the
state
is
ON.
Message
Variables:
state
-
The
value
of
the
state,
which
is
either
ON
or
OFF
System
Action:
Processing
continues.
GTM7575I
SHOW
COMMAND
COMPLETE
Explanation:
This
is
the
end
of
a
set
of
display
messages
resulting
from
issuing
a
SHOW
command.
System
Action:
Processing
continues.
GTM7576I
text
Explanation:
This
is
the
summary
message
text
from
a
SHOW
TRAPS
command.
Message
Variables:
text
-
The
summary
output
from
a
SHOW
TRAPS
command
System
Action:
Processing
continues.
GTM7577E
GLOBAL
VARIABLE
MANAGER
NOT
ACTIVE
Explanation:
The
global
variable
interface
is
not
available.
The
SHOW
VARS
and
SHOW
POOL
commands
are
not
available.
System
Action:
Processing
continues.
Administrator
Response:
If
the
source/390
object
pump
is
shutting
down,
no
action
is
necessary.
If
this
is
not
the
reason,
contact
IBM
Software
Support.
GTM7578E
CONSOLE
MANAGER
NOT
ACTIVE
Explanation:
The
console
manager
interface
is
not
available.
The
SHOW
MSGCOUNT
command
is
not
available.
System
Action:
Processing
continues.
Administrator
Response:
If
the
source/390
object
pump
is
shutting
down,
no
action
is
necessary.
If
this
is
not
the
reason,
contact
IBM
Software
Support.
GTM7579I
CONSOLE
MESSAGES
RECEIVED:
number
Explanation:
The
total
number
of
console
messages
received
is
displayed
on
the
console
when
the
SHOW
MSGCOUNT
command
is
issued.
Message
Variables:
number
-
The
number
of
messages
received
System
Action:
Processing
continues.
GTM7580I
REXX
NOT
ACTIVE
IN
THIS
REGION
Explanation:
The
REFRESH
command
was
issued
for
a
REXX
EXEC,
but
there
is
no
REXX
environment
to
support
running
executable
files.
System
Action:
Processing
continues,
but
results
are
unpredictable.
Administrator
Response:
Contact
IBM
Software
Support.
GTM7581E
CANNOT
RUN
REXX
EXECS,
REXX
NOT
INITIALIZED
Explanation:
An
attempt
was
made
to
run
a
REXX
EXEC
but
there
is
no
REXX
environment
to
support
running
executable
files.
System
Action:
Processing
continues,
but
results
are
unpredictable.
Administrator
Response:
Determine
why
here
is
no
REXX
environment
available
within
the
address
space.
If
necessary,
contact
IBM
Software
Support.
Chapter
1.
Source/390
Messages
-
GTM0001I
-
GTM8665E
55
GTM7582E
INIT
TABLE
SUFFIX
NOT
PASSED
TO
AOPPARM
Explanation:
The
suffix
value
identifying
the
parameter
module
that
is
to
be
used
for
the
Tivoli
Business
Systems
Manager
component
was
not
provided.
This
is
an
internal
error.
System
Action:
The
address
space
shuts
down.
Administrator
Response:
Contact
IBM
Software
Support.
GTM7583E
INIT
TABLE
IS
EMPTY
Explanation:
The
parameter
table
module
for
the
region
contains
no
entries.
This
is
an
internal
error.
System
Action:
The
address
space
shuts
down.
Administrator
Response:
Contact
IBM
Software
Support.
GTM7584I
AOPLEXSY
DETECTED
LROWS
OVERFLOW
ON
session_name
Explanation:
A
3270
session
collecting
data
from
Tivoli
OMEGAMON
products
cannot
find
the
delimiter
value
on
the
screen.
This
value
is
used
by
Tivoli
Business
Systems
Manager
to
control
scrolling
during
the
3270
session.
Message
Variables:
session_name
-
The
name
of
the
session
System
Action:
Processing
continues,
but
some
data
might
be
lost.
Administrator
Response:
Increase
the
number
of
logical
rows
(LROWS)
used
by
the
session.
GTM7585I
ENTER
PARAMETERS,
END
TO
FINISH
Explanation:
Enter
additional
parameters
for
the
source/390
object
pump
or
object
server.
This
message
is
only
issued
if
the
parameter
field
of
the
JCL
EXEC
PGM
statement
for
the
source/390
object
pump
or
object
server
contains
the
keyword
.CONSOLE.
System
Action:
The
source/390
address
space
waits
for
a
reply.
Administrator
Response:
Reply
with
additional
or
changed
startup
parameters.
The
operator
continues
to
enter
additional
parameters
until
the
.END
parameter
is
entered
in
reply
to
this
message.
If
multiple
parameters
are
entered
in
one
reply,
separate
each
parameter
with
a
comma.
A
trailing
comma
is
not
required
when
continuing
input
on
a
subsequent
line.
GTM7586E
KEYWORD
TOO
LONG,
FOUND:
keyword
Explanation:
The
specified
keyword
is
too
long.
The
program
prints
out
the
part
that
it
can
hold.
The
source/390
object
pump
or
object
server
stopped.
Message
Variables:
keyword
-
The
part
of
the
keyword
name
that
the
program
prints
System
Action:
The
source/390
address
space
waits
for
a
reply.
Administrator
Response:
Restart
the
source/390
object
pump
or
object
server,
enter
the
parameters
again,
and
correct
the
parameter
in
error.
GTM7587E
CLOSING
QUOTE
MISSING
FROM
DATA
FOR
KEYWORD
Explanation:
The
data
for
the
specified
keyword
was
started
with
a
single
or
double
quotation
mark,
but
the
program
could
not
find
a
matching
closing
quotation
mark.
This
is
a
syntax
error.
The
source/390
object
pump
or
object
server
stopped.
System
Action:
The
address
space
shuts
down.
Administrator
Response:
Restart
the
source/390
object
pump
or
object
server
and
enter
the
correct
parameters.
GTM7588E
NON
NUMERIC
DATA
FOUND
FOR
KEYWORD
keyword
Explanation:
The
data
for
the
specified
keyword
must
be
numeric.
The
source/390
object
pump
or
object
server
stopped.
Message
Variables:
keyword
-
The
part
of
the
keyword
name
that
the
program
prints
System
Action:
The
address
space
shuts
down.
Administrator
Response:
Restart
the
source/390
object
pump
or
object
server,
enter
the
parameters
again,
and
correct
the
parameter
in
error.
GTM7589E
text
Explanation:
An
error
occurred
processing
the
parameter
data
entered
by
way
of
the
PARM
operand
of
the
JCL
EXEC
PGM
card
or
from
the
operator.
Message
Variables:
text
-
The
message
can
contain
the
following
text:
v
PARAMETER
SET
FAILED
FOR
KEYWORD
keyword
Explanation
An
error
occurred
storing
the
parameter
data.
56
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
Administrator
Response
If
possible,
determine
why
the
error
occurred.
If
necessary,
contact
IBM
Software
Support.
v
DATA
VALUE
TOO
SMALL
FOR
KEYWORD
keyword
Explanation
The
data
entered
for
the
specified
keyword
is
not
within
the
valid
range
(data
is
less
than
the
minimum
allowed).
The
default
value
is
used.
Administrator
Response
To
correct
this,
stop
the
address
space
and
restart
it,
specifying
a
valid
value
for
the
keyword.
v
DATA
VALUE
TOO
LARGE
FOR
KEYWORD
keyword
Explanation
The
data
entered
for
the
specified
keyword
is
not
within
the
valid
range
(data
is
greater
than
the
minimum
allowed).
The
default
value
is
used.
Administrator
Response
To
correct
this,
stop
the
address
space
and
restart
it,
specifying
a
valid
value
for
the
keyword.
v
DATA
MISSING
FOR
KEYWORD
keyword
Explanation
No
data
was
entered
for
the
specified
keyword.
The
keyword
is
ignored.
A
default
value
might
be
used
if
one
exists.
Administrator
Response
To
correct
this,
stop
the
address
space
and
restart
it,
specifying
a
valid
value
for
the
keyword.
GTM7590E
SUBSYSTEM_NAME=NO
IS
NOT
SUPPORTED.
Explanation:
The
source/390
object
pump
SUBSYSTEM_NAME
start
parameter
was
specified
with
a
value
of
NO.
System
Action:
The
source/390
object
pump
shuts
down.
Administrator
Response:
Change
the
value
of
the
parameter
to
a
valid
subsystem
name
or
remove
the
parameter
to
allow
the
default
value
to
be
used.
GTM7597I
STOP
COMMAND
DETECTED
Explanation:
The
STOP
command
was
issued
to
shutdown
the
source/390
address
space.
System
Action:
The
address
space
initiates
the
shutdown
process.
GTM7598I
TERMINATION
IN
PROGRESS
Explanation:
The
source/390
address
space
is
shutting
down.
GTM7599I
TERMINATION
COMPLETE
Explanation:
The
source/390
address
space
ended
successfully.
GTM7600E
IBM
TIVOLI
BUSINESS
SYSTEMS
MANAGER
MCS
CONSOLE
ALREADY
EXISTS
Explanation:
The
source/390
object
pump
is
attempting
to
start
with
an
MCS
console
name
that
is
already
being
used.
System
Action:
The
source/390
object
pump
stops.
Administrator
Response:
Change
the
CONSOLE=console_name
in
the
source/390
object
pump
start
parameters
to
a
name
that
is
unique.
If
the
problem
continues,
contact
IBM
Software
Support.
GTM7601E
CONSOLE
ACTIVATION
FAILED,
RC=return_code
REASON=reason_code
Explanation:
The
source/390
object
pump
could
not
activate
an
MCS
console
during
initialization
of
the
console
interface.
Message
Variables:
return_code
-
The
return
code
returned
from
the
MCSOPER
ACTIVATE
service
reason_code
-
The
reason
code
returned
from
the
MCSOPER
ACTIVATE
service
System
Action:
Processing
continues.
Tivoli
Business
Systems
Manager
is
unable
to
monitor
console
messages.
Administrator
Response:
Determine
why
the
MCS
console
cannot
be
activated.
If
necessary,
contact
IBM
Software
Support.
GTM7602E
CONSOLE
DEACTIVATION
FAILED,
RC=return_code
REASON=reason_code
Explanation:
The
source/390
object
pump
could
not
deactivate
an
MCS
console
during
shutdown
of
the
console
interface.
Message
Variables:
return_code
-
The
return
code
returned
from
the
MCSOPER
DEACTIVATE
service
reason_code
-
The
reason
code
returned
from
the
MCSOPER
DEACTIVATE
service
System
Action:
Processing
continues,
but
the
results
are
unpredictable.
Administrator
Response:
Determine
why
the
MCS
console
cannot
be
deactivated.
If
necessary,
contact
IBM
Software
Support.
Chapter
1.
Source/390
Messages
-
GTM0001I
-
GTM8665E
57
GTM7604I
text
Explanation:
This
indicates
the
status
of
the
MCS
console
queuing.
Message
Variables:
text
-
The
message
can
have
the
following
text:
v
*
MCS
QUEUING
STOPPED,
MESSAGE
DATASPACE
FULL
v
*
MCS
QUEUING
STOPPED,
MAX
MESSAGES
QUEUED
v
*
MCS
QUEUING
STOPPED,
MCS
INTERNAL
ERROR
v
*
MCS
QUEUED
MSGS
AT
80%
System
Action:
Processing
continues.
Administrator
Response:
Determine
why
the
MCS
console
interface
is
not
processing
messages.
If
necessary,
contact
IBM
Software
Support.
GTM7605E
MCS
MESSAGE
QUEUING
RESUME
FAILED
RC=return_code
REASON=reason_code
Explanation:
The
MCS
console
failed
to
resume
message
queuing.
Message
Variables:
return_code
-
The
return
code
returned
from
the
MCSOPMSG
RESUME
service
reason_code
-
The
reason
code
returned
from
the
MCSOPMSG
RESUME
service
System
Action:
Processing
continues.
Tivoli
Business
Systems
Manager
is
unable
to
monitor
console
messages.
Administrator
Response:
Determine
why
the
MCS
console
cannot
resume
processing.
If
necessary,
contact
IBM
Software
Support.
GTM7606I
MCS
MESSAGE
QUEUING
RESUMED
Explanation:
The
MCS
console
is
receiving
messages.
This
message
indicates
that
a
prior
error
condition
no
longer
exists.
System
Action:
Processing
continues.
GTM7607E
MCS
ERROR
RETRIEVING
MESSAGE
RC=return_code
REASON=reason_code
Explanation:
An
error
occurred
while
the
MCS
console
interface
was
retrieving
a
message.
Message
Variables:
return_code
-
The
return
code
returned
from
the
MCSOPMSG
GETMSG
service
reason_code
-
The
reason
code
returned
from
the
MCSOPMSG
GETMSG
service
System
Action:
Processing
continues.
Administrator
Response:
Determine
why
the
MCS
console
cannot
receive
messages.
If
necessary,
contact
IBM
Software
Support.
GTM7610E
INVALID
pgm
PARAMETERS
SUPPLIED
parameters
Explanation:
Tivoli
Business
Systems
Manager
discovered
that
parameters
were
supplied
to
the
monitoring
program
that
were
not
valid.
Message
Variables:
pgm
-
The
name
of
the
monitoring
program
parameters
-
The
parameters
that
were
in
error
System
Action:
Processing
continues.
Some
DASD
and
CACHE
performance
exceptions
might
be
unavailable.
Administrator
Response:
Keep
any
job
logs
and
contact
IBM
Software
Support.
GTM7611E
SYSPLEX
DATA
SERVICES
HAS
NO
BUFFERS
AVAILABLE
FOR
DATA
COLLECTION
Explanation:
Tivoli
Business
Systems
Manager
cannot
monitor
DASD
or
CACHE
performance
because
RMF™
was
started
with
no
SMF
buffers.
System
Action:
Processing
continues.
Some
DASD
and
CACHE
performance
exceptions
might
be
unavailable.
Administrator
Response:
Restart
RMF
specifying
the
SMFBUF
parameter.
GTM7612E
NOT
AUTHORIZED
TO
ACCESS
SYSPLEX
DATA
SERVICES
Explanation:
Tivoli
Business
Systems
Manager
cannot
monitor
DASD
or
CACHE
performance
because
the
Tivoli
Business
Systems
Manager
address
space
is
not
authorized
to
use
sysplex
data
services.
System
Action:
Processing
continues.
Some
DASD
and
CACHE
performance
exceptions
might
be
unavailable.
Administrator
Response:
Ensure
that
the
source/390
object
pump
address
space
is
permitted
to
ERBSDS.SMFDATA
in
the
resource
class
of
FACILITY.
GTM7613E
SYSPLEX
DATA
SERVICES
type
REQUEST
FAILED
RETURN
CODE=return_code
REASON
CODE=reason_code
Explanation:
An
error
occurred
while
processing
sysplex
data
services
request
type.
Message
Variables:
type
-
The
type
of
request
return_code
-
The
failing
return
code
reason_code
-
The
failing
reason
code
58
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
System
Action:
Processing
continues.
Some
DASD
and
CACHE
performance
exceptions
might
be
unavailable.
Administrator
Response:
Keep
any
job
logs
and
contact
IBM
Software
Support.
GTM7614I
UNABLE
TO
USE
SYSPLEX
DATA
SERVICES
RMF
IS
NOT
ACTIVE
Explanation:
Tivoli
Business
Systems
Manager
cannot
monitor
DASD
or
CACHE
performance
because
RMF
is
not
active.
System
Action:
Processing
continues.
Some
DASD
and
CACHE
performance
exceptions
might
be
unavailable.
Administrator
Response:
Start
the
RMF
address
space.
GTM7615E
LOAD
FAILED
FOR
MODULE
pgm
Explanation:
Tivoli
Business
Systems
Manager
cannot
load
the
program,
which
is
required
to
monitor
DASD
and
CACHE
performance.
Message
Variables:
pgm
-
The
name
of
the
program
that
Tivoli
Business
Systems
Manager
cannot
load
System
Action:
Processing
continues.
Some
DASD
and
CACHE
performance
exceptions
might
be
unavailable.
Administrator
Response:
Check
for
the
program
named
in
the
LPALIB
or
LINKLST
concatenation.
If
you
cannot
determine
the
cause
of
the
failure,
contact
IBM
Software
Support.
GTM7616E
UNABLE
TO
OBTAIN
STORAGE
FOR
SYSPLEX
DATA
SERVICES
BUFFER
size
return_code
Explanation:
Tivoli
Business
Systems
Manager
could
not
obtain
a
buffer
to
contain
the
information
for
DASD
and
CACHE
performance
monitoring.
Message
Variables:
size
-
The
amount
of
storage
requested
return_code
-
The
storage
return
code
System
Action:
Processing
continues.
Some
DASD
and
CACHE
performance
exceptions
might
be
unavailable.
Administrator
Response:
Try
to
determine
the
cause
of
the
failure.
If
you
cannot
resolve
the
problem,
keep
any
job
logs
and
contact
IBM
Software
Support.
GTM7620I
QUEUE
MAX
RECS
CURRENT
RECS
PCT
USED
CURRENT
THRES/PCT
LOST
RECS
TOTAL
RECS
Explanation:
This
message
is
issued
in
response
to
the
QUEUE
command.
The
message
forms
a
heading
for
the
subsequent
GTM7621I
messages
that
describe
the
queues.
GTM7621I
queue
max_recs
curr_recs
pct_used
curr_thresh
lost_recs
total_recs
full
Explanation:
This
message
is
issued
in
response
to
the
QUEUE
command.
It
is
issued
once
for
every
queue
contained
in
the
source/390
object
server.
Message
Variables:
queue
-
The
name
of
the
queue
being
reported
max_recs
-
The
maximum
number
of
records
that
can
be
held
by
the
queue
curr_recs
-
The
current
number
of
records
on
the
queue
pct_used
-
The
amount
in
percentage
of
the
queue
currently
in
use
curr_thresh
-
The
threshold
value
which,
when
exceeded,
will
result
in
a
message
being
issued
lost_recs
-
The
number
of
records
that
have
been
discarded
as
a
result
of
the
queue
being
in
a
full
condition
total_recs
-
The
total
number
of
records
which
have
been
written
to
the
queue
full
-
FULL
or
a
blank,
which
indicates
if
the
queue
is
currently
in
a
full
condition
System
Action:
Processing
continues.
GTM7622I
QUEUE
queue
HAS
BEEN
RESET
Explanation:
The
queue
was
successfully
reset
as
a
result
of
the
QUEUE
RESET
command.
Message
Variables:
queue
-
The
name
of
the
queue
being
reset
System
Action:
The
queue
is
reset
to
turn
off
the
full
condition
and
permit
new
records
to
be
written
to
the
queue.
GTM7624I
UNABLE
TO
RESET
QUEUE
queue
THE
QUEUE
IS
AT
100
PERCENT
Explanation:
The
QUEUE
RESET
command
was
issued,
but
the
queue
could
not
be
reset
because
it
is
currently
at
its
maximum
capacity.
Message
Variables:
queue
-
The
name
of
the
queue
System
Action:
The
queue
is
not
reset
and
subsequent
new
records
cannot
be
written
to
the
queue.
Administrator
Response:
Issue
the
command
again
Chapter
1.
Source/390
Messages
-
GTM0001I
-
GTM8665E
59
after
some
messages
have
been
taken
from
the
queue.
GTM7625E
LATCH
ERROR
ON
QUEUE
queue
Explanation:
There
was
an
error
when
attempting
to
obtain
the
latch
for
the
indicated
queue.
This
is
a
server
internal
error.
Message
Variables:
queue
-
The
name
of
the
queue
for
which
the
error
is
being
reported
System
Action:
The
queue
is
not
reset.
Regular
processing
continues.
Administrator
Response:
This
is
an
internal
error.
A
dump
should
be
requested
of
the
source/390
data
space
and
the
address
space
that
reports
the
error.
Keep
all
logs
and
contact
IBM
Software
Support.
GTM7626I
QUEUE
queue
NOT
FOUND
Explanation:
The
QUEUE
RESET
command
was
issued
with
a
queue
name
that
does
not
exist.
Message
Variables:
queue
-
The
name
of
the
queue
entered
in
the
command
System
Action:
No
queue
is
reset
and
processing
continues.
Administrator
Response:
Verify
that
the
name
of
the
queue
entered
was
correct.
Issue
the
QUEUE
command
with
no
parameters
to
obtain
a
list
of
valid
queue
names.
Enter
the
command
again
with
the
correct
queue
name.
GTM7627I
QUEUE
COMMAND
TERMINATED,
SYNTAX
ERROR
Explanation:
The
QUEUE
command
was
entered
incorrectly.
The
only
currently
supported
option
of
the
QUEUE
command
is
the
RESET
option.
System
Action:
No
action
is
taken
and
processing
continues.
Administrator
Response:
Enter
the
command
again
with
the
correct
syntax,
which
is
either
QUEUE
or
QUEUE
RESET
queue_name.
Refer
to
the
IBM
Tivoli
Business
Systems
Manager
Command
Reference
for
more
information.
GTM7628I
QUEUE
COMMAND
TERMINATED,
DATASPACE
NOT
CONNECTED
Explanation:
The
QUEUE
command
was
entered
on
a
source/390
object
pump
or
an
object
server
that
is
not
connected
to
a
source/390
data
space.
System
Action:
No
action
is
taken
and
processing
continues.
Administrator
Response:
The
QUEUE
command
can
only
be
used
on
an
source/390
object
server
or
an
object
pump
that
is
currently
connected
to
a
data
space.
You
should
ensure
that
the
source/390
object
data
space
is
started
and
connected
to
the
source/390
object
server
or
object
pump
prior
to
using
the
QUEUE
command.
GTM7629I
QUEUE
COMMAND
COMPLETE
Explanation:
The
QUEUE
command
successfully
completed.
GTM7690E
UNABLE
TO
LOCATE
SUBSYSTEM.
SUBSYSTEM
NAME
IS
name.
PUMP
WILL
SHUTDOWN.
Explanation:
During
initialization,
the
source/390
object
pump
was
unable
to
locate
the
Tivoli
Business
Systems
Manager
subsystem
control
block.
Message
Variables:
name
-
The
name
of
the
Tivoli
Business
Systems
Manager
subsystem
System
Action:
The
source/390
object
pump
shuts
down.
Administrator
Response:
Keep
all
logs
and
contact
IBM
Software
Support.
GTM7702E
REXX
ENVIRONMENT
CREATE
FAILED
RC=return_code
REASON=reason_code
Explanation:
There
was
an
error
when
attempting
to
create
a
REXX
environment.
Message
Variables:
return_code
-
The
return
code
from
the
AOPRXENV
macro
reason_code
-
The
reason
code
from
the
AOPRXENV
macro
System
Action:
Processing
continues.
Administrator
Response:
Determine
if
the
address
space
is
able
to
load
the
necessary
REXX
modules.
Ensure
that
sufficient
region
storage
was
allocated
to
the
issuing
address
space.
If
this
does
not
resolve
the
problem,
contact
IBM
Software
Support.
GTM7703E
REXX
HOST
ENVIRONMENT
CREATE
FAILED
RC=return_code
Explanation:
There
was
an
error
creating
the
REXX
host
environment.
Message
Variables:
return_code
-
The
return
code
from
the
AOPRXENV
macro
System
Action:
Processing
continues
but
the
results
are
unpredictable.
Administrator
Response:
Determine
if
the
address
space
is
able
to
load
the
necessary
REXX
modules.
Ensure
that
sufficient
region
storage
was
allocated
to
the
issuing
address
space.
If
this
does
not
resolve
the
60
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
problem,
contact
IBM
Software
Support.
GTM7705E
DATASPACE
QPUT
FAILED
WITH
RC=return_code
Explanation:
There
was
an
error
attempting
to
store
a
record
to
a
data
space
queue.
Message
Variables:
return_code
-
The
return
code
from
the
operation
System
Action:
Processing
continues.
Administrator
Response:
Determine
if
the
Tivoli
Business
Systems
Manager
data
space
address
space
is
available.
If
the
problem
continues,
collect
all
logs
and
contact
IBM
Software
Support.
GTM7707E
CROSS
MEMORY
POST
FAILED
WITH
RC=return_code
Explanation:
There
was
an
error
attempting
a
cross
memory
post.
Message
Variables:
return_code
-
The
return
code
from
the
cross
memory
post
request
System
Action:
Processing
continues
but
the
results
are
unpredictable.
Administrator
Response:
Check
that
the
source/390
object
pump
exhausted
the
virtual
storage
to
which
it
was
available.
If
the
problem
continues,
contact
IBM
Software
Support.
GTM7800E
UNABLE
TO
OBTAIN
TRAP
STORAGE
Explanation:
There
was
insufficient
virtual
storage
available
to
create
a
trap.
System
Action:
The
source/390
object
pump
stops.
Administrator
Response:
The
error
indicates
that
the
source/390
object
pump
exhausted
the
virtual
storage
to
which
it
was
available.
Use
the
region
parameter
of
the
EXEC
JCL
card
to
increase
the
amount
of
virtual
storage
available.
GTM7801I
STORAGE
ALLOCATED
FOR
number
TRAPS
Explanation:
The
maximum
number
of
traps
that
can
be
created
is
displayed.
Message
Variables:
number
-
The
maximum
number
of
traps
that
can
be
created
System
Action:
Processing
continues.
GTM7802E
UNABLE
TO
OBTAIN
TRAP
QUEUE
HEADER
STORAGE
Explanation:
There
was
insufficient
virtual
storage
available
to
create
a
trap
queue
header.
System
Action:
The
source/390
object
pump
stops.
Administrator
Response:
The
error
indicates
that
the
source/390
object
pump
exhausted
the
virtual
storage
to
which
it
was
available.
Use
the
region
parameter
of
the
EXEC
JCL
card
to
increase
the
amount
of
virtual
storage
available.
GTM7803E
UNABLE
TO
OBTAIN
TRAP
INDEX
STORAGE
Explanation:
There
was
insufficient
virtual
storage
available
to
create
a
trap
queue
index.
System
Action:
The
source/390
object
pump
stops.
Administrator
Response:
The
error
indicates
that
the
source/390
object
pump
exhausted
the
virtual
storage
to
which
it
was
available.
Use
the
region
parameter
of
the
EXEC
JCL
card
to
increase
the
amount
of
virtual
storage
available.
GTM7811E
AOPPARM
GET
FAILURE
FOR
parameter
Explanation:
There
was
an
error
when
attempting
to
obtain
the
indicated
parameter.
Message
Variables:
parameter
-
The
parameter
being
requested
at
the
time
of
the
error
System
Action:
Processing
continues
but
the
RODM
interface
functionality
is
unavailable.
Administrator
Response:
This
message
is
an
indication
of
a
prior
failure.
Examine
preceding
messages
for
the
appropriate
course
of
action.
GTM7812E
EKG_CONNECT
RC=return_code
REASON=reason_code
Explanation:
A
return
code
that
was
not
valid
was
received
from
the
EKG_CONNECT
call.
Message
Variables:
return_code
-
The
EKG_CONNECT
return
code
value
reason_code
-
The
EKG_CONNECT
reason
code
value
System
Action:
Processing
continues
but
the
RODM
interface
functionality
is
unavailable.
Administrator
Response:
Determine
the
source
of
the
incorrect
message.
Refer
to
the
IBM
Tivoli
NetView
for
z/OS
RODM
and
GMFHS
Programming
Guide
for
more
information.
If
the
problem
cannot
be
resolved,
collect
all
logs
and
contact
IBM
Software
Support.
Chapter
1.
Source/390
Messages
-
GTM0001I
-
GTM8665E
61
GTM7813I
type
RC=return_code
REASON=reason_code
Explanation:
An
error
occurred
during
a
request
to
RODM.
Message
Variables:
type
-
The
type
of
RODM
request
return_code
-
The
return
code
from
the
request
reason_code
-
The
reason
code
from
the
request
System
Action:
Processing
continues
but
results
are
unpredictable.
Administrator
Response:
Determine
the
source
of
the
incorrect
message.
Refer
to
the
IBM
Tivoli
NetView
for
z/OS
RODM
and
GMFHS
Programming
Guide
for
more
information.
If
the
problem
cannot
be
resolved,
collect
all
logs
and
contact
IBM
Software
Support.
GTM7815I
TBSM
HAS
CONNECTED
TO
RODM
:
name
Explanation:
Tivoli
Business
Systems
Manager
successfully
connected
to
the
named
RODM
system.
Message
Variables:
name
-
The
name
of
the
RODM
system
System
Action:
Processing
continues.
GTM7816I
TBSM
HAS
DISCONNECTED
FROM
RODM
:
name
Explanation:
Tivoli
Business
Systems
Manager
successfully
disconnected
from
the
named
RODM
system.
Message
Variables:
name
-
The
name
of
the
RODM
system
System
Action:
Processing
continues.
GTM7817I
TBSM
RODM:
name
TERMINATION
DETECTED.
Explanation:
Tivoli
Business
Systems
Manager
detected
that
the
named
RODM
system
stopped.
Message
Variables:
name
-
The
name
of
the
RODM
system
System
Action:
Processing
continues.
Tivoli
Business
Systems
Manager
automatically
reconnects
to
RODM
when
it
is
available.
GTM7818I
TBSM
RODM
:
MISSING
OR
INVALID
DATA
IN
NOTIFY
MSG
:
text
Explanation:
Tivoli
Business
Systems
Manager
detected
data
that
is
not
valid
in
the
notify
message
received
from
RODM.
Message
Variables:
text
-
The
text
of
the
message
being
processed
System
Action:
Processing
continues.
The
message
is
ignored.
Administrator
Response:
Determine
the
source
of
the
incorrect
message.
Refer
to
the
IBM
Tivoli
NetView
for
z/OS
RODM
and
GMFHS
Programming
Guide
for
more
information.
If
the
problem
cannot
be
resolved,
collect
all
logs
and
contact
IBM
Software
Support.
GTM7819I
TBSM:
state
Explanation:
This
is
a
RODM
status
message.
Message
Variables:
state
-
The
state
of
the
RODM
connection
System
Action:
Processing
continues.
GTM7820I
TBSM:
COMMAND
OPTION
MUST
BE
START
OR
STOP
Explanation:
An
incorrect
option
was
specified
on
the
command
sent
to
RODM
to
start
or
stop
the
RODM
interface.
System
Action:
Processing
continues.
Administrator
Response:
Enter
the
command
again
in
the
correct
format.
Refer
to
the
IBM
Tivoli
Business
Systems
Manager
Command
Reference
for
more
information.
GTM7821E
TBSM:
ALREADY
CONNECTED
TO
RODM
Explanation:
An
attempt
was
made
to
start
the
RODM
connection
when
it
was
already
active.
System
Action:
Processing
continues.
GTM7822E
TBSM:
ALREADY
DISCONNECTED
FROM
RODM
Explanation:
A
request
was
made
to
stop
the
RODM
connection
when
it
was
not
active
System
Action:
Processing
continues.
GTM7823E
TBSM:
RODM
NOT
AVAILABLE.
AWAITING
RODM:
name
Explanation:
An
attempt
was
made
to
start
the
RODM
connection
when
RODM
was
not
available.
Message
Variables:
name
-
The
name
of
the
RODM
system
System
Action:
Tivoli
Business
Systems
Manager
suspends
the
RODM
processing
until
the
named
RODM
system
becomes
available.
62
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
Administrator
Response:
Ensure
that
the
RODM
task
is
activated.
GTM7824I
TBSM
:
RODM
DATA
MODEL
IS
COMPLETED
Explanation:
The
NetView
data
model
load
program
EKGLOTLM
was
submitted
and
acknowledged
by
the
pump
to
begin
to
wait
for
the
network
topology
data
to
be
loaded
into
RODM.
System
Action:
Processing
continues.
GTM7825I
TBSM
:
RODM
STARTED
TO
LOAD
NETWORK
TOPOLOGY
Explanation:
The
object
pump
is
waiting
on
the
RODM_QUERY_MODEL_TIME
time
value
for
the
SNA
topology
manager
to
load
the
network
data
into
RODM.
System
Action:
Processing
continues.
GTM7826I
TBSM
:
RODM
NETWORK
IS
LOADED
AND
MONITORING
IS
ACTIVE
Explanation:
The
RODM_QUERY_MODEL_TIME
expired
and
Tivoli
Business
Systems
Manager
is
sent
an
acknowledgement
that
RODM
is
running.
System
Action:
Processing
continues.
Administrator
Response:
If
any
network
objects
are
posted
with
a
RODM
response
message
containing
a
return
code
of
8
and
a
reason
code
of
54,
it
is
possible
that
the
RODM_QUERY_MODEL_TIME
value
was
not
long
enough
to
wait
for
RODM
to
be
loaded
before
the
object
pump
sent
the
RODM
acknowledgement
request
to
Tivoli
Business
Systems
Manager.
The
RODM_QUERY_MODEL_TIME
value
might
need
to
be
increased.
See
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide
for
more
information
about
this
parameter.
GTM7831E
ABEND
DETECTED
PROGRAM=pgm
EXCEPTION
TERMINATED
EXCEPTION
NAME=exception
Explanation:
A
program,
which
is
being
used
by
the
named
exception,
abended.
Message
Variables:
pgm
-
The
name
of
the
program
that
abended
exception
-
The
name
of
the
exception
for
which
the
program
was
being
run
System
Action:
The
exception
is
no
longer
processed.
Administrator
Response:
Keep
the
SVC
dump
that
is
provided
and
any
job
logs
and
contact
IBM
Software
Support.
GTM7832E
ERROR
REMOVING
REPORTER
PROGRAM
pgm
Explanation:
An
error
was
encountered
while
removing
a
definition
for
the
program.
This
is
an
internal
error.
Message
Variables:
pgm
-
The
program
name
from
which
the
remove
request
was
running
System
Action:
Processing
continues.
Administrator
Response:
Keep
any
job
logs
and
contact
IBM
Software
Support.
GTM7833E
ERROR
REMOVING
COLLECTOR
PROGRAM
pgm
Explanation:
An
error
was
encountered
while
removing
a
definition
for
the
program.
This
is
an
internal
error.
Message
Variables:
pgm
-
The
program
name
from
which
the
remove
request
was
running
System
Action:
Processing
continues.
Administrator
Response:
Keep
any
job
logs
and
contact
IBM
Software
Support.
GTM7835E
UNABLE
TO
OBTAIN
STORAGE
FOR
AOPMNEXP
Explanation:
The
system
was
unable
to
allocate
enough
virtual
storage
to
add
an
exception.
System
Action:
Processing
continues.
Some
exceptions
might
be
unavailable.
Administrator
Response:
The
error
indicates
that
the
source/390
object
pump
exhausted
the
virtual
storage
to
which
it
was
available.
Use
the
region
parameter
of
the
EXEC
JCL
card
to
increase
the
amount
of
virtual
storage
available.
GTM7836E
ERROR
DEFINING
REPORTER
PROGRAM
pgm
Explanation:
An
error
was
encountered
while
adding
a
definition
for
a
program.
This
is
an
internal
error.
Message
Variables:
pgm
-
The
name
of
the
program
being
defined
System
Action:
Processing
continues.
Some
exceptions
might
be
unavailable.
Administrator
Response:
Keep
any
job
logs
and
contact
IBM
Software
Support.
GTM7837E
ERROR
DEFINING
COLLECTOR
PROGRAM
pgm
Explanation:
An
error
was
encountered
while
adding
a
definition
for
a
program.
Chapter
1.
Source/390
Messages
-
GTM0001I
-
GTM8665E
63
Message
Variables:
pgm
-
The
name
of
the
program
being
defined
System
Action:
Processing
continues.
Some
exceptions
might
be
unavailable.
Administrator
Response:
Keep
any
job
logs
and
contact
IBM
Software
Support.
GTM7838E
EXCEPTION
PREVIOUSLY
DEFINED,
EXCEPTION=exception
Explanation:
An
attempt
was
made
to
add
an
exception
which
already
exists.
This
is
an
internal
error.
Message
Variables:
exception
-
The
name
of
the
exception
for
which
the
request
was
made
System
Action:
Processing
continues.
The
existing
exception
is
not
affected.
Administrator
Response:
Keep
any
job
logs
and
contact
IBM
Software
Support.
GTM7839E
INVALID
MONITOR
REQUEST
TYPE
REQUEST
IGNORED
Explanation:
A
request
that
was
not
valid
was
made
to
the
monitor
subtask.
This
is
an
internal
error.
System
Action:
Results
are
unpredictable.
Administrator
Response:
Keep
any
job
logs
and
contact
IBM
Software
Support.
GTM7840E
INVALID
MONITOR
REQUEST
BLOCK
REQUEST
QUEUE
CLEARED
Explanation:
A
request
that
was
not
valid
was
made
to
the
monitor
subtask.
This
is
an
internal
error.
System
Action:
Results
are
unpredictable.
Administrator
Response:
Keep
any
job
logs
and
contact
IBM
Software
Support.
GTM7841E
LOAD
OF
MODULE
AOPMNPRG
FAILED
RC=return_code
Explanation:
The
load
of
the
module
AOPMNPRG
was
unsuccessful.
This
module
is
required
for
the
successful
operation
of
the
monitor
subtask.
Message
Variables:
return_code
-
The
return
code
from
the
load
request
System
Action:
Processing
continues.
No
exceptions
are
available.
Administrator
Response:
Keep
any
job
logs
and
contact
IBM
Software
Support.
GTM7842E
UNABLE
TO
OBTAIN
WORKING
STORAGE
Explanation:
The
monitor
subtask
is
unable
to
obtain
the
required
working
storage.
System
Action:
Processing
continues,
but
the
results
are
unpredictable.
Administrator
Response:
The
error
indicates
that
the
source/390
object
pump
exhausted
the
virtual
storage
available.
Use
the
region
parameter
of
the
EXEC
JCL
card
to
increase
the
amount
of
virtual
storage
available.
GTM7843E
GLOBAL
VARIABLE
RETRIEVE
FAILED
RC=return_code
Explanation:
An
error
was
encountered
while
accessing
a
global
variable
required
during
event
notification.
Message
Variables:
return_code
-
The
return
codes
from
the
global
variable
retrieve
System
Action:
Processing
continues,
but
the
results
are
unpredictable.
Administrator
Response:
This
message
should
be
preceded
by
other
messages.
Use
those
messages
to
investigate
the
cause
of
the
failure.
If
there
is
still
a
problem,
keep
any
job
logs
and
contact
IBM
Software
Support.
GTM7844E
DATASPACE
QPUT
FAILED
WITH
RC=return_code
Explanation:
A
failure
occurred
while
writing
a
notification
to
the
source/390
data
space.
Message
Variables:
return_code
-
The
return
code
from
the
queue
put
operation
System
Action:
Processing
continues,
but
the
results
are
unpredictable.
Administrator
Response:
This
message
should
be
preceded
by
other
messages.
Use
those
messages
to
investigate
the
cause
of
the
failure.
If
there
is
still
a
problem,
keep
any
job
logs
and
contact
IBM
Software
Support.
GTM7845E
CROSS
MEMORY
POST
FAILED
WITH
RC=return_code
Explanation:
A
failure
occurred
during
cross
memory
post
processing.
Message
Variables:
return_code
-
The
return
code
from
the
post
operation
System
Action:
Processing
continues,
but
the
results
are
unpredictable.
Administrator
Response:
Check
that
the
source/390
object
server
address
space
is
active.
If
there
is
still
a
64
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
problem,
keep
any
job
logs
and
contact
IBM
Software
Support.
GTM7851E
UNABLE
TO
OBTAIN
LOCAL
AREA
FOR
PROGRAM
pgm
LENGTH=length
Explanation:
The
monitor
subtask
is
unable
to
obtain
the
required
storage.
Message
Variables:
pgm
-
The
program
for
which
the
request
was
being
made
length
-
The
amount
of
virtual
storage
being
requested
System
Action:
Processing
continues,
but
some
exceptions
might
not
available.
Administrator
Response:
The
error
indicates
that
the
source/390
object
pump
exhausted
the
virtual
storage
to
which
it
was
available.
Use
the
region
parameter
of
the
EXEC
JCL
card
to
increase
the
amount
of
virtual
storage
available.
GTM7852E
INVALID
AOPMNPRG
REMOVE
REQUEST
Explanation:
The
monitor
subtask
program
manger
received
a
remove
program
request
that
was
not
valid.
This
is
an
internal
error.
System
Action:
Processing
continues,
but
some
exceptions
might
not
be
available.
Administrator
Response:
Keep
any
job
logs
and
contact
IBM
Software
Support.
GTM7853E
LOAD
FAILED
FOR
MONITOR
PROGRAM
pgm
RC=return_code
Explanation:
The
system
was
unable
to
load
the
required
monitor
program.
Message
Variables:
pgm
-
The
name
of
the
program
the
system
was
attempting
to
load
return_code
-
The
return
code
from
the
load
request
System
Action:
Processing
continues,
but
some
exceptions
might
not
be
available.
Administrator
Response:
Keep
any
job
logs
and
contact
IBM
Software
Support.
GTM7854E
UNABLE
TO
OBTAIN
AOPMNPRG
STORAGE
LENGTH=pgm
Explanation:
The
monitor
subtask
is
unable
to
obtain
the
required
storage.
Message
Variables:
pgm
-
The
length
of
the
virtual
storage
requested
System
Action:
Processing
continues,
but
some
exceptions
might
not
be
available.
Administrator
Response:
The
error
indicates
that
the
source/390
object
pump
exhausted
the
available
virtual
storage.
Use
the
region
parameter
of
the
EXEC
JCL
card
to
increase
the
storage
amount.
GTM7855E
INVALID
AOPMNPRG
ADD
REQUEST
Explanation:
The
monitor
subtask
program
manger
received
an
add
program
request
that
was
not
valid.
This
is
an
internal
error.
System
Action:
Processing
continues,
but
the
results
are
unpredictable.
Administrator
Response:
Keep
any
job
logs
and
contact
IBM
Software
Support.
GTM7856E
INVALID
MONITOR
PROGRAM
REQUEST
TYPE
SUPPLIED
Explanation:
The
monitor
subtask
program
manger
received
a
request
that
is
not
valid.
System
Action:
Processing
continues,
but
the
results
are
unpredictable.
Administrator
Response:
Keep
any
job
logs
and
contact
IBM
Software
Support.
GTM7857E
UNABLE
TO
OBTAIN
WORKING
STORAGE
FOR
AOPMNMPG
Explanation:
The
monitor
subtask
was
unable
to
obtain
the
required
storage.
System
Action:
Processing
continues,
but
no
exceptions
are
available.
Administrator
Response:
The
error
indicates
that
the
source/390
object
pump
exhausted
the
virtual
storage
to
which
it
was
available.
Use
the
region
parameter
of
the
EXEC
JCL
card
to
increase
the
amount
of
virtual
storage
available.
GTM7858E
ERROR
RECEIVED
FROM
PROGRAM
pgm
DURING
INIT|TERM.
RC=return_code
Explanation:
A
return
code
that
was
not
valid
was
received
during
an
Initialize
or
Terminate
request
to
a
monitoring
program.
Message
Variables:
pgm
-
The
name
of
the
program
return_code
-
The
return
code
received
System
Action:
Processing
continues,
but
some
exceptions
might
not
be
available.
Administrator
Response:
Keep
any
job
logs
and
contact
IBM
Software
Support.
Chapter
1.
Source/390
Messages
-
GTM0001I
-
GTM8665E
65
GTM7860E
text
Explanation:
This
message
was
issued
during
the
processing
of
a
SHOW
EXCPS
command.
The
text
can
be
one
of
the
following
messages:
MONITOR
SUBTASK
IS
NOT
ACTIVE
The
monitor
subtask
was
not
active.
AOPMONS
:
UNABLE
TO
OBTAIN
AOPSTG
STORAGE
The
source/390
object
pump
was
unable
to
obtain
sufficient
virtual
storage.
OPTION
command_option
IS
INVALID,
SPECIFY
LONG
OR
NOLIST
There
was
an
option
detected
that
was
not
valid.
Message
Variables:
command_option
-
The
option
that
was
not
recognized
System
Action:
The
SHOW
EXCPS
command
ends.
Administrator
Response:
If
the
Monitor
subtask
was
not
active,
keep
any
job
logs
and
contact
IBM
Software
Support.
If
the
source/390
object
pump
was
unable
to
obtain
sufficient
virtual
storage,
use
the
region
parameter
of
the
EXEC
JCL
card
to
increase
the
amount
of
virtual
storage
available.
If
the
command
option
was
not
valid,
correct
the
syntax
and
issue
the
command
again.
GTM7861I
exception
STATUS
status
MATCHED
count
OF
executed
Explanation:
The
current
status
of
an
exception
is
displayed.
Message
Variables:
exception
-
The
exception
name
status
-
The
current
status
of
the
exception,
which
is
True
or
False
count
-
The
number
of
times
the
exception
was
evaluated
executed
-
The
number
of
times
the
exception
ran
System
Action:
Processing
continues.
GTM7862I
text
Explanation:
The
text
of
this
message
is
variable.
It
displays
detailed
information
relating
to
an
exception.
It
is
produced
in
relation
to
the
SHOW
EXCPS
command.
Message
Variables:
text
-
The
detail
about
the
exception
System
Action:
Processing
continues.
GTM7863I
TOTAL
NUMBER
OF
EXCEPTIONS=count
Explanation:
The
number
of
exceptions
processed
by
the
SHOW
command
are
displayed.
Message
Variables:
count
-
The
parameter
being
processed
System
Action:
Processing
continues.
GTM7870E
AOPPARM
GET
FAILURE
FOR
parameter
Explanation:
A
failure
occurred
while
attempting
to
read
a
parameter
for
the
RMF
collector.
Message
Variables:
parameter
-
The
parameter
being
processed
System
Action:
Processing
continues.
The
results
are
unpredictable.
Administrator
Response:
This
message
should
be
preceded
by
other
messages.
Use
those
messages
to
investigate
the
cause
of
the
failure.
If
there
is
still
a
problem,
keep
any
job
logs
and
contact
IBM
Software
Support.
GTM7871E
INVALID
parameter
PARM
SPECIFIED
DATA
WAS
value
Explanation:
The
value
specified
for
the
parameter
was
not
valid.
Message
Variables:
parameter
-
The
parameter
name
being
processed
value
-
The
value
specified
System
Action:
Processing
continues.
The
results
are
unpredictable.
Administrator
Response:
Correct
the
parameter
and
start
the
source/390
object
pump
again.
GTM7872E
REQUIRED
parameter
PARM
NOT
FOUND
Explanation:
A
required
parameter
was
not
specified.
Message
Variables:
parameter
-
The
name
of
the
parameter
which
was
not
specified
System
Action:
Processing
continues.
The
results
are
unpredictable.
Administrator
Response:
Refer
to
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide
for
the
parameter.
Correct
the
parameter
and
restart
the
address
space.
66
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
GTM7873I
TCP/IP
INTERFACE
UNAVAILABLE
Explanation:
The
initialization
of
the
internet
protocol
interface
did
not
complete.
The
RMF
collector
ends.
System
Action:
Processing
continues.
RMF
monitoring
is
not
available.
Administrator
Response:
This
might
be
because
the
IP
is
not
available
on
this
system.
If
so,
this
is
an
informational
message.
If
this
message
is
issued
because
of
an
error,
it
will
be
preceded
by
other
messages.
Use
those
messages
to
investigate
the
error.
GTM7874E
ERROR
DURING
TCP/IP
type
REQUEST
RC=return_code
REASON=reason_code
Explanation:
An
IP
request
failed.
Message
Variables:
type
-
The
type
of
request
that
failed
return_code
-
The
hexadecimal
representation
of
the
return
code
reason_code
-
The
hexadecimal
representation
of
the
reason
code
System
Action:
Processing
continues.
The
results
are
unpredictable.
Administrator
Response:
Investigate
the
meaning
of
the
return
and
reason
codes.
If
this
does
not
resolve
the
problem,
keep
any
job
logs
and
contact
IBM
Software
Support.
GTM7875E
INTERNAL
ERROR
UNABLE
TO
LOCATE
TCP/IP
GLOBAL
AREA
Explanation:
The
RMF
collector
was
unable
to
locate
the
IP
global
error.
System
Action:
Processing
continues.
Some
RMF
monitoring
might
not
be
available.
Administrator
Response:
Keep
any
job
logs
and
contact
IBM
Software
Support.
GTM7876E
INTERNAL
ERROR
TCP/IP
GLOBAL
AREA
INACTIVE
Explanation:
The
RMF
collector
found
the
IP
Global
area
was
inactive.
System
Action:
Processing
continues.
Some
RMF
monitoring
might
not
be
available.
Administrator
Response:
Keep
any
job
logs
and
contact
IBM
Software
Support.
GTM7877E
UNABLE
TO
OBTAIN
BUFFER
STORAGE
FOR
RMF
PROCESSING
Explanation:
The
RMF
collector
is
unable
to
obtain
the
required
storage.
System
Action:
Processing
continues.
Some
RMF
monitoring
might
not
be
available.
Administrator
Response:
The
error
indicates
that
the
source/390
object
pump
exhausted
the
virtual
storage
to
which
it
is
available.
Use
the
region
parameter
of
the
EXEC
JCL
card
to
increase
the
amount
of
virtual
storage
available.
GTM7878E
UNABLE
TO
LOCATE
TCP/IP
ADDRESS
SPACE
Explanation:
The
RMF
collector
is
unable
to
locate
an
active
IP
address
space
with
which
to
communicate.
System
Action:
Processing
continues.
RMF
monitoring
is
not
available.
Administrator
Response:
Ensure
that
internet
protocol
is
active
on
the
system.
Specify
the
TCPIP_TASKNAME
parameter
to
direct
the
RMF
monitor
to
a
specific
address
space.
GTM7879E
TCP/IP
INDICATES
THAT
TCPIP_TASKNAME=value
IS
INVALID
Explanation:
The
value
specified
in
the
TCPIP_TASKNAME
parameter
is
rejected
by
the
IP
interface.
Message
Variables:
value
-
The
value
specified
in
the
TCPIP_TASKNAME
parameter
System
Action:
Processing
continues.
RMF
monitoring
is
not
available.
Administrator
Response:
Ensure
that
internet
protocol
is
active
on
the
system.
Ensure
that
the
value
specified
in
the
TCPIP_TASKNAME
parameter
is
valid
and
corresponds
to
the
name
of
the
TCP/IP
address
space
on
the
operating
system
where
the
source/390
object
pump
is
running.
GTM7880E
INVALID
RMF
REPORTER
PARM
SUPPLIED
parameter
Explanation:
The
parameter
passed
to
the
RMF
reporter
during
the
registration
process
is
not
valid.
Message
Variables:
parameter
-
The
parameter
passed
to
the
RMF
reporter
program
System
Action:
The
exception,
which
is
in
the
process
of
being
defined,
is
not
added.
Administrator
Response:
Keep
any
job
logs
and
contact
IBM
Software
Support.
Chapter
1.
Source/390
Messages
-
GTM0001I
-
GTM8665E
67
GTM7881E
PPI
INTERFACE
IS
INACTIVE
Explanation:
The
PPI
Manager
task
is
not
running.
System
Action:
Processing
continues.
Tivoli
Business
Systems
Manager
cannot
receive
information
by
way
of
the
PPI
interface.
Administrator
Response:
Verify
that
the
object_pump
startup
parameter
(PPI=YES)
is
specified.
GTM7882E
GETMAIN
FAILED
FOR
PPI
RECEIVE
BUFFER
Explanation:
Tivoli
Business
Systems
Manager
was
unable
to
allocate
virtual
storage
for
a
receive
buffer.
System
Action:
Processing
continues.
Tivoli
Business
Systems
Manager
cannot
receive
information
by
way
of
the
PPI
interface.
Administrator
Response:
The
error
indicates
that
the
available
virtual
storage
was
exhausted
by
the
source/390
object
pump.
Use
the
region
parameter
of
the
EXEC
JCL
card
to
increase
the
amount
of
virtual
storage
available.
GTM7883E
PPI
RECEIVER
LOST
COMMUNICATION
Explanation:
The
PPI
lost
communication
with
the
NetView
subsystem.
Administrator
Response:
Start
the
NetView
subsystem
(SSI).
Enable
the
PPI
by
issuing
the
following
command:
F
object_pump,PPI
ENABLE
GTM7884I
category
MESSAGES
RECEIVED:
count
Explanation:
This
message
identifies
the
number
of
messages
received
from
the
PPI.
Refer
to
the
SHOW
PPI
command.
Message
Variables:
category
-
The
category
of
messages
count
-
The
count
of
messages
received
System
Action:
Processing
continues.
GTM7885E
type
FAILED
FOR
PPI
-
DTR=value
RC=return_code
Explanation:
A
PPI
function
failed
for
the
requested
PPI
DTR
request.
Message
Variables:
type
-
The
type
of
PPI
function
value
-
The
DTR
value
from
the
request
return_code
-
The
return
code
from
the
request
System
Action:
Processing
continues.
Administrator
Response:
Refer
to
the
IBM
Tivoli
NetView
for
z/OS
Application
Programmer’s
Guide
to
identify
the
return
code
for
the
DTR
type
request.
Also,
refer
to
the
problem
determination
and
troubleshooting
section
for
appropriate
action.
GTM7887E
PPI
OPTION
IS
INVALID
Explanation:
A
PPI
command
that
was
not
valid
was
entered.
System
Action:
Processing
continues
and
no
action
is
taken.
Administrator
Response:
Refer
to
the
object_pump
command
usage
documentation
referencing
the
PPI
commands.
GTM7888I
PPI
TRACE
IS
status
Explanation:
This
message
indicates
the
status
of
the
PPI
trace
facility.
Message
Variables:
status
-
The
status
of
the
PPI
trace
facility.
The
possible
values
are
as
follows:
*
ACTIVE
The
PPI
trace
is
enabled.
The
PPI
messages
received
are
written
to
the
AOPLOG
DD
name.
*
INACTIVE
The
PPI
trace
is
disabled.
System
Action:
Processing
continues.
GTM7889I
PPI
BUFFER
QUEUE
LIMIT
IS
limit
Explanation:
The
Buffer
Queue
Limit
number
is
displayed
when
the
PPI
RESET
queue_limit
command
is
issued.
Note:
Refer
to
the
IBM
Tivoli
NetView
for
z/OS
documentation
regarding
PPI
usage
to
determine
when
it
might
be
appropriate
to
change
this
value.
The
PPI_BUFFER_QUEUE_LIMIT
startup
parameter
for
the
object_pump
initially
sets
this
value.
Message
Variables:
limit
-
The
buffer
queue
limit
System
Action:
Processing
continues.
GTM7890I
PPI
RECEIVER
IS
status
Explanation:
This
message
indicates
the
status
of
the
PPI
receiver.
Message
Variables:
status
-
The
status
of
the
PPI
receiver
might
indicate
one
of
the
following:
*
ACTIVE
The
PPI
receiver
is
running.
*
INACTIVE
The
PPI
receiver
is
not
running.
System
Action:
Processing
continues.
Administrator
Response:
When
the
PPI
is
ACTIVE,
68
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
no
action
is
necessary.
When
the
PPI
is
INACTIVE,
refer
to
the
problem
determination
and
troubleshooting
section
in
the
IBM
Tivoli
NetView
for
z/OS
documentation
for
enabling
the
PPI
interface.
GTM7900W
FREEMAIN
FAILED
CSECT=pgm
OFFSET=address
R15=return_code
PROCESS
CONTINUING
Explanation:
A
FREEMAIN
macro
failed.
Message
Variables:
pgm
-
The
program
name
address
-
The
address
that
was
being
released
return_code
-
The
return
code
from
the
FREEMAIN
macro
System
Action:
Processing
continues
but
results
are
unpredictable.
Administrator
Response:
Determine
why
the
FREEMAIN
macro
failed.
If
necessary,
contact
IBM
Software
Support.
GTM8000E
SEND
-
NO
DATA
TO
SEND
Explanation:
The
data
address
and
length
was
not
provided
on
the
AOPIPR
SEND
function
call.
System
Action:
Processing
continues
but
the
data
is
not
sent.
Administrator
Response:
Check
the
data
provided
to
the
GTMAOPE0
utility.
If
this
message
is
reported
when
not
using
the
GTMAOPE0
utility,
collect
all
logs
and
contact
IBM
Software
Support.
GTM8001E
function
-
NO
CONNECTION
EXISTS
Explanation:
An
attempt
was
made
to
perform
the
specified
AOPIPR
function,
but
it
was
not
connected.
Message
Variables:
function
-
The
function,
which
can
be
DISCONNECT,
SEND,
or
RECEIVE
System
Action:
Processing
continues.
Administrator
Response:
Collect
all
logs
and
contact
IBM
Software
Support.
GTM8002E
SEND
-
GETMAIN
identifier
FAILED
FOR
SEND
BUFFER
Explanation:
The
amount
of
storage
was
insufficient.
Message
Variables:
identifier
-
A
unique
number
specifying
which
GETMAIN
macro
failed
System
Action:
Processing
continues
but
results
are
unpredictable.
Administrator
Response:
Check
the
region
size
to
determine
if
it
must
be
increased.
GTM8003E
function
-
TCPIP_SERVICE
FAILED
TO
LOAD
Explanation:
The
tcpip_service
API
is
unable
to
load
and
process
the
IP
function.
Message
Variables:
function
-
The
function,
which
can
be
CONNECT,
DISCONNECT,
SEND,
RECEIVE,
or
GETIPADDRESS
System
Action:
Processing
continues
but
results
are
unpredictable.
Administrator
Response:
Check
the
TCP/IP
address
space.
The
address
space
might
not
be
available.
GTM8004E
function
-
tcpip_service
FAILED
RC=return_code
Explanation:
The
tcpip_service
API
function
failed
with
the
return
code
indicated.
Message
Variables:
function
-
The
API
function,
which
can
be
GTMIPSND,
GTMIPRCV,
or
GTMIPREV.
tcpip_service
-
The
TCP/IP
service,
which
can
be
CONNECT,
DISCONNECT,
SEND,
RECEIVE,
GETHBADR,
or
GETIPADDRESS.
return_code
-
The
return
code
for
the
API
function
that
failed.
If
GETHBADR
fails,
the
return
code
is
00000.
System
Action:
Processing
continues
but
results
are
unpredictable.
When
GETHBADR
fails,
the
IP
receive
task
ends.
Administrator
Response:
Refer
to
the
appropriate
API
reference
document
in
the
TCP/IP
for
z/OS
library
for
more
information
about
the
return
code.
For
a
GETHBADR
failure,
add
the
VALIDCLIENT_HOSTRES=NO
card
to
the
Object
Server
control
cards.
GTM8005E
function
-
NO
CARRIAGE
CONTROL
CHARACTER
FOUND
Explanation:
The
AOPIPR
interface
processed
a
data
element
that
did
not
end
with
the
ASCII
carriage
control
character
X'0A'.
Message
Variables:
function
-
The
function,
which
can
be
SEND
or
RECEIVE
System
Action:
Processing
continues
but
results
are
unpredictable.
Administrator
Response:
This
is
an
internal
error.
Contact
IBM
Software
Support.
GTM8006E
SEND
-
DATA
LENGTH
EXCEEDS
BUFFER
SIZE
Explanation:
You
attempted
to
send
a
data
element
that
exceeded
the
maximum
buffer
size.
System
Action:
Processing
continues.
Chapter
1.
Source/390
Messages
-
GTM0001I
-
GTM8665E
69
Administrator
Response:
Collect
all
logs
and
contact
IBM
Software
Support.
GTM8007E
RECEIVE
-
CONVERT
NOT
SPECIFIED
Explanation:
You
did
not
specify
the
CONVERT
option
on
the
AOPIPR
RECEIVE
function
call.
The
AOPIPR
RECEIVE
function
did
not
receive
a
proper
response
message
from
the
socket
that
is
in
communication
on
the
other
end.
System
Action:
Processing
continues
but
results
are
unpredictable.
Administrator
Response:
Specify
CONVERT=’YES’
on
the
receive
function
call.
GTM8008E
CONNECT
-
GETMAIN
FAILED
FOR
iprstg
STORAGE
Explanation:
There
is
insufficient
storage
because
the
iprstg
storage
area
was
not
obtained
during
the
CONNECT
function
request.
Message
Variables:
iprstg
-
The
name
of
the
storage
area,
which
is
IPST
or
TCCB
System
Action:
The
connection
fails.
Administrator
Response:
Check
the
region
size.
The
region
size
might
have
to
be
increased.
GTM8009E
CONNECT
-
IP
ADDRESS
AND
PORT
REQUIRED
Explanation:
The
IPADDR
or
PORT
value
specified
is
not
provided
for
the
AOPIPR
CONNECT
function.
System
Action:
The
connection
fails.
Administrator
Response:
Provide
a
valid
IP
address
and
port
number.
GTM8010E
CONNECT
-
INVALID
BUFFER
SIZE
Explanation:
The
BUFFER_SIZE
operand
specified
on
the
AOPIPR
CONNECT
function
is
incorrect.
System
Action:
The
connection
fails.
Administrator
Response:
Verify
that
the
value
for
the
BUFFER_SIZE
operand
is
in
the
range
1–33.
GTM8011E
GET
IP
ADDRESS
-
HOST
NAME
NOT
FOUND
Explanation:
The
name
provided
with
the
TCPIP_SERVER_NAME
operand
for
the
AOPIPR
GETIPADDRESS
function
cannot
be
found.
System
Action:
The
connection
fails.
Administrator
Response:
Verify
that
the
name
used
with
the
TCPIP_SERVER_NAME
operand
is
configured
in
the
LOCAL.HOST
data
set
used
by
TCP/IP
for
z/OS.
GTM8012E
GET
IP
ADDRESS
-
INVALID
TCPIP
NAME
Explanation:
The
name
that
is
provided
with
the
TCPIP_SERVER_NAME
operand
for
the
AOPIPR
GETIPADDRESS
function
is
incorrect.
System
Action:
The
connection
fails.
Administrator
Response:
Verify
that
the
TCPIP_SERVER_NAME
operand
is
alphanumeric.
The
length
can
be
in
the
range
1–24
characters
in
length.
GTM8013E
CONVERT
IP
ADDRESS
-
INVALID
TCPIP
ADDRESS
Explanation:
The
IP
address
that
is
provided
with
the
TCPIP_SERVER_ADDRESS
operand
for
the
AOPIPR
CONVERTIPADDRESS
function
is
incorrect.
System
Action:
The
connection
fails.
Administrator
Response:
Verify
that
the
TCPIP_SERVER_ADDRESS
operand
contains
a
valid
TCP/IP
address
in
character-based
format.
GTM8014E
CONVERT
PORTNUM
-
INVALID
TCPIP
PORT
NUMBER
Explanation:
The
port
number
that
is
provided
with
the
TCPIP_SERVER_PORT
operand
for
the
AOPIPR
CONVERTIPADDRESS
function
is
incorrect.
System
Action:
The
connection
fails.
Administrator
Response:
Verify
that
the
TCPIP_SERVER_PORT
operand
contains
a
valid
TCP/IP
port
number.
The
number
is
in
the
range
1–32767.
GTM8015E
function
-
STIMER
SET
FAILED
FOR
TCPIP_SERVICE
return_code
Explanation:
The
requested
function
failed
when
attempting
to
start
the
timer
for
the
tcpip_service
call.
Message
Variables:
function
-
The
function
that
failed,
which
is
one
of
the
following:
v
CONNECT
v
DISCONNECT
v
SEND
v
RECEIVE
v
GETIPADDRESS
return_code
-
The
return
code
System
Action:
Processing
continues
but
results
are
unpredictable.
Administrator
Response:
Refer
to
the
MVS
macro
services
for
the
return
code
associated
with
the
STIMER
function.
70
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
GTM8016E
function
-
TIMEOUT
OCCURRED
FOR
TCPIP_SERVICE
Explanation:
The
tcpip_service
did
not
complete
processing
prior
to
the
TIMEOUT
value
specified
on
the
function
request.
Message
Variables:
function
-
The
function
that
failed,
which
is
one
of
the
following:
v
CONNECT
v
DISCONNECT
v
SEND
v
RECEIVE
v
GETIPADDRESS
System
Action:
Processing
continues
but
results
are
unpredictable.
Administrator
Response:
Verify
that
the
receiving
end
of
the
TCP/IP
connection
is
available
for
use.
GTM8017E
function
-
UNRECOGNIZED
EVENT
OCCURRED
FOR
TCPIP_SERVICE
Explanation:
The
AOPIPR
interface
is
not
able
to
process
the
event
for
the
specified
function
request.
Message
Variables:
function
-
The
function
that
failed,
which
is
one
of
the
following:
v
CONNECT
v
DISCONNECT
v
SEND
v
RECEIVE
v
GETIPADDRESS
System
Action:
Processing
continues
but
results
are
unpredictable.
Administrator
Response:
Contact
IBM
Software
Support.
GTM8018E
function
-
INVALID
TIMEOUT
VALUE
Explanation:
The
specified
TIMEOUT
value
is
incorrect.
Message
Variables:
function
-
The
function
that
failed,
which
is
one
of
the
following:
v
CONNECT
v
DISCONNECT
v
SEND
v
RECEIVE
v
GETIPADDRESS
System
Action:
The
connection
fails.
Administrator
Response:
Verify
the
TIMEOUT
value.
The
number
is
represented
in
seconds
in
the
range
30—86400.
GTM8019E
RECEIVE
-
NO
RESPONSE
MESSAGE
RECEIVED
Explanation:
The
receiving
application
is
designed
to
return
a
specific
message
back
to
the
sender
application
upon
sending
the
last
data
element.
This
message
holds
the
return
code
that
is
processed
by
the
receiving
application.
The
response
message
is
not
received.
System
Action:
Processing
continues
but
results
are
unpredictable.
Administrator
Response:
Verify
that
a
command
request
is
sent
to
the
receiving
application
as
the
last
data
element.
Refer
to
the
AOPIPR
Macro
specifications.
GTM8020E
INVALID
PARAMETERS
SUPPLIED
parameters
Explanation:
Parameters
that
are
not
valid
were
supplied
to
the
GTMDCOLV
utility.
Message
Variables:
parameters
-
The
parameters
that
are
in
error
System
Action:
The
GTMDCOLV
utility
ends.
Administrator
Response:
Refer
to
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide
for
more
information.
GTM8021E
ERROR
OBTAINING
SMS
INFORMATION
FOR
VOLUME
volser
RC=return_code
Explanation:
The
GTMDCOLV
utility
could
not
collect
system
managed
storage
(SMS)
information
for
the
volume
volser.
Message
Variables:
volser
-
The
VOLSER
of
the
volume
for
which
the
error
occurred
return_code
-
The
return
code
from
the
SMS
facility
System
Action:
The
GTMDCOLV
utility
ends.
Administrator
Response:
Keep
any
job
logs
and
contact
IBM
Software
Support.
GTM8030I
PROCESSING
COMPLETED
SUCCESSFULLY
Explanation:
The
TCP/IP
application
transmitted
all
the
data
to
the
receiving
application.
The
receiving
application
processed
all
the
data
successfully.
System
Action:
Processing
ends.
GTM8031I
PROCESSING
TERMINATED
UNSUCCESSFULLY
Explanation:
The
TCP/IP
application
did
not
complete.
System
Action:
Processing
ends.
Chapter
1.
Source/390
Messages
-
GTM0001I
-
GTM8665E
71
Administrator
Response:
Refer
to
the
previous
error
messages
written
to
the
SYSPRINT
log.
GTM8032E
OPEN
FILE
FAILURE
FOR
DDNAME
ddname
Explanation:
The
file
to
be
used
for
the
DD
name
requested
could
not
be
opened.
Message
Variables:
ddname
-
The
DD
name
System
Action:
The
GTMAOPE0
utility
ends.
Administrator
Response:
Verify
that
the
data
set
or
output
specification
is
valid
in
the
JCL.
Refer
to
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide
for
more
information.
GTM8033E
KEYWORD
IS
TOO
LONG
IN
PREVIOUS
CONTROL
CARD
Explanation:
The
specified
keyword
is
not
coded
correctly.
System
Action:
The
GTMAOPE0
utility
ends.
Administrator
Response:
Verify
the
syntax
for
the
specified
keyword
in
the
previous
control
card.
Refer
to
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide
for
more
information.
GTM8034E
KEYWORD
IS
MISSING
IN
PREVIOUS
CONTROL
CARD
Explanation:
The
specified
keyword
is
missing
the
equal
(=)
sign
to
separate
the
operand.
System
Action:
The
GTMAOPE0
utility
ends.
Administrator
Response:
Verify
the
syntax
for
the
specified
keyword
in
the
previous
control
card.
Refer
to
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide
for
more
information.
GTM8035E
KEYWORD
IS
NOT
SUPPORTED
IN
PREVIOUS
CONTROL
CARD
Explanation:
A
keyword
that
is
not
valid
was
detected
on
a
control
statement
to
the
GTMAOPE0
utility.
System
Action:
The
keyword
is
not
used.
Administrator
Response:
Verify
the
valid
keywords
that
are
supported.
Refer
to
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide
for
more
information.
GTM8036E
KEYWORD
OPERAND
IS
MISSING
IN
PREVIOUS
CONTROL
CARD
Explanation:
The
data
operand
for
the
requested
keyword
is
not
specified.
System
Action:
The
keyword
is
not
used.
Administrator
Response:
Verify
that
a
proper
value
is
specified
for
the
requested
keyword.
Refer
to
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide
for
more
information.
GTM8037E
TCPIP_ADDRESS
OR
TCPIP_NAME
CONTROL
CARD
IS
REQUIRED
Explanation:
The
TCPIP_ADDRESS
or
TCPIP_NAME
control
card
is
not
specified.
System
Action:
The
GTMAOPE0
utility
ends.
Administrator
Response:
Add
one
of
the
control
cards
indicated
to
establish
a
connection.
Refer
to
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide
for
more
information.
GTM8038E
TCPIP_PORT
CONTROL
CARD
IS
REQUIRED
Explanation:
The
TCPIP_PORT
control
card
is
not
specified.
System
Action:
The
GTMAOPE0
utility
ends.
Administrator
Response:
Add
the
indicated
control
card
to
establish
the
connection.
Refer
to
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide
for
more
information.
GTM8039E
COMMAND
CONTROL
CARD
IS
REQUIRED
Explanation:
The
COMMAND
control
card
is
not
specified.
System
Action:
The
GTMAOPE0
utility
ends.
Administrator
Response:
Add
the
COMMAND
control
card
specifying
the
command
alias
name
to
be
run
by
the
ASIMVSIPListenerSvc
service
for
Tivoli
Business
Systems
Manager.
Refer
to
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide
for
more
information.
GTM8040I
source_data
TRANSMISSION
STARTED
Explanation:
The
data
is
now
being
sent
to
the
receiving
application.
Message
Variables:
source_data
-
The
name
of
the
source
data
System
Action:
Processing
continues.
GTM8041I
ddname
RECORDS
SENT
Explanation:
The
ddname
records
were
successfully
sent.
Message
Variables:
ddname
-
The
DD
name
System
Action:
Processing
continues.
72
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
GTM8042I
DUPLICATE
keyword
CONTROL
CARD
PREVIOUS
CARD
IS
IGNORED
Explanation:
The
specified
control
card
is
entered
more
than
once.
Message
Variables:
keyword
-
The
keyword
name
System
Action:
Processing
continues.
Administrator
Response:
The
first
control
card
is
read,
processed,
and
used.
Remove
the
duplicate
cards.
GTM8043I
TCPIP
ADDRESS
IS
ALREADY
USED
PREVIOUS
CARD
IS
IGNORED
Explanation:
Both
the
TCPIP_ADDRESS
and
TCPIP_NAME
control
cards
are
specified.
System
Action:
Processing
continues.
Administrator
Response:
Remove
the
control
card
that
is
not
required
and
not
used.
GTM8044I
BUFFER
SIZE
IS
OUT
OF
RANGE
SETTING
DEFAULT
BUFFERSIZE
TO
1
Explanation:
The
BUFFERSIZE
value
specified
is
outside
of
the
supported
range.
System
Action:
Processing
continues.
Administrator
Response:
Change
the
BUFFERSIZE
to
a
supported
value
in
the
range
1–33.
Refer
to
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide
for
more
information.
GTM8045I
BUFFER
SIZE
IS
NOT
NUMERIC
SETTING
DEFAULT
BUFFERSIZE
TO
1
Explanation:
The
BUFFERSIZE
value
is
specified
incorrectly.
System
Action:
Processing
continues.
Administrator
Response:
Correct
the
BUFFERSIZE
value
to
a
valid
number
in
the
range
1–33.
Refer
to
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide
for
more
information.
GTM8046I
TIMEOUT
IS
OUT
OF
RANGE
SETTING
DEFAULT
TIMEOUT
VALUE
TO
30
Explanation:
The
TIMEOUT
value
specified
is
outside
of
the
supported
range.
System
Action:
Processing
continues.
Administrator
Response:
Change
the
TIMEOUT
value
to
a
supported
value
in
the
range
1–86400.
Refer
to
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide
for
more
information.
GTM8047I
TIMEOUT
IS
NOT
NUMERIC
SETTING
DEFAULT
TIMEOUT
TO
30
Explanation:
The
TIMEOUT
value
is
specified
incorrectly.
System
Action:
Processing
continues.
Administrator
Response:
Change
the
TIMEOUT
value
to
a
valid
number
in
the
range
1–86400.
Refer
to
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide
for
more
information.
GTM8049E
CODEPAGE
NUMBER
IS
INVALID
Explanation:
The
CODEPAGE
operand
is
not
a
valid
number.
System
Action:
The
GTMOPE0
utility
ends.
Administrator
Response:
Change
the
CODEPAGE
operand
to
the
numerical
value
that
is
to
be
used.
Refer
to
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide
for
more
information.
GTM8050E
CODEPAGE
CONTROL
CARD
IS
REQUIRED
Explanation:
The
CODEPAGE
control
card
is
not
specified.
System
Action:
The
GTMOPE0
utility
ends.
Administrator
Response:
Add
the
CODEPAGE
control
card
to
request
the
proper
translation
table
to
be
used.
Refer
to
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide
for
more
information.
GTM8051E
message_text
Explanation:
A
failure
occurred
during
processing
of
the
transmitted
data
System
Action:
The
GTMOPE0
utility
ends.
Administrator
Response:
Refer
to
the
Tivoli
Business
Systems
Manager
log
file
for
the
ASIMVSIPListenerSvc
service.
Depending
on
the
message
text
specified,
different
actions
are
required
to
be
performed.
v
COMMAND
ALIAS
command_name
NOT
FOUND
Explanation
Command
alias
name
transmitted
to
the
ASIMVSIPListenerSvc
service
cannot
be
found
in
the
command
registry
key.
Administrator
Response
Verify
that
the
command
alias
name
is
entered
into
the
command
registry
key.
v
REMOTE
CODEPAGE
IS
INVALID
Chapter
1.
Source/390
Messages
-
GTM0001I
-
GTM8665E
73
Explanation
The
code
page
transmitted
to
the
ASIMVSIPListenerSvc
service
is
not
a
supported
code
page.
Administrator
Response
Correct
the
code
page
and
retransmit
the
data.
v
CLIENT
HOST
VALIDATION
FAILED
ON
HOSThost_name
port
Explanation
The
MVS
client
for
the
host
name
or
IP
address
is
not
configured
in
the
ValidClient
registry
key
for
the
ASIMVSIPListenerSvc
service.
Administrator
Response
Add
the
client
host
name
or
IP
address
to
the
ValidClient
registry
key
and
restart
the
service.
Run
the
discovery
job
again.
GTM8052E
FORMAT_TYPE
VALUE
IS
INVALID
Explanation:
The
value
specified
for
the
FORMAT_TYPE
option
is
not
valid.
System
Action:
The
GTMOPE0
utility
ends.
Administrator
Response:
Refer
to
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide
and
correct
the
data
operand
value.
GTM8053E
data_separator
BYTE
VALUE
IS
INVALID
Explanation:
The
data
separator
override
byte
specified
is
either
too
long
or
the
value
exceeds
255
(X'ff')
Message
Variables:
data_separator
-
The
name
of
the
data
separator
System
Action:
The
GTMOPE0
utility
ends.
Administrator
Response:
Correct
the
data
operand
(byte)
to
indicate
the
data
separator
to
be
used
for
the
transmission
process.
Refer
to
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide
for
more
information.
GTM8054E
INVALID
TCPIP
JOBNAME
SPECIFIED
Explanation:
The
TCP/IP
job
name
that
is
coded
is
incorrect
and
cannot
be
processed.
System
Action:
The
GTMOPE0
utility
ends.
Administrator
Response:
Verify
that
the
TCP/IP
job
name
is
correct.
Ensure
the
length
does
not
exceed
eight
characters.
GTM8055E
CONVERT
REQUESTED
WITH
TEXT
MODE
ON
Explanation:
The
CONVERT
option
can
only
be
used
while
sending
character
data.
The
text
mode
must
be
off.
System
Action:
The
GTMOPE0
utility
ends.
Administrator
Response:
Set
the
option
to
TEXT=NO,
or
you
can
delete
the
TEXT
keyword
control
card.
The
default
value
is
NO.
GTM8060E
NO
COMMAND
CONTROL
CARDS
PROCESSED
RODM
DATA
WILL
NOT
BE
COLLECTED
Explanation:
There
are
no
COMMAND
NAME
control
cards
specified.
There
must
be
at
least
one
command
keyword
card
specified
or
the
AOPRODMD
utility
will
not
run.
System
Action:
The
RODM
unload
utility
ends.
Administrator
Response:
Add
a
COMMAND
control
card
specifying
the
RODM
source
that
is
to
be
transmitted
to
Tivoli
Business
Systems
Manager.
Refer
to
the
GTMOPE1
utility
documentation.
GTM8070I
INVALID
TRACE
OPERAND
SPECIFIED
SETTING
DEFAULT
TO
TRACE
BUFFERS
Explanation:
The
TRACE
operand
can
only
be
specified
with
the
BUFFERS
or
RECORDS
option.
The
BUFFERS
option
is
used
as
the
default
value
if
an
option
is
not
correctly
specified.
System
Action:
Processing
continues.
Administrator
Response:
Change
the
TRACE
operand
to
one
that
is
supported.
GTM8071I
TRACE
RECORDS
OPTION
IN
EFFECT
Explanation:
The
records
read
in
are
written
to
the
TRACE
DD
file.
System
Action:
Processing
continues.
GTM8072I
TRACE
BUFFERS
OPTION
IN
EFFECT
Explanation:
The
buffers
populated
with
the
records
read
in
are
written
to
the
TRACE
DD
file.
System
Action:
Processing
continues.
GTM8200E
name
:
PRIMARY
TCPIP_ADDRESS
OR
TCPIP_NAME
IS
NOT
SPECIFIED
Explanation:
The
TCP/IP
parameter
identifying
the
IP
listener
host
system
that
is
to
receive
the
event
messages
is
not
specified.
74
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
Message
Variables:
name
-
The
name
of
the
IP
service
task
System
Action:
The
object
server
address
space
ends.
Administrator
Response:
Specify
the
TCP/IP
host
address
or
host
name
in
the
object
server
startup
parameters.
Restart
the
source/390
object
server.
GTM8201E
name
:
PRIMARY
PORT
NUMBER
IS
NOT
SPECIFIED
Explanation:
The
TCP/IP
port
number
identifying
the
IP
listener
host
system
that
is
to
receive
the
event
messages
is
not
specified.
Message
Variables:
name
-
The
name
of
the
IP
service
task
System
Action:
The
object
server
address
space
ends.
Administrator
Response:
Specify
the
TCP/IP
port
number
in
the
object
server
startup
parameters.
Restart
the
source/390
object
server.
GTM8202I
name
:
BACKUP
TCPIP
ADDRESS
AND
PORT
IS
NOT
SPECIFIED
Explanation:
The
primary
connection
failed
and
the
object
server
switched
to
use
the
backup
IP
host
system.
The
retry
parameters
were
specified
and
the
backup
IP
parameters
were
not
specified.
Message
Variables:
name
-
The
name
of
the
IP
service
task
System
Action:
The
object
server
address
space
ends.
Administrator
Response:
Specify
the
TCP/IP
backup
IP
host
and
port
number
to
be
used
in
the
event
the
primary
connection
fails.
Restart
the
source/390
object
server.
GTM8203E
name
MGR
:
INITIALIZATION
FAILED
Explanation:
The
IP
service
task
did
not
initialize.
Message
Variables:
name
-
The
name
of
the
IP
service
task
System
Action:
The
object
server
address
space
ends.
Administrator
Response:
Identify
preceding
messages
that
might
indicate
why
the
service
task
is
unable
to
initialize.
Correct
the
problem
and
restart
the
source/390
object
server.
GTM8204I
name
MGR
:
TERMINATED
Explanation:
The
source/390
object
server
ended
the
service
task
manager
during
shutdown
processing.
Message
Variables:
name
-
The
name
of
the
IP
service
task
System
Action:
The
object
server
address
space
ends.
GTM8205I
name
:
READY
TO
TRANSMIT
TO
name
Explanation:
The
source/390
object
server
is
waiting
for
events
to
send
to
Tivoli
Business
Systems
Manager.
Message
Variables:
name
-
The
name
of
the
IP
service
task
name
-
The
IP
address
or
host
name
of
the
IP
listener
system
to
which
the
source/390
object
server
connected
and
is
ready
to
send
Tivoli
Business
Systems
Manager
event
data
System
Action:
Processing
continues.
GTM8206I
name
:
SWITCHING
OVER
TO
name
Explanation:
The
source/390
object
server
switched
over
to
the
backup
IP
Listener
host
system,
either
automatically
as
a
result
of
a
connection
failure
or
because
the
SWITCH
command
was
issued.
Message
Variables:
name
-
The
name
of
the
IP
service
task
name
-
The
IP
address
or
host
name
of
the
IP
listener
system
that
the
object
server
switched
over
and
connected.
The
source/390
object
server
is
now
ready
to
send
event
data
to
this
system.
System
Action:
Processing
continues.
GTM8207I
name
:
CONNECTION
REESTABLISHED
Explanation:
The
source/390
object
server
reconnected
to
the
IP
Listener
host
system.
Message
Variables:
name
-
The
name
of
the
IP
service
task
System
Action:
Processing
continues.
GTM8208E
name
:
function
STIMERM
SERVICE
FAILED
RC=return_code
Explanation:
The
source/390
object
server
failed
while
issuing
a
STIMERM
service
call.
Message
Variables:
name
-
The
name
of
the
IP
service
task
function
-
The
name
of
the
function
running
the
STIMERM
service
return_code
-
The
return
code
indicating
the
failure
of
the
STIMERM
service
call
System
Action:
Processing
continues
and
results
can
be
unpredictable.
Administrator
Response:
Contact
IBM
Software
Support.
Chapter
1.
Source/390
Messages
-
GTM0001I
-
GTM8665E
75
GTM8209E
name
:
GETMAIN
FAILED
FOR
RECEIVE
RESPONSE
MESSAGE
BUFFER
Explanation:
The
source/390
object
server
failed
to
obtain
storage
when
receiving
a
response
message
from
Tivoli
Business
Systems
Manager.
Message
Variables:
name
-
The
name
of
the
IP
service
task
System
Action:
Processing
continues
and
results
can
be
unpredictable.
Administrator
Response:
Check
the
region
size.
The
region
size
might
have
to
be
increased.
GTM8250E
name
:
SERVER
TCPIP_ADDRESS
OR
TCPIP_NAME
IS
NOT
SPECIFIED
Explanation:
The
TCP/IP
parameter
identifying
the
IP
Server
address
is
not
specified.
The
source/390
object
server
is
not
able
to
receive
registration
data
from
Tivoli
Business
Systems
Manager.
Message
Variables:
name
-
The
name
of
the
IP
service
task
System
Action:
The
address
space
ends.
Administrator
Response:
Specify
the
IP
Server
address
or
name
for
the
system
on
which
the
source/390
object
server
is
running.
Restart
the
source/390
object
server.
GTM8251E
name
:
SERVER
PORT
NUMBER
IS
NOT
SPECIFIED
Explanation:
The
TCP/IP
parameter
identifying
the
IP
Server
port
number
is
not
specified.
The
source/390
object
server
is
not
able
to
receive
registration
data
from
Tivoli
Business
Systems
Manager.
Message
Variables:
name
-
The
name
of
the
IP
service
task
System
Action:
The
address
space
ends.
Administrator
Response:
Specify
the
IP
Server
port
number
for
the
system
on
which
the
source/390
object
server
is
running.
Restart
the
source/390
object
server.
GTM8252I
name
:
LISTENING
ON
PORT
name
Explanation:
The
TCP/IP
server
port
number
is
receiving
registration
data
from
Tivoli
Business
Systems
Manager.
Message
Variables:
name
-
The
name
of
the
IP
service
task
name
-
The
listening
port
number
System
Action:
Processing
continues.
GTM8270E
name
:
UNABLE
TO
OBTAIN
STORAGE
FOR
THE
RECEIVE
BUFFER
number
Explanation:
There
is
insufficient
storage
for
the
receive
buffer.
Message
Variables:
name
-
The
name
of
the
IP
service
task
number
-
A
number
indicating
which
GETMAIN
call
failed
System
Action:
The
Receive
function
ends
and
results
can
be
unpredictable.
Administrator
Response:
Check
the
region
size.
The
region
size
might
have
to
be
increased.
GTM8271I
CLIENT
CONNECTED
FROM
PORT:
host_name
address
port
Explanation:
The
source/390
object
server
IP
Listener
service
obtained
a
connection
from
Tivoli
Business
Systems
Manager.
Message
Variables:
host_name
-
The
Tivoli
Business
Systems
Manager
host
name
of
the
system
that
connected
to
the
source/390
object
server
address
-
The
Tivoli
Business
Systems
Manager
IP
address
of
the
system
that
connected
to
the
source/390
object
server
port
-
The
Tivoli
Business
Systems
Manager
port
number
of
the
system
that
connected
to
the
source/390
object
server
System
Action:
Processing
continues.
GTM8272E
CLIENT
IS
NOT
AUTHORIZED:
host_name
Explanation:
A
Tivoli
Business
Systems
Manager
host
system
attempted
to
connect
to
the
object
server
but
the
IP
address
or
host
name
of
the
client
is
not
authorized
to
register
events
for
monitoring.
Message
Variables:
host_name
-
The
Tivoli
Business
Systems
Manager
host
name
or
IP
address
of
the
client
system
System
Action:
The
address
space
ends.
Administrator
Response:
Add
a
VALIDCLIENT
parameter
to
the
startup
parameters
of
the
object
server
specifying
the
Tivoli
Business
Systems
Manager
Client
host
name
or
IP
Address.
Restart
the
source/390
object
server.
GTM8273I
CLIENT
SENDER
SERVICE
TERMINATED:
host_name
Explanation:
The
ASIMVSIPSenderSvc-name
service
running
on
the
Tivoli
Business
System
Manager
Event
Handler
system
stopped.
76
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
Message
Variables:
host_name
-
The
host
name
or
IP
address
of
the
system
where
the
ASIMVSIPSenderSvc-name
service
stopped
System
Action:
The
IP
connection
in
the
object
server
to
the
ASIMVSIPSenderSvc-name
service
is
disconnected.
The
object
server
continues
to
listen
for
future
connection
requests.
Administrator
Response:
Tivoli
Business
Systems
Manager
registration
requests
for
the
object
pump
cannot
be
performed.
Verify
the
state
of
the
ASIMVSIPSenderSvc-name
service
on
the
Event
Handler
system.
If
the
ASIMVSIPSenderSvc-name
service
is
stopped,
then
start
it
manually.
GTM8542E
GTMSEND:
GETMAIN
FAILED
FOR
WORKING
STORAGE
Explanation:
The
source/390
object
server
failed
to
obtain
storage
when
sending
a
message
to
Tivoli
Business
Systems
Manager.
System
Action:
Processing
continues
and
results
can
be
unpredictable.
Administrator
Response:
Check
the
region
size.
The
region
size
might
have
to
be
increased.
GTM8544I
GTMSEND:
SESSION
NOT
ESTABLISHED
Explanation:
The
source/390
object
server
failed
to
allocate
an
LU
6.2
session
to
communicate
with
Tivoli
Business
Systems
Manager.
System
Action:
Processing
continues.
A
subsequent
attempt
might
be
made
to
reallocate
the
session
if
a
retry
is
allowed.
Administrator
Response:
Validate
that
the
LU
as
specified
in
the
REMOTE_APPLID
parameter
is
available.
GTM8545E
GTMSEND:
STIMERM
SERVICE
FAILED
Explanation:
A
request
to
the
STIMERM
service
failed.
System
Action:
Processing
continues.
Administrator
Response:
Contact
IBM
Software
Support.
GTM8546I
GTMSEND:
WAITING
FOR
CONNECTION
Explanation:
The
source/390
object
server
SEND
communications
program
is
waiting
for
the
LU
6.2
connection
to
the
Windows
system
to
be
established.
System
Action:
Processing
continues.
Administrator
Response:
Determine
why
the
connection
to
the
Windows
system
is
not
available.
If
necessary,
contact
IBM
Software
Support.
GTM8547I
GTMSEND:
SESSION
ESTABLISHED
Explanation:
The
source/390
object
server
communications
SEND
program
established
an
LU
6.2
connection
with
the
partner
session.
System
Action:
Processing
continues.
GTM8550I
GTMSEND:
SHUTDOWN
DETECTED
Explanation:
The
source/390
object
server
communications
SEND
program
received
a
shutdown
request.
System
Action:
The
session
is
ended.
GTM8551E
GTMSEND:
EXCEEDED
NUMBER
OF
RETRY
ATTEMPTS
TO
ESTABLISH
LU62
SESSION
Explanation:
While
attempting
to
connect
to
the
partner
LU,
the
initial
attempt
failed
but
a
retry
was
allowed.
The
retry
also
failed.
System
Action:
Processing
continues
and
results
can
be
unpredictable.
Administrator
Response:
Determine
why
the
source/390
object
server
was
unable
to
connect
to
the
partner
LU.
If
necessary,
contact
IBM
Software
Support.
GTM8552E
GTMSEND:
RESOURCE
LIMITATION,
UNABLE
TO
ATTEMPT
TO
ESTABLISH
LU62
CONNECTION
Explanation:
The
source/390
object
server
was
unable
to
connect
to
the
partner
LU
because
the
VTAM
program
indicated
there
are
insufficient
resources
available
for
the
session.
System
Action:
Processing
continues
and
results
can
be
unpredictable.
Administrator
Response:
Check
that
the
VTAM
APPL
definitions
for
the
session
on
the
host
and
partner
LU
are
correctly
defined.
Refer
to
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide
.
If
necessary,
contact
IBM
Software
Support.
GTM8553E
GTMSEND
:
request
function
FAILED
Explanation:
Indicates
that
the
specified
function
within
the
ACC1SEND
program
failed.
Message
Variables:
request
-
The
name
of
the
requesting
program
function
-
The
name
of
the
function
The
following
are
the
possible
values
for
request
and
the
corresponding
user
action:
v
QCREATE
Chapter
1.
Source/390
Messages
-
GTM0001I
-
GTM8665E
77
Explanation
Queue
creation
failed
for
the
work
station
queue
within
the
data
space.
Administrator
Response
Review
the
source/390
object
server
job
log
to
see
if
there
are
any
additional
messages
related
to
the
failure.
Review
the
WSQUEUESIZE
parameter
of
the
source/390
object
server
and
the
DATASPACESIZE
parameter
of
the
data
space.
If
necessary,
restart
the
data
space
and
object
server.
v
QINIT
Explanation
Queue
initialization
failed
for
the
work
station
queue
within
the
data
space.
Administrator
Response
Review
the
source/390
object
server
job
log
to
see
if
there
are
any
additional
messages
related
to
the
failure.
Review
the
WSQUEUESIZE
parameter
of
the
source/390
object
server
and
the
DATASPACESIZE
parameter
of
the
data
space.
If
necessary,
restart
the
source/390
data
space
and
source/390
object
server.
v
NOTIFY
Explanation
An
error
occurred
when
the
send
communications
program
within
the
source/390
object
server
requested
that
it
be
notified
when
a
session
was
established
with
the
partner
LU
over
the
LU
6.2
communications
session.
Administrator
Response
Review
the
source/390
object
server
and
system
console
logs
to
see
if
there
are
any
additional
messages
related
to
the
failure.
Review
the
logs
on
the
SNA
Server
system
for
any
error
messages.
If
necessary,
restart
the
SNA
server
and
the
source/390
object
server.
v
WAIT
Explanation
An
error
occurred
when
the
send
communications
program
issued
a
wait
to
the
source/390
object
server
communications
manager
while
waiting
for
a
NOTIFY
to
complete
(wait
for
session
to
be
established).
Administrator
Response
Review
the
source/390
object
server
and
system
console
logs
to
see
if
there
are
any
additional
messages
related
to
the
failure.
If
necessary,
restart
the
source/390
object
server.
v
DATAWAIT
Explanation
An
error
occurred
when
requesting
a
wait
for
data
to
be
placed
on
the
workstation
queue.
Administrator
Response
Review
the
source/390
object
server
log
to
see
if
there
are
any
additional
messages
related
to
the
failure.
If
necessary,
restart
the
source/390
object
server.
v
SEND
Explanation
An
error
occurred
while
sending
data
to
the
partner
LU
over
the
LU
6.2
session.
Administrator
Response
Review
the
source/390
object
server
and
system
console
logs
to
see
if
there
are
any
additional
messages
related
to
the
failure.
If
necessary,
restart
the
source/390
object
server
and
the
SNA
server.
v
WAITSEND
Explanation
An
error
occurred
when
the
send
communications
program
issued
a
wait
to
the
source/390
object
server
communications
manager
while
waiting
for
a
NOTIFY
to
complete
(wait
for
the
session
to
be
established).
Administrator
Response
Review
the
source/390
object
server
and
system
console
logs
to
see
if
there
are
any
additional
messages
related
to
the
failure.
If
necessary,
restart
the
source/390
object
server.
v
WAITALLO
Explanation
An
error
occurred
when
the
send
communications
program
attempted
to
start
a
session
with
the
partner
LU.
Administrator
Response
Review
the
source/390
object
server
and
system
console
logs
to
see
if
there
are
any
additional
messages
related
to
the
failure.
Review
the
SNA
server
system
logs
to
see
if
any
errors
were
reported
there.
Check
that
the
ACC1RCV
process
is
correctly
defined
to
the
SNA
server
and
that
the
associated
processes
are
running.
System
Action:
Processing
continues
and
results
can
be
unpredictable.
GTM8554E
GTMSEND:
SESSION
DISCONNECTED
Explanation:
The
session
with
the
partner
LU
was
lost.
78
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
System
Action:
Processing
continues.
Administrator
Response:
Determine
why
the
session
was
lost
and
correct
the
problem.
If
necessary,
contact
IBM
Software
Support.
GTM8559I
GTMSEND:
TERMINATED
Explanation:
The
source/390
object
server
communications
SEND
program
ended.
System
Action:
The
session
ends.
GTM8660E
ACC1RECV:
GETMAIN
FAILED
FOR
type
Explanation:
A
GETMAIN
macro
failed
for
the
specified
storage
within
the
RECEIVE
communications
program.
Message
Variables:
type
-
The
type
of
storage
requested
System
Action:
The
receive
function
ends
and
results
can
be
unpredictable.
Administrator
Response:
Determine
why
the
GETMAIN
macro
failed.
If
necessary,
contact
IBM
Software
Support.
GTM8662I
SHUTDOWN
DETECTED
Explanation:
The
source/390
object
server
communications
RECEIVE
program
received
a
shutdown
request.
System
Action:
The
address
space
shuts
down.
GTM8663E
name:
SESSION
DISCONNECTED
Explanation:
The
session
with
the
partner
LU
was
lost.
Message
Variables:
name
-
The
name
of
the
issuing
program.
The
source/390
object
server
waits
for
the
session
to
become
available
again
and
attempts
to
reconnect
to
the
partner
LU.
System
Action:
The
system
attempts
to
reestablish
the
session.
Administrator
Response:
Determine
why
the
session
was
lost
and
correct
the
problem.
If
necessary,
contact
IBM
Software
Support.
GTM8664E
name
:
type
FAILED
Explanation:
The
request
service
failed.
Message
Variables:
name-
The
name
of
the
issuing
program
type
-
The
type
of
request
that
was
being
processed
System
Action:
Processing
continues
and
results
can
be
unpredictable.
Administrator
Response:
Contact
IBM
Software
Support.
GTM8665E
CROSS
MEMORY
POST
FAILED
WITH
RC=return_code
Explanation:
This
post
failure
indicates
that
the
event
messages
are
unable
to
be
received
by
the
source/390
object
server.
Message
Variables:
return_code
-
Indicates
the
return
code
of
the
post
failure
System
Action:
Processing
continues
and
results
can
be
unpredictable.
Administrator
Response:
Contact
IBM
Software
Support.
Chapter
1.
Source/390
Messages
-
GTM0001I
-
GTM8665E
79
Chapter
2.
Agent
Listener
Messages
GTMAL0001I
-
GTMAL0031E
The
following
messages
are
issued
from
the
Agent
Listener
service.
GTMAL0001I
Starting
Tivoli
Business
Systems
Manager
Agent
Listener
3.1
build
on
date.
Explanation:
The
Agent
Listener
3.1
service
started.
Message
Variables:
date
-
The
date
from
the
ASIAgentListener.jar
file
GTMAL0002I
The
Agent
Listener
shutdown
process
has
been
initiated.
Explanation:
The
Agent
Listener
shutdown
process
is
in
progress.
System
Action:
All
socket
connections
to
event
enablement
are
closed,
all
database
connections
are
closed,
and
the
service
is
stopped.
GTMAL0003I
Exception
caught
during
Agent
Listener
shutdown.
Exception:
exception.
Explanation:
An
error
occurred
during
the
Agent
Listener
shutdown
process.
Message
Variables:
exception
-
The
text
that
describes
the
error
System
Action:
The
Agent
Listener
service
stops.
Administrator
Response:
Consult
the
log
files
for
additional
information.
The
logs
files
are
located
in
the
directory
specified
by
the
TivliCommonDir
parameter
in
the
ASIAgentListener.properties
file.
If
the
problem
cannot
be
resolved,
contact
IBM
Software
Support.
GTMAL0004I
The
Agent
Listener
shutdown
process
has
completed.
Explanation:
The
Agent
Listener
shutdown
process
has
successfully
completed.
System
Action:
All
socket
connections
to
event
enablement
closed,
all
database
connections
closed,
and
the
service
stopped.
GTMAL0005I
The
following
key
and
value
retrieved
from
the
ASIAgentListener.properties
file
is
not
valid.
Key:
keyword
Value:
value
Explanation:
The
value
specified
for
the
keyword
is
not
valid.
The
default
value
is
used.
Message
Variables:
keyword
-
The
specified
keyword
in
the
ASIAgentListener.properties
file
value
-
The
value
that
was
not
valid
Administrator
Response:
If
you
do
not
want
to
use
the
default
value
for
the
keyword,
stop
the
Agent
Listener
service,
specify
a
valid
value
for
the
key
in
the
ASIAgentListener.properties
file,
and
restart
the
Agent
Listener
service.
GTMAL0006E
Exception
caught
while
running
the
stored
procedure
al_processMsgs.
Exception:
exception.
Explanation:
An
error
occurred
when
the
data
in
the
Agent
Listener
staging
tables
was
processing.
Message
Variables:
exception
-
The
text
that
describes
the
error
Administrator
Response:
Consult
the
log
files
for
additional
information.
The
logs
files
are
located
in
the
directory
specified
by
the
TivliCommonDir
parameter
in
the
ASIAgentListener.properties
file.
If
the
problem
cannot
be
resolved,
contact
IBM
Software
Support.
GTMAL0007E
There
are
no
Event
Enablement
entries
in
GemEEConfig.properties
file.
Explanation:
The
Agent
Listener
has
not
been
configured
to
connect
to
any
event
enablement
hosts.
System
Action:
The
Agent
Listener
service
stops.
Administrator
Response:
Use
the
GemEEConfig
tool
to
configure
one
or
more
event
enablement
hosts
and
restart
the
Agent
Listener
service.
GTMAL0008E
Exception
caught
while
initializing
AlJdbcHandlerDb.
Exception:
exception.
Explanation:
An
error
occurred
when
the
AlJdbcHandlerDb
thread
was
initialized.
Message
Variables:
exception
-
The
text
that
describes
the
error
System
Action:
The
Agent
Listener
service
stops.
Administrator
Response:
Consult
the
log
files
for
additional
information.
The
logs
files
are
located
in
the
directory
specified
by
the
TivliCommonDir
parameter
©
Copyright
IBM
Corp.
2000,
2004
81
in
the
ASIAgentListener.properties
file.
Restart
the
Agent
Listener
service.
If
the
problem
cannot
be
resolved,
contact
IBM
Software
Support.
GTMAL0009E
Exception
caught
while
initializing
AlJdbcHandler.
Exception:
exception.
Explanation:
An
error
occurred
when
the
AlJdbcHandler
thread
was
initializing.
Message
Variables:
exception
-
The
text
that
describes
the
error
System
Action:
The
Agent
Listener
service
stops.
Administrator
Response:
Consult
the
log
files
for
additional
information.
The
logs
files
are
located
in
the
directory
specified
by
the
TivliCommonDir
parameter
in
the
ASIAgentListener.properties
file.
Restart
the
Agent
Listener
service.
If
the
problem
cannot
be
resolved,
contact
IBM
Software
Support.
GTMAL0010E
Exception
caught
while
initializing
AlEventEnablementListener.
Exception:
exception.
Explanation:
An
error
occurred
when
an
AlEventEnablementListener
thread
that
connects
to
an
event
enablement
host
was
initializing.
Message
Variables:
exception
-
The
text
that
describes
the
error
System
Action:
The
Agent
Listener
service
stops.
Administrator
Response:
Consult
the
log
files
for
additional
information.
The
logs
files
are
located
in
the
directory
specified
by
the
TivliCommonDir
parameter
in
the
ASIAgentListener.properties
file.
Restart
the
Agent
Listener
service.
If
the
problem
cannot
be
resolved,
contact
IBM
Software
Support.
GTMAL0011E
Exception
caught
while
loading
the
GemEEConfig.properties
file.
Exception:
exception.
Explanation:
The
GemEEConfig.properties
file
was
loaded
and
an
error
occurred
during
an
attempt
to
read
the
list
of
configured
event
enablement
host
names.
Message
Variables:
exception
-
The
text
that
describes
the
error
System
Action:
The
Agent
Listener
service
stops.
Administrator
Response:
Use
the
GemEEConfig
tool
to
verify
that
the
configuration
data
for
the
specified
host
name
exists.
GTMAL0012I
Exception
caught
while
connecting
to
database.
Retry
initiated.
Exception:
exception.
Explanation:
An
error
occurred
during
an
attempt
to
connect
to
the
database.
Message
Variables:
exception
-
The
text
that
describes
the
error
System
Action:
The
Agent
Listener
will
attempt
to
connect
to
the
database
again
for
the
configured
DatabaseServerWait
interval.
Administrator
Response:
Consult
the
log
files
for
additional
information.
The
logs
files
are
located
in
the
directory
specified
by
the
TivliCommonDir
parameter
in
the
ASIAgentListener.properties
file.
Verify
that
the
database
parameters
specified
in
the
ASIAgentListener.properties
file
are
correct.
The
properties
file
is
located
on
the
server
where
Tivoli
Enterprise
Console
is
installed.
Verify
that
the
Tivoli
Business
Systems
Manager
database
has
been
installed
and
configured
with
the
correct
values.
Restart
the
Agent
Listener
service.
If
the
problem
cannot
be
resolved,
contact
IBM
Software
Support.
GTMAL0013E
A
BCP
error
occurred.
Explanation:
An
unexpected
BCP
error
occurred.
System
Action:
The
Agent
Listener
service
stops.
Administrator
Response:
Verify
that
the
BCP
parameters
specified
in
the
ASIAgentListener.properties
file
are
correct.
If
the
BCP
parameters
are
modified,
stop
and
restart
the
Agent
Listener
service.
If
the
problem
cannot
be
resolved,
contact
IBM
Software
Support.
GTMAL0014E
Exception
loading
an
Event
Enablement
properties
file.
Exception:
exception.
Explanation:
An
error
occurred
when
the
event
enablement
configuration
data
was
read
from
a
properties
file.
Message
Variables:
exception
-
The
text
that
describes
the
error
Administrator
Response:
Use
the
GemEEConfig
tool
to
verify
that
the
configuration
data
for
the
specified
event
enablement
host
exists.
82
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
GTMAL0015E
Exception
storing
data
in
an
Event
Enablement
properties
file.
Exception:
exception.
Explanation:
An
error
occurred
when
the
event
enablement
configuration
data
was
written
to
a
properties
file.
Message
Variables:
exception
-
The
text
that
describes
the
error
System
Action:
The
Agent
Listener
service
stops.
Administrator
Response:
Use
the
GemEEConfig
tool
to
verify
that
the
configuration
data
for
the
specified
host
name
exists.
GTMAL0016E
Exception
caught
while
initializing
AlJdbcHandlerBatch.
Exception:
exception.
Explanation:
An
error
occurred
when
an
AlJdbcHandlerBatch
thread
was
initializing.
Message
Variables:
exception
-
The
text
that
describes
the
error
System
Action:
The
Agent
Listener
service
stops.
Administrator
Response:
Consult
the
log
files
for
additional
information.
The
logs
files
are
located
in
the
directory
specified
by
the
TivliCommonDir
parameter
in
the
ASIAgentListener.properties
file.
Restart
the
Agent
Listener
service.
If
the
problem
cannot
be
resolved,
contact
IBM
Software
Support.
GTMAL0017E
Exception
caught
while
connecting
to
database.
Exception:
exception.
Explanation:
An
error
occurred
connecting
to
the
database.
Message
Variables:
exception
-
The
text
that
describes
the
error
System
Action:
The
Agent
Listener
service
stops.
Administrator
Response:
Consult
the
log
files
for
additional
information.
The
logs
files
are
located
in
the
directory
specified
by
the
TivliCommonDir
parameter
in
the
ASIAgentListener.properties
file.
Verify
that
the
database
parameters
specified
in
the
ASIAgentListener.properties
file
are
correct.
Verify
that
the
Tivoli
Business
Systems
Manager
database
has
been
installed
and
configured
with
the
correct
values.
Restart
the
Agent
Listener
service.
If
the
problem
cannot
be
resolved,
contact
IBM
Software
Support.
GTMAL0018E
Exception
caught
while
trying
to
allocate
a
block
of
transaction
IDs.
Exception:
exception.
Explanation:
An
error
occurred
when
a
block
of
transaction
IDs
in
the
AL_Stage
table
was
allocated.
Message
Variables:
exception
-
The
text
that
describes
the
error
System
Action:
The
Agent
Listener
service
stops.
Administrator
Response:
Consult
the
log
files
for
additional
information.
The
logs
files
are
located
in
the
directory
specified
by
the
TivliCommonDir
parameter
in
the
ASIAgentListener.properties
file.
If
the
problem
cannot
be
resolved,
contact
IBM
Software
Support.
GTMAL0019E
Exception
caught
closing
a
database
connection.
Exception:
exception.
Explanation:
An
error
occurred
when
a
database
connection
was
closed.
Message
Variables:
exception
-
The
text
that
describes
the
error
System
Action:
The
Agent
Listener
service
stops.
Administrator
Response:
Consult
the
log
files
for
additional
information.
The
logs
files
are
located
in
the
directory
specified
by
the
TivliCommonDir
parameter
in
the
ASIAgentListener.properties
file.
If
the
problem
cannot
be
resolved,
contact
IBM
Software
Support.
GTMAL0020E
Exception
occurred
creating
a
temporary
table.
Exception:
exception.
Explanation:
An
error
occurred
when
a
temporary
database
table
was
created.
Message
Variables:
exception
-
The
text
that
describes
the
error
System
Action:
The
Agent
Listener
service
stops.
Administrator
Response:
Consult
the
log
files
for
additional
information.
The
logs
files
are
located
in
the
directory
specified
by
the
TivliCommonDir
parameter
in
the
ASIAgentListener.properties
file.
If
the
problem
cannot
be
resolved,
contact
IBM
Software
Support.
GTMAL0021E
Exception
caught
initializing
AlJdbcHandlerBatch.
Exception:
exception.
Explanation:
An
error
occurred
when
the
AlJdbcHandlerBatch
thread
was
initializing.
Message
Variables:
exception
-
The
text
that
describes
the
error
Chapter
2.
Agent
Listener
Messages
GTMAL0001I
-
GTMAL0031E
83
System
Action:
The
Agent
Listener
service
stops.
Administrator
Response:
Consult
the
log
files
for
additional
information.
The
logs
files
are
located
in
the
directory
specified
by
the
TivliCommonDir
parameter
in
the
ASIAgentListener.properties
file.
If
the
problem
cannot
be
resolved,
contact
IBM
Software
Support.
GTMAL0022E
Exception
caught
while
running
AlJdbcHandlerBatch.
Exception:
exception.
Explanation:
An
error
occurred
when
the
AlJdbcHandlerBatch
thread
was
processing.
Message
Variables:
exception
-
The
text
that
describes
the
error
System
Action:
The
Agent
Listener
service
stops.
Administrator
Response:
Consult
the
log
files
for
additional
information.
The
logs
files
are
located
in
the
directory
specified
by
the
TivliCommonDir
parameter
in
the
ASIAgentListener.properties
file.
If
the
problem
cannot
be
resolved,
contact
IBM
Software
Support.
GTMAL0023E
Timed
out
waiting
for
records
to
be
written
to
the
database.
Explanation:
The
Agent
Listener
service
timed
out
waiting
for
records
to
be
written
to
the
database.
System
Action:
The
Agent
Listener
service
stops.
Administrator
Response:
Consult
the
log
files
for
additional
information.
The
logs
files
are
located
in
the
directory
specified
by
the
TivliCommonDir
parameter
in
the
ASIAgentListener.properties
file.
If
the
problem
cannot
be
resolved,
contact
IBM
Software
Support.
GTMAL0024E
Exception
caught
while
initializing
prepared
statements.
Exception:
exception.
Explanation:
An
error
occurred
when
batch
statements
were
initializing.
Message
Variables:
exception
-
The
text
that
describes
the
error
System
Action:
The
Agent
Listener
service
stops.
Administrator
Response:
Consult
the
log
files
for
additional
information.
The
logs
files
are
located
in
the
directory
specified
by
the
TivliCommonDir
parameter
in
the
ASIAgentListener.properties
file.
If
the
problem
cannot
be
resolved,
contact
IBM
Software
Support.
GTMAL0025E
Exception
caught
while
clearing
batch
statements.
Exception:
exception.
Explanation:
An
error
occurred
when
all
commands
were
removed
from
a
batch
statement.
Message
Variables:
exception
-
The
text
that
describes
the
error
Administrator
Response:
Consult
the
log
files
for
additional
information.
The
logs
files
are
located
in
the
directory
specified
by
the
TivliCommonDir
parameter
in
the
ASIAgentListener.properties
file.
If
the
problem
cannot
be
resolved,
contact
IBM
Software
Support.
GTMAL0026E
Exception
caught
while
adding
commands
to
a
batch
statement.
Exception:
exception.
Explanation:
An
error
occurred
when
commands
were
added
to
a
batch
statement.
Message
Variables:
exception
-
The
text
that
describes
the
error
System
Action:
The
Agent
Listener
service
stops.
Administrator
Response:
Consult
the
log
files
for
additional
information.
The
logs
files
are
located
in
the
directory
specified
by
the
TivliCommonDir
parameter
in
the
ASIAgentListener.properties
file.
If
the
problem
cannot
be
resolved,
contact
IBM
Software
Support.
GTMAL0027E
The
specified
value
is
null.
Explanation:
The
Agent
Listener
service
was
attempting
to
insert
a
null
value
into
the
database.
System
Action:
The
Agent
Listener
service
stops.
Administrator
Response:
Consult
the
log
files
for
additional
information.
The
logs
files
are
located
in
the
directory
specified
by
the
TivliCommonDir
parameter
in
the
ASIAgentListener.properties
file.
If
the
problem
cannot
be
resolved,
contact
IBM
Software
Support.
GTMAL0028E
Exception
caught
while
closing
an
SQL
statement.
Exception:
exception.
Explanation:
An
error
occurred
when
an
SQL
statement
was
closing.
Message
Variables:
exception
-
The
text
that
describes
the
error
System
Action:
The
Agent
Listener
service
stops.
Administrator
Response:
Consult
the
log
files
for
additional
information.
The
logs
files
are
located
in
the
directory
specified
by
the
TivliCommonDir
parameter
in
the
ASIAgentListener.properties
file.
84
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
If
the
problem
cannot
be
resolved,
contact
IBM
Software
Support.
GTMAL0029E
Exception
caught
while
attempting
to
update
the
AL_Stage
table.
Exception:
exception.
Explanation:
An
error
occurred
when
the
trstate
attribute
in
the
AL_Stage
table
was
updated.
Message
Variables:
exception
-
The
text
that
describes
the
error
System
Action:
The
Agent
Listener
service
stops.
Administrator
Response:
Consult
the
log
files
for
additional
information.
The
logs
files
are
located
in
the
directory
specified
by
the
TivliCommonDir
parameter
in
the
ASIAgentListener.properties
file.
If
the
problem
cannot
be
resolved,
contact
IBM
Software
Support.
GTMAL0030E
Exception
caught
while
executing
batch
commands.
Exception:
exception.
Explanation:
An
error
occurred
when
a
batch
command
to
insert
or
update
the
Agent
Listener
staging
tables
was
executed.
Message
Variables:
exception
-
The
text
that
describes
the
error
System
Action:
The
Agent
Listener
service
stops.
Administrator
Response:
Consult
the
log
files
for
additional
information.
The
logs
files
are
located
in
the
directory
specified
by
the
TivliCommonDir
parameter
in
the
ASIAgentListener.properties
file.
If
the
problem
cannot
be
resolved,
contact
IBM
Software
Support.
GTMAL0031E
Exception
caught
during
BCP
processing.
Exception:
exception.
Explanation:
An
error
occurred
while
processing
a
BCP
file.
Message
Variables:
exception
-
The
text
that
describes
the
error
System
Action:
The
Agent
Listener
service
stops.
Administrator
Response:
Consult
the
log
files
for
additional
information.
The
logs
files
are
located
in
the
directory
specified
by
the
TivliCommonDir
parameter
in
the
ASIAgentListener.properties
file.
If
the
problem
cannot
be
resolved,
contact
IBM
Software
Support.
Chapter
2.
Agent
Listener
Messages
GTMAL0001I
-
GTMAL0031E
85
Chapter
3.
Automated
Business
System
Messages
-
GTMAB1001E
-
GTMAB1048E
The
following
messages
are
issued
from
the
Automated
Business
System.
GTMAB1001E
Unable
to
load
configuration.
Explanation:
The
processing
of
the
configuration
is
not
complete
due
to
a
processing
error.
System
Action:
The
system
will
not
use
this
configuration
and
is
still
using
the
last
valid
configuration.
Administrator
Response:
See
additional
error
messages
for
the
corrective
action.
These
messages
can
be
found
in
the
logs
directory
and
have
the
format
of
absconfig.timestamp.log.
GTMAB1002E
Unable
to
load
configuration
file
file_name.
Explanation:
The
processing
of
the
configuration
file
is
not
complete
due
a
processing
error
in
the
specified
file.
Message
Variables:
file_name
-
The
name
of
the
configuration
file
System
Action:
The
system
will
not
use
this
configuration
and
is
still
using
the
last
valid
configuration.
Administrator
Response:
See
additional
error
messages
for
the
corrective
action.
These
messages
can
be
found
in
the
logs
directory
and
have
the
format
of
absconfig.timestamp.log.
GTMAB1003E
The
class
cid
in
pattern
pattern_id
in
the
Pattern
section
is
not
allowed.
Explanation:
The
specified
pattern
contains
an
unusable
or
nonexistent
class.
Message
Variables:
cid
-
The
class
ID
name
pattern_id
-
The
pattern
ID
number,
which
is
an
integer
System
Action:
The
system
will
not
use
this
configuration
and
is
still
using
the
last
valid
configuration.
Administrator
Response:
Replace
the
class
in
the
specified
pattern
with
a
valid
class.
Run
the
absallowedclassattribute.ksh
script
to
get
a
list
of
valid
classes.
GTMAB1004E
The
attribute
attribute
in
pattern
pattern_id
in
the
Pattern
section
is
not
allowed.
Explanation:
The
specified
pattern
contains
an
unusable
or
nonexistent
attribute.
Message
Variables:
attribute
-
The
attribute
field
name
pattern_id
-
The
pattern
ID
number,
which
is
an
integer
System
Action:
The
system
will
not
use
this
configuration
and
is
still
using
the
last
valid
configuration.
Administrator
Response:
Replace
the
attribute
in
the
specified
pattern
with
a
valid
attribute.
Run
the
absallowedclassattribute.ksh
script
to
get
a
list
of
valid
attributes
for
the
class.
GTMAB1005E
The
When
field
value
of
when
in
pattern
pattern_id
in
the
Pattern
section
is
not
allowed.
Explanation:
The
specified
pattern
in
the
Pattern
section
contains
a
When
field
value
that
is
not
allowed.
Message
Variables:
when
-
The
value
of
the
When
field
pattern_id
-
The
pattern
ID
number,
which
is
an
integer
System
Action:
The
system
will
not
use
this
configuration
and
is
still
using
the
last
valid
configuration.
Administrator
Response:
Replace
the
When
field
value
in
the
specified
pattern
with
a
valid
value.
The
valid
values
are
Previous
or
Current.
GTMAB1006E
The
pattern
pattern_id
in
the
CriteriaToPattern
section
does
not
exist.
Explanation:
The
Pattern
field
in
the
CriteriaToPattern
section
can
only
reference
a
pattern
that
exists
in
the
Pattern
section.
Message
Variables:
pattern_id
-
The
pattern
ID
number,
which
is
an
integer
System
Action:
The
system
will
not
use
this
configuration
and
is
still
using
the
last
valid
configuration.
Administrator
Response:
Replace
the
pattern
in
the
CriteriaToPattern
section
with
an
existing
pattern
ID
from
the
Pattern
section,
or
add
this
pattern
to
the
©
Copyright
IBM
Corp.
2000,
2004
87
Pattern
section
of
the
configuration
file.
GTMAB1007E
The
PatternRelated
pattern_id
in
the
CriteriaToPattern
section
does
not
exist.
Explanation:
The
PatternRelated
field
in
the
CriteriaToPattern
section
can
only
reference
a
pattern
that
exists
in
the
Pattern
section.
Message
Variables:
pattern_id
-
The
pattern
ID
number,
which
is
an
integer
System
Action:
The
system
will
not
use
this
configuration
and
is
still
using
the
last
valid
configuration.
Administrator
Response:
Replace
the
PatternRelated
in
the
CriteriaToPattern
section
with
an
existing
pattern
ID
from
the
Pattern
section,
or
add
this
pattern
to
the
Pattern
section
of
the
configuration
file.
GTMAB1008E
The
PatternRelated
pattern_id
for
criteria
criteria_id
in
the
CriteriaToPattern
section
is
not
allowed
because
it
does
not
appear
in
the
Pattern
column
for
the
same
criteria.
Explanation:
The
PatternRelated
field
can
only
be
populated
with
the
ID
of
a
pattern
that
is
referenced
in
the
Pattern
field
for
the
same
Criteria.
Message
Variables:
pattern_id
-
The
pattern
ID
number,
which
is
an
integer
criteria_id
-
The
criteria
ID
number,
which
is
an
integer
System
Action:
The
system
will
not
use
this
configuration
and
is
still
using
the
last
valid
configuration.
Administrator
Response:
Replace
PatternRelated
with
a
pattern
from
the
Pattern
column
in
the
CriteriaToPattern
section
for
this
Criteria,
or
add
a
record
to
the
CriteriaToPattern
section
that
uses
PatternRelated
in
the
Pattern
column.
GTMAB1009E
Level
level_id
is
missing
from
Path
path_id
in
the
Path
section
of
the
configuration
file.
Explanation:
In
the
Path
section,
the
number
of
the
Level
must
start
at
one
and
be
a
contiguous
series
of
integers
for
each
path.
Message
Variables:
level_id
-
The
level
ID
number,
which
is
an
integer
starting
with
one
(for
example,
1,
2,
3,
4)
path_id
-
The
path
ID
name
string
System
Action:
The
system
will
not
use
this
configuration
and
is
still
using
the
last
valid
configuration.
Administrator
Response:
Add
a
record
containing
the
missing
Level,
or
change
the
Level
numbers
for
the
Path
specified
to
start
at
one
and
be
a
contiguous
series
of
integers.
GTMAB1010E
Path
path_id
in
the
CriteriaToPath
section
does
not
exist
in
the
Path
section
of
the
configuration
file.
Explanation:
The
CriteriaToPath
section
can
only
reference
a
Path
ID
that
exists
in
the
Path
section
of
the
configuration
file.
Message
Variables:
path_id
-
The
path
ID
name
string
System
Action:
The
system
will
not
use
this
configuration
and
is
still
using
the
last
valid
configuration.
Administrator
Response:
Add
a
record
containing
the
missing
Path
to
the
Path
section,
or
change
the
Path
to
be
an
existing
path.
GTMAB1011E
Criteria
criteria_id
in
the
CriteriaToPath
section
does
not
exist
in
the
CriteriaToPattern
section
of
the
configuration
file.
Explanation:
The
CriteriaToPath
section
can
only
reference
a
criteria
ID
that
exists
in
the
CriteriaToPattern
section
of
the
configuration
file.
Message
Variables:
criteria_id
-
The
criteria
ID
number,
which
is
an
integer
System
Action:
The
system
will
not
use
this
configuration
and
is
still
using
the
last
valid
configuration.
Administrator
Response:
Add
a
record
containing
the
missing
Criteria,
or
change
the
Criteria
to
be
an
existing
Criteria,
in
the
CriteriaToPattern
section.
GTMAB1012E
Pattern
pattern_id
in
the
CriteriaToPattern
section
does
not
exist
in
the
Pattern
section
of
the
configuration
file.
Explanation:
The
CriteriaToPath
section
can
only
reference
a
Pattern
ID
that
exists
in
the
Pattern
section.
Message
Variables:
pattern_id
-
The
pattern
ID
number,
which
is
an
integer
System
Action:
The
system
will
not
use
this
configuration
and
is
still
using
the
last
valid
configuration.
Administrator
Response:
Add
a
record
containing
the
missing
Pattern,
or
change
the
Pattern
to
be
an
existing
pattern,
in
the
Pattern
section.
88
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
GTMAB1013E
The
Criteria
criteria_id
and
Pattern
pattern_id
combination
in
the
CriteriaToPath
section
does
not
exist
in
the
CriteriaToPattern
section
of
the
configuration
file.
Explanation:
The
CriteriaToPath
section
can
only
use
criteria
and
pattern
combinations
that
exist
in
the
CriteriaToPattern
section.
Message
Variables:
criteria_id
-
The
criteria
ID
number,
which
is
an
integer
pattern_id
-
The
pattern
ID
number,
which
is
an
integer
System
Action:
The
system
will
not
use
this
configuration
and
is
still
using
the
last
valid
configuration.
Administrator
Response:
Add
a
record
using
the
criteria
and
pattern
combination,
or
change
the
pattern
in
the
CriteriaToPath
section
to
use
an
existing
criteria
and
pattern
combination,
in
the
CriteriaToPattern
section.
GTMAB1014E
The
Path
path_id
and
Level
level_id
combination
in
the
CriteriaToPath
section
does
not
exist
in
the
Path
section
of
the
configuration
file.
Explanation:
The
CriteriaToPath
section
can
only
use
a
path
and
level
combination
that
exists
in
the
Path
section.
Message
Variables:
path_id
-
The
path
ID
name
string
level_id
-
The
level
ID
number,
which
is
an
integer
System
Action:
The
system
will
not
use
this
configuration
and
is
still
using
the
last
valid
configuration.
Administrator
Response:
Add
a
record
using
the
path
and
level
combination
to
the
Path
section,
or
change
the
level
in
the
CriteriaToPath
section
to
use
an
existing
path
and
level
combination
in
the
Path
section.
GTMAB1015E
The
Path
path_id
and
Level
level_id
combination
is
not
allowed
in
the
CriteriaToPath
section.
Explanation:
When
the
Name
field
in
the
Path
section
contains
characters,
it
is
considered
static
and
cannot
dynamically
be
replaced
with
values
found
during
processing.
The
CriteriaToPath
section
is
referencing
the
level
and
path
combination
indicating
that
dynamic
text
replacement
should
occur,
but
the
corresponding
record
in
the
Path
section
already
has
data
in
the
Name
field.
This
must
be
resolved.
Message
Variables:
path_id
-
The
path
ID
name
string
level_id
-
The
level
ID
number,
which
is
an
integer
System
Action:
The
system
will
not
use
this
configuration
and
is
still
using
the
last
valid
configuration.
Administrator
Response:
Change
the
Name
field
for
the
path
and
level
in
the
Path
section
to
not
contain
characters,
or
change
the
record
in
the
CriteriaToPath
section
to
no
longer
reference
the
path
and
level
combination.
GTMAB1016E
The
operand
operand
used
by
ListName
listname_id
in
the
PatternList
section
is
not
allowed.
Explanation:
The
PatternList
section
allows
for
the
creation
of
lists
of
SQL
patterns
for
matching
purposes.
The
operand
that
contains
the
SQL
pattern
is
not
allowed
to
match
all
possible
cases.
If
all
cases
need
to
be
matched,
the
PatternList
functionality
should
not
be
used.
Message
Variables:
operand
-
A
string
that
is
used
as
a
SQL
pattern
match
operator.
listname_id
-
The
listname
ID
name
string
System
Action:
The
system
will
not
use
this
configuration
and
is
still
using
the
last
valid
configuration.
Administrator
Response:
Change
the
operand
to
use
a
more
restrictive
pattern
in
the
operand.
GTMAB1017I
No
records
to
process.
Explanation:
No
records
currently
exist
that
require
processing
by
the
system
at
this
time
for
this
function.
System
Action:
The
system
continues
to
run
and
will
process
additional
records
when
they
arrive
the
next
time
the
function
is
called.
GTMAB1018I
Deleted
number
records.
Explanation:
A
purge
has
successfully
completed
and
has
removed
the
specified
number
of
records.
Message
Variables:
number
-
The
number
of
purged
records
System
Action:
Processing
continues.
GTMAB1019I
On
enqueue
of
records
count
Business
Views
may
be
created.
Explanation:
The
abstest.ksh
script
enables
the
creation
of
business
views
using
the
data
that
currently
exist
in
the
system.
This
count
provides
an
upper
limit
on
the
number
of
business
views
that
can
be
created
based
on
the
configuration
installed
and
objects
requested.
Message
Variables:
count
-
The
number
of
possible
business
views,
which
is
an
integer
System
Action:
Processing
continues.
Chapter
3.
Automated
Business
System
Messages
-
GTMAB1001E
-
GTMAB1048E
89
Administrator
Response:
Determine
if
this
count
is
reasonable
and
matches
your
expectation.
If
so,
enqueue
the
records
to
enable
the
business
views
to
be
created.
Otherwise,
update
the
configuration
and
attempt
the
test
again.
GTMAB1020I
Attempting
to
delete
object
instance
cid
id
Explanation:
The
absdelete.ksh
script
enables
the
deletion
of
business
views
that
were
created
by
the
Automated
Business
System
process.
As
they
are
attempted,
it
reports
the
objects
as
deletion
attempts.
Message
Variables:
cid
-
The
class
ID
name.
id
-
The
object
ID,
which
is
an
integer.
System
Action:
The
system
attempts
to
delete
the
referenced
object.
GTMAB1021E
There
is
a
NULL
value
in
the
column
column
in
the
section
section.
Explanation:
The
specified
column
must
have
a
value.
Message
Variables:
column
-
The
name
of
the
affected
column.
section
-
The
name
of
the
section
where
the
column
is
located.
System
Action:
The
system
will
not
use
this
configuration
and
is
still
using
the
last
valid
configuration.
Administrator
Response:
Supply
a
valid
value
for
the
specified
column.
GTMAB1022I
Enqueued
count
Business
Views
for
possible
creation.
Explanation:
This
message
is
issued
by
the
abstest.ksh
command
when
the
-e
option
is
specified
to
enqueue
the
results
of
the
abstest.ksh
-x
option
for
creating
a
business
view.
The
count
provides
an
upper
limit
on
the
number
of
business
views
that
can
be
created.
Message
Variables:
count
-
The
number
of
possible
business
views,
which
is
an
integer
System
Action:
Processing
continues.
Administrator
Response:
Issue
the
exec
alobProcessQueueCreateLob
command
to
immediately
start
the
ABS
Creation
job,
or
wait
until
the
scheduled
ABS
Creation
job
runs
to
create
the
business
views.
GTMAB1030E
FunctionGroup
value
in
the
section
section
does
not
exist
in
the
FunctionGroup
section.
Explanation:
The
FunctionGroup
specified
by
the
value
in
the
section
named
section
does
not
exist.
Message
Variables:
value
-
The
specified
value
section
-
The
name
of
the
section.
The
section
can
be
the
following:
v
Path
v
CriteriaToPath
v
CriteriaToFunctionGroup
v
FunctionGroupRelevance
System
Action:
The
absconfig
command
fails
and
the
configuration
file
is
not
loaded.
User
Response:
Fix
the
ABS
configuration
file
so
that
there
is
a
corresponding
FunctionGroup
and
run
the
command
again.
GTMAB1031E
Instance
instance
in
section
FunctionGroup
for
FunctionName
type
does
not
exist.
Explanation:
The
instance
of
the
specified
FunctionName
section
does
not
exist.
Message
Variables:
instance
-
The
instance
that
does
not
exist
type
-
The
type
of
FunctionName
System
Action:
The
absconfig
command
fails
and
the
configuration
file
is
not
loaded.
User
Response:
Fix
the
ABS
configuration
file
so
that
there
is
a
corresponding
instance
in
the
referenced
section
and
run
the
command
again.
GTMAB1032E
parameter
for
Instance
instance
in
Section
section.
Explanation:
A
parameter
that
was
not
valid
was
specified
for
the
named
instance
in
the
named
section.
Message
Variables:
parameter
-
The
specified
parameter
that
is
not
valid
instance
-
The
name
of
the
instance
section
-
The
name
of
the
section
System
Action:
The
absconfig
command
fails
and
the
configuration
file
is
not
loaded.
User
Response:
Fix
the
ABS
configuration
file
so
that
the
parameter
value
is
in
the
allowed
range
and
run
the
command
again.
GTMAB1033E
Invalid
UserIDGroup
useridgroup
specified
for
Instance
instance
in
the
DefineServicesAndLinkToEvUsers
section.
Explanation:
A
UserIDGroup
was
specified
in
the
DefineServicesAndLinkToEvUsers
section
that
does
not
exist
in
the
UserIDGroup
section.
Message
Variables:
useridgroup
-
The
specified
UserIDGroup
that
is
not
valid
90
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
instance
-
The
name
of
the
instance
System
Action:
The
absconfig
command
fails
and
the
configuration
file
is
not
loaded.
User
Response:
Specify
an
existing
UserIDGroup
and
run
the
command
again.
GTMAB1034E
Instance
instance
must
be
unique
in
section
section.
Explanation:
The
specified
instance
is
duplicated
in
the
specified
section.
Message
Variables:
instance
-
The
name
of
the
instance
section
-
The
name
of
the
section
System
Action:
The
absconfig
command
fails
and
the
configuration
file
is
not
loaded.
User
Response:
Remove
the
duplicate
instances
from
the
section
and
run
the
command
again.
GTMAB1035E
Invalid
FunctionName
name
specified
in
section
FunctionGroup.
Explanation:
The
FunctionName
value
is
not
valid.
Message
Variables:
name
-
The
name
that
is
not
valid.
Following
are
the
valid
values:
v
SetThresholds
v
SetSendStateChangeEvent
v
SetWeights
v
DefineServicesAndLinkToEvUsers
v
DefineAndUsePBTs
System
Action:
The
absconfig
command
fails
and
the
configuration
file
is
not
loaded.
User
Response:
Specify
a
valid
FunctionName
and
run
the
command
again.
GTMAB1036E
DefineServicesAndLinkToEvUsers
is
an
invalid
FunctionName
for
FunctionGroup
group
appearing
in
the
CriteriaToPath
section.
Explanation:
The
DefineServicesAndLinkToEvUsers
name
is
not
allowed
in
a
FunctionGroup
utilized
in
the
CriteriaToPath
section.
Message
Variables:
group
-
The
name
of
the
group
System
Action:
The
absconfig
command
fails
and
the
configuration
file
is
not
loaded.
User
Response:
Remove
any
DefineServicesAndLinkToEvUsers
references
from
any
function
groups
specified
in
the
CriteriaToPath
section
and
run
the
command
again.
GTMAB1037E
FunctionGroup
group
is
not
allowed
for
Path
path
Level
level
because
the
Name
is
NULL.
Explanation:
The
FunctionGroups
group
can
only
be
specified
for
the
static
Business
Systems
in
the
Path
Section.
Message
Variables:
group
-
The
name
of
the
group
path
-
The
specified
path
level
-
The
specified
level
System
Action:
The
absconfig
command
fails
and
the
configuration
file
is
not
loaded.
User
Response:
Remove
the
FunctionGroup
from
the
specified
Path
entry
and
run
the
command
again.
GTMAB1038E
FunctionName
name
is
not
allowed
for
FunctionGroup
group
because
it
is
specifed
for
Criteria
criteria,
Pattern
pattern,
and
Class
class.
It
is
only
valid
for
class
’LOB’.
Explanation:
A
function
was
specified
that
is
not
allowed
to
be
issued
against
a
non-Business
System
resource.
Message
Variables:
name
-
The
name
of
the
function
group
-
The
name
of
the
group
criteria
-
The
name
of
the
criteria
pattern
-
The
name
of
the
pattern
class
-
The
class
name
System
Action:
The
absconfig
command
fails
and
the
configuration
file
is
not
loaded.
User
Response:
Remove
the
specified
FunctionName
from
the
specified
FunctionGroup
and
run
the
command
again.
GTMAB1039E
Stored
Procedure
procedure
failed
with
return
code
retcode.
Called
by
procedure.
Explanation:
A
stored
procedure
error
occurred.
Message
Variables:
procedure
-
The
name
of
the
stored
procedure
retcode
-
The
return
code
received
from
the
procedure
System
Action:
The
current
transaction
is
rolled
back.
Administrator
Response:
This
represents
a
logic
error.
GTMAB1040I
Business
System
with
instance
id
’instance_id’,
level
’level’,
and
Path
’path’
will
be
queued
for
creation.
Explanation:
This
message
is
issued
when
the
-v
option
is
specified
with
the
abstest
command.
This
option
lists
the
business
system
resources
that
are
being
Chapter
3.
Automated
Business
System
Messages
-
GTMAB1001E
-
GTMAB1048E
91
passed
to
the
common
listener
service
for
creation.
Message
Variables:
instance_id
-
The
path
name
of
the
business
system
resource
level
-
The
level
in
the
Path
section
where
it
will
be
created
path
-
The
Path
entry
in
the
Path
section
of
the
ABS
configuration
file
GTMAB1041I
Invoking
instance
’function_id’
of
Function
named
’function_name’
for
FunctionGroup
named
’function_group’
against
the
Business
System
with
instance
id
of
’instance_id’.
Explanation:
This
message
is
issued
when
the
-m
option
is
specified
with
the
abstest.ksh
command.
It
identifies
the
functions
being
issued
against
business
systems
that
are
specified
by
the
FunctionGroup
column
of
the
Path
section
or
the
CriteriaToPath
section
of
the
ABS
configuration
file.
Message
Variables:
function_id
-
Corresponds
to
the
ABS
configuration
file
section
of
the
same
name
function_name
-
Corresponds
to
the
instance
column
in
the
function_name
section
of
the
ABS
configuration
file
function_group
-
Corresponds
to
the
FunctionGroup
column
of
the
FunctionGroup
section
of
the
ABS
configuration
file
instance_id
-
The
complete
path
name
of
the
business
system
and
corresponds
to
the
resourcepath
column
of
the
ObjPathCache
for
the
corresponding
business
system
User
Response:
Use
the
-m
option
of
the
abstest
command
to
verify
that
the
ABS
configuration
file
is
working
as
designed
and
that
the
correct
method
instances
are
issued.
GTMAB1042I
Invoking
instance
’function_id’
of
Function
named
’function_name’
for
FunctionGroup
named
’function_group’
against
class
’class’
with
object
id
’object_id’.
Explanation:
This
message
is
issued
when
the
-m
option
is
specified
with
the
abstest.ksh
command.
It
identifies
the
functions
being
issued
against
resources
that
match
against
the
CriteriaToFunctionGroup
section
of
the
ABS
configuration
file.
Message
Variables:
function_id
-
Corresponds
to
the
ABS
configuration
file
section
of
the
same
name
function_name
-
Corresponds
to
the
instance
column
in
the
function_name
section
of
the
ABS
configuration
file
function_group
-
Corresponds
to
the
FunctionGroup
column
of
the
FunctionGroup
section
of
the
ABS
configuration
file
class
-
The
class
of
the
resource
object_id
-
The
object
ID
of
the
resource
User
Response:
Use
the
-m
option
of
the
abstest
command
to
verify
that
the
ABS
configuration
file
is
working
as
designed
and
that
the
correct
method
instances
are
being
issued.
GTMAB1043E
The
Criteria
criteria_value
and
value
pattern
pattern_value
combination
in
the
CriteriaToPath
section
does
not
exist
in
the
CriteriaToPattern
section
of
the
configuration
file.
Explanation:
In
the
CriteriaToPath
section,
a
value
of
the
format
pattern:attribute
specified
a
pattern
that
was
not
included
in
the
specified
Criteria.
Message
Variables:
criteria_value
-
The
criteria
value
from
the
CriteriaToPath
section.
pattern_value
-
The
pattern
value
from
the
Value
column
of
the
CriteriaToPath
section.
System
Action:
The
absconfig
script
fails
and
the
configuration
file
is
not
loaded.
Administrator
Response:
Correct
the
CriteriaToPath
section.
GTMAB1044E
Invalid
Operator
operator
for
Pattern
pattern,
Class
class,
and
Attribute
attribute
in
the
Pattern
section.
Explanation:
The
operator
specified
is
not
valid.
Note
that
if
the
specified
operand
is
’IS’,
then
the
Operand1
column
must
be
’NULL’
or
’NOT
NULL’.
Message
Variables:
operator
-
The
Operator
value
that
was
not
valid
pattern
-
The
Pattern
value
that
was
specified
class
-
The
Class
value
that
was
specified
attribute
-
The
Attribute
name
that
was
specified
System
Action:
The
configuration
file
is
rejected.
User
Response:
Correct
the
Operator
value
and
reload
the
configuration
file.
GTMAB1045E
The
AutoCopyEVService
FunctionName
in
FunctionGroup
group
in
the
section
Section
is
only
valid
for
a
FunctionGroup
in
the
CriteriaToPath
Section.
Explanation:
The
AutoCopyEVService
Function
can
only
be
specified
in
a
FunctionGroup
in
the
CriteriaToPath
section.
Message
Variables:
group
-
The
name
of
the
function
group
section
-
The
name
of
the
section
92
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
System
Action:
The
absconfig
command
fails
and
the
configuration
file
is
not
loaded.
User
Response:
Remove
the
AutoCopyEVService
Function
from
the
specified
FunctionGroup,
or
remove
the
FunctionGroup
from
the
specified
Section.
Run
the
command
again.
GTMAB1046E
Invalid
Value
value
for
Instance
instance
in
Section
AutoCopyEVService
Explanation:
The
specified
value
is
not
valid.
Message
Variables:
value
-
The
incorrect
value.
Valid
values
are
’1’
or
’on’.
instance
-
The
name
of
the
instance
System
Action:
The
absconfig
command
fails
and
the
configuration
file
is
not
loaded.
User
Response:
Correct
the
value
and
load
the
configuration
again.
GTMAB1047E
value
is
an
invalid
type.
Explanation:
A
pattern,
criteria,
or
path
value
that
was
not
valid
was
entered
on
the
abstest
command.
The
value
must
match
a
valid
entry
in
the
Pattern,
CriteriaToPattern,
or
Path
section
of
the
ABS
configuration
file.
Message
Variables:
value
-
The
value
that
was
not
valid
type
-
The
value
type,
which
is
either
’Pattern’,
’Criteria’,
or
’Path’
System
Action:
The
abstest
command
is
rejected.
User
Response:
Correct
the
specified
value
and
submit
the
command
again.
GTMAB1048E
Instance
instance1,
and
instance
instance2
in
section
DefineAndUsePBTs
have
duplicate
parameter
values.
This
is
not
allowed.
Explanation:
The
parameter
specifications
for
two
separate
instances
in
the
DefineAndUsePBTs
section
have
duplicate
values
(the
PBTName
value
might
be
duplicated).
These
parameters
must
be
uniquely
defined
for
each
instance
in
the
DefineAndUsePBTs
section.
Message
Variables:
instance1
-
The
first
instance
value
that
might
be
duplicated
instance2
-
The
second
instance
value
that
might
be
duplicated
System
Action:
The
absconfig
command
fails
and
the
configuration
file
is
not
loaded.
User
Response:
Remove
one
of
the
instance
definitions
and
load
the
configuration
file
again.
Chapter
3.
Automated
Business
System
Messages
-
GTMAB1001E
-
GTMAB1048E
93
Chapter
4.
Intelligent
Monitoring
for
BMC
PATROL
Messages
-
GTMIP0001E
-
GTMIP0020E,
GTMIP0002W
-
GTMIP0010W
The
following
messages
are
issued
by
Intelligent
Monitoring
for
BMC
Software
PATROL.
GTMIP0001E
Discovery
process
initialization
failed
Explanation:
The
object
discovery
process
could
not
start
because
the
communication
with
the
common
listener
service
could
not
be
established.
User
Response:
Ensure
that
all
port
numbers
are
set
correctly
and
that
the
common
listener
service
is
running,
then
start
the
process
again.
GTMIP0002E
Unable
to
send
object
with
id
instance_id
Explanation:
The
object
discovery
process
was
unable
to
send
the
instance
request
to
the
common
listener
service.
Message
Variables:
instance_id
-
The
ID
of
the
instance
User
Response:
Ensure
that
the
communication
with
the
common
listener
service
is
set
correctly.
Use
the
wimpdiscovery
command
with
the
-host
hostname
option
to
rediscover
all
instances
on
that
host.
GTMIP0003E
Unable
to
get
object
with
id
instance_id
Explanation:
The
object
discovery
process
was
unable
to
get
the
instance
from
BMC
PATROL.
Message
Variables:
instance_id
-
The
ID
of
the
instance
User
Response:
Ensure
that
BMC
PATROL
Agents
can
be
accessed.
Use
the
wimpdiscovery
command
with
the
-host
hostname
option
to
rediscover
all
instances
on
that
host.
GTMIP0004E
Unable
to
instantiate
the
TSL.
Discovery
cannot
be
executed.
Explanation:
The
discovery
process
is
unable
to
start
correctly.
User
Response:
Check
that
the
processor
is
not
overloaded,
ensure
that
you
have
enough
system
memory,
then
try
again.
GTMIP0005E
Unable
to
initialize
discovery
Explanation:
The
discovery
process
could
not
be
completed
successfully.
User
Response:
Check
that
the
processor
is
not
overloaded,
ensure
that
you
have
enough
system
memory,
then
try
again.
GTMIP0006E
Unable
to
enumerate
instances
Explanation:
The
target
node
of
the
discovery
process
is
not
listed
in
the
HOSTS.CFG
file.
User
Response:
Use
the
wimpgethosts
command
to
add
the
target
node
in
the
HOSTS.CFG
file.
GTMIP0007E
Unable
to
load
the
instances
Explanation:
The
discovery
process
is
unable
to
start
correctly.
User
Response:
Check
that
the
processor
is
not
overloaded,
ensure
that
you
have
enough
system
memory,
and
try
again.
GTMIP0008E
Discovery
cannot
be
executed.
Explanation:
The
discovery
process
is
unable
to
start
correctly.
User
Response:
Check
that
the
processor
is
not
overloaded,
ensure
that
you
have
enough
system
memory,
and
try
again.
GTMIP0009E
Discovery
process
initialization
failed
Explanation:
The
discovery
process
is
unable
to
start
correctly.
User
Response:
Check
that
the
processor
is
not
overloaded,
ensure
that
you
have
enough
system
memory,
and
try
again.
GTMIP0010E
CopyFile
Failed
(filename)
Explanation:
The
wimpgethosts
command
is
unable
to
copy
the
indicated
configuration
file
for
the
backup.
Message
Variables:
filename
-
The
name
of
the
configuration
file
User
Response:
Ensure
that
the
user
who
is
starting
the
wimpgethosts
command
has
the
right
privileges
to
access
the
indicated
file
and
the
directory
where
the
product
is
installed.
Check
that
the
file
system
has
enough
space
to
copy
that
file.
©
Copyright
IBM
Corp.
2000,
2004
95
GTMIP0011E
File
filename
cannot
be
read
Explanation:
The
wimpgethosts
command
is
unable
to
read
the
indicated
configuration
file.
Message
Variables:
filename
-
The
name
of
the
configuration
file
User
Response:
Ensure
that
the
user
who
is
starting
the
wimpgethosts
command
has
the
right
privileges
to
access
the
indicated
file.
Check
if
the
file
is
being
used
by
another
process
or
opened
by
another
user.
If
yes,
the
file
must
be
released
before
you
can
read
it.
GTMIP0012E
WriteFile
Failed
(filename)
Explanation:
The
wimpgethosts
command
is
unable
to
write
the
indicated
configuration
file.
Message
Variables:
filename
-
The
name
of
the
configuration
file
User
Response:
Ensure
that
the
user
who
is
starting
the
wimpgethosts
command
has
the
right
privileges
to
write
in
the
directory
where
the
product
is
installed
and
has
write
access
to
the
configuration
file.
Check
that
the
file
system
has
enough
space
to
create
that
file.
GTMIP0013E
Restoring
File
Failed
(filename)
Explanation:
The
wimpgethosts
command
is
unable
to
restore
the
configuration
file
of
the
indicated
backup
file.
Message
Variables:
filename
-
The
name
of
the
configuration
file
User
Response:
Ensure
that
the
user
who
is
starting
the
wimpgethosts
command
process
has
the
right
privileges
to
read
the
indicated
backup
file
and
to
write
in
the
directory
where
the
product
is
installed.
Ensure
also
that
the
user
has
write
access
to
the
configuration
file.
Check
that
the
file
system
has
enough
space
to
copy
that
file.
GTMIP0014E
Host
hostname
already
exists
Explanation:
The
host
hostname
is
already
listed
in
the
HOSTS.CFG
file.
Message
Variables:
hostname
-
The
name
of
the
host
User
Response:
Since
the
host
already
exists
in
the
configuration
file,
it
cannot
be
added.
If
you
want
to
update
its
information,
you
can
use
the
wimpgethosts
command
with
the
-host
and
-update
options.
GTMIP0015E
CreateFile
Failed
(filename)
Explanation:
The
configuration
file
cannot
be
created
or
updated.
Message
Variables:
filename
-
The
name
of
the
configuration
file
User
Response:
Ensure
that
the
user
has
write
privileges
to
that
file
or
directory.
GTMIP0016E
File
filenamecannot
be
opened
Explanation:
The
wimpgethosts
command
is
unable
to
open
the
indicated
file.
Message
Variables:
filename
-
The
name
of
the
configuration
file
or
the
desktop
files
User
Response:
Check
if
the
configuration
file,
or
any
of
the
desktop
files,
is
being
used
by
another
process
or
opened
by
another
user.
If
yes,
the
file
must
be
released
before
you
can
open
it.
GTMIP0017E
Password
is
different
Explanation:
The
Confirm
password
while
adding
or
updating
a
host
in
the
HOSTS.CFG
file
is
different
from
the
previous
one
that
was
typed.
User
Response:
Correctly
retype
the
Confirm
password.
GTMIP0018E
Could
not
encrypt
password
Explanation:
The
specified
password
cannot
be
encrypted.
User
Response:
Ensure
that
the
password
is
correct
and
try
again.
GTMIP0019E
File
filename
is
not
found
Explanation:
The
wimpgethosts
command
is
unable
to
find
the
indicated
file.
Message
Variables:
filename
-
The
name
of
the
configuration
file
or
the
desktop
files
User
Response:
Ensure
that
the
user
who
is
starting
the
wimpgethosts
command
has
the
right
privileges
to
read
in
the
directory
where
the
product
is
installed
and
verify
the
existence
of
the
desktop
files.
GTMIP0020E
Host
hostname
does
not
exist
Explanation:
During
the
List/Update/Remove
of
a
single
host,
the
wimpgethosts
command
is
unable
to
find
the
indicated
host
in
the
configuration
file.
Message
Variables:
hostname
-
The
name
of
the
host
User
Response:
Ensure
that
the
hostname
is
correct.
GTMIP0002W
DNS
service
unavailable
or
at
wrong
level.
Duplicated
hosts
may
be
generated.
Explanation:
Currently
the
DNS
service
is
unavailable
and
can
cause
the
generation
of
duplicated
hosts
in
the
configuration
file.
User
Response:
Ensure
that
the
network
is
working
96
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
and
the
DNS
service
is
available
and
correctly
configured.
GTMIP0003W
Password
for
host
(hostname)
and
user
(username)
has
been
taken
from
file
filename
Explanation:
When
performing
the
wimpgethosts
command
with
the
-dt
option,
a
host
with
the
same
user
can
exist
in
more
than
one
desktop
file
or
even
in
the
configuration
file.
In
this
case,
the
command
gets
the
host
information
of
only
one
file
and
displays
this
message
to
advise
the
user
from
which
file
the
information
was
taken.
Message
Variables:
hostname
-
The
name
of
the
host
username
-
The
name
of
the
user
filename
-
The
name
of
the
file
GTMIP0010W
Unable
to
establish
connection
to
agent
on
host
hostname
Explanation:
Currently
the
indicated
host
is
unavailable.
Message
Variables:
hostname
-
The
name
of
the
host
User
Response:
Ensure
that
the
network
is
working
and
that
the
PATROL
agent
is
running
correctly
in
the
host
hostname,
then
try
again.
Check
that
the
hostname
or
IP
address
is
correct
or
check
that
the
limit
of
TCP
connections
was
not
reached.
Chapter
4.
Intelligent
Monitoring
for
BMC
PATROL
Messages
-
GTMIP0001E
-
GTMIP0020E,
GTMIP0002W
-
GTMIP0010W
97
Chapter
5.
CICSPlex
SM
Data
Source
Messages
-
GTMCP0001E
-
GTMCP5024I
The
following
messages
relate
to
the
CICSPlex®
SM
data
source.
These
messages
are
issued
by
the
component
of
Tivoli
Business
Systems
Manager
responsible
for
the
discovery
and
the
maintenance
of
CICSPlex
SM
resources.
GTMCP0001E
UNABLE
TO
LOAD
PROGRAM
pgm
Explanation:
The
CICSPlex
SM
batch
discovery
program
was
unable
to
load
the
specified
program.
Message
Variables:
pgm
-
The
name
of
the
program
that
the
CICSPlex
SM
batch
discovery
program
could
not
load
System
Action:
The
CICSPlex
SM
batch
discovery
program
ends.
User
Response:
Determine
why
the
specified
program
could
not
be
loaded.
Check
if
the
correct
STEPLIB
concatenation
exits
for
the
step.
GTMCP0002I
CONNECT
IN
PROGRESS
FOR
CICSPLEX=cicsplex_name
CONTEXT=cmas_name
SCOPE=scope
VERSION=version
Explanation:
The
CICSPlex
SM
batch
discovery
program
is
about
to
connect
to
CICSPlex
SM.
Message
Variables:
cicsplex_name
-
The
name
of
the
requested
CICSPlex
cmas_name
-
The
CMAS
name
for
which
the
request
specifies
context
scope
-
The
scope
of
the
collected
data
version
-
The
version
number
of
CICSPlex
SM
used
for
this
connection
System
Action:
Processing
continues.
GTMCP0006E
INVALID
RETURN
CODE
FROM
CICSPLEX
SM
REQUEST
request
FOR
OBJECT
table_name
RESPONSE=response_code
REASON=reason_code
Explanation:
A
return
code
that
was
unexpected
or
not
valid
was
received
from
the
CICSPlex
SM
request.
Message
Variables:
request
-
The
type
of
request
that
failed
table_name
-
The
name
of
the
CICSPlex
SM
table
issued
for
the
request
response_code
-
The
decimal
response
code
reason_code
-
The
decimal
reason
code
System
Action:
The
CICSPlex
SM
discovery
program
ends.
User
Response:
With
the
response
and
reason
codes,
refer
to
the
CICSPlex
SM
Application
Program
Guide
to
determine
the
cause
of
the
error.
If
the
problem
persists,
contact
IBM
Software
Support.
GTMCP0007E
UNABLE
TO
OPEN
OUTPUT
FILE:
AOPDFILE.
RC=return_code
Explanation:
The
CICSPlex
SM
discovery
program
was
unable
to
open
the
AOPDFILE
output
file.
Message
Variables:
return_code
-
The
return
code
from
the
open
request
System
Action:
The
CICSPlex
SM
discovery
program
ends.
User
Response:
Determine
why
it
was
not
possible
to
open
the
output
file.
If
the
problem
persists,
contact
IBM
Software
Support.
GTMCP0008E
UNABLE
TO
INITIALIZE
REXX
ENVIRONMENT.
RC=return_code
Explanation:
The
CICSPlex
SM
batch
discovery
program
was
unable
to
initialize
a
REXX
environment.
Message
Variables:
return_code
-
The
return
code
from
the
IRXINIT
request
System
Action:
The
CICSPlex
SM
discovery
program
ends.
User
Response:
Refer
to
TSO/E
REXX
Reference
to
determine
the
meaning
of
the
return
code.
If
the
problem
persists,
contact
IBM
Software
Support.
GTMCP0009E
UNABLE
TO
LOCATE
REXX
ROUTINE
name
RC=return_code
Explanation:
The
CICSPlex
SM
batch
discovery
program
was
unable
to
locate
the
specific
REXX
routine
in
the
AOPEXEC
concatenation.
Message
Variables:
name
-
The
routine
name
that
could
not
be
located
return_code
-
The
return
code
from
the
IRXLOAD
request
System
Action:
The
CICSPlex
SM
batch
discovery
program
ends.
©
Copyright
IBM
Corp.
2000,
2004
99
User
Response:
Refer
to
TSO/E
REXX
Reference
to
determine
the
meaning
of
the
return
code.
If
the
problem
persists,
contact
IBM
Software
Support.
GTMCP0010E
REXX
function
FAILED
FOR
ROUTINE
name
RC=return_code
REXX
RC=return_code
Explanation:
The
CICSPlex
SM
batch
discovery
program
received
a
return
code
that
was
not
valid
when
running
a
function
in
relation
to
the
REXX
program.
Message
Variables:
function
-
The
type
of
function
that
failed,
which
can
be
LOAD,
EXEC,
FREE,
or
TERM
name
-
The
name
of
the
REXX
routine
return_code
-
The
return
code
from
the
request
return_code
-
The
REXX
return
code
from
the
request
System
Action:
The
CICSPlex
SM
discovery
program
ends.
User
Response:
Refer
to
TSO/E
REXX
Reference
to
determine
the
meaning
of
the
return
codes.
If
the
problem
persists,
contact
IBM
Software
Support.
GTMCP0011E
INVALID
VALUE
SPECIFIED
FOR
PARAMETER:
parameter
Explanation:
The
CICSPlex
SM
discovery
program
discovered
a
parameter
that
was
not
valid.
Message
Variables:
parameter
-
The
parameter
name
that
was
not
valid.
Valid
names
are
CICSPLEX,
CONTEXT,
SCOPE,
SECVALUE,
or
USERID
System
Action:
The
CICSPlex
SM
discovery
program
ends.
User
Response:
Correct
the
indicated
parameter
and
run
the
job
again.
GTMCP0012E
UNABLE
TO
OBTAIN
SUFFICIENT
VIRTUAL
STORAGE
Explanation:
The
CICSPlex
SM
discovery
program
was
unable
to
obtain
the
required
amount
of
virtual
storage.
System
Action:
The
CICSPlex
SM
discovery
program
ends.
User
Response:
You
must
ensure
that
the
region
parameter
provided
does
not
restrict
the
storage
available
to
the
program.
GTMCP0013I
CPSM
SUBNAME
ENTERED,
CICSPLEXNAME=plexname
SUBNAME=subname
Explanation:
The
CICSPlex
being
processed
is
defined
to
Tivoli
Business
Systems
Manager
with
a
subname.
Message
Variables:
plexname
-
The
name
of
the
CICSPlex
as
known
to
CICSPlex
System
Manager
(CPSM)
subname
-
The
subname
used
to
qualify
the
CICSPlex
in
Tivoli
Business
Systems
Manager
System
Action:
Processing
continues.
GTMCP0014I
CICSPLEX
CMAS
cmasname
IS
UNAVAILABLE.
UNABLE
TO
CONTINUE.
Explanation:
The
batch
discovery
program
cannot
connect
to
the
CMAS.
This
message
indicates
that
there
is
no
CMAS
of
this
name
on
this
system
at
the
release
level
being
used
for
this
connection.
Message
Variables:
cmasname
-
The
name
of
the
CMAS
used
for
this
connection
System
Action:
The
batch
discovery
program
ends
unexpectedly
with
an
abend
code
of
U0008.
User
Response:
Verify
that
the
CMAS
name
and
operating
system
specified
in
the
CICSPlex
properties
on
the
Tivoli
Business
Systems
Manager
console
matches
the
Maintenance
point
CMAS
for
the
CICSPlex.
Also,
verify
that
the
SEYUAUTH
library
concatenated
to
the
discovery
job
matches
the
version
of
CICSPlex
System
Manager
used
by
the
CMAS.
GTMCP0015I
CICSPLEX
plexname
IS
NOT
KNOWN
to
CMAS
cmasname
Explanation:
CICSPlex
SM
indicated
that
the
CICSPlex
is
not
known
to
the
CMAS.
Message
Variables:
plexname
-
The
name
of
the
CICSPlex
being
processed
subname
-
The
name
of
the
CMAS
used
for
this
connection
System
Action:
The
batch
discovery
program
ends
unexpectedly
with
an
abend
code
of
U0008.
User
Response:
Verify
that
the
CMAS
name
and
operating
system
specified
in
the
CICSPlex
properties
on
the
Tivoli
Business
Systems
Manager
console
matches
the
maintenance
point
CMAS
for
the
CICSPlex.
Also,
verify
that
the
SEYUAUTH
library
concatenated
to
the
discovery
job
matches
the
version
of
CICSPlex
System
Manager
used
by
the
CMAS.
GTMCP0016E
UNABLE
TO
OBTAIN
SUFFICIENT
VIRTUAL
STORAGE.
AMOUNT
REQUESTED
WAS
length.
Explanation:
The
batch
discovery
program
cannot
obtain
sufficient
virtual
storage
for
a
data
buffer.
Message
Variables:
length
-
The
length
of
storage
requested
System
Action:
The
batch
discovery
program
ends
100
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
unexpectedly
with
an
abend
code
of
U0008.
User
Response:
Ensure
that
the
region
parameter
does
not
restrict
the
storage
available
to
the
program.
GTMCP0020E
INVALID
RETURN
CODE
FROM
CICSPLEX
SM
REQUEST
name
FOR
OBJECT
table_name
RESPONSE=response_code
REASON=reason_code
Explanation:
A
return
code
was
received
from
a
CICSPlex
SM
request
that
was
not
valid.
Message
Variables:
name
-
The
name
of
the
type
of
request
that
failed
table_name
-
The
name
of
the
CICSPlex
SM
table
that
was
issued
response_code-
The
decimal
response
code
reason_code
-
The
decimal
reason
code
System
Action:
The
CICSPlex
SM
discovery
program
ends.
User
Response:
Use
the
response
and
reason
codes
that
are
provided
and
refer
to
the
CICSPlex
SM
Application
Programming
Guide
to
determine
the
cause
of
the
error.
If
the
problem
persists,
contact
IBM
Software
Support.
GTMCP0021E
UNABLE
TO
OBTAIN
SUFFICIENT
VIRTUAL
STORAGE
Explanation:
The
CICSPlex
task
was
unable
to
obtain
the
required
virtual
storage.
System
Action:
The
CICSPlex
task
ends.
User
Response:
Search
for
other
messages
that
indicate
a
virtual
storage
problem
within
the
source/390
object
pump.
If
the
problem
persists,
contact
IBM
Software
Support.
GTMCP0022I
CONNECT
IN
PROGRESS
FOR
CONTEXT=name
SCOPE=scope
VERSION=version
Explanation:
A
CICSPlex
task
is
connecting
with
CICSPlex
SM.
Message
Variables:
name
-
The
name
of
the
CMAS
that
the
request
has
specified
scope
-
The
scope
of
the
data
that
is
collected
version
-
The
version
number
that
is
used
for
this
CICSPlex
SM
connection
System
Action:
Processing
continues.
GTMCP0023I
INITIALIZATION
COMPLETE
FOR
CICSPLEX
name
Explanation:
The
CICSPlex
task
has
successfully
initialized.
Message
Variables:
name
-
The
name
of
the
CICSPlex
task
that
was
initialized
System
Action:
Processing
continues.
GTMCP0024E
UNABLE
TO
LOAD
PROGRAM
pgm
Explanation:
The
CICSPlex
task
was
unable
to
load
the
specified
program.
Message
Variables:
pgm
-
The
name
of
the
program
that
could
not
be
loaded
System
Action:
The
CICSPlex
task
ends.
User
Response:
Determine
why
the
specified
program
could
not
be
loaded.
Check
to
see
if
the
correct
STEPLIB
concatenation
exists
for
the
source/390
object
pump.
GTMCP0026I
SHUTDOWN
COMPLETE
FOR
CICSPLEX
name
Explanation:
A
CICSPlex
task
has
successfully
ended.
Message
Variables:
name
-
The
CICSPlex
name
of
the
task
that
successfully
ended
System
Action:
Processing
continues.
GTMCP0027E
INVALID
DATA
SPECIFIED
FOR
parameter
Explanation:
The
CICSPlex
task
detected
a
parameter
that
was
not
valid.
Message
Variables:
parameter
-
The
name
of
the
CICSPlex
parameter
that
was
not
valid.
Valid
names
can
be
CONTEXT,
SECVALUE,
or
USERID
System
Action:
The
CICSPlex
task
ends.
User
Response:
Check
the
attributes
when
you
created
the
CICSPlex
resource
in
the
console.
If
the
problem
persists,
contact
IBM
Software
Support.
GTMCP0028E
UNABLE
TO
LOCATE
CICSPLEX
ANCHOR
DURING
TASK
SHUTDOWN
Explanation:
There
was
an
internal
error
upon
shut
down
of
a
CICSPlex
task.
System
Action:
The
CICSPlex
task
continues
to
end.
User
Response:
Collect
the
job
log
and
the
AOP
log
from
the
source/390
object
pump
job
and
contact
IBM
Software
Support.
Chapter
5.
CICSPlex
SM
Data
Source
Messages
-
GTMCP0001E
-
GTMCP5024I
101
GTMCP0033E
INVALID
CICSPLEX
TASK
REQUEST,
VALUE
SPECIFIED
IS=function
Explanation:
The
CICSPlex
task
request
contained
a
function
that
was
not
valid.
Message
Variables:
function
-
The
name
of
the
function
that
was
requested
by
the
CICSPlex
task
System
Action:
The
CICSPlex
task
ends
without
action.
User
Response:
Collect
all
logs
and
contact
IBM
Software
Support.
This
is
a
result
of
an
internal
error.
GTMCP0036I
CICSPLEX
CMAS
cmasname
IS
UNAVAILABLE.
UNABLE
TO
MONITOR
CICSPLEX
plexname
Explanation:
The
source/390
object
pump
cannot
connect
to
the
CMAS.
This
message
indicates
that
there
is
no
CMAS
of
this
name
on
this
system
at
the
release
level
being
used
for
this
connection.
Message
Variables:
cmasname
-
The
name
of
the
CMAS
used
for
this
connection
plexname
-
The
name
of
the
CICSPlex
being
processed
System
Action:
The
CICSPlex
is
not
monitored.
User
Response:
Verify
that
the
CMAS
name
and
operating
system
specified
in
the
CICSPlex
properties
on
the
Tivoli
Business
Systems
Manager
console
matches
the
maintenance
point
CMAS
for
the
CICSPlex.
Also
verify
that
the
SEYUAUTH
library
concatenated
to
the
source/390
object
pump
matches
the
version
of
CICSPlex
System
Manager
used
by
the
CMAS.
GTMCP0037I
CICSPLEX
cicsplex_name
IS
NOT
KNOWN
TO
CMAS
cmas_name
Explanation:
The
CICSPlex
task
was
not
known
to
the
CMAS
specified.
Message
Variables:
cicsplex_name
-
The
name
of
the
unknown
CICSPlex
task
cmas_name
-
The
name
of
the
CMAS
specified
as
a
maintenance
point
System
Action:
Processing
continues.
User
Response:
Attempt
to
start
the
task
again
with
the
correct
CICSPlex
name.
GTMCP0040E
UNABLE
TO
OBTAIN
SUFFICIENT
VIRTUAL
STORAGE
Explanation:
The
CICSPlex
initialization
could
not
complete.
System
Action:
The
source/390
object
pump
stops.
User
Response:
Look
for
other
messages
that
indicate
a
virtual
storage
problem
within
the
source/390
object
pump.
If
the
problem
persists,
contact
IBM
Software
Support.
GTMCP0041E
UNABLE
TO
LOAD
PROGRAM
name
Explanation:
The
source/390
object
pump
could
not
load
the
specified
program.
Message
Variables:
name
-
The
name
of
the
program
that
was
not
loaded
System
Action:
The
source/390
object
pump
stops.
User
Response:
Determine
why
the
specified
program
did
not
load.
Check
if
the
correct
STEPLIB
concatenation
exists
for
the
source/390
object
pump.
GTMCP0060I
CICSPLEX
COMMAND
STARTED
Explanation:
A
CICSPLEX
command
was
issued.
System
Action:
Processing
continues.
GTMCP0061E
CICSPLEX
COMMAND
value
UNKNOWN
USE
SHOW,
START,
STOP
DEBUGON
OR
DEBUGOFF
Explanation:
A
CICSPLEX
command
was
issued
with
an
option
that
was
not
valid.
Message
Variables:
value
-
The
option
value
that
was
not
recognized
by
the
CICSPLEX
command
connection
System
Action:
The
command
ends.
User
Response:
Enter
the
command
again
using
a
valid
option.
GTMCP0062E
CICSPLEX
ANCHOR
NOT
FOUND
Explanation:
There
was
an
internal
error
and
the
CICSPLEX
command
was
unable
to
locate
the
CICSPlex
anchor.
System
Action:
The
CICSPLEX
command
ends.
User
Response:
Collect
all
logs
and
contact
IBM
Software
Support.
GTMCP0063E
AN
INVALID
VALUE
WAS
SUPPLIED
FOR
CICSPLEX
COMMAND
KEYWORD
name
Explanation:
A
value
was
specified
for
a
keyword
that
was
not
valid.
Message
Variables:
name
-
The
name
of
the
keyword
that
was
entered
incorrectly
System
Action:
The
command
ends.
User
Response:
Enter
the
command
again
using
a
valid
keyword.
102
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
GTMCP0064I
NAME
OF
CICSPLEX
CMAS
Explanation:
The
first
line
of
the
SHOW
command
output
is
displayed.
System
Action:
Processing
continues.
GTMCP0065I
name
context
Explanation:
Information
about
the
CICSPlex
task
that
is
currently
running
on
the
source/390
object
pump
is
displayed.
System
Action:
Processing
continues.
GTMCP0066I
CICSPLEX
SHOW
COMMAND
COMPLETE,
NUMBER
DISPLAYED
WAS
count
Explanation:
This
message
forms
the
last
line
of
the
SHOW
command
Message
Variables:
count
-
The
number
of
CICSPlex
tasks
that
are
displayed
by
this
command
System
Action:
Processing
continues.
GTMCP0067E
UNABLE
TO
OBTAIN
WORKING
STORAGE
FOR
CICSPLEX
COMMAND
Explanation:
The
CICSPLEX
command
was
unable
to
obtain
the
required
virtual
storage.
System
Action:
The
CICSPLEX
command
ends.
User
Response:
Search
for
other
messages
that
indicate
a
virtual
storage
problem
within
the
source/390
object
pump.
Contact
IBM
Software
Support.
GTMCP0068I
UNABLE
TO
LOCATE
CICSPLEX
TASK
name
Explanation:
A
CICSPLEX
STOP
command
was
issued
for
a
CICSPlex
that
could
not
be
located
within
the
source/390
object
pump.
Message
Variables:
name
-
The
name
of
the
CICSPlex
task
that
issued
the
STOP
command
System
Action:
The
CICSPLEX
command
ends.
User
Response:
Issue
the
CICSPLEX
command
to
determine
what
tasks
are
active.
If
required,
enter
the
command
again
with
the
correct
CICSPlex
name.
GTMCP0069I
SHUTDOWN
REQUESTED
FOR
CICSPLEX
name
Explanation:
A
CICSPLEX
STOP
command
was
issued
for
a
CICSPlex.
Message
Variables:
name
-
The
name
of
the
CICSPlex
that
was
issued
the
STOP
command
System
Action:
The
CICSPlex
task
is
required
to
shutdown.
GTMCP0070I
START
REQUEST
FAILED
CICSPLEX
name
ALREADY
ACTIVE
Explanation:
A
CICSPLEX
START
command
was
issued
for
a
CICSPlex
that
was
already
active
within
the
source/390
object
pump.
Message
Variables:
name
-
The
name
of
the
CICSPlex
System
Action:
The
CICSPLEX
command
ends.
User
Response:
Issue
the
SHOW
command
to
determine
the
CICSPlex
task
which
are
active.
If
required,
enter
the
command
again
with
the
correct
name.
GTMCP0071I
MONITORING
START
REQUESTED
FOR
CICSPLEX
name
Explanation:
A
CICSPLEX
START
command
was
issued
for
a
CICSPlex.
Message
Variables:
name
-
The
name
of
the
CICSPlex
System
Action:
The
CICSPlex
task
is
dispatched.
GTMCP0072I
CICSPLEX
DEBUG
ON
COMMAND
COMPLETE
Explanation:
A
CICSPLEX
command
has
been
processed
to
enable
the
Debug
mode
for
one
or
more
CICSPlex
tasks.
System
Action:
Processing
continues
with
the
Debug
mode
active.
GTMCP0073I
CICSPLEX
DEBUG
OFF
COMMAND
COMPLETE
Explanation:
A
CICSPLEX
command
has
been
processed
to
disable
the
debug
mode
for
one
or
more
CICSPlex
tasks.
System
Action:
Processing
continues
with
the
debug
mode
inactive.
GTMCP0080E
INVALID
GTMCPXRM
FUNCTION
DETECTED
Explanation:
There
was
an
internal
error
detected
by
the
CICSPlex
Cross
Reference
Manager.
System
Action:
Results
are
unpredictable.
User
Response:
Collect
all
the
logs
and
contact
IBM
Software
Support.
Chapter
5.
CICSPlex
SM
Data
Source
Messages
-
GTMCP0001E
-
GTMCP5024I
103
GTMCP0082E
CICSPLEX
SM
request
REQUEST
FOR
TABLE
name
RESPONSE=response_code
REASON=reason_code
Explanation:
A
return
code
was
issued
from
a
CICSPlex
request
that
was
not
valid.
Message
Variables:
request
-
The
type
of
request
that
failed
name
-
The
name
of
the
CICSPlex
SM
table
response_code
-
The
decimal
response
code
reason_code
-
The
decimal
reason
code
System
Action:
The
CICSPlex
SM
discovery
ends.
User
Response:
Use
the
response
and
reason
codes
and
refer
to
the
CICSPlex
SM
Application
Programming
Guide
to
determine
the
cause
of
the
error.
Contact
IBM
Software
Support.
GTMCP0083E
UNABLE
TO
OBTAIN
SUFFICIENT
VIRTUAL
STORAGE.
AMOUNT
REQUESTED
WAS
size
Explanation:
Unable
to
obtain
the
required
amount
of
virtual
storage.
Message
Variables:
size
-
The
amount
of
storage
that
was
requested
but
not
provided
System
Action:
The
CICSPlex
task
ends.
User
Response:
Look
for
other
messages
about
virtual
storage
problems.
Contact
IBM
Software
Support.
GTMCP0084E
META
DATA
FOR
TABLE
name
DOES
NOT
CONTAIN
DESCRIPTION
FOR
field_name
Explanation:
The
CICSPlex
Cross
Reference
Manager
was
unable
to
locate
Meta
data
for
the
specified
field
in
the
table.
Message
Variables:
name
-
The
name
of
the
CICSPlex
SM
table
field_name
-
The
name
of
the
field
that
could
not
be
located
System
Action:
The
CICSPlex
task
ends.
User
Response:
This
an
internal
error.
Collect
all
logs
and
contact
IBM
Software
Support.
GTMCP0086E
UNABLE
TO
BUILD
CICSPLEX
CROSS
REFERENCE
TABLES
Explanation:
The
CICSPlex
task
was
unable
to
construct
the
cross
reference
tables.
System
Action:
The
results
are
unpredictable.
User
Response:
Collect
all
logs
and
contact
IBM
Software
Support.
GTMCP0100E
UNABLE
TO
OBTAIN
SUFFICIENT
VIRTUAL
STORAGE
Explanation:
The
CICSPlex
task
was
unable
to
obtain
the
required
virtual
storage.
System
Action:
The
CICSPlex
task
ends.
User
Response:
Look
for
other
messages
that
indicate
a
virtual
storage
problem
with
the
source/390
object
pump.
If
the
problem
persists,
contact
IBM
Software
Support.
GTMCP0101E
CONSOLE
name
IS
ALREADY
ACTIVE.
NETID
RETRIEVAL
CANNOT
BE
PERFORMED
Explanation:
The
CICSPlex
Cross
Reference
Manager
was
unable
to
allocate
a
console
when
executing
the
batch
discovery
program
because
the
console
was
already
active.
Message
Variables:
name
-
The
name
of
the
console,
which
is
the
same
as
the
job
name
System
Action:
Processing
continues.
The
discovery
is
unable
to
determine
the
host
for
the
CICSPlex
SM
resources.
User
Response:
Refer
to
the
authorized
Assembler
Services
reference
to
determine
the
cause
of
the
error.
If
the
problem
persists,
contact
IBM
Software
Support.
GTMCP0102E
ERROR
OPENING
EXTENDED
CONSOLE
name
RETURN
CODE=return_code
REASON
CODE
=reason_code
Explanation:
The
CICSPlex
Cross
Reference
Manager
was
unable
to
allocate
a
console
when
executing
the
batch
discovery
program
due
to
a
return
code
received
from
the
MCSOPER
request
that
was
not
valid.
Message
Variables:
name
-
The
name
of
the
console,
which
is
the
same
as
the
job
name
return_code
-
The
return
code
from
the
MCSOPER
request
reason_code
-
The
reason
code
from
the
MCSOPER
request
System
Action:
Processing
continues.
The
discovery
is
unable
to
determine
the
host
for
the
CICSPlex
SM
resources.
User
Response:
Refer
to
the
authorized
Assembler
Services
reference
to
determine
the
cause
of
the
error.
If
the
problem
persists,
contact
IBM
Software
Support.
GTMCP0103E
ERROR
CLOSING
EXTENDED
CONSOLE.
RETURN
CODE=return_code
REASON
CODE=reason_code
Explanation:
The
CICSPlex
Cross
Reference
Manager
received
an
error
when
closing
the
extended
console.
104
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
Message
Variables:
return_code
-
The
return
code
from
the
MCSOPER
request
reason_code
-
The
reason
code
from
the
MCSOPER
request
System
Action:
Processing
continues.
User
Response:
Refer
to
the
authorized
Assembler
Services
reference
to
determine
the
cause
of
the
error.
If
the
problem
persists,
contact
IBM
Software
Support.
GTMCP0105E
ERROR
PARSING
HOST
NETID
CPNAME
Explanation:
The
CICSPlex
Cross
Reference
Manager
was
unable
to
interpret
a
message
to
determine
the
host
CICSPLEX
name.
System
Action:
Processing
continues.
The
discovery
program
is
unable
to
determine
the
host
for
the
CICSPlex
SM
resources.
User
Response:
The
message
indicates
an
internal
error.
It
is
followed
by
message
GTMCP0106E,
which
displays
the
response.
Collect
all
logs
and
contact
IBM
Software
Support.
GTMCP0106E
response_line
Explanation:
The
CICSPlex
Cross
Reference
Manager
was
unable
to
interpret
a
message
to
determine
the
host
CICSPLEX
name.
This
message
displays
the
line.
Message
Variables:
response_line
-
The
message
that
the
program
could
not
interpret
System
Action:
Processing
continues.
The
discovery
program
is
unable
to
determine
the
host
for
the
CICSPlex
SM
resources.
User
Response:
This
message
indicates
an
internal
error.
It
is
preceded
by
message
GTMCP0105E.
Collect
all
logs
and
contact
IBM
Software
Support.
GTMCP0107E
ERROR
ON
EXTENDED
CONSOLE
GET
MESSAGE
REQUEST
RETURN
CODE=return_codeREASON
CODE=reason_code
Explanation:
The
CICSPlex
Cross
Reference
Manager
received
an
error
when
requesting
a
message
from
an
extended
console.
Message
Variables:
return_code
-
The
return
code
from
the
MCSOPER
request
reason_code
-
The
reason
code
from
the
MCSOPER
request
System
Action:
Processing
continues.
User
Response:
Refer
to
the
authorized
Assembler
Services
reference
to
determine
the
cause
of
the
error.
If
the
problem
persists,
contact
IBM
Software
Support.
GTMCP1000E
ERROR
RETURN
CODE
return_code
RECEIVED
FORM
CICSPLEX
SM
API
CALL
name
IN
PROGRAM
pgm
STATUS
CODE
IS
status_code
Explanation:
An
error
code
was
received
in
response
to
the
CICSPlex
SM
API
call
listed.
The
status
code
value
was
also
returned
by
the
API
call.
Message
Variables:
return_code
-
The
error
return
code
from
the
CICSPlex
SM
API
call
name
-
The
name
of
the
API
call
pgm
-
The
name
of
the
program
that
issued
the
error
message
status_code
-
The
status
code
returned
from
the
API
call
System
Action:
Tivoli
Business
Systems
Manager
is
attempting
to
acquire
CICS
information
from
the
CICSPlex
SM
API
for
resource
discovery
or
monitoring.
User
Response:
Use
the
API
name,
return
code,
and
status
code
to
find
out
more
information
on
the
cause
of
the
error.
Refer
to
the
CICSPlex
SM
API
Reference.
GTMCP1001E
ERROR
STATUS
CODE
status_code
RECEIVED
FROM
CICSPLEX
SM
API
CALL
name
IN
PROGRAM
pgm
Explanation:
A
status
code
was
received
in
response
to
the
CICSPlex
SM
API
call.
Message
Variables:
status_code
-
The
status
code
returned
from
the
API
call
name
-
The
name
of
the
specific
API
call
in
error
pgm
-
The
name
of
the
program
that
issued
the
error
System
Action:
Tivoli
Business
Systems
Manager
is
attempting
to
get
CICS
information
from
the
CICSPlex
SM
API
for
resource
discovery
or
monitoring.
User
Response:
Use
the
API
name
and
status
code
to
find
out
more
information
on
the
cause
of
the
error.
Refer
to
the
CICSPlex
SM
API
Reference.
GTMCP1002E
MESSAGE
name
RETURNED
FROM
GTMRXCPF
CALL
IN
PROGRAM
pgm
Explanation:
A
message
was
returned
from
the
internal
routine,
GTMRXCPF.
Message
Variables:
name
-
Source
of
the
line
in
error
pgm
-
The
name
of
the
program
that
issued
the
error
System
Action:
Tivoli
Business
Systems
Manager
is
running
an
internal
process.
For
example,
sending
a
record.
User
Response:
Contact
IBM
Software
Support
and
provide
the
message
information.
Chapter
5.
CICSPlex
SM
Data
Source
Messages
-
GTMCP0001E
-
GTMCP5024I
105
GTMCP1003E
AN
ERROR
type
OCCURRED
IN
PROGRAM
pgm
ON
LINE
number
THE
SOURCE
LINE
IS
text
Explanation:
An
error
occurred
in
the
program
on
a
specific
line.
Message
Variables:
type
-
The
type
of
programming
error
that
occurred
pgm
-
The
name
of
the
program
that
issued
the
error
number
-
The
line
in
the
program
where
the
error
occurred
text
-
The
line
of
text
where
the
error
occurred
System
Action:
Tivoli
Business
Systems
Manager
is
running.
User
Response:
Contact
IBM
Software
Support
and
provide
the
message
information.
GTMCP1004E
UNDEFINED
ACTION
CODE
action_code
IN
PROGRAM
pgm
Explanation:
An
unexpected
action
code
in
a
CICSPlex
SM
resource
table
has
been
identified.
Message
Variables:
action_code
-
The
value
of
the
action
code
variable
pgm
-
The
name
of
the
program
that
issued
the
error
System
Action:
Tivoli
Business
Systems
Manager
is
processing
information
on
updating
a
resource.
User
Response:
Contact
IBM
Software
Support
and
provide
the
message
information.
GTMCP1005E
ERROR
RETURNED
FROM
CICSPLEX
SM
API
CALL
name
IN
PROGRAM
pgm
RESPONSE
=
response_code
REASON
=
reason_code
Explanation:
An
error
code
was
received
in
response
to
the
CICSPlex
SM
API
call
listed.
Message
Variables:
name
-
The
name
of
the
CICSPlex
SM
API
call
pgm
-
The
name
of
program
issuing
the
error
response_code
-
The
response
code
value
of
the
CICSPlex
SM
API
call
reason_code
-
The
reason
code
value
of
the
CICSPlex
SM
API
call
System
Action:
Tivoli
Business
Systems
Manager
is
attempting
to
get
CICS
information
from
the
CICSPlex
SM
API
for
resource
discovery
or
monitoring.
User
Response:
Use
the
API
name
and
status
code
to
find
out
more
information
on
the
cause
of
the
error.
Refer
to
the
CICSPlex
SM
API
Reference.
GTMCP1006E
UNRECOGNIZED
RETURN
CODE
return_code
IN
PROGRAM
pgm
Explanation:
An
unrecognized
return
code
was
found
in
the
program.
Message
Variables:
return_code
-
The
value
of
the
return
code
pgm
-
The
name
of
the
program
that
issued
the
error
System
Action:
Tivoli
Business
Systems
Manager
is
attempting
to
get
CICS
information
from
the
CICSPlex
SM
API
for
resource
discovery
or
monitoring.
User
Response:
Contact
IBM
Software
Support
with
the
message
information.
GTMCP5000I
procedure:
src_cid,
src_id,
format_type,
action_type,
date_time,
seq_num,
obj_type_id,
name
Explanation:
The
procedure
is
processing
a
CICSPlex
record
for
the
specified
items.
Message
Variables:
procedure
-
The
name
of
the
procedure
being
processed.
src_cid
-
The
resource
class
of
the
resource
for
which
the
event
is
being
processed
src_id
-
The
resource
class
ID
of
the
resource
for
which
the
event
is
being
processed
format_type
-
The
format
type
of
the
event
being
processed
action_type
-
The
action
type
of
the
event
being
processed
date_time
-
The
date
and
time
the
event
was
processed
seq_num
-
The
sequence
number
of
the
event
being
processed
obj_type_id
-
The
resource
type
of
event
being
processed.
Valid
types
are
as
follows:
v
CIPX
-
Event
for
CICSPlex
resource
v
CICM
-
Event
for
CMAS
resource
v
CIMA
-
Event
for
MAS
resource
v
CICL
-
Event
for
CMAS
to
CMAS
connection
resource
v
CICO
-
Event
for
MAS
to
MAS
connection
resource
v
CISG
-
Event
for
CICSPlex
System
Group
resource
v
CIFL
-
Event
for
File
resource
v
CITL
-
Event
for
Transaction
resource
v
CID2
-
Event
for
CICS
to
DB2
connection
resource
v
CICB
-
Event
for
Corba
Server
resource
v
CIJF
-
Event
for
Far
File
resource
name
-
The
name
of
CICSPlex
resource
System
Action:
The
CICSPlex
discovery
processing
continues.
106
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
GTMCP5001I
procedure:
inserting
event
into
StagedCPSM_DISC
Explanation:
The
procedure
is
inserting
CICSPlex
discovery
event
into
the
StagedCPSM_DISC
SQL
table.
Message
Variables:
procedure
-
The
name
of
the
procedure
being
processed
System
Action:
The
CICSPlex
discovery
event
is
inserted
into
StagedCPSM_DISC
SQL
table
to
process
the
CICSPlex
discovery
event.
GTMCP5002I
procedure:
obtaining
cid,
id
from
the
discovery
process
Explanation:
The
procedure
is
obtaining
the
class
ID
and
the
ID
of
the
CICSPlex
resource
being
discovered.
Message
Variables:
procedure
-
The
name
of
the
procedure
being
processed.
System
Action:
The
class
ID
and
the
ID
of
the
CICSPlex
resource
being
discovered
is
obtained.
GTMCP5003E
procedure:
error
finding
cid,
id
for
CPSM
resource
Explanation:
The
procedure
is
processing
the
CICSPlex
event
for
the
resource
that
is
not
part
the
the
CICSPlex
resource.
Message
Variables:
procedure
-
The
name
of
the
procedure
being
processed
System
Action:
The
processing
for
the
CICSPlex
event
stops.
Administrator
Response:
Verify
that
the
resource
exists
under
the
proper
CICSPlex.
If
the
CICSPlex
resource
has
not
been
discovered
yet,
use
the
CICSPlex
discovery
process
as
described
in
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide.
GTMCP5004W
procedure
could
not
find
cid,
id
for
CPSM
resource
Explanation:
The
procedure
is
processing
the
CICSPlex
event
for
the
resource
that
might
have
been
removed
from
the
CICSPlex
definition.
Message
Variables:
procedure
-
The
name
of
the
procedure
being
processed
System
Action:
The
event
being
processed
is
not
posted
to
any
Tivoli
Business
Systems
Manager
resource.
User
Response:
If
the
resource
for
which
the
event
is
being
processed
must
be
discovered
again,
use
the
CICSPlex
discovery
process
as
described
in
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide.
Administrator
Response:
Verify
that
the
resource,
which
the
CICSPlex
event
is
for,
exists
under
the
proper
CICSPlex.
If
the
CICSPlex
resource
has
not
been
discovered
yet,
discover
the
resource
using
the
CICSPlex
discovery
process.
GTMCP5005W
procedure:
found
cid=src_cid
id=src_id
Explanation:
The
procedure
is
processing
the
CICSPlex
event
for
the
specified
Tivoli
Business
Systems
Manager
resource.
Message
Variables:
procedure
-
The
name
of
the
procedure
being
processed
src_cid
-
The
Resource
Class
of
the
resource
for
which
the
event
is
being
processed
src_id
-
The
Resource
Class
ID
of
the
resource
for
which
the
event
is
being
processed
System
Action:
The
event
for
the
Tivoli
Business
Systems
Manager
resource
is
processed.
GTMCP5006I
procedure:
auto-creating
exception
type
name
description
Explanation:
The
procedure
is
automatically
creating
an
exception
type
for
the
event.
This
exception
is
being
created
because
it
is
not
defined
in
the
database.
Message
Variables:
procedure
-
The
name
of
the
procedure
being
processed
type
-
The
exception
type
name
-
The
name
of
exception
type
that
is
being
automatically
created
description
-
The
description
of
the
exception
System
Action:
An
exception
is
automatically
created
because
it
is
not
in
the
database.
GTMCP5007I
procedure
obtained
native_key
Explanation:
The
procedure
is
automatically
creating
an
exception
type
for
the
event.
This
exception
is
being
created
because
it
is
not
defined
in
the
database.
Message
Variables:
procedure
-
The
name
of
the
procedure
being
processed
native_key
-
The
key
of
Tivoli
Business
Systems
Manager
resource
System
Action:
The
key
is
obtained
to
place
the
event
on
the
proper
resource.
GTMCP5008I
procedure:
auto-creating
message
description
message_id
message_text
Explanation:
The
procedure
is
automatically
creating
a
message
for
the
event.
This
message
is
being
created
because
it
is
not
defined
in
the
database.
Message
Variables:
procedure
-
The
name
of
the
procedure
being
processed
Chapter
5.
CICSPlex
SM
Data
Source
Messages
-
GTMCP0001E
-
GTMCP5024I
107
message_id
-
The
name
of
the
message
that
is
being
created
message_text
-
The
description
of
the
message
System
Action:
A
message
is
created
because
it
is
not
defined
in
the
Tivoli
Business
Systems
Manager
database.
GTMCP5009W
procedure:
DiscoveryBatch
id
batch_id
is
not
valid
Explanation:
The
procedure
is
automatically
creating
a
message
for
the
event.
This
message
is
being
created
because
it
is
not
defined
in
the
database
Message
Variables:
procedure
-
The
name
of
the
procedure
being
processed
batch_id
-
The
batch
ID
of
the
discovery
file
System
Action:
Discovery
does
not
occur.
Administrator
Response:
Verify
if
a
valid
discovery
batch
ID
is
available.
From
the
SQL
Query
Analyzer,
issue
SELECT
*
FROM
DiscoveryBatch.
This
lists
all
discovery
files
that
have
been
processed,
that
have
failed,
and
that
must
be
processed.
Check
the
following
columns:
v
batchid
-
The
batch
ID
of
the
discovery
file
v
FormatType
-
The
format
type
of
the
discovery
file
(for
example,
18
=
IMS
discovery,
19
=
CICSPlex
discovery)
v
ActionType
-
The
action
type
of
the
discovery
file
(for
example,
1
=
discovery
data,
3
=
message
event)
v
FilePath
-
The
file
path
for
the
discovery
file
v
pstep
-
The
step
number
for
the
discovery
process
v
pstat
-
The
status
of
the
discovery
process
The
following
are
valid
pstat
values:
-4
-
discovery
file
ALLOCATE_ERROR
-2
-
PROCESS_ERROR
during
discovery
file
process
-1
-
LOAD_ERROR
during
discovery
file
load
0
-
discovery
file
ENQUEUED
1
-
Discovery
file
LOADED
2
-
discovery
file
process
INPROGRESS
3
-
discovery
process
COMPLETED
4
-
discovery
file
ALLOCATED
GTMCP5010E
procedure:
Error
loading
discovery
batch
file
file_path
Explanation:
An
error
occurred
while
loading
discovery
data.
Message
Variables:
procedure
-
The
name
of
the
procedure
being
processed.
file_path
-
The
file
path
of
the
discovery
file
System
Action:
Discovery
does
not
occur.
Administrator
Response:
Verify
that
discovery
data
passed
is
valid
and
rerun
the
load
process.
If
the
problem
persists,
contact
IBM
Software
Support.
GTMCP5011I
procedure:
message
name
number
date
time
Explanation:
The
error
occurred
while
loading
discovery
data.
Message
Variables:
procedure
-
The
name
of
the
procedure
being
processed
message
-
The
message
being
processed
name
-
The
name
of
the
resource
being
processed
number
-
The
sequence
number
of
the
message
event
date
time
-
The
date
and
time
stamp
of
when
the
event
was
processed
System
Action:
The
message
event
is
processed.
GTMCP5012E
procedure:
ERROR
-
cannot
determine
the
resource
src_cid
or
src_id
Explanation:
The
procedure
is
processing
an
event
for
a
resource
which
might
have
been
removed
from
CICSPlex
definition.
Message
Variables:
procedure
-
The
name
of
the
procedure
being
processed
src_cid
-
The
Resource
Class
of
the
resource
for
which
the
event
is
being
processed
src_id
-
The
Resource
Class
ID
of
the
resource
for
which
the
event
is
being
processed
System
Action:
The
event
being
processed
in
not
posted
to
any
Tivoli
Business
Systems
Manager
resource.
Administrator
Response:
If
the
resource
for
which
the
event
is
being
processed
must
be
discovered
again,
use
the
CICSPlex
discovery
process
as
described
in
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide.
GTMCP5013I
procedure:
creating
CICSPlex
monitor
message
on
the
target
src_cid
src_id
src_name
Explanation:
The
procedure
is
creating
a
CICSPlex
monitor
message
for
the
appropriate
resource.
Message
Variables:
procedure
-
The
name
of
the
procedure
being
processed
src_cid
-
The
Resource
Class
of
the
resource
for
which
the
event
is
being
processed
src_id
-
The
Resource
Class
ID
of
the
resource
for
which
the
event
is
being
processed
src_name
-
The
name
of
the
resource
being
processed
System
Action:
The
CICSPlex
monitor
message
is
108
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
created
for
the
appropriate
resource.
GTMCP5014I
procedure:
no
staged
events
to
process
Explanation:
The
procedure
attempted
to
process
staged
events,
but
there
was
nothing
to
process.
Message
Variables:
procedure
-
The
name
of
the
procedure
being
processed
System
Action:
No
events
are
processed.
GTMCP5015I
procedure:
max_rows
Explanation:
The
procedure
is
processing
the
CICSPlex
discovery
event
and
is
displaying
the
number
of
events
that
are
in
the
StagedCPSM_DISC
table.
Message
Variables:
procedure
-
The
name
of
the
procedure
being
processed
max_rows
-
The
number
of
events
in
the
StagedCPSM_DISC
table
System
Action:
The
event
is
processed
and
inserted
into
the
StagedCPSM_DISC
table.
GTMCP5016E
procedure:
ERROR
-
could
not
create
discovery
batch
id
Explanation:
The
procedure
is
processing
a
discovery
event
and
is
attempting
to
create
a
discovery
file.
The
INSERT
value
of
this
discovery
file
could
not
be
added
to
the
DiscoveryBatch
table.
The
Object
database
might
be
full.
Message
Variables:
procedure
-
The
name
of
the
procedure
being
processed
System
Action:
The
discovery
event
is
not
processed
because
it
could
not
be
inserted
into
the
DiscoveryBatch
table.
Administrator
Response:
Verify
that
the
Object
database
and
other
database
functions
are
processing
correctly.
If
the
problem
persists,
contact
IBM
Software
Support.
GTMCP5018I
procedure:
allocated
batch_id=batch_id
marked
as
ALLOCATED(4)
Explanation:
The
procedure
successfully
allocated
the
batch_id
for
a
discovery
event
and
has
marked
it
as
ALLOCATED.
Message
Variables:
procedure
-
The
name
of
the
procedure
being
processed
batch_id
-
The
batch
ID
allocated
for
event
discovery
System
Action:
The
batch_id
is
successfully
allocated
for
a
discovery
event.
GTMCP5019I
procedure:
event
batch
batch_id
-
appending
record
to
discovery
table
Explanation:
The
procedure
has
successfully
allocated
batch_id
for
a
discovery
event
and
has
appended
it
to
the
discovery
table.
Message
Variables:
procedure
-
The
name
of
the
procedure
being
processed
batch_id
-
The
batch
ID
allocated
for
event
discovery
System
Action:
The
discovery
event
is
appended
into
discovery
table
CPSMDiscovery.
GTMCP5020I
procedure:
successfully
appended
event
batch
batch_id
in
the
discovery
table
Explanation:
The
procedure
has
successfully
appended
indicated
discovery
records
for
batch_id
in
the
discovery
table.
Message
Variables:
procedure
-
The
name
of
the
procedure
being
processed
number
-
The
number
of
discovery
events
batch_id
-
The
batch
ID
allocated
for
event
discovery
System
Action:
The
indicated
discovery
events
are
processed.
GTMCP5021I
procedure:
marking
batch_id=batch_id
as
LOADED(1)
Explanation:
The
procedure
has
successfully
loaded
discovery
events
and
is
now
marking
the
batch
ID
as
LOADED.
Message
Variables:
procedure
-
The
name
of
the
procedure
being
processed
batch_id
-
The
batch
ID
allocated
for
event
discovery
System
Action:
The
discovery
events
are
loaded
into
the
database.
GTMCP5022I
procedure:
calling
the
discovery
process
procedure
_DiscoverCPSMResources
on
the
partial
batch
Explanation:
The
procedure
is
calling
the
_DiscoverCPSMResources
routine
to
process
discovery
events
that
have
been
recently
loaded.
See
message
GTMCP5021I.
Message
Variables:
procedure
-
The
name
of
the
procedure
being
processed
System
Action:
The
discovery
events
are
processed.
Chapter
5.
CICSPlex
SM
Data
Source
Messages
-
GTMCP0001E
-
GTMCP5024I
109
GTMCP5023E
procedure
ERROR:
_DiscoverCPSMResources
failed
to
process
partial
batch
batch_id
with
error
return_code.
Continuing...
Explanation:
The
procedure
has
called
_DiscoverCPSMResources
routine
to
discover
CICSPlex
resource.
However,
routine
_DiscoverCPSMResources
encountered
an
error
and
the
discovery
process
continues.
Message
Variables:
procedure
-
The
name
of
the
procedure
being
processed
batch_id
-
The
batch
ID
allocated
for
event
discovery
return_code
-
The
return
code
received
from
the
_DiscoverCPSMResources
routine
System
Action:
The
Discovery
events
in
StagedCPSM_DISC
table
have
been
processed
successfully
and
are
now
being
removed
from
the
table.
GTMCP5024I
procedure:
deleted=number
records
from
StagedCPSM_DISC
Explanation:
The
all
discovery
events
in
table
StagedCPSM_DISC
have
been
processed
successfully
and
are
now
being
removed
from
the
table.
Message
Variables:
procedure
-
The
name
of
the
procedure
being
processed
number
-
The
number
of
events
being
processed
System
Action:
The
_DiscoverCPSMResources
calls
nine
other
routines
to
discovery
CICSPlex
resources
and
one
of
them
encountered
an
error.
They
are
as
follows:
v
_DiscoverCPSMResourcesCMAS
-
Discovers
CMAS
regions
v
_DiscoverCPSMResourcesCICS
-
Discovers
CICS
regions
v
_DiscoverCPSMResourcesFILE
-
Discovers
CICS
files
v
_DiscoverCPSMResourcesTRAN
-
Discovers
CICS
transactions
v
_DiscoverCPSMResourcesCICB
-
Discovers
CICS
Corba
Servers
v
_DiscoverCPSMResourcesCICO
-
Discovers
CICS
to
CICS
connections
v
_DiscoverCPSMResourcesCID2
-
Discovers
CICS
to
DB2
connections
v
_DiscoverCPSMResourcesCIJF
-
Discovers
CICS
JAR
files
v
_DiscoverCPSMResourcesCISG
-
Discovers
CICSPlex
system
groups
Administrator
Response:
Verify
that
the
data
in
the
discovery
event
is
properly
formatted
and
send
the
discovery
event
again.
If
the
problem
persists,
contact
IBM
Software
Support.
110
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
Chapter
6.
Command
Line
Interface
Messages
-
GTMCI0001I
-
GTMCI0145E,
GTMDC0010E
and
GTMDC0011E
The
following
messages
are
command
line
interface
messages
and
command
line
interface
database
configuration
messages.
GTMCI0001I
Command
processing
started:
command
Explanation:
A
command
has
been
received
and
processing
has
begun.
Administrator
Response:
None.
GTMCI0002I
Command
processing
completed.
Explanation:
A
received
command
has
been
processed.
Administrator
Response:
The
information
in
any
accompanying
messages
contains
information
regarding
the
success
of
failure
of
the
received
command.
GTMCI0005E
Exception
data:
messages
Explanation:
An
exception
generated
additional
messages.
Administrator
Response:
The
diagnostic
information
in
the
messages
contains
information
that
could
be
useful
in
correcting
any
reported
problems.
After
verifying
and
correcting
any
of
the
reported
problems,
retry
the
command.
If
problems
persist,
contact
IBM
Software
Support.
GTMCI0006E
Required
database
access
option(s)
not
provided:
options
Explanation:
A
database
operation
failed
to
complete
successfully
due
to
insufficient
database
access
information.
Administrator
Response:
Verify
the
IBM
Tivoli
Business
Systems
Manager
database
host
name,
user
name,
and
password
are
properly
configured
or
passed
as
options
on
the
command.
GTMCI0010E
Error
processing
command:
messages
Explanation:
An
error
generated
additional
messages.
Administrator
Response:
The
diagnostic
information
in
the
messages
contains
information
that
could
be
useful
in
correcting
any
reported
problems.
After
verifying
and
correcting
any
of
the
reported
problems,
retry
the
command.
If
problems
persist,
contact
IBM
Software
Support.
GTMCI0011E
Unrecognized
command
action:
action
Explanation:
A
command
was
received
with
an
invalid
syntax.
Administrator
Response:
Verify
the
command
usage,
correct
the
command
syntax,
and
retry
the
command.
GTMCI0012E
Unrecognized
command
option:
option
Explanation:
A
command
was
received
with
an
invalid
syntax.
Administrator
Response:
Verify
the
command
usage,
correct
the
command
syntax,
and
retry
the
command.
GTMCI0013E
Unrecognized
command
option:
option,
for
specified
command
action:
action
Explanation:
A
command
was
received
with
an
invalid
syntax.
Administrator
Response:
Verify
the
command
usage,
correct
the
command
syntax,
and
retry
the
command.
GTMCI0014E
Required
command
action
not
specified.
Explanation:
A
command
was
received
with
an
invalid
syntax.
Administrator
Response:
Verify
the
command
usage,
correct
the
command
syntax,
and
retry
the
command.
GTMCI0015E
Required
command
option
not
specified:
option
Explanation:
A
command
was
received
with
an
invalid
syntax.
Administrator
Response:
Verify
the
command
usage,
correct
the
command
syntax,
and
retry
the
command.
GTMCI0030E
Error
accessing
properties
file:
propertiesFile
Explanation:
The
required
properties
file
could
not
be
loaded.
Administrator
Response:
Verify
the
required
properties
file
was
included
in
the
IBM
Tivoli
Business
Systems
Manager
installation.
©
Copyright
IBM
Corp.
2000,
2004
111
Verify
the
required
properties
file
is
located
in
the
bin
directory
of
the
IBM
Tivoli
Business
Systems
Manager
installation.
If
the
required
properties
file
cannot
be
located,
contact
IBM
Software
Support.
GTMCI0032E
Required
property
value
not
specified:
value,
in
properties
file:
propertiesFile
Explanation:
A
required
property
key
and
value
was
not
specified
in
a
properties
file.
Administrator
Response:
Configure
the
properties
file
with
the
required
property
key
and
value.
GTMCI0040E
Undefined
Resource
Type:
classID
Explanation:
A
command
was
received
with
an
undefined
or
invalid
resource
type.
Administrator
Response:
Correct
the
invalid
resource
type
and
retry
the
command.
GTMCI0100I
The
specified
Resource
Type
to
Placement
Rule
association
has
been
successfully
defined.
Resource
Type:
classID,
Placement
Rule:
rule,
Priority:
priority
Explanation:
The
IBM
Tivoli
Business
Systems
Manager
database
has
been
updated
with
the
specified
Resource
Type
to
Placement
Rule
association.
Administrator
Response:
None.
GTMCI0101E
The
specified
Resource
Type
to
Placement
Rule
association
was
not
defined.
Resource
Type:
classID,
Placement
Rule:
rule
Explanation:
The
IBM
Tivoli
Business
Systems
Manager
database
has
not
been
updated
with
the
specified
Resource
Type
to
Placement
Rule
association.
Administrator
Response:
Any
accompanying
messages
contain
information
regarding
the
failure
of
the
received
command.
GTMCI0101W
The
specified
Resource
Type
to
Placement
Rule
association
was
not
defined.
Resource
Type:
classID,
Placement
Rule:
rule
Explanation:
The
IBM
Tivoli
Business
Systems
Manager
database
has
not
been
updated
with
the
specified
Resource
Type
to
Placement
Rule
association.
Other
command
operations,
such
as
the
defining
of
a
Placement
Rule,
may
complete
successfully.
Administrator
Response:
Any
accompanying
messages
contain
information
regarding
the
failure
of
the
definition
of
the
specified
Resource
Type
to
Placement
Rule
association.
GTMCI0102E
Unrecognized
command
option:
option,
within
Placement
Rule
generation
information.
Explanation:
A
command
was
received
with
an
invalid
syntax.
Administrator
Response:
Verify
the
command
usage,
correct
the
command
syntax,
and
retry
the
command.
GTMCI0103E
Required
command
option
not
specified:
option,
within
Placement
Rule
generation
information.
Explanation:
A
command
was
received
with
an
invalid
syntax.
Administrator
Response:
Verify
the
command
usage,
correct
the
command
syntax,
and
retry
the
command.
GTMCI0104E
A
minimum
of
1
and
a
maximum
of
10
Placement
Rule
generations
can
be
specified.
Explanation:
A
command
was
received
with
an
invalid
syntax.
Administrator
Response:
Verify
the
command
usage,
correct
the
command
syntax,
and
retry
the
command.
GTMCI0105E
Placement
Rule
generation
information
must
specify
either
the
-n
displayname
or
-a
attribute
option.
Generation:
generation
Explanation:
A
command
was
received
with
an
invalid
syntax.
Administrator
Response:
Verify
the
command
usage,
correct
the
command
syntax,
and
retry
the
command.
GTMCI0106E
Placement
Rule
generation
information
cannot
specify
both
-n
displayname
and
-a
attribute
options.
Generation:
generation,
Display
name:
displayName,
Attribute:
attribute
Explanation:
A
command
was
received
with
an
invalid
syntax.
Administrator
Response:
Verify
the
command
usage,
correct
the
command
syntax,
and
retry
the
command.
112
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
GTMCI0107E
Placement
Rule
generation
information
cannot
specify
both
-n
displayname
and
-f
function
options.
Generation:
generation,
Display
name:
displayName,
Function:
function
Explanation:
A
command
was
received
with
an
invalid
syntax.
Administrator
Response:
Verify
the
command
usage,
correct
the
command
syntax,
and
retry
the
command.
GTMCI0108I
The
specified
Placement
Rule
has
been
successfully
defined:
rule
Explanation:
The
IBM
Tivoli
Business
Systems
Manager
database
has
been
updated
with
the
specified
Placement
Rule.
Administrator
Response:
None.
GTMCI0109E
The
specified
Placement
Rule
was
not
defined:
rule
Explanation:
The
IBM
Tivoli
Business
Systems
Manager
database
has
not
been
updated
with
the
specified
Placement
Rule.
Administrator
Response:
Any
accompanying
messages
contain
information
regarding
the
failure
of
the
received
command.
GTMCI0110E
The
specified
Placement
Rule
name
is
already
defined:
rule
Explanation:
The
specified
Placement
Rule
name
is
already
defined.
The
IBM
Tivoli
Business
Systems
Manager
database
has
not
been
updated
with
the
specified
Placement
Rule.
Administrator
Response:
Specify
a
new
Placement
Rule
name
and
retry
the
command.
GTMCI0111E
The
-p
priority
option
must
be
within
the
valid
range
of
1
to
255.
Explanation:
A
command
was
received
with
an
invalid
syntax.
Administrator
Response:
Verify
the
command
usage,
correct
the
command
syntax,
and
retry
the
command.
GTMCI0112I
All
Resource
Type
to
Placement
Rule
associations
have
been
deleted
for
specified
Resource
Type:
classID
Explanation:
The
specified
Resource
Type
to
Placement
Rule
associations
have
been
deleted
from
the
IBM
Tivoli
Business
Systems
Manager
database.
Administrator
Response:
None.
GTMCI0113I
A
Resource
Type
to
Placement
Rule
association
has
been
deleted
for
specified
Resource
Type:
classID,
and
Placement
Rule:
rule
Explanation:
The
specified
Resource
Type
to
Placement
Rule
association
has
been
deleted
from
the
IBM
Tivoli
Business
Systems
Manager
database.
Administrator
Response:
None.
GTMCI0114E
The
specified
Resource
Type
to
Placement
Rule
association
was
not
deleted.
Resource
Type:
classID,
Placement
Rule:
rule
Explanation:
The
specified
Resource
Type
to
Placement
Rule
association
has
not
been
deleted
from
the
IBM
Tivoli
Business
Systems
Manager
database.
Administrator
Response:
Any
accompanying
messages
contain
information
regarding
the
failure
of
the
received
command.
GTMCI0115E
No
Resource
Type
to
Placement
Rule
association
is
currently
defined
for
specified
Resource
Type:
classID,
and
Placement
Rule:
rule
Explanation:
The
specified
Resource
Type
to
Placement
Rule
association
is
not
defined.
The
specified
Resource
Type
to
Placement
Rule
association
has
not
been
deleted
from
the
IBM
Tivoli
Business
Systems
Manager
database.
Administrator
Response:
Specify
a
defined
Resource
Type
to
Placement
Rule
association
and
retry
the
command.
GTMCI0116E
No
Resource
Type
to
Placement
Rule
associations
are
currently
defined
for
specified
Resource
Type:
classID
Explanation:
The
specified
Resource
Type
has
no
Resource
Type
to
Placement
Rule
associations
defined.
The
specified
Resource
Type
to
Placement
Rule
associations
have
not
been
deleted
from
the
IBM
Tivoli
Business
Systems
Manager
database.
Administrator
Response:
Specify
a
defined
Resource
Type
to
Placement
Rule
association
and
retry
the
command.
GTMCI0117I
The
specified
Placement
Rule
has
been
deleted:
rule
Explanation:
The
specified
Placement
Rule
association
has
been
deleted
from
the
IBM
Tivoli
Business
Systems
Manager
database.
Administrator
Response:
None.
Chapter
6.
Command
Line
Interface
Messages
-
GTMCI0001I
-
GTMCI0145E,
GTMDC0010E
and
GTMDC0011E
113
GTMCI0118E
The
specified
Placement
Rule
was
not
deleted:
rule
Explanation:
The
specified
Placement
Rule
association
has
not
been
deleted
from
the
IBM
Tivoli
Business
Systems
Manager
database.
Administrator
Response:
Any
accompanying
messages
contain
information
regarding
the
failure
of
the
received
command.
GTMCI0119E
Display
command
action
cannot
specify
both
-r
rulename
and
-A
options.
Explanation:
A
command
was
received
with
an
invalid
syntax.
Administrator
Response:
Verify
the
command
usage,
correct
the
command
syntax,
and
retry
the
command.
GTMCI0120E
Display
command
action
cannot
specify
both
-c
classname
and
-A
options.
Explanation:
A
command
was
received
with
an
invalid
syntax.
Administrator
Response:
Verify
the
command
usage,
correct
the
command
syntax,
and
retry
the
command.
GTMCI0121E
Display
command
action
cannot
specify
both
-c
classname
and
-r
rulename
options.
Explanation:
A
command
was
received
with
an
invalid
syntax.
Administrator
Response:
Verify
the
command
usage,
correct
the
command
syntax,
and
retry
the
command.
GTMCI0122E
Display
command
action
must
specify
the
-c
classname,
-r
rulename,
or
-A
option.
Explanation:
A
command
was
received
with
an
invalid
syntax.
Administrator
Response:
Verify
the
command
usage,
correct
the
command
syntax,
and
retry
the
command.
GTMCI0123I
Defined
Resource
Type
to
Placement
Rule
association(s):
results
Explanation:
One
or
more
Resource
Type
to
Placement
Rule
associations
that
are
defined
in
the
IBM
Tivoli
Business
Systems
Manager
database
are
displayed.
Administrator
Response:
None.
GTMCI0124I
No
Resource
Type
to
Placement
Rule
associations
are
currently
defined.
Explanation:
No
Resource
Type
to
Placement
Rule
associations
are
defined
in
the
IBM
Tivoli
Business
Systems
Manager
database.
Administrator
Response:
None.
GTMCI0125I
Defined
Placement
Rule(s):
rules
Explanation:
One
or
more
Placement
Rules
that
are
defined
in
the
IBM
Tivoli
Business
Systems
Manager
database
are
displayed.
Administrator
Response:
None.
GTMCI0126I
No
Placement
Rules
are
currently
defined.
Explanation:
No
Placement
Rules
are
defined
in
the
IBM
Tivoli
Business
Systems
Manager
database.
Administrator
Response:
None.
GTMCI0127E
Unsupported
resource
relationship.
The
specified
parent
Resource
Type:
parentClassID,
cannot
be
linked
to
child
Resource
Type:
childClassID
Explanation:
The
IBM
Tivoli
Business
Systems
Manager
database
does
not
support
a
physical
containment
(PHYC)
or
grouping
(GEPC)
link
between
the
parent
Resource
Type
and
the
child
Resource
Type.
The
command
is
failed.
Administrator
Response:
Select
a
parent
Resource
Type
and
a
child
Resource
Type
that
can
be
linked
with
a
parent
Resource
Type
and
the
child
Resource
Type,
and
retry
the
command.
GTMCI0127W
Unsupported
resource
relationship.
The
specified
parent
Resource
Type:
parentClassID,
cannot
be
linked
to
child
Resource
Type:
childClassID
Explanation:
The
IBM
Tivoli
Business
Systems
Manager
database
does
not
support
a
physical
containment
(PHYC)
or
grouping
(GEPC)
link
between
the
parent
Resource
Type
and
the
child
Resource
Type.
The
IBM
Tivoli
Business
Systems
Manager
database
has
not
been
updated
with
the
specified
Resource
Type
to
Placement
Rule
association.
Other
command
operations,
such
as
the
defining
of
a
Placement
Rule,
may
complete
successfully.
Administrator
Response:
If
the
Placement
Rule
was
added
to
the
IBM
Tivoli
Business
Systems
Manager
database,
verify
the
parent
Resource
Types
have
been
defined
as
expected
using
the
"
command.
If
the
parent
Resource
Types
have
been
incorrectly
114
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
specified,
delete
the
Placement
Rule
and
redefine
it
with
correct
parent
Resource
Types.
GTMCI0128E
The
-s
state
option
must
be
set
to
either
’enabled’
or
’disabled’.
Explanation:
A
command
was
received
with
an
invalid
syntax.
Administrator
Response:
Verify
the
command
usage,
correct
the
command
syntax,
and
retry
the
command.
GTMCI0129I
The
specified
Placement
Rule
has
been
state.
Explanation:
The
specified
Placement
Rule
has
been
updated
to
the
specified
state
in
the
IBM
Tivoli
Business
Systems
Manager
database.
Administrator
Response:
None.
GTMCI0130E
The
specified
Placement
Rule
was
not
state.
Explanation:
The
specified
Placement
Rule
has
not
been
updated
to
the
specified
state
in
the
IBM
Tivoli
Business
Systems
Manager
database.
Administrator
Response:
Any
accompanying
messages
contain
information
regarding
the
failure
of
the
received
command.
GTMCI0131E
Undefined
Placement
Rule:
rule
Explanation:
A
command
was
received
with
an
undefined
or
invalid
Placement
Rule.
Administrator
Response:
Correct
the
invalid
Placement
Rule
and
retry
the
command.
GTMCI0132E
A
Resource
Type
to
Placement
Rule
association
already
exists
for
specified
Resource
Type:
classID,
with
priority:
priority
Explanation:
The
specified
Resource
Type
to
Placement
Rule
association
is
already
defined.
The
IBM
Tivoli
Business
Systems
Manager
database
has
not
been
updated
with
the
specified
Resource
Type
to
Placement
Rule
association.
Administrator
Response:
Specify
a
new
Resource
Type
to
Placement
Rule
association
and
retry
the
command.
GTMCI0133E
A
Resource
Type
to
Placement
Rule
association
already
exists
for
specified
Resource
Type:
classID,
and
Placement
Rule:
rule
Explanation:
The
specified
Resource
Type
to
Placement
Rule
association
is
already
defined.
The
IBM
Tivoli
Business
Systems
Manager
database
has
not
been
updated
with
the
specified
Resource
Type
to
Placement
Rule
association.
Administrator
Response:
Specify
a
new
Resource
Type
to
Placement
Rule
association
and
retry
the
command.
GTMCI0134E
A
Resource
Type
to
Placement
Rule
association
does
not
exist
for
specified
Resource
Type:
classID,
and
Placement
Rule:
rule
Explanation:
The
specified
Resource
Type
to
Placement
Rule
association
is
not
defined.
Administrator
Response:
Specify
a
new
Resource
Type
to
Placement
Rule
association
and
retry
the
command.
GTMCI0135E
A
default
priority
could
not
be
applied
to
the
specified
Resource
Type
to
Placement
Rule
association.
Resource
Type:
classID,
Placement
Rule:
rule
Explanation:
The
-p
priority
option
was
not
specified
and
an
attempt
was
made
to
default
the
priority
of
the
Resource
Type
to
Placement
Rule
association.
Other
associations
exist
and
the
priority
could
not
be
defaulted
to
the
lowest
priority
for
the
Resource
Type
(highest
numerical
priority
+
1)
due
to
an
existing
association
with
the
lowest
available
priority
of
255.
The
IBM
Tivoli
Business
Systems
Manager
database
has
not
been
updated
with
the
specified
Resource
Type
to
Placement
Rule
association.
The
command
is
failed.
Administrator
Response:
Define
the
Resource
Type
to
Placement
Rule
association
with
a
specified
priority.
GTMCI0135W
A
default
priority
could
not
be
applied
to
the
specified
Resource
Type
to
Placement
Rule
association.
Resource
Type:
classID,
Placement
Rule:
rule
Explanation:
The
-p
priority
option
was
not
specified
and
an
attempt
was
made
to
default
the
priority
of
the
Resource
Type
to
Placement
Rule
association.
Other
associations
exist
and
the
priority
could
not
be
defaulted
to
the
lowest
priority
for
the
Resource
Type
(highest
numerical
priority
+
1)
due
to
an
existing
association
with
the
lowest
available
priority
of
255.
The
IBM
Tivoli
Business
Systems
Manager
database
has
not
been
updated
with
the
specified
Resource
Type
to
Placement
Rule
association.
Other
command
operations,
such
as
the
defining
of
a
Placement
Rule,
may
complete
successfully.
Administrator
Response:
If
the
Placement
Rule
was
Chapter
6.
Command
Line
Interface
Messages
-
GTMCI0001I
-
GTMCI0145E,
GTMDC0010E
and
GTMDC0011E
115
added
to
the
IBM
Tivoli
Business
Systems
Manager
database
and
the
specified
Resource
Type
to
Placement
Rule
association
is
required,
define
the
association
with
a
specified
priority
using
the
"
command.
GTMCI0136I
A
default
priority
has
been
applied
to
the
specified
Resource
Type
to
Placement
Rule
association.
Resource
Type:
classID,
Placement
Rule:
rule,
Priority:
priority
Explanation:
The
-p
priority
option
was
not
specified
and
the
priority
of
the
Resource
Type
to
Placement
Rule
association
was
defaulted.
The
Resource
Type
to
Placement
Rule
association
was
defaulted
to
1
if
no
other
associations
existed
for
the
Resource
Type.
If
other
associations
exist,
the
priority
will
be
defaulted
to
the
lowest
priority
for
the
Resource
Type
(highest
numerical
priority
+1).
Administrator
Response:
None.
GTMCI0137I
The
-p
priority
option
has
been
ignored
because
no
Resource
Type
has
been
specified.
Explanation:
The
-p
priority
option
has
specified
on
a
"
command
and
no
-c
classname
option
has
been
specified.
The
-p
priority
option
is
ignored
since
there
is
no
applicable
Resource
Type
to
Placement
Rule
association.
Administrator
Response:
None.
GTMCI0138I
The
specified
Resource
Type
to
Placement
Rule
association
has
been
successfully
modified.
Resource
Type:
classID,
Placement
Rule:
rule,
Priority:
priority
Explanation:
The
IBM
Tivoli
Business
Systems
Manager
database
has
been
updated
with
the
specified
Resource
Type
to
Placement
Rule
association
modification.
Administrator
Response:
None.
GTMCI0139E
The
specified
Resource
Type
to
Placement
Rule
association
was
not
modified.
Resource
Type:
classID,
Placement
Rule:
rule,
Priority:
priority
Explanation:
The
IBM
Tivoli
Business
Systems
Manager
database
has
not
been
updated
with
the
specified
Resource
Type
to
Placement
Rule
association
modification.
Administrator
Response:
Any
accompanying
messages
contain
information
regarding
the
failure
of
the
received
command.
GTMCI0140E
Unsupported
command
input:
input,
for
specified
command
action:
action
Explanation:
A
command
was
received
with
an
invalid
syntax.
Administrator
Response:
Verify
the
command
usage,
correct
the
command
syntax,
and
retry
the
command.
GTMCI0141I
Resource
Type
to
Placement
Rule
associations
have
been
successfully
defined
for
number
of
totalNumber
existing
classes.
Explanation:
The
"
class
name
option
was
specified
and
Resource
Type
to
Placement
Rule
associations
have
been
defined
for
the
reported
number
of
existing
distributed
resource
classes.
Administrator
Response:
None.
GTMCI0142E
The
specified
-a
attribute
is
not
valid
for
distributed
resource
classes:
attribute
Explanation:
The
specified
-a
attribute
does
not
contain
one
of
the
following
well
known
distributed
resource
class
attributes:
Data1,
Data2,
Data3,
Data4,
Desc,
EEhost,
EPTTMR,
InstanceID,
Manufacturer,
MgedSystemName,
name,
Product,
TCPHost,
Version
The
IBM
Tivoli
Business
Systems
Manager
database
has
not
been
updated
with
the
specified
Placement
Rule.
Administrator
Response:
Correct
the
invalid
attribute
and
retry
the
command.
GTMCI0143E
The
specified
-f
function
is
not
applied
to
the
specified
distributed
resource
class
-a
attribute.
Function:
function,
Attribute:
attribute
Explanation:
The
SQL
string
function
specified
does
not
reference
the
specified
distributed
resource
class
attribute.
The
attribute
must
appear
as
part
of
the
specified
function.
For
example,
if
"
is
specified,
Data1
must
appear
in
a
function
such
as
".
The
IBM
Tivoli
Business
Systems
Manager
database
has
not
been
updated
with
the
specified
Placement
Rule.
Administrator
Response:
Correct
the
invalid
attribute
or
function
and
retry
the
command.
116
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
GTMCI0144W
The
specified
-f
function
does
not
specify
a
recognized
SQL
string
function:
function
Explanation:
A
warning
is
issued
if
the
specified
-f
function
does
not
contain
one
of
the
following
well
known
SQL
string
functions:
CHARINDEX,
LEFT,
LEN,
LOWER,
LTRIM,
PATINDEX,
REPLACE,
QUOTENAME,
REPLICATE,
REVERSE,
RIGHT,
RTRIM,
SPACE,
STUFF,
SUBSTRING,
UPPER.
The
IBM
Tivoli
Business
Systems
Manager
database
has
been
updated
with
the
specified
Placement
Rule.
Administrator
Response:
If
the
Placement
Rule
was
added
to
the
IBM
Tivoli
Business
Systems
Manager
database,
verify
the
Placement
Rule
has
been
defined
with
the
expected
function
using
the
"
command.
If
the
function
was
incorrectly
specified,
delete
the
Placement
Rule
and
redefine
it
with
a
correct
function.
GTMCI0145E
The
specified
-n
displayname
contains
an
invalid
character
or
expression.
Display
name:
displayName,
Character
or
expression:
expression
Explanation:
The
resource
name
specified
contains
an
invalid,
malformed,
or
unsupported
character
or
expression.
The
IBM
Tivoli
Business
Systems
Manager
database
has
not
been
updated
with
the
specified
Placement
Rule.
Administrator
Response:
Correct
the
invalid
resource
name
and
retry
the
command.
GTMDC0010E
Error
accessing
the
TBSM
database.
Explanation:
A
database
operation
failed
to
complete
successfully.
Administrator
Response:
Retry
the
operation.
If
the
problem
occurs
consistently
for
all
database
operations,
verify:
1.
The
IBM
Tivoli
Business
Systems
Manager
database
server
and
process
are
functioning
properly.
2.
The
network
connection
between
the
local
host
and
the
IBM
Tivoli
Business
Systems
Manager
database
is
functioning
properly.
3.
The
IBM
Tivoli
Business
Systems
Manager
database
host
name,
user
name,
and
password
are
properly
configured
or
passed
as
options
on
commands.
4.
The
JDBC
driver
is
installed
and
configured
properly
in
the
tbsmcmds.properties
file.
After
verifying
and
correcting
any
of
the
preceding
items,
retry
the
operation.
If
problems
persist,
contact
IBM
Software
Support.
GTMDC0011E
Return
code
rc
and
following
database
messages(s)
were
received:
messages
Explanation:
A
database
operation
generated
a
return
code
and/or
additional
messages.
Administrator
Response:
The
diagnostic
information
in
any
messages
contains
information
reported
by
the
JDBC
driver
or
the
IBM
Tivoli
Business
Systems
Manager
database
that
could
be
useful
in
correcting
any
reported
problems.
After
verifying
and
correcting
any
of
the
reported
problems,
retry
the
operation.
If
problems
persist,
contact
IBM
Software
Support.
Chapter
6.
Command
Line
Interface
Messages
-
GTMCI0001I
-
GTMCI0145E,
GTMDC0010E
and
GTMDC0011E
117
Chapter
7.
Common
Listener
Messages
-
GTMCL5200I
-
GTMCL6000E
The
following
messages
are
issued
by
the
Tivoli
Business
Systems
Manager
common
listener
service.
GTMCL5200I
The
request
for
transaction
name
has
been
queued
to
Tivoli
Business
Systems
Manager.
Explanation:
The
XML
file
was
successfully
read
and
was
put
on
the
queue
for
processing.
This
is
an
asynchronous
process,
the
common
listener
reports
any
errors
in
its
message
log
located
in
the
install_dir/XMLtoolkit/logs
directory.
Message
Variables:
name
-
The
name
of
the
XML
file
System
Action:
The
request
was
put
on
the
MQe
queue
for
the
common
listener.
GTMCL5201E
The
XML
file
is
incorrect.
An
error
was
found
with
tag:
tag
Explanation:
While
reading
the
XML
file,
a
statement
was
found
that
is
not
valid.
Message
Variables:
tag
-
The
line
in
the
file
where
the
error
was
found
System
Action:
No
further
processing
was
done
on
the
file
and
it
was
not
sent
to
the
common
listener.
User
Response:
Fix
the
error
and
run
the
command
again.
GTMCL5202E
The
syntax
of
the
command
is
incorrect,
the
value
value
was
not
expected.
Explanation:
While
parsing
the
command
line
arguments,
an
argument
was
found
that
is
not
valid.
Message
Variables:
value
-
The
argument
in
error
System
Action:
No
further
processing
was
performed
when
the
error
was
found.
User
Response:
Correct
the
command
line
input
and
run
the
command
again.
GTMCL5203E
GTMCL5203E:
A
transport
exception
occurred.
Explanation:
The
command
was
unable
to
communicate
with
the
common
listener
server
on
the
Tivoli
Business
Systems
Manager
server.
Verify
the
server
hostname
and
port
in
the
properties
file
or
the
values
specified
on
the
command
line.
Administrator
Response:
GTMCL5204E
The
request
failed
with
return
code
rc.
Explanation:
This
message
is
displayed
when
the
command
failed.
The
return
code
indicates
the
reason.
See
the
enqueuecl
command
description
in
the
IBM
Tivoli
Business
Systems
Manager
Command
Reference
for
a
list
of
the
return
codes.
Message
Variables:
rc
-
The
return
code
System
Action:
No
further
processing
was
performed
when
the
error
was
found.
User
Response:
Review
the
command
processor
log
located
in
the
install_dir/XMLtoolkit/logs
directory
for
the
reason
for
the
error.
GTMCL5205E
Exception
caught.
exception_message.
Explanation:
The
Java™
virtual
machine
returned
an
exception.
Message
Variables:
exception_message
-
The
substituted
message
from
the
exception
System
Action:
No
further
processing
was
performed
when
the
error
was
found.
User
Response:
Review
the
command
processor
log
located
in
the
install_dir/XMLtoolkit/logs
directory
for
the
reason
for
the
error.
GTMCL5206E
Unable
to
load
resource
file
CLToolsResources.
Explanation:
The
command
loads
the
CLToolsResources
message
file
before
processing
the
XML
file.
If
the
message
file
cannot
be
loaded,
processing
stops.
System
Action:
No
further
processing
was
performed
when
the
error
was
found.
User
Response:
Contact
IBM
Software
Support.
GTMCL5207E
Unable
to
load
string
string
from
resource
file
CLToolsResources.
Explanation:
The
command
was
attempting
to
write
a
message,
but
the
string
could
not
be
found
in
the
CLToolsResources
message
file.
©
Copyright
IBM
Corp.
2000,
2004
119
Message
Variables:
string
-
The
substituted
message
identifier
System
Action:
Processing
continues.
User
Response:
Contact
IBM
Software
Support.
GTMCL5208E
A
syntax
error
was
found.
A
value
was
not
supplied
for
flag
Explanation:
An
error
was
found
in
the
command
line
arguments.
The
flag
argument
should
have
been
followed
by
a
value,
but
the
value
was
missing.
Message
Variables:
flag
-
The
name
of
the
argument
System
Action:
No
further
processing
was
performed
when
the
error
was
found.
User
Response:
Fix
the
command
line
input
and
run
the
command
again.
GTMCL5209I
Initalizing
transport
adapter.
Explanation:
This
is
an
informational
message
displayed
when
verbose
(-w)
output
is
requested.
At
this
point,
the
command
is
initializing
the
transport.
GTMCL5210I
Transport
adapter
initialization
complete.
Explanation:
This
is
an
informational
message
displayed
when
verbose
(-w)
output
is
requested.
At
this
point,
the
command
initialized
the
transport.
GTMCL5211I
Registering
with
Tivoli
Business
Systems
Manager.
Explanation:
This
is
an
informational
message
displayed
when
verbose
(-w)
output
is
requested.
At
this
point,
the
command
initialized
the
transport.
GTMCL5212I
Registration
complete,
sessionId:
sess_id
Explanation:
This
is
an
informational
message
displayed
when
verbose
(-w)
output
is
requested.
At
this
point,
the
command
successfully
registered
with
Tivoli
Business
Systems
Manager
and
the
session
identifier
is
displayed.
Message
Variables:
sess_id
-
The
session
identifier
GTMCL5213E
Request
failed
with
an
adapter
exception.
exception.
Explanation:
While
sending
data
to
Tivoli
Business
Systems
Manager,
a
transport
exception
was
received.
Message
Variables:
exception
-
The
substituted
exception
System
Action:
No
further
processing
was
performed
when
the
error
was
found.
User
Response:
Review
the
command
processor
log
located
in
the
install_dir/XMLtoolkit/logs
directory
before
running
the
command
again.
GTMCL5214E
Registration
failed
with
an
exception.
exception.
Explanation:
While
registering
with
Tivoli
Business
Systems
Manager,
an
exception
occurred.
Message
Variables:
exception
-
The
substituted
exception
System
Action:
No
further
processing
was
performed
when
the
error
was
found.
User
Response:
Review
the
command
processor
log
located
in
the
install_dir/XMLtoolkit/logs
directory
before
running
the
command
again.
Ensure
that
the
local
host
name
and
the
common
listener
host
names
are
specified
correctly
in
the
properties
file.
Also
ensure
that
the
clocks
on
the
system
from
which
the
command
is
being
issued
and
the
system
running
the
common
listener
service
are
synchronized.
GTMCL5215I
Begin
Discovery
sess_ID:
request_type
Explanation:
This
is
an
informational
message
that
is
displayed
when
the
verbose
(-w)
flag
is
specified.
The
first
data
segment
is
sent
to
Tivoli
Business
Systems
Manager.
The
session
identifier
is
substituted
for
sess_ID
and
the
type
of
request,
as
specified
by
the
-t
flag,
is
substituted
for
request_type.
Message
Variables:
sess_ID
-
The
substituted
session
identifier
request_type
-
The
substituted
request
type
GTMCL5216I
data_type:
sess_ID
Explanation:
This
is
an
informational
message
that
is
displayed
when
the
verbose
(-w)
flag
is
specified.
This
message
describes
the
type
of
data
sent.
Message
Variables:
data_type
-
The
type
of
data
sent.
Possible
values
are
addObjectInstance,
modifyObjectInstance,
deleteObjectInstance,
event,
beginDiscovery,
commit,
or
rollbackDiscovery.
sess_ID
-
The
session
identifier
GTMCL5217I
Starting
state:
initial_tag
Explanation:
This
is
an
informational
message
that
is
displayed
when
the
verbose
(-ww)
flag
is
specified.
This
message
notes
the
initial
tag
was
parsed.
Message
Variables:
initial_tag
-
The
initial
tag
that
was
parsed.
Possible
values
are
tbsm:addObjectInstance,
tbsm:modifyObjectInstance,
tbsm:deleteObjectInstance,
tbsm:event,
tbsm:addLinkInstance,
tbsm:deleteLinkInstance,
tbsm:beginDiscovery,
tbsm:commitDiscovery,
or
tbsm:rollbackDiscovery.
120
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
GTMCL5218E
Invalid
action
flag
received:
action
Explanation:
An
action
tag
was
parsed
from
the
XML
file
that
was
not
valid.
Message
Variables:
action
-
The
action
substituted
for
the
action
in
error.
Valid
values
are
tbsm:addObjectInstance,
tbsm:modifyObjectInstance,
tbsm:deleteObjectInstance,
tbsm:event,
tbsm:addLinkInstance,
tbsm:deleteLinkInstance,
tbsm:beginDiscovery,
tbsm:commitDiscovery,
or
tbsm:rollbackDiscovery.
System
Action:
No
further
processing
was
performed
when
the
error
was
found.
User
Response:
Review
the
XML
file
and
fix
the
error,
then
run
the
command
again.
GTMCL5219I
Ending
state:
closing_tag
Explanation:
This
is
an
informational
message
that
is
displayed
when
the
verbose
(-ww)
flag
is
specified.
This
message
notes
the
closing
tag
was
parsed.
Message
Variables:
closing_tag
-
The
closing
tag
that
was
parsed.
Possible
values
are
tbsm:addObjectInstance,
tbsm:modifyObjectInstance,
tbsm:deleteObjectInstance,
tbsm:event,
tbsm:addLinkInstance,
tbsm:deleteLinkInstance,
tbsm:beginDiscovery,
tbsm:commitDiscovery,
or
tbsm:rollbackDiscovery.
GTMCL5220E
Fatal
error.
Substring:
substring
from
string
string
Explanation:
The
command
processor
encountered
an
error
while
parsing
the
XML
file.
Message
Variables:
substring
-
The
substring
substituted
for
the
substring
that
caused
the
error
string
-
The
string
substituted
from
which
the
substring
was
taken
System
Action:
No
further
processing
was
performed
when
the
error
was
found.
User
Response:
Review
the
XML
file
and
fix
the
error,
then
run
the
command
again.
GTMCL5221I
Reading
line:
line
Explanation:
This
is
an
informational
message
that
is
displayed
when
the
verbose
(-ww)
flag
is
specified.
Message
Variables:
line
-
The
line
read
from
the
XML
file
GTMCL5222I
Skipping
line:
line
Explanation:
This
is
an
informational
message
that
is
displayed
when
the
verbose
(-ww)
flag
is
specified.
Message
Variables:
line
-
The
line
read
from
the
XML
file
that
is
skipped
User
Response:
Review
the
XML
file
to
ensure
that
there
is
not
a
problem
with
skipping
this
line.
GTMCL5223I
Processing
line:
line
Explanation:
This
is
an
informational
message
that
is
displayed
when
the
verbose
(-ww)
flag
is
specified.
Message
Variables:
line
-
The
substring
that
is
processed
GTMCL5224E
Error
parsing
tags
in
string
string.
Possible
cause
is
a
missing
″>″.
Explanation:
The
command
processor
expected
to
find
a
closing
greater
than
character
(>)
in
the
string,
but
could
not
find
it.
Message
Variables:
string
-
The
string
substituting
the
string
with
the
error
System
Action:
The
transaction
is
cancelled
and
processing
stops.
User
Response:
Specify
the
-ww
flag
and
run
the
XML
file
again
to
further
isolate
the
line
in
the
file
where
the
error
occurred.
Correct
the
XML
tagging
and
run
the
command
again.
GTMCL5225I
Validating
XML
input
file.
Explanation:
This
is
an
informational
message
that
is
displayed
when
the
verbose
(-w)
flag
is
specified
and
indicates
that
XML
validation
is
about
to
begin.
GTMCL5232E
SAX
exception
during
validation.
message
Explanation:
The
SAX
parser
returned
an
exception
while
validating
the
XML
file.
Message
Variables:
message
-
The
message
from
the
SAX
exception
System
Action:
Command
processing
stops.
User
Response:
Correct
the
XML
file
and
run
the
command
again.
GTMCL5234I
message
Explanation:
This
is
a
generic
message
used
to
write
statistical
data
to
the
error
log
located
in
the
install_dir/XMLtoolkit/logs
directory.
The
contents
of
the
statistical
data
is
not
translated
and
is
free
form.
Chapter
7.
Common
Listener
Messages
-
GTMCL5200I
-
GTMCL6000E
121
GTMCL5235I
Query
transaction:
session:
trans_ID
Explanation:
This
message
is
in
response
to
the
querycl
command.
Message
Variables:
session
-
The
queried
session
trans_ID
-
The
transaction
identifier
for
which
information
is
requested
GTMCL5236I
The
current
state
of
the
transaction
is
state
Explanation:
This
message
is
in
response
to
the
querycl
command
and
provides
the
state
of
the
transaction
identifier
specified
on
the
command.
Message
Variables:
state
-
The
state
of
the
transaction
identifier.
Possible
states
are
as
follows:
0
An
SQL
exception
occurred.
Try
the
operation
again.
1
Data
was
received
and
is
awaiting
processing
by
the
database
2
Receiving
data
3
The
transaction
was
rolled
back.
Review
the
CL_Status
table
and
the
common
listener
log
for
errors
4
The
database
is
processing
the
request
5
The
transaction
completed
successfully
6
There
was
an
error
in
database
processing
7
Waiting
to
be
preprocessed
for
the
Tivoli
Enterprise
Console
hierarchy
8
Preprocessing
the
Tivoli
Enterprise
Console
hierarchy
9
Preprocessing
the
Tivoli
Enterprise
Console
hierarchy
failed
GTMCL5237I
Status:
first_substitution
second_substitution
Explanation:
This
message
provides
detailed
data
associated
with
the
transaction
specified
by
the
-t
flag.
The
detailed
data
generally
consists
of
several
occurrences
of
the
GTMCL5237I
message.
Message
Variables:
first_substitution
-
The
first
substitution
is
the
status
associated
with
this
message
second_substitution
-
The
second
substitution
is
the
disposition
of
the
message
GTMCL5238E
An
invalid
integer
was
found,
″value″
Explanation:
A
value
supplied
on
the
command
line
should
be
an
integer,
but
converting
it
from
a
string
to
an
integer
failed.
Message
Variables:
value
-
The
value
that
was
not
valid
System
Action:
Command
processing
stops.
User
Response:
Correct
the
command
line
syntax
and
run
the
command
again.
GTMCL5239E
The
required
tag
″EEhost″
is
missing
from
the
instance
definition.
Explanation:
Resources
created
as
Tivoli
Enterprise
Console-managed
resources
must
include
the
EEhost
attribute.
This
attribute
defines
the
Tivoli
Enterprise
Console
server
that
manages
the
resource.
System
Action:
Command
processing
stops.
User
Response:
Add
the
required
tag
and
run
the
command
again.
GTMCL5240E
An
instance
associated
with
a
class
other
than
a
business
system
was
found.
This
is
not
allowed
for
the
type
of
transaction
specified.
Explanation:
Resources
created
using
bulk
and
delta
(using
the
-t
flag)
must
have
LineOfBusiness
specified
for
the
class.
A
different
class
was
specified
for
the
line
displayed
in
the
message
that
follows.
System
Action:
Command
processing
stops.
User
Response:
Correct
the
instance
definition
as
follows
and
run
the
command
again:
<class>LineOfBusiness</class>
GTMCL5241I
Orphan
resource
information
follows:
Explanation:
This
is
a
multiline
message
displaying
the
orphaned
resources
that
exist
in
the
database.
See
the
GTMCL5242I
message
that
follows.
GTMCL5242I
Instid:
instance_id
Class\ProdVer:
resource_class
InstrID:
instrumentation_id
Explanation:
This
message
provides
the
information
associated
with
one
instance
of
an
orphaned
resource.
Message
Variables:
instance_id
-
The
instance
identifier
specified
with
the
<instid>
tag
in
the
XML
file
resource_class
-
The
type
of
resource
specified
with
the
<class>
or
<prodver>
tag
in
the
XML
file
instrumentation_id
-
The
name
of
the
instrumentation
specified
with
the
-n
flag
on
the
enqueuecl
command
to
create
the
resource
GTMCL5243I
GTMCL5243I:
Validation
completed
successfully.
Explanation:
The
XML
file
formatted
correctly.
GTMCL5244E
GTMCL5244E:
The
XML
parser
does
not
recognize
a
feature:
name
Explanation:
The
feature
specified
in
the
message
is
not
recognized
by
the
parser
as
a
valid
feature
name.
Parsing
stops.
A
copy
of
the
SAX
parser
not
supporting
this
feature
is
contained
in
the
classpath.
Verify
that
the
SAX
parser
being
used
is
the
copy
in
the
122
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
XMLtoolkit/jars
directory
of
the
installation
and
that
another
copy
does
not
exist
in
either
the
lib
or
lib/ext
directory
of
the
JRE.
Message
Variables:
name
-
The
name
that
is
not
recognized
GTMCL5245E
GTMCL5245E:
The
XML
parser
does
not
support
a
feature:
name
Explanation:
The
feature
specified
in
the
message
is
not
recognized
by
the
parser.
Parsing
stops.
A
copy
of
the
SAX
parser
not
supporting
this
feature
is
contained
in
the
classpath.
Verify
that
the
SAX
parser
being
used
is
the
copy
in
the
installation’s
XMLtoolkit/jars
directory
and
that
another
copy
does
not
exist
in
either
the
lib
or
lib/ext
directory
of
the
JRE.
Message
Variables:
name
-
The
name
that
is
not
recognized
GTMCL5246E
GTMCL5246E:
Validation
completed
with
errors.
Explanation:
The
specified
XML
file
is
not
formatted
correctly.
Earlier
messages
list
the
lines
containing
errors.
GTMCL5247E
GTMCL5247E:
A
syntax
error
was
found
in
the
command,
the
flag
value
is
required
but
was
not
provided.
Explanation:
The
flag
specified
in
the
message
is
not
an
optional
flag.
Administrator
Response:
Correct
the
command
line
input
and
rerun
the
command.
GTMCL5248E
GTMCL5248E:
Parser
initialization
failed
with
the
following
exception:
exceptionMessage.
Explanation:
The
program
was
unable
to
setup
the
XML
parser.
The
command
response
will
not
be
displayed.
Administrator
Response:
If
the
problem
cannot
be
corrected,
contact
IBM
Software
Support.
GTMCL5249E
GTMCL5249E:
Exception
thrown
while
parsing
response.
exceptionMessage.
Explanation:
An
XML
exception
was
thrown
by
the
XML
parser.
Administrator
Response:
If
the
problem
cannot
be
corrected,
contact
IBM
Software
Support.
GTMCL5250E
GTMCL5250E:
Invalid
value
hashvalue
received
in
methodname
for
value
xmltag
Explanation:
An
unexpected
XML
tag
was
found,
the
tag
was
not
expected
in
the
context
in
which
it
was
received.
Administrator
Response:
If
the
problem
cannot
be
corrected,
contact
IBM
Software
Support.
GTMCL5251E
GTMCL5251E:
An
invalid
response
was
received.
The
tag
is
xmltag.
Explanation:
An
unexpected
XML
response
tag
was
found,
the
tag
was
not
expected
in
the
context
in
which
it
was
received.
Administrator
Response:
If
the
problem
cannot
be
corrected,
contact
IBM
Software
Support.
GTMCL5252E
GTMCL5252E:
Expected
tag
closexmltag,
but
found
tag
openxmltag.
Explanation:
The
expected
closing
XML
tag
was
not
found.
Message
Variables:
closexmltag
-
The
tag
that
was
expected
openxmltag
-
The
tag
that
was
found
Administrator
Response:
If
the
problem
cannot
be
corrected,
contact
IBM
Software
Support.
GTMCL5253E
LOBC
and
LOBL
links
cannot
be
deleted.
Resources
cannot
be
moved
by
deleting
a
link
and
relinking
the
resource
with
another
link.
Delete
the
resource,
not
the
link
to
the
resource.
Explanation:
A
delete
link
operation
was
requested
and
the
link
type
was
LOBC
or
LOBL.
The
LOBC
links
are
used
for
containment,
meaning
they
identify
where
the
resource
should
be
placed.
Resources
cannot
be
moved
by
deleting
a
containment
link
and
then
linking
the
resource
with
a
new
containment
link.
To
move
a
resource,
delete
the
current
resource
and
then
create
a
new
resource
with
the
proper
links.
The
LOBL
links
are
used
to
associate
a
physical
resource
with
a
business
system
or
to
create
a
business
system
shortcut.
To
remove
the
association
with
a
physical
resource,
delete
the
business
system.
To
remove
a
business
system
shortcut,
delete
the
business
system
shortcut.
Administrator
Response:
Modify
the
XML
file
to
delete
the
resource,
not
the
link,
and
then
resubmit
the
XML
file.
Chapter
7.
Common
Listener
Messages
-
GTMCL5200I
-
GTMCL6000E
123
GTMCL5254E
Single
quotes
are
not
allowed
in
names,
instance
identifiers,
and
critical
resource
list
user
names.
A
single
quote
was
found
in
xmldata.
Explanation:
Single
quotation
marks
are
not
allowed
in
instance
identifiers,
resource
names,
and
critical
resource
list
user
names.
Message
Variables:
xmldata
-
The
tag
in
the
XML
file
that
contained
the
single
quotation
marks.
Administrator
Response:
Edit
the
XML
file
and
remove
the
single
quotation
marks
from
the
string
found
to
be
in
error.
Issue
the
command
again.
GTMCL6000E
A
child
object
is
already
a
parent
object
in
the
Business
System
tree
which
causes
a
primary
key
violation
in
the
lob_link
table.
This
recursive
hierarchy
is
not
supported.
Explanation:
This
error
occurs
if
the
Automated
Business
System
configuration
file
defines
a
recursive
Business
System
Path.
An
example
is
a
Pattern
entry
that
matches
the
LOB
class
and
the
attribute
to
match
is
name.
The
matched
name
corresponds
to
an
existing
Business
System
in
one
of
the
Path
statements,
and
a
CriteriaToPath
entry
attempts
to
place
this
Business
System
lower
in
it’s
own
Path
hierarchy
(resulting
in
a
Path
loop).
User
Response:
Modify
the
Automated
Business
System
configuration
file
to
not
place
a
Business
System
lower
in
it’s
own
hierarchy.
124
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
Chapter
8.
DB2
Feed
Messages
-
GTMDB1001I
-
GTMDB1006W
The
following
messages
are
issued
by
the
Tivoli
Business
Systems
Manager
DB2
feed.
GTMDB1001I
No
records
to
process
because
there
are
no
DB2
discovery
batches
in
the
state
state.
Explanation:
No
records
currently
exist
that
require
processing
by
the
system
at
this
time
for
this
function.
Message
Variables:
state
-
The
mode
of
the
batch
processing,
which
is
a
string.
Examples
of
modes
are
ALLOCATED,
ENQUEUED,
LOADED,
INPROGRESS,
and
COMPLETED.
System
Action:
The
system
continues
to
run
and
will
process
additional
records
as
they
arrive
when
the
function
is
called
again.
GTMDB1002E
Error
loading
discovery
batch
file
file_path.
Explanation:
The
loading
process
was
not
able
to
load
the
specified
file.
Possible
reasons
are
the
file
format
is
not
valid
or
the
specified
action
type
does
not
match
the
contents
of
the
file.
Message
Variables:
file_path
-
The
full
path
and
file
name
of
the
file
containing
the
records
for
a
particular
batch
System
Action:
The
system
continues
to
run,
but
this
batch
will
not
be
loaded.
Administrator
Response:
Verify
that
the
file
is
formatted
correctly,
and
attempt
to
load
the
file
again
using
the
CreateDiscoveryBatch.ksh
command.
GTMDB1003E
Failed
inserting
TBSM
data
into
DB2Discovery
table.
Explanation:
An
internal
database
error
was
encountered
that
prevented
the
file
from
being
loaded.
System
Action:
The
system
continues
to
run,
but
this
batch
will
not
be
loaded.
Administrator
Response:
Attempt
to
load
the
file
again
using
the
CreateDiscoveryBatch.ksh
command.
GTMDB1004E
Batch
batch_id
cannot
be
resolved
to
any
operating
system.
Explanation:
The
discovery
batch
records
are
associated
with
an
operating
system
based
on
their
netid.cpname
value.
If
the
netid.cpname
value
cannot
be
matched
to
a
known
operating
system,
then
the
objects
cannot
be
discovered.
Message
Variables:
file_path
-
The
batch
ID
number,
which
is
an
integer.
This
number
is
used
to
identify
a
particular
group
of
discovery
records.
System
Action:
The
system
continues
to
run,
but
this
batch
will
not
be
processed.
Administrator
Response:
Restart
the
source/390
object
pump
to
rediscover
the
operating
system
to
the
netid.cpname
correlation,
then
attempt
to
load
the
file
again
using
the
CreateDiscoveryBatch.ksh
command.
GTMDB1005I
Deleted
count
successfully
processed
DB2Discovery
rows
for
batch
batch_id.
Explanation:
The
discovery
processing
is
complete
and
the
records
that
were
successfully
discovered
are
purged
from
the
batch.
Message
Variables:
count
-
The
number
of
records,
which
is
an
integer
batch_id
-
The
batch
ID
number,
which
is
an
integer.
This
number
is
used
to
identify
a
particular
group
of
discovery
records.
System
Action:
The
system
continues
to
run,
and
the
state
for
this
batch
is
set
to
COMPLETED.
Administrator
Response:
Restart
the
source/390
object
pump
to
rediscover
the
operating
system
to
the
netid.cpname
correlation,
then
attempt
to
load
the
file
again
using
the
CreateDiscoveryBatch.ksh
command.
GTMDB1006W
count
DB2Discovery
rows
for
batch
batch_id
have
not
been
completely
processed.
Explanation:
The
discovery
processing
is
complete,
but
some
objects
might
not
have
been
fully
discovered
due
to
a
lack
of
object
hierarchy
information.
Message
Variables:
count
-
The
number
of
records,
which
is
an
integer
batch_id
-
The
batch
ID
number,
which
is
an
integer.
This
number
is
used
to
identify
a
particular
group
of
discovery
records.
System
Action:
The
system
continues
to
run,
and
the
state
for
this
batch
is
set
to
COMPLETED.
Administrator
Response:
Examine
the
remaining
records
by
issuing
the
SELECT
*
FROM
DB2Discovery
WHERE
batchid
=
batch_id
SQL
command.
If
the
objects
in
the
batch
need
to
be
discovered,
complete
a
©
Copyright
IBM
Corp.
2000,
2004
125
partial
or
full
discovery
on
the
appropriate
objects.
126
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
Chapter
9.
EDI
Messages
-
GTMED0001
-
GTMSA108
The
REXX
EDI
instrumentation
process
(System
Automation
for
OS/390,
OPS/MVS,
AF/Operator,
MAINVIEW
Auto
Operator)
generates
the
following
messages
for
the
components
of
Tivoli
Business
Systems
Manager.
GTMED0001E
procedure:
name
is
not
a
valid
Format
Type.
Aborting
procedure.
Explanation:
A
format
type
that
was
not
valid
was
passed
when
sending
data
through
the
REXX
EDI
call.
Message
Variables:
procedure
-
The
name
of
procedure
being
processed
name
-
The
format
type
being
passed
System
Action:
The
REXX
EDI
call
ends.
Administrator
Response:
Send
the
data
again
using
a
valid
format
type.
GTMED0002E
procedure:
name
is
not
a
valid
Action
Type.
Aborting
procedure.
Explanation:
An
action
type
that
was
not
valid
was
passed
when
sending
data
through
the
REXX
EDI
call.
Message
Variables:
procedure
-
The
name
of
procedure
being
processed
name
-
The
action
type
being
passed
System
Action:
The
REXX
EDI
call
ends.
Administrator
Response:
Send
the
data
again
using
a
valid
action
type.
GTMED0003E
procedure:
name
is
not
a
valid
Data
Type.
Aborting
procedure.
Explanation:
A
data
type
that
was
not
valid
was
passed
when
sending
data
through
the
REXX
EDI
call.
Message
Variables:
procedure
-
The
name
of
procedure
being
processed
name
-
The
data
type
being
passed
System
Action:
The
REXX
EDI
call
ends.
Administrator
Response:
Send
the
data
again
using
a
valid
data
type.
GTMAF100
FORMAT
TYPE
(ACTION
TYPE
OR
DATA
TYPE)
PASSED
TO
EDI
NOT
VALID.
CALL
BEING
TERMINATED
ON
SYSTEM
SYSID
sysid
Explanation:
Indicates
that
the
format
type
(action
type
or
data
type)
being
passed
using
REXX
EDI
GTMEDIAF,
for
AF
Operator,
is
not
valid.
Message
Variables:
sysid
-
The
system
ID
where
the
message
was
issued
System
Action:
The
call
to
GTMEDIAF
ends
and
no
data
is
sent
to
Tivoli
Business
Systems
Manager
for
processing.
User
Response:
Send
data
with
valid
format
type
(action
type
or
data
type).
GTMAO100
FORMAT
TYPE
(ACTION
TYPE
OR
DATA
TYPE)
PASSED
TO
EDI
NOT
VALID
CALL
BEING
TERMINATED
ON
SYSTEM
SYSID
sysid
Explanation:
Indicates
that
the
format
type
(action
type
or
data
type)
being
passed
using
REXX
EDI
GTMEDIAO,
for
AF
Operator,
is
not
valid.
Message
Variables:
sysid
-
The
system
ID
where
the
message
was
issued
System
Action:
The
call
to
GTMEDIAO
ends
and
no
data
is
sent
to
Tivoli
Business
Systems
Manager
for
processing.
User
Response:
Send
data
with
valid
format
type
(action
type
or
data
type).
GTMOP100
FORMAT
TYPE
(ACTION
TYPE
OR
DATA
TYPE)
PASSED
TO
EDI
NOT
VALID
CALL
BEING
TERMINATED
ON
SYSTEM
SYSID
sysid
Explanation:
Indicates
that
the
format
type
(action
type
or
data
type)
being
passed
using
REXX
EDI
GTMEDIOP,
for
AF
Operator,
is
not
valid.
Message
Variables:
sysid
-
The
system
ID
where
the
message
was
issued
System
Action:
The
call
to
GTMEDIOP
ends
and
no
data
is
sent
to
Tivoli
Business
Systems
Manager
for
processing.
User
Response:
Send
data
with
valid
format
type
(action
type
or
data
type).
©
Copyright
IBM
Corp.
2000,
2004
127
GTMSA100
FORMAT
TYPE
(ACTION
TYPE
OR
DATA
TYPE)
PASSED
TO
EDI
NOT
VALID
CALL
BEING
TERMINATED
ON
SYSTEM
SYSID
sysid
Explanation:
Indicates
that
the
format
type
(action
type
or
data
type)
being
passed
using
REXX
EDI
GTMEDISA,
for
AF
Operator,
is
not
valid.
Message
Variables:
sysid
-
The
system
ID
where
the
message
was
issued
System
Action:
The
call
to
GTMEDISA
ends
and
no
data
is
sent
to
Tivoli
Business
Systems
Manager
for
processing.
User
Response:
Send
data
with
valid
format
type
(action
type
or
data
type).
GTMAF101
EDI
FAILURE
ON
SYSID
RC
=
return_code
AC
=
abend_code
Explanation:
The
call
to
AOPRXEDI
(AOPEDI)
failed.
Message
Variables:
return_code-
The
return
code
abend_code
-
The
abend
code
Return
codes
from
EDI:
Return
Code
Meaning
0
SUCCESSFUL
COMPLETION
4
EDI
INTERFACE
NOT
AVAILABLE
(PUMP
NOT
UP
OR
NOT
RUNNING
EDI)
8
NO
SPACE.
NOT
ENOUGH
SPACE
IN
THE
PUMP
EDI
BUFFER
FOR
THE
DATA
12
DATA
ITEM
IS
LARGER
THAN
MAX
ALLOWED
BY
EDI
(1024
BYTES)
16
GETMAIN
FOR
WORKING
STORAGE
FAILED
(PC
ROUTINE)
20
GETMAIN
FOR
WORKING
STORAGE
FAILED
(EDI
ROUTINE)
24
AN
ABEND
OCCURRED,
CODE
IN
REGISTER
1
(EDI
ROUTINE)
28
AN
ABEND
OCCURRED,
CODE
IN
REGISTER
1
(PC
ROUTINE)
32
ZERO
LENGTHDATA
PASSED
(WILL
NOT
OCCUR
BECAUSE
THE
MODULE
DOES
NOT
PASS
ZERO
LENGTH
DATA
ITEMS
TO
EDI)
The
Abend
Code
is
in
register
1
as
00XXXYYY,
where
XXX
is
the
system
abend
code
and
YYY
is
the
user
abend
code.
System
Action:
The
call
to
AOPRXEDI
(by
GTMEDIAF)
ends
and
no
data
is
sent
to
Tivoli
Business
Systems
Manager
for
processing.
User
Response:
Verify
the
data
sets
are
properly
allocated
by
AF
Operator
started
task.
If
the
problem
persists,
contact
IBM
Software
Support.
GTMAO101
EDI
FAILURE
ON
SYSID
RC
=return_code
AC
=
abend_code
Explanation:
The
call
to
AOPRXEDI
(AOPEDI)
failed.
Message
Variables:
return_code
-
The
return
code
abend_code
-
The
abend
code
Return
codes
from
EDI:
Return
Code
Meaning
0
SUCCESSFUL
COMPLETION
4
EDI
INTERFACE
NOT
AVAILABLE
(PUMP
NOT
UP
OR
NOT
RUNNING
EDI)
8
NO
SPACE.
NOT
ENOUGH
SPACE
IN
THE
PUMP
EDI
BUFFER
FOR
THE
DATA
12
DATA
ITEM
IS
LARGER
THAN
MAX
ALLOWED
BY
EDI
(1024
BYTES)
16
GETMAIN
FOR
WORKING
STORAGE
FAILED
(PC
ROUTINE)
20
GETMAIN
FOR
WORKING
STORAGE
FAILED
(EDI
ROUTINE)
24
AN
ABEND
OCCURRED,
CODE
IN
REGISTER
1
(EDI
ROUTINE)
28
AN
ABEND
OCCURRED,
CODE
IN
REGISTER
1
(PC
ROUTINE)
32
ZERO
LENGTHDATA
PASSED
(WILL
NOT
OCCUR
BECAUSE
THE
MODULE
DOES
NOT
PASS
ZERO
LENGTH
DATA
ITEMS
TO
EDI)
The
Abend
Code
is
in
register
1
as
00XXXYYY,
where
XXX
is
the
system
abend
code
and
YYY
is
the
user
abend
code.
System
Action:
The
call
to
AOPRXEDI
(by
GTMEDIAO)
ends
and
no
data
is
sent
to
Tivoli
Business
Systems
Manager
for
processing.
User
Response:
Verify
the
data
sets
are
properly
allocated
by
Auto
Operator
started
task.
If
the
problem
persists,
contact
IBM
Software
Support.
GTMOP101
EDI
FAILURE
ON
SYSID
RC
=
return_code
AC
=
abend_code
Explanation:
The
call
to
AOPRXEDI
(AOPEDI)
failed.
Message
Variables:
return_code
-
The
return
code
abend_code
-
The
abend
code
Return
codes
from
EDI:
128
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
Return
Code
Meaning
0
SUCCESSFUL
COMPLETION
4
EDI
INTERFACE
NOT
AVAILABLE
(PUMP
NOT
UP
OR
NOT
RUNNING
EDI)
8
NO
SPACE.
NOT
ENOUGH
SPACE
IN
THE
PUMP
EDI
BUFFER
FOR
THE
DATA
12
DATA
ITEM
IS
LARGER
THAN
MAX
ALLOWED
BY
EDI
(1024
BYTES)
16
GETMAIN
FOR
WORKING
STORAGE
FAILED
(PC
ROUTINE)
20
GETMAIN
FOR
WORKING
STORAGE
FAILED
(EDI
ROUTINE)
24
AN
ABEND
OCCURRED,
CODE
IN
REGISTER
1
(EDI
ROUTINE)
28
AN
ABEND
OCCURRED,
CODE
IN
REGISTER
1
(PC
ROUTINE)
32
ZERO
LENGTHDATA
PASSED
(WILL
NOT
OCCUR
BECAUSE
THE
MODULE
DOES
NOT
PASS
ZERO
LENGTH
DATA
ITEMS
TO
EDI)
The
Abend
Code
is
in
register
1
as
00XXXYYY,
where
XXX
is
the
system
abend
code
and
YYY
is
the
user
abend
code.
System
Action:
The
call
to
AOPRXEDI
(by
GTMEDIOP)
ends
and
no
data
is
sent
to
Tivoli
Business
Systems
Manager
for
processing.
User
Response:
Verify
the
data
sets
are
properly
allocated
by
OPS/MVS
started
task.
If
the
problem
persists,
contact
IBM
Software
Support.
GTMSA101
EDI
FAILURE
ON
SYSID
RC
=
return_code
AC
=
abend_code
Explanation:
The
call
to
AOPRXEDI
(AOPEDI)
failed.
Message
Variables:
return_code
-
The
return
code
abend_code
-
The
abend
code
Return
codes
from
EDI:
Return
Code
Meaning
0
SUCCESSFUL
COMPLETION
4
EDI
INTERFACE
NOT
AVAILABLE
(PUMP
NOT
UP
OR
NOT
RUNNING
EDI)
8
NO
SPACE.
NOT
ENOUGH
SPACE
IN
THE
PUMP
EDI
BUFFER
FOR
THE
DATA
12
DATA
ITEM
IS
LARGER
THAN
MAX
ALLOWED
BY
EDI
(1024
BYTES)
16
GETMAIN
FOR
WORKING
STORAGE
FAILED
(PC
ROUTINE)
20
GETMAIN
FOR
WORKING
STORAGE
FAILED
(EDI
ROUTINE)
24
AN
ABEND
OCCURRED,
CODE
IN
REGISTER
1
(EDI
ROUTINE)
28
AN
ABEND
OCCURRED,
CODE
IN
REGISTER
1
(PC
ROUTINE)
32
ZERO
LENGTHDATA
PASSED
(WILL
NOT
OCCUR
BECAUSE
THE
MODULE
DOES
NOT
PASS
ZERO
LENGTH
DATA
ITEMS
TO
EDI)
The
Abend
Code
is
in
register
1
as
00XXXYYY,
where
XXX
is
the
system
abend
code
and
YYY
is
the
user
abend
code.
System
Action:
The
call
to
AOPRXEDI
(by
GTMEDISA)
ends
and
no
data
is
sent
to
Tivoli
Business
Systems
Manager
for
processing.
User
Response:
Verify
the
data
sets
are
properly
allocated
by
systems
automation
started
task.
If
the
problem
persists,
contact
IBM
Software
Support.
GTMAF102
EDI
PROBLEM
RESOLVED
ON
SYSID
sysid
Explanation:
Indicates
that
the
EDI
problem
documented
by
message
GTMAF101
has
been
resolved.
Message
Variables:
sysid
-
The
system
ID
where
the
message
was
issued
System
Action:
The
call
to
GTMEDIAF
processed
successfully.
GTMAO102
EDI
PROBLEM
RESOLVED
ON
SYSID
sysid
Explanation:
Indicates
that
the
EDI
problem
documented
by
message
GTMAO101
has
been
resolved.
Message
Variables:
sysid
-
The
system
ID
where
the
message
was
issued
System
Action:
The
call
to
GTMEDIAO
processed
successfully.
GTMOP102
EDI
PROBLEM
RESOLVED
ON
SYSID
sysid
Explanation:
Indicates
that
the
EDI
problem
documented
by
message
GTMOP101
has
been
resolved.
Message
Variables:
sysid
-
The
system
ID
where
the
message
was
issued
System
Action:
The
call
to
GTMEDIOP
processes
successfully.
Chapter
9.
EDI
Messages
-
GTMED0001
-
GTMSA108
129
GTMSA102
EDI
PROBLEM
RESOLVED
ON
SYSID
sysid
Explanation:
Indicates
that
the
EDI
problem
documented
by
message
GTMSA101
has
been
resolved.
Message
Variables:
sysid
-
The
system
ID
where
the
message
was
issued
System
Action:
The
call
to
GTMEDISA
processes
successfully.
GTMAF103
THE
data_type
format_type,
action_type,
data_type
HAS
A
LENGTH
OF
0
TBSM
EDI
PROCESSING
STOPPED
sysid
Explanation:
Indicates
that
data
type
passed
to
EDI
has
length
of
0
and
EDI
processing
has
stopped.
Message
Variables:
data_type
-
The
valid
data
type
has
a
length
of
0
format_type
-
The
valid
format
type
has
a
length
of
0
action_type
-
The
valid
action
type
has
a
length
of
0
sysid
-
The
system
ID
where
the
message
was
issued
System
Action:
The
call
to
AOPRXEDI
(by
GTMEDIAF)
ends
and
no
data
is
sent
to
Tivoli
Business
Systems
Manager
for
processing.
Also,
message
GTMAF108
is
issued
detailing
format
type,
action
type,
and
data
types
passed
during
this
call.
User
Response:
Pass
the
proper
data
for
the
data
type
in
error.
GTMAO103
THE
data_type
format_type,
action_type,
data_type
HAS
A
LENGTH
OF
0
TBSM
EDI
PROCESSING
STOPPED
sysid
Explanation:
Indicates
that
data
type
passed
to
EDI
has
length
of
0
and
EDI
processing
has
stopped.
Message
Variables:
data_type
-
The
valid
data
type
has
a
length
of
0
format_type
-
The
valid
format
type
has
a
length
of
0
action_type
-
The
valid
action
type
has
a
length
of
0
sysid
-
The
system
ID
where
the
message
was
issued
System
Action:
The
call
to
AOPRXEDI
(by
GTMEDIAO)
ends
and
no
data
is
sent
to
Tivoli
Business
Systems
Manager
for
processing.
Also,
message
GTMAO108
is
issued
detailing
format
type,
action
type,
and
data
types
passed
during
this
call.
User
Response:
Pass
the
proper
data
for
the
data
type
in
error.
GTMOP103
THE
data_type
format_type,
format_type,
data_type
HAS
A
LENGTH
OF
0
TBSM
EDI
PROCESSING
STOPPED
sysid
Explanation:
Indicates
that
data
type
passed
to
EDI
has
length
of
0
and
EDI
processing
has
stopped.
Message
Variables:
data_type
-
The
valid
data
type
has
a
length
of
0
format_type
-
The
valid
format
type
has
a
length
of
0
action_type
-
The
valid
action
type
has
a
length
of
0
sysid
-
The
system
ID
where
the
message
was
issued
System
Action:
The
call
to
AOPRXEDI
(by
GTMEDIOP)
ends
and
no
data
is
sent
to
Tivoli
Business
Systems
Manager
for
processing.
Also,
message
GTMOP108
is
issued
detailing
format
type,
action
type,
and
data
types
passed
during
this
call.
User
Response:
Pass
the
proper
data
for
the
data
type
in
error.
GTMSA103
THE
format_type,
action_type,
data_type
HAS
A
LENGTH
OF
0
TBSM
EDI
PROCESSING
STOPPED
Explanation:
Indicates
that
data
type
passed
to
the
EDI
has
length
of
0
and
EDI
processing
has
stopped
because
of
the
length.
Message
Variables:
format_type
-
The
valid
format
type
has
a
length
of
0
action_type
-
The
valid
action
type
has
a
length
of
0
data_type
-
The
valid
data
type
has
a
length
of
0
System
Action:
The
call
to
AOPRXEDI
(by
GTMEDISA)
ends
and
no
data
is
sent
to
Tivoli
Business
Systems
Manager
for
processing.
Also,
message
GTMSA108
is
issued
detailing
format
type,
action
type,
and
data
types
passed
during
this
call.
User
Response:
You
must
pass
the
proper
data
for
data
type
in
error.
GTMAF104
INVALID
FORMAT
TYPE
PASSED:
format_type
TBSM
EDI
PROCESSING
STOPPED
Explanation:
Indicates
that
a
format
type
that
was
not
valid
was
passed
and
EDI
processing
has
terminated.
Message
Variables:
format_type
-
The
format
type
that
was
not
valid
System
Action:
The
call
to
AOPRXEDI
(by
GTMEDIAF)
ends
and
no
data
is
sent
to
Tivoli
Business
Systems
Manager
for
processing.
Also,
message
GTMAF108
is
issued
detailing
format
type,
action
type,
and
data
types
passed
during
this
call.
User
Response:
You
must
pass
the
proper
format
type.
130
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
GTMAO104
INVALID
FORMAT
TYPE
PASSED:
format_type
TBSM
EDI
PROCESSING
STOPPED
Explanation:
Indicates
that
a
format
type
that
was
not
valid
was
passed
and
EDI
processing
has
ended.
Message
Variables:
format_type
-
The
format
type
that
was
not
valid
System
Action:
The
call
to
AOPRXEDI
(by
GTMEDIAO)
ends
and
no
data
is
sent
to
Tivoli
Business
Systems
Manager
for
processing.
Also,
message
GTMAO108
is
issued
detailing
format
type,
action
type,
and
data
types
passed
during
this
call.
User
Response:
You
must
pass
the
proper
format
type.
GTMOP104
INVALID
FORMAT
TYPE
PASSED:
format_type
TBSM
EDI
PROCESSING
STOPPED
Explanation:
Indicates
that
a
format
type
that
was
not
valid
was
passed
and
EDI
processing
has
ended.
Message
Variables:
format_type
-
The
format
type
that
was
not
valid
System
Action:
The
call
to
AOPRXEDI
(by
GTMEDIOP)
ends
and
no
data
is
sent
to
Tivoli
Business
Systems
Manager
for
processing.
Also,
message
GTMOP108
is
issued
detailing
format
type,
action
type,
and
data
types
passed
during
this
call.
User
Response:
You
must
pass
the
proper
format
type.
GTMSA104
INVALID
FORMAT
TYPE
PASSED:
format_type
TBSM
EDI
PROCESSING
STOPPED
Explanation:
Indicates
that
a
format
type
that
was
not
valid
was
passed
and
EDI
processing
has
ended
Message
Variables:
format_type
-
The
format
type
that
was
not
valid
System
Action:
The
call
to
AOPRXEDI
(by
GTMEDISA)
ends
and
no
data
is
sent
to
Tivoli
Business
Systems
Manager
for
processing.
Also,
message
GTMSA108
is
issued
detailing
Format
Type,
Action
Type,
and
Data
Types
passed
during
this
call.
User
Response:
You
must
pass
the
proper
Format
Type.
GTMAF105
INVALID
ACTION
TYPE
PASSED:
format_type,
action_type
TBSM
EDI
PROCESSING
STOPPED
Explanation:
Indicates
that
an
action
type
that
was
not
valid
was
passed
and
Tivoli
Business
Systems
Manager
EDI
processing
has
ended.
Message
Variables:
format_type
-
The
valid
format
type
action_type
-
The
action
type
that
was
not
valid
System
Action:
The
call
to
AOPRXEDI
(by
GTMEDIAF)
ends
and
no
data
is
sent
to
Tivoli
Business
Systems
Manager
for
processing.
Also,
message
GTMAF108
is
issued
detailing
Format
Type,
Action
Type,
and
Data
Types
passed
during
this
call.
User
Response:
You
must
pass
the
proper
Action
Type
GTMAO105
INVALID
ACTION
TYPE
PASSED:
format_type,
action_type
TBSM
EDI
PROCESSING
STOPPED
Explanation:
Indicates
that
an
action
type
that
was
not
valid
was
passed
and
Tivoli
Business
Systems
Manager
EDI
processing
has
ended.
Message
Variables:
format_type
-
The
valid
format
type
action_type
-
The
action
type
that
was
not
valid
System
Action:
The
call
to
AOPRXEDI
(by
GTMEDIAO)
ends
and
no
data
is
sent
to
Tivoli
Business
Systems
Manager
for
processing.
Also,
message
GTMAO108
is
issued
detailing
format
type,
action
type,
and
data
types
passed
during
this
call.
User
Response:
You
must
pass
the
proper
action
type
GTMOP105
INVALID
ACTION
TYPE
PASSED:
format_type,
action_type
TBSM
EDI
PROCESSING
STOPPED
Explanation:
Indicates
that
an
action
type
that
was
not
valid
was
passed
and
EDI
processing
has
ended.
Message
Variables:
format_type
-
The
valid
format
type
action_type
-
The
action
type
that
was
not
valid
System
Action:
The
call
to
AOPRXEDI
(by
GTMEDIOP)
ends
and
no
data
is
sent
to
Tivoli
Business
Systems
Manager
for
processing.
Also,
message
GTMOP108
is
issued
detailing
format
type,
action
type,
and
data
types
passed
during
this
call.
User
Response:
You
must
pass
the
proper
action
type
GTMSA105
INVALID
ACTION
TYPE
PASSED:
format_type,
action_type
TBSM
EDI
PROCESSING
STOPPED
Explanation:
Indicates
that
an
action
type
that
was
not
valid
was
passed
and
EDI
processing
has
ended
Message
Variables:
format_type
-
The
valid
format
type
action_type
-
The
action
type
that
was
not
valid
System
Action:
The
call
to
AOPRXEDI
(by
Chapter
9.
EDI
Messages
-
GTMED0001
-
GTMSA108
131
GTMEDISA)
ends
and
no
data
is
sent
to
Tivoli
Business
Systems
Manager
for
processing.
Also,
message
GTMSA108
is
issued
detailing
format
type,
action
type,
and
data
types
passed
during
this
call.
User
Response:
You
must
pass
the
proper
action
type
GTMAF106
INVALID
DATA
TYPE
PASSED:
format_type,
action_type,
data_type
TBSM
EDI
PROCESSING
STOPPED
Explanation:
Indicates
that
a
data
type
that
was
not
valid
was
passed
and
EDI
processing
has
ended.
Message
Variables:
format_type
-
The
valid
format
type
action_type
-
The
valid
action
type
data_type
-
The
data
type
that
was
not
valid
System
Action:
The
call
to
AOPRXEDI
(by
GTMEDIAF)
ends
and
no
data
is
sent
to
Tivoli
Business
Systems
Manager
for
processing.
Also,
message
GTMAF108
is
issued
detailing
format
type,
action
type,
and
data
types
passed
during
this
call.
User
Response:
You
must
pass
the
proper
data
type
GTMAO106
INVALID
DATA
TYPE
PASSED:
format_type,
action_type,
data_type
TBSM
EDI
PROCESSING
STOPPED
Explanation:
Indicates
that
a
data
type
that
was
not
valid
was
passed
and
EDI
processing
has
ended.
Message
Variables:
format_type
-
The
valid
format
type
action_type
-
The
valid
action
type
data_type
-
The
data
type
that
was
not
valid
System
Action:
The
call
to
AOPRXEDI
(by
GTMEDIAO)
ends
and
no
data
is
sent
to
Tivoli
Business
Systems
Manager
for
processing.
Also,
message
GTMAO108
is
issued
detailing
format
type,
action
type,
and
data
types
passed
during
this
call.
User
Response:
You
must
pass
the
proper
data
type
GTMOP106
INVALID
DATA
TYPE
PASSED:
format_type,
action_type,
data_type
TBSM
EDI
PROCESSING
STOPPED
Explanation:
Indicates
that
a
data
type
that
was
not
valid
was
passed
and
EDI
processing
has
ended.
Message
Variables:
format_type
-
The
valid
format
type
action_type
-
The
valid
action
type
data_type
-
The
data
type
that
was
not
valid
System
Action:
The
call
to
AOPRXEDI
(by
GTMEDIOP)
ends
and
no
data
is
sent
to
Tivoli
Business
Systems
Manager
for
processing.
Also,
message
GTMOP108
is
issued
detailing
format
type,
action
type,
and
data
types
passed
during
this
call.
User
Response:
You
must
pass
the
proper
data
type
GTMSA106
INVALID
DATA
TYPE
PASSED:
format_type,
action_type,
data_type
TBSM
EDI
PROCESSING
STOPPED
Explanation:
Indicates
that
a
data
type
that
was
not
valid
was
passed
and
EDI
processing
has
ended.
Message
Variables:
format_type
-
The
valid
format
type
action_type
-
The
valid
action
type
data_type
-
The
data
type
that
was
not
valid
System
Action:
The
call
to
AOPRXEDI
(by
GTMEDISA)
ends
and
no
data
is
sent
to
Tivoli
Business
Systems
Manager
for
processing.
Also,
message
GTMSA108
is
issued
detailing
format
type,
action
type,
and
data
types
passed
during
this
call.
User
Response:
You
must
pass
the
proper
data
type
GTMAF107
REQUIRED
DATA
TYPE
format_type,
action_type,
data_type
TBSM
EDI
PROCESSING
STOPPED
Explanation:
Indicates
that
a
required
data
type
was
not
passed
to
the
EDI
call.
EDI
processing
stops.
Message
Variables:
format_type
-
The
valid
format
type
action_type
-
The
valid
action
type
data_type
-
The
required
data
type
that
is
necessary
to
process
the
data
System
Action:
The
call
to
AOPRXEDI
(by
GTMEDIAF)
ends
and
no
data
is
sent
to
Tivoli
Business
Systems
Manager
for
processing.
Also,
message
GTMAF108
is
issued
detailing
format
type,
action
type,
and
data
types
passed
during
this
call.
User
Response:
You
must
pass
the
proper
data
for
data
type
in
error.
GTMAO107
REQUIRED
DATA
TYPE
format_type,
action_type,
data_type
TBSM
EDI
PROCESSING
STOPPED
Explanation:
Indicates
that
a
required
Data
Type
was
not
passed
to
the
EDI
call.
EDI
processing
stops.
Message
Variables:
format_type
-
The
valid
format
type
action_type
-
The
valid
action
type
data_type
-
The
required
data
type
that
is
necessary
to
process
the
data
System
Action:
The
call
to
AOPRXEDI
(by
GTMEDIAO)
ends
and
no
data
is
sent
to
Tivoli
132
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
Business
Systems
Manager
for
processing.
Also,
message
GTMAO108
is
issued
detailing
format
type,
action
type,
and
Data
Types
passed
during
this
call.
User
Response:
You
must
pass
the
proper
data
for
data
type
in
error.
GTMOP107
REQUIRED
DATA
TYPE
format_type,
action_type,
data_type
TBSM
EDI
PROCESSING
STOPPED
Explanation:
Indicates
that
a
required
data
type
was
not
passed
to
the
EDI
call.
EDI
processing
stops.
Message
Variables:
format_type
-
The
valid
format
type
action_type
-
The
valid
action
type
data_type
-
The
required
data
type
that
is
necessary
to
process
the
data
System
Action:
The
call
to
AOPRXEDI
(by
GTMEDIOP)
stops
and
no
data
is
sent
to
Tivoli
Business
Systems
Manager
for
processing.
Also,
message
GTMOP108
is
issued
detailing
format
type,
action
type,
and
data
types
passed
during
this
call.
User
Response:
You
must
pass
the
proper
data
for
data
type
in
error.
GTMSA107
REQUIRED
DATA
TYPE
format_type,
action_type,
data_type
TBSM
EDI
PROCESSING
STOPPED
Explanation:
Indicates
that
a
required
data
type
was
not
passed
to
the
EDI
call.
EDI
processing
stops.
Message
Variables:
format_type
-
The
valid
format
type
action_type
-
The
valid
action
type
data_type
-
The
required
data
type
that
is
necessary
to
process
the
data
System
Action:
The
call
to
AOPRXEDI
(by
GTMEDISA)
stops
and
no
data
is
sent
to
Tivoli
Business
Systems
Manager
for
processing.
Also,
message
GTMSA108
is
issued
detailing
format
type,
action
type,
and
data
types
passed
during
this
call.
User
Response:
You
must
pass
the
proper
data
for
data
type
in
error.
GTMAF108
THE
FOLLOWING
DATA
WAS
PASSED
USING
TBSM
EDI:
FORMAT
TYPE:
format_typeACTION
TYPE:
action_type
DATA
TYPE:
data_type
DATA
TYPE:
data_type
Explanation:
This
message
is
issued
after
GTMSA103,
GTMSA104,
GTMSA105,
GTMSA106,
and
GTMSA107
messages
to
show
the
format
type,
action
type,
and
data
types
passed
to
the
EDI
call.
Message
Variables:
format_type
-
The
format
type
action_type
-
The
action
type
data_type
-
The
data
type
User
Response:
Follow
User
Response
for
messages
GTMAF103,
GTMAF104,
GTMAF105,
GTMAF106,
and
GTMAF107.
GTMAO108
THE
FOLLOWING
DATA
WAS
PASSED
USING
TBSM
EDI:
FORMAT
TYPE
:
format_type
ACTION
TYPE:
action_type
DATA
TYPE:
data_type
Explanation:
This
message
is
issued
after
GTMSA103,
GTMSA104,
GTMSA105,
GTMSA106,
and
GTMSA107
messages
to
show
the
format
type,
action
type,
and
data
types
passed
to
the
EDI
call.
Message
Variables:
format_type
-
The
format
type
action_type
-
The
action
type
data_type
-
The
data
type
User
Response:
Follow
User
Response
for
messages
GTMAO103,
GTMAO104,
GTMAO105,
GTMAO106,
and
GTMAO107.
GTMOP108
THE
FOLLOWING
DATA
WAS
PASSED
USING
TBSM
EDI:
FORMAT
TYPE:
format_type
ACTION
TYPE:
action_type
DATA
TYPE:
data_type
Explanation:
This
message
is
issued
after
GTMSA103,
GTMSA104,
GTMSA105,
GTMSA106,
and
GTMSA107
messages
to
show
the
format
type,
action
type,
and
data
types
passed
to
the
EDI
call.
Message
Variables:
format_type
-
The
format
type
action_type
-
The
action
type
data_type
-
The
data
type
User
Response:
Follow
User
Response
for
messages
GTMOP103,
GTMOP104,
GTMOP105,
GTMOP106,
and
GTMOP107.
GTMSA108
THE
FOLLOWING
DATA
WAS
PASSED
USING
TBSM
EDI:
FORMAT
TYPE:
format_type
ACTION
TYPE:
action_type
DATA
TYPE:
data_type
Explanation:
This
message
is
issued
after
GTMSA103,
GTMSA104,
GTMSA105,
GTMSA106,
and
GTMSA107
messages
to
show
the
format
type,
action
type,
and
data
types
passed
to
the
EDI
call.
Message
Variables:
format_type
-
The
format
type
action_type
-
The
action
type
data_type
-
The
data
type
User
Response:
Follow
the
user
response
for
messages
Chapter
9.
EDI
Messages
-
GTMED0001
-
GTMSA108
133
GTMSA103,
GTMSA104,
GTMSA105,
GTMSA106,
and
GTMSA107.
134
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
Chapter
10.
EIF
Sender
Service
Messages
GTMES0001I
-
GTMES7011I
The
following
messages
are
from
the
EIF
Sender
service.
GTMES0001I
Starting
Tivoli
BSM
EIF
Sender
built
on
date.
Explanation:
The
Tivoli
Business
Systems
Manager
EIF
Sender
service
was
started.
Message
Variables:
date
-
The
build
date
displayed
represents
the
date
from
the
ASIEIFSender.jar
file.
GTMES0002I
The
EIF
Sender
shutdown
process
has
been
initiated.
Explanation:
The
EIF
Sender
shutdown
process
started.
All
Tivoli
Enterprise
Console
threads
are
stopped,
all
database
connections
are
closed,
and
the
service
is
stopped.
GTMES0003E
Exception
caught
during
EIF
Sender
shutdown.
Exception:
error.
Explanation:
An
error
occurred
while
trying
to
shutdown
the
EIF
Sender
service.
Message
Variables:
error
-
The
error
that
occurred
Administrator
Response:
Consult
the
log
files
for
additional
information.
If
the
problem
cannot
be
resolved,
contact
IBM
Software
Support.
GTMES0004I
The
EIF
Sender
shutdown
process
has
completed.
Explanation:
The
EIF
Sender
shutdown
process
completed.
All
Tivoli
Enterprise
Console
threads
are
stopped,
all
database
connections
are
closed,
and
the
service
is
stopped.
GTMES0005I
The
following
key
and
value
retrieved
from
the
ASIEIFSender.properties
file
is
not
valid.
Key:
key
Value:
value.
Explanation:
The
value
specified
for
the
key
is
not
valid.
The
default
value
for
the
specified
keyword
is
used.
Message
Variables:
key
-
The
specified
keyword
value
-
The
value
that
was
not
valid
Administrator
Response:
If
you
do
not
want
to
use
the
default
value
for
the
key,
stop
the
EIF
Sender
service,
specify
a
valid
value
for
the
key
in
the
ASIEIFSender.properties
file,
and
start
the
EIF
Sender
service
again.
GTMES0006E
Exception
caught
while
initializing
EsTecAdapter.
Exception:
error.
Explanation:
An
error
occurred
while
trying
to
start
an
EsTecAdapter
thread
that
sends
events
to
a
Tivoli
Enterprise
Console
host.
Message
Variables:
error
-
The
error
that
occurred
System
Action:
The
EIF
Sender
service
stops.
Administrator
Response:
Consult
the
log
files
for
additional
information
and
start
the
EIF
Sender
service
again.
If
the
problem
cannot
be
resolved,
contact
IBM
Software
Support.
GTMES0007E
There
are
no
exits
configured,
service
will
be
stopped.
Explanation:
The
EIF
Sender
has
not
been
configured
to
start
any
Tivoli
Enterprise
Console
or
user
exit
threads.
System
Action:
The
EIF
Sender
service
stops.
Administrator
Response:
To
configure
exits,
update
the
ASIEIFSender.properties
file.
GTMES0008E
Exception
caught
while
initializing
EsJdbcHandlerDb.
Exception:
error.
Explanation:
An
error
occurred
while
trying
to
start
the
AlJdbchandlerDb
thread.
Message
Variables:
error
-
The
error
that
occurred
System
Action:
The
EIF
Sender
service
stops.
Administrator
Response:
Consult
the
log
files
for
additional
information
and
start
the
EIF
Sender
service
again.
If
the
problem
cannot
be
resolved,
contact
IBM
Software
Support.
GTMES0009E
Exception
caught
while
updating
the
status
for
a
request.
Exception:
error.
Explanation:
An
error
occurred
while
trying
to
update
the
status
field
in
the
IntegrationRequest
table.
Message
Variables:
error
-
The
error
that
occurred
Administrator
Response:
Consult
the
log
files
for
additional
information.
If
the
problem
cannot
be
resolved,
contact
IBM
Software
Support.
©
Copyright
IBM
Corp.
2000,
2004
135
GTMES0010E
Exception
caught
while
connecting
to
database.
Retry
initiated.
Exception:
error.
Explanation:
An
error
occurred
while
trying
to
connect
to
the
database.
The
EIF
Sender
will
try
the
database
connection
again
for
the
configured
DatabaseServerWait
interval.
Message
Variables:
error
-
The
error
that
occurred
System
Action:
The
EIF
Sender
service
stops.
Administrator
Response:
Consult
the
log
files
for
additional
information.
Verify
that
the
database
parameters
specified
in
the
ASIEIFSender.properties
file
are
correct.
Verify
that
the
Tivoli
Business
Systems
Manager
database
has
been
installed
and
configured
with
the
correct
values.
Start
the
EIF
Sender
service
again.
If
the
problem
cannot
be
resolved,
contact
IBM
Software
Support.
GTMES0011E
Exception
caught
while
connecting
to
database.
Exception:
error.
Explanation:
An
error
occurred
while
trying
to
connect
to
the
database.
Message
Variables:
error
-
The
error
that
occurred
System
Action:
The
EIF
Sender
service
stops.
Administrator
Response:
Consult
the
log
files
for
additional
information.
Verify
that
the
database
parameters
specified
in
the
ASIEIFSender.properties
file
are
correct.
Verify
that
the
Tivoli
Business
Systems
Manager
database
has
been
installed
and
configured
with
the
correct
values.
Start
the
EIF
Sender
service
again.
If
the
problem
cannot
be
resolved,
contact
IBM
Software
Support.
GTMES0012E
Exception
caught
closing
a
database
connection.
Exception:
error.
Explanation:
An
error
occurred
while
trying
to
close
a
database
connection.
Message
Variables:
error
-
The
error
that
occurred
Administrator
Response:
Consult
the
log
files
for
additional
information.
If
the
problem
cannot
be
resolved,
contact
IBM
Software
Support.
GTMES0013E
Exception
caught
while
updating
the
EIF_HealthMonitor
table.
Exception:
error.
Explanation:
An
error
occurred
while
trying
to
insert
data
in
the
EIF_HealthMonitor
table.
Message
Variables:
error
-
The
error
that
occurred
Administrator
Response:
Consult
the
log
files
for
additional
information.
If
the
problem
cannot
be
resolved,
contact
IBM
Software
Support.
GTMES0014E
Exception
loading
a
Tivoli
Enterprise
Console
configuration
file.
Exception:
error.
Explanation:
An
error
occurred
while
trying
to
read
Tivoli
Enterprise
Console
configuration
data
from
a
properties
file.
Message
Variables:
error
-
The
error
that
occurred
Administrator
Response:
Use
the
tecstatusconfig
script
to
verify
that
the
configuration
data
for
the
specified
Tivoli
Enterprise
Console
host
exists.
GTMES0015E
Error
returned
from
EIF
API
while
attempting
to
send
an
event.
Error:
error.
Explanation:
An
error
occurred
while
the
EsTecAdapter
thread
was
trying
to
send
an
event
to
a
Tivoli
Enterprise
Console
host.
Message
Variables:
error
-
The
error
that
occurred
Administrator
Response:
Consult
the
log
files
for
additional
information.
If
the
problem
cannot
be
resolved,
contact
IBM
Software
Support.
GTMES0016E
Exception
caught
while
EsTecAdapter
was
attempting
to
send
an
event.
Exception:
error.
Explanation:
An
error
occurred
while
the
EsTecAdapter
thread
was
trying
to
send
an
event
to
a
Tivoli
Enterprise
Console
host.
Message
Variables:
error
-
The
error
that
occurred
Administrator
Response:
Consult
the
log
files
for
additional
information.
If
the
problem
cannot
be
resolved,
contact
IBM
Software
Support.
GTMES0017E
Exception
caught
while
EsTecAdapter
was
initializing
the
TECAgent.
Exception:
error.
Explanation:
An
error
occurred
while
the
EsTecAdapter
thread
was
trying
to
initialize
the
TECAgent.
Message
Variables:
error
-
The
error
that
occurred
Administrator
Response:
Consult
the
log
files
for
additional
information.
If
the
problem
cannot
be
resolved,
contact
IBM
Software
Support.
136
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
GTMES0018E
User
exit
message
msg_text.
Explanation:
A
message
was
issued
by
the
user
exit.
Message
Variables:
msg_text
-
The
text
of
the
user
exit
message
Administrator
Response:
The
contents
of
the
substitution
variable
is
defined
by
the
user
when
the
user
exit
was
written.
Consult
the
log
files
for
additional
information
and
consult
your
local
procedures
to
determine
the
impact
of
the
message.
GTMES7002E
A
syntax
error
was
found
in
the
command,
the
value
value
was
not
expected.
Explanation:
While
parsing
the
command
line
parameters,
a
value
was
encountered
that
was
not
valid.
Message
Variables:
value
-
The
value
in
error
System
Action:
No
further
processing
is
performed
after
the
error
was
found.
Administrator
Response:
Correct
the
command
line
input
and
run
the
command
again.
GTMES7004E
The
resource
specified
could
not
be
uniquely
identified.
Explanation:
The
resource
specified
by
the
values
of
the
-c
and
-n
flags
could
not
be
uniquely
identified.
Specify
the
parent
or
parents
of
the
resource
by
using
the
-t
and
-s
flags.
System
Action:
The
database
did
not
change.
User
Response:
Specify
unique
identifiers
using
the
-t
and
-s
flags
and
submit
the
request
again.
GTMES7005E
The
EIF
Sender
service
could
not
be
stopped.
The
cache
will
not
be
flushed.
Explanation:
The
cache
cannot
be
flushed
while
the
EIF
Sender
service
is
running.
The
command
could
not
stop
the
service.
System
Action:
No
further
processing
is
performed
after
the
error
was
found.
Administrator
Response:
Stop
the
EIF
Sender
service
and
run
the
command
again.
GTMES7006I
The
EIF
Sender
service
state
event
cache
has
been
flushed.
Explanation:
The
cache
was
cleared.
GTMES7007E
The
EIF
Sender
service
state
event
cache
has
been
flushed,
but
the
service
could
not
be
restarted.
Explanation:
The
cache
was
cleared,
but
the
command
was
unable
to
start
the
service
again.
System
Action:
No
further
processing
is
performed.
Administrator
Response:
Start
the
EIF
Sender
service
manually.
GTMES7008I
The
EIF
Sender
service
has
been
started.
Explanation:
The
EIF
Sender
server
successfully
started.
GTMES7009E
The
EIF
Sender
service
failed
to
start.
Explanation:
The
EIF
Sender
server
was
started,
but
it
could
not
start
successfully.
System
Action:
No
further
processing
is
performed.
Administrator
Response:
Check
the
EIF
Sender
service
log
for
errors.
Correct
any
errors
and
start
the
service
again.
GTMES7010E
Unable
to
setup
the
Tivoli
Framework
environment,
processing
stops.
Explanation:
Before
loading
the
baroc
file,
the
Tivoli
environment
must
be
set
up.
This
is
done
by
sourcing
the
setup_env.sh
file,
but
this
file
could
not
be
found.
System
Action:
Processing
ends.
Administrator
Response:
Source
the
setup_env.sh
file
and
then
run
the
script
again.
GTMES7011I
The
baroc
for
Tivoli
Business
Systems
Manager
state
change
events
was
successfully
loaded.
Explanation:
The
classes
for
the
Tivoli
Business
Systems
Manager
state
change
events
have
been
loaded
in
the
Tivoli
Enterprise
Console
rulebase.
This
change
does
not
take
effect
until
the
Tivoli
Enterprise
Console
server
is
recycled.
System
Action:
No
further
processing
is
performed.
Chapter
10.
EIF
Sender
Service
Messages
GTMES0001I
-
GTMES7011I
137
Chapter
11.
Executive
Dashboard
Messages
-
GTMEV5200I,
GTMEV5201E
and
GTMXV0001E
-
GTMXV1002E
The
following
messages
are
generated
by
the
Tivoli
Business
Systems
Manager
executive
dashboard.
GTMEV5200I
Tivoli
Service
Level
Advisor
trends
will
be
deleted
after
number
days
and
violations
will
be
deleted
after
number
days.
Explanation:
This
message
displays
the
current
settings
for
the
retention
of
Tivoli
Service
Level
Advisor
events.
The
values
provided
are
in
days.
This
message
is
displayed
by
the
slaSystemConfiguration
script.
Message
Variables:
number
-
The
number
of
days
that
trends,
trend-cancels,
and
violations
remain
in
the
Tivoli
Business
Systems
Manager
database.
GTMEV5201E
The
value
provided
for
the
-t
or
-v
flag
must
be
greater
than
zero.
Explanation:
The
–t
and
–v
flags
set
the
life,
in
days,
of
a
trend
and
violation
in
the
Tivoli
Business
Systems
Manager
database.
This
value
must
be
a
number
greater
than
0.
User
Response:
Resubmit
the
command
with
a
valid
value.
GTMXV0001E
There
was
an
error
communicating
with
the
IBM
Tivoli
Business
Systems
Manager
executive
dashboard
server.
Explanation:
See
the
message.
System
Action:
IBM
Tivoli
Business
Systems
Manager
executive
dashboard
will
display
stale
data
until
you
exit
and
logon
again.
Operator
Response:
Contact
your
system
administrator.
Administrator
Response:
Identify
and
correct
the
problem
that
prevents
communications
with
the
IBM
Tivoli
Business
Systems
Manager
executive
dashboard
server.
GTMXV0002E
The
IBM
Tivoli
Business
Systems
Manager
executive
dashboard
server
has
detected
an
internal
error.
Explanation:
See
the
message.
Operator
Response:
Contact
your
system
administrator.
Administrator
Response:
Consult
the
WebSphere®
Application
Server
logs
to
see
if
any
messages
there
provide
additonal
details
or
corrective
actions
for
the
problem.
If
not,
contact
IBM
Software
Support.
GTMXV0003E
The
IBM
Tivoli
Business
Systems
Manager
executive
dashboard
server
was
unable
to
save
your
preferences.
Explanation:
See
the
message.
Operator
Response:
Contact
your
system
administrator.
Administrator
Response:
Check
the
IBM
Tivoli
Business
Systems
Manager
database
and
verify
that
it
is
functioning
properly.
Messages
and
exceptions
logged
in
the
WebSphere
Application
Server
logs
might
also
provide
additional
details
or
corrective
actions
for
the
problem.
GTMXV0004E
The
IBM
Tivoli
Business
Systems
Manager
executive
dashboard
server
was
unable
to
retrieve
the
information
you
requested
from
the
IBM
Tivoli
Business
Systems
Manager
database.
Explanation:
See
the
message.
Operator
Response:
Contact
your
system
administrator.
Administrator
Response:
Check
the
IBM
Tivoli
Business
Systems
Manager
database
and
verify
that
it
is
functioning
properly.
Messages
and
exceptions
logged
in
the
WebSphere
Application
Server
logs
might
also
provide
additional
details
or
corrective
actions
for
the
problem.
GTMXV0005I
You
have
requested
to
sign
off
and
exit
this
application.
Explanation:
See
the
message.
GTMXV0006W
There
are
no
services
configured
for
this
user.
Explanation:
See
the
message.
Operator
Response:
Contact
your
system
administrator
to
add
the
services
to
be
monitored
to
this
user.
©
Copyright
IBM
Corp.
2000,
2004
139
GTMXV0007E
Unable
to
obtain
the
requested
information.
Explanation:
See
the
message.
Operator
Response:
The
problem
could
be
due
to
a
database
error,
a
Web
server
error,
or
a
network
error.
If
this
error
continues,
close
the
browser
by
clicking
the
window
close
button
and
try
logging
in
again.
GTMXV0008E
Unable
to
process
information
received
from
the
Web
server.
Explanation:
See
the
message.
Operator
Response:
The
problem
is
due
to
an
error
in
the
Web
server.
Contact
your
system
administrator
for
assistance.
GTMXV0009E
Unable
to
send
information
received
to
the
Web
server.
Explanation:
See
the
message.
Operator
Response:
The
problem
is
due
to
an
error
in
the
executive
dashboard.
Contact
your
system
administrator
for
assistance.
GTMXV0010E
The
IBM
Tivoli
Business
Systems
Manager
executive
dashboard
server
has
detected
an
error
trying
to
authenticate
your
user
ID.
Explanation:
See
the
message.
Operator
Response:
The
problem
is
due
to
an
error
in
Web
server
security
or
the
IBM
Tivoli
Business
Systems
Manager
executive
dashboard
server.
Contact
your
system
administrator
for
assistance.
GTMXV0011I
\nThe
IBM
Tivoli
Business
Systems
Manager
Version
3.1
executive
dashboard.
\n\nLicensed
Materials
-
Property
of
IBM
\n5724-C51
\n(C)
Copyright
by
IBM
Corp.
1996,
2004.
All
rights
reserved.
\n\nUS
Government
Users
Restricted
Rights
-
Use,
duplication,
or
disclosure
restricted
by
GSA
ADP
Schedule
Contract
with
IBM
Corp.\n\n
Explanation:
See
the
message.
GTMXV1001W
An
unrecognized
request_type
request
was
received
from
host
for
user
user
Explanation:
See
the
message.
System
Action:
An
error
is
returned
to
the
client.
Server
processing
continues.
Administrator
Response:
This
warning
can
indicate
a
mismatch
between
the
IBM
Tivoli
Business
Systems
Manager
executive
dashboard
client
and
server.
Verify
that
there
were
no
errors
installing
or
upgrading
the
IBM
Tivoli
Business
Systems
Manager
executive
dashboard
server.
If
there
were
errors,
consult
the
installation
documentation
for
further
actions.
If
there
were
no
errors,
contact
IBM
Software
Support.
GTMXV1002E
An
internal
error
was
detected:
details
Explanation:
See
the
message.
System
Action:
An
error
is
returned
to
the
client.
Server
processing
continues.
Administrator
Response:
Contact
IBM
Software
Support
for
assistance.
140
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
Chapter
12.
Health
Monitor
Service
Messages
GTMHM0001E
-
GTMHM0005I
The
following
messages
are
generated
by
the
Tivoli
Business
Systems
Manager
Health
Monitor
service.
GTMHM0001E
Invalid
Health
Monitor
server
name
specified.
Explanation:
The
registry
items
could
not
be
found
on
the
host
specified
as
the
Health
Monitor
server.
If
it
was
not
explicitly
specified,
then
the
local
host
was
used.
System
Action:
The
operation
fails.
User
Response:
Specify
the
hostname
of
the
Health
Monitor
server
and
try
the
operation
again.
The
user
ID
and
password
of
the
administrator
must
be
the
same
to
allow
access
between
the
Tivoli
Manager
Business
Systems
servers;
and
the
servers
must
be
in
the
same
domain.
GTMHM0002E
Health
Monitor
configuration
failed:
host_var=host_value:
rc
Explanation:
The
attempt
to
update
the
Health
Monitor
service
type
server
(host_var)
to
the
host
list
(host_value)
failed.
Message
Variables:
host_var
-
The
service
type
of
the
Health
Monitor
server
host_value
-
The
name
of
the
host
list
rc
-
The
return
code
System
Action:
The
operation
fails.
User
Response:
Verify
that
the
user
has
security
access
to
modify
the
registry
items
and
try
the
operation
again.
The
user
ID
and
password
of
the
administrator
must
be
the
same
to
allow
access
between
the
Tivoli
Manager
Business
Systems
servers;
and
the
servers
must
be
in
the
same
domain.
GTMHM0003E
Health
Monitor
configuration
failed:
invalid
server
type:
host_var
Explanation:
The
indicated
service
type
is
not
valid
Message
Variables:
host_var
-
The
service
type
that
is
not
valid
System
Action:
The
operation
fails.
User
Response:
Provide
a
valid
service
type
and
try
the
operation
again.
To
view
the
valid
list
of
service
types,
issue
the
ReconfigureHMS.ksh
command
and
specify
the
-l
option.
GTMHM0004E
An
error
occurred
starting
the
Health
Monitor
Service:
rc
Explanation:
The
Health
Monitor
service
could
not
be
started
again
after
the
registry
was
updated.
Message
Variables:
rc
-
The
return
code
System
Action:
The
operation
fails.
User
Response:
Try
the
operation
again.
If
the
operations
fails
again,
contact
IBM
Software
Support.
GTMHM0005I
Health
Monitor
restarted
with
updated
registry
items.
Explanation:
The
Health
Monitor
Service
was
started
again
after
the
host
lists
were
updated.
System
Action:
The
operation
completed
successfully.
User
Response:
Try
the
operation
again.
If
the
operations
fails
again,
contact
IBM
Software
Support.
©
Copyright
IBM
Corp.
2000,
2004
141
Chapter
13.
Intelligent
Monitoring
for
HP
OpenView
Messages
GTMFLCI000E
-
GTMFLCI308E
The
following
messages
are
issued
by
Intelligent
Monitoring
for
HP
OpenView.
GTMFLCI000E
Error!
Unable
to
retrieve
message
from
catalog.
Ensure
the
NLSPATH,
LC_MESSAGES
and
LANG
environment
variables
are
set
correctly.
Explanation:
The
command
could
not
open
the
message
catalog.
System
Action:
The
command
ends.
User
Response:
Set
the
appropriate
environment
variables
and
issue
the
command
again.
GTMFLCI001I
Unavailable.
Explanation:
The
process
is
not
available.
GTMFLCI002I
Available.
Explanation:
The
process
is
available.
GTMFLCI003I
Busy.
Explanation:
The
process
is
busy.
GTMFLCI004I
Processing
finished,
output
file
name
is:
name
Explanation:
The
user
has
issued
a
command.
Processing
for
this
command
has
completed
and
the
output
file
name
is
displayed
in
the
message.
Message
Variables:
name
-
The
name
of
the
output
file
GTMFLCI005E
Unable
to
communicate
with
the
local
host.
Explanation:
An
attempt
to
communicate
with
the
local
host
was
unsuccessful.
User
Response:
The
software
attempted
to
obtain
the
local
host
name
but
was
unsuccessful.
Ensure
that
the
IP
configuration
for
your
local
system
is
correct
and
try
again.
GTMFLCI006E
Unable
to
use
specified
socket.
socket
Explanation:
The
process
could
not
use
the
available
socket
because
the
port
to
which
it
was
trying
to
connect
was
not
available.
Message
Variables:
socket
-
The
name
of
the
socket
User
Response:
Verify
that
the
port
at
the
Tivoli
Business
Systems
Manager
server
is
available.
If
it
is
not,
start
the
listening
service
on
the
server
and
try
the
operation
again.
If
the
port
is
available,
contact
IBM
Software
Support.
GTMFLCI007E
Unable
to
allocate
socket.
Explanation:
The
system
might
have
run
out
of
available
sockets
or
sockets
are
temporarily
unavailable
for
the
interface.
System
Action:
The
MAXSOCKS
value
might
be
too
low
for
this
system.
User
Response:
Try
the
operation
again.
GTMFLCI008E
Unable
to
connect
to
server.
Explanation:
A
general
problem
occurred
when
connecting
to
the
server.
User
Response:
Try
the
command
or
operation
again.
GTMFLCI009E
Unable
to
send
to
server.
Explanation:
One
or
more
errors
occurred
while
trying
to
send
data
to
the
server.
System
Action:
If
the
initial
error
was
caused
by
a
network
problem
and
the
network
is
down,
the
data
has
been
queued
and
will
be
processed
when
the
network
is
restored.
GTMFLCI010E
Unable
to
receive
from
the
server.
Explanation:
The
process
waited
for
a
response
from
the
server,
but
did
not
receive
a
response.
User
Response:
Note
the
problem
and
check
to
ensure
there
is
a
valid
network
connection
to
the
server.
If
the
problem
persists,
contact
your
administrator.
GTMFLCI011E
Unable
to
use
the
specified
file
name:
name
Explanation:
The
process
attempted
to
use
the
specified
file
name.
However,
the
file
name
either
does
not
exist
or
is
read
protected.
Message
Variables:
name
-
The
name
of
the
file
that
could
not
be
used
System
Action:
The
system
has
denied
the
user
of
this
command
or
process
access
to
the
specified
file
name.
©
Copyright
IBM
Corp.
2000,
2004
143
User
Response:
If
this
is
an
authorization
problem,
ensure
you
are
a
super
user.
If
this
is
a
file
system
problem,
ensure
that
the
file
name
actually
exists
and
has
the
correct
file
permissions.
GTMFLCI012E
OVw
database
returned
a
null
map.
Explanation:
The
OpenView
OVw
database
has
returned
a
null
map
for
this
query.
GTMFLCI013E
OVw
database
returned
a
null
symbol
list.
Explanation:
The
OpenView
OVw
database
has
returned
a
null
symbol
list
for
this
query.
GTMFLCI014E
OVw
database
returned
a
null
field
bind
list.
Explanation:
The
OpenView
OVw
database
has
returned
a
null
field
bind
list
for
this
query.
GTMFLCI015E
Incorrect
invocation.
Explanation:
A
command
was
issued
with
the
incorrect
syntax.
User
Response:
Correct
the
syntax
error
and
issue
the
command
again.
Refer
to
the
IBM
Tivoli
Business
Systems
Manager
Command
Reference
for
more
information.
GTMFLCI016E
Topology
agent
is
mapping
map:
map
Explanation:
The
topology
agent
has
successfully
mapped
the
map
indicated
in
this
message.
Message
Variables:
map
-
The
name
of
the
map
GTMFLCI017E
Undefined
return
code
received
from
program
Explanation:
The
operation
generated
a
return
code
that
is
not
defined.
Message
Variables:
program
-
The
name
of
the
operation
that
generated
the
return
code
User
Response:
Note
the
return
code
and
the
symptoms
involved
in
the
error.
If
you
cannot
determine
the
problem,
gather
any
trace
and
log
files
and
contact
IBM
Software
Support.
GTMFLCI018E
Topology
agent
request
timed
out.
Explanation:
The
topology
agent
request
has
timed
out
for
the
configured
timeout
period.
User
Response:
Verify
that
the
configured
allowable
timeout
period
is
adequate
for
your
network.
GTMFLCI019E
Topology
agent
fatal
condition:
condition
Explanation:
The
indicated
condition
has
occurred.
The
topology
agent
might
be
unusable.
Message
Variables:
condition
-
The
topology
agent
fatal
condition
User
Response:
If
the
topology
agent
has
stopped,
try
to
restart
the
agent
and
try
the
operation
again.
GTMFLCI020E
Topology
agent
error:
error
Explanation:
An
error
has
occurred
in
the
topology
agent.
Message
Variables:
error
-
The
type
of
error
that
occurred
User
Response:
If
the
topology
agent
has
stopped,
try
to
restart
the
agent
and
try
the
operation
again.
GTMFLCI021I
Topology
agent
message:
message
Explanation:
The
topology
agent
has
received
the
message
indicated.
Message
Variables:
message
-
The
message
received
from
the
server
User
Response:
Read
the
agent
message
and,
if
necessary,
take
the
appropriate
action.
GTMFLCI022E
Topology
agent
is
unavailable
Explanation:
The
topology
agent
is
not
available.
User
Response:
If
the
topology
agent
has
stopped,
try
to
restart
the
agent.
GTMFLCI023I
Current
Topology
agent
configuration:
configuration
Explanation:
The
topology
agent
has
the
current
configuration
indicated.
Message
Variables:
configuration
-
The
configuration
currently
being
used
by
the
topology
agent
GTMFLCI024E
Topology
agent
did
not
find
the
specified
resources.
Explanation:
The
topology
agent
could
not
locate
the
resources
that
were
specified.
GTMFLCI025E
Topology
agent
unable
to
write
the
specified
file:
name
Explanation:
The
topology
agent
attempted
to
write
to
the
specified
file,
but
was
not
successful
because
of
an
authorization
or
permission
failure.
Message
Variables:
name
-
The
name
of
the
specified
file
144
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
User
Response:
The
process
is
not
authorized
or
does
not
have
permission
to
write
to
the
specified
file,
or
the
file
system
is
full.
Correct
the
problem
and
try
again.
GTMFLCI026I
Stop
message
has
been
sent
to
Topology
agent(s).
Explanation:
A
stop
message
has
been
sent
to
stop
one
or
more
topology
agents.
GTMFLCI027E
OVw
database
contains
a
loop
concerning
these
resources:
resources
Explanation:
The
OpenView
OVw
database
has
a
loop
that
contains
the
resources
indicated
in
this
message.
Message
Variables:
resources
-
The
database
resources
that
are
trapped
in
the
loop
User
Response:
The
database
might
be
damaged.
Contact
IBM
Software
Support
to
report
the
problem.
GTMFLCI028E
Topology
agent
is
busy.
Explanation:
The
topology
agent
is
currently
busy
and
is
unable
to
process
the
request.
GTMFLCI029I
Started
with
revision
level.
Explanation:
The
process
has
started
with
this
revision
level.
GTMFLCI030I
Unable
to
open
log
file.
Explanation:
The
process
was
unable
to
open
the
log
file.
GTMFLCI031E
Socket
number
was
not
provided
in
registration
file.
Explanation:
The
registration
file
did
not
contain
a
socket
number.
System
Action:
The
process
stops.
User
Response:
Ensure
that
the
registration
file
was
installed
properly
and
contains
the
appropriate
port
number.
If
it
does
not,
contact
IBM
Software
Support.
GTMFLCI032E
Socket
specified
is
not
valid.
Explanation:
The
process
has
detected
a
socket
that
is
not
valid.
System
Action:
The
process
stops.
User
Response:
This
could
be
an
internal
problem.
Contact
IBM
Software
Support.
GTMFLCI033E
Socket
allocation
failure.
Explanation:
The
system
was
unable
to
allocate
a
socket
for
the
process.
System
Action:
The
system
denies
additional
sockets
to
the
user
or
process.
Administrator
Response:
Verify
that
the
value
for
the
maximum
number
of
sockets
is
properly
set
for
users
and
processes.
GTMFLCI034E
recvfrom
failure.
Explanation:
The
system
was
unable
to
receive
data
from
a
socket
for
the
process.
System
Action:
The
process
can
no
longer
receive
data
on
the
socket.
Administrator
Response:
Restart
the
process.
GTMFLCI035E
Socket
already
in
use.
Explanation:
A
process
is
attempting
to
use
a
socket
that
is
already
in
use
by
another
process.
System
Action:
The
process
is
denied
use
of
the
socket.
Administrator
Response:
Restart
the
process.
GTMFLCI036I
Received
stop
command.
Explanation:
A
process
received
the
stop
command.
System
Action:
The
process
is
stopped.
GTMFLCI037I
Callback
parameters:
Explanation:
The
callback
parameters
for
the
process
follow.
GTMFLCI038I
IP
Internet
Totals:
Explanation:
The
totals
for
the
IP
internet
follow.
GTMFLCI039I
Callback
return
code.
Explanation:
The
callback
return
code
for
the
process
follows
this
message.
GTMFLCI040E
Unrecognized
command
received.
Explanation:
The
process
has
received
a
command
that
it
does
not
recognize.
User
Response:
Try
the
operation
again.
Chapter
13.
Intelligent
Monitoring
for
HP
OpenView
Messages
GTMFLCI000E
-
GTMFLCI308E
145
GTMFLCI041E
Unable
to
determine
the
resource
type:
Explanation:
The
process
was
unable
to
determine
the
type
of
the
resource
specified.
GTMFLCI043E
HP
OpenView
ending.
Explanation:
The
HP
OpenView
system
is
ending
by
request
or
because
of
an
unknown
reason.
User
Response:
Restart
the
system,
if
necessary.
GTMFLCI044E
Reports
the
following
error:
Explanation:
A
process
has
reported
the
error
that
follows
this
message.
User
Response:
Check
the
error
to
determine
what
occurred
and
take
the
appropriate
action.
GTMFLCI045E
Ending
for
the
following
reason:
Explanation:
The
process
is
ending
for
the
reason
that
follows
this
message.
User
Response:
Determine
the
error,
correct
the
problem
if
possible,
and
restart
the
process.
If
the
problem
persists,
contact
IBM
Software
Support.
GTMFLCI046E
Map
name
and
topology
registration
map
file
name
do
not
match:
Explanation:
The
name
of
the
map
specified
and
the
map
file
name
in
the
registration
file
do
not
match.
User
Response:
Ensure
the
map
name
matches
the
one
in
the
registration
map
file.
GTMFLCI047E
The
trap
wait
time
specified
was
not
valid.
The
default
value
will
be
used.
Explanation:
The
user
entered
a
value
that
was
not
valid
for
this
parameter.
User
Response:
Enter
a
valid
value
and
issue
the
command
again.
GTMFLCI048E
No
trap
wait
time
specified
in
the
registration
file.
Explanation:
The
command
could
not
find
a
default
trap
wait
time
in
the
registration
file.
User
Response:
Correct
the
registration
file
and
report
the
problem
to
IBM
Software
Support.
GTMFLCI049E
Unable
to
set
trap
interval
timer.
Explanation:
The
process
was
unable
to
set
the
interval
timer
for
trap
processing.
User
Response:
Ensure
that
the
registration
file
is
not
damaged
and
issue
the
command
again.
GTMFLCI050E
OVw
database
returned
a
null
map.
Explanation:
The
OpenView
OVw
database
returned
a
null
map
to
the
process.
User
Response:
Ensure
that
the
OVw
database
is
working
properly.
GTMFLCI051E
OVwDb
returned
a
null
field
bind
list
from
OvwDbGetFieldStringValue.
Parameters:
Explanation:
The
OpenView
OVw
database
returned
a
null
field
bind
list.
User
Response:
This
is
probably
an
internal
problem.
Contact
IBM
Software
Support.
GTMFLCI052E
Map
database
returned
a
null
pointer
from
OVwGetSymbolInfo.
Parameters:
Explanation:
The
map
database
returned
a
null
pointer.
The
parameters
follow.
User
Response:
Note
the
parameters
and
report
the
problem
to
IBM
Software
Support.
GTMFLCI053E
Unable
to
allocate
mutex
semaphore.
Another
agent
might
be
running.
Explanation:
The
process
did
not
start
because
it
was
unable
to
obtain
the
semaphore.
User
Response:
Stop
the
other
agent
holding
the
semaphore
and
try
the
operation
again
to
restart
the
agent.
GTMFLCI054E
Memory
allocation
failure
in
routine:
Explanation:
The
specified
routine
received
a
memory
allocation
error.
User
Response:
Ensure
there
are
enough
system
resources
for
this
process
to
run.
Administrator
Response:
Configure
the
maximum
memory
allowed
for
each
process.
GTMFLCI055E
Topology
export
configuration
files
are
missing
or
damaged.
Explanation:
The
configuration
file
for
the
topology
export
is
either
missing
or
damaged.
User
Response:
Try
to
fix
the
damaged
file.
It
might
be
necessary
to
reinstall
the
software
or
manually
edit
the
file
to
correct
this
problem.
GTMFLCI056I
/usr/OV/bin/nvecho
TBSM
bulk
upload
initiated.
Watch
for
updates
at
the
TBSM
console.\n\n
Explanation:
The
bulk
upload
started.
146
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
GTMFLCI057I
/usr/bin/echo
TBSM
bulk
upload
initiated.
Watch
for
updates
at
the
TBSM
console.
Explanation:
The
bulk
upload
started.
GTMFLCI100I
Tivoli’s
Intelligent
Monitor
for
OpenView,
Version
3,
Release
1,
Modification
0.
Explanation:
This
message
provides
version,
release,
and
modification
level
information.
GTMFLCI101I
The
following
Help
Message
is
provided.
Explanation:
This
message
is
provided
for
assistance.
GTMFLCI102I
The
form
of
a
valid
URL
is
myhost.mydomain.com:port
Explanation:
This
message
provides
the
valid
URL
format.
GTMFLCI103I
The
configuration
file
has
the
following
name
-
name
Explanation:
The
indicated
configuration
file
was
processed.
Message
Variables:
name
-
The
name
of
the
file.
GTMFLCI104I
The
contents
of
the
following
configuration
file
have
been
read
-
name
Explanation:
The
indicated
file
was
read
for
processing.
Message
Variables:
name
-
The
name
of
the
file.
GTMFLCI105I
The
following
file
has
been
temporary
deleted
prior
to
processing
-
name
Explanation:
The
indicated
file
was
read
and
temporarily
deleted
while
processing.
Message
Variables:
name
-
The
name
of
the
file.
GTMFLCI106I
The
following
INVALID
parameter
was
found
on
the
command
line
-
parameter
Explanation:
The
command
found
a
parameter
on
the
command
line
that
was
not
valid.
Message
Variables:
parameter
-
The
parameter
that
is
not
valid.
User
Response:
Specify
the
correct
parameter
and
issue
the
command
again.
GTMFLCI200W
Warning.
Explanation:
This
message
is
displayed
when
a
warning
occurs.
Refer
to
any
additional
messages
for
the
root
cause
of
the
problem.
GTMFLCI201W
The
following
file
has
NOT
been
deleted
-
name
Explanation:
The
following
properties
or
configuration
file
was
not
deleted.
Message
Variables:
name
-
The
name
of
the
file.
GTMFLCI202W
Display
parameter
found,
no
other
parameters
will
be
processed!
Explanation:
Because
the
-display
parameter
was
found
first,
no
other
parameters
or
values
on
the
line
are
processed.
GTMFLCI300E
An
Error
occurred.
Explanation:
An
error
occurred
during
command
processing.
An
incorrect
parameter
or
value
was
specified.
User
Response:
Refer
to
any
additional
messages
that
follow
and
correct
the
error.
GTMFLCI301E
An
Exception
Occurred.
Explanation:
An
exception
occurred
during
command
processing.
User
Response:
Contact
IBM
Software
Support.
GTMFLCI302E
An
Invalid
parameter
or
value
was
enter
with
this
particular
command.
Explanation:
An
unrecognized
parameter
or
incorrect
value
was
entered.
User
Response:
Specify
the
correct
parameter
and
value
and
issue
the
command
again.
GTMFLCI303E
A
required
parameter
or
value
for
this
particular
command
was
not
entered.
Explanation:
The
user
did
not
enter
a
required
parameter
and
value.
User
Response:
Make
sure
all
required
parameters
and
value
are
specified
and
issue
the
command
again.
GTMFLCI304E
A
problem
occurred
writing
a
required
parameter
or
value
to
the
following
file
-
name
Explanation:
The
setup
command
could
not
write
certain
parameters
to
the
indicated
file.
Chapter
13.
Intelligent
Monitoring
for
HP
OpenView
Messages
GTMFLCI000E
-
GTMFLCI308E
147
Message
Variables:
name
-
The
name
of
the
file.
GTMFLCI305E
The
following
malformed
URL
[
badurl
]
Explanation:
The
user
entered
an
incorrect
URL
or
IP
address.
Message
Variables:
badurl
-
The
address
that
is
incorrect.
User
Response:
Enter
the
correct
URL
or
IP
address.
GTMFLCI306E
A
parameter
was
entered
with
a
NULL
value
for
this
command
-
parameter
Explanation:
The
setup
command
was
entered
with
a
NULL
parameter
value.
Message
Variables:
parameter
-
The
name
of
the
parameter.
User
Response:
Specify
a
valid
value
and
issue
the
command
again.
GTMFLCI307E
Unable
to
obtain
file
processing
utilities,
stopping...
Explanation:
The
reason
could
be
that
the
file
is
damaged
or
contains
incorrect
characters,
perhaps
due
to
hand-editing
this
file
for
tracing
or
some
other
function.
This
internal
error
indicates
the
file
utilities
cannot
read
the
topxlistener.properties
or
nvid.conf
file.
It
is
possible
that
the
file
has
been
damaged
or
contains
incorrect
characters.
User
Response:
Create
a
new
file.
First,
move
the
file
in
question
to
another
location
or
name.
Then
run
the
command
again
with
the
preferred
parameters
and
their
new
values.
GTMFLCI308E
The
-display
parameter
was
found
with
other
parameters,
it
will
NOT
be
processed.
Explanation:
The
-display
parameter
was
entered
at
the
end
of
a
setup
command
that
contained
other
parameters.
User
Response:
You
cannot
specify
the
-display
parameter
with
other
parameters.
Correct
the
problem
and
run
the
command
again.
148
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
Chapter
14.
IHS
Messages
-
IHS307E
-
IHS829I,
IHS0561I
The
IBM
Tivoli
NetView
for
z/OS
instrumentation
and
discovery
processes
generate
the
following
messages
for
the
components
of
Tivoli
Business
Systems
Manager.
The
help
for
these
messages
is
also
available
from
the
IBM
Tivoli
NetView
for
z/OS
command
facility.
IHS307E
EXECIO
ERROR
ON
ddname
FILE,
RC=return_code
Explanation:
Discovery
processing
found
errors
while
reading
or
writing
information.
Message
Variables:
ddname
-
The
DD
name
of
the
data
set
being
processed
return_code
-
The
return
code
System
Action:
Processing
ends.
Administrator
Response:
This
problem
might
be
caused
by
inadequate
DASD
space
for
the
data
set,
or
a
security
related
error.
Check
the
output
from
the
discovery
job
for
related
error
messages
that
might
give
more
information
about
the
problem.
See
the
z/OS
TSO/E
REXX
Reference
Guide
for
additional
information
on
the
return
code
received
from
the
EXECIO
process.
Correct
any
errors
and
run
the
job
again.
If
you
are
unable
to
determine
the
problem,
contact
IBM
Software
Support.
IHS308E
PARAMETER
MEMBER
ERROR,
parameter
NOT
FOUND.
Explanation:
A
module
has
unsuccessfully
attempted
to
read
a
parameter
member
for
a
resource
being
monitored.
Message
Variables:
parameter
-
The
data
set
and
member
name
combination,
or
the
ddname
and
member
name
combination,
being
processed
System
Action:
An
attempt
will
be
made
to
continue
processing,
but
output
might
be
affected.
Administrator
Response:
Check
that
the
member
exists
in
the
supplied
ddname
or
data
set
name.
If
you
are
unable
to
resolve
this
error,
contact
IBM
Software
Support.
IHS321I
output_text
Explanation:
A
Tivoli
Business
Systems
Manager
user
is
able
to
submit
requests
to
the
host
system
with
the
right-mouse
click
function.
Output
from
these
commands
(or
messages
stating
that
no
values
will
be
output)
is
prefixed
with
IHS321I.
Message
Variables:
output_text
-
The
output
text
received
from
the
host
system
System
Action:
Processing
continues.
Administrator
Response:
There
might
be
instances
where
a
request
to
the
host
system
might
fail
or
return
an
unexpected
response.
Details
of
the
error
should
be
included
in
the
text
that
follows
the
IHS321I
prefix.
Review
these
messages
in
the
appropriate
messages
manual.
Also
check
the
active
NetView
netlog
for
errors.
If
you
are
unable
to
determine
the
problem,
contact
IBM
Software
Support.
IHS332E
IMS_message_text
Explanation:
IMS
rejected
the
command
or
query
that
the
IHSIOTMA
module
sent
to
it
by
returning
an
IMS
message.
The
full
text
of
the
IMS
message
(prefixed
by
DFS)
follows
the
IHS332E
message
prefix.
The
rejection
might
be
an
appropriate
situation.
For
example,
the
configuration
of
IMS
might
not
match
the
query
sent.
Message
Variables:
IMS_message_text
-
This
is
the
full
text
of
the
IMS
message
System
Action:
Tivoli
Business
Systems
Manager
notes
that
no
data
was
returned
from
the
command.
Administrator
Response:
Locate
the
IHS332E
message
within
the
NetView
netlog
and
determine
if
the
IMS
message
received
is
acceptable
or
requires
remedial
action.
If
you
are
unable
to
determine
the
problem,
contact
IBM
Software
Support.
IHS335I
module
WAS
UNABLE
TO
COMMUNICATE
WITH
jobname
USING
OTMA.
Explanation:
The
module
specified
attempted
to
issue
an
IMS
command
to
the
IMS
region
specified
using
the
OTMA
interface,
however
a
return
code
that
was
bad
was
received.
Message
Variables:
module
-
The
module
name
that
encountered
errors
for
IMS
jobname
-
The
job
name
of
the
IMS
Control
Region
System
Action:
Tivoli
Business
Systems
Manager
reports
the
error
for
diagnostic
purposes.
See
associated
©
Copyright
IBM
Corp.
2000,
2004
149
messages
for
further
system
action.
Administrator
Response:
This
is
usually
caused
by
problems
with
the
IMS
OTMA
interface.
Check
the
NetView
netlog
for
other
messages.
Check
that
OTMA
has
been
setup
and
started
correctly
for
the
target
IMS
region.
Contact
IBM
Software
Support
if
you
are
unable
to
resolve
the
problem.
IHS337E
ROUTINE
routine_name
ENCOUNTERED
UNEXPECTED
RETURN
CODE
FROM
subroutine_name,
RC=return_code
Explanation:
The
routine
in
the
message
text
attempted
to
call
the
subroutine_name
and
received
an
unexpected
return
code.
Message
Variables:
routine_name
-
The
name
of
the
routine
subroutine_name
-
The
name
of
the
subroutine
return_code
-
The
return
code:
Return
Code
Condition
0
The
routine
completed
successfully.
4
The
routine
does
not
fully
support
this
release
of
IMS.
Only
minimal
information
was
returned.
8
There
was
an
error
when
creating
some
of
the
REXX
variables.
12
No
parameters
were
provided.
16
The
target
IMS
program
(as
specified
by
IMSID
or
jobname)
was
not
found.
Administrator
Response:
If
you
are
unable
to
resolve
the
problem,
contact
IBM
Software
Support.
IHS338W
ATTEMPT
TO
COMMUNICATE
WITH
AN
IMS
WHOSE
OTMA
IS
DOWN
Explanation:
A
module
was
unable
to
communicate
with
an
IMS
system
that
is
either
down,
or
does
not
have
the
OTMA/CI
interface
active.
System
Action:
Tivoli
Business
Systems
Manager
does
not
receive
any
data
in
response
to
its
query
from
IMS.
Administrator
Response:
The
OTMA/CI
interface
is
probably
not
active,
or
has
not
been
started.
Check
that
it
is
operational
using
the
IMS
/DIS
OTMA
command.
The
OTMA
interface
can
be
started
using
the
IMS
/STA
OTMA
command.
If
the
interface
has
never
been
started,
review
the
IMS
section
in
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide
for
instructions
on
setting
up
the
interface.
If
you
are
unable
to
resolve
this
problem,
contact
IBM
Software
Support.
IHS339E
routine_name
resource
processing_type
PROCESSING
ABANDONED
Explanation:
The
routine
in
the
message
text
received
an
error,
and
has
abandoned
the
processing
specified
for
the
resource.
The
type
of
processing
that
has
been
abandoned
is
indicated
within
the
message
text.
Message
Variables:
routine_name
-
The
name
of
the
routine
resource
-
The
name
of
the
resource
processing_type
-
The
type
of
processing
performed
for
the
resource
System
Action:
Processing
for
this
resource
ends.
Administrator
Response:
See
associated
messages
for
more
information
on
the
problem.
IHS340I
msgstr
Explanation:
This
message
is
issued
by
diagnostic
programs
to
display
various
details
regarding
the
Tivoli
Business
Systems
Manager
instrumentation
environment.
Message
Variables:
msgstr
-
The
message
text
Administrator
Response:
This
message
should
only
occur
when
performing
diagnostic
activities
under
instruction
from
IBM
Software
Support.
IHS343I
IHS$PARM
HAS
BEEN
LOADED
FROM
DSIPARM
Explanation:
This
message
is
issued
from
the
autotask
initialization
task
confirming
that
the
Tivoli
Business
Systems
Manager
Common
Global
Sample
member
IHS$PARM,
and
the
members
included
by
IHS$PARM,
have
been
loaded.
IHS344W
UNINITIALIZED
VALUE
name
USED
IN
module,
JOBNAME=jobname
Explanation:
The
module
attempted
to
access
a
NetView
Common
Global
variable
that
was
not
initialized.
Message
Variables:
name
-
The
name
of
the
variable
module
-
The
name
of
the
module
attempting
to
access
the
variable
jobname
-
The
job
name
of
the
job
for
which
processing
was
undertaken
System
Action:
Processing
ends.
Administrator
Response:
Report
the
problem
to
IBM
Software
Support.
This
problem
might
be
resolved
by
performing
a
mouse-click
rediscovery
of
the
IMS
region
or
by
stopping
and
starting
NetView.
Refer
to
the
IBM
Tivoli
Business
Systems
Manager
Administrator’s
Guide
150
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
before
attempting
to
use
the
IMS
mouse-click
rediscovery
process.
IHS345I
UNEXPECTED
MESSAGE
RECEIVED
BY
module_name,
message_identifier
Explanation:
An
IMS
Event
processing
module
received
a
message
identifier
that
cannot
be
processed.
Message
Variables:
module_name
-
The
name
of
the
IMS
Event
processing
module
message_identifier
-
The
message
identifier
passed
to
the
IMS
Event
processing
module
System
Action:
The
current
message
is
bypassed
and
processing
continues.
Administrator
Response:
Ensure
the
IMS
Message
Automation
Table,
IHSIMAT,
has
been
loaded
and
that
its
contents
are
correct.
IHS346I
IHS$XCMD
opid
module
module_parms
Explanation:
This
message
is
internally
generated
and
is
routed
to
the
internal
routine
IHS$XCMD.
Message
Variables:
opid
-
The
NetView
operator
ID
(must
be
prefixed
by
IHS)
module
-
The
name
of
the
module
(must
be
prefixed
by
IHS)
module_parms
-
The
parameters
to
be
processed
System
Action:
The
message
is
passed
to
the
IHS$XCMD
internal
routine
and
processing
continues.
IHS347E
IHS$XCMD
token
PARAMETER
MUST
BE
PREFIXED
WITH
"IHS"
Explanation:
The
IHS$XCMD
internal
routine
received
incorrectly
formatted
parameters.
Message
Variables:
token
-
The
incorrectly
formatted
parameter
System
Action:
The
request
is
rejected
and
processing
continues.
Administrator
Response:
Review
the
netlog
to
determine
if
the
IHS$XCMD
routine
received
an
incorrectly
formatted
IHS346I
message.
If
not,
contact
IBM
Software
Support.
IHS348E
UNRECOGNIZED
JOB
TYPE,
TYPE=type
IN
module,
JOBNAME=jobname
Explanation:
The
module
attempted
processing
for
a
job,
but
the
job
type
is
not
recognized
or
not
a
valid
type
for
the
process.
Message
Variables:
type
-
The
resource
type
of
the
job
module
-
The
name
of
the
module
that
received
the
message
jobname
-
The
name
of
the
job
being
processed
System
Action:
Processing
by
module
stops.
Administrator
Response:
The
module
has
been
called
for
a
job
for
which
it
was
not
designed.
This
is
probably
due
to
an
incorrect
NetView
setup,
or
errors
during
NetView
startup.
If
you
cannot
identify
the
problem,
contact
IBM
Software
Support.
IHS349I
ALL
resource_type
EXCLUDED,
name
POLL
MONITOR
WILL
NOT
BE
STARTED.
Explanation:
The
administrator
has
excluded
all
resources
of
the
type
indicated
from
monitoring
using
the
IHS$EXCL
SGTMSAMP
member
and
the
IHS#EXCL
utility.
The
named
poll
monitor
will
not
run
as
it
monitors
this
resource
type.
Message
Variables:
resource_type
-
The
type
of
IMS
resource
excluded
(for
example,
database,
transaction,
program)
name
-
The
name
of
the
poll
monitor
System
Action:
The
named
poll
monitor
will
not
run
as
it
monitors
this
resource
type.
Administrator
Response:
If
it
is
intended
that
all
resources
of
this
type
be
excluded,
no
action
needs
to
be
taken.
If
this
is
not
the
case,
review
the
exclude
list
using
the
IHS#EXCL
utility
(described
in
the
IBM
Tivoli
Business
Systems
Manager
Administrator’s
Guide),
and
the
IHS$EXCL
member
in
the
SGTMSAMP
library.
IHS354I
IMS
REGION
name
IS
EXCLUDED
–
PROCESSING
STOPPED
FOR
THIS
REGION.
Explanation:
The
administrator
has
excluded
the
named
IMS
region
using
the
IHS$EXCL
SGTMSAMP
member
and
the
IHS#EXCL
utility.
Message
Variables:
name
-
The
name
of
the
IMS
region
System
Action:
No
event
processing,
polled
processing,
or
discovery
of
the
named
IMS
region
will
occur
until
the
IMS
region
is
removed
from
the
exclude
list.
Administrator
Response:
If
it
is
intended
that
the
IMS
region
is
to
be
excluded,
no
action
needs
to
be
taken.
If
this
is
not
the
case,
review
the
exclude
list
using
the
IHS#EXCL
utility
(described
in
the
IBM
Tivoli
Business
Systems
Manager
Administrator’s
Guide),
and
the
IHS$EXCL
member
in
the
SGTMSAMP
library.
IHS355I
IMS
REGION
name
IS
NO
LONGER
EXCLUDED
–
RE-DISCOVERY
COMMENCING.
Explanation:
The
administrator
has
removed
the
named
IMS
region
from
the
exclude
list
using
the
Chapter
14.
IHS
Messages
-
IHS307E
-
IHS829I,
IHS0561I
151
IHS$EXCL
SGTMSAMP
member
and
the
IHS#EXCL
utility.
Message
Variables:
name
-
The
name
of
the
IMS
region
System
Action:
A
partial
rediscovery
of
the
region
is
commenced.
Processing,
polled
monitoring,
and
event
processing
will
commence
again
at
the
conclusion
of
the
rediscovery.
This
is
described
in
the
IBM
Tivoli
Business
Systems
Manager
Administrator’s
Guide
and
the
IHS$EXCL
member
in
the
SGTMSAMP
library.
IHS356W
IHSIAMB
COULD
NOT
FIND
MODULE
module_name
IN
LIBRARY
name
Explanation:
The
routine
IHSIAMB
attempted
to
get
the
date
and
time
that
the
module
was
bound,
however,
it
was
unable
to
find
the
module
in
the
library
provided.
Message
Variables:
module_name
-
The
name
of
the
module
that
the
IHSIAMB
routine
tried
to
get
the
date
and
time
for
name
-
The
name
of
the
library
System
Action:
Processing
continues,
however
a
full
rediscovery
might
be
run
rather
than
a
(more
efficient)
partial
rediscovery.
Administrator
Response:
This
error
might
impact
performance
and
speed
of
rediscovery.
Check
that
the
named
module
is
in
given
data
set.
If
you
are
unable
to
determine
the
problem,
contact
IBM
Software
Support.
IHS357E
module_name
WAS
NOT
PASSED
CORRECT
PARAMETERS.
Explanation:
The
module_name
was
called,
but
was
not
passed
correct
parameters.
Message
Variables:
module_name
-
The
name
of
the
module
that
did
not
receive
the
correct
parameters
System
Action:
See
associated
messages
for
system
action.
Administrator
Response:
This
usually
indicates
an
internal
error.
If
you
are
unable
to
resolve
error
from
associated
messages,
contact
IBM
Software
Support.
IHS359E
ERROR
OCCURRED
WHEN
routine_name
CALLED
OTMA,
OUTPUT
FROM
OTMA
FOLLOWS:
Explanation:
A
routine
attempted
to
communicate
to
IMS
using
the
OTMA/CI
interface
and
received
an
error.
The
output
received
from
the
attempt
follows
this
message.
Message
Variables:
routine_name
-
The
name
of
the
routine
attempting
to
use
the
OTMA/CI
interface
System
Action:
See
associated
messages
for
system
action.
Administrator
Response:
Confirm
that
the
OTMA/CI
interface
is
configured,
started,
and
available.
Check
that
no
security
violations
occur.
Review
associated
messages
for
further
information.
Refer
to
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide
for
information
on
installing
and
activating
the
OTMA/CI
interface.
If
you
are
unable
to
resolve
the
problem,
contact
IBM
Software
Support.
IHS360I
AO
CONTROLLER
EXIT
IHSIAOEC
INITIALIZED
FOR
IMS
Vv.r.m
type
SYSTEM
imsid
Explanation:
The
Tivoli
Business
Systems
Manager
AO
Controller
Exit
has
been
initialized.
Message
Variables:
v.r.m
-
The
version,
release,
and
modification
level
of
the
IMS
under
which
the
IHSIAOEC
exit
is
running
type
-
The
type
of
IMS,
either
TM/DB,
DCCTL,
or
DBCTL
imsid
-
The
IMS
subsystem
ID
System
Action:
Processing
continues.
IHS361I
SUCCESSFULLY
LOADED
EXIT
CONTROL
TABLE
IHSIAOEE
imsid
Explanation:
The
Exit
Control
Table
has
been
loaded
by
the
Tivoli
Business
Systems
Manager
AO
Controller
Exit.
Message
Variables:
imsid
-
The
IMS
subsystem
ID
System
Action:
Processing
continues.
IHS362E
ERROR
LOADING
EXIT
CONTROL
TABLE
IHSIAOEE
CSRC=return_code
CSRSN=reason_code
imsid
Explanation:
The
Tivoli
Business
Systems
Manager
AO
Controller
Exit
was
not
able
to
load
the
Exit
Control
Table.
Message
Variables:
return_code
-
The
return
code
from
IMS
Callable
Services
reason_code
-
The
reason
code
from
IMS
Callable
Services
imsid
-
The
IMS
subsystem
ID
System
Action:
The
Tivoli
Business
Systems
Manager
AO
Controller
Exit
remains
active,
and
continues
to
be
called
by
IMS,
but
performs
no
action.
Additional
AO
type
2
exits
do
not
get
run.
Tivoli
Business
Systems
Manager
is
not
able
to
capture
all
of
the
expected
IMS
events.
Administrator
Response:
Check
that
the
Exit
Control
Table
has
been
correctly
customized
and
installed,
into
152
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
either
a
load
library
on
the
STEPLIB
of
the
IMS
JCL
procedure,
or
in
the
system
link-list.
For
further
investigation
of
IMS
Callable
Services
return
and
reason
codes,
refer
to
the
IMS
Customization
Guide.
IHS363I
SUCCESSFULLY
LOADED
EXIT
name
imsid
Explanation:
The
Tivoli
Business
Systems
Manager
AO
Controller
Exit
loaded
a
user
specified
exit.
Message
Variables:
name
-
The
name
of
the
user
specified
AO
type
2
exit
imsid
-
The
IMS
subsystem
ID
System
Action:
Tivoli
Business
Systems
Manager
continues
processing.
IHS364E
ERROR
LOADING
EXIT
name
CSRC=return_code
CSRSN=reason_code
imsid
Explanation:
The
Tivoli
Business
Systems
Manager
AO
Controller
Exit
was
not
able
to
load
a
user
specified
exit.
Message
Variables:
name
-
The
name
of
the
user
specified
AO
type
2
exit
return_code
-
The
return
code
from
IMS
Callable
Services
reason_code
-
The
reason
code
from
IMS
Callable
Services
imsid
-
The
IMS
subsystem
ID
System
Action:
The
Tivoli
Business
Systems
Manager
AO
Controller
Exit
disables
this
exit
so
that
it
will
not
be
started.
Administrator
Response:
Check
that
the
user
specified
exit,
as
defined
in
the
Exit
Control
Table,
has
been
correctly
customized
and
installed,
into
either
a
load
library
on
the
STEPLIB
of
the
IMS
JCL
procedure,
or
in
the
system
link-list.
For
further
investigation
of
IMS
Callable
Services
return
and
reason
codes,
refer
to
the
IMS
Customization
Guide.
IHS365E
ERROR
OBTAINING
STORAGE
CSRC
=return_code
CSRSN=reason_code
imsid
Explanation:
The
Tivoli
Business
Systems
Manager
AO
Controller
Exit
was
not
able
to
obtain
storage
for
use
by
a
user-specified
exit.
Message
Variables:
return_code
-
The
return
code
from
IMS
Callable
Services
reason_code
-
The
reason
code
from
IMS
Callable
Services
imsid
-
The
IMS
subsystem
ID
System
Action:
The
Tivoli
Business
Systems
Manager
AO
Controller
Exit
disables
this
exit,
and
it
does
not
start.
Administrator
Response:
Check
IMS
for
indications
of
a
storage
shortage.
For
further
investigation
of
IMS
Callable
Services
return
and
reason
codes,
refer
to
the
IMS
Customization
Guide.
IHS366I
interval_name
INTERVAL
IS
0
FOR
region
–
POLL
MONITOR
DISABLED.
Explanation:
The
interval
for
a
particular
poll
monitor
has
been
set
to
a
value
of
0.
This
value
disables
the
poll
monitor.
Message
Variables:
interval_name
-
The
name
of
the
interval
set
to
a
value
of
0
region
-
The
name
of
the
region
to
be
monitored,
which
is
usually
an
IMS
subsystem
System
Action:
The
poll
monitor
is
disabled.
IHS367W
SYSTEM
CONTENTS
DIRECTORY
(SCD)
COULD
NOT
BE
DISCOVERED
imsid
Explanation:
The
Tivoli
Business
Systems
Manager
AO
Controller
Exit
was
not
able
to
find
the
IMS
System
Contents
Directory
(SCD)
control
block.
Message
Variables:
imsid
-
The
IMS
subsystem
ID
System
Action:
Tivoli
Business
Systems
Manager
AO
Controller
Exit
uses
default
IMS
settings
for
WTO
descriptor
and
routing
codes.
Administrator
Response:
Check
that
IMS
has
initialized
correctly
and,
if
so,
contact
IBM
Software
Support.
IHS368E
UNABLE
TO
LOAD
IHSMKEY
FILTER
PROGRAM
Explanation:
An
exit
program
has
attempted
to
load
the
IHSMKEY
Filter
program,
and
the
LOAD
service
has
returned
a
non-zero
return
code.
System
Action:
The
exit
program
performs
no
further
processing
for
this
job
event.
The
load
is
attempted
again
for
the
next
job
event.
Administrator
Response:
Check
that
the
IHSMKEY
Filter
program
has
been
correctly
installed,
into
either
a
load
library
on
the
STEPLIB
for
this
address
space,
or
in
the
system
link-list.
For
further
details,
refer
to
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide.
Chapter
14.
IHS
Messages
-
IHS307E
-
IHS829I,
IHS0561I
153
IHS369E
UNABLE
TO
DELETE
IHSMKEY
FILTER
PROGRAM
Explanation:
An
exit
program
has
attempted
to
unload
the
IHSMKEY
Filter
program,
and
the
DELETE
service
has
returned
a
non-zero
return
code.
Each
occurrence
of
this
message
indicates
the
creation
of
an
orphaned
copy
of
the
IHSMKEY
Filter
program
within
this
address
space,
which
increases
storage
use
within
this
address
space.
System
Action:
The
exit
program
continues
processing
for
this
job
event.
The
unload
is
attempted
again
for
the
next
job
event.
Administrator
Response:
This
message
indicates
a
possible
problem
with
this
address
space.
Contact
your
administrator.
IHS370I
AO
EXIT
IHSIAOE0
INITIALIZED
FOR
IMS
Vv.r.m
type
SYSTEM
imsid
Explanation:
The
Tivoli
Business
Systems
Manager
AO
Exit
was
initialized.
Message
Variables:
v.r.m
-
The
version,
release,
and
modification
level
of
the
IMS
under
which
IHSIAOE0
is
executing
type
-
The
type
of
IMS,
either
TM/DB,
DCCTL,
or
DBCTL
imsid
-
The
IMS
subsystem
ID
System
Action:
Tivoli
Business
Systems
Manager
continues
processing.
IHS371I
SUCCESSFULLY
LOADED
MESSAGE
TABLE
IHSIAOEM
imsid
Explanation:
The
Tivoli
Business
Systems
Manager
AO
Exit
has
successfully
loaded
the
message
table.
Message
Variables:
imsid
-
The
IMS
subsystem
ID
System
Action:
Tivoli
Business
Systems
Manager
continues
processing.
IHS372E
ERROR
LOADING
MESSAGE
TABLE
IHSIAOEM,
CSRC
=return_code
CSRSN=reason_code
imsid
Explanation:
The
Tivoli
Business
Systems
Manager
AO
Exit
was
not
able
to
load
its
Message
Table.
Message
Variables:
return_code
-
The
return
code
from
IMS
Callable
Services
reason_code
-
The
reason
code
from
IMS
Callable
Services
imsid
-
The
IMS
subsystem
ID
System
Action:
The
Tivoli
Business
Systems
Manager
AO
Exit
remains
active,
continues
to
be
called
by
the
IMS
service,
and
performs
IMS
command
captures,
but
does
not
perform
any
IMS
MTO
message
captures.
Tivoli
Business
Systems
Manager
is
not
able
to
capture
all
of
the
expected
IMS
events.
Administrator
Response:
Check
that
the
Message
Table
has
been
correctly
installed,
into
either
a
load
library
on
the
STEPLIB
of
the
IMS
JCL
procedure,
or
in
the
system
link-list.
For
further
investigation
of
IMS
Callable
Services
return
and
reason
codes,
refer
to
the
IMS
Customization
Guide.
IHS373I
DETECTED
/MODIFY
PREPARE
ACBLIB
FOR
subsys
Explanation:
This
is
an
informational
message.
The
Tivoli
Business
Systems
Manager
AO
Exit
has
detected
that
the
operator
has
entered
a
MODIFY
command.
Message
Variables:
subsys
-
The
subsystem
name
of
the
IMS
system
System
Action:
Tivoli
Business
Systems
Manager
takes
note
of
these
commands
for
information
purposes.
IHS374I
DETECTED
/MODIFY
PREPARE
MODBLKS
FOR
subsys
Explanation:
This
is
an
informational
message.
The
Tivoli
Business
Systems
Manager
AO
Exit
has
detected
that
the
operator
has
entered
a
MODIFY
command.
Message
Variables:
subsys
-
The
subsystem
name
of
the
IMS
system
System
Action:
Tivoli
Business
Systems
Manager
takes
note
of
these
commands
for
information
purposes.
IHS375I
DETECTED
/MODIFY
COMMIT
FOR
subsys
Explanation:
This
is
an
informational
message.
The
Tivoli
Business
Systems
Manager
AO
Exit
has
detected
that
the
operator
has
entered
a
MODIFY
command.
Message
Variables:
subsys
-
The
subsystem
name
of
the
IMS
system
System
Action:
Tivoli
Business
Systems
Manager
takes
note
of
these
commands
for
information
purposes.
IHS376I
DETECTED
command
FOR
subsys
Explanation:
This
is
an
informational
message.
The
Tivoli
Business
Systems
Manager
IMS
AO
Exit
has
detected
that
the
operator
has
entered
an
IMS
command.
Message
Variables:
command
-
The
name
of
the
detected
command
subsys
-
The
subsystem
name
of
the
IMS
system
154
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
System
Action:
Tivoli
Business
Systems
Manager
takes
note
of
these
commands.
IHS377W
SYSTEM
CONTENTS
DIRECTORY
(SCD)
COULD
NOT
BE
DISCOVERED
imsid
Explanation:
The
Tivoli
Business
Systems
Manager
AO
Exit
was
not
able
to
find
the
IMS
System
Contents
Directory
control
block.
Message
Variables:
imsid
-
The
IMS
subsystem
ID
System
Action:
The
Tivoli
Business
Systems
Manager
AO
Exit
uses
default
IMS
settings
for
WTO
descriptor
and
routing
codes.
Administrator
Response:
Check
that
IMS
has
initialized
correctly
and,
if
so,
contact
IBM
Software
Support.
IHS378E
UNABLE
TO
LOAD
AOPEDI
PROGRAM.
Explanation:
An
exit
program
has
attempted
to
load
the
AOPEDI
program
and
the
LOAD
service
has
returned
a
non-zero
return
code.
System
Action:
The
exit
program
performs
no
further
processing
for
this
job
event.
The
load
is
attempted
again
for
the
next
job
event.
Administrator
Response:
Check
that
the
AOPEDI
EDI
program
has
been
correctly
made
available,
by
adding
the
SGTMMODS
load
library
to
either
the
STEPLIB
for
this
address
space,
or
to
the
system
link-list.
For
further
details,
refer
to
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide.
IHS379E
UNKNOWN
TYPE-OF-CALL
INDICATOR
RECEIVED.
Explanation:
An
exit
program
has
been
run
with
an
unexpected
Type-Of-Call
indicator.
This
might
indicate
an
unsupported
version
or
configuration
of
the
CONTROL-M
for
OS/390
program.
System
Action:
The
exit
program
performs
no
further
processing
for
this
invocation.
Administrator
Response:
Contact
IBM
Software
Support.
IHS380E
EXECIO
FOR
FILE
ddname
FAILED
WITH
RC=return_code
Explanation:
The
EXECIO
service
has
failed
while
attempting
to
perform
I/O
to
the
specified
file.
Message
Variables:
ddname
-
The
DD
name
or
dataset
name
against
which
the
EXECIO
service
failed
return_code
-
The
REXX
return
code
from
the
EXECIO
service
System
Action:
The
current
function
ends.
Administrator
Response:
This
might
be
caused
by
inadequate
DASD
space
for
the
file,
or
a
security
related
error.
Check
the
z/OS
system
log
for
other
error
messages
that
might
give
more
information
about
the
problem.
Additional
information
on
this
error
can
be
obtained
by
looking
up
the
return_code
from
the
EXECIO
service
in
the
z/OS
TSO/E
REXX
Reference
Guide.
If
you
are
unable
to
determine
the
problem,
contact
IBM
Software
Support
IHS390E
CALL
TO
IEFSSI
FAILED
WITH
RC=return_code
RSN=reason_code
Explanation:
The
MVS
IEFSSI
service
has
set
a
non-zero
return
code.
Message
Variables:
return_code
-
The
return
code
from
the
MVS
IEFSSI
service
reason_code
-
The
reason
code
from
the
MVS
IEFSSI
service
System
Action:
The
IHSBINIT
program
sets
a
return
code
of
4,
issues
message
number
IHS583W,
and
continues
processing.
Administrator
Response:
Report
the
problem
to
IBM
Software
Support.
IHS391E
CALL
TO
IEFSSI
RETURNED
INCOMPLETE
DATA
Explanation:
The
IEFSSI
service
did
not
return
all
the
expected
data.
System
Action:
The
IHSBINIT
program
sets
a
return
code
of
4,
issues
message
number
IHS583W
and
continues
processing.
Administrator
Response:
Report
the
problem
to
IBM
Software
Support.
IHS392I
DB2PM=value
Explanation:
The
IHSBPMCH
program
has
determined
the
availability
of
DB2PM
for
a
subsystem.
Message
Variables:
value
-
The
availability
of
DB2PM
for
this
subsystem
(YES
or
NO)
IHS394E
name
DSIGET
FAILURE
Explanation:
An
assembler
routine
received
a
non-zero
return
code
from
DSIGET.
Message
Variables:
name
-
The
name
of
the
assembler
routine
System
Action:
Issues
a
secondary
message.
Administrator
Response:
The
REXX
program
that
called
the
assembler
routine
issues
another
message.
Perform
the
actions
recommended
for
that
message.
Chapter
14.
IHS
Messages
-
IHS307E
-
IHS829I,
IHS0561I
155
IHS395E
THE
DB2
SUBSYSTEM
NAME
MUST
BE
1
TO
4
CHARACTERS
LONG
Explanation:
The
subsystem
name
passed
to
the
IHSBFIND
program
was
not
1
–
4
characters
in
length.
System
Action:
Issues
a
secondary
message.
Administrator
Response:
The
REXX
program,
which
called
the
assembler
routine,
issues
another
message.
Perform
the
actions
recommended
for
that
message.
IHS396E
CONNECT
TO
DB2
SUBSYSTEM
name
FAILED.
RETURN
CODES
return_code
reason_code
Explanation:
The
IHSBFIND
program
was
unable
to
connect
to
the
DB2
subsystem.
Message
Variables:
name
-
The
DB2
subsystem
name
return_code
-
The
return
code
from
DB2
interface
that
is
called
by
the
IHSBIFIC
program
reason_code
-
The
reason
code
from
DB2
interface
that
is
called
by
the
IHSBIFIC
program
System
Action:
Issues
a
secondary
message.
Administrator
Response:
The
REXX
program
that
called
the
assembler
routine
issues
another
message.
Perform
the
actions
recommended
for
that
message.
IHS397E
CALL
TO
DB2
DSNWLI
FAILED.
DB2
RETURN
CODES
return_code
reason_code
Explanation:
The
IHSBFIND
program
was
unable
to
call
the
DSNWLI
linkedit
step.
Message
Variables:
return_code
-
The
return
code
from
DB2
interface
that
is
called
by
the
IHSBIFIC
program
reason_code
-
The
reason
code
from
DB2
interface
that
is
called
by
the
IHSBIFIC
program
System
Action:
Issues
a
secondary
message.
Administrator
Response:
Probable
configuration
error.
Refer
to
the
DB2
Messages
and
Codes
manual
for
an
explanation
of
the
return
code
and
reason
code,
which
will
indicate
which
configuration
step
was
unsuccessful.
IHS398E
CALL
TO
DB2
IFI
FAILED.
DB2
RETURN
CODES
return_code
reason_code
Explanation:
The
program
was
unable
to
call
the
DB2
interface
that
is
called
by
the
IHSBIFIC
program.
Message
Variables:
return_code
-
The
return
code
from
DB2
interface
that
is
called
by
the
IHSBIFIC
program
reason_code
-
The
reason
code
from
DB2
interface
that
is
called
by
the
IHSBIFIC
program
System
Action:
Issues
a
secondary
message.
Administrator
Response:
The
REXX
program
that
called
the
assembler
routine
issues
another
message.
Perform
the
actions
recommended
for
that
message.
IHS399I
VER=version
DISTSTAT=status
SPAS=name
SPASSTAT=status
IRLM=name
IRLMSTAT=status
IRLMSSID=subsys_id
VCAT=qualifier
Explanation:
The
IHSBFIND
program
has
extracted
a
number
of
informational
fields
related
to
a
DB2
subsystem.
Message
Variables:
version
-
The
DB2
version
status
-
The
status
of
the
DIST
address
space
name
-
The
name
of
the
SPAS
address
space
status
-
The
status
of
the
SPAS
address
space
name
-
The
name
of
the
IRLM
address
space
status
-
The
status
of
the
IRLM
address
space
subsys_id
-
The
SSID
of
the
IRLM
address
space
qualifier
-
The
VCAT
qualifier
for
the
subsystem
IHS402I
debug_text
Explanation:
This
message
is
issued
in
DEBUG
mode
to
display
diagnostic
internal
data
and
is
only
for
use
by
IBM
Software
Support.
IHS403I
module
name
NOT
KNOWN
TO
TIVOLI
BUSINESS
SYSTEMS
MANAGER.
Explanation:
The
module
attempted
to
access
a
resource
that
is
not
known
(for
example,
has
not
yet
been
discovered)
by
Tivoli
Business
Systems
Manager.
Message
Variables:
module
-
The
module
name
name
-
The
resource
name
System
Action:
Processing
continues.
Administrator
Response:
This
is
usually
caused
by
a
previous
error
during
discovery,
and
might
be
resolved
by
performing
a
mouse-click
rediscovery.
Refer
to
the
IBM
Tivoli
Business
Systems
Manager
Administrator’s
Guide
before
attempting
to
use
the
IMS
mouse-click
rediscovery
process.
IHS404I
PROGRAM
program_name
IS
program_state
Explanation:
The
IMS
Program
poll
monitor
has
detected
that
an
IMS
program
is
in
a
restricted
state.
Message
Variables:
program_name
-
The
program
name
program_state
-
The
state
of
the
program.
This
will
be
either
IN
RESTRICTED
STATE
or
NOW
AVAILABLE.
System
Action:
For
a
state
of
IN
RESTRICTED
STATE,
156
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
an
exception
event
for
the
program
is
sent
to
Tivoli
Business
Systems
Manager
and
processing
continues.
For
a
state
of
NOW
AVAILABLE,
a
resolution
event
for
the
program
is
sent
to
Tivoli
Business
Systems
Manager
and
processing
continues.
Administrator
Response:
If
this
is
an
error,
determine
why
the
program
is
in
a
restricted
state
and
take
appropriate
action.
You
can
use
the
IMS
/DIS
STATUS
PROGRAM
command
to
display
the
status
of
an
IMS
program.
IHS405I
TRANSACTION
transaction_name
IS
transaction_state
Explanation:
The
IMS
Transaction
Poll
Monitor
has
detected
that
an
IMS
transaction
is
in
a
restricted
state.
Message
Variables:
transaction_name
-
The
transaction
name
transaction_state
-
The
state
of
the
transaction.
This
will
be
either
IN
RESTRICTED
STATE
or
NOW
AVAILABLE.
System
Action:
For
a
state
of
IN
RESTRICTED
STATE,
an
exception
event
for
the
transaction
is
sent
to
Tivoli
Business
Systems
Manager
and
processing
continues.
For
a
state
of
NOW
AVAILABLE,
a
resolution
event
for
the
transaction
is
sent
to
Tivoli
Business
Systems
Manager
and
processing
continues.
Administrator
Response:
If
this
is
an
error,
determine
why
the
transaction
is
in
a
restricted
state
and
take
appropriate
action.
You
can
use
the
IMS
/DIS
STATUS
TRAN
command
to
display
the
status
of
an
IMS
transaction.
IHS406I
DATABASE
database_name
IS
database_state
Explanation:
The
IMS
Database
Poll
Monitor
has
detected
that
an
IMS
Database
is
in
a
restricted
state.
Message
Variables:
database_name
-
The
database
name
database_state
-
The
state
of
the
database.
This
will
be
either
IN
RESTRICTED
STATE
or
NOW
AVAILABLE.
System
Action:
For
a
state
of
IN
RESTRICTED
STATE,
an
exception
event
for
the
database
is
sent
to
Tivoli
Business
Systems
Manager
and
processing
continues.
For
a
state
of
NOW
AVAILABLE,
a
resolution
event
for
the
database
is
sent
to
Tivoli
Business
Systems
Manager
and
processing
continues.
Administrator
Response:
If
this
is
an
error,
determine
why
the
database
is
in
a
restricted
state
and
take
appropriate
action.
You
can
use
the
IMS
/DIS
STATUS
DBS
command
to
display
the
status
of
an
IMS
database.
IHS407I
AREA
area_name
IS
area_state
Explanation:
The
IMS
Database
Poll
Monitor
has
detected
that
an
IMS
AREA
is
in
a
restricted
state.
Message
Variables:
area_name
-
The
area
name
area_state
-
The
state
of
the
area.
This
will
be
either
IN
RESTRICTED
STATE
or
NOW
AVAILABLE.
System
Action:
For
a
state
of
IN
RESTRICTED
STATE,
an
exception
event
for
the
area
is
sent
to
Tivoli
Business
Systems
Manager
and
processing
continues.
For
a
state
of
NOW
AVAILABLE,
a
resolution
event
for
the
area
is
sent
to
Tivoli
Business
Systems
Manager
and
processing
continues.
Administrator
Response:
If
this
is
an
error,
determine
why
the
Area
is
in
a
restricted
state
and
take
appropriate
action.
You
can
use
the
IMS
/DIS
STATUS
DBS
command
to
display
the
status
of
an
IMS
Area.
IHS408I
MTO
mto_name
IS
mto_state
Explanation:
The
IMS
MTO
Poll
Monitor
has
detected
that
the
IMS
Primary
or
Secondary
MTO
(Master
Terminal
Operator)
device
is
in
a
restricted
state.
Message
Variables:
mto_name
-
The
MTO
device
name
mto_state
-
The
state
of
the
MTO
device.
This
will
be
either
IN
RESTRICTED
STATE
or
NOW
AVAILABLE.
System
Action:
For
a
state
of
IN
RESTRICTED
STATE,
an
exception
event
for
the
primary
or
secondary
MTO
device
is
sent
to
Tivoli
Business
Systems
Manager
and
processing
continues.
For
a
state
of
NOW
AVAILABLE,
a
resolution
event
for
the
primary
or
secondary
MTO
device
is
sent
to
Tivoli
Business
Systems
Manager
and
processing
continues.
Administrator
Response:
If
this
is
an
error,
determine
why
the
IMS
Primary
or
Secondary
MTO
device
is
in
a
restricted
state
and
take
appropriate
action.
You
can
use
the
IMS
/DIS
MASTER
command
to
display
the
assigned
IMS
Primary
and
Secondary
MTO
devices.
IHS409I
TRANSACTION
QUEUE
tran_queue
queue_status
THRESHOLD
tran_threshold
Explanation:
The
transaction
queue
poll
monitor
has
detected
that
the
number
of
queued
transactions
for
the
IMS
region
threshold
(obtained
by
looking
at
the
output
from
the
/DIS
Q
TRANSACTION
and
/DIS
Q
BALGRP
commands)
exceeds
one
of
the
following
values:
v
The
threshold
specified
by
the
Tivoli
Business
Systems
Manager
console.
v
If
no
threshold
has
been
specified
for
the
IMS
region,
then
the
IHSI.$TXQLEN
value
in
the
IHSIPRM
member
in
the
SGTMSAMP
data
set,
or
by
way
of
an
override
in
the
IHS$UPRM
member.
Chapter
14.
IHS
Messages
-
IHS307E
-
IHS829I,
IHS0561I
157
Message
Variables:
tran_queue
-
The
number
of
transactions
on
the
input
queue
queue_status
-
The
status
of
the
transaction
input
queue.
A
status
of
EXCEED
indicates
that
the
number
of
transactions
queued
exceeds
the
threshold.
A
status
of
WITHIN
indicates
that
the
number
of
transactions
queued
has
fallen
below
the
threshold.
tran_threshold
-
The
threshold
for
the
number
of
transactions
on
the
input
queue
System
Action:
An
exception
event
is
sent
to
Tivoli
Business
Systems
Manager
and
processing
continues.
For
the
status
EXCEED,
an
exception
event
is
sent
to
Tivoli
Business
Systems
Manager
and
processing
continues.
For
the
status
WITHIN,
a
resolution
event
is
sent
to
Tivoli
Business
Systems
Manager
and
processing
continues.
Administrator
Response:
If
this
is
not
an
error,
modify
the
transaction
queue
threshold
using
the
Tivoli
Business
Systems
Manager
console,
or
modify
the
threshold
for
all
IMS
regions
by
adding
the
IHSI.$TXQLEN
parameter
with
the
required
value
to
IHS$UPRM
member
in
the
SGTMSAMP
data
set.
To
introduce
the
changed
values
prior
to
the
next
NetView
startup,
issue
the
IHS$PRMU
REFRESH
command
from
an
NCCF
session.
For
details
of
the
IHS$PRMU
command,
refer
to
the
prolog
of
the
IHS$UPRM
member
in
SGTMSAMP.
For
further
details
regarding
the
IHSI.$TXQLEN
parameter,
refer
to
the
prolog
that
precedes
this
parameter
in
the
IHSIPRM
member
in
SGTMSAMP.
The
IHSIPRM
member
in
SGTMSAMP
contains
the
default
parameter
settings
for
the
IMS
data
source,
as
supplied
with
Tivoli
Business
Systems
Manager.
This
member
should
not
be
changed
IHS410I
buffer
Explanation:
This
message
prefixes
all
IMS
command
response
buffers
output
from
the
OTMA
CI
interface.
Message
Variables:
buffer
-
The
IMS
command
response
buffer
IHS411E
IHSIOTMA
FAILED
IN
THE
subroutine
ROUTINE
WITH
RETRSN=
ret_rsn1
ret_rsn2
ret_rsn3
ret_rsn4
ret_rsn5
Explanation:
This
is
a
diagnostic
message
indicating
that
an
attempt
to
communicate
with
an
IMS
subsystem
by
way
of
the
IHSIOTMA
interface
has
failed.
The
message
text
contains
the
name
of
the
IHSIOTMA
subroutine
that
failed,
followed
by
up
to
five
full
words
(in
hexadecimal)
containing
internal
return
codes
or
reason
codes.
Message
Variables:
subroutine
-
The
name
of
the
subroutine
called
by
the
IHSIOTMA
interface
ret_rsn1
—
ret_rsn5
-
The
words
containing
a
return
or
reason
code
System
Action:
Tivoli
Business
Systems
Manager
reports
the
error
for
diagnostic
purposes.
See
associated
messages
for
further
system
action.
Administrator
Response:
This
is
usually
caused
by
problems
with
the
IMS
OTMA
interface.
Check
the
NetView
netlog
for
other
messages.
Check
the
IMS
Secondary
MTO
device
for
the
target
IMS
region
for
other
messages.
Check
that
the
OTMA
interface
has
been
setup
and
started
correctly
for
the
target
IMS
region.
Contact
IBM
Software
Support
if
you
are
unable
to
resolve
the
problem.
IHS413E
RC20
FROM
IMS
WITHOUT
DFS™
MESSAGE
Explanation:
IMS
returned
a
code
of
20
(error
condition)
in
response
to
an
attempt
to
send
a
command
to
IMS
using
the
OTMA
interface,
but
did
not
provide
an
IMS
message
(prefixed
by
DFS)
to
indicate
the
cause
of
the
IMS
error.
System
Action:
Tivoli
Business
Systems
Manager
reports
the
error
for
diagnostic
purposes.
Administrator
Response:
This
is
usually
caused
by
problems
with
the
IMS
OTMA
interface.
Check
the
NetView
netlog
for
message
numbers
IHS332E,
IHS410I,
IHS411E,
and
IHS426E.
Check
the
IMS
Secondary
MTO
device
for
the
target
IMS
region
for
other
messages.
Check
that
the
OTMA
interface
has
been
set
up
and
started
correctly
for
the
target
IMS
region.
If
you
are
unable
to
resolve
the
problem,
contact
IBM
Software
Support.
IHS415I
MSC
msc_link
IS
msc_link_state
Explanation:
The
MSC
poll
monitor
detected
that
an
IMS
MSC
(Multi-Systems
Coupling)
link
is
in
a
restricted
state.
Message
Variables:
msc_link
-
The
MSC
link
number
msc_link_state
-
The
state
of
the
MSC
link.
This
is
either
IN
RESTRICTED
STATE
or
NOW
AVAILABLE.
System
Action:
For
a
state
of
IN
RESTRICTED
STATE,
an
exception
event
for
the
MSC
link
is
sent
to
Tivoli
Business
Systems
Manager
and
processing
continues.
For
a
state
of
NOW
AVAILABLE,
a
resolution
event
for
the
MSC
link
is
sent
to
Tivoli
Business
Systems
Manager
and
processing
continues.
Administrator
Response:
If
this
is
an
error,
determine
why
the
MSC
link
is
in
a
restricted
state
and
take
appropriate
action.
You
can
use
the
IMS
/DIS
STATUS
LINK
command
to
display
the
status
of
the
MSC
links.
158
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
IHS416I
RE-DISCOVERY
(type)
FOR
(jobname/subsystem)
ACCEPTED.
Explanation:
This
message
is
issued
when
a
discovery
is
requested
for
an
IMS
system.
Message
Variables:
type
-
The
type
of
rediscovery
requested.
Valid
types
are
FULL
and
PARTIAL.
jobname
-
The
job
name
of
the
IMS
control
region
subsystem
-
The
SSID
(subsystem
identifier)
of
the
IMS
subsystem
IHS417E
IHSMSG
IN
module
FAILED
WITH
RC=return_code
EVENTID=message_id
Explanation:
A
call
to
the
IHSMSG
routine
returned
a
non-zero
return
code.
Message
Variables:
module
-
The
module
name
return_code
-
The
return
code
returned
by
the
IHSMSG
routine
message_id
-
The
message
identifier
passed
to
the
IHSMSG
routine
System
Action:
The
event
is
not
sent
to
the
source/390
object
pump
and
processing
continues.
Administrator
Response:
Report
the
error
message
to
IBM
Software
Support.
IHS420I
AVAILABLE
LOGS
BELOW
THRESHOLD
Explanation:
The
number
of
available
IMS
logs
is
below
the
threshold
specified
by
the
Tivoli
Business
Systems
Manager
console,
or
if
no
threshold
has
been
specified
for
the
IMS
region,
the
IHSI.$LOGAVAIL
value
in
the
IHSIPRM
member
in
the
SGTMSAMP
data
set
or
by
way
of
an
override
in
the
IHS$UPRM
member.
System
Action:
An
exception
event
for
the
IMS
system
is
sent
to
Tivoli
Business
Systems
Manager
and
processing
continues.
Administrator
Response:
The
number
of
available
logs
can
be
determined
by
analyzing
the
output
from
an
IMS
/DIS
OLDS
command.
If
this
is
not
an
error,
modify
the
IMS
log
threshold
using
the
Tivoli
Business
Systems
Manager
console,
or
modify
the
threshold
for
all
IMS
regions
by
adding
the
IHSI.$LOGAVAIL
parameter
to
the
IHS$UPRM
member
in
the
SGTMSAMP
data
set.
To
introduce
the
changed
values
prior
to
the
next
NetView
startup,
issue
the
IHS$PRMU
REFRESH
command
from
an
NCCF
session.
For
details
of
the
IHS$PRMU
command,
refer
to
the
prolog
of
the
IHS$UPRM
member
in
SGTMSAMP.
For
further
details
regarding
the
IHSI.$LOGAVAIL
parameter,
refer
to
the
prolog
that
precedes
this
parameter
in
the
IHSIPRM
member
in
SGTMSAMP.
The
IHSIPRM
member
in
SGTMSAMP
contains
the
default
parameter
settings
for
the
IMS
data
source,
as
supplied
with
Tivoli
Business
Systems
Manager.
This
member
should
not
be
changed.
IHS421I
AVAILABLE
LOGS
ABOVE
THRESHOLD
Explanation:
The
number
of
available
IMS
logs
has
exceeded
the
threshold
specified
by
the
Tivoli
Business
Systems
Manager
console,
or
if
no
threshold
has
been
specified
for
the
IMS
region,
the
IHSI.$LOGAVAIL
parameter
in
the
IHSIPRM
member
in
the
SGTMSAMP
data
set,
or
by
way
of
an
override
in
the
IHS$UPRM
member.
System
Action:
A
resolution
event
for
the
IMS
system
is
sent
to
Tivoli
Business
Systems
Manager
and
processing
continues.
Administrator
Response:
The
IHSIPRM
member
contains
the
default
parameter
settings
for
the
IMS
data
source,
as
supplied
with
Tivoli
Business
Systems
Manager,
this
member
should
not
be
changed.
To
override
the
default
parameter
settings
within
IHSIPRM
add
the
parameter,
with
the
required
value,
into
the
IHS$UPRM
override
member
within
the
SGTMSAMP
data
set.
To
introduce
the
changed
values
prior
to
the
next
NetView
startup,
issue
the
IHS$PRMU
REFRESH
command
from
an
NCCF
session.
For
details
of
the
IHS$PRMU
command,
refer
to
the
prolog
of
the
IHS$UPRM
member
in
SGTMSAMP.
For
further
details
regarding
the
IHSI.$LOGAVAIL
parameter,
refer
to
the
prolog
that
precedes
this
parameter
in
the
IHSIPRM
member
in
SGTMSAMP.
IHS422I
LOG
ARCHIVE
DURATION
ABOVE
THRESHOLD
Explanation:
An
IMS
Log
Archive
job
did
not
complete
within
the
time
limit
set
in
Tivoli
Business
Systems
Manager.
System
Action:
An
exception
event
for
the
IMS
system
is
sent
to
Tivoli
Business
Systems
Manager
and
processing
continues.
Administrator
Response:
This
usually
indicates
that
an
error
occurred
in
the
log
archive
job,
or
the
job
was
prevented
from
processing.
Look
at
the
output
from
the
log
archive
job
to
determine
if
any
errors
occurred.
If
there
is
no
error
(for
example,
the
log
archive
job
is
still
running),
increase
the
IMS
log
archive
duration
threshold
using
the
Tivoli
Business
Systems
Manager
console,
or
modify
the
threshold
for
all
IMS
regions
by
adding
the
IHSI.$ARCHTIME
parameter
to
the
IHS$UPRM
member
in
the
SGTMSAMP
data
set.
To
introduce
the
changed
values
prior
to
the
next
NetView
startup,
issue
the
IHS$PRMU
REFRESH
command
from
an
NCCF
session.
For
details
of
the
IHS$PRMU
command,
refer
to
the
prolog
of
the
IHS$UPRM
member
in
SGTMSAMP.
Chapter
14.
IHS
Messages
-
IHS307E
-
IHS829I,
IHS0561I
159
The
IHSIPRM
member
in
SGTMSAMP
contains
the
default
parameter
settings
for
the
IMS
data
source,
as
supplied
with
Tivoli
Business
Systems
Manager.
This
member
should
not
be
changed.
For
further
details
regarding
the
IHSI.$ARCHTIME
parameter,
refer
to
the
prolog
that
precedes
this
parameter
in
the
IHSIPRM
member
in
SGTMSAMP.
IHS423I
LOG
ARCHIVE
DURATION
BELOW
THRESHOLD
Explanation:
Tivoli
Business
Systems
Manager
has
detected
the
successful
completion
of
an
IMS
Log
Archive
job.
System
Action:
A
resolution
event
for
the
IMS
system
is
sent
to
Tivoli
Business
Systems
Manager
and
processing
continues.
Administrator
Response:
This
occurs
after
an
IHS422I
message
is
issued.
See
the
IHS422I
message
description
for
more
information.
IHS426E
OTMA
TIMED
OUT
module
jobname
Explanation:
This
message
is
issued
when
the
time
taken
to
complete
an
IMS
command,
using
the
IHSIOTMA
module,
exceeds
the
allowed
time
limit.
Message
Variables:
module
-
The
name
of
the
module
that
started
the
IHSIOTMA
module
jobname
-
The
job
name
of
the
IMS
Control
Region
Administrator
Response:
Ensure
the
IMS
control
region
with
which
the
NetView
program
is
attempting
to
communicate
is
up
and
has
the
OTMA
interface
started.
If
the
message
occurs
repeatedly,
add
the
IHSI.OTMA.TIMEOUT
parameter
to
the
IHS$UPRM
member
in
the
SGTMSAMP
data
set
with
an
increased
value.
To
introduce
the
changed
values
prior
to
the
next
NetView
startup,
issue
the
IHS$PRMU
REFRESH
command
from
an
NCCF
session.
For
details
of
the
IHS$PRMU
command,
refer
to
the
prolog
of
the
IHS$UPRM
member
in
SGTMSAMP.
The
IHSIPRM
member
in
SGTMSAMP
contains
the
default
parameter
settings
for
the
IMS
data
source,
as
supplied
with
Tivoli
Business
Systems
Manager.
This
member
should
not
be
changed.
For
further
details
regarding
the
IHSI.OTMA.TIMEOUT
parameter,
refer
to
the
prolog
that
precedes
this
parameter
in
the
IHSIPRM
member
in
SGTMSAMP.
If
this
does
not
resolve
the
problem,
contact
IBM
Software
Support.
IHS427E
module
HAS
DETECTED
NULL
variable
FOR
subsystem
Explanation:
This
message
is
issued
when
a
module
detects
that
the
content
of
the
specified
variable
is
null.
Message
Variables:
module
-
The
name
of
the
module
variable
-
The
name
of
the
variable
that
contains
nulls
subsystem
-
The
job
name
of
the
subsystem
or
the
subsystem
name
Administrator
Response:
This
message
indicates
a
module
has
unsuccessfully
attempted
to
retrieve
information
from
either
a
NetView
function
or
a
NetView
global
variable.
Review
the
NetView
netlog
for
related
messages.
If
you
are
unable
to
determine
the
cause
of
the
problem,
contact
IBM
Software
Support.
When
the
variable
value
is
either
XCFGRP
or
XCFMEM,
it
indicates
the
XCF
parameters
for
an
IHSIOTMA
call
are
incomplete.
The
IHSIOTMA
module
is
unable
to
communicate
with
an
IMS
subsystem
unless
both
the
XCF
Group
name
and
XCF
Member
name
of
the
IMS
subsystem
are
supplied.
The
IMS
XCF
Group
name
and
IMS
XCF
Member
name
are
retrieved
from
NetView
global
variables
that
are
loaded
during
the
IMS
rediscovery
process.
This
problem
might
be
caused
by
an
error
during
rediscovery,
or
because
the
OTMA
interface
has
not
been
started
on
the
target
IMS.
This
problem
might
be
resolved
by
stopping
and
starting
the
OTMA
interface
on
the
target
IMS
(using
the
/STO
OTMA,
and
/STA
OTMA
IMS
commands),
or
by
performing
a
mouse-click
rediscovery.
Refer
to
the
IBM
Tivoli
Business
Systems
Manager
Administrator’s
Guide
before
attempting
to
use
the
IMS
mouse-click
rediscovery
process.
IHS430I
command
COMMAND
ISSUED
ON
AUTOTASK
autotask
Explanation:
Tivoli
Business
Systems
Manager
issued
a
command
on
a
NetView
autotask.
Message
Variables:
command
-
The
name
of
the
command
that
is
issued
autotask
-
The
NetView
autotask
on
which
the
command
is
run
System
Action:
The
command
runs
on
the
designated
autotask.
IHS431E
KEYWORD
keyword
IS
NOT
SUPPORTED
IN
location
Explanation:
A
keyword
that
is
not
valid
was
specified
in
an
input
file
record.
Message
Variables:
keyword
-
The
keyword
that
is
not
valid
location
-
The
location
of
the
member
containing
the
keyword
that
is
not
valid.
The
format
is
as
follows:
ddname(member)
dataset(member)
For
example,
DSIPARM(IHSSMONI)
TBSM.SGTMSAMP(IHSSMONI).
System
Action:
The
record
containing
the
keyword
that
is
not
valid
is
ignored
and
processing
continues.
160
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
Administrator
Response:
Check
the
location
in
the
header
information
for
the
correct
syntax
and
modify
the
record
accordingly.
IHS433I
UNINITIALIZED
VALUE
variable
USED
IN
module
Explanation:
The
module
has
attempted
to
reference
a
variable,
but
the
value
for
the
variable
has
not
yet
been
set
(for
example,
a
NOVALUE
condition).
Message
Variables:
variable
-
The
variable
name
whose
value
could
not
be
retrieved
module
-
The
module
name
System
Action:
Processing
for
this
module
ends.
Administrator
Response:
This
usually
indicates
an
internal
error.
Report
the
error
to
IBM
Software
Support.
This
error
might
be
resolved
by
stopping
and
restarting
the
region
being
monitored,
or
by
performing
a
mouse-click
rediscovery.
Refer
to
the
IBM
Tivoli
Business
Systems
Manager
Administrator’s
Guide
for
more
information
about
performing
mouse-click
rediscoveries.
IHS435I
PROBLEM
ALLOCATING
THE
ddname
DATASET
dataset_name
Explanation:
This
message
is
issued
when
a
file
allocation
fails.
Message
Variables:
ddname
-
The
data
definition
name
dataset_name
-
The
data
set
name
or
names
System
Action:
Processing
continues.
Administrator
Response:
If
you
are
unable
to
resolve
the
error,
contact
IBM
Software
Support.
IHS439I
PROGRAM
pgm
COMPLETE
Explanation:
This
message
is
issued
when
the
program
completes.
Message
Variables:
program
-
The
name
of
the
program
performing
the
action
IHS443E
error
CONDITION
TRAPPED
IN
pgm
LINE
line
(CODE
return_code)
DESCRIPTION
msg
Explanation:
Handle
REXX
Signal
error
processing.
Message
Variables:
error
-
The
error
condition
pgm
-
The
program
name
line
-
The
line
in
the
code
where
the
error
occurred
return_code
-
The
return
code
(optional)
msg
-
The
description
of
the
error,
if
available
Administrator
Response:
Investigate
the
cause
of
failure.
If
you
are
unable
to
resolve
the
problem,
contact
IBM
Software
Support.
IHS447E
module
-
RETURN
CODE
return_code
FROM
IHSMSG.
PROCESSING
TERMINATED.
Explanation:
Unable
to
send
events
to
the
source/390
object
pump.
Message
Variables:
module
-
The
module
name
return_code
-
The
return
codes
returned
by
IHSMSG
System
Action:
Processing
continues.
Administrator
Response:
Report
the
error
message
to
IBM
Software
Support.
IHS451I
pgm
COMPLETED
WITH
RETURN
CODE
return_code
called_mod
call_mod_rc
subsystem
Explanation:
This
message
is
issued
to
indicate
whether
the
program
completed
successfully
or
unsuccessfully
with
a
return
code
return_code.
It
might
also
indicate
a
called
subsidiary
module,
the
return
code
from
that
module,
and
the
name
of
a
subsystem.
Message
Variables:
pgm
-
The
program
name,
which
might
include
additional
identification
parameters
in
parentheses.
return_code
-
The
return
code
from
the
program
called_mod
-
The
module
called
from
the
program
call_mod_rc
-
The
return
code
from
the
module
subsystem
-
The
subsystem
name
or
job
name
System
Action:
Processing
continues.
Administrator
Response:
Contact
IBM
Software
Support
if
the
return
code
is
a
non-zero
value.
IHS452I
resource
STATUS
status
AT
subsystem
INITIALIZATION
Explanation:
The
named
resource
was
found
to
be
in
either
UP
or
DOWN
status
when
the
named
job
was
initializing
Message
Variables:
resource
-
The
name
of
the
resource;
for
example,
the
job
name
of
a
region
or
subsystem
status
-
The
state
in
which
the
resource
was
found.
The
status
is
either
UP
or
DOWN.
subsystem
-
The
subsystem
that,
on
startup,
has
resulted
in
the
status
of
the
resource
to
be
checked.
The
subsystem
is
often
NETVIEW,
or
a
DB2
subsystem
or
Data
Sharing
Group.
System
Action:
Processing
continues.
Chapter
14.
IHS
Messages
-
IHS307E
-
IHS829I,
IHS0561I
161
IHS458E
module
FAILED
WITH
RC
return_code
msg_parms
Explanation:
The
internal
routine
module
has
received
a
non-zero
return
code.
Message
Variables:
module
-
The
name
of
the
processing
module
return_code
-
The
return
code
for
the
failed
routine
msg_parms
-
The
message
text
and
parameters
from
the
calling
module.
The
message
text
is
contained
with
brackets
and
prefixed
by
the
string
MSG,
if
available.
The
parameters
are
contained
with
brackets
and
prefixed
by
the
string
PARMS,
if
available.
System
Action:
The
current
message
is
bypassed
and
processing
continues.
Administrator
Response:
If
you
are
unable
to
determine
the
problem,
contact
IBM
Software
Support.
IHS466E
NO
EVENTS
WERE
PASSED
TO
module
IN
SAFE
safe
Explanation:
The
named
module
was
called
to
perform
processing
of
bulk
events,
taking
these
events
from
the
named
NetView
safe.
However,
this
safe
did
not
hold
any
events.
Message
Variables:
module
-
The
module
that
was
called
safe
-
The
name
of
the
safe
used
as
input
to
the
module
System
Action:
Processing
continues.
Administrator
Response:
This
is
usually
caused
by
a
previous
error.
Check
for
previous
error
messages
describing
an
error,
and
resolve
these
errors.
If
you
are
unable
to
determine
the
problem,
contact
IBM
Software
Support.
IHS470E
COULD
NOT
DETERMINE
SUBSYS.
PARMS(parm_string)
Explanation:
The
IHSMSG
program
was
unable
to
extract
the
name
of
the
subsystem
from
the
input
parameters.
Message
Variables:
parm_string
-
The
The
IHSMSG
program
input
parameters
System
Action:
Processing
continues.
Administrator
Response:
Review
the
input
parameters
within
the
message.
If
you
are
unable
to
determine
the
source
of
the
error,
contact
IBM
Software
Support.
IHS473I
COULD
NOT
DETERMINE
NETID.SSCPNAME
Explanation:
The
NETID
(Network
Identifier)
and
SSCPNAME
(System
Services
Control
Point
name)
of
the
MVS
system
could
not
be
determined.
System
Action:
Processing
continues.
Administrator
Response:
The
NETID
and
SSCPNAME
values
are
derived
from
the
output
of
the
MVS
D
NET,VTAMOPTS
command.
Ensure
VTAM
was
started
and
available
at
the
time
of
the
error.
If
not,
contact
IBM
Software
Support.
IHS485I
threshold_name
SET
TO
new_value.
PREVIOUS
VALUE
WAS
current_value.
Explanation:
Provides
the
Tivoli
Business
Systems
Manager
console
user
with
the
previous
threshold
value
and
confirmation
of
the
new
value.
Message
Variables:
threshold_name
-
The
name
of
the
threshold
new_value
-
The
new
value
of
the
threshold
current_value
-
The
current
value
of
the
threshold
Administrator
Response:
For
the
IMS
data
source,
the
threshold
names
are
documented
within
the
IHSIPRM
member
in
the
SGTMSAMP
data
set.
IHS486E
threshold_name
NOT
SET
TO
new_value
-
VALUE
NOT
VALID.
CURRENT
VALUE
IS
current_value.
Explanation:
Indicates
the
new
value
entered
by
the
Tivoli
Business
Systems
Manager
console
user
for
the
threshold
is
not
a
valid
value.
The
value
must
be
positive
integer
value.
Message
Variables:
threshold_name
-
The
name
of
the
threshold
new_value
-
The
new
value
of
the
threshold
current_value
-
The
current
value
of
the
threshold
Administrator
Response:
The
threshold
names
are
documented
within
the
IHSIPRM
member
in
the
SGTMSAMP
data
set
for
the
IMS
data
source,
and
within
the
IHSBPRM
member
in
SGTMSAMP
for
the
DB2
data
source.
Correct
the
value
and
enter
it
again.
IHS487W
ims_jobname
IS
IMS
RELEASE
release
-
THIS
RELEASE
IS
NOT
SUPPORTED
BY
TIVOLI
BUSINESS
SYSTEMS
MANAGER.
Explanation:
The
IMS
region
indicated
by
its
IMS
ID
(Subsystem
Identifier)
or
its
Control
Region
job
name
is
an
IMS
release
that
is
not
supported
by
Tivoli
Business
Systems
Manager.
Message
Variables:
ims_jobname
-
The
job
name
of
the
162
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
IMS
control
region
or
the
IMS
ID
(Subsystem
Identifier)
release
-
The
release
number
that
is
not
supported
System
Action:
No
processing
or
monitoring
occurs
for
this
IMS
region.
Administrator
Response:
If
you
require
this
IMS
region
to
be
supported,
upgrade
to
an
IMS
release
that
is
supported
by
Tivoli
Business
Systems
Manager.
IHS488I
DISCOVERY
OF
ALL
IMS
REGIONS
ON
NETVIEW
STARTUP
status
Explanation:
Upon
NetView
startup,
all
IMS
regions
and
associated
address
spaces
are
found,
and
rediscovery
processing
is
performed
as
required.
This
message
states
either
that
this
processing
has
commenced
(status
=
COMMENCED)
or
finished
(status
=
COMPLETED).
Message
Variables:
status
-
The
status
of
the
NetView
startup
action
System
Action:
If
status
=
COMMENCED,
rediscovery
is
performed
for
all
detected
IMS
and
related
regions.
IHS489I
name
text
current_value
unit
Explanation:
Indicates
the
current
value
of
a
threshold
or
interval.
Message
Variables:
name
-
The
name
of
the
threshold
or
interval
text
-Either
THRESHOLD
IS
or
INTERVAL
IS
current_value
-
The
current
value
of
the
threshold
or
interval
unit
-
The
unit
of
the
threshold
or
interval
(only
occurs
in
some
cases)
Administrator
Response:
The
threshold
names
are
documented
within
the
IHSIPRM
member
in
the
SGTMSAMP
data
set
for
the
IMS
data
source,
and
within
the
IHSBPRM
member
in
SGTMSAMP
for
the
DB2
data
source.
IHS492E
ERROR
READING
IMS
CONNECT
CONFIGURATION,
RSN=reason_code
Explanation:
This
message
is
issued
by
IHSIRITO
if
it
encounters
a
problem
reading
the
IMS
Connect
configuration.
The
type
of
error
is
further
clarified
by
the
reason
code.
Message
Variables:
reason_code
1
No
configuration
data
read
2
Unable
to
retrieve
PROCLIB
data
set
name
3
Unable
to
retrieve
configuration
member
name
4
Configuration
member
not
in
IMS
Connect
parm
5
QSAM
error
reading
configuration
data
System
Action:
Processing
continues,
however
the
rediscovery
of
the
IMS
Connect
region
is
not
successful.
Administrator
Response:
Verify
that
the
IMS
Connect
configuration
member
in
the
IMS
Connect
PROCLIB
is
present
and
correct
(as
described
in
the
IMS
Connect
Guide
and
Reference).
If
this
problem
persists,
contact
IBM
Software
Support.
IHS493W
OTMA
IS
NOT
STARTED
FOR
ims_jobname,
TIVOLI
BUSINESS
SYSTEMS
MANAGER
PROCESSING
WILL
BE
IMPEDED.
Explanation:
Tivoli
Business
Systems
Manager
processing
for
IMS
TM/DB
and
DBCTL
regions
relies
heavily
on
the
IMS
OTMA
facility
being
active
for
these
IMS
regions.
The
named
IMS
region,
however,
does
not
have
the
IMS
OTMA
facility
started
and
active.
Message
Variables:
ims_jobname
-
The
job
name
of
the
IMS
Control
Region
System
Action:
Tivoli
Business
Systems
Manager
attempts
to
continue
processing,
however
some
resources
and
events
might
not
be
monitored,
and
other
errors
might
occur.
Administrator
Response:
Start
the
OTMA
facility
for
this
IMS
region
as
soon
as
possible,
then
schedule
a
mouse-click
rediscovery
to
ensure
all
resources
were
discovered.
IHS495I
OTMA
WAS
STOPPED
FOR
ims_jobname
Explanation:
OTMA
was
stopped
for
the
stated
IMS
region.
Message
Variables:
ims_jobname
-
The
job
name
of
the
IMS
Control
Region
System
Action:
Processing
continues.
Administrator
Response:
Start
OTMA
for
this
IMS
region
as
soon
as
possible,
then
perform
a
mouse-click
rediscovery
to
ensure
all
resources
have
been
discovered.
Processing
for
the
IMS
region
relies
strongly
on
OTMA
being
started.
Investigate
why
OTMA
has
been
stopped.
IHS496W
REGION
jobname
NOT
STARTED
–
UNABLE
TO
PERFORM
REDISCOVERY.
Explanation:
A
rediscovery
was
attempted
for
the
jobname
job.
However,
this
job
has
not
started,
or
is
not
completely
operational.
Note
that
Tivoli
Business
Systems
Manager
cannot
rediscover
an
IMS
region
until
it
has
issued
a
DFS994I
message
indicating
that
it
completed
its
startup
processes.
This
often
occurs
from
Chapter
14.
IHS
Messages
-
IHS307E
-
IHS829I,
IHS0561I
163
attempting
a
mouse-click
rediscovery
for
a
region
that
did
not
start,
or
is
not
completely
operational.
Message
Variables:
jobname
-
The
job
name
of
the
region
System
Action:
Rediscovery
for
this
job
does
not
occur.
Administrator
Response:
Check
that
the
job
is
completely
up
and
operational,
and
try
the
operation
again.
Note
that
IMS
regions
cannot
be
rediscovered
until
the
restart
is
complete
(and
the
region
has
issued
message
number
DFS994I
that
startup
completed).
If
you
cannot
resolve
the
problem,
contact
IBM
Software
Support.
IHS497I
PARTITIONS
FOR
HALDB
MASTER
mdb_name,
discovery_status
DISCOVERED
IN
ims_name
Explanation:
A
discovery_status
of
NOT
indicates
IMS
discovery
processing
did
not
identify
the
HALDB
partitions
of
the
HALDB
Master
database
mdb_name
in
the
IMS
system
ims_name.
A
discovery_status
of
NOW
indicates
that
the
issue
that
was
preventing
identification
of
the
partitions
is
now
resolved.
This
can
be
caused
if
the
HALDB
Master
database
was
offline
because
of
a
prior
IMS
/DBR
command,
and
the
IMS
discovery
attempted
to
identify
the
partitions
of
the
HALDB
Master
database
mdb_name.
Message
Variables:
mdb_name
-
The
name
of
the
HALDB
Master
database
discovery_status
-
The
discovery
status
of
the
HALDB
Master
database,
which
is
NOT
or
NOW
ims_name
-
The
job
name
of
the
IMS
Control
Region
whose
IMS
system
is
being
discovered
System
Action:
The
HALDB
partitions
of
the
HALDB
Master
database
will
not
be
discovered.
Discovery
processing
continues.
Administrator
Response:
Ensure
the
HALDB
Master
database
is
available
online
and
the
HALDB
partitions
are
correctly
defined
within
the
IMS
RECON
data
sets.
To
discover
the
missing
HALDB
partitions,
initiate
a
partial
discovery
for
the
IMS
system
from
the
Tivoli
Business
Systems
Manager
console
using
the
mouse-click
discovery
command.
If
the
problem
persists,
contact
IBM
Software
Support.
IHS498I
PARTITION
name
IS
IN
RESTRICTED
STATE.
Explanation:
This
message
is
issued
when
the
IMS
Database
Poll
Monitor
detects
that
an
IMS
HALDB
Partition
is
in
a
restricted
state.
The
IMS
Database
Poll
Monitor
determines
this
by
analyzing
the
status
that
appear
for
databases
on
the
output
of
an
IMS
/DIS
STATUS
DBS
command.
Message
Variables:
name
-
The
name
of
the
IMS
HALDB
partition
System
Action:
An
exception
event
for
the
partition
name
is
sent
to
Tivoli
Business
Systems
Manager
and
processing
continues.
Administrator
Response:
If
this
is
an
error,
determine
why
the
HALDB
Partition
is
in
a
restricted
state
and
take
appropriate
action.
IHS499I
PARTITION
name
IS
NOW
AVAILABLE
Explanation:
The
IMS
Database
Poll
Monitor
detects
that
an
IMS
HALDB
Partition
is
no
longer
in
a
restricted
state.
IMS
has
analyzed
the
output
of
an
IMS
/DIS
STATUS
DBS
command
and
found
that
the
HALDB
Partition
that
was
previously
in
a
restricted
status
no
longer
appears
or
it
appears
with
an
unrestricted
status.
Message
Variables:
name
-
The
name
of
the
IMS
HALDB
partition
System
Action:
A
resolution
event
for
the
partition
name
is
sent
to
Tivoli
Business
Systems
Manager
and
processing
continues.
IHS570E
type
CONDITION
TRAPPED
IN
name
LINE
line
(CODE)
return_code
text
Explanation:
A
REXX
EXEC
has
trapped
a
SIGNAL
condition.
Message
Variables:
type
-
The
type
of
SIGNAL
condition
name
-
The
name
of
the
REXX
EXEC
where
processing
stopped
line
-
The
line
number
within
the
REXX
EXEC
where
processing
stopped
return_code
-
The
return
code
from
the
SIGNAL
condition
text
-
The
description
text
from
the
SIGNAL
condition
System
Action:
The
REXX
EXEC
trapped
the
SIGNAL
condition.
Administrator
Response:
Record
the
SIGNAL
condition
details
and
contact
IBM
Software
Support.
IHS571E
UNABLE
TO
LOGON
TO
TMON
FOR
MVS
(APPLID
=
applid).
Explanation:
An
attempt
to
log
on
to
the
ASG
TMON
for
MVS
application
failed.
Message
Variables:
applid
-
The
VTAM
application
ID
of
the
TMON
for
MVS
application
System
Action:
Another
logon
attempt
will
be
made
after
the
interval
specified
with
the
IHSZTM.WAITLOGON
parameter
in
the
IHSZTMIN
DSIPARM
member.
164
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
Administrator
Response:
v
This
message
is
followed
by
an
IHS750I
message
displaying
messages
issued
by
VTAM
or
ASG
TMON
for
MVS.
Review
these
messages.
v
Ensure
that
the
ASG
TMON
for
MVS
TMONMVS
started
task
is
up
and
is
accepting
logon
requests.
v
Check
that
the
VTAM
application
ID
for
the
TMON
for
MVS
application
is
active.
v
Check
the
values
specified
in
the
IHSZTMIN
DSIPARM
member.
v
Check
the
user
ID
and
password
specified
in
the
IHSZTMIN
DSIPARM
member
by
logging
on
to
ASG
TMON
for
MVS
using
this
user
ID
and
password.
Check
that
this
user
ID
has
access
to
the
Exception
Activity
Display.
v
If
the
SRCLU
value
used
for
the
logon
attempt
is
specified
in
any
of
the
accompanying
messages
from
the
NetView
for
z/OS
program,
check
that
this
SRCLU
value
is
defined
and
operational.
IHS572E
UNABLE
TO
DISPLAY
THE
EXCEPTION
ACTIVITY
DISPLAY
PANEL
FOR
TMON
FOR
MVS
(APPLID
=
applid).
Explanation:
After
successfully
logging
on
to
ASG
TMON
for
MVS,
an
error
occurred
attempting
to
display
the
Exception
Activity
Display
panel.
Message
Variables:
applid
-
The
VTAM
application
ID
of
the
TMON
for
MVS
application
System
Action:
Monitoring
of
TMON
for
MVS
stops.
Administrator
Response:
This
is
usually
caused
by
the
user
ID
specified
in
the
IHSZTMIN
DSIPARM
member
not
having
access
to
the
Exception
Activity
Display
panel.
Check
also
that
Tivoli
Business
Systems
Manager
supports
the
version
of
ASG-TMON
for
MVS
currently
used.
If
you
are
unable
to
resolve
this
problem,
contact
IBM
Software
Support.
IHS573E
UNABLE
TO
RETRIEVE
EXCEPTIONS
FROM
TMON
FOR
MVS
(APPLID
=
applid).
Explanation:
After
successfully
logging
on
to
ASG
TMON
for
MVS,
an
error
occurred
retrieving
exceptions.
Message
Variables:
applid
-
The
VTAM
application
ID
of
the
TMON
for
MVS
application
System
Action:
Another
attempt
to
log
on
to
ASG
TMON
for
MVS
and
access
the
Exception
Activity
Display
panel
is
made
after
the
interval
specified
with
the
IHSZTM.WAITLOGON
parameter
in
the
IHSZTMIN
DSIPARM
member.
Administrator
Response:
This
often
occurs
if
communications
between
Tivoli
Business
Systems
Manager
and
ASG
TMON
for
MVS
are
interrupted.
Check
that
the
TMON
for
MVS
TMONMVS
started
task
is
operational
and
is
accepting
logon
requests.
v
Ensure
that
the
ASG
TMON
for
MVS
TMONMVS
started
task
is
up
and
is
accepting
logon
requests.
v
Check
that
the
VTAM
application
ID
for
the
TMON
for
MVS
application
is
active.
v
When
Tivoli
Business
Systems
Manager
attempts
again
to
log
on
to
TMON
for
MVS,
check
any
messages
for
further
information.
v
Check
the
NetView
netlog
for
NetView
errors.
If
you
are
unable
to
resolve
the
problem,
contact
IBM
Software
Support.
IHS574W
STOPPED
RETRIEVAL
AT
num
PANELS
OF
EXCEPTIONS
FROM
TMON
FOR
MVS
(APPLID
=
applid)
Explanation:
Tivoli
Business
Systems
Manager
has
stopped
retrieving
TMON
for
MVS
exceptions
after
num
panels
from
the
Exception
Activity
Display
were
read.
Message
Variables:
num
-
The
number
of
panels
read
from
the
Exception
Activity
Display
panel
applid
-
The
VTAM
application
ID
of
the
TMON
for
MVS
application
System
Action:
Processing
continues,
however
any
TMON
for
MVS
Exception
Activity
panels
beyond
the
first
num
are
ignored.
Administrator
Response:
Log
on
to
TMON
for
MVS
and
confirm
that
there
are
more
than
num
panels
of
exceptions
displayed
in
the
Exception
Activity
Display
panel.
If
so,
reduce
the
number
of
exceptions
trapped
by
Tivoli
Business
Systems
Manager
by
customizing
the
settings
within
ASG
TMON
for
MVS,
or
by
changing
the
values
for
LEVEL
or
GROUPS
in
the
IHSZTMIN
DSIPARM
member.
Otherwise,
contact
IBM
Software
Support.
IHS576E
RETURN
CODE
return_code
RECEIVED
WHEN
ATTEMPTING
TO
READ
name
FROM
ddname.
Explanation:
Tivoli
Business
Systems
Manager
has
received
an
unexpected
return
code
when
attempting
to
read
a
member
from
a
file
into
storage.
Message
Variables:
return_code
-
The
return
code
from
the
NetView
PIPE
doing
the
I/O
name
-
The
member
name
that
was
being
read
ddname
-
The
file
name
or
DD
name
of
the
data
set
concatenation
containing
name
System
Action:
Tivoli
Business
Systems
Manager
attempts
to
continue
processing.
Administrator
Response:
Check
that
the
member
being
read
exists
in
the
file
concatenation,
and
that
all
Chapter
14.
IHS
Messages
-
IHS307E
-
IHS829I,
IHS0561I
165
data
sets
in
the
concatenation
are
valid.
Check
the
NetView
netlog
and
z/OS
syslog
for
associated
messages.
Check
that
no
security
violations
occurred
for
data
sets
within
the
file
concatenation.
If
you
are
unable
to
resolve
the
problem,
contact
IBM
Software
Support.
IHS577W
INCORRECT
PARAMETER
value
SPECIFIED
IN
dd
MEMBER
member.
Explanation:
An
unexpected
or
incorrect
parameter
was
specified
in
the
parameter
member.
Message
Variables:
value
-
The
parameter
specified
with
the
incorrect
value
dd
-
The
DD
name
holding
the
parameter
member
name
-
The
parameter
member
name
System
Action:
Tivoli
Business
Systems
Manager
attempts
to
continue
processing.
Administrator
Response:
This
is
caused
by
an
incorrect
value
being
specified
for
a
parameter
(for
example,
a
word
being
specified
instead
of
a
number),
or
no
value
being
specified
for
a
compulsory
parameter.
Check
the
parameter
value
specified
and
correct
it
as
appropriate.
If
you
are
unable
to
resolve
the
problem,
contact
IBM
Software
Support.
IHS579I
feed
INSTRUMENTATION
DISABLED.
Explanation:
Tivoli
Business
Systems
Manager
was
instructed
to
stop
monitoring
the
data
source
named
in
the
message.
Message
Variables:
feed
-
The
data
source
that
was
disabled
System
Action:
Processing
for
the
named
Tivoli
Business
Systems
Manager
data
source
stops.
Administrator
Response:
A
Tivoli
Business
Systems
Manager
parameter
was
set
by
a
request
(for
example,
by
an
operator).
If
this
is
not
preferred,
review
all
parameters
relevant
to
the
data
source
(refer
to
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide
for
more
information),
and
change
the
relevant
parameter
to
enable
monitoring.
If
you
are
unable
to
resolve
this
problem,
contact
IBM
Software
Support.
IHS580E
IHSMSG
FAILED
WITH
RETURN
CODE
return_code
ACTION
=
action_code
OBJECT
TYPE
=
object_type
SUBSYSTEM
=
DB2_subsys_name
Explanation:
An
internal
API
failed
to
complete.
Message
Variables:
return_code
-
The
return
code
from
IHSMSG
action_code
-
The
action
code
defined
within
the
message
object_type
-
The
type
of
resource
to
which
the
message
was
being
sent
DB2_subsys_name
-
The
DB2
subsystem
which
owns
the
resource
System
Action:
Processing
continues.
Administrator
Response:
This
is
an
internal
error.
Contact
IBM
Software
Support.
IHS582I
IHSBINIT
COMPLETED
WITH
RETURN
CODE
return_code
Explanation:
Initialization
of
DB2
instrumentation
for
Tivoli
Business
Systems
Manager
completed.
Message
Variables:
return_code
-
The
return
code
Administrator
Response:
If
the
return
code
is
not
zero,
examine
the
NetView
log
preceding
this
message
for
more
detailed
error
messages,
and
respond
to
them.
IHS583W
IHSBINIT
-
UNSUCCESSFUL
CALL
TO
IHSBPMCH
PROCESSING
CONTINUES
Explanation:
Unsuccessful
call
to
IHSBPMCH.
System
Action:
Exceptions
from
the
DB2
Performance
Monitor
will
not
be
processed.
Administrator
Response:
This
is
an
internal
error.
Contact
IBM
Software
Support.
IHS589W
FORMAT
OF
MAINVIEW
MESSAGE
msgid
NOT
VALID
FOR
IBM
TIVOLI
BUSINESS
SYSTEMS
MANAGER
INSTRUMENTATION.
Explanation:
An
unexpected
message
was
received.
Message
Variables:
msgid
-
The
unique
identifier
of
the
message
System
Action:
The
message
will
not
be
processed.
Administrator
Response:
This
is
an
internal
error.
Contact
IBM
Software
Support.
IHS606E
pgm
subsystem
DISCOVERY
ABANDONED,
CUSTOMIZATION
ERRORS
FOUND
Explanation:
The
named
program
determined
that
the
nominated
DB2
subsystem
cannot
be
discovered
due
to
errors
which
are
related
to
Tivoli
Business
Systems
Manager
or
DB2
customization.
Message
Variables:
pgm
-
The
program
that
issued
the
message
subsystem
-
The
name
of
the
subsystem
being
processed
System
Action:
The
discovery
is
bypassed.
Administrator
Response:
Refer
to
the
IBM
Tivoli
166
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
Business
Systems
Manager
Administrator’s
Guide
for
more
information.
Run
the
DB2
IVP
program
for
the
nominated
DB2
subsystem
and
correct
any
errors.
The
DB2
subsystem
will
then
be
discovered
at
the
next
subsystem
or
when
the
NetView
program
is
started
again.
IHS607I
pgm
REDISCOVERY
FOR
object
name
ROUTED
TO
domain
Explanation:
The
named
program
has
determined
that
the
nominated
DB2
subsystem
or
Data
Sharing
Group
is
monitored
by
another
NetView
domain,
which
is
responsible
for
processing
the
discovery.
Message
Variables:
pgm
-
The
program
that
issued
the
message
object
-
The
literal
SSNAME
or
DSGNAME
name
-
The
name
of
the
DB2
subsystem
or
Data
Sharing
group
domain
-
The
name
of
the
NetView
domain
that
performs
the
discovery
System
Action:
The
discovery
continues
on
the
nominated
domain.
Administrator
Response:
No
response
is
necessary
unless
the
discovery
does
not
complete
successfully.
In
that
case,
examine
the
NetView
log
on
the
nominated
domain
for
further
information.
IHS608E
pgm
MONITORING
DOMAIN
FOR
object
name
IS
NOT
KNOWN
Explanation:
The
named
program
was
unable
to
determine
the
NetView
domain
which
should
perform
the
discovery
of
the
nominated
Data
Sharing
Group.
Message
Variables:
pgm
-
The
program
that
issued
the
message
object
-
The
literal
SUBSYSTEM
or
DSG
name
-
The
name
of
the
DB2
subsystem
or
Data
Sharing
group
System
Action:
The
discovery
is
bypassed.
Administrator
Response:
Ensure
that
the
Tivoli
Business
Systems
Manager
console
is
connected
to
the
NetView
domain
that
is
monitoring
the
relevant
object.
IHS609I
pgm
status
DISCOVERY
OF
class
OBJECTS
Explanation:
The
named
program
has
either
started
or
finished
the
process
of
discovering
the
named
class
of
resources.
Message
Variables:
pgm
-
The
program
that
issued
the
message
status
-
The
status,
which
is
either
STARTED
or
FINISHED
class
-
The
name
of
the
class
of
resources
System
Action:
The
discovery
process
continues.
IHS620W
pgm
-
NO
DB2
SUBSYSTEMS
CURRENTLY
ACTIVE
FOR
DSG
name
Explanation:
An
attempt
was
made
to
issue
a
DB2
command
to
a
Data
Sharing
Group,
but
there
were
no
active
members
available
to
process
the
command.
Message
Variables:
pgm
-
The
program
that
detected
the
situation
name
-
The
DB2
Data
Sharing
Group
name
System
Action:
The
program
ends
without
issuing
the
requested
command.
Administrator
Response:
Ensure
that
at
least
one
DB2
subsystem
in
the
Data
Sharing
Group
is
active
and
issue
the
command
again.
If
the
command
was
issued
through
the
DeRespinisGUI
from
a
DB2
subsystem
resource
instead
of
a
Data
Sharing
Group
resource,
name
might
be
null.
This
occurs
if
no
members
of
the
Data
Sharing
Group
were,
or
are,
monitored
by
the
host.
The
subsystem
or
subsystems
might
be
inactive,
or
they
might
be
active
but
excluded
from
monitoring.
IHS621E
CALL
TO
IHSMSG
FROM
pgm
FAILED
WITH
RETURN
CODE
=
return_code
ACTION
=
action_code
OBJECT
TYPE
=
object_type
SUBSYSTEM
=
name
Explanation:
The
IHSMSG
program
was
unable
to
send
a
message
to
the
source/390
object
pump.
Message
Variables:
pgm
-
The
program
that
detected
the
situation
return_code
-
The
return
code
from
IHSMSG
action_code
-
The
action
code
defined
within
the
message
object_type
-
The
type
of
resource
to
which
the
message
was
being
sent
name
-
The
DB2
subsystem
which
owns
the
resource
System
Action:
The
program
ends
without
sending
the
message.
Administrator
Response:
Identify
the
host
event
which
caused
the
message
to
be
built,
then
report
the
problem
to
IBM
Software
Support.
IHS622E
CALL
TO
IHSMSG
FROM
pgm
FAILED
WITH
RETURN
CODE
=
return_code
ACTION
=
action_code
OBJECT_TYPE
=
object_type
DSG
NAME
=
name
Explanation:
The
IHSMSG
program
was
unable
to
send
a
message
to
the
source/390
object
pump.
Message
Variables:
pgm
-
The
program
that
detected
the
situation
Chapter
14.
IHS
Messages
-
IHS307E
-
IHS829I,
IHS0561I
167
return_code
-
The
return
code
from
IHSMSG
action_code
-
The
action
code
defined
within
the
message
object_type
-
The
type
of
resource
to
which
the
message
was
being
sent
name
-
The
DB2
Data
Sharing
Group
which
owns
the
resource
System
Action:
The
program
ends
without
sending
the
message.
Administrator
Response:
Identify
the
host
event
which
caused
the
message
to
be
built,
then
report
the
problem
to
IBM
Software
Support.
IHS623W
pgm
:
MESSAGE
message_id
FROM
name
IGNORED.
MESSAGE
NOT
VALID
FOR
A
STAND-ALONE
DB2
SUBSYSTEM.
Explanation:
A
message
related
to
a
group
buffer
pool
has
been
issued
from
a
DB2
subsystem.
Tivoli
Business
Systems
Manager
considers
this
to
be
a
stand-alone
subsystem
and
does
not
participate
in
a
data
sharing
group.
Message
Variables:
pgm
-
The
program
that
issued
the
message
message_id
-
The
DB2
message
being
processed
name
-
The
name
of
the
DB2
subsystem
that
issued
the
message
System
Action:
Processing
continues.
The
DB2
message
is
not
processed.
Administrator
Response:
If
the
subject
DB2
subsystem
is
part
of
a
data
sharing
group,
then
it
has
been
incorrectly
identified
as
a
stand-alone
subsystem.
Report
the
problem
to
IBM
Software
Support.
IHS624E
pgm
-
IRLM
CGLOBAL
NOT
FOUND
FOR
SUBSYSTEM
name
WHEN
PROCESSING
MESSAGE
text
Explanation:
When
processing
a
message
from
a
subsystem
resource,
the
program
was
unable
to
identify
the
IRLM
resource
to
which
the
message
should
be
posted.
This
might
occur
during
DB2
subsystem
initialization
if
an
exception
is
received
while
discovery
is
being
performed.
Message
Variables:
pgm
-
The
program
that
detected
the
situation
name
-
The
name
of
the
subsystem
resource
text
-
The
system
message
which
was
being
processed
by
the
program
System
Action:
The
program
ends
without
sending
the
message.
Administrator
Response:
If
this
message
was
issued
during
DB2
discovery,
it
can
be
ignored.
Otherwise,
report
the
problem
to
IBM
Software
Support.
IHS625E
pgm
-
DATA
SHARING
GROUP
CGLOBAL
NOT
FOUND
FOR
SUBSYSTEM
name
WHEN
PROCESSING
MESSAGE
text
Explanation:
When
processing
a
message
from
a
subsystem
resource,
the
program
was
unable
to
identify
the
Data
Sharing
Group
resource
to
which
the
message
should
be
posted.
This
might
occur
during
DB2
subsystem
initialization
if
an
exception
is
received
while
discovery
is
being
performed.
Message
Variables:
pgm
-
The
program
that
detected
the
situation
name
-
The
name
of
the
subsystem
resource
text
-
The
system
message
which
was
being
processed
by
the
program
System
Action:
The
program
ends
without
sending
the
message.
Administrator
Response:
If
this
message
was
issued
during
DB2
discovery,
it
can
be
ignored.
Otherwise,
report
the
problem
to
IBM
Software
Support.
IHS626E
pgm
-
UNSUCCESSFUL
CALL
TO
IHSBSQL
FOR
SUBSYSTEM
name.
PROCESSING
TERMINATED.
info
Explanation:
The
IHSBSQL
program
did
not
successfully
perform
the
requested
function.
Message
Variables:
pgm
-
The
program
(and
optionally,
the
subroutine)
which
detected
the
situation
name
-
The
name
of
the
subsystem
resource
info
-
Variable
return
information
from
IHSBSQL
System
Action:
The
program
ends
without
sending
the
message.
Administrator
Response:
Probable
configuration
error.
The
return
information
from
the
IHSBSQL
program
might
include
a
standard
SQL
error
code;
refer
to
the
DB2
Messages
and
Codes
manual
for
an
explanation
of
the
return
code
and
reason
code,
which
will
indicate
which
configuration
step
was
unsuccessful.
If
the
return
information
is
not
an
SQL
error
code,
report
the
problem
to
IBM
Software
Support.
IHS627E
pgm
-
UNSUCCESSFUL
CALL
TO
IHSBFIND
FOR
SUBSYSTEM
name.
PROCESSING
TERMINATED.
Explanation:
The
IHSBFIND
program
returned
no
information.
Message
Variables:
pgm
-
The
program
that
called
IHSBFIND
168
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
name
-
The
name
of
the
subsystem
resource
being
processed
System
Action:
Processing
continues
with
the
next
defined
subsystem.
Administrator
Response:
The
REXX
program
that
called
the
assembler
routine
issues
another
message.
Perform
the
actions
recommended
for
that
message.
IHS628I
pgm
FINISHED
PROCESSING
SUBSYSTEM
name
WITH
RETURN
CODE
return_code.
Explanation:
The
initialization
or
ending
process
has
been
completed
for
a
DB2
subsystem.
Message
Variables:
pgm
-
The
program
that
issued
the
message
name
-
The
name
of
the
subsystem
resource
being
processed
return_code
-
The
return
code
set
by
the
issuing
program
System
Action:
Processing
continues
with
the
next
relevant
subsystem.
Administrator
Response:
If
return
code
is
0
(zero),
no
action
is
necessary.
For
return
codes
other
than
0,
analyze
the
NetView
log
for
earlier
messages
and
take
the
recommended
action.
IHS629I
pgm
INTERVAL
FOR
name
IS
interval.
Explanation:
The
IHSBTIME
program
is
listing
the
current
values
for
monitor
intervals.
Message
Variables:
pgm
-
The
program
that
issued
the
message
name
-
The
name
of
the
monitor
specified
in
the
command
interval
-
The
new
interval
Administrator
Response:
If
the
interval
is
not
as
expected,
examine
the
NetView
log
for
related
error
messages
and
respond
to
them.
IHS630I
SUBSYSTEM
name
IS
status;
UNABLE
TO
ISSUE
COMMAND:
command
Explanation:
The
IHSBIFIC
program
attempted
to
issue
a
DB2
command
to
a
subsystem,
but
was
unable
to
do
so.
Message
Variables:
name
-
The
DB2
subsystem
to
which
the
command
was
directed
status
-
The
status
of
the
DB2
subsystem,
which
can
be
one
of
the
following:
v
API_ERROR
v
DOWN
v
EXCLUDED
v
MAINT_MODE
v
NOT_MONITORED
v
NOT_REGISTERED
v
SSUP
v
UNCONTACTABLE
v
UNDEFINED
v
UNKNOWN
v
UNSUPPORTED
command
-
The
command
which
was
being
issued
System
Action:
The
program
ends
without
issuing
the
requested
command.
Administrator
Response:
If
the
status
is
API_ERROR
or
NOT_REGISTERED,
examine
the
NetView
log
preceding
this
message
for
more
detailed
error
messages
and
respond
to
them.
If
the
status
is
DOWN,
verify
that
the
DB2
subsystem
has
successfully
initialized
before
issuing
the
command
again.
If
the
status
is
EXCLUDED,
the
subsystem
has
been
defined
in
the
IHS$EXCL
member
for
exclude
processing.
If
the
status
is
MAINT_MODE,
report
the
problem
to
your
DB2
administrator.
If
the
status
is
NOT_MONITORED
or
UNCONTACTABLE,
examine
the
NetView
log
preceding
this
message
for
more
detailed
error
messages,
and
respond
to
them.
This
is
probably
the
result
of
a
configuration
problem.
If
the
status
is
SSUP,
the
subsystem
is
currently
being
processed
by
Tivoli
Business
Systems
Manager,
and
the
final
status
has
not
yet
been
determined.
Try
the
command
again
after
a
short
interval
to
allow
the
process
to
complete.
If
the
message
is
repeated,
report
the
problem
to
IBM
Software
Support.
If
the
status
is
UNDEFINED
or
UNKNOWN,
report
the
problem
to
your
DB2
administrator.
If
the
status
is
UNSUPPORTED,
the
software
level
of
the
DB2
subsystem
is
not
supported
by
Tivoli
Business
Systems
Manager.
IHS631E
pgm
MONITOR
name
CANNOT
BE
MODIFIED
WITH
DSGNAME=DSG;
USE
SSNAME=SUBSYS
Explanation:
The
IHSBTIME
program
has
been
commanded
to
change
the
interval
for
a
monitor,
which
does
not
exist
at
the
Data
Sharing
Group
resource
level.
Message
Variables:
pgm
-
The
program
that
issued
the
message
name
-
The
monitor
name
specified
in
the
command
System
Action:
The
program
ends
without
modifying
the
interval
for
the
specified
monitor.
Administrator
Response:
Probable
user
error.
Identify
the
DB2
subsystem
related
to
the
monitor
and
reissue
Chapter
14.
IHS
Messages
-
IHS307E
-
IHS829I,
IHS0561I
169
the
command,
specifying
SSNAME=subsys
instead
of
DSGNAME=dsg.
IHS632E
SUBSYSTEM
name
IS
INCOMPATIBLE;
UNABLE
TO
ISSUE
COMMAND:
command
Explanation:
The
IHSBIFIC
program
attempted
to
issue
a
DB2
command
to
a
subsystem,
but
was
unable
to
do
so.
Message
Variables:
name
-
The
DB2
subsystem
to
which
the
command
was
directed
command
-
The
command
which
was
being
issued
System
Action:
The
program
ends
without
issuing
the
requested
command.
Administrator
Response:
This
might
be
caused
by
a
configuration
error.
The
version,
release,
or
the
maintenance
level
(or
any
combination
of
these)
of
DSNALI/DSNWLI2
in
the
DB2
STEPLIB
used
by
the
issuing
NetView
region
is
incompatible
with
the
STEPLIB
used
by
the
specified
DB2
subsystem.
IHS633I
pgm
POLLING
MONITOR
name1
FOR
name2
INTERVAL
status
CHANGED
FROM
interval1
TO
interval2.
Explanation:
The
IHSBTIME
program
is
processing
a
request
to
change
the
interval
for
the
monitor.
Message
Variables:
pgm
-
The
program
that
issued
the
message
name1
-
The
name
of
the
monitor
specified
in
the
command
name2
-
The
Data
Sharing
Group
or
subsystem
name
specified
in
the
command
status
-
The
literal
"has
been"
or
"will
be"
interval1
-
The
original
interval
interval2
-
The
new
interval
System
Action:
The
IHSBTIME
program
operates
asynchronously.
Requests
to
change
monitor
intervals
are
first
validated
then
queued
for
implementation.
If
the
status
is
"will
be",
the
request
has
been
validated
and
queued.
If
the
status
is
"has
been",
the
asynchronous
change
has
been
completed.
Administrator
Response:
Verify
that
the
monitor
name,
owning
resource,
and
new
interval
meet
requirements.
If
a
request
has
been
accepted
and
queued,
but
not
completed,
examine
the
NetView
log
for
related
error
messages
and
respond
to
them.
IHS634E
pgm
POLLING
MONITOR
name
FOR
parameter
INTERVAL
WAS
NOT
CHANGED
TO
interval
Explanation:
The
IHSBTIME
program
did
not
change
the
monitor
interval.
Message
Variables:
pgm
-
The
program
that
issued
the
message
name
-
The
name
of
the
monitor
specified
in
the
command
parameter
-
The
DSGNAME=dsg
or
SSNAME=subsys
parameter
as
specified
in
the
command
interval
-
The
new
interval
System
Action:
The
command
is
rejected.
Administrator
Response:
Examine
the
related
error
messages
that
were
returned
to
your
console
and
respond
to
them.
This
message
will
also
be
issued
if
the
new
interval
value
is
the
same
as
the
current
interval.
If
the
monitor
is
IHSBTMCL,
it
might
not
be
in
use
at
your
site.
IHS635E
pgm
UNSUPPORTED
POLLING
MONITOR
NAME:
name
Explanation:
The
IHSBTIME
program
was
requested
to
change
a
monitor
which
is
not
supported.
Message
Variables:
pgm
-
The
program
that
issued
the
message
name
-
The
name
of
the
monitor
specified
in
the
command
System
Action:
The
command
is
rejected.
Administrator
Response:
Correct
the
monitor
name
and
issue
the
command
again.
IHS636E
IHSBIFIC
REQUIRES
AT
LEAST
THREE
KEYWORDS.
ONLY
number
RECEIVED:
parameter1
parameter2
Explanation:
The
IHSBIFIC
program
was
called
with
insufficient
keyword
parameters.
Message
Variables:
number
-
The
number
of
parameters
received
(0–2)
parameter1
-
The
keyword
parameter
1
(if
specified)
parameter2
-
The
keyword
parameter
2
(if
specified)
System
Action:
The
command
is
rejected.
Administrator
Response:
Specify
the
additional
parameters
required
and
issue
the
command
again.
If
the
IHSBIFIC
program
was
called
by
a
system
routine,
report
the
problem
to
IBM
Software
Support.
170
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
IHS637E
IHSBIFIC
UNABLE
TO
LOAD
DSNALI/DSNWLI2:
ABEND
CODE
abend_code
sub_code
Explanation:
The
IHSBIFIC
program
was
unable
to
load
the
DB2
command
interface
module
or
its
alias.
Message
Variables:
abend_code
-
The
abend
code
as
returned
by
the
LOAD
macro
sub_code
-
The
sub
code
as
returned
by
the
LOAD
macro
System
Action:
The
command
is
rejected.
Tivoli
Business
Systems
Manager
will
not
be
able
to
communicate
with
any
DB2
subsystems.
Administrator
Response:
This
is
probably
a
configuration
error.
Follow
the
problem
determination
relevant
to
the
abend
and
subcodes.
IHS638E
IHSBIFIC
RETURNED
AN
ERROR
RESPONSE
AND
number
LINES
OF
OUTPUT
FOR:
command
Explanation:
The
IHSBIFIC
program
issued
a
command
to
a
DB2
subsystem,
which
accepted
the
command
but
only
partially
processed
it.
Message
Variables:
number
-
The
number
of
lines
of
command
response
returned
by
the
DB2
subsystem
command
-
The
command
being
processed
System
Action:
Command
processing
has
been
completed.
Administrator
Response:
Examine
the
command
response
for
the
reason
why
the
DB2
subsystem
did
not
fully
process
the
command.
IHS639E
IHSBIFIC
ENCOUNTERED
THE
FOLLOWING:
text
Explanation:
The
IHSBIFIC
program
encountered
an
unusual
situation.
Message
Variables:
text
-
The
variable
response
from
IHSBIFIC
System
Action:
The
command
ends.
Administrator
Response:
This
is
probably
a
system
error.
Report
the
problem
to
IBM
Software
Support.
IHS640E
pgm
ERROR:
REQUIRE
PARMS
-
REG
|DEREG
|PUSHCMD
|PUSHGLOB
|PULLGLOB
|QUERY
DSG
Explanation:
The
program
was
called
with
insufficient
parameters.
Message
Variables:
pgm
-
The
program
that
detected
the
situation
System
Action:
The
program
ends.
Administrator
Response:
This
is
probably
a
system
error.
If
the
program
was
called
by
the
user,
ensure
that
sufficient
parameters
are
specified.
If
the
program
was
not
called
by
the
user,
report
the
problem
to
IBM
Software
Support.
IHS641E
pgm
ERROR:
UNSUPPORTED
PARM:
parameter
Explanation:
The
program
was
called
with
a
parameter
that
was
not
valid.
Message
Variables:
pgm
-
The
program
that
detected
the
situation
parameter
-
The
parameter
that
was
not
valid
System
Action:
The
program
ends.
Administrator
Response:
This
is
probably
a
system
error.
If
the
program
was
called
by
the
user,
ensure
that
sufficient
parameters
are
specified.
If
the
program
was
not
called
by
the
user,
report
the
problem
to
IBM
Software
Support.
IHS642E
pgm
ERROR:
parameter
REQUIRES
SUBSYS
PARAMETER:
command
Explanation:
The
program
was
called
with
a
parameter
which
also
requires
a
subsystem
specification.
Message
Variables:
pgm
-
The
program
that
detected
the
situation
parameter
-
The
valid
parameter
which
requires
the
additional
subparameter
command
-
A
sample
of
how
the
command
should
have
been
specified
System
Action:
The
program
ends.
Administrator
Response:
This
is
probably
a
system
error.
If
the
program
was
called
by
the
user,
ensure
that
sufficient
parameters
are
specified.
If
the
program
was
not
called
by
the
user,
report
the
problem
to
IBM
Software
Support.
IHS643E
pgm
ERROR:
parm
BAD
RC
(return_code)
ON
queue_name
resource_name
Explanation:
The
program
received
a
non-zero
return
code
from
IHS$LOCK.
Message
Variables:
pgm
-
The
program
that
detected
the
situation
parm
-
The
primary
parameter
passed
to
IHS$LOCK
return_code
-
The
return
code
from
IHS$LOCK
queue_name
-
The
Qname
passed
to
IHS$LOCK
resource_name
-
The
Rname
passed
to
IHS$LOCK
System
Action:
The
enqueue
is
not
processed.
Chapter
14.
IHS
Messages
-
IHS307E
-
IHS829I,
IHS0561I
171
Administrator
Response:
This
is
probably
a
system
error.
Report
the
problem
to
IBM
Software
Support.
IHS645E
pgm
ERROR:
action
NOT
VALID:
THIS
DOMAIN
IS
THE
ACTIVE
MONITOR
FOR
resource
Explanation:
The
requested
action
is
not
valid
for
an
active
monitor.
Message
Variables:
pgm
-
The
program
that
detected
the
situation
action
-
The
action
that
was
requested
resource
-
The
Data
Sharing
Group
that
was
specified
System
Action:
The
program
ends.
Administrator
Response:
This
is
probably
a
system
error.
If
the
program
was
called
by
the
user,
ensure
that
the
correct
parameters
are
specified.
If
the
program
was
not
called
by
the
user,
report
the
problem
to
IBM
Software
Support.
IHS646E
pgm
ERROR:
action
NOT
DONE:
NO
ACTIVE
MONITORING
DOMAIN
FOR
resource
Explanation:
The
requested
action
cannot
be
performed
because
there
is
no
active
monitor
for
the
Data
Sharing
Group.
Message
Variables:
pgm
-
The
program
that
detected
the
situation
action
-
The
action
requested
resource
-
The
Data
Sharing
Group
specified
System
Action:
The
program
ends.
Administrator
Response:
This
is
probably
a
system
error.
If
the
program
was
called
by
the
user,
ensure
that
the
correct
parameters
are
specified.
If
the
program
was
not
called
by
the
user,
report
the
problem
to
IBM
Software
Support.
IHS647I
pgm
function
RETURNED:
response
Explanation:
This
message
is
displayed
if
a
program
decides
to
log
the
response
to
a
request.
Message
Variables:
pgm
-
The
program
that
issued
the
message
function
-
The
function
being
executed
response
-
The
response
from
the
program.
This
is
highly
variable
and
is
for
informational
purposes
only.
IHS648E
pgm
ERROR:
UNABLE
TO
COMMUNICATE
WITH
DOMAIN:
name
OPERATOR:
operator
Explanation:
The
program
was
unable
to
issue
the
RMTCMD
command
to
the
specified
NetView
operator
in
the
specified
domain.
Message
Variables:
pgm
-
The
program
that
detected
the
situation
name
-
The
remote
NetView
domain
operator
-
The
operator
in
the
remote
NetView
domain
System
Action:
The
RMTCMD
command
cannot
be
issued.
An
exception
in
the
format:
IHS648E_%
is
sent
to
the
relevant
DB2
Data
Sharing
Group.
Discovery
and
event
processing
will
be
degraded
or
disabled.
Administrator
Response:
Examine
the
NetView
log
preceding
the
error
message
and
respond
to
the
error
message
or
messages.
Ensure
that
all
relevant
NetView
domains
that
monitor
DB2
subsystems
belonging
to
the
affected
data
sharing
group
are
authorized
to
issue
RMTCMDs
to
each
other,
and
that
they
have
functional
network
connections
at
all
times.
When
the
error
condition
is
corrected,
the
program
resumes
communications.
See
message
IHS649I.
IHS649I
pgm
RESUMED
COMMUNICATIONS
WITH
DOMAIN:
name
OPERATOR:
operator
Explanation:
The
program
was
able
to
issue
the
RMTCMD
command
to
the
specified
NetView
operator
in
the
specified
domain
following
a
previous
failure,
identified
in
message
IHS648E.
Message
Variables:
pgm
-
The
program
that
detected
the
situation
name
-
The
remote
NetView
domain
operator
-
The
operator
in
the
remote
NetView
domain
System
Action:
The
system
resolves
the
IHS648E_%
exception
against
the
relevant
DB2
Data
Sharing
Group.
Administrator
Response:
If
the
situation
occurs
on
a
regular
basis,
the
communication
links
among
the
relevant
NetView
domains
might
require
upgrading.
IHS680W
THRESHOLD
VALUE
FOR
name1
IN
SUBSYSTEM
name2
REJECTED.
DEFAULT
VALUE
OF
number
MINUTES
WILL
BE
USED
Explanation:
The
interval
specified
for
a
monitor
was
unacceptable.
An
acceptable
default
has
been
assigned.
Message
Variables:
name1
-
The
monitor
name
name2
-
The
subsystem
name
number
-
The
default
interval
in
use
172
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
System
Action:
The
monitor
is
set
to
the
default
interval.
Administrator
Response:
Ensure
that
the
requested
interval
is
acceptable
for
the
specified
monitor.
IHS681E
pgm
GLOBAL
VARIABLE
FOR
name
IN
keyword
subsys
NOT
FOUND.
Explanation:
A
required
NetView
global
variable
was
not
defined
for
the
subsystem.
Message
Variables:
pgm
-
The
program
that
detected
the
situation
name
-
The
variable
name
keyword
-
A
keyword
indicating
whether
the
variable
belongs
to
a
DB2
subsystem
or
Data
Sharing
Group
subsys
-
The
subsystem
or
Data
Sharing
Group
name
System
Action:
Processing
of
the
message
ends.
Administrator
Response:
This
is
probably
a
system
error.
Report
the
problem
to
IBM
Software
Support.
IHS682E
pgm
ERROR:
INTERVAL
interval
NOT
NUMERIC.
Explanation:
The
program
was
issued
a
request
to
modify
a
polling
monitor
interval
to
a
non-numeric
value.
Message
Variables:
pgm
-
The
program
that
detected
the
situation
interval
-
The
requested
interval
System
Action:
The
interval
is
not
changed.
Administrator
Response:
Ensure
that
a
valid
interval
is
specified.
IHS683W
pgm
WARNING:
SQL
QUERY
RETURNED
num
LINES
FOR
v1
v2
v3
v4
v5
v6
v7
Explanation:
A
call
to
the
IHSBSQL
program
did
not
return
the
expected
number
of
lines.
Message
Variables:
pgm
-
The
name
of
the
module
num
-
The
number
of
lines
returned
by
IHSBSQL
v1...v7
-
Variable
data
which
specifically
identifies
the
relevant
resource
System
Action:
Further
processing
of
the
resource
is
bypassed.
Administrator
Response:
It
might
be
necessary
to
examine
the
historical
behavior
of
the
relevant
resource
in
order
to
evaluate
the
significance
of
the
number
of
lines
returned.
For
example,
if
the
resource
was
flagged
as
an
exception
in
one
polling
cycle
and
is
deleted
(or
dropped)
before
the
next
polling
cycle,
no
lines
might
be
returned
during
the
resolution
process
for
that
resource.
Further
processing
is
bypassed
and,
for
this
specific
example,
the
exception
remains
unresolved
unless
the
job
scheduling
tool
Delete
Old
IMS
and
DB2
Objects
is
run.
If
number
of
lines
returned
is
two
or
greater,
contact
IBM
Software
Support.
IHS684E
pgm
ERROR:
KEYWORD
keyword
MUST
BE
DSGNAME
OR
SSNAME.
Explanation:
A
keyword
that
was
not
valid
was
passed
to
the
program.
Message
Variables:
pgm
-
The
program
that
detected
the
situation
keyword
-
The
keyword
that
was
not
valid
System
Action:
The
command
is
rejected.
Administrator
Response:
Ensure
that
the
command
parameters
are
correctly
specified.
IHS685W
pgm
WARNING:
type
name
IS
EXCLUDED
FROM
MONITORING.
Explanation:
While
processing
an
event,
the
program
has
determined
that
the
specified
resource
has
been
excluded
from
monitoring.
Message
Variables:
pgm
-
The
program
that
issued
the
message
type
-
The
type
of
resource
name
-
The
name
of
the
resource
System
Action:
Events
related
to
the
specified
resource
are
not
processed.
If
the
program
is
IHSBSSUP,
then
no
discovery
processing
is
performed
for
the
resource.
Administrator
Response:
Confirm
that
the
resource
should
be
excluded
from
monitoring.
IHS686W
pgm
WARNING:
UNABLE
TO
MONITOR
type
name.
Explanation:
The
named
resource
is
not
monitored.
Message
Variables:
pgm
-
The
program
that
issued
the
message
type
-
The
type
of
resource
name
-
The
name
of
the
resource
System
Action:
Events
related
to
the
specified
resource
are
not
processed.
Administrator
Response:
This
message
is
issued
to
alert
the
administrator
to
a
potential
error
condition.
If
the
situation
is
expected,
ignore
this
message.
Otherwise,
examine
the
related
messages
which
were
written
to
the
NetView
log
and
respond
to
them.
Chapter
14.
IHS
Messages
-
IHS307E
-
IHS829I,
IHS0561I
173
IHS687W
member:
INVALID
TIMER
INTERVAL
(value)
SPECIFIED
IN
IHS$PARM
FOR
THE
timer_name
TIMER.
DEFAULT
VALUE
OF
nnnn
MINUTES
WILL
BE
USED.
Explanation:
The
timer
interval
to
be
used
for
the
DB2
Polling
Monitors
must
be
a
numeric
value,
within
the
range
applicable
for
that
timer.
The
minimum
and
maximum
values
for
each
timer
are
documented
in
the
IHSBPRM
member
in
the
SGTMSAMP
data
set,
along
with
the
default
value
to
be
used
if
an
incorrect
value
is
entered.
Message
Variables:
member
-
The
name
of
the
REXX
program
issuing
this
message
value
-
The
value
entered
for
this
timer
that
was
not
valid
timer_name
-
The
specific
timer
affected
(IHSBPOLL,
IHSBCLER,
IHSBRSLV,
or
IHSBTMCL)
nnnn
-
The
default
value
to
be
used
System
Action:
Processing
continues
and
the
default
value
applicable
to
that
timer
is
used.
Administrator
Response:
Correct
the
value
specified
for
the
interval
parameter
in
the
IHS$UPRM
override
member.
To
immediately
update
a
timer
interval
for
a
particular
DB2
subsystem
or
data
sharing
group,
issue
the
Set
Poll
Monitor
Intervals
command
for
the
required
resource
from
the
Tivoli
Business
Systems
Manager
console.
The
IHS$PARM
member
in
the
SGTMSAMP
data
set
contains
includes
for
the
IHSBPRM
and
IHS$UPRM
members
in
SGTMSAMP.
The
IHSBPRM
member
contains
the
default
parameter
settings
for
the
DB2
data
source,
as
supplied
with
Tivoli
Business
Systems
Manager.
This
member
should
not
be
changed.
To
override
the
default
parameter
settings
within
IHSBPRM,
add
the
parameter
with
the
required
value
into
the
IHS$UPRM
override
member
within
SGTMSAMP.
To
introduce
the
changed
values
prior
to
the
next
NetView
startup,
issue
the
IHS$PRMU
REFRESH
command
from
an
NCCF
session.
For
details
of
the
IHS$PRMU
command,
refer
to
the
prolog
of
the
IHS$UPRM
member
in
SGTMSAMP.
IHS688E
member:
INVALID
TOKEN
(token)
DETECTED
IN
MESSAGE
message_id.
MESSAGE
NOT
PROCESSED.
Explanation:
A
token
ID
that
was
not
valid
has
been
parsed
from
an
incoming
DB2
message.
Message
Variables:
member
-
The
name
of
the
REXX
program
issuing
this
message
token
-
The
token
parsed
from
the
incoming
message
message_id
-
The
message
ID
of
the
incoming
message
containing
the
token
that
was
not
valid
System
Action:
Processing
continues
and
the
incoming
message
will
be
ignored.
No
event
will
be
created.
Administrator
Response:
If
you
are
not
interested
in
monitoring
this
particular
message,
remove
all
references
to
it
from
the
NetView
message
automation
table.
Otherwise,
notify
IBM
Software
Support
of
this
error.
IHS689E
pgm
UNABLE
TO
PARSE
RESPONSE
var_1
var_2
var_3
var_4
var_5
Explanation:
The
named
program
was
unable
to
parse
the
response
to
a
command
or
query.
Message
Variables:
pgm
-
The
program
that
detected
the
situation
var_1
through
var_5
-
The
summary
information
describing
the
parsed
response
System
Action:
The
program
performs
additional
error
recovery.
Administrator
Response:
Examine
the
NetView
log
preceding
the
error
message
for
more
detailed
messages.
If
there
are
no
additional
error
messages,
contact
IBM
Software
Support.
IHS700E
INVALID
PARAMETER:
parameter_description
Explanation:
A
parameter
has
been
passed
that
was
not
valid.
Message
Variables:
parameter_description
-
The
type
and
description
of
the
parameter
that
was
passed
Administrator
Response:
Specify
the
correct
parameter.
IHS701I
number
RECORDS
action
object_type
object_name
BY
pgm
Explanation:
The
number
of
records
written
to,
or
read
from,
the
named
object
by
the
named
program.
Message
Variables:
number
-
The
record
count
action
-
The
action
performed,
either
WRITTEN
TO
or
READ
FROM
object_type
-
The
source
or
target,
either
DD,
FILE,
or
DATASET
object_name
-
The
name
of
the
source
or
target
pgm
-
The
name
of
the
program
that
performed
the
action
174
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
IHS702I
pgm
:
END
OF
PROCESSING
Explanation:
The
name
of
the
program
that
has
completed
processing.
Message
Variables:
pgm
-
The
name
of
the
program
that
completed
processing
IHS703I
GATHERING
DATA
-
description
Explanation:
Initial
discovery
processing
is
gathering
data.
Message
Variables:
description
-
The
source
from
where
the
information
is
being
collected
IHS704E
TIVOLI
BUSINESS
SYSTEMS
MANAGER-SA
AUTOTASK
name
IS
NOT
AVAILABLE
Explanation:
The
autotask
is
not
available
to
use
for
the
System
Automation
for
OS/390
interface
processing.
Message
Variables:
name
-
The
name
of
the
autotask
Administrator
Response:
Ensure
that
the
autotask
is
defined
to
NetView
DSIPARM
member
DSIOPF
as
follows:
1.
The
data
set
hlq.SGTMSAMP
is
required
to
be
included
in
the
NetView
started
task
DSIPARM
DD
concatenation.
2.
The
member
hlq.SGTMSAMP(IHS$OPF)
is
required
to
be
included
into
the
NetView
DSIPARM
member
DSIOPFU
or
the
site
equivalent.
Refer
to
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide
for
further
information.
IHS705I
BAD
RC
return_code
reading_from/writing_to
DD
ddname
Explanation:
Initial
discovery
processing
has
found
errors
reading
or
writing
information
during
the
initial
discovery
processing.
Message
Variables:
return_code
-
The
return
code
from
I/O
operation
reading_from/writing_to
-
The
action
being
performed
ddname
-
The
DD
name
of
the
data
set
in
question
as
defined
in
hlq.SGTMSAMP(IHSSBCPJ)
Administrator
Response:
Check
the
return
code
for
the
EXECIO
operation.
Check
the
IHSSBCPJ
JES
joblog
for
errors
If
the
error
is
reading
information,
check
input
data
set
SAINDSN
(ddname)
for
valid
data.
Run
IHSSDISC
again
if
necessary
from
the
NetView
for
z/OS
command
line.
If
the
error
is
writing
information,
check
error
messages
concerning
output
data
set
BCPOUT
in
the
IHSSBCPJ
JES
joblog.
IHS707I
RESOURCE
resource
HAS
A
MONITORING
LEVEL
OF
monitor_level
Explanation:
The
System
Automation
for
OS/390
monitoring
level
of
a
resource
was
changed
by
a
right-click
command
on
the
Tivoli
Business
Systems
Manager
console.
Message
Variables:
resource
-
The
System
Automation
for
OS/390
resource
name
in
the
form
resource/type/system
(for
example,
RMF/APL/TIC1)
monitor_level
-
The
new
monitoring
level
being
applied
to
the
resource.
Every
time
there
is
a
change
in
the
status
of
the
resource
at
this
monitoring
level,
the
new
status
is
propagated
to
the
Tivoli
Business
Systems
Manager
console,
unless
the
monitoring
level
is
set
to
NONE.
The
possible
values
are
as
follows:
Compound
–
use
System
Automation
for
OS/390
compound
status
Observed
–
use
System
Automation
for
OS/390
observed
status
None
–
the
resource
will
not
be
monitored
Default
–
use
the
default
monitoring
level
If
the
value
of
Default
is
specified
as
the
monitoring
level
on
the
Tivoli
Business
Systems
Manager
console,
the
monitoring
level
is
determined
as
follows:
1.
The
first
match
of
the
resource
against
a
resource
mask
specified
in
the
DSIPARM(IHSSMONI)
member.
2.
If
no
resource
masks
are
specified
or
matched,
or
the
IHSSMONI
member
does
not
exist,
the
system
default
of
Compound
is
used.
System
Action:
The
resource
continues
to
be
monitored
using
the
new
monitoring
level.
IHS708I
TIVOLI
BUSINESS
SYSTEMS
MANAGER-SA
INITIALIZATION
COMPLETED
Explanation:
Tivoli
Business
Systems
Manager
is
now
able
to
process
information
passed
from
System
Automation
for
OS/390.
IHS709E
TIVOLI
BUSINESS
SYSTEMS
MANAGER-SA
INTERFACE
IS
TERMINATING
Explanation:
The
Tivoli
Business
Systems
Manager
interface
with
System
Automation
for
OS/390
is
ending
because
of
an
error.
Administrator
Response:
Check
the
active
NetView
netlog
for
errors.
Chapter
14.
IHS
Messages
-
IHS307E
-
IHS829I,
IHS0561I
175
IHS710I
LOADING
IHS$EXCL
SINCE
IT
IS
NOT
CURRENTLY
LOADED
Explanation:
This
message
is
issued
when
the
IHS$EXCL
member
is
loaded
from
the
DSIPARM
DD
for
the
first
IMS
or
DB2
event
generated
since
the
NetView
startup.
IHS711I
IHS#EXCL
VALID
OPTIONS
ARE:
Explanation:
This
multiline
message
is
issued
when
the
IHS#EXCL
command
is
issued
with
an
option
that
is
not
valid.
The
options
are:
SHOW
Shows
the
current
loaded
filter
and
statistics
REFRESH
Refreshes
the
filter
from
the
IHS$EXCL
DSIPARM
member
CHECK
Checks
the
type,
resource_name,
and
event_id
Administrator
Response:
Enter
the
command
again
with
a
valid
option.
IHS712E
RESOURCE_TYPE
type
IS
NOT
SUPPORTED.
Explanation:
This
message
is
issued
when
an
unsupported
resource_type
is
specified
in
the
IHS$EXCL
member,
or
in
the
IHS#EXCL
CHECK
command.
Message
Variables:
type
-
The
type
of
resource
Administrator
Response:
Refer
to
the
IHS$EXCL
DSIPARM
member
for
a
list
of
supported
resource
types.
IHS713I
IHS$EXCL
DSIPARM
MEMBER
HAS
BEEN
LOADED
FOR
SYSNAME
sys_name
Explanation:
This
message
is
issued
when
the
IHS$EXCL
member
has
been
loaded
from
the
DSIPARM
DD.
The
filters
are
listed
as
part
of
this
multiline
message.
Message
Variables:
sys_name
-
The
z/OS
system
name
IHS714I
IHS$EXCL
DSIPARM
HAS
NO
FILTERS
FOR
SYSNAME
sys_name
Explanation:
This
message
is
issued
when
the
IHS#EXCL
SHOW
command
is
used
and
no
filters
are
active
for
this
system.
Message
Variables:
sys_name
-
The
z/OS
system
name
Administrator
Response:
If
this
message
is
unexpected,
review
the
IHS$EXCL
DSIPARM
member.
Issue
the
IHS#EXCL
REFRESH
command
to
load
the
IHS$EXCL
member
from
the
DSIPARM
DD.
IHS715I
IHS$EXCL
WAS
LOADED
date
time
FROM
dsn
Explanation:
This
message
is
issued
when
the
IHS#EXCL
SHOW
command
is
used.
The
current
loaded
filters
and
statistics
are
also
listed
as
part
of
this
multiline
message.
Message
Variables:
date
-
The
date
the
IHS$EXCL
member
was
loaded
from
the
DSIPARM
DD
time
-
The
time
the
IHS$EXCL
member
was
loaded
from
the
DSIPARM
DD
dsn
-
The
DSN
where
the
IHS$EXCL
member
was
loaded
IHS716E
VALID
PARMS
ARE:
Resource_Type
Resource_Name
{Event_ID}
Explanation:
The
IHS#EXCL
CHECK
command
was
called
with
incorrect
parameters.
The
following
are
the
valid
parameters:
Resource_Type
Valid
resource
type
as
documented
in
the
IHS$EXCL
SGTMSAMP
member
(required)
Resource_Name
The
name
of
the
resource
(required)
Event_ID
The
ID
of
the
event
(optional)
For
more
information
about
the
parameters,
refer
to
SGTMSAMP
member
IHS$EXCL.
The
following
are
examples
of
the
correct
IHS#EXCL
CHECK
calls:
v
IHS#EXCL
CHECK
DBSS
DB6A
v
IHS#EXCL
CHECK
IMPG
PGM1
DFS1234
Administrator
Response:
If
this
is
in
a
response
to
a
user
command,
enter
the
command
again
with
valid
parameters.
If
not,
contact
IBM
Software
Support.
IHS717I
RC
return_code
reason_code
Explanation:
This
message
is
issued
when
the
IHS#EXCL
CHECK
command
is
used.
Message
Variables:
return_code
-
The
return
code
is
0
or
4
reason_code
-
The
reason
code
is:
0
Matched
=>
Exclude
4
NO-Match
=>
Include
IHS718I
job_name
(job_id)
HAS
action_taken
number
data_source
DISCOVERY
RECORDS
FOR
subsystem
TO
NT.
(obj_type)
Explanation:
If
the
action_taken
is
BEEN
SUBMITTED
TO
SEND,
more
items
were
encountered
during
a
subsystem
discovery
than
the
limit
specified
in
the
IHS$DISC_FROM
job.
A
batch
job
was
submitted
to
process
those
events.
176
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
If
the
action_taken
is
SUCCESSFULLY
SENT,
the
events
were
successfully
sent
by
the
batch
job.
If
the
action_taken
is
FAILED
TO
SEND,
the
batch
job
failed.
Message
Variables:
job_name
(job_id)
-
The
name
of
the
job
that
was
submitted
or
completed.
In
the
case
of
submitted,
the
JES
job
ID
is
listed
with
the
job
name.
action_taken
-
The
status
of
the
batch
job.
The
following
are
the
valid
values:
v
BEEN
SUBMITTED
TO
SEND
v
SUCCESSFULLY
SENT
v
FAILED
TO
SEND
number
-
The
number
of
discovery
records
sent
data_source
-
The
data
source
producing
the
records
(usually
IMS
or
DB2)
subsystem
-
The
subsystem
for
which
discovery
records
were
created
obj_type
-
The
object
type
of
the
subsystem
System
Action:
If
the
action_taken
is
BEEN
SUBMITTED
TO
SEND,
the
job
is
submitted
by
an
internal
reader
for
batch
processing
and
processing
continues.
If
the
action_taken
is
SUCCESSFULLY
SENT
or
FAILED
TO
SEND,
processing
ends.
Administrator
Response:
If
the
action_taken
is
BEEN
SUBMITTED
TO
SEND,
records
are
usually
processed
in
batch
to
avoid
flooding
the
source/390
address
spaces
and
the
Tivoli
Business
Systems
Manager
distributed
servers.
If
bulk
discovery
processing
is
appropriate,
no
action
is
necessary.
If
bulk
discovery
processing
is
not
appropriate,
review
the
defined
threshold
(for
IMS
and
DB2
data
sources,
the
IHS$DISC_FROM
parameter
in
the
IHS$PRM
and
IHS$UPRM
SGTMSAMP
members).
Refer
to
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide
for
more
information
about
source/390
bulk
discovery.
If
the
action_taken
is
SUCCESSFULLY
SENT,
no
response
is
required.
If
the
action_taken
is
FAILED
TO
SEND,
review
why
the
job
failed
(for
example,
a
JCL
error,
security
problem,
or
destination
specification
error).
If
possible,
correct
the
error
and
submit
the
job
again.
Otherwise,
reschedule
the
discovery
of
the
subsystem
in
question
using
the
right-click
function.
This
typically
submits
a
new
IHS$DISC
job.
IHS719I
number
feed
type
RECORDS
FOR
nvsubsys
HAVE
BEEN
SENT
TO
NT
VIA
PUMP
SESSION
Explanation:
This
is
an
informational
message.
A
number
of
events
were
processed
in
bulk.
The
number
of
these
events
does
not
exceed
the
threshold
set
by
the
IHS$DISC_FROM
parameter
in
IHS$PRM
or
by
way
of
an
override
in
IHS$UPRM,
and
events
were
sent
by
way
of
the
source/390
pump.
Message
Variables:
number
-
The
number
of
events
sent
feed
-
The
data
source
sending
the
event
(for
example,
IMS,
DB2)
type
-
The
type
of
records
(DISCOVERY
or
EVENT)
nvsubsys
-
The
job
name
of
the
NetView
subsystem
sending
the
records
System
Action:
The
events
are
sent
by
way
of
the
source/390
pump.
Administrator
Response:
The
default
value
of
the
IHS$DISC_FROM
parameter
is
specified
within
the
IHS$PRM
member
in
the
SGTMSAMP
data
set.
This
member
should
not
be
changed.
To
override
this
value,
add
the
IHS$DISC_FROM
parameter
with
the
required
value
into
the
IHS$UPRM
override
member
within
SGTMSAMP.
To
introduce
the
changed
values
prior
to
the
next
NetView
startup,
issue
the
IHS$PRMU
REFRESH
command
from
an
NCCF
session.
For
details
of
the
IHS$PRMU
command,
refer
to
the
prolog
of
the
IHS$UPRM
member
in
SGTMSAMP.
For
further
details
regarding
the
IHS$DISC_FROM
parameter,
refer
to
the
prolog
that
precedes
this
parameter
in
the
IHSIPRM
member
in
SGTMSAMP.
IHS720I
event_logging_text
Explanation:
This
message
is
issued
when
the
IHS_LOGGING
logging
variable
is
set
to
ON.
It
is
to
display
internal
logging
events
data
and
is
only
for
use
by
IBM
Software
Support.
Message
Variables:
event_logging_text
-
The
text
display
of
the
events
been
processed
IHS721E
INSTORE
DSIPARM.IHS$DISC
LOCAL
FAILED
RC
retcode
Explanation:
The
IHS$DISC
JCL
template
in
DSIPARM
has
variables
that
are
resolved
before
being
submitted.
The
NetView
SUBMIT
command
is
used
to
submit
the
JCL.
The
resolved
JCL
is
temporarily
saved
as
a
local
in-storage
DSIPARM
member
which
the
NetView
SUBMIT
command
will
access.
The
NetView
PIPE
INSTORE
DSIPARM.IHS$DISC
LOCAL
stage
command
failed
with
the
return
code
listed.
Message
Variables:
retcode
-
The
return
code
as
returned
in
the
secondary
output
steam
from
the
Chapter
14.
IHS
Messages
-
IHS307E
-
IHS829I,
IHS0561I
177
NetView
PIPE
INSTORE
stage
System
Action:
The
IHS$DISC
is
not
submitted.
Administrator
Response:
Refer
to
the
NetView
online
help
or
IBM
Tivoli
NetView
for
z/OS
Programming:
Pipes
for
an
explanation
of
the
return
code
from
the
PIPE
INSTORE
stage
command.
IHS722E
ddname
action
FAILED
RC
return_code
Explanation:
An
attempt
to
perform
a
file
operation
against
ddname
failed.
Message
Variables:
ddname
-
The
DD
name
of
the
file
action
-
The
file
operation
being
performed.
Valid
actions
are
READ,
WRITE,
or
CLOSE.
return_code
-
The
return
code
received
from
the
EXECIO
operation
System
Action:
If
this
error
occurs
within
the
NetView
program,
the
discovery
events
for
the
subsystem
are
not
sent,
and
processing
continues.
If
this
error
occurs
when
running
batch
initial
discovery,
the
job
ends.
Administrator
Response:
If
you
are
unable
to
determine
the
reason
for
the
failure,
contact
IBM
Software
Support.
IHS723E
FLDNUM
field_id
IS
NOT
VALID
FOR
format\action
Explanation:
The
IHSMSG
internal
routine
received
an
event
which
contains
a
field
that
is
not
valid.
Message
Variables:
field_id
-
A
numeric
value
which
is
the
internal
representation
of
the
field
in
error
format
-
A
numeric
value
which
is
the
internal
representation
of
the
Tivoli
Business
System
Manager
feed
action
-
A
numeric
value
which
indicates
if
this
is
an
exception,
resolution,
or
discovery
event
System
Action:
The
event
is
bypassed
and
processing
continues.
Administrator
Response:
This
is
an
internal
error
to
assist
in
the
diagnosis
of
the
problem.
Review
the
netlog
for
associated
messages
and
contact
IBM
Software
Support.
IHS724I
DISCOVERY
REQUEST
FOR
resource
HAS
BEEN
ACCEPTED.
Explanation:
The
system
has
accepted
a
request
to
perform
mouse-click
discovery
for
a
resource.
Message
Variables:
resource
-
The
resource
that
will
be
discovered
System
Action:
Mouse-click
discovery
operates
asynchronously.
Requests
to
perform
discovery
are
first
validated,
then
queued,
for
processing.
This
enables
the
console
to
be
used
for
other
processing
while
the
discovery
continues.
Administrator
Response:
If
a
request
has
been
accepted
and
queued,
but
not
completed,
examine
the
NetView
log
for
related
error
messages
and
respond
to
them.
IHS727E
MSG
NUMBER
IS
NOT
IN
RANGE
300
TO
upper_limit
–
msg_number
Explanation:
The
internal
routine
IHS$MSG
attempted
to
issue
a
message
outside
the
allowed
range.
Message
Variables:
upper_limit
-
The
highest
IHS
number
message
issued
msg_number
-
The
message
number
in
error
System
Action:
The
request
is
rejected
and
processing
continues.
Administrator
Response:
This
is
an
internal
error.
Contact
IBM
Software
Support.
IHS729I
PERFORMING
IBM
TIVOLI
BUSINESS
SYSTEMS
MANAGER
MIGRATION
TASKS
Explanation:
Tivoli
Business
Systems
Manager
has
detected
that
this
is
the
first
time
the
current
release
has
been
run.
System
Action:
Tivoli
Business
Systems
Manager
performs
migration
tasks
for
IMS.
IHS730I
(command)
A
VALUE
FOR
THE
feed_name
job_subsystem
NAME
PARAMETER
MUST
BE
SPECIFIED
Explanation:
The
IMS
or
DB2
discovery
command
entered
from
the
Tivoli
Business
Systems
Manager
console
did
not
identify
the
name
of
the
systems
to
be
discovered.
For
an
IMS
discovery
command,
enter
a
valid
value
into
the
IMS
Jobname
parameter
field.
For
a
DB2
discovery
command,
enter
a
valid
value
into
the
DB2
Subsystem
parameter
field.
Message
Variables:
command
-
The
name
of
the
command
feed_name
-
The
name
of
the
Tivoli
Business
Systems
Manager
data
resource.
For
example,
IMS
or
DB2.
job_subsystem
-
For
an
IMS
discovery,
the
value
is
JOB.
For
a
DB2
discovery,
the
value
is
SUBSYSTEM.
System
Action:
The
command
is
rejected.
Administrator
Response:
For
an
IMS
discovery,
the
value
entered
into
the
IMS
Jobname
parameter
is
used
to
populate
the
second
parameter
of
the
IHS$RDIS
command.
Similarly
for
a
DB2
discovery,
the
value
entered
into
the
DB2
Subsystem
parameter
is
used
to
populate
the
second
parameter
of
the
IHS$RDIS
178
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
command.
The
Tivoli
Business
Systems
Manager
console
sends
the
IHS$RDIS
command
to
the
host
system
to
perform
the
required
discovery.
See
the
IHS820I
message
for
details
of
the
syntax
required
for
the
second
parameter
of
the
IHS$RDIS
command.
IHS742I
module
–
UNEXPECTED
OUTPUT
RECEIVED
FROM
IMS
(jobname)
DISPLAY
COMMAND
Explanation:
The
module
issued
an
IMS
display
command
and
the
output
received
did
not
contain
the
expected
text.
Message
Variables:
module
-
The
name
of
the
REXX
module
jobname
-
The
Job
Name
of
the
IMS
Control
Region
System
Action:
All
processing
requiring
the
output
from
this
display
command
is
stopped
and
processing
continues.
This
message
is
usually
followed
by
message
numbers
IHS332E
or
IHS750I
with
the
text
of
the
output
received.
IHS743W
NUMBER
OF
type
EVENTS
(number)
FOR
subsystem
EXCEEDS
THRESHOLD
(threshold).
Explanation:
A
poll
monitor
has
detected
resources
in
error
for
this
subsystem,
however
the
number
of
resources
in
error
exceeds
the
threshold
specified
by
the
IHSI.$POLLTHRESH
parameter
for
IMS
resources,
or
the
IHSBPOLL.THRESHOLD
parameter
for
DB2
resources.
For
IMS
resources,
the
IHSI.$POLLTHRESH
parameter
is
specified
within
IHSIPRM
or
by
way
of
an
override
within
IHS$UPRM.
For
DB2
resources,
the
IHSBPOLL.THRESHOLD
parameter
is
specified
within
IHSBPRM
or
by
way
of
an
override
within
IHS$UPRM.
Message
Variables:
type
-
The
type
of
resource.
The
type
can
be
MESSAGE/EXCEPTION
for
DB2,
and
DATABASE,
PROGRAM,
or
TRANSACTION
for
IMS.
number
-
The
number
of
resources
in
error
subsystem
-
The
name
of
the
DB2
subsystem
name
or
the
job
name
of
the
IMS
control
region
threshold
-
The
threshold
value
System
Action:
No
exception
events
for
the
named
type
are
sent.
One
IHS743W
event
is
sent.
No
further
events
for
this
resource
type
and
subsystem
will
be
sent
until
the
number
of
resources
in
error
for
this
subsystem
is
reduced
below
the
threshold.
Administrator
Response:
Perform
the
action
typically
done
when
a
resource
is
found
in
error
by
a
poll
monitor.
For
IMS
resources,
the
default
value
of
the
IHSI.$POLLTHRESH
parameter
is
specified
within
the
IHSIPRM
member
in
the
SGTMSAMP
data
set.
This
member
should
not
be
changed.
To
override
this
value,
add
the
IHSI.$POLLTHRESH
parameter
with
the
required
value
into
the
IHS$UPRM
override
member
within
SGTMSAMP.
For
DB2
resources,
the
default
value
of
the
IHSBPOLL.THRESHOLD
parameter
is
specified
within
the
IHSBPRM
member
in
the
SGTMSAMP
data
set.
This
member
should
not
be
changed.
To
override
this
value,
add
the
IHSBPOLL.THRESHOLD
parameter
with
the
required
value
into
the
IHS$UPRM
override
member
within
SGTMSAMP.
To
introduce
the
changed
values
prior
to
the
next
NetView
startup,
issue
the
IHS$PRMU
REFRESH
command
from
an
NCCF
session.
For
details
of
the
IHS$PRMU
command,
refer
to
the
prolog
of
the
IHS$UPRM
member
in
SGTMSAMP.
For
further
details
regarding
the
IMS
IHSI.$POLLTHRESH
parameter,
refer
to
the
prolog
that
precedes
this
parameter
in
the
IHSIPRM
member
in
SGTMSAMP.
For
the
DB2
IHSBPOLL.THRESHOLD
parameter,
refer
to
the
prolog
that
precedes
this
parameter
in
the
IHSBPRM
member
in
SGTMSAMP.
IHS744I
NUMBER
OF
type
EVENTS
FOR
subsystem
NO
LONGER
EXCEEDS
THRESHOLD.
Explanation:
An
IHS743I
message
was
previously
issued
and
the
number
of
resources
in
error
for
this
subsystem
has
fallen
below
the
threshold
specified
by
the
IHSI.$POLLTHRESH
parameter
for
IMS
resources,
or
the
IHSBPOLL.THRESHOLD
parameter
for
DB2
resources.
For
IMS
resources,
the
IHSI.$POLLTHRESH
parameter
is
specified
within
the
IHSIPRM
member
in
the
SGTMSAMP
data
set,
or
by
way
of
an
override
within
the
IHS$UPRM
member.
For
DB2
resources,
the
IHSBPOLL.THRESHOLD
parameter
is
specified
within
the
IHSBPRM
member
in
the
SGTMSAMP
data
set,
or
by
way
of
an
override
within
the
IHS$UPRM
member.
Message
Variables:
type
-
The
type
of
resource.
The
type
can
be
MESSAGE/EXCEPTION
for
DB2,
and
DATABASE,
PROGRAM,
or
TRANSACTION
for
IMS.
subsystem
-
The
name
of
the
DB2
subsystem
name
or
the
job
name
of
the
IMS
control
region
System
Action:
The
previous
IHS743W
state
is
cleared,
and
exception
events
for
this
resource
and
subsystem
are
now
sent
as
usual.
Administrator
Response:
Refer
to
message
number
IHS743W
about
amending
the
IHSI.$POLLTHRESH
and
IHSBPOLL.THRESHOLD
parameter
settings.
Chapter
14.
IHS
Messages
-
IHS307E
-
IHS829I,
IHS0561I
179
IHS745E
IHS$EVTQ_LIMIT
limit
HAS
BEEN
EXCEEDED.
EVENTS
HAVE
BEEN
LOST.
Explanation:
This
message
is
issued
when
the
number
of
queued
events
within
the
NetView
program
exceeds
the
value
set
by
the
IHS$EVTQ_LIMIT
parameter.
The
IHS$EVTQ_LIMIT
parameter
is
specified
within
the
IHS$PRM
member
in
the
SGTMSAMP
data
set,
or
by
way
of
an
override
within
the
IHS$UPRM
member.
The
events
are
only
queued
when
there
has
been
a
failure
to
send
an
event
to
the
pump
by
way
of
the
PPI.
Message
Variables:
limit
-
The
current
IHS$EVTQ_LIMIT
setting
System
Action:
The
queue
is
automatically
condensed
to
keep
the
most
recent
events
for
each
subsystem.
In
addition,
where
possible,
an
IHS745E
exception
event
is
put
on
the
queue
per
subsystem
to
indicate
that
events
have
been
lost.
Administrator
Response:
Determine
the
reason
the
queue
is
full.
See
the
IHS746E
messages
in
the
netlog.
Before
increasing
the
IHS$EVTQ_LIMIT,
see
the
tuning
considerations
section
for
NetView
in
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide.
The
default
value
of
the
IHS$EVTQ_LIMIT
parameter
is
specified
within
the
IHS$PRM
member
in
the
SGTMSAMP
data
set.
This
member
should
not
be
changed.
To
increase
this
value,
add
the
IHS$EVTQ_LIMIT
parameter
with
the
increased
value
into
the
IHS$UPRM
override
member
within
SGTMSAMP.
To
introduce
the
changed
values
prior
to
the
next
NetView
startup,
issue
the
IHS$PRMU
REFRESH
command
from
an
NCCF
session.
For
details
of
the
IHS$PRMU
command,
refer
to
the
prolog
of
the
IHS$UPRM
member
in
SGTMSAMP.
For
further
details
regarding
the
IHS$EVTQ_LIMIT
parameter,
refer
to
the
prolog
that
precedes
this
parameter
in
the
IHS$PRM
member
in
SGTMSAMP.
IHS746E
SEND
TO
PPI
RECEIVER
rcvrid
FAILED
WITH
RC
retcode.
reason
Explanation:
A
send
to
the
pump
PPI
receiver
rcvrid
failed
with
PPI
return
code
retcode.
The
return
codes
and
reasons
are
as
follows:
Return
Code
Reason
4
TBSM
PUMP
PPI
RECEIVER
IS
INACTIVE
24
NETVIEW
PPI
IS
NOT
ACTIVE
26
TBSM
PUMP
IS
NOT
ACTIVE
WITH
PPI=YES
28
NETVIEW
SUBSYSTEM
IS
ACTIVE
WITH
NOPPI
35
TBSM
PUMP
PPI_BUFFER_QUEUE_LIMIT
HAS
BEEN
EXCEEDED
These
are
command
return
codes.
For
other
return
codes,
the
reason
REFER
TO
THE
NETVIEW
APPLICATION
PROGRAMMER’S
GUIDE
is
received.
Message
Variables:
rcvrid
-
The
pump
PPI
receiver
ID,
which
is
NETVAOP
by
default
retcode
-
The
PPI
return
code
reason
-
A
short
description
of
the
PPI
return
code
System
Action:
Events
will
be
queued.
In
the
case
that
the
Tivoli
Business
Systems
Manager
pump
was
not
active
and
is
started,
the
queued
events
will
be
sent
to
the
pump
as
soon
as
the
PPI
receiver
becomes
active
(by
way
of
a
trap
in
IHS$MAT).
To
handle
other
cases,
such
as
PPI
queue
full
condition,
a
timer
is
used
to
try
again.
The
timer
is
automatically
started
when
a
failure
occurs,
for
the
number
of
minutes
specified
by
the
IHS$EVTQ_INTERVAL
parameter
in
the
SGTMSAMP
member
IHS$PRM,
or
by
way
of
an
override
within
the
IHS$UPRM
member.
The
timer
is
automatically
stopped
when
all
the
events
in
the
queue
have
been
successfully
sent
to
the
PPI.
Administrator
Response:
Depending
on
the
reason
listed,
make
sure
the
NetView
PPI
is
active,
the
pump
is
active,
and
the
pump
has
been
configured
with
PPI=YES.
The
NetView
DISPPI
command
lists
the
status
of
the
PPI
receiver.
If
it
is
INACTIVE
and
the
pump
is
active,
then
issue
the
pump
PPI
ENABLE
command.
The
default
value
of
the
IHS$EVTQ_INTERVAL
parameter
is
specified
within
the
IHS$PRM
member
in
the
SGTMSAMP
data
set.
This
member
should
not
be
changed.
To
amend
this
value,
add
the
IHS$EVTQ_INTERVAL
parameter
with
the
amended
value
into
the
IHS$UPRM
override
member
within
SGTMSAMP.
To
introduce
the
changed
values
prior
to
the
next
NetView
startup,
issue
the
IHS$PRMU
REFRESH
command
from
an
NCCF
session.
For
details
of
the
IHS$PRMU
command,
refer
to
the
prolog
of
the
IHS$UPRM
member
in
SGTMSAMP.
For
further
details
regarding
the
IHS$EVTQ_INTERVAL
parameter,
refer
to
the
prolog
that
precedes
this
parameter
in
the
IHS$PRM
member
in
SGTMSAMP.
IHS747I
THERE
ARE
CURRENTLY
num
QUEUED
EVENTS
IN
NETVIEW
Explanation:
A
previous
error
has
prevented
events
from
being
sent
to
the
PPI
receiver,
resulting
in
events
being
queued.
This
message
might
have
been
issued
from
an
attempt
by
Tivoli
Business
Systems
Manager
to
retry
sending
these
events
to
the
PPI
receiver.
Message
Variables:
num
-
The
number
of
queued
events
180
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
Administrator
Response:
Determine
why
the
PPI
receiver
is
not
functioning
and
resolve
the
problem.
See
the
description
for
message
number
IHS746E
for
more
information.
IHS748I
num
QUEUED
EVENTS
HAVE
BEEN
SENT
TO
PPI
RECEIVER
rcvrid
Explanation:
This
message
indicates
the
number
of
queued
events
that
have
successfully
been
sent
to
the
PPI
receiver
and
removed
from
the
NetView
queue.
See
IHS746E
messages
in
the
netlog
for
more
information
about
the
events.
Message
Variables:
num
-
The
number
of
queued
events
rcvrid
-
The
pump
PPI
receiver
ID,
which
is
NETVAOP
by
default
IHS750I
OUTPUT
DISPLAY
FOLLOWS:
Explanation:
This
is
issued
as
a
header
message
preceding
the
display
of
data
from
a
Tivoli
Business
Systems
Manager
process.
This
is
preceded
by
another
Tivoli
Business
Systems
error
or
informational
message.
System
Action:
Processing
continues.
Administrator
Response:
Review
the
data
following
this
message,
together
with
any
relevant
previous
messages,
and
take
any
action
as
required.
IHS751I
COMMAND
IN
module_name
TIMED
OUT
Explanation:
The
routine
module_name
received
no
response
from
an
attempt
to
issue
a
command
to
another
subsystem
(usually
MVS
or
IMS)
within
the
maximum
time
period
specified
by
the
IHSI.$CORRWAIT
parameter.
Message
Variables:
module_name
-
The
name
of
the
module
Administrator
Response:
For
IMS,
the
default
value
of
the
IHSI.$CORRWAIT
parameter
is
specified
within
the
IHSIPRM
member
in
the
SGTMSAMP
data
set.
This
member
should
not
be
changed.
To
increase
the
delay
value,
add
the
IHSI.$CORRWAIT
parameter
with
the
required
value
into
the
IHS$UPRM
override
member
within
SGTMSAMP.
To
introduce
the
changed
values
prior
to
the
next
NetView
startup,
issue
the
IHS$PRMU
REFRESH
command
from
an
NCCF
session.
For
details
of
the
IHS$PRMU
command,
refer
to
the
prolog
of
the
IHS$UPRM
member
in
SGTMSAMP.
For
further
details
regarding
the
IHSI.$CORRWAIT
parameter,
refer
to
the
prolog
that
precedes
this
parameter
in
the
IHSIPRM
member
in
SGTMSAMP.
If
this
does
not
resolve
the
problem,
contact
IBM
Software
Support.
IHS752I
DEFAULT
VALUE
nn
USED
FOR
cglobal
Explanation:
This
is
issued
when
cglobal
has
no
value
or
an
incorrect
value
is
defined
in
one
of
the
members
from
the
SGTMSAMP
data
set
that
is
included
by
IHS$PARM.
A
default
value
of
nn
is
used
and
saved
in
that
common
global
variable.
Message
Variables:
nn
-
The
default
value
being
used
cglobal
-
The
common
global
variable
System
Action:
The
default
value
is
used
and
processing
continues.
Administrator
Response:
If
this
common
global
variable
is
in
the
IHS$UPRM
member,
correct
the
value
set.
If
not,
check
the
value
set
for
the
parameter
in
the
SGTMSAMP
members
included
by
IHS$PARM.
If
this
common
global
variable
is
not
present
in
any
of
the
above
SGTMSAMP
members,
create
an
entry
in
the
IHS$UPRM
member.
The
IHS$PARM
SGTMSAMP
member
contains
a
number
of
includes,
these
are
for
the
IHS$PRM,
IHSIPRM
(IMS
data
source),
IHSBPRM
(DB2
data
source),
and
IHSSPRM
(SA390
data
source)
parameter
members.
These
contain
default
parameter
settings
for
their
respective
data
sources,
as
supplied
with
Tivoli
Business
Systems
Manager.
The
IHS$PRM,
IHSIPRM,
IHSBPRM,
and
IHSSPRM
members
should
not
be
changed.
To
override
the
default
parameter
settings
within
these
members,
add
the
parameter
with
the
required
value
to
the
IHS$UPRM
override
member
in
the
SGTMSAMP
data
set.
For
further
details,
refer
to
the
prolog
at
the
beginning
of
each
of
these
members
in
SGTMSAMP.
To
introduce
the
changed
values
prior
to
the
next
NetView
startup,
issue
the
IHS$PRMU
REFRESH
command
from
an
NCCF
session.
For
details
of
the
IHS$PRMU
command,
refer
to
the
prolog
of
the
IHS$UPRM
member
in
SGTMSAMP.
IHS753W
ATTEMPTED
TO
ALLOCATE
MORE
THAN
num
DATASETS
TO
DDNAME
ddname.
ONLY
FIRST
num
PROCESSED.
Explanation:
During
an
attempt
to
read
and
process
several
data
sets
related
to
a
subsystem,
it
was
discovered
that
there
were
more
data
sets
in
the
concatenation
than
Tivoli
Business
Systems
Manager
is
capable
of
processing.
Message
Variables:
num
-
The
maximum
number
of
data
sets
in
the
concatenation
that
can
be
processed
ddname
-
The
DDNAME
to
which
Tivoli
Business
Systems
Manager
was
attempting
to
allocate
these
data
sets
System
Action:
Tivoli
Business
Systems
Manager
only
processes
the
first
num
data
sets
in
the
concatenation.
The
remaining
data
sets
are
ignored.
Administrator
Response:
Review
the
concatenation
to
determine
whether
the
libraries
following
the
Chapter
14.
IHS
Messages
-
IHS307E
-
IHS829I,
IHS0561I
181
maximum
number
might
contain
useful
information
for
Tivoli
Business
Systems
Manager.
If
possible,
rearrange
the
concatenation
to
get
these
within
the
limit.
If
necessary,
contact
IBM
Software
Support
to
have
the
limit
increased.
IHS810I
num
type
JOBS
FOUND
BY
routine
Explanation:
This
message
reports
the
number
of
jobs
of
a
particular
type
found
during
processing.
Message
Variables:
num
-
The
number
of
jobs
found
type
-
The
type
of
job,
for
example
CICS
routine
-
The
name
of
the
routine
that
found
the
jobs
System
Action:
Processing
continues.
Administrator
Response:
Investigate
the
reason
for
the
failure.
If
you
cannot
determine
the
problem,
add
the
DEBUG
option
to
the
DISCOVER
request
parameter
string,
and
review
the
IHS402I
debug
messages
in
the
AOPLOG
data
definition.
If
you
still
cannot
determine
the
problem,
contact
IBM
Software
Support.
IHS811I
DISCOVER
NAME=name
TYPE=type
–
status
Explanation:
An
IHSSDJLJ
batch
job,
or
Pump
DISCOVER
modify
command,
has
started
or
completed.
Message
Variables:
name
-
The
value
of
the
Name
parameter
used
by
this
Discover
request.
This
is
a
wildcard
mask
that
is
compared
against
the
names
of
each
active
Address
Space.
type
-
The
value
of
the
Type
parameter
used
by
this
Discover
request.
The
values
are
STC,
JOB,
or
ALL.
status
-
The
status
of
this
Discover
request.
The
values
are
STARTED
or
COMPLETED.
System
Action:
Processing
continues.
IHS812E
ERROR
IN
IHSSDJL
–
reason
Explanation:
The
IHSSDJLJ
batch
job,
or
Pump
DISCOVER
modify
command,
has
failed.
Message
Variables:
reason
-
The
following
reasons
can
exist:
IHSSDJL
CAN
ONLY
BE
INVOKED
FROM
A
PUMP
ENVIRONMENT
The
IHSSDJL
program
was
incorrectly
started
from
outside
of
the
Pump
environment.
For
example,
this
program
cannot
be
started
from
the
NetView
program.
UNKNOWN
PARAMETER
'parm'.
VALID
ARE:
NAME=namemask
TYPE=STC|JOB|ALL
DDNAME=bcpdd
The
DISCOVER
parameters
were
not
valid
NO
REPLY
FROM
D
J,L
COMMAND
There
was
no
reply
from
the
D
J,L
command
UNEXPECTED
MESSAGE
message
The
reply
from
the
D
J,L
command
was
not
message
IEE114I
WRITE
TO
DDNAME
ddname
FAILED
A
write
to
the
data
definition
ddname
failed.
There
will
be
other
messages
that
provide
more
information
on
the
failure.
System
Action:
The
Discovery
process
ends.
Administrator
Response:
Investigate
the
reason
for
the
failure.
If
you
cannot
determine
the
problem,
add
the
DEBUG
option
to
the
DISCOVER
request
parameter
string,
and
review
the
IHS402I
debug
messages
in
the
AOPLOG
data
definition.
If
you
still
cannot
determine
the
problem,
contact
IBM
Software
Support.
IHS813E
MODULE
name
ENCOUNTERED
VERSION
RELATED
ERROR
WITH
product
Explanation:
The
module
called
is
not
valid
for
the
product
version
specified,
or
the
module
encountered
a
version-related
error.
Message
Variables:
name
-
The
name
of
the
called
module
product
-
The
product
being
monitored
System
Action:
Processing
ends.
Administrator
Response:
This
typically
indicates
an
installation
error.
Check
the
module
name
specified
and
determine
if
version-specific
tailoring
is
required
during
Tivoli
Business
Systems
Manager
installation.
If
so,
review
this
tailoring
and
repeat
if
necessary.
If
the
module
has
been
assembled
with
product
macros,
check
that
the
versions
of
the
macro
libraries
used
during
assembly
are
correct,
if
necessary.
If
you
are
unable
to
determine
the
problem,
contact
IBM
Software
Support.
IHS814E
AO
EXIT
name
DISABLED
FOR
IMS
Vv.r.m
type
SYSTEM
ims_id
Explanation:
The
Tivoli
Business
Systems
Manager
AO
Exit
was
disabled
due
to
a
previous
error.
Message
Variables:
name
-
The
exit
name
v.r.m
-
The
version,
release,
and
modification
level
of
the
IMS
under
which
IHSIAOE0
is
executing
type
-
The
type
of
IMS,
either
TM/DB,
DCCTL,
or
DBCTL
ims_id
-
The
IMS
subsystem
ID
System
Action:
The
IMS
AO
exit
is
disabled
and
messages
are
not
echoed
to
the
console.
182
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
Administrator
Response:
Look
for
previous
messages
describing
an
error
and
resolve
this
error.
When
resolved,
restart
this
IMS
region
to
activate
the
IMS
AO
exit.
If
you
are
unable
to
determine
the
cause
of
this
error,
contact
IBM
Software
Support.
IHS815I
module
COMMENCED
PROCESSING
Explanation:
The
named
module
started
processing.
Message
Variables:
module
-
The
module
name
that
started
System
Action:
Processing
continues.
IHS816E
MODULE
module
NOT
LINKED
INTO
PROGRAM
program
Explanation:
The
named
program
has
attempted
to
call
an
external
routine
held
in
the
named
module.
This
call
has
failed,
as
the
module
holding
the
external
routine
was
not
link-edited
into
the
program.
Message
Variables:
module
-
The
name
of
the
module
that
must
be
link-edited
into
the
program
program
-
The
program
name
System
Action:
Processing
ends.
Administrator
Response:
This
is
usually
caused
by
an
installation
error.
Check
that
all
SMP/E
DD
definitions
used
to
install
the
named
program
are
correct.
Check
also
any
customization
steps
performed
after
SMP/E
installation
that
might
affect
this
program,
and
correct
if
necessary.
If
you
are
unable
to
locate
the
problem,
contact
IBM
Software
Support.
IHS817I
module
disc_type
REDISCOVERY
STARTING
FOR
resource_type
resource_name
(FROM
datetime).
Explanation:
The
named
routine
has
commenced
rediscovery
of
this
resource.
Message
Variables:
module
-
The
name
of
a
module
that
is
performing
the
rediscovery
disc_type
-
The
type
of
discovery,
which
is
either
FULL
or
PARTIAL
resource_type
-
The
type
of
resource
being
rediscovered
resource_name
-
The
name
of
the
resource
being
rediscovered
datetime
-
For
partial
rediscoveries,
resources
modified
or
added
only
after
this
date
and
time
are
rediscovered.
For
full
rediscoveries,
this
variable
is
not
output.
System
Action:
Rediscovery
of
this
resource
continues.
IHS818I
LOGON
TO
application
FROM
routine
SUCCESSFUL.
Explanation:
A
routine
successfully
logged
on
to
the
named
application.
Message
Variables:
application
-
The
name
of
the
application
or
VTAM
application
ID
routine
-
The
name
of
the
routine
logging
on
to
the
application
System
Action:
Processing
continues.
IHS819E
FORMAT
OF
TMON
FOR
MVS
EXCEPTION
ACTIVITY
DISPLAY
UNEXPECTED
(applid).
Explanation:
Tivoli
Business
Systems
Manager
successfully
logged
on
to
ASG
TMON
for
MVS,
but
encountered
an
unexpected
format
of
the
Exception
Activity
Display
panel.
Message
Variables:
applid
-
The
VTAM
application
ID
of
the
ASG
TMON
for
MVS
application
System
Action:
ASG
TMON
for
MVS
monitoring
stops.
Administrator
Response:
This
usually
occurs
when
using
an
unsupported
version
of
ASG
TMON
for
MVS.
Check
the
ASG
TMON
for
MVS
version
and
migrate
to
a
supported
release,
if
necessary.
If
you
are
unable
to
resolve
the
problem,
contact
IBM
Software
Support.
IHS820I
(command)
INCORRECT
PARAMETERS,
PLEASE
RE-SPECIFY.
Explanation:
The
parameters
specified
for
the
IHS$RDIS
command
are
incorrect.
The
IHS$RDIS
command
has
three
parameters,
which
are
described
as
follows:
v
The
first
parameter
is
required
and
indicates
the
name
of
the
Tivoli
Business
Systems
Manager
data
source,
as
follows:
IMS
The
command
selects
IMS
systems
for
discovery.
DB2
The
command
selects
DB2
subsystems
for
discovery.
v
The
second
parameter
is
mandatory
and
indicates
which
of
the
active
IMS
systems
or
DB2
subsystems
are
selected
for
discovery.
This
parameter
contains
one
of
the
following:
–
The
subsystem
name
of
an
active
DB2
subsystem
or
a
character
mask
that
is
matched
against
the
subsystem
names
of
all
active
DB2
subsystems.
The
mask
is
a
standard
format
mask
with
a
question
mark
(?)
indicating
any
one
character,
and
an
asterisk
(*)
indicating
any
zero
or
more
characters.
For
a
DB2
subsystem,
this
parameter
must
be
between
1
–
4
characters
in
length.
Chapter
14.
IHS
Messages
-
IHS307E
-
IHS829I,
IHS0561I
183
–
The
JES
job
name
of
an
active
IMS
Control
Region
or
a
character
mask
that
is
matched
against
the
job
names
of
all
active
IMS
Control
Regions.
The
mask
is
a
standard
format
mask
with
a
question
mark
(?)
indicating
any
one
character,
and
an
asterisk
(*)
indicating
any
zero
or
more
characters.
For
an
IMS
system,
this
parameter
must
be
between
1
–
8
characters
in
length.
–
A
value
of
an
asterisk
(*)
indicates
that
either
all
active
IMS
systems
or
DB2
subsystems
on
the
MVS
system
are
to
be
selected.
v
The
third
parameter
is
optional
and
indicates
the
scope
of
the
discovery
to
be
performed.
The
valid
values
are
FULL
and
PARTIAL.
If
this
parameter
is
not
specified,
the
default
value
is
PARTIAL.
Message
Variables:
command
-
The
name
of
the
command
System
Action:
The
command
is
rejected.
IHS821I
(command)
PARAMETER
(value)
IS
NOT
VALID,
FEED
(feed_name)
NAME
(mask_name)
TYPE
(discovery_type)
Explanation:
The
parameter
value
supplied
as
input
to
the
IHS$RDIS
command
is
not
valid.
Enter
the
command
again
with
the
correct
parameter.
See
the
IHS820I
message
for
an
explanation
of
the
IHS$RDIS
command
parameters.
Message
Variables:
command
-
The
name
of
the
command
value
-
The
value
of
the
IHS$RDIS
command
parameter
that
is
not
valid
feed_name
-
The
value
of
the
first
parameter.
This
is
the
name
of
the
Tivoli
Business
Systems
Manager
data
resource.
For
example,
IMS
or
DB2
systems.
mask_name
-
The
value
of
the
second
parameter.
This
is
the
job
name
of
an
active
IMS
Control
region
or
the
subsystem
name
of
an
active
DB2
subsystem.
Or
alternatively,
a
character
mask
that
enables
multiple
active
IMS
or
DB2
systems
to
be
selected.
discovery_type
-
The
value
of
the
third
parameter.
This
specifies
the
scope
of
the
discovery
requested.
System
Action:
The
command
is
rejected.
IHS822I
(command)
NO
ACTIVE
feed_name
SYSTEMS
FOUND
FOR
mask_name
Explanation:
The
command
was
unable
to
find
any
active
IMS
or
DB2
systems
that
match
the
name
or
mask
specified.
Message
Variables:
command
-
The
name
of
the
command
feed_name
-
The
name
of
the
Tivoli
Business
Systems
Manager
data
resource.
For
example,
IMS
or
DB2
systems.
mask_name
-
The
job
name
of
an
active
IMS
Control
region
or
the
subsystem
name
of
an
active
DB2
system.
Or
alternatively,
a
character
mask
that
enables
multiple
active
IMS
or
DB2
systems
to
be
selected.
System
Action:
The
command
is
rejected.
Administrator
Response:
Ensure
that
the
IMS
or
DB2
systems
specified
in
the
command
were
active
and
had
completed
restart
processing
when
the
command
was
issued.
If
the
problem
persists,
contact
IBM
Software
Support.
IHS823I
MPR
NOT
AVAILABLE
TO
PROCESS
TRANSACTION
tran_name,
CLASS
tran_class.
Explanation:
The
IMS
transaction
queue
poll
monitor
detected
that
the
queue
count
of
the
transaction
exceeds
the
threshold
specified
for
the
IMS
region
and
that
there
are
no
MPRs
(Message
Processing
Regions)
available
to
process
this
transaction.
The
threshold
is
specified
by
the
Tivoli
Business
Systems
Manager
console.
If
no
threshold
was
specified
for
the
IMS
region,
then
the
IHSI.$TXQLEN_MPR
parameter
specified
within
the
IHS$UPRM
override
member
is
used.
If
no
override
is
specified,
the
default
setting
from
the
IHSIPRM
member
is
used.
Message
Variables:
tran_name
-
The
name
of
the
IMS
transaction
tran_class
-
The
transaction
class
of
this
IMS
transaction
System
Action:
An
exception
event
is
sent
to
Tivoli
Business
Systems
Manager
and
processing
continues
Administrator
Response:
If
this
is
not
an
error,
modify
the
IMS
MPR
transaction
queue
threshold
using
the
Tivoli
Business
Systems
Manager
console,
or
modify
the
threshold
for
all
IMS
regions
by
adding
the
IHSI.$TXQLEN_MPR
parameter
to
the
IHS$UPRM
member
in
the
SGTMSAMP
data
set.
To
introduce
the
changed
values
prior
to
the
next
NetView
startup,
issue
the
IHS$PRMU
REFRESH
command
from
an
NCCF
session.
For
details
of
the
IHS$PRMU
command,
refer
to
the
prolog
of
the
IHS$UPRM
member
in
SGTMSAMP.
The
IHSIPRM
member
in
SGTMSAMP
contains
the
default
parameter
settings
for
the
IMS
data
source,
as
supplied
with
Tivoli
Business
Systems
Manager.
This
member
should
not
be
changed.
For
further
details
regarding
the
IHSI.$TXQLEN_MPR
parameter,
refer
to
the
prolog
that
precedes
this
parameter
in
the
IHSIPRM
member
in
SGTMSAMP.
IHS824I
MPR
NOW
AVAILABLE
TO
PROCESS
TRANSACTION
tran_name.
Explanation:
The
IMS
transaction
queue
poll
monitor
detected
that
the
queue
count
of
the
transaction
is
within
the
threshold
specified
for
the
IMS
region,
or
there
are
now
MPRs
(Message
Processing
Regions)
184
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
available
to
process
this
transaction.
The
threshold
is
specified
by
the
Tivoli
Business
Systems
Manager
console.
If
no
threshold
was
specified
for
the
IMS
region,
then
the
IHSI.$TXQLEN_MPR
parameter
specified
within
the
IHS$UPRM
override
member
is
used.
If
no
override
is
specified,
the
default
setting
from
the
IHSIPRM
member
is
used.
Message
Variables:
tran_name
-
The
name
of
the
IMS
transaction
System
Action:
A
resolution
is
sent
to
Tivoli
Business
Systems
Manager
and
processing
continues
Administrator
Response:
Refer
to
message
number
IHS823I
about
amending
the
IHSI.$TXQLEN_MPR
parameter
setting.
IHS825E
(module)
TYPE
(input_ims_type)
IS
NOT
VALID
FOR
job_name,
SPECIFY
(ims_type).
Explanation:
The
module
received
an
IMS
type
that
does
not
match
the
IMS
type
retrieved
from
the
active
IMS
Control
Region.
Message
Variables:
module
-
The
name
of
the
module
input_ims_type
-
The
IMS
Tivoli
Business
Systems
Manager
Object
Type
supplied
as
input
to
the
module.
Valid
values
are:
IMSS
IMS
TM/DB
system
IMTM
IMS
DCCTL
system
IMDB
IMS
DBCTL
system
job_name
-
The
job
name
of
an
active
IMS
Control
Region
ims_type
-
The
IMS
Tivoli
Business
Systems
Manager
Object
Type
derived
directly
from
the
active
IMS
Control
Region
System
Action:
The
command
is
rejected.
Administrator
Response:
Enter
the
command
again
and
specify
the
IMS
type
identified
within
the
message
text.
IHS826E
(module)
JOB
NAME
(job_name)
IS
NOT
VALID
Explanation:
The
syntax
of
the
JES
job
name
or
started
task
name
is
not
valid.
A
job
or
started
task
name
is
in
the
range
of
1
–
8
alphanumeric
or
special
characters
(for
example,
$,
#,
@).
The
first
character
must
be
an
alphabetic
or
special
character.
Refer
to
the
appropriate
manual
in
the
z/OS
MVS
JCL
library
for
further
details.
Message
Variables:
module
-
The
name
of
the
module
job_name
-
The
value
of
the
JES
job
or
started
task
name
that
is
not
valid
System
Action:
The
command
is
rejected.
Administrator
Response:
Enter
the
command
again
and
specify
a
valid
JES
job
or
started
task
name.
If
this
is
not
possible
or
the
problem
persists,
contact
IBM
Software
Support.
IHS827E
(module)
DISCOVERY
TYPE
(disc_type)
IS
NOT
VALID.
Explanation:
The
module
received
a
rediscovery
request
type
that
is
not
valid.
Message
Variables:
module
-
The
name
of
the
module
disc_type
-
The
discovery
type
that
is
not
valid.
The
valid
values
are
PARTIAL,
FULL
or
a
null
value,
which
defaults
to
the
PARTIAL
value.
System
Action:
The
command
is
rejected.
Administrator
Response:
Enter
the
command
again
and
specify
one
of
the
valid
discovery
types.
IHS828E
JOB
NAME
(job_name)
IS
NOT
AN
IMS
CONTROL
REGION
Explanation:
The
named
job
or
started
task
name
is
not
an
IMS
Control
Region.
Message
Variables:
job_name
-
The
name
of
an
active
job
or
started
task
System
Action:
The
command
is
rejected.
Administrator
Response:
Enter
the
command
again
and
specify
the
job
name
of
an
IMS
Control
Region.
If
the
problem
persists,
contact
IBM
Software
Support.
IHS829I
(module)
feed_name
REDISCOVERY
FOR
name
DEFERRED.
Explanation:
The
installation
specified
that
rediscovery
be
deferred.
For
IMS
resources,
this
is
achieved
by
setting
the
value
of
IHSI_REDISC
to
DEFER.
For
DB2
resources,
this
is
achieved
by
setting
the
value
of
IHSB_REDISC
to
DEFER.
Message
Variables:
module
-
The
name
of
the
module
feed_name
-
The
name
of
the
Tivoli
Business
Systems
Manager
data
resource.
For
example,
IMS
or
DB2
systems.
name
-
The
job
name
of
the
IMS
Control
Region
or
the
name
of
the
DB2
subsystem
being
rediscovered
System
Action:
The
scope
of
the
rediscovery
is
reduced
and
processing
continues.
Administrator
Response:
For
further
details
regarding
the
IMS
IHSI_REDISC
parameter,
refer
to
the
prolog
that
precedes
this
parameter
in
the
IHSIPRM
member
in
the
SGTMSAMP
data
set.
For
the
DB2
IHSB_REDISC
parameter,
refer
to
the
prolog
that
precedes
this
parameter
in
the
IHSBPRM
member
in
SGTMSAMP.
To
override
this
parameter,
add
it
with
the
required
value
to
the
IHS$UPRM
override
member
within
Chapter
14.
IHS
Messages
-
IHS307E
-
IHS829I,
IHS0561I
185
SGTMSAMP.
To
introduce
the
changed
values
prior
to
the
next
NetView
startup,
issue
the
IHS$PRMU
REFRESH
command
from
an
NCCF
session.
IHS0561I
EITHER
THE
USER
ID
WAS
NULL
OR
THE
USER
ID
COULD
NOT
BE
VERIFIED
BECAUSE
THE
NETVIEW
OPERATOR
TASK
WAS
NOT
ACTIVE.
IF
THE
TASK
IS
NOT
ACTIVE,
AUTOLOGN=YES
MAY
NEED
TO
BE
SET
IN
NETVIEW.
ERROR
RUNNING
COMMAND.
Explanation:
The
user
attempted
to
issue
a
z/OS
task
and
the
task
server
attempted
to
verify
the
user
ID
and
password
through
the
NetView
program,
but
the
verification
failed.
Either
the
user
ID
was
null
or
the
NetView
operator
task
associated
with
the
user
ID
was
not
active.
If
the
user
ID
was
null
and
the
OS_V
table
is
used,
verify
that
the
entries
in
the
OS_V
table
are
valid.
This
might
require
entering
the
user
ID
and
password
again
into
the
OS_V
table
through
the
Configure
TGM
TaskServer
Connection
dialog.
Administrator
Response:
If
the
OS_V
table
is
not
used
for
user
IDs,
sign
off
and
sign
back
onto
the
console,
and
enter
the
NetView
user
ID
and
password
again
the
next
time
a
task
is
issued.
If
the
user
ID
is
valid
in
both
cases,
contact
your
NetView
system
programmer
and
request
verification
that
the
NetView
operator
task
for
the
user
ID
is
active.
If
it
is
not
active,
either
AUTOLOGN=YES
should
be
set
in
the
NetView
program
so
that
the
operator
task
will
start
when
a
task
is
issued,
or
the
operator
task
should
be
signed
on.
186
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
Chapter
15.
IMS
Feed
Messages
-
GTMIM1001I
-
GTMIM1006W
The
following
messages
are
issued
by
the
Tivoli
Business
Systems
Manager
IMS
feed.
GTMIM1001I
No
records
to
process
because
there
are
no
IMS
discovery
batches
in
the
state
state.
Explanation:
No
records
currently
exist
that
require
processing
by
the
system
at
this
time
for
this
function.
Message
Variables:
state
-
The
mode
of
batch
processing,
which
is
a
string.
Examples
of
modes
are
ALLOCATED,
ENQUEUED,
LOADED,
INPROGRESS,
and
COMPLETED.
System
Action:
The
system
continues
to
run
and
will
process
additional
records
as
they
arrive
when
the
function
is
called
again.
GTMIM1002E
Error
loading
discovery
batch
file
file_path.
Explanation:
The
loading
process
was
not
able
to
load
the
specified
file.
Possible
reasons
are
the
file
format
is
not
valid
or
the
specified
action
type
does
not
match
the
contents
of
the
file.
Message
Variables:
file_path
-
The
full
path
and
file
name
of
the
file
containing
the
records
for
a
particular
batch
System
Action:
The
system
continues
to
run,
but
this
batch
will
not
be
loaded.
Administrator
Response:
Verify
that
the
file
is
formatted
correctly,
and
attempt
to
load
the
file
again
using
the
CreateDiscoveryBatch.ksh
command.
GTMIM1004E
Batch
batch_id
cannot
be
resolved
to
any
operating
system.
Explanation:
The
discovery
batch
records
are
associated
with
an
operating
system
based
on
their
netid.cpname
value.
If
the
netid.cpname
value
cannot
be
matched
to
a
known
operating
system,
then
the
objects
cannot
be
discovered.
Message
Variables:
file_path
-
The
batch
ID
number,
which
is
an
integer.
This
number
is
used
to
identify
a
particular
group
of
discovery
records.
System
Action:
The
system
continues
to
run,
but
this
batch
will
not
be
processed.
Administrator
Response:
Restart
the
source/390
object
pump
to
rediscover
the
operating
system
to
the
netid.cpname
correlation,
then
attempt
to
load
the
file
again
using
the
CreateDiscoveryBatch.ksh
command.
GTMIM1005I
Deleted
count
successfully
processed
IMSDiscovery
rows
for
batch
batch_id.
Explanation:
The
discovery
processing
is
complete
and
the
records
that
were
successfully
discovered
are
purged
from
the
batch.
Message
Variables:
count
-
The
number
of
records,
which
is
an
integer
batch_id
-
The
batch
ID
number,
which
is
an
integer.
This
number
is
used
to
identify
a
particular
group
of
discovery
records.
System
Action:
The
system
continues
to
run,
and
the
state
for
this
batch
is
set
to
COMPLETED.
Administrator
Response:
Restart
the
source/390
object
pump
to
rediscover
the
operating
system
to
the
netid.cpname
correlation,
then
attempt
to
load
the
file
again
using
the
CreateDiscoveryBatch.ksh
command.
GTMIM1006W
count
IMSDiscovery
rows
for
batch
batch_id
have
not
been
completely
processed.
Explanation:
The
discovery
processing
is
complete,
but
some
objects
might
not
have
been
fully
discovered
due
to
a
lack
of
object
hierarchy
information.
Message
Variables:
count
-
The
number
of
records,
which
is
an
integer
batch_id
-
The
batch
ID
number,
which
is
an
integer.
This
number
is
used
to
identify
a
particular
group
of
discovery
records.
System
Action:
The
system
continues
to
run,
and
the
state
for
this
batch
is
set
to
COMPLETED.
Administrator
Response:
Examine
the
remaining
records
by
issuing
the
SELECT
*
FROM
IMSDiscovery
WHERE
batchid
=
batch_id
SQL
command.
If
the
objects
in
the
batch
need
to
be
discovered,
complete
a
partial
or
full
discovery
on
the
appropriate
objects.
©
Copyright
IBM
Corp.
2000,
2004
187
Chapter
16.
Console
Messages
-
GTMJC0502I
-
GTMJC9191I
The
following
messages
are
generated
by
the
Tivoli
Business
Systems
Manager
console
and
console
server.
The
message
information
in
this
chapter
can
also
be
viewed
directly
from
the
console.
When
a
particular
message
is
displayed,
click
the
question
mark
in
the
upper
right
corner
of
the
message
box,
or
press
the
F1
key.
The
Task
Assistant
displays
with
the
complete
message
and
explanation
text.
You
can
also
view,
or
search
on,
the
complete
list
of
console
and
console
server
messages
from
the
console
by
clicking
Help
—>
Message
Index.
GTMJC0502I
User
name
user_id
log
on
successful.
Explanation:
The
console
server
has
validated
and
logged
on
the
user.
System
Action:
The
console
server
continues
processing.
Administrator
Response:
None
required.
This
message
indicates
that
the
system
has
validated
the
user
supplied
user
name
and
password
and
that
the
user
name
is
a
member
of
one
of
the
groups
allowed
to
use
IBM
Tivoli
Business
Systems
Manager.
GTMJC0503E
Log
on
of
user
name
user_id
failed.
Explanation:
The
user
name
could
not
be
authenticated.
System
Action:
The
user
is
prompted
to
correct
their
user
name,
password,
or
both.
Operator
Response:
Ensure
your
user
name
and
password
are
correct
and
attempt
to
log
on
again.
If
the
problem
persists,
contact
the
administrator.
Administrator
Response:
Ensure
that
the
user
name
and
password
are
valid.
If
the
problem
persists,
contact
Customer
Support.
GTMJC0505E
Unable
to
create
console
server.
Explanation:
The
console
server
was
unable
to
create
the
resource
required
for
one
or
more
of
its
functions.
System
Action:
The
console
server
stops.
Operator
Response:
Contact
the
administrator.
Administrator
Response:
Restart
the
console
server
service.
If
the
problem
persists,
contact
Customer
Support.
GTMJC0506E
An
error
occurred
accessing
the
IBM
Tivoli
Business
Systems
Manager
database.
Diagnostic
information:
diaginfo
Explanation:
A
database
operation
failed
to
complete
successfully.
System
Action:
The
system
cancels
the
failed
database
operation.
Operator
Response:
Retry
the
operation.
If
the
problem
persists,
contact
the
administrator.
Administrator
Response:
If
the
problem
occurs
only
for
certain
tasks,
such
as
inserting,
updating,
or
deleting
resources,
see
the
console
server
log
for
error
messages
that
could
help
explain
the
problem.
If
the
problem
occurs
consistently
for
all
database
operations,
verify
that:
1.
The
IBM
Tivoli
Business
Systems
Manager
database
server
and
process
are
functioning
correctly.
2.
The
network
connection
between
the
console
server
and
the
IBM
Tivoli
Business
Systems
Manager
database
is
functioning
correctly.
3.
The
data
source
for
the
IBM
Tivoli
Business
Systems
Manager
database
is
correctly
configured
in
the
WebSphere
Application
server.
4.
The
IBM
Tivoli
Business
Systems
Manager
database
server
is
configured
to
permit
a
sufficient
number
of
connections.
The
number
of
connections
could
be
limited
by
the
licensing
or
configuration
of
the
database
server.
After
verifying
and
correcting
any
of
the
preceding
items,
restart
the
console
server.
If
the
problem
persists,
contact
Customer
Support.
If
the
problem
occurs
only
for
a
particular
operation
or
set
of
operations,
contact
Customer
Support.
Be
prepared
to
describe
the
set
of
operations
that
led
up
to
this
message
and
other
activities
in
the
system
that
you
believe
could
be
related
to
the
error.
GTMJC0508E
An
error
occurred
saving
workspace
workspace.
Explanation:
You
attempted
to
save
a
workspace,
but
this
action
did
not
complete
successfully.
©
Copyright
IBM
Corp.
2000,
2004
189
System
Action:
The
workspace
was
not
saved,
but
console
processing
continues.
Operator
Response:
Save
the
workspace
again.
If
the
problem
persists,
notify
the
administrator.
Administrator
Response:
Verify
that
available
disk
space
exists
on
the
database
server
and
that
the
console
server
and
database
server
are
both
running.
GTMJC0510E
An
error
occurred
connecting
to
the
database
using
data
source
datasource
.
Diagnostic
information:
diaginfo
Explanation:
The
console
server
could
not
establish
a
new
connection
to
the
IBM
Tivoli
Business
Systems
Manager
database.
System
Action:
The
action
requiring
database
access
is
stopped.
Operator
Response:
Contact
the
administrator.
Administrator
Response:
Verify
the
following:
1.
The
IBM
Tivoli
Business
Systems
Manager
database
server
and
process
are
functioning
correctly.
2.
The
network
connection
between
the
console
server
and
the
IBM
Tivoli
Business
Systems
Manager
database
is
functioning
correctly.
3.
The
data
source
for
the
IBM
Tivoli
Business
Systems
Manager
database
is
correctly
configured
in
the
WebSphere
Application
server.
4.
The
IBM
Tivoli
Business
Systems
Manager
database
server
is
configured
to
permit
a
sufficient
number
of
connections.
The
number
of
connections
could
be
limited
by
the
licensing
or
configuration
of
the
database
server.
The
diagnostic
information
in
the
message
contains
information
reported
by
the
database
driver
or
the
WebSphere
Application
server
that
could
be
useful
in
locating
the
problem.
After
verifying
and
correcting
any
of
the
preceding
items,
restart
the
console
server.
If
the
problem
persists,
contact
Customer
Support.
GTMJC0511E
Error
communicating
with
server
server_id.
Explanation:
The
console
encountered
an
error
while
communicating
with
the
console
server.
System
Action:
The
operation
requiring
server
communication
is
stopped.
If
the
communication
error
occurred
after
the
server
portion
of
an
update
operation
completed,
the
updates
remain
in
place.
Operator
Response:
Verify
that:
1.
You
specified
the
host
name
of
the
console
server
correctly
in
the
sign
on
panel.
2.
Your
computer
is
connected
to
the
network
and
TCP/IP
networking
is
functioning
correctly.
Retry
the
operation.
If
the
problem
persists,
contact
the
administrator.
Administrator
Response:
If
the
problem
occurs
consistently
at
startup
for
many
or
all
consoles
attempting
to
connect
to
the
console
server,
verify
the
following:
1.
The
server
computer
is
connected
to
the
network
and
TCP/IP
networking
is
functioning
correctly.
2.
The
console
server
is
running.
3.
The
console
server
and
any
firewalls
between
the
console
and
console
server
are
configured
consistently.
4.
If
the
console
server
is
configured
to
use
ports
for
the
boot
strap
address
other
than
the
default
value
2809,
specify
the
port
in
the
Server
name
field
of
the
IBM
Tivoli
Business
Systems
Manager
sign
on
panel
using
the
hostname:port
syntax.
Configure
the
server
by
using
Administrative
Console
Servers
->
Application
Servers
->
yourservername
->
End
Points
->
BOOTSTRAP_ADDRESS.
If
the
problem
occurs
intermittently
during
operation,
it
could
be
due
to
network
traffic
or
a
transient
network
problem.
If
the
problem
appears
to
be
related
to
a
specific
operation,
contact
Customer
Support
and
describe
the
situation
leading
up
to
the
failure.
GTMJC0512E
The
workspace
cannot
be
saved
with
the
name
workspace_name.
Select
Save
Workspace
as...
to
rename
it.
Explanation:
You
attempted
to
save
a
workspace
with
a
name
that
is
not
valid.
System
Action:
Console
processing
continues,
but
the
workspace
is
not
saved.
Operator
Response:
Select
Console
->
Save
Workspace
as
to
save
the
workspace
with
a
different
name,
or
continue
without
saving
the
workspace.
Administrator
Response:
Advise
the
operator
to
save
the
workspace
using
a
valid
name.
GTMJC0513E
The
function
you
requested
is
not
implemented.
Explanation:
You
selected
a
function
that
the
console
cannot
complete.
System
Action:
The
function
is
not
performed.
Operator
Response:
If
the
problem
persists,
contact
Customer
Support.
Administrator
Response:
If
the
problem
persists,
contact
Customer
Support.
190
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
GTMJC0514E
An
unexpected
error
occurred.
Contact
Customer
Support.
Explanation:
An
error
occurred
from
the
console.
System
Action:
The
requested
action
did
not
succeed.
Operator
Response:
Recreate
the
problem
with
all
the
tracing
enabled.
Obtain
the
console
and
server
logs.
Administrator
Response:
View
the
logs
and
interpret
the
information.
If
possible,
verify
that
the
database
contains
the
correct
information.
GTMJC0515E
Unable
to
display
the
requested
view.
The
view
model
view_model
was
not
found.
Explanation:
You
requested
a
view
that
the
console
cannot
display.
System
Action:
The
view
is
not
displayed.
Operator
Response:
If
the
problem
persists,
contact
Customer
Support.
Administrator
Response:
If
the
problem
persists,
contact
Customer
Support.
GTMJC0516E
An
error
occurred
saving
preferences
preferences.
Explanation:
The
system
encountered
an
error
while
saving
the
user
preferences
to
the
database.
System
Action:
Preference
changes
are
not
saved
and
processing
continues.
Operator
Response:
If
the
problem
persists,
notify
the
administrator.
Administrator
Response:
Verify
that
available
disk
space
exists
on
the
database
server
and
that
the
console
server
and
database
server
are
both
running.
GTMJC0517I
User
name
user_id
logged
out
successfully.
Explanation:
The
message
indicates
that
the
operator
logged
out
from
the
console
server.
System
Action:
The
system
continues
processing
for
other
operators.
GTMJC0518E
The
workspace
workspace
is
a
shared
workspace
that
can
only
be
saved
by
an
administrator.
Explanation:
You
attempted
to
save
a
workspace
using
the
name
of
an
existing
workspace
which
can
only
be
saved
by
an
administrator.
System
Action:
The
console
processing
continues,
but
the
workspace
is
not
saved.
Operator
Response:
Use
Console
->
Save
Workspace
as
to
save
the
workspace
using
a
name
different
from
any
other
existing
administrator
workspaces.
Administrator
Response:
Advise
the
operator
to
save
the
workspace
using
a
name
which
is
not
used
by
an
existing
administrator
workspace.
GTMJC0519E
An
error
occurred
with
security
protocols.
Explanation:
This
indicates
a
general
problem
with
authentication.
System
Action:
The
operator
is
prompted
to
correct
their
user
name,
password,
or
both.
Operator
Response:
Ensure
your
user
name
and
password
are
correct
and
attempt
to
log
on
again.
If
the
problem
persists,
contact
the
administrator.
Administrator
Response:
This
problem
might
be
caused
by
network
connectivity
problems
between
the
console
and
the
console
server.
If
the
problem
persists,
contact
Customer
Support.
GTMJC0521I
Operators
do
not
have
permission
to
access
this
workspace.
Only
administrators
can
access
this
workspace.
Permissions
can
be
modified
by
editing
the
workspace
properties
from
the
Open
Workspace
window.
Explanation:
A
workspace
was
saved,
but
no
operators
were
given
permission
to
access
to
this
workspace.
System
Action:
The
console
processing
continues.
Administrator
Response:
No
action
is
necessary
unless
you
want
to
provide
operators
access
to
the
saved
workspace.
GTMJC0522E
The
workspace
workspace
is
currently
open.
It
cannot
be
deleted.
Explanation:
You
attempted
to
delete
a
workspace
that
you
have
open.
This
is
not
permitted.
System
Action:
The
console
processing
continues,
but
the
selected
workspace
is
not
deleted.
Operator
Response:
If
you
want
to
delete
the
workspace,
then
you
must
close
the
open
view
of
this
workspace
and
perform
the
delete
function
again.
Administrator
Response:
Advise
the
operator
that
the
console
does
not
support
deleting
a
workspace
while
it
is
currently
open.
The
operator
must
close
the
open
view
of
the
workspace
and
perform
the
delete
function.
Chapter
16.
Console
Messages
-
GTMJC0502I
-
GTMJC9191I
191
GTMJC0523W
Are
you
sure
you
want
to
delete
workspace
workspace?
Explanation:
You
attempted
to
delete
a
workspace.
You
are
being
asked
to
confirm
the
deletion.
System
Action:
The
console
processing
continues.
The
workspace
is
deleted
if
you
click
Yes.
If
you
click
No,
the
workspace
is
not
deleted.
Operator
Response:
Click
Yes
in
the
message
window
if
you
want
to
delete
the
workspace.
If
you
do
not,
click
No.
Administrator
Response:
It
is
a
standard
function
to
confirm
a
workspace
deletion.
Instruct
the
operator
to
click
Yes
or
No
in
the
message
window
depending
on
whether
they
want
the
deletion
to
continue.
GTMJC0525W
The
workspace
with
the
name
workspace_name
already
exists.
Do
you
want
to
overwrite
it?
Explanation:
You
attempted
to
save
a
workspace
using
a
duplicate
name.
You
are
being
asked
to
provide
a
confirmation
before
the
existing
workspace
is
overwritten.
System
Action:
The
console
processing
continues.
The
existing
workspace
is
overwritten
if
you
click
Yes.
If
you
click
No,
this
workspace
is
not
saved.
Operator
Response:
Click
Yes
in
the
message
window
if
you
want
to
save
the
workspace
and
overwrite
the
existing
workspace.
Click
No
to
avoid
overwriting
the
existing
workspace.
If
you
click
No,
you
can
attempt
to
save
it
again
with
a
different
name
by
using
Console
->
Save
Workspace
as.
Administrator
Response:
It
is
a
standard
function
to
request
confirmation
before
overwriting
an
existing
workspace.
Instruct
the
operator
to
click
Yes
or
No
in
the
message
window
depending
on
whether
they
want
the
save
to
continue
and
overwrite
the
existing
workspace.
GTMJC0527E
Unable
to
parse
notification
fields
in
notification
resource
notification_resource.
Explanation:
An
unexpected
format
was
encountered
by
the
console
server
when
it
retrieved
a
notification
event
from
the
IBM
Tivoli
Business
Systems
Manager
database.
System
Action:
The
notification
event
is
ignored.
Operator
Response:
If
the
problem
persists,
contact
Customer
Support.
Administrator
Response:
If
the
problem
persists,
contact
Customer
Support.
GTMJC0528E
An
error
occurred
accessing
the
database
table
database_table.
Explanation:
The
console
server
encountered
a
problem
accessing
a
table
in
the
IBM
Tivoli
Business
Systems
Manager
database.
System
Action:
The
processing
is
stopped.
Operator
Response:
If
the
problem
persists,
contact
Customer
Support.
Administrator
Response:
If
the
problem
persists,
contact
Customer
Support.
GTMJC0529I
The
user
ID
user_id
connected
successfully
to
the
server.
Explanation:
The
user
ID
named
in
the
message
has
logged
on
to
the
console
and
the
console
has
connected
to
the
server.
System
Action:
Processing
continues.
GTMJC0530I
The
user
ID
user_id
successfully
disconnected
from
the
server.
Explanation:
The
console
being
used
by
the
operator
named
in
the
message
has
disconnected
from
the
server.
System
Action:
Processing
continues
for
other
operators.
GTMJC0531E
Unable
to
access
preferences
for
user
ID
user_id.
Explanation:
You
do
not
have
access
to
preferences.
System
Action:
Processing
continues,
but
the
preferences
are
not
saved.
Operator
Response:
Ask
the
administrator
to
add
your
user
ID
to
the
administrator
credentials.
Administrator
Response:
The
user
ID
is
not
in
the
administrator
credentials.
Provide
access
to
the
user
ID.
If
the
problem
persists,
contact
Customer
Support.
GTMJC0532W
Deleting
resource
removes
the
business
system
and
all
its
children
from
parent.
Do
you
want
to
delete
this
business
system
and
all
its
children?
Explanation:
You
are
deleting
a
business
system
that
is
contained
in
another
business
system.
If
the
current
view
contains
any
children
for
this
business
system,
they
are
removed
along
with
the
business
system.
This
business
system
and
its
children
are
removed
from
all
views
that
contain
this
business
system.
System
Action:
This
business
system
and
all
of
its
children
are
removed
from
the
specified
parent
business
system
in
the
business
systems
tree.
All
views
192
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
that
contain
this
business
system
are
updated
to
remove
the
business
system
and
its
children.
Operator
Response:
Confirm
the
deletion
of
this
business
system
and
its
children.
GTMJC0533E
This
console
(build
console_build_level)
is
incompatible
with
the
server
(build
server_build_level).
You
need
to
upgrade
the
console
to
at
least
build
build_level
to
connect
to
this
server.
Explanation:
The
version
of
the
current
console
and
server
are
incompatible
because
they
are
not
on
the
same
build
level.
System
Action:
The
console
does
not
start.
Operator
Response:
Contact
the
administrator.
Administrator
Response:
Uninstall
the
console
code
and
reinstall
it
using
the
suggested
build
level.
See
information
about
uninstalling
the
console
in
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide.
If
the
problem
persists,
contact
Customer
Support.
GTMJC0534E
The
launch
failed.
The
launch
target
launch_target
could
not
be
found
in
the
RDM_LAUNCHER
table.
Explanation:
The
application
launch
failed.
The
RDM_LAUNCHER
table
does
not
contain
an
entry
that
matches
the
RDM
name
in
the
control_id
of
the
MenuItem
entry
for
your
selection.
System
Action:
The
GTMJC0534E
message
is
issued
to
the
operator.
The
system
is
available
for
other
requests.
Operator
Response:
Turn
on
all
tracing
and
recreate
the
problem.
Save
the
console
logs
and
contact
your
administrator.
Administrator
Response:
Examine
the
control_id
column
of
the
MenuItem
table
entry
that
created
the
menu
item
the
operator
selected.
The
first
token
in
the
control_id
is
the
RDM
name.
Examine
the
entries
in
the
RDM_LAUNCHER
table.
Look
for
entries
with
a
matching
value
in
the
RDM_NAME
column
and
a
matching
value
in
the
PLATFORM
column
of
the
entry
for
the
operator’s
operating
system
platform.
WSERVER
matches
all
Windows
servers.
WCLIENT
matches
Windows
client
servers.
A
short
name
such
as
Windows
matches
all
Windows
operating
systems.
UNIX
matches
all
UNIX-based
systems.
If
there
is
no
matching
entry,
that
is
the
reason
for
the
failure.
Create
a
matching
entry.
If
there
is
a
matching
entry,
contact
Customer
Support
and
provide
the
logs,
text
export
of
the
MenuItem
table
entry,
and
a
text
export
of
all
the
RDM_LAUNCHER
table
entries.
GTMJC0535E
The
launch
failed.
The
launch
target
launch_target
failed
to
start,
the
invocation
was:
invocation
Explanation:
The
console
tried
to
start
the
application
but
the
application
did
not
start.
System
Action:
The
message
GTMJC0535E
is
issued
to
the
operator.
The
system
is
available
for
other
requests.
Operator
Response:
Turn
on
all
tracing
and
recreate
the
problem.
Save
the
console
logs
and
contact
your
administrator.
Administrator
Response:
Try
the
invocation
in
the
message
from
a
command
line
where
the
launch
failed,
and
observe
the
results.
If
the
invocation
from
the
command
line
starts
the
application,
contact
Customer
Support
and
provide
the
logs,
text
export
of
the
MenuItem
table
entry,
and
a
text
export
of
all
the
RDM_LAUNCHER
table
entries.
If
the
invocation
did
not
start,
the
application
determines
what
is
wrong
and
corrects
it.
This
could
be
an
addition
to
the
PATH
variable,
the
definition
of
an
environment
variable,
or
modifying
the
PROGRAM_NAME
column
or
the
PROGRAM_DATA
column
of
the
appropriate
entry.
GTMJC0536E
The
launch
failed.
The
launch
target
launch_target
is
busy.
Try
again
in
a
few
minutes.
Explanation:
The
target
application
is
currently
fulfilling
another
request
and
cannot
respond
to
the
new
request.
System
Action:
The
GTMJC0536E
message
is
issued
to
the
operator.
The
system
is
available
for
other
requests.
Operator
Response:
If
the
request
was
attempted
on
a
UNIX-based
system,
wait
a
few
minutes
and
try
the
launch
again.
If
this
is
not
a
UNIX-based
system,
turn
on
all
tracing
and
recreate
the
problem.
Save
the
console
logs
and
provide
them
to
your
administrator.
The
problem
can
also
be
with
the
application
you
are
trying
to
launch.
Administrator
Response:
If
the
operator,
whose
launch
failed,
is
working
off
of
an
x-terminal
that
connects
to
a
multi
x-terminal
system,
verify
that
each
x-terminal
has
its
own
unique
value
for
the
$DISPLAY
environment
variable.
If
they
do
not,
correct
this
and
try
the
launch
again.
If
the
retry
(after
$DISPLAY
correction)
fails
the
same
way,
verify
that
the
target
application
supports
multiple
ports
for
launch.
Verify
that
multiple
ports
are
defined
for
the
target
application
and
that
the
RDM_LAUNCHER
table
entry
for
the
target
application
contains
a
port
range
that
encompasses
the
target
applications
ports.
Correct
any
of
the
preceding
situations
and
try
the
launch
again.
Determine
if
the
target
application
was
launched
successfully
prior
to
the
current
failing
launch.
If
it
was,
the
problem
is
with
the
target
application.
Refer
to
the
documentation
for
the
target
application,
have
Chapter
16.
Console
Messages
-
GTMJC0502I
-
GTMJC9191I
193
appropriate
documentation
for
the
target
application
available,
and
contact
Customer
Support.
GTMJC0537E
The
launch
failed.
No
reason
is
available,
contact
the
administrator.
Explanation:
The
launch
failed
and
IBM
Tivoli
Business
Systems
Manager
provides
no
specific
reason
for
the
failed
launch.
System
Action:
The
message
GTMJC0537E
is
issued
to
the
operator.
The
system
is
available
for
other
requests.
Operator
Response:
Turn
on
all
tracing
and
try
the
function
again.
Gather
the
console
logs
and
contact
the
administrator.
Administrator
Response:
Locate
the
exception
named
LALaunchException
and
its
associated
message
for
this
event
in
the
console
logs.
If
the
base
exception
is
an
IO
Exception,
contact
network
support
and
determine
if
IP
or
HTTP
bindings
are
correctly
installed
on
the
operator’s
console.
If
the
associated
message
indicates
that
a
type
is
not
valid,
find
the
RDM_LAUNCHER
entry
for
the
target
application
and
correct
its
PROTOCOL
type.
Valid
PROTOCOL
types
are
CmdLine,
Sockets,
or
HTTP.
If
this
problem
persists,
contact
Customer
Support
and
provide
all
documentation.
GTMJC0538E
The
launch
failed.
An
unexpected
condition
occurred,
contact
the
administrator.
Explanation:
The
launch
failed
due
to
an
internal
error
in
IBM
Tivoli
Business
Systems
Manager.
System
Action:
The
GTMJC0538E
message
is
issued
to
the
operator.
The
system
is
available
for
other
requests,
but
other
launch
requests
can
also
fail.
Operator
Response:
Turn
on
all
tracing
and
try
to
recreate
the
problem.
Provide
the
console
logs
to
your
administrator.
Administrator
Response:
If
the
problem
persists,
gather
the
operator
furnished
logs,
text
exports
of
the
MenuItem
table
entry
and
RDM_LAUNCHER
table
entry
for
this
launch
and
contact
Customer
Support.
Provide
all
the
gathered
documentation.
GTMJC0539W
Deleting
resource
removes
the
business
system
and
all
its
children.
Do
you
want
to
delete
this
business
system
and
all
its
children?
Explanation:
You
are
deleting
a
business
system
and
all
its
children.
This
business
system
and
its
children
are
removed
from
all
views
that
contain
this
business
system.
System
Action:
This
business
system
and
its
children
are
removed
from
the
business
systems
tree
and
from
all
views
that
contain
this
business
system.
Operator
Response:
Confirm
the
deletion
of
this
business
system
and
its
children.
GTMJC0540W
resource
is
the
source
business
system
for
number_of_shortcuts
business
system
shortcuts.
Deleting
this
business
system
folder
removes
it
and
all
its
children.
Each
business
system
shortcut
will
be
marked
to
indicate
that
the
source
business
system
folder
was
deleted.
The
children
will
no
longer
be
visible
from
the
business
system
shortcuts.
Do
you
want
to
delete
this
business
system
folder
that
has
business
system
shortcuts,
and
all
its
children?
Explanation:
You
are
deleting
a
business
system
folder
and
all
its
children,
which
will
affect
the
business
system
shortcuts
that
are
linked
to
the
business
system
folder.
This
business
system
folder
is
removed
from
all
views,
and
its
children
are
removed
from
all
views
that
contain
this
resource
or
any
of
its
business
system
shortcuts.
The
business
system
shortcuts
will
be
marked
to
indicate
that
the
source
business
system
folder
was
deleted.
See
Understanding
Business
System
Shortcuts
and
Resource
Indicators
for
additional
information.
System
Action:
This
business
system
folder
and
its
children
are
removed
from
the
business
systems
tree
and
from
all
views
that
contain
this
business
system
folder.
Any
view
that
contains
a
business
system
shortcut
that
is
linked
to
this
resource
is
also
modified
to
remove
the
children
and
to
indicate
the
removal
of
the
source
business
system
folder.
Operator
Response:
Confirm
the
deletion
of
this
business
system
folder
that
is
linked
to
one
or
more
business
system
shortcuts,
and
its
children.
GTMJC0541W
resource
is
the
source
business
system
folder
for
number_of_shortcuts
business
system
shortcuts.
Deleting
this
business
system
folder
removes
it
and
all
its
children
from
parent.
Each
business
system
shortcut
will
be
marked
to
indicate
that
the
source
business
system
folder
was
deleted.
The
children
will
no
longer
be
visible
from
the
business
systems
shortcuts.
Do
you
want
to
delete
this
business
system
folder
that
has
business
system
shortcuts,
and
all
its
children?
Explanation:
You
are
deleting
a
business
system
folder
that
is
contained
in
another
business
system,
and
all
its
children.
Deleting
this
business
system
folder
will
affect
the
business
system
shortcuts
that
are
linked
to
this
194
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
business
system
folder.
This
business
system
folder
is
removed
from
all
views,
and
its
children
are
removed
from
all
views
that
contain
this
business
system
folder,
or
one
of
its
shortcuts.
The
business
system
shortcuts
will
be
marked
to
indicate
that
the
source
business
system
folder
was
deleted.
See
Understanding
Business
System
Shortcuts
and
Resource
Indicators
for
additional
information.
System
Action:
This
business
system
folder
and
its
children
are
removed
from
the
specified
parent
business
system
in
the
business
systems
tree,
and
from
all
views
that
contain
this
business
system
folder.
Any
view
that
contains
a
business
system
shortcut
that
is
linked
to
this
resource
is
modified
to
remove
the
children
and
to
indicate
the
removal
of
the
source
business
system
folder.
Operator
Response:
Confirm
the
deletion
of
this
business
system
folder
that
is
linked
to
one
or
more
business
system
shortcuts,
and
its
children.
GTMJC0542W
You
are
resetting
the
customized
attributes
of
a
business
system
shortcut
to
the
attributes
of
the
source
business
system
folder
that
it
was
created
from.
Doing
this
will
reset
the
customized
attributes
of
the
business
system
shortcut
to
those
of
its
source
business
system
folder.
You
will
lose
any
individual
customization
of
attributes
and
propagation
settings
that
you
might
have
performed.
Are
you
sure
you
want
to
reset
the
attributes
of
the
selected
business
system
shortcut?
Explanation:
You
are
resetting
the
customized
attributes
of
the
selected
business
system
shortcut
to
those
of
the
source
business
system
that
it
was
created
from.
If
you
reset
the
customized
attributes
of
this
business
system
shortcut,
future
changes
to
the
same
attributes
of
the
source
business
system
folder
will
be
applied
to
this
business
system
shortcut.
See
Understanding
Business
System
Shortcuts
for
additional
information.
System
Action:
If
you
reset
the
customized
attributes
of
this
business
system
shortcut,
the
attributes
will
be
reset
to
those
of
the
source
business
system
folder
and
future
changes
to
the
source
will
also
be
applied
to
this
shortcut.
Administrator
Response:
Confirm
that
you
want
to
reset
the
attributes
of
this
business
system
shortcut
and
click
the
appropriate
button.
GTMJC0543W
You
are
about
to
delete
resource,
which
is
a
business
system
shortcut.
Deleting
this
business
system
shortcut
removes
it
from
the
business
systems
tree
and
from
all
views
that
contain
this
business
system
shortcut.
Do
you
want
to
delete
this
business
system
shortcut?
Explanation:
You
are
deleting
a
business
system
shortcut.
This
business
system
shortcut
will
be
removed
from
the
business
systems
tree
and
from
all
views
that
contain
this
shortcut.
Because
the
children
of
the
business
system
shortcut
are
derived
from
the
source
business
system,
the
children
will
be
removed
from
all
views
that
contain
the
business
system
shortcut,
but
the
children
resources
will
not
be
deleted.
See
Understanding
Business
System
Shortcuts
for
additional
information.
System
Action:
This
business
system
shortcut
will
be
deleted
and
views
that
contain
the
shortcut
will
be
updated
to
remove
the
shortcut
and
its
children.
The
children
resources
will
not
be
removed
from
the
database
because
they
belong
to
the
source
business
system.
Operator
Response:
Confirm
the
deletion
of
this
business
system
shortcut.
GTMJC0544W
You
are
about
to
delete
resource,
which
is
a
business
system
shortcut,
from
parent.
Deleting
this
business
system
shortcut
removes
it
from
the
specified
parent
business
system
and
from
all
views
that
contain
this
business
system
shortcut.
Do
you
want
to
delete
this
business
system
shortcut?
Explanation:
You
are
deleting
a
business
system
shortcut.
This
business
system
shortcut
will
be
removed
from
the
specified
parent
business
system
and
from
all
views
that
contain
the
shortcut.
Because
the
children
of
the
business
system
shortcut
are
derived
from
the
source
business
system,
they
will
be
removed
from
all
views
that
contain
the
business
system
shortcut,
but
the
children
resources
will
not
be
deleted.
See
Understanding
Business
System
Shortcuts
for
additional
information.
System
Action:
This
business
system
shortcut
will
be
deleted
and
views
that
contain
the
shortcut
will
be
updated
to
remove
this
shortcut
and
its
children.
The
children
resources
will
not
be
removed
from
the
database
because
they
belong
to
the
source
business
system.
Operator
Response:
Confirm
the
deletion
of
this
business
system
shortcut.
GTMJC0546I
The
user
registry
cache
refresh
completed
successfully.
Explanation:
The
refresh
of
the
console
server
user
registry
cache
that
you
requested
has
completed
without
error.
System
Action:
Processing
continues.
Chapter
16.
Console
Messages
-
GTMJC0502I
-
GTMJC9191I
195
Operator
Response:
None
required
Administrator
Response:
None
required
GTMJC0547E
The
console
server
is
unable
to
validate
the
user
name
or
group
because
of
an
internal
error.
Contact
the
administrator
user_id.
Explanation:
The
user
name
cannot
log
on
or
be
authorized
to
use
IBM
Tivoli
Business
Systems
Manager
because
of
an
internal
error.
System
Action:
The
user
is
prompted
to
try
again.
Operator
Response:
Contact
the
administrator.
Administrator
Response:
Ensure
that
the
console
server
has
been
correctly
configured
as
documented
in
the
IBM
Tivoli
Business
Systems
Manager
Administrator’s
Guide.
If
the
problem
persists,
contact
Customer
Support.
GTMJC0548E
An
error
occurred
accessing
the
user
registry.
Diagnostic
information:
diaginfo
Explanation:
An
error
was
encountered
when
accessing
the
user
registry.
System
Action:
The
system
cancels
the
failed
operation.
Operator
Response:
Retry
the
operation.
If
the
problem
persists,
contact
the
administrator.
Administrator
Response:
The
message
contains
diagnostic
information
provided
by
the
user
registry
that
could
be
helpful
in
determining
the
cause
of
the
error.
Other
actions
you
can
take
to
isolate
user
registry
problems
include:
v
If
you
are
using
a
Lightweight
Directory
Access
Protocol
user
registry,
verify
that
the
directory
server
is
running
and
that
network
connectivity
exists
between
it
and
the
console
server.
v
Verify
that
security
settings
are
correct
in
the
WebSphere
Application
Server,
including
any
userid,
password,
or
certificate
needed
to
access
the
Lightweight
Directory
Access
Protocol
server.
v
If
the
message
occurs
while
processing
a
specific
user
or
group
name,
verify
that
the
name
syntax
and
spelling
are
those
expected
by
the
user
registry.
GTMJC0549E
The
user
name
user_name
could
not
be
validated.
Try
again
or
contact
the
administrator.
Explanation:
The
user
name
could
not
be
authenticated.
System
Action:
The
operator
is
prompted
to
correct
the
user
name,
password,
or
both.
Operator
Response:
Ensure
your
user
name
and
password
are
correct
and
attempt
to
log
on
again.
If
the
problem
persists,
contact
the
administrator.
Administrator
Response:
Ensure
that
the
user
name
and
password
are
valid.
If
the
problem
persists,
contact
Customer
Support.
GTMJC0550E
The
user
name
user_name
does
not
have
access
to
the
console.
Contact
the
administrator.
Explanation:
This
occurs
when
the
user
name
is
not
a
member
of
a
group
authorized
to
use
IBM
Tivoli
Business
Systems
Manager.
System
Action:
The
operator
is
prompted
to
try
again
when
the
problem
has
been
corrected
by
the
administrator.
Operator
Response:
Contact
the
administrator.
Administrator
Response:
For
the
sign
on
to
proceed,
the
specified
user
must
be
mapped
to
one
of
the
following
roles
for
the
console
server
application:
TBSM_Administrators,
TBSM_Administrators_Super,
TBSM_Operators,
TBSM_Operators_Restricted.
See
the
IBM
Tivoli
Business
Systems
Manager
Administrator’s
Guide
for
details.
If
the
problem
persists,
contact
Customer
Support.
GTMJC0551E
The
launch
in
failed.
The
launch
in
argument
launch_arg
was
not
specified.
Contact
the
administrator.
Explanation:
You
started
a
launch
to
the
console
from
another
product.
The
launch
failed
because
the
context
data
given
to
console
was
incomplete.
System
Action:
The
GTMJC0551E
message
is
issued
to
the
operator.
The
system
is
available
for
other
requests.
Operator
Response:
Turn
on
all
tracing
and
try
to
recreate
the
problem.
Provide
the
console
logs
to
the
administrator.
Administrator
Response:
Examine
the
menu
item
and
launch
definitions
of
the
launch
initiator
application,
correct
the
argument
in
error,
and
stop
and
start
the
initiating
application.
Try
the
launch
again.
If
it
fails,
contact
Customer
Support
and
provide
the
console
logs,
menu
item,
and
launch
table
entries
from
the
initiating
application.
GTMJC0552E
The
launch
in
failed.
The
launch
in
argument
launch_arg
was
not
valid.
Contact
the
administrator.
Explanation:
A
launch-in
to
the
console
from
another
application
failed.
Some
or
all
of
the
launch
in
context
data
was
not
valid.
System
Action:
Message
GTMJC0552E
is
issued
to
the
196
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
operator.
The
system
is
available
for
other
requests.
Operator
Response:
Turn
on
all
tracing
in
the
initiating
application.
Try
to
recreate
the
problem.
Provide
the
logs
from
both
applications
to
the
administrator.
Administrator
Response:
Correct
the
launch-in
data
in
the
initiating
programs
launch
table
or
menu
item
entry.
If
the
problem
persists,
contact
Customer
Support
and
provide
the
logs
and
the
table
entries
from
the
initiating
application.
GTMJC0553E
Unauthorized
launch
in
connection
from
non
local
host
to
this
host
local_host_id
non-local_internet_address.
Connection
closed.
Explanation:
A
program
attempted
to
connect
to
the
port
to
which
IBM
Tivoli
Business
Systems
Manager
listens
for
launch-in
connections.
The
connection
was
rejected
because
the
program
and
the
console
are
running
on
different
hosts.
System
Action:
Message
GTMJC0553E
is
issued
to
the
operator.
The
system
is
available
for
other
requests.
Operator
Response:
Contact
the
administrator
and
provide
the
local
host
name
and
the
non-local
address
listed
in
the
message.
Administrator
Response:
If
this
is
a
required
launch-in,
move
the
initiating
program
onto
the
host
where
the
console
you
want
to
launch
is
running.
GTMJC0554E
The
launch
in
failed.
No
matching
resource
was
found
to
display.
Contact
the
administrator.
Explanation:
The
data
to
identify
a
resource
to
be
displayed
did
not
match
any
resource
in
the
IBM
Tivoli
Business
Systems
Manager
database.
System
Action:
Message
GTMJC0554E
is
issued
to
the
operator.
The
system
is
available
for
other
requests.
Operator
Response:
Search
in
the
console
logs
for
the
string
retrieveTMResource.
Find
the
string
run
request
in
a
prior
log
record.
Look
for
the
data
that
begins
with
Handler=.
Supply
the
data
to
the
administrator.
Administrator
Response:
The
console
uses
the
Handler
data
to
locate
and
display
a
resource
in
a
view.
No
matching
resource
was
found.
Determine
why
the
program
initiating
the
launch
did
not
supply
the
correct
data
or
why
the
IBM
Tivoli
Business
Systems
Manager
database
does
not
contain
the
resource.
Correct
the
situation
and
try
the
launch
again.
See
the
section
about
configuring
launch
entries
within
the
console
in
the
IBM
Tivoli
Business
Systems
Manager
Installation
and
Configuration
Guide.
GTMJC0555E
A
value
for
a
required
field
is
not
specified.
Explanation:
Fields
marked
with
an
asterisk
are
required.
When
a
service
is
created
or
modified,
values
for
all
required
fields
must
be
specified.
System
Action:
Console
processing
continues,
but
data
is
not
saved.
Administrator
Response:
Specify
a
value
for
the
required
field
or
cancel
the
request.
GTMJC0558E
An
error
occurred
deleting
workspace
workspace
Explanation:
You
attempted
to
delete
a
workspace,
but
this
function
did
not
complete
successfully.
System
Action:
The
console
processing
continues,
but
the
workspace
was
not
deleted.
Operator
Response:
Attempt
to
delete
the
workspace
again.
If
the
problem
persists,
notify
the
administrator.
Administrator
Response:
Verify
that
available
disk
space
exists
on
the
database
server
and
that
the
console
server
and
database
server
are
both
running.
GTMJC0560E
Cannot
save
an
empty
workspace.
Explanation:
You
attempted
to
save
a
workspace
without
having
an
open
workspace
view.
This
is
not
supported.
System
Action:
The
console
processing
continues,
but
no
workspace
is
saved.
Operator
Response:
Click
OK
in
the
message
box.
Open
a
view
before
you
attempt
to
save
a
workspace.
Administrator
Response:
Notify
the
operator
that
empty
views
cannot
be
saved
as
a
workspace.
Have
the
operator
open
a
view
before
attempting
to
save
a
workspace.
GTMJC0561W
The
workspace_name
workspace
is
a
shared
workspace
that
can
only
be
saved
by
administrators.
Would
you
like
to
save
this
as
a
private
workspace?
Explanation:
You
attempted
to
save
an
administrator
only
workspace.
You
are
not
allowed
to
overwrite
the
existing
shared
workspace,
but
you
can
save
it
as
a
private
workspace.
System
Action:
The
console
processing
continues.
A
private
workspace
is
saved
if
you
click
Yes.
If
you
click
No,
the
workspace
is
not
saved.
Operator
Response:
Click
Yes
in
the
message
box
if
you
want
to
save
a
private
version
of
the
shared
workspace.
If
you
do
not,
click
No
and
the
workspace
is
not
saved.
Chapter
16.
Console
Messages
-
GTMJC0502I
-
GTMJC9191I
197
Administrator
Response:
An
operator
cannot
save
a
shared
workspace
owned
by
an
administrator.
Instruct
the
operator
to
click
Yes
or
No
in
the
message
box
depending
on
whether
they
want
to
save
the
workspace
as
a
private
workspace.
GTMJC0562E
The
default
workspace
workspace_name
cannot
be
opened.
Explanation:
The
console
tried
to
automatically
load
the
default
workspace
while
starting,
but
was
unable
to
access
it.
System
Action:
The
console
processing
continues,
but
without
opening
the
default
workspace.
Operator
Response:
Restart
the
console.
Load
the
default
workspace,
or
continue
to
use
the
console
and
manually
open
the
desired
views.
Select
Console
->
Open
Workspace
to
open
a
saved
workspace.
If
the
problem
persists,
contact
the
administrator.
Administrator
Response:
Verify
that
the
workspace
exists
and
has
not
been
deleted,
and
that
the
operator
attempting
to
open
the
workspace
is
included
in
the
workspace
access
list.
GTMJC0563W
The
selected
task
selected_task
is
currently
running.
Are
you
sure
you
want
to
remove
the
selected
task?
Explanation:
You
requested
to
remove
a
task
that
is
currently
running.
System
Action:
Removing
a
running
task
removes
the
task
from
the
Task
Monitor,
but
does
not
necessarily
cancel
the
running
task
and
could
lead
to
unpredictable
results
in
the
console.
Operator
Response:
To
safely
remove
a
task
from
the
Task
Monitor,
use
the
Remove
command
on
a
selected
task
that
does
not
have
a
Running
status.
Administrator
Response:
This
message
occurs
when
the
user
selects
Remove
for
a
running
task.
It
is
a
typical
operation
to
notify
the
user
of
this
scenario.
If
necessary,
explain
to
the
user
that
the
task
should
be
canceled
and
then
removed.
GTMJC0565I
There
are
currently
no
created
tasks.
To
view
a
task
in
the
Task
Monitor
the
task
must
be
started,
running,
or
finished
running.
Explanation:
There
are
currently
no
created
tasks
and
there
are
no
tasks
to
monitor.
System
Action:
The
Task
Monitor
view
is
not
displayed.
Operator
Response:
You
can
open
the
Task
Monitor
if
a
task
is
started,
running,
or
finished
running.
GTMJC0566W
number_of_running_tasks
of
the
number_of_selected_tasks
selected
tasks
are
currently
running.
Are
you
sure
you
want
to
remove
all
selected
tasks?
Explanation:
You
requested
to
remove
at
least
one
task
that
is
currently
running
in
the
Task
Monitor.
System
Action:
Removing
a
running
task
removes
the
task
from
the
Task
Monitor,
but
does
not
necessarily
cancel
the
running
task
and
could
lead
to
unpredictable
results
in
the
console.
Operator
Response:
To
safely
remove
a
task
from
the
Task
Monitor,
use
the
Remove
command
on
selected
tasks
that
do
not
have
a
Running
status.
Administrator
Response:
This
message
occurs
when
the
user
selects
Remove
for
a
running
task.
It
is
a
typical
operation
to
notify
the
user
of
this
scenario.
If
necessary,
explain
to
the
user
that
the
task
should
be
canceled
then
removed.
GTMJC0567E
The
task
has
been
removed
from
the
Task
Monitor.
Explanation:
You
are
attempting
to
locate
a
task
that
has
been
removed
from
the
Task
Monitor.
System
Action:
The
task
that
has
been
removed
from
the
Task
Monitor
is
not
located.
Operator
Response:
None.
Once
a
task
has
been
removed
from
the
Task
Monitor,
you
cannot
retrieve
it.
Administrator
Response:
This
message
occurs
when
the
user
has
removed
a
task
from
the
Task
Monitor
and
then
attempts
to
locate
that
task.
Once
a
task
has
been
removed
from
the
Task
Monitor,
the
user
cannot
retrieve
it.
GTMJC0568I
An
error
occurred
updating
a
resource
name.
Explanation:
An
error
occurred
while
updating
the
logical
resource
name.
System
Action:
The
console
continues
processing.
The
resource
name
has
not
been
updated.
Operator
Response:
Contact
the
administrator.
Administrator
Response:
An
error
occurred
renaming
a
resource
name.
Create
a
new
logical
resource
based
on
this
physical
resource.
If
the
problem
persists,
contact
Customer
Support.
GTMJC0569W
Resource
with
cid:
res_cid
is
not
available.
Explanation:
The
system
could
not
obtain
the
properties
information
for
the
resource.
198
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
System
Action:
Processing
continues,
but
without
the
properties
information.
Operator
Response:
If
the
problem
persists,
contact
Customer
Support.
Administrator
Response:
If
the
problem
persists,
contact
Customer
Support.
GTMJC0570W
Resource
with
cid:
res_cid,
id:
res_id
was
not
found.
Any
views
based
on
this
resource
are
closed.
Explanation:
The
system
could
not
obtain
the
attributes
for
the
resource.
Usually,
this
means
that
the
resource
has
been
deleted
from
the
database.
This
message
is
displayed
when
you
open
a
workspace
that
references
a
resource
that
no
longer
exists
in
the
database.
System
Action:
The
system
closes
the
views
that
are
rooted
at
the
resource.
Operator
Response:
If
the
message
is
displayed
when
you
open
a
workspace,
save
the
workspace
to
remove
the
reference
to
the
deleted
resource.
If
the
problem
occurs
in
cases
not
involving
a
deleted
resource,
contact
Customer
Support.
Administrator
Response:
If
the
message
appears
when
you
open
a
workspace,
save
the
workspace
to
remove
the
reference
to
the
deleted
resource.
If
this
problem
occurs
in
cases
not
involving
a
deleted
resource,
contact
Customer
Support.
GTMJC0571E
Unable
to
launch
the
Web
browser.
The
command
was:
cmd_txt
Explanation:
The
Web
browser
failed
to
start
or
an
IO
error
occurred
during
processing.
System
Action:
The
system
is
available
for
other
requests.
Operator
Response:
Look
at
the
Web
browser
setting
in
Console
->
Preferences
->
General.
If
Use
a
specific
Web
browser
is
selected,
make
sure
that
the
specified
path
is
correct
and
make
sure
the
directory
is
in
the
PATH.
Try
the
operation
again
with
all
tracing
enabled
and
gather
the
logs.
Administrator
Response:
If
the
problem
persists,
manually
try
to
use
the
URL
in
the
browser.
If
a
specific
browser
is
indicated
on
the
Console
->
Preferences
->
General
page,
try
running
it
from
a
command
line.
If
the
problem
persists,
gather
the
logs
and
snapshots
of
the
entry
in
the
MenuItem
table
that
creates
the
menu
item
that
launches
the
browser
and
contact
Customer
Support.
See
the
section
on
URL
Launch
in
the
IBM
Tivoli
Business
Systems
Manager
Administrator’s
Guide
for
more
details.
GTMJC0572E
The
object
class
obj_class
was
not
found
in
the
database.
Explanation:
A
database
query
for
the
specified
object
class
failed.
System
Action:
Object
class
information
was
not
returned.
Operator
Response:
Contact
your
administrator.
Administrator
Response:
See
the
console
log
for
error
messages
that
could
explain
the
problem.
GTMJC0573W
Deleting
resource_name
permanently
removes
the
physical
resource
and
all
its
children
from
the
database.
All
business
system
resources
that
are
linked
to
this
physical
resource
are
marked
as
deleted
in
the
business
system
tree.
Do
you
want
to
delete
this
physical
resource
and
all
its
children?
Explanation:
You
are
deleting
a
resource
that
represents
a
physical
resource.
Any
children
of
this
resource
are
also
deleted.
If
this
resource
or
any
of
its
children
appear
in
a
business
system,
they
are
marked
as
deleted.
System
Action:
This
resource
and
its
children
are
deleted.
Any
business
systems
that
contain
this
resource
or
its
children
will
be
updated
to
mark
the
resources
as
deleted.
Operator
Response:
Confirm
the
deletion
of
this
resource
and
its
children.
GTMJC0574W
At
least
one
resource
must
be
selected
for
the
copy
function.
Explanation:
One
or
more
resources
must
be
selected
for
the
copy
function.
System
Action:
No
copy
operation
was
performed.
Operator
Response:
Select
one
or
more
resources
and
try
the
copy
function
again.
GTMJC0575W
A
single
resource
must
be
selected
as
an
insertion
point
for
the
paste
function.
Explanation:
A
single
resource
must
be
selected
to
act
as
the
insertion
point
for
the
paste
function.
The
insertion
point
acts
as
the
parent
of
the
pasted
resources.
System
Action:
No
paste
function
was
performed.
Operator
Response:
Select
a
single
resource
and
perform
the
paste
function
again.
Chapter
16.
Console
Messages
-
GTMJC0502I
-
GTMJC9191I
199
GTMJC0576W
The
paste
function
is
not
supported
in
the
current
view.
Explanation:
The
paste
function
is
only
valid
when
defining
a
business
system
tree
view.
System
Action:
No
paste
function
was
performed.
Operator
Response:
Open
a
business
system
and
use
the
paste
function
to
add
new
resources
in
the
view.
GTMJC0578E
The
query
returned
too
many
rows.
Submit
the
query
with
more
restrictive
criteria.
Explanation:
The
query
resulted
in
more
rows
than
can
be
returned
by
the
console
server.
System
Action:
The
operator
is
informed
so
that
they
can
use
more
restrictive
criteria.
Operator
Response:
Change
the
column
filters
so
that
the
query
is
more
specific.
GTMJC0579E
The
query
returned
is
num_rows
rows.
Submit
the
query
with
more
restrictive
criteria.
Explanation:
The
query
resulted
in
more
rows
than
can
be
returned
by
the
console
server.
System
Action:
The
operator
is
informed
so
they
can
use
more
restrictive
criteria.
Operator
Response:
Change
the
column
filters
so
that
the
query
is
more
specific.
GTMJC0580W
Deleting
the
uncategorized
MVS
resource
res_name.
Do
you
want
to
delete
this
resource?
Explanation:
The
named
resource
is
about
to
be
deleted.
If
you
do
not
want
to
delete
the
resource,
click
No.
Otherwise,
click
Yes.
System
Action:
After
answering
the
confirmation
message,
the
system
is
available
for
other
requests.
Operator
Response:
Answer
the
message
confirmation.
GTMJC0581W
Deleting
the
selected
uncategorized
MVS
resources.
Do
you
want
to
delete
these
uncategorized
MVS
resources?
Explanation:
The
selected
resources
are
going
to
be
deleted.
If
you
do
not
want
to
delete
the
resources,
click
No.
Otherwise,
click
Yes.
System
Action:
After
answering
the
confirmation
message,
the
system
is
available
for
other
requests.
Operator
Response:
Answer
the
message
confirmation.
GTMJC0582E
The
reclassify
failed.
No
target
classes
are
available.
Contact
the
administrator.
Explanation:
The
console
was
unable
to
build
a
list
of
target
classes
for
the
re-categorization
of
the
MVS
uncategorized
resources.
System
Action:
The
system
is
available
for
other
requests,
but
results
can
be
unpredictable.
This
error
indicates
the
database
could
be
damaged.
Operator
Response:
Turn
on
all
tracing
and
try
the
request
again.
If
the
problem
persists,
copy
the
console
logs
and
notify
the
administrator.
Administrator
Response:
If
this
problem
persists,
contact
Customer
Support
and
provide
the
console
and
console
server
logs.
GTMJC0583E
The
reclassify
action
failed.
A
complex
resource
was
not
found.
Contact
the
administrator.
Explanation:
An
internal
error
occurred
in
the
console
or
console
server
code.
The
database
could
be
damaged.
System
Action:
The
system
is
available,
but
results
could
be
unpredictable.
Operator
Response:
Turn
on
all
tracing
and
repeat
the
request.
Copy
the
console
logs
and
give
them
to
the
administrator.
Make
a
list
of
all
parents
of
the
selected
uncategorized
MVS
resource.
Administrator
Response:
Contact
Customer
Support
and
provide
the
console
and
console
server
logs
and
the
operator’s
list
of
parent
resources.
GTMJC0585E
The
database
access
timed
out
or
was
canceled.
Detailed
information:
detail_info
Explanation:
A
call
to
the
IBM
Tivoli
Business
Systems
Manager
database
did
not
complete
within
the
allotted
time.
Processing
of
the
request
by
the
console
server
is
stopped.
System
Action:
Processing
of
the
request
is
stopped.
Operator
Response:
Try
the
operation
again.
If
the
problem
persists,
contact
the
administrator.
Administrator
Response:
If
the
problem
occurs
during
periods
of
heavy
IBM
Tivoli
Business
Systems
Manager
database
usage,
you
can
increase
the
time-out
value
for
the
console
server
and
the
database
accesses
by
increasing
the
value
specified
for
com.tivoli.tbsm.server.DBManager.activeTimeout
in
the
Servers.properties
file.
You
must
restart
the
console
server
for
changes
in
the
Servers.properties
file
to
take
affect.
If
this
problem
persists
or
appears
to
be
related
to
a
200
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
specific
operation,
contact
Customer
Support.
GTMJC0586I
The
default
filters
for
the
Events
view
are:
Minimum
alert
state:
Yellow
Time:
Within
the
last
30
minutes
Do
you
want
to
run
the
database
query
immediately
using
these
default
filters,
or
do
you
want
to
specify
filters?
Explanation:
The
console
provides
default
filters
for
the
Events
view.
You
can
use
these
filters
immediately
and
run
the
database
query
to
return
results.
Because
this
could
take
some
time,
depending
on
the
number
of
events
in
the
system,
you
can
bypass
this
query
and
set
your
own
filters.
System
Action:
The
Event
view
opens
and
the
console
waits
until
the
operator
selects
one
of
two
options.
Operator
Response:
Click
Run
Default
Query
to
run
the
database
query
immediately.
The
Events
view
displays
the
results.
Click
Cancel
to
display
the
Events
view,
which
is
empty.
You
can
then
specify
your
own
filters
and
click
the
Refresh
icon
in
the
lower
right
corner
of
the
view.
GTMJC0587I
The
scheduled
state:
UNKNOWN
is
added
in
the
list
of
scheduledState_
type
Explanation:
The
UNKNOWN
state
is
added
as
an
option
for
the
scheduled
state.
System
Action:
Console
processing
continues.
The
UNKNOWN
scheduled
state
is
considered
as
the
other
scheduled
state
in
the
database.
GTMJC0588E
Scheduled
State:
state_name
is
not
allowed
for
this
cid.
Explanation:
The
wrong
scheduled
state
is
selected
for
this
resource.
System
Action:
The
system
provides
an
exception
and
continues
processing.
Operator
Response:
This
condition
should
not
occur
unless
the
database
for
the
scheduled
state
data
has
been
damaged.
Administrator
Response:
The
error
for
this
message
occurs
only
when
the
database
for
this
field
is
damaged.
Fix
the
data
in
the
database.
If
the
problem
persists,
contact
Customer
Support.
GTMJC0589E
The
connection
to
the
server
has
been
lost.
The
console
continues
trying
to
reconnect
until
a
connection
is
successful
or
until
it
is
closed.
To
close
and
exit
the
console,
click
Close.
Connection
attempts:
conn_attmpts
Explanation:
The
console
has
stopped
receiving
updates
from
the
console
server
and
is
attempting
to
reconnect
to
the
server.
System
Action:
The
console
continues
to
attempt
to
reconnect
to
the
console
server
until
successful
or
the
console
is
manually
closed.
The
status
of
resources
are
not
updated
until
the
connection
is
re-established.
Operator
Response:
Click
Close
to
close
the
console,
or
allow
the
system
to
automatically
restore
the
connection.
Administrator
Response:
If
the
problem
occurs
intermittently,
it
could
be
due
to
network
traffic
or
a
transient
network
problem.
If
the
connection
is
not
re-established
in
a
few
minutes,
verify
that:
1.
The
TCP/IP
network
is
functioning
correctly.
2.
The
console
server
is
running.
If
the
problem
seems
to
be
related
to
a
specific
operation,
contact
Customer
Support
and
describe
the
situation
leading
up
to
the
failure.
GTMJC0590E
The
attempt
to
connect
to
RDM_name
timed
out.
Explanation:
The
application
was
started.
The
console
was
unable
to
connect
to
the
application
to
pass
the
application
context
data.
System
Action:
Processing
continues.
Operator
Response:
Look
for
the
entry
in
the
RDM_LAUNCHER
table
for
the
launched
application.
The
entry
specifies
the
port
numbers
on
which
IBM
Tivoli
Business
Systems
Manager
attempts
to
connect.
Ensure
that
the
launched
application
is
listening
on
a
port
in
the
specified
port
range.
Is
the
launched
application
waiting
for
the
operator
to
log
on?
IBM
Tivoli
Business
Systems
Manager
attempts
the
connection
for
a
limited
amount
of
time.
Administrator
Response:
If
the
operator
did
not
have
enough
time
to
log
on
to
the
launched
application,
increase
the
WAIT_TIME,
the
RETRY_COUNT,
or
both
for
the
launched
application
entry
in
the
RDM_LAUNCHER
table.
If
the
problem
persists,
recreate
the
problem
with
all
tracing
on
and
the
target
application
enabled.
Gather
the
logs
from
both
programs,
contact
Customer
Support,
and
provide
the
documentation.
GTMJC0591E
The
resource
resource_name
could
not
be
created
because
it
would
result
in
a
business
system
that
is
a
descendant
of
an
identical
business
system.
Explanation:
A
business
system
was
created
that
is
a
descendant
of
another
one
linked
to
the
same
resource.
This
is
not
supported.
Chapter
16.
Console
Messages
-
GTMJC0502I
-
GTMJC9191I
201
System
Action:
The
resource
is
not
created
and
processing
continues.
Operator
Response:
Create
the
business
system
with
a
different
parent
resource.
Administrator
Response:
Create
the
business
system
with
a
different
parent
resource.
GTMJC0592W
The
registered_files
of
selected_files
selected
FILE
resources
are
already
registered.
Do
you
want
the
unregistered_files
that
are
unregistered
FILE
resources
to
be
registered?
Explanation:
If
you
want
the
selected
unregistered
FILE
resources
to
be
registered,
select
Yes.
If
not,
select
No.
System
Action:
None
Operator
Response:
Select
Yes
or
No
for
the
preferred
action.
GTMJC0593W
The
unregistered_files
of
selected_files
selected
FILE
resources
are
already
unregistered.
Do
you
want
the
registered_files
that
are
registered
FILE
resources
to
be
unregistered?
Explanation:
If
you
want
the
selected
registered
FILE
resources
to
be
unregistered,
select
Yes.
If
not,
select
No.
System
Action:
None
Operator
Response:
Select
Yes
or
No
for
the
preferred
action.
GTMJC0594E
The
resource
cid:
res_cid,
id:
res_id
could
not
be
deleted
because
it
is
a
shared
resource.
Explanation:
The
resource
was
not
deleted
because
it
is
a
shared
resource
and
the
system
could
not
determine
from
the
context
which
instance
of
sharing
should
be
removed.
System
Action:
The
resource
remains
unchanged
and
processing
continues.
Operator
Response:
Try
deleting
the
resource
from
a
different
view,
such
as
a
tree
view,
so
that
the
system
can
determine
the
context
of
the
delete
operation.
Administrator
Response:
Try
deleting
the
resource
from
a
different
view,
such
as
a
tree
view,
so
that
the
system
can
determine
the
context
of
the
delete
operation.
GTMJC0595E
The
resource
cid:
res_cid,
id:
res_id
could
not
be
deleted
because
it
is
directly
contained
and
referenced
in
one
or
more
other
locations.
Explanation:
The
resource
you
tried
to
delete
is
a
directly
contained
resource
that
is
referenced
by
other
links.
It
cannot
be
deleted
because
it
would
invalidate
the
other
links.
System
Action:
The
resource
remains
unchanged
and
processing
continues.
Operator
Response:
Open
the
Business
Impact
view
to
see
the
other
locations
where
the
resource
appears.
Administrator
Response:
Open
the
Business
Impact
view
to
see
the
other
locations
where
the
resource
appears.
GTMJC0596E
Priority
entry
does
not
contain
this
priority
value,
or
null
priority
entry
Explanation:
The
selected
priority
value
is
not
one
of
the
priority
entries
or
no
priority
entry
exists.
System
Action:
The
console
processing
continues.
Administrator
Response:
This
error
is
ignored
and
the
first
entry
in
the
priority
listing
is
selected
as
the
default
value.
GTMJC0597E
You
cannot
drop
or
paste
the
resource
res_cid
into
a
Business
System
view.
Explanation:
The
resource
you
tried
to
drop
or
paste
into
a
Business
System
view
represents
a
Critical
Resource
List.
Critical
Resource
Lists
cannot
be
included
in
other
business
systems.
System
Action:
The
drop
or
paste
operation
cannot
proceed.
Operator
Response:
Select
other
resources
to
drop
or
paste
into
the
Business
System
view.
Administrator
Response:
Select
other
resources
to
drop
or
paste
into
the
Business
System
view.
GTMJC0598W
registered_transactions
of
selected_transactions
selected
TRANSACTION
resources
are
already
registered.
Do
you
want
the
unregistered_transactions
unregistered
TRANSACTION
resources
to
be
registered?
Explanation:
The
program
is
confirming
that
Register
is
the
preferred
action.
System
Action:
If
the
user
clicks
Yes,
the
selected
unregistered
transaction
resources
will
be
registered.
If
the
user
clicks
No,
no
resource
will
be
registered.
Operator
Response:
Click
Yes
if
you
want
the
selected
202
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
unregistered
transaction
resources
to
be
registered.
Otherwise
click
No.
Administrator
Response:
This
is
a
typical
situation
that
occurs
when
both
registered
and
unregistered
transactions
are
selected.
Instruct
the
operator
to
click
Yes
or
No
based
on
the
preferred
action.
GTMJC0599W
unregistered_transactions
of
selected_transactions
selected
TRANSACTION
resources
are
already
unregistered.
Do
you
want
the
registered_transactions
registered
TRANSACTION
resources
to
be
unregistered?
Explanation:
The
program
is
confirming
that
unregistering
is
the
preferred
action.
System
Action:
If
the
user
clicks
Yes,
the
selected
registered
transaction
resources
will
be
unregistered.
If
the
user
clicks
No,
no
resource
will
be
unregistered.
Operator
Response:
Click
Yes
if
you
want
the
selected
registered
transaction
resources
to
be
unregistered,
otherwise
click
No.
Administrator
Response:
This
is
a
typical
situation
that
occurs
when
both
registered
and
unregistered
transactions
are
selected.
Instruct
the
operator
to
click
Yes
or
No
based
on
the
preferred
action.
GTMJC0602W
The
selected
Topology
view
is
empty.
The
view
is
closed.
Explanation:
The
Topology
view
selected
does
not
contain
any
resources.
This
could
be
working
correctly,
or
the
view
could
be
populated
later
when
the
database
cache
has
been
updated.
System
Action:
The
console
processing
continues,
but
the
Topology
view
is
closed.
Operator
Response:
Select
another
type
of
view
for
the
resource
or
select
another
resource,
then
select
the
preferred
Topology
view.
If
the
database
cache
has
not
had
time
to
update,
try
the
selection
later.
Administrator
Response:
Look
at
the
Console
server
log
for
database
errors
in
building
the
Topology
view.
GTMJC0603W
The
operation
was
canceled
at
your
request.
The
information
in
the
view
could
be
incomplete
or
outdated.
Explanation:
One
or
more
operations
were
stopped
before
they
were
complete.
Affected
views
might
contain
outdated
or
incomplete
data
because
the
retrieval
was
stopped.
System
Action:
Console
processing
continues.
Operator
Response:
Close
the
view
if
you
do
not
need
the
information
in
it,
or
refresh
the
view
to
retrieve
valid
information.
Administrator
Response:
Close
the
view
if
you
do
not
need
the
information
in
it,
or
refresh
the
view
to
retrieve
valid
information.
GTMJC0604E
’res_name’
is
a
business
system
resource.
A
business
system
resource
can
only
be
copied
to
a
critical
resource
list
(CRL).
Explanation:
The
resource
you
want
to
drop
or
paste
in
the
business
system
view
is
a
business
system
resource.
A
business
system
resource
cannot
be
copied
to
another
place
in
the
Business
Systems
tree
except
to
a
critical
resource
list
(CRL).
If
you
need
another
copy
of
the
physical
resource
in
the
business
system
view,
copy
that
resource
from
the
All
Resources
view.
System
Action:
The
drop
or
paste
operation
cannot
proceed.
Administrator
Response:
Select
other
resources
to
drop
or
paste
into
the
business
system
view.
See
Understanding
Business
System
Shortcuts
for
additional
information.
GTMJC0605E
’res_name’
is
a
business
system
folder
shortcut.
A
business
system
folder
shortcut
can
only
be
copied
to
a
critical
resource
list
(CRL).
Explanation:
The
resource
that
you
want
to
drop
or
paste
in
the
business
system
view
is
a
business
system
folder
shortcut.
A
business
system
folder
shortcut
cannot
be
copied
to
another
place
in
the
Business
System
tree
except
to
a
critical
resource
list.
If
you
need
another
shortcut
of
the
business
system
folder
source
in
the
Business
System
tree,
copy
the
business
system
folder
source,
not
one
of
its
shortcuts.
System
Action:
The
drop
or
paste
operation
does
not
proceed.
Administrator
Response:
Select
other
resources
to
drop
or
paste
into
the
business
system
view.
See
Understanding
Business
System
Shortcuts
for
additional
information.
GTMJC0606E
’res_name’
is
in
a
critical
resource
list.
Items
that
are
in
a
critical
resource
list
can
only
be
placed
into
a
critical
resource
list.
Explanation:
The
items
that
you
want
to
drop
or
paste
in
the
business
system
view
were
created
in
a
critical
resource
list.
Items
created
in
a
critical
resource
list
cannot
be
placed
outside
a
critical
resource
list.
System
Action:
The
drop
or
paste
operation
does
not
proceed.
Administrator
Response:
Select
other
resources
to
drop
or
paste
into
the
business
system
view.
See
Chapter
16.
Console
Messages
-
GTMJC0502I
-
GTMJC9191I
203
Understanding
Business
System
Shortcuts
for
additional
information.
GTMJC0609E
One
or
more
items
you
want
to
add
to
an
executive
dashboard
list
were
created
in
a
critical
resource
list.
Items
that
were
created
in
a
critical
resource
list
are
not
valid
for
an
executive
dashboard
list.
Explanation:
The
item
that
you
want
to
add
to
an
executive
dashboard
list
was
created
in
a
critical
resource
list.
Because
these
items
cannot
be
configured
as
an
executive
dashboard
service,
this
is
not
a
valid
action.
System
Action:
The
request
to
add
resources
is
ignored.
Administrator
Response:
To
add
resources
to
an
executive
dashboard
list,
use
business
system
folders
or
business
system
folder
shortcuts
that
were
not
created
in
a
critical
resource
list.
See
Understanding
Business
System
Shortcuts
for
additional
information.
GTMJC0610I
The
business
system
folder
source
’res_name’
is
an
executive
dashboard
service.
Do
you
want
the
new
business
system
folder
shortcut
automatically
configured
as
an
executive
dashboard
service?
Explanation:
A
business
system
folder
shortcut
is
being
created
from
a
business
system
folder
source.
Click
Yes
if
you
want
the
business
system
folder
shortcut
configured
as
an
executive
dashboard
service.
Click
No
if
you
do
not
want
the
business
system
shortcut
configured
as
an
executive
dashboard
service.
Click
Yes
to
All
to
have
all
of
the
business
system
folder
shortcuts
configured
as
an
executive
dashboard
service
if
the
source
business
system
folder
has
a
configured
service.
Clicking
Yes
to
All
applies
to
items
you
have
not
already
responded
to.
Clicking
Cancel
cancels
this
entire
operation
including
the
items
that
you
have
already
responded
to.
System
Action:
Processing
continues
according
to
your
response.
Administrator
Response:
Respond
to
the
message.
If
you
click
Cancel,
no
items
are
copied
or
pasted.
Clicking
Yes
to
All
affects
the
business
system
folder
shortcut
you
are
currently
being
asked
about
and
any
business
system
folder
shortcuts
that
result
from
the
copy
or
paste
action.
Clicking
Yes
to
All
does
not
affect
items
you
have
already
been
asked
about.
See
Understanding
Business
System
Shortcuts
for
additional
information.
GTMJC0611I
This
window
shows
the
results
of
your
request
to
take
ownership
of,
or
transfer
or
close
events
or
notes.
It
also
lists
the
reasons
for
failure
if
events
or
notes
were
not
successfully
processed.
Because
your
request
could
have
included
more
than
one
event
or
note,
you
could
see
more
than
one
message.
Explanation:
Possible
messages
are:
System
Action:
None.
Administrator
Response:
None
required
GTMJC0620W
The
current
workspace
is
closing.
Information
in
one
or
more
views
might
not
be
saved.
Do
you
want
to
save
the
workspace?
Explanation:
The
current
workspace
is
closing.
To
save
any
customizations
to
the
workspace,
you
can
save
the
current
workspace
before
it
is
closed.
System
Action:
The
workspace
does
not
close
until
the
operator
clicks
Save
or
Do
Not
Save
in
response
to
the
confirmation
message.
Operator
Response:
Click
Save
to
save
the
current
workspace
and
close
the
views.
Click
Do
Not
Save
to
discard
changes
to
the
workspace
and
close
the
views.
Click
Cancel
to
return
to
the
workspace
without
saving
or
closing
any
views.
GTMJC0621W
The
console
is
closing.
Are
you
sure
you
want
to
close
the
console?
Explanation:
Before
the
console
closes,
you
are
given
an
opportunity
to
confirm
that
you
want
the
console
to
close.
System
Action:
The
console
does
not
close
until
the
operator
clicks
Yes
in
response
to
the
confirmation
message.
Operator
Response:
Click
Yes
to
close
the
console.
Click
No
to
cancel
the
request
and
to
return
to
the
console.
GTMJC0651E
Problem
ticket
creation
failed.
specific_error
Explanation:
You
attempted
to
create
a
problem
ticket,
but
it
did
not
complete
successfully.
System
Action:
A
problem
ticket
was
not
created
and
the
failure
was
reported.
Operator
Response:
Verify
that
you
have
supplied
information
and
made
selections
for
all
necessary
fields.
Make
any
corrections
indicated
in
the
text
of
the
204
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
message
and
attempt
to
create
the
problem
ticket
again.
If
the
problem
persists,
notify
the
administrator.
Administrator
Response:
Verify
that
the
operator
is
supplying
valid
information
for
all
fields
required
by
the
problem
management
system.
Verify
that
a
valid
user
name
and
password
for
the
problem
system
are
being
used.
Also,
verify
that
the
problem
system
is
running
and
that
a
connection
exists
between
the
console
and
the
problem
management
system.
For
additional
information,
see
the
IBM
Tivoli
Business
Systems
Manager
Problem
and
Change
Management
Integration
Guide.
GTMJC0653E
Problem
ticket
update
failed.
specific_error
Explanation:
You
attempted
to
update
or
close
a
problem
ticket,
but
this
action
was
unable
to
complete
successfully.
System
Action:
The
problem
ticket
was
not
updated
and
the
failure
was
reported.
Operator
Response:
Verify
that
you
have
supplied
information
and
made
selections
for
all
necessary
fields.
Make
any
corrections
indicated
in
the
text
of
the
message
and
attempt
to
update
or
close
the
problem
ticket
again.
If
the
problem
persists,
notify
the
administrator.
Administrator
Response:
Verify
that
the
operator
is
supplying
valid
information
for
all
fields
required
by
your
problem
management
system.
If
pertinent,
verify
that
a
valid
user
name
and
password
for
the
problem
management
system
are
being
used.
Also,
verify
that
the
problem
management
system
is
running
and
that
a
connection
exists
between
the
console
and
the
problem
management
system.
GTMJC0654E
Problem
ticket
query
failed.
specific_error
Explanation:
You
attempted
to
find
a
specific
problem
ticket
or
a
list
of
problem
tickets,
but
the
query
was
unable
to
locate
a
matching
ticket.
If
there
is
no
specific
error
text
in
the
message,
then
a
matching
ticket
could
not
be
found
in
the
problem
management
system.
If
there
was
message
text
indicating
a
specific
error,
then
the
query
could
not
be
performed.
System
Action:
No
problem
tickets
were
returned
from
the
query.
The
Find
Problem
Tickets
window
is
still
displayed.
Operator
Response:
If
the
message
indicates
no
specific
error,
then
refine
your
Find
search
criteria
and
try
again.
If
a
specific
error
was
mentioned
in
the
message,
make
any
possible
corrections
and
try
again.
Notify
the
administrator
if
the
problem
persists.
Administrator
Response:
If
there
is
no
specific
error
mentioned
in
the
message,
then
there
are
no
tickets
matching
the
Find
criteria.
Inform
the
operator
to
refine
the
Find
search
criteria.
If
there
seems
to
be
a
Find
error,
verify
that
the
problem
management
system
is
running
and
that
a
connection
exists
between
the
console
and
the
problem
management
system.
GTMJC0661E
Change
request
creation
failed.
specific_error
Explanation:
An
attempt
to
create
a
change
request
was
made,
but
it
was
unsuccessful.
System
Action:
A
change
request
was
not
created
and
the
failure
was
reported.
Operator
Response:
Verify
that
you
have
supplied
information
and
made
selections
for
all
necessary
fields.
Make
any
corrections
indicated
in
the
text
of
the
message
and
attempt
to
create
the
change
request
again.
If
the
problem
persists,
contact
the
administrator.
Administrator
Response:
Verify
that
the
operator
is
supplying
valid
information
for
all
fields
required
by
your
change
management
system.
If
pertinent,
verify
that
a
valid
user
name
and
password
for
the
change
management
system
are
being
used.
Also,
verify
that
the
change
management
system
is
running
and
that
a
connection
exists
between
the
console
and
the
change
management
system.
GTMJC0663E
Change
request
update
failed.
specific_error
Explanation:
An
attempt
to
update
a
change
request
was
made,
but
it
was
unsuccessful.
System
Action:
The
change
request
was
not
updated
and
the
failure
was
reported.
Operator
Response:
Verify
that
you
have
supplied
information
and
made
selections
for
all
necessary
fields.
Make
any
corrections
indicated
in
the
text
of
the
message
and
attempt
to
update
the
change
request.
If
the
problem
persists,
contact
the
system
administrator.
Administrator
Response:
Verify
that
the
operator
is
supplying
valid
information
for
all
fields
required
by
your
change
management
system.
If
pertinent,
verify
that
a
valid
user
name
and
password
for
the
change
management
system
are
being
used.
Also,
verify
that
the
change
management
system
is
running
and
that
a
connection
exists
between
the
console
and
the
change
management
system.
GTMJC0664E
Change
request
query
failed.
specific_error
Explanation:
You
attempted
to
find
a
specific
change
request
or
a
list
of
change
requests,
but
the
query
was
unable
to
locate
a
matching
request.
If
there
is
no
specific
error
text
in
the
message,
then
a
matching
request
could
not
be
found
in
the
change
management
system.
If
there
was
message
text
indicating
a
specific
error,
then
the
query
could
not
be
performed.
Chapter
16.
Console
Messages
-
GTMJC0502I
-
GTMJC9191I
205
System
Action:
No
change
requests
were
returned
from
the
query.
The
Find
Change
Requests
window
is
still
displayed.
Operator
Response:
If
the
message
indicates
no
specific
error,
then
refine
your
Find
search
and
try
again.
If
a
specific
error
was
mentioned
in
the
message,
make
any
possible
corrections
and
try
again.
If
the
problem
persists,
contact
the
administrator
.
Administrator
Response:
If
there
is
no
specific
error
mentioned
in
the
message,
there
are
no
requests
matching
the
Find
criteria.
Inform
the
operator
to
refine
the
Find
search
criteria.
If
there
seems
to
be
a
Find
error,
verify
that
the
change
management
system
is
running
and
that
a
connection
exists
between
the
console
and
the
change
management
system.
GTMJC0665E
The
closure
failed
for
problem
ticket
problem_ticket_id.
Verify
that
your
problem
management
system
is
running
and
connected.
Do
you
want
to
retry?
Explanation:
You
attempted
to
close
a
problem
ticket,
but
this
action
was
unable
to
complete
successfully.
System
Action:
The
problem
ticket
has
not
been
updated
and
the
failure
was
reported.
Operator
Response:
Make
any
corrections
that
might
have
caused
the
failure
and
click
Yes
to
retry,
otherwise
click
No
to
exit
without
attempting
to
close
the
problem
ticket
again.
If
you
retry
the
closure
and
the
problem
persists,
notify
the
administrator.
Administrator
Response:
Verify
that
the
problem
management
system
is
running
and
that
a
connection
exists
between
the
database
server
and
the
problem
management
system.
GTMJC0670W
Are
you
sure
you
want
a
blank
user
name
or
password?
Explanation:
The
OK
button
was
clicked
without
entering
a
user
name
or
a
password.
This
is
a
confirmation
message.
System
Action:
You
are
returned
to
the
Access
Info
window
if
you
click
No,
otherwise
the
user
name
and
password
are
used
even
if
they
were
blank.
Operator
Response:
Click
Yes
to
proceed
to
the
user
name
or
password
field,
which
contains
an
empty
value,
or
click
No
to
return
to
the
Access
Info
window
to
modify
the
values.
Administrator
Response:
This
message
was
displayed
as
a
confirmation
because
the
operator
entered
a
blank
user
name
or
password
on
the
Access
Info
window.
Inform
the
operator
if
blank
values
are
not
valid
for
the
user
name
and
password.
GTMJC0671I
The
server
returned
result_size
rows.
The
server
might
have
attempted
to
return
more
data
than
is
allowed
for
this
view.
The
limit
for
this
view
is
currently
view_limit.
Explanation:
The
data
you
are
viewing
could
be
incomplete.
For
certain
views,
administrators
can
configure
limits
on
the
amount
of
data
that
can
be
returned.
This
limit
was
either
reached
or
exceeded.
System
Action:
None
Operator
Response:
Contact
the
administrator
and
inquire
about
adjusting
the
limit
for
this
view.
For
information
about
resource
limits
in
HyperViews,
see
the
information
that
is
in
the
Notes
section
of
HyperView.
Administrator
Response:
This
message
is
displayed
because
the
view
limits
were
exceeded
by
this
request.
To
adjust
these
limits,
go
to
Console
->
Administrator
Preferences
->
Configuration.
GTMJC0672E
You
attempted
to
insert
num_resources
resources
into
the
business
system.
You
can
only
insert
up
to
resource_limit
resources
at
one
time.
Explanation:
You
are
pasting
or
dropping
more
resources
into
a
business
system
than
is
allowed
by
the
console
server.
System
Action:
The
drop
or
paste
operation
is
canceled.
Operator
Response:
Reduce
the
number
of
resources
to
be
dropped
or
pasted
to
the
specified
limit.
GTMJC0673W
You
customized
the
Display
Properties
of
this
view,
and
are
now
specifying
the
Always
use
the
display
properties
in
my
preferences
option
in
your
Console
Preferences.
Customizations
to
this
specific
view
will
not
be
displayed.
The
view
will
be
displayed
using
the
preferences
specified
in
Console
Preferences.
Explanation:
You
previously
customized
the
Display
Properties
of
this
view.
However,
now
the
Always
use
the
display
properties
in
my
preferences
option
is
selected
in
the
Console
Preferences.
This
overrides
the
view
customizations
and
the
view
will
be
displayed
with
the
Console
Preferences
option
instead.
System
Action:
None
Operator
Response:
If
you
want
to
use
the
customizations
of
the
view,
clear
the
Always
use
the
display
properties
in
my
preferences
checkbox
in
the
Console
Preferences.
206
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
GTMJC0677E
Unable
to
obtain
a
list
of
problem
system
or
change
system
user
IDs.
The
action
cannot
continue.
Explanation:
You
attempted
to
perform
a
problem
ticket
or
change
request
action,
but
the
action
cannot
continue
because
a
list
of
valid
user
IDs
for
the
system
could
not
be
obtained.
System
Action:
The
attempted
action
is
stopped
and
you
are
returned
to
your
previous
window.
Operator
Response:
Attempt
the
action
again.
If
the
problem
persists,
notify
the
administrator.
Administrator
Response:
Verify
that
the
Request
Processor
is
returning
a
valid
list
of
user
IDs
to
the
console.
The
list
returned
by
the
Request
Processor
in
response
to
a
REQUEST_GET_UIDS
query
must
contain
at
least
one
user
name
and
password
pair.
It
might
also
be
necessary
to
verify
that
the
problem
or
change
system
system
is
running
and
that
a
connection
exists
between
the
console
and
the
problem
or
change
management
system
as
appropriate
for
your
installation.
GTMJC0678E
The
action
cannot
continue
because
an
error
has
occurred.
specific_error
Return
code
=return_code.
Explanation:
You
attempted
to
perform
a
problem
ticket
or
change
request
action,
but
an
error
occurred
which
has
prevented
it
from
continuing.
System
Action:
The
attempted
action
is
stopped
and
you
are
returned
to
your
previous
window.
Operator
Response:
Resolve
any
problems
indicated
in
the
message
and
attempt
the
action
again.
If
the
problem
persists,
notify
the
administrator.
Administrator
Response:
Verify
that
the
Request
Processor
is
obtaining
and
returning
valid
problem
or
change
data
to
the
console.
Also,
verify
that
the
problem
or
change
system
is
running
and
that
a
connection
exists
between
the
console
and
the
problem
or
change
management
system
as
appropriate
for
your
installation.
GTMJC0679E
An
error
occurred
initializing
the
window.
specific_error
Return
code
=return_code.
Explanation:
You
attempted
to
open
a
problem
ticket
or
change
request
window,
but
an
error
occurred
during
initialization
that
prevented
it
from
opening
successfully.
System
Action:
The
display
of
the
window
is
stopped
and
you
are
returned
to
your
previous
location
in
the
console.
Operator
Response:
Make
any
required
corrections
indicated
in
the
message
and
attempt
to
open
the
window
again.
If
the
problem
persists,
notify
the
administrator.
Administrator
Response:
Verify
that
the
Request
Processor
is
obtaining
and
returning
valid
problem
or
change
data
to
the
console.
Also,
verify
that
the
problem
or
change
system
is
running
and
that
a
connection
exists
between
the
console
and
the
problem
or
change
management
system
as
appropriate
for
your
installation.
For
additional
information,
see
the
IBM
Tivoli
Business
Systems
Manager
Problem
and
Change
Management
Integration
Guide.
GTMJC0680E
The
access
information
that
you
entered
was
not
valid.
You
must
enter
a
user
name
and
password
that
is
authorized
to
access
NetView.
Explanation:
You
entered
access
information,
but
it
does
not
have
the
required
level
of
authorization
to
access
the
NetView
product.
System
Action:
The
create
or
update
action
does
not
proceed
because
the
access
information
was
not
valid.
The
prompt
window
for
NetView
access
information
is
displayed
again.
Operator
Response:
Enter
a
valid
user
name
and
password
and
attempt
the
operation
again.
If
the
problem
persists,
have
the
administrator
verify
that
your
user
name
and
password
have
the
necessary
level
of
authorization
to
access
the
NetView
product.
Administrator
Response:
Verify
that
the
operator
is
entering
a
valid
user
name
and
password
to
access
the
NetView
product.
GTMJC0681E
There
is
an
authorization
problem
with
the
access
information
that
you
entered.
You
must
enter
a
user
ID
and
password
that
is
authorized
to
perform
the
requested
task
in
NetView.
The
return
code
is:
specific_error
Explanation:
You
entered
a
valid
NetView
user
ID
and
password,
but
the
task
is
unable
to
complete
with
this
access
information.
The
access
information
might
not
have
the
necessary
level
of
authorization.
System
Action:
The
create
or
update
action
does
not
proceed
because
there
is
a
problem
with
the
access
information.
The
prompt
window
for
NetView
access
information
is
displayed
again.
Operator
Response:
Enter
a
different
valid
user
ID
and
password
and
then
attempt
the
operation
again.
If
the
problem
persists,
have
the
administrator
verify
that
your
user
ID
and
password
have
the
necessary
level
of
authorization.
Administrator
Response:
Verify
that
the
operator
is
entering
a
valid
user
ID
and
password
with
the
Chapter
16.
Console
Messages
-
GTMJC0502I
-
GTMJC9191I
207
necessary
level
of
authorization.
GTMJC0682E
Your
access
information
cannot
be
validated
because
of
a
problem
with
the
NetView
connection.
Verify
that
the
NetView
connection
is
active
and
retry
the
operation.
Explanation:
You
entered
access
information,
but
it
cannot
be
validated
due
to
a
connection
problem.
System
Action:
The
create
or
update
action
does
not
proceed
because
the
access
information
cannot
be
validated.
The
prompt
window
for
NetView
access
information
is
displayed
again.
Operator
Response:
Contact
the
administrator
to
establish
that
the
NetView
connection
is
working.
Enter
your
access
information
again
and
attempt
the
operation
again.
If
the
problem
persists,
contact
the
administrator.
Administrator
Response:
Verify
that
the
connection
to
NetView
is
active.
GTMJC0683E
There
was
a
failure
validating
your
access
information.
The
return
code
is:
specific_error
Explanation:
You
entered
access
information
for
the
NetView
product,
but
it
could
not
be
validated
due
to
a
system
or
connection
problem.
System
Action:
The
create
or
update
action
does
not
proceed
because
the
access
information
cannot
be
validated.
The
prompt
window
for
NetView
access
information
is
displayed
again.
Operator
Response:
Enter
your
access
information
and
attempt
the
operation
again.
If
the
problem
persists,
notify
the
administrator
and
provide
the
specific
return
code
if
available.
Administrator
Response:
Verify
that
a
live
connection
to
the
NetView
product
still
exists
and
is
working
correctly.
GTMJC0684E
The
access
information
that
you
entered
was
not
valid.
You
must
enter
a
user
name
and
password
that
is
authorized
to
access
the
requested
system.
Explanation:
You
entered
access
information,
but
it
does
not
have
the
required
level
of
authorization
to
access
the
problem
or
change
system.
System
Action:
The
create
or
update
action
does
not
proceed
because
the
access
information
was
not
valid.
The
prompt
window
for
the
access
information
is
displayed
again.
Operator
Response:
Enter
a
valid
user
name
and
password
then
attempt
the
operation
again,
or
click
Cancel
to
return
to
the
dialog
without
continuing
with
the
attempted
action.
If
the
problem
persists,
have
the
administrator
verify
that
your
user
name
and
password
have
the
necessary
level
of
authorization
to
access
the
requested
problem
or
change
system.
Administrator
Response:
Verify
that
the
user
is
entering
a
valid
user
name
and
password
to
access
the
requested
problem
or
change
system.
GTMJC0685W
note_count
notes
have
events
that
were
not
among
the
selected
events.
You
can
choose
whether
or
not
to
process
these
notes.
Clicking
Cancel
stops
processing
of
the
notes.
Explanation:
The
notes
corresponding
with
the
events
you
selected
have
additional
events
that
were
not
selected.
Because
the
operation
takes
place
at
the
note
level,
the
events
that
were
not
selected
will
be
affected
by
the
operation.
System
Action:
You
are
prompted
with
choices
on
how
to
proceed.
Operator
Response:
You
can
choose
to
process
all
of
these
notes,
not
process
the
notes
that
have
additional
events,
or
not
process
any
of
the
notes.
GTMJC0686I
Field
customization
is
now
enabled.
You
might
have
to
open
the
windows
again
before
you
can
see
the
customizable
fields.
Fields
that
can
be
customized
are
highlighted
with
a
magenta
border.
You
can
customize
a
field
by
clicking
it
with
the
left
mouse
button
while
pressing
the
Alt
key.
Press
Ctl-Shft-F9
to
end
customization.
Explanation:
You
can
customize
any
of
the
customizable
fields.
The
console
continues
to
function
during
customization.
You
can
open
additional
views
and
windows
and
interact
as
usual.
Changes
take
affect
immediately,
as
they
are
made,
and
affect
all
users
of
the
server
to
which
you
are
connected.
System
Action:
The
console
is
updated
to
highlight
customizable
fields.
Also,
any
fields
that
were
marked
deleted
by
previous
customization
sessions
are
displayed
so
they
can
be
further
customized.
Administrator
Response:
Customize
highlighted
fields
according
to
your
requirements.
GTMJC0687I
Field
customization
is
now
disabled;
you
might
have
to
open
the
windows
again
before
you
can
see
the
typical
presentation.
Explanation:
You
ended
your
customization.
System
Action:
The
client
is
updated
to
show
the
208
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
typical
presentation,
including
any
customization
you
just
performed.
Administrator
Response:
Verify
that
your
customization
is
acceptable,
and
enable
customization
again
if
you
must
further
refine
your
changes.
GTMJC0690W
You
requested
to
stop
displaying
the
dialog_title
window.
Click
’Close
Window’
to
confirm
your
selection
and
close
the
dialog_title
window.
Explanation:
You
clicked
Stop
while
the
specified
window
was
initializing.
You
are
asked
to
confirm
that
you
want
to
stop
displaying
the
specified
window.
System
Action:
The
window
initialization
continues
unless
you
confirm
the
stop
action
by
clicking
Close
Window
on
this
message.
If
you
confirm
the
stop,
then
the
display
of
the
window
will
be
canceled.
Operator
Response:
Click
Close
Window
on
this
message
to
stop
the
display
of
the
window.
Click
Cancel
to
continue
displaying
the
window.
Administrator
Response:
The
user
selected
to
stop
the
display
of
a
window
while
it
was
still
initializing.
The
user
is
being
prompted
to
confirm
the
action.
Instruct
the
user
to
click
Cancel
to
continue
displaying
the
window
or
to
click
Close
Window
to
dismiss
the
window.
GTMJC0701W
The
workspace
was
saved
by
a
previous
version
of
IBM
Tivoli
Business
Systems
Manager
and
needs
to
be
migrated.
The
console
attempts
to
restore
the
workspace.
However,
some
attributes
of
the
workspace
or
its
views
could
revert
to
the
default
settings.
Explanation:
The
workspace
contains
information
that
can
be
accessed
by
this
version
of
the
console
only
after
the
workspace
has
been
migrated.
System
Action:
The
console
loads
as
much
of
the
workspace
as
it
can.
Workspace
attributes
that
cannot
be
restored
typically
revert
to
their
default
settings.
Operator
Response:
None
required.
You
might
want
to
ask
your
Administrator
to
migrate
the
workspace
so
that
it
can
be
fully
restored
by
this
version
of
the
console.
GTMJC0703W
The
workspace
migration
was
incomplete.
Workspace
or
view
attributes
which
could
not
be
restored
will
revert
to
their
defaults.
See
the
log
for
details.
Explanation:
The
console
was
unable
to
restore
information
about
the
workspace.
System
Action:
The
workspace
is
restored,
as
much
as
possible,
and
presented.
Administrator
Response:
The
log
file
should
document
which
attributes
of
the
workspace
could
not
be
fully
restored.
GTMJC0704E
The
item
you
are
attempting
to
paste
or
drop
is
not
valid
for
this
view.
Explanation:
An
item
is
being
pasted
or
dropped
into
a
view.
It
is
not
a
valid
item
for
this
view.
Only
resources
can
be
pasted
or
dropped
into
a
view.
Furthermore,
resources
cannot
be
copied
or
pasted
across
different
instances
of
the
console.
System
Action:
The
paste
or
drop
operation
is
ended.
Operator
Response:
From
the
same
console
as
the
target
view,
copy
the
console
resources
to
the
clipboard
or
drag
resources.
Then
perform
the
paste
or
drop
operation
again.
GTMJC0705E
A
tree
expansion
string
that
is
not
valid,
invalid_string
,
was
encountered.
The
expansion
has
been
ignored.
Explanation:
The
program
encountered
a
saved
tree
state
string
with
a
format
that
is
not
valid.
This
can
occur
when
a
tree
expansion
is
restored
from
a
damaged
workspace.
System
Action:
The
expansion
string
that
is
not
valid
is
ignored
and
processing
continues.
The
tree
might
not
be
fully
expanded.
Operator
Response:
Expand
the
tree
manually
to
the
state
you
want
and
then
save
the
workspace.
Administrator
Response:
Expand
the
tree
manually
to
the
state
you
want
and
then
save
the
workspace.
GTMJC0706W
You
requested
to
save
a
workspace
containing
the
view
view_title
with
expansion_count
tree
branches
expanded.
When
you
restore
this
workspace,
it
could
take
a
long
time
for
the
system
to
restore
the
view
to
its
current
state.
Do
you
want
to
save
the
expanded
state,
save
the
collapsed
state,
or
not
save
changes
to
the
expansion
state?
Explanation:
The
system
saves
a
list
of
expanded
branches
in
a
view
when
you
save
a
view
in
a
workspace.
When
the
system
restores
such
a
workspace,
it
must
query
the
database
to
retrieve
the
data
for
each
expanded
branch.
In
some
situations
this
retrieval
can
be
time
consuming
and
affect
overall
system
performance.
System
Action:
The
system
prompts
the
user
for
the
action
to
take.
If
the
user
clicks
Save
Expanded,
the
system
saves
the
workspace
including
the
expanded
tree
state.
If
the
user
clicks
Save
Collapsed,
the
system
Chapter
16.
Console
Messages
-
GTMJC0502I
-
GTMJC9191I
209
saves
the
workspace
but
does
not
save
the
tree
expanded
state.
If
the
user
clicks
Do
Not
Save,
the
system
does
not
modify
the
expanded
branches
information
for
the
view.
Operator
Response:
Click
Save
Expanded
to
save
the
workspace
with
the
branches
expanded.
Click
Save
Collapsed
to
save
the
workspace
with
the
branches
collapsed.
Click
Do
Not
Save
to
leave
the
expanded
branches
information
in
the
workspace
unchanged.
GTMJC0707W
You
requested
to
open
a
workspace
containing
a
view
with
expansion_count
tree
branches
expanded.
It
could
take
a
long
time
for
the
system
to
restore
the
view
to
its
expanded
state.
Do
you
want
to
open
the
view
in
its
expanded
state?
Explanation:
For
the
system
to
open
the
view
in
its
expanded
state,
it
must
query
the
database
to
retrieve
the
data
for
each
expanded
branch.
In
some
situations
this
retrieval
can
be
time
consuming
and
affect
overall
system
performance.
If
you
do
not
need
all
of
the
tree
branches
to
be
fully
expanded,
click
No
to
get
faster
response
time.
System
Action:
The
system
prompts
the
user
for
the
action
to
take.
If
the
user
clicks
Yes,
the
system
performs
the
full
tree
expansion.
If
the
user
clicks
No,
the
system
opens
the
tree
with
only
the
top
level
branch
expanded.
Operator
Response:
Click
Yes
to
open
the
view
with
the
tree
branches
in
the
expanded
state.
Click
No
to
open
the
view
with
only
the
top
level
expanded.
GTMJC0710E
Response
value
must
be
greater
than
zero
and
cannot
exceed
the
interval
value.
Explanation:
You
modified
either
the
heartbeat
interval
or
the
heartbeat
response
and
as
a
result
the
response
value
is
no
longer
valid.
The
response
value
cannot
be
zero
when
an
interval
has
been
specified
and
the
response
value
cannot
be
greater
than
the
value
specified
for
the
interval.
System
Action:
Modifications
are
not
made
until
the
values
are
corrected.
Operator
Response:
Correct
the
response
or
interval
values.
GTMJC0721E
Mismatched
brackets
are
in
the
text
of
the
field:
field_name.
Explanation:
The
text
in
the
specified
entry
field
contains
grouping
brackets
that
are
not
matched
as
a
pair.
System
Action:
The
Administrator
Preferences
are
not
saved.
Operator
Response:
Correct
the
mismatched
bracket
in
the
pair
so
that
the
brackets
are
the
same:
[
].
GTMJC0722E
Nested
brackets
are
in
the
text
of
the
field:
field_name.
Explanation:
The
text
in
the
specified
entry
field
contains
brackets
within
another
pair
of
brackets.
Nested
brackets
are
not
allowed.
System
Action:
The
Administrator
Preferences
are
not
saved.
Operator
Response:
Edit
the
text
to
remove
the
nested
brackets.
GTMJC0723E
An
ownership
note
cannot
be
created
on
the
selected
resource
because
there
are
no
unowned
events
for
that
resource.
Explanation:
The
selected
resource
does
not
have
any
events
or
child
events
that
can
be
owned.
System
Action:
An
ownership
note
is
not
created.
Operator
Response:
Verify
that
the
selected
resource
does
not
have
an
ownership
note.
Administrator
Response:
Verify
that
the
option
to
Clear
Alerts
from
Resources
is
not
selected.
If
Clear
Alerts
from
Resources
is
not
selected,
the
resource
could
have
a
non-green
alert
state
even
though
the
resource
has
no
unowned
events.
GTMJC0724E
The
note
was
not
updated.
The
note
is
either
closed,
or
you
are
no
longer
authorized
to
update
the
note.
Explanation:
The
note
could
not
be
updated
because
it
is
either
closed
or
its
ownership
has
changed.
System
Action:
The
note
properties
were
not
updated.
Operator
Response:
Verify
the
state
and
ownership
of
the
note.
Administrator
Response:
Verify
the
operator’s
authority
to
update
the
note.
GTMJC0730E
Search
criteria
is
not
valid.
Search
strings
that
contain
only
wildcards
are
only
valid
when
one
or
more
resource
types
are
individually
selected.
Explanation:
When
the
Any
resource
type
option
is
selected,
the
search
string
must
contain
characters
that
are
not
wildcards.
System
Action:
The
search
does
not
take
place.
Operator
Response:
Type
a
search
string
that
contains
non-wildcard
characters
in
the
search
field,
or
select
specific
resource
types.
210
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
Administrator
Response:
This
message
occurs
when
the
Any
resource
type
option
is
selected
and
only
wildcards
are
entered
in
the
search
field.
Instruct
the
operator
to
either
select
specific
resource
types
or
type
a
search
string
that
contains
non-wildcard
characters
in
the
search
field.
GTMJC0731E
The
value
for
APPLID
is
not
valid.
APPLID
is
required.
Either
no
value
is
specified
or
the
value
that
is
specified
does
not
have
the
correct
syntax.
Explanation:
1.
The
APPLID
value
is
required.
2.
The
APPLID
must
be
1-8
characters
in
length.
3.
The
first
character
must
be
one
of
these
characters:
ABCDEFGHIJKLMNOPQRSTUVWXYZ@#$
4.
The
second
through
eighth
characters
must
be
from
this
character
set:
ABCDEFGHIJKLMNOPQRSTUVWXYZ@#$0123456789
System
Action:
Console
processing
continues,
but
the
create
action
does
not
occur.
Operator
Response:
Correct
the
APPLID.
Administrator
Response:
Instruct
the
operator
to
correct
the
APPLID.
GTMJC0732E
The
value
for
Profile
Suffix
is
not
valid.
The
value
that
is
specified
does
not
have
the
correct
syntax.
Explanation:
1.
The
Profile
Suffix
is
optional.
2.
The
Profile
Suffix
must
be
one
or
two
characters
in
length.
3.
The
characters
must
be
from
this
character
set:
ABCDEFGHIJKLMNOPQRSTUVWXYZ@#$0123456789
System
Action:
Console
processing
continues,
but
the
create
action
does
not
occur.
Operator
Response:
Correct
the
Profile
Suffix
or
do
not
specify
a
Profile
Suffix.
Administrator
Response:
Instruct
the
operator
to
correct
the
Profile
Suffix.
GTMJC0733E
The
value
for
First
Screen
is
not
valid.
The
value
that
is
specified
does
not
have
the
correct
syntax.
Explanation:
1.
The
First
Screen
is
optional.
2.
The
First
Screen
must
be
1-8
characters
in
length.
3.
The
first
character
must
be
one
of
these
characters:
ABCDEFGHIJKLMNOPQRSTUVWXYZ@#$
4.
The
second
through
eighth
characters
must
be
from
this
character
set:
ABCDEFGHIJKLMNOPQRSTUVWXYZ@#$0123456789
System
Action:
Console
processing
continues.
The
create
action
does
not
occur.
Operator
Response:
Correct
the
First
Screen
or
do
not
specify
a
First
Screen.
Administrator
Response:
Instruct
the
operator
to
correct
the
First
Screen.
GTMJC0734W
Do
you
want
to
save
the
changes
you
made
to
the
login
values?
Explanation:
The
changed
values
have
not
been
saved.
You
are
asked
if
you
want
to
save
the
changes.
System
Action:
Console
processing
continues.
All
changes
are
saved
if
you
click
Save.
If
you
click
Do
not
save,
changes
are
not
saved.
Operator
Response:
Click
Save
in
the
message
box
if
you
want
to
save
the
changes
you
made.
If
you
do
not
want
to
save
your
changes,
click
Do
not
save.
Administrator
Response:
Instruct
the
operator
to
click
either
Save
or
Do
not
save
in
the
message
box,
depending
on
whether
or
not
they
want
to
save
the
changes.
GTMJC0735E
A
database
update
failed.
Contact
Customer
Support.
Explanation:
A
database
update
for
the
Performance
Monitor
Login
Properties
dialog
failed.
System
Action:
The
requested
action
did
not
succeed.
Operator
Response:
Recreate
the
problem
with
all
tracing
enabled.
Obtain
the
console
and
server
logs.
Administrator
Response:
View
the
logs
and
interpret
the
information.
If
possible,
verify
that
the
database
contains
the
correct
information.
GTMJC0736E
The
value
specified
for
APPLID
is
not
valid.
The
specified
value
does
not
have
the
correct
syntax.
Explanation:
1.
The
APPLID
must
be
one
to
eight
characters
in
length.
2.
The
first
character
must
be
one
of
these
characters:
ABCDEFGHIJKLMNOPQRSTUVWXYZ@#$
3.
The
second
through
eighth
characters
must
be
from
this
character
set:
ABCDEFGHIJKLMNOPQRSTUVWXYZ@#$0123456789
System
Action:
Console
processing
continues.
The
create
action
does
not
occur.
Operator
Response:
Correct
the
APPLID.
Administrator
Response:
Instruct
the
operator
to
correct
the
APPLID.
Chapter
16.
Console
Messages
-
GTMJC0502I
-
GTMJC9191I
211
GTMJC0737W
Deleting
service
removes
the
service
from
the
view
of
parent.
Do
you
want
to
delete
this
service
resource?
Explanation:
You
are
deleting
a
service
from
an
executive
dashboard
list.
System
Action:
The
service
will
no
longer
appear
in
the
executive
dashboard
list.
Administrator
Response:
Confirm
deletion
of
this
service.
GTMJC0738W
Deleting
executive
dashboard
user
deletes
the
executive
dashboard
user
from
the
executive
dashboard
lists.
Do
you
want
to
remove
this
executive
dashboard
user?
Explanation:
You
are
deleting
an
executive
dashboard
user
who
is
no
longer
defined
in
the
user
registry,
from
the
executive
dashboard
lists.
System
Action:
The
executive
dashboard
user
will
not
appear
in
the
executive
dashboard
lists
until
the
user
is
redefined
in
the
user
registry.
If
the
executive
dashboard
user
is
restored
to
the
user
registry,
services
are
not
restored
and
will
have
to
be
added.
Administrator
Response:
Confirm
deletion
of
this
executive
dashboard
user.
GTMJC0739W
Deleting
unexpected,
which
is
a
resource
of
type
type,
is
not
supported.
Explanation:
You
are
attempting
to
delete
a
resource,
but
delete
is
not
supported
for
this
resource
type.
System
Action:
Processing
continues
but
the
resource
is
not
deleted.
Administrator
Response:
Contact
Customer
Support
and
provide
the
console
log
and,
if
possible,
a
screen
capture
of
this
message.
GTMJC0740E
The
Service
Identifier
specified
for
the
service,
serviceID1,
is
a
duplicate
Service
Identifier.
The
following
Service
Identifier
is
proposed,
Service
Identifier2.
Explanation:
You
are
attempting
to
define
a
service,
but
the
Service
Identifier
you
specified
is
identical
to
the
Service
Identifier
of
a
service
that
is
associated
with
a
different
resource.
You
could
accept
the
proposed
Service
Identifier
or
replace
the
proposed
Service
Identifier
with
another
value
of
your
choice.
System
Action:
Processing
continues
but
the
service
was
not
created.
Administrator
Response:
Specify
a
different
Service
Identifier.
GTMJC0741E
The
definition
of
the
service
failed.
Explanation:
You
are
attempting
to
create
a
service
but
a
call
to
the
IBM
Tivoli
Business
Systems
Manager
database
failed.
System
Action:
Processing
continues,
but
the
service
was
not
created.
Administrator
Response:
Contact
Customer
Support
and
provide
the
console
log
and
the
server
log.
GTMJC0742E
An
error
occurred
and
the
service
resource
was
not
created.
Explanation:
You
are
attempting
to
create
a
service
resource
but
a
call
to
the
IBM
Tivoli
Business
Systems
Manager
database
failed
to
create
the
service
resource.
System
Action:
The
service
resource
was
not
created.
Administrator
Response:
Contact
Customer
Support
and
provide
the
console
log
and
the
server
log.
GTMJC0743E
The
Service
Resource
Identifier
specified
for
the
service
resource,
serviceID1,
is
a
duplicate
Service
Resource
Identifier.
The
following
Service
Resource
Identifier
is
proposed,
Service
Identifier2.
Explanation:
You
are
attempting
to
define
a
service
resource,
but
the
Service
Resource
Identifier
you
specified
is
identical
to
the
Service
Resource
Identifier
of
a
service
resource
that
is
associated
with
a
different
resource.
You
could
accept
the
proposed
Service
Resource
Identifier
or
replace
the
proposed
Service
Resource
Identifier
with
another
value
of
your
choice.
System
Action:
Processing
continues
but
the
service
resource
was
not
created.
Administrator
Response:
Specify
a
different
Service
Resource
Identifier.
GTMJC0744W
You
requested
to
inactivate
a
service.
If
this
service
is
inactivated,
executives
will
no
longer
be
able
to
see
or
access
it
from
their
executive
dashboards.
The
following
executives
will
be
affected:
ListOfExecutives
Click
Yes
to
inactivate
the
service.
Click
No
if
you
do
not
want
to
inactivate
the
service.
Explanation:
By
clearing
the
checkbox
you
are
inactivating
this
service.
The
service
will
be
removed
from
all
executive
dashboard
lists
that
it
is
currently
in.
If
you
activate
this
service
in
the
future
by
selecting
the
checkbox,
you
must
add
the
service
to
any
executive
dashboard
lists
where
you
want
it
to
appear.
System
Action:
If
inactivated,
the
service
is
removed
212
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
from
all
executive
dashboard
lists
where
it
currently
appears.
GTMJC0745E
You
are
opening
or
refreshing
the
executive
dashboard
lists
view.
The
IBM
Tivoli
Business
Systems
Manager
console
is
unable
to
reach
the
IBM
WebSphere
user
registry.
The
list
of
executive
dashboard
users
cannot
be
refreshed.
Explanation:
Calls
to
the
IBM
WebSphere
user
registry,
to
obtain
a
current
list
of
executive
dashboard
users,
do
not
complete.
No
more
attempts
to
contact
the
IBM
WebSphere
user
registry
will
be
made.
System
Action:
This
message
appears
each
time
the
executive
dashboard
list
view
is
opened
or
refreshed
unless
one
of
the
outstanding
requests
completes.
Other
console
functions
should
be
available.
Processing
continues.
Administrator
Response:
Stop
and
start
the
console
server,
and
then
restart
the
console.
If
the
problem
occurs
again,
contact
Customer
Support
GTMJC0750W
You
cannot
cancel
the
selected
task
because
it
is
no
longer
in
a
Pending
status.
Explanation:
Tasks
that
have
been
sent
to
the
problem/change
system
or
that
have
completed
cannot
be
canceled.
System
Action:
The
task
is
not
canceled
and
it
continues
to
run.
Typical
success
or
failure
processing
takes
place
when
the
task
completes.
Operator
Response:
No
action
is
required,
but
if
the
action
completes
successfully,
you
might
want
to
take
steps
to
undo
the
task
that
was
performed.
Administrator
Response:
This
message
occurs
when
a
user
clicks
Cancel
to
stop
a
running
or
completed
task.
It
is
typical
operation
to
notify
the
user
of
these
limitations.
Notify
the
user
that
tasks
that
are
beyond
the
Pending
status
cannot
be
canceled.
If
necessary,
assist
the
user
with
undoing
the
task
(for
example,
assist
the
user
with
closing
a
ticket
that
was
created,
or
changing
a
ticket
property
back
to
its
previous
value).
GTMJC0751W
The
Create
Problem
Ticket
task
cannot
be
restarted.
You
can
only
restart
creation
tasks
that
were
canceled
or
that
failed
to
complete
successfully.
Explanation:
You
attempted
to
restart
a
task
that
cannot
be
restarted.
Create
tasks
that
are
in
a
Pending,
Running,
or
Completed
state
cannot
be
restarted.
System
Action:
The
selected
task
is
not
restarted
or
altered.
Operator
Response:
To
create
a
new
problem
ticket,
you
must
use
one
of
the
standard
methods
in
the
console,
such
as
selecting
Problem
Ticket
->
Create
from
the
context
menu
of
a
resource.
Administrator
Response:
This
message
occurs
when
a
user
clicks
Restart
for
a
Create
Problem
Ticket
task
that
is
in
a
state
for
which
Restart
is
not
available.
It
is
typical
operation
to
notify
the
user
of
these
limitations.
If
necessary,
explain
other
methods
of
creating
a
problem
ticket
from
the
console.
GTMJC0752W
The
Update
Problem
Ticket
task
cannot
be
restarted.
Explanation:
The
Restart
command
is
not
available
for
Update
tasks
because
ticket
properties
could
have
been
updated
by
someone
else
since
this
task
was
originally
submitted.
Restarting
the
task
could
replace
or
overwrite
updates
made
by
the
other
person.
System
Action:
The
selected
task
is
not
restarted
or
altered.
Operator
Response:
To
update
a
problem
ticket,
use
the
New
command
to
display
the
current
ticket
properties
in
a
Problem
Ticket
Properties
dialog
so
that
a
new
update
can
be
attempted.
Administrator
Response:
This
message
occurs
when
a
user
clicks
Restart
for
an
Update
Problem
Ticket
task.
It
is
typical
operation
to
notify
the
user
of
these
limitations.
If
necessary,
explain
other
methods
of
updating
a
problem
ticket.
GTMJC0753W
The
Create
Change
Request
task
cannot
be
restarted.
You
can
only
restart
creation
tasks
that
were
canceled
or
that
failed
to
complete
successfully.
Explanation:
You
attempted
to
restart
a
task
that
cannot
be
restarted.
Create
tasks
that
are
in
a
Pending,
Running,
or
Completed
state
cannot
be
restarted.
System
Action:
The
selected
task
is
not
restarted
or
altered.
Operator
Response:
To
create
a
new
change
request,
you
must
use
one
of
the
standard
methods
in
the
console,
such
as
selecting
Change
Request
->
Create
from
the
context
menu
of
a
resource.
Administrator
Response:
This
message
occurs
when
a
user
clicks
Restart
for
a
Create
Change
Request
task
that
is
in
a
state
for
which
restart
is
not
available.
It
is
typical
operation
to
notify
the
user
of
these
limitations.
If
necessary,
explain
other
methods
of
creating
a
change
request
to
the
user.
GTMJC0754W
The
Update
Change
Request
task
cannot
be
restarted.
Explanation:
The
Restart
command
is
not
available
for
Update
tasks
because
ticket
properties
could
have
been
updated
by
someone
else
since
this
task
was
originally
Chapter
16.
Console
Messages
-
GTMJC0502I
-
GTMJC9191I
213
submitted.
Restarting
the
task
could
replace
or
overwrite
updates
made
by
the
other
person.
System
Action:
The
selected
task
is
not
restarted
or
altered.
Operator
Response:
To
update
a
change
request,
use
the
New
command
to
display
the
current
ticket
properties
in
a
Change
Request
Properties
dialog
and
then
try
to
do
the
update.
Administrator
Response:
This
message
occurs
when
a
user
clicks
Restart
for
an
Update
Change
Request
task.
It
is
typical
operation
to
notify
the
user
of
these
limitations.
If
necessary,
explain
other
methods
of
updating
a
change
request
to
the
user.
GTMJC0760E
The
following
notes
could
not
be
closed.
Explanation:
The
selected
note(s)
could
not
be
successfully
closed.
A
reason
that
indicates
why
the
problem
occurred
is
listed
for
each
note.
System
Action:
The
requested
Close
Note
action
did
not
succeed.
Operator
Response:
Review
the
reasons
listed
in
the
table
and
correct
the
problems.
Administrator
Response:
View
and
assess
each
note
and
verify
that
the
reason
listed
for
the
failure
does
not
exist.
If
no
explanation
can
be
found,
view
the
log
files
to
determine
the
cause
of
the
error.
GTMJC0761E
Enter
a
resolution
when
closing
a
note.
Explanation:
The
note
cannot
be
closed
without
a
resolution.
System
Action:
The
note
was
not
updated.
Operator
Response:
Enter
a
resolution
in
the
Resolution
field.
GTMJC0762E
The
specified
browser
cannot
be
found.
Ensure
that
the
browser
name
you
entered
is
a
fully
qualified
executable
file
name.
Explanation:
The
file
name
that
was
specified
for
the
browser
could
not
be
found.
System
Action:
The
browser
is
not
launched.
Operator
Response:
Enter
a
fully
qualified
Web
browser
executable
file
name
in
the
Web
Browser
fully
qualified
executable
file
name
field.
GTMJC0770W
Resource
Type
thresholds
changes
could
affect
all
resources
of
the
given
Resource
Type
and
might
result
in
significant
system
impact.
Explanation:
You
selected
to
change
Resource
Type
thresholds.
Changes
made
to
Resource
Type
thresholds
could
affect
all
resources
of
the
given
Resource
Type.
System
Action:
The
Resource
Type
threshold
fields
on
the
Resource
Properties
dialog
are
enabled
for
editing.
Operator
Response:
Click
OK
to
dismiss
the
message.
GTMJC0810W
Do
you
want
to
save
the
changes
you
made
on
this
dialog?
Explanation:
Changes
made
on
this
dialog
have
not
yet
been
saved.
You
are
being
asked
if
you
want
to
save
the
changes.
System
Action:
Console
processing
continues.
Any
changes
are
saved
if
you
click
Save.
If
you
click
Do
Not
Save,
the
changes
are
not
saved
to
the
database.
Operator
Response:
Click
Save
in
the
message
to
save
changes.
Click
Do
Not
Save
if
you
do
not
want
to
save
changes.
Click
Cancel
to
return
to
the
dialog.
Administrator
Response:
Instruct
the
operator
to
click
Save,
Do
Not
Save,
or
Cancel
depending
on
whether
they
want
to
save
the
changes,
dismiss
the
changes,
or
return
to
the
dialog.
GTMJC0811E
An
error
has
occurred.
The
remarks
have
not
been
added
to
the
note(s).
Explanation:
You
attempted
to
add
note
remarks,
but
this
action
did
not
complete
successfully.
System
Action:
The
remarks
were
not
saved.
You
are
returned
to
the
Add
Remarks
dialog
containing
your
remarks.
Operator
Response:
Attempt
to
add
the
remarks
again.
If
the
problem
persists,
you
can
copy
your
remarks
to
the
clipboard
for
later
use,
then
notify
the
administrator.
Administrator
Response:
Try
adding
remarks
using
your
login
to
determine
if
the
problem
is
specific
to
the
user.
If
the
problem
persists,
then
gather
the
console
log
files
and
contact
Customer
Support.
GTMJC0812E
The
field_name
field
is
empty,
or
contains
only
blank
characters.
Explanation:
Information
is
required
in
the
specified
field
before
the
requested
action
can
be
performed.
System
Action:
The
action
was
not
performed.
You
are
returned
to
the
dialog
or
view
from
which
you
requested
the
action.
Operator
Response:
Enter
data
into
the
required
field
214
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
and
try
the
action
again,
or
cancel
the
request.
Administrator
Response:
The
user
requested
an
action
without
supplying
required
data.
Instruct
the
user
to
enter
data
into
the
specified
field.
If
the
required
data
is
being
supplied
and
an
error
still
occurs,
then
gather
the
console
log
files
and
contact
Customer
Support.
GTMJC0813E
The
specified
minimum
percent,
minimum_percent,
is
not
less
than
the
maximum
percent,
max_percent.
Explanation:
You
attempted
to
specify
a
minimum
percentage
that
is
greater
than
the
maximum
percent.
System
Action:
The
action
was
not
performed.
You
are
returned
to
the
dialog
or
view
from
which
you
attempted
to
perform
the
action.
Operator
Response:
Enter
data
into
the
specified
field
and
attempt
the
action
again,
or
cancel
if
you
do
not
want
to
perform
the
action.
Administrator
Response:
This
function
is
only
available
to
administrators.
GTMJC0814W
Are
you
sure
you
want
to
delete
this
threshold?
resource_count
resources
are
currently
linked
to
this
threshold.
Explanation:
You
are
being
asked
to
confirm
that
you
want
to
delete
a
threshold.
The
system
also
displays
the
number
of
resources
whose
status
will
no
longer
be
affected
by
this
threshold
if
you
delete
it.
System
Action:
If
you
confirm
that
you
want
to
delete
the
threshold,
the
threshold
is
deleted.
Administrator
Response:
Click
Yes
to
delete
the
threshold.
Click
No
if
you
do
not
want
to
delete
the
threshold.
GTMJC0815W
The
specified
minimum
alert
state,
minimum_alertstate,
is
not
less
than
the
maximum
alert
state,
max_alertstate.
Explanation:
You
attempted
to
specify
a
minimum
alert
state
that
is
greater
than
the
maximum
alert
state.
System
Action:
The
action
was
not
performed.
You
are
returned
to
the
dialog
or
view
from
which
you
attempted
to
perform
the
action.
Operator
Response:
Enter
data
into
the
specified
field
and
attempt
the
action
again,
or
cancel
if
you
do
not
want
to
perform
the
action.
Administrator
Response:
This
function
is
only
available
to
administrators.
GTMJC0816I
Enter
the
weight
value
for
child
resource
child_weight_value.
Explanation:
Specify
the
relative
weight
you
want
this
resource
to
contribute
to
the
percentage-based
thresholding
of
its
parent
resource.
System
Action:
When
you
click
OK,
the
weight
will
be
changed
to
the
value
that
you
specified.
Administrator
Response:
Enter
data
into
the
specified
field
and
click
OK.
Click
Cancel
to
dismiss
this
dialog
and
leave
the
weight
unchanged.
For
additional
information,
read
the
Weight
section
under
Columns
in
Child
resources
table
in
Propagation
Properties.
GTMJC0817E
The
specified
PBT
name,
pbt_name,
is
not
unique.
Change
the
name
to
one
that
is
not
already
in-use.
Explanation:
PBTs
must
have
unique
names,
and
the
name
specified
is
already
in-use.
System
Action:
Returns
to
the
Threshold
Properties
dialog.
Operator
Response:
Change
the
name
to
proceed
or
click
Cancel
to
discard
your
changes
and
dismiss
this
dialog.
Administrator
Response:
This
function
is
only
available
to
administrators.
GTMJC0818E
The
properties
of
this
PBT
are
identical
to
those
of
another
PBT.
PBTs
are
considered
duplicates
if
all
of
the
following
are
identical:
Minimum
and
maximum
percentages
Minimum
and
maximum
alert
states
Event
type
Event
message
state
Event
name
Event
description
Event
alert
state
Event
priority
Ensure
that
one
or
more
properties
are
unique
to
this
PBT.
Explanation:
System
Action:
Returns
to
the
Threshold
Properties
dialog.
Operator
Response:
Ensure
the
PBT
is
unique
or
click
Cancel
to
discard
your
changes
and
dismiss
this
dialog.
Administrator
Response:
This
function
is
only
available
to
administrators.
Chapter
16.
Console
Messages
-
GTMJC0502I
-
GTMJC9191I
215
GTMJC6200E
This
image
is
not
compatible
to
use
as
an
image.
Select
another
image.
Explanation:
You
selected
an
image
that
cannot
be
understood
by
the
console.
System
Action:
The
create
or
update
action
does
not
proceed
because
the
access
information
cannot
be
validated.
The
prompt
window
for
NetView
access
information
is
displayed
again.
Operator
Response:
Select
another
image
to
use.
Administrator
Response:
Select
another
image
to
use.
GTMJC6201I
The
selected
image
was
successfully
deleted
from
the
database.
Explanation:
The
request
made
to
the
database
to
delete
the
image
was
successful.
System
Action:
None
Operator
Response:
This
is
an
informational
message
that
indicates
a
successful
image
deletion.
GTMJC6201W
Are
you
sure
you
want
to
delete
the
selected
image
from
the
database?
Explanation:
You
attempted
to
delete
an
image
from
the
database.
You
are
being
asked
to
confirm
the
deletion.
System
Action:
The
console
processing
continues.
The
image
is
deleted
if
you
click
Yes.
If
you
click
No,
the
image
is
not
deleted.
Operator
Response:
Click
Yes
in
the
message
box
if
you
want
to
delete
the
image.
If
you
do
not,
click
No.
Administrator
Response:
It
is
customary
to
confirm
an
image
deletion.
Instruct
the
operator
to
click
Yes
or
No
in
the
message
box
depending
on
whether
they
want
the
deletion
to
continue.
GTMJC6202I
The
modified
images
were
successfully
updated
in
the
database.
Explanation:
The
request
to
the
database
to
update
any
modified
image
information
was
successful.
System
Action:
None
Operator
Response:
This
is
an
informational
message
that
indicates
a
successful
update
to
any
modified
images
in
the
database.
GTMJC6203W
Some
images
have
been
added
or
modified
and
not
saved.
Do
you
want
to
save
this
information?
Explanation:
You
modified
or
added
images
that
have
not
been
updated
in
the
database.
You
are
asked
to
confirm
the
deletion.
System
Action:
The
console
processing
continues.
All
image
information
that
has
been
added
or
modified
is
saved
in
the
database
if
you
click
Yes.
If
you
click
No,
image
modification
and
additions
are
not
saved
to
the
database.
Operator
Response:
Click
Yes
in
the
message
box
if
you
want
to
save
changes
for
any
modified
image.
If
you
do
not,
click
No.
Administrator
Response:
Instruct
the
operator
to
click
Yes
or
No
in
the
message
box
depending
on
whether
they
want
the
cancel
to
continue.
GTMJC6204W
Do
you
want
to
save
the
changes
you
made
to
the
page
page?
Explanation:
You
modified
a
page
that
has
not
been
updated
in
the
database.
You
are
being
asked
to
confirm
the
change.
System
Action:
The
console
processing
continues.
All
changes
that
were
made
are
saved
if
you
click
Yes.
If
you
click
No,
the
modifications
are
not
saved
to
the
database.
Operator
Response:
Click
Yes
in
the
message
box
to
save
changes.
Click
No
if
you
do
not
want
to
save
changes.
Administrator
Response:
Instruct
the
operator
to
click
Yes
or
No
depending
on
whether
they
want
to
cancel
or
continue.
GTMJC6205W
Do
you
want
to
save
the
changes
you
made
to
the
thresholds?
Explanation:
You
modified
the
page
that
has
not
been
updated
in
the
database.
You
are
asked
to
confirm
the
change.
System
Action:
The
console
processing
continues.
All
changes
that
were
modified
are
saved
if
you
click
Yes,
If
you
click
No,
modifications
are
not
saved
to
the
database.
Operator
Response:
Click
Yes
in
the
message
box
if
you
want
to
save
changes.
If
you
do
not,
click
No.
Administrator
Response:
Instruct
the
operator
to
click
Yes
or
No
in
the
message
box
depending
on
whether
they
want
the
cancel
to
continue.
GTMJC6206W
Do
you
want
to
save
the
changes
you
made
to
the
properties?
Explanation:
You
modified
the
page
that
was
updated
in
the
database.
You
are
being
asked
to
confirm
the
change.
System
Action:
The
console
processing
continues.
All
changes
that
were
modified
are
saved
if
you
click
Yes.
If
you
click
No,
modifications
are
not
saved
to
the
database.
Operator
Response:
Click
Yes
in
the
message
box
if
216
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
you
want
to
save
changes.
If
you
do
not,
click
No.
Administrator
Response:
Instruct
the
operator
to
click
Yes
or
No
in
the
message
box
depending
on
whether
they
want
the
cancel
function
to
continue.
GTMJC6207I
Connect
command
successfully
sent.
Explanation:
You
sent
a
Connect
request
to
the
system
name
that
is
listed
for
APPLID.
System
Action:
The
console
processing
continues.
GTMJC6208I
Disconnect
command
successfully
sent.
Explanation:
You
sent
a
Disconnect
request
to
the
system
name
listed
under
APPLID.
System
Action:
The
console
processing
continues.
GTMJC6209I
Recycle
command
successfully
sent.
Explanation:
You
sent
a
Recycle
request
to
the
system
name
listed
under
APPLID.
System
Action:
The
console
processing
continues.
GTMJC6210I
Image
sizes
that
are
missing
from
the
database
are
scaled
from
the
medium
image.
Therefore,
changes
made
to
the
medium
image
impact
other
images
that
are
scaled
from
the
medium
image.
Select
the
Change
all
images
option
to
have
images
marked
as
CHANGE
added
to
the
database
associated
with
the
resource
type
of
the
medium
image.
Select
the
Change
medium
image
option
to
have
images
marked
as
SCALED
appear
in
the
console.
Scaled
images
are
not
saved
to
the
database.
Changing
an
existing
image
to
the
same
image
results
in
no
changes
to
the
image.
Explanation:
The
medium-sized
image
is
used
to
scale
large,
small,
or
tiny
images
that
are
missing.
Changes
to
a
medium
image
can
impact
other
images
that
use
the
medium
image
to
scale
to
the
appropriate
resource
image
size.
System
Action:
The
console
processing
continues.
Administrator
Response:
The
Image
Manager
is
enabling
the
user
to
preview
the
image
as
a
result
of
changes
to
a
medium-sized
image.
GTMJC6212I
No
images
were
found
containing
this
file
name.
Explanation:
There
were
no
corresponding
file
names
currently
displayed
in
the
Image
Manager
that
contain
the
specified
text.
System
Action:
The
console
processing
continues.
Administrator
Response:
There
are
no
images
found
that
contain
the
file
name
entered
by
the
user.
GTMJC6220W
This
user
might
not
be
able
to
view
this
resource.
Do
you
want
to
continue?
Explanation:
The
user
to
whom
the
note
has
been
assigned
does
not
have
this
resource
available
in
a
critical
resource
list.
The
user
might
not
be
able
to
view
the
resource.
System
Action:
If
the
user
clicks
Yes,
then
the
processing
continues
and
the
ownership
note
will
be
transferred.
If
the
user
clicks
No,
then
the
dialog
remains
open
and
the
transfer
will
not
occur.
Operator
Response:
Click
Yes
in
the
message
box
if
you
want
to
save
changes.
If
you
do
not,
click
No.
Administrator
Response:
Instruct
the
operator
to
click
Yes
or
No
from
the
message
box
depending
on
whether
they
want
the
cancel
to
continue.
GTMJC6221E
This
user
is
not
allowed
to
drop
or
paste
resources
into
a
business
system.
Explanation:
Operators
can
only
drop
or
paste
resources
into
their
own
Critical
Resource
List.
Operators
cannot
drop
or
paste
resources
into
a
business
system.
System
Action:
The
drop
or
paste
operation
is
ended.
Operator
Response:
Drop
or
paste
the
resource(s)
into
your
own
Critical
Resource
List.
If
a
business
system
needs
to
be
modified,
contact
the
administrator
and
request
the
change.
GTMJC6222E
The
directory
location
is
not
valid.
Explanation:
The
directory
that
was
specified
as
the
location
of
preference
and
workspace
files
is
not
valid.
System
Action:
The
import/export
utility
stops
until
a
valid
directory
location
is
specified.
Administrator
Response:
Specify
a
valid
directory
location.
GTMJC6223W
The
preference
for
user
user_name
already
exists
in
the
database.
Do
you
want
to
overwrite
this
preference
in
the
database?
Explanation:
A
preference
is
already
stored
in
the
database
for
the
specified
user.
System
Action:
If
you
click
Yes,
the
import
utility
will
overwrite
the
preference
in
the
database.
If
you
click
No,
the
preference
for
this
user
will
not
be
imported.
Administrator
Response:
Click
Yes
to
have
the
import
utility
overwrite
the
preference
in
the
database.
Click
Chapter
16.
Console
Messages
-
GTMJC0502I
-
GTMJC9191I
217
No
if
you
do
not
want
to
import
the
preference
for
this
user.
GTMJC6224W
The
workspace
workspace_name
already
exists
in
the
database.
Do
you
want
to
overwrite
this
workspace
in
the
database?
Explanation:
The
specified
workspace
is
already
stored
in
the
database.
System
Action:
If
you
click
Yes,
the
import
utility
will
overwrite
this
workspace
in
the
database.
If
you
click
No,
this
workspace
will
not
be
imported.
Administrator
Response:
Click
Yes
to
have
the
import
utility
overwrite
this
workspace
in
the
database.
Click
No
if
you
do
not
want
to
import
this
workspace.
GTMJC6225E
An
error
occurred
while
importing
the
preference
for
user
user_name
to
the
database.
Explanation:
There
was
an
error
importing
this
preference
to
the
database.
System
Action:
This
preference
was
not
imported.
Administrator
Response:
Run
the
import/export
utility
again.
GTMJC6226E
An
error
occurred
while
importing
workspace
workspace_name
to
the
database.
Explanation:
There
was
an
error
importing
this
workspace
to
the
database.
System
Action:
This
workspace
was
not
imported.
Administrator
Response:
Run
the
import/export
utility
again.
GTMJC6227W
The
file
file_name
already
exists.
Do
you
want
to
overwrite
this
file?
Explanation:
The
specified
file
already
exists.
System
Action:
If
you
click
Yes,
the
import/export
utility
will
overwrite
this
file.
If
you
click
No,
the
preference
or
workspace
will
not
be
exported.
If
you
click
Yes
to
all,
the
import/export
utility
will
overwrite
all
specified
files
that
already
exist.
Administrator
Response:
Click
Yes
to
have
the
import/export
utility
overwrite
this
file.
Click
No
if
you
do
not
want
to
export
this
preference
or
workspace.
Click
Yes
to
all
to
have
the
import/export
utility
overwrite
all
specified
files
that
already
exist.
GTMJC6228E
An
error
occurred
while
exporting
the
preference
for
user
user_name.
Explanation:
There
was
an
error
exporting
this
preference
to
a
file.
System
Action:
This
preference
was
not
exported.
Administrator
Response:
Run
the
import/export
utility
again.
GTMJC6229E
An
error
occurred
while
exporting
workspace
workspace_name.
Explanation:
There
was
an
error
exporting
this
workspace
to
the
database.
System
Action:
This
workspace
was
not
exported.
Administrator
Response:
Run
the
import/export
utility
again.
GTMJC6230E
Operators
are
not
authorized
to
add
resources
to
an
executive
dashboard
list.
Explanation:
Only
administrators
are
authorized
to
add
resources
to
an
executive
dashboard
list.
System
Action:
The
request
to
add
resources
to
the
executive
dashboard
list
is
ignored.
Operator
Response:
If
a
resource
needs
to
be
added
to
an
executive
dashboard
list,
contact
an
administrator
and
request
the
change.
GTMJC6231E
The
resources
you
want
to
add
to
the
executive
dashboard
list
contain
one
or
more
physical
resources
and
or
critical
resource
lists.
Physical
resources
and
critical
resource
lists
are
not
valid
for
an
executive
dashboard
list.
Explanation:
You
are
attempting
to
add
a
physical
resource
or
a
critical
resource
list
to
an
executive
dashboard
list.
Only
business
systems
can
be
added
to
an
executive
dashboard
list.
Furthermore,
resources
cannot
be
added
across
different
instances
of
the
console.
System
Action:
The
request
to
add
resources
is
ignored.
Administrator
Response:
From
the
same
console
as
the
target
view,
copy
only
business
systems
to
the
clipboard
or
drag
only
business
systems.
Then
add
the
resources
to
the
executive
dashboard
list.
GTMJC6232W
number
of
the
number
business
systems
you
want
to
add
to
the
executive
dashboard
list
do
not
have
a
service
associated
with
them.
A
service
must
be
associated
with
a
business
system
before
the
business
system
can
be
added
to
an
executive
dashboard
list.
218
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
Select
Yes
to
open
the
properties
notebook
for
each
business
system
that
does
not
have
an
associated
service.
You
can
then
configure
a
service
for
each
business
system.
Select
No
to
ignore
each
business
system
that
does
not
have
an
associated
service.
Each
business
system
that
has
an
associated
service
is
added
to
the
executive
dashboard
list.
Explanation:
Some
of
the
business
systems
cannot
be
added
to
the
executive
dashboard
list
because
a
service
is
not
associated
with
the
business
systems.
System
Action:
None
of
the
business
systems
is
added
to
the
executive
dashboard
list.
The
system
is
waiting
for
a
response
from
you.
Administrator
Response:
Select
Yes
to
open
the
properties
notebook
for
each
business
system
that
does
not
have
an
associated
service.
You
can
then
configure
a
service
for
each
business
system.
Select
No
to
ignore
each
business
system
that
does
not
have
an
associated
service.
Each
business
system
that
has
an
associated
service
is
added
to
the
executive
dashboard
list.
GTMJC6233E
A
minimum
of
one
event
must
be
selected
to
create
an
ownership
note.
Explanation:
No
events
are
selected.
To
proceed,
select
at
least
one
event.
Operator
Response:
To
proceed,
select
one
or
more
of
the
events
that
are
listed
in
the
Events
table.
GTMJC6234W
The
following
resources
could
not
be
expanded
because
the
data
returned
exceeds
the
limit
defined
for
the
view.
Explanation:
The
resource(s)
were
not
expanded.
Operator
Response:
Contact
your
administrator
to
change
the
limits
for
this
view.
Administrator
Response:
In
the
Administrator
Preferences,
Configuration
page,
increase
the
view
limits
so
that
more
rows
can
be
returned
from
the
database.
GTMJC9103I
Warning:
Only
num_items
items
are
displayed.
Explanation:
The
data
for
the
view
might
have
been
truncated
and
therefore
the
contents
of
the
view
are
incomplete.
System
Action:
When
the
console
server
indicates
that
the
refresh
of
a
view
has
been
truncated,
then
the
console
displays
this
message.
Operator
Response:
You
can
see
the
total
number
of
items
displayed
by
looking
at
the
status
area
at
the
bottom
of
the
table.
You
can
use
the
filters
to
further
restrict
the
search,
in
order
to
return
fewer
items.
Administrator
Response:
The
system
is
working
correctly.
However,
if
you
suspect
there
is
a
problem,
contact
Customer
Support.
GTMJC9104I
This
view
might
contain
a
large
number
of
resources.
Use
the
column
filters
to
specify
criteria
for
displaying
the
resources
in
this
view.
Refresh
the
window
to
update
the
view
from
the
database.
Explanation:
The
view
could
result
in
a
large
amount
of
data,
and
the
purpose
of
this
message
is
to
remind
you
of
this
fact
so
that
you
can
set
some
filters
to
reduce
the
amount
of
data
returned
to
the
console.
System
Action:
This
message
is
displayed
when
a
view
is
opened
and
that
view
uses
table
filters
when
querying
the
console
server.
Operator
Response:
Set
the
filters
as
necessary
and
refresh
the
view.
GTMJC9106W
Are
you
sure
you
want
to
permanently
delete
resource
and
all
its
children
from
the
database?
This
operation
cannot
be
undone.
Do
you
want
to
delete
this
physical
resource
and
all
its
children?
Explanation:
A
physical
resource
has
been
selected
for
deletion
and
a
confirmation
is
required
before
permanently
removing
this
resource
and
its
children
from
the
database.
System
Action:
The
resource
and
its
children
will
be
permanently
removed
from
the
database.
Operator
Response:
Confirm
that
the
resource
and
its
children
should
be
removed
from
the
database.
GTMJC9107W
You
are
saving
changes
to
the
enabled
state
of
the
following
PBTs
for
this
business
system
shortcut.
linked_PBTs
Future
changes
to
the
local
enablement
of
the
PBT
that
is
linked
to
the
business
system
source
will
not
affect
the
local
enablement
of
the
same
PBT
on
this
shortcut.
Explanation:
You
changed
the
local
enablement
of
at
least
one
PBT.
If
that
PBT
is
also
linked
to
the
business
system
source,
local
enablement
for
the
source
and
the
shortcut
can
now
vary
independently.
System
Action:
If
you
save
the
changes
you
made,
this
shortcut
will
have
its
own
link
to
these
PBTs
and
as
a
result
their
local
enablement
will
no
longer
be
tied
to
that
of
the
same
PBTs
on
the
business
system
source.
Chapter
16.
Console
Messages
-
GTMJC0502I
-
GTMJC9191I
219
Administrator
Response:
Confirm
that
you
want
to
save
the
changes
you
made.
If
you
cancel
the
changes,
none
of
your
PBT-related
changes
will
be
saved
and
the
resource
properties
notebook
will
remain
open.
See
Understanding
Business
System
Shortcuts
for
information
about
business
system
shortcuts.
See
About
Percentage
Based
Thresholds
for
information
about
percentage
based
thresholds.
GTMJC9108W
You
have
linked
the
following
PBTs
to
a
source
business
system
from
which
shortcut_count
business
system
shortcuts
were
created.
linked_PBTs
These
newly-linked
PBTs
will
also
be
linked
to
the
shortcuts,
except
in
those
cases
where
a
shortcut
has
already
been
linked
to
a
PBT.
Explanation:
Linking
PBTs
to
a
business
system
source
also
implicitly
links
them
to
the
business
system
shortcuts
of
the
source.
System
Action:
If
you
save
the
changes
you
made,
the
shortcuts
will
be
implicitly
linked
to
these
PBTs.
Administrator
Response:
Confirm
that
you
want
to
save
the
changes
you
made.
If
you
cancel
the
changes,
none
of
your
PBT-related
changes
will
be
saved
and
the
resource
properties
notebook
will
remain
open.
See
Understanding
Business
System
Shortcuts
for
information
about
business
system
shortcuts.
See
About
Percentage
Based
Thresholds
for
information
about
percentage
based
thresholds.
GTMJC9109W
You
have
unlinked
the
following
PBTs
from
a
source
business
system
from
which
shortcut_count
business
system
shortcuts
were
created.
unlinked_PBTs
These
newly-unlinked
PBTs
will
also
be
unlinked
from
the
shortcuts,
except
for
those
shortcuts
that
were
explicitly
linked
to
a
given
PBT.
Explanation:
Linking
PBTs
to
a
business
system
source
also
implicitly
links
them
to
the
business
system
shortcuts
of
the
source.
Subsequently
unlinking
a
PBT
from
a
source
also
implicitly
unlinks
it
from
the
shortcuts,
subject
to
the
following
exceptions
that
explicitly
link
a
PBT
to
a
shortcut:
v
A
PBT
is
linked
to
a
shortcut
business
system
prior
to
being
linked
to
the
source
business
system
for
the
shortcut.
v
The
enabled
state
for
a
PBT
on
a
business
system
shortcut
is
modified,
at
which
point
the
PBT
relationship
to
the
shortcut
becomes
separate
from
the
relationship
to
the
business
system
source.
System
Action:
If
you
save
the
changes
you
made,
these
shortcuts
will
be
implicitly
unlinked
from
these
PBTs,
subject
to
the
exceptions
described
above.
Administrator
Response:
Confirm
that
you
want
to
save
the
changes
you
made.
If
you
cancel
the
changes,
none
of
your
PBT-related
changes
will
be
saved
and
the
resource
properties
notebook
will
remain
open.
See
Understanding
Business
System
Shortcuts
for
information
about
business
system
shortcuts.
See
About
Percentage
Based
Thresholds
for
information
about
percentage
based
thresholds.
GTMJC9110W
You
are
saving
changes
to
the
enabled
state
of
the
following
PBTs
for
this
business
system
source.
There
are
shortcut_count
business
system
shortcuts
associated
with
this
source.
modified_PBTs
The
enabled
state
will
also
be
changed
for
the
shortcuts,
except
for
those
shortcuts
that
were
explicitly
linked
to
a
given
PBT.
Explanation:
Linking
PBTs
with
a
source
implicitly
links
them
with
a
shortcut.
This
means
that
changes
to
the
enablement
on
the
source
also
affect
the
shortcut,
subject
to
the
following
exceptions
that
explicitly
link
a
PBT
to
a
shortcut:
v
A
PBT
is
linked
to
a
shortcut
business
system
prior
to
being
linked
to
the
source
business
system
for
the
shortcut.
v
The
enabled
state
for
a
PBT
on
a
business
system
shortcut
is
modified,
at
which
point
the
PBT
relationship
to
the
shortcut
becomes
separate
from
the
relationship
to
the
business
system
source.
System
Action:
If
you
save
the
changes
you
made,
the
local
enablement
of
these
PBTs
will
be
changed
for
this
source
and
all
shortcuts,
subject
to
the
exceptions
described
above.
Administrator
Response:
Confirm
that
you
want
to
save
the
changes
you
made.
If
you
cancel
the
changes,
none
of
your
PBT-related
changes
will
be
saved
and
the
resource
properties
notebook
will
remain
open.
See
Understanding
Business
System
Shortcuts
for
information
about
business
system
shortcuts.
See
About
Percentage
Based
Thresholds
for
information
about
percentage
based
thresholds.
GTMJC9120W
You
are
changing
information
in
one
or
more
fields
of
a
business
system
shortcut
to
be
different
from
the
source
business
system
folder
that
it
was
created
from.
If
you
save
the
changes,
these
fields
will
no
longer
be
updated
when
changes
are
made
to
the
same
fields
of
the
source
business
system
folder.
Fields
being
changed:
field_name_list
220
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
Are
you
sure
you
want
to
save
these
changes?
Explanation:
As
long
as
a
field
contains
the
same
value
as
the
source
business
system
folder,
changes
made
to
that
field
in
the
source
business
system
folder
are
also
applied
to
the
business
system
shortcuts
that
are
created
from
the
folder.
You
are
changing
the
value
for
one
or
more
fields
so
that
the
fields
no
longer
have
the
same
values
that
the
source
business
system
folder
has.
This
means
that
the
business
system
shortcut
is
no
longer
updated
when
the
specific
fields
are
changed
on
the
source
business
system
folder.
See
Understanding
Business
System
Shortcuts
for
additional
information.
System
Action:
If
you
save
the
values
for
this
business
system
shortcut,
it
will
no
longer
receive
changes
made
to
the
same
fields
on
the
source
business
system
folder.
Administrator
Response:
If
you
want
to
break
the
link
to
the
same
fields
on
the
source
business
system
folder,
confirm
that
the
values
should
be
saved.
GTMJC9121W
You
are
changing
one
or
more
fields
to
match
those
of
the
source
business
system
folder
that
this
business
system
shortcut
was
created
from.
If
you
save
the
changes,
these
fields
will
be
relinked
to
the
source
business
system
folder
and
information
in
the
fields
will
be
updated
when
changes
are
made
to
the
same
fields
of
the
source
business
system
folder.
Fields
being
changed:
field_name_list
Are
you
sure
you
want
to
save
these
changes?
Explanation:
As
long
as
information
in
a
field
of
a
business
system
shortcut
contains
the
same
value
as
the
source
business
system
folder,
changes
that
are
made
to
the
field
in
the
source
business
system
folder
are
also
applied
to
the
business
system
shortcuts
that
were
created
from
the
folder.
You
are
changing
the
value
for
one
or
more
fields
of
a
shortcut
so
that
the
fields
have
the
same
values
as
the
source
business
system
folder.
This
means
that
the
listed
fields
in
the
business
system
shortcut
will
be
updated
with
the
same
values
as
the
source
business
system
folder
when
the
listed
fields
are
changed
on
the
source.
See
Understanding
Business
System
Shortcuts
for
additional
information.
System
Action:
If
you
save
the
changes
to
the
values
for
this
business
system
shortcut,
the
shortcut
will
receive
updates
when
the
listed
fields
of
the
source
business
system
folder
are
changed.
Administrator
Response:
If
you
want
to
restore
the
link
to
the
corresponding
fields
on
the
source
business
system
folder,
confirm
that
the
values
should
be
saved
GTMJC9122W
You
are
changing
information
in
one
or
more
fields
of
a
source
business
system
folder
from
which
number_of_shortcuts
business
system
shortcuts
were
created.
Each
change
will
be
applied
to
the
same
fields
of
the
business
system
shortcuts
unless
those
fields
have
been
customized
on
the
shortcut.
Fields
being
changed:
field_name_list
Are
you
sure
you
want
to
save
these
changes?
Explanation:
As
long
as
information
in
a
field
of
a
business
system
shortcut
contains
the
same
value
as
the
source
business
system
folder,
changes
that
are
made
to
the
field
in
the
source
business
system
folder
are
also
applied
to
the
business
system
shortcuts
that
were
created
from
the
folder.
You
are
changing
the
value
for
one
or
more
fields
of
a
source
business
system
folder
and
these
changes
will
be
applied
to
the
business
system
shortcuts
that
were
created
from
this
source,
if
the
corresponding
fields
of
the
shortcut
have
not
been
customized.
See
Understanding
Business
System
Shortcuts
for
additional
information.
System
Action:
If
you
save
the
values
for
this
source
business
system
folder,
the
changes
will
be
applied
to
the
listed
fields
of
its
business
system
shortcuts
unless
those
fields
on
the
shortcut
have
been
customized.
Administrator
Response:
If
you
want
to
change
the
information
in
the
listed
fields
of
this
source
business
system
folder,
and
cause
uncustomized
fields
of
its
business
system
shortcuts
to
be
updated
as
well,
confirm
that
the
values
should
be
saved.
GTMJC9150I
Problem
ticket
ticket_id
was
created
successfully
for
resource
resource_name.
Explanation:
A
problem
ticket
was
successfully
created
in
the
problem
management
system.
System
Action:
A
problem
ticket
was
created.
The
console
processing
continues.
GTMJC9152I
Update
was
successful
for
problem
ticket
ticket_id.
Explanation:
The
problem
ticket
was
successfully
updated
or
closed
in
your
problem
management
system.
System
Action:
The
problem
ticket
was
updated.
The
console
processing
continues.
GTMJC9160I
Change
request
request_id
was
created
successfully
for
resource
resource_name.
Explanation:
A
change
request
was
successfully
created
in
the
change
management
system.
Chapter
16.
Console
Messages
-
GTMJC0502I
-
GTMJC9191I
221
System
Action:
A
change
request
was
created.
The
console
processing
continues.
GTMJC9162I
Update
was
successful
for
change
request
request_id.
Explanation:
The
change
request
was
successfully
updated
in
the
change
management
system.
System
Action:
The
change
request
was
updated.
The
console
processing
continues.
GTMJC9190I
The
context
menu
can
only
be
displayed
for
one
unique
problem
ticket.
Explanation:
The
requested
context
menu
cannot
be
displayed
because
it
is
only
applicable
to
a
single
unique
problem
ticket.
If
you
have
selected
multiple
entries,
the
context
menu
can
only
be
displayed
if
they
all
associated
with
the
same
problem
ticket.
System
Action:
The
console
displays
this
message.
GTMJC9191I
The
context
menu
can
only
be
displayed
for
one
unique
resource.
Explanation:
The
requested
context
menu
cannot
be
displayed
because
it
is
only
applicable
to
a
single
unique
resource.
If
you
select
multiple
entries,
the
context
menu
can
only
be
displayed
if
all
the
selections
are
associated
with
the
same
resource.
System
Action:
The
console
displays
this
message.
222
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
Chapter
17.
Intelligent
Monitoring
for
NetIQ
AppManager
Message
-
GTMIA0001E
The
following
message
is
issued
by
Intelligent
Monitoring
for
NetIQ
AppManager.
GTMIA0001E
Invalid
subnet
mask
was
specified.
Explanation:
The
subnet
mask
you
have
specified
is
incorrect.
User
Response:
Specify
a
valid
subnet
mask.
©
Copyright
IBM
Corp.
2000,
2004
223
Chapter
18.
Percentage-based
Threshold
Messages
-
GTMPT1000E
-
GTMPE1302E
The
following
are
Tivoli
Business
Systems
Manager
percentage-based
threshold
messages.
GTMPT1000E
At
least
one
of
PBTID
and
PBTName
must
not
be
NULL
Explanation:
There
was
an
attempt
to
work
with
a
percentage-based
threshold
without
specifying
its
name
or
ID.
System
Action:
The
operation
fails.
User
Response:
Specify
the
name
or
ID
of
a
percentage-based
threshold
and
try
the
operation
again.
GTMPT1001E
Enabled
must
be
0
(disabled)
or
1
(enabled)
Explanation:
There
was
an
attempt
to
define
or
update
the
Enabled
field
of
a
percentage-based
threshold
with
a
value
that
is
not
valid.
System
Action:
The
operation
fails.
User
Response:
Specify
0
or
1
for
the
Enabled
field
and
try
the
operation
again.
GTMPT1002E
MinAlertState
must
be
1(Green),
2(Yellow),
or
3(Red)
Explanation:
There
was
an
attempt
to
define
or
update
the
MinAlertState
field
of
a
percentage-based
threshold
with
a
value
that
is
not
valid.
System
Action:
The
operation
fails.
User
Response:
Specify
1,
2,
or
3
for
the
MinAlertState
field
and
try
the
operation
again.
GTMPT1003E
MaxAlertState
must
be
1(Green),
2(Yellow),
or
3(Red)
Explanation:
There
was
an
attempt
to
define
or
update
the
MaxAlertState
field
of
a
percentage-based
threshold
with
a
value
that
is
not
valid.
System
Action:
The
operation
fails.
User
Response:
Specify
1,
2,
or
3
for
the
MaxAlertState
field
and
try
the
operation
again.
GTMPT1004E
MinAlertState
cannot
be
greater
than
MaxAlertState
Explanation:
There
was
an
attempt
to
define
or
update
a
percentage-based
threshold
with
MinAlertState
greater
than
MaxAlertState.
System
Action:
The
operation
fails.
User
Response:
Specify
a
MinAlertState
value
that
is
less
than
or
equal
to
MaxAlertState
and
try
the
operation
again.
GTMPT1005E
MinPercentage
must
be
between
0
and
100
Explanation:
There
was
an
attempt
to
define
or
update
the
MinPercentage
field
of
a
percentage-based
threshold
with
a
value
that
is
not
valid.
System
Action:
The
operation
fails.
User
Response:
Specify
a
MinPercentage
value
in
the
range
0
–
100
and
try
the
operation
again.
GTMPT1006E
MaxPercentage
must
be
between
0
and
100
Explanation:
There
was
an
attempt
to
define
or
update
the
MaxPercentage
field
of
a
percentage-based
threshold
with
a
value
that
is
not
valid.
System
Action:
The
operation
fails.
User
Response:
Specify
a
MaxPercentage
value
in
the
range
0
–
100
and
try
the
operation
again.
GTMPT1007E
MinPercentage
cannot
be
greater
than
MaxPercentage
Explanation:
There
was
an
attempt
to
define
or
update
a
percentage-based
threshold
with
MinPercentage
greater
than
MaxPercentage.
System
Action:
The
operation
fails.
User
Response:
Specify
a
MinPercentage
value
that
is
less
than
or
equal
to
MaxPercentage
and
try
the
operation
again.
GTMPT1008E
EventType
must
be
EXCP
(Exception)
or
MESG
(Message)
Explanation:
There
was
an
attempt
to
define
or
update
the
EventType
field
of
a
percentage-based
threshold
with
a
value
that
is
not
valid.
System
Action:
The
operation
fails.
User
Response:
Specify
either
EXCP
or
MESG
for
EventType
and
try
the
operation
again.
©
Copyright
IBM
Corp.
2000,
2004
225
GTMPT1009E
EventName
cannot
be
NULL
Explanation:
There
was
an
attempt
to
define
or
update
the
EventName
field
of
a
percentage-based
threshold
with
a
NULL
value.
System
Action:
The
operation
fails.
User
Response:
Specify
a
non-NULL
value
for
EventName
and
try
the
operation
again.
GTMPT1010E
EventText
cannot
be
NULL
Explanation:
There
was
an
attempt
to
define
or
update
the
EventText
field
of
a
percentage-based
threshold
with
a
NULL
value.
System
Action:
The
operation
fails.
User
Response:
Specify
a
non-NULL
value
for
EventText
and
try
the
operation
again.
GTMPT1011E
EventAlertState
must
be
1(Green),
2(Yellow),
or
3(Red)
Explanation:
There
was
an
attempt
to
define
or
update
the
EventAlertState
field
of
a
percentage-based
threshold
with
a
value
that
is
not
valid.
System
Action:
The
operation
fails.
User
Response:
Specify
1,
2,
or
3
for
EventAlertState
and
try
the
operation
again.
GTMPT1012E
EventPriority
must
be
1(Critical)
,
2(High),
3(Medium),
4(Low),
or
5(Ignore)
Explanation:
There
was
an
attempt
to
define
or
update
the
EventPriority
field
of
a
percentage-based
threshold
with
a
value
that
is
not
valid.
System
Action:
The
operation
fails.
User
Response:
Specify
1
–
5
for
EventPriority
and
try
the
operation
again.
GTMPT1013E
Unknown
bit
set
in
EventFlags
Explanation:
There
was
an
attempt
to
define
or
update
the
EventFlags
field
of
a
percentage-based
threshold
with
an
undefined
bit
set.
System
Action:
The
operation
fails.
User
Response:
Specify
either
0
(normal
exception
or
message)
or
1
(singleton
exception)
for
EventFlags
and
try
the
operation
again.
GTMPT1014E
Unknown
bit
set
in
ExecMode
Explanation:
An
undefined
bit
was
set
in
the
ExecMode
parameter.
System
Action:
The
operation
fails.
User
Response:
Set
only
the
defined
bits
of
ExecMode
and
try
the
operation
again.
Valid
bits
are
1
(ValidateParams),
2
(BestEffort),
and
4
(ReportErrors).
GTMPT1015E
Attempt
to
create
a
percentage-based
threshold
with
a
duplicate
name
Explanation:
There
was
an
attempt
to
define
two
or
more
percentage-based
thresholds
with
the
same
name
but
different
parameters.
System
Action:
The
operation
fails.
User
Response:
Make
sure
that
each
percentage-based
threshold
being
defined
has
a
distinct
name
and
try
the
operation
again.
GTMPT1400E
Missing
input
table
#PBTsToDefine
Explanation:
A
call
to
DefineAndUsePBTs
was
made
without
defining
the
#PBTsToDefine
table.
System
Action:
The
operation
fails.
User
Response:
Create
and
populate
the
#PBTsToDefine
table
and
try
the
operation
again.
GTMPT1100E
Specified
percentage-based
threshold
does
not
exist
Explanation:
A
call
was
made
to
GetPBTs
or
GetPBTStatus
for
an
undefined
percentage-based
threshold.
System
Action:
The
operation
fails.
User
Response:
Specify
a
valid
percentage-based
threshold
and
try
the
operation
again.
GTMPT1101E
DesiredResultSets
must
be
1,
2,
or
3
Explanation:
The
DesiredResultSets
parameter
to
GetPBTs
was
specified
with
a
value
that
is
not
valid.
System
Action:
The
operation
fails.
User
Response:
Specify
1
(definitions),
2
(references),
or
3
(both)
for
DesiredResultSets
and
try
the
operation
again.
GTMPT1200E
Specified
object
does
not
exist
Explanation:
A
call
to
SetWeights
contains
an
object
reference
that
is
not
valid.
System
Action:
The
operation
fails.
User
Response:
Specify
a
valid
object
ID
and
try
the
operation
again.
GTMPT1201E
Unknown
bit
set
in
ExecMode
Explanation:
An
undefined
bit
was
set
in
the
ExecMode
parameter
of
SetWeights.
System
Action:
The
operation
fails.
226
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
User
Response:
Set
only
the
defined
bits
of
ExecMode
and
try
the
operation
again.
Valid
bits
are
1
(ValidateParams),
2
(BestEffort),
and
4
(ReportErrors).
GTMPT1202E
Negative
value
specified
for
NewWeight.
Must
be
between
0
and
10,000.
Explanation:
The
NewWeight
parameter
for
SetWeights
was
specified
with
a
value
that
is
not
valid.
System
Action:
The
operation
fails.
User
Response:
Specify
a
value
in
the
range
0
–
10000
for
SetWeights
and
try
the
operation
again.
GTMPT1203E
Value
greater
than
10,000
specified
for
NewWeight.
Must
be
between
0
and
10,000.
Explanation:
The
NewWeight
parameter
for
SetWeights
was
specified
with
a
value
that
is
not
valid.
System
Action:
The
operation
fails.
User
Response:
Specify
a
value
in
the
range
0
–
10000
for
SetWeights
and
try
the
operation
again.
GTMPT1204E
Null
value
specified
for
NewWeight.
Must
be
between
0
and
10,000.
Explanation:
The
NewWeight
parameter
for
SetWeights
was
specified
with
a
value
that
is
not
valid.
System
Action:
The
operation
fails.
User
Response:
Specify
a
value
in
the
range
0
–
10000
for
SetWeights
and
try
the
operation
again.
GTMPT1300E
Specified
object
does
not
exist
Explanation:
A
call
to
UsePBTs
contained
an
object
reference
that
is
not
valid.
System
Action:
The
operation
fails.
User
Response:
Specify
a
valid
object
ID
and
try
the
operation
again.
GTMPT1301E
Specified
percentage-based
threshold
does
not
exist
Explanation:
A
call
to
UsePBTs
specified
an
undefined
percentage-based
threshold.
System
Action:
The
operation
fails.
User
Response:
Specify
a
valid
percentage-based
threshold
ID
or
name
and
try
the
operation
again.
GTMPT1302E
Invalid
Action
code
specified.
Must
be
0(disable),
1(enable),
or
2(delete).
Explanation:
The
Action
parameter
for
UsePBTs
contains
a
value
that
is
not
valid.
System
Action:
The
operation
fails.
User
Response:
Specify
0,
1,
or
2
for
the
Action
parameter
and
try
the
operation
again.
GTMPT1303E
Unknown
bit
set
in
ExecMode
Explanation:
An
undefined
bit
was
set
in
the
ExecMode
parameter
of
UsePBTs.
System
Action:
The
operation
fails.
User
Response:
Set
only
the
defined
bits
of
ExecMode
and
try
the
operation
again.
Valid
bits
are
1
(ValidateParams),
2
(BestEffort),
and
4
(ReportErrors).
Chapter
18.
Percentage-based
Threshold
Messages
-
GTMPT1000E
-
GTMPE1302E
227
Chapter
19.
Program
Exit
Messages
-
GTMPE1000I
-
GTMPE2008E
The
following
are
Tivoli
Business
Systems
Manager
program
exit
messages.
GTMPE1000I
program
called
SetDataFilePath.
Data
file
path
=
folder
Explanation:
This
message
is
written
to
the
INTMGRyyymmdd.log
file
for
tracing
and
debugging.
It
logs
the
fact
that
the
SetDataFilePath()
procedure
has
been
called.
Message
Variables:
program
-
The
name
of
the
calling
program.
The
value
is
always
IntegrationManager.
folder
-
This
value
is
the
file
folder
name
read
from
the
registry
where
the
Tivoli
Business
Systems
Manager
data
files
are
located.
GTMPE1001I
REQUEST_RETURN_CODE
=
retcode
Explanation:
This
message
is
written
to
the
INTMGRyyymmdd.log
file
for
tracing
and
debugging.
It
logs
the
value
of
the
REQUEST_RETURN_CODE
name
value
pair.
Message
Variables:
retcode
-
The
value
of
the
return
code
within
a
guid.out
file.
GTMPE1003I
Procedure
ProcessRequest()
started.
Explanation:
This
message
is
written
to
the
INTMGRyyymmdd.log
file
for
tracing
and
debugging.
It
logs
the
fact
that
the
ProcessRequest()
procedure
was
called.
GTMPE1004I
Procedure
ProcessRequest()
using
RequestProcessName
=
program
Explanation:
This
message
is
written
to
the
INTMGRyyymmdd.log
file
for
tracing
and
debugging.
It
logs
the
name
of
the
program
used
to
process
requests.
Message
Variables:
program
-
The
name
of
the
request
processor
program
that
should
be
started
to
process
a
request.
GTMPE1005I
Shell
command
to
execute
value
Explanation:
This
message
is
written
to
the
INTMGRyyymmdd.log
file
for
tracing
and
debugging.
It
logs
the
value
of
the
command
line
argument
used
to
process
a
request.
Message
Variables:
value
-
The
string
value
that
represent
the
command
line
argument
to
be
executed
on
the
command
line.
GTMPE1006I
RequestProcessorHandle
=
process_id
inside
procedure
ProcessRequest().
Explanation:
This
message
is
written
to
the
INTMGRyyymmdd.log
file
for
tracing
and
debugging.
It
logs
the
value
of
the
operating
system
process
number
that
was
created.
Message
Variables:
process_id
-
The
process
ID
returned
form
the
CreateProcess()
API
call.
GTMPE1007I
Procedure
ProcessRequest()
completed
successfully.
Explanation:
This
message
is
written
to
the
INTMGRyyymmdd.log
file
for
tracing
and
debugging.
It
logs
the
fact
that
the
procedure
ProcessRequest()
completed
without
error.
GTMPE1008I
ProcessRequest()
ended.
Explanation:
This
message
is
written
to
the
INTMGRyyymmdd.log
file
for
tracing
and
debugging.
It
logs
the
fact
that
the
CreateProcess()
API
call
within
the
ProcessRequest()
procedure
completed.
GTMPE1009I
ProcessRequest()
ended.
Explanation:
This
message
is
written
to
the
INTMGRyyymmdd.log
file
for
tracing
and
debugging.
It
logs
the
fact
that
the
procedure
ProcessRequest()
completed.
GTMPE1010I
Procedure
GetRequestOutput()
called.
Explanation:
This
message
is
written
to
the
INTMGRyyymmdd.log
file
for
tracing
and
debugging.
It
logs
the
fact
that
the
procedure
GetRequestOutput()
was
called.
GTMPE1011I
Procedure
GetRequestOutput()
returning
a
value
of
value.
Explanation:
This
message
is
written
to
the
INTMGRyyymmdd.log
file
for
tracing
and
debugging.
It
logs
the
return
value
from
the
GetRequestOutput()
procedure.
Message
Variables:
value
-
The
numeric
value
returned
from
the
GetRequestOutput()
procedure.
©
Copyright
IBM
Corp.
2000,
2004
229
GTMPE1012I
Procedure
GetRequestOutput()
ended.
Explanation:
This
message
is
written
to
the
INTMGRyyymmdd.log
file
for
tracing
and
debugging.
It
logs
the
fact
that
the
call
to
the
GetRequestOutput()
procedure
ended.
GTMPE1013I
Procedure
GetRequestOutput()
has
caused
an
error.
Explanation:
This
message
is
written
to
the
INTMGRyyymmdd.log
file
for
tracing
and
debugging.
It
logs
the
fact
that
the
call
to
the
GetRequestOutput()
procedure
has
produced
an
error.
Administrator
Response:
If
integration
requests
are
failing,
contact
IBM
Software
Support.
GTMPE1014I
Procedure
RequestOutput()
called.
Explanation:
This
message
is
written
to
the
INTMGRyyymmdd.log
file
for
tracing
and
debugging.
It
logs
the
fact
that
the
procedure
RequestOutput()
was
called.
GTMPE1015I
Procedure
RequestOutput()
ended.
Explanation:
This
message
is
written
to
the
INTMGRyyymmdd.log
file
for
tracing
and
debugging.
It
logs
the
fact
that
the
procedure
RequestOutput()
has
ended.
GTMPE1016I
Procedure
RequestOutput()
has
caused
an
error.
Explanation:
This
message
is
written
to
the
INTMGRyyymmdd.log
file
for
tracing
and
debugging.
It
logs
the
fact
that
the
call
to
the
RequestOutput()
procedure
has
produced
an
error.
Administrator
Response:
If
integration
requests
are
failing,
contact
IBM
Software
Support.
GTMPE1017I
Procedure
DeleteDataFiles
has
been
called.
Explanation:
This
message
is
written
to
the
INTMGRyyymmdd.log
file
for
tracing
and
debugging.
It
logs
the
fact
that
the
procedure
DeleteDataFiles()
was
called.
GTMPE2000E
REQUEST_RETURN_CODE
is
missing
in
output
file
-
contact
admin.
Explanation:
This
error
message
occurs
when
your
request
processor
does
not
generate
a
REQUEST_RETURN_CODE
name
value
pair
in
the
guid.out
file.
User
Response:
Contact
your
administrator.
Administrator
Response:
Correct
the
logic
in
your
request
processor
to
generate
the
name
value
pair
as
the
first
entry
in
the
guid.out
file.
GTMPE2001E
REQUEST_ERROR_MSG
is
missing
in
output
file
-
contact
admin.
Explanation:
This
error
message
occurs
when
your
request
processor
does
not
generate
a
REQUEST_ERROR_MSG
name
value
pair
in
the
guid.out
file.
User
Response:
Contact
your
administrator.
Administrator
Response:
Correct
the
logic
in
your
request
processor
to
generate
the
name
value
pair
as
the
second
entry
in
the
guid.out
file.
This
entry
should
follow
the
REQUEST_RETURN_CODE
name
value
pair
entry.
GTMPE2002E
Line
in
output
file
contained
the
wrong
number
of
data
elements
-
contact
admin.
Explanation:
This
error
message
occurs
when
your
request
processor
does
not
generate
the
correct
format
for
a
line
entry
in
the
guid.out
file.
User
Response:
Contact
your
administrator.
Administrator
Response:
All
lines
in
the
guid.out
file
should
be
in
the
following
format:
fieldname|row_id|number_of_records|fieldvalue
(CR+LF)
GTMPE2003E
Empty
output
file
found-
contact
admin.
Explanation:
This
error
message
indicates
that
your
request
processor
generated
an
empty
guid.out
file.
User
Response:
Contact
your
administrator.
Administrator
Response:
Verify
the
logic
that
formats
and
writes
to
the
guid.out
file.
GTMPE2004E
Could
not
find
output
file
-
contact
admin.
Explanation:
This
message
typically
occurs
when
there
is
no
connection
from
your
Problem
or
Change
application.
This
error
can
also
occur
if
there
is
a
failure
in
the
execution
code
within
your
request
processor.
User
Response:
Contact
your
administrator.
Administrator
Response:
Verify
that
your
connection
between
the
database
server
and
the
application
is
active.
Test
your
request
processor
code
using
a
guid.in
file
generated
from
the
GUI
process.
Other
possible
causes
of
the
problem
include
the
following:
230
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
v
There
was
an
error
in
the
integration
program
in
which
it
failed
to
correctly
process
the
results
returned
from
the
problem
application.
v
v
The
integration
program
did
not
format
the
output
file
correctly.
v
v
There
was
a
failure
between
the
integration
and
the
problem
application.
v
v
The
problem
application
was
not
available.
v
v
A
time-out
value
was
exceeded.
The
problem/change
process
calls
the
integration
program
and
waits
30
seconds
(the
default)
for
the
<GUID>.out
file
to
be
created.
If
the
file
is
not
created,
this
error
will
be
generated.
This
can
occur
if
your
network
or
other
parts
of
their
environment
is
running
slowly.
If
this
is
the
case,
the
time-out
value
can
be
increased
in
the
SystemsConfiguration
table.
GTMPE2005E
Request
processor
name
timed
out
-
contact
admin.
Timeout(sec)
timeout
setting.
Explanation:
This
error
message
indicates
that
your
request
processor
did
not
generate
a
guid.out
file
within
the
TIMEOUT_VALUE
specified
in
the
SystemConfiguration
table.
If
no
value
is
specified,
the
default
value
is
45
seconds.
Message
Variables:
name
-
The
name
of
the
request
processor
file.
timeout
setting
-
The
current
time
out
value.
This
value
is
in
seconds.
User
Response:
Contact
your
administrator.
Administrator
Response:
Increase
the
TIMEOUT_VALUE
in
the
SystemConfiguration
table
or
insert
a
TIME_OUT
row
in
the
SystemConfiguration
table
with
a
value
greater
that
45
seconds.
GTMPE2006E
Request
failed
request_process_name.
Last
DLL
error
-
contact
admin.
value
Explanation:
This
error
message
occurs
when
an
attempt
to
call
a
request
processor
from
the
command
line
cannot
find
the
file
for
the
command.
Message
Variables:
request_process_name
-
The
name
of
the
request
processor
file.
value
-
The
numeric
value
for
the
Windows
DLL
error
from
the
API
call
to
CreateProcess().
User
Response:
Contact
your
administrator.
Administrator
Response:
If
your
request
processor
is
a
Visual
Basic
or
C
executable,
check
your
registry
entry
to
verify
it
is
registered.
If
your
request
processor
is
not
a
Windows
executable
file
(for
example,
REXX,
Kornshell)
you
might
have
not
entered
a
correct
value
in
the
request
processor
language
entry
of
the
SystemConfiguration
table.
GTMPE2007E
Could
not
find
file
-
contact
admin.
value
error
Explanation:
This
error
message
indicates
that
your
request
processor
program
name
defined
in
the
SystemConfiguration
table
could
not
be
found
in
the
Tivoli_manager\data
directory
on
your
database
server.
Message
Variables:
value
-
The
value
of
the
command
line
argument
that
was
executed.
This
will
contain
the
name
of
the
request
processor.
error
-
Additional
error
information
describing
why
the
file
could
not
be
found.
User
Response:
Contact
your
administrator.
Administrator
Response:
Check
the
file
name
in
the
SystemConfiguration
table
to
ensure
it
is
the
correct
file
name
and
that
it
is
not
misspelled.
If
the
file
is
not
in
the
Tivoli_manager\data
folder,
place
a
copy
into
the
folder.
GTMPE2008E
Last
DLL
error
-
contact
admin.
value
error
Explanation:
This
error
message
indicated
that
the
API
call
to
CreateProcess()
failed.
Message
Variables:
value
-
The
numeric
value
for
the
Windows
DLL
error
from
the
API
call
to
CreateProcess().
error
-
Additional
error
information
describing
why
the
API
call
failed.
User
Response:
Contact
your
administrator.
Administrator
Response:
Try
the
previous
request
again.
If
the
error
persists,
contact
IBM
Software
Support.
Chapter
19.
Program
Exit
Messages
-
GTMPE1000I
-
GTMPE2008E
231
Chapter
20.
Resource
Level
Propagation
Messages
-
GTMPR1001E
-
GTMPR1009E
The
following
are
Tivoli
Business
Systems
Manager
resource
level
propagation
messages.
GTMPR1001E
An
attempt
was
made
to
set
a
class-level
threshold
to
-1.
Explanation:
A
value
that
was
not
valid
was
specified
for
the
threshold.
The
resource
type
threshold
must
be
a
positive
value.
System
Action:
The
operation
fails.
User
Response:
Correct
the
value
and
try
the
operation
again.
See
the
appendix
in
the
IBM
Tivoli
Business
Systems
Manager
Command
Reference
for
information
about
the
XML
values.
See
the
IBM
Tivoli
Business
Systems
Manager
Administrator’s
Guide
for
information
about
Automated
Business
Systems.
GTMPR1002E
An
attempt
was
made
to
set
a
threshold
to
a
negative
value
other
than
-1.
Explanation:
A
value
that
was
not
valid
was
specified
for
the
threshold.
The
value
must
be
a
positive
value
or
-1.
System
Action:
The
operation
fails.
User
Response:
Correct
the
value
and
try
the
operation
again.
See
the
appendix
in
the
IBM
Tivoli
Business
Systems
Manager
Command
Reference
for
information
about
the
XML
values.
See
the
IBM
Tivoli
Business
Systems
Manager
Administrator’s
Guide
for
information
about
Automated
Business
Systems.
GTMPR1003E
AlertState
must
be
2(Yellow),
or
3(Red).
Explanation:
A
value
that
was
not
valid
was
specified
for
the
AlertState
field
of
the
threshold.
System
Action:
The
operation
fails.
User
Response:
Specify
2
(or
y
or
yellow)
or
3
(or
r
or
red)
for
the
AlertState
value
and
try
the
operation
again.
See
the
appendix
in
the
IBM
Tivoli
Business
Systems
Manager
Command
Reference
for
information
about
the
XML
values.
See
the
IBM
Tivoli
Business
Systems
Manager
Administrator’s
Guide
for
information
about
Automated
Business
Systems.
GTMPR1004E
Priority
must
be
2(High),
3(Medium),
or
4(Low).
Explanation:
A
value
that
was
not
valid
was
specified
for
the
Priority
field
of
the
threshold.
System
Action:
The
operation
fails.
User
Response:
Specify
2
(or
h
or
high),
3
(or
m
or
medium),
or
4
(or
l
or
low)
for
the
Priority
value
and
try
the
operation
again.
See
the
appendix
in
the
IBM
Tivoli
Business
Systems
Manager
Command
Reference
for
information
about
the
XML
values.
See
the
IBM
Tivoli
Business
Systems
Manager
Administrator’s
Guide
for
information
about
Automated
Business
Systems.
GTMPR1005E
An
attempt
was
made
to
set
the
threshold
for
an
invalid
cid.
Explanation:
The
specified
resource
did
not
have
a
valid
resource
type
identifier
(CID).
System
Action:
The
operation
fails.
User
Response:
Specify
a
valid
CID
for
the
resource
and
try
the
operation
again.
The
CID
is
the
Tivoli
Business
System
Manager
resource
type
identifier.
The
CID
can
be
obtained
through
the
console
by
setting
the
Tooltips
of
the
Administrative
Preferences
and
hovering
over
the
resource
with
the
mouse.
See
the
appendix
in
the
IBM
Tivoli
Business
Systems
Manager
Command
Reference
for
information
about
the
XML
values.
See
the
IBM
Tivoli
Business
Systems
Manager
Administrator’s
Guide
for
information
about
Automated
Business
Systems.
GTMPR1006E
EventType
must
be
0(ChildEvent)
or
1(ExceptionEvent).
Explanation:
A
value
that
was
not
valid
was
specified
for
the
EventType
field
of
the
threshold.
System
Action:
The
operation
fails.
User
Response:
Specify
0
(or
c
or
childevent)
or
1
(or
e
or
exceptionevent)
for
the
EventType
value
and
try
the
operation
again.
See
the
appendix
in
the
IBM
Tivoli
Business
Systems
Manager
Command
Reference
for
information
about
the
XML
values.
See
the
IBM
Tivoli
Business
Systems
Manager
©
Copyright
IBM
Corp.
2000,
2004
233
Administrator’s
Guide
for
information
about
Automated
Business
Systems.
GTMPR1007E
An
attempt
was
made
to
set
the
threshold
and
the
cid
or
id
is
null.
Explanation:
A
CID
and
an
ID
must
be
specified.
The
CID
is
the
Tivoli
Business
System
Manager
resource
type
identifier,
and
the
ID
is
the
Tivoli
Business
System
Manager
generated
identifier
for
the
resource.
System
Action:
The
operation
fails.
User
Response:
Specify
a
valid
CID
and
ID
for
the
resource
and
try
the
operation
again.
The
CID
and
ID
can
be
obtained
through
the
console
by
setting
the
Tooltips
of
the
Administrative
Preferences
and
hovering
over
the
resource
with
the
mouse.
See
the
appendix
in
the
IBM
Tivoli
Business
Systems
Manager
Command
Reference
for
information
about
the
XML
values.
See
the
IBM
Tivoli
Business
Systems
Manager
Administrator’s
Guide
for
information
about
Automated
Business
Systems.
GTMPR1008E
An
attempt
was
made
to
reset
a
class-level
threshold.
Explanation:
The
thresholds
for
a
resource
instance
can
be
reset
to
the
resource
type
(class-level)
thresholds.
The
resource
type
thresholds
can
be
changed
explicitly,
but
not
reset.
System
Action:
The
operation
fails.
User
Response:
Specify
a
resource
ID
and
try
the
operation
again.
The
ID
can
be
obtained
through
the
console
by
setting
the
Tooltips
of
the
Administrative
Preferences
and
hovering
over
the
resource
with
the
mouse.
See
the
appendix
in
the
IBM
Tivoli
Business
Systems
Manager
Command
Reference
for
information
about
the
XML
values.
See
the
IBM
Tivoli
Business
Systems
Manager
Administrator’s
Guide
for
information
about
Automated
Business
Systems.
GTMPR1009E
An
attempt
was
made
to
set
the
threshold
higher
than
999,999.
Explanation:
A
value
that
was
not
valid
was
specified
for
the
threshold
value.
System
Action:
The
operation
fails.
User
Response:
Specify
a
threshold
value
less
than
999999
and
try
the
operation
again.
See
the
appendix
in
the
IBM
Tivoli
Business
Systems
Manager
Command
Reference
for
information
about
the
XML
values.
See
the
IBM
Tivoli
Business
Systems
Manager
Administrator’s
Guide
for
information
about
Automated
Business
Systems.
234
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
Chapter
21.
Resource
Object
Data
Manager
Messages
-
GTMRO0100E
-
GTMRO0112E
The
following
messages
relate
to
the
Resource
Object
Data
Manager
(RODM).
These
messages
are
issued
by
the
component
of
Tivoli
Business
Systems
Manager
responsible
for
the
discovery
and
the
maintenance
of
RODM
resources.
GTMRO0100E
_LoadRODMDiscoveryBatch:
DiscoveryBatch
ID
id
is
not
valid.
Explanation:
The
ID
associated
with
the
bcp
file
that
was
downloaded
cannot
be
processed.
Message
Variables:
id
The
batch
ID
number
of
the
bcp
RODM
Discovery
file
attempted
to
be
processed
System
Action:
The
RODM
Discovery
Load
Job
failed.
Administrator
Response:
Check
the
DiscoveryBatch
table
for
the
batch
ID
and
determine
the
state
of
the
processing.
Verify
that
there
is
a
batch
ID
in
ENQUEUED
(pstat
value
of
0)
state.
You
might
have
to
run
the
RODM
Unload
Job
again
to
retrieve
another
bcp
RODM
file.
GTMRO0101E
_LoadRODMDiscoveryBatch:
Could
not
parse
filename
(OS
error
error_code),
aborting.
Explanation:
An
error
occurred
parsing
the
bcp
file
received
from
the
RODM
Unload
Job.
Message
Variables:
filename
The
bcp
filename
received
from
the
RODM
Unload
Job
error_code
The
error
code
returned
from
the
parseRODM
script
called
by
the
_LoadRODMDiscoveryBatch-stored
procedure
System
Action:
The
RODM
Discovery
Load
Job
failed.
Administrator
Response:
Check
the
DiscoveryBatch
table
for
the
batch
ID
and
filename
that
is
processed.
Verify
that
the
bcp
filename
that
is
being
processed
is
a
RODM
downloaded
file.
You
might
have
to
perform
the
RODM
Unload
Job
again
to
ensure
that
a
RODM
bcp
file
is
received.
GTMRO0102E
_LoadRODMDiscoveryBatch:
Error
loading
discovery
batch
file
filenameLink.dat
Explanation:
An
error
occurred
loading
the
link.dat
file
that
was
generated
by
the
parseRODM
script
into
the
Tivoli
Business
System
Manager
database.
Message
Variables:
filename
A
link
data
file
(link.dat)
that
is
created
by
the
parseRODM
script,
which
contains
the
RODM
Links
System
Action:
The
RODM
Discovery
Load
Job
failed.
Administrator
Response:
Collect
all
messages
generated
from
the
SQL
job
RODM
Discovery
Load
and
contact
IBM
Software
Support.
GTMRO0103E
_LoadRODMDiscoveryBatch:
Error
loading
discovery
batch
file
filenameObjValScalar.dat
Explanation:
An
error
occurred
loading
the
ObjValScalar.dat
file
that
was
generated
by
the
parseRODM
script
into
the
Tivoli
Business
Systems
Manager
database.
Message
Variables:
filename
An
object
value
data
file
(ObjValScalar.dat)
that
is
created
by
the
parseRODM
script,
which
contains
the
RODM
Resource
Value
data
System
Action:
The
RODM
Discovery
Load
Job
failed.
Administrator
Response:
Collect
all
messages
generated
from
the
RODM
Discovery
Load
Job
and
contact
IBM
Software
Support.
GTMRO0104E
_LoadRODMDiscoveryBatch:
Error
loading
discovery
batch
file
filenameObject.dat
Explanation:
An
error
occurred
loading
the
object.dat
file
that
was
generated
by
the
parseRODM
script
into
the
Tivoli
Business
Systems
Manager
database.
Message
Variables:
filename
An
object
data
file
(Object.dat)
that
is
created
by
the
parseRODM
script,
which
contains
the
RODM
Resources
System
Action:
The
RODM
Discovery
Load
Job
failed.
Administrator
Response:
Collect
all
messages
generated
from
the
RODM
Discovery
Load
Job
and
©
Copyright
IBM
Corp.
2000,
2004
235
contact
IBM
Software
Support.
GTMRO0105E
_LoadRODMDiscoveryBatch:
No
SNA/APPN
or
GMFHSAggregateFolder
resource
inserted.
Explanation:
The
RODM
Discovery
Load
SQL
job
was
run
before
having
inserted
the
SNA/APPN
Network
or
GMFHSAggregateFolder
resource
on
the
physical
tree.
System
Action:
The
RODM
Discovery
Load
Job
failed.
Administrator
Response:
Insert
a
SNA/APPN
Network
or
GMFHSAggregateFolder
resource.
The
RODM
Discovery
Load
and
Process
can
now
be
performed.
GTMRO0106W
_DiscoverRODMObjects:
Error
adding
links
based
on
RODMFieldLinkMap.
Explanation:
The
RODM
Discovery
Process
Job
failed
while
applying
the
links
to
the
Tivoli
Business
Systems
Manager
database.
System
Action:
The
RODM
Discovery
Process
Job
continues.
Administrator
Response:
Collect
all
messages
generated
from
the
RODM
Discovery
Process
Job
and
contact
IBM
Software
Support.
GTMRO0107W
_DiscoverRODMObjects:
Error
updating
links
based
on
RODMFieldLinkMap.
Explanation:
The
RODM
Discovery
Process
Job
failed
while
updating
the
links
to
the
Tivoli
Business
Systems
Manager
database.
System
Action:
The
RODM
Discovery
Process
Job
continues.
Administrator
Response:
Collect
all
messages
generated
from
the
RODM
Discovery
Process
Job
and
contact
IBM
Software
Support.
GTMRO0108W
RODM_object_discovery_backend:
Error
adding
RODMManagedObject
records.
Explanation:
The
RODMManagedObject
table
is
not
updated
in
the
Tivoli
Business
Systems
Manager
database.
System
Action:
The
RODM
Discovery
Process
Job
continues.
The
SNA/APPN
Network
or
GMFHSAggregateFolder
view
might
not
reflect
the
most
recent
discovery.
Administrator
Response:
Collect
all
messages
generated
from
the
RODM
Discovery
Process
Job
and
contact
IBM
Software
Support.
GTMRO0109W
RODM_object_discovery_backend:
Error
adding
top
level
links
for
cid.
Explanation:
The
links
that
are
to
be
established
from
the
networks
to
the
top-level
resources
did
not
get
updated
in
the
Tivoli
Business
Systems
Manager
database.
System
Action:
The
RODM
Discovery
Process
Job
continues.
The
SNA/APPN
Network
or
GMFHSAggregateFolder
view
might
not
reflect
the
most
recent
discovery.
Administrator
Response:
Collect
all
messages
generated
from
the
RODM
Discovery
Process
Job
and
contact
IBM
Software
Support.
GTMRO0110W
RODM_object_discovery_backend:
Error
adding
GMFF->GMFA
links
Explanation:
The
links
between
GMFF
and
GMFA
did
not
get
updated
in
the
Tivoli
Business
Systems
Manager
database.
System
Action:
The
RODM
Discovery
Process
Job
continues.
The
GMFHSAggregateFolder
view
might
not
reflect
the
most
recent
discovery.
Administrator
Response:
Collect
all
messages
generated
from
the
RODM
Discovery
Process
Job
and
contact
IBM
Software
Support.
GTMRO0111W
RODM_object_discovery_backend:
Error
inserting
RODMManagedLinks
Explanation:
The
RODMManagedLinks
table
is
not
updated
in
the
Tivoli
Business
Systems
Manager
database.
System
Action:
The
RODM
Discovery
Process
Job
continues.
The
SNA/APPN
Network
or
GMFHSAggregateFolder
view
might
not
reflect
the
most
recent
discovery.
Administrator
Response:
Collect
all
messages
generated
from
the
RODM
Discovery
Process
Job
and
contact
IBM
Software
Support.
GTMRO0112E
asisp_uploadGetRODMObjects:
Invalid
response
type:
response_type
Explanation:
The
response
type
used
is
not
supported.
The
supported
response
types
are
the
following:
0
Response
message
is
not
requested.
1
Exception
response
message
is
requested
to
be
returned
when
an
error
occurred
after
the
registration
process
completes.
2
Definite
response.
The
response
message
is
always
requested
to
be
returned
after
the
registration
process
completes.
Message
Variables:
236
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
response_type
The
response
type
that
generated
the
error
System
Action:
The
RODM
Discovery
Process
is
terminated.
The
SNA/APPN
Network
or
GMFHSAggregateFolder
views
are
updated.
The
new
discovered
resources
are
not
automatically
registered.
Administrator
Response:
Collect
all
messages
generated
from
the
RODM
Discovery
Process
Job
and
contact
IBM
Software
Support.
Chapter
21.
Resource
Object
Data
Manager
Messages
-
GTMRO0100E
-
GTMRO0112E
237
Chapter
22.
Unicenter
TNG
Messages
-
GTMIT0001E
-
GTMIT0005E
The
following
messages
relate
to
the
Unicenter
TNG
data
source.
These
messages
are
issued
by
the
component
of
Tivoli
Business
Systems
Manager
responsible
for
the
discovery
and
the
maintenance
of
Unicenter
TNG
resources.
GTMIT0001E
Discovery
process
initialization
failed
Explanation:
The
resource
discovery
process
could
not
start
because
the
communication
with
the
Common
Listener
or
with
Unicenter
TNG
could
not
be
established.
User
Response:
Ensure
that
the
database
server
is
active
and
all
port
numbers
have
been
set
correctly.
Start
the
process
again.
GTMIT0002E
Unable
to
get
an
instance
with
the
ID
instance_id
Explanation:
The
resource
discovery
process
was
unable
to
get
the
instance
from
Unicenter
TNG.
Message
Variables:
instance_id
-
The
wimtdiscovery
-id
command
User
Response:
Ensure
that
Unicenter
TNG
can
be
accessed,
and
that
the
database
server
is
active.
Use
the
wimtdiscovery
-id
command
to
discover
the
required
instance.
GTMIT0003E
Unable
to
send
an
instance
request
with
the
instance
ID
instance_id
Explanation:
The
resource
discovery
process
was
unable
to
send
the
instance
request
to
Common
Listener.
Message
Variables:
instance_id
-
The
wimtdiscovery
-id
command.
User
Response:
Ensure
that
the
communication
with
Common
Listener
is
set
correctly.
Use
the
wimtdiscovery
-id
command
to
discover
the
required
instance.
GTMIT0004E
Discovery
process
failed
Explanation:
The
resource
discovery
process
could
not
be
completed
successfully.
User
Response:
Ensure
that
you
have
enough
system
memory
and
that
all
port
numbers
have
been
set
correctly.
Also
the
database
server
must
be
active.
GTMIT0005E
Invalid
subnet
mask
was
specified
Explanation:
The
subnet
mask
you
have
specified
is
incorrect.
User
Response:
Specify
a
valid
subnet
mask.
©
Copyright
IBM
Corp.
2000,
2004
239
Chapter
23.
Utility
Messages
-
GTMTU1001E
-
GTMTU5336E
The
following
messages
are
issued
by
Tivoli
Business
Systems
Manager
utilities.
GTMTU1001E
Missing
required
parameter
parm
Explanation:
The
command
did
not
include
a
required
parameter.
No
further
processing
was
done.
Message
Variables:
parm
-
The
missing
option.
System
Action:
No
further
processing
was
performed
after
the
error
was
found.
User
Response:
Fix
the
error
and
run
the
command
again.
GTMTU1002W
The
XML
file
is
incorrect.
An
error
was
found
on
line
number
with
tag:
tag
Explanation:
While
reading
the
XML
file,
a
statement
was
found
that
was
not
valid.
The
line
in
error
has
been
included
in
the
message.
No
further
processing
was
done
on
the
file.
Message
Variables:
number
-
The
line
number
in
the
file
tag
-
The
erroneous
tag.
System
Action:
No
further
processing
was
performed
after
the
error
was
found.
User
Response:
Fix
the
error
and
run
the
command
again.
GTMTU1003E
The
XML
file
is
incorrect.
Required
information
parm
is
missing
at
line
number.
Explanation:
While
reading
the
XML
file,
a
statement
was
found
that
was
not
valid.
The
line
in
error
has
been
included
in
the
message.
No
further
processing
was
done
on
the
file.
Message
Variables:
parm
-
The
missing
option
number
-
The
line
number
in
the
file
System
Action:
No
further
processing
was
performed
after
the
error
was
found.
User
Response:
Fix
the
error
and
run
the
command
again.
GTMTU1004E
filename
does
not
exist.
Explanation:
The
specified
file
name
does
not
exist.
Message
Variables:
filename
-
The
name
of
the
file
System
Action:
No
further
processing
was
performed
after
the
error
was
found.
User
Response:
Fix
the
error
and
run
the
command
again.
GTMTU1006E
A
CID
does
not
exist
for
the
product/version
specified.
Explanation:
A
product
or
version
was
specified
that
was
not
valid.
System
Action:
The
operation
fails.
User
Response:
Specify
a
valid
product
and
version
and
try
the
operation
again.
The
product
and
version
is
the
name
of
a
Tivoli
software
component
product
associated
with
distributed
resources
that
have
dynamically-generated
Tivoli
Business
Systems
Manager
resource-type
identifiers
(also
known
as
CIDs).
Issue
the
following
command
for
the
current
list
of
valid
product
and
versions:
sh
gemgenprod.sh
-l
See
the
appendix
in
the
IBM
Tivoli
Business
Systems
Manager
Command
Reference
for
information
about
the
XML
values.
See
the
IBM
Tivoli
Business
Systems
Manager
Administrator’s
Guide
for
information
about
Automated
Business
Systems.
GTMTU1007W
Qualified
resource
path
resolved
to
non-Business
System
resource.
Explanation:
The
qualified
path
specification
resolved
to
a
non-business
system
resource
or
resources.
These
resources
are
ignored
for
the
operation.
The
operation
is
performed
only
on
the
business
system
resources.
System
Action:
The
operation
continues
for
the
business
system
resources.
User
Response:
Verify
the
operation
was
run
for
the
correct
business
system.
If
not,
try
the
operation
again
with
the
corrected
qualified
resource
path.
See
the
appendix
in
the
IBM
Tivoli
Business
Systems
Manager
Command
Reference
for
information
about
specifying
values
through
XML.
See
the
IBM
Tivoli
Business
Systems
Manager
Administrator’s
Guide
for
information
about
Automated
Business
Systems.
GTMTU1008E
Qualified
resource
path
resolved
to
multiple
resources.
Explanation:
The
qualified
path
specification
resolved
to
more
than
one
resource.
System
Action:
The
operation
fails.
©
Copyright
IBM
Corp.
2000,
2004
241
User
Response:
Specify
a
qualified
resource
path
that
resolves
uniquely
to
the
desired
resource
and
try
the
operation
again.
See
the
appendix
in
the
IBM
Tivoli
Business
Systems
Manager
Command
Reference
for
information
about
specifying
values
through
XML.
See
the
IBM
Tivoli
Business
Systems
Manager
Administrator’s
Guide
for
information
about
Automated
Business
Systems.
GTMTU1009E
A
CID
does
not
exist
for
the
feed
specified
instid.
Explanation:
The
specified
instid
did
not
resolve
to
a
Tivoli
Business
System
Manager
resource
type
identifier
(also
known
as
a
CID).
Message
Variables:
instid
-
The
feed-generated
(for
example,
common
listener
service)
resource
identifier
System
Action:
The
operation
fails.
User
Response:
Specify
an
instance
ID
that
resolves
uniquely
to
the
desired
resource
and
try
the
operation
again.
See
the
appendix
in
the
IBM
Tivoli
Business
Systems
Manager
Command
Reference
for
information
about
specifying
values
through
XML.
See
the
IBM
Tivoli
Business
Systems
Manager
Administrator’s
Guide
for
information
about
Automated
Business
Systems.
GTMTU1010E
A
CID
does
not
exist
for
the
class.
Explanation:
The
specified
classname
did
not
resolve
to
a
Tivoli
Business
System
Manager
resource
type
identifier
(also
known
as
a
CID).
Message
Variables:
class
-
The
class
name
that
was
not
recognized
System
Action:
The
operation
fails.
User
Response:
Specify
a
valid
class
and
try
the
operation
again.
See
the
appendix
in
the
IBM
Tivoli
Business
Systems
Manager
Command
Reference
for
information
about
specifying
values
through
XML.
See
the
IBM
Tivoli
Business
Systems
Manager
Administrator’s
Guide
for
information
about
Automated
Business
Systems.
GTMTU1011E
Qualified
resource
path
resolved
to
multiple
Business
System
resources.
Explanation:
The
qualified
path
specification
resolved
to
more
than
one
business
system
resource.
System
Action:
The
operation
fails.
User
Response:
Specify
a
resource
path
that
uniquely
identifies
the
business
system
you
want
and
try
the
operation
again.
See
the
appendix
in
the
IBM
Tivoli
Business
Systems
Manager
Command
Reference
for
information
about
specifying
values
through
XML.
See
the
IBM
Tivoli
Business
Systems
Manager
Administrator’s
Guide
for
information
about
Automated
Business
Systems.
GTMTU1012E
No
resources
for
the
qualified
resource
path
specified.
Explanation:
The
qualified
path
specification
did
not
resolve
to
any
resource.
System
Action:
The
operation
fails.
User
Response:
Specify
a
resource
path
that
uniquely
identifies
the
resource
you
want
and
try
the
operation
again.
See
the
appendix
in
the
IBM
Tivoli
Business
Systems
Manager
Command
Reference
for
information
about
specifying
values
through
XML.
See
the
IBM
Tivoli
Business
Systems
Manager
Administrator’s
Guide
for
information
about
Automated
Business
Systems.
GTMTU1015E
Data
type
mismatch.
Explanation:
The
data
type
did
not
match
the
method
parameter
data
type.
System
Action:
The
operation
fails.
User
Response:
Specify
the
appropriate
data
format,
string
or
integer,
based
on
the
method
definitions
and
issue
the
command
again.
Refer
to
the
appendix
in
the
IBM
Tivoli
Business
Systems
Manager
Command
Reference
for
information
about
the
method
parameters.
GTMTU1030E
Value
must
be
either
0
or
1.
Explanation:
The
value
specified
with
the
-a
parameter
of
the
setAlertStateChangeEvent.ksh
command
was
not
valid.
System
Action:
The
operation
fails.
User
Response:
Specify
a
value
of
0
or
1
and
retry
the
operation.
Refer
to
the
appendix
in
the
IBM
Tivoli
Business
Systems
Manager
Command
Reference
for
information
about
specifying
values
through
XML.
GTMTU1040E
The
specified
resource
is
either
not
in
the
database
or
has
been
deleted.
Explanation:
The
export
routine
could
not
find
the
requested
resource
in
the
database.
User
Response:
Verify
that
the
correct
CID
and
ID
were
entered
by
turning
on
the
console
tooltips
administrator
preference
CID
and
ID
and
hover
the
mouse
over
the
lines
of
business.
After
verifying
the
correct
values,
enter
the
command
again.
GTMTU1041E
One
of
two
errors
occurred.
Either
both
the
-c
and
the
-i
flags
were
not
specified,
or
an
invalid
value
was
specified
for
one
of
these
flags.
The
-c
flag
must
specify
″LOB″
and
the
-i
flag
cannot
specify
″0″
as
the
id.
Explanation:
A
syntax
error
occurred.
Incorrect
flags
or
values
were
specified.
242
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
User
Response:
Correct
the
syntax
and
enter
the
command
again.
GTMTU1042E
The
business
system
root
node
could
not
be
reached
for
LOB
name.
This
business
system
is
orphaned.
Explanation:
A
path
could
not
be
found
from
the
specified
business
system
to
the
top
of
the
business
systems
hierarchy.
Message
Variables:
name
-
The
name
of
the
business
system
Administrator
Response:
Contact
IBM
Customer
Support.
GTMTU1043E
Could
not
locate
enumeration
for
MNO2FlagValues.
Explanation:
An
internal
error
has
occurred.
Administrator
Response:
Contact
IBM
Customer
Support.
GTMTU1044E
Could
not
locate
enumeration
value
for
SendAlertStateChangeEvent.
Explanation:
An
internal
error
has
occurred.
Administrator
Response:
Contact
IBM
Customer
Support.
GTMTU1045E
Multiple
(amount)
Business
Systems
with
the
name
″name″
were
found.
Reissue
the
command
using
the
-c
and
-i
flags,
specifying
the
cid
and
id
from
the
list
below.
Explanation:
The
exportlobasxml
command
was
issued
with
the
-n
flag.
The
name
specified
is
not
a
unique
business
system
name.
The
messages
that
follow
this
one
list
each
of
the
business
systems
with
this
same
name,
along
with
their
associated
CID
and
ID.
Message
Variables:
amount
-
The
number
of
business
systems
found
with
the
duplicate
name
name
-
The
duplicated
business
system
name
User
Response:
Issue
the
command
again
with
the
-c
and
-i
flags
and
specify
the
CID
and
ID
for
the
appropriate
business
system.
GTMTU1046E
A
line
of
business
with
the
name
″name″
was
not
found.
Explanation:
The
exportlobasxml
command
was
issued
with
the
-n
flag.
The
name
specified
could
not
be
found
in
the
database.
Message
Variables:
name
-
The
name
of
the
business
system
that
could
not
be
located
User
Response:
Verify
the
name
of
the
business
system
and
issue
the
command
again
with
the
correct
business
system
name.
GTMTU1047I
CID:
cid
ID:
id
InstanceID:
instid
Explanation:
This
message
is
associated
with
message
number
GTMTU1045E.
The
CID,
ID,
and
the
instance
identifier
associated
with
the
named
business
system
are
displayed.
The
instance
identifier
usually
contains
the
business
system
hierarchy.
Message
Variables:
cid
-
The
class
identifier
of
the
business
system
id
-
The
ID
of
the
business
system
instid
-
The
instance
identifier
of
the
business
system
GTMTU1049W
The
following
Business
Systems
could
not
be
exported:
Explanation:
This
message
might
be
received
when
exporting
business
systems
using
the
exportlobasxml.sh
command.
It
indicates
that
some
business
systems
or
business
system
resources
could
not
be
exported
and
the
corresponding
list
is
printed
with
the
message.
Administrator
Response:
See
the
exportlobasxml.sh
in
the
IBM
Tivoli
Business
Systems
Manager
Command
Reference
for
more
details.
GTMTU5303E
Missing
required
parameter
-f
output_file_path
Explanation:
An
error
occurred
while
parsing
the
input
arguments.
The
-f
flag
was
missing.
Message
Variables:
output_file_path
-
The
value
to
be
specified
with
the
-f
flag
System
Action:
No
further
processing
was
performed.
User
Response:
Correct
the
syntax
of
the
command
and
run
it
again.
GTMTU5304E
Must
use
-c
and
-i
together
to
define
the
starting
resource.
Explanation:
An
error
occurred
while
parsing
the
input
arguments.
The
-c
and
-i
flags
must
be
used
together.
System
Action:
No
further
processing
was
performed.
User
Response:
Correct
the
command
syntax
and
run
the
command
again.
GTMTU5305E
The
-i
parameter
is
not
numeric.
Explanation:
An
error
occurred
while
parsing
the
input
arguments,
the
-i
flag
must
be
followed
by
a
numeric
value.
Chapter
23.
Utility
Messages
-
GTMTU1001E
-
GTMTU5336E
243
System
Action:
No
further
processing
was
performed.
User
Response:
Correct
the
command
syntax
and
run
the
command
again.
GTMTU5306I
Use
the
teceifconfig
script
to
set
the
value
associated
with
flag.
Run
teceifconfig
on
the
server
running
the
EIF
Sender
service
Explanation:
The
specified
flag
is
no
longer
valid
for
this
command.
This
flag
is
associated
with
either
migration
or
modification
of
the
EIF
configuration
files.
The
EIF
configuration
files
are
stored
on
the
server
running
the
EIF
Sender
service.
Message
Variables:
flag
-
The
name
of
the
command
option
User
Response:
Run
the
teceifconfig
command
on
the
EIF
Sender
service
server
to
modify
the
EIF
configuration
files.
GTMTU5307I
Use
the
teceifconfig
script
to
display
the
EIF
configuration
files.
The
command
teceifconfig
is
installed
on
the
server
running
the
EIF
Sender
service.
Explanation:
The
display
flag
on
the
tecstatusconfig
command
no
longer
displays
the
Tivoli
Enterprise
Console
EIF
configurations.
This
information
is
now
kept
on
the
server
running
the
EIF
Sender
service.
User
Response:
To
see
the
Tivoli
Enterprise
Console
EIF
configuration
information,
run
the
teceifconfig
command
from
the
server
running
the
EIF
Sender
service.
GTMTU5308I
The
files
were
migrated
previously.
No
action
was
taken.
Explanation:
The
EIF
configuration
files
have
already
been
migrated.
System
Action:
No
action
was
taken.
GTMTU5309E
Directory
name
was
not
found.
Migration
failed.
If
the
EIF
Sender
is
not
installed
on
the
SQL
server,
then
the
previous
configuration
files
cannot
be
migrated
and
will
need
to
be
redefined
using
teceifconfig.
Explanation:
The
directory
with
previous
configuration
files
cannot
be
found.
System
Action:
The
migration
request
fails.
Administrator
Response:
Install
the
EIF
Sender
on
the
same
server
as
the
SQL
server
to
enable
configuration
migration.
GTMTU5310I
Waiting:
status1
Processing:
status2
Tivoli
Enterprise
Console
Complete:
status3
User
Complete:
status4.
Waiting
are
records
available
but
not
yet
dequeued.
Processing
are
records
dequeued
and
being
processed.
Tivoli
Enterprise
Console
complete
have
been
sent
to
Tivoli
Enterprise
Console
and
are
waiting
user
exit
completion.
User
complete
are
records
waiting
to
be
sent
to
Tivoli
Enterprise
Console.
Explanation:
This
message
displays
statistical
information
associated
with
the
EIF
Sender
service
queues.
Message
Variables:
status1
—
status4
-
The
statistical
information
GTMTU5311E
Error
stopping
service
service.
Stop
the
service
and
rerun
the
script.
Explanation:
This
operation
requires
that
the
service
specified
by
service
be
stopped.
The
script
could
not
stop
the
service.
Message
Variables:
service
-
The
service
that
could
not
be
stopped
System
Action:
The
action
requested
is
not
performed.
Administrator
Response:
Stop
the
service
manually,
then
run
the
script
again.
GTMTU5312E
Error
starting
service
service.
Explanation:
This
operation
requires
that
the
service
specified
by
service
be
stopped.
The
script
stopped
the
service
successfully
and
performed
the
requested
action,
but
could
not
start
the
service
again.
Message
Variables:
service
-
The
service
that
could
not
be
started
System
Action:
The
action
requested
was
performed,
but
the
script
could
not
start
the
service
again.
Administrator
Response:
Start
the
service
manually.
GTMTU5313E
Migration
of
EIF
profiles
and
configuration
of
new
profiles
must
be
performed
on
the
server
running
the
EIF
Sender
service
Explanation:
The
Tivoli
Enterprise
Console
EIF
configuration
files
must
be
stored
on
the
server
running
the
EIF
Sender
service.
If
the
EIF
Sender
service
is
not
installed
on
the
SQL
server
and
Tivoli
Enterprise
Console
EIF
configuration
profiles
had
been
previously
defined
on
the
SQL
server
using
the
tecstatusconfig
command,
then
the
EIF
configurations
cannot
be
migrated
and
must
be
manually
entered
on
the
EIF
Sender
service
server
using
the
-t
flag
with
the
teceifconfig
command.
244
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
Administrator
Response:
Run
the
teceifconfig
command
again
on
the
EIF
Sender
service
server.
GTMTU5314I
Health
Monitor
setting
value1
has
been
updated
to
value2.
Explanation:
The
thresholds
for
the
Health
Monitor
have
been
updated.
These
values
take
effect
when
the
Health
Monitor
is
refreshed.
The
setting
and
its
value
are
substituted
for
value1
and
value2,
respectively
Message
Variables:
value1,
value2
-
The
setting
and
the
substituted
value
GTMTU5315E
The
warning
threshold
(value1)
state
must
be
less
than
the
severe
threshold
(value2).
Explanation:
The
warning
threshold
value
must
be
less
than
the
severe
threshold
value.
The
value
specified
on
the
command
line
is
provided
in
the
message
(either
warning
or
severe,
depending
on
the
command)
and
the
corresponding
setting
in
the
database
is
displayed.
Message
Variables:
value1,
value2
-
The
threshold
values
Administrator
Response:
Adjust
the
setting
and
submit
the
command
again.
GTMTU5316I
There
have
been
approximately
number
business
systems
deleted
since
the
time
of
the
last
backup.
Do
you
want
to
continue
with
the
restore
(specify
’1’
to
continue)?
Explanation:
Provides
an
estimate
as
to
the
number
of
business
systems
that
are
created
by
the
import.
This
is
an
estimate
based
on
the
creation
date
of
the
export
file.
System
Action:
Command
processing
is
suspended.
User
Response:
Specify
1
to
continue
with
the
import.
Any
other
response
stops
the
command
from
further
processing.
GTMTU5317I
Command
terminated.
Explanation:
The
value
of
1
was
not
used
in
response
to
the
GTMTU5318I
message.
System
Action:
Command
processing
ends.
GTMTU5318E
The
file
specified
with
the
-f
flag
could
not
be
found.
If
the
name
was
not
fully
qualified,
check
the
installdir/data/export
directory
to
validate
the
filename.
Explanation:
If
the
name
was
fully
qualified,
then
the
specified
flag
was
not
found.
If
the
value
was
a
file
name,
then
the
file
was
not
found
in
the
installdir/data/export
directory.
System
Action:
Command
processing
ends.
User
Response:
If
the
file
resides
in
another
directory,
use
the
-f
flag
to
specify
the
path
and
run
the
command
again.
GTMTU5319W
Unable
to
extract
the
date
from
the
export
file,
the
estimated
number
of
deleted
resources
may
be
inaccurate.
Explanation:
The
export
XML
file
typically
contains
the
date
when
the
file
was
created,
but
the
date
was
not
found
in
the
specified
file.
Therefore,
the
estimated
impact
to
the
system
is
not
accurate.
GTMTU5320W
The
request
timed
out
waiting
for
transaction
trans_id.
The
current
state
is
state.
Explanation:
While
the
system
was
waiting
for
the
import
transaction
to
complete,
the
specified
time
was
exceeded.
The
default
time
is
300
seconds.
Message
Variables:
trans_id
-
The
transaction
ID
state
-
The
last
known
state
System
Action:
Command
processing
ends.
User
Response:
To
resume
the
import
transaction,
issue
the
importlobfromxml
command
again
and
specify
the
-v
flag.
Specifying
a
value
of
-1
for
the
transaction
indicatea
that
the
last
transaction
attempted
should
be
used.
GTMTU5321E
The
request
failed
for
transaction
trans_id.
The
current
state
is
state.
Explanation:
The
import
request
failed.
The
verification
step
will
not
start.
Message
Variables:
trans_id
-
The
transaction
ID
state
-
The
current
state
System
Action:
Command
processing
ends.
User
Response:
Review
the
return
code
and
use
the
querycltran
command
to
query
additional
details,
using
the
indicated
trans_id.
GTMTU5322I
The
request
succeeded
for
transaction
trans_id.
The
current
state
is
state.
Explanation:
The
import
step
was
successful
and
the
verification
step
will
start.
Message
Variables:
trans_id
-
The
transaction
ID
state
-
The
current
state
System
Action:
Command
processing
continues.
Chapter
23.
Utility
Messages
-
GTMTU1001E
-
GTMTU5336E
245
GTMTU5323E
The
request
failed
for
transaction
trans_id
because
of
an
internal
error.
The
return
code
was
ret_code.
Explanation:
The
query
request
failed.
The
verification
step
will
not
start.
Message
Variables:
trans_id
-
The
transaction
ID
ret_code
-
The
return
code
received
from
the
query
request
System
Action:
Command
processing
ends.
User
Response:
Review
the
return
code
and
use
the
querycltran
command
to
query
additional
details,
using
the
indicated
trans_id.
GTMTU5324E
The
request
failed.
The
return
code
was
ret_code.
Explanation:
The
import
file
was
not
sent
to
the
Tivoli
Business
Systems
Manager
database
because
of
an
internal
error.
Message
Variables:
ret_code
-
The
return
code
received
from
the
query
request
System
Action:
Command
processing
ends.
User
Response:
Review
the
return
code
and
use
the
querycltran
command
to
query
additional
details.
GTMTU5325E
Invalid
value
specified
for
flag
flag.
Explanation:
The
value
specified
with
the
indicated
command
option
is
not
valid.
Message
Variables:
flag
-
The
name
of
the
command
option
System
Action:
No
further
processing
was
performed.
User
Response:
Select
a
valid
value
and
issue
the
command
again.
See
the
IBM
Tivoli
Business
Systems
Manager
Command
Reference
for
more
information.
GTMTU5326I
Configuration
file
for
’file’
has
been
deleted.
Explanation:
Confirms
that
the
specified
EIF
configuration
file
was
deleted.
Message
Variables:
file
-
The
name
of
the
EIF
configuration
file
GTMTU5327I
Configuration
file
for
’file’
was
not
found.
Explanation:
The
delete
request
failed.
The
indicated
EIF
configuration
file
was
not
found.
Message
Variables:
file
-
The
name
of
the
file
that
was
not
located
User
Response:
Verify
that
the
correct
host
name
was
specified.
Run
the
teceifconfig
command
using
the
-q
option
to
verify
that
the
configuration
file
exists.
GTMTU5328E
Configuration
file
file
already
exists,
this
is
a
fully
qualified
name
for
name.
Please
specify
the
fully
qualified
name
for
the
Tivoli
Enterprise
Console
server.
Explanation:
The
teceifconfig
command
was
issued
with
name
specified
for
the
-a
flag,
but
the
EIF
configuration
file
file
already
exists.
The
name
name
is
a
short
version
of
file,
which
implies
that
these
are
for
the
same
Tivoli
Enterprise
Console
server.
Message
Variables:
file
-
The
name
of
the
EIF
configuration
file
name
-
The
name
of
the
Tivoli
Enterprise
Console
server
System
Action:
No
further
processing
was
performed.
User
Response:
Issue
the
command
again
specifying
the
fully
qualified
host
name
for
the
Tivoli
Enterprise
Console
server.
GTMTU5330W
Port
numbers
cannot
be
updated
for
configuration
files
that
specify
multiple
servers.
Delete
the
configuration
and
then
add
a
new
configuration
with
the
new
ports.
Explanation:
You
can
only
configure
multiple
port
numbers
when
you
create
the
configuration
file
with
multiple
servers.
System
Action:
The
update
process
does
not
complete.
Administrator
Response:
Delete
the
configuration
file
using
the
-d
option.
Then
recreate
the
file
and
specify
the
multiple
servers
(using
the
-a
option)
and
the
ports
(using
the
-o
option).
GTMTU5331I
Checking
for
existing
configuration
files.
Explanation:
See
the
message
text.
System
Action:
Processing
continues.
GTMTU5332I
Using
file
name
Explanation:
The
indicated
file
is
being
used.
Message
Variables:
name
-
The
name
of
the
file
being
used
System
Action:
Processing
continues.
GTMTU5333I
Starting
validation
of
the
common
listener
cache.
Explanation:
Validation
of
the
common
listener
cache
started.
System
Action:
Processing
continues.
246
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
GTMTU5334I
Checking
the
state
of
the
transaction.
Explanation:
The
import
procedure
is
waiting
for
the
import
to
finish.
System
Action:
Processing
continues.
GTMTU5335E
The
-n
flag
cannot
be
used
with
the
-c
and
-i
flags.
Specify
either
a
name
or
the
cid/id
combination.
Explanation:
The
command
was
issued
with
both
the
-n
and
-c
flags.
These
flags
are
mutually
exclusive.
User
Response:
Issue
the
command
again
and
specify
either
the
-n
flag
or
the
-c
and
-i
flags.
GTMTU5336E
Either
the
-f
or
-m
flag
must
be
specified,
but
both
cannot
be
specified
at
the
same
time.
Explanation:
The
command
syntax
requires
either
the
-f
flag
or
the
-m
flag,
but
not
both.
User
Response:
Issue
the
command
again
specifying
either
the
-f
flag
if
an
export
of
a
business
system
is
being
requested,
or
the
-m
flag
if
configuration
information
is
required.
Chapter
23.
Utility
Messages
-
GTMTU1001E
-
GTMTU5336E
247
Chapter
24.
Web
Console
Messages
-
GTMWC1002I
-
GTMWC3088E
The
following
messages
are
generated
by
the
Tivoli
Business
Systems
Manager
Web
console.
All
of
the
message
information
in
this
chapter
can
also
be
viewed
directly
from
the
Web
console.
You
can
view
(and
search
on)
the
complete
list
of
Web
console
messages
including
explanation
text
by
clicking
the
Message
Index
icon
from
the
Task
Assistant
tool
bar.
GTMWC1002I
Problem
ticket
number
ticket_number
was
created.
Explanation:
A
new
problem
ticket
was
generated.
The
ticket
number
is
the
unique
identifier
associated
with
the
problem
ticket.
System
Action:
A
problem
ticket
was
created.
Console
processing
continues.
Operator
Response:
Click
OK
to
close
the
message.
GTMWC1003I
Problem
ticket
number
ticket_number
is
closed.
Explanation:
An
open
problem
ticket
was
closed.
GTMWC1004I
Problem
ticket
number
ticket_number
has
been
updated.
Explanation:
The
problem
ticket
was
successfully
updated
in
your
problem
management
system.
System
Action:
The
problem
ticket
was
updated.
Console
processing
continues.
Operator
Response:
Click
OK
to
close
the
message.
GTMWC1010I
The
preferences
have
been
saved.
Explanation:
The
preferences
were
saved.
GTMWC1011I
The
console
session
has
expired.
Explanation:
Console
sessions
expire
after
a
prolonged
period
of
inactivity.
GTMWC1019I
The
maximum
search
results
can
not
exceed
the
maximum
search
results
set
by
the
administrator.
Set
the
closest
maximum
value
value
within
the
administrator
defined
limit.
Explanation:
The
administrator
set
a
value
for
the
maximum
number
of
search
results
that
can
be
returned.
Operator
Response:
Change
the
selection
to
the
highest
value
within
the
administrator
defined
limit.
GTMWC1020I
Resource
resource
was
added
to
the
Critical
Watch
List.
Explanation:
This
message
verifies
that
the
resource
was
successfully
added
to
the
Critical
Watch
List.
GTMWC1022I
Resource
resource
was
removed
from
the
Critical
Watch
List.
Explanation:
This
message
verifies
that
the
resource
was
removed
from
the
Critical
Watch
List.
GTMWC2001W
The
filter
filter_name
already
exists.
Do
you
want
to
replace
it?
Explanation:
You
attempted
to
create
a
filter
using
a
duplicate
filter
name.
Before
the
filter
is
overwritten,
you
are
asked
to
confirm
that
you
want
to
replace
the
filter.
Operator
Response:
Click
Replace
to
replace
the
filter.
Click
Do
not
replace
to
keep
the
filter.
GTMWC2004W
Are
you
sure
you
want
to
delete
filter
filter_name?
Explanation:
You
attempted
to
delete
a
filter.
You
are
asked
to
confirm
the
deletion.
Operator
Response:
Click
Yes
to
delete
the
filter.
Click
No
to
keep
the
filter.
GTMWC2013W
The
filter
has
not
been
saved.
Are
you
sure
you
want
to
exit
now?
Explanation:
You
attempted
to
exit
without
saving
the
filter.
You
are
asked
to
confirm
that
you
want
to
exit
without
saving
the
filter.
Operator
Response:
Click
Exit
to
exit
without
saving
the
filter.
©
Copyright
IBM
Corp.
2000,
2004
249
GTMWC2014W
If
you
return
to
the
basic
filter
mode,
only
the
first
criteria
in
the
multiple
filter
criteria
table
will
be
kept
and
any
advanced
features
will
be
reset.
Do
you
want
to
continue?
Explanation:
You
attempted
to
return
to
the
basic
filter
criteria
page.
If
you
return
to
the
basic
filter
criteria
page,
only
the
first
criteria
in
the
multiple
filter
criteria
table
will
be
kept
and
the
other
entries
in
the
table
will
be
deleted.
Advanced
filter
features
will
be
reset
to
their
basic
values.
Operator
Response:
Click
Continue
to
use
the
basic
filter
mode.
Click
Do
not
continue
to
stay
with
the
advanced
filter
mode.
GTMWC2016W
The
preferences
have
not
been
saved.
Are
you
sure
you
want
to
exit
now?
Explanation:
You
attempted
to
exit
without
saving
the
preferences.
You
are
asked
to
confirm
that
you
want
to
exit
without
saving
the
preferences.
Operator
Response:
Click
Exit
to
exit
without
saving
the
preferences.
Click
Do
not
exit
to
continue
working
with
the
user
preference.
GTMWC2018W
The
portfolio
has
not
been
updated.
Are
you
sure
you
want
to
exit
now?
Explanation:
You
attempted
to
exit
without
applying
the
changes
you
made
to
the
portfolio.
You
are
asked
to
confirm
the
exit.
Operator
Response:
Click
Exit
to
exit
without
applying
your
changes.
GTMWC2020W
The
critical
watch
list
configuration
has
not
been
saved.
Are
you
sure
you
want
to
exit
now?
Explanation:
You
attempted
to
exit
the
critical
watch
list
configuration
without
saving
it.
You
are
being
asked
to
confirm
the
exit.
Operator
Response:
Click
Exit
to
exit
the
critical
watch
list
configuration
without
saving
it.
GTMWC2021W
More
results
were
found
(
num_results
)
than
could
be
returned.
Explanation:
You
ran
a
filter
that
found
more
results
than
could
be
returned.
You
can
set
the
maximum
number
of
results
that
can
be
returned
in
your
user
preferences.
Operator
Response:
If
this
is
a
filter
you
created,
you
can
edit
the
filter
and
change
the
filter
criteria
to
be
more
selective.
Or
you
can
change
the
setting
in
your
user
preferences
to
increase
the
maximum
returns.
To
do
this,
go
to
View
Miscellaneous
->
User
Preferences
->
Maximum
Returns.
However,
a
console
administrator
can
configure
a
limit
that
could
override
the
setting
that
you
configure.
Administrator
Response:
You
can
configure
a
limit
that
overrides
maximum
returns
by
changing
the
number
in
the
Current
column
for
Search
Results
on
the
Configuration
page
of
Administrator
Preferences
in
the
console
(not
the
Web
console).
To
do
this,
go
to
the
console
and
select
Console
->
Administrator
Preferences
->
Configuration.
GTMWC2022W
Are
you
sure
you
want
to
cancel
setting
up
the
problem
ticket
connection?
Explanation:
This
message
is
to
verify
that
you
want
to
cancel
setting
up
the
problem
ticket
connection.
Operator
Response:
Select
Cancel
to
cancel
setting
up
the
problem
ticket
connection.
Select
Do
not
cancel
to
continue
setting
up
the
problem
ticket
connection.
GTMWC2023W
Are
you
sure
you
want
to
cancel
working
on
this
problem
ticket?
Explanation:
This
message
is
to
verify
that
you
want
to
cancel
working
on
this
problem
ticket.
Operator
Response:
Select
Cancel
to
cancel
working
on
this
problem
ticket.
Select
Do
not
cancel
to
continue
working
on
this
problem
ticket.
GTMWC2024W
Are
you
sure
you
want
to
cancel
working
on
this
note?
Explanation:
This
message
is
to
verify
that
you
want
to
cancel
working
on
this
note.
Operator
Response:
Select
Cancel
to
cancel
working
on
this
note.
Select
Do
not
cancel
to
continue
working
on
this
note.
GTMWC2025W
Some
filters
are
no
longer
available.
Click
the
Configure
Watch
List
button
to
reconfigure
filters.
Explanation:
Some
filters
are
unavailable
either
because
they
were
deleted
or
because
you
no
longer
have
access
to
the
filters.
GTMWC2026W
Changes
you
made
to
the
filter
criteria
affect
the
selected
columns
in
the
Columns
step.
One
or
more
of
the
selected
columns
is
no
longer
valid
and
will
be
removed
if
you
continue.
Do
you
want
to
continue?
Explanation:
Some
resource
types
support
resource-specific
columns.
If
you
previously
selected
one
or
more
resource-specific
columns
and
then
changed
the
resource
type
in
the
filter
criteria,
these
250
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
columns
are
no
longer
valid.
If
you
continue,
the
resource-specific
columns
will
be
removed
from
your
list
of
Selected
Columns
in
the
Columns
step.
Operator
Response:
Select
Continue
to
remove
the
resource-specific
columns.
Select
Do
not
continue
to
keep
your
current
list
of
selected
columns.
GTMWC2027W
The
new
owner
might
not
be
able
to
view
this
resource.
Do
you
want
to
continue?
Explanation:
The
user
you
are
assigning
this
note
to
might
not
have
access
to
the
resource
that
is
associated
with
this
note.
System
Action:
If
you
select
Continue
the
note
is
assigned
to
the
new
owner.
Operator
Response:
Select
Continue
to
assign
the
note
to
the
new
owner.
Administrator
Response:
This
message
occurs
when
a
user
attempts
to
transfer
ownership
of
a
note
to
an
operator
who
might
not
have
access
to
the
resource.
GTMWC2028W
More
results
were
found
(num_found)
from
filter
filter
than
could
be
returned.
Explanation:
Your
critical
watch
list
ran
a
filter
that
found
more
results
than
could
be
returned.
You
can
configure
the
maximum
number
of
results
that
can
be
returned
in
your
user
preferences.
However,
a
console
administrator
can
set
a
maximum
for
returns
that
could
override
the
setting
that
you
configure.
Operator
Response:
If
this
is
a
filter
you
created,
you
can
edit
the
filter
and
change
the
filter
criteria
to
be
more
selective.
Or
you
can
change
the
setting
in
your
user
preferences
to
increase
the
maximum
returns.
GTMWC2029W
Take
ownership
complete:
num_events
event(s)
were
already
owned
or
cleared.
Explanation:
Your
request
to
take
ownership
completed.
You
took
ownership
of
events
that
were
not
owned.
However,
one
or
more
of
the
events
were
already
owned
or
were
cleared
by
another
user.
Operator
Response:
Another
user
processed
one
or
more
of
the
events
you
attempted
to
take
ownership
of.
Refresh
your
view
to
see
an
updated
list
of
resources
or
events.
GTMWC2030W
More
notes
were
found
(
num_notes
)
than
could
be
returned.
Explanation:
Your
request
to
view
notes
found
more
notes
than
could
be
returned.
Operator
Response:
The
console
administrator
configures
the
maximum
number
of
notes
that
can
be
returned.
If
this
limit
was
reached
from
View
My
Notes,
the
administrator
might
have
to
increase
the
maximum
returns
for
notes.
If
this
limit
was
reached
from
View
All
Notes,
you
can
change
the
search
criteria
to
be
more
selective.
GTMWC3000E
An
internal
error
occurred.
Explanation:
Your
request
could
not
be
completed
because
of
an
internal
error.
Operator
Response:
Close
the
task
and
try
the
task
again.
If
the
problem
persists,
contact
the
administrator.
Administrator
Response:
This
error
may
indicate
a
problem
with
the
connection
to
the
IBM
Tivoli
Business
Systems
Manager
database.
If
the
problem
occurs
intermittently
during
operation,
it
could
be
because
of
network
traffic
or
an
intermittent
network
problem.
If
the
problem
appears
to
be
related
to
a
specific
operation,
contact
Tivoli
Customer
Support
and
describe
the
situation
leading
up
to
the
error.
GTMWC3001E
A
value
must
be
entered
for
the
Filter
Name.
Explanation:
You
attempted
to
proceed
without
a
filter
name.
Enter
a
filter
name
before
continuing.
Operator
Response:
Enter
a
filter
name
and
then
retry
the
request.
GTMWC3002E
Authentication
failed.
The
user
ID
or
password
could
have
been
entered
incorrectly
or
misspelled.
Explanation:
Authentication
failed
because:
v
The
user
ID
or
password
might
have
been
entered
incorrectly
or
be
misspelled.
v
The
user
ID
might
not
exist.
v
The
account
could
have
expired
or
it
could
have
been
disabled.
v
The
password
could
have
expired.
Operator
Response:
Enter
a
valid
user
ID
and
password.
GTMWC3004E
The
requested
filter
was
not
found.
Explanation:
The
filter
was
either
deleted
or
you
no
longer
have
access
to
the
filter.
All
references
to
this
filter
will
be
removed
from
your
portfolio.
Operator
Response:
If
this
filter
was
deleted
in
error
or
you
need
access
to
it,
see
your
administrator.
GTMWC3010E
Values
were
not
entered
or
selected
for
Filter
Criteria.
Explanation:
You
attempted
to
proceed
without
entering
filter
criteria.
Type
or
select
at
least
one
value
before
proceeding.
Chapter
24.
Web
Console
Messages
-
GTMWC1002I
-
GTMWC3088E
251
Operator
Response:
Enter
or
select
one
or
more
filter
criteria
values
and
try
the
request
again.
GTMWC3011E
Criteria
must
be
added
to
the
Criteria
Table
before
proceeding.
Explanation:
At
least
one
filter
criteria
must
be
added
to
the
filter
criteria
table
before
proceeding.
Operator
Response:
Click
Create
to
add
filter
criteria.
GTMWC3012E
The
bootstrap
process
for
the
IBM
Tivoli
Business
Systems
Manager
Web
console
failed.
Some
parts
of
the
console
might
not
function
correctly.
Please
contact
the
administrator
to
report
this
problem.
Explanation:
The
startup
process
for
the
IBM
Tivoli
Business
Systems
Manager
Web
console
failed.
Operator
Response:
Contact
the
administrator
Administrator
Response:
Check
the
Web
application
server
message
logs.
GTMWC3015E
The
value
for
field_name
must
be
a
number
between
1
and
32767.
Explanation:
The
value
you
entered
is
not
a
number
between
1
and
32767.
Operator
Response:
Change
the
value
to
a
valid
number
and
try
the
request
again.
GTMWC3019E
The
event
time
condition
is
not
valid.
Confirm
that
all
three
time
condition
values
are
specified.
Explanation:
You
attempted
to
proceed
with
a
time
condition
that
is
not
valid.
A
valid
time
condition
must
be
entered
before
continuing.
Operator
Response:
Enter
values
in
all
three
time
condition
fields
and
then
try
the
request
again.
GTMWC3031W
Remarks
could
not
be
added
to
one
or
more
of
the
selected
notes.
The
notes
were
transferred
to
another
user.
Explanation:
Another
user
transferred
one
or
more
of
the
notes
you
were
trying
to
add
remarks
to.
Operator
Response:
Refresh
your
notes
view
to
see
an
updated
list
of
your
notes.
GTMWC3032W
One
or
more
of
the
selected
notes
could
not
be
transferred.
The
notes
were
either
closed
or
transferred
to
another
user.
Explanation:
Another
user
changed
one
or
more
of
the
notes
you
attempted
to
transfer.
The
notes
were
either
closed
or
transferred
to
someone
else.
Operator
Response:
Refresh
your
notes
view
to
see
an
updated
list
of
your
notes.
GTMWC3033W
One
or
more
of
the
selected
events
could
not
be
closed
out.
These
events
are
either
already
closed
or
are
owned
by
another
user.
Explanation:
Another
user
closed
or
took
ownership
of
one
or
more
of
the
events
you
attempted
to
close.
Operator
Response:
Refresh
your
events
view
to
see
an
updated
list
of
events.
GTMWC3035E
An
internal
error
occurred
reloading
the
problem
ticket
notebook.
Explanation:
An
internal
error
occurred
while
the
problem
ticket
notebook
was
reloading.
The
error
could
be
caused
by
a
connection
problem
with
the
problem
management
system.
Operator
Response:
Try
the
operation
again.
If
the
problem
persists,
contact
your
administrator.
Administrator
Response:
Verify
that
the
problem
management
system
is
running
and
that
a
connection
exists
between
the
console
server
and
the
problem
management
system.
GTMWC3037E
A
starting
point
resource
must
be
selected
before
proceeding
to
the
next
step.
Explanation:
You
attempted
to
proceed
without
a
starting
point
resource.
You
must
select
a
starting
point
resource
before
proceeding
to
the
next
step.
Operator
Response:
Click
Browse
and
select
a
starting
point
resource
and
then
try
the
request
again.
GTMWC3038E
A
starting
point
resource
must
be
selected.
Explanation:
You
clicked
OK
without
first
selecting
a
starting
point
resource.
Operator
Response:
Select
a
starting
point
resource
and
then
click
OK.
GTMWC3040E
An
error
occurred
communicating
with
the
IBM
Tivoli
Business
Systems
Manager
console
server.
Explanation:
An
error
occurred
communicating
with
the
IBM
Tivoli
Business
Systems
Manager
console
server.
Operator
Response:
Try
the
operation
again.
If
the
problem
persists,
contact
the
administrator.
Administrator
Response:
This
error
may
indicate
a
252
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
problem
with
the
connection
to
the
IBM
Tivoli
Business
Systems
Manager
database.
If
the
problem
occurs
intermittently
during
operation,
it
could
be
because
of
network
traffic
or
an
intermittent
network
problem.
If
the
problem
appears
to
be
related
to
a
specific
operation,
contact
Tivoli
Customer
Support
and
describe
the
situation
leading
up
to
the
error.
GTMWC3048E
There
is
an
authorization
problem
with
the
access
information
you
entered.
Enter
a
user
ID
and
password
that
are
authorized
to
perform
the
requested
task
in
NetView.
The
return
code
is:
specific_error
Explanation:
The
NetView
user
ID
and
password
you
entered
are
valid,
but
the
task
is
not
able
to
complete
because
the
user
ID
and
password
do
not
have
the
necessary
level
of
authorization.
System
Action:
The
create
or
update
action
does
not
proceed
because
there
is
a
problem
with
the
access
information.
The
prompt
window
for
NetView
access
information
is
displayed
again.
Operator
Response:
Enter
a
different
valid
user
ID
and
password
and
try
the
operation
again.
If
the
problem
persists,
have
the
administrator
verify
that
the
user
ID
and
password
you
entered
have
the
necessary
level
of
authorization.
Administrator
Response:
Verify
that
the
operator
is
entering
a
valid
user
ID
and
password
that
have
the
necessary
level
of
authorization.
GTMWC3049E
Your
access
information
cannot
be
validated
because
the
connection
to
NetView
appears
to
be
down.
Verify
that
the
NetView
connection
is
active
and
retry
the
operation.
Explanation:
The
access
information
entered
cannot
be
validated
because
of
a
connection
problem.
System
Action:
The
create
or
update
action
does
not
proceed
because
the
access
information
cannot
be
validated.
The
prompt
window
for
NetView
access
information
is
displayed
again.
Operator
Response:
Have
the
administrator
establish
the
NetView
connection
and
enter
your
access
information
and
attempt
the
operation
again.
If
the
problem
persists,
contact
the
administrator.
Administrator
Response:
Verify
that
the
NetView
connection
is
active.
GTMWC3050E
A
failure
occurred
validating
the
problem
ticket
access
information.
The
return
code
is:
specific_error
Explanation:
The
NetView
access
information
that
was
entered
could
not
be
validated
because
of
a
system
or
connection
problem.
System
Action:
The
create
or
update
action
does
not
proceed
because
the
access
information
cannot
be
validated.
The
prompt
window
for
NetView
access
information
is
displayed
again.
Operator
Response:
Enter
your
access
information
and
attempt
the
operation
again.
If
the
problem
persists,
notify
the
administrator
and
provide
the
specific
return
code
if
it
is
available.
Administrator
Response:
Verify
that
a
NetView
connection
still
exists
and
is
working.
GTMWC3051E
The
problem
ticket
access
information
entered
is
not
valid.
Enter
a
user
ID
and
password
that
are
authorized
to
access
NetView.
Explanation:
The
access
information
entered
does
not
have
the
required
level
of
authorization
to
access
NetView.
System
Action:
The
create
or
update
action
does
not
proceed
because
the
access
information
is
not
valid.
The
prompt
window
for
NetView
access
information
is
displayed
again.
Operator
Response:
Enter
a
valid
user
ID
and
password
and
attempt
the
operation
again.
If
the
problem
persists,
contact
the
administrator
to
verify
that
your
user
ID
and
password
have
the
necessary
level
of
authorization
for
accessing
NetView.
Administrator
Response:
Verify
that
the
operator
is
entering
a
valid
user
ID
and
password
for
accessing
NetView.
GTMWC3052E
The
access
information
entered
is
not
valid.
Enter
a
user
ID
and
password
that
are
authorized
to
access
the
problem
ticket
system.
Explanation:
You
entered
access
information,
but
the
user
ID
and
password
are
not
valid.
System
Action:
The
create
or
update
action
does
not
proceed
because
the
access
information
is
not
valid.
The
prompt
window
for
problem
ticket
system
access
information
is
displayed
again.
Operator
Response:
Enter
a
valid
user
ID
and
password
then
attempt
the
operation
again.
If
the
problem
persists,
contact
the
administrator
to
verify
that
your
user
ID
and
password
are
correct
for
accessing
the
problem
ticket
system.
Administrator
Response:
Verify
that
the
operator
is
entering
a
valid
user
ID
and
password
for
accessing
the
problem
ticket
system.
Chapter
24.
Web
Console
Messages
-
GTMWC1002I
-
GTMWC3088E
253
GTMWC3060E
Filter
criteria
must
be
selected
before
you
can
perform
that
action.
Explanation:
This
action
requires
that
you
select
filter
criteria.
Operator
Response:
Select
a
filter
criteria
and
retry
the
request.
GTMWC3061E
At
least
one
column
must
be
selected
before
you
can
continue.
Explanation:
No
columns
are
selected
for
the
filter.
Select
at
least
one
column
before
continuing.
Operator
Response:
Add
at
least
one
column
to
the
Selected
Columns
before
continuing.
GTMWC3062E
You
are
not
authorized
to
run
the
action_name
action
against
the
selected
item
number
sel_row.
Explanation:
You
must
log
in
with
the
appropriate
authorization
to
run
this
action
against
this
item.
Operator
Response:
If
you
need
to
perform
this
action,
contact
your
administrator
to
get
the
appropriate
authorization.
GTMWC3063E
You
selected
actual_sels
items.
You
need
to
select
needed_sels
to
run
the
action_name.
Explanation:
Each
action
requires
that
a
certain
number
of
items
be
selected.
You
have
not
selected
an
appropriate
number
of
items.
Operator
Response:
Select
an
appropriate
number
of
items
and
retry
the
action.
GTMWC3064E
Because
you
are
not
authorized
to
run
the
action_name
action
against
some
of
the
selected
items,
the
action
did
not
run
against
any
of
the
selected
items.
Explanation:
You
can
run
the
action
against
the
selected
items
if
you
have
authorization
to
run
the
action
against
all
of
the
items
that
are
selected.
Operator
Response:
Deselect
any
items
that
you
are
not
authorized
to
run
actions
against
and
run
the
action
again.
GTMWC3065E
An
error
occurred
attempting
to
run
the
action_name
action
against
the
selected
item
number
sel_row.
Explanation:
An
error
occurred
communicating
with
the
IBM
Tivoli
Business
Systems
Manager
console
server.
Operator
Response:
Try
the
operation
again.
If
the
problem
persists,
contact
the
administrator.
Administrator
Response:
This
error
may
indicate
a
problem
with
the
connection
to
the
IBM
Tivoli
Business
Systems
Manager
database.
If
the
problem
occurs
intermittently
during
operation,
it
might
be
because
of
network
traffic
or
an
intermittent
network
problem.
If
the
problem
appears
to
be
related
to
a
specific
operation,
contact
Tivoli
Customer
Support
and
describe
the
situation
leading
up
to
the
error.
GTMWC3066E
An
error
occurred
attempting
to
create
a
problem
ticket.
Explanation:
The
console
server
encountered
an
error
while
trying
to
create
a
problem
ticket
and
the
user
canceled
without
fixing
the
error.
The
problem
ticket
system
is
unavailable
until
this
issue
is
resolved.
Operator
Response:
Try
the
operation
again.
If
the
problem
persists,
contact
the
administrator.
Administrator
Response:
Use
the
Problem
Preference
page
and
associated
messages
to
help
determine
the
source
of
this
problem.
GTMWC3068E
Problem
ticket
creation
failed.
specific_error
Explanation:
You
attempted
to
create
a
problem
ticket,
but
it
did
not
complete
successfully.
System
Action:
A
problem
ticket
was
not
created
and
the
failure
was
reported.
Operator
Response:
Verify
that
you
have
supplied
information
and
made
selections
for
all
necessary
fields.
Make
any
corrections
indicated
in
the
text
of
the
message
and
attempt
to
create
the
problem
ticket
again.
If
the
problem
persists,
notify
the
administrator.
Administrator
Response:
Verify
that
the
operator
is
supplying
valid
information
for
all
fields
required
by
the
problem
management
system.
Verify
that
a
valid
user
name
and
password
for
the
problem
system
are
being
used.
Also,
verify
that
the
problem
system
is
running
and
that
a
connection
exists
between
the
console
and
the
problem
management
system.
For
additional
information,
see
the
IBM
Tivoli
Business
Systems
Manager
Problem
and
Change
Management
Integration
Guide.
GTMWC3069E
An
error
occurred
attempting
to
update
a
problem
ticket.
Explanation:
The
console
server
encountered
an
error
while
trying
to
update
a
problem
ticket.
This
failure
was
noted
by
the
problem
ticket
editor
and
the
user
canceled
without
fixing
the
error.
Problem
ticket
creation
will
fail
until
this
issue
is
resolved.
Operator
Response:
Try
the
operation
again.
If
the
problem
persists,
contact
the
administrator.
Administrator
Response:
Use
the
problem
ticket
254
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
editor
and
associated
messages
to
help
determine
the
source
of
this
problem.
GTMWC3071E
Problem
ticket
update
failed.
specific_error
Explanation:
You
attempted
to
update
or
close
a
problem
ticket,
but
this
action
was
unable
to
complete
successfully.
System
Action:
The
problem
ticket
was
not
updated
and
the
failure
was
reported.
Operator
Response:
Verify
that
you
have
supplied
information
and
made
selections
for
all
necessary
fields.
Make
any
corrections
indicated
in
the
text
of
the
message
and
attempt
to
update
or
close
the
problem
ticket
again.
If
the
problem
persists,
notify
the
administrator.
Administrator
Response:
Verify
that
the
operator
is
supplying
valid
information
for
all
fields
required
by
your
problem
management
system.
If
pertinent,
verify
that
a
valid
user
name
and
password
for
the
problem
management
system
are
being
used.
Also,
verify
that
the
problem
management
system
is
running
and
that
a
connection
exists
between
the
console
and
the
problem
management
system.
GTMWC3073E
You
are
not
authorized
to
access
the
IBM
Tivoli
Business
Systems
Manager
Web
console.
Explanation:
The
role
assigned
to
this
user
does
not
have
access
to
the
IBM
Tivoli
Business
Systems
Manager
Web
console.
Administrator
Response:
Use
the
WebSphere
Administrative
console
to
assign
an
appropriate
role
to
this
user
for
accessing
the
IBM
Tivoli
Business
Systems
Manager
Web
console.
GTMWC3074E
A
value
must
be
entered
for
the
search
string.
Explanation:
You
attempted
to
search
for
groups
without
entering
a
search
string.
Enter
a
search
string
before
continuing.
For
example,
enter
TBSM*
to
search
for
all
groups
that
begin
with
TBSM.
Operator
Response:
Enter
a
search
string
and
then
retry
the
request.
GTMWC3075E
A
task
identifier
was
not
provided
in
the
request
path.
Explanation:
The
HTTP
request
did
not
include
a
task
identifier.
Administrator
Response:
A
task
identifier
was
not
supplied
with
the
request.
Ensure
that
the
launching
application
is
configured
correctly
to
launch
into
the
IBM
Tivoli
Business
Systems
Manager
Web
console.
GTMWC3076E
The
task
identifier
taskID
is
not
recognized.
Explanation:
The
task
identifier
that
was
specified
is
not
supported.
Administrator
Response:
The
IBM
Tivoli
Business
Systems
Manager
Web
console
does
not
support
the
specified
task
identifier.
GTMWC3077E
You
are
not
authorized
to
launch
the
task
taskID.
Explanation:
You
attempted
a
task
that
you
are
not
authorized
to
do.
Administrator
Response:
The
IBM
Tivoli
Business
Systems
Manager
Web
console
blocked
access
to
the
task
because
the
user
is
not
authorized
to
perform
it.
If
appropriate,
assign
the
user
a
role
that
is
authorized
to
run
the
task.
GTMWC3078E
Configuration
of
the
console
failed.
Explanation:
The
console
configuration
failed
because
of
a
parsing
error.
GTMWC3079E
Search
criteria
is
not
valid.
Search
strings
that
are
empty
or
contain
only
wildcards
are
valid
only
when
specific
resource
types
are
selected.
Explanation:
When
no
resource
types
are
selected,
the
search
string
must
include
characters
that
are
not
wildcards.
System
Action:
The
search
does
not
take
place.
Operator
Response:
Type
a
search
string
that
includes
non-wildcard
characters
in
the
search
field,
or
select
specific
resource
types.
Administrator
Response:
This
message
occurs
when
no
resource
types
are
selected
and
only
wildcards
are
entered
in
the
search
field.
Instruct
the
operator
to
either
select
specific
resource
types
or
type
a
search
string
that
includes
non-wildcard
characters
in
the
search
field.
GTMWC3080E
Too
many
columns
are
selected.
At
most
max_col_names
can
be
selected.
Explanation:
Too
many
columns
are
selected.
Remove
columns
from
the
Selected
Columns
list
so
that
the
total
number
of
selected
columns
does
not
exceed
the
maximum
allowed.
Operator
Response:
Remove
one
or
more
columns
from
the
Selected
Columns
list
before
continuing.
Chapter
24.
Web
Console
Messages
-
GTMWC1002I
-
GTMWC3088E
255
GTMWC3081E
A
minimum
of
one
event
must
be
selected
to
create
an
ownership
note.
Explanation:
No
events
are
selected
in
the
event
table.
To
proceed,
select
at
least
one
event.
Operator
Response:
Select
at
least
one
event
from
the
table
to
proceed.
GTMWC3082E
A
value
must
be
entered
for
the
Remark.
Explanation:
You
attempted
to
proceed
without
entering
a
Remark.
Enter
a
Remark
before
continuing.
Operator
Response:
Enter
a
Remark
and
then
try
the
request
again.
GTMWC3083E
The
value
entered
for
the
Remark
is
too
long.
The
Remark
cannot
exceed
max_remark_length
characters.
Explanation:
The
Remark
you
entered
is
too
long.
Shorten
the
remark
text
so
that
it
does
not
exceed
the
maximum
length.
Operator
Response:
Shorten
the
remark
text
and
then
retry
the
request.
GTMWC3084E
The
value
entered
for
the
Description
is
too
long.
The
description
cannot
exceed
max_description_length
characters.
Explanation:
The
description
you
entered
is
too
long.
Shorten
the
description
text
so
that
it
does
not
exceed
the
maximum
length.
Operator
Response:
Shorten
the
description
text
and
then
retry
the
request.
GTMWC3085E
The
value
entered
for
the
Resolution
is
too
long.
The
resolution
cannot
exceed
max_resolution_length
characters.
Explanation:
The
resolution
you
entered
is
too
long.
Shorten
the
resolution
text
so
that
it
does
not
exceed
the
maximum
length.
Operator
Response:
Shorten
the
resolution
text
and
then
retry
the
request.
GTMWC3086E
This
note
could
not
be
changed
because
it
was
either
closed
or
transferred
to
another
user.
Explanation:
The
note
was
either
closed
or
transferred
to
another
user.
Operator
Response:
To
see
an
updated
list
of
your
notes,
Refresh
the
view.
GTMWC3087E
The
filter
filter_name
already
exists.
Explanation:
You
changed
the
name
of
the
filter.
However,
a
filter
with
this
name
already
exists.
Operator
Response:
Duplicate
names
are
not
allowed.
Change
the
name
of
the
filter
to
a
unique
name.
GTMWC3088E
The
filter
filter_name
no
longer
exists.
Explanation:
Another
user
deleted
the
filter.
Operator
Response:
If
this
filter
was
deleted
in
error,
see
your
administrator.
256
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
Chapter
25.
WebSphere
for
OS/390
Messages
-
GTMWS001E
-
GTMWS008E
The
following
messages
relate
to
the
WebSphere
for
z/OS
data
source.
These
messages
are
issued
by
the
component
of
Tivoli
Business
Systems
Manager
responsible
for
the
discovery
and
the
maintenance
of
WebSphere
for
z/OS
resources.
GTMWS001E
WebSphere
Complexes
are
not
configured
Explanation:
The
WebSphere
Complexes
table
is
empty.
System
Action:
The
dynamic
create
process
is
stopped
and
no
resources
are
created.
User
Response:
Create
the
WebSphere
Complexes
business
system
and
configure
at
least
one
operating
system.
GTMWS002E
WebSphere
Complexes
are
not
associated
with
any
operating
system
Explanation:
No
match
exists
in
WebSphere
Complexes
table
for
the
target
operating
system
resource
that
is
processing
the
server
startup
message.
System
Action:
The
dynamic
create
process
is
ended
and
no
resources
are
created.
User
Response:
Drag
and
drop
the
target
operating
system
resource
into
the
corresponding
WebSphere
business
system.
GTMWS003E
WebSphere
Object
Name
length
is
invalid
Explanation:
The
object
name
for
the
target
console
server
instance
does
not
meet
the
required
criteria.
A
server
instance
name
includes
the
parent
server
name
and
one
extra
character
appended
to
it.
System
Action:
The
link
method
is
ended
and
no
link
is
created
for
the
target
console
server
instance.
User
Response:
Name
the
target
console
server
instance
to
meet
the
above
criteria.
GTMWS004E
link_type
Link
failed,
WebSphere
ID
wbs_id
is
invalid
Explanation:
The
target
server
resource
cannot
be
found
because
the
WebSphere
ID
in
the
WebSphere
Complexes
table
was
not
valid.
Message
Variables:
link_type
-
The
target
link
type
wbs_id
-
The
target
WebSphere
ID.
Valid
value
are
as
follows:
v
DNIL
–
the
link
between
the
Daemon
and
its
instance
v
NMIL
–
the
link
between
the
Naming
server
and
its
instance
v
IRIL
–
the
link
between
the
Interface
Repository
server
and
its
instance
v
SMIL
–
the
link
between
the
System
Management
server
and
its
instance
v
APIL
–
the
link
between
the
Console
server
and
its
instance
System
Action:
The
link
method
is
ended
and
no
server
resource
and
link
are
created
for
the
target
instance
resource.
User
Response:
This
problem
indicates
that
the
WebSphere
Complexes
table
has
been
damaged.
Delete
and
insert
again
the
WebSphere
and
CBF
resources
and
restart
servers.
GTMWS005E
instance
cannot
be
linked
to
server.
Invalid
Server
server_cid,
server_id,
inst_cid
inst_id,
type
Explanation:
A
server
instance
link
has
not
been
created
due
to
problems
locating
the
target
server
resource.
Message
Variables:
instance
-
The
name
of
target
instance
resource
server
-
The
name
of
target
server
resource
server_cid
-
The
class
ID
of
target
server
resource
server_id
-
The
ID
of
target
server
resource
inst_cid
-
The
class
ID
of
target
server
instance
resource
inst_id
-
The
ID
of
target
server
instance
resource
type
-
The
link
type
of
target
server
and
server
instance
resources
System
Action:
The
link
method
is
ended
and
no
link
is
created
for
the
target
instance
resource.
User
Response:
This
condition
indicates
damaged
entries
in
containment
or
resource
view
table
for
the
target
server
resource.
Delete
and
insert
again
the
WebSphere
and
CBF
resources
and
restart
the
servers.
©
Copyright
IBM
Corp.
2000,
2004
257
GTMWS008E
Target
WebSphere
or
CBF
resources
are
not
created
Explanation:
The
forced
rebuilding
of
the
WebSphere
Complexes
table
failed
to
update
the
WebSphere
or
CBF
ID
fields
because
these
resources
have
not
been
created.
System
Action:
The
dynamic
create
process
is
ended
and
no
resources
are
created.
User
Response:
Insert
the
target
WebSphere
or
CBF
resources
and
restart
the
servers.
258
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
Chapter
26.
ASG-Zeke
Messages
-
GTMZE0002I
-
GTMZE0014E
The
following
messages
are
issued
during
the
creating
of
resources
or
processing
of
events
for
Allen
System
Groups
ASG-Zeke.
GTMZE0002I
There
is
no
entry
in
DiscoveryBatch
for
batch_scheduler_type.
Explanation:
The
report
file
or
files
for
bulk
discovery
do
not
exist.
The
mainframe
computer
has
to
send
the
report
file
or
files
through
the
ASIMVSIPListenerSvc
service
before
process
Load.
Message
Variables:
batch_scheduler_type
-
The
batch
scheduler
type,
which
can
be
ASG-Zeke
or
CA7
User
Response:
Contact
the
administrator.
Administrator
Response:
If
you
want
to
perform
bulk
discovery,
send
the
report
file
or
files
from
the
mainframe
computer
through
the
ASIMVSIPListenerSvc
service.
GTMZE0003I
Other
_DiscoverZEKEObjects
process
IS
running.
Explanation:
Only
one
bulk
discovery
process
should
be
run
at
a
time.
User
Response:
Contact
the
administrator.
Administrator
Response:
The
bulk
discovery
process
has
to
be
run
after
the
other
process
completes.
It
is
also
possible
that
the
last
process
failed
and
the
pstat
process
is
still
in
running
state.
Check
the
DiscoveryBatch
table
on
the
specific
format_type
and
action_type
values
for
errors.
GTMZE0008I
Following
schedule
sets
are
not
created.
Explanation:
It
is
required
that
all
schedule
sets
must
be
created
before
bulk
discovery
for
ASG-Zeke.
If
any
schedule
sets
are
not
created,
the
process
will
roll
back.
System
Action:
The
transaction
is
rolled
back.
Administrator
Response:
Create
the
listed
schedule
sets
before
running
this
process
again.
GTMZE0010I
Following
schedules
are
not
created.
Explanation:
The
automatic
creation
of
batch
schedules
failed.
Check
the
zeke_schedules
and
Disc_schedules
tables
and
verify
that
the
parent
ID
and
object
name
exist.
System
Action:
Rollback
transaction.
User
Response:
Contact
the
administrator.
Administrator
Response:
Report
the
problem
to
IBM
Software
Support.
GTMZE0014E
No
mapping
FOR
message
TEXT:
event_text
aborting.
Explanation:
If
the
message
cannot
be
mapped,
the
event
is
sent
to
the
zeke_audit_events
table.
Message
Variables:
event_text
-
The
event
text
System
Action:
The
event
is
sent
to
the
zeke_audit_events
table.
User
Response:
Contact
the
administrator.
Administrator
Response:
Verify
that
it
is
a
valid
event.
If
this
event
should
be
posted,
report
the
problem
to
IBM
Software
Support.
GTMZE0018E
ZEKE
FILE
NOT
SUPPORTED
Explanation:
The
ZEKE
input
file
used
for
the
bulk
discovery
process
does
not
contain
valid
data.
User
Response:
Change
the
input
file
to
use
the
correct
LIST
PLAN
or
LIST
EVENTS
report
provided
by
the
ZEKE
reporting
system.
Rerun
the
Zeke
bulk
discovery
job.
©
Copyright
IBM
Corp.
2000,
2004
259
Appendix
A.
SQL
Messages
The
following
messages
are
issued
when
using
SQL.
50500
asisp_insertparentlink:
invalid
container
link
cid,
aborting
Explanation:
An
internal
error
occurred
when
trying
to
create
an
object.
There
is
no
valid
containment
relationship
that
would
allow
the
requested
object
to
be
created
under
the
specified
parent.
Message
Variables:
cid
-
The
class
ID
of
the
containing
object
System
Action:
The
create
operation
terminates.
User
Response:
Note
the
class
ID
of
the
containing
object
and
the
type
of
object
you
attempted
to
create
and
contact
the
administrator.
Administrator
Response:
This
is
a
severe
error
because,
by
design,
the
user
interface
should
not
have
presented
the
option
of
creating
an
object
with
an
invalid
link.
Contact
IBM
Software
Support.
50501
asisp_insertparentlink:
no
container
link
from
cid
to
cid,
aborting
Explanation:
An
internal
error
occurred
when
trying
to
create
an
object.
A
containment
relationship
was
specified,
but
this
type
of
relationship
is
invalid
for
the
two
specified
classes.
Message
Variables:
cid
-
The
class
IDs
of
the
containing
objects
System
Action:
The
create
operation
terminates.
User
Response:
Note
the
class
IDs
in
the
message
and
contact
the
administrator.
Administrator
Response:
This
is
a
severe
error
because,
by
design,
the
user
interface
should
not
have
presented
the
option
of
creating
an
object
with
an
invalid
link.
Contact
IBM
Software
Support.
50502
asisp_insertparentlink:
could
not
insert
link
from
cid1
id1
to
cid2
id2,
aborting
Explanation:
An
unresolved
error
occurred
while
trying
to
create
a
link
between
the
parent
object
and
the
newly
created
child
object.
Message
Variables:
cid1
-
The
class
ID
of
the
contained
object
id1
-
The
instance
ID
of
the
contained
object
cid2
-
The
class
ID
of
the
contained
object
id2
-
The
instance
ID
of
the
contained
object
System
Action:
The
create
operation
terminates.
User
Response:
Contact
the
administrator.
Administrator
Response:
Use
the
information
in
the
message
to
execute
the
following
SQL:
SELECT
*
FROM
link
WHERE
src_cid
=
’cid1’
AND
src_id
=
id1
AND
dst_cid
=
’cid2’
AND
dst_id=id2
SELECT
*
FROM
containment
WHERE
src_cid
=
’cid1’
AND
src_id
=
id1
AND
dst_cid
=
’cid2’
AND
dst_id=id2
Report
the
output
of
the
above
query
and
the
original
error
message
to
IBM
Software
Support.
90051
SQL
Server
Log
Shipping
OOS:
Database:
database,
DELTA:
time
Explanation:
The
SQL
job
TBSM
Log
Shipping
Out
of
Sync
Check
runs
every
20
minutes
on
the
secondary
site
to
check
the
Tivoli
Business
Systems
Manager
databases
on
the
secondary
site,
and
verifies
that
they
are
within
20
minutes
of
synchronization
to
the
primary
site
databases.
If
the
databases
are
not
within
20
minutes
of
synchronization,
the
job
returns
an
error
code.
The
SQL
server
will
then
generates
this
message
on
the
secondary
site
SQL
server
with
the
details
of
which
database
or
databases
are
out
of
lynch
and
what
the
time
difference
(Delta)
is.
The
SQL
server
can
be
configured
to
send
the
error
message
to
other
computers
(it
uses
the
net
send
command).
Typically,
the
customer
will
configure
the
SQL
server
to
send
the
message
to
the
Health
Monitor
client
workstation.
Message
Variables:
database
-
The
name
of
the
database
time
-
The
time
difference
System
Action:
Processing
continues.
The
message
will
be
sent
again
if
the
database
is
still
out
of
synchronization
when
the
job
runs
20
minutes
later.
Administrator
Response:
Perform
the
following
tasks
to
determine
why
the
database
is
out
of
synchronization:
1.
Verify
that
the
SQL
job
TBSM
Log
Shipping
Transaction
Log
Backup
is
running
normally
on
the
primary
site.
©
Copyright
IBM
Corp.
2000,
2004
261
2.
Verify
that
the
SQL
job
TBSM
Log
Shipping
Copy
Job
is
running
normally
on
the
secondary
site.
3.
Verify
that
the
SQL
job
TBSM
Log
Shipping
Load
Copy
Job
is
running
normally
on
the
secondary.
4.
Check
if
there
is
any
SQL
process
connecting
to
the
database
for
an
abnormal
length
of
time.
5.
Execute
the
SQL
Query
msdb..log_ship_entity_log
to
check
the
copy
and
load
job
status.
262
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
Appendix
B.
Summary
of
Messages
Used
for
Automation
The
following
sections
list
the
new,
changed,
and
deleted
IHS-prefixed
messages
that
might
be
used
for
automation
purposes.
New
Messages
The
following
new
messages
have
been
added
to
v3.1:
IHS366I
interval_name
INTERVAL
IS
0
FOR
region
–
POLL
MONITOR
DISABLED.
IHS430I
command
COMMAND
ISSUED
ON
AUTOTASK
autotask
IHS431E
KEYWORD
keyword
IS
NOT
SUPPORTED
IN
location
IHS439I
PROGRAM
pgm
COMPLETE
IHS497I
PARTITIONS
FOR
HALDB
MASTER
mdb_name,
discovery_status
DISCOVERED
IN
ims_name
IHS606E
pgm
subsystem
DISCOVERY
ABANDONED,
CUSTOMIZATION
ERRORS
FOUND
IHS607I
pgm
REDISCOVERY
FOR
object
name
ROUTED
TO
domain
IHS608E
pgm
MONITORING
DOMAIN
FOR
object
name
IS
NOT
KNOWN
IHS609I
pgm
status
DISCOVERY
OF
class
OBJECTS
IHS689E
pgm
UNABLE
TO
PARSE
RESPONSE
var_1
var_2
var_3
var_4
var_5
IHS707I
RESOURCE
resource
HAS
A
MONITORING
LEVEL
OF
monitor_level
IHS753W
ATTEMPTED
TO
ALLOCATE
MORE
THAN
num
DATASETS
TO
DDNAME
ddname.
ONLY
FIRST
num
PROCESSED.
IHS810I
num
type
JOBS
FOUND
BY
routine
IHS813E
MODULE
name
ENCOUNTERED
VERSION
RELATED
ERROR
WITH
product
IHS814E
AO
EXIT
name
DISABLED
FOR
IMS
Vv.r.m
type
SYSTEM
ims_id
IHS815I
module
COMMENCED
PROCESSING
IHS816E
MODULE
module
NOT
LINKED
INTO
PROGRAM
program
IHS817I
module
disc_type
REDISCOVERY
STARTING
FOR
resource_type
resource_name
(FROM
datetime).
IHS818I
LOGON
TO
application
FROM
routine
SUCCESSFUL.
IHS819E
FORMAT
OF
TMON
FOR
MVS
EXCEPTION
ACTIVITY
DISPLAY
UNEXPECTED
(applid).
IHS820I
(command)
INCORRECT
PARAMETERS,
PLEASE
RE-SPECIFY.
IHS821I
(command)
PARAMETER
(value)
IS
NOT
VALID,
FEED
(feed_name)
NAME
(mask_name)
TYPE
(discovery_type)
IHS822I
(command)
NO
ACTIVE
feed_name
SYSTEMS
FOUND
FOR
mask_name
©
Copyright
IBM
Corp.
2000,
2004
263
IHS823I
MPR
NOT
AVAILABLE
TO
PROCESS
TRANSACTION
tran_name,
CLASS
tran_class.
IHS824I
MPR
NOW
AVAILABLE
TO
PROCESS
TRANSACTION
tran_name.
IHS825E
(module)
TYPE
(input_ims_type)
IS
NOT
VALID
FOR
job_name,
SPECIFY
(ims_type).
IHS826E
(module)
JOB
NAME
(job_name)
IS
NOT
VALID
IHS827E
(module)
DISCOVERY
TYPE
(disc_type)
IS
NOT
VALID.
IHS828E
JOB
NAME
(job_name)
IS
NOT
AN
IMS
CONTROL
REGION
IHS829I
(module)
feed_name
REDISCOVERY
FOR
name
DEFERRED.
Changed
Messages
The
following
messages
have
changed
in
v3.1:
IHS344W
UNINITIALIZED
VALUE
name
USED
IN
module,
JOBNAME=jobname
IHS348E
UNRECOGNIZED
JOB
TYPE,
TYPE=type
IN
module,
JOBNAME=jobname
IHS349I
ALL
resource_type
EXCLUDED,
name
POLL
MONITOR
WILL
NOT
BE
STARTED.
IHS371I
SUCCESSFULLY
LOADED
MESSAGE
TABLE
IHSIAOEM
imsid
IHS373I
DETECTED
/MODIFY
PREPARE
ACBLIB
FOR
subsys
IHS374I
DETECTED
/MODIFY
PREPARE
MODBLKS
FOR
subsys
IHS375I
DETECTED
/MODIFY
COMMIT
FOR
subsys
IHS376I
DETECTED
command
FOR
subsys
IHS403I
module
name
NOT
KNOWN
TO
TIVOLI
BUSINESS
SYSTEMS
MANAGER.
IHS416I
RE-DISCOVERY
(type)
FOR
(jobname/subsystem)
ACCEPTED.
IHS433I
UNINITIALIZED
VALUE
variable
USED
IN
module
IHS452I
resource
STATUS
status
AT
subsystem
INITIALIZATION
IHS458E
module
FAILED
WITH
RC
return_code
msg_parms
IHS466E
NO
EVENTS
WERE
PASSED
TO
module
IN
SAFE
safe
IHS486E
threshold_name
NOT
SET
TO
new_value
-
VALUE
NOT
VALID.
CURRENT
VALUE
IS
current_value.
IHS496W
REGION
jobname
NOT
STARTED
–
UNABLE
TO
PERFORM
REDISCOVERY.
IHS571E
UNABLE
TO
LOGON
TO
TMON
FOR
MVS
(APPLID
=
applid).
IHS572E
UNABLE
TO
DISPLAY
THE
EXCEPTION
ACTIVITY
DISPLAY
PANEL
FOR
TMON
FOR
MVS
(APPLID
=
applid).
IHS573E
UNABLE
TO
RETRIEVE
EXCEPTIONS
FROM
TMON
FOR
MVS
(APPLID
=
applid).
IHS574W
STOPPED
RETRIEVAL
AT
num
PANELS
OF
EXCEPTIONS
FROM
TMON
FOR
MVS
(APPLID
=
applid)
264
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
IHS576E
RETURN
CODE
return_code
RECEIVED
WHEN
ATTEMPTING
TO
READ
name
FROM
ddname.
IHS577W
INCORRECT
PARAMETER
value
SPECIFIED
IN
dd
MEMBER
member.
IHS579I
feed
INSTRUMENTATION
DISABLED.
IHS701I
number
RECORDS
action
object_type
object_name
BY
pgm
IHS704E
TIVOLI
BUSINESS
SYSTEMS
MANAGER-SA
AUTOTASK
name
IS
NOT
AVAILABLE
IHS708I
TIVOLI
BUSINESS
SYSTEMS
MANAGER-SA
INITIALIZATION
COMPLETED
IHS709E
TIVOLI
BUSINESS
SYSTEMS
MANAGER-SA
INTERFACE
IS
TERMINATING
IHS712E
RESOURCE_TYPE
type
IS
NOT
SUPPORTED.
IHS716E
VALID
PARMS
ARE:
Resource_Type
Resource_Name
{Event_ID}
IHS718I
job_name
(job_id)
HAS
action_taken
number
data_source
DISCOVERY
RECORDS
FOR
subsystem
TO
NT.
(obj_type)
IHS719I
number
feed
type
RECORDS
FOR
nvsubsys
HAVE
BEEN
SENT
TO
NT
VIA
PUMP
SESSION
IHS745E
IHS$EVTQ_LIMIT
limit
HAS
BEEN
EXCEEDED.
EVENTS
HAVE
BEEN
LOST.
IHS747I
THERE
ARE
CURRENTLY
num
QUEUED
EVENTS
IN
NETVIEW
IHS748I
num
QUEUED
EVENTS
HAVE
BEEN
SENT
TO
PPI
RECEIVER
rcvrid
Deleted
Messages
The
following
messages
have
been
deleted
from
v3.1:
IHS300E
IHS301E
IHS304E
IHS305E
IHS306E
IHS310W
IHS311W
IHS324I
IHS325W
IHS326E
IHS327E
IHS328W
IHS329W
IHS330I
IHS351E
IHS352E
ISH412E
IHS414I
IHS446E
IHS448I
IHS449I
Appendix
B.
Summary
of
Messages
Used
for
Automation
265
IHS483E
IHS484E
IHS601E
IHS602E
IHS603E
IHS604I
IHS605I
IHS610E
IHS611E
IHS612I
IHS613E
IHS614I
IHS615I
IHS616E
IHS617W
IHS618E
IHS619W
IHS706W
IHS725E
IHS726E
IHS728W
IHS740W
IHS741E
266
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
Support
information
This
section
describes
the
following
options
for
obtaining
support
for
IBM
products:
v
“Searching
knowledge
bases”
v
“Obtaining
fixes”
v
“Contacting
IBM
Software
Support”
on
page
268
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
computer
or
on
an
intranet
server.
An
index
is
provided
for
searching
the
Tivoli
Business
Systems
Manager
library.
If
you
have
Adobe
Acrobat
on
your
system,
you
can
use
the
Search
command
to
locate
specific
text
in
the
library.
For
more
information
about
using
the
index
to
search
the
library,
see
the
online
help
for
Acrobat.
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
Web
search.
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
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,
click
I.
When
the
list
of
products
is
displayed,
click
IBM
Tivoli
Business
Systems
Manger
for
z/OS.
This
opens
the
product-specific
support
site.
©
Copyright
IBM
Corp.
2000,
2004
267
3.
Under
Search
our
support
knowledge
base
for
IBM
Tivoli
Business
Systems
Manger
for
z/OS,
type
your
text
in
the
search
field
and
click
the
Submit
button.
You
can
limit
your
search
by
selecting
Solve
a
problem,
Download,
or
Learn,
or
any
combination.
For
tips
on
refining
your
search,
click
Search
assistance.
4.
When
you
find
the
list
of
fixes,
fix
packs,
or
other
service
updates
that
you
are
looking
for,
click
the
name
of
a
fix
to
read
the
description
and
optionally
download
the
fix.
To
receive
weekly
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
Preferences.
Select
a
product
family
and
check
the
appropriate
boxes
for
the
type
of
information
you
want.
5.
Click
Submit.
6.
For
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).
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
Passport
Advantage
Web
page
(http://www.lotus.com/services/passport.nsf/WebDocs/
Passport_Advantage_Home)
and
click
How
to
Enroll
–
By
phone:
For
the
phone
number
to
call
in
your
country,
go
to
the
IBM
Software
Support
Web
site
(http://techsupport.services.ibm.com/guides/contacts.html)
and
click
the
name
of
your
geographic
region.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
268
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
the
contacts
page
of
the
IBM
Software
Support
Handbook
on
the
Web
(http://techsupport.services.ibm.com/guides/contacts.html)
and
click
the
name
of
your
geographic
region
for
phone
numbers
of
people
who
provide
support
for
your
location.
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.
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:
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
re-created?
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
By
phone:
For
the
phone
number
to
call
in
your
country,
go
to
the
contacts
page
of
the
IBM
Software
Support
Handbook
on
the
Web
(techsupport.services.ibm.com/guides/contacts.html)
and
click
the
name
of
your
geographic
region.
If
the
problem
you
submit
is
for
a
software
defect
or
for
missing
or
inaccurate
documentation,
IBM
Software
Support
creates
an
Authorized
Program
Analysis
Support
information
269
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
and
Obtaining
fixes.
270
IBM
Tivoli
Business
Systems
Manager:
Message
Reference
Notices
This
information
was
developed
for
products
and
services
offered
in
the
U.S.A.
IBM
may
not
offer
the
products,
services,
or
features
discussed
in
this
document
in
other
countries.
Consult
your
local
IBM
representative
for
information
on
the
products
and
services
currently
available
in
your
area.
Any
reference
to
an
IBM
product,
program,
or
service
is
not
intended
to
state
or
imply
that
only
that
IBM
product,
program,
or
service
may
be
used.
Any
functionally
equivalent
product,
program,
or
service
that
does
not
infringe
any
IBM
intellectual
property
right
may
be
used
instead.
However,
it
is
the
user’s
responsibility
to
evaluate
and
verify
the
operation
of
any
non-IBM
product,
program,
or
service.
IBM
may
have
patents
or
pending
patent
applications
covering
subject
matter
described
in
this
document.
The
furnishing
of
this
document
does
not
give
you
any
license
to
these
patents.
You
can
send
license
inquiries,
in
writing,
to:
IBM
Director
of
Licensing
IBM
Corporation
North
Castle
Drive
Armonk,
NY
10504-1785
U.S.A.
For
license
inquiries
regarding
double-byte
(DBCS)
information,
contact
the
IBM
Intellectual
Property
Department
in
your
country
or
send
inquiries,
in
writing,
to:
IBM
World
Trade
Asia
Corporation
Licensing
2-31
Roppongi
3-chome,
Minato-ku
Tokyo
106,
Japan
The
following
paragraph
does
not
apply
to
the
United
Kingdom
or
any
other
country
where
such
provisions
are
inconsistent
with
local
law:
INTERNATIONAL
BUSINESS
MACHINES
CORPORATION
PROVIDES
THIS
PUBLICATION
″AS
IS″
WITHOUT
WARRANTY
OF
ANY
KIND,
EITHER
EXPRESS
OR
IMPLIED,
INCLUDING,
BUT
NOT
LIMITED
TO,
THE
IMPLIED
WARRANTIES
OF
NON-INFRINGEMENT,
MERCHANTABILITY
OR
FITNESS
FOR
A
PARTICULAR
PURPOSE.
Some
states
do
not
allow
disclaimer
of
express
or
implied
warranties
in
certain
transactions,
therefore,
this
statement
might
not
apply
to
you.
This
information
could
include
technical
inaccuracies
or
typographical
errors.
Changes
are
periodically
made
to
the
information
herein;
these
changes
will
be
incorporated
in
new
editions
of
the
publication.
IBM
may
make
improvements
and/or
changes
in
the
product(s)
and/or
the
program(s)
described
in
this
publication
at
any
time
without
notice.
Any
references
in
this
information
to
non-IBM
Web
sites
are
provided
for
convenience
only
and
do
not
in
any
manner
serve
as
an
endorsement
of
those
Web
sites.
The
materials
at
those
Web
sites
are
not
part
of
the
materials
for
this
IBM
product
and
use
of
those
Web
sites
is
at
your
own
risk.
©
Copyright
IBM
Corp.
2000,
2004
271
IBM
may
use
or
distribute
any
of
the
information
you
supply
in
any
way
it
believes
appropriate
without
incurring
any
obligation
to
you.
Licensees
of
this
program
who
wish
to
have
information
about
it
for
the
purpose
of
enabling:
(i)
the
exchange
of
information
between
independently
created
programs
and
other
programs
(including
this
one)
and
(ii)
the
mutual
use
of
the
information
which
has
been
exchanged,
should
contact:
IBM
Corporation
2Z4A/101
11400
Burnet
Road
Austin,
TX
78758
U.S.A.
Such
information
may
be
available,
subject
to
appropriate
terms
and
conditions,
including
in
some
cases
payment
of
a
fee.
The
licensed
program
described
in
this
document
and
all
licensed
material
available
for
it
are
provided
by
IBM
under
terms
of
the
IBM
Customer
Agreement,
IBM
International
Program
License
Agreement
or
any
equivalent
agreement
between
us.
Information
concerning
non-IBM
products
was
obtained
from
the
suppliers
of
those
products,
their
published
announcements
or
other
publicly
available
sources.
IBM
has
not
tested
those
products
and
cannot
confirm
the
accuracy
of
performance,
compatibility
or
any
other
claims
related
to
non-IBM
products.
Questions
on
the
capabilities
of
non-IBM
products
should
be
addressed
to
the
suppliers
of
those
products.
Trademarks
IBM,
the
IBM
logo,
CICS,
CICSPlex,
DB2,
developerWorks,
DFS,
DFSMS/MVS,
eServer,
IMS,
iSeries,
Lotus,
MVS,
NetView,
OMEGAMON,
OS/390,
Passport
Advantage,
PBT®,
pSeries,
Rational,
Redbooks,
RMF,
Tivoli,
the
Tivoli
logo,
Tivoli
Enterprise
Console,
VTAM,
WebSphere,
z/OS,
and
zSeries
are
trademarks
or
registered
trademarks
of
International
Business
Machines
Corporation
in
the
United
States,
other
countries,
or
both.
Java
and
all
Java-based
trademarks
and
logos
are
trademarks
or
registered
trademarks
of
Sun
Microsystems,
Inc.
in
the
United
States,
other
countries,
or
both.
UNIX
is
a
registered
trademark
of
The
Open
Group
in
the
United
States
and
other
countries.
Windows
is
a
registered
trademark
of
Microsoft®
Corporation
in
the
United
States,
other
countries,
or
both.
Other
company,
product,
and
service
names
may
be
trademarks
or
service
marks
of
others.
272
IBM
Tivoli
Business
Systems
Manager:
Message
Reference