Neoview Workload Management Services Guide (R2.3)

Specify the TEXT option to collect the SQL syntax 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 TEXT, WMS does not collect any SQL text for the service (that is NO_TEXT).
Adding a Comment for the Service
You can optionally provide text to describe the service that you are creating. For example, to
describe a service intended for data loading, you might specify:
"dataloading service"
You must delimit the comment in double quotes. For details about the syntax, see “ADD SERVICE
Command” (page 56).
Example of Adding a Service
For example, in NCI, this ADD SERVICE command adds the DATALOADING service to the
WMS configuration, gives the service high priority, and sets the active period of queries to 20:00
to 23:00:
NS%add service dataloading priority high, active 20:00 to 23:00;
--- WMS operation complete.
NS%
For the syntax, see the “ADD SERVICE Command” (page 56). You can also execute the ADD
SERVICE command in JDBC and ODBC client applications. For more information, see “How to
Execute WMS Commands in NCI” (page 55).
Altering a Service
Use the ALTER SERVICE command to alter the setting of a service. For example, in NCI, this
ALTER SERVICE command changes the priority and active time of the DATALOADING service
in the WMS configuration:
NS%alter service dataloading priority medium-high, active 22:00 to 23:59;
--- WMS operation complete.
NS%
For the syntax, see the “ALTER SERVICE Command” (page 58). You can also execute the ALTER
SERVICE command in JDBC and ODBC client applications. For more information, see “How to
Execute WMS Commands in NCI” (page 55).
How an Altered Service Affects Queries
Whenever you alter a service, it is recommended that you do so when few or no queries associated
with that service are running on the Neoview platform. In case you alter a service when queries
associated with that service are being issued, be aware of these consequences.
New values of the maximum CPU busy and maximum memory usage do not affect the currently
executing queries associated with the service. However, new values of the maximum CPU busy
and maximum memory usage affect waiting queries and new incoming queries associated with
the service. When the new maximum CPU busy and memory usage are less than the previous
values of the service, the lower thresholds cause waiting queries associated with the service to
stay in the waiting queue longer until resources become available. When the new maximum
CPU busy and memory usage are greater than the previous values of the service, the higher
thresholds cause waiting queries associated with the service to start executing sooner than they
would have at lower thresholds.
Changing the priority or active time of the service does not affect the currently executing queries
associated with the service. However, the new priority or active time does affect waiting queries
and any new incoming queries associated with the service.
Configuring User-Defined Services 31