Providing software solutions since 1976

• Log in
• Create profile
• Welcome
  [Log out]
• Edit profile

• Print  |
• Feedback  |
• Share

  • E-mail

  
  
  

  E-mail This Page

  Your Name:*
  Your E-mail:*
  Recipient E-mail:*
  Send a copy to me
  Personal Message:
  
  

  * indicates a required field

In Release 8.1 and above of the SAS System, using the DROP= (or KEEP=)
data set option along with NODUPKEY once a data set has already been
sorted may not sort the data set again. For example:

   PROC SORT DATA=TEST OUT=TEST1 (DROP=KEY4) NODUPKEY;
     BY KEY1 KEY2 KEY3 DESCENDING KEY4;
   RUN;
   PROC SORT DATA=TEST1 OUT=TEST2 (DROP=KEY3) NODUPKEY;
     BY KEY1 KEY2 KEY3;
   RUN;

generates the following NOTE in the SAS Log:

   NOTE: Input data set is already sorted; it has been copied to the
         output data set

To circumvent the problem, specify the FORCE option.  For example:

   PROC SORT DATA=TEST OUT=TEST1 (DROP=KEY4) NODUPKEY;
     BY KEY1 KEY2 KEY3 DESCENDING KEY4;
   RUN;
   PROC SORT DATA=TEST1 OUT=TEST2 (DROP=KEY3) NODUPKEY FORCE;
     BY KEY1 KEY2 KEY3;
   RUN;


A Technical Support hot fix for Release 8.2 TSLEVEL TS2M0 for this
issue is available at:

http://www.sas.com/techsup/download/hotfix/82_sbcs_prod_list.html#005030

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

http://www.sas.com/techsup/download/hotfix/82_dbcs_prod_list.html#005030

Operating System and Release Information

A fix for Release 8.2 (TS2M0) for this issue is available at:

A fix for Release 8.2 (TS2M0) with Asian Language Support (DBCS) for this issue is available at: