Re: Reducing ODBC connection impact

Hello Jim,

Am 06.12.2019 um 20:09 schrieb 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