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

196 UPDATE_LOCK_TYPE= LIBNAME Option 4 Chapter 10UPDATE_LOCK_TYPE= LIBNAME OptionSpecifies how data in a DBMS table is locked during an update transaction.Default value: DBMS-specificValid in: SAS/ACCESS LIBNAME statementDBMS support: DB2 under UNIX and PC Hosts, DB2 under z/OS, Microsoft SQL Server,ODBC, OLE DB, Oracle, Sybase, Sybase IQ, TeradataSyntaxUPDATE_LOCK_TYPE=ROW | PAGE | TABLE | NOLOCK |VIEWSyntax DescriptionROW [valid for DB2 under UNIX and PC Hosts, Microsoft SQL Server, ODBC,Oracle]locks a row if any of its columns are to be updated.PAGE [valid for Sybase]locks a page of data, which is a DBMS-specific number of bytes. This value is notvalid for the Sybase interface when you use the .TABLE [valid for DB2 under UNIX and PC Hosts, DB2 under z/OS, Microsoft SQLServer, ODBC, Oracle, Sybase IQ, Teradata]locks the entire DBMS table.NOLOCK [valid for Microsoft SQL Server, ODBC with Microsoft SQL Server driver,OLE DB, Oracle, Sybase]does not lock the DBMS table, page, or any rows when reading them for update. (Thisvalue is valid in the Microsoft SQL Server, ODBC, Oracle, and Sybase interfaces.)VIEW [valid for Teradata]locks the entire DBMS view.DetailsYou can set a lock for one DBMS table by using the data set option or for a group ofDBMS tables by using the LIBNAME option. See the locking topic for your interface inthe DBMS-specific reference section for details.See AlsoTo apply this option to an individual data set, see the “UPDATE_LOCK_TYPE= DataSet Option” on page 397.“SCHEMA= LIBNAME Option” on page 181UPDATE_MODE_WAIT= LIBNAME OptionSpecifies during SAS/ACCESS update operations whether Teradata should wait to acquire a lock orfail the request when a different user has locked the DBMS resource.