James:
  I have the NV 5.1.1 CD, and had schedule the installation for 3/13/99. Need 
less to say I will postponed. 
Will I get the updated version automatically or should I  write to swlist again?
Thank in advance.
Gil Irizarry
>>> James Shanks <James_Shanks AT TIVOLI DOT COM> 03/09 8:21 PM >>>
Yup.  Please see my append "Problem found in 5.1.1".  It was discovered on
Friday, APAR IX88166 was created,  and some of our best engineers worked
over the weekend to fix it.   The fix was applied to our systems and the
reporting customer system yesterday, and the results certified today.

The gist of it is that status propagation will fail on some routers (and
only on routers) when their interfaces change status.  They may stay green
even when their interfaces go red, or they may stay blue if unmanaged and
re-managed.  That is a horrible bug, I know.  That's why we worked so hard
to fix it as soon as it was discovered.

Only those customers who have already installed 5.1.1 are affected.
Shipment of 5.1.1 has been halted until a new copy can be used to replace
it in Software Distribution.

More details are in the "Problem found in 5.1.1" append I just sent.

On behalf of the entire Support organization, my apologies.  We have
already begun meetings to discuss how to prevent this kind of thing (a bug
of this magnitude going undetected in the Verification process) happening
again.

James Shanks
Tivoli (NetView for UNIX) L3 Support



Art DeBuigny <debuigny AT DALLAS DOT NET> on 03/09/99 06:11:27 PM

Please respond to Discussion of IBM NetView and POLYCENTER Manager on
      NetView <NV-L AT UCSBVM.UCSB DOT EDU>

To:   NV-L AT UCSBVM.UCSB DOT EDU 
cc:    (bcc: James Shanks)
Subject:  IX88166???





I've heard it through the grapevine that IX88166 has just been released,
and that all NetView customers may be impacted.  This fix supposedly
corrects NetView's status propogation.  Also, there are only two ways to
fix the system up after applying the code fixes, either restart your
database from scratch, or manually hit each and every device and change the
status propogation from Compound, to symbol, then back to compound again.

Needless to say this does not please me at all.  I have a very large
database with a very large number of objects, and I have noticed no
problems in this arena.  I don't want to jump unless I am 100 percent sure
that there is a problem.

Can someone from Tivoli confirn or deny this problem and give us more
details about how to confirm its impact on our systems?

Thanks;

Art DeBuigny
debuigny AT dallas DOT net