Appendix C Error Messages

CAUSE: UNABLE TO INTERPRET RECEIVED PATH REPORT — Unable to find an X.25 address to call from the remote node name given.

ACTION: Check consistency between configuration file and network directory. In order to map the node name to the X.25 address, both the address key and the IP address are used.

CAUSE: EXCEEDED PROTOCOL MODULE'S SOCKET LIMIT. — All call socket entries in the X.25 internal tables are in use.

ACTION: Remember to release call sockets when no IPCCONNECT and IPCRECVCN are expected.

CAUSE: All connection entries in X.25 internal tables are in use.

ACTION: Remember to shut the VC's that are no longer in use.

CAUSE: CONNECTION ABORTED BY LOCAL PROTOCOL MODULE. — Greater than 30,000 bytes of data was received in a single message.

ACTION: Alter the remote application program to send smaller messages.

CAUSE: The inactivity timer has timed out.

ACTION: Shutdown the connection before re-opening it.

CAUSE: CONNECTION FAILURE DETECTED. — A clear packet has been received. The remote system or network aborted the connection.

ACTION: Retrieve the cause/diagnostic field with IPCCONTROL (to examine the cause), and issue IPCSHUTDOWN on the virtual circuit.

CAUSE: ADDRESS CURRENTLY IN USE BY ANOTHER SOCKET. — The requested protocol relative address is already used by another process through another IPCCREATE call.

ACTION: Use another protocol relative address or wait for previous process to release its call socket.

CAUSE: TRANSPORT IS GOING DOWN. — A NETCONTROL STOP command has been issued. All connections have been aborted.

ACTION: Issue an IPCSHUTDOWN on all call sockets and virtual circuit sockets.

CAUSE: DESTINATION UNREACHABLE. — Outgoing access not allowed. The destination X.25 address is either not configured in the SVC path table or the security flags do not allow outbound calls to this address. It could also be a problem with the network directory.

ACTION: Check the configuration of SVC path table security and the network directory.

CAUSE: ATTEMPT TO ESTABLISH CONNECTION FAILED. — A connection could not be opened between the XL node and the DTC.

ACTION: Issue IPCSHUTDOWN on the virtual circuit, check the DTC XNA card is working, and re-issue IPCCONNECT.

CAUSE: PROTOCOL MODULE DOES NOT HAVE SUFFICIENT ­RESOURCES — The protocol module has run out of buffers.

ACTION: Try again later. Reduce network load by closing some connections or increase the number of buffers in the configuration.

CAUSE: INVALID CALL USER DATA OPT RECORD ENTRY — Too much call user data has been sent. The amount is determined by the "no address flag" and use of the fast select facility. The maximum call user data that can be sent is 128 bytes (with fast select).

ACTION: Send a smaller CUD, use fast select, or use the "no address" option.

CAUSE: INVALID FACILITIES SET OPT RECORD ENTRY — The facility set passed as a parameter has not been found in the internal facility set table.

ACTION: Use one of the facility sets defined in the configuration or add a new one.

CAUSE: RESET EVENT OCCURRED ON X.25 CONNECTION. — An unsolicited reset packet was received.

ACTION: Use IPCCONTROL (request 12) to examine the cause/diagnostic field. The connection is still up and operational but some data may have been lost.

CAUSE: SOCKET IS ALREADY IN USE. — A single socket per network interface can be created with the catch-all capability.

ACTION: Wait for catch-all socket to be released.

CAUSE: INTERRUPT EVENT OCCURRED ON X.25 CONNECTION. — An interrupt packet was received.

ACTION: Use IPCCONTROL (request 12) to get interrupt data. The connection is still up and operational.

CAUSE: CONNECTION REQUEST REJECTED BY REMOTE. — The outgoing call was rejected either by the local DTC, the network, the remote DTC or the remote host.

ACTION: Use IPCCONTROL (request 12) to retrieve the cause/diagnostic field. Take action depending on cause/diagnostic using table given.

CAUSE: INCOMPATIBLE WITH PROTOCOL STATE. — This connection is currently in the reset state. Either a reset was sent and the protocol is waiting for a reset confirmation, or a reset has been received.

ACTION: If you issued the reset, then wait and reissue the call later. Otherwise, issue IPCRECV> to complete an incoming reset.