Starting the UNIX Spawner

Syntax: Starting the UNIX Spawner

Here is the syntax for the command to start the UNIX spawner:

sastcpd <options>

Options for the UNIX Spawner

Here are the options that can be specified with the sastcpd command. For a list of Encryption options that can also be specified on the UNIX spawner, see SAS System Options for Encryption in Encryption in SAS.

-logconfigloc file-specification

specifies the location of the XML configuration file that is used to initialize the SAS logging facility. The configuration 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. Relevant log data for the UNIX spawner might include the date and time, the log level, the thread ID, and the logger.

The file-specification that defines the location of the XML configuration file must be a valid filename or a path and filename for your operating environment. If the path contains spaces, enclose the file-specification in quotation marks.

Here is an example of the command to invoke the SAS logging facility:

spawner -logconfigloc unxspawnerlog.xml

Note: If –LOGCONFIGLOC is specified, spawner messages are routed to the App.Connect.JobSpawner logger. State messages are routed to the root logger.

See:For details about the SAS logging facility, see SAS Logging: Configuration and Programming Reference.

-nocleartext: 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.

-noinheritance: 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.

-noscript: prevents sign-on from clients that use scripts, and allows sign-on only from clients that do not use scripts.

The -noscript option is useful if you want to limit SAS start-up commands to the use of the -sascmd option. Specifying -noscript restricts clients from specifying additional options in SAS start-up commands or script files. If -noscript is used, -sascmd must also be used.

Requirement:The client must specify a user ID and a password during sign-on.

See:For details about signing on, see SIGNON Statement and Command in SAS/CONNECT User's Guide.

-xmlconfigfile fully-qualified-path: specifies a fully qualified path to the configuration file in XML format that contains the information necessary to connect to a SAS Metadata Server. For details about creating the configuration file, see the Base SAS Help for the Metadata Server Connections window.

Alias:-omrconfigfile

Requirement:If -xmlconfigfile is used, -sasspawnercn must also be used.

-sascmd "command"

specifies the SAS command or a command file that is specific to the UNIX operating environment 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.

Example:

#!/bin/ksh 
#---------------------------------- 
# mystartup #---------------------------------- 
. ~/.profile 
sas -dmr -noterminal -nosyntaxcheck -device grlink -comamid tcp $* 
#------------------------------

Note: The $* positional parameter enables you to specify additional SAS options when you invoke SAS.

-sasdaemonservice port-number | service-name: specifies the port or service that the SAS/CONNECT server uses to notify the spawner that it is ready to receive requests from SAS clients. When socket inheritance is enabled, the SAS client and the SAS/CONNECT server communicate via this port. If you use a service, it must be configured in the SERVICES file on the computer that the SAS/CONNECT server session runs on.

-sasspawnercn “CONNECT-spawner-object-name”: specifies the name of the CONNECT spawner object in the SAS Metadata Repository. A name that includes one or more spaces must be enclosed in quotation marks. For details about generating a CONNECT spawner definition for the SAS Metadata Server, see the help for the SAS/CONNECT Spawner server type in the Server Manager of SAS Management Console.

Requirement:If -sasspawnercn is used, -xmlconfigfile must also be used.

-service service-name: specifies the name of the service that the UNIX spawner program uses to listen for incoming requests. This value is identical to the service value in the REMOTE= option that the user specifies at the client at sign on. Because there is no default, you must specify this value.

The service name must also be defined in the \etc\services file at both the client and the server.

-shell: enables the SAS session that is invoked by the spawner program to create a UNIX shell, which is required in order for the server to run X commands.

Without specifying the -shell option to the UNIX spawner, X command processing is disabled, by default. For details about running X commands from your SAS session, see SAS Companion for UNIX Environments.

For an example of how to start the UNIX spawner, see Scripted Sign-on to a UNIX Spawner.

Encryption Options for the UNIX Spawner

You can also use options in the spawner invocation for encrypting SAS client/server data transfers. For more information, see SAS System Options for Encryption in Encryption in SAS. For example programs, seeEncryption Technologies: Examples in Encryption in SAS.