Explanation | The named property file could not be located. |
Action | Supply the correct location of the property file. |
Explanation | The column and string delimiters cannot be the same. |
Action | Supply different characters for the column and string delimiters. |
Explanation | The tModel for the given key cannot be found. |
Action | Supply a correct tModel key. |
Explanation | A command argument has been supplied that is unknown. |
Action | Check your arguments with the usage information in the accompanying message. |
Explanation | Two unique tModel keys are required to move a value set from one tModel to another. |
Action | Supply two unique tModel keys. |
Explanation | The named value set file could not be located. |
Action | Supply the correct location of the value set file. |
Explanation | The line at the line number shown has a starting string delimiter, but not a finishing one. |
Action | Correct the line, or consider using a different string delimiter (-stringDelimiter). |
Explanation | The line at the line number shown does not contain enough fields. |
Action | Correct the line, or consider using a different column delimiter (-columnDelimiter). |
Explanation | The line at the line number shown contains too many fields. |
Action | Correct the line, or consider using a different column delimiter (-columnDelimiter). |
Explanation | The value set data file contains two or more codes of the same value with the same parent code. |
Action | Correct the line. See the Information Center information about user-defined value sets for more details. |
Explanation | The value set data file contains a parent code that is invalid in its context. |
Action | Correct the parent key code. See the Information Center information about user-defined value sets for more details. |
Explanation | The value set data file contains a value that is too large. |
Action | Decrease the size of the value. See the Information Center information about user-defined value sets for more details. |
Explanation | An IO Exception was received when trying to read the value set file. |
Action | Ensure that the value set file is readable and is in UTF-8 format. See the Information Center information about user-defined value sets for more details. |
Explanation | An IO Exception was received when trying to read the properties file. |
Action | Ensure that the properties file is readable and is in UTF-8 format. |
Explanation | The value set file is not in UTF-8 format. |
Action | Correct the file encoding format. See the Information Center information about user-defined value sets for more details. |
Explanation | The UDDI application could not be contacted. |
Action | Ensure that UDDI is installed and running on the host you have targeted. See the arguments -host, -port, -node, and -server. |
Explanation | An unexpected exception was detected. |
Action | Examine the Exception stack trace to determine its cause. |
Explanation | The targeted tModel has a status of checked, therefore you must use care if you change its value set. |
Action | To confirm this operation, enter the command with the -override argument. |
Explanation | The targeted tModel to be loaded already has a value set. |
Action | To confirm this operation and overwrite the existing value set, enter the command with the -override argument. |
Explanation | A UDDI Registry message was received. |
Action | Examine the message to determine its cause. |
Explanation | This message is for informational purposes only. It confirms the number of value set lines loaded for the tModel. |
Action | No action is required. |
Explanation | This message is for informational purposes only. It confirms the change of value set from one tModel to another. |
Action | No action is required. |
Explanation | This message is for informational purposes only. It confirms the removal of the value set for the tModel. |
Action | No action is required. |