ABCs of z/OS System Programming Volume 3 - IBM Redbooks

Note: Load module partitioned data sets that reside on different types of devices should
not be compared. Under most circumstances, the data sets will not compare as equal.
A partitioned data set or partitioned data set extended can be compared only if all names in
one or both directories have counterpart entries in the other directory. The comparison is
made on members identified by these entries and corresponding user data.
Recommendation: Use the SuperC utility instead of IEBCOMPR. SuperC is part of
ISPF/PDF and the High Level Assembler Toolkit Feature. SuperC can be processed in the
foreground as well as in batch, and its report is more useful.
Examples of comparing data sets
As mentioned, partitioned data sets or PDSEs can be compared only if all the names in one
or both of the directories have counterpart entries in the other directory. The comparison is
made on members that are identified by these entries and corresponding user data.
You can run this sample JCL to compare two cataloged, partitioned organized (PO) data sets:
//DISKDISK JOB ...
// EXEC PGM=IEBCOMPR
//SYSPRINT DD SYSOUT=A
//SYSUT1 DD DSN=PDSE1,DISP=SHR
//SYSUT2 DD DSN=PDSE2,DISP=SHR
//SYSIN DD *
COMPARE TYPORG=PO
/*
Figure 4-3 IEBCOMPR sample
Figure 4-2 on page 110 shows several examples of the directories of two partitioned data
sets.
In Example 1, Directory 2 contains corresponding entries for all the names in Directory 1;
therefore, the data sets can be compared.
In Example 2, each directory contains a name that has no corresponding entry in the other
directory; therefore, the data sets cannot be compared, and the job step will be ended.
Chapter 4. Storage management software 111