09-26-2013 08:56 AM
Would a data step help? It is a bit difficult to suggest without some context.
What code have you tried and what errors / issues are you getting?
What is your input and output like?
09-26-2013 12:19 PM
You could possibly use "PUT" to create a flat file with the SAS data you intended to export/import and then ftp or otherwise transfer the flat file and input it in a data step.
10-01-2013 06:16 AM
PUT can be used instead of PROC EXPORT, not IMPORT.
Again, explain your problems with IMPORT, and what kind of file you are trying to import.
10-01-2013 11:02 AM
I agree my repley to the initial question did not explain that the PUT was to replace the proc export portion of the planned data exchange. This is assuming that the file you want to import is a SAS file and that you have access to the platform the file is coming from. In a data step you would simply use PUT to externalize the fields needed to a flat file. The FILE stmt would specify what file the data would be written to. The systax of that varies by platfrom. A crude example that will put heading fields out for the first obs and use commas for the following is being pasted below.
FILE CSVOUT; /* CSV FILE */
IF _N_=1 THEN PUT 'SYSID,JOB,DAY,HOUR,CPUTM';
PUT SYSID "," JOB "," DAY "," HOUR "," PGMCPUTM;
This file could then be moved to the other platform via ftp or remotely access via the SAS FTP method on the platform you want to import the data to. I'm sure there are fancier ways to do this as well.
I also agree with the other poster's that an example of what errors you are encountering or what you are specifically trying to do would be key to getting a resolution.
10-10-2013 07:49 PM
Sometimes it depends on the licence. If Excel SAS talking is restricted then Proc import could be a problem.
My system does not allow me to export to Excel but I can export to csv. It doesn't allow me to do proc import an excel file.
However from the file menu you can import by following the prompt.