Configuring the rc.spds File

Here is an example of a typical unmodified rc.spds file:

     #!/bin/sh -x
     # Sample startup script for SPDS.
     # This script starts the SPDS Name Server
     # data server and ODBC server processes
     # using assumed install directories. Most
     # paths are controlled through shell variables
     # defined at the beginning of the script.
     # If you change this script, copy it to
     # the SPDS site directory and modify that
     # copy just to make sure that a subsequent
     # SPDS software upgrade doesn't wipe out
     # your site modifications to the script.
     #------------------------------------------
     #
     # Define some primary variables. INSTDIR is the
     # root directory of your installation.  INSTDIR is
     # initialized to run rc.spds from the site dir
     # of your installation.
     #
     # NSPORT is the SPDS name server listen port;
     #        if omitted uses "spdsname" service entry.
     # SNSPORT is the SPDS ODBC server listen port;
     #        if omitted uses "spdssnet" service entry.
     #
     # If you are running through a firewall the NSPORT and
     # SNSPORT must be surfaced through the firewall.  In
     # addition, the SPDS server listen port and operator port
     # must be surfaced through the firewall. If you are not
     # running through a firewall allow the server to choose
     # these ports.
     #
     # SRVLPORT is the SPDS server listen port;
     #        leave as 0 if NOT running through a firewall.
     #
     # SRVOPORT is the SPDS server operator port;
     #        leave as 0 if NOT running through a firewall.
     #
     # Refer to the SPDS Admin Doc section on Security for
     # more information on running SPDS through a firewall.
     #
     NSPORT=5190
     SNSPORT=5191
     SRVLPORT=0
     SRVOPORT=0
     INSTDIR=<InstallDir>
     PARMDIR=$INSTDIR/site
     ACLDIR=$INSTDIR/site
     LICFILE=<SASHOME>/licenses/<SPD License File>

The following sections describe the configuration changes that you might want to make in the rc.spds file.

The rc.spds script assumes that you want to start the SNET Server (spdssnet) to support OBDC, JDBC, or htmSQL access to SPD Server data stores. If this is not what you want, you can delete or comment out the following lines near the bottom of the rc.spds script.

# Startup the spdssnet server. This server supports
# ODBC access to SPDS data. Note the
# only parameter is the optional spdssnet listen
# port number. If not explicitly specified it
# will default to the "spdssnet" service in /etc/services
#

/bin/sleep 2
if [ -z "$SNSPORT" ]; then
   spdssnet 1>$SNSLOG 2>&1 &
else
   spdssnet -listenport $SNSPORT 1>$SNSLOG 2>&1 &

The rc.spds script assumes that you are running SPD Server concurrently with an SPD Server 3.x environment. The script also assumes that the SPD Server name server and the SNET Server will run using explicit port number assignments. The following lines at the beginning of rc.spds assign the ports numbers:

NSPORT=5190  (name server port for spdsnsrv)
SNSPORT=5191 (SNET Server port for spdssnet)

If these ports are in use, or are otherwise unavailable, choose new port numbers. If you omit these assignments, rc.spds uses the name services entries SPDSNAME and SPDSSNET. If you do not run the SNET Server, you do not need to modify the SNSPORT definition.

The rc.spds script assumes that you want to keep the logs from messages written to STDOUT or STDERR of the spdsnsrv ( SPD Server name server) and spdsserv (SPD Server host) processes. The shell variable LOGDIR= defines the directory in which these logs are kept. If you do not want to keep these logs, change LOGDIR=, and the rc.spds script will use /dev/null. If you want to keep the logs in another location besides InstallDir/log, change LOGDIR=.

The DSRVFILE= and DSRVTIME= spdsserv options, NSRVFILE= and NSRVTIME= spdsnsrv options, and SNSFILE= and SNSTIME= spdssnet options are enabled with the following shell variables by default:

Specify the log file prefix and the log file cycle time of day to enable automatic log filename generation and cycling of the log file. The file path for the -logfile option is generated by concatenating the LOGDIR= and LOGFILE= variables. For more information about these options, see SPD Server Host Commands. When automatic log filename generation and cycling are enabled, the only messages that are sent to the default log file are those written to STDERR. If you want to disable automatic log filename generation and cycling, change the settings to empty pointers, such as the DSRVFILE= and DSRVTIME= options.

The LOGFILE= and LOGTIME= spdsserv options are enabled by default with the following shell variables:

These settings enable automatic log filename generation and cycling by specifying the log file prefix and the log file cycle time of day. The file path for the -logfile option is generated by concatenating the LOGDIR= and LOGFILE= variables. For more information about these options, see SPD Server Host Commands. When automatic log filename generation and cycling are enabled, the only messages that go to the InstallDir/log/spdsserv.log file are those written to STDERR. If you want to disable automatic log filename generation and cycling, change the settings to empty pointers.

The rc.spds script enables you to use the SPD Server audit file facility, but the audit file facility is not enabled by default. Use the following shell variables to configure the SPD Server audit file facility:

When AUDDIR= and AUDFILE= are set, proxy audit file creation is enabled. When AUDDIR= and AUDFILESQL= are set, SQL audit file creation is enabled. If AUDTIME= is set, automatic audit file cycling occurs at the specified time of day. For more information about the audit file facility, see SPD Server Host Commands.

The rc.spds script assumes that you keep your spdsserv.parm parameter file and your SPD Server user password file in the InstallDir/site directory. If you do not keep the files in this location, you need to change the ACLDIR= and PARMDIR= assignments. You can include this script into your system start-up file so that it is executed as part of starting the system. Otherwise, the SPD Server administrator must manually start SPD Server after the system starts.