Date: Mon, 8 Jun 2009 13:54:39 -0400
Reply-To: Michael Raithel <michaelraithel@WESTAT.COM>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: Michael Raithel <michaelraithel@WESTAT.COM>
Subject: Re: Remote back to local in sas/connect?
Content-Type: text/plain; charset="us-ascii"
Jack Hamilton posted the following:
> If I have set up a connection to a remote session, I can use
> a remote libname to write from the local session to a library
> on remote machine.
> Is there a way for code executing on the remote session
> inside an rsubmit block to write data back to a library in
> the local session (without setting up another remote session
> in the opposite direction, and not using sas/share)?
Jack, I agree with Andre. I think that the only way to do this is to use a PROC DOWNLOAD to "force" your remote data back down to a local SAS data library. See example #1 in my SAS Global Forum 2007 paper:
Process Your SAS(r) Datasets Anyway, Anyhow, Anywhere You Choose With SAS/Connect
That is how I have always handled this type of situation. And, there are other PROC DOWNLOAD options that will allow you to download more than just a single SAS data set at a time.
But, having said all of that, I am also wondering if there is a way to do something along the lines of this from example #3:
libname LINUXLIB "/home/marsyst/wessug" SERVER=SASB;
...within an RSUBMIT block on the remote server, where SASB is actually my local server. Kind of like:
libname WINLIB "C:\home\marsyst\wessug" SERVER=SASB;
...so that anything "stored" in the WINLIB SAS data library on the remote server will actually be stored on my local machine.
I don't think it will work, but don't know for sure. Perhaps we will get lucky and a SAS/CONNECT guru birdie will take time off from collecting earthworms and building a nest to chime in on this thread... privately, of course!!!!!
I hope that this suggestion proves helpful now, and in the future!
Of course, all of these opinions and insights are my own, and do not reflect those of my organization or my associates. All SAS code and/or methodologies specified in this posting are for illustrative purposes only and no warranty is stated or implied as to their accuracy or applicability. People deciding to use information in this posting do so at their own risk.
Michael A. Raithel
"The man who wrote the book on performance"
Author: Tuning SAS Applications in the MVS Environment
Author: Tuning SAS Applications in the OS/390 and z/OS Environments, Second Edition
Author: The Complete Guide to SAS Indexes
You cannot prevent the birds of sorrow from flying over your head,
but you can prevent them from building nests in your hair. - Chinese Proverb