[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference proxy::nautilus

Title:	VAX 85xx, 8700, and 88xx Product Information
Notice:	Looking for a patch? See Note 1209.l!
Moderator:	MSE1::SYSTEM

Created:	Fri Feb 14 1986
Last Modified:	Wed Apr 09 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	1443
Total number of notes:	7491

1443.0. "8800 Y2K compliant" by CSC32::MEREOS () Mon Apr 07 1997 22:41

    
    
    This is probably a long shot, but is the Nautilus PRO380
    console software Year 2000 compliant?
    
    Sandra Mereos
    Customer Support Center

T.R Title User Personal
Name Date Lines

1443.1 In the most important sense, yes. ATLANT::SCHMIDT See http://atlant2.zko.dec.com/ Wed Apr 09 1997 02:50 35

T.R	Title	User	Personal Name	Date	Lines
1443.1	In the most important sense, yes.	ATLANT::SCHMIDT	See http://atlant2.zko.dec.com/	`Wed Apr 09 1997 02:50`	35
	Sandra: > This is probably a long shot, but is the Nautilus PRO380 > console software Year 2000 compliant? It depends on what you mean by "compliant". :-) Way back when, before Y2K testing was the rage, I did some testing. From what I remember, P/OS displays dd-mmm-yy dates and won't let you enter a date that is greater than '99, so all the file directories ON THE CONSOLE will show 01-Jan-00 sort of dates in the next "millenium". And I suppose any date-based DCL commands like MCR> DIR /SINCE will select the wrong files. I wrote a hack (called OLDMAN.MAC) which would correct this problem, at least until 2027. It did this by reaching into the P/OS exec and smashing years < 50 into years+100, so '00 became 100, '01 became 101, etc. The date printout routines still showed '00, '01, and so forth, but now date comparisons worked correctly. I'm pretty sure that OLDMAN was never shipped with any version of the Console and I have no idea if the official support folks could still find it or build it. But you might ask them, if you can find them. (Send me mail if you can't.) Meanwhile, all this has very little bearing on the operation of the VAX. You MAY need to reset the VAX Time-of-Year clock after the big roll-over into 2000, but it should work fine after that. So in that most important sense ("Will the VAX keep working?"), yes, the Console should be Y2K compliant. Atlant

Sandra:

> This is probably a long shot, but is the Nautilus PRO380
> console software Year 2000 compliant?

  It depends on what you mean by "compliant". :-)

  Way back when, before Y2K testing was the rage, I did some
  testing. From what I remember, P/OS displays dd-mmm-yy
  dates and won't let you enter a date that is greater than
  '99, so all the file directories *ON THE CONSOLE* will show
  01-Jan-00 sort of dates in the next "millenium". And I
  suppose any date-based DCL commands like MCR> DIR /SINCE
  will select the wrong files.

  I wrote a hack (called OLDMAN.MAC) which would correct this
  problem, at least until 2027. It did this by reaching into
  the P/OS exec and smashing years < 50 into years+100, so
  '00 became 100, '01 became 101, etc. The date printout
  routines still showed '00, '01, and so forth, but now
  date comparisons worked correctly. I'm pretty sure that
  OLDMAN was never shipped with any version of the Console
  and I have no idea if the official support folks could still
  find it or build it. But you might ask them, if you can find
  them. (Send me mail if you can't.)

  Meanwhile, all this has very little bearing on the operation
  of the VAX. You *MAY* need to reset the VAX Time-of-Year clock
  after the big roll-over into 2000, but it should work fine after
  that.

  So in that most important sense ("Will the VAX keep working?"),
  yes, the Console should be Y2K compliant.

                                   Atlant