NS3000/iX Operations and Maintenance Reference Manual (36922-90042)

Chapter 2 33
Operating Your Network
Verifying Network Connections and Services
Receive failures” listed above, then your system may have hardware
link problems; see “Investigating the Link” in the NS 3000/iX Error
Messages Reference Manual.
Miscellaneous Test Errors
Certain errors may appear in all software line tests which do not fit in
the categories described above. They are listed here.
SOCKERR # MESSAGE: PCERRMSG FAILED (SOCKERR #)
CAUSE: Error message could not be acquired from the message
catalogue SOCKCAT.NET.SYS.
ACTION: Ensure that the message catalog exists. Examine errors
returned to the console before and after this error.
SOCKERR # MESSAGE: IPCSHUTDOWN FAILED
CAUSE: Socket could not be closed.
ACTION: Examine errors returned to the console before this error. Take
action for appropriate SOCKERR.
General Test Suggestions
If the following SOCKERRs appear together, then the network may be
“too busy” — that is, coordinating too many processes — to permit
proper operation of the XPVAL tests:
Error Message
REMOTE ABORTED THE CONNECTION
SOCKET TIMEOUT
and
CONNECTION REQUEST FAILED
RESPONSE TO CONNECTION FAILED
LOCAL IPCRECVCN FAILED
Wait until network activity lessens to execute the tests.
Examine the Protocol Module errors regarding the TCP entity. Protocol
Module errors are listed in the “Network Transport Protocol Errors”
table in the NS 3000/iX Error Messages Reference Manual.