Sense code 1016

XID Format 3 parameter error: Data in the XID3 is not acceptable to the receiving component because the value in the received XID3 field, whose byte and bit offset is specified by the XID negotiation error (X'22') control vector (which also carries this sense data), is inconsistent with the corresponding field in the sent XID3.

Bytes 2 and 3 following the sense code contain sense code specific information.
0000
No specific code applies.
0001
The field in the received XID3 that specifies the maximum number of I-frames that the sender can receive before acknowledgment is set to zero.
0002
The adjacent node has been inconsistent in its request for ACTPU. In a nonactivation XID3 exchange, it has changed the value of the ACTPU suppression indicator sent in the previous XID3 exchange.
0003
The field in the received XID3 that specifies the maximum BTU length that the sender can receive is set to less than 99 bytes, the minimum required.
0004
The received XID was not XID Format 3 when XID Format 3 was expected.
0005
The adjacent node does not support BIND segment generation but does support receipt of BIND segments. Any T2.1 node supporting receipt of BIND segments must also support generation of BIND segments.
0006
The adjacent node is an end node, does not support BIND segment receipt, and has a maximum BTU size of less than 265, the minimum required in this case.
0007
The adjacent node is a network node, does not support BIND segment receipt, and has a maximum BTU size of less than 521, the minimum size required in this case.
0008
The adjacent node has changed its networking capabilities in an XID3 from those declared in the previous negotiation-proceeding or nonactivation XID3. A node may not change from an end node to a network node or from a network node to an end node in two different negotiation-proceeding or nonactivation XID3s.
0009
The adjacent node is an APPN network node, does not provide CP services, and supports CP-CP sessions, a combination not allowed.
000A
During a nonactivation XID3 exchange, the adjacent node has changed the TG number that was negotiated during the activation exchange.
000B
The adjacent node is the TG number negotiation winner and designates a TG number that the receiving node cannot allocate to this connection. When parallel TGs are supported between the two nodes, zero is always such a number.
Tip:
  • This sense code occurs when two VTAMs are attached by a 3172 token ring and channel-to-channel connections or any other type of connection in parallel to a 3172 connection. After deactivation of a VTAM® node with 3172 connections, you should do one of the following actions:
    • Wait at least four minutes before attempting to restart the failed VTAM.
    • Attempt reattachment of the 3172 connections to adjacent nodes first to prevent TG number contention.
  • If you receive this sense code in message IST1085I and the PU name in the preceding IST590I message is an Enterprise Extender (EE) PU, this connection traverses EE. If this connection traverses EE, a duplicate CP name might be in the network. From the host where the 1016000B sense code was received in message IST1085I, issue a DISPLAY EE,CPNAME= command, where CPNAME specifies the resource name from the IST1085I message. This command will show information about the CP with the active EE connection.
000C
The adjacent node is an APPN network node that does not support BIND segment generation, and this node has a maximum BTU receive size of less than 521. This node might, therefore, be unable to receive a BIND with RSCV from the adjacent network node.
000D
The adjacent node indicates that it does not support the SDLC command/response profile in its XID3. This is the only command/response profile supported by APPN and LEN nodes.
000E
Different product set IDs have been given in the product set ID (X'10') control vectors appended to two different received XID3s from the same adjacent node.
000F
The link station roles specified in the sent and received negotiation-proceeding XID3s are not compatible. To activate a connection, one node must contain a primary link station; the other, a secondary link station.
0010
The support of combined asynchronous balanced mode link stations indicated in the sent and received negotiation-proceeding XID3s is not in agreement.
0011
A received XID3 indicates an attempt to activate multiple connections has been made when parallel transmission groups are not supported between the two nodes involved in the XID exchange.
0012
The adjacent node has sent the network name (X'0E', CP name) control vector in XID3 but indicates it does not support the exchange state indicators.
0013
The DLC type indicated in the sent and received negotiation-proceeding XID3s is not in agreement.
0016
This TG is predefined in this node (range 1–20) but the TG number received in the XID3 from the adjacent node is not the same.

Tip: If you receive this sense code while you are trying to establish a connection with a dynamic EE PU, the dialing side of the connection receives an INOP notification. The cause of the problem might be that none of the TGNs specified on the EE model PU are available.

0018
The adjacent node is an APPN node but does not support adaptive BIND pacing as a sender and receiver.
001A
The adjacent node is inconsistent in its support of parallel TGs. Support of parallel TGs between two nodes cannot change either in link-activation XID exchanges on different TGs or in successive XID exchanges on the same TG.
001B
The adjacent node provides or requests CP services but does not support CP-CP sessions; for example, Bytes 8–9, bits 10–11 of the received negotiation-proceeding XID3 were set to ten, a setting combination not allowed for T2.1 nodes.
001F
The setting of the intersubnetwork link indicator of the TG descriptor control vector received in XID3 is inconsistent with the receiving node system definition. This sense data value is issued only if both sender and receiver support the setting of this bit.
0021
During a negotiation-proceeding XID3 exchange, one node specifies in the HPR capabilities (X'61') control vector that error recovery is required, but the other node specifies no error recovery is required. HPR protocols will not be used on this TG. (This sense data is not carried in the XID negotiation error (X'22') control vector.)
Tip: The link activated as a non-HPR link due to a disagreement between the link partners on the level of error recovery procedures (ERP) to be used. Check the value of the LLERP parameter associated with the VTAM PU, as well as the level of ERP supported for that DLC type by the link partner.
0022
The adjacent node is an HPR node (that is, it included an HPR capabilities (X'61') control vector in XID3), but is specified a maximum BTU size less than 768.
Tip: This sense code can also be issued at the following times:
  • At XID time for a Local SNA (CDLC) connection if the maximum PIU size (a factor of the IOBUF size multiplied by the MAXBFRU value) is less than 525 bytes.
  • At XID time for a TCP/IP CDLC connection if the product of the write_buffers times write_size, specified on the DEVICE statement, is larger than the read capacity on the read side.
0023
The adjacent node is an HPR node (that is, it included an HPR capabilities (X'61') control vector in XID3), but it specified an ANR label length that was not valid (for example, less than one or greater than eight).
0024
The adjacent node is an HPR node (for example, it included an HPR Capabilities (X'61') control vector in XID3), but the receiving node detected that it specified a CP NCE identifier length that was not valid (for example, less than one or greater than eight).
0025
The adjacent node is an HPR node (for example, it included an HPR Capabilities (X'61') control vector in XID3), but the receiving node detected that it specified a route setup NCE identifier length that was not valid (for example, less than one or greater than eight).
0026
The adjacent node is an HPR node (for example, it included an HPR Capabilities (X'61') control vector in XID3), but the receiving node detected that the length of the HPR Transport Tower (X'81') subfield of the control vector is inconsistent with the length of a field included in the subfield.
0031
The link being activated by this node requires the link to support HPR, be RTP capable, and support the control flows over RTP tower. The adjacent node has indicated that it does not support HPR for this link.
0032
The link being activated by this node requires the link to support HPR, be RTP capable, and support the control flows over RTP tower. The adjacent node has indicated that this link is not RTP capable.
0033
The link being activated by this node requires the link to support HPR, be RTP capable, and support the control flows over RTP tower. The adjacent node has indicated that it does not support control flows over RTP for this link.
0034
The link being activated by this node requires the support of logical data link control (LDLC) during XID exchange for this link. The adjacent node has indicated that it does not support LDLC for this link.
0035
A negotiable or zero TG number was received in XID3, but multiple links are defined between the switched ports. Use of predefined TG numbers is required.
0047
The link being activated by this node requires the link to support HPR, be RTP capable, and support the control flows over Enterprise Extender. The adjacent node has indicated that this link is not RTP capable.
Parent topic: 10XX (request error)