Multiple servants

With workload management (WLM), you can control the number of servants that are running and how they are performing. WLM manages the response time and throughput of transactions according to their assigned service class, the associated performance objectives, and the availability of system resources. To meet these goals, WLM sometimes needs to control or override the number of servants that are active.

Product applications are deployed within a generic server. One or more server instances must be defined on one or more systems within a node. Each server instance consists of a controller and one or more servants. The controllers are started by MVS™ as started tasks, and servants are started by WLM, as they are needed.

WLM dynamic application environments can be enabled on your z/OS® system if you are running on z/OS Release 2, with the service update for APAR OW54622 installed, or if you are running on a higher level of z/OS. If you have WLM dynamic application environments enabled on your system, WLM honors the specifications for the number of servants. If you are using static application environments, which is a setting that is specified through the WLM ISPF panels, then you must also enable multiple servants by indicating No limit in the WLM ISPF panels.

Avoid trouble: If you use multiple servants, remember that: gotcha



Related tasks
Controlling the minimum and maximum number of servants
Using transaction classes to classify workload for WLM
Enabling multiple servants on z/OS®
Concept topic    

Terms of Use | Feedback

Last updated: Oct 22, 2010 12:21:29 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-zos&topic=crun_servants
File name: crun_servants.html