Version Impact Analysis

This report is formatted as the Consolidation Workplace panel.

At the end of this report, a Legend of the Header Abbreviations and Version Difference Symbols is provided to assist you in reviewing the Version Impact Analysis. For each same-name member set, you can easily determine which versions are different and which are equal to the base code, as well as how difficult it would be to reconcile the versions. Let's analyze, member by member, the following panel:

                         VERSION IMPACT ANALYSIS

DIFFERENCE BASE MEMBER ACTION   COMPL DERV #1  DERV #2  DERV #3  LANGUAGE
@===       $TEST       =Execute None  $TEST    $TEST    $TEST    PL1
.@$.                   *Execute Low   ABC      ABC               JCL
@$$$       ASMBLBAS    *Execute High  ASMBLBAS ASMBLBAS ASMBLBAS BAL
@==.       CMNZAPR     =Execute None  CMNZAPR  CMNZAPR           COBOL
@$$=       COBOLBAS    *Execute Mid   COBOLBAS COBOLBAS COBOLBAS COBOL

LEGEND - Header Abbreviations and Versions Symbols
    DIFFERENCE - graphical summary of versions differences
     "@" - denotes the version used as a Base
     "." - denotes a missing version of a member
     "=" - denotes a version equal to the Base version
     "$" - denotes a version different from the Base
     "b" - denotes a banner appended to consolidated version
     " " - denotes a missing versions library
    ACTION - last action against the set of member versions
     *Execute - versions have been compared and merged
     *Reconcl - versions have been reconciled: Work In Suspense
     **Export - versions have been consolidated and exported
     "=" instead of "*" denotes equal versions

Member $TEST - From the Difference Impact summary @=== and the Degree of Complexity COMPL = None, all versions are present and equal. M+R has determined that the language is PL/I.
Member ABC - From the Difference Impact summary .@$. and the Degree of Complexity COMPL = Low, there are two versions of that member in the first and second derivative, and they differ slightly (low complexity). Note that the first derivative version assumes the role of a base because there is no member ABC in the base library. It is JCL.
Member ASMBLBAS - From the Difference Impact summary @$$$ and the Degree of Complexity COMPL = High, all versions are present and significantly different (high complexity). They are written in IBM Assembler (BAL).
Member CMNZAPR - From the Difference Impact summary @==. and the Degree of Complexity COMPL = None, there is no version of that member in the third derivative library and no difference between the present COBOL programs.
Member COBOLBAS - From the Difference Impact summary @$$= and the Degree of Complexity COMPL = Mid, all versions are present, the base and the third derivative versions are equal, and there are some differences between the COBOL base and the first and second derivatives so that their reconciliation will be of medium complexity.

Batch Execution Summary

The last part of the Batch Execution Report provides a summary, shown below, of the Version Impact Analysis performed by this run. The summary contains rich information about the differences between the member versions in the base and derivatives libraries and the complexity of their reconciliation.

                         M+R BATCH EXECUTION SUMMARY
                  R E C O N C I L I A T I O N COMPLEXITY      NUMBER
                -----ZERO ------LOW ---MEDIUM -----HIGH      OF SETS
    EXECUTED            2         1         1         1            5
    RECONCILED          0         0         0         0            0
    EXPORTED            0         0         0         0            0
    NOT EXECUTED                                                   1
      STOP 14:18:35   COND CODE 4

The sets of member versions are divided according to their degree of reconciliation complexity (None, Low, Medium, or High) and their current reconciliation status (Executed, Reconciled, Exported, or Not Executed).

In the preceding panel, 5 member sets have been compared and merged, of which 2 have zero complexity (that is, all versions are equal) and the rest have some Degree of Complexity. All 5 member sets have been executed during this run—see the 5 SER036I message lines in the "Member Sets Execution Messages." If there are executed member sets in the WIS library prior to this run, their status is included in the summary.

If there are reconciled/exported member sets in the WIS/export libraries prior to this run, their status is reported on the second and third line of the summary.

Note

A Reconciled member set is one that has been edited by the user but is not exported yet.

The not executed member set is the one that has an empty member—see the message SER046A line in the "Member Sets Execution Messages."

The Batch Execution job returns the following condition codes.

0 - successful completion
4 - member I/O error - e.g., an empty member
8 - data set I/O error (versions or WIS library)
16 - severe error