Analysys of COBOL program Listings.

Anuj Dhawan · Posted: Sat May 06, 2006 5:57 pm

HI,

Problem Statement :How I search the value in the variable causing data exception.

I am new to the Environment of Mainframes,I got a Data Exception Abend S0C7,with the following details:

Status of COBOL Program & JCL corresponding to it:

Program : Activated
JCL: Abends with S0C7

Details of CEEDUMP:
A Data Exception was caused by data referenced at displacement 15D from the start of TGT BLF cell 00 (X'0000'). The field contains
X'4040'. Refer to the data division map in the program listing to
locate the field name.

The field causing the exception is located in a data record of program
XXXXXX.

Details of SYSOUT:
The system detected a data exception (System Completion Code=0C7).
From compile unit XXXXXX at entry point XXXXXX at statement 1359offset +0000190A at address 3BA0264A.

By the statement no. (blue color above)I will get the variable name,in the listing, which is causing Data Exception , But how will I get the value in that, & then how to trace the program to resolve the problem

Moreover ,what's the meaning of TGT BLF cell in Details of CEEDUMP.

shrivatsa · Posted: Sun May 07, 2006 12:25 pm

If you want to get the value in the variable name you can use xpeditor or intertest tool to debug.

There are lot of tools available if you have one of them you can easily solve this type of problem.

sen_1983us · New User Joined: 21 May 2005 Posts: 21 Location: Hyderabad

Hi,

You can compile the progam with option TEST(SYM).

so while in creating DUMP you can see the value of the variables

Regards
Senthil

prasadvrk · Posted: Mon Jun 12, 2006 12:45 pm

Find line 1359 in the SYSPRINT of you compiler listing and this is where your program has abended . Fix the problem , mostly non numeric value would have been moved into a numeric field. Fix that, compile and run again.

Anuj Dhawan · Posted: Fri Jun 08, 2007 9:25 pm

Hi,

Thanks for the suggestions.

Pons · Posted: Tue Jun 12, 2007 12:53 pm

In production environment we can't compile using the compiler options. So we have to analyse using the offset one we got from the sysout.

You can use endevor and foot print and find that last f bytes of your offset,
That place of code made this abend. Then we easily find the roor cause.

Anuj Dhawan · Posted: Tue Jun 12, 2007 5:07 pm

William Thompson · Posted: Tue Jun 12, 2007 5:25 pm

socker_dad · Posted: Tue Jun 12, 2007 9:53 pm

Boy, I remember when being able to read a hexadecimal dump was an art form. sigh.

And sorry that this is so lengthy.

Do you have a product called Abend Aid? Probably not if you are asking us.

The idea is to add the given displacement (15D, in your case) to the address given by the base register. And it is hexadecimal addition, so don't forget your base 16 math.

Then you scan down your dump to the given address and read the instruction, checking the contents of the fields. It really helps when you have a yellow IBM instruction card which shows the hexadecimal equivalents of the commands. Wasn't 5D a MVC?

But even that won't help unless you know enough Assembler to realize that MVC is a Move Character command, and that the first field after the command is the RECEIVING field contents and the second is the sending field contents.

And unless your compile is done with the Assembler listing, that won't help much, because then you have to take the Assembler instruction back to your COBOL code to figure out what fields are being referenced by the abending command.

So how do you do this quickly and easily? You have to know what causes what errors - basically, you have to understand your data.

S0C7 is a data exception. This most commonly means that a numeric value has had something done to it that results in it being placed in an alphanumeric field. So start with your numeric fields. Pic 9(nn) fields are very forgiving, so start your research with your COMP fields (COMP, COMP-3, etc.).

Because you got a S0C7, I can safely assume this is a batch job and you are dealing with standard input files. Input files have copybook layouts. Look at the copybook. Find the "packed" (COMP) fields. Using the layout positions, use File-Aid to scan the file for non-numeric data in these fields.

File-Aid option 8 from the main menu allows you to get a file layout froma copybook. This tells you what position the particular field starts in and how long it is. Here is an example:

UmeySan · Posted: Thu Jun 14, 2007 1:45 pm

Socker_Dad !

Well done, great answer, very well detailed & comprehensible.
My respekt.

Regards, UmeySan

Btw: MVC = D2

Pons · Posted: Fri Jun 15, 2007 3:45 pm

Hi,
Sorry for the delay, that is not f bytes that is an four bytes.
I dont know how to copy my main frame screen here. so i just copy the content.

CEE3207S The system detected a data exception (System Completion Code=0C7).
From compile unit PL759P at entry point PL759P at compile unit offset +0000BB18 at entry offset +0000BB18 at

address 0006EB18.
<> LEAID ENTERED (LEVEL 05/09/2005 AT 11.27)
<> LEAID PROCESSING COMPLETE. RC=0

So you just copy the last Four bytes fo teh offset. BB18. Then you may use the Endevor Footprint option with the corresponding program list, you find this bytes.

It shows as

ADD 00BB18 so this add cause the problem. in this corresponding line you may find the code which is causing the problem

ADD 1 TO PLOV-IBS-ACTVY-CNT.

Its an Alpha Numeric Character and they try to add...

Anuj Dhawan · Posted: Wed Jun 27, 2007 7:38 pm

Thanks socker_dad. I'll keep your suggestions in mind to deal with next abend/s & will come up with new queris if required.

Thanks Pons.