From:	SMTP%"mose@ns.ccsn.edu"  9-JAN-1995 09:03:03.50
To:	EVERHART
CC:	
Subj:	NTPdate 1.1 for VMS available (mandatory update)

From: mose@ns.ccsn.edu (Russell Mosemann)
X-Newsgroups: comp.protocols.time.ntp,comp.os.vms,vmsnet.networks.tcp-ip.ucx
Subject: NTPdate 1.1 for VMS available (mandatory update)
Date: 6 Jan 1995 18:16:52 -0600
Organization: Concordia College, Seward, NE
Lines: 21
Distribution: inet
Message-ID: <3ekmhkINNcc9@ns.ccsn.edu>
NNTP-Posting-Host: ccsn.edu
Summary: NTPdate 1.1 for VMS available (mandatory update)
Keywords: ntpdate vms
To: Info-VAX@Mvb.Saic.Com
X-Gateway-Source-Info: USENET

   NTPdate 1.0 for VMS recently stopped working.  No, it was not planned
obsolesence.  :-)  As of 1995, the number of seconds counted in VMS
binary time (since November 17, 1858) no longer fits in a variable for
ntp time.  This problem has been corrected in version 1.1 and is
available on

      ftp.ccsn.edu in /pub/ntpdate

   The new version should also be available shortly on louie.udel.edu,
the repository of ntp wisdom.
   For those wondering, ntpdate is similar to rdate (remote date) for
Unix.  It sets the system clock according to a remote server.  While
rdate specifies accuracy to 1 second, NTPdate uses the Network Time
Protocol to achieve much greater accuracy (assuming you have access to
an NTP server).
   RDATE for VMS and NTPdate for VMS work with VMS 5.x, 6.x,
UCX 2.x, 3.x, VAXC and DECC.
-- 
Russell Mosemann     Concordia College      Voice: (402) 643-7445
Computing Center     Seward, NE 68434       Fax:   (402) 643-4073
"Will reading a PowerBook make you computer literate?"