3. CAPACITY PLANNING DATABASE › 3.3 Resource Element Files › 3.3.1 Usage Guidelines
3.3.1 Usage Guidelines
The resource element files hold subsets of CA MICS file data
element values extracted from either the DETAIL, DAYS, WEEKS
or MONTHS timespan. You select the data elements for your
resource element file. Like business element files, there
can be any number of resource element files. A
three-character user-supplied name identifies each of the
resource element file definitions.
Refer to Figure 3-1 to see the relationship between resource
element and business element files. The number of cycles (or
copies) of the files maintained is represented by nn. These
cycles have the following values:
Cycle 01: Data from the last file load or update plus any
data from the previous Cycle 01 that is not
older than allowed by the parameter Amount of
data retained on the Resource Element file
Definition screen shown in Figure 3-7). The
CAPxxx01 file contains user-supplied
observations while the CPFxxx01 file contains
the forecasted observations from the workload
forecasting routines. The CPFxxx01 file is not
created until you generate and save a forecast
for the first time.
Cycle 02: Data that is contained in the Cycle 01 file when
it is aged. Aging occurs before the Cycle 01
file is loaded or updated. The Cycle 02 file
acts as a backup copy of the Cycle 01 file as it
existed before the last file update. This cycle
and all succeeding cycles may contain data older
than allowed in the Cycle 01 file because of the
Amount of data retained parameter. Aging of the
CPFxxxnn files (forecast data files) does not
occur until you explicitly specify forecast file
aging in one of the workload forecasting
routines.
Cycle 03 Data from the Cycle xx-1 file just before it was
through aged. This occurs each time the Cycle 01 file
Cycle nn: is updated.
The Cycle 01 file is the input file for the analysis and
forecasting programs. It is created the first time you
execute the file definition inquiry. Reexecuting the file
definition inquiry causes it to be updated. This update
extracts the specified database elements from the DETAIL,
DAYS, WEEKS or MONTHS timespans of the CA MICS database and
merges them to produce user-defined records.
Consider the schematic shown in Figure 3-3. In this example,
data elements (not shown in the figure) are extracted from
the four prior monthly cycles of the CA MICS database. For
this example, assume that the program is executed in May
1997. Hence the four monthly records produced by the
database load represent the time period from January to April
of 1997. The result of executing the user-supplied
parameters is that four observations are written into the
first cycle of the resource element file. Also assume that
three cycles are specified to be maintained in the file.
+------------+
| Screen |
| Definition |
| for File |
| xxx |
+------------+
|
+--------------+--------------+-------------+
| Creates | |
V V V
+----------+ +----------+ +----------+
| CAPxxx01 | Resource | CPFxxx01 | | CPWxxx01 |
+----------+ Element +----------+ +----------+
| Apr 97 | Files |Does not | |Does not |
| Mar 97 | |exist | |exist |
| Feb 97 | |until | |until |
| Jan 97 | |forecasts | |worksheet |
+----------+ |are saved | |is applied|
+----------+ +----------+
Figure 3-3. Files after the Initial Loading of Data
If, in September 1997, another load of four months of CA MICS
data is requested, the sequence of execution would be as
follows: First, the data in the Cycle 01 file is aged
(copied) into the Cycle 02 file. Next, the existing Cycle 01
file is updated with the additional four months of data and
any observations in the new Cycle 01 file that are older than
the maximum data retention value you specified are dropped.
Figure 3-3 shows the status of the files.
+------------+
| Screen |
| Definition |
| for File |
| xxx |
+------------+
|
+--------------+--------------+-------------+
| Creates | |
V V V
+----------+ +----------+ +----------+
| CAPxxx01 | Resource | CPFxxx01 | | CPWxxx01 |
+----------+ Element +----------+ +----------+
| Aug 97 | Files |Does not | |Does not |
| Jul 97 | |exist | |exist |
| Jun 97 | |until | |until |
| May 97 | |forecasts | |worksheet |
| Apr 97 | |are saved | |is applied|
| Mar 97 | | | | |
| Feb 97 | | | | |
| Jan 97 | | | | |
+----------+ +----------+ +----------+
|
V
+----------+
| CAPxxx02 |
+----------+
| Apr 97 |
| Mar 97 |
| Feb 97 |
| Jan 97 |
+----------+
Figure 3-4. Files after the Second Loading of Data
In addition to specifying the number of cycles you want to
maintain, you must also specify the number of months, weeks
or days of data that you want to retain within each cycle.
For example, if you specify that nine months of data should
be available for analysis, and, if in January 1998, you load
another four months data into the file, any data older than
nine months prior to January 1998 is dropped from the Cycle
01 file, although it still exists in the older cycles. This
example is illustrated in Figure 3-4.
+------------+
| Screen |
| Definition |
| for File |
| xxx |
+------------+
|
+--------------+--------------+-------------+
| Creates | |
V V V
+----------+ +----------+ +----------+
| CAPxxx01 | Resource | CPFxxx01 | | CPWxxx01 |
+----------+ Element +----------+ +----------+
| Dec 97 | Files |Does not | |Does not |
| Nov 97 | |exist | |exist |
| Oct 97 | |until | |until |
| Sep 97 | |forecasts | |worksheet |
| Aug 97 | |are saved | |is applied|
| Jul 97 | | | | |
| Jun 97 | | | | |
| May 97 | | | | |
| Apr 97 | | | | |
+----------+ +----------+ +----------+
|
V
+----------+
| CAPxxx02 |
+----------+
| Aug 97 |
| Jul 97 |
| Jun 97 |
| May 97 |
| Apr 97 |
| Mar 97 |
| Feb 97 |
| Jan 97 |
+----------+
|
V
+----------+
| CAPxxx03 |
+----------+
| Apr 97 |
| Mar 97 |
| Feb 97 |
| Jan 97 |
+----------+
Figure 3-5. Files after the Third Loading of Data
If you load data a fourth time in May 1998, the old Cycle 03
file is dropped from the Capacity Planning database file
because of the user-specified limit. Section 3.3.3.1.1
describes how to specify this limit.
+------------+
| Screen |
| Definition |
|for File xxx|
+------------+
V
+--------------+--------------+-------------+
V Creates V V
+----------+ +----------+ +----------+
| CAPxxx01 | Resource | CPFxxx01 | | CPWxxx01 |
+----------+ Element +----------+ +----------+
| Apr 98 | Files |Does not | |Does not |
| Mar 98 | |exist | |exist |
| Feb 98 | |until | |until |
| Jan 98 | |forecasts | |worksheet |
| Dec 97 | |are saved | |is applied|
| Nov 97 | | | | |
| Oct 97 | | | | |
| Sep 97 | | | | |
| Aug 97 | | | | |
+----------+ +----------+ +----------+
V
+----------+
| CAPxxx02 |
+----------+
| Dec 97 |
| Nov 97 |
| Oct 97 |
| Sep 97 |
| Aug 97 |
| Jul 97 |
| Jun 97 |
| May 97 |
| Apr 97 |
| Mar 97 |
| Feb 97 |
| Jan 97 |
+----------+
V
+----------+
| CAPxxx03 |
+----------+
| Aug 97 |
| Jul 97 |
| Jun 97 |
| May 97 |
| Apr 97 |
| Mar 97 |
| Feb 97 |
| Jan 97 |
+----------+
Figure 3-6. Files after the Fourth Loading of Data
Note throughout this example that forecast files do not exist
until you save forecasts. Forecast data is created and aged
in the same way as actual data. Note that the historical
files (CAP files) and the forecast files (CPF files) are not
aged together. The CAP files are aged whenever you perform a
file update. You can age the CPF files only when you request
aging through a parameter on the workload forecast routine
control screens.
Throughout this example that worksheet files do not exist
until you applied one. Worksheet data is created and aged in
the same way as actual data. Note that the historical files
(CAP files) and the worksheet files (CPW files) are not aged
together. The CAP files are aged whenever you perform a file
update. You can age the CPW files when you apply the
worksheet to the database.
In addition to the data elements defined for the resource
element files containing the derived from CA MICS files (the
CAPxxxnn files), the forecast files (CPFxxxnn files) contain
three additional data elements:
FILE_NO: The types of forecast data from the workload
forecasting routines. If FILE_NO is 11, the
data values are point estimates. If FILE_NO is
12, the data values are confidence limits.
FORYEAR: The year value of the most recent historical
observation used to derive the forecast. For
example, if you specify to Univariate Model
Forecasting that a forecast is to be generated
based on data from June 1997 through October
1998, the value of FORYEAR would be 98. This
data element containing this value would be
present on each of the observations that are
forecasted during that execution of Univariate
Model Forecasting.
FORMONTH/ The month, week, or day value of the most recent
FORWEEK/ historical observation used to derive the
FORMNDY: forecast. For example, if you specify to
Univariate Model Forecasting that a monthly
forecast is to be generated based on data from
June 1997 through October 1998, the value of
FORMONTH would be 10. This data element
containing this value would be present on each
of the observations that are forecasted during
that execution of Univariate Model Forecasting.
Copyright © 2014 CA.
All rights reserved.
|
|