Send and Receive Settings

Encryption Scheme (ciphertype)

This field specifies the method of encryption.

0:

Use HULFT Encryption Scheme

1:

Incorporate encryption exit routine and use other encryption scheme

Refer to Encryption and Encryption exit routine for the details.

Receive Open Mode (rcvfilewait)

This field specifies how to treat the exclusive control of Receive file.

0:

Return an error when the Receive file is locked.

1:

Wait until the lock is released.

Transfer Group Check (tgrpchk)

This field specifies how to handle the checking of the Transfer Group in receiving.

If you choose to check, HULFT checks the sending host name against the host names registered in the Transfer Group (GRPID) of the corresponding record of the Receive Management Information. Also, you can choose to let HULFT give an error, when the Transfer Group ID is not registered in the record of the Receive Management Information.

0:

Do not check

1:

Check only when the Transfer Group ID is registered in the target record of the Receive Management Information

2:

Always check and give an error when the Transfer Group ID is not registered

Dynamic Parameter Specification (dynparam)

This field specifies whether the File Name, the Transfer Group Name, or the Host Name can be dynamically changed with the Send File command (utlsend) or not.

0:

Disable dynamic specification

1:

Enable dynamic specification

Message Dynamic Parameter Specification (msgdynparam)

The field specifies how to treat received message.

0:

Never replace any messages in all the management information

1:

Replace the messages in the Send Management Information and the Receive Management Information, while don't replace messages in the Job Information

2:

Do not replace messages in the Send Management Information and the Receive Management Information, while replace the messages in the Job Information

3:

Replace the messages in all the management information

Receive Multiplex Level Over Retry (rcvover_rty)

This field specifies whether or not to retry connection, when an error occurs due to excess in the Receive Multiplex Level, in the socket connection from a local host to the Receive process of a remote host.

0:

Do not retry and give an error

1:

Retry connection

Regarding retry count and retry interval for reconnection, the Connect Retry Count (retrycnt) and the Connect Retry Interval (retry time) are used, respectively.

Send Transfer Error Recovery (enderrmode)

This field specifies whether HULFT should handle sending as successful termination or unsuccessful termination,

when the application encounters with either of the following situations:

• When you specify 'Clear(C)' for the Send File Mode in the Send Management Information, yet clearing has terminated unsuccessfully

• When you specify 'Delete(D)' for the Send File Mode in the Send Management Information, yet deletion has terminated unsuccessfully

0:

Handle the result as an unsuccessful termination and execute the Unsuccessful Job.

1:

Handle the result as a successful termination and execute the Successful Job.

Criteria to Delete Resend Queue (resenddel)

This field specifies conditions to delete records from the Resend Queue where the Send File is issued for the File ID that is placed in the Resend Queue.

1:

Delete the records of which File ID and Host Name correspond to those of the Send files.

2:

Delete the records of which File ID, Host Name, and File Name correspond to those of the Send file.

Receive File Max. Size (rcvmaxfilesize)

This field specifies the maximum file size which can be received in the Receive process.

When your Linux/AIX system does not support the file system of 2GB or more, specify 2147483647.

This field is optional.

Note

• The setting of this field is disabled either of the following cases; where the product version of the host on the sending side is lower than HULFT5 or where direct transfer from Mainframe is carried out.

• Due to code conversion, the size of the receive file may be larger than the size of the send file.

  In this case, receiving-side transferring may end successfully even if the size of the receive file exceeds the maximum receive file size that you specify here.

  For details on the conditions that cause the size of the receive file to increase due to code conversion, refer to the following:

  HULFT10 Code Conversion Manual : Shift code conversion rules

Local Host Name (myhostname)

This field specifies the local host name when you intend to use a different name from the node name (hostname) of Linux/AIX system, which is usually used as the local host name, due to an administrative reason on the side of remote host and the like.

There is no default value. If defaulted, node name (hostname) is set.

Compression Type Selection (comp_selection)

Specify which compression type is used when the host on the receiving side does not support the compression type specified on the host on the sending side.

C:

Common

Use a compression type with the highest compression efficiency that is available on both the hosts on the sending side and receiving side

The supported types in order of compression efficiency are as follows:

Zstandard > DEFLATE > None

Example: If the compression type specified on the host on the sending side is Zstandard and the compression type with the highest compression efficiency that can be specified on the host on the receiving side is DEFLATE, DEFLATE is used to transfers.

N:

None

No compression is used if the host on the receiving side does not support the compression type specified on the host on the sending side.