All of our S/390 systems (Linux/390, VM & z/OS) get the time from an external time source..ie the IBM 9037 sysplex timer. We manually set the time in the sysplex timer (about once a year :)) We don't care how accurate the time is, so we've never looked into having the sysplex timer get it's time via NTP. I'm sure this is possible, however.
"Steven A. Adams" wrote: > > On Fri, 2003-05-30 at 14:10, Alan Cox wrote: > > On Gwe, 2003-05-30 at 22:40, Steven A. Adams wrote: > > > This might be a little off topic so feel free to let me know if it is. > > > > > > Our z/800 is about 90 seconds off of time with the rest of the network > > > and this is starting to cause some havoc with an application that we are > > > currently developing. I have been told that getting the mainframe to > > > sync up is probably an expensive proposition. I am being told that there > > > is not a way to use ntpd under one of my Linux guests to set the clock > > > and propagate these settings through VM to the CTC. So, if you don't > > > mind me asking, what solutions are commonly used for time sync? > > > > In the Linux world and to an extent nowdays in the Windows world NTP > > seems to be the popular system. Its an internet standard that will let > > you lock your machiens to each other and to global time sources that > > ultimately anchor back to atomic clocks. > > > > xntpd is the Linux daemon for this, but I don't know if VM has anything > > of its own to talk ntp > > Thanks Alan, > I am very familiar with ntp. My question was intended to see what others > do to sync the hardware clock on the mainframe itself. Is there an ntp > equivalent that will set and maintain the hardware clock on the z/800? > --
