z/OS: TCP/IP Access Method

SAS/CONNECT Error Messages under z/OS

For TCP/IP, if SAS/CONNECT is unable to connect to the TCP/IP port, the following system message appears:

connection
                           refused

The connection might fail at sign-on 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 the same time.

Under z/OS, use the NETSTAT utility to show active sockets and to show who is waiting for a socket.

SAS/SHARE Error Messages under z/OS

No
                           TCP service server-id on
                           this host

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

Cannot
                           locate TCP host host name

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 that has the same name, there might be a conflict with another software application. Please contact your system administrator.

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

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

Cannot
                           locate TCP host node

The node that is 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 the Server for information about two-level server names.