Help to find to diagnose a CODE 0C4/AKEA

merovich · Posted: Tue Jul 16, 2013 8:00 pm

I am trying to analyze this abend

(CODE 0C4/AKEA) HAS OCCURRED AT OFFSET X FFFFFFFF IN PROGRAM DSPT020.

from the transacation dump I got

SELECT TYPE=AND
0 DUMPID=1/0010
0
1ACRE1 --- CICS TRANSACTION DUMP --- CODE=ASRA TRAN=TX9H ID=1/0010 DATE=13/07/10 TIME=11:15:23 PAGE 1
-SYMPTOMS= AB/UASRA PIDS/5655M1500 FLDS/DFHABAB RIDS/DSPT020
-CICS LEVEL = 0650
-PSW & REGISTERS AT TIME OF INTERRUPT
0PSW 079D0000 00C00B96 00020011 00C00000
0REGS 0-7 1AD1C2A9 1AD1C190 80050200 973FF318 49F46900 1B906458 16E143B2 17AB6C18
0REGS 8-15 42502C80 49F46906 00155008 001550D0 00BC5000 1AD1C128 68C00B96 00000000
-EXECUTION KEY 9
0The transaction was in Basespace mode
0REGISTERS AT LAST EXEC COMMAND
0REGS 0-7 1AD1C2A9 1AD1C190 80050200 973FF318 49F46900 1B906458 16E143B2 17AB6C18
0REGS 8-15 42502C80 49F46906 00155008 001550D0 00BC5000 1AD1C128 68C00B96 00000000

of course the PSW 00C00B96 isnt pointing to any module

------ MODULE INDEX -----
0LOAD PT. NAME ENTRY PT LENGTH LOAD PT. NAME ENTRY PT LENGTH LOAD PT. NAME ENTRY PT LENGTH
00004A000
000280600 MNET020 00280600 000009D0 16AFF700 DFHEDC 16AFF814 00000190 16D87400 DFHUSDM 16D92438 0000D490
014500000 DFHSIP 145597D8 0017F060 16AFF900 DFHDCP 16AFFA14 00000440 16D94900 DFHWBDML 16DCD360 00045F68
01699D000 DFHSRP 169A1614 00004D28 16AFFE00 DFHDIPDY 16AFFF14 000001A0 16DDA900 CSQCOPEN 16DDAB88 00000E10

I review the DSPT020 flow and found that it completed their processing according to my memory map

as you can see my abend registers are the equal to my registers at last exec
so it seems that it is abending in my last exec (EXEC CICS RETURN)

my R14 is 68C00B96 so their 24 low significant bits are equal to my PSW value although my DSPT020 module is AMODE(31)

PROGRAM INFORMATION FOR THE CURRENT TRANSACTION
0 Number of Levels 00000003
0INFORMATION FOR PROGRAM AT LEVEL 00000003 of 00000003
0 Program Name DSPT020 Invoking Program DCNL200
0 Load Point 173FF2F0 Program Length 000002E8
0 Entry Point 973FF318 Addressing Mode AMODE 31
0 Language Defined ASSEMBLER Language Deduced ASSEMBLER
0 Commarea Address 1B906458 Commarea Length 00000025
0 Execution Key USER Data Location ANY
0 Concurrency THREADSAFE Api CICSAPI
0 Runtime NONLE370
0 Environment User application
0INFORMATION FOR PROGRAM AT LEVEL 00000002 of 00000003
1ACRE1 --- CICS TRANSACTION DUMP --- CODE=ASRA TRAN=TX9H ID=1/0010 DATE=13/07/10 TIME=11:15:23 PAGE 92
- Program Name DCNL200 Invoking Program DFHMIRS
0 Load Point 1B19D1B0 Program Length 00003F48
0 Entry Point 9B19D1B0 Addressing Mode AMODE 31
0 Language Defined Unknown Language Deduced COBOL II
0 Commarea Address 1AD13988 Commarea Length 000000DA
0 Execution Key USER Data Location ANY
0 Concurrency THREADSAFE Api CICSAPI
0 Runtime LE370
0 Environment User application
0INFORMATION FOR PROGRAM AT LEVEL 00000001 of 00000003
0 Program Name DFHMIRS Invoking Program CICS
0 Load Point 00000000 Program Length 00000000
0 Entry Point 00000000 Addressing Mode AMODE 24
0 Language Defined ASSEMBLER Language Deduced ASSEMBLER
0 Commarea Address 00000000 Commarea Length 00000000
0 Execution Key CICS Data Location BELOW
0 Concurrency QUASIRENT Api CICSAPI
0 Runtime NONLE370
0 Environment CICS system program

Any help about how to find the RCA ?

Best regards and thanks in advance

Horacio Merovich
ISBAN

colin777 · New User Joined: 06 Jun 2013 Posts: 19 Location: Singapore

Whenever a Program program checks within the CICS region, MVS will trap the PC and hand control to CICS thru the Kernel Domain. The Kernel will issue the Program Interrupt code AKEA and (in your case an 0C4..Protection Exception). It will then determine which Domain was in control at the time of the PC, and in this case and most cases its the Application Domain and pass control to this Domain's error handler routine with is DFHSRP. So we get the ASRA abend. Remember the middle 2 characters of every abend code, indicate who issued the abend.

In the DFHAP0001 or DFHSR0001 msg, if the failing offset is 'FFFFFFFF', then CICS was unable to locate the failing instruction.

This indicates that the failure was in a subroutine that was invoked by a Call. A Protection Exception, indicates that an address of some valid storage area was not set up correctly and contained low-values. So before we get into any lengthy analysis, please check on any subroutines and check that all parameters passed by the Calling program are allowed for and addressed in the Called program.

If we are dealing with only Assembler here, then you will need to check all Dsects.

If you are not sure of the structure of the Load module then run an AMBLIST utility on the Load module.

//JOBNAME JOB,’ACCNT’,’AMBLIST’,CLASS=A,MSGCLASS=X,
// NOTIFY=&SYSUID
//STEP1 EXEC PGM=AMBLIST
//SYSPRINT DD SYSOUT=*
//SYSLIB DD DSN=THE.LOAD.LIBRARY,DISP=SHR
//SYSIN DD *
LISTLOAD MEMBER=membername,output=xref
//

In the Output look for the heading ‘Control Section’, then review the data under headings : LMOD LOC NAME LENGTH TYPE

This will give you all the subroutines in the Load module, and so a much better understanding of its structure.

I hope this helps

Colin777