Join Paired Problem



Support for NetApp SyncSort for z/OS, Visual SyncSort, SYNCINIT, SYNCLIST and SYNCTOOL

Re: Join Paired Problem

Postby BillyBoyo » Thu Feb 23, 2012 7:01 pm

Don't you think it is probably related to the SORT, and therefore is removing duplicates from the output file? The manual will confirm.
BillyBoyo
Global moderator
 
Posts: 3804
Joined: Tue Jan 25, 2011 12:02 am
Has thanked: 22 times
Been thanked: 264 times

Re: Re: Join Paired Problem

 

Re: Join Paired Problem

Postby Alissa Margulies » Thu Feb 23, 2012 8:16 pm

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.
Alissa Margulies
Syncsort Mainframe Product Services
201-930-8260
zos_tech@syncsort.com
Alissa Margulies
Global moderator
 
Posts: 369
Joined: Tue Feb 26, 2008 11:15 pm
Location: USA
Has thanked: 1 time
Been thanked: 1 time

Re: Join Paired Problem

Postby pjagathis » Fri Feb 24, 2012 12:04 pm

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..!
Thanks and Regards,
Jagathis P
pjagathis
 
Posts: 67
Joined: Wed May 04, 2011 5:04 pm
Location: Chennai
Has thanked: 0 time
Been thanked: 0 time

Re: Join Paired Problem

Postby BillyBoyo » Fri Feb 24, 2012 1:31 pm

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.
BillyBoyo
Global moderator
 
Posts: 3804
Joined: Tue Jan 25, 2011 12:02 am
Has thanked: 22 times
Been thanked: 264 times

Re: Join Paired Problem

Postby pjagathis » Fri Feb 24, 2012 5:06 pm

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..!
Thanks and Regards,
Jagathis P
pjagathis
 
Posts: 67
Joined: Wed May 04, 2011 5:04 pm
Location: Chennai
Has thanked: 0 time
Been thanked: 0 time

Re: Join Paired Problem

Postby BillyBoyo » Fri Feb 24, 2012 6:16 pm

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.
BillyBoyo
Global moderator
 
Posts: 3804
Joined: Tue Jan 25, 2011 12:02 am
Has thanked: 22 times
Been thanked: 264 times

Re: Join Paired Problem

Postby Alissa Margulies » Fri Feb 24, 2012 9:48 pm

In this case, the DUPKEYS and SUM statements are equivalent. you can use either one.
Alissa Margulies
Syncsort Mainframe Product Services
201-930-8260
zos_tech@syncsort.com
Alissa Margulies
Global moderator
 
Posts: 369
Joined: Tue Feb 26, 2008 11:15 pm
Location: USA
Has thanked: 1 time
Been thanked: 1 time

Re: Join Paired Problem

Postby pjagathis » Mon Feb 27, 2012 4:58 pm

Thanks Alissa for your response..!
Thanks and Regards,
Jagathis P
pjagathis
 
Posts: 67
Joined: Wed May 04, 2011 5:04 pm
Location: Chennai
Has thanked: 0 time
Been thanked: 0 time

Previous

Return to Syncsort/Synctool

 


  • Related topics
    Replies
    Views
    Last post