DB2 10.5 for Linux, UNIX, and Windows

concurrent-access-resolution-clause

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


>>-WAIT FOR OUTCOME--------------------------------------------><

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. The settings for the registry variables DB2_EVALUNCOMMITTED, DB2_SKIPDELETED, and DB2_SKIPINSERTED are ignored. This clause applies when the isolation level is CS or RS and is ignored when an isolation level of UR or RR is in effect.

This clause causes the following behavior and settings to be overridden:

The default behavior for currently committed that is defined by the cur_commit configuration parameter.
Any higher level setting such as bind options, CLI settings, JDBC settings, or lock modifications.