SOC7 is data exception and can occur when packed 
instructions are used. For its resolution , we have to 
correct the data or conversion formatin the program.

SOC7 abend occure due to the data exception or mostly due 
to moving of non-numric data into numric data field.

we can resolve this correcting the data format.

Actualy S0C7 abends normaly happens due to wrong data/ non-
numeric data in numeric field.By wrong data i mean to say 
like if key is duplicated or some garbage data.

      The resolution can be done in two ways :
1)code fix by which you can fix the cobol program code and 
stage it
2)By deleting the bad records from the file 

But be carefull about the file deletion if its a batch 
process and some other  jobs depend on the p[articular 
job,so it can effect to other if any wron fixation done.

Q31)	Basically you need to correcting the offending 
data. Many times the reason for SOC7 is an un-initialized 
numeric item. 
Examine that possibility first. Many installations provide 
you a dump for run time abend’s ( it can be  generated also 
by calling some subroutines or OS services thru  assembly 
language).  These dumps provide the offset of the last  
instruction at which the abend occurred.  Examine the 
compilation output XREF listing to get the verb and the 
line 
number of the source  code at this offset.  Then you can 
look at the source code to find the  bug.  To get capture 
the 
runtime dumps,  you will have to define some  datasets 
(SYSABOUT etc ) in the JCL. If none of these are helpful,  
use 
judgement and DISPLAY to localize  the source of error. 
Some installation might have batch program debugging 
tools.  Use them.