| Check Solution/Patch to Uninstall (ttpmc2206s000) |  |
| use.session.to check to see if you can uninstall the solutions. You can start this session from the following sessions: Process Solutions (ttpmc2101m000) for a solution. Process Patches (ttpmc2102m000) for a patch. Installation runs (ttpmc2503m000) for an installation run. The session works on solutions that are present in the registry of solutions. The check is always carried out multilevel. As a result all solutions that have the current solution as a related solution, pre-requisites, co-requisites, and post-requisites, are checked. One exception applies: see the Ignore Post-Requisites field for more information. Before the check is carried out, all solutions of the given update VRC and other update VRCs in the VRC combination that have the status To Uninstall, are set back to status Installed. This session sets the status of the solutions that are checked, and that satisfy the conditions to be uninstalled, and have the status Installed, to To Uninstall, unless you select the Retain Status option. If a superseding solution is checked to be uninstalled, the solution's superseded solutions also receives the status To Uninstall. If the superseded solution belongs to a closed patch, you need the password for the patch to be able to uninstall the superseding solution. The next step is to uninstall the solutions. The following figure shows the forms of the session if you start the session either from the Process Solutions (ttpmc2101m000) session or the Process Patches (ttpmc2102m000) session. The following figure shows the form of the session if you start the session from the Installation runs (ttpmc2503m000) session. Related topics PMC introduction PMC overview PMC recipient procedure
Fields | Description
Update VRC | A physical VRC at the PMC recipient side in which updates are installed. Every update VRC has a base VRC linked.
Solution Code | A unique code of the solution or patch in a base VRC.
Installation Run | installation run.
Retain Status | Select this option if you want to check the solutions, but you do not want to change the status of the solutions to To Uninstall. This option is useful if you only want to see the consequences of the uninstallation of a particular solution. The Check Solutions to Uninstall report shows the status that the solution would receive. However, if you look in the Process Solutions (ttpmc2101m000) session or the Process Patches (ttpmc2102m000) seesion, you still see the former status: Installed.
Uninstall Entire Dependent Runs | Select this option to uninstall only the solutions of the specified installation runs and the dependent solutions, or the other solutions of the installation run in which a dependent solution is installed. Example: Assume you have the following Solutions installed: Example: Installed Solutions You want to uninstall Installation run 10. Because of the defined dependencies, you must also uninstall solutions 154, 163, and 199. With this field, you can control whether solution 168 will also be uninstalled. Solution 210 will not be uninstalled, because the solution's installation run does not contain a dependent solution. To uninstall all solutions as of a particular point, you can use the installation run range, for example, 10 to 999999. Yes All solutions of an installation run will be uninstalled if one or more solutions must be uninstalled, due to the defined dependencies. No Only dependent solutions outside the given installation run range will be uninstalled.
Ignore Post-Requisites | Select this check box to ignore post-requisite dependencies. A post-requisite dependency is defined between an old solution and a new solution if the old solution was incorrect. Yes Post-requisite dependencies are ignored. This implies that the older solution remains Installed. However, if both solutions are installed in the same installation run, both solutions will be uninstalled. No Post-requisite dependencies are not ignored. The older solution is also uninstalled.
Detailed Report | Select this check box to print a detailed report with all solutions that will be uninstalled. The solution details are printed in a separate section of the Check Solutions to Uninstall report. For each solution, the dependencies are printed.