During SAS/ACCESS Read operations, specifies whether Teradata should wait to acquire a lock or fail the request when a different user has already locked the DBMS resource.
| Valid in: | SAS/ACCESS LIBNAME statement |
|---|---|
| Category: | Data Access |
| Default: | none |
| Data source: | Teradata |
| See: | READ_ISOLATION_LEVEL= LIBNAME option, READ_LOCK_TYPE= LIBNAME option, READ_MODE_WAIT= data set option, Locking in the Teradata Interface |
Table of Contents
specifies for Teradata to wait to acquire the lock, so SAS/ACCESS waits indefinitely until it can acquire the lock.
specifies Teradata fails the lock request if the specified DBMS resource is locked.
If you specify READ_MODE_WAIT=NO and if a different user holds a restrictive lock, the executing SAS step fails. SAS/ACCESS continues processing the job by executing the next step.
If you specify READ_MODE_WAIT=YES, SAS/ACCESS waits indefinitely until it can acquire the lock.
A restrictive lock means that another user is holding a lock that prevents you from obtaining the lock that you want. Until the other user releases the restrictive lock, you cannot obtain your lock. For example, another user's table-level WRITE lock prevents you from obtaining a READ lock on the table.