| OpenVMS: TCP/IP Access Method |
| Task List |
Configure the OpenVMS spawner service.
Start the OpenVMS spawner at the server.
Note: If the OpenVMS spawner is not being used, there are no server
tasks. ![[cautionend]](../../../../common/61991/HTML/default/images/cautend.gif)
Note: SAS/CONNECT enables TCP/IP connections from clients outside a
firewall to spawners that run on servers inside a firewall. For details, see Configuring SAS/CONNECT for Use with a Firewall. ![[cautionend]](../../../../common/61991/HTML/default/images/cautend.gif)
| Configuring the OpenVMS Spawner Service |
To enable clients to connect to an OpenVMS server by using the OpenVMS spawner, configure the spawner service in the SERVICES file at the server. For details, seeConfiguring the SERVICES File.
| Starting the OpenVMS Spawner |
You must start the OpenVMS spawner on an OpenVMS server to enable clients to connect to it. The spawner program resides on a server and listens for SAS/CONNECT client requests for connection to the server. After the spawner program receives a request, it starts a server session. For details, see OpenVMS Spawner.
If encryption has been configured at the server, set the appropriate encryption options when starting the spawner.
| SAS/CONNECT Server Example |
The following command starts the spawner VMSSPAWN on an OpenVMS computer. The absence of the -SASCMD option in the spawner start-up command implies that the client will use a script to specify the SAS command that starts SAS on the OpenVMS computer.
!sasroot/utilities/bin/sastcpd -service vmsspawn
Copyright © 2008 by SAS Institute Inc., Cary, NC, USA. All rights reserved.