Subject: ADSM/NT 3.1.2.1 Uninstall Alert

BACKGROUND
----------
A problem has been identified with the level 3.1.2.1 ADSM/NT server
package that was available on index.storsys.ibm.com between the
afternoon of Monday Nov 30 and the morning of Wednesday Dec 2.

The package was removed from index.storsys.ibm.com early on Dec 2
while the cause of the problem was being determined. The corrected
package was made available on Friday, Dec 4.

PROBLEM
-------
When uninstalling the ADSM ODBC component Uninstallshield will remove
a registry key that will prevent the system from booting normally.

HOW TO TELL IF YOU NEED TO ELIMINATE THE PROBLEM
------------------------------------------------
Look at the file: ...\ibm\adsm\readmes\read1st.txt.

The header in packages with the problem will have the following
statement:

  Last Updated: 3.1.2.1

The header in the fixed package will have the following statement:

  Last Updated: 3.1.2.1 (includes fixed uninstall)

Note that if you have the fixed package no further action is required.

TO ELIMINATE THE PROBLEM
------------------------
If the header in your 3.1.2.1 read1st.txt file does not contain the
words (includes fixed uninstall) you will need to eliminate the
problem.

To eliminate the problem you need to delete all .isu files in the ODBC
directory of the ADSM tree.  For example,  

  del c:\"program files"\ibm\adsm\odbc\*.isu

You should not run the ADSM uninstall program until these files have been
deleted. You should also not install any other ADSM maintenance until
these files have been deleted. Failure to remove these files may cause 
your system to not boot normally. 

Note that the number of .isu files in the ODBC directory will depend on how
many times you have applied maintenance so it would be normal to find
one or more .isu files. The problem only occurs in the .isu file installed 
by the original 3.1.2.1 package but it is safe and recommended that you 
remove all .isu files in the ODBC directory.

You can continue to use the original 3.1.2.1 package after the ODBC .isu 
files have been deleted. The only side effect is that Uninstallshield will
not be able to uninstall the ADSM ODBC and Base components until
subsequent ADSM maintenance is applied.

WHAT TO DO IF THE PROBLEM OCCURS
--------------------------------
If you are unable to boot after uninstalling ADSM you should be able
to recover by choosing the NT option to switch to the last known good
configuration during the bootup process.  Note that on NT4 this is
done by pressing 'L' when you are at the Hardware
Profile/Configuration Recovery Menu.