Date: Thu, 3 Jul 2003 09:54:32 -0400
Reply-To: Sigurd Hermansen <HERMANS1@WESTAT.COM>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: Sigurd Hermansen <HERMANS1@WESTAT.COM>
Subject: Re: DBMS/Copy, v9, & PROC Copy
Content-Type: text/plain; charset="iso-8859-1"
The XPORT variant of the LIBNAME statement is one of the rare cases in which
the connection string can have a file extension. The SAS XPORT engine
actually treats a system file as a SAS library. For that a PROC COPY to or
from an XPORT library should include a SELECT statement. One note of
caution: the XPORT library (file) name does not have to have the same name
as a dataset it contains. In most cases I create a separate XPORT library
for each SAS dataset and use the name of the dataset as the 'stem' of the
XPORT file name.
Sig
-----Original Message-----
From: Miller, Jeremy T. [mailto:zyp9@CDC.GOV]
Sent: Wednesday, July 02, 2003 3:19 PM
To: SAS-L@LISTSERV.UGA.EDU
Subject: DBMS/Copy, v9, & PROC Copy
SAS-Lers,
How are most of you dealing with v9 and DBMS/Copy. Is the best approach to
create xport files with PROC COPY?
Lets say I have this data set:
data a;
do i = 1 to 10;
output;
end;
run;
If I wanted to read this with DBMS/Copy, how do I create a file using PROC
Copy. I've looked at the online doc, but I'm not getting the:
libname xptout xport 'filename-on-sending-host';
because the filename that is created has no extension. Without an
extension, DBMS/Copy won't let you select it.
Thanks.
|