4F0C - 4EE6 = X'28' which is most likely an assembler CICS Stub length. CEDX reports offset from the entry point and syslog reports from the load point.

Richard ----- Original Message ----- From: Barkow, Eileen To: CICS-L@LISTSERV.UGA.EDU Sent: Thursday, May 06, 2010 8:49 AM Subject: Re: Offset difference between CEDX and SYSLOG

4ee6+6=4f0c

Since the 0c7 is most likely in a 6 byte decimal instruction, CEDX is stopping right before the abend occurs and

The syslog is showing the actual psw instruction offset, which is 6 bytes after the abending instruction.

From: CICS List [mailto:CICS-L@LISTSERV.UGA.EDU] On Behalf Of Hari.R Sent: Wednesday, May 05, 2010 11:48 PM To: CICS-L@LISTSERV.UGA.EDU Subject: Re: Offset difference between CEDX and SYSLOG

Hi,

Since this is ASRA, you should be able to see the error statement easily from the syslog offset.

try putting some edit check to avoid the abend.

Thanks Kris.

On Wed, May 5, 2010 at 11:28 PM, Agra Rizqa Cendrajaya <silverant@gmail.com> wrote:

Dear Listers,

I get ABEND ASRA at my program called BNODATE, trans ID OACJ. While I do CEDX I get this Error message :

TRANSACTION:,OACJ,PROGRAM:,BNODATE ,TASK:,0045329,APPLID:,CICSUAT ,DISPLAY:, 00 ,STATUS: ,AN ABEND HAS OCCURRED COMMAREA = '10078OACJOACJ01...%...<BNODATE BNCJS1 SC0303N.......'... EIBTIME = 101331 EIBDATE = 0110126 EIBTRNID = 'OACJ' EIBTASKN = 45329 EIBTRMID = '0078'

EIBCPOSN = 8 EIBCALEN = 3800 EIBAID = X'7D' AT X'001400EA' EIBFN = X'0A04' READQ AT X'001400EB' EIBRCODE = X'000000000000' AT X'001400ED' EIBDS = '........' + EIBREQID = '........' ,OFFSET:X'004EE6' , ,INTERRUPT: DATA EXCEPTION ,ABEND : ,ASRA ,PSW: X'079D1000 935EEBCC,00060007'

But When I see the SYSLOG, I get the following :

+DFHSR0001 CICSUAT An abend (code 0C7/AKEA) has occurred at offset X'00004F0C' in program BNODATE. +DFHME0116 CICSUAT 776 (Module:DFHMEME) CICS symptom string for message DFHSR0001 is PIDS/5655M1500 LVLS/650 MS/DFHSR0001 RIDS/DFHSRP PTFS/HCI6500 AB/S00C7 AB/UAKEA RIDS/BNODATE ADRS/00004F0C +DFHDU0205 CICSUAT A SYSTEM DUMP FOR DUMPCODE: SR0001 , WAS SUPPRESSED BY THE GLOBAL SYSTEM DUMP SUPPRESSION OPTION

Most of the time, the CEDX more accurate. Why the offset is different on CEDX and SYSLOG for the one problem ? I'm a programmer and at our production site, I'm not allowed to do CEDX, so I can only rely on SYSLOG. If the offset is not correct, it will make me difficult to trace back, which line of codes make the ABEND.

Any responses will be appreciated :)

Thank you. -- You hear but do not listen. The distinction is clear.