Have you read the CEDA pages?
Particularly:http://support.sas.com/documentation/cdl/en/lrcon/61722/HTML/default/a002143983.htm
Also about data migration:
http://support.sas.com/rnd/migration/planning/files/crossplatform.html
Why CEDA Is Invoked for a SAS®9 File in a SAS®9 Session
Character encoding: CEDA is invoked when you share a file with users in another locale who have an incompatible encoding. For more information, see the topic about national language support or see Processing Data Using Cross-Environment Data Access (CEDA) in SAS Language Reference: Concepts.
Operating environment family: In a SAS®9 session, you can run the CONTENTS procedure on any SAS®9 file to determine the operating environment where it was created. To learn the operating environment of your current SAS®9 session, create a quick data set and run PROC CONTENTS on it. If the data representation of the file matches that of your current operating environment, then the file is native on that operating environment. If you're running under AIX, Solaris, or HP-UX, you'll notice all of those operating environments are listed in the log, because those operating environments comprise an operating environment family.
To know when CEDA is being used, set the SAS system option MSGLEVEL=I. That is:
options msglevel=i;
Here's an example of the message that displays in the log:
INFO: Data file MYFILES.GRADES.DATA is in a format that is native to
another host, or the file encoding does not match the session encoding.
Cross Environment Data Access will be used, which might require
additional CPU resources and might reduce performance.
Beginning with SAS 9.1.3 Service Pack 4, you get this behavior even if you do not specify MSGLEVEL=I.
Run proc contents, and use the OUTREP= option if needed.
... View more
