PH33917: INTERMITTENT INZX111 T001MG 0 K / 0 K AND SUBSEQUENT ABENDS D37

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• An unload intermittently fails after having
  issued the following messages
  INZX111 ddname 0 K / 0 K REQUESTED ON 2 SYSDA SIZE=(n * p), RC=0
  IEC031I D37-rc,mod, jjj,sss,ddname,
  dev,ser,diagcode,dsname(member)
  This can very rarely occurs if the following conditions are
  fulfilled:
  - a logical unload is processed in native mode
  - the ORDER clause specified by the logical unload triggers the
  INDEXSCAN feature.
  

Local fix

• a new run of the unload usually completes successfully. To avoid
  any occurence of this issue for a sensible job, consider
  specifying the INDEXSCAN NO option if the rlated loss of
  performance is not a problem.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of Db2 High Performance Unload         *
  *                 for z/OS                                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: An unload intermittently fails after    *
  *                      having issued the following messages    *
  *                      INZX111 T001MG 0 K / 0 K REQUESTED ON 2 *
  *                      SYSDA SIZE=(n * p), RC=0                *
  *                      IEC031I   D37-rc,mod, jjj,sss,T001MG,   *
  *                      dev,ser,diagcode,dsname(member)         *
  *                                                              *
  *                      This can very rarely occurs if the      *
  *                      following conditions are fullfilled:    *
  *                      - a logical unload is processed in      *
  *                      native mode                             *
  *                      - the ORDER clause specified by the     *
  *                      logical unload triggers the INDEXSCAN   *
  *                      feature.                                *
  *                                                              *
  *                      This very rare issue occurs when two    *
  *                      Unix threads - one dedicated to reading *
  *                      the LDS of the involved tablespace and  *
  *                      another one dedicated to the sort       *
  *                      process -  which creation is requested  *
  *                      by Db2 HPU in a given order are not     *
  *                      actually created by the system in the   *
  *                      same order. In a nutshell, this occurs  *
  *                      when the sort processing unexpectedly   *
  *                      starts before the reading of the data.  *
  ****************************************************************
  * RECOMMENDATION: Apply the PTF                                *
  ****************************************************************
  Intermittent INZX111 T001MG 0 K / 0 K and subsequent ABENDS D37
  

Problem conclusion

• Code has been changed to fix this problem
  

Temporary fix

Comments

• ×**** PE21/03/31 FIX IN ERROR. SEE APAR PH35906  FOR DESCRIPTION
  ×**** PE21/08/13 FIX IN ERROR. SEE APAR PH39836  FOR DESCRIPTION
  ×**** PE21/09/28 FIX IN ERROR. SEE APAR PH40942  FOR DESCRIPTION
  ×**** PE22/10/17 FIX IN ERROR. SEE APAR PH50224  FOR DESCRIPTION
  

APAR Information

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

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

  UI74571

Modules/Macros

• INZCHECK INZCRX10 INZCRXSM INZCRXSQ INZTPMEM INZUTILK
  

Fix information

• Fixed component name

  DB2 HI PERF UNL

• Fixed component ID

  5697F4400

Applicable component levels

• R510 PSY UI74571

     UP21/03/30 P F103

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.