Timeout attributes

The values of the following attributes depend on the settings of the associated site attributes:

attrtimeout, readtimeout, and writetimeout – These attributes must be within the ranges specified by the maxtimeout and mintimeout site attributes.

Note: When using the NFS version 4 protocol, these timeout values should be set to a value less than or equal to the lease time. Otherwise, it is possible for performance problems to occur when attempting to access MVS data sets.

noattrtimeout, noreadtimeout and nowritetimeout – These attributes are valid only when nomaxtimeout is specified in the site attributes.

There are three processing attributes which control when files are timed out: attrtimeout, readtimeout, and writetimeout. The server determines which of these timeouts are in effect based on the last file operation. Thus when an existing file is appended, the file cannot be accessed before it times out in the time specified for writetimeout and is released by the server, because write operations result in exclusive locking. Similarly, if a file is read, it is not released before it times out in the time specified for readtimeout seconds.

The readtimeout and writetimeout attributes do not apply to the MVS data set or member being opened by NFS version 4 OPEN operation because there is a stateful CLOSE operation that closes and releases the data set or member.

The readdirtimeout site attribute controls the internal readdir cache used by directory lookups of MVS z/OS conventional data sets to be timed out or discarded based on a customizable value. The default is 30 seconds.