OK - I may have the answer - or maybe even a couple ways to get it!

The QWCRSSTS API (Retrieve System Status) has pool selection since V5R1. And it has 2 formats that might pertain to this question - SSTS0400 has pool information and includes the number of threads running in the pool. This might be more than the things we call jobs - so maybe SSTS0500 is the thing - it gives you the subsystems that are using a pool, and from that you could use the QWDRSBSD API (Retrieve Subsystem Information). Format SBSI0100 includes the number of active jobs in the subsystem.


-------------- Original message --------------
From: "Paul Jackson" <paulgjackson@xxxxxxxxx>

On Sat, Jun 7, 2008 at 6:42 AM, Bryan Dietz wrote:
I think that the QUSLJOB API could also be used:


It looks like Key 0307 (Current system pool identifier)
is promising.

Hi Brian,

it appears that that option only allows you to list what appears in
the resultant job list not what is filtered out initially. I guess if
I listed *every* job and then interrogated the pool identifier, that
might work although would be slow.

Thanks for the tip though,
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2015 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