IBM Support

JR41543: OPERATIONS CONSOLE DATABASE TIMESTAMPS CAN BE INCORRECT WHEN EVENTS OCCUR ACROSS DAYLIGHT SAVING TIME CHANGES

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • perations Console database timestamps can be incorrect when
    events across daylight saving time changes.
    
    This can be seen in two places. The first is in job run
    information, the second in system resource information.
    
    The problem in job run information is caused by the DataStage
    engine writing times, to be processed by the EngMonApp
    Operations Console process, in local time.
    The EngMonApp reading the times and the DataStage engine get out
    of step as daylight saving times change and incorrect timestamps
    can be written to the database.
    
    The solution to this is for the DataStage Engine to write all
    its timestamps as UTC timestamps. This means that daylight
    saving time changes have no adverse effect.
    
    The problem in system resource information is caused by the two
    Operations Console processes ResTrackApp and ResMonApp
    communicating in local time, where across a daylight saving time
    change the two processes no longer agree on the local time
    without restarting the processes.
    
    The solution to this is for the communication between the two
    processes to be in UTC timestamps avoiding any daylight saving
    time change issues.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users of Operations Console, across daylight saving time
    changes.
    ****************************************************************
    PROBLEM DESCRIPTION:
    When daylight saving causes the local time to change by an hour,
    some data in Operations Console can be stored with the wrong
    date and time. This means that some job run information or
    system resource information will be shown with time offset from
    the new local time.
    ****************************************************************
    RECOMMENDATION:
    Apply patch or fix pack.
    ****************************************************************
    

Problem conclusion

  • All internal components of Operations Console have been changed
    to always communicate with each other in UTC to avoid issues
    with local time daylight saving changes.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR41543

  • Reported component name

    WIS DATASTAGE

  • Reported component ID

    5724Q36DS

  • Reported release

    870

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-12-22

  • Closed date

    2012-01-30

  • Last modified date

    2012-01-30

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

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

Modules/Macros

  • SERVER
    

Fix information

  • Fixed component name

    WIS DATASTAGE

  • Fixed component ID

    5724Q36DS

Applicable component levels

  • R870 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSVSEF","label":"InfoSphere DataStage"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.7","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
11 October 2021