Official | Receive

Table C.4 Problems That Are Related to Receiving
Trouble	Measure
Unable to open a Receive file	Check whether the file exists under File Name (FILENAME) in the Receive Management Information.
Make sure that the Receive file is not being used by other processing.
If Registration Mode (TRANSMODE) is 'New Creation,' make sure that a Receive file with the same name as that you specified in File Name does not exist.
Unable to write to a file	Check the available free space on the hard disk. If 'Multiple Receive' and 'Restore' is specified for Receive Mode (RCVTYPE) and Error Handling (ABNORMAL), respectively, or when receiving data in a CSV format, more free space is required than the actual size of the data to be received.
Unable to acquire the name of the host on the sending side	Check that the host on the sending side has been registered in the 'hosts' file.
Check that there is a carriage return after the final record of the host on the sending side in the 'hosts' file.
A code conversion fails	Check that the Format Information and Multi Format Information defined in the host on the sending side corresponds to the received data.
A communication error occurs	Check whether the host on the sending side has forcibly terminated the sending.
Check whether or not a socket read time-out has occurred on the host on the sending side.
Make sure that the settings of devices, such as routers, and the setting of the LAN environment are correct.
Received data is garbled	If a Cipher Key is set in the Receive Management Information, make sure that it matches the Cipher Key of the host on the sending side.
In the case of the sending-side conversion, make sure that Code Set for Transfer (cs4trnsfr) of the local host is correctly registered in the Host Information of the host on the sending side.
In the case of the receiving-side conversion, make sure that Code Set for Transfer of the host on the sending side is correctly registered in the Host Information.
Unable to receive a file that uses network resources (networked files)	If HULFT operates under the system account, HULFT may be unable to log in to the server that stores the target file. Make sure that the permission to access the target file and the permission to access the path that is specified for Path to Location for Cross-Product Sharing (hulsharepath) in the System Environment Settings are granted to the account that started HULFT.
Make sure that the target file is not being used by HULFT on another host or by another application.
Check that the path to the file is specified in a UNC format.
Check the following points on the server that stores the file: Whether the ping command works correctly Whether prerequisites for using networked files are met Whether you can view and edit the relevant file in applications other than HULFT

Unable to open a Receive file

Check whether the file exists under File Name (FILENAME) in the Receive Management Information.

Make sure that the Receive file is not being used by other processing.

If Registration Mode (TRANSMODE) is 'New Creation,' make sure that a Receive file with the same name as that you specified in File Name does not exist.

Unable to write to a file

Check the available free space on the hard disk. If 'Multiple Receive' and 'Restore' is specified for Receive Mode (RCVTYPE) and Error Handling (ABNORMAL), respectively, or when receiving data in a CSV format, more free space is required than the actual size of the data to be received.

Unable to acquire the name of the host on the sending side

Check that the host on the sending side has been registered in the 'hosts' file.

Check that there is a carriage return after the final record of the host on the sending side in the 'hosts' file.

A code conversion fails

Check that the Format Information and Multi Format Information defined in the host on the sending side corresponds to the received data.

A communication error occurs

Check whether the host on the sending side has forcibly terminated the sending.

Check whether or not a socket read time-out has occurred on the host on the sending side.

Make sure that the settings of devices, such as routers, and the setting of the LAN environment are correct.

Received data is garbled

If a Cipher Key is set in the Receive Management Information, make sure that it matches the Cipher Key of the host on the sending side.

In the case of the sending-side conversion, make sure that Code Set for Transfer (cs4trnsfr) of the local host is correctly registered in the Host Information of the host on the sending side.

In the case of the receiving-side conversion, make sure that Code Set for Transfer of the host on the sending side is correctly registered in the Host Information.

Unable to receive a file that uses network resources (networked files)

If HULFT operates under the system account, HULFT may be unable to log in to the server that stores the target file. Make sure that the permission to access the target file and the permission to access the path that is specified for Path to Location for Cross-Product Sharing (hulsharepath) in the System Environment Settings are granted to the account that started HULFT.

Make sure that the target file is not being used by HULFT on another host or by another application.

Check that the path to the file is specified in a UNC format.

Check the following points on the server that stores the file:

Whether the ping command works correctly
Whether prerequisites for using networked files are met
Whether you can view and edit the relevant file in applications other than HULFT