IBM Support

OW36731: TDUS FLOW FROM ANYNET DLUR TO VTAM DLUS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • When VTAM DLUS is connected to an ANYNET DLUR, the DLUR sends
    TDUs to VTAM.  These TDUs are just discarded because an ANYNET
    attached DLUR appears to VTAM as a LEN device.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All using DLUR/DLUS with ANYNET SNA over IP. *
    ****************************************************************
    * PROBLEM DESCRIPTION: TDUs are flowing from an ANYNET         *
    *                      attached DLUR to the DLUS.              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    An ANYNET attached DLUR is considered to be LEN to the VTAM
    DLUS, and as such the TDUs are of no use.  They should not be
    sent to the VTAM DLUS.
    When the VTAM DLUS detects that the DLUR is connected using
    ANYNET (LEN), it will indicate no TDU support in the 51 vector.
    The DLUR (as of EP24825) will not send TDUs to the DLUS if the
    TDU support indicator in the CV 51 is off.
    
    These changes (DLUS and DLUR) are supported by AMB item 8445.
    

Problem conclusion

Temporary fix

Comments

  • When the VTAM DLUS detects that the DLUR is connected using
    ANYNET (LEN), it will indicate no TDU support in the 51 vector.
    The DLUR (as of EP24825) will not send TDUs to the DLUS if the
    TDU support indicator in the CV 51 is off.
    
    These changes (DLUS and DLUR) are supported by AMB item 8445.
    

APAR Information

  • APAR number

    OW36731

  • Reported component name

    VTAM V4 MVS/ESA

  • Reported component ID

    569511701

  • Reported release

    301

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    1998-12-14

  • Closed date

    1999-01-08

  • Last modified date

    1999-01-08

  • 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

  • R301 PSN

       UP

  • R401 PSN

       UP

  • R411 PSN

       UP

  • R501 PSN

       UP

  • R701 PSN

       UP

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"301","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSCY4DZ","label":"DO NOT USE"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"301","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
08 January 1999