IBM Support

JR28884: PCOM: XIDS FLOOD THE NETWORK WHEN DUPLICATE CP NAME USED

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Using CS613 EEDLC configuration with a duplicate CP name
    the host is assigning the TG number and the link activates
    successfully with a different TG number than the one with active
    CP-CP sessions.  Then when the node attempts to activate another
    ( because the other node with a duplicate CP name already has
    CP-CP sessions )  CP-CP session, the host sends a DISC RQ and
    CS613 responds DISC RSP(DM).  Since the link is auto activate,
    CS613 immediately retries activation of the link (no delay) that
    was disconnected.  There is no delay since it was not an
    activation failure.
    
    There needs to be a configurable option in the ACG to control
    the frequency of reactivation attempts.
    

Local fix

  • Use a unique CP name in the PCOM ACG
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users who have erroneously configured their  *
    *                 network to have two machines with the same   *
    *                 CP name.                                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: Continuous retries to establish links   *
    *                      occur when two machines have the same   *
    *                      CP name.                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The remote end was allowing the link to activate, then
    immediately disconnecting it.  We therefore instantly retried
    the failing link, causing a loop of retries.
    

Problem conclusion

  • APPN.SYS code was changed to treat a link that fails shortly
    after starting as a "failed activation" rather than "active
    link failure". Retries are therefore no longer instant.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR28884

  • Reported component name

    COMM SERV NT 6.

  • Reported component ID

    5639F2503

  • Reported release

    613

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-04-03

  • Closed date

    2008-04-03

  • Last modified date

    2008-04-04

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

    IC55615

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

    JR28892

Modules/Macros

  • APPN
    

Fix information

  • Fixed component name

    COMM SERV NT 6.

  • Fixed component ID

    5639F2503

Applicable component levels

  • R613 PSN

       UP

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSHQNF","label":"Communications Server for Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"613","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
16 October 2021