Problem | The named property file could not be located. |
User response | Supply the correct location of the property file. |
Problem | The column and string delimiters can not be the same. |
User response | Supply different characters for the column and string delimiters. |
Problem | The tModel for the given key can not be found. |
User response | Supply a correct tModel key. |
Problem | A command argument has been supplied that is unknown. |
User response | Check your arguments with the Usage information given with this error message. |
Problem | Two unique tModel keys are required to move a Value Set from one tModel to another. |
User response | Supply two unique tModel keys. |
Problem | The named value set file could not be located. |
User response | Supply the correct location of the value set file. |
Problem | The line at <Line Number> has a starting string delimiter, but not a finishing one. |
User response | Correct the line, or consider using a different string delimiter (-stringDelimiter). |
Problem | The line at <Line Number> does not contain enough fields. |
User response | Correct the line, or consider using a different column delimiter (-columnDelimiter). |
Problem | The line at <Line Number> contains too many fields. |
User response | Correct the line, or consider using a different column delimiter (-columnDelimiter). |
Problem | The Value Set file contains two or more Key Codes of the same value for the same parent key code. |
User response | Correct the line. |
Problem | The Value Set file contains a parent key code that is invalid in its context. |
User response | Correct the parent key code. |
Problem | The Value Set file contains a value that is too large. |
User response | Decrease the size of the value. |
Problem | An IO Exception was received when trying to read the Value Set file. |
User response | Ensure the Value Set file is readable and is in UTF-8 format. |
Problem | An IO Exception was received when trying to read the properties file. |
User response | Ensure the properties file is readable and is in UTF-8 format. |
Problem | The Value Set file is not in UTF-8 format. |
User response | Correct the file encoding format. |
Problem | The UDDI application could not be contacted. |
User response | Ensure UDDI is installed and running on the Host you have targeted. See arguments -host, -port, -node, and -server. |
Problem | An unexpected exception was received. |
User response | Examine the Exception stack trace on its cause. If the problem cannot be resolved, contact your IBM Customer Service Center. |
Problem | The targeted tModel has a "checked" status and therefore should not have its value set changed without care. |
User response | To confirm this operation, enter the command with the -override argument. |
Problem | The targeted tModel to be loaded already has a value set. |
User response | To confirm this operation and over write the existing value set, enter the command with the -override argument. |
Problem | A UDDI Registry message was received. |
User response | Examine the message on its cause. If the problem cannot be resolved, contact your IBM Customer Service Center. |
Problem | An informational message that confirms the number of value set lines loaded for the tModel. |
User response | None. |
Problem | An informational message that confirms the change of value set from one tModel to another. |
User response | None. |
Problem | An informational message that confirms the removal of the value set for the tModel. |
User response | None. |