× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Basically I've been told that faulting is rather high on Base and it's
been suggested that I move Domino out to a different pool. I've been told
that moving to a separate lpar isn't worth the hassle of ptf's, upgrades,
saves, etc.

I want to ensure that I have enough memory for this new pool without
starving Base.

Other than memory are there other things I should tune? For example
comparing DSPSBSD on my domino servers and on QUSRWRK and QSYSWRK (two big
consumers of Base) shows the Routing entries. I figure that if I move
Domino I would have to add the new pool to the subsystem description and
change the routing entry to use this new pool and Base. For example, a
"traditional" system may have QBATCH and
Pool Storage
ID Size (K)
1 *BASE
2 *SHRPOOL1
and it's "Routing entries" will have
Pool identifier . . . . . . . . . . . . . . : 2
So I figure I would have to change those two items in the subsystem
description. Should I also look at altering the classes used?
For example, my ARCHIVE1 server using ARCHIVE1 subsystem and ARCHIVE1
class.
Class . . . . . . . . . . . . . . . . . . . . . . : ARCHIVE1
Library . . . . . . . . . . . . . . . . . . . . : QUSRNOTES
Run priority . . . . . . . . . . . . . . . . . . : 20
Time slice in milliseconds . . . . . . . . . . . : 2000
Eligible for purge . . . . . . . . . . . . . . . : *YES
Default wait time in seconds . . . . . . . . . . : 120
Maximum CPU time in milliseconds . . . . . . . . : *NOMAX
Maximum temporary storage in megabytes . . . . . : *NOMAX
Maximum threads . . . . . . . . . . . . . . . . . : *NOMAX
Text . . . . . . . . . . . . . . . . . . . . . . :

QUSRWRK has multiple routing entries. All using different classes. A
sample class there might be:
Class . . . . . . . . . . . . . . . . . . . . . . : QSYSCLS50
Library . . . . . . . . . . . . . . . . . . . . : QSYS
Run priority . . . . . . . . . . . . . . . . . . : 50
Time slice in milliseconds . . . . . . . . . . . : 2000
Eligible for purge . . . . . . . . . . . . . . . : *YES
Default wait time in seconds . . . . . . . . . . : 30
Maximum CPU time in milliseconds . . . . . . . . : *NOMAX
Maximum temporary storage in megabytes . . . . . : *NOMAX
Maximum threads . . . . . . . . . . . . . . . . . : *NOMAX

I shouldn't have to mess with the classes, should I? Just the pool
definitions and the routing entries, right?

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.