Pat, It is that simple. My guess is that SNTPD task queries the time in the processor clock (think TIME or STCK macro) and I presume formats the result in an appropriate NTP format and makes it available on the appropriate port (123?) to all requesters.
If you have an ETR AND you set and correct it using an external source (like NIST) then you will be able to provide accurate time to your organization. If you set the mainframe clock with the operator's wristwatch then you might not have accurate time but you will have consistent timestamps across all platforms which is what you are requesting i.e. no more transactions completing on one platform before they have begun on another. Alan -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Miller, Pat Thanks to all who have commented. It's been an education. SNTPD started task. Seems simple enough. Howsomever, neither the IP Config guide nor Reference tells you much more than the name of the procedure, where to find the sample, and what it does. I.e., neither tells you how it works or any setup you have to provide in order for it to key off an ETR. Surely I have to at least point something to the ETR and/or provide some authentication? Pat, You don't need a Sysplex timer to do this. The sysplex timer ensures the mainframe(s)have a consistent time. With or without a timer you can run an SNTP task on the mainframe (its part of TCP/IP since about z/OS 1.6), otherwise look for Keith Clapp's excellent SNTP product. Have your enterprise query the SNTP on the mainframe and set their clocks off that for a consistent timestamp across your organization. Developers are asking me if we can do this to prevent anomalies between timestamps across platforms. In case it's an issue, no, I don't have a sysplex or timer. ---------------------------------------------------------------------- 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
