Urgent!! SOC4 reason code 4



Support for OS/VS COBOL, VS COBOL II, COBOL for OS/390 & VM and Enterprise COBOL for z/OS

Re: Urgent!! SOC4 reason code 4

Postby dick scherrer » Fri Dec 16, 2011 12:46 pm

Hello,

Please note that i asked about the load modules - not some "other modules" that were built for testing.

If the modules are restaged, recompiled, relinked, there may be some subtle difference(s) that cause the problem (like SSRANGE as Nic mentioned).
Hope this helps,
d.sch.
User avatar
dick scherrer
Global moderator
 
Posts: 6304
Joined: Sat Jun 09, 2007 8:58 am
Has thanked: 3 times
Been thanked: 91 times

Re: Re: Urgent!! SOC4 reason code 4

 

Re: Urgent!! SOC4 reason code 4

Postby durga_r82 » Fri Dec 16, 2011 12:51 pm

Hi,

We tried both the ways. Both gave same result in development.
1. Copied the load module from the other env
2. Retrieving, Recompiling, Relinking.
durga_r82
 
Posts: 24
Joined: Fri Dec 16, 2011 9:30 am
Has thanked: 0 time
Been thanked: 0 time

Re: Urgent!! SOC4 reason code 4

Postby BillyBoyo » Fri Dec 16, 2011 12:58 pm

Have you determined which instruction is failing in ProgB, and if not, why not?
BillyBoyo
Global moderator
 
Posts: 3804
Joined: Tue Jan 25, 2011 12:02 am
Has thanked: 22 times
Been thanked: 264 times

Re: Urgent!! SOC4 reason code 4

Postby BillyBoyo » Fri Dec 16, 2011 1:07 pm

Unable to "view" the instruction, or find it in the dump, this is probably because a whole chunk of your program has been overwritten with spaces.

In Cobol it is much more difficult to branch to a data area, as the compiler generates all the code. You have to have your code overwritten by something which happens to be a branch instruction. You will be enormously unlucky if it is that, so stick to the overwriting.

What is the change that has been made to the programs involved?

If you have SSRANGE on then is the order of your items on the CALL and PROCEDURE DIVISION USING the same?

Does ProgB call any other modules?
BillyBoyo
Global moderator
 
Posts: 3804
Joined: Tue Jan 25, 2011 12:02 am
Has thanked: 22 times
Been thanked: 264 times

Re: Urgent!! SOC4 reason code 4

Postby durga_r82 » Fri Dec 16, 2011 1:11 pm

Steve guided me from dump I posted that it is in the BASR

THE FAILING INSTRUCTION IS AT 13F5C24A
0DEF BASR R14,R15



THE BREAKING EVENT ADDRESS (BEA) IS 00000000_13F7C6BE

In ProgB, it is failing immediately after entering the program for the 3rd request. The first statement in ProgB is a display "*******Start of ProgB********' which doesn't get displayed.
Is this you're referring? Please let me know if any specifics from dump is required. Thanks.
durga_r82
 
Posts: 24
Joined: Fri Dec 16, 2011 9:30 am
Has thanked: 0 time
Been thanked: 0 time

Re: Urgent!! SOC4 reason code 4

Postby durga_r82 » Fri Dec 16, 2011 1:15 pm

ProgB calls a Stored procedure of different application and also has COBOL as INCLUDEs

Both the call and procedure division using uses the same Copybook. We had checked the length of it also and is matching with ProgB linkage.
durga_r82
 
Posts: 24
Joined: Fri Dec 16, 2011 9:30 am
Has thanked: 0 time
Been thanked: 0 time

Re: Urgent!! SOC4 reason code 4

Postby BillyBoyo » Fri Dec 16, 2011 1:21 pm

Can you post the code for the CALL and the PROCEDURE DIVISION USING and show the LINKAGE SECTION for progB.

Next hour I'm busy, sorry... if it is still ongoing I'll see you then.

EDIT: On borrowed time here. Can you try to find the program code for ProgB in the dump. Find the start of Progb, look for the displacement of the first instruction in your compile listing, make an adress from that and look at it, tell us what you see. Is it instruction-looking, or "odd".
Last edited by BillyBoyo on Fri Dec 16, 2011 1:24 pm, edited 1 time in total.
BillyBoyo
Global moderator
 
Posts: 3804
Joined: Tue Jan 25, 2011 12:02 am
Has thanked: 22 times
Been thanked: 264 times

Re: Urgent!! SOC4 reason code 4

Postby durga_r82 » Fri Dec 16, 2011 1:23 pm

Anything that has to do with DSNECP10. Not sure what it means but looks like that is where it is failing when lionked via CEEBTOR.

Is the ENTRY POINT AT 00015000 below related to DASD SIZE HEX (15000). This was specified in the listing. Is there any relation?

PROGRAM LANGUAGE LAST EXECUTED STATEMENT
ProgB COBOL/ZOS FAILED WITH ABEND CODE S0C4 AT
ADDRESS 160870BC ProgB + X'BC'
ProgA COBOL/ZOS CALLED ProgB FROM OFFSET 924A
DSNECP10 CALLED ProgA VIA A LINK FROM
ADDRESS 00047250 DSNECP10 + X'32250'


E X T E N D E D S Y S T E M V I E W

PROGRAM ProgB FAILED WITH ABEND CODE S0C4
AT ADDRESS 00000000_160870BC, OFFSET BC IN PROGRAM EPIGTEBT.

FAILING INSTRUCTION: STH R4,0
INSTRUCTION HAS NO OPERANDS


REGISTERS AT TIME OF ABEND:
NAME VALUE DATA DESCRIPTION/LOCATION
R0 00000000_00081498 EPIGTE STORAGE: SUBPOOL(001) KEY(8)
R1 00000000_000814A0 'A6080000 0008'X STORAGE: SUBPOOL(001) KEY(8)
R2 00000000_00081018 NULLS ('00'X) STORAGE: SUBPOOL(001) KEY(8)
R3 00000000_13FFC0B8 NULLS ('00'X) STORAGE: SUBPOOL(002) KEY(8)
R4 00000000_140440B8 NULLS ('00'X) STORAGE: SUBPOOL(002) KEY(8)
24 00000000000440B8 NULLS ('00'X) PROGRAM DSNECP10 +2F0B8
R5 00000000_000697FC '93F77240 93F7'X STORAGE: SUBPOOL(001) KEY(8)

.
.
.
.

PROGRAM LEVEL 1
PROGRAM DSNECP10 VIA A LINK CEEBTOR FROM ADDRESS 00047250 DSNECP10 +
X'32250'
ENTRY POINT AT 00015000
REGISTER SAVE AREA AT 0000D758
0 00000000_00047374 1 00000000_00012EA0 2 00000000_00000000 3 00000000_00012E90
4 00000000_00000000 5 00000000_00000016 6 00000000_00012A78 7 00000000_00000000
8 00000000_00000000 9 00000000_00013600 A 00000000_00012D40 B 00000000_80046D00
C 00000000_0000D758 D 00000000_00000000 E 00000000_80FDE5A8 F 00000000_93F53000
durga_r82
 
Posts: 24
Joined: Fri Dec 16, 2011 9:30 am
Has thanked: 0 time
Been thanked: 0 time

Re: Urgent!! SOC4 reason code 4

Postby BillyBoyo » Fri Dec 16, 2011 3:36 pm

For you DISPLAY the compiler (I don't know which version you have) probably has a Load for V(IGZCDSP ), a LA for parameters and then the BASR.

Why is the display there? What is EPIGTEBT? The displacement there is so close, it can't be a Cobol program. Any idea what it is?
BillyBoyo
Global moderator
 
Posts: 3804
Joined: Tue Jan 25, 2011 12:02 am
Has thanked: 22 times
Been thanked: 264 times

Re: Urgent!! SOC4 reason code 4

Postby BillyBoyo » Fri Dec 16, 2011 3:55 pm

I don't get how a STH and BASR are both involved.

I apologise, but I'm really only flitting in and out on this one - may just be making it more confusing, but never could resist a dump. Now a surprise (I didn't know about it) children's Christmas event.... back later. Good luck 'til then.
BillyBoyo
Global moderator
 
Posts: 3804
Joined: Tue Jan 25, 2011 12:02 am
Has thanked: 22 times
Been thanked: 264 times

PreviousNext

Return to IBM Cobol

 


  • Related topics
    Replies
    Views
    Last post