Memory is no problem. Match up the combination of
Pool definitions
Routing entries
with WRKSHRPOOL. For example QBATCH may have multiple routing entries. If
I look at *ANY I will see:
Pool identifier . . . . . . . . . . . . . . : 2
and the pool definitions show:
Pool Storage
ID Size (K)

Now, if I look at WRKSHRPOOL you can match those up.

You do not allocate processor by subsystem. I'm sure you've seen
WRKACTJOB showing something in QINTER and then later something in QBATCH
using something close to or even exceeding 100% of CPU. But if you want a
snapshot there are some performance files you can analyze to see what
subsystem is consuming what amount of processor. Attached is a snapshot
from iNav. Remember, that's just analyzing performance data that exists
on your system. I am bcc'ing you since attachments are stripped from the

Rob Berendt

This thread ...


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

This mailing list archive is Copyright 1997-2019 by 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].