This is usually very misunderstood. It's really the number of service class
PERIODS WITH velocity or response GOALS (i.e. with an importance level). The
reason is because WLM on each system will wake up every ten seconds (that's an
eternity in a z14!) to see if goals are being missed. It starts
We're in the software developmental business and one of our customers reported
a problem when 100 WLM service classes were defined and active. We needed to
reproduce their environment to test a fix. Once I read the advice "don't do
it", I used one of our stand-alone z/OS system
: IBM-MAIN@LISTSERV.UA.EDU
Date: 16/02/2021 13:21
Subject:[EXTERNAL] Re: WLM Service Classes
Sent by:IBM Mainframe Discussion List
Mark,
IBM recommends < 30 Service Classes. WLM has a limited amount of time to
cycle through the WLM service classes, and if > 30 service cl
:
> Mark,
>
> IBM recommends < 30 Service Classes. WLM has a limited amount of time to
> cycle through the WLM service classes, and if > 30 service classes, IBM says
> WLM can't complete it in time.
>
> Jerry
>
> -Original Message-
>
> From:
Mark,
IBM recommends < 30 Service Classes. WLM has a limited amount of time to cycle
through the WLM service classes, and if > 30 service classes, IBM says WLM
can't complete it in time.
Jerry
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Mark Jacob
I seem to recall that there's a recommendation not to exceed a certain number
of defined WLM service classes for *reasons*. Is my recollection correct?
Mark Jacobs
Sent from [ProtonMail](https://protonmail.com), Swiss-based encrypted email.
GPG Public Key -
https://api.protonmail.ch/pks
