Re: MVT COBOL under MVS3.8j.

Hello!
I don't know either. But there's still a rumor circulating that all of
the tools for program building for MVS (or Z/OS or OS/390) were built
on the matching time period of VM. And as for these problems? Two
things to say, one is I arranged it. And the second is that of if this
issue isn't resolved by the end of the month, then we are going to
leave the issue as is, and from there it will be revisited by the
person who started this, when he has the time, and report it as such.
-----
Gregg C Levine [email protected]
"This signature fought the Time Wars, time and again."


On Thu, Sep 12, 2019 at 6:13 PM Gary [email protected] [H390-MVS]
<[email protected]> wrote:
>
> <snip>
>
> By the way, the manual, GC28-6399-2, page 40, specify how
> to code the REGION statement for the compiler.
>
> I've never seen used the REGION statement in this way:
>
> REGION=(nnnnnxK[,nnnnnyK])
>
> It looks like the second parameter "nnnnnyK" is rather
> important for this COBOL compiler, but I can't understand
> why.
>
> May I ask for an explanation?
>
> > The answer you are seeking is found on the same page in the manual under the heading " Specifying Main Storage Requirements for a Job (Region)".  The short answer is unless you have an IBM 2361 Core Storage "attached" or your MVS has been "genned" for storage hierarchies, then you need not worry about the second memory allocation.  There is a Max storage size of 16383k, 1k less than 16M.
>
> I don't remember who stated that the compiler was built from "source" under VM.  Is that a viable option for MVS?
>
> Regards,
>
> Gary
>
>
>  don't remember
> 
> ________________________________
> Posted by: Gary <[email protected]>
> ________________________________

Sign on the door of the datacenter, "Remember to trust the fish who
runs the site!"