IBM Support

PM70745: 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 min, 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 V8.0 and   *
    *                  V8.5 XSLT users calling the EXSLT           *
    *                  date:date-time(), date:date(), or           *
    *                  date:time() functions in 30-min offset      *
    *                  timezones                                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: EXSLT date:date-time() incorrect for    *
    *                      30 min offset timezones                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The EXSLT date:date-time() function is incorrect for timezones
    that are offset by 30 min, 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 packs 8.0.0.5 and 8.5.0.1.  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

    PM70745

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-08-13

  • Closed date

    2012-10-02

  • Last modified date

    2012-10-02

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

    PM70744

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

Fix information

  • Fixed component name

    WEBSPHERE APP S

  • Fixed component ID

    5724J0800

Applicable component levels

  • R800 PSY

       UP

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 October 2021