| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 62.1 | Ask Storage Directly... | XDELTA::HOFFMAN | Steve, OpenVMS Engineering | Wed Mar 12 1997 16:30 | 11 |
| : Does anyone know whether there are Year 2000 implications for HSCs or
: similar devices?
(Above cross-posted in SIOG::YEAR2000 17.*.)
I'd check directly with the Cronic and HSx teams directly -- they may
or may not be following the OpenVMS Y2K notes conference... (There
does not seem to be much (anything?) on Cronic about Y2K. And there
is information that the current Cronic release -- V8.6 -- is likely
the last Cronic release for the HSC series...)
|
| 62.2 | See SSAG::ASK_SSAG 6475.* | XDELTA::HOFFMAN | Steve, OpenVMS Engineering | Fri Mar 14 1997 15:29 | 0 |
| 62.3 | Y2K Compliance for controllers | KAPTIN::BLEI | Larry Bleiweiss 237-6080 SHR3-2/X17 | Wed Mar 19 1997 14:52 | 31 |
| Year 2000 Storage compliance including leap year for hardware devices
__________________________________________________________
A - Do they accept a date from controllers console
B - Receive date information during initialization from host
C - Can they accept dates beyond Dec 31, 1999
D - Roll the date over from Dec 31,1999 to Jan 1, 2000 on internal clock
E - Can they print dates beyond Dec 31, 1999
F - Can they compute leap years beyond 1996 (29 February 2000)
A B C D E F
HS1CP Y Y Y Y Y Y
HSD05 NA NA NA NA NA NA*
HSD10 N Y Y Y Y Y
HSD30 Y Y Y Y Y Y
HSD50 Y Y Y Y Y Y
HSCXX Y Y Y Y Y Y
KDM70 N Y Y Y Y N**
HSJxx Y Y Y Y Y Y
CIPCA NA NA NA NA NA NA
SWXNA Y Y Y Y Y Y
SWXRC-04/05 Y Y Y Y Y Y
HSZ20 Y Y Y Y Y Y
HSZ40 Y Y Y Y Y Y
* Does not have an internal clock
** reports: 01 March 2000
NOTE: The KDM70 (which has been EOLed for many years) does not report the
leap day correctly in the year 2000. A blitz is being written to inform
the field of this anomaly and how to correct it.
|
| 62.4 | Thanks | SIOG::FARRELLY | | Tue Mar 25 1997 11:25 | 1 |
| Thanks Larry,Steve - I appreciate the information. Pat.
|