Where Used Tree and Result Example
The following example illustrates the contents of the Tree and Result datasets, for a simple Where Used scenario. Consider the case where Tables T1 and T2 are starting objects that are used by Function F1. Function F1 is used by Programs P1, P2 and P3.
Tree Dataset
The Tree dataset lists pairs of objects in the tree of results found by the Where Used action. The left side of the pair is an object, the right side of the pair is an object that uses the object on the right side of the pair directly. In the above example, the Tree dataset would have the following pairs:
| Child | Parent (distinct list of pairs) |
|---|---|
| TABL T1 | FUNC F1 |
| FUNC F1 | PROG P1 |
| FUNC F1 | PROG P2 |
| FUNC F1 | PROG P3 |
| TABL T2 | FUNC F1 |
Result Dataset
The Result dataset is an expansion of the results in the Tree dataset, and contains a list of object pairs. The objects on the left side of each pair are starting objects. The objects on the right side are objects that can be found by following the links between objects, beginning with the starting object on the left side of the pair. In the above example, the Result dataset would have the following pairs:
| Child (starting objects) | Parent (all direct and indirect parents) |
|---|---|
| TABL T1 | FUNC F1 |
| TABL T1 | PROG P1 |
| TABL T1 | PROG P2 |
| TABL T1 | PROG P3 |
| TABL T2 | FUNC F1 |
| TABL T2 | PROG P1 |
| TABL T2 | PROG P2 |
| TABL T2 | PROG P3 |
Typically, the Result dataset will be much larger than the Tree dataset, sometimes an order of magnitude larger. In the Object Change Impact Analysis package workflow, the Where Used action’s Result dataset is not generated in order to save time and storage space.