I am trying to use PROC EXPORT in SAS Enterprise Guide 6.1, through the Citrix environment, to send datasets to Excel, however seem to be having problems with the paths of the files.
The code that I have is as follows:
proc export data = work.Test
outfile = '\\servername\path\Test.xls'
dbms = xls replace;
sheet = "Test";
run;
The error message that I receive is "ERROR: Insufficient authorization to access /sasconfig/compute/ciapp/Lev1/CIApp/\servername\path\Test.xls."
The path I am providing is being appended to another path that I have not defined. Note, the server name is not an alias such as "C:", it is actually the path of the server, but I have removed it for confidentiality.
If I change the line to:
outfile = 'H:/Test.xls'
the error message is "ERROR: Physical file does not exist, /sasconfig/compute/ciapp/Lev1/CIApp/H:/Test.xls"
but if I change the line to:
outfile = '/Test.xls'
the error message is "ERROR: Insufficient authorization to access /Test.xls."
I think I fundamentally am not understanding the file paths that SAS is trying to use. What am I doing wrong/how can I determine a path where I can actually export an Excel file to?
Citrix is probably using UNIX style paths instead of Windows style paths. So instead of \\servername\path you would use //servername/path. h:\ might also be correct (but not h:/) if your SAS server has h:\ defined (not the EG location - has to be where sas.exe actually runs).
SAS EG is an interface to work on a server. If your data resides on the server, you would need to find the full network path to your computer's C drive. Otherwise, you could just change the server in EG to "local" and run everything locally so it would recognize the paths as local.
So if you have a shared drive user (typically not C:), that you can read/write to, you can use properties of a folder on that shared drive to retrieve full path and use that to export. Similarly, you should be able to open network, find the network name of your PC on there and use a relative path like \sharedservername\users\yourusername\subfolder\path\ as an export path.
You can also look at SAS EG's Export wizard's automatically generated code for a dummy export to your path and reuse that code. It will probably retrieve and write the appropriate full path for you.
Related
I am trying to copy files from one directory to another in SAS EG, but it was not working.
The basic idea in here is to convert .xlsm file to .xlsx file.
%sysexec( copy "&path.\excel1.xlsm"
"&path.\excel1.xlsx" ) ;
I didn't get any error in SAS EG, but nothing happen (no file copied), does anyone know the reason?
Make sure that your SAS session has the XMCD option turned on.
XCMD Enables the X command in SAS.
You can use PROC OPTIONS or GETOPTION() function to see the current setting. This option must be set when the session starts so you might need to modify the server you are connecting to with Enterprise Guide to one with the option turned on (or modify the configuration of the server).
Also make sure that the command and path you are using will work on the server where your SAS code is running. You can look at some of the automatic macro variables like SYSSCP, SYSHOSTNAME and SYSHOSTINFO to see the operating system where SAS is running.
22 %put &=sysscp &=syshostname &=syshostinfolong ;
SYSSCP=WIN SYSHOSTNAME=XXXXXX SYSHOSTINFOLONG=X64_10PRO WIN 10.0.18362 Workstation
If you still have issues you can also use another method to run your command where you will be able to more easily see the messages that the operating system might generate. For example using the PIPE filename engine.
data _null_;
infile %sysfunc(quote(copy "&path.\excel1.xlsm" "&path.\excel1.xlsx" 2>&1)) pipe;
input;
put _infile_;
run;
I am just playing around with SAS, writing the following code
options nocenter nonumber;
data vag;
infile "C:\Users\Deborah\Desktop\School\STA 318\book\veggies.txt";
input Name $ Code $ Days Number Price;
CostPerSeed = Price / Number;
run;
The location of the file is correct, but the error I am getting
ERROR: Physical file does not exist, /opt/sasinside/SASConfig/Lev1/SASApp/C:\Users\Deborah\Desktop\School\STA 318\book\veggies.txt.
What can I do to fix this?
You are working on Unix server, not you local PC. While you are running a local client on your PC (like SAS EG), you can't actually access local resources on your local PC because these resources needs to be made available to Unix box itself.
You have four options:
1. Use an import Wizard in SAS EG. It will generate a data step and will use hidden SAS EG methods to convert your text file and move it as a data set to Unix server where you then can create variables that you want.
See if your file system is available to you in SAS EG. Expand your workspace server. You should see "files". Expand to the folder that you are allowed to use and drag&drop your text file into there.
Upload files to the unix server using whatever file transfer method is available. Usually you would have some sort of FTP server running.
Also, as Joe suggested, you can install this custom task http://blogs.sas.com/content/sasdummy/2012/12/06/copy-files-in-sas-eg/
It can do a lot better job that step 2 or 3 because it can be part of your process, resolve macro variables and fix file formatting issues between Windows and Unix. Thanks Joe!!
We have default SAS workspace of x TB. We also have alternate 10X TB workspace on same server at different folder location.
Can anyone please help me with syntax that can be used in SAS EG to point to the alternate workspace instead of default one?
The SAS work directory can be changed for individuals by creating a $HOME/sasv9.cfg file and placing one line in it:
-WORK {full path to the SAS work directory}
if you are running in unix, you can change the work directory in the execution. nohup sas -work /myworkdirectory mypgm.sas &
Are you referring to the SAS work library, which is the location where SAS lets you store temporary data sets?
If so, then it depends. Are you using EG to in a client/server setup? In that setup you will have to get your SAS Admin to make changes on the server or in the SAS Metadata to point the work library for all Workspace Servers that start to use the other location that has more available space.
Would you not define SAS libraries out of these workspaces?
i.e. libname mydata '/folders/myfolders/'
This will then assign each library to your active SAS session.
Use this as precode to any manipulation your doing.
If you have Management Console, or Using PROC METADATA you can create permanent libraries.
You mentioned workspace, so I assume you need to control the WORK library.
Use the SAS system option
options work=library-specification
In the SAS documentation it states: specifies the libref or physical name of the storage space where all data sets with one-level names are stored. This library must exist.
Make sure the the file space is "close" to where the processing is done or file transfer will be a bottleneck.
Hi I don't have much space on my C drive so I'm looking to move my work library for SAS EG 5.1 over to a folder on my D drive. How could I do this?
Thanks!
Presuming you are using EG to work locally, you can change it in your sasv9.cfg file:
This is usually found in the SASFoundation/nls/en (or equivalent language) directory.
Another option (which avoids changing the config file) is to change the value of the TEMP environment variable. Remember though that SAS is I/O heavy, and if the D drive is a remote network location you may suffer performance-wise..
An option if you're unable to modify the Config file, is to define a USER libname:
libname user "d:\saslib\";
or similar. That will become your default one-level libname (ie, if you say data have; that will now be stored in user.have, not work.have). It doesn't override it if you have specified work explicitly, and it doesn't automatically clean up after itself, so be aware of these issues.
I created some CSV files and exported them to a file folder on a SAS server. I'm using the Excel SAS add-in to make some charts. For whatever reason, the only folder I can access is "My Folder", which I can also view inside Enterprise Guide. There, I can modify it and make changes.
Unfortunately, I can't figure out the path to the folder. I want to write my text files (or maybe some datasets) to that folder so I can access them with the add-in. Side note - I tried to just export the CSV files to a network drive but wasn't allowed for security reasons I guess. It looks like I'm stuck with "My Folder" being the only option, I just can't figure out the path to make use of it.
If your "My Folder" is equivalent to a SAS library, you can do the following:
%sysfunc(pathname(work));
That gives you the path to the work library, which is at least one location that you have write access to.
My guess is that you are confusing two things:
1. Physical folders. (the ones you are looking for)
2. SAS Metadata. (the 'file system' you are seeing)
It has been a while i worked with the excel add-in, but if (no guarantees ;)) i recall correctly, you can only access SAS objects that were registered in the SAS server metadata.
The SAS metadata looks like a file structure, but it is virtual. Objects in the same metadata folder can actually have a totally different disk location.
The easiest way would be to register the file you want to access in the metadata. (the 'my folder' if you want to make it easiest) Of course, this requires certain administrative rights on the server.
If not possible, i'm not sure that you can access it some other way through the SAS add-in.
For reference, the metadata path to your "My Folder" is /User Folders/&sysuserid/My Folder
You can store the files in a folder on the server and give a reference to the folder using LIBNAME in the autoexec.sas file in your ~/home folder on the server. The when you browse libraries using the add in, you will see the reference to your folder present there.
for the university demo edition on linux/Mac try this
INFILE '/folders/myfolders/yourfilename';
if you have set up your shared folders as described in the install howto.
See one example from "the little SAS book" loading raw data:
You can also see the path in the status line at the bottom
Other aproach: enter
%put all;
will list "all" macro variables in the log. There you can find:
GLOBAL USERDIR /folders/myfolders
So in the example above you could also use
INFILE "&USERDIR/yourfilename";