Service Level Reporting

You can use the Service Level Reporting (SLR) feature to define performance goals for your subsystem and batch applications and then measure the actual performance of those applications.

You define four groups of transactions for each application subtypes:

  • CICS
  • Db2
  • IMS
  • MQ
  • Batch

Related topics

Getting-started

UIE-concepts

Each group is defined by the amount of CPU and I/O resources that are consumed by the transactions or jobs that match that application definition.

You also define target goals for each group, which represent the percentage of the transactions or jobs in an application that should have a response time below a specified response time goal. The actual performance of your applications is evaluated against the target goals. The results are written to a Visualizer file, which you can view using Visualizer SLR graphs.

Using the SLRPARMS command, you must first define default values for each application subtype for which you want to measure SLR performance—BATCH, CICS, Db2, IMS, and MQ. After you have established subsystem type defaults, you can override the default values for response time goal and percentage of transactions for a specific application by specifying additional SLR parameters on the APPL command. You cannot override the CPU and I/O limits, which define groups for different application types.

For additional information about defining SLR parameters, see SLRPARMS and APPL.

Important

During SLR processing, to match a subsystem transaction to an SLR group, UIE must convert a transaction's number of CPU seconds to the number of MIPS, using the MIPS rating of the logical system on which the transaction executes. The MIPS rating of a logical system is obtained from data in the type 70 record or by looking up the logical system CPU type in the BMC Hardware table. If the subsystem data (CICS, Db2, IMS, or MQ) is processed before a type 70 record is read, the MIPS rating of the logical system might be unknown. In this case, the subsystem transaction cannot be matched to an SLR group. To correct this situation, you might need to specify a PSYS command for each logical system that requires SLR reporting. The PSYS command should include the CPUTYPE parameter.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*