OpenVMS Spawner

Starting the OpenVMS Spawner

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

SASTCPD <options>

options can be any of the following:

-HELP

prints a list of valid parameters.

-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 OpenVMS 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 vmsspawnerlog.xml

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 (before SAS 6.09E and 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.

This option requires that the client specify a user ID and a password during sign-on. For details, see the SIGNON statement in the SAS/CONNECT User's Guide.

-NOSCRIPT can be 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.

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

If -XMLCONFIGFILE is used, -SASSPAWNERCN must also be used.

Alias:

-OMRCONFIGFILE

-SASCMD "command"

specifies the SAS command or a command file that is specific to the OpenVMS operating environment and 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. For example:

sastcpd -service sasjob -sascmd "@mystartup.com"

The MYSTARTUP file contains these lines, which start SAS in an OpenVMS environment:

$!
$! mystartup
$!
sas /DMR/NOTERMINAL/NOSYNTAXCHECK/COMAMID=TCP
$ exit

-SASDAEMONSERVICE port-number | service-name

specifies the port or a 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, its name 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, see the help for the SAS/CONNECT Spawner server type in the Server Manager of SAS Management Console.

If -SASSPAWNERCN is used, -XMLCONFIGFILE must also be used.

-SERVICE service-name

specifies the name of the service that the spawner 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 before sign-on. Because there is no default, you must specify this value.

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

-SHELL

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

Without specifying the -SHELL option to the OpenVMS spawner, X command processing is disabled, by default. For details about running X commands from your SAS session, see SAS Companion for OpenVMS on HP Integrity Servers.

-NETENCRYPT

specifies whether a SAS client/server data transfer is encrypted.

-NETENCRYPTALGORITHM

specifies the encryption algorithm for SAS client/server data transfers. Only SASProprietary is supported for OpenVMS operating environments.

For an example of how to start a spawner, see Spawner Connection Examples.

Top of Page