PI16437: SYSREC RECORDS MAY BE INCORRECTLY DISCARDED WHEN LOADING A PARTITIONED TABLE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• This APAR addresses the following issues:
  
  1)  In some instances no limit key values are returned by the
      server to the client. The UTSN blocks returned to the client
     have limit key lengths of 0 and contain no limit key data.
      This causes the records to be incorrectly discarded.
  2) There are various problems with the way the partitioning key
     is built from a SYSREC record.  Null indicators are not
     included in the key, default values are ignored and key
     columns are not always padded with the correct pad
     characters.  All of these issues can lead to cases where
     records are incorrectly discarded.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of DB2 Analytics Accelerator Loader    *
  *                 for z/OS                                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: This APAR addresses the following       *
  *                      issues:                                 *
  *                                                              *
  *                      1.  In some instances no limit key      *
  *                          values are returned by the server t *
  *                          the client. The UTSN blocks returne *
  *                          to the client have limit key length *
  *                          of 0 and contain no limit key data. *
  *                          This causes the records to be       *
  *                          incorrectly discarded.              *
  *                      2. There are various problems with the  *
  *                         way the partitioning key is built    *
  *                         from a SYSREC record.  Null          *
  *                         indicators are not included in the   *
  *                         key, default values are ignored and  *
  *                         key columns are not always padded    *
  *                         with the correct pad characters.     *
  *                         All of these issues can lead to      *
  *                         cases where records are incorrectly  *
  *                         discarded.                           *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• Apply the PTF.
  

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

• HLORUSQL
  

Fix information

• Fixed component name

  IDAA LOADER ZOS

• Fixed component ID

  5639OLA00

Applicable component levels

• R110 PSY UI18467

     UP14/06/04 P F406

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.