3. CAPACITY PLANNING DATABASE › 3.1 Structural Description
3.1 Structural Description
Typically, Capacity Planning requires you to retain far fewer
data elements than what CA MICS database maintains; however,
it requires many more cycles of the data elements than CA
MICS normally maintains. The CA MICS Capacity Planner lets
you develop composite files, known as resource element files
and business element files, that merge the necessary data
elements from many CA MICS files into a single Capacity
Planning file. A resource element file is a SAS data set
that contains data elements you select from CA MICS files or
from user-defined data elements that are computed from CA
MICS data elements. A business element file is a SAS data
set that contains user-specified and supplied data elements
from sources other than CA MICS files.
The CA MICS Capacity Planner provides a bridge between the
capacity planner and the CA MICS database. The files you
produce require a minimum of DASD space for retaining a great
number of historical observations. Moreover, the resources
required to process these files are minimal.
With the application of CAP6480 first delivered with r12 SP3
(PSP0804), the Capacity Planner began implementing SAS
compression on newly created historical Capacity Planner
database cycles.
An internal SAS macro variable CAPCMPRS set to YES has been
added to shared.prefix.SOURCE($CAPMSTR). With this variable
set to yes, any capacity database cycle created either during
an initialization of a new database, or during an update to
an existing database, is created with SAS compression active.
This method will compress the new 01 cycle of the historical
database. During subsequent database updates the database
aging routine will copy the compressed 01 cycle to the 02
cycles deleting the highest cycle in retention, gradually
over time compressing all files of the capacity database.
In some cases, a compressed SAS file may take more space than
if it were not compressed. To determine your compression
savings for each newly created database file, review your
SASLOG from either the initial capacity database create or
the subsequent database update jobs.
In your review, consider that capacity database compression
is active for all historical files in the entire capacity
database, so the best way to determine if compressing your
capacity database saves you space is to compress the entire
capacity database. Performing this function will provide
compression statistics for the entire capacity file.
If you prefer to compress all previously created private
capacity database history files use the JCL provided in the
Backup, Restore and Compression section of this guide.
When you create a resource element or business element file,
you supply a three-character file identifier as one of the
parameters. This identifier generates unique SAS data set
names for the SAS data sets that you need to support a
particular study (using the analysis programs documented in
Chapters 4 through 10). Moreover, the presence of this
identifier in the SAS data set names lets you conduct
multiple studies simultaneously.
When you create resource element, meta, or business element
files, three groups of data sets are generated in the CA MICS
Capacity Planning database:
o A file or set of files containing the historical
observations called CAPxxxnn, where xxx is the file
identifier and nn denotes a cycle number. For business
element files, the CAPxxxnn files will contain all of the
observations that you provide.
o A file or set of files containing the forecasted
observations called CPFxxxnn, where xxx is the file
identifier and nn denotes a cycle number. These
observations are generated by the Univariate Modeling,
Business Element Forecasting, and Multivariate Regression
Forecasting routines of the CA MICS Capacity Planner.
These files do not exist until you run one of these
routines and specify that forecasts are to be saved and/or
aged.
o A file or set of files containing worksheet observations
called CPWxxxnn, where xxx is the file identifier and nn
denotes a cycle number. These observations are generated
by the Worksheet Facility that is part of the CA MICS
Capacity Planner. These files do not exist until you run a
Worksheet Apply routine.
Figure 3-1 provides a schematic diagram of the data sets
generated by the CA MICS Capacity Planner. You specify the
number of cycles (nn) when the files are defined.
+------------+
| Screen |
| Definition |
| for File |
| xxx |
+------------+
|
+----------------+---------------+
| | |
Creates V V V
+----------+ +----------+ +----------+
Resource | CAPxxx01 | | CPFxxx01 | | CPWxxx01 |
Element +----------+ +----------+ +----------+
Files | | | | | |
+----------+ +----------+ +----------+
or | | |
V V V
Meta +----------+ +----------+ +----------+
Files | CAPxxx02 | | CPFxxx02 | | CPWxxx02 |
+----------+ +----------+ +----------+
or | | | | | |
+----------+ +----------+ +----------+
Business | | |
Element V V V
Files . . .
. . .
. . .
| | |
V V V
+----------+ +----------+ +----------+
| CAPxxxnn | | CPFxxxnn | | CPWxxxnn |
+----------+ +----------+ +----------+
| | | | | |
+----------+ +----------+ +----------+
These files These files These files
contain contain contain user
actual data forecasts forecast data
from the from the
forecasting Worksheet
routines Facility
Figure 3-1. Resource, Meta, and Business Element File Creation
Copyright © 2014 CA.
All rights reserved.
|
|