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

Starting a Spawner on Alpha/VMS
If the spawner is to service more than one client user ID, the spawner should run under an account that has the
following privileges:
IMPERSONATE NETMBX READALL TMPMBX
These privileges are required in order for the spawner to create a detached process with the connecting client as the
owner.
If the spawner is to service one client, the spawner may be launched under that client's user ID.
Note: If you are printing or using SAS/GRAPH procedures, you must set the display to a machine running an X
server. For example:
set display/create/transport=tcpip/node=
Included as part of the Base SAS installation are some sample DCL files that demonstrate how to start the daemon as
a detached process. The files listed here are all located in SAS$ROOT:[MISC.BASE]. Make a backup copy of these
files before making any modifications.
OBJSPAWN_STARTUP.COM
executes OBJSPAWN.COM as a detached process.
OBJSPAWN.COM
runs the spawner. OBJSPAWN.COM also includes other commands that your site may need in order to run
the appropriate version of the spawner, to set the display node, to define a process level logical pointing to a
template DCL file (OBJSPAWN_TEMPLATE.COM), and perform any other actions needed before the
spawner is started.
OBJSPAWN_TEMPLATE.COM
performs setup that is needed in order for the client process to execute. The spawner first checks to see if the
logical SAS$OBJSPAWN_TEMPLATE is defined. If SAS$TKELS_TEMPLATE is defined, when the server
first starts the corresponding template file is executed as a DCL command procedure. You are not required to
define the template file.
OBJSPAWN.CFG
provides a sample configuration file for the spawner.
Note: After the spawner is started, an attempt is made to write a message to stdout indicating whether objspawn
initialization completed or failed.
IOM Bridge Servers
Starting a Spawner on Alpha/VMS 146