>If you're off a second or three, you're right - no biggie. However, if >you've got a multiple-mainframe environment and you're running >time-sensitive transactions, it's best to keep their time in sync as much as >possible. > >> >>> But then, my experience with TOD drift against a known standard has >>> been rather remarkable. Quite seriously, it has been only a few >>> seconds over a year's period of time. >> >> Perception. >> Corporate LAN runs off to a timesource every so often - all the users >> ever see is a consistent (correct) time value. >> Mainframe (even with ETR) wanders around always "off-time" - unless it >> also synchs to a (different) timesource. Given the questions we see >> here on the list, I wonder if the majority of ETRs aren't synched to >> an atomic source at all, but set locally. >>
Is it not time to start plugging those ETRs into a phone jack and using the technology that will correct the time? Go to the SHARE Conference or start researching Server Time Protocol (STP) in the new boxes. NTP is not accurate enough for the amount of work a mainframe can handle. The weenie boxes may be okay processing with a few seconds difference, but Parallel Sysplex can not. Sysplex timers can dial out to a timesource so the operator's wrist watch was only a starting point. And if Corporate allows time to be set that way, shame on them. Let your wan/lan get the time off the mainframe and you will be using a consistent time. Replacing Sysplex Timers: Server Time Protocol (STP) Overview and Planning Part 1 of 2 - 08/15/2007 08:00 Wednesday In this session, part one of two, the speakers will discuss an overview of the Server Time Protocol (STP), the new paradigm for synchronizing clocks between System z servers in a timing network. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
