End codes

HULFT IoT outputs the following end codes.

Table 4.1 End codes
End code Description Action
0 The transfer ended successfully. None
1

An error occurred in HULFT on the receiver.

In the details code, the status code of HULFT on the receiver is set.

 Check the Receive Log, and then execute the processing again after taking the appropriate actions.
2

The executed job ended abnormally.

In the details code, the following return value is set according to the executed job.

• 　For user jobs: the return value set by users

• 　For OS commands: the return value of the command

Check the details code.

Note if the return value is the following value, the detail code becomes 9999.

• 　The return value is greater than 9999.

• 　The return value is a minus value.
3 Acquisition of the time from the OS failed. Check the details code.
4 HULFT IoT communicated with a product of an unsupported version, or HULFT IoT is set to use an unsupported function.* Check the settings of HULFT on the receiver.
5 The size of the file changed between the start time and the end time of transfer. Changes to the file might have been made during the transfer.

Check the data of the send file.

If the data contains an error, restart Agent and send the file again.
6

The length of a single record of a text file exceeds 32,767 bytes.

You cannot send files for which the length of one record exceeds 32,767 bytes.

For text transfer, the length of one record (the data up to an including a newline character) is limited to 32,768 bytes.

Check that the file to be sent is correct.
7 Unexpected data was received during the loading of data from a socket. Check that the data was sent from Agent.
8

Processing to acquire the termination information of the host on the receiver failed.

The processing on the receiver might have terminated successfully.

 Check the status code of HULFT on the receiver.
9 Deletion of a transfer failed. Confirm the existence, permissions, and lock status of the file.
10 Moving of a send file failed. Create more free space on the disk, and then try transferring the file again.
11 Acquisition of the size of the send file failed.

Measure 1: Check that the file exists.

Measure 2: Check that the send file is not being used by other processing.
12 Processing for reserving memory failed. Increase free memory through other means, such as by closing other applications, and then execute it again.
13 Compression processing failed.

An OS failure or similar problem might have occurred.

Check the environment.
14 Unexpected data was received. Check the version of HULFT on the receiver.
15 Initial processing of job execution failed. A file system error, OS failure, or similar problem might have occurred. Check the environment.
100

Issuance of a request to acquire a received file failed.

In the details code, the status code of the curl command has been set.

 Check the status code of the curl command.
101

The received file could not be downloaded.

In the details code, the response code from Manager has been set.

 Check the status code of Manager.
102 Access to the specified path is not permitted. Change the path of File Name at Send Destination to an accessible path.
103 A data size error occurred in the downloaded file. Check the network environment.
104

The executed job ended abnormally.

In the details code, the end code of the job is set.

Check the details code.

Note if the return value is the following value, the detail code becomes 9999.

• 　The return value is greater than 9999.

• 　The return value is a minus value.
105 Initial processing of job execution failed. A file system error, OS failure, or similar problem might have occurred. Check the environment.
512 Receive processing was suspended by a cancel request. None
516 The value of Receive Multiplex Level (rcvpsnum) in the system environment settings is exceeded by HULFT on the receiver. Increase the value of Receive Multiplex Level at HULFT on the receiver, or wait for the next trigger fire.
525

Acquisition of the termination status of the file transfer of the host on the receiver failed.

The host on the receiver might have terminated successfully.

 Check the status code of HULFT on the receiver.
530 An error in the record count of the sending data or an error in the file size of the sending data occurred.

An inconsistency in the transfer record count occurred.

Check the contents of the send and receive files and attributes.

If the encryption exit routine is used, check that the encryption key is correct.
535 A data verification error occurred.

In this transferred data, a data error or a lack of data might have occurred during communication.

Check the network status, and then try again.
542 Unexpected data has been received.

Measure 1: Change the HULFT 7 communication mode for host information to "Y" (Yes), and then try transferring the file again.

Measure 2: Check that the data was sent from Agent.
591 Receive processing was terminated by a forced termination request. None
603 File transfer was stopped because the instance of Agent stopped during the transfer. None
1000 Processing for reserving memory failed. Increase free memory through other means, such as by closing other applications, and then execute it again.
1001 The file cannot be opened. Confirm the existence, permissions, and lock status of the file.
1002 Exclusive control of the file failed. A file system error, OS failure, or similar problem might have occurred. Check the environment.
1003 Write processing to the file failed. A file system error, OS failure, or similar problem might have occurred. Check the environment.
1004 Read processing of the file failed. A file system error, OS failure, or similar problem might have occurred. Check the environment.
1005 Read processing of the file failed. A file system error, OS failure, or similar problem might have occurred. Check the environment.
1006 Write processing to the file failed. A file system error, OS failure, or similar problem might have occurred. Check the environment.
1007 Write processing to the file failed. A file system error, OS failure, or similar problem might have occurred. Check the environment.
1008 Write processing to the file failed. A file system error, OS failure, or similar problem might have occurred. Check the environment.
1009 Read processing of the file failed. A file system error, OS failure, or similar problem might have occurred. Check the environment.
1010 Read processing of the file failed. A file system error, OS failure, or similar problem might have occurred. Check the environment.
1011 Acquisition of file information failed. A file system error, OS failure, or similar problem might have occurred. Check the environment.
1012 Read processing of the file failed. A file system error, OS failure, or similar problem might have occurred. Check the environment.
1100 Processing of socket generation failed.

A socket stream failure might have occurred.

Check the environment.
1101 Acquisition of socket information failed.

A socket stream failure might have occurred.

Check the environment.
1102 Communication with a remote host failed to connect.

Check the network environment.

Check the specified host name and port number, or check that HULFT has started.
1103 Write processing of data to the remote host failed.

A socket stream failure might have occurred.

Check the environment.
1104 Read processing of data from the remote host failed.

A socket stream failure might have occurred.

Check the environment.
1105 Acquisition of socket information failed.

A socket stream failure might have occurred.

Check the environment.
1106 Acquisition of socket information failed.

A socket stream failure might have occurred.

Check the environment.
1107 Read processing of data from the remote host failed.

A socket stream failure might have occurred.

Check the environment.
1108 A timeout occurred during communication processing with the remote host.

Measure 1: Check whether there are any problems with the communication lines.

Measure 2: Set a longer period for [Socket Read Timeout].
1109 Processing for reserving memory failed. Increase free memory through other means, such as by closing other applications, and then execute it again.
1110 Acquisition of socket information failed.

A socket stream failure might have occurred.

Check the environment.
1111 The setting of socket information failed.

A socket stream failure might have occurred.

Check the environment.
1112 Initialization of SSL communication failed. Increase free memory through other means, such as by closing other applications, and then execute it again.
1113 Setting the communication option failed. A file system error, OS failure, or similar problem might have occurred. Confirm the environment.
1114 Agent ID or Unit is not registered in Manager that is the connection destination.

Measure 1: Agent has not been registered to Manager. It is necessary for Agent to reactivate.

Perform the following steps:

  1. Delete the "agent_id" line that is described in the agent.conf file.
  2. Stop Agent
  3. Start Agent
Measure 2: The unit that is allocated to Agent does not exist. Register the unit and the profile.
1115 The protocol is incorrect. Trouble or lack of data might occur during the communication. Confirm the network status, and then execute it again.
1200 Processing for reserving memory failed. Close other applications, etc.
1201 Processing to set the communication between processes failed. A file system error, OS failure, or similar problem might have occurred. Check the environment.
1202 Generation of a process failed.

The OS environment is unstable.

Check that no other processes are running abnormally.
1203 Processing of communication between processes failed. A file system error, OS failure, or similar problem might have occurred. Check the environment.
1204 Processing of communication between processes failed. A file system error, OS failure, or similar problem might have occurred. Check the environment.
1205 Processing of communication between processes failed. A file system error, OS failure, or similar problem might have occurred. Check the environment.
1206 A timeout occurred during the wait for a process. Set a longer period for [Job Timeout] of Agent Operation Settings, or set it to [Off].
1207 An unexpected error occurred during the wait for a process. A file system error, OS failure, or similar problem might have occurred. Check the environment.
1208

A generated process stopped by receiving a signal.

In a details code, the signal number is set.

 Check the details code.
1209 Generation of a process failed.

The OS environment is unstable.

Check that no other processes are running abnormally.
1210 Generation of a process failed.

The OS environment is unstable.

Check that no other processes are running abnormally.
1300 A socket disconnection was detected during the loading of data from the socket.

A socket stream failure might have occurred.

Check the environment.
1301 Processing for reserving memory failed. Close other applications, etc.
1302 Unexpected data has been received. Check that the data was sent from Agent.
1303 Acquisition of the time failed. A file system error, OS failure, or similar problem might have occurred. Check the environment.

*

:

For details about functions that HULFT IoT cannot use, see Note about HULFT settings.