|
We have used this method repeatedly during the last few years for transfers of
SAS datasets from VAX/VMS and from Unix to Windows:
On the VAX side:
libname xpt xport "<path to file><member name in SAS AXP catalog>.xpt";
/* This special export library resides in a file object, not a directory. */
libname lib v612 "<AXP directory path of library>";
proc copy in=lib out=xpt;
select <member name in SAS AXP catalog> ;
run;
Using FTP (binary mode) or other binary file transfer method, copy .xpt file
to PC disk or network:
Under MS Windows:
libname lib v612 "<directory path under Windows>";
proc copy in=xpt out=lib;
select <member name in SAS AXP catalog> ;
run;
If either AXP or Windows SAS does not recognize the v612 engine, you may have to
use an earlier version number (v608?). Reversing the procedure works as well,
except that you may have to reblock Windows export datasets after uploading them
to the VAX and before copying them.
Sig
_____________________________ Original message ________________________
SAS-Lers:
Here's some PROC CONTENTS details on a SAS dataset currently residing on
our VAX Alpha.
Observations: 19939
Member Type: DATA
Variables: 22
Engine: V612
Indexes: 0
Observation Length: 177
-----Engine/Host Dependent Information-----
Data Set Page Size: 26624
Number of Data Set Pages: 134
File Format: 607
First Data Page: 1
Max Obs per Page: 150
Obs in First Data Page: 133
Host Format: AXP
Disk Blocks Allocated: 6975
I would like to know if there is a relatively painless way to get this
dataset moved over to the PC side so I can use it in PC-SAS under Win95.
Can I do this with PROC COPY ?
Any help would be greatly appreciated.
Thanks.
---------------------------
sj wall
walls@phibred.com
---------------------------
| 
