Specifies during SAS/ACCESS Update operations whether Teradata should wait to acquire a lock or fail the request when a different user has locked the DBMS resource.
Valid in: SAS/ACCESS LIBNAME statement
Default: none
Data source: Teradata
See: Locking in the Teradata InterfaceUPDATE_MODE_WAIT= data set option



Syntax Description

specifies for Teradata to wait to acquire the lock, so SAS/ACCESS waits indefinitely until it can acquire the lock.
specifies that Teradata fails the lock request if the specified DBMS resource is locked.


If you specify UPDATE_MODE_WAIT=NO and a different user holds a restrictive lock, the executing SAS step fails. SAS/ACCESS continues processing the job by executing the next step.
A restrictive lock means that a different 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.
Use SAS/ACCESS locking options only when the standard Teradata standard locking is undesirable.