ConcurrentAccessResolution IBM data server driver configuration keyword
Specifies the concurrent access resolution to use.
- Equivalent CLI keyword
- Equivalent IBM® Data Server Provider for .NET connection string keyword
- IBM data server driver configuration file (db2dsdriver.cfg) configuration syntax
<parameter name="ConcurrentAccessResolution" value="0 | CurrentlyCommitted | WaitForOutcome | SkipLockedData"/>
- Default setting:
- Usage notes:
- The ConcurrentAccessResolution keyword
specifies a prepare attribute that overrides the default behavior
that is specified for cursor stability (CS) scans:
- The client does not supply a prepare option.
- On every prepared statement, the CLI driver
and IBM Data Server Provider for
the currently committed semantics. The database manager uses the currently
committed version of the data for applicable scans when the data is
updated or deleted. The uncommitted inserted rows are skipped. Applicable
scans include read-only scans that can be part of a read-only statement
or a non-read-only statement. The CurrentlyCommitted option
applies when the isolation level is cursor stability (CS) or read
stability (RS); otherwise, the value is ignored. For RS, only uncommitted
inserts are skipped.
The settings for the DB2_EVALUNCOMMITTED, DB2_SKIPDELETED, and DB2_SKIPINSERTED registry variables do not apply to scans that use currently committed semantics.
- On every prepared statement, the CLI driver and IBM Data Server Provider for .NET specify the skip locked data clause. The currently committed semantics are used, and rows that are being inserted are skipped. The SkipLockedData option is not supported for Db2® servers. If you specify the option, it is ignored.
- On every prepared statement, the CLI driver and IBM Data Server Provider for .NET specify the wait for outcome clause. CS and higher isolation level scans wait for the commit or rollback when the data is updated or deleted. Rows that are being inserted are not skipped. The settings for the DB2_EVALUNCOMMITTED, DB2_SKIPDELETED, and DB2_SKIPINSERTED registry variables do not apply.
For Db2, use the ConcurrentAccessResolution keyword to override the default behavior for the currently committed semantic that is defined by the cur_commit configuration parameter.
For Db2 for z/OS® servers, use the ConcurrentAccessResolution keyword to enable the currently committed semantic behavior. There is no equivalent database configuration parameter for specifying this behavior for Db2 for z/OS servers.
Db2 for z/OS Version 10 servers support only insert and delete operations for the currently committed semantic.
The Db2 for IBM i V6R1 server supports only the 0 and WaitForOutcome options of the ConcurrentAccessResolution keyword. Db2 for IBM i V7R1 and later servers support all options of the keyword.