3. PERFORMANCE ANALYSIS TOOLS › 3.3 Data Clustering Analysis › 3.3.6 Case Studies › 3.3.6.1 Batch Job Class Study › 3.3.6.1.2 Control Parameters
3.3.6.1.2 Control Parameters
Figure 3-50 illustrates the Data Clustering screen.
/-------------------------- Data Clustering -----------------------------------\
|Command ===> |
| |
|Composing CA MICS Inquiry: CLASS - Batch Job Class Case Study |
| |
|CA MICS file ===> JOB - |
|Time-span: DETAIL Cycle(s) ===> 01 - 10|
|Data base ===> A _ _ _ _ |
|Allow Run-time Override of Data Base ===> Y (Y/N) and/or Cycle(s) ===> Y (Y/N)|
| |
|Analysis based on ===> JOBTCBTM TAPEUSE_ ________ ________ ________ |
| ________ ________ ________ ________ ________ |
|Report for each cluster ===> JOBEDASD JOBETAPE JOBTOHRS JOBNLR ________ |
| ________ ________ ________ ________ ________ |
| |
|Data Selection: Allow run-time override|
| Date ===> _______ - _______ _______ - _______ ===> N (Y/N)|
| Hour ===> __ - __ __ - __ __ - __ ===> N (Y/N)|
| Zone ===> 1 2 3 4 _ _ _ _ _ ===> N (Y/N)|
| SYSID ===> SYSA ____ ____ ____ ____ ____ ===> N (Y/N)|
| |
| |
|Specify extended options ===> Y (Y/N) |
\-------------------------------------------------------------------------------/
Figure 3-50. Data Clustering Screen
The Data Clustering screen contains the following fields:
CA MICS file: The CA MICS file to be used for workload
characterization. (For this example, we
specified the CA MICS BATJOB File for a job
class study.)
Cycles: The number of cycles to be specified. (For
example, we specified ten cycles. In an actual
study, analyze as much data as possible before
you initiate a new job class structure.)
Database: The single-character database identifier for
this file at your site.
Analysis The CA MICS data element feature names (CPU
based on: Time and Tape Drive Usage) to be used in the
clustering procedure. Because TAPEUSE is a
user supplied element that is used to summarize
tape device usage, it is defined on the
User-Defined Data Element Derivation Macro
screen and uses the DRVMAC macro to populate
the data values. (As discussed in Section
3.3.2.4, you should specify as few features as
possible.)
DASD EXCPs, Tape EXCPs, Tape Drive Occupancy
Time, and print lines are specified for
reporting purposes.
/--------------------------- Extended Options Menu --------------------------\
|Command ===> |
| |
|Inquiry Step: Data Clustering |
| |
| |
|Specify global data selection exit ===> N (Y/N/R) |
|Specify non-CA MICS data element derivation exit===> Y (Y/N/R) |
| |
|Specify alternate input file ===> N (Y/N/R) |
|Save selected input observations ===> N (Y/N/R) |
|Save cluster output observations ===> Y (Y/N/R) |
| |
|Specify data filtering parameters ===> Y (Y/N/R) |
|Specify clustering execution options ===> Y (Y/N/R) |
|Define report description element names ===> N (Y/N/R) |
| |
| |
| |
| |
\-------------------------------------------------------------------------------/
Figure 3-51. Data Clustering Extended Options Menu
You can select additional option specifications on the
Extended Options Menu. Figure 3-51 shows an example with
four of the extended options specified.
/------------------------ Report Description Elements ----------- ROW 1 OF 2\
|Command ===> Scroll ===> CSR |
| |
|Inquiry Step: Data Clustering |
| |
| Note: The application will automatically insert all key sequence |
| elements relevant to the CA MICS file being analyzed into |
| the clusters for use in optional reporting. There is no need |
| to include any key sequence elements. |
| |
|Line cmds: I Insert D Delete M Move |
| |
|Cmd Element Data element label (long name) Warning |
| - -------- ---------------------------------------- -------- |
| _ JOBCLASS |
| _ |
|****************************** BOTTOM OF DATA *******************************|
| |
| |
\-------------------------------------------------------------------------------/
Figure 3-52. Report Description Elements Screen
Since we wished to create an optional external report data
set during the study, we also specified two descriptive
variables. We selected the variable, JOBCLASS (job class),
so that the results of the cluster analysis could be compared
with the current job class structure and the assignment of
particular jobs could be determined. These data elements are
specified on the Report Description Elements screen shown in
Figure 3-52 above.
/------------------------------- SAS Statements -----------------------------\
|Command ===> Scroll ===> CSR |
| |
|Inquiry Step: Data Clustering |
| |
|Line Cmds: I Insert D Delete R Repeat M Move C Copy |
| |
|Cmd SAS Statements for: Specifying data element derivation |
| - ------------------------------------------------------------------------ |
| _ - %MACRO DRVMAC; |
| _ IF JOBMXNTA EQ 0 THEN TAPEUSE = 0; |
| _ ELSE IF 01 LE JOBMXNTA LE 3 THEN TAPEUSE = 1; |
| _ ELSE TAPEUSE = 2; |
| _ LABEL TAPEUSE = "Tape Device Usage Indicator"; |
| _ - %MEND DRVMAC; |
|****************************** BOTTOM OF DATA *******************************|
| |
| |
| |
| |
\-------------------------------------------------------------------------------/
Figure 3-53. User-Defined Data Element Derivation Macro
The SAS statements that compute the user-defined data
elements are placed in the DRVMAC macro shown in Figure
3-53 above.
/--------------------- Data Filtering Options --------------------- ROW 1 OF 1\
|Command ===> Scroll ===> CSR |
| |
|Inquiry Step: Data Clustering |
| |
| Please enter the names of elements that should be checked for zero |
| values. Observations with elements specified below that contain zero |
| values will be subsequently discarded from further processing. |
| |
|Line Cmds:%I+Insert %D+Delete %M+Move |
| |
|Cmd Element Data element label (long name) Warning |
| - -------- ---------------------------------------- -------- |
| _ JOBTCBTM |
| _ |
| _ |
|****************************** BOTTOM OF DATA *******************************|
| |
| |
| |
\-------------------------------------------------------------------------------/
Figure 3-54. Filter Observations
We excluded jobs that used no CPU time from the study, since
they did not execute due to a JCL error, or some other
abnormal condition. To exclude jobs with no CPU usage,
specify the data element name, JOBTCBTM, on the Data
Filtering Options screen shown in Figure 3-54 above.
/--------------------- Save Cluster Output Observations ---------------------\
|Command ===> |
| |
|Inquiry Step: Data Clustering |
| |
|SAS file name ===> ALLOBS |
| |
|SAS data set name ===> 'your.dataset.name' |
| |
| |
| |
\-------------------------------------------------------------------------------/
Figure 3-55. External Report Output File Definition
In this case study we wanted to create the SAS data set name,
ALLOBS, that contains the cluster analysis output. To do
this, we specified ALLOBS as the SAS file name on the
External Report Output File Definition screen shown in Figure
3-55 above.
/----------------------------- Inquiry Processing ----------------------------\
|Command ===> |
| |
| |
| |
| Active MICF Inquiry: CLASS - Batch Job Class Case Study |
| Author: Charles Frost |
| |
| |
| Specify Inquiry processing ===> EXECUTE (EXECUTE/MODIFY/SAVE/CANCEL) |
| EXECUTE - Execute the inquiry. |
| MODIFY - Redisplay the inquiry for modification. |
| SAVE - Exit from inquiry composition and save the inquiry. |
| CANCEL - Exit from inquiry composition without saving the inquiry. |
| |
| |
|Instructions: |
| |
| Specify desired option and press ENTER key. |
| |
| |
| |
| |
\-------------------------------------------------------------------------------/
Figure 3-56. Inquiry Processing
After a Data Clustering analysis inquiry is created, the
Inquiry Processing screen shown here is displayed. From this
screen, you can execute the newly created inquiry, modify it,
save it without executing it, or cancel the parameter
specifications you just entered.
Copyright © 2014 CA.
All rights reserved.
|
|