I know that recent versions of EG can copy files between a SAS server and the local Windows filesystem. But is there any way of getting EG to delete a file as a step in a process flow?
Assuming you're running EG connected to a server that does not have access to your local PC, I don't believe you can without using .NET or something inside EG. You cannot do something like run an X command or similar, because SAS is not on your local machine and can't access it.
It should be possible however to script (using .NET) an extension to EG to do something like this, though (the same way the copy files extension was originally written). But it wouldn't be a SAS process.
Note: The original task was described in a blog post by Chris Hemedinger; that post did not however describe how to actually write such an extension beyond detailing that it uses SAS Workspace APIs. You might look into that first.
Related
I'm struggling to find a solution to this problem.
The import/export wizard works fine from SAS for pathing to static local and shared drive file locations.
I get stuck trying to use PROC EXPORT so save multiple datasets to different sheets in an Excel workbook for retention policies.
I thought I found a solution that would be great. Referencing a LIBNAME to a local file.
When I run:
""LIBNAME x xlsx 'C:\Users\xxxx\Desktop\EXISITING_CONSOL.xlsx';""
I get confirmation it worked, but when I reference it or try to view it in the Servers navigation window it errors out.
NOTE: Libref X was successfully assigned as follows:
Engine: XLSX
Physical Name: C:\Users\xxxx\Desktop\EXISITING_CONSOL.xlsx
Current version: 9.04.01M3P062415
Operating System: LIN X64
---SAS/ACCESS Interface to PC Files
I would like to use this library method but I'm indifferent to a solution as long as I can save the datasets to a folder path through my PC that I can F3.
I appreciate any direction!
The issue you have here is that SAS can't actually see your c:\users\... folder, unless you have a share set up (and since the SAS Server is on Linux, it would have to have a different structure anyway). The "Import wizard" actually imports it locally (using some .Net code in Enterprise Guide) and then uploads the data to the SAS server.
The normal way this is handled is for you to use a network share that both SAS and your local PC can see - often something like \yourcompany.com\sharename\foldername\ or similar.
If you don't have something like this, then you can use the "Copy Files" task in Enterprise Guide to copy files down locally that are on the server. See this blog post about it.
Basically when I do sorting or join table in sas, the sas will use resources / space from local disk C: to process the code, but since I only have 100GB left on local disk C:, It will result in error whenever SAS was out of resources.
My question is how to configure / change the setting in SAS to use resources from Local Disk E: instead, since I have larger space there.
I already looking through the forum, but found no similiar question.
Please Help.
Assuming you are talking about desktop SAS, or a server that you administer, you can control where the work and utility folders are stored in a few ways.
The best way is to use the -work and -utilloc options in your sasv9.cfg file. That file can be in a few places, but often the SAS Shortcut you open SAS with specifies it with the -CONFIG option. You can also set the option in that shortcut with -WORK or -UTILLOC command line options. The article How SAS Finds and Processes Configuration Files can help you decide the location of the sasv9.cfg you want to modify; if you are using a personal copy on your own laptop, you may change the one in the Program Files folder, but if not, or if you don 't have administrative rights, you have other places you can place a config file that will override that one.
A paper that discusses a few of these options is one by Peter Eberhardt and Mengting Wang.
One way is to set up a library named user for projects that will be time intensive and this way you get it to be dynamic as needed. When you have a library called user, that becomes the default workspace instead of work. But, you need to clean up that library manually, it won't delete data sets automatically when you're done with it.
libname user '/folders/myfolders/demo';
As #Tom indicates, you can also set an option to use a library that already exists if desired.
options user = myLib;
An advantage of this method over the config file method as it only does it for projects where it's needed, rather than your full system.
I need to extract a particular sheet from a .xls file on my local machine and get it as a .sas7bdat files on the SAS server on which I work (or the other way round, that is, import it and then convert).
The problem is that although this can be done using the Import Wizard, I need to do this using the 'Copy Files Add-in' because it needs to be built as a part of an automated process.
When I tried doing this using the copy files add-in, it DID copy the .xls file onto the server according to the log, but the .xls file didn't actually show in the library and could not be referenced either (or maybe I'm just referencing it wrongly).
This has led me to believe that I need to convert it to a .sas7bdat and then import it.
Is there a way to get past this? Please bear in mind that I am talking about an automated process, so the wizard is useless for me (or is it? I'm not sure)
NOTE : I am extremely sorry that I cannot post the log and screenshots here, because I work as an offshore resource for a very large bank and cannot post anything here. I have, however, tried to make my problem as clear as possible. If any further clarifications are needed, please let me know!
I assume you've read There and Back Again which covers this in some detail.
Ultimately, all you're doing is copying the excel file as a file onto the SAS server. You're not importing it into a SAS dataset. You would import it by placing the file (either the remote file after copy files add-in, or the local file) in the workflow as an import step.
For example, if you chose /usr/lib/sasdata/myexcel.xls as the remote copy destination, you then need to include that file in your workflow as an import step (you can drag/drop the file and it will automatically create that step for you, with some wizardry).
I have a production environment server using SAS Platform.
Is there a way to generate a report of a list of all metadata objects deployed in this production environment?
More accurately, is there an easy point-and-click way using one of the SAS Tools (e.g. SAS EG, SAS DI, SAS SMC)? If not I am open to the "right" way of doing it.
you can try using the %MDSECDS macro which is shipped whit SAS/Foundation. This macro provide a lot of informations like you are looking for.
If you are looking to extract a list of all the objects that can be seen in the folder tree, this macro from the macrocore library will do it:
%mm_tree(outds=allmyobjects)
Note - if you have multiple repositories, you will need to run this for each (and set options metarepository=YOURREPO; each time).
A macro to get the list of repos is available here.
I am running SAS EG which is installed in Windows but have access to GRID in AIX. Now I want to drop some of the files generated in a program (mostly csv) to a windows location.
My first question, is it possible without using fancy X or call system (guessing) routine with just one libname or filename.
Second question is will it be possible to drop generated files from EG session in the windows directory.
If you have SAS/CONNECT licensed, and are able to run a local SAS session as well as the connection to UNIX, you can use PROC UPLOAD or DOWNLOAD, or even better, you can define a libname like so:
libname ulib server=unix slibref=work;
server=unix defines which remote session you are accessing (you may have multiple simultaneously) and slibref=work defines which server-side libname you are accessing. Change both values as needed. This requires having an open connection to the server (via SAS/CONNECT), and would be executed in your local session.
If you do NOT have SAS/CONNECT licensed, and/or cannot start a local session on your desktop, you have a few options.
First off, if the UNIX server can mount the windows location as a drive, then you can simply write to it as if it were on the UNIX machine. This is likely if it is on a shared drive on your NAS or similar; however, if by 'windows location' you mean 'on my desktop machine', it's unlikely.
Second, you may be able to use an EG add-on that allows you to do this. If you're able to install it, it's a simple point and click interface. It is NOT scriptable in SAS (it may be scriptable via automation, I'm not sure). Chris Hemedinger made it available in his blog (currelt(http://blogs.sas.com/content/sasdummy/2012/12/06/copy-files-in-sas-eg/); it is called "Copy Files" if that link breaks and you need to search for it. The blog post has the add-on and instructions for installing it.