SuperC compare of load module data might show unexpected differences. This is because SuperC compares all the data in the load module as it is found on DASD, and does not attempt to decode which portions are executable, and which might contain uninitialized storage.

The complex data format on DASD is dependent on the load module data set block size, and defined storage definitions which are controlled by the linkage editor. The size stored by the linkage editor in the PDS directory may differ from the DASD data byte count reported by SuperC and Browse depending on the characteristics of the load module.

If load modules are exact copies of each other, SuperC should find no differences. If load modules have been link-edited from the same object but with different block sizes, SuperC will probably report they are different.

Because of the relative DASD addresses (TTRs) in load modules, the recommended procedure for comparing load modules which have not been reblocked is to use the AMBLIST utility with LISTLOAD OUTPUT=MODLIST against both load modules, then use SuperC to compare the two AMBLIST outputs. There is no easy way to compare load modules with different internal record sizes such as occurs when COPYMOD or LINKEDIT processes them.