Neoview Workload Management Services Guide (R2.4)

Managing Queries
You can manage queries in WMS by using the HOLD, RELEASE, and CANCEL commands:
• “Holding a Query” (page 78)
• “Releasing a Query” (page 78)
• “Cancelling a Query” (page 79)
Holding a Query
Use the HOLD command to put an individual query, all queries, or all queries for a given service
on hold. The HOLD command either suspends an executing query or takes a waiting query out
of the waiting queue, thus allowing other queries in the waiting queue to proceed to the executing
state when system resources become available. You can put the query back into the executing
or waiting state by issuing a RELEASE command. For more information, see “Releasing a Query”
(page 78).
This HOLD command holds a specific query:
SQL>mode ns
NS%hold query MXID01002020782212110119447606071000000015509ROLE.USR200_498_S1
+>;
--- WMS operation complete.
NS%
For the syntax, see the “HOLD Command” (page 113).
This table shows how the HOLD command affects waiting and executing queries:
Table 5-1 Effect of the HOLD Command
ActionWMS Command
WMS puts the query on hold.HOLD when QUERY_STATE = WAITING
WMS suspends the query.HOLD when QUERY_STATE = EXECUTING
Use the STATUS QUERIES or STATUS QUERY command to display the QUERY_STATE column,
which shows the current state of a query. For more information, see the “STATUS QUERIES
Command” (page 127) or “STATUS QUERY Command” (page 136).
Releasing a Query
Use the RELEASE command to release an individual query that was put on hold, all holding
queries, or all holding queries for a given service. This RELEASE command releases a holding
query:
SQL>mode ns
NS%release query MXID01002020782212110119447606071000000015509ROLE.USR200_498_S1
+>;
--- WMS operation complete.
NS%
For the syntax, see the “RELEASE Command” (page 125).
This table shows how the RELEASE command affects holding queries:
78 Managing Workload