Bytes 2 and 3 following the sense code contain sense-code-specific
information.
- 0000
- No specific code applies.
VTAM® Information: When VTAM receives this sense code for
a session initiation, it continues searching through the adjacent
SSCP table until the destination LU is found or routing is exhausted.
VTAM hint: Possible causes
of this error include, but are not limited to, the following ones:
- If resources are not activating correctly when a new NCP is activated,
either rename the new NCP or use another method to make sure that
the old resource resolution table (RRT) is replaced with the new RRT.
- If you are trying to establish a session to a 3274, this error
can occur when DATMODE=HALF is not coded on the PU definition statement.
- A VARY INACT,FORCE command on a switched PU is turned into a VARY
INACT,REACT.
- If a USERVAR is defined, the USERVAR name is required for session
initiation instead of the real name.
- There is not enough storage to enable VTAM to add a dynamic application program to
the symbol resolution table (SRT).
- Another resource with the same name as a dynamic application program
that requests to open its ACB has already been defined.
- 0001
- The logical unit vector (LUV) table is too small.
- 0002
- Either the SSCP is not the owner, or it was not added by dynamic
reconfiguration.
- 0003
- Previous RNAA received for the same address. Check the LOCADDR
in the LU definitions.
- 0004
- Local address X'0000' specified for a logical unit added
to a cluster controller module (PU Type 2).
- 0005
- Attempted to switch the line mode when the link was already active.
- 0006
- The logical unit was specified at system generation as not available
for dynamic reconfiguration.
- 0007
- Attempted to switch the line mode while an activate link command
is in progress.
- 0008
- Attempted to switch the line mode while a deactivate link is in
progress.
- 0009
- Attempted to switch the line mode while a wrap is in progress
on this line.
- 000A
- Either the specified physical unit was not assigned to the specified
link, or the specified logical unit was not assigned to the specified
physical unit.
- 000B
- The logical unit or the physical unit was in active session.
- 000D
- A logical unit was still assigned to the physical unit.
- 000E
- The resource to be dynamically reconfigured is a system generated
resource and is defined as not DR-deletable.
- 000F
- An RNAA received from an SSCP is rejected because it specifies
a resource (adjacent link station or LU) that currently has an address
assigned as a result of the RNAA of another SSCP; or an ACTLU, FNA,
or SETCV received from an SSCP is rejected because it specifies a
resource address that is not assigned to an existing resource or is
assigned as a result of the RNAA of another SSCP.
- 0010–0013
- Set aside for implementation-specific use, and will not be otherwise
defined in SNA; see implementation documentation for details of usage.
- 0010
- Attempted to switch the line mode while a line trace or scanner
interface trace (SIT) is in process.
- 0014
- ANS mismatch discovered.
- 0015
- The type modifier (3270 indicator) is already set and does not
match the type modifier in this command.
- 0016
- The PU type on SETCV does not match the actual PU type.
- 0017
- The error-recovery modifier is already set and does not match
the error-recovery modifier in this command.
- 0018
- The pass limit is already set and does not match the pass limit
field in this command.
- 0019
- A SETCV was received containing a value for the SDLC BTU send
limit that conflicts with the previous value received.
VTAM hint: This sense code
can be displayed in a VTAM message,
but is set by another product. It might be an NCP sense code. See NCP, SSP, and EP Messages and Codes for
a complete description.
- 001A
- The maximum segment size is already set and does not match the
maximum segment size in this command.
- 001B
- The command specifies a pool indicator that is not X'00' or X'01'.
- 001C
- The RNAA request contains a network ID that is not known to the
gateway PU.
VTAM Information: When VTAM receives this sense code for
a session initiation, it continues searching through the adjacent
SSCP table until the destination LU is found or routing is exhausted.
- 001D
- An address-pair session key in a network-qualified address pair
control vector (X'15') is not known to the gateway PU.
- 001E
- A gateway PU received an RNAA request for a cross-network session
and all possible address transforms for the named resource are allocated.
VTAM Information: When VTAM receives this sense code for
a session initiation, it continues searching through the adjacent
SSCP table until the destination LU is found or routing is exhausted.
- 0020
- The gateway node receiving an RNAA request cannot support another
session between the named resource pair.
VTAM Information: When VTAM receives this sense code for a session
initiation, it continues searching through the adjacent SSCP table
until the destination LU is found or routing is exhausted.
- 0024
- A PU received an ACTPU request with the SSCP-PU session capabilities
control vector (X'0B') indicating that the sending SSCP does
not support ENA, but the PU does not know the SSCP’s maximum
subarea address value.
- 0025
- Set aside for implementation-specific use, and will not be otherwise
defined in SNA; see implementation documentation for details of usage.
VTAM hint: This
sense code can be displayed in a VTAM message,
but is set by another product. It might be an NCP sense code. See NCP, SSP, and EP Messages and Codes for
a complete description.
- 0026
- MAXOUT of zero received.
- 0027
- A request for a function was received by a component, but the
function was not enabled or activated.
- 0028
- Cleanup termination of an LU-LU session has been converted to
a forced termination by the LU. The SSCP must wait for session-ended
signals before deleting its session awareness records of the session.
- 0029
- Second-level application state change has occurred. An application
program served by an MS application program has changed the state
of a node that might result in the rejection or failure of a current
request or of a future request that would have previously been honored.
- 002A
- The route setup procedure identified in a session services request
was not in the expected state.
- 0030
- An FNA was received for an LU that has an active SSCP-LU session.
- 0031
- Bind failure: Mismatch of date, time, or NCP load module name.
The load module currently processing in the CCU does not match the
NPM resource resolution table (RRT) in use by NPM. The NCP generation
date, time, and load module name in the NPM RRT must match that in
the NCP exactly. Verification is through the user data in the bind
image.
- 0032
- A BFSESSINFO was received when the LU was not pending BFSESSINFO;
the reported sessions will be terminated, and the associated network
addresses will be freed. This sense data is also included in the
BFCLEANUP when the sessions are terminated.
- 0033
- A BIND with the same LFSID as an existing pending-reset session
has been received by a boundary function from a peripheral PLU.
- 0034
- A termination request has been received for a resource that has
been taken over by an SSCP. The termination type is not strong enough
to apply to the resources. The termination type needs to be forced
or cleanup.
- 0035
- A cross-domain resource, which was expected to be active, is inactive.
- 0036
- The short hold mode logical connection selected does not exist.
- 0037
- A non-short hold mode connection was attempted on a port (group)
that is dedicated to short hold mode operation.
- 0038
- There is an inconsistency of mode between the XID sender and receiver.
The XID receiver is operating in short hold mode. Examples include
inconsistent settings of the short hold indicator (SHI), the short
hold status indicator (SHSI), and the XID exchange state indicator.
- 0039
- CP Transaction Error: CP Capabilities (X'12C1') GDS variable
request sent indicating conversation complete or without change direction
(CEB or ¬CD) or CP Capabilities reply sent indicating conversation
not yet complete (¬CEB).
VTAM hint: This
sense code is set by VTAM in
the following situations:
- During contention winner CP-CP session activation.
- The execution of an APPCCMD CONTROL=ALLOC,QUALIFY=CONWIN instruction
to allocate a conwinner CP-CP session failed due to an unrecoverable
error, and APPC did not communicate to the issuing TP a non-zero sense
code at the time the ALLOC instruction was posted back. The RCPRI
and RCSEC return codes displayed in message IST1002I in the IST1110I
message group provide more information about the cause of the error.
- The execution of the APPCCMD CONTROL=RECEIVE,QUALIFY=SPEC instruction
to receive the capabilities of the adjacent CP completed successfully,
but the TP issuing that instruction was not notified that the partner
LU has unconditionally deallocated the conversation. You might want
to make the system programmer aware of this situation.
- During contention loser CP-CP session activation.
- The execution of the APPCCMD CONTROL=RECEIVE,QUALIFY=SPEC instruction
to receive the capabilities of the adjacent CP completed successfully,
but the partner LU did not enter RECEIVE state as expected. You might
want to make the system programmer aware of this situation.
- During contention winner or contention loser CP-CP session activation.
- The execution of an APPCCMD CONTROL=SEND,QUALIFY=DATA instruction
to send our CP capabilities to the adjacent CP failed due to an unrecoverable
error, and APPC did not communicate to the issuing TP a non-zero sense
code at the time the SEND was posted back. The RCPRI and RCSEC return
codes displayed in message IST1002I in the IST1110I message group
provide more information about the cause of the error.
- The execution of the APPCCMD CONTROL=RECEIVE,QUALIFY=SPEC instruction
to receive the adjacent CP's capabilities failed due to an unrecoverable
error, and APPC did not communicate to the issuing TP a non-zero sense
code at the time the RECEIVE was posted back. The RCPRI and RCSEC
return codes displayed in message IST1002I in the IST1110I message
group provide more information about the cause of the error.
- The execution of the APPCCMD CONTROL=RECEIVE,QUALIFY=SPEC instruction
to receive the adjacent CP's capabilities completed successfully,
but something other than data was received from the partner CP. You
might want to make the system programmer aware of this situation.
- 003A
- A null XID was received when an XID3 with its exchange state indicators
set to "prenegotiation," "negotiation proceeding,"or "exchange
state indicators not supported" was expected.
- 003B
- A null XID was received when a nonactivation XID3 was expected.
- 003C
- An XID3 with the exchange state indicators set to "prenegotiation"was
received when either of the values "negotiation proceeding" or "exchange
state indicators not supported" was expected.
- 003D
- A nonactivation XID3 was received when a null XID or link-activation
XID3 was expected.
- 003E
- A link activation XID3 was received when a null XID or nonactivation
XID3 was expected.
- 003F
- The node with a secondary link station attempted to initiate a
nonactivation exchange when secondary-initiated nonactivation exchanges
are not supported on the connection.
- 0040
- A mode-setting command was received and was either not expected
or not valid for the receiving node; for example, SNRME was received
when SNRM was expected.
- 0041
- An XID3 with the Exchange State indicators specifying a negotiation-proceeding
exchange was received when an XID3 indicating a prenegotiation exchange
was expected. If prenegotiation XID3s are used in a link activation
XID exchange, each node must send and receive one.
- 0042
- On an ABM TG on which secondary-initiated nonactivation XID exchanges
are supported, the adjacent link station has initiated a nonactivation
exchange by sending a nonactivation XID3 in which the ABM Nonactivation
XID Exchange Initiator indicator specifies that the sending node is
not initiating a nonactivation exchange. On such TGs, the initiator
of a nonactivation exchange always explicitly indicates that it is
initiating a nonactivation exchange.
- 0046
- An XID3 indicating that the sender supports the Exchange State
indicators was received when the sender had previously indicated that
it does not support this field in XID3.
- 0047
- An XID has been received after receipt of a mode-setting command
but before the completion of the mode-setting sequence, for example,
before RR, RNR, or an I-frame with the poll bit set has been sent
by the node with the primary link station after it has received UA
in response to its mode-setting command.
- 0048
- A node with an NRM primary link station has received an XID3 when
it has no outstanding commands. NRM secondary link stations send
XIDs only in response to XID commands.
- 0049
- The XID3 received from the adjacent node had an XID negotiation
error (X'22') control vector appended. The XID exchange will therefore
terminate unsuccessfully.
- 004A
- The request cannot be accepted because dynamic reconfiguration
is in process for the target resource.
- 004B
- Set aside for implementation-specific use, and will not be otherwise
defined in SNA; see implementation documentation for details of usage.
VTAM hint: This
sense code can be displayed in a VTAM message,
but is set by another product. It might be an NCP sense code. See NCP, SSP, and EP Messages and Codes for
a complete description.
- 004C
- Set aside for implementation-specific use, and will not be otherwise
defined in SNA; see implementation documentation for details of usage.
VTAM hint: This
sense code can be displayed in a VTAM message,
but is set by another product. It might be an NCP sense code. See NCP, SSP, and EP Messages and Codes for
a complete description.
- 004D
- Set aside for implementation-specific use, and will not be otherwise
defined in SNA; see implementation documentation for details of usage.
VTAM hint: This
sense code can be displayed in a VTAM message,
but is set by another product. It might be an NCP sense code. See NCP, SSP, and EP Messages and Codes for
a complete description.
- 004E
- A node with a secondary NRM link station attempted to initiate
a nonactivation XID exchange with an XID3. Nodes with secondary NRM
link stations can solicit a nonactivation XID3 exchange only by sending
a null XID at a response opportunity.
- 0050
- An UNBIND request was received on behalf of a resource for which
a previous UNBIND is in progress. The second UNBIND does not indicate
an override of the first, and is therefore a duplicate request.
- 0051
- Set aside for implementation-specific use, and will not be otherwise
defined in SNA; see implementation documentation for details of usage.
VTAM hint: This
sense code can be displayed in a VTAM message,
but is set by another product. It might be an NCP sense code. See NCP, SSP, and EP Messages and Codes for
a complete description.
- 0052
- Set aside for implementation-specific use, and will not be otherwise
defined in SNA; see implementation documentation for details of usage.
VTAM hint: This
sense code can be displayed in a VTAM message,
but is set by another product. It might be an NCP sense code. See NCP, SSP, and EP Messages and Codes for
a complete description.
- 0053
- An activation request was received for a CDRM whose subarea address
is already known by another CDRM name.
- 0054
- An adjacent node is not the node type that the receiving node
was configured to expect.
- 0055
- The adjacent node is attempting to establish a connection through
a connection network but the virtual routing node CP named in the
TG Descriptor (X'46') control vector appended on the received negotiation-proceeding
XID3 is not valid.
- 0056
- Locate Phase Error: A Locate GDS variable was received that
contained an incorrect request-reply-chain status field; for example,
c reply was received while the receiver was in chain state.
- 0057
- The received NOTIFY type is not supported in the current state
of the receiver.
- 0058
- An intra-FRSE PVC segment subport received an RNAA (assignment
type X'5') with a DLC header link station address field containing
a value outside the valid range. The RNAA is rejected.
- 0059
- An intra-FRSE PVC segment subport received an RNAA with a control
vector X'43' specifying discontinue link-level contact if an auto
network shutdown procedure is initiated. The RNAA is rejected.
- 005A
- RNAA was received to add an intra-FRSE PVC segment subport to
a hierarchical physical resource that is not active.
- 0060
- An intra-FRSE PVC segment subport received an RNAA with a control
vector X'43' specifying that modem test support is permitted. The
RNAA is rejected.
- 0061
- An intra-FRSE PVC segment subport received an RNAA with a control
vector X'43' frame send control value field containing a value outside
the valid range. The RNAA is rejected.
- 0062
- An intra-FRSE PVC segment subport received an RNAA with a control
vector X'43' node type identifier field specifying a node type other
than T1. The RNAA is rejected.
- 0063
- An intra-FRSE PVC segment subport received an RNAA with a control
vector X'43' specifying that null XID polling for the secondary station
should be used. The RNAA is rejected.
- 0064
- A SETCV defining an intra-FRSE PVC segment subport set was received
that contained an element address in the DR pool.
- 0065
- A SETCV defining an intra-FRSE PVC segment subport set was received
from an SSCP that did not originally add all the subarea element addresses
listed in the SETCV to the DR pool.
- 0066
- An ACTTRACE was received for a link connection trace while a trace
for a logical link using that link connection was active, or ACTTRACE
was received for a logical link trace while a trace for its underlying
physical link connection was active.
- 0067
- An intra-FRSE PVC segment subport received an RNAA5 containing
a DLC Header Link Station Address that is being used by an existing
frame relay terminating equipment subport.
- 0068
- An XID was received with a networking capabilities indicator (specifying
whether the sender is an APPN network node) that is not consistent
with the receiver definition for the connection. The connection is
rejected.
- 0069
- An XID was received with CP services and CP-CP session support
indicators that are not consistent with the receiver definition for
the connection. The connection is rejected.
- 006A
- A node type mismatch exists between the two SSCPs setting up a
VRTG.
VTAM hint: VTAM sets this sense code when
a VRTG connection is rejected because the VRTG partner host is configured
as an unexpected node type.
- 006B
- The IP address specified in an RNAA(Type=X'05') for a
new internet protocol (IP) PU is a duplicate of an existing IP address.