Hi all -

   I mentioned a while back we were using SETCLOCK for year 2000 testing
   on one of our 'crash and burn' machines.  There were quite a few
   people using it, both developers and support people, but somehow our
   925 got into a curious state:

S925(/SYS/PUB):showtime
SUN, OCT 28, 1934,  4:36 AM
S925(/SYS/PUB):showclock

SYSTEM TIME: WED, APR 25, 2027, 11:00:42 PM
[...]

   I'm really at a loss as to how the hardware and software clocks could
   get so out of sync.  Now using SETCLOCK at the CI aborts the CI.  This
   machine is still on MPE/iX X.55.20.  Any clue as to how it got so
   confused (along with us)?

   cv
--
Craig Vespe [log in to unmask] Unison Software 811 Barton Springs, Austin Tx.78704
512-478-0611 http://www.unison.com NASDAQ UNSN disclaimer quote ANSI graphics