Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

Insufficient Storage issue while executing a job

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL & VSAM
View previous topic :: :: View next topic  
Author Message
rexx77

New User


Joined: 14 Apr 2008
Posts: 73
Location: Mysore

PostPosted: Fri Jul 10, 2015 10:29 pm    Post subject: Insufficient Storage issue while executing a job
Reply with quote

Hi Folks,

Greetings!!

For a new development project, we enhanced the existing production COBOL module with around 800 to 900 lines of code to make it 2700 LOC. This includes adding two dimensional array with max occurrence 10000 (with depending on clause). When executing this module in batch mode (it is common module) in test region we got insufficient storage issue.

Code:

       Current Condition:
         CEE0198S The termination of a thread was signaled due to an unhandled condition.
       Original Condition:
         CEE0813S Insufficient storage was available to satisfy a get storage (CEECZST) request.
       Location:
         Program Unit: CEEVGTSI Entry: CEEVGTSI Statement:  Offset: +00000B9E


Checked with my storage team and they suggested that it is to do with load module size increase and asked me to check the internal array size, as during batch mode execution I am getting storage issue. Even I have reduced the size of the array to 1 max occurrence to see how it behaves, still storage issue is occurring. My shop has restriction on adding REGION parameter in Job card to address this issue.

can any one help me with possible suggestion why this issue is occurring in test regions? Any solution to this is most welcome

Thanks in advance.
Back to top
View user's profile Send private message

Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 7913
Location: Bellevue, IA

PostPosted: Fri Jul 10, 2015 10:45 pm    Post subject:
Reply with quote

The code you added increased the program memory requirements beyond what you have available. Increase the region size. If you believe this is not possible, contact your site support group for assistance -- because the ONLY solution to this problem is to increase the REGION value (or you can go back to the old program and forget making the changes).
Back to top
View user's profile Send private message
rexx77

New User


Joined: 14 Apr 2008
Posts: 73
Location: Mysore

PostPosted: Sat Jul 11, 2015 12:05 am    Post subject:
Reply with quote

Thanks Robert.

What is quite puzzling me is, the same common module if executed from other jobs (Job A and Job B, Job C, Job D) it works out fine. But this storage issue is occurring only in few jobs which calls this module, max 3 jobs.

I understand the size of the load module has increased and storage is unavailable, but it should have met with insufficient storage issue in all executions across all jobs. If any one has any idea, please let me know

Will keep you posted after discussing with my storage team. Thanks
Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 7913
Location: Bellevue, IA

PostPosted: Sat Jul 11, 2015 1:51 am    Post subject:
Reply with quote

Quote:
but it should have met with insufficient storage issue in all executions across all jobs
This makes ABSOLUTELY no sense to me. If job A's main program uses 5 megabytes and job B's main program uses 500 kilobytes and job C and D have main programs using 2 megabytes, why would you think the region requirements for all 4 jobs would be the same? You cannot look at just the common subprogram to determine memory requirements -- you must look at the entire run unit (the main program and all loaded subprograms) to determine memory requirements. And for COBOL, as an example, there are different IBM-supplied routines for different functions -- one program may not use any of them and another uses several of them; hence the load module size of COBOL programs can vary drastically. Not to mention that various compiler options can impact load module size as well!
Back to top
View user's profile Send private message
rexx77

New User


Joined: 14 Apr 2008
Posts: 73
Location: Mysore

PostPosted: Mon Jul 13, 2015 8:39 pm    Post subject:
Reply with quote

Thanks Robert. I just overlooked the fact from the calling module/Job perspective.

Thanks for the detailed clarification.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL & VSAM All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts DFHRESPONSE returns issue divated CICS 3 Wed Nov 02, 2016 6:32 pm
No new posts Can sending 5 MB data between cobol p... Kevin Vaz CICS 12 Tue Oct 18, 2016 4:50 pm
No new posts Easytrieve - Report writing - Only 1 ... Abhi Nature CA Products 2 Wed Sep 14, 2016 11:40 am
No new posts REXX Screen not working due to LINKED... sundarkudos CLIST & REXX 1 Mon May 09, 2016 1:44 pm
No new posts Issue in sending zip file as mail att... ajithajt JCL & VSAM 8 Thu Apr 07, 2016 9:11 am


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us