SPD Server Command Reference

SPD Server operation revolves around the executable files described in the packing list. The executables are in the /bin subdirectories. Each executable supports a set of command-line options that override default features, or provides site-dependent configuration information. The command-line options for each executable are provided in the following sections:

SPD Server Name Server Commands

The SPD Server LIBNAME engine connects to the SPD Server Name Server. The Name Server resolves LIBNAME domain names into physical file system paths for librefs. The Name Server also resolves host node and end-point (TCP port) addresses for each LIBNAME. Each SPD Server host process (spdsserv process) registers LIBNAME domain information from its configuration file with its appointed Name Server process (spdsnsrv process). Multiple SPD Server hosts can use the same Name Server to register their LIBNAME domains. The only requirement is that the combination of the LIBNAME= option values from the SPD Server host's LIBNAME configuration file must be unique across all SPD Server hosts connecting to the Name Server.
Part of the function of the Name Server process is to start an SPD Server logging process. The spdslog process performs message logging functions. Message logging functions are controlled using spdsnsrv command-line options. Message logging functions include automatic log filename generation and periodic log file cycling.
The spdsnsrv command-line options control automatic log filename generation and cycling properties. Name Server availability improves performance because you can periodically switch to a new Name Server log file without halting and restarting SPD Server. The default rc.spds script in the samples/ directory of your SPD Server installation provides examples of spdsnsrv command-line options.
When using automatic log filename generation and cycling, remember to periodically clean the log files. Proper log file maintenance includes archiving logs using secondary or long-term storage.
Many users retain only a few generations of log files for quick reference. A shell script that runs on a regular basis (such as CRONTAB) is a good way to perform log maintenance on your server machine.
The SPD Server Name Server is invoked using the following command-line syntax:
spdsnsrv [-option [optval]...]  
The spdsnsrv command supports the following options:
-listenport port#
Specifies the explicit TCP port number that the Name Server uses to accept connections from the SPD Server LIBNAME engine and its SPD Server hosts. If no port is specified, the Name Server queries the system for port addresses using the service name spdsname. If no such service has been registered, SPD Server chooses a dynamic port number for the Name Server to use.
-licensefile lic-file
License file keys are generated by SAS and provided to you. With this release of SPD Server, you receive an SPD Server license key for each machine where you license SPD Server. Each key must be entered into the license file by the SPD Server administrator. The SPD Server will not run on a machine without first entering a valid license key in the license file. License keys are plain text strings with product, site, and machine information along with the password that is required to use Server in this specific environment.
-logfile fileSpec
Selects automatic server log file creation by the logger process. fileSpec specifies a partial pathname or filename specification that is used to generate the complete log file path. For example, if you specified fileSpec as \DOWNlogs\spdsnsrv, the generated name would appear:\DOWNlogs\spdsnsrv_mmddyyyy_hh:mm:ss.spdslog, where mmddyyyy and hh:mm:ss are taken from the system time when the log file is created.
-logtime hh:mm
Specifies a time of day to cycle a new generation of the Name Server log file. At this time each day, the previous log file is closed and a new log file is opened.

SPD Server Host Commands

The SPD Server LIBNAME engine connects to the SPD Server host to access data in the server environment. The SPD Server host uses the SPD Server password file to validate each SPD Server user, and then creates a LIBNAME proxy process on behalf of each of them.
The SPD Server host is invoked using the following command-line syntax:
spdsserv [-option [optval]...]  
Part of the function of the SPD Server host process is to start SPD Server logging processes. The spdslog process performs message logging functions. The spdsaud process performs audit logging functions. Message and audit logging functions are controlled using spdsserv command-line options.
Both message and audit logging facilities include automatic log filename generation and periodic log file cycling support. The spdsserv command-line options control automatic log filename generation cycling properties. Server availability improves because you can periodically switch to a new server log and audit log without halting and restarting SPD Server. The default rc.spds script shipped in the samples/ directory of your SPD Server installation provides examples of the command-line options.
Audit log records are kept for all resources accessed by each LIBNAME proxy process. The audit log saves records in its own separate space, away from other server log files. A sample SAS job that processes the audit log and generates a report is provided. Check samples/audit.sas for information about processing the audit log and generating the report. To enable the audit log, use the spdsserv command with the -AUDITFILE option.
When using automatic server log cycling or audit log cycling, remember to periodically clean the log files. Proper log file maintenance includes archiving logs using secondary or long-term storage.
Many users only retain a few generations of log files for quick reference. A shell script that runs on a regular basis (such as CRONTAB) is a good way to perform log maintenance on your server machine.
The spdsserv command supports the following options:
-parmfile file-spec
Allows you to specify an explicit file path for the SPD Server host's parameter file. This file is mandatory and contains any SPD Server options. If this option is omitted, the SPD Server host assumes a parameter file named spdsserv.parm is in the process's current working directory. Option declarations in this file are of the following form:
Option[ = Value];
The recognized -PARMFILE option names are listed, but full descriptions are available only in online documentation. Most sites do not need to modify the default values in InstallDir/site/spdsserv.parm. For more information about the parameter file, see "Setting Up SPD Server Parameter Files" in the SAS Scalable Performance Data (SPD) Server 4.5: User's Guide.For more information about setting up server parameters, seeIntroduction.
-acldir pwd-dir-path
Specifies the directory path to the SPD Server host SPD Server password file. This option can be omitted if the PASSPATH option is declared in the SPD Server host's -PARMFILE option. A valid SPD Server password file is required even when running with the -NOACL option. You must use the SPD Server psmgr utility to create the password file and to populate it with the set of valid SPD Server user IDs.
-noacl
Disables SPD Server login validation for SPD Server LIBNAME engine connections to the SPD Server host.
-nameserver node-name
Specifies the node name where the Name Server process is running. This does not need to be the same node that is hosting the SPD Server host processes. This option is required.
-nameserverport port#
Allows you to specify an explicit TCP port number for the SPD Server host to use to connect to its Name Server. If no port is specified, the Name Server queries the system for a registered port address using the service name spdsname.
-libnamefile file-spec
Specifies the name of the file that contains the logical LIBNAME domain definitions that the SPD Server host supports. LIBNAME definitions can span multiple lines and must begin with the LIBNAME=name keyword. For more information about SPD Server LIBNAME parameter files, see Introduction.
-logfile fileSpec
Selects automatic server log file creation by the logger process. fileSpec specifies a partial path or filename specification that is used to generate the complete log file path. For example, if you specified fileSpec as /logs/spds, the generated name would appear as: /logs/spds mmddyyyy_hh:mm:ss.spdslog, where mmddyyyy and hh:mm:ss are taken from the system time when the log file is created.
-logtime hh:mm
Specifies a time of day to cycle a new generation of the server log file. At this time each day, the previous log file is closed and new log file is opened.
-auditfile fileSpec
Enables audit logging for the server and automatic audit log file creation by the audit process. fileSpec specifies a path or filename specification that is used to generate the complete audit file path. For example, if you specified fileSpec as /audit/spds, the generated name would appear as:
/audit/spds_mmddyyyy_yyyy.spdsaudit, where mmddyyyy is taken
                              from the system date when the log file is created.
                           
-audittime hh:mm
Specifies a time of day to cycle a new generation of the audit log file. At this time each day, the previous log file is closed and new log file is opened.

SNET Server Commands

The SNET Server is the connection point for clients accessing SPD Server data through ODBC, JDBC, or htmSQL applications.
Part of the function of the SPD Server SNET process is to perform SPD Server logging. The spdslog process manages SPD Server message logging functions. You configure SPD Server message logging functions using spdssnet command-line options.
Message logging facilities include automatic log filename generation and periodic log file cycling support. SNET server availability improves because you can periodically switch to a new Name Server log file without halting and restarting SPD Server.
The default rc.spds script in the samples/ directory provides examples of the command-line options.
When using automatic SNET server log cycling, remember to periodically clean the log files. Proper log file maintenance includes archiving logs using secondary or long-term storage.
Many users only retain a few generations of log files for quick reference. A shell script that runs on a regular basis (such as CRONTAB) is a good way to perform log maintenance on your server machine.
The SNET Server is invoked with the following command-line syntax:
spdssnet [-listenport listen_port]
The spdssnet command supports the following options:
-listenport listen_port
Specifies the listen port number that spdssnet uses to accept connections from ODBC, JDBC, or htmSQL clients. If no listen port number is specified, spdssnet uses the name service spdssnet from the /etc/services file to determine its listen port.
-logfile fileSpec
Selects automatic server log file creation by the logger process. fileSpec specifies a partial path or filename specification that is used to generate the complete log file path. For example, if you specified fileSpec as \DOWNlogs\spdssnet, the generated name would appear as
\DOWNlogs\spdssnet_mmddyyyy_hh:mm:ss.spdslog
, where mmddyyyy and hh:mm:ss are taken from the system time when the log file is created.
-logtime hh:mm
Specifies a time of day to cycle a new generation of the SNET log file. At this time each day, the previous log file is closed and new log file is opened.

Password Utility Reference

The SPD Server psmgr utility allows the SPD Server administrator to create and maintain the data set containing the authorized SPD Server user IDs. This is the SPD Server analog of the normal UNIX user ID facility. If you choose to run SPD Server ACL support, you need to create and populate the SPD Server password file using this utility before starting the SPD Server. For more information about the Password Manager utility, see The Password Manager Utility psmgr.

Performance Server Reference

The SPD Performance Server is available to monitor and log the activity of the SPD Server processes. The SAS Management Console SPD Server Manager can connect to the Performance Server to provide real-time feedback about the SPD Server process activity.
For more information about SPD Server performance monitoring, see Accessing the SPD Manager in SAS Management Console.