View previous topic :: View next topic
|
Author |
Message |
bhairon singh rathore
New User
Joined: 19 Jun 2008 Posts: 91 Location: banglore
|
|
|
|
Hi All,
I am getting compilar error "THE SIZE OF THE "WORKING STORAGE SECTION" EXCEEDED THE COMPILER LIMIT OF 128 MEG, RESULT ARE UNPREDICTABLE" due to size of array.
My question is how can we increase the COMPILER LIMIT FROM 128 MEG
THANKS IN ADVANCE |
|
Back to top |
|
|
Bill Woodger
Moderator Emeritus
Joined: 09 Mar 2011 Posts: 7309 Location: Inside the Matrix
|
|
|
|
You can't.
You can look at using LOCAL-STORAGE if you can define something in the main program and the table is less than 128MB itself.
You can also investigate EXTERNAL.
You can also investigate "acquiring" LE storage and using a definition in the LINKAGE SECTION. You may have to use a "window" on this if greater than 128MB. |
|
Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006 Posts: 6250 Location: Mumbai, India
|
|
|
|
Unfortunately* you can not go beyond the limits, as Bill said, however, the question is -- why do you need such huge Working-Storage? Can you break them in Sub-modules?
This similar topic might interest you: ibmmainframes.com/about54572.html
* -- Limits are, well Limits -- there is nothing unfortunate about them. |
|
Back to top |
|
|
Bill Woodger
Moderator Emeritus
Joined: 09 Mar 2011 Posts: 7309 Location: Inside the Matrix
|
|
|
|
You can also wait until you have Enterprise COBOL V5.1. This is going to be available in June. You need to be on z/OS 1.13 to use it. You will then have up to 2GB for WORKING-STORAGE :-)
I think you need to show your data definition and how you intend to use the data. It is often the case that a different solution is possible, rather than having a huge table. |
|
Back to top |
|
|
bhairon singh rathore
New User
Joined: 19 Jun 2008 Posts: 91 Location: banglore
|
|
|
|
Thanks for your valuable suggestion - I will break my cobol code to sub module |
|
Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006 Posts: 6250 Location: Mumbai, India
|
|
|
|
Don't break it - just sub-divide! |
|
Back to top |
|
|
Garry Carroll
Senior Member
Joined: 08 May 2006 Posts: 1193 Location: Dublin, Ireland
|
|
|
|
Anuj Dhawan wrote: |
Don't break it - just sub-divide! |
...aahhhhh - terminology, terminology.... |
|
Back to top |
|
|
Bill O'Boyle
CICS Moderator
Joined: 14 Jan 2008 Posts: 2501 Location: Atlanta, Georgia, USA
|
|
|
|
As suggested by Bill W. -
Quote: |
"You can also investigate "acquiring" LE storage and using a definition in the LINKAGE SECTION. You may have to use a "window" on this if greater than 128MB." |
Why such a large array? What are you storing in this array?
Defining this array in LINKAGE, using an OCCURS DEPENDING ON, will yield a true variable-length array, as you would only need to acquire the amount of storage necessary, using the LE Callable routine "CEEGTST".
How does the array get populated? Is it via a VSAM file, QSAM file or by some other means?
Please advise.... |
|
Back to top |
|
|
|