On 17 Mar 2006 09:34:16 -0800,
in bit.listserv.ibm-main I wrote:
>I may be mistaken (it happens a couple times a year :-) ), but I was under
>the impression that a parallel sysplex did *not* require an ETR, only a
>sysplex timer.
>
>ETR != Sysplex Timer
Based on feedback from Alan Field, Shane and Giovanni Cerquone, I admit
being egregiously mistaken in this statement. (This group has a great, and
very tolerant, collection of teachers!) I think the following diagram more
accurately summarizes the architecture I was writing about in earlier
messages:
+----------+ +----------+ +----------+
| | | | | |
| zOS A | | zOS B | | zOS C |
| | | | | |
+----------+ +----------+ +----------+
| | |
| | |
+---------------+---------------+
|
|
+---------+
| Sysplex |
| Timer |
| (ETR) |
+---------+
|
|
+-------------+
| External |
| Time |
| Source |
| Interface |
| (CLO Card?) |
+-------------+
|
|
+---------+
| NIST |
| GPS |
| etc |
+---------+
I hope this version is a more accurate representation of reality!
Relating back to the original suggestions of running an NTP server on the
mainframe: that solution will keep all of your shop's systems pretty much
in synch, but without that "External Time Source Interface", your systems
still may not reflect real-world time.
--
Eric Chevalier E-mail: [EMAIL PROTECTED]
Web: www.tulsagrammer.com
Is that call really worth your child's life? HANG UP AND DRIVE!
----------------------------------------------------------------------
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
