Date: Sat, 16 Mar 1996 00:07:28 GMT
Reply-To: Tom Skinner <Thomas_M_Skinner@CCM.FM.INTEL.COM>
Sender: "SAS(r) Discussion" <SAS-L@UGA.CC.UGA.EDU>
From: Tom Skinner <Thomas_M_Skinner@CCM.FM.INTEL.COM>
Organization: Intel Corporation
Subject: Re: Q: SAS transport engines
Sung-Il Cho <sungil@HOHP.HARVARD.EDU> wrote:
>Dear SAS-Lers,
>
> I'm pretty confused about sas transport engines and want to get
>some help. I'm trying to convert EPI-Info (v6) files using DBMS/COPY
>software, which provides options for sas transport files:
>1) SAS Xport Transport Engine
>2) SAS Transport V5
>3) SAS Transport V6
>4) SAS Transport V6 Compressed
>
>I've been using 'sasv5xpt' engine to convert
>PC SAS files to Unix SAS files without really understanding
>why I should go back to v5.
>Now that I see many different things about transport, I guess
>I should to know about sas transport engines in general,
>and the ways they work.
>
>While I try to get hold of the Tech Report about Transporting SAS files,
>could somebody give me a basic idea ?
>
>I'd appreciate any comments.
This is a comment, and not an explanation!
I'm pretty confused too! See the thread on VMS to JMP transports.
In my last post on the subject I retract my statemetn about CPORT create
transport
libraries being compatible with what JMP call a transport file. It in fact
requires
an XPORT engine file. When you try to CIMPORT an XPORT engine file in SAS, it
tells
you that you can't read a V5 transport file with a latter release. So does
this
mean V5 Transport=XPORT. From what you cite above as separate options, I doubt
it.
Perhaps someone can explain. This is the stuff that keep us SAS support folks
in
business.
--
Tom Skinner
End User Reporting and Analytical Tools Product Manager
Tools, Repository and Integrated Methods, IT
Intel Corporation
These are my views and opinions and not necessarily those of the Intel
Corporation
I am not an Intel Spokesperson.
|