A short while ago our console (a PRO380) was updated and the clock
came up one year advanced.  The ramifications from this took us more
than a week to straignten out and I dreamed of a way to prevent this
nightmare.  I've come up with a procedure which will warn me that
something is awry and I hope that others may find the idea worthwhile. 
Near the beginning of the file SYSTARTUP_V5.COM, before any files are
touched, I scan a list of files that I know are touched during a
normal period of up-time.  If latest of the RDTs (revision date_time)
is within 30 days of what the system thinks is the current time, I
accept it.  I throw away any RDT which is too near the supposedly
current date_time on the presumption that the file may have just been
touched.  To implement in your location you will have to examine your
system for some files which meet the criteria I outlined above.

Gerson H Cohen
National Institutes of Health, 5/335
Bethesda, MD  20892
ghc@vger.niddk.nih.gov


Command file used is included.