IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

How to use CEEDUMP to solve S0C7


IBM Mainframe Forums -> JCL & VSAM
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
mkssampathkumar
Warnings : 1

New User


Joined: 31 Aug 2006
Posts: 57
Location: chennai

PostPosted: Wed Dec 27, 2006 9:53 am
Reply with quote

Hi
when am executing a program ,am getting SOC7 abend.
It shows clearly the reason for the error in Sysout but am not getting the exact place or variable name where the error occurs .it also creates the CEEDUMP.

With the help of CEEDUMP ,can we get any idea?
Both CEEDUMP and Sysout displays the error..Whats the use of CEEDUMp(is shows some offset address).
Whats the use of offset address.

Any body Clarrify this??


Thanks in advance..
Back to top
View user's profile Send private message
guptae

Moderator


Joined: 14 Oct 2005
Posts: 1208
Location: Bangalore,India

PostPosted: Wed Dec 27, 2006 10:03 am
Reply with quote

Hi There,

Please go through the attached doc
Back to top
View user's profile Send private message
mkssampathkumar
Warnings : 1

New User


Joined: 31 Aug 2006
Posts: 57
Location: chennai

PostPosted: Wed Dec 27, 2006 10:55 am
Reply with quote

Hi
Thanks for ur reply.It is very useful to me..But here am not using SDSF.we are using IOF.in IOF ,where we have to see the the error.

Go to complier listing (i.e. the SDSF for compile JCL)--u r specifying to see the error in the SDSF.if am using IOF,instead of this in where i have to see.
Back to top
View user's profile Send private message
mkssampathkumar
Warnings : 1

New User


Joined: 31 Aug 2006
Posts: 57
Location: chennai

PostPosted: Wed Dec 27, 2006 11:10 am
Reply with quote

Hi
I tried with ur program..

The error which am getting is

"Z" was not defined as a data-name. The statement was discarded.

"Y" was not defined as a data-name. The statement was discarded.

Am getting this error in SYSPRINT itself.Am not getting anything like what u told..

1 LOG *
2 JCL *
3 MESSAGES *
4 SYSPRINT COB
5 SYSPRINT LKED

After executing ,these are the five steps am getting .In SYSPRINT, am getting the error clearly.Here CEEDUMP is not creating..

Thanks ..
Bye..
Back to top
View user's profile Send private message
William Thompson

Global Moderator


Joined: 18 Nov 2006
Posts: 3156
Location: Tucson AZ

PostPosted: Wed Dec 27, 2006 2:49 pm
Reply with quote

Try it again, the compute line is commented out, you do not need to include it in your test.
Back to top
View user's profile Send private message
mkssampathkumar
Warnings : 1

New User


Joined: 31 Aug 2006
Posts: 57
Location: chennai

PostPosted: Wed Dec 27, 2006 3:18 pm
Reply with quote

Hi
Thanks for ur reply..
i tried and am getting SOC7 error.i searched in complier listing (i.e. the IOF for compile JCL), but there is no string called 'HEXLOC'.


Defined Cross-reference of data names References

6 A. . . . . . . . . . . . . . . M12 13 15
7 B. . . . . . . . . . . . . . . 13 14
8 C
9 X. . . . . . . . . . . . . . . M13 16


AM getting like this(SCREEN 3), after the above lines its shows


Context usage is indicated by the letter preceding a procedure-name reference.
These letters and their meanings are:
A = ALTER (procedure-name)
D = GO TO (procedure-name) DEPENDING ON
E = End of range of (PERFORM) through (procedure-name)
G = GO TO (procedure-name)
P = PERFORM (procedure-name)
T = (ALTER) TO PROCEED TO (procedure-name)
U = USE FOR DEBUGGING (procedure-name)






i cant find the details which are present in SCREEN 4.

AM using XREF compiler option.other than that anything i have to specify additionally??

Thanks in advance

Bye..
Back to top
View user's profile Send private message
William Thompson

Global Moderator


Joined: 18 Nov 2006
Posts: 3156
Location: Tucson AZ

PostPosted: Wed Dec 27, 2006 3:33 pm
Reply with quote

I am sorry, I rarely use a dump on a data exception other than to look at where the PSW is pointing and get the base/displacement pointing to the offending data.
Simply put, you probably have garbage in a filed you are doing some math against.
If you can't find somebody in your shop to help you read the dump, you could begin to isolate where the problem is in your code by imbeding displays in your program and noting which was the last display prior to the abend. Each time you test, you can narrow down the abend location by changing the location of the displays until you have a display on each side of a single statement and only the before one works before the abend. Then look at that statement and where the data comes from.

Good luck, and keep us posted on your progress.
Back to top
View user's profile Send private message
dick scherrer

Moderator Emeritus


Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix

PostPosted: Wed Dec 27, 2006 10:35 pm
Reply with quote

Hello,

You might look at your source program for any uninitialized numeric fields in your WORKING-STORAGE.

Sometimes a group move will move non-numeric values over a defined numeric field.

Often, "new" data has invalid data in what is supposed to be a numeric field.

As Bill said
Quote:
Good luck, and keep us posted on your progress
Back to top
View user's profile Send private message
sri_code

New User


Joined: 20 Nov 2006
Posts: 19
Location: india

PostPosted: Wed Dec 27, 2006 11:17 pm
Reply with quote

cant you use Xpeditor.........
in Xpeditor its very easy to find this... just keep the MONITOR ON and put a breakpoint at the end and run the program(F12)... it'll stop at the place where SOC7 occurs.
Back to top
View user's profile Send private message
William Thompson

Global Moderator


Joined: 18 Nov 2006
Posts: 3156
Location: Tucson AZ

PostPosted: Wed Dec 27, 2006 11:36 pm
Reply with quote

Xpeditor, we don't need no stinking Xpeditor..... icon_lol.gif (apologies to Alfonso Bedoya in Treasure of Sierra Madre)
Back to top
View user's profile Send private message
mkssampathkumar
Warnings : 1

New User


Joined: 31 Aug 2006
Posts: 57
Location: chennai

PostPosted: Thu Dec 28, 2006 10:00 am
Reply with quote

Hi
We have to use 'OFFSET' compiler option to display the offset(HEXLOC) address in SYSPRINT.after am using the OFFSET compiler option am getting the offset address..

Those who are getting SOC& abend,just look at the compiler option whether they using the OFFSET option or not.

Thanks for all those who are help me to solve this problem..

Thanks
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> JCL & VSAM

 


Similar Topics
Topic Forum Replies
No new posts S0C7 - Field getting overlayed COBOL Programming 2
No new posts how to solve this power failure shutd... ABENDS & Debugging 5
No new posts Any idea about how to solve 3022 aben... IMS DB/DC 3
No new posts S0C7 abend while running a Cobol Program COBOL Programming 2
No new posts S0C7 abend not able to locate COBOL Programming 8
Search our Forums:

Back to Top