Gary, Doug, and everyone:
Hopefully this is the last time I'll have to explain this.
Whether you have NetView V4 or V5, your NetView is Y2K ready now. That
doesn't mean it's perfect, but that all major functions, daemons, netmon
polling and discovery, maps, events, rulesets, and what-have-you, work just
fine when the millennium changes. But detailed and systematic testing by
Tivoli verification found what amounts to three (3) minor problems. These
are fixed in NetView V5.1 and U453385. I will explain them below.
Doug -
There are no Y2K fixes I am aware of in U451880. I could be wrong, but I
just checked the README again.
But it doesn't really matter, since U453385 will include what is in
U451880, anyway. When will V4 go out of support? There has been an
announcement that it will be the end of this year, but I do not know how
firm that is. Check with your Tivoli marketing rep for an official answer.
I don't have it and this is not the place to get it.
Gary -
The three minor user interface problems are these:
(1) Some logs in /usr/OV/log have misleading dates in their timestamps.
One said "1900" for "2000", others said "100" (UNIX programmers will
recognize "100" as the output of the mktime command -- see the man pages).
These did not affect anything, except that they look funny. They have all
been fixed.
(2) Using the filter editor you could not set a viewing filter based on the
date and time in the year 2000. The GUI only accepts two-digit dates and
this meant that "00" was interpreted as 1969, before the start of the UNIX
clock. This has been fixed, though the GUI still only accepts 2 digits.
This one defect is the only one which could have been called a bug, but it
is in a feature very few people use. And you could still use the Search
facility of the Events workspace as an alternative, so it is a very minor
one indeed. And it has been fixed.
(3) a sample in the xnmgraph man page for graphing random values fails at
exactly 00/00/00 (the stroke of midnight) because you cannot divide by
zero. Start it up again at one minute after midnight and it would run just
fine. This has been fixed so that it runs through midnight too.
Everyone -
Now that we've explored this is detail, I hope everyone will understand why
I say your NetView is Y2K ready now, but there are a couple of minor
problems fixed in the next round of maintenance. Please do not go to your
managers and tell them that NetView is not Y2K compliant. It is. And I am
tired of explaining to my management that I did not tell you it wasn't.
James Shanks
Tivoli (NetView for UNIX) L3 Support
Douglas Staub <Douglas_Staub@KEYBANK.COM> on 08/19/98 02:58:00 PM
Please respond to Discussion of IBM NetView and POLYCENTER Manager on
NetView et alia <NV-L@UCSBVM.UCSB.EDU>
To: NV-L@UCSBVM.UCSB.EDU
cc: (bcc: James Shanks)
Subject: Re: Year2000 -- Least Path Of Resistance?
I have just installed U451880, which is a NetView 4.1 Y2K (I think) - does
U453385 have other Y2K fixes? Is support for Netview 4.1 supposed to cease
at the end of the year or is this even known yet? Thanks for your time.
Doug Staub
(216)689-0632
Key Services Corporation
dstaub@keybank.com
(Embedded
image moved James_Shanks @ TIVOLI.COM
to file: 08/19/98 02:03 PM
PIC05852.PCX)
Please respond to NV-L@UCSBVM.ucsb.edu
To: NV-L @ UCSBVM.ucsb.edu
cc: (bcc: Douglas Staub/GL/KSC/KeyCorp)
Subject: Re: Year2000 -- Least Path Of Resistance?
The easiest thing to do right now is to wait for U453385 which is in test
right now, and apply it when it comes out in early September. Your V4
system is Y2K-ready now, for all intents and purposes, as I have said
before. There are just a couple of minor user interface problems cleared
up in that PTF.
James Shanks
Tivoli (NetView for UNIX) L3 Support
"Boyles, Gary P" <gary.p.boyles@INTEL.COM> on 08/19/98 12:58:05 PM
Please respond to Discussion of IBM NetView and POLYCENTER Manager on
NetView et alia <NV-L@UCSBVM.UCSB.EDU>
To: NV-L@UCSBVM.UCSB.EDU
cc: (bcc: James Shanks)
Subject: Year2000 -- Least Path Of Resistance?
We're moving to NetView On NT V5.1, but we also have some
AIX systems running NetView V4.1.1, which I have to make sure
our Year2000 compliant (as a backup plan to NV on NT).
Which requires the least work:
a) Moving from NetView V4.1 (last PTFs installed
U438904 & U440147) to a Year2000 version of V4.1.2+
b) Moving from current NetView V4.1 new NetView V5.1
Again, this is a backup plan, and my real intent is to use NV NT
(so I'm looking for the least amount of upgrade work).
Thanks in advance.
Gary Boyles, Intel Corporation gary.p.boyles@intel.com
PIC05852.PCX
Description: Binary data
|