| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 169.1 | SYSGEN PQL Minimums Set Higher? | XDELTA::HOFFMAN | Steve, OpenVMS Engineering | Mon Feb 10 1997 17:05 | 7 |
|
Take a look at the SYSGEN> SHOW/PQL values, and see if the PQL_M*
quota values are set above those of your username -- these quotas
are the minimum values. (The PQL_D* values are the default values,
if no value has been specified as part of the process creation or
process login.)
|
| 169.2 | Yes they follow the PQL*'s but... | CALDEC::SCHMIDT | | Mon Feb 10 1997 17:41 | 7 |
| Yes, they do match the pql_m* values.
But don't the pql values get applied to non-interactive processes (i.e
whose mode is "other")
My interactive login session should follow the limits as set in the uaf,
right & not what is set by the pql parameters?
|
| 169.3 | | ZIMBRA::BERNARDO | Dave Bernardo, VMS Engineering | Mon Feb 10 1997 18:48 | 3 |
| The minimum values set by the PQL parameters affect ALL processes.
d.
|
| 169.4 | How autogen sets pql_m* values | CALDEC::SCHMIDT | | Tue Feb 11 1997 10:59 | 9 |
| o.k. What I don't understand is why autogen appears to be setting the
pql_mw* parameters based on what min_wsmax is set at in my modparams.dat
file.
It just doesn't seem right that this is the expected behaviour. The
outcome is that pql_mwsextent is set to what wsmax gets set to. Makes
setting the repective uaf quota a moot point.
btw this is vms 6.2-1h3
|
| 169.5 | | ZIMBRA::BERNARDO | Dave Bernardo, VMS Engineering | Tue Feb 11 1997 11:17 | 6 |
| The minimum working set parameters have to be large enough to
support WSMAX. The values are used to size the balance set slots
which contain the working set lists.
WSEXTENT getting set to WSMAX is intentional and is meant to
override the values in the UAF.
|
| 169.6 | CSC is happy about it... | GIDDAY::GILLINGS | a crucible of informative mistakes | Tue Feb 11 1997 22:00 | 13 |
| re .4:
Since many UAFs are much older than the current system, some of them
contain quotas appropriate for ancient, resource starved systems. Prior
to the AUTOGEN change (V6.0), it wasn't that unusual for the CSC to find
systems with lots of memory paging heavily because the users were
constrained by tiny WSEXTENTS. These days, the amount of memory on systems
and the newer algorithms for managing it make the concept of WSEXTENT pretty
much obselete.
AUTOGEN setting PQL_MWSEXTENT=WSMAX just makes sure that customers use
the memory they paid for.
John Gillings, Sydney CSC
|