IBM Support

IV42059: CALENDAR DISPLAYS WORK TIMES INCORRECTLY FOR MONTHS WHERE DAYLIGHT SAVINGS STARTS AND FINISHES

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as unreproducible.

Error description

  • Environment:
    Version IBM Maximo Asset Management 7.5.0.3 Build 20120713-1120
    DB
    Build V7503-01
    IBM Maximo for Transportation 7.5.0.0-20121011-0616 Build
    20110415-1936
    DB Build V7500-06 HFDB Build HF7500-07
    IBM Maximo Linear Management 7.5.0.0 Build 20120713-1120 DB
    Build V7500-
    01
    Tivoli's process automation engine 7.5.0.3 Build 20120713-1120
    DB Build
    V7503-157
    IBM Maximo for Service Providers 7.5.1.1-20121028-2135 Build
    20120702-
    1801 DB Build V7511-18 HFDB Build HF7511-02
    Customization for JHG 7.5.0.0 Build 20121207-1212 DB Build
    V7500-216
    IBM Maximo Asset Management Scheduler 7.5.1.0 Build
    20120713-1120 DB
    Build V7510-123
    
    Server OS Windows Server 2008 6.0 build 6002 Service Pack 2
    Timezone: UTC+10:00 (Canberra, Melbourne, Sydney)
    
    Problem Description:
    Calendar displays work times incorrectly for months where
    daylight
    savings starts and finishes
    
    When viewing a calendar, in specific months (i.e. October and
    April) it
    displays the working times incorrectly.  This coincides with
    the
    start/finish months of daylight savings.
    
    Replication steps:
    1. Create a calendar start date 01/07/2012 to 30/06/2015
    2. Define a Shift Pattern of 7, with 1 to 5 as working days
    
       Start Day: MONDAY             Start Time   End Time  Work
    Hours
       Sequence of Pattern Day: 01    8:00        17:00       08:00
                                02    8:00        17:00       08:00
                                03    8:00        17:00       08:00
                                04    8:00        17:00       08:00
                                05    8:00        17:00       08:00
                                06
                                07
    
    3.Apply this Shift Pattern to the calendar
    4.Navigate through the months and observe results below
    For example:
    September 2012: OK. Work days are from Monday to Friday.
    October 2012: Not OK.  Work days are from Sunday and Thursday.
    November 2012: OK.
    December 2012: OK.
    January 2013:  OK.
    February 2013: OK.
    March 2013:    OK.
    April 2013:    Not OK. Work days are from Thursday to Monday
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Maximo Users in Australia using Calendars                    *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * CALENDAR DISPLAYS WORK TIMES INCORRECTLY FOR MONTHS WHERE    *
    * DAYLIGHT SAVINGS STARTS AND FINISHES                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply fixpack 7.5.0.5 of Base Services                       *
    ****************************************************************
    

Problem conclusion

Temporary fix

Comments

  • Unable to reproduce the issue with work days in October 2012 or
    April 2013.  Machine was set to UTC +10:00 Canberra, Melbourne,
    Sydney in Date and Time, Time Zone Settings.  In addition, the
    Region and Langugae, format set to English (Australia).  The
    user's default profile was set to a locale of en_AU, calendar
    type of gregorian and time zone of Australia/Canberra.
    

APAR Information

  • APAR number

    IV42059

  • Reported component name

    MAXIMO SCHEDULE

  • Reported component ID

    5724R46SE

  • Reported release

    750

  • Status

    CLOSED UR5

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2013-05-08

  • Closed date

    2013-08-05

  • Last modified date

    2013-08-05

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

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

Modules/Macros

  • MAXIMO
    

Fix information

Applicable component levels

  • R750 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS9NUN","label":"Maximo Asset Management Scheduler"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"750","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
05 August 2013