On Fri, 2003-05-30 at 16:34, Michael Morgan wrote: > 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. >
The sysplex timer seems to be the creature. We really don't have the budget to purchase one so my thought was to add an ntp child in the OS2 laptops and have that communicate with the ntp server that keeps time for the rest of our network. It's my understanding the support element laptops are the source that the mainframe uses to get time since it seems to be following the clock drift on the primary support element unit. Up until last week we really didn't care about time on the mainframe either but the Java developers have found a problem and since websphere is running under MVS we need to correct it from there. It seems to me that my idea should work but there is still the question of whether, or not, IBM will have a problem with something like this running on the laptops. Has anyone else tried this idea or is time something that just isn't all that important to most mainframe shops?
