|SAS/SHARE User's Guide|
You must perform the following steps to create the server environment on an OpenVMS host:
|Setting SAS System Performance Options|
The following SAS system options can be used to tune server performance:
For SAS/SHARE, setting the value of the BUFNO= option too high may hurt performance by using too much memory because SAS/SHARE may be accessing multiple files at once.
Under OpenVMS, there is no maximum number of buffers you can allocate, except for memory constraints. However, it is unusual to specify more than 10. See All Hosts: Setting SAS System Performance Options for more information about the BUFNO= option.
Under OpenVMS, the value of the BUFSIZE= option can range from 0 to the host maximum. The value is always rounded up to the next multiple of 512 bytes. If the value is 0, the engine picks a value based on the size of the observation.
You may want to vary the value of the BUFSIZE= option if you are trying to maximize memory usage or the number of observations per page. See All Hosts: Setting SAS System Performance Options for more information about the BUFSIZE= option.
Note: The overhead that is incurred by the UNBUFLOG option may degrade
the performance of a busy server.
A typical SAS configuration file follows:
bufno=2 bufsize=65024 unbuflog
See SAS Companion for the OpenVMS Operating Environment for more information about these SAS system options.
|Creating a Command File for the Server|
The command file performs any necessary process setup and invokes the SAS System. The SAS System runs a SAS program that contains any setup that is needed for the server environment and then runs the PROC SERVER statement. See Starting and Managing a SAS/SHARE Server for details about how to write a SAS program to start a server.
Use the following syntax to create a command file for a server:
$set noon $! $ SAS /ALTLOG=SYS$OUTPUT /ALTPRINT=SYS$OUTPUT /COMAMID=access-method sas-input-file $! $exit
How the logical name SYS$OUTPUT is defined depends on how the command file is executed. See Executing the Command File for the Server for this information.
|Executing the Command File for the Server|
You can execute the command file for a server in one of two ways:
Use the SUBMIT command to start the server during start-up of your OpenVMS system or start a server by executing a command.
Because of its nature, a server typically runs in a detached process. Rather than execute the RUN command directly during system start-up or at other times, you should execute the RUN command in a batch command file that you submit with the SUBMIT/USER= command. This ensures that the server is created with appropriate privileges and file access authority. The SUBMIT/USER= command requires the CMKRNL privilege.
The syntax of the SUBMIT command is
|$ SUBMIT/USER=user-name batch-filename|
$ RUN /DETACHED - /AUTHORIZE - /INPUT=command-input-file - /OUTPUT=command-output-file - /ERROR=error-file - /PROCESS_NAME=process-name - /SYS$SYSTEM:LOGINOUT.EXE
Note: This file must also contain device or directory specifications.
If the file does not contain these specifications, then the detached process
Note: This file must also
contain device or directory specifications. If the file does not contain these
specifications, then the detached process may fail.
file must also contain device or directory specifications. If the file does
not contain these specifications, then the detached process may fail.
Use this method to start the server automatically when the first client accesses it. The advantage of this method is that you do not have to explicitly start the server. However, the disadvantage is that this method causes the first LIBNAME statement or the first PROC OPERATE statement that accesses the server to operate more slowly than it would with an explicitly started server. Notify users of the server's delayed response to these statements.
Use the Network Control Program (NCP) syntax to declare the server as a known object. For example,
|NCP> DEFINE OBJECT server-name NUMBER 0 USER user-name -|
|_PASSWORD user-password FILE full-filename-specification -|
When you use this method to execute the command file for the server, the logical name SYS$OUTPUT is defined to the file SYS$LOGIN:NETSERVER.LOG.
It is possible to have the DECnet network automatically start the object without first issuing the NCP DEFINE command, but this method is not recommended for starting a server. Instead, you should use the NCP DEFINE command to automatically start the server. For more information about automatically starting a server without using the NCP DEFINE command, contact SAS Institute Technical Support.
Top of Page
Copyright 1999 by SAS Institute Inc., Cary, NC, USA. All rights reserved.