IBM Mainframe Forum

Don't you think it is probably related to the SORT, and therefore is removing duplicates from the output file? The manual will confirm.

I'm not sure I understand the question. The duplicates are removed after the JOIN processing and REFORMATing has taken place. Hence, in this case, based on the REFORMAT statement, only F2 records are being written out. Therefore, the duplicates from F2 are removed from the output. Does this answer your question? If not, please try to explain your question again.

Thank you.

Hi Alissa,

Please apologize me if i am wrong.

According to your below statement, the duplicates are removed after only the reformat fields are executed. If so we can give "SUM FIELDS=NONE".

It will do the same..!

I thought that using the "DUPKEYS FIELDS=NONE" statement will remove the duplicates in any of 2 files before matching.

I think you have little bit more now.

Thanks much..!

If you are going to contradict someone like Alissa, who has deep intimate knowledge of the product, you should at least provide references to the manual to support your statements, or sample input/output where you feel that this has occurred.

Hi BillyBoyo,

I am not saying Alissa is wrong!

I am asking my thought is correct or wrong to her?

If I am wrong anywhere in my statement, Please apologize me..!

I don't have Syncsort documentation. You do, I assume.

I think you'll discover that SUM FIELDS=NONE and DUPKEYS FIELDS=NONE would be the same, operate in the same way. I suspect DUPKEYS has some additional options which are not available on the SUM.

Look in your manual for references to the order in which things are done. If you have a joinkeys operation which is followed by a SORT then control statements after the SORT will refer to the SORT not something earlier.

In this case, the DUPKEYS and SUM statements are equivalent. you can use either one.

Thanks Alissa for your response..!