A service class identifies a block of related transactions that share common response-time goals for a single workload; the transactions must be related by transaction name, the user ID that invoked them, the VTAM terminal ID (LU name) that submitted them, the CICS region running them, or any combination thereof. Defining new service classes, associating them with a workload, and setting their response-time goals usually compose the second step when implementing the SLA support within OMEGAMON XE for CICS on z/OS. To define a new service class complete the following tasks:
The Define new Service Class window is displayed.
OMEGAMON XE for CICS on z/OS provides 31 default service classes (ATRANS through ZTRANS, CSM1, CSM2, CSM3, CSM5, and CSMI). Service classes ATRANS through ZTRANS cover transactions based on the first character of the transaction name. Service classes CSM1, CSM2, CSM3, CSM5, and CSMI cover the transactions with those names.
You can also change an existing service class's associated workload or its response-time settings:
The Edit Service Class—Base Goal window opens again, and shows the name of the selected service class, the workload it is currently associated with, and its Response Time and Goal areas:
After you have created a service class, you must identify the CICS transactions, userIDs, LU names, and CICS regions associated with it; continue with Editing a service class's classification rules.