Re: MVT COBOL under MVS3.8j.

"Giuseppe Vitillaro giuseppe-yuD/ahkh7LvrZ44/[email protected] [H390-MVS]" <[email protected]>
Newsgroups gmane.comp.emulators.hercules390.mvs
Message-ID <[email protected]>
On Thu, 12 Sep 2019, Gary [email protected] [H390-MVS] wrote:

> OK, I did some "light" reading of the 
> LY28-6486-2_OS_VS_COBOL_Compiler_Rel_2_PLM manual.  Fun stuff. The XREF 
> listing is produced by Phase 6A (pgs 190 & 191).  Of interest is that if XREF 
> was specified, then Phase 6A uses the GETALL routine in the TAMER to get all 
> available storage...
>
> Going back to GC28-6399-2.  There are 3 parameters of interest. The JCL 
> REGION, COBOL SIZE and COBOL BUF.  Appendix D is of informative reading if 
> you what all of the facts.  Here is the short version, COBOL SIZE is the 
> maximum amount of storage to be used by the compiler.  COBOL BUF is the 
> amount of storage to use from SIZE for use by I/O file buffers and the like.  
> The JCL REGION value must be 6K greater than the COBOL SIZE value. Appendix D 
> has a nice long formula for calculating the necessary memory required by the 
> compiler.  The key information is that the resident phase 00 takes 80K and 
> the minimum buffer size is 2768 BYTES.
>
> Peppe's TK4- values where 9M for REGION, 8192K for SIZE and 2048K for BUF.  
> There is a large difference between 2768 bytes and 2097152 bytes (2M).
>
> I would suggest that Peppe overide the COBOL BUF to be 4096K or don't specify 
> it at all and let the compiler calculate the required size for the buffer 
> pool.  Using a quarter of the available REGION for buffers seems to be a 
> waste.  The SIZE parm could also be bumped up to 9M - 6K to get a little more 
> room.
>
> If it still fails, then a more detailed reading of the Logic Manual and of 
> memory management modules for MVS and MVT to look for differences.
>
> Hope this helps.
>
> Gary
>
One word for all the "valuable" informations provided
in the previous posts to my question: THANKS!

A big THANK YOU to all!

I'll try to read the manual and to experiment
with these values.

Peppe.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.