As the first step in the decommissioning of sasCommunity.org the site has been converted to read-only mode.
Here are some tips for How to share your SAS knowledge with your professional network.
Tips Talk:Remotely subset a large dataset
Good tip. Agree with Art that a link would help. --Don Henderson 20:43, 28 January 2012 (EST)
might it be wise to split this a little?
SAS/Connect supports remote access to the remote library even more simply! (without needing to determine libname path)
In the local session:
LIBNAME RWORK REMOTE SERVER= PRDSYS SLIBREF= WORK ;
documented in example of a client using a server library
The potential benefit (performance) arising from using the path to the remote library, occurs when the client can read the server file-system directly - without using SAS/Connect Remote Library Services(RLS).
libname rpath "&pad" access= readonly ;
This works in a SAS/Connect mpConnect context using the SASCMD= or depends on something like UNC conventions.
Performance gain then occurs because you avoid the SAS/Connect method which implements a trantab conversion, like proc cport and proc import, of the data that is passed over that RLS connection.
Another option to obtain the objectives of this tip : - use the INHERITLIB option of "signon" or "rsubmit" statements to make local (client) libraries available on the remote (server) session. then the code could be
rsubmit PRDSYS inheritlib=( work=Cwork ); DATA CWork.test1; SET sashelp.class; WHERE sex='M'; RUN; endrsubmit ; proc print data= work.test1 ; run ;
Inheritlib is documented for rsubmit at rSubmit documentation
- Peter Since you have done most of the work already, would you consider turning your above notes into an article which can be cited by the tip. That way we can contrast techniques. This is a bit outside of my area so I hesitate to do it myself. This tip is currently the only thing in the RSUBMIT Statement category. --Art Carpenter (talk) 17:35, 9 February 2014 (CST)