IBM Support

PH13786: ABENDCC3 RSN040E0001 IN LOCAL COMMUNICATION CLOSE PROCESSING

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Dmgr issued svcdump during termination.
    The code is ABENDCC3-040E0001.
    .
     Entry       E  Offset  Statement   Load Mod
     bboclsur(bacb*,int,void*,void*,int*,int*,int*)
     CF_Local_Connection::close_connection(int)
     CF_Local_Connection::close_connection()
     CF_Local_Connection_Object_Manager::cleanUp(_jobject*)
     CF_Local_Listener::deactivate_listener()
     CF_TCP_Request::stopListener(void*)
    .
    In this scenario the server-side of a Local Communication (LCOM)
    connection was stopping in dmgr ANM100.  The LCOM stop code
    drives cleanup for each open connection.  A call to native
    module bboclsur is made to cleanup resources and inform the
    other-side of the connection of the close/cleanup.
    In this case the client was nodeagent ANN110. This target
    address space was well into termination and the schedule of
    an SRB failed and resulted in an ABENDCC3 with an abend
    reason code of 040E0001.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: WebSphere Application Server for z/OS   *
    *                      controller issued ABENDCC3              *
    *                      RSN=040E0001                            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    An ABEND CC3 reason code 040E0001 was issued from Local
    Communication (LCOM) connection cleanup code.  A schedule of an
    SRB is made to the address space of the client-side of a LCOM
    connection going through cleanup processing.  The reason for
    the SRB is to cleanup resources related to the connection that
    can only be done from the client-side address space.
    The target address space is either no longer around or is far
    enough in its termination processing that the schedule fails.
    Our schedule routine, bbooschd.plx, will issue the referenced
    ABEND code and reason in this scenario.
    

Problem conclusion

  • Code has been added to not issue an ABENDCC3 REASON=040E0001
    during LCOM connection cleanup when the target address
    space is not available.  The resource targeted for cleanup
    will be released by normal address space termination.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.5.5.17 and 9.0.5.1.  Please refer to the Recommended
    Updates
    page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH13786

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-06-25

  • Closed date

    2019-07-26

  • Last modified date

    2019-07-26

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

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

Fix information

  • Fixed component name

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
17 October 2021