If a process is not taking much CPU while not impacting paging, the
issue is unlikely memory; what memory pool it runs in will not matter.
More likely it is the priority of the process which is limiting the CPU
that is available to that process versus others with a better priority,
or that the application needs to be coded to take advantage of parallel
processing due to any serialized nature of its work, or if already the
application is very parallel then it may need to reduce impact of waits
due to too much time spent in serialization versus actual work, or ???
There is a newsgroup ibm.software.iseries.pase dedicated to PASE on
the news server news://news.software.ibm.com
This mailing list archive is Copyright 1997-2019 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