Comparing two lists/ResDescs

The side-by-side comparison of two lists or ResDescs consists of several "reports", each offering a different type of comparison.

Table 1. Side-by-side comparison reports of two lists/ResDescs
Comparison report Report shows… Use this report to identify… Checksum required?
Processing order All groups/ResGroups in processing order Groups/ResGroups that appear in one of the lists/ResDescs, but are missing from the other; groups that appear in both lists, but are in a different position in the processing order.

Processing order is significant only for lists, not ResDescs. For ResDescs, ResGroups are always listed in alphabetic order.

 
Name differences Groups/ResGroups with different names, but same checksums Groups/ResGroups that contain similar or identical resource definitions, depending on the type of checksum that you have selected. Yes
Checksum differences Groups/ResGroups with different checksums, but same names Groups/ResGroups that have the same name, but contain different resource definitions.

This report is relevant only when comparing lists/ResDescs from different CICS® configurations. In a single CICS configuration, groups/ResGroups with the same name will always have the same checksum, because they are the same group/ResGroup.

Yes
Checksum values All groups/ResGroups in alphabetic order, with checksums Any type of difference. Yes
All details All groups/ResGroups in processing order, with checksums Yes

All but one of the reports requires you to activate checksums, either by entering CHECKSUM type on the command line, or by selecting a checksum type from the Checksum action bar choice.

The checksum type determines which resource definition attributes are used to calculate the checksums on which the comparison reports are based. The checksum types available for side-by-side comparisons of lists/ResDescs are:

FULL
All attributes.
LIST
Your choice of attributes for each resource type.

You need to have defined the LIST checksums previously: when displaying a list panel of resource definitions, you specify a resource type in the filter field, and then enter CHECKSUM LIST. A panel appears where you can select which attributes of that resource type you want to include in LIST checksums. This panel also shows which attributes are included in the predefined PARTIAL checksums.

NAME
Resource definition name and type only.
PARTIAL
A selection of attributes predefined by CICS Configuration Manager.

The different checksum types enable you to customize the level of comparison of the two lists/ResDescs.

To step through the reports, press the NextPage key (F11).

The reports that require checksums contain the following "anomaly" flag columns:

N
Indicates groups/ResGroups that have the same checksums, but different names. The name differences report shows only these groups/ResGroups.
O
Indicates groups/ResGroups that appear in a different order in the two lists/ResDescs, or appear in one but are missing from the other.
C
Indicates groups/ResGroups that have the same names, but different checksums. This only happens when comparing lists/ResDescs from different CICS configurations. The checksum difference report shows only these groups/ResGroups.

The N and C anomaly flags are mutually exclusive: groups/ResGroups that appear on the name differences report do not appear on the checksum differences report.


Information Information

Feedback


Timestamp icon Last updated: Friday, 8 February 2013


http://pic.dhe.ibm.com/infocenter/cicsts/v5r1/topic//ccv-ispf-compare-lists.htm