0 |
0 |
No error. |
ENXIO (138) |
0 |
The requested NSS client is not connected. System Action: Request is failed but the connection remains open.
Response: Send requests for active NSS clients only.
|
EOPNOTSUPP (1112) |
0 |
The requested NSS client is not enabled for
remote monitoring. System Action: Request is failed but connection
remains open.
Response: Send requests only for NSS clients
that are enabled for remote monitoring. Otherwise, configure and permit
the given NSS client for remote monitoring.
|
EINVAL (121) |
NMsRsnBadIdent (1) |
Invalid message or record identifier supplied
in message. System Action: Connection is closed.
Response:
Reissue the connection and send a correctly formatted message.
|
EINVAL (121) |
NMsRsnBadVersion (2) |
Invalid version supplied in message header.
System Action: Request is failed but connection remains open.
Response: Send a correctly formatted message.
|
EINVAL (121) |
NMsRsnBadType (3) |
Unsupported or unknown message type supplied
in message header. System Action: Request is failed but connection
remains open.
Response: Send a supported message type.
|
EINVAL (121) |
NMsRsnExcessiveSize (4) |
Excessive message size. System Action: Connection
is closed.
Response: Reissue the connection and send a correctly
formatted message.
|
EINVAL (121) |
NMsRsnHdrSize (5) |
Message header size is invalid. System Action:
Request is failed but connection remains open.
Response: Send
a message with the header size field set to the correct value.
|
EINVAL (121) |
NMsRsnMsgSize (6) |
Message size is invalid. For example, the message
might be too short, or the message size might be greater than the
sum of its parts. System Action: Request is failed but connection
remains open.
Response: Send a correctly formatted message.
|
EINVAL (121) |
NMsRsnReservedNonzero (7) |
Reserved data in message header, record header,
or record data specifies a nonzero value. Reserved fields must be
set to 0 for compatibility with future versions of the interface.
System Action: Request is failed but connection remains open.
Response: Send a message with reserved fields set to 0.
|
EINVAL (121) |
NMsRsnRecordLength (8) |
Unrecognized record length supplied in message.
Length does not correspond to known record data. System Action:
Request is failed but connection remains open.
Response: Send
a message with input filters of the correct length.
|
EINVAL (121) |
NMsRsnRecordCount (9) |
Unsupported record count supplied in message.
NMI requests currently support a maximum of 20 input filters. System Action: Request is failed but connection remains open.
Response: Send a message with the correct number of input filters.
|
EINVAL (121) |
NMsRsnSectionLength (10) |
Unrecognized section length supplied in record.
Length does not correspond to known section data. System Action:
Request is failed but connection remains open.
Response: Send
a message with correct input filters.
|
EINVAL (121) |
NMsRsnSectionCount (11) |
Unrecognized section count supplied in record.
NMI requests currently allow one section in an input filter record.
System Action: Request is failed but connection remains open.
Response: Send a message with correct input filters.
|
EINVAL (121) |
NMsRsnFilterSpec (12) |
The input filter specification indicates a combination
of filter values that is unsupported for the message's request type.
System Action: Request is failed but connection remains open.
Response: Send a message with a valid input filter specification
for the message type.
|
EINVAL (121) |
NMsRsnFilterValue (13) |
The input filter specification contains a value
that is out of range. System Action: Request is failed but connection
remains open.
Response: Send a message with correct input
filter values.
|
EINVAL (121) |
NMsRsnManTypeConflict(14) |
Manual tunnel activation and deactivation requests
for multiple tunnels must contain uniform tunnel specifications: either
tunnel IDs or tunnel names. The request contained a mixture of tunnel
names and tunnel IDs. System Action: Request is failed but connection
remains open.
Response: Separate manual tunnel names and tunnel
IDs into different requests.
|
EINVAL (121) |
NMsRsnPolicySource (15) |
The policy source value in the policy load request
is invalid. System Action: NO action is required.
Response:
Send a message with a valid NMsecPolSrcSource value.
|
EACCESS (111) |
0 |
Access denied to the requested resource. System Action: Request is failed but connection remains open.
Administrator Response: Permit the user to the security resource.
|
EACCESS (111) |
0 |
Insufficient storage available in the server
to process the request. System Action: Request is failed but connection
remains open.
Response: Increase the REGION size for the IKE
daemon, or send a message with a narrower set of input filters to
limit the response.
|
ENOMEM (132) |
NMsRsnTooManyConns (1) |
The NMI thread is already using its maximum
number of 50 connections and cannot accept any more. System Action:
Connection is not opened and the request is failed.
Response:
Try the request again later.
|
ENOMEM (132) |
NMsRsnNSClient (2) |
Insufficient storage available in the NSS client
to process the request. System Action: Request is failed but connection
remains open.
Response: Increase the REGION size for the NSS
client, or send a message with a narrower set of input filters to
limit the response.
|
ETIMEDOUT (1127) |
NMsRsnNSClient (2) |
Response message was not received from the NSS
client in sufficient time. System Action: Request is failed but
connection remains open.
Response: Resend the request message
to the server.
|
EIO (122) |
(z/OS® UNIX System Services Errno) |
A file system I/O error occurred. The reason
code contains the errno value that describes the error. System
Action: Request is failed but connection remains open.
Response:
Diagnose the z/OS UNIX System Services Errno using z/OS UNIX System Services Messages and Codes.
|
EMVSERR (157) |
0 |
A call to an MVS™ service failed or an internal NSSD error has occurred.
System Action: Request fails but connection remains open.
A message appears in the MVS system log with additional diagnostic information.
Response:
Contact IBM® service.
|