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