|
View previous topic :: View next topic
|
| Author |
Message |
vamseepotti
New User
Joined: 21 Oct 2003
Posts: 45
|
|
|
|
| Could anybody explain how to Resolve S0C7 |
|
| Back to top |
|
 |
mdtendulkar
Active User
Joined: 29 Jul 2003
Posts: 237
Location: USA
|
|
|
|
Hello vamseepotti,
Basically you need to correct the offending data.
Many times the reason for SOC7 is an uninitialized numeric item. Examine that possibility first.
Many installations provide you a dump for run time abends ( it can be generated also by calling some subroutines or OS services through 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 JCL.
If none of these are helpful, use judgement and DISPLAY to localize the source of error.
Some installtion might have batch program debugging tools. Use them.
One of the tool is as below:
www.share.org/proceedings/sh98/data/S8417.PDF
Hope this helps,
Regards
Mayuresh Tendulkar |
|
| Back to top |
|
|
mcmillan
Site Admin
Joined: 18 May 2003
Posts: 1210
Location: India
|
|
| Back to top |
|
|
gv_narayana_rao
New User
Joined: 21 Feb 2004
Posts: 10
|
|
|
|
S0C7:
The S0C7 USUALLY COMES (ONE OF THE MANY REASONS) DUE TO INVALID NUMERIC OPERATIONS LIKE COMPARING A NUMERIC VALUE WITH LOW-VALUES OR HIGH-VALUES.
IN THIS CASE AS THE REPLY GIVEN BELOW U CAN GO THRU THE DUMP AND GET THE VERB AND RECTIFY THAT.
WE CAN ALSO RECTIFY THAT BY INITIALIZING THE NUMERIC VARIABLES PROPERLY WITH INITIALIZE VERB. U CAN ALSO USE ISNUMERIC CLAUSE IN COBOL TO OVERCOME THIS PROBLEMS.
HOPE THIS MIGHT HELP U.
[/i] |
|
| Back to top |
|
|
mcmillan
Site Admin
Joined: 18 May 2003
Posts: 1210
Location: India
|
|
|
|
Dear,
I will summarize your posts:
| Code: |
Basically you need to correct 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 abends ( 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 installtion might have batch program debugging tools. Use them |
|
|
| Back to top |
|
|
|
|
