• Print |
• E-mail  |
• Bookmark

Specifying the UNIQUE option on a SET statement causes the KEY=
search to always begin at the "top" of the index.  Starting in
Version 8 TSLEVEL D1, if there are consecutive duplicate KEY= values
in the transaction data set and unique KEY= values in the master data
set, SAS incorrectly matches only the first occurrence.

To circumvent this problem, specify the LIBNAME option
REREAD_EXPOSURE=YES and the data set option CNTLLEV=REC.  Note that
using REREAD_EXPOSURE=YES may cause data integrity issues.  With
REREAD_EXPOSURE=YES, the SAS/ACCESS engine behaves like a random
access engine when rereading a row, so there is no guarantee that
the same row will be returned each time.  Thus there is the
potential for data integrity exposures within the scope of your SAS
session.

This problem is corrected in Release 8.1 TS1M0.

Operating System and Release Information