Writer instructions | |
---|---|
Page title | For most spaces, this page must be titled Space announcements. For spaces with localized content, this page must be titled Space announcements l10n. |
Purpose | Provide an announcement banner on every page of your space. |
Location | Move this page outside of your home branch. |
Guidelines |
Cost Management workloads
BMC AMI Cost Management
provides you the opportunity to analyze the work that affects software cost not only at the individual LPARs level, but also on the level of individual jobs, started tasks, and address spaces aggregated into objects called workloads.
Cost Management provides the following different methods of aggregation:
- Importance
- Service Class name
- Report Class
- WLM Workload name in WLM Policy
- Suite
- Subsystem Address Space (IBM CICS, IBM IMS, IBM Db2, and so on)
Each workload type always corresponds to the total activity in the LPAR. So, different types of workloads always represent, from different perspectives, the same total work performed in an LPAR. This information is derived from RMF and SMF measurement data using proprietary BMC algorithms.
The following table describes each workload type:
Workload type | Description |
---|---|
Importance | Activity is aggregated using Service Class Period Importance from the WLM Policy |
Service Class name | Activity is aggregated by Service Class. |
Report Class | Activity is aggregated by Report Class |
Suites | Suites are user-defined groups of jobs and STC |
WLM Workload name in WLM Policy | Activity is aggregated according to the workload name in the Workload Manager (WLM) policy |
Subsystem address space | Subsystem address space type activity is aggregated by Subsystem Address Types (CICS, CICSUTL, Db2, DB2UTL, IMS, IMSUTL, IRLM, OMVS, MQSeries, WAS) All other activity is aggregated into workload OTHER_WORK. |
Related topic