Skip to Content

UIE SUITES

BMC Performance Predictor for Mainframes enables you to model activity in your datacenter on the level of Service Class (SC) periods.

However, at times, you might find that your business applications cannot be defined in terms of Service Classes. Jobs and started tasks belonging to different applications can be running in the same Service Class. Transactional subsystems like CICS, IMS, Db2, MQ can handle transactions simultaneously from different applications.

Universal Information Exchange (UIE) enables you to model your business applications on a much more detailed level. Using UIE, you can isolate individual jobs, started tasks, or TSO sessions, and group them together into objects called SUITES. You can create models using these objects instead of using Service Classes.

Related topic

Getting-started

If you include additional information about transactional subsystems (SMF type 110, TMON for CICS or BMC AMI Ops Monitor for CICS records, BMC AMI Ops Monitor for IMS Offline, SMF type 100 and 101 for Db2, SMF type 115 and 116 for MQ, SMF 120 for WAS), UIE can process transactional data, trace them into jobs and started tasks, combine them into applications and determine what part of computing resources (that is, CPU, DASD, or Tapes) was used by each application.

Adding this information into the model gives you an opportunity to model effects of hardware upgrades on your applications and effects of application growth on your hardware usage.

At the same time as Universal Information Exchange is collecting information about Service Classes, UIE also gathers and processes information about individual executing tasks (that is, jobs, started tasks, TSO sessions, and so on).

All the tasks executing in the enterprise are combined into groups called SUITES. You obtain information about SUITES from type 30 and type 42/6 SMF records. Although you can get some information about SUITES from 30/4 and 30/5 records, most of the information comes from 30/2 and 30/3 records (interval type 30 records).

Therefore, enabling interval SMF recording is very important for all types of tasks on all z/OS systems in the enterprise. UIE does not process any information for the tasks that do not have any type 30/2 or 30/3 records. The activity for these tasks is not accounted for in the BMC Performance Predictor for Mainframes model or in the Visualizer file.

The SUITE command controls the grouping of tasks into SUITES. See SUITE.

If you do not specify any SUITE commands, tasks are assigned to SUITES based on the default rules. The same default rules also apply to the tasks that did not match any specified SUITE command.

You can change some of the default rules using the SEPARATESUBSYS command as described in Default-SUITE-assignment-rules.

Default rules for SUITE grouping and the functionality of SUITE commands are designed to provide the following capabilities:

  • You do not need to specify multiple commands to generate information, which is sufficiently detailed, and at the same time, not too voluminous.
  • Provide you with an option to specify only those types of subsystems that interest you.
  • Provide a detailed representation for the important tasks, while combining all unimportant tasks together and representing them with a few workloads in UIE output.


 

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

Universal Information Exchange 2.2