2. PERFORMANCE REPORTING ANALYSIS › 2.10 Product Measured Usage Analysis › 2.10.2 Usage Guidelines › 2.10.2.1 LPAR Product Resource Consumption
2.10.2.1 LPAR Product Resource Consumption
The LPAR Product Measured Usage query analyzes information in
the Measured Usage Global (BATMUG) file. It can help you
track resource consumption and produce a software inventory
by LPAR for any products reported with the SMF type 89 (Usage
Data) records. Resource consumption analysis for performance
or workload shifting is best done at the DAYS-or-DAYS-by-Hour
summarization level.
To produce a general software inventory, it is best to
execute the LPAR Product Measured Usage report against the
BATMUG file at the MONTHS timespan. This report will
summarize the entire month's product usage by LPAR by product
into a one-line-per-product-by-month report.
When generating software inventory for the purpose of
subcapacity pricing, the report should be run against the
DAYS timespan, producing a report summarizing product usage
by day by product. The problem with generating this report
for this purpose from the month's timespan is that your CA
MICS month's file will probably be defined from the first day
of one month to the last day of the next month. IBM defines
its billing cycle as the second day of one month to the first
day of the next month. Therefore, you will either be
including the first day of the prior month or excluding the
first day of the next month.
To help you understand what is in the BATMUG file, the four
CA MICS elements that make up a product follow in their key
file sequence order:
MUPROD - Product Name
MUVER - Product Version
MUPRODID - Product ID
MUQUAL - Product Qualifier
By default, the report presents product usage summarized at
the product ID level. Optionally, the report can be reported
at the product qualifier level. When reporting at the product
qualifier level you will see all instances of an individual
product's execution. For example, when reporting at the
product qualifier level, your report will show all instances
of IMS/ESA V9R1 batch and started tasks. Conversely, when
reporting at the product ID level, all IMS/ESA V9R1 usage
will be summarized to the product ID level.
The the input data can be subset by specifying a vendor in
the Data Selection section of the query composition panel.
For example, if you only wanted to report on product supplied
by IBM, you would type 'IBM CORP' in the Vendor field. The
data will then be subset prior to reporting.
To further subset the input data beyond the data selection
options available on the query composition panel, you can
specify a global data selection exit by coding a SELECT macro
under the Extended Options panel. If you enter Y (Yes) in
the Specify global data selection exit field, the Global Data
Selection Panel, which is shown in Figure 2-227, is
displayed. This panel allows you to enter SAS statements that
will perform special data selection functions.
The SELECT MACRO can be used for special selection code based
on any data element in the BATMUG file. A typical use may be
to limit data analysis by excluding a specific product from
analysis. The following example will exclude all releases of
z/OS from the analysis.
/-------------------------------- SAS Statements -------------------------------\
| Command ===> Scroll ===> CSR |
| |
| Inquiry Step: Combined Hourly System Usage Analysis |
| |
| Line Cmds: I Insert D Delete R Repeat M Move C Copy |
| |
| Cmd SAS Statements for: Specifying global data selection |
| - ------------------------------------------------------------------------ |
| _ - %MACRO SELECT; |
| _ IF MUPROD NE 'z/OS'; ___________________________________________________ |
| _ ________________________________________________________________________ |
| _ - %MEND SELECT; |
| ****************************** BOTTOM OF DATA ******************************** |
| |
\---------------------------------------------------------------------------------/
Figure 2-227. Global Data Selection Exit Panel
The generated report shows product consumption and maximum
product consumption in CPU time, service units (SUs), and
millions of service units (MSUs). It calculates a product's
MSU consumption rate based on observed activity.
The Product Measured Usage inquiry lets you analyze the
following items:
o Product Resource Consumption in CPU Time
o Product Resource Consumption in SUs
o Product Resource Consumption in MSUs
o Product Resource Consumption as an MSU Rate
