227
Results Storage Area Response Codes Section 8-6
Network Relay Errors For network relay errors using SEND(090) or RECV(098), check the path of
the command using the routing tables and the nature of the error using the
response code to eliminate the cause of the error.
For network relay errors using CMND(490), the location of the relay error is
recorded in the second through third words of the response, as shown below.
8-6 Results Storage Area Response Codes
The response codes stored in the Results Storage Area can be used to trou-
bleshoot socket service problems. Refer to Socket Services Parameter Area 1
to 8 (Ethernet Unit to CPU Unit) on page 88 for the location of the response
codes stored in the Results Storage Area.
The UNIX socket service error messages corresponding to the response
codes are given in the following table. Refer to the documentation for the
devices involved when communicating between an Ethernet Unit and other
devices.
7Bit 6 5 4 3 2 1 0
1
First byte
Command code
7 6 5 4 3 2 1 0
Second byte
First word
7 654 3 2 1 0
1: PLC non-fatal error flag
1: PLC fatal error flag
Relay error flag
1
7 6 5 4 3 2 1 0
S-b-response code (SRES)
Second word
Main response code (MRES)
7 654 3 2 1 0
1
7 6 5 4 3 2 1 0
Error node address
Third word
Error network address
Response
code
UNIX error
message
Description Probable remedy
0003 ESRCH No such process Close the local socket and try reopening it.
0006 ENXIO No such device or address
0009 EBADF Bad file number (incorrect socket
specification)
000D EACCES Permission denied
(Broadcast address specified for
remote IP address for active TCP
open)
Check the IP address of the remote node and
try to reconnect.
000E EFAULT Bad address (copy failed between
kernel and user area)
Close the local socket and try reopening it.
0011 EEXIST File exists
0016 EINVAL Invalid argument (socket library
argument error)
0018 EMFILE Too many open files (More than 32
sockets)
0020 EPIPE Broken pipe (remote node closed
socket)
Close the local socket.
003C EPROTONO-
SUPPORT
Protocol not supported (protocol
other than UDP, TCP, or RAW speci-
fied)
Close the local socket and try reopening it.
003D EPROTOTYPE Protocol wrong type for socket
003E ENOBUFS No buffer space available There is too much load (traffic) on the Ethernet
Unit. Check your user applications.
