Posted: Wed Apr 29, 2009 6:37 am Post subject: how to split a program ?
Hi,
I have a 8000 line program which is giving storage error
"Original Condition:
CEE0813S Insufficient storage was available to satisfy a get storage (CEECZST)"
Now I think the solution would be splitting the main program in to 2 and calling the second one..
Can someone tell me what are all the points to be taken care in doing so, And is this the right approach ? is there any better way to handle this case ?
I have looked into your site, but I am getting almost same details of my Dump master. I am almost sure that the issue is with the working storage space as the error comes when I am trying to increase the size of an array table.
Joined: 20 Oct 2006 Posts: 1411 Topics: 26 Location: germany
Posted: Wed Apr 29, 2009 8:45 am Post subject:
and how are you trying to increase the size of your array table (is that a COBOL internal table?) _________________ Dick Brenholtz
American living in Varel, Germany
Joined: 20 Oct 2006 Posts: 1411 Topics: 26 Location: germany
Posted: Wed Apr 29, 2009 11:53 pm Post subject:
suresh_d,
you are not answering my question, which I repeat:
how are you increasing the size of the array? _________________ Dick Brenholtz
American living in Varel, Germany
Joined: 26 Nov 2002 Posts: 12380 Topics: 75 Location: San Jose
Posted: Thu Apr 30, 2009 8:16 pm Post subject:
Suresh_d,
Compile the program with the compiler option DATA(31) (above the line). You can do this add the following line as the first line in your program (before ID division)
Depending on what the output shows, you may be able to adjust the HEAP and/or STACK values to get enough run-time storage. _________________ Regards,
Anuj
Thanks for your replies. I was on leave so couldn't reply you. Thanks for your suggestion but my knowledge is less to process your suggestions I landed back in same error or a different one This time I am copying and pasting the actual content from my program and job log.
CBL DATA(31) --> added this line
IDENTIFICATION DIVISION.
Code:
"CBL" was specified as a restricted word in the current reserved word table. The reserved word table used may be different from the IBM-supplied default. Refer to the Language Reference for IBM Enterprise COBOL Version 3 for information on reserved words.
So just gave REGION=0M but it gave same error.
Anuj,
I gave your syntax, it gave information, but I am not able to understand it, Can you explain me how to understand the info. here is the dump of the information I got -
Code:
CEE0813S Insufficient storage was available to satisfy a get storage (CEECZST) request.
The traceback information could not be determined.
Options Report for Enclave MPY033 05/05/09 7:03:51 AM
Language Environment V01 R08.00
1Storage Report for Enclave MPY033 05/05/09 7:03:51 AM
Language Environment V01 R08.00
0 STACK statistics:
Initial size: 131072
Increment size: 131072
Maximum used by all concurrent threads: 29416
Largest used by any thread: 29184
Number of segments allocated: 2
Number of segments freed: 0
0 THREADSTACK statistics:
Initial size: 0
Increment size: 0
Maximum used by all concurrent threads: 0
Largest used by any thread: 0
Number of segments allocated: 0
Number of segments freed: 0
0 LIBSTACK statistics:
Initial size: 4096
Increment size: 4096
Maximum used by all concurrent threads: 0
Largest used by any thread: 0
Number of segments allocated: 1
Number of segments freed: 0
0 THREADHEAP statistics:
Initial size: 4096
Increment size: 4096
Maximum used by all concurrent threads: 0
Largest used by any thread: 0
Successful Get Heap requests: 0
Successful Free Heap requests: 0
Number of segments allocated: 0
Number of segments freed: 0
0 HEAP statistics:
Initial size: 32768
Increment size: 32768
Total heap storage used (sugg. initial size): 0
Successful Get Heap requests: 0
Successful Free Heap requests: 0
Number of segments allocated: 0
Number of segments freed: 0
0 HEAP24 statistics:
Initial size: 8192
Increment size: 4096
Total heap storage used (sugg. initial size): 0
Successful Get Heap requests: 0
Successful Free Heap requests: 0
Number of segments allocated: 0
Number of segments freed: 0
0 ANYHEAP statistics:
Initial size: 16384
Increment size: 8192
Total heap storage used (sugg. initial size): 12528
Successful Get Heap requests: 999
Successful Free Heap requests: 977
Number of segments allocated: 1
Number of segments freed: 0
0 BELOWHEAP statistics:
Initial size: 16384
Increment size: 4096
Total heap storage used (sugg. initial size): 17048
Successful Get Heap requests: 5
Successful Free Heap requests: 0
Number of segments allocated: 2
Number of segments freed: 0
0 Additional Heap statistics:
Successful Create Heap requests: 0
Successful Discard Heap requests: 0
Total heap storage used: 0
Successful Get Heap requests: 0
Successful Free Heap requests: 0
Number of segments allocated: 0
Number of segments freed: 0
Largest number of threads concurrently active: 1
End of Storage Report
Joined: 20 Oct 2006 Posts: 1411 Topics: 26 Location: germany
Posted: Tue May 05, 2009 3:51 am Post subject:
from your compile listing, what are the AMODE and RMODE parms?
I may have interpreted something incorrectly, but it looks like this program is running as 24. If so, it is running under the 64-line which would make it reasonable that the program does not have enough space.
how much of the program executes before the failure? _________________ Dick Brenholtz
American living in Varel, Germany
My program is comipled using BAGMAN - AMODE=24 and there is no rmode in the complie jcl. I don't know how to see how much the program is exected. I am posting my joblog - thinking it may be useful. Let me know if anything else needs to be looked in. Sorry if I am testing your patience.
[code:1:7c0d639474]
07.03.12 JOB31294 ---- TUESDAY, 05 MAY 2009 ----
07.03.12 JOB31294 IRR010I USERID K82887 IS ASSIGNED TO THIS JOB.
07.03.13 JOB31294 ICH70001I K82887 LAST ACCESS AT 06:59:11 ON TUESDAY, MAY 5
07.03.13 JOB31294
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum