Re: Reducing ODBC connection impact

Hello Jim,

Am 29.12.2019 um 17:53 schrieb Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx>:

What you are referring to is the subsystem pool (1 in your example) and the
system pool (5 in this case) which is assigned by the system when the
shared pool (*SHRPOOL1) is first used by the system.

This confusing ID schema is not very helpful in getting a grip. :-)

Best practice says (particularly at the early version release you are
using) to always have *BASE as subsystem pool 1, and the memory you want
the jobs to use as subsystem 2 (or higher but that’s rare).

You’ve discovered the CHGSBSD command. It should look like:

CHGSBSD QSERVER POOLS((1 *BASE ) (2 *SHRPOOL1))

Thanks. I'm not sure how the OS handles such configuration. Memory is taken from *BASE. When is memory in *SHRPOOL1 utilized?

Then you must change the routing to force the system to use the subsystem pool 2.

Ah, okay. So the *BASE entry is just some kind of safekeeper?

Of course, questions answered raise new questions. :-) Would it maybe better to utilize a SBS-private pool? AFAIK, these can't be changed as shared pools can be by perfadjust but I don't think this is abig deal. More interesting would be how big I should size that memory pool.

Sorry if I messed up the commands, typing on my phone and going from memory
since not connected to a system at the moment.

No worries, you seem to be correct going just from memory. :-)

:wq! PoC

PGP-Key: DDD3 4ABF 6413 38DE - https://www.pocnet.net/poc-key.asc