IBM Support

DFHAP0001 0C1 AKEA at offset FFFF in DFHSUWT when using CA ENF

Question & Answer


Question

Why am I receiving message "DFHAP0001 An abend (code 0C1/AKEA) has occurred at offset X'FFFF' in module DFHSUWT" during CICS Transaction Server for z/OS (CICS TS) V5.2 startup? The CICS region does stay up after the abends. I am in the process of getting vendor products ready for z/OS V2.2, including CA ENF from CA Technologies, but have not converted any system to z/OS V2.2 yet.

These are the messages I see in the CICS log:

 DFHSI8434I Control returned from PLT programs during the third stage of initialization.                      
 DFHSI1517  Control is being given to CICS.                                                                   
 DFHAP0001  An abend (code 0C1/AKEA) has occurred at offset X'FFFF' in module DFHSUWT.                          
 DFHME0116  (Module:DFHMEME) CICS symptom string for message   
 DFHAP0001  PIDS/5655Y0400 LVLS/690 MS/DFHAP0001 RIDS/DFHSUWT PFS/HCI6900                                                           
            AB/S00C1 AB/UAKEA RIDS/DFHSUWT ADRS/0000FFFF  

Answer

If you have a system dump from the DFHAP0001 abend 0C1 AKEA, you can look at the Kernel error table by using IPCS command VERBX DFHPDxxx 'KE' (where xxx is your release level of CICS like 690 for CICS TS 5.2).

From the dump, the task running in error is CSSY, III.

  0020   1B375100 ***Running** 1AB9C700 III CSSY 1AA9B380 1A943200 *YES*  
 
 KE Domain Error Table only shows 1 abend0c1 at the time of the dump:  
      ERR_NUM   ERR_TIME  KE_NUM  ERROR TYPE    ERR_CODE  MODULE    OFFSET 
      =======   ========  ======  ==========    ========  ======    ====== 
      00000001  09:45:40   0020   PROGRAM_CHECK 0C1/AKEA  UNKNOWN   UNKNOWN
                                                                      
       Error Code:  0C1/AKEA    Error Type:  PROGRAM_CHECK
       Timestamp:  D0A87E8DAAB9F586                                        
       Date (GMT)   :  27/04/16         Time (GMT)   :  13:45:40.746143    
       Date (LOCAL) :  27/04/16         Time (LOCAL) :  09:45:40.746143    
      KE_NUM:  0020  KE_TASK:  00000000_1B375100  TCA_ADDR:  1AB9C700      
      DS_TASK:  1AA9B380  XM_TOKEN:  1AB0A300  TRAN_NO:  00010             
 
     Program DFHSUWT  was in control, but the PSW was elsewhere.          
     Error happened under the CICS RB.                                    
     PSW:  07040000 80000000 00000000 300047F2                       
     Instruction Length:  2  Interrupt Code:  01                     
     Exception Address:  00000000_30004800                           
     Execution key at Program Check/Abend: 0     Addressing Mode:  31
     Space at Program Check/Abend: Basespace                         
     Breaking Event Address: 00000000_0191B242                       
     CICS Error Instruction Address: 300047F2                        
     Register contents are:                                          
     GPR 0-3   00000000_00011000  00000000_007D17F5                  
               00000000_00007000  00000000_1A7BDBE0                  
     GPR 4-7   00000000_1B37ACC0  00000000_7F62A000                  
               00000000_1AA6A0F2  80000000_1529D118                  
     GPR 8-B   00000000_00BA3000  00000000_1B37B62A                  
               00000000_00000068  00000000_1B37B0A8                  
     GPR C-F   00000000_1AB9C700  00000000_1B37ACC0        

      

Register 14 (9A7BED14) points to DFHSUWT HCI6900 at offset 1134 . The instruction is 0CEF (BASSM 14,15) at offset 1132.

Note that when you receive an offset of x'ffff', this indicates that the abend has not truly occurred in DFHSUWT, rather the abend has occurred somewhere that CICS cannot recognize.

You can enter IPCS command IP SYSTRACE to display the system trace. For this problem, I can see SVC 23 or WTO macro is issued. The PSW address 1A7BED32 points to DFHSUWT at offset 1152. However, the PSW address 300047F0 of the corresponding SVCR 23 points to invalid storage which is the cause of the abend0c1.

  PR   ASID WU-Addr-  Ident  CD/D     PSW----- Address-     Unique-1   Unique-2  Unique-3                                                   
 0000 0129 009FC178  SVCR    23     00000000_300047F0  00000000 00011000 007D17F5                               
                                                                                                 07040000 80000000                      
 0000 0129 009FC178  PGM    010     00000000_300047F0  00020010 00000000 30004800   
                                                                                                 07040000 80000000     
 0000 0129 009FC178  PGM    011     00000000_300047F0  00020011 00000000   
 0000 0129 009FC178 *RCVY  PROG 940C1000 00000001  00000000            

                                             

Backing up in systrace, I see the following PSW addresses:

  PR   ASID WU-Addr-  Ident  CD/D     PSW----- Address-     Unique-1   Unique-2  Unique-3           
 0000 0129 009FC178  SVC     78     00000000_00B920D4  0000E602 000002F0  00000000  Getmain                      
                                                                                                07040000 80000000                      
 0000 0129 009FC178  SVCR   78     00000000_00B920D4  00000000 000002F0  009A9D10                               
                                                                                                 07040000 80000000                      
 0000 0129 009FC178  SVC     78     00000000_00B9226A  0000E603 000002F0  009A9D10  Freemain                    
                                                                                                07041000 80000000                     
 0000 0129 009FC178  SVCR    78    00000000_00B9226A  00000000 000002F0  009A9D10                              
                                                                                                 07041000 80000000                     

Browsing storage and backing up from the PSW addresses that I saw in the systrace, I see the following eyecatcher for a CA ENF module:

  00B92010    | {{.......#MID... |                                     
  00B92020    | ...y....CASEJLOG |                                     
  00B92030    |  CAW1E10  ~RMID( |                                     
  00B92040    | RESERVE)~ 201202 |                                     
  00B92050    | 17 04.40 ....... |                                     
  00B92060    | CA ENF           |                                     
  00B92070    |          R14.1   |                                     
  00B92080    |  - COPYRIGHT (C) |                                     
  00B92090    |  1991-2012 CA.   |                                     
  00B920A0    |  ALL RIGHTS RESE |   

It appears that the problem is a result of bad CA ENF modules. If you do not need the CA ENF code, you should be able to specify MODE(CICS,NONE) in the ENFPARM member being referenced by the ENF proc and comment the CICSREL statement. This should disable CA ENF in the CICS region and circumvent the problem until you can get a fix from CA Technologies.

Or, you might want to simply delete the CA ENF (CICS) component (FMID: CAW3E10) from the CA Common Services SMP/E environment.

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Platform":[{"code":"PF035","label":"z\/OS"}],"Component":"Startup","Version":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Product Synonym

CICS/TS CICSTS CICS TS CICS Transaction Server

Document Information

Modified date:
04 May 2016

UID

dwa1268306