CONCURRENTACCESSRESOLUTION bind option

The CONCURRENTACCESSRESOLUTION option specifies which concurrent access resolution option to use for statements in a package.

Command option	Option values	Used with
CONCURRENTACCESSRESOLUTION	(WAITFOROUTCOME) (USECURRENTLYCOMMITTED)	BIND PACKAGE BIND PLAN BIND SERVICE REBIND PACKAGE ¹ REBIND PLAN REBIND TRIGGER PACKAGE

Note:

The CONCURRENTACCESSRESOLUTION bind option is not valid for REBIND of packages for native SQL procedures or advanced triggers.

Option descriptions for CONCURRENTACCESSRESOLUTION

CONCURRENTACCESSRESOLUTION(USECURRENTLYCOMMITTED)

Specifies that when a read transaction requires access to a row that is locked by an INSERT or DELETE operation, the database manager can access the currently committed row, if one exists, and continue to the next row. The read transaction does not need to wait for the INSERT or DELETE operation to commit. This clause applies when the isolation level in effect is cursor stability or read stability.

Under the following circumstances, if USECURRENTLYCOMMITTED is specified for a package, WAITFOROUTCOME behavior is used instead:

The table space on which the package operates is not a universal table space.
XML data is being selected, and the data does not support multiple XML versions. In this case, the Db2 database manager cannot determine whether the data has been committed.

CONCURRENTACCESSRESOLUTION(WAITFOROUTCOME)

Specifies that when a read transaction requires access to a row that is locked by an INSERT or DELETE operation, the read transaction must wait for a COMMIT or ROLLBACK operation to complete.

Default values for CONCURRENTACCESSRESOLUTION

Process	Default value
BIND SERVICE	None
BIND PLAN	None
BIND PACKAGE	Existing value
REBIND PLAN	Existing value
REBIND PACKAGE	None
REBIND TRIGGER PACKAGE	None

The following table shows how Db2 handles uncommitted INSERT operations for each combination of the CONCURRENTACCESSRESOLUTION option and SKIPUNCI subsystem parameter settings. For uncommitted DELETE operations, the WAITFORDATA option behavior applies if CONCURRENTACCESSRESOLUTION option is not specified.

Table 1. Db2 behavior for SKIPUNCI subsystem parameter and CONCURRENTACCESSRESOLUTION bind option combinations
SKIPUNCI value	CONCURRENTACCESSRESOLUTION value	Resulting behavior
YES	USECURRENTLYCOMMITTED	Skip uncommitted INSERTs
YES	WAITFOROUTCOME	Wait for COMMIT or ROLLBACK
YES	Not specified	Skip uncommitted INSERTs
NO	USECURRENTLYCOMMITTED	Skip uncommitted INSERTs
NO	WAITFOROUTCOME	Wait for COMMIT or ROLLBACK
NO	Not specified	Wait for COMMIT or ROLLBACK