|
|
|
Reason:
This message is issued if a null value is given in xml.
Action:
The program exits. Put the correct value in xml, and then restart the transfer.
Reason:
This message is issued if the XCOM Ping action is performed with TRNENCRL_CIPHER value set to COMPAT.
Action:
Retry XCOM Ping action with TRNENCRL_CIPHER value set to ciphers other than COMPAT. See the list of ciphers allowed for TRNENCRL_CIPHER.
Reason:
Malformed characters were detected during Unicode conversion.
Action:
None. The detected malformed characters can be found in the transfer trace.
Reason:
Malformed characters detected during Unicode conversion were substituted.
Action:
None. The detected malformed characters can be found in the transfer trace.
Reason:
Malformed characters detected during Unicode conversion were skipped.
Action:
None. The detected malformed characters can be found in the transfer trace.
Reason:
CARRIAGE_FLAG=XPACK is automatically set for Unicode transfer.
Action:
None
Reason:
Summary of Unicode conversion is written in the trace.
Action:
None
Reason:
Block I/O is not supported for Unicode transfer. Hence Block I/O has been disabled internally.
Action:
None
Reason:
Unicode converter is opened successfully for Unicode transfer.
Action:
None. The name of the charset, canonical name and CCSID (if available) of the charset opened for Unicode transfer can be found in the trace.
Reason:
The remote partner returned an error indicating that the Unicode transfer (CODE_FLAG=UTF8 or CODE_FLAG=UTF16) is not supported by that version of CA XCOM Data Transport.
Action:
Upgrade the remote CA XCOM Data Transport.
Reason:
Failed to load ICU (International Components for Unicode) Library required for Unicode transfer.
Action:
Check if your CA XCOM Data Transport installation is valid. The ICU library will be installed by CA XCOM Data Transport installer. Retry the operation. If the problem persists contact CA Technical Support.
Reason:
CA XCOM Data Transport API (XcomAPI) returns this error code when the local_delim contains an invalid value.
Action:
Correct the value of the local_delim XCOM API member passed to XcomAPI routine. See the list of supported delimiters for local_delim in Application Programming Interface chapter in this guide.
Reason:
CA XCOM Data Transport API (XcomAPI) returns this error code when the remote_delim parameter contains an invalid value.
Action:
Correct the value of the remote_delim XCOM API member passed to the XcomAPI routine. See the list of supported delimiters for remote_delim in the Application Programming Interface chapter in this guide.
Reason:
CA XCOM Data Transport API (XcomAPI) returns this error code when the mbcs_inputerror parameter contains an invalid value.
Action:
Correct the value of the mbcs_inputerror XCOM API member passed to the XcomAPI routine. See the list of correct formats for mbcs_inputerror in the Application Programming Interface chapter in this guide.
Reason:
CA XCOM Data Transport API (XcomAPI) returns this error code when the mbcs_inputerror parameter contains an invalid value.
Action:
Correct the value of the mbcs_inputerror XCOM API member passed to the XcomAPI routine. See the list of correct formats for mbcs_inputerror in the Application Programming Interface chapter in this guide.
Reason:
CA XCOM Data Transport API (XcomAPI) returns this error code when the mbcs_inputerror parameter contains an invalid value.
Action:
Correct the value of the mbcs_inputerror XCOM API member passed to the XcomAPI routine. See the list of correct formats for mbcs_inputerror in the Application Programming Interface chapter in this guide.
Reason:
CA XCOM Data Transport API (XcomAPI) returns this error code when the mbcs_converror parameter contains an invalid value.
Action:
Correct the value of the mbcs_converror XCOM API member passed to the XcomAPI routine. See the list of correct formats for mbcs_converror in the Application Programming Interface chapter in this guide.
Reason:
CA XCOM Data Transport API (XcomAPI) returns this error code when the mbcs_converror parameter contains an invalid value.
Action:
Correct the value of the mbcs_converror XCOM API member passed to the XcomAPI routine. See the list of correct formats for mbcs_converror in the Application Programming Interface chapter in this guide.
Reason:
CA XCOM Data Transport API (XcomAPI) returns this error code when the mbcs_converror parameter contains an invalid value.
Action:
Correct the value of the mbcs_converror XCOM API member passed to the XcomAPI routine. See the list of correct formats for mbcs_converror in the Application Programming Interface chapter in this guide.
Reason:
Failed to open Unicode converter for the Unicode transfer (CODE_FLAG=UTF8 or CODE_FLAG=UTF16).
Action:
Check the LOCAL_CHARSET, REMOTE_CHARSET or DEFAULT_CHARSET values. See the list of charsets supported in the Appendix chapter in this guide.
Reason:
Failed to open Unicode converter for the Unicode transfer (CODE_FLAG=UTF8 or CODE_FLAG=UTF16).
Action:
Check the LOCAL_CHARSET, REMOTE_CHARSET or DEFAULT_CHARSET values. See the list of charsets supported in the Appendix chapter in this guide.
Reason:
Failed to open the Unicode converter for translating the Unicode data to the negotiated Unicode encoding internally.
Action:
Retry the operation. If the problem persists, contact CA Technical Support.
Reason:
Failed to allocate the memory required for Unicode conversion.
Action:
Retry the operation. If the problem persists, contact CA Technical Support.
Reason:
The replacement character specified with the MBCS_CONVERROR=REPLACE#nnnnnn option is not a valid Unicode character.
Action:
Specify a valid Unicode character in the decimal value for the MBCS_CONVERROR=REPLACE#nnnnnn option.
Reason:
The replacement character specified with the MBCS_INPUTERROR=REPLACE#nnnnnn option is not a valid Unicode character.
Action:
Specify a valid Unicode character in the decimal value for the MBCS_INPUTERROR=REPLACE#nnnnnn option.
Reason:
The replacement character specified with the MBCS_CONVERROR=REPLACE#nnnnnn option cannot be converted to the specified charset.
Action:
Specify a valid Unicode character in the decimal value for the MBCS_CONVERROR=REPLACE#nnnnnn option which can be converted to the charset.
Reason:
The replacement character specified with the MBCS_INPUTERROR=REPLACE#nnnnnn option cannot be converted to the specified charset.
Action:
Specify a valid Unicode character in the decimal value for the MBCS_INPUTERROR=REPLACE#nnnnnn option which can be converted to the charset.
Reason:
An error occurred during Unicode conversion.
Action:
Check the actual error message in the transfer trace.
Reason:
An error occurred during converting from the specified charset to Unicode encoding.
Action:
Retry the operation. If the problem persists, contact CA Technical Support.
Reason:
An error occurred during converting from the Unicode encoding to specified charset.
Action:
Retry the operation. If the problem persists, contact CA Technical Support.
Reason:
An error occurred during Unicode conversion.
Action:
None. The detected malformed characters can be found in the transfer trace.
Reason:
Checkpoint restart is not supported for Encryption At Rest when BlockIO is disabled (CACHE_READ_SZ and CACHE_WRITE_SZ set to 0). Hence Checkpoint restart is internally disabled.
Action:
None. The transfer will restart from the beginning of the file.
Reason:
Checkpoint restart is not supported with (L)EAR_HASH. Hence Checkpoint restart is internally disabled.
Action:
None. The transfer will restart from the beginning of the file.
Reason:
Using truncation for Unicode data can result in data loss or corruption if truncation occurs in the middle of an MBCS character.
Action:
Initiate the transfer without using truncation. Insure that a large enough logical record length (LRECL) is specified that can hold Unicode data which may have a larger LRECL than the source data.
| Copyright © [set copyright date variable] CA. All rights reserved. |
|