topic Re: SAS Connect, passing local client library to remote server SAS session in SAS Programming

SAS Connect, passing local client library to remote server SAS session

advoss — Mon, 02 Dec 2013 15:04:16 GMT

My apologies if this is not the correct forum; please advise me of a more appropriate forum.

I am using SAS Connect to connect my Windows workstation to a UNIX work station (SASDEV1).

I can/do access the UNIX SAS libraries on my Windows workstation using LIBNAME statements with the SLIBREF option.

Is there a way that I can reference/work with my local SAS libraries on the UNIX session? I know that I can PROC UPLOAD the data,

Something like:

SIGNON SCRIPT=RLINKUN9 REMOTE=SASDEV1;

libname UNIXWORK SERVER=SASDEV1 SLIBREF=WORK;

libname LOCALPRM 'C:\LOCALPRM';

RSUBMIT SASDEV1;

libname WINDOWSP ???? WLIBREF=LOCALPRM;

...

libname WINDOWSP clear;

ENDRSUBMIT;

SIGNOFF SCRIPT=RLINKUN9 REMOTE=SASDEV1;

Thank you.

Re: SAS Connect, passing local client library to remote server SAS session

SASKiwi — Mon, 02 Dec 2013 19:15:26 GMT

Here are a couple of options to check out:

1) Signon from remote SAS session on the Unix workstation back to your PC. You will have to ensure that the Unix SAS session has a signon script that will work back on your Windows PC and your PC security setup may have to be changed to allow remote connections from the Unix box. Then you can assign SLIBREF-type LIBNAMEs referencing your PC libraries exactly like you are doing already.

2) Create network shares on Unix to point back to your PC folders, something like //mypc/mycdrive/myfolder. This will probably require help from your IT network people. With a network share you just put the full path in a standard LIBNAME statement. You may also need the LIBNAME option to store SAS data in cross-platform format as you are working across operating systems.

Re: SAS Connect, passing local client library to remote server SAS session

advoss — Mon, 02 Dec 2013 20:15:41 GMT

Thanks, SASKiwi.

I had thought of your option 1, but IT does not allow us to connect to Windows workstations...security risk. For similar reasons, I'm pretty sure that option 2 is not allowed, either.

But, thank you for your input.

Re: SAS Connect, passing local client library to remote server SAS session

SASKiwi — Mon, 02 Dec 2013 22:32:07 GMT

Then how about a central file share that is accessible to both your PC and your Unix workstation? Or just use PROC UPLOAD as you have already mentioned.

Re: SAS Connect, passing local client library to remote server SAS session

Patrick — Tue, 03 Dec 2013 06:57:59 GMT

Could you do the same the other way round? From the Unix box to Windows?

If so then you could nest the rsubmits: first connect to Unix and then within this session rsubmit back to Windows - and define the remote library as seen from the Unix box (so the slibref within the outer rsubmit block.

Re: SAS Connect, passing local client library to remote server SAS session

advoss — Tue, 03 Dec 2013 13:22:03 GMT

Sorry, but within our environment, we can't SIGNON to Windows workstations.

I thought that there was, perhaps in SAS V8 a system option that allowed the passing of the a libref from the client to the server, but I must have just dreamed that. And, if it wasn't a dream, it was probably only for the WORK library.

Thanks, everyone, for the input.

Re: SAS Connect, passing local client library to remote server SAS session

Peter_C — Thu, 05 Dec 2013 22:00:52 GMT

http://support.sas.com/documentation/cdl/en/connref/63066/HTML/default/viewer.htm#p1eyablk3vvdlkn1h5euyczvt585.htm

Inheritlib

Re: SAS Connect, passing local client library to remote server SAS session

advoss — Thu, 05 Dec 2013 22:15:21 GMT

That's was what I was looking for. Thank you, Peter. I'll go read the information, now.