🚀 go-pugleaf

In article <2670@mitech.com>, gjc@mitech.com (George J. Carrette) writes:
> In article <BuA99G.GBF@comp.vuw.ac.nz>, don@rata.vuw.ac.nz (Don Stokes) writes:
>> gareth@lucifer.latrobe.edu.au (Gareth Who) writes:
>>> -SYSTEM-F-INSFMEM, insufficient dynamic memory
>> The size of process pool is affected by the CTLPAGES and PIOPAGES SYSGEN
>> parameters.  CTLPAGES is probably the one to hit.  (PIOPAGES is used mostly
>> for process-permanent files.)
>
> Is BYTLM involved in this?

No.  BYTLM controls the amount of nonpaged pool you can tie up at any one time
for buffers for buffered I/O operations.  Generally, running out of BYTLM
results in either RWAST wait state (the default unless you have disabled
process resource wait mode) or SS$_EXQUOTA.

Note that, although Don is correct in that *in this case* the INSFMEM status
is probably pointing to a problem with the process dynamic memory, this status
can also reflect a shortage of nonpaged pool.  In fact, SS$_INSFMEM is the
"not enough pool available" status return from EXE$ALONONPAGED and all of its
friends.  These routines are commonly used by device drivers, and the usual
action when such a routine returns with an error status is to return that error
status as the completion status for the user's $QIO call.

	--- Jamie Hanrahan, Kernel Mode Consulting, San Diego CA
uucp 'g' protocol guru and release coordinator, VMSnet (DECUS uucp) W.G., and
Chair, VMS Programming and Internals Working Group, U.S. DECUS VAX Systems SIG
Internet:  jeh@cmkrnl.com, hanrahan@eisner.decus.org, or jeh@crash.cts.com
Uucp:  ...{crash,eisner,uunet}!cmkrnl!jeh