DB2 FOR LUW / DB2FORLUW / 970 - DB2

SQL Server wrapper uses the default isolation serializable when 
using federated two phase commit. 
 
Here is the reproducing scripts: 
db2 => set passthru <your_server>; 
 
db2 => select transaction_isolation_level from 
sys.dm_exec_sessions where host_name = '<your_federation_host>'; 
 
transaction_isolation_level 
--------------------------- 
                          2 
 
  1 record(s) selected. 
 
db2 => set passthru reset; 
DB20000I  The SQL command completed successfully. 
 
db2 => alter server SQLSERVER options(set DB2_TWO_PHASE_COMMIT 
'N'); 
DB20000I  The SQL command completed successfully. 
db2 => 
db2 => set passthru <your_server>; 
DB20000I  The SQL command completed successfully. 
db2 => select transaction_isolation_level from 
sys.dm_exec_sessions where host_name = '<your_federation_host>'; 
 
transaction_isolation_level 
--------------------------- 
                          2 
 
  1 record(s) selected. 
 
db2 => set passthru reset; 
DB20000I  The SQL command completed successfully. 
 
This APAR will support new behavior: set the remote 
corresponding  isolation according to DB2's isolation.

DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

not known / see Local fix

New requirement for F2PC

forerunner  : APAR is sysrouted TO one or more of the following: IC96413 IC96418 
follow-up : 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

31.05.2013
16.12.2013
16.12.2013