Solving System Abend S878

bachi234 · New User Joined: 15 May 2007 Posts: 6 Location: VA

This problem occurs if the compile parms are different.
I got the same problem and i changed the compile parms and ran it and it went fine.

Thanks.

Guru Bob · New User Joined: 31 Jan 2008 Posts: 21 Location: Malaysia

Ok so the problem solved or still existing?

If using TSO can you not execute it in batch or is it a TSO process.

If TSO then you only have 2m or 4M or 8M usually allocated to TSO. Depends on your sysprogs.

I suspect then you are running below the line with QSAM buffers but not sure why.

Why do you not make a change and display the file DDNAMe as they open successfully and CLOSE under SYSPRINT or similar. LEast it will show you how far you get.

You need to know the BLKSIZE so you can work out how much storage you are using for all the files you are accessing. LOADLIBS and all.

swapnadeep.ganguly · Active User Joined: 21 Mar 2007 Posts: 203 Location: India

Hi Shitij,

I am not moving the Load Library.

I had created a compile JCL for testing purposes using my personal load library. When I used this library, I was able to execute my job successfully.

However, when I staged my component in Endevor, a load library was created for the purpose. But when I am using this loadlibrary to execute my Batch job, my job is abending with S878.

enrico-sorichetti · Posted: Wed Feb 20, 2008 11:42 am

So after all You found a difference
the best thing to do is to speak with the endevor support team
looks like it is their job to fix everything up

but to avoid this kind of problems the process used to build entities should be always the same

swapnadeep.ganguly · Active User Joined: 21 Mar 2007 Posts: 203 Location: India

Hi,

Can any one please let me know how can we code the GETMAIN macro?

bachi234 · New User Joined: 15 May 2007 Posts: 6 Location: VA

Swapnadeep,

You said that you created compile JCL for testing purpose,check with the endevour compile listing and compare the compile parms and you will definitely find the difference.

I think you need to hard code this compile and link edit parms when you are compiling in endeavour.
COMPILE PARMS ===> RENT,ADV,NODYNAM,NOSEQ,DATA(31)
LINK EDIT PARMS ===> AMODE(31),RMODE(24).

I faced the same problem which you faced in test region i could run it with out problem when i staged it in Changeman(in your case it is endeavor) my compile job went fine but when i took the load lib from changeman package and ran the job i got S878 abend.

You can say that you can put REGION=0M in the run jcl and you will solve the problem but its not advicable becz it may not work the same as you did so change the compile parms and runt it i am sure u are gonna solve it..

Thanks

swapnadeep.ganguly · Active User Joined: 21 Mar 2007 Posts: 203 Location: India

Hi Bachi,

The solution provided by you worked. Thanks a lot...

xknight · Posted: Thu Mar 06, 2008 2:12 pm

Just change your region=0M ......then try it....

878 ABEND HAPPENS WHEN IT LAST'S OUT THE SPECIFIED REGION SIZE.

Mistermind · New User Joined: 08 Feb 2008 Posts: 46 Location: Dublin

Your harmless loadlib probably has a default RMODE=24, ie. the loadmodule is loaded at 24-bit address below the 16MB line. The more modern loadlibs probably have RMODE=31, ie. inisisting on loading above the 16MB line, which means your partition requires a larger REGION= size.

mohan tarte · New User Joined: 01 Nov 2008 Posts: 1 Location: Pune

Hi Bachi,

Thanks a lot man!!
We were also able to resolve the S878 error by including those compile options in changeman while compiling the program.

COMPILE PARMS : RENT,ADV,NODYNAM,NOSEQ,DATA(31)
LINK EDIT PARMS : AMODE(31),RMODE(24)