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 it provides site-dependent configuration information. The command-line options for each executable are described 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 (spdsserv) host process registers LIBNAME domain information from its configuration file with its appointed name server (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 that connect 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 include automatic log filename generation and periodic log file cycling. You can periodically switch to a new name server log file without stopping and restarting SPD Server, which improves the availability of the name server.
The spdsnsrv command-line options control automatic log filename generation and cycling properties. The default rc.spds script in the samples/ directory of your SPD Server installation provides examples of spdsnsrv command-line options.
When you are 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.
Invoke the SPD Server name server by 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 on which you license SPD Server. The SPD Server administrator must enter each key into the license file. The SPD Server will not run on a machine whose valid license key has not been entered into the license file. License keys are plain text strings that include product, site, and machine information, and the password that is required for using Server in this specific environment.
-logfile fileSpec
specifies that the logger process automatically creates a server log file. fileSpec specifies a partial pathname or filename specification that is used to generate the complete log file path. For example, if you specify fileSpec as \DOWNlogs\spdsnsrv, the name \DOWNlogs\spdsnsrv_mmddyyyy_hh:mm:ss.spdslog is generated. The values mmddyyyy and hh:mm:ss indicate the time when the system created the log file.
-logtime hh:mm
specifies the time of day to cycle a new generation of the name server log file. At this time each day, the previous log file will be closed and a new log file will be 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.
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. The spdsserv command-line options control the message and audit logging functions. Message and audit logging functions include automatic log filename generation and log file cycling support. You can periodically switch to a new name server log file without stopping and restarting SPD Server, which improves the availability of the name server.
The spdsserv command-line options control automatic log filename generation cycling properties. 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 that are 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 you are 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 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.
Invoke the SPD Server host by using the following command-line syntax:
spdsserv [-option [optval]...]  
The spdsserv command supports the following options:
-acldir pwd-dir-path
specifies the directory path to the SPD Server host SPD Server password file. You can omit this option if the PASSPATH option is declared in the SPD Server host's -PARMFILE option. A valid SPD Server password file is required even when you specify 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.
-auditfile fileSpec
enables audit logging for the server and automatic audit log file creation by the audit process. fileSpec specifies a path or filename that is used to generate the complete audit file path. For example, if you specify fileSpec as /audit/spds, the generated name will be/audit/spds_mmddyyyy_hh:mm:ss.spdsaudit, where mmddyyyy is the system date when the log file was created.
-audittime hh:mm
specifies the time of day to cycle a new generation of the audit log file. At this time each day, the previous log file will be closed and a new log file will be opened.
-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 Setting Up SPD Server Libname Parameter Files .
-logfile fileSpec
specifies that the logger process automatically creates a server log file. The fileSpec value specifies a partial path or filename that is used to generate the complete log file path. For example, if you specify fileSpec as /logs/spds, the generated name will be /logs/spds mmddyyyy_hh:mm:ss.spdslog, where mmddyyyy and hh:mm:ss indicate the system time when the log file was created.
-logtime hh:mm
specifies the time of day to cycle a new generation of the server log file. At this time each day, the previous log file will be closed and a new log file will be opened.
-nameserver node-name
specifies the node name where the name server process is running. This node does not need to be the same node that is hosting the SPD Server host processes. This option is required.
-nameserverport port#
specifies an explicit TCP port number for the SPD Server host to use to connect to its name server. If you do not specify a port, the name server queries the system for a registered port address that is using the service name spdsname.
-noacl
disables SPD Server login validation for SPD Server LIBNAME engine connections to the SPD Server host.
-parmfile file-spec
specifies 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 that 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. You do not need to modify the default values in InstallDir/site/spdsserv.parm for most environments. For more information about the parameter file and setting up server parameters, see Setting Up SPD Server Parameter Files .

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 stopping and restarting SPD Server.
The default rc.spds script in the samples/ directory provides examples of the command-line options.
When you are 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 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.
Invoke the SNET Server by using 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 you do not specify a listen port number, spdssnet uses the name service spdssnet from the /etc/services file to determine its listen port.
-logfile fileSpec
specifies that the logger process automatically creates a server log file. The fileSpec value specifies a partial path or filename that is used to generate the complete log file path. For example, if you specify fileSpec as \DOWNlogs\spdssnet, the generated name will be \DOWNlogs\spdssnet_mmddyyyy_hh:mm:ss.spdslog, where mmddyyyy and hh:mm:ss indicate the system time when the log file was created.
-logtime hh:mm
specifies the time of day to cycle a new generation of the SNET log file. At this time each day, the previous log file will be closed and new log file will be opened.

Password Utility Reference

The SPD Server administrator can use the SPD Server psmgr utility to create and maintain the data set that contains the authorized SPD Server user IDs. This utility is the SPD Server analog of the UNIX user ID facility. If you choose to run SPD Server ACL support, you need to use this utility to create and populate the SPD Server password file before you start 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. For more information about SPD Server performance monitoring, see Accessing SPD Server Services in SAS Management Console.