|SAS/CONNECT User's Guide|
|SAS Software Products|
Both SAS/CONNECT and SAS/SHARE provide services in a
client/server environment. However, there are well-defined differences between
the functionality of SAS/CONNECT and that of SAS/SHARE. Mapping these characteristics
with the requirements of an application should enable you to determine which
product you need to get the job done. In many cases, you might find that you
want to combine functionality from both products.
What is SAS/CONNECT software?
SAS/CONNECT software enables a SAS session on one host to create a SAS session on another host and use that remote session to access remote data and execute SAS statements.
SAS/CONNECT software provides various services for the client/server environment:
What is SAS/SHARE software?
SAS/SHARE software provides a multi-user client/server environment for the SAS System. The multi-user server provides concurrent update access to SAS data for local and remote users across the enterprise. The server also provides remote users with low-overhead connectivity for reading SAS data.
SAS/SHARE software consists of two procedures and a SAS I/O engine:
What is the difference between
SAS/CONNECT software and SAS/SHARE
SAS/CONNECT software puts the full power of the SAS System at your disposal on the remote host. You can send work to it and get back the results, use it to download or upload data, or access remote data through it as if it were local. If you license SAS/ACCESS software on the remote host, you can also update DBMS data. However, update access to SAS data through the remote session requires that the remote session have exclusive access to the data.
SAS/SHARE software, by contrast, provides a multi-user
data server which permits access to remote data as if it were local and concurrent
update access to that data by multiple client SAS sessions. You cannot send
arbitrary work to a SAS/SHARE server to be performed, and you cannot update
DBMS data, but you can share SAS libraries, data sets, and catalogs with other
users in update mode.
What is the difference between
creating a SAS/CONNECT remote
session and connecting to a remote SAS/SHARE server?
A SAS/CONNECT remote session is a dedicated SAS session on the remote host. This session is exclusively yours. You create the remote session when you need it, and terminate it when you are finished with it.
A remote SAS/SHARE server is a single SAS session that
is shared by many users for the purpose of local access to remote data. The
server reads and writes data on behalf of its users but typically has its
own privileges and permissions. The server must already be running when you
try to connect to it and continues to run after you disconnect from it. The
server is started by an administrator or as part of system start-up.
How is the REMOTE engine distributed?
The REMOTE engine is distributed with base SAS software.
You must license either SAS/CONNECT or SAS/SHARE software in order to use
it. Licensing either product on the local (client) machine allows you to use
it to access data through a SAS/SHARE server. Of course, SAS/SHARE software
must be licensed on the remote (server) machine.
What is remote library services?
Remote library services (RLS) is a feature of SAS/CONNECT and SAS/SHARE software that allows you to access SAS data on a remote host (regardless of machine architecture) as if it were local. The REMOTE engine sends requests either to a single-user SAS/CONNECT server that runs in a SAS/CONNECT remote session or to a multi-user SAS/SHARE server that runs in its own SAS session on the remote host.
I have end users with desktop machines who just need read-only access to SAS
data on a mainframe or on a UNIX workstation. Because they only need read
access, not update access, should I license only SAS/CONNECT software on the
client and server machines?
Not necessarily. If your users need remote computing services on a mainframe or on a UNIX workstation or if they need bulk data transfer services between the platforms, you need SAS/CONNECT software on the desktop (local) and remote (mainframe or UNIX) hosts. However, if you have a number of users who only need to read remote data, you can avoid the overhead of a SAS/CONNECT sign on for each of those users by licensing SAS/SHARE software on the remote hosts and SAS/CONNECT or SAS/SHARE on the local host. The users can use remote library services to connect directly to the SAS/SHARE server on the remote platform and access subsets of the data more quickly.
Top of Page
Copyright 1999 by SAS Institute Inc., Cary, NC, USA. All rights reserved.