|Date: ||Fri, 14 Dec 2001 13:03:01 +0100|
|Reply-To: ||Ace <b.rogers@VIRGIN.NET>|
|Sender: ||"SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>|
|From: ||Ace <b.rogers@VIRGIN.NET>|
|Subject: ||Re: sas/connect question|
|Content-Type: ||text/plain; charset=us-ascii|
On Fri, 14 Dec 2001 12:44:13 +0100, ciro baldi <firstname.lastname@example.org> wrote:
>i use sas v8 on pc connecting to a remote host unix with sas/connect.
>i use the remote library system to look at the datasets on the remote
>i can do it easily for permanent library, but it's complicate for
>looking at the datasets in the
>temporary work_area, because i don't know in advance how sas on the
>remote host name the temporary directory. A (not very satisfying) way to
>bypass the problem is 1) launching the connection 2)go to unix and take
>note on what is the name of the work-directory that sas has created
>3)come back on the sas-pc and write on the program another remote
>Can somebody suggest me an automatic way to manage this issue?
>thank you in advance
The information you require is stored, amongst other places, in the
view SASHELP.VSLIB on the remote machine. So you can access this,
either by creating a remote libname for the SASHELP library, or remote
submitting code and transferring the result, then using it to assign
the remote libname.
A quick solution that comes to my mind would be something like this:
rsubmit MYSERVER ;
proc sql noprint ;
create table workpath as select path from sashelp.vslib where libname
= 'WORK' ;
proc download data=workpath;
proc sql noprint;
select path into:path from workpath ;
libname remwork remote "&path" server=MYSERVER ;
Unfortunately, it seems that in some environments, like the UNIX I
just tested this on, the directory used for the WORK libname is only
created in a transient space, so cannot be accessed by processes
except the original creating process.
So you won't be able to access the remote WORK library through LS at
all, at least in a UNIX environment.
Best of luck anyway,
Ace in Alsace