The alternate index being built was defined with the UNIQUEKEY attribute. That is, the alternate key exists on only one base cluster record. However, multiple occurrences of the same alternate key have been encountered. The system writes this message for each multiple occurrence. The message gives the alternate key first, up to a maximum of the first ten bytes, expressed in hexadecimal.
If the base cluster is a key-sequenced data set, the specified record is the prime key (up to a maximum of the first ten bytes) expressed in hexadecimal.
If the base cluster is an entry-sequenced data set, the specified record is the prime relative block address (RBA) in decimal.
An alternate index record is created containing the alternate key and only the first prime key or RBA listed. All subsequent prime keys/RBAs will not be reflected in the alternate index record.
If the error recurs and the program is not in error, search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM® Support Center. Provide the JCL and the SYSOUT output for the job.
If the UNIQUEKEY attribute was correctly specified, then the base cluster is in error. Correct it through a calling program
Then rebuild the alternate index using the BLDINDEX Command.
DFSMSdfp
IDCBI01