The OPLOCKTIMEOUT command interrogates and sets the time-out values used by the opportunistic locking feature of Client Access Services. It controls the parameters of the algorithms that time out requests to return opportunistic locks.
You can use the minimum values during off-hours while using library maintenance to back up files and use the default values during normal working hours. This usage minimizes the delay to library maintenance caused by powered-off PCs.
Syntax
Explanation
If you enter the command without integers, the system displays the current values.
<integer>
The first integer specifies the maximum time, in seconds, a user or program attempting to access a file has to wait, while an outstanding opportunistic lock is recalled. If the workstation holding the lock does not return it and remains connected for this time period, a NOTAVAILABLERSLT result is sent to the workstation client or the MCP environment user that is requesting access to the file.
-
Reducing this value reduces the delay in the case where the client with the opportunistic lock is in some undesirable state and cannot return the opportunistic lock.
-
Increasing this value can reduce the cases where a NOTAVAILABLERSLT result is returned because the client with the opportunistic lock is slow to respond but is responding. (The slow response can result from the client not giving high priority to the task of returning the opportunistic lock, or because it is behind a congested TCP/IP router.)
The second integer specifies the allowed idle time, in seconds, before the connection is dropped to a client workstation that is not responding to an opportunistic lock recall command. Any workstation activity restarts this time period. Therefore, the elapsed time, before connection to the workstation is dropped can be greater than the allowed idle time. (When Client Access Services drops the connection to a client, it closes all files opened by that client. This implicitly frees any opportunistic locks held by that client.)
-
Reducing this value reduces the delay in the case where the client, with the opportunistic lock is either powered off, in software failure, or otherwise not responding.
-
Increasing this value can reduce the cases where a long pause in activity is interpreted as complete failure. (Long pauses in activity, as seen by the server, can be caused by poor processor scheduling by the client or by packets being dropped by a congested TCP/IP router.)
The defaults are
OPLOCKTIMEOUT = 30, 10
The minimum values are
OPLOCKTIMEOUT = 10, 3
| Note: | Time-out values specified by OPLOCKTIMEOUT take effect immediately. |
