turns on debug level output.
specifies that the spawner uses FIPS compliant encryption to protect communications. When -ENCRYPTFIPS is specified, only SSL and AES encryption algorithms are valid.
| See | ENCRYPTFIPS System Option in Encryption in SAS |
| Example | The following example enables SSL and AES encryption.“SAS-installation-directory\SASFoundation\
9.4\cntspawn.exe” –encryptfips |
specifies to print the Help message.
specifies the filename to use for spawner log output if you are not using the -LOGCONFIGLOC option. The -LOG option should not be used with the -LOGCONFIGLOC option. If both options are specified, the -LOGCONFIGLOC option takes precedence.
| Example | The following example uses the ConnectSpawner.sh script
on UNIX to start the SAS/CONNECT spawner and specifies that debug-level
log messages are sent to the unxspawner.log file.ConnectSpawner.sh -start -debug -log unxspawner.log |
enables the SAS logging facility for SAS servers and names the location of the configuration
file that is used by the SAS logging facility to create spawner log output. The configuration
file is an XML file that specifies and configures loggers
and appenders for the SAS/CONNECT spawner. The SAS Deployment
Wizard automatically creates an initial logging configuration file
for the spawner named logconfig.xml that
you can modify as needed to adjust your logging configuration. The
file is located in the sas-installation-directory/Lev-n/ConnectSpawner/ directory
on UNIX and the sas-installation-directory\Lev-n\ConnectSpawner\ directory
on Windows. The file contains the pattern layout for the messages
that are generated and automatically directed to an output device,
such as a console or a log file. Relevant log data for the Windows
spawner might include the date and time, the log level, the thread
ID, and the logger.
| Note | If -LOGCONFIGLOC is specified, spawner messages are routed by default to the App.Connect.Spawner logger. |
| See | For information about using the -LOGCONFIGLOC option in the SAS Logging Facility, see LOGCONFIGLOC= System Option in SAS Logging: Configuration and Programming Reference. |
| Example | The following spawner start-up command invokes the
SAS Logging Facility and specifies the name and location of the logging
configuration file, winspawnerlog.xml.“SAS-installation-directory\SASFoundation\
9.4\cntspawn.exe” -logconfigloc winspawnerlog.xml |
| Example | Sample SAS/CONNECT Spawner logconfig.xml File |
enables you to specify the service name or port number that will listen for operator connections. Operator connections are connections made through the operator port. The operator port is a unique port number that is used for administrative purposes.
| Range | 1- 65535 |
specifies the type of encryption algorithm to use when communicating with the metadata server. The following algorithms can be used: RC2, RC4, TripleDES, SAS Proprietary, and AES.
specifies the level of encryption when communicating with the metadata server.
specifies the password of user who is to connect to metadata server.
specifies the port to connect to on metadata server.
specifies the name or IP address of the metadata server.
specifies the user ID of the user who is to connect to metadata server.
specifies the number of bits in data encryption keys.
specifies that network encryption is required.
specifies the name of encryption algorithm.
prevents sign-ons from clients that do not support user ID and password encryption. This option prevents clients that are running older releases (prior to SAS 6.09E and SAS 6.11 TS040, which do not support user ID and password encryption) from signing on to the spawner program. However, the default permits both encrypted and plaintext user IDs and passwords.
disables socket inheritance. Socket inheritance allows SAS/CONNECT servers to use the socket connection that is established between the SAS/CONNECT client and the spawner. Socket inheritance saves resources and is easier to configure when clients connect to a server that is within a firewall. Socket inheritance is enabled by default.
prevents sign-on from clients that use scripts, and allows sign-on only from clients that do not use scripts.
specifies the SAS command or a command file that invokes SAS when a client attempts to connect to a server using the port defined by the -SERVICE command. The -SERVICE option specifies an alternate port that the spawner uses to listen for incoming requests for connection.
cd !sasroot sas.exe %*The first line changes to the directory where the SAS executable is stored. The second line starts SAS. Add options as needed at this SAS start-up command.
specifies the SAS command or a command file that starts a SAS session when you sign on without a script. If the client does not specify a script file at sign-on, the -SASCMD option must be specified when starting the spawner.
#!/bin/ksh #---------------------------------- # mystartup #---------------------------------- . ~/.profile sas -noterminal -nosyntaxcheck $* #------------------------------
specifies a UNIX System Services (USS) shell script for starting a SAS session. You must use -SASCMD and a shell script if you do not specify a sign-on script in the client session using an RLINK fileref. The script interprets the command arguments and environment variables and builds a TSO command that invokes a SAS session. For an example of a SAS start-up shell script, see Defining the Shell Script for Starting SAS.
Use the -SASCMD option to do the following
-DMR -COMAMID<access-method> -NOSPLASH -ICON -NOTERMINAL
specifies the service name or port number that the SAS/CONNECT server uses to listen for SAS child process connections. When socket inheritance is enabled, the SAS client and the SAS/CONNECT server communicate via this port. If you use a service, its name must be configured in the SERVICES file on the computer that the SAS/CONNECT server session runs on.
specifies the name of the spawner definition to retrieve from the SAS Metadata Server.
specifies the service name or port number to use to listen for client connections.
“SAS-installation-directory\SASFoundation\9.4\cntspawn.exe” -service 5020signon node-name.5020 -mgmtport 5030
| Note | If the -SERVICE option is not specified, the spawner will listen on the Telnet port (23). |
specifies that the started SAS/CONNECT servers will allow X commands.
specifies that the server requires client authentication for SSL connections.
specifies that the server check CRL for revoked digital certificates for SSL.
identifies support for the Security Support Provider Interface for single sign-on connections to the spawner. If the client and the server run under Windows and if the client does not supply a user ID and password to the server, SSPI (Security Support Provider Interface) is used to perform client authentication. SSPI authentication is disabled by default. To enable SSPI authentication, you must specify -SSPI in the spawner start-up command. In versions prior to 9.4, SSPI was enabled by default.
| Default | -NOSSPI |
turns on trace level output.
specifies the filename to use to get SAS Metadata Server access information. A path that includes one or more spaces must be enclosed in quotation marks.
| Alias | -OMRCONFIGFILE |
causes an instance of a
SAS Connect Spawner
C:\SAS>cntspawn -install
specifies the Windows service that must be started before the spawner service starts. The service-name value is the name of the dependent service that is displayed in the Microsoft Windows Services snap-in (services.msc).
| Alias | -IDEP |
specifies the description that you assign to the spawner that is installed and started as a Windows service, when you also specify the -INSTALL option.. The -SERVDESC option is valid only when installing the spawner using the -INSTALL option on the CNTSPAWN command. The description can be viewed with the services applet in Windows. A specified spawner description cannot exceed 256 characters and must be enclosed in quotation marks if it contains one or more spaces.
cntspawn -install -servicename "SAS spawner 5" -servdesc
"A SAS process that listens for requests to spawn SAS/Connect
servers"| Alias | -SERVDESC |
specifies the directory in which to run the Windows service, when you also specify the -INSTALL option.
| Alias | -SERVDIR |
specifies the name that you assign to the spawner that is installed, or uninstalled, and started as a service in the Windows operating environment. A specified name overrides the default name that is automatically assigned when the -INSTALL option is used.
cntspawn -install -servicename "Doug's spawner"cntspawn -uninstall -servicename "Doug's spawner"
| Alias | -NAME |
specifies the password for the user account that spawner will run under as a service. For details about SSL, see Encryption in SAS, located in the Base SAS Help and Documentation.
| Alias | -SERVPASS |
specifies a user name that the Windows service will run under, when you also specify the -INSTALL option. This option can be abbreviated as -SU.
| Alias | -SU, -SERVUSER |
specifies the name of the issuer of the digital certificate that SSL should use.
specifies the serial number of the digital certificate that SSL should use.
specifies the subject name of the digital certificate that SSL should use.
instructs the spawner to uninstall as a Windows service, which was previously installed and started by using the -INSTALL option.
cntspawn -uninstall -servicename "Doug's spawner"
| Alias | -DEINSTALL or -DI |
specifies the name of the file that contains the list of trusted certificate authorities.
specifies the name of the file that contains the public certificate to use for SSL.
specifies the location of CRL file.
specifies the name of the file that contains PKCS12 information to use for SSL.
specifies the password to use to decrypt the PKCS12 information.
specifies the name of the file that contains the public certificate's private key to use for SSL.
specifies the password to use to decrypt the private key, if the private key is encrypted.
<?xml version="1.0" encoding="UTF-8"?>
<logging:configuration xmlns:logging="http://www.sas.com/xml/logging/1.0/">
<!-- Rolling log file with default rollover of midnight -->
<appender class="RollingFileAppender" name="TimeBasedRollingFile">
<param name="Append" value="false"/>
<param name="Unique" value="true"/>
<param name="ImmediateFlush" value="true"/>
<rollingPolicy class="TimeBasedRollingPolicy">
<param name="FileNamePattern" value="/<SAS-configuration-directory>
/Lev<n/ConnectSpawner/Logs/
ConnectSpawner_%d_%S{hostname}_%S{pid}.log"/>
</rollingPolicy>
<layout>
<param name="HeaderPattern" value="Host: '%S{hostname}',
OS: '%S{os_family}', Release: '%S{os_release}',
Command:'%S{startup_cmd}'"/>
<param name="ConversionPattern" value="%d %-5p [%t] :%u - %m"/>
</layout>
</appender>
<!-- Unix System Facility Appender, writes to unix system log -->
<appender class="UNXFacilityAppender" name="UnixSysLog">
<filter class="RepeatMatchFilter">
<param name="AcceptOnMatch" value="false"/>
</filter>
<layout>
<param name="ConversionPattern" value="%-5p [%t] :%u - %m"/>
</layout>
</appender>
<!-- Administration message logger -->
<logger name="Admin">
<level value="Info"/>
<appender-ref ref="UnixSysLog"/>
</logger>
<!-- Application message logger -->
<logger name="App">
<level value="Trace"/>
</logger>
<!-- Audit message logger -->
<logger name="Audit">
<level value="Info"/>
</logger>
<!-- IOM protocol message logger -->
<logger name="IOM">
<level value="Info"/>
</logger>
<!-- Logging Facility logger -->
<logger name="Logging">
<level value="Error"/>
<appender-ref ref="UnixSysLog"/>
</logger>
<!-- Root logger -->
<root>
<level value="Error"/>
<appender-ref ref="TimeBasedRollingFile"/>
<!-- Caution: Do NOT edit, modify or remove the following statement. -->
<appender-ref ref="IOMServer"/>
</root>
<!-- Caution: Do NOT edit or modify the configuration information below. -->
<!-- Settings are enabled for the internal server execution environment. -->
<!-- IOM Server Appender -->
<appender class="IOMServerAppender" name="IOMServer">
<param name="MaxEntries" value="10000"/>
<layout>
<param name="ConversionPattern" value="%d %-5p [%t] %u - %m"/>
</layout>
</appender>
<!-- Event Appender -->
<appender class="IOMEventAppender" name="Events">
<param name="Scope" value="server"/>
<param name="Threshold" value="Debug"/>
<layout>
<param name="ConversionPattern" value="%d %-5p [%t] %u - %m"/>
</layout>
</appender>
<!-- Server Administration Message Logger -->
<logger name="Perf.ARM.IOM.ConnectSpawner.ServerAdministration">
<level value="Debug"/>
<appender-ref ref="Events"/>
</logger>
</logging:configuration>