NetWare  for  SAA  Alarms

Session level send error

Session level OAF address duplication

Route request failed

Too many sessions request

No begin bracket

Unexpected request

Unexpected BIS reply

Error in basic conversation

Error in mapped conversation

Bad bind response

Received bad NS

Bad unbind request

Format error

Unexpected unbind response

Bad initialization self response

Bad bind request

Unexpected BIS request

Invalid NS record

Session level protocol violation

Bad frame

Bracket error

Bad GDS Variable

Session security error

Conversation security error

Link error

Bad transfer MS data

Abnormal unbind

Create TP error

Access password error

Abnormal termination

SNA host link connected

SNA host link disconnected

Serial number violation


NWSAA Session Level Send Error
Session level send error

Explanation:

The NetWare for SAA issued a session level send error.  Application specific error data was generated as a result of a SEND_ERROR, MC_SEND_ERROR, DEALLOCATE, or MC_DEALLOCATE.

Default Severity:

Minor.

Action:

Because the error pertains to the application, consult the application developer or the application manual to determine the problem.


NWSAA OAF Address Duplication
Session level OAF address duplication

Explanation:

The NetWare for SAA received a duplicate Origin Address Field (OAF) on Destination Address Field (DAF).  A session activation request was received for a session that is already active.

Default Severity:

Minor.

Action:

Restart the session on which the problem occurred.


NWSAA Route Request Failed
Route request failed

Explanation:

The NetWare for SAA was unable to perform a route request to an LU due to an invalid LU name or network addressable unit (NAU).

Default Severity:

Minor.

Action:

Check the configuration parameters for the LU and restart the session.


NWSAA Too Many Sessions Request
Too many sessions requested

Explanation:

The NetWare for SAA rejected a request to activate more sessions than configured for the specified LU.

Default Severity:

Minor.

Action:

If more sessions are needed, have the application issue an ATTACH_LU verb for the LU allowing more sessions.


NWSAA No Begin Bracket
No Begin Bracket bit

Explanation:

The NetWare for SAA detected a Begin Bracket bit not set in Request Header (RH).  The Partner LU did not set the required Begin Bracket bit in the RH.

Default Severity:

Minor.

Action:

Ensure that the Partner LU software is compatible with the NetWare for SAA.  The LU partner software should set the Begin Bracket in the RH.


NWSAA Unexpected Request
Unexpected request

Explanation:

The NetWare for SAA detected a "Request to Receive" sent in a wrong state by the Partner LU.

Default Severity:

Minor.

Action:

Ensure the Partner LU software sends "Request to Receive" in the appropriate state as specified in the SNA protocol.


NWSAA Unexpected BIS Reply
Unexpected BIS reply

Explanation:

The NetWare for SAA received an unexpected BRACKET INITIATION STOPPED (BIS) reply.  The Partner LU sent the NetWare for SAA a BIS reply even though the NetWare for SAA never sent a BIS request.

Default Severity:

Minor.

Action:

Ensure that the Partner LU software sends BIS replies as specified in the SNA protocol.


NWSAA Error in Basic Conversation
Error in basic conversation

Explanation:

The NetWare for SAA detected an error in the Basic Conversation protocol.  The Partner LU on a basic conversation violated the SNA protocol.

Default Severity:

Minor.

Action:

Ensure the Partner LU software follows the SNA protocol.


NWSAA Error in Mapped Conversation
Error in mapped conversation

Explanation:

The NetWare for SAA detected an error in the Mapped Conversation protocol.  The Partner LU on a mapped conversation violated the SNA protocol.

Default Severity:

Minor.

Action:

Ensure the Partner LU software follows the SNA protocol.


NWSAA Bad Bind Response
Bad bind response

Explanation:

A BIND response was received for a session that the NetWare for SAA did not send a BIND request for.

Default Severity:

Minor.

Action:

No action is necessary unless it appears that the unrequested BIND response is related to other network problems.


NWSAA Received Bad NS
Received bad NS

Explanation:

The NetWare for SAA received an unsupported or unrecognized SNA Network Services (NS) request or response.  The Netware for SAA ignores any unsupported or unrecognized NS requests or response it receives.

Default Severity:

Minor.

Action:

Ensure the host sends only valid NS requests and responses.


NWSAA Bad Unbind Request
Bad unbind request

Explanation:

The NetWare for SAA received an UNBIND request with a syntax error.  The Partner LU violated the SNA protocol by sending an UNBIND request with invalid syntax.

Default Severity:

Minor.

Action:

Ensure the Partner LU software follows the SNA protocol.


NWSAA Format Error
Format error

Explanation:

The NetWare for SAA received a Session Control Request with a format error.  The Partner LU violated the SNA protocol by sending a Session Control Request with a format error.

Default Severity:

Minor.

Action:

Ensure the Partner LU software follows the SNA protocol.


NWSAA Unexpected Unbind Response
Unexpected unbind response

Explanation:

The NetWare for SAA received an unexpected UNBIND response.  An UNBIND response was received for a session that the NetWare for SAA did not send an UNBIND request for.

Default Severity:

Minor.

Action:

No action is necessary unless it appears that the unrequested UNBIND response is related to other network problems.


NWSAA Bad Init-Self Response
Bad initialization self response

Explanation:

The NetWare for SAA received an unrequested INIT-SELF response.  The host sent the NetWare for SAA an INIT-SELF response even though the NetWare for SAA never sent an INIT-SELF request.

Default Severity:

Minor.

Action:

Ensure the host software does not send unrequested INIT-SELF response.


NWSAA Bad Bind Request
Bad bind request

Explanation:

The NetWare for SAA received a BIND request with a syntax, state, or semantic error.  The Partner LU violated the SNA protocol by sending a BIND request with a syntax, state, or semantic error.

Default Severity:

Minor.

Action:

Ensure the Partner LU software follows the SNA protocol.


NWSAA Unexpected BIS Request
Unexpected BIS request

Explanation:

The NetWare for SAA received an unexpected BRACKET INITIATION STOPPED (BIS) request.  The Partner LU violated the SNA protocol by sending a BIS request in the wrong state.

Default Severity:

Minor.

Action:

Ensure the Partner LU software follows the SNA protocol.


NWSAA Invalid NS Record
Invalid NS record

Explanation:

The NetWare for SAA received an invalid Network Services (NS) record.  The host violated the SNA protocol by sending an invalid NS record to the NetWare for SAA.

Default Severity:

Minor.

Action:

Ensure the host software follows the SNA protocol.


NWSAA Session Level Protocol Voilation
Session level protocol violation

Explanation:

The NetWare for SAA detected an error in a session level protocol.  The NetWare for SAA detected a violation of the SNA protocol caused by the Partner LU.

Default Severity:

Minor.

Action:

Ensure the partner LU software follows the SNA protocol.


NWSAA Bad Frame
Bad frame

Explanation:

The NetWare for SAA Data Link Control (DLC) sent an invalid transmission header or frame size.  The SNA transmission header was either invalid or the frame size was too small to be a valid SNA frame.

Default Severity:

Minor.

Action:

Verify the operation and the frame size of the local and remote DLCs.  Also, verify that the remote system is configured for SNA.


NWSAA Bracket Error
Bracket error

Explanation:

The NetWare for SAA received a Bracket error.  The Partner LU violated the SNA protocol by incorrectly setting the Begin Bracket indicator.

Default Severity:

Minor.

Action:

Ensure the Partner LU software follows the SNA protocol.


NWSAA Bad GDS Variable
Bad GDS variable

Explanation:

The NetWare for SAA received an erroneous General Data Stream (GDS) variable from a Partner LU on a mapped conversation.

Default Severity:

Minor.

Action:

Ensure the Partner LU software follows the SNA protocol.


NWSAA Session Security Error
Session security error

Explanation:

The NetWare for SAA received a session level security error.  The session could not be bound because of a session level security error.

Default Severity:

Minor.

Action:

Ensure the application supplies the correct LU-LU password.


NWSAA Conversation Security Error
Conversation security error

Explanation:

The NetWare for SAA received a conversation level security error.  The conversation could not be bound because of an error in the conversation level security.

Default Severity:

Minor.

Action:

Allocate the conversation again, and specify the correct conversation level security information.


NWSAA Link Error
Link error

Explanation:

The NetWare for SAA link level error occurred.  The NetWare for SAA could not establish a data link with a host or another node.

Default Severity:

Minor.

Action:

Check the physical connection between the local system and the remote system.  Also, verify that the remote system is operational.


NWSAA Bad Transfer MS Data
Bad transfer MS data

Explanation:

The NetWare for SAA Network Management Vector Transport (NMVT) message provided by a TRANSFER_MS_DATA verb was too large for the Request/Response Unit (RU) size.  Because the NMVT was too large for the RU size, it was not sent to the SSCP.

Default Severity:

Minor.

Action:

Reduce the size of the data being sent or increase the RU size so it is adequate.


NWSAA Abnormal Unbind
Abnormal unbind

Explanation:

The NetWare for SAA received an abnormal UNBIND.  The Partner LU abnormally terminated a session by sending an UNBIND.

Default Severity:

Minor.

Action:

Determine the cause of the UNBIND and correct the condition by using the sense data included with the UNBIND.


NWSAA Create TP Error
Create TP error

Explanation:

The NetWare for SAA detected a Transaction Program (TP) error.  The application subsystem Create_TP exit returned the error to the NetWare for SAA.  An incoming allocate was therefore rejected by the NetWare for SAA.

Default Severity:

Minor.

Action:

Refer to the application for the cause of the rejection.


NWSAA Access Password Error
Access password error

Explanation:

The NetWare for SAA Access detected a password error.  The NetWare for SAA was unable to access a password for the session level security. Therefore a session could not be bound.

Default Severity:

Minor.

Action:

Change the application so it provides a password to the NetWare for SAA through the ACCESS_LU_LU_PW verb.


NWSAA Abnormal Termination
Abnormal termination

Explanation:

The NetWare for SAA terminated itself abnormally.  The termination may have been caused by insufficient server memory, in-proper installation, or configuration error.

Default Severity:

Major.

Action:

Verify that sufficient memory is available for the NetWare for SAA to function,  the installation was completed properly, and the configuration using CSCON utility was done properly.


SNA host link connected

Explanation:

The NetWare for SAA  established a host link using the profile requested by the user.

Default Severity:

Informational.

Action:

This message is for information only.  No action is required.


SNA host link disconnected

Explanation:

The NetWare for SAA disconnected the host link.

Default Severity:

Informational.

Action:

Refer to the error status code and check the documentation for the cause of link disconnection.  Take the appropriate action.  If the host link was removed by unloading the profile, then no action is required.


NWSAA Serial Number Violation
Serial number violation

Explanation:

The NetWare for SAA detected a serial number violation.  The violation was caused by running an unauthorized copy of the NetWare for SAA on a NetWare server.  It is possible that one copy of  NetWare for SAA was installed on two or more NetWare servers and executed simultaneously.

Default Severity:

Critical.

Action:

Unload the unauthorized copy or copies of the NetWare for SAA.