[Info-vax] Process memory settings

[Syltrem]

"John Reagan" <johnrreagan at earthlink.net> wrote in message 
news:gPednZO2EabKqBnXnZ2dnUVZ_iydnZ2d at earthlink.com...
>
> "Syltrem" <syltremzulu at videotron.ca> wrote in message 
> news:OHVgm.541093$6p1.295994 at en-nntp-02.dc1.easynews.com...
>>
>> I tried a few more things:
>>
>> COBOL/NOOBJECT
>> This is not very helpful to me, but it does complete successfully so 
>> tells the the source code is ok and compiler optimization can be done.
>>
>> COBOL/NOPTIMIZE also completes successfully. Better.
>>
>> COBOL/OPTIMIZE=LEVEL=1 fails.
>>
>> Though I now have something usable, if not optimal, I'd still want to 
>> understand how to increase the working set, if someone knows.
>
> First of all 51,000 lines of COBOL is actually quite small in the COBOL 
> world.  Is it "computer generated" or "human generated"?
>

human

> You still didn't mention what version.  V5.9 is the latest.

We didn't compile COBOL for years here. My version is older than I tought.

COBOL V2.5-961


>
> As for "it does compile on the VAX so it must compile in 32-bits", the VAX 
> COBOL compiler is quite different than the Alpha COBOL compiler.  Totally 
> different optimization/code-generator.  Actually, the VAX COBOL compiler 
> doesn't do much optimization at all.
>
> I'm a little shocked it dies with OPT=LEVEL=1.  The minimal set of 
> optimizations that get enabled at level 1 are quite simple.  The 
> interesting ones don't kick in until 2,3,4.
>
> Make sure you are using the latest compiler.  If it still runs out of 
> memory, I'd submit a problem report including the source so the team can 
> reproduce it.
>
> John
>

I'll install the latest compiler.and try again
Are you sure about 5.9 being the latest version ? I have a CD dated June 
2009 with Cobol 2.9

Syltrem