Tip:

 To determine the isolation level of a package, execute the following query

: 

     SELECT ISOLATION FROM SYSCAT.PACKAGES

       WHERE PKGNAME =  XXXXXXXX 

       AND PKGSCHEMA =  YYYYYYYY 

where 

XXXXXXXX

 is the name of the package and 

YYYYYYYY

 is the schema name 

of the package. Both of these names must be in all capital letters

.

On database servers that support REXX 

When a database is created, multiple bind files that support the different isolation 

levels for SQL in REXX are bound to the database. Other command line 

processor packages are also bound to the database when a database is created.

REXX and the command line processor connect to a database using a default 

isolation level of cursor stability. Changing to a different isolation level does not 

change the connection state. It must be executed in the CONNECTABLE AND 

UNCONNECTED state, or in the IMPLICITLY CONNECTABLE state.

At the statement level 

Use the WITH clause. The statement level isolation level overrides the isolation 

level specified for the package in which the statement appears.

You can specify an isolation level for the following SQL statements:

SELECT 

SELECT INTO 

Searched DELETE 

INSERT 

Searched UPDATE 

DECLARE CURSOR 

The following conditions apply to isolation levels specified for statements:

The WITH clause cannot be used on subqueries. 

The WITH UR option applies only to read only operations. In other cases, the 

statement is automatically changed from UR to CS. 

From CLI or ODBC at runtime 

Use the 

CHANGE ISOLATION LEVEL

 command. For DB2 Call Level Interface (DB2 

CLI), you can change the isolation level as part of the DB2 CLI configuration. At 

runtime, use the 

SQLSetConnectAttr

 function with the 

SQL_ATTR_TXN_ISOLATION

attribute to set the transaction isolation level for the current connection 

referenced by the 

ConnectionHandle

. You can also use the 

TXNISOLATION

keyword in the 

db2cli.ini

 file .

232 

MySQL to DB2 UDB Conversion Guide