Using the KEY= and UNIQUE options on a SET or MODIFY statement does
not cause the KEY= search to begin at the top of the index for an SPDE
data set.  Naming a data set accessed with the SPDE engine as the
master data set on a MODIFY statement with the KEY= and UNIQUE options
may produce the following message in the SAS log:

  ERROR: No matching observation was found in MASTER data set.

This error occurs if there are consecutive duplicates of the key value
in the transaction data set and a single value of the key in the
master data set.  The master data set is only updated with the first
occurrence of the key from the transaction data set.

If there are consecutive duplicates in both the transaction and the
master data sets, the updated master data set incorrectly contain the
duplicates from the transaction data set.

A fix for SAS 9.1.3 (9.1 TS1M3) for this issue is available at:

http://www.sas.com/techsup/download/hotfix/e9_sbcs_prod_list.html#011110

For customers running SAS with Asian Language Support (DBCS), this
fix should be downloaded from:

http://www.sas.com/techsup/download/hotfix/e9_dbcs_prod_list.html#011110

Operating System and Release Information

A fix for SAS 9.1.3 (9.1 TS1M3) for this issue is available at:

A fix for SAS 9.1.3 (9.1 TS1M3) with Asian Language Support (DBCS) for this issue is available at :