PH68521: Incorrect unloaded data for an unload in native mode involving CHAR(graphic-expression)

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• The data unloaded by a logical unload is affected by one of the
  following issues:
  - one or more fields from the unloaded data contain incorrect
    data
  - the selected rows are not the expected ones
  
  This occurs if all the following conditions are true:
  - the unload is run in native mode
  - the SELECT statement specifies an SQL expression involving
    the CHAR scalar function with an argument of GRAPHIC or
    VARGRAPHIC data type
  - for at least one row, the result of the
    CHAR(graphic-expression) expression contains padding
    characters (see details below)
  
  Root cause
  ------
  The root cause of the issue is a wrong evaluation of
  CHAR(graphic-expression) consisting of the use of an incorrect
  of padding character when needed. Instead of the SBCS padding
  character (converted to the target CCSID), the first byte of the
  DBCS padding character converted into the target CCSID is used.
  
  Incorrectness of the unloaded data
  -----
  The root cause described above can have various impacts that
  depend on the SQL expression containing the
  CHAR(graphic-expression), the involved data and source and
  target CCSIDs. The incorrectness of the output cannot be
  predicted.
  
  Scope of the issue
  -----
  The result of the CHAR(graphic-expression) expression contains
  padding characters if all the conditions below are met:
  - the GRAPHIC data used as an argument of the CHAR function
    contains at least one character which transcription in the
    target CCSID is encoded in less than three bytes
  - the GRAPHIC data converted into the target CCSID is less than
    255-byte long
  

Local fix

• Perform the unload in SQL mode using DB2 FORCE where applicable
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of Db2 High Performance Unload for     *
  *                 z/OS                                         *
  ****************************************************************
  * PROBLEM DESCRIPTION: The data unloaded by a logical unload   *
  *                      is affected by one of the following     *
  *                      issues:                                 *
  *                      - one or more fields from the unloaded  *
  *                        data contain incorrect data           *
  *                      - the selected rows are not the         *
  *                        expected ones                         *
  *                                                              *
  *                      This occurs if all the following        *
  *                      conditions are true:                    *
  *                      - the unload is run in native mode      *
  *                      - the SELECT statement specifies an SQL *
  *                        expression involving the CHAR scalar  *
  *                        function with an argument of GRAPHIC  *
  *                        or VARGRAPHIC data type               *
  *                      - for at least one row, the result of   *
  *                        the CHAR(graphic-expression)          *
  *                        expression contains padding           *
  *                        characters (see details below)        *
  *                                                              *
  *                      Root cause                              *
  *                      ------                                  *
  *                      The root cause of the issue is a wrong  *
  *                      evaluation of CHAR(graphic-expression)  *
  *                      consisting of the use of an incorrect   *
  *                      of padding character when needed.       *
  *                      Instead of the SBCS padding character   *
  *                      (converted to the target CCSID), the    *
  *                      first byte of the DBCS padding          *
  *                      character converted into the target     *
  *                      CCSID is used.                          *
  *                                                              *
  *                      Incorrectness of the unloaded data      *
  *                      -----                                   *
  *                      The root cause described above can have *
  *                      various impacts that depend on the SQL  *
  *                      expression containing the               *
  *                      CHAR(graphic-expression), the involved  *
  *                      data and source and target CCSIDs. The  *
  *                      incorrectness of the output cannot be   *
  *                      predicted.                              *
  *                                                              *
  *                      Scope of the issue                      *
  *                      -----                                   *
  *                      The result of the                       *
  *                      CHAR(graphic-expression) expression     *
  *                      contains padding characters if all the  *
  *                      conditions below are met:               *
  *                      - the GRAPHIC data used as an argument  *
  *                        of the CHAR function contains at      *
  *                        least one character which             *
  *                        transcription in the target CCSID is  *
  *                        encoded in less than three bytes      *
  *                      - the GRAPHIC data converted into the   *
  *                        target CCSID is less than 255-byte    *
  *                        long                                  *
  *                                                              *
  *                      Local fix: Perform the unload in SQL    *
  *                      mode using DB2 FORCE where applicable   *
  ****************************************************************
  * RECOMMENDATION: Apply the PTF                                *
  ****************************************************************
  Incorrect unloaded data for an unload in native mode involving
  CHAR(graphic-expression)
  

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:

  UO05888 UO05904

Modules/Macros

• INZUTILK
  

Fix information

• Fixed component name

  DB2 HI PERF UNL

• Fixed component ID

  5697F4400

Applicable component levels

• R520 PSY UO05888

     UP25/11/27 P F511

• R610 PSY UO05904

     UP25/11/27 P F511

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.