SAS/ACCESS 9.2 for Relational Databases: Reference, Fourth Edition

The LIBNAME Statement for Relational Databases 4 UPDATE_MULT_ROWS= LIBNAME Option 197Default value: noneValid in: SAS/ACCESS LIBNAME statementDBMS support: TeradataSyntaxUPDATE_MODE_WAIT=YES | NOSyntax DescriptionYESspecifies for Teradata to wait to acquire the lock, so SAS/ACCESS waits indefinitelyuntil it can acquire the lock.NOspecifies for Teradata to fail the lock request if the specified DBMS resource is locked.DetailsIf you specify UPDATE_MODE_WAIT=NO and if a different user holds a restrictivelock, then the executing SAS step fails. SAS/ACCESS continues processing the job byexecuting the next step.A restrictive lock means that a different user is holding a lock that prevents you fromobtaining the lock that you want. Until the other user releases the restrictive lock, youcannot obtain your lock. For example, another user’s table level WRITE lock preventsyou from obtaining a READ lock on the table.Use SAS/ACCESS locking options only when the standard Teradata standard lockingis undesirable.See AlsoTo apply this option to an individual data set, see the “UPDATE_MODE_WAIT=Data Set Option” on page 398.“Locking in the Teradata Interface” on page 832UPDATE_MULT_ROWS= LIBNAME OptionIndicates whether to allow SAS to update multiple rows from a data source, such as a DBMS table.Default value: NOValid in: SAS/ACCESS LIBNAME statementDBMS support: Aster nCluster, Greenplum, HP Neoview, Microsoft SQL Server, Netezza,ODBC, OLE DB, Sybase IQSyntaxUPDATE_MULT_ROWS=YES | NO