IBM Support

PI55344: The job logs are producing a date such as 2016-12-28 as opposed to 2015-12-28 during the last week of the year

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • During the last week of the year the job log directory
    structure is producing a directory with the wrong date.  The
    date produced is one year in advance.  You will see
    2016-12-28 as opposed to 2015-12-28 in your directory
    structure for the job logs.  This issue does not effect what
    is printed out in the logs, but only the directory
    structure.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Liberty Profile- Batch               *
    ****************************************************************
    * PROBLEM DESCRIPTION: The job logs are producing a date such  *
    *                      as 2016-12-28 as opposed to 2015-12-28  *
    *                      during the last week of the year        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The issue is that during the last week of the year the job log
    directory structure is producing a directory with the wrong
    date.  The date produced is one year in advance.  For example
    you will see 2016-12-28 as opposed to 2015-12-28 in your
    directory structure for the job logs.  Switching from the ISO-
    8601 week year calendar format to the normal calendar format
    fixes this issue.
    

Problem conclusion

  • The date format used to retrieve the year has been changed. When
    using SimpleDateFormat with "YYYY-MM-dd" it will produce 2016-12
    29 and when using SimpleDateFormat with "yyyy-MM-dd" it will
    produce 2015-12-29, this is an example using the date of
    December 29th, 2015.  This is because YYYY is ISO-8601 week year
    which looks at the week containing January 1st as the first week
    of 2016 and yyyy which is the normal calendar year which will
    produce 2015.  This issue does not effect what is printed out in
    the logs, but only the directory name.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 8.5.5.10.  Please refer to the Recommended Updates page for
    delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

  • Available upon request.
    

Comments

APAR Information

  • APAR number

    PI55344

  • Reported component name

    WAS LIBERTY COR

  • Reported component ID

    5725L2900

  • Reported release

    855

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-01-13

  • Closed date

    2016-01-22

  • Last modified date

    2016-01-22

  • 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

    WAS LIBERTY COR

  • Fixed component ID

    5725L2900

Applicable component levels

  • R855 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSD28V","label":"WebSphere Application Server Liberty Core"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"855","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
13 October 2021