Communication Settings

Connect Retry Count (retrycnt)

This field specifies the retry count for reconnection when the socket connection to the receiving side has failed.

When '0' is specified, reconnection is not carried out.

Connect Retry Interval (retrytime)

This field specifies the retry interval for reconnection in seconds when the socket connection to the receiving side has failed. In addition, the field specifies the wait time before auto resending.

Auto Resend Retry Count (sockerr_autoretry)

This field specifies the number of attempts to execute the Auto Resend when a communication error occurs during the Send and Receive process.

When '0' is set, the Auto Resend is not carried out.

Socket Timeout (socktime)

This field specifies timeout interval in seconds where there is no response from remote host during socket communication. If the processing reached timeout, HULFT regards the state as a communication error, and cuts off the communication. Because the field specifies a time range to detect errors in network, specify suitable value for the network in use.

Socket Buffer Size for Data Sending (sndsocksize)

This field specifies the buffer size for data sending that is applied in socket communication.

When you specify '0,' HULFT applies the value configured in its environment (OS) to carry out socket communication.

Note

Send processing ends unsuccessfully when the upper limit of the maximum socket buffer size (OS) is changed to a smaller value than the one of HULFT Socket Buffer Size for Data Sending after the Send daemon starts.

Socket Buffer Size for Data Receiving (rcvsocksize)

This field specifies the buffer size for data receiving that is applied in socket communication.

When you specify '0,' HULFT applies the value configured in its environment (OS) to carry out socket communication.

Note

Send processing ends unsuccessfully when the upper limit of the maximum socket buffer size (OS) is changed to a smaller value than the one of HULFT Socket Buffer Size for Data Receiving after the Send daemon starts.

Observe Timeout (obssocktime)

This field specifies the timeout for a response to a request in the Observe process in seconds.

When it reaches to timeout, HULFT regards the state as no reply, and terminates the Observe process.

IP Version (ipversion)

This field specifies the version of the IP protocol for socket communication.

4:

Connect with IPv4 only.

4/6:

When unable to connect with IPv4, try connecting with IPv6.

6/4:

When unable to connect with IPv6, try connecting with IPv4.

6:

Connect with IPv6 only.

Framed Message Transfer Type (proctranstype)

Specify a data transfer method.

N:

Error Detection Priority mode

HULFT operates in Error Detection Priority mode at the time both sending and receiving. The data transfer method, the timing for the error detection, and the timing of cancelation acknowledgment are the same as those of HULFT lower than Ver.7.

S:

Send Speed Priority mode

As for sending, HULFT operates in Transfer Speed Priority mode, while the application operates in Error Detection Priority mode for receiving. In Send Speed Priority mode, utilization of resources at the time of sending varies more widely than the conventional transfer method of HULFT lower than Ver.7, which may cause delay in the timing of error detection and the cancelation acknowledgment. When the HULFT on the receiving side is not in Transfer Speed Priority mode, HULFT operates in Error Detection Priority mode.

R:

Receive Speed Priority mode

As for receiving, HULFT operates in Transfer Speed Priority mode, while the application operates in Error Detection Priority mode for sending. In Receive Speed Priority mode, utilization of resources at the time of receiving varies more widely than the conventional transfer method of HULFT lower than Ver.7, which may cause delay in the timing of error detection and the cancelation acknowledgment. When the HULFT on the sending side is not in Transfer Speed Priority mode, HULFT operates in Error Detection Priority mode.

A:

Send and Receive Speed Priority mode

HULFT operates in Transfer Speed Priority mode at the time of both sending and receiving. In Send and Receive Speed Priority mode, utilization of resources at the time of sending and receiving varies more widely than the conventional transfer method of HULFT lower than Ver.7, which may cause delay in the timing of error detection and the cancelation acknowledgment. When the HULFT on the other side is not in Transfer Speed Priority mode, HULFT operates in Error Detection Priority mode.