MVSFORUMS.com

chandhroo · Beginner Joined: 02 Dec 2002 Posts: 36 Topics: 13

Hi,
Im running PROG1 which has got 19 subroutines. Basically this is to migration to LE370. In LE370, when I run PROG1, it abends with SOC4. I found the program which abends, when i give DISPLAY statement to find location, it executes successfully. I removed DISPLAY statement one by one to find which DISPLAY statement makes it successful and found one. I haven't found any issue like this so far. Could you tell me if there anything clicks?

Thanks
Chandru

kolusu · Posted: Fri Dec 12, 2003 10:44 am Post subject:

Chandru,

I don't think DISPLAY statements has got anything to do with your abend.can you please post the exact error message(starts CEEXXXX). I beleive that it has something to do with the compile options of the subroutine.

Kolusu
_________________
Kolusu
www.linkedin.com/in/kolusu

chandhroo · Beginner Joined: 02 Dec 2002 Posts: 36 Topics: 13

Kolusu,
I also think, DISPLAY statement does nothing. But I tried all the way to find solution, but couldn't. When run thru xpediter, it works fine.

I'm getting
CEE3204S The system detected a protection exception (System
Completion Code=0C4).

--Chandru

hari_uss · Posted: Fri Dec 12, 2003 2:12 pm Post subject:

Chandru,

May be you have unequal number of parameters between the main program and subprograms. That is, you have the total length of communication area same, but number of parameters coded in CALL USING in main program and LINKAGE SECTION of subprogram are different? If that is the case, try to make them same (you might want to replace some FILLERs in linkage section of subprogram with variables like LK-FILLER1, LK-FILLER2 etc).

Not sure whether it will work, but may be worth a try.

Hari.

kolusu · Posted: Fri Dec 12, 2003 2:35 pm Post subject:

chandroo,
This is just a wild guess, but worth a try. Before you added any of display statements , the pgm might be pulling the subroutine from an OLD loadlib. Now once you add the display statements and compiled it , it is picking the latest version and there by you are not having any problem.The old loadlib must be compiled with a different AMODE

So check your steplib concatenation and check if the above mentioned is true.

vani · Beginner Joined: 28 May 2003 Posts: 51 Topics: 30

Hi,

I too am having the same problem of CEEDUMP.

I have 8 subroutines and a main program. This is a C-Db2 application.
wherein I will only precompile and compile all the subroutines and linkedit all the 8 subroutines while compiling the main. Then do a bind and run the application.

Its throwing the below error, please help it out.

CEE3204S The system detected a protection exception (System Completion Code=0C4)
From entry point IBuffer::removeRef() at statement 386 at compile unit
+00000058 at address 0D968610.

chandhroo · Beginner Joined: 02 Dec 2002 Posts: 36 Topics: 13

Kolusu/Hari,
Sorry for the delayed response. I tried all possible ways as mentioned above, but no change. Now I have found other solution to fix SOC4.
Currently DD statement for output file is-
//TAPEOD DD DUMMY.
When I change add DCB parameter for this DD statement as given below works fine.
//TAPEOD DD DUMMY,
// RECFM=VB,LRECL=63,BLKSIZE=23476

Could you please tell why this difference is? I thought when we say DUMMY, there will not be any IO operation take place, so it doesn't matter to code DCB parameters, but it does matter. Could you please explain and send me link for this issue.
Expecting your valuable reply.

Thanks
Chandru

kolusu · Posted: Tue Jan 06, 2004 3:27 pm Post subject:

Chandru,

Can you post the FD entry for the file TAPEOD?

Thanks,

Kolusu
_________________
Kolusu
www.linkedin.com/in/kolusu

chandhroo · Beginner Joined: 02 Dec 2002 Posts: 36 Topics: 13

Actually we have IO handler assembler routine for all IO processing, so please find all of them.
File description for TAPEOD:

kolusu · Posted: Tue Jan 06, 2004 4:03 pm Post subject:

Chandru,

When you specify RECORD CONTAINS 0 CHARACTERS and the BLOCK CONTAINS 0 CHARACTERS clause is specified (or omitted), the block size is determined at run time from the DD parameters or the data set label of the file. For output data sets, with either of the above conditions, the DCB used by Language Environment will have a zero block size value. If you do not specify a block size value, the operating system might select a System Determined Block Size (SDB).

I am guessing that since you are using a common routine which can be used for different file lengths, the routine is expecting the dcb parameters from the JCL.

Now lets us test something here. Do you have any other file in the same program where you are actually writting instead of dummying it out? If you do have just remove the dcb parameters for that file and run it. Let us know what you find

Thanks

Kolusu
_________________
Kolusu
www.linkedin.com/in/kolusu

chandhroo · Beginner Joined: 02 Dec 2002 Posts: 36 Topics: 13

Kolusu,
I removed DCB from other file as you said, which is also causeing abend. But still I'm not clear how it is working when we concatenate SYS1.COB2LIB, why it doesn't expect DCB parameters when we concatenate SYS1.COB2LIB. I couldn't provide correct reason for this issue. Because this issue is not documented in the manual for LE migration.

--Chandru

chandhroo · Beginner Joined: 02 Dec 2002 Posts: 36 Topics: 13

Hi,
Finaly found the solution for this issue. We raised this issue to IBM support team and got following response. Hope it will help you.