ConcurrentAccessResolution CLI/ODBC configuration keyword

• DB2® for Linux, UNIX, and Windows server
• DB2 for z/OS® server
• DB2 for i V6R1 and later servers

• 0: No setting. The client does not supply a prepare option.
• 1: Use the currently committed semantics. On every prepared statement, the CLI driver specifies the currently committed semantics. The value indicates that 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. The setting value of 1 applies when the isolation level 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 or a non read-only statement. The settings for the registry variables DB2_EVALUNCOMMITTED, DB2_SKIPDELETED, and DB2_SKIPINSERTED do not apply to scans with the currently committed semantics. However, the settings for these registry variables still apply to scans that do not use the currently committed semantics.
• 2: Wait for outcome. On every prepared statement, the CLI driver specifies the wait for outcome clause. The cursor stability 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 registry variables DB2_EVALUNCOMMITTED, DB2_SKIPDELETED, and DB2_SKIPINSERTED no longer apply.
• 3: Skip locked data. On every prepared statement, the CLI driver specifies the skip locked data clause. The currently committed semantics are used and rows that are being inserted are skipped. The option 3 is not supported on DB2 for Linux, UNIX, and Windows servers. If specified, the option 3 setting is ignored.

For DB2 for Linux, UNIX, and Windows servers, use the ConcurrentAccessResolution keyword to override the default behavior for the currently committed semantics that are defined by the cur_commit configuration parameter. For DB2 for z/OS servers, use the ConcurrentAccessResolution keyword to enable currently committed behavior. There is no equivalent database configuration parameter available on DB2 for z/OS server for specifying this behavior.

DB2 for z/OS Version 10 server supports only INSERT and DELETE operations of the currently committed semantics.

DB2 for i V6R1 server supports only the options 0 and 2. DB2 for i V7R1 and later servers supports all available options for the ConcurrentAccessResolution keyword.