2. SAMPLE PLANNING APPLICATIONS › 2.2 WLM Workload Planning › 2.2.2 Control Parameters
2.2.2 Control Parameters
Relatively few parameters are needed to implement the Goal
Mode Planning Sample Application. The control screens
included in the online facility allow you to quickly enter
the required information.
/----------------------------- WLM Workload Planning --------------------------\
|Command ===> |
|Enter a ? in any data entry field for more information on valid values. |
|Composing CAP DB File def.: GM1 - WLM Workload Planning Sample Application |
| |
|Summarization Level |
| Primary ===> MONTHS (DAYS/WEEKS/MONTHS) |
| Secondary ===> ZONE (ZONE/HOUR/DAYNAME) |
| |
|Input File Time-Span ===> DETAIL (DETAIL/DAYS/WEEKS/MONTHS) |
| |
|Amount of data retained ===> 60 (1-9999 months) |
|Age of oldest forecast ===> 24 (1-9999 months) |
|History cycles ===> 3 (1-99 cycles) |
|Forecast cycles ===> 3 (1-99 cycles) |
| |
|Data base ID (s) ===> P |
| |
| |
| |
|Specify extended options ===> Y (Y/N) |
\------------------------------------------------------------------------------/
Figure 2-2.01. WLM Workload Planning Screen
Figure 2-2.01 shows the WLM Workload Planning screen, which
is the main control screen for the WLM Workload Planning
Sample Application. It contains the following fields:
Summariza- The output summarization corresponds to the
tion level: combination of the primary and secondary
summarization levels. These control how the
output file is summarized in your capacity
planner database.
Input file The timespan (either DETAIL, DAYS, WEEKS or
timespan: MONTHS) of the HARCPU, WLMSEC and WLMSEM files
that you wish to use as input when creating the
Capacity Planner database file.
Amount of The number of days, weeks or months of
data historical data to be retained in the CAPxxx01
retained: cycle of the Capacity Planner database file.
Any historical observations older than what you
specify for this parameter are dropped from the
file during the file update.
Age of The number of days, weeks or months that you
oldest want to retain a forecast after it is generated.
forecast: Any forecast older than what you specify for
this parameter is dropped when a new forecast is
generated and saved.
History The number of cycles or versions of the
cycle: historical data you want to retain. A new cycle
is created when the file is updated and the
existing cycles aged (for example, Cycle 01 is
aged to Cycle 02 and Cycle 02 becomes Cycle 03).
Forecast The number of cycles or versions of the forecast
cycle: data you want to retain. A new cycle is created
when you specify forecast aging in one of the
workload forecasting routines and the existing
cycles are aged (for example, Cycle 01 is aged
to Cycle 02 and Cycle 02 becomes Cycle 03).
Data base The database unit identifier(s) (up to fourteen
ID(s): units) that contain the WLMSEC and WLMSEM files
to be used with this sample application. If you
are uncertain in which database unit these files
reside, type a question mark (?) in this field
to display a message listing of the valid
database unit identifiers for this sample
application.
Specify If you want extended options, specify Y (YES),
extended and the Extended Options Menu (Figure 2-2.02) is
options: displayed.
/--------------------------- Extended Options Menu ---------------------------\
|Command ===> |
| |
|Inquiry Step: WLM Workload Planning Sample Application |
| |
| |
|Combine all SYSIDs into a composite ===> N (Y/N) |
| Composite SYSID ===> ____ |
| |
|Combine all zones into a composite ===> N (Y/N) |
| Composite zone ===> _________ |
| |
|Specify: |
| Common data selection parameters ===> N (Y/N/R) |
| Global data selection exit ===> N (Y/N/R) |
| Workload mapping definition ===> Y (Y/N/R) |
| Workload mapping (CAPAPU) exit ===> N (Y/N/R) |
| CPU time adjustment parameters ===> N (Y/N/R) |
| Notes report enabled ===> YES (YES/NO) |
| Contents reports enabled ===> YES (YES/NO) |
| |
| |
| |
| |
| |
\------------------------------------------------------------------------------/
Figure 2-2.02. WLM Workload Planning Extended Options Menu
The extended options available with the WLM Workload Planning
Sample Application (Figure 2-2.02) are:
Combine all You can combine SYSIDs in the capacity planning
SYSIDs into database file. Enter a Y (YES) if you want data
a composite: for all of the SYSIDs to be summarized into a
single observation with the Composite SYSID
value.
Combine all You can combine zones, hours, and daynames in
zones/hours/ the capacity planning database file. The prompt
daynames for this field changes to zones or hours or
into a daynames depending on what you specify for the
composite: summary level parameter. Enter a Y (YES) if you
want all of the zones, hours, and daynames to be
summarized into a single observation with the
composite value.
Specify Specify the SYSIDs and zones, and hours or
common data daynames to be used for data selection from the
selection CA MICS input file(s). Enter Y (YES) to display
parameters: the Common Data Selection screen (Figure
2-2.03.) Enter R (RESET) to reset any selections
you previously made to SYSID and zone, and hour
or daynames.
Specify You can use your own SAS statements to select
global data data from the CA MICS input file(s). Enter Y
selection (YES) to display the SAS System Statements
exit: screen (Figure 2-2.04). Enter R (RESET) to
reset any selections you previously made to the
default of no user- specified data selection.
Specify You can define a Workload mapping table. Enter
workload Y (YES) to display the Workload Mapping
mapping Definition screen (Figure 2-2.05), which
definition: provides you with the options for defining a
workload mapping table.
Specify You can use your own SAS statements to split
workload Service Classes into workload (CAPAPU) groups.
mapping Enter Y (YES) to display the SAS System
(CAPAPU) Statements screen.
exit:
Specify CPU Specify the parameters to be used CPU time
time for adjustment (normalization). Enter Y (YES) to
adjustment display the CPU Time Adjustment Parameters
parameters: screen (Figure 2-2.07). Enter R (RESET) to reset
any selections you previously made to CPU time
adjustment.
This option is not available if you select the
composite SYSID option on this screen.
You must select either the Workload mapping definition
extended option or the Workload mapping (CAPAPU) exit to
complete the Workload Planning Sample Application definition.
Notes If you have entered notes associated with the
report capacity planning database file definition, a
enabled: Yes in this field prints the note as part of
file updating.
Contents A Yes in this field prints the contents of the
reports capacity planning database file as part of file
enabled: updating.
/--------------------------- Common Data Selection ---------------------------\
|Command ===> |
| |
|Inquiry Step: WLM Workload Planning Sample Application |
| |
| |
|SYSID ===> ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ |
| ____ ____ ____ ____ ____ |
| |
|Zone ===> _ _ _ _ _ _ _ _ _ (1 - 9) |
| |
|Hour ===> __ - __ __ - __ __ - __ __ - __ __ - __ (0 - 23) |
| |
|Dayname===> _________ _________ _________ _________ _________ |
| |
| |
| |
| |
| |
| |
| |
| |
| |
\------------------------------------------------------------------------------/
Figure 2-2.03. Common Data Selection Screen - WLM Workload Planning
The Common Data Selection screen (Figure 2-2.03) allows you
to define the following data selection criteria:
SYSID: The SYSIDs that you want to include in your
capacity planning database file. You can enter
a maximum of 15 one- to four-character SYSIDs.
Leave this parameter blank to include data for
all SYSIDs.
Zone: You can specify up to nine zones to be included
in the capacity planning database file. Leave
this parameter blank to include data for all
zones.
Hour: Specify the five hours or hour ranges to be
included in the capacity planning database file.
Selection of this parameter is valid only if you
enter the DETAIL, DAYS, or WEEKS timespan on the
WLM Workload Planning screen (Figure 2-2.01).
Leave this parameter blank to include data for
all hours.
Dayname: You can enter up to five daynames to be included
in the capacity planning database file. Leave
blank to include all days. Input the first
unique characters and the application will fill
in the rest. Selection of this parameter is only
valid when the input timespan is DETAIL or DAYS.
/-------------------------- SAS System Statements ---------- COLUMNS 001 072--\
|Command ===> Scroll ===> PAGE |
| |
|SAS Statements for the SELECT Macro |
|-------------------------------------------------------------------------------|
|****** ***************************** TOP OF DATA ******************************|
|==MSG> SPECIFY SAS STATEMENTS TO SUBSET THE CAPACITY PLANNING DATA BASE FILE. |
|=NOTE= %MACRO SELECT; <=== PLEASE DO NOT PLACE LINES BEFORE THIS LINE. |
|000001 |
|000002 |
|000003 |
|000004 |
|000005 |
|000006 |
|000007 |
|000008 |
|000009 |
|000010 |
|=NOTE= %MEND SELECT; <=== PLEASE DO NOT PLACE LINES AFTER THIS LINE. |
|****** **************************** BOTTOM OF DATA ****************************|
| |
\------------------------------------------------------------------------------/
Figure 2-2.04. SAS System Statements Screen - WLM Workload Planning
The SAS System Statements screen (Figure 2-2.04) lets you
define your own data selection logic. You can code any valid
SAS statements as described in the SAS manuals. The %MACRO
SELECT and %MEND SELECT statements are already provided, and
are field protected from modification.
Note: This is a PDF/EDIT screen. All PDF/EDIT commands are
available.
/------------------------ Workload Mapping Definition ------------------------\
|Command ===> |
| |
|Inquiry step: WLM Workload Planning Sample Application |
| |
| |
|Workload mapping table data set name |
| ===> ________________________________________________________ |
| |
| |
| Edit workload mapping table ===> NO (YES/NO) |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
\------------------------------------------------------------------------------/
Figure 2-2.05. Workload Mapping Definition Screen
The Workload Mapping Definition screen (Figure 2-2.05) offers
two options for defining a Workload Mapping Table: you can
name an externally created data set containing valid workload
mapping statements or you can define the workload mapping
statements online. The following fields are included on this
screen:
Workload The name of an externally created data set
mapping that contains valid workload mapping
table data statements. This parameter can be either a
set name: sequential data set or the member of a
partitioned data set.
Code this parameter as you would any other data
set name. If the data is in a member of a
partitioned data set, include the member name as
part of this parameter. If the data set name is
cataloged under your userid, do not enter your
userid as part of the data set name. If you
code a fully qualified data set name (that is,
including a userid), enclose this data set name
in single quotes.
Edit The specification that allows you to edit the
workload workload mapping table. Enter Y (YES) if you
mapping want to invoke the online editor to modify
table: workload mapping statements in the data set that
is named on the workload mapping table data set
name parameter.
WORKLOAD MAPPING TABLE
The Workload Mapping Table is specified using the ISPF/PDF
Editor, which will be invoked if you specify Y (YES) for the
Edit workload mapping table option. The table contains two
types of entries, the first of which defines the workload
group names and titles. The format of the entry is
WORKLOAD group-name group-title
where group-name is a one- to 12-character workload group
name and group-title is a one- to 40-character name of the
group. Group-title is used to build the DESCRIPT data
element for each workload group.
The second entry type specifies which Service Classes are
included in each group. The format is
srvclass group-name
where srvclass is the one- to eight-byte service class name
and group-name matches a group-name given in a WORKLOAD
statement. Any service class that you do not specify on a
workload mapping statement defaults to a workload group of
OTHER.
An example of a very simple workload mapping table follows.
Note how the descriptions are coded. There is ample use of
non-text characters and embedded blanks. Do not use
quotation marks to surround the descriptions.
WORKLOAD IMSPROD PRODUCTION IMS REGIONS
WORKLOAD BATCH ALL PRODUCTION BATCH
WORKLOAD TBATCH ALL TEST BATCH
WORKLOAD TSO ALL TSO
TSODEV TSO
PRODCNTL TSO
IMSAPPL1 IMSPROD
IMSAPPL2 IMSPROD
HOTBATCH BATCH
REGBATCH BATCH
DEVBATCH TBATCH
Specifying this workload mapping would cause WLMSEC and
WLMSEM data for both the IMSAPPL1 and IMSAPPL2 Service
Classes to be combined into a workload entry named IMSPROD.
Likewise, specifying this workload mapping would cause the
DEVBATCH service class to be left isolated in its own
workload called TBATCH.
/----------------------- SAS System Statements ---------- COLUMNS 001 072--\
|Command ===> Scroll ===> PAGE |
| |
|SAS Statements for the CAPAURT Macro |
|-------------------------------------------------------------------------------|
|****** ***************************** TOP OF DATA ******************************|
|==MSG> SPECIFY SAS STATEMENTS TO SUBSET THE CAPACITY PLANNING DATA BASE FILE. |
|=NOTE= %MACRO CAPAURT; <=== PLEASE DO NOT PLACE LINES BEFORE THIS LINE. |
|000001 |
|000002 SELECT(WLMCLASS); |
|000003 WHEN(HOTBATCH) CAPAPU = 'BATCH'; |
|000004 WHEN(SLOBATCH) CAPAPU = 'BATCH'; |
|000005 WHEN(TSO) D0; |
|000006 IF SYSID = 'PROD' |
|000007 THEN CAPAPU = 'PROD TSO'; |
|000008 ELSE CAPAPU = 'TEST TSO'; |
|000009 END; |
|000010 OTHERWISE CAPAPU = 'OTHERSTF'; |
|000011 END; |
|000012 |
|000013 |
|000014 |
|000015 |
|000016 |
|000017 |
|=NOTE= %MEND CAPAURT; <=== PLEASE DO NOT PLACE LINES AFTER THIS LINE. |
|****** **************************** BOTTOM OF DATA ****************************|
| |
\------------------------------------------------------------------------------/
Figure 2-2.06. Workload Mapping (CAPAPU) Exit Screen - WLM Workload Planning
The Workload Mapping (CAPAPU) Exit screen (Figure 2-2.06)
lets you specify the values for the CAPAPU elements directly
with SAS code. This SAS code can reference CA MICS elements
SYSID, SYSPLEX, WLMCLASS, and WLMCLSPD in determining what to
specify for the CAPAPU. The CAPAURT exit is invoked during
the initial data extraction for the WLMSEC file. Any valid
SAS code is allowed in the exit.
Note that when you use the exit, element DESCRIPT is not
available in the resulting capacity planning database.
/----------------------- CPU Time Adjustment Parameters ----------------------\
|Command ===> |
| |
|Inquiry step: WLM Workload Planning Sample Application |
| |
| |
|Base CPU model ===> ____________ |
|Number of processors in base CPU model ===> __ (1-16) |
|Base CPU service unit coefficient ===> ______ (per processor) |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
\------------------------------------------------------------------------------/
Figure 2-2.07. CPU Time Adjustment Parameters Screen - WLM Workload Planning
The information on the CPU Time Adjustment Parameters screen
(Figure 2-2.07) is required only if you choose CPU time
normalization for the WLM Workload Planning Sample
Application.
Base CPU The 10-character identifier for the base
model: processor. Do not use embedded blanks or equal
signs (=) in this value. For example, if you
want to normalize your actual CPU time values to
the equivalent of a 1000 ZZ, then code 1000ZZ in
this field.
Number of The number of internal CPUs in the base
processors processor. This value must be an integer
in base CPU greater than 0 and less than or equal to 16.
model:
Base CPU The service-units-to-CPU-seconds conversion
service factor for the base processor. The value must
unit be a real number greater than 0. You can
coefficient: compute a relative performance rating by
dividing this value by the corresponding
service-unit-to-CPU-second factor for the
processor represented by the SYSID (see Section
2.2.1 for an example of this calculation). You
can use vendor-supplied values for the factor,
or a factor based on your own evaluations.
Copyright © 2014 CA.
All rights reserved.
|
|