Chapter Contents

Previous

Next
SAS/CONNECT User's Guide

Introduction

To access a server, you submit a LIBNAME statement to your local SAS session to define a remote SAS data library. The location of the remote SAS data library is determined by the value of the SERVER= option in the LIBNAME statement. The following figure shows how the LIBNAME statement is used to access a remote data library.

Accessing a Remote Data Library

[IMAGE]

To access a multi-user server, the server must already be created and running. You specify the name of the server in the SERVER= option in the LIBNAME statement. The value of the SERVER= option is first checked to see if it matches the remote session id of one of the current SAS/CONNECT conversations. If it fails to match any of the current remote session ids, it is assumed to identify a multi-user server. Therefore, if you are accessing both a single-user server and a multi-user server from your local SAS session, you must use unique values for the SERVER= option. The use of the single-user server takes precedence over the use of the multi-user server.

After you have a libref defined to a server, you should avoid clearing and re-assigning the libref multiple times. Repeating this sequence is inefficient because, as the last libref that is associated with a server is cleared, the local session disconnects from the server. When the same libref is re-issued, the local session must again connect to the server. To avoid this overhead, only clear the defined librefs when you have completed any processing that accesses data that is defined by these librefs.

A server does not terminate when the last LIBNAME statement is cleared. A multi-user server remains active, awaiting connections from users until it is stopped by the server administrator using the OPERATE procedure (refer to the SAS/SHARE User's Guide for more information about multi-user servers). A single-user server remains active, awaiting new connections from a local session until you sign off. The remote session also remains active for subsequent remote submits. To terminate both the remote single-user server as well as the remote SAS session, you must issue the SIGNOFF command at the completion of all remote processing.


Chapter Contents

Previous

Next

Top of Page

Copyright 1999 by SAS Institute Inc., Cary, NC, USA. All rights reserved.