No, it shouldn't_take_ memory from jobs that need it, but
it should_give_ memory to the jobs that need it, pulling it from *BASE.
if you have diverse workloads (e.g. long running batch, short batch,
java) all competing for memory in *BASE you may well have worse
performance than you would have if you break out into pools...
Jim has a good lead to follow with Indexing, but I was able to help
performance by breaking out my work into separate shared memory pools...
On 11/1/2013 2:37 PM, Joel Harvell wrote:
> others will explain in better detail than me, but
> you need to break out your subsystems from*BASE into *SHRPOOLs*...
> I understand about moving SubSystems to other pools, but wouldn't that
> actually take memory away from the jobs that need it. This system is very
> sensitive to memory allocation. I want to be sure about the process and
> the affects before I offer a pool configuration change.
This mailing list archive is Copyright 1997-2013 by MIDRANGE dot 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 here. If you have questions about this, please contact