Index records with duplicate keys

IMS Index Builder does not acknowledge key uniqueness until all records of a target index are sorted and until index load is initiated. Before loading a record, IMS Index Builder checks for key duplication.

If the index is defined with unique keys and one or more duplicate keys are encountered, the completion code for the index is A30 and the completion messages show the count of the loaded records and the count of the records that are not loaded due to key duplication. The records with duplicate keys are stored in the stripes with LLQ "DUPLKEYS". If DBRC is active, a DBRC NOTIFY REORG is not done.

The DUPLKEYS stripe can be used for control purposes and subsequent record processing, and will be retained after the job ends.