Status codes of the Receive process
200 Insufficient disk space
- Description:
-
Insufficient disk space for creating the receive data or work data.
- Measure:
-
Delete any unnecessary files on the disk, ensure that there is sufficient disk space, and then retry the attempt.
201 Undefined data type
- Description:
-
Undefined receiving message type.
- Measure:
-
An error may have occurred while receiving data. Retry the transfer.
202 An error of fields in the message
- Description:
-
Fields in the message are not sufficient.
- Measure:
-
An error may have occurred while receiving data. Retry the transfer.
203 An error in data length in file info
- Description:
-
The data length of the received data does not match the data length in the file information.
- Measure:
-
An error may have occurred while receiving data. Retry the transfer.
204 Undefined file information
- Description:
-
Failed to acquire the management information.
- Measure:
-
Check whether the Receive Management Information is correct.
205 File already exists.
- Description:
-
A file with the same name already exists.
- Measure:
-
When a file with the same name already exists, 'New Creation Mode (N)' cannot be specified for Registration Mode (TRANSMODE). Specify 'Replace Mode (R)' or 'Append Mode (M).'
206 A db communication error
- Description:
-
Receiving of the CSV format failed.
- Measure:
-
HULFT or the operating system environment is in unstable condition. Restart the system.
207 A generation control error
- Description:
-
Unable to perform the processing of generational management for the Receive file.
- Measure:
-
The number of generations may have exceeded the maximum. The extension of the generation file should be in the range from 0001 up to the maximum value specified in No. of Generations.
Sort out Receive files and check the Generational Management Information file (File ID.info).
208 A data convert error
- Description:
-
Code conversion or attribute conversion failed.
- Measure 1:
-
For regular transfer, check Code Set for Transfer (KCODETYPE) and Standard for Japanese (JISYEAR) in the System Environment Settings and the Host Information. For a format transfer, check Field Type in the Format Information also.
- Measure 2:
-
For instant transfer, check Code Set for Transfer and Standard for Japanese in the System Environment Settings on both local and remote hosts. For a format transfer, check Field Type in the Format Information also.
209 A client error
- Description:
-
A error may have occurred on the sending host or the proxy server.
- Measure:
-
Check the logs on the sending host. When you have been using a proxy server, check the logs of the proxy server. After checking the logs, take appropriate measures and retry the transfer. When this error occurred, the code assigned to the Detail Code is the Status Code of the sending host or the proxy server.
210 A length over error
- Description:
-
Data length per record has exceeded the maximum.
- Measure:
-
In the case of Test Transfer, the maximum length per record (up to the line feed) is 32768 bytes.
The file that exceeds this size cannot be received.
211 A parameter error
- Description:
-
There is an error in the registration of the Receive Management Information.
- Measure:
-
Check whether there is no error in the combination of Error Handling (ABNORMAL), Generational Management (GENCTL), and Receive Mode (RCVTYPE) in the Receive Management Information.
212 A cipher error
- Description:
-
Decoding of the encryption failed.
- Measure:
-
An error may have occurred while receiving data. Check the environment such as errors in the socket stream, operating system, and the like. Then retry the transfer.
214 A exchanger error
- Description:
-
An error occurred while interfacing with Exchanger.
- Measure:
-
Refer to Exchanger / Option Manual.
215 Maximum file size exceeded.
- Description:
-
The size of the Receive file has exceeded the maximum.
- Measure:
-
Increase the value for the Receive File Max.Size or split the Send file, then retry the transfer.
218 A format mismatch
- Description:
-
The contents of the received data are inconsistent with the definition in the Format Information.
- Measure:
-
The Receive file cannot be handled with the specified format ID. Check and correct the settings in the record of the Format ID that is specified on the sending host, or compare the contents of the Send file with the settings in Format ID, then correct the settings as needed. Then, retry the transfer.
219 Option product is not installed.
- Description:
-
Required option products have not been installed.
- Measure:
-
The specified function cannot be executed because the option products have not been installed.
Check the Send Management Information, the Receive Management Information, and environment, then retry the transfer.
220 Invalid transfer group
- Description:
-
The host name has not been registered in the transfer group ID that has been specified in the Receive Management Information.
- Measure:
-
Register the host name to the transfer group ID that has been specified in the Receive Management Information.
221 Transfer group information unregistered.
- Description:
-
The Transfer Group Information is not registered.
- Measure:
-
Transfer Group ID is not specified, and Transfer Group Check is set to '2.'
When you want to disable Transfer Group Check, set '0' or '1' to Transfer Group Check.
When you want to enable Transfer Group Check, specify Transfer Group ID.
222 Function not supported in this version.
- Description:
-
Unsupported function.
- Measure:
-
An unsupported string has been specified for Interface DBID in the Send Management Information.
The string that can be specified for Interface DBID is 'CSV.'
223 A client error, but job success
- Description:
-
An error may have occurred in the sending host.
However, the Successful job on the receiving side has ended successfully. - Measure:
-
View the Send Log record and take appropriate measures, then retry the attempt.
When this error occurred, the code assigned to the Detail Code is the Status Code of the sending side.
224 A socket error, but job success
- Description:
-
Reading or writing of the communication socket failed. However, the Successful Job on the receiving side has ended successfully.
- Measure:
-
Status of the sending side could not be verified. Network condition may be unstable.
Check the environment.
225 Receive file does not exist.
- Description:
-
The Receive file does not exist. The Receive file has been deleted during receiving.
- Measure:
-
Identify the cause of the deletion, then retry the transfer.
226 A data inflation error
- Description:
-
Failed to uncompress the data.
- Measure:
-
An error such as an operating system error occurred. Check the environment.
When encryption is used, Cipher Key in the Send Management Information do not match Cipher Key in the Receive Management Information. Set the correct value for Cipher Key in both the Send Management Information and the Receive Management Information.
227 recieve file invalid
- Description:
-
Receive file name is invalid.
- Measure:
-
Check whether the pathname of the receive file exceeds the maximum length. If so, specify a shorter pathname.
Also, check whether the pathname of the receive file contains a character other than alphanumeric characters. If so, specify a pathname containing only alphanumeric characters.
616 refused instant transfer
- Description:
-
The instant transfer request from the sending host was denied during the receive processing. HOSTNAME=%s
- Measure:
-
Check whether the request from the sending host is correct. If correct, take any of the following measures:
-
If the sending host is not registered in the Host Information, register its information.
-
If the sending host is registered in the Host Information, change the allowance/denial settings for the host in the Host Information.
-
Specify a root directory path under which files can be received as the Instant Transfer Receive Root Directory field in the System Environment Settings.
-