PH28931: DFHAP0002 SEVERE ERROR CODE X'1954' IN MODULE DFHAPLI1 LE LOCK TASKS SUSPENDED FOR THIS LOCK REGION HANGS

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• You are running CICS TS 5.4, and an application receives
  program checks reported in the following messages:
  
  DFHSR0622 An attempt to access the UDSA has caused the Abend
            which follows
  DFHAP0001 An abend (code  0C4/AKEA) has occurred at
            offset X'FFFFFFFF' in module DFHAPLI3
  This program check occurred in module IGZCEV5/CEEEV005. The last
  trace prior to the program check shows a call to LE:
  
  APLI EVENT CALL-TO-LE/370 - Establish_Ownership_Type
             Program_name(xxxxxxxx)
  This task terminates, and about a minute later the following
  error ocurred:
  
  DFHAP0002 A severe error (code X'1954') has occurred in
            module DFHAPLI1.
  The corresponding trace:
  
  AP 1948 APLI  EVENT CALL-TO-LE/370 Thread_Initialization
                Program_name(yyyyyyyy)
  AP 1954 APLI  *EXC* - LE Lock/Unlock Err
  
  Dispatcher shows other tasks suspended in LMQUEUE waits for the
  LE LOCK.
  The AP0002 error occurred, because CICS lock manager thinks this
  kernel task already owns the LE LOCK.  It turns out the task
  that experienced the program check a minute earlier, was running
  on this same kernel task, and never freed the lock in its error
  recovery.
  
  Additional Symptoms:  KIXREVRJL
  hang hung lelock LE_LOCK 0C4
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICS users.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: Retention of LE_LOCK after an LE        *
  *                      failure in initialisation causes all    *
  *                      programs that interact with LE to fail. *
  ****************************************************************
  When LE fails while initialising an LE program and the
  failure occurs in a call via DFHAPLI3 then the recovery
  routine (RR) in DFHAPLI1 does not know that the LE_LOCK is held
  and does not free it.
  
  This causes problems for all further LE compliant programs.
  
  Additional keywords: LE_LOCK AP0002 APLIREC APLI3REC
  

Problem conclusion

• DFHAPLI3 was given it's own RR to free the LE_LOCK, if held,
  and percolate back to the RR in DFHAPLI1.
  
  The new AP 1956 APLI3 *EXC* trace entry will be included in
  the next refresh of the Knowledge Centre at 5.4, 5.5 and 5.6.
  

Temporary fix

Comments

APAR Information

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

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

  UI72688 UI72689 UI72690

Modules/Macros

• DFHAPLI1 DFHAPLI2 DFHAPLI3 DFHAPLJ1 DFHAPLJ3 DFHAPLJP DFHAPLX1
  DFHAPLX3 DFHAPPIS DFHLITRI DFHSJSA  DFHSJWL  DFJ@H356 DFJ@H427
  DFJ@H467 DFJ@H468
  

Fix information

• Fixed component name

  CICS TS Z/OS V5

• Fixed component ID

  5655Y0400

Applicable component levels

• R100 PSY UI72690

     UP20/11/21 P F011

• R200 PSY UI72689

     UP20/11/21 P F011

• R300 PSY UI72688

     UP20/11/21 P F011

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.