PI92215: SELECT WITH USECURRENTLYCOMMITTED AND EVALUNC NO GETS +100 WHILEANOTHER TRANSACTION IS DOING DELETES + INSERTS IN A SINGLE SCOPE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• SELECT with UseCurrentlyCommitted bind option and subsystem
  parameter EVALUNC NO gets +100 (record not found) while another
  transaction is doing deletes + inserts on the same table in a
  single commit scope.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All Db2 for z/OS users enabling transactions                 *
  * that read data to access the currently                       *
  * committed data when they encounter                           *
  * uncommitted delete operations.                               *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * When users specify USE CURRENTLY                             *
  * COMMITTED for CONCURRENT ACCESS                              *
  * RESOLUTION option, and specify NO for                        *
  * EVALUNC option, SELECT statement                             *
  * incorrectly resulted in SQLCODE100                           *
  * when there are uncommitted deleted                           *
  * rows to be returned.                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply corrective PTF when available                          *
  ****************************************************************
  A transaction is doing INSERT and DELETE operations, another
  transaction is doing SELECT operations concurrently. Several
  currently committed data options are used, e.g. USE CURRENTLY
  COMMITTED, EVALUNC NO, ISOLATION(CS) CURRENTDATA(NO) so that
  SELECT operations can read currently committed data when they
  encountered uncommitted delete operation. There is a timing
  window that caused SELECT to not get back any uncommitted
  deleted records and receive SQLCODE100 instead.
  

Problem conclusion

• The logic that determines whether or not to return an
  uncommitted deleted record has been fixed. With the fix, Db2
  will correctly identify uncommitted deleted records when it
  processes currently committed data options.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UI53813 UI53815

Modules/Macros

• DSNIACCH DSNIFPS1 DSNIRNXT DSNIONX2 DSNISRID DSNIADR  DSNISFS
  DSNISFX2 DSNISFRL DSNIRPRE DSNIOST2
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RC10 PSY UI53813

     UP18/02/28 P F802 ¢

• RB10 PSY UI53815

     UP18/02/28 P F802 ¢

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.