Re: Allocation of memory pools

Here, we use QPFRADJ set to 2.  Some people will argue that it's not 
dynamic enough for their shop.  This will only switch so much memory at a 
time.  Great for gradual shifts, etc.  However if you do like we do and 
fire up 11 domino partitions at once QBASE gets memory starved big time 
while they are starting up.  QPFRADJ just doesn't move that much memory at 
once.  I suppose we could modify our programs that fire up Domino and have 
it do a CHGSHRPOOL to blast memory out of QINTER and QSHRPOOL1 to free it 
up back into *base immediately prior to starting up the Domino servers, 
but I didn't want to calculate that.

"IF" this affects your shop and you find that the memory adjustment is not 
quick enough, etc for your shop it may behoove you to look at a third 
party package that adjusts more to your taste.  We didn't.

Another thing to consider.
WRKSHRPOOL
F11=Display tuning data
This allows you to set something like, I don't care how bored this pool 
is, do not take more than x memory from it so that when I start this one 
huge job I don't have to twiddle my thumbs waiting on QPFRADJ.  Conversely 
you can say I don't care how busy Fred's query makes QINTER; do not take 
more than x memory from everywhere else and put it there and make my batch 
jobs, etc, suffer terribly.  This, we have played around with.

Rob Berendt