Question & Answer
Question
I used ISPF option 3.3 (Move/Copy Utility) to copy a member of a load library into a PDS load library, and into a PDSE load library. Then I used ISPF option 3.13 with the Compare Type of "byte" to compare the existing member to the new members in the new load libraries. The new member in the PDS differs from the same member in the PDSE.
Answer
Both the tutorial and ISPF User's Guide state the following under "Comapring Load Modules".
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.
If you use Browse and just look at the output you can see the load modules are not formatted the same way when looking at a PDSE vs the PDS of the same load module. Functionally they would work the same way, but they are stored differently so SUPERC will not show them as being the same.
Was this topic helpful?
Document Information
Modified date:
16 November 2016
UID
dwa1321024