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. If you sync to WAVY, or via Internet, or via GPS, even once a day, you're pretty much set anyway. If your mainframe clock is losing more than 2 seconds a day, you're not scrubbing your incoming power well enough (IMNSHO).
Generally, I prefer to keep systems in sync as much as possible if the business needs to accurately track the transaction timings from the terminal through the network up to the mainframe and back again. It also comes in handy to have accurate time stamps for SWIFT (and even some ACH) transactions. But then again, I'm a bit of a horophile (no sniggering, it doesn't mean THAT) so I've got a variety of atomic clocks and watches all over the place. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Eric Bielefeld Sent: Friday, May 18, 2007 20:29 To: [email protected] Subject: Re: Synchronize Time Between Mainframe and Servers? Unless you have some extremely time sensitive applications, if your running a sysplex and all the lpars are using the same time, whats the big deal. If you're off by less than a second or three, I doubt if most things would really matter. I'm sure there are a lot of things that would matter, but I doubt if the last 2 jobs I had - one in manufacturing and one in catalog sales, would really matter. Eric Bielefeld Sr. z/OS Systems Programmer Milwaukee, Wisconsin 414-475-7434 ----- Original Message ----- From: "Shane" <[EMAIL PROTECTED]> > On Fri, 2007-05-18 at 18:19 -0400, Thompson, Steve wrote: > >> 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. > > It's about time IBM allowed the clock correction to be driven by an > "accepted" source. Maybe the next step will be to just be a (local) > client like everyone else. > It's just a server after all ... > > Shane ... ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
