Previous Topic: Running Component Change Processing in BatchNext Topic: Public Change to Access Path

Managing Model Objects › Impact Analysis › Component Change Processing Scenario

Component Change Processing Scenario

  1. Suppose we have the scenario shown in the following diagram. This example shows the details of component change processing that take place as a result of both a private and a public change to an access path.

  2. The arrows indicate the usage sequence for the functions that use the access path. The numbers in the small boxes indicate the usage level of each object relative to the access path at level 0.

    The following section shows the difference between a private and public change to Access Path.

Private Change to Access Path

Suppose you intend to change the source member name for Access Path using the Edit Access Path Details panel. CA 2E considers this to be a private change to Access Path. As a result, CA 2E:

  1. Expands all usages of Access Path until the first external function on any given sequence of usages is encountered. These are shown with darker borders and the word GEN.

    Private Change to Access Path

    Note: That all usage levels beyond the first external function are ignored; in this case, PMTRCD, EXCEXTFUN 1, and EXCINTFUN 3 are not included in the expansion.

  2. Sets the Required Action Indicator for the affected external functions to GEN in the All Objects lists.