nv-l
[Top] [All Lists]

Re: Y2K Problem in NV6k 5.1?

To: nv-l@lists.tivoli.com
Subject: Re: Y2K Problem in NV6k 5.1?
From: James_Shanks@TIVOLI.COM
Date: Fri, 19 Feb 1999 09:21:29 -0500
Reply-to: Discussion of IBM NetView and POLYCENTER Manager on NetView <NV-L@UCSBVM.UCSB.EDU>
Sender: Discussion of IBM NetView and POLYCENTER Manager on NetView <NV-L@UCSBVM.UCSB.EDU>
As long as the two-digit date is unambiguous, they are still permitted.
Since you cannot have snmpCollect data from the year 1900, it is
unambiguous.    People are still using "00" to represent the year 2000.  My
VISA has an expiration date of 07/00.

James Shanks
Tivoli (NetView for UNIX) L3 Support



John Creasey <creasey@OZEMAIL.COM.AU> on 02/19/99 01:13:41 AM

Please respond to Discussion of IBM NetView and POLYCENTER Manager on
      NetView <NV-L@UCSBVM.ucsb.edu>

To:   NV-L@UCSBVM.ucsb.edu
cc:    (bcc: James Shanks)
Subject:  Y2K Problem in NV6k 5.1?





I'm not sure if this is a Y2K issue, but snmpColDump still seems
to report the year in its dates as 2 digit.  I thought you had
to remove all 2 digit dates to be fully Y2K compliant.

John Creasey.
Advantra.

<Prev in Thread] Current Thread [Next in Thread>

Archive operated by Skills 1st Ltd

See also: The NetView Web