The LIBNAME Statement for Relational Databases |
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.
Default value: |
none
|
Valid in: |
SAS/ACCESS LIBNAME
statement
|
DBMS support: |
Teradata
|
UPDATE_MODE_WAIT=YES | NO
|
-
YES
-
specifies for Teradata to wait to acquire
the lock, so SAS/ACCESS waits indefinitely
until it can acquire the lock.
-
NO
-
specifies for Teradata to fail 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 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.
To apply this option to an individual data
set, see
the
UPDATE_MODE_WAIT= Data Set Option.
Locking in the Teradata Interface
Copyright © 2010 by SAS Institute Inc., Cary, NC, USA. All rights reserved.