Communications Access Methods for SAS/CONNECT and SAS/SHARE Software

CMS: TCP/IP Access Method

SAS/CONNECT

For TCP/IP, SAS/CONNECT may be unable to connect to the TCP/IP port. The following system message appears:

connection refused

The connection may fail at SIGNON for the following reasons:

The remote side is not listening.
The packet sequence is out of order, which can indicate that the routers are not working properly.
The maximum number of connections has been reached.
There is a flow problem, which indicates that too many packets are being sent to the remote side at once.

SAS/SHARE

No TCP service <server-id> on this host

The service specified in the SERVERID= option is not one of the SAS/SHARE TCP/IP service names that are defined in the TCP services file.

Cannot locate TCP host <node>

The TCP/IP software is probably not running on the server's node.

Cannot bind TCP socket.
System message is 'address already in use'

Another server with the same name is already running on this node, or another TCP/IP application is using the predefined port numbers that the TCP/IP access method is trying to use. If another server of the same name is running, choose one of the other defined server names. If there is no other server running with the same name, this may indicate a conflict with another software package. Please contact your system administration personnel.

Cannot connect to TCP socket.
System message is 'connection refused'

The server specified by the SERVER= option cannot be located on the specified node.

Cannot locate TCP host <node>

The node specified in a two-level name is not known to the TCP/IP software, or the TCP/IP software is not running on the user's node. See Specifying a Server Name for information on two-level server names.

Chapter Contents
Previous
Next
Top of Page