02-12-2007 11:29 AM
02-27-2007 08:21 AM
03-09-2007 12:57 PM
03-12-2007 02:43 PM
08-19-2010 10:25 AM
10-24-2011 09:50 AM
I am using the EG 4.2, is there a way to perform this task programatically? That is, Upload/Download SAS Data Sets using SAS Code.
10-24-2011 11:14 AM
A couple of ways come to mind.
1) if you can map the local drive from the server (or know the UNC name), you can use LIBNAMES and PROC COPY.
2) if you local administrators will enable the X command in SAS, you can use the OS copy procedures to move the files.
02-03-2016 04:51 PM
You note the UPLOAD uses the SAS OLEDB local data provider.
Q1: Is the OLEDB provider dependent on the bitness of the SAS table? Supposing the providers are different, 32/64 and are dependent on the bitness of the SAS table...if one installs EG32 or EG64 (no local SAS) are both the SAS OLE32 and OLE64 data providers installed?
Q2: If a SAS table is loaded from one OS, Windows, to another OS, Unix...will the table be migrated so the cross-platform engine on the Unix server would need be utitlized (32 migrates to 64). (I might surmise that if the OLEDB driver is being used, the SAS table is not going through a simple binary/ftp transfer)
02-03-2016 06:55 PM
Wow @RogerSpeas, you win the award for updating the oldest thread this week! (This post was originally from 2007.)
To answer your question, the OLE DB provider is not a factor during the Upload or Download. In the original post, I just wanted to point out that when you don't use the Upload task, you can still read local data set files with EG and EG will transfer those records to SAS as needed -- but it's slow. The Upload task makes the transfer a faster operation -- using a binary FTP-like transfer.
After Upload, the task checks to see if the data set encoding matches that of the SAS session and if it doesn't, it runs a DATA step to fix it up.