Portal | Manuals | References | Downloads | Info | Programs | JCLs | Mainframe wiki | Quick Ref
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Profile Log in to check your private messages Log in
 
How to find which record caused the S0C7 Abend

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL & VSAM
View previous topic :: :: View next topic  
Author Message
MGayathri

New User


Joined: 19 May 2007
Posts: 25
Location: Chennai

PostPosted: Thu Jul 24, 2008 4:46 pm    Post subject: How to find which record caused the S0C7 Abend
Reply with quote

Hi,
In a one million input file, Using the List option i would know which COBOL statement caused the S0C7 .. Can you help me how to read the Address space,so that which record has caused the Abend and wat was the actual data for the cause.
Thanks,
Gay3
Back to top
View user's profile Send private message

Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 8165
Location: East Dubuque, Illinois, USA

PostPosted: Thu Jul 24, 2008 5:06 pm    Post subject:
Reply with quote

What does address space have to do with this? Hopefully, if you got an S0C7 abend you got a dump. Read the dump to fix the problem. The data that caused the problem will be in the dump, and usually the file buffer area that shows the specific record as well.
Back to top
View user's profile Send private message
MGayathri

New User


Joined: 19 May 2007
Posts: 25
Location: Chennai

PostPosted: Thu Jul 24, 2008 5:16 pm    Post subject:
Reply with quote

Hi,
I need to know how to read the Hex format of the DUMP which caused the error.HOw to locate the corect record with the offset address
Back to top
View user's profile Send private message
Garry Carroll

Active Member


Joined: 08 May 2006
Posts: 998
Location: Dublin, Ireland / Edinburgh, Scotland

PostPosted: Thu Jul 24, 2008 5:34 pm    Post subject:
Reply with quote

The PSW in the dump is most likely pointing to the instruction after the one that caused the S0C7. Six bytes before this is the decimal instruction. The 1st byte is the instruction, the 2nd byte the operand lengths (a nibble each), the 3rd & 4th bytes refer to operand 1 and the 5th and 6th byte to operand 2. The operand bytes are of format Rooo (register, offset). using the "registers at entry.." in the dump calculate the operand addresses and then, using the length fields, check which is not a valid decimal field.

Regards,
Garry.
Back to top
View user's profile Send private message
UmeySan

Active Member


Joined: 22 Aug 2006
Posts: 757
Location: Germany

PostPosted: Thu Jul 24, 2008 5:35 pm    Post subject:
Reply with quote

Hi MGayathri !

First check if any abend-aid software is unstalled in your shop.
so you get more informations as on a normal dump. let your mates teach you on how to interpret these.

Normaly you get EntryPointLocation of your Programm and the Adress, where abend occurs. So you can calculate:
AbendAdress - EntryPoint = Command in Listing
So one line before that, there's th command where the shit happens.

To locate the field and it's content in the dump:

Look at your ProgrammListing. get the adress of the Field there.
Add this to the EntryPointAdress of the dump. You get a new adress.
Look up this adress in the dump, There's your field.


And last but not least:

Check if XPEDITER is installed. If you don't know how to operate that tool, ask your mates to help you. Trace your programm with that tool.
Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 8165
Location: East Dubuque, Illinois, USA

PostPosted: Thu Jul 24, 2008 5:48 pm    Post subject:
Reply with quote

Quote:
I need to know how to read the Hex format of the DUMP which caused the error.HOw to locate the corect record with the offset address
It's pretty much impossible for you to learn how to read a dump from forum posts; you need help from your systems programmers or coworkers with the specific dump. For example, if you have Abend-Aid available it provides you with the current record (buffer) of each file; in a standard system dump you have to dig for this data.
Back to top
View user's profile Send private message
roopannamdhari
Warnings : 1

New User


Joined: 14 Sep 2006
Posts: 71
Location: Bangalore

PostPosted: Fri Jul 25, 2008 12:34 pm    Post subject:
Reply with quote

HI,

ceedump displays content of working storage variable when ABEND occurs . Using these working stroage variable information it is possible to find the record which causing abend.
Back to top
View user's profile Send private message
Anuj Dhawan

Senior Member


Joined: 22 Apr 2006
Posts: 6258
Location: Mumbai, India

PostPosted: Fri Jul 25, 2008 3:46 pm    Post subject:
Reply with quote

Hi,

Please search the forum on S0C7, you will get a lots of hit, some of them are -

http://www.ibmmainframes.com/viewtopic.php?t=31028&highlight=s0c7
http://www.ibmmainframes.com/viewtopic.php?t=29940&highlight=s0c7
http://www.ibmmainframes.com/viewtopic.php?t=29198&highlight=s0c7
http://www.ibmmainframes.com/viewtopic.php?t=29179&highlight=s0c7
http://www.ibmmainframes.com/viewtopic.php?t=10853&highlight=s0c7
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL & VSAM All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts ASP3 ABEND IN CICS Vedant CICS 0 Fri Oct 20, 2017 3:18 pm
No new posts Copy 4 byte of data from the last rec... arunsoods DFSORT/ICETOOL 9 Fri Oct 06, 2017 12:15 pm
No new posts Updating the Trailer count in variabl... satheshbabur DFSORT/ICETOOL 6 Wed Aug 30, 2017 9:49 pm
No new posts Repeat part of record multiple times Learncoholic DFSORT/ICETOOL 4 Tue Aug 29, 2017 11:33 am
No new posts Command to find TMEMBER name for a TPIPE Siva NKK Kothamasu IMS DB/DC 0 Wed Aug 16, 2017 6:08 pm

Facebook
Back to Top
 
Job Vacancies | Forum Rules | Bookmarks | Subscriptions | FAQ | Polls | Contact Us