| Title: | DECWINDOWS 26-JAN-89 to 29-NOV-90 |
| Notice: | See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit |
| Moderator: | STAR::VATNE |
| Created: | Mon Oct 30 1989 |
| Last Modified: | Mon Dec 31 1990 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 3726 |
| Total number of notes: | 19516 |
Dear All:
In DECW$CHECK_PARAMS.COM it checks to see if, among others,
the SYSGEN parameters PQL_MWSQUOTA & PQL_MWSDEFAULT are
equal to 60. If higher or lower, it suggests changing them to
60.
Now, a couple of things:
1) I thought the PQL_M* parameters were not to be modified
and to be just used as minimum settings below which
the PQL_D* parameters should not be set.
2) I work at CSC, and today had a customer who modified,
at DECW request, these parameters to 60 and rebooted.
DECW would not come up and produced LKWSETFUL errors.
Which is not unexpected considering what I understand
about these Sysgen Parameters. We changed the PQL_M*
parameters back to default and all worked well except
for CHECK_PARAMS yelling about them.
Should this be happening? If so, Why?
Do I have the right definition of the Sysgen Parameters?
Hmmmmmm,
jjjones
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 324.1 | CSC32::JJONES | Sat Mar 04 1989 22:15 | 8 | ||
A little more about .0
The customer is on a VSII/GPX.
I have a VS3100 and my PQL_M* parameters are set to what
DECW$CHECK_PARAMS.COM wants to see them as and I have no
problem.
| |||||
| 324.2 | PEKKA::PEURA | Pekka Peura, CSG-Helsinki | Sun Mar 05 1989 05:39 | 12 | |
Has your customer changed VIRTUALPAGECNT higher than what AUTOGEN
would calculate it to? I had this same
problem on my 16MB VS3200. I had upped VIRTUALPAGECNT to 200000
to be able to analyze large crashdumps. With that high VIRTUALPAGECNT
i a) either got LKWSETFUL at boot time or b) had to change PQL_MWSQUOTA
to a higher value and then CHECK_PARAMS complained.
After i lowered VIRTUALPAGECNT to 100000 LKWSETFUL problem went away.
Pekka
| |||||
| 324.3 | CADSYS::DIPACE | Alice DiPace | Sun Mar 05 1989 17:01 | 18 | |
re: .0, .2 We have had a similar problem with a 3500 with 32meg of memory. We eventually modified DECW$CHECK_PARAMS.COM to check that these parameters were atleast 60 but greater ok. With machines with larger amounts of memory and/or large virtual needs, these parameters must be greater than 60 or you will get a lock working set full problem. We have filed the problem in this notes file (?? or some other permutation of this notes file) and qar'ed it, but the problem still seems to get shipped. Guess they don't expect some decent sized work stations out there... Alice | |||||
| 324.4 | pql parameters defined | CSC32::JJONES | Fri Mar 17 1989 22:19 | 58 | |
Just to add a little info on some questions I raised in .0
===========================================================================
PQL Minimum SYSGEN Parameters Used For Interactive Logins
COPYRIGHT (c) 1988 by Digital Equipment Corporation.
ALL RIGHTS RESERVED. No distribution except as provided under contract.
TITLE: PQL Minimum SYSGEN parameters used for interactive logins.
PRODUCT: VMS, Version 4.n
DATE: January 1988
SOURCE: Customer Support Center/Colorado Springs
\ by G. House of VMS/C
\
INFORMATION:
Users get higher values than those specified for process quotas and/or
working set sizes in their UAF records.
When a login is performed using LOGINOUT, one would expect that all
the process quotas would be taken from the values defined in the UAF
record for the user. This is not the case. The PQL_Mxxx SYSGEN
parameters are also utilized.
ANALYSIS:
The PQL parameters define the default (PQL_Dxxx) and minimum
(PQL_Mxxx) values to be used for the associated process quotas. The
default quotas are used for detached processes which do not execute
LOGINOUT to acquire the quota values from SYSUAF. The minimum
parameters are enforced for all processes on the system.
The following values are affected:
WSQUOTA, Working set quota
WSEXTENT, Working set extent
WSDEFAULT, Working set default
PGFLQUOTA, Page file quota
BIOLM, Buffered I/O limit
DIOLM, Direct I/O limit
BYTLM, Byte count limit
PRCLM, Subprocess quota
FILLM, Open file quota
ASTLM, AST quota
TQELM, Timer queue quota
CPULM, CPU time limit
ENQLM, Enqueue (lock) quota
JTQUOTA, Job logical name table quota
| |||||