CAP Tracking Applications
The tracking applications case study illustrates how to create a resource element file that describes the resource requirements of a payroll application from the MONTHS timespan of the BATJOB File.
micsrm140
The tracking applications case study illustrates how to create a resource element file that describes the resource requirements of a payroll application from the MONTHS timespan of the BATJOB File.
Problem Description
The tracking applications case study addresses the following areas:
- Summarizing multiple SYSIDs and ZONEs into a composite SYSID and ZONE. Although you may typically expect an application to run during a specific zone or on a specific processor, summarizing data from all zones and systems prevents the loss of data when the application runs in an unexpected manner.
- Using a selection exit to limit the volume of data that is processed by the program. Rather than summarizing the data for all jobs, the selection exit retains data for the application being studied and excludes data for all of the other jobs.
Identifying applications in the MONTHS timespan of the BATJOB File depends on the way that you define the BATJOB File accounting fields. In the test installation, applications are identified by two three-character account codes (ACCTNO1 and ACCTNO2). The payroll application is identified by the account codes P39 and 028. We chose the following data elements to characterize the application for this case study:
Data Element
| Description
|
JOBTCBTM | Total TCB CPU time used by the application |
JOBSRBTM | Total SRB CPU time used by the application |
JOBNLR | Total lines printed by the application |
JOBMXWSS | The maximum working set size of the application |
JOBCOUNT | The total number of jobs executed during the month |
JOBSTEPS | The total number of job steps executed during the month |
JOBSYSAB | The total number of system ABENDs experienced by the application during the month |
JOBUSRAB | The total number of user ABENDs experienced by the application during the month |
Although these data elements do not provide a complete characterization of all resources that are used by the application, they are examples of key indicators that capacity planners would find interesting. The
MICS
BATJOB File contains many other data elements which you could select to augment this capacity database file, based on your own interest.Control Parameters
Figures 3-70 through 3-78 show the control screens that we used to create and execute this resource element file example.
Figure 3-70. Resource Element File Definition Screen
/---------------------- Resource Element File Definition ---------------------\ |Command ===> | |Enter a ? in any data entry field for more information on valid values. | | CAP DB File def.: PAY - Payroll Application Example | | | |Summarization Level | | Primary ===> MONTHS (DAYS/WEEKS/MONTHS) | | Secondary ===> ZONE (ZONE/HOUR/ENDTS/DAYNAME) | | | |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 ===> N (YES/NO) | | Contents reports ===> N (YES/NO) | | | |Specify extended options ===> N (Y/N) | --------------------------------------------------------------------------------
The specifications on the Resource Element File Definition screen that is shown in Figure 3-70 do the following:
- Set the timespan to MONTHS
- Set the summary level to ZONE
Figure 3-71. Selecting Common Data
/--------------------------- Resource Element File ---------------------------\ |Option ===> 1 | | | |Composing CAP DB file def.: PAY - Payroll Application Example | | | | | | 1 - Insert Common Data Selection | | Specify data selection criteria to apply to ALL files. | | 2 - Insert CA MICS File and Data Element Selection | | Select a CA MICS file and data elements. | | 3 - Insert Cross-File Data Element Definition | | Specify cross-file data element derivations. | | | | | | | | | | | | | | | | | | | | | | | --------------------------------------------------------------------------------
Option 1, Insert Common Data Selection, is chosen on the Resource Element File screen that is shown in Figure 3-71.
Figure 3-72. Common Data Selection Screen
/--------------------------- Common Data Selection ---------------------------\ |Command ===> | |Enter a ? in any data entry field for more information on valid values. | |Composing CAP DB File def.: PAY - Payroll Application Example | | | | | |SYSID ===> TSO1 TSO2 ____ ____ ____ ____ ____ ____ ____ ____ | | ____ ____ ____ ____ ____ | | | |Zone ===> _ _ _ _ _ _ _ _ _ (1 - 9) | | | |Hour ===> __ - __ __ - __ __ - __ __ - __ __ - __ (0 - 23) | | | |Dayname ===> _________ _________ _________ _________ _________ | | | | | | | | | | | | | | | | | |Specify common data selection SAS statements ===> Y (Y/N/R) | --------------------------------------------------------------------------------
The Common Data Selection screen that is shown in Figure 3-72 specifies that observations with SYSIDs that are equal to TSO1 or TSO2 are to be included in the resource element data file. SAS statements are specified to further control data selection.
Figure 3-73. Common Data Selection Screen
/-------------------------- SAS System Statements ---------------------------\ |Command ===> Scroll ===> CSR | | | |Inquiry Step: File & Data Element Sel.: PAY - PAYROLL APPLICATION | | | |SAS Statements for the SELECT Macro | |------------------------------------------------------------------------------| |****** ***************************** TOP OF DATA *****************************| |==MSG> SPECIFY SAS STATEMENTS TO SUBSET THE CAPACITY PLANNING DATA BASE FILE. | |=NOTE= %MACRO SELECT; <=== PLEASE DO NOT PLACE LINES BEFORE THIS LINE. | |000001 IF ACCTN01 = 'P39' AND ACCTN02 = '028' ; | |=NOTE= %MEND SELECT; <=== PLEASE DO NOT PLACE LINES AFTER THIS LINE. | |****** **************************** BOTTOM OF DATA ***************************| | | --------------------------------------------------------------------------------
The Common Data Selection screen that is shown in Figure 3-73 is specified to further subset the input file by selecting observations for a particular pair of account numbers only.
Figure 3-74. Selecting
MICS
Files and Data Elements/--------------------------- Resource Element File ---------------------------\ |Option ===> 2 | | | |Composing CAP DB file def.: PAY - Payroll Application Example | | | | | | 1 - Insert Common Data Selection | | Specify data selection criteria to apply to ALL files. | | 2 - Insert CA MICS File and Data Element Selection | | Select a CA MICS file and data elements. | | 3 - Insert Cross-File Data Element Definition | | Specify cross-file data element derivations. | | | | | | | | | | | | | | | | | | | | | | | --------------------------------------------------------------------------------
Option 2, Insert
MICS
File and Data Element Selection, is chosen on the Resource Element File screen that is shown in Figure 3-74.The
MICS
File and Data Element Selection screen that is shown in Figure 3-75 specifies that the MICS
JOB file in database complex P is to be used. The data elements to be included in the resource element file are listed.Figure 3-75.
MICS
File and Data Element Selection Screen - Screen 1/-------------------- CA MICS File and Data Element Selection ---------------\ |Command ===> Scroll ===> CSR | |Enter a ? in any data entry field for more information on valid values. | |Composing CAP DB File def.: PAY - Payroll Application Example | |CA MICS file ===> JOB (fff) - BATCH USER JOB ACTIVITY FILE | |Input Time-Span ===> MONTHS (DETAIL/DAYS/WEEKS/MONTHS) | |Data base (s) ===> P | |Include CAPAPUs ===> N (Y/N) -------Line Commands--------| |Summarize file by ===> ________ | I Insert C Copy D Delete || |Specify file exits ===> N (Y/N) | R Repeat E Calculations || | | S Depend Clauses & Label || | ----------------------------| | Sum Data | |Cmd Name Label (long name) D Type Type Order Len Output-Format | | - -------- ----------------------------- - ---- ---- ----- --- ------------- | | _ DATE Interval End Date | | _ RET D 000 7 DATE7________ | | _ JOBCOUNT Job Executions | | _ ACCM N 050 5 _____________ | | _ JOBMXWSS Max Step Work Set | | _ MAX N 050 5 _____________ | | _ JOBNLR Total Log. Writer | | _ ACCM N 050 13 _____________ | | _ JOBSRBTM Job SRB CPU Time | | _ ACCM T 050 10 TIME14.2_____ | | _ JOBSTEPS Number of Steps | | _ ACCM N 050 10 _____________ | | _ JOBSYSAB Job System Abends | | _ ACCM N 050 5 _____________ | |******************************* BOTTOM OF DATA *******************************| | | --------------------------------------------------------------------------------
Figure 3-75.
MICS
File and Data Element Selection Screen - Screen 2/-------------------- CA MICS File and Data Element Selection ---------------\ |Command ===> Scroll ===> CSR | |Enter a ? in any data entry field for more information on valid values. | |Modifying CAP DB File def.: PAY - Payroll Application Example | |CA MICS file ===> JOB (fff) - BATCH USER JOB ACTIVITY FILE | |Input Time-Span ===> MONTHS (DETAIL/DAYS/WEEKS/MONTHS) | |Data base (s) ===> P | |Include CAPAPUs ===> N (Y/N) -------Line Commands--------| |Summarize file by ===> ________ | I Insert C Copy D Delete || |Specify file exits ===> N (Y/N) | R Repeat E Calculations || | | S Depend Clauses & Label || | ----------------------------| | Sum Data | |Cmd Name Label (long name) D Type Type Order Len Output-Format | | - -------- ----------------------------- - ---- ---- ----- --- ------------- | | _ JOBTCBTM Job TCB CPU Time | | _ ACCM T 050 10 TIME14.2_____ | | _ JOBUSRAB Job User Abends | | _ ACCM N 050 5 _____________ | | _ MONTH Month of Year | | _ RET N 000 2 _____________ | | _ SYSID System Identifier | | _ RET A 000 4 _____________ | | _ YEAR Year of Century | | _ RET N 000 2 _____________ | | _ ZONE Time Zone | | _ RET A 000 1 _____________ | --------------------------------------------------------------------------------
Figure 3-76. Validating the Inquiry
/--------------------------- Resource Element File --------Inquiry Validated.-\ |Command ===> Scroll ===> CSR | | | |Composing CAP DB File def.: PAY - Payroll Application Example | | | |Update the capacity planning data base file ===> Y (Y/N) | | | |Line Cmds: S Select I Insert D Delete R Repeat | | | |Cmd Data Base File Definition Step | | - ------------------------------------------------------------------ | | _ Resource Element File Definition | | _ Common Data Selection | | _ File & Data Element Sel.: JOB - BATCH USER JOB ACTIVITY FILE | |****************************** BOTTOM OF DATA ********************************| | | | | | | | | | | | | | | | | --------------------------------------------------------------------------------
After the resource element file definition parameters are specified, the Resource Element File screen is used to validate the inquiry. Figure 3-76 shows this screen after VALIDATE is typed at the Command prompt.
Figure 3-77. Saving the Inquiry
/----------------------- Update Capacity Planning File -------- Confirm Save.-\ |Command ===> | | | |Modifying CAP DB File def.: PAY - Payroll Application Example | | | | | |This file definition has been changed and must be saved before updating the | |file. | | | | | |Do you wish to save the file definition and update the file? ===> YES (YES/NO) | | | | | | | | | |Instructions: | | | | Press ENTER key to save the file definition and update the file. | | | | Reply NO and press enter key to cancel the file update request. | | | | | | | --------------------------------------------------------------------------------
The Update Capacity Planning file screen that is shown in Figure 3-77 is used to save the inquiry so that it can be executed.
Figure 3-78. Executing the Inquiry
/----------------------- Update Capacity Planning File -------------------------\ |Command ===> | | | |Composing CAP DB File def.: PAY - Payroll Application Example | | | |Type of update ===> INITIALIZE (INITIALIZE/UPDATE) | |Replace existing file? ===> N (Y/N) | | | |Input data source ===> ONLINE (ARCHIVE/ONLINE) | |CA MICS file cycle(s) ===> 01 - 05 (0 - 99) | |Archive generation number ===> ___ (0 to -99) | | | |Starting date of update ===> _______ (ddmonyy) | |Number of months to select ===> 5___ (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. | | | --------------------------------------------------------------------------------
Cycles 1 through 5 are specified as input to the database loading process on the Update Capacity Planning File screen that is shown in Figure 3-78. The updated resource element file will be printed after the update is complete.
Output Report
The following figure 3-79 shows the output that is created by the PROCPRINT of the updated data set.
3-79 Resource Element File Contents Report
CA MICS Capacity Planner OBS DATE JOBCOUNT JOBNLR JOBSRBTM JOBSTEPS JOBSYSAB JOBTCBTM JOBUSRAB JOBMXWSS MONTH SYSID YEAR ZONE 1 31MAY98 470 69572 0:49:06.09 1725 10 16:56:39.10 9 280 5 TSOA 98 A 2 30JUN98 682 44740 1:09:51.00 2190 46 21:30:41.10 20 491 6 TSOA 98 A 3 31JUL98 556 78848 1:04:02.63 1439 33 19:55:22.87 13 724 7 TSOA 98 A 4 31AUG98 718 153084 1:04:57.95 1618 57 20:01:14.77 26 608 8 TSOA 98 A 5 30SEP98 559 57062 0:56:43.29 1495 24 17:10:10.31 32 1599 9 TSOA 98 A