Chapter Contents |
Previous |
Next |
READ_LOCK_TYPE= |
Default value: | None |
Syntax | |
Details | |
See Also |
Syntax |
READ_LOCK_TYPE= TABLE |
Details |
READ_LOCK_TYPE= is useful if you want to lock out concurrent changes in order to access an entire table as it is at that particular moment. You can also use it to prevent timeouts from contention with other application processes that are reading the same table.
DB2 locking is handled internally. No explicit locking is done. Consult your DBA to determine what the locking process is for your installation of DB2.
If you set READ_LOCK_TYPE=TABLE, then you must also set the CONNECTION= option to UNIQUE, which means that there is a separate physical connection for each table that is opened in your SAS application. You cannot share a connection when a DB2 table is locked. If you do not set the CONNECTION= option to UNIQUE, the SAS step fails.
If you set READ_LOCK_TYPE=TABLE, you might also want to evaluate whether or not you change the SPOOL= option from its default value of YES. If the table is locked and its data cannot be changed during the read transaction, you may not need to create a utility spool file.
For a full description of this option, refer to READ_LOCK_TYPE= .
See Also |
UPDATE_LOCK_TYPE=
Chapter Contents |
Previous |
Next |
Top of Page |
Copyright 1999 by SAS Institute Inc., Cary, NC, USA. All rights reserved.