Communication
- Connect Retry Count (retrycnt)
-
Specify how many times HULFT retries to connect when the socket connection fails.
When '0' is set, reconnection is not carried out.
- Connect Retry Interval (retrytime)
-
Specify the retry interval for reconnection where the socket connection fails in seconds.
- Auto Resend Retry Count (sockerr_autoretry)
-
Specify how many times HULFT retries automatic resending when a communication error occurs during the transfer process.
When '0' is set, automatic resend is not carried out.
- Socket Read Timeout (socktime)
-
Specify the time-out interval in seconds for when there is no response from a remote host during a socket communication. If the process reaches the time-out, HULFT considers this a transmission error, and then it cuts off communication. Because the setting value indicates the time used for error detection in the network, select a value suitable for the network in use.
- Socket Buffer Size for Data Sending (sndsocksize)
-
Specify the send size of data for socket communication in bytes.
Set '0' or a value in the range from '4096' to '2147483647.'
When you set '0,' HULFT applies the value configured in its environment (operating system) to operate.
NoteAfter the Send process is started, if you change the upper limit of the maximum socket buffer size for the operating system to a value smaller than HULFT Socket Buffer Size for Data Sending (sndsocksize), the Send processing will end unsuccessfully.
- Socket Buffer Size for Data Receiving (rcvsocksize)
-
Specify the receive size of data for socket communication in bytes.
Set '0' or a value in the range from '4096' to '2147483647.'
When you set '0,' HULFT applies the value configured in its environment (operating system) to operate.
NoteAfter the Send process is started, if you change the upper limit of the maximum socket buffer size for the operating system to a value smaller than HULFT Socket Buffer Size for Data Receiving (rcvsocksize), the Send processing will end unsuccessfully.
- Service Connect Timeout (srvtime)
-
Specify the time-out period in seconds from the service command until connection of the Observe process when a service request is acknowledged from another host. Increase this value if a large amount of service requests are accepted and time-out errors occur frequently.
- HULFT Manager Timeout (admsocktime)
-
Specify the time-out period in seconds to interrupt communication during the Observe process when there is no reply from HULFT Manager.
- IP Version (ipversion)
-
Specify the version of the IP protocol for socket communication.
- 4:
-
Use IPv4 when connecting to the remote host; use only IPv4 when being connected
- 4/6:
-
Use IPv4 first when connecting to the remote host, try with IPv6 if connection fails; use both IPv4 and IPv6 when being connected
- 6/4:
-
Use IPv6 first when connecting to the remote host, try with IPv4 if connection fails; use both IPv4 and IPv6 when being connected
- 6:
-
Use IPv6 when connecting to the remote host; use only IPv6 when being connected
NoteRegister the IPv6 address of the local host in DNS or the 'hosts' file when specifying '4/6,' '6/4,' or '6.'
- Queue of Pending Connect (listen)
-
Specify the maximum number of connections that a Send, a Receive, or an Observe process can accept at the same time. An error occurs at the connection side when the number of connections at one time exceeds this value. Note that this is not the maximum number of communications allowed at one time.
The value that can be specified depends on the OS where HULFT is operating. For more details, refer to the relevant manual of operating system.
- Framed Message Transfer Type (proctranstype)
-
Specify a data transfer method.
- Error Detection Priority Mode:
-
HULFT operates in Error Detection Priority mode for both sending and receiving. The data transfer method, the timing for the transfer error detection, and the timing of cancelation acknowledgment are the same as those of HULFT lower than Ver.7.
- Send Speed Priority Mode:
-
For sending, HULFT operates in Transfer Speed Priority mode, and for receiving, it operates in Error Detection Priority mode. In Send Speed Priority mode, utilization of resources when the Send processing is carried out varies more widely than the conventional transfer method of HULFT lower than Ver.7, and this may cause a delay in error detection and cancelation acknowledgment. When HULFT on the receiving side is not in Transfer Speed Priority mode, Error Detection Priority mode is applied.
- Receive Speed Priority Mode:
-
For receiving, HULFT operates in Transfer Speed Priority mode, and for sending, it operates in Error Detection Priority mode. In Receive Speed Priority mode, utilization of resources when the Receive processing is carried out varies more widely than the conventional transfer method of HULFT lower than Ver.7, and this may cause a delay in error detection and cancelation acknowledgment. When HULFT on the sending side is not in Transfer Speed Priority mode, Error Detection Priority mode is applied.
- 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 HULFT on the other side is not in Transfer Speed Priority mode, Error Detection Priority mode is applied.
For information on the different data transfer methods, refer to Windows Administration Manual.