SUPPORT / SAMPLES & SAS NOTES
 

Support

Usage Note 15379: Cross-Environment Data Access (CEDA) utilization message

DetailsCodeAboutRate It

Beginning in SAS® 9.1.3 Service Pack 3, the following message is produced when a data set is accessed with the Cross-Environment Data Access (CEDA) functionality of the BASE engine and the system option NOTES is set:

  NOTE: Data file libref.member.DATA is in a format native to another host or the file encoding does not match the
        session encoding. Cross Environment Data Access will be used, which may require additional CPU resources
        and reduce performance.

Before you can remove this note, you must identify why CEDA was triggered. This information is obtained by the CONTENTS procedure where you can examine the fields entitled DATA REPRESENTATION and ENCODING. The Full Code tab shows how to place information in the log file that will report if the data representation is native or foreign. The remainder of this note provides code to convert the data representation. See Usage Note 15597 to convert encoding. 

Since the data set is native to the operating environment in which it was created, one way to create a native data set is to use the DATA/SET statements. Another method is to use the COPY procedure with the NOCLONE option. Example code follows. When you first run the code to create a native file from the foreign one, the CEDA note will be issued because it is the underlying technology used to convert the file. Further processing of the file should not trigger the CEDA note. If the CEDA note remains, then check the encoding attribute, which also triggers CEDA processing when it is incompatible with the session encoding. The example code below shows how to use a DATA step with a SET statement to create a native file that does not require CEDA processing:

   libname in 'path_old_directory';
   libname out 'path_new_directory';
   data out.data-set-name;
      set in.data-set-name;
   run;

The example code below shows how to use PROC COPY to create a native file that does not require CEDA processing:

   libname in 'path_old_directory';
   libname out 'path_new_directory';
   proc copy in=in out=out noclone memtype=data;
      select data-set-name;
   run;

If you want to convert an entire SAS data library, omit the SELECT statement. If you want to delete the non-native file from the source library, use the MOVE option in the PROC COPY statement.



Operating System and Release Information

Product FamilyProductSystemSAS Release
ReportedFixed*
SAS SystemBase SASMicrosoft Windows XP Professional9.1 TS1M3 SP3
Microsoft Windows NT Workstation9.1 TS1M3 SP3
Microsoft® Windows® for 64-Bit Itanium-based Systems9.1 TS1M3 SP3
Microsoft Windows XP 64-bit Edition9.1 TS1M3 SP3
Microsoft Windows Server 2003 Enterprise Edition9.1 TS1M3 SP3
Microsoft Windows Server 2003 Datacenter Edition9.1 TS1M3 SP3
Microsoft Windows Server 2003 Standard Edition9.1 TS1M3 SP3
Microsoft Windows 2000 Professional9.1 TS1M3 SP3
Microsoft Windows 2000 Server9.1 TS1M3 SP3
z/OS9.1 TS1M3 SP3
64-bit Enabled Solaris9.1 TS1M3 SP3
Microsoft Windows 2000 Advanced Server9.1 TS1M3 SP3
Microsoft Windows 2000 Datacenter Server9.1 TS1M3 SP3
64-bit Enabled AIX9.1 TS1M3 SP3
OpenVMS Alpha9.1 TS1M3 SP3
64-bit Enabled HP-UX9.1 TS1M3 SP3
HP-UX IPF9.1 TS1M3 SP3
Linux on Itanium9.1 TS1M3 SP3
Linux9.1 TS1M3 SP3
Tru64 UNIX9.1 TS1M3 SP3
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.