[Info-vax] Process memory settings

[Joseph Huber]

Syltrem wrote:

> 
> "Syltrem" <syltremzulu at videotron.ca> wrote in message
> news:AwUgm.549222$Tp1.144878 at en-nntp-01.dc1.easynews.com...
>> Also if that helps, no matter what parameter I change (PGFLQUO, WSEXTENT
>> etc) the SHOW PROC/QUO will always show this after the compiler exits :
>>
>> Peak working set size:     645568
>> Peak virtual size:         845664
>>
>>
>> And I cannot increase the max authorized WS so that "Peak virtual size"
>> can go higher. Why can't I increase it ? Where is this value derived from
>> ?
> 
> 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.
> 

As others have told already, the working set size is NOT your problem.

But to answer the question: it is the minimum of WSEXTENT (per user in UAF),
and the system parameter WSMAX. 

--
Joseph Huber, http://www.huber-joseph.de