Joined: 07 Dec 2007 Posts: 2205 Location: San Jose
Elixir,
As dick scherrer pointed out, Comparex utility is not related to DFSORT. However here is an equivalent DFSORT JCL which will give you the desired results based on your comparex control cards.
With the above, if you have a records on INA which are "surplus" they are ignored. All records on INB match to a record on INA. If you look at the Sysout, you'll see record counts. Are they they same?
If your 1,35 makes a unique key, and the data is in order, you wouldn't need the default Sort that is happening.
Joined: 07 Dec 2007 Posts: 2205 Location: San Jose
Elixir wrote:
Thanks very much skolusu.
I ran using the following control card and the sortout is empty.
Does it mean that all the fields in both the files except column 36 and 37 are equal.
NO. I gave DFSORT equivalent control cards for your comparex control cards. If you got an empty sortout, it doesn't mean that both files are equal, it just means that INB file does not have any extra records that don't match with records in INA file. If you had ran the sample JCL I gave you would have noticed that it did not write the mismatched records from INA file.
Elixir wrote:
the record length of my files being compared are 738
I got sortout empty
In your initial post you mentioned that the key is only 57 bytes, now how did it dramatically increase to 738 bytes? Is this a entirely a new requirement ? If you want to compare the full 738 bytes why are your comparex control cards only checking for 57 bytes as key?
