II03990: SENSE 800A0000 PIU TOO LARGE FOR TG BETWEEN PU TYPE4/5'S.

APAR status

• Closed as canceled.

Error description

• TPINFO VTAMINFO
  569511701 R10A R160 R170 R180 R190 R1A0 R1B0 R1C0 R1D0 R210
  R220
    If a PIU is too large to be passed from one PU Type4/5
  to another PU Type4/5, an exception request (EXR) with
  sense 800A0000 may be generated. The SNA Network Product
  Formats (LY43-0081) manual describes this process in
  chapter 4 (RH's) under the heading 'EXCEPTION REQUEST'.
  This section lists the rules for building the EXR - it
  will contain sense 800A0000 along with up to 3 bytes of RU.
  
  Note that a PIU contains up to 26 bytes of TH, a possible
     3 byte RH and possible RU data. The total PIU size cannot
     be greater than the values calculated below.
  
  For VTAM/NCP nodes in the session path, the following
  definition values should be checked for each configuration
  used:
  
  - VTAM to channel-attached NCP:
      VTAM will take the smaller of:
         - MAXDATA on the PCCU statement (or LINE/PU
            statement for channel-attachment NCP) or,
         - The value sent in the XID for max PIU size by the
            NCP. This will be: the product of BFRS (from the
            BUILD statement) and TRANSFR (from the channel
            adapter LINE statement for 3745 or 3720 with V5
            NCP; or from the BUILD statement for other NCPs).
  
  - Channel-attached NCP to VTAM:
      The product of MAXBFRU from the HOST statement (or
      from the LINE statement for channel-attachment NCP)
      and IOBUF size (from VTAM start options).
  
  - VTAM to VTAM through CTCA (CTC):
      - If both VTAM's have the CTCA enhancement (V3R2 and
        above include the CTCA enhancement) - product of
        MAXBFRU (from CTCA LINE statement) and 4K.
        Note: The first page of buffer storage has prefix/
        header info that will decrease available buffer space
        by 24 bytes.
      - If one or both VTAM's does not have the CTCA
        enhancement - product of MAXBFRU (LINE statement)
        and IOBUF size from VTAM start options (LFBUF size
        for pre-V4R2 VSE VTAM.
  
  - NCP to link-attached NCP:
      Product of TRANSFR (LINE statement) and BFRS (BUILD
      statement).
  
  - NCP to link-attached VTAM:
      Product of MAXBFRU (CA LINE statement) and IOBUF size
      from VTAM start options for VM VTAM (LFBUF size for
      VSE VTAM).
  
  -------
  NOTE: The definitions of ALL PU TYPE4/5's on the session
  PATH must be checked.  Any PU4/5 can change the too-long-
  PIU into an 800A0000 exception request.
    The 800A0000 will flow to the destination LU. Some LU's
  will return the sense in a response. Other LU's will UNBIND -
  some will include the 800A0000 in the UNBIND sense data -
  others will not.
  -------
  ADDITIONAL KEYWORDS: 800A, RPL RETURN CODE 0403 0404
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• INFO APAR.
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels