When a request is made to lock a record but the record is already locked by another process, the behaviour of USoft can be influenced in two ways:.
This timeout can be changed by adding the following resource setting to the command line, using the -xrm option:
In this instance, the result is a timeout of 60 seconds.
Increasing the timeout has the advantage that timeout error messages do not appear too soon, and stop the transaction too soon. A disadvantage is that too long a timeout may cause a user to wait too long for a locked record.
SELECT column FROM table FOR UPDATE OF column SKIP LOCKED