IBM Mainframe Forum

During one of the job failure, Sysout displayed below message.
How can I check the exact line of the code that's causing a problem using Offset value or Address??

Could you please explain me importance of offset value and Address while checking the problem.



Message from SYSOUT:-
CEE6750C The system or user abend U2002 R=NULL was issued.
From compile unit AW415 at entry point AW415 at statement 786 at compile unit offset +00005784 at entry
offset +00005784 at address 0D441980.

Plz clarify

Hi,

You need to compile your code and you'll get (or should get) a section in the COBOL compile output that looks something like this



The offset in your abend message referes to HEXLOC in the compile output. You should find the nearest HEXLOC to your offset, then the LINE in the compile output should be the offending line causing the abend (note the HEXLOC and the offset usually are not the same, so you need to look for the closest match).

Hopefully you'll be able to do this. There are other tools you can use such as Abendaid, Fault Analyser etc. but I don't know if you have these products installed. Perhaps talk to your local friendly Systems programmer who should be able to help.

Good luck
Steve

I never found exact match in the HEXLOC section, as you said we need to check it for nearest match.

I have one more question, Any idea about Address??
What is the importance of it and how it will be helpful in debugging the problem.

Thanks a lot for educating me on Offset values.

Hello,

I never found exact match in the HEXLOC section

Often (usually) one cobol statement generates multiple actual instructions and the one the abends is not at an exact displacement in the compile.

Depending on which address you mean (many are used in the execution of a program), the address is probably the address of the failed instruction. Going to that place in the dump and referring to something that shows the construction of all of the "machine" instructions (what used to be referred to as a "green card" or a "yellow card") one can use the registers and displacements (more addresses) to see what the program was doing when the abend occurred.

Many systems have a tool like AbendAid that does a lot of this work for the developer.