27.12.2013 Views

SAS® Integration Technologies: Administrator's Guide (LDAP Version)

SAS® Integration Technologies: Administrator's Guide (LDAP Version)

SAS® Integration Technologies: Administrator's Guide (LDAP Version)

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

For a list of all of the available options, refer to the Attributes for Spawner and Attributes for Server. In general,<br />

simple procedures work best. Any option can become the source of problems, so include only the options that you<br />

need.<br />

After you have created the STC procedure, you can start the object spawner by issuing an operator command:<br />

Define the Object Spawner System Security Configuration<br />

The z/OS system considers the object spawner a daemon process. Therefore, if the BPX.DAEMON profile of the<br />

RACF Facility class is active and RACF program control is enabled, then the SAS and SAS/C load libraries specified<br />

in the STC procedure must be program controlled. However, the userid under which the object spawner runs does not<br />

require RACF READ access to the BPX.DAEMON profile.<br />

If the following messages appear in the z/OS system log when a client attempts to connect, then a necessary library is<br />

not program controlled.<br />

ICH420I PROGRAM program−name [FROM LIBRARY dsname]<br />

CAUSED THE ENVIRONMENT TO BECOME UNCONTROLLED.<br />

BPXP014I ENVIRONMENT MUST BE CONTROLLED FOR DAEMON (BPX.DAEMON)<br />

PROCESSING<br />

Start the Object Spawner<br />

START OBJSPAWN<br />

<strong>SAS®</strong> <strong>Integration</strong> <strong>Technologies</strong>: <strong>Administrator's</strong> <strong>Guide</strong> (<strong>LDAP</strong> <strong>Version</strong>)<br />

For a list of all available spawner invocation options, see Spawner Invocation Options. If there are no configuration<br />

errors, the object spawner will assume a listening state by entering a detected wait state (DW).<br />

Task 3: Create a SAS Startup Command<br />

Create the Startup Command<br />

The startup command is meant to build a parameter string that is capable of launching SAS. The startup command in<br />

the spawner configuration must end with '−−' to indicate the end of the user specified parameters. Here is a sample<br />

shell script (startsas.sh):<br />

#!/bin/sh<br />

#<br />

# foundDashDash is a boolean. When TRUE,<br />

# we found the string "−−" in our arguments.<br />

#<br />

foundDashDash=0<br />

#<br />

# Construct our arguments<br />

#<br />

args=''<br />

for arg in "$@" ; do<br />

if [ "$arg" != "−−" ]; then<br />

tmp="$arg ";<br />

else<br />

tmp="SRVOPTS(''";<br />

Configuring and Starting the Object Spawner on z/OS 136

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!