PK11272: THE CONVERSION OF A FLOAT TO A CHAR GENERATES AN INVALID FLOATING POINT CONSTANT.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• FLOAT data generates an invalid data format. Getting the
  following error message on the load utility:
  INPUT FIELD 'xxxxxxx' INVALID FOR 'xxxxxxxx.xxxxxxxx', ERROR
  CODE '03'
  (RE)LOAD PHASE STATISTICS - NUMBER OF INPUT RECORDS PROCESSED=1
  UTILITY DATA BASE SERVICES MEMORY EXECUTION ABENDED,
  REASON=X'00E40323
  The conversion of a FLOAT to a CHAR generates an invalid
  floating point constant.     PB 7367
  Additional Symptoms:
  1. Incorrect output for a graphic row.
     Wrong evaluation of LENGTH(graphic_column)).
     PB 7400
  2. DECIMAL(DAY()) unloaded with incorrect precision.
     PB 7405
  3. Time argument of TIMESTAMP scalar function ignored.
     PB 7399
  4. Enhancement: full support of LENGTH scalar function.
     PB 7426
  5. Wrong precision when CHAR(decimal_expression) in unloaded.
     PB 7403
  6. Wrong precision when evaluating a decimal division.
     PB 7402
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of DB2 High Performance Unload.        *
  ****************************************************************
  * PROBLEM DESCRIPTION: FLOAT data generates an invalid data    *
  *                      format. Getting the following error     *
  *                      message on the load utility:            *
  *                      INPUT FIELD 'xxxxxxx' INVALID FOR       *
  *                      'xxxxxxxx.xxxxxxxx', ERROR CODE '03'    *
  *                      (RE)LOAD PHASE STATISTICS - NUMBER OF   *
  *                      INPUT RECORDS PROCESSED=1 UTILITY DATA  *
  *                      BASE SERVICES MEMORY EXECUTION ABENDED, *
  *                      REASON=X'00E40323                       *
  *                      The conversion of a FLOAT to a CHAR     *
  *                      generates an invalid floating point     *
  *                      constant.     PB 7367                   *
  *                      Additional Symptoms:                    *
  *                      1. Incorrect output for a graphic row.  *
  *                         Wrong evaluation of                  *
  *                         LENGTH(graphic_column). PB 7400      *
  *                      2. DECIMAL(DAY()) unloaded with         *
  *                         incorrect precision. PB 7405         *
  *                      3. Time argument of TIMESTAMP scalar    *
  *                         function ignored. PB 7399            *
  *                      4. Enhancement: full support of LENGTH  *
  *                         scalar function. PB 7426             *
  *                      5. Wrong precision when                 *
  *                         CHAR(decimal_expression) is          *
  *                         unloaded. PB 7403                    *
  *                      6. Wrong precision when evaluating a    *
  *                         decimal division. PB 7402            *
  ****************************************************************
  * RECOMMENDATION: APPLY the PTF.                               *
  ****************************************************************
  

Problem conclusion

• - Module UDBSPXWR was changed to process correctly CHAR(float).
  Additional fixes:
  1. Module UDBSPXWR was changed to process correctly
     LENGTH(graphic).
  2. Module INZNODE was changed to process correctly
     DECIMAL(DAY()) and DECIMAL(MONTH()).
  3. Module UDBSPXWR was changed to process correctly the
     TIMESTAMP function.
  4. Module INZNODE was changed to remove limitation of the
     LENGTH function.
  5. Module INZNODE was changed to convert the result of the
     decimal expression with the correct precision and scale
     before applying the CHAR function.
  6. Module INZNODE was changed to evaluate correcly the precision
     and scale in case of decimal division.
  

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:

  UK07312 UK07313

Modules/Macros

•    INZUTILB
  

Fix information

• Fixed component name

  DB2 HI PERF UNL

• Fixed component ID

  5697F4400

Applicable component levels

• R210 PSY UK07312

     UP05/09/22 P F509

• R220 PSY UK07313

     UP05/09/22 P F509

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.