The Migration Guide for Enterprise COBOL release 6.1 says:
Compile-time storage requirements are substantially increased compared to prior
versions of Enterprise COBOL. The compiler requires a minimum of 200 M region
size to run.
When upgrading to COBOL V6.x, CA Endevor COBOL Generate processors might need to be updated to increase storage requirements.
Recommend the following as a way to determine the necessary increase:
- Compile a large program (ideally the largest one you can find onsite) outside of Endevor with the old COBOL
- Reduce the REGION size until the compile fails. Note the minimum REGION required by the old compiler (REGION_OLD).
- Do the same thing with the new compiler. Note the minimum REGION required by the new compiler (REGION_NEW).
- Increase the REGION size for Endevor batch runs by the difference (REGION_NEW minus REGION_OLD)
** Remember that REGION= specified in the JOB statement overrides REGION= specified in the EXEC statement.
This means that Endevor users need to remove or change the REGION parm in the JOB cards used when submitting a batch job from Endevor
It all virtual storage. The problem arises when Processors or Endevor batch JOB statements have a REGION size of 4M specified and the new COBOL 6.x compiler is requiring for something much larger.
According to the IBM z/OS MVS JCL Reference --
Use the REGION parameter to specify the amount of central or virtual storage that the job requires. The system applies the value that you code on REGION to each step of the job.
Use the MEMLIMIT parameter to specify the limit on the total size of usable virtual storage above the bar in a single address space.
Thanks for the link to the presentation Philip
If you code REGION=200M,MEMLIMIT=3G then it is only virtual memory being consumed isn’t it?