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

A data set accessed via the Release 8.1 REMOTE engine may be corrupted.
(REMOTE engine access occurs with either a multi-user SAS/SHARE server
or SAS/CONNECT's Remote Library Services (RLS).  Note that the release
of SAS being run by the SAS/SHARE or RLS single-user server does not
affect this problem.)  One or more observations in the data set may be
overwritten with values from other observations.  No errors or warnings
are produced when the corruption occurs, and the number of observations
written by the step is correct.

The corruption may cause subsequent steps which process the data set to
fail.  Reported symptoms include:

   ERROR: BY variables are not properly sorted on data set
          <libref.member>.

This message sets the automatic variable _ERROR_ to 1, which results in
the contents of the PDV being written to the SAS Log.  If the data set
is being processed sequentially, the _N_ variable's value represents the
number of the observation which was overlaid.

Other symptoms include receiving the following message from a PROC SORT
step which specifies the NODUP or NODUPKEY option when the original data
set had already had duplicate observations removed:

   NOTE: <n> observations with duplicate key values were deleted.


A Technical Support hot fix for Release 8.1 TSLEVEL TS1M0 for this issue
is available at:

http://www.sas.com/techsup/download/hotfix/81_sbcs_prod_list.html#003461

This problem is fixed in Release 8.2.

NOTE:  This is fixed in all shipments of Release 8.1 on MVS shipped
       after 11OCT2000.  This fix would also be included in shipments of
       SAS/SHARE or SAS/CONNECT to be added to a current installation of
       Release 8.1.

Operating System and Release Information

A fix for Release 8.1 (TS1M0) for this issue is available at: