BookmarkSubscribeRSS Feed
msd83
Calcite | Level 5

Hi all,

I have some SAS datasets that were created on Windows operation system (Base SAS 9.2). The files have been copied to a Base SAS 9.4 running on a UNIX environment. I am trying to convert these to SPDE data sets using PROC COPY but this does not seem to work. It seems this is becuase the datasets were created in a Windows operating system.

Has anyone got any advice?

Many thanks

6 REPLIES 6
msd83
Calcite | Level 5

I don't have the log information but I will try and provide when I run the PROC copy again.

LinusH
Tourmaline | Level 20

It's not clear how you use PROC COPY.

Basically, SPDE tables can never be copied/moved with non SAS tools - search paths etc is included in the metadata portion of the data set. To be able to use PROC COPY in the situation you describe, is to use it on a Remote Libname between the old Windows server and the UNIX server. This could work, but gives awful performance.

If you can use SAS/CONNECT, PROC DOWNLOAD is a far better option.

Otherwise, PROC CPORT/CIMPORT is a method that should be reliable.

Data never sleeps
Peter_C
Rhodochrosite | Level 12

Have a look at the dataset option CEDA

(Stands for cross environment data access)

LinusH
Tourmaline | Level 20

Yeah, CEDA could work. But I believe that the tables still needs to be in it's original location, so ability to mount that Windows drive across the network is crucial.

Data never sleeps
msd83
Calcite | Level 5

Thanks for the idea, I will explore the CEDA option as well.

Thanks LinusH as well.

CFC_SAS_Communities_400x225.jpg

Call for content now open!

It's your turn to help shape SAS Innovate 2027. Share your expertise and inspire the SAS community.

Submit your proposal →

How to connect to databases in SAS Viya

Need to connect to databases in SAS Viya? SAS’ David Ghan shows you two methods – via SAS/ACCESS LIBNAME and SAS Data Connector SASLIBS – in this video.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 6 replies
  • 4451 views
  • 0 likes
  • 4 in conversation