Matching CICS performance parameters to service policies

You must ensure that the CICS® performance parameters are compatible with the Workload Manager service policies used for the CICS workload.

In general, you should define CICS performance objectives to the z/OS® Workload Manager first, and observe the effect on CICS performance. Once the z/OS Workload Manager definitions are working correctly, you can then consider tuning the CICS parameters to further enhance CICS performance. However, you should use CICS performance parameters as little as possible.

Performance attributes that you might consider using are:

Transaction priority, passed on dynamic transaction routing.
You should take care when choosing the priority to assign to each transaction. Although you can specify transaction priorities from 1 to 255, you should avoid using a large number of closely spaced values. You will get as much benefit if you use a small number of widely spaced values.

The priority assigned by the CICS dispatcher must be compatible with the performance parameters defined to the z/OS Workload Manager.
Maximum number of concurrent user tasks for the CICS region.
Maximum number of concurrent tasks in each transaction class.
Maximum number of sessions between CICS regions.