IST467I

Explanation
 This message is the first in a group of messages.
A complete description of the message group follows.   IST467I  CONTACTED ERROR TYPE type FOR ID = nodename
[IST1580I  XID RECEIVED BY VTAM:]
[IST1574I    offset hexdata_1 hexdata_2 hexdata_3 hexdata_4 EBCDIC_data]
⋮
[IST1574I    offset hexdata_1 hexdata_2 hexdata_3 hexdata_4 EBCDIC_data]
[IST1582I    CONTROL VECTOR X'22' ANALYSIS:]
[IST1583I      BYTE OFFSET OF FIRST BYTE IN ERROR = byteoffset]
[IST1584I      BIT OFFSET OF FIRST BIT IN ERROR = bitoffset]
[IST1585I      SENSE CODE = sense]
[IST1586I  XID SENT BY VTAM:
[IST1574I    offset hexdata_1 hexdata_2 hexdata_3 hexdata_4 EBCDIC_data]
⋮
[IST1574I    offset hexdata_1 hexdata_2 hexdata_3 hexdata_4 EBCDIC_data]
[IST1582I    CONTROL VECTOR X'22' ANALYSIS:]
[IST1583I      BYTE OFFSET OF FIRST BYTE IN ERROR = byteoffset]
[IST1584I      BIT OFFSET OF FIRST BIT IN ERROR = bitoffset]
[IST1585I      SENSE CODE = sense]
IST314I  END

 IST467I  The activation procedure for nodename failed
because of an error specified by the CONTACTED RU error type.
 Notes: If the XID received from the adjacent node contains no data (XID(NULL)), VTAM® does not issue messages IST1574I,
IST1580I, or IST1582I through IST1585I.
For a type of 05, 07, and 08, VTAM displays the XID data received
from and sent to the adjacent node. The information received from
the adjacent nodes is displayed in messages IST1580I and IST1574I.
The information sent to the adjacent nodes is displayed in messages
IST1586I and IST1574I. The IST1582I subgroup follows the XID to which
it refers.
For a type of 0B, VTAM displays the XID data received from the
adjacent node, or sent to the adjacent node, or both. The information
received from the adjacent nodes is displayed in messages IST1580I
and IST1574I. The information sent to the adjacent nodes is displayed
in messages IST1586I and IST1574I. The IST1582I subgroup follows the
XID to which it refers.

type can be one of the following:  02
Load Required. No fields follow.
03
A CONTACT RU error occurred during processing; no XIDs are available.
The routes between the activating host and the target NCP might be
defined incorrectly.
05
Exchanged XID parameters are not compatible. Possible reasons
include:  The transmission group numbers do not match or the transmission
group number is zero in both nodes.
The adjacent PU is not able to accept the XID parameter.
If this is not a transmission group problem, ensure that HOSTSA
has been coded in your start list. If HOSTSA is not coded in either
start list, you might get this error.
There might be a lack of storage in the channel-attached hosts.

07
No routing capability to the adjacent node.
08
VTAM cannot add the link
station to the currently active TG. Possible reasons include:  XID parameters are incompatible with other links in an NCP multilink
transmission group.
There is another active TG with the same TG number connecting
the same two subareas. One of the subareas is a VTAM host.
This host has a connection to another node with the same subarea
number as the one being activated.
NCP will set this error type if the MLTG segment size of the new
link is smaller than the MLTG size currently in use by the TG.

09
The NCP is loaded, but is in another subnetwork.
0A
Unable to contact the link station.  This error type is set if
the PU is in INACT status.  Type 0A will be used when both the SSCP
and the sending PU support the attachment of T2.1 nodes.  Format 3
XID fields are present when the CONTACTED node is a T2.1 node.
0B
The 2.1 boundary function detected an XID error during a contact
sequence for a PU type 2.0 or 2.1 node.

 IST1574I  This message displays the XID received from (if preceded by message
IST1580I) or sent to (if preceded by message IST1586I) the adjacent
node.
offset is the hexadecimal offset in the XID.
hexdata_1, hexdata_2, hexdata_3 and hexdata_4 each
display 4 bytes of the XID in hexadecimal format.
EBCDIC_data displays 16 bytes of the XID in
EBCDIC format. Unprintable characters are represented by periods.

 IST1580I  This message is a header for the information displayed in messages
IST1574I and IST1582I through IST1585I for the XID received from the
adjacent node.

 IST1582I  This message is a header for the information displayed in messages
IST1583I through IST1585I. Messages IST1582I through IST1585I are
present only if CV X'22' is present in the XID.
The IST1582I subgroup follows the XID to which it refers.

 IST1583I  This message is issued only if byteoffset in
message IST1583I is nonzero or bitoffset in message
IST1584I is nonzero.
byteoffset is the hexadecimal offset of the
byte containing the error, as noted by the adjacent node. Offsets
are from byte 0 in the XID.

 IST1584I  This message is issued only if byteoffset in
message IST1583I is nonzero or bitoffset in message
IST1584I is nonzero.
bitoffset is the hexadecimal offset of the
bit containing the error, as noted by the adjacent node. Offsets are
from bit 0 in the XID.

 IST1585I  This message is issued only if sense data is included in CV X'22'.
sense is the SNA sense code set by the adjacent
node identifying the reason the XID is rejected.

 IST1586I  This message is a header for the information displayed in message
IST1574I for the XID sent by VTAM to
the adjacent node.

System action
 Activation of nodename fails. VTAM deactivates the node.

Operator response
 Save the system log and print the major node
definition for problem determination.

System programmer response
 For types 03,
05, 07, 08, and 0B, verify that the network definitions
for the nodes involved are correct.
 Additional recommended
actions include:  A type of 02 indicates that the communications
controller is not loaded.
A type of 03 indicates one of the following
problems:  A link-hardware problem during CONTACT processing. In this case,
follow the installation problem determination procedure for the link.
There is an emulator program in the communication controller you
are attempting to activate.
The adjacent link station on the NCP side of the channel connection
has not been activated.

For a type of 05:  Make sure that the applicable link and link-station definitions
are compatible.
Ensure that HOSTSA has been coded in your start list.
For a storage problem, check the bufsize value
specified for the IOBUF buffer pool. If a channel-attached NCP is
in this domain, this value must match or be greater than the value
used for the UNITSZ operand on the HOST statement in the NCP definition.
For an explanation of the bufsize value, see the
description of buffer pool start options in the z/OS Communications Server: SNA Resource Definition
Reference.

For a type of 07, make sure the proper
route definitions have been supplied in each subarea node. 
For a type of 08, make sure that the
applicable link and link-station definitions are compatible. Issue
a DISPLAY STATIONS command for a summary of connections to this subarea. 
For a type of 0B, either the sent or
received XID might contain an appended CV X'22' that provides
more detailed information about the cause of the error. The last 4
bytes of the CV X'22' might contain sense data.

 For type 05, 07, 08, or 0B,
see the section on common subarea problems,  in the z/OS Communications Server: SNA Diagnosis Vol
1, Techniques and Procedures for additional examples and problem determination
actions. See SNA Network Product Formats or z/OS® Communications
Server: SNA Data Areas Volume 1 for additional
information on interpreting the CV X'22' and sense data,
if provided in messages IST1582I through IST1585I.
 For an apparent
software problem, take the following actions:  If you have access to IBMLink, search for known problems with similar
symptoms. If no applicable matches are found, report the problem to IBM® using the Electronic Technical
Report (ETR) option on IBMLink.
If you do not have access to IBMLink, report the problem to the IBM software support center.

Routing code
 8

Descriptor code
 5 