Explanation | This is the usage message displayed at the command line when the user has entered a combination of arguments or options that were not valid. |
Action | Enter the command according to the usage message. |
Explanation | This message is used as a marker in the message log file to indicate when the tool starts. |
Action | None. |
Explanation | Indicates the import function has started. |
Action | None. |
Explanation | Indicates the delete function has started. |
Action | None. |
Explanation | Indicates that the tModel with the specified key has bean imported. |
Action | None. |
Explanation | Indicates that reading of the canonical tModel XML file and creation of the tModels has started. |
Action | None. |
Explanation | Indicates that reading of the canonical tModel XML file and creation of the tModels has completed successfully. |
Action | None. |
Explanation | Indicates the requested function completed successfully. |
Action | None. |
Explanation | The XML parser reports a warning about the content of the canonical tModel XML file. |
Action | Based on the context of the warning message, check the validity of the canonical tModel XML file. |
Explanation | The XML parser reports an error about the content of the canonical tModel XML file. |
Action | Based on the context of the error message, check the validity of the canonical tModel XML file. |
Explanation | A parser feature set by the Canonical TModel Import Tool is not recognized by the parser. |
Action | Check you are using the correct type and level of XML parser. If correct, contact your IBM support center. |
Explanation | A parser feature set by the Canonical TModel Import Tool is not supported by the parser. |
Action | Check you are using the correct type and level of XML parser. If correct, contact your IBM support center. |
Explanation | A parser property set by the Canonical TModel Import Tool is not recognized by the parser. |
Action | Check you are using the correct type and level of XML parser. If correct, contact your IBM support center. |
Explanation | A parser property set by the Canonical TModel Import Tool is not supported by the parser. |
Action | Check you are using the correct type and level of XML parser. If correct, contact your IBM support center. |
Explanation | Canonical TModel Import Tool cannot locate the configuration file. |
Action | Canonical TModel Import Tool looks for a default configuration properties file with the file name 'UDDICanonicalTModelImportTool.properties' in the current directory. Check that the configuration file has this name and exists in the execution directory. |
Explanation | The configuration file could not be read. |
Action | Check the file path points to a valid file and that the current user has permission to read the file. |
Explanation | A required property is missing from the configuration file. |
Action | Add the missing property name and value to the configuration file. Check that the property name is not misspelled. |
Explanation | A value was given to a property other than 'true' or 'false'. |
Action | Set the property value to 'true' or 'false'. |
Explanation | A value was given to a property other than an integer value. |
Action | Set the property value to an integer value. |
Explanation | The canonical tModel XML file could not be read due to an IO error. |
Action | Check that the current user has permission to read the file. |
Explanation | The attempt to close the message log file failed. |
Action | The disk might be full. If so, clear some space or direct log output to a different disk. |
Explanation | The attempt to close the trace log file failed. |
Action | The disk might be full. If so, clear some space or direct log output to a different disk. |
Explanation | The Canonical TModel Import Tool logger could not find the specified file. |
Action | Ensure the trace file is correctly defined in the configuration properties file. |
Explanation | Canonical TModel Import Tool was invoked with no function specified. |
Action | Specify one function in accordance with the usage message. |
Explanation | The argument value does not match any of the allowed arguments. |
Action | Specify arguments in accordance with the usage message. |
Explanation | The specified database driver could not be loaded. |
Action | Check the database driver value in the configuration file is valid, and the driver's class is present on the class path. |
Explanation | A connection could not be established with the database at the specified URL with the specified userid. |
Action | Check the database URL, userid and password values are correct in the configuration file, and that the database manager is running. |
Explanation | An unspecified error occurred when parsing the canonical tModel XML file. |
Action | Check the canonical tModel XML file content is valid according to the Canonical TModel Import Tool schema file. Reference the information center for details. |
Explanation | Errors occurred when parsing the canonical tModel XML file. |
Action | Check the canonical tModel XML file content is valid according to the Canonical TModel Import Tool schema file. Reference the information center for details. |
Explanation | Warnings occurred when parsing the canonical tModel XML file. |
Action | Check the canonical tModel XML file content is valid according to the Canonical TModel Import Tool schema file. Reference the information center for details. |
Explanation | An unexpected error occurred. |
Action | Check configuration file settings and all databases are active. If necessary, contact your IBM support center. |
Explanation | A tModel contained in the canonical tModel XML file already exists in the UDDI Registry, the import request for this tModel is ignored. |
Action | Ignore the warning or use the delete function to remove the tModel and then import. |
Explanation | Indicates the tModel was successfully removed from the UDDI registry database. |
Action | None. |
Explanation | An unexpected SQL Exception has been encountered. |
Action | Examine the SQL Exception Message to determine the cause of the problem. |
Explanation | An unexpected SQL Exception has been encountered whilst trying to commit the database changes. |
Action | Examine the SQL Exception Message to determine the cause of the problem. |
Explanation | An unexpected SQL Exception has been encountered whilst trying to rollback the database changes. |
Action | Examine the SQL Exception Message to determine the cause of the problem. |
Explanation | An unexpected SQL Exception has been encountered whilst trying to set autocommit off. |
Action | Examine the SQL Exception Message to determine the cause of the problem. |