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

Data Set Options for Relational Databases 4 READ_MODE_WAIT= Data Set Option 363TABLE [valid only for DB2 under UNIX and PC Hosts, DB2 under z/OS, ODBC,Oracle, Microsoft SQL Server, Teradata]locks the entire DBMS table. If you specify READ_LOCK_TYPE=TABLE, you mustalso specify the CONNECTION=UNIQUE, or you receive an error message. SettingCONNECTION=UNIQUE ensures that your table lock is not lost—for example, dueto another table closing and committing rows in the same connection.NOLOCK [valid only for Microsoft SQL Server, Oracle, Sybase, and ODBC with theMicrosoft SQL Server driver]does not lock the DBMS table, pages, or any rows during a read transaction.VIEW [valid only for Teradata]locks the entire DBMS view.DetailsIf you omit READ_LOCK_TYPE=, you get either the default action for the DBMS thatyou are using, or a lock for the DBMS that was set with the LIBNAME statement. Seethe locking topic for your interface in the DBMS-specific reference section for details.See AlsoTo assign this option to a group of relational DBMS tables or views, see the“READ_LOCK_TYPE= LIBNAME Option” on page 176.“CONNECTION= LIBNAME Option” on page 108READ_MODE_WAIT= Data Set OptionSpecifies during SAS/ACCESS read operations whether Teradata waits to acquire a lock or failsyour request when a different user has locked the DBMS resource.Default value: LIBNAME settingValid in: DATA and PROC steps (when accessing DBMS data using SAS/ACCESSsoftware)DBMS support: TeradataSyntaxREAD_MODE_WAIT=YES | NOSyntax DescriptionYESspecifies that Teradata waits to acquire the lock, and SAS/ACCESS waits indefinitelyuntil it can acquire the lock.NOspecifies that Teradata fails the lock request if the specified DBMS resource is locked.