3. CAPACITY PLANNING DATABASE › 3.4 Meta Files › 3.4.2 Screen Operation › 3.4.2.1 Creating a Database Specification › 3.4.2.1.1 File Definition
3.4.2.1.1 File Definition
Figure 3-93 shows the first step for creating a user-defined
meta file.
/---------------------------- Meta File Definition ---------------------------\
|Command ===> |
|Enter a ? in any data entry field for more information on valid values. |
|Composing CAP DB File def.: SYS - System Activity Tracking File |
| |
|Summarization Level |
| Primary ===> MONTHS (DETAIL/DAYS/WEEKS/MONTHS) |
| Secondary ===> ZONE (ZONE/HOUR/ENDTS/DAYNAME) |
| |
|Capacity Planner Data Base ===> PRIVATE (Private/Shared) |
| |
|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) |
| |
|Enable: |
| Notes report ===> YES (YES/NO) |
| Contents reports ===> YES (YES/NO) |
| |
|Specify extended options ===> N (Y/N/R) |
\------------------------------------------------------------------------------/
Figure 3-93. Meta File Definition Screen
The Meta File Definition screen shown in Figure 3-93 is the
main control screen for defining meta files. 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.
Note: When you choose a secondary summarization
level of ENDTS, you can only select one CA MICS
file as input. This is due to the difficulty in
merging ENDTS values across multiple files.
Capacity The specification that tells where ALL input
Planner files that make up this Meta file reside. Choose
Database: PRIVATE (the default) if you wish the meta file
to be made up of information in your own
Capacity Planning database. Choose SHARED if you
wish to process information in the Shared
Capacity Planning database.
Note: If this meta file will ever be executed
using the Production Updating Feature of
CA MICS, this field must be set to SHARED,
because you will not be able to copy the file
definition from your private catalog to the
shared catalog.
Amount The number of days, weeks, or months of
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 wish 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
cycles: historical data that you wish to retain. A
new cycle is created when the file is updated
and the existing cycles are aged (that is, Cycle
01 becomes Cycle 02 and Cycle 02 becomes Cycle
03).
Forecast The number of cycles or versions of the forecast
cycles: data that you wish 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 (that is, Cycle 01
becomes Cycle 02 and Cycle 02 becomes Cycle 03).
Specify The specification for selecting extended
Extended options. If you specify Y (YES), the Extended
Options: Options Menu shown in Figure 3-94 displays.
/--------------------------- Extended Options Menu ---------------------------\
|Command ===> |
| |
|Inquiry Step: |
| |
|Combine SYSIDs into a composite ===> N (Y/N) |
| Composite SYSID ===> ____ |
|Combine zones into a composite ===> N (Y/N) |
| Composite zone ===> _________ |
| |
|Number of CAPAPUS ===> 0 (0 through 9) |
|CAPAPU title (First APU) ===> ________________________________________ |
|CAPAPU2 title ===> ________________________________________ |
|CAPAPU3 title ===> ________________________________________ |
|CAPAPU4 title ===> ________________________________________ |
|CAPAPU5 title ===> ________________________________________ |
|CAPAPU6 title ===> ________________________________________ |
|CAPAPU7 title ===> ________________________________________ |
|CAPAPU8 title ===> ________________________________________ |
|CAPAPU9 title ===> ________________________________________ |
| |
|Specify |
| SAS Statements to set CAPAPUs ===> N (Y/N/R) |
| |
\------------------------------------------------------------------------------/
Figure 3-94. Meta File Extended Options Menu
Combine all The specification for combining SYSIDs in the
SYSIDs into Capacity Planning database file. Specify a Y
a composite: (YES) if you wish data for all of the SYSIDs to
be summarized into a single observation with
the Composite SYSID value.
Combine all The specification for combining zones/hours in
zones/hours/ the Capacity Planning database file. The
daynames prompt for this field changes to zones, hours or
into a daynames depending on what you specify for the
composite: summary level parameter. Specify a Y (YES) if
you want all of the zones/hours/daynames to be
summarized into a single observation with the
Composite zone/hour/dayname value.
Number of Specify the number (0 to 9) of application units
CAPAPUs: (CAPAPUs) you are defining for this element.
This activates the optional CAPAPU feature so
that these data elements are present in the
Capacity Planning database file, and are
included in the summarization sequence during
file summarization and merging. If you specify
that CAPAPUs are to be active, you will be
prompted to specify the SAS statements needed to
derive the CAPAPU groupings and corresponding
CAPAPU values.
CAPAPU Specify the 1-40 character title for each CAPAPU
titles: you are defining for this data element.
Specify SAS The specification that allows you to use your
Statements own SAS Statements for defining your resource
to set element file. Specify Y (YES) to display the
CAPAPUs: SAS Statements screen shown in Figure 3-95. This
option is only available if you specify
CAPAPUs.
/--------------------------- SAS System Statements ---------------------------\
|Command ===> Scroll ===> CSR |
| |
|SAS Statements for the CAPAURT Macro |
|-------------------------------------------------------------------------------|
|****** ***************************** TOP OF DATA ******************************|
|==MSG> SPECIFY SAS STATEMENTS TO SET CAPAPU VALUES. |
|=NOTE= %MACRO CAPAURT; <=== PLEASE DO NOT PLACE LINES BEFORE THIS LINE. |
|000001 |
|000002 |
|000003 |
|000004 |
|000005 |
|000006 |
|000007 |
|000008 |
|000009 |
|000010 |
|=NOTE= %MEND CAPAURT; <=== PLEASE DO NOT PLACE LINES AFTER THIS LINE. |
|****** **************************** BOTTOM OF DATA ****************************|
\------------------------------------------------------------------------------/
Figure 3-95. SAS Statements Screen - Defining CAPAPU
The SAS Statements screen shown in Figure 3-95 allows you to
define the SAS statements required to group CAP input
observations into application workload groups that are
appropriate for your installation. All statements that you
specify must conform with the syntax specified in the SAS
manuals.
Two special data elements are available to you for use in
defining your CAPAPU values. The first, CAPIFILE, is a
three-character data element that contains the CAP file name
that corresponds to the CAP file that you chose for
processing after you selected the Insert CAP File and Data
Element Selection option on the Meta File menu (see Section
3.4.2.1.2). The second, CAPIAPU (including CAPIAPU2 to
CAPIAPU9), corresponds to the CAPAPU value found for the
current observation being read from the input CAP file that
you chose. For example, if you specify the Insert CAP File
and Data Element Selection twice, once for CAP file: CPG,
which has one observation for each Performance Group and
again for CAP file: CPA, which has one observation for each
Performance Group/Performance Period combination. CAPIFILE
would be 'CPG' when reading the CPG file and 'CPA' when
reading the CPA file. The following example illustrates the
use of the CAPIFILE and CAPIAPU data elements in defining new
CAPAPU values for the output meta file:
%MACRO CAPAURT;
IF CAPIFILE EQ 'CPA' AND SUBSTR(CAPIAPU,1,1) EQ 2 THEN DO;
IF SUBSTR(CAPIAPU,2,1) EQ 1 THEN CAPAPU='WORKLOAD1';
ELSE IF SUBSTR(CAPIAPU,2,1) EQ 2 THEN CAPAPU='WORKLOAD2';
ELSE IF SUBSTR(CAPIAPU,2,1) EQ 3 THEN CAPAPU='WORKLOAD3';
ELSE IF SUBSTR(CAPIAPU,2,1) EQ 4 THEN CAPAPU='WORKLOAD4';
ELSE IF SUBSTR(CAPIAPU,2,1) EQ 5 THEN CAPAPU='WORKLOAD5';
END;
ELSE IF CAPIFILE EQ 'CGA' THEN DO;
IF SUBSTR(CAPIAPU,1,1) EQ 7 THEN CAPAPU='WORKLOAD6';
ELSE IF SUBSTR(CAPIAPU,1,2) EQ 62 THEN CAPAPU='WORKLOAD7';
ELSE IF SUBSTR(CAPIAPU,1,1) NE 2 THEN CAPAPU='WORKLOAD8';
END;
%MEND CAPAURT;
Copyright © 2014 CA.
All rights reserved.
|
|