Author: Bill Woodger
Subject: Reply to: Joinkeys with duplicated keys
Posted: Fri Sep 23, 2016 12:12 pm (GMT 5.5)
mistah kurtz,
If you use 3,4 as the keys, there are no duplicate keys, so there is evidence for OP being correct with 4,3 (their problem is with duplicate keys).
juares castro,
You are SORTing both files (each JOINKEYS SORTs its input unless told not to). You sample data doesn't show any reason for this (data is in key order). Consider using SORTED on the JOINKEYS statement(s).
It looks as though you just want to "side-by-side" the data. Both your input files are the same. Best way to do this is to generate a sequence number, appended to each record (for fixed-length records, prepended to the data for variable-length records) and using the sequence number as the key.
Subject: Reply to: Joinkeys with duplicated keys
Posted: Fri Sep 23, 2016 12:12 pm (GMT 5.5)
mistah kurtz,
If you use 3,4 as the keys, there are no duplicate keys, so there is evidence for OP being correct with 4,3 (their problem is with duplicate keys).
juares castro,
You are SORTing both files (each JOINKEYS SORTs its input unless told not to). You sample data doesn't show any reason for this (data is in key order). Consider using SORTED on the JOINKEYS statement(s).
It looks as though you just want to "side-by-side" the data. Both your input files are the same. Best way to do this is to generate a sequence number, appended to each record (for fixed-length records, prepended to the data for variable-length records) and using the sequence number as the key.