SAS/SHARE User's Guide

Starting a Server: A Fast-Track Approach

You may need to use the fast-track approach to start a new server quickly if

you are installing SAS/SHARE for the first time.
a new application presents a sudden demand.
system resources become strained and require that the workload be shifted to a new server.

If you are new to SAS/SHARE software, there are a number of different issues to consider as you fine-tune your server environment: system options, pre-defined libraries, automated start-up, and so on. However, you might want to defer some of these issues and start a server right away so that your applications developers can begin to create new applications or migrate old ones to the multi-user environment.

To get a server up and running with minimal effort, perform the following steps in a SAS session on the server machine (that is, the host at which you start a server):

After the requisite configuration has been done for the communications access method, declare the communications access method to be used between a SAS/SHARE server and its clients.
An example of declaring the TCP/IP communications access method follows:
```
options comamid=tcp;
```
Start the server, assigning it the name that you just configured. An example of starting a server named SHARE1 follows:
```
proc server id=share1;
run;
```
The following message appears in the server SAS log with a default time stamp:
```
18Feb1999:09:47:30.000 SAS server SHARE1 started.
```

The SAS/SHARE server is now available for SAS clients and other clients to use.

CAUTION:: Be aware of these limitations to the fast-track approach to starting a server. Server security was not addressed. It may be possible for a client that accesses the server to have the same privilege to access data as the server does. Also, any SAS client that can access the server can manage the server with PROC OPERATE statements. Thus, such a client can stop the server or stop access to any library through the server. For details about server and library security, see Server Security.
If you run a server SAS session interactively, the SAS session assumes that you can resolve any problems that it encounters by using a requestor window. While the SAS session waits for a response to its query, the server may not be able to continue to service client requests until the query is answered. However, you might not be aware that a response is required if the window in which the server is running is not visible or is not being monitored. Therefore, it is recommended that you specify the SAS system option NOTERMINAL so that SAS does not display requestor windows, and it handles the situation without prompting.

Chapter Contents
Previous
Next
Top of Page