Chapter Contents


SAS/CONNECT User's Guide

Protocol Gateway

The protocol gateway service connects two SAS sessions that do not use a common communications access method in a networked environment. A network comprises one or more logical domains, each of which maps a topological area according to the communications protocol or access method that it supports.

A SAS session can communicate with any other SAS session that runs in the same logical domain because both sessions use the same access method. Furthermore, SAS sessions from different logical domains can communicate by means of the DOMAIN server if at least one domain supports multiple access methods (one of which must be used in both domains). The DOMAIN server eliminates the need to configure multiple protocols in a given domain.

The DOMAIN server provides the gateway that allows communication between SAS sessions that are running in different logical domains, as illustrated in the following figure.

Protocol Gateway Service with DOMAIN Server


All sessions in both domains can intercommunicate by using the DOMAIN server's set of common access methods. A message flows over the originator's native access method to the DOMAIN server. This access method is called the inbound access method. The server re-directs a message to the cross-domain destination by using the destination's native access method. Conversely, the outbound access method is the access method that is used on the target host side of the protocol gateway.

System Requirements

The DOMAIN server requires a dedicated SAS session that runs in an OS/2 or in a Windows NT environment.

Using the Protocol Gateway

To connect two SAS sessions when using the protocol gateway of the DOMAIN server, you must initialize the DOMAIN server and specify the inbound and outbound communication access methods for the DOMAIN server. For the TCP/IP outbound access method, sign-on scripts must be specified for the DOMAIN server.

Note:   If you use the TCP/IP access method, you may need to configure the DOMAIN server in the SERVICES file.   [cautionend]

In addition, you must set macro variables at the SAS/CONNECT local host or at the SAS/SHARE client to identify the DOMAIN server node name and the server identifier and to provide DOMAIN server security for connecting local hosts or clients. The macro variables that are set are based on the inbound access method that is used.

You must also specify the remote host that you are connecting to, the local host, and the security environment variables that will be used for the userid and password of the target host. The DOMAIN server supplies the specified value to the outbound access method, which negotiates security with the target host.

For more information about configuring and using the DOMAIN server, see Communications Access Methods for SAS/CONNECT and SAS/SHARE Software.


The PROTOCOL option in the PROC DOMAIN statement is used to create the DOMAIN server DOMSVR using the TCP/IP access method. The COMAMID, COMAUX1 and COMAUX2 options should be specified on the command line or in your configuration file.

The macro variable GWHOST stores the fully qualified TCP/IP node name of the DOMAIN server STAR.XYZ.ABC and has the userid BASS and the password TIME2GO.

proc domain protocol serverid=domsrv;

Submit the following statements from the SAS/CONNECT local host:

%let TCPSEC=bass.time2go;

options comamid=tcp remote=RMTNODE;

Chapter Contents



Top of Page

Copyright 1999 by SAS Institute Inc., Cary, NC, USA. All rights reserved.