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

IP and TELNET Access Methods

CAUTION:: Version 6 Only Beginning with Version 7, the TELNET access method is not supported. However, information about TELNET is included here for Version 6 users.

SAS/CONNECT

For TELNET, the WAITFOR statement in the script looks for all possibilities. If no condition is met, the number of seconds that are specified to wait should be less than the amount of time allowed by the connection itself before it drops because there is no activity. If the WAITFOR statement is not set properly, the following message appears during an asynchronous SIGNON:

ERROR:  Read Error

For TELNET, if the SIGNON statement appears to hang during a SIGNON, change the EOPCHAR in the SIGNON script to LF. The default EOPCHAR is CR. CR is not recognized by some remote systems.

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.

On OS/390, use the NETSTAT utility to show active sockets and to show who is waiting on a socket.

When signing on with TCP/IP and LAN Workplace for OS/2, the following error can occur:

ERROR:  Supporting Access Method Initialization Failed.

Error recovery follows:

Ensure that the EXCELAN variable is set in the SAS configuration file. It should point to the directory that contains the LAN Workplace for OS/2 TCP/IP software.
Example:
```
set excelan=c:\lanwp
```
Verify that the HOSTS file contains the appropriate local and remote Internet addresses and node-name pairs.
Ensure that the SAS configuration file contains the HOSTNAME variable that is set to the actual local host name.

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 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 may be a conflict with another software package. Please contact your system administrator.

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 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