Batch Workload Analysis Tool User s Guide Version 4

Batch Workload Analysis Tool User′s GuideVersion 4.3

July 23, 2013

------------------Document Owner:John A. Campbell

T/L 938-2087720-396-2087

[email protected]

IBM ATS System z Capacity Planning Support (CPS)Gaithersburg, MD

CAUTION ON THE USE OF THIS DOCUMENT

The tool described in this document provides a means of estimating the elapsed time for batch jobssolely based on the differences in CPU speeds for a base processor and a target processor, the number ofengines on each system, and system capacities. Data sharing is not considered.

This tool is meant to be used to give the customer a starting point for addressing jobs that could becandidates for running on processors other than the processor they currently run on. The results of thistool must be used with caution when evaluating jobs to be moved to the target processor. There is noguarantee that your results will correspond to the projections. Many factors, including but not limited tothe following, may result in significant variances between the actual and projected results:

• Different I/O configurations between base and target systems.

• Differences greater than 10% between actual processor utilization and the utilization parameters usedwhen running the tool.

• Customer workload characteristics different from the workloads used to generate LSPR values.

This document has not been subject to any formal review.

© Copyright IBM Corp. 2013

USE AND WARRANTY

IBM ATS System z Capacity Planning Support (CPS)

CPS tools may NOT be distributed outside of IBM! CPS capacity planning tools are provided for theexclusive use of IBM employees and authorized IBM Business Partners. These tools may be useddirectly with customers, and output from the tools can be provided to customers. However, the toolsthemselves are NOT authorized for distribution outside of IBM.

The CPS tools are provided to IBM Business Partners for use within the theirenterprise for IBM cus-tomers. Additional copies, if needed, must be obtained from IBM. By downloading the tools, BusinessPartner agrees not to disassemble, reverse compile, or otherwise attempt to create source code for thetool.

THE CPS TOOLS ARE PROVIDED ON AN AS IS BASIS WITH NO WARRANTIES, EITHEREXPRESS OR IMPLIED, INCLUDING THE POSSIBLE INFRINGEMENT OF ANY THIRDPARTY INTELLECTUAL PROPERTY RIGHTS. USE OF THE TOOLS IS ENTIRELY AT THEBUSINESS PARTNERS RISK AND IBM SHALL NOT BE LIABLE FOR ANY DAMAGES,EITHER DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL, INCLUDING BUT NOTLIMITED TO BUSINESS, REVENUE, GOODWILL, OR LOSS OF ANTICIPATED PROFITSOR BENEFITS, EVEN IF IBM HAS BEEN ADVISED OF THE POSSIBILITY OF SUCHDAMAGES AND NOTWITHSTANDING THE FAILURE OF ANY ESSENTIAL PURPOSE.

How to contact Capacity Planning Support:Lotus Notes: CPS PC Tools/Gaithersburg/IBM@IBMUS

E-mail: [email protected]

TRADEMARKS

The following terms are trademarks of the IBM Corporation in the United States or other countries orboth:

CICS* OS/390DB2* Parallel Sysplex*DFSORT RMFe-business logo* S/390*Enterprise Storage Server WebSphere*IBM* VSE/ESAIBM logo* VM/ESA*IMS z/OS*LSPR z/VM*Multiprise* zSeriesIBM System z9 IBM System z10IBM zEnterprise System* IBM zEnterprise 196 (z196)IBM System z* IBM zEnterprise 114 (z114)IBM zEnterprise EC12 (zEC12) IBM zEnterprise BC12 (zBC12)

* Registered trademarks of IBM Coporation

ii

Summary of Changes

************************************************************************************ Version Date Summary of Changes ** ------- -------- ----------------------------------------------------------- ** 1.0 09/23/94 Initial Release ** ** 1.1 10/19/94 Changed units for MINET and MINDELTA to seconds instead of ** minutes. ** Changed the graphs to distinguish between jobs that had ** increased elapsed times and jobs that had decreased elapsed ** times. ** Added a TOTAL line at the end of JOB and STEP reports. ** ** 1.11 10/24/94 Allow TARGETRPP and BASERPP to contain 2 digits to the right** of the decimal place. ** Allow value from 1 to 100 for BASEBUSY and TARGETBUSY. ** ** 1.2 12/02/94 Changed to always use CB84 LSPR Values. ** Added new user parameters: CLASS, NOTCLASS, LINES, BASE#LCP,** and TARGET#LCP. ** Added capacity planning information. ** Changed command for obtaining the tool. ** ** 1.3 01/05/95 Added LSPRTYPE parameter to allow user to select CB84 or ** CBW2 LSPR values. ** ** 1.4 04/17/95 Added JES3, JES3CLASS, and NOTJES3CLASS to allow the user ** to select and display JES3 job classes. ** 1.5 08/15/95 Added WORKTYPE parameter to allow the user to select the ** type of work to be included in the reports. ** Added CRITPATH as RPTTYPE option and CRITJOBS parameter ** to produce a critical path report. ** Added support for up to 12 processors. ** Added 9672 models R53, R63, R73, R83, and RX3 to performance** data table. ** Added number of EXCPs and number of tape mounts to job and ** step reports. ** Added graph showing groupings of jobs by CPU utilization. ** ************************************************************************************

Summary of Changes iii

************************************************************************************ Version Date Summary of Changes ** ------- -------- ----------------------------------------------------------- ** 1.6 10/23/95 Added 9672 models RA2, R12, R22, R32, R42, R52, and R72 ** to performance data table. ** ** 1.61 12/05/95 The CB84 LSPR workload values will be the default. ** ** 1.7 01/02/96 The maximum number of jobs in a critical path report has ** been increased to 300. ** ** 1.8 01/30/96 Added MINCPUTIME parm to allow filtering on CPU time. ** Added CHECKABEND parm to allow filtering jobs that ** ended abnormally. ** Added PGMNAME parm to allow filtering on program names ** for step reports. ** Added RPTTYPE(INFO) parm to allow a new report to be ** produced that shows general information about jobs. ** The S/390 Parallel Center will no longer run the tool. ** ************************************************************************************

Summary of Changes iv

************************************************************************************ Version Date Summary of Changes ** ------- -------- ----------------------------------------------------------- ** 2.0 09/11/96 Allow type 70 records to be used to calculate system ** utilization. ** Increase the limits on the number of PGROUP, NOTPGROUP, ** CLASS, NOTCLASS, JES3CLASS, and NOTJE3CLASS parameters ** that can be entered. ** Show total of EXCPs in the Job Report. ** Show EXCPs per CPU second in the Job Information Report. ** Added new parameters LPARNAME and BUSYRATIO. ** Made SYSID a mandatory parameter. ** Allow jobnames to be filtered using search fields at ** specified locations within the jobname. ** Added SERVCLASS and NOTSERVCLASS parameters for customers ** running in goal mode. ** Added S/390 Multiprise 2000 and S/390 9672 G3 models to ** the performance data table. ** ** 2.1 09/23/96 Added S/390 Multiprise 2000 models 102, 103, 104, 105, and ** 106. Made minor changes to performance data for other ** Multiprise 2000 models and for 9672 G3 models. ** ** 2.2 12/12/96 Added 9672 RY4 model to the performance data table. ** Added USEBUSYRATIO parameter and changed the meaning of ** the BUSYRATIO parameter. ** ** 2.3 03/21/97 Added NAMECHANGE parameter as quick and dirty solution to ** to duplicate names in critical path. ** Allow comments in parameters. ** Fixed bug that caused slight rounding error when BASERPP ** and TARGETRPP values were entered with decimal points. ** ** 2.4 06/12/97 Added 2003 models 107, 124, and 1C5 and 9672 models RA5, ** RB5, RC5, R15, R25, R35, R45, R55, R65, R75, R85, R95, ** RX5, and RY5 to the performance data table. ** 2.5 12/08/97 Changed all LSPR values to use OS/390 R1 measurements and ** make all values relative to a 9672/R15. ** 2.6 03/05/98 Added 2003 models 203, 204, 205, 206, 207, 215, 216, 224, ** 225, 227, 2C5, 237, 246, 247 and 257 to the performance ** data table. ** Added informational message when mutually exclusive ** parameters USEBUSYRATIO and TARGETBUSY are both specified. ** If both specified, TARGETBUSY value is used. ** Changed sample JCL step 5, sysprint DD statement to show ** Lrecl 133 and Blocksize 6650 to avoid loosing last 2 ** characters of report. ** 07/10/98 Changed documentation for NAMECHANGE parameter to show ** show STARTTIME=hh:mm:ss with added colons. ** 2.7 09/22/98 Changed max SERVCLASS and max NONSERVCLASS from 20 to 50. ** Added G5 6972 models RA6, R16, RB6, R26, RC6, RD6, T16, ** T26, R36, R46, R56, R66, R76, R86, R96, RX6, Y76, Y86, Y96, ** YX6. ** 2.8 07/02/99 Removed reference to BWAT2OPC. Changed discription of ** PGMNAME(X) parameter for clarification. ** Added G5 6972 Turbo models Y16, Y26, Y36, Y46, Y56, & Y66. ** Added G6 6972 models ** Added G6 6972 Turbo models ************************************************************************************

Summary of Changes v

************************************************************************************ Version Date Summary of Changes ** ------- -------- ----------------------------------------------------------- ** 3.0 01/12/00 LSPR values for these processors changed to reflect the ** CB84 and CBW2 LSPR workloads on OS/390 V2R4. ** ** 9021-711,821,822,831,832,941,942,952,962,972,982,9X2 ** 2003-102,103,104,105,106,107,115,116,124,125,126,135, ** 136,146,156,1C5,202,203,204,205,206,207,215,216, ** 224,225,227,237,246,247,257,2C5. ** 7060-H30,H50,H70 (New). ** 9672-R11,R21,R31,R41,R51,R61,R12,R22,R32,R42,R52,R72, ** RA2,R53,R63,R73,R83,RX3,R14,R24,R34,R44,R54,R64, ** R74,R84,R94,RA4,RB4,RC4,RX4,RY4,R15,R25,R35,R45, ** R55,R65,R75,R85,R95,RA5,RB5,RC5,RX5,RY5,R16,R26, ** R36,R46,R56,R66,R76,R86,R96,RA6,RB6,RC6,RD6,RX6, ** T16,T26,Y16,Y26,Y36,Y46,Y56,Y66,Y76,Y86,Y96,YX6, ** X17,X27,X37,X47,X57,X67,X77,X87,X97,XX7,XY7,XZ7, ** Z17,Z27,Z37,Z47,Z57,Z67,Z77,Z87,Z97,ZX7,ZY7,ZZ7. ** ** LSPR values for these processors continue to reflect the ** CB84 and CBW2 LSPR workloads on OS/390 V1R1. These values ** will change if OS/390 V2R4 LSPR data becomes available. ** ** 3090-15T,17T,18T,25T,28T,120E,150E,180E,200E,280E,300E, ** 400E,500E,600E,100S,120S,150S,170S,180S,200S,250S, ** 280S,300S,380S,400S,500S,600S,110J,120J,150J,170J, ** 180J,200J,250J,280J,300J,380J,400J,500J,600J. ** 9021-330,340,500,520,580,620,640,660,720,740,820,860,900.** 9121-180,190,210,260,311,320,411,440,480,490,511,521,522,** 570,610,621,622,732,742. ** 9221-120,130,150,170,200,191,201,211,221,421. ** 4381-90E,91E,92E. ** ** BASERPP and TARGETRPP parameters expanded to accept three ** decimal point precision (0.001) from two (0.01). ** ** Support added for mixed CB84/CBW2 workloads. ** ** New message added to inform user when abended jobs are not ** included in the reports. I.e. Abended job encountered but ** CHECKABEND parameter defaulted or was set to YES. ** ** New parameters RPTCLASS and NOTRPTCLASS were added. ** ** Runs with errors encountered will now have the user ** parameters printed. ** ** Support added to process the Y2K SMF date field ** extension. ** ************************************************************************************

Summary of Changes vi

************************************************************************************ Version Date Summary of Changes ** ------- -------- ----------------------------------------------------------- ** 3.1 03/07/01 LSPR values for ALL processors changed to reflect the ** CB84 and CBW2 LSPR workloads on OS/390 V1R1. ** ** Support added for zSeries 900 models (2064); ** 101, 102, 103, 104, 105, 106, 107, 108, 109, ** 1C1, 1C2, 1C3, 1C4, 1C5, 1C6, 1C7, 1C8, 1C9, ** 110, 111, 112, 113, 114, 115, 116 ** ** 3.2 01/14/02 Updated BWATOOL installation instructions in section ** ′ Installing the Tool′ . ** 02/19/02 Support added for 2066 models 0A1, 0B1, 0C1, 001, 0A2, ** 002, 003 004 ** Support added for 7060 models H55, H75. ** Support added for 3006 model B01 ** Support added for Multiprize 3000 models A01, A10, A20 ** LSPR values used are still based on OS/390 V1R1 for all ** supported processors. ** ** 3.3 04/01/02 Updated BWATOOL installation instructions in section ** ′ Installing the Tool′ , due BWATOOL.LIB is now ** packaged as an unterse load module ** 04/26/02 Support added for 2064 models 2C1, 2C2, 2C3, 2C4, 2C5, 2C6, ** 2C7, 2C8. 2C9, 210, 211, 212, 213, 214, 215, 216 ** ** 3.4 05/13/03 Support added for 2066 models 0E1, 0X2 ** Support added for 2084 models 301, 302, 303, 304, ** 305, 306, 307, 308, 309, 310, 311, 312, 313, 314, ** 315, 316 ** ** 3.4a 08/05/03 Added Use and Warranty information ** Added Trademarks information ** Update ″Installing the Tool″ chapter ** Corrected problem with LSPR data for all models ** Add check for type 70 subtype 1 records ** ** 3.5 04/07/04 Support added for 2086 models 110, 210, 310, 410, ** 120, 220, 320, 420, 130, 230, 330, 430, 140, 240, ** 340, 440, 150, 250, 350, 450, 160, 260, 360, 460, ** 170, 270, 370, 470 ** Change SYSOUT=A to SYSOUT=* in sample JCL ** ** 3.6 07/26/05 -Support added for 2094 models 701, 702, 703, 704, ** 705, 706, 707, 708, 709, 710, 711, 712, 713, 714, ** 715, 716 ** -Correct problem determining when start and end date ** are the same day. Changed limit for BASE#CP, ** BASE#LCP, TARGET#CP and TARGET#LCP from 12 to 16. ** -Remove check for TARGET_CPUTIME less than MIN_CPU ** -Don′ t calculate JOBDATA_BASE_CPUPCNT for INFO ** report since a job can have elapsed time of zero ** which causes S0C9 abend ************************************************************************************

Summary of Changes vii

************************************************************************************ Version Date Summary of Changes ** ------- -------- ----------------------------------------------------------- ** 3.7 04/27/06 Support added for 2094 models (24) ** 401, 402, 403, 404, 405, 406, 407, 408, ** 501, 502, 503, 504, 505, 506, 507, 508, ** 601, 602, 603, 604, 605, 606, 607, 608 ** Support added for 2096 models (73) ** A01, A02, A03, B01, B02, B03, C01, C02, ** C03, D01, D02, D03, E01, E02, F01, F02, ** G01, H01, I01, J01, K04, L03, L04, M03, ** M04, N02, N03, N04, O02, O03, O04, P02, ** P03, P04, Q02, Q03, R04, R01, R02, R03, ** R04, S01, S02, S03, S04, T01, T02, T03, ** T04, U01, U02, U03, U04, V01, V02, V03, ** V04, W01, W02, W03, W04, X01, X02, X03 ** X04, Y01, Y02, Y03, Y04, Z01, Z02, Z03 ** Z04 ** Support removed for all 4381 models (3) ** 90E, 91E, 92E ** Support removed for all 3090 models (40) ** Support removed for all 9221 modesl (10) ** 120, 130, 150, 170, 200, 191, 201, 211, ** 221, 421 ** Support removed for 9121 models (10) ** 180, 190, 210, 260, 320, 440, 480, 490, ** 570, 610 ** Support removed for 9021 models (13) ** 330, 340, 500, 520, 580, 620, 640, 660, ** 720, 740, 820, 860, 900 ** Support removed for 3000 models (3) ** A01, A10, A20 ** Support removed for 3006 models (1) ** B01 ** Changed default for LSPRTYPE to CBW2 ** Corrected calculation of base system utilization ** used in reports ** Don′ t override number of base logical processors ** with value in SMF70BDN field since this field ** does not report the number of active logical ** logical processors if IRD is active ** ************************************************************************************

Summary of Changes viii

************************************************************************************ Version Date Summary of Changes ** ------- -------- ----------------------------------------------------------- ** 3.8 02/26/08 LSPR values for ALL processors changed to reflect the ** batch workloads measured for z/OS V1R8. The CB84 ** (CB-S) workload is no longer included in LSPR ** tables supported by LSPR and the CBW2 (CB-L) ** workload chacteristics have changed significantly. ** Therefore, the CB-Mix workload has been assigned ** to replace CB84 (CB-S), representing I/O intensive ** batch. A modified LoIO-Mix workload has been ** assigned to replace CBW2 (CB-L), representing CPU ** intensive batch. ** ** Support added for 2097 models (52) ** 401, 402, 403, 404, 405, 406, 407, 408, 409, 410, ** 411, 412, 501, 502, 503, 504, 505, 506, 507, 508, ** 509, 510, 511, 512, 601, 602, 603, 604, 605, 606, ** 607, 608, 609, 610, 611, 612, 701, 702, 703, 704, ** 705, 706, 707, 708, 709, 710, 711, 712, 713, 714, ** 715, 716 ** Support removed for all 9021 models (12) ** Support removed for all 9121 models (9) ** Support removed for all 9672 models (96) ** Support removed for all 2003 models (32) ** Support removed for all 7060 models (5) ** ** 3.8a 03/20/08 Update CBW2 capacity values based on a custom z/OS ** 1.8 LSPR MIX (CB-L=27.7%, WASDB=62.6%, OLTP-T=6.8%, ** OLTP-W=2.9%) ** ************************************************************************************

Summary of Changes ix

************************************************************************************ Version Date Summary of Changes ** ------- -------- ----------------------------------------------------------- ** 3.9 10/21/08 Capacity values for ALL processors updated using ** z/OS 1.9 LSPR data. ** ** Support added for 2098 (z10 BC) models (130): ** A01, A02, A03, A04, A05, B01, B02, B03, B04, B05, ** C01, C02, C03, C04, C05, D01, D02, D03, D04, D05, ** E01, E02, E03, E04, E05, F01, F02, F03, F04, F05, ** G01, G02, G03, G04, G05, H01, H02, H03, H04, H05, ** I01, I02, I03, I04, I05, J01, J02, J03, J04, J05, ** K01, K02, K03, K04, K05, L01, L02, L03, L04, L05, ** M01, M02, M03, M04, M05, N01, N02, N03, N04, N05, ** O01, O02, O03, O04, O05, P01, P02, P03, P04, P05, ** Q01, Q02, Q03, Q04, Q05, R01, R02, R03, R04, R05, ** S01, S02, S03, S04, S05, T01, T02, T03, T04, T05, ** U01, U02, U03, U04, U05, V01, V02, V03, V04, V05, ** W01, W02, W03, W04, W05, X01, X02, X03, X04, X05, ** Y01, Y02, Y03, Y04, Y05, Z01, Z02, Z03, Z04, Z05 ** ** Support added for 2084 (z990) models with more ** than 16 CPs (up to 32 CPs): ** 317, 318, 319, 320, 321, 322, 323, 324, 325, 326, ** 327, 328, 329, 330, 331, 332 ** ** Support added for 2094 (z9 EC/700) models with more ** than 16 CPs (up to 32 CPs): ** 717, 718, 719, 720, 721, 722, 723, 724, 725, 726, ** 727, 728, 729, 730, 731, 732 ** ** Support added for 2097 (z10 EC/700) models with more ** than 16 CPs (up to 32 CPs): ** 717, 718, 719, 720, 721, 722, 723, 724, 725, 726, ** 727, 728, 729, 730, 731, 732 ** ************************************************************************************

Summary of Changes x

************************************************************************************ Version Date Summary of Changes ** ------- -------- ----------------------------------------------------------- ** 4.0 07/22/10 Capacity values for ALL processors updated using ** z/OS V1R11 LSPR data. CBW2 capacity values are now ** based on the Low-Avg LSPR workload category and ** CB84 capacity values are now based on the Avg-High ** LSPR workload category. ** ** Support added for 2817 models (77) ** 401, 402, 403, 404, 405, 406, 407, 408, 409, 410, ** 411, 412, 413, 414, 415, 501, 502, 503, 504, 505, ** 506, 507, 508, 509, 510, 511, 512, 513, 514, 515, ** 601, 602, 603, 604, 605, 606, 607, 608, 609, 610, ** 611, 612, 613, 614, 615, 701, 702, 703, 704, 705, ** 706, 707, 708, 709, 710, 711, 712, 713, 714, 715, ** 716, 717, 718, 719, 720, 721, 722, 723, 724, 725, ** 726, 727, 728, 729, 730, 731, 732 ** ** 4.1 07/12/11 Support added for 2818 (z114) models (130)using ** z/OS V1R11 LSPR data: ** A01, A02, A03, A04, A05, B01, B02, B03, B04, B05, ** C01, C02, C03, C04, C05, D01, D02, D03, D04, D05, ** E01, E02, E03, E04, E05, F01, F02, F03, F04, F05, ** G01, G02, G03, G04, G05, H01, H02, H03, H04, H05, ** I01, I02, I03, I04, I05, J01, J02, J03, J04, J05, ** K01, K02, K03, K04, K05, L01, L02, L03, L04, L05, ** M01, M02, M03, M04, M05, N01, N02, N03, N04, N05, ** O01, O02, O03, O04, O05, P01, P02, P03, P04, P05, ** Q01, Q02, Q03, Q04, Q05, R01, R02, R03, R04, R05, ** S01, S02, S03, S04, S05, T01, T02, T03, T04, T05, ** U01, U02, U03, U04, U05, V01, V02, V03, V04, V05, ** W01, W02, W03, W04, W05, X01, X02, X03, X04, X05, ** Y01, Y02, Y03, Y04, Y05, Z01, Z02, Z03, Z04, Z05 ** ** 4.2 08/28/12 Capacity values for ALL processors updated using ** z/OS V1R13 LSPR data. CBW2 capacity values are ** based on the Low-Avg LSPR workload category and ** CB84 capacity values are based on the Avg-High ** LSPR workload category. ** ** Support added for 2827 models (92) ** 401, 402, 403, 404, 405, 406, 407, 408, 409, 410, ** 411, 412, 413, 414, 415, 416, 417, 418, 419, 420, ** 501, 502, 503, 504, 505, 506, 507, 508, 509, 510 ** 511, 512, 513, 514, 515, 516, 517, 518, 519, 520, ** 601, 602, 603, 604, 605, 606, 607, 608, 609, 610, ** 611, 612, 613, 614, 615, 616, 617, 618, 619, 620, ** 701, 702, 703, 704, 705, 706, 707, 708, 709, 710 ** 711, 712, 713, 714, 715, 716, 717, 718, 719, 720, ** 721, 722, 723, 724, 725, 726, 727, 728, 729, 730, ** 731, 732 ** ************************************************************************************

Summary of Changes xi

************************************************************************************ Version Date Summary of Changes ** ------- -------- ----------------------------------------------------------- ** 4.3 07/23/13 Fix problem using LSPRTYPE(num) when LSPR/RPP ** values are greaterthan approx. 46,000 which causes ** the harmonic mean calculation to be incorrect. *** Support added for 2828 (zBC12) models (156) using ** z/OS 1.13 LSPR data: ** A01, A02, A03, A04, A05, A06, B01, B02, B03, B04, B05, B06, ** C01, C02, C03, C04, C05, C06, D01, D02, D03, D04, D05, D06, ** E01, E02, E03, E04, E05, E06, F01, F02, F03, F04, F05, F06, ** G01, G02, G03, G04, G05, G06, H01, H02, H03, H04, H05, H06, ** I01, I02, I03, I04, I05, I06, J01, J02, J03, J04, J05, J06, ** K01, K02, K03, K04, K05, K06, L01, L02, L03, L04, L05, L06, ** M01, M02, M03, M04, M05, M06, N01, N02, N03, N04, N05, N06, ** O01, O02, O03, O04, O05, O06, P01, P02, P03, P04, P05, P06, ** Q01, Q02, Q03, Q04, Q05, Q06, R01, R02, R03, R04, R05, R06, ** S01, S02, S03, S04, S05, S06, T01, T02, T03, T04, T05, T06, ** U01, U02, U03, U04, U05, U06, V01, V02, V03, V04, V05, V06, ** W01, W02, W03, W04, W05, W06, X01, X02, X03, X04, X05, X06, ** Y01, Y02, Y03, Y04, Y05, Y06, Z01, Z02, Z03, Z04, Z05, Z06 *** Note: Capacity values didn′ t change for all existing models ** ************************************************************************************

Summary of Changes xii

Introduction

This document describes an MVS host based tool that will analyze a customer′s SMF data and producereports showing how long batch jobs run on current systems and an estimate of how long they would runon other systems.It is specifically intended to help answer the following questions:

1. What jobs are good candidates for running on a given processor?

2. How much would jobs benefit from running on a faster processor?

3. What overall change in elapsed time might there be for jobs within an existing critical path?

The tool is a batch job ′quicksizer′ that will produce ballpark estimates of what the run time delta would bewhen running on various processors.

In addition, there is a basic critical path analysis function available, to estimate the delta change in the startand end times for each job in the critical path, together with a summarized delta for the entire critical jobstream. This requires the user to provide a description of the critical path via user parameters.

The tool was designed with the intent that it could be run in a customer′s shop and the results understoodwithout consulting IBM performance experts.

Introduction xiii

Contents

Methodology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Elapsed Time Projection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Relative Processor Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Installing the Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Obtaining the Tool from the Intranet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Obtaining the Tool from PartnerInfo (PartnerWorld) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Obtaining the Tool from VM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Uploading Files to the MVS Host System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Loading BWATOOL.ULIB into BWATOOL.LOADLIB . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Preparing to Run the Analysis Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8SMF Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8User Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Parameters for Describing Base and Target Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Parameters for Filtering SMF Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Parameters for Specifying Report Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Parameters for Critical Path Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Rules for Coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Parameter Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Required Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Running On A Partitioned Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Physically Partitioned . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Logically Partitioned . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Using LSPR Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Adjusting for LPAR Overhead - Supplying RPP Values . . . . . . . . . . . . . . . . . . . . . . . . 20BASEMODEL and TARGETMODEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20BASEBUSY and TARGETBUSY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20BASE#LCP and TARGET#LCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Estimating TARGETBUSY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22When the Target System is More Than 1 CEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Suggestions for Running the Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Suggested Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Suggested Sort Sequences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Determining Job Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Jobs Whose Run Time Will Be Most Affected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Interested in Specific Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Estimating Batch Window Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

JCL Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26JCL Modifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28STEP1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28STEP3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

STEP5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Contents xiv

Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Job and Step Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Critical Path Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Job Time Line Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

How to Read This Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Job Information Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Sorting Reports in Different Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Appendix A. Machines Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Appendix B. Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47End of Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Contents xv

Methodology

There are two inputs to the Batch Workload Analysis Tool.

1. SMF data

Record type 30, subtypes 4 and 5 must be collected.

Record type 70 should be collected for the same timeframe as the type 30 records.

2. User Parameters.

See “User Parameters” on page 8 for a description of these parameters.

SMF type 30 records that meet the criteria specified in the user parameters are selected. The following cri-teria can be specified by the user to control the selection process:

1. A system identifier.

2. A time range.

3. A date range

4. Performance group number(s).

5. Job name(s).

6. Program name(s).

7. Job class(es)

8. Minimum and maximum elapsed time.

9. Minimum and maximum elapsed time delta.

Jobs/steps that are selected from the SMF file will be included in the final report that shows how muchelapsed time the job/step used on the base system and the projected elapsed time if it were run on the targetsystem.

Elapsed Time Projection

Elapsed time consists of 3 basic components:

1. CPU time

The base system′s Relative Processor Performance (RPP) number and the target system′s RPP numberare normalized to uni-processor values. The ratio of these normalized performance numbers is used tomultiply the measured CPU time to get a projected CPU time. The difference between the projectedCPU time and the measured CPU time is added to the measured elapsed time. See “Relative ProcessorPerformance” on page 3 for more detail about RPP.

2. Queue time

This is processor queue time, not the time that a job is sitting on an input queue waiting for an initiator.

The queue time is estimated based on the number of processors and CPU percent busy as documentedin Empirical Models of Processor Response Times by J. B. Major from CMG Transactions Winter 1988.Since processor utilization is the most important factor in estimating queue time, be as accurate as youcan when specifying the utilization of the base and target systems.

To eliminate queue time from the estimate, code a value for BASEBUSY and TARGETBUSY that is60% or less.

Methodology 1

3. I/O time

I/O time is assumed to be the same on both the base and target systems.

The projected elapsed time is calculated as follows:

PROJECTED CPU TIME = MEASURED CPU TIME x (BASE RPP/TARGET RPP)

PROJECTED ELAPSED TIME = MEASURED ELAPSED TIME+ PROJECTED CPU TIME - MEASURED CPU TIME+/- QUEUE TIME DELTA

This tool does not do a detailed analysis of other factors such as storage utilization, I/O device utilization,etc. For a more detailed analysis of the batch workload, tools like PMIO and SNAP/SHOT® should beused.

Methodology 2

Relative Processor Performance

The number used as a multiplier to transform the measured CPU time to the projected CPU time is derivedfrom the Relative Processor Performance (RPP) numbers for the base and target processors. For themachines found in Appendix A, “Machines Supported” on page 45, the RPP is automatically calculated bythe tool by using the Large System Performance Reference (LSPR) value for the following workloads:

• CB84

CB84 is a commercial batch workload. The work done by these jobs includes various combinations ofcompile, link-edit, and execute steps. Utility jobs, primarily for data manipulation, are also included.Assembler H, COBOL/VS, PL/I Optimizing Compiler, and DFSORT software is also used by thejobstream. Access methods include BSAM, QSAM, BDAM, and VSAM.

LSPR values for the CB84 workload will be not be used unless the user inputs the LSPRTYPE(CB84)parameter.

The CB84 LSPR workload was renamed to CB-S in the z/OS 1.4 LSPR data.

The CB84 (CB-S) LSPR workload is not supported in the z/OS 1.11 LSPR tables. Therefore, the Avg-High LSPR workload category has been assigned to replace CB84, representing I/O intensive batch.

• CBW2

CBW2 is a commercial batch workload beginning with MVS/SP 4.2.2 measurements. The workload ismore resource intensive than jobs in the CB84 workload, uses more current software, and exploits ESAfeatures. The work done by these jobs includes various combinations of C, COBOL, FORTRAN, andPL/I compile, link-edit, and execute steps. Sorting, DFSMS utilities, VSAM and DB2 utilities, SQLprocessing, SLR processing, graphics, and FORTRAN engineering/scientific subroutine library proc-essing are also included. Access methods include DB2, VSAM, and QSAM.

The LSPR values for the CBW2 workload will be used by default or when the user inputs theLSPRTYPE(CBW2) parameter.

The CBW2 LSPR workload was renamed to CB-L in the z/OS 1.4 LSPR data.

The CBW2 (CB-L) LSPR workload is not supported in the z/OS 1.11 LSPR tables. Therefore, theLow-Avg LSPR workload category has been assigned to replace CBW2, representing CPU intensivebatch.

These LSPR values use a 9672/R15 as a reference point.

The LSPR values are normalized to a uni-processor, for example.

Base processor = 3090/300J, which is a 3-way with LSPR value of 1.34Normalized LSPR value = 1.34/3 = 0.45

Target processor = 9672/R61, which is a 6-way with LSPR value of 1.38Normalized LSPR value = 1.38/6 = 0.23

For other machines, you will have to supply the RPP values via the BASERPP and TARGETRPP parame-ters. You can use whatever values you would like from whatever sources you have. Some example sourcesare LSPRPC, RELPERF, and CRIPS on MKTTOOLS and Large Systems Performance Reference, Docu-ment Number SC28-1187. The ratio of the numbers, not the meaning of the numbers, is what is important.However, LSPR values should be used if known since they are the most accurate numbers for specific typesof work.

When you supply RPP values, use the values for the system, not the uni-processor normalized value. The toolwill calculate the normalized value.

Methodology 3

Figure 1. Job Flow

Methodology 4

Installing the Tool

There are three alternatives to obtaining the MVS host based tool called BWATOOL. You should use theone that is appropriate for you.

Obtaining the Tool from the Intranet

IBM employees can obtain the BWATOOL and BWATOOL User′s Guide via the intranet site:

• http://w3-1.ibm.com/support/americas/wsc/cpsproducts.html

• find BWATOOL from the list

• click on download button to obtain a self-extracting zip file named bwatool.exe

• click on documentation to obtain the user′s guide in PDF format

Reference the section in this document titled ″Uploading Files to the MVS Host System″ to continue theinstall.

To be notified of BWATOOL′s updates, subscribe to INEWS Category called TECHSUP on the intranetsite.

Obtaining the Tool from PartnerInfo (PartnerWorld)

IBM Business Partners can obtain the BWATOOL and BWATOOL User′s Guide via the PartnerInfosystem:

1. Access Netscape and type url http://www-1.ibm.com/partnerworld/sales/systems/

2. Sign on to PartnerWorld with id and password

3. Select GEO

4. Goto the left hand NAV bar

5. Select Servers

6. Select zSeries

7. Select Selling Resources

8. Select Technical Tools

9. Search on BWATOOL

Reference the section in this document titled ″Uploading Files to the MVS Host System″ to continue theinstall.

To be notified of BWATOOL′s updates, subscribe to IBM North America Channel News.

Installing the Tool 5

Obtaining the Tool from VM

IBM employees can obtain the BWATOOL and BWATOOL User′s Guide via the VM system by usingeither VM command:

• OMNIDISK CPSTOOLS GET BWATOOL PACKAGE

• TOOLS SENDTO WSCVM TOOLS CPSTOOLS GET BWATOOL PACKAGE

The files will be sent to your reader after issuing the VM command. The files you will use are:

• BWATOOL DOC (tool description and change history)

• BWATOOL TERS3820 (user′s guide)

• BWATOOL PDFBIN (users′s guide in PDF format)

• BWATOOL JCL (sample jcl)

• BWATOOL ULIB (untersed load module)

Send the files named BWATOOL ULIB and BWATOOL JCL to the MVS host system using sendfile. Usethe TSO receive command to receive the files into datasets named BWATOOL.ULIB and BWATOOL.JCL.

Remember to modify the JCL (job card) to conform to the local installation standards and point to thecorrect SMF dataset before running the tool.

Reference the section in this document titled ″Loading BWATOOL.ULIB into BWATOOL.LOADLIB″ tocontinue the install.

To be notified of BWATOOL′s updates, subscribe to the tool on VM.

Uploading Files to the MVS Host System

The following information provides instructions on uploading the BWATOOL files (obtained via theintranet or PartnerInfo System) to the MVS host system.

To upload files to the VS system after downloading file bwatool.exe, do the following:

1. Execute bwatool.exe to expand the file on your PC. There will be four files:

a. bwatool.doc (summary description and change history)

b. bwatool.jcl (sample jcl)

c. bwatool.lib (untersed load module)

d. bwatool.pkg (package file)

2. Upload bwatool.lib to an MVS dataset named BWATOOL.ULIB as binary. The RECFM MUST beFB and the LRECL MUST be 80 when doing the upload.

3. Upload bwatool.jcl to an MVS dataset named BWATOOL.JCL as text. The RECFM MUST be FBand the LRECL MUST be 80 when doing the upload.

4. Remember to modify the JCL (job card) to conform to the local installation standards and point to thecorrect SMF dataset before running the tool.

Reference the section in this document titled ″Loading BWATOOL.ULIB into BWATOOL.LOADLIB″ tocontinue the install.


Loading BWATOOL.ULIB into BWATOOL.LOADLIB

BWATOOL.ULIB is a sequential data set and BWATOOL.LOADLIB is a Partitioned Data Set (PDS).The follow steps describe what must be done to create BWATOOL.LOADLIB from BWATOOL.ULIB:

1. Allocate BWATOOL.LOADLIB as a PDS.

The PDS should be defined as follows.

• Record Format = U

• Record Length = 0

• Block size = 32720

• Directory blocks = 1

• Primary allocation = 1 cylinder

• Secondary allocation = 1 cylinder

2. Enter the following TSO command:

• RECEIVE INDSNAME(BWATOOL.ULIB)

3. Reply to the ″Enter restore parameters″ prompt as follows:

• DA(BWATOOL.LOADLIB)

BWATOOL.LOADLIB will contain 3 members

1. BWATRMF

2. BWATRPT1

3. BWATSMF1


Preparing to Run the Analysis Tool

In order to analyze the workload, the following must be done before running the tool:

1. Dump SMF data

2. Code the user parameters

If you do not have access to an MVS system, the S/390 Parallel Center has two TSO accounts that you mayuse. The SMF data would have to be sent to the S/390 Parallel Center and would then be copied to disksthat would be accessible from these TSO accounts so that you could then run the tool. For further informa-tion about this option, contact the owner of this document.

SMF Data

SMF data should be collected for a period of time that is representative of the work to be analyzed. Thiscould be several days of data or several hours.

The following SMF data should be collected.

1. Record type 30

The following type 30 subtypes must be collected.

a. Subtype 4

Contains resources used by a job step.

b. Subtype 5

Contains resources used by a job.

2. Record type 70

This data is optional but should be used if available. Type 70 data will be used to calculate system utili-zation and is much more accurate than using the BASEBUSY parameter.

The SMF data may contain other record types.

User Parameters

User parameters are used to provide necessary information to the analysis tool and to provide optional infor-mation that will tailor the workload selection to the user′s needs.

Parameters are entered after the //SYSIN DD * statement in the JCL.

Comments

You can code a parameter as a comment by putting * in column 1.

* THIS IS A COMMENT

Preparing to Run the Analysis Tool 8

Parameters for Describing Base and Target Systems

Parameter Description

BASEMACH(x) This parameter identifies the machine type on which the SMF workload measure-ment data was collected. This input is mandatory if BASERPP is not entered. IfBASERPP is entered, the machine type indicated by BASEMACH will appear inthe report heading but the BASERPP value will be used in calculations. IfBASERPP is not entered, the machine must be one of those found in the table inAppendix A, “Machines Supported” on page 45.

BASEMODEL(x) This identifies the model of the machine type on which the SMF workload meas-urement data was collected. This input is mandatory if BASEMACH is entered. IfBASERPP is not entered, the model must be one of those found in the table inAppendix A, “Machines Supported” on page 45. For physically or logically parti-tioned systems, see “Running On A Partitioned Machine” on page 20.

TARGETMACH(x) This parameter identifies the target machine type for which the run times will beprojected. If neither TARGETMACH nor TARGETRPP are entered, the targetmachine defaults to a 9672. If TARGETRPP is entered, the machine type indi-cated by TARGETMACH will appear in the report heading but theTARGETRPP value will be used in calculations. If TARGETMACH is enteredwithout TARGETRPP, the machine type must be one of those found in the tablein Appendix A, “Machines Supported” on page 45.

TARGETMODEL(x) This identifies the model of the target machine for which the run times will beprojected. If TARGETMACH is entered, this parameter must be entered. IfTARGETRPP is not entered, the model must be one of those found in the tablein Appendix A, “Machines Supported” on page 45. For physically or logicallypartitioned systems, see “Running On A Partitioned Machine” on page 20.

BASERPP(n) This is the RPP for the system on which the SMF workload measurement datawas collected. Do not normalize this value to a uni-processor. The tool will calculatethe normalized value. You may code a decimal point and 2 digits to the right of thedecimal point. A maximum of 5 digits may be entered witout a decimal point or 4digits with a decimal point. The following are examples of valid ways to code thisparameter.

BASERPP(23.52)BASERPP(42)BASERPP(42.0)

This parameter must be used in conjunction with TARGETRPP but should notbe used if both the base and target systems appear in the table in Appendix A,“Machines Supported” on page 45. See “Relative Processor Performance” onpage 3 for details.

TARGETRPP(n) This is the RPP for the target system for which the run times will be projected. Donot normalize this value to a uni-processor. The tool will calculate the normalizedvalue. This parameter must be entered if BASERPP is entered and follows thesame rules for decimal points as BASERPP. It should not be used if both the baseand target systems appear in the table in Appendix A, “Machines Supported” onpage 45. See “Relative Processor Performance” on page 3 for details.

BASE#CP(n) This is the number of processors being used on the base system. If all theprocessors are being used and the machine is one of those found in the table inAppendix A, “Machines Supported” on page 45, this parameter does not have tobe entered. For other machines, this parameter is mandatory.


TARGET#CP(n) This is the number of processors being used on the target system. If all theprocessors are being used and the machine is one of those found in the table inAppendix A, “Machines Supported” on page 45, this parameter does not have tobe entered. For a 9672, the default is 6 processors unless overridden by this param-eter.

BASE#LCP(n) This is the number of logical processors assigned to an LPAR on the base system.

TARGET#LCP(n) This is the number of logical processors assigned to an LPAR on the target system.

BASEBUSY(n) This is the percent busy for the base system, where n can be any number less thanor equal to 100. This parameter must be entered if SMF type 70 records are notbeing used to calculate system utilization. This parameter effects the queue timeestimation so be as accurate as you can. To eliminate queue time for the basesystem from estimated elapsed time delta, code a value of 60 or less forBASEBUSY. If the analysis is for batch jobs that run as high priority jobs, use avalue of 60 or less so that queue time is not included in the estimated elapsed timedelta.

TARGETBUSY(n) This is the percent busy for the target system, where n can be any number less thanor equal to 100. The default is to use the same value as BASEBUSY or the samevalue that is calculated for the base system using type 70 records. An alternative isto code USEBUSYRATIO(YES) which will cause TARGETBUSY to be calcu-lated in relation to the base system utilization using the ratios of the base and targetsystem capacities or using a percentage of the base system utilization by specifyinga value for BUSYRATIO. This parameter effects the queue time estimation so beas accurate as you can if you enter the TARGETBUSY parameter. To eliminatequeue time for the target system from the estimated elapsed time delta, code avalue of 60 or less for TARGETBUSY. If the analysis is for batch jobs that run ashigh priority jobs, use a value of 60 or less so that queue time is not included in theestimated elapsed time delta. See “Estimating TARGETBUSY” on page 22 for adiscussion of how to estimate this parameter.

LSPRTYPE(x) Enter this parameter where x = CB84, CBW2, or a whole number in the rangestarting with zero (0) and ending with one hundred (100). Specifying CB84 willcause the LSPR values for a CB84 workload to be used. CBW2 gives you theLSPR values for a CBW2 workload. Specifying a whole number will give you amixed CB84/CBW2 workload where the number represents the CB84 weightingfactor. For example, LSPRTYPE(80) will give you LSPR values for a mixed work-load where 80% of the workload is CB84 and the remaining 20% is CBW2. Thecalculated LSPR value is based on a harmonic mean calculation.

If this parameter is not entered, the default will be to use the CBW2 LSPR values.

This parameter is not used for machines that are not found in the table inAppendix A, “Machines Supported” on page 45.

USEBUSYRATIO(x) This parameter controls how the target busy will be calculated in relation to thebase busy. Enter this parameter with x = YES if you want the target busy to becalculated in relation to the base busy using the ratio of the base and target systemcapacities if BUSYRATIO is not specified or using a percentage of the base systemutilization if BUSYRATIO is specified. Enter this parameter with x = NO if youwant target busy to be the same as base busy. If this parameter is not entered, thedefault is USEBUSYRATIO(NO).

If TARGETBUSY is entered, this parameter is not used.


BUSYRATIO(x) This parameter is used to specify a percentage to multiply the base system utiliza-tion by to get a target system utilization. For example, if the base system is 90%busy for some time period and a value of 80 is entered for BUSYRATIO, thetarget system would be calculated as 72% busy during this time period. Thisparameter is intended for situations in which workload is being moved from a largecapacity machine to several smaller capacity machines. For example, if work thatruns on a 9021/9X2 were evenly split between two 9672/R84s, based on LSPRratios each 9672 could expect to run at 85% of the utilization of the 9021/9X2.

This paramater must be used in conjunction with the USEBUSYRATIO parameter.


Parameters for Filtering SMF Data


SYSID(x) This is the system identifier, maximum of 4 characters, contained in the SMFrecords. This parameter is mandatory. Only those SMF records whose systemidentifier matches this parameter will be selected.

LPARNAME(x) This is the name of the logical partition to be analyzed, maximum of 8 characters,for systems that are running in LPAR mode.

STIME(hhmm) This is the beginning of a time range where hh = hours and mm = minutes in 24hour clock format. Only jobs/steps starting after this time will be selected. Thisparameter is mandatory for Critical Path Reports and when using type 70 recordsto calculate system utilization.

ETIME(hhmm) This is the end of a time range where hh = hours and mm = minutes in 24 hourclock format. Only jobs/steps starting before this time will be selected. This param-eter is mandatory for Critical Path Reports and when using type 70 records to cal-culate system utilization.

SDATE(yyddd) This is a start date where yy is the last 2 digits of the year and ddd is the day of theyear. Only jobs/steps starting on or after this date will be selected. This parameteris mandatory for Critical Path Reports and when using type 70 records to calculatesystem utilization.

EDATE(yyddd) This is an end date where yy is the last 2 digits of the year and ddd is the day ofthe year. Only jobs/steps starting on or before this date will be selected. Thisparameter is mandatory for Critical Path Reports and when using type 70 recordsto calculate system utilization.

MINDELTA(s) This is the minimum elapsed time delta in seconds. Only jobs/steps whoseprojected elapsed time differs from the current system elapsed time by more thanthis value will be selected. For example, if you entered a value of 1 for this param-eter, only jobs/steps whose projected elapsed time differed from the measuredelapsed time by more than 1 second would be selected for the report.

MAXDELTA(m) This is the maximum elapsed time delta in minutes. Only jobs/steps whoseprojected elapsed time differs from the current system elapsed time by less than thisvalue will be selected. For example, if you entered a value of 60 for this parameter,only jobs/steps whose projected elapsed time differed from the measured elapsedtime by less than 60 minutes would be selected for the report.

MINET(s) This is the minimum elapsed time in seconds. Only jobs/steps whose measuredelapsed time is greater than this value will be selected.

MAXET(m) This is the maximum elapsed time in minutes. Only jobs/steps whose measuredelapsed time is less than this value will be selected.

MINCPUTIME(s) This is the minimum CPU time in seconds. Only jobs/steps whose measured CPUtime is greater than this value will be selected.

JOBNAME(x) This identifies jobs that should be selected. A maximum of 300 of the job nameparameters may be entered. JOBNAME and CRITJOBS parameters cannot bothbe entered in the same run. You can use an asterisk(*) as a wild card as illustratedin the following examples:

JOBNAME(*XYZ) - select all jobs whose names end in XYZ.JOBNAME(ABC*) - select all jobs whose names start with ABC.JOBNAME(PAY*X2) - select all jobs whose names start with PAY and end with X2.JOBNAME(***Z3X**) - select all jobs that have Z3X in the 4th, 5th, and

6th positions of the jobname.


NOTJOBNAME(x) This identifies jobs that should not be selected. A maximum of 100 of these param-eters may be entered. The same wildcard rules used for JOBNAME apply toNOTJOBNAME.

PGROUP(n) This identifies performance groups that should be selected when running in com-patibility mode. Performance group, and service class or report class parameters,cannot be entered in the same run. A maximum of 100 performance group parame-ters may be entered.

NOTPGROUP(n) This identifies performance groups that should not be selected when running incompatibility mode. Performance group, and service class or report class parame-ters, cannot be entered in the same run. A maximum of 25 of these parametersmay be entered.

CLASS(x) This identifies job classes that should be selected. A maximum of 20 job classparameters may be entered.

NOTCLASS(x) This identifies job classes that should not be selected. A maximum of 20 of theseparameters may be entered.

JES3CLASS(x) This identifies JES3 job classes that should be selected. A maximum of 20 JES3job class parameters may be entered.

NOTJES3CLASS(x) This identifies JES3 job classes that should not be selected. A maximum of 20 ofthese parameters may be entered.

SERVCLASS(x) This identifies service classes that should be selected when running in goal mode.When used in combination with the RPTCLASS parameter, the parameters areprocessed with ′or′ logic. Jobs will be selected if in either the specified service classor in the specified report class. Service class and performance group parameterscannot be used in the same run. A maximum of 50 of these parameters may beentered.

NOTSERVCLASS(x) This identifies service classes that should not be selected when running in goalmode. When used in combination with the NOTRPTCLASS parameter, theparameters are processed with ′or′ logic. Jobs will not be selected if in either thespecified service class or in the specified report class. Service class and performancegroup parameters cannot be used in the same run. A maximum of 50 of theseparameters may be entered.

RPTCLASS(x) This identifies report classes that should be selected when running in goal mode.When used in combination with the SERVCLASS parameter, the parameters areprocessed with ′or′ logic. Jobs will be selected if in either the specified service classor in the specified report class. Report class and performance group parameterscannot be used in the same run. A maximum of 50 of these parameters may beentered.

NOTRPTCLASS(x) This identifies report classes that should not be selected when running in goalmode. When used in combination with the NOTSERVCLASS parameter, theparameters are processed with ′or′ logic. Jobs will not be selected if in either thespecified service class or in the specified report class. Report class and performancegroup parameters cannot be used in the same run. A maximum of 50 of theseparameters may be entered.

WORKTYPE(x) This identifies the type of work to be analyzed, where x can be JOBS, TASKS,TSO, or ALL. The default is ALL.

This parameter can be entered more than once. For example if you wanted JOBSand TASKS you would enter the parameter twice as follows.


WORKTYPE(JOBS)WORKTYPE(TASKS)

• JOBS

Enter this keyword to select jobs entered via the job entry subsystem.

• TASKS

Enter this keyword to select started tasks.

• TSO

Enter this keyword to select batch work entered via TSO.

• ALL

Enter this keyword to select JOBS, TASKS, and TSO. This is the default ifthe WORKTYPE parameter is not entered.

PGMNAME(x) This parameter is effective only when RPTTYPE(STEP) is specified. It identifiesprograms that should be selected. The output report contains only the steps of jobswhich execute the named program. A maximum of 25 PGMNAME(X) parametersmay be entered. You can code an asterisk(*) as the first character of a programname, the last character of a program name, or within a program name to act as awildcard. The following examples illustrate how this would work.

PGMNAME(*XYZ) - select all programs whose names end in XYZ.PGMNAME(ABC*) - select all programs whose names start with ABC.PGMNAME(PAY*X2) - select all programs whose names start with PAY and end with X2.

CHECKABEND(x) Enter this parameter where x = NO if you do not want to eliminate jobs that endabnormally. The default is YES. Jobs that end abnormally will be eliminated fromthe reports and an informational message will be printed.


Parameters for Specifying Report Contents


RPTTYPE(x) This identifies the type of report that is wanted, where x can be JOB, STEP,TIMELINE, or CRITPATH.

Only one report type will be produced in a single execution of the tool.

• JOB

A Job Analysis Report shows both actual and projected data for jobs but indi-vidual steps within the job are not shown. This is the default.

• STEP

A Step Analysis Report shows both actual and projected data for each stepwithin a job. For customers running in goal mode, service class cannot be dis-played in step reports.

• TIMELINE

A Time Line Report shows job start and end times and projected end times ona time line. The maximum time that can be shown is 12 hours and theminimum is 2 hours. Use the STIME, ETIME, SDATE, and EDATE param-eters to control the amount of time to be shown.

• CRITPATH

For dependent jobs, this report shows how the end time would change for eachjob and for the entire job path. This parameter is used in conjunction with theCRITJOBS parameter.

• INFO

This report shows general information about the jobs as they were run on thebase system.

LINES(n) This parameter specifies the number of lines per page for the reports. The defaultis 64 lines per page.

CUSTNAME(x) This identifies the customer and will appear in the report if entered. A maximum of60 characters is allowed.

JES3(x) Enter this parameter where x = YES if you want JES3 job classes displayed in theJob Report. The default is NO. This parameter is ignored if a Step Report isrequested. For customers running in goal mode, the service classes cannot be dis-played in the reports if the JES3 job classes are displayed.


Parameters for Critical Path Analysis

The following parameter is used to describe the job dependencies to be included in the report when the usercodes RPTTYPE(CRITPATH).


CRITJOBS(a>b,c,d,e,f,g,h,i,j,k) Enter this to identify jobs in the critical path to be analyzed. Themaximum number of jobs in the critical path report is 300.CRITJOBS and JOBNAME parameters cannot both be entered inthe in the same run.

For the critical path shown in Figure 2 on page 17 the parameterswould be coded as follows..

CRITJOBS(JOBA>JOBB,JOBC)CRITJOBS(JOBB>JOBD)CRITJOBS(JOBC>JOBE,JOBF)CRITJOBS(JOBD>JOBG)CRITJOBS(JOBE>JOBG,JOBH)CRITJOBS(JOBF>JOBJ)CRITJOBS(JOBG>JOBI)CRITJOBS(JOBH>JOBJ)CRITJOBS(JOBI>JOBK)CRITJOBS(JOBJ>JOBK)

Definitions

Predecessor Job A job that must complete before other job(s) can start. From the example criticalpath shown in Figure 2 on page 17. JOBA is a predecessor to JOBB and JOBC.

Successor Job A job that cannot start until other job(s) have completed. From the example criticalpath shown in Figure 2 on page 17. JOBB and JOBC are successors to JOBA.

Rules for Coding

• The same jobname may not be in the critical path more than once.

The following error message will be displayed if a jobname runs more than once during the time periodbeing analyzed.

ERROR: CRIT PATH JOB xxxxxxxx RAN MORE THAN ONCE

If the same jobname runs in the critical path multiple times, you have 3 options

1. If it is a very short running job, omit it from the path definition.

2. If the job runs long enough to have a significant impact on the critical path, break up the analysisinto several paths where the same jobname will appear only once in the path being analyzed.

3. Use the NAMECHANGE parameter to alter the name of the job.

• A predecessor job is separated from its successor jobs by a greater than(>) sign.

• If there is more than one successor job, separate the successor jobs by commas(,).

• If all the successor jobs will not fit on one line, you can continue by repeating the parameter with thepredecessor job and the successor jobs that would not fit on the previous line.

For example, if jobs JOB00001 through JOB00010 are successors to JOB00000, you could code theparameters as follows.

CRITJOBS(JOB00000>JOB00001,JOB00002,JOB00003,JOB00004,JOB00005,JOB00006,JOB00007,JOB00008)CRITJOBS(JOB00000>JOB00009,JOB00010)


• A job may not have more than 15 predecessor jobs.

• The maximum total number of jobs in the critical path is 300.

Note: SDATE, EDATE, STIME, and ETIME parameters must be provided to limit the time period for thecritical path.

Note: Jobs that are part of the critical path often run at higher priority than other batch jobs and thereforewill not experience significant CPU queueing delays. Ask the customer if their critical path jobs run at higherpriority than their other batch work and if so use a value of 60 or less for BASEBUSY and TARGETBUSYeven though the actual utilization of the system may be greater than this.

Figure 2. Critical Path Diagram



NAMECHANGE(OLDNAME=xxxxxxxx,STARTTIME=hh:mm:ss,NEWNAME=zzzzzzzz) To changejob name in SMF data.

Use this parameter to work around the problem of having duplicate job names in the critical path, wherexxxxxxxx is the job name as it exists in the SMF data, hh:mm:ss is the start time of the job, and zzzzzzzz isthe new job name to replace the old job name with.

The following example will illustrate how to use this parameter.

Job ABCD started at 18:20:35 and must complete before job EFGH which started at 19:01:12 .

Job ABCD ran again at 20:17:39 and must complete before job EFGH which started at 20:49:18 .

Use the NAMECHANGE parameter to change one of the sets of duplicate jobnames as follows:

NAMECHANGE(OLDNAME=ABCD,STARTTIME=20:17:39,NEWNAME=ABCD2)NAMECHANGE(OLDNAME=EFGH,STARTTIME=20:49:18,NEWNAME=EFGH2)

You could then code the CRITJOBS parameters as follows:

CRITJOBS(ABCD>EFGH)CRITJOBS(ABCD2>EFGH2)

Parameter Defaults

If no values are entered for the following parameters the indicated default values will be used.

Parameter Default Value

TARGETMACH 9672

TARGETMODEL R61

TARGETBUSY BASEBUSY

STIME 0000

ETIME 2400

SDATE 01001

EDATE 99365

RPTTYPE JOB

LINES 64

JES3 NO

WORKTYPE ALL

LSPRTYPE CBW2

CHECKABEND NO for RPTTYPE(INFO). YES for all otherreport types

USEBUSYRATIO NO


Required Parameters

The following parameters are required in the situations described in the table:

Parameter When Required

SYSID Always

LPARNAME When the system to be analyzed is running inLPAR mode and type 70 records are being usedto calculate system utilization.

STIME Always required for CRITPATH andTIMELINE reports.

ETIME Always required for CRITPATH andTIMELINE reports.

SDATE Always required for CRITPATH reports.Required for all reports when type 70 records areused for system utilization.

EDATE Always required for CRITPATH reports.Required for all reports when type 70 records areused for system utilization.

BASEMACH & BASEMODEL Required when BASERPP is not entered. IfBASERPP is not entered, BASEMACH &BASEMODEL must be one of the systems listedin Appendix A, “Machines Supported” onpage 45.

BASERPP Required when the base system or the targetsystem is not one of systems listed inAppendix A, “Machines Supported” on page 45.

BASE#CP Required when BASERPP is entered.

BASEBUSY Required when type 70 records are not being usedto calculate system utilization.

TARGETMACH & TARGETMODEL Required when TARGETRPP is not entered. IfTARGETRPP is not entered TARGETMACH& TARGETMODEL must be one of the systemslisted in Appendix A, “Machines Supported” onpage 45.

TARGETRPP Required when the base system or the targetsystem is not one of systems listed inAppendix A, “Machines Supported” on page 45.

TARGET#CP Required when TARGETRPP is entered.


Running On A Partitioned Machine

Physically Partitioned

Use the BASEMODEL or TARGETMODEL that best describes the number of processors that were in thepartition. For example, if you are running on one side of a 9021 model 982, use 941 for the BASEMODEL.

Logically Partitioned

There are two approaches to selecting a relative performance value for an LPAR.

Using LSPR Defaults

For systems contained in Appendix A, “Machines Supported” on page 45, LSPR defaults will be used if noRPP values are supplied by the user. These LSPR values do not take into account the overhead of LPAR.

Adjusting for LPAR Overhead - Supplying RPP Values

The LPAR overhead may or may not have a significant effect on the RPP value. It can only be determinedby running LPARCE. LPARCE is available on the CPSTOOLS disk at WSCVM.

The estimate of host LPAR-mode capacity/host B-mode capacity, which is displayed on the LPARCE′Input and Summary Panel′, should be multiplied by the basic mode system RPP value to get an RPP valuethat reflects LPAR overhead.

Base System

• Run LPARCE for the base system.

• Multiply RPP times LPAR-mode capacity/B-mode capacity and use the result for BASERPP.

Target System: If you are going to run the work on the target system in logical partitions, do the following:

• Run LPARCE for the target system.

• Multiply RPP times LPAR-mode capacity/B-mode capacity and use the result for TARGETRPP.

If you are going to run the work on the target system in basic mode, do the following:

• For TARGETRPP, use the unadjusted basic mode RPP value.

BASEMODEL and TARGETMODEL

• Use the BASEMODEL that corresponds to the number of physical processors on the system. If runningLPAR in a physically partitioned system, use the model that corresponds to the number of physicalprocessors on one side of the system.

• Use the TARGETMODEL that corresponds to the number of physical processors on the system.

BASEBUSY and TARGETBUSY

You can let BWATOOL calculate these values or you can do it manually.


Using SMF Type 70 Records: If you have type 70 records, you should let BWATOOL calculate the systemutilization. System utilization may vary significantly during the time period being analyzed. By using the datain the type 70 records, BWATOOL will use the system utilization at the time that each job was runningrather than one value for all jobs.

Note: If you are analyzing batch jobs that run as high priority work, use a BASEBUSY value of 60 insteadof using type 70 records.

Mannually Calculating System Utilization

• For BASEBUSY, do the following.

Look at the IN READY data in an RMF CPU Activity Report for the LPAR being analyzed andcompare the IN READY AVG to the number of logical processors(#LCP) assigned to the LPAR.

If the IN READY AVG <= #LCP, use a value of 60 for BASEBUSY.

If the IN READY AVG > #LCP and < #LCP + 2, use a value from 65 to 75 for BASEBUSY.

If the IN READY AVG >= #LCP + 2 and < #LCP + 5, use a value from 75 to 85 forBASEBUSY.

If the IN READY AVG >= #LCP + 5, use a value from 85 to 95 for BASEBUSY.

• For TARGETBUSY, use the total system utilization if running in basic mode or use the same value asBASEBUSY if running in LPAR mode.

BASE#LCP and TARGET#LCP

• For BASE#LCP, use the number of logical processors assigned to the LPAR. You can omit this param-eter if you are using type 70 records to calculate system utilization.

• For TARGET#LCP, use the number of logical processors assigned to the LPAR or omit this parameterif running in basic mode.


Estimating TARGETBUSY

The basic equation used in these examples is as follows:

TARGETBUSY = BASEBUSY * (BASERPP/TARGETRPP)

The following example uses a 9021/740 as base system, a 9672/R61 as a target system, and the LSPR valuesfor these systems as the RPP values. In this example we want to see if we could move workload that uses30% of the base system to a 9672 R61.

TARGETBUSY = 30% * (2.75/1.38) = 60%

From these calculations, we can see that the workload that was using 30% of the 9021/740 would use 60%of the 9672/R61.

Suppose we wanted to run work from the base system on some target system whose utilization would notexceed a given value. In order to determine what target system will meet our needs, we must calculate theRPP value for the target system. Since we know the RPP for the base system, the utilization for the basesystem, and the utilization of the target system, reworking our basic equation would provide the RPP valuefor the target system as follows:

TARGETRPP = (BASERPP * BASEBUSY)/TARGETBUSY

If we used LSPR values for RPP, we could look up this number in LSPR tables to find what processorswould meet our needs.

When the Target System is More Than 1 CEC

In situations where the workload from the base system will be migrated to more than 1 Central ElectronicComplex(CEC), the tool must be run for each CEC unless each CEC has the same RPP value and sameutilization. For example, if the customer is migrating work to a 9672 E02 that has 6 CPUs on one CEC and4 CPUs on the other the tool would be run twice. The first time the following parameters would be used. Inthis case the user determined that enough work would be migrated to the CEC with 6 CPUs to run it at 90percent busy.

• TARGETMACH(9672)

• TARGETMODEL(R61)

• TARGETBUSY(90)

The tool would then be run a second time with the following parameters. In this case the user determinedthat enough work would be migrated to the CEC with 4 CPUs to run it at 80 percent busy.

• TARGETMACH(9672)

• TARGETMODEL(R41)

• TARGETBUSY(80)


Suggestions for Running the Tool

With a judicious selection of parameters and by sorting the reports in the most effective sequence, the usercan focus on the jobs that are of most interest. The following suggestions should help you decide whatparameters and what sort sequences to use.

Suggested Parameters

The parameters that you use will usually depend on how much you already know about the batch workloadand how much you want to narrow down the analysis. In most cases you will probably be interested inspecific time periods and/or specific jobs. The following parameters will be the most useful.

• STIME and ETIME

Use these parameters to focus the analysis on the time period that you consider critical. For example, ifyou want to focus on jobs that run between 8:00 PM and 6:00 AM, you would code these parameters asSTIME(2000) and ETIME(0600).

• SDATE and EDATE

Use these parameters to focus the analysis on a specific day or days.

• JOBNAME

Use this parameter if you have specific jobs that you want to analyze. This parameter can be entered upto 300 times, but you can analyze more than 300 jobs by including * within the job names as awildcard.

• PGROUP

Use this parameter to limit the analysis to specific performance groups.

• CLASS and JES3CLASS

Use this parameter to limit the analysis to specific job classes.

• RPTTYPE

The first time you run the analysis tool, you will probably want the Job Report. This is the default andyou do not have to code this parameter if that is what you want. This will produce an analysis at the joblevel of granularity.

If you want to produce a report at a job step level of granularity, code this parameter asRPTTYPE(STEP). If you request a Step Report, it is recommended that you also code the JOBNAMEand PGMNAME parameters to reduce the size of the output.

If you want to produce a job time line report, code this parameter as RPTTYPE(TIMELINE).

If you can define the jobs in the critical path, you can create a report showing the effects of job depend-encies by coding this parameters as RPTTYPE(CRITPATH).


Suggested Sort Sequences

As with the user parameters, the way you choose to sort the reports depends on how much you alreadyknow about the batch workload. The following sort sequences will probably be most useful, but there maybe situations where other sequences will provide better information. See “Sorting Reports in DifferentOrder” on page 44 for information on how to sort in other sequences.

The SORT control statements that follow are placed after the //SYSIN DD * statement in STEP4 in theJCL example shown in “JCL Requirements” on page 26.

Determining Job Flow

If you don′t know what your job flow is you should sort by date and time. This would show you thesequence in which the jobs ran.

The SORT control statement to sort by date and time is:

SORT FIELDS=(25,4,PD,A,29,4,BI,A)

Requesting a Job Time Line Report may also help you visualize how jobs flow.

For a Critical Path Report, you must sort the records by date and time.

Jobs Whose Run Time Will Be Most Affected

By sorting in order of elapsed time delta, the jobs will be reported in order from most effected job to leasteffected, or vice versa if you sort in ascending order.

The SORT control statement to sort by elapsed time delta in descending sequence is:

SORT FIELDS=(49,4,FI,D)

Interested in Specific Jobs

If the report will contain many different jobs, it will be easier to find specific jobs if you sort in job namesequence.

The SORT control statement to sort by job name is:

SORT FIELDS=(3,8,CH,A)

Some jobs may appear numerous times within a report. To sort by date and time within jobname, theSORT control statement would be coded as:

SORT FIELDS=(3,8,CH,A,25,4,PD,A,29,4,BI,A)


Estimating Batch Window Changes

If you know the jobs in the critical path and the order that they must run, the Critical Path Report is thebest method.

If you do not know the jobs in the critical path, by using the average percent delta a rough estimate of theeffect on the batch window could be calculated as follows:

• Find the line in the Job Report that starts with the word TOTALS.

This line will be at the end of the detail data section of the report, before the bar graphs.

− Multiply the PERCENT DELTA from this line times the current batch window time to get an esti-mate of the change to the batch window.

For example, if the PERCENT DELTA were +10% and the batch windowcurrently takes 12 hours to complete, the estimated batch windowchange would be 12 x 10% = +1.2 hours.

This estimate will be more accurate if the STIME and ETIME parameters are used to limit theanalysis to the time period of the current batch window and if JOBNAME parameters are used toeliminate as many jobs as possible that are not part of the batch window.


JCL Requirements

The following is a sample JCL for running the tool.

Note: Please note that STEP1 and STEP2 are new beginning with version 2.0. The type 70 records may bein the same file that contains the type 30 records.

//BWATJOB1 JOB MSGLEVEL=(1,1),CLASS=A//JOBLIB DD DSN=BWATOOL.LOADLIB,DISP=SHR//* ****************************//* SELECT TYPE 70 SMF RECORDS *//* ****************************//STEP1 EXEC PGM=BWATRMF//TYPE70 DD DSN=SMF.DATA,DISP=(OLD,KEEP)//SYSBUSY DD DSN=&SYSBUSY,DISP=(NEW,PASS),// UNIT=SYSDA,SPACE=(CYL,(2,1)),// DCB=(RECFM=FB,LRECL=46)//SYSUDUMP DD SYSOUT=*//* **********************//* SORT TYPE 70 RECORDS *//* **********************//STEP2 EXEC PGM=SORT,COND=(0,NE),REGION=6144K//SORTIN DD DSN=&SYSBUSY,DISP=(OLD,PASS)//SORTOUT DD DSN=&SORTBSY,DISP=(NEW,PASS),// UNIT=SYSDA,SPACE=(CYL,(2,1)),// DCB=(RECFM=FB,LRECL=46)//SYSPRINT DD SYSOUT=*//SYSOUT DD SYSOUT=*//SORTWK01 DD UNIT=SORTWK,SPACE=(CYL,(4))//SORTWK02 DD UNIT=SORTWK,SPACE=(CYL,(4))//SORTWK03 DD UNIT=SORTWK,SPACE=(CYL,(4))//SORTWK04 DD UNIT=SORTWK,SPACE=(CYL,(4))//SORTWK05 DD UNIT=SORTWK,SPACE=(CYL,(4))//SORTWK06 DD UNIT=SORTWK,SPACE=(CYL,(4))//SYSIN DD *

SORT FIELDS=(1,11,CH,A)/*

JCL Requirements 26

//* ****************************//* SELECT TYPE 30 SMF RECORDS *//* ****************************//STEP3 EXEC PGM=BWATSMF1//* ************************//* SYSUT1 IS THE SMF DATA *//* ************************//SYSUT1 DD DSN=SMF.DATA,DISP=(OLD,KEEP)//SYSUT2 DD DSN=&RPTDATA,UNIT=SYSDA,DISP=(NEW,PASS),// SPACE=(CYL,(10,5))//SYSUT3 DD DSN=&PARMS1,UNIT=SYSDA,DISP=(NEW,PASS),SPACE=(TRK,(1))//SYSUT4 DD DSN=&PARMS2,UNIT=SYSDA,DISP=(NEW,PASS),SPACE=(TRK,(1))//SYSUT5 DD DSN=&CRITPTH,UNIT=SYSDA,DISP=(NEW,PASS),SPACE=(TRK((1))//SYSBUSY DD DSN=&SORTBSY,DISP=(OLD,PASS)//* ******************************//* SYSPRINT IS THE ERROR REPORT *//* ******************************//SYSPRINT DD SYSOUT=*//SYSUDUMP DD SYSOUT=*//* ***********************************//* PLACE USER PARAMETERS AFTER SYSIN *//* ***********************************//SYSIN DD */*//* *********************************************************************//* SORT THE REPORT DATA - this is an example of sorting by date & time *//* *********************************************************************//STEP4 EXEC PGM=SORT,REGION=6144K,COND=(0,NE)//SORTLIB DD DSN=SYS1.SORTLIB,DISP=SHR//SYSPRINT DD SYSOUT=*//SYSOUT DD SYSOUT=*//SORTIN DD DSN=&RPTDATA,DISP=(OLD,PASS)//SORTOUT DD DSN=&SORTJOB,UNIT=SYSDA,DISP=(NEW,PASS),// SPACE=(CYL,(10,5))//SORTWK01 DD UNIT=SORTWK,SPACE=(CYL,(5))//SORTWK02 DD UNIT=SORTWK,SPACE=(CYL,(5))//SORTWK03 DD UNIT=SORTWK,SPACE=(CYL,(5))//SORTWK04 DD UNIT=SORTWK,SPACE=(CYL,(5))//SORTWK05 DD UNIT=SORTWK,SPACE=(CYL,(5))//SORTWK06 DD UNIT=SORTWK,SPACE=(CYL,(5))//* *******************************************//* YOU CAN CHANGE THE SEQUENCE OF THE REPORT *//* BY CHANGING THE SORT FIELDS. *//* *******************************************//SYSIN DD *

SORT FIELDS=(25,4,PD,A,29,4,BI,A)/*//* ****************//* CREATE REPORTS *//* ****************//STEP5 EXEC PGM=BWATRPT1,COND=(0,NE)//SYSUT1 DD DSN=&SORTJOB,DISP=(OLD,PASS)//SYSUT2 DD DSN=&PARMS1,DISP=(OLD,PASS)//SYSUT3 DD DSN=&PARMS2,DISP=(OLD,PASS)//SYSUT4 DD DSN=&CRITPTH,DISP=(OLD,PASS)//SYSPRINT DD SYSOUT=*,DCB=(RECFM=FBA,LRECL=133,BLKSIZE=6650)//SYSUDUMP DD SYSOUT=*

JCL Requirements 27

JCL Modifications

The job card will have to be changed to work on the customer′s system.

If you installed the tool in a PDS other than BWATOOL.LOADLIB, change the DSN on the JOBLIBstatement.

STEP1

Inputs• TYPE70

This is the dataset containing the type 70 SMF records. This can be the same dataset that contains thetype 30 records. If there are no type 70 records to be processed, you can shorten the run time by codingthe DD statement as follows:

//TYPE70 DD DUMMY

STEP3

Inputs• SYSUT1

This is the dataset containing the type 30 SMF records.

• SYSIN

The user parameters follow this statement.

Outputs• SYSPRINT

This is a report of any erroneous user parameters or errors encountered while running BWATSMF1.

STEP5

Outputs• SYSPRINT

This is the requested report.

JCL Requirements 28

Reports

There are five(5) types of reports that can be requested.

1. Job Report

Shows actual base system data and projected target system data at a job level.

2. Step Report

Shows actual base system data and projected target system data at a job step level.

3. Job Time Line Report

Shows job start and end times and projected end times on a time line.

4. Critical Path Report

For dependent jobs, this report shows how the end time would change for each job and for the entirejob path.

5. Job Information Report

Shows only base system data.

Job and Step Reports

The following information is included in both the job and step reports unless otherwise indicated.

• Performance Group Number

• Job Class

• Job Name

• Program Name

Appears only in the step report.

• Date that the job started

• Time that the job started

• Measured elapsed time

This is the elapsed time for this job as measured on the base system.

• Projected Delta

This is the estimated change in elapsed time if the job were run on the target system.

• Percent Delta

This is the estimated percentage of change in the elapsed time if the job were run on the target system.

• Measured CPU Time

This is the CPU time used by the job running on the base system.

• Projected CPU Time

This is the estimated CPU time that the job would use if it were running on the target system.

Reports 29

• Measured CPU Percent

This is the measured CPU time on the base system divided by the elapsed time on the base system. It isan indicator of how CPU intensive a job is.

• Queue Time Delta

This is an estimate of how the queue time would change if the job were run on the target system inrelation to the queue time that would have been used on the base system. It is one of the factors used tocalculate the elapsed time delta.

• Number of EXCPs

• Number of Tape Mounts

• A total line indicating the following:

− Total number of jobs

− Total elapsed time

− Total elapsed time delta

− Percent of elapsed time change

− Total CPU time for base system

− Total CPU time for target system

− Base system CPU to elapsed time ratio(percent)

− Total queue time delta

− Total number of EXCPs

• The earliest and latest start times for jobs in the report.

• The base system calculated utilization for the jobs contained in the report.

• The target system estimated utilization for the jobs contained in the report.

This can be used for simple capacity planning to get an idea of how many target systems would beneeded to run the base system workload.

• A graph showing percent of jobs grouped into categories by percent elapsed time change. See Figure 5 on page 35 for a sample graph.

The data is categorized into the following percent ranges.

− Between 0 and 10 percent








− Greater than 100 percent

Reports 30

Note: Jobs whose elapsed time increases are indicated by +++++ on the graph.

Jobs whose elpased time decreased are indicated by ----- on the graph.

A single + indicates that at least 1 job/step had an increase in this category but the percent ofjobs was too small to show up on the graph.

A single - indicates that at least 1 job/step had a decrease in this category but the percent of jobswas too small to show up on the graph.

A single + and a single - indicates that at least 1 job/step had an increase and at least onejob/step had a decrease in this category but the percent of jobs was too small to show up on thegraph.

• A graph showing percent of jobs grouped by elapsed time change. See Figure 5 on page 35 for a samplegraph.

The data is categorized into the following time ranges.

− Less than or equal to 1 minute

− Between 1 and 3 minutes







− Greater than 60 minutes

Also for each category, the total CPU time, average CPU time, and percent of CPU time as measuredon the base system and the total CPU time projected for the target system are displayed.

Note: Jobs whose elapsed time increases are indicated by +++++ on the graph.

Jobs whose elpased time decreased are indicated by ----- on the graph.

A single + indicates that at least 1 job/step had an increase in this category but the percent ofjobs was too small to show up on the graph.

A single - indicates that at least 1 job/step had a decrease in this category but the percent of jobswas too small to show up on the graph.

A single + and a single - indicates that at least 1 job/step had an increase and at least onejob/step had a decrease in this category but the percent of jobs was too small to show up on thegraph.

Reports 31

• A graph showing percent of jobs grouped by CPU utilization percent. See Figure 6 on page 36 for asample graph.

The data is categorized into the following percent ranges.







− Greater than 75 percent

Note: A single * indicates that at least 1 job/step fell into this category but the percent of jobs was toosmall to show up on the graph.

See Figure 3 on page 33, for a sample Job Report and Figure 7 on page 37 for a sample Step Report.

Reports 32

BWATRPT2 Version 2.0 - JOB ANALYSIS REPORT PAGE 0007

BASE SYSTEM: 9021/711TARGET SYSTEM: 9672/R11

J JOB PROGRAM START START MEASURED PROJECTED PERCENT MEASURED PROJECTED MEASURED Q TIME NUMBER TAPE PGN C NAME NAME DATE TIME ELAPSED DELTA DELTA CPU TIME CPU TIME CPU% DELTA EXCPS MOUNTS11 C CARP001A 94045 19:07:15 00:02:48 +00:01:00 + 35% 00:00:05 00:00:25 3% +00:00:39 905 211 C CBW2TR01 94045 19:07:06 00:00:00 +00:00:01 +120% 00:00:00 00:00:00 18% +00:00:00 1310 A COBB001A 94045 19:18:19 00:01:02 +00:02:35 +249% 00:00:38 00:02:56 61% +00:00:16 1,818 411 B COB2001A 94045 19:07:12 00:01:06 +00:01:36 +145% 00:00:17 00:01:21 26% +00:00:33 2,15511 C CPGM001A 94045 19:09:54 00:05:24 +00:08:00 +147% 00:01:27 00:06:47 27% +00:02:41 84,70911 C DB2J001A 94045 19:07:14 00:10:00 +00:03:44 + 37% 00:00:20 00:01:37 3% +00:02:28 29,69611 C DB2J001B 94045 19:08:19 00:06:54 +00:08:24 +121% 00:01:15 00:05:49 18% +00:03:50 95,16711 C DB2J001C 94045 19:15:13 00:02:15 +00:04:02 +179% 00:00:50 00:03:55 37% +00:00:57 47,83411 C DB2J001D 94045 19:07:09 00:06:52 +00:01:01 + 14% 00:00:05 00:00:26 1% +00:00:40 1,60211 B DB2J001E 94045 19:13:53 00:02:40 +00:01:09 + 42% 00:00:06 00:00:30 4% +00:00:45 1,05611 B DB2J001F 94045 19:14:02 00:01:14 +00:00:34 + 45% 00:00:03 00:00:14 4% +00:00:22 87511 C DB2J001G 94045 19:08:32 00:04:39 +00:06:11 +132% 00:01:01 00:04:44 21% +00:02:28 63,24111 C DB2J001H 94045 19:07:16 00:06:30 +00:09:23 +144% 00:01:40 00:07:46 25% +00:03:17 87,894 1011 C DPST001A 94045 19:07:10 00:02:42 +00:00:25 + 15% 00:00:02 00:00:10 1% +00:00:16 1,30111 C DPST001B 94045 19:10:04 00:02:48 +00:01:15 + 44% 00:00:07 00:00:32 4% +00:00:49 2,78711 C DPST001C 94045 19:13:11 00:02:43 +00:00:25 + 15% 00:00:02 00:00:10 1% +00:00:16 3,549 110 A INUP001A 94045 19:15:55 00:00:13 +00:00:14 +103% 00:00:01 00:00:07 11% +00:00:08 99811 C PAYR001A 94045 19:07:09 00:06:44 +00:06:38 + 98% 00:00:41 00:03:14 10% +00:04:06 19,88310 A PAYR001B 94045 19:16:16 00:01:15 +00:00:35 + 47% 00:00:03 00:00:15 4% +00:00:23 4,021********************************************************************************************************************************

TOTALS 32 JOBS 01:38:12 + 01:16:11 + 77% 00:11:16 00:52:23 11% +00:35:03 982,073

EARLIEST JOB STARTED AT 19:07:06 ON 94045 LATEST JOB STARTED AT 19:20:06 ON 94045 BASE SYSTEM CALCULATED UTILIZATION FOR SELECTED JOBS 86% TARGET SYSTEM ESTIMATED UTILIZATION FOR SELECTED JOBS 399%

Figure 3. Sample Job Report Showing 9672 Projections

Reports 33

100+||||

90+||||

80+||||

70+||||

P 60+ -----E | -----R | -----C | -----E | -----N 50+ -----T | -----

| -----O | -----F | -----

40+ -----J | -----O | -----B | +++++S | +++++

30+ +++++| +++++| +++++ -----| +++++ -----| +++++ -----

20+ +++++ -----| +++++ +++++| +++++ +++++| +++++ +++++| +++++ +++++

10+ +++++ +++++| +++++ +++++| +++++ +++++ +++++| +++++ +++++ +++++| +++++ +++++ +++++ +++++ +++++ + + + +-------------------------------------------------------------------------------------------

<=10% <=20% <=30% <=40% <=50% <=60% <=75% <=100% >100%PERCENT OF ELAPSED TIME CHANGE

Figure 4. Sample Graph of Percent of Elapsed Time Change

Reports 34

100+|| -----| -----| -----

90+ -----| -----| -----| -----| -----

80+ -----| -----| -----| -----| -----

70+ -----| -----| -----| +++++| +++++

P 60+ +++++E | +++++R | +++++C | +++++E | +++++N 50+ +++++T | +++++

| +++++O | +++++F | +++++

40+ +++++J | +++++O | +++++B | +++++S | +++++

30+ +++++| +++++| +++++| +++++| +++++

20+ +++++| +++++| +++++| +++++| +++++

10+ +++++| +++++| +++++| +++++| +++++ ----- +- +- +- + +- +-------------------------------------------------------------------------------------------

<=1 <=3 <=5 <=10 <=20 <=30 <=45 <=60 >60ELAPSED TIME CHANGE (MINUTES)

ACTUAL: TOT CPU TIME 012:27:52 004:52:24 003:26:56 004:19:36 002:16:17 000:15:48 001:14:35 001:17:23AVG CPU TIME 000:00:03 000:00:54 000:02:27 000:03:27 000:06:11 000:07:54 000:14:55 000:38:41AVG CPU % 8.81 9.35 13.00 19.04 19.76 43.88 21.82 46.23

PROJECTED: TOT CPU TIME 055:52:31 021:51:10 015:27:52 019:24:03 010:11:06 001:10:51 005:34:27 005:47:00

Figure 5. Sample Graph of Elapsed Time Change

Reports 35

100+||||

90+||||

80+|| ******| ******| ******

70+ ******| ******| ******| ******| ******

P 60+ ******E | ******R | ******C | ******E | ******N 50+ ******T | ******

| ******O | ******F | ******

40+ ******J | ******O | ******B | ******S | ******

30+ ******| ******| ******| ******| ******

20+ ******| ******| ******| ****** ******| ****** ******

10+ ****** ******| ****** ******| ****** ******| ****** ****** ****** ******| ****** ****** ****** ****** * * * *-----------------------------------------------------------------------------------------------

<=10% <=20% <=30% <=40% <=50% <=60% <=75% >75%CPU UTILIZATION

Figure 6. Sample Graph of Percent of CPU Utilization

Reports 36

BWATRPT2 Version 1.2 - STEP ANALYSIS REPORT PAGE 0003


J JOB PROGRAM START START MEASURED PROJECTED PERCENT MEASURED PROJECTED MEASURED Q TIME PGN C NAME NAME DATE TIME ELAPSED DELTA DELTA CPU TIME CPU TIME CPU% DELTA 10 A SLRP001A DREMNBEB 94045 19:15:45 00:02:30 +00:02:23 + 95% 00:00:13 00:01:04 9% +00:01:32 10 A SLRP001A IDCAMS 94045 19:18:16 00:00:00 +00:00:00 +115% 00:00:00 00:00:00 21% +00:00:00 10 A SLRP001A DREMNBEB 94045 19:15:24 00:00:20 +00:00:08 + 38% 00:00:00 00:00:03 3% +00:00:05 10 A SLRP001A IDCAMS 94045 19:15:44 00:00:00 +00:00:00 + 46% 00:00:00 00:00:00 4% +00:00:00 11 B SLRP001B IEFBR14 94045 19:18:18 00:00:00 +00:00:00 +300% 00:00:00 00:00:00 85% +00:00:00 11 B SLRP001B IEFBR14 94045 19:18:18 00:00:00 +00:00:00 +111% 00:00:00 00:00:00 22% +00:00:00 11 B SLRP001B IKJEFT01 94045 19:18:18 00:00:39 +00:01:07 +168% 00:00:13 00:01:02 33% +00:00:17 11 B SORT001A SORT 94045 19:16:25 00:00:38 +00:00:26 + 68% 00:00:02 00:00:11 6% +00:00:17 11 B SORT001A SORT 94045 19:17:03 00:00:36 +00:00:13 + 36% 00:00:01 00:00:05 3% +00:00:08 11 B SORT001A ERRMSG 94045 19:17:40 00:00:00 +00:00:00 + 0% 00:00:00 00:00:00 0% +00:00:00 11 B SORT001A SORT 94045 19:15:31 00:00:18 +00:00:08 + 44% 00:00:00 00:00:03 4% +00:00:05 11 B SORT001A SORT 94045 19:15:50 00:00:34 +00:00:08 + 23% 00:00:00 00:00:03 2% +00:00:05 11 B SORT001A SORT 94045 19:12:52 00:00:05 +00:00:04 + 82% 00:00:00 00:00:01 8% +00:00:02 11 B SORT001A SORT 94045 19:12:57 00:02:34 +00:00:50 + 32% 00:00:04 00:00:21 3% +00:00:33 11 B SORT001B SORT 94045 19:13:50 00:00:39 +00:00:20 + 51% 00:00:01 00:00:09 4% +00:00:13 11 B SORT001B SORT 94045 19:17:14 00:00:34 +00:00:13 + 38% 00:00:01 00:00:05 3% +00:00:08 11 B SORT001B SORT 94045 19:14:49 00:02:25 +00:01:36 + 66% 00:00:09 00:00:42 6% +00:01:02 11 B SORT001B SORT 94045 19:14:30 00:00:18 +00:00:04 + 26% 00:00:00 00:00:02 2% +00:00:03 11 B SORT001B SORT 94045 19:13:46 00:00:03 +00:00:03 + 86% 00:00:00 00:00:01 8% +00:00:02 11 B TIMS001A FORTVS2 94045 19:07:39 00:00:06 +00:00:06 +111% 00:00:00 00:00:04 14% +00:00:03 11 B TIMS001A FORTVS2 94045 19:07:57 00:00:05 +00:00:05 +108% 00:00:00 00:00:03 13% +00:00:03 11 B TIMS001A FORTVS2 94045 19:08:15 00:00:07 +00:00:08 +121% 00:00:01 00:00:05 18% +00:00:03 11 B TIMS001A FORTVS2 94045 19:08:22 00:00:03 +00:00:04 +114% 00:00:00 00:00:02 15% +00:00:02 11 B TIMS001A FORTVS2 94045 19:08:26 00:00:05 +00:00:06 +117% 00:00:00 00:00:04 16% +00:00:03 10 A TIMS001B HEWL 94045 19:16:09 00:01:24 +00:01:25 +101% 00:00:09 00:00:44 11% +00:00:50 10 A TIMS001B IEBCOPY 94045 19:17:33 00:00:05 +00:00:01 + 26% 00:00:00 00:00:00 2% +00:00:00 10 A TIMS001C B3431TS 94045 19:17:41 00:00:43 +00:01:57 +272% 00:00:29 00:02:18 68% +00:00:09*****************************************************************************************************************

TOTALS 150 JOB STEPS 01:38:05 + 01:14:42 + 76% 00:11:11 00:52:15 11% +00:33:37

EARLIEST JOB STARTED AT 19:07:06 ON 94045 LATEST JOB STARTED AT 19:20:37 ON 94045 BASE SYSTEM CALCULATED UTILIZATION FOR SELECTED JOBS 83% TARGET SYSTEM ESTIMATED UTILIZATION FOR SELECTED JOBS 385%

Figure 7. Sample Step Report

Reports 37

Critical Path Report

This report shows how the start and end times for jobs in the critical path would change. See Figure 8 onpage 39 for a sample report.

All times are in hours, minutes, and seconds.

• Under the CURRENT heading in the report are the start and end times when running on the basesystem.

• Under the PROJECTED heading are the start and end times when running on the target system.

• Under the DELTA END TIME column is the difference in end times between the base and targetsystems.

For example, if a job finished at 18:30:00 on the base system and is projected to finish at 18:20:15 on thetarget system, the delta end time would be -00:09:45.

• The final line in the report has a jobname of CRITPATH. This line summarizes the start and end timesfor the entire critical path for both the base and target systems.

Reports 38

BWATRPT4 VERSION 1.5 - CRITICAL PATH REPORT PAGE 0001

CUSTOMER:


<---------- CURRENT -----------> <--------- PROJECTED ----------> DELTA JOB START START END END START START END END END NAME DATE TIME DATE TIME DATE TIME DATE TIME TIME

CASWLGBK 95179 23:55:28 95180 00:01:22 95179 23:55:28 95180 00:01:22 -00:00:00

CARQLGBK 95180 00:00:14 95180 00:00:15 95180 00:00:14 95180 00:00:15 -00:00:00

CAONLBKA 95180 00:00:47 95180 00:17:55 95180 00:00:47 95180 00:17:50 -00:00:04

CAV18D 95180 00:01:02 95180 00:01:04 95180 00:01:02 95180 00:01:04 +00:00:00

CA24RBKB 95180 00:01:12 95180 00:01:13 95180 00:01:12 95180 00:01:13 +00:00:00

CARQLG 95180 00:01:18 95180 00:01:19 95180 00:01:18 95180 00:01:19 +00:00:00

CAADMBKP 95180 00:18:10 95180 00:20:18 95180 00:18:05 95180 00:20:12 -00:00:05

CA12D 95180 00:20:25 95180 00:21:01 95180 00:20:19 95180 00:20:56 -00:00:05

CA17D 95180 00:22:23 95180 00:22:35 95180 00:22:17 95180 00:22:29 -00:00:06

CA200D 95180 00:48:42 95180 00:58:19 95180 00:48:31 95180 00:58:04 -00:00:14

CA160D 95180 00:58:21 95180 00:58:27 95180 00:58:06 95180 00:58:12 -00:00:15

CA51D 95180 01:04:07 95180 01:04:44 95180 01:03:52 95180 01:04:28 -00:00:15

CABKONAB 95180 01:04:46 95180 01:11:46 95180 01:04:31 95180 01:11:27 -00:00:19

CAV44D 95180 01:41:49 95180 01:47:03 95180 01:41:15 95180 01:46:27 -00:00:35

CA238D 95180 01:47:05 95180 01:57:06 95180 01:46:30 95180 01:56:26 -00:00:40

CAMTRBKA 95180 01:50:04 95180 01:59:16 95180 01:49:23 95180 01:58:28 -00:00:47

CACICSD2 95180 01:59:18 95180 01:59:25 95180 01:58:31 95180 01:58:38 -00:00:47

CA210D 95180 01:59:19 95180 02:03:32 95180 01:58:51 95180 02:03:03 -00:00:28

CAV56D 95180 02:03:34 95180 02:03:35 95180 02:03:05 95180 02:03:06 -00:00:28

CACICSD7 95180 02:16:25 95180 02:16:31 95180 02:15:38 95180 02:15:44 -00:00:47

CAMTRBKP 95180 02:16:36 95180 02:26:31 95180 02:15:49 95180 02:25:37 -00:00:54

==================================================================================================

CRITPATH 95179 23:55:28 95180 02:26:31 95179 23:55:28 95180 02:25:37 -00:00:54

Figure 8. Sample Critical Path Report

Reports 39

Job Time Line Report

This report shows the job start and end times on the base system and the projected end times if running onthe target system.

BWATRPT3 VERSION 1.2 - JOB TIME LINE REPORT PAGE 0001

BASE SYSTEM: 9121/610TARGET SYSTEM: 9672/6-way

JOB 2200 2300 2400 0100NAME |-----------------------------|-----------------------------|-----------------------------|-----------------------------|

BRSPB1J |---|>

BRSPB1J |--------------------|--------->

FASPB1J ||

FASPB1J |--------|----->

FASPB1J6 |-|>

FASPB1J7 |-|>

FASPB1J |--|->

FASPB1J ||>

FAMPB1J |-------------------------------------|------------------->

FASPB1J ||

FASPB1J1 ||

FASPB1J2 ||

FASPB1J3 ||

FASPB1J4 |-|>

FASPB1J5 ||

FASPB1J5 |-----|------>

BRSPB1J |-|>

BRSPB1J |--|->

BRSPB1J |-----|--->

FASPB1J |-------|--->

FASPB1J |-|->

FASPB1J |----|>

FASPB1J |-----|---->

FASPB1J |--------------|-->

DUMPMAN4 |

Figure 9. Sample Job Time Line Report

Reports 40

How to Read This Report• Base system start and end times

Indicated by a pair of vertical bars(|). If only one | is present it means the job ended within the sametime period that it started.

These are the actual start and end times taken from the SMF data.

• Target system end time

When the projected elapsed time increases, the projected end time will be to the right of the base systemend time and will be indicated by a greater than(>) sign. When the projected end time falls within thesame time period as the base system end time the > indicator is not shown.

When the projected elapsed time decreases, the projected end time will be to the left of the base systemend time and will be indicated by a less than(<) sign. When the projected end time falls within the sametime period as the base system end time the < indicator is not shown.

The following examples will illustrate this.JOB 2200 2300 2400 0100 NAME |-----------------------------|-----------------------------|-----------------------------|-----------------------------|

BRSPB1J |---|>Job started at 22:04 and ended at 22:11Job projected to end at 22:13

FASPB1J ||Job started at 22:22 and ended at 22:24Job projected to end at 22:25

FASPB1J |-----------<----|Job started at 22:24 and ended at 23:00Job projected to end at 22:49

FASPB1J |>Job started at 23:02 and ended at 23:03Job projected to end at 23:05

FASPB1J |Job started at 23:26 and ended at 23:26Job projected to end at 23:27

A single time period on the time line varies according to the total number of hours on the time line. Forexample, for 12 hours a single time period would be 6 minutes. A job that started at 22:06 and ended at22:21 would be indicated as |-| (three 6 minute time periods). For a 2 hour time line, a single time periodwould be 1 minute. The same job that started at 22:06 and ended at 22:21 would be indicated as |-------------|(Fifteen 1 minute time periods).

Reports 41

Job Information Report

The following information is included in the Job Information Report.

• Machine Type and Model

• MVS Level

• Performance Group Number

• Job Class

• Job Name

• Service Class

• Date that the job started

• Time that the job started

• Elapsed time

• CPU Time

• Completion Code

• Termination Indicator

This is an indicator of whether or not a job ended abnormally. If this field in the report begins with anasterisk(*), the job ended abnormally. The value in this field is a hexadecimal representation of bits indi-cating the reason the job terminated. A description of the bit meanings can be found in SMF docu-ments but if you don′t see * at the beginning of this field the job ended normally and these bits will be0.

• Number of steps in the job

• Number of EXCPs

• Number of EXCPs per CPU second

• Number of Tape Mounts

Reports 42

BWATRPT5 VERSION 2.0 - JOB INFORMATION REPORT 07/01/1996 PAGE 0001

CUSTOMER:

BASE SYSTEM: 9021/520 SYSID - XYZ1 MVS LEVEL: SP4.3.0

J JOB START START ELAPSED CPU COMPLETION TERMINATION NUMBER NUMBER EXCPS PER TAPE PGN C NAME DATE TIME TIME TIME CODE INDICATOR STEPS EXCPS CPU SEC MOUNTS

1 G SACMSG 96152 23:40:02 00:23:17 00:00:00 0000 0000 1 9 1121 A SERVMSG 96152 23:45:03 00:18:13 00:00:00 0000 0000 1 1 121 A SMFDAILY 96153 00:00:52 00:11:12 00:00:13 0000 0000 7 13,740 1,033 14 P BKUPCFP 96153 00:00:55 00:03:25 00:00:01 0000 0000 2 1,326 960 11 A TMON8FSU 96153 00:00:55 00:04:17 00:00:05 0000 0000 1 3,442 661 11 A SCRATCH 96153 00:03:16 00:02:15 00:00:04 0000 0000 3 12,668 2,6554 P BKUPDCM 96153 00:04:20 00:54:10 00:00:28 0000 0000 2 48,421 1,707 14 F DCENSTAT 96153 00:05:09 00:00:36 00:00:01 0000 0000 4 406 2741 A TMON8RWM 96153 00:05:13 00:53:09 00:13:45 0000 0000 17 66,752 80 11 A DFDSS 96153 00:05:32 00:01:27 00:00:02 0004 0000 1 83 30

17 I DBEDSTAT 96153 00:05:49 00:02:03 00:00:00 0000 0000 1 116 1264 F DNURSRPT 96153 00:06:12 00:05:08 00:00:10 9528 0000 16 3,856 3751 T BALCHECK 96153 00:07:06 00:25:45 00:00:31 0000 0000 4 70,945 2,254

17 I DBHFHPEX 96153 00:07:54 00:01:22 00:00:02 0000 0000 3 501 2271 A TMON8RWV 96153 00:08:08 00:43:35 00:10:03 0000 0000 16 47,210 78 14 F DNRSTSR2 96153 00:11:35 00:00:48 00:00:01 0000 0000 1 2,076 1,2971 A RMFPLOT 96153 00:12:05 00:00:14 00:00:02 0000 0000 1 423 2001 A SMFMONTH 96153 00:12:20 00:06:22 00:00:00 0000 0000 1 45 264 14 F EZCEN055 96153 00:12:24 00:00:06 00:00:00 0000 0000 1 362 6964 F DADMDEL 96153 00:12:34 00:09:40 00:00:00 0000 0000 1 387 6241 A RMFDURAT 96153 00:18:43 00:01:52 00:00:07 0000 0000 1 1,599 2001 A CIMSREPT 96153 00:20:46 00:03:19 00:00:10 0000 0000 9 4,628 4484 F DBDHSTEX 96153 00:22:15 00:38:00 00:00:22 0000 0000 31 13,960 6201 A CIMSREPM 96153 00:24:14 00:14:24 00:00:57 0000 0000 9 24,018 418 2

17 E DPATSTMT 96153 00:30:05 00:13:23 00:00:17 0000 0000 1 3,324 1881 T RBALEXT 96153 00:32:56 00:26:45 00:01:14 0000 0000 1 5,015 671 A CERNMSG 96153 00:38:38 00:02:25 00:00:00 0000 0000 1 1 14

17 E DSTMREP 96153 00:43:34 00:06:05 00:00:05 0000 0000 1 270 531 A TMON8MTH 96153 00:58:31 00:25:13 00:05:01 0000 0000 3 17,399 57 44 P BKUPPROC 96153 00:58:32 00:05:48 00:00:16 0000 0000 2 27,055 1,657 11 A DTE2DAYJ 96153 01:00:01 00:00:05 00:00:00 0000 0000 2 35 1201 M MMSCLOS2 96153 01:00:03 00:01:03 00:00:00 0000 0000 1 86 3581 A SERVMSG 96153 01:00:04 00:03:21 00:00:00 0000 0000 1 1 124 F AD890102 96153 01:00:17 00:01:05 00:00:02 0000 0000 2 581 205

17 E CENCDSTL 96153 01:00:23 00:00:44 00:00:00 0000 0000 1 413 503 17 E FPBCRARB 96153 01:01:08 00:00:42 00:00:02 0000 0000 3 1,263 625

4 F ADCS8901 96153 01:01:23 00:00:12 00:00:00 0000 0000 1 361 6564 F BHSPECL 96153 01:01:35 00:00:14 00:00:00 0000 0000 1 685 901

Figure 10. Sample Job Information Report

Reports 43

Sorting Reports in Different Order

The order that records appear in the reports can be easily altered by changing the SORT control statementin the step preceding program BWATRPT1.

The following fields contained in the input to BWATRPT1 may be combined in various ways to producereports in different sequences:

Field Name Location in Input

Performance Group Number 1 - 2 (binary)

Job Name 3 - 10 (character)

Step Number 11 - 12 (binary)

Program Name/Service Class/Report Class 13 - 20 (character)

System ID 21 - 24 (character)

Date started 25 - 28 (packed)

Time started 29 - 32 (binary)

Date ended 33 - 36 (packed)

Time ended 37 - 40 (binary)

Measured Elapsed Time 41 - 44 (binary)

Projected Elapsed Time 45 - 48 (binary)

Projected Elapsed Time Delta 49 - 52 (binary)

Percent of Elapsed time Change 53 - 56 (binary)

Measured CPU Time 57 - 60 (binary)

Projected CPU Time 61 - 64 (binary)

Measured CPU to Elapsed Time Ratio 65 - 68 (binary)

Projected CPU to Elapsed Time Ratio 69 - 72 (binary)

Number of EXCPs 89 - 92 (binary)

Number of Tape Mounts 93 - 96 (binary)

Job Class 103 - 103 (character)

JES3 Job Class 104 - 111 (character)

For example to sort the report in sequence from highest to lowest projected elapsed time within start date,the SORT control statement in STEP4 would be coded as:

SORT FIELDS=(25,4,PD,A,45,4,FI,D)

Reports 44

Appendix A. Machines Supported

Performance information for the following machines is programmed into the tool so that BASERPP andTARGETRPP parameters are not needed if both the base and target machines are contained in this table.

LSPR values for 2064, 2066, 2084, 2086, 2094, 2096, 2097, 2098, 2817, 2818, 2827, and 2828 processormodels based on z/OS V1R13.

MachineType

Models MachineType

Models

2064 101 102 103 104 105 106 107 108 109110 111 112 113 114 115 116 1C11C2 1C3 1C4 1C5 1C6 1C7 1C8 1C92C1 2C2 2C3 2C4 2C5 2C6 2C7 2C82C9 210 211 212 213 214 215 216

2066 0A1 0B1 0C1 0A2 001 002 003 0040E1 0X2

2084 301 302 303 304 305 306 307 308 309310 311 312 313 314 315 316 317 318319 320 321 322 323 324 325 326 327328 329 330 331 332

2086 110 210 310 410 120 220 320 420 130230 330 430 140 240 340 440 150 250350 450 160 260 360 460 170 270 370470

2094 401 402 403 404 405 406 407 408 501502 503 504 505 506 507 508 601 602603 604 605 606 607 608 701 702 703704 705 706 707 708 709 710 711 712713 714 715 716 717 718 719 720 721722 723 724 725 726 727 728 729 730731 732

2096 A01 A02 A03 B01 B02 B03 C01 C02C03 D01 D02 D03 E01 E02 F01 F02G01 H01 I01 J01 K04 L03 L04 M03M04 N02 N03 N04 O02 O03 O04P02 P03 P04 Q02 Q03 Q04 R01 R02R03 R04 S01 S02 S03 S04 T01 T02T03 T04 U01 U02 U03 U04 V01V02 V03 V04 W01 W02 W03 W04X01 X02 X03 X04 Y01 Y02 Y03Y04 Z01 Z02 Z03 Z04

2097 401 402 403 404 405 406 407 408 409410 411 412 501 502 503 504 505 506507 508 509 510 511 512 601 602 603604 605 606 607 608 609 610 611 612701 702 703 704 705 706 707 708 709710 711 712 713 714 715 716 717 718719 720 721 722 723 724 725 726 727728 729 730 731 732

2098 A01 A02 A03 A04 A05 B01 B02B03 B04 B05 C01 C02 C03 C04 C05D01 D02 D03 D04 D05 E01 E02E03 E04 E05 F01 F02 F03 F04 F05G01 G02 G03 G04 G05 H01 H02H03 H04 H05 I01 I02 I03 I04 I05J01 J02 J03 J04 J05 K01 K02 K03K04 K05 L01 L02 L03 L04 L05M01 M02 M03 M04 M05 N01 N02N03 N04 N05 O01 O02 O03 O04O05 P01 P02 P03 P04 P05 Q01 Q02Q03 Q04 Q05 R01 R02 R03 R04R05 S01 S02 S03 S04 S05 T01 T02T03 T04 T05 U01 U02 U03 U04U05 V01 V02 V03 V04 V05 W01W02 W03 W04 W05 X01 X02 X03X04 X05 Y01 Y02 Y03 Y04 Y05Z01 Z02 Z03 Z04 Z05

Appendix A. Machines Supported 45

MachineType

Models MachineType

Models

2817 401 402 403 404 405 406 407 408 409410 411 412 413 414 415 501 502 503504 505 506 507 508 509 510 511 512513 514 515 601 602 603 604 605 606607 608 609 610 611 612 613 614 615701 702 703 704 705 706 707 708 709710 711 712 713 714 715 716 717 718719 720 721 722 723 724 725 726 727728 729 730 731 732

2818 A01 A02 A03 A04 A05 B01 B02B03 B04 B05 C01 C02 C03 C04 C05D01 D02 D03 D04 D05 E01 E02E03 E04 E05 F01 F02 F03 F04 F05G01 G02 G03 G04 G05 H01 H02H03 H04 H05 I01 I02 I03 I04 I05J01 J02 J03 J04 J05 K01 K02 K03K04 K05 L01 L02 L03 L04 L05M01 M02 M03 M04 M05 N01 N02N03 N04 N05 O01 O02 O03 O04O05 P01 P02 P03 P04 P05 Q01 Q02Q03 Q04 Q05 R01 R02 R03 R04R05 S01 S02 S03 S04 S05 T01 T02T03 T04 T05 U01 U02 U03 U04U05 V01 V02 V03 V04 V05 W01W02 W03 W04 W05 X01 X02 X03X04 X05 Y01 Y02 Y03 Y04 Y05Z01 Z02 Z03 Z04 Z05

2827 401 402 403 404 405 406 407 408 409410 411 412 413 414 415 416 417 418419 420 501 502 503 504 505 506 507508 509 510 511 512 513 514 515 516517 518 519 520 601 602 603 604 605606 607 608 609 610 611 612 613 614615 616 617 618 619 620 701 702 703704 705 706 707 708 709 710 711 712713 714 715 716 717 718 719 720 721722 723 724 725 726 727 728 729 730731 732

2828 A01 A02 A03 A04 A05 A06 B01B02 B03 B04 B05 B06 C01 C02 C03C04 C05 C06 D01 D02 D03 D04D05 D06 E01 E02 E03 E04 E05 E06F01 F02 F03 F04 F05 F06 G01 G02G03 G04 G05 G06 H01 H02 H03H04 H05 H06 I01 I02 I03 I04 I05I06 J01 J02 J03 J04 J05 J06 K01K02 K03 K04 K05 K06 L01 L02L03 L04 L05 L06 M01 M02 M03M04 M05 M06 N01 N02 N03 N04N05 N06 O01 O02 O03 O04 O05O06 P01 P02 P03 P04 P05 P06 Q01Q02 Q03 Q04 Q05 Q06 R01 R02R03 R04 R05 R06 S01 S02 S03 S04S05 S06 T01 T02 T03 T04 T05 T06U01 U02 U03 U04 U05 U06 V01V02 V03 V04 V05 V06 W01 W02W03 W04 W05 W06 X01 X02 X03X04 X05 X06 Y01 Y02 Y03 Y04Y05 Y06 Z01 Z02 Z03 Z04 Z05 Z06

Appendix A. Machines Supported 46

Appendix B. Error Messages

Invalid Keyword

Explanation: A user parameter was entered that contained a keyword that was not one of thekeywords recognized by the code.

User Response: Correct the parameter and resubmit the job.

Invalid parameter value

Explanation: A user parameter was entered that contained invalid data.

User Response: Correct the parameter and resubmit the job.

BASEMACH and BASEMODEL or BASERPP required

Explanation: The user did not enter BASEMACH and BASEMODEL or BASERPP.

User Response: If both the base and target systems are listed in the table of supported systems,you should enter BASEMACH and BASEMODEL. Otherwise you must enter BASERPP.

TARGETMODEL required with TARGETMACH.

Explanation: The user entered TARGETMACH but not TARGETMODEL.

User Response: Enter the TARGETMODEL parameter.

TARGETRPP not valid without BASERPP.

Explanation: The user entered TARGETRPP but not BASERPP. If either of these parameters isentered the other must be entered also.

User Response: Enter the BASERPP parameter or remove the TARGETRPP parameter if boththe base and target systems are listed in the table of supported systems.

Maximum job names or program names exceeded

Explanation: A maximum of 300 JOBNAME parameters may be entered or a maximum of 300jobs may be defined as CRITJOBS. A maximum of 100 NOTJOBNAME parameters may beentered. A maximum of 25 PGMNAME parameters may be entered.

User Response: Remove some of the job names.

Appendix B. Error Messages 47

Maximum performance groups exceeded.

Explanation: A maximum of 100 PGROUP parameters or 25 NOTPGROUP parameters maybe entered.

User Response: Remove some of the PGROUP parameters.

Maximum job classes exceeded.

Explanation: A maximum of 20 CLASS/JES3CLASS parameters may be entered. A maximumof 20 NOTCLASS/NOTJES3CLASS parameters may be entered.

User Response: Remove some of the classes.

BASEMODEL required with BASEMACH.

Explanation: The user entered BASEMACH but not BASEMODEL.

User Response: Enter the BASEMODEL parameter.

TARGETRPP required with BASERPP.

Explanation: The user entered BASERPP but not TARGETRPP. If either of these parameters isentered the other must be entered also.

User Response: Enter the TARGETRPP parameter or remove the BASERPP parameter if boththe base and target systems are listed in the table of supported systems.

Number of processors must be specified.

Explanation: Whenever BASERPP and TARGETRPP are entered, BASE#CP andTARGET#CP must also be entered.

User Response: Enter the BASE#CP and TARGET#CP parameters.

STIME & ETIME required for TIMELINE.

Explanation: The user requested a TIMELINE report but did not specify a start time and endtime for the report.

User Response: Enter STIME and ETIME values. If the times are more than 12 apart, theETIME value will be changed to the STIME value plus 12 hours.


STIME & ETIME required for CRITPATH.

Explanation: The user requested a CRITPATH report but did not specify a start time and endtime for the report.

User Response: Enter STIME and ETIME parameters.

SDATE & EDATE required for CRITPATH.

Explanation: The user requested a CRITPATH report but did not specify a start date and enddate for the report.

User Response: Enter SDATE and EDATE parameters.

JOBNAME and CRITJOBS not allowed together

Explanation: The user entered both JOBNAME and CRITJOBS parameters.

User Response: Remove the JOBNAME parameters or the CRITJOBS parameters. Ifrequesting a CRITPATH report, the CRITJOBS parameters must be entered.

Maximum jobs on single line exceeded.

Explanation: The user entered more than 20 job names in a single CRITJOBS statement.

User Response: Enter multiple CRITJOBS statements to define the jobs. There is no limit to thetotal number of successor jobs that a job can have(except for the 300 total jobs limit), but nomore than 20 job names can be entered in a single CRITJOBS statement.

SDATE & EDATE required if BASEBUSY is not entered.

Explanation: When a BASEBUSY parameter is not entered, the system utilization will be calcu-lated using type 70 records. SDATE and EDATE must be entered to indicate a date range forthe type 70 records. This date range may not exceed 4 days.

User Response: Either enter the SDATE and EDATE parameters or enter the BASEBUSYparameter.


Start and end dates cannot differ by more than 4 days if BASEBUSY not entered.

Explanation: When a BASEBUSY parameter is not entered, the system utilization will be calcu-lated using type 70 records. The maximum allowable length of time for the system calculation is4 days. The time period indicated by the SDATE and EDATE parameters exceeds 4 days.

User Response: Either change the SDATE and EDATE parameters so that the time range doesnot exceed 4 days or enter the BASEBUSY parameter.

SYSID is required.

Explanation: The user did not enter a SYSID parameter. This parameter is always required.

User Response: Enter the SYSID parameter.

BASEMACH and BASEMODEL are not valid

Explanation: The system indicated by BASEMACH and BASEMODEL is not one of thesystems in the table of supported systems.

User Response: Correct the BASEMACH and BASEMODEL values to match one of the sup-ported systems or enter the BASERPP and BASE#CP parameters if it is not a supported system.

TARGETMACH and TARGETMODEL are not valid

Explanation: The system indicated by TARGETMACH and TARGETMODEL is not one ofthe systems in the table of supported systems.

User Response: Correct the TARGETMACH and TARGETMODEL values to match one ofthe supported systems or enter the TARGETRPP and TARGET#CP parameters if it is not asupported system.

No SMF records matched selection criteria.

Explanation: Either the SMF data did not contain type 30 subtype 4 records for step reports ortype 30 subtype 5 records for other reports or there were no records that made it through all thefiltering parameters that the user entered.

User Response: Remove all filtering parameters and run the job again. If the same error occursagain without filtering parameters, either the input does not contain any type 30 SMF records orthe type 30 records are not the correct subtype(subtype 4 or 5).


CRITICAL PATH JOB xxxxxxxx NOT FOUND IN SMF.

Explanation: The user requested a CRITPATH report but one of the jobs identified in aCRITJOBS parameter was not found in the SMF data.

User Response: Either correct the CRITJOBS parameter, change the SDATE, EDATE, STIME,and ETIME parameters, or code CHECKABEND(NO).

CRIT PATH JOB xxxxxxxx RAN MORE THAN ONCE.

Explanation: The user requested a CRITPATH report and one of the jobs identified in aCRITJOBS parameter ran more than once during the time period indicated by the SDATE,EDATE, STIME, and ETIME parameters.

User Response: You make have to break up the analysis into multiple time periods. CodeSDATE, EDATE, STIME, and ETIME parameters for each run so that no job in the criticalpath runs more than once during that time period.

WARNING: Job xxxxxxxx has start time outside the range of type 70 times.

Explanation: The job whose name appears in this message has a start time that is not within therange of times for the type 70 records. This is only a warning. It does not cause the batch anal-ysis to terminate. A value of 60% system utilization will be used for this job.

User Response: None.

The input does not contain any type 70 records.

Explanation: The user did not enter a BASEBUSY value so type 70 records will be used tocalculate system utilization. There were no type 70 records in the input.

User Response: Use a dataset that contains type 70 records for the same time period as the type30 records or enter a value for BASEBUSY so that type 70 records will not be used.

There were no type 70 records found for the SYSID, LPARNAME, or time period entered.

Explanation: The user did not enter a BASEBUSY value so type 70 records will be used tocalculate system utilization. None of the type 70 records matched the SYSID that was entered orthe LPARNAME that was entered or none of the type 70 records were for the time period thatthe user entered.

User Response: If you are sure that the correct input was used, correct correct the SYSID,SDATE, EDATE, STIME, and ETIME parameters to match the data in the input.


An LPARNAME parameter must be entered to identify which LPAR to analyze.

Explanation: The record type 70 data indicates that the base system is running in LPAR mode.An LPAR name must be entered so that the data for the correct LPAR is used.

User Response: Enter an LPARNAME parameter.

MAXIMUM PREDECESSORS EXCEEDED FOR JOB xxxxxxxx

Explanation: A job defined in the critical path had more than 15 predecessors.

User Response: Remove some of the predecessors and rerun the job.

PGROUP & SERVCLASS are mutually exclusive

Explanation: The user entered performance group and service class parameters. Performancegroups are used in compatibility mode and service classes are used in goal mode. It is not pos-sible to use both parameters at the same time.

User Response: Remove the performance group parameters if running in goal mode or removethe service class parameters if running in compatibility mode.

Maximum service classes exceeded.

Explanation: A maximum of 20 SERVCLASS parameters and 20 NOTSERVCLASS parametersmay be entered.

User Response: Remove some of the service classes.

USEBUSYRATIO required with BUSYRATIO.

Explanation: The user entered a BUSYRATIO parameter but did not enter a USEBUSYRATIOparameter.

User Response: Enter the USEBUSYRATIO parameter or remove the BUSYRATIO parameter.

INFORMATIONAL: TARGETBUSY and USEBUSYRATIO are mutually exclusive parame-ters. The TARGETBUSY value is used.

Explanation: The user entered both the TARGETBUSY and USEBUSYRATIO parameters.These parameters are mutually exclusive. If both are specified, the TARGETBUSY parameterwill be used and the USEBUSYRATIO will be ignored.



Abended jobs not included in the reports.

Explanation: The following list of jobs ended abnormally and are not included in the reportsbecause the CHECKABEND parameter has been allowed to default or has been set to YES.


End of Document


Batch Workload Analysis Tool User s Guide Version 4

Documents

Transcript of Batch Workload Analysis Tool User s Guide Version 4