× 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.



Is there really nothing unique about a memory pool, other than the name?
Sure the size also.
But other than size or name?
For example, shared vs calc on the paging? Are certain loads better in
one than the other?

Is there a reason to have jobs with certain contentious job properties out
of the same pool? For example, are any of the attributes shown in DSPJOB
OPTION(*RUNA) contentious between jobs of other settings?
Or subsystem routing entries utilizing different classes (WRKCLS)?
After all, it is the subsystem routing entry which determines what pool to
run a particular job in.

On our main production box QBATCH has two pools. Subsystem pool 1 points
to *BASE. Subsystem pool 2 points to *SHRPOOL1. Some of the subsystem
routing entries say use subsystem pool 1 and some say subsystem pool 2.


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.