Re: Check your ancient performance settings

Hi

To reply to your assumption about activity level, here is the documentation from IBM, where activity level is an attribute of a pool definition in a subsystem definition -

A subsystem definition can have a maximum of 10 memory pool definitions specified. Included in the subsystem definition are:

* Pool definition identifier: This is the identifier inside the
subsystem description, of the storage pool definition.
* Size: This is the size of the storage pool expressed in KB (1K=1024
bytes) multiples and is the amount of main storage that the pool can
use.
* Activity level: This is the maximum number of threads that can run
at the same time in the pool.

A subsystem also has a maximum active attribute for itself.



On 10/10/2019 4:13 AM, Patrik Schindler wrote:

Hello Vernon,

-snip-
Sorry, this is where my knowledge is all too blurry. Activity levels as I understand means how many programs can be active in a pool at once. Being activated as I understand means, these must be kept in RAM. If a pool isn't large enough and there are many active programs, they compete for RAM which runs the pool into a thrashing condition.
I'm wondering how this can be a number of programs, since I guess allocation of storage within programs greatly varies with different purposes. Maybe this is calculated by means of a basic minimum allocation for every active program to just run. Filling a load-all SFL within a program to it's maximum size might not count to that minimum but just adds paging activity in that pool. Which in turn invalidates my initial thought of pool size divided by minimum allocation equals activity level.

Maybe you can elaborate on the true meaning of the term activity level?

-snip-