A few months ago we activated the "ACCURACY" parameter with a value of 50 ( the default is zero ) on a few of our z/OS systems ( all systems are z/OS V2R1 ). We verified that the "IEA034I THE TOD CLOCK ACCURACY MONITOR IS ACTIVE." is issued whenever these z/OS systems are IPL'ed. Until Saturday night, we have never received any "alert" from this TOD CLOCK ACCURACY MONITOR. However, we did receive the following message on each z/OS system that has that monitor active: IEA032E TOD CLOCK ACCURACY LIMITS MAY HAVE BEEN EXCEEDED.
The IEA032E messages occurred around 8PM Eastern Time on December 31, 2016. The IEA032E messages were repeated every hour on each z/OS system until about 2AM on January 1, 2017, or about 6 hours after they started. Also, the IEA032E messages have not re-occurred since that 2AM timeframe. We have confirmation from IBM that the IEA032E messages were triggered by the leap second that was inserted into UTC. They also indicated how to perform a leap second adjustment via the STP panels if we needed the 50ms accuracy when the leap second occurred. Has anyone else implemented the TOD accuracy monitor on their z/OS systems? Did anyone else receive the IEA032E messages or did you perform the leap second adjustment ahead of the leap second occurrence? Glenn Miller ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
