SNA Transport Error Messages

MPE documents

CAUSE: An invalid session number was specified in a call to an SNA Transport intrinsic.

ACTION: Write down the circumstances and call your Hewlett-Packard support contact.

CAUSE: The SNA completer was activated with an invalid Cstation, Xfercount, or TargetFlag parameter.

ACTION: Write down the circumstances and call your Hewlett-Packard support contact.

CAUSE: An SNA service passed an out-of-bounds parameter to an SNA Transport intrinsic.

ACTION: Write down the circumstances and call your Hewlett-Packard support contact.

CAUSE: The Flag parameter passed to the SNARcv or SNAPreview intrinsic was invalid.

ACTION: Write down the circumstances and call your Hewlett-Packard support contact.

CAUSE: The NAU's LU-SSCP session is active.

ACTION: None.

CAUSE: An SNAOpenUser was attempted, but no room for another Available File Table (AFT) entry is available in the current stack segment.

ACTION: Write down the circumstances and call your Hewlett-Packard support contact.

CAUSE: The pacing indicator (PI) was set in the Request/Response Header (RH) passed to one of the SNA Send intrinsics.

ACTION: Write down the circumstances and call your Hewlett-Packard support contact.

CAUSE: The Begin Chain Indicator (BCI) was not set in the Response Header (RH) passed to one of the SNA Send intrinsics when sending a response.

ACTION: Write down the circumstances and call your Hewlett-Packard support contact.

CAUSE: The End Chain Indicator (ECI) was not set in the Response Header (RH) passed to one of the SNA Send intrinsics when sending a response.

ACTION: Write down the circumstances and call your Hewlett-Packard support contact.

CAUSE: The Enciphered Data Indicator (EDI) was set in the Request Header (RH) passed to one of the SNA Send intrinsics when sending a request.

ACTION: Write down the circumstances and call your Hewlett-Packard support contact.

CAUSE: Various reserved bits in the Request/Response Header (RH) were incorrectly set by the calling SNA service when making a call to the SNA Send intrinsics.

ACTION: Write down the circumstances and call your Hewlett-Packard support contact.

CAUSE: A serious error occurred in SNA Transport.

ACTION: Write down the circumstances and call your Hewlett-Packard support contact.

CAUSE: A call to the SNA Send intrinsics, specifying a buffer length larger than the one specified in the Half Session Control Block (HSCB) for that session, was made.

ACTION: Write down the circumstances and call your Hewlett-Packard support contact.

CAUSE: A call to the SNAOpenUser intrinsic to open an LU-LU session was made, and the corresponding LU-SSCP session is not yet active.

ACTION: Ensure that the LU-SSCP session has been activated on the remote system. If it has not been activated, activate it and try again.

CAUSE: A call to the SNAControl intrinsic (with FunctionCode = 1) passed a bad Plabel for the software interrupt procedure.

ACTION: Write down the circumstances and call your Hewlett-Packard support contact.

CAUSE: A message on the LU-SSCP session is pending and must be completed before a Send can be issued.

ACTION: A call to the SNARcv or SNARcvfromSSCP intrinsic must be made before any calls to the SNA Send intrinsics are made.

CAUSE: An SNA Receive completed, but the Request/Response Unit (RU) received was larger than the buffer provided in the call to the SNARcv, SNAPreview, or SNARcvfromSSCP intrinsic.

ACTION: Write down the circumstances and call your Hewlett-Packard support contact.

CAUSE: A call to the SNAOpenUser intrinsic to open an LU-LU session was made, but the LU name specified in the call is not configured for this node.

ACTION: Use NMMGR or the configuration file critical summary to check for the valid LUs configured for the requested node.

CAUSE: An invalid session type parameter was specified in a call to the SNAOpenUser intrinsic to open a session.

ACTION: Write down the circumstances and call your Hewlett-Packard support contact.

CAUSE: An SNA service received a negative response as a result of a call to the SNASendtoSSCP intrinsic.

ACTION: Write down the circumstances and call your Hewlett-Packard support contact.

CAUSE: A call to the NMConfgetdata intrinsic failed for some reason.

ACTION: Write down the circumstances and call your Hewlett-Packard support contact.

CAUSE: A call to an SNARcv intrinsic was made while a current request is outstanding.

ACTION: Write down the circumstances and call your Hewlett-Packard support contact.

CAUSE: The specified LUs are all in use.

ACTION: Try again later when the system is less busy, or try using another group of LUs.

CAUSE: A call to the SNAClose or SNAControl intrinsic was made while a send or receive is pending.

ACTION: Write down the circumstances and call your Hewlett-Packard support contact.

CAUSE: An SNA service passed a bad function code to the SNAControl or SNASessinfo intrinsic.

ACTION: Write down the circumstances and call your Hewlett-Packard support contact.

CAUSE: An invalid node name was specified in a call to the SNAOpenUser intrinsic.

ACTION: Ensure that the specified node is a valid SNA node that is currently active.

CAUSE: A call to the SNASendtoSSCP or SNARcvfromSSCP intrinsic was made on an LU-LU session.

ACTION: Write down the circumstances and call your Hewlett-Packard support contact.

CAUSE: An invalid error code was passed to the SNAErrmsg intrinsic.

ACTION: Write down the circumstances and call your Hewlett-Packard support contact.

CAUSE: An attempt to call an SNA Transport intrinsic was made while in user mode.

ACTION: Write down the circumstances and call your Hewlett-Packard support contact.

CAUSE: An invalid InfoWanted parameter was specified in a call to the SNASessinfo intrinsic.

ACTION: Write down the circumstances and call your Hewlett-Packard support contact.

CAUSE: An attempt to abort an SNARcv, SNARcvFromSSCP, or SNASendtoSSCP intrinsic was made when no such request was outstanding.

ACTION: Write down the circumstances and call your Hewlett-Packard support contact.

CAUSE: A link shutdown has been requested with the SNACONTROL STOP command, and all sessions are being notified.

ACTION: Wait until the link has been restarted and then continue.

CAUSE: A protocol shutdown has been requested with the SNACONTROL STOP command, and all sessions are being notified.

ACTION: Wait until the link has been restarted and then continue.

CAUSE: A protocol shutdown has been requested with the SNACONTROL STOPSESS command, and the session it was requested for is being notified.

ACTION: None.

CAUSE: A quiesce shutdown has been requested with the SNACONTROL STOP command. New sessions will not be started, and all current active sessions are to complete their current activities and close in an orderly fashion.

ACTION: Wait until the link has been restarted and then continue.

CAUSE: A quiesce shutdown has been requested with the SNACONTROL STOPSESS command, and the session it was requested for is being closed in an orderly fashion.

ACTION: None.

CAUSE: The SNA Transport message catalog file (CATSNA.PUB.SYS) is missing, invalid, or locked by another process.

ACTION: Replace the catalog file with a valid SNA catalog file.

CAUSE: A call was made to an SNA Transport intrinsic without enough stack space available or with the data segment frozen in memory.

ACTION: Write down the circumstances and call your Hewlett-Packard support contact.

CAUSE: An invalid offset into the given data segment was specified in a call to an SNA Transport intrinsic.

ACTION: Write down the circumstances and call your Hewlett-Packard support contact.

CAUSE: A link failure has occurred, and all sessions are being notified.

ACTION: Wait until the node has been reactivated and then try again.

CAUSE: An SNA Transport internal error has occurred, and all sessions are being notified.

ACTION: Write down the circumstances and call your Hewlett-Packard support contact.

CAUSE: An invalid MaxInfolgth parameter was specified in a call to the SNASessinfo intrinsic.

ACTION: Write down the circumstances and call your Hewlett-Packard support contact.

CAUSE: A buffer too small to hold the error message from the SNA Transport message catalog file (CATSNA.PUB.SYS) was passed in a call to the HPSNAErrmsg or SNAErrmsg intrinsic. The message was truncated to fit into the buffer that was passed.

ACTION: Write down the circumstances and call your Hewlett-Packard support contact.

CAUSE: An attempt to send an expedited request was made while in a state that does not allow it.

ACTION: Write down the circumstances and call your Hewlett-Packard support contact.

CAUSE: An attempt to send a request was made before a Start Data Traffic (SDT) has been received or the positive response has been sent.

ACTION: Write down the circumstances and call your Hewlett-Packard support contact.

CAUSE: A response to a Start Data Traffic (SDT) is being sent, but no SDT was received from the remote system.

ACTION: Write down the circumstances and call your Hewlett-Packard support contact.

CAUSE: An invalid sequence of session control events has occurred.

ACTION: Write down the circumstances and call your Hewlett-Packard support contact.

CAUSE: An attempt to send a ReQuest Recovery (RQR) request was made while in a state other than reset.

ACTION: Write down the circumstances and call your Hewlett-Packard support contact.

CAUSE: A response to a Set and Test Sequence Numbers (STSN) request is being sent, but no corresponding STSN request has been received.

ACTION: Write down the circumstances and call your Hewlett-Packard support contact.

CAUSE: An attempt to send a CRyptography Verification (CRV) request or response was made.

ACTION: Write down the circumstances and call your Hewlett-Packard support contact.

CAUSE: An attempt to send an unsupported Session Control (SC) request was made.

ACTION: Write down the circumstances and call your Hewlett-Packard support contact.

CAUSE: An attempt to send an unsupported Session Control (SC) response was made.

ACTION: Write down the circumstances and call your Hewlett-Packard support contact.

CAUSE: An SNA service is trying to send a response to a deactivation request (UNBIND, DACTLU, or DACTPU), but no such deactivation request has been received.

ACTION: The SNA service should examine the situations in which a deactivation response is sent, and verify that a response is sent only after a deactivation request has been received.

CAUSE: An SNA service is trying to send a response to an activation request (BIND, ACTLU, or ACTPU), but no such activation request has been received.

ACTION: The SNA service should examine the situations in which an activation response is sent, and verify that a response is sent only after an activation request has been received.

CAUSE: A target parameter passed in a call to the IOWait intrinsic is too small to receive sense data. The size of the target parameter is checked only when a non-waited call to the SNASendToSSCP intrinsic completes.

ACTION: Ensure that the size of the target parameter (the second parameter) that was passed to the IOWait intrinsic is at least 4 bytes.

CAUSE: When changing from compatibility mode (CM) to native mode (NM), an error occurred when an SNA compatibility mode intrinsic was called.

ACTION: Write down the circumstances and call your Hewlett-Packard support contact.

CAUSE: When SNAOpenUser was called to open an LU, the LU was opened as a secondary LU. A secondary LU is not capable of issuing a BIND. However, a call was made to SNASendExpedited, to send a BIND. So, an error occurred.

ACTION: Modify the user program that is calling SNASendExpedited.

CAUSE: When user data is sent to the remote system, if the pacing window is not open SNA Transport must place the request in its queue. If, at the same time, the remote system sends an expedited request (which is not affected by the pacing window), SNA Transport could hang. To avoid being hung, SNA Transport aborts the previous waited send call and generates this message to warn the user.

ACTION: The user program should handle this situation.