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

[Chris Townley]

On 22/12/2020 23:13, Jan-Erik Söderholm wrote:
> Den 2020-12-22 kl. 20:45, skrev Chris Townley:
>> On 22/12/2020 18:05, Arne Vajhøj wrote:
>>> 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.
>>>
>>> Are there scenarios where PQL_MPGFLQUOTA is required because
>>> SYSUAF value is not used??
>>>
>>> Arne
>>>
>>>
>> I recollect that the PQL parameters are used for detached jobs - UAF 
>> for interactive, and batch queue settings for batch jobs
>>
>> Chris
> 
> Hm... No, PQL params are *not* specific for detached processes. And there
> is a dfference between the "default" and the "min" PQL params.
> 
> The "min" PQL parameters are always used for any process no matter how
> it is started. I'm not sure that you can override them on the RUN command.
> They override the UAF params for simple interactive logins, as an example.
> 
> Batch queue does not need to have any process parameters specified.
> They can, but are not needed. The UAF for the user that runs the batch
> job is normaly used.
> 
> The "default" params are used when there is no UAF parameters to use.
> Like when you do a run/detach and specify your own EXE directly in the
> RUN command.
> 
> If you do a run/detach/user=xxx and specify LOGINOUT.EXE (with your own
> COM file that runs *your* EXE as the /INPUT paramater) a full login will
> run and a DCL environment is created for your detached process. And in
> that case the UAF params for the specifed username are used (overrided
> by the PQL "min" params if they are higher).
> 
> The second way, using LOGINOUT.EXE, is needed if you need your process
> to have process local logical names. You can then define them in the COM
> file before you run your own EXE.
> 
> So in the second case using LOGINOUT.EXE, only the PQL "min" parameters
> comes into play, the "default" does not replace the UAF parameters. And
> your detached process runs in a full DCL environment.
> 
> If I'm not completely missing things here...
> 
> Jan-Erik.
Thanks - it was a long time ago, so forgive me if not quite right.

We used a lot of the RUN/DETACHED flavour to start detached job 
controllers that started various (partially) parameter controlled 
images. I had the job later of getting sensible quotas etc. after the 
original developers had moved on.

Chris