Chapter 5 NetIPC (SOCKERRS) Error Messages

CAUSE: No error was detected.

ACTION: None.

CAUSE: Area between S and Z registers is not sufficient for execution of the intrinsic.

ACTION: :PREP your program file with a greater MAXDATA value.

CAUSE: A specified parameter is out of bounds.

ACTION: Check all parameters to make certain they are between the user's DL and S registers. If an array is specified, make certain all of it is within bounds.

CAUSE: A :NETCONTROL was not issued to bring up the network transport.

ACTION: Notify your operator.

CAUSE: Specified socket type parameter is of an unknown value.

ACTION: Check and modify your socket type parameter.

CAUSE: Specified protocol parameter is of an unknown value.

ACTION: Check and modify protocol parameter.

CAUSE: An unsupported bit in the flags parameter was set, or a nonprivileged user set a privileged bit.

ACTION: Verify that the proper bits are specified in the flags parameter. Bit numbering is from left to right (0-31).

CAUSE: An unsupported option was specified in the opt record, or a nonprivileged user attempted to specify a privileged option.

ACTION: Check the options added to the opt record and remove or modify the option. Verify that the opt record was initialized correctly using INITOPT.

CAUSE: A NETCONTROL has not been issued to activate the requested protocol module.

ACTION: Notify your operator.

CAUSE: The type of socket you are trying to create is not supported by the protocol to be used.

ACTION: Use a different socket type or protocol.

CAUSE: Invalid option length specified or value of option is not positive.

ACTION: Correct option specification.

CAUSE: No addresses were available for dynamic allocation.

ACTION: If unsuccessful the second time, see Appendix A “Submitting an SR ” of this manual.

CAUSE: The address option in the opt record has an error in it (e.g., invalid length).

ACTION: Check the values being placed in the opt record.

CAUSE: User has already reached the limit of 64 sockets per process.

ACTION: Shut down any sockets which are not being used or have been aborted.

CAUSE: Transport's Path Cache or Path Descriptor table is full.

ACTION: Contact your operator to see if the table can be expanded.

CAUSE: NetIPC was unable to parse the specified opt record.

ACTION: Check your INITOPT and ADDOPT calls.

CAUSE: Maximum message size option in the opt record had an error associated with it (for example, too many bytes specified, invalid message size value).

ACTION: Check the values being placed in the opt record.

CAUSE: Data offset option in the opt record had an error associated with it (for example, too many bytes specified).

ACTION: Check the values being placed in the opt record.

CAUSE: The same opt record option was specified twice.

ACTION: Remove the redundant call.

CAUSE: Maximum connection requests queued option in the opt record had an error associated with it (for example, too many bytes specified, bad value).

ACTION: Check the values being placed in the opt record.

CAUSE: Error occurred attempting to initialize NetIPC, or Network Management is still initializing.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: The attempt to create a data segment failed because the DST table was full or there was not enough virtual memory.

ACTION: Contact your operator to see if these tables can be expanded.

CAUSE: A required parameter was not supplied in an option variable intrinsic call.

ACTION: Check your calling sequence.

CAUSE: Specified name length was too large or negative.

ACTION: Check your name length parameter. Shorten the name if necessary.

CAUSE: Specified descriptor is not a valid socket, connection, or destination descriptor.

ACTION: Check the value being specified.

CAUSE: The socket descriptor given in the IPCNAME call was for a VC socket; VC sockets may not be named.

ACTION: Check if the correct descriptor was specified.

CAUSE: Specified name was previously given.

ACTION: Use a different name.

CAUSE: The particular NetIPC intrinsic cannot be called from split stack.

ACTION: Recode to call the intrinsic from the stack. Vectored data may be required.

CAUSE: Name is too long or has a negative length.

ACTION: Check the name's length. Shorten the name if necessary.

CAUSE: NetIPC previously detected and reported an irrecoverable error; most likely it was initiated by the protocol module.

ACTION: The socket can no longer be used. Call IPCSHUTDOWN to clean up.

CAUSE: A socket can have only four names; the caller attempted to give it a fifth.

ACTION: Use no more than four names.

CAUSE: Socket registry or give table is full.

ACTION: Shut down unused sockets, call IPCNAMERASE on any sockets that no longer need to be looked up, or get given sockets. See Appendix A “Submitting an SR ” of this manual.

CAUSE: Name was not previously specified in an IPCNAME or IPCGIVE call; IPCNAMERASE or IPCGET was previously issued with the name; or socket no longer exists.

ACTION: Check names specified, make sure names were properly agreed on, determine if a timing problem exists.

CAUSE: Attempted to erase a name of a socket you do not own.

ACTION: Have the owner of the socket call IPCNAMERASE.

CAUSE: Syntax of the node name is invalid.

ACTION: Check the node name being supplied.

CAUSE: Unable to resolve the specified node name as an NS node name.

ACTION: Check the node name to see if it is correct. The node name may be valid but the specified node's transport may not be active.

CAUSE: User has already reached the limit of 261 destination descriptors per process.

ACTION: Call IPCSHUTDOWN on any unneeded destination descriptors.

CAUSE: Send to remote socket registry process failed. This is often caused by the fact that the PXP protocol module is not active on the local node.

ACTION: Contact your operator. If unable to resolve the problem, see Appendix A “Submitting an SR ” of this manual.

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 Appendix A “Submitting an SR ” of this manual.

CAUSE: Unable to interpret the information returned by the remote socket registry process regarding the looked-up socket.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: The message received from the remote registry process does not appear to be a valid socket registry message.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: Specified data length parameter is too long or negative.

ACTION: Check and modify the value.

CAUSE: Supplied destination descriptor value is not that of a valid destination descriptor.

ACTION: Verify that you are passing an active destination descriptor.

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.

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.

CAUSE: Specified descriptor is not for a call socket.

ACTION: Validate the value being passed.

CAUSE: Protocol module being used cannot create any more sockets.

ACTION: Contact your operator; the limit may be configurable.

CAUSE: The no wait call would block because the socket is not ready for desired operation.

ACTION: Re-initiate the call or call the select to assure socket is ready for desired operation.

CAUSE: User tried to send data too many times in nowait mode without calling IOWAIT.

ACTION: Call IOWAIT to complete a send. The limit is 7.

CAUSE: User tried to issue too many consecutive nowait receives without calling IOWAIT.

ACTION: Call IOWAIT to complete a receive. The limit is 1.

CAUSE: The socket timer popped before data was received.

ACTION: If this is not desired, call IPCCONTROL to increase or disable the timeout.

CAUSE: User has no space for allocating an Active File Table entry.

ACTION: Close unnecessary files or sockets.

CAUSE: User called IPCCONNECT without a subsequent IPCRECV before issuing the current request.

ACTION: Call IPCRECV.

CAUSE: IPCRECV called with deferred connection option. IPCCONTROL has not been called to accept/reject.

ACTION: Use the call IPCCONTROL with the accept/reject option.

CAUSE: Remote protocol module aborted the connection. This will occur when a peer has called IPCSHUTDOWN on the connection.

ACTION: Call IPCSHUTDOWN to clean up your end of the connection.

CAUSE: Local protocol module encountered some error which caused it to abort the connection.

ACTION: Call IPCSHUTDOWN to clean up your end of the connection. See Appendix A “Submitting an SR ” of this manual.

CAUSE: Supplied value is not that of a valid VC socket (connection) descriptor.

ACTION: Check the value being given.

CAUSE: An event occurred which caused the local protocol module to determine that the connection is no longer up (for example, retransmitted data was never acknowledged).

ACTION: Call IPCSHUTDOWN to clean up your end of the connection.

CAUSE: Informational message.

ACTION: Do not attempt to receive any more data.

CAUSE: Bits in the flags parameter were set which indicate requests for mutually exclusive options.

ACTION: Check and clear the appropriate bits.

CAUSE: Attempted an operation with nowait I/O outstanding.

ACTION: Call IOWAIT to complete the I/O or IPCCONTROL to abort any receives.

CAUSE: Request code is unknown or a nonprivileged user requested a privileged option.

ACTION: Validate the value being passed.

CAUSE: Unable to create an entity used for communication between NetIPC and the protocol module.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: Value specified for the timeout is negative.

ACTION: Modify the value.

CAUSE: Mode of socket cannot be used.

ACTION: Use IPCCONTROL to specify correct mode.

CAUSE: Attempted to turn off trace when tracing was not on.

ACTION: Remove the call.

CAUSE: Requested trace file name is not valid.

ACTION: Validate and modify the trace file name.

CAUSE: An error was detected in the option specifying the maximum amount of data to be traced (for example, negative value, too large, too many bytes used to specify the value).

ACTION: Modify the values being used.

CAUSE: An error was detected in the option specifying the maximum amount of records to be in the trace file (for example, negative or too large a value, too many bytes used to specify the value).

ACTION: Modify the values being used.

CAUSE: Attempted to turn on tracing when tracing already enabled.

ACTION: Remove the call or turn off trace before the call.

CAUSE: The Node Management Subsystem (NMS) was unable to enable tracing.

ACTION: Call IPCCHECK; the protocol module error returned will be the Node Management error number. Refer to the Node Management Errors (NMERR) to determine the appropriate action for the specified NMERR.

CAUSE: IPCCHECK was called, but the user had no sockets or destination descriptors, and therefore no data structure for retaining error codes.

ACTION: None, but no NetIPC or protocol module errors are available.

CAUSE: IPCERRMSG was called with an invalid NetIPC error code.

ACTION: Check the value being passed.

CAUSE: The error message catalog does not exist, it is opened exclusively, or the caller does not have access rights to the file.

ACTION: Notify your operator.

CAUSE: MAKECAT was not successfully run on the message catalog.

ACTION: Notify your operator.

CAUSE: Internal error.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: Internal error.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: Internal error.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: Internal error.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: Internal error.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: Internal error.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: Internal error.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: Attempted use of the buffer manager by NetIPC or the protocol module resulted in an error.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: Data segment index value in the vectored data array is not valid.

ACTION: Check the value being supplied.

CAUSE: The count of data in the vectored data array is invalid.

ACTION: Check the values being given.

CAUSE: More than two data locations were specified in the vectored data array.

ACTION: Limit the number to two per operation. Use multiple sends or receives if necessary.

CAUSE: Type of vectored data is unknown (must be a 0, 1, 2, or 4) or the data type is for a data segment (1 or 2) and the user is not privileged.

ACTION: Check the value being used.

CAUSE: Protocol module does not support graceful release, process tried to release connection that was not in the correct state, or output pending.

ACTION: Check command sequence.

CAUSE: User data option is not supported for IPCRECV or IPCCONNECT.

ACTION: Do not use user data option.

CAUSE: Internal error.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: Internal error.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: Address being specified for use is already being used.

ACTION: Stop application or choose a different socket address.

CAUSE: The transport is being shut down.

ACTION: If you are a privileged user trying to specify a well known address, try again later. If you are nonprivileged, then see Appendix A “Submitting an SR ” of this manual.

CAUSE: Process tried to send after initiating graceful release.

ACTION: Check command sequence.

CAUSE: Process tried to receive after remote initiated graceful release.

ACTION: Check command sequence.

CAUSE: NetIPC received a protocol module error which it was unable to map.

ACTION: Call IPCCHECK to get the protocol module error. Call IPCSHUTDOWN to clean up. See Appendix A “Submitting an SR ” of this manual.

CAUSE: An internal error was detected.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: A request was made which cannot be performed with software interrupts enabled.

ACTION: Disable software interrupts or remove the request

CAUSE: Procedure label passed when enabling software interrupts is invalid.

ACTION: Check the PLABEL you are passing.

CAUSE: Socket registry program missing.

ACTION: Contact your Hewlett-Packard representative for assistance.

CAUSE: The transport was unable to route the packet to the destination.

ACTION: Notify your operator.

CAUSE: Protocol module was unable to set up the requested connection. This may be caused by the remote protocol module not being active.

ACTION: Notify your operator.

CAUSE: NetIPC software was incompatible with the software being executed by the remote registry process.

ACTION: Notify your operator.

CAUSE: An unsupported option was specified in the opt record, or a nonprivileged user attempted to specify a privileged option.

ACTION: Check your opt record and remove or modify the option.

CAUSE: An unsupported option was specified in the opt record, or a nonprivileged user attempted to specify a privileged option.

ACTION: Check your opt record and remove or modify the option.

CAUSE: User error. Entry number of option is either negative or higher than specified in INITOPT value.

ACTION: Correct and reissue command.

CAUSE: User error. Data length for option is either negative or higher than specified in INITOPT value.

ACTION: Correct and reissue command.

CAUSE: Number of option entries is either too high or negative. Either an internal restriction or a user mistake.

ACTION: Remove the cause by making the number positive or smaller in value.

CAUSE: The option record indicates that the entry is not valid or the buffer supplied by the user was too small to hold all of the data.

ACTION: Check entry number, make sure the option record has not been written over and check output buffer length.

CAUSE: Protocol module is temporarily out of buffers or internal data descriptors.

ACTION: Retry later when the system load is lighter.

CAUSE: Invalid X.25 network name specified or not configured.

ACTION: Correct the network name or notify the operator.

CAUSE: The length of the call user data is invalid for the transport protocol type.

ACTION: Check the length of the call user data option in the opt array. The call user data opt record must be greater than 1 for IPCCONNECT and 4 for IPCRECVCN. The maximum length is protocol specific.

CAUSE: 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: The user may request the address of the calling node. Address of 8 bytes will be returned.

ACTION: The length of the option entry must be exactly 8 bytes.

CAUSE: The reason code of the option in IPCSHUTDOWN has an invalid length.

ACTION: Check the values being placed in the opt record.

CAUSE: 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: The attempt to obtain a semaphore before sending a message to the protocol module failed.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: A single socket per network interface can be created with the catch-all capability.

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

CAUSE: Invalid flag bits set in protocol specific flags option, or invalid length specified for option, or user did not have NA capability.

ACTION: Check bits set and length specified. Bit numbering is from left to right (0-31).

CAUSE: An unsolicited interrupt packet was received.

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

CAUSE: No VC configured in the configuration file.

ACTION: Check the configuration file for X.25.

CAUSE: The remote node received the connection request and rejected it.

ACTION: The call may be retried later. Otherwise, the reason for the reject must be known.

CAUSE: The D bit setting is not consistent in configuration file of local and destination node.

ACTION: Check the configuration file for X.25.

CAUSE: The user requested an operation which is not supported by the protocol module.

ACTION: Verify the sequence of intrinsic calls.

CAUSE: No PVC configured.

ACTION: Check the configuration file for X.25.

CAUSE: A connection request was issued on a PVC which is in use by another process.

ACTION: Select a different PVC or retry later.

CAUSE: Address specified in opt parameter is out of range.

ACTION: Specify an address in the range 30767 to 32767.

CAUSE: An invalid address length was specified in the opt parameter.

ACTION: The address length is 2 bytes (for non-privileged users).

CAUSE: Attempt was made to accept or reject a connection that is open or in the process of closing.

ACTION: Use flags parameter in IPCRECVCN to defer acceptance or rejection of the connection request.

CAUSE: X.25 connection was reset.

ACTION: Call IPCSHUTDOWN to clean up the connection.

CAUSE: A nodename and an IP address have both been specified in a call to IPCDEST.

ACTION: Specify either the nodename or the IP address but not both.

CAUSE: Invalid use of the fast select.

ACTION: Validate the calling sequence.

CAUSE: For IPCCONNECT, IPCRECVCN, or IPCRECV, the opt parameter facility field length is wrong.

ACTION: Check the facility field length. The length must be 1 to 109 bytes inclusive.

CAUSE: An IPCCONTROL request 9, accept the connection, cannot be performed.

ACTION: Use IPCCONTROL request 15 to reject the connection.

CAUSE: Warning message. READOPT request was for less data than available.

ACTION: Specify a greater length in READOPT.