Send and Receive

Encryption Scheme (ciphertype)

Specify the method of encryption that HULFT uses.

0:

Use HULFT Encryption Scheme

1:

Use other encryption scheme by incorporating encryption exit routine

Refer to Encryption and Encryption exit routine for details about encryption exit routines.

Note

Do not specify '1' (Other Encryption Scheme) for Encryption Scheme (ciphertype) when HULFT Cipher Option is not installed. If you do so, you cannot start up the Send process and the Receive process after you restart the HULFT service.

Receive Ready Notification (rcvcmd)

Specify the use of the Receive Ready Notification function.

The Resend Request command (utlrecv.exe -a) is specified.

Refer to Method of automatic startup upon power on for details about the Receive Ready Notification function.

Send Unit Selection (sndpsend)

Specify the timing when HULFT completes the Send processing. The timing to update the Send Multiplex Level changes depending on this value.

0:

At the time of subsequent job completion

1:

Immediately before subsequent job start-up

Transfer Group Check (tgrpchk)

Specify transfer group check processing when receiving.

The host name of the sending side is checked against the host name registered in Transfer Group ID (GRPID) of the Receive Management Information, and when it is not registered, it can be considered an error.

0:

Do not check

1:

Check only when Transfer Group ID is set in the Receive Management Information; do not check when it is not set

2:

Check only when Transfer Group ID is set in the Receive Management Information; return an error when it is not set

Retry Count on Locked Send File (lockcnt)

Specify the number of times reopening is tried when the Send file is being used by another process or application program.

When '0' is set, no retry will be carried out.

Retry Interval on Locked Send File (locktime)

Specify the interval in seconds until the next reopening attempt when opening of the Send file fails.

Retry Count on Locked Receive File (rretrycnt)

Specify the number of times reopening is tried when the Receive file is being used by another process or application program.

When '0' is set, no retry will be carried out.

Note

Only when the Receive file is being used by a process other than HULFT, the settings of Retry Count on Locked Receive File and Retry Interval on Locked Receive File become valid. When the Receive file is being used by any HULFT processing, the setting of Receive File Lock Standby takes precedence over the settings of Retry Count on Locked Receive File and Retry Interval on Locked Receive File. Refer to the explanations of Retry Interval on Locked Receive File and Receive File Lock Standby.

Retry Interval on Locked Receive File (rretrytime)

Specify the interval in seconds until the next reopening attempt when opening of the Receive file fails.

Note

Only when the Receive file is being used by a process other than HULFT, the settings of Retry Count on Locked Receive File and Retry Interval on Locked Receive File become valid. When the Receive file is being used by any HULFT processing, the setting of Receive File Lock Standby takes precedence over the settings of Retry Count on Locked Receive File and Retry Interval on Locked Receive File. Refer to the explanations of Retry Count on Locked Receive File and Receive File Lock Standby.

Retry Count on Send File (sretrycnt)

Specify the number of request re-issue attempts when connection to the Send process by using the Send File command (utlsend.exe) fails.

When '0' is set, re-issue will not be attempted.

Retry Interval on Send File (sretrytime)

Specify the interval until the next attempt of request re-issue in seconds when connection to the Send process by using the Send File command fails.

Dynamic Parameter Specification (dynparam)

Specify whether or not file names, transfer group names, and host names can be dynamically changed in the Send File command.

0:

Disable dynamic specification

1:

Enable dynamic specification

Message Dynamic Parameter Specification (msgdynparam)

Specify the mode to use while receiving the message.

Specify whether to replace the environment variables '$MSGn' and '$MSGLn' that are specified in the management information with the messages that are specified for the corresponding parameters of the command.

0:

Never replace any environment variables in management information with messages.

1:

Replace environment variables in the Send Management Information and the Receive Management Information with messages; do not replace environment variables in the Job Information and the Mail Interface Information with messages.

2:

Do not replace environment variables in the Send Management Information and the Receive Management Information with messages; replace environment variables in the Job Information and the Mail Interface Information with messages.

3:

Replace all the environment variables in management information with messages.

Receive Multiplex Level Over Retry (rcvover_rty)

Specify whether to retry the connection where an error occurs due to the excess of the Receive Multiplex Level during socket connection to a host on the receiving side.

0:

Do not retry and return an error

1:

Retry the connection

For the reconnect retry count and interval, Connect Retry Count (retrycnt) and Connect Retry Interval (retrytime) are used respectively.

Send Transfer Error Recovery (enderrmode)

Specify how to treat the send result if clearing the Send file or deleting the Send file terminates unsuccessfully.

The setting of this field is applied in the following conditions:

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

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

    0:

    Handle the state as an unsuccessful termination and execute the Unsuccessful Job

    1:

    Handle the state as a successful termination and execute the Successful Job

Criteria to Delete Resend Queue (resenddel)

Specify criteria to delete records from the Resend Queue when the Send File is issued for the file ID that is placed in the Resend Queue and when transfer ends unsuccessfully.

1:

Delete the records in which the file ID and host name match those of the file to send.

2:

Delete the records in which the file ID, host name, and file name match those of the file to send.

Receive File Max. Size (rcvmaxfilesize)

Specify in bytes the maximum size of a file that can be received in a transfer (Receive processing).

Depending on the supported operating system, there are some host types that do not support transferring a file that exceeds 2 to the power of 31 bytes. When file transfer is carried out with such hosts, specify the maximum size supported by that host.

Note

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

In this case, receiving 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

Clear Unsent File (delreqcpfile)

Specify whether or not to delete the Send Control file (sddreqcp.dat) and Forced Stop Send Control file (sddfrccp.dat) when the Send process starts up.

0:

Do not delete

1:

Delete

Clear Resend Queue File (delresendfile)

Specify whether or not to delete the Resend Queue file (sddreqls.dat) when the Send process starts up.

0:

Do not delete

1:

Delete

Receive File Lock Standby (rcvfilelockwait)

Specify the exclusive control process of the Receive file.

0:

Handle it as an error when the Receive file is locked

1:

Wait until the file is unlocked

Note

If the processing by HULFT locks the Receive file, HULFT conforms to the setting in Receive File Lock Standby. In that case, HULFT disables the settings of Retry Count on Locked Receive File and Retry Interval on Locked Receive File.
If a processing other than the processing performed by HULFT locks the Receive file, HULFT disables the settings in Receive File Lock Standby yet it enables the settings in Retry Count on Locked Receive File and Retry Interval on Locked Receive File.

Local Host Name (myhostname)

Normally, the host name set in the operating system is used as the local host name. This field is used when setting a different name for the remote host for a reason of administration.

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 compression type

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 for transfers.

N:

No compression

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.