PK64424: DATE AND/OR TIME FORMATS ARE GARBLED BY HPU UNLOAD WHEN THERE IS A LOCAL DEFINITION FOR THE FORMATS.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When the installation has a LOCAL definition ( pointed to
  DSNHDECP ) for DATE and TIME formats, HPU UNLOAD can result
  in the format being garbled:
  1. For SELECT processed natively by HPU, DATE or TIME
     columns are generated in ISO format rather than in the
     LOCAL format.
     This occurs in FORMAT DSNTIAUL, FORMAT DELIMITED, when dates
  are converted to CHAR or VARCHAR using scalar function in the
  SELECT, and when date constant appear in a WHERE clause.
     2. For select processed by DB2 (ex: DB2 FORCE or SQL-ACCESS
     ONLY) the data returned by DB2 are in LOCAL format
     (DD/MM/YYYY) while HPU thinks they are in ISO format
     (YYYY-MM-DD). So when reformatting the data before writing it
     in the output file, the date columns are scrambled.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of DB2 High Perfromance Unload.        *
  ****************************************************************
  * PROBLEM DESCRIPTION: This applies to V310 only:              *
  *                      1. Columns with data type BINARY are    *
  *                      incorrectly unloaded: the first 2       *
  *                      bytes of the unloaded data are          *
  *                      replaced by 2 length bytes. PB 9221     *
  *                      2. Errors when the date/time formats    *
  *                       are defined as LOCAL:                  *
  *                      a. For SELECT processed natively, HPU   *
  *                       generate the ISO format for date       *
  *                       columns instead of LOCAL format        *
  *                       defined. This occurs in FORMAT         *
  *                       DSNTIAUL, FORMAT DELIMITED, when date  *
  *                       are converted to CHAR or VARCHAR using *
  *                       scalar function in the SELECT, and     *
  *                       when date constant appear in a WHERE   *
  *                       clause (in this last case the date in  *
  *                       DD/MM/YYYY format will be processed as *
  *                       a DD/JJ/YYYY USA format (month and     *
  *                       days) will be exchanged, which will    *
  *                       NOT return the correct rows, or may    *
  *                       be refused by the syntax parser).      *
  *                      b. For select processed by DB2 (ex:     *
  *                       DB2 FORCE or SQL-ACCESS ONLY) the      *
  *                       data returned by DB2 are in LOCAL      *
  *                       format (DD/MM/YYYY) while HPU thinks   *
  *                       they are in ISO format (YYYY-MM-DD).   *
  *                       So when reformatting the data before   *
  *                       writing it in the output file, the     *
  *                       date columns are scrambled. PB 9280    *
  *                      3. In FORMAT USER, when a date/time or  *
  *                      timestamp is converted to a char with   *
  *                      NULL OFF or NULLID NO, the content of   *
  *                      the output field for null values used   *
  *                      to be blank in HPU 220. In HPU 310 it   *
  *                      was set to 0001-01-01. PB 9329          *
  ****************************************************************
  * RECOMMENDATION: APPLY the PTF.                               *
  ****************************************************************
  1. inznode wad changed to correctly handle binary data.
  2. (complete fix) udbcrfel, inzpab, inzpabf, inzgcrtx, inznode
  were changed so that the DB2 date/time exit is invoked whenever
  necessary. The following restriction apply : with native HPU
  syntax and DELIMITED or VARIABLE formats, date is still
  unloaded with ISO format.
  3.inznode was changed to use the default value corresponding to
  the target data type (i.e. char) default value (blanks) instead
  of the source data type (date/time or timestamp) default value.
  

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

•    INZUTILK
  

Fix information

• Fixed component name

  DB2 HI PERF UNL

• Fixed component ID

  5697F4400

Applicable component levels

• R310 PSY UK39330

     UP08/09/04 P F809

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.