Status codes of the Receive program

400

Description:

Insufficient disk capacity for generating receive data or work data.

Measure:

To ensure enough free space, delete any unnecessary files from the disk. Then, retry the operation.

401

Description:

A communication error occurred.

Measure 1:

An invalid application other than the one executed sending may have accessed the Receive port. Check the port number of the applications in use.

Measure 2:

Retry the transfer as the error may have occurred during data receiving.

402

Description:

A communication error occurred.

Measure:

An error may have occurred during receiving data. Retry the transfer.

403

Description:

The file information does not match the received data length.

Measure:

An error may have occurred during receiving data. Retry the transfer.

405

Description:

A file with the same name exists.

Measure 1:

When another Receive file with the same name exists, files cannot be received if Registration Mode is set to 'New Creation.' Change Registration Mode to 'Replace' or 'Add.'

Measure 2:

If the generational management option is enabled, the error implies that the generation file to be newly created already exists. Remove the existing generation file, and retry the Receive operation.

406

Description:

An error occurred on the sending host or the proxy server.

Measure:

Check logs on the sending host. When using a proxy server, check logs of the proxy server. After checking logs, take appropriate measures, and retry the operation.

When this error occurs, error code of the sending host, or error code of the proxy server are stored to Detail Code.

For the Description and the Measure for the error codes, refer to the Error Codes manuals for the receiving host or the proxy server.

407

Description:

An error occurred during decompressing the received data.

Measure:

Retry the transfer.

408

Description:

An error occurred during code conversion of received data.

Measure 1:

Check consistency between the content of the record of the Format Information on the sending-side host and the content of the received data.

Measure 2:

Handling of Unregistered Custom Characters (gaijierr) is set to "0" (Raise an error) in the System Environment Settings. For a text transfer, check the registered custom characters also.

Measure 3:

For regular transfer, check that both Kanji Code Type and Standard for Japanese are identical between the System Environment Settings on the sending-side host and the receiving-side host record in the Host Information.

Measure 4:

For instant transfer, check that both Code Set for Transfer and Standard for Japanese in the System Environment Settings are identical between the sending-side and receiving-side hosts.

409

Description:

HULFT version of the sending host (Mainframe or UNIX) is lower than 3.0.

Measure 1:

Files cannot be received through format transfer when HULFT on the sending host is Mainframe and lower than Ver.3.0. Upgrade the version of HULFT on the sending host.

Measure 2:

Files cannot be received through format transfer when HULFT on the sending host is UNIX and lower than Ver.3.0. Upgrade the version of HULFT on the sending host.

410

Description:

The Receive file size is 0 bytes.

Measure:

When the file size is 0 bytes, CSV conversion, XML interface, or database interface are unavailable.

411

Description:

Deletion of the temporary file failed.

Measure:

Remove the file with the name of 'receive_file_name.tmp.number.number.' in the Receive file creation directory.

412

Description:

Database interface cannot be used if the generational management option is enabled.

Measure:

Database interface cannot be used if Generational Management is selected. Reset the Send Management Information on the sending host.

415

Description:

Check that the received data matches the format definition stored in the Format Information or the Multi Format Information.

Measure 1:

Check that the size of the key value does not exceed the length for a record by calculating the size based on values stored in the Multi Format Information.

Measure 2:

A key value that is not registered in the Multi Format Information exists in the received data.

416

Description:

Cannot receive a file larger than the value set for the Receive File Max. Size (rcvmaxfilesize) in the System Environment Settings.

Measure:

Check the size of Receive File Max. Size (rcvmaxfilesize) of the System Environment Settings.

417

Description:

Too long message.

Measure:

Specify a short message.

418

Description:

DB interface function is not supported by HULFT 6 and higher.

Measure 1:

For HULFT Ver.7, do not specify any value other than 'CSV' or 'XML' for Interface DBID.

Measure 2:

For HULFT Ver.8, do not specify any value other than 'CSV' for Interface DBID.

Measure 3:

For HULFT-BB Server or HULFT-BB Client, do not specify any value other than 'CSV' for Interface DBID.

419

Description:

Invalid character string is specified in a message.

Measure:

When $MSGn or $MSGLn is specified in each ID, only alphanumeric characters or symbols can be specified.

420

Description:

The Receive file name violates the naming rules.

Measure 1:

Change the Send file name.

Measure 2:

Do not specify '$SNDFILE' as File Name of the Receive Management Information.

423

Description:

An error may have occurred on the sending host.

Measure:

Check the sending status log, take appropriate measures, and retry the operation. Detail code that is set becomes the Status Code of the sending side.

424

Description:

Failed to read a socket.

Measure:

The sending host status can not be checked. Network status may be unstable. Check your environment.

425

Description:

The Receive file name generated by replacing environment variables or messages is too long.

Measure 1:

Shorten the Receive file path name.

Measure 2:

Shorten the Send file path name or the Send file name.

Measure 3:

Shorten the message.

426

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.

512

Description:

Receive operation is suspended per cancel request.

Measure:

None.

513

Description:

Receive operation cannot be executed as the file already exists.

Measure:

This error occurs when Registration Mode of the Receive Management Information is 'New Creation', the Receive file exists without satisfying the checkpoint conditions, and the Checkpoint Resend Request comes. Change as follows: do not execute the Checkpoint Resend File, delete the Receive file or Receive Management Information satisfies checkpoint conditions.

514

Description:

The Post-receive Job ended abnormally.

Measure1

Check the status by Receiving Side Job Status.

Measure2

When you execute Receiving to cloud storage and "Successful Job Completion" is set in Notification, even if the execution of a Successful job fails, Error Handling is not executed. Keep this in mind when executing Resend and when re-executing a job.

515

Description:

Post-receive Job was not completed within the Job Time-out (jobwtimeout) period in the System Environment Settings.

Measure:

Check the value specified for Job Timeout (jobwtimeout) in the System Environment Settings.

516

Description:

The number of connections to the Receive process exceeds the value specified for Receive Multiplex Level(rcvpsnum) in the System Environment Settings.

Measure:

If this error occurs repeatedly, review the set value for Receive Process Multiplex Level (rcvpsnum) in the System Environment Settings.

517

Description:

HULFT version on the sending host does not support Transfer Test.

Measure:

Upgrade the HULFT version on the sending host to Ver.8.0.0 or higher. If the current HULFT version is 8.0.0 or higher, review the Use HULFT7 Comm. Mode setting in the Host Information on the sending host.

526

Description:

Socket close queue failed, but Receive operation was successfully terminated.

Measure:

Network may have been disconnected. Check the network environment.

530

Description:

An error occurred regarding the record count or file size of the send data.

Measure 1:

The record counts (or data sizes for a binary file transfer) of the send file and the receive file differ. Check the consistency between the record of the Format Information and the content of the data.

Measure 2:

Check that the type of the data format is the same as Transfer Type in the Send Management Information.

Measure 3:

When the encryption exit routine is used, check that Cipher Key is correctly specified.

Measure 4:

For instant transfer, check that the type of the data format is the same as the transfer type specified when Send File was issued.

535

Description:

An error occurred in data verification.

Measure:

During the transfer of this data, a data error may have occurred, or some pieces of the data have been lost. Check the network status, and retry the verification.

536

Description:

An error occurred in data verification.

Measure 1:

HULFT version on the sending host does not support data verification. Check the version of the sending host.

Measure 2:

The host does not support the value specified for Verify Data in the Receive Management Information. Review the setting of Verify Data in the Receive Management Information.

540

Description:

Specified function is not supported in processing with HULFT on the remote host.

Measure 1:

Check if none of File ID, Format ID, and Multi Format ID is specified in 9 bytes or more.

Measure 2:

Check that 'XML' is not set to Interface DBID in the Send Management Information on the sending host.

591

Description:

The Receive processing ended with forced termination request.

Measure:

None.

600

Description:

Insufficient disk capacity for generating receive data or work data.

Measure:

To ensure enough free space, delete any unnecessary files from the disk. Then, retry the operation.

601

Description:

A communication error occurred.

Measure 1:

An invalid application other than the one executed sending may have accessed the Receive port. Check the port number of the applications in use.

Measure 2:

Retry the transfer as the error may have occurred during data receiving.

602

Description:

A communication error occurred.

Measure:

An error may have occurred during receiving data. Retry the transfer.

605

Description:

A file with the same name exists.

Measure 1:

When a Receive file with the same name exists, files cannot be received if Registration Mode is set as 'New Creation.' Change Registration Mode to 'Replace' or 'Append.'

Measure 2:

When the generational management option is enabled, the error implies that the generation file to be newly created already exists. Retry the Receive operation after deleting the existing generation file.

606

Description:

An error occurred on the sending host.

Measure:

Refer to the send status of the sending host, take appropriate measures, and then retry the transfer. When this error occurs, the error code of the sending host is stored to Detail Code. For the description and measure of the error code, refer to the relevant manual of the sending host.

607

Description:

An error occurred in decompressing the received data.

Measure:

Retry the transfer.

608

Description:

An error occurred during code conversion of the received data.

Measure:

Check consistency of the received data with the format definition stored in the Format Information on the sending side.

609

Description:

HULFT version of the sending host (Mainframe or UNIX) is lower than 3.0.

Measure 1:

Files cannot be received through format transfer when HULFT on the sending host is Mainframe and lower than Ver.3.0. Upgrade the version of HULFT on the sending host.

Measure 2:

Files cannot be received through format transfer when HULFT on the sending host is UNIX and lower than Ver.3.0. Upgrade the version of HULFT on the sending host.

610

Description:

Database interface cannot be carried out when the file size of data is 0 bytes.

Measure:

None.

616

Description:

A request for instant transfer issued by an unregistered host has been rejected.

Measure:

Check that the request from the sending-side host is correct. If correct, take any of the following measures:

1. If the sending-side host is not registered in the Host Information, register it.

2. If the sending-side host is registered in the Host Information, appropriately change the request acceptance settings in the Host Information.

3. Specify a directory path allowed for file receiving as Instant Transfer Receive Directory in the System Environment Settings