2. SAMPLE PLANNING APPLICATIONS › 2.1 z/OS Processor Planning › 2.1.2 Control Parameters
2.1.2 Control Parameters
You need relatively few parameters to implement the z/OS
Processor Planning Sample Application. The control screens
included in the online facility allow you to quickly enter
the information required.
/-------------------------- z/OS Processor Planning --------------------------\
|Command ===> |
|Enter a ? in any data entry field for more information on valid values. |
|Composing CAP DB File def.: CPU - z/OS Processor 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) ===> ___________________________ |
| |
| |
| |
| |
|Specify extended options ===> Y (Y/N) |
\------------------------------------------------------------------------------/
Figure 2-1.01. z/OS Processor Planning Control Screen
Figure 2-1.01 shows the z/OS Processor Planning screen, which
is the main control screen for the z/OS Processor 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
planning database.
Input file The timespan (either DETAIL, DAYS, WEEKS or
timespan: MONTHS) of the HARCPU File that you want to use
as input when creating the capacity planning
database file. If you plan to select the CPU
Time Adjustment option, the WLMSEC File must
also be present at this timespan.
Amount of The number of days, weeks, or months of
data historical data to be retained in the CAPxxx01
retained: cycle of the capacity planning 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
forecast: generated. 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
cycles: historical data that 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
cycles: data that 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 identifiers (up to fourteen
ID(s): units) that contain the HARCPU and WLMSEC Files
to be used with this sample application. If
you are uncertain in which database unit the
HARCPU and WLMSEC 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, enter Y (YES), and
Extended the Extended Options Menu shown in Figure 2-1.02
Options: is displayed.
/--------------------------- Extended Options Menu ---------------------------\
|Command ===> |
| |
|Inquiry Step: z/OS Processor 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 ===> Y (Y/N/R) |
| Global data selection exit ===> Y (Y/N/R) |
| CPU time adjustment parameters ===> Y (Y/N/R) |
| Notes report enabled ===> YES (YES/NO) |
| Contents reports enabled ===> YES (YES/NO) |
| |
| |
| |
\------------------------------------------------------------------------------/
Figure 2-1.02. z/OS Processor Planning Extended Options Menu
The extended options available with the z/OS Processor
Planning Sample Application (Figure 2-1.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 the
zones/hours/ capacity planning database file. The prompt for
daynames this field changes to zones, hours, or daynames
into a depending on what you specify for the summary
composite: 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, hours or daynames
common data to use for data selection in the CA MICS input
selection files. Enter Y (YES) to display the Common
parameters: Data Selection screen shown in Figure 2-1.03.
Enter R (RESET) to reset any specifications you
previously made to SYSID and zone, hour, or
dayname.
Specify You can use your own SAS statements to select
global data data from the CA MICS input files. Enter Y
selection (YES) to display the SAS System Statements
exit: screen shown in Figure 2-1.04. Enter R (RESET)
to reset any specifications you previously made
to the default of no user-specified data
selection.
Specify CPU Specify the parameters to use for CPU time
time adjustment (normalization), if you want this
adjustment optional feature. Enter Y (YES) to display the
parameters: CPU Time Adjustment Parameters screen shown in
Figure 2-1.05. Enter R (RESET) to reset any
specifications you previously made to CPU time
adjustment.
This option is not available if you specify the
composite SYSID option on the CPU Planning
screen shown in Figure 2-1.01. If you select
CPU time adjustment, you must also provide
database units that contain the WLMSEC File on
the CPU Planning screen.
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: z/OS Processor Planning Sample Application |
| |
| |
|SYSID ===> ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ |
| ____ ____ ____ ____ ____ |
| |
|Zone ===> _ _ _ _ _ _ _ _ _ (1 - 9) |
| |
|Hour ===> __ - __ __ - __ __ - __ __ - __ __ - __ (0 - 23) |
| |
|Dayname===> _________ _________ _________ _________ _________ |
| |
| |
| |
| |
| |
| |
| |
| |
| |
\------------------------------------------------------------------------------/
Figure 2-1.03. Common Data Selection Screen-z/OS Processor Planning
The Common Data Selection screen, shown in Figure 2-1.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: Enter the five hours or hour ranges to be
included in the capacity planning database file.
Specification of this parameter is valid only if
you specify the DETAIL, DAYS, or WEEKS timespan
on the z/OS Processor Planning screen shown in
Figure 2-1.01. Leave this parameter blank to
include data for all hours.
Dayname: 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. Specification 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-1.04. SAS System Statements Screen-z/OS Planning Global Data Selection
The SAS System Statements screen shown in Figure 2-1.04
allows you to define your own data selection logic. You can
code any valid SAS statements, as described in the SAS
guides. 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.
/----------------------- CPU Time Adjustment Parameters ----------------------\
|Command ===> |
| |
|Inquiry step: z/OS Processor Planning Sample Application |
| |
| |
|Base CPU model ===> 2094-722 |
|Number of processors in base CPU model ===> 22 (1-99) |
|Base CPU service unit coefficient ===> 19777.5 (per processor) |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
\------------------------------------------------------------------------------/
Figure 2-1.05. CPU Time Adjustment Parameters Screen
The information on the CPU Time Adjustment Parameters screen
shown in Figure 2-1.05 is required only if you choose CPU
time normalization for the z/OS Processor Planning Sample
Application.
Base CPU The 10-character identifier for the base
model: processor. Any name is acceptable in this
field. 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 2094-722, you would code
2094-722 in this field.
Number of The number of internal CPUs in the base
processors processor. This value must be an integer (that
in base CPU is, do not use a decimal point), and it must be
model: greater than 0 and less than or equal to 99.
For example, if you specify a 2094-722 as the
base CPU model, then you would code a 22 in this
field since a 2094-722 has twenty two internal
CPUs.
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.1.1 for an example of this calculation). You
can use vendor-supplied values for the factor,
or a factor based on your own evaluations. For
example, if you specify a 2094-722 as the base
CPU model, you would code 19777.5 in this field.
Copyright © 2014 CA.
All rights reserved.
|
|