The NO–WAIT option works for DataServer applications in the same way that it works for OpenEdge database applications: the DataServer uses a time-out mechanism. If Sybase does not return a record within a set period of time, the DataServer considers the record to be locked. It then cancels the request to Sybase and sets the "locked" and "not available" conditions.

During a period of heavy demand, you might encounter situations where the "not available" condition is set although the record is not currently locked by a user. In this case, you might want to increase the time-out interval by using the -Dsrv RESP_TIMEOUT parameter.