Well, I think we've found a simple way out of this. The PC our console automation runs on is already sync'd with the network, which gets its time from an external source. For the time being, we are going to set up a script to capture this time and issue console SET CLOCK commands. May be off by a few seconds, but good enough for our humble purposes at this time.
In the future, we will consider STP and sync to the same source as the network, which might eventually evolve to option 1, below (those of you who have fought in the Architecture Wars know you have to choose your battles carefully). Timothy Sipples of IBM wrote: At present you have two choices for keeping mainframe time in sync with other servers' time clocks: 1. Make the mainframe boss. This is the best choice for a lot of reasons. Set up the mainframe to get its external time reference, then use the built-in time server so that other servers can get time sync over the network, perhaps in a hierarchy. 2. Have both the mainframe and your organization's master time server (if they are unfortunately different entitites) both sync to the same external time reference (such as NIST dial-up). This might not offer as much accuracy, but it might be sufficient for certain purposes. Again, thanks to all who contributed. ---------------------------------------------------------------------- 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
