Conference noted::dnu_osi

2187.0. "Year 2000 and Decnet" by FORTY2::JONES (Neil, the newtrok is the cupmoter) Thu Jun 05 1997 08:01

    
    I have read in other notes that DECnet does not yet offer Year 2000
    support. Is this true?
    
    For interest I have been resetting the clock to the year 1999 to see
    what happens. I realise I may have been a bit foolish to do this but
    I wanted to work out what/how to do this.
    
    First I could only set the clock when the network cable was plugged
    out and I had booted as single-user. If I have the network cable
    plugged in then the time resets itself to the real current time.
    
    I don't have NTP or RDATE configured so my guess is that some network
    service reset the date? Anybody got any ideas?
    
    Also something nasty seems to have happened to my machine with respect
    to udp. That is it no longer seems to exist. As soon as I try to do
    something that involves sockets, such as running dbx, the machine
    crashes. I would really be interested to know how I could fix udp by
    the way, (without reinstalling the o/s).
    
    Neil

>    I have read in other notes that DECnet does not yet offer Year 2000
>    support. Is this true?

I think it would be more correct to say that we don't currently claim Y2K
compliance - this will be changing, because it's a requirement to be Y2K
compliant.  I know testing has been going on - for a few days we had 2 systems
booted into the year 1999 (remember Space 1999?) and let them roll into 2000; I
haven't heard the full results of that test but it has been done.  I think the
biggest problem for the test was getting paks that were valid for 2000.

--Scott

    Regarding your clock being reset - that was probably dtssd - the
    DECnet version of ntp.  --  Vince