IBM Tivoli Composite Application Manager for Application
Diagnostics
Version 7.1.0.2
Messaging Guide
GC27-2822-00
IBM Tivoli Composite Application Manager for Application
Diagnostics
Version 7.1.0.2
Messaging Guide
GC27-2822-00
Note
Before using this information and the product it supports, read the information in “Notices” on page 519.
Edition Notice
This 2010 edition applies to Version 7.1.0.2 of IBM Tivoli Composite Application Manager for Application
Diagnostics and to all subsequent releases and modifications until otherwise indicated in new editions.
© Copyright IBM Corporation 2007, 2010.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
Tables . . . . . . . . . . . . . . xlvii
Chapter 2. System Messages for ITCAM
Agent for WebSphere Applications . . 23
About this guide . . . . . . . . . . xlix
CYNAA Messages: Archive Agent . . . . . . .
CYNAA0001D: Queue Queue in the Archive
Agent has wrapped. The queue size is QueueSize.
The total enqueued is TotalEnqueued. The total
dequeued is TotalDequeued. . . . . . . . .
CYNAA0002W: Queue Queue in the Archive
Agent is full. All entries have been discarded.
The queue size is QueueSize. The total enqueued
is TotalEnqueued. The total dequeued is
TotalDequeued. . . . . . . . . . . . .
CYNAA0003I: An unexpected worker type was
created in the Archive Agent. . . . . . . .
CYNAA0004I: An unexpected data message type
was created in the Archive Agent. . . . . . .
CYNAA0005D: The client disconnected from the
Archive Agent server. Worker thread
WorkerThread is ending. The component ID is
ComponentId . . . . . . . . . . . . . .
CYNAA0006D: The Archive Agent is initializing
queue Queue. The queue type is QueueType. The
component ID is ComponentId. . . . . . . .
CYNAA0007I: There is an unknown queue type
in the Archive Agent for queue Queue. . . . .
CYNAA0008I: There is an unspecified priority for
queue type QueueType. The Archive Agent is
continuing with default priority DefaultPriority. .
CYNAA0009I: There is an unspecified size for
queue Queue. The Archive Agent is continuing
with default size DefaultSize.. . . . . . . .
CYNAA0010I: The Producer Connection
ProducerConnectionto the Archive Agent server
was established. The component ID is
ComponentId. . . . . . . . . . . . . .
CYNAA0011I: The Consumer Connection
ConsumerConnection to the Archive Agent server
was established. The component ID is
ComponentId. . . . . . . . . . . . . .
CYNAA0012I: The Servicer Connection
ServicerConnection to the Archive Agent server
was established. The component ID is
ComponentId. . . . . . . . . . . . . .
CYNAA0013I: The Archive Agent server is now
listening at port Port. . . . . . . . . . .
CYNAA0014I: The Archive Agent server is
shutting down. . . . . . . . . . . . .
CYNAA0015I: The Archive Agent server's
shutdown is complete.. . . . . . . . . .
CYNAA0016E: An error ErrorCode occurred while
starting up database agents. . . . . . . . .
CYNAA0017E: The Archive Agent was unable to
join the Kernel. . . . . . . . . . . . .
Intended audience . . . . . . . . . . . xlix
Publications . . . . . . . . . . . . . . xlix
ITCAM for Application Diagnostics library . . xlix
Related publications . . . . . . . . . . . l
Accessing terminology online. . . . . . . . li
Accessing publications online. . . . . . . . li
Ordering publications . . . . . . . . . . lii
Accessibility . . . . . . . . . . . . . . lii
Tivoli technical training . . . . . . . . . . lii
Conventions used in this guide . . . . . . . . lii
Typeface conventions . . . . . . . . . . lii
Variables for directories . . . . . . . . . liii
What's new in this publication . . . . . lv
Chapter 1. Log files, tracing, and utilities 1
Log files and tracing for the Tivoli Enterprise
Monitoring Agent. . . . . . . . . . . .
Gather Script . . . . . . . . . . . .
Tracing within the Tivoli Enterprise Monitoring
Agent. . . . . . . . . . . . . . .
Tivoli Enterprise Monitoring Agent log files . .
Plug-in for IBM Support Assistant (ISA) . . .
Log files and tracing for the Data Collector . . .
First Failure Data Capture . . . . . . . .
Gather Script . . . . . . . . . . . .
Setting the logging and tracing levels . . . .
Data Collector logs . . . . . . . . . .
Plug-in for IBM Support Assistant (ISA) . . .
Log files and tracing for the Managing Server . .
First Failure Data Capture . . . . . . . .
Gather Script . . . . . . . . . . . .
Changing the log level. . . . . . . . .
Managing Server logs . . . . . . . . .
LogViewer . . . . . . . . . . . . .
Tracing and logging within the Tivoli Enterprise
Portal (Summary Workspaces) . . . . . . .
Tracing and logging within the Tivoli Enterprise
Portal Server . . . . . . . . . . . .
Tracing and logging within the Tivoli Enterprise
Portal desktop client on Windows . . . . .
Tracing and logging within the Tivoli Enterprise
Portal desktop client on UNIX systems or Linux
Tracing and logging within the Tivoli Enterprise
Portal Web client . . . . . . . . . .
Environment Checking Utility . . . . . . .
Installing Memory Dump Diagnostic for Java with
IBM Support Assistant. . . . . . . . . .
Where to install ISA and MDD for Java . . .
Downloading ISA . . . . . . . . . .
Installing ISA . . . . . . . . . . . .
Installing MDD for Java . . . . . . . .
© Copyright IBM Corp. 2007, 2010
. 1
. 1
. 2
. 3
. 5
. 6
. 6
. 6
. 7
. 8
. 9
. 9
. 9
. 10
. 10
. 11
. 11
. 16
. 16
. 16
. 17
. 17
. 18
.
.
.
.
.
20
20
21
21
21
23
23
23
23
23
24
24
24
24
24
24
24
25
25
25
25
25
25
iii
CYNAA0018E: An exception occurred while
creating Archive Agent server socket ServerSocket.
The Archive Agent is ending. . . . . . . .
CYNAA0019E: An exception occurred while
accepting Archive Agent server socket connection
SocketConnection. The Archive Agent is ignoring
the exception.. . . . . . . . . . . . .
CYNAA0020I: The Archive Agent is discarding a
request record with mismatched records. . . .
CYNAA0021I: A request record in the Archive
Agent has corrupted (mismatched) methods. . .
CYNAA0022E: Archive Agent ArchiveAgent
encountered error Error while starting. . . . .
CYNAA0023I: Archive Agent ArchiveAgentis
starting. . . . . . . . . . . . . . .
CYNAA0024I: Archive Agent ArchiveAgentis
shutting down. . . . . . . . . . . . .
CYNAA0026E: There was a socket error while
creating worker thread WorkerThread. . . . . .
CYNAA0027E: The Archive Agent with
component ID ComponentId is not registered with
the Kernel. . . . . . . . . . . . . .
CYNAA0028E: The Archive Agent's properties
file was not found. . . . . . . . . . . .
CYNAA0029E: Database exception Exception
occurred when inserting or updating data from
table Table. . . . . . . . . . . . . . .
CYNAA0030W: Database exception Exception
occurred while deleting data from table Table. . .
CYNAA0031E: Database exception Exception
occurred while updating or deleting data from
the table in the Archive Agent. . . . . . . .
CYNAA0032E: The thread ID is null. The IMS
record was discarded. . . . . . . . . . .
CYNAU Messages: Application Monitor . . . . .
CYNAU0001I: WebServer webservName is
Removed . . . . . . . . . . . . . .
CYNAU0002I: WebServer webservName was
added . . . . . . . . . . . . . . .
CYNAU0005I: username added account accname
CYNAU0006I: username modified account
accname1 and accname2 . . . . . . . . .
CYNAU0007I: username modified group
assignments for accname1 and accname2 . . . .
CYNAU0008I: username deleted account accname
CYNAU0009I: username logged in.
. . . . .
CYNAU0010I: username failed log-in because the
user does not exist.
. . . . . . . . . .
CYNAU0011I: username failed log in because the
account is suspended. . . . . . . . . . .
CYNAU0012I: username failed login because the
password used was incorrect. . . . . . . .
CYNAU0013I: username logged out . . . . .
CYNAU0014I: username session timed out. . . .
CYNAU0015I: username with unix username,
unxusername, authenticated. . . . . . . . .
CYNAU0016I: username , unix username
unxusername failed authenticated. . . . . . .
CYNAU0017I: username changed unxusername
account status to: accstatus . . . . . . . .
CYNAU0018I: Created Role : rolename . . . .
iv
26
26
26
26
26
26
27
27
27
27
27
28
28
28
28
28
28
29
29
29
29
29
29
29
29
29
30
30
30
CYNAU0019I: Role : rolename deleted . . . .
CYNAU0020I: Role : rolename is duplicated to :
newrolename . . . . . . . . . . . . .
CYNAU0021I: Role : newrolename is Modified.
.
CYNAU0030I: For user : userName creating
Schedule : scheName . . . . . . . . . .
CYNAU0031I: Modifying Schedule : scheName
informatin minute : min hour : hrs week : week
month : month level : level . . . . . . . .
CYNAU0032I: For user : userName modifying
Schedule : scheName . . . . . . . . . .
CYNAU0033I: Schedule: ScheduleNamewas
deleted . . . . . . . . . . . . . . .
CYNAU0036I: UESR : username changed the
PRIORITY : priority of the THREAD : threadid on
SERVER : servername . . . . . . . . . .
CYNAU0037I: UESR : username changed the
STATUS : status of the THREAD : threadid on
SERVER : servername . . . . . . . . . .
CYNAU0038I: Server Group : groupName created
by : uname . . . . . . . . . . . . . .
CYNAU0039I: Server Group : groupName
modified by : modname old values are : oldval
accounts = accName and servers = servName new
values are : oldval accounts = accName and
servers = servName . . . . . . . . . . .
CYNAU0040I: Setting schedule : scheName for
user : userName of group : groupName . . . .
CYNAU0041I: Changing MOD Level : modlevel
for user : userName of group : groupName . . .
CYNAU0042I: Setting Sampling L1 : rateL1 L2 :
rateL2 and L3 : rateL3 for user : userName of
group : groupName to System default : sysdefault .
CYNAU0043I: Changing Sampling Rate for user :
userName of group : groupName as follows: L1
from : rateL1 to torateL1 L2 from : rateL1 to
torateL1 L3 from : rateL1 to torateL1 . . . . .
CYNAU0050I: Setting Schedule to: scheName for
user : userName with Probe : Probeid . . . . .
CYNAU0051I: Setting Mod Level to: modLevel for
user : userName with Probe : Probeid . . . . .
CYNAU0052I: Changing Sampling Rate for user :
userName with Probe : probeId as follows: L1 from
: rateL1 to torateL1 L2 from : rateL1 to torateL1 L3
from : rateL1 to torateL1 . . . . . . . . .
CYNAU0053I: Changing Sampling Rate for user :
userName as: L1 from : rateL1 to torateL1 L2 from :
rateL1 to torateL1 L3 from : rateL1 to torateL1 . .
CYNAU0054I: UESR : username soft killed the
THREAD : threadid on SERVER : servername . .
CYNAU0055I: UESR : username hard killed the
THREAD : threadid on SERVER : servername . .
CYNAU0132I: uName saved changes to Data
Collection Settings as (Value: Old/New) -- PMI
Polling Frequency: oldPMIFreq/newPMIFreq L1
Sampling Rate: oldL1Rate/newL1Rate L2 Sampling
Rate: oldL2Rate/newL2Rate L3 Sampling Rate:
oldL3Rate/newL3Rate . . . . . . . . . .
30
30
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
30
30
30
30
31
31
31
31
31
31
31
31
32
32
32
32
32
32
32
33
33
33
CYNAU0133I: Default MOD (Monitoring on
Demand) Level Value (Old/New) :
oldModLevel/newModLevel Max Method Records
(Old/New) : oldMaxMethRec/newMaxMethRec . .
CYNAU0136I: username TIMEOUT . . . . .
CYNAU0140I: Server Group : groupName
duplicated to : dupname by origName . . . . .
CYNAU0141I: Server Group : groupName deleted
by : uName . . . . . . . . . . . . .
CYNAU0143I: New Trap Created nameCreated
By: userName . . . . . . . . . . . . .
CYNAU0144I: Trap Modified Original Values:
orgValues New Values: newValues Created By:
createBy Modified By: modifyBy . . . . . . .
CYNAU0145I: Trap Deleted trapName Deleted By:
delBy . . . . . . . . . . . . . . .
CYNAU0146I: Trap Duplicated Old Name:
oldName oldName2 Duplicated By: dupBy
. . .
CYNAU0147I: Trap Activated value Created By:
createBy Duration: duration Iterations left: iterLeft
Activation Suppression Time: actSup Target Data
Collector(s): target Activated By: actBy . . . .
CYNAU0148I: Trap Activation Modified value
Created By: createBy Duration: duration Terminate
when all conditions met: iterLeft Activation
Suppression Time: actSup Target Data
Collector(s): target Activated By: actBy . . . .
CYNAU0149I: Trap value deactivated by name
.
CYNAU0150I: One of your traps was triggered
TrapName: value TrapDate: trapDate trapTime
AppServer: appServer Request: request Method:
method TrapCondition: condition Offending
Content: content Threshold: threshold Max/Min:
maxMin Number Of Hits: hits . . . . . . .
CYNAU0151I: One problem has been created
Alert Id: alertId Problem Timestamp:
alertEventTime alertEventTime Group Id: groupId
Probe Id: probeId Name: name Description:
description Origin: origin Status: status . . . .
CYNAU0152I: One problem was created Problem
Id: problemId . . . . . . . . . . . . .
CYNAU0153I: The URL from ITCAMfTT is not
valid, the parameter para is null. . . . . . .
CYNAU0154I: One problem was updated
Problem Id: problemId Status: status . . . . .
CYNAU0155I: One heap dump schedule has
been created Username: userName Date/Time:
dateTime Group: group Server: server Force GC: gc
CYNAU0156I: One heap dump schedule has
been modified Username: userName Date/Time:
dateTime Group: group Server: server Force GC: gc
CYNAU0157I: One heap dump schedule has
been deleted Username: userName Date/Time:
dateTime Group: group Server: server Heap dump
file name: fileName . . . . . . . . . . .
CYNAU134I: uName saved changes to
Application Overview Settings as (Value:
Old/New) -- Threshold1: oldThreshold1/
newThreshold1 Threshold1: oldThreshold2/
newThreshold2 Baseline Type: baselineType . . .
33
33
33
33
33
34
34
34
34
34
34
34
35
35
35
35
35
35
35
36
CYNAU135I: uName saved changes to SNMP
Settings as (Value: Old/New) -- Host:
oldHost/newHost Port: oldPort/newPort
Community: oldCommu/newCommu . . . . .
CYNB Messages: Byte Code Modification . . . .
CYNB6007E: Exception exception occurred while
parsing XML file filename.. . . . . . . . .
CYNB6008E: Exception exception occurred while
parsing XML file filename.. . . . . . . . .
CYNB6009I: The system was unable to locate the
userbcm.xmlfilename property. . . . . . . .
CYNB6011I: The Byte Code Modification engine
is instrumenting class className. . . . . . .
CYNB6013W: This is warning message name. The
Byte Code Modification engine might experience
problems during class loading and manipulation..
CYNB6014W: Exception man: pkgname:className
has occurred after execution of Byte Code
Modification. . . . . . . . . . . . . .
CYNB6017I: The name of the request file is
filename. . . . . . . . . . . . . . .
CYNB6019I: The Byte Code Modification engine
loaded the definition for an instrumented class
named name. . . . . . . . . . . . . .
CYNB6025W: The Byte Code Modification engine
failed to obtain XML definition files for a
platform. . . . . . . . . . . . . . .
CYNB6026E: The Byte Code Modification engine
failed to load its properties file.. . . . . . .
CYNB6028I: The Byte Code Modification engine
is processing a Java class file named entry. . . .
CYNB6029W: The ClassModifier component is
not specified . . . . . . . . . . . . .
CYNB6030I: No Byte Code Modification regular
expressions have been specified. . . . . . .
CYNB6031I: The Byte Code Modification engine
is adding regular expression regExpStr to its
include list. . . . . . . . . . . . . .
CYNB6032I: The first instruction firstInstruction
has been added to the Byte Code Modification
include list. . . . . . . . . . . . . .
CYNB6038W: Exception exception has occurred.
CYNB6039W: Byte Code Modification is not
instrumenting native and abstract method
Method. . . . . . . . . . . . . . . .
CYNB6100E: Exception exception has occurred.. .
CYNB6101E: The default Byte Code Modification
properties file defaultBcmPropFile was not found. .
CYNB6103E: An exception occurred while
attempting to Byte Code Modify system class
classname. . . . . . . . . . . . . . .
CYNB6104E: An exception occurred while
attempting to Byte Code Modify application class
classname. . . . . . . . . . . . . . .
CYNB6105E: An exception occurred while Byte
Code Modification was attempting to build its
WPSRequestInterceptor component. . . . . .
CYNB6106I: The name of this userbcm.xmlfile is
xml file name. . . . . . . . . . . . . .
CYNB6107I: Byte Code Modification is
instrumenting method Method. . . . . . . .
Contents
36
36
36
36
36
37
37
37
37
37
37
38
38
38
38
38
39
39
39
39
39
39
40
40
40
40
v
BWMCR and CYNCR Messages: Installation . . .
BWMCR8403E: The password is not correct for
the user specified. . . . . . . . . . . .
BWMCR8250E: The user does not have authority
to create tables in this database. . . . . . .
BWMCR8251E: Installation error. The software
generated an exception . . . . . . . . .
BWMCR8252E: Invalid URL format: . . . . .
BWMCR8253E: The host name cannot contain
spaces. . . . . . . . . . . . . . . .
BWMCR8254E: Invalid data.. . . . . . . .
BWMCR8255E: The Host Name field is empty or
contains more than 256 characters.. . . . . .
BWMCR8256E: The host name that was entered
cannot be found. . . . . . . . . . . .
BWMCR8257E: A host name that DNS can
resolve must be provided. . . . . . . . .
BWMCR8258E: You must enter a fully qualified
host name (such as
servername.it.yourcompany.com) . . . . . .
BWMCR8259E: An incorrect host name caused an
error in the installation of the management
server. . . . . . . . . . . . . . . .
BWMCR8260E: The port number must be an
integer value: . . . . . . . . . . . .
BWMCR8261E: The specified port number is out
of range. Valid TCP/IP port numbers must be
positive integers from 1 to 65535. . . . . . .
BWMCR8262E: Valid TCP/IP port numbers must
be positive integers from 1 to 65535. . . . . .
BWMCR8263E: Invalid data.. . . . . . . .
BWMCR8264E: The text in the host name field
must not include a protocol, such as http:// or
https://. . . . . . . . . . . . . . .
BWMCR8265E: The computer identified in the
Host Name field cannot be contacted at the
specified port. . . . . . . . . . . . .
BWMCR8266E: The port is busy: . . . . . .
BWMCR8267E: The user name must not contain
spaces. . . . . . . . . . . . . . . .
BWMCR8268E: The group name must not
contain spaces. . . . . . . . . . . . .
BWMCR8269E: The user name cannot be root.. .
BWMCR8270E: The user is not defined on this
computer. . . . . . . . . . . . . . .
BWMCR8271E: The group is not defined on this
computer. . . . . . . . . . . . . . .
BWMCR8272E: The user is not root. This
installation can only be run as the root user. . .
BWMCR8273E: You must have Administrator
privileges to install or uninstall this software. . .
BWMCR8274E: The installation program failed to
initialize the installation context. See the trace log
for more details. . . . . . . . . . . . .
BWMCR8275E: IBM Tivoli Composite
Application Manager does not support the
specified platform. See the trace log for more
details. . . . . . . . . . . . . . . .
vi
40
40
41
41
41
42
42
42
42
43
43
43
43
43
44
44
44
44
45
45
45
46
46
47
47
47
48
48
BWMCR8276E: Failed to run the bat file that
configures the management agent. The service
might not have been created. See the trace log for
more details. . . . . . . . . . . . . .
BWMCR8277E: Failed to run the bat file that
removes the management agent configuration.
The service might not have been removed. See
the trace log for more details. . . . . . . .
BWMCR8278E: Failed to run the script that
configures the management agent. The
configuration might not have completed. See the
trace log for more details. . . . . . . . .
BWMCR8279E: Failed to run the script that
removes the management agent configuration.
The configuration might not have been removed.
See the trace log for more details. . . . . . .
BWMCR8280E: Registration of the management
agent failed. Verify the management server
information and connectivity. . . . . . . .
BWMCR8281E: The management agent cannot
unregister from the management server. * . . .
BWMCR8282E: An error occurred configuring the
management server. . . . . . . . . . .
BWMCR8283E: Failed to completely remove
configuration files from the management server. .
BWMCR8284E: The software that you are trying
to install is already installed. . . . . . . .
BWMCR8285E: A required file that is part of
prerequisite was not found: . . . . . . . .
BWMCR8286E: There was a prerequisite failure.
An invalid registry key was found. . . . . .
BWMCR8287E: There was a prerequisite failure.
A required registry key was not found. . . . .
BWMCR8288E: Due to prerequisite failure, this
installation cannot continue. . . . . . . . .
BWMCR8289E: There was an error during
connecting to the database: . . . . . . . .
BWMCR8290E: There was an error during
executing a database query: . . . . . . . .
BWMCR8291E: There was an error during
processing the result set from a database query: .
BWMCR8292E: The specified node name is not
correct. . . . . . . . . . . . . . . .
BWMCR8293E: The specified cell name is not
correct. . . . . . . . . . . . . . . .
BWMCR8294E: The specified server name is not
correct. . . . . . . . . . . . . . . .
BWMCR8295E: The install program cannot
contact WebSphere Application Server. . . . .
BWMCR8296E: The data entered does not match
the data specified in the local installation files of
the WebSphere Application Server. . . . . .
BWMCR8297E: The URL format is incorrect. . .
BWMCR8298E: The Store and Forward Agent
failed to configure. . . . . . . . . . . .
BWMCR8299E: The batch file to remove the Store
and Forward Agent configuration failed. . . .
BWMCR8300E: The db2java.zip file was not
found in the specified JDBC path. . . . . . .
BWMCR8301E: The user already exists. . . . .
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
48
48
49
49
49
50
50
50
51
51
51
51
52
52
52
52
52
53
53
53
53
54
54
54
55
55
BWMCR8302E: The uid is already defined on this
computer. . . . . . . . . . . . . . .
BWMCR8303E: The specified path is not a fully
qualified UNIX path. . . . . . . . . . .
BWMCR8304E: The specified path is not a fully
qualified UNIX path. . . . . . . . . . .
BWMCR8305E: The specified path is not a fully
qualified UNIX path. . . . . . . . . . .
BWMCR8306E: An error occurred because a
required field was not populated. . . . . . .
BWMCR8307E: The specified home directory for
the user was not found. . . . . . . . . .
BWMCR8308E: No directory path is provided for
disk space check. . . . . . . . . . . .
BWMCR8309E: An invalid directory path was
provided for a disk space check . . . . . .
BWMCR8310E: Invalid minimum disk space
value provided for disk space check . . . . .
BWMCR8311E: Directory path fails minimum
free disk space check . . . . . . . . . .
BWMCR8312E: The DB2 environment variable
must be set prior to running the installation if an
existing DB2 server is used. . . . . . . . .
BWMCR8313E: Invalid db2admin home directory
path . . . . . . . . . . . . . . . .
BWMCR8314E: The db2admin home directory
path fails the minimum free disk space check. . .
BWMCR8315E: Invalid db2inst home directory
path . . . . . . . . . . . . . . . .
BWMCR8316E: The db2inst home directory path
fails the required minimum free disk space check.
BWMCR8317E: The test connection to the
management server failed. Unable to contact the
management server. Management agent
installation cannot continue until the connection
is established. . . . . . . . . . . . .
BWMCR8319E: The WCP (WebSphere Caching
Proxy) cannot be installed. The system does not
meet WCP installation requirements. . . . . .
BWMCR8321E: The DB2 installation failed. Install
DB2 using the DB2 setup program and run this
installation again using an existing database. . .
BWMCR8322E: The installation failed to create
the database and bufferpool. You can create the
bufferpool and database before continuing or
cancel the installation. . . . . . . . . . .
BWMCR8323E: The installation failed while
installing the WebSphere Application Server. . .
BWMCR8324E: The installation failed while
installing the WebSphere Application Server
Fixpack. . . . . . . . . . . . . . .
BWMCR8325E: The installation failed while
starting the WebSphere Application Server.
. .
BWMCR8326E: The WebSphere Application
Server installation failed while adding IHS to the
existing WebSphere server. . . . . . . . .
BWMCR8327E: The installation failed because the
version and release of the operating system is
below the supported level. This system is version
and release: . . . . . . . . . . . . .
55
56
56
56
56
56
57
57
57
57
58
58
58
58
59
59
60
60
60
61
61
61
61
62
BWMCR8328E: The installation failed because the
version and release of the operating system is not
a supported level. This system is version and
release:
. . . . . . . . . . . . . .
BWMCR8329E: The installation failed because the
service pack level of the operating system is
below the supported level. This system is service
pack level: . . . . . . . . . . . . .
BWMCR8330E: The installation failed because the
maintenance level of the operating system is
below the supported level. This system is
maintenance level: . . . . . . . . . . .
BWMCR8331E: The installation failed because the
host name cannot be resolved. . . . . . . .
BWMCR8332E: The user does not have the
required authority to create a schema in this
database. . . . . . . . . . . . . . .
BWMCR8333E: The IP address of the local
system was detected to be 127.0.0.1, which is not
allowed. Verify the hosts file. . . . . . . .
BWMCR8334E: The path specified for the {0} CD
is invalid: . . . . . . . . . . . . . .
BWMCR8335E: Unable to grant the user
Windows user rights necessary for WebSphere
Application Server.
. . . . . . . . . .
BWMCR8336E: An error occurred while
removing the database tables. The tables must be
removed manually. . . . . . . . . . . .
BWMCR8337E: The required BUFFPOOL32K
database bufferpool does not exist. You can
create the bufferpool and database before
continuing or cancel the installation program. . .
BWMCR8338E: Kernel parameters are not at
appropriate levels for the installation of DB2.
Update the settings and reboot the system before
rerunning this installation. . . . . . . . .
BWMCR8339E: The DB2 user ID is not valid. . .
BWMCR8340E: The DB2 user password is not
valid. . . . . . . . . . . . . . . .
BWMCR8341E: There was a prerequisite failure.
Internet Explorer 4.01 Service Pack 2 is required
to complete the installation. . . . . . . . .
BWMCR8342E: The selected destination directory
already has an uninstall subdirectory, _uninst53.
Remove this subdirectory or install to another
directory. . . . . . . . . . . . . . .
BWMCR8343E: The specified UID for the user
was not found. . . . . . . . . . . . .
BWMCR8344E: The specified license key
contained non-numeric characters or otherwise
was not a valid long integer.. . . . . . . .
BWMCR8345E: No more licenses are available on
the server. . . . . . . . . . . . . . .
BWMCR8346E: WebSphere 5.1 is required to
complete the installation . . . . . . . . .
BWMCR8347E: The IBM Tivoli Composite
Application Manager for Response Time Tracking
Fix pack 5.2-WTP-FP01 does not support the
specified platform. See the trace log for more
details. . . . . . . . . . . . . . . .
Contents
62
62
62
63
63
63
63
63
64
64
64
65
65
65
66
66
66
66
67
67
vii
BWMCR8348E: This IBM Tivoli Composite
Application Manager for Response Time Tracking
installation is supported on the Windows 2003
platform only. See the trace log for more details. .
BWMCR8349E: The selected destination directory
already has an uninstallation subdirectory,
_uninst5201. Uninstall the fix pack and remove
this subdirectory before reinstalling. . . . . .
BWMCR8350E: The IBM Tivoli Composite
Application Manager for WebSphere and J2EE
upgrade must be installed on a machine with a
previous version of the product. . . . . . .
BWMCR8351E: The IBM Tivoli Composite
Application Manager for Response Time Tracking
upgrade must be installed on a machine with a
previous version of the product. A valid
installation was not found in the directory that
was specified. Specify the base installation
directory of a valid management server that
contains a config/db.properties file. . . . . .
BWMCR8352E: The management server
configuration did not complete successfully
during the fix pack installation. . . . . . .
BWMCR8353E: The management server
configuration did not remove properly during
the fix pack uninstallation and might not have
been completely removed. . . . . . . . .
BWMCR8354E: The management agent
configuration did not complete successfully
during the fix pack installation.. . . . . . .
BWMCR8355E: An error occurred while trying to
stop the management agent. . . . . . . . .
BWMCR8356E: Updated management agents
exist. All management agents must roll back to
Version 5.2 before the management server fix
pack can roll back to the Version 5.2 level. . . .
BWMCR8357E: Kernel parameters are not at
appropriate levels for the installation of DB2.
Update the settings and reboot the system before
rerunning this installation. . . . . . . . .
BWMCR8358E: The WebSphere Application
Server, Version 6.0 installation image that was
specified was not valid. . . . . . . . . .
BWMCR8359E: The DB2, Version 8.2 installation
image that was specified was not valid. . . . .
BWMCR8360E: The WebSphere Caching Proxy,
Version 6.0 installation image that was specified
was not valid. . . . . . . . . . . . .
BWMCR8361E: The username and password
specified cannot be used to contact the
WebSphere Application Server. . . . . . . .
BWMCR8362E: The user does not have the
appropriate rights to run the management server.
BWMCR8363E: Security is not enabled in
WebSphere. Clear the check box labeled
WebSphere Security enabled and try again. . . .
BWMCR8364E: The zos.properties file was not
found in the /etc/tmtp/MA/config directory. . .
BWMCR8365E: The management agent failed to
properly configure. See the trace log for details. .
viii
67
67
68
68
68
69
69
69
70
70
71
71
72
72
72
72
73
73
BWMCR8366E: This product has already been
installed on this system. . . . . . . . . .
BWMCR8367E: The management server upgrade
configuration did not complete successfully. . .
BWMCR8369E: An installed IBM Tivoli
Monitoring for Transaction Performance, Version
5.2 Store and Forward Agent was not detected on
this machine.
. . . . . . . . . . . .
BWMCR8370E: To perform the IBM Tivoli
Composite Application Manager for Response
Time Tracking, Version 6.1 Store and Forward
Agent upgrade, the WebSphere Edge Component
Server, Version 5.0 must be uninstalled. . . . .
BWMCR8371E: A version of WebSphere Edge
Component Server has been detected that is not
supported for this release. Only WebSphere Edge
Component Server, Versions 5.1 and above are
supported.. . . . . . . . . . . . . .
BWMCR8372E: WebSphere Application Server 6.0
migration failed and the upgrade cannot
continue. . . . . . . . . . . . . . .
BWMCR8373E: Upgrading configuration for
management agent failed. . . . . . . . .
BWMCR8374E: The username and password
validation failed. Check to make sure the user
name entered has agent privileges on the
management server. . . . . . . . . . .
BWMCR8375E: The port is reserved: . . . . .
BWMCR8376E: The user you specify must have
root privileges. . . . . . . . . . . . .
BWMCR8377E: WebSphere failed to map roles to
users. . . . . . . . . . . . . . . .
BWMCR8378E: The test connection to the
management server failed. Unable to contact the
management server. The management agent
could not remove its registration from the
management server. . . . . . . . . . .
BWMCR8390E: Internet Explorer Enhanced
Security is set on high for the internet zone. This
setting must be medium or lower. . . . . . .
BWMCR8391E: Installation of the management
server in a Network Deployment environment is
not supported with this installation wizard. Refer
to the ITCAMfRTT installation guide for
instructions for installing in a clustered
environment.
. . . . . . . . . . . .
BWMCR8392E: The uninstallation of
management agent behaviors did not complete
successfully. One or all of the behaviors failed to
uninstall. See the trace log for more details. . .
BWMCR8393E: The WebSphere Application
Server, Version 5.1.1 fixpack image that was
specified was not valid. . . . . . . . . .
BWMCR8394E: The WebSphere Application
Server, Version 5.1.1.2 fixpack image that was
specified was not valid. . . . . . . . . .
BWMCR8395E: The installation failed while
installing the WebSphere Application Server
Fixpack. . . . . . . . . . . . . . .
BWMCR8396E: The installation did not find the
specified database. . . . . . . . . . . .
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
73
73
74
74
74
75
75
75
75
76
76
76
77
77
78
78
78
78
79
BWMCR8397E: The post-installation apply script
failed to create links. . . . . . . . . . .
BWMCR8398E: Management agents at an
unsupported version exist. All management
agents must be upgraded to Version 5.301 or 6.0
or higher before the management server can be
upgraded to the Version 6.1 level. . . . . . .
BWMCR8399E: The WebSphere Application
Server, Version 6.0.2 installation image that was
specified was not valid. . . . . . . . . .
BWMCR8400E: The db2profile file was not found
in the specified JDBC path. . . . . . . . .
BWMCR8401E: Maximum number of concurrent
agent installs reached. . . . . . . . . . .
BWMCR8402E: The user you are using does not
have permission to install agents on this server. .
BWMCR8404E: This machine has configuration
entries that might prevent the DB2 installation
from completing successfully. . . . . . . .
BWMCR8405E: The password properties do not
follow the local operating system security policy. .
BWMCR8406E: The home directory for this user
cannot be accessed. . . . . . . . . . . .
BWMCR8407E: The installation detected that this
machine is configured for a terminal server and
is not in the installation mode. The installation
cannot continue. . . . . . . . . . . . .
BWMCR8500W: There are tables in the database.
BWMCR8501W: A self-signed certificate must be
created in the ManagementServer/
IBMHTTPSERVER/(platform)/keys/key.kdb file
before you start the server. Refer to the
installation guide for instructions. . . . . . .
BWMCR8502W: The Windows user name must
not exceed 20 characters. . . . . . . . . .
BWMCR8503W: The installation failed to modify
the db2profile script. Update the script after the
installation completes according to the
instructions in the Problem Determination guide. .
BWMCR8508W: The WebSphere Application
Server could not be started. Manually restart the
WebSphere Application Server. . . . . . . .
BWMCR8509W: The WebSphere Application
Server could not be stopped. Ensure that the
server is stopped before continuing the
installation. . . . . . . . . . . . . .
BWMCR8510W: The original installation files
could not be backed up. . . . . . . . . .
BWMCR8511W: The original installation files
could not be restored. . . . . . . . . . .
BWMCR8512W: An error was received while
copying the SSL Key Store File. . . . . . .
BWMCR8513W: An error was received while
copying the SSL Key Store File and SSL Trust
Store File. . . . . . . . . . . . . . .
BWMCR8514W: There are no tables in the
database. . . . . . . . . . . . . . .
79
79
80
80
80
80
81
81
81
81
82
82
82
83
83
83
83
84
84
84
84
BWMCR8515W: A domain user has been
specified. Domain users must have Act as part of
the operating system and administrative user
rights on the domain controller as well as on the
local machine. Before proceeding with this
installation, verify that the domain user has these
privileges. If these privileges can not be granted,
the installation program will complete
successfully, but WebSphere will be unable to
start.. . . . . . . . . . . . . . . .
BWMCR8516W: Other uninstallation directories
have been detected. Make sure no other
uninstallers exist in the same product directory
before running this uninstallation. Click OK to
continue. . . . . . . . . . . . . . .
BWMCR8517W: One of the HP kernel parameters
is not set to a WAS recommended value in the
/stand/system file.
. . . . . . . . . .
BWMCR8518W: The tables in the database are
not empty. . . . . . . . . . . . . . .
BWMCR8519W: There are no tables, but there are
tablespaces in the database. . . . . . . . .
BWMCR8520W: There are tables in the database
but the number of tables is wrong. . . . . .
BWMCR8521W: Applications may still be
installed on this management agent. . . . . .
BWMCR8522W: This is not a supported platform.
BWMCR8523W: This is not a supported platform.
BWMCR8028I: Required Field: Password . . .
BWMCR8029I: Required Field: User . . . . .
BWMCR8037I: Required Field: Verify Password
BWMCR8038I: The passwords entered do not
match. . . . . . . . . . . . . . . .
BWMCR8039I: The user entered does not exist on
this machine. . . . . . . . . . . . . .
BWMCR8040I: The specified user already exists
on this machine. . . . . . . . . . . . .
BWMCR8050I: To use a proxy host to connect to
the management server, configure the proxy host
name and port in the connection settings of
Internet Explorer. . . . . . . . . . . .
BWMCR8061I: A local version of WebSphere was
found on this machine. IBM Tivoli Composite
Application Manager for Response Time
Tracking, Version 6.1 will use this installation. . .
BWMCR8062I: A local version of WebSphere was
not detected. IBM Tivoli Composite Application
Manager for Response Time Tracking, Version 6.1
will install WebSphere 6.0 on this machine. . . .
BWMCR8063I: The installation program found a
version of WebSphere Application Server that
does not include the required IBM HTTP Server.
The installation program will install this server. .
BWMCR8078I: Required Field: Proxy Host . . .
BWMCR8079I: Required Field: Port Number . .
BWMCR8084I: Required Field: Cell Name . . .
BWMCR8085I: Required Field: Server Name . .
BWMCR8086I: Required Field: Node Name. . .
BWMCR8087I: Required Field: SOAP Connector
Port . . . . . . . . . . . . . . . .
BWMCR8088I: Required Field: JDBC Path . . .
Contents
85
85
85
86
86
86
86
86
87
87
87
87
87
87
87
88
88
88
88
88
88
88
88
89
89
89
ix
BWMCR8094I: Required Field: URL . . . . .
BWMCR8096I: Required Field: Mask . . . . .
BWMCR8098I: The installation tried to use a
version of WebSphere 6.0 that does not have
WebSphere Application Server, refresh pack 6.0.2
installed. WebSphere Application Server refresh
pack 6.0.2 or later is required for this product to
run on WebSphere 6.0. The product is also
supported on WebSphere Application Server,
Version 5.1. . . . . . . . . . . . . .
BWMCR8101I: SSL Key Store File and Password
entered are invalid . . . . . . . . . . .
BWMCR8109I: Required Field: Key File Name . .
BWMCR8110I: Required Field: Key File Password
BWMCR8111I: Required Field: Trust File Name
BWMCR8112I: Required Field: Trust File
Password . . . . . . . . . . . . . .
BWMCR8113I: Required Field: Port With Client
Authentication . . . . . . . . . . . .
BWMCR8114I: Required Field: Port Without
Client Authentication . . . . . . . . . .
BWMCR8115I: Required Field: Key File does not
exist . . . . . . . . . . . . . . . .
BWMCR8116I: Required Field: Trust File does not
exist . . . . . . . . . . . . . . . .
BWMCR8128I: Installation of the WebSphere
caching proxy requires a system reboot. The
installation program will resume after reboot. . .
BWMCR8129I: Required Field: KDB Key
Information . . . . . . . . . . . . .
BWMCR8130I: The key ring file does not exist.
BWMCR8131I: The password stashed file does
not exist. . . . . . . . . . . . . . .
BWMCR8145I: Required Field: Port For
Management Server Console. . . . . . . .
BWMCR8149I: The minimum version and release
of this operating system is: . . . . . . . .
BWMCR8150I: The minimum service pack level
of this operating system is: . . . . . . . .
BWMCR8151I: The minimum maintenance level
of this operating system is: . . . . . . . .
BWMCR8153I: The specified mask value is in an
invalid format. . . . . . . . . . . . .
BWMCR8154I: The user account you specify
must have membership in the Administrators
group. The user also needs 'Act as part of the
operating system' and 'Logon as a service' user
rights. The user did not have one or both of
these user rights but was granted by the
installation process. To proceed with the
installation, cancel the current installation. Go to
Start->Shut Down and log off. Then, log back in
and restart the installation. . . . . . . . .
BWMCR8155I: Required Field: Admin Console
Port . . . . . . . . . . . . . . . .
BWMCR8157I: Required Field: database name . .
BWMCR8158I: Required Field: SID . . . . .
BWMCR8159I: Required Field: port . . . . .
BWMCR8160I: Required Field: host . . . . .
BWMCR8161I: Password entered is not valid for
the specified SSL Key Store File . . . . . .
x
89
89
89
89
89
90
90
90
90
90
90
90
90
90
91
91
91
91
91
91
91
92
92
92
92
92
92
BWMCR8162I: Password entered is not valid for
the specified SSL Trust File . . . . . . . .
BWMCR8164I: Password does not meet
specifications. Choose another password. . . .
BWMCR8165I: The temp drive does not have
enough space. Free up some temporary space or
rerun the installation from the command line
using the -W spanningBean.tempDir={dir} option.
See the trace file for more details. . . . . . .
BWMCR8166I: Configured the management
agent successfully. . . . . . . . . . . .
BWMCR8167I: Unregistered the management
agent successfully. . . . . . . . . . . .
BWMCR8168I: Usage: configMa.sh [install |
uninstall] . . . . . . . . . . . . . .
BWMCR8169I: Local directories created. \nGo to
/etc/tmtp/MA/config, verify setupEnv.sh and
customize zos.properties. \nRun configMa.sh to
register the management agent. . . . . . .
BWMCR8170I: This script will prepare the IBM
Tivoli Composite Application Manager for
Response Time Tracking management agent for
configuration. \nIt will create local directories in
/etc and /var directories. \nDo you want to
continue ? [y/n]
. . . . . . . . . . .
BWMCR8171I: Check values in zos.properties
including port numbers entered are all correct. .
BWMCR8172I: * (Specify a User account that
exists on the WebSphere Application Server of
the management server. This user account must
have the "agent" role.)
. . . . . . . . .
BWMCR8173I: Upgraded the configuration for
the management agent. . . . . . . . . .
BWMCR8174I: The installation tried to use a 5.0
version of WebSphere Application Server, version
5.0.1 that has Embedded Messaging Installed.
WebSphere Application Server Fix pack 5.0.2 or
later is required for this product to be migrated
to WebSphere Application Server 6.0. . . . . .
BWMCR8175I: The installation tried to use a
version of WebSphere that does not have
WebSphere Application Server, Fix pack 5.1.1.2
installed. WebSphere Application Server Fix pack
5.1.1.2 or later is required for this product. The
installation images for the fixpack can be
obtained from the IBM Tivoli Composite
Application Manager, Version 6.1 CD packet. . .
BWMCR8176I: The installation program tried to
upgrade a version of the management server that
is not supported. A management server at the
5.3.1 level or later is required for this upgrade. .
BWMCR8177I: The installation program could
not connect to specified database, this could be
caused by incorrect database information like
server, database name, user, password or port.
\nCorrect the information and try again. If all
information is correct, the database may not
exist. \nSelect Yes to allow the installation
program to attempt to create the database. . . .
92
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
92
93
93
93
93
93
93
93
94
94
94
94
94
94
95
BWMCR8178I: This script will create links for the
ARM shared libraries in /usr/lib directory. \nDo
you want to continue ? [y/n] . . . . . . .
BWMCR8179I: Done. Links were created
successfully in /usr/lib directory. . . . . . .
BWMCR8180I: The installation program tried to
use a version of the management server that
does not have the appropriate fix pack level
installed. A version of the management server at
Fix pack 5.301 or later is required for this
product. . . . . . . . . . . . . . .
BWMCR8181I: The installation tried to use a
version of the management server that does not
have the appropriate fix pack level installed. A
version of the management server at Fix pack
5.301 or later is required for this product. . . .
BWMCR8182I: The installation tried to use a DB2
version that is not supported by this product.
DB2 8.1 ESE with Fixpack 6a or later is required
for this product. . . . . . . . . . . . .
BWMRTT0001A: The User Name or Password
entered is not valid . . . . . . . . . . .
BWMRTT0002A: The ojdbc14.jar file was not
found in the specified JDBC path. . . . . . .
BWMCR8518E: The host name is not fully
qualified. Provide a fully qualified host name. . .
BWMCR8175E: There is no enough disk
spacedestination. . . . . . . . . . . . .
BWMCR8193E: Unsupported operating
systemosname. . . . . . . . . . . . .
BWMCR8176E: The value valueyou entered for
the namefield is invalid. . . . . . . . . .
BWMCR8177E: The JAVA_HOME pointed JRE is
invalid, please useavaVersionCmdto validate it. If
correct,javaVersionCmdwill print out version of
the JRE.. . . . . . . . . . . . . . .
BWMCR8178E: The JAVA_HOME pointed JRE is
invalid, please usejavaVersionCmdto validate it. If
correct,javaVersionCmdwill print out version of
the JRE,but the print out ofjavaVersionOutput. . .
BWMCR8179E: The JAVA_HOME is invalid,the
java.exe(windows) or java(linux or unix) does not
exist. . . . . . . . . . . . . . . .
BWMCR8180E: Installation program could not
resolve the specified hostname. Type a fully
qualified host name that the Domain Name
System service can resolve before you proceed. .
BWMCR8181E: Incorrect host name. Type a fully
qualified host name that the Domain Name
System service can resolve before you proceed. .
BWMCR8182E: The path is not empty:pathPlease
select an empty path or a new path. . . . . .
BWMCR8183I: Select Action.. . . . . . . .
BWMCR8184I: Select action to be executed.. . .
BWMCR8185I: Exit after the action execution. . .
BWMCR8186E: The value valueyou entered for
thenamefield is invalid. . . . . . . . . .
BWMCR8187E: Incorrect host name or IP address
for the local machine. . . . . . . . . . .
95
95
95
95
95
96
96
96
96
96
96
97
97
97
97
97
98
98
98
98
98
BWMCR8188E: The specified RMI port number is
out of range. Valid TCP/IP port numbers must
be positive integers between 8200 and 8299. . . 98
BWMCR8189E: The specified controller RMI port
number is out of range. Valid TCP/IP port
numbers must be positive integers from 8300 to
8399.. . . . . . . . . . . . . . . . 98
BWMCR8190W: The Data Collector cannot
connect to the Managing Server. . . . . . . 99
BWMCR8191W: The Managing Server cannot
connect to the Data Collector. . . . . . . . 99
BWMCR8192E: The path is not
writable:pathPlease select a writable path. . . . 99
BWMCR8623E: An error occurred while trying to
validate the response file path. . . . . . . . 99
BWMCR8625E: An error occurred while trying to
validate the option choosing on this panel. . . . 99
BWMCR8627I: A warning occurred while trying
to validate the specified response file name. . . 100
BWMCR8629E: An error occurred while trying
to validate the specified response file name. . . 100
BWMCR8631E: An error occurred while trying
to validate the specified response file name. . . 100
BWMCR8633E: An error occurred while trying
to validate the specified response file name. . . 100
BWMCR8635E: The directory path dir contains
spaces, which is not acceptable. . . . . . . 101
BWMCR8636E: The destination path cannot
contain the following special characters:
spechar_list . . . . . . . . . . . . . 101
CYNCR8026I: Required Field: Admin User . . 101
CYNCR8028I: Required Field: Password . . . 101
CYNCR8029I: Required Field: User . . . . . 101
CYNCR8037I: Required Field: Verify Password 101
CYNCR8038I: The passwords entered do not
match.. . . . . . . . . . . . . . . 101
CYNCR8039I: The user entered does not exist
on this machine. . . . . . . . . . . . 101
CYNCR8040I: The specified user already exists
on this machine. . . . . . . . . . . . 102
CYNCR8061I: A local version of WebSphere
Application Server was found on this machine.
IBM Tivoli Composite Application Manager for
WebSphere 6.1 will use this installation of
WebSphere Application Server. . . . . . . 102
CYNCR8062I: A local version of WebSphere
Application Server was not detected. IBM Tivoli
Composite Application Manager for WebSphere
6.1 will install WebSphere Application Server 6.1
on this machine. . . . . . . . . . . . 102
CYNCR8084I: Required Field: Cell Name . . . 102
CYNCR8085I: Required Field: Server Name . . 102
CYNCR8086I: Required Field: Node Name . . 102
CYNCR8087I: Required Field: SOAP Connector
Port . . . . . . . . . . . . . . . 102
CYNCR8088I: Required Field: JDBC Path . . . 102
CYNCR8094I: Required Field: URL . . . . . 103
98
Contents
xi
CYNCR8098I: The installation tried to use a
version of WebSphere 6.0 that does not have
WebSphere Application Server, Fix Pack 6.0.2
installed. WebSphere Application Server, Fix
Pack 6.0.2 or later is required for this product to
run on WebSphere 6.0. . . . . . . . . .
CYNCR8101I: The SSL Key Store File and
Password entered are invalid. . . . . . . .
CYNCR8109I: Required Field: Key File Name
CYNCR8110I: Required Field: Key File
Password. . . . . . . . . . . . . .
CYNCR8111I: Required Field: Trust File Name
CYNCR8112I: Required Field: Trust File
Password. . . . . . . . . . . . . .
CYNCR8113I: Required Field: Port With Client
Authentication . . . . . . . . . . . .
CYNCR8114I: Required Field: Port Without
Client Authentication . . . . . . . . . .
CYNCR8115I: Required Field: Key File does not
exist. . . . . . . . . . . . . . . .
CYNCR8116I: Required Field: Trust File does
not exist. . . . . . . . . . . . . . .
CYNCR8145I: Required Field: Port For
Managing Server Console . . . . . . . .
CYNCR8149I: The minimum version and release
of this operating system is: . . . . . . . .
CYNCR8150I: The minimum service pack level
of this operating system is: . . . . . . . .
CYNCR8151I: The minimum maintenance level
of this operating system is: . . . . . . . .
CYNCR8154I: The user account you specify
must have membership in the Administrators
group. The user also needs Act as part of the
operating system and Logon as a service user
rights. The user did not have one or both of
these user rights but was granted access by the
installation process. To proceed with the
installation, cancel the current installation. Select
Start > Shut Down and log off. Then, log back
in and restart the installation. . . . . . . .
CYNCR8155I: Required Field: Administrative
Console Port . . . . . . . . . . . .
CYNCR8157I: Required Field: Database Name
CYNCR8158I: Required Field: SID . . . . .
CYNCR8159I: Required Field: Port . . . . .
CYNCR8160I: Required Field: Host Name . . .
CYNCR8161I: The entered password is not valid
for the specified SSL Key Store File. . . . . .
CYNCR8162I: The entered password is not valid
for the specified SSL Trust File. . . . . . .
CYNCR8164I: The password does not meet
specifications. Choose another password. . . .
CYNCR8165I: The temporary drive does not
have enough space. Free up some temporary
space or rerun the installation from the
command line using the -W
spanningBean.tempDir={dir} option. See the
trace file for more details. . . . . . . . .
xii
103
103
103
103
103
103
103
104
104
104
104
104
104
104
105
105
105
105
105
105
105
105
106
106
CYNCR8177I: The installation could not connect
to the specified database. It might not exist. The
installation will create the database and the
tables. . . . . . . . . . . . . . . .
CYNCR8178I: The admin user entered does not
exist on this machine. . . . . . . . . .
CYNCR8179I: The Database Instance user
entered does not exist on this machine. . . . .
CYNCR8180I: The Database Schema user
entered does not exist on this machine. . . . .
CYNCR8194W: There was a failure while
unconfiguring the Data Collector on application
server. . . . . . . . . . . . . . . .
CYNCR8195E: Incorrect host name or IP address
for the local machine.. . . . . . . . . .
CYNCR8196W: Will the following application
servers be reconfigured?\nappserver . . . . .
CYNCR8197E: Unable to get Data Collector
install configuration, Please install Data
Collector again.. . . . . . . . . . . .
CYNCR8250E: The user does not have authority
to create tables in this database. . . . . . .
CYNCR8251E: The software generated an error
during the installation. . . . . . . . . .
CYNCR8253E: The host name cannot contain
spaces. . . . . . . . . . . . . . .
CYNCR8254E: The installer encountered invalid
data that prevents completion of the installation.
CYNCR8255E: The host name has not been
specified or the specified host name is too long. .
CYNCR8256E: The installer cannot find the
specified host name. . . . . . . . . . .
CYNCR8257E: A host name that the Domain
Name System can resolve must be provided. . .
CYNCR8258E: You must enter a fully qualified
host name (such as
servername.it.yourcompany.com).. . . . . .
CYNCR8259E: An incorrect host name caused
an error in the installation of the Managing
Server.. . . . . . . . . . . . . . .
CYNCR8260E: The port number must be an
integer value. . . . . . . . . . . . .
CYNCR8261E: The specified port number is
outside of the range for valid TCP/IP port
numbers. . . . . . . . . . . . . . .
CYNCR8262E: The port number specified for
TCP/IP communication is invalid. . . . . .
CYNCR8263E: The installer encountered invalid
data that prevents completion of the installation.
CYNCR8264E: The text in the host name field
must not include a protocol, such as http:// or
https://. . . . . . . . . . . . . . .
CYNCR8265E: The computer identified in the
Host Name field cannot be contacted at the
specified port. . . . . . . . . . . . .
CYNCR8266E: The port is busy. . . . . . .
CYNCR8267E: The user name must not contain
spaces.. . . . . . . . . . . . . . .
CYNCR8268E: The group name must not
contain spaces. . . . . . . . . . . . .
CYNCR8269E: The user name cannot be root.
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
106
106
106
106
106
107
107
107
107
107
108
108
108
108
109
109
109
109
110
110
110
110
111
111
111
112
112
CYNCR8270E: The user is not defined on this
computer.. . . . . . . . . . . . . .
CYNCR8271E: The group is not defined on this
computer.. . . . . . . . . . . . . .
CYNCR8272E: The user is not root. This
installation can only be run as the root user. . .
CYNCR8273E: You must have Administrator
privileges to install or uninstall this software.. .
CYNCR8274E: The installation program failed to
initialize the installation context. . . . . . .
CYNCR8275E: IBM Tivoli Composite
Application Manager for WebSphere does not
support the specified platform. . . . . . .
CYNCR8276E: The system failed to run the .bat
file that configures the agent. The service might
not have been created. . . . . . . . . .
CYNCR8277E: The system failed to run the .bat
file that removes the agent configuration. The
service might not have been removed. . . . .
CYNCR8278E: The system failed to run the
script that configures the agent. The
configuration might not have completed. . . .
CYNCR8279E: The system failed to run the
script that removes the agent configuration. The
configuration might not have been removed. . .
CYNCR8282E: An error occurred configuring
the Managing Server. . . . . . . . . . .
CYNCR8283E: The system failed to completely
remove configuration files from the Managing
Server. . . . . . . . . . . . . . . .
CYNCR8284E: The software that you are trying
to installation is already installed. . . . . .
CYNCR8285E: A required file for searching for
prerequisites was not found: . . . . . . .
CYNCR8286E: There was a prerequisite failure.
An invalid registry key was found. . . . . .
CYNCR8287E: There was a prerequisite failure.
A required registry key was not found.
. . .
CYNCR8288E: Due to prerequisite failure, this
installation cannot continue. . . . . . . .
CYNCR8289E: There was an error connecting to
the database: . . . . . . . . . . . .
CYNCR8290E: There was an error executing a
database query: . . . . . . . . . . .
CYNCR8291E: There was an error processing
the result set from a database query: . . . .
CYNCR8292E: The specified node name is not
correct. . . . . . . . . . . . . . .
CYNCR8293E: The specified cell name is not
correct. . . . . . . . . . . . . . .
CYNCR8294E: The specified server name is not
correct. . . . . . . . . . . . . . .
CYNCR8295E: WebSphere Application Server
cannot be contacted using the specified port.
The WebSphere Application Server might not be
running or the specified port number is
incorrect. . . . . . . . . . . . . . .
CYNCR8296E: The data entered does not match
the data specified in the local installation files of
the WebSphere Application Server. . . . . .
113
113
114
114
114
114
115
115
115
115
116
116
116
116
117
117
117
117
117
118
118
118
118
119
119
CYNCR8300E: The db2java.zip file was not
found in the specified JDBCpath. . . . . . .
CYNCR8301E: The user already exists. . . . .
CYNCR8302E: The UID is already defined on
this computer. . . . . . . . . . . . .
CYNCR8303E: The specified path is not a fully
qualified UNIX path. . . . . . . . . . .
CYNCR8304E: The specified path is not a fully
qualified UNIX path. . . . . . . . . . .
CYNCR8305E: The specified path is not a fully
qualified UNIX path. . . . . . . . . . .
CYNCR8306E: An error occurred because a
required field was not populated. . . . . .
CYNCR8307E: The specified home directory for
the user was not found. . . . . . . . . .
CYNCR8308E: The directory path required for a
disk space check has not been set. . . . . .
CYNCR8309E: An invalid directory path was
provided for a disk space check. . . . . . .
CYNCR8310E: The minimum disk space value
required for a disk space check was not set or is
invalid. . . . . . . . . . . . . . .
CYNCR8311E: The provided directory path did
not have the minimum specified free disk space.
CYNCR8312E: The DB2 environment variable
must be set prior to running the installation if
an existing DB2 server is used. . . . . . .
CYNCR8313E: The specified db2admin home
directory path is invalid. . . . . . . . .
CYNCR8314E: The specified db2admin home
directory path did not have the required
minimum free disk space. . . . . . . . .
CYNCR8315E: The specified db2inst home
directory path is invalid. . . . . . . . .
CYNCR8316E: The specified dbinst home
directory path did not have the required
minimum free disk space. . . . . . . . .
CYNCR8317E: The test connection to the
Managing Server failed. The system was unable
to contact the Managing Server. Agent
installation cannot continue until the connection
is established. . . . . . . . . . . . .
CYNCR8321E: An error occurred while running
the embedded DB2 installation. The current
installation will be canceled. Refer to the
ITCAM for Application Diagnostics installation
trace log and DB2 installation log for more
details. . . . . . . . . . . . . . .
CYNCR8323E: The installation failed while
installing the WebSphere Application Server. . .
CYNCR8324E: The installation failed while
installing the WebSphere Application Server
Fixpack. . . . . . . . . . . . . . .
CYNCR8325E: The installation failed while
starting WebSphere Application Server. . . .
CYNCR8327E: The installation failed because
the version and release of the operating system
is below the supported level. . . . . . . .
CYNCR8328E: The installation failed because
the version and release of the operating system
is not at a supported level. . . . . . . . .
Contents
119
119
120
120
120
121
121
121
121
121
122
122
122
123
123
123
123
123
124
124
125
125
125
126
xiii
CYNCR8329E: The installation failed because
the service pack level of the operating system is
below the supported level. . . . . . . . .
CYNCR8330E: The installation failed because
the maintenance level of the operating system is
below the supported level. . . . . . . . .
CYNCR8331E: The installation failed because
the host name cannot be resolved. . . . . .
CYNCR8332E: The user does not have the
required authority to create a schema in this
database. . . . . . . . . . . . . . .
CYNCR8333E: The IP address of the local
system was detected as 127.0.0.1, which is not
allowed. . . . . . . . . . . . . . .
CYNCR8334E: The path specified for the {0}
CD-ROM is invalid: . . . . . . . . . .
CYNCR8335E: The system was unable to grant
the user the Windows user rights necessary for
WebSphere Application Server. The installation
cannot continue. . . . . . . . . . . .
CYNCR8336E: An error occurred while
removing the database tables. The tables must
be removed manually. . . . . . . . . .
CYNCR8338E: Kernel parameters MSGMAX
and MSGMNB must be set to 65535 in the
/etc/system file. . . . . . . . . . . .
CYNCR8339E: The DB2 user ID does not satisfy
the required set of conditions. . . . . . . .
CYNCR8340E: The DB2 user password does not
satisfy the required set of conditions. . . . .
CYNCR8341E: There was a prerequisite failure.
Internet Explorer 4.01 Service Pack 2 is required
to complete the installation. . . . . . . .
CYNCR8342E: The selected destination directory
already has an uninstall subdirectory, _uninst53.
CYNCR8343E: The specified UID for the user
was not found. . . . . . . . . . . . .
CYNCR8344E: The specified license key
contained non-numeric characters or was not a
valid long integer. . . . . . . . . . . .
CYNCR8345E: No more licenses are available on
the server. . . . . . . . . . . . . .
CYNCR8346E: WebSphere Application Server
5.1 is required to complete the installation. . .
CYNCR8357E: One of the HP Kernel parameters
is not set correctly in the /stand/system file. . .
CYNCR8358E: The WebSphere Application
Server 6.1 installation image directory that was
specified is not valid. . . . . . . . . . .
CYNCR8359E: The DB2 8.2 installation image
directory that was specified is not valid. . . .
CYNCR8360E: The WebSphere Application
Server 6.1.1 installation image directory that
was specified is not valid. . . . . . . . .
CYNCR8361E: The user name and password
specified cannot be used to contact WebSphere
Application Server. . . . . . . . . . .
CYNCR8362E: The user does not have the
appropriate rights to run the Managing Server. .
CYNCR8363E: Security is not enabled in
WebSphere Application Server. . . . . . .
xiv
126
126
126
126
127
127
127
127
128
128
128
129
129
129
129
129
130
130
130
131
131
131
132
132
CYNCR8366E: This product has already been
installed on this system. . . . . . . . . .
CYNCR8374E: User name and Password
validation failed. Ensure that the user name
entered has agent privileges on the Managing
Server. . . . . . . . . . . . . . .
CYNCR8375E: The port is reserved. . . . . .
CYNCR8376E: The user you specify must have
root privileges. . . . . . . . . . . . .
CYNCR8377E: WebSphere Application Server
failed to map roles to users. . . . . . . .
CYNCR8378E: The test connection to the
Managing Server failed. The system was unable
to contact the Managing Server. . . . . . .
CYNCR8390E: Internet Explorer Enhanced
Security is set on high for the internet zone.
This setting must be medium or lower. . . . .
CYNCR8391E: WebSphere Network Deployment
is not supported. . . . . . . . . . . .
CYNCR8396E: The installation did not find the
specified database. . . . . . . . . . .
CYNCR8398E: The installer was unable to get
the topology information from WebSphere
Application Server. . . . . . . . . . .
CYNCR8399E: The installer was unable to
validate server and port information with
WebSphere Application Server. . . . . . .
CYNCR8400E: Server creation failed. . . . .
CYNCR8401E: The db2profile file was not found
in the specified JDBC path. . . . . . . . .
CYNCR8402E: The installer encountered invalid
data that prevents completion of the installation.
CYNCR8500W: There are existing tables in the
database. . . . . . . . . . . . . . .
CYNCR8502W: The Windows user name must
not exceed 20 characters. . . . . . . . .
CYNCR8503W: The installation failed to modify
the db2profile script. . . . . . . . . . .
CYNCR8508W: The WebSphere Application
Server could not be started. . . . . . . .
CYNCR8509W: The WebSphere Application
Server could not be stopped. . . . . . . .
CYNCR8515W: A domain user has been
specified. Before proceeding with this
installation, verify that the domain user has
these privileges. . . . . . . . . . . .
CYNCR8516W: Other uninstallation directories
have been detected. . . . . . . . . . .
CYNCR8517W: One of the HP Kernel
parameters is not set to a WebSphere
Application Server recommended value in the
/stand/system file. The installation will
continue. . . . . . . . . . . . . . .
CYNCR8518E: The host name host name is not
fully qualified. Provide a fully qualified host
name or IP address. . . . . . . . . . .
CYNCR8519E: The server server name appears to
be down or unreachable. . . . . . . . .
CYNCR8520E: Select a server for monitoring.
CYNCR8521E: Server server is not in the list of
known servers: server list. . . . . . . . .
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
132
132
133
133
133
133
134
134
134
135
135
135
135
136
136
136
136
137
137
137
137
138
138
138
138
139
CYNCR8522E: The system was unable to
retrieve a list of known servers from server
server using SOAP port port. . . . . . . .
CYNCR8523I: The system is configuring server
server. . . . . . . . . . . . . . . .
CYNCR8524I: The system is unconfiguring
server server. . . . . . . . . . . . .
CYNCR8525E: There was a failure while
configuring server server. . . . . . . . .
CYNCR8526E: There was a failure while
unconfiguring the Data Collector on application
server server. . . . . . . . . . . . .
CYNCR8527I: The application servers associated
with this Data Collector must be unconfigured
before the uninstallation can complete. The
uninstallation program will assist you in
removing the configuration from these servers. .
CYNCR8528E: The Installer is unable to write to
directory directory. . . . . . . . . . . .
CYNCR8529E: Unable to determine if the
following application server, Vendor=vendor,
AppServerType=serverType,
Version=appServerVersion, meets the prerequisites
in the file dcprereqsFile. . . . . . . . . .
CYNCR8530E: Failed to create database. . . .
CYNCR8531W: An ITCAM for Application
Diagnostics product already exists on this server
instance. . . . . . . . . . . . . . .
CYNCR8532E: The file separator in the specified
Managing Server home directory is invalid. . .
CYNCR8601I: Stopping WebSphere Application
Server.. . . . . . . . . . . . . . .
CYNCR8603I: Uninstalling WebSphere
Application Server. . . . . . . . . . .
CYNCR8605I: Stopping the DB2 . . . . . .
CYNCR8607I: Uninstalling the DB2 . . . . .
CYNCR8609E: An error occurred while selecting
the features to be uninstalled. . . . . . . .
CYNCR8611I: Dropping the DB2 Tables and
Database. . . . . . . . . . . . . . .
CYNCR8613I: Uninstallation of DB2 is complete.
CYNCR8615I: Uninstallation of WebSphere
Application Server is complete. . . . . . .
CYNCR8617I: Dropping the Oracle Tables and
Database. . . . . . . . . . . . . . .
CYNCR8619E: The server server name on profile
profilehome appears to be unreachable. . . . .
CYNCR8621E: Click the YES button to continue
to force uninstallation or click the NO button to
verify that the SOAP port is specified correctly,
and use the administrative console to determine
if it is up.. . . . . . . . . . . . . .
CYNCR8623E: An error occurred while trying to
validate the response file path. . . . . . .
CYNCR8625E: An error occurred while trying to
validate the option choosing on this panel. . .
CYNCR8627I: An warning occurred while trying
to validate the specified response file name. . .
CYNCR8629E: An error occurred while trying to
validate the specified response file name. . . .
139
139
139
139
140
140
140
140
141
141
141
141
141
142
142
142
142
142
142
142
142
143
143
143
143
144
CYNCR8631E: An error occurred while trying to
validate the specified response file name. . . .
CYNCR8633E: An error occurred while trying to
validate the specified response file name. . . .
CYNCR8635I: The uninstaller detected that the
ITCAM for Application Diagnostics and J2EE
Managing Server Version 6.1 is still in running. .
CYNCR9100E: The installation program cannot
connect to the specified database. . . . . .
CYNCR9101E: The ojdbc14.jar file was not
found in the specified JDBC path. . . . . .
CYNCR9102E: The specified ORACLE Sqlplus
User does no exists. . . . . . . . . . .
CYNCR9103E: The db2profile file was not found
in the specified User's Home. . . . . . . .
CYNCR9104E: The db2cc.jar and
db2jcc_license_cu.jar files was not found in the
specified JDBC path. . . . . . . . . . .
CYNCR9105E: The specified the installation
directory of DB2 is invalid. . . . . . . . .
CYNCR9106E: The installation cannot connect to
the specified database. . . . . . . . . .
CYNCR9107E: The installation cannot connect to
the specified database. . . . . . . . . .
CYNCR9108E: The installation cannot connect to
the specified database. . . . . . . . . .
CYNCR9109E: The installation cannot connect to
the specified database. . . . . . . . . .
CYNCR9110E: The installation cannot connect to
the specified database. . . . . . . . . .
CYNCR9111E: The installation cannot connect to
the specified database. . . . . . . . . .
CYNCR9112E: NIS is enabled on this machine.
Therefore the option to create users is
unavailable. . . . . . . . . . . . . .
CYNCR9113E: The DB2 instance user's home
directory path fails the required minimum free
disk space check. . . . . . . . . . . .
CYNCR9114E: The installation program failed to
create the bufferpool, tablespace, database, or
tables. You can create the bufferpool, tablespace,
database, or tables manually. . . . . . . .
CYNCR9115E: The DB2 8.2 installation image
directory that was specified is not valid. . . .
CYNCR9200I: Required Field: Managing Server
Host Selection . . . . . . . . . . . .
CYNCR9200W: Some errors occur during
restarting the WebSphere Application Server. . .
CYNCR9201I: Required Field: Database Host
CYNCR9202I: Required Field: Port Number . .
CYNCR9203I: Required Field: Database Instance
User ID . . . . . . . . . . . . . .
CYNCR9204I: Required Field: Database Instance
Password. . . . . . . . . . . . . .
CYNCR9205I: Required Field: Database Schema
User ID . . . . . . . . . . . . . .
CYNCR9206I: Required Field: Database Schema
Password. . . . . . . . . . . . . .
CYNCR9207I: Required Field: Oracle Sqlplus
User . . . . . . . . . . . . . . .
CYNCR9208I: Required Field: Oracle Home . .
Contents
144
144
144
145
145
145
145
146
146
146
146
146
147
147
147
147
148
148
148
148
149
149
149
149
149
149
149
149
149
xv
CYNCR9209I: Required Field: DBA User ID . .
CYNCR9210I: Required Field: DBA Password
CYNCR9211E: The installer was unable to get
the topology information from WebSphere
Application Server. . . . . . . . . . .
CYNCR9211I: The Oracle Home you entered is
invalid . . . . . . . . . . . . . .
CYNCR9212E: The WebSphere Application
Server 6.1 installation image directory that was
specified is not valid. . . . . . . . . . .
CYNCR9213E: The WebSphere Application
Server 6.1 installation image directory that was
specified is not valid. . . . . . . . . . .
CYNCR9214E: An error occurred while trying to
validate the WebSphere Application Server
information entered on the this panel. . . . .
CYNCR9215E: The specified installation
destination of WebSphere is not valid. . . . .
CYNCR9216E: The system temporary space is
too small to install a new WebSphere
Application Server. . . . . . . . . . .
CYNCR9500E: The Visualization Engine
installation failed. . . . . . . . . . . .
CYNCR9501E: The specified port number
(portNumber) is invalid. . . . . . . . . .
CYNCR9601E: An error occurred while trying to
validate the WebSphere Application Server
information entered on this panel. . . . . .
CYNCR9602E: An error occurred while trying to
run WebSphere Application Server's wsadmin
utility. The following are error messages from
wsadmin: “wsadminMsg ” . . . . . . . .
CYNCR9603E: An error occurred while trying to
run WebSphere Application Server's wsadmin
utility. The following are error messages from
wsadmin: “wsadminMsg ” . . . . . . . .
CYNCR9604E: An error occurred while trying to
validate the WebSphere Application Server
information entered on this panel. . . . . .
CYNCR9605E: The -Xrun or -agentlib has
already been configured in the generic JVM
arguments for WebSpere Application Server
server . . . . . . . . . . . . . . .
CYNCR9606E: The Auto Synchronization
Service of the NodeAgent node is disabled.
Before continuing the Data Collector
configuration, make sure the local configuration
repository for WebSphere Application Server is
consistent with the master repository for the
Deployment Manager. . . . . . . . . .
CYNCR9607E: The Auto Synchronization
Service of the NodeAgent node is disabled.
Before continuing the Data Collector
configuration, perform a node synchronization. .
CYNCR9608E: The Auto Synchronization
Service of the NodeAgent node is disabled. The
Data Collector Configuration Tool will perform
a node synchronize action before continuing
with the Data Collector configuration. . . . .
xvi
150
150
150
150
150
150
151
151
151
152
152
152
152
153
153
153
154
154
154
CYNCR9609E: An error occurred while trying to
synchronize node node. The following are error
messages from wsadmin: “wsadminMsg ” . . .
CYNCR9610E: An error occurred while trying to
synchronize node node. . . . . . . . . .
CYNCR9611I: The default GC log file location
orglog is changed to newlog. If you delete the
new GC log file directory after configuration, it
might cause the WebSphere Application Server
not to start up. . . . . . . . . . . . .
CYND Messages: Data Collector . . . . . . .
Data Collector on z/OS . . . . . . . . .
Data Collector on Windows and UNIX . . . .
Byte Code Modification Messages . . . . .
Generic Probe Engine . . . . . . . . .
Request Aggregator . . . . . . . . . .
CYNG Messages: Global Publish Server . . . .
CYNG0001E: The Global Publish Server cannot
determine whether the database is DB2 or
Oracle. . . . . . . . . . . . . . .
CYNG0002E: The Global Publish Server was
unable to establish a database connection. . . .
CYNG0003I: The Global Publish Server's
DbConnectionPool monitoring thread is awake
and running. . . . . . . . . . . . .
CYNG0004W: The Global Publish Server's
monitoring thread in the database connection
pool is replacing an inactive connection. . . .
CYNG0005E: The Global Publish Server's
DbConnectionPool monitoring thread was
unable to replace an inactive connection. . . .
CYNG0006W: The Global Publish Server's
DbConnectionPool monitoring thread is
reclaiming a hung connection. . . . . . . .
CYNG0007E: The Global Publish Server's
DbConnectionPool monitoring thread was
unable to reclaim a hung connection. . . . .
CYNG0008E: An exception occurred while
attempting to get a database connection from
the pool. . . . . . . . . . . . . . .
CYNG0009E: An exception occurred while
attempting to return a database connection to
the pool. . . . . . . . . . . . . . .
CYNG0010E: The Global Publish Server was
unable to open a Global Publish Server
properties file. . . . . . . . . . . . .
CYNG0011E: The Global Publish Server was
unable to determine the IP address to listen on. .
CYNG0012E: The Global Publish Server was
unable to determine the port number to listen
on. . . . . . . . . . . . . . . . .
CYNG0013E: The Global Publish Server was
unable to determine the component ID to
register with the Kernel. . . . . . . . . .
CYNG0014E: The Global Publish Server was
unable to determine the socket backlog value
from the properties file. . . . . . . . . .
CYNG0015E: The Global Publish Server was
unable to determine the connection pool size
value from the properties file. . . . . . . .
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
155
155
155
156
156
190
203
217
218
218
218
218
219
219
219
220
220
220
220
221
221
222
222
222
223
CYNG0016E: The Global Publish Server was
unable to determine the JDBC driver name from
the system environment.. . . . . . . . .
CYNG0017E: The Global Publish Server was
unable to determine the database URL from the
system environment. . . . . . . . . . .
CYNG0018E: The Global Publish Server was
unable to determine the database user from the
system environment. . . . . . . . . . .
CYNG0019E: The Global Publish Server was
unable to determine the database password
from the system environment. . . . . . . .
CYNG0020E: The Global Publish Server was
unable to determine the value of the backup
thread timer from the properties file. . . . .
CYNG0021E: The Global Publish Server was
unable to determine the value of the cleanup
thread timer from the properties file. . . . .
CYNG0022E: The Global Publish Server was
unable to determine the value of the
dequeueing thread timer from the properties
file. . . . . . . . . . . . . . . . .
CYNG0023E: The Global Publish Server was
unable to determine the value of the sampling
thread timer from the properties file. . . . .
CYNG0024E: The Global Publish Server was
unable to determine the value for the token
resolution timeout from the properties file. . .
CYNG0025E: The Global Publish Server was
unable to determine the value of the orphan
resolution timeout from the properties file. . .
CYNG0026E: The Global Publish Server was
unable to determine the value of the thread end
timeout from the properties file. . . . . . .
CYNG0027E: The Global Publish Server was
unable to determine the value of the resolved
transaction timeout from the roperties file. . .
CYNG0028E: The Global Publish Server was
unable to determine the value of the insert
batch size from the properties file. . . . . .
CYNG0029E: The Global Publish Server was
unable to determine the value of the maximum
socket writes from the properties file. . . . .
CYNG0030E: The Global Publish Server was
unable to determine the value of the write
timeout from the properties file. . . . . . .
CYNG0031I: The Global Publish Server
successfully started. . . . . . . . . . .
CYNG0032E: An error occurred while
attempting to start the Global Publish Server.. .
CYNG0033E: An error occurred while
attempting to stop the Global Publish Server.. .
CYNG0034E: An error occurred while
attempting to change the Global Publish Server
log level. . . . . . . . . . . . . . .
CYNG0035E: An error occurred while
attempting to ping the Global Publish Server. .
CYNG0036E: An error occurred while
attempting to run dumpState against the Global
Publish Server. . . . . . . . . . . . .
223
224
224
224
225
225
226
226
227
227
228
228
228
229
229
230
230
230
230
231
231
CYNG0037E: An error occurred while
attempting to contact the Kernel. . . . . . .
CYNG0038E: The system was unable to create a
proxy object to join the Kernel. . . . . . .
CYNG0039E: The Global Publish Server was
unable to join the Kernel as a result of an
incorrectly specified IP address. . . . . . .
CYNG0040E: The Global Publish Server was
able to create a proxy object, but it failed to join
the Kernel. . . . . . . . . . . . . .
CYNG0041E: The Global Publish Server was
unable to start a server socket. . . . . . .
CYNG0042W: The Global Publish Server is
attempting to process a thread end event for an
unknown thread. . . . . . . . . . . .
CYNG0043W: The Global Publish Server is
attempting to process a RequestRecord event for
an unknown thread. . . . . . . . . . .
CYNG0044E: An exception was encountered
while the Global Publish Server was attempting
to process a RequestRecord event. . . . . .
CYNG0045I: Token Token is timing out as a
result of a parent call without a child call. . . .
CYNG0046I: Token Token is timing out as a
result of a child call without a parent call. . . .
CYNG0047I: Token Token is timing out because a
missing Global Publish Server thread end event
is missing. . . . . . . . . . . . . .
CYNG0048E: An exception was caught while
the Global Publish Server was attempting to
restore data from the last database backup
image. . . . . . . . . . . . . . . .
CYNG0049I: The Global Publish Server was
initialized with data stored in the database. The
Token map size is size1, and the Thread map
size is size2. . . . . . . . . . . . . .
CYNG0051E: The Global Publish Server
encountered an exception while attempting to
retrieve a request record from the in-memory
cache. . . . . . . . . . . . . . . .
CYNG0052I: The Global Publish Server has
mapped in-flight tokens tokenList to permanent
tokens returnList. . . . . . . . . . . .
CYNG0053I: A stop request was received. The
Global Publish Server backs up its information
to the database.. . . . . . . . . . . .
CYNG0054E: The Global Publish Server caught
an exception while attempting to back up the
Token map as part of a standard shutdown. . .
CYNG0055E: The Global Publish Server caught
an exception while attempting to back up the
Thread Map as part of a standard shutdown.. .
CYNG0056I: The Global Publish Server
successfully backed up data to the database. . .
CYNG0057E: The Global Publish Server caught
an exception while attempting a graceful
shutdown. . . . . . . . . . . . . .
CYNG0058I: Shutdown of the Global Publish
Server completed successfully. . . . . . . .
CYNG0059I: The Dequeueing Thread started.
Contents
231
231
232
232
232
233
233
233
233
234
234
234
234
235
235
235
235
236
236
236
236
236
xvii
CYNG0060I: The Dequeueing Thread is now
attempting to dequeue count records. . . . .
CYNG0061I: The Global Publish Server's
Dequeueing Thread is attempting to process a
gpsInvokeStart record: processGpsInvokeStart
server server id, thread thread id, token token. . .
CYNG0062I: The Global Publish Server's
Dequeueing Thread is attempting to process a
gpsInvokeEnd record: processGpsInvokeEnd
server server id, thread thread id, token token, star
time startTime. . . . . . . . . . . . .
CYNG0063I: The Global Publish Server's
Dequeueing Thread is attempting to process a
gpsReceiveStart record: processGpsReceiveStart
server server id, thread thread id, token token,
start time startTime. . . . . . . . . . .
CYNG0064I: The Global Publish Server's
Dequeueing Thread is attempting to process a
gpsReceiveEnd record: processGpsReceiveEnd
server server id, thread thread id, token token,
start time startTime. . . . . . . . . . .
CYNG0065I: The Global Publish Server's
Dequeueing Thread is attempting to process a
gpsPutStart record: processGpsPutStart server
server id, thread thread id, token token, start time
startTime. . . . . . . . . . . . . . .
CYNG0066I: The Global Publish Server's
Dequeueing Thread is attempting to process a
gpsPutEnd record: processGpsPutEnd server
server id, thread thread id, token token, start time
startTime. . . . . . . . . . . . . . .
CYNG0067I: The Global Publish Server's
Dequeueing Thread is attempting to process a
gpsGetStart record: processGpsGetStart server
server id, thread thread id, token token, start time
startTime. . . . . . . . . . . . . . .
CYNG0068I: The Global Publish Server's
Dequeueing Thread is attempting to process a
gpsGetEnd record: processGpsGetEnd server
server id, thread thread id, token token, start time
startTime. . . . . . . . . . . . . . .
CYNG0069I: The Global Publish Server's
Dequeueing Thread is attempting to process a
gpsGetEnd record: processRequestRecord server
server id, thread thread id, start time: startTime. .
CYNG0070I: The Global Publish Server's
Dequeueing Thread is attempting to process a
gpsGetEnd record: processThreadEnd server
server id, thread thread id, start time startTime.. .
CYNG0071I: Dequeueing took number
milliseconds. . . . . . . . . . . . .
CYNG0072E: The Global Publish Server
received a corrupt message from the Publish
Server.. . . . . . . . . . . . . . .
CYNG0073I: The Global Publish Server's
Dequeueing Thread is exiting now. . . . . .
CYNG0074I: The Global Publish Server's
Dequeueing Threadhas was killed as a result of
a user action. . . . . . . . . . . . .
CYNG0075I: The BackupThread started. . . .
xviii
237
237
237
237
237
237
238
238
238
238
238
238
239
239
239
239
CYNG0076E: An error occurred while trying to
drop the table GPSTOKEN from the database. .
CYNG0077E: An error occurred while trying to
drop the table GPSTOKENINFO from the
database. . . . . . . . . . . . . . .
CYNG0078E: An error occurred while trying to
drop the table GPSUOE from the database. . .
CYNG0079E: An error occurred while trying to
drop the table GPSUOEINFO from the database.
CYNG0080E: An error occurred while trying to
drop the table GPSREQUEST from the database.
CYNG0081E: An exception was caught while
attempting to create the tables in which the
Global Publish Server backs up its data
structures. . . . . . . . . . . . . .
CYNG0082I: BackupThread stopped. . . . .
CYNG0083I: BackupThread been killed as a
result of user action. . . . . . . . . . .
CYNG0084E: An error occurred while
attempting to back up the Token map. . . . .
CYNG0085E: Backing up the Token map took
number milliseconds. . . . . . . . . . .
CYNG0086E: An error occurred while
attempting to back up the Token map. . . . .
CYNG0087E: An error occurred while
attempting to back up the Thread map. . . .
CYNG0088I: Backing up the Thread map took
number milliseconds. . . . . . . . . . .
CYNG0089E: An error occurred while
attempting to back up the Thread map. . . .
CYNG0090I: The Global Publish Server's
CleanupThread started. . . . . . . . . .
CYNG0091I: The Global Publish Server's
CleanupThread declined to prune thread
threadId on server ServerId because the Publish
Server had not yet been notified of sampling
values. . . . . . . . . . . . . . .
CYNG0092I: Token token is fully resolved, so the
system is removing it from memory.. . . . .
CYNG0093I: Thread ThreadId on server ServerId
has no unresolved tokens, so the system is
removing it from memory. . . . . . . . .
CYNG0094I: The Global Publish Server's
CleanupThread took number milliseconds. . . .
CYNG0095E: An exception was caught during
the CleanupThread operation while attempting
clean up the Token and Thread maps. . . . .
CYNG0096I: The Global Publish Server's
CleanupThread finished executing. . . . . .
CYNG0097I: The Global Publish Server's
CleanupThread was killed. . . . . . . . .
CYNG0098I: The Global Publish Server's
SamplingThread started.. . . . . . . . .
CYNG0099I: The Global Publish Server's
SamplingThread could not find information in
memory for a thread end event. . . . . . .
CYNG0100I: During a sampling check, the
Global Publish Server failed to find a linked
thread. It is sending it back to queue. . . . .
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
239
240
240
240
240
241
241
241
241
242
242
242
242
242
243
243
243
243
243
243
244
244
244
244
244
CYNG0101I: The Global Publish Server is
notifying Publish Server componentId that thread
threadId on server serverId: boolean . . . . .
CYNG0102E: An exception was caught during
SamplingThread operation. . . . . . . . .
CYNG0103I: SamplingThread execution took
number milliseconds. . . . . . . . . . .
CYNG0104E: An exception was caught during
SamplingThread operation. . . . . . . . .
CYNG0105I: SamplingThread is exiting. . . .
CYNG0106I: SamplingThread was killed as a
result of user action. . . . . . . . . . .
CYNG0107I: The Global Publish Server's
MonitoringThread started. . . . . . . . .
CYNG0108I: BackupThread is dead. The Global
Publish Server will start a new one. . . . . .
CYNG0109I: The Global Publish Server is
unable to contact or stop BackupThread, which
is null or does not exist. . . . . . . . . .
CYNG0110I: CleanupThread is dead. The Global
Publish Server will start a new one. . . . . .
CYNG0111I: The Global Publish Server is unable
to contact or stop CleanupThread, which is null
or does not exist. . . . . . . . . . . .
CYNG0112I: DequeueingThread is dead. The
Global Publish Server will start a new one. . .
CYNG0113I: The Global Publish Server is
unable to contact or stop DequeueingThread,
which is null or does not exist. . . . . . .
CYNG0114I: SamplingThread is dead. The
Global Publish Server will start a new one. . .
CYNG0115I: The Global Publish Server is
unable to contact or stop SamplingThread,
which is null or does not exist. . . . . . .
CYNG0116E: An exception was caught during
MonitorThread operation. . . . . . . . .
CYNG0117I: SamplingThread is exiting. . . .
CYNG0118I: The Global Publish Server's
SamplingThread was killed by user action. . .
CYNG0119E: A client has attempted to connect
to the Global Publish Server and failed as a
result of a network error. . . . . . . . .
CYNG0120I: Publish Server psId connected to
the Global Publish Server. . . . . . . . .
CYNG0121I: An exception occurred in the
Socket Listener. . . . . . . . . . . . .
CYNG0122E: The Global Publish Server was
unable to open a server socket on port Port. . .
CYNG0123I: A VEGateway connected to the
Global Publish Server. . . . . . . . . .
CYNG0124E: Communication between the
front-end and the Global Publish Server failed. .
CYNG0125E: Communication between the
front-end and the Global Publish Server failed. .
CYNG0126W: A format exception occurred
while parsing property propName. The default
value is being used. . . . . . . . . . .
CYNG0127E: An exception occurred while the
Global Publish Server was sending data to the
Archive Agent. . . . . . . . . . . . .
CYNI Messages: Publish Server . . . . . . .
245
245
245
245
245
246
246
246
246
246
246
246
246
247
247
247
247
247
247
248
248
248
248
248
249
249
CYNI0001E: An error occurred while trying to
retrieve the command agent for Data Collector
probeId. . . . . . . . . . . . . . .
CYNI0002E: An error occurred while trying to
get PerfSummary for Data Collector probeId. . .
CYNI0003E: An error occurred while trying to
get PerfSnapshot for Data Collector probeId. . .
CYNI0004E: An error occurred while trying to
get ClusterRuntime for Data Collector probeId. .
CYNI0005E: An error occurred while trying to
get ServerRuntime for Data Collector probeId.. .
CYNI0006E: An error occurred while trying to
get EJBComponents for Data Collector probeId. .
CYNI0007E: An error occurred while trying to
get WebAppComponents for Data Collector
probeId. . . . . . . . . . . . . . .
CYNI0008E: An error occurred while trying to
get Applications for Data Collector probeId. . .
CYNI0009E: An error occurred while trying to
get ConnectorConnectionPools for Data
Collector probeId. . . . . . . . . . . .
CYNI0010E: An error occurred while trying to
get ExecuteQueues for Data CollectorprobeId. . .
CYNI0011E: An error occurred while trying to
get JDBCConnectionPools for Data Collector
probeId. . . . . . . . . . . . . . .
CYNI0012E: An error occurred while trying to
get JTARuntimes for Data Collector probeId. . .
CYNI0013E: An error occurred while trying to
get JMSRuntime for Data Collector probeId. . .
CYNI0014E: An error occurred while trying to
get ORBData for Data Collector probeId. . . .
CYNI0015E: An error occurred while trying to
get Datasource for Data Collector probeId. . . .
CYNI0016E: An error occurred while trying to
get SMFRecords for Data Collector probeId. . .
CYNI0017E: An error occurred while trying to
get RegionInfoIntf for Data Collector probeId. . .
CYNK Messages: Kernel. . . . . . . . . .
CYNK0001E: Property Property was not found in
file File. . . . . . . . . . . . . . .
CYNK0002I: Relationship record
RelationshipRecord was updated, retrieved,
deleted, or created. The client and server IDs
associated with the record are ClientId and
ServerId. . . . . . . . . . . . . . .
CYNK0003I: Service Service of component
Component on platform Platform on host and
port HostAndPort failed to renew the contract
with the Kernel. . . . . . . . . . . .
CYNK0004I: Service Service of component
Component on platform Platform on host and
port HostAndPortdid not renewed the contract
on time. The Kernel is trying to ping the
component. . . . . . . . . . . . . .
CYNK0005I: The contract of service Service of
component Component on platform Platform on
host and port HostAndPort expires at
TimeExpires. . . . . . . . . . . . . .
249
250
250
250
250
250
251
251
251
251
252
252
252
252
252
253
253
253
253
253
254
254
254
249
249
Contents
xix
CYNK0006I: Service Service of component
Component on platform Platform on host and
port HostAndPort has not renewed the contract
with the Kernel on time, but the Kernel was
able to ping the service. . . . . . . . . .
CYNK0007I: The Kernel RMI server has started
and is listening at port number Port. . . . .
CYNK0008I: The Kernel started. . . . . . .
CYNK0009I: The Kernel has notified Publish
Server PublishServer of trapping server
unavailability. The component ID of the
unavailable server is ComponentId. . . . . .
CYNK0010D: Service Service of component
Component on platform Platform on host and
port HostAndPort disconnected from the Kernel. .
CYNK0011D: All proxy objects were requested.
Service Service of component Component on
platform Platform on host and port HostAndPort
was returned. . . . . . . . . . . . .
CYNK0012D: All clone proxies with generic ID
GenericId were requested. Service Service of
component Component on platform Platform on
host and port HostAndPort was returned. . . .
CYNK0013D: All clone proxies with the
specified generic ID were requested. No clone
was found. . . . . . . . . . . . . .
CYNK0014D: All clone proxies with generic ID
GenericId were requested. Proxy Proxy was
returned. . . . . . . . . . . . . . .
CYNK0015D: All clone proxies with generic ID
GenericId were requested. No clone was found. .
CYNK0016D: The Kernel is obtaining
monitoring level information from Data
Collector DataCollector. DataCollector is found to
be running at Location. . . . . . . . . .
CYNK0017I: A lookup request was received by
the Kernel. Service Service of component
Component on platform Platform on host and
port HostAndPort was returned. . . . . . .
CYNK0018I: The time associated with the
service registered with the Kernel is out of sync
with the time associated with the Kernel. The
time reported by the service is TimeService. The
time reported by the Kernel is TimeKernel. . . .
CYNK0019I: The volume statistics for Data
Collector DataCollector were reported by the
Publish Server. The incremental volume is
IncrementalVolume. The total volume is
TotalVolume. . . . . . . . . . . . . .
CYNK0020I: Service Service of component
Component on platform Platform on host and
port HostAndPort has requested a contract
renewal with the Kernel. . . . . . . . .
CYNK0021I: The component ID ComponentId
conflicts with the one registered. . . . . . .
CYNK0022I: Service Service of component
Component on platform Platform on host and
port HostAndPort has registered with the Kernel.
CYNK0023D: The Kernel is retrieving a list of
enabled and available Data Collectors. The
number of results is NumberResults. . . . . .
xx
254
254
254
254
255
255
255
255
255
255
255
256
256
256
256
256
256
257
CYNK0024D: The Kernel is retrieving a list of
disabled Data Collectors. The number of results
is NumberResults. . . . . . . . . . . .
CYNK0025I: The configuration repository was
Result successfully.. . . . . . . . . . .
CYNK0026I: System configuration was Result
successfully. . . . . . . . . . . . . .
CYNK0027I: The Kernel is broadcasting system
configuration to service Service of component
Component on platform Platform on host and
port HostAndPort. . . . . . . . . . . .
CYNK0028I: The configuration for Data
Collector with ID DataCollectorId was
successfully created. . . . . . . . . . .
CYNK0029D: All Data Collector configuration
information was successfully retrieved. . . . .
CYNK0030I: The Kernel is broadcasting Data
Collector configuration information to service
Service of component Component on platform
Platform on host and port HostAndPort. . . . .
CYNK0031I: The configuration for trap Trap
with ID TrapId was successfully Result. . . . .
CYNK0032I: The Kernel is preparing to
broadcast configuration information for the trap
with ID TrapId. . . . . . . . . . . . .
CYNK0033I: Configuration information for the
trap with ID TrapId was found to be deleted.
The Kernel is preparing to broadcast it to
Publish Servers. . . . . . . . . . . .
CYNK0034I: No Publish Server was found to be
responsible for evaluating the trap with ID
TrapId. . . . . . . . . . . . . . . .
CYNK0035I: The Publish Server with
component ID ComponentId was found to be
responsible for evaluating the trap with ID
TrapId. . . . . . . . . . . . . . . .
CYNK0036I: The Kernel is broadcasting
configuration information for the trap with ID
TrapId to the Publish Server with component ID
ComponentId.. . . . . . . . . . . . .
CYNK0037I: The schedule with ID ScheduleId
was successfully Result. . . . . . . . . .
CYNK0038I: All schedules were successfully
retrieved. . . . . . . . . . . . . . .
CYNK0039I: The Kernel is broadcasting the
schedule to service Service of component
Component on platform Platform on host and
port HostAndPort. . . . . . . . . . . .
CYNK0040I: The Kernel shut down. . . . . .
CYNK0041I: SMF data for Data Collector
DataCollector was already collected by Publish
Server PublishServer. . . . . . . . . . .
CYNK0042I: An SMF record was created for
Data Collector DataCollector and was collected
by Publish Server PublishServer. . . . . . .
CYNK0043W: The request ID is unknown. . .
CYNK0044E: There was an undefined Kernel
component ID in Kernel Kernel. . . . . . .
CYNK0045E: The Archive Agent proxy object
was not found. The Kernel will retry in
TimeRetry seconds.. . . . . . . . . . .
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
257
257
257
257
257
257
257
258
258
258
258
258
258
258
258
259
259
259
259
259
259
259
CYNK0046I: Data Collector DataCollector was
found to be Result. The record was successfully
sent to Archive Agent ArchiveAgent. . . . . .
CYNK0047I: Configuration information for Data
Collector with ID DataCollectorId was
successfully retrieved. . . . . . . . . .
CYNK0048W: The SMF key is unknown. . . .
CYNK0049I: All Scheduled configuration
information was successfully retrieved . . . .
CYNK0050D: The Global Publish Server mask is
not available from the properties file. A new one
is being created. . . . . . . . . . . .
CYNK0051W: Global Publish Server mask
GpsMask in the database for Data Collector
DataCollector seems to be corrupted. . . . . .
CYNK0052I: The current mask value for
GPSMASK obtained from the database is
MaskValue. . . . . . . . . . . . . .
CYNK0053I: There is no record in the
GPSMASK table for Data Collector DataCollector.
CYNK0054W: Exception Exception occurred
while retrieving the counter from the database
for GPSMASK. . . . . . . . . . . . .
CYNK0055W: Exception Exception occurred
while generating and updating the counter, so
the Kernel is trying again for a second time. . .
CYNK0056W: Exception Exception occurred for
the second time while generating and updating
the counter, so the Kernel is aborting token
generation for GPSMASK. . . . . . . . .
CYNK0057I: The Kernel is calculating the mask
for Data Collector DataCollector. . . . . . .
CYNK0058I: Exception Exception occurred while
converting the mask string stored in the
database to an integer. . . . . . . . . .
CYNK0059I: The Kernel is returning GPSMASK
GpsMask for Data Collector DataCollector. . . .
CYNK0060I: There is no Global Publish Server
counter in the database, so the system is
initializing the counter to 1. . . . . . . .
CYNK0061I: A Global Publish Server mask
exists for Data Collector DataCollector in the
configuration. . . . . . . . . . . . .
CYNK0062I: A Global Publish Server mask does
not exist for the Data Collector. The Kernel is
creating a new one. . . . . . . . . . .
CYNK0063I: The HTTP codebase server started
at listening port ListeningPort. . . . . . . .
CYNK0064I: The .jar file JarFile was requested
and downloaded successfully. . . . . . . .
CYNK0065I: The Request For Stub server
started at listening port ListeningPort. . . . .
CYNK0066E: IP address IpAddress is not valid.
Code download fails. . . . . . . . . . .
CYNK0067I: Service Service successfully
registered with the Kernel. . . . . . . . .
CYNK0068E: The Kernel was unable to be
joined. The java.rmi.server.codebase property is
set to PropertyValue. . . . . . . . . . .
260
260
260
260
260
260
260
260
261
261
261
261
261
261
261
261
262
262
262
262
262
262
262
CYNK0069E: Database exception Exception
occurred while querying or updating records in
tables. . . . . . . . . . . . . . . .
CYNK0070E: An exception occurred while
starting the Kernel. Kernel Kernel is being
stopped. . . . . . . . . . . . . . .
CYNK0071I: Kernel WatchDog Service Started .
CYNM Messages: Message Dispatcher . . . . .
CYNM0001E: An exception occurred while
attempting to retrieve and unload the system
configuration from the Kernel.. . . . . . .
CYNM0002E: The system configuration from the
Kernel is null. . . . . . . . . . . . .
CYNM0003E: An exception occurred when the
Message Dispatcher was leaving the Kernel. . .
CYNM0004E: An exception occurred while
creating EmailEngine. . . . . . . . . .
CYNM0005E: An exception occurred while
creating TrapDispatcher. . . . . . . . . .
CYNM0006I: TrapDispatcher has started. . . .
CYNM0007I: TrapDispatcher has stopped. . . .
CYNM0008E: An exception occurred while
parsing the SNMP port string. . . . . . . .
CYNM0009E: An exception occurred while
trying to contact the Kernel. . . . . . . .
CYNM0010I: The Message Dispatcher is
starting. . . . . . . . . . . . . . .
CYNM0011E: The system was unable to
unmarshall the TrapDispatcher proxy object. . .
CYNM0012E: An exception occurred while
creating EmailEngine. . . . . . . . . .
CYNM0013E: The system property
component.id was not specified. . . . . . .
CYNM0014E: The system property
component.listen.port was not specified. . . .
CYNM0015E: The system property
template.directory was not specified. . . . .
CYNM0016E: The system property smtp.host
was not specified. . . . . . . . . . . .
CYNM0017E: The system property
component.listen.port is not valid. . . . . .
CYNM0018E: An exception occurred while
initializing SNMPV1Api. . . . . . . . .
CYNM0019E: An exception occurred while
setting SNMP peer parameters. . . . . . .
CYNM0020E: An exception occurred while
creating EmailEngine. . . . . . . . . .
CYNM0021E: System property
properties.filename is not defined in mdctl.sh. .
CYNM0023E: An exception occurred while
creating EmailEngine. . . . . . . . . .
CYNP Messages: Publish Server . . . . . . .
CYNP0001E: An exception occurred while
creating AaGateway. . . . . . . . . . .
CYNP0002E: An exception occurred while
creating PsGateway. . . . . . . . . . .
CYNP0003I: The Publish Server is establishing a
relationship between probe probe and Publish
Server psId. . . . . . . . . . . . . .
Contents
263
263
263
263
263
263
264
264
264
264
264
264
265
265
265
265
265
265
266
266
266
266
266
267
267
267
267
267
268
268
xxi
CYNP0004E: An exception occurred while
registering the Publish Server-Data Collector
relationship with the Kernel. . . . . . . .
CYNP0005E: An exception occurred while
creating and starting PMITask for probe
octigateID. . . . . . . . . . . . . .
CYNP0006E: The Publish Server got a GC End
event before getting a GC Start event for probe
execCtx. . . . . . . . . . . . . . .
CYNP0007W: The Publish Server got a GC Start
event when there is already a GC Start event
pending for execution context execCtx. . . . .
CYNP0008W: The Publish Server failed sending
data to the Archive Agent. . . . . . . . .
CYNP0009E: An exception occurred processing
Method Record. . . . . . . . . . . .
CYNP0010W: The Publish Server is removing
the execution context for the request type
requestType from the corrupted requests. . . .
CYNP0011W: The Publish Server is dropping
the incoming record for execution context
execCtx because this thread is corrupted. . . .
CYNP0012E: An exception occurred while
processing RequestLevelRecord. . . . . . .
CYNP0013W: The Publish Server dropped a
record for the execution context execCtx. . . .
CYNP0014W: An exception occurred while
sending the request to PsGateway. . . . . .
CYNP0015W: There is a missing main request
for the nested request with type type on thread
execCtx. . . . . . . . . . . . . . .
CYNP0016W: There is a missing method trace
for the end of the request on thread execCtx. . .
CYNP0017W: The Publish Server got a new
request when there was already another request
pending on thread execCtx . . . . . . . .
CYNP0018W: Matching Start is null for the
request type type on thread execCtx. . . . . .
CYNP0019I: RequestRecord is corrupted. The
matching request type is matchingrequesttype.
The matching stack depth is matchingStackDepth.
The current request type is currentRequestType.
The current stack depth is currentStackDepth. . .
CYNP0020W: The start request is missing for
the method trace on thread execCtx. . . . . .
CYNP0021I: The Publish Server is inferring a
request for method methodId. . . . . . . .
CYNP0022E: The Publish Server could not find
the CLASSLOAD record corresponding to the
method with ID methodId. . . . . . . . .
CYNP0023I: The maximum number of records
per request has been reached. So the Publish
Server dropped noofrecords records for execution
context execCtx.. . . . . . . . . . . .
CYNP0024I: The Publish Server is deleting a
request for thread of ID threadId, because the
time limit of timeLimit has elapsed. . . . . .
CYNP0025I: The time difference between the
Publish Server and probe probeId is
timeDiffmilliseconds. . . . . . . . . . .
xxii
268
268
268
269
269
269
269
270
270
270
270
270
271
271
271
272
272
272
272
273
273
273
CYNP0026E: A exception occurred while getting
the time for probe probeId. . . . . . . . .
CYNP0027W: The Publish Server could not
retrieve the method detail corresponding to the
method with ID methodId for the execution
context execCtx.. . . . . . . . . . . .
CYNP0028W: An exception occurred while
parsing method of ID methodId for the execution
context execCtx.. . . . . . . . . . . .
CYNP0029E: The Publish Server was unable to
load the system configuration from the Kernel. .
CYNP0030E: The Publish Server was unable to
start ProbeStatsManager. . . . . . . . .
CYNP0031E: The Publish Server was unable to
start ResourceStatsManagerTimer. . . . . .
CYNP0032E: The Publish Server was unable to
start AVMDataSource. . . . . . . . . .
CYNP0033E: The Publish Server was unable to
start AAProducerResetTimer. . . . . . . .
CYNP0034I: The Publish Server daemon is
listening on the socket at host host on port port. .
CYNP0035E: The Publish Server was unable to
start. The socket is already bound to port port. .
CYNP0036E: An exception occurred when the
Message Dispatcher was leaving the Kernel. . .
CYNP0037I: The Publish Server is shutting
down and leaving the Kernel service at host host
on port port. . . . . . . . . . . . . .
CYNP0038E: An exception occurred while
accepting the connection from the Data
Collector. . . . . . . . . . . . . . .
CYNP0039E: An exception occurred while
reading INIT records from the Data Collector. .
CYNP0040W: An unknown initialization data
type of recType was sent to the Publish Server. .
CYNP0041E: The socket attached to the Publish
Server threw an exception. data, probeinfo . . .
CYNP0042E: An exception occurred while the
Publish Server was reading data from the
socket. data, probeinfo . . . . . . . . . .
CYNP0043E: An exception occurred while the
Publish Server was closing the data socket. data,
probeinfo . . . . . . . . . . . . . .
CYNP0044I: The Publish Server is shutting
down and leaving the Kernel service serviceId. .
CYNP0045W: The Publish Server received an
unexpected query of type queryType.. . . . .
CYNP0046E: The Publish Server got a null
system configuration from the Kernel. . . . .
CYNP0047E: The Publish Server received wrong
record data for the packet header record record1,
record2, record3. . . . . . . . . . . . .
CYNP0048E: An exception occurred with the
Publish Server during communication with
probe probeId. . . . . . . . . . . . .
CYNP0049E: A communication time out
occurred when the probe was communicating
with the Publish Server. . . . . . . . . .
CYNP0050I: An unexpected exception occurred
with the socket of Data Collector probeId. . . .
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
273
274
274
274
274
275
275
275
275
275
276
276
276
276
276
277
277
277
277
277
278
278
278
278
278
CYNP0051I: An unexpected exception occurred
with the socket of Data Collector probeId. . . .
CYNP0052E: An exception occurred while the
Publish Server was being stopped. . . . . .
CYNP0053W: The Publish Server was unable to
figure out the mod level from the request of the
Data Collector, so it is using the default mod
level. . . . . . . . . . . . . . . .
CYNP0054E: An exception occurred while the
Publish Server was sending data to the Archive
Agent. . . . . . . . . . . . . . . .
CYNP0055W: A format exception occurred
while parsing property propName. The default
value defaultValue is being used. . . . . . .
CYNP0056W: An exception occurred while
getting PMI data from the administrative server
adminServer at port port of node nodeName of
application server appserverName. . . . . . .
CYNP0057E: An exception occurred while
computing portal statistics in the Publish Server.
CYNP0058E: The Publish Server was unable to
get the command agent for probe probeId. . . .
CYNP0059E: An exception occurred while
getting the time difference for the probe probeId..
CYNP0060E: An exception occurred when the
Publish Server was stopped. . . . . . . .
CYNP0061E: An exception occurred when the
Publish Server was restarted. . . . . . . .
CYNP0062W: The Archive Agent buffer was
exceeded.. . . . . . . . . . . . . .
CYNP0063E: An exception occurred while
communicating with the Kernel to look up the
Archive Agent. . . . . . . . . . . . .
CYNP0064E: An exception occurred while the
Publish Server was communicating with the
Archive Agent. . . . . . . . . . . . .
CYNP0065E: An exception occurred while the
timeout checker was pruning active requests in
the Publish Server.. . . . . . . . . . .
CYNP0066E: An exception occurred when the
Publish Server was started. . . . . . . . .
CYNP0067I: The Publish Server received an
availability notification from the Kernel
regarding the status of Data Collector probeId.
The status is staus.. . . . . . . . . . .
CYNP0068I: The Publish Server is closing a
socket that is not valid for Data Collector
probeId. . . . . . . . . . . . . . .
CYNP0069W: The socket is still valid with Data
Collector probeID, so the Publish Server is not
closing the socket. . . . . . . . . . . .
CYNP0070W: The Publish Server got a GC End
event without getting GC Start event execCtx. .
CYNP0071I: The Publish Server is registering
probe probeId with DCAvailabilityChecker.. . .
CYNP0072I: An exception occurred while
registering probe probeId with
DCAvailabilityChecker. . . . . . . . . .
CYNP0073I: The Publish Server is unregistering
probe probeId with DCAvailabilityChecker.. . .
279
279
279
279
279
280
280
280
280
280
281
281
281
282
282
282
282
282
283
283
283
283
283
CYNP0074E: An exception occurred in
ProbeStatsManager. . . . . . . . . . .
CYNP0075I: The Publish Server is creating an
IMSComplex for complex. . . . . . . . .
CYNP0076I: Probe probeId has joined complex
complex. . . . . . . . . . . . . . .
CYNP0077I: Probe probeId has left complex
complex. . . . . . . . . . . . . . .
CYNP0078I: The request is corrupted for
message of ID msgId. . . . . . . . . . .
CYNP0079W: SNMP Agent is not available. . .
CYNP0080E: An exception occurred while the
Publish Server was sending SNMP Trap. . . .
CYNP0081W: Email Engine is not available. . .
CYNP0082E: An exception occurred while the
Publish Server was sending Email Trap. . . .
CYNP0083W: The Publish Server is deleting the
request of message ID msgId because the time
limit of timeout has elapsed. . . . . . . .
CYNP0084W: The Publish Server is deleting the
Global Publish Server request of message ID
msgId because the time limit of timeout has
elapsed. . . . . . . . . . . . . . .
CYNP0085W: The Publish Server received a
response of null for SMF Info for the probe
probeId. . . . . . . . . . . . . . .
CYNP0086E: The Publish Server received a
response of null for SMFDaily Service for the
probe probeIdn. . . . . . . . . . . . .
CYNP0087E: An exception occurred while
parsing SMF Info from the probe probeId. . . .
CYNP0088W: The Publish Server dropped a
record for the execution context execCtx. . . .
CYNQ Messages: Port Consolidator . . . . . .
CYNQ0001E: Port Consolidator services failed
to start. . . . . . . . . . . . . . .
CYNQ0002I: The Port Consolidator started
successfully and its services are up and running.
CYNQ0003E: The Port Consolidator failed to
stop a service. . . . . . . . . . . . .
CYNQ0004I: Port Consolidator service
serviceName has status status. . . . . . . .
CYNQ0005E: The Port Consolidator failed to
ping service serviceName. . . . . . . . .
CYNQ0006E: The Port Consolidator failed to list
services. . . . . . . . . . . . . . .
CYNQ0007E: The Port Consolidator failed to
remove services. . . . . . . . . . . .
CYNQ0008E: There is an invalid RMI port
number. . . . . . . . . . . . . . .
CYNQ0009E: There is an unknown host name
for java.rmi.server.hostname. . . . . . . .
CYNQ0010E: There is an invalid
max.ping.failure property. . . . . . . . .
CYNQ0011E: System property am.home has not
been specified. . . . . . . . . . . . .
CYNQ0012E: An error occurred when
populating properties from property file
filename. . . . . . . . . . . . . . .
CYNQ0013E: KernelProxyService failed to
export to port portNum. . . . . . . . . .
Contents
284
284
284
284
284
284
285
285
285
285
285
286
286
286
286
286
287
287
287
287
287
288
288
288
288
288
289
289
289
xxiii
CYNQ0014E: The Port Consolidator failed to
marshall KernelProxyService. . . . . . . .
CYNQ0015E: KernelProxyService failed to join
the Kernel. . . . . . . . . . . . . .
CYNQ0016I: KernelProxyService started
successfully. . . . . . . . . . . . . .
CYNQ0017I: KernelProxyService stopped
successfully. . . . . . . . . . . . . .
CYNQ0018E: ProbeControllerProxyService failed
to export to port portNum. . . . . . . . .
CYNQ0019E: The Port Consolidator failed to
marshall ProbeControllerProxyService. . . . .
CYNQ0020E: ProbeControllerProxyService failed
to join the Kernel. . . . . . . . . . . .
CYNQ0021I: ProbeControllerProxyService
started successfully. . . . . . . . . . .
CYNQ0022I: ProbeControllerProxyService
stopped successfully. . . . . . . . . . .
CYNQ0023E: CommandAgentProxyService
failed to export to port port. . . . . . . .
CYNQ0024E: The Port Consolidator failed to
marshall CommandAgentProxyService.. . . .
CYNQ0025E: CommandAgentProxyService
failed to join the Kernel. . . . . . . . . .
CYNQ0026I: CommandAgentProxyService
started successfully. . . . . . . . . . .
CYNQ0027I: CommandAgentProxyService
stopped successfully. . . . . . . . . . .
CYNS Messages: Common Services Address Space
CYNS0000E : CYN1 TASK ALREADY ACTIVE
CYNS0001W : START CIB NOT FREED . . .
CYNS0002I : CYN1 READY TO ACCEPT
COMMANDS . . . . . . . . . . . .
CYNS0003E : INVALID COMMAND TYPE . .
CYNS0004I : command text. . . . . . . .
CYNS0005I : STOP COMMAND ACCEPTED
CYNS0006I : STOP PENDING
. . . . . .
CYNS0007I : CYN1 NOW ACTIVE . . . . .
CYNS0008I : CYN1 NOW INACTIVE . . . .
CYNS0009E : PARM FIELD IS MISSING OR
INCORRECT . . . . . . . . . . . .
CYNS0010E : UNKNOWN COMMAND . . .
CYNS0011E : INVALID DUMP PARAMETERS
CYNS0012E : MEMORY NOT AVAILABLE . .
CYNS0013I: AAAAAAAA XXXXXXXX
XXXXXXXX XXXXXXXX XXXXXXXX|................ .
CYNS0014E : SYSLOG TASK ENDED - CYN1
ENDING . . . . . . . . . . . . . .
CYNS0015E : REMOTE OPERATOR TASK
ENDED - CYN1 ENDING . . . . . . . .
CYNS0016E : COMMAND AREA
ALLOCATION FAILED . . . . . . . . .
CYNS0017I : STATS OPTION NOW SET . . .
CYNS0018E : UNKNOWN STATS OPTION. NO
ACTION . . . . . . . . . . . . . .
CYNS0023I : TRACE OPTION NOW SET . . .
CYNS0024E : UNKNOWN TRACE OPTION.
NO ACTION . . . . . . . . . . . .
CYNS0025E : SYSLOG TASK NOT ACTIVE. NO
ACTION . . . . . . . . . . . . . .
xxiv
289
290
290
290
290
290
291
291
291
291
291
291
292
292
292
292
292
292
293
293
293
293
293
294
294
294
295
295
295
295
296
296
296
296
297
297
297
CYNS0026I : SPINLOG COMMAND
ACCEPTED . . . . . . . . . . . . .
CYNS0027E : SYSLOG AREA ALLOCATION
FAILED . . . . . . . . . . . . . .
CYNS0028E : SYSLOG DATASET OPEN
FAILED . . . . . . . . . . . . . .
CYNS0029E : SYSLOG DATASET CLOSE
FAILED . . . . . . . . . . . . . .
CYNS0033E : INVALID ZAP PARAMETERS . .
CYNS0034E : ADDRESS CONTENTS
MISMATCH . . . . . . . . . . . . .
CYNS0035I : STAMP OPTION NOW SET . . .
CYNS0036E : UNKNOWN STAMP OPTION.
NO ACTION . . . . . . . . . . . .
CYNS0037E : ERROR LINKING TO CYN1CALL
FROM CYN1FU83. . . . . . . . . . .
CYNS0038E : INVALID CPU PARAMETERS . .
CYNS0039I: ACCUMULATED CPU FOR ASID
XXXX: ssss.sss . . . . . . . . . . . .
CYNS0040I: ASSB_TIME_ON_IFA ASID XXXX:
rrrr.rrr . . . . . . . . . . . . . . .
CYNS0041I: ASSB_TIME_ON_CP ASID XXXX:
ssss.sss . . . . . . . . . . . . . .
CYNS0042I: ASSB_TIME_IFA_ON_CP ASID
XXXX: tttt.ttt . . . . . . . . . . . .
CYNS0043E: INVALID ERBSMFI RETURN
CODE: nnnnn . . . . . . . . . . . .
CYNS0045I: CYN1 ID: CYN1DRVR vv.ll.uu
mm/dd/yy hh.mn . . . . . . . . . .
CYNS0100E: NO MORE ENTRY IN SERVER
DIRECTORY . . . . . . . . . . . .
CYNS0101E: NO MORE ENTRY IN
SERVER/CONTAINER TABLE . . . . . .
CYNS0102E: NO MORE ENTRY IN SERVER
SECTION POOL . . . . . . . . . . .
CYNS0103E: NO MORE ENTRY IN BEAN
SECTION POOL . . . . . . . . . . .
CYNS0104E: NO MORE ENTRY IN BEAN
METHOD SECTION POOL . . . . . . .
CYNS0108E: NO MORE ENTRY IN
HTTPSESSMGR SECTION POOL . . . . .
CYNS0109E: NO MORE ENTRY IN WEBAPP
SECTION POOL . . . . . . . . . . .
CYNS0110E: NO MORE ENTRY IN SERVLET
SECTION POOL . . . . . . . . . . .
CYNS0105I: RECEIVING A 120 SMF RECORD
OF SUBTYPE 3 . . . . . . . . . . . .
CYNS0106I: RECEIVING A 120 SMF RECORD
OF SUBTYPE 6 . . . . . . . . . . . .
CYNS0107I : RECEIVING A 120 SMF RECORD
OF SUBTYPE 8 . . . . . . . . . . . .
CYNVE Messages: Application Monitor . . . .
CYNVE0000E: username Your login attempt was
unsuccessful. . . . . . . . . . . . .
CYNVE0002E: A system error has occurred. . .
CYNVE0002E: A system error has occurred.
Check VE log files to get more information
about the error. . . . . . . . . . . . .
CYNVE0003E: You do not have permission to
access this feature.. . . . . . . . . . .
CYNVE0004E: Enter your user name. . . . .
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
297
297
298
298
298
298
299
299
299
299
300
300
300
300
301
301
302
302
302
302
302
302
302
302
302
302
302
303
303
303
303
304
304
CYNVE0005E: Enter your Password. . . . .
CYNVE0006E: serverID The server was not
found by the ServerID. . . . . . . . . .
CYNVE0007E: serverID An error occurred while
trying to look up the Data Collector. . . . .
CYNVE0008E: cloneID The Data Collector was
not found by Kernel.
. . . . . . . . .
CYNVE0009E: genericID The Data Collector
cannot be found by Kernel. . . . . . . .
CYNVE0010E: Your license has expired for
product : product. . . . . . . . . . . .
CYNVE0011E: The Product does not have a
valid license enrolled. . . . . . . . . .
CYNVE0012W: You are now using the
temporary license. You need to enroll a license
for product : product within 60 days starting
from today : date To perform this operation,
refer to the Installation Guide. . . . . . .
CYNVE0013W: You are still using the temporary
license. Your Try and Buy license will expire
after days. You need to enroll a license for
product: product To perform this operation, refer
to the Installation Guide. . . . . . . . .
CYNVE0014E: An error occurred during the
license Initialization or validation and the return
status is : status. . . . . . . . . . . .
CYNVE0015E: The login page cannot be
displayed because the session could not be
created. . . . . . . . . . . . . . .
CYNVE0018W: You are now using the
temporary license. You need to enroll license for
this product within 60 days starting from today
: date . . . . . . . . . . . . . . .
CYNVE0019W: You are still using the temporary
license. Your Try and Buy license will expire
after days. . . . . . . . . . . . . .
CYNVE0020E: Cannot delete account. . . . .
CYNVE0021E: Cannot delete Admin account.
CYNVE0022E: Cannot delete account, because it
is connected to a report.
. . . . . . . .
CYNVE0023I: Account deleted successfully. . .
CYNVE0030E: User Name: UserName already
exists . . . . . . . . . . . . . . .
CYNVE0031I: User account created.
. . . .
CYNVE0032E: User Name: UName already
exists on the system. . . . . . . . . . .
CYNVE0040E: First Name: FName is not valid.
CYNVE0041E: Last Name: LName is not valid.
CYNVE0042E: User Name: UserName is not
valid. . . . . . . . . . . . . . . .
CYNVE0043E: OS User Name: OsName is not
valid. . . . . . . . . . . . . . . .
CYNVE0044E: Email: emailName entered is not
valid. . . . . . . . . . . . . . . .
CYNVE0045E: Role is not selected. . . . . .
CYNVE0046E: Account form validation failed.
CYNVE0047I: Account form validation
successful. . . . . . . . . . . . . .
CYNVE0048I: Account modified.
. . . . .
CYNVE0050E: Invalid Role Name: roleName. . .
304
304
304
305
305
305
305
306
306
306
306
306
306
306
307
307
307
307
307
307
307
307
307
308
308
308
308
308
308
308
CYNVE0051E: Role Name: roleName already
exists. . . . . . . . . . . . . . . .
CYNVE0052I: Role: roleNamecreated. . . . .
CYNVE0060E: Choose role to delete. . . . .
CYNVE0061I: Role: roleName deleted. . . . .
CYNVE0062I: Role changed. . . . . . . .
CYNVE0063I: Role: RoleName deleted. . . . .
CYNVE0070E: Invalid Role Name: RoleName.
CYNVE0071E: Role Name: RoleName already
exists. . . . . . . . . . . . . . . .
CYNVE0072E: Choose a role. . . . . . . .
CYNVE0073I: Role: RoleName duplicated. . . .
CYNVE0080I: Account does not exist. . . . .
CYNVE0081I: Account modified.
. . . . .
CYNVE0110E: Group name is NULL. . . . .
CYNVE0111E: Invalid group name: grpName . .
CYNVE0113E: Group name: grpName already
exists. . . . . . . . . . . . . . . .
CYNVE0114I: Server group: grpName
created/modified.
. . . . . . . . . .
CYNVE0120E: Group name is not selected. . .
CYNVE0121E: Group name is NULL or blank.
CYNVE0122E: Invalid group name: grpName
CYNVE0123E: Group name: grpName already
exists. . . . . . . . . . . . . . . .
CYNVE0124I: Server group: grpName
duplicated. . . . . . . . . . . . . .
CYNVE0130E: Invalid Threshold 1: thrs1 . . .
CYNVE0131E: Threshold 2 is not valid: thrs2
CYNVE0132E: Threshold is not valid: thrs
. .
CYNVE0133E: Day is not valid: duration . . .
CYNVE0134E: Start date is not valid: sdate . .
CYNVE0135E: End date is not valid: edate
. .
CYNVE0136E: Date range is not valid: dateRange
CYNVE0137E: Response time is not valid:
resptime . . . . . . . . . . . . . .
CYNVE0138E: Gateway is not valid: gateway . .
CYNVE0139E: Portal page response time is not
valid: portalRespTime . . . . . . . . . .
CYNVE0140E: Authentication response time is
not valid: autheRespTime
. . . . . . . .
CYNVE0141E: Authorization response time is
not valid: authoRespTime
. . . . . . . .
CYNVE0142E: Model building response time is
not valid: ModelRespTime . . . . . . . .
CYNVE0143E: Page loading response time is not
valid: PageRespTime . . . . . . . . . .
CYNVE0144E: Portlets baseline response time is
not valid: PortletRespTime . . . . . . . .
CYNVE0145E: Gateway servlet response time
threshold is not valid: gatwayRespTimeThres . .
CYNVE0146E: Portal Pages Response Time
Threshold is not valid: PortalRespTimeThres . .
CYNVE0147E: Authentication response time
threshold is not valid: AutheRespTimeThres . .
CYNVE0148E: Authorization response time
threshold is not valid: AuthoRespTimeThres . .
CYNVE0149E: Model building response time
threshold is not valid: ModelRespTimeThres . .
CYNVE0150E: Page loading response time
threshold is not valid: PageRespTimeThres . . .
Contents
308
308
309
309
309
309
309
309
309
309
309
309
310
310
310
310
310
310
310
310
310
310
311
311
311
311
311
311
311
311
311
312
312
312
312
312
312
312
313
313
313
313
xxv
CYNVE0151E: Portlets response time threshold
1 is not valid: PortalRespTimeThres1 . . . . .
CYNVE0152E: Gateway servlet response time
threshold indicator 2 is not valid:
GatewayRespTimeThres2 . . . . . . . . .
CYNVE0153E: Portal pages response time
threshold indicator 2 is not valid:
PortalRespTimeThres2 . . . . . . . . . .
CYNVE0154E: Authentication response time
threshold indicator 2 is not valid:
AutheRespTimeThres2 . . . . . . . . . .
CYNVE0155E: Authorization response time
threshold indicator 2 is not valid:
AuthoRespTimeThres2 . . . . . . . . . .
CYNVE0156E: Model building response time
threshold indicator 2 is not valid:
ModelRespTimeThres2 . . . . . . . . . .
CYNVE0157E: Page loading response time
threshold indicator 2 is not valid:
PageRespTimeThres2 . . . . . . . . . .
CYNVE0158E: Portlets response time threshold
indicator 2 is not valid: PortletsRespTimeThres2 .
CYNVE0159I: Validation successful. . . . . .
CYNVE0162I: Pinging server serverName whose
ProbeID is probeId is successful. . . . . . .
CYNVE0163E: Failed to ping server serverName
whose ProbeID is probeId. . . . . . . . .
CYNVE0164I: Group groupName deleted
successfully.
. . . . . . . . . . . .
CYNVE0170E: Configration object is not
selected. . . . . . . . . . . . . . .
CYNVE0171E: Server is not selected for
configuration. . . . . . . . . . . . .
CYNVE0172E: The limit of data collectors to be
monitored has been exceeded. . . . . . . .
CYNVE0172I: Data Collector server: serverName
is configured. . . . . . . . . . . . .
CYNVE0173E: CICS and IMS servers are not
monitored by ITCAM Basic. . . . . . . .
CYNVE0174E: z/OS servers are not supported
by ITCAM Basic. . . . . . . . . . . .
CYNVE0180E: No servers are selected for
unconfiguring. . . . . . . . . . . . .
CYNVE0181E: Data Collector configuration
error. . . . . . . . . . . . . . . .
CYNVE0182E: Server with id, serverId is
unavailable. . . . . . . . . . . . . .
CYNVE0182I: Data Collector server: serverName
is unconfigured. . . . . . . . . . . .
CYNVE0183E: Security property is not valid:
securityProp. . . . . . . . . . . . . .
CYNVE0183I: The security
property:securityProphas been saved for server:
serverName . . . . . . . . . . . . .
CYNVE0184E: Kernel is unavailable. . . . .
CYNVE0190E: Configuration object name is
invalid: configName . . . . . . . . . .
CYNVE0191E: Configuration object: configName
already exists. . . . . . . . . . . . .
CYNVE0192E: Configuration object not selected.
xxvi
313
313
313
314
314
314
314
314
314
314
315
315
315
315
315
315
315
316
316
316
316
316
316
317
317
317
317
317
CYNVE0193I: Configuration object configName is
duplicated as: configName . . . . . . . .
CYNVE0200E: Configuration object name is not
valid: configName . . . . . . . . . . .
CYNVE0201E: Configuration object: configName
already exists. . . . . . . . . . . . .
CYNVE0202I: Configuration object: configName
is modified. . . . . . . . . . . . . .
CYNVE0203E: Configuration object name is not
valid: configName . . . . . . . . . . .
CYNVE0204E: Configuration object: configName
already exists. . . . . . . . . . . . .
CYNVE0205I: Configuration object: configName
is created. . . . . . . . . . . . . .
CYNVE0206I: Configuration object: configName
is applied to Probe server: ProbeName . . . .
CYNVE0207I: Configuration object: configName
is deleted. . . . . . . . . . . . . .
CYNVE0208I: Disabling Probe: ProbeName
. .
CYNVE0209I: Enabling Probe: ProbeName . . .
CYNVE0250E: Polling Frequency is not valid:
pollongFreq . . . . . . . . . . . . .
CYNVE0251E: Level one Sampling Rate is not
valid: L1samplingRate
. . . . . . . . .
CYNVE0252E: Level two Sampling Rate is not
valid: L2samplingRate
. . . . . . . . .
CYNVE0253E: Level three Sampling Rate is not
valid: L3samplingRate
. . . . . . . . .
CYNVE0254E: Max Method Records is not
valid: maxMethRec
. . . . . . . . . .
CYNVE0255E: Max Message Length is not valid:
maxMesgLen
. . . . . . . . . . . .
CYNVE0256E: Threshold 1 is not valid:
threshold1 . . . . . . . . . . . . . .
CYNVE0257E: Threshold 2 is not valid:
threshold2 . . . . . . . . . . . . . .
CYNVE0258E: Threshold is not valid: threshold
CYNVE0259E: Duration is not valid: duration
CYNVE0260E: Start date is not valid: sdate . .
CYNVE0261E: End date is not valid: edate
. .
CYNVE0262E: Date range is not valid: dateRange
CYNVE0263E: Response time is not valid:
respTime . . . . . . . . . . . . . .
CYNVE0264E: Port number is not valid:
portNumber . . . . . . . . . . . . .
CYNVE0265E: SNMP Host/IP is not valid: host
CYNVE0266E: SNMP Comminity is not valid:
community . . . . . . . . . . . . .
CYNVE0267I: System properties validated and
saved.
. . . . . . . . . . . . . .
CYNVE0270E: Message Dispatcher is
unavailable. . . . . . . . . . . . . .
CYNVE0271I: Testing SNMP message sent to
hostName on port portName with community
commuName passed. . . . . . . . . . .
CYNVE0272E: Testing SNMP message sent to
hostName on port portName with community
commuNamefailed.
. . . . . . . . . .
CYNVE0273E: Cannot save SNMP setting. . .
CYNVE0280E: Schedule ScheduleName event
already exists. . . . . . . . . . . . .
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
317
317
318
318
318
318
318
318
318
318
318
319
319
319
319
319
319
319
319
319
320
320
320
320
320
320
320
320
320
320
321
321
321
321
CYNVE0281I: Schedule: ScheduleName created.
CYNVE0282E: Schedule name is not
validScheduleName
. . . . . . . . . .
CYNVE0283E: Schedule name: ScheduleName
already exists. . . . . . . . . . . . .
CYNVE0284I: Schedule is added to:
ScheduleName . . . . . . . . . . . .
CYNVE0285I: Schedule: ScheduleName is deleted
CYNVE0290E: Schedule name: ScheduleName not
selected. . . . . . . . . . . . . . .
CYNVE0291E: Schedule name is not valid:
ScheduleName . . . . . . . . . . . .
CYNVE0292E: Schedule name: ScheduleName
already exists. . . . . . . . . . . . .
CYNVE0293I: Schedule name: ScheduleName
duplicated. . . . . . . . . . . . . .
CYNVE0301E: L1 Sampling Rate is not
validSampleRateL1
. . . . . . . . . .
CYNVE0302E: L2 sampling rate is not
validSampleRateL2
. . . . . . . . . .
CYNVE0303E: L3 sampling rate is not
validSampleRateL3
. . . . . . . . . .
CYNVE0304I: Group schedule has changed. . .
CYNVE0311E: L1 sampling rate is not
validSampleRateL1
. . . . . . . . . .
CYNVE0312E: L2 sampling rate is not
validSampleRateL2
. . . . . . . . . .
CYNVE0313E: L3 sampling rate is not
validSampleRateL3
. . . . . . . . . .
CYNVE0314I: Data Collector
Server:serverNameschedule has changed. . . .
CYNVE0321E: L1 sampling rate is not
validSampleRateL1
. . . . . . . . . .
CYNVE0322E: L2 sampling rate is not
validSampleRateL2
. . . . . . . . . .
CYNVE0323E: L3 sampling rate is not
validSampleRateL3
. . . . . . . . . .
CYNVE0324I: The All servers schedule has
changed. . . . . . . . . . . . . . .
CYNVE0367E: The Specific Data Collector not
found. . . . . . . . . . . . . . .
CYNVE0413I: Component panel displayed . .
CYNVE0340E: Unable to display charts for
Recent Activity display. . . . . . . . . .
CYNVE0341E: The selected server is
unavailable. . . . . . . . . . . . . .
CYNVE0343E: Select a server. . . . . . . .
CYNVE0344E: Select a metric from the list. . .
CYNVE0350E: Select a metric from the list to
view Recent Activity.
. . . . . . . . .
CYNVE0355E: Select a group. . . . . . . .
CYNVE0356E: The Recent Activity display
feature is not supported. . . . . . . . .
CYNVE0357E: Select a server. . . . . . . .
CYNVE0358E: The selected server is
unavailable. . . . . . . . . . . . . .
CYNVE0359E: Unable to save group/server
information in the session. . . . . . . . .
CYNVE0410E: The data is unavailable.
. . .
CYNVE0411E: Server unavailable. . . . . .
CYNVE0412E: The date is not valid.. . . . .
321
321
321
322
322
322
322
322
322
322
322
322
322
323
323
323
323
323
323
323
323
323
324
324
324
324
324
324
325
325
325
325
325
326
326
326
CYNVE0420E: No Kernel available. . . . . .
CYNVE0421E: Unable to contact Kernel. . . .
CYNVE0422E: Unable to contact Polling
Agent.pacomponentid . . . . . . . . . .
CYNVE0423E: Unable to contact Message
Dispatcher.mdcomponentid . . . . . . . .
CYNVE0424E: Unable to contact Global Publish
Server.componentid
. . . . . . . . . .
CYNVE0425E: Unable to contact Data
Collector.componentid . . . . . . . . . .
CYNVE0426E: Unable to contact Publish
Server.componentid
. . . . . . . . . .
CYNVE0427E: Unable to contact Archive
Agent.componentid
. . . . . . . . . .
CYNVE0428I: Data Collector(Probe) is not
available.
. . . . . . . . . . . . .
CYNVE0431I: Kernel link clicked. . . . . .
CYNVE0432I: Data Collector link clicked. . . .
CYNVE0433I: Data Collector link clicked. . . .
CYNVE0434I: Publish Server link clicked. . . .
CYNVE0435I: Archive Agent link clicked. . . .
CYNVE0436I: Email link clicked.
. . . . .
CYNVE0437I: GPS link clicked. . . . . . .
CYNVE0438I: Polling agent link clicked. . . .
CYNVE0439E: Unable to display self-diagnosis
page. . . . . . . . . . . . . . . .
CYNVE0471E: No Data Available. . . . . .
CYNVE0490E: Access is denied to delete this
top report. . . . . . . . . . . . . .
CYNVE0491E: Access is denied to modify this
report. . . . . . . . . . . . . . .
CYNVE0492E: Access is denied to view this top
report. . . . . . . . . . . . . . .
CYNVE0493E: Duplicate report name entered.
CYNVE0494E: The report name field is blank.
CYNVE0495E: E-mail report link cannot
function. . . . . . . . . . . . . . .
CYNVE0496E: Access is denied to create this
Portal Report. . . . . . . . . . . . .
CYNVE0497E: Access denied to create this
Portal Report. . . . . . . . . . . . .
CYNVE0500E: Report type is not supported.
CYNVE0500I: Server aggregation selected. . .
CYNVE0500W: Modifying the top report. . . .
CYNVE0501E: Modify report denied. . . . .
CYNVE0501I: Creating a schedule report. . . .
CYNVE0501W: Modifying the report. . . . .
CYNVE0502E: Recurrence is not supported. . .
CYNVE0502I: Creating a report. . . . . . .
CYNVE0502W: Modifying the report. . . . .
CYNVE0503E: Error modifying the report. . .
CYNVE0503I: Creating a top report.
. . . .
CYNVE0503W: Modifying the report. . . . .
CYNVE0504E: Recurrence is not supported. . .
CYNVE0504I: Modifying a schedule Report. . .
CYNVE0505I: Modifying a report. . . . . .
CYNVE0510E: The date range StartDate is not
valid. . . . . . . . . . . . . . . .
CYNVE0511E: The date range End Date is not
valid. . . . . . . . . . . . . . . .
Contents
326
326
327
327
327
327
328
328
328
328
328
328
329
329
329
329
329
329
329
329
330
330
330
330
330
330
331
331
331
331
331
331
331
332
332
332
332
332
332
332
332
332
333
333
xxvii
CYNVE0512E: The date range End Date must be
after the Start Date. . . . . . . . . . .
CYNVE0513E: The graphical environment is not
set up correctly on your server. . . . . . .
CYNVE0514E: The contrast report is no longer
compatible. . . . . . . . . . . . . .
CYNVE0515E: No stored report is selected. . .
CYNVE0520E: The time entered is not valid.
CYNVE0521E: An e-mail address was entered
that is not valid. . . . . . . . . . . .
CYNVE0522E: The dates entered are not valid.
CYNVE0523E: The weeks entered are not valid.
CYNVE0524E: The months entered are not
valid. . . . . . . . . . . . . . . .
CYNVE0530E: The report name is not valid. . .
CYNVE0531E: Duplicate report name entered.
CYNVE0532E: Error saving the report. . . . .
CYNVE0550E: E-mail address is not valid. . .
CYNVE0560E: Action denied. Cannot send an
e-mail. . . . . . . . . . . . . . .
CYNVE0561E: Error in sending an e-mail.
. .
CYNVE0570E: The elapsed time threshold is not
valid. . . . . . . . . . . . . . . .
CYNVE0571E: The elapsed time threshold is not
valid. . . . . . . . . . . . . . . .
CYNVE0581E: The graphical environment is not
set up correctly on your server. . . . . . .
CYNVE0582E: No report name was entered. . .
CYNVE0583E: Error while saving the report.
CYNVE0584E: Duplicate report name entered.
CYNVE0585E: Access is denied to view this
report. . . . . . . . . . . . . . .
CYNVE0586E: The requested report is not
available.
. . . . . . . . . . . . .
CYNVE0587E: Access denied to save this report.
CYNVE0590E: The requested top report is not
available.
. . . . . . . . . . . . .
CYNVE0591E: Access is denied to view this top
report. . . . . . . . . . . . . . .
CYNVE0760E: A server error has occurred. . .
CYNVE0761E: The Publish Server is
unavailable. . . . . . . . . . . . . .
CYNVE0762E: The Kernel is unavailable. . . .
CYNVE0763E: The server could not be found.
CYNVE0764E: The task cannot be completed.
CYNVE0765I: The transaction finished
executing. . . . . . . . . . . . . .
CYNVE0766I: The request finished executing.
CYNVE0770E: The Publish Server is
unavailable. . . . . . . . . . . . . .
CYNVE0771E: The selected server is
unavailable. . . . . . . . . . . . . .
CYNVE0772E: There are no servers in the
selected group.
. . . . . . . . . . .
CYNVE0773E: The kernel is unavailable. . . .
CYNVE0780E: A server error occurred.
. . .
CYNVE0781E: The Publish Server is
unavailable. . . . . . . . . . . . . .
CYNVE0782E: The Kernel is unavailable. . . .
CYNVE0783E: The server could not be found.
xxviii
333
333
333
334
334
334
334
334
334
335
335
335
335
335
335
336
336
336
336
336
337
337
337
337
337
337
338
338
338
338
338
339
339
339
339
339
340
340
340
340
340
CYNVE0784I: The transaction finished
executing. . . . . . . . . . . . . .
CYNVE0785I: The request finished executing.
CYNVE0790E: A server error occurred.
. . .
CYNVE0791E: The Publish Server is
unavailable. . . . . . . . . . . . . .
CYNVE0792E: The kernel is unavailable. . . .
CYNVE0793E: The active server is unavailable.
CYNVE0800E: A server error occurred.
. . .
CYNVE0801E: The Publish Server is
unavailable. . . . . . . . . . . . . .
CYNVE0802E: The kernel is unavailable. . . .
CYNVE0803E: The active server is unavailable.
CYNVE0810E: Select a group. . . . . . . .
CYNVE0811E: Select a server. . . . . . . .
CYNVE0820E: A server error occurred.
. . .
CYNVE0821E: The Publish Server is
unavailable. . . . . . . . . . . . . .
CYNVE0822E: The Kernel is unavailable. . . .
CYNVE0823E: The server could not be found.
CYNVE0824I: The transaction finished
executing. . . . . . . . . . . . . .
CYNVE0825I: The request finished executing.
CYNVE0830E: A server error occurred.
. . .
CYNVE0831E: The Publish Server is
unavailable. . . . . . . . . . . . . .
CYNVE0832E: The kernel is unavailable. . . .
CYNVE0833E: The server could not be found.
CYNVE0834I: The transaction finished
executing. . . . . . . . . . . . . .
CYNVE0835I: The request finished executing.
CYNVE0840E: The server is currently
unavailable. . . . . . . . . . . . . .
CYNVE0841E: The system is currently
unavailable. . . . . . . . . . . . . .
CYNVE0842E: No data available for the work
area. . . . . . . . . . . . . . . .
CYNVE0850E: No classes are instrumented for
lock analysis. . . . . . . . . . . . .
CYNVE0851E: Lock analysis data is not being
collected. . . . . . . . . . . . . . .
CYNVE0852E: The selected Data Collector does
not support the Lock Analysis feature. . . . .
CYNVE0853E: An error occurred with the server
selection.
. . . . . . . . . . . . .
CYNVE0854E: The selected server is
unavailable. . . . . . . . . . . . . .
CYNVE0860E: You entered an e-mail address :
email that is invalid. . . . . . . . . . .
CYNVE0870E: An error occurred while trying to
send the e-mail. . . . . . . . . . . .
CYNVE0871E: To e-mail a link, save the report
first. . . . . . . . . . . . . . . .
CYNVE0880E: Select a search type. . . . . .
CYNVE0881E: Enter a search value.
. . . .
CYNVE0882E: You entered a search value :
searchVal that is not valid. . . . . . . . .
CYNVE0883E: You entered a search value : sVal
whose length is : sValLen which exceeds the
field limit of 60. . . . . . . . . . . .
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
341
341
341
341
341
342
342
342
342
342
343
343
343
343
343
344
344
344
344
344
345
345
345
345
345
345
346
346
346
346
346
347
347
347
347
347
348
348
348
CYNVE0884E: You entered a search value : sVal
whose length is : sValLen which exceeds the
field limit of 255. . . . . . . . . . . .
CYNVE0885E: You entered a search value : sVal
whose length is : sValLen which exceeds the
field limit of 10000. . . . . . . . . . .
CYNVE0920E: The request you selected is
complete. . . . . . . . . . . . . .
CYNVE0921E: Unable to locate the home
request in Publish Server. . . . . . . . .
CYNVE0930E: The GPS is currently unavailable.
CYNVE0950E: Port number is not valid:
hostname . . . . . . . . . . . . . .
CYNVE0951E: Cannot add Web server.
. . .
CYNVE0952E: Cannot display Web server. . .
CYNVE0953E: HostName/IP Address is not
valid: hostname . . . . . . . . . . . .
CYNVE0954I: Web server with hostname:
hostname and Port Number: hostname is added. .
CYNVE0955E: HostName/IP Address: hostname
cannot be added. . . . . . . . . . . .
CYNVE0956E: Port is not valid: port, Port
number should be in the range of 1 - 65535. . .
CYNVE0960E: Problem deleting Web server
whose IP and port is: webserver . . . . . .
CYNVE0961E: Cannot delete Web server whose
IP and port is: webserver
. . . . . . . .
CYNVE0962I: Delete Web server whose IP and
port is: webserver . . . . . . . . . . .
CYNVE1000E: The charts on the Web Overview
page cannot display. . . . . . . . . . .
CYNVE1001E: The Polling agent is not running.
CYNVE1020E: Cannot display Web server. . .
CYNVE1060E: Failed to create Portal Manager
EJB. . . . . . . . . . . . . . . .
CYNVE1061I: No portal summary data is
available for the server whose server ID is:
serverID . . . . . . . . . . . . . .
CYNVE1070E: The selected server whose server
id is: serverIdis not available. . . . . . . .
CYNVE1071E: Select a portal server. . . . .
CYNVE1072E: Unable to display the Portal
Overview page. . . . . . . . . . . .
CYNVE1073E: The charts on the Portal
Overview page cannot display. . . . . . .
CYNVE1082E: To configure thresholds, the
server must be assigned to a group.
. . . .
CYNVE1090E: Select a group. . . . . . . .
CYNVE1091E: Select a server. . . . . . . .
CYNVE1100E: Select an x-axis metric. . . . .
CYNVE1101E: Select a y-axis metric. . . . .
CYNVE1102E: Select a different y-axis metric.
CYNVE1103E: Select a valid y-axis max metric.
CYNVE1104E: Select a valid y-axis metric. . .
CYNVE1111E: Error running the report. . . .
CYNVE1112E: Data is unavailable. . . . . .
CYNVE1160E: The server with the server
id:serverId is unavailable. . . . . . . . .
CYNVE1160I: URL from ITCAMfTT is not valid,
the 'cicsOrims' parameter is null.
. . . . .
348
348
349
349
349
349
349
349
349
350
350
350
350
350
350
350
351
351
351
351
351
351
352
352
352
352
352
353
353
353
353
353
353
354
354
354
CYNVE1160W: No installed applications are
displayed for this server, serverName. . . . .
CYNVE1161E: URL from ITCAMfTT is not
valid. . . . . . . . . . . . . . . .
CYNVE1161I: URL from ITCAMfTT is not
valid,, the 'inst' parameter is null. . . . . .
CYNVE1161W: The link to the Admin console is
not available. . . . . . . . . . . . .
CYNVE1162E: Server Overview page is unable
to retrieve information for this group. . . . .
CYNVE1162I: URL from ITCAMfTT is not valid,
the 'ipAddress' parameter is null. . . . . .
CYNVE1162W: The System Resources
information for this server serverNameis
unavailable. . . . . . . . . . . . . .
CYNVE1163E: The server serverName is
unavailable. . . . . . . . . . . . . .
CYNVE1163I: URL from ITCAMfTT is not valid,
the 'admin' parameter is null. . . . . . . .
CYNVE1163W: The System Resources
information for this z/OS server is unavailable.
CYNVE1164E: The Server was not found in the
database.
. . . . . . . . . . . . .
CYNVE1164W: The Publish Server is
unavailable. . . . . . . . . . . . . .
CYNVE1165W: The Publish Server returned no
PMI data. . . . . . . . . . . . . .
CYNVE1170E: Unable to display data on the
Group Overview page. . . . . . . . . .
CYNVE1171E: Unable to retrieve response time
data for the Group Overview page, as a result
of the following exception: exception
. . . .
CYNVE1172E: Unable to retrieve throughput
data for the Group Overview page, as a result
of the following exception: exception
. . . .
CYNVE1173E: Unable to retrieve response time
data for the Server Overview page, as a result
of the following exception: exception
. . . .
CYNVE1174E: Unable to retrieve throughput
data for Server Overview page, as a result of
the following exception: exception . . . . .
CYNVE1175E: Unable to retrieve data for the
Web Server overview page, as a result of the
following exception: exception . . . . . . .
CYNVE1176E: Unable to retrieve data for the
Portal Overview page, as a result of the
following exception: exception . . . . . . .
CYNVE1177E: Unable to retrieve data for the
Portal Summary pages, as a result of the
following exception: exception . . . . . . .
CYNVE1178E: Unable to process data for the
Portal Overview page. . . . . . . . . .
CYNVE1179E: Unable to process data for the
Portal Summary pages. . . . . . . . . .
CYNVE1200E: Cannot find any servers by
specific groupId: groupid . . . . . . . .
CYNVE1201E: Unable to retrieve data from
Database, tables tablename, due to the following
SQL Exception: exception . . . . . . . .
CYNVE1202E: Error while retrieving pid from
Kernel, probeId = tablename . . . . . . .
Contents
354
354
355
355
355
355
355
355
356
356
356
356
356
357
357
357
357
358
358
358
358
359
359
359
359
359
xxix
CYNVE1206W: No Data Collector is selected to
apply configuration: configName . . . . . .
CYNVE1300E: Problem finding server as a
result of the following exception: exception . .
CYNVE1301E: Problem finding alerts as a result
of the following exception: exception
. . . .
CYNVE1302E: Problem finding alerts as a result
of the following exception: exception
. . . .
CYNVE1303E: Problem finding events as a
result of the following exception: exception . .
CYNVE1304E: DC is not available . . . . .
CYNVE1330E: Problem finding problem as a
result of the following exception: exception . .
CYNVE1331E: Saving problem by: problem as a
result of the following exception: exception . .
CYNVE1332E: Problem deleting problem by:
problem as a result of the following exception:
exception . . . . . . . . . . . . . .
CYNVE1333E: Problem deleting problem by:
problem as a result of the following exception:
exception . . . . . . . . . . . . . .
CYNVE1334E: Problem finding problem by:
problem as a result of the following exception:
exception . . . . . . . . . . . . . .
CYNVE1335E: The group is not valid: groupId
CYNVE1336E: The server is not valid: probeId
CYNVE1337E: Input the problem name . . .
CYNVE1338E: Input the problem description
CYNVE1339E: The time is not valid: time . . .
CYNVE1370E: Fail to call problem finder . . .
CYNVE1429I: Component link: kernelinstant on
left panel is shown correctly. . . . . . . .
CYNVE1430I: Component link: compinstant on
left panel is shown correctly. . . . . . . .
CYNVE1431E: Left-side component panel is not
shown correctly. . . . . . . . . . . .
CYNVE1560E: Failed to get JMX Data from Data
Access Layer . . . . . . . . . . . .
CYNVE1561E: Failed to get JMX categories from
Data Access Layer. . . . . . . . . . .
CYNVE1562E: Error in getting JMX data. . . .
CYNVE1563E: Missing 'usejsp' attribute in VE
display configuration file . . . . . . . .
CYNVE1565E: Unable to get server group
information from database.
. . . . . . .
CYNVE1566E: Unable to get data collector
information from database.
. . . . . . .
CYNVE1568E: Failed to get JMX data from data
collector. . . . . . . . . . . . . . .
CYNVE1569E: Failed to get JMX Categories
from data collector. . . . . . . . . . .
CYNVE1570E: Failed to get JMX data. . . . .
CYNVE1571E: Failed to get JMX data in calling
method JMXAcquireAttribute.getAttribute. . .
CYNVE1605E: Error retrieving all Traps
definition. SQL Exception: exception . . . . .
CYNVE1606E: Error retrieving all Traps
definition by UserID. SQL Exception: exception .
CYNVE1607E: Error retrieving a Trap definition
by TRAPID. SQL Exception: exception . . . .
xxx
360
360
360
360
360
360
361
361
361
361
361
361
362
362
362
362
362
362
362
362
362
363
363
363
363
364
364
364
364
365
365
365
365
CYNVE1608E: Error inserting/updating a Trap
Definition. SQL Exception: exception . . . . .
CYNVE1609E: Error deleting a Trap definition.
SQL Exception: exception . . . . . . . .
CYNVE1610E: Error retrieving the unfiltered
Trap history list. SQL Exception: exception . . .
CYNVE1611E: Error reading a properties file.
CYNVE1612E: Error retrieving the filtered Trap
history list. SQL Exception: exception . . . .
CYNVE1613E: Error retrieving number of
filtered Trap History. SQL Exception: exception .
CYNVE1614E: Error retrieving filtered Trap list.
SQL Exception: exception . . . . . . . .
CYNVE1615E: Error retrieving filtered Trap list.
SQL Exception: exception . . . . . . . .
CYNVE1616E: Error retrieving filtered Trap list.
SQL Exception: exception . . . . . . . .
CYNVE1617E: Error retrieving a Trap. SQL
Exception: exception . . . . . . . . . .
CYNVE1618E: Error deleting a Trap History.
SQL Exception: exception . . . . . . . .
CYNVE1619E: Error retrieving a Trap
StackTrace. SQL Exception: exception . . . .
CYNVE1620E: Error retrieving thread dump.
SQL Exception: exception . . . . . . . .
CYNVE1621E: Error retrieving Trap Action for
DB2. SQL Exception: exception
. . . . . .
CYNVE1622E: Error retrieving Trap Action for
Oracle. SQL Exception: exception . . . . . .
CYNVE1623E: Error retrieving Unfiltered Trap
Action for DB2. SQL Exception: exception . . .
CYNVE1624E: Error retrieving Unfiltered Trap
Action for ORACLE. SQL Exception: exception .
CYNVE1625E: Error retrieving filtered Trap
Action for DB2. SQL Exception: exception . . .
CYNVE1626E: Error retrieving filtered Trap
Action for ORACLE. SQL Exception: exception .
CYNVE1627E: Error retrieving filtered Trap
Action for DB2. SQL Exception: exception . . .
CYNVE1628E: Error retrieving filtered Trap
Action for ORACLE. SQL Exception: exception .
CYNVE1629E: Error retrieving Trap Names.
SQL Exception: exception . . . . . . . .
CYNVE1630E: Error retrieving filtered Trap
History for DB2. SQL Exception: exception
. .
CYNVE1631E: Error retrieving filtered Trap
History for ORACLE. SQL Exception: exception .
CYNVE1632E: Error retrieving filtered Trap
History for DB2. SQL Exception: exception
. .
CYNVE1633E: Error retrieving filtered Trap
History for ORACLE. SQL Exception: exception .
CYNVE1634E: Error retrieving all Traps
definition by UserId for a server. SQL
Exception: exception . . . . . . . . . .
CYNVE1800E: ProblemLogAction Exception . .
CYNVE1801E: JNDI_NAME is not valid: problem
CYNVE1802E: DAL Resource Adapter
Connection Error . . . . . . . . . . .
CYNVE1830E: File does not exist when
attempting to get the application configuration .
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
365
366
366
366
366
367
367
367
367
368
368
368
368
369
369
369
369
370
370
370
370
371
371
371
371
372
372
372
372
372
373
CYNVE1831W: No application configuration
was found in server configuration . . . . .
CYNVE1832W: Getting commandagent error
CYNVE1833E: The Configuration File does not
support selected DC . . . . . . . . . .
CYNVE1834E: The Configuration Application
does not support selected DC . . . . . . .
CYNVE1940E: Invalid method profile duration:
duration . . . . . . . . . . . . . .
CYNVE1950E: An error occurred while
attempting to launch into TEP. . . . . . .
CYNVE1951E: Unable to launch into TEP
because TEMA does not support ITCAM J2SE
DCs. . . . . . . . . . . . . . . .
CYNVE2000E: Unable to save the Server
Statistics configuration. . . . . . . . . .
CYNVE2000I: Server statistics overview
configuration saved successfully. . . . . . .
CYNVE2001E: The default configuration is
unavailable. . . . . . . . . . . . . .
CYNVE2002E: The Server Statistics Overview
page is unavailable. . . . . . . . . . .
CYNVE3000E: The server displayNameis
currently unavailable. . . . . . . . . .
CYNVE3000I: SMF history is not available for
the Data Collector whose component ID is:
componentID. . . . . . . . . . . . .
CYNVE3001E: The Publish Server is
unavailable. . . . . . . . . . . . . .
CYNVE3001I: Byte activity data is not available
for the Data Collector whose component ID is:
componentID. . . . . . . . . . . . .
CYNVE3002E: Region database pool data for
server serverDisplayNameis unavailable.
. . .
CYNVE3002I: Transaction activity data is not
available for the Data Collector whose
component ID is: componentID. . . . . . .
CYNVE3003E: List of resource names not found.
CYNVE3003I: EJB activity data is not available
for the Data Collector whose component ID is:
componentID. . . . . . . . . . . . .
CYNVE3004E: The server displayNameis
unavailable. . . . . . . . . . . . . .
CYNVE3004I: Servlet activity data is not
available for the Data Collector whose
component ID is: componentID. . . . . . .
CYNVE3005E: The system is currently
unavailable. . . . . . . . . . . . . .
CYNVE3005I: Miscellaneous data is not
available. . . . . . . . . . . . . . .
CYNVE3006E: Data for the server displayName is
unavailable. . . . . . . . . . . . . .
CYNVE3006I: EJB coverage information is not
available.
. . . . . . . . . . . . .
CYNVE3007E: Select a server. . . . . . . .
CYNVE3007I: Servlet coverage information is
not available. . . . . . . . . . . . .
CYNVE3008E: This feature is not supported for
the selected server with this application server
platform: serverPlatform. . . . . . . . . .
373
373
373
373
374
374
374
374
374
374
375
375
375
375
375
375
376
376
376
376
376
376
377
377
377
377
377
377
CYNVE3008I: Unable to populate SQL for the
SMF Data Collector whose probe ID is: probeID.
CYNVE3009E: Failed to find server. . . . . .
CYNVE3009I: System Resources data is not
available.
. . . . . . . . . . . . .
CYNVE3010E: EJB used to get server or server
group failed. . . . . . . . . . . . .
CYNVE3010I: SMF history is not available for
the Data Collector whose probe ID is: probeID. .
CYNVE3011E: Select a group. . . . . . . .
CYNVE3011I: The number of total sessions is
not available for the Data Collector whose probe
ID is: probeID. . . . . . . . . . . . .
CYNVE3012E: Select a resource. . . . . . .
CYNVE3012I: Unable to contact server manager
bean. . . . . . . . . . . . . . . .
CYNVE3013E: Unable to display charts on
System Resource pages. . . . . . . . . .
CYNVE3013I: System Resource data is
unavailable for the Data Collector whose
component ID is: componentID. . . . . . .
CYNVE3014E: Unable to get CTG data, as a
result of the following exception: exception. . .
CYNVE3014I: System Resource data is
unavailable for this Data Collector. . . . . .
CYNVE3015E: Unable to access MQI data, as a
result of the following exception: exception. . .
CYNVE3015I: CPU Utilization data is
unavailable for the Data Collector whose
component ID is: componentID. . . . . . .
CYNVE3016I: Memory data is unavailable for
the Data Collector whose component ID is:
componentID. . . . . . . . . . . . .
CYNVE3017I: Transaction data is unavailable for
the Data Collector whose component ID
is:componentID. . . . . . . . . . . . .
CYNVE3018I: Database connection pool data is
unavailable for the Data Collector whose
component ID is:componentID.
. . . . . .
CYNVE3019I: EJB coverage data is unavailable
for the Data Collector whose component ID is:
componentID. . . . . . . . . . . . .
CYNVE3020I: Servlet coverage data is
unavailable for the Data Collector whose
component ID is: componentID. . . . . . .
CYNVE3021I: EJB activity data is unavailable
for the Data Collector whose component ID is:
componentID. . . . . . . . . . . . .
CYNVE3022I: Servlet activity data is unavailable
for the Data Collector whose component ID is:
componentID. . . . . . . . . . . . .
CYNVE3023I: Thread pool data is unavailable
for the Data Collector whose component ID is:
componentID. . . . . . . . . . . . .
CYNVE3024I: System resource data is
unavailable for the Data Collector whose probe
ID is: probeID. . . . . . . . . . . . .
CYNVE3025I: Unable to compare double values,
s1 and s2, for sorting on System Resource pages.
CYNVE3026I: Unable to compare long values, s1
and s2, for sorting on system resource pages. .
Contents
377
378
378
378
378
378
378
378
379
379
379
379
379
379
380
380
380
380
380
381
381
381
381
381
381
381
xxxi
CYNVE3027I: Unable to compare Date values,
s1 and s2, for sorting on system resource pages.
CYNVE3028I: Can not be parsed by decimal
format. . . . . . . . . . . . . . .
CYNVE3029I: Cannot be parsed as integers. . .
CYNVE3030I: Cannot be parsed by longs.
. .
CYNVE3031I: Cannot be parsed as dates. . . .
CYNVE3032I: Database connection pool data is
unavailable for the Data Collector whose
component ID is: componentID. . . . . . .
CYNVE4000E: Default page, homePage, could
not be saved. . . . . . . . . . . . .
CYNVE4000I: Default page has been
successfully saved. . . . . . . . . . .
CYNVE4001E: Unable to display the Enterprise
Overview page. . . . . . . . . . . .
CYNVE4002E: Unable to display history on the
Enterprise Overview page. . . . . . . . .
CYNVE4003E: Unable to display charts on the
Enterprise Overview page. . . . . . . . .
CYNVE4004E: Unable to display the Enterprise
Overview page. . . . . . . . . . . .
CYNVE4005E: Unable to display charts on the
Group Overview page. . . . . . . . . .
CYNVE4007E: Unable to display the Group
Overview page. . . . . . . . . . . .
CYNVE5000E: Failed to capture data for Server
Statistics Overview page. . . . . . . . .
CYNVE5001E: Unable to access the list of
available Data Collectors on the Server Statistics
Overview page. . . . . . . . . . . .
CYNVE5002E: Unable to access the list of
servers to display the Server Statistics Overview
page, as a result of the following exception:
exception. . . . . . . . . . . . . . .
CYNVE5003E: Unable to get the server group
manager EJB. . . . . . . . . . . . .
CYNVE5004E: Unable to access throughput and
response time information for the group,
groupName. The following exception is shown:
exception . . . . . . . . . . . . . .
CYNVE5005E: Unable to access baseline
throughput and response time information for
the group, groupName. The following exception
is shown: exception . . . . . . . . . .
CYNVE5006E: Unable to access history for any
server group, as a result of the following
exception: exception . . . . . . . . . .
CYNVE5007E: Unable to access the list of
disabled Data Collectors for display on the
Server Statistics Overview page, as a result of
the following exception: exception. . . . . .
CYNVE5008E: Unable to get server manager
EJB. . . . . . . . . . . . . . . .
CYNVE5009E: Unable to retrieve data for the
display of recent activity, as a result of the
following exception: exception . . . . . . .
CYNWS Messages: Web Services . . . . . . .
CYNWS0001E: An authentication failure has
occurred for the current user. . . . . . . .
xxxii
382
382
382
382
382
382
382
382
383
383
383
383
383
384
384
384
384
384
385
385
385
385
386
386
386
386
CYNWS0002W: No trap is defined for the
current user. . . . . . . . . . . . . .
CYNWS0003W: There is no aggregate data for
traps. . . . . . . . . . . . . . . .
CYNW Messages: Polling Agent . . . . . . .
CYNW0001E: An exception occurred while
communicating with the Archive Agent. . . .
CYNW0002E: A error occurred while binding to
the RMI. . . . . . . . . . . . . . .
CYNW0003E: An error occurred while joining
the Kernel. . . . . . . . . . . . . .
CYNW0004I: The Polling Agent started polling
and storing the information in the database for
server server at port port. The server's ID is
serverId. . . . . . . . . . . . . . .
CYNW0005E: An error occurred while the
Polling Agent was unbinding from the RMI. . .
CYNW0006E: An exception occurred while the
Polling Agent was retrieving LookupAgent from
the Kernel. . . . . . . . . . . . . .
CYNW0007I: The Web server with IP address ip
at port portwas added to a monitor. The server's
ID is serverId. . . . . . . . . . . . .
CYNW0008I: The Polling Agent is removing
Web server with IP address ip at port port from
monitoring. The server's ID is serverId. . . . .
CYNX Messages: Installation . . . . . . . .
CYNX0001E: There were usage errors, where a
number of arguments were incorrect for: java
UserInputsFilePath,
ConfigurationTemplatesPath, and
DestinationPath. . . . . . . . . . . .
CYNX0002E: Configuration template template
was not found. The concrete configuration XML
file could not be created. . . . . . . . .
CYNX0003E: A configuration template cannot be
found for the following application server
versions: version. The concrete configuration
XML file could not be created.. . . . . . .
CYNX0004E: The concrete configuration XML
file could not be generated due to missing
values in the dcInputs.txt file. . . . . . . .
CYNX0005I: The concrete configuration file file
was generated successfully. . . . . . . . .
CYNX0006E: The value for the variable variable
was not found in the userInputs file. This
variable was not replaced in file fileName. . . .
CYNX0007E: File fileName1 cannot be modified
successfully and copied to the file fileName2. . .
CYNX0008E: The system could not load the
property file fileName successfully. . . . . .
CYNX0009E: One or more -Xrun JVM
arguments were found for the server server.
Configuration is skipped for server server. . . .
CYNX0010E: The system failed to get the
backup of the current application server
configuration. . . . . . . . . . . . .
CYNX0011E: The system failed to set variable.
CYNX0012E: The system failed to save and
commit the newly applied configuration. . . .
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
386
386
387
387
387
387
387
387
388
388
388
388
388
389
389
389
389
389
390
390
390
390
391
391
CYNX0013E: The system failed to create the
post-installation instruction file for the
WebLogic unmanaged application server. . . .
CYNDA Messages: Data Access . . . . . . .
CYNDA001E: An Exception occurred while
initializing the Data Access Layer. . . . . .
CYNDA002E: Command Configuration number
has the wrong number of Commands Elements.
It should contain only one Commands Element.
CYNDA003E: Exception while creating the
Command cmdName . . . . . . . . . .
CYNDA004E: Exception while processing the
Command Configuration file cmdName
. . .
CYNDA005E: Command name is not specified
for the command cmdName
. . . . . . .
CYNDA006E: Class for the Command is not
specified for the command cmdName . . . .
CYNDA007E: No queries found corresponding
to the input category category . . . . . . .
CYNDA008E: No query name or category name
is passed in the input. At least one category or
query should be present in input. . . . . .
CYNDA009E: No command is associated with
the query queryType . . . . . . . . . .
CYNDA200W: The Command Configuration
File fileName does not have any Commands to
configure. . . . . . . . . . . . . .
CYNDA400I: DAL is processing the commands
configured from the file fileName in the directory
fileDir . . . . . . . . . . . . . . .
CYNDA401I: Initialized the command with
name cmdName and class name className . . .
CYNDA402I: Registering a query queryType of
category category with the command cmdName .
CYNDA403I: The command cmdName is
registered. . . . . . . . . . . . . .
KYN Messages: Tivoli Enterprise Monitoring Agent
KYNA0001I: ITCAM for Application Diagnostics
monitoring agent start-up complete. . . . . .
KYNA0002E: ITCAM for Application
Diagnostics monitoring agent initialization
failed: errorMessage. . . . . . . . . . .
KYNA0003I: The Agent configuration file file
loaded successfully. . . . . . . . . . .
KYNA0004E: Agent configuration file file was
not found. . . . . . . . . . . . . .
KYNA0005E: Agent configuration file file
loading error: errorMessage. . . . . . . . .
KYNA0006I: The Agent context file file loaded
successfully. . . . . . . . . . . . . .
KYNA0007W: The Agent context file file was not
found. . . . . . . . . . . . . . . .
KYNA0008W: Agent context file file loading
error: errorMessage. . . . . . . . . . .
KYNA0009I: Listening for incoming data
collector connections on port port. . . . . .
KYNA0010I: Application server discovered:
serverInfo. . . . . . . . . . . . . . .
KYNA0011I: Application server connected:
serverId. . . . . . . . . . . . . . .
391
391
391
392
392
392
392
393
393
393
393
394
394
394
394
394
394
395
395
395
395
395
396
396
396
396
396
396
KYNA0012I: Application server disconnected:
serverId. . . . . . . . . . . . . . .
KYNA0013E: The Application server connection
connectionInfo failed: errorMessage . . . . . .
KYNA0014I: Resource data monitoring started
for application server serverId resourceMethod. . .
KYNA0015I: Resource data monitoring stopped
for the application server serverId. . . . . .
KYNA0016I: Request data monitoring started
for the application server serverId requestMethod. .
KYNA0017I: Request data monitoring stopped
for the application server serverId. . . . . .
KYNA0018I: Verbose GC output monitoring
started for the application server serverId with
interval gcInterval. . . . . . . . . . . .
KYNA0019I: Verbose GC output monitoring
stopped for the application server serverId. . .
KYNA0020I: Application server log scrapping
started for the application server serverId alsInfo..
KYNA0021I: Application server log scrapping
stopped for the application server serverId. . .
KYNA0022E: Application server log scrapping
stopped for the application server serverId with
error: errorMsg. . . . . . . . . . . . .
KYNA0023I: Take action tactId completed
successfully for application server serverId. . .
KYNA0024E: Take action tactId failed for the
application server serverId: tactReason. . . . .
KYNA0025I: Take action tactId processing
started for the application server serverId. . . .
KYNA0026E: Take sample table failed for
application server serverId: errorMsg. . . . . .
KYND Messages: ITCAM for Application
Diagnostics Secondary Data Collector . . . . .
KYND0001E: AgentConnection class initializer
not able to load native library: Library Name . .
KYND0002W: WorkLoad requests could not be
measured by Request Analysis . . . . . .
KYND0003E: Unable to write to MVS console Console Name . . . . . . . . . . . .
KYND0004E: Unable to check native library
build level because native library not available .
KYND0005E: Incompatibility detected between
Java library Java Library and Native Library
Native Library. Java library build level is Java
Library Level Native library build level is Native
Library Level . . . . . . . . . . . . .
KYND0006E: Incompatibility detected between
Native library Native Library and Java Library
Java Library. Native library build level is Native
Library Level Java library build level is Java
Library Level . . . . . . . . . . . . .
KYND0007E: Error Error caught attempting to
verify Native library compatibility . . . . .
KYND0008E: Unable to obtain current working
directory - Working Directory . . . . . . .
KYND0009W: MessageMessages could not be
sent to the monitoring agent . . . . . . .
KYND0010I: Data collector transport handler
thread ended . . . . . . . . . . . .
Contents
396
397
397
397
397
397
397
398
398
398
398
398
398
399
399
399
399
399
400
400
400
400
401
401
401
401
xxxiii
KYND0011E: Data collector has caught
exception Exception during sample collection
and communication . . . . . . . . . .
KYND0012E: The data collector has become
disconnected from the monitoring agent . . .
KYND0013E: Exception: Exception caught in
DataGatherer thread . . . . . . . . . .
KYND0014E: Exception: Exception caught
processing Poll request . . . . . . . . .
KYND0015E: Incompatible Agent build level
detected. Actual = Actual Level Required =
Required Level. Agent session disconnected. . .
KYND0016I: Attempting to connect to agent on
port Port Number . . . . . . . . . . .
KYND0017I: Data collector has connected to the
monitoring agent on port Port Number . . . .
KYND0018I: Data collector detailed logging is
enabled with type Type . . . . . . . . .
KYND0019I: Data collector detailed logging is
disabled . . . . . . . . . . . . . .
KYND0020I: Data collector detailed log opened
on Type . . . . . . . . . . . . . .
KYND0021W: Unable to open Type due to
exception: Exception . . . . . . . . . .
KYND0022E: I/O error encountered writing log
file Log File . . . . . . . . . . . . .
KYND0023E: Unable to capture records for DD
name Reason: Reason . . . . . . . . . .
KYND0024I: Performance Monitoring
Infrastructure Service is available for ServerName
defined at ServerRoot configuration repository .
KYND0025W: Performance Monitoring
Infrastructure Service is not available for
ServerName defined at ServerRoot configuration
repository . . . . . . . . . . . . .
KYNX Messages: WebSphere Extended
Deployment Agent . . . . . . . . . . .
KYNX0001E: WebSphere location WAS_HOME
is invalid. . . . . . . . . . . . . .
KYNX0002I: Connection with the WebSphere
cell Cell was successfully established. . . . .
KYNX0003W: Connection with the WebSphere
cell Cell failed with error Error. . . . . . .
KYNX0004I: Connection with the WebSphere
cell Cell was retried successfully. . . . . . .
KYNX0005E: Connection with the WebSphere
cell Cell failed with error Error. . . . . . .
KYNX0006I: The WebSphere cell Cell was added
to the agent. . . . . . . . . . . . . .
KYNX0007I: The WebSphere cell Cell was
removed from the agent . . . . . . . . .
KYNX0008I: Collection was disabled for the
WebSphere cell Cell. . . . . . . . . . .
KYNX0009I: Collection was enabled for the
WebSphere cell Cell. . . . . . . . . . .
KYNX0010I: Connection with the WebSphere
cell Cell failed with error Error and is scheduled
to reconnect with interval in seconds Interval. .
401
402
402
402
402
403
403
403
403
403
403
403
404
404
404
404
404
405
405
405
405
406
406
406
406
406
Chapter 3. System Messages for
ITCAM Agent for J2EE . . . . . . . 409
xxxiv
BWMIN Messages: Abstract Configurator . . . .
BWMIN0000E: An error occurred with the
installation program. . . . . . . . . . .
KYJ messages: Tivoli Enterprise Monitoring Agent
KYJA0001I: ITCAM for J2EE monitoring agent
start-up complete. . . . . . . . . . . .
KYJA0002E: ITCAM for J2EE monitoring agent
initialization failed: errorMessage. . . . . . .
KYJA0003I: The Agent configuration file file
loaded successfully. . . . . . . . . . .
KYJA0004E: The Agent configuration file file
was not found. . . . . . . . . . . . .
KYJA0005E: Agent configuration file file loading
error: errorMessage. . . . . . . . . . .
KYJA0006I: The Agent context file file loaded
successfully. . . . . . . . . . . . . .
KYJA0007W: The Agent context file file was not
found. . . . . . . . . . . . . . . .
KYJA0008W: Agent context file file loading
error: errorMessage. . . . . . . . . . .
KYJA0009I: Listening for incoming data
collector connections on port port. . . . . .
KYJA0010I: Application server discovered:
serverInfo. . . . . . . . . . . . . . .
KYJA0011I: Application server connected:
serverId. . . . . . . . . . . . . . .
KYJA0012I: Application server disconnected:
serverId. . . . . . . . . . . . . . .
KYJA0013E: Application server connection
connectionInfo failed: errorMessage.. . . . . .
KYJA0014I: Resource data monitoring started for
application server serverId resourceMethod. . . .
KYJA0015I: Resource data monitoring stopped
for application server serverId. . . . . . . .
KYJA0016I: Request data monitoring started for
application server serverId requestMethod. . . .
KYJA0017I: Request data monitoring stopped
for application server serverId. . . . . . . .
KYJA0018I: Verbose GC output monitoring
started for application server serverId with
interval gcInterval. . . . . . . . . . . .
KYJA0019I: Verbose GC output monitoring
stopped for application server serverId. . . . .
KYJA0020I: Application server log scrapping
started for application server serverId alsInfo. . .
KYJA0021I: Application server log scrapping
stopped for application server serverId. . . . .
KYJA0022E: Application server log scrapping
stopped for application server serverId with
error: errorMsg. . . . . . . . . . . . .
KYJA0023I: Take action tactId successfully
completed for application server serverId. . . .
KYJA0024E: Take action tactId failed for
application server serverId: tactReason. . . . .
KYJA0025I: Take action tactId processing started
for application server serverId. . . . . . . .
KYJA0026E: Take sample table failed for
application server serverId: errorMsg. . . . . .
CYJNW Messages: SAP NetWeaver config toolkit
CYJNW0001E: invalid Central Instance Home
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
409
409
409
409
409
409
409
410
410
410
410
410
410
411
411
411
411
411
411
412
412
412
412
412
412
413
413
413
413
413
413
CYJNW0002E: Central Instance Network Home
is not valid . . . . . . . . . . . . .
CYJNW0003E: Server Home is not valid . . .
CYJNW0004E: JNDI information is not valid
CYJNW0005E: User or Password is not valid
CYJNW0006E: HostName or IP address is not
valid. . . . . . . . . . . . . . . .
CYJNW0007E: Port number is not valid or JNDI
service is unavailable . . . . . . . . . .
CYJNW0008E: The server is not a local server
CYJNW0009E: The server has been configured
before, unconfigure it first . . . . . . . .
CYJNW0010E: The server has not been
configured . . . . . . . . . . . . .
CYJNW0011E: The server is running now. Please
stop the server and make sure the database is
running when you uninstall or unconfigure
Data Collector. Please refer to Data Collector
Installation Guide. Click Yes to continue
Unconfigure the Data Collector, Click No to
stop Unconfigure the Data Collector. . . . .
CYJNW0012E: The server is not running now.
Please start the server before you configure Data
Collector. Please refer to Data Collector
Installation Guide.. . . . . . . . . . .
CYJNW0013E: JVM GC Log should be a file not
a directory. . . . . . . . . . . . . .
CYJWCC Messages: WebSphere Application Server
Community Edition . . . . . . . . . . .
CYJWCC001E: Cannot connect to WASCE
server, check your environment and server
settings. . . . . . . . . . . . . . .
CYJWCC002E: Incorrect UserID/Password. . .
CYJWCC003E: Cannot connect to WASCE
server, check host/port. . . . . . . . . .
CYJWCC004E: The server version is not correct.
CYJWCC005E: The JAVA HOME is not correct.
Please use WASCE_JAVA_HOME defined in
SERVER_HOME/bin/setenv.bat or setenv.sh. . .
CYJWCC006E: This is not a valid WASCE server
directory. Please check the specified directory. .
CYJWCC007E: Instance name is not valid. . . .
CYJWCC008E: This server has been configured
by another DC. Please unconfigure the old DC
first. . . . . . . . . . . . . . . .
CYJWCC009E: The GC log file is not valid. . .
CYJWLC Messages: WebLogic . . . . . . . .
CYJWLC001: Cannot find weblogic server.
Check your environment and server settings. . .
CYJWLC002: Incorrect User/Password. . . . .
CYJWLC003: Cannot connect to weblogic
server,check host/port parameters. If connecting
to weblogic over SSL, please check SSL client
CA trust keystore file , and client certification
files/types/password also. . . . . . . . .
CYJWLC004: The Host Name is Incorrect. . . .
CYJWLC005: The WebLogic startup script does
not exist. . . . . . . . . . . . . . .
CYJWLC006: stdout redirection file or parent
directory does not exist.
. . . . . . . .
CYND Messages: Data Collector . . . . . . .
414
414
414
414
414
414
415
415
415
415
416
416
416
416
416
416
416
416
416
417
417
417
417
417
417
417
417
418
418
418
CYND0012I: Data Collector stopping. . . . .
CYND0013I: Data Collector stopped. . . . .
CYND0014I: Data Collector starting. . . . .
CYND0015I: Data Collector started. . . . . .
CYND0026I: Event Agent started. . . . . .
CYND0027E: Failed in publishing records to
Publish Server. . . . . . . . . . . . .
CYND0031I: Getting Publish Engine from
kernel.. . . . . . . . . . . . . . .
CYND0033I: Publish Engine successfully
downloaded from kernel. . . . . . . . .
CYND0040I: Include List: List . . . . . . .
CYND0042I: Exclude List: List
. . . . . .
CYND0046W: record1/record2 records dropped
CYND0049I: Connected to Publish
ServerHost:Server with send buffer size Buffer
Size . . . . . . . . . . . . . . .
CYND0079E: Error in getting stack trace for
thread Thread ID . . . . . . . . . . .
CYND0087I: Logging level changed from Level
to Level1. . . . . . . . . . . . . . .
CYND0219E: Failed to GetStringUTFChars . .
CYND0220E: generateThreadDump failed
. .
CYND0221E: generateThreadDump failed
. .
CYND0222E: Can't get ThreadDumpInfo class
CYND0223E: Cannot find method Method
. .
CYND0224E: Failed to allocate memory . . .
CYND0225E: Event Agent already started
. .
CYND0226E: Failed to obtain jvmmi handle for
heap dump . . . . . . . . . . . . .
CYND0227E: No javacore is generated.
. . .
CYND0228E: Unable to get RAS . . . . . .
CYND0229I: Number of CPU = Number of CPU
CYND0230E: Error in getting number of cpu
with return code = Error code . . . . . . .
CYND1001I: Native Custom Service initialized
successfully.
. . . . . . . . . . . .
CYND1001I: DC for WebLogic 8/9 . . . . .
CYND1002E: Custom Service initialization failed
because JVMPI could not be initialized
. . .
CYND1002I: DC for WebLogic. . . . . . .
CYND1003I: Native Custom Service shutdown
complete. . . . . . . . . . . . . .
CYND1003I: WebLogic Server Home . . . .
CYND1004I: Native probe started successfully.
CYND1004I: WebLogic Server Home Directory,
for example C:/bea/weblogic81. . . . . . .
CYND1005I: Native probe stopped successfully.
CYND1005I: WebLogic Server Type . . . . .
CYND1006E: The am.home system property is
undefined. . . . . . . . . . . . . .
CYND1006I: WebLogic Server Type . . . . .
CYND1007W: The weblogic.Domain system
property is undefined. . . . . . . . . .
CYND1008I: WebLogic Server 8 . . . . . .
CYND1008W: The am.nodename system
property is undefined. . . . . . . . . .
CYND1009W: The weblogic.Name system
property is undefined. . . . . . . . . .
CYND1009I: WebLogic Server 9 . . . . . .
Contents
418
418
418
418
418
419
419
419
419
419
419
420
420
420
420
420
420
421
421
421
421
421
421
421
422
422
422
422
422
422
422
422
423
423
423
423
423
423
423
423
423
424
424
xxxv
CYND1010W: The am.appserver system
property is undefined. . . . . . . . . .
CYND1010I: Select the WebLogic server version
number . . . . . . . . . . . . . .
CYND1011I: ProbeManager started successfully.
CYND1011I: Java Home . . . . . . . . .
CYND1012E: Failed to start ProbeManager. . .
CYND1012I: Java home directory name . . .
CYND1013F: JVMPI was not initialized by
native probe start exiting. . . . . . . . .
CYND1014I: Probe manager stopped
successfully. . . . . . . . . . . . . .
CYND1015F: JVMPI initialization failed. . . .
CYND1016I: Initialized event interface
successfully.
. . . . . . . . . . . .
CYND1017E: Failed to initialize JVMMI. . . .
CYND1018I: Using tracing mode:
mode_str(mode_int), and monitoring level is:
mod_level . . . . . . . . . . . . . .
CYND1019E: Error occurred during encryption.
CYND1020E: Invalid file name. . . . . . .
CYND1021I: WebLogic Server Host . . . . .
CYND1021E: Invalid user ID or password. . .
CYND1022E: Invalid file name. . . . . . .
CYND1022I: WebLogic server's jndi host name
or IP address . . . . . . . . . . . .
CYND1023E: Invalid user ID or password. . .
CYND1023I: WebLogic JMX Server Port . . .
CYND1024E: Could not open the file: filename
CYND1024I: WebLogic server port number . .
CYND1025E: No data in the file: filename . . .
CYND1025I: WebLogic Server User ID . . . .
CYND1026E: Invalid file name, user ID or
password. . . . . . . . . . . . . .
CYND1026I: WebLogic server JMX user id . .
CYND1027E: Could not open the file for
writing: filename . . . . . . . . . . .
CYND1027I: WebLogic Server Password . . .
CYND1028E: The input string is corrupt. . . .
CYND1028I: WebLogic server JMX password
CYND1029E: UID, PASSWORD or filename is
NULL. . . . . . . . . . . . . . .
CYND1029I: WebLogic Server Instance Names
CYND1030E: Your actual password and
decrypted password don't match
. . . . .
CYND1030I: The list of webLogic server
instance names . . . . . . . . . . . .
CYND1031E: The user ID read from the file is
not the same as the UID entered.
. . . . .
CYND1031I: Console Output Redirect File. . .
CYND1032E: Password read from the file is not
the same as the password entered. . . . . .
CYND1032I: The redirection File name of
WebLogic server standard output is needed
when the selected instance is a standalone
server. When the selected server is a Managed
Server, the redirection file name can be obtained
from MBean Server . . . . . . . . . .
CYND1033I: Verified user ID and password by
reading the created file, passwordfile. filename
was correctly created. . . . . . . . . .
xxxvi
424
424
424
424
424
425
425
425
425
425
425
425
426
426
426
426
426
426
426
427
427
427
427
427
427
427
428
428
428
428
428
428
428
429
429
429
CYND1033I: WebLogic Server Startup Script . .
CYND1034E: Encrypted password string is
corrupt. . . . . . . . . . . . . . .
CYND1034I: Weblogic server startup script
normally will be startWebLogic.cmd/sh. . . .
CYND1035E: Error occurred during decryption.
CYND1035I: TEMA Host Name . . . . . .
CYND1036E: The password is too long. It
should be less than max_len characters.
. . .
CYND1036I: TEMA host name can be found in
itcamdc/etc/kwjdc.properties.. . . . . . .
CYND1037E: JVMPI could not create a Raw
Monitor for GlobalLock. . . . . . . . .
CYND1037I: TEMA Port Number . . . . .
CYND1038E: Global lock was created before
initialization of JVMPI. . . . . . . . . .
CYND1038I: TEMA port number can be found
in itcamdc/etc/kwjdc.properties. . . . . . .
CYND1039I: JVM GC Log . . . . . . . .
CYND1039W: This is an unknown event type,
TypeID: evt_type . . . . . . . . . . .
CYND1040E: The EventAgent was not started
and cannot manage ThreadData. . . . . . .
CYND1040I: JVM GC log is used to obtain java
GC log. . . . . . . . . . . . . . .
CYND1041W: Failed to send data. . . . . .
CYND1041I: WebLogic Server Version . . . .
CYND1042E: Event Queue is NULL for Thread,
TID: tid . . . . . . . . . . . . . .
CYND1042I: Please enter the WebLogic Home
and Java Home. WebLogic Server Home is the
installation directory of WebLogic(e.g.
C:\\bea\\weblogic8). WebLogic Server Version
is the major version of WebLogic server. Java
Home is the installation directory of JDK that is
used to run Weblogic server. . . . . . . .
CYND1043W: Overall events
dropped/deleted:evtDropCnt . . . . . . .
CYND1043I: Please enter the information of
WebLogic Server for server instances discovery
WebLogic Server Host is the name of host
where the admin server is located. WebLogic
JMX service port is the listening port for the
JMX service of WebLogic. User ID and
password are required in order to get JMX Data
from MBean Server. . . . . . . . . . .
CYND1044I: Events dropped cnt for thread
threadNamebecause they exceeded event queue
limit of queueLimit
. . . . . . . . . .
429
429
429
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
429
429
430
430
430
430
430
430
431
431
431
431
431
431
432
432
432
432
432
432
433
433
CYND1044I: Please select server instance to
instrument. Please select the Server instance you
expect to instrument. After selecting the
instance, please input following information
which is used to configure DC to collect data
from related WebLogic server instance.
WebLogic Server Host is the name of host
where the instrumented server is located.
WebLogic JMX service Port is the listening port
for the JMX service of WebLogic server. User ID
and password are required by DC in order to
get JMX data from MBean server. Startup script
is the script that is used to start WebLogic
Server instance. . . . . . . . . . . .
CYND1045I: Modify WebLogic startup script
CYND1045W: Thread data creation failed. . .
CYND1046I: EvtAgentManager started. . . .
CYND1046I: Modify WebLogic startup script
CYND1047I: EvtAgentManager stopped. . . .
CYND1047I: UNIX 64bit JVM . . . . . . .
CYND1048E: Class file is corrupt. . . . . .
CYND1048I: Validating MBean Server related
information . . . . . . . . . . . . .
CYND1049E: Bad class file magic number:magic
CYND1049I: Validating MBean Server Host
name and service point . . . . . . . . .
CYND1050E: Failed to open library: libName . .
CYND1050I: Validating Startup Script . . . .
CYND1051I: Memory limit is less than the
minimum limit: memLimit MB
. . . . . .
CYND1051I: Retreiving Server information from
MBean Server . . . . . . . . . . . .
CYND1052I: Memory monitor properties,
ULimit: memUlimit bytes, Accept Threshold:
threadHold bytes, URL Limit: urlUlimit, SQL
Limit: sqlUlimit
. . . . . . . . . . .
CYND1052I: Validating Java home, Server
Home, Server version . . . . . . . . .
CYND1053I: Queue counter resets every
resetTimerCount iterations. . . . . . . . .
CYND1054W: Memory Limit reached, Data
Collector stopped accepting data, Limit:
usedMemUlimit Memory Utilization: memTaken .
CYND1055I: Memory utilization is below the
limit; the Data Collector is accepting data, Limit:
usedMemUlimit Memory Utilization: memTaken .
CYND1055I: TEMA Host Name . . . . . .
CYND1056W: Network Agent Thread is not
started/alive/ready; rejecting send data. . . .
CYND1056I: The TEMA host name can be
found in itcamdc/etc/kwjdc.properties. . . .
CYND1057W: The queue is full and exceeds the
buffer limit. . . . . . . . . . . . . .
CYND1058I: Validating Server Version . . . .
CYND1058W: Publish Server lookup failed. . .
CYND1059E: The Data Collector failed to
connect to host %s /port %d. Error number is
%d
. . . . . . . . . . . . . . .
CYND1060I: Successfully connected to Publish
Server Host: %s Port: %d Buffer Size: %d . . .
CYND1061I: Wrong server home selected.
. .
433
433
433
434
434
434
434
434
434
434
434
434
435
435
435
435
435
435
435
436
436
436
436
436
436
436
437
437
437
CYND1062I: The selected Weblogic Server
Version does not match the Weblogic Server
Home.. . . . . . . . . . . . . . .
CYND1063I: The selected Weblogic Server
Startup script was incorrect. . . . . . . .
CYND1064I: A clean server instance cannot be
unconfigured. . . . . . . . . . . . .
CYND1065I: Current server instance is already
configured. . . . . . . . . . . . . .
CYND1068I: weblogic 9 is not compatible with
selected JAVA HOME, please select jdk version
1.5 or above.. . . . . . . . . . . . .
CYND1069I: The instance has been configured
by another DC, please unconfigure it firstly. . .
CYND1070I: The instance has been configured
by RTT without fixpack, please reconfigure the
instance after apply the fixpack for RTT. . . .
CYND1071I: GC log file path doesn't exist! . .
CYND1072E: SSL Trust CA keystore file doesn't
exists. . . . . . . . . . . . . . . .
CYND1073E: SSL client certificate file doesn't
exist:{0} . . . . . . . . . . . . . .
CYND1074E: Element count not equals in
WL_SSL_CERT_TYPES and
WL_SSL_CERT_FILES. . . . . . . . . .
CYND1075E: SSL certificate file types contains
invalid type string, legal type string should be
PEM or DER. . . . . . . . . . . . .
CYND1076E: Element count not equals in
WL_SSL_CERT_TYPES and
WL_SSL_CERT_FILES. . . . . . . . . .
CYND1077E: SSL certificate file types contains
invalid type string, legal type string should be
PEM or DER. . . . . . . . . . . . .
CYND1078E: Set SSL client certificates failed.
CYND1079E: {0} has too few files,{0} should
contain at least two files: SSL client private key
and client certificate file.. . . . . . . . .
CYND1060I: WebLogic Portal Server 8 . . . .
CYND1061E: Socket write to Publish Server
failed, [%s:%d], ERRNO: %s . . . . . . .
CYND1062I: Network agent thread started. . .
CYND1063I: Successfully connected to the
Publish Server socket. . . . . . . . . .
CYND1064E: Failed to connect to the Publish
Server socket. . . . . . . . . . . . .
CYND1065W: Could not obtain Publish Server
proxy details from the Kernel.
. . . . . .
CYND1066I: NetworkAgentManager started.
CYND1066I: WebLogic Server domain name . .
CYND1067I: NetworkAgentManager stopped.
CYND1067I: WebLogic Server domain name . .
CYND1068E: am.home was not found; failed to
initialize the Property Manager. . . . . . .
CYND1069E: Default property file %s not
found. . . . . . . . . . . . . . . .
CYND1070I: Using property file %s. . . . . .
CYND1071I: PropertyMgr started. . . . . .
CYND1072I: Thread Manager started. . . . .
CYND1073I: Thread Manager stopped.
. . .
Contents
437
437
437
437
437
438
438
438
438
438
438
438
438
438
438
438
438
438
439
439
439
439
439
439
439
439
439
439
440
440
440
440
xxxvii
CYND1074E: Failed to retrieve the command
arguments for WAS. . . . . . . . . . .
CYND1075E: Failed to retrieve command line
arguments for Stand Alone Java. . . . . . .
CYND1076E: Failed to construct
ThreadDumpInfo object. . . . . . . . .
CYND1077E: Probe is disabled; cannot return
stack trace. . . . . . . . . . . . . .
CYND1078I: Using modfile: %s . . . . . .
CYND1079I: Failed to write modfile. . . . .
CYND1080I: Using probe level %d. . . . . .
CYND1081I: Native library build TIME : %s
DATE: %s . . . . . . . . . . . . .
CYND1082I: Successfully registered
defineNativeMethodsForClassNative for
com.cyanea.bcm.bootstrap.BcmBootstrap.class. .
CYND1083E: Cannot find
com.cyanea.bcm.bootstrap.BcmBootstrap.class. .
CYND1084I: Heap Snapshot not supported by
default; set internal.doheapdump=true to
activate it. . . . . . . . . . . . . .
CYND1085W: Failed to open stdout. . . . .
CYND1086E: Unable to send CTRL+BREAK
event to JVM process. Err(%ld) . . . . . .
CYND1087E: Unable to send SIGQUIT to JVM
process. Err(%ld) . . . . . . . . . . .
CYND1088E: Cannot get Java system property
cyanea.probe.stdout. . . . . . . . . . .
CYND1089E: Cannot open
cyanea.probe.stdout:%s . . . . . . . . .
CYND1090E: Failed to retrieve command line
arguments for WebLogic. . . . . . . . .
CYND1091E: Incorrect method id from method
stack . . . . . . . . . . . . . . .
CYND1092E: Cannot find the the method stack.
CYND1093E: Run out of method stack. . . . .
CYND1094E: Primitive Stack overflow. . . . .
CYND1095E: Primitive Hash overflow. . . . .
CYND1096E: MPHash overflow. . . . . . .
CYND1097E: MPData table overflow. . . . .
CYND1098I: Total estimated memory allocated
by Method Profiling, %s MB. . . . . . . .
CYND1100I: Region Mask from Kernel = Kernel
CYND1101I: Please restart your Application
server to enable the configuration and ensure to
shutdown WebLogic server instance via the
Administration Console. For more detailed
information about how to shut down WebLogic
Server, please refer to URL:
http://e-docs.bea.com/wls/docs81/
ConsoleHelp/startstop.html. If a node manager
is used to start and stop the configured server
instance, please restart the node manager too. If
a server instance configured by Data Collector is
an administrative server instance, when the
server is shutdown there are some exceptions
throwing and the server instance will be
restarted automatically. In this case, please stop
it again and start it using startup command. . .
CYND1102I: Region ID = 0xID8X . . . . .
CYND1102I: JNDI Protocol Type . . . . . .
xxxviii
440
440
440
440
441
441
441
441
441
441
441
441
442
442
442
442
442
443
443
443
443
443
444
444
444
444
444
444
445
CYND1103I: Region Mask = 0xMask8X . . . .
CYND1103I: t3 . . . . . . . . . . . .
CYND1104E: Cannot get the server common
storage with error number = Error . . . . .
CYND1104I: t3s(one way SSL)
. . . . . .
CYND1105I: Enqueue server, Server, exclusively
with return code = RC . . . . . . . . .
CYND1105I: t3s(two way SSL) . . . . . .
CYND1106I: Enqueue server, Server, shared with
return code = RC . . . . . . . . . . .
CYND1106I: Select the JNDI Procotol type. . .
CYND1107I: Gps counter file = Counter. . . .
CYND1107I: SSL trust CA key store file . . .
CYND1108I: Gps counter get from file = File
CYND1108I: Select the trust CA key store file
used by SSL to verify the server certificate. . .
CYND1109I: Gps counter file, File, created . .
CYND1109I: SSL client certificate file type
strings. . . . . . . . . . . . . . .
CYND1110I: SSL client certificate file type
strings, should be DER or PEM, multiple file
type strings are separated by |. . . . . . .
CYND1111I: SSL client certificate files . . . .
CYND1112E: Unable to open counter file, File
CYND1112I: SSL client certificate files, the first
file should be private key file. All but the first
of the certificates are issuer certificates for the
previous certificate. multiple files are separated
by |. . . . . . . . . . . . . . . .
CYND1113I: Password for encrypted SSL client
RSA private key . . . . . . . . . . .
CYND1114I: Password for encrypted SSL client
RSA private key; if the file is not encrypted,
password is not required. . . . . . . . .
CYND2001I: DC for Tomcat 5 . . . . . . .
CYND2002I: DC for Tomcat . . . . . . .
CYND2003I: Tomcat Server Home . . . . .
CYND2004I: Tomcat Server Home Directory, for
example, C:/jakarta-tomcat-5.0.28. . . . . .
CYND2005I: Tomcat Server Type . . . . . .
CYND2006I: Tomcat Server Type . . . . . .
CYND2008I: Tomcat Server 5.0 . . . . . .
CYND2009I: Tomcat Server 5.5 . . . . . .
CYND2010I: Select the Tomcat server version
number . . . . . . . . . . . . . .
CYND2011I: Java Home . . . . . . . . .
CYND2012I: Java home directory name . . .
CYND2021I: Tomcat Server Startup Script . . .
CYND2022I: The Tomcat server startup script
usually will be catalina.bat/sh. . . . . . .
CYND2023I: Instance Names . . . . . . .
CYND2024I: List of instances . . . . . . .
CYND2026I: Standard Out File . . . . . .
CYND2027I: Standard Out File . . . . . .
CYND2029I: <html><font size=4>Tomcat Server
Home is Tomcat installation location.
<br>Tomcat Server Version is the specified
version. <br>Java Home is JDK installation
location</html> . . . . . . . . . . .
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
445
445
445
445
445
445
445
446
446
446
446
446
446
446
446
446
446
447
447
447
447
447
447
447
447
448
448
448
448
448
448
448
448
448
448
448
449
449
CYND2030I: Tomcat Server Startup Script is the
full path of the Tomcat startup script.( e.g.
C:/tomcat5.5/bin/catalina.bat ) Instance Name
is Tomcat Server Instance Name that will be
shown on VE.( e.g. tomcat55instance ) Caution:
Tomcat Startup Script should be
catalina.sh/catalina.bat but startup.sh/
startup.bat. . . . . . . . . . . . . .
CYND2031I: Server Version. . . . . . . .
CYND2035I: TEMA Host Name . . . . . .
CYND2036I: TEMA host name can be found in
itcamdc/etc/kwjdc.properties.. . . . . . .
CYND2037I: TEMA Port Number . . . . .
CYND2038I: TEMA port number can be found
in itcamdc/etc/kwjdc.properties. . . . . . .
CYND2039I: JVM GC Log . . . . . . . .
CYND2040I: JVM GC log is used to obtain the
java GC log. . . . . . . . . . . . . .
CYND2050I: Use JDK as 64 bit? . . . . . .
CYND2051I: Use JDK as 64 bit? . . . . . .
CYND2025I: Cannot find the file
catalina.properties at tomcat home, check the
file!. . . . . . . . . . . . . . . .
CYND2052I: Use JDK as 64 bit? . . . . . .
CYND2053I: Cannot find startup script! . . .
CYND2054I: The server is not the correct
version! . . . . . . . . . . . . . .
CYND2055I: The server was configured before!
CYND2056I: RTT61 Fixpack needed!. . . . .
CYND2057I: This instance name is already in
use! . . . . . . . . . . . . . . .
CYND2058I: The server is running now. Please
stop the server when you uninstall or
unconfigure Data Collector. Please refer to Data
Collector Installation Guide. . . . . . . .
CYND2059I: A Tomcat server shouldn't use
different instance name during reconfiguration! .
CYND2060I: GC log file path doesn't exist! . .
CYND3001I: DC for JBoss 3/4 . . . . . . .
CYND3002I: DC for JBoss . . . . . . . .
CYND3003I: JBoss Server Home . . . . . .
CYND3004I: JBoss Server Home Directory, For
example C:/jboss-4.0.4 . . . . . . . . .
CYND3005I: JBoss Server Type . . . . . .
CYND3006I: JBoss Server Type . . . . . .
CYND3008I: JBoss 4 . . . . . . . . . .
CYND3009I: JBoss 3 . . . . . . . . . .
CYND3010I: Select the JBoss server version . .
CYND3011I: Java Home . . . . . . . . .
CYND3012I: Java home directory name . . .
CYND3021I: JBoss Server Host . . . . . .
CYND3022I: JNDI host name or IP address of
the target JBoss server . . . . . . . . .
CYND3023I: JBoss JNP service Port . . . . .
CYND3024I: JNDI port of the target JBoss server
CYND3025I: JBoss Server User ID . . . . .
CYND3026I: JDNI user of the target JBoss server
CYND3027I: JBoss Server Password . . . . .
CYND3028I: JDNI password of the target JBoss
server . . . . . . . . . . . . . . .
CYND3029I: JBoss Server Instance Names . . .
449
449
449
449
449
450
450
450
450
450
450
450
450
450
451
451
451
451
451
451
451
451
451
451
451
451
452
452
452
452
452
452
452
452
452
452
453
453
453
453
CYND3030I: JBoss Server Instance Names . . .
CYND3033I: JBoss Server Startup Script . . .
CYND3034I: JBoss server startup script,
normally will be run.bat/sh. . . . . . . .
CYND3041I: JBoss Output Redirect File . . .
CYND3042I: The file to which JBoss server's
stdout will be redirected. . . . . . . . .
CYND3057I: TEMA Port Number . . . . .
CYND3058I: The TEMA port number can be
found in itcamdc/etc/kwjdc.properties. . . .
CYND3059I: JVM GC Log . . . . . . . .
CYND3060I: JVM GC log is used to obtain the
java GC log. . . . . . . . . . . . . .
CYND3061I: JBoss Server Version. . . . . .
CYND3071I: Enter the JBoss Server Information
and Java Home. JBoss Server Host is the host
name of the machine where JBoss is located.
JBoss JNP service Port is the listening port for
the bootstrap JNP service of JBoss. Need to
input user/password? is only checked when
security is enabled. User ID and Password are
used only when security of JBoss is enabled.
JBoss Server Home is the installation directory
of JBoss( e.g. C:/JBoss-4.0.3SP1). JBoss Server
Version is the major version of JBoss server. Java
Home is the JDK installation directory. . . . .
CYND3072I: Enter the startup script of JBoss
Server . Startup Script is full path of run.bat (on
Windows) or run.sh (on Linux/UNIX). . . . .
CYND3073I: Select the server that will be
configured. . . . . . . . . . . . . .
CYND3081I: Use JDK as 64 bit? . . . . . .
CYND3082I: Use JDK as 64 bit? . . . . . .
CYND3083I: Use JDK as 64 bit? . . . . . .
CYND3091I: Need to input user/password? . .
CYND3092I: Need to input user/password? . .
CYND3093I: Need to input user/password? . .
CYND3094I: Validating Java home, Server
Home, Server version . . . . . . . . .
CYND3095I: Validating JBoss Server Host name
and JNP service port . . . . . . . . . .
CYND3096I: Validating Startup Script . . . .
CYND3097I: Retrieving Server information from
JBoss Server . . . . . . . . . . . . .
CYND4001I: DC for NetWeaver 2004 . . . .
CYND4001I: Data Collector Controller is
listening at port portNumber . . . . . . .
CYND4002I: DC for NetWeaver . . . . . .
CYND4002I: After joining the Kernel, security
manager is: Securitymanager . . . . . . .
CYND4003E: Failed to start controller. . . . .
CYND4003I: NetWeaver Server Type . . . .
CYND4004I: Received notification of probe
configuration update: Probeconfig . . . . . .
CYND4004I: NetWeaver Server Type . . . .
CYND4005E: Failed to allocate port to
controller. . . . . . . . . . . . . .
CYND4005I: NetWeaver Server Version. . . .
CYND4006I: NetWeaver Server 2004. . . . .
CYND4007I: Select the NetWeaver server
version number . . . . . . . . . . .
Contents
453
453
453
453
453
453
453
454
454
454
454
454
454
455
455
455
455
455
455
455
455
455
455
455
455
455
455
456
456
456
456
456
456
456
457
xxxix
CYND4006I: Received notification that probe
configuration was removed. . . . . . . .
CYND4007E: Failed to set monitoring level. . .
CYND4008I: Java Home . . . . . . . . .
CYND4008I: Native Probe and JAVA-JNI threads
successfully started. . . . . . . . . . .
CYND4009I: Java home directory name . . .
CYND4009E: Java-JNI threads were not started.
CYND4010E: Failed to start native probe. . . .
CYND4011I: You are trying to stop a Data
Collector which was not started successfully.
.
CYND4012E: Failed to stop command agent.
CYND4013I: Probe Controller stopped
successfully. . . . . . . . . . . . . .
CYND4014E: Error occurred while stopping the
probe. . . . . . . . . . . . . . . .
CYND4015W: Event agent is alive. Cannot start
another event agent. . . . . . . . . . .
CYND4016W: Network agent is alive. Cannot
start another agent. . . . . . . . . . .
CYND4017W: Publish Server status thread is
alive. Cannot start another agent. . . . . .
CYND4018I: NetWeaver Server Host . . . .
CYND4018E: Failed to start Publish Server
agent. . . . . . . . . . . . . . . .
CYND4019E: Failed to stop Publish Server
agent. . . . . . . . . . . . . . . .
CYND4019I: NetWeaver server's jndi host name
or IP address . . . . . . . . . . . .
CYND4020E: Failed to get sampling rate. . . .
CYND4020I: NetWeaver Server Port . . . . .
CYND4021I: NetWeaver server port number . .
CYND4021I: Scheduler configuration is null for
ID: Scheduleid . . . . . . . . . . . .
CYND4022E: Failed to set scheduler
configuration. . . . . . . . . . . . .
CYND4022I: NetWeaver Server User ID . . .
CYND4023E: Failed to update scheduler
configuration. . . . . . . . . . . . .
CYND4023I: NetWeaver Server Jndi User ID
CYND4024I: NetWeaver Server Password . . .
CYND4024I: Invalid monitoring level: Modlevel
specified, ignore the new monitoring value. . .
CYND4025E: Failed to set new monitoring level.
CYND4025I: NetWeaver Server Jndi User ID
CYND4026E: Failed to get default monitoring
level. . . . . . . . . . . . . . . .
CYND4026I: NetWeaver Server Instance Names
CYND4027I: Probe security is not enabled. . .
CYND4027I: The list of NetWeaver Server
Instance names . . . . . . . . . . . .
CYND4028E: Error occurred when creating
probe controller loginstub. . . . . . . . .
CYND4028I: Central Instance Installation . . .
CYND4029I: Probe security is enabled.
. . .
CYND4029I: Local Dialog Instance Installation
CYND4030E: The Am home path is not set. Set
the system property Am.Home for the Data
Collector.
. . . . . . . . . . . . .
CYND4030I: Distributed Dialog Instance
Installation . . . . . . . . . . . . .
xl
457
457
457
457
457
457
457
458
458
458
458
458
458
458
459
459
459
459
459
459
459
459
460
460
460
460
460
460
460
461
461
461
461
461
461
461
461
462
462
462
CYND4031E: An error occurred when setting up
Cyanea custom service. . . . . . . . . .
CYND4031I: Netweaver DC installation type
CYND4032E: Unable to join Kernel, retrying.
CYND4032I: Central Instance Home . . . . .
CYND4033E: Failed to start probe controller.
CYND4033I: Central Instance Home . . . . .
CYND4034E: Unable to save monitoring level.
CYND4034I: Server Home . . . . . . . .
CYND4035E: Unable to find monitoring
file:Modfile . . . . . . . . . . . . .
CYND4035I: Server Home . . . . . . . .
CYND4036E: Unable to read monitoring file:
Modfile . . . . . . . . . . . . . .
CYND4036I: Central Instance Network Home
CYND4037I: Central Instance Network Home
CYND4037W: Unknown proxy
host:Proxyhostname. . . . . . . . . . .
CYND4038E: Unable to load Cyanea probe
configuration file: Probeconfigfile . . . . . .
CYND4038I: Please select the installation type of
Data Collector for NetWeaver. . . . . . . .
CYND4039E: Error occurred while getting
product version number. . . . . . . . .
CYND4039I: DC will monitor the central
instance. Server Home: The absolute path of
central instance home directory. (e.g.,
'/usr/sap/J2E/JC00') . . . . . . . . . .
CYND4040E: Failed to load library: Libname . .
CYND4040I: Data Collector will monitor the
local dialog instance. Please enter server home
and central instance home. Server Home: The
absolute path of local dialog instance home
directory.(e.g., '/usr/sap/J2E/J01'). Central
Instance Home: the absolute path of central
instance home directory.(e.g.,
'/usr/sap/J2E/JC00') . . . . . . . . . .
CYND4041I: DC will monitor the distributed
dialog instance. Please enter server home,
central instance home and central instance
network home. Server Home: The absolute path
of distributed dialog instance home
directory.(e.g., '/usr/sap/J2E/J01') Central
Instance Home: The absolute path of central
instance home directory.(e.g.,
'/usr/sap/J2E/JC00')Central Instance Network
Home: A local path mounted from central
instance home directory.(e.g.,
'/mnt/usr/sap/J2E/JC00') . . . . . . . .
CYND4041I: Native custom service start
notification issued successfully. . . . . . .
CYND4042E: An error occurred in native
custom service start. . . . . . . . . . .
CYND4042I: Please enter the information of
NetWeaver for Server Instances Discovery
NetWeaver Server Host: the qualified hostname
of local machine.NetWeaver Server Port: the P4
port of the SAP NetWeaver instance. NetWeaver
Server User ID and password: required in order
to get JMX Data from MBean Server. for
example: Administrator/password . . . . .
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
462
462
462
463
463
463
463
463
463
464
464
464
464
464
464
465
465
465
465
465
466
466
466
466
CYND4043I: Select monitoring instance. . . .
CYND4043I: Setting probe Sampling Rate for
monitoring level (L0, L1, L2, L3):L0, L1, L2, L3,
Usesystemdefault: Issystemdefault
. . . . .
CYND4044I: Enter Server Information . . . .
CYND4044I: Incorrect system default
monitoring level: Modlevel . . . . . . . .
CYND4045I: Incorrect monitoring level: Modlevel
CYND4046E: Unable to find monitoring file:
Modfile . . . . . . . . . . . . . .
CYND4047I: Loaded the native library: libName
CYND4048E: Failed to deserialize marshalled
object.
. . . . . . . . . . . . . .
CYND4049E: Failed to get the proxy server from
Kernel. . . . . . . . . . . . . . .
CYND4050E: An error occurred during the start
of the proxy task thread. . . . . . . . .
CYND4051I: Join Proxy Server and Kernel
successfully. Service ID: serviceID, probeID . . .
CYND4052E: Failed to join Proxy Server and
Kernel. . . . . . . . . . . . . . .
CYND4052I: Install 64bit DC . . . . . . .
CYND4053E: Am Home is not defined, not
initializing security module. . . . . . . .
CYND4053I: Install 64bit DC . . . . . . .
CYND4054I: The Cyanea password file
(Cyanea.Pswdfile) is not defined.
. . . . .
CYND4054I: JVM GC Log . . . . . . . .
CYND4055E: The password file: Pwdfile does
not exist. . . . . . . . . . . . . . .
CYND4055I: JVM GC log that is used to obtain
java GC log. . . . . . . . . . . . . .
CYND4056I: Notes: 1)On Windows platform,
the path separator should be '\\'; On
UNIX/Linux platform, the path separator
should be '/'.2) Please also refer to the
installation guide for post-installation for
additional configuration steps required. . . .
CYND4061E: Unable to start command agent.
CYND4062I: Command agent controller started
at port. . . . . . . . . . . . . . .
CYND4063I: Unable to obtain request
information. . . . . . . . . . . . . .
CYND4064W: Exception while reading the Java
core file. . . . . . . . . . . . . . .
CYND4065E: An error occurred while sending
Heap dump data to the Publish Server. . . .
CYND4066E: An error occurred while
initializing JMX agent. . . . . . . . . .
CYND4067E: An error occurred while creating
object name: . . . . . . . . . . . .
CYND4068I: No Mbean object found of type: in
process . . . . . . . . . . . . . .
CYND4069E: An error occurred while creating
Adminclient. . . . . . . . . . . . .
CYND4070E: An error occurred while querying
for configuration objects of type: . . . . . .
CYND4071E: An error occurred while querying
for configuration attributes: . . . . . . .
CYND4072E: Deploymentmanager.Rmi.Port
property is not set in Datacollector.Properties. .
466
467
467
467
467
467
467
467
467
468
468
468
468
468
468
469
469
469
469
469
469
469
470
470
470
470
470
470
470
470
471
CYND4073E: Deploymentmanager.Rmi.Host
property is not set in Datacollector.Properties. .
CYND4074E:
Deploymentmanager.Rmi.Connection property
is not set in Datacollector.Properties. . . . .
CYND4075E: Failed to create Adminservice. . .
CYND4076E: Server Mbean not found . . . .
CYND4077E: Error while registering JMX client.
CYND4078E: Probeservice did not start
successfully.
. . . . . . . . . . . .
CYND4079E: Error while retrieving PMI data
for the: component . . . . . . . . . . .
CYND5001I: DC for WebSphere Application
Server Community Edition . . . . . . . .
CYND5002I: DC for WebSphere CE . . . . .
CYND5003I: WebSphere CE Server Home . . .
CYND5004I: WebSphere CE Server Home
Directory, for example C:/Program
Files/IBM/WebSphere/
AppServerCommunityEdition.. . . . . . .
CYND5005I: WebSphere CE Server Type . . .
CYND5006I: WebSphere CE Server Type . . .
CYND5008I: 1.0.1 . . . . . . . . . . .
CYND5010I: Select the WebSphere Community
Edition server version number . . . . . .
CYND5011I: Java Home . . . . . . . . .
CYND5012I: Java home directory name . . .
CYND5023I: WebSphere CE RMI Port . . . .
CYND5024I: The RMI port of the target
WebSphere CE server. . . . . . . . . .
CYND5025I: WebSphere CE User ID. . . . .
CYND5026I: The user of the target WebSphere
CE server. . . . . . . . . . . . . .
CYND5027I: WebSphere CE Password . . . .
CYND5028I: The password of the target
WebSphere CE server. . . . . . . . . .
CYND5029I: WebSphere CE Server Instance
Name . . . . . . . . . . . . . . .
CYND5030I: WebSphere CE Server Instance
Name . . . . . . . . . . . . . . .
CYND5055I: TEMA Host Name . . . . . .
CYND5056I: TEMA host name that can be
found in itcamdc/etc/kwjdc.properties. . . .
CYND5057I: TEMA Port Number . . . . .
CYND5058I: TEMA port number that can be
found in itcamdc/etc/kwjdc.properties. . . .
CYND5059I: JVM GC Log . . . . . . . .
CYND5060I: JVM GC log that is used to obtain
java GC log. . . . . . . . . . . . . .
CYND5061I: WebSphere CE Server Version . .
CYND5071I: Enter the WebSphere CE Home
and Java Home. WebSphere CE Server Home is
the installation directory of WebSphere CE( for
example, C:/Program Files/IBM/WebSphere/
AppServerCommunityEdition ). WebSphere CE
Server Version is the major version of
WebSphere CE server. Java Home is the JDK
installation directory used by WebSphere CE
Server.. . . . . . . . . . . . . . .
471
471
471
471
472
472
472
472
472
472
473
473
473
473
473
473
473
473
473
473
474
474
474
474
474
474
474
474
474
474
475
475
475
471
Contents
xli
CYND5072I: Enter the information for
WebSphere CE Server for server discovery and
configuration. WebSphere CE RMI Port is the
listening port for the RMI service. User ID and
Password are the credentials used to access RMI
service. . . . . . . . . . . . . . .
CYND5073I: Enter the server instance name.
Server Instance Name is the name of the server
instance. . . . . . . . . . . . . . .
CYND5237I: Using SSL server socket for
component: CommandAgent. All clients
connecting to this component MUST connect via
SSL, else the client socket may hang till the
timeout expires. No user action is required. . .
CYND5238E: [BCM] CtgCallBack Error Message:
CYND5239I: ITCAM Product Mode: productmode
CYND5240I: TCAM Product Mode changed to:
productmode . . . . . . . . . . . . .
CYND5241E: ITCAM Product Mode changed
failed: productmode . . . . . . . . . .
CYND5242E: Data Collector could not connect
to Publishing Server. . . . . . . . . . .
CYND5243E: Data Collector tried to connect to
Publishing Server numberOfTimes times, but
failed. . . . . . . . . . . . . . . .
CYND6000E: Exception occurred while parsing
XML file. . . . . . . . . . . . . . .
CYND6001E: Unexpected exception. Refer to the
tracing log. . . . . . . . . . . . . .
CYND6001I: Data Collector Controller is
listening at port portNumber . . . . . . .
CYND6001I: Yes . . . . . . . . . . .
CYND6001W: Returning original Server Socket
in multiple context mode, provider might not
support this implementation . . . . . . .
CYND6002E: ObjectName invalid format MalformedObjectNameException was produced.
CYND6002I: JMXConnectorServer was
successfully initialized . . . . . . . . .
CYND6002I: No . . . . . . . . . . .
CYND6002W: Not pure secure mode: server
trusted by subject . . . . . . . . . . .
CYND6003E: Unable to load configuration file:
Probeconfigfile . . . . . . . . . . . .
CYND6003I: PING request was processed. . .
CYND6003I: J2SE Server Home . . . . . .
CYND6003W: Insecure mode: it is
recommended to turn on SSL . . . . . . .
CYND6004E: GC logging is not enabled. . . .
CYND6004I: Secure Socket Factory successfully
initialized . . . . . . . . . . . . .
CYND6003I: J2SE Server Home . . . . . .
CYND6003I: J2SE Server Home . . . . . .
CYND6005E: GC Log file name is not specified
in JVM parameters or in GCLogVariable
. . .
CYND6005I: Pure secure mode: using default
trusted managers . . . . . . . . . . .
CYND6005I: Server Type . . . . . . . .
CYND6006E: Error during Regexp subsystem
initialization. Refer to the tracing log. . . . .
CYND6006I: J2SE Server Type . . . . . . .
xlii
475
475
475
475
476
476
476
476
476
476
477
477
477
477
477
477
477
477
477
477
477
478
478
478
478
478
478
CYND6007E: KeyStore location or store
password or key password are not defined . .
CYND6008E: No SSL compatible server socket
implementation is available, if you are using
JDK 1.3, download JSSE extension and install it
following JDK documentation
. . . . . .
CYND6008I: J2SE Application Name . . . .
CYND6009E: Exception when initializing SSL
parameters . . . . . . . . . . . . .
CYND6009I: Fill this table with required
parameters to connect the embedded JMX
Server.. . . . . . . . . . . . . . .
CYND6010E: Exception in the task. Refer to the
tracing log. . . . . . . . . . . . . .
CYND6010I: A name less then 50 char(s), no
<space>\\/&*: . . . . . . . . . . . .
CYND6011E: Cannot open the GC Log file:
GCLogfile
. . . . . . . . . . . . .
CYND6011I: Java Home . . . . . . . . .
CYND6012I: Java home directory name . . .
CYND6021I: JMX Server Host . . . . . . .
CYND6022I: JMX host name or IP address of
the target J2SE server. . . . . . . . . .
CYND6023I: JMX Server Port . . . . . . .
CYND6024I: JMX port of the target J2SE server
CYND6025I: JMX Server User ID . . . . . .
CYND6026I: JMX user of the target J2SE
application . . . . . . . . . . . . .
CYND6027I: JMX Server Password . . . . .
CYND6028I: JMX password of the target J2SE
application . . . . . . . . . . . . .
CYND6029I: J2SE Application Instance Name
CYND6030I: A name less then 50 char(s), no
<space>\\/&*: . . . . . . . . . . . .
CYND6031I: GC Collector MBean was
registered, object name: objectName . . . . .
CYND6031I: Replace the existing startup script
CYND6032E: JMXConnectorServer was not
found. . . . . . . . . . . . . . . .
CYND6032I: Generate sample script . . . . .
CYND6033E: RequestAggregator was not found
CYND6033I: J2SE Application Startup Script . .
CYND6033W: Skip the incomplete GC event.
CYND6034I: J2SE Application startup script. . .
CYND6035I: Is there an embedded JMX Server ?
(Yes for JDK 1.5) . . . . . . . . . . .
CYND6036I: Accessed by remote connection ?
CYND6037I: Enter the J2SE Application
Information and Java Home. J2SE Server Home
is the J2SE application working directory( e.g.
C:/MyProg ). J2SE Application Name is the
application name in letter or number without
space( e.g. MyProg ). Java Home is java home
that application uses( e.g. C:/JDK14 ). J2SE Main
Class is main class name( e.g. com.myprog.Main ).
478
478
478
478
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
479
479
479
479
479
479
479
479
479
479
479
479
480
480
480
480
480
480
480
480
480
480
480
480
480
480
481
481
481
481
481
CYND6038I: Enter the J2SE Application JMX
Information. Is there an embedded JMX Server ?
Answer Yes if there is existing embedded JMX
Server running with J2SE application server(Yes
for JDK1.5 ). Access by remote connection ?
Answer Yes if JMX Server is connected
remotely(e.g. JDK1.5 is connected locally, answer
No.). JMX Server Host, JMX Server Port, JMX
Server User ID, JMX Server Password Required
JMX connection parameters for JMX Server
which is connected remotely. . . . . . . .
CYND6039I: Enter the J2SE Application Startup
Information. J2SE Application Instance Name is
name of instance in letter or number without
space( e.g. MyProg1). Replace the existing
startup script : replace an existing startup script.
J2SE Application Startup Script is startup script
path( e.g. C:/MyProg/bin/start.bat ). Java
Argument Macro is Macro String to be replaced
in startup script. Generate sample script :
dcstartup.sh or dcstartup.bat, used to launch the
application after Data Collector is configured.
Script Path is the directory for the sample
startup script( e.g. C:/MyProg/bin ). JVM
Arguments is JVM options without main class
name( e.g. -Dvarible1=value1 ). Program
Arguments is program arguments after main
class. . . . . . . . . . . . . . . .
CYND6043I: J2SE Main Class . . . . . . .
CYND6044I: J2SE Main Class, for example,
com.mycompany.Main . . . . . . . . .
CYND6045I: JMX Server Embedded . . . . .
CYND6046I: Remote Connection Parameters
CYND6047I: Java Argument Macro . . . . .
CYND6048I: Name of the Java Argument Macro
to be replaced . . . . . . . . . . . .
CYND6051I: Script Path . . . . . . . . .
CYND6051I: OS Info MBean was registered,
object name: objectName . . . . . . . . .
CYND6052I: Script Path . . . . . . . . .
CYND6053I: JVM Arguments . . . . . . .
CYND6054I: JVM Arguments . . . . . . .
CYND6055I: Program Arguments. . . . . .
CYND6056I: Program Arguments. . . . . .
CYND6057I: Use JDK as 64 bit? . . . . . .
CYND6058I: Use JDK as 64 bit? . . . . . .
CYND6059I: Use JDK as 64 bit? . . . . . .
CYND7001E: Error while creating a silent
installation file {0}
. . . . . . . . . .
CYND7001I: ITCAM Data Collector for Oracle
Application Server 9.0.3 / 10.1.2 . . . . . .
CYND7002E: Error during installation {0} . . .
CYND7002I: DC for Oracle Application Server
CYND7003E: Error while the migration tool was
backing up the home directory {0} . . . . .
CYND7003I: Oracle Application Server Home
CYND7004E: ISDataBase Access error {0} . . .
CYND7004I: Oracle Application Server Home
Directory. For example C:/OraHome_1. . . .
CYND7005I: Oracle Application Server Type . .
CYND7006E: Error while Loading properties {0}
481
482
482
482
482
482
482
482
483
483
483
483
483
483
483
483
483
483
483
483
483
483
484
484
484
484
484
484
CYND7006I: Oracle Application Server Type . .
CYND7007E: Error during migration {0} . . .
CYND7008E: Wrong path to product: {0} . . .
CYND7008I: Oracle Application Server 9.0.3 . .
CYND7009I: Oracle Application Server 10.1.2
CYND7010I: Select the Oracle Application
Server version number . . . . . . . . .
CYND7010W: An error occurred while deleting
the temporary file. . . . . . . . . . .
CYND7011I: Java Home . . . . . . . . .
CYND7012E: The CERT_PATH variable was not
found . . . . . . . . . . . . . . .
CYND7012I: Java home directory name . . .
CYND7013E: An error occurred while
uninstalling the Visualization Engine: {0} {1} . .
CYND7013I: Managing Server's AM Home . .
CYND7014E: CYANEA_HOME_OS variable was
not found in setenv.sh file . . . . . . . .
CYND7014I: Managing Server AM home
directory . . . . . . . . . . . . . .
CYND7015E: Cannot read {0} . . . . . . .
CYND7015I: Managing Server Kernel Host
Name . . . . . . . . . . . . . . .
CYND7016E: Cannot write to file {0} . . . .
CYND7016I: The Managing Server kernel host
name or IP address . . . . . . . . . .
CYND7017I: Managing Server kernel Codebase
Port . . . . . . . . . . . . . . .
CYND7018I: The Managing Server kernel
codebase port number . . . . . . . . .
CYND7019E: Certificates data or Certificate path
is not correct . . . . . . . . . . . .
CYND7019I: Managing Server kernel RFS Port
CYND7020I: The Managing Server kernel rfs
port number. . . . . . . . . . . . .
CYND7021E: Variable in ve.properties is not
correct: {0} . . . . . . . . . . . . .
CYND7023E: An error occurred while getting
WebSphere servers topology data: topology data
is empty. Script output: {0} . . . . . . . .
CYND7024E: File not found: {0} . . . . . .
CYND7026E: An exception occurred while
getting DB port and server data from variable:
{0} . . . . . . . . . . . . . . . .
CYND7027E: Database type cannot be
recognized. Error in setenv.sh file data.
. . .
CYND7029I: Oracle Application Server Instance
Names . . . . . . . . . . . . . .
CYND7031E: An error occurred while setting in
IS database: . . . . . . . . . . . . .
CYND7030I: The list of Oracle Application
Server instance names . . . . . . . . .
CYND7031I: Oracle Application Server Process
Management XML. . . . . . . . . . .
CYND7032I: Oracle Application Server startup
script will normally be opmn.exe/sh. . . . .
CYND7033E: An error occurred while restoring
subfolders . . . . . . . . . . . . .
CYND7034E: Updating DB failed with exit code
{0} . . . . . . . . . . . . . . . .
Contents
484
485
485
485
485
485
485
485
485
485
486
486
486
486
486
486
486
487
487
487
487
487
487
487
487
487
488
488
488
488
488
488
489
489
489
xliii
CYND7035E: An error occurred while executing:
{0}. Error: {1} . . . . . . . . . . . .
CYND7035I: TEMA Host Name . . . . . .
CYND7036E: The error occurred while
uninstalling the Visualization Engine: {0} . . .
CYND7036I: TEMA host name can be found in
itcamdc/etc/kwjdc.properties.. . . . . . .
CYND7037E: Incorrect Managing Server host
name: {0}. A fully qualified host name should be
provided. . . . . . . . . . . . . .
CYND7037I: TEMA Port Number . . . . .
CYND7038E: WAS_home variable is not defined
CYND7038I: TEMA port number can be found
in itcamdc/etc/kwjdc.properties. . . . . . .
CYND7039E: The error occurred while running
the script for uninstalling the Visualization
Engine. {0} {1} . . . . . . . . . . . .
CYND7039I: JVM GC Log . . . . . . . .
CYND7040E: An error occurred while getting
profiles . . . . . . . . . . . . . .
CYND7040I: JVM GC log is used to obtain java
GC log. . . . . . . . . . . . . . .
CYND7041E: Variable app.install.path is not
defined or could not read the file . . . . .
CYND7042E: Not WebSphere 6, profile not foun
CYND7045E: An error occurred while getting
the profile home dir: the profile name is not
defined . . . . . . . . . . . . . .
CYND7047I: Starting installation ... . . . . .
CYND7048E: An error occurred while getting
WAS version data. Error code: {0} . . . . .
CYND7056E: Installation file not found: {0} . .
CYND7057E: Migration failed: {0} . . . . .
CYND7059E: The path to the product is empty.
CYND7060E: Unsuccessful exit code . . . .
CYND7060I: Enter Oracle Server Information
and Java Home. Oracle Application Server
Home is the installation directory of Oracle( e.g.
C:/OraHome_1 ). Oracle Server Version is the
major version of Oracle server. Java Home is the
JDK installation directory. JVM GC Log is the gc
log file of JVM. For Oracle10g it can be specified
freely; for Oracle9i, it should be the log
file(under $OracleHome/opmn/logs) of the OC4J
instance to be configured. . . . . . . . .
CYND7061E: The directory '{0}' is in use . . .
CYND7061I: Select an oracle application server
instance to configure/unconfigure. . . . . .
CYND7062I: Install DC for 64bit JVM . . . .
CYND7062I: Directory is in use or does not exist
CYND7063I: Install DC for 64bit JVM . . . .
CYND7063E: Aborted by user
. . . . . .
CYND7064I: Starting migration. . . . . . .
CYND7064I: Oracle Server Version. . . . . .
CYND7065I: Generating silent file . . . . .
CYND7066I: Uninstalling Visual Engine . . .
CYND7069I: Removing backup directory . . .
CYND7070I: Executing script to update DB: {0}
CYND7071I: Migration successfully finished . .
CYND7072I: Folders successfully restored
. .
CYND7073I: DB update not selected . . . .
xliv
489
489
489
490
490
490
490
490
490
491
491
491
491
491
491
492
492
492
492
492
492
493
493
493
493
493
493
493
493
493
494
494
494
494
494
494
494
CYND7074I: WAS version = 5, do not uninstall
the Visualization Engine . . . . . . . .
CYND7077I: An error occurred while executing:
{0}. Arguments: {1} . . . . . . . . . .
CYND7079I: An error occurred: KEYSTR_LOC
variable not defined . . . . . . . . . .
CYND7080I: The file deleted successfully {0}
CYND7081W: The file deletion failed {0} . . .
CYND7082I: The folders backed up successfully.
CYND7083I: The command executed
successfully. . . . . . . . . . . . . .
CYND7084I: The Visualization Engine
uninstalled successfully . . . . . . . . .
CYND7086I: Backup directory name: {0} . . .
CYND7115I: Execute the command: {0}
. . .
CYND7116I: Command Done . . . . . . .
CYND7120I: Timeout occurred while executing
the process: {0}
. . . . . . . . . . .
CYND7124I: Starting migration of server: {0}
CYND7126I: Server was migrated: {0} . . . .
CYND7137I: Selected profile: {0}, profile home:
{1} . . . . . . . . . . . . . . . .
CYND7138I: Visualization Engine installation
not selected . . . . . . . . . . . . .
CYND7140I: Backing up folders to: {0} . . . .
CYND7141I: Uninstalling the Visualization
Engine: WAS version == 6 . . . . . . . .
CYND7142I: Deleting . . . . . . . . .
CYND7145I: Copying keys and certificates files
to standard install location... . . . . . . .
CYND7148I: Installation finished with exit code:
{0} . . . . . . . . . . . . . . . .
CYND7157I: Setting +x mode to db2update.sh:
{0} . . . . . . . . . . . . . . . .
CYND7159I: Upgrading DB finished with exit
code {0} . . . . . . . . . . . . . .
CYND7161I: Copying file {0} . . . . . . .
CYND7163I: Executing command: {0} . . . .
CYNOAS Messages: Oracle. . . . . . . . .
CYNOAS001I: oc4j.jar does not exist. . . . .
CYNOAS002I: opmn.xml does not exist. . . .
CYNOAS003I: server.xml does not exist for the
selected server instance.
. . . . . . . .
CYNOAS004I: The server version is not correct.
CYNOAS005I: The oracle instance has already
been configured. . . . . . . . . . . .
CYNOAS006I: The oracle instance has not been
configured yet.
. . . . . . . . . . .
CYNOAS007I: The directory of TEMA log file
not exists . . . . . . . . . . . . . .
CYNWLC Messages: JBoss . . . . . . . . .
CYNWLC001D: Cannot connect to the JBoss
server. Check your environment and server
settings. . . . . . . . . . . . . . .
CYNWLC002D: Incorrect UserID/Password.
CYNWLC003D: Cannot connect to the JBoss
server. Check the host and port. . . . . . .
CYNWLC004D: The directory of redirect file
does not exist. Check the directory. . . . . .
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
494
494
494
494
494
494
494
494
494
494
494
494
494
494
494
495
495
495
495
495
495
495
495
495
495
495
495
495
495
495
496
496
496
496
496
496
496
496
CYNWLC005D: This is not a valid JBoss server
directory. Check the directory that was
specified.
. . . . . . . . . . . . .
CYNWLC006D: The UserID/Password of the
JBoss server is not correct. Check the parameters
that were specified. . . . . . . . . . .
CYNWLC007D: Cannot connect to the JBoss
server. Make sure that the JBoss is running or
check whether the Server Host/Port specified
are correct. . . . . . . . . . . . . .
CYNWLC008D: The JBoss version that you
selected is not correct! . . . . . . . . .
CYNWLC009D: The Server instance you
selected is not configured! . . . . . . . .
CYNWLC010D: The Server instance you
selected has already been configured by another
DC!\n Please unconfigure that DC first. . . .
CYNWLC011D: The Startup Script you inputed
is not the right script that start up the running
JBoss!\n Please correct the Startup Script you
Inputed. . . . . . . . . . . . . . .
CYNWLC012D: JAVA HOME that the running
JBoss Server used is not the one you inputed!\n
Please correct the JAVA HOME you inputed. . .
CYNWLC013D: The Server Home you inputed
is not the Server Home of running JBoss!\n
Please correct the Server Home you inputed. . .
CYNWLC014D: Need RTT Fixpack for the RTT
you installed to this JBoss server!. . . . . .
CYNWLC015D: The path of GC Log does not
exist!\n Please correct the GC log you inputed. .
CYNPE Messages:Request Aggregator . . . . .
CYNPE0001I: Generic Probe Engine Runtime
Environment is now initialized. . . . . . .
CYNPE0002I: Generic Probe Engine initialized
startup class StartupClass. . . . . . . . .
CYNPE0003I: Generic Probe Engine shutdown
initiated. . . . . . . . . . . . . . .
CYNPE0004I: Generic Probe Engine initialized
runtime component RuntimeComponent
class.RuntimeClass. . . . . . . . . . . .
CYNPE0005I: MBean Manager has been
initialized. . . . . . . . . . . . . .
CYNPE0006I: MBean Manager registered MBean
ObjectName. . . . . . . . . . . . . .
CYNPE0007I: MBean Manager loaded the
registration engine RegistrationEngine. . . . .
CYNPE0008E: XML parsing error occurred:
errorType parsing file fileName. . . . . . . .
CYNPE0009E: Aspect definition aspectName is
defined with abstract pointcut pointcutName but
has no concretizePointcut definition.. . . . .
CYNPE0010I: MBean manager created MBean
server with class MBeanServerClass and default
domain name domainName. . . . . . . . .
CYNPE0011E: MBean manager was unable to
create MBean server with class MBeanServerClass
and default domain name domainName.. . . .
CYNX Messages: Installation . . . . . . . .
496
497
497
497
497
497
497
497
498
498
498
498
499
499
499
499
499
499
499
499
499
499
499
499
CYNX0001E: There were usage errors, where a
number of arguments were incorrect for the
following: java UserInputsFilePath,
ConfigurationTemplatesPath, and
DestinationPath. . . . . . . . . . . .
CYNX0002E: Configuration template was not
found. The concrete configuration XML file
could not be created. . . . . . . . . . .
CYNX0003E: A configuration template cannot be
found for the following application server
versions: . The concrete configuration XML file
could not be created. . . . . . . . . . .
CYNX0004E: The concrete configuration XML
file could not be generated due to missing
values in the dcInputs.txt file. . . . . . . .
CYNX0005I: The concrete configuration file was
generated successfully. . . . . . . . . .
CYNX0006E: The value for the variable was not
found in the userInputs file. This variable was
not replaced in file . . . . . . . . . . .
CYNX0007E: File cannot be modified
successfully and copied to the file . . . . . .
CYNX0008E: The system could not load the
property file successfully. . . . . . . . .
CYNX0009E: One or more -Xrun JVM
arguments were found for the server .
Configuration is skipped for server . . . . .
CYNX0010E: The system failed to get the
backup of the current application server
configuration. . . . . . . . . . . . .
CYNX0011E: The system failed to set . . . . .
CYNX0012E: The system failed to save and
commit the newly applied configuration. . . .
CYNX0013E: The system failed to create the
post-installation instruction file for the
WebLogic unmanaged application server. . . .
499
500
500
500
500
501
501
501
501
502
502
502
502
Chapter 4. System Messages for
ITCAM Agent for HTTP Servers. . . . 503
KHT messages . . . . . . . . . . . . .
KHTC0000I: Configurator messages . . . . .
KHTC0001I: Ok . . . . . . . . . . .
KHTC0002E: Error: There are no -C options. It is
necessary to specify a home path. . . . . .
KHTC0003E: Unexpected exception {0}. Refer to
trace log. . . . . . . . . . . . . . .
KHTC0006E: Error: Unable to determine version
of Apache runtime specified by home path {0} .
KHTC0008W: Warning: {0} is already
configured. . . . . . . . . . . . . .
KHTC0010I: Info: {0} was configured. . . . .
KHTC0011E: Error: {0} file was not found. . . .
KHTC0012W: Warning: {0} is not configured.
KHTC0013I: Info: {0} was unconfigured. . . .
KHTC0015E: Error: 64-bit Apache module for
Windows is not provided. . . . . . . . .
KHTC0016E: Error: Unable to find required
module: {0} . . . . . . . . . . . . .
KHTA0000I: Composite Application Manager
monitoring agent startup complete. . . . . .
Contents
503
503
503
503
503
503
504
504
504
504
504
504
504
505
xlv
KHTH0001I: Apache WebServer {0} was
successful. . . . . . . . . . . . . .
KHTH0002E: Apache WebServer {0} failed with
error code {1}. . . . . . . . . . . . .
KHTH0003E: Unexpected exception: {0}, refer to
trace log. . . . . . . . . . . . . . .
KHTS0011W: SNMP info for Sun Web Server
isn't available, check Sun Web Server SNMP
agent configuration. . . . . . . . . . .
505
505
505
Search the Internet . . . . . . . . . .
Obtaining fixes . . . . . . . . . . . . .
Receiving weekly support updates . . . . . .
Contacting IBM Software Support . . . . . .
Determine the business impact of your problem
Describe your problem and gather background
information . . . . . . . . . . . . .
Submit your problem to IBM Software Support
510
511
511
512
512
513
513
505
Index . . . . . . . . . . . . . . . 515
Appendix A. Accessibility . . . . . . 507
Trademarks . . . . . . . . . . . . 517
Appendix B. Support information . . . 509
Searching knowledge bases . . . . .
Finding Release Notes . . . . .
Tivoli Support Technical Exchange .
Search the information center on your
system or network. . . . . . .
xlvi
. .
. .
. .
local
. .
.
.
.
. 509
. 509
. 510
.
. 510
Notices . . . . . . . . . . . . . . 519
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Tables
1.
2.
3.
ITCAM Agent for WebSphere Applications Data
Collector log path . . . . . . . . . . . 8
ITCAM Agent for J2EE Data Collector log path 9
Path to cynlogging.properties and
cyn-cclog.properties . . . . . . . . . 9
© Copyright IBM Corp. 2007, 2010
4.
5.
Available column names for LogViewer
queries . . . . . . . . . . . . . . 13
Severity Level . . . . . . . . . . . 513
xlvii
xlviii
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
About this guide
This guide provides troubleshooting information for installing, customizing,
starting, and maintaining the 4 main components that make upIBM® Tivoli®
Composite Application Manager for Application Diagnostics (ITCAM for
Application Diagnostics). These components are:
v Agent for WebSphere® applications
v Agent for J2EE
v Agent for HTTP Servers
v Managing Server
The 3 agent components listed above are also components of ITCAM for
Applications Version 6.2.3. However, if you are using ITCAM for Applications, the
Managing Server (deep dive) functionality is not available. In this case, ignore all
references to this functionality in this document.
Intended audience
This guide is for administrators or advanced users wanting to troubleshoot ITCAM
for Application Diagnostics. The guide assumes that readers are familiar with
maintaining operating systems, administering Web servers, maintaining databases,
and general information technology procedures. Specifically, readers of this guide
must have some knowledge of the following topics:
v Web application servers, such as IBM WebSphere
v IBM Tivoli Monitoring software
Operating systems on which you intend to install product components
Web servers, such as IBM HTTP Server and Apache HTTP Server
WebSphere Application Server Community Edition
Web application servers, such as WebLogic, NetWeaver, JBoss, Oracle, and
Tomcat, and J2SE applications
v Internet protocols such as HTTP, HTTPS, TCP/IP, Secure Sockets Layer (SSL),
and Transport Layer Security (TLS)
v
v
v
v
v Digital certificates for secure communication
Publications
This section lists publications in the product library and related documents. It also
describes how to access Tivoli publications online and how to order Tivoli
publications.
ITCAM for Application Diagnostics library
The following publications provide additional information about ITCAM for
Application Diagnostics. They are included in the ITCAM for Application
Diagnostics library available at http://publib.boulder.ibm.com/infocenter/
tivihelp/v24r1/topic/com.ibm.itcamfad.doc_7101/ic-homepage.html.
v IBM Tivoli Composite Application Manager for Application Diagnostics: Prerequisites
Provides the hardware and software requirements for installing ITCAM for
Application Diagnostics components.
© Copyright IBM Corp. 2007, 2010
xlix
v IBM Tivoli Composite Application Manager for Application Diagnostics: User's Guide
Provides the user overview, user scenarios, and Helps for every ITCAM for
Application Diagnostics component.
v IBM Tivoli Composite Application Manager for Application Diagnostics: Planning an
Installation
Provides the user with a first reference point for a new ITCAM for Application
Diagnostics installation or upgrade.
ITCAM Agent for WebSphere Applications Installation and Configuration
Guides:
– IBM Tivoli Composite Application Manager: Agent for WebSphere Applications
Installation and Configuration Guide
– IBM Tivoli Composite Application Manager: Agent for WebSphere Applications
Installation and Configuration Guide for z/OS
– IBM Tivoli Composite Application Manager: Agent for WebSphere Applications Data
Collector Installation and Configuration Guide for IBM i
Provide installation instructions for setting up and configuring ITCAM Agent for
WebSphere Applications on distributed, z/OS®, and IBM i systems.
v ITCAM Agent for J2EE Applications Installation and Configuration Guides:
v
– IBM Tivoli Composite Application Manager: Agent for J2EE Data Collector
Installation and Configuration Guide
– IBM Tivoli Composite Application Manager: Agent for J2EE Monitoring Agent
Installation and Configuration Guide
Provide installation instructions for setting up and configuring ITCAM Agent for
J2EE.
v IBM Tivoli Composite Application Manager: Agent for HTTP Servers Installation and
Configuration Guide
Provides installation instructions for setting up and configuring ITCAM Agent
for HTTP Servers.
v IBM Tivoli Composite Application Manager for Application Diagnostics Managing
Server Installation Guide
Provides installation instructions for setting up and configuring ITCAM for
Application Diagnostics Managing Server.
v IBM Tivoli Composite Application Manager for Application Diagnostics:
Troubleshooting Guide
Provides instructions on problem determination and troubleshooting for ITCAM
for Application Diagnostics.
v IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging
Guide
Provides information about system messages received when installing and using
ITCAM for Application Diagnostics.
Related publications
The following documentation also provides useful information:
v WebSphere Application Server:
Information about WebSphere Application Server is provided on the following
Web site:
http://www-306.ibm.com/software/webservers/appserv/was/library
v IBM DB2®:
Information about IBM DB2 is provided on the following Web site:
l
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
http://www-306.ibm.com/software/data/sw-library/
v IBM Tivoli Enterprise Console®:
Information about IBM Tivoli Enterprise Console is provided on the following
Web site:
http://submit.boulder.ibm.com/tividd/td/EnterpriseConsole3.9.html
v IBM Tivoli Data Warehouse:
Information about IBM Tivoli Data Warehouse is provided on the following Web
site:
http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp?toc=/
com.ibm.tivoli.tdwi.doc/toc.xml
v IBM Tivoli Change and Configuration Management Database:
Information about IBM Tivoli Change and Configuration Management Database
is provided on the following Web site:
http://publib.boulder.ibm.com/infocenter/tivihelp/v10r1/index.jsp?toc=/
com.ibm.ccmdb.doc/ccmdb_ic.xml
v IBM Support Assistant:
Information about IBM Support Assistant is provided on the following Web site:
http://www-306.ibm.com/software/support/isa/index.html?rcss=rtlrre
Accessing terminology online
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://publib.boulder.ibm.com/tividd/glossary/tivoliglossarymst.htm
The IBM Terminology Web site consolidates the terminology from IBM product
libraries in one convenient location. You can access the Terminology Web site at the
following Web address:
http://www.ibm.com/software/globalization/terminology
Accessing publications online
The documentation CD contains the publications that are in the ITCAM for
Application Diagnostics library. The format of the publications is PDF, HTML, or
both.
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 documentation center at the following Web address:
https://www.ibm.com/developerworks/wikis/display/tivolidoccentral/Home
Access the Tivoli Information Center for ITCAM for Application Diagnostics at the
following Web address:
http://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/topic/
com.ibm.itcamfad.doc_7101/ic-homepage.html
Note: If you print PDF documents on other than letter-sized paper, set the option
in the File > Print window that allows Adobe Reader to print letter-sized pages on
your local paper.
About this guide
li
All IBM Tivoli product documentation can be accessed through the Tivoli
Documentation Central Wiki page at http://www.ibm.com/developerworks/
wikis/display/tivolidoccentral/Home.
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, contact your software account representative to order Tivoli
publications. To locate the telephone number of your local representative, perform
the following steps:
1. Go to the following Web site:
http://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/
pbi.cgi
2. Select your country from the list and click Go.
3. Click About this site in the main panel to see an information page that
includes the telephone number of your local representative.
Accessibility
Accessibility features help users with a physical disability, such as restricted
mobility or limited vision, to use software products successfully. With this product,
you can use assistive technologies to hear and navigate the interface. You can also
use the keyboard instead of the mouse to operate all features of the graphical user
interface.
For additional information, see Appendix A, “Accessibility,” on page 507.
Tivoli technical training
For Tivoli technical training information, refer to the following IBM Tivoli
Education Web site:
http://www.ibm.com/software/tivoli/education/
Conventions used in this guide
This guide uses several conventions for special terms and actions, operating
system-dependent commands and paths, and margin graphics.
Typeface conventions
This guide uses the following typeface conventions:
Bold
v Lowercase commands and mixed case commands that are otherwise
difficult to distinguish from surrounding text
lii
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
v Interface controls (check boxes, push buttons, radio buttons, spin
buttons, fields, folders, icons, list boxes, items inside list boxes,
multicolumn lists, containers, menu choices, menu names, tabs, property
sheets), labels (such as Tip:, and Operating system considerations:)
v Keywords and parameters in text
Italic
v Citations (examples: titles of publications, diskettes, and CDs
v Words defined in text (example: a nonswitched line is called a
point-to-point line)
v Emphasis of words and letters (words as words example: "Use the word
that to introduce a restrictive clause."; letters as letters example: "The
LUN address must start with the letter L.")
v New terms in text (except in a definition list): a view is a frame in a
workspace that contains data.
v Variables and values you must provide: ... where myname represents....
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
Variables for directories
This guide refers to the following variables:
ITM_home
The top level directory for installation of IBM Tivoli Monitoring
components.
ITCAM_home
The top level directory for installation of IBM Tivoli Composite Application
Monitoring components.
DC_home and MS_home
The directory where the Data Collector or Managing Server are installed.
About this guide
liii
liv
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
What's new in this publication
ITCAM Agent for WebSphere Applications
This publication contains information that applies to version 7.1.0.2 of IBM Tivoli
Composite Application Manager for Application Diagnostics. You should have the
following maintenance of the product installed:
v ITCAM Agent for WebSphere Applications 7.1.0.2
ITCAM Agent for J2EE
This publication contains information that applies to the 6.2.0.4 version of the
product:
v Data Collector Fix Pack 4
v J2EE Monitoring Agent Fix Pack 4
ITCAM Agent for HTTP Servers
v ITCAM Agent for HTTP Servers 7.1.0.2
You can use the auto-learning thresholds and benchmark performance for a new
application (or changed environment) and to understand where thresholds should
be established. In conjunction with this offering, best practices related to logical
navigation views and correlation of situations for automation of problem
identification can be found in the Open Process Automation Library (OPAL). For
more information, see the following Web site: http://catalog.lotus.com/wps/
portal/tcam
© Copyright IBM Corp. 2007, 2010
lv
lvi
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Chapter 1. Log files, tracing, and utilities
Log files contain useful information for analyzing and troubleshooting any issue
that may occur in the system. You can also enable tracing in order to log additional
details. It is suggested that you perform tracing and capture the log files before
contacting IBM support for assistance.
ITCAM for Application Diagnostics includes several tools for generating and
managing log files. It also provides an Environmental Checking Utility (ECU). You
can use this utility to check that prerequisite packages are installed correctly prior
to installation
Log files and tracing for the Tivoli Enterprise Monitoring Agent
The Tivoli Enterprise Monitoring Agent is a component of ITCAM Agent for
WebSphere Applications, ITCAM Agent for J2EE, and ITCAM Agent for HTTP
Servers.
Gather Script
The Gather Script is a script that collects system information such as CPU and
memory data, network status, registry and environment variables. It also collects
specific information on the product, such as configuration settings, log files and
maintenance level. It compresses all the collected information into a single file.
When you contact IBM support for assistance, the support engineer will ask you to
upload the file for further analysis.
ITCAM Agent for WebSphere Applications
For ITCAM Agent for WebSphere Applications, the name of the Tivoli Enterprise
Monitoring Agent gather script is:
v on Windows, ITM_home\TMAITM6\kyncollect.cmd
v on Linux, UNIX systems, and z/OS, ITM_home/ITM_BINARCH/yn/bin/
kyncollect.sh
The script takes no parameters.
The output file will be located in the following directory:
v on Windows, %TEMP%\KYN
v on Linux, UNIX systems, and z/OS, ITM_home/tmp/kyn
ITCAM Agent for J2EE
For ITCAM Agent for J2EE, the name of the Tivoli Enterprise Monitoring Agent
gather script is:
v on Windows, ITM_home\TMAITM6\kyjcollect.cmd
v on Linux, UNIX systems, and z/OS, ITM_home/ITM_BINARCH/yn/bin/
kyjcollect.sh
The script takes no parameters.
The output file will be located in the following directory:
© Copyright IBM Corp. 2007, 2010
1
v on Windows, %TEMP%\KYJ
v on Linux and UNIX systems, ITM_home/tmp/kyj
ITCAM Agent for HTTP Servers
For ITCAM Agent for HTTP Servers, the name of the Tivoli Enterprise Monitoring
Agent gather script is:
v on Windows, ITM_home\TMAITM6\khtcollect.cmd
v on Linux, UNIX systems, and z/OS, ITM_home/ITM_BINARCH/ht/bin/
khtcollect.sh
The script takes no parameters.
The output file will be located in the following directory:
v on Windows, %TEMP%\KHT
v on Linux and UNIX systems, ITM_home/tmp/kht
Tracing within the Tivoli Enterprise Monitoring Agent
For all the agents, tracing within the Tivoli Enterprise Monitoring Agent is
controlled by setting the KBB_RAS1 environment variable, using the format
KBB_RAS1=ERROR (UNIT:<unitname> <trace type>), as per the following examples:
v KBB_RAS1=ERROR (UNIT:kyn ALL) (UNIT:kwj all)
Writes all error messages.
Writes all trace messages for source files beginning with "kyn" or "kwj"
Tip: Use "kyn" for ITCAM Agent for WebSphere Applications, "kyj" for ITCAM
Agent for J2EE, and "kht" for ITCAM Agent for HTTP Servers.
v KBB_RAS1=ERROR (UNIT:kwj INPUT OUTPUT STATE)
Writes all error messages.
Writes INPUT, OUTPUT, and STATE trace messages for source files beginning
with 'kwj'.
v KBB_RAS1=ERROR
Writes trace messages for all errors.
Useful traces
Generally, requests for tracing and interpretation of traces must only be done by
those who have intimate knowledge of the code.
v KBB_RAS1=UNIT:kwjira FLOW STATE
Traces Monitoring Agent activity on the IBM Tivoli Monitoring framework API
boundary.
v KBB_RAS1=ERROR (UNIT:KWJJ FLOW STATE)
Traces the native Monitoring Agent interface flow with the Java sub-agent.
Where to specify tracing parameters
Set tracing parameters in the following locations, depending on the agent and the
OS:
v For ITCAM Agent for WebSphere Applications:
– On Windows: ITM_home\TMAITM6\KYNENV file
– On Linux and UNIX systems: /Install_home/config/yn.ini file
– On z/OS: KYNENV member of RKANPAR data set
v For ITCAM Agent for J2EE:
2
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
– On Windows: ITM_home\TMAITM6\KYJENV file
– On Linux and UNIX systems: /ITM_home/config/yj.ini file
v For ITCAM Agent for HTTP Servers:
– On Windows: ITM_home\TMAITM6\KHTENV file
– On Linux and UNIX systems: /ITM_home/config/ht.ini file
You can also set these parameters using the GUI. This GUI is also available in
UNIX systems using the X Window System.
Note:
1. When troubleshooting the monitoring agent, enable tracing for the Data
Collector code that communicates with the monitoring agent. See “Setting the
logging and tracing levels” on page 7
2. When troubleshooting Application Summary workspaces, enable tracing for
the ITCAM for Application Diagnostics support code in the Tivoli Enterprise
Portal, as this code is used to create the green .yellow/red "lights" in the
workspaces. See “Tracing and logging within the Tivoli Enterprise Portal
(Summary Workspaces)” on page 16
Tivoli Enterprise Monitoring Agent log files
ITCAM Agent for WebSphere Applications
Location of the logs in Windows:
v ITM_home\logs\COMPUTER_NAME_yn_*.log [contains Monitoring Agent native code
trace messages]
v ITM_home\logs\kyn-TEMA-trace.log [contains Monitoring Agent java code trace
messages]
v ITM_home\logs\kyn-TEMA-msg.log [contains Monitoring Agent log messages]
v ITM_home\logs\KYN.Primary.*.*JVM.log [contains Monitoring Agent JVM
messages]
v ITM_home\TMAITM6\logs\itcamfwasras1.log [contains Monitoring Agent
configuration messages]
Location of the log files in UNIX/Linux:
v ITM_home/logs/COMPUTER_NAME_yn_*.log
v ITM_home/logs/itm_config.log
v ITM_home/logs/itm_config.trc
v ITM_home/logs/KYN.Primary.*.*JVM.log
Location of the log files in z/OS:
v ITM_home/logs/COMPUTER_NAME_yn_*.log
v ITM_home/logs/kyn-TEMA-trace.log
v ITM_home/logs/kyn-TEMA-msg.log
v ITM_home/logs/KYN.Primary.*.*JVM.log
The location of the native code trace log files can be changed using the Manage
Tivoli Monitoring Services utility (in the right click menu for the agent, select
Advanced > Edit Trace Parms...); it can not be changed on z/OS. To set the
location of other log files, use the following configuration files:
v Windows - ITM_home\TMAITM6\kynjlog.properties
v UNIX/Linux - ITM_home/arch/yn/config/kynjlog.properties
Chapter 1. Log files, tracing, and utilities
3
v z/OS - ITM_home/yn/config/kynjlog.properties
Attention: The configuration files for the logs must not be changed without the
prior consent of IBM Tivoli Support Team.
ITCAM Agent for J2EE
Location of the logs in Windows:
v ITM_home\logs\COMPUTER_NAME_yj_*.log [contains Monitoring Agent native code
trace messages]
v ITM_home\logs\kyj-TEMA-trace.log [contains Monitoring Agent java code trace
messages]
v ITM_home\logs\kyj-TEMA-msg.log [contains Monitoring Agent log messages]
v ITM_home\logs\KYJ.Primary.*.*JVM.log [contains Monitoring Agent JVM
messages]
Location of the log files in UNIX/Linux:
v ITM_home/logs/COMPUTER_NAME_yj_*.log
v ITM_home/arch/logs/kyj-tema-trace.log
v ITM_home/arch/logs/kyj-tema-msg.log
v ITM_home/logs/KYJ.Primary.*.*JVM.log
The location of the native code trace log files can be changed using the Manage
Tivoli Monitoring Services utility (in the right click menu for the agent, select
Advanced > Edit Trace Parms...). To set the location of other log files, use the
following configuration files:
v Windows - ITM_home\TMAITM6\kyjjlog.properties
v UNIX/Linux - ITM_home/arch/yj/config/kyjjlog.properties
Attention: The configuration files for the logs must not be changed without the
prior consent of IBM Tivoli Support Team.
ITCAM Agent for HTTP Servers
Location of the logs in Windows:
v ITM_home\logs\COMPUTER_NAME_ht_*.log [contains native code trace messages]
v ITM_home\logs\kht-TEMA-trace.log [contains java code trace messages]
v ITM_home\logs\kht-TEMA-msg.log [contains Agent log messages]
v ITM_home\logs\KHT.Primary.*.*JVM.log [contains Agent JVM messages]
Location of the log files in UNIX/Linux:
v
v
v
v
v
ITM_home/logs/COMPUTER_NAME_ht_*.log
ITM_home/arch/logs/kht-tema-trace.log
ITM_home/arch/logs/kht-tema-msg.log
ITM_home/logs/itm_config.log
ITM_home/logs/itm_config.trc
v ITM_home/logs/KHT.Primary.*.*JVM.log
The location of the native code trace log files can be changed using the Manage
Tivoli Monitoring Services utility (in the right click menu for the agent, select
Advanced > Edit Trace Parms...). To set the location of other log files, use the
following configuration files:
v Windows - ITM_home\TMAITM6\khtjlog.properties
4
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
v UNIX/Linux - ITM_home/arch/ht/config/khtjlog.properties
Attention: The configuration files for the logs must not be changed without the
prior consent of IBM Tivoli Support Team.
Plug-in for IBM Support Assistant (ISA)
ITCAM for Application Diagnostics plug-in for IBM Support Assistant (ISA) is a
plug-in available for download in ISA. It is a GUI-based utility for collecting log
files and system information. You can submit a service request through ISA with
the file generated by the plug-in. For instructions on obtaining and installing the
ISA software, please refer to “Downloading ISA” on page 21 and “Installing ISA”
on page 21.
Downloading the plug-in from IBM Support Assistant (ISA)
To download the ITCAM for Application Diagnostics plug-in for ISA, perform the
following steps:
1. Launch IBM Support Assistant
2. Click Updater on the main page
3. You will see a list of installed plug-ins. Click New Plug-ins
Note: If you are using ISA version 3.0.0.1, click New Products and Tools
4. You will see a list of plug-ins available for download. Click to expand Tivoli
tree
5. Check the box next to IBM Tivoli Composite Application Manager for
Application Diagnostics 7.1
6. Click Install button
7. Click I agree button to accept the license agreement
8. The download will start and the installation will also start after the download
is complete. When the installation finishes, you will be asked for restarting the
ISA, click OK button to restart it
Using the plug-in to collect log files and system information
To use the ITCAM for Application Diagnostics plug-in to collect log files and
system information, perform the following steps:
1. Launch IBM Support Assistant
2. Click Service on the main page
3. Click Collect Data on the left panel
4. Expand IBM Tivoli Composite Application Manager for Application
Diagnostics 7.1
5. Select ITCAM Data Collector Problem.
6. Click Collect button
7. You will be asked for the location of the data collector installation directory.
Please input the path in the text box provided and click OK to continue
8. The process will start and will collect the system information and log files. It
will display the location of the output file it generates when it finishes
9. You can submit a service request through ISA with the file is being generated
by the plug-in
Chapter 1. Log files, tracing, and utilities
5
Log files and tracing for the Data Collector
The Data Collector is a component of ITCAM Agent for WebSphere Applications
and ITCAM Agent for J2EE.
Important: ITCAM Agent for HTTP Servers does not include a Data Collector.
First Failure Data Capture
First Failure Data Capture (FFDC) uses an in-memory tracing tool that runs
continuously. When an unexpected error occurs, FFDC dumps the trace
information to a log file for use in analyzing the problem. FFDC collects
information that is intended primarily for use by IBM software support
technicians. It runs automatically, you do not need to perform any action to start or
stop it. If you experience conditions requiring you to contact software support,
your support representative can assist you in reading and analyzing the FFDC log.
FFDC does not affect the performance of the product.
For information about receiving assistance from IBM Software Support, see
“Contacting IBM Software Support” on page 512.
You can retrieve FFDC logs from the following default locations:
v For Managing Server, they are:
Microsoft Windows:
C:\Program Files\ibm\tivoli\common\CYN\FFDC
Linux or UNIX systems:
/var/ibm/tivoli/common/CYN/FFDC
OS/400®:
/QIBM/UserData/tivoli/common/CYN/FFDC
v For ITCAM Agent for WebSphere Applications, they are:
Microsoft Windows:
ITM_home\tmaitm6\wasdc\7.1.0.2\logs
Linux or UNIX systems:
ITM_home/component_name/yn/wasdc/7.1.0.2/logs
IBM i:
/QIBM/UserData/tivoli/common/CYN/FFDC
v For ITCAM Agent for J2EE, they are:
Microsoft Windows:
C:\Program Files\ibm\tivoli\common\CYN\FFDC
Linux or UNIX systems:
ITM_home/component_name/yn/wasdc/7.1.0.2/logs
Gather Script
The Gather Script is a script that collects system information such as CPU and
memory data, network status, registry and environment variables. It also collects
specific information on the product such as configuration settings, log files and
maintenance level. It compresses all the collected information into a single file.
When contacting IBM support for assistance, you will be asked to upload the file
for further analysis.
6
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
For information about receiving assistance from IBM Software Support, see
“Contacting IBM Software Support” on page 512.
ITCAM Agent for WebSphere Applications
The Data Collector Gather Script for ITCAM Agent for WebSphere Applications is:
v Windows: ITM_home\TMAITM6\bin\cyn_collector.cmd
v Linux and UNIX systems: ITM_home/arch/yn/bin/cyn_collector.sh
v IBM i: DC_home/itcamdc/bin/cyn_os400_collector.sh
The syntax for running the Gather Script is:
cyn_collector_script_name [[-a] | [-s server]]
where:
-a makes the script collect information from all application servers on the host.
-s makes the script collect information from one application server; server is the
name of the application server.
Important: The -s option is not available on IBM i.
You must specify either -a or -s server
The script will display the name of the resulting *.jar file.
ITCAM Agent for J2EE
The Data Collector Gather Script for ITCAM Agent for J2EE is:
v Windows: DC_home\itcamdc\bin\cyn_collector_J2.cmd
v Linux and UNIX systems: DC_home/itcamdc/bin/cyn_collector_J2.sh
Start the Gather Script without parameters. The name of the created file is
v Windows: DC_home\collect.jar
v Linux and UNIX systems: DC_home/collect.tar.gz
Setting the logging and tracing levels
To change the logging and tracing level for the Data Collector, you need to edit
property files and then restart the Data Collector. Different files are used for native
code and Java code. These settings apply to the Data Collector of both ITCAM
Agent for WebSphere Applications and ITCAM Agent for J2EE.
There are four components in the native code of the Data Collector. They are
Network Agent, Event Agent, Command Agent and Common code. To change the
log levels for these components, modify the file DC_home/runtime/ServerInstance/
cyn-cclog.properties. For example:
logger.dc.trace.listenerNames=handler.file.dc.trace
# dc command agent logger properties
logger.dc.ca.trace.level=INFO
# dc network agent logger properties
logger.dc.na.trace.level=DEBUG_MID
# dc event agent logger properties
logger.dc.ea.trace.level=DEBUG_MIN
# dc common code logger properties
logger.dc.cc.trace.level=INFO
Chapter 1. Log files, tracing, and utilities
7
Important: Restart the Data Collector after making changes to
cyn-cclog.properties.
Attention: On IBM i, the file cyn-cclog.properties is in EBCDIC encoding; when
saving changes, ensure the file is saved in this encoding.
You may specify tracing levels for the Java code in the Data Collector in the
DC_home/runtime/instance/cynlogging.properties file. The following code snippet
from that file indicates where to specify the tracing level for the primary data
collector Java code:
#----------------------------------------------# Data Collector
#----------------------------------------------# MESSAGE LOGGER
CYN.msg.datacollector.level=INFO
CYN.msg.datacollector.logging=true
# TRACE LOGGER
CYN.trc.datacollector.level=INFO
Note: INFO means only errors and informational trace messages will be written.
You may also specify the tracing level for the Data Collector Java code that
communicates with the Tivoli Enterprise Monitoring Agent. Make the following
changes in the same file:
# MESSAGE LOGGER
CYN.msg.temadc.level=INFO
CYN.msg.temadc.logging=true
# TRACE LOGGER
CYN.trc.temadc.level=INFO
CYN.trc.temadc.logging=true
Tracing can be set at more granular levels by setting CYN.trc.partially qualified
class name.level=debug level in the cynlogging.properties properties file. This
property stipulates that for the class beginning with partially qualified class name
tracing will be at the specified level. For example:
v CYN.trc.com.ibm.tivoli.kyn.gccollector=DEBUG_MID
Traces "middle" level of debugging for classes beginning with
"com.ibm.tivoli.kyn.gccollector"
v CYN.trc.com.ibm.tivoli.kyn.requestmanager=DEBUG_MAX
Traces "maximum" level of debugging for classes beginning with
"com.ibm.tivoli.kyn.requestmanager".
Note: The Data Collector must be restarted for changes to take effect.
Data Collector logs
The ITCAM Agent for WebSphere Applications Data Collector logs are, by default,
located in the following directory:
Table 1. ITCAM Agent for WebSphere Applications Data Collector log path
8
Windows
DC_home\logs\hostname.servername\
Linux and UNIX systems
DC_home/logs/hostname.servername/
IBM i
/QIBM/UserData/tivoli/common/CYN/logs
z/OS
config_home/runtime/
appserver_version.node_name.server_name/logs/CYN/logs
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
The ITCAM Agent for J2EE Data Collector logs are, by default, located in the
following directory:
Table 2. ITCAM Agent for J2EE Data Collector log path
Windows
C:\Program Files\ibm\tivoli\common\CYN\logs
Linux and UNIX systems
/var/ibm/tivoli/common/CYN/logs
The log file names are:
v msg-dc-native.log
v msg-dc-ParentLast.log
v trace-dc-bcm.log
v trace-dc-native.log
v trace-dc-ParentLast.log
For both ITCAM Agent for WebSphere Applications and ITCAM Agent for J2EE,
you can modify the log file location by modifying the cynlogging.properties and
cyn-cclog.properties files. Their location is:
Table 3. Path to cynlogging.properties and cyn-cclog.properties
Windows
DC_home\runtime\server_instance\
Linux and UNIX systems,
and IBM i
DC_home/runtime/server_instance/
z/OS
config_home/runtime/server_instance/
Plug-in for IBM Support Assistant (ISA)
ITCAM for Application Diagnostics plug-in for IBM Support Assistant (ISA) is a
plug-in available for download in ISA. It is a GUI-based utility for collecting log
files and system information. You can submit a service request through ISA with
the file generated by the plug-in. For the detailed information on how to download
and use the plug-in, please refer to “Plug-in for IBM Support Assistant (ISA)” on
page 5.
Log files and tracing for the Managing Server
The Managing Server is used for deep dive diagnostics. It communicates with
ITCAM Agent for WebSphere Applications and ITCAM Agent for J2EE.
First Failure Data Capture
First Failure Data Capture (FFDC) uses an in-memory tracing tool that runs
continuously. When an unexpected error occurs, FFDC dumps the trace
information to a log file for use in analyzing the problem. FFDC collects
information that is intended primarily for use by IBM software support
technicians. It runs automatically, you do not need to perform any action to start or
stop it. If you experience conditions requiring you to contact software support,
your support representative can assist you in reading and analyzing the FFDC log.
FFDC does not affect the performance of the product.
For information about receiving assistance from IBM Software Support, see
“Contacting IBM Software Support” on page 512.
You can retrieve FFDC logs for the Managing Server from the following default
locations:
Chapter 1. Log files, tracing, and utilities
9
Microsoft Windows:
C:\Program Files\ibm\tivoli\common\CYN\FFDC
UNIX/Linux:
/var/ibm/tivoli/common/CYN/FFDC
Gather Script
The Gather Script is a script that collects system information such as CPU and
memory data, network status, registry and environment variables. It also collects
specific information on the product such as configuration settings, log files and
maintenance level. It compresses all the collected information into a single file.
When contacting IBM support for assistance, you will be asked to upload the file
for further analysis.
The Managing Server Gather Script is located in MS_HOME/bin/MS_Gather_Data.sh.
It is invoked using the command:
./MS_Gather_Data.sh pmr-number [appserver_home where VE is installed] [SERVER_NAME]
, for example:
./MS_Gather_Data.sh 70023.900.000
On Windows, use the Microsoft Services for Unix shell to start this script.
The result of running the MS gather script is a zipped file, containing the
following:
v
v
v
v
v
Most contents of MS_HOME (bin, etc, logs and scripts)
All logs in the /var directory
Status of all components (text file for each component)
Text file of OS information
List of installed libraries
v server.xml for the specified server
v Netstat output
Changing the log level
The Managing Server supports changing the log level dynamically.
To change the log level of the Managing Server, use the following command in
MS_HOME/bin :
./amctl.sh component [debugmin | debugmax | debugmid | traceoff |
messageoff | error | warn | info]
where component is one of the following:
v kl1: First instance of the Kernel
v kl2: Second instance of the Kernel
v ps1: First instance of the Publish Server
v
v
v
v
v
10
ps2: Second instance of the Publish Server
aa1: First instance of Archive Agent
aa2: Second instance of Archive Agent
md: Message Dispatcher
sam1: First instance of Structured Application Monitor (SAM) Global Publish
Server
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
v pa: Polling Agent
On Windows, use the Microsoft Services for Unix shell to start this script.
Managing Server logs
The Managing Server logs are:
v MS_home/logs/am_stderr.log
v MS_home/logs/am_stdout.log
v MS_home/msg-component.log
v MS_home/trace-component.log
v MS_home/audit-ms.log
LogViewer
ITCAM for Application Diagnostics supports a common XML format in which log
messages and traces are logged. This viewer processes logs in that format so you
can view and query their content.
The viewer can filter messages and traces by time, severity, thread ID, component,
and other data, and convert the logged messages into ASCII or HTML for
presentation. Visual cues are associated with error and warning messages.
In this section, the following terminology is used:
v A log record is a single coherent entry in the log file. The log record contains
several fields (time, server, logText, etc.). A log should describe either user
activities or the visible behavior of the program.
v A trace record is a single coherent entry in the trace file (similar to the log
record). A trace record describes the internal activity of the application. Tracing
is of interest to a programmer; trace records are not generally useful to the end
user.
v A column header: Each log or trace record contains multiple fields, some more
interesting than others. The term column header refers to these items.
v A filter predicate describes an expression that the LogViewer uses to determine
if a particular record will be present in the output. Contrast with column header,
which describes a field within the record.
Starting the LogViewer
You can start the viewer either by the wrapper script (recommended) or direct
JVM invocation.
Using the wrapper script: In Windows, the wrapper script is located at
MS_HOME\logviewer. You can start the LogViewer by running the following
command:
viewer.bat [(-q Query_String) | (-f filename)]
[-s (text | html)]
[-h]
<input1.xml> [<input2.xml> <input3.xml> ...]
where:
v -q specifies a query string, which defines what will be in the output and the
format of that output. See “Specifying the query string” on page 13.
v -f specifies a file that contains the query string.
Only one of -q or -f can be specified.
Chapter 1. Log files, tracing, and utilities
11
v -s specifies either text or html output (default is html). The html output is in
UTF-8 encoding. Text output is in the default encoding of the console where the
command is issued.
v -h displays the usage statement.
v All other arguments are interpreted as log XML input files. When multiple input
files are given, the log and trace records are merged based on the timestamp.
In UNIX, the wrapper script is located at MS_HOME/logviewer. You can start the
LogViewer by running the following command:
viewer.sh [(-q Query_String) | (-f filename)]
[-s (text | html)]
[-h]
<input1.xml> [<input2.xml> <input3.xml> ...]
Direct JVM invocation: To start the LogViewer by direct JVM invocation, please
set the CLASSPATH environment variable such that the following binary files are
included:
v jlog.jar
v viewer.jar
v xmlparserAPIs.jar
v xercesImpl.jar
v regex4j.jar
Run the following command to start the LogViewer:
java -DVIEWER_HOME=
[-DTRACE=DEBUG_MIN]
[-DSHOWTITLE=TRUE]
com.tivoli.log.viewer.Cli
[(-q Query_String) | (-f filename)]
[-s (text | html)]
[-h]
<input1.xml> [<input2.xml> <input3.xml> ...]
where:
v the -DVIEWER_HOME system property defines the location of the stylesheet
(.css) files. These stylesheets will be embedded in the output HTML file.
v the -DTRACE system property defines the level of tracing. The default is
DEBUG_MIN, but DEBUG_MID and DEBUG_MAX are also valid settings.
v the -DSHOWTITLE system property directs the HTML formatter to either
include or omit the title. The default is to include the title. The title consists of a
comma-separated list of input filenames.
v -cp "viewer.jar:jlog.jar:xercesImpl.jar:xmlparserAPIs.jar:regex4j.jar" indicates to
the JVM which .jar files must be available so the viewer can function. If these
.jar files are not in the current directory, provide the full pathname to each .jar
file.
Note: This example uses the UNIX colon separator ':'. In DOS, this would be a
semicolon, ';'.
v -q specifies a query string, which defines what will be in the output and the
format of that output. See “Specifying the query string” on page 13.
v -f specifies a file that contains the query string.
Only one of -q or -f can be specified.
12
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
v -s specifies either text or html output (default is html). The html output is in
UTF-8 encoding. Text output is in the default encoding of the console where the
command is issued.
v -h displays the usage statement.
v All other arguments are interpreted as log XML input files. When multiple input
files are given, the log and trace records are merged based on the timestamp.
Specifying the query string: The query string has the following format:
select column[,column] where Filter_Predicate
Following the reserved word "select" comes one or more column headers. These
are the elements of the log or trace records that will appear n the output. A
timestamp is always displayed in the output for each record.
After the reserved word "where" comes a filter predicate, which determines which
records will be present in the output.
The default query string is:
select default where true
Table 4 lists the column names.
Table 4. Available column names for LogViewer queries
column header
datatype
content
all
select all columns
default
default columns are Time, Severity, MessageId,
LogText, Server, ProductId, Component, and
ProductInstance
Element
string
either Message or Trace
Time
string
localized time
Millis
long int
time in milliseconds
Server
string
server name or IP address
ServerFormat
string
for example, TCP/IP
Client
string
client name
ProductId
string
three letters
Component
string
ProductInstance
string
LogText
string
SourceFile
string
name of the source file where the event was
generated
SourceMethod
string
name of the method that generated the event
SourceLine
string
line number where the event was generated
CorrelationId
string
Principal
string
Process
string
Thread
string
Exception
string
MessageId
string
Chapter 1. Log files, tracing, and utilities
13
Table 4. Available column names for LogViewer queries (continued)
column header
datatype
TraceLevel
string
Severity
string
LogAttribs
string
content
Note: The column headers are not case sensitive.
Specifying the filter predicate: A filter predicate can be either an expression or
the reserved word "true", which is a complete filter expression that indicates
filtering is disabled and that every log and trace record should be output.
Conditional operators used in the filter predicate:
v = (equal)
v > (greater than)
v < (less than)
v >= (greater than or equal to)
v <= (less than or equal to)
v <> (not equal to)
v MATCH. The MATCH pattern-matching operator is a very powerful operator
that allows you to select log or trace records using regular-expression syntax.
Strings with either special characters or spaces used in the regular expression
must be enclosed in single quotes.
Boolean operators used in the filter predicate are OR and AND. Boolean operators
conjoin two expressions. They must take the form:
(expression) OR (expression)
(expression) AND (expression)
The parentheses are required around each expression.
Error handling: The query string is verified for correctness, and processing halts
if the query string is malformed. The column labels are validated. Each
command-line argument is validated; if an invalid argument value is specified,
processing halts. If one of the input log XML files is malformed, there will be no
further attempt to read from that file; however, other input files will be processed.
Examples: Show the default fields of all message and trace records in html form:
viewer sample.xml > sample.html
Select for display all fields with a correlation ID of 12. The output is sent to stdout:
viewer -q"select all where CorrelationId = 12" -stext sample.xml
Display all fields with a timestamp less than 1007067881373 milliseconds
(Timestamp is the only column name that takes a numeric argument instead of a
string). Output is in text format, written to stdout:
viewer -q"select all where Millis < 1007067881373" -stext sample.xml
Display only the server and the product ID that meet the boolean expression. Since
boolean operators are present, parentheses indicate the order of operator
evaluation. Input is merged from three files: sample1.xml, sample2.xml, and
sample3.xml:
14
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
java -DVIEWER_HOME="./" -DTRACE="DEBUG_MAX" com.tivoli.log.viewer.Cli
-q"select server,ProductId where (messageid MATCH ’FRWEP00[10-45]’)
AND ((server = ’joe’) OR (severity = ’ERROR’))"
sample1.xml sample2.xml sample3.xml
Filter on the log attribute with the name FNG and the value 123:
viewer -q"select default where LogAttribs MATCH ’FNG=123’" sample.xml
Troubleshooting: Boolean operators require parentheses. The following example
demonstrates the strictness of boolean evaluation:
viewer -q"select default where (server = ’joe’) AND (element = ’trace’)
AND (messageID=’FRWEP0001E’)"
This results in the following error:
2002.04.10 14:52:19.755 com.tivoli.log.viewer.QueryTree labels Tivoli IVR 1
log viewer wintest2.dev.tivoli.com IP
IVR0019E unexpected character after query: AND
The solution is to ensure that each boolean expression has the form "(expression)
OR (expression)" or "(expression) AND (expression)". So in this case, we could
change the example to:
viewer -q"select default where ((server = ’joe’) AND (element = ’trace’))
AND (messageID = ’FRWEP0001E’)"
Using quotes in the query string: The following example attempts to make a query
using the MATCH operator, but the query string is not delimited by double quotes:
viewer.sh -qselect default where logText match ^get *.xml
This results in the following error:
2002.03.29 14:21:47.014 com.tivoli.log.viewer.QueryTree labels Tivoli IVR 1
log viewer aix102.dev.tivoli.com IP IVR0017E missing column label
When a query is incomplete, LogViewer issues an error to indicate which
component of the query string was found to be missing. In this example it was
expecting to find a column label, but the string terminated. Without double quotes
around the query string, the shell provides each word of the query in a different
argument, resulting in the string appearing as "select". We can correct the situation
by adding double quotes around the query string like so:
viewer.sh -q"select default where logText match ^get" *.xml
Upon running this corrected query, we get the following error:
2002.03.29 14:18:53.423 (null) main Tivoli IVR 1
log viewer jrowlan2.dev.tivoli.com IP
IVR0021E Invalid character ^ found in query string.
The query syntax allows values to be enclosed in single quotes, which signal to the
viewer that the string inside the single quote need not be parsed:
viewer.sh -q"select default where logText match ’^get’" *.xml
Single quotes are also required if the term contains spaces. Directory names and
file names occasionally contain spaces. Since the viewer accepts space-separated
file names, this creates ambiguity. The following could be interpreted either as two
separate files , "a" and "b/c", or as a single file, "c", in subdirectory "a b":
viewer a b/c
To resolve this, use quotes around any file name that contains spaces. For example:
Chapter 1. Log files, tracing, and utilities
15
viewer "a b/c"
identifies a file named "c" in subdirectory "a b", whereas
viewer a b/c
identifies two files, "a" and "c in subdirectory b".
Tracing and logging within the Tivoli Enterprise Portal (Summary
Workspaces)
On the Tivoli Enterprise Portal server and client, ITCAM for Application
Diagnostics installs custom code for the Summary Workspaces.
In case of unexpected behavior in these workspaces you may perform tracing both
on the server (backend) and on the client (desktop or Web). The tracing results will
be available in log files.
Tracing and logging within the Tivoli Enterprise Portal Server
To turn on tracing on the Tivoli Enterprise Portal Server, edit the following file:
v on Windows, ITM_home\cnps\kfwenv
v on UNIX systems or Linux, ITM_home/config/cq.ini
If there is a line starting with SET KBB_RAS1 = , append the following text to this
line:
(UNIT:ITCAMWREvaluatorImpl INPUT ERROR DETAIL)(UNIT:SituationProcessor
INPUT ERROR DETAIL)(UNIT:TepsQueryHelper INPUT ERROR DETAIL)
If such a line does not exist in the file, add the following line to it:
SET KBB_RAS1 = ERROR (UNIT:ITCAMWREvaluatorImpl INPUT ERROR DETAIL)
(UNIT:SituationProcessor INPUT ERROR DETAIL)
(UNIT:TepsQueryHelper INPUT ERROR DETAIL)
After this, restart the Tivoli Enterprise Portal Server. Re-create the unexpected
behavior, and get the following log file:
v on Windows, ITM_home\CNPSJ\profiles\ITMProfile\logs\ITMServer\
SystemOut.log
v on UNIX systems or Linux, ITM_home/ITM_BINARCH/iw/profiles/ITMProfile/
logs/ITMServer/SystemOut.log
Tracing and logging within the Tivoli Enterprise Portal desktop
client on Windows
To turn on tracing on the Tivoli Enterprise Portal desktop client on Windows, edit
the file ITM_home\cnp\cnp.bat . Change the following line:
set _CMD= %_JAVA_CMD% -Xms64m -Xmx256m -showversion -noverify =-classpath %CPATH%
-Dkjr.trace.mode=LOCAL -Dkjr.trace.file=C:\IBM\ITM\CNP\LOGS\kcjras1.log -Dkjr.
trace.params=ERROR -DORBtcpNoDelay=true -Dibm.stream.nio=true -Dice.net.
maxPersistentConnections=16 -Dice.net.persistentConnectionTimeout=1 -Dcnp.http
.url.host=SVOINEA2 -Dvbroker.agent.enableLocator=false candle.fw.pres.CMWApplet
to:
16
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
set _CMD= %_JAVA_CMD% -Xms64m -Xmx256m -showversion -noverify -classpath %CPATH%
-Dkjr.trace.mode=LOCAL -Dkjr.trace.file=C:\IBM\ITM\CNP\LOGS\kcjras1.log -Dkjr.
trace.params="ERROR (UNIT:WR DETAIL)" -DORBtcpNoDelay=true -Dibm.stream.nio
=true -Dice.net.maxPersistentConnections=16 -Dice.net.persistentConnectionTimeout
=1 -Dcnp.http.url.host=SVOINEA2 -Dvbroker.agent.enableLocator=false candle.fw.pres
.CMWApplet
Then restart the Portal client, re-create the unexpected behavior, and exit the Portal
client.
Get the following log files: ITM_home\cnp\kcjras1*.log
Tracing and logging within the Tivoli Enterprise Portal desktop
client on UNIX systems or Linux
To turn on tracing on the Tivoli Enterprise Portal desktop client on UNIX systems
or Linux, edit the file ITM_home/ITM_BINARCH/cj/bin/cnp.sh . Change the following
line:
${TEP_JAVA_HOME}/bin/java -Xms64m -Xmx256m -showversion -noverify
-classpath ${CPATH} -Dkjr.trace.mode=LOCAL
-Dkjr.trace.file=/opt/IBM/itm621/Home/logs/kcjras1.log
-Dkjr.trace.params=ERROR -Dibm.stream.nio=true
-DORBtcpNoDelay=true -Dcnp.http.url.host=
-Dkjr.browser.default=/usr/bin/mozilla -Dvbroker.agent.enableLocator=false
-Dhttp.proxyHost= -Dhttp.proxyPort= candle.fw.pres.CMWApplet
$1 $2 $3 $4 $5 $6 $7 $8 $9 $10 2>&1 1>> ${LOGFILENAME}.log
to:
${TEP_JAVA_HOME}/bin/java -Xms64m -Xmx256m -showversion -noverify
-classpath ${CPATH}
-Dkjr.trace.mode=LOCAL -Dkjr.trace.file=/opt/IBM/itm621/Home/logs/kcjras1.log
-Dkjr.trace.params="ERROR (UNIT:WR DETAIL)" -Dibm.stream.nio=true
-DORBtcpNoDelay=true -Dcnp.http.url.host= -Dkjr.browser.default=/usr/bin/mozilla
-Dvbroker.agent.enableLocator=false -Dhttp.proxyHost= -Dhttp.proxyPort=
candle.fw.pres.CMWApplet $1 $2 $3 $4 $5 $6 $7 $8 $9 $10 2>&1 1>>
${LOGFILENAME}.log
Then restart the Portal client, re-create the unexpected behavior, and exit the Portal
client.
Get the following log files: ITM_home/logs/kcjras1*.log
Tracing and logging within the Tivoli Enterprise Portal Web
client
To turn on tracing on the Tivoli Enterprise Portal Web client, edit the following file
on the Tivoli Enterprise Server host:
v on Windows, ITM_home\CNB\applet.html
v on UNIX systems or Linux, ITM_home/ITM_BINARCH/cw/applet.html
Change the following line:
<PARAM NAME = "kjr.trace.params" VALUE="ERROR">
to
<PARAM NAME = "kjr.trace.params" VALUE="ERROR(UNIT:WR DETAIL)">
On a Windows system, launch a Web browser, re-create the unexpected behavior of
the Tivoli Enterprise Portal, and exit the browser.
Chapter 1. Log files, tracing, and utilities
17
Then, get the following log files: C:\Documents and Settings\username\
Application Data\IBM\Java\Deployment\log\*.trace
Environment Checking Utility
The Environment Checking Utility (ECU) is a stand-alone tool. You can use this
utility to check the prerequisite packages before launching the ITCAM Agent for
WebSphere Applications installer, ITCAM Agent for WebSphere Applications
configuration, or Managing Server installer. The ECU generates a report to specify
if the prerequisite packages have been installed correctly. The prerequisite packages
are registered in a property file. The property file can be extended if new
prerequisite packages or libraries are required.
To get the Environment Checking Utility, use IBM Passport Advantage®
(http://www.ibm.com/software/passportadvantage). Search for the IBM Tivoli
Composite Application Manager for Application Diagnostics V7.1: (ITCAMAD71)
Managing Server Component. The ECU is also shipped as a part of the ITCAM for
Application Diagnostics installation media set.
Complete the following installation steps before launching the Environment
Checking Utility:
1. Install the Runtime Environment for the Java platform version 1.4.2 or higher.
2. Set JAVA_HOME in the system environment variables.
v For Windows, set JAVA_HOME=JRE_PATH
v For Linux and UNIX systems, JAVA_HOME=JRE_PATH; export JAVA_HOME
3. Use one of the following commands to launch the ECU:
v For Windows, envcheck.bat
v For Linux and UNIX systems, envcheck.sh
On UNIX systems, to ensure the ECU can gather all the necessary operating
system information, log on as the root user.
4. Use the following command line to launch the ECU on Windows:
envcheck.bat -reportPath Report_save_path [-check Configuration_file_name]
[-logPath Log_path] [-tmpPath Tmp_path] [-showSteps] [-noWizard] [-help]
On Linux and UNIX systems, use the following command line to launch the
ECU:
./envcheck.sh -reportPath Report_save_path [-check Configuration_file_name]
[-logPath Log_path] [-tmpPath Tmp_path] [-showSteps] [-noWizard] [-help]
You can use the following parameters:
a. -reportPath Report_save_path
This parameter is required. The ECU generates a report of all the content
checks. Report_save_path indicates the path name to save the report to.
b. -check Configuration_file_name
This parameter is optional. You can use this parameter to specify the
configuration file for this release. There are two configuration files -check
itcamfwas_dc and -check itcamfwas_ms in the ECU command line.
v itcamfwas_dc: defines the environment check steps and parameters for
the Data Collector
v itcamfwas_ms: defines the environment check steps and parameters for
the Managing Server
18
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
If you do not specify the -check parameter option in the command line at
the beginning of ECU execution, the ECU will prompt you to select one of
the configuration files.
c. -logPath Log_path
This parameter is optional. It indicates the log path name for the ECU. The
default log directory is ECU_PATH/logs.
d. -tmpPath Tmp_path
This parameter is optional. It indicates the temporary directory for ECU.
The default temporary directory is ECU_PATH/tmp.
e. -showSteps
This parameter is optional. If you have this parameter in the command line,
the ECU will prompt you with steps generated by a navigation wizard.
f. -noWizard
This parameter is optional. If you have this parameter in the command line,
the ECU will not prompt you for any wizard navigation inputs but the
following options are available: Back, Next or Cancel.
g. -help
This parameter is optional. Display information on available options.
5. The ECU performs the following checks. You are prompted to enter any
additional information if required.
a. OS Information check.
Checks operating system version, release, architecture, bit mode, and user
information.
b. Prerequisite OS packages and libraries check.
On a UNIX platform, the ECU checks the prerequisite packages of ITCAM
Agent for WebSphere Applications Data Collector and ITCAM Agent for
J2EE Data Collector.
c. Processor and memory information check.
Checks the information processors and memory.
d. Database information check.
Checks installed DB2 information.
e. Ports check.
Checks the default ports of the Data Collector.
f. Select WebSphere Home.
Selects the WebSphere Application Server home directory to check.
g. WebSphere Information check.
h.
i.
j.
k.
l.
Checks the selected WebSphere Application Server information.
Global Security Status check.
Checks the Global Security Status of selected WebSphere Application Server
information.
Select Application Server Instance.
Selects the application server instances to check.
JVM parameters check.
Checks the JVM parameters of selected application server instances.
WebSphere Connection wsadmin check.
Checks the wsadmin connection of selected application server instances.
Generate Java Core.
Chapter 1. Log files, tracing, and utilities
19
Generates Java core of selected application server instances.
m. Open source J2EE frameworks check.
Checks if open source J2EE frameworks are installed on the selected
application server instances.
n. Third-party tools check.
Checks if third-party tools are installed on the selected application server
instances.
o. Other Tivoli products check.
Checks if other Tivoli products are installed on the selected application
server instances.
The ECU generates a report of the content checks and saves it to the
location specified by the -reportPath parameters.
Installing Memory Dump Diagnostic for Java with IBM Support
Assistant
Memory Dump Diagnostic for Java (MDD for Java) either analyzes a single heap
dump or analyzes and compares two heap dumps and searches for evidence of a
memory leak. In order to download MDD for Java, you will need to first install
IBM Support Assistant (ISA). ISA provides extra help with diagnosing problems
and provides extra tools and components for troubleshooting as well as providing
a place to write problems (PMRs).
You can either manually take a heap dump or schedule a heap dump using MDD
for Java's Heap Dump Management feature.
The Heap Dump Management feature allows you to schedule or immediately
initiate the collection of an IBM Heap Dump for a particular application server.
Then this dump must be downloaded and post-processed outside ITCAM's user
interface (Application Monitor) using MDD for Java. The other Memory Diagnosis
tools provided by ITCAM, such as Memory Analysis, Heap Analysis and Memory
Leak Diagnosis, provide analysis via the Application Monitor.
MDD for Java only analyzes heap dumps from IBM JDKs. For non-IBM JDKs use
the ITCAM Memory Leak Diagnosis feature.
If you are using an OS/400 system, MDD for Java is only supported on PASE JDK.
Searching capabilities are not supported for ITCAM for Application Diagnostics in
ISA.
Where to install ISA and MDD for Java
The following are two common configurations:
v Install ISA & MDD for Java on a standalone server that is not running an
application server. After the IBM heap dump has been collected on the
application server, it must be transfered to the MDD for Java computer for
post-processing.
This configuration is recommended for production environments where you do
not want the post-processing of the dump to impact the performance of the
application server.
v Install ISA and MDD for Java on each application server host machine, so that
you can analyze the heap dump locally without having to transfer it.
20
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
This configuration may be suitable for a development or test environment where
the overhead of analyzing the heap dump is not a concern.
The decision on where to install may also be influenced by the platforms
supported by ISA.
Downloading ISA
To download ISA, perform the following procedure:
1. Go to the following URL:https://www14.software.ibm.com/webapp/iwm/
web/preLogin.do?source=isa
2. If you do not have a universal IBM user ID, you will need to click register now
and fill in the required information. Upon completion, you can return to this
page and sign in to download ISA.
3. After signing in, select the radio button to download IBM Support Assistant
Version 3.0.0.1.
4. Click Continue.
5. Select View license. After reading the license, click the I agree check box and
then click I confirm to continue with the download.
6. Click Download now next to the correct platform. It is suggested you
download to the server on which the Data Collector is installed.
7. Click Save to download ISA to your hard drive.
Installing ISA
Perform the following procedure to install ISA:
1. Go to the directory on your hard drive where you saved the ISA zip file.
2. Extract the files.
3. Double-click the setupwin32.exe file.
4. Follow the installation instructions to install ISA.
5. Open the ISA program.
Installing MDD for Java
Perform the following procedure to install MDD for Java:
1. Double-click Updater to open it.
2. Select the New Products and Tools tab.
3. Open the WebSphere directory by clicking the + sign.
4. Click the check box to select WebSphere Application Server. (The version you
select does not matter.)
5. Click Install.
6. Select the feature under Features to Install and review the license.
7. Click Yes to accept the license.
8. Click OK to accept the following message that displays:
New product plug-ins or tool plug-ins were installed successfully.
Please make sure to restart IBM Support Assistant for these changes
to take effect.
9. Click Install.
10. Click OK to accept the following message that displays:
Chapter 1. Log files, tracing, and utilities
21
Reminder–You are installing a common component tool.
After installation, you may not see the common component tool in the
Tools component.
Common component tools only display in the Tools component
if a product is added that uses them.
11.
12.
13.
14.
22
This is why you need to install a version of WebSphere.
Select Memory Dump Diagnostic for Java under the Features to Install and
review the license.
Click Yes to accept the license.
Click OK at the restart IBM Support Assistant message.
Close and restart ISA.
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Chapter 2. System Messages for ITCAM Agent for WebSphere
Applications
CYNAA Messages: Archive Agent
The Archive Agent is a Java component of the Managing Server. All such messages
have IDs in the range CYNAA0001D to CYNAA0032E.
CYNAA0001D: Queue Queue in the Archive Agent has
wrapped. The queue size is QueueSize. The total enqueued is
TotalEnqueued. The total dequeued is TotalDequeued.
Explanation
See message.
CYNAA0002W: Queue Queue in the Archive Agent is full. All
entries have been discarded. The queue size is QueueSize.
The total enqueued is TotalEnqueued. The total dequeued is
TotalDequeued.
Explanation
If this error occurs more than five times, follow the instructions shown in the
Operator Response.
Operator response
Increase the queue size property for the specified queue in the properties file for
the Archive Agent. For example, if Archive Agent aa1 is throwing this error for the
PMI queue, increase the queue's PMI size in aa1.properties and restart the Archive
Agent.
CYNAA0003I: An unexpected worker type was created in the
Archive Agent.
Explanation
The client created a worker type that is not valid. The only valid values are
WT_PRODUCER , WT_CONSUMER , and WT_SERVICER.
CYNAA0004I: An unexpected data message type was created
in the Archive Agent.
Explanation
The client created a message type that is not valid. The valid value is MT_DATA.
© Copyright IBM Corp. 2007, 2010
23
CYNAA0005D: The client disconnected from the Archive Agent
server. Worker thread WorkerThread is ending. The component
ID is ComponentId .
Explanation
The thread used to process the connection is ending.
CYNAA0006D: The Archive Agent is initializing queue Queue.
The queue type is QueueType. The component ID is
ComponentId.
Explanation
See message.
CYNAA0007I: There is an unknown queue type in the Archive
Agent for queue Queue.
Explanation
Supported queue types are PMI, method, polling, availability, memory, and
trap_actionHistory.
CYNAA0008I: There is an unspecified priority for queue type
QueueType. The Archive Agent is continuing with default
priority DefaultPriority.
Explanation
See message.
CYNAA0009I: There is an unspecified size for queue Queue.
The Archive Agent is continuing with default size DefaultSize.
Explanation
See message.
CYNAA0010I: The Producer Connection ProducerConnectionto
the Archive Agent server was established. The component ID
is ComponentId.
Explanation
See message.
CYNAA0011I: The Consumer Connection ConsumerConnection
to the Archive Agent server was established. The component
ID is ComponentId.
Explanation
See message.
24
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNAA0012I: The Servicer Connection ServicerConnection to
the Archive Agent server was established. The component ID
is ComponentId.
Explanation
See message.
CYNAA0013I: The Archive Agent server is now listening at
port Port.
Explanation
See message.
CYNAA0014I: The Archive Agent server is shutting down.
Explanation
See message.
CYNAA0015I: The Archive Agent server's shutdown is
complete.
Explanation
See message.
CYNAA0016E: An error ErrorCode occurred while starting up
database agents.
Explanation
There are possible database connection errors.
Operator response
Ensure that the database connection parameter values for JDBC_DRIVER_NAME,
JDBC_DRIVER_JAR, JDBC_DRIVER_URL, JDBC_USER, and JDBC_PASSWORD in
the setenv.sh file, and restart the Archive Agent.
CYNAA0017E: The Archive Agent was unable to join the
Kernel.
Explanation
The Kernel is down.
Operator response
Restart the Kernel. After the Kernel starts successfully, restart the Archive Agent.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
25
CYNAA0018E: An exception occurred while creating Archive
Agent server socket ServerSocket. The Archive Agent is
ending.
Explanation
See message.
Operator response
If the Archive Agent is already running. stop and restart the Archive Agent.
CYNAA0019E: An exception occurred while accepting Archive
Agent server socket connection SocketConnection. The Archive
Agent is ignoring the exception.
Explanation
See message.
Operator response
If the Archive Agent is already running, stop and restart the Archive Agent.
CYNAA0020I: The Archive Agent is discarding a request
record with mismatched records.
Explanation
See message.
CYNAA0021I: A request record in the Archive Agent has
corrupted (mismatched) methods.
Explanation
The entry or exit sequences in method data do not match, so all methods in that
record are being discarded.
CYNAA0022E: Archive Agent ArchiveAgent encountered error
Error while starting.
Explanation
See message.
Operator response
If the error is a database error, check the database parameter values in the
setenv.sh file. Run amctl.sh dbtest to determine whether the database connection is
valid. Restart the Archive Agent after fixing any database errors.
CYNAA0023I: Archive Agent ArchiveAgentis starting.
Explanation
See message.
26
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNAA0024I: Archive Agent ArchiveAgentis shutting down.
Explanation
See message.
CYNAA0026E: There was a socket error while creating worker
thread WorkerThread.
Explanation
See message.
Operator response
Ensure that socket port that is specified in setenv.sh and used for the Archive
Agent is valid and not being used by any other program.
CYNAA0027E: The Archive Agent with component ID
ComponentId is not registered with the Kernel.
Explanation
See message.
Operator response
Check the status of the kernel by running amctl.sh kl1 status and amctl.sh kl2
status. If the Kernel is not started or is hung, restart the Kernel. When the Kernel
has started successfully, restart the Archive Agent.
CYNAA0028E: The Archive Agent's properties file was not
found.
Explanation
Either the Archive Agent's properties file does not exist or the correct path was not
specified.
Operator response
Ensure that the aa1.properties file and the aa2.properties file exist. If they are in the
$AM_home/etc directory, restart the Archive Agent.
CYNAA0029E: Database exception Exception occurred when
inserting or updating data from table Table.
Explanation
See message.
Operator response
To resolve the database exception, check the exception stack trace in the trace file.
If it is a deadlock error and occurs many times, turn off the data trimmer by
setting ENABLE_DATATRIMMER to False. Restart the Archive Agent and run the
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
27
data trimmer process manually. For other exceptions, contact your database
administrator.
CYNAA0030W: Database exception Exception occurred while
deleting data from table Table.
Explanation
See message.
Operator response
To resolve the database exception, check the exception stack trace in the trace file.
If it is a deadlock error and occurs many times, turn off the data trimmer by
setting ENABLE_DATATRIMMER to False. Restart the Archive Agent and run the
data trimmer process manually. For other exceptions, contact your database
administrator.
CYNAA0031E: Database exception Exception occurred while
updating or deleting data from the table in the Archive Agent.
Explanation
See message.
Operator response
To resolve the database exception, check the exception stack trace in the trace file.
CYNAA0032E: The thread ID is null. The IMS record was
discarded.
Explanation
See message.
CYNAU Messages: Application Monitor
The following messages relate to the Application Monitor. Another name for the
Application Monitor is Visualization Engine. All such messages have IDs in the
range CYNAU0001I to CYNAU135I.
CYNAU0001I: WebServer webservName is Removed
Explanation
The specified Web Server was removed.
CYNAU0002I: WebServer webservName was added
Explanation
The specified Web Server was added.
28
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNAU0005I: username added account accname
Explanation
The user added the specified account successfully.
CYNAU0006I: username modified account accname1 and
accname2
Explanation
The user modified the specified account successfully.
CYNAU0007I: username modified group assignments for
accname1 and accname2
Explanation
The user modified the specified account group assignments successfully.
CYNAU0008I: username deleted account accname
Explanation
The user deleted the specified account successfully.
CYNAU0009I: username logged in.
Explanation
The user logged in successfully.
CYNAU0010I: username failed log-in because the user does
not exist.
Explanation
The user failed to log in because the user doesn't exist.
CYNAU0011I: username failed log in because the account is
suspended.
Explanation
The user log-in failed because the user account is suspended.
CYNAU0012I: username failed login because the password
used was incorrect.
Explanation
The user log-in failed because the password was incorrect.
CYNAU0013I: username logged out
Explanation
The user logged out successfully.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
29
CYNAU0014I: username session timed out.
Explanation
The user session timed out.
CYNAU0015I: username with unix username, unxusername,
authenticated.
Explanation
The user was successfully authenticated.
CYNAU0016I: username , unix username unxusername failed
authenticated.
Explanation
The user authentication failed.
CYNAU0017I: username changed unxusername account status
to: accstatus
Explanation
The user account status was successfully changed.
CYNAU0018I: Created Role : rolename
Explanation
The user role was successfully created.
CYNAU0019I: Role : rolename deleted
Explanation
The user role was successfully deleted.
CYNAU0020I: Role : rolename is duplicated to : newrolename
Explanation
The user role was successfully duplicated.
CYNAU0021I: Role : newrolename is Modified.
Explanation
The user role was successfully modified.
CYNAU0030I: For user : userName creating Schedule :
scheName
Explanation
The schedule was successfully created for the user.
30
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNAU0031I: Modifying Schedule : scheName informatin
minute : min hour : hrs week : week month : month level : level
Explanation
The schedule information was successfully modified.
CYNAU0032I: For user : userName modifying Schedule :
scheName
Explanation
The schedule was modified successfully.
CYNAU0033I: Schedule: ScheduleNamewas deleted
Explanation
The schedule was deleted successfully.
CYNAU0036I: UESR : username changed the PRIORITY :
priority of the THREAD : threadid on SERVER : servername
Explanation
The user successfully changed the thread priority.
CYNAU0037I: UESR : username changed the STATUS : status
of the THREAD : threadid on SERVER : servername
Explanation
The user successfully changed the thread status.
CYNAU0038I: Server Group : groupName created by : uname
Explanation
The server group was created Successfully.
CYNAU0039I: Server Group : groupName modified by :
modname old values are : oldval accounts = accName and
servers = servName new values are : oldval accounts =
accName and servers = servName
Explanation
The server group was modified successfully.
CYNAU0040I: Setting schedule : scheName for user :
userName of group : groupName
Explanation
The new Schedule was changed successfully.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
31
CYNAU0041I: Changing MOD Level : modlevel for user :
userName of group : groupName
Explanation
The Monitoring on Demand (MOD) Level was changed successfully.
CYNAU0042I: Setting Sampling L1 : rateL1 L2 : rateL2 and L3 :
rateL3 for user : userName of group : groupName to System
default : sysdefault
Explanation
The sampling rates of the specified group were set to the system defaults
successfully.
CYNAU0043I: Changing Sampling Rate for user : userName of
group : groupName as follows: L1 from : rateL1 to torateL1 L2
from : rateL1 to torateL1 L3 from : rateL1 to torateL1
Explanation
The sampling rates of the specified group were successfully changed.
CYNAU0050I: Setting Schedule to: scheName for user :
userName with Probe : Probeid
Explanation
Schedule was successfully set.
CYNAU0051I: Setting Mod Level to: modLevel for user :
userName with Probe : Probeid
Explanation
The Monitoring on Demand (MOD) Level was changed successfully.
CYNAU0052I: Changing Sampling Rate for user : userName
with Probe : probeId as follows: L1 from : rateL1 to torateL1 L2
from : rateL1 to torateL1 L3 from : rateL1 to torateL1
Explanation
The sampling rates for the specified user were successfully changed.
CYNAU0053I: Changing Sampling Rate for user : userName as:
L1 from : rateL1 to torateL1 L2 from : rateL1 to torateL1 L3 from
: rateL1 to torateL1
Explanation
The sampling rates for the specified user were successfully changed.
32
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNAU0054I: UESR : username soft killed the THREAD :
threadid on SERVER : servername
Explanation
The user successfully soft- killed the Thread.
CYNAU0055I: UESR : username hard killed the THREAD :
threadid on SERVER : servername
Explanation
The user successfully hard- killed the Thread.
CYNAU0132I: uName saved changes to Data Collection
Settings as (Value: Old/New) -- PMI Polling Frequency:
oldPMIFreq/newPMIFreq L1 Sampling Rate:
oldL1Rate/newL1Rate L2 Sampling Rate: oldL2Rate/newL2Rate
L3 Sampling Rate: oldL3Rate/newL3Rate
Explanation
The data collection settings changed successfully.
CYNAU0133I: Default MOD (Monitoring on Demand) Level
Value (Old/New) : oldModLevel/newModLevel Max Method
Records (Old/New) : oldMaxMethRec/newMaxMethRec
Explanation
Data Collector setting changed successfully.
CYNAU0136I: username TIMEOUT
Explanation
The login session timed out.
CYNAU0140I: Server Group : groupName duplicated to :
dupname by origName
Explanation
The server group was duplicated successfully.
CYNAU0141I: Server Group : groupName deleted by : uName
Explanation
The server group is deleted successfully.
CYNAU0143I: New Trap Created nameCreated By: userName
Explanation
The user successfully created a new trap.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
33
CYNAU0144I: Trap Modified Original Values: orgValues New
Values: newValues Created By: createBy Modified By: modifyBy
Explanation
A Trap was modified.
CYNAU0145I: Trap Deleted trapName Deleted By: delBy
Explanation
A Trap was deleted.
CYNAU0146I: Trap Duplicated Old Name: oldName oldName2
Duplicated By: dupBy
Explanation
A Trap was duplicated.
CYNAU0147I: Trap Activated value Created By: createBy
Duration: duration Iterations® left: iterLeft Activation
Suppression Time: actSup Target Data Collector(s): target
Activated By: actBy
Explanation
A Trap was activated.
CYNAU0148I: Trap Activation Modified value Created By:
createBy Duration: duration Terminate when all conditions met:
iterLeft Activation Suppression Time: actSup Target Data
Collector(s): target Activated By: actBy
Explanation
An activated trap was modified.
CYNAU0149I: Trap value deactivated by name
Explanation
A trap was deactivated.
CYNAU0150I: One of your traps was triggered TrapName:
value TrapDate: trapDate trapTime AppServer: appServer
Request: request Method: method TrapCondition: condition
Offending Content: content Threshold: threshold Max/Min:
maxMin Number Of Hits: hits
Explanation
A trap was triggered.
34
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNAU0151I: One problem has been created Alert Id: alertId
Problem Timestamp: alertEventTime alertEventTime Group Id:
groupId Probe Id: probeId Name: name Description: description
Origin: origin Status: status
Explanation
A problem was created.
CYNAU0152I: One problem was created Problem Id: problemId
Explanation
A problem was deleted.
CYNAU0153I: The URL from ITCAMfTT is not valid, the
parameter para is null.
Explanation
There is no value for the request parameter.
CYNAU0154I: One problem was updated Problem Id: problemId
Status: status
Explanation
A problem was deleted.
CYNAU0155I: One heap dump schedule has been created
Username: userName Date/Time: dateTime Group: group
Server: server Force GC: gc
Explanation
A heap dump schedule has been created.
CYNAU0156I: One heap dump schedule has been modified
Username: userName Date/Time: dateTime Group: group
Server: server Force GC: gc
Explanation
A heap dump schedule has been modified.
CYNAU0157I: One heap dump schedule has been deleted
Username: userName Date/Time: dateTime Group: group
Server: server Heap dump file name: fileName
Explanation
A heap dump schedule has been deleted.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
35
CYNAU134I: uName saved changes to Application Overview
Settings as (Value: Old/New) -- Threshold1:
oldThreshold1/newThreshold1 Threshold1: oldThreshold2/
newThreshold2 Baseline Type: baselineType
Explanation
The application overview settings were successfully changed.
CYNAU135I: uName saved changes to SNMP Settings as
(Value: Old/New) -- Host: oldHost/newHost Port: oldPort/newPort
Community: oldCommu/newCommu
Explanation
The SNMP settings were successfully changed.
CYNB Messages: Byte Code Modification
The following messages relate to Byte Code Modification. All such messages have
IDs in the range CYNB6007E to CYNB6107I.
CYNB6007E: Exception exception occurred while parsing XML
file filename.
Explanation
An error happened during parsing of the specified Byte Code Modification user
instrumentation control file.
Operator response
Check the existence and validity of the Byte Code Modification user
instrumentation control file.
CYNB6008E: Exception exception occurred while parsing XML
file filename.
Explanation
An error happened during parsing of the specified Byte Code Modification user
instrumentation control file.
Operator response
Check the existence and validity of the Byte Code Modification user
instrumentation control file.
CYNB6009I: The system was unable to locate the
userbcm.xmlfilename property.
Explanation
The system could not find the property from the Application Server's Byte Code
Modification properties file that specifies the Byte Code Modification user
instrumentation control file name.
36
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
Do nothing, if you do not want to instrument your application classes. If you do
want to instrument your application classes, add userbcm.xmlfilenameproperty to
your Application Server's Byte Code Modification properties file and specify it
with your Byte Code Modification user instrumentation control file name.
CYNB6011I: The Byte Code Modification engine is
instrumenting class className.
Explanation
This message is in regards to BcmClassLoader.
CYNB6013W: This is warning message name. The Byte Code
Modification engine might experience problems during class
loading and manipulation.
Explanation
See message.
Operator response
Check the Byte Code Modification trace log for further information.
CYNB6014W: Exception man: pkgname:className has
occurred after execution of Byte Code Modification.
Explanation
Manifest is not present in the package.
Operator response
Check the Byte Code Modification trace log for further information.
CYNB6017I: The name of the request file is filename.
Explanation
The Byte Code Modification engine reports enabled request definition XML files in
the Byte Code Modification properties file.
CYNB6019I: The Byte Code Modification engine loaded the
definition for an instrumented class named name.
Explanation
See message.
CYNB6025W: The Byte Code Modification engine failed to
obtain XML definition files for a platform.
Explanation
See message.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
37
Operator response
Check your installation and check if Java system property appserver.platform is
defined properly.
CYNB6026E: The Byte Code Modification engine failed to load
its properties file.
Explanation
See message.
Operator response
Check if bcm.properties has been installed at the etc subdirectory of the Data
Collector's installation directory.
CYNB6028I: The Byte Code Modification engine is processing
a Java class file named entry.
Explanation
See message.
CYNB6029W: The ClassModifier component is not specified
Explanation
The Byte Code Modification engine could not find its ClassModifier component.
Operator response
Check if Java system am.bcm.classModifier is defined properly.
CYNB6030I: No Byte Code Modification regular expressions
have been specified.
Explanation
The Byte Code Modification engine could not find regular expression definitions.
Operator response
Set the am.bcm.includeList Java system property if needed.
CYNB6031I: The Byte Code Modification engine is adding
regular expression regExpStr to its include list.
Explanation
See message.
38
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNB6032I: The first instruction firstInstruction has been added
to the Byte Code Modification include list.
Explanation
See message.
CYNB6038W: Exception exception has occurred.
Explanation
The Byte Code Modification engine might experience problems during class
manipulation.
Operator response
Check the Byte Code Modification trace log for further information.
CYNB6039W: Byte Code Modification is not instrumenting
native and abstract method Method.
Explanation
The Byte Code Modification engine does not instrument native and abstract
methods.
CYNB6100E: Exception exception has occurred.
Explanation
The Byte Code Modification engine experienced problem when loading its
properties file.
Operator response
Check your installation to make sure the bcm.properties file is present.
CYNB6101E: The default Byte Code Modification properties
file defaultBcmPropFile was not found.
Explanation
The Byte Code Modification engine experienced problem when loading its
properties file.
Operator response
Check your installation to make sure the bcm.properties file is present.
CYNB6103E: An exception occurred while attempting to Byte
Code Modify system class classname.
Explanation
The Byte Code Modification engine experienced problems while instrumenting a
class.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
39
Operator response
Check the Byte Code Modification trace log for further information.
CYNB6104E: An exception occurred while attempting to Byte
Code Modify application class classname.
Explanation
The Byte Code Modification engine experienced problem while instrumenting a
class.
Operator response
Check the Byte Code Modification trace log for further information.
CYNB6105E: An exception occurred while Byte Code
Modification was attempting to build its
WPSRequestInterceptor component.
Explanation
See message.
Operator response
Check the Byte Code Modification trace log for further information.
CYNB6106I: The name of this userbcm.xmlfile is xml file name.
Explanation
See message.
CYNB6107I: Byte Code Modification is instrumenting method
Method.
Explanation
See message.
BWMCR and CYNCR Messages: Installation
The following messages occur during installation. All such messages have IDs in
the range BWMCR8403E to BWMCR8523W or CYNCR8026I to CYNCR9604E.
BWMCR8403E: The password is not correct for the user
specified.
Explanation
The password specified for this user is not correct.
Operator response
Verify the password for this user and retype it, or specify a different user.
40
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
BWMCR8250E: The user does not have authority to create
tables in this database.
Explanation
The user that you entered in the Database User ID field must have authority to
create tables in the specified DB2 or Oracle database.
v This message is displayed if the user does not have authority to create tables in
the tablespace that the database administrator created for the management
repository.
Operator response
Take one of the following actions:
v Type the user ID and password of a user that has authority to create tables in
the tablespace that is used for the management repository.
v Use your database client software to grant authority to the database user
specified in the Database User ID and Database Password fields. Grant the
permission required to create tables in the tablespace to be used for the
management repository.
BWMCR8251E: Installation error. The software generated an
exception
Explanation
An installation error has occurred and might prevent completion of the installation.
Operator response
View the trace log to determine the problem. After correcting the issue, continue
the installation or cancel and restart the installation.
BWMCR8252E: Invalid URL format:
Explanation
The URL of the management server must be specified in the following format:
protocol://hostname:portnumber
where:
v protocol has one of the following values:
– http if the management server is not a secure server
– https if the management server is a secure server
v hostname is the fully qualified name of the host machine for the management
server
v (optional)portnumber is a valid port number that the management server can use
to communicate with the 5.2 management server.
Example: https://msserver.it.company.com:443
Operator response
Type the URL of the management server in the correct format.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
41
BWMCR8253E: The host name cannot contain spaces.
Explanation
The name you entered in the Host Name field contains spaces, as in the following
example:
servername.it.your company.com
Operator response
Type a valid host name with no spaces in the Host Name field.
BWMCR8254E: Invalid data.
Explanation
The installation program encountered invalid data that prevents completion of the
installation.
Operator response
Review the specifications that you have typed. If you are using the installation
wizard, enter the required installation data again and continue the installation . If
the error persists, view the trace log to determine the problem. After correcting the
issue, continue the installation or cancel and restart the installation.
BWMCR8255E: The Host Name field is empty or contains
more than 256 characters.
Explanation
The Host Name field is empty or contains a name that is too long. The DNS
limitation for a fully qualified host name is 256 characters.
Operator response
Verify the correct host name and type it in the Host Name field.
BWMCR8256E: The host name that was entered cannot be
found.
Explanation
The installation program cannot find the specified host name.
Operator response
Type a host name that the Domain Name System (DNS) service can resolve before
you proceed. You must provide the fully qualified host name of the Managing
Server.
42
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
BWMCR8257E: A host name that DNS can resolve must be
provided.
Explanation
The Domain Name System (DNS) service cannot resolve this host name.
Operator response
Type a host name that the Domain Name System (DNS) service can resolve before
you proceed. You must provide the fully qualified host name or the IP address of
the host machine for the management server.
BWMCR8258E: You must enter a fully qualified host name
(such as servername.it.yourcompany.com)
Explanation
This error occurs when you enter a host name with no delimiter characters.
Operator response
Type a fully qualified host name in the Host Name field. For example, enter
servername.it.yourcompany.com, instead of only servername.
BWMCR8259E: An incorrect host name caused an error in the
installation of the management server.
Explanation
The syntax of the host name might be incorrect.
Operator response
Type a host name that the Domain Name System (DNS) service can resolve before
you proceed. You must provide the fully qualified host name or the IP address of
the host machine for the management server.
BWMCR8260E: The port number must be an integer value:
Explanation
This message is displayed when you enter a non-numeric character in the Port
Number field.
Operator response
Type an integer value in the Port Number field, for example, 80.
BWMCR8261E: The specified port number is out of range.
Valid TCP/IP port numbers must be positive integers from 1 to
65535.
Explanation
The Port Number field contains a port number that is not within the accepted
range of 1 to 65535.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
43
Operator response
Type a port number in the Port Number field that is not less than 1 and not
greater than 65535.
BWMCR8262E: Valid TCP/IP port numbers must be positive
integers from 1 to 65535.
Explanation
The port number specified for TCP/IP communication is invalid.
Operator response
Type a port number that is a positive integer greater than zero and less than
65,535.
BWMCR8263E: Invalid data.
Explanation
The installation program encountered invalid data that prevents completion of the
installation.
Operator response
Review the specifications that you have typed. If you are using the installation
wizard, enter the required installation data again and continue the installation . If
the error persists, view the trace log to determine the problem. After correcting the
issue, continue the installation, or cancel and restart the installation.
BWMCR8264E: The text in the host name field must not
include a protocol, such as http:// or https://.
Explanation
This message is displayed when you enter a URL with http:// or https:// in the
Host Name field, as in the following example:
https://msserver.it.yourcompany.com
Operator response
Type a host name without the http:// or https:// protocol. For example, enter
imsserver.it.yourcompany.com.
BWMCR8265E: The computer identified in the Host Name field
cannot be contacted at the specified port.
Explanation
The installation program cannot connect to the computer specified in the Host
Name field because the port is unavailable. The host computer might be down, the
server software on the specified port might be down, or the server software cannot
use the specified port.
44
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
v Verify that you accurately entered the host name and port.
v Consult the trace log for more information about the cause of the failure.
v Make sure that the host name is the name of a computer that has the server
software installed.
v Test connectivity to the network. If the network is down, retry the installation at
a later time.
v Try connecting to the server directly through a browser. In the address field of
the browser, enter the URL of the server, using the host name and port that you
specified in the installation window. Example: https://
servername.it.yourcompany.com:443.
BWMCR8266E: The port is busy:
Explanation
An application is currently using the port that you specified in the Port Number
field.
Operator response
Stop the application that is currently using the port you specified, or specify a
different port.
BWMCR8267E: The user name must not contain spaces.
Explanation
On UNIX-based systems, the management server must run under an existing user
and group on this computer. The user and group names must not contain spaces.
This message is displayed if the name you entered in the User field contains
spaces, for example, management server.
Operator response
Take one of the following actions:
v Type a valid name in the User field with no spaces.
v Modify an existing user name so that it does not contain spaces.
v Create a new user for the product component (management server). Add the
new user to an existing group or create both a new user and a new group. The
user and group names must not contain spaces.
Note:
v You do not need to exit the installation program to create a user or group. When
you are finished, enter the new user name in the User field.
v To work with users and groups, you can use the admintool on Solaris, the smit
on AIX®, the linuxconf on Linux, or any text editor such as VI.
BWMCR8268E: The group name must not contain spaces.
Explanation
On UNIX-based systems, the management server must run under an existing user
and group on this computer. The user and group names must not contain spaces.
This message is displayed if the name you entered in the Group field contains
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
45
spaces, for example, Web Transaction Performance.
Operator response
Take one of the following actions:
v Type a valid name in the Group field with no spaces.
v Modify an existing group name so that it does not contain spaces.
v Create a new group (and optionally, a new user) for the product component
(management server). The user and group names must not contain spaces.
Note:
v The group must be associated with the user name that you enter in the User
field.
v You do not need to exit the installation program to create a user or group. When
you are finished, enter the new name in the User or Groupfield.
v To work with users and groups, you can use the admintool on Solaris, the smit
on AIX, or the linuxconf on Linux, or any text editor such as VI.
BWMCR8269E: The user name cannot be root.
Explanation
You entered root in the User field. The management server cannot run as the root
user. Installing the server under root creates a security risk.
Operator response
Take one of the following actions:
v Type the name of an existing user on this computer, other than root, under
which the product component (management server) can run. The user name
must not contain spaces.
v Create a new user for the product component. Add the new user to an existing
group or create both a new user and a new group. The user and group names
must not contain spaces.
Note:
v You do not need to exit the installation program to create a user or group. When
you are finished, enter the new user name in the User field.
v To work with users and groups, you can use the admintool on Solaris, smit on
AIX, linuxconf on Linux, or any text editor such as VI.
BWMCR8270E: The user is not defined on this computer.
Explanation
The installation program does not recognize the name entered in the User field. On
UNIX-based systems, the management server must run under an existing user on
this computer.
Operator response
Take one of the following actions:
v Type a valid name of an existing user in the User field. The user name must not
contain spaces.
46
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
v Create a new user for the product component (management server). Add the
new user to an existing group or create both a new user and a new group. The
user and group names must not contain spaces.
Note:
v You do not need to exit the installation program to create a user or group. When
you are finished, enter the new user name in the User field.
v To work with users and groups, you can use the admintool on Solaris, smit on
AIX, linuxconf on Linux, or any text editor such as VI.
BWMCR8271E: The group is not defined on this computer.
Explanation
The installation program does not recognize the name that you entered in the
Group field.
Operator response
Take one of the following actions:
v Type a valid name of an existing group in the Group field. The group name
must not contain spaces.
v Create a new group (and optionally, a new user) for the product component. The
user and group names must not contain spaces.
Note:
v The group must be associated with the user name that you enter in the User
field.
v You do not need to exit the installation program to create a user or group. When
you are finished, enter the new name in the User or Group field.
v To work with users and groups, you can use the admintool on Solaris, smit on
AIX, linuxconf on Linux, or any text editor such as VI.
BWMCR8272E: The user is not root. This installation can only
be run as the root user.
Explanation
This message is displayed if you did not log on as the root user before starting the
installation or uninstallation program.
Operator response
Click Cancel to exit the (un)installation program. Log on as the root user and
restart the (un)installation.
BWMCR8273E: You must have Administrator privileges to
install or uninstall this software.
Explanation
This message is displayed if you did not log on as a user with administrator
privileges before starting the installation or uninstallation program.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
47
Operator response
Click Cancel to exit the (un)installation program. Log on as an Administrator user
and restart the (un)installation.
BWMCR8274E: The installation program failed to initialize the
installation context. See the trace log for more details.
Explanation
The installation program failed to initialize. It failed to read in the prerequisites
XML file or a system error occurred.
Operator response
Consult the trace log for more information about the cause of the failure.
BWMCR8275E: IBM Tivoli Composite Application Manager
does not support the specified platform. See the trace log for
more details.
Explanation
See the IBM Tivoli Composite Application Manager Installation Guide for details
on supported platforms.
Operator response
Upgrade the operating system to a supported version, reinstall the operating
system to a supported version, or use a different computer with a supported
platform.
BWMCR8276E: Failed to run the bat file that configures the
management agent. The service might not have been created.
See the trace log for more details.
Explanation
The batch file that configures the management agent failed to run. As a result, the
agent service cannot be created.
Operator response
View the trace log to determine the problem. After correcting the issue, try the
installation again.
BWMCR8277E: Failed to run the bat file that removes the
management agent configuration. The service might not have
been removed. See the trace log for more details.
Explanation
The uninstallation of the agent did not complete successfully. View the trace file to
determine the cause of failure.
48
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
The agent might need to be cleaned up manually. Remove the agent service and all
files before reinstalling.
BWMCR8278E: Failed to run the script that configures the
management agent. The configuration might not have
completed. See the trace log for more details.
Explanation
A script that helps configure the management agent failed to run. As a result,
configuration is not complete.
Operator response
View the trace log to determine the problem. After correcting the issue, try the
installation again.
BWMCR8279E: Failed to run the script that removes the
management agent configuration. The configuration might not
have been removed. See the trace log for more details.
Explanation
The uninstallation of the agent did not complete successfully. View the trace file to
determine the cause of failure.
Operator response
The agent might need to be cleaned up manually. Stop the agent daemon and
remove any files before attempting to reinstall.
BWMCR8280E: Registration of the management agent failed.
Verify the management server information and connectivity.
Explanation
The agent installation program attempts to register the agent with the management
server information that you specified in the Management Server Information
window. This message is displayed if the agent cannot register with the
management server. Possible causes for this failure are that the management server
is down or that you specified incorrect information on the Management Server
Information window.
Operator response
v Check the trace log to determine the exact reason for the failure.
v Verify all of the information that you entered in the Management Server
Information window. For example, verify that you entered the user ID and
password of a user authorized to log on to the management server computer
that is specified in the Host Name field. Also check that the security information
(whether SSL-enabled or not) and port number are correct.
v Verify connectivity to the management server that you specified. Try logging on
to the management server from a browser on this computer.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
49
BWMCR8281E: The management agent cannot unregister from
the management server. *
Explanation
The uninstallation program cannot unregister the agent from the management
server. Possible causes for this failure are that information is incorrect in the
endpoint properties, the management server is down, the management server
cannot be contacted, or the management server was uninstalled.
The uninstall completes but management agent does not unregister from the
management server.
Operator response
If the management server was uninstalled, no action is needed.
If management server is still in use, archive the management agent that failed to
unregister so that it does not display in the user interface. To archive the
management agent take the following action:
On the console and go to System Administration->Work With Agents, select the
agent that was uninstalled and choose Archive from the pull down menu.
BWMCR8282E: An error occurred configuring the
management server.
Explanation
The configuration of the management server did not complete successfully.
Operator response
View the trace log to determine the problem. After correcting the issue, try the
installation again.
BWMCR8283E: Failed to completely remove configuration files
from the management server.
Explanation
The uninstallation of the management server did not complete successfully. A
probable cause for this failure is that a file is locked by another process.
Operator response
If you cannot find the process, reboot the computer to stop the process. View the
trace file to determine the cause of failure. Follow steps in the documentation to
make sure that the management server is completely removed from the computer
before attempting to reinstall.
50
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
BWMCR8284E: The software that you are trying to install is
already installed.
Explanation
The installation program encountered a file that is used for inventory information
on this computer. This file contained text that indicates this software is already
installed on this computer. The Prereqs.xml file on the CD identifies the file names
being searched on the different operating systems and the text within them that is
used to indicate that the software is already installed.
Operator response
Run the uninstallation program to uninstall this software or remove the text from
the inventory file to force the installation to proceed.
BWMCR8285E: A required file that is part of prerequisite was
not found:
Explanation
The installation program was not able to locate the file that is needed to examine
the system for the installed applications.
Operator response
Create the file or install the program that created the file.
BWMCR8286E: There was a prerequisite failure. An invalid
registry key was found.
Explanation
The installation program encountered a key in the registry that is part of an
application that violates the requirements of this product.
Operator response
Remove the registry key or uninstall the program that created the registry key.
BWMCR8287E: There was a prerequisite failure. A required
registry key was not found.
Explanation
The installation program expected to find a required key in the registry.
Operator response
Add the required registry key or reinstall the program that creates the registry key.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
51
BWMCR8288E: Due to prerequisite failure, this installation
cannot continue.
Explanation
The installation program encountered violations of the prerequisite configuration
for this product.
Operator response
Review and correct the prerequisite conditions before you attempt to install again.
BWMCR8289E: There was an error during connecting to the
database:
Explanation
The installation program failed to make an initial connection to the database that
you specified.
Operator response
Ensure that the database is running and accessible in the network. Confirm that
the values you entered for the database are correct before you continue the
installation.
BWMCR8290E: There was an error during executing a
database query:
Explanation
The installation program failed to make an initial query to the database you
specified.
Operator response
View the trace log to determine the cause of the problem.
BWMCR8291E: There was an error during processing the
result set from a database query:
Explanation
The installation program encountered an error while it processed the result set
from the specified database.
Operator response
View the trace log to determine the cause of the problem.
BWMCR8292E: The specified node name is not correct.
Explanation
The node name must match the node name specified in the local installation of
WebSphere Application Server. Locate the node name by opening the WebSphere
Administrative Console and clicking Environment -->Manage WebSphere Variables.
52
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
The node name is listed in the WebSphere Variable window.
Operator response
Type the correct node name and try again.
BWMCR8293E: The specified cell name is not correct.
Explanation
The node name must match the cell name specified in the local installation files of
WebSphere Application Server. You can locate the cell name by opening the
WebSphere Administrative Console and clicking Environment -->Manage
WebSphere Variables. The cell name is listed in the WebSphere Variable window.
Operator response
Type the correct cell name and try again.
BWMCR8294E: The specified server name is not correct.
Explanation
The server name must match the cell name specified in the local installation files of
the WebSphere Application Server. Locate the server name by opening the
WebSphere Administrative Console and clicking Environment -->Manage
WebSphere Variables. The server name is listed in the WebSphere Variable window.
Operator response
Type the correct cell name and try again.
BWMCR8295E: The install program cannot contact WebSphere
Application Server.
Explanation
WebSphere Application Server cannot be contacted using the specified port. The
WebSphere Application Server might not be running, the specified port number
may be incorrect or Application Server might have global security enabled.
Operator response
Verify that the WebSphere Application Server is running, the SOAP port number
specified corresponds to the port in the configuration of the Application Server,
Select the checkbox if WebSphere Global Security is enabled and try again.
BWMCR8296E: The data entered does not match the data
specified in the local installation files of the WebSphere
Application Server.
Explanation
The node name, cell name, server name, and port name must match the node
name, cell name, server name, and port name specified in the local installation of
the WebSphere Application Server.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
53
Operator response
Type the correct node name, cell name, server name, and port name, and try again.
BWMCR8297E: The URL format is incorrect.
Explanation
The URL of the WebSphere caching proxy must be specified in the following
format:
protocol://hostname:portnumber
where:
v protocol has one of the following values:
– http if the WCP is not a secure server
– https if the WCP is a secure server
v hostname is the fully qualified name of the host computer for the WCP
v (optional)portnumber is a valid port number that the WCP can use to
communicate with the 5.2 management server.
Example: https://imsserver.it.company.com:443
Operator response
Type the URL of the WCP in the correct format.
BWMCR8298E: The Store and Forward Agent failed to
configure.
Explanation
The Store and Forward Service configuration failed during installation.
Operator response
View the trace log for details indicating why the Store and Forward Service
configuration failed. Correct any problems indicated in the trace log and try the
installation again.
BWMCR8299E: The batch file to remove the Store and
Forward Agent configuration failed.
Explanation
The Store and Forward Service was not created as a result of the batch file failure.
Operator response
View the trace log for details indicating why the Store and Forward Service
configuration failed. You might need to manually remove parts of the Store and
Forward Agent.
54
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
BWMCR8300E: The db2java.zip file was not found in the
specified JDBC path.
Explanation
The specified JDBC path must be a directory containing the db2java.zip file.
Operator response
Specify the correct JDBC path. The file is located in the basdir\sqllib\java directory
of the DB2 client on Windows or the DB2 instance user home directory on UNIX.
BWMCR8301E: The user already exists.
Explanation
The name that you entered in the User field already exists, but you specified that
you want to create a new user with this name.
Operator response
Take one of the following actions:
v Type a valid name of a new user in the User field. The user name must not
contain spaces.
v Delete this user from the computer.
Note:
v You do not need to exit the installation program to delete a user or group. When
you are finished, enter the new user name in the User field.
v To work with users and groups, you can use the admintool on Solaris, smit on
AIX, linuxconf on Linux.
BWMCR8302E: The uid is already defined on this computer.
Explanation
The installation program found that the value you entered in the Uid field already
exists in the /etc/passwd file. On UNIX-based systems, the uid or Unique
Identifier must be unique for each user that is defined in the /etc/passwd file.
Operator response
Take one of the following actions:
v Type a valid UID that is not already being used Uid field.
v Use an existing user rather than trying to create a new user.
v Delete the user using this UID value from the /etc/passwd file
v Change the user's line in the /etc/passwd file so that it uses a unique UID
value.
Note:
v You do not need to exit the installation program to create a user or group. When
you are finished, enter the UID value in the Uid field.
v To work with users and groups, you can use the admintool on Solaris, smit on
AIX, linuxconf on Linux, or any text editor such as VI.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
55
BWMCR8303E: The specified path is not a fully qualified UNIX
path.
Explanation
The installation program discovered that you did not specify the correct file or
directory.
Operator response
Type in a fully qualified UNIX path and try the installation again.
BWMCR8304E: The specified path is not a fully qualified UNIX
path.
Explanation
The installation program discovered that the path specified for the file or directory
includes more than the allowed maximum characters.
Operator response
Specify the fully qualified UNIX path with less than 1024 characters in length.
BWMCR8305E: The specified path is not a fully qualified UNIX
path.
Explanation
The value you specified for the file or directory field is not fully qualified because
it did not begin with a slash.
Operator response
Specify a fully qualified UNIX path that begins with a slash.
BWMCR8306E: An error occurred because a required field
was not populated.
Explanation
All fields must be populated.
Operator response
Type data into all fields and try again.
BWMCR8307E: The specified home directory for the user was
not found.
Explanation
The home directory for an existing user must be specified in the /etc/password
file on UNIX systems so that the installation program can identify the existing user.
56
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
Correct the /etc/passwd file, choose another existing user, or create a new user
during this installation.
BWMCR8308E: No directory path is provided for disk space
check.
Explanation
The directory path required for a disk space check has not been set.
Operator response
Ensure that a valid directory path is provided.
BWMCR8309E: An invalid directory path was provided for a
disk space check
Explanation
The path name supplied for a disk space check does not exist or is not a directory.
Operator response
Ensure that a valid directory path is provided.
BWMCR8310E: Invalid minimum disk space value provided for
disk space check
Explanation
The minimum disk space value required for a disk space check was not set or is
invalid. The value must be less than or equal to 1 megabyte.
Operator response
Ensure that a valid minimum disk space is provided.
BWMCR8311E: Directory path fails minimum free disk space
check
Explanation
The provided directory path did not have the minimum specified free disk space.
Operator response
Provide a directory path free disk space that meets the specified minimum. Refer
to the IBM Tivoli Composite Application Manager for WebSphere and J2EE
Installation Guide for the disk space requirements for your system.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
57
BWMCR8312E: The DB2 environment variable must be set
prior to running the installation if an existing DB2 server is
used.
Explanation
When the DB2 client software is installed, certain environment variables are active,
such as db2instance.
Operator response
Cancel to exit the installation and make sure you can connect properly before
re-running the installation. On UNIX, source the db2profile of the DB2 instance
user. On Windows, install the DB2 client software. On all operating systems, the
database must be cataloged properly before the DB2 client can be used.
If this machine has a DB2 server already installed, bring up the DB2 command-line
environment and make sure you can list the database directory. The database and
bufferpool must already exist.
If this machine accesses a remote db2 server, it must have the DB2 client software
installed on it and the remote database must be properly cataloged. Further, if this
is a UNIX operating system, the command, . db2profile, must be run before
running the installation, where db2profile refers to a file in the sqllib subdirectory
of the db2 instance user. For further instructions on how to perform these steps
consult the Problem Determination Guide.
BWMCR8313E: Invalid db2admin home directory path
Explanation
The specified db2admin home directory path is invalid.
Operator response
Provide a valid db2admin home directory path.
BWMCR8314E: The db2admin home directory path fails the
minimum free disk space check.
Explanation
The specified db2admin home directory path did not have the required minimum
free disk space.
Operator response
Provide a directory path whose free disk space meets the specified minimum.
Refer to the IBM Tivoli Composite Application Manager for WebSphere and J2EE
Installation Guide for the disk space requirements for your computer.
BWMCR8315E: Invalid db2inst home directory path
Explanation
The specified db2inst home directory path is invalid.
58
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
Provide a valid directory path.
BWMCR8316E: The db2inst home directory path fails the
required minimum free disk space check.
Explanation
The specified dbinst home directory path did not have the required minimum free
disk space.
Operator response
Provide a directory path with the required minimum free disk space. Refer to the
IBM Tivoli Composite Application Manager for WebSphere and J2EE Installation
Guide for the disk space requirements for your system.
BWMCR8317E: The test connection to the management server
failed. Unable to contact the management server. Management
agent installation cannot continue until the connection is
established.
Explanation
Possible reasons that the management server connection is broken include the
following scenarios:
o The management server is down.
o The management server information was entered incorrectly (incorrect hostname,
port, user name or password).
o The user name entered does not have agent privileges on the management
server.
o The management server was not restarted after a new installation.
Operator response
To resolve this error, the user running the installation can perform any of the
following actions:
o Verify that the management server is running. If the management server is not
running, start it. IBM Tivoli Composite Application Manager starts automatically
when WebSphere Application Server is restarted. Or, from the WebSphere
Application Server admin console, you can go to Applications->Enterprise
Applications, select TMTP and click Start. A green arrow displays next to the
application if it is running correctly.
o Verify whether the information entered matches the management server
information (hostname, port, security enabled, user name or password).
o Verify that the user specified has agent roles on the management server.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
59
o If the management server was installed without restarting WebSphere
Application Server afterwards, the management agent cannot connect to the
management server. Make sure that WebSphere Application Server was restarted.
Before restarting the WebSphere Application Server, make sure the db2
environment is set up. On UNIX, source the db2profile of the DB2 instance user.
o Use a different management server.
BWMCR8319E: The WCP (WebSphere Caching Proxy) cannot
be installed. The system does not meet WCP installation
requirements.
Explanation
This message is displayed if your system does not meet the requirements to install
WCP.
Operator response
Click Cancel to exit the installation program. Install the patches required by the
WCP installation and restart the installation. The required WCP patches can be
verified by manually running the checkPatchLevbel.sh shell script that is supplied
on the installation media.
BWMCR8321E: The DB2 installation failed. Install DB2 using
the DB2 setup program and run this installation again using
an existing database.
Explanation
This message is displayed if there is an error while running the embedded DB2
installation.
Operator response
Examine the DB2 logs and determine why the installation failed. Using the DB2
media, install DB2. Follow the steps for installing IBM Tivoli Composite
Application Manager using an existing database. Create a database and bufferpool,
and re-run the installation.
BWMCR8322E: The installation failed to create the database
and bufferpool. You can create the bufferpool and database
before continuing or cancel the installation.
Explanation
This message is displayed if the creation of the database or bufferpool fails after an
embedded db2 installation.
Operator response
You must create the database and bufferpool before continuing. The database must
be named tmtp. Examine the DB2 logs and determine why the database creation
failed. Follow the steps for using an existing database that explain how to create a
database and bufferpool.
60
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
BWMCR8323E: The installation failed while installing the
WebSphere Application Server.
Explanation
This message is displayed if there is an error during the embedded WebSphere
installation.
Operator response
Examine the WebSphere logs and determine why the installation failed. Use the
WebSphere media to install the WebSphere Application Server manually and restart
this installation using the steps for an existing the WebSphere Application Server.
BWMCR8324E: The installation failed while installing the
WebSphere Application Server Fixpack.
Explanation
This message is displayed if there is an error during the installation of WebSphere
Fixpack 5.1.1.
Operator response
Examine the WebSphere logs and determine why the installation failed. Use the
WebSphere media to install the fixpack manually and restart the installation
program using the steps for an existing WebSphere Application Server.
BWMCR8325E: The installation failed while starting the
WebSphere Application Server.
Explanation
This message is displayed if there is an error during the embedded WebSphere
Application Server installation while starting the WebSphere Application Server.
Operator response
Examine the WebSphere Application Server logs to determine why the installation
failed. Use the WebSphere Application Server media to install it manually and
restart this installation using the steps for an existing WebSphere Application
Server.
BWMCR8326E: The WebSphere Application Server installation
failed while adding IHS to the existing WebSphere server.
Explanation
This message is displayed if there is an error during the embedded installation of
IHS.
Operator response
Examine the WebSphere logs to determine why the installation failed. Use the
WebSphere media to install it manually and restart the installation program.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
61
BWMCR8327E: The installation failed because the version and
release of the operating system is below the supported level.
This system is version and release:
Explanation
This message is displayed if there is an error during the prerequisite checking of
the installation initialization.
Operator response
Upgrade or reinstall the operating system to a supported version.
BWMCR8328E: The installation failed because the version and
release of the operating system is not a supported level. This
system is version and release:
Explanation
This message is displayed if there is an error during the prerequisite checking of
the installation initialization.
Operator response
Upgrade or reinstall the operating system to a supported version.
BWMCR8329E: The installation failed because the service
pack level of the operating system is below the supported
level. This system is service pack level:
Explanation
This message is displayed if there is an error during the prerequisite checking of
the installation initialization.
Operator response
Upgrade or reinstall the operating system to a supported version.
BWMCR8330E: The installation failed because the
maintenance level of the operating system is below the
supported level. This system is maintenance level:
Explanation
This message is displayed if there is an error during the prerequisite checking of
the installation initialization.
Operator response
Upgrade or reinstall the operating system to a supported maintenance level.
62
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
BWMCR8331E: The installation failed because the host name
cannot be resolved.
Explanation
This message is displayed if there is an error during the prerequisite checking of
the installation initialization.
Operator response
Inspect and repair the hosts file or other method of host name resolution.
BWMCR8332E: The user does not have the required authority
to create a schema in this database.
Explanation
This message is normally displayed if the user does not have DB2 SYSADM or
SYSCTRL authority.
Operator response
Ensure that the user has DB2 SYSADM or SYSCTRL authority
BWMCR8333E: The IP address of the local system was
detected to be 127.0.0.1, which is not allowed. Verify the hosts
file.
Explanation
The installation program cannot continue because the IP address of local system
detected was 127.0.0.1. The IP address must be a valid address.
Operator response
Check the hosts file to make sure that it has a valid IP address and host name. On
Windows operating systems, this file is %SystemRoot%/system32/drivers/etc/
hosts and on UNIX operating systems, it is /etc/hosts. Edit this file if necessary
and retry the installation.
BWMCR8334E: The path specified for the {0} CD is invalid:
Explanation
The location specified an incorrect location for the CD.
Operator response
Restart the installation program using the correct path to the CD-ROM drive.
BWMCR8335E: Unable to grant the user Windows user rights
necessary for WebSphere Application Server.
Explanation
The user needs Act as part of the operating system and Logon as a service user
right to run WebSphere Application Server. The user did not have one or both of
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
63
these rights and the installation was unable to grant these user rights to the user.
The installation cannot continue.
Operator response
Grant these rights to the user and run the installation again.
BWMCR8336E: An error occurred while removing the
database tables. The tables must be removed manually.
Explanation
An error occurred while removing the database tables. Examine the installation
trace log for more detailed information
Operator response
Manually remove the database tables using the utilities provided with the database
BWMCR8337E: The required BUFFPOOL32K database
bufferpool does not exist. You can create the bufferpool and
database before continuing or cancel the installation program.
Explanation
The BUFFPOOL32K database bufferpool is required but has not been created by
the installation program.
Operator response
Follow the instructions in the IBM Tivoli Composite Application Manager for
WebSphere and J2EE Installation Guide to create the bufferpool. Continue the
installation.
BWMCR8338E: Kernel parameters are not at appropriate
levels for the installation of DB2. Update the settings and
reboot the system before rerunning this installation.
Explanation
DB2 requires that specific kernel parameters be updated. After updating the
settings, reboot and rerun this installation.
Operator response
1. Update the required kernel parameters as documented in the Problem
Determination Guide. These settings are located in /etc/system on a solaris
system. The minimum values are as follows: \n
v msgsys:msginfo_msgmax = 65535
v msgsys:msginfo_msgmnb = 65535
v msgsys:msginfo_msgmap = 1794
v msgsys:msginfo_msgmni = 1792
v msgsys:msginfo_msgssz = 32
v msgsys:msginfo_msgtql = 1792
64
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
v
v
v
v
v
msgsys:msginfo_msgseg = 32767
shmsys:shminfo_shmmax = 966367641
shmsys:shminfo_shmseg = 240
shmsys:shminfo_shmmni = 2048
semsys:seminfo_semmni = 2048
v
v
v
v
semsys:seminfo_semmap = 2050
semsys:seminfo_semmns = 4300
semsys:seminfo_semmnu = 2048
semsys:seminfo_semume = 240
2. Reboot the system for these settings to take effect.
3. Rerun the management server installation.
BWMCR8339E: The DB2 user ID is not valid.
Explanation
The DB2 user ID does not satisfy the required set of conditions.
Operator response
These are the rules for valid DB2 user IDs:
v Can contain 1 to 8 characters.
v Can include letters, numbers, @, #, $
v Cannot begin with IBM, SYS, SQL, or a number
v Cannot be a DB2 reserved word (USERS, ADMINS, GUESTS, PUBLIC or
LOCAL)
v Cannot end with a $
v Cannot include accented characters
BWMCR8340E: The DB2 user password is not valid.
Explanation
The DB2 user password does not satisfy the required set of conditions.
Operator response
These are the rules for valid DB2 user passwords:
v Can contain 1 to 8 characters.
v Cannot have an expiry date or usage restrictions.
v Can include A through Z, a through z, 0 through 9, @, #, $, or &
v Cannot begin with a number or &
BWMCR8341E: There was a prerequisite failure. Internet
Explorer 4.01 Service Pack 2 is required to complete the
installation.
Explanation
The installation program failed to discover a required version of Internet Explorer.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
65
Operator response
Install Internet Explorer 4.01 Service Pack 2 or higher.
BWMCR8342E: The selected destination directory already has
an uninstall subdirectory, _uninst53. Remove this subdirectory
or install to another directory.
Explanation
An existing subdirectory of _uninst53 indicates there was a previous installation of
the product.
Operator response
Remove the directory or select a new destination directory.
BWMCR8343E: The specified UID for the user was not found.
Explanation
The UID for an existing user must be specified in the /etc/password file on UNIX
systems so that the installation program can identify the existing user.
Operator response
Correct the /etc/passwd file, choose another existing user, or create a new user
during this installation.
BWMCR8344E: The specified license key contained
non-numeric characters or otherwise was not a valid long
integer.
Explanation
The license key must be a 16-digit number with no punctuation, non-numeric
characters or spaces.
Operator response
Correct the license key or choose another license key.
BWMCR8345E: No more licenses are available on the server.
Explanation
A license key that is valid for a finite number of licenses is specified in
server.properties when the management server is installed. The maximum number
of endpoints has already been installed against that server.
Operator response
Change the license key to one that allows another endpoint, or uninstall one of the
existing endpoints.
66
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
BWMCR8346E: WebSphere 5.1 is required to complete the
installation
Explanation
The installation program did not discover a required version of WebSphere.
Operator response
Install WebSphere 5.1 or higher and rerun the installation.
BWMCR8347E: The IBM Tivoli Composite Application Manager
for Response Time Tracking Fix pack 5.2-WTP-FP01 does not
support the specified platform. See the trace log for more
details.
Explanation
See the IBM Tivoli Composite Application Manager for WebSphere and J2EE
prerequisite page for details on supported platforms.
Operator response
Perform this upgrade on a computer with a supported operating system. If your
computer is a platform that was added in this release, run the full installation
rather than the upgrade. See the IBM Tivoli Composite Application Manager for
WebSphere and J2EE Installation Guide for more details.
BWMCR8348E: This IBM Tivoli Composite Application
Manager for Response Time Tracking installation is supported
on the Windows 2003 platform only. See the trace log for more
details.
Explanation
The supported platform is Windows 2003 only. This installation does not support
UNIX or other Windows platforms.
Operator response
If this is a supported IBM Tivoli Composite Application Manager for Response
Time Tracking, Version 5.2 platform, follow the upgrade procedures in the Readme
for the 5.2-WTP-FP01 fix pack.
BWMCR8349E: The selected destination directory already has
an uninstallation subdirectory, _uninst5201. Uninstall the fix
pack and remove this subdirectory before reinstalling.
Explanation
An existing subdirectory of _uninst5201 indicates that there was a previous
installation of the product.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
67
Operator response
Uninstall the fix pack and remove the directory.
BWMCR8350E: The IBM Tivoli Composite Application Manager
for WebSphere and J2EE upgrade must be installed on a
machine with a previous version of the product.
Explanation
The installation program did not detect an installation of IBM Tivoli Composite
Application Manager for WebSphere and J2EE. The upgrade must be installed on a
machine with a previous version of the product.
Operator response
Install a supported version of IBM Tivoli Composite Application Manager for
WebSphere and J2EE and then install the product upgrade.
BWMCR8351E: The IBM Tivoli Composite Application Manager
for Response Time Tracking upgrade must be installed on a
machine with a previous version of the product. A valid
installation was not found in the directory that was specified.
Specify the base installation directory of a valid management
server that contains a config/db.properties file.
Explanation
The installation program was unable to find the BASEDIR/config/db.properties
file. The upgrade installation must be run on a machine with a previous version of
the product in the specified installation directory.
Operator response
Review and correct the destination directory.
BWMCR8352E: The management server configuration did not
complete successfully during the fix pack installation.
Explanation
This error can occur if another process locks required files. For example, if
WebSphere Application Server does not shutdown correctly during fix pack
installation, required files might remain locked. This error can also occur if the
installation program encounters a problem while trying to update the database
tables in the database.
Operator response
To resolve this error, the user performing the installation can review the installation
and management server log files for more information about the failure. Access
these log files in the common logging directory. The installation log file is named
trace-install.log. The management server log file is named trace-ms.log. After
correcting the issue, you must run the installation again.
68
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
BWMCR8353E: The management server configuration did not
remove properly during the fix pack uninstallation and might
not have been completely removed.
Explanation
This error can occur if another process locks the required files so that the files
cannot be replaced and rolled back from the backup copy. For example, if
WebSphere Application Server does not shutdown correctly during fix pack
uninstallation, required files can remain locked. This error can also occur while
trying to roll back the database tables in the database.
Operator response
To resolve this error, the user performing the fix pack uninstallation must stop the
process that is locking the files. If you cannot find the process that is locking the
files, reboot the computer to stop the process. Review the installation and
management server trace log files for more information about the failure. Access
these log files in the common logging directory. The installation log file is named
trace-install.log. The management server log file is named trace-ms.log. Follow the
steps in the documentation to verify that the management server is completely
removed from the computer before attempting to reinstall.
BWMCR8354E: The management agent configuration did not
complete successfully during the fix pack installation.
Explanation
This error occurs if the management agent encounters a problem during the
configuration process.
Operator response
> Review the installation trace log file, trace-install.log, for more information about
the failure. The log file is located in the common logging directory. To resolve this
error, shut down the management agent manually and reinstall the fix pack.
BWMCR8355E: An error occurred while trying to stop the
management agent.
Explanation
This error occurs if the management agent can not be stopped.
Operator response
Verify that the management agent can be stopped from the Services panel.
To resolve this error, shut down the management agent manually and reinstall the
fix pack.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
69
BWMCR8356E: Updated management agents exist. All
management agents must roll back to Version 5.2 before the
management server fix pack can roll back to the Version 5.2
level.
Explanation
The fix pack uninstallation prerequisites failed because an updated management
agent was detected in the database. All management agents must roll back to
Version 5.2 before you can roll the management server fix pack back to the Version
5.2 level.
Operator response
To resolve this error, the user performing the installation or uninstallation must roll
back all management agents to the 5.2 level before uninstalling the fix pack from
the management server. To determine if an updated management agent exists,
perform one of the following procedures. From the GUI, go to System
Administration->Work with Agent Updates->Show Agents with Updates Installed
to determine if any updated management agents display. Or, check for a listing of
updated management agents in the version1 column in the ep table in the
database. If updated management agents display in either the GUI or ep database,
roll back the management agents by performing the following steps: Go to System
Administration->Work with Agent Updates->Show Agents with Updates Installed,
select the management agent that you want to roll back, click the drop-down
menu, and choose Uninstall Update. When all management agents are rolled back,
uninstall the fix pack on the management server.
BWMCR8357E: Kernel parameters are not at appropriate
levels for the installation of DB2. Update the settings and
reboot the system before rerunning this installation.
Explanation
DB2 requires that specific kernel parameters be updated. After updating the
settings, reboot and rerun this installation.
Operator response
1. Update the required kernel parameters as documented in the Problem
Determination Guide. These settings are located in /stand/system on an HP-UX
system. The minimum values are as follows: \n
v MIN_MAXUPRC = 512;
v MIN_MAXFILES = 256;
v
v
v
v
v
v
v
v
v
70
MIN_NPROC = 1024;
MIN_NFLOCKS = 8192;
MIN_NINODE = 2048;
MIN_NFILE = 8192;
MIN_MSGSEG = 32767;
MIN_MSGMNB = 65535;
MIN_MSGMAX = 65535;
MIN_MSGTQL = 256;
MIN_MSGMAP = 258;
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
v
v
v
v
v
MIN_MSGMNI = 256;
MIN_MSGSSZ = 16;
MIN_SEMMNI = 512;
MIN_SEMMAP = 514;
MIN_SEMMNS = 1024;
v
v
v
v
MIN_SEMMNU = 1024;
MIN_SHMMAX = 268435456;
MIN_SHMSEG = 16;
MIN_SHMMNI = 300;
2. Reboot the system for these settings to take effect.
3. Rerun the management server installation.
BWMCR8358E: The WebSphere Application Server, Version 6.0
installation image that was specified was not valid.
Explanation
The specified directory does not contain installation images for WebSphere
Application Server, Version 6.0 or the images in the specified directory do not have
the correct permissions. The license.txt file in the specified directory either does not
exist or does not contain the following string: IBM WEBSPHERE APPLICATION
SERVER, v. 6.0.
Operator response
The person performing the installation must locate a directory with valid
WebSphere Application Server, Version 6.0 installation images and specify that
directory. Or, the user can click the check box to perform an embedded installation
using CDs. Alternatively, the user can manually install WebSphere Application
Server, Version 6.0 and then rerun the management server installation.
BWMCR8359E: The DB2, Version 8.2 installation image that
was specified was not valid.
Explanation
The specified directory does not contain installation images for DB2, Version 8.2 or
the images in the specified directory do not have the correct permissions.
Operator response
Locate a directory with valid DB2, Version 8.2 installation images and specify that
directory or click the check box to perform an embedded installation using CDs.
Alternatively, manually install DB2 or use an existing DB2 or Oracle database and
rerun the management server installation.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
71
BWMCR8360E: The WebSphere Caching Proxy, Version 6.0
installation image that was specified was not valid.
Explanation
The specified directory does not contain installation images for WebSphere Caching
Proxy, Version 6.0. The launchpad.jar file in the specified directory does not exist.
Operator response
Locate a directory with valid WebSphere Caching Proxy, Version 6.0 installation
images and specify that directory or click the check box to perform an embedded
installation using CDs. Alternatively, manually install WebSphere Caching Proxy,
Version 5.1 or 6.0 and then rerun the Store and Forward agent installation.
BWMCR8361E: The username and password specified cannot
be used to contact the WebSphere Application Server.
Explanation
WebSphere Application Server cannot be contacted using the specified username
and password. The WebSphere Application Server might not be running or the
specified username or password is incorrect.
Operator response
Verify that the WebSphere Application Server is running, type in the correct
username and password, and try again.
BWMCR8362E: The user does not have the appropriate rights
to run the management server.
Explanation
The username given does not have the appropriate rights to run the Managing
Server.
Operator response
Verify that the user has the Act as part of the Operating System and Log on as
a Service rights on the local system.
If the message was displayed during the Managing Server installation process, also
verify that the user is a member of the domain administrative group and has the
Act as part of the operating system privilege in the Domain security policy on
the domain controller.
After this, try again.
BWMCR8363E: Security is not enabled in WebSphere. Clear
the check box labeled WebSphere Security enabled and try
again.
Explanation
The WebSphere Application Server is not configured with security enabled.
72
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
Clear the check box for WebSphere Application Server security enabled and try
again.
BWMCR8364E: The zos.properties file was not found in the
/etc/tmtp/MA/config directory.
Explanation
The configuration of the management agent cannot continue until the
zos.properties file is in the etc/tmtp/MA/config directory and contains customized
information details such as host and user names.
Operator response
To resolve this error, copy the zos.properties file from the config1 directory in the
product installation directory. Customize the file and run the configuration
program again.
BWMCR8365E: The management agent failed to properly
configure. See the trace log for details.
Explanation
The management agent configuration failed.
Operator response
To resolve this error on z/OS systems, review the trace log located in the
/var/ibm/tivoli/common/BWM/logs directory for an error or exceptions. Correct
the error and rerun the configuration program.
BWMCR8366E: This product has already been installed on
this system.
Explanation
Product already installed.
Operator response
Uninstall the current product from the system, and then try running the
installation program again.
BWMCR8367E: The management server upgrade configuration
did not complete successfully.
Explanation
This error can occur if WebSphere Application Server migration has not been
completed successfully. For example, if WebSphere Application Server 6.0 cannot
be stopped and started correctly. This error can also occur if the installation
program encounters a problem while trying to update the database tables in the
database. A rollback of the TMTP application and database is performed
automatically.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
73
Operator response
To resolve this error, the user performing the installation can review the installation
and management server log files for more information about the failure. Access
these log files in the common logging directory. The installation log file is named
trace-install.log. The management server log file is named trace-ms.log. WebSphere
Application Server 5.1 is backed up before upgrade and restored as part of
rollback. Verify WebSphere Application Server 5.1 is operational. If the old TMTP
application is running, try upgrade again. If not, restore WebSphere Application
Server 5.1 manually from was51_backup.zip in WebSphere Application Server 5.1
directory, this file is created as part of WebSphere Application Server migration
process. Start WebSphere Application Server 5.1 and rerun the upgrade again.
BWMCR8369E: An installed IBM Tivoli Monitoring for
Transaction Performance, Version 5.2 Store and Forward
Agent was not detected on this machine.
Explanation
This upgrade can only be installed on a machine on which a IBM Tivoli
Monitoring for Transaction Performance, Version 5.2 Store and Forward Agent is
installed.
Operator response
Install the IBM Tivoli Monitoring for Transaction Performance, Version 5.2 Store
and Forward Agent before attempting this upgrade, or install IBM Tivoli
Composite Application Manager for WebSphere and J2EE, Version 6.1.
BWMCR8370E: To perform the IBM Tivoli Composite
Application Manager for Response Time Tracking, Version 6.1
Store and Forward Agent upgrade, the WebSphere Edge
Component Server, Version 5.0 must be uninstalled.
Explanation
This product requires WebSphere Edge Component Server, Version 5.1 or Version
6.0.
Operator response
Uninstall the current WebSphere Edge Component Server, Version 5.0 from the
system.
BWMCR8371E: A version of WebSphere Edge Component
Server has been detected that is not supported for this
release. Only WebSphere Edge Component Server, Versions
5.1 and above are supported.
Explanation
Only WebSphere Edge Component Server 5.1 and above are supported in this
release.
74
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
Uninstall the old version of WebSphere Edge Component Server from this
machine.
BWMCR8372E: WebSphere Application Server 6.0 migration
failed and the upgrade cannot continue.
Explanation
As part of WebSphere Application Server 6.0 migration, the previous WebSphere
Application Server is backed up first and then WebSphere Application Server 6.0 is
installed. One of these steps failed to run successfully.
Operator response
To resolve this error, analyze the trace-install.log, correct the error, and run the
program again. If same problem occurs again, try to run the WebSphere
Application Server 6.0 migration manually by launching the WebSphere
Application Server 6.0 installation program and follow the steps. Run the upgrade
again once WebSphere Application Server has been migrated.
BWMCR8373E: Upgrading configuration for management
agent failed.
Explanation
Automatically editing setupEnv.sh script failed.
Operator response
Verify setupEnv.sh script exists in local directory, /etc/tmtp/MA/config. If not,
rerun prepUpgradeCondig.sh and rerun configMa upgrade.
BWMCR8374E: The username and password validation failed.
Check to make sure the user name entered has agent
privileges on the management server.
Explanation
The username does not have agent role on the management server.
The username does not exist on management server.
The password entered is incorrect.
Operator response
Verify that the user exists and is mapped correctly to the agent role for the
nanagement server.
BWMCR8375E: The port is reserved:
Explanation
The application already uses the port that you specified in the Port Number field.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
75
Operator response
Specify a different port.
BWMCR8376E: The user you specify must have root
privileges.
Explanation
This message is displayed if you entered a user on the panel that does not have
root privileges.
Operator response
Enter a user that has root privileges.
BWMCR8377E: WebSphere failed to map roles to users.
Explanation
The WebSphere roles must be mapped to actual operating system users defined for
the host on which WebSphere is installed.
Operator response
Verify WebSphere log why user roles mapping failed, look for exceptions and
errors. Correct any errors found and rerun Install.
BWMCR8378E: The test connection to the management server
failed. Unable to contact the management server. The
management agent could not remove its registration from the
management server.
Explanation
The uninstallation program cannot remove the registration of the agent from the
management server. Possible causes for this failure are that information is incorrect
in the endpoint properties, the management server is down, the management
server cannot be contacted, or the management server was uninstalled.
The uninstall completes but management agent does not unregister from the
management server.
Operator response
If the management server was uninstalled, no action is needed.
If management server is still in use, archive the management agent that failed to
unregister so that it does not display in the user interface. To archive the
management agent take the following action:
On the console and go to System Administration->Work With Agents, select the
agent that was uninstalled and choose Archive from the pull down menu.
76
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
BWMCR8390E: Internet Explorer Enhanced Security is set on
high for the internet zone. This setting must be medium or
lower.
Explanation
Internet Explorer Enhanced Security for the internet zone must be set to a medium
level for the management agent to operate properly on Windows 2003. If the
Internet Explorer Enhanced Security is set at high, the management agent does not
show an online state after installation.
The Microsoft Windows Server 2003 Internet Explorer Enhanced Security
Configuration component (also known as Microsoft Internet Explorer hardening)
reduces a server's vulnerability to attacks from Web content by applying more
restrictive Internet Explorer security settings. As a result, Internet Explorer
Enhanced Security Configuration can prevent some Web sites from displaying
properly or performing as expected.
Operator response
Change the Internet zone security setting to medium from high. To change the
security setting take the following action:
1. Open Internet Explorer and select Internet Options from the Tools menu.
2. On the Security tab select Internet.
3. Move the slider bar at the bottom of the window to select a medium or lower
security level.
4. Click OK to apply the changes.
BWMCR8391E: Installation of the management server in a
Network Deployment environment is not supported with this
installation wizard. Refer to the ITCAMfRTT installation guide
for instructions for installing in a clustered environment.
Explanation
The WebSphere port validation threw an exception which can occur if installing
IBM Tivoli Composite Application Manager for Response Time Tracking against
WebSphere Network Deployment Manager. Refer to the ITCAMfRTT installation
guide for instructions for installing in a clustered environment. This installation
wizard will be cancelled.
Operator response
Refer to the ITCAMfRTT installation guide for instructions for installing in a
clustered environment.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
77
BWMCR8392E: The uninstallation of management agent
behaviors did not complete successfully. One or all of the
behaviors failed to uninstall. See the trace log for more
details.
Explanation
The uninstallation of the agent behaviors did not complete successfully. View the
trace file to determine the cause of failure.
Operator response
The agent might need to be cleaned up manually. See the Problem Petermination
Guide for assistance in cleaning up after a failed uninstall.
BWMCR8393E: The WebSphere Application Server, Version
5.1.1 fixpack image that was specified was not valid.
Explanation
Installation images for WebSphere Application Server Fixpack 5.1.1 were not found
in the specified directory or these installation images do not have the correct
permissions.
Operator response
Verify there is a subdirectory named fixpacks and that there is a jar file that begin
with was51_*. For example, was51_fp1_win.jar on Windows systems.
BWMCR8394E: The WebSphere Application Server, Version
5.1.1.2 fixpack image that was specified was not valid.
Explanation
The installation images for WebSphere Application Server Fixpack 5.1.1.2 were not
found in the specified directory or these installation images do not have the correct
permissions.
Operator response
Verify there is a sub directory named fixpacks and that there is a jar file that begin
with was511_*, for example, was511_cf2_win.jar on Windows systems.
BWMCR8395E: The installation failed while installing the
WebSphere Application Server Fixpack.
Explanation
This message is displayed if there is an error during the installation of WebSphere
Fixpack 5.1.1.2.
Operator response
Examine the WebSphere logs and determine why the installation failed. Use the
WebSphere media to install the fixpack manually and restart the installation using
the steps for an existing WebSphere Application Server.
78
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
BWMCR8396E: The installation did not find the specified
database.
Explanation
If you are using Oracle, adatabase must be created before the installation.
Operator response
Run the sample script manually to create the database and tables and run the
installation again.
BWMCR8397E: The post-installation apply script failed to
create links.
Explanation
The ARM shared libraries for IBM Tivoli Composite Application Manager for
Response Time Tracking are installed to /usr/lib/tmtp and links are created from
/usr/lib to /usr/lib/tmtp but failed to create the links.
Operator response
Remove the links in /usr/lib manually and rerun the script or create the links
manually using the ln -s command for all libraries in /usr/lib/tmtp.
BWMCR8398E: Management agents at an unsupported
version exist. All management agents must be upgraded to
Version 5.301 or 6.0 or higher before the management server
can be upgraded to the Version 6.1 level.
Explanation
The upgrade installation prerequisites failed because an outdated management
agent was detected in the database. All management agents must be upgraded to
Version 5.301 or 6.0 or higher before the management server can be upgraded to
the Version 6.1 level.
Operator response
To resolve this error, the user performing the upgrade must first upgrade all
management agents to a supported level before upgrading the management server.
To determine if an unsupported management agent exists, perform one of the
following procedures. From the GUI, go to System Administration->Work with
Agents-> to determine if any unsupported management agents display. Or, check
for a listing of unsupported management agents in the version1 column in the ep
table in the database. If unsupported management agents display in either the GUI
or ep database, upgrade the management agents by performing the following
steps: Go to System Administration->Work with Agent Updates->Show Agents
with Updates Installed, select the management agent that you want to update,
click the drop-down menu, and choose Install Update. When all management
agents are upgraded, upgrade the management server.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
79
BWMCR8399E: The WebSphere Application Server, Version
6.0.2 installation image that was specified was not valid.
Explanation
The specified directory does not contain installation images for WebSphere
Application Server, Version 6.0.2 or the images in the specified directory do not
have the correct permissions.
Operator response
The person performing the installation must locate a directory with valid
WebSphere Application Server, Refresh pack 6.0.2 installation images and specify
that directory. Or, the user can click the check box to perform an embedded
installation using CDs. Alternatively, the user can manually install WebSphere
Application Server, Version 6.0 and apply the refresh pack 6.0.2 then rerun the
management server installation.
BWMCR8400E: The db2profile file was not found in the
specified JDBC path.
Explanation
The specified JDBC path must be a db2 instance user's home directory containing
the db2profile file.
Operator response
Specify the correct JDBC path. The file is located in the DB2 instance user home
directory, db2inst/sqllib.
BWMCR8401E: Maximum number of concurrent agent installs
reached.
Explanation
Number of allowed cocurrent management agent installs was reached.
Operator response
Wait until later and try again.
BWMCR8402E: The user you are using does not have
permission to install agents on this server.
Explanation
The user used for Management Server does not have agent role.
Operator response
Make sure the user has agent role on Management Server and try again.
80
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
BWMCR8404E: This machine has configuration entries that
might prevent the DB2 installation from completing
successfully.
Explanation
Configuration entries were found that might prevent the DB2 installation from
completing successfully. These configuration entries might have been left over from
a previous DB2 installation that was not removed completely.
Operator response
Complete the following steps to clean up the configuration so that the DB2
installation can complete successfully.
v Check the /etc/services file for DB2 entries. Remove those entries if DB2 has
been uninstalled from this system.
v Check the default users of DB2 or user home. Remove those user and user
home.
v Check the default DB2 installation directory. Remove the directory.
BWMCR8405E: The password properties do not follow the
local operating system security policy.
Explanation
The password specified is invalid. All users must have passwords that follow the
security policies of the local machine. The most common problem is with the
minimum password length.
Operator response
Specify a password that adheres to the security policy on this machine. This policy
can be found by launching the Control Panel. Select Administrative Tools > Local
Security Policy > Account Policies > Password Policy. This will list the
requirements for passwords on this machine.
BWMCR8406E: The home directory for this user cannot be
accessed.
Explanation
An error occurred when trying to access the specified user's home directory.
Operator response
Verify that the home directory associated with the specified user in /etc/password
exists on this system and that the user has write permissions to this directory.
BWMCR8407E: The installation detected that this machine is
configured for a terminal server and is not in the installation
mode. The installation cannot continue.
Explanation
This installation must be run in installation mode.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
81
Operator response
Installation mode is activated by typing "change user /install" at a command
prompt. After the installation has completed, you must return to normal execution
mode by using the command "change user /execute."
BWMCR8500W: There are tables in the database.
Explanation
Installation will not create tables but use existing tables.
Operator response
Accept to use existing tables or drop the tables before proceeding.
BWMCR8501W: A self-signed certificate must be created in
the ManagementServer/IBMHTTPSERVER/(platform)/keys/
key.kdb file before you start the server. Refer to the
installation guide for instructions.
Explanation
To achieve minimal SSL connectivity, the installation program provides a key
database file that includes a self-signed certificate. The installation program cannot
find this file.
Operator response
To achieve minimal SSL connectivity, the product provides a self-signed certificate
in the required format, a key database file. Find the key.kdb key database file that
comes with the product. Search the temporary directory of the installation files or
search in the installation CDs. Copy and paste this file into the following path of
your product installation: ManagementServer/IBMHTTPSERVER/(platform)/keys. This
file enables connectivity in the product, but is appropriate for controlled
environments, not for production environments.
To achieve a level of security for a production environment, contact an
administrator of Web servers in your company to find out if the company has
third-party certificates or custom-made certificates that you can use for
communication in IBM Tivoli Composite Application Manager for Response Time
Tracking. See the installation guide for more information about modifying or
replacing the key database file to enhance security.
BWMCR8502W: The Windows user name must not exceed 20
characters.
Explanation
The specified user name is too long and cannot be created.
Operator response
Enter a user name that is less than 20 characters.
82
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
BWMCR8503W: The installation failed to modify the db2profile
script. Update the script after the installation completes
according to the instructions in the Problem Determination
guide.
Explanation
For local db2 8.2 server installations, you must add a variable and run a command
to run the db2profile file in the sqllib subdirectory of the instance users home
directory .
Operator response
Follow the instructions in the Problem Determination Guide to modify the file and
run the command after the installation completes. Failure to do this causes partial
data rollup to fail in some cases.
BWMCR8508W: The WebSphere Application Server could not
be started. Manually restart the WebSphere Application
Server.
Explanation
The WebSphere Application Server could not be started.
Operator response
Run the startServer.sh command on UNIX systems or the startServer.bat command
on Windows systems to start the WebSphere Application Server before after
completing the installation. The syntax is: startServer server1
BWMCR8509W: The WebSphere Application Server could not
be stopped. Ensure that the server is stopped before
continuing the installation.
Explanation
The WebSphere Application Server must be stopped before continuing the
installation.
Operator response
Run the stopServer.sh command on UNIX systems or the stopServer.bat command
on Windows systems to stop the WebSphere Application Server before continuing
the installation. The syntax is: stopServer server1 -username WAS user -password
WAS password
BWMCR8510W: The original installation files could not be
backed up.
Explanation
A problem was encountered when attempting to back up the original installation
files. Some files may not be backed up.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
83
Operator response
Before continuing, make a backup copy of the management server directory. This
enables you to revert to your previous state in the event of a problem.
BWMCR8511W: The original installation files could not be
restored.
Explanation
A problem was encountered when attempting to restore the original installation
files. Some files may not be restored. The product may be in an instable state.
Operator response
See the IBM Tivoli Composite Application Manager for Response Time Tracking
Problem Determination Guide for details on how to recover from a failed
installation.
BWMCR8512W: An error was received while copying the SSL
Key Store File.
Explanation
A file error was received during the copy of the SSL Key Store File.
Operator response
Manually copy the SSL files to the MA config directory. Edit the
endpoint.properties file endpoint.keystore property to point to the new location
before restarting the management agent.
BWMCR8513W: An error was received while copying the SSL
Key Store File and SSL Trust Store File.
Explanation
A file error was received during the copy of the SSL Key Store File and SSL Trust
Store File.
Operator response
Manually copy the SSL files to the Managing Server config directory. Edit the SSL
settings in WebSphere Application Server to point to the new Key Store and Trust
Store File locations before restarting WebSphere Application Server.
BWMCR8514W: There are no tables in the database.
Explanation
The database you chose must have tables for the upgrade of this product.
Operator response
Select a valid IBM Tivoli Composite Application Manager for Response Time
Tracking database and start the upgrade again.
84
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
BWMCR8515W: A domain user has been specified. Domain
users must have Act as part of the operating system and
administrative user rights on the domain controller as well as
on the local machine. Before proceeding with this installation,
verify that the domain user has these privileges. If these
privileges can not be granted, the installation program will
complete successfully, but WebSphere will be unable to start.
Explanation
Domain users specified on this panel must have the Act as part of the operating
system and administrative user rights on the domain controller.
Operator response
Before proceeding with this installation, verify that the domain user has these
privileges. If it doesn't, use a domain user that does have the privileges, use a local
operating system user, or ensure that the domain user specified is granted the
necessary privileges and then restart the installation program.
BWMCR8516W: Other uninstallation directories have been
detected. Make sure no other uninstallers exist in the same
product directory before running this uninstallation. Click OK
to continue.
Explanation
The IBM Tivoli Composite Application Manager for WebSphere and J2EE product
is installed by ISMP. ISMP creates an uninstallation directory that starts with
_uninst* for the product it installs. The current uninstaller has detected other
uninstallation directories that potentially might have fixpacks.
Operator response
Verify the currently installed IBM Tivoli Composite Application Manager products
and follow the installation guide to remove all installed products before
proceeding with the uninstallation.
BWMCR8517W: One of the HP kernel parameters is not set to
a WAS recommended value in the /stand/system file.
Explanation
The WebSphere Application Server requires specific kernel parameters to be
updated on HPUX for better performance.
Operator response
Update the required kernel parameters as documented in the WebSphere
Application Server Installation Guide for HPUX if any performance degradation is
noticed. Installation will continue.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
85
BWMCR8518W: The tables in the database are not empty.
Explanation
The installation program can use exiting tables but they must be empty.
Operator response
Drop the tables or re-create the tables.
BWMCR8519W: There are no tables, but there are tablespaces
in the database.
Explanation
For DB2, both tables and tablespaces must exist or must not exist.
Operator response
Drop the tablespaces.
BWMCR8520W: There are tables in the database but the
number of tables is wrong.
Explanation
The number of tables is too small, you may be using wrong database, a previous
uninstallation may not have dropped all the tables correctly, or manual creation of
database and tables may not have created all the tables.
Operator response
Drop the tables and run the installation program again.
BWMCR8521W: Applications may still be installed on this
management agent.
Explanation
The uninstall has detected applications on this management agent.
Operator response
Verify that the management server is up and there is a network connection to
management server before proceeding. Uninstalling all applications from this
management agent may not complete successfully otherwise.
BWMCR8522W: This is not a supported platform.
Explanation
The operating system under that the install is running is not an officially
supported platform for this release of the product.
86
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
You may proceed to install the product but no support will be provided for any
installation failures.
BWMCR8523W: This is not a supported platform.
Explanation
The operating system under that the install is running is not supported platform
for this release of the product.
Operator response
You may proceed to install the product but no support will be provided for any
installation failures.
BWMCR8028I: Required Field: Password
Explanation
No additional information is available for this message.
BWMCR8029I: Required Field: User
Explanation
No additional information is available for this message.
BWMCR8037I: Required Field: Verify Password
Explanation
No additional information is available for this message.
BWMCR8038I: The passwords entered do not match.
Explanation
No additional information is available for this message.
BWMCR8039I: The user entered does not exist on this
machine.
Explanation
No additional information is available for this message.
BWMCR8040I: The specified user already exists on this
machine.
Explanation
No additional information is available for this message.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
87
BWMCR8050I: To use a proxy host to connect to the
management server, configure the proxy host name and port
in the connection settings of Internet Explorer.
Explanation
No additional information is available for this message.
BWMCR8061I: A local version of WebSphere was found on
this machine. IBM Tivoli Composite Application Manager for
Response Time Tracking, Version 6.1 will use this installation.
Explanation
No additional information is available for this message.
BWMCR8062I: A local version of WebSphere was not detected.
IBM Tivoli Composite Application Manager for Response Time
Tracking, Version 6.1 will install WebSphere 6.0 on this
machine.
Explanation
No additional information is available for this message.
BWMCR8063I: The installation program found a version of
WebSphere Application Server that does not include the
required IBM HTTP Server. The installation program will install
this server.
Explanation
No additional information is available for this message.
BWMCR8078I: Required Field: Proxy Host
Explanation
No additional information is available for this message.
BWMCR8079I: Required Field: Port Number
Explanation
No additional information is available for this message.
BWMCR8084I: Required Field: Cell Name
Explanation
No additional information is available for this message.
BWMCR8085I: Required Field: Server Name
Explanation
No additional information is available for this message.
88
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
BWMCR8086I: Required Field: Node Name
Explanation
No additional information is available for this message.
BWMCR8087I: Required Field: SOAP Connector Port
Explanation
No additional information is available for this message.
BWMCR8088I: Required Field: JDBC Path
Explanation
No additional information is available for this message.
BWMCR8094I: Required Field: URL
Explanation
No additional information is available for this message.
BWMCR8096I: Required Field: Mask
Explanation
No additional information is available for this message.
BWMCR8098I: The installation tried to use a version of
WebSphere 6.0 that does not have WebSphere Application
Server, refresh pack 6.0.2 installed. WebSphere Application
Server refresh pack 6.0.2 or later is required for this product
to run on WebSphere 6.0. The product is also supported on
WebSphere Application Server, Version 5.1.
Explanation
No additional information is available for this message.
BWMCR8101I: SSL Key Store File and Password entered are
invalid
Explanation
No additional information is available for this message.
BWMCR8109I: Required Field: Key File Name
Explanation
No additional information is available for this message.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
89
BWMCR8110I: Required Field: Key File Password
Explanation
No additional information is available for this message.
BWMCR8111I: Required Field: Trust File Name
Explanation
No additional information is available for this message.
BWMCR8112I: Required Field: Trust File Password
Explanation
No additional information is available for this message.
BWMCR8113I: Required Field: Port With Client Authentication
Explanation
No additional information is available for this message.
BWMCR8114I: Required Field: Port Without Client
Authentication
Explanation
No additional information is available for this message.
BWMCR8115I: Required Field: Key File does not exist
Explanation
No additional information is available for this message.
BWMCR8116I: Required Field: Trust File does not exist
Explanation
No additional information is available for this message.
BWMCR8128I: Installation of the WebSphere caching proxy
requires a system reboot. The installation program will
resume after reboot.
Explanation
No additional information is available for this message.
BWMCR8129I: Required Field: KDB Key Information
Explanation
No additional information is available for this message.
90
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
BWMCR8130I: The key ring file does not exist.
Explanation
No additional information is available for this message.
BWMCR8131I: The password stashed file does not exist.
Explanation
No additional information is available for this message.
BWMCR8145I: Required Field: Port For Management Server
Console
Explanation
No additional information is available for this message.
BWMCR8149I: The minimum version and release of this
operating system is:
Explanation
No additional information is available for this message.
BWMCR8150I: The minimum service pack level of this
operating system is:
Explanation
No additional information is available for this message.
BWMCR8151I: The minimum maintenance level of this
operating system is:
Explanation
No additional information is available for this message.
BWMCR8153I: The specified mask value is in an invalid
format.
Explanation
No additional information is available for this message.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
91
BWMCR8154I: The user account you specify must have
membership in the Administrators group. The user also needs
'Act as part of the operating system' and 'Logon as a service'
user rights. The user did not have one or both of these user
rights but was granted by the installation process. To proceed
with the installation, cancel the current installation. Go to
Start->Shut Down and log off. Then, log back in and restart
the installation.
Explanation
No additional information is available for this message.
BWMCR8155I: Required Field: Admin Console Port
Explanation
No additional information is available for this message.
BWMCR8157I: Required Field: database name
Explanation
No additional information is available for this message.
BWMCR8158I: Required Field: SID
Explanation
No additional information is available for this message.
BWMCR8159I: Required Field: port
Explanation
No additional information is available for this message.
BWMCR8160I: Required Field: host
Explanation
No additional information is available for this message.
BWMCR8161I: Password entered is not valid for the specified
SSL Key Store File
Explanation
No additional information is available for this message.
BWMCR8162I: Password entered is not valid for the specified
SSL Trust File
Explanation
No additional information is available for this message.
92
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
BWMCR8164I: Password does not meet specifications.
Choose another password.
Explanation
No additional information is available for this message.
BWMCR8165I: The temp drive does not have enough space.
Free up some temporary space or rerun the installation from
the command line using the -W spanningBean.tempDir={dir}
option. See the trace file for more details.
Explanation
No additional information is available for this message.
BWMCR8166I: Configured the management agent
successfully.
Explanation
No additional information is available for this message.
BWMCR8167I: Unregistered the management agent
successfully.
Explanation
No additional information is available for this message.
BWMCR8168I: Usage: configMa.sh [install | uninstall]
Explanation
No additional information is available for this message.
BWMCR8169I: Local directories created. \nGo to
/etc/tmtp/MA/config, verify setupEnv.sh and customize
zos.properties. \nRun configMa.sh to register the management
agent.
Explanation
No additional information is available for this message.
BWMCR8170I: This script will prepare the IBM Tivoli
Composite Application Manager for Response Time Tracking
management agent for configuration. \nIt will create local
directories in /etc and /var directories. \nDo you want to
continue ? [y/n]
Explanation
No additional information is available for this message.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
93
BWMCR8171I: Check values in zos.properties including port
numbers entered are all correct.
Explanation
No additional information is available for this message.
BWMCR8172I: * (Specify a User account that exists on the
WebSphere Application Server of the management server.
This user account must have the "agent" role.)
Explanation
No additional information is available for this message.
BWMCR8173I: Upgraded the configuration for the
management agent.
Explanation
No additional information is available for this message.
BWMCR8174I: The installation tried to use a 5.0 version of
WebSphere Application Server, version 5.0.1 that has
Embedded Messaging Installed. WebSphere Application
Server Fix pack 5.0.2 or later is required for this product to be
migrated to WebSphere Application Server 6.0.
Explanation
No additional information is available for this message.
BWMCR8175I: The installation tried to use a version of
WebSphere that does not have WebSphere Application Server,
Fix pack 5.1.1.2 installed. WebSphere Application Server Fix
pack 5.1.1.2 or later is required for this product. The
installation images for the fixpack can be obtained from the
IBM Tivoli Composite Application Manager, Version 6.1 CD
packet.
Explanation
No additional information is available for this message.
BWMCR8176I: The installation program tried to upgrade a
version of the management server that is not supported. A
management server at the 5.3.1 level or later is required for
this upgrade.
Explanation
No additional information is available for this message.
94
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
BWMCR8177I: The installation program could not connect to
specified database, this could be caused by incorrect
database information like server, database name, user,
password or port. \nCorrect the information and try again. If
all information is correct, the database may not exist. \nSelect
Yes to allow the installation program to attempt to create the
database.
Explanation
No additional information is available for this message.
BWMCR8178I: This script will create links for the ARM shared
libraries in /usr/lib directory. \nDo you want to continue ? [y/n]
Explanation
No additional information is available for this message.
BWMCR8179I: Done. Links were created successfully in
/usr/lib directory.
Explanation
No additional information is available for this message.
BWMCR8180I: The installation program tried to use a version
of the management server that does not have the appropriate
fix pack level installed. A version of the management server at
Fix pack 5.301 or later is required for this product.
Explanation
No additional information is available for this message.
BWMCR8181I: The installation tried to use a version of the
management server that does not have the appropriate fix
pack level installed. A version of the management server at
Fix pack 5.301 or later is required for this product.
Explanation
No additional information is available for this message.
BWMCR8182I: The installation tried to use a DB2 version that
is not supported by this product. DB2 8.1 ESE with Fixpack 6a
or later is required for this product.
Explanation
No additional information is available for this message.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
95
BWMRTT0001A: The User Name or Password entered is not
valid
BWMRTT0002A: The ojdbc14.jar file was not found in the
specified JDBC path.
Explanation
The specified JDBC pathmust be a directory containing the ojdbc14.jar file.
BWMCR8518E: The host name is not fully qualified. Provide a
fully qualified host name.
Explanation
The host name must be fully qualified.
Operator response
Type a host name that the Domain Name System service can resolve before you
proceed. You must provide the fully qualified host name.
BWMCR8175E: There is no enough disk spacedestination.
BWMCR8193E: Unsupported operating systemosname.
BWMCR8176E: The value valueyou entered for the namefield is
invalid.
Explanation
The requirements for this field are: Is this a required field (Yes/No)?IsRequiredThe
Regular Expression definition for this field is:RegExp. The length of the value for
this field must be betweenminLengthandmaxLength. The value must be of the
typevalidationType. The value for this field must be betweenminValueandmaxValue.
96
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
BWMCR8177E: The JAVA_HOME pointed JRE is invalid,
please useavaVersionCmdto validate it. If
correct,javaVersionCmdwill print out version of the JRE.
BWMCR8178E: The JAVA_HOME pointed JRE is invalid,
please usejavaVersionCmdto validate it. If
correct,javaVersionCmdwill print out version of the JRE,but the
print out ofjavaVersionOutput.
BWMCR8179E: The JAVA_HOME is invalid,the
java.exe(windows) or java(linux or unix) does not exist.
BWMCR8180E: Installation program could not resolve the
specified hostname. Type a fully qualified host name that the
Domain Name System service can resolve before you
proceed.
Explanation
The communication between the Data Collector and Managing Server need fully
qualified host name.
Operator response
Check the hosts file to make sure that it has a valid IP address and host name. On
Windows operating systems, this file is %SystemRoot%/system32/drivers/etc/
hosts and on UNIX operating systems, it is /etc/hosts. Edit this file if necessary
and retry to connect Managing Server.
BWMCR8181E: Incorrect host name. Type a fully qualified host
name that the Domain Name System service can resolve
before you proceed.
Explanation
The communication between the Data Collector and Managing Server need fully
qualified host name. You can not input IP address or host name which can not be
resolved.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
97
BWMCR8182E: The path is not empty:pathPlease select an
empty path or a new path.
BWMCR8183I: Select Action.
BWMCR8184I: Select action to be executed.
BWMCR8185I: Exit after the action execution.
BWMCR8186E: The value valueyou entered for thenamefield is
invalid.
Explanation
The requirements for this field are: Is this a required field (Yes/No)?IsRequired. The
Regular Expression definition for this field is:RegExp. The length of the value for
this field must be betweenminLengthandmaxLength. The value must be of the
typevalidationType.
BWMCR8187E: Incorrect host name or IP address for the local
machine.
Explanation
Cannot find this host name or IP address from the local machine setting.
BWMCR8188E: The specified RMI port number is out of range.
Valid TCP/IP port numbers must be positive integers between
8200 and 8299.
Explanation
The RMI Port Number field contains a port number that is not within the accepted
range from 8200 to 8299.
Operator response
Type a port number in the RMI Port Number field that is not less than 8200 and
not greater than 8299.
BWMCR8189E: The specified controller RMI port number is
out of range. Valid TCP/IP port numbers must be positive
integers from 8300 to 8399.
Explanation
The Controller RMI Port Number field contains a port number that is not within
the accepted range from 8300 to 8399.
Operator response
Type a port number in the Controller RMI Port Number field that is not less than
8300 and not greater than 8399.
98
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
BWMCR8190W: The Data Collector cannot connect to the
Managing Server.
Explanation
Communications between the Data Collector and Managing Server may not be
functioning.
Operator response
1. Verify that the host name or IP address that you specified for the Data
Collector is correct.
2. Verify that the firewall is enabled on the Data Collector machine.
3. Verify that the RMI Port Number and Controller RMI Port Number are not
blocked by firewall software on the Data Collector host machine.
BWMCR8191W: The Managing Server cannot connect to the
Data Collector.
Explanation
Communications between the Managing Server and Data Collector may not be
functioning.
Operator response
1. Verify that the host name or IP address that you specified for the Data
Collector is correct.
2. Verify that the Managing Server can resolve the host name or IP address of the
Data Collector.
3. Verify that the firewall is enabled on the Data Collector machine.
4. Verify that the RMI Port Number and Controller RMI Port Number are not
blocked by firewall software on the Data Collector host machine.
BWMCR8192E: The path is not writable:pathPlease select a
writable path.
BWMCR8623E: An error occurred while trying to validate the
response file path.
Explanation
This message is displayed if the response file path is leaved as blank or current
user account do not has writable authority on the response file path.
Operator response
Specify a writable directory and a valid response file name.
BWMCR8625E: An error occurred while trying to validate the
option choosing on this panel.
Explanation
This message is displayed if no option is selected.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
99
Operator response
Select one of two options on the panel at least.
BWMCR8627I: A warning occurred while trying to validate the
specified response file name.
Explanation
This message is displayed if the specified response file exists already.
Operator response
Select YES to continue to overwrite existing file, select NO to specify another file
name.
BWMCR8629E: An error occurred while trying to validate the
specified response file name.
Explanation
This message is displayed if the specified response file exists already and the
current user account do not have write authority on this file.
Operator response
Modify the file atrribute to ensure the existing file is writable or choose another file
name.
BWMCR8631E: An error occurred while trying to validate the
specified response file name.
Explanation
This message is displayed if the current user account do not have write authority
on the directory where the response file will be generated.
Operator response
Modify the folder atrribute to ensure the specified directory is writable or choose
another directory.
BWMCR8633E: An error occurred while trying to validate the
specified response file name.
Explanation
This message is displayed if the current input value is a directory.
Operator response
Specify a fully qualified file name.
100
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
BWMCR8635E: The directory path dir contains spaces, which
is not acceptable.
Explanation
The directory path you entered contains spaces, as in the following example:
C:\Program Files\My Product
Operator response
Type a valid directory path with no spaces, or turn on NTFS shortname generation
in the Windows registry.
BWMCR8636E: The destination path cannot contain the
following special characters: spechar_list
Explanation
No additional information is available for this message.
CYNCR8026I: Required Field: Admin User
Explanation
No additional information is available for this message.
CYNCR8028I: Required Field: Password
Explanation
No additional information is available for this message.
CYNCR8029I: Required Field: User
Explanation
No additional information is available for this message.
CYNCR8037I: Required Field: Verify Password
Explanation
No additional information is available for this message.
CYNCR8038I: The passwords entered do not match.
Explanation
No additional information is available for this message.
CYNCR8039I: The user entered does not exist on this
machine.
Explanation
No additional information is available for this message.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
101
CYNCR8040I: The specified user already exists on this
machine.
Explanation
No additional information is available for this message.
CYNCR8061I: A local version of WebSphere Application Server
was found on this machine. IBM Tivoli Composite Application
Manager for WebSphere 6.1 will use this installation of
WebSphere Application Server.
Explanation
No additional information is available for this message.
CYNCR8062I: A local version of WebSphere Application Server
was not detected. IBM Tivoli Composite Application Manager
for WebSphere 6.1 will install WebSphere Application Server
6.1 on this machine.
Explanation
No additional information is available for this message.
CYNCR8084I: Required Field: Cell Name
Explanation
No additional information is available for this message.
CYNCR8085I: Required Field: Server Name
Explanation
No additional information is available for this message.
CYNCR8086I: Required Field: Node Name
Explanation
No additional information is available for this message.
CYNCR8087I: Required Field: SOAP Connector Port
Explanation
No additional information is available for this message.
CYNCR8088I: Required Field: JDBC Path
Explanation
No additional information is available for this message.
102
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNCR8094I: Required Field: URL
Explanation
No additional information is available for this message.
CYNCR8098I: The installation tried to use a version of
WebSphere 6.0 that does not have WebSphere Application
Server, Fix Pack 6.0.2 installed. WebSphere Application
Server, Fix Pack 6.0.2 or later is required for this product to
run on WebSphere 6.0.
Explanation
No additional information is available for this message.
CYNCR8101I: The SSL Key Store File and Password entered
are invalid.
Explanation
No additional information is available for this message.
CYNCR8109I: Required Field: Key File Name
Explanation
No additional information is available for this message.
CYNCR8110I: Required Field: Key File Password
Explanation
No additional information is available for this message.
CYNCR8111I: Required Field: Trust File Name
Explanation
No additional information is available for this message.
CYNCR8112I: Required Field: Trust File Password
Explanation
No additional information is available for this message.
CYNCR8113I: Required Field: Port With Client Authentication
Explanation
No additional information is available for this message.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
103
CYNCR8114I: Required Field: Port Without Client
Authentication
Explanation
No additional information is available for this message.
CYNCR8115I: Required Field: Key File does not exist.
Explanation
No additional information is available for this message.
CYNCR8116I: Required Field: Trust File does not exist.
Explanation
No additional information is available for this message.
CYNCR8145I: Required Field: Port For Managing Server
Console
Explanation
No additional information is available for this message.
CYNCR8149I: The minimum version and release of this
operating system is:
Explanation
No additional information is available for this message.
CYNCR8150I: The minimum service pack level of this
operating system is:
Explanation
No additional information is available for this message.
CYNCR8151I: The minimum maintenance level of this
operating system is:
Explanation
No additional information is available for this message.
104
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNCR8154I: The user account you specify must have
membership in the Administrators group. The user also needs
Act as part of the operating system and Logon as a service
user rights. The user did not have one or both of these user
rights but was granted access by the installation process. To
proceed with the installation, cancel the current installation.
Select Start > Shut Down and log off. Then, log back in and
restart the installation.
Explanation
No additional information is available for this message.
CYNCR8155I: Required Field: Administrative Console Port
Explanation
No additional information is available for this message.
CYNCR8157I: Required Field: Database Name
Explanation
No additional information is available for this message.
CYNCR8158I: Required Field: SID
Explanation
No additional information is available for this message.
CYNCR8159I: Required Field: Port
Explanation
No additional information is available for this message.
CYNCR8160I: Required Field: Host Name
Explanation
No additional information is available for this message.
CYNCR8161I: The entered password is not valid for the
specified SSL Key Store File.
Explanation
No additional information is available for this message.
CYNCR8162I: The entered password is not valid for the
specified SSL Trust File.
Explanation
No additional information is available for this message.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
105
CYNCR8164I: The password does not meet specifications.
Choose another password.
Explanation
No additional information is available for this message.
CYNCR8165I: The temporary drive does not have enough
space. Free up some temporary space or rerun the installation
from the command line using the -W
spanningBean.tempDir={dir} option. See the trace file for more
details.
Explanation
No additional information is available for this message.
CYNCR8177I: The installation could not connect to the
specified database. It might not exist. The installation will
create the database and the tables.
Explanation
No additional information is available for this message.
CYNCR8178I: The admin user entered does not exist on this
machine.
Explanation
No additional information is available for this message.
CYNCR8179I: The Database Instance user entered does not
exist on this machine.
Explanation
No additional information is available for this message.
CYNCR8180I: The Database Schema user entered does not
exist on this machine.
Explanation
No additional information is available for this message.
CYNCR8194W: There was a failure while unconfiguring the
Data Collector on application server.
Explanation
An error occurred while unconfiguring the Data Collector on the application
server.
Do you want to uninstall anyway (Yes) or stop the uninstallation (No)? The server
might fail to startup if you uninstall anyway.
106
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
Check the logs to determine the cause of failure. Rerun the unconfiguration to
remove the Data Collector.
CYNCR8195E: Incorrect host name or IP address for the local
machine.
Explanation
Can not find this host name or IP address from local machine setting.
CYNCR8196W: Will the following application servers be
reconfigured?\nappserver
Explanation
No additional information is available for this message.
CYNCR8197E: Unable to get Data Collector install
configuration, Please install Data Collector again.
Explanation
No additional information is available for this message.
CYNCR8250E: The user does not have authority to create
tables in this database.
Explanation
The user that you entered in the Database User ID field must have authority to
create tables in the specified DB2 or Oracle database. This message is displayed if
the user does not have authority to create tables in the table space that the
database administrator created for the management repository.
Operator response
Take one of the following actions:
v Enter the user ID and password of a user that has authority to create tables in
the table space that is used for the management repository.
v Use your database client software to grant authority to the database user
specified in the Database User ID and Database Password fields. Grant the
permission required to create tables in the table space to be used for the
management repository.
CYNCR8251E: The software generated an error during the
installation.
Explanation
An installation error has occurred and might prevent completion of the installation.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
107
Operator response
Take the following action:
1. View the trace log to determine the problem.
2. After correcting the issue, continue the installation or cancel and restart the
installation.
CYNCR8253E: The host name cannot contain spaces.
Explanation
The name you entered in the Host Name field contains spaces, as in the following
example:
servername.it.your company.com
Operator response
Enter a valid host name with no spaces in the Host Name field.
CYNCR8254E: The installer encountered invalid data that
prevents completion of the installation.
Explanation
See message.
Operator response
Take the following action
1. Review the specifications that you entered.
2. If you are using the installation wizard, enter the required installation data
again and continue the installation.
3. If the error persists, view the trace log to determine the problem.
4. After correcting the issue, continue the installation or cancel and restart the
installation.
CYNCR8255E: The host name has not been specified or the
specified host name is too long.
Explanation
The Host Name field is empty or contains a name that is too long. The Domain
Name System limitation for a fully qualified host name is 256 characters.
Operator response
Verify the correct host name and type it in the Host Name field.
CYNCR8256E: The installer cannot find the specified host
name.
Explanation
See message.
108
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
Enter a host name that the Domain Name System service can resolve before you
proceed. You must provide the fully qualified host name or the IP address of the
host machine for the Managing Server.
CYNCR8257E: A host name that the Domain Name System can
resolve must be provided.
Explanation
See message.
Operator response
Enter a host name that the Domain Name System service can resolve before you
proceed. You must provide the fully qualified host name or the IP address of the
host machine.
CYNCR8258E: You must enter a fully qualified host name
(such as servername.it.yourcompany.com).
Explanation
This error occurs when you enter a host name with no delimiter characters.
Operator response
Enter a fully qualified host name in the Host Name field. For example, enter
servername.it.your company.com instead of only servername.
CYNCR8259E: An incorrect host name caused an error in the
installation of the Managing Server.
Explanation
The syntax of the host name might be incorrect.
Operator response
Enter a host name that the Domain Name System service can resolve before you
proceed. You must provide the fully qualified host name or the IP address of the
host machine for the Managing Server.
CYNCR8260E: The port number must be an integer value.
Explanation
A non-numeric character was entered in the Port Number field.
Operator response
Enter an integer value in the Port Number field, for example, 80.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
109
CYNCR8261E: The specified port number is outside of the
range for valid TCP/IP port numbers.
Explanation
The Port Number field contains a port number that is not within the accepted
range of 1 to 65535.
Operator response
Enter a port number in the Port Number field that is within the accepted range.
CYNCR8262E: The port number specified for TCP/IP
communication is invalid.
Explanation
Valid TCP/IP port numbers must be positive integers from 1 to 65535.
Operator response
Enter a port number that is within the accepted range.
CYNCR8263E: The installer encountered invalid data that
prevents completion of the installation.
Explanation
See message.
Operator response
Take the following action
1. Review the specifications that you entered.
2. If you are using the installation wizard, enter the required installation data
again and continue the installation.
3. If the error persists, view the trace log to determine the problem.
4. After correcting the issue, continue the installation or cancel and restart the
installation.
CYNCR8264E: The text in the host name field must not
include a protocol, such as http:// or https://.
Explanation
A URL with http:// or https:// in the Host Name field has been entered, as in the
following example:
https://msserver.it.yourcompany.com.
Operator response
Enter a host name without the http:// or https:// protocol. For example, enter
imserver.it.yourcompany.com.
110
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNCR8265E: The computer identified in the Host Name field
cannot be contacted at the specified port.
Explanation
The installation program cannot connect to the computer specified in the Host
Name field because the port is unavailable. One or more of the following might be
the cause:
v The host computer might be down.
v The server software on the specified port might be down.
v The server software cannot use the specified port.
Operator response
Take one or more of the following actions until you find a solution:
v Verify that you accurately entered the host name and port.
v Consult the trace log for more information about the cause of the failure.
v Ensure that the host name is the name of a computer that has the server
software installed.
v Test connectivity to the network. If the network is down, retry the installation at
a later time.
v Try connecting to the server directly through a browser. In the address field of
the browser, enter the URL of the server, using the host name and port that you
specified in the installation window, for example, https://
servername.it.yourcompany.com:443.
CYNCR8266E: The port is busy.
Explanation
An application is currently using the port that you specified in the Port Number
field.
Operator response
Stop the application that is currently using the port you specified, or specify a
different port.
CYNCR8267E: The user name must not contain spaces.
Explanation
On UNIX-based systems, the Managing Server must run under an existing user
and group on this computer. The user and group names must not contain spaces.
The name you entered in the User field contains spaces, for example, Managing
Server.
Operator response
Take one of the following actions:
v Enter a valid name in the User field with no spaces.
v Modify an existing user name so that it does not contain spaces.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
111
v Create a new user for the product component (Managing Server). Add the new
user to an existing group or create both a new user and a new group. The user
and group names must not contain spaces.
Notes®:
v You do not need to exit the installation program to create a user or group. When
you are finished, enter the new user name in the User field.
v To work with users and groups, you can use admintool on Solaris, smit on AIX,
linuxconf on Linux, or any text editor such as VI.
CYNCR8268E: The group name must not contain spaces.
Explanation
On UNIX-based systems, the Managing Server must run under an existing user
and group on this computer. The user and group names must not contain spaces.
The name you entered in the Group field contains spaces, for example, Web
Transaction Performance.
Operator response
Take one of the following actions:
v Enter a valid name in the Group field with no spaces.
v Modify an existing group name so that it does not contain spaces.
v Create a new group (and optionally, a new user) for the product component
(Managing Server). The user and group names must not contain spaces.
Notes:
v The group must be associated with the user name that you enter in the User
field.
v You do not need to exit the installation program to create a user or group. When
you are finished, enter the new name in the User or Group field.
v To work with users and groups, you can use admintool on Solaris, smit on AIX,
linuxconf on Linux, or any text editor such as VI.
CYNCR8269E: The user name cannot be root.
Explanation
You entered root in the User field. The Managing Server cannot run as the root
user. Installing the server under root creates a security risk.
Operator response
Take one of the following actions:
v Enter the name of an existing user on this computer, other than root, under
which the product component (Managing Server) can run. The user name must
not contain spaces.
v Create a new user for the product component. Add the new user to an existing
group or create both a new user and a new group. The user and group names
must not contain spaces.
Notes:
112
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
v You do not need to exit the installation program to create a user or group. When
you are finished, enter the new user name in the User field.
v To work with users and groups, you can use admintool on Solaris, smit on AIX,
linuxconf on Linux, or any text editor such as VI.
CYNCR8270E: The user is not defined on this computer.
Explanation
The installation program does not recognize the name that you entered in the User
field. On UNIX-based systems, the Managing Server must run under an existing
user on this computer.
Operator response
Take one of the following actions:
v Enter a valid name for an existing user in the User field. The user name must
not contain spaces.
v Create a new user for the product component (Managing Server). Add the new
user to an existing group or create both a new user and a new group. The user
and group names must not contain spaces.
Notes:
v You do not need to exit the installation program to create a user or group. When
you are finished, enter the new user name in the User field.
v To work with users and groups, you can use admintool on Solaris, smit on AIX,
linuxconf on Linux, or any text editor such as VI.
CYNCR8271E: The group is not defined on this computer.
Explanation
The installation program does not recognize the name that you entered in the
Group field.
Operator response
Take one of the following actions:
v Enter a valid name for an existing group in the Group field. The group name
must not contain spaces.
v Create a new group (and optionally, a new user) for the product component. The
user and group names must not contain spaces.
Notes:
v The group must be associated with the user name that you enter in the User
field.
v You do not need to exit the installation program to create a user or group. When
you are finished, enter the new name in the User or Group field.
v To work with users and groups, you can use admintool on Solaris, smit on AIX,
linuxconf on Linux, or any text editor such as VI.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
113
CYNCR8272E: The user is not root. This installation can only
be run as the root user.
Explanation
You did not log on as the root user before starting the installation or uninstallation
program.
Operator response
Click Cancel to exit the installation or uninstallation program. Log on as the root
user and restart the installation or uninstallation.
CYNCR8273E: You must have Administrator privileges to
install or uninstall this software.
Explanation
You did not log on as a user with administrator privileges before starting the
installation or uninstallation program.
Operator response
Click Cancel to exit the installation or uninstallation program. Log on as an
Administrator user and restart the installation or uninstallation.
CYNCR8274E: The installation program failed to initialize the
installation context.
Explanation
The installation program either failed to read in the prerequisite XML file or a
system error occurred.
Operator response
Consult the trace log for more information about the cause of the failure.
CYNCR8275E: IBM Tivoli Composite Application Manager for
WebSphere does not support the specified platform.
Explanation
See the installation guide for details on supported platforms.
Operator response
Take one of the following actions:
v Upgrade the operating system to a supported version.
v Reinstall the operating system to a supported version.
v Use a different computer with a supported platform.
114
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNCR8276E: The system failed to run the .bat file that
configures the agent. The service might not have been
created.
Explanation
The batch file that configures the agent failed to run. As a result, the agent service
cannot be created.
Operator response
View the trace log to determine the problem. After correcting the issue, try the
installation again.
CYNCR8277E: The system failed to run the .bat file that
removes the agent configuration. The service might not have
been removed.
Explanation
The uninstallation of the agent did not complete successfully.
Operator response
View the trace file to determine the cause of failure. The agent might need to be
cleaned up manually. Remove the agent service and all files before reinstalling.
CYNCR8278E: The system failed to run the script that
configures the agent. The configuration might not have
completed.
Explanation
A script that helps configure the agent failed to run. As a result, configuration is
not complete.
Operator response
View the trace log to determine the problem. After correcting the issue, try the
installation again.
CYNCR8279E: The system failed to run the script that
removes the agent configuration. The configuration might not
have been removed.
Explanation
The uninstallation of the agent did not complete successfully.
Operator response
View the trace file to determine the cause of failure. The agent might need to be
cleaned up manually. Stop the agent daemon and remove any files before
attempting to reinstall.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
115
CYNCR8282E: An error occurred configuring the Managing
Server.
Explanation
The configuration of the Managing Server did not complete successfully.
Operator response
View the trace log to determine the problem. After correcting the issue, try the
installation again.
CYNCR8283E: The system failed to completely remove
configuration files from the Managing Server.
Explanation
The uninstallation of the Managing Server did not complete successfully. A
probable cause for this failure is that a file is locked by another process.
Operator response
If you cannot find the process, reboot the computer to stop the process. View the
trace file to determine the cause of failure. Follow steps in the documentation to
make sure that the Managing Server is completely removed from the computer
before attempting to reinstall.
CYNCR8284E: The software that you are trying to installation
is already installed.
Explanation
The installer encountered a file that is used for inventory information on this
computer. This file contained text that indicates this software is already installed
on this computer. The Prereqs.xml file on the CD identifies the file names being
searched on the different operating systems and the text within them that is used
to indicate that the software is already installed.
Operator response
Run the uninstallation program to uninstall this software or remove the text from
the inventory file to force the installation to proceed.
CYNCR8285E: A required file for searching for prerequisites
was not found:
Explanation
The installer was not able to locate the file that is needed to examine the system
for the installed applications.
Operator response
Create the file or install the program that created the file.
116
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNCR8286E: There was a prerequisite failure. An invalid
registry key was found.
Explanation
The installer encountered a key in the registry that is part of an application that
violates the requirements of this product.
Operator response
Remove the registry key or uninstall the program that created the registry key.
CYNCR8287E: There was a prerequisite failure. A required
registry key was not found.
Explanation
The installer expected to find a required key in the registry.
Operator response
Add the required registry key or reinstall the program that creates the registry key.
CYNCR8288E: Due to prerequisite failure, this installation
cannot continue.
Explanation
The installer encountered violations of the prerequisite configuration for this
product.
Operator response
Review and correct the prerequisite conditions before you attempt to install again.
See the installation guide for more details.
CYNCR8289E: There was an error connecting to the database:
Explanation
The installer failed to make an initial connection to the database that you specified.
Operator response
Ensure that the database is running and accessible in the network. Confirm that
the values you entered for the database are correct before you continue the
installation.
CYNCR8290E: There was an error executing a database query:
Explanation
The installer failed to make an initial query to the database you specified.
Operator response
View the trace log to determine the origin of the problem.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
117
CYNCR8291E: There was an error processing the result set
from a database query:
Explanation
The installer encountered an error while it processed the result set from the
specified database.
Operator response
View the trace log to determine the origin of the problem.
CYNCR8292E: The specified node name is not correct.
Explanation
The node name must match the node name specified in the local installation of
WebSphere Application Server. Locate the node name by opening the WebSphere
Application Server administrative console and clicking Environment > Manage
WebSphere Variables. The node name is listed in the WebSphere Application Server
Variable window.
Operator response
Enter the correct node name and try again.
CYNCR8293E: The specified cell name is not correct.
Explanation
The node name must match the cell name specified in the local installation files of
WebSphere Application Server. You can locate the cell name by opening the
WebSphere Application Server administrative console and clicking Environment >
Manage WebSphere Variables. The cell name is listed in the WebSphere Application
Server Variable window.
Operator response
Enter the correct cell name and try again.
CYNCR8294E: The specified server name is not correct.
Explanation
The server name must match the cell name specified in the local installation files of
the WebSphere Application Server. Locate the server name by opening the
WebSphere Application Server administrative console and clicking Environment >
Manage WebSphere Variables. The server name is listed in the WebSphere
Application Server Variable window.
Operator response
Enter the correct cell name and try again.
118
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNCR8295E: WebSphere Application Server cannot be
contacted using the specified port. The WebSphere
Application Server might not be running or the specified port
number is incorrect.
Explanation
The port number specified does not match the port number specified in the local
installation files of WebSphere Application Server, or the WebSphere Application
Server is not running.
Operator response
Verify that the WebSphere Application Server is running, enter the correct port
number, and try again.
CYNCR8296E: The data entered does not match the data
specified in the local installation files of the WebSphere
Application Server.
Explanation
The node name, cell name, server name, and port name must match the node
name, cell name, server name, and port name specified in the local installation of
the WebSphere Application Server.
Operator response
Enter the correct node name, cell name, server name, and port name, and try
again.
CYNCR8300E: The db2java.zip file was not found in the
specified JDBCpath.
Explanation
The specified JDBC path must be a directory containing the db2java.zip file.
Operator response
Specify the correct JDBC path. The file is located in the basdir\sqllib\java directory
of the DB2 client on Windows systems or the DB2 instance user home directory on
UNIX systems.
CYNCR8301E: The user already exists.
Explanation
The name that you entered in the User field already exists, but you specified that
you want to create a new user with this name.
Operator response
Take one of the following actions:
v Enter a valid name of a new user in the User field. The user name must not
contain spaces.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
119
v Delete this user from the computer.
Notes:
v You do not need to exit the installation program to delete a user or group. When
you are finished, enter the new user name in the User field.
v To work with users and groups, you can use admintool on Solaris, smit on AIX,
or linuxconf on Linux.
CYNCR8302E: The UID is already defined on this computer.
Explanation
The installation program found that the value you entered in the Uid field already
exists in the /etc/passwd file. On UNIX-based systems, the UID or Unique
Identifier must be unique for each user that is defined in the /etc/passwd file.
Operator response
Take one of the following actions:
v Enter a valid UID that is not already being used in the Uid field.
v Use an existing user rather than trying to create a new user.
v Delete the user using this UID value from the /etc/passwd file
v Change the user's line in the /etc/passwd file so that it uses a unique UID
value.
Note:
v You do not need to exit the installation program to create a user or group. When
you are finished, enter the UID value in the Uid field.
v To work with users and groups, you can use the admintool on Solaris, smit on
AIX, linuxconf on Linux, or any text editor such as VI.
CYNCR8303E: The specified path is not a fully qualified UNIX
path.
Explanation
The installation program discovered that you did not specify the correct file or
directory.
Operator response
Enter a fully qualified UNIX path and try the installation again.
CYNCR8304E: The specified path is not a fully qualified UNIX
path.
Explanation
The installation program discovered that the path specified for the file or directory
includes more than the allowed maximum characters.
Operator response
Specify the fully qualified UNIX path with less than 1024 characters.
120
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNCR8305E: The specified path is not a fully qualified UNIX
path.
Explanation
The value you specified for the file or directory field is not fully qualified because
it did not begin with a slash.
Operator response
Specify a fully qualified UNIX path that begins with a slash.
CYNCR8306E: An error occurred because a required field was
not populated.
Explanation
All fields must be populated.
Operator response
Enter data into all fields and try again.
CYNCR8307E: The specified home directory for the user was
not found.
Explanation
The home directory for an existing user on UNIX systems must be specified in the
/etc/password file so that the installation program can identify the existing user.
Operator response
Correct the /etc/password file, choose another existing user, or create a new user
during this installation.
CYNCR8308E: The directory path required for a disk space
check has not been set.
Explanation
See message.
Operator response
Ensure that a valid directory path is provided.
CYNCR8309E: An invalid directory path was provided for a
disk space check.
Explanation
The path name supplied for a disk space check does not exist or is not a directory.
Operator response
Ensure that a valid directory path is provided.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
121
CYNCR8310E: The minimum disk space value required for a
disk space check was not set or is invalid.
Explanation
The value must be less than or equal to 1 megabyte.
Operator response
Ensure that a valid minimum disk space is provided.
CYNCR8311E: The provided directory path did not have the
minimum specified free disk space.
Explanation
See message.
Operator response
Provide a value for the directory path free disk space that meets the specified
minimum. Refer to the installation guide for the disk space requirements for your
system.
CYNCR8312E: The DB2 environment variable must be set
prior to running the installation if an existing DB2 server is
used.
Explanation
When the DB2 client software is installed, certain environment variables are active,
such as db2instance.
Operator response
Take the following action
1. Exit the installation and make sure you can connect properly before re-running
the installation.
v On UNIX systems, source the db2profile of the DB2 instance user.
v On Windows systems, install the DB2 client software.
v On all operating systems, the database must be cataloged properly before the
DB2 client can be used.
2. If this machine has a DB2 server already installed, bring up the DB2
command-line environment and make sure you can list the database directory.
The database and bufferpool must already exist.
3. If this machine accesses a remote DB2 server, it must have the DB2 client
software installed on it and the remote database must be properly cataloged.
Furthermore, if this is a UNIX operating system, the command db2profile must
be run before running the installation. db2profile refers to a file in the sqllib
subdirectory of the DB2 instance user. For further instructions on how to
perform these steps consult the problem determination guide.
122
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNCR8313E: The specified db2admin home directory path is
invalid.
Explanation
See message.
Operator response
Provide a valid db2admin home directory path.
CYNCR8314E: The specified db2admin home directory path
did not have the required minimum free disk space.
Explanation
See message.
Operator response
Provide a directory path whose free disk space meets the specified minimum.
Refer to the installation guide for the disk space requirements for your computer.
CYNCR8315E: The specified db2inst home directory path is
invalid.
Explanation
See message.
Operator response
Provide a valid directory path.
CYNCR8316E: The specified dbinst home directory path did
not have the required minimum free disk space.
Explanation
See message.
Operator response
Provide a directory path with the required minimum free disk space. Refer to the
installation guide for the disk space requirements for your system.
CYNCR8317E: The test connection to the Managing Server
failed. The system was unable to contact the Managing
Server. Agent installation cannot continue until the connection
is established.
Explanation
Possible reasons that the Managing Server connection is broken include the
following scenarios:
v The Managing Server is down.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
123
v The Managing Server information was entered incorrectly (incorrect host name,
port, user name or password).
v The user name entered does not have agent privileges on the Managing Server.
v The Managing Server was not restarted after a new installation.
Operator response
To resolve this error, the user running the installation can perform any of the
following actions:
v Verify that the Managing Server is running. If the Managing Server is not
running, start it. IBM Tivoli Composite Application Manager for WebSphere
starts automatically when WebSphere Application Server is restarted. Or, from
the WebSphere Application Server administrative console, you can select
Application > Enterprise Applications, select IBM Tivoli Composite Application
Manager for WebSphere, and click Start. A green arrow displays next to the
application if it is running correctly.
v Verify whether the information entered matches the Managing Server
information (host name, port, security enabled, user name or password).
v Verify that the user specified has agent roles on the Managing Server.
v If the Managing Server was installed without restarting WebSphere Application
Server afterwards, the agent cannot connect to the Managing Server. Make sure
that WebSphere Application Server was restarted. Before restarting the
WebSphere Application Server, make sure the DB2 environment is set up. On
UNIX, source the db2profile of the DB2 instance user.
v Use a different Managing Server.
CYNCR8321E: An error occurred while running the embedded
DB2 installation. The current installation will be canceled.
Refer to the ITCAM for Application Diagnostics installation
trace log and DB2 installation log for more details.
Explanation
The DB2 embedded installation failed.
Operator response
Complete the following steps:
1. View the DB2 installation logs for information about the cause of the failure.
The logs are written to /tmp/db2setup.log on UNIX systems and to the My
Documents\DB2LOG directory under the user ID with which the DB2
installation was performed on Windows systems.
2. See the ITCAM for Application Diagnostics Problem Determination guide.
3. Correct the source of the failure.
4. Re-run the installation.
CYNCR8323E: The installation failed while installing the
WebSphere Application Server.
Explanation
There was an error during the embedded WebSphere Application Server
installation.
124
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
Take the following action
1. View the WebSphere installation logs for information about the cause of the
failure. The logs are written to MS_BASEDIR/temp/wasInstallLog.txt.
2. See the ITCAM for Application Diagnostics Problem Determination guide.
3. Correct the source of the failure.
4. Re-run the installation.
CYNCR8324E: The installation failed while installing the
WebSphere Application Server Fixpack.
Explanation
There was an error during the installation of WebSphere Application Server
Fixpack 6.0.2.
Operator response
Take the following action
1. View the WebSphere installation logs for information about the cause of the
failure. The logs are written to WAS_BASEDIR/logs.
2. See the ITCAM for Application Diagnostics Problem Determination guide.
3. Correct the source of the failure.
4. Re-run the installation.
CYNCR8325E: The installation failed while starting WebSphere
Application Server.
Explanation
There was an error during the embedded WebSphere Application Server
installation while starting the WebSphere Application Server.
Operator response
Take the following action
1. Examine the WebSphere Application Server logs and determine why the
installation failed.
2. Use the WebSphere Application Server media to install it manually.
3. Restart the installation using the steps provided in the installation guide for
installing IBM Tivoli Composite Application Manager for WebSphere with an
existing WebSphere Application Server.
CYNCR8327E: The installation failed because the version and
release of the operating system is below the supported level.
Explanation
There was an error during the prerequisite checking of the installation
initialization.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
125
Operator response
Upgrade or reinstall the operating system to a supported version.
CYNCR8328E: The installation failed because the version and
release of the operating system is not at a supported level.
Explanation
Operator response
Upgrade or reinstall the operating system to a supported version.
CYNCR8329E: The installation failed because the service pack
level of the operating system is below the supported level.
Explanation
There was an error during the prerequisite checking of the installation
initialization.
Operator response
Upgrade or reinstall the operating system to a supported service pack level.
CYNCR8330E: The installation failed because the maintenance
level of the operating system is below the supported level.
Explanation
There was an error during the prerequisite checking of the installation
initialization.
Operator response
Upgrade or reinstall the operating system to a supported maintenance level.
CYNCR8331E: The installation failed because the host name
cannot be resolved.
Explanation
There was an error during the prerequisite checking of the installation
initialization.
Operator response
Inspect and repair the hosts file, or use other methods for host name resolution.
CYNCR8332E: The user does not have the required authority
to create a schema in this database.
Explanation
The user probably does not have DB2 SYSADM or SYSCTRL authority.
126
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
Ensure that the user has DB2 SYSADM or SYSCTRL authority.
CYNCR8333E: The IP address of the local system was
detected as 127.0.0.1, which is not allowed.
Explanation
The installation program cannot continue because the detected IP address of local
system was 127.0.0.1. The IP address must be a valid address.
Operator response
Take the following action
1. Check the hosts file to make sure that it has a valid IP address and host name.
On Windows systems, this file is %SystemRoot%/system32/drivers/etc/hosts,
and on UNIX systems, it is /etc/hosts.
2. Edit this file if necessary.
3. Retry the installation.
CYNCR8334E: The path specified for the {0} CD-ROM is
invalid:
Explanation
The location specified an incorrect location for the CD-ROM.
Operator response
Restart the install using the correct path to the CD-ROM.
CYNCR8335E: The system was unable to grant the user the
Windows user rights necessary for WebSphere Application
Server. The installation cannot continue.
Explanation
The user needs Act as part of the operating system and Logon as a service user
rights to run WebSphere Application Server. The user did not have one or both of
these rights and the installation was unable to grant these user rights to the user.
Operator response
Grant these rights to the user and retry the installation.
CYNCR8336E: An error occurred while removing the database
tables. The tables must be removed manually.
Explanation
See message.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
127
Operator response
Examine the installation trace log for more detailed information. Manually remove
the database tables using the utilities provided with the database.
CYNCR8338E: Kernel parameters MSGMAX and MSGMNB
must be set to 65535 in the /etc/system file.
Explanation
DB2 requires that specific Kernel parameters be updated.
Operator response
Update the required Kernel parameters as documented in the "Prerequisites and
pre-installation for Managing Server on UNIX" chapter of the ITCAM for
Application Diagnostics Installation and Customization Guide, then reboot the
system, and rerun the installation.
CYNCR8339E: The DB2 user ID does not satisfy the required
set of conditions.
Explanation
These are the rules for valid DB2 user IDs:
v Can contain 1 to 8 characters
v Can include letters, numbers, @, #, $
v Cannot begin with IBM, SYS, SQL, or a number
v Cannot be a DB2-reserved word (USERS, ADMINS, GUESTS, PUBLIC or
LOCAL)
v Cannot end with a $
v Cannot include accented characters
Operator response
Change the DB2 user ID so that it satisfies those conditions.
CYNCR8340E: The DB2 user password does not satisfy the
required set of conditions.
Explanation
These are the rules for valid DB2 user passwords:
v Can contain 1 - 8 characters
v Cannot have an expiration date or usage restrictions
v Can include A - Z, a - z, 0 - 9, or @, #, $, or &
v Cannot begin with a number or &
Operator response
Change the DB2 user password so that it satisfies those conditions.
128
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNCR8341E: There was a prerequisite failure. Internet
Explorer 4.01 Service Pack 2 is required to complete the
installation.
Explanation
See message.
Operator response
Install Internet Explorer 4.01 Service Pack 2 or higher.
CYNCR8342E: The selected destination directory already has
an uninstall subdirectory, _uninst53.
Explanation
An existing _uninst53 subdirectory indicates there was a previous installation of
the product.
Operator response
Remove the directory or select a new destination directory.
CYNCR8343E: The specified UID for the user was not found.
Explanation
The UID for an existing user must be specified in the /etc/password file on UNIX
systems so that the installation program can identify the existing user.
Operator response
Correct the /etc/passwd file, choose another existing user, or create a new user
during this installation.
CYNCR8344E: The specified license key contained
non-numeric characters or was not a valid long integer.
Explanation
The license key must be a 16-digit number with no punctuation, non-numeric
characters or spaces.
Operator response
Correct the license key or choose another license key.
CYNCR8345E: No more licenses are available on the server.
Explanation
A license key that is valid for a finite number of licenses is specified in
server.properties when the Managing Server is installed. The maximum number of
endpoints has already been installed against that server.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
129
Operator response
Change the license key to one that allows another endpoint, or uninstall one of the
existing endpoints.
CYNCR8346E: WebSphere Application Server 5.1 is required
to complete the installation.
Explanation
The installer did not discover a required version of WebSphere Application Server.
Operator response
Install WebSphere Application Server 5.1 or higher and rerun the installation.
CYNCR8357E: One of the HP Kernel parameters is not set
correctly in the /stand/system file.
Explanation
DB2 requires that specific Kernel parameters be updated for HP-UX.
Operator response
Take the following action
1. Update the required kernel parameters as documented in the "Prerequisites and
pre-installation for Managing Server on UNIX" chapter of the ITCAM for
Application Diagnostics Installation and Customization Guide.
2. Shut down the agent manually and reinstall the fix pack.
CYNCR8358E: The WebSphere Application Server 6.1
installation image directory that was specified is not valid.
Explanation
The specified directory does not contain installation images for WebSphere
Application Server 6.1, or the images in the specified directory do not have the
correct permissions. The license.txt file in the specified directory either does not
exist or does not contain the following string: IBM WEBSPHERE APPLICATION
SERVER, V. 6.1.
Operator response
Take one of the following actions:
1. The person performing the installation must locate a directory with valid
WebSphere Application Server 6.1 installation images and specify that directory.
2. The user can click the check box to perform an embedded installation using
CDs.
130
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNCR8359E: The DB2 8.2 installation image directory that
was specified is not valid.
Explanation
The specified directory does not contain installation images for DB2 8.2, or the
images in the specified directory do not have the correct permissions. The
readme.txt file in the specified directory either does not exist or does not contain
the following string: IBM DB2 Universal Database™ Enterprise Server Edition.
Operator response
Take one of the following actions:
1. The person performing the installation can locate a directory with valid DB2 8.2
installation images and specify that directory.
2. The user can click the check box to perform an embedded installation using
CDs.
CYNCR8360E: The WebSphere Application Server 6.1.1
installation image directory that was specified is not valid.
Explanation
The specified directory does not contain installation images for WebSphere
Application Server 6.0.1 or the images in the specified directory do not have the
correct permissions.
Operator response
Take one of the following actions:
1. The person performing the installation must locate a directory with valid
WebSphere Application Server, Refresh Pack 6.0.1 installation images and
specify that directory.
2. The user can click the check box to perform an embedded installation using
CDs.
3. The user can manually install WebSphere Application Server 6.0, apply the
Refresh Pack 6.0.1, then rerun the Managing Server installation.
CYNCR8361E: The user name and password specified cannot
be used to contact WebSphere Application Server.
Explanation
The WebSphere Application Server might not be running or the specified user
name or password is incorrect.
Operator response
Verify that the WebSphere Application Server is running, enter the correct user
name and password, and try again.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
131
CYNCR8362E: The user does not have the appropriate rights
to run the Managing Server.
Explanation
The user name given does not have the appropriate rights to run WebSphere
Application Server securely.
Operator response
Verify that the user has Act as part of the operating system and Log on as a service
rights and try again.
CYNCR8363E: Security is not enabled in WebSphere
Application Server.
Explanation
The WebSphere Application Server is not configured with security enabled.
Operator response
Deselect the check box for WebSphere Application Server security enabled and try
again.
CYNCR8366E: This product has already been installed on this
system.
Explanation
See message.
Operator response
Uninstall the current product from the system, and then try running this
installation again.
CYNCR8374E: User name and Password validation failed.
Ensure that the user name entered has agent privileges on the
Managing Server.
Explanation
One of the following issues has occurred:
v The user name does not have agent role on the Managing Server.
v The user name does not exist on the Managing Server.
v The password entered is incorrect.
Operator response
Verify that the user exists and is mapped correctly to the agent role for the
Managing Server.
132
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNCR8375E: The port is reserved.
Explanation
The application already uses the port that you specified in the Port Number field.
Operator response
Specify a different port.
CYNCR8376E: The user you specify must have root privileges.
Explanation
You entered a user on the panel that does not have root privileges.
Operator response
Enter a user that has root privileges.
CYNCR8377E: WebSphere Application Server failed to map
roles to users.
Explanation
The WebSphere Application Server roles must be mapped to actual operating
system users defined for the host on which WebSphere Application Server is
installed.
Operator response
Look in the WebSphere Application Server log for exceptions and errors concerning
why user roles mapping failed. Correct any errors found and rerun installation.
CYNCR8378E: The test connection to the Managing Server
failed. The system was unable to contact the Managing
Server.
Explanation
One of the following issues has occurred:
v The uninstallation program cannot unregister the agent from the Managing
Server. The following issues are possible causes for this failure:
– Information is incorrect in the endpoint properties.
– The Managing Server is down.
– The Managing Server cannot be contacted.
– The Managing Server was uninstalled.
v The uninstallation completes but the agent does not unregister from the
Managing Server.
Operator response
Take one of the following actions:
v If the Managing Server was uninstalled, no action is needed.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
133
v If Managing Server is still in use, archive the agent that failed to unregister so
that it does not display in the user interface. To archive the agent take the
following action On the console, select System Administration->Work With
Agents, select the agent that was uninstalled, and select Archive from the pull
down menu.
CYNCR8390E: Internet Explorer Enhanced Security is set on
high for the internet zone. This setting must be medium or
lower.
Explanation
Internet Explorer Enhanced Security for the internet zone must be set to a medium
level for the agent to operate properly on Windows 2003. If the Internet Explorer
Enhanced Security is set at high, the agent never shows an online state after
installation.
The Microsoft Windows Server 2003 Internet Explorer Enhanced Security
Configuration component (also known as Microsoft Internet Explorer hardening)
reduces a server's vulnerability to attacks from Web content by applying more
restrictive Internet Explorer security settings. As a result, Internet Explorer
Enhanced Security Configuration can prevent some Web sites from displaying
properly or performing as expected.
Operator response
Change the Internet zone security setting from high to medium. To change the
security setting, take the following action
1. Open Internet Explorer and select Internet Options from the Tools menu.
2. On the Security tab select Internet.
3. Move the slider bar at the bottom of the window to select a medium or lower
security level.
4. Click OK to apply the changes.
CYNCR8391E: WebSphere Network Deployment is not
supported.
Explanation
The WebSphere port validation threw an exception, which can occur if installing
IBM Tivoli Monitoring for Transaction Performance against WebSphere Network
Deployment Manager. Installation cannot be continued.
Operator response
Do not install IBM Tivoli Monitoring for Transaction Performance on WebSphere
Application Server configured with Network Deployment.
CYNCR8396E: The installation did not find the specified
database.
Explanation
A database has to be created before the installation for Oracle.
134
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
Run the sample script manually to create the database and tables and rerun the
installation.
CYNCR8398E: The installer was unable to get the topology
information from WebSphere Application Server.
Explanation
This problem is usually caused when WebSphere Application Server is not running
during the installation.
Operator response
Start WebSphere Application Server, and click Next to try again.
CYNCR8399E: The installer was unable to validate server and
port information with WebSphere Application Server.
Explanation
This problem is usually caused when WebSphere Application Server is not running
during the installation.
Operator response
Start WebSphere Application Server, and press the Next button to try again.
CYNCR8400E: Server creation failed.
Explanation
The ITCAM for Application Diagnostics product is installed into WebSphere
Application Server by running WebSphere Application Server jacl scripts. One of
the jacl script executions returned unsuccessful and ITCAM for Application
Diagnostics installation failed.
Operator response
Cancel the installation and try again. Make sure WebSphere Application Server
information entered is correct, for example, in ND environments, profile name has
to be entered instead of the server name. Check the installation guide for more
information.
CYNCR8401E: The db2profile file was not found in the
specified JDBC path.
Explanation
The specified JDBC path must be a DB2 instance user's home directory containing
the db2profile file.
Operator response
Specify the correctJDBC path. The file is located in the DB2 instance user home
directory, db2inst/sqllib.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
135
CYNCR8402E: The installer encountered invalid data that
prevents completion of the installation.
Explanation
See message.
Operator response
Take the following action
1. Review the specifications that you entered.
2. If you are using the installation wizard, enter the required installation data
again and continue the installation.
3. If the error persists, view the trace log to determine the problem.
4. After correcting the issue, continue the installation or cancel and restart the
installation.
CYNCR8500W: There are existing tables in the database.
Explanation
The installation will not create tables but will use existing tables.
Operator response
Accept the use of existing tables, or drop the tables before proceeding.
CYNCR8502W: The Windows user name must not exceed 20
characters.
Explanation
The specified user name is too long and cannot be created.
Operator response
Enter a user name that is less than 20 characters.
CYNCR8503W: The installation failed to modify the db2profile
script.
Explanation
For local DB2 8.2 server installations, you must add a variable and run a command
to run the db2profile file in the sqllib subdirectory of the instance users home
directory.
Operator response
Follow the instructions in the problem determination guide to modify the script
and run the command after the installation completes. Failure to follow this
procedure causes partial data rollup to fail in some cases.
136
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNCR8508W: The WebSphere Application Server could not
be started.
Explanation
See message.
Operator response
Run the startServer.sh command on UNIX systems or the startServer.bat command
on Windows systems to manually restart the WebSphere Application Server before
completing the installation. The syntax is: startServer server1
CYNCR8509W: The WebSphere Application Server could not
be stopped.
Explanation
The WebSphere Application Server must be stopped before continuing the
installation.
Operator response
Run the stopServer.sh command on UNIX systems or the stopServer.bat command
on Windows systems to stop the WebSphere Application Server before continuing
the installation. The syntax is: stopServer server1 -username WebSphere
Application Server user -password WebSphere Application Server password
CYNCR8515W: A domain user has been specified. Before
proceeding with this installation, verify that the domain user
has these privileges.
Explanation
Domain users specified on this panel must have the Act as part of the operating
system and administrative user rights on the domain controller as well as on the
local machine. If these privileges cannot be granted, the installation will complete
successfully, but WebSphere Application Server will be unable to start.
Operator response
Before proceeding with this installation, you must verify that the domain user has
these privileges. If it does not, take one of the following actions and then restart
the installation:
v Use a domain user that has the correct privileges.
v Use a local operating system user.
v Ensure that the domain user specified is granted the necessary privileges.
CYNCR8516W: Other uninstallation directories have been
detected.
Explanation
The product is installed by ISMP. ISMP creates an uninstallation directory that
starts with _uninst* for the product it installs. The current uninstaller has detected
other uninstallation directories that potentially could have fixpacks. The user must
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
137
make sure no other uninstallers exist in the same product directory before running
this uninstallation.
Operator response
Verify the currently installed IBM Tivoli Composite Application Manager for
WebSphere products, and follow the IBM Tivoli Composite Application Manager
for WebSphere Installation and Customization Guide for instructions about
uninstallations for all installed products before proceeding with the uninstallation.
CYNCR8517W: One of the HP Kernel parameters is not set to
a WebSphere Application Server recommended value in the
/stand/system file. The installation will continue.
Explanation
For better performance, WebSphere Application Server recommends specific Kernel
parameters to be updated on HP-UX.
Operator response
If any performance degradation is noticed, update the required Kernel parameters
as documented in the "Prerequisites and pre-installation for Managing Server on
UNIX" chapter of the ITCAM for Application Diagnostics Installation and
Customization Guide.
CYNCR8518E: The host name host name is not fully qualified.
Provide a fully qualified host name or IP address.
Explanation
The host name must be fully qualified.
Operator response
Enter a host name that the Domain Name System service can resolve before you
proceed. You must provide the fully qualified host name or the IP address of the
host.
CYNCR8519E: The server server name appears to be down or
unreachable.
Explanation
An attempt was made to query the server for configuration data. However the
attempt failed.
Operator response
Verify that the server is specified correctly, and use the administrative console to
see that it is up.
CYNCR8520E: Select a server for monitoring.
Explanation
No server was selected for monitoring.
138
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
Select one of the listed servers.
CYNCR8521E: Server server is not in the list of known
servers: server list.
Explanation
A server was requested for instrumentation during silent install. However, it is not
one of the known servers.
Operator response
Select one of the listed servers.
CYNCR8522E: The system was unable to retrieve a list of
known servers from server server using SOAP port port.
Explanation
An attempt was made to retrieve a list of known servers using the information that
you have provided. Either the connection failed due to an invalid user name or
password, or the server does not have the administrative service enabled.
The server might not have administrative privileges if it is a member of a cluster.
You might want to specify the cluster manager host and SOAP port in that case.
Operator response
Check for correct the user name and password. Check the installer trace log to see
what error message WebSphere has given for the failed connection.
CYNCR8523I: The system is configuring server server.
Explanation
No additional information is available for this message.
CYNCR8524I: The system is unconfiguring server server.
Explanation
No additional information is available for this message.
CYNCR8525E: There was a failure while configuring server
server.
Explanation
No additional information is available for this message.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
139
CYNCR8526E: There was a failure while unconfiguring the
Data Collector on application server server.
Explanation
An error occurred while unconfiguring the Data Collector on the application
server.
Application server(s) must be running during unconfiguration. For ND
environments, Node Agent and Deployment Manager must also be running.
Operator response
Check the logs to see the cause of failure. Rerun the unconfiguration to remove the
Data Collector.
CYNCR8527I: The application servers associated with this
Data Collector must be unconfigured before the uninstallation
can complete. The uninstallation program will assist you in
removing the configuration from these servers.
Explanation
No additional information is available for this message.
CYNCR8528E: The Installer is unable to write to directory
directory.
Explanation
IBM Tivoli products write logs in the Tivoli Common Logging Directory. This
includes installation logs, and runtime logs.
Operator response
Ensure that the installer and runtime have permission to write to the Tivoli
Common Logging Directory, as specified above.
CYNCR8529E: Unable to determine if the following application
server, Vendor=vendor, AppServerType=serverType,
Version=appServerVersion, meets the prerequisites in the file
dcprereqsFile.
Explanation
A check was made to see if the application server and operating system meet all
the prerequisites using the DCPrereqsCheck.xml file and the check failed.
Operator response
Consult the product documentation to make sure that application server and
operating system are supported before continuing. Click Yes to continue
configuring the Data Collector. Click No to stop the configuration.
140
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNCR8530E: Failed to create database.
Explanation
Database and tables are created by database scripts, the scripts returned a non zero
value.
Operator response
Check the logs in MS_INSTDIR/logs directory, correct the errors and rerun the
installer. Make sure correct database information is entered, for example, user and
password.
CYNCR8531W: An ITCAM for Application Diagnostics product
already exists on this server instance.
Explanation
An ITCAM for Application Diagnostics product is already using this server
instance. Installation of more than one product component (such as a Managing
Server or Data Collector) on the same server instance may cause conflicts and is
not supported.
Operator response
To allow the installation to continue, choose another server instance.
CYNCR8532E: The file separator in the specified Managing
Server home directory is invalid.
Explanation
If the specified Managing Server is running on a Windows systems, use \ as file
separator.
If the specified Managing Server is running on a UNIX systems or Linux, use / as
file separator.
Operator response
To allow the installation to continue, make sure the file separator in the specified
Managing Server Home Directory is right.
CYNCR8601I: Stopping WebSphere Application Server.
Explanation
Operator response
CYNCR8603I: Uninstalling WebSphere Application Server.
Explanation
Operator response
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
141
CYNCR8605I: Stopping the DB2
Explanation
Operator response
CYNCR8607I: Uninstalling the DB2
Explanation
Operator response
CYNCR8609E: An error occurred while selecting the features
to be uninstalled.
Explanation
This message is displayed if there is an error during the selection of the features to
be uninstalled.
Operator response
Examine the features to be uninstalled. Select at least one of them to continue the
uninstallation.
CYNCR8611I: Dropping the DB2 Tables and Database.
Explanation
Operator response
CYNCR8613I: Uninstallation of DB2 is complete.
Explanation
Operator response
CYNCR8615I: Uninstallation of WebSphere Application Server
is complete.
Explanation
Operator response
CYNCR8617I: Dropping the Oracle Tables and Database.
Explanation
Operator response
CYNCR8619E: The server server name on profile profilehome
appears to be unreachable.
Explanation
The uninstallation cannot proceed correctly.
142
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
Click the YES button to force uninstallation; click the NO button to verify that the
server is specified correctly, and use the administrative console to determine if it is
up.
Attention: if you force uninstallation, you may have to remove the Visualization
Engine manually after uninstalling the Managing Server.
CYNCR8621E: Click the YES button to continue to force
uninstallation or click the NO button to verify that the SOAP
port is specified correctly, and use the administrative console
to determine if it is up.
Explanation
Operator response
CYNCR8623E: An error occurred while trying to validate the
response file path.
Explanation
This message is displayed if you did not enter a value in the response file path
field or if the current user does not have write authority for the directory entered
in the response file path field.
Operator response
Specify a writable directory and a valid response file name.
CYNCR8625E: An error occurred while trying to validate the
option choosing on this panel.
Explanation
This message is displayed if the non of the two options is selected.
Operator response
Select one of two options on the panel at least.
CYNCR8627I: An warning occurred while trying to validate the
specified response file name.
Explanation
This message is displayed if the specified response file existed already.
Operator response
Select "YES" to continue to use existing file and the file will be overwrited, select
"NO" to back to specify another file name.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
143
CYNCR8629E: An error occurred while trying to validate the
specified response file name.
Explanation
This message is displayed if the specified response file existed already while the
current user account do not have write authority on this file.
Operator response
Modify the file atrribute to ensure the existing file is writable or choose another file
name.
CYNCR8631E: An error occurred while trying to validate the
specified response file name.
Explanation
This message is displayed if the current user account do not have write authority
on the directory where the response file will be generated.
Operator response
Modify the folder attribute to ensure the specified directory is writable or choose
another directory.
CYNCR8633E: An error occurred while trying to validate the
specified response file name.
Explanation
This message is displayed if the current user input is a directory.
Operator response
Specify a file name with full file path.
CYNCR8635I: The uninstaller detected that the ITCAM for
Application Diagnostics and J2EE Managing Server Version
6.1 is still in running.
Explanation
The Managing Server must be stopped first before the uninstallation.
Operator response
Click the YES button to stop the Managing Server and continue with the
uninstallation or click the NO button to stay at the current panel. You can stop the
Managing Server manually by taking the following actions:
v From the Windows Start menu, select (All) Programs > ITCAM for Application
Diagnostics and J2EE Managing Server Version 6.1 > am-stop.sh.
v From a UNIX shell environment, enter the Managing Server home directory and
run the command "sh bin/am-stop.sh"
144
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNCR9100E: The installation program cannot connect to the
specified database.
Explanation
An error occured when the installation program try to connect to the specified
database.
Operator response
Ensure that the database is running and accessible in the network. Confirm that
the information you entered for the database is correct before you continue the
installation. If the error still exist, it may be caused by some environment errors of
OS or Database. To resolve this error, review the installation trace log file,
trace-install.log, for more information about the failure. The log file is located in
the common logging directory.
CYNCR9101E: The ojdbc14.jar file was not found in the
specified JDBC path.
Explanation
The specified JDBC path must be a directory containing the ojdbc14.jar file.
Operator response
Specify the correct JDBC path. The file is located in the ORACLE_HOME\jdbc\lib
directory of the Oracle client on Windows systems or the ORACLE_HOME/jdbc/
lib on UNIX systems.
CYNCR9102E: The specified ORACLE Sqlplus User does no
exists.
Explanation
This user must be a OS user, that has right to access ORACLE Sqlplus.
Operator response
CYNCR9103E: The db2profile file was not found in the
specified User's Home.
Explanation
The specified DB2 Instance User's Home must be a DB2 instance user's home
directory containing the db2profile file.
Operator response
Specify the correct DB2 Instance User. The specified User's home must have a
db2profile file.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
145
CYNCR9104E: The db2cc.jar and db2jcc_license_cu.jar files
was not found in the specified JDBC path.
Explanation
The specified JDBC path must be a directory containing the db2cc.jar and
db2jcc_license_cu.jar files.
Operator response
Specify the correct JDBC path. The file is located in the basdir\sqllib\java directory
of the DB2 client on Windows systems or the DB2 instance user home directory on
UNIX systems.
CYNCR9105E: The specified the installation directory of DB2
is invalid.
Explanation
The specified the installation directory of DB2 is not clean.
Operator response
Specify a clean directory for DB2 installation.
CYNCR9106E: The installation cannot connect to the specified
database.
Explanation
The port number you entered is not the port of the specified database.
Operator response
Ensure that the database is running and accessible in the network. Confirm that
the port number you entered for the database is correct before you continue the
installation.
CYNCR9107E: The installation cannot connect to the specified
database.
Explanation
The database name you entered does not exist.
Operator response
Ensure that the database is running and accessible in the network. Confirm that
the database name you entered for the database is correct before you continue the
installation.
CYNCR9108E: The installation cannot connect to the specified
database.
Explanation
The user id and password you entered is invalid.
146
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
Ensure that the database is running and accessible in the network. Confirm that
the user id and password you entered for the database is correct before you
continue the installation.
CYNCR9109E: The installation cannot connect to the specified
database.
Explanation
The SID you entered does not exist.
Operator response
Ensure that the database is running and accessible in the network. Confirm that
the database name you entered for the database is correct before you continue the
installation.
CYNCR9110E: The installation cannot connect to the specified
database.
Explanation
The user id and password you entered is expired.
Operator response
Ensure that the database is running and accessible in the network. Log on the
machine with the user id you specified, and change the password of the user id as
the OS required.
CYNCR9111E: The installation cannot connect to the specified
database.
Explanation
The DB2 Server you specified is setup to use CLIENT Authentication, which
resulted in the connection authorization failure.
Operator response
Reconfigure the DB2 server, to use SERVER Authentication instead of CLIENT
Authentication. This can be done by using DB2 command: db2 update dbm cfg
using authentication server, and restart DB2 server.
CYNCR9112E: NIS is enabled on this machine. Therefore the
option to create users is unavailable.
Explanation
The typical installation of Managing Server is unavailable.
Operator response
Use the custom installation and use existing users for DB2 Database server
installation.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
147
Or using an existing Database server.
CYNCR9113E: The DB2 instance user's home directory path
fails the required minimum free disk space check.
Explanation
The typical installation of Managing Server is unavailable.
Operator response
Use the custom installation and specify another directory with enough free space
for DB2 instance user's home.
CYNCR9114E: The installation program failed to create the
bufferpool, tablespace, database, or tables. You can create the
bufferpool, tablespace, database, or tables manually.
Explanation
This message is displayed if the creation of the bufferpool, tablespace, database, or
tables fails.
Operator response
You must create the database, bufferpool, tablespace, or tables manually. Follow
the steps in the installation guide for configuring an existing database to be used
with the Managing Server.
CYNCR9115E: The DB2 8.2 installation image directory that
was specified is not valid.
Explanation
Your system is HP-UX 11i v2 (B.11.23.0409) PA-RISC. The DB2 image must be a
DB2 installation image at FP9 level or later. Or you can apply a workaround.
Operator response
Take one of the following actions:
1. Use a DB2 installation image at FP9 level or later.
2. Apply a workaround for your current image. See the following Web site:
http://www-1.ibm.com/support/docview.wss?rs=71&uid=swg21223704.
CYNCR9200I: Required Field: Managing Server Host Selection
Explanation
No additional information is available for this message.
148
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNCR9200W: Some errors occur during restarting the
WebSphere Application Server.
Explanation
This message is displayed if there is an error during restarting the WebSphere
Application Server.
Operator response
Examine the WebSphere Application Server logs to determine why the installation
failed. Restart WebSphere Application Server manually, after installation.
CYNCR9201I: Required Field: Database Host
Explanation
No additional information is available for this message.
CYNCR9202I: Required Field: Port Number
Explanation
No additional information is available for this message.
CYNCR9203I: Required Field: Database Instance User ID
Explanation
No additional information is available for this message.
CYNCR9204I: Required Field: Database Instance Password
Explanation
No additional information is available for this message.
CYNCR9205I: Required Field: Database Schema User ID
Explanation
No additional information is available for this message.
CYNCR9206I: Required Field: Database Schema Password
Explanation
No additional information is available for this message.
CYNCR9207I: Required Field: Oracle Sqlplus User
Explanation
No additional information is available for this message.
CYNCR9208I: Required Field: Oracle Home
Explanation
No additional information is available for this message.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
149
CYNCR9209I: Required Field: DBA User ID
Explanation
No additional information is available for this message.
CYNCR9210I: Required Field: DBA Password
Explanation
No additional information is available for this message.
CYNCR9211E: The installer was unable to get the topology
information from WebSphere Application Server.
Explanation
This problem is usually caused by the follow reason:
Incorrect SOAP port.
Server instance of specified WebSphere Application Server has been configured by
other ITCAM product.
Operator response
Click back to specify another WebSphere Application Server or SOAP, and try
again.
CYNCR9211I: The Oracle Home you entered is invalid
Explanation
No additional information is available for this message.
CYNCR9212E: The WebSphere Application Server 6.1
installation image directory that was specified is not valid.
Explanation
The specified directory is not the base version of WebSphere Application Server
6.1.
Operator response
Take one of the following actions:
1. Choose a directory with valid WebSphere Application Server 6.1 installation
images.
2. Click the check box to perform an embedded installation using CDs.
CYNCR9213E: The WebSphere Application Server 6.1
installation image directory that was specified is not valid.
Explanation
Current® OS is 32bit platform, but The specified directory is not the 32bit version
of WebSphere Application Server 6.1.
150
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
Take one of the following actions:
1. Choose a directory with valid WebSphere Application Server 6.1 installation
images.
2. Click the check box to perform an embedded installation using CDs.
CYNCR9214E: An error occurred while trying to validate the
WebSphere Application Server information entered on the this
panel.
Explanation
Validation is done by executing the wsadmin script and the output from the
command is given below.
In most cases, this is caused by entering the wrong SOAP port, user ID and
password, or the WebSphere Application Server might be down.
Operator response
Ensure that the WebSphere Application Server is up and running. It can be started
by running the startServer script located in the bin directory of the home directory
for WebSphere Application Server.
Also, ensure that the correct SOAP port is entered. The port number can be viewed
in the WebSphere Application Server administrative console.
CYNCR9215E: The specified installation destination of
WebSphere is not valid.
Explanation
The specified directory is not clean.
The specified directory is already registered in the registry of WebSphere.
Operator response
Specify another directory and try again.
CYNCR9216E: The system temporary space is too small to
install a new WebSphere Application Server.
Explanation
The WebSpere Application Server Installation program requires at least 400® MB
free space of system temporay directory.
Operator response
To continue Managing Server installation, you can select custom installation and
using existing WebSphere Application Server.
Or you can free the space of system temporary directory and try again.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
151
CYNCR9500E: The Visualization Engine installation failed.
Explanation
This message is displayed if there is an error while running the Visualization
Engine installation.
Operator response
Examine the installation logs and WebSphere logs to determine why the
installation failed.
CYNCR9501E: The specified port number (portNumber) is
invalid.
Explanation
The port number is already in use, or the port number was already entered in
another field.
Operator response
Specify another port number.
CYNCR9601E: An error occurred while trying to validate the
WebSphere Application Server information entered on this
panel.
Explanation
The Data Collector Configuration Tool did not receive a valid response within the
allotted time when it was trying to validate the information with WebSphere
Application Server's wsadmin utility.
In most cases, this is caused by an incorrect username or password, or wsadmin is
experiencing some problems.
Operator response
Make sure that the username and password for WebSphere Application Server are
correct.
Also, make sure that WebSphere Application Server's wsadmin utility is running
correctly.
CYNCR9602E: An error occurred while trying to run
WebSphere Application Server's wsadmin utility. The following
are error messages from wsadmin: “wsadminMsg ”
Explanation
In most cases, this is caused by redundant directories in WebSphere Application
Server's configuration directory.
152
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
Make sure that WebSphere Application Server's wsadmin utility is running
correctly.
Use the following command in wsadmin to check that wsadmin is running
correctly:
$AdminConfig getid /Cell:/
CYNCR9603E: An error occurred while trying to run
WebSphere Application Server's wsadmin utility. The following
are error messages from wsadmin: “wsadminMsg ”
Explanation
Invocation of wsadmin failed.
Operator response
Make sure that WebSphere Application Server's wsadmin utility is running
correctly.
Use the following command in wsadmin to check that wsadmin is running
correctly:
$AdminConfig getid /Cell:/
CYNCR9604E: An error occurred while trying to validate the
WebSphere Application Server information entered on this
panel.
Explanation
The cell ID for WebSphere Application Server that was retrieved from wsadmin
does not match the local topology.
Operator response
Make sure that the host name of WebSphere Application Server is correct. For ND
environments the host name must be the Deployment Manager's host name
CYNCR9605E: The -Xrun or -agentlib has already been
configured in the generic JVM arguments for WebSpere
Application Server server
Explanation
The Data Collector Configuration Tool cannot apply configuration on this server.
Operator response
Choose another WebSphere Application Server to configure.
Or remove the -Xrun or -agentlib option that has already been configured in the
generic JVM arguments and restart the Data Collector Configuration Tool to
continue.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
153
CYNCR9606E: The Auto Synchronization Service of the
NodeAgent node is disabled. Before continuing the Data
Collector configuration, make sure the local configuration
repository for WebSphere Application Server is consistent
with the master repository for the Deployment Manager.
Explanation
The Data Collector Configuration Tool will read the JVM parameters of the
application server from the WebSphere local configuration repository.
Operator response
Log into the Administrative Console for the Deployment Manager and perform a
node synchronization, or use the WebSphere Application Server syncNode
command.
CYNCR9607E: The Auto Synchronization Service of the
NodeAgent node is disabled. Before continuing the Data
Collector configuration, perform a node synchronization.
Explanation
Before continuing the Data Collector Configuration, the local configuration
repository for WebSphere Application Server must be consistent with the master
repository for the Deployment Manager.
The Data Collector Configuration Tool will read the JVM parameters of the
application server from the WebSphere local configuration repository.
Operator response
Log into the Administrative Console for the Deployment Manager and perform a
node synchronization, or use the WebSphere Application Server syncNode
command.
CYNCR9608E: The Auto Synchronization Service of the
NodeAgent node is disabled. The Data Collector Configuration
Tool will perform a node synchronize action before continuing
with the Data Collector configuration.
Explanation
Ensure that the NodeAgent is up and running. It can be started by running the
startNode script located in the bin directory of the home directory for WebSphere
Application Server.
Before continuing the Data Collector configuration, the local configuration
repository for WebSphere Application Server must be consistent with the master
repository for the Deployment Manager.
The Data Collector Configuration Tool will read the JVM parameters of the
application server from the WebSphere local configuration repository.
154
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
Click OK to let the Data Collector Configuration Tool perform the node
synchronization.
Click Cancel to skip the node synchronization.
CYNCR9609E: An error occurred while trying to synchronize
node node. The following are error messages from wsadmin:
“wsadminMsg ”
Explanation
Make sure that the NodeAgent is up and running. It can be started by running the
startNode script located in the bin directory of the home directory for WebSphere
Application Server.
Operator response
Perform the node synchronization manually.
Log into the Administrative Console for the Deployment Manager and perform a
node synchronization, or use WebSphere Application Server's syncNode command.
CYNCR9610E: An error occurred while trying to synchronize
node node.
Explanation
Wsadmin did not respond correctly within the expected time.
Make sure that the NodeAgent is up and running. It can be started by running the
startNode script located in the bin directory of the home directory for WebSphere
Application Server.
Operator response
Perform the node synchronization manually.
Log into the Administrative Console for the Deployment Manager and perform a
node synchronization, or use WebSphere Application Server's syncNode command.
CYNCR9611I: The default GC log file location orglog is
changed to newlog. If you delete the new GC log file directory
after configuration, it might cause the WebSphere Application
Server not to start up.
Explanation
No additional information is available for this message.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
155
CYND Messages: Data Collector
The following messages relate to the IBM Tivoli Composite Application Manager
for WebSphere data collector. All such messages have IDs in the range CYND0012I
to CYND7163I and CYNPE0001I to CYNPE0011E.
Data Collector on z/OS
CYND0012I: The Data Collector stopping.
Explanation
Status message for the Data Collector.
CYND0013I: The Data Collector stopped.
Explanation
Status message for the Data Collector.
CYND0014I: The Data Collector starting.
Explanation
Status messages for the Data Collector.
CYND0015I: The Data Collector started.
Explanation
Status message for the Data Collector.
CYND0026I: Event Agent started.
Explanation
A status message during the start-up of the Data Collector.
CYND0027E: Failed in publishing records to Publish Server.
Explanation
The Data Collector encountered a communication error when its Event Agent
attempted to send the records to the publish server.
Operator response
Ensure the Publish Server is running correctly. If the problem persists, contact IBM
Software Support.
CYND0031I: Getting Publish Engine from kernel.
Explanation
The Data Collector tried to download the interface code to the Publish Server from
the Kernel.
CYND0032I: Publish Engine successfully downloaded from
kernel.
Explanation
The Data Collector successfully downloaded the interface code to the Publish
Server from the Kernel.
156
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND0033I: The publish engine was successfully downloaded
from the Kernel.
Explanation
The Data Collector successfully downloaded the interface code to the Publish
Server from the Kernel.
CYND0040I: The include list is List.
Explanation
During startup, the Data Collector displays a list of classes which will be
monitored when the Profiling mode is turned on. This list must be specified as a
sub-list of the exclude list.
Operator response
Determine whether the list is correct. This list can be modified by reconfiguring the
data collector.
CYND0042I: Exclude List: List.
Explanation
During start-up, the Data Collector displays a list of classes whose methods will
not be monitored when the Profiling mode is turned on.
Operator response
Determine whether the list is correct. This list can be modified by reconfiguring the
data collector.
CYND0046W: record1/record2 records dropped.
Explanation
The Event Agent of the Data Collector has to drop a number of records due to
either network slowdown or an overloaded Publish Server.
Operator response
Determine whether the Publish Server is bottlenecked on CPU capacity or a
network congestion between the Data Collector and the Publish Server. Restart the
Publish Server if desirable. Contact IBM support if the problem persists.
CYND0049I: Connected to Publish ServerHost:Server with send
buffer size Buffer Size
Explanation
The Data Collector has connected to the Publish Server at the specified IP address
and port number. The send buffer size is set to the value specified by the Publish
Server.
CYND0079E: Error in getting stack trace for thread Thread ID
Explanation
Command Agent failed to get the stack trace for the specified thread.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
157
Operator response
Report to IBM Support.
CYND0087I: The logging level changed from Level to Level1.
Explanation
Indicates that a request to change the logging level is complete.
CYND0219E: Failed to GetStringUTFChars
Explanation
An error occurred while converting strings to UTF8.
Operator response
Report to IBM Support.
CYND0220E: generateThreadDump failed
Explanation
The thread dump info field is null.
Operator response
Report to IBM Support.
CYND0221E: generateThreadDump failed
Explanation
Generating thread dump failed.
Operator response
Report to IBM Support.
CYND0222E: Can't get ThreadDumpInfo class
Explanation
Cannot get the thread dump information.
Operator response
Report to IBM support.
CYND0223E: Cannot find method Method
Explanation
Cannot find method name.
Operator response
Report to IBM Support.
158
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND0224E: Failed to allocate memory
Explanation
Memory allocation failed.
Operator response
Report to IBM support.
CYND0225E: Event Agent already started
Explanation
Event agent has already started.
Operator response
None.
CYND0226E: Failed to obtain jvmmi handle for heap dump
Explanation
Getting JVMMI handle for heap dump has failed.
Operator response
Report to IBM Support.
CYND0227E: No javacore is generated.
Explanation
Javacore is not generated.
Operator response
None
CYND0228E: Unable to get RAS
Explanation
Getting RAS has failed.
Operator response
Report to IBM Support.
CYND0229I: Number of CPU = Number of CPU
Explanation
Display the machine number of cpu.
Operator response
None.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
159
CYND0230E: Error in getting number of cpu with return code =
Error code
Explanation
Error in getting number of cpu.
Operator response
Report to IBM support.
CYND1001I: Native Custom Service initialized successfully.
Explanation
See Message.
Operator response
CYND1002E: Custom Service initialization failed because JVMPI
could not be initialized
Explanation
Custom Service initialization failure is because the JVM argument -Xrun is not
being specified correctly.
Operator response
Refer to the Installation Guide and verify that the Application server is configured
correctly.
CYND1003I: Native Custom Service shutdown complete.
Explanation
See Message.
Operator response
CYND1004I: Native probe started successfully.
Explanation
See Message.
Operator response
CYND1005I: Native probe stopped successfully.
Explanation
See Message.
Operator response
CYND1006E: The am.home system property is undefined.
Explanation
The Installer failed to set am.home during installation.
160
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
Refer to the Installation Guide for information about specifying am.home correctly.
CYND1007W: The weblogic.Domain system property is
undefined.
Explanation
The Installer failed to set weblogic.Domain during installation.
Operator response
Refer to the Installation Guide for information about specifying weblogic.Domain
correctly.
CYND1008W: The am.nodename system property is undefined.
Explanation
The Installer failed to set am.nodename during installation.
Operator response
Refer to the Installation Guide for information about specifying am.nodename
correctly.
CYND1009W: The weblogic.Name system property is undefined.
Explanation
The Installer failed to set weblogic.Name during installation.
Operator response
Refer to the Installation Guide for information about specifying weblogic.Name
correctly.
CYND1010W: The am.appserver system property is undefined.
Explanation
The Installer failed to set am.appserver during installation.
Operator response
Refer to the Installation Guide for information about specifying am.appserver
correctly.
CYND1011I: ProbeManager started successfully.
Explanation
See Message.
Operator response
CYND1012E: Failed to start ProbeManager.
Explanation
JVMPI initialization failed.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
161
Operator response
Check the application configuration and Installation Guide. Verify that the required
JVM arguments are set correctly.
CYND1013F: JVMPI was not initialized by native probe start
exiting.
Explanation
Failure to initialize JVMPI might be caused by either a corrupted libam.so file, or
JVM arguments are set incorrectly.
Operator response
Check the application configuration and Installation Guide. Verify that the required
JVM arguments are set correctly.
CYND1014I: Probe manager stopped successfully.
Explanation
See Message.
Operator response
CYND1015F: JVMPI initialization failed.
Explanation
Failure to initialize JVMPI might be caused by either a corrupted libam.so file, or
JVM arguments that are set incorrectly.
Operator response
Check the application configuration and Installation Guide. Verify that the required
JVM arguments are set correctly.
CYND1016I: Initialized event interface successfully.
Explanation
See Message.
Operator response
CYND1017E: Failed to initialize JVMMI.
Explanation
Failure to initialize JVMMI may be caused by either a corrupted libam.so file, or
JVM arguments are set incorrectly.
Operator response
Check the application configuration and Installation Guide. Verify that the required
JVM arguments are set correctly.
162
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND1018I: Using tracing mode: mode_str(mode_int), and
monitoring level is: mod_level
Explanation
There are three tracing modes: classic, new and hybrid. The default tracing mode is
new. There are three monitoring (MOD) levels. They are Production (L1), Problem
Determination (L2) and Debug Method Trace (L3). The default MOD level is L1.
CYND1019E: Error occured during encryption.
Explanation
The error occurred as the result of a corrupted user ID and password.
Operator response
Check the input user ID and password, and verify that they are in clear text.
CYND1020E: Invalid file name.
Explanation
The filename containing the userID and password is invalid.
Operator response
Verify that the properties certificate.path and keystore.location are set correctly in
datacollector.properties.
CYND1021E: Invalid userID or password.
Explanation
UserID or password is missing.
Operator response
Enter a valid userID and password.
CYND1022E: Invalid file name.
Explanation
The filename containing userID and password is invalid.
Operator response
Verify that the properties certificate.path and keystore.location are set correctly in
datacollector.properties.
CYND1023E: Invalid userID or password.
Explanation
UserID or password is missing.
Operator response
Refer to the Installation Guide and enter a valid user ID and password.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
163
CYND1024E: Could not open the file: filename
Explanation
Either the file does not exist, or the file does not have read permissions.
Operator response
Verify that the file exists and has read permission
CYND1025E: No data in the file: filename
Explanation
The file is empty.
Operator response
Verify that the file contains a valid userID and password.
CYND1026E: Invalid file name, userID or password.
Explanation
Either the file name, userID or password is missing.
Operator response
Refer to the Installation Guide and verify that a valid ker store, certificate, user ID
and password are provided.
CYND1027E: Could not open the file for writing: filename
Explanation
The error may be caused by no write permissions on the file.
Operator response
Verify the account has write permissions to the file.
CYND1028E: The input string is corrupt.
Explanation
The userID and password is too long.
Operator response
Verify that the userID and password do not exceed the maximum length.
CYND1029E: UID, PASSWORD or filename is NULL.
Explanation
The userID, password or generated password filename is missing.
Operator response
Refer to the Installation Guide and verify that a valid user ID, password and
generated password filename exist.
164
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND1030E: Your actual password and decrypted password
don't match
Explanation
The password may contain a space.
Operator response
Turn off Caps Lock and ensure there are no spaces in the password.
CYND1031E: The userID read from the file is not the same as UID
entered.
Explanation
Verify that you typed in a valid userID.
Operator response
Enter a valid userID.
CYND1032E: Password read from the file is not the same as the
password entered.
Explanation
Verify that you typed in a valid password.
Operator response
Enter a valid password.
CYND1033I: Verified userID and password by reading the created
file, passwordfile. filename was properly created.
Explanation
See Message.
Operator response
CYND1034E: Encrypted password string is corrupt.
Explanation
The password is too long.
Operator response
Verify that the password does not exceed the maximum length.
CYND1035E: Error occurred during decryption.
Explanation
The password may be corrupt.
Operator response
Enter a valid password
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
165
CYND1036E: The password is too long. It should be less than
max_len characters.
Explanation
The password is too long.
Operator response
Verify that the password does not exceed the maximum length.
CYND1037E: JVMPI could not create a Raw Monitor for
GlobalLock.
Explanation
An internal error has occurred.
Operator response
Restart the Application Server.
CYND1038E: Global lock was created before initialization of
JVMPI.
Explanation
An internal error has occurred.
Operator response
Restart the Application Server.
CYND1039W: This is an unknown event type, TypeID: evt_type
Explanation
An internal error has occurred.
Operator response
Restart the Application Server.
CYND1040E: The EventAgent was not started and cannot
manage ThreadData.
Explanation
The EventAgent failed to start.
Operator response
Refer to the Installation Guide for the Data Collector. Restart the Application
Server.
CYND1041W: Failed to send data.
Explanation
The connection to the Publish Server is broken.
166
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
Check the network connection between the Data Collector and the Managing
Server. Verify that the connection is established correctly.
CYND1042E: Event Queue is NULL for Thread, TID: tid
Explanation
An internal error has occurred.
Operator response
Restart the Application Server.
CYND1043W: Overall events dropped/deleted:evtDropCnt
Explanation
The Publish Server is down.
Operator response
Check the Managing Server and verify the Publish Server is up and running.
CYND1044I: Events dropped cnt for thread threadName because
they exceeded event queue limit of queueLimit
Explanation
This message indicates that either the event queue size is too small or the
frequency of sending data to the Publish Server is too low. If this message occurs
repeatedly, the metrics collected on the Managing Server will be incorrect.
Operator response
Increase the event queue size and publish frequency. In datacollector.properties,
modify the property internal.probe.event.queue.size.limit and
internal.probe.publishing.frequency.
CYND1045W: Thread data creation failed.
Explanation
The server is out of native memory.
Operator response
Check memory utilization on the server.
CYND1046I: EvtAgentManager started.
Explanation
See Message.
Operator response
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
167
CYND1047I: EvtAgentManager stopped.
Explanation
See Message.
Operator response
CYND1048E: Class file is corrupt.
Explanation
The ClassLoadHookEvent is corrupted. Therefore, eventHandler failed to get
constant pool.
Operator response
Restart the Application Server.
CYND1049E: Bad class file magic number:magic
Explanation
The class file is corrupted.
Operator response
Restart the Application Server.
CYND1050E: Failed to open library: libName
Explanation
The library path was not set properly/
Operator response
Refer to the Installation Guide. Verify that the library path is set correctly.
CYND1051I: Memory limit is less than the minimum limit:
memLimit MB
Explanation
The minimum memory limit is 4MB
Operator response
Verify that the property internal.memory.limit in datacollector.properties is
assigned a value within the limits.
CYND1052I: Memory monitor properties, ULimit: memUlimit bytes,
Accept Threshold: threadHold bytes, URL Limit: urlUlimit, SQL
Limit: sqlUlimit
Explanation
See Message.
Operator response
168
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND1053I: Queue counter resets every resetTimerCount
iterations.
Explanation
By default, the counters used by memory monitor reset every hour.
CYND1054W: Memory Limit reached, Data Collector stopped
accepting data, Limit: usedMemUlimit Memory Utilization:
memTaken
Explanation
This warning may occur when the rate of receiving events is higher than the rate
of publishing events.
Operator response
Check network configuration, and verify that there is enough network bandwidth
to transfer data to Publish Server.
CYND1055I: Memory utilization is below the limit; the Data
Collector is accepting data, Limit: usedMemUlimit Memory
Utilization: memTaken
Explanation
See Message.
Operator response
CYND1056W: Network Agent Thread is not started/alive/ready;
rejecting send data.
Explanation
The Data Collector failed to initialize the Network Agent.
Operator response
Restart the Application Server.
CYND1057W: The queue is full and exceeds the buffer limit.
Explanation
The network is slow, and it takes significant amount of time to publish data.
Operator response
Check the network configuration.
CYND1058W: Publish Server lookup failed.
Explanation
The Kernel of the Publish Server is down.
Operator response
Check the Managing Server and verify all the components are up and running.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
169
CYND1059E: The Data Collector failed to connect to host %s
/port %d. Error number is %d
Explanation
The Data Collector failed to establish a connection to the Publish Server.
Operator response
Check the Managing Server configuration and verify that the Publish Server ports
are set correctly.
CYND1060I: Successfully connected to Publish Server Host: %s
Port: %d Buffer Size: %d
Explanation
See Message.
Operator response
CYND1061E: Socket write to Publish Server failed, [%s:%d],
ERRNO: %s
Explanation
The Data Collector failed to write to the socket.
Operator response
Check the network configuration and the error code.
CYND1062I: Network agent thread started.
Explanation
See Message.
Operator response
CYND1063I: Successfully connected to the Publish Server
socket.
Explanation
See Message.
Operator response
CYND1064E: Failed to connect to the Publish Server socket.
Explanation
The Publish Server may be down.
Operator response
Check the Managing Server configuration.
170
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND1065W: Could not obtain Publish Server proxy details from
the Kernel.
Explanation
The Publish Server could be down.
Operator response
Check the Managing Server configuration.
CYND1066I: NetworkAgentManager started.
Explanation
See Message.
Operator response
CYND1067I: NetworkAgentManager stopped.
Explanation
See Message.
Operator response
CYND1068E: am.home was not found; failed to initialize the
Property Manager.
Explanation
The Installer failed to set it during installation.
Operator response
Refer to the Installation Guide and specify it correctly.
CYND1069E: Default property file %s not found.
Explanation
The Installer failed to copy it during installation.
Operator response
Refer to the Installation Guide and copy it manually.
CYND1070I: Using property file %s.
Explanation
See Message.
Operator response
CYND1071I: PropertyMgr started.
Explanation
See Message.
Operator response
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
171
CYND1072I: Thread Manager started.
Explanation
See Message.
Operator response
CYND1073I: Thread Manager stopped.
Explanation
See Message.
Operator response
CYND1074E: Failed to retrieve the command arguments for WAS.
Explanation
An internal error has occurred.
Operator response
Restart the Application Server.
CYND1075E: Failed to retrieve command line arguments for
Stand Alone Java.
Explanation
An internal error has occurred.
Operator response
Restart the Application Server.
CYND1076E: Failed to construct ThreadDumpInfo object.
Explanation
The server is out of Java heap memory.
Operator response
Increase Java heap size and restart the Application Server.
CYND1077E: Probe is disabled; cannot return stack trace.
Explanation
The Data Collector is not configured yet.
Operator response
Configure the Data Collector from the Managing Server.
172
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND1078I: Using modfile: %s
Explanation
See Message.
Operator response
CYND1079I: Failed to write modfile.
Explanation
There are no write permissions on mod file.
Operator response
Verify that am.home/etc has both read and write permissions.
CYND1080I: Using probe level %d.
Explanation
See Message.
Operator response
CYND1081I: Native library build TIME : %s DATE: %s
Explanation
See Message.
Operator response
CYND1082I: Successfully registered
defineNativeMethodsForClassNative for
com.cyanea.bcm.bootstrap.BcmBootstrap .class.
Explanation
See Message.
Operator response
CYND1083E: Cannot find com.cyanea.bcm.bootstrap
.BcmBootstrap.class.
Explanation
The JVM arguments -Xbootclasspath is not configured properly.
Operator response
Check the Installation Guide and verify that JVM is configured properly.
CYND1084I: Heap Snapshot not supported by default; set
internal.doheapdump=true to activate it.
Explanation
This message only applies to Solaris OS. Heap snapshot might crash the server
when it is under load.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
173
Operator response
Set internal.doheapdump=true to activate heap snapshot on Solaris after careful
consideration.
CYND1085W: Failed to open stdout.
Explanation
The cause of this error is that either cyanea.probe.stdout is not defined or the value
is incorrect.
Operator response
Verify that cyanea.probe.stdout is configured with the proper value.
CYND1086E: Unable to send CTRL+BREAK event to JVM
process. Err(%ld)
Explanation
The Application Server was started as a Windows service. CTRL+BREAK only
works when the server is started from a console.
Operator response
Start the server from a console and try again.
CYND1087E: Unable to send SIGQUIT to JVM process. Err(%ld)
Explanation
Java process hangs or is under load.
Operator response
Do not try to get thread dump or a stack trace when the server is under load. Try
later when the server load is lighter.
CYND1088E: Cannot get Java system property
cyanea.probe.stdout.
Explanation
The Installer failed to set it properly. This property is only needed for hotspot jdk.
Operator response
Refer to the Installation Guide and configure it correctly.
CYND1089E: Cannot open cyanea.probe.stdout:%s
Explanation
The possible cause of this error is that the wrong value was specified. For
WebSphere 5 and WebSphere 6, it is defined as WAS_home/serverName/logs/
native_stdout.log; for weblogic stand alone server, it is defined as java process
standard output; for weblogic remotely managed server, it is defined as
WL_home/common/NodeManagerLogs/domainName_serverName/serverName_output.log
174
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
Verify that cyanea.probe.stdout is configured with the proper value.
CYND1090E: Failed to retrieve command line arguments for
WebLogic.
Explanation
An internal error has occurred.
Operator response
Restart the Application Server.
CYND1100I: Region Mask from Kernel = Kernel
Explanation
Received region mask from kernel.
CYND1102I: Region ID = 0xID8X
Explanation
Region ID of the datacollector.
CYND1103I: Region Mask = 0xMask8X
Explanation
Region mask of the datacollector.
CYND1104E: Cannot get the server common storage with error
number = Error
Explanation
Cannot get the server common storage.
Operator response
Report to IBM Support.
CYND1105I: Enqueue server, Server, exclusively with return code
= RC
Explanation
Return code when locking the server common storage exclusively.
Operator response
Report to IBM support if the return code does not equal 0 or 4.
CYND1106I: Enqueue server, Server, shared with return code =
RC
Explanation
Return code when locking the server common storage shared.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
175
Operator response
Report to IBM support if the return code does not equal 0.
CYND1107I: Gps counter file = Counter
Explanation
File to persist the gps counter.
Operator response
None.
CYND1108I: Gps counter get from file = File
Explanation
Gps counter got from the file.
Operator response
None.
CYND1109I: Gps counter file, File, created
Explanation
Gps counter file created when it does not exist.
Operator response
None.
CYND1112E: Unable to open counter file, File
Explanation
Not able to open gps counter file.
Operator response
Report to IBM Support.
CYND1554I: Thread Thread has had Global Publish Server token
Token inserted into it.
Explanation
The Global Publish Server token has been inserted into the data stream flowing to
the CTG gateway.
CYND1555I: Thread Thread has called startGpsInvokeRequest.
Explanation
The system will process a Global Publish Server callback.
176
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND1556I: Thread Thread has exceeded the CommArea length
limit. No Global Publish Server token has been added.
Explanation
A Global Publish Server token has not been inserted into the data stream because
CommArea is full.
CYND1557I: Thread Thread has not had a Global Publish Server
token inserted since the call type is Token.
Explanation
Global Publish Server token has not been inserted into the data stream because the
ECI call type does not call for it.
CYND1558E: Thread Thread has encountered exception
Exception.
Explanation
An exception occurred while inserting a Global Publish Server token into
CommArea, possibly corrupting CommArea. The current CTG request may be
damaged.
Operator response
Check the status of the current CTG request on CICS®. Save the log files and report
this to IBM Software Support.
CYND1559E: Thread Thread has encountered exception
Exception.
Explanation
An exception has occurred during logging of status. This should not have any
effect on the CTG request.
Operator response
Check the status of the current CTG request on CICS.
CYND1566E: Thread Thread has encountered exception
Exception.
Explanation
An exception has occurred while restoring the CommArea returning from CICS.
Operator response
Check the status of the calling application for a possible error. Report this to IBM
Software Support.
CYND1567I: Thread Thread has called endGpsInvokeRequest.
Explanation
The product has finished tracking this CTG call.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
177
CYND1568E: Thread Thread has encountered exception
Exception.
Explanation
An exception has occurred while preparing to send data to a system resources call.
No CTG data should have been affected.
Operator response
Report this to IBM Software Support.
CYND1570E: Thread Thread has encountered exception
Exception.
Explanation
An exception occurred while gathering the protocol, URL, and port number for
this CTG request.
Operator response
Check the status of the request in CICS. Report this to IBM Software Support.
CYND1571E: Thread Thread has encountered exception
Exception.
Explanation
An exception occurred for the CTG local flow while modifying the CommArea
before calling CICS.
Operator response
Check the status of the request in CICS for possible data corruption. Report this to
IBM Software Support.
CYND1572E: Thread Thread has encountered exception
Exception.
Explanation
An exception occurred for the CTG local flow while restoring the CommArea to
the original state.
Operator response
Check the status of the calling application for possible data corruption. Report this
to IBM Software Support.
CYND1573E: Thread Thread has encountered exception
Exception.
Explanation
An exception occurred for the CTG local flow while preparing to call
endGpsInvokeRequest(). No CTG data corruption should have occurred.
178
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
Check the status of the System Resources report. Report this to IBM Software
Support.
CYND1574E: CTGCALLBACK failed to get a token.
Explanation
The Data Collector was not able to get a token.
Operator response
Report this to IBM Software Support.
CYND1574I: Thread Thread is logging to system resources:\nURL
= URL\nServer = Server\nProgram = Program\nDuration = Duration
Explanation
The protocol, URL and port number are being sent to system resources.
CYND1577I: For JMXDelegate.initialize, the user install directory
is Diectory, and the install root is Install Root.
Explanation
This is status information for initialization of the JMX proxy for configuration
service.
CYND1578W: For JMXDelegate.initialize, .init is Init.
Explanation
An exception occurred during initialization of the JMX proxy for configuration
service.
Operator response
Report this to IBM Software Support.
CYND1579W: Thread Thread has encountered exception
Exception.
Explanation
A JDBC call back (BeforeJDBC) error has occurred.
Operator response
Report this to IBM Software Support.
CYND1582W: Thread Thread has encountered exception
Exception.
Explanation
A JDBC call back (AfterJDBC) error has occurred.
Operator response
Report this to IBM Software Support.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
179
CYND1583W: Thread Thread has encountered exception
Exception.
Explanation
A JDBC call back (BeforeDataSource) error has occurred.
Operator response
Report this to IBM Software Support.
CYND1584I: Thread Thread has called
ProbeUtils.beginSQLRequest:\nSQL = Sql\nDataSource = Data
Source\nOriginated = Originated\nNode = Node
Explanation
The system will process a JDBC callback.
CYND1585I: Thread Thread has called
ProbeUtils.endSQLRequest:\nSQL = Sql\nDataSource = Data
Source\nOriginated =Originated\nNode = Node
Explanation
A JDBC callback was processed.
CYND1586I: The configuration service is disabled.
Explanation
The configuration service is not running, probably because the indicated bean was
set to false.
Operator response
If you have not intentionally disabled the configuration service, ensure that
com.ibm.websphere.management.enableConfigMBean has been set to true and then
restart.
CYND1587I: The configuration service is enabled.
Explanation
The system will process a PMI service.
CYND1588I: PMI is enabled.
Explanation
PMI will be processed.
CYND1589I: PMI is disabled.
Explanation
PMI will not be processed.
CYND1590I: JMX initialization was completed.
Explanation
See message.
180
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND1591W: The JMX proxy for the configuration service has
failed to initialize. Exception Exception has occurred.
Explanation
See message.
Operator response
Report this to IBM Software Support.
CYND1599E: Thread Thread encountered an error from IMS
callback IMS.
Explanation
An error occurred while doing an IMS™ call back.
Operator response
Report this to IBM Software Support.
CYND1600E: Thread Thread encountered an error from IMS
callback. The token is null.
Explanation
The passed token does not meet the specific definition.
Operator response
Report this to IBM Software Support.
CYND1601E: Thread Thread has encountered an error from IMS
callback functions. It expected a 4 bytes token, but the feedback
was Feed Back.
Explanation
An unexpected exception from IMS callback functions has occurred.
Operator response
Report this to IBM Software Support.
CYND1700E: Thread Thread encountered exception Exception
from JMSMQ callback functions.
Explanation
An unexpected exception from JMS/MQI callback functions has occurred.
Operator response
Report this to IBM Software Support.
CYND1705I: The system has turned on heap analysis for all
tracked classes.
Explanation
Heap data will be processed.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
181
CYND1706I: The system has turned off heap analysis for all
tracked classes.
Explanation
Heap data will not be processed.
CYND1707I: The system is setting the tracing level in Level 2 to
L2 and in Level 3 to L3.
Explanation
See message.
Operator response
If not actively debugging a problem, consider reducing the tracing level to improve
performance.
CYND1801W: BcmControl.init failed validation.
Explanation
The validation for the Byte Code Modification control file has failed.
Operator response
Report this to IBM Software Support.
CYND1802W: BcmControl.init is missing file File.
Explanation
The Byte Code Modification control file is missing.
Operator response
Report this to IBM Software Support.
CYND1803W: BcmControl.init encountered exception Exception.
Explanation
An exception has occurred during Byte Code Modification control file initialization.
Operator response
Report this to IBM Software Support.
CYND1804W: Modification of this type Type is disabled. The
system has failed to remove type Type1.
Explanation
The system failed to remove Byte Code Modification.
Operator response
Report this to IBM Software Support.
182
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND1805W: For BcmControl.cleanFiles, the source directory
Directory is not a directory.
Explanation
The source directory is not a directory.
Operator response
Make sure the source directory is a directory, and try again.
CYND1806W: For BcmControl.createJarFile, type Type is not
valid.
Explanation
This is not a valid type to create a JAR file.
Operator response
Report this to IBM Software Support.
CYND1807W: For BcmControl.createJarFile, type Type is
modification disabled.
Explanation
The Byte Code Modification control modification for a specific type is disabled.
CYND1808W: For BcmControl.createJarFile, there is a missing
JAR filename for type Type.
Explanation
The JAR file is missing for a specific type.
Operator response
Report this to IBM Software Support.
CYND1809W: For BcmControl.validate, property file Property is
missing.
Explanation
See message.
Operator response
Report this to IBM Software Support.
CYND1810I: Modification of type Type is disabled. Type Type1 is
removed.
Explanation
An existing JAR file was deleted.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
183
CYND1811I: The control file was validated.\nSource Path =
Source Path\nDestination Path = Destination Path\nControl file =
File
Explanation
A Byte Code Modification control file was processed.
CYND1812W: The system failed to create JAR file File for type
Type and was unable to rename the temporary file.
Explanation
See message.
Operator response
Report this to IBM Software Support.
CYND1813I: JAR file File was created successfully for type Type.
Explanation
See message.
CYND1814I: A JAR file exists with identical name and size. There
was no replacement of file File.
Explanation
See message.
CYND1815I: A JAR file exists with identical name but of different
size. Since applyLatest flag is enabled, the system replaced the
existing file File with a new one.
Explanation
See message.
CYND1816W: A JAR file exists with identical name but of
different size. Since applyLatest flag is disabled, the existing file
File is being removed.
Explanation
See message.
CYND1817W: The system failed to delete the existing JAR file
File. Possible library changes may render this JAR file to be
outdated. An attempt to delete this file has failed.
Explanation
See message.
CYND1818I: An existing file File is detected. Since modification
of this type Type is disabled, this file has been deleted.
Explanation
See message.
184
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND1819W: The system failed to delete the existing JAR file
File. The modification flag for this type Type is set to disabled,
but an attempt to delete this file has failed.
Explanation
See message.
Operator response
Report this to IBM Software Support.
CYND1820I: This is the beginning of BcmControl.selfTest.
Explanation
This is a self test message.
CYND1821I: Processing Process
Explanation
This is a self test message.
CYND1822W: The system stopped processing Process because it
cannot deduce its type.
Explanation
See message.
Operator response
Report this to IBM Software Support.
CYND1823I: Classes within this file are subjected to
modification: Class
Explanation
This is a self test message.
CYND1824I: Classes within this file should not be modified: File.
Explanation
This is a self test message.
CYND1825I: This file is of type Type.
Explanation
This is a self test message.
CYND1826I: This type is enabled.
Explanation
This is a self test message.
CYND1827I: This type is disabled.
Explanation
This is a self test message.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
185
CYND1828I: The XML file is of type Type.
Explanation
This is a self test message.
CYND1829I: The replacement flag for this type is enabled.
Explanation
This is a self test message.
CYND1830I: The replacement flag for this type is disabled.
Explanation
This is a self test message.
CYND1831I: The JAR file is of type Type
Explanation
This is a self test message.
CYND1832I: This is the end of the self test.
Explanation
This is a self test message.
CYND1851I: The system cannot delete the previous Byte Code
Modification JAR file: File.
Explanation
See message.
CYND1852W: There are no contents in the Byte Code
Modification directory Directory.
Explanation
See message.
Operator response
Report this to IBM Software Support.
CYND1853I: Unknown entry type Type was skipped.
Explanation
This is not a valid type to process.
CYND1900W: The system failed to initialize BcmControl. Byte
Code Modification is disabled.
Explanation
See message.
Operator response
Report this to IBM Software Support.
186
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND1901I: The system is processing XML file File.
Explanation
See message.
CYND1902I: The system has started modifying the class Class.
Explanation
See message.
CYND1903I: The system has finished modifying the class.
Explanation
The class has been processed.
CYND1904W: An exception occurred in creating JAR file File.
Explanation
See message.
Operator response
Report this to IBM Software Support.
CYND1905I: The system is skipping processing XML file file.
Explanation
This Byte Code Modification XML file will not be processed.
CYND1906I: The system has started processing the resource.
The URL is Url. The resource name is Resource Name.
Explanation
The resource will be processed.
CYND1907W: The system could not find resource Resource.
Explanation
See message.
Operator response
Report this to IBM Software Support.
CYND1908W: The stream is null for type Type.
Explanation
See message.
Operator response
Report this to IBM Software Support.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
187
CYND1909I: The system has finished processing the resource.
The URL is Url.
Explanation
The resource was processed.
CYND2000E: Data type mismatch (Long) Type
Explanation
There is a mismatch with the data type.
Operator response
Report this to IBM Software Support.
CYND2001E: Data type mismatch (Stat) Type
Explanation
There is a mismatch with the data type.
Operator response
Report this to IBM Software Support.
CYND2002E: Data type mismatch (Load) Type
Explanation
There is mismatch on the data type.
Operator response
Report this to IBM Software Support.
CYND2050I: The probe supports Byte Code Modification Mod
level Level.
Explanation
The Byte Code Modification level is supported.
CYND2051I: Probe does not support Byte Code Modification Mod
level Level.
Explanation
The Byte Code Modification level is not supported.
CYND2052E: There is an unsatisfied link for type Type.
Explanation
The link is not satisfied.
Operator response
Report this to IBM Software Support.
188
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND2053E: An unsatisfied link error occurred for
MethodLevelModule.initializeClass().
Explanation
See message.
Operator response
Make sure the libam.so file is deployed properly. Report this to IBM Software
Support.
CYND2054I: The system is initializing class Class.
Explanation
The class will be processed.
CYND2055I: The system is flushing method IDs for class Class.
Explanation
The class will be processed.
CYND2056I: The probe is recognized as enabled for Byte Code
Modification.
Explanation
The probe will process Byte Code Modification data.
CYND2057I: The system is flushing out previously loaded class
Class.
Explanation
The class will be processed.
CYND2058E: There was an unsatisfied link error while unloading
link Link.
Explanation
See message.
Operator response
Report this to IBM Software Support.
CYND2059E: Exception Exception has occurred in ITCAMfTTImpl.
Explanation
See message.
Operator response
Report this to IBM Software Support.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
189
CYND2060I: The probe will process IBM Tivoli Composite
Application Manager for Transaction Tracking data.
Explanation
See message.
CYND2061I: The probe will not process IBM Tivoli Composite
Application Manager for Transaction Tracking data.
Explanation
See message.
CYND2062W: The Data Collector was not able to connect to the
Managing Server.
Explanation
See message.
Operator response
Report this to IBM Software Support.
CYND2063W: The Data Collector was not able to connect to the
Managing Server and log messages are now off.
Explanation
The Data Collector could not connect to the Managing Server. No additional
messages will be issued.
Operator response
Report this to IBM Software Support.
CYND2064I: Connection to the Managing Server is disabled.
Explanation
The Data Collector will not try to contact the Managing Server, because the
am.itcam.enable property is set to "no".
Data Collector on Windows and UNIX
CYND4001I: Data Collector Controller is listening at port
portNumber
Explanation
This is the RMI runtime listening port for the Data collector.
CYND4002I: After joining the Kernel, security manager is:
Securitymanager
Explanation
Data Collector uses the security manager from WebSphere if global security is
enabled, otherwise it is null.
190
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND4003E: Failed to start controller.
Explanation
Controller failed to join Kernel.
Operator response
First, make sure Kernel is up and running. Second, make sure Data Collector
configuration (Kernel.Codebase, Java.Rmi.Server.Codebase) is specified properly.
CYND4004I: Received notification of probe configuration update:
Probeconfig
Explanation
Kernel notified Data Collector that its configuration is updated.
CYND4005E: Failed to allocate port to controller.
Explanation
RMI port for controller specified in Datacollector.Properties is in use.
Operator response
Specify an unused port.
CYND4006I: Received notification that probe configuration was
removed.
Explanation
Kernel notified Data Collector that its configuration was removed.
CYND4007E: Failed to set monitoring level.
Explanation
Monitoring level have to be numerical.
Operator response
Enter only numbers for the monitoring level in the probe configuration.
CYND4008I: Native Probe and JAVA-JNI threads successfully
started.
Explanation
The JNI thread for the native probe has started successfully
CYND4009E: Java-JNI threads were not started.
Explanation
The probe controller failed to initialize the native probe.
Operator response
Restart the application server.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
191
CYND4010E: Failed to start native probe.
Explanation
The configuration of the Data Collector is not set properly.
Operator response
Check the Installation Guide and make sure the proper configuration is set.
CYND4011I: You are trying to stop a Data Collector which was
not started successfully.
Explanation
If probe is not started successfully, ignore stop command.
CYND4012E: Failed to stop command agent.
Explanation
An internal error has occurred.
Operator response
Check trace log for more information.
CYND4013I: Probe Controller stopped successfully.
Explanation
Probe controller has stopped successfully.
CYND4014E: Error occurred while stopping the probe.
Explanation
An internal error has occurred.
Operator response
Check the trace log for more information.
CYND4015W: Event agent is alive. Cannot start another event
agent.
Explanation
There have been two or more attempts to start the event agent.
Operator response
Restart the application server.
CYND4016W: Network agent is alive. Cannot start another agent.
Explanation
There have been two or more attempts to start the network agent.
Operator response
Restart the application server.
192
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND4017W: Publish Server status thread is alive. Cannot start
another agent.
Explanation
There have been two or more attempts to start the Publish Server agent.
Operator response
Restart the application server.
CYND4018E: Failed to start Publish Server agent.
Explanation
An internal error has occurred.
Operator response
Check trace log for more details.
CYND4019E: Failed to stop Publish Server agent.
Explanation
An internal error has occurred.
Operator response
Check trace log for more details.
CYND4020E: Failed to get sampling rate.
Explanation
The sampling rate contains a space or tab.
Operator response
Sampling rate should only contain digits.
CYND4021I: Scheduler configuration is null for ID: Scheduleid
Explanation
The scheduler configuration is missing.
Operator response
Check Visualization Engine (VE) for Data Collector configuration.
CYND4022E: Failed to set scheduler configuration.
Explanation
Kernel failed to update scheduler configuration.
Operator response
Check trace log for more details.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
193
CYND4023E: Failed to update scheduler configuration.
Explanation
Data Collector failed to parse the scheduler configuration.
Operator response
Check trace log for more details.
CYND4024I: Invalid monitoring level: Modlevel specified, ignore
the new monitoring value.
Explanation
An invalid monitoring level was specified. The Data Collector will ignore it.
CYND4025E: Failed to set new monitoring level.
Explanation
An internal error has occurred.
Operator response
Check trace log for more details.
CYND4026E: Failed to get default monitoring level.
Explanation
Kernel may be down.
Operator response
Verify that the Kernel is up and running.
CYND4027I: Probe security is not enabled.
Explanation
Probe controller security is disabled. To enable the security, set the system property
'security.enabled'.
CYND4028E: Error occurred when creating probe controller
loginstub.
Explanation
Probe controller failed to export object probe controller login.
Operator response
Check trace log for more details.
CYND4029I: Probe security is enabled.
Explanation
Probe controller security is enabled.
194
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND4030E: The Am home path is not set. Set the system
property Am.Home for the Data Collector.
Explanation
The Installer failed to set this property.
Operator response
Check Application Server configuration. Verify that the Java system property
Am.Home is defined properly.
CYND4031E: An error occurred when setting up Cyanea custom
service.
Explanation
Initialization failed.
Operator response
Check trace log for more details.
CYND4032E: Unable to join Kernel, retrying.
Explanation
The Kernel may be down.
Operator response
Verify the Kernel is up and running.
CYND4033E: Failed to start probe controller.
Explanation
The probe controller failed to join the Kernel.
Operator response
Check trace log for more details.
CYND4034E: Unable to save monitoring level.
Explanation
Monitoring file does not have write permissions.
Operator response
Verify the this account has write permissions to the monitoring file.
CYND4035E: Unable to find monitoring file:Modfile
Explanation
Monitoring file does not exist.
Operator response
Verify that Am.Home/Etc has read and write permissions.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
195
CYND4036E: Unable to read monitoring file: Modfile
Explanation
Monitoring file does not have read permissions.
Operator response
Verify that Am.Home/Etc has read and write permissions.
CYND4037W: Unknown proxy host:Proxyhostname
Explanation
An incorrect Host name is specified for the property Proxy.Host in the
Datacollector.Properties file.
Operator response
Verify that the correct Host name is set for Proxy.Host.
CYND4038E: Unable to load Cyanea probe configuration file:
Probeconfigfile
Explanation
Datacollector.Properties is missing.
Operator response
Verify that the probe configuration fle exists and has read permissions.
CYND4039E: Error occurred while getting product version
number.
Explanation
The Version.Properties file is missing.
Operator response
Verify that Version.Properties is installed properly.
CYND4040E: Failed to load library: Libname
Explanation
The library path is not configured properly.
Operator response
Check the Data Collector Installation Guide and verify that the Library Path is
configured properly.
CYND4041I: Native custom service start notification issued
successfully.
Explanation
The native custom service for all the managers has started successfully.
196
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND4042E: An error occurred in native custom service start.
Explanation
An internal error has occurred.
Operator response
Check Msg-Dc-Native.Log and Trace-Dc-Native.Log for more information.
CYND4043I: Setting probe Sampling Rate for monitoring level
(L0, L1, L2, L3):L0, L1, L2, L3, Usesystemdefault: Issystemdefault
Explanation
Display the actual Sampling Rate for all monitoring levels.
CYND4044I: Incorrect system default monitoring level: Modlevel
Explanation
The monitoring level entered was out of range, therefore the settings will revert
back to the system default.
CYND4045I: Incorrect monitoring level: Modlevel
Explanation
The monitoring level entered was out of range, therefore the settings will revert
back to the system default.
CYND4046E: Unable to find monitoring file: Modfile
Explanation
This account may not have permissions to create a monitoring file at
Am.Home/Etc.
Operator response
Verify that Am.Home/Etc has read and write permission.
CYND4047I: Loaded the native library: libName
Explanation
The native library has loaded successfully.
CYND4048E: Failed to deserialize marshalled object.
Explanation
Some jars shared by both the Data Collector and Managing Server are out of sync.
Operator response
Verify that jars are synchronized between Managing Server and Data Collector.
CYND4049E: Failed to get the proxy server from Kernel.
Explanation
Proxy server may be down.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
197
Operator response
Verify proxy server is up and running.
CYND4050E: An error occurred during the start of the proxy task
thread.
Explanation
Kernel may be down.
Operator response
Check trace log for more details.
CYND4051I: Join Proxy Server and Kernel successfully. Service
ID: serviceID, probeID
Explanation
The Probe controller has joined the Proxy Server and the Kernel successfully. The
Service ID identifies the Proxy Server, and the Probe ID identifies the Kernel.
CYND4052E: Failed to join Proxy Server and Kernel.
Explanation
Proxy Server may be down, or Kernel may be down.
Operator response
Check trace log for more details.
CYND4053E: Am Home is not defined, not initializing security
module.
Explanation
The Installer failed to install properly.
Operator response
Check the Installation Guide and verify Am.Home is configured properly.
CYND4054I: The Cyanea password file (Cyanea.Pswdfile) is not
defined.
Explanation
The property Cyanea.Pswsfile is not configured.
Operator response
Check the Data Collector Installation Guide and specify the properties file correctly.
CYND4055E: The password file: Pwdfile does not exist.
Explanation
The password file is missing.
198
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
Verify the installation of the password file.
CYND4061E: Unable to start command agent.
Explanation
Failed to start command agent thread in Data Collector due to the specified error.
Operator response
Fix the specified error and restart the Application server.
CYND4062I: Command agent controller started at port.
Explanation
Command agent controller started successfully.
CYND4063I: Unable to obtain request information.
Explanation
An error occurred while trying to retrieve Http request information.
CYND4064W: Exception while reading the Java core file.
Explanation
An error occurred while trying to read the Java core file.
Operator response
It may be a file permissions error. Grant write permissions to the directory in
which the core file is written.
CYND4065E: An error occurred while sending Heap dump data to
the Publish Server.
Explanation
An error occurred while sending Heap dump data to the Publish Server. .
Operator response
Verify that the Publish Server has started successfully, if no restart the Publish
Server.
CYND4066E: An error occurred while initializing JMX agent.
Explanation
An error occurred while initializing JMX agent.
Operator response
Verify that the Application server has started successfully.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
199
CYND4067E: An error occurred while creating object name:
objectName
Explanation
An error occurred while creating object name.
Operator response
Verify that the Application server has started successfully.
CYND4068I: No Mbean object found of type: type in process
process
Explanation
Mbean object of the specified type is not found on the server.
CYND4069E: An error occurred while creating Adminclient.
Explanation
An error occurred while creating Adminclient.
Operator response
Verify that the Application server has started successfully.
CYND4070E: An error occurred while querying for configuration
objects of type: type
Explanation
An error occurred while querying for configuration objects.
Operator response
Verify that the Application server has started successfully.
CYND4071E: An error occurred while querying for configuration
attributes:
Explanation
An error occurred while querying for configuration attributes.
Operator response
Verify that the Application server has started successfully.
CYND4072E: Deploymentmanager.Rmi.Port property is not set in
Datacollector.Properties.
Explanation
To collect System Resources information the Deploymentmgr.Rmi.Port property
needs to be set in Datacollector.Properties.
Operator response
Set Deploymentmgr.Rmi.Port Property in Datacollector.Properties and restart the
server.
200
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND4073E: Deploymentmanager.Rmi.Host property is not set in
Datacollector.Properties.
Explanation
To collect System Resources information the Deploymentmgr.Rmi.Host property
needs to be set in Datacollector.Properties.
Operator response
Set Deploymentmgr.Rmi.Host property in Datacollector.Properties and restart the
server.
CYND4074E: Deploymentmanager.Rmi.Connection property is
not set in Datacollector.Properties.
Explanation
To collect System Resources information the Deploymentmgr.Rmi.Connection
property needs to be set in Datacollector.Properties.
Operator response
Set Deploymentmgr.Rmi.Connection property in Datacollector.Properties and
restart the server.
CYND4075E: Failed to create Adminservice.
Explanation
Failed to create Adminservice.
Operator response
Verify that the Application server has started successfully.
CYND4076E: Server Mbean not found
Explanation
JMX agent is unable to locate server Mbean.
Operator response
Verify that the Application server has started successfully.
CYND4077E: Error while registering JMX client.
Explanation
Error while registering JMX client.
Operator response
Verify that the Application server has started successfully.
CYND4078E: Probeservice did not start successfully.
Explanation
An error occurred while starting probe services.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
201
Operator response
Verify that the configuration parameters are correct.
CYND4079E: Error while retrieving PMI data for the: component
component .
Explanation
Error while retrieving PMI data for the specified component.
Operator response
Verify that the configuration parameters are correct.
CYND5236I: Privacy Filter is On. Http Request Query String, SQL
String and Http Cookie data is not trasmitted
Explanation
Privacy Filter is properly set and privacy data is not transmitted to Managing
Server
CYND5237I: Using SSL server socket for component:
CommandAgent. All clients connecting to this component MUST
connect via SSL, else the client socket may hang till the timeout
expires. No user action is required.
Explanation
Command agent started successfully in SSL mode.
CYND5238E: [BCM] CtgCallBack Error Message:
Explanation
An error message was issued in CtgCallBack.
Operator response
Refer to the issued message, and contact IBM Support.
CYND5239I: ITCAM Product Mode: productmode
Explanation
Data collected by the data collector is limited by the product mode.
Operator response
Consult the license under which the ITCAM Managing Server is running.
CYND5240I: ITCAM Product Mode changed to: productmode
Explanation
The data collector is now operating according to the specified product mode.
Operator response
Consult the license under which the ITCAM Managing Server is running.
202
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND5241E: ITCAM Product Mode changed failed: productmode
Explanation
The product mode is invalid or unsupported.
Operator response
Consult the license under which the ITCAM Managing Server is running.
Byte Code Modification Messages
CYND6001E: Unexpected exception. Refer to the tracing log.
Explanation
No additional information is available for this message.
CYND6001I: Data Collector Controller is listening at port
portNumber
Explanation
This is the RMI runtime listening port for the Data collector.
Operator response
Consult the license under which the ITCAM Managing Server is running.
CYND6001W: Returning original Server Socket in multiple
context mode, provider might not support this implementation
Explanation
No additional information is available for this message.
CYND6002E: ObjectName invalid format MalformedObjectNameException was produced.
Explanation
No additional information is available for this message.
CYND6002I: JMXConnectorServer was successfully initialized
Explanation
No additional information is available for this message.
CYND6002W: Not pure secure mode: server trusted by subject
Explanation
No additional information is available for this message.
CYND6003E: Unable to load configuration file: Probeconfigfile
Explanation
No additional information is available for this message.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
203
CYND6003I: PING request was processed.
Explanation
No additional information is available for this message.
CYND6003W: Insecure mode: it is recommended to turn on SSL
Explanation
No additional information is available for this message.
CYND6004E: GC logging is not enabled.
Explanation
No additional information is available for this message.
CYND6004I: Secure Socket Factory successfully initialized
Explanation
No additional information is available for this message.
CYND6005E: GC Log file name is not specified in JVM
parameters or in GCLogVariable
Explanation
No additional information is available for this message.
CYND6005I: Pure secure mode: using default trusted managers
Explanation
No additional information is available for this message.
CYND6006E: Error during Regexp subsystem initialization. Refer
to the tracing log.
Explanation
No additional information is available for this message.
CYND6007E: KeyStore location or store password or key
password are not defined
Explanation
No additional information is available for this message.
CYND6008E: No SSL compatible server socket implementation is
available, if you are using JDK 1.3, download JSSE extension
and install it following JDK documentation
Explanation
No additional information is available for this message.
CYND6009E: Exception when initializing SSL parameters
Explanation
No additional information is available for this message.
204
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND6010E: Exception in the task. Refer to the tracing log.
Explanation
No additional information is available for this message.
CYND6011E: Cannot open the GC Log file: GCLogfile
Explanation
No additional information is available for this message.
CYND6031I: GC Collector MBean was registered, object name:
objectName
Explanation
No additional information is available for this message.
CYND6032E: JMXConnectorServer was not found.
Explanation
No additional information is available for this message.
CYND6033E: RequestAggregator was not found
Explanation
No additional information is available for this message.
CYND6033W: Skip the incomplete GC event.
Explanation
No additional information is available for this message.
CYND6051I: OS Info MBean was registered, object name:
objectName
Explanation
No additional information is available for this message.
CYND6076W: The Byte Code Modification engine could not
identify a list of classes to be instrumented.
Explanation
See message.
Operator response
Check if Java system property appserver.platform is defined properly, and check if
platform-specific request definition XML files are installed properly.
CYND6089I: The Byte Code Modification engine could not find
directory directory.
Explanation
See message.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
205
Operator response
Check your installation.
CYND6090I: The Byte Code Modification engine could not find its
working directory.
Explanation
See message.
Operator response
Check your installation.
CYND6094I: The Byte Code Modification engine could not find a
resource for name.
Explanation
The Byte Code Modification engine could not find a class.
CYND6095I: The stream is null for name.
Explanation
The Byte Code Modification engine could not load a class.
CYND7001E: Error while creating a silent installation file {0}
Explanation
The migration tool was not able to create the silent options file used for
installation.
Operator response
Check the write permissions for the temporary directory.
CYND7002E: Error during installation {0}
Explanation
An error occurred during the installation of ITCAM 6.1
Operator response
Refer to the log file for the error reason.
CYND7003E: Error while the migration tool was backing up the
home directory {0}
Explanation
Migration tool was not able to back up the ITCAM 6.0 home directory
Operator response
Check the write permission for the ITCAM 6.0 home directory.
206
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND7004E: ISDataBase Access error {0}
Explanation
An internal InstallShield error occurred
Operator response
Restart the migration tool.
CYND7006E: Error while Loading properties {0}
Explanation
The silent options file was not loaded.
Operator response
Specify the correct silent options file.
CYND7007E: Error during migration {0}
Explanation
An error caused the Migration to fail.
Operator response
Refer to the log file for the error reason
CYND7008E: Wrong path to product: {0}
Explanation
The wrong path was specified to the ITCAM 6.0 home directory.
Operator response
Enter the correct path to the ITCAM 6.0 home directory.
CYND7010W: An error occurred while deleting the temporary file.
Explanation
No additional information is available for this message.
CYND7012E: The CERT_PATH variable was not found
Explanation
The setenv.sh script does not set the CERT_PATH variable.
Operator response
Fix the setenv.sh script to set the CERT_PATH variable.
CYND7013E: An error occurred while uninstalling the
Visualization Engine: {0} {1}
Explanation
The uninstallation of the ITCAM 6.0 Visualization Engine failed.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
207
Operator response
Refer to the log file for the error reason.
CYND7014E: CYANEA_HOME_OS variable was not found in
setenv.sh file
Explanation
The setenv.sh script does not set the CYANEA_HOME_OS variable.
Operator response
Fix the setenv.sh script to set the CYANEA_HOME_OS variable.
CYND7015E: Cannot read {0}
Explanation
The migration tool cannot read the specified file.
Operator response
Check the read permission for the file.
CYND7016E: Cannot write to file {0}
Explanation
The migration tool cannot write to the specified file.
Operator response
Check the write permission for the file.
CYND7019E: Certificates data or Certificate path is not correct
Explanation
The CERT_PATH variable in the setenv.sh script has an incorrect value.
Operator response
Fix the CERT_PATH variable in the setenv.sh script.
CYND7021E: Variable in ve.properties is not correct: {0}
Explanation
The specified variable has an incorrect value.
Operator response
Fix the variable in the ve.properties file.
CYND7023E: An error occurred while getting WebSphere servers
topology data: topology data is empty. Script output: {0}
Explanation
An error occurred while getting the WebSphere servers topology data.
208
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
Ensure that WebSphere application server information is entered correctly.
CYND7024E: File not found: {0}
Explanation
The migration tool cannot find the specified file.
Operator response
Check the write permission for the directory.
CYND7026E: An exception occurred while getting DB port and
server data from variable: {0}
Explanation
Operator response
Fix the JDBC_DRIVER_URL variable in setenv.sh script.
CYND7027E: Database type cannot be recognized. Error in
setenv.sh file data.
Explanation
The JDBC_DRIVER_URL variable in the setenv.sh script has an incorrect value.
Operator response
Fix the JDBC_DRIVER_URL variable in setenv.sh script.
CYND7031E: An error occurred while setting in IS database:
Explanation
An internal InstallShield error occurred.
Operator response
Restart the migration.
CYND7033E: An error occurred while restoring subfolders
Explanation
The migration tool was not able to restore ITCAM 6.0 directories.
Operator response
Restore ITCAM 6.0 from the backup directory manually
CYND7034E: Updating DB failed with exit code {0}
Explanation
An error occurred while updating the database.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
209
Operator response
Ensure that the correct database parameters were specified and restart the
migration.
CYND7035E: An error occurred while executing: {0}. Error: {1}
Explanation
The error occurred during the external script execution.
Operator response
Refer to the log file for the error reason.
CYND7036E: The error occurred while uninstalling the
Visualization Engine: {0}
Explanation
The error occurred while uninstalling the ITCAM 6.0 Visualization Engine.
Operator response
Refer to the log file for the error reason.
CYND7037E: Incorrect Managing Server host name: {0}. A fully
qualified host name should be provided.
Explanation
The specified Managing Server host name is not correct. It cannot be an IP address
or host name that cannot be resolved.
Operator response
Specify the fully qualified host name and click the Retry button.
CYND7038E: WAS_home variable is not defined
Explanation
The setenv.sh script does not set the WAS_home variable.
Operator response
Fix the setenv.sh script to set the WAS_home variable.
CYND7039E: The error occurred while running the script for
uninstalling the Visualization Engine. {0} {1}
Explanation
The specified error occurred while running the script for uninstalling ITCAM 6.0
Visualization Engine.
Operator response
Refer to the log file for the error reason.
210
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND7040E: An error occurred while getting profiles
Explanation
The migration tool was not able to get the list of WebSphere Application Server
profiles.
Operator response
Refer to the log file for the error reason.
CYND7041E: Variable app.install.path is not defined or could not
read the file
Explanation
The ve.properties file is not readable or has an incorrect app.install.path property.
Operator response
Ensure that the ve.properties file exists and has the app.install.path property
defined.
CYND7042E: Not WebSphere 6, profile not found
Explanation
The migration tool was not able to get the profile name from app.install.path
property defined in the ve.properties file.
Operator response
Ensure that the ve.properties file has the app.install.path property defined correctly.
CYND7045E: An error occurred while getting the profile home
dir: the profile name is not defined
Explanation
The migration tool obtained an empty profile name.
Operator response
Ensure that the WebSphere Application Server is installed correctly.
CYND7047I: Starting installation ...
Explanation
No additional information is available for this message.
CYND7048E: An error occurred while getting WebSphere
Application Server version data. Error code: {0}
Explanation
The migration tool was not able to parse the versionInfo script output.
Operator response
Refer to the log file for the error reason
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
211
CYND7056E: Installation file not found: {0}
Explanation
The migration tool was not able to run the ITCAM 6.1 installation.
Operator response
Ensure that the installation image was copied to the disk correctly and restart the
migration.
CYND7057E: Migration failed: {0}
Explanation
The migration tool finished unsuccessfully because of the error indicated
Operator response
Refer to the log file for the error reason.
CYND7059E: The path to the product is empty.
Explanation
An empty path was specified to the ITCAM 6.0 home directory.
Operator response
Enter the correct path to the ITCAM 6.0 home directory.
CYND7060E: Unsuccessful exit code
Explanation
Silent installation of the ITCAM 6.1 finished unsuccessfully.
Operator response
Refer to the log file for the error reason.
CYND7061E: The directory '{0}' is in use
Explanation
Another process is using the specified directory.
Operator response
End all programs that are using the ITCAM 6.0 home directory and click the Retry
button.
CYND7062I: Directory is in use or does not exist
Explanation
No additional information is available for this message.
CYND7063E: Aborted by user
Explanation
No additional information is available for this message.
212
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND7064I: Starting migration.
Explanation
No additional information is available for this message.
CYND7065I: Generating silent file
Explanation
No additional information is available for this message.
CYND7066I: Uninstalling Visual Engine
Explanation
No additional information is available for this message.
CYND7067I: Visual Engine installation is not selected, exit
without deinstalling
Explanation
No additional information is available for this message.
CYND7068I: WebSphere instance found: {0}
Explanation
No additional information is available for this message.
CYND7069I: Removing backup directory
Explanation
No additional information is available for this message.
CYND7070I: Executing script to update DB: {0}
Explanation
No additional information is available for this message.
CYND7071I: Migration successfully finished
Explanation
No additional information is available for this message.
CYND7072I: Folders successfully restored
Explanation
No additional information is available for this message.
CYND7073I: DB update not selected
Explanation
No additional information is available for this message.
CYND7074I: WAS version = 5, do not uninstall the Visualization
Engine
Explanation
No additional information is available for this message.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
213
CYND7077I: An error occurred while executing: {0}. Arguments:
{1}
Explanation
No additional information is available for this message.
CYND7079I: An error occurred: KEYSTR_LOC variable not
defined
Explanation
No additional information is available for this message.
CYND7080I: The file deleted successfully {0}
Explanation
No additional information is available for this message.
CYND7081W: The file deletion failed {0}
Explanation
No additional information is available for this message.
CYND7082I: The folders backed up successfully.
Explanation
No additional information is available for this message.
CYND7083I: The command executed successfully.
Explanation
No additional information is available for this message.
CYND7084I: The Visualization Engine uninstalled successfully
Explanation
No additional information is available for this message.
CYND7086I: Backup directory name: {0}
Explanation
No additional information is available for this message.
CYND7115I: Execute the command: {0}
Explanation
No additional information is available for this message.
CYND7116I: Command Done
Explanation
No additional information is available for this message.
CYND7120I: Timeout occurred while executing the process: {0}
Explanation
No additional information is available for this message.
214
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND7124I: Starting migration of server: {0}
Explanation
No additional information is available for this message.
CYND7126I: Server was migrated: {0}
Explanation
No additional information is available for this message.
CYND7137I: Selected profile: {0}, profile home: {1}
Explanation
No additional information is available for this message.
CYND7138I: Visualization Engine installation not selected
Explanation
No additional information is available for this message.
CYND7140I: Backing up folders to: {0}
Explanation
No additional information is available for this message.
CYND7141I: Uninstalling the Visualization Engine: WAS version
== 6
Explanation
No additional information is available for this message.
CYND7142I: Deleting
Explanation
No additional information is available for this message.
CYND7145I: Copying keys and certificates files to standard
install location...
Explanation
No additional information is available for this message.
CYND7148I: Installation finished with exit code: {0}
Explanation
No additional information is available for this message.
CYND7157I: Setting +x mode to db2update.sh: {0}
Explanation
No additional information is available for this message.
CYND7159I: Upgrading DB finished with exit code {0}
Explanation
No additional information is available for this message.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
215
CYND7161I: Copying file {0}
Explanation
No additional information is available for this message.
CYND7163I: Executing command: {0}
Explanation
No additional information is available for this message.
216
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Generic Probe Engine
CYNPE0001I: Generic Probe Engine Runtime Environment is now
initialized
Explanation
Operator response
CYNPE0002I: Generic Probe Engine initialized startup class
StartupClass
Explanation
Operator response
CYNPE0003I: Generic Probe Engine shutdown initiated
Explanation
Operator response
CYNPE0004I: Generic Probe Engine initialized runtime
component RuntimeComponent class RuntimeClass
Explanation
Operator response
CYNPE0005I: MBean Manager has been initialized
Explanation
Operator response
CYNPE0006I: MBean Manager registered MBean ObjectName
Explanation
Operator response
CYNPE0007I: MBean Manager loaded the registration engine
RegistrationEngine
Explanation
Operator response
CYNPE0008E: XML parsing error occurred: errorType parsing file
fileName
Explanation
Operator response
CYNPE0009E: Aspect definition aspectName is defined with
abstract pointcut pointcutName but has no concretizePointcut
definition
Explanation
Operator response
CYNPE0010I: MBean manager created MBean server with class
MBeanServerClass and default domain name domainName
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
217
Explanation
Operator response
CYNPE0011E: MBean manager was unable to create MBean
server with class MBeanServerClass and default domain name
domainName
Explanation
Operator response
Request Aggregator
CYNPE0002E: XML parsing error has occurred: errorType parsing
file fileName
Explanation
Operator response
CYNRA0001I: Request Aggregator is now initialized
Explanation
Operator response
CYNG Messages: Global Publish Server
The following messages relate to the Global Publish Server. All such messages have
IDs in the range CYNG0001E to CYNG0127E.
CYNG0001E: The Global Publish Server cannot determine
whether the database is DB2 or Oracle.
Explanation
See message.
System action
The Global Publish Server shut down.
Operator response
Contact your system administrator immediately.
Problem determination
Ensure that the JDBC drivers in the Managing Server are correctly installed and
configured.
CYNG0002E: The Global Publish Server was unable to
establish a database connection.
Explanation
The Global Publish Server has attempted to create a database connection pool, and
was unable to connect to the database.
218
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
System action
The Global Publish Server shuts down.
Operator response
Ensure that the database is running and contact your system administrator if it is
not.
Problem determination
Ensure that the database is running on the specified host, and that the
communication mechanisms are correct.
CYNG0003I: The Global Publish Server's DbConnectionPool
monitoring thread is awake and running.
Explanation
The monitoring thread in the database connection pool that ensure that all the
managed connections are working properly has awakened and is running.
CYNG0004W: The Global Publish Server's monitoring thread
in the database connection pool is replacing an inactive
connection.
Explanation
The monitoring thread in the database connection pool identified an inactive
connection and is attempting to replace it.
CYNG0005E: The Global Publish Server's DbConnectionPool
monitoring thread was unable to replace an inactive
connection.
Explanation
The DBConnectionPool monitoring thread tried to open a connection to the
database, and an exception was encountered.
System action
The system failed to open a new connection. It is attempting to continue.
Operator response
Ensure that you have database connectivity, or contact your system administrator.
Ensure that the database is up, running, and correctly configured. Also, ensure that
the JDBC drivers are installed correctly.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
219
CYNG0006W: The Global Publish Server's DbConnectionPool
monitoring thread is reclaiming a hung connection.
Explanation
The DBConnectionPool monitoring thread is forcibly reclaiming a connection that
has been checked out for 30 minutes or longer.
CYNG0007E: The Global Publish Server's DbConnectionPool
monitoring thread was unable to reclaim a hung connection.
Explanation
The DBConnectionPool tried to forcibly reclaim a hung connection and
encountered an exception.
System action
The system is attempting to continue.
Operator response
Ensure that you have database connectivity, or contact your system administrator.
Problem determination
Ensure that the database is up, running, and correctly configured. Also, ensure that
the JDBC drivers are installed correctly.
CYNG0008E: An exception occurred while attempting to get a
database connection from the pool.
Explanation
An exception occurred while DBConnectionPool.getConnection was running.
Check the trace logs for more detailed information.
System action
The system is attempting to continue.
Operator response
Ensure that you have database connectivity, or contact your system administrator.
Problem determination
Ensure that the database is up, running, and correctly configured. Also, ensure that
the JDBC drivers are installed correctly.
CYNG0009E: An exception occurred while attempting to return
a database connection to the pool.
Explanation
An exception occurred while DBConnectionPool.releaseConnection was running.
Check the trace logs for more detailed information.
220
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
System action
The system is attempting to continue.
Operator response
Ensure that you have database connectivity, or contact your system administrator.
Problem determination
Ensure that the database is up, running, and correctly configured. Also, ensure that
the JDBC drivers are installed correctly.
CYNG0010E: The Global Publish Server was unable to open a
Global Publish Server properties file.
Explanation
The Global Publish Server was unable to locate or open sam1.properties.
System action
The Global Publish Server shuts down.
Operator response
Contact your system administrator and confirm that the Managing Server is
correctly installed.
Problem determination
Ensure that the etc/sam1.properties file is located in the installation directory.
CYNG0011E: The Global Publish Server was unable to
determine the IP address to listen on.
Explanation
The Global Publish Server was unable to locate the value for HOST_SAM in the
file sam1.properties.
System action
The Global Publish Server shuts down.
Operator response
Contact your system administrator and confirm that the Managing Server is
correctly installed and configured.
Problem determination
Ensure that the file etc/sam1.properties is located in the installation directory, has
the correct permissions, and that the value for HOST_SAM is correct.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
221
CYNG0012E: The Global Publish Server was unable to
determine the port number to listen on.
Explanation
The Global Publish Server was unable to locate the value for PORT_SAM in the
file sam1.properties.
System action
The Global Publish Server shuts down.
Operator response
Contact your system administrator and confirm that the Managing Server is
correctly installed and configured.
Problem determination
Ensure that the file etc/sam1.properties is located in the installation directory, has
the correct permissions, and that the value for PORT_SAM is correct.
CYNG0013E: The Global Publish Server was unable to
determine the component ID to register with the Kernel.
Explanation
The Global Publish Server was unable to locate the value for SAM_ID in the file
sam1.properties.
System action
The Global Publish Server shuts down.
Operator response
Contact your system administrator and confirm that the Managing Server is
correctly installed and configured.
Problem determination
Ensure that the file etc/sam1.properties is located in the installation directory, has
the correct permissions, and that the value for SAM_ID is correct.
CYNG0014E: The Global Publish Server was unable to
determine the socket backlog value from the properties file.
Explanation
The Global Publish Server was unable to locate the value for SOCKET_BACKLOG
in the file sam1.properties.
System action
The system is using the default value (5).
222
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
Contact your system administrator and confirm that the Managing Server is
correctly installed and configured.
Problem determination
Ensure that the file etc/sam1.properties is located in the installation directory, has
the correct permissions, and that the value for SOCKET_BACKLOG is correct.
CYNG0015E: The Global Publish Server was unable to
determine the connection pool size value from the properties
file.
Explanation
The Global Publish Server was unable to locate the value for CONN_POOL_SIZE
in the file sam1.properties.
System action
The system is using the default value (5).
Operator response
Contact your system administrator and confirm that the Managing Server is
correctly installed and configured.
Problem determination
Ensure that the file etc/sam1.properties is located in the installation directory, has
the correct permissions, and that the value for CONN_POOL_SIZE is correct.
CYNG0016E: The Global Publish Server was unable to
determine the JDBC driver name from the system
environment.
Explanation
The Global Publish Server was unable to locate the value for
JDBC_DRIVER_NAME in the system environment.
System action
The Global Publish Server exits.
Operator response
Contact your system administrator and confirm that the Managing Server is
correctly installed and configured.
Problem determination
Ensure that the file bin/setenv.sh is located in the installation directory, has the
correct permissions, and that the value for JDBC_DRIVER_NAME is correct.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
223
CYNG0017E: The Global Publish Server was unable to
determine the database URL from the system environment.
Explanation
The Global Publish Server was unable to locate the value for DB_URL in the
system environment.
System action
The Global Publish Server exits.
Operator response
Contact your system administrator and confirm that the Managing Server is
correctly installed and configured.
Problem determination
Contact your system administrator and confirm that the Managing Server is
correctly installed and configured.
CYNG0018E: The Global Publish Server was unable to
determine the database user from the system environment.
Explanation
The Global Publish Server was unable to locate the value for DB_USER in the
system environment.
System action
The Global Publish Server exits.
Operator response
Contact your system administrator and confirm that the Managing Server is
correctly installed and configured.
Problem determination
Ensure that the file bin/setenv.sh is located in the installation directory, has the
correct permissions, and that the value for DB_USER is correct.
CYNG0019E: The Global Publish Server was unable to
determine the database password from the system
environment.
Explanation
The Global Publish Server was unable to locate the value for DB_PASSWORD in
the system environment.
System action
The Global Publish Server exits.
224
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
Contact your system administrator and confirm that the Managing Server is
correctly installed and configured.
Problem determination
Ensure that the file bin/setenv.sh is located in the installation directory, has the
correct permissions, and that the value for DB_PASSWORD is correct.
CYNG0020E: The Global Publish Server was unable to
determine the value of the backup thread timer from the
properties file.
Explanation
The Global Publish Server was unable to locate the value for
BACKUP_THREAD_TIMER in the file etc/sam1.properties.
System action
The system is using the default value (5 minutes).
Operator response
Contact your system administrator and confirm that the Managing Server is
correctly installed and configured.
Problem determination
Ensure that the file etc/sam1.properties is located in the installation directory, has
the correct permissions, and that the value for BACKUP_THREAD_TIMER is
correct.
CYNG0021E: The Global Publish Server was unable to
determine the value of the cleanup thread timer from the
properties file.
Explanation
The Global Publish Server was unable to locate the value for
CLEANUP_THREAD_TIMER in the file etc/sam1.properties.
System action
The system is using the default value (5 minutes).
Operator response
Contact your system administrator and confirm that the Managing Server is
correctly installed and configured.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
225
Problem determination
Ensure that the file etc/sam1.properties is located in the installation directory, has
the correct permissions, and that the value for CLEANUP_THREAD_TIMER is
correct.
CYNG0022E: The Global Publish Server was unable to
determine the value of the dequeueing thread timer from the
properties file.
Explanation
The Global Publish Server was unable to locate the value for
DEQUEUEING_THREAD_TIMER in the file etc/sam1.properties.
System action
The system is using the default value (500 milliseconds).
Operator response
Contact your system administrator and confirm that the Managing Server is
correctly installed and configured.
Problem determination
Ensure that the file etc/sam1.properties is located in the installation directory, has
the correct permissions, and that the value for DEQUEUEING_THREAD_TIMER is
correct.
CYNG0023E: The Global Publish Server was unable to
determine the value of the sampling thread timer from the
properties file.
Explanation
The Global Publish Server was unable to locate the value for
SAMPLING_THREAD_TIMER in the file etc/sam1.properties.
System action
The system is using the default value (2000 milliseconds).
Operator response
Contact your system administrator and confirm that the Managing Server is
correctly installed and configured.
Problem determination
Ensure that the file etc/sam1.properties is located in the installation directory, has
the correct permissions, and that the value for SAMPLING_THREAD_TIMER is
correct.
226
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNG0024E: The Global Publish Server was unable to
determine the value for the token resolution timeout from the
properties file.
Explanation
The Global Publish Server was unable to locate the value for
TOKEN_RESOLUTION_TIMEOUT in the file etc/sam1.properties.
System action
The system is using the default value (5 days).
Operator response
Contact your system administrator and confirm that the Managing Server is
correctly installed and configured.
Problem determination
Ensure that the file etc/sam1.properties is located in the installation directory, has
the correct permissions, and that the value for TOKEN_RESOLUTION_TIMEOUT
is correct.
CYNG0025E: The Global Publish Server was unable to
determine the value of the orphan resolution timeout from the
properties file.
Explanation
The Global Publish Server was unable to locate the value for
ORPHAN_RESOLUTION_TIMEOUT in the file etc/sam1.properties.
System action
The system is using the default value (5 minutes).
Operator response
Contact your system administrator and confirm that the Managing Server is
correctly installed and configured.
Problem determination
Ensure that the file etc/sam1.properties is located in the installation directory, has
the correct permissions, and that the value for
ORPHAN_RESOLUTION_TIMEOUT is correct.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
227
CYNG0026E: The Global Publish Server was unable to
determine the value of the thread end timeout from the
properties file.
Explanation
The Global Publish Server was unable to locate the value for
THREAD_END_TIMEOUT in the file etc/sam1.properties.
Operator response
Contact your system administrator and confirm that the Managing Server is
correctly installed and configured.
Problem determination
Ensure that the file etc/sam1.properties is located in the installation directory, has
the correct permissions, and that the value for THREAD_END_TIMEOUT is
correct.
CYNG0027E: The Global Publish Server was unable to
determine the value of the resolved transaction timeout from
the roperties file.
Explanation
The Global Publish Server was unable to locate the value for
RESOLVED_TRANSACTION_TIMEOUT in the file etc/sam1.properties.
System action
The system is using the default value (1 minute).
Operator response
Contact your system administrator and confirm that the Managing Server is
correctly installed and configured.
Problem determination
Ensure that the file etc/sam1.properties is located in the installation directory, has
the correct permissions, and that the value for
RESOLVED_TRANSACTION_TIMEOUT is correct.
CYNG0028E: The Global Publish Server was unable to
determine the value of the insert batch size from the
properties file.
Explanation
The Global Publish Server was unable to locate the value for
INSERT_BATCH_SIZE in the file etc/sam1.properties.
228
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
System action
The system is using the default value (1000 records).
Operator response
Contact your system administrator and confirm that the Managing Server is
correctly installed and configured.
Problem determination
Ensure that the file etc/sam1.properties is located in the installation directory, has
the correct permissions, and that the value for INSERT_BATCH_SIZE is correct.
CYNG0029E: The Global Publish Server was unable to
determine the value of the maximum socket writes from the
properties file.
Explanation
The Global Publish Server was unable to locate the value for
MAX_SOCKET_WRITES in the file etc/sam1.properties.
System action
The system is using the default value (100,000 writes).
Operator response
Contact your system administrator and confirm that the Managing Server is
correctly installed and configured.
Problem determination
Ensure that the file etc/sam1.properties is located in the installation directory, has
the correct permissions, and that the value for MAX_SOCKET_WRITES is correct.
CYNG0030E: The Global Publish Server was unable to
determine the value of the write timeout from the properties
file.
Explanation
The Global Publish Server was unable to locate the value for WRITE_TIMEOUT in
the file etc/sam1.properties.
Operator response
Contact your system administrator and confirm that the Managing Server is
correctly installed and configured.
Problem determination
Ensure that the file etc/sam1.properties is located in the installation directory, has
the correct permissions, and that the value for WRITE_TIMEOUT is correct.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
229
CYNG0031I: The Global Publish Server successfully started.
Explanation
See message.
CYNG0032E: An error occurred while attempting to start the
Global Publish Server.
Explanation
Check the trace logs for possible reasons for the error.
System action
The Global Publish Server failed to start.
Operator response
Check the trace logs or contact your system administrator.
Problem determination
Check the trace logs for assistance in diagnosing this problem.
CYNG0033E: An error occurred while attempting to stop the
Global Publish Server.
Explanation
Check the trace logs to see possible reasons for this.
System action
The Global Publish Server failed to stop. The Global Publish Server is still running
and is possibly unstable.
User response
Use the amctl.sh sam1 forcestop command to stop the Global Publish Server to
stop the Global Publish Server without backing up data in memory, and might
lead to a loss of some data.
CYNG0034E: An error occurred while attempting to change
the Global Publish Server log level.
Explanation
A user attempted to change the log level of the Global Publish Server using a
command script, and the attempt failed.
System action
The Global Publish Server is still running, but might be unstable.
230
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
User response
Examine the trace logs for additional diagnostic information. If necessary, restart
the Global Publish Server.
CYNG0035E: An error occurred while attempting to ping the
Global Publish Server.
Explanation
A user attempted to ping the Global Publish Server using a control script, and an
exception was produced.
User response
Examine the trace logs for additional diagnostic information. The Global Publish
Server might need adjustment.
CYNG0036E: An error occurred while attempting to run
dumpState against the Global Publish Server.
Explanation
A user attempted to get the status of the Global Publish Server using a control
script, and an exception was produced.
User response
Examine the trace logs for additional diagnostic information. The Global Publish
Server might need adjustment.
CYNG0037E: An error occurred while attempting to contact
the Kernel.
Explanation
A user attempted an action on the Global Publish Server using a control script, and
an exception was produced while trying to contact the Kernel. The Kernel might
be offline, or there may be a network connectivity issue.
User response
Examine the trace logs for additional diagnostic information. The Global Publish
Server or the Kernel might need adjustment. Also, ensure that the following system
properties exist and are correct: java.security.policy, kernel.codebase, and
kernel.rfs.address.
CYNG0038E: The system was unable to create a proxy object
to join the Kernel.
Explanation
During Global Publish Server startup, an exception was encountered when the
Global Publish Server proxy object attempted to join the Kernel. The Kernel might
be offline, or there might be a network connectivity issue
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
231
User response
Examine the trace logs for additional diagnostic information. The Global Publish
Server or the Kernel might need adjustment.
CYNG0039E: The Global Publish Server was unable to join the
Kernel as a result of an incorrectly specified IP address.
Explanation
The Global Publish Server uses a tiered method to determine which IP address to
use to join the Kernel. First, it looks for java.rmi.server.hostname in the system
property, if it cannot find java.rmi.server.hostname, then it looks for HOST_SAM in
sam1.properties.
User response
Ensure that java.rmi.server.hostname is specified in setenv.sh or in samctl.sh, or the
value of HOST_SAM is specified in sam1.properties. However,
java.rmi.server.hostname takes precedence.
CYNG0040E: The Global Publish Server was able to create a
proxy object, but it failed to join the Kernel.
Explanation
There is a connectivity, configuration, or network problem with the Global Publish
Server or the Kernel.
User response
Check the trace logs for additional diagnostic information.
CYNG0041E: The Global Publish Server was unable to start a
server socket.
Explanation
The Global Publish Server listens on a socket at a port specified by the property
PORT_SAM. The Global Publish Server was unable to open a socket on this port.
System action
The Global Publish Server shuts down.
User response
Ensure that the value for PORT_SAM is set correctly in the bin/setenv.sh file and
does not conflict with any other Managing Server components. Also, check the
trace logs for additional diagnostic information.
232
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNG0042W: The Global Publish Server is attempting to
process a thread end event for an unknown thread.
Explanation
The Global Publish Server received a thread end event, but was unable to find the
thread in memory.
System action
The Global Publish Server disregards the event.
CYNG0043W: The Global Publish Server is attempting to
process a RequestRecord event for an unknown thread.
Explanation
The Global Publish Server received a RequestRecord event, but was unable to find
the thread in memory.
System action
The Global Publish Server disregards the event.
CYNG0044E: An exception was encountered while the Global
Publish Server was attempting to process a RequestRecord
event.
Explanation
See message.
System action
The Global Publish Server disregards the event.
User response
Check the trace logs for more information about this problem.
CYNG0045I: Token Token is timing out as a result of a parent
call without a child call.
Explanation
The token in question had a GPS_INVOKE or GPS_PUT event, and the
corresponding GPS_RECEIVE or GPS_GET event was not received within the
allotted timeout period.
System action
The Global Publish Server prunes this token from memory.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
233
CYNG0046I: Token Token is timing out as a result of a child
call without a parent call.
Explanation
The token in question had a GPS_RECEIVE or GPS_GET event, and the
corresponding GPS_INVOKE or GPS_PUT event was not received within the
allotted timeout period.
System action
The Global Publish Server prunes this token from memory.
CYNG0047I: Token Token is timing out because a missing
Global Publish Server thread end event is missing.
Explanation
One or more of the thread's involved with the token is missing its thread end
event, and the timeout period has expired.
System action
The Global Publish Server will prune this token from memory.
CYNG0048E: An exception was caught while the Global
Publish Server was attempting to restore data from the last
database backup image.
Explanation
When the Global Publish Server starts it attempts to prepopulate its memory
structures based on the values in the database from its most recent backup. The
Global Publish Server attempted to do this, and an exception was produced.
System action
The Global Publish Server starts with empty structures in memory.
User response
Check the trace logs for additional diagnostic information.
CYNG0049I: The Global Publish Server was initialized with
data stored in the database. The Token map size is size1, and
the Thread map size is size2.
Explanation
The Global Publish Server successfully restored data cached in the database and
begins operating as normal.
234
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNG0051E: The Global Publish Server encountered an
exception while attempting to retrieve a request record from
the in-memory cache.
Explanation
The Global Publish Server maintains a cache of stripped-down request records for
requests that have completed, but are participating in active composite
transactions. The Global Publish Server attempted to access a record in this cache
and an exception was caught.
System action
An empty RequestRecord is substituted.
User response
Check the trace logs for additional diagnostic information.
CYNG0052I: The Global Publish Server has mapped in-flight
tokens tokenList to permanent tokens returnList.
Explanation
The tokens used in-flight by the Global Publish Server are too small to guarantee
long-term uniqueness. Before allowing the records to be saved to the database, the
Global Publish Server generates a permanent token for each in-flight token.
CYNG0053I: A stop request was received. The Global Publish
Server backs up its information to the database.
Explanation
When the Global Publish Server receives a shutdown request, it backs up
information about all unresolved composite transactions to the database. This
information is restored when the server is restarted.
CYNG0054E: The Global Publish Server caught an exception
while attempting to back up the Token map as part of a
standard shutdown.
Explanation
When the Global Publish Server shuts down, it backs up its memory structures to
the database so they can be restored when the server is restarted. An exception
was caught during this process.
System action
The backup transaction is rolled back, and shutdown continues.
User response
Check the trace logs for additional diagnostic information.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
235
CYNG0055E: The Global Publish Server caught an exception
while attempting to back up the Thread Map as part of a
standard shutdown.
Explanation
When the Global Publish Server shuts down it backs up its memory structures to
the database so they can be restored when the server is restarted. An exception
was caught during this process.
System action
The backup transaction is rolled back, and shutdown continues.
User response
Check the trace logs for additional diagnostic information.
CYNG0056I: The Global Publish Server successfully backed
up data to the database.
Explanation
The Global Publish Server successfully completed backing up its data structures
and will now proceed with a graceful shutdown.
CYNG0057E: The Global Publish Server caught an exception
while attempting a graceful shutdown.
Explanation
When the Global Publish Server shuts down it backs up its memory structures to
the database so that they can be restored when the server is restarted. An
exception was caught during this process.
System action
Shutdown continues, but data in memory might not be backed up correctly.
User response
Check the trace logs for additional diagnostic information.
CYNG0058I: Shutdown of the Global Publish Server completed
successfully.
Explanation
The Global Publish Server successfully completed backing up its data structures
and a graceful shutdown is now completed.
CYNG0059I: The Dequeueing Thread started.
Explanation
The Dequeueing Thread reads from the Global Publish Server's inbound queue,
processes the values in the queue, and manages the memory structures.
236
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNG0060I: The Dequeueing Thread is now attempting to
dequeue count records.
Explanation
The Dequeueing Thread reads from the Global Publish Server's inbound queue,
processes the values in the queue, and manages the memory structures.
CYNG0061I: The Global Publish Server's Dequeueing Thread
is attempting to process a gpsInvokeStart record:
processGpsInvokeStart server server id, thread thread id, token
token.
Explanation
See message.
CYNG0062I: The Global Publish Server's Dequeueing Thread
is attempting to process a gpsInvokeEnd record:
processGpsInvokeEnd server server id, thread thread id, token
token, star time startTime.
Explanation
See message.
CYNG0063I: The Global Publish Server's Dequeueing Thread
is attempting to process a gpsReceiveStart record:
processGpsReceiveStart server server id, thread thread id,
token token, start time startTime.
Explanation
See message.
CYNG0064I: The Global Publish Server's Dequeueing Thread
is attempting to process a gpsReceiveEnd record:
processGpsReceiveEnd server server id, thread thread id,
token token, start time startTime.
Explanation
See message.
CYNG0065I: The Global Publish Server's Dequeueing Thread
is attempting to process a gpsPutStart record:
processGpsPutStart server server id, thread thread id, token
token, start time startTime.
Explanation
See message.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
237
CYNG0066I: The Global Publish Server's Dequeueing Thread
is attempting to process a gpsPutEnd record:
processGpsPutEnd server server id, thread thread id, token
token, start time startTime.
Explanation
See message.
CYNG0067I: The Global Publish Server's Dequeueing Thread
is attempting to process a gpsGetStart record:
processGpsGetStart server server id, thread thread id, token
token, start time startTime.
Explanation
See message.
CYNG0068I: The Global Publish Server's Dequeueing Thread
is attempting to process a gpsGetEnd record:
processGpsGetEnd server server id, thread thread id, token
token, start time startTime.
Explanation
See message.
CYNG0069I: The Global Publish Server's Dequeueing Thread
is attempting to process a gpsGetEnd record:
processRequestRecord server server id, thread thread id, start
time: startTime.
Explanation
See message.
CYNG0070I: The Global Publish Server's Dequeueing Thread
is attempting to process a gpsGetEnd record:
processThreadEnd server server id, thread thread id, start time
startTime.
Explanation
See message.
CYNG0071I: Dequeueing took number milliseconds.
Explanation
The Dequeueing Thread reads from the Global Publish Server's inbound queue,
processes the values in the queue, and manages the memory structures.
238
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNG0072E: The Global Publish Server received a corrupt
message from the Publish Server.
Explanation
An exception was caught while attempting to process a message from the Publish
Server.
System action
The event is dropped.
User response
Check the trace logs for additional diagnostic information.
CYNG0073I: The Global Publish Server's Dequeueing Thread
is exiting now.
Explanation
See message.
CYNG0074I: The Global Publish Server's Dequeueing
Threadhas was killed as a result of a user action.
Explanation
See message.
CYNG0075I: The BackupThread started.
Explanation
BackupThread periodically writes the Global Publish Server's in-memory data to
the database in case of a crash.
CYNG0076E: An error occurred while trying to drop the table
GPSTOKEN from the database.
Explanation
It is possible that this message can occur in the course of normal operations with
no ill effects.
System action
The Global Publish Server continued to the next step.
User response
Check the trace logs for additional diagnostic information.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
239
CYNG0077E: An error occurred while trying to drop the table
GPSTOKENINFO from the database.
Explanation
It is possible that this message can occur in the course of normal operations with
no ill effects.
System action
The Global Publish Server continues to the next step.
User response
Check the trace logs for additional diagnostic information.
CYNG0078E: An error occurred while trying to drop the table
GPSUOE from the database.
Explanation
It is possible that this message can occur in the course of normal operations with
no ill effects.
System action
The Global Publish Server continues to the next step.
User response
Check the trace logs for additional diagnostic information.
CYNG0079E: An error occurred while trying to drop the table
GPSUOEINFO from the database.
Explanation
It is possible that this message can occur in the course of normal operations with
no ill effects.
System action
The Global Publish Server continues to the next step.
User response
Check the trace logs for additional diagnostic information.
CYNG0080E: An error occurred while trying to drop the table
GPSREQUEST from the database.
Explanation
It is possible that this message can occur in the course of normal operations with
no ill effects.
240
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
System action
The Global Publish Server continues to the next step.
User response
Check the trace logs for additional diagnostic information.
CYNG0081E: An exception was caught while attempting to
create the tables in which the Global Publish Server backs up
its data structures.
Explanation
See message.
System action
The Global Publish Server continues to the next step.
User response
Check the trace logs for additional diagnostic information.
CYNG0082I: BackupThread stopped.
Explanation
The BackupThread periodically writes the Global Publish Server in-memory data to
the database to allow for crash recovery.
CYNG0083I: BackupThread been killed as a result of user
action.
Explanation
The BackupThread periodically writes the Global Publish Server in-memory data to
the database to allow for crash recovery.
CYNG0084E: An error occurred while attempting to back up
the Token map.
Explanation
See message.
System action
The Global Publish Server continues to the next step.
User response
Check the trace logs for additional diagnostic information.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
241
CYNG0085E: Backing up the Token map took number
milliseconds.
Explanation
The Global Publish Server backs up both its Token map and Thread map to the
database periodically to allow for crash recovery.
CYNG0086E: An error occurred while attempting to back up
the Token map.
Explanation
See message.
System action
The Global Publish Server continues to the next step.
User response
Check the trace logs for additional diagnostic information.
CYNG0087E: An error occurred while attempting to back up
the Thread map.
Explanation
See message.
System action
The Global Publish Server continues to the next step.
User response
Check the trace logs for additional diagnostic information.
CYNG0088I: Backing up the Thread map took number
milliseconds.
Explanation
The Global Publish Server backs up both its Token map and Thread map to the
database periodically to allow for crash recovery.
CYNG0089E: An error occurred while attempting to back up
the Thread map.
Explanation
See message.
System action
The Global Publish Server continues to the next step.
242
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
User response
Check the trace logs for additional diagnostic information.
CYNG0090I: The Global Publish Server's CleanupThread
started.
Explanation
CleanupThread prunes resolved and timed out transactions from memory
structures.
CYNG0091I: The Global Publish Server's CleanupThread
declined to prune thread threadId on server ServerId because
the Publish Server had not yet been notified of sampling
values.
Explanation
CleanupThread prunes resolved and timed out transactions from memory
structures. This transaction is pruned after the Publish Server has been notified of
sampling information.
CYNG0092I: Token token is fully resolved, so the system is
removing it from memory.
Explanation
The Global Publish Server's CleanupThread prunes resolved and timed out
transactions from memory structures. This transaction is fully resolved and is
pruned.
CYNG0093I: Thread ThreadId on server ServerId has no
unresolved tokens, so the system is removing it from memory.
Explanation
The Global Publish Server's CleanupThread prunes resolved and timed out
transactions from memory structures. This transaction is fully resolved and is
pruned.
CYNG0094I: The Global Publish Server's CleanupThread took
number milliseconds.
Explanation
CleanupThread prunes resolved and timed out transactions from memory
structures.
CYNG0095E: An exception was caught during the
CleanupThread operation while attempting clean up the Token
and Thread maps.
Explanation
See message.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
243
System action
The Global Publish Server continues to the next step.
User response
Check the trace logs for additional diagnostic information.
CYNG0096I: The Global Publish Server's CleanupThread
finished executing.
Explanation
CleanupThread prunes resolved and timed out transactions from memory
structures.
CYNG0097I: The Global Publish Server's CleanupThread was
killed.
Explanation
CleanupThread prunes resolved and timed out transactions from memory
structures.
CYNG0098I: The Global Publish Server's SamplingThread
started.
Explanation
SamplingThread handles inheritance of sampling values from parent transactions
to child transactions.
CYNG0099I: The Global Publish Server's SamplingThread
could not find information in memory for a thread end event.
Explanation
SamplingThread encountered an error with in-memory structures. The error is
ignored.
CYNG0100I: During a sampling check, the Global Publish
Server failed to find a linked thread. It is sending it back to
queue.
Explanation
The Publish Server requested sampling information for a thread that the Global
Publish Server is unaware of. The Global Publish Server tries again to notify the
Publish Server soon.
244
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNG0101I: The Global Publish Server is notifying Publish
Server componentId that thread threadId on server serverId:
boolean
Explanation
The Publish Server requested sampling information for a thread, and the Global
Publish Server is responding.
CYNG0102E: An exception was caught during SamplingThread
operation.
Explanation
SamplingThread handles responses to Publish Server inquiries about sampling
values.
System action
The Global Publish Server continues to the next step.
User response
Check the trace logs for additional diagnostic information.
CYNG0103I: SamplingThread execution took number
milliseconds.
Explanation
SamplingThread handles responses to Publish Server inquiries about sampling
values.
CYNG0104E: An exception was caught during SamplingThread
operation.
Explanation
SamplingThread handles responses to Publish Server inquiries about sampling
values.
System action
The Global Publish Server continues to the next step.
User response
Check the trace logs for additional diagnostic information.
CYNG0105I: SamplingThread is exiting.
Explanation
SamplingThread handles responses to Publish Server inquiries about sampling
values.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
245
CYNG0106I: SamplingThread was killed as a result of user
action.
Explanation
SamplingThread handles responses to Publish Server inquiries about sampling
values
CYNG0107I: The Global Publish Server's MonitoringThread
started.
Explanation
MonitoringThread checks the status of the other worker threads in the system, and
kills or restarts them if something goes wrong.
CYNG0108I: BackupThread is dead. The Global Publish Server
will start a new one.
Explanation
See message.
CYNG0109I: The Global Publish Server is unable to contact or
stop BackupThread, which is null or does not exist.
Explanation
See message.
CYNG0110I: CleanupThread is dead. The Global Publish
Server will start a new one.
Explanation
See message.
CYNG0111I: The Global Publish Server is unable to contact or
stop CleanupThread, which is null or does not exist.
Explanation
See message.
CYNG0112I: DequeueingThread is dead. The Global Publish
Server will start a new one.
Explanation
See message.
CYNG0113I: The Global Publish Server is unable to contact or
stop DequeueingThread, which is null or does not exist.
Explanation
See message.
246
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNG0114I: SamplingThread is dead. The Global Publish
Server will start a new one.
Explanation
See message.
CYNG0115I: The Global Publish Server is unable to contact or
stop SamplingThread, which is null or does not exist.
Explanation
See message.
CYNG0116E: An exception was caught during MonitorThread
operation.
Explanation
An exception was caught while attempting to check the status of Global Publish
Server worker threads.
System action
The Global Publish Server continues to the next step.
User response
Check the trace logs for additional diagnostic information.
CYNG0117I: SamplingThread is exiting.
Explanation
The SamplingThread is not stopping.
CYNG0118I: The Global Publish Server's SamplingThread was
killed by user action.
Explanation
See message.
CYNG0119E: A client has attempted to connect to the Global
Publish Server and failed as a result of a network error.
Explanation
An exception was caught while attempting to open ObjectInputStreams on the
socket.
System action
The Global Publish Server continues to the next step.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
247
User response
Check the trace logs for additional diagnostic information.
CYNG0120I: Publish Server psId connected to the Global
Publish Server.
Explanation
SamplingThread was killed by user action.
CYNG0121I: An exception occurred in the Socket Listener.
Explanation
See message.
System action
The Global Publish Server is probably unstable.
User response
Check the trace logs for additional diagnostic information.
CYNG0122E: The Global Publish Server was unable to open a
server socket on port Port.
Explanation
A network error was encountered.
User response
Check the trace logs for additional diagnostic information. Restart the Global
Publish Server now.
CYNG0123I: A VEGateway connected to the Global Publish
Server.
Explanation
A VEGateway was created to handle a user request from the front-end.
CYNG0124E: Communication between the front-end and the
Global Publish Server failed.
Explanation
See message.
User response
Check the trace logs for additional diagnostic information. Restart the Global
Publish Server now.
248
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNG0125E: Communication between the front-end and the
Global Publish Server failed.
Explanation
See message.
User response
Check the trace logs for additional diagnostic information. Restart the Global
Publish Server now.
CYNG0126W: A format exception occurred while parsing
property propName. The default value is being used.
Explanation
Various configuration parameters are set in the properties file, and the specified
property is not valid, so the Global Publish Server is using the default value.
Operator response
Check the specified property in the configuration file and make sure it is a valid
numerical value.
CYNG0127E: An exception occurred while the Global Publish
Server was sending data to the Archive Agent.
Explanation
See message.
Operator response
Review the trace logs to determine the cause of the error.
CYNI Messages: Publish Server
The Publish Server is a Java component of the Managing Server that collects and
publishes data. All such messages have IDs in the range CYNI0001E to
CYNI0017E.
CYNI0001E: An error occurred while trying to retrieve the
command agent for Data Collector probeId.
Explanation
To poll PMI information, the command agent from the Data Collector is retrieved.
An error occurred while retrieving it.
Operator response
Ensure that the Data Collector is running. Check the trace logs to determine the
cause of the error.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
249
CYNI0002E: An error occurred while trying to get
PerfSummary for Data Collector probeId.
Explanation
See message.
Operator response
Ensure that the Data Collector is running. Check the trace logs to determine the
cause of the error.
CYNI0003E: An error occurred while trying to get
PerfSnapshot for Data Collector probeId.
Explanation
See message.
Operator response
Ensure that the Data Collector is running. Check the trace logs to determine the
cause of the error.
CYNI0004E: An error occurred while trying to get
ClusterRuntime for Data Collector probeId.
Explanation
See message.
Operator response
Ensure that the Data Collector is running. Check the trace logs to determine the
cause of the error.
CYNI0005E: An error occurred while trying to get
ServerRuntime for Data Collector probeId.
Explanation
See message.
Operator response
Ensure that the Data Collector is running. Check the trace logs to determine the
cause of the error.
CYNI0006E: An error occurred while trying to get
EJBComponents for Data Collector probeId.
Explanation
See message.
250
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
Ensure that the Data Collector is running. Check the trace logs to determine the
cause of the error.
CYNI0007E: An error occurred while trying to get
WebAppComponents for Data Collector probeId.
Explanation
See message.
Operator response
Ensure that the Data Collector is running. Check the trace logs to determine the
cause of the error.
CYNI0008E: An error occurred while trying to get Applications
for Data Collector probeId.
Explanation
See message.
Operator response
Ensure that the Data Collector is running. Check the trace logs to determine the
cause of the error.
CYNI0009E: An error occurred while trying to get
ConnectorConnectionPools for Data Collector probeId.
Explanation
See message.
Operator response
Ensure that the Data Collector is running. Check the trace logs to determine the
cause of the error.
CYNI0010E: An error occurred while trying to get
ExecuteQueues for Data CollectorprobeId.
Explanation
See message.
Operator response
Ensure that the Data Collector is running. Check the trace logs to determine the
cause of the error.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
251
CYNI0011E: An error occurred while trying to get
JDBCConnectionPools for Data Collector probeId.
Explanation
See message.
Operator response
Ensure that the Data Collector is running. Check the trace logs to determine the
cause of the error.
CYNI0012E: An error occurred while trying to get
JTARuntimes for Data Collector probeId.
Explanation
See message.
Operator response
Ensure that the Data Collector is running. Check the trace logs to determine the
cause of the error.
CYNI0013E: An error occurred while trying to get JMSRuntime
for Data Collector probeId.
Explanation
See message.
Operator response
Ensure that the Data Collector is running. Check the trace logs to determine the
cause of the error.
CYNI0014E: An error occurred while trying to get ORBData for
Data Collector probeId.
Explanation
See message.
Operator response
Ensure that the Data Collector is running. Check the trace logs to determine the
cause of the error.
CYNI0015E: An error occurred while trying to get Datasource
for Data Collector probeId.
Explanation
See message.
252
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
Ensure that the Data Collector is running. Check the trace logs to determine the
cause of the error.
CYNI0016E: An error occurred while trying to get SMFRecords
for Data Collector probeId.
Explanation
See message.
Operator response
Ensure that the Data Collector is running. Check the trace logs to determine the
cause of the error.
CYNI0017E: An error occurred while trying to get
RegionInfoIntf for Data Collector probeId.
Explanation
See message.
Operator response
Ensure that the Data Collector is running. Check the trace logs to determine the
cause of the error.
CYNK Messages: Kernel
The following messages relate to the IBM Tivoli Composite Application Manager
for WebSphere kernel services. All such messages have IDs in the range
CYNK0001E to CYNK0071I.
CYNK0001E: Property Property was not found in file File.
Explanation
See message.
Operator response
Edit the properties file associated with the Kernel, for example kl1.properties, and
add the missing property and its value as specified in the default Kernel properties
file.
CYNK0002I: Relationship record RelationshipRecord was
updated, retrieved, deleted, or created. The client and server
IDs associated with the record are ClientId and ServerId.
Explanation
See message.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
253
CYNK0003I: Service Service of component Component on
platform Platform on host and port HostAndPort failed to renew
the contract with the Kernel.
Explanation
See message.
CYNK0004I: Service Service of component Component on
platform Platform on host and port HostAndPortdid not
renewed the contract on time. The Kernel is trying to ping the
component.
Explanation
See message.
CYNK0005I: The contract of service Service of component
Component on platform Platform on host and port HostAndPort
expires at TimeExpires.
Explanation
See message.
CYNK0006I: Service Service of component Component on
platform Platform on host and port HostAndPort has not
renewed the contract with the Kernel on time, but the Kernel
was able to ping the service.
Explanation
See message.
CYNK0007I: The Kernel RMI server has started and is listening
at port number Port.
Explanation
See message.
CYNK0008I: The Kernel started.
Explanation
See message.
CYNK0009I: The Kernel has notified Publish Server
PublishServer of trapping server unavailability. The component
ID of the unavailable server is ComponentId.
Explanation
See message.
254
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNK0010D: Service Service of component Component on
platform Platform on host and port HostAndPort disconnected
from the Kernel.
Explanation
See message.
CYNK0011D: All proxy objects were requested. Service Service
of component Component on platform Platform on host and
port HostAndPort was returned.
Explanation
See message.
CYNK0012D: All clone proxies with generic ID GenericId were
requested. Service Service of component Component on
platform Platform on host and port HostAndPort was returned.
Explanation
See message.
CYNK0013D: All clone proxies with the specified generic ID
were requested. No clone was found.
Explanation
See message.
CYNK0014D: All clone proxies with generic ID GenericId were
requested. Proxy Proxy was returned.
Explanation
See message.
CYNK0015D: All clone proxies with generic ID GenericId were
requested. No clone was found.
Explanation
See message.
CYNK0016D: The Kernel is obtaining monitoring level
information from Data Collector DataCollector. DataCollector is
found to be running at Location.
Explanation
See message.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
255
CYNK0017I: A lookup request was received by the Kernel.
Service Service of component Component on platform Platform
on host and port HostAndPort was returned.
Explanation
See message.
CYNK0018I: The time associated with the service registered
with the Kernel is out of sync with the time associated with
the Kernel. The time reported by the service is TimeService.
The time reported by the Kernel is TimeKernel.
Explanation
See message.
CYNK0019I: The volume statistics for Data Collector
DataCollector were reported by the Publish Server. The
incremental volume is IncrementalVolume. The total volume is
TotalVolume.
Explanation
See message.
CYNK0020I: Service Service of component Component on
platform Platform on host and port HostAndPort has requested
a contract renewal with the Kernel.
Explanation
See message.
CYNK0021I: The component ID ComponentId conflicts with the
one registered.
Explanation
The conflict is being resolved by removing the existing registration record for that
service.
CYNK0022I: Service Service of component Component on
platform Platform on host and port HostAndPort has registered
with the Kernel.
Explanation
See message.
256
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNK0023D: The Kernel is retrieving a list of enabled and
available Data Collectors. The number of results is
NumberResults.
Explanation
See message.
CYNK0024D: The Kernel is retrieving a list of disabled Data
Collectors. The number of results is NumberResults.
Explanation
See message.
CYNK0025I: The configuration repository was Result
successfully.
Explanation
See message.
CYNK0026I: System configuration was Result successfully.
Explanation
See message.
CYNK0027I: The Kernel is broadcasting system configuration
to service Service of component Component on platform
Platform on host and port HostAndPort.
Explanation
See message.
CYNK0028I: The configuration for Data Collector with ID
DataCollectorId was successfully created.
Explanation
See message.
CYNK0029D: All Data Collector configuration information was
successfully retrieved.
Explanation
See message.
CYNK0030I: The Kernel is broadcasting Data Collector
configuration information to service Service of component
Component on platform Platform on host and port HostAndPort.
Explanation
See message.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
257
CYNK0031I: The configuration for trap Trap with ID TrapId was
successfully Result.
Explanation
See message.
CYNK0032I: The Kernel is preparing to broadcast
configuration information for the trap with ID TrapId.
Explanation
See message.
CYNK0033I: Configuration information for the trap with ID
TrapId was found to be deleted. The Kernel is preparing to
broadcast it to Publish Servers.
Explanation
See message.
CYNK0034I: No Publish Server was found to be responsible
for evaluating the trap with ID TrapId.
Explanation
The specified trap ID is not associated with any Publish Server.
CYNK0035I: The Publish Server with component ID
ComponentId was found to be responsible for evaluating the
trap with ID TrapId.
Explanation
The specified Publish Server is responsible for evaluating the specified trap.
CYNK0036I: The Kernel is broadcasting configuration
information for the trap with ID TrapId to the Publish Server
with component ID ComponentId.
Explanation
See message.
CYNK0037I: The schedule with ID ScheduleId was successfully
Result.
Explanation
See message.
CYNK0038I: All schedules were successfully retrieved.
Explanation
See message.
258
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNK0039I: The Kernel is broadcasting the schedule to
service Service of component Component on platform Platform
on host and port HostAndPort.
Explanation
See message.
CYNK0040I: The Kernel shut down.
Explanation
See message.
CYNK0041I: SMF data for Data Collector DataCollector was
already collected by Publish Server PublishServer.
Explanation
See message.
CYNK0042I: An SMF record was created for Data Collector
DataCollector and was collected by Publish Server
PublishServer.
Explanation
See message.
CYNK0043W: The request ID is unknown.
Explanation
See message.
CYNK0044E: There was an undefined Kernel component ID in
Kernel Kernel.
Explanation
See message.
Operator response
Define the component.id property in the Kernel properties file and restart the
Kernel.
CYNK0045E: The Archive Agent proxy object was not found.
The Kernel will retry in TimeRetry seconds.
Explanation
See message.
Operator response
Verify that the Archive Agent started successfully. If not, restart the Archive Agent.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
259
CYNK0046I: Data Collector DataCollector was found to be
Result. The record was successfully sent to Archive Agent
ArchiveAgent.
Explanation
See message.
CYNK0047I: Configuration information for Data Collector with
ID DataCollectorId was successfully retrieved.
Explanation
See message.
CYNK0048W: The SMF key is unknown.
Explanation
See message.
CYNK0049I: All Scheduled configuration information was
successfully retrieved
Explanation
All Scheduled configuration information was successfully retrieved.
CYNK0050D: The Global Publish Server mask is not available
from the properties file. A new one is being created.
Explanation
See message.
CYNK0051W: Global Publish Server mask GpsMask in the
database for Data Collector DataCollector seems to be
corrupted.
Explanation
See message.
CYNK0052I: The current mask value for GPSMASK obtained
from the database is MaskValue.
Explanation
See message.
CYNK0053I: There is no record in the GPSMASK table for Data
Collector DataCollector.
Explanation
See message.
260
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNK0054W: Exception Exception occurred while retrieving
the counter from the database for GPSMASK.
Explanation
See message.
CYNK0055W: Exception Exception occurred while generating
and updating the counter, so the Kernel is trying again for a
second time.
Explanation
See message.
CYNK0056W: Exception Exception occurred for the second
time while generating and updating the counter, so the Kernel
is aborting token generation for GPSMASK.
Explanation
See message.
CYNK0057I: The Kernel is calculating the mask for Data
Collector DataCollector.
Explanation
See message.
CYNK0058I: Exception Exception occurred while converting
the mask string stored in the database to an integer.
Explanation
See message.
CYNK0059I: The Kernel is returning GPSMASK GpsMask for
Data Collector DataCollector.
Explanation
See message.
CYNK0060I: There is no Global Publish Server counter in the
database, so the system is initializing the counter to 1.
Explanation
See message.
CYNK0061I: A Global Publish Server mask exists for Data
Collector DataCollector in the configuration.
Explanation
See message.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
261
CYNK0062I: A Global Publish Server mask does not exist for
the Data Collector. The Kernel is creating a new one.
Explanation
See message.
CYNK0063I: The HTTP codebase server started at listening
port ListeningPort.
Explanation
See message.
CYNK0064I: The .jar file JarFile was requested and
downloaded successfully.
Explanation
See message.
CYNK0065I: The Request For Stub server started at listening
port ListeningPort.
Explanation
See message.
CYNK0066E: IP address IpAddress is not valid. Code download
fails.
Explanation
A valid IP address is required for successful code download.
Operator response
Set nodeauth.ip in the Kernel properties file and restart the Kernel.
CYNK0067I: Service Service successfully registered with the
Kernel.
Explanation
See message.
CYNK0068E: The Kernel was unable to be joined. The
java.rmi.server.codebase property is set to PropertyValue.
Explanation
See message.
Operator response
Ensure that the java.rmi.server.codebase property is set correctly in the Kernel
properties file and that the Kernel can access the files specified in that property.
262
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNK0069E: Database exception Exception occurred while
querying or updating records in tables.
Explanation
See message.
Operator response
Fix the database error and restart the Kernel.
CYNK0070E: An exception occurred while starting the Kernel.
Kernel Kernel is being stopped.
Explanation
See message.
Operator response
Check the exception in the trace file for more information.
CYNK0071I: Kernel WatchDog Service Started .
Explanation
Kernel WatchDog service started.
CYNM Messages: Message Dispatcher
The following messages relate to the Message Dispatcher. All such messages have
IDs in the range CYNM0001E to CYNM0023E.
CYNM0001E: An exception occurred while attempting to
retrieve and unload the system configuration from the Kernel.
Explanation
See message.
Operator response
Verify that the Kernel is up and running. Check the trace logs to determine the
cause of the error.
CYNM0002E: The system configuration from the Kernel is null.
Explanation
See message.
Operator response
Verify that the Kernel is up and running. Check the trace logs to determine the
cause of the error.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
263
CYNM0003E: An exception occurred when the Message
Dispatcher was leaving the Kernel.
Explanation
See message.
Operator response
Verify that the Kernel is up and running. Check the trace logs to determine the
cause of the error.
CYNM0004E: An exception occurred while creating
EmailEngine.
Explanation
See message.
Operator response
Check the trace logs to determine the cause of the error.
CYNM0005E: An exception occurred while creating
TrapDispatcher.
Explanation
The system was unable to contact the Kernel.
Operator response
Ensure that the following system properties: java.security.policy, kernel.codebase,
and kernel.rfs.address. Check the trace logs to determine the cause of the error.
CYNM0006I: TrapDispatcher has started.
Explanation
See message.
CYNM0007I: TrapDispatcher has stopped.
Explanation
See message.
CYNM0008E: An exception occurred while parsing the SNMP
port string.
Explanation
See message.
Operator response
Set the valid port number in the Visualization Engine.
264
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNM0009E: An exception occurred while trying to contact
the Kernel.
Explanation
See message.
Operator response
Check the following system properties: java.security.policy, kernel.codebase, and
kernel.rfs.address.
CYNM0010I: The Message Dispatcher is starting.
Explanation
See message.
CYNM0011E: The system was unable to unmarshall the
TrapDispatcher proxy object.
Explanation
See message.
Operator response
Check the trace logs to determine the cause of the error.
CYNM0012E: An exception occurred while creating
EmailEngine.
Explanation
See message.
Operator response
Check the trace logs to determine the cause of the error.
CYNM0013E: The system property component.id was not
specified.
Explanation
The system property component.id is required to identifying the component.
Operator response
Check the md.properties file and verify that this property is defined.
CYNM0014E: The system property component.listen.port was
not specified.
Explanation
This property is used by the Message Dispatcher.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
265
Operator response
Check the md.properties file and verify that this property is defined.
CYNM0015E: The system property template.directory was not
specified.
Explanation
This property is used by the Message Dispatcher.
Operator response
Check the md.properties file and verify that this property is defined.
CYNM0016E: The system property smtp.host was not
specified.
Explanation
This property is used by the Message Dispatcher.
Operator response
Check the md.properties file and verify that this property is defined.
CYNM0017E: The system property component.listen.port is
not valid.
Explanation
This property is used by the Message Dispatcher.
Operator response
Check the md.properties file and verify that this property is a valid number.
CYNM0018E: An exception occurred while initializing
SNMPV1Api.
Explanation
To send SNMP traps, the Message Dispatcher initializes SNMPV1Api and uses it.
Operator response
Check the trace logs to determine the cause of the error.
CYNM0019E: An exception occurred while setting SNMP peer
parameters.
Explanation
To send SNMP traps, the Message Dispatcher requires SNMP peer parameters
(host and port) to be set. Using the Visualization Engine to set these parameters.
This exception is produced if the parameters used are not valid.
266
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
Ensure that the SNMP peer parameters set correctly in the Visualization Engine.
CYNM0020E: An exception occurred while creating
EmailEngine.
Explanation
See message.
Operator response
Check the trace logs to determine the cause of the error.
CYNM0021E: System property properties.filename is not
defined in mdctl.sh.
Explanation
This property is required to retrieve the system properties of the Message
Dispatcher.
Operator response
Ensure that this property is defined to the right value.
CYNM0023E: An exception occurred while creating
EmailEngine.
Explanation
See message.
Operator response
Check the trace logs to determine the cause of the error.
CYNP Messages: Publish Server
The Publish Server is a Java component of the Managing Server that collects and
publishes data. All such messages have IDs in the range CYNP0001E to
CYNP0088W.
CYNP0001E: An exception occurred while creating AaGateway.
Explanation
AaGateway is used to store data from the Publish Server.
Operator response
Check the trace logs to determine the cause of the error.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
267
CYNP0002E: An exception occurred while creating PsGateway.
Explanation
PsGateway is used to verify trap violations from the Publish Server.
Operator response
Check the trace logs to determine the cause of the error.
CYNP0003I: The Publish Server is establishing a relationship
between probe probe and Publish Server psId.
Explanation
When the Data Collector joins the Publish Server, the Publish Server establishes a
relationship with the Data Collector and registers it with the Kernel.
CYNP0004E: An exception occurred while registering the
Publish Server-Data Collector relationship with the Kernel.
Explanation
This may happen if the Kernel is down or if there is some other problem with
kernel.
Operator response
Verify that the Kernel is up and running. Check the trace logs to determine the
cause of the error.
CYNP0005E: An exception occurred while creating and
starting PMITask for probe octigateID.
Explanation
When the Data Collector joins the Publish Server, the Publish Server registers
PMITask to poll and compute PMI data from the Data Collector. This exception is
thrown if the Publish Server is unable to start the Task.
Operator response
Check the trace logs to determine the cause of the error.
CYNP0006E: The Publish Server got a GC End event before
getting a GC Start event for probe execCtx.
Explanation
The Data Collector sends GC events (Start and End) to the Publish Server in order.
It is an error if the Publish Server gets an End event before getting a Start event.
Operator response
Check the Data Collector logs and trace logs if the Data Collector is dropping the
records or if there are other other errors.
268
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNP0007W: The Publish Server got a GC Start event when
there is already a GC Start event pending for execution
context execCtx.
Explanation
The Data Collector sends GC events (Start and End) to the Publish Server in order.
It is an error if the Publish Server gets a Start event right after getting another GC
Start event without getting an End event for the previous Start event.
Operator response
Check the Data Collector logs and trace logs to determine if the Data Collector is
dropping the records or if there are other errors.
CYNP0008W: The Publish Server failed sending data to the
Archive Agent.
Explanation
The Publish Server uses the AaGateway component inside the Publish Server to
send data to the Archive Agent. This error happens if the AaGateway component
is null.
Operator response
Check the trace logs to determine the cause of the error.
CYNP0009E: An exception occurred processing Method
Record.
Explanation
The Publish Server receives method records from the Data Collector. If the records
are corrupted, the Publish Server produces this exception.
Operator response
Check the trace logs to determine the trace logs to determine the error.
CYNP0010W: The Publish Server is removing the execution
context for the request type requestType from the corrupted
requests.
Explanation
The Publish Server maintains a list of any corrupted requests. If any subsequent
top level request arrives with the same execution context, the Publish Server
removes the corrupted request from the list.
Operator response
Check the trace logs to determine the the error.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
269
CYNP0011W: The Publish Server is dropping the incoming
record for execution context execCtx because this thread is
corrupted.
Explanation
If any request is corrupt and if the Publish Server gets any records for the same
thread, those records are dropped.
Operator response
Check the trace logs to determine the trace logs to determine the error.
CYNP0012E: An exception occurred while processing
RequestLevelRecord.
Explanation
When StandardPSVisitor was processing RequestLevelRecord it encountered an
exception.
Operator response
Check the trace logs to determine the error.
CYNP0013W: The Publish Server dropped a record for the
execution context execCtx.
Explanation
When the Data Collector is unable to process all the events that are generated, it
drops some events and informs the Publish Server. This message indicates that the
Data Collector dropped an event for the specified execution context.
CYNP0014W: An exception occurred while sending the
request to PsGateway.
Explanation
Once the Publish Server receives the complete request, it is sent to PsGateway for
further processing to trigger traps. This message is issued if something fails during
processing the request for a trap.
Operator response
Check the trace logs to determine the error.
CYNP0015W: There is a missing main request for the nested
request with type type on thread execCtx.
Explanation
The Publish Server maintains the request. The requests are listed in the stack in the
order in which they were invoked. If the Publish Server gets the nested request
without the top level request, this warning message is issued.
270
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
Check the trace logs to determine the cause of the error. Also, validate this error
message by checking for dropped records in the logs.
CYNP0016W: There is a missing method trace for the end of
the request on thread execCtx.
Explanation
The Publish Server maintains a stack of requests. The requests are listed in the
stack in the order in which they were invoked. If the Publish Server gets the end
of the request without the start, this warning message is issued.
Operator response
Check the logs to determine if t he Data Collector has recently reconnected to the
Publish Server (a component of the) Managing Server. A reconnection may happen
if either the Data Collector or the Managing Server was restarted, or if network
connectivity is temporarily lost. If a reconnect happens, the start of a request may
happen when the Data Collector is not communicating with the Publish Server.
Then, when the end of the request occurs, the Publish Server emits this warning
message. Next it removes the request as corrupted, issuing a CYNP0010W
message. In such situations, ignore the messages.
CYNP0017W: The Publish Server got a new request when
there was already another request pending on thread execCtx
Explanation
The Publish Server maintains a stack of requests. The requests are listed in the
stack in the order in which they were invoked. If the Publish Server gets the start
of the request when there is already another request pending on the same thread,
this warning message is issued.
Operator response
Check the trace logs to determine the cause of the error. Also, validate this error
message by checking for dropped records in the logs.
CYNP0018W: Matching Start is null for the request type type
on thread execCtx.
Explanation
The Publish Server maintains a stack of requests. The requests are listed in the
stack in the order in which they were invoked. If the Publish Server gets the end
of the nested request without the start of the nested request, this warning message
is issued.
Operator response
Check the trace logs to determine the cause of the error. Also, validate this error
message by checking for dropped records in the logs.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
271
CYNP0019I: RequestRecord is corrupted. The matching
request type is matchingrequesttype. The matching stack depth
is matchingStackDepth. The current request type is
currentRequestType. The current stack depth is
currentStackDepth.
Explanation
The Publish Server maintains a stack of requests. The requests are listed in the
stack in the order in which they were invoked. If the Publish Server does not get
the start and end in the same order, then this message is issued.
Operator response
Check the trace logs to determine the cause of the error. Also, validate this error
message by checking for dropped records in the logs.
CYNP0020W: The start request is missing for the method
trace on thread execCtx.
Explanation
The Publish Server maintains a stack of requests. The requests are listed in the
stack in the order in which they were invoked. If the Publish Server gets method
requests without the top level request, this message is issued.
Operator response
Check the trace logs to determine the cause of the error. Also, validate this error
message by checking for dropped records in the logs.
CYNP0021I: The Publish Server is inferring a request for
method methodId.
Explanation
The Publish Server creates a dummy request if it gets a method record on a thread
without any top level request.
CYNP0022E: The Publish Server could not find the
CLASSLOAD record corresponding to the method with ID
methodId.
Explanation
Data Collector sends the CLASSLOAD events to publish server that contains the
method details. Later when data collector sends method ID in method events,
publish server tries to retrieve method detail corresponding to this. This message
indicates there is no method detail corresponding to method ID in publish server.
272
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
CYNP0023I: The maximum number of records per request has
been reached. So the Publish Server dropped noofrecords
records for execution context execCtx.
Explanation
The Publish Server has a maximum number of method records any request can
contain. The Publish Server drops those records that exceed the maximum.
Operator response
The maximum method record limit can be modified by setting the property
Maximum Method Limit in Visualization Engine - System Properties.
CYNP0024I: The Publish Server is deleting a request for
thread of ID threadId, because the time limit of timeLimit has
elapsed.
Explanation
The Publish Server maintains active requests for a certain configured amount of
time. Any requests that exceed the time limit will be removed.
CYNP0025I: The time difference between the Publish Server
and probe probeId is timeDiffmilliseconds.
Explanation
Publish server uses Managing Server time to keep track of the times of the
requests. Because data collector time can be different than managing server time,
publish server computes the time difference between managing server and data
collector.
CYNP0026E: A exception occurred while getting the time for
probe probeId.
Explanation
Publish server uses Managing Server time to keep track of the times of the
requests. Because data collector time can be different than managing server time,
publish server computes the time difference between managing server and data
collector. This message indicates that publish server was unable to find the time of
data collector.
Operator response
Check the trace logs to determine the cause of the error.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
273
CYNP0027W: The Publish Server could not retrieve the
method detail corresponding to the method with ID methodId
for the execution context execCtx.
Explanation
The Data Collector sends the CLASSLOAD records when the class is loaded, and
in the subsequent events where method events are sent, the Data Collector sends
only the method ID. If the Publish Server doesn't have the method detail before it
gets the method ID, this message is issued.
Operator response
Check the trace logs to determine the cause of the error.
CYNP0028W: An exception occurred while parsing method of
ID methodId for the execution context execCtx.
Explanation
The Data Collector sends the method ID to the Publish Server. This warning is
thrown when the Publish Server fails to convert the method ID string to an integer.
Operator response
Check the trace logs to determine the cause of the error.
CYNP0029E: The Publish Server was unable to load the
system configuration from the Kernel.
Explanation
An exception occurred while retrieving the system configuration from the Kernel.
Operator response
Verify that the Kernel is up and running. Check the trace logs to determine the
cause of the error.
CYNP0030E: The Publish Server was unable to start
ProbeStatsManager.
Explanation
When the Publish Server started, it attempted to start ProbeStatsManager to
manage the statistics of the probe, but ProbeStatsManager failed.
Operator response
Check the trace logs to determine the cause of the error.
274
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNP0031E: The Publish Server was unable to start
ResourceStatsManagerTimer.
Explanation
When the Publish Server started, it attempted to start ResourceStatsManagerTimer
to manage the statistics of the resource, but ResourceStatsManagerTimer failed.
Operator response
Check the trace logs to determine the cause of the error.
CYNP0032E: The Publish Server was unable to start
AVMDataSource.
Explanation
When the Publish Server started, it attempted to start AVMDataSource to manage
the availability statistics of the probe, but AVMDataSource failed.
Operator response
Check the trace logs to determine the cause of the error.
CYNP0033E: The Publish Server was unable to start
AAProducerResetTimer.
Explanation
When the Publish Server started, it attempted to start AAProducerResetTimer to
load balance the Archive Agent connections, but AAProducerResetTimer failed.
Operator response
Check the trace logs to determine the cause of the error.
CYNP0034I: The Publish Server daemon is listening on the
socket at host host on port port.
Explanation
See message.
CYNP0035E: The Publish Server was unable to start. The
socket is already bound to port port.
Explanation
See message.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
275
Operator response
CYNP0036E: An exception occurred when the Message
Dispatcher was leaving the Kernel.
Explanation
See message.
Operator response
Verify that the Kernel is up and running. Check the trace logs to determine the
cause of the error.
CYNP0037I: The Publish Server is shutting down and leaving
the Kernel service at host host on port port.
Explanation
See message.
Operator response
CYNP0038E: An exception occurred while accepting the
connection from the Data Collector.
Explanation
When the Data Collector starts, it establishes a connection with the Publish Server
by using a socket to send data to the Publish Server. The connection failed.
Operator response
Check the trace logs to determine the cause of the error.
CYNP0039E: An exception occurred while reading INIT
records from the Data Collector.
Explanation
The Data Collector sends initialization data as part of the protocol, and the Publish
Server encountered a problem while reading the data.
Operator response
Check the trace logs to determine the cause of the error.
CYNP0040W: An unknown initialization data type of recType
was sent to the Publish Server.
Explanation
INIT data is sent to the Publish Server when any component wants to
communicate with the Publish Server. This error is issued when any component
does not adhere to the protocol.
276
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
Check the trace logs to determine the cause of the error.
CYNP0041E: The socket attached to the Publish Server threw
an exception. data, probeinfo
Explanation
Different components (such as the Data Collector, Visualization Engine, or Global
Publish Server) connect to the Publish Server using the TCP/IP socket.
Operator response
Check the trace logs to determine the cause of the error.
CYNP0042E: An exception occurred while the Publish Server
was reading data from the socket. data, probeinfo
Explanation
See message.
Operator response
Check the trace logs to determine the cause of the error.
CYNP0043E: An exception occurred while the Publish Server
was closing the data socket. data, probeinfo
Explanation
See message.
Operator response
Review the trace logs to determine the cause of the error.
CYNP0044I: The Publish Server is shutting down and leaving
the Kernel service serviceId.
Explanation
The Publish Server has been requested to shut down and it has started shutting
down.
CYNP0045W: The Publish Server received an unexpected
query of type queryType.
Explanation
Any component can query the Publish Server and each query has a type associated
with it. If the Publish Server gets an undefined query type, this message is issued.
Operator response
Check which query type is being invoked and which component is invoking it.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
277
CYNP0046E: The Publish Server got a null system
configuration from the Kernel.
Explanation
When the Publish Server started, it was unable to get the system configuration
from the Kernel.
Operator response
Check the logs of the Publish Server and the Kernel. Also, check the trace logs to
determine the cause of the error.
CYNP0047E: The Publish Server received wrong record data
for the packet header record record1, record2, record3.
Explanation
The Data Collector sends data to the Publish Server in a custom protocol. This
protocol specifies that when the Data Collector sends incorrect information, this
message is issued.
Operator response
Check which component is responsible for the protocol corruption, and check the
logs of that component.
CYNP0048E: An exception occurred with the Publish Server
during communication with probe probeId.
Explanation
See message.
Operator response
Check the trace logs to determine the cause of the error.
CYNP0049E: A communication time out occurred when the
probe was communicating with the Publish Server.
Explanation
See message.
Operator response
Check the trace logs to determine the cause of the error.
CYNP0050I: An unexpected exception occurred with the
socket of Data Collector probeId.
Explanation
Network conditions are a possible cause for this type of error.
278
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNP0051I: An unexpected exception occurred with the
socket of Data Collector probeId.
Explanation
The connection was reset by the peer. Network conditions are a possible cause for
this type of error.
CYNP0052E: An exception occurred while the Publish Server
was being stopped.
Explanation
See message.
Operator response
Check the trace logs to determine the cause of the error.
CYNP0053W: The Publish Server was unable to figure out the
mod level from the request of the Data Collector, so it is using
the default mod level.
Explanation
See message.
CYNP0054E: An exception occurred while the Publish Server
was sending data to the Archive Agent.
Explanation
See message.
Operator response
Check the trace logs to determine the cause of the error.
CYNP0055W: A format exception occurred while parsing
property propName. The default value defaultValue is being
used.
Explanation
The configuration parameters are set in the properties file. The specified property
is not valid, so the Publish Server is using the default value.
Operator response
Check the specified property in the configuration file and ensure that it is a valid
numerical value.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
279
CYNP0056W: An exception occurred while getting PMI data
from the administrative server adminServer at port port of node
nodeName of application server appserverName.
Explanation
An exception occurred while retrieving PMI information from the Data Collector.
Operator response
Check the trace logs to determine the cause of the error.
CYNP0057E: An exception occurred while computing portal
statistics in the Publish Server.
Explanation
The Publish Server gathers portal data from the Data Collector and computes
aggregate statistics for the portal data. An exception occurred during this stage.
Operator response
Check the trace logs to determine the cause of the error.
CYNP0058E: The Publish Server was unable to get the
command agent for probe probeId.
Explanation
To get the time difference between the probe and the Publish Server, the Publish
Server must retrieve the command agent from the Kernel and query for the time.
The Publish Server was unable to retrieve the command agent.
Operator response
Check that the Data Collector and the Kernel are up and running.
CYNP0059E: An exception occurred while getting the time
difference for the probe probeId.
Explanation
The Publish Server invokes the command agent on the Data Collector to compute
the time difference between the probe and the Publish Server.
Operator response
Check the trace logs to determine the cause of the error.
CYNP0060E: An exception occurred when the Publish Server
was stopped.
Explanation
See message.
280
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
Check the trace logs to determine the cause of the error.
CYNP0061E: An exception occurred when the Publish Server
was restarted.
Explanation
See message.
Operator response
Check the trace logs to determine the cause of the error.
CYNP0062W: The Archive Agent buffer was exceeded.
Explanation
The Publish Server sends data to the archive agent using a queue, and if the
maximum queue limit is exceeded, this message is issued.
Operator response
Try to increase the queue size. Check the trace logs to determine the cause of this.
Action
Increase the following settings in the ps1.properties and ps2.properties files:
v # Size of the Queue used to send data records from PS to AA
v #cyanea.ps.aa.maxQueueLength=50
v cyanea.ps.aa.maxQueueLength=5000
Change the default value of 50 for this queue to 5000. You may have to increase
the following setting when you increase the heap size to prevent out of memory
condition:
Set HEAP_MAX_SIZE_PS=1024 in <MS>/bin/setenv.sh
Note: If dropped records are also in the archive agent logs, you must also change
the following property for archive agent in the aa1.properties and aa2.properties
files:
v #queues.method.size=5120
v queues.method.size=20000
Also increase archive agent heap size:
Set HEAP_MAX_SIZE_ARCHIVE_AGENT=1024 in <MS>/bin/setenv.sh.
CYNP0063E: An exception occurred while communicating with
the Kernel to look up the Archive Agent.
Explanation
See message.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
281
Operator response
Make sure the Kernel is up and running. Check the trace logs to determine the
cause of the error.
CYNP0064E: An exception occurred while the Publish Server
was communicating with the Archive Agent.
Explanation
See message.
Operator response
Check the trace logs to determine the cause of the error.
CYNP0065E: An exception occurred while the timeout checker
was pruning active requests in the Publish Server.
Explanation
The TIMEOUT thread is a timer that prunes active requests in the Publish Server
that have been active for more than a specified time. This message is issued when
an error occurs during this process.
Operator response
Check the trace logs to determine the cause of the error.
CYNP0066E: An exception occurred when the Publish Server
was started.
Explanation
See message.
Operator response
Check the trace logs to determine the cause of the error.
CYNP0067I: The Publish Server received an availability
notification from the Kernel regarding the status of Data
Collector probeId. The status is staus.
Explanation
See message.
CYNP0068I: The Publish Server is closing a socket that is not
valid for Data Collector probeId.
Explanation
When the Data Collector is down, the Kernel informs the Publish Server about the
status. The Publish Server closes the socket for the Data Collector.
282
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNP0069W: The socket is still valid with Data Collector
probeID, so the Publish Server is not closing the socket.
Explanation
If the Kernel does not receive the heartbeat from the Data Collector, it can assume
the Data Collector is down and sends the status information to the Publish Server.
Before terminating the connection with the Data Collector, the Publish Server will
check the status of the socket. If the socket is valid, it might wait some time before
it closes the communication with the Data Collector.
CYNP0070W: The Publish Server got a GC End event without
getting GC Start event execCtx.
Explanation
The Data Collector sends GC events (Start and End) to the Publish Server in order.
It is an error if the Publish Server gets an End event before getting a Start Event.
Operator response
Check the Data Collector logs and trace logs to determine whether the Data
Collector is dropping the records or for other errors.
CYNP0071I: The Publish Server is registering probe probeId
with DCAvailabilityChecker.
Explanation
If the Data Collector does not respond with a heartbeat, the Kernel can treat the
Data Collector as unavailable and inform the Publish Server about the status.
Before terminating the connection with the Data Collector, the Publish Server keeps
trying to ping the Data Collector to determine if it is active.
CYNP0072I: An exception occurred while registering probe
probeId with DCAvailabilityChecker.
Explanation
If the Data Collector does not respond with a heartbeat, the Kernel can treat the
Data Collector as unavailable and inform the Publish Server about the status.
Before terminating the connection with the Data Collector, the Publish Server keeps
trying to ping the Data Collector to determine if it is active. This message is issued
if registering the Data Collector with DCAvailabilityChecker fails.
Operator response
Check the trace logs to determine the cause of the error.
CYNP0073I: The Publish Server is unregistering probe probeId
with DCAvailabilityChecker.
Explanation
If the Data Collector does not respond with a heartbeat, the Kernel can treat the
Data Collector as unavailable and inform the Publish Server about the status.
Before terminating the connection with the Data Collector, the Publish Server keeps
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
283
trying to ping the Data Collector to determine if it is active. If the Data Collector
responds to a ping, the Publish Server removes it from DCAvailabilityChecker.
CYNP0074E: An exception occurred in ProbeStatsManager.
Explanation
ProbeStatsManager is used to compute the statistics of the probe. An exception
occurred while computing the statistics.
Operator response
Check the trace logs to determine the cause of the error.
CYNP0075I: The Publish Server is creating an IMSComplex for
complex.
Explanation
IMS transactions spawn across multiple regions, but all of them reside in the same
complex. The Publish Server maintains IMSComplex internally to handle the
multiple regions.
CYNP0076I: Probe probeId has joined complex complex.
Explanation
IMS transactions spawn across multiple regions, but all of them reside in the same
complex. The Publish Server maintains IMSComplex internally to handle the
multiple regions. This message indicates that a probe or region joined the specified
IMSComplex.
CYNP0077I: Probe probeId has left complex complex.
Explanation
IMS transactions spawn across multiple regions, but all of them reside in the same
complex. The Publish Server maintains IMSComplex internally to handle the
multiple regions. This message indicates that a probe region has left the specified
IMSComplex.
CYNP0078I: The request is corrupted for message of ID msgId.
Explanation
The Publish Server maintains the stack of the request internally by capturing the
different events the Data Collector sends for the specified request.
Operator response
Check the trace logs to determine the cause of the error.
CYNP0079W: SNMP Agent is not available.
Explanation
SNMP Agent is used to send SNMP Traps. This message indicates that SNMP
Agent is not available, so traps are not being sent.
284
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
Check the trace logs to determine the cause of the error.
CYNP0080E: An exception occurred while the Publish Server
was sending SNMP Trap.
Explanation
See message.
Operator response
Check the trace logs to determine the cause of the error.
CYNP0081W: Email Engine is not available.
Explanation
Email Engine is used to send Trap e-mails. This message indicates that Email
Engine is not available, so traps are not being sent.
Operator response
Check the trace logs to determine the cause of the error.
CYNP0082E: An exception occurred while the Publish Server
was sending Email Trap.
Explanation
See message.
Operator response
Check the trace logs to determine the cause of the error.
CYNP0083W: The Publish Server is deleting the request of
message ID msgId because the time limit of timeout has
elapsed.
Explanation
The Publish Server maintains an active request for the specified amount of of time.
Any request exceeds this time limit will be removed.
CYNP0084W: The Publish Server is deleting the Global
Publish Server request of message ID msgId because the time
limit of timeout has elapsed.
Explanation
The Publish Server maintains an active request for a specified amount of time. Any
request that exceeds this limit will be removed.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
285
CYNP0085W: The Publish Server received a response of null
for SMF Info for the probe probeId.
Explanation
The Publish Server polled the Data Collector for SMF Info, and received a response
of null for SMF Info.
Operator response
Check the Data Collector logs for more information.
CYNP0086E: The Publish Server received a response of null
for SMFDaily Service for the probe probeIdn.
Explanation
The Publish Server uses SMFDaily Service to retrieve SMF Info from the Data
Collector.
Operator response
Check the Data Collector logs for more information. Check the trace logs to
determine the cause of the error.
CYNP0087E: An exception occurred while parsing SMF Info
from the probe probeId.
Explanation
The Publish Server polled the Data Collector for SMF Info, and received an
exception.
Operator response
Check the Data Collector logs for more information. Check the trace logs to
determine the cause of the error.
CYNP0088W: The Publish Server dropped a record for the
execution context execCtx.
Explanation
If the Publish Server is unable to process all the events that are generated by the
Data Collector, it drops some of the events for the queue context.
Operator response
Check the Publish Server logs for more information. Check the trace logs to
determine the cause of the error.
CYNQ Messages: Port Consolidator
The following messages relate to the Port Consolidator. All such messages have
IDs in the range CYNQ0000 to CYNQ0999.
286
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNQ0001E: Port Consolidator services failed to start.
Explanation
It possible that the Port Consolidator cannot communicate with the Kernel.
System action
The Port Consolidator will shut down now.
Operator response
Check the Port Consolidator configuration and make sure that the Kernel host
name and ports are accurate.
Ensure that the Kernels are up and running.
CYNQ0002I: The Port Consolidator started successfully and
its services are up and running.
Explanation
See message.
CYNQ0003E: The Port Consolidator failed to stop a service.
Explanation
The possible cause of this error is that the Port Consolidator cannot communicate
with the Kernel.
Operator response
Force shutdown the Port Consolidator by passing option forcestop to the startup
script.
Ensure that the Kernels are up running.
CYNQ0004I: Port Consolidator service serviceName has status
status.
Explanation
See message.
CYNQ0005E: The Port Consolidator failed to ping service
serviceName.
Explanation
The possible cause of this error is that the KernelProxyService is not reachable.
Operator response
Shut down and restart the Port Consolidator.
Check trace-portconsolidator.log for more information.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
287
CYNQ0006E: The Port Consolidator failed to list services.
Explanation
The possible cause of this error is that the KernelProxyService is not reachable.
Operator response
Shut down and restart the Port Consolidator.
Check trace-portconsolidator.log for more information.
CYNQ0007E: The Port Consolidator failed to remove services.
Explanation
The possible cause of this error is that the KernelProxyService is not reachable.
Operator response
Shut down and restart the Port Consolidator.
Check trace-portconsolidator.log for more information.
CYNQ0008E: There is an invalid RMI port number.
Explanation
The possible cause of this error is that property proxy.rmi.port contains white
characters.
Operator response
Set proxy.rmi.port to the available port, and restart the Port Consolidator.
Check trace-portconsolidator.log for additional diagnostic information.
CYNQ0009E: There is an unknown host name for
java.rmi.server.hostname.
Explanation
The possible cause of this error is that property java.rmi.server.hostname contains
an invalid host name.
Operator response
Set java.rmi.server.hostname to the valid host name, and restart the Port
Consolidator.
Check trace-portconsolidator.log for additional diagnostic information.
CYNQ0010E: There is an invalid max.ping.failure property.
Explanation
The possible cause of this error is that property max.ping.failure contains white
characters.
288
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
System action
The default value will be set.
User response
It is not necessary to restart the Port Consolidator. Check trace-portconsolidator.log
for additional diagnostic information.
CYNQ0011E: System property am.home has not been
specified.
Explanation
The possible cause of this error is that the installer failed to set property am.home.
User response
Ensure property am.home is specified in proxyserverctrl.sh and restart the Port
Consolidator.
CYNQ0012E: An error occurred when populating properties
from property file filename.
Explanation
The possible cause of this error is that the user does not have write permission for
directory am.home/etc.
User response
Check trace-portconsolidator.log for additional diagnostic information. Grant read
and write permission to am.home/etc.
CYNQ0013E: KernelProxyService failed to export to port
portNum.
Explanation
The possible cause of this error is that the port that KernelProxyService tried to
bind to was not available.
User response
Check trace-portconsolidator.log for additional diagnostic information. Set
proxy.rmi.port to any available port and restart the Port Consolidator.
CYNQ0014E: The Port Consolidator failed to marshall
KernelProxyService.
Explanation
The possible cause of this error is that the JVM failed to serialize
KernelProxyService.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
289
User response
Check trace-portconsolidator.log for additional diagnostic information.
CYNQ0015E: KernelProxyService failed to join the Kernel.
Explanation
The possible cause of this error is that the Kernel is down.
User response
Check trace-portconsolidator.log for additional diagnostic information. The Kernel
may be offline, or there may be a network connectivity issue. Also, check the
following system properties: kernel.codebase and kernel.rfs.address.
CYNQ0016I: KernelProxyService started successfully.
Explanation
KernelProxyService joins the Kernel successfully.
CYNQ0017I: KernelProxyService stopped successfully.
Explanation
See message.
CYNQ0018E: ProbeControllerProxyService failed to export to
port portNum.
Explanation
The possible cause of this error is that the port that ProbeControllerService tried to
bind to was not available.
User response
Check trace-portconsolidator.log for additional diagnostic information. Set
proxy.rmi.port to any available port and restart the Port Consolidator.
CYNQ0019E: The Port Consolidator failed to marshall
ProbeControllerProxyService.
Explanation
The possible cause of this error is that the JVM failed to serialize
ProbeControllerProxyService.
User response
Check trace-portconsolidator.log for additional diagnostic information.
290
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNQ0020E: ProbeControllerProxyService failed to join the
Kernel.
Explanation
The possible cause of this error is that the Kernel is down.
User response
Check trace-portconsolidator.log for additional diagnostic information. The Kernel
may be offline, or there may be a network connectivity issue. Also, check the
following system properties: kernel.codebase and kernel.rfs.address.
CYNQ0021I: ProbeControllerProxyService started successfully.
Explanation
ProbeControllerProxyService joined the Kernel successfully.
CYNQ0022I: ProbeControllerProxyService stopped
successfully.
Explanation
See message.
CYNQ0023E: CommandAgentProxyService failed to export to
port port.
Explanation
The possible cause of this error is that the port that CommandAgentProxyService
tried to bind to was not available.
User response
Check trace-portconsolidator.log for additional diagnostic information. Set
proxy.rmi.port to any available port and restart the Port Consolidator.
CYNQ0024E: The Port Consolidator failed to marshall
CommandAgentProxyService.
Explanation
The possible cause of this error is that the JVM failed to serialize
CommandAgentProxyService.
User response
Check trace-portconsolidator.log for additional diagnostic information.
CYNQ0025E: CommandAgentProxyService failed to join the
Kernel.
Explanation
The possible cause of this error is that the Kernel is down.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
291
User response
Check trace-portconsolidator.log for additional diagnostic information. The Kernel
may be offline, or there may be a network connectivity issue. Also, check the
following system properties: kernel.codebase and kernel.rfs.address.
CYNQ0026I: CommandAgentProxyService started
successfully.
Explanation
CommandAgentProxyService joined the Kernel successfully.
CYNQ0027I: CommandAgentProxyService stopped
successfully.
Explanation
See message.
CYNS Messages: Common Services Address Space
The following messages relate to the IBM Tivoli Composite Application Manager
for WebSphere Common Services Address Space. All such messages have IDs in
the range CYNS0000E to CYNS0107I and apply only to the z/OS platform.
CYNS0000E : CYN1 TASK ALREADY ACTIVE
Explanation
Only one service address space can run per Sysplex node or LPAR. The extraneous
address space is terminated. CYN1 is the MVS™ subsystem name.
User response
None.
CYNS0001W : START CIB NOT FREED
Explanation
The initial operator dialogue control block was not freed. Service address space is
allowed to proceed anyway.
User response
None.
CYNS0002I : CYN1 READY TO ACCEPT COMMANDS
Explanation
The service address space is up and active.
User response
None.
292
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNS0003E : INVALID COMMAND TYPE
Explanation
An invalid operator command type was sent to the service address space. Once the
service address space is running, only Modify or Stop commands are accepted.
Command is disregarded.
User response
Only enter Modify or Stop command.
CYNS0004I : command text
Explanation
An operator Modify command was just entered. This message echoes its text.
User response
None.
CYNS0005I : STOP COMMAND ACCEPTED
Explanation
The STOP command was entered. The service address space acknowledges its
receipt, and starts wrap-up procedures.
User response
None.
CYNS0006I : STOP PENDING
Explanation
The STOP command was entered. This message occurs after message CYNS0005I.
The service address space is in the process of terminating after notifying all
subtasks to stop.
User response
None.
CYNS0007I : CYN1 NOW ACTIVE
Explanation
The service address space is operational and ready to receive client requests. This
message appears in response to the "ACT" modify command.
User response
None.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
293
CYNS0008I : CYN1 NOW INACTIVE
Explanation
The service address space is running but client requests will not be accepted. This
message appears in response to the "INACT" modify command. Use this command
to perform "housekeeping" tasks without being interfering with client requests.
User response
None.
CYNS0009E : PARM FIELD IS MISSING OR INCORRECT
Explanation
The CYN1 address space runs as a started task of which the JCL is in a PROCLIB
member. CYN1 expects the specification of a "PARM=" statement in that JCL.
User response
Either specify a default PARM in the PROCLIB member or override it with your
own in the start command. The PARM statement is of the form "PARM=’XXXX’",
where "XXXX" is appended to the string "CYNP" to form the name "CYNPXXXX".
CYNPXXXX is the name of a member of the library from which CYN1 is executing
(STEPLIB). For example:
S CYN1.CC,PARM='TEST"
will cause CYN1 to try loading the member CYNPTEST from its STEPLIB.
CYNPXXXX modules contain run parameters for the CYN1 address space.
CYNS0010E : UNKNOWN COMMAND
Explanation
The modify command echoed by the CYNS0004I message contains an
unrecognized command verb.
User response
Make sure that the command verb is properly spelled, or that there is no space
after the comma following the task name. For example if CYN1 was started with
the following START command:
S CYN1.CC
when the TRACE command is used, the following MODIFY commands will cause
message CYNS0010E:
F CC,TRAC ON (should be TRACE)
F CC, TRACE ON ( space after the comma)
The following command is valid:
F CC,TRACE ON
294
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNS0011E : INVALID DUMP PARAMETERS
Explanation
One or more parameters in the DUMP modify command are invalid.
User response
Correct the parameter specification and re-enter the command. The DUMP
command is of the following form:
DUMP,AS,hhhhhhhh,n
Where AS stands for "address space", hhhhhhhh is an 8 hexadecimal digit number
specifying the address of the starting memory location to dump, and n the number
(decimal) of bytes to dump.
CYNS0012E : MEMORY NOT AVAILABLE
Explanation
The memory location specified in the address range of the DUMP command or the
address field of the ZAP command is not accessible, i.e., protected or out of range.
User response
Usually low-core 00001000 through 000050000 is not available for display or
zapping.
CYNS0013I: AAAAAAAA XXXXXXXX XXXXXXXX XXXXXXXX
XXXXXXXX|................
Explanation
This line is displayed several times with the DUMP command or twice with the
ZAP command to display the memory range or echo the area being zapped.
AAAAAAAA is the address of the first byte on the corresponding line.
XXXXXXXX is the hexadecimal display of the contents of memory locations 4 bytes
at a time (16 bytes per line). The right hand side of the vertical bar displays the
corresponding EBCDIC characters if valid, otherwise a blank space is printed for
each byte that does not correspond to a valid EBCDIC character. Example:
CYNS0013I: 11284000 C3E8D5C1 F10002DC C0000000
00000000 |CYNA1
{CYNS0013I: 11284010 00000000 00000000 00000000
00000000
|
User response
None.
CYNS0014E : SYSLOG TASK ENDED - CYN1 ENDING
Explanation
The CYN1 main task has detected that the SYSLOG task has ended and is
terminating. The SYSLOG task is the CYN1 tasks which funnels output from the
various CYN1 tasks to the SYSLOG dataset.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
295
User response
Restart the address space after correcting what caused the SYSLOG task to end.
The SYSLOG dataset is full or run out of space. Also see messages CYNS0027E,
CYNS0028E, and CYNS0029E.
CYNS0015E : REMOTE OPERATOR TASK ENDED - CYN1
ENDING
Explanation
The CYN1 main task has detected that the remote operator task ended and is
terminating. The remote operator task allows cross-memory operator command
input through a TSO terminal to the CYN1 address space and routes its output to
the issuing TSO address space rather than the master console.
User response
None. Restart the address space after correcting what caused the remote operator
task to end.
CYNS0016E : COMMAND AREA ALLOCATION FAILED
Explanation
Main memory allocation for an internal data block failed. The corresponding task
(remote operator task) is ending, causing the entire address space to end. This
message is followed by message CYNS0015E.
User response
Restart the address space with enough memory.
CYNS0017I : STATS OPTION NOW SET
Explanation
This message is displayed after a successful completion of the operator STATS
command. It follows a "STATS RESET" or "STATS CUMUL" command. The STATS
command is used to reset the start of SMF statistics history interval.
User response
None.
CYNS0018E : UNKNOWN STATS OPTION. NO ACTION
Explanation
An invalid option was specified in the STATS command.
User response
Only "STATS RESET" or "STATS CUMUL" is allowed. Check for spelling or more
than one blank space between STATS and either RESET or CUMUL.
296
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNS0023I : TRACE OPTION NOW SET
Explanation
This message is displayed after a successful completion of the operator TRACE
command. It follows a "TRACE ON" or "TRACE OFF" command. The TRACE
command causes SYSLOG information messages to be written.
User response
None.
CYNS0024E : UNKNOWN TRACE OPTION. NO ACTION
Explanation
An invalid option was specified in the TRACE command.
User response
Only "TRACE ON" or "TRACE OFF" is allowed. Check for spelling or more than
one blank space between TRACE and either ON or OFF.
CYNS0025E : SYSLOG TASK NOT ACTIVE. NO ACTION
Explanation
This message is displayed after the TRACE, SPINLOG, or STAMP command is
entered when the SYSLOG task is not active (and therefore the address space is in
the process of terminating).
User response
See messages CYNS0014E, CYNS0027E, CYNS0028E, and CYNS0029E.
CYNS0026I : SPINLOG COMMAND ACCEPTED
Explanation
This message acknowledges receipt of the SPIN command by the CYN1 address
space. The SPINLOG specifies to "spin" the SYSLOG dataset, i.e., close then reopen
it.
User response
None, unless messages CYNS0028E or CYNS0029E appear.
CYNS0027E : SYSLOG AREA ALLOCATION FAILED
Explanation
Main memory allocation for an internal data area failed. The corresponding task
(SYSLOG task) is ending, causing the entire address space to end. This message is
followed by message CYNS0014E.
User response
Restart the address space with enough memory.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
297
CYNS0028E : SYSLOG DATASET OPEN FAILED
Explanation
The corresponding task (SYSLOG task) is ending, causing the entire address space
to end. This message is followed by message CYNS0014E.
User response
Correct the problem and restart the CYN1 task. Check the SYSLOG DD statement.
CYNS0029E : SYSLOG DATASET CLOSE FAILED
Explanation
The corresponding task (SYSLOG task) is ending, causing the entire address space
to end. This message is followed by message CYNS0014E.
User response
Correct the problem and restart the CYN1 task. The SYSLOG dataset may be full
or out of space.
CYNS0033E : INVALID ZAP PARAMETERS
Explanation
One or more parameters in the ZAP modify command are invalid.
User response
Correct the parameter specification and re-enter the command. The ZAP command
is of the form:
ZAP,{AS or SS},hhhhhhhh,cccccccc
,nnnnnnnn
Where AS stands for "address space", SS for "authorized address space" (some
low-core memory), hhhhhhhh is an 8 hexadecimal digit number specifying the
address of the memory location to zap, cccccccc the current contents of this
memory location, and nnnnnnnn the value to replace (zap) it with.
CYNS0034E : ADDRESS CONTENTS MISMATCH
Explanation
The contents of the memory location at the address specified in the ZAP command
do not match the actual contents. The ZAP does not take effect.
User response
Correct the parameter specification (address and/or contents) and re-enter the
command. Use the DUMP command to display the current contents of the memory
location to zap.
298
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNS0035I : STAMP OPTION NOW SET
Explanation
This message is displayed after a successful completion of the operator STAMP
command. It follows a "STAMP ON" or "STAMP OFF" command. The STAMP
command causes the logging and time stamping of major events in the CYN1
address space. This function is currently not implemented.
User response
None.
CYNS0036E : UNKNOWN STAMP OPTION. NO ACTION
Explanation
An invalid option was specified in the STAMP command.
User response
Only "STAMP ON" or "STAMP OFF" is allowed. Check for spelling or more than
one blank space between STAMP and either ON or OFF.
CYNS0037E : ERROR LINKING TO CYN1CALL FROM
CYN1FU83
Explanation
While intercepting the SMF records generated by a particular WebSphere
Application Server instance, the corresponding control region encountered the
error. The control region could not access the CYN1 module CYN1FU83, which
replaces exit routine IEFU83.
User response
This is an installation problem; ensure the CYN1FU83 module is either in the
LPALIB or the LINKLIST, or in the STEPLIB statement of the JCL for the control
region PROC.
CYNS0038E : INVALID CPU PARAMETERS
Explanation
One or more parameters in the CPU modify command are invalid.
User response
Correct the parameter specification and re-enter the command. The CPU command
is of the following form:
CPU hhhh
where hhhh is a 4-hexadecimal digit number specifying the ASID (address space
identifier) of the address space to which the CPU command applies.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
299
CYNS0039I: ACCUMULATED CPU FOR ASID XXXX: ssss.sss
Explanation
This message is displayed after a CPU command. XXXX is the ASID (in
hexadecimal) of the corresponding address space. The CPU time is expressed in
seconds, to three decimal places. Under z/OS V1R6 and above, this message is
followed by messages CYNS0040I, CYNS0041I, and CYNS0042I.
User response
None.
CYNS0040I: ASSB_TIME_ON_IFA ASID XXXX: rrrr.rrr
Explanation
This message, along with CYNS0041I and CYNS0042I, is displayed after a CPU
command following message CYNS0039I if running under z/OS V1R6 and above.
XXXX is replaced by the ASID (in hexadecimal) of the corresponding address
space. The CPU times are normalized and expressed in seconds, to three decimal
places. They display respectively the accumulated CPU time spent on IFA
(Integration Facility for Applications) processors, also known as zSeries®
Application Assist Processors (zAAP); the accumulated CPU time spent on Central
Processor (CP); and the accumulated CPU time spent on CP that could have been
spent on zAAP.
User response
None.
CYNS0041I: ASSB_TIME_ON_CP ASID XXXX: ssss.sss
Explanation
This message, along with CYNS0040I and CYNS0042I, is displayed after a CPU
command following message CYNS0039I if running under z/OS V1R6 and above.
XXXX is replaced by the ASID (in hexadecimal) of the corresponding address
space. The CPU times are normalized and expressed in seconds, to three decimal
places. They display respectively the accumulated CPU time spent on IFA
(Integration Facility for Applications) processors, also known as zSeries Application
Assist Processors (zAAP); the accumulated CPU time spent on Central Processor
(CP); and the accumulated CPU time spent on CP that could have been spent on
zAAP.
User response
None.
CYNS0042I: ASSB_TIME_IFA_ON_CP ASID XXXX: tttt.ttt
Explanation
This message, along with CYNS0040I and CYNS0041I, is displayed after a CPU
command following message CYNS0039I if running under z/OS V1R6 and above.
XXXX is replaced by the ASID (in hexadecimal) of the corresponding address
space. The CPU times are normalized and expressed in seconds, to three decimal
places. They display respectively the accumulated CPU time spent on IFA
300
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
(Integration Facility for Applications) processors, also known as zSeries Application
Assist Processors (zAAP); the accumulated CPU time spent on Central Processor
(CP); and the accumulated CPU time spent on CP that could have been spent on
zAAP.
User response
None.
CYNS0043E: INVALID ERBSMFI RETURN CODE: nnnnn
Explanation
This message is output in case a problem was encountered when using the CPU
command. nnnnn is a decimal number giving the error code returned by the
ERBSMFI program used to display CPU time information.
User response
If nnnnn is 256, the ASID you specified in the CPU command does not exist. If
ERBSMFI is not installed in your environment, the return code will be 134 (or
hexadecimal 086, LINK error). Correct the problem, and re-enter the command.
CYNS0045I: CYN1 ID: CYN1DRVR vv.ll.uu mm/dd/yy hh.mn
Explanation
This message is displayed after a VER command. The VER command displays the
current version (vv), level (ll), sub- level (uu) of the CYN1 main task entry point
(CYN1DRVR) and the current date and time (mm, dd, yy, hh, mn) it was
assembled. Example:
01.00.00
CYNS0045I:
06/18/02 16.53
CYN1 ID:
CYN1DRVR
User response
None.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
301
CYNS0100E: NO MORE ENTRY IN SERVER DIRECTORY
CYNS0101E: NO MORE ENTRY IN SERVER/CONTAINER
TABLE
CYNS0102E: NO MORE ENTRY IN SERVER SECTION POOL
CYNS0103E: NO MORE ENTRY IN BEAN SECTION POOL
CYNS0104E: NO MORE ENTRY IN BEAN METHOD SECTION
POOL
CYNS0108E: NO MORE ENTRY IN HTTPSESSMGR SECTION
POOL
CYNS0109E: NO MORE ENTRY IN WEBAPP SECTION POOL
CYNS0110E: NO MORE ENTRY IN SERVLET SECTION POOL
Explanation
When either one of the above messages appears in the CYN1 SYSLOG dataset, the
system was not able to allocate additional space for the corresponding SMF data in
the current interval. The current interval SMF data will be limited to the system
allocated by the system.
User response
The sizes of the various pools, tables, and directories mentioned above are
specified in the CYNPXXXX member loaded by the CYN1 address space when it is
started. This information can be tailored to the particular installation with
assistance from IBM Support: it specifies how many concurrent server instances
SMF records will be written to the SMF data set, how many beans could be
concurrently specified by all the servers during any interval, how many methods
used by all the beans during any interval, and how many Web applications and
servlets could be concurrently specified by all the servers during any interval.
CYNS0105I: RECEIVING A 120 SMF RECORD OF SUBTYPE 3
CYNS0106I: RECEIVING A 120 SMF RECORD OF SUBTYPE 6
CYNS0107I : RECEIVING A 120 SMF RECORD OF SUBTYPE 8
Explanation
The above messages are written to the CYN1 SYSLOG dataset when the SMF exit
routine IEFU83 detected that WebSphere wrote the above SMF records to an SMF
dataset. The exit routine writes the corresponding information in the CYN1
repository. These messages will appear in the SYSLOG dataset if the TRACE option
in the TRACE command is ON.
302
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
User response
None.
CYNVE Messages: Application Monitor
The following messages relate to the Application Monitor. Another name for the
Application Monitor is Visualization Engine. All such messages have IDs in the
range from CYNVE0000E to CYNVE5009E.
CYNVE0000E: username Your login attempt was unsuccessful.
Explanation
ITCAM Visualization Engine login failed.
Operator response
1. Make sure that the user name and password are correct. 2. Verify that the user
has been linked to a correct OS account. 3. Execute authenticate program directly
under $AM_home/bin. The syntax is $AM_home/bin/authenticate {username}
{password}. If the return value is 1, then the user name and password are correct.
If the return value is 2, then the password is incorrect.
CYNVE0002E: A system error has occurred.
Explanation
An unexpected system error occurred.
Operator response
Verify that the database is up and running. Check the VE log file to see if there are
any SQL exceptions.
Note: This error may have occurred because you entered an incorrect DB2 instance
port number during the Managing Server installation.
CYNVE0002E: A system error has occurred. Check VE log files
to get more information about the error.
Explanation
This can happen when you close a problem in Problem Center using a
non-supported browser such as Internet Explorer 7, Opera or Maxon.
Operator response
The product supports Internet Explorer 5.5 and 6.0 only.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
303
CYNVE0003E: You do not have permission to access this
feature.
Explanation
The Visualization Engine privileges are determined by the user role associated with
this account. If the user role does not have permission to access this feature, then
the account cannot access this feature.
Operator response
Verify that the user role associated with this account has permission to access this
feature. 1. Go to User Profile page, find the role associated with this account. 2. Go
to Role Management page, see if the role can access this feature.
CYNVE0004E: Enter your user name.
Explanation
The customer did not enter a user name.
Operator response
Enter the user name.
CYNVE0005E: Enter your Password.
Explanation
The customer did not enter the password.
Operator response
Enter the password.
CYNVE0006E: serverID The server was not found by the
ServerID.
Explanation
This Data Collector can not be found.
Operator response
Verify that the server is configured in the SERVERS table (ISCONFIGURED = 1).
CYNVE0007E: serverID An error occurred while trying to look
up the Data Collector.
Explanation
This Data Collector cannot be found.
Operator response
Turn on the trace log to see the exception trace.
304
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNVE0008E: cloneID The Data Collector was not found by
Kernel.
Explanation
This server clone was not found by CloneID.
Operator response
Ensure that the Data Collector maintains a heart beat with the Kernel.
CYNVE0009E: genericID The Data Collector cannot be found
by Kernel.
Explanation
This server clone was not found by ProbeID.
Operator response
Ensure that the Data Collector is configured in the SERVERS table and maintains a
heart beat with the Kernel.
CYNVE0010E: Your license has expired for product : product.
Explanation
Your license so you cannot use this product.
Operator response
Your license has expired. If it was a Try and Buy license, then you must buy the
Full product license.
CYNVE0011E: The Product does not have a valid license
enrolled.
Explanation
A valid license is not found for the application. The application cannot be used
without a valid license.
Operator response
Follow the instructions in the Installation Guide to enroll the Basic license, the Try
and Buy license which is valid for 60 days, or the Full Product license to use this
product.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
305
CYNVE0012W: You are now using the temporary license. You
need to enroll a license for product : product within 60 days
starting from today : date To perform this operation, refer to
the Installation Guide.
CYNVE0013W: You are still using the temporary license. Your
Try and Buy license will expire after days. You need to enroll a
license for product: product To perform this operation, refer to
the Installation Guide.
CYNVE0014E: An error occurred during the license
Initialization or validation and the return status is : status.
Explanation
Failed to initialize or validate the license because of one or more errors.
Operator response
Refer to the Installation Guide for information about how to enroll the license. Try
to run the application again.
CYNVE0015E: The login page cannot be displayed because
the session could not be created.
Explanation
This application requires a session to be created.
Operator response
Check that cookies are enabled.
CYNVE0018W: You are now using the temporary license. You
need to enroll license for this product within 60 days starting
from today : date
Operator response
Refer to the Installation Guide about how to perform this operation.
CYNVE0019W: You are still using the temporary license. Your
Try and Buy license will expire after days.
Operator response
Refer to the Installation Guide about how to perform this operation.
CYNVE0020E: Cannot delete account.
Explanation
You cannot delete your own account.
306
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNVE0021E: Cannot delete Admin account.
Explanation
You cannot delete the Administrator account.
CYNVE0022E: Cannot delete account, because it is connected
to a report.
Explanation
The account cannot be deleted, because there are reports owned by this account.
CYNVE0023I: Account deleted successfully.
Explanation
The user account was deleted successfully
CYNVE0030E: User Name: UserName already exists
Explanation
The user name you entered already exists. Enter a unique user name.
CYNVE0031I: User account created.
Explanation
The user account was created successfully.
CYNVE0032E: User Name: UName already exists on the
system.
Explanation
The user name you entered already exists on the system. Enter a unique user
name.
CYNVE0040E: First Name: FName is not valid.
Explanation
The first name must contain 1 – 20 alphabetical characters.
CYNVE0041E: Last Name: LName is not valid.
Explanation
The last name must contain 1 - 20 alphabetical characters.
CYNVE0042E: User Name: UserName is not valid.
Explanation
The user name must contain 3 – 255 alphanumeric characters.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
307
CYNVE0043E: OS User Name: OsName is not valid.
Explanation
The OS user name you entered is not valid.
CYNVE0044E: Email: emailName entered is not valid.
Explanation
Enter a valid e-mail address.
CYNVE0045E: Role is not selected.
Explanation
Select a role for this account.
CYNVE0046E: Account form validation failed.
Explanation
Account form validation failed due as a result of incorrect information in the form.
Operator response
Check the fields of the form and correct your information.
CYNVE0047I: Account form validation successful.
Explanation
Your account form validated successfully.
CYNVE0048I: Account modified.
Explanation
Your account was modified successfully.
CYNVE0050E: Invalid Role Name: roleName.
Explanation
The role name must contain 1 — 20 alphabetical characters.
CYNVE0051E: Role Name: roleName already exists.
Explanation
The role name you entered already exists. Enter a unique role name.
CYNVE0052I: Role: roleNamecreated.
Explanation
A new role was created successfully.
308
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNVE0060E: Choose role to delete.
Explanation
Select a role first and then delete.
CYNVE0061I: Role: roleName deleted.
Explanation
The user role was deleted successfully.
CYNVE0062I: Role changed.
Explanation
The user role was changed successfully.
CYNVE0063I: Role: RoleName deleted.
Explanation
The user was deleted successfully.
CYNVE0070E: Invalid Role Name: RoleName.
Explanation
The role name must contain 1 — 20 alphabetical characters.
CYNVE0071E: Role Name: RoleName already exists.
Explanation
The role name you entered is duplicated and already exists. Enter a unique role
name.
CYNVE0072E: Choose a role.
Explanation
Select a role to duplicate.
CYNVE0073I: Role: RoleName duplicated.
Explanation
Role duplicated successfully.
CYNVE0080I: Account does not exist.
Explanation
The account you are trying to access has been deleted.
CYNVE0081I: Account modified.
Explanation
Modification of user account is successful.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
309
CYNVE0110E: Group name is NULL.
Explanation
Enter a unique name for the group.
CYNVE0111E: Invalid group name: grpName
Explanation
The group name can only contain alphanumeric characters.
CYNVE0113E: Group name: grpName already exists.
Explanation
The group name you entered already exists. Enter a unique group name.
CYNVE0114I: Server group: grpName created/modified.
Explanation
The server group was created or modified successfully.
CYNVE0120E: Group name is not selected.
Explanation
To duplicate a group, select a group from the drop-down list.
CYNVE0121E: Group name is NULL or blank.
Explanation
Enter a unique name for the group. Group name cannot be null or blank.
CYNVE0122E: Invalid group name: grpName
Explanation
The group name can only contain alphanumeric characters.
CYNVE0123E: Group name: grpName already exists.
Explanation
The group name you entered already exists. Enter a unique group name.
CYNVE0124I: Server group: grpName duplicated.
Explanation
The server group was duplicated successfully.
CYNVE0130E: Invalid Threshold 1: thrs1
Explanation
Enter a valid Baseline Response Time Alert Level 1 in the range of 1 - 999%.
310
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNVE0131E: Threshold 2 is not valid: thrs2
Explanation
Enter a valid Baseline Response Time Alert Level 2 in the range of 1 - 999%.
CYNVE0132E: Threshold is not valid: thrs
Explanation
The Alert Level 1 value must be less than the Alert Level 2 value.
CYNVE0133E: Day is not valid: duration
Explanation
Enter a valid number of days in the range of 1 - 31 days.
CYNVE0134E: Start date is not valid: sdate
Explanation
You entered a start date that was not valid.
CYNVE0135E: End date is not valid: edate
Explanation
You entered an end date that was not valid.
CYNVE0136E: Date range is not valid: dateRange
Explanation
The start date must occur before the end date.
CYNVE0137E: Response time is not valid: resptime
Explanation
Enter a valid response time in the range of 0-10000.
CYNVE0138E: Gateway is not valid: gateway
Explanation
Enter a valid Gateway Servlet baseline response time in the range of 0 - 10000.
CYNVE0139E: Portal page response time is not valid:
portalRespTime
Explanation
Enter a valid Portal Page baseline response time in the range of 0 - 10000.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
311
CYNVE0140E: Authentication response time is not valid:
autheRespTime
Explanation
Enter a valid authentication baseline response time in the range of 0 - 10000.
CYNVE0141E: Authorization response time is not valid:
authoRespTime
Explanation
Enter a valid authorization baseline response time in the range of 0 - 10000.
CYNVE0142E: Model building response time is not valid:
ModelRespTime
Explanation
Enter a valid model building baseline response time in the range of 0 - 10000.
CYNVE0143E: Page loading response time is not valid:
PageRespTime
Explanation
Enter a valid page loading baseline response time in the range of 0 - 10000.
CYNVE0144E: Portlets baseline response time is not valid:
PortletRespTime
Explanation
Enter a valid portlet baseline response time in the range of 0 - 10000.
CYNVE0145E: Gateway servlet response time threshold is not
valid: gatwayRespTimeThres
Explanation
Enter a valid gateway servlet response time threshold indicator 1 in the range of 0
-999.
CYNVE0146E: Portal Pages Response Time Threshold is not
valid: PortalRespTimeThres
Explanation
Enter a valid portal pages response time threshold indicator 1 in the range of 0
-999.
312
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNVE0147E: Authentication response time threshold is not
valid: AutheRespTimeThres
Explanation
Enter a valid authentication response time threshold indicator 1 in the range of 0
-999.
CYNVE0148E: Authorization response time threshold is not
valid: AuthoRespTimeThres
Explanation
Enter a valid authorization response time threshold indicator 1 in the range of
0-999.
CYNVE0149E: Model building response time threshold is not
valid: ModelRespTimeThres
Explanation
Enter a valid model building response time threshold indicator 1 in the range of
0-999.
CYNVE0150E: Page loading response time threshold is not
valid: PageRespTimeThres
Explanation
Enter a valid page loading response time threshold indicator 1 in the range of
0-999.
CYNVE0151E: Portlets response time threshold 1 is not valid:
PortalRespTimeThres1
Explanation
Enter a valid portlets response time threshold indicator 1 in the range of 0-999.
CYNVE0152E: Gateway servlet response time threshold
indicator 2 is not valid: GatewayRespTimeThres2
Explanation
Enter a valid gateway servlet response time threshold indicator 2 in the range of
0-999.
CYNVE0153E: Portal pages response time threshold indicator
2 is not valid: PortalRespTimeThres2
Explanation
Enter a valid portal pages response time threshold indicator 2 in the range of
0-999.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
313
CYNVE0154E: Authentication response time threshold
indicator 2 is not valid: AutheRespTimeThres2
Explanation
Enter a valid authentication response time threshold indicator 2 in the range of
0-999.
CYNVE0155E: Authorization response time threshold indicator
2 is not valid: AuthoRespTimeThres2
Explanation
Enter a valid authorization response time threshold indicator 2 in the range of
0-999.
CYNVE0156E: Model building response time threshold
indicator 2 is not valid: ModelRespTimeThres2
Explanation
Enter a valid model building response time threshold indicator 2 in the range of
0-999.
CYNVE0157E: Page loading response time threshold indicator
2 is not valid: PageRespTimeThres2
Explanation
Enter a valid page loading response time threshold indicator 2 in the range of
0-999.
CYNVE0158E: Portlets response time threshold indicator 2 is
not valid: PortletsRespTimeThres2
Explanation
Enter a valid portlets response time threshold indicator 2 in the range of 0-999.
CYNVE0159I: Validation successful.
Explanation
Baseline form validation is successful.
CYNVE0162I: Pinging server serverName whose ProbeID is
probeId is successful.
Explanation
The attempt to ping the group of servers was successful. The ping status was
updated.
314
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNVE0163E: Failed to ping server serverName whose
ProbeID is probeId.
Explanation
The attempt to ping the servers failed.
Operator response
Check the Self-diagnosis page to verify the availability of the Probe .
CYNVE0164I: Group groupName deleted successfully.
Explanation
The group was deleted successfully.
CYNVE0170E: Configration object is not selected.
Explanation
Select a configuration object to apply to a server.
CYNVE0171E: Server is not selected for configuration.
Explanation
Select the server to be configured from the unconfigured server list.
Operator response
Check on the Self-diagnosis page to verify the Probe has joined the Kernel. If yes,
then select the Server from the unConfigured Data Collectors menu item.
CYNVE0172E: The limit of data collectors to be monitored has
been exceeded.
Explanation
ITCAM Basic only allows 2 JVMs to be monitored at a time.
Operator response
Verify that the number of configured data collectors is less than 2.
CYNVE0172I: Data Collector server: serverName is configured.
Explanation
Data Collector configuration is successful.
CYNVE0173E: CICS and IMS servers are not monitored by
ITCAM Basic.
Explanation
ITCAM Basic does not support CICS and IMS servers.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
315
Operator response
Verify that none of the selected data collectors to configure is CICS or IMS.
CYNVE0174E: z/OS servers are not supported by ITCAM
Basic.
Explanation
ITCAM Basic does not support z/OS servers.
Operator response
Verify that none of the selected data collectors to configure is a z/OS server.
CYNVE0180E: No servers are selected for unconfiguring.
Explanation
Select a server to unconfigure from the Configured Server list.
Operator response
Check on the Self-diagnosis page to verify the Probe has joined the Kernel. If yes,
then select the Server from the Configure Data Collectors Menu.
CYNVE0181E: Data Collector configuration error.
Explanation
One or more Data Collectors was not configured.
Operator response
Check on the Self-diagnosis page to verify the Probe has joined the Kernel.
CYNVE0182E: Server with id, serverId is unavailable.
Explanation
The server is unavailable.
Operator response
Check the admin console for the application server to see if it is up and running.
CYNVE0182I: Data Collector server: serverName is
unconfigured.
Explanation
The Data Collector was successfully unconfigured.
CYNVE0183E: Security property is not valid: securityProp.
Explanation
Enter a valid value for this property. Valid values are true or false.
316
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
Enter a valid value for this property. Valid values are true or false.
CYNVE0183I: The security property:securityProphas been
saved for server: serverName
Explanation
The security property was successfully saved.
CYNVE0184E: Kernel is unavailable.
Explanation
The kernel is unavailable.
Operator response
Check the Self-diagnosis page to verify that the kernel is up and running.
CYNVE0190E: Configuration object name is invalid:
configName
Explanation
The configuration object name must contain between 4 and 10 alphanumeric
characters. Spaces are not allowed.
CYNVE0191E: Configuration object: configName already exists.
Explanation
The configuration object name you entered already exists.
CYNVE0192E: Configuration object not selected.
Explanation
Select a configuration object to duplicate.
CYNVE0193I: Configuration object configName is duplicated
as: configName
Explanation
The configuration object was successfully duplicated.
CYNVE0200E: Configuration object name is not valid:
configName
Explanation
The configuration object name must contain between 4 and 10 alphanumeric
characters. Spaces are not allowed.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
317
CYNVE0201E: Configuration object: configName already exists.
Explanation
The configuration object name you entered already exists.
CYNVE0202I: Configuration object: configName is modified.
Explanation
The configuration object was successfully modified.
CYNVE0203E: Configuration object name is not valid:
configName
Explanation
The configuration object name must contain between 4 — 10 alphanumeric
characters. Spaces are not allowed.
CYNVE0204E: Configuration object: configName already exists.
Explanation
The configuration object name you entered already exists.
CYNVE0205I: Configuration object: configName is created.
Explanation
The configuration object was created successfully.
CYNVE0206I: Configuration object: configName is applied to
Probe server: ProbeName
Explanation
The configuration object is applied to the Probe, and the Probe is configured
automatically.
CYNVE0207I: Configuration object: configName is deleted.
Explanation
The configuration object was deleted successfully.
CYNVE0208I: Disabling Probe: ProbeName
Explanation
The Probe was disabled successfully.
CYNVE0209I: Enabling Probe: ProbeName
Explanation
The Probe was enabled successfully.
318
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNVE0250E: Polling Frequency is not valid: pollongFreq
Explanation
Enter a numeric value for the Polling Frequency.
CYNVE0251E: Level one Sampling Rate is not valid:
L1samplingRate
Explanation
Enter a valid L1 Sampling Rate in the range of 0-100%.
CYNVE0252E: Level two Sampling Rate is not valid:
L2samplingRate
Explanation
Enter a valid L2 Sampling Rate in the range of 0-100%.
CYNVE0253E: Level three Sampling Rate is not valid:
L3samplingRate
Explanation
Enter a valid L3 Sampling Rate in the range of 0-100%.
CYNVE0254E: Max Method Records is not valid: maxMethRec
Explanation
Enter a valid Maximum Method Records value in the range of 2 – 9999999.
CYNVE0255E: Max Message Length is not valid: maxMesgLen
Explanation
Enter a valid Maximum IMS Message Data Length value in the range of 0 – 32768.
CYNVE0256E: Threshold 1 is not valid: threshold1
Explanation
Enter a valid Baseline Response Time Alert Level 1 in the range of 1-999%.
CYNVE0257E: Threshold 2 is not valid: threshold2
Explanation
Enter a valid Baseline Response Time Alert Level 2 in the range of 1-999%.
CYNVE0258E: Threshold is not valid: threshold
Explanation
The Alert Level 1 value must be less than the Alert Level 2 value.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
319
CYNVE0259E: Duration is not valid: duration
Explanation
Enter a valid number of days in the range of 1-31 days.
CYNVE0260E: Start date is not valid: sdate
Explanation
You entered a start date that was not valid.
CYNVE0261E: End date is not valid: edate
Explanation
You entered an end date that was not valid.
CYNVE0262E: Date range is not valid: dateRange
Explanation
The start date must occur before the end date.
CYNVE0263E: Response time is not valid: respTime
Explanation
Enter a valid response time in the range of 0-10000.
CYNVE0264E: Port number is not valid: portNumber
Explanation
Enter a valid port number in the range of 0-65535.
CYNVE0265E: SNMP Host/IP is not valid: host
Explanation
Enter a valid Hostname or IP Address.
CYNVE0266E: SNMP Comminity is not valid: community
Explanation
Enter a valid community.
CYNVE0267I: System properties validated and saved.
Explanation
The system property form was validated successfully, and the default values were
saved.
CYNVE0270E: Message Dispatcher is unavailable.
Explanation
Unable to contact Message Dispatcher.
320
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
Check on the Self-diagnosis page to verify that the Message Dispatcher has joined
the Kernel.
CYNVE0271I: Testing SNMP message sent to hostName on
port portName with community commuName passed.
Explanation
SNMP test is successful.
CYNVE0272E: Testing SNMP message sent to hostName on
port portName with community commuNamefailed.
Explanation
Unable to send SNMP Message.
Operator response
Check whether the host exists and is alive. Check that the port is not in use by
other applications.
CYNVE0273E: Cannot save SNMP setting.
Explanation
Unable to save SNMP settings.
Operator response
The host may be down. Ensure that the port on that host is not in use by another
application.
CYNVE0280E: Schedule ScheduleName event already exists.
Explanation
A schedule already exists for that time.
CYNVE0281I: Schedule: ScheduleName created.
Explanation
A new schedule was created.
CYNVE0282E: Schedule name is not validScheduleName
Explanation
The schedule name must contain only alphanumeric characters.
CYNVE0283E: Schedule name: ScheduleName already exists.
Explanation
The schedule name already exists.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
321
CYNVE0284I: Schedule is added to: ScheduleName
Explanation
A schedule was added successfully.
CYNVE0285I: Schedule: ScheduleName is deleted
Explanation
A schedule was deleted successfully.
CYNVE0290E: Schedule name: ScheduleName not selected.
Explanation
Select a schedule to duplicate.
CYNVE0291E: Schedule name is not valid: ScheduleName
Explanation
The schedule name must contain only alphanumeric characters.
CYNVE0292E: Schedule name: ScheduleName already exists.
Explanation
The schedule name already exists and cannot be duplicated.
CYNVE0293I: Schedule name: ScheduleName duplicated.
Explanation
The schedule name was duplicated successfully.
CYNVE0301E: L1 Sampling Rate is not validSampleRateL1
Explanation
Enter a numeric value in the range of 0 and 100 for L1 sampling rate.
CYNVE0302E: L2 sampling rate is not validSampleRateL2
Explanation
Enter a numeric value in the range of 0 and 100 for the L2 sampling rate.
CYNVE0303E: L3 sampling rate is not validSampleRateL3
Explanation
Enter a numeric value in the range of 0 and 100 for L3 sampling rate.
CYNVE0304I: Group schedule has changed.
Explanation
The group schedule was changed successfully.
322
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNVE0311E: L1 sampling rate is not validSampleRateL1
Explanation
Enter a numeric value in the range of 0 and 100 for the L1 sampling rate.
CYNVE0312E: L2 sampling rate is not validSampleRateL2
Explanation
Enter a numeric value in the range of 0 and 100 for the L2 sampling rate.
CYNVE0313E: L3 sampling rate is not validSampleRateL3
Explanation
Enter a numeric value in the range of 0 – 100 for the L3 sampling rate.
CYNVE0314I: Data Collector Server:serverNameschedule has
changed.
Explanation
The server schedule was changed successfully.
CYNVE0321E: L1 sampling rate is not validSampleRateL1
Explanation
Enter a numeric value in the range of 0 – 100 for the L1 sampling rate.
CYNVE0322E: L2 sampling rate is not validSampleRateL2
Explanation
Enter a numeric value in the range of 0 — 100 for the L2 sampling rate.
CYNVE0323E: L3 sampling rate is not validSampleRateL3
Explanation
Enter a numeric value in the range of 0 and 100 for the L3 sampling rate.
CYNVE0324I: The All servers schedule has changed.
Explanation
All servers schedule was changed successfully.
CYNVE0367E: The Specific Data Collector not found.
Explanation
The Data Collector could not be found by using CommandAgent with PROBE_ID.
Operator response
Verify that the passing parameter PROBE_ID has the correct value.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
323
CYNVE0413I: Component panel displayed
Explanation
The component panel that contain links to the Kernel, Data Collector, Publisher,
Archive Agent, Email, Polling Agent and GPS displayed successfully.
CYNVE0340E: Unable to display charts for Recent Activity
display.
Explanation
The graphics environment on your server is not correctly configured.
Operator response
Ensure that X11 is running properly on the application server on which the
Visualization Engine is installed.
CYNVE0341E: The selected server is unavailable.
Explanation
The server selected for Recent Activity display is currently unavailable.
Operator response
Check the self-diagnosis page to verify the availability of the server, or check the
Admin console.
CYNVE0343E: Select a server.
Explanation
Select a server to view Recent Activity data.
Operator response
Select a server from the drop-down list.
CYNVE0344E: Select a metric from the list.
Explanation
Select a metric to view Recent Activity data.
Operator response
Select a metric from the metric 1 drop-down list.
CYNVE0350E: Select a metric from the list to view Recent
Activity.
Explanation
A metric must be selected to view recent activity data.
324
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
Select a metric from the metric 1 drop-down list.
CYNVE0355E: Select a group.
Explanation
A group must be selected to populate the list of servers.
Operator response
Select a group from the drop-down list.
CYNVE0356E: The Recent Activity display feature is not
supported.
Explanation
The Recent Activity display feature is not supported on the CICS platform Data
Collectors.
Operator response
Select a server (non-CICS) for which Recent Activity display is supported.
CYNVE0357E: Select a server.
Explanation
A server must be selected to view Recent Activity data.
Operator response
Select a server from the drop-down list.
CYNVE0358E: The selected server is unavailable.
Explanation
The server selected for Recent Activity display is currently unavailable.
Operator response
Check the self-diagnosis page to verify the availability of the server or check the
Admin console.
CYNVE0359E: Unable to save group/server information in the
session.
Explanation
The selected group/server were unable to be saved to the current session. The EJB
that was used to retrieve the server group information failed.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
325
Operator response
Verify that the 'servers' table exists in the database, and if does, ensure that the
selected server occupies a row in this table.
CYNVE0410E: The data is unavailable.
Explanation
You selected data that is currently unavailable.
Operator response
Select another reporting period to for your report.
CYNVE0411E: Server unavailable.
Explanation
The server is currently unavailable.
Operator response
Select another server or restart the server.
CYNVE0412E: The date is not valid.
Explanation
You entered a date that is not valid. Enter a valid date.
Operator response
Enter a valid date.
CYNVE0420E: No Kernel available.
Explanation
Unable to contact Kernel.
Operator response
The Kernel might not have been started correctly. Try to access Kernel status by
using the klctl.sh kl1 status.
CYNVE0421E: Unable to contact Kernel.
Explanation
Error while contacting Kernel.
Operator response
The Managing Server side Kernel port might be in use or a previous Kernel stop
might not have stopped the Kernel correctly. Kill all the Kernel processes and try
again. Check for a heart beat on the Kernel on the Managing Server side, then
enter (./amctl.sh kl1 ping).
326
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNVE0422E: Unable to contact Polling Agent.pacomponentid
Explanation
Error contacting Polling Agent.
Operator response
On the Managing Server side, check for the heart beat of the Polling Agent; enter
(./amctl.sh pa ping) to check whether it is up or down. Check that the Polling
Agent has joined the Kernel; enter (./amctl.sh kl1 status). Then check whether the
Polling Agent component appears in the Kernel list.
CYNVE0423E: Unable to contact Message
Dispatcher.mdcomponentid
Explanation
Error contacting Message Dispatcher.
Operator response
On the Managing Server side, check for the heart beat of the Message Dispatcher;
enter (./amctl.sh md ping) to check whether it is up or down. Check that the
Message Dispatcher has joined the Kernel; enter (./amctl.sh kl1 status). Then check
whether the Message Dispatcher component appears in the Kernel list.
CYNVE0424E: Unable to contact Global Publish
Server.componentid
Explanation
Error contacting Global Publish Server.
Operator response
On the Managing Server side, check for the heart beat of the Global Publish Server;
enter (./amctl.sh sam1 ping) to check whether it is up or down. Check that the
Global Publish Server has joined the Kernel; enter (./amctl.sh kl1 status). Then
check whether the Global Publish Server component appears in the Kernel list.
CYNVE0425E: Unable to contact Data Collector.componentid
Explanation
Error contacting Data Collector.
Operator response
On the Managing Server side, check whether the Data Collector has joined the
Kernel; enter (./amctl.sh kl1 status) to check whether the Data Collector
component appears in the Kernel list. You can also check whether the Data
Collector is configured properly, and the Data Collector server is restarted after
Data Collector installation. To gather more information, turn on the Data Collector
trace by entering (./amctl.sh dc trace).
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
327
CYNVE0426E: Unable to contact Publish Server.componentid
Explanation
Error contacting Publish Server.
Operator response
On the Managing Server side, check the heart beat of the Publish Server; enter
(./amctl.sh ps1 ping) to check whether it is up or down. Check whether the
Publish Server has joined the Kernel; enter (./amctl.sh kl1 status) to check whether
the Publish Server component appears in the Kernel list.
CYNVE0427E: Unable to contact Archive Agent.componentid
Explanation
Error contacting Archive Agent.
Operator response
On the Managing Server side, check the heart beat of the Archive Agent; enter
(./amctl.sh aa1 ping) to check whether it is up or down. Check whether the
Archive Agent has joined the Kernel; enter (./amctl.sh kl1 status) to check whether
the Archive Agent component appears in the Kernel list.
CYNVE0428I: Data Collector(Probe) is not available.
Explanation
Error contacting Data Collector(Probe) since it is not configured.
Operator response
Data Collector might be in the unconfigured state. Check the unconfigured Data
Collector list, and configure the Data Collector.
CYNVE0431I: Kernel link clicked.
Explanation
Kernel view displayed successfully.
CYNVE0432I: Data Collector link clicked.
Explanation
Data Collector Controller view displayed successfully.
CYNVE0433I: Data Collector link clicked.
Explanation
Data Collector displayed successfully.
328
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNVE0434I: Publish Server link clicked.
Explanation
Publisher displayed successfully.
CYNVE0435I: Archive Agent link clicked.
Explanation
Archive Agent displayed successfully.
CYNVE0436I: Email link clicked.
Explanation
Email displayed successfully.
CYNVE0437I: GPS link clicked.
Explanation
GPS view displayed successfully.
CYNVE0438I: Polling agent link clicked.
Explanation
Polling Agent view displayed successfully.
CYNVE0439E: Unable to display self-diagnosis page.
Explanation
None of the views (Kernel, Data Collector, Publisher, Archive Agent, Email, GPS or
Polling Agent) display correctly.
CYNVE0471E: No Data Available
Explanation
Unable to retrieve Data from the Database
Operator response
This might be because the archive agnet is down or the Database has been
corrupted. Ensure that the Database is not corrupted.
CYNVE0490E: Access is denied to delete this top report.
Explanation
You do not have permission to delete this report.
Operator response
Ensure that the account has correct access to the selected server groups and
servers.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
329
CYNVE0491E: Access is denied to modify this report.
Explanation
You do not have permission to modify this report.
Operator response
Ensure that the account has correct access to the selected server groups and
servers.
CYNVE0492E: Access is denied to view this top report.
Explanation
You do not have permission to access to any group.
Operator response
Ensure that the account has correct access to the selected server groups and
servers.
CYNVE0493E: Duplicate report name entered.
Explanation
The user entered a report name that already exists. Enter a unique report name.
Operator response
Enter a unique Report name to save this Report.
CYNVE0494E: The report name field is blank.
Explanation
You have not entered a report name. Enter a unique report name
Operator response
The report name field cannot be blank. Enter a unique report name to save this
report.
CYNVE0495E: E-mail report link cannot function.
Explanation
To e-mail a link, save the report first.
Operator response
You need to save the report first, and then try sending the e-mail report link.
CYNVE0496E: Access is denied to create this Portal Report.
Explanation
You do not have permission to access to any group of Portal Servers.
330
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
Make sure the account has proper access to selected server group of portal servers
to perform this operation.
CYNVE0497E: Access denied to create this Portal Report.
Explanation
The System currently does not have any portal servers.
Operator response
Ensure that the account has correct access to one or more portal servers to perform
this operation.
CYNVE0500E: Report type is not supported.
Explanation
The selected report type is not supported by the selected Data Collector.
Operator response
Select a report type that the selected Data Collector supports.
CYNVE0500I: Server aggregation selected.
Explanation
The server aggregation was successfully selected.
CYNVE0500W: Modifying the top report.
Explanation
You modified a saved top report.
CYNVE0501E: Modify report denied.
Explanation
You do not have permission to modify this report.
CYNVE0501I: Creating a schedule report.
Explanation
You created an availability schedule report.
CYNVE0501W: Modifying the report.
Explanation
You modified a saved report.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
331
CYNVE0502E: Recurrence is not supported.
Explanation
Recurrence is not supported for this type of report.
Operator response
Recurrence is not supported for Top Reports.
CYNVE0502I: Creating a report.
Explanation
You created an availability report.
CYNVE0502W: Modifying the report.
Explanation
You modified the saved scheduled report.
CYNVE0503E: Error modifying the report.
Explanation
An error occurred while modifying the report.
CYNVE0503I: Creating a top report.
Explanation
You created a top report.
CYNVE0503W: Modifying the report.
Explanation
You modified a saved report.
CYNVE0504E: Recurrence is not supported.
Explanation
By default, recurrence is not supported.
CYNVE0504I: Modifying a schedule Report.
Explanation
You modified a schedule report.
CYNVE0505I: Modifying a report.
Explanation
You modified a saved report.
332
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNVE0510E: The date range StartDate is not valid.
Explanation
You entered a date range Start Date that is not valid.
Operator response
Select a valid Start Date.
CYNVE0511E: The date range End Date is not valid.
Explanation
You entered a date range End Date that is not valid.
Operator response
Select a valid End Date after the Start Date.
CYNVE0512E: The date range End Date must be after the Start
Date.
Explanation
The date range End Date must occur after the Start Date.
Operator response
Select the End Date after the Start Date.
CYNVE0513E: The graphical environment is not set up
correctly on your server.
Explanation
The graphical environment is not set up correctly on your server.
Operator response
Refer to the Installation Guide for more information about setting up a graphical
environment.
CYNVE0514E: The contrast report is no longer compatible.
Explanation
The contrast report is no longer compatible. Choose another report by modifying
the current report.
Operator response
Choose another report for comparison.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
333
CYNVE0515E: No stored report is selected.
Explanation
No stored report is selected. Select a report.
Operator response
Select a stored report.
CYNVE0520E: The time entered is not valid.
Explanation
You entered a time that is not valid. Enter a valid time.
Operator response
Enter a valid time in the format of HH:MM, for example, 21:30.
CYNVE0521E: An e-mail address was entered that is not valid.
Explanation
You entered an e-mail address that is not valid. Enter a valid e-mail address.
Operator response
Enter a valid e-mail address. For multiple addresses, separate with commas.
CYNVE0522E: The dates entered are not valid.
Explanation
You entered a dates entry that is not valid.
Operator response
Enter a valid numeric date. For multiple dates, separate with commas.
CYNVE0523E: The weeks entered are not valid.
Explanation
You entered a weeks entry that is not valid.
Operator response
Enter a valid numeric week.
CYNVE0524E: The months entered are not valid.
Explanation
You entered a months entry that is not valid.
Operator response
Enter a valid numeric month.
334
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNVE0530E: The report name is not valid.
Explanation
You entered a report name that is not valid.
Operator response
Enter a valid report name.
CYNVE0531E: Duplicate report name entered.
Explanation
You entered a report name that already exists. Enter a unique report name.
Operator response
Enter a unique report name to save this report.
CYNVE0532E: Error saving the report.
Explanation
An error occurred while saving the report.
Operator response
Make sure the Managing Server and database are up and running.
CYNVE0550E: E-mail address is not valid.
Explanation
You entered a e-mail address that is not valid. Enter a valid e-mail address.
Operator response
Enter a valid e-mail address.
CYNVE0560E: Action denied. Cannot send an e-mail.
Explanation
To e-mail a link, save the report first.
Operator response
Save the report and then try to e-mail the report.
CYNVE0561E: Error in sending an e-mail.
Explanation
An error occurred while trying to send the e-mail.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
335
Operator response
Verify the SNMP host address on md.properties of the Message Dispatcher. Ensure
that the correct host address is set and that the Message Dispatcher is up and
running.
CYNVE0570E: The elapsed time threshold is not valid.
Explanation
You entered a value for the elapsed time threshold field that is not valid.
Operator response
Enter a numeric value for elapsed time threshold.
CYNVE0571E: The elapsed time threshold is not valid.
Explanation
You entered a value for the CPU time threshold field that is not valid.
Operator response
Enter a numeric value for the CPU time threshold.
CYNVE0581E: The graphical environment is not set up
correctly on your server.
Explanation
The graphical environment is not set up correctly on your server.
Operator response
Refer to the Installation Guide for more information about setting up a graphical
environment.
CYNVE0582E: No report name was entered.
Explanation
No report name was entered. Enter a unique report name.
Operator response
You did not enter a report name to save. Enter an unique name to save this report.
CYNVE0583E: Error while saving the report.
Explanation
An error occurred while saving the report.
Operator response
Ensure that the Managing Server and database are up and running.
336
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNVE0584E: Duplicate report name entered.
Explanation
You entered a report name that already exists. Enter a unique report name.
Operator response
Enter a unique report name to save this report.
CYNVE0585E: Access is denied to view this report.
Explanation
You do not have the permissions to view this report.
Operator response
Ensur that the account has the correct access to the selected server groups and
servers.
CYNVE0586E: The requested report is not available.
Explanation
You requested a report that is not available.
Operator response
Verify the REPORTDEF table on the database against corresponding report ID.
CYNVE0587E: Access denied to save this report.
Explanation
You do not have the permissions to save this report.
Operator response
Ensure that the account has proper access to selected server groups and servers.
CYNVE0590E: The requested top report is not available.
Explanation
You requested a top report that is not available.
Operator response
Verify the REPORTDEF table on the database against the corresponding report ID.
CYNVE0591E: Access is denied to view this top report.
Explanation
You do not have permission to view this top report.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
337
Operator response
Ensure that the account has correct access to the selected server groups and
servers.
CYNVE0760E: A server error has occurred.
Explanation
A server error occurred. The system is unable to communicate with the server at
this time.
Operator response
Check the self-diagnosis page to ensure that one or more Data Collectors are up
and running.
CYNVE0761E: The Publish Server is unavailable.
Explanation
A Publish Server error occurred. The system is unable to communicate with the
server at this time.
Operator response
Check the self-diagnosis page to ensure that one or more Publish Servers are up
and running.
CYNVE0762E: The Kernel is unavailable.
Explanation
A Kernel error occurred. The system is unable to communicate with the server at
this time.
Operator response
Check the self-diagnosis page to ensure that Kernel1 or Kernel2 is up and running.
CYNVE0763E: The server could not be found.
Explanation
The selected server is unavailable at this time.
Operator response
Check the self-diagnosis page to ensure the availability of the server.
CYNVE0764E: The task cannot be completed.
Explanation
A command agent error occurred. The system is unable to communicate with the
server at this time.
338
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
Check the self-diagnosis page to ensure the availability of the server.
CYNVE0765I: The transaction finished executing.
Explanation
The selected transaction is no longer active. Select another active transaction.
Operator response
Start another long running transaction and try a Method Trace.
CYNVE0766I: The request finished executing.
Explanation
The selected request is no longer active. Select another active request.
Operator response
Start another long running request and try a Method Trace.
CYNVE0770E: The Publish Server is unavailable.
Explanation
The Publish Server is needed to retrieve Request Record information to be
displayed in the In-flight requests section.
Operator response
Check the self-diagnosis page to ensure that one or more Publish Servers are up
and running.
CYNVE0771E: The selected server is unavailable.
Explanation
The selected server is unavailable at this time.
Operator response
Check the self-diagnosis page to ensure the availability of the servers.
CYNVE0772E: There are no servers in the selected group.
Explanation
There are no servers in the selected group.
Operator response
Check the Server Group Management page and ensure that the group you selected
has some servers as group members.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
339
CYNVE0773E: The kernel is unavailable.
Explanation
The kernel is unavailable.
Operator response
Check the self-diagnosis page to ensure that the kernel is up and running.
CYNVE0780E: A server error occurred.
Explanation
A server error occurred. The system is unable to communicate with the server at
this time.
Operator response
Check the self-diagnosis page to ensure that one or more Data Collectors are up
and running.
CYNVE0781E: The Publish Server is unavailable.
Explanation
A Publish Server error occurred. The system is unable to communicate with the
server at this time.
Operator response
Check the self-diagnosis page to ensure that one or more Publish Servers are up
and running.
CYNVE0782E: The Kernel is unavailable.
Explanation
A Kernel error occurred. The system is unable to communicate with the server at
this time.
Operator response
Check the self-diagnosis page to ensure that Kernel1 or Kernel2 is up and running.
CYNVE0783E: The server could not be found.
Explanation
The selected server is unavailable at this time.
Operator response
Check the self-diagnosis page to ensure the availability of the server.
340
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNVE0784I: The transaction finished executing.
Explanation
The selected transaction is no longer active. Select another active transaction.
Operator response
Start another long running transaction and try a Method Trace.
CYNVE0785I: The request finished executing.
Explanation
The selected request is no longer active. Select another active request.
Operator response
Start another long running request and try a Method Trace.
CYNVE0790E: A server error occurred.
Explanation
A server error occurred. The system is unable to communicate with the server at
this time.
Operator response
1. Check the self-diagnosis page to ensure that the Data Collector is up and
running. 2. Check that proxy port is not blocked by firewall
CYNVE0791E: The Publish Server is unavailable.
Explanation
A Publish Server error occurred. The system is unable to communicate with the
server at this time.
Operator response
Check the self-diagnosis page to ensure that one or more Publish Servers are up
and running.
CYNVE0792E: The kernel is unavailable.
Explanation
A Kernel error occurred. The system is unable to communicate with the server at
this time.
Operator response
Check the self-diagnosis page to ensure that Kernel1 or Kernel2 is up and running.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
341
CYNVE0793E: The active server is unavailable.
Explanation
4
The selected server is unavailable at this time.
Operator response
Check the self-diagnosis page to ensure the availability of the servers.
CYNVE0800E: A server error occurred.
Explanation
A server error occurred. The system is unable to communicate with the server at
this time.
Operator response
Check the self-diagnosis page to ensure that the Data Collector is up and running.
CYNVE0801E: The Publish Server is unavailable.
Explanation
A Publish Server error occurred. The system is unable to communicate with the
server at this time.
Operator response
Check the self-diagnosis page to ensure that one or more Publish Servers are up
and running.
CYNVE0802E: The kernel is unavailable.
Explanation
A Kernel error occurred. The system is unable to communicate with the server at
this time.
Operator response
Check the self-diagnosis page to ensure that Kernel1 or Kernel2 is up and running.
CYNVE0803E: The active server is unavailable.
Explanation
The selected server is unavailable at this time.
Operator response
Check the self-diagnosis page to ensure the availability of the servers.
342
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNVE0810E: Select a group.
Explanation
You did not select a group.
Operator response
Select a group from the group selection drop-down list.
CYNVE0811E: Select a server.
Explanation
You did not select a server.
Operator response
Select a server from the server selection drop-down list.
CYNVE0820E: A server error occurred.
Explanation
A server error occurred. The system is unable to communicate with the server at
this time.
Operator response
Check the self-diagnosis page to ensure that one or more Data Collectors are up
and running.
CYNVE0821E: The Publish Server is unavailable.
Explanation
A Publish Server error occurred. The system is unable to communicate with the
server at this time.
Operator response
Check the self-diagnosis page to ensure that one or more Publish Servers are up
and running.
CYNVE0822E: The Kernel is unavailable.
Explanation
A Kernel error occurred. The system is unable to communicate with the server at
this time.
Operator response
Check the self-diagnosis page to ensure that Kernel1 or Kernel2 is up and running.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
343
CYNVE0823E: The server could not be found.
Explanation
The selected server is unavailable at this time.
Operator response
Check the self-diagnosis page to ensure the availability of the server.
CYNVE0824I: The transaction finished executing.
Explanation
The selected transaction is no longer active. Select another active transaction.
Operator response
Start another long running transaction and try a Method Trace.
CYNVE0825I: The request finished executing.
Explanation
The selected request is no longer active. Select another active request.
Operator response
Start another long running request and try a Method Trace.
CYNVE0830E: A server error occurred.
Explanation
A server error occurred. The system is unable to communicate with the server at
this time.
Operator response
Check the self-diagnosis page to ensure that one or more Data Collectors are up
and running.
CYNVE0831E: The Publish Server is unavailable.
Explanation
A Publish Server error occurred. The system is unable to communicate with the
server at this time.
Operator response
Check the self-diagnosis page to ensure that one or more publish servers are up
and running.
344
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNVE0832E: The kernel is unavailable.
Explanation
A Kernel error occurred. The system is unable to communicate with the server at
this time.
Operator response
Check the self-diagnosis page to ensure that Kernel1 or Kernel2 is up and running.
CYNVE0833E: The server could not be found.
Explanation
The selected server is unavailable at this time.
Operator response
Check the self-diagnosis page to ensure the availability of the server.
CYNVE0834I: The transaction finished executing.
Explanation
The selected transaction is no longer active. Select another active transaction.
Operator response
Start another long running transaction and try a Method Trace.
CYNVE0835I: The request finished executing.
Explanation
The selected request is no longer active. Select another active request.
Operator response
Start another long running request and try a Method Trace.
CYNVE0840E: The server is currently unavailable.
Explanation
The server is currently unavailable.
Operator response
Check the self-diagnosis page to ensure the availability of the servers.
CYNVE0841E: The system is currently unavailable.
Explanation
A command agent error occurred. The system is unable to communicate with the
server at this time.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
345
Operator response
Check the self-diagnosis page to ensure that one or more Data Collectors are up
and running.
CYNVE0842E: No data available for the work area.
Explanation
No data is available for the selected work area.
Operator response
Try a different work area to access the Data.
CYNVE0850E: No classes are instrumented for lock analysis.
Explanation
There are no classes instrumented for lock analysis.
Operator response
Check the BCM properties of the Data Collector and verify that the lock
instrumentation is enabled.
CYNVE0851E: Lock analysis data is not being collected.
Explanation
No lock data is being collected.
Operator response
Check the BCM properties of the Data Collector and ensure that the lock collection
is enabled.
CYNVE0852E: The selected Data Collector does not support
the Lock Analysis feature.
Explanation
The selected Data Collector does not support the Lock Analysis feature.
Operator response
Check the BCM properties on the Data Collector.
CYNVE0853E: An error occurred with the server selection.
Explanation
No server was selected. Select a server.
Operator response
Select a server from the list of servers on the drop-down list.
346
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNVE0854E: The selected server is unavailable.
Explanation
The selected server is unavailable at this time.
Operator response
Check the self-diagnosis page to ensure the availability of the server.
CYNVE0860E: You entered an e-mail address : email that is
invalid.
Explanation
You entered an e-mail address that is not valid.
Operator response
Enter a valid e-mail address for the report or report link to be e-mailed.
CYNVE0870E: An error occurred while trying to send the
e-mail.
Explanation
An error occurred while trying to get the E-mail Engine.
Operator response
Check the self-diagnosis page to ensure the availability of Message Dispatcher.
Also, ensure that smtp.host on md.properties is set to your e-mail server IP
address.
CYNVE0871E: To e-mail a link, save the report first.
Explanation
You attempted to e-mail a link for the report without first saving the report.
Operator response
Save the report first and then try again to e-mail the report or link for that report.
CYNVE0880E: Select a search type.
Explanation
You did not select any search type on which to perform the search.
Operator response
Select a search type on which to perform the search.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
347
CYNVE0881E: Enter a search value.
Explanation
You did not enter any search value on which to perform the search.
Operator response
Enter the search value on which to perform the search.
CYNVE0882E: You entered a search value : searchVal that is
not valid.
Explanation
You entered a search value that is not valid.
Operator response
Enter a valid search value against the search type on which to perform the search.
CYNVE0883E: You entered a search value : sVal whose length
is : sValLen which exceeds the field limit of 60.
Explanation
You entered a search value that exceeds the field limit of 60. Enter a valid search
value.
Operator response
Enter a valid search value against the search type on which to perform the Search.
CYNVE0884E: You entered a search value : sVal whose length
is : sValLen which exceeds the field limit of 255.
Explanation
You entered a search value that exceeds the field limit of 255. Enter a valid search
value.
Operator response
Enter a valid search value against the search type on which to perform the Search.
CYNVE0885E: You entered a search value : sVal whose length
is : sValLen which exceeds the field limit of 10000.
Explanation
You entered a search value that exceeds the field limit of 10000. Enter a valid
search value.
Operator response
Enter a valid search value against the search type on which to perform the Search.
348
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNVE0920E: The request you selected is complete.
Explanation
The request you selected is complete and no longer active.
Operator response
Select another active request.
CYNVE0921E: Unable to locate the home request in Publish
Server.
Explanation
Unable to locate the selected home request. This is usually a timing issue.
Operator response
Try the home request again because it is usually a timing issue.
CYNVE0930E: The GPS is currently unavailable.
Explanation
The GPS is currently unavailable.
Operator response
Change to the Managing Server directory $AM_home/bin and enter ./amctl.sh
sam1 status
CYNVE0950E: Port number is not valid: hostname
Explanation
Enter an integer value for the port number.
CYNVE0951E: Cannot add Web server.
Explanation
A problem occurred while adding a Web server.
CYNVE0952E: Cannot display Web server.
Explanation
A problem occurred while displaying the Web servers.
CYNVE0953E: HostName/IP Address is not valid: hostname
Explanation
Enter a valid host name or IP address.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
349
CYNVE0954I: Web server with hostname: hostname and Port
Number: hostname is added.
Explanation
Web server was added successfully.
CYNVE0955E: HostName/IP Address: hostname cannot be
added.
Explanation
This web server is already being monitored.
CYNVE0956E: Port is not valid: port, Port number should be in
the range of 1 - 65535.
Explanation
The Port number is out of Range. It must be in the range of 1 - 65535
CYNVE0960E: Problem deleting Web server whose IP and port
is: webserver
Explanation
A problem occurred while deleting a Web server.
CYNVE0961E: Cannot delete Web server whose IP and port is:
webserver
Explanation
A problem occurred while deleting a Web server.
CYNVE0962I: Delete Web server whose IP and port is:
webserver
Explanation
Web Server deleted successfully.
CYNVE1000E: The charts on the Web Overview page cannot
display.
Explanation
Because the graphical environment is not set up correctly, the charts on the Web
Overview page cannot display.
Operator response
Ensure that the virtual frame buffer is up and running.
350
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNVE1001E: The Polling agent is not running.
Explanation
The Polling agent must be running to monitor Web servers.
Operator response
Check on the self-diagnosis page to verify the availability of the Polling agent.
CYNVE1020E: Cannot display Web server.
Explanation
A problem occurred while displaying Web servers. Contact your System
Administrator.
CYNVE1060E: Failed to create Portal Manager EJB.
Explanation
The EJB needed to retrieve portal information was not created.
Operator response
Verify that the database is up and running.
CYNVE1061I: No portal summary data is available for the
server whose server ID is: serverID
Explanation
No portal summary data is available.
CYNVE1070E: The selected server whose server id is:
serverIdis not available.
Explanation
The selected portal server is not available for monitoring.
Operator response
Verify that this server is available on the self-diagnosis page, or check its
availability on the Admin console.
CYNVE1071E: Select a portal server.
Explanation
A portal server has not been selected in the drop-down list on the Portal Overview
page.
Operator response
Select an active portal server from the server list displayed in the drop-down list.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
351
CYNVE1072E: Unable to display the Portal Overview page.
Explanation
The EJB used to retrieve portal server information for this group failed.
Operator response
Ensure that the database is up and running correctly.
CYNVE1073E: The charts on the Portal Overview page cannot
display.
Explanation
Because the graphical environment is not set up correctly, the Portal Overview
page cannot display.
Operator response
Ensure that the virtual frame buffer is up and running.
CYNVE1082E: To configure thresholds, the server must be
assigned to a group.
Explanation
This server is currently in the Unassigned Servers group. Assign this server to a
group before you configure its thresholds.
Operator response
Navigate to the server groups section under Administration, and either create a
new group or add this server to an existing group.
CYNVE1090E: Select a group.
Explanation
You did not select a group.
Operator response
Select a group from the drop-down list.
CYNVE1091E: Select a server.
Explanation
The user did not select a server.
Operator response
Select a server from the drop-down list.
352
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNVE1100E: Select an x-axis metric.
Explanation
You did not select an x-axis metric.
Operator response
Select a demand metric from the x-axis drop-down list.
CYNVE1101E: Select a y-axis metric.
Explanation
You did not select a y-axis metric.
Operator response
Select a supply metric from the y-axis drop-down list.
CYNVE1102E: Select a different y-axis metric.
Explanation
You selected the same metric for both x-axis and y-axis. Enter a different y-axis
metric.
Operator response
Select a different y-axis metric. It must be different than the one selected on the
X-Axis.
CYNVE1103E: Select a valid y-axis max metric.
Explanation
You entered zero or a value that is not valid as the y-axis max metric. Enter a valid
metric that is greater than zero.
Operator response
Enter a y-axis max metric that is greater than zero.
CYNVE1104E: Select a valid y-axis metric.
Explanation
You entered a y-axis metric that is not valid. Enter a valid metric that is in the
range of 1 - 100.
Operator response
Enter a y-axis max metric that is in the range of 1 - 100.
CYNVE1111E: Error running the report.
Explanation
You are trying to run a report that does not exist.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
353
Operator response
Check the database to determine whether the report exists.
CYNVE1112E: Data is unavailable.
Explanation
You are trying to create a report with data that is unavailable.
Operator response
Check the database to determine whether the data is available during the report
Period.
CYNVE1160E: The server with the server id:serverId is
unavailable.
Explanation
The selected server is unavailable.
Operator response
Check the self-diagnosis page or Administrator console for the server to verify
availability.
CYNVE1160I: URL from ITCAMfTT is not valid, the 'cicsOrims'
parameter is null.
Explanation
The value is missing for the 'cicsOrims' parameter. The parameter will not be
passed in the URL for ITCAMfTT.
CYNVE1160W: No installed applications are displayed for this
server, serverName.
Explanation
Unable to retrieve the list of applications installed on this server.
Operator response
Check the self-diagnosis page to ensure that the kernel is up and running.
CYNVE1161E: URL from ITCAMfTT is not valid.
Explanation
URL from ITCAMfTT is not valid.
Operator response
Ensure that the URL passed from ITCAMfTT has all the correct parameters.
354
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNVE1161I: URL from ITCAMfTT is not valid,, the 'inst'
parameter is null.
Explanation
The value is missing for the 'inst' parameter 'inst'. The parameter will not be
passed in the URL for ITCAMfTT.
CYNVE1161W: The link to the Admin console is not available.
Explanation
The link to the Admin console cannot be displayed for this Weblogic server.
Operator response
Check the self-diagnosis page to ensure that the Publish Server is up and running.
CYNVE1162E: Server Overview page is unable to retrieve
information for this group.
Explanation
The EJB used to retrieve server information for this group failed.
Operator response
Ensure that the database is up and running.
CYNVE1162I: URL from ITCAMfTT is not valid, the 'ipAddress'
parameter is null.
Explanation
The value is missing for the 'ipAddress' parameter. The parameter will not be
passed in the URL for ITCAMfTT.
CYNVE1162W: The System Resources information for this
server serverNameis unavailable.
Explanation
The System Resources information for this server cannot be retrieved.
Operator response
Check the self-diagnosis page to ensure that the Publish Server is up and running.
CYNVE1163E: The server serverName is unavailable.
Explanation
The selected server is unavailable.
Operator response
Check the self-diagnosis page or Admin console for the server to verify availability.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
355
CYNVE1163I: URL from ITCAMfTT is not valid, the 'admin'
parameter is null.
Explanation
The value is missing for the 'admin' parameter. The parameter will not be passed
in the URL for ITCAMfTT.
CYNVE1163W: The System Resources information for this
z/OS server is unavailable.
Explanation
The System Resources information for this z/OS server was not retrievable.
Operator response
Check the self-diagnosis page to ensure that the Publish Server is up and running.
CYNVE1164E: The Server was not found in the database.
Explanation
Using all the information from the URL, cannot find the right match of the server
in the database.
Operator response
1. Ensure that all the values from the URL are correct. 2. Check if the specific Data
Collector is up and running. 3. Check if the specific Data Collector is configured. 4.
Check the database, Octigate, table MAPTTSERVERS to determine if the passing
epuuid from the URL has been inserted into the table. 5. Check the database,
Octigate, to ensure that the specific Data Collector is stored in table SERVERS, and
that the value of the passing parameters from the URL match the value of the
table's attribute.
CYNVE1164W: The Publish Server is unavailable.
Explanation
The Publish Server retrieves PMI data to display System Resources information; it
is currently unavailable.
Operator response
Check the self-diagnosis page to ensure that the Publish Server is up and running.
CYNVE1165W: The Publish Server returned no PMI data.
Explanation
The Publish Server retrieves PMI data. When no PMI data is available, the System
Resources page does not display any information.
Operator response
Check the Admin console for this server to verify that PMI settings are turned on
and set appropriately.
356
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNVE1170E: Unable to display data on the Group Overview
page.
Explanation
The Group Overview page is not displaying any data captured from the database.
Operator response
Ensure that the database is up and running, and that the database administrator
can connect to the octigate schema.
CYNVE1171E: Unable to retrieve response time data for the
Group Overview page, as a result of the following exception:
exception
Explanation
Response time data for the Group Overview page was unavailable for retrieval.
Operator response
Ensure that the database is up and running and that the MEMORY_DATA table
exists.
CYNVE1172E: Unable to retrieve throughput data for the
Group Overview page, as a result of the following exception:
exception
Explanation
Throughput data for the Group Overview page was unavailable for retrieval.
Operator response
Ensure that the database is up and running and that the MEMORY_DATA table
exists.
CYNVE1173E: Unable to retrieve response time data for the
Server Overview page, as a result of the following exception:
exception
Explanation
Response time data for the Server Overview page was unavailable for retrieval.
Operator response
Ensure that the database is up and running and that the MEMORY_DATA table
exists.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
357
CYNVE1174E: Unable to retrieve throughput data for Server
Overview page, as a result of the following exception:
exception
Explanation
Throughput data for the Server Overview page was unavailable for retrieval.
Operator response
Ensure that the database is up and running and that the MEMORY_DATA table
exists.
CYNVE1175E: Unable to retrieve data for the Web Server
overview page, as a result of the following exception:
exception
Explanation
Data for the Web Server Overview page was unavailable for retrieval.
Operator response
Ensure that the database is up and running and that the
WEBSERVERCHARTDATA table exists.
CYNVE1176E: Unable to retrieve data for the Portal Overview
page, as a result of the following exception: exception
Explanation
Data for the Portal Overview page was unavailable for retrieval.
Operator response
Ensure that the database is up and running and that the PORTALOVERVIEW table
exists.
CYNVE1177E: Unable to retrieve data for the Portal Summary
pages, as a result of the following exception: exception
Explanation
Data for the Portal Summary page was unavailable for retrieval.
Operator response
Ensure that the database is up and running and that the PORTALSTATS table
exists.
358
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNVE1178E: Unable to process data for the Portal Overview
page.
Explanation
The SQL for retrieving data to be displayed on the portal overview page failed to
return a valid result.
Operator response
Ensure that the PORTALOVERVIEW table has the avgRT and exeCount columns.
CYNVE1179E: Unable to process data for the Portal Summary
pages.
Explanation
Data for the Portal Summary page was unable to be processed.
Operator response
Ensure that the PORTALSTATS table has the avgRT and exeCount columns.
CYNVE1200E: Cannot find any servers by specific groupId:
groupid
Explanation
Data was unavailable for retrieval by EJB, ServerGroupManager.
Operator response
Verify that the database is up and running and that the SERVERS table exists.
CYNVE1201E: Unable to retrieve data from Database, tables
tablename, due to the following SQL Exception: exception
Explanation
An unexpected system error occurred.
Operator response
Verify that the database is up and running and that the table exists. Check the
trace log file to see if there are any SQL exceptions.
CYNVE1202E: Error while retrieving pid from Kernel, probeId =
tablename
Explanation
Unable to retrieve any pid from the Kernel by probeId for one of the following
reasons: 1. The specific DataCollector is currently down. 2. Kernel is currently
down.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
359
Operator response
1. Determine if the DataCollector is available. 2. Determine if the Kernel is
available. 3. Check the Kernel's message log file and VE trace log file for more
exceptions.
CYNVE1206W: No Data Collector is selected to apply
configuration: configName
Explanation
None of the Data Collectors are selected to be added to the applied list
Operator response
Check the self-diagnosis page to see whether the data collector joined the kernel. If
the data collector has joined the kernel, select a data collector from the list of data
collectors to apply the configuration.
CYNVE1300E: Problem finding server as a result of the
following exception: exception
Explanation
Check whether the EJB server is running.
CYNVE1301E: Problem finding alerts as a result of the
following exception: exception
Explanation
Check whether the EJB server is up and running.
CYNVE1302E: Problem finding alerts as a result of the
following exception: exception
Explanation
Ensure that the database (default: octigate) is up and running. Try the command
for db2 database (db2 connect to octigate user [username] using [password]). If the
connection is good, verify that the USERS table (for db2 database - db2 list tables)
exists and has an account.
CYNVE1303E: Problem finding events as a result of the
following exception: exception
Explanation
Check whether the resource adapter is available.
CYNVE1304E: DC is not available
Explanation
Check whether the monitored application server is running.
360
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNVE1330E: Problem finding problem as a result of the
following exception: exception
Explanation
Ensure that the database (default: octigate) is up and running. Try the command
for db2 database (db2 connect to octigate user [username] using [password]). If the
connection is good, verify that the USERS table (for db2 database - db2 list tables)
exists and has an account.
CYNVE1331E: Saving problem by: problem as a result of the
following exception: exception
Explanation
Ensure that the database (default: octigate) is up and running. Try the command
for db2 database (db2 connect to octigate user [username] using [password]). If the
connection is good, verify that the USERS table (for db2 database - db2 list tables)
exists and has an account.
CYNVE1332E: Problem deleting problem by: problem as a
result of the following exception: exception
Explanation
Ensure that the database (default: octigate) is up and running. Try the command
for db2 database (db2 connect to octigate user [username] using [password]). If the
connection is good, verify that the USERS table (for db2 database - db2 list tables)
exists and has an account.
CYNVE1333E: Problem deleting problem by: problem as a
result of the following exception: exception
Explanation
Ensure that the database (default: octigate) is up and running. Try the command
for db2 database (db2 connect to octigate user [username] using [password]). If the
connection is good, verify that the USERS table (for db2 database - db2 list tables)
exists and has an account.
CYNVE1334E: Problem finding problem by: problem as a result
of the following exception: exception
Explanation
Ensure that the database (default: octigate) is up and running. Try the command
for db2 database (db2 connect to octigate user [username] using [password]). If the
connection is good, verify that the USERS table (for db2 database - db2 list tables)
exists and has an account.
CYNVE1335E: The group is not valid: groupId
Explanation
Select a valid group from the Group drop-down list.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
361
CYNVE1336E: The server is not valid: probeId
Explanation
Select a valid server from Server drop-down list.
CYNVE1337E: Input the problem name
Explanation
The problem name field cannot be empty when you add a problem manually.
CYNVE1338E: Input the problem description
Explanation
The problem description field cannot be empty when you add a problem manually.
CYNVE1339E: The time is not valid: time
Explanation
Correct the time.
CYNVE1370E: Fail to call problem finder
Explanation
Ensure that the problem finder resource adapter is available
CYNVE1429I: Component link: kernelinstant on left panel is
shown correctly.
Explanation
Kernel instance is available and displayed successfully.
CYNVE1430I: Component link: compinstant on left panel is
shown correctly.
Explanation
Component links on the left panel displayed successfully.
CYNVE1431E: Left-side component panel is not shown
correctly.
Explanation
There is a problem displaying the component panel on the self-diagnosis page.
CYNVE1560E: Failed to get JMX Data from Data Access Layer
Explanation
1. Unable to connect to the Data Access Layer. 2. Data Access Layer is unable to
connect to the Data Collector. 3. Data Collector is unable to get JMX data from the
JMX Engine
362
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
1. Ensure that the Data Access Layer is installed correctly as a resource adapter. 2.
Verify that the Data Access Layer log file is able to communicate with the Data
Collector. 3. Verify that the Data Collector log file is able to get JMX data from the
JMX Engine.
CYNVE1561E: Failed to get JMX categories from Data Access
Layer.
Explanation
1. Unable to connect to the Data Access Layer. 2. Data Access Layer is unable to
connect to the Data Collector. 3. Data Collector is unable to get category
information from the JMX Engine
Operator response
1. Ensure that the Data Access Layer is installed correctly as a resource adapter. 2.
Verify that the Data Access Layer log file is able to communicate with the Data
Collector. 3. Verify that the Data Collector log file is able to get JMX categories
from the JMX Engine.
CYNVE1562E: Error in getting JMX data.
Explanation
This is a general error message. Check the VE log files for more information.
Operator response
Check VE log files.
CYNVE1563E: Missing 'usejsp' attribute in VE display
configuration file
Explanation
The 'usejsp' attribute is not set in the VE display configuration file
Operator response
Check VE display configuration file under the subdirectories $AM_home/etc/
veconfig. For JMX Browser (System Resource), the subdirectory is jmxbrowser; for
JMX Resource tab under Problem Center, the subdirectory is problemcenter/
resource.
CYNVE1565E: Unable to get server group information from
database.
Explanation
Unable to get server group information from the database.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
363
Operator response
Check database connectivity and VE log files to see if there are any database
errors.
CYNVE1566E: Unable to get data collector information from
database.
Explanation
Unable to get data collector information from the database.
Operator response
Check database connectivity and VE log files to see if there are any database
errors.
CYNVE1568E: Failed to get JMX data from data collector.
Explanation
Failed to get JMX data from the data collector.
Operator response
1. VE might not be able to get the Command Agent from Kernel. Check the Kernel
status to see if both data collector's controller and probe have correctly joined the
Kernel. 2. VE might not be able to get JMX data from the Command Agent. 3.
Check the VE log files to see if there are any exceptions.
CYNVE1569E: Failed to get JMX Categories from data
collector.
Explanation
Failed to get JMX categories from the data collector.
Operator response
1. VE might not be able to get the Command Agent from the Kernel. Check the
Kernel status to see if both data collector's controller and probe correctly joined the
Kernel. 2. VE might not be able to get the JMX categories from the Command
Agent. 3. Check the VE log files to see if there are any exceptions.
CYNVE1570E: Failed to get JMX data.
Explanation
Failed to get JMX data.
Operator response
Check the VE log files to see if there are any exceptions.
364
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNVE1571E: Failed to get JMX data in calling method
JMXAcquireAttribute.getAttribute.
Explanation
Failed to get JMX data in the calling method JMXAcquireAttribute.getAttribute.
Operator response
Check the VE log files to see if there are any exceptions.
CYNVE1605E: Error retrieving all Traps definition. SQL
Exception: exception
Explanation
An SQL attempt to retrieve all Traps definition failed.
Operator response
Ensure that the database, default name (octigate), is up and running. If the
connection is good, verify that the 'TRAPDEFS' and 'TRAPACTIONS' tables exist.
CYNVE1606E: Error retrieving all Traps definition by UserID.
SQL Exception: exception
Explanation
An SQL attempt to retrieve all Traps definition by UserID failed.
Operator response
Ensure that the database, default name (octigate), is up and running. If the
connection is good, verify that the 'TRAPDEFS' and 'TRAPACTIONS' tables exist
and that the USERID request parameter has the correct value.
CYNVE1607E: Error retrieving a Trap definition by TRAPID.
SQL Exception: exception
Explanation
An SQL attempt to retrieve a Traps definition by TRAPID failed.
Operator response
Ensure that the database, default name (octigate), is up and running. If the
connection is good, verify that the 'TRAPDEFS' and 'TRAPACTIONS' tables exist
and that TRAPID request parameter has the correct value.
CYNVE1608E: Error inserting/updating a Trap Definition. SQL
Exception: exception
Explanation
An SQL attempt to insert/update a Trap definition failed.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
365
Operator response
Ensure that the database, default name (octigate), is up and running. If the
connection is good, verify that the 'TRAPDEFS' table exists.
CYNVE1609E: Error deleting a Trap definition. SQL Exception:
exception
Explanation
An SQL attempt to delete a Trap definition and the same Trap action by
TRAPDEFID failed.
Operator response
Ensure that the database, default name (octigate), is up and running. If the
connection is good, verify that the 'TRAPDEFS' and 'TRAPACTION' tables exist
and that TRAPDEFID has the correct value.
CYNVE1610E: Error retrieving the unfiltered Trap history list.
SQL Exception: exception
Explanation
An SQL attempt to retrieve the unfiltered Trap history list failed.
Operator response
Ensure that the database, default name (octigate), is up and running. If the
connection is good, verify that the 'TRAPDEFS', 'TRAP_HISTORY' and 'SERVERS'
tables exist.
CYNVE1611E: Error reading a properties file.
Explanation
Attempt to read the properties file, ve.properties, failed.
Operator response
Ensure that the properties file, ve.properties, in the Managing Server's etc directory
exists, and that variable, com.cyanea.octigate.database.ORACLE_8I, exists.
CYNVE1612E: Error retrieving the filtered Trap history list.
SQL Exception: exception
Explanation
An SQL attempt to retrieve the filtered Trap History list by TRAPID failed.
Operator response
Ensure that the database, default name (octigate), is up and running. Verify that
the 'TRAP_HISTORY' table exists and that the passing parameter TRAPID has
correct value.
366
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNVE1613E: Error retrieving number of filtered Trap History.
SQL Exception: exception
Explanation
SQL Error Retrieving number of filtered Trap History by SERVERID.
Operator response
Ensure that the database, default name (octigate), is up and running. If the
connection is good, verify that the 'TRAP_HISTORY' and 'TRAPDEFS' tables exist
and that the passing parameter SERVERID has the correct value.
CYNVE1614E: Error retrieving filtered Trap list. SQL
Exception: exception
Explanation
An SQL attempt to retrieve filtered Trap list by SERVERID and TRAPID failed.
Operator response
Ensure that the database, default name (octigate), is up and running. If the
connection is good, verify that the 'TRAP_HISTORY', 'SERVER' and 'TRAPDEFS'
tables exist and that the passing parameters SERVERID and TRAPID have the
correct values.
CYNVE1615E: Error retrieving filtered Trap list. SQL
Exception: exception
Explanation
An SQL attempt to retrieve filtered Trap list by GROUPID failed.
Operator response
Ensure that the database, default name (octigate), is up and running. If the
connection is good, verify that the 'TRAP_HISTORY', 'SERVER', 'MAP_GR_SE' and
'TRAPDEFS' tables exist and that the passing parameter GROUPID has the correct
value.
CYNVE1616E: Error retrieving filtered Trap list. SQL
Exception: exception
Explanation
An SQL attempt to retrieve filtered Trap list by GROUPID and TRAPID failed.
Operator response
Ensure that the database, default name (octigate), is up and running. If the
connection is good, verify that the 'TRAP_HISTORY', 'SERVER', 'MAP_GR_SE' and
'TRAPDEFS' tables exist and that the passing parameter GROUPID has the correct
value.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
367
CYNVE1617E: Error retrieving a Trap. SQL Exception:
exception
Explanation
An SQL attempt to retrieve a Trap History by ID (Trap History ID) failed.
Operator response
Ensure that the database, default name (octigate), is up and running. If the
connection is good, verify that the 'TRAP_HISTORY' table exists and that the
passing parameter ID has the correct value.
CYNVE1618E: Error deleting a Trap History. SQL Exception:
exception
Explanation
An SQL attempt to delete the Trap history by ID (Trap History ID) failed.
Operator response
Ensure that the database, default name (octigate), is up and running. If the
connection is good, verify that the 'TRAP_HISTORY' table exists and that the
passing parameter ID has the correct value.
CYNVE1619E: Error retrieving a Trap StackTrace. SQL
Exception: exception
Explanation
An SQL attempt to retrieve a Trap stack trace by TH_ID failed.
Operator response
Ensure that the database, default name (octigate), is up and running. If the
connection is good, verify that the 'TRAP_STACK_TRACE' and 'TEXTSTRING'
tables exist and that the passing parameter TH_ID has the correct value.
CYNVE1620E: Error retrieving thread dump. SQL Exception:
exception
Explanation
An SQL attempt to retrieve thread dump for Trap history by TH_ID failed.
Operator response
Ensure that the database, default name (octigate), is up and running. If the
connection is good, verify that the 'TRAP_THREAD_DUMP' table exists and that
the passing parameter TH_ID has the correct value.
368
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNVE1621E: Error retrieving Trap Action for DB2. SQL
Exception: exception
Explanation
An SQL attempt to retrieve Trap action by SERVERID and TRAPID for DB2 failed.
Operator response
Ensure that the database, default name (octigate), is up and running. If the
connection is good, verify that the 'TRAP_HISTORY', 'TRAPDEFS' and 'SERVERS'
tables exist and that the passing parameters SERVERID and TRAPID have the
correct values.
CYNVE1622E: Error retrieving Trap Action for Oracle. SQL
Exception: exception
Explanation
An SQL attempt to retrieve Trap action by SERVERID and TRAPID for Oracle
failed.
Operator response
Ensure that the database, default name (octigate), is up and running. If the
connection is good, verify that the 'TRAP_HISTORY', 'TRAPDEFS' and 'SERVERS'
tables exist and that the passing parameters SERVERID and TRAPID have the
correct values.
CYNVE1623E: Error retrieving Unfiltered Trap Action for DB2.
SQL Exception: exception
Explanation
An SQL attempt to retrieve unfiltered Trap history for DB2 failed.
Operator response
Ensure that the database, default name (octigate), is up and running. If the
connection is good, verify that the 'TRAP_HISTORY', 'TRAPDEFS' and 'SERVERS'
tables exist.
CYNVE1624E: Error retrieving Unfiltered Trap Action for
ORACLE. SQL Exception: exception
Explanation
An SQL attempt to retrieve unfiltered Trap history for ORACLE failed.
Operator response
Ensure that the database, default name (octigate), is up and running. If the
connection is good, verify that the 'TRAP_HISTORY', 'TRAPDEFS' and 'SERVERS'
tables exist.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
369
CYNVE1625E: Error retrieving filtered Trap Action for DB2.
SQL Exception: exception
Explanation
An SQL attempt to retrieve filtered Trap action by TRAPID for DB2 failed.
Operator response
Ensure that the database, default name (octigate), is up and running. If the
connection is good, verify that the 'TRAP_HISTORY', 'TRAPDEFS' and 'SERVERS'
tables exist and that the passing parameter TRAPID has the correct value.
CYNVE1626E: Error retrieving filtered Trap Action for
ORACLE. SQL Exception: exception
Explanation
An SQL attempt to retrieve filtered Trap action by TRAPID for ORACLE failed.
Operator response
Ensure that the database, default name (octigate), is up and running. If the
connection is good, verify that the 'TRAP_HISTORY', 'TRAPDEFS' and 'SERVERS'
tables exist and that the passing parameter TRAPID has the correct value.
CYNVE1627E: Error retrieving filtered Trap Action for DB2.
SQL Exception: exception
Explanation
An SQL attempt to retrieve filtered Trap action by SERVERID for DB2
Operator response
Ensure that the database, default name (octigate), is up and running. If the
connection is good, verify that the 'TRAP_HISTORY', 'TRAPDEFS' and 'SERVERS'
tables exist amd that the passing parameter TRAPID has the correct value.
CYNVE1628E: Error retrieving filtered Trap Action for
ORACLE. SQL Exception: exception
Explanation
An SQL attempt to retrieve filtered Trap action by SERVERID for ORACLE failed.
Operator response
Ensure that the database, default name (octigate), is up and running. If the
connection is good, verify that the 'TRAP_HISTORY', 'TRAPDEFS' and 'SERVERS'
tables exist and that the passing parameter TRAPID has the correct value.
370
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNVE1629E: Error retrieving Trap Names. SQL Exception:
exception
Explanation
An SQL attempt to retrieve Trap names failed.
Operator response
Ensure that the database, default name (octigate), is up and running. If the
connection is good, verify that the 'TRAP_HISTORY', 'TRAPDEFS' tables exist.
CYNVE1630E: Error retrieving filtered Trap History for DB2.
SQL Exception: exception
Explanation
An SQL attempt to retrieve filtered Trap Action by GROUPID for DB2 failed.
Operator response
Ensure that the database, default name (octigate), is up and running. Check that
the 'TRAP_HISTORY', 'TRAPDEFS', 'MAP_GR_SE' and 'SERVERS' tables exist and
that the passing parameter GROUPID has the correct value.
CYNVE1631E: Error retrieving filtered Trap History for
ORACLE. SQL Exception: exception
Explanation
An SQL attempt to retrieve filtered Trap Action by GROUPID for ORACLE failed.
Operator response
Ensure that the database, default name (octigate), is up and running. Check that
the 'TRAP_HISTORY', 'TRAPDEFS', 'MAP_GR_SE' and 'SERVERS' tables exist and
that the passing parameter GROUPID has the correct value.
CYNVE1632E: Error retrieving filtered Trap History for DB2.
SQL Exception: exception
Explanation
An SQL attempt to retrieve filtered Trap Action by GROUPID and TRAPID for
DB2 failed.
Operator response
Ensure that the database, default name (octigate), is up and running. Check that
the 'TRAP_HISTORY', 'TRAPDEFS', 'MAP_GR_SE' and 'SERVERS' tables exist and
that the passing parameters GROUPID and TRAPID have the correct values.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
371
CYNVE1633E: Error retrieving filtered Trap History for
ORACLE. SQL Exception: exception
Explanation
An SQL attempt to retrieve filtered Trap Action by GROUPID and TRAPID for
ORACLE failed.
Operator response
Ensure that the database, default name (octigate), is up and running. Check that
the 'TRAP_HISTORY', 'TRAPDEFS', 'MAP_GR_SE' and 'SERVERS' tables exist and
that the passing parameters GROUPID and TRAPID have correct values.
CYNVE1634E: Error retrieving all Traps definition by UserId
for a server. SQL Exception: exception
Explanation
An SQL attempt to retrieve all Traps definition by UserID for a server failed.
Operator response
Ensure that the database, default name (octigate), is up and running. If the
connection is good, verify that the 'TRAPDEFS' and 'TRAPACTIONS' tables exist
and that the value of the request parameter USERID has the correct value.
CYNVE1800E: ProblemLogAction Exception
Explanation
Ensure that the Tivoli Enterprise Monitoring Agent is installed correctly and
running.
Operator response
CYNVE1801E: JNDI_NAME is not valid: problem
Explanation
The JNDI_NAME is not valid.
Operator response
Attempt to access the WebSphere Application Server admin console to check the
JNDI_NAME.
CYNVE1802E: DAL Resource Adapter Connection Error
Explanation
An error occurred when communicating with the DAL Resource Adapter.
Operator response
Attempt to access the WebSphere Application Server admin console to check the
DAL Resource Adapter.
372
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNVE1830E: File does not exist when attempting to get the
application configuration
Explanation
An error occurred when communicating with EJB when attempting to get the
application configuration.
Operator response
Refresh the page.
CYNVE1831W: No application configuration was found in
server configuration
Explanation
An error occurred when communicating with EJB when attempting to get the
application configuration.
Operator response
Refresh the page.
CYNVE1832W: Getting commandagent error
Explanation
An error occurred when attempting to get the command agent.
Operator response
Ensure that the kernel is running.
CYNVE1833E: The Configuration File does not support
selected DC
Explanation
The Data Collector maybe a CICS Data Collector,IMS Data Collector or WBI Data
Collector.
Operator response
Refresh the page.
CYNVE1834E: The Configuration Application does not support
selected DC
Explanation
The Data Collector maybe a CICS Data Collector,IMS Data Collector or WBI Data
Collector.
Operator response
Refresh the page.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
373
CYNVE1940E: Invalid method profile duration: duration
Explanation
Enter a valid method profile duration between 1-999.
CYNVE1950E: An error occurred while attempting to launch
into TEP.
Explanation
An error occurred while attempting to launch into Tivoli Enterprise Portal. Make
sure Tivoli Enterprise Portal has been configured correctly.
Operator response
Check ve.properties to see if {tep.hostname}, {tep.port}, {tep.baseurl} have been set
correctly. Check the table DC_IDENTITY_INFO to see if there is a mapping
between probeId and TEMANodeName of the server.
CYNVE1951E: Unable to launch into TEP because TEMA does
not support ITCAM J2SE DCs.
Explanation
Tivoli Enterprise Monitoring Agent does not support ITCAM J2SE DCs and thus
VE can not find a mapping between the ITCAM Data Collector and the Tivoli
Enterprise Monitoring Agent.
Operator response
CYNVE2000E: Unable to save the Server Statistics
configuration.
Explanation
The configuration on the Server Statistics Overview page was unable to be saved.
Operator response
Check the database to ensure that it is up and running, and verify that the
'properties' table exists.
CYNVE2000I: Server statistics overview configuration saved
successfully.
Explanation
The configuration for the server statistics overview page was saved successfully.
CYNVE2001E: The default configuration is unavailable.
Explanation
The default configuration on the Server Statistics Overview page is unavailable.
374
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
Check the database to ensure that it is up and running, and verify that the
'properties' table exists.
CYNVE2002E: The Server Statistics Overview page is
unavailable.
Explanation
The Server Statistics Overview page cannot display.
Operator response
Check the self-diagnosis page to ensure that the Kernel is up and running.
CYNVE3000E: The server displayNameis currently unavailable.
Explanation
The selected server is unavailable at this time.
Operator response
Check the self-diagnosis page to verify the availability of the server.
CYNVE3000I: SMF history is not available for the Data
Collector whose component ID is: componentID.
Explanation
SMF history is not available on the System Resources pages.
CYNVE3001E: The Publish Server is unavailable.
Explanation
The Publish Server is needed to retrieve PMI information to display in the System
Resources sections.
Operator response
Check the self-diagnosis page to verify that one or more Publish Servers are up
and running.
CYNVE3001I: Byte activity data is not available for the Data
Collector whose component ID is: componentID.
Explanation
Byte activity data is not available on this server on the System Resources pages.
CYNVE3002E: Region database pool data for server
serverDisplayNameis unavailable.
Explanation
The data for region database pools for this server is unavailable.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
375
Operator response
Verify that the jars in MS_home/lib3.2 (Managing Server) match the jars in
DC_home/lib3.2 (Data Collector).
CYNVE3002I: Transaction activity data is not available for the
Data Collector whose component ID is: componentID.
Explanation
Transaction activity data is not available on the System Resources pages. .
CYNVE3003E: List of resource names not found.
Explanation
The list of resource names, used to retrieve System Resource data, is not found.
Operator response
Verify that the file, MS_home/etc/msg.properties, exists and is in the correct path.
CYNVE3003I: EJB activity data is not available for the Data
Collector whose component ID is: componentID.
Explanation
EJB activity data is not available on the System Resources pages.
CYNVE3004E: The server displayNameis unavailable.
Explanation
The selected server is unavailable.
Operator response
Check the self-diagnosis page to verify the availability of the server.
CYNVE3004I: Servlet activity data is not available for the Data
Collector whose component ID is: componentID.
Explanation
Servlet activity data is not available on the System Resources pages.
CYNVE3005E: The system is currently unavailable.
Explanation
The system is unavailable.
Operator response
Check the self-diagnosis page to verify the availability of the server.
376
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNVE3005I: Miscellaneous data is not available.
Explanation
Miscellaneous data is not available on the System Resources pages.
CYNVE3006E: Data for the server displayName is unavailable.
Explanation
Data for the selected server is unavailable.
Operator response
Verify that the jars in MS_home/lib3.2 (Managing Server) match the jars in
DC_home/lib3.2 (Data Collector).
CYNVE3006I: EJB coverage information is not available.
Explanation
EJB coverage information is not available on the System Resources pages.
CYNVE3007E: Select a server.
Explanation
No server was selected on the System Resources page.
Operator response
Select a server from the drop-down list to view System Resource data for a
particular server.
CYNVE3007I: Servlet coverage information is not available.
Explanation
Servlet coverage information is not available on the System Resources pages.
CYNVE3008E: This feature is not supported for the selected
server with this application server platform: serverPlatform.
Explanation
No System Resources information is available for this server.
Operator response
Select a different server to view System Resources information.
CYNVE3008I: Unable to populate SQL for the SMF Data
Collector whose probe ID is: probeID.
Explanation
SQL cannot be populated for the System Resources pages because the Publish
Server is down or the data is unavailable for this Data Collector.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
377
CYNVE3009E: Failed to find server.
Explanation
The EJB used to get the server failed.
Operator response
Ensure that the database is up and running.
CYNVE3009I: System Resources data is not available.
Explanation
Data is not available for this SMF Data Collector on the System Resources pages.
CYNVE3010E: EJB used to get server or server group failed.
Explanation
The EJB used to get the server or server group failed.
Operator response
Ensure that the database is up and running.
CYNVE3010I: SMF history is not available for the Data
Collector whose probe ID is: probeID.
Explanation
SMF history is not available for this Data Collector on the System Resources pages.
CYNVE3011E: Select a group.
Explanation
No group was selected on the System Resources Comparison page.
Operator response
Select a group to compare System Resources.
CYNVE3011I: The number of total sessions is not available for
the Data Collector whose probe ID is: probeID.
Explanation
The number of total sessions is not available for this Data Collector on the System
Resources pages.
CYNVE3012E: Select a resource.
Explanation
No resource was selected on the System Resource Comparison page.
378
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
Select a resource to compare System Resources.
CYNVE3012I: Unable to contact server manager bean.
Explanation
No server manager EJB was found. Ensure that the database is up and running.
CYNVE3013E: Unable to display charts on System Resource
pages.
Explanation
The graphics environment is not set up to display charts.
Operator response
Verify that X11 is running correctly to view graphs.
CYNVE3013I: System Resource data is unavailable for the
Data Collector whose component ID is: componentID.
Explanation
Verify that the jars in MS_home/lib3.2 (Managing Server) match the jars in
DC_home/lib3.2 (Data Collector).
CYNVE3014E: Unable to get CTG data, as a result of the
following exception: exception.
Explanation
The SQL attempt to access the CTG data failed.
Operator response
Ensure that the database is up and running, and that the ctg_sr_overview table
exists.
CYNVE3014I: System Resource data is unavailable for this
Data Collector.
Explanation
Verify that the jars in MS_home/lib3.2 (Managing Server) match the jars in
DC_home/lib3.2 (Data Collector).
CYNVE3015E: Unable to access MQI data, as a result of the
following exception: exception.
Explanation
The SQL attempt to access the MQI data failed.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
379
Operator response
Ensure that the database is up and running, and that the
mqi_queue3004_sr_overview table exists.
CYNVE3015I: CPU Utilization data is unavailable for the Data
Collector whose component ID is: componentID.
Explanation
Verify that the PMI settings for this server are correct. Also, verify that the jars in
MS_home/lib3.2 (Managing Server) match the jars in DC_home/lib3.2 (Data
Collector).
CYNVE3016I: Memory data is unavailable for the Data
Collector whose component ID is: componentID.
Explanation
Verify that the PMI settings for this server are correct. Also, verify that the jars in
MS_home/lib3.2 (Managing Server) match the jars in DC_home/lib3.2 (Data
Collector).
CYNVE3017I: Transaction data is unavailable for the Data
Collector whose component ID is:componentID.
Explanation
Verify that the PMI settings for this server are correct. Also, verify that the jars in
MS_home/lib3.2 (Managing Server) match the jars in DC_home/lib3.2 (Data
Collector).
CYNVE3018I: Database connection pool data is unavailable for
the Data Collector whose component ID is:componentID.
Explanation
Verify that the PMI settings for this server are correct. Also, verify that the jars in
MS_home/lib3.2 (Managing Server) match the jars in DC_home/lib3.2 (Data
Collector).
CYNVE3019I: EJB coverage data is unavailable for the Data
Collector whose component ID is: componentID.
Explanation
Verify that the PMI settings for this server are correct. Also, verify that the jars in
MS_home/lib3.2 (Managing Server) match the jars in DC_home/lib3.2 (Data
Collector).
380
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNVE3020I: Servlet coverage data is unavailable for the Data
Collector whose component ID is: componentID.
Explanation
Verify that the PMI settings for this server are correct. Also, verify that the jars in
MS_home/lib3.2 (Managing Server) match the jars in DC_home/lib3.2 (Data
Collector).
CYNVE3021I: EJB activity data is unavailable for the Data
Collector whose component ID is: componentID.
Explanation
Verify that the PMI settings for this server are correct. Also, verify that the jars in
MS_home/lib3.2 (Managing Server) match the jars in DC_home/lib3.2 (Data
Collector).
CYNVE3022I: Servlet activity data is unavailable for the Data
Collector whose component ID is: componentID.
Explanation
Verify that the PMI settings for this server are correct. Also, verify that the jars in
MS_home/lib3.2 (Managing Server) match the jars in DC_home/lib3.2 (Data
Collector).
CYNVE3023I: Thread pool data is unavailable for the Data
Collector whose component ID is: componentID.
Explanation
Verify that the PMI settings for this server are correct. Also, verify that the jars in
MS_home/lib3.2 (Managing Server) match the jars in DC_home/lib3.2 (Data
Collector).
CYNVE3024I: System resource data is unavailable for the Data
Collector whose probe ID is: probeID.
Explanation
Verify that the jars in MS_home/lib3.2 (Managing Server) match the jars in
DC_home/lib3.2 (Data Collector).
CYNVE3025I: Unable to compare double values, s1 and s2, for
sorting on System Resource pages.
Explanation
The specified values are unable to be parsed as doubles.
CYNVE3026I: Unable to compare long values, s1 and s2, for
sorting on system resource pages.
Explanation
The specified values are unable to be parsed as longs.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
381
CYNVE3027I: Unable to compare Date values, s1 and s2, for
sorting on system resource pages.
Explanation
The specified values are unable to be parsed as dates.
CYNVE3028I: Can not be parsed by decimal format.
Explanation
Strings used to sort on system resource pages cannot be parsed.
CYNVE3029I: Cannot be parsed as integers.
Explanation
Strings used to sort on system resource pages cannot be parsed.
CYNVE3030I: Cannot be parsed by longs.
Explanation
Strings used to sort on system resource pages cannot be parsed.
CYNVE3031I: Cannot be parsed as dates.
Explanation
Strings used to sort on system resource pages cannot be parsed.
CYNVE3032I: Database connection pool data is unavailable for
the Data Collector whose component ID is: componentID.
Explanation
Verify that the PMI settings for this server are correct. Also, verify that the jars in
MS_home/lib3.2 (Managing Server) match the jars in DC_home/lib3.2 (Data
Collector).
CYNVE4000E: Default page, homePage, could not be saved.
Explanation
The page selected to be the landing page was not saved.
Operator response
Ensure that the database is up and running, and that the database administrator
can connect to the octigate schema.
CYNVE4000I: Default page has been successfully saved.
Explanation
The Default landing page was successfully saved to the database.
382
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNVE4001E: Unable to display the Enterprise Overview
page.
Explanation
The Enterprise Overview page is unable to display correctly.
Operator response
Ensure that the database is up and running, and that the database administrator
can connect to the octigate schema.
CYNVE4002E: Unable to display history on the Enterprise
Overview page.
Explanation
The history on the charts on the Enterprise Overview page cannot display.
Operator response
Ensure that the database is up and running, and that the database administrator
can connect to the octigate schema.
CYNVE4003E: Unable to display charts on the Enterprise
Overview page.
Explanation
The graphical environment is not set up correctly, so charts on the Enterprise
Overview page cannot display.
Operator response
Ensure that the virtual frame buffer is up and running.
CYNVE4004E: Unable to display the Enterprise Overview
page.
Explanation
Information about the server groups was not captured for display on the
Enterprise Overview page.
Operator response
Ensure that the database is up and running, and that the database administrator
can connect to the octigate schema.
CYNVE4005E: Unable to display charts on the Group
Overview page.
Explanation
The graphical environment is not set up correctly, so charts on the Group
Overview page cannot display.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
383
Operator response
Ensure that the virtual frame buffer is up and running.
CYNVE4007E: Unable to display the Group Overview page.
Explanation
The Group Overview page is not displayed as a result of incorrect pagination.
Operator response
Ensure that the value entered for pagination is correct.
CYNVE5000E: Failed to capture data for Server Statistics
Overview page.
Explanation
Data for the Server Statistics Overview page is not available.
Operator response
Use the Self-diagnosis page to ensure that the kernel is up and running.
CYNVE5001E: Unable to access the list of available Data
Collectors on the Server Statistics Overview page.
Explanation
Information for the list of available Data Collectors is not being captured.
Operator response
Use the Self-diagnosis page to ensure that the kernel is up and running.
CYNVE5002E: Unable to access the list of servers to display
the Server Statistics Overview page, as a result of the
following exception: exception.
Explanation
Information for the list of servers is not being captured.
Operator response
Use the Self-diagnosis page to ensure that the kernel is up and running.
CYNVE5003E: Unable to get the server group manager EJB.
Explanation
The EJB failed to access the server group manager bean, which is needed for
information on the Server Statistics Overview page.
384
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
Ensure that the database is up and running and that the GROUPS table exists.
CYNVE5004E: Unable to access throughput and response
time information for the group, groupName. The following
exception is shown: exception
Explanation
Throughput and response time data is unavailable for retrieval.
Operator response
Ensure that the database is up and running and that the VOLUMESTATS table
exists with data for the group.
CYNVE5005E: Unable to access baseline throughput and
response time information for the group, groupName. The
following exception is shown: exception
Explanation
Throughput and response time baseline data is unavailable for retrieval.
Operator response
Ensure that the database is up and running and that the VOLUMESTATS table
exists with data for the group.
CYNVE5006E: Unable to access history for any server group,
as a result of the following exception: exception
Explanation
Historical data for this group is unavailable for retrieval.
Operator response
Ensure that the database is up and running and that the VOLUMESTATS table
exists with data for the group.
CYNVE5007E: Unable to access the list of disabled Data
Collectors for display on the Server Statistics Overview page,
as a result of the following exception: exception.
Explanation
The list of disabled Data Collectors is not being retrieved.
Operator response
Use the Self-diagnosis page to ensure that the kernel is up and running.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
385
CYNVE5008E: Unable to get server manager EJB.
Explanation
The EJB failed to get the server manager bean, which is needed for information on
the Server Statistics Overview page.
Operator response
Ensure that the database is up and running and that the SERVERS table exists.
CYNVE5009E: Unable to retrieve data for the display of recent
activity, as a result of the following exception: exception
Explanation
The SQL used to retrieve recent activity data was unable to be executed.
Operator response
Ensure that the database is up and running and that the MEMORY_DATA exists
and has the following columns: JVM_CPU, JVM_HEAP_SIZE, REQ_COUNT,
AVG_RES_TIME, SESSION_COUNT, and SYS_PAGE_RATE.
Also, ensure that the GC_DATA table exists and has the following columns:
GC_COUNT, TOTAL_GC_TIME, and AVG_HEAP_SIZE
CYNWS Messages: Web Services
The following messages relate to the Web services. All such messages have IDs in
the range CYNWS0001E to CYNWS0003W.
CYNWS0001E: An authentication failure has occurred for the
current user.
Explanation
An invalid user name or password has been specified.
Operator response
Check to make sure that the user name and password are correct.
CYNWS0002W: No trap is defined for the current user.
Explanation
No trap is defined for the current user in the selected date range.
Operator response
Make sure to specify the right user and date range.
CYNWS0003W: There is no aggregate data for traps.
Explanation
Aggregated statistics are not provided on trap data.
386
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
Make the selection to import instance data instead.
CYNW Messages: Polling Agent
The following messages relate to the Polling Agent. All such messages have IDs in
the range CYNW0001E to CYNW0008I.
CYNW0001E: An exception occurred while communicating
with the Archive Agent.
Explanation
See message.
Operator response
Check the trace logs to determine the cause of the error.
CYNW0002E: A error occurred while binding to the RMI.
Explanation
When the Polling Agent starts, it binds with the RMI. An error occurred during
this stage.
Operator response
Check the trace logs to determine the cause of the error.
CYNW0003E: An error occurred while joining the Kernel.
Explanation
When the Polling Agent starts, it joins the Kernel. An error occurred during this
stage.
Operator response
Check the trace logs to determine the cause of the error.
CYNW0004I: The Polling Agent started polling and storing the
information in the database for server server at port port. The
server's ID is serverId.
Explanation
The Polling Agent has started monitoring the specified Web server.
CYNW0005E: An error occurred while the Polling Agent was
unbinding from the RMI.
Explanation
The Polling Agent uses the RMI for communication with the rest of the Managing
Server components.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
387
Operator response
Check the trace logs to determine the cause of the error.
CYNW0006E: An exception occurred while the Polling Agent
was retrieving LookupAgent from the Kernel.
Explanation
The Polling Agent retrieves LookupAgent from the Kernel to communicate with
different components. An error occurred during this stage.
Operator response
Check the trace logs to determine the cause of the error.
CYNW0007I: The Web server with IP address ip at port portwas
added to a monitor. The server's ID is serverId.
Explanation
See message.
CYNW0008I: The Polling Agent is removing Web server with IP
address ip at port port from monitoring. The server's ID is
serverId.
Explanation
The specified Web server was removed from configuration.
CYNX Messages: Installation
The following messages occur during installation. All such messages have IDs in
the range CYNX0001E to CYNX0013E.
CYNX0001E: There were usage errors, where a number of
arguments were incorrect for: java UserInputsFilePath,
ConfigurationTemplatesPath, and DestinationPath.
Explanation
UserInputsFilePath is the user inputs properties file with a fully qualified path.
ConfigurationTemplatesPath is the specify directory. DestinationPath is where the
concrete configuration files are to be copied.
Operator response
Pass the correct number of arguments.
388
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNX0002E: Configuration template template was not found.
The concrete configuration XML file could not be created.
Explanation
The concrete configuration XML file cannot be generated due to the missing
template file in a specific directory.
Operator response
Provide the correct template. If the specific type is not supported, you can fall back
to a lower application server version.
CYNX0003E: A configuration template cannot be found for the
following application server versions: version. The concrete
configuration XML file could not be created.
Explanation
The concrete configuration XML file cannot be generated due to a missing template
file in a specific directory.
Operator response
Provide the correct template. If the specific type is not supported, you can fall back
to a lower application server version.
CYNX0004E: The concrete configuration XML file could not be
generated due to missing values in the dcInputs.txt file.
Explanation
One more more values such as APPSERVER or APPSERVER_VERSION are missing
from the dcInputs.txt file.
Operator response
Correct the dcInputs.txt value. Provide all the necessary information and rerun the
installer.
CYNX0005I: The concrete configuration file file was generated
successfully.
Explanation
The Generate Config module generated the concrete configuration XML file which
will be used to apply configuration to the specific application server.
CYNX0006E: The value for the variable variable was not found
in the userInputs file. This variable was not replaced in file
fileName.
Explanation
Some values are missing in the userInputs file. Substitution for these variables
could not be done successfully.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
389
Operator response
Specify the correct values for all the necessary variables in the userInputs file. If
you do not, then manually edit the destination file and specify the values for these
variables.
CYNX0007E: File fileName1 cannot be modified successfully
and copied to the file fileName2.
Explanation
One or more variables could not be substituted successfully. Their values could not
be found in a property file.
Operator response
Specify the correct values for all the necessary variables in the userInputs file. If
you do not, then manually edit the destination file and specify the values for these
variables.
CYNX0008E: The system could not load the property file
fileName successfully.
Explanation
The system failed to load or read the property file due to a missing file or wrong
permissions.
Operator response
The property file might not exist or might not be accessible. Make sure that the file
exists and it has read permission.
CYNX0009E: One or more -Xrun JVM arguments were found
for the server server. Configuration is skipped for server
server.
Explanation
The -Xrun argument is found in the server's JVM arguments. The Data Collector
cannot be installed on already existing JVM profiles.
Operator response
Disable all the other JVM profiles and rerun the installer.
CYNX0010E: The system failed to get the backup of the
current application server configuration.
Explanation
See message.
390
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
Use the application server backup utility to back up the configuration manually
before running the installer.
CYNX0011E: The system failed to set variable.
Explanation
One or more errors occurred while applying the configuration.
Operator response
Refer to the installation guide and apply the configuration manually.
CYNX0012E: The system failed to save and commit the newly
applied configuration.
Explanation
See message.
Operator response
Refer to the installation guide and apply the configuration manually.
CYNX0013E: The system failed to create the post-installation
instruction file for the WebLogic unmanaged application
server.
Explanation
See message.
Operator response
Refer to the installation guide and apply the configuration manually.
CYNDA Messages: Data Access
The following messages occur during installation. All such messages have IDs in
the range CYNDA001E to CYNDA403I.
CYNDA001E: An Exception occurred while initializing the Data
Access Layer.
Explanation
DAL initializes by reading the configuration files for the various commands that
DAL supports. An exception occurred while processing the command files.
Operator response
Check the Exception stack trace for a detail error.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
391
CYNDA002E: Command Configuration number has the wrong
number of Commands Elements. It should contain only one
Commands Element.
Explanation
Various Commands are configured in the Command Configuration file. It must
contain only one Commands Element that has various Command Elements.
Operator response
Verify that the configuration file is correct. Ensure that it has only one Commands
Element.
CYNDA003E: Exception while creating the Command
cmdName
Explanation
An exception occurred while reading the command configuration and initializing
the Command.
Operator response
Check the exception for more details.
CYNDA004E: Exception while processing the Command
Configuration file cmdName
Explanation
An exception occurred while processing the Command Configuration file. This file
is used to initialize DAL and various Commands.
Operator response
There might be multiple reasons for the exception. The Command configuration
file might not exist or the XML content in the file might not be valid.
CYNDA005E: Command name is not specified for the
command cmdName
Explanation
Every Command defined for DAL must have a name attribute specified. Specify a
name for the specified command.
Operator response
Check the configuration for the specified command and include a name attribute.
392
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNDA006E: Class for the Command is not specified for the
command cmdName
Explanation
Every Command defined for DAL must have a class attribute specified. Specify a
class for the command.
Operator response
Check the configuration for the specified command and include a class attribute.
CYNDA007E: No queries found corresponding to the input
category category
Explanation
Queries are defined in DAL Command configuration files. When any input invokes
DAL using a category, DAL retrieves all the queries corresponding to that category.
This message is issued when no queries are defined using this category.
Operator response
Ensure that there are queries defined for this category.
CYNDA008E: No query name or category name is passed in
the input. At least one category or query should be present in
input.
Explanation
DAL is invoked with a query name or category name. This message is issued
when no query or category name is passed in the input.
Operator response
Ensure that at least one category or query name is passed in the input.
CYNDA009E: No command is associated with the query
queryType
Explanation
This message indicates that no command is configured for the specified query type
in the DAL Command configuration files.
Operator response
Ensure that the query type passed and that a Command can support this query
type.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
393
CYNDA200W: The Command Configuration File fileName does
not have any Commands to configure.
Explanation
The Command Configuration File contains the list of Commands for DAL to
configure. This Message indicates that the Configuration file does not have any
Commands to configure.
Operator response
Ensure that there is at least one Command for DAL to configure.
CYNDA400I: DAL is processing the commands configured
from the file fileName in the directory fileDir
Explanation
This message identifies the configuration file used by DAL to process various
commands.
Operator response
CYNDA401I: Initialized the command with name cmdName and
class name className
Explanation
This message indicates that the specified command was created and initialized.
Operator response
CYNDA402I: Registering a query queryType of category
category with the command cmdName
Explanation
This message identifies the query type that is being registered with the command
and category.
Operator response
CYNDA403I: The command cmdName is registered
Explanation
This message indicates that the specified command was registered with DAL.
Operator response
KYN Messages: Tivoli Enterprise Monitoring Agent
The Tivoli Enterprise Monitoring Agent produces errors messages with IDs in the
range KYNA0000 to KYNA0999; these are described below and in the following
pages.
394
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
KYNA0001I: ITCAM for Application Diagnostics monitoring
agent start-up complete.
Explanation
The ITCAM for Application Diagnostics Tivoli Enterprise Monitoring Agent
successfully completed initialization.
KYNA0002E: ITCAM for Application Diagnostics monitoring
agent initialization failed: errorMessage.
Explanation
The ITCAM for Application Diagnostics Tivoli Enterprise Monitoring Agent
initialization failed.
Operator response
Collect the agent log and contact IBM support.
KYNA0003I: The Agent configuration file file loaded
successfully.
Explanation
The ITCAM for Application Diagnostics Tivoli Enterprise Monitoring Agent
successfully loaded the configuration file specified in the message.
KYNA0004E: Agent configuration file file was not found.
Explanation
The ITCAM for Application Diagnostics monitoring configuration file specified in
the message was not found, the default configuration settings will be used.
Operator response
Reconfigure the ITCAM for Application Diagnostics Tivoli Enterprise Monitoring
Agent to restore the configuration file, or collect the agent log and contact IBM
support.
KYNA0005E: Agent configuration file file loading error:
errorMessage.
Explanation
The ITCAM for Application Diagnostics monitoring configuration file specified in
the message could not be loaded so the default configuration settings will be used.
Operator response
Delete the corrupted configuration file manually and reconfigure the ITCAM for
Application Diagnostics Tivoli Enterprise Monitoring Agent to restore it, or collect
the agent log and contact IBM support.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
395
KYNA0006I: The Agent context file file loaded successfully.
Explanation
The ITCAM for Application Diagnostics Tivoli Enterprise Monitoring Agent
successfully loaded the context file specified in the message.
KYNA0007W: The Agent context file file was not found.
Explanation
The ITCAM for Application Diagnostics monitoring context file specified in the
message was not found and will be recreated.
KYNA0008W: Agent context file file loading error:
errorMessage.
Explanation
The ITCAM for Application Diagnostics monitoring context file specified in the
message could not be loaded, the corrupted file has been deleted and will be
recreated.
KYNA0009I: Listening for incoming data collector connections
on port port.
Explanation
The ITCAM for Application Diagnostics Tivoli Enterprise Monitoring Agent
successfully completed socket interface initialization and is ready to accept
incoming data collector connections.
KYNA0010I: Application server discovered: serverInfo.
Explanation
The ITCAM for Application Diagnostics Tivoli Enterprise Monitoring Agent
accepted the new application server connection and successfully completed
handshaking. The new application server has been registered in agent context and
is now available for on-line monitoring.
KYNA0011I: Application server connected: serverId.
Explanation
The ITCAM for Application Diagnostics Tivoli Enterprise Monitoring Agent
accepted the registered application server connection and successfully completed
handshaking. The application server is now available for on-line monitoring.
KYNA0012I: Application server disconnected: serverId.
Explanation
The ITCAM for Application Diagnostics Tivoli Enterprise Monitoring Agent
detected that the application server is disconnected. The application server is no
longer available for on-line monitoring, but historical and log scrapping data
monitoring functions are available.
396
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
KYNA0013E: The Application server connection connectionInfo
failed: errorMessage
Explanation
The ITCAM for Application Diagnostics Tivoli Enterprise Monitoring Agent
accepted the incoming data collector connection but handshaking failed with
errors, the application server is not available for monitoring.
Operator response
Collect agent and data collector logs and contact IBM support.
KYNA0014I: Resource data monitoring started for application
server serverId resourceMethod.
Explanation
The ITCAM for Application Diagnostics Tivoli Enterprise Monitoring Agent started
resource data monitoring for the specified application server.
KYNA0015I: Resource data monitoring stopped for the
application server serverId.
Explanation
The ITCAM for Application Diagnostics Tivoli Enterprise Monitoring Agent
stopped resource data monitoring for the specified application server.
KYNA0016I: Request data monitoring started for the
application server serverId requestMethod.
Explanation
The ITCAM for Application Diagnostics monitoring started request data
monitoring for the specified application server.
KYNA0017I: Request data monitoring stopped for the
application server serverId.
Explanation
The ITCAM for Application Diagnostics Tivoli Enterprise Monitoring Agent
stopped request data monitoring for the specified application server.
KYNA0018I: Verbose GC output monitoring started for the
application server serverId with interval gcInterval.
Explanation
The ITCAM for Application Diagnostics Tivoli Enterprise Monitoring Agent started
verbose GC output monitoring for the specified application server.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
397
KYNA0019I: Verbose GC output monitoring stopped for the
application server serverId.
Explanation
The ITCAM for Application Diagnostics Tivoli Enterprise Monitoring Agent
stopped verbose GC output monitoring for the specified application server.
KYNA0020I: Application server log scrapping started for the
application server serverId alsInfo.
Explanation
The ITCAM for Application Diagnostics Tivoli Enterprise Monitoring Agent started
application server log scrapping for the specified application server.
KYNA0021I: Application server log scrapping stopped for the
application server serverId.
Explanation
The ITCAM for Application Diagnostics Tivoli Enterprise Monitoring Agent
stopped application server log scrapping for the specified application server.
KYNA0022E: Application server log scrapping stopped for the
application server serverId with error: errorMsg.
Explanation
The ITCAM for Application Diagnostics Tivoli Enterprise Monitoring Agent
stopped application server log scrapping for the specified application server
because errors were detected.
Operator response
Collect the agent and data collector logs and contact IBM support.
KYNA0023I: Take action tactId completed successfully for
application server serverId.
Explanation
The ITCAM for Application Diagnostics Tivoli Enterprise Monitoring Agent
successfully completed take action for the specified application server.
KYNA0024E: Take action tactId failed for the application server
serverId: tactReason.
Explanation
The ITCAM for Application Diagnostics Tivoli Enterprise Monitoring Agent failed
to take action for the specified application server.
Operator response
Collect the agent and data collector logs and contact IBM support.
398
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
KYNA0025I: Take action tactId processing started for the
application server serverId.
Explanation
The ITCAM for Application Diagnostics Tivoli Enterprise Monitoring Agent started
background take action processing for the specified application server.
KYNA0026E: Take sample table failed for application server
serverId: errorMsg.
Explanation
The ITCAM for Application Diagnostics Tivoli Enterprise Monitoring Agent failed
to collect a sample for the specified application server.
Operator response
Collect the agent and data collector logs and contact IBM support.
KYND Messages: ITCAM for Application Diagnostics Secondary Data
Collector
The following messages relate to the ITCAM for Application Diagnostics's
secondary data collector (which accumulates WebSphere performance data and
passes it to the ITCAM for Application Diagnostics Tivoli Enterprise Monitoring
Agent for processing). All such messages have IDs in the range KYND0000 to
KYND0999.
KYND0001E: AgentConnection class initializer not able to load
native library: Library Name
Explanation
The data collector was unable to load the specified native library. The data
collector cannot continue.
Operator response
Ensure that the specified native library is installed in the proper directory.
KYND0002W: WorkLoad requests could not be measured by
Request Analysis
Explanation
Requests were completing faster than the request analysis component could
measure. Consequently, some requests were not measured. The number of requests
not measured is displayed.
Operator response
None. This error usually occurs only in very busy environments.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
399
KYND0003E: Unable to write to MVS console - Console Name
Explanation
Because of the specified Java exception, the data collector was unable to write a
message to the system console.
Operator response
Investigate the Java exception. If necessary, contact IBM support.
KYND0004E: Unable to check native library build level
because native library not available
Explanation
The data collector was unable to verify the compatibility of the native library
because the library was not locatable.
Operator response
Examine the installation log for errors during the installation of the data collector.
KYND0005E: Incompatibility detected between Java library
Java Library and Native Library Native Library. Java library build
level is Java Library Level Native library build level is Native
Library Level
Explanation
During initialization, the data collector found that the build level of its Java JAR
file is incompatible with the build level of its native library module. The data
collector cannot continue.
Operator response
Examine the installation log for errors during the installation of the data collector.
If maintenance was recently applied, ensure that all steps in the configuration
process were completed successfully.
KYND0006E: Incompatibility detected between Native library
Native Library and Java Library Java Library. Native library build
level is Native Library Level Java library build level is Java
Library Level
Explanation
During initialization, the data collector found that the build level of its native
library module is incompatible with the build level of its Java JAR jar file. The data
collector cannot continue.
Operator response
Examine the installation log for errors during the installation of the data collector.
If maintenance was recently applied, ensure that all steps in the configuration
process were completed successfully.
400
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
KYND0007E: Error Error caught attempting to verify Native
library compatibility
Explanation
An exception occurred when the data collector was attempting to verify
compatibility with the native library. The exact error is given by exception.
Operator response
Verify the installation log for errors during the installation of the data collector. If
maintenance was recently applied, ensure that all steps in the configuration process
were completed successfully.
KYND0008E: Unable to obtain current working directory Working Directory
Explanation
A Java exception was caught trying to determine the name of the current working
directory.
Operator response
Contact IBM support.
KYND0009W: MessageMessages could not be sent to the
monitoring agent
Explanation
Messages were being generated faster than the data collector could handle them.
Consequently, some of the messages were not sent to the monitoring agent and
were dropped.
Operator response
Make sure the data collector has successfully connected to the monitoring agent.
KYND0010I: Data collector transport handler thread ended
Explanation
This message is normal if the application server is shutting down. It indicates that
a sample collection and communication thread belonging to the data collector is
ending as a result of the application server shutdown.
KYND0011E: Data collector has caught exception Exception
during sample collection and communication
Explanation
A Java exception was caught in a sampling or transport thread belonging to the
data collector.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
401
Operator response
Contact IBM support.
KYND0012E: The data collector has become disconnected
from the monitoring agent
Explanation
The data collector has lost its connection to the monitoring agent.
Operator response
Investigate the cause of the failure. This could be because the monitoring agent has
stopped running or has disconnected from the data collector for some reason. If
necessary, contact IBM support.
KYND0013E: Exception: Exception caught in DataGatherer
thread
Explanation
A Java exception was caught while attempting to collect data for transmission to
the monitoring agent. A stack trace is also written into the log.
Operator response
Contact IBM support.
KYND0014E: Exception: Exception caught processing Poll
request
Explanation
A Java exception was caught while attempting to collect data for transmission to
the monitoring agent. A stack trace is also written into the log.
Operator response
Contact IBM support.
KYND0015E: Incompatible Agent build level detected. Actual =
Actual Level Required = Required Level. Agent session
disconnected.
Explanation
The data collector discovered it was connecting to an older version of the
monitoring agent, which is unsupported.
Operator response
Determine why the monitoring agent version is too old relative to the version of
the data collector. If necessary, contact IBM support.
402
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
KYND0016I: Attempting to connect to agent on port Port
Number
Explanation
The data collector is attempting to connect to the monitoring agent on the specified
IP port.
KYND0017I: Data collector has connected to the monitoring
agent on port Port Number
Explanation
The data collector has established a connection with the monitoring agent on the
specified IP port.
KYND0018I: Data collector detailed logging is enabled with
type Type
Explanation
The data collector has enabled detailed logging. The message indicates the type of
tracing being performed.
KYND0019I: Data collector detailed logging is disabled
Explanation
The data collector has disabled detailed logging.
KYND0020I: Data collector detailed log opened on Type
Explanation
The data collector is writing a diagnostic log file to the file specified in the
message.
KYND0021W: Unable to open Type due to exception: Exception
Explanation
The data collector was unable to open the log file in the message because of the
specified exception. The data collector is continuing execution without a log file.
Operator response
Attempt to determine what caused the exception. Ensure that the application
server has the authority to create log files. If necessary, contact IBM support.
KYND0022E: I/O error encountered writing log file Log File
Explanation
An I/O error was detected while writing to the data collector log file specified in
the message.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
403
Operator response
Determine why the data collector cannot write to the log file.
KYND0023E: Unable to capture records for DD name Reason:
Reason
Explanation
The data collector was requested to gather garbage-collection data, but it was
unable to trap verbose GC messages for the reason specified. The ddname
identifies the DD statement from which messages are to be trapped.
Operator response
If Reason is No DEB, the WebSphere Application Server server does not have the
SYSOUT DD statement open. Ensure that the SYSOUT DD statement is present in
the application server JCL and that the JVM_LOGFILE parameter is not specified
in the current.env file for the application server. For any other reason, contact IBM
support.
KYND0024I: Performance Monitoring Infrastructure Service is
available for ServerName defined at ServerRoot configuration
repository
Explanation
The Performance Monitoring Infrastructure (PMI) service is avalable.
KYND0025W: Performance Monitoring Infrastructure Service is
not available for ServerName defined at ServerRoot
configuration repository
Explanation
The Performance Monitoring Infrastructure (PMI) service is not available. The
monitoring agent cannot collect and report PMI data.
Operator response
To collect and report PMI data, you must first enable the PMI service through the
WebSphere administrative console.
KYNX Messages: WebSphere Extended Deployment Agent
The following messages relate to the WebSphere Extended Deployment Agent.
They have IDs started with KYNX.
KYNX0001E: WebSphere location WAS_HOME is invalid.
Explanation
The specified directory does not exist or does not contain installed WebSphere
Extended Deployment product.
404
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
Set correct WebSphere location in the connection settings and enable the collection.
KYNX0002I: Connection with the WebSphere cell Cell was
successfully established.
Explanation
Connection with the cell was established and the monitoring was started.
Operator response
None.
KYNX0003W: Connection with the WebSphere cell Cell failed
with error Error.
Explanation
The connections with the cell's deployment manager was failed. Some monitoring
information may be lost while the connection is re-established.
Operator response
Find out why connection was broken. If the deployment manager can be restarted,
it is not the error. Check your environment for any issues that may break the
connection.
KYNX0004I: Connection with the WebSphere cell Cell was
retried successfully.
Explanation
Connection with the cell's deployment manager was retried immediately after a
break, and was without any data collection request failure. The connection break
should have minimal or no affect to the data collection.
Operator response
None.
KYNX0005E: Connection with the WebSphere cell Cell failed
with error Error.
Explanation
Connection can't be established with the specified cell.
Operator response
Find out what causes the failure and resolve the problem. It may be caused by
wrong connection settings, deployment manager not running or the network
between Tivoli Enterprise Monitoring Agent computer and deployment manager
not available or blocked by firewall.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
405
KYNX0006I: The WebSphere cell Cell was added to the agent.
Explanation
The WebSphere cell was added to the agent and will be displayed as a subnode in
the navigation tree.
Operator response
When the subnode is displayed in the navigation tree, configure your deployment
manager connection settings, set desired monitoring settings and enable
monitoring.
KYNX0007I: The WebSphere cell Cell was removed from the
agent
Explanation
The WebSphere cell was removed from the agent and will be displayed as offline
in the navigation tree.
Operator response
Clear the offline subnodes from the navigation tree.
KYNX0008I: Collection was disabled for the WebSphere cell
Cell.
Explanation
No monitoring will occur for the cell until collection is enabled by the user.
Operator response
None.
KYNX0009I: Collection was enabled for the WebSphere cell
Cell.
Explanation
The connection with the deployment manager will be established and monitoring
is started for the cell.
Operator response
None.
KYNX0010I: Connection with the WebSphere cell Cell failed
with error Error and is scheduled to reconnect with interval in
seconds Interval.
Explanation
Connection with the deployment manager failed and is scheduled to reconnect.
406
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
None.
Chapter 2. System Messages for ITCAM Agent for WebSphere Applications
407
408
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Chapter 3. System Messages for ITCAM Agent for J2EE
BWMIN Messages: Abstract Configurator
The following messages relate to the Abstract Configurator. All such messages
have IDs in the range BWMIN0000 to BWMIN0999.
BWMIN0000E: An error occurred with the installation program.
Operator response
Contact IBM Software Support.
KYJ messages: Tivoli Enterprise Monitoring Agent
The Tivoli Enterprise Monitoring Agent produces errors messages with IDs in the
range KYJA0000 to KYJA0999; these are described below and in the following
pages.
KYJA0001I: ITCAM for J2EE monitoring agent start-up
complete.
Explanation
The Tivoli Enterprise Monitoring Agent successfully completed initialization.
KYJA0002E: ITCAM for J2EE monitoring agent initialization
failed: errorMessage.
Explanation
The Tivoli Enterprise Monitoring Agent initialization failed.
Operator response
Collect the agent log and contact IBM support.
KYJA0003I: The Agent configuration file file loaded
successfully.
Explanation
The Tivoli Enterprise Monitoring Agent successfully loaded the configuration file
specified in the message.
KYJA0004E: The Agent configuration file file was not found.
Explanation
The Tivoli Enterprise Monitoring Agent monitoring configuration file specified in
the message was not found, the default configuration settings will be used.
© Copyright IBM Corp. 2007, 2010
409
Operator response
Reconfigure the Tivoli Enterprise Monitoring Agent to restore the configuration
file, or collect the agent log and contact IBM support.
KYJA0005E: Agent configuration file file loading error:
errorMessage.
Explanation
The Tivoli Enterprise Monitoring Agent monitoring configuration file specified in
the message could not be loaded so the default configuration settings will be used.
Operator response
Delete the corrupted configuration file manually and reconfigure Tivoli Enterprise
Monitoring Agent to restore the configuration file, or collect the agent log and
contact IBM support.
KYJA0006I: The Agent context file file loaded successfully.
Explanation
The Tivoli Enterprise Monitoring Agent successfully loaded the context file
specified in the message.
KYJA0007W: The Agent context file file was not found.
Explanation
The Tivoli Enterprise Monitoring Agent monitoring context file specified in the
message was not found and will be recreated.
KYJA0008W: Agent context file file loading error:
errorMessage.
Explanation
The Tivoli Enterprise Monitoring Agent monitoring context file specified in the
message could not be loaded so the corrupted file was deleted and will be
recreated.
KYJA0009I: Listening for incoming data collector connections
on port port.
Explanation
The Tivoli Enterprise Monitoring Agent successfully completed socket interface
initialization and is ready to accept incoming data collector connections.
KYJA0010I: Application server discovered: serverInfo.
Explanation
The Tivoli Enterprise Monitoring Agent accepted the new application server
connection and successfully completed handshaking. The new application server
was registered in the agent context and is available for on-line monitoring.
410
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
KYJA0011I: Application server connected: serverId.
Explanation
The Tivoli Enterprise Monitoring Agent accepted the registered application server
connection and successfully completed handshaking. The application server is
available for on-line monitoring.
KYJA0012I: Application server disconnected: serverId.
Explanation
The Tivoli Enterprise Monitoring Agent detected that the application server is
disconnected. The application server is no longer available for on-line monitoring,
but historical and log scrapping data monitoring functions are available.
KYJA0013E: Application server connection connectionInfo
failed: errorMessage.
Explanation
The Tivoli Enterprise Monitoring Agent accepted the incoming data collector
connection but handshaking failed with errors. The application server is not
available for monitoring.
Operator response
Collect agent and data collector logs and contact IBM support.
KYJA0014I: Resource data monitoring started for application
server serverId resourceMethod.
Explanation
The Tivoli Enterprise Monitoring Agent started resource data monitoring for the
specified application server.
KYJA0015I: Resource data monitoring stopped for application
server serverId.
Explanation
The Tivoli Enterprise Monitoring Agent stopped resource data monitoring for the
specified application server.
KYJA0016I: Request data monitoring started for application
server serverId requestMethod.
Explanation
The Tivoli Enterprise Monitoring Agent monitoring started request data monitoring
for the specified application server.
Chapter 3. System Messages for ITCAM Agent for J2EE
411
KYJA0017I: Request data monitoring stopped for application
server serverId.
Explanation
The Tivoli Enterprise Monitoring Agent stopped request data monitoring for the
specified application server.
KYJA0018I: Verbose GC output monitoring started for
application server serverId with interval gcInterval.
Explanation
The Tivoli Enterprise Monitoring Agent started verbose GC output monitoring for
specified application server.
KYJA0019I: Verbose GC output monitoring stopped for
application server serverId.
Explanation
The Tivoli Enterprise Monitoring Agent stopped verbose GC output monitoring for
specified application server.
KYJA0020I: Application server log scrapping started for
application server serverId alsInfo.
Explanation
The Tivoli Enterprise Monitoring Agent started application server log scrapping for
specified application server.
KYJA0021I: Application server log scrapping stopped for
application server serverId.
Explanation
The Tivoli Enterprise Monitoring Agent stopped application server log scrapping
for specified application server.
KYJA0022E: Application server log scrapping stopped for
application server serverId with error: errorMsg.
Explanation
The Tivoli Enterprise Monitoring Agent stopped application server log scrapping
for the specified application server because of errors detected.
Operator response
Collect the agent and data collector logs and contact IBM support.
412
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
KYJA0023I: Take action tactId successfully completed for
application server serverId.
Explanation
The Tivoli Enterprise Monitoring Agent successfully completed take action for the
specified application server.
KYJA0024E: Take action tactId failed for application server
serverId: tactReason.
Explanation
The Tivoli Enterprise Monitoring Agent take action failed for the specified
application server.
Operator response
Collect the agent and data collector logs and contact IBM support.
KYJA0025I: Take action tactId processing started for
application server serverId.
Explanation
The Tivoli Enterprise Monitoring Agent started background take action processing
for the specified application server.
KYJA0026E: Take sample table failed for application server
serverId: errorMsg.
Explanation
The Tivoli Enterprise Monitoring Agent failed to collect a sample for the specified
application server.
Operator response
Collect the agent and data collector logs and contact IBM support.
CYJNW Messages: SAP NetWeaver config toolkit
The following messages are related to SAP NetWeaver config toolkit. All such
messages have IDs in the range CYJNWI0000 to CYJNWI0999.
CYJNW0001E: invalid Central Instance Home
Explanation
The Central Instance Home is not valid
Operator response
Enter the correct Central Instance Home, for example, on Windows systems,
C:\usr\sap\J2E\JC00, on UNIX, /usr/sap/J2E/JC00
Chapter 3. System Messages for ITCAM Agent for J2EE
413
CYJNW0002E: Central Instance Network Home is not valid
Explanation
The Central Instance Network Home is not valid
Operator response
Ensure that the local path has been mounted from central instance home.
CYJNW0003E: Server Home is not valid
Explanation
Server Home is invalid
Operator response
Enter the correct value for Server Home, The Server Home value should be the
same as the instance home that will be monitored. For example, on Windows
systems, C:\usr\sap\J2E\JC00, on UNIX, /usr/sap/J2E/JC00
CYJNW0004E: JNDI information is not valid
Explanation
JNDI information is not valid
Operator response
Rnsure that NetWeaver is running and the JNDI information is correct.
CYJNW0005E: User or Password is not valid
Explanation
JNDI User or Password is not valid.
Operator response
Enter the correct JNDI User and Password
CYJNW0006E: HostName or IP address is not valid.
Operator response
Ensure that the HostName or IP address is correct, and that the IP address is a
qualified address, not a loopback address if the user input the IP address here
CYJNW0007E: Port number is not valid or JNDI service is
unavailable
Explanation
The port is not valid, or the server might be too busy to service the request, or the
server might not be registered to service any requests.
414
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
Ensure that the Port number is correct and JNDI service is available
CYJNW0008E: The server is not a local server
Operator response
Ensure that the server number is correct.
CYJNW0009E: The server has been configured before,
unconfigure it first
Operator response
The server has been configured before, unconfigure it first
CYJNW0010E: The server has not been configured
Operator response
The server has not been configured.
CYJNW0011E: The server is running now. Please stop the
server and make sure the database is running when you
uninstall or unconfigure Data Collector. Please refer to Data
Collector Installation Guide. Click Yes to continue Unconfigure
the Data Collector, Click No to stop Unconfigure the Data
Collector.
Explanation
The server is running now. Stop the server and make sure the database is running
when you uninstall or unconfigure Data Collector. Refer to Data Collector
Installation Guide. Click Yes to continue Unconfigure the Data Collector, Click No
to stop Unconfigure the Data Collector.
Operator response
The server is running now. Stop the server and make sure the database is running
when you uninstall or unconfigure Data Collector. Refer to Data Collector
Installation Guide. Click Yes to continue Unconfigure the Data Collector, Click No
to stop Unconfigure the Data Collector.
Chapter 3. System Messages for ITCAM Agent for J2EE
415
CYJNW0012E: The server is not running now. Please start the
server before you configure Data Collector. Please refer to
Data Collector Installation Guide.
CYJNW0013E: JVM GC Log should be a file not a directory.
CYJWCC Messages: WebSphere Application Server Community
Edition
The following messages are related to WebSphere Application Server Community
Edition. All such messages have IDs in the range CYJWCC0000 to CYJWCC0999.
CYJWCC001E: Cannot connect to WASCE server, check your
environment and server settings.
Operator response
Ensure that the JNDI parameters are correct.
CYJWCC002E: Incorrect UserID/Password.
Operator response
Ensure that the user ID or the password is correct.
CYJWCC003E: Cannot connect to WASCE server, check
host/port.
Operator response
Ensure that the host name or port number is correct.
CYJWCC004E: The server version is not correct.
Operator response
Ensure that the server version you selected is correct.
CYJWCC005E: The JAVA HOME is not correct. Please use
WASCE_JAVA_HOME defined in SERVER_HOME/bin/
setenv.bat or setenv.sh.
Operator response
Ensure that the java home you selected is correct.
CYJWCC006E: This is not a valid WASCE server directory.
Please check the specified directory.
Operator response
Ensure that the server home you selected is correct.
416
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYJWCC007E: Instance name is not valid.
Operator response
Ensure that the instance name does not contain any illegal character.
CYJWCC008E: This server has been configured by another
DC. Please unconfigure the old DC first.
Operator response
Unconfigure the old Data Collector and then configure this DC again.
CYJWCC009E: The GC log file is not valid.
Operator response
Ensure that the GC log file you selected is reachable.
CYJWLC Messages: WebLogic
The following messages are related to WebLogic. All such messages have IDs in
the range CYJWLC0000 to CYJWLC0999.
CYJWLC001: Cannot find weblogic server. Check your
environment and server settings.
Operator response
Contact IBM Software Support.
CYJWLC002: Incorrect User/Password.
Operator response
Contact IBM Software Support.
CYJWLC003: Cannot connect to weblogic server,check
host/port parameters. If connecting to weblogic over SSL,
please check SSL client CA trust keystore file , and client
certification files/types/password also.
Operator response
Contact IBM Software Support.
CYJWLC004: The Host Name is Incorrect.
Explanation
The machine hosting dc and appserver has a name that must be resolved by DNS
or the host file.
Operator response
Contact IBM Software Support.
Chapter 3. System Messages for ITCAM Agent for J2EE
417
CYJWLC005: The WebLogic startup script does not exist.
Explanation
The startup shell, such as startWebLogic.sh or startWebLogic.cmd, does not exist.
Operator response
Contact IBM Software Support.
CYJWLC006: stdout redirection file or parent directory does
not exist.
Explanation
The stdout redirection file is a file that is used to save the standard system output.
Operator response
Contact IBM Software Support.
CYND Messages: Data Collector
The following messages relate to the ITCAM Agent for J2EE data collector. All such
messages have IDs in the range CYND0000 to CYND0999.
CYND0012I: Data Collector stopping.
Explanation
Status messages of the Data Collector.
CYND0013I: Data Collector stopped.
Explanation
Status messages of the Data Collector.
CYND0014I: Data Collector starting.
Explanation
Status messages of the Data Collector.
CYND0015I: Data Collector started.
Explanation
Status messages of the Data Collector.
CYND0026I: Event Agent started.
Explanation
A status message during the start-up of the Data Collector.
418
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND0027E: Failed in publishing records to Publish Server.
Explanation
The Data Collector encountered a communication error when its Event Agent
attempted to send the records to the publish server.
Operator response
Ensure that the publisher is running correctly. If the problem persists, contact the
IBM support.
CYND0031I: Getting Publish Engine from kernel.
Explanation
The Data Collector tried to download the interface code to the Publish Server from
the Kernel.
CYND0033I: Publish Engine successfully downloaded from
kernel.
Explanation
The Data Collector successfully downloaded the interface code to the Publish
Server from the Kernel.
CYND0040I: Include List: List
Explanation
During start-up, the Data Collector displays a list of classes that will be monitored
when the Profiling mode is turned on. This list should be specified as a sub-list of
the exclude list.
Operator response
Determine whether the list is correct. This list can be modified by reconfiguring the
data collector.
CYND0042I: Exclude List: List
Explanation
During start-up, the Data Collector displays a list of classes whose methods will
not be monitored when the Profiling mode is turned on.
Operator response
determine whether the list is correct. This list can be modified by reconfiguring the
data collector.
CYND0046W: record1/record2 records dropped
Explanation
The Event Agent of the Data Collector has to drop a number of records due to
either network slowdown or an overloaded Publish Server.
Chapter 3. System Messages for ITCAM Agent for J2EE
419
Operator response
Determine whether the Publish Server is bottlenecked on CPU capacity or a
network congestion between the Data Collector and the Publish Server. Restart the
Publish Server if desirable. Contact IBM support if the problem persists.
CYND0049I: Connected to Publish ServerHost:Server with send
buffer size Buffer Size
Explanation
The Data Collector connected to the Publish Server at the specified IP address and
port number. The send buffer size is set to the value specified by the Publish
Server.
CYND0079E: Error in getting stack trace for thread Thread ID
Explanation
Command Agent failed to get the stack trace for the specified thread.
Operator response
Report to IBM support.
CYND0087I: Logging level changed from Level to Level1.
Explanation
Indicates that a request to change the logging level is complete.
CYND0219E: Failed to GetStringUTFChars
Explanation
An error occurred while converting string to UTF8.
Operator response
Report to IBM support.
CYND0220E: generateThreadDump failed
Explanation
The thread dump info field is null.
Operator response
Report to IBM support.
CYND0221E: generateThreadDump failed
Explanation
Generating thread dump failed.
420
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
Report to IBM support.
CYND0222E: Can't get ThreadDumpInfo class
Explanation
Cannot get the thread dump information.
Operator response
Report to IBM support.
CYND0223E: Cannot find method Method
Explanation
Cannot find method name.
Operator response
Report to IBM support.
CYND0224E: Failed to allocate memory
Explanation
Memory allocation failed.
Operator response
Report to IBM support.
CYND0225E: Event Agent already started
CYND0226E: Failed to obtain jvmmi handle for heap dump
Explanation
Getting JVMMI handle for heap dump has failed.
Operator response
Report to IBM support.
CYND0227E: No javacore is generated.
Explanation
Javacore is not generated.
CYND0228E: Unable to get RAS
Explanation
Getting RAS has failed.
Chapter 3. System Messages for ITCAM Agent for J2EE
421
Operator response
Report to IBM support.
CYND0229I: Number of CPU = Number of CPU
Explanation
Display the machine number of cpu.
CYND0230E: Error in getting number of cpu with return code
= Error code
Explanation
Error in getting number of cpu.
Operator response
Report to IBM support.
CYND1001I: Native Custom Service initialized successfully.
CYND1001I: DC for WebLogic 8/9
Explanation
Data Collector for WebLogic Name.
CYND1002E: Custom Service initialization failed because
JVMPI could not be initialized
Explanation
Custom Service initialization failure is because the JVM argument -Xrun is not
being specified correctly.
Operator response
Refer to the Installation Guide and verify that the Application server is configured
correctly.
CYND1002I: DC for WebLogic
Explanation
Data Collector for WebLogic short name.
CYND1003I: Native Custom Service shutdown complete.
CYND1003I: WebLogic Server Home
Explanation
WebLogic Server Home Directory, for example C:/bea/weblogic81.
422
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
Input this argument.
CYND1004I: Native probe started successfully.
CYND1004I: WebLogic Server Home Directory, for example
C:/bea/weblogic81.
CYND1005I: Native probe stopped successfully.
CYND1005I: WebLogic Server Type
Explanation
WebLogic server type should be wls.
CYND1006E: The am.home system property is undefined.
Explanation
The Installer failed to set am.home during installation.
Operator response
Refer to the Installation Guide for information about specifying am.home correctly.
CYND1006I: WebLogic Server Type
Explanation
WebLogic server type should be wls.
CYND1007W: The weblogic.Domain system property is
undefined.
Explanation
The Installer failed to set weblogic.Domain during installation.
Operator response
Refer to the Installation Guide for information about specifying weblogic.Domain
correctly.
CYND1008I: WebLogic Server 8
Explanation
WebLogic server version 8
CYND1008W: The am.nodename system property is undefined.
Explanation
The Installer failed to set am.nodename during installation.
Chapter 3. System Messages for ITCAM Agent for J2EE
423
Operator response
Refer to the Installation Guide for information about specifying am.nodename
correctly.
CYND1009W: The weblogic.Name system property is
undefined.
Explanation
The Installer failed to set weblogic.Name during installation.
Operator response
Refer to the Installation Guide for information about specifying weblogic.Name
correctly.
CYND1009I: WebLogic Server 9
Explanation
WebLogic server version 9
CYND1010W: The am.appserver system property is undefined.
Explanation
The Installer failed to set am.appserver during installation.
Operator response
Refer to the Installation Guide for information about specifying am.appserver
correctly.
CYND1010I: Select the WebLogic server version number
CYND1011I: ProbeManager started successfully.
CYND1011I: Java Home
Explanation
The Home directory of JDK that the application server instance uses.
CYND1012E: Failed to start ProbeManager.
Explanation
JVMPI initialization failed.
Operator response
Check the application configuration and Installation Guide. Verify that the required
JVM arguments are set correctly.
424
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND1012I: Java home directory name
Explanation
The Home directory of JDK that the application server instance uses.
CYND1013F: JVMPI was not initialized by native probe start
exiting.
Explanation
Failure to initialize JVMPI might be caused by either a corrupted libam.so file, or
JVM arguments are set incorrectly.
Operator response
Check the application configuration and Installation Guide. Verify that the required
JVM arguments are set correctly.
CYND1014I: Probe manager stopped successfully.
CYND1015F: JVMPI initialization failed.
Explanation
Failure to initialize JVMPI might be caused by either a corrupted libam.so file, or
JVM arguments that are set incorrectly.
Operator response
Check the application configuration and Installation Guide. Verify that the required
JVM arguments are set correctly.
CYND1016I: Initialized event interface successfully.
CYND1017E: Failed to initialize JVMMI.
Explanation
Failure to initialize JVMMI might be caused by either a corrupted libam.so file, or
JVM arguments that are set incorrectly.
Operator response
Check the application configuration and Installation Guide. Verify that the required
JVM arguments are set correctly.
CYND1018I: Using tracing mode: mode_str(mode_int), and
monitoring level is: mod_level
Explanation
There are three tracing modes: classic, new and hybrid. The default tracing mode is
new. There are three monitoring (MOD) levels. They are Production (L1), Problem
Determination (L2) and Debug Method Trace (L3). The default MOD level is L1.
Chapter 3. System Messages for ITCAM Agent for J2EE
425
CYND1019E: Error occurred during encryption.
Explanation
The error occurred as the result of a corrupted user ID and password.
Operator response
Check the input user ID and password, and verify that they are in clear text.
CYND1020E: Invalid file name.
Explanation
The filename containing the user ID and password is invalid.
Operator response
Verify that the properties certificate.path and keystore.location are set correctly in
datacollector.properties.
CYND1021I: WebLogic Server Host
Explanation
WebLogic server's jndi host name or IP address.
CYND1021E: Invalid user ID or password.
Explanation
User ID or password is missing.
Operator response
Enter a valid user ID and password.
CYND1022E: Invalid file name.
Explanation
The filename containing user ID and password is invalid.
Operator response
Verify that the properties certificate.path and keystore.location are set correctly in
datacollector.properties.
CYND1022I: WebLogic server's jndi host name or IP address
Explanation
WebLogic server's jndi host name or IP address
CYND1023E: Invalid user ID or password.
Explanation
User ID or password is missing.
426
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
Refer to the Installation Guide and enter a valid user ID and password.
CYND1023I: WebLogic JMX Server Port
Explanation
WebLogic server JMX port number.
CYND1024E: Could not open the file: filename
Explanation
Either the file does not exist, or the file does not have read permissions.
Operator response
Verify that the file exists and has read permission
CYND1024I: WebLogic server port number
CYND1025E: No data in the file: filename
Explanation
The file is empty.
Operator response
Verify that the file contains a valid user ID and password.
CYND1025I: WebLogic Server User ID
Explanation
The user ID to connect with WebLogic server MBean Server.
CYND1026E: Invalid file name, user ID or password.
Explanation
Either the file name, user ID or password is missing.
Operator response
Refer to the Installation Guide and verify that a valid ker store, certificate, user ID
and password are provided.
CYND1026I: WebLogic server JMX user id
Explanation
WebLogic server JMX user ID, the user should be admin user.
Chapter 3. System Messages for ITCAM Agent for J2EE
427
CYND1027E: Could not open the file for writing: filename
Explanation
The error might be caused by no write permissions on the file.
Operator response
Verify that the account has write permissions to the file.
CYND1027I: WebLogic Server Password
Explanation
WebLogic server JMX password.
CYND1028E: The input string is corrupt.
Explanation
The user ID and password is too long.
Operator response
Verify that the user ID and password do not exceed the maximum length.
CYND1028I: WebLogic server JMX password
CYND1029E: UID, PASSWORD or filename is NULL.
Explanation
The user ID, password or generated password filename is missing.
Operator response
Refer to the Installation Guide and verify that a valid user ID, password and
generated password filename exist.
CYND1029I: WebLogic Server Instance Names
Explanation
The list of webLogic server instance names.
CYND1030E: Your actual password and decrypted password
don't match
Explanation
The password might contain a space.
Operator response
Turn off Caps Lock and ensure that there are no spaces in the password.
428
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND1030I: The list of webLogic server instance names
CYND1031E: The user ID read from the file is not the same as
the UID entered.
Explanation
Verify that you typed in a valid user ID.
Operator response
Enter a valid user ID.
CYND1031I: Console Output Redirect File
Explanation
The file to which the weblogic server's stdout will be redirected.
CYND1032E: Password read from the file is not the same as
the password entered.
Explanation
Verify that you entered a valid password.
Operator response
Enter a valid password.
CYND1032I: The redirection File name of WebLogic server
standard output is needed when the selected instance is a
standalone server. When the selected server is a Managed
Server, the redirection file name can be obtained from MBean
Server
Explanation
The WebLogic server to which standard output will be redirected.
CYND1033I: Verified user ID and password by reading the
created file, passwordfile. filename was correctly created.
CYND1033I: WebLogic Server Startup Script
Explanation
Weblogic server startup script normally will be startWebLogic.cmd/sh.
CYND1034E: Encrypted password string is corrupt.
Explanation
The password is too long.
Chapter 3. System Messages for ITCAM Agent for J2EE
429
Operator response
Verify that the password does not exceed the maximum length.
CYND1034I: Weblogic server startup script normally will be
startWebLogic.cmd/sh.
CYND1035E: Error occurred during decryption.
Explanation
The password might be corrupt.
Operator response
Enter a valid password
CYND1035I: TEMA Host Name
Explanation
The host name to be used to communicate with Tivoli Enterprise Monitoring Agent
system.
CYND1036E: The password is too long. It should be less than
max_len characters.
Explanation
The password is too long.
Operator response
Verify that the password does not exceed the maximum length.
CYND1036I: TEMA host name can be found in
itcamdc/etc/kwjdc.properties.
Explanation
The host name to be used to communicate with Tivoli Enterprise Monitoring Agent
system.
CYND1037E: JVMPI could not create a Raw Monitor for
GlobalLock.
Explanation
An internal error has occurred.
Operator response
Restart the Application Server.
430
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND1037I: TEMA Port Number
Explanation
The port number to be used to communicate with Tivoli Enterprise Monitoring
Agent system.
CYND1038E: Global lock was created before initialization of
JVMPI.
Explanation
An internal error has occurred.
Operator response
Restart the Application Server.
CYND1038I: TEMA port number can be found in
itcamdc/etc/kwjdc.properties.
Explanation
The port number to be used to communicate with Tivoli Enterprise Monitoring
Agent system.
CYND1039I: JVM GC Log
Explanation
The file is used to obtain the java GC log.
CYND1039W: This is an unknown event type, TypeID: evt_type
Explanation
An internal error has occurred.
Operator response
Restart the Application Server.
CYND1040E: The EventAgent was not started and cannot
manage ThreadData.
Explanation
The EventAgent failed to start.
Operator response
Refer to the Installation Guide for the Data Collector. Restart the Application
Server.
Chapter 3. System Messages for ITCAM Agent for J2EE
431
CYND1040I: JVM GC log is used to obtain java GC log.
Explanation
The file is used to obtain the java GC log.
CYND1041W: Failed to send data.
Explanation
The connection to the Publish Server is broken.
Operator response
Check the network connection between the Data Collector and the Managing
Server. Verify that the connection is established correctly.
CYND1041I: WebLogic Server Version
Explanation
The WebLogic server version supported by ITCAM for J2EE Data Collector.
CYND1042E: Event Queue is NULL for Thread, TID: tid
Explanation
An internal error has occurred.
Operator response
Restart the Application Server.
CYND1042I: Please enter the WebLogic Home and Java Home.
WebLogic Server Home is the installation directory of
WebLogic(e.g. C:\\bea\\weblogic8). WebLogic Server Version is
the major version of WebLogic server. Java Home is the
installation directory of JDK that is used to run Weblogic
server.
Explanation
SERVER_HOME/SERVER_VERSION/JAVA_VERSION.
CYND1043W: Overall events dropped/deleted:evtDropCnt
Explanation
The Publish Server is down.
Operator response
Check the Managing Server and verify that the Publish Server is up and running.
432
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND1043I: Please enter the information of WebLogic Server
for server instances discovery WebLogic Server Host is the
name of host where the admin server is located. WebLogic
JMX service port is the listening port for the JMX service of
WebLogic. User ID and password are required in order to get
JMX Data from MBean Server.
Explanation
JNDI info.
CYND1044I: Events dropped cnt for thread threadNamebecause
they exceeded event queue limit of queueLimit
Explanation
This message indicates that either the event queue size is too small or the
frequency of sending data to the Publish Server is too low. If this message occurs
repeatedly, the metrics collected on the Managing Server will be incorrect.
Operator response
Increase the event queue size and publish frequency. In datacollector.properties,
modify the property internal.probe.event.queue.size.limit and
internal.probe.publishing.frequency.
CYND1044I: Please select server instance to instrument.
Please select the Server instance you expect to instrument.
After selecting the instance, please input following
information which is used to configure DC to collect data from
related WebLogic server instance. WebLogic Server Host is
the name of host where the instrumented server is located.
WebLogic JMX service Port is the listening port for the JMX
service of WebLogic server. User ID and password are
required by DC in order to get JMX data from MBean server.
Startup script is the script that is used to start WebLogic
Server instance.
Explanation
Server instance selection.
CYND1045I: Modify WebLogic startup script
CYND1045W: Thread data creation failed.
Explanation
The server is out of native memory.
Chapter 3. System Messages for ITCAM Agent for J2EE
433
Operator response
Check memory utilization on the server.
CYND1046I: EvtAgentManager started.
CYND1046I: Modify WebLogic startup script
CYND1047I: EvtAgentManager stopped.
CYND1047I: UNIX 64bit JVM
CYND1048E: Class file is corrupt.
Explanation
The ClassLoadHookEvent is corrupted. Therefore, eventHandler failed to get
constant pool.
Operator response
Restart the Application Server.
CYND1048I: Validating MBean Server related information
CYND1049E: Bad class file magic number:magic
Explanation
The class file is corrupted.
Operator response
Restart the Application Server.
CYND1049I: Validating MBean Server Host name and service
point
CYND1050E: Failed to open library: libName
Explanation
The library path was not set correctly.
Operator response
Refer to the Installation Guide. Verify that the library path is set correctly.
434
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND1050I: Validating Startup Script
CYND1051I: Memory limit is less than the minimum limit:
memLimit MB
Explanation
The minimum memory limit is 4MB
Operator response
Verify that the property internal.memory.limit in datacollector.properties is
assigned a value within the limits.
CYND1051I: Retreiving Server information from MBean Server
CYND1052I: Memory monitor properties, ULimit: memUlimit
bytes, Accept Threshold: threadHold bytes, URL Limit: urlUlimit,
SQL Limit: sqlUlimit
CYND1052I: Validating Java home, Server Home, Server
version
CYND1053I: Queue counter resets every resetTimerCount
iterations.
Explanation
Be default, the counters used by memory monitor reset every hour.
CYND1054W: Memory Limit reached, Data Collector stopped
accepting data, Limit: usedMemUlimit Memory Utilization:
memTaken
Explanation
This warning might occur when the rate of receiving events is higher than the rate
of publishing events.
Operator response
Check network configuration, and verify that there is enough network bandwidth
to transfer data to Publish Server.
Chapter 3. System Messages for ITCAM Agent for J2EE
435
CYND1055I: Memory utilization is below the limit; the Data
Collector is accepting data, Limit: usedMemUlimit Memory
Utilization: memTaken
CYND1055I: TEMA Host Name
Explanation
The host name to be used to communicate with Tivoli Enterprise Monitoring Agent
system.
CYND1056W: Network Agent Thread is not started/alive/ready;
rejecting send data.
Explanation
The Data Collector failed to initialize the Network Agent.
Operator response
Restart the Application Server.
CYND1056I: The TEMA host name can be found in
itcamdc/etc/kwjdc.properties.
Explanation
The host name to be used to communicate with Tivoli Enterprise Monitoring Agent
system.
CYND1057W: The queue is full and exceeds the buffer limit.
Explanation
The network is slow, and it takes significant amount of time to publish data.
Operator response
Check the network configuration.
CYND1058I: Validating Server Version
Explanation
Validate Server Version
CYND1058W: Publish Server lookup failed.
Explanation
The Kernel of the Publish Server is down.
Operator response
Check the Managing Server and verify that all the components are up and
running.
436
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND1059E: The Data Collector failed to connect to host %s
/port %d. Error number is %d
Explanation
The Data Collector failed to establish a connection to the Publish Server.
Operator response
Check the Managing Server configuration and verify that the Publish Server ports
are set correctly.
CYND1060I: Successfully connected to Publish Server Host:
%s Port: %d Buffer Size: %d
CYND1061I: Wrong server home selected.
CYND1062I: The selected Weblogic Server Version does not
match the Weblogic Server Home.
Explanation
The selected Weblogic Server Version does not match the Weblogic Server Home!
CYND1063I: The selected Weblogic Server Startup script was
incorrect.
CYND1064I: A clean server instance cannot be unconfigured.
CYND1065I: Current server instance is already configured.
CYND1068I: weblogic 9 is not compatible with selected JAVA
HOME, please select jdk version 1.5 or above.
Explanation
The Java Home is incorrect.For weblogic 9 should use JDK version 1.5 or above.
Chapter 3. System Messages for ITCAM Agent for J2EE
437
CYND1069I: The instance has been configured by another DC,
please unconfigure it firstly.
CYND1070I: The instance has been configured by RTT without
fixpack, please reconfigure the instance after apply the
fixpack for RTT.
CYND1071I: GC log file path doesn't exist!
CYND1072E: SSL Trust CA keystore file doesn't exists.
CYND1073E: SSL client certificate file doesn't exist:{0}
CYND1074E: Element count not equals in
WL_SSL_CERT_TYPES and WL_SSL_CERT_FILES.
CYND1075E: SSL certificate file types contains invalid type
string, legal type string should be PEM or DER.
CYND1076E: Element count not equals in
WL_SSL_CERT_TYPES and WL_SSL_CERT_FILES.
CYND1077E: SSL certificate file types contains invalid type
string, legal type string should be PEM or DER.
CYND1078E: Set SSL client certificates failed.
Explanation
Set SSL client certificates failed, ensure certificate files and the sequence are valid.
CYND1079E: {0} has too few files,{0} should contain at least
two files: SSL client private key and client certificate file.
Explanation
WL_SSL_CERT_FILES/INST_WL_SSL_CERT_FILES should contains at least two
files: SSL client private key and client certificate file, and need to contain
intermediate CA certificate file if required.
CYND1060I: WebLogic Portal Server 8
CYND1061E: Socket write to Publish Server failed, [%s:%d],
ERRNO: %s
Explanation
The Data Collector failed to write to the socket.
438
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
Check the network configuration and the error code.
CYND1062I: Network agent thread started.
CYND1063I: Successfully connected to the Publish Server
socket.
CYND1064E: Failed to connect to the Publish Server socket.
Explanation
The Publish Server might be down.
Operator response
Check the Managing Server configuration.
CYND1065W: Could not obtain Publish Server proxy details
from the Kernel.
Explanation
The Publish Server could be down.
Operator response
Check the Managing Server configuration.
CYND1066I: NetworkAgentManager started.
CYND1066I: WebLogic Server domain name
CYND1067I: NetworkAgentManager stopped.
CYND1067I: WebLogic Server domain name
CYND1068E: am.home was not found; failed to initialize the
Property Manager.
Explanation
The Installer failed to set it during installation.
Operator response
Refer to the Installation Guide and specify it correctly.
CYND1069E: Default property file %s not found.
Explanation
The Installer failed to copy it during installation.
Chapter 3. System Messages for ITCAM Agent for J2EE
439
Operator response
Refer to the Installation Guide and copy it manually.
CYND1070I: Using property file %s.
CYND1071I: PropertyMgr started.
CYND1072I: Thread Manager started.
CYND1073I: Thread Manager stopped.
Operator response
CYND1074E: Failed to retrieve the command arguments for
WAS.
Explanation
An internal error has occurred.
Operator response
Restart the Application Server.
CYND1075E: Failed to retrieve command line arguments for
Stand Alone Java.
Explanation
An internal error has occurred.
Operator response
Restart the Application Server.
CYND1076E: Failed to construct ThreadDumpInfo object.
Explanation
The server is out of Java heap memory.
Operator response
Increase Java heap size and restart the Application Server.
CYND1077E: Probe is disabled; cannot return stack trace.
Explanation
The Data Collector is not configured yet.
Operator response
Configure the Data Collector from the Managing Server.
440
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND1078I: Using modfile: %s
CYND1079I: Failed to write modfile.
Explanation
There are no write permissions on modfile.
Operator response
Verify that am.home/etc has both read and write permissions.
CYND1080I: Using probe level %d.
CYND1081I: Native library build TIME : %s DATE: %s
CYND1082I: Successfully registered
defineNativeMethodsForClassNative for
com.cyanea.bcm.bootstrap.BcmBootstrap.class.
CYND1083E: Cannot find
com.cyanea.bcm.bootstrap.BcmBootstrap.class.
Explanation
The JVM arguments -Xbootclasspath is not configured correctly.
Operator response
Refer to the Installation Guide and verify that JVM is configured correctly.
CYND1084I: Heap Snapshot not supported by default; set
internal.doheapdump=true to activate it.
Explanation
This message only applies to Solaris OS. Heap snapshot might crash the server
when it is under load.
Operator response
Set internal.doheapdump=true to activate heap snapshot on Solaris after careful
consideration.
CYND1085W: Failed to open stdout.
Explanation
The cause of this error is that either cyanea.probe.stdout is not defined or the value
is incorrect.
Operator response
Verify that cyanea.probe.stdout is configured with the correct value.
Chapter 3. System Messages for ITCAM Agent for J2EE
441
CYND1086E: Unable to send CTRL+BREAK event to JVM
process. Err(%ld)
Explanation
The Application Server was started as a Windows service. CTRL+BREAK only
works when the server is started from a console.
Operator response
Start the server from a console and try again.
CYND1087E: Unable to send SIGQUIT to JVM process.
Err(%ld)
Explanation
Java process hangs or is under load.
Operator response
Do not try to get thread dump or a stack trace when the server is under load. Try
later when the server load is lighter.
CYND1088E: Cannot get Java system property
cyanea.probe.stdout.
Explanation
The Installer failed to set it correctly. This property is only needed for hotspot jdk.
Operator response
Refer to the Installation Guide and configure it correctly.
CYND1089E: Cannot open cyanea.probe.stdout:%s
Explanation
The possible cause of this error is that the wrong value was specified. For
WebSphere 5 and WebSphere 6, it is defined as WAS_home/serverName/logs/
native_stdout.log; for weblogic stand alone server, it is defined as java process
standard output; for weblogic remotely managed server, it is defined as
WL_home/common/NodeManagerLogs/domainName_serverName/
serverName_output.log
Operator response
Verify that cyanea.probe.stdout is configured with the correct value.
CYND1090E: Failed to retrieve command line arguments for
WebLogic.
Explanation
An internal error occurred.
442
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
Restart the Application Server.
CYND1091E: Incorrect method id from method stack
Explanation
An internal error for Method Profiling has occurred.
Operator response
Should be an warning messages, if this messages repeated many times. Stop using
Method Profiling.
CYND1092E: Cannot find the the method stack.
Explanation
An internal error for Method Profiling has occurred.
Operator response
Should be an warning messages, if this messages repeated many times. Stop using
Method Profiling.
CYND1093E: Run out of method stack.
Explanation
An internal error for Method Profiling has occurred.
Operator response
Increase am.mp.threadSize in datacollector.properties and restart Application
Server.
CYND1094E: Primitive Stack overflow.
Explanation
An internal error for Method Profiling has occurred.
Operator response
Increase am.mp.threadSize in datacollector.properties and restart Application
Server.
CYND1095E: Primitive Hash overflow.
Explanation
An internal error for Method Profiling has occurred.
Operator response
Increase am.mp.threadSize in datacollector.properties and restart Application
Server.
Chapter 3. System Messages for ITCAM Agent for J2EE
443
CYND1096E: MPHash overflow.
Explanation
An internal error for Method Profiling has occurred.
Operator response
Increase am.mp.leagueTableSize in datacollector.properties and restart Application
Server.
CYND1097E: MPData table overflow.
Explanation
An internal error for Method Profiling has occurred.
Operator response
Increase am.mp.leagueTableSize in datacollector.properties and restart Application
Server.
CYND1098I: Total estimated memory allocated by Method
Profiling, %s MB.
CYND1100I: Region Mask from Kernel = Kernel
Explanation
Received region mask from kernel.
CYND1101I: Please restart your Application server to enable
the configuration and ensure to shutdown WebLogic server
instance via the Administration Console. For more detailed
information about how to shut down WebLogic Server, please
refer to URL: http://e-docs.bea.com/wls/docs81/ConsoleHelp/
startstop.html. If a node manager is used to start and stop the
configured server instance, please restart the node manager
too. If a server instance configured by Data Collector is an
administrative server instance, when the server is shutdown
there are some exceptions throwing and the server instance
will be restarted automatically. In this case, please stop it
again and start it using startup command.
Explanation
This is the post configuration instruction of data collector.
CYND1102I: Region ID = 0xID8X
Explanation
Region ID of the datacollector.
444
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND1102I: JNDI Protocol Type
CYND1103I: Region Mask = 0xMask8X
Explanation
Region mask of the datacollector.
CYND1103I: t3
Explanation
jndi protocol : t3
CYND1104E: Cannot get the server common storage with
error number = Error
Explanation
Cannot get the server common storage.
Operator response
Report to IBM support.
CYND1104I: t3s(one way SSL)
Explanation
jndi protocol : t3s over one way SSL
CYND1105I: Enqueue server, Server, exclusively with return
code = RC
Explanation
Return code when locking the server common storage exclusively.
Operator response
Report to IBM support if the return code does not equal 0 or 4.
CYND1105I: t3s(two way SSL)
Explanation
jndi protocol : t3s over two way SSL
CYND1106I: Enqueue server, Server, shared with return code =
RC
Explanation
Return code when locking the server common storage shared.
Operator response
Report to IBM support if the return code does not equal 0.
Chapter 3. System Messages for ITCAM Agent for J2EE
445
CYND1106I: Select the JNDI Procotol type
Explanation
Select the JNDI Procotol type: t3,t3s( one way or two way SSL).
CYND1107I: Gps counter file = Counter
Explanation
File to persist the gps counter.
CYND1107I: SSL trust CA key store file
Explanation
Select the SSL trust CA key store file.
CYND1108I: Gps counter get from file = File
Explanation
Gps counter got from the file.
CYND1108I: Select the trust CA key store file used by SSL to
verify the server certificate.
CYND1109I: Gps counter file, File, created
Explanation
Gps counter file created when it does not exist.
CYND1109I: SSL client certificate file type strings
Explanation
SSL client PEM file type strings, should be DER or PEM, separated by |.
CYND1110I: SSL client certificate file type strings, should be
DER or PEM, multiple file type strings are separated by |.
Explanation
SSL Client PEM file type strings, should be DER or PEM, separated by |.
CYND1111I: SSL client certificate files
Explanation
SSL Client certificate files, multiple files are separated by |.
CYND1112E: Unable to open counter file, File
Explanation
Not able to open gps counter file.
446
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
Report to IBM support.
CYND1112I: SSL client certificate files, the first file should be
private key file. All but the first of the certificates are issuer
certificates for the previous certificate. multiple files are
separated by |.
CYND1113I: Password for encrypted SSL client RSA private
key
Explanation
Password for encrypted SSL client RSA private key; if the file is not encrypted,
password is not required.
CYND1114I: Password for encrypted SSL client RSA private
key; if the file is not encrypted, password is not required.
CYND2001I: DC for Tomcat 5
Explanation
Data Collector for Tomcat Name
CYND2002I: DC for Tomcat
Explanation
Data Collector for Tomcat short name
CYND2003I: Tomcat Server Home
Explanation
Tomcat Server Home Directory, for example, C:/jakarta-tomcat-5.5.15.
Operator response
Input this argument.
CYND2004I: Tomcat Server Home Directory, for example,
C:/jakarta-tomcat-5.0.28.
Explanation
The application cannot resolve the IP address of the computer on which it is
running.
CYND2005I: Tomcat Server Type
Explanation
Tomcat server type should be tomcat.
Chapter 3. System Messages for ITCAM Agent for J2EE
447
CYND2006I: Tomcat Server Type
Explanation
Tomcat server type should be tomcat
CYND2008I: Tomcat Server 5.0
Explanation
Tomcat server version 5.0
CYND2009I: Tomcat Server 5.5
Explanation
Tomcat server version 5.5
CYND2010I: Select the Tomcat server version number
CYND2011I: Java Home
Explanation
The Java home directory that the application server instance uses.
CYND2012I: Java home directory name
Explanation
The Java home directory that the application server instance uses.
CYND2021I: Tomcat Server Startup Script
Explanation
The Tomcat server startup script usually will be catalina.bat/sh.
CYND2022I: The Tomcat server startup script usually will be
catalina.bat/sh.
CYND2023I: Instance Names
Explanation
The list of tomcat server instance names.
CYND2024I: List of instances
Explanation
The list of tomcat server instance names.
CYND2026I: Standard Out File
Explanation
The Tomcat Server Standard Out File.
448
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND2027I: Standard Out File
Explanation
The Tomcat Server Standard Out File.
CYND2029I: <html><font size=4>Tomcat Server Home is
Tomcat installation location. <br>Tomcat Server Version is the
specified version. <br>Java Home is JDK installation
location</html>
Explanation
Tomcat Home Information.
CYND2030I: Tomcat Server Startup Script is the full path of
the Tomcat startup script.( e.g. C:/tomcat5.5/bin/catalina.bat )
Instance Name is Tomcat Server Instance Name that will be
shown on VE.( e.g. tomcat55instance ) Caution: Tomcat
Startup Script should be catalina.sh/catalina.bat but
startup.sh/startup.bat.
Explanation
Tomcat Server Instance Information.
CYND2031I: Server Version
Explanation
Tomcat Server Version Information.
CYND2035I: TEMA Host Name
Explanation
The host name be used to communicate with the Tivoli Enterprise Monitoring
Agent system.
CYND2036I: TEMA host name can be found in
itcamdc/etc/kwjdc.properties.
Explanation
The host name be used to communicate with Tivoli Enterprise Monitoring Agent
system.
CYND2037I: TEMA Port Number
Explanation
The port number to be used to communicate with Tivoli Enterprise Monitoring
Agent system.
Chapter 3. System Messages for ITCAM Agent for J2EE
449
CYND2038I: TEMA port number can be found in
itcamdc/etc/kwjdc.properties.
Explanation
The port numbe to be used to communicate with Tivoli Enterprise Monitoring
Agent system.
CYND2039I: JVM GC Log
Explanation
The file used to obtain the java GC log.
CYND2040I: JVM GC log is used to obtain the java GC log.
Explanation
The file is used to obtain the java GC log.
CYND2050I: Use JDK as 64 bit?
CYND2051I: Use JDK as 64 bit?
CYND2025I: Cannot find the file catalina.properties at tomcat
home, check the file!
CYND2052I: Use JDK as 64 bit?
CYND2053I: Cannot find startup script!
CYND2054I: The server is not the correct version!
Operator response
Ensure that the correct version of the server is selected.
450
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND2055I: The server was configured before!
CYND2056I: RTT61 Fixpack needed!
CYND2057I: This instance name is already in use!
CYND2058I: The server is running now. Please stop the server
when you uninstall or unconfigure Data Collector. Please refer
to Data Collector Installation Guide.
CYND2059I: A Tomcat server shouldn't use different instance
name during reconfiguration!
CYND2060I: GC log file path doesn't exist!
CYND3001I: DC for JBoss 3/4
Explanation
Data Collector for JBoss Name
CYND3002I: DC for JBoss
Explanation
Data Collector for JBoss short name
CYND3003I: JBoss Server Home
Explanation
JBoss Server Home Directory, for example C:/jboss-4.0.4
CYND3004I: JBoss Server Home Directory, For example
C:/jboss-4.0.4
Explanation
JBoss Server Home Directory.
CYND3005I: JBoss Server Type
Explanation
JBoss server type should be jboss.
CYND3006I: JBoss Server Type
Explanation
JBoss server type should be jboss.
Chapter 3. System Messages for ITCAM Agent for J2EE
451
CYND3008I: JBoss 4
Explanation
JBoss server version 4
CYND3009I: JBoss 3
Explanation
JBoss server version 3.
CYND3010I: Select the JBoss server version
CYND3011I: Java Home
Explanation
The Java home directory that the application server instance uses.
CYND3012I: Java home directory name
Explanation
The Java home directory that the application server instance uses.
CYND3021I: JBoss Server Host
Explanation
JNDI host name or IP address of the target JBoss server.
CYND3022I: JNDI host name or IP address of the target JBoss
server
Explanation
JNDI host name or IP address of the target JBoss server.
CYND3023I: JBoss JNP service Port
Explanation
JNDI port of the target JBoss server.
CYND3024I: JNDI port of the target JBoss server
Explanation
JNDI port of the target JBoss server.
CYND3025I: JBoss Server User ID
Explanation
JDNI user of the target JBoss server (leave it blank if no user is defined.)
452
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND3026I: JDNI user of the target JBoss server
CYND3027I: JBoss Server Password
Explanation
JDNI password of the target JBoss server (leave it blank if no user is defined.)
CYND3028I: JDNI password of the target JBoss server
CYND3029I: JBoss Server Instance Names
Explanation
The list of JBoss server instance names (there should be only one name listed).
CYND3030I: JBoss Server Instance Names
Explanation
The list of JBoss server instance names (there should be only one name listed).
CYND3033I: JBoss Server Startup Script
Explanation
JBoss server startup script, normally will be run.bat/sh.
CYND3034I: JBoss server startup script, normally will be
run.bat/sh.
CYND3041I: JBoss Output Redirect File
Explanation
The file JBoss server's stdout will be redirected to.
CYND3042I: The file to which JBoss server's stdout will be
redirected.
CYND3057I: TEMA Port Number
Explanation
The port number to be used to communicate with Tivoli Enterprise Monitoring
Agent system.
CYND3058I: The TEMA port number can be found in
itcamdc/etc/kwjdc.properties.
Explanation
The port number to be used to communicate with Tivoli Enterprise Monitoring
Agent system.
Chapter 3. System Messages for ITCAM Agent for J2EE
453
CYND3059I: JVM GC Log
Explanation
The file is used to obtain the java GC log.
CYND3060I: JVM GC log is used to obtain the java GC log.
Explanation
The file is used to obtain the java GC log.
CYND3061I: JBoss Server Version.
Explanation
The JBoss server version supported by ITCAM for J2EE Data Collector.
CYND3071I: Enter the JBoss Server Information and Java
Home. JBoss Server Host is the host name of the machine
where JBoss is located. JBoss JNP service Port is the
listening port for the bootstrap JNP service of JBoss. Need to
input user/password? is only checked when security is
enabled. User ID and Password are used only when security
of JBoss is enabled. JBoss Server Home is the installation
directory of JBoss( e.g. C:/JBoss-4.0.3SP1). JBoss Server
Version is the major version of JBoss server. Java Home is
the JDK installation directory.
Explanation
SERVER_HOST/SERVER_PORT/SERVER_HOME/SERVER_VERSION/
JAVA_VERSION.
CYND3072I: Enter the startup script of JBoss Server . Startup
Script is full path of run.bat (on Windows) or run.sh (on
Linux/UNIX).
Explanation
JNDI info.
CYND3073I: Select the server that will be configured.
Explanation
Discovery results and selection
454
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND3081I: Use JDK as 64 bit?
CYND3082I: Use JDK as 64 bit?
CYND3083I: Use JDK as 64 bit?
CYND3091I: Need to input user/password?
CYND3092I: Need to input user/password?
CYND3093I: Need to input user/password?
CYND3094I: Validating Java home, Server Home, Server
version
CYND3095I: Validating JBoss Server Host name and JNP
service port
CYND3096I: Validating Startup Script
Explanation
Validating Startup Script and redirection file name.
CYND3097I: Retrieving Server information from JBoss Server
CYND4001I: DC for NetWeaver 2004
Explanation
Data Collector for NetWeaver Name.
CYND4001I: Data Collector Controller is listening at port
portNumber
Explanation
This is the RMI runtime listening port for the Data collector.
CYND4002I: DC for NetWeaver
Explanation
Data Collector for NetWeaver short name.
CYND4002I: After joining the Kernel, security manager is:
Securitymanager
Explanation
Data Collector uses the security manager from WebSphere if global security is
enabled, otherwise it is null.
Chapter 3. System Messages for ITCAM Agent for J2EE
455
CYND4003E: Failed to start controller.
Explanation
Controller failed to join Kernel.
Operator response
First, make sure Kernel is up and running. Second, make sure Data Collector
configuration (Kernel.Codebase, Java.Rmi.Server.Codebase) is specified properly.
CYND4003I: NetWeaver Server Type
Explanation
NetWeaver server type should be NetWeaver.
CYND4004I: Received notification of probe configuration
update: Probeconfig
Explanation
Kernel notified Data Collector that its configuration is updated.
CYND4004I: NetWeaver Server Type
Explanation
NetWeaver server type should be NetWeaver.
CYND4005E: Failed to allocate port to controller.
Explanation
RMI port for controller specified in Datacollector.Properties is in use.
Operator response
Specify an unused port.
CYND4005I: NetWeaver Server Version
Explanation
NetWeaver server version.
CYND4006I: NetWeaver Server 2004
Explanation
NetWeaver server version 2004.
456
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND4007I: Select the NetWeaver server version number
CYND4006I: Received notification that probe configuration
was removed.
Explanation
Kernel notified Data Collector that its configuration was removed.
CYND4007E: Failed to set monitoring level.
Explanation
Monitoring level have to be numerical.
Operator response
Enter only numbers for the monitoring level in the probe configuration.
CYND4008I: Java Home
Explanation
The Java home directory that the application server instance uses.
CYND4008I: Native Probe and JAVA-JNI threads successfully
started.
Explanation
The JNI thread for the native probe has started successfully
CYND4009I: Java home directory name
Explanation
The Java home directory that the application server instance uses.
CYND4009E: Java-JNI threads were not started.
Explanation
The probe controller failed to initialize the native probe.
Operator response
Restart the application server.
CYND4010E: Failed to start native probe.
Explanation
The configuration of the Data Collector is not set properly.
Operator response
Check the Installation Guide and make sure the proper configuration is set.
Chapter 3. System Messages for ITCAM Agent for J2EE
457
CYND4011I: You are trying to stop a Data Collector which was
not started successfully.
Explanation
If probe is not started successfully, ignore stop command.
CYND4012E: Failed to stop command agent.
Explanation
An internal error has occurred.
Operator response
Check trace log for more information.
CYND4013I: Probe Controller stopped successfully.
CYND4014E: Error occurred while stopping the probe.
Explanation
An internal error has occurred.
Operator response
Check the trace log for more information.
CYND4015W: Event agent is alive. Cannot start another event
agent.
Explanation
There have been two or more attempts to start the event agent.
Operator response
Restart the application server.
CYND4016W: Network agent is alive. Cannot start another
agent.
Explanation
There have been two or more attempts to start the network agent.
Operator response
Restart the application server.
CYND4017W: Publish Server status thread is alive. Cannot
start another agent.
Explanation
There have been two or more attempts to start the Publish Server agent.
458
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
Restart the application server.
CYND4018I: NetWeaver Server Host
Explanation
NetWeaver server's jndi host name or IP address.
CYND4018E: Failed to start Publish Server agent.
Explanation
An internal error has occurred.
Operator response
Check trace log for more details.
CYND4019E: Failed to stop Publish Server agent.
Explanation
An internal error has occurred.
Operator response
Check trace log for more details.
CYND4019I: NetWeaver server's jndi host name or IP address
CYND4020E: Failed to get sampling rate.
Explanation
The sampling rate contains a space or tab.
Operator response
Sampling rate should only contain digits.
CYND4020I: NetWeaver Server Port
Explanation
NetWeaver server's jndi port number.
CYND4021I: NetWeaver server port number
CYND4021I: Scheduler configuration is null for ID: Scheduleid
Explanation
The scheduler configuration is missing.
Chapter 3. System Messages for ITCAM Agent for J2EE
459
Operator response
Check Visualization Engine (VE) for Data Collector configuration.
CYND4022E: Failed to set scheduler configuration.
Explanation
Kernel failed to update scheduler configuration.
Operator response
Check trace log for more details.
CYND4022I: NetWeaver Server User ID
Explanation
NetWeaver server's jndi user ID.
CYND4023E: Failed to update scheduler configuration.
Explanation
Data Collector failed to parse the scheduler configuration.
Operator response
Check trace log for more details.
CYND4023I: NetWeaver Server Jndi User ID
Explanation
NetWeaver server jndi user ID, the user should be admin user.
CYND4024I: NetWeaver Server Password
Explanation
NetWeaver server's jndi password.
CYND4024I: Invalid monitoring level: Modlevel specified,
ignore the new monitoring value.
Explanation
An invalid monitoring level was specified. The Data Collector will ignore it.
CYND4025E: Failed to set new monitoring level.
Explanation
An internal error has occurred.
Operator response
Check trace log for more details.
460
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND4025I: NetWeaver Server Jndi User ID
Explanation
NetWeaver server jndi password.
CYND4026E: Failed to get default monitoring level.
Explanation
Kernel may be down.
Operator response
Verify that the Kernel is up and running.
CYND4026I: NetWeaver Server Instance Names
Explanation
The list of NetWeaver server instance names.
CYND4027I: Probe security is not enabled.
Explanation
Probe controller security is disabled. To enable the security, set the system property
'security.enabled'.
CYND4027I: The list of NetWeaver Server Instance names
CYND4028E: Error occurred when creating probe controller
loginstub.
Explanation
Probe controller failed to export object probe controller login.
Operator response
Check trace log for more details.
CYND4028I: Central Instance Installation
Explanation
Install Data Collector on Central instance.
CYND4029I: Probe security is enabled.
Explanation
Probe controller security is enabled.
Chapter 3. System Messages for ITCAM Agent for J2EE
461
CYND4029I: Local Dialog Instance Installation
Explanation
Dialog instance and central instance are on one machine and installation Data
Collector on dialog instance.
CYND4030E: The Am home path is not set. Set the system
property Am.Home for the Data Collector.
Explanation
The Installer failed to set this property.
Operator response
Check Application Server configuration. Verify that the Java system property
Am.Home is defined properly.
CYND4030I: Distributed Dialog Instance Installation
Explanation
Dialog instance and central instance are not on one machine and installation Data
Collector on dialog instance.
CYND4031E: An error occurred when setting up Cyanea
custom service.
Explanation
Initialization failed.
Operator response
Check trace log for more details.
CYND4031I: Netweaver DC installation type
Explanation
There are three types supported: Central instance installation, Local dialog instance
installation, Distributed dialog instance installation.
CYND4032E: Unable to join Kernel, retrying.
Explanation
The Kernel may be down.
Operator response
Verify the Kernel is up and running.
462
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND4032I: Central Instance Home
Explanation
Central Instance Home Directory, for example on Windows systems:
C:\\\\usr\\\\sap\\\\J2E\\\\JC00 or on UNIX systems: /usr/sap/J2E/JC00.
Operator response
Input this argument.
CYND4033E: Failed to start probe controller.
Explanation
The probe controller failed to join the Kernel.
Operator response
Check trace log for more details.
CYND4033I: Central Instance Home
Explanation
Central Instance Home Directory, for example on Windows systems:
C:\\\\usr\\\\sap\\\\J2E\\\\JC00 or on UNIX systems: /usr/sap/J2E/JC00.
CYND4034E: Unable to save monitoring level.
Explanation
Monitoring file does not have write permissions.
Operator response
Verify the this account has write permissions to the monitoring file.
CYND4034I: Server Home
Explanation
SAP Instance Home Directory, and the Data Collector will monitor applications
deployed on this instance, for example, on Windows systems:
C:\usr\sap\J2E\\JC00 or on UNIX systems: /usr/sap/J2E/JC00.
Operator response
Input this argument.
CYND4035E: Unable to find monitoring file:Modfile
Explanation
Monitoring file does not exist.
Operator response
Verify that Am.Home/Etc has read and write permissions.
Chapter 3. System Messages for ITCAM Agent for J2EE
463
CYND4035I: Server Home
Explanation
SAP Instance Home Directory, and the Data Collector will monitor applications
deployed on this instance, for example, on Windows systems:
C:\usr\sap\J2E\JC00 or on UNIX systems: /usr/sap/J2E/JC00.
CYND4036E: Unable to read monitoring file: Modfile
Explanation
Monitoring file does not have read permissions.
Operator response
Verify that Am.Home/Etc has read and write permissions.
CYND4036I: Central Instance Network Home
Explanation
The Central instance network home directory should be a local path mounted from
the central instance home directory.
Operator response
Input this argument.
CYND4037I: Central Instance Network Home
Explanation
The Central instance network home directory should be a local path mounted from
the central instance home directory.
CYND4037W: Unknown proxy host:Proxyhostname
Explanation
An incorrect Host name is specified for the property Proxy.Host in the
Datacollector.Properties file.
Operator response
Verify that the correct Host name is set for Proxy.Host.
CYND4038E: Unable to load Cyanea probe configuration file:
Probeconfigfile
Explanation
Datacollector.Properties is missing.
Operator response
Verify that the probe configuration fle exists and has read permissions.
464
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND4038I: Please select the installation type of Data
Collector for NetWeaver.
Explanation
Three Data Collector installation type are supported:
1. Central instance installation --- Install Data Collector on Central instance.
2. Local dialog instance installation --- Dialog instance and central instance are on
one machine and install Data Collector on dialog instance.
3. Distributed dialog instance installation --- Dialog instance and central instance
are not on one machine and install Data Collector on dialog instance.
CYND4039E: Error occurred while getting product version
number.
Explanation
The Version.Properties file is missing.
Operator response
Verify that Version.Properties is installed properly.
CYND4039I: DC will monitor the central instance. Server
Home: The absolute path of central instance home directory.
(e.g., '/usr/sap/J2E/JC00')
Explanation
Data Collector will monitor the central instance. Server Home: The absolute path of
central instance home directory. (e.g., '/usr/sap/J2E/JC00')
CYND4040E: Failed to load library: Libname
Explanation
The library path is not configured properly.
Operator response
Check the Data Collector Installation Guide and verify that the Library Path is
configured properly.
CYND4040I: Data Collector will monitor the local dialog
instance. Please enter server home and central instance
home. Server Home: The absolute path of local dialog
instance home directory.(e.g., '/usr/sap/J2E/J01'). Central
Instance Home: the absolute path of central instance home
directory.(e.g., '/usr/sap/J2E/JC00')
Explanation
Data Collector will monitor the local dialog instance. Enter server home and
central instance home. Server Home: The absolute path of local dialog instance
home directory.(e.g., '/usr/sap/J2E/J01') Central Instance Home: the absolute path
Chapter 3. System Messages for ITCAM Agent for J2EE
465
of central instance home directory.(e.g., '/usr/sap/J2E/JC00')
CYND4041I: DC will monitor the distributed dialog instance.
Please enter server home, central instance home and central
instance network home. Server Home: The absolute path of
distributed dialog instance home directory.(e.g.,
'/usr/sap/J2E/J01') Central Instance Home: The absolute path
of central instance home directory.(e.g., '/usr/sap/J2E/
JC00')Central Instance Network Home: A local path mounted
from central instance home directory.(e.g.,
'/mnt/usr/sap/J2E/JC00')
CYND4041I: Native custom service start notification issued
successfully.
Explanation
The native custom service for all the managers has started successfully.
CYND4042E: An error occurred in native custom service start.
Explanation
An internal error has occurred.
Operator response
Check Msg-Dc-Native.Log and Trace-Dc-Native.Log for more information.
CYND4042I: Please enter the information of NetWeaver for
Server Instances Discovery NetWeaver Server Host: the
qualified hostname of local machine.NetWeaver Server Port:
the P4 port of the SAP NetWeaver instance. NetWeaver Server
User ID and password: required in order to get JMX Data from
MBean Server. for example: Administrator/password
Explanation
Enter the following JNDI information:
v SAPNW64HOST: Central instance host or dialog instance host
v SAPNW64PORT: JNDI port number
v SAPNW64USER: JNDI user name
v
SAPNW64PSWD: Password for JNDI user
CYND4043I: Select monitoring instance
Explanation
Select which instance you want the Data Collector to monitor.
466
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND4043I: Setting probe Sampling Rate for monitoring level
(L0, L1, L2, L3):L0, L1, L2, L3, Usesystemdefault:
Issystemdefault
Explanation
Display the actual Sampling Rate for all monitoring levels.
CYND4044I: Enter Server Information
CYND4044I: Incorrect system default monitoring level:
Modlevel
Explanation
The monitoring level entered was out of range, therefore the settings will revert
back to the system default.
CYND4045I: Incorrect monitoring level: Modlevel
Explanation
The monitoring level entered was out of range, therefore the settings will revert
back to the system default.
CYND4046E: Unable to find monitoring file: Modfile
Explanation
This account may not have permissions to create a monitoring file at
Am.Home/Etc.
Operator response
Verify that Am.Home/Etc has read and write permission.
CYND4047I: Loaded the native library: libName
Explanation
The native library has loaded successfully.
CYND4048E: Failed to deserialize marshalled object.
Explanation
Some jars shared by both the Data Collector and Managing Server are out of sync.
Operator response
Verify that jars are synchronized between Managing Server and Data Collector.
CYND4049E: Failed to get the proxy server from Kernel.
Explanation
Proxy server may be down.
Chapter 3. System Messages for ITCAM Agent for J2EE
467
Operator response
Verify proxy server is up and running.
CYND4050E: An error occurred during the start of the proxy
task thread.
Explanation
Kernel may be down.
Operator response
Check trace log for more details.
CYND4051I: Join Proxy Server and Kernel successfully.
Service ID: serviceID, probeID
Explanation
The Probe controller has joined the Proxy Server and the Kernel successfully. The
Service ID identifies the Proxy Server, and the Probe ID identifies the Kernel.
CYND4052E: Failed to join Proxy Server and Kernel.
Explanation
Proxy Server may be down, or Kernel may be down.
Operator response
Check trace log for more details.
CYND4052I: Install 64bit DC
CYND4053E: Am Home is not defined, not initializing security
module.
Explanation
The Installer failed to install properly.
Operator response
Check the Installation Guide and verify Am.Home is configured properly.
CYND4053I: Install 64bit DC
Explanation
Install 64bit Data Collector, the default value is true
468
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND4054I: The Cyanea password file (Cyanea.Pswdfile) is
not defined.
Explanation
The property Cyanea.Pswsfile is not configured.
Operator response
Check the Data Collector Installation Guide and specify the properties file correctly.
CYND4054I: JVM GC Log
Explanation
The file that is used to obtain the java GC log.
CYND4055E: The password file: Pwdfile does not exist.
Explanation
The password file is missing.
Operator response
Verify the installation of the password file.
CYND4055I: JVM GC log that is used to obtain java GC log.
Explanation
The file that is used to obtain the java GC log.
CYND4056I: Notes: 1)On Windows platform, the path separator
should be '\\'; On UNIX/Linux platform, the path separator
should be '/'.2) Please also refer to the installation guide for
post-installation for additional configuration steps required.
Explanation
The file that is used to obtain the java GC log.
CYND4061E: Unable to start command agent.
Explanation
Failed to start command agent thread in Data Collector due to the specified error.
Operator response
Fix the specified error and restart the Application server.
CYND4062I: Command agent controller started at port.
Explanation
Command agent controller started successfully.
Chapter 3. System Messages for ITCAM Agent for J2EE
469
CYND4063I: Unable to obtain request information.
Explanation
An error occurred while trying to retrieve Http request information.
CYND4064W: Exception while reading the Java core file.
Explanation
An error occurred while trying to read the Java core file.
Operator response
It may be a file permissions error. Grant write permissions to the directory in
which the core file is written.
CYND4065E: An error occurred while sending Heap dump data
to the Publish Server.
Operator response
Verify that the Publish Server has started successfully, if no restart the Publish
Server.
CYND4066E: An error occurred while initializing JMX agent.
Operator response
Verify that the Application server has started successfully.
CYND4067E: An error occurred while creating object name:
Operator response
Verify that the Application server has started successfully.
CYND4068I: No Mbean object found of type: in process
Explanation
Mbean object of the specified type is not found on the server.
CYND4069E: An error occurred while creating Adminclient.
Operator response
Verify that the Application server has started successfully.
CYND4070E: An error occurred while querying for
configuration objects of type:
Explanation
An error occurred while querying for configuration objects.
Operator response
Verify that the Application server has started successfully.
470
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND4071E: An error occurred while querying for
configuration attributes:
Operator response
Verify that the Application server has started successfully.
CYND4072E: Deploymentmanager.Rmi.Port property is not set
in Datacollector.Properties.
Explanation
To collect System Resources information the Deploymentmgr.Rmi.Port property
needs to be set in Datacollector.Properties.
Operator response
Set Deploymentmgr.Rmi.Port Property in Datacollector.Properties and restart the
server.
CYND4073E: Deploymentmanager.Rmi.Host property is not set
in Datacollector.Properties.
Explanation
To collect System Resources information the Deploymentmgr.Rmi.Host property
needs to be set in Datacollector.Properties.
Operator response
Set Deploymentmgr.Rmi.Host property in Datacollector.Properties and restart the
server.
CYND4074E: Deploymentmanager.Rmi.Connection property is
not set in Datacollector.Properties.
Explanation
To collect System Resources information the Deploymentmgr.Rmi.Connection
property needs to be set in Datacollector.Properties.
Operator response
Set Deploymentmgr.Rmi.Connection property in Datacollector.Properties and
restart the server.
CYND4075E: Failed to create Adminservice.
Operator response
Verify that the Application server has started successfully.
CYND4076E: Server Mbean not found
Explanation
JMX agent is unable to locate server Mbean.
Chapter 3. System Messages for ITCAM Agent for J2EE
471
Operator response
Verify that the Application server has started successfully.
CYND4077E: Error while registering JMX client.
Operator response
Verify that the Application server has started successfully.
CYND4078E: Probeservice did not start successfully.
Explanation
An error occurred while starting probe services.
Operator response
Verify that the configuration parameters are correct.
CYND4079E: Error while retrieving PMI data for the:
component .
Explanation
Error while retrieving PMI data for the specified component.
Operator response
Verify that the configuration parameters are correct.
CYND5001I: DC for WebSphere Application Server Community
Edition
Explanation
Data Collector for WebSphere Community Edition Name
CYND5002I: DC for WebSphere CE
Explanation
Data Collector for WebSphere Community Edition short name
CYND5003I: WebSphere CE Server Home
Explanation
WebSphere Community Edition Server Home Directory, for example C:\Program
Files\IBM\WebSphere\AppServerCommunityEdition.
472
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND5004I: WebSphere CE Server Home Directory, for
example C:/Program Files/IBM/WebSphere/
AppServerCommunityEdition.
Explanation
The application cannot resolve the IP address of the computer on which it is
running.
CYND5005I: WebSphere CE Server Type
Explanation
The WebSphere Community Edition server type should be wasce.
CYND5006I: WebSphere CE Server Type
Explanation
The WebSphere Community Edition server type should be wasce
CYND5008I: 1.0.1
Explanation
WebSphere Community Edition server version 1.0
CYND5010I: Select the WebSphere Community Edition server
version number
CYND5011I: Java Home
Explanation
The Java home directory that the application server instance uses.
CYND5012I: Java home directory name
Explanation
The Java home directory that the application server instance uses.
CYND5023I: WebSphere CE RMI Port
Explanation
The RMI port of the target WebSphere Community Edition server.
CYND5024I: The RMI port of the target WebSphere CE server
CYND5025I: WebSphere CE User ID
Explanation
The user of the target WebSphere Community Edition server.
Chapter 3. System Messages for ITCAM Agent for J2EE
473
CYND5026I: The user of the target WebSphere CE server
CYND5027I: WebSphere CE Password
Explanation
The password of the target WebSphere Community Edition server.
CYND5028I: The password of the target WebSphere CE server
CYND5029I: WebSphere CE Server Instance Name
Explanation
The list of WebSphere Community Edition server instance name.
CYND5030I: WebSphere CE Server Instance Name
Explanation
The list of WebSphere Community Edition server instance name.
CYND5055I: TEMA Host Name
Explanation
The host name to be used to communicate with the Tivoli Enterprise Monitoring
Agent system.
CYND5056I: TEMA host name that can be found in
itcamdc/etc/kwjdc.properties.
Explanation
The host name to be used to communicate with the Tivoli Enterprise Monitoring
Agent system.
CYND5057I: TEMA Port Number
Explanation
The port number to be used to communicate with the Tivoli Enterprise Monitoring
Agent system.
CYND5058I: TEMA port number that can be found in
itcamdc/etc/kwjdc.properties.
Explanation
The port number that is used to communicate with the Tivoli Enterprise
Monitoring Agent system.
CYND5059I: JVM GC Log
Explanation
The file that is used to obtain the java GC log.
474
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND5060I: JVM GC log that is used to obtain java GC log.
Explanation
The file that is used to obtain the java GC log.
CYND5061I: WebSphere CE Server Version
Explanation
The WebSphere Community Edition server version supported by ITCAM for J2EE
Data Collector.
CYND5071I: Enter the WebSphere CE Home and Java Home.
WebSphere CE Server Home is the installation directory of
WebSphere CE( for example, C:/Program Files/IBM/WebSphere/
AppServerCommunityEdition ). WebSphere CE Server Version is
the major version of WebSphere CE server. Java Home is the
JDK installation directory used by WebSphere CE Server.
Explanation
SERVER_HOME/SERVER_VERSION/JAVA_VERSION.
CYND5072I: Enter the information for WebSphere CE Server
for server discovery and configuration. WebSphere CE RMI
Port is the listening port for the RMI service. User ID and
Password are the credentials used to access RMI service.
Explanation
JNDI info.
CYND5073I: Enter the server instance name. Server Instance
Name is the name of the server instance.
Explanation
Discovery results and selection.
CYND5237I: Using SSL server socket for component:
CommandAgent. All clients connecting to this component
MUST connect via SSL, else the client socket may hang till
the timeout expires. No user action is required.
Explanation
Command agent started successfully in SSL mode.
CYND5238E: [BCM] CtgCallBack Error Message:
Explanation
An error message was issued in CtgCallBack.
Chapter 3. System Messages for ITCAM Agent for J2EE
475
Operator response
Refer to the issued message, and contact IBM Support.
CYND5239I: ITCAM Product Mode: productmode
Explanation
Data collected by the data collector is limited by the product mode.
Operator response
Consult the license under which the ITCAM Managing Server is running.
CYND5240I: TCAM Product Mode changed to: productmode
Explanation
The data collector is now operating according to the specified product mode.
Operator response
Consult the license under which the ITCAM Managing Server is running.
CYND5241E: ITCAM Product Mode changed failed:
productmode
Explanation
The product mode is invalid or unsupported.
Operator response
Consult the license under which the ITCAM Managing Server is running.
CYND5242E: Data Collector could not connect to Publishing
Server.
Operator response
Check Publishing Server's status and Data Collector's configuration.
CYND5243E: Data Collector tried to connect to Publishing
Server numberOfTimes times, but failed.
Explanation
Data Collector could not connect to Publishing Server.
Operator response
Check Publishing Server's status and Data Collector's configuration.
CYND6000E: Exception occurred while parsing XML file.
Explanation
An error happened during xml file parsing.
476
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Operator response
Check the existence and validity of the xml file in question.
CYND6001E: Unexpected exception. Refer to the tracing log.
Explanation
No additional information is available for this message.
CYND6001I: Data Collector Controller is listening at port
portNumber
Explanation
This is the RMI runtime listening port for the Data collector.
Operator response
Consult the license under which the ITCAM Managing Server is running.
CYND6001I: Yes
CYND6001W: Returning original Server Socket in multiple
context mode, provider might not support this implementation
CYND6002E: ObjectName invalid format MalformedObjectNameException was produced.
CYND6002I: JMXConnectorServer was successfully initialized
CYND6002I: No
CYND6002W: Not pure secure mode: server trusted by subject
CYND6003E: Unable to load configuration file: Probeconfigfile
CYND6003I: PING request was processed.
CYND6003I: J2SE Server Home
Explanation
J2SE Application Home Directory, for example C:/MyJavaProgram
Operator response
Input this argument.
Chapter 3. System Messages for ITCAM Agent for J2EE
477
CYND6003W: Insecure mode: it is recommended to turn on
SSL
CYND6004E: GC logging is not enabled.
CYND6004I: Secure Socket Factory successfully initialized
CYND6003I: J2SE Server Home
Explanation
J2SE Application Home Directory, for example C:/MyJavaProgram
Operator response
Input this argument.
CYND6003I: J2SE Server Home
Explanation
J2SE Application Home Directory, for example C:/MyJavaProgram
Operator response
Input this argument.
CYND6005E: GC Log file name is not specified in JVM
parameters or in GCLogVariable
CYND6005I: Pure secure mode: using default trusted
managers
CYND6005I: Server Type
Explanation
Server type should be J2SE.
CYND6006E: Error during Regexp subsystem initialization.
Refer to the tracing log.
CYND6006I: J2SE Server Type
Explanation
J2SE server type should be J2SE.
478
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND6007E: KeyStore location or store password or key
password are not defined
CYND6008E: No SSL compatible server socket implementation
is available, if you are using JDK 1.3, download JSSE
extension and install it following JDK documentation
CYND6008I: J2SE Application Name
CYND6009E: Exception when initializing SSL parameters
CYND6009I: Fill this table with required parameters to connect
the embedded JMX Server.
Explanation
Fill this table with the required parameters to connect embedded JMX Server.
CYND6010E: Exception in the task. Refer to the tracing log.
CYND6010I: A name less then 50 char(s), no <space>\\/&*:
Explanation
A name less then 50 char(s), no <space>\\/&*:
CYND6011E: Cannot open the GC Log file: GCLogfile
CYND6011I: Java Home
Explanation
The Java home directory that the application server instance uses.
CYND6012I: Java home directory name
Explanation
The Java home directory that the J2SE application instance uses
CYND6021I: JMX Server Host
Explanation
JMX host name or IP address of the target J2SE server.
CYND6022I: JMX host name or IP address of the target J2SE
server
Explanation
JMX host name or IP address of the target J2SE application.
Chapter 3. System Messages for ITCAM Agent for J2EE
479
CYND6023I: JMX Server Port
Explanation
JMX port of the target J2SE application.
CYND6024I: JMX port of the target J2SE server
CYND6025I: JMX Server User ID
Explanation
The JMX user of the target J2SE application (leave it blank if no user is defined.)
CYND6026I: JMX user of the target J2SE application
CYND6027I: JMX Server Password
Explanation
The JMX password of the target J2SE application (leave it blank if no user is
defined.)
CYND6028I: JMX password of the target J2SE application
CYND6029I: J2SE Application Instance Name
CYND6030I: A name less then 50 char(s), no <space>\\/&*:
CYND6031I: GC Collector MBean was registered, object name:
objectName
CYND6031I: Replace the existing startup script
Explanation
Replace the existing startup script.
CYND6032E: JMXConnectorServer was not found.
CYND6032I: Generate sample script
CYND6033E: RequestAggregator was not found
CYND6033I: J2SE Application Startup Script
Explanation
J2SE application startup script normally will be run.bat/sh.
480
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND6033W: Skip the incomplete GC event.
CYND6034I: J2SE Application startup script.
CYND6035I: Is there an embedded JMX Server ? (Yes for JDK
1.5)
CYND6036I: Accessed by remote connection ?
CYND6037I: Enter the J2SE Application Information and Java
Home. J2SE Server Home is the J2SE application working
directory( e.g. C:/MyProg ). J2SE Application Name is the
application name in letter or number without space( e.g.
MyProg ). Java Home is java home that application uses( e.g.
C:/JDK14 ). J2SE Main Class is main class name( e.g.
com.myprog.Main ).
Explanation
J2SE Application Information
CYND6038I: Enter the J2SE Application JMX Information. Is
there an embedded JMX Server ? Answer Yes if there is
existing embedded JMX Server running with J2SE application
server(Yes for JDK1.5 ). Access by remote connection ?
Answer Yes if JMX Server is connected remotely(e.g. JDK1.5 is
connected locally, answer No.). JMX Server Host, JMX Server
Port, JMX Server User ID, JMX Server Password Required
JMX connection parameters for JMX Server which is
connected remotely.
Explanation
J2SE Application JMX Information
Chapter 3. System Messages for ITCAM Agent for J2EE
481
CYND6039I: Enter the J2SE Application Startup Information.
J2SE Application Instance Name is name of instance in letter
or number without space( e.g. MyProg1). Replace the existing
startup script : replace an existing startup script. J2SE
Application Startup Script is startup script path( e.g.
C:/MyProg/bin/start.bat ). Java Argument Macro is Macro
String to be replaced in startup script. Generate sample script
: dcstartup.sh or dcstartup.bat, used to launch the application
after Data Collector is configured. Script Path is the directory
for the sample startup script( e.g. C:/MyProg/bin ). JVM
Arguments is JVM options without main class name( e.g.
-Dvarible1=value1 ). Program Arguments is program
arguments after main class.
Explanation
J2SE Application Startup Information
CYND6043I: J2SE Main Class
Explanation
The J2SE Main Class, for example, com.mycompany.Main
CYND6044I: J2SE Main Class, for example,
com.mycompany.Main
Explanation
J2SE Main Class, for example, com.mycompany.Main
CYND6045I: JMX Server Embedded
CYND6046I: Remote Connection Parameters
CYND6047I: Java Argument Macro
CYND6048I: Name of the Java Argument Macro to be replaced
Explanation
The name of the Java Argument Macro to be replaced.
482
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND6051I: Script Path
CYND6051I: OS Info MBean was registered, object name:
objectName
CYND6052I: Script Path
CYND6053I: JVM Arguments
CYND6054I: JVM Arguments
CYND6055I: Program Arguments
CYND6056I: Program Arguments
CYND6057I: Use JDK as 64 bit?
CYND6058I: Use JDK as 64 bit?
CYND6059I: Use JDK as 64 bit?
CYND7001E: Error while creating a silent installation file {0}
Explanation
The migration tool was not able to create the silent options file used for
installation.
Operator response
Check the write permissions for the temporary directory.
CYND7001I: ITCAM Data Collector for Oracle Application
Server 9.0.3 / 10.1.2
Explanation
Data Collector for Oracle Application Server full name.
CYND7002E: Error during installation {0}
Explanation
An error occurred during the installation of ITCAM 6.1
Operator response
Refer to the log file for the error reason.
CYND7002I: DC for Oracle Application Server
Explanation
Data Collector for Oracle Application Server short name
Chapter 3. System Messages for ITCAM Agent for J2EE
483
CYND7003E: Error while the migration tool was backing up
the home directory {0}
Explanation
Migration tool was not able to back up the ITCAM 6.0 home directory
Operator response
Check the write permission for the ITCAM 6.0 home directory.
CYND7003I: Oracle Application Server Home
Explanation
Oracle Application Server Home Directory. For example: C:/OraHome_1.
Operator response
This parameter is mandatory and should be filled in with the correct installation
location.
CYND7004E: ISDataBase Access error {0}
Explanation
An internal InstallShield error occurred
Operator response
Restart the migration tool.
CYND7004I: Oracle Application Server Home Directory. For
example C:/OraHome_1.
CYND7005I: Oracle Application Server Type
Explanation
Oracle Application server type. The default value is oracle.
CYND7006E: Error while Loading properties {0}
Explanation
The silent options file was not loaded.
Operator response
Specify the correct silent options file.
CYND7006I: Oracle Application Server Type
Explanation
Oracle Application server type. The default value is oracle.
484
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND7007E: Error during migration {0}
Explanation
An error caused the Migration to fail.
Operator response
Refer to the log file for the error reason
CYND7008E: Wrong path to product: {0}
Explanation
The wrong path was specified to the ITCAM 6.0 home directory.
Operator response
Enter the correct path to the ITCAM 6.0 home directory.
CYND7008I: Oracle Application Server 9.0.3
CYND7009I: Oracle Application Server 10.1.2
CYND7010I: Select the Oracle Application Server version
number
CYND7010W: An error occurred while deleting the temporary
file.
CYND7011I: Java Home
Explanation
Java home directory that the application server instance uses.
CYND7012E: The CERT_PATH variable was not found
Explanation
The setenv.sh script does not set the CERT_PATH variable.
Operator response
Fix the setenv.sh script to set the CERT_PATH variable.
CYND7012I: Java home directory name
Explanation
Java home directory that the application server instance uses.
Chapter 3. System Messages for ITCAM Agent for J2EE
485
CYND7013E: An error occurred while uninstalling the
Visualization Engine: {0} {1}
Explanation
The uninstallation of the ITCAM 6.0 Visualization Engine failed.
Operator response
Refer to the log file for the error reason.
CYND7013I: Managing Server's AM Home
Explanation
The Managing Server's AM home parameter.
CYND7014E: CYANEA_HOME_OS variable was not found in
setenv.sh file
Explanation
The setenv.sh script does not set the CYANEA_HOME_OS variable.
Operator response
Fix the setenv.sh script to set the CYANEA_HOME_OS variable.
CYND7014I: Managing Server AM home directory
Explanation
The Managing Server's AM home parameter.
CYND7015E: Cannot read {0}
Explanation
The migration tool cannot read the specified file.
Operator response
Check the read permission for the file.
CYND7015I: Managing Server Kernel Host Name
Explanation
The Managing Server's kernel host name or IP address.
CYND7016E: Cannot write to file {0}
Explanation
The migration tool cannot write to the specified file.
Operator response
Check the write permission for the file.
486
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND7016I: The Managing Server kernel host name or IP
address
CYND7017I: Managing Server kernel Codebase Port
Explanation
The Managing Server's kernel codebase port number.
CYND7018I: The Managing Server kernel codebase port
number
CYND7019E: Certificates data or Certificate path is not correct
Explanation
The CERT_PATH variable in the setenv.sh script has an incorrect value.
Operator response
Fix the CERT_PATH variable in the setenv.sh script.
CYND7019I: Managing Server kernel RFS Port
Explanation
The Managing Server server's kernel RFS port number.
CYND7020I: The Managing Server kernel rfs port number
CYND7021E: Variable in ve.properties is not correct: {0}
Explanation
The specified variable has an incorrect value.
Operator response
Fix the variable in the ve.properties file.
CYND7023E: An error occurred while getting WebSphere
servers topology data: topology data is empty. Script output:
{0}
Explanation
An error occurred while getting the WebSphere servers topology data.
Operator response
Ensure that WebSphere application server information is entered correctly.
CYND7024E: File not found: {0}
Explanation
The migration tool cannot find the specified file.
Chapter 3. System Messages for ITCAM Agent for J2EE
487
Operator response
Check the write permission for the directory.
CYND7026E: An exception occurred while getting DB port and
server data from variable: {0}
Explanation
Operator response
Fix the JDBC_DRIVER_URL variable in setenv.sh script.
CYND7027E: Database type cannot be recognized. Error in
setenv.sh file data.
Explanation
The JDBC_DRIVER_URL variable in the setenv.sh script has an incorrect value.
Operator response
Fix the JDBC_DRIVER_URL variable in setenv.sh script.
CYND7029I: Oracle Application Server Instance Names
Explanation
The list of Oracle Application Server instance names.
CYND7031E: An error occurred while setting in IS database:
Explanation
An internal InstallShield error occurred.
Operator response
Restart the migration.
CYND7030I: The list of Oracle Application Server instance
names
CYND7031I: Oracle Application Server Process Management
XML
Explanation
The Oracle Application Server Process Management XML will normally be
opmn.xml.
488
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND7032I: Oracle Application Server startup script will
normally be opmn.exe/sh.
CYND7033E: An error occurred while restoring subfolders
Explanation
The migration tool was not able to restore ITCAM 6.0 directories.
Operator response
Restore ITCAM 6.0 from the backup directory manually
CYND7034E: Updating DB failed with exit code {0}
Explanation
An error occurred while updating the database.
Operator response
Ensure that the correct database parameters were specified and restart the
migration.
CYND7035E: An error occurred while executing: {0}. Error: {1}
Explanation
The error occurred during the external script execution.
Operator response
Refer to the log file for the error reason.
CYND7035I: TEMA Host Name
Explanation
The host name be used to communicate with the Tivoli Enterprise Monitoring
Agent system.
CYND7036E: The error occurred while uninstalling the
Visualization Engine: {0}
Explanation
The error occurred while uninstalling the ITCAM 6.0 Visualization Engine.
Operator response
Refer to the log file for the error reason.
Chapter 3. System Messages for ITCAM Agent for J2EE
489
CYND7036I: TEMA host name can be found in
itcamdc/etc/kwjdc.properties.
Explanation
The host name to be used to communicate with the Tivoli Enterprise Monitoring
Agent system.
CYND7037E: Incorrect Managing Server host name: {0}. A fully
qualified host name should be provided.
Explanation
The specified Managing Server host name is not correct. It cannot be an IP address
or host name that cannot be resolved.
Operator response
Specify the fully qualified host name and click the Retry button.
CYND7037I: TEMA Port Number
Explanation
The port number to be used to communicate with the Tivoli Enterprise Monitoring
Agent system.
CYND7038E: WAS_home variable is not defined
Explanation
The setenv.sh script does not set the WAS_home variable.
Operator response
Fix the setenv.sh script to set the WAS_home variable.
CYND7038I: TEMA port number can be found in
itcamdc/etc/kwjdc.properties.
Explanation
The port number to be used to communicate with the Tivoli Enterprise Monitoring
Agent system.
CYND7039E: The error occurred while running the script for
uninstalling the Visualization Engine. {0} {1}
Explanation
The specified error occurred while running the script for uninstalling ITCAM 6.0
Visualization Engine.
Operator response
Refer to the log file for the error reason.
490
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND7039I: JVM GC Log
Explanation
The file is used to obtain the java GC log.
CYND7040E: An error occurred while getting profiles
Explanation
The migration tool was not able to get the list of WebSphere Application Server
profiles.
Operator response
Refer to the log file for the error reason.
CYND7040I: JVM GC log is used to obtain java GC log.
Explanation
The file is used to obtain the java GC log.
CYND7041E: Variable app.install.path is not defined or could
not read the file
Explanation
The ve.properties file is not readable or has an incorrect app.install.path property.
Operator response
Ensure that the ve.properties file exists and has the app.install.path property
defined.
CYND7042E: Not WebSphere 6, profile not foun
Explanation
The migration tool was not able to get the profile name from app.install.path
property defined in the ve.properties file.
Operator response
Ensure that the ve.properties file has the app.install.path property defined correctly.
CYND7045E: An error occurred while getting the profile home
dir: the profile name is not defined
Explanation
The migration tool obtained an empty profile name.
Operator response
Ensure that the WebSphere Application Server is installed correctly.
Chapter 3. System Messages for ITCAM Agent for J2EE
491
CYND7047I: Starting installation ...
Explanation
No additional information is available for this message.
CYND7048E: An error occurred while getting WAS version
data. Error code: {0}
Explanation
The migration tool was not able to parse the versionInfo script output.
Operator response
Refer to the log file for the error reason
CYND7056E: Installation file not found: {0}
Explanation
The migration tool was not able to run the ITCAM 6.1 installation.
Operator response
Ensure that the installation image was copied to the disk correctly and restart the
migration.
CYND7057E: Migration failed: {0}
Explanation
The migration tool finished unsuccessfully because of the error indicated
Operator response
Refer to the log file for the error reason.
CYND7059E: The path to the product is empty.
Explanation
An empty path was specified to the ITCAM 6.0 home directory.
Operator response
Enter the correct path to the ITCAM 6.0 home directory.
CYND7060E: Unsuccessful exit code
Explanation
Silent installation of the ITCAM 6.1 finished unsuccessfully.
Operator response
Refer to the log file for the error reason.
492
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND7060I: Enter Oracle Server Information and Java Home.
Oracle Application Server Home is the installation directory of
Oracle( e.g. C:/OraHome_1 ). Oracle Server Version is the
major version of Oracle server. Java Home is the JDK
installation directory. JVM GC Log is the gc log file of JVM.
For Oracle10g it can be specified freely; for Oracle9i, it should
be the log file(under $OracleHome/opmn/logs) of the OC4J
instance to be configured.
Explanation
Select the Oracle application server home directory, version and jdk home.
CYND7061E: The directory '{0}' is in use
Explanation
Another process is using the specified directory.
Operator response
End all programs that are using the ITCAM 6.0 home directory and click the Retry
button.
CYND7061I: Select an oracle application server instance to
configure/unconfigure.
CYND7062I: Install DC for 64bit JVM
CYND7062I: Directory is in use or does not exist
Explanation
No additional information is available for this message.
CYND7063I: Install DC for 64bit JVM
Explanation
Install Data Collector for 64bit JVM, the default value is true
CYND7063E: Aborted by user
CYND7064I: Starting migration.
CYND7064I: Oracle Server Version.
Explanation
Oracle server version supported by ITCAM for J2EE Data Collector.
Chapter 3. System Messages for ITCAM Agent for J2EE
493
CYND7065I: Generating silent file
CYND7066I: Uninstalling Visual Engine
CYND7069I: Removing backup directory
CYND7070I: Executing script to update DB: {0}
CYND7071I: Migration successfully finished
CYND7072I: Folders successfully restored
CYND7073I: DB update not selected
CYND7074I: WAS version = 5, do not uninstall the
Visualization Engine
CYND7077I: An error occurred while executing: {0}.
Arguments: {1}
CYND7079I: An error occurred: KEYSTR_LOC variable not
defined
CYND7080I: The file deleted successfully {0}
CYND7081W: The file deletion failed {0}
CYND7082I: The folders backed up successfully.
CYND7083I: The command executed successfully.
CYND7084I: The Visualization Engine uninstalled successfully
CYND7086I: Backup directory name: {0}
CYND7115I: Execute the command: {0}
CYND7116I: Command Done
CYND7120I: Timeout occurred while executing the process:
{0}
CYND7124I: Starting migration of server: {0}
CYND7126I: Server was migrated: {0}
CYND7137I: Selected profile: {0}, profile home: {1}
494
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYND7138I: Visualization Engine installation not selected
CYND7140I: Backing up folders to: {0}
CYND7141I: Uninstalling the Visualization Engine: WAS
version == 6
CYND7142I: Deleting
CYND7145I: Copying keys and certificates files to standard
install location...
CYND7148I: Installation finished with exit code: {0}
CYND7157I: Setting +x mode to db2update.sh: {0}
CYND7159I: Upgrading DB finished with exit code {0}
CYND7161I: Copying file {0}
CYND7163I: Executing command: {0}
CYNOAS Messages: Oracle
The following messages are related to Oracle. All such messages have IDs in the
range CYNOAS0000 to CYNOAS0999.
CYNOAS001I: oc4j.jar does not exist.
Operator response
Ensure that Oracle is installed correctly and ORACLE_HOME is the right
installation directory.
CYNOAS002I: opmn.xml does not exist.
Operator response
Ensure that Oracle is installed correctly and opmn.xml is under
ORACLE_HOME/opmn/conf
CYNOAS003I: server.xml does not exist for the selected server
instance.
Operator response
Ensure that the server instance you have chosen to install Data Collector in exists.
CYNOAS004I: The server version is not correct.
Operator response
Ensure that the Oracle server version you selected is correct.
Chapter 3. System Messages for ITCAM Agent for J2EE
495
CYNOAS005I: The oracle instance has already been
configured.
Operator response
Ensure that the oracle instance you selected has not been configured before.
CYNOAS006I: The oracle instance has not been configured
yet.
Operator response
Ensure that the oracle instance you selected has been configured before.
CYNOAS007I: The directory of TEMA log file not exists
Operator response
Ensure that the directory of Tivoli Enterprise Monitoring Agent log file exists.
CYNWLC Messages: JBoss
The messages below are related to JBoss. All such messages have IDs in the range
CYNWLC0000 to CYNWLC0999.
CYNWLC001D: Cannot connect to the JBoss server. Check
your environment and server settings.
Operator response
Contact IBM Software Support.
CYNWLC002D: Incorrect UserID/Password.
Operator response
Contact IBM Software Support.
CYNWLC003D: Cannot connect to the JBoss server. Check
the host and port.
Operator response
Contact IBM Software Support.
CYNWLC004D: The directory of redirect file does not exist.
Check the directory.
Operator response
Contact IBM Software Support.
CYNWLC005D: This is not a valid JBoss server directory.
Check the directory that was specified.
Operator response
Contact IBM Software Support.
496
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNWLC006D: The UserID/Password of the JBoss server is
not correct. Check the parameters that were specified.
Operator response
Contact IBM Software Support.
CYNWLC007D: Cannot connect to the JBoss server. Make
sure that the JBoss is running or check whether the Server
Host/Port specified are correct.
Operator response
Contact IBM Software Support.
CYNWLC008D: The JBoss version that you selected is not
correct!
Operator response
Contact IBM Software Support.
CYNWLC009D: The Server instance you selected is not
configured!
Operator response
Contact IBM Software Support.
CYNWLC010D: The Server instance you selected has already
been configured by another DC!\n Please unconfigure that DC
first.
Operator response
Contact IBM Software Support.
CYNWLC011D: The Startup Script you inputed is not the right
script that start up the running JBoss!\n Please correct the
Startup Script you Inputed.
Operator response
Contact IBM Software Support.
CYNWLC012D: JAVA HOME that the running JBoss Server
used is not the one you inputed!\n Please correct the JAVA
HOME you inputed.
Operator response
Contact IBM Software Support.
Chapter 3. System Messages for ITCAM Agent for J2EE
497
CYNWLC013D: The Server Home you inputed is not the Server
Home of running JBoss!\n Please correct the Server Home
you inputed.
Operator response
Contact IBM Software Support.
CYNWLC014D: Need RTT Fixpack for the RTT you installed to
this JBoss server!
Operator response
Contact IBM Software Support.
CYNWLC015D: The path of GC Log does not exist!\n Please
correct the GC log you inputed.
Operator response
Contact IBM Software Support.
CYNPE Messages:Request Aggregator
The following messages are related to request aggregator. All such messages have
IDs in the range CYNPE0000 to CYNPE0999.
498
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNPE0001I: Generic Probe Engine Runtime Environment is
now initialized.
CYNPE0002I: Generic Probe Engine initialized startup class
StartupClass.
CYNPE0003I: Generic Probe Engine shutdown initiated.
CYNPE0004I: Generic Probe Engine initialized runtime
component RuntimeComponent class.RuntimeClass.
CYNPE0005I: MBean Manager has been initialized.
CYNPE0006I: MBean Manager registered MBean ObjectName.
CYNPE0007I: MBean Manager loaded the registration engine
RegistrationEngine.
CYNPE0008E: XML parsing error occurred: errorType parsing
file fileName.
CYNPE0009E: Aspect definition aspectName is defined with
abstract pointcut pointcutName but has no concretizePointcut
definition.
CYNPE0010I: MBean manager created MBean server with
class MBeanServerClass and default domain name
domainName.
CYNPE0011E: MBean manager was unable to create MBean
server with class MBeanServerClass and default domain name
domainName.
CYNX Messages: Installation
The following messages occur during installation. All such messages have IDs in
the range CYNX0000 to CYNX9999.
CYNX0001E: There were usage errors, where a number of
arguments were incorrect for the following: java
UserInputsFilePath, ConfigurationTemplatesPath, and
DestinationPath.
Explanation
UserInputsFilePath is the user inputs properties file with a fully qualified path.
ConfigurationTemplatesPath is the specify directory. DestinationPath is where the
concrete configuration files are to be copied.
Chapter 3. System Messages for ITCAM Agent for J2EE
499
Operator response
Pass the correct number of arguments.
CYNX0002E: Configuration template was not found. The
concrete configuration XML file could not be created.
Explanation
The concrete configuration XML file cannot be generated due to the missing
template file in a specific directory.
Operator response
Provide the correct template. If the specific type is not supported, you can fall back
to a lower application server version.
CYNX0003E: A configuration template cannot be found for the
following application server versions: . The concrete
configuration XML file could not be created.
Explanation
The concrete configuration XML file cannot be generated due to a missing template
file in a specific directory.
Operator response
Provide the correct template. If the specific type is not supported, you can fall back
to a lower application server version.
CYNX0004E: The concrete configuration XML file could not be
generated due to missing values in the dcInputs.txt file.
Explanation
One more more values such as APPSERVER or APPSERVER_VERSION are missing
from the dcInputs.txt file.
Operator response
Correct the dcInputs.txt value. Provide all the necessary information and rerun the
installer.
CYNX0005I: The concrete configuration file was generated
successfully.
Explanation
The Generate Config module generated the concrete configuration XML file which
will be used to apply configuration to the specific application server.
500
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
CYNX0006E: The value for the variable was not found in the
userInputs file. This variable was not replaced in file .
Explanation
Some values are missing in the userInputs file. Substitution for these variables
could not be done successfully.
Operator response
Specify the correct values for all the necessary variables in the userInputs file. If
you do not, then manually edit the destination file and specify the values for these
variables.
CYNX0007E: File cannot be modified successfully and copied
to the file .
Explanation
One or more variables could not be substituted successfully. Their values could not
be found in a property file.
Operator response
Specify the correct values for all the necessary variables in the userInputs file. If
you do not, then manually edit the destination file and specify the values for these
variables.
CYNX0008E: The system could not load the property file
successfully.
Explanation
The system failed to load or read the property file due to a missing file or wrong
permissions.
Operator response
The property file might not exist or might not be accessible. Make sure that the file
exists and it has read permission.
CYNX0009E: One or more -Xrun JVM arguments were found
for the server . Configuration is skipped for server .
Explanation
The -Xrun argument is found in the server's JVM arguments. The Data Collector
cannot be installed on already existing JVM profiles.
Operator response
Disable all the other JVM profiles and rerun the installer.
Chapter 3. System Messages for ITCAM Agent for J2EE
501
CYNX0010E: The system failed to get the backup of the
current application server configuration.
Operator response
Use the application server backup utility to back up the configuration manually
before running the installer.
CYNX0011E: The system failed to set .
Explanation
One or more errors occurred while applying the configuration.
Operator response
Refer to the installation guide and apply the configuration manually.
CYNX0012E: The system failed to save and commit the newly
applied configuration.
Operator response
Refer to the installation guide and apply the configuration manually.
CYNX0013E: The system failed to create the post-installation
instruction file for the WebLogic unmanaged application
server.
Operator response
Refer to the installation guide and apply the configuration manually.
502
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Chapter 4. System Messages for ITCAM Agent for HTTP
Servers
KHT messages
The Tivoli Enterprise Monitoring Agent produces errors messages with IDs in the
range KHTC0000 to KHTC0016, KHTA0000, KHTH0001 to KHTH0003, and
KHTS0011; these are described below and in the following pages.
KHTC0000I: Configurator messages
Explanation
The message shows the title of the post-configuration dialog.
KHTC0001I: Ok
Explanation
The message shows the text of the OK button.
KHTC0002E: Error: There are no -C options. It is necessary to
specify a home path.
Explanation
-C option is missing from the PreProcess property in the khtcma.ini file.
User response
Reinstall the agent.
KHTC0003E: Unexpected exception {0}. Refer to trace log.
Explanation
Exception was raised during the configuration of the Apache server.
User response
Review the trace log for detailed information and resolve the problem.
KHTC0006E: Error: Unable to determine version of Apache
runtime specified by home path {0}
Explanation
Unable to determine the Apache version.
User response
Check whether the Apache control command returns proper version and resolve
the problem.
© Copyright IBM Corp. 2007, 2010
503
KHTC0008W: Warning: {0} is already configured.
Explanation
The specified Apache server is already configured for monitoring.
KHTC0010I: Info: {0} was configured.
Explanation
The Apache server is successfully configured for monitoring.
KHTC0011E: Error: {0} file was not found.
Explanation
Configuration or executable file as specified on the configuration dialog is not
found.
User response
Run the agent configuration again and specify correct configuration file and
executable file.
KHTC0012W: Warning: {0} is not configured.
Explanation
During the unconfiguration of the Apache monitoring module, it was found that
the module was not configured.
KHTC0013I: Info: {0} was unconfigured.
Explanation
The monitoring module was successfully removed from the Apache server during
configuration.
KHTC0015E: Error: 64-bit Apache module for Windows is not
provided.
Explanation
On Windows systems, the 64-bit Apache server is not supported.
User response
Install the supported version of the Apache server.
KHTC0016E: Error: Unable to find required module: {0}
Explanation
The directory where ITCAM for Application Diagnostics - Tivoli Enterprise
Monitoring Agent Apache modules are stored was not found.
User response
Reinstall the agent.
504
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
KHTA0000I: Composite Application Manager monitoring agent
startup complete.
Explanation
The Tivoli Enterprise Monitoring Agent has successfully completed initialization.
KHTH0001I: Apache WebServer {0} was successful.
Explanation
Action carried out on Apache Web Server was finished successfully.
KHTH0002E: Apache WebServer {0} failed with error code {1}.
Explanation
Action carried out on Apache Web Server failed.
User response
Collect the agent log, and contact IBM support.
KHTH0003E: Unexpected exception: {0}, refer to trace log.
Explanation
A program exception has occurred in the Apache monitoring module. The variable
in the message indicates the type of exception.
User response
Collect the agent log, and contact IBM support.
KHTS0011W: SNMP info for Sun Web Server isn't available,
check Sun Web Server SNMP agent configuration.
Explanation
SNMP info for Sun Web Server isn't available, check Sun Web Server SNMP agent
configuration.
User response
If you have Sun Web Server installed check if it was configured properly for SNMP
monitoring.
Chapter 4. System Messages for ITCAM Agent for HTTP Servers
505
506
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Appendix A. Accessibility
Accessibility features help a user who has a physical disability, such as restricted
mobility or limited vision, to use software products successfully. These are the
major accessibility features you can use with IBM Tivoli Composite Application
Manager when accessing it on the IBM Personal Communications terminal emulator:
v You can operate all features using the keyboard instead of the mouse.
v You can read text through interaction with assistive technology.
v You can use system settings for font, size, and color for all user interface
controls.
v You can magnify what is displayed on your screen.
For more information about viewing PDFs from Adobe, go to the following web
site: http://www.adobe.com/enterprise/accessibility/main.html
© Copyright IBM Corp. 2007, 2010
507
508
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Appendix B. Support information
This section describes the following options for obtaining support for IBM
products.
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.
Finding Release Notes
You can find Release Note information online by viewing IBM Technotes.
Technotes are short documents that cover a single topic. You can search the
Technote collection for common problems and solutions, as well as known
limitations and workarounds. Technotes are continuously updated to provide
current product information.
You can search for Technotes and subscribe to have future Technotes e-mailed to
you, as described below. Alternatively, you can watch demonstrations of these
procedures at the following Web site: http://www-306.ibm.com/software/
support/sitetours.html
Finding Technotes
Perform the following actions to access Technotes for this product:
1. Launch the IBM Software Support Web site: http://www.ibm.com/software/
support
2. Follow the instructions on the screen to search for the Technotes related to the
issue encountered.
Subscribing to new Technotes
You can subscribe to an RSS feed of the product support page or subscribe to
receive e-mail notification about product tips and newly published fixes through
My support. To subscribe to an RSS news feed of the product support page, click
the orange RSS button under the Stay up to date pane.
My Support is a personalized portal that enables you to:
v Specify the products for which you want to receive notifications
v Create a personalized page that provides product information for the products
you use
v Choose from flashes, downloads, and Technotes
v Receive an e-mail update in your inbox
Perform the following actions to subscribe to My Support e-mails:
1. Launch an IBM support Web site, such as the following site:
http://www.ibm.com/support/us/
2. Click My support in the upper-right corner of the page.
3. If you have not yet registered, click register in the upper-right corner of the
support page to create your user ID and password.
4. Sign in to My support.
© Copyright IBM Corp. 2007, 2010
509
5. On the My support page, click Add products.
6. Make the following selections from the lists to add this product to your
personal page:
a. Software
b. Systems Management
c. Application Performance & Availability
7. Click Add products.
8. Click Subscribe to email.
9. Set your preferences to specify the information you want in your e-mails.
10. Click Update.
11. Click Submit.
Tivoli Support Technical Exchange
You can become a participant in the new Tivoli Support Technical Exchange, where
you can expand your technical understanding of your current Tivoli products in a
convenient format hosted by Tivoli support engineers. This program provides
support discussions about product information, troubleshooting tips, common
issues, problem solving resources, and other topics. As Exchange leaders, Tivoli
engineers provide subject matter expert direction and value. Participating in the
Exchange helps you manage your Tivoli products with increased effectiveness.
What do you do to participate? Review the schedule of Exchange sessions. Find a
topic of interest and select register. Provide your name, phone number, company
name, number of attendees, the Exchange Topic, and IBM Customer number. You
will be invited to attend a one to two hour conference call where the information is
presented. The new Tivoli Support Technical Exchange can help with the following
areas:
v Increased product knowledge
v Ways to avoid common pitfalls
v Support recommendations
v Proactive customer support
v Helpful hints and tips
v Knowledge transfer
v Expansion of your knowledge base
For more information or to suggest a future Exchange session, contact Support
Technical Exchange ([email protected]). To learn more, visit the following Web
site: http://www-306.ibm.com/software/sysmgmt/products/support/
supp_tech_exch.html
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. You can use the search function of this
information center to query conceptual information, instructions for completing
tasks, reference information, and support documents.
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
510
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
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 Google
Obtaining fixes
A product fix might be available to resolve your problem. To determine what fixes
are available for your IBM software product, follow these steps:
1. Go to the IBM Software Support Web site at http://www.ibm.com/software/
support
2. Click Drivers in the Related support section.
3. In the Products of IBM section, select one software category from the Category
list.
4. Select one product from the Sub-category list.
5. Use the Search within results field if you want to refine your search.
6. Click Search.
7. From the list of downloads returned by your search, click the name of a fix to
read the description of the fix and to optionally download the fix.
For more information about the types of fixes that are available, see the IBM
Software Support Handbook at http://techsupport.services.ibm.com/guides/
handbook.html
Receiving weekly support updates
To receive weekly e-mail notifications about fixes and other software support news,
follow these steps:
1. Go to the IBM Software Support Web site at http://www.ibm.com/software/
support
2. Click My support in the upper right corner of the page.
3. If you have already registered for My support, sign in and skip to the next
step. If you have not registered, click Register now. Complete the registration
form using your e-mail address as your IBM ID and click Submit.
4. Click Edit profile.
5. In the Products list, select Software. A second list is displayed.
6. In the second list, select a product segment, for example, Application servers.
A third list is displayed.
7. In the third list, select a product subset, for example, Distributed Application
& Web Servers. A list of applicable products is displayed.
8. Select the products for which you want to receive updates, for example, IBM
HTTP Server and WebSphere Application Server.
9. Click Add products.
10. After selecting all products that are of interest to you, click Subscribe to
e-mail on the Edit profile tab.
11. Select Please send these documents by weekly e-mail.
Appendix B. Support information
511
12.
13.
14.
15.
Update your e-mail address as needed.
In the Documents list, select Software.
Select the types of documents that you want to receive information about.
Click Update.
If you experience problems with the My support feature, you can obtain help in
one of the following ways:
Online
Send an e-mail message to [email protected], describing your problem.
By phone
Call 1-800-IBM-4You (1-800-426-4968).
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 site: http://www.ibm.com/
software/passportadvantage Then 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).
v For IBM eServer™ software products (including, but not limited to, DB2 and
WebSphere products that run in zSeries, pSeries®, and iSeries® environments),
you can purchase a software maintenance agreement by working directly with
an IBM sales representative or an IBM Business Partner. For more information
about support for eServer software products, go to the IBM Technical Support
Advantage Web page (http://www.ibm.com/servers/eserver/techsupport.html)
If you are not sure what type of software maintenance contract you need, call
1-800-IBMSERV (1-800-426-7378) in the United States or, from other countries, go to
the contacts page of the 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 these steps when contacting 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:
512
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Table 5. Severity Level
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 by going 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.
If the problem you submit is for a software defect or for missing or inaccurate
documentation, IBM Software Support creates an Authorized Program Analysis
Report (APAR). The APAR describes the problem in detail. Whenever possible,
IBM Software Support provides a workaround for you to implement until the
APAR is resolved and a fix is delivered. IBM publishes resolved APARs on the
IBM product support Web pages daily, so that other users who experience the
same problem can benefit from the same resolutions.
Appendix B. Support information
513
514
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Index
A
Abstract Configurator messages 409
accessibility lii, 507
Application Monitor messages 28, 303
Archive Agent messages 23
B
books xlix
see publications li
Byte Code Modification messages
36
information centers, searching to find
software problem resolution 510
Install ISA and MDD for Java 20
installation messages 40, 388
Installation messages 499
Internet, searching to find software
problem resolution 510
ISA
Download plug-in 5
Plug-in 5, 9
J
J2EE Agent messages
JBoss messages 496
C
Change
Log level 10
Collector log files and system information
Plug-in 5
Common Services Address Space
messages 292
conventions
typeface lii
customer support 512
D
Data Access Messages 391
Data Collector messages 156, 399, 418
Direct JVM invocation 12
disability 507
Download plug-in
IBM Support Assistant 5
E
education
see Tivoli technical training
Environment Checking 18
lii
409
K
Kernel messages 253
KHT messages 503
knowledge bases, searching to find
software problem resolution 509
KYJ messages 409
KYNA messages 394
KYND messages 399
KYNX messages 404
L
log file utilities
First Failure Data Capture 6, 9
Gather Script 1
LogViewer 11
Log files and Utilities
Environment Checking Utility 18
Log level
Change 10
LogViewer 11
Start 11
F
M
Filter predicate
Specify 14
First Failure Data Capture
fixes, obtaining 511
manuals xlix
see publications li
Memory Dump Diagnostic for Java with
IBM Support Assistant 20
Message Dispatcher messages 263
6, 9
G
Gather Script 1
Running procedures 6
Global Publish Server messages
O
218
I
IBM Support Assistant
Download plug-in 5
Plug-in 5, 9
© Copyright IBM Corp. 2007, 2010
online publications
accessing li
Oracle messages 495
ordering publications lii
P
Plug-in
Collect log files and system
information 5
IBM Support Assistant 5, 9
Polling Agent messages 387
Port Consolidator messages 286
problem determination
describing problem for IBM Software
Support 513
determining business impact for IBM
Software Support 512
submitting problem to IBM Software
Support 513
Procedures
Run Gather Script 6
publications xlix
accessing online li
ordering lii
Publish Server messages 249, 267
Q
Query string
Specify 13
R
reader requirements xlix
Release Notes, finding 509
Request Aggregator messages 498
requirements for readers xlix
S
SAP NetWeaver config toolkit
messages 413
Software Support
contacting 512
describing problem for IBM Software
Support 513
determining business impact for IBM
Software Support 512
submitting problem to IBM Software
Support 513
Specify
Filter predicate 14
Query string 13
Start
LogViewer 11
support updates, e-mail notifications 511
T
Technotes
e-mail notifications 509
viewing 509
Tivoli Enterprise Tivoli Enterprise
Monitoring Agent messages 394
515
Tivoli Information Center li
Tivoli Support Technical Exchange
Tivoli technical training lii
training, Tivoli technical lii
typeface conventions lii
510
V
Variables for directories
liii
W
Web Services messages 386
WebLogic messages 417
WebSphere Application Server
Community Edition messages 416
WebSphere Extended Deployment Agent
messages 404
Wrapper script 11
516
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of
International Business Machines Corp., registered in many jurisdictions worldwide.
Other product and service names might be trademarks of IBM or other companies.
A current list of IBM trademarks is available on the Web at “Copyright and
trademark information” at www.ibm.com/legal/copytrade.shtml.
Adobe is either a registered trademark or a trademark of Adobe Systems
Incorporated in the United States, other countries, or both.
Linux is a registered trademark of Linus Torvalds in the United States, other
countries, or both.
Microsoft and Windows are trademarks of Microsoft Corporation in the United
States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other
countries.
Java and all Java-based trademarks are trademarks or registered trademarks
of Oracle and/or its affiliates.
Other company, product, and service names may be trademarks or service marks
of others.
© Copyright IBM Corp. 2007, 2010
517
518
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Notices
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in
other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user's responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not give you
any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785 U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM
Intellectual Property Department in your country or send inquiries, in writing, to:
Intellectual Property Licensing
Legal and Intellectual Property Law
IBM Japan Ltd.
1623-14, Shimotsuruma, Yamato-shi
Kanagawa 242-8502 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. 2007, 2010
519
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.
Any performance data contained herein was determined in a controlled
environment. Therefore, the results obtained in other operating environments may
vary significantly. Some measurements may have been made on development-level
systems and there is no guarantee that these measurements will be the same on
generally available systems. Furthermore, some measurement may have been
estimated through extrapolation. Actual results may vary. Users of this document
should verify the applicable data for their specific environment.
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.
All statements regarding IBM's future direction or intent are subject to change or
withdrawal without notice, and represent goals and objectives only.
All IBM prices shown are IBM's suggested retail prices, are current and are subject
to change without notice. Dealer prices may vary.
This information is for planning purposes only. The information herein is subject to
change before the products described become available.
This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which
illustrate programming techniques on various operating platforms. You may copy,
modify, and distribute these sample programs in any form without payment to
520
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
IBM, for the purposes of developing, using, marketing or distributing application
programs conforming to the application programming interface for the operating
platform for which the sample programs are written. These examples have not
been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or
imply reliability, serviceability, or function of these programs. You may copy,
modify, and distribute these sample programs in any form without payment to
IBM for the purposes of developing, using, marketing, or distributing application
programs conforming to IBM‘s application programming interfaces.
Each copy or any portion of these sample programs or any derivative work, must
include a copyright notice as follows:
© (your company name) (year). Portions of this code are derived from IBM Corp.
Sample Programs. © Copyright IBM Corp. 2005. All rights reserved.
If you are viewing this information in softcopy form, the photographs and color
illustrations might not display.
Notices
521
522
IBM Tivoli Composite Application Manager for Application Diagnostics: Messaging Guide
Printed in USA
GC27-2822-00