Tivoli Application Dependency Discovery Manager Version Message Reference IBM

Transcription

1 Tivoli Application Dependency Discovery Manager Version Message Reference IBM

2

3 Tivoli Application Dependency Discovery Manager Version Message Reference IBM

4 Note Before using this information and the product it supports, read the information in Notices on page 277. Edition notice This edition applies to version 7, release 3 of IBM Tivoli Application Dependency Discovery Manager (product number 5724-N55) and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright IBM Corporation 2007, US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 About this information The purpose of this PDF document version is to provide the related topics from the information center in a printable format. Conventions used in this information center Terms and definitions In the IBM Tivoli Application Dependency Discovery Manager (TADDM) documentation certain conventions are used. They are used to refer to the operating system-dependent variables and paths, the COLLATION_HOME directory, and the location of the collation.properties file, which is referenced throughout the TADDM documentation, including in the messages. Operating system-dependent variables and paths In this information center, the UNIX conventions are used for specifying environment variables and for directory notation. When using the Windows command line, replace $variable with %variable% for environment variables, and replace each forward slash (/) with a backslash (\) in directory paths. If you are using the bash shell on a Windows system, you can use the UNIX conventions. COLLATION_HOME directory TADDM root directory is also referred to as the COLLATION_HOME directory. On operating systems such as AIX or Linux, the default location for installing TADDM is the /opt/ibm/taddm directory. Therefore, in this case, the $COLLATION_HOME directory is /opt/ibm/taddm/dist. On Windows operating systems, the default location for installing TADDM is the c:\ibm\taddm directory. Therefore, in this case, the %COLLATION_HOME% directory is c:\ibm\taddm\dist. Location of collation.properties file The collation.properties file contains TADDM server properties and includes comments about each of the properties. It is located in the $COLLATION_HOME/etc directory. Refer to the following list of terms and definitions to learn about important concepts in the IBM Tivoli Application Dependency Discovery Manager (TADDM). access collection A collection that is used to control the access to configuration items and permissions to modify configuration items. You can create access collections only when data-level security is enabled. Copyright IBM Corp. 2007, 2016 iii

6 asynchronous discovery In TADDM, the running of a discovery script on a target system to discover systems that cannot be accessed directly by the TADDM server. Because this discovery is performed manually, and separately from a typical credentialed discovery, it is called asynchronous. business application A collection of components that provides a business functionality that you can use internally, externally, or with other business applications. CI See configuration item. collection In TADDM, a group of configuration items. configuration item (CI) A component of IT infrastructure that is under the control of configuration management and is therefore subject to formal change control. Each CI in the TADDM database has a persistent object and change history associated with it. Examples of a CI are an operating system, an L2 interface, and a database buffer pool size. credentialed discovery TADDM sensor scanning that discovers detailed information about the following items: v Each operating system in the runtime environment. This scanning is also known as Level 2 discovery, and it requires operating system credentials. v The application infrastructure, deployed software components, physical servers, network devices, virtual systems, and host data that are used in the runtime environment. This scanning is also known as Level 3 discovery, and it requires both operating system credentials and application credentials. credential-less discovery TADDM sensor scanning that discovers basic information about the active computer systems in the runtime environment. This scanning is also known as Level 1 discovery, and it requires no credentials. Data Management Portal The TADDM web-based user interface for viewing and manipulating the data in a TADDM database. This user interface is applicable to a domain server deployment, to a synchronization server deployment, and to each storage server in a streaming server deployment. The user interface is very similar in all deployments, although in a synchronization server deployment, it has a few additional functions for adding and synchronizing domains. discover worker thread In TADDM, a thread that runs sensors. Discovery Management Console The TADDM client user interface for managing discoveries. This console is also known as the Product Console. It is applicable to a domain server deployment and to discovery servers in a streaming server deployment. The function of the console is the same in both of these deployments. discovery server A TADDM server that runs sensors in a streaming server deployment but does not have its own database. iv Application Dependency Discovery Manager: Messages

7 domain In TADDM, a logical subset of the infrastructure of a company or other organization. Domains can delineate organizational, functional, or geographical boundaries. domain server A TADDM server that runs sensors in a domain server deployment and has its own database. domain server deployment A TADDM deployment with one domain server. A domain server deployment can be part of a synchronization server deployment. In a domain server deployment, the following TADDM server property must be set to the following value: com.collation.cmdbmode=domain launch in context The concept of moving seamlessly from one Tivoli product UI to another Tivoli product UI (either in a different console or in the same console or portal interface) with single sign-on and with the target UI in position at the proper point for users to continue with their task. Level 1 discovery TADDM sensor scanning that discovers basic information about the active computer systems in the runtime environment. This scanning is also known as credential-less discovery because it requires no credentials. It uses the Stack Scan sensor and the IBM Tivoli Monitoring Scope sensor. Level 1 discovery is very shallow. It collects only the host name, operating system name, IP address, fully qualified domain name, and Media Access Control (MAC) address of each discovered interface. Also, the MAC address discovery is limited to Linux on System z and Windows systems. Level 1 discovery does not discover subnets. For any discovered IP interfaces that do not belong to an existing subnet that is discovered during Level 2 or Level 3 discovery, new subnets are created based on the value of the com.collation.ipnetworkassignmentagent.defaultnetmask property in the collation.properties file. Level 2 discovery TADDM sensor scanning that discovers detailed information about each operating system in the runtime environment. This scanning is also known as credentialed discovery, and it requires operating system credentials. Level 2 discovery collects application names and the operating system names and port numbers that are associated with each running application. If an application has established a TCP/IP connection to another application, this information is collected as a dependency. Level 3 discovery TADDM sensor scanning that discovers detailed information about the application infrastructure, deployed software components, physical servers, network devices, virtual systems, and host data that are used in the runtime environment. This scanning is also known as credentialed discovery, and it requires both operating system credentials and application credentials. multitenancy In TADDM, the use by a service provider or IT vendor of one TADDM installation to discover multiple customer environments. Also, the service provider or IT vendor can see the data from all customer environments, but within each customer environment, only the data that is specific to the About this information v

8 respective customer can be displayed in the user interface or viewed in reports within that customer environment. Product Console See Discovery Management Console. script-based discovery In TADDM, the use, in a credentialed discovery, of the same sensor scripts that sensors provide in support of asynchronous discovery. SE See server equivalent. server equivalent (SE) A representative unit of IT infrastructure, defined as a computer system (with standard configurations, operating systems, network interfaces, and storage interfaces) with installed server software (such as a database, a web server, or an application server). The concept of a server equivalent also includes the network, storage, and other subsystems that provide services to the optimal functioning of the server. A server equivalent depends on the operating system: Operating system Windows 500 AIX 1000 Linux 1000 HP-UX 500 Network devices 1000 Approximate number of CIs storage server A TADDM server that processes discovery data that is received from the discovery servers and stores it in the TADDM database. The primary storage server both coordinates the discovery servers and all other storage servers and serves as a storage server. All storage servers that are not the primary are called secondary storage servers. streaming server deployment A TADDM deployment with a primary storage server and at least one discovery server. This type of deployment can also include one or more optional secondary storage servers. The primary storage server and secondary storage servers share a database. The discovery servers have no database. In this type of deployment, discovery data flows in parallel from multiple discovery servers to the TADDM database. In a streaming server deployment, the following TADDM server property must be set to one of the following values: v com.collation.taddm.mode=discoveryserver v com.collation.taddm.mode=storageserver For all servers except for the primary storage server, the following properties (for the host name and port number of the primary storage server) must also be set: v com.collation.primarystorageserver.host v com.collation.primarystorageserver.port vi Application Dependency Discovery Manager: Messages

9 If the com.collation.taddm.mode property is set, the com.collation.cmdbmode property must not be set or must be commented out. synchronization server A TADDM server that synchronizes discovery data from all domain servers in the enterprise and has its own database. This server does not discover data directly. synchronization server deployment A TADDM deployment with a synchronization server and two or more domain server deployments, each of which has its own local database. In this type of deployment, the synchronization server copies discovery data from multiple domain servers one domain at a time in a batched synchronization process. In a synchronization server deployment, the following TADDM server property must be set to the following value: com.collation.cmdbmode=enterprise This type of deployment is obsolete. Therefore, in a new TADDM deployment where more than one server is needed, use the streaming server deployment. A synchronization server can be converted to become a primary storage server for a streaming server deployment. TADDM database In TADDM, the database where configuration data, dependencies, and change history are stored. Each TADDM server, except for discovery servers and secondary storage servers, has its own database. Discovery servers have no database. Storage servers share the database of the primary storage server. TADDM server A generic term that can represent any of the following terms: v domain server in a domain server deployment v synchronization server in a synchronization server deployment v discovery server in a streaming server deployment v storage server (including the primary storage server) in a streaming server deployment target system In the TADDM discovery process, the system to be discovered. utilization discovery TADDM sensor scanning that discovers utilization information for the host system. A utilization discovery requires operating system credentials. About this information vii

10 viii Application Dependency Discovery Manager: Messages

11 Message reference This reference lists and describes each message that is generated by the IBM Tivoli Application Dependency Discovery Manager Fix Pack 3. Messages are listed in ascending alphanumeric order. For Message Guide for previous TADDM releases, see the following documents: v TADDM : the Message Reference v guide (cmdb_msgref7300_pdf.pdf file) v TADDM : the Message Reference v guide (cmdb_msgref7301_pdf.pdf file) v TADDM : the Message Reference v guide (cmdb_msgref7302_pdf.pdf file) CTJOP Messages for the CTJOP component. Platform IP messages CTJOP0000E The ScopeException is given a null exception to wrap. The Topology Manager receives an unexpected condition. Check the TADDM Server to ensure it is operating properly. CTJOP0001E The following scope element needs to have a name and IP address: scope_element. The scope element is missing either its name or IP address attribute. Ensure the scope element is complete. The scope element needs to have a name and IP address. CTJOP0002E The following scope element needs to have a name and IP address: scope_element The scope element is missing either its name or IP address attribute. Ensure the scope element is complete. The scope element needs to have a name and IP address. CTJOP0003E The following scope element is missing attributes: scope_element. The following attributes are missing: missing_attributes. The RangeScope element is missing at least one attribute. Ensure the Scope element is complete. You need to specify the value for the missing attribute. CTJOP0004E The following scope element type is unknown: unknown_scope_element_type. The scope type is not valid. Specify a valid scope type. The following types are valid: IP Address, IP range of addresses, or an IP network. CTJOP0005E The following scope contains no elements: scope_without_elements. This scope does not have any values associated with it. elements. Ensure the scope has CTJOP0006E The scope element contains an incorrectly formatted exclusion. The scope exclusion is not a correctly formatted IP address. For example, a valid IP address. Ensure the exclusion string is Copyright IBM Corp. 2007,

12 CTJOP0007E CTJOP0034I CTJOP0007E The following IP address is not valid: VALUE_0. Enter a valid IP address. The IP address is not correctly formatted. For example, valid IP address. Ensure the IP address is a CTJOP0014E The following scope element type is not known: unknown_scope_element_type This type of scope is not a valid type. Ensure the scope type is a valid choice: an IP address, an IP range of addresses, or an IP network. CTJOP0008E The following netmask is not valid: invalid_netmask. Enter a valid netmask. The subnet mask is not correctly formatted. For example, valid. Ensure the subnet mask is CTJOP0009E The following starting IP address is not valid: invalid_starting_ip_address. The starting IP address is not valid. The format should be Ensure the starting IP address is a valid IP address. CTJOP0010E The following ending IP address is not valid: invalid_ending_ip_address. The ending IP address is not valid. The format should be is a valid IP address. Ensure the ending IP address CTJOP0011E The scope element is missing an attribute. The scope element is missing either the IP address or subnet mask attribute. all required attributes. Ensure the scope element has CTJOP0012E The server cannot convert the IpSet object with an unknown type. The type specified for the IpSet object is not a valid type. Ensure the IpSet type is valid. The following list identifies valid options: IP address, IP range of addresses, or an IP network. CTJOP0013E The following scope contains no elements: scope_without_elements. The scope does not have any values associated with it. required elements. Ensure the scope has the CTJOP0015E An error occurred when creating the initial scopes. CTJOP0016E The IP address is not valid. The scope exclusion is not a correctly formatted IP address. For example, a valid IP address. Ensure the exclusion string is CTJOP0017E The following IP address is not a valid IP address: invalid_ip_address The subnet mask is not correctly formatted. For example, entered is valid. Ensure the subnet mask CTJOP0018E The following scope element should have name, but no name has been defined: scope_element. Specify a name. This scope element is missing a name. Ensure the scope element is complete and a name has been defined. CTJOP0019W Unable to create network object for IP address: ip address with the netmask: netmask The subnet mask is a not valid netmask. For example, valid. Ensure the subnet mask is CTJOP0034I Using the configuration value of configuration_value to determine default subnet masks. This configuration value, which is specified in the collation.properties file, will be used to determine subnet masks for L1 Network objects. None 2 Application Dependency Discovery Manager: Messages

13 CTJOP0035W CTJOP0042E CTJOP0035W In the collation.properties file, the following part of the value of the defaultnetmask property does not have a '/' between the IP range and the subnet mask: configuration_value. This portion of the configuration value is incorrect and will be ignored. configuration value. Correct the syntax of the CTJOP0036W In the collation.properties file, the following part of the value of the defaultnetmask property does not have a subnet mask that is an integer: configuration_value. This portion of the configuration value is incorrect and will be ignored. configuration value. Correct the syntax of the CTJOP0037W In the collation.properties file, the following part of the value of the defaultnetmask property does not have a subnet mask that is between 8 and 32: configuration_value. This portion of the configuration value is incorrect and will be ignored. configuration value. Correct the syntax of the CTJOP0040W In the collation.properties file, the following part of the value of the defaultnetmask property has an ending IP address that is not in the correct form: configuration_value. This portion of the configuration value is incorrect and will be ignored. Refer to the documentation for information about the correct format to use. Correct the syntax of the configuration value. CTJOP0041W In the collation.properties file, the following part of the value of the defaultnetmask property has a starting IP address that is not lower than the ending IP address: configuration_value. This portion of the configuration value is incorrect and will be ignored. configuration value. Correct the syntax of the CTJOP0042E The following sub scope is unknown: unknown_sub_scope. The specified sub scope name is not found on the scope list. name. Specify a valid sub scope CTJOP0038W In the collation.properties file, the following part of the value of the defaultnetmask property does not have a '-' between the starting and ending IP addresses: configuration_value. This portion of the configuration value is incorrect and will be ignored. configuration value. Correct the syntax of the CTJOP0039W In the collation.properties file, the following part of the value of the defaultnetmask property has a starting IP address that is not in the correct form: configuration_value. This portion of the configuration value is incorrect and will be ignored. Refer to the documentation for information about the correct format to use. Correct the syntax of the configuration value. Message reference 3

14 CTJOP0100E CTJOP0122E Platform utility messages CTJOP0100E The following driver type is not known: unknown_driver_type. The JDBC driver is not of a known type. Ensure the JDBC driver is one of the known types: Oracle, Sybase, DB2, SqlServer, or a valid generic JDBC driver. CTJOP0102W The expected model object implementation class is not available. The application is using the following dynamic proxy: dynamic_proxy. CTJOP0103W The zero argument constructor did not work. The application is using the following dynamic proxy: dynamic_proxy. CTJOP0104W The zero argument constructor has the wrong access. The application is using the following dynamic proxy: dynamic_proxy. CTJOP0105E The argument is not a modelobject. The object is being returned. CTJOP0106W The expected model object implementation class is missing the appropriate constructor: class_missing_constructor. CTJOP0107W The following constructor did not work: constructor_did_not_work. CTJOP0110W The expected model object implementation class is not available: class_not_available. CTJOP0111W The zero argument constructor did not work: constructor_did_not_work. CTJOP0112W The zero argument constructor has the wrong access: constructor_wrong_access. CTJOP0113E The implementation is not available for the following object: object. CTJOP0114E The class is not valid. The class does not use the correct URI for new classes. The class must start with the following string: com.collation.platform.model. Programmer response: Specify the class to start with the following string: com.collation.platform.model. CTJOP0115E There is not enough swap space. The server waited for the following amount of time: swap_space_wait_time. The command is unable to complete successfully because the system swap space is too small. Ensure the system has enough swap space to run the command successfully. CTJOP0120E The following command does not contain valid command line syntax: VALUE_0. The command does not contain valid command line syntax. Each argument is either a quoted string, or a string without spaces. Correct the syntax of the command. Rerun the command. CTJOP0121E The thread is not available. The thread pool is given a thread to assign work to, but the thread is busy. available. Ensure the TADDM Server is CTJOP0122E The application cannot add the URL to system classloader. The server is attempting to change the classpath by adding another class, but the add fails. available. Ensure the TADDM Server is 4 Application Dependency Discovery Manager: Messages

15 CTJOP0131E CTJOP0155E CTJOP0131E This is not a directory. The file specified is not a directory. The recurvise delete command does not work. Correct the command to specify a directory. Retry the command. CTJOP0132E The following file cannot be deleted: file_not_deleted. the command. The file cannot be deleted. Ensure the file exists. Retry CTJOP0133E The following directory is not empty: directory_name. deleted. If the directory is not empty, it cannot be Ensure the directory is empty. Retry the command. CTJOP0134E The following directory has not been deleted: directory_name. command. The attempt to delete the directory fails. Correct the error. Retry the CTJOP0135E The following field is not recognized as an array: field_not_recognized_as_array. The field specified is an array and must have the [] array notation. Add the array notation [] to the query. Retry the command. CTJOP0136E The following field is not an array: not_an_array. Do not use the array notation ([]). The field specified is not an array. Do not use the [] array notation. Remove the [] array notation from the query. Retry the command. CTJOP0137E The field, field_name, is not found in the class class. class. attribute for the class. The field is not a valid attribute for the Correct the field to be a valid CTJOP0140E The query expression contains the following invalid operand: VALUE_0. The operand is not valid. The valid string operands are equals, not-equals, starts-with, ends-with, contains, not-contains, is-null and is-not-null, and instanceof. The valid numeric operands are "==", "!=", "<", "<=", ">", ">=". the command. CTJOP0141E The JDBC URL is null. Correct the operand. Retry The JDBC driver URL specified for the database driver is null. Ensure the JDBC driver is not null. Retry the command. CTJOP0150E There is an error in Props.verifyPropertyFileLoad. The application cannot load the following property file: file_name. The system cannot access the collation.properties file. Ensure the TADDM Server is running and that it is available. Ensure the collation.properties file is located in the correct directory. CTJOP0152E There is an error in Props.getHome. The application cannot derive com.collation.home from VALUE_0. The system cannot access the collation.properties file. Ensure the TADDM Server is running and that it is available. Ensure the collation.properties file is located in the correct directory. CTJOP0154E The file does not exist. The system cannot access the localized file, searching lang_country_variant, lang_country, lang, and without any language specification. Ensure the file, or one of the NLS variations is available. CTJOP0155E SecurityException obtaining the security provider list. The system cannot obtain the list of Java security providers. Ensure that the TADDM-provided IBM JRE is being used. Message reference 5

16 CTJOP0156E CTJOP0169E CTJOP0156E Encryption key already exists. A new encryption key cannot be generated if one already exists, since TADDM data may already encrypted with this key. Use updatekey.sh or updatekey.bat to change the encryption key and migrate encrypted data to use the new key. CTJOP0157E Error using IBMJCEFIPS provider. An attempt to use the IBMJCEFIPS security provider failed, resulting in a NoSuchProviderException. Ensure that the TADDM-provided IBM JRE is being used. CTJOP0158E Error using the AES cryptographic algorithm. An attempt to use the AES cryptographic algorithm failed, resulting in a NoSuchAlgorithmException. Ensure that the TADDM-provided IBM JRE is being used. CTJOP0159E A cryptographic error occurred. An attempt to use the AES cryptographic algorithm from the IBMJCEFIPS security provider failed, resulting in a NoSuchPaddingException. Ensure that the TADDM-provided IBM JRE is being used. CTJOP0160E A cryptographic error occurred. An attempt to use the AES cryptographic algorithm from the IBMJCEFIPS security provider failed, resulting in an InvalidKeyException. Ensure that the TADDM-provided IBM JRE is being used. CTJOP0163E A cryptographic error occurred. An attempt to use the AES cryptographic algorithm from the IBMJCEFIPS security provider failed, resulting in an IOException. Ensure that the TADDM-provided IBM JRE is being used. CTJOP0164E A cryptographic error occurred. An attempt to use the AES cryptographic algorithm from the IBMJCEFIPS security provider failed, resulting in a ClassNotFoundException. Ensure that the TADDM-provided IBM JRE is being used. CTJOP0165E An IO error occurred while loading the TADDM cryptographic key. An attempt to load the TADDM cryptographic key failed, resulting in an IOException. Ensure that the key file exists in the location specified by com.collation.security.key. CTJOP0166E An error occurred while loading the TADDM cryptographic key. An attempt to load the TADDM cryptographic key failed, resulting in a ClassNotFoundException. Ensure that the key file exists in the location specified by com.collation.security.key. CTJOP0167E An IO error occurred while saving the TADDM cryptographic key. An attempt to save the TADDM cryptographic key failed, resulting in an IOException. Ensure that the key file location specified by com.collation.security.key is writable by the TADDM system user. CTJOP0161E A cryptographic error occurred. An attempt to use the AES cryptographic algorithm from the IBMJCEFIPS security provider failed, resulting in an InvalidKeyException. Ensure that the TADDM-provided IBM JRE is being used. CTJOP0162E A cryptographic error occurred. An attempt to use the AES cryptographic algorithm from the IBMJCEFIPS security provider failed, resulting in an IllegalBlockSizeError. Ensure that the TADDM-provided IBM JRE is being used. CTJOP0168E An attempt to read an encrypted object from an XML file failed. An attempt to read an encrypted object from an XML file failed, resulting in an exception. CTJOP0169E An attempt to write an encrypted object to an XML file failed. An attempt to write an encrypted object to an XML file failed, resulting in an exception. 6 Application Dependency Discovery Manager: Messages

17 CTJOP0170E CTJOT0015E CTJOP0170E An attempt to write an encryption key to a file failed. The specified com.collation.security.key is a directory. Ensure that the key file location specified by com.collation.security.key is a filename and relative path within the TADDM directory. CTJOP0171W Location tag value is set, but location tagging is disabled. Location tag value is set, but location tagging is disabled. To enable it set com.ibm.cdb.locationtaggingenabled parameter in collation.properties. CTJOP0172W Location tag exceeds maximum length: VALUE_0. Location tag truncated to: VALUE_1 Too long location tag was specified. CTJOP0173W Unable to send PDU packet on VALUE_0 SNMP operation failed CTJOT Messages for the CTJOT component. Topology Manager messages CTJOT0000E The cluster has no elements. CTJOT0010E An error occurs when attempting to delete the following object: object_not_deleted. The object is referenced by the following business service: business_service. The removeobject method fails because the object is contained in the business service. In addition, the force flag is not specified. Operator response: Delete the object from the business service before trying to remove the object, or specify the force flag. CTJOT0011E An error occurs when attempting to delete the following object: object_not_deleted. The object is referenced by the following application: application. The removeobject method fails because the object is contained in the application. In addition, the force flag is not specified. Operator response: Delete the object from the application before trying to remove the object, or specify the force flag. CTJOT0012E An error occurs when attempting to delete the following object: object_not_deleted. The object is referenced by the following cluster: cluster. The removeobject method fails because the object is contained in the cluster. In addition, the force flag is not specified. Operator response: Delete the object from the cluster before trying to remove the object, or specify the force flag. CTJOT0013E The component is not found. One of the components specified for the application definition is not a valid component. Application components must be one of the following items: an Application Server, an Application Server Cluster, a Software Module, a Software Resource, or a Computer System. Operator response: Create the object to be added to the application, or delete it from the application definition. CTJOT0014E The application name is not set. not set. Operator response: a name attribute. The name attribute of the application is Update the application to include CTJOT0015E The following component type is not valid: component_type_not_valid. The following list identifies valid application component types: Application Server, Application Server Cluster, Software Module, Software Resource, or Computer System. Operator response: Specify a valid component to be added to the application. Message reference 7

18 CTJOT0016E CTJOT0035E CTJOT0016E The following component type is not valid: component_type_not_valid. The following list identifies valid business service component types: Application Server, Application Server Cluster, Software Module, Software Resource, Computer System, or IT System. Operator response: Specify a valid component to be added to the business service. CTJOT0017E An error occurs when attempting to delete the following object: object_not_deleted. The object is referenced by the following relationships: relationships. The removeobject method fails because the object is contained in the relationship, and the force flag is not specified. Operator response: Delete the object from the relationship before trying to remove the object, or specify the force flag. CTJOT0018E An error occurs when attempting to delete the following object: object_not_deleted. The object is referenced by the following collections: collections. The removeobject method fails because the object is contained in the collection, and the force flag is not specified. Operator response: Delete the object from the collection before trying to remove the object, or specify the force flag. CTJOT0019E The following Extended Attributes were not defined for objclass : collection. The Extended Attributes were not stored in the database because they were not defined. Only defined Extended Atributes are stored in the database. Operator response: Define the Extended Attributes that are missing and save the Extended Attributes again. CTJOT0020E The session times out. CTJOT0021E The authorization did not complete. CTJOT0022E The scope is read-only. CTJOT0030E An error occurred. The call to close the connection to the Persistence Manager fails, or an invalid parameter is detected in the Topomgr security check. available. Ensure the TADDM Server is CTJOT0031E The user is not authorized to edit the roles and permissions. Administrator privileges are required to edit roles and permissions. The current user is not an administrator. Operator response: To edit the roles and permissions, log in as an administrator. CTJOT0032E The session times out. The merge object function did not complete before timing out. available. Ensure the TADDM Server is CTJOT0033E The user is not authorized to edit the scope. edit scopes. The Discover permission is required to Operator response: To edit the scopes, log in as a user with Discover permission. CTJOT0034E The user does not have the following permissions: permissions to the object with the following GUID: guid The user requires authorization to read or modify the object, or both. Operator response: Log in with a user ID that has the necessary permissions. CTJOT0035E The object that you are attempting to update does not have all its attributes set. occur. available. If the server is unavailable, this error can Ensure the TADDM Server is 8 Application Dependency Discovery Manager: Messages

19 CTJOT0036E CTJOT0079E CTJOT0036E The user is not authorized to create objects. The Discover permission is required to create objects. Operator response: To create objects, log in with a user ID that has the Discover permission. CTJOT0040E The session timed out. CTJOT0041E The authorization did not complete.. CTJOT0042E This version exists. CTJOT0054E An error occurs during SQL file parsing: VALUE_0. CTJOT0055E The SQL statement cannot be run: VALUE_0. Exception: VALUE_1. CTJOT0056E The result set for the statement cannot be closed: VALUE_0. Exception: VALUE_1. CTJOT0057E The statement cannot be closed for the following object: VALUE_0. Exception: VALUE_1. CTJOT0059E The SQL procedure cannot be run: VALUE_0. Exception: VALUE_1. CTJOT0060E The statement cannot be closed for the following object: VALUE_0. Exception: VALUE_1. CTJOT0068E mig_create_migration_procedure.1 Create migration procedure CTJOT0069E mig_create_migration_procedure.2 Create migration procedure CTJOT0070E mig_execute_cursor_migration.1 Create view CTJOT0071E mig_execute_cursor_migration.2 View created CTJOT0072E mig_execute_cursor_migration.3 Create procedure CTJOT0073E mig_execute_cursor_migration.4 Procedure created CTJOT0074E mig_execute_cursor_migration.5 Run migration procedure CTJOT0075E mig_execute_cursor_migration.6 Migration procedure run CTJOT0076E mig_execute_cursor_migration.7 Drop view CTJOT0077E mig_execute_cursor_migration.8 View dropped CTJOT0078E mig_execute_cursor_migration.9 Drop procedure CTJOT0079E mig_execute_cursor_migration.10 Procedure dropped Message reference 9

20 CTJOT0080E CTJOT0102E CTJOT0080E Primary key violation occurs during SQL execution. Switch to cursor migration. CTJOT0092E mig_execute_statement_migration.8 DML single statement migration has completed CTJOT0081E Transaction log is full. Switch to cursor migration. CTJOT0082E Ignored exception undefined object name CTJOT0083E Undefined object name CTJOT0084E mig_execute_statement_migration.1 Preparing to run the SQL statement CTJOT0085E mig_execute_statement_migration.2 Single statement DDL operation CTJOT0087E mig_execute_statement_migration.3 Single statement DDL operation - complete CTJOT0088E mig_execute_statement_migration.4 DML operation CTJOT0089E mig_execute_statement_migration.5 Performing DML operation using cursor in a procedure CTJOT0093E mig_execute_statement_migration.9 Records affected by the DML operation: 0. Operation skipped CTJOT0094E mig_add_column_to_table.1 Cannot directly alter the table. Recreating table. CTJOT0095E mig_add_column_to_table.2 Rename table CTJOT0096E mig_add_column_to_table.3 Create new table CTJOT0097E mig_add_column_to_table.4 Table created CTJOT0098E mig_add_column_to_table.5 Prepare to move data to the new table CTJOT0099E mig_add_column_to_table.6 Data inserted with a single SQL statement CTJOT0100E mig_execute_migration.12 Migration to the specified version is already complete CTJOT0090E mig_execute_statement_migration.6 DML cursor migration has completed CTJOT0091E mig_execute_statement_migration.7 Performing DML operation using single SQL statement CTJOT0101E mig_execute_migration.0 Dropping view CTJOT0102E mig_execute_migration.10 Migration successful 10 Application Dependency Discovery Manager: Messages

21 CTJOT0103E CTJOT0204E CTJOT0103E mig_execute_migration.11 Migration has not completed CTJOT0104E Exception during SQL statement execution CTJOT0115E A primary key violation occurs during SQL execution. Switch to cursor migration. CTJOT0116E The name is being used by an object. CTJOT0105E Migration to the specified version is already complete CTJOT0106E The specified version does not exist. CTJOT0107E Preparing to run the SQL statement. CTJOT0108E Single statement DDL operation CTJOT0109E Single statement DDL operation - complete CTJOT0110E DML operation CTJOT0117E Column list is indexed. CTJOT0118E The index does not exist. CTJOT0119E Migration is successful. CTJOT0120E Migration is not complete. CTJOT0121E Running the runstats command on a table. CTJOT0200E A connection to the database is not available: VALUE_0. CTJOT0111E Number of records affected by the current SQL statement. CTJOT0201E The JDBC driver is not loaded: VALUE_0. VALUE_1 CTJOT0112E DML cursor migration has completed CTJOT0113E Number of records affected by the current SQL statement. CTJOT0114E DML single statement migration has completed CTJOT0202E SQLException information: VALUE_0, SQLSTATE: VALUE_1, Error code: VALUE_2. CTJOT0203E The connection to the database cannot be closed: VALUE_0. Exception: VALUE_1 CTJOT0204E The record limit for SQL operations is not valid. Exception: VALUE_0 Message reference 11

22 CTJOT0205E CTJOT0307I CTJOT0205E This version is installed. Wait until the discovery or bulk load operation has completed, and then run the command again. CTJOT0206E An error occurs during the upgrade: VALUE_0 CTJOT0207E The default classfile does not exist. Skipping GUIDs migration by class. CTJOT0208E The properties are not loaded. CTJOT0209E Dropping nonexistent primary key - operation ignored CTJOT0210E Column being added already exists in table CTJOT0211E migration.execute_migration.i.ce: Column being added already exists in table CTJOT0212E Cannot roll back changes made in database transaction: VALUE_0. Exception: VALUE_1 CTJOT0300I AdjustL1Networks has started. The command that adjusts L1 network assignments has started. None CTJOT0301I AdjustL1Networks has completed. The command that adjusts L1 network assignments has completed. None CTJOT0302W The system is currently busy, and the adjustl1networks command cannot be run. The adjustl1networks command cannot run while a discovery or bulk load operation is in progress. CTJOT0303E An unexpected error occurred while running the adjustl1networks command. The command did not complete successfully. This error indicates a serious problem with the TADDM server or database. Check the log files for any additional messages the might indicate the problem. Correct any problems, restart the TADDM server, and try the operation again. CTJOT0304E The IpNetwork object with subnet address of subnet_address and netmask of subnet_address could not be created. An error occurred while storing an IpNetwork object in the database. This might indicate a database problem. Check the database configuration. Correct any problems and try the operation again. CTJOT0305E The IpInterface object with IP address of IP_address could not be created. An error occurred while storing an IpInterface object in the database. This might indicate a database problem. Check the database configuration. Correct any problems and try the operation again. CTJOT0306I Checking existing IpNetwork object with subnet address of subnet_address and netmask of netmask. The program that adjusts L1 network assignments is examining existing IpNetworks. None CTJOT0307I Creating new IpNetwork object with subnet address of subnet_address and netmask of netmask. The program that adjusts L1 network assignments is creating new IpNetworks. None 12 Application Dependency Discovery Manager: Messages

23 CTJOT0308W CTJOT0506E CTJOT0308W The adjustl1networks command is not supported on the synchronization server. The adjustl1networks command cannot be run on an synchronization server, because there might be unneeded Network objects after domain server synchronization. domain servers. Run the program on the CTJOT0400I Topology builder is starting. The topology builder service is starting. CTJOT0401I Topology builder is stopping. The topology builder service is stopping. CTJOT0402I Topology builder agent agent_name is starting. starting. The specified topology builder agent is CTJOT0403I Topology builder agent agent_name is stopping. stopping. The specified topology builder agent is CTJOT0404E An error occurred while running the agent_name topology builder agent: error_message. The specified topology builder agent did not complete successfully. CTJOT0405E An error occurred during the topology builder process: error_message. The topology builder process did not complete successfully. CTJOT0406I Value for property: property_name not found in db2zos.xml configuration file. ALTER statements will not be generated. The ALTER generator cannot generate ALTER statements because does not have required property value set up in db2zos.xml configuration file. To generate ALTER statements provide required values in db2zos.xml configuration file and try again. CTJOT0500E XML Schema definition file is missed. accessible. XML Schema definition file is not Make sure that XML Schema definition file is accessible. CTJOT0501E Unable to initialize schema validator for BizApps. Error occurred during parsing the specified file as a schema. definition file is valid. Make sure that XML Schema CTJOT0502E Unable to initialize XML parser for BizApps. Error occurred during using factory to get an instance of DocumentBuilder. be created. A DocumentBuilder cannot CTJOT0503E The XML file xml_file is not valid. According to the XML Schema the specified XML file is not valid. Make sure that the specified XML file is valid according to the XML Schema definition file. CTJOT0504E An error occurred during processing the file: xml_file The specified XML file parsing did not complete successfully. XML file is valid. Make sure that the specified CTJOT0505E Initialization of BizAppsAgent failed. An error occurred while initializing BizAppsAgent. Check the log files for any additional messages that might indicate the cause of the problem. CTJOT0506E An error occurred during traversing BizApps directory: xml_directory An error occurred while traversing a specific BizApps directory. Check the log files for any additional messages that might indicate the cause of the problem. Message reference 13

24 CTJOT0507E CTJOT0700E CTJOT0507E An error occurred during processing grouping pattern "name" (guid: guid). Check the log files for the detailed messages. An error occurred while processing a specific BizApp. Check the log files for any additional messages that might indicate the cause of the problem. CTJOT0508E Topology builder agent error occurred. Check the log files for the detailed messages. successfully. Topology builder agent did not complete Check the log files for any additional messages that might indicate the cause of the problem. CTJOT0509W An error occurred during loading of one or more CIs. Check the log files for the detailed messages. Business service agent could not load a CI for the given GUID. Check the log files for any additional messages that might indicate the cause of the problem. Check whether the given CI exists in the TADDM database. CTJOT0510E An error occurred during setting the grouping pattern "name" (guid: guid) status. Check the log files for the detailed messages. status. An error occurred while setting the Check the log files for any additional messages that might indicate the cause of the problem. CTJOT0600I MssObjLinkCleanupAgent has already run within the last days_between_runs days since server start. CTJOT0602I Removed links_to_remove orphaned MSSOBJLINK_REL records. CTJOT0603I No orphaned MSSOBJLINK_REL records found. CTJOT0610W Unable to remove one or more orphaned MSSOBJLINK_REL records. The attempt to delete a batch of MSSOBJLINK_REL records failed due to a likely database error. The error may be temporary, not repeatable, and the orphaned MSSOBJLINK_REL records will be deleted the next time the agent runs. Check the TopologyBuilder.log for more details about the error. Reconfiguration of the database or JDBC connection may be required. CTJOT0620E Cannot connect to database. No JDBC connections are currently available. Number of JDBC connections to the database has been exceeded, or some other database error has occurred. Check the TopologyBuilder.log for more details about the error. Reconfiguration of the database or JDBC connection may be required. CTJOT0621E Unable to prepare SQL statement for execution: sql_statement The SQL statement may be invalid, or some other database error has occurred. Check the TopologyBuilder.log for more details about the error. CTJOT0622E Unable to complete database query for orphaned MSSOBJLINK_REL records. A JDBC or database error has occurred. Check the TopologyBuilder.log for more details about the error. CTJOT0601I Found links_to_remove orphaned MSSOBJLINK_REL records to remove. CTJOT0700E Error processing agents. 14 Application Dependency Discovery Manager: Messages

25 CTJOT0700W CTJOT0715I CTJOT0700W Unexpected error creating dependency between source and destination. CTJOT0705I Creating App2App dependency between source and destination. CTJOT0701E Creating SystemToSystem dependency between source and destination. CTJOT0705W Unable to queue NetworkConnection for storage. CTJOT0701I Waiting for DependencyWriters to shutdown. CTJOT0701W Unable to queue dependency for storage. CTJOT0702E Unknown relation type reltype CTJOT0702I Creating NetworkConnection between source and destination. CTJOT0702W Guid not set. CTJOT0703E LDAPDependencyAgent.run() failed. CTJOT0706W Unable to resolve location tag CTJOT0707W Could not find cs in the cache for ip_addr CTJOT0708W Unexpected Exception. CTJOT0709W Unexpected exception searching for processes. CTJOT0710I Regenerating aliases... CTJOT0711I The alias recalculation tool already completed successfully. CTJOT0703I Creating Sys2App dependency between source and destination. CTJOT0712I Skipping the running of the alias regeneration tool CTJOT0703W Object returned by getjdoinstance is not a ModelObject: var CTJOT0713E Alias generation failed due to the following error: variable0. CTJOT0704I Creating App2Sys dependency between source and destination. CTJOT0704W Unexpected AttributeNotSetException. CTJOT0714I Processing data provider variable0. CTJOT0715I Aliases processed variable0. Message reference 15

26 CTJOT0716I CTJOT0742E CTJOT0716I Processing dependent aliases variable0. CTJOT0717I Dependent aliases processed variable0. CTJOT0718I Searching for duplicates. CTJOT0719I Records removed from variable0 : variable1. CTJOT0720I The number of inheritance mapping orphans found: variable0. CTJOT0721I Searching for possible over merges. CTJOT0722E Failed to initialize NRS. CTJOT0729I The number of records updated: variable0. CTJOT0730I Searching for broken relationships for the class name: variable0 [variable1/variable2]. CTJOT0731I Searching for switching guids. This might take a while, please wait. CTJOT0732I Switching guids summary: variable0. CTJOT0733I variable0, the total number of guid switches: variable1\n. CTJOT0734I The total number of guid switches summary per class:\n. CTJOT0723I No over merges found. CTJOT0724I Possible over merges found: CTJOT0725I The total number of over merges found: variable0. CTJOT0735I Switching guids found: variable0. See the verify-data.log for details. CTJOT0737E Invalid parameter: variable0. CTJOT0739E Unable to create JDBC connections. CTJOT0726I The number of inconsistent records in relationships found: variable0. CTJOT0727I The number of dependent objects found: variable0. CTJOT0728I The number of records deleted: variable0. CTJOT0740I JDBC connections created. CTJOT0741E Invalid data to form a Guid: variable0.variable1. CTJOT0742E Not able to recreate degenerated master alias for object with the GUID variable0. 16 Application Dependency Discovery Manager: Messages