The isolation level can be specified in several different ways. The following 

heuristics are used in determining which isolation level will be used in compiling 

an SQL statement:

Static SQL:

  If an isolation clause is specified in the statement, then the value of that 

clause is used. 

  If no isolation clause is specified in the statement, then the isolation level 

used is the one specified for the package at the time when the package 

was bound to the database. 

Dynamic SQL:

  If an isolation clause is specified in the statement, then the value of that 

clause is used. 

  If no isolation clause is specified in the statement, and a SET CURRENT 

ISOLATION statement has been issued within the current session, then 

the value of the CURRENT ISOLATION special register is used. 

  If no isolation clause is specified in the statement, and no SET CURRENT 

ISOLATION statement has been issued within the current session, then 

the isolation level used is the one specified for the package at the time 

when the package was bound to the database. 

Note:

 Many commercially written applications provide a method for 

choosing the isolation level. Refer to the application documentation for 

information. 

SQL procedure and isolation level

This section discusses when to specify the isolation level for a SQL procedure. 

At precompile or bind time 

For an application written in a supported compiled language, use the 

ISOLATION

option of the Command Line Processor 

PREP

 or 

BIND

 commands. You can also 

use the PREP or BIND APIs to specify the isolation level.

If you create a bind file at precompile time, the isolation level is stored in the 

bind file. If you do not specify an isolation level at bind time, the default is the 

isolation level used during precompilation. 

If you do not specify an isolation level, the default of cursor stability is used. 

 Chapter 7. Application porting 

231