IBM Support

PI49398: TIMESTAMP WITH TIME ZONE VALUE IS NOT UNLOADED CORRECTLY WHEN AN EXTERNAL PARM IS SPECIFIED TO INCREASE THE TIMESTAMP PRECISION

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If a customer specifies an EXTERNAL parm to increase the
    precision of a TIMESTAMP WITH TIME ZONE column when doing an
    UNLOAD, the expanded microsecond value of the timestamp shifts
    the time zone value to the right.  But, the time zone value
    is truncated as it exceeds the length of the original timestamp
    value.  And, then the unloaded timestamp value is padded with
    spaces up to the length specified with the EXTERNAL parm.
    A LOAD that tries to use the SYSREC and SYSPUNCH generated by an
    UNLOAD that expands the precision of the timestamp with
    time zone value will fail with MSGDSNU334I.
    

Local fix

  • Don't specify an EXTERNAL parm to expand the precision of a
    TIMESTAMP WITH TIME ZONE when doing an UNLOAD.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All DB2 10 for z/OS users of UNLOAD utility  *
    *                 with a TIMESTAMP WITH TIMEZONE column.       *
    ****************************************************************
    * PROBLEM DESCRIPTION: TIMESTAMP (n) WITH TIMEZONE column is   *
    *                      unloaded incorrectly during an UNLOAD   *
    *                      TABLESPACE utility with TIMESTAMP WITH  *
    *                      TIMEZONE EXTERNAL (nn) specified.       *
    ****************************************************************
    * RECOMMENDATION: Apply corrective PTF when available          *
    ****************************************************************
    The UNLOAD utility was run on a table with a TIMESTAMP (n) WITH
    TIMEZONE column.  The UNLOAD field specification for the column
    specified EXTERNAL (nn) to increase the precision of the
    TIMESTAMP.  The TIMESTAMP WITH TIMEZONE was unloaded
    incorrectly.  The last two bytes of the value were truncated.
    
    Example of the incorrect value of TIMESTAMP (7) WITH TIMEZONE
    value unloaded specifying TIMESTAMP WITH TIMEZONE EXTERNAL (35)
    1999-12-31-12.59.59.123456700-11:
    
    Example of the correct value of TIMESTAMP (7) WITH TIMEZONE
    value unloaded specifying TIMESTAMP WITH TIMEZONE EXTERNAL (35)
    1999-12-31-12.59.59.123456700-11:30
    

Problem conclusion

  • UNLOAD utility code has been modified to correct the problem.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI49398

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-09-28

  • Closed date

    2015-12-29

  • Last modified date

    2016-02-01

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

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

    UI34134

Modules/Macros

  • DSNUULVA
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UI34134

       UP16/01/15 P F601

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.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
01 February 2016