concurrent-access-resolution-clause

The concurrent-access-resolution-clause specifies the concurrent access resolution to use for the statement.


>>-+-SKIP LOCKED DATA--------+---------------------------------><
   +-USE CURRENTLY COMMITTED-+   
   '-WAIT FOR OUTCOME--------'

SKIP LOCKED DATA: Specifies that the select-statement, searched UPDATE statement (including a searched update operation in a MERGE statement), or searched DELETE statement that is prepared in the PREPARE statement will skip rows when incompatible locks are held on the row by other transactions. These rows can belong to any accessed table that is specified in the statement. SKIP LOCKED DATA can be used only when isolation level NC, UR, CS, or RS is in effect.; SKIP LOCKED DATA is ignored if it is specified when the isolation level that is in effect is RR.
USE CURRENTLY COMMITTED: Specifies that the database manager can use the currently committed version of the data for applicable scans when it is in the process of being updated or deleted. Rows in the process of being inserted can be skipped. This clause applies if possible when the isolation level is CS without the KEEP LOCKS clause and is ignored otherwise. Applicable scans include read-only scans.
WAIT FOR OUTCOME: Specifies to wait for the commit or rollback when encountering data in the process of being updated or deleted. Rows encountered that are in the process of being inserted are not skipped. This clause applies if possible when the isolation level is CS or RS. It is ignored when an isolation level of NC, UR, or RR is in effect.