To check the dependencies that must be met to install and activate specific internal code changes, select Install and activate of specific changes.
Automatic dependency checking is performed when you actually attempt to change the internal code of the Hardware Management Console by installing and activating specific internal code changes. But you can use this choice to manually perform the same dependency checking now, without installing and activating the changes or otherwise changing the console's internal code.
Changes checked for dependencies
Selecting this choice checks that dependencies of only the internal code changes you specify on a subsequent window, if the changes are eligible for being installed and activated. That is, dependencies will be checked only for specified internal code changes that were retrieved to the console, but are not currently installed.
Using the results of dependency checking
The results of dependency checking provide information that may assist you with planning and managing internal code changes. For example:
Note: | The detailed information identifies the operations and internal code changes you must use to meet the dependencies. |
Warning: Many combinations of specific internal code changes may meet all dependencies for being installed and activated, but it is recommended that you install and activate all retrieved internal code changes instead. Using specific changes risks installing and activating an untested combination of changes.
Availability of this option
This option is available while any internal code changes are eligible for being installed. That is, this option is available while any changes are retrieved.
Otherwise, the option is unavailable.