System Environment Settings

Timeout settings

If the number of parallel uploads reaches the maximum number, any additional uploads will be placed in the queue until one or more running uploads are finished and a slot opens in the available number of uploads. In this case, if the wait time is too long, a timeout occurs during communication with HULFT. The following value is used for the time until this timeout occurs:

The value of the non-communication timeout value specified by the sending-side host (*1) minus the subtracted value (*2) (unit: seconds)

*1

:

If the value is in minutes, convert the value to seconds before performing the calculation.

*2

:

Use the smaller of the following two values as the subtracted value:

  • Non-communication timeout value specified by the sending-side host x 0.1 (unit: seconds)

  • 10 seconds

 

Non-communication timeouts are specified as follows:

Table 2.16 Non-communication timeouts by host type

Sending Host

Setting

HULFT for zOS

Socket Read Timeout (TIMEOUT) in the System Environment Settings (seconds)

HULFT for MSP

TCMTIME parameter in the ISP environment for TISP (minutes)

HULFT for XSP

HULFT for IBMi

Socket Read Timeout (SOCKTIME) in the System Environment Settings (seconds)

HULFT for UNIX/Linux

Socket Timeout (socktime) in the System Environment Settings (seconds)

HULFT for NSK

HULFT for Windows

Socket Read Timeout (socktime) in the System Environment Settings (seconds)

 

If timeout errors occur frequently in uploads to object storage, change the settings for non-communication timeouts for the sending-side host.