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

To prevent SOC4 going to SNAP


IBM Mainframe Forums -> ABENDS & Debugging
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
Arunkumar Chandrasekaran

New User


Joined: 01 Jun 2010
Posts: 63
Location: India

PostPosted: Sat Jul 21, 2012 6:14 pm
Reply with quote

Hi all,
I am debugging one assembler program.It is getting SOC4 after some records went to SNAP.When I m tried debugging it using IBM debug tool
It is not showing SOC4 for the very first record.I tried with running the job with one record also.it is not showing SOC4 in Debug screen instead it is starting from first again.

now i need to make my job to fail with SOC4 when first record encountered abend.Is there any parameters used for that??
Please help.
Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 8577
Location: Dubuque, Iowa, USA

PostPosted: Sat Jul 21, 2012 7:00 pm
Reply with quote

Since an S0C4 abend is a storage problem, it is quite possible that the program you are working to debug requires X records (where X is 10, 100, 1000, 317 ... who knows the exact number?) to be processed before the storage violation occurs. Expecting that the program will abend on the first record is, in my opinion, a completely false and unrealistic expectation. You would be far better off using an actual dump taken when the S0C4 occurred for debugging -- although that may be completely beyond your skills to do.

And what does your topic title mean? It is not a very good title for what you are asking.
Back to top
View user's profile Send private message
Peter cobolskolan

Active User


Joined: 06 Feb 2012
Posts: 104
Location: Sweden

PostPosted: Sat Jul 21, 2012 7:12 pm
Reply with quote

Why dont you just alanyze the dump produced? It should clearly show you the failing instruction, and if its in your program, you should be able to understand. If the interrupt is not in your program, it takes some experience to find out, but often traces back to Read, Write or other macros, that you are responsible to use correct.
Back to top
View user's profile Send private message
PeterHolland

Global Moderator


Joined: 27 Oct 2009
Posts: 2476
Location: Netherlands, Amstelveen

PostPosted: Sat Jul 21, 2012 9:32 pm
Reply with quote

SNAP? Is that a snap dump? If yes, its an invoked dump in the program, output of that dump is going to a dataset defined by SDUMP. Consult the manuals for that.
Back to top
View user's profile Send private message
dick scherrer

Moderator Emeritus


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

PostPosted: Sun Jul 22, 2012 1:51 am
Reply with quote

Hello,

Does any of the code use an array? Sometimes an array "end" is not detcted and executable code or a saved address is "walked on" causing something unpredictable to happen (abend, data corruption, etc).
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 -> ABENDS & Debugging

 


Similar Topics
Topic Forum Replies
No new posts Handling abend to prevent termination CICS 0
No new posts Where is output from PARM ABEXIT (SNA... CA Products 3
No new posts IDMS/DC-COBOL program - SNAP error wh... IDMS/ADSO 5
No new posts Getting soc4 on internal table in cobol COBOL Programming 13
No new posts Help with SOC4 on DSNHLI/DSNELI DB2 11
Search our Forums:

Back to Top