Sense code 0877

Resource mismatch: The receiver of a request has detected a mismatch between two of the following resources: (1) its definition of an affected resource, (2) the actual configuration, and (3) the definition of the resource as implied in the request.

Bytes 2 and 3 following the sense code contain sense-code-specific information.

0000

No specific code applies.

0001

Link defined as switched is nonswitched: A link defined to an ACTLINK receiver as being switched was found to be nonswitched during the activation attempt.

0002

Link defined as SDLC is non-SDLC: A link defined to an ACTLINK receiver as being SDLC was found to be non-SDLC during the activation attempt.

0003

Link defined as having automatic connect-out capability does not: A link defined to an ACTLINK receiver as having automatic connect-out capability was found to lack it during the activation attempt.

0004

ACTLINK received for a resource other than a link: An ACTLINK was received that resolved to a local device number representing a device other than a link.

0005

Link defined as X.21 is not X.21.

0006

Link defined as LPDA-capable is configured in NRZI mode.

0007

A request that is allowed only for a primary link station was received for a link station that is defined to the receiver as secondary.

0008

A request for link problem determination for modems was received for a link that is defined to the receiver as not supporting link problem determination for modems.

0009

A request for link problem determination for modems was received for a link that is defined to the receiver as a supporting link, but no problem determination support for modems was found on the link.

000A

A request that is allowed only for a nonswitched link was received for a link that is defined to the receiver as switched.

000B

A request that is allowed only for a link with a modem not using the multiplexed links feature was received for a link that is defined to the receiver as having a modem using the multiplexed links feature.

000C

Resource definition mismatch for modems: A request that is allowed only for a link with a nontailed modem was received for a link that is defined to the receiver as having a tailed modem.

000D

The sending SSCP and the receiving Type 4 node having conflicting system definitions. A BIND has been received for an SLU that contains an incorrect SLU address. The LU address in the BIND is a primary address. The LU address cannot be used for a secondary role on a new session.

000E

The sending SSCP and the receiving Type 4 node have conflicting system definitions. A BIND has been received for an independent LU, but the LU specified is not in a Type 2.1 node.

000F

The sending SSCP and the receiving Type 4 node have conflicting system definitions. The SSCP owner is the same as the SSCP sending the nonactivation CONTACT PIU but the PU is not a Type 2.1. The CONTACT is for a Type 2.1 node, but the PU is not defined as Type 2.1 to the receiver.

0010

The BFCLEANUP is for an independent LU, but the LU specified is not an independent LU.

0011

The subarea address portion of an addressed LU is not equal to the subarea address of the Type 4 node. The LU is not in the same subarea as the Type 4 node.

0012

If the BFCLEANUP is for a resource that is not a BF LU, the request will be rejected. This is a situation where the function is not supported by the target resource. It can be caused by a SYSDEF mismatch between the Type 4 node and the SSCP.

0013

The network ID field in the BIND SLU name is not equal to the network ID of the boundary function, or the SLU name field is not equal to the LU name field in the boundary function control block for the LU.

0014

The LU specified in the FNA is not associated with the PU specified in the FNA; that is, an LU address (byte 7–n) is not associated with the PU target address specified.

0015

BFCINIT name mismatch: The BIND cannot be built from the BFCINIT because the NQ PLU name does not match. The session activation is rejected by the boundary function with a BFTERM.

0016

Invalid target address; either:

The PU with which the specified LUs are to be associated is not Type 1 or Type 2; that is, the SSCP attempts to add an LU to a PU, but the boundary function has defined that PU as a Type 4.
The SSCP sent an RNAA assignment Type X'0' or X'5' with a PU or LU specified instead of a link. This is caused by a definition mismatch.

0017

MAXSUBA required for pre-ENA address assignment: If MAXSUBA is not specified and an RNAA requesting a pre-ENA address is received, the RNAA is rejected.

0018

An RNAA Type 4 was received requesting an auxiliary address on a dependent LU.

0019

Multiple sets of dial information are specified for a native ATM call when only one set is allowed.

VTAM® hint: A possible cause of this error is that more than one DLCADDR operand (subfield 1 or 21) is specified on the following definition statements in the following major nodes:

GROUP definition statement in the XCA major node (TGs to connection networks)
PATH definition statement in the switched major node (TGs over SVCs)

001A

The target LU specified in a BFCLEANUP or BFCINIT is not associated with the same link station that is associated with the session indicated in the URC control vector.

001B

The target link station specified in a BFCLEANUP is not the same link station as the session indicated in the URC control vector.

001C

Resource definition mismatch for BFCINIT: The sending SSCP and the receiving Type 4 node have conflicting system definition. A BFCINIT has been received for an LU address that is currently being used by an active LU-LU session. The LU address is primary on this already active session. The LU address cannot be used for a secondary role on a new session.

001D

The LU address in the BFCINIT is a secondary address; the BFCINIT is rejected.

001E

The subject LU specified in the BFSESSINFO RU is not defined to the SSCP as an independent LU; this is a mismatch between the SSCP and the BF.

001F

A dependent LU is attached to a PU that indicates ACTPU is to be suppressed; the SSCP cannot activate the LU because ACTLU is not supported.

VTAM hint: The PU sent an XID that had the ACTPU suppression bit turned on. You need to reconfigure the PU to correct the error.

0020

A peripheral node supporting independent LUs has attached (using a nonswitched link) to a Type 2 PU that cannot have independent LU sessions through it. The SSCP activation request received for one of these independent LUs has failed.

0021

An RNAA(Add) was received by the boundary function for a resource defined at system definition time, which is not allowed.

VTAM hint:

A physical connection must exist for a resource if you are attempting to use dynamic reconfiguration. For more information about dynamic reconfiguration, see z/OS Communications Server: SNA Network Implementation Guide.
This error can occur for a physical unit if a network address has been specified on the ADDR operand of the PU definition statement, but there is no physical connection for the resource. For more information about the ADDR operand, see z/OS Communications Server: SNA Resource Definition Reference.

0022

The link for which ACTLINK was issued is an S/390® channel path that has been defined for connections only to a Type 2.1 node. However, the SSCP that sent ACTLINK had previously indicated it does not support Type 2.1 connections.

0023

Modem test support cannot be changed. The RNAA or SETCV containing the SDLC secondary station (X'03') or the extended SDLC secondary station (X'43') control vector is rejected.

0024

The data mode cannot be changed. The RNAA or SETCV containing the SDLC secondary station (X'03') or the extended SDLC secondary station (X'43') control vector is rejected.

0025

The receiving node is unable to process a BIND for the LU type specified for the given LU name.

0026

A link is defined as not supporting HPR, but the port supports only HPR links.

VTAM hint: Possible reasons for this error include, but are not limited to, the following ones:

A connection over a native ATM SVC cannot be established because the TG is not defined to support APPN and HPR.
One or more values are coded incorrectly on a PU definition statement in a switched major node that defines an APPN TG over a native ATM SVC. These incorrect values might be on the HPR, CONNTYPE, or PUTYPE operands, which must specify HPR=YES, CONNTYPE=APPN, and PUTYPE=2 for native ATM connections. Any other values coded on these operands cause a connection over a native ATM SVC to fail.
Dial-out or dial-in attempts to establish a session over an Enterprise Extender connection fail.
The selected link station does not have HPR=RTP capability. To resolve this problem, specify one of the following start options:
- Start option HPR=RTP
- Start option HPR=(RTP,ANR). Specify HPR=YES either on the PU definition statement or on the operator command activating the PU.

0027

A link connection request for a non-empty active link connection configuration was received by the management services element; the active link connection configuration of the DLC element is empty; that is, it has no link connection components present.

0028

An RNAA(Move) was received for an adjacent link station (ALS), and the TO and FROM links were neither both primary nor both secondary.

0029

The RU refers to a resource, and the sender and receiver disagree about its status. One considers it a static resource, the other a dynamic resource.

002A

A session cannot be activated because the node does not support segment generation and the maximum link BTU size is too small to satisfy a requirement on the minimum send RU size as defined for the session mode.

002B

A session cannot be activated because the node does not support segment reassembly and the maximum link BTU size is too small to satisfy a requirement on the minimum receive RU size as defined for the session mode.

002C

BFSESSINFO was received reporting a subject LU in another network, or BFINIT was received with a NETID specified for the PLU which was not the same as the NETID of the ALS (XNETALS=YES) or the receiving SSCP (XNETALS=NO).

002D

BFSESSINFO was received for an (independent) subject LU, but the reported LU is considered by the receiver as a dependent LU.

002E

BFSESSINFO was received reporting a dynamic subject LU that the receiver considers to be located under a different adjacent link station (ALS) than that reported in the BFSESSINFO. The SSCP will attempt to correct this configuration mismatch.

002F

BFSESSINFO was received reporting a subject LU that the receiver considers to be located under a different adjacent link station (ALS) than that reported in the BFSESSINFO. The SSCP cannot correct this configuration mismatch.

0030

BFSESSINFO was received for a subject LU, but the receiver has the address associated with a different LU, which it considers to be static.

0031

BFSESSINFO was received for a subject LU, but the receiver has the address associated with anything other than a static LU or cross-domain resource.

0032

BFSESSINFO was received for an LU. The subject LU is verified, but, for a given session, either the partner LU is reported as the primary and the receiver does not consider that LU to be primary-capable, or the partner LU is reported as the secondary and the receiver does not consider that LU to be secondary-capable.

0033

Upon receipt of BFSESSINFO, the receiver considers the control block associated with a partner LU to be a cross-domain resource that is not active or an application that is not active.

0034

Upon receipt of BFSESSINFO, the receiver considers the control block associated with a partner LU to be neither an LU, cross-domain resource, nor an application.

0035

A network address was returned in RSP(RNAA) that the receiver believes is already associated with a different resource.

0036

BFSESSINFO was received containing an adjacent link station (ALS) address that was not valid. For example, the ALS does not represent a Type 2.1 node.

0037

BFSESSINFO was received for a subject LU, where the secondary address specified in the BFSESSINFO does not match the secondary address the SSCP believes is associated with the LU.

0038

The subject LU specified in the BFSESSINFO RU is not defined to the SSCP as an LU or a cross-domain resource.

0039

A request that is valid only for a switched subarea link was received for a link that is not subarea-capable.

003A

A request that is valid only for a nonswitched subarea link was received for a subarea dial link.

003B

An RNAA (add) was received for an LU; however an LU with the same name but a different local address already exists under the specified ALS.

0041

Takeover processing completed, but the SSCP did not receive a BFSESSINFO for a resource that the SSCP believed to be a static, independent LU.

0042

A BFINIT sent by the boundary was processed by the SSCP and the PLU resource is not owned by this SSCP. This is probably the result of a TAKEOVER and GIVEBACK occurring before the BFINIT was processed by the SSCP. This might also be caused by a definition error for the PLU.

0043

A request was received for a nonswitched resource that is valid only for a switched resource.

0044

X.21 dial and auto-call capability not present—resource mismatch.

0045

A session request was received and the NETID for the resource does not match that of the adjacent link station providing service for the resource.

VTAM hint: When a VTAM host has a Type 2.1 connection to a gateway NCP (XNETALS=YES is specified), a different VTAM host must own the Type 5 connection to the NCP.

0046

A CONNOUT was received indicating the sender and receiver have a system-definition mismatch: the CONNOUT connection type field specified a nonswitched link, but the receiver does not define the affected node as a T2.1 node on a nonswitched link or as one that supports XID3 exchange.

VTAM hint: This sense code can be displayed in a VTAM message but is set by another product. It might be issued by NCP. See NCP V7R8, SSP V4R8, EP R14 Messages and Codes for a description of sense codes set by NCP.

0047

A session request or BFSESSINFO request was received and the network ID for the OLU or the subject LU does not match that of the adjacent link station providing service for the resource.

0048

The DLU is an independent LU but the selected boundary function is not independent LU capable.

0049

A BFSESSINFO request was received but the subject resource is not active.

0050

The element address of an intra-FRSE PVC segment subport specified in a SETCV resides on the same frame-relay port as another subport within a subport set.

0051

The maximum frame size in the system — definition differs for any two partners in an intra-FRSE PVC segment subport set specified in a SETCV.

0052

Adjacent frame-relay equipment management protocols are not supported on either of the frame-relay ports for the primary or its backup subport specified in the SETCV for the intra-FRSE PVC segment subport set.

VTAM hint: A possible cause of this error is that there is a conflict in the coding of the PU definition and the FRSESET definition.

A backup PU has been coded in the FRSESET definition statement, but either this backup PU or its corresponding primary PU was coded on a line that has LMI=NO coded.

In order to have backup, the primary and backup PUs must be defined on lines whose link-station subport supports local management interface (LMI) protocol (LMI=ANSI or LMI=CCITT coded on the first PU definition statement under the LINE definition statement). For information about the LMI keyword, see NCP, SSP, and EP Resource Definition Reference.

0053

A node identifies itself as a extended border node for some sessions but claims not to be a extended border node for other sessions.

VTAM hint: This sense code can be displayed in a VTAM message, but is set by another product.

0054

SETCV was received to define an intra-FRSE segment subport set between subports that are incompatible; one of the subports does not support alternate physical paths.

0055

SETCV was received to define an intra-FRSE segment subport set between subports that are incompatible; one of the subports is on an outboard DLC and the other is not on an outboard DLC.

0056

A CPSVRMGR session cannot be established over a LEN connection that is not of type TCP.