Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

Possible reasons and solutions for s0c7 & s0c4

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> ABENDS & Debugging
View previous topic :: :: View next topic  
Author Message
priya_gmain

New User


Joined: 18 Sep 2006
Posts: 7

PostPosted: Thu Oct 12, 2006 3:02 pm    Post subject: Possible reasons and solutions for s0c7 & s0c4
Reply with quote

Hi

Wat is the possible reasons and solutions for s0c7 & s0c4

Regards
priya
Back to top
View user's profile Send private message

guptae

Moderator


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

PostPosted: Thu Oct 12, 2006 3:27 pm    Post subject:
Reply with quote

Hi there,

S0C4


An invalid main storage address was generated.

POSSIBLE CAUSES

1. Uninitialized index or a runaway index due to a program loop. (T
could also cause a S0C7).

2. An attempt to reference an output area before the data set was opene
after it was closed.

3. An attempt to execute a module with unresolved link-edit references.

4. The items specified in the USING lists of the calling and called p
grams are assumed by the compiler to be identical in order, data ty
and field length. Any discrepancy in this correspondence may result
an S0C4.

5. See also S0C1

WHAT TO DO


1. Check the values of the indexes and LINKAGE SECTION. (SHOW INDEX
LINKAGE)

2. Check the status of input and output data sets used. (SHOW FILEs)

3. Use COUNT with the AFTER command to check for program looping.


System ABEND: S0C7

Description: This ABEND is a data exception and can only occur when
decimal (packed) instructions are used. One of the
following can cause this error:

1) The sign or digit codes of one or more bytes
manipulated by the packed or CONVERT TO BINARY
instructions is invalid for packed decimal use.
Packed decimal digits must be in the range 0 through
9, with only the sign digit being a digit in the range
A through F.

2) Fields in decimal (packed) arithmetic overlap
incorrectly.

3) A packed decimal multiplicand has too many high-order
significant digits.

Possible causes for this abend include:

Subscript error, referenced beyond table
COBOL: working storage not initialized
bad data, should check data for errors
garbage in a field being tested or displayed
move zeroes to group level is display, had sublevels
that were not
period missing after imperative statements within AT
END clause
binary field in an arithmetic operation is not large
enough to accept result

User Action: Correct the format of the data being manipulated by the
packed decimal instructions in the program and rerun the
job.
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 -> ABENDS & Debugging All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts TABLES/MS from Specialized Solutions ... Gary Jacek COBOL Programming 0 Thu Sep 03, 2015 12:08 am
No new posts TABLES/MS from Specialized Solutions ... Gary Jacek IMS DB/DC 0 Thu Sep 03, 2015 12:08 am
No new posts S0C7 abend not able to locate Rijit COBOL Programming 8 Wed Apr 01, 2015 4:03 pm
No new posts Getting S0C4 while running COBOL Data... kalakuntlavenkat COBOL Programming 4 Thu Feb 26, 2015 8:48 pm
No new posts S0C7 Data Exception Error Niti Srivastava ABENDS & Debugging 4 Mon Feb 23, 2015 5:40 pm


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us