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

OpenVMS: TCP/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 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 and is not recognized by some remote systems.

SAS/CONNECT and SAS/SHARE

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

connection
refused

The connection may fail at SIGNON for either of the following reasons:

The remote side is not listening.
The maximum number of connections has been reached.

SAS/SHARE

Failure to enter a server's name, a port, and an alias in the SERVICES file results in an error when you try to access the server.

The following partial SAS log shows the error message that the user receives if the server service is omitted from the SERVICES file.

36   options comamid=tcp fullstimer; 
37   %let tcpsec=_prompt_; 
38   libname sasdata 'edc.prog2.sasdata'
             server=sdcmvs.sharsrvx; 
You cannot connect to server SDCMVS.SHARSRVX because 
ERROR:  No TCP service 'sharsrvx' on this host. 
ERROR:  Error in the LIBNAME or FILENAME statement.

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 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 that has 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 that has 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. Contact your system administrator.

Chapter Contents
Previous
Next
Top of Page