Date: Mon, 18 Mar 2002 15:42:07 +0100
Reply-To: Peter Crawford <peter.crawford@DB.COM>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: Peter Crawford <peter.crawford@DB.COM>
Subject: CEDA (was...Antwort: (MAR) RE: Transferring VAX data set to the
PC when a VAX is unavailable)
Content-type: text/plain; charset=iso-8859-1
I was very disappointed to discover that CEDA des not
support v8 datasets they way that SASSFIO supports
v6 sas data. Many assurances from customer support
suggested I only needed to set certain options to ensure
the data were created well enough to be read on other
platforms ....... (things I did not expect after reading the
original documents on cross platform data access) !
Now recently I see that the SAS System Viewer (which
shares the underlying basic sas file i/o routines with
SASSFIO) does not support "Network Open" for v8 datasets
>>>>>>>>> because SASSFIO does not support v8 datasets !!!
This is documented in a sas usage note 3903. see:
So it seems that CEDA does not fully replace SASSFIO as we
move data from v6.12 up to v8+ !!!
My disappointment is not enough to "move" SI
Would you like to add your weight to the proposal that
>>> SAS System Viewer should support "Network Open" of v8 data
Perhaps the friend of Charlie Schwartz would not need
to start more than a SAS System Viewer session, to read the data
if it is in v6 format. However v7+ releases are not supported
Extract from the SAS System Viewer Help
Files Supported by the SAS System Viewer
The SAS System Viewer lets you view the following types of SAS files:
Files supported by Viewer:
Read Only 7.00 Data Sets created under the Windows environment (sas7bdat, sd7)
6.04 - 6.12 Data Sets (sd2, ssd, ssd0x, saseb$data)
6.06 - 6.12 Catalogs - Directory Information Only (sc2, sct, sct0x, saseb$catalog)
3.2.2 JMP® Data Sets - Macintosh and Windows (jmp)
SAS Transport Files (stx, xpt)
SAS Log Files (.lst, .lis)
SAS List Files (.log)
HTML Files (.html, .htm)
Read and Write Enabled Comma Delimited Files (csv)
Space Delimited Files (prn)
Text Based Files (sas, dat, cfg)
Note: SAS data sets, generated by Release 6.04 and later of the
SAS System for Windows, OS/2, or DOS, can be up to 2 gigabytes
in size. Data sets can be compressed, encrypted, indexed, or audited.
Note that only data sets compressed by using the COMPRESS=YES or
COMPRESS=CHAR data set options (ie RLE algorithm) are supported.
Data sets compressed by using the COMPRESS=BINARY data set option
(ie RDC algorithm) are not supported.
Also note that the auxiliary files created to support indexing (ie .sas7bndx
or .si2) or auditing ( ie .sas7baud) cannot be opened by the viewer.
V6 data can be accessed via HTTP and FTP network protocols.
Note: The SAS System Viewer cannot open SAS files created under the Digital UNIX platform.
Version 6.12 and Version 7 Cross-platform Files Supported:
IBM AIX for RS/6000
Microsoft Windows 95 and 98
Microsoft Windows NT (Intel versions)
Open VMS Alpha
Version 6.12 Only Cross-platform Files Supported:
PowerPC for Mac OS
Data General UNIX
Open VMS VAX
Version 7 Cross-platform Files NOT Supported:
Digital UNIX (also not supported for V6 filetypes)
Datum: 18/03/2002 13:57
Antwort an: Michael Raithel <RAITHEM@WESTAT.COM>
Betreff: (MAR) RE: Transferring VAX data set to the PC when a VAX is unava ilable
Charlie Schwartz posted the following:
>A friend has a VAX SAS dataset which she would like to read in SAS on
>the PC. She does not have access to a VAX in order to make a transport
>data set. Is there a way or a tool that will allow her to do this?
Charlie; if your friend is lucky enough, she just might be able to
accomplish this task with very little effort through SAS's Cross-Environment
Data Access (CEDA). CEDA is relatively "new" and allows Version 7 and later
SAS data sets CREATED ON OTHER PLATFORMS to be read by Version 7 and later
SAS software. There are a couple of caveats, such as a degradation in
computer performance when processing SAS data sets through CEDA, but, what
the heck? At least she will be able to read the darn thing!
CEDA is included in BASE SAS software, and you do not have to invoke any
special options or procedures to use it. Your friend should simply execute
a CONTENTS Procedure against the SAS data set and see if the CONTENTS
Procedure works. If it does, cool; if not, oh well!
If the CONTENTS Procedure works, she should see something like "VAX" or
"VMS" or whatever in the HOST CREATED field.
One thing that I would heartily recommend is that she have MSGLEVEL=I set in
a SAS OPTIONS statement. Once done, she will get the following type of
message every time she processes a SAS data set through CEDA:
INFO: Data set SASLIB.Charlie.DATA is in a foreign host format.
Cross Environment Data
Access will be used, which may require additional CPU resources and
The message, above, is important because it reminds one that he/she is
processing a SAS data set from a foreign platform and that there _IS_ a
performance penalty. I, personally, do not want to lose sight of which data
sets came from where.
Charlie, best of luck to your friend as she attempts to crunch a VAX SAS
data set on her PC!
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"
Author: Tuning SAS Applications in the MVS Environment
...in violent times, you shouldn't have to sell your soul... -- Tears for
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet.
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.