NetIPC 3000/XL Programmer's Reference Manual (5958-8600)
Table Of Contents
- 1 NetIPC Fundamentals
- 2 Cross-System NetIPC
- 3 NetIPC Intrinsics
- 4 NetIPC Examples
- A IPC Interpreter (IPCINT)
- B Cause and Diagnostic Codes
- C ErrorMessages
- D Migration From PTOP to NetIPC and RPM
- E C Program Language Considerations
Appendix C 193
Error Messages
NetIPC Errors
44 MESSAGE: NO RESPONSE FROM REMOTE REGISTRY SERVER.
CAUSE: No reply was received from the remote registry process. This is
often due to the remote node not having initialized its transport.
ACTION: Contact your operator. If unable to resolve the problem, see
“Submitting an SR” at the end of this appendix.
46 MESSAGE: UNABLE TO INTERPRET RECEIVED PATH REPORT.
CAUSE: Unable to interpret the information returned by the remote
socket registry process regarding the looked-up socket.
ACTION: See “Submitting an SR” at the end of this appendix.
47 MESSAGE: INVALID MESSAGE RECEIVED FROM REMOTE SERVER.
CAUSE: The message received from the remote registry process does not
appear to be a valid socket registry message.
ACTION: See “Submitting an SR” at the end of this appendix.
50 MESSAGE: INVALID DATA LENGTH.
CAUSE: Specified data length parameter is too long or negative.
ACTION: Check and modify the value.
51 MESSAGE: INVALID DESTINATION DESCRIPTOR.
CAUSE: Supplied destination descriptor value is not that of a valid
destination descriptor.
ACTION: Verify that you are passing an active destination descriptor.
52 MESSAGE: SOURCE AND DESTINATION SOCKET PROTOCOL
MISMATCH.
CAUSE: The source socket is not of the same protocol as the socket
described by the destination descriptor.
ACTION: Validate that you are using the correct destination descriptor.
Make certain both processes have agreed on the same protocol.
Determine the correct socket was looked up.
53 MESSAGE: SOURCE AND DESTINATION SOCKET TYPE MISMATCH.
CAUSE: The source socket cannot be used for communication with the
socket described by the destination descriptor.
ACTION: Validate that you are using the correct destination descriptor.
Make certain both processes have agreed on the same method of
communication. Determine the correct socket was looked up.
54 MESSAGE: INVALID CALL SOCKET DESCRIPTOR.
CAUSE: Specified descriptor is not for a call socket.
ACTION: Validate the value being passed.