We have not implemented this yet, but we are planning on doing it this summer....z/OS 1.4 added an SNTP daemon:
From: z/OS V1R4.0 CS: IP Configuration Guide: 2.13 Document Number: SC31-8775-02 � Copyright IBM Corp. 2000, 2002 | 2.13 Chapter 19. SNTPD daemon | SNTPD is a TCP/IP daemon that is used to synchronize time between a client | and a server. Simple Network Time Protocol (SNTP) is a protocol for | synchronizing clocks across a WAN or LAN through a specific formatted | message. An External Time Reference (ETR), named stratum 0, is chosen as | the highest timer reference used for synchronization. A stratum 1 server | is attached to and receives the time from the stratum 0 timer. For | example, the z/OS sysplex timer could be a stratum 0 timer, and z/OS | Communications Server would be a stratum 1 server. A client attached to | the stratum 1 server can also be a stratum 2 server, receiving the time | from the stratum 1 server, and so on. SNTP uses UDP packets for data | transfer with the well-known port number 123. RFC 2030 (Mills 1996) | describes SNTP. You can start SNTPD from the z/OS shell or as a started | procedure. Each of these methods is described below. TCP/IP must be | started prior to starting SNTPD. As I read this, I should be able to use an atomic clock as a stratum 0 server, with z/OS being stratum1 which should have the net effect of getting z/OS time as accurate as any of our other clocks using ntp. ----------------------------------- Jeremy Warren Sr. Systems Programmer KB Toy Stores mailto:[EMAIL PROTECTED]@kbtoys.com "Steven A. Adams" <[EMAIL PROTECTED]> Sent by: Linux on 390 Port <[EMAIL PROTECTED]> 05/31/2003 02:18 PM Please respond to Linux on 390 Port To: [EMAIL PROTECTED] cc: Subject: Re: [LINUX-390] Time Sync 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?
