Options to Start the z/OS Spawner

Options for the z/OS Spawner

In order to start the z/OS spawner, you must specify options in the PARMS file. You can specify any of the following options and any of the Encryption Options. For details about the Encryption options, see SAS System Options for Encryption in Encryption in SAS.

-help: prints a list of valid options.

-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 z/OS 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 zosspawnerlog.xml

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

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

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

See:For more information, 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. Use UNIX file-naming conventions for specifying the path. 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 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. For an example of starting the spawner, see Encrypted Sign-on to a z/OS Spawner.

-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, 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 to use 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 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 | port-number: specifies the name or TCP/IP port number of the service that the z/OS 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.

Service names and ports must be configured in the SERVICES file on both the client and server. Choose a unique port number that is in the range of 1 to 65535. For details about the SERVICES files, see Configuring the SERVICES File.

-shell: enables the SAS session that the spawner invokes to support the XCMD system option, which allows execution of TSO commands in the session. Without specifying the -SHELL option, X command processing is disabled by default. For details about running X commands from your SAS session, see the SAS Companion for z/OS.

For an example of how to start the spawner, see Encrypted Sign-on to a z/OS Spawner.

Encryption Options for the z/OS 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.