IBM Support

PH24366: LIBERTY FAILS TO REMOVE THE CLIENT ADDRESS SPACE LEVEL RESMGRS WHEN CLEANING UP LIBERTY'S CLIENT STRUCTURES

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

  • Customer noticed that *MASTER* was suddenly using an
    extensive
    amount of CPU.  Analysis of a stand alone dump revealed that
    the
    CPUs were tight looping in the Liberty Angel module
    BBGZAFSM.
    The loop was identified on one instruction 05EF with R15
    pointing back to the start of the same instruction.
    

Local fix

  • Ensure all client address spaces that were connected to the
    Angel are stopped before the Angel is restarted again.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Liberty for z/OS                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: Liberty on z/OS is not deleting Client  *
    *                      address space level RESMGRs             *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Code is missing during the client side cleanup of structures
    related to using OLA.  The missing code is to delete an
    established address space level RESMGR.   If the usage pattern
    of OLA for the client is in a long lived address space, such as
    a batch initiator or a CICS region, these RESMGRs can build up
    over time.   There is a small amount of Common storage related
    to each established RESMGR.
    
    It has been observed in a customer scenario where over 100
    outstanding RESMGRs were present when the address space went
    though EOM termination.
    

Problem conclusion

  • Code has been added during the client side cleanup of data
    structures to delete the established address space level
    RESMGR.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 20.0.0.5.  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

    PH24366

  • Reported component name

    LIBERTY PROF -

  • Reported component ID

    5655W6514

  • Reported release

    CD0

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-04-13

  • Closed date

    2020-04-20

  • Last modified date

    2021-02-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

    LIBERTY PROF -

  • Fixed component ID

    5655W6514

Applicable component levels

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Platform":[{"code":"PF054","label":"z\/OS"}],"Version":"CD0"}]

Document Information

Modified date:
27 February 2021