 |
» |
|
|
|
The following SNA Transport messages can appear on Pass Thru devices
or, in some cases, the system console. MESSAGE: Successful Completion. (SNAERR
0) | CAUSE: The SNA Transport intrinsic was successfully completed. ACTION: None. |
MESSAGE: Illegal DB register. (SNAERR
1) call to an SNA Transport intrinsic was made in split stack. | CAUSE: An SNA subsystem made a call to an SNA Transport
intrinsic while in split stack mode. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Invalid session. (SNAERR 2)
A call was made to an SNA Transport intrinsic with a bad session
number. | CAUSE: A call to an SNA Transport intrinsic was made,
specifying an invalid session number parameter. ACTION: Note the circumstances and report them to your
HP representative. |
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: Note the circumstances and report them to your
HP representative. |
MESSAGE: Security violation. (SNAERR
4) User or program not authorized to use this SNA class. | CAUSE: An SNA subsystem, or the user, is not authorized
to use this SNA class. ACTION: Specify a class name the subsystem or user is
authorized to use. Check with your system administrator to determine
the correct class to use. |
MESSAGE: Parameter bounds violation.
(SNAERR 5) An out-of-bounds parameter was passed to an SNA Transport
intrinsic. | CAUSE: An SNA subsystem passed an out-of-bounds parameter
to an SNA Transport intrinsic. ACTION: Note the circumstances and report them to your
HP representative. |
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: Note the circumstances and report them to your
HP representative. |
MESSAGE: Session is active. (SNAERR
7) | CAUSE: The LU-SSCP session for this NAU is active. ACTION: None. |
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 AFT entry
is available in the current stack segment. ACTION: Note the circumstances and report them to your
HP representative. |
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 RH passed
to one of the SNA Send intrinsics. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Bad BCI in RH. (SNAERR 11)
An improper chaining sequence occurred. | CAUSE: The Begin Chain Indicator (BCI) was not set in
the RH passed to one of the SNA Send intrinsics when sending a response. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Bad ECI in RH. (SNAERR 12)
An improper chaining sequence occurred. | CAUSE: The End Chain Indicator (ECI) was not set in the
RH passed to one of the SNA Send intrinsics when sending a response. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Bad EDI in RH. (SNAERR 13)
Attempt was made to send enciphered data. | CAUSE: The Enciphered Data Indicator (EDI) was set in
the RH passed to one of the SNA Send intrinsics when sending a request. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Reserved bits in RH must be
set to zero. (SNAERR 14) | CAUSE: Various reserved bits in the RH were incorrectly
set by the calling SNA subsystem when making a call to the SNA Send intrinsics. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Internal Error. (SNAERR 15)
An SNA Transport Internal Error occurred. | CAUSE: A serious error occurred in SNA Transport. ACTION: Note the circumstances and report them to your
HP representative. |
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 was made, specifying a buffer length
larger than the one specified in the Half Session Control Block (HSCB)
for that session. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: NAU is inactive. (SNAERR 17)
The LU-SSCP session for this NAU is inactive. | CAUSE: A call to SNAOpenuser 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 host side. If it has not been activated, activate it and
try again. |
MESSAGE: Invalid Plabel. (SNAERR18)
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: Note the circumstances and report them to your
HP representative. |
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 SNARcv or SNARcvfromSSCP must be made before any calls to the SNA Send intrinsics are made. |
MESSAGE: RU buffer too small. (SNAERR
20) An RU received was larger than the buffer provided. | CAUSE: An SNA Receive completed, but the RU received was larger than
the buffer provided in the SNARcv, Preview, or RcvfromSSCP call. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Invalid class name. (SNAERR
21) The Class name specified does not exist. | CAUSE: A call to SNAOpenuser to open an LU-LU session was made, but the class
name specified in the call is not configured for this node. ACTION: Check with your system manager for the valid classes configured
for the requested node. |
MESSAGE: Invalid session type. (SNAERR
22) An attempt was made to open a non LU-LU session. | CAUSE: A call to SNAOpenuser was made to open a session, specifying an invalid
session type parameter. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Negative LU-SSCP response.
(SNAERR 23) A negative response was sent by the host in response
to a request. | CAUSE: An SNA subsystem received a negative response
as a result of a call to the SNASendtoSSCP intrinsic. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Invalid configuration access.
(SNAERR 24) SNA Transport was unable to access the required configuration
data. | CAUSE: A call to NMConfgetdata failed. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Request pending. (SNAERR 25)
An SNA Transport Receive request is already pending. | CAUSE: A call to an SNA Transport Receive intrinsic was made while a current request is
outstanding. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: No available NAU. (SNAERR
26) All LUs in the specified SNA class are currently in use. | CAUSE: All LUs in the specified SNA class are currently
in use. ACTION: Try again later when the system is less busy,
or try using another SNA class. |
MESSAGE: IO pending. (SNAERR 27) | CAUSE: A call to the SNAClose or SNAControl intrinsic was made while a send or receive is
pending. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Invalid function code. (SNAERR
28) | CAUSE: An SNA subsystem passed a bad function code to
the SNAControl or SNASessinfo intrinsic. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Inactive node or invalid node
name. (SNAERR 29) | CAUSE: A call to the SNAOpenuser intrinsic was made, specifying an invalid node
name. ACTION: Ensure that the specified node is a valid SNA
node that is currently active. |
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: Note the circumstances and report them to your
HP representative. |
MESSAGE: Invalid error code. (SNAERR
31) | CAUSE: An invalid error code was passed to the SNAErrmsg intrinsic. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Privilege mode required. (SNAERR
32) | CAUSE: An attempt to call an SNA Transport intrinsic
was made while in user mode. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Invalid InfoWanted parameter.
(SNAERR 33) | CAUSE: A call to the SNASessinfo intrinsic was made, specifying an invalid InfoWanted parameter. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: No request pending. (SNAERR
35) | CAUSE: An attempt to abort an SNA Receive, RcvFromSSCP, or SendtoSSCP was made when no such request was outstanding. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Link shutdown occurred. (SNAERR
36) | CAUSE: A link shutdown has been requested via the SNACONTROL STOP command, and all sessions are being notified. ACTION: Wait until the link has been restarted and then
continue. |
MESSAGE: Protocol shutdown requested.
(SNAERR 37) | CAUSE: A protocol shutdown has been requested via the SNACONTROL STOP command, and all sessions are being notified. ACTION: Wait until the link has been restarted and then
continue. |
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. |
MESSAGE: Invalid Msg Catalog. (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. |
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: Note the circumstances and report them to your
HP representative. |
MESSAGE: Invalid data offset. (SNAERR
48) | CAUSE: A call to an SNA Transport intrinsic was made,
specifying an invalid offset into the given data segment. ACTION: Note the circumstances and report them to your
HP representative. |
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. |
MESSAGE: SNA Transport Internal Error
Shutdown. (SNAERR 52) | CAUSE: An SNA Transport internal error has occurred,
and all sessions are being notified. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Hierarchical Shutdown. (SNAERR
53) | CAUSE: A hierarchical shutdown is occurring, and all
sessions are being notified. ACTION: Wait until the node has been reactivated and then
try again. |
MESSAGE: Bad Maxinfo length parameter.
(SNAERR 55) | CAUSE: A call to the SNASessinfo intrinsic was made, specifying an invalid MaxInfoLength parameter. ACTION: Note the circumstances and report them to your
HP representative. |
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: Note the circumstances and report them to your
HP representative. |
MESSAGE: Data traffic inactive. (SNAERR
101) | CAUSE: An attempt to send a request was made before a
Start Data Traffic (SDT) had been received, or the positive response
has been sent. ACTION: Note the circumstances and report them to your
HP representative. |
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 host. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Invalid session control protocol.
(SNAERR 103) | CAUSE: An invalid sequence of session control events
has occurred. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: RQR request pending. (SNAERR
104) | CAUSE: An attempt to send an RQR request was made while
in a state other than Reset. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: STSN request not pending.
(SNAERR 105) | CAUSE: A response to an STSN request is being sent, but
no corresponding STSN request has been received. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Unsupported CRV request/response.
(SNAERR 107) | CAUSE: An attempt to send a CRV request or response was
made. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Unsupported session control
request. (SNAERR 108) | CAUSE: An attempt to send an unsupported Session Control
(SC) request was made. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Unsupported session control
response. (SNAERR 109) | CAUSE: An attempt to send an unsupported Session Control
(SC) response was made. ACTION: Note the circumstances and report them to your
HP representative. |
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. |
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 (UNBIND, DACTLU, or DACTPU), 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. |
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 SendToSSCP 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. |
|
