Appendix B. QUICK START TUTORIAL › B.1 Quick Start Tutorial for CPU Planning › B.1.1 Build the Capacity Database for Processor Planning
B.1.1 Build the Capacity Database for Processor Planning
The CA MICS capacity database for an application will be
stored in a SAS Data Library as members that contain the
historical data and the forecasts that are based on the
historical data. As a user, you will store your capacity
database files on a SAS data library that has your TSO userid
as the high level prefix. This user SAS data library is
called a Private capacity database. Once you are satisfied
that the files for a capacity application are correct, they
can be copied to a common SAS Data Library called the Shared
Capacity Database, which has the CA MICS sharedprefix as its
high level qualifier.
If you have never created an application under the CA MICS
Capacity Planner, the SAS Data Library for your private
capacity database will not yet exist. This SAS Data Library
will be allocated automatically as you follow a procedure
such as the one described in this section. If you have
already built an application sometime in the past, then the
SAS Data Library for your private capacity database should
exist already. It might be archived on your system or it
might have been deleted. If it was deleted and you have
followed the backup procedure described in section 12.2 of
this guide, then you could restore your private capacity
database by using the "Private Capacity Planning Database
Restore" procedure which is also described in section 12.2.
When you decide to build a capacity database, you must
determine what data to collect and the timespan at which the
data should be summarized.
This exercise uses the MONTHS timespan for input and
summarization since exceptions or unique system behavior
will not be a concern at this higher timespan. However, if
there are certain days or certain hours of a day that usually
have high CPU utilization, the ZONE element could be defined
so that these peak periods can be isolated. In building the
Capacity Database, peak periods could be eliminated from
the capacity application.
To start the exercise:
1. If this is the first time that you are using the Capacity
Planner, the SAS Data Library that will contain your
capacity database has not yet been allocated. Thus you
should go into the MWF 4;3;0;6 panel ("Data Set Allocation
Parameters"). Under the "Data Set" column are entries for
CAPACITY and for CAPPDS. You will see something similar
to these lines:
_ CAPACITY MICS6.USER.CAPACITY TRK 20 10 3390
_ CAPPDS MICS6.USER.CAPPDS TRK 20 10 20 3390
The names under "Data Set Name Suffix" will be
concatenated after TSO userid to form the names of these
datasets when they are allocated. Thus your private
capacity database will reside in
userid.MICS6.USER.CAPACITY
Note that the names here have 'MICS6.USER' as part of the
suffix. This is purely arbitrary and could be different
in your CA MICS complex.
If you need to change either of these names, you can do so
on this panel. Also, you should change the allocation
space allocation parameters and the "DASD unit" if other
values are appropriate.
2. Proceed to MWF 4;3;1 and INSERT a new Capacity Query
(Documentation: CAP Section 1.5.3).
Code values that you want for the "File Name" and "Title".
Record the File Name here: ________.
Select 1 for "Sample Applications" and press ENTER.
3. A list of available Sample Applications will appear. For
our example here, we will select 1 for "z/OS Processor
Planning" (Documentation: CAP Section 2.1) and press
ENTER.
4. Keep the Summarization Level defaults where MONTHS is the
Primary and ZONE is the secondary.
Specify at least one unit data base ID. If you are doing
a Processor Planning application, then the data base ID
must be for a RMF unit.
You may code Y after "Specify extended options" and press
ENTER.
5. Go to the Extended Options Menu (Section 2.1.1 and 2.1.2).
Specify CPU time adjustment parameters as described in
Figure B-1.
NOTE: WLMSEC is required if the CPU time adjustment is
specified.
/----------------------- CPU Time Adjustment Parameters ----------------------\
|Command ===> |
| |
|Inquiry step: z/OS Processor Planning Application |
| |
| |
|Base CPU model ===> MYCPU_______ |
|Number of processors in base CPU model ===> 1_ (1-16) |
|Base CPU service unit coefficient ===> 100___ (per processor) |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
\------------------------------------------------------------------------------/
Figure B-1. CPU Time Adjustment Parameters Screen
6. After completing the entries in these definition screens,
exit out of them until you arrive at the "Inquiry
Processing" panel. Code EXECUTE after "Specify Inquiry
Processing" and press ENTER
The "Update Capacity Planning File" screen will appear.
See Figure B-2.
/----------------------- Update Capacity Planning File -----------------------\
|Command ===> |
| |
|Executing CAP DB File def.: QC1 - Quick Start CPU Example |
| |
|Type of update ===> INITIALIZE (INITIALIZE/UPDATE) |
|Replace existing file? ===> N (Y/N) |
| |
|Input data source ===> ARCHIVE (ARCHIVE/ONLINE) |
|CA MICS file cycle(s) ===> __ - __ (0 - 99) |
|Archive generation number ===> -6_ (0 to -99) |
| |
|Starting date of update ===> _______ (ddmonyy) |
|Number of months to select ===> ____ (1 to 9999) |
| |
|Mode of execution ===> BATCH (BATCH/FOREGROUND) |
| |
|List updated file contents? ===> YES (YES/NO) |
| |
| |
| |
| |
| |
|Press END to invoke MICF inquiry execution to update the resource element file.|
|Enter CANCEL to terminate the resource element file update. |
\------------------------------------------------------------------------------/
Figure B-2. Update Capacity Planning File Screen
7. Complete the entries on this panel. Since this is the
first time the capacity database will be updated for this
application, the "Type of update" should be INITIALIZE and
"Replace existing file" should be N.
The "Input data source" can be ARCHIVE or ONLINE. If
ARCHIVE is chosen, then the "Archive generation number"
must also be chosen. On the other hand, if ONLINE is
chosen, then the input will come directly from an
existing CA MICS timespan. In this case, the "CA MICS
file cycle(s)" must be specified and the "Archive
generation number" must be blank.
The Starting date and the number of months to select
should be coded.
You may select BATCH or FOREGROUND as the "Mode of
execution". You might find the BATCH option to be
better as a learning tool, since you can study a listing
of the batch job before it is submitted for execution.
Note: It is best to bring in as much data as possible. It
is recommended that you specify ARCHIVE (the relative GDG
can be specified on the execute, such as 0, -1, -2, -3,
etc.) to use the monthly archive tapes. Rerun a second
time using the online files in order to have as much
history as possible for analysis. Remember, you have to
change the "Number of Months to select" to bring in more
than one month's data.
8. Press END and follow the panels until you reach the MICF
Execution screen. Code Y for "Override Execution Options"
and for "Edit Generated Jobstream". Press ENTER.
Review the "Execution Options" and press END to generate
the batch update job.
Note that in the JCL portion of this job is a DD statement
for CAPCOMDS. The DSN should refer to the SAS Data
Library that will contain the capacity database members
for this job. By the time this batch job has been
generated, this SAS Data Library should have been
allocated.
9. Submit the job and track its progress. The output should
have a PROC CONTENTS listing of all the variables in the
member that has been created. It should also contain a
listing of the CA MICS performance data that were input
to the job.
10. You will need to run the query you just built on a
regular basis. The execution interval depends on the
timespan selected; ie., days, weeks, months. This may be
accomplished by one of the following methods:
a. Production Reporting. The private query will need to
be copied to the SHARED inquiry catalog (MWF 4;3;4).
b. Run the JCL from the inquiry within a production
scheduling system such as CA-7.
c. Run the PRIVATE inquiry each day (MWF 4;3;1).
11. For this exercise, copy this query to the SHARED capacity
database.
This enables the scheduling of this query and makes it
available for all three of the scheduling options listed
in Step 10.
a. Go to MWF 4;3;4 to copy the PRIVATE query to the
SHARED capacity database.
b. Go to MWF 4;3;1 and delete the original Private query
(you can always copy the SHARED copy back if the need
arises) to eliminate duplicate data.
12. You should now have one copy of capacity history in your
sharedprefix.CAPACITY This copy will be backed up by
your DAILY or MONTHLY CA MICS backup job for your primary
unit.
Note that you will need to set up your own backup and
restore jobs for your private capacity database by
following the directions in section 12.2 of this guide.
Copyright © 2014 CA.
All rights reserved.
|
|