|
|
|
The Sysplex Aggregation Compliance report provides, for every machine (CPC) analyzed, the average contribution of each z/OS logical partition to the Sysplexes' workload, over an expected 40 hours prime shift period. Based upon IBM's Parallel Sysplex Aggregation rules, the report also determines which Sysplex, if any, a machine belongs to. INTENDED USE: IBM's Parallel Sysplex Aggregation allows customers to receive software pricing benefits by adding together software licenses in a Parallel Sysplex in order to price them as a single entity. To qualify for aggregation, a Sysplex must meet all IBM's criteria in the hardware, software, and operational categories. The Sysplex Aggregation Compliance report is intended to help you assess whether your machines meet the Parallel Sysplex Aggregation 50% operational criterion: on a given machine, the images participating in the Parallel Sysplex must account for at least 50% of the workload on the machine in order to belong to this Sysplex. This report is designed to enable you to analyze your Sysplex environment for compliance with the LPAR usage criterion of IBM's Parallel Sysplex Aggregation rules. It assumes but does not verify your compliance with the other criteria for aggregation. Use of the Sysplex Aggregation Compliance report is not designed to arrive at a conclusive determination of your eligibility for Parallel Sysplex Aggregation. This determination may only be made by IBM. REPORT FORMAT: This inquiry produces a single page table for each reported period of 40 hours from 5 consecutive business days.
S Y S P L E X A G G R E G A T I O N C O M P L I A N C E R E P O R T Page 001 Customer Name : XYZ Corp. Reporting Period: 19NOV07:09:00 - 23NOV07:17:00 Machine: CPC1 Serial: p0963 MSUs Rating: 742 Model: 2094-S28(712) Logical Partitions ------------------ LPAR Operating System Contribution Name Sysid System Name Sysplex Pct MSUs Notes (may affect reporting accuracy) -------- ----- ------------ -------- -------- ------ ------ --------------------------------------------------- CF01 No data for this LPAR was provided. ZOS1 ZOS1 z/OS 1.8 ZOS1 PLEXC1 31.2% 88 0h55 of data missing out of the 40h00 expected. ZOS2 No data for this LPAR was provided. ZOS3 ZOS3 z/OS 1.8 ZOS3 PLEXC1 51.0% 143 VM01 No data for this LPAR was provided. ZPR1 ZPR1 z/OS 1.8 ZPR1 PLEXC1 12.8% 36 ZQA1 ZQA1 z/OS 1.8 ZQA1 PLEXC1 5.0% 14 Based on the above information, the Primary Sysplex for CPC1 is: PLEXC1 ========================================================================= Machine: CPC2 Serial: p6193 MSUs Rating: 247 Model: 2064-1C7 Logical Partitions ------------------ LPAR Operating System Contribution Name Sysid System Name Sysplex Pct MSUs Notes (may affect reporting accuracy) -------- ----- ------------ -------- -------- ------ ------ --------------------------------------------------- DRP1 No data for this LPAR was provided. XAZ1 XAZ1 z/OS 1.8 XAZ1 PLEXD1 27.2% 35 XAZ2 XAZ2 z/OS 1.8 XAZ2 PLEXP1 61.2% 79 XAZ3 XAZ3 z/OS 1.8 XAZ3 PLEXD1 11.6% 15 Based on the above information, the Primary Sysplex for CPC2 is: PLEXP1 =========================================================================
Figure 3-25. Sysplex Aggregation Compliance report
FIELDS DESCRIPTION
The report is broken in to four sections in the following
order: header, machine overview, LPAR summary, and
conclusion. The general layout of the report is:
+-- Header (describes the reporting period)
!
! +-- Machine 1 overview (general characteristics of CPC1)
! !
! ! +-- LPAR summary (list all LPARs' contribution)
! ! ! ...
! ! ! ...
! ! +-- ...
! !
! +-- Conclusion (primary Sysplex determination for CPC1)
!
! +-- Machine 2 overview (general characteristics of CPC2)
! !
! ! +-- LPAR summary
! ! ! ...
! ! ! ...
! ! +-- ...
! !
! +-- Conclusion (primary Sysplex determination for CPC2)
+--
Each section is explained below:
Header section
--------------
Customer Name: The name of the customer as specified in the
MICF execution panel.
Reporting Period: The starting and ending times of the prime
shift. This field can be used to control if the information
stored in the CA MICS database covers the expected amount of
data, representing 40 hours from 5 consecutive business days.
We will use the following week as a reference for all
examples listed in this section:
Mon, November 19, 2007
Tue, November 20, 2007
Wed, November 21, 2007
Thu, November 22, 2007
Fri, November 23, 2007
Sat, November 24, 2007
Sun, November 25, 2007
By default, the prime shift is 9am-5pm, Monday through
Friday. This would show up as the following reporting
period:
19NOV07:09:00 - 23NOV07:17:00
When the Sysplex Aggregation Compliance report is executed
using the DETAIL or DAYS timespans, the default reporting
period can be altered in three ways:
1) Modify the prime shift starting day: Any day of the
week can be chosen as the starting day of the period.
The reporting program will automatically extend the
input data selection for 5 days from the starting day.
For example, if your prime shift starts on Wednesdays,
the reporting period will be 9am-5pm, Wednesday through
Sunday:
21NOV07:09:00 - 25NOV07:17:00
2) Modify the prime shift starting hour: Any hour of the
day can be chosen as the starting hour of the period
(this can be combined with a modified starting day as
described above). The reporting program will
automatically extend the input data selection for 8
hours from this time. For example, if your prime shift
starts at 8am, the reporting period will be 8am-4pm,
Monday through Friday:
19NOV07:08:00 - 23NOV07:16:00
3) Exclude lunch time hours: Up to two consecutive hours
may be excluded from the input data. This can be useful
if you do not want to consider lunch time utilization as
being part of your prime shift pattern. The reporting
program will automatically extend the input data
selection for 8 hours from the starting hour and exclude
the lunch time interval. For example, using the default
prime shift, if you want to remove two lunch hours
(12am-2pm), the reporting period will be 9am-12am and
2pm-7pm, Monday through Friday, and the excluded hours
will be displayed:
19NOV07:09:00 - 23NOV07:19:00
(Lunch Time Excluded: 12:00-13:59)
When the Sysplex Aggregation Compliance report is executed
using the WEEKS timespan, you must supply the CA MICS zones
that represent your prime shift. You can also use zone
selection with the DETAIL or DAYS timespans, but this is
mutually exclusive with the prime shift specifications
described above. Therefore, you should carefully review your
CA MICS parameters in order to supply the correct zones to
the program. Although no verification is performed against
the zone setup, an additional note will be displayed next to
the reporting period field:
19NOV07:09:00 - 23NOV07:17:00 (CA MICS zone selected: 1)
Machine overview section
------------------------
Machine: An arbitrary designation of the machine in the form
CPCn where n is incremented by one each time a different
machine is found within the reporting period.
Serial: The unique serial number of the machine in the form
"pnnnn" where nnnn are the last four digits of the processor
serial number.
MSUs Rating: The software MSU rating for the machine being
analyzed.
If a master LPAR (for example PRD1) has been specified for
this machine on the MICF execution panel, a note will
immediately follow the machine specifications:
NOTE: All LPAR timestamps have been adjusted to the
specified master LPAR, PRD1.
LPAR summary section
--------------------
This section provides a table containing the information for
all the active logical partitions in the machine that are
using general purpose processors. The Sysplex calculations
can only be performed for LPARs that produced SMF type 70
subtype 1 records.
If the program detects that no SMF records exist for an LPAR,
all columns will be empty, and a note will be displayed.
Otherwise the following information is provided for each
LPAR:
LPAR Name: The name of the logical partition.
Sysid: The SYSID name for the instance of z/OS running in
the logical partition.
Operating System: The O/S and level of the logical partition.
System Name: The system name for the instance of z/OS
running in the logical partition.
Sysplex: The Parallel Sysplex name for the logical
partition.
Contribution Pct: The average utilization contribution (in
%) of the LPAR's workload, as a percentage of workload on the
machine over the reporting period. zAAP/zIIP special
processors are included in the calculations.
Contribution MSUs: The average utilization contribution (in
MSUs) of the LPAR's workload, over the reporting period.
zAAP/zIIP special processors are included in the
calculations.
Notes: For each logical partition, various notes may appear
in this column. This is an indication that the report
accuracy may be affected. These notes can be one of the
following:
"No data for this LPAR was provided": The data covered by
the reporting period does not contain any information for
this logical partition (originally no SMF type 70 subtype 1
record). This is not necessarily a problem if this LPAR is
not a z/OS system (for example VM, coupling facility).
But, if it is a z/OS system, its potential contribution to
a Sysplex activity cannot be assessed.
"HHhMM of data missing out of the 40h00 expected": The
data for the logical partition is incomplete. If the same
amount of data is missing for all LPARs, one reason may be
that the reporting period does not cover a full prime
shift.
Conclusion section
------------------
This section provides the primary Sysplex determination.
Based on the logical partitions' contributions to the various
sysplexes, the program displays the name of the sysplex the
machine belongs to. It is either the name of the Sysplex
that generates at least 50% of the workload of the machine,
or *NONE* if no Sysplex reaches the 50% limit.
A sysplex name means aggregation with other machines is
possible, *NONE* means the machine cannot aggregate.
DATA SOURCE (file/timespan):
HARCPU and HARLPC at the DETAIL, DAYS, or WEEKS timespan.
DATA ELEMENTS USED AND CALCULATIONS:
Consult the SAS source code used to generate this report
in sharedprefix.MICS.SOURCE(@RMFSPX1).
HOW TO PRODUCE THE REPORT:
o Enter the CA MICS Workstation Facility (MWF).
o Choose option 2, CA MICS Information Center Facility
(MICF).
o Choose option 2, Database Inquiries.
o Select RMFLPU, whose Catalog Group is PERFORM.
o Complete the MICF Execution panel. (If you are not
familiar with MICF, see the MICF User Guide and the MICF
Reference Guide.)
o Complete the specification panel illustrated below.
(Descriptions of the fields follow the panel.)
+----------------------------------------------------------------------+ |------------ Sysplex Aggregation Compliance Report -----------------| | Command ===> | | | | Composing Inquiry: RMFLPU - Sysplex Aggregation Compliance Report | | Database ===> ___________ | | Cycle(s) ===> __ - __ | | Timespan ===> ______ (DETAIL/DAYS/WEEKS) | | | | Customer Name ===> ________________________________________ | | | | Prime Shift Selections: | | | | Starting Day ===> ___ - Hour ===> __ Lunch Hours ===> __ - __| | or | | CA MICS Zone ===> _ _ _ _ | | | | Master LPARs (CPC serial number last 4 digits followed by LPAR name):| | ===> ____ ________ - ____ ________ - ____ ________ - ____ ________| | ===> ____ ________ - ____ ________ - ____ ________ - ____ ________| | ===> ____ ________ - ____ ________ - ____ ________ - ____ ________| | ===> ____ ________ - ____ ________ - ____ ________ - ____ ________| | ===> ____ ________ - ____ ________ - ____ ________ - ____ ________| +----------------------------------------------------------------------+
Database - Required. No default.
Specify up to six database unit IDs (the IDs of the
CA MICS database units from which the files are read).
If CA MICS files exist in only one database unit, this
parameter is set automatically. To display a selection
list of valid database unit IDs, specify ? (question
mark).
Cycle(s) - Required. Defaults to 01.
Specify 00-99 in either data entry field; leading
zeros are inserted automatically. The CA MICS files
cycle (specify first field) or cycle range (specify
both fields) for the inquiry execution. It is
important, for the accuracy of the report, that enough
cycles be specified to cover IBM's view of the prime
shift (40 hours from 5 consecutive business days).
Customer Name - Required. No default.
Specify the customer name that will be displayed in
the header of the report.
The default reporting period is 9am to 5pm, Monday
through Friday (40 hours). If necessary, you can
specify a different range of days and/or hours to match
your own prime shift patterns. You can also exclude up
to 2 consecutive hours per day if you do not want to
consider lunch time utilization. This facility is only
available with the DETAIL and DAYS timespans, when no CA
MICS zone is specified. If the WEEKS timespan is used
or if CA MICS zones are selected, these zones are
expected to represent your complete prime shift.
Starting Day - Optional. Defaults to MON. MON-SUN.
Specify the starting day of your prime shift. Valid
with DETAIL and DAYS only.
Starting Hour - Optional. Defaults to 09. 00-23.
Specify the starting hour of your prime shift. Valid
with DETAIL and DAYS only.
Lunch Hours - Optional. No default. 00-23.
Specify up to two consecutive hours to exclude from
the report. Valid with DETAIL and DAYS only.
CA MICS Zone - Required with WEEKS, otherwise optional.
No default. 1-9.
You can specify up to four zone values. An input
observation is selected if its zone value is equal to
any of the specified values. Because this parameter
is mutually exclusive with the other prime shift
specifications, it is expected that the selected
period represents your entire prime time (40 hours
from 5 consecutive business days). Otherwise, the
report may draw incorrect conclusions.
Master LPARs - Optional. No default. CPC serial number
last 4 digits followed by LPAR name.
You can specify which LPAR (for up to 20 machines)
represents local time in the event that different
LPARs are running in different time zones. All other
LPARs' timestamps will be adjusted to match the
master. If no LPAR is explicitly specified, the most
contributing one will be considered as the master.
USAGE CONSIDERATIONS:
This inquiry provides a user exit that you can use to perform
additional data selection from the CA MICS database. To
invoke this exit, you must first copy the shared inquiry into
your private MICF catalog, then select it for modification.
Finally code SAS statements in the SELECT macro, bracketed by
the %MACRO and %MEND statements.
The default for the SELECT macro is null. This macro is
invoked when the observations are read from the specified
CA MICS file(s). You can use it to delete observations from
the data as it is selected. For example, in a system
activity study, you might want to exclude test systems
starting with a T from the analysis. You would then code
the following:
%MACRO SELECT;
IF SYSID NE: 'T';
%MEND SELECT;
Note that you do not have to code the %MACRO and %MEND
statements, as they are already provided for you.
IMPORTANT: You must code each specified SAS statement in
accordance with the syntax of the SAS Macro Language, as
described in the SAS manuals. No validity checking is done
on the defined code. If the user code contains syntax or
logic errors, the inquiry will either terminate abnormally or
will produce unpredictable results.
************************************************************
** Note: This report cannot be produced if the CA MICS **
** database contains essential data elements only.**
************************************************************
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |