guptae
Moderator
Joined: 14 Oct 2005
Posts: 1208
Location: Bangalore,India
|
|
|
|
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. |
|
