On Tue, 17 Jun 2008 23:08:42 +0900, Timothy Sipples wrote: >Actually, as of October, 2007, System z's Server Time Protocol (STP) can >act as a Simple Network Time Protocol (SNTP)/NTP ... > >http://www.ibm.com/systems/z/advantages/pso/stp/ntp.html > Hooray!
>Also, I agree that it is highly desirable to have your mainframe act as the >master (S)NTP server ... > >http://publib.boulder.ibm.com/infocenter/zos/v1r9/index.jsp?topic=/com.ibm.zos.r9.halu101/sntpdinfo.htm > >So, in summary, you can use the STP feature to let the mainframe get a >master time for your organization (via SNTP/NTP client support, such as by >connecting to a dedicated GPS box that delivers its time signal via a Gulp. $$$? >closed NTP link). Then use the mainframe's SNTPD -- included with z/OS -- >to keep every other server and client in sync. That'd be the preferred >approach. > Now you must face the organizational politics. The group with the existing NTP server may not wish to relinquish its position in the pecking order, and argue, "We were given the requirement to provide 5-second accuracy compared to NIST and 1-second agreement across the installation. We are meeting that requirement and operating successfully. Can you provide a business justification for spending $$$ to get accuracy 1000 times better than needed?" They may be deaf to the argument, "We're the best so we should be the master." By being in closer agreement with NIST, you may be perceived as violating established practice. -- gil ---------------------------------------------------------------------- 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
