On Mon, 16 Jun 2008 14:10:51 -0500, McKown, John wrote: >> -----Original Message----- >> [mailto:[EMAIL PROTECTED] On Behalf Of Chauhan, Jasbir >> Sent: Monday, June 16, 2008 2:03 PM >> >> As part of the PCI audit we need to look into adopting NTP >> (network time >> protocol) on the mainframe to ensure all of our 'systems' are >> synchronized. Can STP provide NTP client capability to maintain 'same >> time' across heterogeneous platforms. > >z/OS cannot be an NTP client. However, you can use STP (which is not >NTP!) to maintain the clock on the z and then use z/OS as your NTP >server for the rest of your systems. > There are several sides to this topic:
o AFAIK, there is no way to maintain accurate time on z without spending the big bucks for STP (or ETR, if it's still supported). o With STP, z will probably have the most accurate time of any system in your shop. Logically, z should be the NTP server. o But, as so often stated in this list, logic must sometimes yield to Legacy inertia. And in the OP's case, it appears that "Legacy" is the existing non-z NTP server. IBM would be well advised to learn to play well with others as an NTP client. -- 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
