How can I resolve a CLSCV00 or MK4CV00 storage error?

Document ID:  TEC444987
Last Modified Date:  07/21/2015
{{active ? 'Hide' : 'Show'}} Technical Document Details

Products

  • CA VISION:Builder for CMS
  • CA VISION:Builder for VSE
  • CA VISION:Builder for z/OS
  • CA VISION:Inform for CICS
  • CA VISION:Two for CMS
  • CA VISION:Two for VSE
  • CA VISION:Two for z/OS

Releases

  • CA VISION:Builder for z/OS:Release:15.0
  • CA VISION:Inform for CICS:Release:15.0
  • CA VISION:Two for CMS:Release:15.0
  • CA VISION:Two for z/OS:Release:15.0
  • CA VISION:Builder for CMS:Release:15

Components

  • CA VISION:Builder.:V:BLDR
  • CA VISION:Two:V:TWO

Description:

The seemingly obvious solution of increasing the REGION in the JCL does not work.

Solution:

Code                Message                                               Explanation 
---------           ----------------------------------         ----------------------------------- 
MK4CV00               NO MORE MAIN STORAGE AVAILABLE            MAIN STORAGE REQUIREMENTS HAVE
                      FOR TABLES/BUFFER/INTERNAL                EXCEEDED AVAILABILITY. 
                      ARRAYS. 
CLSCV00               NO MORE MAIN STORAGE                      MAIN STORAGE REQUIREMENTS HAVE 
                                                                AVAILABLE. EXCEEDED AVAILABILITY. 

When the above CV00 errors issue, the most common user response is to increase the REGION on his JOB or EXEC statement.

The problem is that the storage requirements that have been exceeded are VISION:Builder internal storage which are limited by the product, so increasing the REGION usually has no impact on the problem.

The first thing to note is what type of job is running.

If it is a COMLIB utility run, (i.e. PGM=MARKUTIL, MARKDUMP, MARKREST) then APARs CL104, BL132, BL141 and BL144 should be applied to increase the default amount of COMLIB working storage and optimize the way it is used. There are no negative consequences to applying these APARs in today's environments and Technical Support will be happy to supply them to any supported customer.

If it is a definition or processing run (PGM=MARKIV), then the most common solution is to increase internal working storage. The default is 1 Megabyte, but this can be overridden at the site level via the MAXETMN parameter in the site parameter module, M4PARAMS. The current setting can be seen on the banner page in the last column on the right, 3rd up from the bottom. Increasing this value in M4PARAMS would increase available working storage for all jobs run against that VISION:Builder loadlib. Again, in today's environments, increasing the site default from 1M to 4M presents no negative impact.

The amount of working storage available can also be overridden at run time by modifying the M4INPUT to the application. Add a fixed format RP statement with the MAXGETMN parameter, or a GETMAIN parameter to the freeform CONTROL command.

Note that in any case, when the working storage is increased, then the REGION must be increased to handle the addition if it is not already sufficient.

There is already an enhancement open to improving the documentation to clarify this message in future issues of the documentation.

Please help us improve!

Will this information enable you to resolve your issue?

Please tell us what we can do better.

{{feedbackText.length ? feedbackText.length : '0'}}/255

{{status}}

Not what you were looking for?

Search Again >

Product Information

Support by Product >

Communities

Join a Community >