|
View previous topic :: View next topic
|
| Author |
Message |
JayC
New User
Joined: 27 Sep 2008
Posts: 70
|
|
|
|
Case closed ... (Almost )..anyway, This is how the story ended...
It seems that a recent implementation to the DB ( wasn't correct) hence this update job which gave me the S0C7 was bypassing alot of records which would other wise have normally gone through the program and updated the DB fine.
The problem with the new DB field was fixed.... corrective action to prevent the many bypasses (millions) were taken, and the same notorious file was rerun through the same program (this program which gave me the S0C7 was not fixed or corrected in the corrective action)... and the whole thing ran through absolutely fine.
My guess is that due to the large volumn of bypasses-counters/variables tracking the same would have overflown...
Anyway - time and effort taken to solve the S0C7 using "Follow the yellow brick road" I mean, "follow the OFFSET of the abending instruction were in this case were futile.
I guess I was just narrow-minded to think that the Abending Instruction-OFFSET address would give me all the answers... would give me all the answers...OFFSET |
|
| Back to top |
|
 |
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19243
Location: Inside the Matrix
|
|
|
|
Hello,
| Quote: |
| I guess I was just narrow-minded to think that the Abending Instruction-OFFSET address would give me all the answers... would give me all the answers...OFFSET |
Using the offset, you can find where the abend occurred and what caused the abend, but the why the condition exists often takes most of the work 
Good to hear it is now working - thank you for letting us know 
d |
|
| Back to top |
|
|
|
|
