Use this window to check whether internal code changes meet all the dependencies that must be met to use them with operations that change the internal code of the Hardware Management Console.
Important: | Ordinarily, only an IBM representative checks the dependencies of internal code changes, typically while following a service procedure for changing the console's internal code. If you are not following a service procedure, it is recommended that you check dependencies only with assistance from IBM Product Engineering, provided through your IBM service representative or IBM Support Center. |
Internal code is organized into units call Engineering Changes (ECs), which are referred to also as streams.
Internal code changes may provide new internal code, or correct or improve existing internal code, for particular streams. If internal code changes for multiple streams are needed, together, to complete an addition, correction, or improvement of the CPC's internal code, then the internal code changes have dependencies. For example, if Engineering Change (EC) E12345, change level 001, must be installed and activated before EC E54321 level 005 can be installed and activated, then EC E54321 level 005 has a dependency on EC E12345 level 001.
The dependencies of internal code changes are designated by IBM when the changes are created. After internal code changes are retrieved to the console, their dependencies, if any, are checked automatically whenever you start an operation that will change the console's internal code. Such an operation will be attempted only if all dependencies of the internal code changes are met.
This option provides a means for manually checking the dependencies of internal code changes. Manually checking dependencies is useful:
By manually checking the dependencies of internal code changes you intend to select while performing the operation, you may get a detailed list of the dependencies that would not be met, but which you must meet before or while actually attempting the operation.
Note: | This is especially important if you intend to use specific internal code changes, rather than all changes, while performing the operation. Using specific changes increases the possibility of not specifying one or more dependencies of the specific changes. |
By manually checking the dependencies of internal code changes you selected while attempting the operation, you get a detailed list of the dependencies that were not met, but which you must meet before or while attempting the operation again.
Dependency checking options
To check dependencies of internal code changes manually, select the option that describes the operation and internal code changes for which you want dependencies checked, then click OK.
You can find more detailed help on the following elements of this window:
OK
Cancel
Help