Sense code 0806

Resource unknown: For example, the request contained a name or address not identifying a PU, LU, SSCP, link, or link station known to the receiver or the sender.

Note: In an interconnected network environment, this sense code might be set by an SSCP in whose subnetwork and domain the LU was expected to reside; it is not set by an SSCP that is only an intermediary on the session-setup path. A gateway SSCP examines the resource identifier control vector in a session setup request (for example, CDINIT), to determine whether the LU is in the SSCP’s subnetwork and domain.

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: A possible cause of this error is that uservarname has been specified on the ID operand of the DISPLAY NCPSTOR command.

0001

The resources identified in an SNA address list (X'04') MS common subvector are unknown to the PU receiving the request.

Note: When this sense data flows in a negative response to a network management vector transport (NMVT), the referenced X'04' subvector is the one that was present in the request NMVT to which the negative response corresponds. When this sense data flows in a sense data (X'7D') MS common subvector, the referenced X'04' subvector is present with the X'7D' subvector in the same major vector.

0002

Set aside for implementation-specific use, and will not be otherwise defined in SNA; see implementation documentation for details of usage.

VTAM issues this code in response to an NPM session collection request for an undefined resource to indicate that the request was successful.

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 V7R8, SSP V4R8, EP R14 Messages and Codes for a complete description.

0004

The indicated resources in the accompanying name list (X'06') subvector are unknown to the control point to which the request containing the subvector was routed.

Note: Names in the hierarchy below the level of the first unknown resource are not examined by the control point.

0005

The physical unit is currently in the physical unit dynamic reconfiguration pool.

0006

For a dynamic reconfiguration DELETE, MOVE, or REPLACE operation, the resource to be dynamically reconfigured could not be found.

0007

The LU address in bytes 8–9 of RNAA Type X'04' is already in the free pool.

0008

For a dynamic reconfiguration DELETE, MOVE, or REPLACE operation, the NAU name in RNAA does not correspond to the resource identified by the element address in the RNAA.

0009

The SSCP(OLU) cannot identify the SSCP(DLU), and the default SSCP rerouting is not enabled.

000A

The configuration identifier specified in a management services command is not recognized by the DLC manager at the receiving node.

0011

An unknown OLU name was specified in the request.

0012

An unknown DLU name was specified in the request.

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:

No CDRMs are active.
No CDRSC exists for the DLU, and one cannot be created dynamically because CDRDYN=NO. Verify that a host CDRM definition exists and is activated if this node was started with a subarea number, and ensure that CDRDYN=YES is specified on the CDRM definition. See z/OS Communications Server: SNA Resource Definition Reference for information about the CDRDYN operand.

0013

An unknown SLU name was specified in the request.

0014

An unknown PLU name was specified in the request.

0015

An unknown OLU address was specified in the request.

0016

An unknown DLU address was specified in the request.

0017

An unknown SLU address was specified in the request.

0018

An unknown PLU address was specified in the request.

0021

The session-initiation request specified that the receiving SSCP is the SSCP having the DLU in its domain, but the DLU is unknown to the receiving SSCP. This error can occur if a CDRM is coded incorrectly on the CDRSC definition statement.

0022

The originator of the request or response is unknown to the receiver.

0023

The destination of the request or response is unknown to the sender.

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

An unknown LU1 name was specified in the request.

0025

An unknown LU2 name was specified in the request.

0026

The SSCP does not have a session with the boundary function PU of an independent LU.

0027

The PU associated with a switched SLU is unknown. Session setup processing for the switched SLU cannot proceed.

0028

NAU1 network address is unknown.

0029

NAU2 network address is unknown.

002A

The NAU name in the CONTACT or ACTLU does not correspond to the resource at the target address.

002B

The TG being activated is unknown.

002C

The identification supplied by the adjacent node in its XID3 differed from the identification that the receiving node was configured to expect.

002D

Set aside for implementation-specific use, and will not be otherwise defined in SNA; see implementation documentation for details of usage.

002E

Set aside for implementation-specific use, and will not be otherwise defined in SNA; see implementation documentation for details of usage.

002F

The destination resource was not found on this node during a session activation attempt.

0030

The adjacent node was not identified during CP-CP session activation or deactivation.

0031

Upon receiving a route request from another component in the node, TRS has been unable to locate in its topology database the destination network node or any network node specified in the TG vectors for the destination end node; the request is rejected.

0032

A SETCV defining an intra-FRSE PCV segment subport set was received containing an element address unknown to the receiver.

0033

A network resource needed for session establishment has become unavailable resulting in the termination of the pending session establishment procedure.

0034

REQDACTPU received for an unknown PU.

VTAM hint: This sense code is set by VTAM when processing the REQDACTPU request received from the dependent LU requester (DLUR) to deactivate the PU, but the PU is not known to VTAM. VTAM will send a negative REQDACTPU response with the sense code to the DLUR.

Verify that the PU name is specified correctly in the PU definition for the switched major node and in the DLUR definitions. If you have a system where PUs are being dynamically created, verify that the PU name is specified correctly in either the NIDDEF or CPNDEF definitions and in the DLUR definitions.

0035

The local node has received an unknown adjacent CP name in a request to activate or deactivate a CP-CP session.

0036

No SSCP-SSCP session exists between the VRTG end points.

VTAM Information: VTAM sets this sense code when a CDINIT(5) or DSRLSR(4) cannot be sent because there is no SSCP session between the VR-based TG (VRTG) endpoints. A VRTG, although it creates the appearance of APPN, always represents underlying subarea connectivity and the existing subarea requirement that every SSCP in the network must have an active CDRM session with every other SSCP in that network is still in effect. See the information about VRTGs in z/OS Communications Server: SNA Network Implementation Guide .

3426

Product-specific sense code.

VTAM hint: This sense code can be displayed in a VTAM message but is set by another product. It might be issued by CICS®. If issued by CICS, bytes 2 and 3 map to a CICS message number. See http://www-01.ibm.com/software/htp/cics/library/ for additional information about CICS messages and codes.