CA SYSVIEW and Daylight Savings Time (DST) change

book

Article ID: 38328

calendar_today

Updated On:

Products

CA SYSVIEW Performance Management

Issue/Introduction

Question:  

Does CA SYSVIEW have any problems or concerns when it comes to Daylight Savings Time?

Answer: 

SYSVIEW uses the TOD Clock (STCK), which is a monotonic function that is always increasing in value, to calculate intervals and elapsed times. When a DST change occurs, the STCK value does not change. Only the Time Zone Offset, which is adjusted by the Server Time Protocol (STP), is updated. To determine the local time, the TOD Clock (represented in UTC), is adjusted by the Time Zone Offset.

As long as the maintenance specified below (see Resolution section) is applied, there are no known issues with leaving SYSVIEW, SYSVUSER, and the SYSVIEW for CICS data collectors active when a DST change occurs.  If this maintenance is not applied, the recommendation is to stop SYSVIEW, SYSVUSER, and SYSVIEW for CICS in each region prior to the DST change, and restart them afterwards. 

Environment

Release: SYSVIEW 14.2, SYSVIEW 15.0, SYSVIEW 16.0


Component: BASE (MVS), CICS

Resolution

PTF SO08743 for SYSVIEW 16.0

PTF SO08657 for SYSVIEW 15.0

PTF SO08675 for SYSVIEW 14.2  

Additional Information

When displaying log stream data (CTRANLOG, IMSTLOG, etc.) after the time zone change occurred to set the time back (Fall back), data that was recorded in the past hour (that now has a future timestamp) will not appear in the log stream until an hour passes. Adding the CUSHION 01:00:00 NODISCARD keywords to the command string (i.e., CTRANLOG CUSHION 01:00:00 NODISCARD) would allow all the records to be displayed