IBM Support

IT25561: INCORRECT TIMEZONE INDICATOR WHEN DATES ARE CLOSE TO DST BOUNDARIES

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • When a DateTime object is formatted for display, for example by
    CASTING CURRENT_TIME to a String, if the formatting pattern
    contains a timezone indicator and the current time is within +/-
    the raw GMT offset for that timezone away from a DST boundary
    then the timezone indicator may be incorrect.
    
    For example if the DST boundary is:
    
    2111-01-02 01:00:00 GMT
    
    And the local timezone is GMT+1 then between the following time
    the timezone indicator will incorrectly be calculated as GMT+2
    instead of GMT+1:
    
    2111-01-02 00:00:01 (GMT) 01:00:01 (local)
    2111-01-02 00:01:00 (GMT) 03:00:01 (local)
    
    The date and time is otherwise correct and the DST adjustment is
    applied correctly only the timestamp indicator is incorrect.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus version 10 or App Connect
    Enterprise version 11.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    <span style="background-color:rgb(255, 255, 255)">When a
    DateTime object is formatted for display, for example by
    </span><span style="background-color:rgb(255, 255, 255)">CASTING
    CURRENT_TIME to a String, if the formatting pattern </span><span
    style="background-color:rgb(255, 255, 255)">contains a timezone
    indicator and the current time is within +/- </span><span
    style="background-color:rgb(255, 255, 255)">the raw GMT offset
    for that timezone away from a DST boundary  </span><span
    style="background-color:rgb(255, 255, 255)">then the timezone
    indicator may be incorrect.                  </span>
    <span style="background-color:rgb(255, 255, 255)">
    
    </span>
    <span style="background-color:rgb(255, 255, 255)">For example if
    the DST boundary is:                            </span>
    <span style="background-color:rgb(255, 255, 255)">
    
    </span>
    <span style="background-color:rgb(255, 255, 255)">2111-01-02
    01:00:00 GMT                                        </span>
    <span style="background-color:rgb(255, 255, 255)">
    
    </span>
    <span style="background-color:rgb(255, 255, 255)">And the local
    timezone is GMT+1 then between the following time </span><span
    style="background-color:rgb(255, 255, 255)">the timezone
    indicator will incorrectly be calculated as GMT+2 </span><span
    style="background-color:rgb(255, 255, 255)">instead of GMT+1:
                                                 </span>
    <span style="background-color:rgb(255, 255, 255)">
    
    </span>
    <span style="background-color:rgb(255, 255, 255)">2111-01-02
    00:00:01 (GMT) 01:00:01 (local)                     </span>
    <span style="background-color:rgb(255, 255, 255)">2111-01-02
    00:01:00 (GMT) 03:00:01 (local)                     </span>
    <span style="background-color:rgb(255, 255, 255)">
    
    </span>
    <span style="background-color:rgb(255, 255, 255)">The date and
    time is otherwise correct and the DST adjustment is </span><span
    style="background-color:rgb(255, 255, 255)">applied correctly
    only the timestamp indicator is incorrect.  The problem is
    caused by an ambiguous conversion when formatting the
    timestamp.</span>
    

Problem conclusion

  • When creating a DateTime object or a Time object using
    CURRENT_TIME or CURRENT_GMTTIMESTAMP the milliseconds since
    epoch are stored with the object. If this object remains
    unmodified then the milliseconds since epoch is used when
    formatting the object for display meaning ambiguous conversions
    during DST boundaries can not occur.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v10.0      10.0.0.20
    v11.0      11.0.0.8
    
    The latest available maintenance can be obtained from:
    http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041
    
    If the maintenance level is not yet available,information on
    its planned availability can be found on:
    http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT25561

  • Reported component name

    INTEGRATION BUS

  • Reported component ID

    5724J0540

  • Reported release

    A00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-07-05

  • Closed date

    2020-03-27

  • Last modified date

    2020-03-27

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

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

Fix information

  • Fixed component name

    INTEGRATION BUS

  • Fixed component ID

    5724J0540

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
27 March 2020