option #50

Continue NOLOCK I/O when record locking error occurs

 

USupported on Unix

 

 

When system option #50 is set and you get an internal runtime failure due to a record locking problem (for example, when opening a record on an NFS server that does not support record locking, such as OpenVMS), the OPEN is automatically retried using the NOLOCK qualifier.