IBM Support

PM70744: EXSLT DATE:DATE-TIME() INCORRECT FOR 30 MIN OFFSET TIMEZONES

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The EXSLT date:date-time() function is incorrect for timezones
    that are offset by 30 minutes, such as India Standard Time
    (IST) GMT+5:30 or Newfoundland Standard Time (NST, Java: CNT)
    GMT-3:30.
    
    The minute part of the timezone offset is calculated as the
    remainder of the total offset divided by the number of
    milliseconds in an hour - which yields a result in
    milliseconds instead of minutes.
    
    This works when the minute offset is 0, but yields 1800000
    when it should be 30, as in the following example:
    
    2012-02-29T11:28:32-03:1800000
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server Feature    *
    *                  Pack for XML XSLT users calling the EXSLT   *
    *                  date:date-time(), date:date(), or           *
    *                  date:time() functions in 30-minute offset   *
    *                  timezones                                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: EXSLT date:date-time() is incorrect     *
    *                      for 30 minute offset timezones          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The EXSLT date:date-time() function is incorrect for timezones
    that are offset by 30 minutes, such as India Standard Time
    (IST) GMT+5:30 or Newfoundland Standard Time (NST, Java: CNT)
    GMT-3:30.
    The minute part of the timezone offset is calculated as the
    remainder of the total offset divided by the number of
    milliseconds in an hour - which yields a result in
    milliseconds instead of minutes.
    This works when the minute offset is 0, but yields 1800000
    when it should be 30, as in the following example:
    2012-02-29T11:28:32-03:1800000
    

Problem conclusion

  • The date:date-time() function now calculates the minute part
    of the timezone offset correctly.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 1.0.0.13. Please refer to the Recommended Updates page
    for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM70744

  • Reported component name

    XML FEATUREPACK

  • Reported component ID

    5724J0856

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-08-13

  • Closed date

    2013-02-06

  • Last modified date

    2013-02-06

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

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

    PM70745

Fix information

  • Fixed component name

    XML FEATUREPACK

  • Fixed component ID

    5724J0856

Applicable component levels

  • R700 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SUPPORT","label":"IBM Worldwide Support"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"1.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
09 February 2022