PM67750: ABEND4C5 742D0402 EZBIPOUT AFTER VIPAROUTE DELETE

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as unreproducible in next release.

Error description

  • ABENDS4C5 Reason 742D0402 in EZBIPOUT (base) offset x'3262'
    after OBEYFILE is done with a VIPAROUTE DELETE.
    Problem only occurs when VIPAROUTE is configured, a connection
    is distributed using the VIPAROUTE route, and an obeyfile is
    done with a VIPAROUTE DELETE.
    The next packet arriving on that connection to the distributor
    will use the route associated with the deleted VIPAROUTE.
    Depending upon the state of that route, the packet may be
    discarded or the 4C5 abend may occur.
    
    This can also occur if the route being used for VIPAROUTE is
    deleted, typically as a result of dynamic routing.
    
    
    Other Symptoms:
    
      S0C4 ABEND in EZBXFMS6 or EZBXFGP2, with the reference from
      XFCRHTE_RTE@ pointing to an area that is either not an RTE or
      is no longer accessible.
    

Local fix

  • Local fix is to wait for all of the distributed connections
    using the deleted VIPAROUTE to end, or move the distributed
    VIPA ownership to a backup.  The distributed VIPA
    ownership may be returned to the original owner after the
    takeover has occurred if desired.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of the IBM Communications Server   *
    *                 for z/OS Version 1 Release 12 and 13 IP:     *
    *                 VIPAROUTE                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: Abend4C5 742D0402 in module EZBIPOUT    *
    *                      after VIPAROUTE has been deleted.       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Abend4C5 742D0402 in module EZBIPOUT after VIPAROUTE has been
    deleted.
    
    VIPAROUTE DEFINE is configured on a SYSPLEX Distributor TCP/IP
    stack and active distributed connections exist to the target
    defined by the VIPAROUTE definition.  An OBEYFILE is issued
    with VIPAROUTE DELETE causing the active connections to revert
    back to the internal interface route to the target.  The logic
    that sets the internal interface route is incorrectly using
    the VIPAROUTE route during the initial distribution of the
    connection.  This causes the revert logic to continue using the
    route selected for the VIPAROUTE destination instead of the
    internal interface route.
    
    The failure to revert to the internal interface route will
    cause an undesired network path and GRE encapsulation for
    the distributed connections that were using the VIPAROUTE.
    
    The abend occurs when the route selected for the VIPAROUTE
    destination is deleted from the TCP/IP routing table and
    active distributed connections have incorrectly reverted to
    this route.
    +-------------------------------------------------------------+
    + Please check our Communications Server for OS/390 homepages +
    + for common networking tips and fixes.  The URL for these    +
    + homepages can be found in Informational APAR II11334.       +
    +-------------------------------------------------------------+
    

Problem conclusion

Temporary fix

Comments

  • The SYSPLEX Distributor logic has been amended to save the
    internal interface route when a connection is distributed.
    

APAR Information

  • APAR number

    PM67750

  • Reported component name

    TCP/IP V3 MVS

  • Reported component ID

    5655HAL00

  • Reported release

    1D0

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-06-27

  • Closed date

    2012-07-23

  • Last modified date

    2013-01-10

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

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

    UK80465 UK80466

Modules/Macros

  • EZBCTFME EZBITTRC EZBXFACI EZBXFHSH EZBXFMS6
    EZBXFUTL EZBXFUT3 EZBX6ACI EZBX6HSH EZBX6UTL EZBX6UT3
    

Fix information

  • Fixed component name

    TCP/IP V3 MVS

  • Fixed component ID

    5655HAL00

Applicable component levels

  • R1C0 PSY UK80465

       UP12/09/08 P F209

  • R1D0 PSY UK80466

       UP12/09/08 P F209

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

z/OS family

Software version:

1D0

Operating system(s):

z/OS

Reference #:

PM67750

Modified date:

2013-01-10

Translate my page

Machine Translation

Content navigation