IBM Support

PH20735: DMGR CR ISSUED ABEND0C4-11 DUMP AFTER STOP COMMAND.

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • The ABEND0C4 occurs when referencing a client's native control
    block that has been freed. The native z/OS Control block being
    referenced is IHAASCB (ASCB). The code in control at the time of
    the ABEND was driven from the server-side of a Local
    Communication connection (LCOM) for the cleanup of a connection.
    There are a number of different scenarios that can drive the
    cleanup code of a connection. This appears to be somewhat of
    timing related. If this path got control before the OS freed the
    client's ASCB then there would not have been an ABEND; or if the
    targeted resources being cleaned up where previously cleaned up
    on other cleanup paths.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    *                  V8.5                                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: WebSphere Application Server for z/OS   *
    *                      ABEND0C4 in bboclsur after stop         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    A stop was issued to terminate the server.  During the
    cleanup
    of "server-side" local communication connections established
    resource managers (RESMGRs) are deleted.  An ABENDS0C4 was
    encountered when referencing the client's ASCB control block
    from the server.  Due to timing windows, the client had
    progressed far enough in termination to have z/OS release
    its
    address space control blocks.  Also, involved in this
    scenario, the client avoided "normal" connection cleanup
    (ie. a cancel was used to terminate the client).
    

Problem conclusion

  • Code has been modified to not reference the client side
    control
    blocks to obtain information needed to delete established
    RESMGRs related to the local communication connections.
    
    The fix for this APAR is targeted for inclusion in fix pack
    8.5.5.18 and 9.0.5.4.  For more information, see
    'Recommended
    Updates for WebSphere Application Server':
    http://www.ibm.com/support/docview.wss?
    rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH20735

  • 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

    2020-01-06

  • Closed date

    2020-01-27

  • Last modified date

    2020-01-28

  • 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

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
10 February 2022