Moving QSERVER to use *SHRPOOL1 is not going to have any impact on the QZDASOINIT jobs. Those jobs run in QUSRWRK by default. Only the daemon job (QZDASRVSD) runs in QSERVER.
Dawn
Email: dawnmayican@xxxxxxxxxxx<mailto:dawnmayican@xxxxxxxxxxx>
Web: Dawnmayi.com<
http://Dawnmayi.com>
Twitter: DawnMayiCan
Blog:
http://ibmsystemsmag.com/power-systems/i-can-blog/
LinkedIn:
https://www.linkedin.com/in/dawnmay/
On Dec 29, 2019, at 8:52 AM, Patrik Schindler <poc@xxxxxxxxxx<mailto:poc@xxxxxxxxxx>> wrote:
Hello Jim,
Am 06.12.2019 um 20:09 schrieb midrangel@xxxxxxxxxxxxxxxxx<mailto:midrangel@xxxxxxxxxxxxxxxxx>
What you need to review is the prestart job entries. That along with the
class (in the PJE) control how those jobs run. Depending on how much memory
you have consider putting them into their own pool and out of *BASE. Make
sure the activity level in the pool they do run in is high enough.
Thanks for your hints. I changed the *SBSD for the complete QSERVER to use *SHRPOOL1. I was setting it via wrkshrpool to 16M, 3 *MAXACT, and *CALC for dynamic allocation until I know how much memory tasks actually need. Perfadjust came along and already adjusted it to be 12M and 10 *MAXACT.
Need to do some test runs, to discover how the box behaves now with load on QZDASOINIT.
I still hadn't time to look into Work Management again, so I'm still confused how to interpret the output of wrksbs. Example: QSPL is shown to utilize pool 2 and 3 in columns 1 and 2. After my change, QSERVER has just an entry 5 in column 1. So far, I understand that QSERVER is not allowed to utilize any other pool than 5 which is tied to *SHRPOOL1 in chgsbsd. Right?
:wq! PoC
PGP-Key: DDD3 4ABF 6413 38DE -
https://www.pocnet.net/poc-key.asc
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx>
Before posting, please take a moment to review the archives
at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx<mailto:support@xxxxxxxxxxxx> for any subscription related questions.
Help support midrange.com<
http://midrange.com> by shopping at amazon.com<
http://amazon.com> with our affiliate link:
https://amazon.midrange.com
midrange.com
