Specifies the concurrent access resolution
to use.
- db2cli.ini keyword syntax:
- ConcurrentAccessResolution = 0 | 1 | 2 | 3
- Default setting:
- DB2® CLI does not supply
a prepare option, and the currently committed behavior is determined
by the database configuration.
- Applicable when:
- Connected to a database using DB2 Connect™ or DB2 for Linux, UNIX, and Windows
- Equivalent environment or connection attribute:
- SQL_ATTR_CONCURRENT_ACCESS_RESOLUTION
- Usage notes:
- This keyword specifies a prepare attribute that overrides the
default behavior specified for cursor stability (CS) scans.
- 0 = No setting. The client does not supply a prepare option.
- 1 = Use currently committed semantics. CLI flows
"currently committed" on every prepare, which means that the database
manager can use the currently committed version of the data for applicable
scans when the data is in the process of being updated or deleted.
Rows in the process of being inserted can be skipped. This setting
applies when the isolation level in effect is Cursor Stability or
Read Stability (for Read Stability it skips uncommitted inserts only)
and is ignored otherwise. Applicable scans include read-only scans
that can be part of a read-only statement as well as a non read-only
statement. The
settings for the registry variables DB2_EVALUNCOMMITTED, DB2_SKIPDELETED,
and DB2_SKIPINSERTED do not apply to scans using
currently committed. However, the settings for these registry variables
still apply to scans that do not use currently committed.
- 2 = Wait for outcome. CLI flows
"wait for outcome" on every prepare, which means that Cursor Stability
and higher scans wait for the commit or rollback when encountering
data in the process of being updated or deleted. Rows in the process
of being inserted are not skipped. The settings for the registry variables
DB2_EVALUNCOMMITTED, DB2_SKIPDELETED, and DB2_SKIPINSERTED no longer
apply.
- 3 = Skip locked data. CLI flows
"skip locked data" on every prepare, which means that currently committed
semantics are used and rows in the process of being inserted are skipped.
This option is not supported on DB2 for Linux, UNIX, and Windows.
If specified, this setting is ignored.
For DB2 for Linux, UNIX, and Windows,
use this keyword to override the default behavior for currently committed
that is defined by the cur_commit configuration
parameter. For DB2 for z/OS®,
use this keyword to enable currently committed behavior. There is
no equivalent database configuration parameter available on DB2 for z/OS for
specifying this behavior.
DB2 z/OS Version 10 only supports
INSERT and DELETE operations of currently committed.
DB2 Version 9.7 for Linux, UNIX, and Windows