Previous Page | Next Page

Data Set Options for Relational Databases


Specifies during SAS/ACCESS update operations whether the DBMS waits to acquire a lock or fails your request when a different user has locked the DBMS resource.
Default value: LIBNAME setting
Valid in: DATA and PROC steps (when accessing DBMS data using SAS/ACCESS software)
DBMS support: Teradata

Syntax Description
See Also



Syntax Description


specifies that Teradata waits 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 if a different user holds a restrictive lock, then your SAS step fails and SAS/ACCESS continues the job by processing the next step. If you specify UPDATE_MODE_WAIT=YES, SAS/ACCESS waits indefinitely until it can acquire the lock.

A restrictive lock means that a different user is holding a lock that prevents you from obtaining your desired lock. 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 Teradata standard locking is undesirable.

For more information, see the locking topic in the Teradata section.

See Also

To assign this option to a group of relational DBMS tables or views, see the UPDATE_MODE_WAIT= LIBNAME Option.

Locking in the Teradata Interface

Previous Page | Next Page | Top of Page