If for any reason, you want to maintain the same behavior as in releases prior to DB2 9.7, you can also set the CUR_COMMIT database configuration parameter to DISABLED. To understand how the same scenario may behave without CUR_COMMIT, set the registry variable and stop and start the instance. On a DB2 command window, issue:
Currently committed is now disabled, run the same SQL commands from DB2 command prompt, you can see the deadlock.
Right pane shows the output of the sample scenario without currently committed semantics. User B will get SQL0911N with Reason code 2 due to deadlock.
To maintain the default behavior of DB2 9.7 change the CUR_COMMIT value to ON. On a DB2 command window, issue: