Component Impact Analysis

The Impact Analysis function performs a bottom-up query to find all higher-level components that reference or invoke a selected, subordinate component. For example, a reusable subroutine might be called by multiple higher-level programs, and you might want to discover which programs those are before making any changes to the subroutine.

The subordinate component selected for impact analysis may be might be a copybook, subroutine, JCL procedure, or physical object name for a data set, program, or JCL procedure referenced in a name-to-symbol mapping. The higher-level components returned by an impact analysis query may be like-source, like-load, like-copybook, or members of a JCL procedure library.

The dependency relationship of interest is selectable at the time the Impact Analysis function is requested. Only one dependency type may be queried at a time.

Invoking and Viewing the Impact Analysis Report

Invoking the Impact Analysis Report

The Impact Analysis report is invoked from the following menus in the Serena Explorer navigation view of the Serena perspective:

• Baseline component contextual menu — Expand the z/OS Applications node for the relevant ZMF server. Navigate to the desired application node and expand it, then expand the Baseline node and the node for the relevant baseline library, then right-click on the component whose build of materials you wish to view. When the contextual menu displays, select Impact Analysis. See ZMF Operations on Baseline Library Components.

• Package component contextual menu — Expand the z/OS Applications node for the relevant ZMF server. Navigate to the desired application node and expand it, then expand the Packages node, then the node for the relevant change package and staging library, then right-click on the component whose build of materials you wish to view. When the contextual menu displays, select Impact Analysis. See ZMF Operations on Package Components.

• Promotion component contextual menu — Expand the z/OS Applications node for the relevant ZMF server. Navigate to the desired application node and expand it, then expand the Promotion node, then the node for the relevant promotion site, promotion level, and library type, then right-click on the component whose build of materials you wish to view. When the contextual menu displays, select Impact Analysis. See Promotion Component Contextual Menu.

Viewing the Impact Analysis Report

The requested impact analysis report displays in a ZMF table view under the Impact Analysis tab in the lower right pane of the perspective.

Impact Analysis Wizard Step-by-Step

To request an impact analysis report, perform the following steps.

1. Select the Impact Analysis option from the subordinate component’s contextual menu.

2. The Component Impact Analysis parameters window prompts you to specify a description of the subordinate components. It also requests a dependency relationship and any results filters you might want to apply.

   ![../images/comp-impact.png]

   1. Under the heading Subordinate Component Information, specify the Name, Library Type, and Application of the subordinate component whose impact is to be analyzed. Observe the rules in the table for each subordinate component type.

      Type of Component	Field Entries
      Copybook	Name of referenced copybook, or a pattern with at least one literal character and an asterisk (*) wildcard.
      	Library Type must be CPY or a like-copybook library.
      	Application where the subordinate component is used. May be a pattern or a standalone asterisk (*) wildcard for cross-application components.
      Data Set	Name of referenced data set, or a pattern with at least one literal character and an asterisk wildcard. Data set names or patterns may match fully qualified physical data set names, symbolic data set names such as &SYMBOLIC, or Generation Data Group (GDG) names without a relative generation number. Temporary files such as &&TEMP are not supported.
      	Library Type must be an asterisk wildcard.
      	Application where the subordinate component is used. May be a pattern or a standalone asterisk wildcard for cross-application components.
      JCL Procedure	Name of a JCL procedure referenced by other JCL components in an EXEC statement, or a pattern with at least one literal character and an asterisk wildcard.
      	Library Type must be an asterisk wildcard.
      	Application where the subordinate component is used. May be a pattern or a standalone asterisk wildcard for cross-application components.
      Subroutine	Name of statically linked subprogram module, or a pattern with at least one literal character and an asterisk wildcard.
      	Library Type must be LOD or a like-load library.
      	Application where the subordinate component is used. May be a pattern or a standalone asterisk wildcard for cross-application components.
      Program	Name of a program referenced in the PGM= parameter of a JCL EXEC statement, or a pattern with at least one literal character and an asterisk wildcard.
      	Library Type must be an asterisk wildcard.
      	Application where the subordinate component is used. May be a pattern or a standalone asterisk wildcard for cross-application components.

   2. In the Relationship field, select from the pull-down list the dependency relationship for which an impact analysis report is desired.

      Option	Description
      Copybook	Requests all copybooks referenced by the higher-level component. Returns SRC, like-source, CPY, and like-copybook objects only; other library types are ignored.
      DSN Name/Symbol	Requests all data set name-to-symbol mappings used by the higher-level component (that is, any subordinate JCL components that include a DSN= or DSNAME= parameter in a DD statement). Returns JCL, like-JCL, PRC, and like-procedure objects only.
      JCL Procedure	Requests all JCL procedures invoked by the higher-level component (that is, any subordinate JCL components that include an EXEC statement). Returns JCL, like-JCL, PRC, and like-procedure objects only.
      PGM Name/Symbol	Requests all program name-to-symbol mappings used by the higher-level component (that is, any subordinate JCL components that contain a PGM=parameter in an EXEC statement). Returns JCL, like-JCL, PRC, and like-procedure objects only.
      Subroutine	Requests all subroutines called by the higher-level component (that is, all subordinate load modules that reference a statically link-edited subprogram). Returns LOD and like-load objects only.

   3. Under the heading Superior Component Information (Filtering), retain the default asterisk (*) wildcards to see all returned results, or enter a pattern with wildcards to filter results by component Name, Library Type, or Application.

   4. Click the Case Sensitive Query checkbox if the search for component dependencies should respect case in component, library, and application names. This option is frequently desirable with z/OS USS zFS components.

   5. Click OK to submit the query.

3. A list of higher-level components matching your search criteria are returned under the Impact Analysis tab in the bottom right pane of the perspective. The search parameters are shown in the information bar below the tab name. For example: