PH61739: ALLOW TO RESTORE THE BEHAVIOR OF THE LOCK TABLE FEATURE THAT EXISTED IN VERSION PRIOR TO 5.2

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• (HPU 5.2 only) In the Db2 HPU version prior to 5.2, the LOCK of
  the table necessary to strictly honor the LOCK YES Db2 HPU
  option or the SHRLEVEL REFERENCE option from the other unload
  tools emulated by Db2 HPU. Was skipped if the Db2 state of the
  tablespace containing the table to be locked prevented to lock
  the table but also to update the table. In such a case, during
  the unload, nothing prevented the restricted state of the
  tablespace to be removed. Thus, reenabling updates and
  preventing to guarantee the consistency of the  unloaded data
  requested by the LOCK YES or SHRLEVEL REFERENCE options. Db2 HPU
  5.2 removed this insufficiently rigorous behavior. As this
  change can negatively impact production unloads that rely on or
  tolerate the former behavior, it should be made available in Db2
  HPU 5.2 while retaining, by default, the new, more rigorous
  behavior.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of Db2 High Performance Unload for     *
  *                 z/OS                                         *
  ****************************************************************
  * PROBLEM DESCRIPTION: (HPU 5.2 only) In Db2 HPU version       *
  *                      prior to 5.2, the LOCK of the table     *
  *                      necessary to strictly honor the LOCK    *
  *                      YES Db2 HPU option or the SHRLEVEL      *
  *                      REFERENCE option from the other unload  *
  *                      tools emulated by Db2 HPU, was skipped  *
  *                      if the Db2 state of the tablespace      *
  *                      containing the table to be locked       *
  *                      prevented to lock the table but also    *
  *                      to update the table. In such a case,    *
  *                      during the unload, nothing prevented    *
  *                      the restricted state of the tablespace  *
  *                      to be removed thus reenabling updates   *
  *                      and preventing to guarantee the         *
  *                      consistency of the  unloaded data       *
  *                      requested by the LOCK YES or SHRLEVEL   *
  *                      REFERENCE options. Db2 HPU 5.2 removed  *
  *                      this insufficiently rigorous behavior.  *
  *                      As this change can negatively impact    *
  *                      production unloads that rely on or      *
  *                      tolerate the former behavior, it        *
  *                      should be made available in Db2 HPU     *
  *                      5.2 while retaining, by default, the    *
  *                      new, more rigorous behavior.            *
  ****************************************************************
  * RECOMMENDATION: Apply the PTF                                *
  ****************************************************************
  allow to restore the behavior of the LOCK table feature that
  existed in version prior to 5.2
  

Problem conclusion

• Code has been changed to fix this problem
  

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:

  UI97541

Modules/Macros

• INZ$$CCQ INZ$$PRM INZMQRY  INZPARM  INZTDSC  INZTOOLS INZTVAR
  INZUTIB1 INZUTIB2 INZUTILC INZUTILD INZUTILK
  

Fix information

• Fixed component name

  DB2 HI PERF UNL

• Fixed component ID

  5697F4400

Applicable component levels

• R520 PSY UI97541

     UP24/07/03 P F407

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.