Send and Receive Settings

Encryption Scheme (CIPHERTYPE)

This field specifies the method of encryption. (Optional)

0 :: Use HULFT Encryption Scheme
1 :: Incorporate encryption exit routine and use other encryption scheme

Specify '1' for this field if you have installed HULFT Cipher Option to encrypt data.

For details of encryption exit routines, refer to Encryption and Encryption Exit Routine.

Transfer Group Check (TGRPCHK)

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

HULFT compares the host name of a sending host with the host names specified in the record of the Transfer Group ID that is registered in the Receive Management Information. Specifying this field allows you to give an error if a host name is not registered.

0 :: Do not check
1 :: Check only when the Transfer Group ID is registered in the Receive Management Information, otherwise do not check
2 :: Check only when the Transfer Group ID is registered in the Receive Management Information, otherwise handle the Host Name as an error

If omitted, "0" is set.

Dynamic Parameter Specification (DYNPARAM)

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

0 :: Do not allow dynamic change
1 :: Allow dynamic change

If omitted, '1' is set.

Message Dynamic Parameter Specification (MSGDYNPARAM)

This field specifies how to treat received message. (Optional)

The options determine the target management information for replacing variables ('&MSG0' to '&MSG5' and '&MSGL0' to '&MSGL1') with the messages that are specified by a transmitter.

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 do not 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

If omitted, '3' is set.

Receive Multiplex Level Over Retry (RCVOVER_RTY)

This field specifies whether to retry connection when an error occurs due to excessive multiplicity at the time when the socket connection is attempted. (Optional)

0 :: Do not retry the connection and give an error
1 :: Retry the connection

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

If omitted, "0" is set.

Send Transfer Error Recovery (ENDERRMODE)

This field specifies whether HULFT should handle entire send processing as successful termination or unsuccessful termination, when the application encounters with either of the following situation: (Optional)

When you specify 'C: Clear' for the Send File Mode (CLEAR) in the Send Management Information, yet clearing a Send file has ended unsuccessfully
When you specify 'D: Delete' for the Send File Mode (CLEAR) in the Send Management Information, yet deletion of a Send file has ended 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

If omitted, "0" is set.

Criteria to Delete Resend Queue (RESENDDEL)

This field specifies the conditions to delete records from the Resend Queue where the Send File is issued for the same File ID that exists in the Resend Queue. (Optional)

0 :: Delete the records of which File ID and Host Name correspond to those of the Send files
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 files

If omitted, "0" is set.

Receive File Max. Size (RCVMAXFILESIZE)

This field specifies the maximum file size which is allowed in receiving (Bytes). (Optional)

If omitted, '999999999999999999' is set.

Note

Receiving a file from HULFT for Mainframe via direct transfer ignores the value of this field.
The size of the receive file might become larger than that of the send file as a result of a code conversion.

Note that receiving-side transferring might end successfully even when the receive file exceeds the maximum size specified in this field.

For details on the conditions under which the size of receive files becomes larger, refer to the following:

HULFT10 Code Conversion Manual : Shift code conversion rules