What should I do when I receive message IST467I?

IST467I is the first in a group of messages. The exchange ID (XID) received by VTAM is shown in messages IST1574I and IST1580I. The XID sent by VTAM is shown in messages IST1574I and IST1586I. Compare the XIDs to determine why the PU rejected the XID.

Sample XIDs from an IST467I message group:

             ***********************************************
             *   The following is for XID format 2.  All   *
             *   references to bytes and bits are in hex.  *
             ***********************************************
             XID1 (Received from the NCP) =
                   242AFFF0 00000000 00080000 00010000
                   00035007 D5C3D7D3 D6C1C440 80000203
                   002A05F3 00800000 0000
             XID2 (Sent to the NCP by VTAM) =
                   242AFFF0 00000000 200800F9 DE010000
                   00010000 40404040 40404040 81000200
                   002A05F3 00000000 0000

Note: If type is 0B in message IST467I, additional error information may be contained in a CV X'22' appended to the end of the XID. See the User Response for an example.

Probable cause:

 Note: The explanations that follow cover more than the single error that the sample XID1 and XID2 represents.

 The first digit of the XID is the format. In the preceding sample XIDs, the format is format 2.

 Byte X'12' of the XID1 received from the NCP is the error byte.

     Bit 0
         Reserved (unused) 
     Bit 1
         Received XID unacceptable 
     Bit 2
         Incompatible 
     Bit 3
         Transmission group (TG) undefined 

 Bit 1 of byte X'12' is set for the following reasons:

     1 - The XID2 at displacement X'00' was not equal to 24 or 25.
     2 - The XID2 at displacement X'08' was not equal to 20.
     3 - The XID2 at displacement X'13' was not equal to 00.
     4 - The XID2 at displacement X'1E' was not equal to 02.
     5 - If running NCP: depending on the release of NCP you have:
         For NCP V4R3, V5R2, and higher: The XID2 from VTAM at displacement X'0B'--X'0C' is less than 1296 decimal (X'0510'). The value in this field is the result of MAXBFRU from the HOST macro times the IOBUF buffer size in the VTAM start list. This error is set only when the NCP definitions have specified the HOST connection using GROUP LNCTL=CA.
         For NCP prior to V4R3 and V5R2: The XID2 from VTAM at displacement X'0B'--X'0C' is less than (XID plus X'20'--X'21') times (XID plus X'22'--X'23') minus (XID plus X'24') in the XID sent by NCP. This result corresponds to the value specified on the MAXBFRU operand times the value specified on the UNITSZ operand minus the value specified on the BFRPAD operand. 

reasons cont: 6 - There is no path to the subarea number defined at X'11' in the XID2 that uses this connection. 7 - Bit 2 of byte X'12' is set because the received XID1 at X'25' is not equal to X'20', and an existing connection exists with the origin subarea. 8 - Bit 3 of byte X'12' is set because either the TG number in the XID2 at displacement X'0D' or the subarea from the XID2 at X'11' is unknown to the NCP.

Reasons 2, 3, and 4 should not occur, but should help to verify XID offsets.

For reason 5, refer to the z/OS Communications Server: SNA Resource Definition Reference and the NCP, SSP, and EP Resource Definition Reference regarding specification of buffer sizes.

For reason 6, refer to the z/OS Communications Server: SNA Resource Definition Reference and the NCP, SSP, and EP Resource Definition Reference regarding the definition of PATH statements. Also, transmission group (TG) mismatch could cause the problem. A TG mismatch could occur, for example, if an NCP is attached as a CA major node, and TG=ANY is coded in the CA major node in VTAM, and TG=ANY is coded on the NCP line definition for this attachment.

For reason 7, refer to the z/OS Communications Server: SNA Resource Definition Reference regarding the use of the CHANCON parameter of the PCCU macro.

For reason 8, refer to the NCP, SSP, and EP Resource Definition Reference regarding the use of the CANETID parameter on the BUILD macro. Verify that it is coded correctly for each network in which it is assigned.

      Notes:

     In the sample XID1 given above, byte X'12' contains the value X'50'. Bit 2 and bit 3 indicate that the XID2 was unacceptable and that the transmission group was not defined. The problem in this case was that there were no PATH definition statements defined in the NCP for the host subarea.

     The contacted error type 05 can also be posted if the NETIDs in the 2 XIDs do not match.

     The NETID will appear in a CV X'12' at the end of the XIDs. If they do not match, correct the NETID operand on the PU definition statement in one or both PU definitions.

     A contacted error type 05 may occur if a channel-to-channel connection is defined between two VTAM systems that have the same subarea. Subarea numbers must be unique.

     In this case, the 4 bytes starting at offset X'E' in XID1 and XID2 will be the same. XID offset X'E' contains the subarea numbers. XID1 contains the subarea number of the receiver, and XID2 contains the subarea number of the sender.

     The following example is for type 0B when a CV X'22' is appended to the end of the XID.


                   IST467I CONTACTED ERROR TYPE 0B FOR ID = AHHCPU1
                   IST1580I XID RECEIVED BY VTAM:
                   IST1581I   +000 348AFFF0 99260000 10CB4100 00000080 *...0............
                   IST1581I   +010 00060530 0000000E 09F1C9E2 E3D7E4E2 *.........1ISTPUS
                   IST1581I   +020 40400E0C F4D5C5E3 C14BE2E2 C3D7F1C1 *  ..4NETA.SSCP1A
                   IST1581I   +030 0E08F7C1 C8C8C3D7 E4F14609 09800000 *..7AHHCPU1......
                   IST1581I   +040 00000000 01103A00 2311040E 02F5F6F9 *.............569
                   IST1581I   +050 F5F1F1F7 F0F1F8F0 F10804F0 F4F0F4F0 *511701801..04040
                   IST1581I   +060 F00A06C1 C3C661E5 E3C1D416 11011300 *0..ACF/VTAM.....
                   IST1581I   +070 11F9F0F2 F1000000 0000F0F1 F3F2F0F8 *.9021.....013208
                   IST1581I   +080 F2220700 09040000 0000              *2.........
                   IST1582I   CONTROL VECTOR 22 ANALYSIS:
                   IST1583I     BYTE OFFSET OF FIRST BYTE IN ERROR = X'0009'
                   IST1584I     BIT OFFSET OF FIRST BIT IN ERROR = X'04'
                   IST1586I XID SENT BY VTAM:
                   IST1581I   +000 34B1FFF0 992B0000 10F74100 00000080 *...0.....7......
                   IST1581I   +010 15060530 0010000E 09F1C9E2 E3D7E4E2 *.........1ISTPUS
                   IST1581I   +020 40400E0C F4D5C5E3 C14BE2E2 C3D7F2C1 *  ..4NETA.SSCP2A
                   IST1581I   +030 0E08F7C1 C8C8C3D7 E4F14609 09801500 *..7AHHCPU1......
                   IST1581I   +040 00000000 02612E30 00088001 00280000 *...../..........
                   IST1581I   +050 00002381 141D0000 007800AC DED371AC *.............L..
                   IST1581I   +060 DED37108 D4000000 00000000 08D20000 *.L..M........K..
                   IST1581I   +070 00000000 00103A00 2311040E 02F5F6F9 *.............569
                   IST1581I   +080 F5F1F1F7 F0F1F8F0 F10804F0 F4F0F4F0 *511701801..04040
                   IST1581I   +090 F00A06C1 C3C661E5 E3C1D416 11011300 *0..ACF/VTAM.....
                   IST1581I   +0A0 11F9F0F2 F1000000 0000F0F1 F3F2F0F8 *.9021.....013208
                   IST1581I   +0B0 F2                                  *2
                   IST314I END


     Refer to the description of message IST467I in z/OS Communications Server: SNA Messages for additional information.