🚀 go-pugleaf

Some additional information about some of the resource waits you mention:

    	4	RWPFF	Page file full.  The page file to which this process
    			is assigned is full.
Symbol and meaning defined, but never used in the code in either V3 or V4.

    	5	RWPAG	Waiting for paged pool.
Never used in V3, used in V4.

    	6	RWBRK	$BRKTHRU wait.
Used in V3, obsolete and never used in V4.  (The V3 broadcast mechanism was
very different and had hooks deep into many pieces of the system.  The V4
mechanism is much cleaner and works with, rather than against, the terminal
driver.)

    	7	RWIMG	Image activator interlock.
Used V3, obsolete in V4.  (Implemented an interlock between INSTALL and the
image activator.  Now, the lock manager is used.)

    	8	RWQUO	A pooled quota has been exceeded.  Use SDA to figure
    			out which one.
Symbol and meaning defined, but never used in the code in either V3 or V4.

    	9	RWLCK	Lock ID database is full? (can anybody fill me in?).
Symbol and meaning defined, but never used in the code in either V3 or V4.

    	12	RWMPB	Waiting for the modified page writer (to do something,
    			but I'm not sure what.  Can anybody fill me in?).
Indicates that a process tried to fault a modified page out of its working
set, but the modified page list was too big (larger than MPW_WAITLIMIT).
This is an emergency self-protection mechanism that triggers when insufficient
page file space, or other incorrect parameter settings, cause the modified
page writer to get way behind - processes that try to create even more work
for the modified page writer get throttled.  (Transient occurences of RMMPB
are probably common.  For example, setting MPW_WAITLIMIT to the same value as
MPW_HILIMIT (which AUTOGEN seems to like to do) makes this quite likely.)

Since modified page writing is done by the SWAPPER, which runs as a process
at priority 16, high-priority real-time processes that hogged the system
could also cause this situation.

    	13	RWSCS	Waiting for a systems communications services
    			(cluster) event.
Used by the cluster-wide lock manager.

    	14	RWCLU	Waiting for a cluster transition.
Used by the cluster-wide lock manager.

Some waits (RWSCS, RWCLU, for example) occur at elevated priorities and are
never interruptable for things like CTRL/Y or process deletion.  Others
(RWAST, RWMPE) may or may not be interruptable.

The wait states noted above as "Never used in the code" or "Obsolete in V4"
may show up in SDA if the process state gets corrupted somehow.

							-- Jerry
-------