Defining service classes
Service classes are categories of work, within a workload, to which you can assign performance goals.
- Performance
goals You can assign the following performance goals to the service classes:
- Response time
- You can define an average response time (the amount of time required to complete the work) or a response time with percentile (a percentage of work to be completed in the specified amount of time).
- Discretionary
- You can specify that the goal is discretionary for any work for which you do not have specific goals.
- Velocity
- For work not related to transactions, such as batch jobs and started tasks. For CICS® regions started as started tasks, a velocity goal applies only during start-up.
Note:- For service classes for CICS transactions, you cannot define velocity performance goals, discretionary goals, or multiple performance periods.
- For service classes for CICS regions, you cannot define multiple performance periods.
- Business importance to the installation
You can assign an importance to a service class, so that one service class goal is recognized as more important than other service class goals. There are five levels of importance, numbered, from highest to lowest, 1 to 5.
You can also create service classes for started tasks and JES, and can assign resource groups to those service classes. You can use such service classes to manage the workload associated with CICS as it starts up, but before CICS transaction-related work begins. (Note that when you define CICS in this way, the address space name is specified as TN, for the task or JES “transaction” name.)
There is a default service class, called SYSOTHER. It is used for CICS transactions for which z/OS® workload management cannot find a matching service class in the classification rules—for example, if the couple data set becomes unavailable.
- Do not mix CICS-supplied transactions with user transactions
- Do not mix routed with non-routed transactions
- Do not mix conversational with pseudo-conversational transactions
- Do not mix long-running and short-running transactions.