BASEstartm Open DAS
for
Modicon®
on OpenVMStm
Installation and User's
Guide
Appendix A
I/O Error Messages
This appendix contains returned values and associated error messages
for the low level I/O routines.
allocerror, An error occurred when allocating an OpenVMS port,
Explanation: Error. An error occurred when allocating
an OpenVMS port. The allocation is done when a connection is initiated
with the VMD.
User Action: An error message detailing the error
should have been logged. Examine the error to determine the proper
corrective action.
allocstatus, Status for port XX returned from SYS$ALLOC, XX,
Explanation: Error. An error occurred when allocating
a port.
User Action: Examine the error message to determine
the cause of the error and take appropriate action based on the error
message.
assignerror, An error occurred when assigning a channel to an OpenVMS
port,
Explanation: Error. An error occurred when assigning a
channel to an OpenVMS port. The assignment is done when a connection is
initiated with the VMD.
User Action: An error message detailing the error
should have been logged. Examine the error to determine the proper
corrective action.
assignstatus, Status for port XX returned from SYS$ASSIGN, XX,
Explanation: Error. An error occurred when assigning a
channel.
User Action: Examine the error message to determine
the cause of the error and take appropriate action based on the error
message.
connecterror, Error connecting to Internet address,
Explanation: Error. An error occurred when attempting
to connect to an Internet address.
User Action: Examine the log file (BASEstar Open) or
stderr to determine the error that occurred. Then take corrective
action based on the error that was found.
dataoverrun, Data overrun occurred on the line,
Explanation: Error. A data overrun occurred on the
line.
User Action: Use a slower baud rate or switch to a
port that has faster hardware.
dont, TELNET server refused to allow TELNET option,
Explanation: Error. The TELNET server responded with
"DON'T" to a request, "WILL", for the requested TELNET option.
User Action: Enable the apropriate option on the
TELNET server or substitute a server that supports requested option.
dontdobin, TELNET server refused to allow binary data reception,
Explanation: Error. The TELNET server responded with
"DON'T" to a request, "WILL", for the host to send binary data (TELNET
option RFC 856).
User Action: Enable binary mode transmission on the
TELNET server or substitute a server that supports binary mode
transmission/reception.
econnrefused, The attempt to connect was rejected for port XX,
Explanation: Error. An attempt to connect resulted was
rejected by the remote server.
User Action: If using TELNET, check the terminal
server to ensure that the listener port has been properly configured
and enabled.
ehostunreach, No route to host is present for port XX,
Explanation: Error. An attempt to connect to a TELNET
port resulted in an unreachable status being returned.
User Action: Make sure that the IP address and port
number are properly defined and that a gateway is defined on the host.
enetunreach, No route to the network or host is present for port XX,
Explanation: Error. An attempt to connect to a TELNET
port resulted in an unreachable status being returned.
User Action: Make sure that the IP address and port
number are properly defined and that a gateway is defined on the host.
etimedout, Connection timed out for port XX,
Explanation: Error. An attempt to connect to a port or
socket timed out.
User Action: If using LAT, make sure that the port is
defined in the LAT Control Program and that noone else is using the
port. Then attempt to reconnect to the port. If using TELNET, make sure
that the IP address and port number are defined properly on the
terminal server and that the listener port is enabled. Also ensure that
a gateway is defined if the host and the terminal server are not on the
same subnet.
getdvistatus, Status for port XX returned from SYS$GETDVI, XX,
Explanation: Error. An error occurred when getting
device information.
User Action: Examine the error message and the port
definition to determine the cause of the error and take appropriate
action based on the error message.
inaddrerror, Error when converting an Internet address to binary form,
Explanation: Error. An error occurred when convertng
an Internet address
User Action: Examine the Internet address to determine
the error and then correct the Internet address.
invalidport, An invalid port definition was specified,
Explanation: Error. A port definition that was defined
in ODS is not valid. Either the port is not a valid TT type device or
device characteristics could not be obtained for the port.
User Action: Examine the log file (BASEstar) or stderr
to determine the error status and the function which detected the
error. Take action based on the error message.
invalidspeed, An invalid baud rate was specified,
Explanation: Error. A baud rate that was defined in
ODS is not valid.
User Action: Check the documentation to determine
valid baud rates for the hardware platform being used. Then modify the
baud rate in ODS to a valid value.
latcode, Status for port XX returned from SYS$QIOW (IO$_TTY_PORT |
IO$M_LT_CONNECT) = X,
Explanation: Error. An error occurred when connecting
to a LAT port.
User Action: Examine the error code to determine the
cause of the error and take appropriate action based on the error code.
laterror, An error occurred when connecting to a LAT port,
Explanation: Error. An error occurred when connecting
to a LAT port. The connection is done when a connection is initiated
with the VMD.
User Action: An error message detailing the error
should have been logged. Examine the error to determine the proper
corrective action.
latmodeminv, Invalid attempt to enable modem signals on a LAT port,
Explanation: Error. LAT ports do not support setting
of the "modem" ODS parameter to "TRUE".
User Action: Change the port to a non-LAT port or
change the "modem" parameter to "FALSE", "0" or "OFF".
latstatus, Status for port XX returned from SYS$QIOW (IO$_TTY_PORT |
IO$M_LT_CONNECT), XX,
Explanation: Error. An error occurred when connecting
to a LAT port.
User Action: Examine the error message to determine
the cause of the error and take appropriate action based on the error
message.
negfailed, TELNET option negotiation failed,
Explanation: Error. An I/O error occurred when
attempting to negotiate TELNET options.
User Action: Examine the log file (BASEstar Open) or
stderr to determine the cause of the error and then take corrective
action based on the error found.
noalttypeahead, "/ALTYPEAHD" must be specified for the given port,
Explanation: Error. The DAS requires that /ALTYPEAHD
be specified for the port that is being used to communicate to the
device. ALTYPEAHD helps to ensure that characters transmitted by the
device are not lost when the host is busy.
User Action: Use DCL to "SET TERM/PERM/ALTYPEAHD
port_name" on the port being used to communicate to the device(s).
nolicense, No software license,
Explanation: Error. The DAS requires a software
license.
User Action: Install the license PAK for the DAS.
parity, Parity error,
Explanation: Error. A parity error occurred on the
port.
User Action: Check parity of the device and make sure
it matches of the host. (LAT and TELNET parity is set in the terminal
server.) If parity is set correctly, then verify that all cabling is
grounded and terminated properly.
portsyncerror, Unable to change file descriptor to blocking,
Explanation: Error. An error occurred when using
ioctl() to place a file descriptor in blocking mode.
User Action: Examine the log file (BASEstar Open) or
stderr to determine the error and then take corrective action based on
the error found.
portsyncstatus, Unable to change file descriptor to blocking for port
XX, errno = X,
Explanation: Error. An error occurred when using
ioctl() to place a file descriptor in blocking mode.
User Action: Look up the error and then take
corrective action based on the error found.
portsyntax, Improper syntax for intenet address,
Explanation: Error. There is an error in the syntax of
the port address.
User Action: Check the syntax of the address and
correct it to be a well formed internet address.
recverror, Read (recv) error occurred on the port,
Explanation: Error. An error was found when reading
from the port. Examine the log file (BASEstar Open) or stderr to
determine the errno returned by the read.
User Action: Examine the log file (BASEstar Open) or
stderr to determine the errno returned by the recv call. Then take
action based on the error found.
recvstatus, Read (recv) error on port XX, errno = X,
Explanation: Error. An error was found when reading
from the port. The error number for the error is given in the message.
User Action: Look up the error and take action based
on the error found.
socketerror, Error in obtaining a socket for port,
Explanation: Error. An error was found when issuing a
'socket' call to obtain a socket for a TCP/IP connection.
User Action: Examine the log file (BASEstar Open) or
stderr to determine the errno returned by the socket call. Then take
action based on the error found.
socketstatus, Error in obtaining a socket for port XX, errno = X,
Explanation: Error. An error was found when issuing a
'socket' call to obtain a socket for a TCP/IP connection.
User Action: Look up the error and take action based
on the error found.
telnetiac, TELNET command XX received on port XX,
Explanation: Error. A TELNET command was received when
in binary mode. In binary mode no TELNET commands are expected.
User Action: No user action should be necessary. The
DAS will abort the connection and reset binary mode when it reconnects.
ttbreakerror, An error occurred when sending a break to a port,
Explanation: Error. An error was returned when sending
a break to the port.
User Action: Examine the log file (BASEstar Open) or
stderr to determine the error that occurred. Then take action based on
the error found.
ttcharerror, An error occurred when defining TT characteristics,
Explanation: Error. An error occurred when setting up
TT characteristics. The TT characteristics are set when a connection is
initiated with the VMD.
User Action: An error message detailing the error
should have been logged. Examine the error to determine the proper
corrective action.
ucxseterror, Error returned from SYS$QIO - IO$_SETMODE,
Explanation: Error. An error occurred when attempting
to set the socket address. This UCX call is equivalent to the C Socket
socket ().
User Action: Examine the log file (BASEstar Open) or
stderr to determine the error that occurred. Then take corrective
action based on the error that was found.
ucxsetstatus, Status for port XX returned from SYS$QIO - IO$_SETMODE,
XX,
Explanation: Error. An error occurred when attempting
to set the socket address. This UCX call is equivalent to the C Socket
socket ().
User Action: Examine the error status and look up the
error to determine the cause and corrective action to take.
unexpectiac, An unexpected "IAC" was received while in TELNET binary
mode,
Explanation: Error. An "IAC" (Is A command) character
was received after a TELNET line was negotiated to transmit and receive
in binary mode. In binary mode, the only expected TELNET control
command is the IAC character itself.
User Action: No action should be necessary. The DAS
will abort the connection if this should occur and then attempt to
renegotiate binary transmission/reception when reconnecting.
vmsconnectstatus, Status for port XX returned from SYS$QIO -
IO$_ACCESS, XX,
Explanation: Error. An error occurred when attempting
to connect to an Internet address. This UCX call is equivalent to the C
connect ().
User Action: Look up the error status to determine the
error that occurred. Then take corrective action based on the error
that was found.
vmsreaderror, QIO read error on port,
Explanation: Error. An error was found when reading
from an OpenVMS port. Examine the log file (BASEstar Open) or stderr to
determine the status returned by the read.
User Action: Look up the error and take action based
on the error found.
vmsreadstatus, QIO read error on port XX, XX,
Explanation: Error. An error occurred when reading
data from an OpenVMS port.
User Action: Examine the error message and take
corrective action based on the error message.
vmsrecverror, Error returned from SYS$QIO - IO$_READVBLK,
Explanation: Error. An error was found when reading
from the port. This UCX call is equivalent to the C Socket recv ().
User Action: Examine the log file (BASEstar Open) or
stderr to determine the error that occurred. Then take action based on
the error found.
vmsrecvstatus, Status for port XX:X returned from SYS$QIO -
IO$_READVBLK, XX,
Explanation: Error. An error was found when reading
from the port. This UCX call is equivalent to the C Socket recv ().
User Action: Look up the error status to determine the
error that occurred. Then take corrective action based on the error
that was found.
vmsttbreakstatus, Status for port XX returned from SYS$QIO -
IO$_SETMODE, XX,
Explanation: Error. An error was returned when sending
a break to the port.
User Action: Look up the error status to determine the
error that occurred. Then take corrective action based on the error
that was found.
vmsttcharstatus, Status for port XX returned from SYS$QIOW
(IO$_SETMODE), XX,
Explanation: Error. An error occurred when setting
port characteristics.
User Action: Look up the error number to determine the
cause of the error and take appropriate action based on the error code.
wont, TELNET server refused to accept TELNET option,
Explanation: Error. The TELNET server responded with
"WON'T" to a request, "DO", for the requested TELNET option.
User Action: Enable the apropriate option on the
TELNET server or substitute a server that supports the requested option.
wontdobin, TELNET server refused to send binary data,
Explanation: Error. The TELNET server responded with
"WON'T" to a request, "DO", for the server to send binary data (TELNET
option RFC 856).
User Action: Enable binary mode transmission on the
TELNET server or substitute a server that supports binary mode
transmission/reception.
wrongdevice, An invalid device type was detected for a port,
Explanation: Error. A device type other than a
terminal was detected for the indicated port.
User Action: Modify the ODS port definition to use a
valid TT type device.