PM56690: DB2 10 - UNLOAD DATE COLUMN IN TIMESTAMP EXTERNAL FORMAT

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • In DB2 10 an UNLOAD of a DATE column in TIMESTAMP EXTERNAL
    format without a length specified returns a 19 byte TIMESTAMP.
    In prior releases a 26 byte TIMESTAMP was returned.
    

Local fix

  • Specify a length parm for the DATE column when doing an
    UNLOAD in TIMESTAMP EXTERNAL format.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: DB2 10 for z/OS users of UNLOAD utility to   *
    *                 unload DATE column to TIMESTAMP EXTERNAL     *
    ****************************************************************
    * PROBLEM DESCRIPTION: When UNLOAD DATE column to TIMESTAMP    *
    *                      EXTERNAL and length not specified,      *
    *                      the output is 19 bytes long instead of  *
    *                      26 bytes long.                          *
    ****************************************************************
    * RECOMMENDATION: Apply corrective PTF when available          *
    ****************************************************************
    When running UNLOAD utility using the following syntax:
    
    UNLOAD TABLESPACE database.tablespace
      FROM TABLE creator.table
        (DATE        POSITION(*)       TIMESTAMP EXTERNAL)
    
    SYSREC output is:
    2011-01-01.00.00.00
    
    But it should look like this:
    2011-01-01.00.00.00.000000
    
    The problem happens because we introduced timestamp precision in
    DB2 10 for z/OS. DATE is considered with no precision, so zero
    precision timestamp is always unloaded for DATE column. Although
    timestamp precision is new feature, UNLOAD should generate 26
    byte timestamp (precision 6) as default.
    
    In addition, if the length specified for TIMESTAMP EXTERNAL is
    26, as in the following syntax:
    
    UNLOAD TABLESPACE database.tablespace
      FROM TABLE creator.table
        (DATE        POSITION(*)       TIMESTAMP EXTERNAL(26))
    
    SYSREC output is:
    2011-01-01.00.00.00   -- 19 byte timestamp plus 7 padding blanks
    
    But it should look like this:
    2011-01-01.00.00.00.000000
    
    Unload should generate 26 byte timestamp for length specified
    equal to 26 as well.
    

Problem conclusion

  • UNLOAD utility is modified to generate 26 byte timestamp
    (precision 6) in SYSREC when no length specified or length
    specified equal to 26 for UNLOAD DATE column to TIMESTAMP
    EXTERNAL.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM56690

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-01-25

  • Closed date

    2012-04-05

  • Last modified date

    2012-05-02

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

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

    UK77843

Modules/Macros

  •    DSNUULVA DSNUUUFA
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UK77843

       UP12/04/26 P F204

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.



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

DB2 for z/OS

Software version:

A10

Reference #:

PM56690

Modified date:

2012-05-02

Translate my page

Machine Translation

Content navigation