Status codes and detail codes for Send processing
This section explains status codes and detail codes for the Send processing.
When you contact your Technical Support Service representative, notify them of the system code.
- Example:
-
Status Code: 0000-0000(0000) System code
Status Code |
Detail Code |
Error Message |
---|---|---|
0 |
0 |
Ended successfully. |
4 |
4 |
Failed to open the Send file. |
8 |
Failed to open the Send file. |
|
12 |
An error occurred during opening of the Send file. |
|
16 |
The member name does not exist in the Partitioned Organization file. |
|
20 |
One or more attributes of the Send file are invalid. |
|
4887 |
One or more attributes of the Send file are invalid. |
|
DYNALLOC |
Failed to allocate the Send file (Send work file). For detail codes, refer to the return codes for the DYNALLOC macro in Authorized Assembler Services Guide. |
|
8 |
1 |
Failed to connect to the host on the receiving side. |
2 |
An error occurred during transfer processing. |
|
3 |
An error occurred during receiving. |
|
4 |
Failed to release the connection with the communication destination. * The message 'XRT0002' appears on the console. For details on error codes, check the RC=xxxx of the console message, and then refer to the applicable section in Communication error code list. |
|
12 |
VSAM |
Failed to access the management file. For detail codes, refer to the feedback codes in DFSMS Macro Instructions for Data Sets. |
16 |
Status code |
An error occurred on the host on the receiving side. Refer to Detail codes when errors occur on receiving-side hosts. |
20 |
1 |
This is a Send file access error (a DISK failure may have occurred). |
24 |
1 |
The region for the Send program (XRSND) is insufficient. |
2 |
Communication protocol error occurred in HULFT |
|
28 |
0 |
Cancelation processing was carried out. |
32 |
0 |
The size of the sent data and the size of the received data differ. |
36 |
604 |
Check the level of the version of HULFT on the host on the receiving side. |
40 |
0 |
Failed to connect to HULFT proxy. |
44 |
0 |
Failed to carry out the Direct Transfer. |
48 |
0 |
Failed to clear the Send file. |
52 |
1 |
A file size error occurred during execution of the Checkpoint Resend File. |
56 |
1 |
HULFT-SAN is not installed on the host on the receiving side. |
2 |
The Send processing was carried out via proxy. |
|
3 |
SAN transfer is specified between mainframes. |
|
4 |
The Send file is not a Sequential Organization file. |
|
5 |
HULFT-SAN transfer error occurred on the host on the receiving side. |
|
6 |
The Send processing with the Work File Transfer was carried out. |
|
7 |
The volume serial number is not specified. |
|
8 |
Sending Side is specified for the code conversion. |
|
9 |
The Send file is a multi-volume file. |
|
10 |
The Send processing is carried out for a file on a tape volume. |
|
60 |
1 |
Failed to open the intermediate volume. The message 'XRTFS05' appears on the console, and the detail code is output. Look up the detail code. |
2 |
Failed to write to the intermediate volume. The message 'XRTFS05' appears on the console, and the detail code is output. Look up the detail code. |
|
607 |
HULFT-SAN is not installed on the host on the receiving side. Install HULFT-SAN. |
|
64 |
0 |
Failed to convert between EBCDIC codes. |
1 |
A user table cannot be specified for code conversion to UTF-8. |
|
2 |
The record length exceeded 32750 bytes after code conversion to UTF-8. |
|
3 |
If the Code Set for Transfer (cs4trnsfr) in the System Environment Settings is 'UTF-8,' sending-side conversion cannot be carried out. |
|
68 |
Encryption exit routine |
Encryption processing failed. |
72 |
0 |
Pack zone conversion failed. |
76 |
0 |
XML conversion failed. |
80 |
0 |
SAN transfer cannot be carried out because HULFT-SAN is not installed. |
84 |
XRCUNLCN error code |
An error occurred in the z/OS Unicode Services during code conversion. This is a HULFT system error. "XRC0010" is displayed on the console. If you have a technical support agreement, check the return code and the reason code displayed in the error message and then contact your Technical Support Service representative. |
85 |
1 |
An error occurred during the DEFLATEINIT processing. Contact your Technical Support Service representative. |
2 |
An error occurred during the DEFLATE processing. Contact your Technical Support Service representative. |
|
3 |
An error occurred during the DEFLATE processing. Contact your Technical Support Service representative. |
|
4 |
DEFLATE compression is not available for your product grade. Change Compression Preference (COMP) in the Send Management Information. |
|
516 |
0 |
The number of connections exceeded the specified Receive Multiplex Level on the host on the receiving side. |
525 |
0 |
Acquisition of the end status of the host on the receiving side failed. Processing on the host on the receiving side may have ended successfully. |
540 |
0 |
A function that cannot be used with the version of HULFT at the communication destination is specified.
|
542 |
0 |
HULFT acknowledged data that was not expected from the communication destination. Take either of the following measures:
|
544 |
0 |
Confirm that the combination of the code set specified for the Code Set for Transfer (KCODETYPE) in the Host Information and the setting of the EBCDIC Set in the Send Management Information or the Receive Management Information is supported. For details, refer to the explanation on Convertible Code Set Combinations in Code Conversion Manual. |
545 |
0 |
Failed to communicate in Forced Strong Key mode. Confirm that the communication destination meets all of the following conditions:
|
546 |
0 |
The Forced Strong Key mode in the System Environment Settings and the length of the cipher key in the management information do not match.
|
604 |
0 |
A Transfer Test that includes the host on the receiving side cannot be carried out. The Use HULFT7 Comm. Mode in the Host Information may be enabled, or the host on the receiving side may not support the Transfer Test function. |
615 |
0 |
The version of the receiving-side host does not support instant transfer. Check the version of the receiving-side host. |
9999 |
9999 |
The Send processing was forcibly ended on the host on the sending side. |