AX – Add Impacts

This section provides information about AX-Add Impacts.

AX – Definition

The AX (Add Impacts from Cross Reference) option is used to create and display a list of components that are related to the Target Component.

Type AX next to a module, as shown in the following figure, to see its change impacts.

Using the AX Command

ASSIGNMENT         PLAY000022: CHANGE CYCLE EXAMPLE 2       Row     1 of     9
Command ===>                                                  Scroll ===> CSR
                                                                     More -->
+-----------------------------------------------------------------------------+
| Select(/) Add Approve Close Join Reset Show/Hide Work ++/--                 |
+-----------------------------------------------------------------------------+
    Type     Name     Lev Op A User     Date MM DD Time Status
    ________ ________ ____ __ _ ________ __________ _____ ____________________
__   CLST     TREXX03 STG1 P    USER003 2022-05-16 12:19
__   COB      TPROG01 DEV1 G    USER002 2022-05-16 10:14
__   COB      TPROG02 DEV1 G    USER001 2022-05-16 10:11
__   COB      TSUBR01 STG1 G    USER002 2022-05-16 10:14
__   COB      TSUBR02 DEV1 G    USER003 2022-05-16 10:19
__   COPY     TCPYA01 STG1 G    USER002 2022-05-16 10:14
__   COPY     TCPYA02 DEV1 G    USER002 2022-05-16 10:14
AX   COPY     TCPYB01 STG1 P    USER002 2022-05-16 10:14
__   COPY     TCPYB02 DEV1 P    USER002 2022-05-16 10:14
------------------------------- Bottom of List -------------------------------

Calling and Called Components

The generated list includes all components that call the Target Component, together with all components called by the Target Component. The list can be used for impact analysis and to help build a comprehensive Assignment of tasks to represent the impacted components.

Using AX to “Drill Down”

Additional AX commands can be entered when the Component Impacts screen is displayed to browse impacted components, list all versions of impacted components, and add tasks for the impacted components to the current Assignment, as required.

Component Impacts Screen

The Target Component is listed at the top of the Component Impacts screen, and repeated in the scrollable area if references are found as Seq 0.

Components that reference the Target Component are displayed above it as Seq +n, and components that are referenced by the Target Component are displayed below it as Seq -n. The Cat field identifies the impact Category (whether it is a program or a job, for example).

The Impact field may further qualify the type of impact, for example DCLGEN or CICSLINK. The Status field may further qualify references that are incomplete or not applicable and advise if the Component has already been added to the current Assignment.

Component Impacts Screen

22.                PLAY000022 - COMPONENT IMPACTS           Row     1 of     6
Command ===>                                                  Scroll ===> CSR
                                                                     More -->
  Type: COB_____ Name: TCPYB01_ Appl: PLAY____ SubAppl: PLAY____
  Usage: _ Seq Limit: 30 Action: _

   Seq      Type Name     Lvl Cat Impact   Status        Assignment Appl
   ________ ____ ________ ____ ____ ________ _____________ __________ ________
  +++3     JOB TJOB01   STG1 JOB                         PLAY000022 PLAY
  ++2      COB TPROG01 STG1 PGM                         PLAY000022 PLAY
  +1       COB TSUBR01 STG1 PGM                         PLAY000022 PLAY
  ++2      JOB TJOB01   STG1 JOB                         PLAY000022 PLAY
  +1       COB TPROG01 STG1 PGM                         PLAY000022 PLAY
  0        COPY TCPYB01 STG1 .... ........ ............. PLAY000022 PLAY
------------------------------- Bottom of List -------------------------------

Component Impacts List Operations

Commands can be entered to the left of the related impact. Valid line commands are:

A—Add the component to the Task List.
AX—Add impacts for a referenced or impacted component.
B—Browse impacted component.
V—Version list. Show all active versions of the impacted component.

Loading and Updating Component Impacts

Component Impacts are loaded into the Code Pipeline Repository when components are promoted to the first controlled level above the update level. In other words, the component is parsed on the first P (Promote).

In the Promote process, the source code is parsed using language-specific parsers to determine the various impacts and relationships. Code Pipeline provides parsers for various languages, and these are automatically invoked if the Component Reference capability has been enabled for the designated Code Pipeline applications and member types.

Code Pipeline Administrators can also run batch jobs to populate the Repository for designated Applications and Levels.