×
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.
There is some good reason for both:
- *machine should have a minimal but reasonable value for the system functions to work without being swapped out. A flexible behaviour would have too much negative performance impacts. You set a reasonable minimum value in QMCHPOOL which cannot be lower than the recommendation of the system firmware (Try to set it to 128MB on a V7R4 box) but one can increase the value (if you have the memory) and your system is under heavy load. See also WRKSHRPOOL
- *spool also should not be set to flexible if the system is low on memory. Writers usually should start sending data as soon as there is something in the OutQ. Consider a client waiting at the sales desk for some printout but the writer program has been swapped out. *spool should be set to a reasonable value depending on system and load. A good start is 2MB per each single writer.
-h
Am 08.02.2020 um 10:42 schrieb Patrik Schindler <poc@xxxxxxxxxx>:
I don't know why IBM recommends *SPOOL being static. My guess is that it avoids the *BASE pool to be shrinking and growing all the time when pfradjust kicks in and sometimes adjusts according to (lack of) activity in *SPOOL.
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.
midrange.com
