|
View previous topic :: View next topic
|
| Author |
Message |
simha520
New User
Joined: 28 Mar 2007
Posts: 2
Location: hyderabad
|
|
|
|
| HOW to handle these (soc7, socb) abends. can you guide me |
|
| Back to top |
|
 |
William Thompson
Global Moderator
Joined: 18 Nov 2006
Posts: 3156
Location: Tucson AZ
|
|
| Back to top |
|
|
kavisuresh
New User
Joined: 22 May 2007
Posts: 7
Location: chennai
|
|
|
|
S0C7 might be due to the below three reasons along with the user
action,
1)Description: A S0C7 FORCED FOR REASONS OTHER THAN DATA EXCEPTIONS, SUCH AS AN INVALID CONTROL CARD OR A FLAG NOT SET CORRECTLY ON THE REGISTER CONTROL FILE.
User Action: CHECK THE DISPLAY MESSAGES FOR THE ABENDING
STEP FOR ADDITIONAL INFORMATION.
2)Description: -READ IN A SIGNED COMP-3 FIELD INTO AN UNSIGNED
COMP-3 FIELD.
User Action: SIGN THE RECEIVING FIELD AND RECOMPILE.
3)Description: MOVING ZERO TO A TABLE 01-LEVEL THAT HAD COMP-3
FIELDS UNDER IT. THIS FILLED THE TABLE WITH X'F0'
User Action:
1. MOVE ZEROS TO THE ELEMENTARY TABLE FIELDS OR
2. USE INITIALIZE AT GROUP LEVEL (COBOL II)
S0CB might be due to the below reason along with User Action,
Description: This ABEND is caused by a decimal divide exception. A
quotient exceeds the specified data field size.
User Action: Dividing by zero is the most common cause of this ABEND.
Correct the program logic error that caused the divide
exception and resubmit the job.
Regards,
Kavisuresh |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
Very often, an s0cb is caused due to a divide by zero.
Is there something in your situation that is related to DB2? If not, your topic can be moved to a more appropriate category. |
|
| Back to top |
|
|
|
|
