Workload management DDL statements consist of the CREATE,
ALTER, and DROP statements that you use to work with service classes,
workloads, work class sets, work action sets, thresholds, and histograms.
The DB2® workload
management DDL statements are as follows:
- CREATE SERVICE CLASS, ALTER SERVICE CLASS, and DROP SERVICE CLASS
- CREATE WORKLOAD, ALTER WORKLOAD, and DROP WORKLOAD
- GRANT USAGE ON WORKLOAD and REVOKE USAGE ON WORKLOAD
- CREATE THRESHOLD, ALTER THRESHOLD, and DROP THRESHOLD
- CREATE WORK CLASS SET, ALTER WORK CLASS SET, and DROP WORK CLASS
SET
- CREATE WORK ACTION SET, ALTER WORK ACTION SET, and DROP WORK ACTION
SET
- CREATE HISTOGRAM TEMPLATE, ALTER HISTOGRAM TEMPLATE, and DROP
HISTOGRAM TEMPLATE
Workload management DDL statements differ from other DB2 DDL statements:
- Only one uncommitted workload management DDL statement is permitted
at a time across all database members. If an uncommitted workload
management DDL statement exists, subsequent workload management DDL
statements wait until the uncommitted workload management DDL statement
is either committed or rolled back. Workload management DDL statements
are processed in the order in which they are issued.
- Every workload management DDL statement must be followed by a
COMMIT or ROLLBACK statement.
- A workload management DDL statement cannot be issued in an XA
transaction. After a connection issues a workload management DDL statement,
the same connection must issue a COMMIT or ROLLBACK statement immediately
after the workload management DDL statement. With XA transactions,
it is possible for multiple connections to join a transaction, and
any of the connections can commit or roll back the transaction. In
this situation, it is impossible to ensure that the workload management
environment would be correctly implemented.
- DB2 for z/OS® does not recognize DB2 Database for Linux, UNIX, and Windows workload management DDL statements.
DB2 Version 10.1 for Linux, UNIX, and Windows