IBM Support

PH08463: REGION HANG HUNG WITH TASKS IN LMQUEUE WAITS FOR THE LE_LOCK MAY ALSO SEE DFHAP0002 CODE 1954

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • You are running CICS Transaction server 5.2 and
    start seeing more of the following message:
    DFHAP1301 Language Environment has detected a
              corruption of its control blocks. Transaction tran
              currently executing.
    
    Then sometimes following this, may also see the following
    message:
    DFHAP0002 A severe error (code X'1954') has occurred in
                        module DFHAPLI1.
    
    Code 1954 invovles lock manager- indicates LE Lock/Unlock Err
    
    Then the region locks up, with many tasks stuck in LMQUEUE
    waits.
    A dump at the time of the hang shows the tasks waiting on
    the LE_LOCK.  It appears the task that owned the lock went
    away without releasing it.
    .
    Looking at the times of the LMQUEUE suspends, we found it always
    related to an entry in the Kernel Error table..with the same
    time stamp. The ERROR TYPE  of this entry was always
     'DEFERRED ABEND' for an AKC3- a purge request.
    
    Turns out the processing of this deferred abend in DFHAPLI1, can
    cause a task- owning this LE_LOCK, to terminate without ever
    unlocking it.
    Additional Symptom(s) Search Keyword(s): KIXREVxxx
    hang locked up purge while in  first dispatch
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION: Many tasks waiting on the LE_LOCK after *
    *                      a call to Language Environment          *
    *                      program_check_recovery.                 *
    ****************************************************************
    A task abends between acquiring the LE_LOCK and setting flag
    le_lock_acquired. This means that the lock is never freed and
    then many tasks hang, waiting on the lock.
    

Problem conclusion

  • DFHAPLI1 has been changed to release the LE_LOCK in the event
    of a problem occurring between the lock being acquired and
    le_lock_acquired being turned on.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH08463

  • Reported component name

    CICS TS Z/OS V5

  • Reported component ID

    5655Y0400

  • Reported release

    200

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-02-12

  • Closed date

    2019-04-03

  • Last modified date

    2019-05-02

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

    PI97817

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

    UI62294

Modules/Macros

  • DFHAPLI1 DFHAPLI2 DFHAPLI3
    

Fix information

  • Fixed component name

    CICS TS Z/OS V5

  • Fixed component ID

    5655Y0400

Applicable component levels

  • R200 PSY UI62294

       UP19/04/04 P F904

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.

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.5","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.5","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 May 2019