| Print Dependencies (Multilevel) (ttpmc1440m000) |  |
| Use this session to print the dependencies multi-level. For each Solution in the range the dependencies are listed. The following figure shows the form of the session with the default field values: The way of printing depends on the dependency types. If a solution has a Post-requisite dependency, a separate entry is printed just like if the post-requisite solution was in the given solution range. The same applies to Co-requisite solutions. So, post- and co-requisite dependencies can be seen in the tree of the original solution, but they are not exploded in the tree of the solution being processed, but in a separate tree. Pre-requisite solutions are shown in the tree of the solution being processed. This is done multi-level. The level on which pre-requisite solutions occur is printed by the system. The direct pre-requisite solutions get level 1, the pre-requisites of the pre-requisite solutions get level 2, etc. Example Solution: 123000
Level | Solution
1 | 112463
.2 | 118403
..3 | 117043
...4 | 116432
1 | 120534
1 | 122539
.2 | 118543
.2 | 122463
..3 | 118403
...4 | 117043
....5 | 116432
.2 | 119004
1 | 116302
If there are large dependency trees, this session may run a long time. Moreover, the disk space used to store intermediate results may be significant. The sessions shows a progress indicator, showing you that it is still busy. The most important information in the progress indicator is the size of the intermediate file. If this file becomes too large, you can stop the printing. If you stop the printing, only the selection of data stops. The session will still try to produce the report with the data gathered until the moment of stopping. The system will need extra disk space to sort the intermediate file. Several options are present to influence the output and the running time of the session. Related topics PMC introduction PMC overview PMC distributor procedure
Fields | Description
Base VRC | A means in PMC to identify products in a unique way. Updates at the distributor side are provided with the base VRC identifier. A base VRC can contain the code of the physical VRC in which the related master product is installed, for example, B61_a, but can also be a code not related to a physical VRC, for example, 7.6_a_tt. At the recipient side, every update VRC is linked to a base VRC identifier. The installation process checks if the base VRC identifier of the update matches with the base VRC identifier of the update VRC. If not, you cannot install the update in that update VRC.
Solution | The unique identification code of the solution in a base VRC.
Stop at Released Patches | If you select this check box, the amount of output being generated will be reduced. The system will print the dependency tree multi-level, but as soon as it encounters a solution in the tree, which belongs to a released patch, this solution itself is printed, but the dependencies of the solution are not printed. Note If the given solution or a solution in the given range belongs to a released patch, the system will print all dependent solutions within this released patch, but as soon as it encounters a solution belonging to another released patch, this solution is not exploded anymore. Example: Solution: 123000
Level | Solution | SP
1 | 112463 |
.2 | 118403 | SP2
..3 | 117043 | SP1
...4 | 116432 | SP1
1 | 120534 |
1 | 122539 |
.2 | 118543 | SP2
.2 | 122463 |
..3 | 118403 | SP2
...4 | 117043 | SP1
....5 | 116432 | SP1
.2 | 119004 | SP2
1 | 116302 | SP1
If you select this option, the following data will be printed: Solution: 123000
Level | Solution | SP
1 | 112463 |
.2 | 118403 | SP2
1 | 120534 |
1 | 122539 |
.2 | 118543 | SP2
.2 | 122463 |
..3 | 118403 | SP2
.2 | 119004 | SP2
1 | 116302 | SP1
Suppress Repeating Dependency Trees | If you select this check box, the amount of output being generated will be reduced. As soon as a solution is processed in a tree, that is printed already, the solution is printed with a * character, but is not exploded anymore. Example: Solution: 123000
Level | Solution | SP
1 | 112463 |
.2 | 118403 | SP2
..3 | 117043 | SP1
...4 | 116432 | SP1
1 | 120534 |
1 | 122539 |
.2 | 118543 | SP2
.2 | 122463 |
..3 | 118403 | SP2
...4 | 117043 | SP1
....5 | 116432 | SP1
.2 | 119004 | SP2
1 | 116302 | SP1
If you select this option, the following data will be printed: Solution: 123000
Level | Solution | SP
1 | 112463 |
.2 | 118403 | SP2
..3 | 117043 | SP1
...4 | 116432 | SP1
1 | 120534 |
1 | 122539 |
.2 | 118543 | SP2
.2 | *122463 |
.2 | 119004 | SP2
1 | 116302 | SP1
The tree of solution 122463 is not printed anymore, because it was already exploded before on level 1.
Skip Co-requisites | If you select this check box, Co-requisite dependencies are not printed.
Explode Co-requisites | You can only select this check box if you do not select the Skip Co-requisites check box. If you select this check box, all Co-requisite dependent solutions, which are found during the processing of the solutions in the given range, are also printed with their own tree. If you clear this check box, the Co-requisite dependencies are printed, but no separate tree is printed.
Skip Post-requisites | If you select this check box, Post-requisite dependencies are not printed.