Performance goals for CICS regions

You can define performance goals, such as response times, for CICS® (and other z/OS® subsystems that comprise your workload).

You can define goals for:
  • Individual CICS regions
  • Groups of transactions running under CICS
  • Individual transactions running under CICS
  • Transactions associated with individual userids
  • Transactions associated with individual LU names.

To define the performance goals for CICS regions, allocate each CICS job a service class and then specify target response times for the service class. Typically, production regions and test regions are placed in different service classes, because response times for production regions are more critical than for test regions.

Workload management also collects performance and delay data, which can be used by reporting and monitoring products, such as the Resource Measurement Facility™ (RMF™), Tivoli® Decision Support for z/OS, or vendor products.

The service level administrator defines your installation's performance goals, and monitoring data, based on business needs and current performance. The complete definition of workloads and performance goals is called a service definition. You may already have this kind of information in a service level agreement (SLA).



dfht30z.html | Timestamp icon Last updated: Monday, 5 June 2017