PH64299: A LOGICAL UNLOAD RUN IN NATIVE MODE AND SPECIFYING A HEXADECIMALCONSTANT PRODUCES INCORRECT DATA

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• The data unloaded by Db2 HPU for a logical unload is affected
  by at least one of the following issues:
  - case 1) The unloaded records contain incorrect data
  - case 2) The selected rows are not the relevant/expected ones
  
  This can occur if all the following required conditions are
  fulfilled:
  - the logical unload in question is run in native mode
  - the input/unloaded table data is not in EBCDIC
  - the SELECT statement specifies an SQL expression containing a
  hexadecimal constant for at least one of the following items:
  - case 1) a column of the resulting table,
  - case 2) a predicate of a WHERE clause.
  
  When additional conditions regarding
  - the encoding requested for the unloaded data
  - and the data type of the items of the SQL expression that
  contains the the SQL expression that cannot be comprehensively
  detailed appl, the SQL expression is incorrectly evaluated as
  the encoding of the hexadecimal constant is unduly considered
  as being EBCDIC instead of the encoding of the unloaded table.
  
  For example, the unload is affected if the following expression
  CHAR (col_1) !! X'0A' is specified where the data type of col_1
  is part is either a numeric data type or is
  date/time/timestamp. An expression like col_1  !! X'0A' does
  not trigger the issue if the data type of col_1 is a char or
  varchar datatype.
  

Local fix

• run the unload in SQL mode by specifying Db2 FORCE.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of Db2 High Performance Unload for     *
  *                 z/OS                                         *
  ****************************************************************
  * PROBLEM DESCRIPTION: The data unloaded by Db2 HPU for a      *
  *                      logical unload is affected by at least  *
  *                      one of the following issues:            *
  *                      - case 1) The unloaded records contain  *
  *                        incorrect data                        *
  *                      - case 2) The selected rows are not     *
  *                        the relevant/expected ones            *
  *                                                              *
  *                      This can occur if all the following     *
  *                      required conditions are fulfilled:      *
  *                      - the logical unload in question is     *
  *                        run in native mode                    *
  *                      - the input/unloaded table data is not  *
  *                        in EBCDIC                             *
  *                      - the SELECT statement specifies an     *
  *                        SQL expression containing a           *
  *                        hexadecimal constant for at least     *
  *                        one of the following items:           *
  *                      - case 1) a column of the resulting     *
  *                        table,                                *
  *                      - case 2) a predicate of a WHERE        *
  *                        clause.                               *
  *                                                              *
  *                      When additional conditions regarding    *
  *                      - the encoding requested for the        *
  *                        unloaded data                         *
  *                      - and the data type of the items of     *
  *                        the SQL expression that contains      *
  *                        the SQL expression                    *
  *                      that cannot be comprehensively          *
  *                      detailed appl, the SQL expression is    *
  *                      incorrectly evaluated as the encoding   *
  *                      of the hexadecimal constant is unduly   *
  *                      considered as being EBCDIC instead of   *
  *                      the encoding of the unloaded table.     *
  *                                                              *
  *                      For example, the unload is affected if  *
  *                      the following expression CHAR (col_1)   *
  *                      !! X'0A' is specified where the data    *
  *                      type of col_1 is part is either a       *
  *                      numeric data type or is                 *
  *                      date/time/timestamp. An expression      *
  *                      like col_1  !! X'0A' does not trigger   *
  *                      the issue if the data type of col_1 is  *
  *                      a char or varchar datatype.             *
  *                                                              *
  *                      Local fix: run the unload in SQL mode   *
  *                      by specifying Db2 FORCE.                *
  ****************************************************************
  * RECOMMENDATION: Apply the PTF                                *
  ****************************************************************
  a logical unload run in native mode and specifying a
  hexadecimal constant produces incorrect data (incorrout)
  

Problem conclusion

• Code has been changed to fix this problem
  

Temporary fix

Comments

• ×**** PE25/02/28 FIX IN ERROR. SEE APAR PH65475  FOR DESCRIPTION
  

APAR Information

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

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

  UI99746

Modules/Macros

• INZUTILK
  

Fix information

• Fixed component name

  DB2 HI PERF UNL

• Fixed component ID

  5697F4400

Applicable component levels

• R510 PSY UI99746

     UP25/01/30 P F501

• R520 PSY UI99745

     UP25/01/30 P F501

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.