Report summary

This is a common header section that appears in all deployment analysis reports.

Purpose

Contains statistics for the entire report. These statistics represent values before filtering. For information on the number of resource definitions suppressed from the report by filtering, see Filtering summary.

Example

                         CICS Deployment Analysis Report
                            Cold Start Compare Report
                                 Report Summary

 ReportSet 1  ReportSet 2
    Count        Count     Code Description
 -----------  -----------  ---- ------------------------------------------------------------
       72           72          Total matched definitions with no exceptions
     2961           29          Total mismatched definitions
        0          132          Total definitions excluded from analysis

Contents

This section contains the following information:

Total matched definitions with no exceptions
(Relevant only to reports that compare two report sets.) The number of resource definitions in this report set that exactly matched a resource definition in the other report set. Although the report shows a separate value for each report set, these two values will always be identical.
Total mismatched definitions
(Relevant only to reports that compare two report sets.) The number of resource definitions that did not exactly match a resource definition in the other report set. This is the sum of the following two values:
  • The number of resource definitions in the mismatched section
  • The number of resource definitions in the matched definitions (with exceptions) section

That is, this value lists the number of resource definitions that do not match, even if the only difference is their "enablement state" (as shown in the "Ena" column in later sections: for example, one resource definition is enabled, the other is disabled).

In the previous example listing, notice that the number of mismatched definitions for report set 1 is much higher than for report set 2. In this example, report set 1 represents runtime resource definitions and report set 2 represents candidate resource definitions. It is typical for a set of runtime resource definitions to contain more resource definitions than the set of candidate resource definitions with which they are being compared, for various reasons:

  • The candidate resource definitions might have been collected from a subset of the lists that would normally be used at startup.
  • The runtime resource definitions include dynamically generated resource definitions that do not exist in the set of candidate resource definitions.
Total inventory report records
(Relevant only to reports that list one report set; not shown in the previous example.) The number of resource definitions collected (the total of the Records values in the Data Sources section), minus the number of resource definitions excluded (as described in the following item).
Total definitions excluded from analysis
(Relevant only to report sets of candidate resource definitions.) The number of candidate resource definitions that CICSĀ® Configuration Manager excluded from the report. This value is a count of the following resource definitions, depending on the report type:

The following candidate resource definitions have no direct runtime equivalent, so CICS Configuration Manager excludes them from cold start compare reports:

LSRPOOL, TYPETERM, and SESSION resource definitions
CICS Configuration Manager excludes these types of candidate resource definition from cold start compare reports because there are no directly equivalent types of runtime resource definition. For instance, LSRPOOL resource definitions can exist in a CSD file, but there is no directly equivalent type of runtime resource definition in an active CICS region.

In this case, "excluded" means that the report does not attempt to match these types of candidate resource definition with runtime resource definitions. However, the report continues to use these types of candidate resource definition for referential integrity. For example, if a TERMINAL candidate resource definition refers to a TYPETERM resource definition that would not yet have been installed, the Referential Integrity Verification section of the report lists the TERMINAL candidate resource definition.

Unused duplicates
CICS Configuration Manager excludes unused duplicate candidate resource definitions from all reports because they will never be "deployed" (installed). For example, suppose you request a candidates report for a set of resource definitions that contains three duplicates (resource definitions with the same name and type). The resource definitions section of the report lists only one of the duplicates: the one that CICS would install, according to its rules of precedence. The resource definition section excludes the other two duplicates. However, the duplicate definitions verification section of the report lists all three duplicates, indicating why two of them were excluded. The "Total definitions excluded from analysis" value for this candidates report would be 2. Similarly, suppose you request a cold start compare report using this same set of candidate resource definitions. The two rejected duplicates appear only in the duplicate definitions verification section of the report.

For report sets of runtime resource definitions, this value is always 0 ("exclude" processing does not apply to runtime resource definitions).


Information Information

Feedback


Timestamp icon Last updated: Friday, 1 November 2013


http://pic.dhe.ibm.com/infocenter/cicsts/v5r1/topic//ccv-batch-da-report-section-summary.htm