PH30540: INCORRECT DISPâTICHING OF UNLOADED ROWS OVER OUTPUT DATASETS IF BOTH GLOBAL AND PARTITION DDNAME SPECIFIED

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• (HPU 5.1 Only) Some of the output datasets specified to receive
  the unloaded data (OUTDDN option) at partition level (i.e. one
  data set per partition) do not contain the expected rows.
  This occurs when the following conditions are fulfilled :
  - OUTDDN or UNLDDN specifies a ""root"" ddname (i.e. ddnames
  with this prefix and a numerical suffix are allocated in the
  JCL)
  a ""partition"" ddname (i.e. root + numerical suffix) is
  allocated for every partition of the table space, except for
  some of them
  - the ""root"" ddname is allocated
  - the LDS parallelism is less than the number of partitions to
  be unloaded
  In such a case, the data set allocated to the root ddname should
  receive the data from the partition for which no partition
  ddname is specified and every dataset allocated as a partition
  ddname should receive the data from the corresponding partition.
  When this issue occurs, some of the dataset associated to the
  partition ddnames are empty and the rows expected in these
  dataset are gathered in the dataset associated with the root
  ddname.
  

Local fix

• specify a partition ddname for every partition
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of Db2 High Performance Unload         *
  *                 for z/OS                                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: Some of the output datasets specified   *
  *                      to receive the unloaded data (OUTDDN    *
  *                      option) at partition level (i.e. one    *
  *                      data set per partition) do not contain  *
  *                      the expected rows.                      *
  *                                                              *
  *                      This occurs when the following          *
  *                      conditions are fulfilled :              *
  *                      - OUTDDN or UNLDDN specifies a "root"   *
  *                      ddname (i.e. ddnames with this prefix   *
  *                      and a numerical suffix are allocated in *
  *                      the JCL)                                *
  *                      a "partition" ddname (i.e. root +       *
  *                      numerical suffix) is allocated for      *
  *                      every partition of the table space,     *
  *                      except for some of them                 *
  *                      - the "root" ddname is allocated        *
  *                      - the LDS parallelism is less than the  *
  *                      number of partitions to be unloaded     *
  *                                                              *
  *                      In such a case, the data set allocated  *
  *                      to the root ddname should receive the   *
  *                      data from the partition for which no    *
  *                      partition ddname is specified and every *
  *                      dataset allocated as a partition ddname *
  *                      should receive the data from the        *
  *                      corresponding partition. When this      *
  *                      issue occurs, some of the dataset       *
  *                      associated to the partition ddnames are *
  *                      empty and the rows expected in these    *
  *                      dataset are gathered in the dataset     *
  *                      associated with the root ddname.        *
  ****************************************************************
  * RECOMMENDATION: Apply the PTF                                *
  ****************************************************************
  Incorrect dispatching of unloaded rows over output datasets if
  both global and partition ddname specified
  

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:

Modules/Macros

• INZHPUCL INZTVAR  INZUTILK
  

Fix information

• Fixed component name

  DB2 HI PERF UNL

• Fixed component ID

  5697F4400

Applicable component levels

• R510 PSY UI73305

     UP20/12/31 P F012

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.