home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!saimiri.primate.wisc.edu!ames!agate!ucbvax!BLACK-ICE.CC.VT.EDU!valdis
- From: valdis@BLACK-ICE.CC.VT.EDU (Valdis Kletnieks)
- Newsgroups: comp.protocols.time.ntp
- Subject: Re: Seeking NTP for IBM MVS and OS/2
- Message-ID: <9301070558.AA15098@black-ice.cc.vt.edu>
- Date: 7 Jan 93 05:59:18 GMT
- References: <726384531.0.CASNER@CASNER.ISI.EDU>
- Sender: daemon@ucbvax.BERKELEY.EDU
- Distribution: inet
- Organization: The Internet
- Lines: 28
- X-Unparsable-Date: Thu, 07 Jan 1993 00:58:51 +22311841
-
- On Wed, 06 Jan 1993 21:28:51 EST, you said:
- > Are there any implementations of NTP available for IBM mainframes
- > and for PC's running OS/2?
- > -- Steve
- > -------
-
- Steve:
-
- I assume you mean for IBM mainframes of the S/390 genre. On those,
- the 'sysplex timer' may provide the needed facilities.
-
- On *all* S/360, S/370, 303x, 43xx, 308x, and 309x boxen, you had to hit
- the 'TOD ENABLE' switch in order to let the operating system actually
- modify the clock. This is a *HARDWARE* interlock implemented in the
- processor controller.
-
- AIX/370 (and presumably AIX/ESA) will run NTP OK, because they access
- the clock via the 'gettimeofday()' call. Unfortunately, MVS is a
- lost cause, because once you hit TOD ENABLE during IPL, the value
- returned by a Store Clock instruction is pretty immutable.
-
- I have no information on what effect the S/390 Sysplex Timer has
- on all of this - it may remove the hardware interlock restriction
- and allow software tweaking of the TOD clock.
- --
- Valdis Kletnieks
- Computer Systems Engineer
- Virginia Tech
-