 |
» |
|
|
|
Listed below are the error messages that can occur when SNA Transport
intrinsics are being used. They are listed in numerical order according to message
number. SNA Transport, itself, does not display these messages: It
returns the error number to the SNA service using the intrinsics,
and the service can optionally display the message. These messages
are not logged; they are written to $STDLIST by the SNA service only. - SNAERR 2
- MESSAGE
Invalid session. (SNAERR 2) A call was made to an SNA Transport intrinsic with a bad session number. - 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.
- SNAERR 3
- MESSAGE
Missing Completer Parameter. (SNAERR 3)
An SNA Transport completion occurred with a missing parameter.
- 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.
- SNAERR 5
- MESSAGE
Parameter bounds violation. (SNAERR 5)
An out-of-bounds parameter was passed to an SNA Transport intrinsic.
- 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.
- SNAERR6
- MESSAGE
Invalid flag parameter. (SNAERR 6)
An invalid flag parameter was passed to an SNA Transport intrinsic.
- 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.
- SNAERR7
- MESSAGE
Session is active. (SNAERR 7)
The LU-SSCP session for this NAU is active.
- CAUSE
The NAU's LU-SSCP session is active.
- ACTION
None.
- SNAERR9
- MESSAGE
No available AFT entry. (SNAERR 9)
No room left in current stack segment for another AFT.
- 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.
- SNAERR10
- MESSAGE
Bad PI in RH. (SNAERR 10) The Pacing indicator was set in the RH sent to SNA Transport.
- 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.
- SNAERR 11
- MESSAGE
Bad BCI in RH. (SNAERR 11)
An improper chaining sequence occurred.
- 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.
- SNAERR 12
- MESSAGE
Bad ECI in RH. (SNAERR 12)
An improper chaining sequence occurred.
- 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.
- SNAERR 13
- MESSAGE
Bad EDI in RH. (SNAERR 13)
Attempt was made to send enciphered data.
- 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.
- SNAERR 14
- MESSAGE
Reserved bits in RH must be set to zero. (SNAERR 14)
- 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.
- SNAERR15
- MESSAGE
Internal Error. (SNAERR 15)
An SNA Transport Internal Error occurred.
- CAUSE
A serious error occurred in SNA Transport.
- ACTION
Write down the circumstances and call your Hewlett-Packard support contact.
- SNAERR16
- MESSAGE
Invalid RU size. (SNAERR 16)
An attempt was made to send an RU longer than the Max RU size.
- 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.
- SNAERR17
- MESSAGE
NAU is inactive. (SNAERR 17)
The LU-SSCP session for this NAU is inactive.
- 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.
- SNAERR18
- MESSAGE
Invalid Plabel. (SNAERR 18)
An Invalid plabel was passed to the SNAControl intrinsic.
- 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.
- SNAERR 19
- MESSAGE
LU-SSCP message pending. (SNAERR 19)
- 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.
- SNAERR 20
- MESSAGE
RU buffer too small. (SNAERR 20)
An RU received was larger than the buffer provided.
- 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.
- SNAERR 21
- MESSAGE
Invalid LU name. (SNAERR 21)
The LU name specified does not exist.
- 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.
- SNAERR 22
- MESSAGE
Invalid session type. (SNAERR 22)
An attempt was made to open a non LU-LU session.
- 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.
- SNAERR23
- MESSAGE
Negative LU-SSCP response. (SNAERR 23)
A negative response was sent by the host in response to a request.
- 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.
- SNAERR24
- MESSAGE
Invalid configuration access. (SNAERR 24)
SNA Transport was unable to access the required configuration data.
- CAUSE
A call to the NMConfgetdata intrinsic failed for some reason.
- ACTION
Write down the circumstances and call your Hewlett-Packard support contact.
- SNAERR25
- MESSAGE
Request pending. (SNAERR 25)
An SNA Transport Receive request is already pending.
- 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.
- SNAERR26
- MESSAGE
No available NAU. (SNAERR 26)
All LUs specified in the SNAOPENUSER are currently in use.
- 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.
- SNAERR 27
- MESSAGE
IO pending. (SNAERR 27)
- 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.
- SNAERR 28
- MESSAGE
Invalid function code. (SNAERR 28)
- 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.
- SNAERR 29
- MESSAGE
Inactive node or invalid node name. (SNAERR 29)
- 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.
- SNAERR 30
- MESSAGE
Illegal call. (SNAERR 30)
An attempt was made to access an LU-SSCP session in an LU-LU session.
- 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.
- SNAERR31
- MESSAGE
Invalid error code. (SNAERR 31)
- CAUSE
An invalid error code was passed to the SNAErrmsg intrinsic.
- ACTION
Write down the circumstances and call your Hewlett-Packard support contact.
- SNAERR32
- MESSAGE
Privilege mode required. (SNAERR 32)
- 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.
- SNAERR33
- MESSAGE
Invalid InfoWanted parameter. (SNAERR 33)
- 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.
- SNAERR35
- MESSAGE
No request pending. (SNAERR 35)
- 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.
- SNAERR 36
- MESSAGE
Link shutdown occurred. (SNAERR 36)
- 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.
- SNAERR 37
- MESSAGE
Protocol shutdown requested. (SNAERR 37) - 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.
- SNAERR 38
- MESSAGE
Quiesce shutdown requested. (SNAERR 38) - 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.
- SNAERR39
- MESSAGE
CATSNA.PUB.SYS access error. (SNAERR 39)
SNA Transport was unable to access its catalog file.
- 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.
- SNAERR40
- MESSAGE
Out of Stack Space. (SNAERR 40)
- 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.
- SNAERR48
- MESSAGE
Invalid data offset. (SNAERR 48)
- 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.
- SNAERR51
- MESSAGE
Link Failure occurred. (SNAERR 51)
- CAUSE
A link failure has occurred, and all sessions are being notified.
- ACTION
Wait until the node has been reactivated and then try again.
- SNAERR 52
- MESSAGE
SNA Transport Internal Error Shutdown. (SNAERR 52)
- 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.
- SNAERR 55
- MESSAGE
Bad Maxinfo length parameter. (SNAERR 55)
- 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.
- SNAERR 58
- MESSAGE
Error msg truncated because buffer was too small. (SNAERR 58)
- 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.
- SNAERR 100
- MESSAGE
Expedited response pending. (SNAERR 100)
- 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.
- SNAERR101
- MESSAGE
Data traffic inactive. (SNAERR 101)
- 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.
- SNAERR102
- MESSAGE
SDT request not received. (SNAERR 102)
- 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.
- SNAERR103
- MESSAGE
Invalid session control protocol. (SNAERR 103)
- CAUSE
An invalid sequence of session control events has occurred.
- ACTION
Write down the circumstances and call your Hewlett-Packard support contact.
- SNAERR104
- MESSAGE
RQR request pending. (SNAERR 104)
- 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.
- SNAERR 105
- MESSAGE
STSN request not pending. (SNAERR 105)
- 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.
- SNAERR 107
- MESSAGE
Unsupported CRV request/response. (SNAERR 107)
- 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.
- SNAERR 108
- MESSAGE
Unsupported session control request. (SNAERR 108)
- 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.
- SNAERR 109
- MESSAGE
Unsupported session control response. (SNAERR 109)
- 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.
- SNAERR110
- MESSAGE
No such deactivation request (UNBIND,DACTLU,DACTPU) received. (SNAERR 110)
- 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.
- SNAERR111
- MESSAGE
No such activation request (BIND,ACTLU,ACTPU) received. (SNAERR 111)
- 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.
- SNAERR112
- MESSAGE
The target parameter passed to iowait is too small. (SNAERR 112)
- 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.
- SNAERR113
- MESSAGE
An error occurred during a switch from CM to NM. (SNAERR 113)
- 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.
- SNAERR115
- MESSAGE
Couldn't send BIND on a Secondary LU. (SNAERR 115)
- 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.
- SNAERR116
- MESSAGE
A waited send intrinsic call was aborted by SNA Transport to avoid a deadlock. (SNAERR 116)
- 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.
|
