OA35428 - WLM goal of BOTH
When internal CICS queue contention increases on such systems and the CICS TORs and AORs are being managed to the goals
of the transactions, WLM currently has no way to give the work managers, the CICS TORs,
faster access to resources than the work consumers, the CICS AORs. At higher utilization levels, typically above 85%,
a noticeable queue delay within the CICS TORs might be recognized. This reduces end-to-end response time of the CICS
transactions and throughput of the CICS work. These symptoms become more visible in a HIPERDISPATCH=YES environment.
This 'problem' manifested itself in a customer environment when they tried to tighten down the CICS response time goals. The AORs were using a response time goal while the TORs were being managed by a velocity goal. When the AOR response times were lowered to represent the business needs, the transactions being dispatched from the TORs saw elongated response times. Logically it makes sense as there was no response time goal to aim at, so as the more resource intensive AOR workload used processing cycles the TOR transactions suffered. A new key word of BOTH has been added to 'Manage Region Using Goals Of' options.
The guidelines include .....
The new option BOTH should be used for CICS TORs only. All
CICS AORs should remain at the default TRANSACTION. In
addition, the started task or JES service class for CICS TORs
should be defined with a higher importance than the response
time service classes for the CICS transactions. This enables
WLM to give CICS TORs fast access to resources, especially
CPU, while it can still manage the larger part of the CICS
workloads running in the AORs towards response time goals.