HP 3000 Manuals HP 3000 Manuals
Chapter 5 NetIPC (SOCKERRS) Error Messages
NetIPC are (32-bit) integers that are returned in the result parameter of
NetIPC intrinsics when the intrinsic execution fails. (A result of 0
indicates that the intrinsic succeeded.) In addition, both NetIPC errors
and Transport Protocol errors are returned in the IPCCHECK intrinsic:
NetIPC errors in the ipcerr parameter and Transport Protocol errors in
the pmerr parameter.
0 MESSAGE SUCCESSFUL COMPLETION.
CAUSE No error was detected.
ACTION None.
1 MESSAGE INSUFFICIENT STACK SPACE.
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.
3 MESSAGE PARAMETER BOUNDS VIOLATION.
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.
4 MESSAGE TRANSPORT HAS NOT BEEN INITIALIZED.
CAUSE A :NETCONTROL was not issued to bring up the
network transport.
ACTION Notify your operator.
5 MESSAGE INVALID SOCKET TYPE.
CAUSE Specified socket type parameter is of an unknown
value.
ACTION Check and modify your socket type parameter.
6 MESSAGE INVALID PROTOCOL.
CAUSE Specified protocol parameter is of an unknown
value.
ACTION Check and modify protocol parameter.
7 MESSAGE ERROR DETECTED IN flags 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).
8 MESSAGE INVALID OPTION IN THE opt RECORD.
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.
9 MESSAGE PROTOCOL IS NOT ACTIVE.
CAUSE A NETCONTROL has not been issued to activate the
requested protocol module.
ACTION Notify your operator.
10 MESSAGE PROTOCOL DOES NOT SUPPORT THE SPECIFIED SOCKET
TYPE.
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.
12 MESSAGE ERROR DETECTED WITH MAXIMUM MESSAGES QUEUED
OPTION.
CAUSE Invalid option length specified or value of
option is not positive.
ACTION Correct option specification.
13 MESSAGE UNABLE TO ALLOCATE AN ADDRESS.
CAUSE No addresses were available for dynamic
allocation.
ACTION If unsuccessful the second time, see "Submitting
an SR" in appendix A of this manual.
14 MESSAGE ADDRESS OPTION ERROR.
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.
15 MESSAGE ATTEMPT TO EXCEED LIMIT OF SOCKETS PER PROCESS.
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.
16 MESSAGE OUT OF PATH DESCRIPTORS OR PATH DESCRIPTOR
EXTENSIONS.
CAUSE Transport's Path Cache or Path Descriptor table
is full.
ACTION Contact your operator to see if the table can be
expanded.
18 MESSAGE FORMAT OF THE opt RECORD IS INCORRECT.
CAUSE NetIPC was unable to parse the specified opt
record.
ACTION Check your INITOPT and ADDOPT calls.
19 MESSAGE ERROR DETECTED WITH MAXIMUM MESSAGE SIZE OPTION.
CAUSE Maximum message size option in the opt record
had an error associated with it (e.g., too many
bytes specified, invalid message size value).
ACTION Check the values being placed in the opt record.
20 MESSAGE ERROR WITH DATA OFFSET OPTION.
CAUSE Data offset option in the opt record had an
error associated with it (e.g., too many bytes
specified).
ACTION Check the values being placed in the opt record.
21 MESSAGE DUPLICATE opt RECORD OPTION SPECIFIED.
CAUSE The same opt record option was specified twice.
ACTION Remove the redundant call.
24 MESSAGE ERROR DETECTED IN MAXIMUM CONNECTION REQUESTS
QUEUED OPTION.
CAUSE Maximum connection requests queued option in the
opt record had an error associated with it
(e.g., too many bytes specified, bad value).
ACTION Check the values being placed in the opt record.
25 MESSAGE SOCKETS NOT INITIALIZED; NO GLOBAL DATA SEGMENT.
CAUSE Error occurred attempting to initialize NetIPC,
or Network Management is still initializing.
ACTION See "Submitting an SR" in appendix A of this
manual.
26 MESSAGE UNABLE TO ALLOCATE A DATA SEGMENT.
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.
27 MESSAGE REQUIRED PARAMETER NOT SPECIFIED.
CAUSE A required parameter was not supplied in an
option variable intrinsic call.
ACTION Check your calling sequence.
28 MESSAGE INVALID NAME LENGTH.
CAUSE Specified name length was too large or negative.
ACTION Check your name length parameter. Shorten the
name if necessary.
29 MESSAGE INVALID DESCRIPTOR.
CAUSE Specified descriptor is not a valid socket,
connection, or destination descriptor.
ACTION Check the value being specified.
30 MESSAGE UNABLE TO NAME CONNECTION SOCKETS.
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.
31 MESSAGE DUPLICATE NAME.
CAUSE Specified name was previously given.
ACTION Use a different name.
32 MESSAGE NOT CALLABLE IN SPLIT STACK.
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.
33 MESSAGE INVALID NAME.
CAUSE Name is too long or has a negative length.
ACTION Check the name's length. Shorten the name if
necessary.
34 MESSAGE CRITICAL ERROR PREVIOUSLY REPORTED; MUST
SHUTDOWN SOCKET.
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.
35 MESSAGE ATTEMPT TO EXCEED LIMIT OF NAMES PER SOCKET.
CAUSE A socket can have only four names; the caller
attempted to give it a fifth.
ACTION Use no more than four names.
36 MESSAGE TABLE OF NAMES IS FULL.
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 "Submitting an SR" in
appendix A of this manual.
37 MESSAGE NAME NOT FOUND.
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.
38 MESSAGE USER DOES NOT OWN THE SOCKET.
CAUSE Attempted to erase a name of a socket you do not
own.
ACTION Have the owner of the socket call IPCNAMERASE.
39 MESSAGE INVALID NODE NAME SYNTAX.
CAUSE Syntax of the node name is invalid.
ACTION Check the node name being supplied.
40 MESSAGE UNKNOWN NODE.
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.
41 MESSAGE ATTEMPT TO EXCEED PROCESS LIMIT OF DESTINATION
DESCRIPTORS.
CAUSE User has already reached the limit of 261
destination descriptors per process.
ACTION Call IPCSHUTDOWN on any unneeded destination
descriptors.
43 MESSAGE UNABLE TO CONTACT THE REMOTE REGISTRY SERVER.
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 "Submitting an SR" in appendix A of
this manual.
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" in appendix A of
this manual.
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" in appendix A of this
manual.
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" in appendix A of this
manual.
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.
55 MESSAGE EXCEEDED PROTOCOL MODULE'S SOCKET LIMIT.
CAUSE Protocol module being used cannot create any
more sockets.
ACTION Contact your operator; the limit may be
configurable.
56 MESSAGE CALL WOULD BLOCK WHILE USING SELECT ASYNCHRONOUS
NODE.
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.
57 MESSAGE ATTEMPT TO EXCEED LIMIT OF NOWAIT SENDS
OUTSTANDING.
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.
58 MESSAGE ATTEMPT TO EXCEED LIMIT OF NOWAIT RECEIVES
OUTSTANDING.
CAUSE User tried to issue too many consecutive nowait
receives without calling IOWAIT.
ACTION Call IOWAIT to complete a receive. The limit is
1.
59 MESSAGE SOCKET TIMEOUT.
CAUSE The socket timer popped before data was
received.
ACTION If this is not desired, call IPCCONTROL to
increase or disable the timeout.
60 MESSAGE UNABLE TO ALLOCATE AN AFT.
CAUSE User has no space for allocating an Active File
Table entry.
ACTION Close unnecessary files or sockets.
62 MESSAGE CONNECTION REQUEST PENDING; CALL IPCRECV TO
COMPLETE.
CAUSE User called IPCCONNECT without a subsequent
IPCRECV before issuing the current request.
ACTION Call IPCRECV.
63 MESSAGE WAITING CONFIRMATION; CALL IPCCONTROL TO
ACCEPT/REJECT.
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.
64 MESSAGE REMOTE ABORTED THE CONNECTION.
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.
65 MESSAGE CONNECTION ABORTED BY LOCAL PROTOCOL MODULE.
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 "Submitting an SR" in appendix
A of this manual.
66 MESSAGE INVALID CONNECTION DESCRIPTOR.
CAUSE Supplied value is not that of a valid VC socket
(connection) descriptor.
ACTION Check the value being given.
67 MESSAGE CONNECTION FAILURE DETECTED.
CAUSE An event occurred which caused the local
protocol module to determine that the connection
is no longer up (e.g., retransmitted data was
never acknowledged).
ACTION Call IPCSHUTDOWN to clean up your end of the
connection.
68 MESSAGE RECEIVED A GRACEFUL RELEASE OF THE CONNECTION.
CAUSE Informational message.
ACTION Do not attempt to receive any more data.
69 MESSAGE MUTUALLY EXCLUSIVE flags OPTIONS SPECIFIED.
CAUSE Bits in the flags parameter were set which
indicate requests for mutually exclusive
options.
ACTION Check and clear the appropriate bits.
71 MESSAGE I/O OUTSTANDING.
CAUSE Attempted an operation with nowait I/O
outstanding.
ACTION Call IOWAIT to complete the I/O or IPCCONTROL to
abort any receives.
74 MESSAGE INVALID IPCCONTROL REQUEST CODE.
CAUSE Request code is unknown or a nonprivileged user
requested a privileged option.
ACTION Validate the value being passed.
75 MESSAGE UNABLE TO CREATE A PORT FOR LOW LEVEL I/O.
CAUSE Unable to create an entity used for
communication between NetIPC and the protocol
module.
ACTION See "Submitting an SR" in appendix A of this
manual.
76 MESSAGE INVALID TIMEOUT VALUE.
CAUSE Value specified for the timeout is negative.
ACTION Modify the value.
77 MESSAGE INVALID WAIT/NOWAIT MODE.
CAUSE Mode of socket cannot be used.
ACTION Use IPCCONTROL to specify correct mode.
78 MESSAGE TRACING NOT ENABLED.
CAUSE Attempted to turn off trace when tracing was not
on.
ACTION Remove the call.
79 MESSAGE INVALID TRACE FILE NAME.
CAUSE Requested trace file name is not valid.
ACTION Validate and modify the trace file name.
80 MESSAGE ERROR IN TRACE DATA LENGTH OPTION.
CAUSE An error was detected in the option specifying
the maximum amount of data to be traced (e.g.,
negative value, too large, too many bytes used
to specify the value).
ACTION Modify the values being used.
81 MESSAGE ERROR IN NUMBER OF TRACE FILE RECORDS OPTION.
CAUSE An error was detected in the option specifying
the maximum amount of records to be in the trace
file (e.g., negative or too large a value, too
many bytes used to specify the value).
ACTION Modify the values being used.
82 MESSAGE TRACING ALREADY ENABLED.
CAUSE Attempted to turn on tracing when tracing
already enabled.
ACTION Remove the call or turn off trace before the
call.
83 MESSAGE ATTEMPT TO TURN ON TRACE FAILED.
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.
84 MESSAGE PROCESS HAS NO LOCAL SOCKET DATA STRUCTURES.
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.
85 MESSAGE INVALID SOCKET ERROR NUMBER.
CAUSE IPCERRMSG was called with an invalid NetIPC
error code.
ACTION Check the value being passed.
86 MESSAGE UNABLE TO OPEN ERROR CATALOG SOCKCAT.NET.SYS.
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.
87 MESSAGE GENMESSAGE FAILURE; NOT A MESSAGE CATALOG.
CAUSE MAKECAT was not successfully run on the message
catalog.
ACTION Notify your operator.
88 MESSAGE INVALID REQUEST SOCKET DESCRIPTOR
CAUSE Internal error
ACTION See "Submitting an SR" in appendix A of this
manual.
89 MESSAGE INVALID REPLY SOCKET DESCRIPTOR
CAUSE Internal error.
ACTION See "Submitting an SR" in appendix A of this
manual.
91 MESSAGE WOULD EXCEED LIMIT OF REPLIES EXPECTED
CAUSE Internal error.
ACTION See "Submitting an SR" in appendix A of this
manual.
92 MESSAGE MUST REPLY TO BEFORE RECEIVING ANOTHER REQUEST.
CAUSE Internal error.
ACTION See "Submitting an SR" in appendix A of this
manual.
93 MESSAGE INVALID SEQUENCE NUMBER
CAUSE Internal error.
ACTION See "Submitting an SR" in appendix A of this
manual.
94 MESSAGE NO OUTSTANDING REQUESTS.
CAUSE Internal error.
ACTION See "Submitting an SR" in appendix A of this
manual.
95 MESSAGE RECEIVED AN UNSOLICITED REPLY.
CAUSE Internal error.
ACTION See "Submitting an SR" in appendix A of this
manual.
96 MESSAGE INTERNAL BUFFER MANAGER ERROR.
CAUSE Attempted use of the buffer manager by NetIPC or
the protocol module resulted in an error.
ACTION See "Submitting an SR" in appendix A of this
manual.
98 MESSAGE INVALID DATA SEGMENT INDEX IN VECTORED DATA.
CAUSE Data segment index value in the vectored data
array is not valid.
ACTION Check the value being supplied.
99 MESSAGE INVALID BYTE COUNT IN VECTORED DATA.
CAUSE The count of data in the vectored data array is
invalid.
ACTION Check the values being given.
100 MESSAGE TOO MANY VECTORED DATA DESCRIPTORS.
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.
101 MESSAGE INVALID VECTORED DATA TYPE.
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.
102 MESSAGE UNABLE TO GRACEFULLY RELEASE THE CONNECTION
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.
103 MESSAGE USER DATA NOT SUPPORTED DURING CONNECTION
ESTABLISHMENT.
CAUSE User data option is not supported for IPCRECV or
IPCCONNECT.
ACTION Do not use user data option.
104 MESSAGE CAN'T NAME A REQUEST SOCKET
CAUSE Internal error.
ACTION See "Submitting an SR" in appendix A of this
manual.
105 MESSAGE NO REPLY RECEIVED.
CAUSE Internal error.
ACTION See "Submitting an SR" in appendix A of this
manual.
106 MESSAGE ADDRESS CURRENTLY IN USE BY ANOTHER SOCKET.
CAUSE Address being specified for use is already being
used.
ACTION If you are a privileged user trying to specify a
well known address, try again later. If you are
nonprivileged, then see "Submitting an SR" in
appendix A of this manual.
107 MESSAGE TRANSPORT IS GOING DOWN.
CAUSE The transport is being shut down.
ACTION Call IPCSHUTDOWN on all sockets and destination
descriptors.
108 MESSAGE USER HAS RELEASED CONNECTION; UNABLE TO SEND
DATA.
CAUSE Process tried to send after initiating a
graceful release.
ACTION Check command sequence.
109 MESSAGE PEER HAD RELEASED THE CONNECTION; UNABLE TO
RECEIVE DATA.
CAUSE Process tried to receive after remote initiated
graceful release.
ACTION Check command sequence.
110 MESSAGE UNANTICIPATED ERROR.
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 "Submitting
an SR" in appendix A of this manual.
111 MESSAGE INTERNAL SOFTWARE ERROR DETECTED.
CAUSE An internal error was detected.
ACTION See "Submitting an SR" in appendix A of this
manual.
112 MESSAGE NOT PERMITTED WITH SOFTWARE INTERRUPTS ENABLED.
CAUSE A request was made which cannot be performed
with software interrupts enabled.
ACTION Disable software interrupts or remove the
request.
113 MESSAGE INVALID SOFTWARE INTERRUPT PROCEDURE LABEL.
CAUSE Procedure label passed when enabling software
interrupts is invalid.
ACTION Check the PLABEL you are passing.
114 MESSAGE CREATION OF SOCKET REGISTRY PROCESS FAILED.
CAUSE Socket registry program missing.
ACTION Contact your Hewlett-Packard representative for
assistance.
116 MESSAGE DESTINATION UNREACHABLE.
CAUSE The transport was unable to route the packet to
the destination.
ACTION Notify your operator.
117 MESSAGE ATTEMPT TO ESTABLISH CONNECTION FAILED.
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.
118 MESSAGE INCOMPATIBLE VERSION.
CAUSE NetIPC software was incompatible with the
software being executed by the remote registry
process.
ACTION Notify your operator.
119 MESSAGE ERROR IN BURST SIZE 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.
120 MESSAGE ERROR IN WINDOW UPDATE THRESHOLD 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.
124 MESSAGE ENTRY NUMBER NOT VALID FOR SPECIFIED OPT RECORD.
CAUSE User error. Entry number of option is either
negative or higher than specified in INITOPT
value.
ACTION Correct and reissue command.
125 MESSAGE INVALID OPTION DATA LENGTH.
CAUSE User error. Data length for option is either
negative or higher than specified in INITOPT
value.
ACTION Correct and reissue command.
126 MESSAGE INVALID NUMBER OF EVENTUAL OPT RECORD ENTRIES.
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.
127 MESSAGE UNABLE TO READ ENTRY FROM OPT RECORD.
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.
131 MESSAGE PROTOCOL MODULE DOES NOT HAVE SUFFICIENT
RESOURCES.
CAUSE Protocol module is temporarily out of buffers or
internal data descriptors.
ACTION Retry later when the system load is lighter.
141 MESSAGE X.25 NETWORK NAME INCORRECTLY SPECIFIED
CAUSE Invalid X.25 network name specified or not
configured.
ACTION Correct the network name or notify the operator.
142 MESSAGE INVALID CALL USER DATA OPT RECORD ENTRY.
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.
143 MESSAGE INVALID FACILITIES SET OPT RECORD ENTRY
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.
144 MESSAGE INVALID CALLING NODE OPT ENTRY.
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.
145 MESSAGE INVALID REASON CODE ENTRY.
CAUSE The reason code of the option in IPCSHUTDOWN has
an invalid length.
ACTION Check the values being placed in the opt record.
146 MESSAGE RESET EVENT OCCURRED ON X.25 CONNECTION
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.
151 MESSAGE COULD NOT OBTAIN A SEMAPHORE.
CAUSE The attempt to obtain a semaphore before sending
a message to the protocol module failed.
ACTION See "Submitting an SR" in appendix A of this
manual.
153 MESSAGE SOCKET IS ALREADY IN USE.
CAUSE A single socket per network interface can be
created with the catch-all capability.
ACTION Wait for catch-all socket to be released.
155 MESSAGE INVALID X.25 FLAGS OPT RECORD ENTRY.
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).
156 MESSAGE INTERRUPT EVENT OCCURRED ON X.25 CONNECTION
CAUSE An unsolicited interrupt packet was received.
ACTION Use IPCCONTROL (request 12) to get interrupt
data. The connection is still up and
operational.
157 MESSAGE NO VIRTUAL CIRCUIT CONFIGURED.
CAUSE No VC configured in the configuration file.
ACTION Check the configuration file for X.25.
158 MESSAGE CONNECTION REQUEST REJECTED BY REMOTE.
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.
159 MESSAGE INVALID X.25 D BIT SETTING.
CAUSE The D bit setting is not consistent in
configuration file of local and destination
node.
ACTION Check the configuration file for X.25.
160 MESSAGE INCOMPATIBLE WITH PROTOCOL STATE.
CAUSE The user requested an operation which is not
supported by the protocol module.
ACTION Verify the sequence of intrinsic calls.
162 MESSAGE X.25 PERMANENT VIRTUAL CIRCUIT DOES NOT EXIST.
CAUSE No PVC configured.
ACTION Check the configuration file for X.25.
163 MESSAGE PERMANENT VIRTUAL CIRCUIT ALREADY ESTABLISHED.
CAUSE A connection request was issued on a PVC which
is in use by another process.
ACTION Select a different PVC or retry later.
164 MESSAGE ADDRESS VALUE IS OUT OF RANGE.
CAUSE Address specified in opt parameter is out of
range.
ACTION Specify an address in the range 30767 to 32767.
165 MESSAGE INVALID ADDRESS LENGTH.
CAUSE An invalid address length was specified in the
opt parameter.
ACTION The address length is 2 bytes (for
non-privileged users).
166 MESSAGE CONNECTION NOT IN VIRTUAL CIRCUIT WAIT CONFIRM
STATE.
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.
168 MESSAGE RESTART EVENT OCCURRED ON X.25 CONNECTION.
CAUSE X.25 connection was reset.
ACTION Call IPCSHUTDOWN to clean up the connection.
169 MESSAGE NODENAME AND INTERNET ADDRESS CANNOT BOTH BE
SPECIFIED
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.
170 MESSAGE ERROR WITH THE USE OF THE FAST SELECT FACILITY.
CAUSE Invalid use of the fast select.
ACTION Validate the calling sequence.
171 MESSAGE INVALID FACILITY FIELD.
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.
172 MESSAGE CONNECTION MUST BE REJECTED.
CAUSE An IPCCONTROL request 9, accept the connection,
cannot be performed.
ACTION Use IPCCONTROL request 15 to reject the
connection.
173 MESSAGE MORE DATA IS AVAILABLE.
CAUSE Warning message. READOPT request was for less
data than available.
ACTION Specify a greater length in READOPT.