IBM Support

IJ28306: INCORRECT DATE SELECTION DISPLAY WHEN USER TIME ZONE IS DIFFERENT THAN DATABASE AND APPLICATION SERVER TIME ZONE

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

  • DESCRIPTION:
    When filtering for dates on the List View in an application
    with a Date/Time field, and the user profile has a Time Zone
    specified that is different than the database and application
    server's UTC time zone, the lookup shows incorrect or
    misleading/unexpected default date and time selections in the
    lookup.
    
    STEPS TO REPRODUCE:
    -Prerequisite Condition: the database time zone and the
    application server time zone must be set to UTC
    -Set the database (example used is Oracle) time zone to UTC:
    1. Log in to maximo database server as system
    2. Execute following commands:
      ALTER DATABASE SET TIME_ZONE = '+00:00'; (Oracle syntax)
      connect / as sysdba;
      shutdown
      startup
    3. Verify the database time zone with following command:
      SELECT DBTIMEZONE FROM dual;
    4. Set the Maximo application server Time Zone to be UTC
    5. Log in to maxdemo instance
    6. Go To Profile | Default Information
    7. In the Time Zone field | Select Value
    8. In the Value column enter "toronto" and press Enter
    9. Click America/Toronto
    10. Click OK
    11. Go To System Configuration | Platform Configuration |
    Application Designer
    12. In the Application field enter "wotrack" and press Enter
    13. Click WOTRACK to open the record
    14. Click on the List View tab
    15. Click the Scheduled Start field to highlight it
    16. Click the Control Properties button on the toolbar
    17. In the Attribute field | Select Value
    18. In the Attribute field enter "targstart" and press Enter
    19. Click TARGSTARTDATE where the Object value is WORKORDER
    20. In the Label field enter "Target Start Date"
    21. Click the checkbox for "Sortable?"
    22. Save the record
    23. Click the X to close the Table Column Properties dialog
    24. Sign out
    25. Log in
    26. Verify that the time display is 4 hours earlier than the
    application server/client pc time:
    27. Go To Work Orders | Work Order Tracking
    28. Common Actions | New Work Order
    29. Compare the time value in the Status Date field to the time
    displayed on the client PC
    30. Common Actions | Clear Changes, then click No
    31. Available Queries | All Records
    32. On the Target Start Date field click the Select Date and
    Time button
    
    RESULT:
    Yesterday's date is highlighted as the current date; the first
    available time selection in the right pane is 8:00 PM; the
    summary is that the default date and time selection is the
    previous date at 8:00 PM
    
    EXPECTED RESULT:
    Today's date should be highlighted as the current date; the
    first available time selection in the right pane should be 8:00
    AM; the default date and time selection should be the current
    date at 00:00, or current time range
    
    REPORTED IN VERSION:
    Tivoli's process automation engine 7.6.1.2 Build 20200715-0100
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * MAXIMO                                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Incorrect date selection display when user time zone is      *
    * different than database and application server time zone     *
    ****************************************************************
    

Problem conclusion

  • _The fix for this APAR is contained in the following maintenance
    package: release\fix pack for Release 7.6.1.3 Product_
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ28306

  • Reported component name

    MAXIMO ASST MGM

  • Reported component ID

    5724R46AM

  • Reported release

    761

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-09-22

  • Closed date

    2021-07-02

  • Last modified date

    2021-07-02

  • 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

    MAXIMO ASST MGM

  • Fixed component ID

    5724R46AM

Applicable component levels

[{"Type":"MASTER","Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKT6","label":"IBM Maximo Asset Management"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]

Document Information

Modified date:
03 July 2021