ITM OMEGAMON Daylight Savings Time DST Changes

Technote (FAQ)


Question

What is needed for our Tivoli Monitoring products on z/OS to support DST?

Answer

- For Epilog, we recommend shutting down for one hour in the fall (going from daylight savings to standard time) to eliminate the possibility of duplicate timestamps. In the spring (from standard time to daylight savings) No action is needed.

- In classic OMEGAMON, the time is obtained directly from the system clock. No action is needed. The new time will appear automatically.

- The OMEGAMON II CUA, OMEGAVIEW, TEMS, and TEMS agents get the time from ITMS/ENGINE (CL/Engine). In order to pick up the time change you must either recycle the started task or issue the following TIME RESET modify command:

F cua_stc,TIME RESET

The RESET command would result in a message as shown below:

KLVTI002 TIVOLI ENGINE TIME RESET TO: hh:mm:ss DATE: mm/dd/yyyy

ITMS/ENGINE (CL/Engine) messages are stored in internal buffers and written out to the RKLVLOG at periodic intervals. To see the messages you may need to issue the following command after the TIME RESET.

F cua_stc,FLUSH

or the command

F cua_stc,ECHO


- The address spaces which execute EXEC PGM=KLV will take the reset command, this includes hub Tivoli Enterprise Management Servers (HTEMS), the remote Tivoli Enterprise Management Servers (RTEMS), OMEGAMON XE agents, OMEGAMON CUA, OMEGAVIEW and CL/SUPERSESSION.

  1. TIME with no parameters displays the current ITMS/ENGINE time. This may differ from the system local time if it has been changed by the system operator since ITMS/ENGINE has started.
  2. Use "TIME" with the "RESET" option to reset ITMS/ENGINE DATE and TIME to the system local date and time if it has been changed by the system operator. This may be done for example, when daylight saving time starts or ends.
  3. All unexpired timers are updated to reflect the new date and time. RKLVLOG messages, table database timestamps, and NAF records will contain the new date and time. A NAF record is written to indicate the time reset event. User-written NAF programs must consider the time reset if NAF is used for accounting or billing purposes.

Cross reference information
Segment Product Component Platform Version Edition
Systems and Asset Management Tivoli OMEGAMON II for CICS All Versions
Systems and Asset Management Tivoli OMEGAMON II for DB2 All Versions
Systems and Asset Management Tivoli OMEGAMON II for IMS All Versions
Systems and Asset Management Tivoli OMEGAMON II for Mainframe Networks All Versions
Systems and Asset Management Tivoli OMEGAMON II for MVS All Versions
Systems and Asset Management Tivoli OMEGAMON II for SMS
Systems and Asset Management Tivoli OMEGAMON XE for CICS on z/OS All Versions
Systems and Asset Management Tivoli OMEGAMON XE for CICS TG on z/OS 4.2.0, 5.1.0
Systems and Asset Management Tivoli OMEGAMON XE for DB2 Performance Expert for z/OS 4.2.0, 4.1.0, 5.1.0, 5.1.1, 5.2.0
Systems and Asset Management Tivoli OMEGAMON XE for DB2 Performance Monitor for z/OS 5.1.0, 5.1.1, 5.2.0
Systems and Asset Management Tivoli OMEGAMON XE for IMS on z/OS 4.2.0, 3.1.0, 4.1.0, 5.1.0
Systems and Asset Management Tivoli OMEGAMON XE for Linux on zSeries Version Independent
Systems and Asset Management Tivoli OMEGAMON XE for Mainframe Networks 4.2.0, 5.1.0, 5.1.1
Systems and Asset Management Tivoli OMEGAMON XE for Messaging for z/OS 6.0.1, 6.0.0, 7.0, 7.0.1, 7.1.0
Systems and Asset Management Tivoli OMEGAMON XE for Storage Version Independent
Systems and Asset Management Tivoli Composite Application Manager for Application Diagnostics on z/OS 7.1, 6.1, 7.1.1
Systems and Asset Management Tivoli OMEGAMON XE on z/OS z/OS 4.2, 5.1.0, 5.1.1

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Tivoli Monitoring Version 6

Software version:

All Versions

Operating system(s):

z/OS

Reference #:

1569725

Modified date:

2014-03-03

Translate my page

Machine Translation

Content navigation