Configuring the scope of impact analysis
When the impact analysis engine examines CI relationships to calculate impacts, it searches a specified number of levels away from the CI where it began the search. The engine finds impacts by examining related CIs for impacts, then examining CIs that are related to those CIs, and so on. A system property determines how many levels of related CIs the engine will examine to calculate impacts.
About this task
There are two system properties that you can use to limit
the number of targets that the impact analysis engine examines:
To specify a limit for impact analysis, perform the following
steps:- pmchgiarule.maxdepth - This system property specifies the number of levels of related CIs the engine examines to calculate impacts. The default maximum depth is 10.
- pmchg.ci.impacts.maxrecords - This property specifies the maximum number of CI targets the Change Impact Analysis will process. It is available to prevent accidental use of Impact Analysis on Changes with large numbers of target CIs because the calculations take a long time and the results are not useful. Impact analysis is not useful for Changes on large numbers of CIs because so many outages are identified that it is not reasonable to use them for scheduling. In those cases, a best practice is to schedule like a Release; that is, schedule for a time when a large scale outage is acceptable. If you set this property to zero, all the target CIs specified on the implementation tasks of the Change are always analyzed, no matter how many are specified.
Procedure
- To open the System Properties application, click .
- Click Filter, type pmchg in the Property Name field, and press Enter to display a list of system properties that are defined for Change Management.
- Select the system property to display information about the property.
- Specify a different value in the Global Value field.
- Click
. - Click
to refresh the system properties.