Date: Wed, 21 Jul 2010 08:37:29 -0400
Reply-To: Michael Raithel <michaelraithel@WESTAT.COM>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: Michael Raithel <michaelraithel@WESTAT.COM>
Subject: Re: CEDA - Native Data Set
In-Reply-To: <201007202036.o6KICAmd006990@willow.cc.uga.edu>
Content-Type: text/plain; charset="us-ascii"
Dear SAS-L-ers,
Swamy posted the following:
> Hello,
>
> I am using SAS 9.2 TS Level 2M2 , XP_PRO Platform
> Trying to access few SAS data sets which was created in UNIX,
>
> Error message
> ***********************************************************************
> TWING.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.
> ***********************************************************************
>
> Can someone please help me to understand this error message and the
> steps
> to make the Data sets readable , I looked at few reference about CEDA -
> Cross-Environment Data Access, but was not sure how could I open those
> data sets in windows.
>
Swamy, as you have heard from clever SAS-L-ers Mary, Michael, and Tom, this is not an "error", but simply a warning from SAS telling you that the data set you are trying to read under SAS for Windows was created by SAS running on an operating system foreign to Windows--in this case UNIX. (<--Hey, can that count as the longest non-run on sentence posted to SAS-L for 2010?!?!?!?). As you noted, SAS used its CEDA engine to process the data set. So, I would wager that you got what you wanted--unsettling log message aside.
The best ever treatise on CEDA was written by fellow Washingtonian Bruce Gilsen, for the SUGI 31 conference:
CEDA; The Invisible Hand
http://www2.sas.com/proceedings/sugi31/225-31.pdf
It may be a bit old, but the information is well presented and accurate.
Oh, hey, take special note of the many things that you _CANNOT_ do with a SAS data set created on a foreign OS. Those are the things that will produce the true ERROR:'s in your Windows SAS programs!
Swamy, best of luck in all your SAS endeavors!
I hope that this suggestion proves helpful now, and in the future!
Of course, all of these opinions and insights are my own, and do not reflect those of my organization or my associates. All SAS code and/or methodologies specified in this posting are for illustrative purposes only and no warranty is stated or implied as to their accuracy or applicability. People deciding to use information in this posting do so at their own risk.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Michael A. Raithel
"The man who wrote the book on performance"
E-mail: MichaelRaithel@westat.com
Author: Tuning SAS Applications in the MVS Environment
Author: Tuning SAS Applications in the OS/390 and z/OS Environments, Second Edition
http://www.sas.com/apps/pubscat/bookdetails.jsp?catid=1&pc=58172
Author: The Complete Guide to SAS Indexes
http://www.sas.com/apps/pubscat/bookdetails.jsp?catid=1&pc=60409
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
All the powers in the universe are already ours. It is we who
have put our hands before our eyes and cry that it is dark. - Swamy Vivekananda
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
