 |
» |
|
|
|
The following SNA Transport messages can appear on Pass Thru devices
or, in some cases, the system console. MESSAGE: Illegal DB register. (SNAERR
1) | CAUSE: The DB register was pointing to an extra data
segment on a call to an SNA Link intrinsic. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Invalid session. (SNAERR 2) | CAUSE: You probably passed an SNA IMF intrinsic an invalid
terminal identifier parameter. ACTION: Be sure you used the terminal identifier returned
by OPEN3270. |
MESSAGE: Invalid SNA catalog file.
(SNAERR 3) | CAUSE: The parameter was omitted on a call to an SNA
Link intrinsic. ACTION: Note the circumstances and contact your HP representative. |
MESSAGE: Security violation. (SNAERR
4) | CAUSE: You tried to invoke Pass Thru by specifying a
class name that you were not authorized to use. ACTION: Specify a class name that you are authorized to
use. Check with your system administrator to determine which classes
are available. This can be determined by the user and program. |
MESSAGE: Parameter bounds violation.
(SNAERR 5) | CAUSE: SNA IMF passed SNA Link an out-of-bounds parameter. ACTION: Note the circumstances and contact your HP representative. |
MESSAGE: Invalid flag parameter. (SNAERR
6) | CAUSE: SNA IMF passed an invalid flag parameter to an
SNA Link intrinsic. ACTION: Note the circumstances and contact your HP representative. |
MESSAGE: Session is active. (SNAERR
7) | CAUSE: The NAU has been activated. ACTION: None. |
MESSAGE: Session is inactive. (SNAERR
8) | CAUSE: You attempted to send data on the LU-SSCP session,
but the LU had not been activated by the host. ACTION: Try again after the node has been activated from
the host side. |
MESSAGE: No available AFT entry. (SNAERR
9) | CAUSE: There were not enough available file table (AFT)
entries in the process control block extension for SNA IMF to complete
the initialization for the Pass Thru session. ACTION: Too many files may have been opened by your program;
try again. |
MESSAGE: Bad PI in RH. (SNAERR 10 | CAUSE: Invalid Pacing Indicator in Request/Response Header. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Bad BCI in RH. (SNAERR 11) | CAUSE: Invalid Begin Chain Indicator in Request/Response
Header. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Bad ECI in RH. (SNAERR 12) | CAUSE: Invalid End Chain Indicator in Request/Response
Header. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Bad EDI in RH. (SNAERR 13 | CAUSE: Invalid Enciphered Data Indicator in Request/Response Header. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Reserved bits in RH must be
set to zero. (SNAERR 14) | CAUSE: SNA IMF failed to initialize reserved bits in
the Request/Response Header. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Internal Error. (SNAERR 15) | CAUSE: An internal error has occurred in the SNA Link
software, most likely causing the node to shut down. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Invalid RU size. (SNAERR 16) | CAUSE: SNA IMF passed an SNA Link intrinsic an RU which
exceeded the allowable size for this session. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: NAU is inactive. (SNAERR 17) | CAUSE: The NAU is not active. ACTION: Ensure that the NAU has been activated on the
host side. |
MESSAGE: Invalid Plabel. (SNAERR 18) | CAUSE: The SNAControl intrinsic was passed an invalid PLabel by SNA IMF. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: LU-SCCP message pending. (SNAERR
19) | CAUSE: A message on the LU-SSCP session is pending and
must be completed before proceeding further. ACTION: Issue a call to RECV3270 before proceeding. |
MESSAGE: RU buffer too small. (SNAERR
20) | CAUSE: The RU size used by SNA IMF is too small to contain
the data to be returned by SNA Link. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Invalid class name. (SNAERR
21) | CAUSE: You specified an invalid class name in the Pass
Thru info string, or the class is not associated with the specified
node. ACTION: Invoke Pass Thru and specify a correct class name.
Check with your system manager for the valid classes configured
in the configuration file for the requested node name. |
MESSAGE: Invalid session type. (SNAERR
22) | CAUSE: An invalid session type parameter was passed to
SNA Link. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Negative LU-SSCP response.
(SNAERR 23) | CAUSE: A negative response occurred on the LU-SSCP session. ACTION: Make sure the IBM host application that you are
trying to access is operational. If it is, note the circumstances
and contact your HP representative. |
MESSAGE: Invalid configuration access.
(SNAERR 24) | CAUSE: The node manager (NMMGR) configuration file name (NMCONFIG)
is incorrect, or the file is corrupt or missing. The SNA Link software
encountered an error accessing data in the configuration file, so
SNA IMF could not start the Pass Thru session. ACTION: Have the system manager verify the accuracy of
the configuration file, and try again. |
MESSAGE: Request pending. (SNAERR 25) | CAUSE: A request is already pending. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: No available NAU. (SNAERR
26) | CAUSE: All the NAUs configured in the SNA class specified
in the info string are currently in use. ACTION: Try again later when the system is less busy,
or specify another class name if one is configured. |
MESSAGE: I/O pending. (SNAERR 27) | CAUSE: A previous I/O request has not been completed. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Invalid function code. (SNAERR
28) | CAUSE: SNA IMF passed SNA Link an invalid function code
parameter. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Inactive node or invalid node
name. (SNAERR 29) | CAUSE: You specified an invalid node name in the Pass
Thru info string, or the node you specified has not been activated
on the HP 3000. ACTION: Verify the accuracy of the info string and check
with the system manager to make sure the node you specified has
been activated on the HP 3000. |
MESSAGE: Illegal call. (SNAERR 30 | CAUSE: SNA IMF and SNA Link are not synchronized with
respect to the type of session established. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Invalid error code. (SNAERR
31) | CAUSE: SNA IMF passed SNAErrMsg an invalid error code parameter. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Privilege mode required. (SNAERR
32) | CAUSE: An SNA Link intrinsic was called that required
Privilege Mode capability. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Invalid InfoWanted parameter.
(SNAERR 33) | CAUSE: SNA IMF passed SNASessInfo an invalid InfoWanted parameter. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: No request pending. (SNAERR
35) | CAUSE: There are no requests pending. ACTION: None. |
MESSAGE: Link shutdown occurred. (SNAERR
36) | CAUSE: The node that you specified in the info string
when Pass Thru was invoked has been shut down. An SNACONTROL STOP command was issued or a link error has occurred; your
session has been terminated. ACTION: Try again later when the HP 3000 node
has been reactivated with the SNACONTROL START command. |
MESSAGE: Protocol shutdown requested.
(SNAERR 37) | CAUSE: The node on which you are running has been shut
down by the system manager with the SNACONTROL STOP command. ACTION: Try again later when the HP 3000 node
has been reactivated with the SNACONTROL START command. |
MESSAGE: Quiesce shutdown requested.
(SNAERR 38) | CAUSE: The node on which you are running has been shut
down by the system manager with the SNACONTROL STOP command. The SNA node is being restrained from starting
new jobs. As current jobs finish, the system gradually winds down
until jobs are no longer running. ACTION: Try again later when the HP 3000 node
has been reactivated with the SNACONTROL START command. |
MESSAGE: Invalid parameters. (SNAERR
39) | CAUSE: The message catalog CATSNA.PUB.SYS is invalid. ACTION: Inform your system manager. |
MESSAGE: No stack space. (SNAERR 40) | CAUSE: The SNA Link subsystem could not process a request
made by the SNA IMF Pass Thru process due to insufficient stack
space. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Invalid request. (SNAERR 41) | CAUSE: Invalid request. ACTION: Try again later. |
MESSAGE: Invalid trace element. (SNAERR
42) | CAUSE: An invalid trace element was encountered by SNA
Link. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Invalid trace state. (SNAERR
43) | CAUSE: An invalid trace state was encountered by SNA
Link. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Invalid subclass. (SNAERR
44) | CAUSE: SNA Link encountered an invalid subclass. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Invalid entry. (SNAERR 45) | CAUSE: An invalid entry was detected by SNA Link. ACTION: Note the circumstances and contact your HP representative. |
MESSAGE: Maximum data too small. (SNAERR
46) | CAUSE: SNA IMF passed SNA Link an invalid MaxData parameter. ACTION: Note the circumstances and contact your HP representative. |
MESSAGE: Invalid action code. (SNAERR
47) | CAUSE: SNA IMF passed SNA Link an invalid ActionCode parameter. ACTION: Note the circumstances and contact your HP representative. |
MESSAGE: Invalid data offset. (SNAERR
48) | CAUSE: SNA IMF passed SNA Link an invalid data offset
parameter. It was probably negative or longer than the length of
the message. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Invalid FunctionParm. (SNAERR
49) | CAUSE: SNA IMF passed SNAControl an invalid function parameter. Legal values range from
0 through 6. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Invalid buffer length. (SNAERR
50) | CAUSE: SNA IMF passed an invalid buffer length to an
SNA Link intrinsic. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Link Failure occurred. (SNAERR
51) | CAUSE: The node on which you are running has shut down
due to a link failure, and your session has been terminated. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Transport Internal Error Shutdown.
(SNAERR 52) | CAUSE: The SNA Link software has encountered an internal
error, and the node has been shut down. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Hierarchical Shutdown. (SNAERR
53) | CAUSE: The host has deactivated your NAU, so your session
has been terminated. ACTION: Try again after the host has reactivated the NAU,
or contact the IBM system manager to have the NAU reactivated. |
MESSAGE: Bad Maxinfo length parameter.
(SNAERR 55) | CAUSE: SNA IMF passed SNA Link an invalid MaxInfoLength parameter. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Expedited response pending.
(SNAERR 100) | CAUSE: An expedited response is pending and must be completed
before proceeding. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: Data traffic inactive. (SNAERR
101) | CAUSE: The host has not sent the necessary command sequence
to activate your session. ACTION: Check with your system administrator or IBM operator
to make sure the NAUs on the HP 3000 have been properly
activated, then try again. |
MESSAGE: SDT request not received.
(SNAERR 102) | CAUSE: The host has not sent the necessary command sequence
to activate your session. ACTION: Check with your system administrator or IBM operator
to make sure the NAUs on the HP 3000 have been properly
activated, then try again. |
MESSAGE: Invalid session control protocol.
(SNAERR 103) | CAUSE: An internal error has occurred in the SNA Link
subsystem, or an illegal request was received from the host. ACTION: Note the circumstances and report them to your
HP representative. |
MESSAGE: RQR request pending. (SNAERR
104) | CAUSE: SNA IMF has requested recovery for the session. ACTION: Note the circumstances and contact your HP representative. |
MESSAGE: STSN request not pending.
(SNAERR 105) | CAUSE: There is no STSN pending. ACTION: Note the circumstances and contact your HP representative. |
MESSAGE: Pacing not allowed. (SNAERR
106) | CAUSE: An invalid attempt was made to use pacing. ACTION: Note the circumstances and contact your HP representative. |
MESSAGE: Unsupported CRV request/response.
(SNAERR 107) | CAUSE: The primary requested an unsupported function.
SNA Link does not support Cryptography Verification (CRV). ACTION: Change the host application's BIND to
turn off cryptography. |
MESSAGE: Unsupported session control
request. (SNAERR 108) | CAUSE: An unsupported session control request was attempted. ACTION: Note the circumstances and contact your HP representative. |
MESSAGE: Unsupported session control
response. (SNAERR 109) | CAUSE: An unsupported session control response was detected
by SNA Link. ACTION: Note the circumstances and contact your HP representative. |
MESSAGE: No such deact req (UNBIND,DACTLU,DACTPU)
rcvd. (SNAERR 110) | CAUSE: No deactivation request has been received. ACTION: Note the circumstances and contact your HP representative. |
MESSAGE: No such act req (BIND,,ACTPU)
rcvd. (SNAERR 111) | CAUSE: No activation request has been received for your
NAU. ACTION: Ensure that the NAU has been activated on the
host. |
MESSAGE: CLEAR request not received.
(SNAERR 112) | CAUSE: The primary session control has not sent a CLEAR. ACTION: Note the circumstances and contact your HP representative. |
|
