Use a response file to uninstall maintenance silently.
Use the Update Installer program from the same user ID that installed the product that you are updating. Otherwise, the file ownership mismatches might require correction by the root user.
Follow these steps to uninstall maintenance silently:
The following response file demonstrates how to uninstall a fix pack silently.
################################################################################ # # This is the silent install response file for uninstalling maintenance packages # using the update installer. # # A common use of an options file is to run the wizard in silent mode. This lets # the options file author specify wizard settings without having to run the # wizard in graphical or console mode. To use this options file for silent mode # execution, *uncomment* and modify the parameters defined within. # # Use the following command line when running the wizard from the update # installer directory: # # update -options responsefiles/uninstall.txt -silent # # Enclose all values within a single pair of double quotes. # ################################################################################ ################################################################################ # # Used to input the maintenance backup package filename to be uninstalled. # This is the same filename as the package that was originally installed. # A maintenance package can only be uninstalled if a backup package exists. # # For example: -W backup.package="PQ20029.pak" # # Note: If you do not specify a package, then a default of the last installed maintenance # package is used, as the following example demonstrate: # -W backup.package="6.1.0.1-WEBSV-FEP-WinX32-FP000001.pak" ################################################################################ # # Used to modify the product install location that will be updated. # This value should be left commented out if the Update Installer is # being run from the recommended location, as the following example demonstrates: # # For example: -W product.location="C:\Program Files\IBM\WebSphere\AppServer" # # Note: The product install location needs to be specified, and it needs to # be the full path. # -W product.location="D:\IBM\WebSphere\AppServerNonroot3" ################################################################################ # File Permission Checking # # The installer does not check that it has sufficient file permissions to # perform the installation by default. # # Uncomment the following option to notify the installer that it should # check that it has sufficient file permissions to perform the required # install operation on each file to be installed. # # This option is not applicable for Windows. # # -OPT checkFilePermissions="true" # ############################################################################### # # AIX Non-root user limitation # # The AIX user account running the Update Installer program also must be able to # run the slibclean command; otherwise, a root user must run the slibclean command # before the Update Installer program runs. # # Uncomment the following option to notify the installer that a root user has run # the slibclean command before the Update Installer program runs. # #-OPT rootUserHasRunSlibcleanCommandSuccessfully="true" ################################################################################ # # Do not edit these values. # -W update.type="uninstall"
In this information ... | IBM Redbooks, demos, education, and more(Index) |