Neoview Workload Management Services Guide (R2.3)

• PRIORITY MEDIUM-HIGH
• PRIORITY MEDIUM
• PRIORITY LOW-MEDIUM
• PRIORITY LOW
If you do not specify a priority for the service, the default priority is medium.
Setting the System Resource Thresholds of the Service
You can set these system resource thresholds for the service:
• MAX_CPU_BUSY, which is a percentage from zero to 100 of the total CPU busy allowed
for the service. This value is an average of CPU busy across all segments in the cluster.
• MAX_MEM_USAGE, which is a percentage from zero to 100 of memory usage allowed for
the service. This value is an average of memory usage across all segments in the cluster.
If you do not set system resource thresholds for the service, WMS uses the system resource
thresholds of the WMS system configuration. If you do not set the system resource thresholds
of the WMS system configuration, WMS uses these internal default thresholds:
• 100% for MAX_CPU_BUSY
• 85% for MAX_MEM_USAGE
Setting the Active Time of the Service
The active time of a service is a time range when the service can execute queries. Outside the
active time range, a service cannot execute incoming queries associated with the service. If a
query is still executing in the service when the end time is reached, WMS allows the query to
continue executing outside the active time range. However, WMS rejects any new incoming
queries associated with the service if they occur outside the active time range.
By default, the active time is from 00:00 through 23:59. To change the active time, specify the
start and end times during which you want the service to execute queries. The start or end time,
hh:mm, is in hours (hh) and minutes (mm). Currently, the active time cannot span more than one
day.
For example, if you specify an active time of 15:00 to 18:00, WMS enables queries associated with
the service to start executing between the hours of 15:00 to 18:00. WMS rejects any queries
associated with the service that try to execute outside the active time of 15:00 to 18:00.
Setting the Execution and Waiting Timeouts of the Service
You can set a timeout value, EXEC_TIMEOUT, for executing queries in the service. The timeout
value can be from zero to 1440 minutes. When the timeout value is reached, WMS cancels the
executing query and stops that NDCS server. If you do not specify an EXEC_TIMEOUT value,
the default is zero, meaning no timeout is in effect.
CAUTION: Do not set an EXEC_TIMEOUT value for a service that handles long-running inserts
or updates of the database.
You can also set a timeout value, WAIT_TIMEOUT, for the waiting queries in the service. The
timeout value can be from zero to 1440 minutes. When the timeout value is reached, WMS cancels
the waiting query and returns an error message. If you do not specify a WAIT_TIMEOUT value,
the default is zero, meaning no timeout is in effect.
Setting the Output Options of the Service
Specify the PLAN option to collect the execution plan of queries executing in the service. Client
tools, such as NCI and the Neoview Manageability Repository, can then use and display this
data. If you do not specify PLAN, WMS does not collect any plans for the service (that is,
NO_PLAN) .
30 Configuring WMS