|
View previous topic :: View next topic
|
| Author |
Message |
leo_sangha
New User
Joined: 11 Aug 2005
Posts: 85
Location: England
|
|
|
|
Hi,
I'm new to CICS, could you please help me resolve this error
DFHSR0001 XDCDV111 An abend (code 0C4/AKEA) has occurred at offset X'FFFFFFFF'
DFHME0116 XDCDV111
(Module:DFHMEME) CICS symptom string for message DFHSR0001 is
PIDS/5655M1500 LVLS/640 MS/DFHSR0001 RIDS/DFHSRP PTFS/UK05645
AB/S00C4 AB/UAKEA RIDS/FTSD012 ADRS/FFFFFFFF |
|
| Back to top |
|
 |
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA
|
|
|
|
| What have you done to resolve it so far? |
|
| Back to top |
|
|
leo_sangha
New User
Joined: 11 Aug 2005
Posts: 85
Location: England
|
|
|
|
| I checked the length of the module FTSD012 in test region & production. It is correct. |
|
| Back to top |
|
|
Terry Heinze
JCL Moderator
Joined: 14 Jul 2008
Posts: 1249
Location: Richfield, MN, USA
|
|
|
|
| Why is ASRA in the Topic subject but the error message refers to AKEA? |
|
| Back to top |
|
|
Earl Haigh
Active User
Joined: 25 Jul 2006
Posts: 475
|
|
|
|
OC4/AKEA is normally an indication you are referencing or moving data outside your programs boundaries.
if you are new to CICS, your will need to discuss with your peers or ask your CICS technical support people to help with debugging your program. |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA
|
|
|
|
Your header says ASRA (which is a data exception in CICS), but your error message references AKEA (which is an addressing error in CICS). You need to be more careful about describing your error!
| Quote: |
I checked the length of the module FTSD012 in test region & production. It is correct.
|
Exactly what does this have to do with your problem? Addressing exceptions could be a table subscript out of range, a module linked incorrectly (24-bit instead of 31- bit), referencing DFHCOMMAREA that doesn't exist, or various other things. None of these have anything to do with the length of the module -- so your checking the length, while not invalid, is of absolutely no help in solving your problem.
If you have Xpediter or other debugging tool available, run your transaction through it. Otherwise, use CEDF to trace through the program and figure out what's happening. You could also ask your CICS support staff to help you with a trace and debug via it. If you have Abend Aid on site, it can be very helpful in debugging CICS errors. If you identify where the module is going awry, you are much closer to figuring out which of the many forms of addressing exception you're dealing with, and that much closer to fixing it. |
|
| Back to top |
|
|
leo_sangha
New User
Joined: 11 Aug 2005
Posts: 85
Location: England
|
|
|
|
Hi All,
Thanks for all the valuable feedback. And i apologize for the confusion regarding the abend i mentioned in the subject.
I'm trying to xpedite but i'm getting below error:
********** PROGRAM IS NOT IN PPT OR IS DISABLED ***********
Please advise. |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA
|
|
|
|
You need to:
1) enable the program in the PPT if it is disabled, or
2) add the program to the PPT if it does not exist (which may require your CICS support person to update the appropriate definition) |
|
| Back to top |
|
|
|
|
