Service policies for batch jobs

Batch support provides a rule-based service policy methodology and a completion time service policy goal type. It enhances workload management for batch because batch jobs and OLTP workloads can mix in the same product installation.

We must have batch installed to define service policies. See topics about dynamic operations.

Service policy classification is controlled by a set of rules defined to the job scheduler. These rules can be composed of Boolean expressions and can include the following operand types:

• Submitter identity

• Submitter group

• Job name

• Job class

• Application name

• Application type

• Platform

• Time

See Batch job classification for details on the operand types.

Goals types

• Discretionary goals indicate work that does not have significant value. As a result, work of this type can see a degradation in performance when resources are constrained.

• Average response time goals are indicative of work with a higher priority than discretionary. The average response time goal is assigned a specific time goal.

• Percentile response time goals are another measure for work with a higher priority than discretionary. The percentile response goals are defined with specific criteria. The percentile response time target is the percentage of requests whose response time is T or less that should be P or more. A target has particular values for T and P.

Default classification rules and precedence

Batch support provides two default classification rules:

1. A rule that assigns any job of type Java EE to the transaction class defined by default IIOP work class of the named Java EE application.

2. A rule that assigns any job to the default transaction class, DEFAULT_TC

Both default rules can be edited and deleted. The order of the rules can be modified, and user-defined classification can be added. The job scheduler evaluates the list of classification rules in order and assigns the transaction class specified by the first matching rule. Only one classification rule set for a cell is supported. A default configurable transaction class, named DEFAULT_TC by default, is associated with this set. If none of the classifications rules match a job, then the default transaction class is applied to that job. Graphical user interface (GUI) support for choosing a transaction class from a list while building a rule is only present when batch support is installed. When batch alone exists, there is a text field where a transaction class name is specified.

Related concepts

Batch jobs and their environment