topic Re: Shared File Library in SAS 9.2 in Administration and Deployment

Shared File Library in SAS 9.2

DavidPhillips2 — Mon, 29 Jun 2015 16:57:24 GMT

Can someone direct me to documentation that explains how to create a shared file library in SAS 9.2 and how to create a basic code block that is shared with another SAS file via an include statement. I found a lot of documentation online about using include but none that explains how to create a file library in Management Console.

Re: Shared File Library in SAS 9.2

DavidPhillips2 — Mon, 29 Jun 2015 20:33:20 GMT

Related is there a way to reference a SAS file via an include statement in the same directory

e.g.

%include \current directory\util.sas

Re: Shared File Library in SAS 9.2

Kurt_Bremser — Tue, 30 Jun 2015 05:58:39 GMT

In SAS you can address files by absolute or relative path. The relative path will start in the current working directory of the SAS process, so it is best to always use absolute paths.

One way to solve your problem is to set the path in a separate macro variable, so you need to set it only once:

%include "&your_path./&your_file";

Re: Shared File Library in SAS 9.2

Kurt_Bremser — Tue, 30 Jun 2015 06:03:02 GMT

When you store objects (like Enterprise Guide projects) in metadata, SAS uses a webdav server for the objects and stores only links in the metadata.

How to set up shared includes depends very much on your setup (remote/local, OS type, security considerations)

Re: Shared File Library in SAS 9.2

jakarman — Tue, 30 Jun 2015 13:03:54 GMT

Check the filename statement. It supports the same approach has as a libname disconnect ting from a physical location. When you have a fileref like a libref you can use that one with including sources.this HTML class.

http://support.sas.com/documentation/cdl/en/hostunx/67464/HTML/default/viewer.htm#n1cwdt7h01vaken0zl8veh8x3ybc.htm

The syntax will be " %Inc fileref (sas_source) ; " it is like using pds members on a mainframe. Concatenation is possible and can solve dtap approaches. More advanced is using catalog members that are stored in sas libraries. It is technical more complicated but solves os differences.

You have found some things about that. But I am missing what your issues are. Most likely the abstraction when done is easy but the abstraction step is difficult.

Re: Shared File Library in SAS 9.2

DavidPhillips2 — Wed, 01 Jul 2015 14:46:11 GMT

To use the filename statement it looks like I need to reference the full server path of the SAS file I am including. Is there a way to know what this path is?

All of the examples that I see online state C:/file name rather than the SAS server path.

Re: Shared File Library in SAS 9.2

jakarman — Thu, 02 Jul 2015 08:21:47 GMT

David, the naming convention wit a drive letter is the full physical path as related to the windows machine the process is running on. That is what you find in the examples.

Reading your question it could be you are asking for resources on other windows machines. That could be solved in different ways.

An admin on a windows domain could set up a dfs approach. By that the domain network connections are made on that server to possible many other locations and machines. Still offering that local drive letter but hiding all those other machines. That is often used as it made migrations easy.

Having unc names wit a server name \\server\networkname with the server in the same netbios dns name or using the full ip a dress you can explicitly use other machine resources.

All is there at http://support.sas.com/documentation/cdl/en/hostwin/63285/HTML/default/viewer.htm#refextfile.htm

That unc naming usage is with a windows sas session and not that easy with Unix. The member fileref usage is generic.

Re: Shared File Library in SAS 9.2

DavidPhillips2 — Thu, 02 Jul 2015 12:55:52 GMT

This identified the full path:

%macro grabpathname;

%sysget(SAS_EXECFILEPATH)

%mend grabpathname;

%put %grabpathname;

Re: Shared File Library in SAS 9.2

jakarman — Thu, 02 Jul 2015 14:37:23 GMT

Dave that one is windows specific for the DMS approach. See 2010 tt_sas01 making your Sas programs environment aware. It is a setting just got from the OS and Sas config.

It will not work in a sas bi/di approach what is getting more common these days as server based.

As for batch or analytics the evironment dtap and program as sysin option or in stream code are known at start why are you trying to detect that afterwards. Use the knowledge you have at the start of programs or code.