The following table summarizes the effects of the storage protection, CPU protection, and exemption from transaction response time management options:
| When you... | WLM... |
|---|---|
| Assign CPU protection to a service class used to manage address spaces and/or enclaves. | Protects any address space or enclave managed according to the goals of that service class. Address spaces being managed as servers are managed according to the goals of the served transactions. |
| Assign storage protection to an ASCH, JES, OMVS, STC, or TSO address space. | Protects any address space which matches the classification rule, regardless of its server status. Address spaces currently running in multiperiod service classes or in service classes with a short response time goal (20 seconds or less) are excluded from protection. |
| Assign CPU or storage protection to a CICS® or IMS™ transaction. | Protects any regions recognized as serving that CICS/IMS transaction, unless you prevent WLM from managing the regions as servers. Note that once storage protection is assigned to any transaction in a service class, then all transactions in the same service class become storage protected. |
| Manage a CICS or IMS region using the goals of the region. | Is prevented from managing the region according to the response time goals of the transactions it is running. It does not recognize the region as a server. The region is managed using the goal of the service class assigned to the region. Transaction response time data is not reported in the service classes to which the transactions are classified, but is still reported in their report classes, if assigned. |
| Manage a CICS or IMS region using the goals of both region and transaction. | Manages the region using the goal of the service class assigned to the region. This also ensures that the region tracks all transaction completions correctly so that it can still manage the CICS service classes with response time goals. The option should only be used for CICS TORs. All AORs should remain at the default (TRANSACTION). In addition, the service class for the CICS TORs should be defined with a higher importance than the the service class for the CICS transactions. |
| Issue the RESET QUIESCE command. | Will no longer enforce CPU protection. All other options remain unchanged. |
| Issue the RESET SRVCLASS or RESET RESUME command. | Will assign CPU protection if the target service class has the CPU protection attribute. All other options remain unchanged. |