Troubleshooting - IBM Tivoli Composite Application Manager for Application Diagnostics v7.1

1. Troubleshooting
2. Tracing and logging within the Tivoli Enterprise Portal (Summary Workspaces)
3. Tracing and logging within the Tivoli Enterprise Portal Server
4. Tracing and logging within the Tivoli Enterprise Portal desktop client on Windows
5. Tracing and logging within the Tivoli Enterprise Portal desktop client on UNIX systems or Linux
6. Tracing and logging within the Tivoli Enterprise Portal Web client
7. Environment Checking Utility
8. Install Memory Dump Diagnostic for Java with IBM Support Assistant
9. Where to install ISA and MDD for Java
10. Downloading ISA
11. Install ISA
12. Install MDD for Java
13. Troubleshooting: ITCAM Agent for WebSphere Applications
14. Installation and configuration
15. All platforms
    • Classpath for the portal client is missing
    • data collector cannot work with several deployment managers in WAS XD environment
    • data collector configuration tips
    • data collector installation fails
    • Error message is displayed during data collector configuration
    • Error message "JACL failed" displays when running UpdateInstaller
    • Error messages occur in the log files after installing the JVMTI interim fix on Sun JDK 1.5.0
    • Failure to access the Oracle Application Server Enterprise Manager after configuring the data collector
    • Incomplete list of servers shown during the installation
    • Manually changing the Tivoli Enterprise Monitoring Agent host name in ITCAM Agent for WebSphere Applications data collector
    • Only one log file can be found after multiple CICS DCs were installed on the same computer
    • Required permissions for data collector configuration for WAS
    • Special requirements for CICS installation
    • The monitoring agent fails to start
    • Uninstall the data collector
    • WAS 7.0 cannot start and returns an "Unable to create Java Virtual Machine" error

16. Distributed platforms
    • Cannot start WebSphere administrative console after installing data collector on Windows
    • data collector installation fails on Linux platforms because of inadequate permissions
    • ECU check fails to return the correct value
    • Error messages are displayed on the console when installing or configuring the agent for WebSphere Applications or J2EE as a non-root user on the AIX system
    • Failure to open external links in ITCAM launchpad on the UNIX System
    • Insufficient temporary disk space when installing on HP-UX
    • OS agent does not start after Tivoli Enterprise Monitoring Agent local installation or upgrade
    • Customized situations are not available after a version update

17. IBM i systems
    • Error occurs when installing the data collector on iSeries systems
    • Fail to get WebSphere version information during the silent installation of the data collector on the i5/OS system
    • Uninstall eCAM 7.0 on i5/OS silently

18. z/OS systems
    • ConnectorNotAvailableException found in data collector logs on z/OS system
    • Run ITCAM Agent for WebSphere Applications

19. All platforms
    • Cannot call the IBM Tivoli Monitoring Client after reconfiguring data collector
    • Change server alias fails
    • Disable and enable the data collector without losing the configuration settings
    • Enable Method Profiling
    • Errors displayed in the data collector logs
    • Error getting ITLM Application Tookit
    • Error KCIIN0205E occurs when stopping Tivoli Enterprise Monitoring Agent
    • Errors occur during or after upgrading
    • Error KDY0005E occurs when remote upgrading Tivoli Enterprise Monitoring Agent to ITCAM for Application Diagnostics
    • Monitoring overhead rises after upgrade from ITCAM for WebSphere version 6.1 Fix Pack 4 or lower
    • Export all the defined Situations into one handy file
    • Failed to update UpdateAutoRun.sh
    • Inconsistent JVM heap size value reported in Server Activity Display and System Resources
    • ITCAM can not be started or configured when the path name of IBM Tivoli Monitoring contains special symbols
    • Managing Server and data collectors require a restart after IP address change
    • Method report does not contain the expected trace although MOD-L3 and proper filter definition are specified
    • Monitor GC when the GC log path is changed after installed ITCAM for Application Diagnostics
    • No Heap Dump available on Solaris JDK1.5
    • NullPointerExceptions
    • Out of Memory errors occur when using L3 and hotspot JVM
    • Restore the previous WAS configuration after data collector installation and configuration
    • Significant CPU consumption and high latency observed if a thread dump is requested
    • Some features are not working
    • Stack trace cannot be returned for RMI EJB invocations
    • Tivoli Enterprise Monitoring Agent fails to work
    • The data collector workload on the PS/AA is not balanced
    • The platform CPU has a negative value
    • The memory requirements increase
    • Turning on or turning off the data collector connections
    • Warning CJL0047W during unconfiguration of the data collector
    • WebSphere Proxy Server crashes

20. Distributed platforms
    • HP uninstallation cannot delete some toolkit files
    • Tivoli Enterprise Monitoring Agent on Windows Vista fails to start without administrator rights
    • Tivoli Enterprise Monitoring Agent cannot be started on SuSE Linux Enterprise Server 9

21. IBM i systems
    • WAS fails to start on IBM i 6.1

22. z/OS systems
    • Install, configuring, and running ITCAM for WebSphere on z/OS with Global Security turned on
    • KYNM001E KYNALSRD: SERVICE=IXGCONN(CONNECT) FOR LOGSTREAM
    • z/OS: Problem with amupdate.sh script after making changes in the cynlogging.properties file
    • z/OS: Diagnosing ITCAM data collector configuration problems with global security
    • z/OS: Configuration user can not read FFDC and other log files
    • z/OS data collector: Request metrics and method trace data do not appear
    • z/OS data collector: Protocol Timeout

23. Troubleshooting: ITCAM Agent for J2EE
    • Installation and configuration
    • data collector
    • Cannot connect to JBoss server when configuring the data collector for JBoss 4.2.0 or higher
    • data collector configuration fails
    • data collector installation fails
    • data collector for WebLogic server instance cannot be unconfigured
    • Failed to create the default data collector log path
    • Messages displayed during a silent installation
    • Non-root user configuration problems
    • Restart the application server after installing data collector for WAS Community Edition 1.1.0.2 on Windows platform generates error messages
    • The monitoring agent
    • Tivoli Enterprise Monitoring Agent fails to start with error message "ERROR: required environment variable KWJ_PROD is not set"
    • Run ITCAM Agent for J2EE
    • data collector
    • Error messages occur in the log files after installing the JVMTI interim fix on Sun JDK 1.5.0
    • Attempts to start WebLogic Portal Server 10 using Sun JDK 1.5 or HP JDK 1.5 produce out-of-memory error messages
    • CICS Transaction Gateway (CTG) Common Client Interface (CCI) Transactions not correlated
    • Custom Mbean does not function when the category name is in lowercase
    • data collector fails to start
    • DB2-related applications cannot be deployed on Oracle 9 after the data collector is configured
    • J2SE data collector has JAVA Null Exception Errors
    • J2SE data collector custom request fails
    • JBoss data collector throws java.lang.NoClassDefFoundError exception during server start
    • Net Weaver: Cannot get request data from CTG/IMS/MQI library
    • No Heap Dump available on Solaris JDK1.5
    • Port number of the request URL in the Request/Session Object Link is incorrect on an Oracle data collector
    • Server fails to start
    • The data collector on Sun IAS 6.5 cannot read garbage collection events when using the custom JVM launcher
    • WebLogic does not function after the data collector is installed
    • The monitoring agent
    • Tivoli Enterprise Monitoring Agent on Windows Vista fails to start without administrator rights
    • Tivoli Enterprise Monitoring Agent fails to start or recycle the server
    • Tivoli Enterprise Monitoring Agent stops because of lack of memory

24. Troubleshooting: ITCAM Agent for HTTP Servers
    • Tivoli Enterprise Monitoring Agent fails to start or recycle the server
    • Tivoli Enterprise Monitoring Agent on Windows Vista fails to start without administrator rights
    • Tivoli Enterprise Monitoring Agent stops because of lack of memory
    • Web Servers Summary view does not display the new server name

25. Troubleshooting: Tivoli Enterprise Portal
    • Agent node cannot be found after reconfiguration
    • Application Server subnode not available
    • Automatic threshold and history problems after upgrading
    • Cannot see the hover help in summary workspace
    • Dashboard table filter cannot handle informational situations
    • Historical view problems
    • Issues arising out of Attribute name changes
    • ITCAM Agent for WebSphere Applications shows disconnected in workspace server summary
    • ITLM agent not installed
    • Manually removing the Tivoli Enterprise Portal Server database and TEPS2 ODBC driver
    • Not reporting data problems
    • Problems on Situations in Tivoli Enterprise Portal
    • Request failed during execution (KFWITM220E)
    • Resource IDs displayed instead of English language strings
    • Time span icons are missing
    • Tivoli Enterprise Portal browser client fails with error "CMWApplet notinited"
    • The Failed Login Rate Metric displays 0 on Sun Web site
    • The Tivoli Enterprise Monitoring Agent JMX connection socket binding is reported incorrectly
    • The Oracle application server displays incorrect port number in the Request Name column
    • The version of the HTTP Server is wrong on Tivoli Enterprise Portal
    • Tomcat JDBC Connection Pools is always 0 on REC
    • New Take actions and Situations appear in workspaces for older Tivoli Enterprise Monitoring Agent versions

26. Troubleshooting: Managing Server
    • Installation and configuration
    • Configure many WASs takes a long time
    • Core dump error occurs when accessing the Visualization Engine on an Oracle database
    • Create application traps in Managing Server Visualization Engine to see ITCAM agents data in RPT version 7 and 8
    • Display problems during Managing Server installation
    • Error CYNK0069E: MON_HEAP_SZ occurred while querying or updating records in tables
    • Failed to start am_start.sh after Managing Server installation on Windows Server 2003 SP1
    • Failure to log on to the Managing Server
    • FFDC returns a failure during Managing Server installation
    • Java not found error occurred during installations from CD
    • Managing Server and embedded installations fail
    • Managing Server fails to get WebSphere profile information when upgrading
    • Managing Server installer hangs at 75% completed
    • Managing Server is started successfully but the connection has problem
    • Restore the WAS configuration
    • RHEL5 requires xlibp files from Fedora Core v6 for Managing Server to install
    • Security issue when installing Managing Server in WAS Network Deployment
    • Problems on the installation and connection of Managing Server databases
    • Set up the cygwin X server to install the Managing Server remotely
    • Windows: Scripts Execution Authentication
    • Run the Managing Server
    • Application Monitor shows data collectors as unavailable even though they are running
    • Authoritative server does not list in the sorted order in the comparison table after setting up a Runtime Environment Comparison
    • Change the Managing Server that a data collector is connected to
    • Changes to make on WAS administration console for the Visualization Engine to work correctly
    • Problems and tips on the databases of Managing server
    • Customers running at monitoring level 2 (MOD L2) cannot obtain Method Profiling data
    • CYNP0016W: There is a missing method trace for the end of the request
    • Data is not correctly shown
    • Error CYNVE0181E: One or more data collectors were unable to be configured
    • Inapplicable features when customizing an user-defined role
    • Inconsistent timestamp shown in Heap Dump Management with time set in data collector
    • ITCAM Agent for WebSphere Applications/J2EE Database optimization
    • Launch in context to portal fails
    • Load-balancing Archive Agents across multiple Publishing Servers
    • Managing Server and data collectors require a restart after IP address change
    • Messages with severity "INFO" level are still logged after the log level is set to "ERROR"
    • New traps and PAR reports from the ITCAM 6.1 Managing Server Fix Pack 2 still exist but do not work after uninstallation
    • OutOfMemory exceptions
    • Port 9090 Conflicts error on AIX
    • Problems and tips on language issues
    • Problems with Server Active Display page
    • Problems with method trace
    • Request throughput spikes when Managing Server is restarted
    • SAD Client Requests Time uses managing server local time
    • Server Availability graph does not correctly account for offline servers
    • Server name displayed as a double value when exporting report to CSV file
    • Significant CPU consumption and high latency observed if a thread dump is requested
    • Some pages are displayed inappropriately in MSVE
    • The Server Unavailable trap can be triggered only once when the server is not available
    • Unable to load kernel classes from a user other than root
    • Web Session Browser feature not supported at monitoring level 1
    • CYNVE0471E: No Data Available message displayed when trying to generate a report
    • Accessibility
    • Support information
    • Search knowledge bases
    • Finding Release Notes
    • Finding Technotes
    • Subscribing to new Technotes
    • Tivoli Support Technical Exchange
    • Search the information center on your local system or network
    • 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
    • Notices
    • Trademarks
    • Messaging Guide
    • PDF
    • Note
    • Edition Notice
    • About this guide
    • Intended audience
    • Publications
    • ITCAM for Application Diagnostics library
    • Related publications
    • Access terminology online
    • Access publications online
    • Ordering publications
    • Accessibility
    • Tivoli technical training
    • Conventions used in this guide
    • Typeface conventions
    • Variables for directories
    • Log files, tracing, and utilities

27. Log files and tracing for the Tivoli Enterprise Monitoring Agent
    • Gather Script
    • Tracing within the Tivoli Enterprise Monitoring Agent
    • Useful traces
    • Where to specify tracing parameters
    • Tivoli Enterprise Monitoring Agent log files
    • Plug-in for IBM Support Assistant (ISA)
    • Downloading the plug-in from IBM Support Assistant (ISA)
    • Use the plug-in to collect log files and system information

28. Log files and tracing for the data collector
    • First Failure Data Capture
    • Gather Script
    • Set the logging and tracing levels
    • data collector logs
    • Plug-in for IBM Support Assistant (ISA)

29. Log files and tracing for the Managing Server
    • First Failure Data Capture
    • Gather Script
    • Change the log level
    • Managing Server logs
    • LogViewer
    • Start the LogViewer
    • Use the wrapper script
    • Direct JVM invocation
    • Specify the query string
    • Specify the filter predicate
    • Error handling
    • Examples

30. Troubleshooting
    • 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
    • Install Memory Dump Diagnostic for Java with IBM Support Assistant
    • Where to install ISA and MDD for Java
    • Downloading ISA
    • Install ISA
    • Install MDD for Java

31. System Messages for ITCAM Agent for WebSphere Applications
    • 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.
    • 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.

32. 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
    • 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
    • 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
    • CYNAU135I: uName saved changes to SNMP Settings as (Value: Old/New) -- Host: oldHost/newHost Port: oldPort/newPort Community: oldCommu/newCommu

33. 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.

34. 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.
    • 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 WAS.
    • BWMCR8296E: The data entered does not match the data specified in the local installation files of the WAS.
    • 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.
    • 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 WAS.
    • BWMCR8324E: The installation failed while installing the WAS Fixpack.
    • BWMCR8325E: The installation failed while starting the WAS.
    • BWMCR8326E: The WAS 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:
    • 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 WAS.
    • 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.
    • 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 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 WAS, Version 6.0 installation image specified was not valid.
    • BWMCR8359E: The DB2, Version 8.2 installation image specified was not valid.
    • BWMCR8360E: The WebSphere Caching Proxy, Version 6.0 installation image specified was not valid.
    • BWMCR8361E: The username and password specified cannot be used to contact the WAS.
    • 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.
    • 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: WAS 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 WAS, Version 5.1.1 fixpack image specified was not valid.
    • BWMCR8394E: The WAS, Version 5.1.1.2 fixpack image specified was not valid.
    • BWMCR8395E: The installation failed while installing the WAS Fixpack.
    • BWMCR8396E: The installation did not find the specified database.
    • 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 WAS, Version 6.0.2 installation image 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 WAS could not be started. Manually restart the WAS.
    • BWMCR8509W: The WAS 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.
    • 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 WAS 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
    • BWMCR8094I: Required Field: URL
    • BWMCR8096I: Required Field: Mask
    • BWMCR8098I: The installation tried to use a version of WebSphere 6.0 that does not have WAS, refresh pack 6.0.2 installed. WAS refresh pack 6.0.2 or later is required for this product to run on WebSphere 6.0. The product is also supported on WAS, 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
    • 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 WAS 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 WAS, version 5.0.1 that has Embedded Messaging Installed. WAS Fix pack 5.0.2 or later is required for this product to be migrated to WAS 6.0.
    • BWMCR8175I: The installation tried to use a version of WebSphere that does not have WAS, Fix pack 5.1.1.2 installed. WAS 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.
    • 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.
    • BWMCR8188E: The specified RMI port number is out of range. Valid TCP/IP port numbers must be positive integers between 8200 and 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.
    • BWMCR8190W: The data collector cannot connect to the Managing Server.
    • BWMCR8191W: The Managing Server cannot connect to the data collector.
    • BWMCR8192E: The path is not writable:pathPlease select a writable path.
    • BWMCR8623E: An error occurred while trying to validate the response file path.
    • BWMCR8625E: An error occurred while trying to validate the option choosing on this panel.
    • BWMCR8627I: A warning occurred while trying to validate the specified response file name.
    • BWMCR8629E: An error occurred while trying to validate the specified response file name.
    • BWMCR8631E: An error occurred while trying to validate the specified response file name.
    • BWMCR8633E: An error occurred while trying to validate the specified response file name.
    • BWMCR8635E: The directory path dir contains spaces, which is not acceptable.
    • BWMCR8636E: The destination path cannot contain the following special characters: spechar_list
    • CYNCR8026I: Required Field: Admin User
    • CYNCR8028I: Required Field: Password
    • CYNCR8029I: Required Field: User
    • CYNCR8037I: Required Field: Verify Password
    • CYNCR8038I: The passwords entered do not match.
    • CYNCR8039I: The user entered does not exist on this machine.
    • CYNCR8040I: The specified user already exists on this machine.
    • CYNCR8061I: A local version of WAS was found on this machine. IBM Tivoli Composite Application Manager for WebSphere 6.1 will use this installation of WAS.
    • CYNCR8062I: A local version of WAS was not detected. IBM Tivoli Composite Application Manager for WebSphere 6.1 will install WAS 6.1 on this machine.
    • CYNCR8084I: Required Field: Cell Name
    • CYNCR8085I: Required Field: Server Name
    • CYNCR8086I: Required Field: Node Name
    • CYNCR8087I: Required Field: SOAP Connector Port
    • CYNCR8088I: Required Field: JDBC Path
    • CYNCR8094I: Required Field: URL
    • CYNCR8098I: The installation tried to use a version of WebSphere 6.0 that does not have WAS, Fix Pack 6.0.2 installed. WAS, 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.
    • 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.
    • 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: WAS cannot be contacted using the specified port. The WAS 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 WAS.
    • 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 WAS.
    • CYNCR8324E: The installation failed while installing the WAS Fixpack.
    • CYNCR8325E: The installation failed while starting WAS.
    • 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.
    • 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 WAS. 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: WAS 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 WAS 6.1 installation image directory specified is not valid.
    • CYNCR8359E: The DB2 8.2 installation image directory specified is not valid.
    • CYNCR8360E: The WAS 6.1.1 installation image directory specified is not valid.
    • CYNCR8361E: The user name and password specified cannot be used to contact WAS.
    • CYNCR8362E: The user does not have the appropriate rights to run the Managing Server.
    • CYNCR8363E: Security is not enabled in WAS.
    • 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: WAS 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 WAS.
    • CYNCR8399E: The installer was unable to validate server and port information with WAS.
    • 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 WAS could not be started.
    • CYNCR8509W: The WAS 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 WAS 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.
    • 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 WAS.
    • CYNCR8603I: Uninstalling WAS.
    • 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 WAS 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.
    • 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 specified is not valid.
    • CYNCR9200I: Required Field: Managing Server Host Selection
    • CYNCR9200W: Some errors occur during restarting the WAS.
    • 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
    • CYNCR9209I: Required Field: DBA User ID
    • CYNCR9210I: Required Field: DBA Password
    • CYNCR9211E: The installer was unable to get the topology information from WAS.
    • CYNCR9211I: The Oracle Home you entered is invalid
    • CYNCR9212E: The WAS 6.1 installation image directory specified is not valid.
    • CYNCR9213E: The WAS 6.1 installation image directory specified is not valid.
    • CYNCR9214E: An error occurred while trying to validate the WAS 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 WAS.
    • CYNCR9500E: The Visualization Engine installation failed.
    • CYNCR9501E: The specified port number (portNumber) is invalid.
    • CYNCR9601E: An error occurred while trying to validate the WAS information entered on this panel.
    • CYNCR9602E: An error occurred while trying to run WAS's wsadmin utility. The following are error messages from wsadmin: wsadminMsg
    • CYNCR9603E: An error occurred while trying to run WAS's wsadmin utility. The following are error messages from wsadmin: wsadminMsg
    • CYNCR9604E: An error occurred while trying to validate the WAS 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 WAS 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.
    • 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 WAS not to start up.

35. CYND Messages: data collector
    • data collector on z/OS
    • CYND0012I: The data collector stopping.
    • CYND0013I: The data collector stopped.
    • CYND0014I: The data collector starting.
    • CYND0015I: The data collector started.
    • CYND0026I: Event Agent started.
    • CYND0027E: Failed in publishing records to Publish Server.
    • CYND0031I: Getting Publish Engine from kernel.
    • CYND0032I: Publish Engine successfully downloaded from kernel.
    • CYND0033I: The publish engine was successfully downloaded from the Kernel.
    • CYND0040I: The include list is 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: The 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.
    • CYND1002E: Custom Service initialization failed because JVMPI could not be initialized
    • CYND1003I: Native Custom Service shutdown complete.
    • CYND1004I: Native probe started successfully.
    • CYND1005I: Native probe stopped successfully.
    • CYND1006E: The am.home system property is undefined.
    • CYND1007W: The weblogic.Domain system property is undefined.
    • CYND1008W: The am.nodename system property is undefined.
    • CYND1009W: The weblogic.Name system property is undefined.
    • CYND1010W: The am.appserver system property is undefined.
    • CYND1011I: ProbeManager started successfully.
    • CYND1012E: Failed to start ProbeManager.
    • 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 occured during encryption.
    • CYND1020E: Invalid file name.
    • CYND1021E: Invalid userID or password.
    • CYND1022E: Invalid file name.
    • CYND1023E: Invalid userID or password.
    • CYND1024E: Could not open the file: filename
    • CYND1025E: No data in the file: filename
    • CYND1026E: Invalid file name, userID or password.
    • CYND1027E: Could not open the file for writing: filename
    • CYND1028E: The input string is corrupt.
    • CYND1029E: UID, PASSWORD or filename is NULL.
    • CYND1030E: Your actual password and decrypted password don't match
    • CYND1031E: The userID read from the file is not the same as UID entered.
    • CYND1032E: Password read from the file is not the same as the password entered.
    • CYND1033I: Verified userID and password by reading the created file, passwordfile. filename was properly created.
    • CYND1034E: Encrypted password string is corrupt.
    • CYND1035E: Error occurred during decryption.
    • CYND1036E: The password is too long. It should be less than max_len characters.
    • CYND1037E: JVMPI could not create a Raw Monitor for GlobalLock.
    • CYND1038E: Global lock was created before initialization of JVMPI.
    • CYND1039W: This is an unknown event type, TypeID: evt_type
    • CYND1040E: The EventAgent was not started and cannot manage ThreadData.
    • CYND1041W: Failed to send data.
    • CYND1042E: Event Queue is NULL for Thread, TID: tid
    • CYND1043W: Overall events dropped/deleted:evtDropCnt
    • CYND1044I: Events dropped cnt for thread threadName because they exceeded event queue limit of queueLimit
    • CYND1045W: Thread data creation failed.
    • CYND1046I: EvtAgentManager started.
    • CYND1047I: EvtAgentManager stopped.
    • CYND1048E: Class file is corrupt.
    • CYND1049E: Bad class file magic number:magic
    • CYND1050E: Failed to open library: libName
    • CYND1051I: Memory limit is less than the minimum limit: memLimit MB
    • CYND1052I: Memory monitor properties, ULimit: memUlimit bytes, Accept Threshold: threadHold bytes, URL Limit: urlUlimit, SQL Limit: sqlUlimit
    • 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
    • CYND1056W: Network Agent Thread is not started/alive/ready; rejecting send data.
    • CYND1057W: The queue is full and exceeds the buffer limit.
    • 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
    • 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.
    • CYND1067I: NetworkAgentManager stopped.
    • 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.
    • 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.
    • CYND1100I: Region Mask from Kernel = Kernel
    • CYND1102I: Region ID = 0xID8X
    • CYND1103I: Region Mask = 0xMask8X
    • CYND1104E: Cannot get the server common storage with error number = Error
    • CYND1105I: Enqueue server, Server, exclusively with return code = RC
    • CYND1106I: Enqueue server, Server, shared with return code = RC
    • CYND1107I: Gps counter file = Counter
    • CYND1108I: Gps counter get from file = File
    • CYND1109I: Gps counter file, File, created
    • CYND1112E: Unable to open counter file, File
    • CYND1554I: Thread Thread has had Global Publish Server token Token inserted into it.
    • CYND1555I: Thread Thread has called startGpsInvokeRequest.
    • CYND1556I: Thread Thread has exceeded the CommArea length limit. No Global Publish Server token has been added.
    • CYND1557I: Thread Thread has not had a Global Publish Server token inserted since the call type is Token.
    • CYND1558E: Thread Thread has encountered exception Exception.
    • CYND1559E: Thread Thread has encountered exception Exception.
    • CYND1566E: Thread Thread has encountered exception Exception.
    • CYND1567I: Thread Thread has called endGpsInvokeRequest.
    • CYND1568E: Thread Thread has encountered exception Exception.
    • CYND1570E: Thread Thread has encountered exception Exception.
    • CYND1571E: Thread Thread has encountered exception Exception.
    • CYND1572E: Thread Thread has encountered exception Exception.
    • CYND1573E: Thread Thread has encountered exception Exception.
    • CYND1574E: CTGCALLBACK failed to get a token.
    • CYND1574I: Thread Thread is logging to system resources:\nURL = URL\nServer = Server\nProgram = Program\nDuration = Duration
    • CYND1577I: For JMXDelegate.initialize, the user install directory is Diectory, and the install root is Install Root.
    • CYND1578W: For JMXDelegate.initialize, .init is Init.
    • CYND1579W: Thread Thread has encountered exception Exception.
    • CYND1582W: Thread Thread has encountered exception Exception.
    • CYND1583W: Thread Thread has encountered exception Exception.
    • CYND1584I: Thread Thread has called ProbeUtils.beginSQLRequest:\nSQL = Sql\nDataSource = Data Source\nOriginated = Originated\nNode = Node
    • CYND1585I: Thread Thread has called ProbeUtils.endSQLRequest:\nSQL = Sql\nDataSource = Data Source\nOriginated =Originated\nNode = Node
    • CYND1586I: The configuration service is disabled.
    • CYND1587I: The configuration service is enabled.
    • CYND1588I: PMI is enabled.
    • CYND1589I: PMI is disabled.
    • CYND1590I: JMX initialization was completed.
    • CYND1591W: The JMX proxy for the configuration service has failed to initialize. Exception Exception has occurred.
    • CYND1599E: Thread Thread encountered an error from IMS callback IMS.
    • CYND1600E: Thread Thread encountered an error from IMS callback. The token is null.
    • CYND1601E: Thread Thread has encountered an error from IMS callback functions. It expected a 4 bytes token, but the feedback was Feed Back.
    • CYND1700E: Thread Thread encountered exception Exception from JMSMQ callback functions.
    • CYND1705I: The system has turned on heap analysis for all tracked classes.
    • CYND1706I: The system has turned off heap analysis for all tracked classes.
    • CYND1707I: The system is setting the tracing level in Level 2 to L2 and in Level 3 to L3.
    • CYND1801W: BcmControl.init failed validation.
    • CYND1802W: BcmControl.init is missing file File.
    • CYND1803W: BcmControl.init encountered exception Exception.
    • CYND1804W: Modification of this type Type is disabled. The system has failed to remove type Type1.
    • CYND1805W: For BcmControl.cleanFiles, the source directory Directory is not a directory.
    • CYND1806W: For BcmControl.createJarFile, type Type is not valid.
    • CYND1807W: For BcmControl.createJarFile, type Type is modification disabled.
    • CYND1808W: For BcmControl.createJarFile, there is a missing JAR filename for type Type.
    • CYND1809W: For BcmControl.validate, property file Property is missing.
    • CYND1810I: Modification of type Type is disabled. Type Type1 is removed.
    • CYND1811I: The control file was validated.\nSource Path = Source Path\nDestination Path = Destination Path\nControl file = File
    • CYND1812W: The system failed to create JAR file File for type Type and was unable to rename the temporary file.
    • CYND1813I: JAR file File was created successfully for type Type.
    • CYND1814I: A JAR file exists with identical name and size. There was no replacement of file File.
    • 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.
    • CYND1816W: A JAR file exists with identical name but of different size. Since applyLatest flag is disabled, the existing file File is being removed.
    • 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.
    • CYND1818I: An existing file File is detected. Since modification of this type Type is disabled, this file has been deleted.
    • 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.
    • CYND1820I: This is the beginning of BcmControl.selfTest.
    • CYND1821I: Processing Process
    • CYND1822W: The system stopped processing Process because it cannot deduce its type.
    • CYND1823I: Classes within this file are subjected to modification: Class
    • CYND1824I: Classes within this file should not be modified: File.
    • CYND1825I: This file is of type Type.
    • CYND1826I: This type is enabled.
    • CYND1827I: This type is disabled.
    • CYND1828I: The XML file is of type Type.
    • CYND1829I: The replacement flag for this type is enabled.
    • CYND1830I: The replacement flag for this type is disabled.
    • CYND1831I: The JAR file is of type Type
    • CYND1832I: This is the end of the self test.
    • CYND1851I: The system cannot delete the previous Byte Code Modification JAR file: File.
    • CYND1852W: There are no contents in the Byte Code Modification directory Directory.
    • CYND1853I: Unknown entry type Type was skipped.
    • CYND1900W: The system failed to initialize BcmControl. Byte Code Modification is disabled.
    • CYND1901I: The system is processing XML file File.
    • CYND1902I: The system has started modifying the class Class.
    • CYND1903I: The system has finished modifying the class.
    • CYND1904W: An exception occurred in creating JAR file File.
    • CYND1905I: The system is skipping processing XML file file.
    • CYND1906I: The system has started processing the resource. The URL is Url. The resource name is Resource Name.
    • CYND1907W: The system could not find resource Resource.
    • CYND1908W: The stream is null for type Type.
    • CYND1909I: The system has finished processing the resource. The URL is Url.
    • CYND2000E: Data type mismatch (Long) Type
    • CYND2001E: Data type mismatch (Stat) Type
    • CYND2002E: Data type mismatch (Load) Type
    • CYND2050I: The probe supports Byte Code Modification Mod level Level.
    • CYND2051I: Probe does not support Byte Code Modification Mod level Level.
    • CYND2052E: There is an unsatisfied link for type Type.
    • CYND2053E: An unsatisfied link error occurred for MethodLevelModule.initializeClass().
    • CYND2054I: The system is initializing class Class.
    • CYND2055I: The system is flushing method IDs for class Class.
    • CYND2056I: The probe is recognized as enabled for Byte Code Modification.
    • CYND2057I: The system is flushing out previously loaded class Class.
    • CYND2058E: There was an unsatisfied link error while unloading link Link.
    • CYND2059E: Exception Exception has occurred in ITCAMfTTImpl.
    • CYND2060I: The probe will process IBM Tivoli Composite Application Manager for Transaction Tracking data.
    • CYND2061I: The probe will not process IBM Tivoli Composite Application Manager for Transaction Tracking data.
    • CYND2062W: The data collector was not able to connect to the Managing Server.
    • CYND2063W: The data collector was not able to connect to the Managing Server and log messages are now off.
    • CYND2064I: Connection to the Managing Server is disabled.
    • data collector on Windows and UNIX
    • CYND4001I: data collector Controller is listening at port portNumber
    • CYND4002I: After joining the Kernel, security manager is: Securitymanager
    • CYND4003E: Failed to start controller.
    • CYND4004I: Received notification of probe configuration update: Probeconfig
    • CYND4005E: Failed to allocate port to controller.
    • CYND4006I: Received notification that probe configuration was removed.
    • CYND4007E: Failed to set monitoring level.
    • CYND4008I: Native Probe and JAVA-JNI threads successfully started.
    • 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.
    • CYND4018E: Failed to start Publish Server agent.
    • CYND4019E: Failed to stop Publish Server agent.
    • CYND4020E: Failed to get sampling rate.
    • CYND4021I: Scheduler configuration is null for ID: Scheduleid
    • CYND4022E: Failed to set scheduler configuration.
    • CYND4023E: Failed to update scheduler configuration.
    • CYND4024I: Invalid monitoring level: Modlevel specified, ignore the new monitoring value.
    • CYND4025E: Failed to set new monitoring level.
    • CYND4026E: Failed to get default monitoring level.
    • CYND4027I: Probe security is not enabled.
    • CYND4028E: Error occurred when creating probe controller loginstub.
    • CYND4029I: Probe security is enabled.
    • CYND4030E: The Am home path is not set. Set the system property Am.Home for the data collector.
    • CYND4031E: An error occurred when setting up Cyanea custom service.
    • CYND4032E: Unable to join Kernel, retrying.
    • CYND4033E: Failed to start probe controller.
    • CYND4034E: Unable to save monitoring level.
    • CYND4035E: Unable to find monitoring file:Modfile
    • CYND4036E: Unable to read monitoring file: Modfile
    • CYND4037W: Unknown proxy host:Proxyhostname
    • CYND4038E: Unable to load Cyanea probe configuration file: Probeconfigfile
    • CYND4039E: Error occurred while getting product version number.
    • CYND4040E: Failed to load library: Libname
    • CYND4041I: Native custom service start notification issued successfully.
    • CYND4042E: An error occurred in native custom service start.
    • CYND4043I: Setting probe Sampling Rate for monitoring level (L0, L1, L2, L3):L0, L1, L2, L3, Usesystemdefault: Issystemdefault
    • 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.
    • CYND4053E: Am Home is not defined, not initializing security module.
    • CYND4054I: The Cyanea password file (Cyanea.Pswdfile) is not defined.
    • CYND4055E: The password file: Pwdfile does not exist.
    • 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: objectName
    • CYND4068I: No Mbean object found of type: type in process process
    • CYND4069E: An error occurred while creating Adminclient.
    • CYND4070E: An error occurred while querying for configuration objects of type: type
    • CYND4071E: An error occurred while querying for configuration attributes:
    • CYND4072E: Deploymentmanager.Rmi.Port property is not set in Datacollector.Properties.
    • 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 component .
    • CYND5236I: Privacy Filter is On. Http Request Query String, SQL String and Http Cookie data is not trasmitted
    • 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: ITCAM Product Mode changed to: productmode
    • CYND5241E: ITCAM Product Mode changed failed: productmode
    • Byte Code Modification Messages
    • CYND6001E: Unexpected exception. Refer to the tracing log.
    • CYND6001I: data collector Controller is listening at port portNumber
    • 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
    • CYND6002W: Not pure secure mode: server trusted by subject
    • CYND6003E: Unable to load configuration file: Probeconfigfile
    • CYND6003I: PING request was processed.
    • CYND6003W: Insecure mode: it is recommended to turn on SSL
    • CYND6004E: GC logging is not enabled.
    • CYND6004I: Secure Socket Factory successfully initialized
    • CYND6005E: GC Log file name is not specified in JVM parameters or in GCLogVariable
    • CYND6005I: Pure secure mode: using default trusted managers
    • CYND6006E: Error during Regexp subsystem initialization. Refer to the tracing log.
    • 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
    • CYND6009E: Exception when initializing SSL parameters
    • CYND6010E: Exception in the task. Refer to the tracing log.
    • CYND6011E: Cannot open the GC Log file: GCLogfile
    • CYND6031I: GC Collector MBean was registered, object name: objectName
    • CYND6032E: JMXConnectorServer was not found.
    • CYND6033E: RequestAggregator was not found
    • CYND6033W: Skip the incomplete GC event.
    • CYND6051I: OS Info MBean was registered, object name: objectName
    • CYND6076W: The Byte Code Modification engine could not identify a list of classes to be instrumented.
    • CYND6089I: The Byte Code Modification engine could not find directory directory.
    • CYND6090I: The Byte Code Modification engine could not find its working directory.
    • CYND6094I: The Byte Code Modification engine could not find a resource for name.
    • CYND6095I: The stream is null for name.
    • CYND7001E: Error while creating a silent installation file {0}
    • CYND7002E: Error during installation {0}
    • CYND7003E: Error while the migration tool was backing up the home directory {0}
    • CYND7004E: ISDataBase Access error {0}
    • CYND7006E: Error while Loading properties {0}
    • CYND7007E: Error during migration {0}
    • CYND7008E: Wrong path to product: {0}
    • CYND7010W: An error occurred while deleting the temporary file.
    • CYND7012E: The CERT_PATH variable was not found
    • CYND7013E: An error occurred while uninstalling the Visualization Engine: {0} {1}
    • CYND7014E: CYANEA_HOME_OS variable was not found in setenv.sh file
    • CYND7015E: Cannot read {0}
    • CYND7016E: Cannot write to file {0}
    • CYND7019E: Certificates data or Certificate path is not correct
    • 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.
    • CYND7031E: An error occurred while setting in IS database:
    • CYND7033E: An error occurred while restoring subfolders
    • CYND7034E: Updating DB failed with exit code {0}
    • CYND7035E: An error occurred while executing: {0}. Error: {1}
    • CYND7036E: The error occurred while uninstalling the Visualization Engine: {0}
    • CYND7037E: Incorrect Managing Server host name: {0}. A fully qualified host name should be provided.
    • CYND7038E: WAS_home variable is not defined
    • CYND7039E: The error occurred while running the script for uninstalling the Visualization Engine. {0} {1}
    • CYND7040E: An error occurred while getting profiles
    • CYND7041E: Variable app.install.path is not defined or could not read the file
    • CYND7042E: Not WebSphere 6, profile not found
    • 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
    • CYND7061E: The directory '{0}' is in use
    • CYND7062I: Directory is in use or does not exist
    • CYND7063E: Aborted by user
    • CYND7064I: Starting migration.
    • CYND7065I: Generating silent file
    • CYND7066I: Uninstalling Visualization Engine
    • CYND7067I: Visualization Engine installation is not selected, exit without deinstalling
    • CYND7068I: WebSphere instance found: {0}
    • 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}
    • 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}
    • Generic Probe Engine
    • 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
    • Request Aggregator
    • CYNPE0002E: XML parsing error has occurred: errorType parsing file fileName
    • CYNRA0001I: Request Aggregator is now initialized

36. 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.
    • 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.
    • 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.
    • 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.
    • 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.
    • 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.

37. CYNI Messages: Publish Server
    • 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.

38. 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.
    • 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.
    • 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.
    • 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.
    • 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 .

39. 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.

40. 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.
    • 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.
    • 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.
    • 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.
    • 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.

41. 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.
    • 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.

42. 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
    • 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

43. 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.
    • 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.
    • 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
    • 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.
    • 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.
    • 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.
    • 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.
    • 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.
    • 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.
    • 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.
    • 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
    • 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
    • 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
    • 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.
    • 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.
    • 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

44. CYNWS Messages: Web Services
    • CYNWS0001E: An authentication failure has occurred for the current user.
    • CYNWS0002W: No trap is defined for the current user.
    • CYNWS0003W: There is no aggregate data for traps.

45. 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.

46. 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.
    • CYNX0013E: The system failed to create the post-installation instruction file for the WebLogic unmanaged application server.

47. 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

48. 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.
    • 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.

49. 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
    • 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

50. 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.

51. System Messages for ITCAM Agent for J2EE
    • 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.

52. CYJNW Messages: SAP NetWeaver config toolkit
    • CYJNW0001E: invalid Central Instance Home
    • 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.

53. CYJWCC Messages: WAS 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.

54. 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.

55. CYND Messages: data collector
    • 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
    • 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.
    • 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 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
    • 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 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.
    • 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.
    • 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
    • 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>
    • 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 to 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
    • 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 to 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
    • 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
    • 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
    • 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 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.
    • 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 WAS Community Edition
    • CYND5002I: DC for WebSphere CE
    • CYND5003I: WebSphere CE Server Home
    • CYND5004I: WebSphere CE Server Home Directory, for example C:/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 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:/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.
    • 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
    • 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 ).
    • 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}
    • 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}
    • 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 Visualization 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}
    • 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}

56. 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

57. 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.
    • CYNWLC005D: This is not a valid JBoss server directory. Check the directory 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.

58. 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.

59. CYNX Messages: Installation
    • 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.

60. System Messages for ITCAM Agent for HTTP Servers
    • 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.
      • 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.

    • Messages from ITCAM for WebSphere data collector and ITCAM for J2EE data collector
    • Accessibility
    • Support information
    • Search knowledge bases
    • Finding Release Notes
    • Finding Technotes
    • Subscribing to new Technotes
    • Tivoli Support Technical Exchange
    • Search the information center on your local system or network
    • 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
    • Notices
    • Trademarks
    • TTAPI: Integratte with for Transactions
      • TTAPI integration support table
      • ITCAM Agent for WebSphere Applications: Configure TTAPI
      • ITCAM Agent for J2EE: Configure TTAPI

    +

    Search Tips   |   Advanced Search