z/OS Workload Manager: region and transaction goals

z/OS® Workload Manager can manage CICS® work toward a region goal or a transaction response time goal. You can choose which goal is used.

When you choose to manage toward a region goal, z/OS Workload Manager uses the goal for the service class that is assigned to the CICS address space under the JES or STC classification rules. When you choose to manage towards a transaction goal, z/OS Workload Manager uses the goals for the service classes that are assigned to transactions or groups of transactions under the CICS subsystem classification rules. You can select which mode to use when you are working with the JES or STC classification rules.

When you manage towards a transaction goal, z/OS Workload Manager does not directly manage resource allocations for the transactions. Instead, it makes calculations to assign appropriate resources to the CICS regions that can run the transactions. This can work less well if regions have a diverse mix of transactions and response time goals. In this situation, managing toward a region goal might work better.

Sometimes, the processing for a single work request requires more than one transaction in the CICS region. For example, up to four transactions, with different transaction identifiers, might be needed to process an inbound SOAP request in a CICS provider region. Take this into account when you decide whether to use a transaction goal or a region goal.

You can optionally use RMF™ to report on transaction response times, but still manage the CICS work at the region level. This is documented in the IBM® Redbooks® publication System Programmer's Guide to: Workload Manager SG24-6472 in the section titled “11.5 Reporting”.



zwlm_reg_and_tran_goals.html | Timestamp icon Last updated: Sunday, 4 June 2017