|
View previous topic :: View next topic
|
| Author |
Message |
sanjaykumar.s
New User
Joined: 22 Jul 2008
Posts: 1
Location: Chennai
|
|
|
|
| What is the general procedure to solve a SOC7 error? I need it in detail. |
|
| Back to top |
|
 |
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006
Posts: 6966
Location: porcelain throne
|
|
|
|
| there is a lot of 'DETAIL' in the forums about soc7's. |
|
| Back to top |
|
|
UmeySan
Active Member
Joined: 22 Aug 2006
Posts: 771
Location: Germany
|
|
|
|
@Dick !
Great, i really love your answers |
|
| Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006
Posts: 6966
Location: porcelain throne
|
|
|
|
| I try not to be an asshole, but, the poster has obviously not searched or looked at any of the threads in debugging or cobol..... |
|
| Back to top |
|
|
roopannamdhari
Warnings : 1
New User
Joined: 14 Sep 2006
Posts: 71
Location: Bangalore
|
|
|
|
Sanjay,
If compiler having "TEST" option than it will generate line number for Cobol pgm in compilation-outlist as well as displays statement number which causes pgm to abend
in CEEDUMP.
1. F Statement (in ceedump)
2. Take out the statement number
3. Find that statement number in compiler outlist to know which statement causing pgm to abend.
If compiler is using OFFSET than you can consider offset value
Thanks |
|
| Back to top |
|
|
|
|
