View previous topic :: View next topic
|
Author |
Message |
swapnadeep.ganguly
Active User
Joined: 21 Mar 2007 Posts: 203 Location: India
|
|
|
|
Hi,
1. We are using DATA(31)
2. REGION is not specified either in job card or Proc currently. However we have used REGION=2401M
3. The files that are created are simple PS.
4. There are in total 30 sequential files.
5. Not mentioned BLKSIZE in the JCL.
6. No I am not using REGION= in STEP execution. |
|
Back to top |
|
|
Guru Bob
New User
Joined: 31 Jan 2008 Posts: 21 Location: Malaysia
|
|
|
|
2401M sounds very high
OK DATA(31) means QSAM buffers are above the line so you are not out of sequential storage. However I am ammused that REGION=2041M is passing. Try specifying REGION=0M which will give you as much as you can get.
What is your BLKSIZES please? Do you have any QSAM files concatenated together? |
|
Back to top |
|
|
swapnadeep.ganguly
Active User
Joined: 21 Mar 2007 Posts: 203 Location: India
|
|
|
|
We have not mentioned the BLKSIZE parameter. The JCL takes it up on its own.
Also we are not concatenating any QSAM files. |
|
Back to top |
|
|
shitij
New User
Joined: 09 Sep 2005 Posts: 31 Location: Delhi
|
|
|
|
Hi,
As per as my understanding u are trying to move the Load of the pgm from one stage to another (to Pre-Prod?).
Is it that u have to bring the load from ur personal lib. to a pre-defined lib. and from there u can sub. the staging job via endevor...and the load is migrated to Pre-Prod.
From there u make a package and finally it reaches production.
Now from ur personal lib. to the pre-defined one its going smooth...but when u try to move to Pre-Prod it gives user abend.
Am I correct in mapping the problem???
Pls let me know as i have seen such issues in my system too.
Regards,
Shitij |
|
Back to top |
|
|
Guru Bob
New User
Joined: 31 Jan 2008 Posts: 21 Location: Malaysia
|
|
|
|
OK so its a while after executing starts. I am suspecting QSAM buffers. The program I can assume is linked AMODE(31) RMODE(ANY).
Do you open all SEQ files at once? If not can you determine from the DUMP which file youare at the opening point for?
Doesn't the abend offset allow you to pinpoint the actual line of code in the program at failure?
Can you Try REGION=0M on the jobcard.
The BLKSIZE is available on the JESMSGS for each DDNAME so you can see what each opened file BLKSIZE was.
One way of proving it is QSAM memory problem with S878 is to code BUNFO=1 or BUFNO=2 for all QSAM files and rerun. |
|
Back to top |
|
|
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. |
|
Back to top |
|
|
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. |
|
Back to top |
|
|
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. |
|
Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007 Posts: 10872 Location: italy
|
|
|
|
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 |
|
Back to top |
|
|
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? |
|
Back to top |
|
|
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 |
|
Back to top |
|
|
swapnadeep.ganguly
Active User
Joined: 21 Mar 2007 Posts: 203 Location: India
|
|
|
|
Hi Bachi,
The solution provided by you worked. Thanks a lot... |
|
Back to top |
|
|
xknight
Active User
Joined: 22 Jan 2008 Posts: 117 Location: Liberty city
|
|
|
|
Just change your region=0M ......then try it....
878 ABEND HAPPENS WHEN IT LAST'S OUT THE SPECIFIED REGION SIZE. |
|
Back to top |
|
|
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. |
|
Back to top |
|
|
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) |
|
Back to top |
|
|
|