Neoview Workload Management Services Guide (R2.3)

If the total number of queries in WMS is less than or equal to the limit, WMS maps the query to
a service level.
WMS maps the query to a service level based on the attribute set by the NDCS server. If you set
a service for the client session or the query, WMS executes the query in that service. If you do
not set a service for the client session or query, WMS searches for a service name that matches
the second part of the client role, such as MGR from ROLE.MGR. If WMS does not find a service
name that matches the role, WMS maps the query to the default service, HP_DEFAULT_SERVICE.
See Figure 1-3 (page 19).
Figure 1-3 How WMS Maps a Service to a Query
After WMS maps the query to a service level, it checks that the average memory usage is less
than or equal to the threshold limit, MAX_MEM_USAGE, of the service. If the
MAX_MEM_USAGE was not set for the service, WMS checks the MAX_MEM_USAGE of the
WMS system configuration. If the MAX_MEM_USAGE was not set for the WMS system
configuration, WMS checks the internal default threshold for MAX_MEM_USAGE, which is 85%
. If the average memory usage exceeds the MAX_MEM_USAGE, WMS puts the query in the
waiting queue.
If the average memory usage is less than or equal to the MAX_MEM_USAGE, WMS checks that
the average CPU busy is less than or equal to the threshold limit, MAX_CPU_BUSY, of the service.
If the MAX_CPU_BUSY was not set for the service, WMS checks the MAX_CPU_BUSY of the
WMS system configuration. If the MAX_CPU_BUSY was not set for the WMS system configuration
, WMS checks the internal default threshold for MAX_CPU_BUSY, which is 100%. If the average
CPU busy exceeds the MAX_CPU_BUSY, WMS puts the query in the waiting queue.
WMS continues to check the queries in the waiting queue to see if they can execute given the
current system resources (memory usage and CPU busy). As soon as resources become available,
WMS starts executing the queries associated with higher priority services in the waiting queue.
For information about how the priority of a service influences the execution of queries in that
service, see “How Service Priorities and System Resource Thresholds Work” (page 25).
If the average memory usage and CPU busy are under the resource threshold limits, WMS checks
that the service assigned to the query is in the active state. The active state is influenced by the
active time of the service or by the HOLD command. For example, if the active time of a service
is between the hours of 22:00 and 23:59, the service is inactive (that is, on hold) any time outside
of 22:00 and 23:59. Even if the current time is within the active time of the service, a user can put
the service on hold by issuing the HOLD command. For more information, see the “HOLD
Command” (page 63). If the service assigned to the query is inactive (that is, on hold), WMS
rejects the request to execute the query and returns an error message to the application. If the
service is active, WMS allows the query to start executing.
How WMS Works 19