[Info-vax] SOLVED : Re: Process quota problem after upgrade to 8.4-2L1

[Stephen Hoffman]

On 2020-12-22 18:05:50 +0000, Arne Vajhj said:

> On 12/22/2020 9:33 AM, Phillip Helbig (undress to reply) wrote:
>> In article <rrsk17$10p8$1 at gioia.aioe.org>, Joukj
>> <joukj at hrem.nano.tudelft.nl> writes:
>>> Thanks Hoff, You pointed me to the Right solution: Doubling all the 
>>> pql_m* parameters did not help. But setting PQL_MPGFLQUOTA to 18000000 
>>> (may be too high but set the same as for "user" system) did the trick. 
>>> So also Tad's suggestion was correct. It wer the pagefile-quota.
>> 
>> I'll see if this helps my problem.  I remember adjusting quotas, but 
>> not system parameters.
> 
> My understanding is that setting PQL_MPGFLQUOTA sets the minimum 
> PGFLQUOTA so that even those usernames with lower values in SYSUAF get 
> the PQL_MPGFLQUOTA value.

Correct. That system parameter setting is a system-wide minimum. It's a 
fairly large hammer, but one that can be necessary.

> Are there scenarios where PQL_MPGFLQUOTA is required because SYSUAF 
> value is not used??

There are cases when the developer forgot to specify quotas such as on 
a detached process creation, yes.

These arise both with defaulted RUN /DETACH commands, and with 
defaulted $creprc calls.

Most developers eventually learn that the process quotas and the 
mailbox quotas and the IOSBs and such should not be defaulted.

Eventually.

Due to compatibility, some bad ideas from closer to VAX-11/VMS got 
rolling cannot be required.

These are among those.

Had a pair of apps years back, one blew up because the default mailbox 
quotas were too small, and the other app blew up when the same settings 
were too large.

Which is part of why I'm skeptical around the efficacy of containers, 
save as a means of software licensing arbitrage.


-- 
Pure Personal Opinion | HoffmanLabs LLC