IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1

---

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.
  

Parent topic:

CYND Messages: data collector

---

+

Search Tips   |   Advanced Search