BEST/1 Capacity Planning Tool

Transcription

1 iseries BEST/1 Capacity Planning Tool Version 5 SC

2

3 iseries BEST/1 Capacity Planning Tool Version 5 SC

4 Note Before using this information and the product it supports, be sure to read the general information under Notices on page ix. Second Edition (May 2001) This edition applies to Version 5 Release 1 Modification 0 of the licensed program IBM Performance Tools for iseries and to all subsequent releases and modifications until otherwise indicated in new editions. This edition replaces SC This edition applies only to reduced instruction set computer (RISC) systems. Copyright International Business Machines Corporation 1998, All rights resered. US Goernment Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Copyright BMC Software, Inc., 1998, 2001

5 Contents Figures ii Notices ix Programming Interface Information x Trademarks xi About BEST/1 Capacity Planning Tool (SC ) xiii Who should read this book xiii Prerequisite and related information xiii Operations Naigator xi How to send your comments xi Summary of Changes to BEST/1 Capacity Planning Tool (SC ).. x Chapter 1. Introduction to Capacity Planning How to Start BEST/ The Capacity Planning Process When to Use Capacity Planning Significant Capabilities of the Capacity Planning Tool BEST/1 Performance Statistics BEST/1 Assumptions and Conditions Major Assumptions Major Conditions BEST/1 Modeling Process Major Options for Modeling with BEST/ Work with BEST/1 Models Basic User Leel Adanced User Leel Aailable Menu Options Capacity Planning Files and Usage Chapter 2. Workload Concepts Job Classification BEST/1 Job Types Defining Work to the Model Workload Definition Function Definition Transaction Definition Non-interactie Transactions Example Showing Workloads, Functions and Transactions Specifying Objecties and Actie Jobs Summary of Workloads, Functions, Transactions, and Objecties Chapter 3. Building a Model Using Measured Data Selecting Data for Capacity Planning Measured Workloads Creating a Model Using Performance Data Basic Method Adanced Method Classifying Jobs into Workloads Using the Default Job Classification Default Job Classification Defining a Job Classification How BEST/1 Handles Licensed Internal Code Tasks Assigning Jobs to Workloads by Job Type Assigning Jobs to Workloads by Job Name Assigning Jobs to Workloads by Communications 46 Specifying Paging Behaiors Defining Non-interactie Transactions Creating the Model Mixing Workloads from Different Serers Mixing Workloads from Different Serers Example Chapter 4. Building a Model Using Predefined Workloads Using Predefined Workloads Using BATCH Predefined Workloads Selecting Predefined Workload Chapter 5. System Configuration Read Conersion System Configuration Menu Changing CPU and Other Resource Values Working with Disk Resources Editing ASPs Editing Main Storage Pools Working with Communications Resources Chapter 6. Model Analysis and Calibration Verifying the Workloads Working with Functions Working with Transactions Verifying the Number of Actie Jobs in the Workload Changing the application type Calibrating the Model Comparing Measured and Predicted Data Calibrating Response Time Calibrating Other Resources Model Analysis Results Analysis Summary Recommendations Workload Report ASP and Disk Arm Report Disk Resources Report Main Storage Pool Report Communications Resources Report Saing Results Copyright IBM Corp. 1998, 2001 iii

6 Chapter 7. Modeling Changes to the System Specifying Performance Objecties Editing Utilization Guidelines and Thresholds 102 Editing Sync Reads Guidelines Editing Paging Behaior Values Editing CISC-to-RISC Conersion Factors Performance Objecties for Interactie and Non-interactie Actiity Analyzing the Model Modeling Workload Growth Growing a Workload Manually Specifying Growth for a Single Workload Growing a Workload Automatically Changing Functions and Transactions Changing System Resources Automatic Hardware Changes with Manual Growth Changing CPU and Other Resource Values Selecting a CPU Selecting Main Storage Size Selecting Release Leel Changing Disk Resources Changing ASP Disk Protection Changing Main Storage Pools Adjusting Actiity Leels Changing Communications Resources Understanding Recommendations Exceptions Recommendations How Utilizations are Predicted Memory Modeling Memory Modeling Terminology Techniques for Achieing Effectie Storage Recommendations Chapter 8. Selected Modeling Topics 145 Modeling Client Access Strategy for Defining Workloads Reiewing the Number of Actie Jobs in the New Model Reiewing the Workloads Analyzing the Client Access Model Understanding Results Modeling Non-interactie Work Defining Non-Interactie Transactions Modeling Interactie Transactions Linked to Non-Interactie Modeling Batch Isolation of Batch into an Independent Workload Special Considerations when you collect data 155 Inclusion of Batch in CPU Model Recommendation Calibrating *BATCHJOB Workloads Predicting Batch Transaction Throughput Example Batch Window Modeling Basic Procedure for Batch Window Modeling 160 Communications Support Hardware Characteristics Communications Configuration Distribution of Characters Transferred Across Line Resources Modeling Data Protection Comparing Performance for Data Protection Methods Additional Modeling Considerations for 9337 Disk Array Subsystem Modeling Transitions Between CISC and RISC Modeling ASPs and Journaling Modeling Release Leel Performance Improements Chapter 9. Capacity Planning Examples Performance Tips When Doing What-if...? Analysis Creating a BEST/1 Model from Performance Data Creating a Model from Existing Performance Data Basic Creating a Model from Existing Performance Data Adanced Adding Throughput to an Existing System Projecting Future System Needs as a Result of Oerall System Growth Graphing Results Displaying Graphs from the Current Model Displaying Graphs from a Preious Model Creating Your Own Graphs Adding a Newly Announced CPU to the Hardware Characteristics File Leaing the Current Model Chapter 10. Printing Model Reports and Graphs Printed Reports Sample Printed Output Analysis Summary Report Recommendations Report Workload Report ASP and Disk Arm Report Disk Resources Report Main Storage Pool Report Comm Resources Report Model Report Analysis Parameters Graph Format Graphical Output Changing the Axis Range Graphing a Single Set of Model Results Oerlaying Graphs of Two Results Printing Graphs in BEST/ Plotting Graphs in BEST/ Sample Custom Graphs Appendix A. BEST/1 Workload Groups for Capacity Planning COMMERCIAL Workload Group i BEST/1 Capacity Planning Tool V5R1

7 SQL RTW Workload RTW Transaction Details RTW Transaction Summary RTW Tables and Indexes SPOOL Workload Group BATCH Workload Group Background batch serer Commercial Orders Deelopment Complex Query Summary Query (medium complexity) Sort Query (medium complexity) OFFICE Workload Group SERVER Workload Group Client/Serer Simple OLTP Client/Serer Medium OLTP (DQ) Heay USF/400 Multimedia User Heay Image Slide Show (Shared Folders) Heay Image Slide Show (IPCS) Heay Image and Audio Slide Show Medium Continuous Video (Shared Folders) Medium Continuous Video (FSIOP) INDUSTRY Workload group Appendix B. Query to Print JOB/TASK Types and CPU Utilization Appendix C. Conerting BEST/1 Models and Migrating Data Configuration Changes to Pre-V4R2 BEST/1 Models System/36 Migration Utility Migration Utility Instructions for the System/36 MIGUTL Procedure Example of Migrating System/36 Measured Data Appendix D. BEST/1 Principles Response Time Variation Appendix E. Manual Batch Window Modeling Basic Concepts and Formulas Queuing Multipliers Example Relatie CPU Power Table Appendix F. Externally Described Files 289 Appendix G. Graphic Support Variables X-axis Variables Y-axis Variables Appendix H. BEST/1 Hardware Name Mapping Appendix I. Building Performance Profiles Fie Steps to Enabling Proper System Sizing Data Collection Create Baseline Model Verify Baseline Model Workload and Hardware Changes Use the Model for Future System Sizings Sending the Performance Profiles to IBM Appendix J. Upgrading CISC-to-RISC Example Manual Upgrade to a RISC System Automatic Upgrade to a RISC System Determining Which Conersion Factors to Use Appendix K. Tuning Performance Improement Factors Traditional Commercial Transaction Processing Applications Communications Enironments Compile Enironments Sae/Restore Enironments Appendix L. Untranslated Messages 337 Bibliography Index Contents

8 i BEST/1 Capacity Planning Tool V5R1

9 Figures 1. BEST/1 for the AS/400 Main Menu The Modeling Process Range of Results Using the BEST/1 Capacity Planning Tool Work with BEST/1 Models Display Work with BEST/1 Model Menu Basic User Leel Work with BEST/1 Model Menu Adanced User Leel Work with Results Display More BEST/1 Options Menu Relationship of Jobs to BEST/1 Workloads Edit Job Classifications by Job Type Example Assign Jobs to Workloads by Job Type Example Workload Components of a Model Change Workload Display Change Function Display Change Transaction - Process Heay Mail Define Non-Interactie Transactions Display Create Workload Display Change Function - Process Heay Mail Change Transaction - Process Heay Mail Specify Objecties and Actie Jobs BEST/1 Relationship of Workload Components Create BEST/1 Model from Performance Data Basic Create BEST/1 Model from Performance Data Adanced Select Sample Periods Select Sample Periods Job Classification Menu Specify Job Classification Category Assigning Jobs to Workloads by Job Type Specify Job Classification Category Specify Job Classification Category Assign Jobs to Workloads Specify Paging Behaiors Define Non-Interactie Transactions Display Define Non-interactie Transactions Creation of the Model Select Predefined Workload - Batch Modeling Example Select a Predefined Workload Group Select a Predefined Workload Create Workload Display Work with Configuration Member Display Configuration Main Menu Change CPU and Other Resource Values Specify other logical partitions Working with Disk Resources Editing ASP Data Protection Editing Main Storage Pools Work with Communications Resources Work with BEST/1 Model Display Work with BEST/1 Model Flow Chart Adanced User Leel Work with Workloads Validation Example Change Workload Change Function Work with Transactions Display Change Transaction Details Validate Model Objecties Select Application Type Measured and Predicted Comparison Display Measured and Predicted Comparison for Calibration Measured and Predicted Comparison (After Calibration) Display (Change) the Transaction Detail After Calibration Work with BEST/1 Model - Calibrate Model Work with Results Model Analysis Analysis Summary Display for Calibration Model Recommendations Model Workload Report Model Workload Report - Response Time Components Disk ASP and Disk Arm Report Disk Resources Report Main Storage Report Communications Resource Report Sae Current Results Analysis Parameters Menu Changing Analysis Guidelines Edit Sync Reads Guidelines CISC and RISC Guidelines and Thresholds Edit Paging Behaior Values Edit CISC-to-RISC Conersion Factors Specify Objecties and Actie Jobs Work with BEST/1 Model Display Work with BEST/1 Model Specify Growth of Workload Actiity Work with Results Display New Objecties Display Recommendations Display Work with BEST/1 Model Display Work with Results Display Analysis Summary Display Analysis Display for Multiple Points Change Function Display Change Transaction Display Edit Transactions Display Manual Growth - Display Results of Automatic Hardware Upgrade Manual Growth - Graph of Automatic Hardware Upgrade Change CPU and Other Resource Values CPU Selection Selecting Main Storage Size Selecting Release Leel Copyright IBM Corp. 1998, 2001 ii

10 98. Working with Disk Resources Select Resources to Change Features Changing ASP Data Protection Changing Main Storage Pools Changing Communications Resources Display Recommendations Resident Set s. Page Faults or Sync Reads Relatie Change in Resident Set Size Synchronous Reads/Transaction s. Resident Set Size Change Paging Behaior Display Editing Sync Reads Guidelines Resident Sets with Paging Exponents Client Access Example Assign Job Types to Workloads Display Objecties of Newly Created Model Reiew Workloads Reiew CA4 Workload Define Non-interactie Transactions Work with Workloads Change Workload Work with Functions Change Function Work with Transactions Create Transaction Create Model from Performance Data - Batch Run Time Edit Job Classifications - Batch Run Time Specify Objecties - Batch Run Time Display Workload Report - Batch Run Time More BEST/1 Options Menu Hardware Characteristics Menu Work with Communications IOP Features Work with Line Speeds Specify Connections to Comm IOPs Work with BEST/1 Model Menu Configuration Menu Work with Communications Resources Create Multifunction IOP Create IOP Create Communications Lines Specify Chars to Comm Line Resources Change CPU Model Display Specify Performance Improements Display Creating a BEST/1 Model Basic Select Sample Periods Work with BEST/1 Model Menu Basic Scenario Select Sample Periods Analysis Summary Report Recommendations Report Workload Report ASP and Disk Arm Report Disk Resources Report Main Storage Pool Report Communications Resources Report Printout of Model Detail Part Printout of Model Detail Part Printout of Model Detail Part Analysis Parameters Printout of Graph Format Details IBM-Supplied Graph Formats BEST/1 Create Graph Format BEST/1 Graphic Support Variables Change Axis Ranges Display Single Results, Multiple Workload Graph Example Oerlay, Multiple Workload Graph Example Specify Printer Change Printer Options Specify Plotter Disk Utilization by Total Workload Disk IOP Utilization by Total Workload CPU Utilization by Non-Interactie Throughput CPU Utilization by Interactie Throughput Response Time ersus Interactie Throughput Response Time by Workload CPU Utilization Component Breakdown Sample Bar Chart Query Query Query Query 2 (page 1 of 2) Query 2 (page 2 of 2) Sample Query Output (edited for clarity) Estimating the Queuing Multiplier Queuing Multiplier for Gien Utilization of the Resource General Batch Run Time Formula Detailed Batch Run Time Formula CPU Queuing Multiplier Formula Disk Queuing Multipliers SQL Query to Calculate PDIO - Batch Run Time Non-Interactie Workload - One Batch Job Selected Resource Utilization Expansion - One Batch Job Selected Resource Utilization Expansion - All Jobs Disk Utilization - Batch Run Time Batch Example: Relatie CPU Performance Multipliers RIXCXX01 Model Analysis Summary Report Recommendations Report Analysis Summary Report Recommendations Report Analysis Summary Report *NORMAL Analysis Summary Report *TRNNORM1 333 iii BEST/1 Capacity Planning Tool V5R1

11 Notices This information was deeloped for products and serices offered in the U.S.A. IBM may not offer the products, serices, or features discussed in this document in other countries. Consult your local IBM representatie for information on the products and serices currently aailable in your area. Any reference to an IBM product, program, or serice is not intended to state or imply that only that IBM product, program, or serice may be used. Any functionally equialent product, program, or serice that does not infringe any IBM intellectual property right may be used instead. Howeer, it is the user s responsibility to ealuate and erify the operation of any non-ibm product, program, or serice. IBM may hae patents or pending patent applications coering subject matter described in this document. The furnishing of this document does not gie you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation 500 Columbus Aenue Thornwood, NY U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106, Japan The following paragraph does not apply to the United Kingdom or any other country where such proisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Licensees of this program who wish to hae information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation Software Interoperability Coordinator 3605 Highway 52 N Copyright IBM Corp. 1998, 2001 ix

12 Rochester, MN U.S.A. Such information may be aailable, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this information and all licensed material aailable for it are proided by IBM under terms of the IBM Customer Agreement or any equialent agreement between us. Any performance data contained herein was determined in a controlled enironment. Therefore, the results obtained in other operating enironments may ary significantly. Some measurements may hae been made on deelopment-leel systems and there is no guarantee that these measurements will be the same on generally aailable systems. Furthermore, some measurement may hae been estimated through extrapolation. Actual results may ary. Users of this document should erify the applicable data for their specific enironment. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of indiiduals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrates programming techniques on arious operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of deeloping, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples hae not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, sericeability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of deeloping, using, marketing, or distributing application programs conforming to IBM s application programming interfaces. If you are iewing this information softcopy, the photographs and color illustrations may not appear. Programming Interface Information This publication is intended to help you to achiee high system performance. This publication documents General-Use Programming Interface and Associated Guidance Information proided by Performance Tools for iseries (5722-PT1) and Operating System/400 (5722-SS1). General-Use programming interfaces allow the customer to write programs that obtain the serices of Performance Tools for iseries (5722-PT1) and Operating System/400 (5722-SS1). This publication documents Product-Sensitie Programming Interface and Associated Guidance Information. x BEST/1 Capacity Planning Tool V5R1

13 Product-Sensitie programming interfaces allow the customer installation to perform tasks such as diagnosing, modifying, monitoring, repairing, tailoring, or tuning of this IBM software product. Use of such interfaces creates dependencies on the detailed design or implementation of the IBM software product. Product-Sensitie programming interfaces should be used only for these specialized purposes. Because of their dependencies on detailed design and implementation, it is to be expected that programs written to such interfaces may need to be changed in order to run with new product releases or ersions, or as a result of serice. Trademarks The following terms are trademarks of International Business Machines Corporation in the United States, or other countries, or both: Adanced Function Printing AFP Application System/400 APPN AS/400 Client Series e (Stylized) GDDM IBM Intelligent Printer Data Stream IPDS iseries iseries 400 MVS OfficeVision/400 Operating System/400 OS/2 OS/400 PowerPC AS PS/2 SAA System/370 System/36 Systems Application Architecture Ultimedia 400 Other company, product, and serice names may be trademarks or serice marks of others. Notices xi

14 xii BEST/1 Capacity Planning Tool V5R1

15 About BEST/1 Capacity Planning Tool (SC ) Who should read this book This book proides information about the capacity planning tool, BEST/1. This book describes how to: Model current system performance. Predict hardware upgrades needed to meet current performance objecties. Predict future hardware needs based on business growth projections. Predict performance of additional or changed applications. This manual is intended for those responsible for managing the performance of iseries serers. To use this manual effectiely, you should know the following: General system performance concepts such as response time and throughput. How to collect performance data. Refer to the Performance oeriew topic in the V5R1 iseries Information Center for information on Collection Serices. Basic system tuning concepts such as actiity leel and pool size. How to use Performance Tools commands, such as Print System Reports (PRTSYSRPT command) and Analyze Performance Data (ANZPRFDTA command). Some chapters might be more appropriate than others, depending on your leel of expertise. The following list is a suggestion for how to use this manual. Getting Started Chapter 1, Introduction to Capacity Planning, Chapter 2, Workload Concepts, and Chapter 9, Capacity Planning Examples. Basic Information Chapter 3, Building a Model Using Measured Data, Chapter 4, Building a Model Using Predefined Workloads, Chapter 5, System Configuration, and Chapter 6, Model Analysis and Calibration. Adanced Techniques Chapter 7, Modeling Changes to the System and Chapter 8, Selected Modeling Topics. Prerequisite and related information Use the iseries Information Center as your starting point for looking up iseries and AS/400e technical information. You can access the Information Center two ways: From the following Web site: From CD-ROMs that ship with your Operating System/400 order: iseries Information Center, SK3T This package also includes the PDF ersions of iseries manuals, iseries Information Center: Supplemental Manuals, SK3T , which replaces the Softcopy Library CD-ROM. The iseries Information Center contains adisors and important topics such as CL commands, system application programming interfaces (APIs), logical partitions, Copyright IBM Corp. 1998, 2001 xiii

16 clustering, Jaa, TCP/IP, Web sering, and secured networks. It also includes links to related IBM Redbooks and Internet links to other IBM Web sites such as the Technical Studio and the IBM home page. With eery new hardware order, you receie the following CD-ROM information: iseries 400 Installation and Serice Library, SK3T This CD-ROM contains PDF manuals needed for installation and system maintenance of an IBM ~ iseries 400 serer. iseries 400 Setup and Operations CD-ROM, SK3T This CD-ROM contains IBM iseries Client Access Express for Windows and the EZ-Setup wizard. Client Access Express offers a powerful set of client and serer capabilities for connecting PCs to iseries serers. The EZ-Setup wizard automates many of the iseries setup tasks. For related information, see the Bibliography on page 339. Operations Naigator IBM iseries Operations Naigator is a powerful graphical interface for managing your iseries and AS/400e serers. Operations Naigator functionality includes system naigation, configuration, planning capabilities, and online help to guide you through your tasks. Operations Naigator makes operation and administration of the serer easier and more productie and is the only user interface to the new, adanced features of the OS/400 operating system. It also includes Management Central for managing multiple serers from a central serer. For more information on Operations Naigator, see the iseries Information Center. How to send your comments Your feedback is important in helping to proide the most accurate and high-quality information. If you hae any comments about this book or any other iseries documentation, fill out the readers comment form at the back of this book. If you prefer to send comments by mail, use the readers comment form with the address that is printed on the back. If you are mailing a readers comment form from a country other than the United States, you can gie the form to the local IBM branch office or IBM representatie for postage-paid mailing. If you prefer to send comments by FAX, use either of the following numbers: United States, Canada, and Puerto Rico: Other countries: If you prefer to send comments electronically, use one of these addresses: Comments on books: [email protected] Comments on the iseries Information Center: [email protected] Be sure to include the following: The name of the book or iseries Information Center topic. The publication number of the book. The page number or topic to which your comment applies. xi BEST/1 Capacity Planning Tool V5R1

17 Summary of Changes to BEST/1 Capacity Planning Tool (SC ) There were no functional enhancements to BEST/1 in V5R1. Howeer, reisions to the V5R1 documentation include the following: CL commands were remoed from Appendix F and moed to the iseries Information Center. The Collection Serices QAPMxxxx files are aailable from the Performance oeriew topic in the iseries Information Center. These files preiously resided in the Work Management book, Appendix A. Support for the following performance monitor commands was withdrawn in V5R1: Start Performance Monitor (STRPFRMON) End Performance Monitor (ENDPFRMON) Start Performance Collection (STRPFRCOL) End Performance Collection (ENDPFRCOL) Work with Performance Collection (WRKPFRCOL) Add Performance Collection (ADDPFRCOL) Change Performance Collection (CHGPFRCOL) Note: You can still use the Performance Tools reports for data that was collected by the performance monitor in releases prior to V5R1. In many occurrences in the book we mention both the performance monitor and Collection Serices as methods for collecting performance data. Prior to V5R1, the performance monitor used the QAPMJOBS file for storing data. Collection Serices does not create the QAPMJOBS file. Instead, the QAPMJOBL file is proided for compatibility with the performance monitor and combines data from the QAPMJOBMI file and the QAPMJOBOS file. The QAPMJOBS file is created when the performance monitor database files are migrated with the Conert Performance Data (CVTPFRDTA) command to a newer release. Therefore, you will find occurrences where we refer to both the QAPMJOBS file and the QAPMJOBL file. The enhancements to BEST/1 in V4R4 include the following: The effects of ASP-based data compression are modeled explicitly. You can specify whether arms in an ASP hae compression turned on or off. An ASP compression flag exists for each ASP in the model that indicates whether or not compression is actie for any arms that support compression that are assigned to that ASP. You can change the alue of these flags to model the effect of haing compression actie or not haing it actie. The Create Disk Drie Feature display and the Change Disk Drie Feature display contain a new field that indicates what the compression oerhead is. The Work with Disk Drie Features display and the Select Disk Drie Feature display contain a new column for compression oerhead. This field represents the additional percentage of serice time when compression is actie for an ASP with arms of this drie feature. For example, if this alue is 10%, and your model contains an arm of this type assigned to an ASP that has compression actie, and the arm serice time is 6 milliseconds, then the analysis treats the arm as if it has a serice time of 6.6 milliseconds. Copyright IBM Corp. 1998, 2001 x

18 You will find no indication on the Work with Disk Resources display or the disk ersion of the Change Disk Resources display as to whether or not compression is actie for a particular arm. Logical partitioning support. BEST/1 models the performance of an indiidual logical partition based on the number of processors, main storage, and arious I/O deices that are assigned to that partition. On the Change CPU Model display, the Maximum logical partitions field represents the maximum number of logical partitions that this CPU model supports. This number cannot be greater than the number of processors. CPU models that do not support logical partitioning hae a alue of 1 for this field. On the Change CPU and the Other System Values display, the Actie Processors field shows the number of actie processors in the current logical partition. F9 (Specify other logical partitions) is a new function key that shows the Specify Other Logical Partitions display. The Specify Other Logical Partitions display shows the configuration resources that are currently attached to the serer but are attached to other partitions. These resources are also aailable to moe to the current partition. See Specifying other logical partitions on page 64 for additional information. A new Processors field is added to the Configuration display and shows a alue between 1 and 99. When the CPU supports logical partitions, the field shows actie processors per total processors. For example, you would see 2/4 in the Processors field. When the CPU does not support logical partitions, the field shows only the total number of processors. Support for main storage pools was increased from 16 to 64. CPU names no longer consist of a 3-character model and a 4-character system feature code. The naming conention for CPU names consists of a 3-character model, followed by a 4-character processor feature code and a 4-character interactie processor feature code. Each CPU has a unique 7-character system feature code, but you should be familiar with the new 11-character name. BEST/1 did not change the displays that contain the 7-character CPU information. Instead, BEST/1 issues a message that identifies the 7-character system feature code and the longer name: BEST/1 CPU model xxx yyyy refers to IBMCPU model xxx zzzz-zzzz. BEST/1 now supports threads. In preious releases, BEST/1 considered threads as part of the same job. I/O distribution within an ASP is modeled based on the capacity of each disk arm. For example, if your ASP has a1gbarmanda2gbarm, the 2 GB arm will receie twice as many I/Os as the 1 GB arm. You can specify different disk utilization guidelines for each ASP in your model. These guidelines are specified in each model on the Edit ASP display, which is accessed from the Configuration menu. The enhancements to BEST/1 in V4R5 include the following: Support for PCI nodes. Support for this new bus architecture is included in configuration checking, correcting, and recommendations. The number of aailable PCI slots is used when determining how many PCI-based IOPs can be added to a system. You can model differences in workload scaling across CPU models by specifying an application type at the transaction leel. Each application type has a performance adjustment factor for each CPU model. This factor is applied during analysis because a single CPU performance rating is no longer sufficient xi BEST/1 Capacity Planning Tool V5R1

19 to indicate how workloads will scale across CPU models. You can access the application type information by using any one of the following: F13 (Select application type) from the Create Workload display F13 (Select application type) from the Change Workload display F17 (Application types) from the Edit Transactions display See Changing the application type on page 82 for details. Summary of Changes to BEST/1 Capacity Planning Tool (SC ) xii

20 xiii BEST/1 Capacity Planning Tool V5R1

21 Chapter 1. Introduction to Capacity Planning How to Start BEST/1 Capacity planning is an ongoing process used to determine current system performance and future data processing needs. This process began before you installed your system. Your data processing requirements were estimated using data from reference accounts, system sizing guides, and recommendations from BEST/1, the capacity planning tool. From the AS/400 Main Menu, type the Start BEST/1 (STRBEST) command to start BEST/1. The BEST/1 for the AS/400 main menu appears, as shown in Figure 1. BEST/1 for the AS/400 Select one of the following: 1. Work with BEST/1 models 5. Create BEST/1 model from performance data 10. Work with results 50. General information and tutorial 60. More BEST/1 options Selection or command ===> 1 F3=Exit F4=Prompt F9=Retriee F12=Cancel F21=Basic user leel Figure 1. BEST/1 for the AS/400 Main Menu Notes: 1. When you use the STRBEST command to obtain the BEST/1 for the AS/400 menu, you can optionally specify a member name and library name. BEST/1 records session actiity in this member, if specified. If a member name is specified, the file containing this member is QACYLOGS in the library specified. 2. You can also optionally specify that the user leel is *BASIC, instead of the default user leel of *ADVANCED. When using the STRBEST command, the default for the user leel is *ADVANCED. When using GO PERFORM to start BEST/1, the default for the user leel is *BASIC. 3. When you specify STRBEST LIB, BEST/1 uses any hardware-characteristic information in library LIB. In most cases, you should ensure that no hardware table exists in the specified library or do not specify a library on the STRBEST command. When you do this, you use the latest table in library QPFR. Copyright IBM Corp. 1998,

22 The Capacity Planning Process In its simplest form, using BEST/1 is a three-step process: 1. Measure the performance data. Collect the performance data with Collection Serices. 2. Analyze the BEST/1 model. Create a representatie model of the performance data with the Create BEST/1 Model (CRTBESTMDL) command. Then analyze the BEST/1 model to find bottlenecks and to predict future system changes with the Analyze BEST/1 Model (ANZBESTMDL) command in batch mode. You can also use the Start BEST/1 (STRBEST) command to use the product interactiely to create and analyze the model. 3. Decide on the changes to make to the model. Perform What-if...? analysis and continue the analysis process until you are satisfied with the results. Decide Measure Analyze Figure 2. The Modeling Process When to Use Capacity Planning After your system has been installed, you can continue the capacity planning process using BEST/1. Perform capacity planning in the following situations: The system load grows. When you predict that the system load will increase in the olume of transactions, first run Collection Serices to gather performance data showing the current system load. Use this data to make projections as to the capability of the system s present configuration to handle the additional olume. A good way to spot performance trends is by running Collection Serices continuously and creating historical performance data with the Create Historical Data (CRTHSTDTA) command. You can then display the performance data graphically with the Display Historical Data (DSPHSTGPH) command. For more information on these commands, see the iseries Information Center. You anticipate changes to applications. If there are plans to make functional changes to one or more applications on your system, you need to understand the effects of these changes. To analyze the effect of the changes, collect and analyze performance data on the current application. Measure the changed application in a prototype enironment. The effects of the changes can then be easily determined. Current performance does not meet objecties. Conduct performance analysis if the end-user response time is longer, or if the total system throughput is less than the users need.you may want to turn to the adisor (ANZPFRDTA), a tool used to analyze data, to help you with performance analysis. See the Performance Tools for iseries book for more information on the adisor. If you conduct capacity planning with current system performance data, you can gain insight into problem areas (processing unit, disk, main storage, and so on). 2 BEST/1 Capacity Planning Tool V5R1

23 An application backlog exists. If you need to install additional applications, you need to predict their effects on the system. To do this, measure the current applications, and estimate the new applications using IBM-supplied workloads. Doing so proides you with data about the performance of the existing applications, as well as information on the performance of the new applications. Costs are becoming an issue. Use the output of capacity planning to assist you in estimating what, if any, additional hardware or programming changes should be made to improe performance or throughput. You can also use capacity planning to estimate the effects of changes to hardware as well as to programs. With this data, you can decide how to improe performance while minimizing cost, both in time and money. You are installing another iseries serer. If the new serer is to do the same type of work as your current serer but at a different throughput leel, measure your current serer and use that data to predict what configuration will meet the new throughput leel. If the new serer will do completely different work, use IBM-supplied workloads to predict the configuration. Significant Capabilities of the Capacity Planning Tool The most common use for a capacity planning tool is to enable the user to model the current serer and then see what would happen if the serer, the configuration, or the workload was changed. The user may want to know the effect on throughput, response time, CPU utilization, DASD (disk) utilization, and other parameters. The scenario of changing hardware or workload, re-analyzing and iewing results is called What if...? analysis and is a term used when discussing BEST/1 support. The following is a list of the major capabilities of BEST/1. High-leel modeling BEST/1 creates a full model (configuration and workloads) with a single pass through the performance data. Modeling of jobs with different priorities. Workload characterization More flexible workload characterization. With BEST/1, you can create workloads using most of the job attributes, define non-interactie transactions, and deal with additional types of interactie transactions. BEST/1 treats all workloads identically regardless of whether they are measured, predefined (IBM-supplied), or user-defined workloads. BEST/1 models: - Interactie workloads Dependent Work Stations (DWS) support Programmable Work Station Function (WSF) Display Station Pass-through (DSPT) Distributed Data Management (DDM) - Non-interactie workloads Batch or other non-interactie work, such as data queue jobs Client Access shared folders, file transfer, router Chapter 1. Introduction to Capacity Planning 3

24 Job classifications into workloads can be saed and reused with other measurement interals. This is an enhancement of the functions proided by functional areas, which allow you to set up groups of users or jobs to make selection easier. Enhanced support for non-interactie transactions. Each workload in the BEST/1 enironment can create interactie and non-interactie transactions. Non-interactie transactions can be defined in terms of logical I/Os, CPU seconds, communications I/Os, or print lines. In addition, the non-interactie workload can automatically increase with the interactie workload. Note: The term non-interactie transaction is used throughout BEST/1. Besides representing normally understood non-interactie work such as Client Access file transfer and shared folder, batch job, compiler, and data queue jobs, non-interactie transactions also represent Licensed Internal Code (*LIC) work and system work portions of interactie work. BEST/1 enables the modeling of additional workloads that could not preiously be done. These include the ability to model new interactie workloads that are generated when using a Programmable Work Station (PWS). Also, DSPT source and target workloads and Distributed Data Management (DDM) can be modeled. Tuning characteristics can be modeled and changed so that the affect of changing the number of memory pools, the size of memory pools and the number of actiity leels in each pool can be ascertained. Also, BEST/1 supports user-defined resource guidelines and thresholds, and high priority job leel alues (default is 20). These alues can be used instead of the alues supplied with BEST/1. Representation of storage pools and CPUs Explicit representation of all auxiliary storage pools (ASPs), including corresponding mirroring and checksum protecting. Explicit representation of storage pools and actiity leels. Preiously a single storage pool was assumed for each type of job (interactie, batch, spool), with jobs of different classes not allowed to share pools. Explicit representation of CPU priorities. BEST/1 shows the job priorities in their actual order, whether spool, interactie, or batch. Definition within the model, of multiple ASPs and the ratio of I/O operations per ASP. It is also possible to model the leel of data protection within each ASP, for example, checksum or mirroring, or none. The 9337 Disk Array Subsystem - Base and High Aailability models (see note) are supported. The 9337 models are supported similarly to 9336 disks, and are modeled uniquely because of their additional protectie I/O operations. Note: The 9337 Disk Array Subsystem High Aailability model is used generally. Besides using this model, the following can be used: 660x-070 features 671x-070 features 690x-070 features , 115, 120, 125, , 222, 217, 227, , 442, 482 For more information on special hardware naming conersions, see Appendix H. BEST/1 Hardware Name Mapping. 4 BEST/1 Capacity Planning Tool V5R1

25 BEST/1 Performance Statistics Hardware support BEST/1 proides an interface to its CPU, disk parameters, and communications hardware that can be used to model new CPU models or disk hardware in between releases of the Performance Tools licensed program. Announcement of new hardware generally includes new input into BEST/1 tables. Externalization of hardware characteristics and utilization guidelines and thresholds. The user can now model new hardware as it is announced and change analysis guidelines and thresholds. Externalization of sync read guidelines. Communications support Support for indiidual communications IOPs and lines, for both Local Area Network (LAN) and Wide Area Network (WAN). In addition, support for the total number and serice time for LAN controllers and WAN work station controllers. Graphics support Separation of graph data from graph formats. Data can now be iewed in a ariety of formats. Oerlay of up to fie results members. Ability to change axis range for more accurate data representation. BEST/1 proides the following performance statistics. Aerage hardware utilization CPU DASD Controllers Communications resources BEST/1 computes, produces output for and contains guidelines for: aerage central processing unit (CPU) utilization, disk arm utilization (percent busy), disk controller utilization, disk IOP utilization, communications line utilization, communications IOP utilization, local and wide area network (WAN) workstation controller, local area network (LAN) controller utilization, multifunction IOP utilization, and disk, LAN, WAN, and Integrated Netfinity Serer IOA utilization. The performance data for memory utilization is not directly apportioned to indiidual jobs or *LIC tasks. As a result, BEST/1 s capability to model memory is ery conseratie. This means BEST/1 may recommend additional memory before it is actually needed. Note: There is no system measurement of LAN controller and WAN work station controller utilization. This means, BEST/1 calculates utilization based on serice time and number of controllers, in conjunction with remote traffic on controllers. Aerage internal and external response times The aerage internal response time is based on the performance data in the QAPMJOBS file (performance monitor) and QAPMJOBL file (Collection Chapter 1. Introduction to Capacity Planning 5

26 Serices). External response time is estimated based on the number of characters transmitted and the line speed. BEST/1 does not use 5494 release leel 1.1 external response time for DWS deices. Aerage interactie and non-interactie throughput Interactie and non-interactie work is shown in transactions per hour. Aerage disk I/O s by auxiliary storage pool (ASP) and input/output processor (IOP), input/output adapter (IOA) BEST/1 disk output shows the aerage number of disk I/Os spread across ASPs, IOPs, and IOAs. Aerage number of jobs in each storage pool BEST/1 shows the aerage number of both actie and ineligible jobs that are either in the storage pool or waiting to come into the storage pool. Sync read rate for each storage pool The number of synchronous reads generated by the jobs running in the storage pool is shown as sync reads per second. BEST/1 Assumptions and Conditions BEST/1 is an analytic modeling tool, which proides expert ealuations and configurations. As such, the results depend entirely on the accuracy of the input, the analytic model, and the rule base for ealuations and configurations. Major Assumptions As with most capacity planning, there are some conditions or assumptions present. The following list represents the major assumptions under which BEST/1 performs its modeling work. Data is collected on a well-tuned, stable system. When measured data is collected, the system workload should be heay, but operating at an acceptable leel to the customer. One hour s worth of measured data should be selected for internal with fairly leel system loads. For interactie work, typically 1 2 hours is good. For non-interactie work, the selected period is after 2 6 hours. BEST/1 uses sample performance data. Data collection is done on a system in which all pool sizes and actiity leels are set to reasonable alues, secondary paging (thrashing) does not occur, and if excess storage is present, working set sizes are appropriate for the actiity leel of the pool. The time slices should be large enough to minimize actie-to-ineligible transitions (shown as A-I in the Performance Tools Transaction Report Interactie Jobs output). The workload is reasonably homogeneous. That is, one particular program within a workload is not causing a resource limitation. The workload is steady-state. This means that the number of interactie users and batch tasks is relatiely constant. The proportion of a workload s I/Os to an auxiliary storage pool (ASP) is based on the proportion of total I/Os handled by the disks on that ASP. Read and write operations are distributed on the same basis. There are no seere resource limitations (bottlenecks) in the system. That is, none of the primary deices (processing unit, disk, and so on) are excessiely utilized. All jobs specified as actie are performing work. 6 BEST/1 Capacity Planning Tool V5R1

27 The aerage serice time of each disk request is the same. All disk requests are spread eenly across all disk dries in each ASP. The actiity on the local work station IOPs is spread eenly across all IOPs, and the utilization of each IOP is the same. The serice time and response time depend on the application. All controllers are equally distributed across all communications lines for LAN and WAN. All local, LAN, and WAN controllers hae the same serice time, respectiely. As the system approaches saturation (high utilization) of one or more resources, the accuracy of the analytic model for response time prediction diminishes. An analytic model is best used to predict when a resource will become saturated. Knowing when a resource will become saturated allows you to plan your workloads and hardware upgrades. Figure 3 depicts the range of results you can expect from BEST/1. At the higher utilizations, the range of the results is greater. Because BEST/1 uses an analytic model, the results are not precise. For example, calculated aerage response times of 2 or 3 seconds are considered alid, when in actuality users could be experiencing an aerage response time of 2.4 seconds. Note: BEST/1 reports the aerage response time. The actual response times ary, based on the applications you run. Figure 3. Range of Results Using the BEST/1 Capacity Planning Tool BEST/1 calculates the number of disk arms required to achiee acceptable performance based solely on the number of disk I/Os per second. BEST/1 does not calculate the disk storage requirements for programs, files, and libraries. Major Conditions The major conditions in BEST/1 that you should be aware of are: No specific batch run time (also called batch window ) modeling support. Chapter 1. Introduction to Capacity Planning 7

28 BEST/1 supports modeling non-interactie workloads (batch is a subset of non-interactie) CPU and disk resource consumption against any other system work. Output proides a rated throughput for batch expressed in transactions per hour. This information can be used to estimate changes in throughput based on configuration or workload changes. Howeer, BEST/1 does not proide detailed batch job run time (batch window) or job scheduling analysis. Predicting Batch Transaction Throughput Example on page 157 contains an example showing how to control model parameters to achiee changes in logical disk I/Os per hour. You can use the relatie increase in transactions per hour against measured run time to estimate a new run time. No default configuration When creating a model from predefined workloads, BEST/1 does not default to any hardware configuration. You must use the Configuration Menus to select an IBM-proided configuration that may need additional modification. BEST/1 messages direct you to the configuration step. Performance Modeling of measured data may take a significant amount of time and CPU resource. Care should be taken that modeling does not impact an already heaily loaded system. You need to experiment with your own set of measured data and CPU model to schedule modeling with the best compromise between obtaining output and system resource impact. Note: An alternatie is to use the Create BEST/1 Model (CRTBESTMDL) and Analyze BEST/1 Model (ANZBESTMDL) commands in a batch program to aoid major impacts to the high priority work on the system. Print spooling BEST/1 assumes that all printing support modeled makes use of the system spooling functions. Miscellaneous Diskette, tape, and CD-ROM support is not modeled. BEST/1 Modeling Process Regardless of current assumptions and conditions, BEST/1 proides capacity planning for a wide range of iseries work. The following steps represent the typical modeling process for BEST/1. You can accomplish these steps in batch by using Performance CL commands, or run BEST/1 interactiely with the STRBEST command. It is assumed that before you begin this process you collect and erify measured data on a well-tuned system. 1. Create the Model a. Assign work to workloads. Workloads can consist of measured, IBM-supplied predefined workloads, or user-defined workloads in any combination. Each workload has one or more functions. Each function has one or more transactions. Measured data includes user jobs, OS/400 jobs, and *LIC tasks. BEST/1 proides implicit and explicit assignment of work to workloads by job classifications such as user ID, job name, job type, and communications line. 1) Define and erify workload functions. 2) Define and erify function transactions. b. Define and erify objecties: 8 BEST/1 Capacity Planning Tool V5R1

29 1) Number of jobs. 2) Response time. 3) Transactions per hour (throughput). For measured data these are generated by BEST/1 from the workload assignments. 2. Work with the Model After the model has been created, use the Work with Model display to: a. Work with workload, function, and transaction definitions. For each workload erify if the function and transaction definitions processed by BEST/1 are reasonable. b. Verify acceptability or change objecties. c. Analyze the model with or without recommendations. 3. Work with Results a. Compare analysis summary to measured data, if used. b. Optionally calibrate the model. c. Do What if...? analysis for workloads. 1) Add more work stations 2) Add new applications 3) Increase batch workload d. Do What if...? analysis for memory pools or ASPs 1) Change the number or sizes of memory pools 2) Change the actiity leels in a memory pool 3) Change the number of ASPs 4) Change protection leel to checksum or mirroring e. Do growth analysis 4. Analyze results from growth or hardware changes 5. Print the tables or plot the graphs 6. Sae the model and results 7. Use the results as input to other tools Major Options for Modeling with BEST/1 The major options on the BEST/1 for the AS/400 main menu that are discussed in this chapter are: Work with BEST/1 models Work with results More BEST/1 options Two user leels exist when working with capacity planning actiities. The two leels are *BASIC and *ADVANCED. How you start the BEST/1 function determines your user leel. If you use the STRBEST command, the default user leel is *ADVANCED. If you use the GO PERFORM, option 4, the default user leel is *BASIC. Work with BEST/1 Models Use the Work with BEST/1 Models display, as shown in Figure 4 on page 10 to create a new model or work with an existing model. A model can be any combination of measured, predefined, or user-defined work. Work with Models lets you Create, Copy, Work with, Delete, Print, or Rename a model. You can Chapter 1. Introduction to Capacity Planning 9

30 define and classify jobs (units of work) into workloads (groups of work that can be modeled as a distinct unit of work), to analyze and grow the model, work with the results, and graph and sae the modeling results. Library... JONES Name Work with BEST/1 Models Type options, press Enter. 1=Create 3=Copy 4=Delete 5=Work with 6=Print 7=Rename Opt Model Text Date Time _ BEST1MODEL 04/21/93 10:26:49 _ APRDATA Data collected at /15/93 10:45:31 Command ===> F3=Exit F4=Prompt F5=Refresh F9=Retriee F12=Cancel F15=Sort by model F16=Sort by text F19=Sort by date and time Bottom Figure 4. Work with BEST/1 Models Display You can create a BEST/1 model interactiely or as a batch job (recommended). After the model has been created you need to use the Work with BEST/1 Models display to work with that model. If you choose a specific model with option 5 (Work with) from the Work with BEST/1 Models display, the next display which appears is the Work with BEST/1 Model menu. Again, depending on how you started the BEST/1 function determines which options are aailable from the Work with BEST/1 Model display. Note: Press F21 to toggle between the two user leels. Basic User Leel You see the menu for the basic user leel in Figure 5 on page 11. From this menu you can work with seeral options. The options include defining configurations, analyzing models, and predicting results. This menu proides access to capacity planning functions and high-leel modeling. You should hae some general knowledge of modeling concepts and capacity planning concepts. 10 BEST/1 Capacity Planning Tool V5R1

31 Work with BEST/1 Model Performance data...: BESTDATA (Q ) Model/Text...: BEST1MODEL Select one of the following: 7. Specify workload growth and analyze model 10. Configuration menu 11. Work with results 50. About BEST/1 More... Selection or command ===> F3=Exit F4=Prompt F9=Retriee F12=Cancel F15=Sae current model F17=Analyze with ANZBESTMDL F22=Calibrate model F24=More keys Model BEST1MODEL has been read Figure 5. Work with BEST/1 Model Menu Basic User Leel Adanced User Leel You see the menu for the adanced user leel in Figure 6. From this menu you can work with seeral options. The options include workload definitions, objecties, and additional model analysis options. This menu proides access to capacity planning functions and low-leel modeling. You should hae a ery good working knowledge of modeling concepts and capacity planning concepts. Work with BEST/1 Model Performance data...: BESTDATA (Q ) Model/Text...: BEST1MODEL Select one of the following: 1. Work with workloads 2. Specify objecties and actie jobs 5. Analyze current model 6. Analyze current model and gie recommendations 7. Specify workload growth and analyze model 10. Configuration menu 11. Work with results More... Selection or command ===> F3=Exit F4=Prompt F9=Retriee F12=Cancel F15=Sae current model F17=Analyze with ANZBESTMDL F22=Calibrate model F24=More keys Model BEST1MODEL has been read Figure 6. Work with BEST/1 Model Menu Adanced User Leel Chapter 1. Introduction to Capacity Planning 11

32 Aailable Menu Options Table 1 identifies the BEST/1 functions that are aailable for the *BASIC user or the *ADVANCED user. The difference in function between the two leels is to allow the inexperienced user to focus on the primary capacity planning actiities. Table 1. *BASIC and *ADVANCED User Leel Functions Aailable Function *BASIC *ADVANCED Working with workloads No Yes Specifying objects No Yes Specifying actie jobs No Yes Analyzing current models No Yes Giing recommendations No Yes Specifying workload growth Yes Yes Analyzing models Yes Yes Accessing configuration menu Yes Yes Working with results Yes Yes Accessing information about BEST/1 Yes Yes The following paragraphs proide summary descriptions of all the options that can be selected on the Work with BEST/1 Model display. Work with workloads Use the Work with Workloads display to reiew the accuracy of the function and transaction details of a workload deried by BEST/1. The Work with workloads and Specify objecties and actie jobs options can be part of both the create model and the analyze model processes. Specify objecties and actie jobs Use Specify objecties and actie jobs to alidate the number of actie jobs. For the initial modeling process you should accept the BEST/1 alues. Initially leae the throughput and response time objecties as zeros for all workloads. This indicates no objecties, therefore no exceptions are generated regardless of predicted alues. You may change these alues, as a way of adding growth to the current model, after the model has been created. Analyze current model Analyze the model takes the current hardware configuration and workload definitions and analyzes this data. Analyze model produces a set of exceptions. Analyze current model and gie recommendations Analyze with recommendations consumes additional CPU and makes recommendations for new hardware, including CPU model, main storage size, and the number of additional hardware features. Specify workload growth and analyze model You may select the workload growth rate(s), number of periods to model, and whether you want BEST/1 to automatically upgrade hardware according to its guidelines/thresholds. The functions accessed from this option are termed manual growth ersus automatic growth. Growth support is discussed in Chapter 7. Modeling Changes to the System. Configuration menu 12 BEST/1 Capacity Planning Tool V5R1

33 The configuration menu option leads you into additional options for iewing and changing CPU, local and WAN work station controllers, LAN controllers, communications support, disk, storage pools, and ASPs. Work with Results Work with Results enables you display or print with current or preiously saed modeling results by iewing reports and graphing results. About BEST/1 This menu proides introductory information to new BEST/1 users. It includes BEST/1 naigation, creating a measured model, analysis issues, descriptions of reports and graphs, an oeriew of BEST/1 external files, and a summary of enhancements in the current release. Work with Results After any of the analyze functions (options 5, 6, 7) has completed, you can work with the analysis results as discussed after Figure 7. Work with results lets you look at seeral categories of results including analysis summary, recommendations, and workload reports. All the reports proide the following function key support: Press F10 (Re-analyze model) to analyze the model again in the method as the preious analysis (whether or not to proide recommendations). Press F15 (Configuration menu) to change hardware configuration. Press F17 (Analyze multiple points) to automatically grow the work with default growth rate and ten growth periods. Press F18 to change actie jobs or response times and throughput objecties. Press F19 to work with workloads. Printed Report Text... Type options, press Enter. 5=Display 6=Print Work with Results Opt Report Name Measured and predicted comparison Analysis Summary Recommendations Workload Report ASP and Disk Arm Report Disk Resources Report Main Storage Pool Report Communications Resources Report All of the aboe Bottom F3=Exit F12=Cancel F14=Select saed results F15=Sae current results F18=Graph current results F19=Append saed results F24=More keys Figure 7. Work with Results Display The following proides summary descriptions of the options that can be selected on the Work with Results display. Analysis Summary Chapter 1. Introduction to Capacity Planning 13

34 The analysis summary shows oerall hardware configuration, resource utilization, response time, and transactions per hour (throughput). In addition to the general report function keys, you can also use F11 (Measured and predicted comparison) to compare modeled and measured data results. A large difference between measured and predicted resource utilization or response time should be examined to determine if the measured data is appropriate for further modeling efforts. The Measured and Predicted Comparison display proides an automatic interactie response time calibration function. For resource calibration, manual calibration is initiated with function key F22 from the Work with BEST/1 model display. For more information about calibration, see Chapter 6. Model Analysis and Calibration. Recommendations You can reiew the BEST/1 recommendations to see messages that suggest pool size or actiity leel changes, indicate resource utilization problems, and identify hardware changes. The guideline and threshold alues shipped with BEST/1 are listed in Chapter 7. Modeling Changes to the System. Workload Report The workload report shows for each workload CPU utilization, transaction throughput, LAN and WAN response time, and response time components. Response time components are CPU, disk I/O, pool, communications, and other. A large other would indicate that some kind of exceptional wait condition (object lock,...) is present. ASP and Disk Arm Report This report shows, for each auxiliary storage pool (ASP), the number of disk arms and a set of disk arm statistics, such as Percent busy and I/Os per second. Disk Resources Report This report shows, for each IOP doing disk processing, and for each disk IOA, the IOP and IOA utilization and number of disk arms. The Disk Resources Report and the ASP and Disk Arm Report show the same disk arm statistics. Main Storage Pool Report This report shows, for each pool, its size and actiity leel, its actie-to-ineligible alues, and the number of synchronous database and non-database reads per second. The number of synchronous reads per second is an approximation of the number of database and non-database page faults per second. The Work Management book contains guidelines for page faults per second. For more information about how synchronous reads relate to page faults, see Memory Modeling on page 135. Communications Resources Report This report shows communications IOP and IOA utilization and information for each communications line resource, such as line speed and response time per transaction. The Measured and Predicted Comparison report can be accessed from the Work with Results display when the current model is created from performance data and a single-period analysis is done. The Work with Results display proides function keys to select preiously saed results, sae the current results, graph the current results, and append preiously 14 BEST/1 Capacity Planning Tool V5R1

35 saed results to the current results. Append results adds all the periods of the appended results to the current results. This enables you to mimic the effects of a greater number of analysis periods. More BEST/1 Options More BEST/1 Options menu enables you to iew and change hardware information and modeling guidelines as well as migrate OS/400 MDLSYS files and System/36 performance data into formatted data that BEST/1 can use. The six Work with member options enable you to copy, delete, print, and rename the arious members in a specified library. The following is a description of the options on the More BEST/1 Options display. Select one of the following: More BEST/1 Options 1. Work with job classification members 2. Work with workload members 3. Work with configuration members 4. Work with hardware members 5. Work with results members 6. Work with analysis parameters members 10. Hardware characteristics menu 11. Analysis parameters menu 20. Conert MDLSYS files 21. Migrate S/36 workload 51. Moing from MDLSYS to BEST/1 Selection or command ===> F3=Exit F4=Prompt F9=Retriee F12=Cancel Figure 8. More BEST/1 Options Menu Work with job classification members Job classifications identify how jobs are grouped to form workloads. In addition to the options listed aboe, you can change job classification found in the specified library. Work with workload members A workload member contains information about a single workload. Work with configuration members A configuration file contains a complete description of saed OS/400 configurations, including CPU, elements of the disk subsystem, storage pools, and communications resources. Work with hardware members A hardware file contains all the physical hardware resources recognized by BEST/1. Work with results members Results members contain the data used to generate BEST/1 reports and graphs. Work with analysis parameters members Guideline members contain the guideline and threshold alues used to determine configuration changes during analysis. Chapter 1. Introduction to Capacity Planning 15

36 Hardware characteristics menu Select this option to work with CPU models, disk IOPs, disk dries, communications IOPs, and line speeds. Analysis parameters menu The analysis parameters menu enables you to edit utilization guidelines, synchronous reads guidelines, and global paging behaior alues. Conert MDLSYS files Use this option to conert MDLSYS files from preious product releases. See Appendix C. Conerting BEST/1 Models and Migrating Data for more information. Migrate S/36 workload Select this option to migrate an S/36 workload to a BEST/1 workload. See System/36 Migration Utility on page 272 for more information. Moing from MDLSYS to BEST/1 Select this option to display information pertinent to current MDLSYS users. Note: BEST/1 members from preious releases conert automatically when read. Other Considerations From the More BEST/1 Options display, you can create your own hardware resources, such as CPU models or disks. The hardware characteristics option enables you to introduce information for modeling new hardware announcements in between releases of the Performance Tools licensed program. Any such hardware announcement will generally proide the modeling parameter alues needed for entry into BEST/1 displays. You can also edit the IBM-supplied guidelines and thresholds according to your specific requirements. You can sae these members and restore them for later modeling. For example, you may want to use different guidelines for CPU utilization and disk arm utilization for different models. Capacity Planning Files and Usage BEST/1 uses performance data files for measured data. In addition to these QAPMcccc files, BEST/1 creates and uses files that are accessed when creating and analyzing models. These files are: A Model file contains the information used by BEST/1. It is a collection of workloads, performance objecties and a system configuration. A list of the existing models appears on the Work with BEST/1 Models display. A Workload file contains the information associated with a single workload. Workload files are created when you use the Sae workload to workload member option on the Work with Workloads display. This function is especially useful for transferring workloads between models. A Configuration file contains the description of a specific system configuration. This file can be used to include a specific configuration for analysis without manually changing multiple system configuration alues or oerlaying the current workload characteristics. You can do this on the Configuration menu. A Job classification file identifies how jobs running on the system are grouped into workloads. Jobs can be classified using the following categories: user ID, job type, job name, account code, job number, subsystem, pool, controller, communications line, and functional areas. 16 BEST/1 Capacity Planning Tool V5R1

37 A Hardware characteristics file contains the hardware resources that are included in the modeling session. This file can be updated when new hardware is announced between releases of the Performance Tools. This file contains the performance characteristics and configuration policies (alid configuration possibilities). You can copy, change, and use this file based on your own requirements. The IBM-supplied file in the QPFR library. An Analysis parameters file contains the utilization guidelines and thresholds that are used by BEST/1 to recommend hardware upgrades. It also contains globally defined transaction paging characteristics, guidelines and thresholds. A Results file contains the performance predictions made by BEST/1 during the analysis of a model. It can be printed or shown graphically. A Graph format file identifies the format of the graph used to display the data. Figure 9 represents the relationship between OS/400 jobs and BEST/1 model workloads, functions, and transactions. Figure 9. Relationship of Jobs to BEST/1 Workloads The BEST/1 model is composed of work actie during a performance data collection period or predefined work or user-defined work. BEST/1 support requires implicit or explicit assignment of jobs/tasks to workloads, functions, and transactions. Chapter 1. Introduction to Capacity Planning 17

38 18 BEST/1 Capacity Planning Tool V5R1

39 Chapter 2. Workload Concepts Job Classification The purpose of this chapter is to proide a description of BEST/1 support for assignment of work to workloads, definition of functions and transactions within a workload, and specification of number of actie jobs, response time, throughput, and other alues. By properly specifying workloads and actie jobs, you should feel comfortable that the model represents the work to use for capacity planning. Note: Specifying workloads and actie jobs is only aailable with the Adanced User Leel. Classifying jobs into workloads is one of the most powerful of BEST/1 support features as it proides a superset of MDLSYS capabilities in this area. User jobs, operating system jobs, and *LIC tasks represent the work that must be associated with a workload in a model. To ease the workload definition process, BEST/1 proides a default set of workloads based on job type. It is highly recommended that you use the default job classification for most modeling. Note: The default job classification is automatically used when you select Option 5 (Create BEST/1 model from performance data) on the BEST/1 main menu. The following sections describe many of the options aailable within BEST/1 for job classifications. When deciding on workload assignments for work from measured data, BEST/1 proides options for classifying jobs by any one category as follows: User ID Job type Job name Account code Job number Subsystem Pool Control unit Communications line Functional area When you select one of these options from the Specify Job Classification Category display, you are presented with a secondary display where you can enter specific alues alid for the option selected. In many instances, you would ask BEST/1 to query the measured data by pressing F9 (Display alues from data), for the alues specific to this particular data. For example, after selecting Job type, you can hae BEST/1 query the QAPMJOBS file (performance monitor) or the QAPMJOBL file (Collection Serices) and present you with a list of all work grouped into BEST/1 job types such as interactie, batch, and Client Access. Copyright IBM Corp. 1998,

40 Figure 10 and Figure 11 show job type Edit Job Classifications and Assign Jobs to Workload (showing the function key F9 query results) displays. Edit Job Classifications Enter workload names and category alues which are assigned to each workload, press Enter. Jobs with unassigned alues become part of workload QDEFAULT. Workload Job Type Workload Job Type Workload Job Type F3=Exit F9=Display alues from data F12=Cancel To display alues from the performance data, press F9 More... Figure 10. Edit Job Classifications by Job Type Example Assign Jobs to Workloads Workload... Type options, press Enter. Unassigned jobs become part of workload QDEFAULT. 1=Assign to aboe workload 2=Unassign Number of CPU I/O Opt Workload Job Type Transactions Seconds Count _ *AUTOSTART _ *BATCH _ *CLIENTAC _ *EVOKE _ *INTERACTV _ *PTHRUTGT _ *MONITOR _ *SYSTEM _ *LIC _ *WRITER _ *SCPF Bottom F3=Exit F12=Cancel F15=Sort by workload F16=Sort by job type F17=Sort by transactions F18=Sort by CPU seconds F19=Sort by I/O count Figure 11. Assign Jobs to Workloads by Job Type Example BEST/1 Job Types You are free to assign *AUTOSTART, *BATCH, and *EVOKE into separate workloads or into a single workload, for example, BATCHBAS. *MONITOR represents subsystem monitor job work. *EVOKE represents work started by receied program start requests for APPC and other communications protocols and internal system INTRA eokes. 20 BEST/1 Capacity Planning Tool V5R1

41 *ADV36 represents all Adanced 36 jobs and tasks running as a guest on OS/400. *CLIENTAC4 represents all Client Access jobs and tasks, except for those items noted under type *DDM. *PTHRUTGT represents normal Display Station Pass-Through target work. *SYSTEM represents all other OS/400 work, which includes work done by system jobs QSYSARB, QSYSARB2, QSYSARB3, QSYSARB4, QSYSARB5, QLUS, QPFRADJ, QDBSRVn, QDCOBJn, QJOBSCD, QALERT, and QSPLMAINT. For additional information regarding system jobs, see the Work Management book. *LIC represents licensed internal code tasks. BEST/1 has internal algorithms to assign *LIC tasks to the appropriate workloads. For more information on *LIC tasks, see How BEST/1 Handles Licensed Internal Code Tasks on page 42. *WRITER represents spool writer jobs. *LIC represents all *LIC task work, including work done on behalf of user or OS/400 jobs. When you collect performance data, the *SCPF work represents work done by the SCPF job. This includes running some low priority and possibly long-running system functions. One known function is the management of log QHST. Defining Work to the Model Additional job types not shown in Assign Jobs to Workloads by Job Type example include *DDM (DDM target serer), *READER (spool readers), and *PTHRUSRC (Display Station Pass-Through source work). *DDM work represents normal target DDM (serer) work, Client Access Shared Folders type 0 and 1, and original client Submit Remote Command work. Chapter 3. Building a Model Using Measured Data proides more details with a specific example. A hierarchical approach is used to model work on the system. A model contains one or more workloads. Each workload has one or more functions and each function has one or more transactions. Figure 12 on page 22 is a graphical representation of the relationships between the BEST/1 model components. Chapter 2. Workload Concepts 21

42 Figure 12. Workload Components of a Model Workload Definition A workload is represented by a set of one or more functions. Each function groups together streams of transactions that hae been created by specific jobs or tasks. These key attributes of a workload include the number of local, LAN, and WAN jobs performing this specific work for each job function, the number of interactie and non-interactie transactions per job, the workload type (*NORMAL or *BATCHJOB), and the system resources required for each transaction. The following represents key points about a BEST/1 workload: A workload is the main unit of input to the capacity planning tool. A workload is used to represent a grouped set of actiity (work) to be used in capacity planning. A measured workload is the equialent of a measured profile in MDLSYS. A predefined workload is the equialent of a predefined profile in MDLSYS. A user-defined workload contains data proided by the user. Note: Working with workloads is normally aailable only at the adanced user leel. Workloads can come from different sources: Measured Workload A measured workload is a collection of measured data that describes how the system is used by that set of system actiity. It is a summary of the collected job data and task data. This data includes internal response time, throughput, number of disk I/Os per transaction, and processing time per transaction. BEST/1 supports one workload describing all system actiity or system actiity grouped into multiple workloads. BEST/1 uses sample data. BEST/1 directly accesses the performance data when a model is created. Predefined Workload Predefined workloads are measured workloads proided by IBM. They are supplied with BEST/1 in library QPFR. Data is proided by IBM for standard applications with each new release of Operating System/400 (OS/400). These 22 BEST/1 Capacity Planning Tool V5R1

43 workloads assist in determining the effect of a new application on the system, without haing to perform your own benchmark to obtain measured data. Predefined workloads are useful as a first approximation, if the applications to be modeled can be made from a combination of predefined workloads. It is often more accurate to use measured workloads which more closely resemble the true customer enironment. The BEST/1 predefined workloads are grouped into workload groups to more easily classify the work they represent. The groups are: OFFICE COMMERCIAL BATCH SPOOL SERVER INDUSTRY COMMERCIAL Workload Group The predefined workload group COMMERCIAL includes the Repeatable Approach to Measuring Performance-COBOL (RAMP-C). IBM uses this set of programs to determine serice leels for comparing system performance. RAMP-C is composed of four interactie transactions that range from simple to complex, depending on the amount of processing unit, disk, and main storage the transaction uses when it runs. You can mix these transactions in any combination to match what you beliee to be the complexity of your interactie application. Refer to COMMERCIAL Workload Group on page 249, for more information. The predefined workload group Commercial also includes the Relational Transaction Workload (referred to in BEST/1 as SQL RTW). RTW consists of six different transactions that range from simple to medium complexity. Two of the transactions perform inentory tracking functions, while the other four transactions perform stock control functions. Each RTW workstation executes all six transactions per standard mix. Refer to SQL RTW Workload on page 250 for more information. BATCH Workload Group The predefined workload group BATCH, is used to predict the effect of batch processing on the interactie performance. These batch programs range from processor-intensie to disk-intensie. Processor-intensie batch programs do not significantly affect interactie performance (assuming batch has a lower priority than interactie and it runs in its own storage pool). A disk-intensie batch program may increase the interactie response time if the disk utilization is high. SPOOL Workload Group The predefined workload group SPOOL is used to predict the effect of spool processing on the interactie performance. Printers can be attached to a local or remote workstation controller. If the total number of lines printed per minute is large, the controller and remote line utilization can become large, causing the interactie response time to increase. Workloads range from simple printing to complex printing using Adanced Function Printing (AFP) support. SERVER Workload Group The predefined workload group Client/Serer belongs to the application serer category. This means there is an application program running on a serer that is exchanging information with an application program running on the PC. Refer to SERVER Workload Group on page 263 for more information. Chapter 2. Workload Concepts 23

44 INDUSTRY Workload Group The predefined workload group Industry proides a set of OS/400 workload definitions which are a composite sketch of real iseries serers. Refer to INDUSTRY Workload group on page 265 for more information. User-Defined Workload The user-defined workloads contain similar data to measured workloads, but the data must be proided by the user. The following items need to be defined: Workloads: Workload type, functions per user per hour and key/think time. Functions: Transactions per function. Transactions: CPU time per transaction, permanent writes, synchronous and asynchronous database (DB) read and write operations, and synchronous and asynchronous non-database (NDB) read and write operations. For more information on these parameters, consult the Performance Tools for iseries book. This method is difficult when starting with minimal data. Howeer, an easier approach would be to start with existing measured or predefined workloads and changing some of the parameters. You should understand the ramifications of making such changes, as indiscriminate changes may affect the accuracy of the model analysis results. Note: The Work with Workloads display supports saing a defined workload. This saed workload can later be added to an existing or new model with the Work with Workloads display. This proides a way of combining workloads from different sets of performance measurement data for modeling on a single CPU. Function Definition In general, a function is defined in terms of: 24 BEST/1 Capacity Planning Tool V5R1 A set of transactions performed by the user or job to accomplish a business operation such as calendar update or inoice. The set of transactions run in a set of storage pools, each at a gien priority number. Both interactie and non-interactie transactions work together to accomplish a function. Key/think time (N/A for non-interactie functions). Functions are defined to the model in terms of: Usage mode. Casual, interrupted, or steady usage mode influences the aerage key/think time and the number of functions per user. Casual mode is considered 2 characters keyed per second. Interrupted mode is 4 characters per second and steady mode is 5 characters per second. Workloads with only non-interactie transactions hae a usage mode of 4 (N/A). The default is for interrupted usage. Functions per user. A function represents the number of times that the function is called by each user of this workload; it is expressed in terms of functions per user per hour. For measured data, BEST/1 defaults to 1 function per user per hour, therefore the number of transactions per function also equals the number of transactions per user per hour. For predefined workloads, multiple functions may be defined based on the specific workload. Number of transactions per function. This represents the number of transactions generated each time the function is performed. The underlying transactions may consist of interactie, non-interactie or a combination of both types.

45 Aerage key/think time (K/T). This represents the aerage number of seconds that a user of the function requires from the receipt of one response until the end of keying the data for the next transaction and pressing the enter key. Key/think time is N/A for non-interactie transactions. A function consists of one or more transactions. The Change Workload display in Figure 13 shows the basic data relating transactions to functions. The alue under the heading Functions per user actually is functions per user per hour. The number of interactie or non-interactie transactions per hour can be calculated by multiplying transactions per function by functions per hour. Interactie and non-interactie transactions should not be added together, as they hae ery different characteristics. Change Workload Workload...: INTER CPU architecture....: *RISC Type changes, press Enter. Workload text... Measured from TESTLIB (Q ) Workload type... *NORMAL F4 for list Usage mode =Casual, 2=Interrupted, 3=Steady, 4=N/A Functions Ag K/T Tns per Function Function Text per User (secs) Inter Non-inter Function of INTER Bottom F3=Exit F4=Prompt F6=Work with functions F9=Specify chars to comm lines F10=Specify I/Os to ASPs F12=Cancel F24=More keys Figure 13. Change Workload Display Figure 14 shows the Change Function display. This display shows the number of physical I/Os (including DB and NDB I/Os) done by each transaction type. The total number of I/Os per function per user can be calculated by multiplying the number of transactions per function by the number of I/Os per transaction and summing the results for each transaction type. A similar calculation can be done to determine the total amount of CPU time used per function per user. The alue shown under the column heading CPU Time is in B10 CPU seconds. This can be conerted to the correct model by diiding by the appropriate Relatie Internal Performance factor shown in Relatie CPU Power Table on page 287. BEST/1 transaction detail support requires the CPU component be expressed in terms of B10 CPU seconds. During the analysis step these times are conerted (internally) to the proper alues based on the CPU listed in the model configuration details. The expression of the CPU time in B10 seconds allows for workload portability to other serers. BEST/1 s assumption is that the hardware characteristics file will always list CPU models in terms of their relatie performance to a B10. The B10 is the standard relatie performance factor used in all OS/400 documentation comparing CPU models. Chapter 2. Workload Concepts 25

46 BEST/1 assigns CPU power to specific models using the Relatie Internal Processor Performance rating as measured by IBM. In some cases, the rating for a specific CPU model or feature will differ from other published reports which quote the Relatie Performance of the system based on a specific benchmark. Note: The performance of RISC-based CPU models is now published by IBM using the CPW rating. BEST/1 continues to use the Relatie Internal Processor Performance rating. Change Function Workload...: INTER Measured from TESTLIB (Q ) Function...: INTER Change fields, press Enter. Function text... Function of INTER Key/Think time Seconds Additional delays....0 Seconds Transaction Pool Transactions CPU Time Total Type ID Priority per Function (Secs) I/Os Transaction Type: 1=Interactie, 2=Non-interactie Bottom F3=Exit F6=Work with transactions F12=Cancel Figure 14. Change Function Display Transaction Definition A transaction is the smallest unit of work in a workload definition. It includes: Interactie Transactions. Interactie transactions represent the work done by the system when you press the Enter key or a function key. The end of the transaction occurs when the new display appears and the workstation is capable of additional input. Non-interactie Transactions. Non-interactie transactions represent the work done by jobs and tasks which are not connected to a workstation. Examples include batch jobs and system actiity which may hae occurred as a result of an interactie transaction. Figure 14 shows a function which consists of the interactie transaction (transaction type 1) running in pool 4 and the non-interactie transactions (transaction type 2) running in pools 1, 2, and 4. The work represented by all transactions within a workload grow simultaneously when modeling growth by the number of actie jobs or growth percentages. A typical example would be the growth of the data queue inoice print job and picking slip print job with their associated order entry jobs. 26 BEST/1 Capacity Planning Tool V5R1

47 Change Transaction Workload...: QDEFAULT Measured from QPFRDATA (Q ) Function...: QDEFAULT Function of QDEFAULT Type choices, press Enter. Transaction Type =Inter, 2=Non Pool ID... 2 F4forlist CPU priority CPUtime Secs (on B10) Database time Secs (on B10) Permanent writes percent Chars transferred in... 0 Chars transferred out... 0 Exceptional wait....0 sec Application type... *DEFAULT F4 for list More... DB Reads DB Writes NDB Reads NDB Writes Sync I/Os Async I/Os F3=Exit F4=Prompt F6=Calculate B10 CPU time F12=Cancel F13=Change paging behaior Figure 15. Change Transaction - Process Heay Mail The following is a description of the parameters that define a transaction shown in Figure 15: Transaction Type Type 1 means interactie transaction. Type 2 means non-interactie transaction. Pool ID Pool ID indicates the storage area in which the transaction ran. CPU Priority The priority of the transaction is shown. You can reiew the pool ID and priority alues to distinguish between *LIC work and OS/400 or user work. Pool ID 1 is the machine pool (*MACH) and a priority of 0 indicates *LIC work. Pool 2 is the base (*BASE) pool. *LIC tasks run at priority 0. OS/400 jobs run at user-specified alues The normal interactie default priority alue is 10 for the system console job, and 20 for normal interactie jobs. BEST/1 uses priority 20 or higher (1-20) as its default for comparing predicted utilization against objecties. Because BEST/1 uses weighted aerages, some workload transaction details will show priority alues that are not shown in Performance Tools reports. For example if 10 and 20 priority work is aeraged together, you will see some transactions running at a priority such as 14 or 16 on the BEST/1 displays but no such priority will appear in the Performance Tools Component report. The performance data does not proide sufficient mapping of a specific FSnnnn task to a specific end user job, so BEST/1 must use intelligent approximations for its modeling work. Do not become confused with these transactions or other transactions that appear to take 0 CPU seconds, if they are shown. They took a ery small amount of resource that, when rounded up to the number of decimal positions shown on the display, appear as 0. CPU Time This transaction detail display (Change Transaction) shows the transaction CPU time as B10 CPU seconds. On the Change Transaction display you can type CPU Chapter 2. Workload Concepts 27

48 milliseconds (for example, D45 milliseconds), based on a measured Performance Tools report, and hae BEST/1 translate that into B10 CPU seconds. You can use this feature by pressing F6 (Calculate B10 CPU time). BEST/1 transaction details require that the CPU component be expressed in terms of B10 CPU seconds. During the analysis step these times are conerted (internally) to the proper alues based on the CPU listed in the model configuration details. The expression of the CPU time in B10 seconds allows for workload portability to other serers. BEST/1 s assumption is that the hardware characteristics file will always list CPU models in terms of their relatie performance to a B10. Database time The number of B10 database seconds used per transaction. Permanent Writes BEST/1 calculates the percentage of transaction writes that were sent to a permanent (ersus temporary) object. Characters Transferred In/Out This may be input for user-defined transactions and predefined workload transactions. For measured data, BEST/1 uses performance data and calculates this. The characters transmitted per transaction alue is intended for BEST/1 to use along with line speed for determining response time and utilization of communications resources. This calculation is theoretical because there is no measured data from which to determine real measured response time. Characters transferred in represents the characters coming into the serer and Characters transferred out represents the characters going from the serer to the display station. Exceptional Wait Any alue shown here allows BEST/1 to account for response time differences between measured data and predicted data, based on CPU and disk resource utilization. During the initial modeling process this field will be zero. During the model analysis process you can calibrate response time between predicted (by BEST/1) and measured response time if there is a large difference. A typical reason for a discrepancy would be a long database record or other object lock wait. Paging Behaior This is a ariable that is used to estimate a page faulting rate for the transaction. The paging characteristics can be defined as *GENERIC, *RAMPC, *OFFICE, and *SQLRTW, which are predefined characteristics, or if you change any paging alue, the paging behaior is changed to *USER. For more information on paging behaior alues, see Memory Modeling on page 135. Application types BEST/1 proides the capability to model the differences in workload scaling across different CPUs by adjusting transaction times according to application type. See Changing the application type on page 82 for additional details. Number of synchronous and asynchronous database (DB) and non-database (NDB) I/O operations This identifies the aerage number of disk I/Os charged to this transaction by BEST/1. The alues here are calculated by BEST/1 for measured data and part of a predefined workload. It must be manually entered for a user-defined transaction. You should be careful if you change seeral of these fields when using measured data, unless you are an expert at changing these alues in estimating What-if...? 28 BEST/1 Capacity Planning Tool V5R1

49 changes to an application design. That is, you can change some of these fields without jeopardizing the integrity of an existing application. If you change other fields you may hae difficulty getting actual job scheduling or program coding changes into the application to duplicate any modeled results based on the BEST/1 changes. If you are using predefined workloads, you may want to change some fields to approximate differences between the predefined workload and your understanding of an application that will be written. You are still responsible for deeloping an application that reflects the modeling parameters you selected. You would typically enter data into these fields when defining a user-defined workload. If you hae measured data from an application that you feel is similar to the transaction being defined, you may enter data into the Transaction type, Pool ID, CPU priority, CPU time, Characters transferred, and disk I/O read and write fields. Do not enter data into the other fields. You can change two fields without risk to get reasonable modeling results. Change priority or pool ID if the transaction is one that you can control, such as a type 1 (interactie) that reflects your order entry or similar application. This is the way you model a What-if...? change to the priority or pool in which the transaction runs is made. Non-interactie Transactions The use of the term non-interactie transaction is somewhat arbitrary, because workloads such as batch, by definition, cannot hae response times or key/think times. The concept of a non-interactie transaction is used to quantify a measurable unit of work, and should not be confused with how interactie transactions are defined. When you create a model, you can define non-interactie transactions using any one of the following parameters to categorize units of work: Logical I/Os Communications I/Os CPU seconds Print lines User Defined BEST/1 defaults to logical (disk) I/Os as the unit of measure for non-interactie transactions. Figure 16 on page 30 shows the display where non-interactie work can be grouped together into logical work units. This is one of the steps to define a job classification member. The job classification member is referenced when BEST/1 creates a model from measured data. Chapter 2. Workload Concepts 29

50 Define Non-Interactie Transactions Job classification category...: Job Type Type choices, press Enter. ---Actiity Counted as Transaction--- Total Transactions Workload Type Quantity when Type = *NONE QDEFAULT *LGLIO INTER *LGLIO BATCH *LGLIO CA4 *LGLIO Type: F3=Exit *LGLIO, *CMNIO, *CPUSEC, *PRINT, *NONE F12=Cancel Bottom Figure 16. Define Non-Interactie Transactions Display You can define non-interactie transactions as one of the last steps to create a model. It cannot be changed once the model has been built. The only way to change it is to re-create the model using a different job classification member. In a similar manner BEST/1 associates non-interactie system work (OS/400, *LIC tasks) with user work for growth modeling. BEST/1 does this automatically based on internal algorithms that allocate system work to user work. For instance, non-interactie (system) work gets generated by using mirroring, which increases system I/O. This is why an interactie workload is always included in the workloads shown on the Define Non-Interactie Transactions display. If there is no non-interactie work explicitly assigned to an interactie workload, system work is represented in the non-interactie transaction. See Defining Non-interactie Transactions on page 48 for more information. Example Showing Workloads, Functions and Transactions The workload defines the functions (or business processes) that one user performs, such as creating a document, or iewing a calendar. The actie jobs define the number of actie users doing that kind of work. Functions are made up of many transactions which may equate to a paper transaction, but usually they are associated with an Enter key after entering information on a display. Describing workload, function, and transaction relationships is difficult unless one understands the details of the entire application. It is easier to reiew the relationship between the elements of a workload with an example from an IBM-supplied, predefined workload. Therefore, this topic uses the office predefined workload as its basis for discussion. Figure 17 on page 31 shows the arious functions that an office manager can perform using the predefined Office Workload. Together all the functions listed that hae a number of Functions per User greater than zero, contribute to the workload MANAGER. For example, on the aerage, a MANAGER iews a 30 BEST/1 Capacity Planning Tool V5R1

51 calendar 1.8 times per hour, processes heay mail.9 times an hour, processes light mail.9 times an hour, and so on. Create Workload Type changes, press Enter. Workload... MANAGER Name Workload text... Managerial Workload type... *NORMAL F4 for list CPU architecture... *RISC *CISC, *RISC Usage mode =Casual 2=Interrupted 3=Steady 4=N/A Functions Ag K/T Tns per Function Function Text per User (secs) Inter Non-inter Update one calendar Update group calendar View one calendar Process heay mail Process light mail Create small document Reise small document Reise large document More... F3=Exit F4=Prompt F6=Work with functions F9=Specify chars to comm lines F10=Specify I/Os to ASPs F12=Cancel F24=More keys Figure 17. Create Workload Display By pressing F6 (Work with functions), it is possible to show more detail about the functions that make up the Workload MANAGER. Select the Process heay mail function to show more details as shown in Figure 18. Change Function Workload...: MANAGER Managerial Function...: D_HVY_MAIL Process heay mail Change fields, press Enter. Function text... Process heay mail Key/Think time Seconds Additional delays....0 Seconds Transaction Pool Transactions CPU Time Total Type ID Priority per Function (Secs) I/Os Transaction Type: 1=Interactie, 2=Non-interactie Bottom F3=Exit F6=Work with transactions F12=Cancel Figure 18. Change Function - Process Heay Mail Figure 18 shows the transactions which make up the Process heay mail function. They are split into arious pools at different priorities: 32 interactie transactions which run at priority 20 in pool 3. These are the typical look at mail and send note functions performed at the workstation. Chapter 2. Workload Concepts 31

52 2.53 non-interactie transactions run at priority 50 in the *BASE pool (2). This represents the print document transaction non-interactie transactions which run at priority 0 in the machine pool (pool 1). This is system actiity directly charged to the process heay mail function..43 non-interactie transactions run in the *BASE pool. This represents general actiity that is reapportioned across all functions in this predefined workload. As you can see by the CPU time alue of B10 CPU seconds, this represents a significant amount of work and therefore has been included in this predefined workload. As will be discussed later in the publication, if measured data were being used to create a BEST/1 model, this unassigned system work would default to an IBM proided workload named QDEFAULT. Since QDEFAULT is not proided with predefined workloads, this system work is assigned as a transaction to the predefined workload. Note: Appendix A. BEST/1 Workload Groups for Capacity Planning proides details of all IBM-supplied predefined workloads. A more detailed iew of the interactie transaction from Figure 18 on page 31 which you can display as follows: From the Change Function display, press F6 (Work with transactions). Select option 2 (Change) in the Opt column next to Transaction Type 1. Change Transaction Workload...: MANAGER Managerial Function...: D_HVY_MAIL Process heay mail Type choices, press Enter. Transaction Type =Inter, 2=Non Pool ID... 3 F4forlist CPU Priority CPUtime Secs (on B10) Database time Secs (on B10) Permanent writes percent Chars transferred in Chars transferred out Exceptional wait....0 sec Paging behaior... *OFFICE F4 for list Application type... *DEFAULT F4 for list More... DB Reads DB Writes NDB Reads NDB Writes Sync I/Os Async I/Os F3=Exit F4=Prompt F6=Calculate B10 CPU time F12=Cancel F13=Change paging behaior Figure 19. Change Transaction - Process Heay Mail Specifying Objecties and Actie Jobs 32 BEST/1 Capacity Planning Tool V5R1 Specification of actie jobs objecties is an important part of the modeling process. Each workload can hae its own set of performance objecties. BEST/1 uses these alues when analyzing the model, so that the proposed hardware and configuration will meet the customer s business requirements. For an example of specifying objecties, see Adding Throughput to an Existing System on page 197. For more information on specifying objecties, see Chapter 7. Modeling Changes to the System.

53 Note: Specifying objecties and actie jobs is normally aailable only at the adanced user leel. Figure 20 shows the display for changing actie jobs and workload objecties. Specify Objecties and Actie Jobs Model/Text: BEST1MODEL Type changes, press Enter. Workload Actie ----Interactie---- Non-inter Workload Connect Type Jobs Rsp Time Thruput Thruput WORKLOAD01 *LOCAL *NORMAL WORKLOAD01 *LAN *NORMAL WORKLOAD02 *WAN *BATCHJOB F3=Exit F11=Show all quantities F12=Cancel F15=Sort by connect type F19=Work with Workloads WAN jobs present with no WAN configuration Bottom Figure 20. Specify Objecties and Actie Jobs When using measured data it is not uncommon to see a fractional number of actie jobs, as shown in Figure 20. The number of actie jobs or workstations in the performance data collection period can ary and what is shown represents an aerage. For workloads built from measured data, a workload type of *BATCHJOB indicates that the jobs in that workload hae all met the following criteria: All jobs are batch type (non-interactie and batch). All jobs were actie for at least 95% of the measurement interal, that is, eery job was more or less continuously actie throughout the interal. Storage pools used by these low priority transactions serice only non-interactie transactions. For *BATCHJOB workloads, BEST/1 displays the number of concurrent batch jobs. For more information on *BATCHJOB workloads, see Chapter 6. Model Analysis and Calibration. If the current configuration contains no WAN or LAN elements, then the message at the bottom of the display in Figure 20 (or the LAN equialent) will be displayed. If you receie this message, either set actie jobs to 0 or add communications configuration elements. To add communications configuration elements, use F12 to return to the Work with BEST/1 Model display and select option 10 to access the Configuration menu. System Configuration is described in Chapter 5. System Configuration. Chapter 2. Workload Concepts 33

54 Summary of Workloads, Functions, Transactions, and Objecties Figure 21 is a summary of the relationships between the principal components of a BEST/1 model. Looking at transaction rate as the representation of work, consider transaction rate as the product of the number of LAN and WAN jobs, the number of functions per job (user) per hour, and the number of transactions per function. The transaction priority and its associated storage pool affect the results. Succeeding chapters in this document proide more details in the model creation process and model analysis. Workload Transaction Rate (trans per hour) is the product of: Number of local, LAN, and WAN jobs multiplied by: Number of functions per job/user per hour multiplied by: Number of transactions per function with priority and storage pool assignment Figure 21. BEST/1 Relationship of Workload Components 34 BEST/1 Capacity Planning Tool V5R1

55 Chapter 3. Building a Model Using Measured Data The purpose of this chapter is to gie an oeriew of the steps for building a model using performance measurement data. By selecting data that is representatie for your study, and describing your workloads accurately, you can build a more useful model. Selecting Data for Capacity Planning Measured Workloads First collect input data for capacity planning. Then either create a model in BEST/1 or use the Create BEST/1 Model (CRTBESTMDL) command to produce the measured model. The example Creating a BEST/1 Model from Performance Data on page 182 outlines these steps. Consider the following when selecting measurements to help ensure alid capacity planning results. Collect data for a time period representatie of a period of aerage load, as well as a period of heay load. Once you collect seeral such periods of data, reiew it to ensure that it: 1. Accurately represents the system 2. Is representatie; that is, seeral aerage load models are similar to each other. Create models for a continuous period of time. Consider how many and what kind of workloads should be specified gien the objectie of the capacity planning study. You can choose to group all users in a single workload, or diide them into multiple workloads. Multiple workloads may be important if the workloads and performance characteristics of the users differ significantly. Multiple workloads are necessary if you plan to grow the workloads at different growth rates. BEST/1 makes the following assumptions about the system during the selected measurement periods: All pool sizes and actiity leels are set to reasonable alues. Secondary paging (thrashing)does not occur. Excess storage is not present. The current state of system tuning will continue in the future. You can, of course, analyze the effect of tuning changes by changing the model. Time slices are large enough to minimize actie-to-ineligible transitions (shown as A I in the Interactie Jobs Summary). When you collect performance data to use for capacity planning, consider what abnormal situations might occur that would skew the data. Abnormal situations might include unusual programming deelopment actiity (such as compiles), system operator actiity (such as library sae and restore during peak interactie times), long-running queries, higher-than-normal transaction rates, or periods of low actiity in which response time is significantly better than normal. When you are satisfied that the data is representatie, consistent, and useful for capacity planning, you are ready to specify the workloads to include in the capacity planning model. If you hae more than a few hours of measurement data, in normal circumstances you will create your model selecting a1to2hour interal from Copyright IBM Corp. 1998,

56 the whole sample. If you decide to create a model oer a whole day, your results may not be representatie and the job may take a long time (perhaps hours) to complete. Creating a Model Using Performance Data You can use one of two methods for creating BEST/1 models from performance data: basic or adanced. The basic method is easier and is proided primarily for the user who does not need access to detailed model creation parameters. The adanced method is for users who want to specify model creation details, such as how jobs are classified into workloads and the definition of non-interactie transactions. Basic Method To create a model using the basic method, select option 5 (Create BEST/1 from Performance Data) on the Create BEST/1 for the AS/400 display. You see the Create Model from Performance Data display as shown in Figure 22. Create BEST/1 Model from Performance Data Type choices, press Enter. Use *SLTHOUR to select an hour-long time period or use *SLTITV to select select first and last interal of a one to two hour time period. The time period selected should be representatie of your peak processing actiity. Performance data: Member... Name, F4 for list Library... QPFRDATA Name Start time... *SLTHOUR Time, *FIRST, *SLTHOUR, *SLTITV Start date... *FIRST Date, *FIRST Stop time... *LAST Time, *LAST Stop date... *LAST Date, *LAST F3=Exit F4=Prompt F12=Cancel The main steps for the basic procedure are: 1. Select performance data 2. Specify the time period 3. Name the model Adanced Method When you use the adanced method to create a model, do the following: 36 BEST/1 Capacity Planning Tool V5R1 Figure 22. Create BEST/1 Model from Performance Data Basic 1. Select option 1 (Work with BEST/1 models) from the BEST/1 for the AS/400 display. 2. Select option 1 (Create) from the Work with BEST/1 Models display. 3. Type the name of the model that you want to create. Note: Typing XX for the model name causes the name and text of the model to take the name and text of the selected performance member.

57 4. Select option 1 (Create from performance data) from the Create BEST/1 Model display. You see the Create Model from Performance Data display in Figure 23. The main steps for the adanced method are: 1. Select performance data 2. Specify the time period 3. Specify the job classification a. Classify jobs into workloads b. Specify paging behaiors c. Define non-interactie transactions 4. Submit the CRTBESTMDL batch job Use the *SLTHOUR alue to display all hour-long time periods from which to select a single time period. Use the *SLTITV alue to display all data interals from which to select a starting and ending interal. Create BEST/1 Model from Performance Data Model...: MM Type choices, press Enter. Use *SLTHOUR to select an hour-long time period or use *SLTITV to select select first and last interal of a one to two hour time period. The time period selected should be representatie of your peak processing actiity. Text... Performance data: Member... Name, F4 for list Library... QPFRDATA Name Start time... *SLTHOUR Time, *FIRST, *SLTHOUR, *SLTITV Start date... *FIRST Date, *FIRST Stop time... *LAST Time, *LAST Stop date... *LAST Date, *LAST F3=Exit F4=Prompt F12=Cancel Figure 23. Create BEST/1 Model from Performance Data Adanced Figure 24 on page 38 shows the Select Hour-Long Period display. A single period can be selected using the Opt field. Sometimes the periods shown do not represent an hour-long period. This can occur when: The interal length does not diide eenly into 60 minutes. The last interal is shorter than normal. The total time is less than an hour. Chapter 3. Building a Model Using Measured Data 37

58 Select Hour-Long Period Library...: QPFRDATA Performance member..: Q Type option, press Enter. Select an hour-long period representatie of your peak processing actiity. Each time period is the sum of a one-hour performance monitor data collection. The time stamp shown is that of the last interal in the time period. 1=Select End ---Transaction--- --CPU Util--- I/Os per Sec Opt Date Time Count Rsp Time Total Inter Sync Async 1 03/10/94 10:37: _ 03/10/94 10:52: _ 03/10/94 11:07: _ 03/10/94 11:22: _ 03/10/94 11:32: Bottom F3=Exit F12=Cancel F15=Sort by interal F16=Sort by count F17=Sort by rsp time F18=Sort by total CPU util F19=Sort by total I/Os Figure 24. Select Sample Periods Figure 25 on page 39 shows the Select Time Interal display. Start and stop sample periods can be selected by using the Opt field. To select a range, with starting and ending sample periods, type a 1 next to the beginning and ending periods. All samples within these start and stop times are included. You cannot select more than one range of sample periods. To select a single period, place a 1 next to only one period. 38 BEST/1 Capacity Planning Tool V5R1

59 Select Time Interal Library...: QPFRDATA Performance member..: Q Type option, press Enter. 1=Select Select first and last interal. ---Transaction--- --CPU Util--- I/Os per Sec Opt Date Time Count Rsp Time Total Inter Sync Async 1 03/10/94 09:52: _ 03/10/94 10:07: _ 03/10/94 10:22: _ 03/10/94 10:37: _ 03/10/94 10:52: _ 03/10/94 11:07: _ 03/10/94 11:22: _ 03/10/94 11:32: Bottom F3=Exit F12=Cancel F15=Sort by interal F16=Sort by count F17=Sort by rsp time F18=Sort by total CPU util F19=Sort by total I/Os Figure 25. Select Sample Periods Classifying Jobs into Workloads Job Classification identifies how jobs running on the system are grouped into workloads. Figure 26 on page 40 shows the three main ways in which jobs (and tasks) may be classified. Chapter 3. Building a Model Using Measured Data 39

60 Classify Jobs Select one of the following: 1. Use default job classification 2. Classify jobs into workloads 3. Use existing job classifications Selection _ F3=Exit F12=Cancel Figure 26. Job Classification Menu Use option 1 (Use default job classification) unless you wish to model with more granular workloads. This diides work into four types of workloads that will suit a majority of general purpose situations, and is good for a first cut. Option 2 (Classify jobs into workloads) leads you to the Specify Job Classification Category display. Use this option when defining a new job classification scheme or to remoe work from workloads. You can sae the defined job classification for use in later model creation. Option 3 (Use existing job classification), lets you select a saed job classification scheme when building a new model. Using the Default Job Classification Some of the benefits for using the default job classification are: Easier to use (less naigation). BEST/1 assigns Licensed Internal Code (*LIC) tasks to appropriate workloads. See How BEST/1 Handles Licensed Internal Code Tasks on page 42 for more information on *LIC tasks. The default job classification subdiides the measured workload you are creating into the following categories: Interactie (INTERACTIV workload) Non-interactie (NONINTER workload) Client Access (CLIENTAC4 workload) System (QDEFAULT workload) Adanced 36 (NONINTER workload) Default Job Classification Table 2 shows the allocation of jobs to workloads when the default option is chosen (option 1) to classify jobs. 40 BEST/1 Capacity Planning Tool V5R1

61 Table 2. Default Job Classification Default Workload INTERACTIV CLIENTAC4 NONINTER Job Type *PTHRUSRC *PTHRUTGT *DDM *MRT *INTERACTV *CLIENTAC4 *EVOKE *AUTOSTART *BATCH *READER *WRITER *SCPF *ADV36 QDEFAULT *MONITOR *LIC *SYSTEM Note: *SYSTEM36 type jobs are placed into workloads depending on the alues of the other fields in the QAPMJOBS file (performance monitor) and the QAPMJOBL file (Collection Serices). For example, if JBS36E = Y and JBTYPE = I then it is placed into the INTERACTIVE workload. Client Access Shared Folder Type 0 and 1 and original client Submit Remote Command work are classified as *DDM job type. WSF work is classified as *CLIENTAC4 job type. Other Client Access work (file transfer, data queues, and so on) is classified as *CLIENTAC4 job type. Defining a Job Classification Figure 27 on page 42 shows the display for Specify Job Classification Category. Jobs will be classified according to the category chosen. Only one category selection is possible for each model. Chapter 3. Building a Model Using Measured Data 41

62 Type choice, press Enter. Specify Job Classification Category Category... 1=User ID 2=Job type 3=Job name 4=Account code 5=Job number 6=Subsystem 7=Pool 8=Control unit 9=Comm line 10=Functional area F3=Exit F12=Cancel Figure 27. Specify Job Classification Category The most commonly used categories are Job type and Job name. After entering the option a query may be run against the measured data which groups jobs according to the selection criteria. The Edit Job Classification display appears when selecting any of the options shown on this display. The Edit Job Classification display is formatted according to the category option you selected. On that display you can enter specific alues, such as user ID or job number, or you can choose F9 (Display alues from data) to hae BEST/1 query the QAPMJOBS file (performance monitor) or the QAPMJOBL file (Collection Serices) according to your job category selection. The display shown in Figure 28 on page 43 shows the results of a query based on job type. Once job classification has been completed, the classification can be saed and reused on different performance data sets. For example, you may wish to model the resources used by particular work stations, or the user IDs from a particular department. Any job not specifically assigned to a workload becomes part of the QDEFAULT workload. How BEST/1 Handles Licensed Internal Code Tasks The model building process automatically apportions licensed internal code tasks (*LIC) if you do not explicitly assign them to a workload. That is, the resources used by *LIC tasks, which cannot always be linked to the jobs that initiated them, are redistributed according to certain internal algorithms. These algorithms are much better than if a user attempts to group *LIC tasks with user and OS/400 jobs. Note: In Figure 27, the Job name category represents *LIC task names, user, and OS/400 job names. The display output resembles the Component Report, a performance report produced from the sample data collected, but does not identify the job/task type as the Component Report does. 42 BEST/1 Capacity Planning Tool V5R1

63 The workloads reflect the resources used aboe and below the Machine Interface (MI) and allow more accurate scaling during the modeling process. It is not recommended to explicitly assign any *LIC tasks to a specific workload. BEST/1 has internal algorithms to allocate *LIC tasks to the appropriate workloads. Shared Folder work is an example of an operating system leel job that may initiate an *LIC task and use resources of other *LIC tasks (such as an APPC controller station IOM). BEST/1 contains the information necessary to apportion the appropriate *LIC work to a Client Access workload and apportion other *LIC work to other workloads including QDEFAULT. Approximations are made when information in the performance database files is incomplete. The performance data may not contain some key information. Note: On the Assign Jobs to Workloads display, certain categories will display a blank line which represents any work on the system that does not hae a displayable alue for the category. This blank entry often includes *LIC tasks which BEST/1 will apportion to appropriate workloads, therefore you should not assign this work to a specific workload. Assigning Jobs to Workloads by Job Type In Figure 28, jobs hae been grouped together by job type. The user then allocates the different job type groupings to workloads. There can be more than one job type in a workload. All unassigned jobs are automatically assigned to the workload QDEFAULT. Assign Jobs to Workloads Workload... CA4 Type options, press Enter. Unassigned jobs become part of workload QDEFAULT. 1=Assign to aboe workload 2=Unassign Number of CPU I/O Opt Workload Job Type Transactions Seconds Count _ BATCH *AUTOSTART _ BATCH *BATCH *CLIENTAC _ BATCH *EVOKE _ INTER *INTERACTV _ INTER *PTHRUTGT *MONITOR *SYSTEM *LIC *WRITER *SCPF Bottom F3=Exit F12=Cancel F15=Sort by workload F16=Sort by job type F17=Sort by transactions F18=Sort by CPU seconds F19=Sort by I/O count Figure 28. Assigning Jobs to Workloads by Job Type You are free to assign *AUTOSTART, *BATCH, and *EVOKE into separate workloads or group them all into one workload (BATCH in this example). Chapter 2. Workload Concepts lists other possible job types not shown on this example. Chapter 3. Building a Model Using Measured Data 43

64 The performance work is included in job type *BATCH. Normally, the amount of performance work is negligible and has no effect on modeling results. Howeer, if you are collecting trace data or 5494 remote response time monitor data (RRSPTIME parameter not *NONE as specified on the STRPFRMON command), then this batch work must be considered. Chapter 8. Selected Modeling Topics proides additional details. Be aware that *CLIENTAC4 job type work includes: Client Access original client Terminal Emulation work (WSF, PC5250, and Rumba) Client Access original client Shared Folders type 2 work Client Access original client Transfer File work Client Access original client Message Facility work Client Access original client Virtual Print work Client Access original client Data Queue API work Client Access original client Remote SQL work Client Access original client License Management Client Access optimized client Terminal Emulation (WSF, PC5250, and Rumba) Client Access optimized client File Serer (shared folders) Client Access optimized client Database Serer (file transfer, remote SQL, ODBC) Client Access optimized client Network Print Serer Client Access optimized client Data Queue Serer Client Access optimized client Central Serer (license management, client management, NLS conersion map retrieal) Client Access Shared Folders type 0 and type 1 and original client Submit Remote Command work are grouped under *DDM job type work. If other DDM target work was also actie during performance data collection, Client Access *DDM work cannot be separated from this other DDM work by BEST/1 job type job classification support. See Chapter 8. Selected Modeling Topics for more details on Client Access. Assigning Jobs to Workloads by Job Name BEST/1 enables you to assign jobs to workloads based on job name. This function is useful when you want to model the effect of changing a ery specific workload. For better results, you must follow strict job naming conentions. The job name cannot be freely defined in all cases. Interactie Jobs The job name is taken from the display deice description. - The default name for DWS deices is deice-name, for example, DSPccc. - The default for pass-through target (serer) and Telnet serer deices is QPADEVxxxx. - The default for Client Access Work Station Function is the remote control point name plus two characters, for example, PCJIMS1. Batch Jobs The job name is taken from JOB parameter in the Submit Job (SBMJOB) command. The default is *JOBD; this means that the name of the job is the same as the job description you are using. Serer Jobs 44 BEST/1 Capacity Planning Tool V5R1

65 A serer job is the term used to describe a non-interactie job that has processing characteristics similar to an interactie workstation job but does not do workstation I/O. The primary characteristic of a serer job is that it is started and waits for work to do, typically at the request of another job. When the serer job receies a request for work, it performs the function and then goes back to a wait state, waiting for the next work request. The wait-process-wait sequence is similar to a workstation interactie job that waits for operator input, receies the input and processes it, then writes to the workstation and waits for more operator input. A serer job is partially a batch job in the way it is started and partially an interactie job in the way it processes and waits for data. One example of a serer job is a job that receies order entry information from another job, produces the printed order inoice and then waits for more order entry information. Another example of a serer job is the OS/400 database serer job that waits for SQL-based requests from a client workstation. For more information on OS/400 serer jobs, see the REXX/400 Reference book. The job name is taken from the: - JOB parameter in the Submit Job (SBMJOB) command. The default is *JOBD; this means that the name of the job is the same as the job description you are using. - JOB parameter in the Add Job Schedule Entry (ADDJOBSCDE) command when job scheduling is used. - JOB parameter in the Add Autostart Job Entry (ADDAJE) command when automatically starting a job when a subsystem monitor start is used. - JOB parameter in the Add Prestart Job Entry (ADDPJE) command when using prestarted jobs. - Communications deice name, when the job is started by a receied program start request. Note: Typically, serer jobs are continuously running, though there will be periods of waiting for work. If this job is running in a pool that contains no interactie jobs, then BEST/1 may assign the workload a type of *BATCHJOB. Because a true batch job s throughput is dependent on the resources aailable, serer jobs are not true batch jobs. Consequently, after the model has been created, select option 1 on the Work with BEST/1 Model menu to work with workloads. Select option 2 to change the workload. If the workload has been assigned a workload type of *BATCHJOB, change it to *NORMAL. If a serer job workload is characterized as *BATCHJOB, BEST/1 assigns unexpectedly high CPU utilization to that workload that does not compare accurately to measured performance data. When selecting jobs by job name you can use generic searches to group jobs that follow a naming conention. A suggested way to select jobs by either name or user profile is to create a functional area (from the Specify Job Classification Category display) where you can set up groups of users, groups of jobs, or both. This has the potential to combine both selections; howeer you hae to be ery careful not to include the same job in more than one workload. Chapter 3. Building a Model Using Measured Data 45

66 Assigning Jobs to Workloads by Communications BEST/1 enables you to assign jobs to workloads based on communications line or control unit options. If communications line is selected, all work that was not associated by performance data with a communication line will be assigned to only one workload. This enables models to be created which allow for workload changes according to remote locations. This can include changes to the number of remote work stations or changes to business olumes. If control unit is selected, all work that can be associated with a local work station controller, a display pass-through irtual controller, or a WAN controller is identified. All other work is assigned to a single workload. Type choice, press Enter. Specify Job Classification Category Category =User ID 2=Job type 3=Job name 4=Account code 5=Job number 6=Subsystem 7=Pool 8=Control unit 9=Comm line 10=Functional area F3=Exit F12=Cancel Figure 29. Specify Job Classification Category The Specify Job Classification Category display in Figure 29 is used with option 9 (Comm line) to group jobs by communications line category. The Edit Job Classification display in Figure 30 on page 47 shows workload and communications line pairs manually typed in. Only the communications lines that were actie during performance data collection are shown. 46 BEST/1 Capacity Planning Tool V5R1

67 Edit Job Classifications Enter workload names and category alues which are assigned to each workload, press Enter. Jobs with unassigned alues become part of workload QDEFAULT. Workload Comm Line Workload Comm Line Workload Comm Line NRD NRDLIN01 PTA PTALIN01 WIT WITLIN01 WRD WRDLIN01 QDEFAULT F3=Exit F9=Display alues from data F12=Cancel To display alues from performance data, press F9. Figure 30. Specify Job Classification Category Figure 30 shows workload assignments with actiity from lines NRDLIN01, PTALIN01, WITLIN01, and WRDLIN01. The remaining actiity will be assigned to workload QDEFAULT. For easier selection and assignment of workloads, press F9 (Display alues from data) to hae BEST/1 query the QAPMJOBS file (performance monitor) or the QAPMJOBL file (Collection Serices) and present a list of communications line names instead of trying to remember the communications line names. Figure 31 shows the selection display. Assign Jobs to Workloads Workload... Type options, press Enter. Unassigned jobs become part of workload QDEFAULT. 1=Assign to aboe workload 2=Unassign Number of CPU I/O Opt Workload Comm Line Transactions Seconds Count _ _ NRD NRDLIN _ PTA PTALIN _ WIT WITLIN _ WRD WRDLIN Bottom F3=Exit F12=Cancel F15=Sort by workload F16=Sort by comm line F17=Sort by transactions F18=Sort by CPU seconds F19=Sort by I/O count Figure 31. Assign Jobs to Workloads Chapter 3. Building a Model Using Measured Data 47

68 Use options 1 and 2 to assign and unassign the actiity associated with the communications lines. The Number of Transactions, CPU Seconds, and I/O Count statistics imply the degree of line actiity. Function keys which allow sorting of lines may assist in speeding the selection process. Note: The first line shown under communications line names shows no communications line. This line represents all work that was not assigned to any communications line. This other work can be assigned to only one workload, but it is preferable to let BEST/1 assign this work to the QDEFAULT workload in order to appropriately handle *LIC tasks. Specifying Paging Behaiors From the Specify Paging Behaiors display, as seen in Figure 32 you can choose the paging behaior you want to assign to all transactions within each workload. The choices are *GENERIC, *OFFICE, *RAMPC, and *SQLRTW. For more information about paging behaior, see Memory Modeling on page 135. Type choice, press Enter. Specify Paging Behaiors Workload QDEFAULT INTER PTA WIT WRD Paging Behaior (F4 for list) *GENERIC *GENERIC *GENERIC *GENERIC *GENERIC F3=Exit F4=Prompt F12=Cancel Bottom Figure 32. Specify Paging Behaiors Defining Non-interactie Transactions Figure 33 on page 49 shows the display where non-interactie work can be grouped together into logical work units. The unit of work Type and Quantity will not affect the response time nor system resources utilization for an interactie transaction. This change allows the user to define a unit of work which corresponds to a meaningful business unit of work. For example, if on aerage in the batch workload it takes 10 logical I/Os to complete a single inoice, then specifying *LGLIO in the Type column and 10 in the Quantity column will result in batch throughput being expressed in terms of inoices of work. It is possible to specify *NONE in the Type column and type the total number of transactions (business or paper ) transactions in the Total Transactions column. This alue is in transactions per hour. For example, if you type 12 in the Total Transactions column, BEST/1 considers the alue as 12 transactions per hour. 48 BEST/1 Capacity Planning Tool V5R1

69 Define Non-Interactie Transactions Job classification category...: Job Type Type choices, press Enter. ---Actiity Counted as Transaction--- Total Transactions Workload Type Quantity when Type = *NONE QDEFAULT *LGLIO INTER *LGLIO BATCH *LGLIO CA4 *LGLIO Type: F3=Exit *LGLIO, *CMNIO, *CPUSEC, *PRINT, *NONE F12=Cancel Bottom Figure 33. Define Non-Interactie Transactions Display You can define non-interactie transactions as one of the last steps to create a model. It cannot be changed once the model has been built. The only way to change it is to re-create the model. Resources include logical disk I/Os, CPU seconds, communications input/output operations, or printed lines as shown in Figure 34 on page 50. User defined transactions are defined by specifying Type = *NONE and typing a alue in the Total Transactions field. For instance, a user can indicate that 27 loan applications are processed within a workload by typing 27 in the Total Transactions and Type of *NONE to indicate the exact number of transactions (loan applications). Chapter 3. Building a Model Using Measured Data 49

70 Define Non-Interactie Transactions Job classification category...: Subsystem Type choices, press Enter. ---Actiity Counted as Transaction--- Total Transactions Workload Type Quantity when Type = *NONE QDEFAULT *LGLIO BATCH3 *LGLIO BATCH2 *LGLIO LOANAPP *NONE Type: *LGLIO, *CMNIO, *CPUSEC, *PRINT, *NONE F3=Exit F12=Cancel Bottom Figure 34. Define Non-interactie Transactions Non-interactie work can be expressed in terms of non-interactie transactions. It is possible to allocate non-interactie jobs to a specific memory pool and assign priorities for each non-interactie transaction. Non-interactie work can also be associated with specific ASPs. These functions proide a modeling enironment that approaches a real iseries serer. While non-interactie jobs generally run at a low priority, they can still interfere with the interactie jobs and hae an effect on IOPs, disk and memory. These effects can be seen by altering the model and iewing the analysis results. Creating the Model The actual creation of the model occurs after the job classification scheme has been selected. The create process accesses performance data and builds a model according to the specified job classifications. Figure 35 on page 51 is the display which is presented prior to building the model. A model can be built either in batch (recommended) or interactiely. Take the defaults to create in batch or set the Job Description to *NONE to create the model interactiely. 50 BEST/1 Capacity Planning Tool V5R1

71 Type choices, press Enter. Confirm Creation of BEST/1 Model Model... MEASURED Name Library... SCHIMU Name Text... Measured_Performance_Data Replace... N Y=Yes, N=No Jobname... CRTBESTMDL Name, *JOBD Job description... QPFRJOBD Name, *NONE, *USRPRF Library... QPFR Name, *LIBL, *CURLIB F12=Cancel Figure 35. Creation of the Model You may choose seeral options to determine if the model creation is complete: F5 (Refresh) on the Work with BEST/1 Models display. Examine your work station message queue for a job completed message. Use a command entry display to run the Work with Submitted Jobs (WRKSBMJOB) command. Note: When this display is reached from Option 5 (Create BEST/1 model from Performance Data), the Job name and Job description fields are not shown, and the model is created interactiely. After the model is created, it is automatically analyzed, and the Work with BEST/1 Model menu appears. Mixing Workloads from Different Serers BEST/1 supports defining and mixing workloads from multiple serers. This support can be used to determine if a single large serer can do the work of two or more smaller serers. Note: When mixing workloads from measured data collected on different serers you need to understand, and possibly change, transaction pool ID assignments in the model being created or changed. For example, on serer one, pool ID 3 may be used for spooling, but on serer two, pool ID 3 may be used for interactie work and pool ID 4 is used for spooling. To ensure proper modeling results, you may need to reassign the pool ID of some transactions on one of the serers. You need to determine which system to use as your base. When workloads hae been measured on a CISC CPU and others on a RISC CPU, the transaction alues will continue to reflect this difference. The CISC-to-RISC conersion factors applies to the appropriate workloads (such as, on CISC workloads when modeling on a RISC CPU) to reflect the type of CPU in the model configuration. Chapter 3. Building a Model Using Measured Data 51

72 Mixing Workloads from Different Serers Example You might want to consolidate seeral serers workloads onto a single serer. For example, an organization may hae multiple serers located in Los Angles, Chicago, and New York City. Each cities may een hae remote locations in neighboring states. A decision was made to consolidate all of these serers onto one central serer in Chicago. The Chicago serer would then be responsible for supporting all of the actiity in the remote cities. If one wants to know what size serer would be needed to support the workloads from all three serers, BEST/1 can help proide the solution. Consider the following process to consolidate the workloads: 1. As with any BEST/1 model, you will need to build a model for each location using performance data. Refer to Creating a Model Using Performance Data on page 36 for details. This includes the proper method for selecting representatie data, defining the workloads, as well as creating and calibrating each model. Depending on the nature of the business, each model may be built entirely independent of each other, or time differences may need to be considered. For example, if the business is commodities trading, there is a specific peak period for actiity no matter where one is in the country. On the other hand, if the business inoles local retail actiity, the local time zones and specific life style of the region may dictate another prediction of peak times. 2. Verify the QDEFAULT workload for each system accounts for less than 3% of the system s total actiity. If it accounts for a great deal more than 3%, consider identifying additional workloads until QDEFAULT is left with about 3%. The workload called QDEFAULT is to account for any actiity not recorded in any of the other defined workloads. 3. Once each model has been built, consider renaming each of the workloads, with the exception of QDEFAULT. Assume each model had workloads identified by four departments: Sales, Serice, Shipping, and Accounting. These may hae been identified by user profiles. Each model would also hae a workload called QDEFAULT for any other system actiity not recorded in one of these four departments. Rename the workloads so that they can be identified once they are combined. For example, rename the workloads in Chicago to be CSALES, CSERVICE, CSHIPPING and CACCOUNT. New York City could be renamed NYSALES or NYSERVICE. Use option 8 on the Work with Workload menu. 4. Combine all of the workloads into one model. Because all the workloads will be transferred to the Chicago serer, start with this workload. After selecting Work with BEST/1 Models (option 1 on the main menu) proceed to Work with Workloads (option 1). From this display, use F6 to add each workload to the Chicago model (one at a time). There would be a total of 13 workloads: three SALES workloads (CSALES, NYSALES and LASALES), three SERVICE workloads, three SHIPPING workloads, three ACCOUNTING workloads, and one QDEFAULT. 5. Because these workloads came from three different serers, the ASPs and Pool assignments, as well as the communication connections, need to be erified. The following should be checked: a. Verify all disk actiity is in the same ASP b. Verify the system pool numbering scheme Note: For example, QINTER may hae been system pool number 4 in Chicago and system pool number 3 in New York City. Once the workloads are combined make sure all of the actiity is occurring in the correct pool. In this case, all of the priority 20 interactie work, is 52 BEST/1 Capacity Planning Tool V5R1

73 allocated to system pool number 4 since Chicago had QINTER in system pool number 4. To edit these items, refer to Working with Functions on page 76. c. Check workloads with communication lines associated with them. In this example new communication IOPs and communication lines may hae to be created in the consolidated model to handle the New York City and Los Angles workload. d. Assign the workloads which used communication lines on the separate systems to indiidual communication lines on the consolidated system. Refer to Distribution of Characters Transferred Across Line Resources on page Verify the model is alid by using F13 on the Configuration menu. 7. Sae the model with a different name so to keep each model separate and easily identifiable (using F15 on the Work with BEST/1 Model display). By maintaining separate models, it will be easier for one to reconstruct BEST/1 s results at a future date. 8. Analyze the model and determine the CPU utilization of QDEFAULT. If it does not account for 3% of the combined workload in the consolidated model, it may be desirable to adjust the workloads. The rationale is that as new workloads are added to the consolidated system QDEFAULT (representing the system oerhead) would grow proportionately. In this case, it is feasible to be a little conseratie and grow the QDEFAULT workload to slightly exceeded 3%. This adjustment can be accomplished by using option 2 (Specifying Objecties) or option 7 (Specify Workload Growth) on the Work with BEST/1 Model menu. Seeral iterations may be required until the desired leel of actiity is achieed. 9. The consolidated system model are treated as any other single system model. You can start growing the workloads to simulate future conditions and analyzing the results for answers to what if scenarios. Refer to Modeling Workload Growth on page 110 for modeling projected growth in workloads. Similarly you would want to analyze seeral different hardware configurations. Refer to Changing System Resources on page 119 for techniques to change CPU and other system resources. Note: It is suggested that each time hardware resources are changed, you should sae the model under a different name. For example, you may start on model F50 and call it COMBINF50. If you were to then model a configuration , it might be called COMB2044. This type of scheme makes it easy to go back to any of the models for any fine tuning in the future. Chapter 3. Building a Model Using Measured Data 53

74 54 BEST/1 Capacity Planning Tool V5R1

75 Chapter 4. Building a Model Using Predefined Workloads Using Predefined Workloads This chapter describes the predefined workloads that are aailable with BEST/1, when to use them and how they are accessed. A comparison is gien between the workloads that are aailable with this product and other OS/400 capacity planning tools. Predefined workloads are used when no measured data is aailable. Always try to use real data in preference to approximating your requirements with a set of predefined workloads. They should be used when there are no measurements of future workloads or new applications under deelopment. Be aware that when you use predefined workloads, the margin for error is increased. Note: When mixing predefined workloads with measured workloads, you may need to change the pool ID of the IBM-supplied workload transactions. Otherwise, modeling analysis may produce inaccurate results. For example, the predefined office workload process heay mail function transactions run in pools 1, 2, and 3. The process heay mail interactie transaction runs in pool 3 and its associated print transaction runs in pool 2. If, on your measured system, pool ID 3 is used for print spooling, you may want to change the process heay mail interactie transaction to run in a pool you use for interactie work, such as pool 4. When modeling both measured and predefined workloads it is recommended you use the measured data storage allocation as the base for making any pool adjustments. Predefined workloads are subject to the same CISC-to-RISC conersion factors as measured workloads. If CISC-based predefined workloads are modeled on a RISC CPU, the CISC-to-RISC conersion factors applies to the predefined workload just as if the workload was created from CISC-based measured data. The predefined workloads supplied with this product are sometimes different than those proided with other capacity planning tools, such as MDLSYS or QSIZE400 (een though they may hae similar names). In BEST/1, workloads are logically arranged in workload groups. A workload group is a set of predefined workloads that share a common characteristic. The following workload groups/workloads are supplied with BEST/1. BATCH Commercial orders (ery heay) Deelopment orders (ery heay) Complex query Summary query Sort query Background batch serer COMMERCIAL Copyright IBM Corp. 1998,

76 RAMP-C SQL RTW OFFICE IBM Office Benchmark V2 Secretarial Managerial Professional Correspondence center SPOOL Simple print AFP(*NO) Simple print AFP(*YES) Complex print AFP(*YES) SERVER Client/Serer Medium OLTP (DQ) Client/Serer Simple OLTP Heay Image and Audio Slide Show Heay Image Slide Show (IPCS) Heay Image Slide Show (Shared Folders) Heay USF/400 Multimedia User Medium Continuous Video (IPCS) Medium Continuous Video (Shared Folders) Lotus Notes Mail Disc DB Users Notes Bench Mail Users WWW Static Page Serer INDUSTRY Aerospace Industry Apparel and Retail Distribution Industry Chemical/Pharmaceutical Industry Communications Industry Computer Serices Industry Consultants/CPA/Legal Industry Higher Education Industry Finance Industry General Workload summary Health/Medical Industry K-12 Education Industry Media Industry Manufacturing Industry Petroleum Industry Process Industry Public Utilities Industry Securities Industry State and Local Goernment Industry Transportation Industry Wholesale Distribution and Serices Industry 56 BEST/1 Capacity Planning Tool V5R1

77 User-defined Same type of data as predefined Specific to user s application Can be used before application is aailable Commercial Orders is a synthetic batch workload often associated with commercial data processing. It focuses on retrieing, resequencing, and organizing data from seeral files with relatiely small amount of processing of data within the files, much like many end-of-day or end-of month jobs. It can also include jobs that run at the same time with interactie work where the work is submitted to batch because it requires a large amount of disk I/O. The workload operates on 18 physical files of arious sizes and record lengths. Each file has 10 logical iews using nine different indexes built oer it. The indexes allow physical access to the files sequentially, randomly, or some combination of sequential from a random starting point. The job consists of three functions: Order alidation simulation Order processing simulation File copy ( records into temporary file) The deelopment workload is a synthetic workload of the type of processing that might occur when application deelopment actiities run at the same time as normal production work. It includes a mixture of compiles and library sae operations as follows: Large compilation Small compilation Sae procedure Repeats small compilation Repeats sae procedure See Appendix A. BEST/1 Workload Groups for Capacity Planning for additional details on predefined workloads. Using BATCH Predefined Workloads The BATCH workload group contains the workloads shown in Figure 36 on page 58. Chapter 4. Building a Model Using Predefined Workloads 57

78 Select Predefined Workload Group...: BATCH Type option, press Enter. 1=Select Opt Predefined Workloads Commercial orders Deelopment orders Complex query Summary query Sort query Background batch serer F3=Exit F12=Cancel Bottom Figure 36. Select Predefined Workload - Batch Modeling Example Commercial orders is the workload with heaiest I/O. Summary query is the workload with greatest CPU time per I/O. Deelopment Orders is a workload with a mixture of processes, such as compilations and sae operations. The complexity of the batch transactions can be checked by examining function and transaction definition details. These can be changed if required to be more representatie of the application being modeled. Use care when modeling with predefined batch workloads. They are ery resource intensie and may not represent your actual batch enironment. These workloads are most suitable in situations where the batch workload uses all the aailable resources. You may want to lower the CPU seconds or number of disk I/O operations per transaction within these workloads to more closely approximate the resource consumption of your application. Selecting Predefined Workload There are two ways predefined workloads can be used: Creating a new model Adding predefined workloads to an existing model When creating a new model, you will be gien the option of working with measured data or using predefined workloads. The other way to use predefined workloads is to add them to an existing model. This is done from the Work with BEST/1 Model display. Select option 1 Work with Workloads. From this display select F9 (Add predefined workloads) and the Select Predefined Workload Group display appears, shown in Figure 37 on page 59. Before you can select a predefined workload you must select a workload group. Each group contains a number of related workloads. 58 BEST/1 Capacity Planning Tool V5R1

79 Library... QPFR Name Type option, press Enter. 1=Select Select Predefined Workload Group Workload Opt Group Text _ BATCH IBMSupplied (BATCH) 1 COMMERCIAL IBM Supplied (Includes RAMP-C) _ OFFICE IBMSupplied (OfficeVision/400) _ SPOOL IBMSupplied (SPOOL) _ SERVER IBMSupplied (Client/Serer) _ INDUSTRY IBMSupplied (Industry) F3=Exit F12=Cancel Bottom Figure 37. Select a Predefined Workload Group Once the group has been selected, the corresponding workload panels will be displayed. Select the required workloads. Select Predefined Workload Group...: Commercial Type option, press Enter. 1=Select Opt Predefined Workloads 1 RAMP-C _ SQL RTW F3=Exit F12=Cancel Bottom Figure 38. Select a Predefined Workload Selected workloads are added to the current model. When you select the IBM-proided RAMP-C workload by typing a 1 in the corresponding Option field, you are presented with Figure 39 on page 60. The Create Workload display shows the RAMP-C function definition. Type a workload name and press the Enter key to include the predefined workload in your model. Chapter 4. Building a Model Using Predefined Workloads 59

80 Create Workload Type changes, press Enter. Workload... ENTRIES Name Workload text... RAMP-C CPU architecture... *RISC *CISC, *RISC Workload type... *NORMAL F4 for list Usage mode =Casual, 2=Interrupted, 3=Steady, 4=N/A Functions Ag K/T Tns per Function Function Text per User (secs) Inter Non-inter Inquiry Simple updates Multiple entry updates Complex processing F3=Exit F4=Prompt F6=Work with functions F9=Specify chars to comm line resources F12=Cancel F24=More keys Bottom Figure 39. Create Workload Display To iew or change transaction details you can use one of the following methods: Use F6 (Work with functions) on the Create Workload display, followed by the Display or Change Function sequence of displays. Select option 9 (Edit transactions) on the Work with Workloads display. Normally you would not need to change the transaction definition; howeer, in this case press the Enter key on this Create Workload display. It is possible to add multiple workloads to the same model from the same or different workload groups. When all required workloads hae been added, do not forget to define the objecties for each workload. See Chapter 2. Workload Concepts. 60 BEST/1 Capacity Planning Tool V5R1

81 Chapter 5. System Configuration Prior to analyzing a model, BEST/1 requires a alid OS/400 system configuration. If you are modeling from measured data, the QAPMxxxx files contain the necessary hardware and storage pool configuration information. If you are modeling using only predefined workloads or user-defined workloads, BEST/1 does not automatically select a hardware configuration. Howeer, BEST/1 supplies a set of standard OS/400 hardware configurations in library QPFR. These configurations are shown in Figure 40. This display is shown by selecting the Work with configuration members option on the More BEST/1 Options menu using library QPFR. Alternatiely, you can use a similar display called Select Configuration Member, if you attempt to analyze a model that has no hardware configuration defined. In either case, BEST/1 will allow you to select one of these IBM-supplied configurations. The modeling process can then proceed. Library... QPFR Name Type option, press Enter. 3=Copy 4=Delete 6=Print 7=Rename Work with Configuration Members Opt Member Text Date Time A20S_2010 Sample 9402 configuration 06/27/95 20:40:42 A200_2030 Sample 9402 configuration 06/27/95 20:40:42 A200_2031 Sample 9402 configuration 06/27/95 20:40:42 A200_2032 Sample 9402 configuration 06/27/95 20:40:42 A30S_2411 Sample 9406 configuration 06/27/95 20:40:42 A30S_2412 Sample 9406 configuration 06/27/95 20:40:42 A300_2040 Sample 9406 configuration 06/27/95 20:40:42 A300_2041 Sample 9406 configuration 06/27/95 20:40:42 A300_2042 Sample 9406 configuration 06/27/95 20:40:42 A310_2043 Sample 9406 configuration 06/27/95 20:40:42 A310_2044 Sample 9406 configuration 06/27/95 20:40:41 More... F3=Exit F5=Refresh F12=Cancel F15=Sort by member F16=Sort by text F19=Sort by date and time Figure 40. Work with Configuration Member Display You can copy one of these IBM-supplied configurations to your library and iew or change it with the Configuration menu option on the Create BEST/1 Model display. Once a model has been created, measured or IBM-supplied configuration data can be changed and saed as discussed in the remainder of this chapter. BEST/1 allows you to sae and use a saed configuration when modeling. Function keys F14 (Replace with saed configuration) and F15 (Sae current configuration) can be accessed from the Configuration menu shown in Figure 41 on page 63. You can use F24 (More keys) to display these function keys, but you can still access these function keys when they are not isible on the menu. Copyright IBM Corp. 1998,

82 Read Conersion System Configuration Menu The configuration of a pre-v4r2 model can be changed when read into BEST/1. This is generally done to add IOAs to the configuration that are required in V4R2 but were not supported in earlier releases. Some IOP features support disk actiity (disk IOPs and some multifunction IOPs) and some IOP features support communications actiity (communications IOPs and multifunction IOPs). BEST/1 can change IOP connections when the original configuration is not compatible with the current hardware specifications. For example, if a multifunction IOP is attached to disk controllers, but the hardware table shows that the IOP does not support disk actiity, the controllers and arms are deleted. These types of changes are indicated by either change, create, or delete messages. Additional messages can be displayed. See Configuration Changes to Pre-V4R2 BEST/1 Models on page 271 for a listing of these messages. The Configuration menu can be accessed by using option 10, on the Work with BEST/1 Model display. Figure 41 on page 63 shows the display layout. The current OS/400 system configuration can be displayed or changed, including CPU model, system features, disk configuration, ASPs, memory pools, and communications resources. If an IBM-supplied configuration is being used, the changes to the configuration last only for the duration of the capacity planning session. To sae the changed configuration, first make a copy of the IBM-supplied configuration, and then change the copy. BEST/1 assigns CPU power to specific models using the Relatie Internal Processor Performance rating as measured by IBM. In some cases, the rating for a specific CPU model or feature will differ from other published reports which quote the Relatie Performance of the system based on the specific benchmark. BEST/1 assigns performance settings to the Disk IOP and Disk Deice tables based on total subsystem performance as it relates to probable customer enironments, as measured by IBM. In most cases, these numbers differ from the published hardware specifications which do not consider specific OS/400 enironments. Note: Because of the capability to add newly announced hardware between releases of the Performance Tools, it is possible to change a CPU model configuration to a relatie performance factor that is not alid. If you do this, any modeling output may show capabilities that are not actually possible, such as a D45 with a B10 multiplier of There will be no indication on the output that you hae results that are not alid. 62 BEST/1 Capacity Planning Tool V5R1

83 Configuration M CPU odel...: 23BB Comm IOPs...: 0 Processors...: 4/4 LANlines...: 9 Main stor (MB)...: 8192 WAN lines...: 3 Main stor pools...: 4 Disk IOPs...: 2 Multifunction IOPs...: 12 Disk ctls...: 4 Disk IOAs...: 5 Disk arms...: 75 Comm IOAs...: 11 ASPs...: 1 IPCS IOAs...: 0 Select one of the following: 1. Change CPU and other resource alues 2. Work with disk resources 3. Edit ASPs 4. Edit main storage pools 5. Work with communications resources Selection or command ===> F3=Exit F4=Prompt F9=Retriee F12=Cancel F13=Check configuration F17=Correct configuration F24=More keys BEST/1 CPU model BB refers to IBMCPU model Figure 41. Configuration Main Menu A number of function keys are proided to assist the user: After changes are made, F13 (Check configuration) can be used to check that the new configuration is alid. If the OS/400 model type is changed (for example, from a 9406 to a 9404) then you may get warning messages when you use F13 to check the alidity of the configuration. F17 (Correct configuration) allows you to make automatic corrections to disk and communications resources in one step. A brief log displays, that tells you what has been changed. Configurations can be saed using F15 (Sae current configuration). The current configuration can be replaced with a preiously saed configuration using F14 (Replace with saed configuration). This menu is also accessed by a function key from arious report displays. The message at the bottom of the display also proides an example of the CPU naming conention that is used by BEST/1. BEST/1 uses a unique 7-character feature code to identify CPUs. To aoid confusion with orderable feature codes, BEST/1 displays a message that contains the 7-character feature code that it uses and the 11-character feature code by which this CPU is known in the order process. Changing CPU and Other Resource Values This display enables you to change the OS/400 system type (9402, 9404, 9406), the OS/400 model number, the main storage for this model, and the release leel. You can also change the number and serice times for local and WAN workstation controllers and LAN controllers. The controller serice times are used during analysis to predict LAN and WAN response times. For LAN controllers and WAN workstation controllers, the serice time can represent many types of hardware. For example, a PS/2, a 5494, and a 9404 system can all be LAN controllers that supply work to the system being modeled. Although the effect on total response time is usually ery small, by Chapter 5. System Configuration 63

84 supplying an aerage serice time for each group of controllers, you can see results in the analysis reports. Model/Text: Q Type choices, press Enter. Change CPU and Other Resource Values M System unit , 9404, 9406 CPU odel... 23BB F4 for list System storage (MB) F4 for list Release leel... V4R5M0 F4 for list Actie processors... 4 Unaailable PCI slots... 0 F3=Exit F4=Prompt F9=Specify other logical partitions F12=Cancel BEST/1 CPU model BB refers to IBMCPU model Figure 42. Change CPU and Other Resource Values BEST/1 makes the following assumptions about communications resources: Workstations are eenly distributed across all controllers within a group (local, LAN, or WAN). WAN workstation controllers and LAN controllers are equally distributed across the aailable WAN and LAN lines. All local workstation controllers hae the same serice times, as do all LAN controllers and WAN workstation controllers. Specifying other logical partitions When you are working with logical partitions and you want BEST/1 to specify recommendations, use the Specify Other Logical Partitions display to indicate what configuration resources are attached to this serer but attached to other partitions and which resources are aailable to be moed to this partition, if needed. You must specify how you want your resources allocated by using the following types of configuration resources: Processors and main storage IOPs: multifunction, disk, LAN, and WAN WAN communication lines 64 BEST/1 Capacity Planning Tool V5R1

85 Specify Other Logical Partitions Type changes, press Enter. Aailable processors... 0_ Current Aailable Change Mode Main storage (MB) _ 0 C Multifunction IOPs... 60_ 0 C Disk IOPs... 50_ 10_ C LANIOPs... 30_ 0 C WANIOPs... 20_ 0 C WAN lines... 80_ 0 C Change Mode: M=Moe first, C=Create first F3=Exit F6=All unaailable F12=Cancel Figure 43. Specify other logical partitions The Aailable processors field is the number of processors for this serer, which can be made aailable to this partition, if needed. The total of the Aailable column plus the processors in the Current partition cannot exceed the CPU total. Similarly, the other resources represent the amount of that resource which is currently assigned to other partitions, and of the total, the amount that is aailable to be assigned to this partition, if needed. When more than one of these resources is needed in this partition, the Change Mode column is used to indicate from where that resource should originate. If the Change Mode alue is C, BEST/1 adds a new resource of that type before attempting to retriee the resource from other partitions. If the Change Mode alue is M, BEST/1 uses what is aailable from other partitions first. BEST/1 recommends new resources only when you need more resources than are aailable. For example, you hae a CPU model that supports a maximum of 20 disk IOPs, and your current logical partition has 5, and other logical partitions hae 13. BEST/1 determines that four more disk IOPs are needed. If the alue in the Aailable column is 0, then BEST/1 does not moe any disk IOPs from other partitions into this one, but instead upgrades the CPU to a model that can support at least 22 disk IOPs. If the alue is at least 4 and the Change Mode field is M, then BEST/1 will moe 4 of the 13 disk IOPs from the other partitions into your current partition. If the alue in the Aailable column is at least 2 and the Change Mode field is C, then BEST/1 creates two disk IOPs. That means that the serer is at its maximum of 20 disk IOPs, and BEST/1 moes 2 of the 13 in the other partitions into the current partition. Note: Wheneer you work with a logically partitioned processor, the RPRs for the logical partition deice is less than the RPRs for the total system. Contact your IBM support person for help with adjusting the serer capacity ratings for your partition. To determine the totals for each resource type on this display, use the Work with Hardware Resource (WRKHDWRSC) command. Chapter 5. System Configuration 65

86 Working with Disk Resources On this display you can iew all disk resources connected to the CPU. Disk resources are diided into these types: Input/output processor (IOP) Input/output adapter (IOA) Disk controller Disk arms Disk IOAs are represented explicitly, but can only be attached to multifunction IOPs. Work with Disk Resources Model/Text: BEST1MODEL Sample BEST/1 model Position to... IOP name, *TOP, *BOT Type options, press Enter. 2=Change 3=Copy 4=Delete 7=Rename 8=Create disk arms RAID Serice Time Opt Resource Feature Type ASP Array (Msecs per IO) _ CMB *MFIOP.9 _ DI *IOA 1.7 DD *ARM DD *ARM DD *ARM DD *ARM _ SI *IOP 1.4 _ ARRAY *CTL DD *ARM DD *ARM F3=Exit F4=Prompt F6=Create IOP F9=Select resources to change features F12=Cancel Figure 44. Working with Disk Resources Editing ASPs Figure 45 on page 67 shows the display for changing the data protection mode of an Auxiliary Storage Pool (ASP). The protection leel of each ASP can be separately defined as *NONE, *MIRROR, or *CHECKSUM. Note: ASPs containing arms with the high aailability option are normally *NONE. If an ASP contains a combination of high aailability and non-high aailability arms, *NONE or *MIRROR is possible. If an ASP with *MIRROR data protection contains high aailability arms, only the non-high aailability arms are mirrored. See Modeling ASPs and Journaling on page 177 for more information on modeling new ASPs. 66 BEST/1 Capacity Planning Tool V5R1

87 Model/Text: Q Type changes, press Enter. Edit ASPs Number of Data Compression Utilization ASP Disk Arms Drie Feature Protection Actie Guideline 1 75 ** *NONE N *STD Drie Feature: ** = mixed Data Protection: *NONE, *MIRROR, *CHECKSUM Compression Actie: Y=Yes, N=No Utilization Guideline: 1-100, *STD=from Edit Utilization Guidelines F3=Exit F12=Cancel F14=Work with disk resources Bottom Figure 45. Editing ASP Data Protection The Edit ASPs display shows you whether or not compression is actie for all disk arms assigned to this ASP that support compression. A alue of Y indicates that compression is actie; a alue of N indicates that compression is not actie. If compression is actie, then serice times for these disks is increased during analysis by the compression oerhead specified in the hardware table. In addition to the compression indication, this display also shows you the utilization guideline for all disk arms assigned to this ASP. When this field contains a number, this guideline alue oerrides the disk arm alues on the Edit Utilization Guidelines display. When this field contains *STD, arm utilization guidelines reert to the arm alues on the Edit Utilization Guidelines display. Editing Main Storage Pools Figure 46 on page 68 shows the display to edit pool data. Each pool is modeled indiidually. Changing the pool sizes and actiity leels can hae a significant effect on the resources used by different workloads. Pools can be created using F6 (Create). Chapter 5. System Configuration 67

88 Edit Main Storage Pools Model/Text: BEST1MODEL Sample BEST/1 model M Main storage size...: 512 B KB Type changes, press Enter. To delete a pool, set size to *NOSTG. Actiity Size Pool ID Pool Name Leel (KB) F3=Exit F6=Create F12=Cancel F17=Re-scale pool sizes Bottom Figure 46. Editing Main Storage Pools Working with Communications Resources This display shows all of the communications IOPs, IOAs, and the line resources in the current configuration. You can create or change communications resource parameters such as the communications IOP or IOA feature, its aerage serice time, line speed, and the number of lines connected to each IOP or IOA. Note: Communications IOAs can only connect to some multifunction IOPs. Communications IOAs cannot connect to communications IOPs. Work with Communications Resources Type options, press Enter. 2=Change 3=Copy 4=Delete 7=Rename 8=Create line resources Nbr of Line Speed Pct Line Opt Resource Feature Lines Type (Kbit/sec) Oerhead CC *IOP LANLINE1 1 *LINE CC *IOP WANLINE1 6 *LINE CMB *MFIOP LIN19 1 *IPCS D27DBF0101 *LINE LIN *IOA CMN08 1 *LINE LIN *IOA QESLINE 1 *LINE F3=Exit F6=Create IOP F12=Cancel Bottom Figure 47. Work with Communications Resources 68 BEST/1 Capacity Planning Tool V5R1

89 Multifunction IOPs will appear on this display. If the multifunction IOP can support disk processing, they will also appear on the Work with Disk Resources display. See Communications Configuration on page 165 for more information on communications resources. Chapter 5. System Configuration 69

90 70 BEST/1 Capacity Planning Tool V5R1

91 Chapter 6. Model Analysis and Calibration The key to accurate modeling is being able to construct a model that reacts in a way similar to the system being modeled. You must be able to recognize the performance data sets that are representatie of your OS/400 workload. Similarly, after the model has been built, you should feel comfortable that it is behaing in an appropriate manner. This chapter discusses techniques for building good models and proides an oeriew of the model analysis process. Figure 48 reiews the processing options for a newly created or changed model. After you create a model, select option 5 (Work with) on the Work with BEST/1 Models display as shown in Figure 4 on page 10. The menu shown in Figure 48 appears. This chapter discusses BEST/1 support for options 1, 2, 5, 6, and 11. Work with BEST/1 Model Performance data...: Model/Text...: BESTDATA BEST1MODEL Select one of the following: 1. Work with workloads 2. Specify objecties and actie jobs 5. Analyze current model 6. Analyze current model and gie recommendations 7. Specify workload growth and analyze model 10. Configuration menu 11. Work with results More... Selection or command ===> F3=Exit F4=Prompt F9=Retriee F12=Cancel F15=Sae current model F17=Analyze using ANZBESTMDL F22=Calibrate model F24=More keys Figure 48. Work with BEST/1 Model Display Work with workloads Use the Work with workloads display to reiew the accuracy of the function and transaction details of a workload deried by BEST/1. This menu option is only aailable at the adanced user leel. Specify objecties and actie jobs Use the Specify Objecties and Actie Jobs display to alidate the number of actie jobs. For the initial modeling process you should accept the BEST/1 alues if measured data is being used. This menu option is only aailable at the adanced user leel. Analyze current model Analyze current model takes the current hardware configuration and workload definitions and analyzes this data. The Work with Results display lets you look at seeral categories of results including analysis summary, recommendations and workload reports. Copyright IBM Corp. 1998,

92 This menu option is only aailable at the adanced user leel. This option is equialent to using Option 7 (Specify workload growth and analyze model) and specifying 1 period to analyze with Determine configuration changes set to N. Analyze current model and gie recommendations Analyze with recommendations will consume additional CPU and will make recommendations for new hardware and pool size alues. Hardware changes will identify CPU model, memory size, disk IOP, disk arm quantities, and feature numbers. Communications IOP and line speed quantities, and their respectie feature numbers will also be identified. This option takes longer to run than option 5. This menu option is only aailable at the adanced user leel. This option is equialent to using Option 7 (Specify workload growth and analyze model) and specifying 1 period to analyze with Determine configuration changes set to Y. Specify workload growth and analyze model You may select the workload growth rate(s), number of periods to model, and whether you want BEST/1 to automatically upgrade hardware according to its guidelines and thresholds. The functions accessed from this option are termed manual growth, ersus automatic growth. Chapter 7. Modeling Changes to the System contains workload growth details. Configuration menu The Configuration menu option leads you into additional options for iewing and changing CPU, local Work Station Controller, communications Disk, storage pools, and ASPs. Configuration details are not described in this chapter. See Chapter 5. System Configuration for additional configuration information. Work with results After any of the analyze functions (options 5, 6, 7) has completed, you can work with the analysis results as discussed in Model Analysis Results on page 91. The Work with Results display proides summary and detail information for response time, throughput, and resource utilization. In addition, you can work with preiously saed results. About BEST/1 This menu proides introductory information to new BEST/1 users. It includes BEST/1 naigation, creating a measured model, analysis issues, descriptions of reports and graphs, an oeriew of BEST/1 external files, and a summary of enhancements in the current release. Page down to see this menu selection. Figure 49 on page 73 shows the naigation sequence for working with BEST/1 models. The remainder of this chapter discusses: Verifying workloads and objecties before calibration Calibrating predicted results ersus measured results Interpreting model analysis output 72 BEST/1 Capacity Planning Tool V5R1

93 Figure 49. Work with BEST/1 Model Flow Chart Adanced User Leel Chapter 6. Model Analysis and Calibration 73

94 Verifying the Workloads Before performing What-ifs...? on the model, your workloads should be checked to see if they reflect the work on your system. In addition, not all measured performance data can be used as a basis for your model. The most important questions to ask are: Does the measured workload really represent the workload to be modeled? Does the measured data represent a well-tuned enironment? BEST/1 makes certain assumptions and has some conditions; see BEST/1 Assumptions and Conditions on page 6 for more details. Reiew this section and check that your data or your situation is compatible with these assumptions. Remember, if you use inappropriate input data, then the results will be inaccurate. As you become familiar with BEST/1, you will notice that it uses a high degree of precision (often up to three decimal places). Do not confuse precision with model accuracy. The model is only as accurate as you make it. Chapter 2. Workload Concepts, discussed that the work on the system is composed of workloads, and each workload is composed of functions, and each function is composed of transactions. The number of actie jobs shows how many users were associated with each workload. See Verifying the Number of Actie Jobs in the Workload on page 79 for further information on the number of actie jobs based on measured data. In initial modeling sessions, you might consider accepting the BEST/1 default definitions of workloads, functions and transactions, then changing some of these when you thoroughly understand the work being modeled. Before measured workloads are used, reiew and erify them. Are they: Representatie If you are using measured workloads, check if the data collection was taken in a representatie day and if the period selected included peak hours. Check the performance data interal selected. If it is less than 30 minutes a small anomaly might hae a significant effect on your model. On the other hand, if it is more than two hours, you will not be able to reflect peak hours work. One hour of performance data, with 15-minute sample interals, is a good default time to use. Note: With Collection Serices you can collect your data continuously, and then select which time periods you want to use. When using predefined workloads look at the workload description to see if it matches the workload you are trying to model. Consistent You should expect similar workloads if models are built from two different representatie sets of data. Accurate The system from which you are measuring data should be well tuned. The issue is not that the system does not hae performance problems, but that these problems are not due to poor tuning. Examples of poor tuning include: - Failed disk arms resulting in problems such as excessie amounts of checksumming and I/Os. 74 BEST/1 Capacity Planning Tool V5R1

95 - Poorly chosen actiity leels. - Badly fragmented disks resulting in excessie head moement and longer seek times. - Higher priority (lower priority alue) for jobs that hae a less critical time factor. Unless you change the model to reflect the elimination of these problems, BEST/1 will assume that these problems will continue indefinitely. If these problems are somehow corrected in the real system, but the effect of the corrections is not reflected in the model, BEST/1 performance prediction is likely to be oerly conseratie, and might result in premature upgrade recommendations. Therefore, it is adisable to correct such tuning or malfunction problems. Check the interal between samples when measuring data. Do not use ery large interals. The default, 15 minutes, is good for most cases. Figure 50 begins the flow of workload INTER analysis and alidation. Work with Workloads Model/Text: TEST Workload Analysis Type options, press Enter. 1=Create 2=Change 3=Copy 4=Delete 5=Display 6=Print 7=Rename 8=Sae workload to workload member 9=Edit transactions Opt Workload Text _ BATCH Measured from BEST1LAB (Q ) 2 INTER Measured from BEST1LAB (Q ) _ QDEFAULT Measured from BEST1LAB (Q ) Bottom F3=Exit F6=Add saed workload F9=Add predefined workload F12=Cancel F13=Combine workloads Figure 50. Work with Workloads Validation Example By being able to describe your model at arious leels of detail, it is possible to grow or change your model at the workload, function or transaction leel. Howeer, the purpose of this chapter is to alidate the model s workload details rather than using it for growth analysis. The relationship between these entities can be found in Chapter 2. Workload Concepts and it is graphically depicted in Figure 12 on page 22. Use option 2 (Change) to change workload details. If you are not making any changes, use option 5 (Display), to display the workload, function, or transaction details on each display. Note: If you want to go directly to the Change Transaction display to edit the transaction, use option 9 (Edit Transactions) from the Work with Workloads display. Chapter 6. Model Analysis and Calibration 75

96 Working with Functions Figure 51 shows a function defined for a particular workload. Although changing function and transaction details is supported, do not change anything unless you hae calibrated the model and you understand the effect of your changes. Workload...: INTERACTIV CPU architecture...: *RISC Application type...: *DEFAULT Change Workload Type changes, press Enter. Press F13 to specify a single application type for all transactions. Workload text... Measured from MASCK1 (Q ) Workload type... *NORMAL F4 for list Usage mode =Casual, 2=Interrupted, 3=Steady, 4=N/A Functions Ag K/T Tns per Function Function Text per User (secs) Inter Non-inter Function of INTERACTIV Bottom F3=Exit F4=Prompt F6=Work with functions F9=Specify chars to comm lines F10=Specify I/Os to ASPs F12=Cancel F24=More keys Figure 51. Change Workload On this display you can change: Workload type The number of functions per user per hour The aerage key/think time The usage mode BEST/1 defaults to one function per user per hour for all workloads created from measured data. For workloads built from measured data, a workload type of *BATCHJOB, which represents batch jobs, indicates that the jobs in that workload hae all met the following criteria: All jobs are batch type (non-interactie and batch). All jobs were actie for at least 95% of the measurement interal, that is, eery job was more or less continuously actie throughout the interal. Storage pools used by these jobs serice only batch transactions (no system tasks). As arious system changes are analyzed, BEST/1 predicts an increase or decrease in the number of transactions processed for these batch jobs. That means that if system performance improes, BEST/1 predicts how many more transactions can be processed by each batch job. If system performance deteriorates, BEST/1 predicts that less transactions will be processed. 76 BEST/1 Capacity Planning Tool V5R1

97 If this is not how you would like your work treated, change the workload type to *NORMAL. You can access the Change Workload display, by selecting option 2 (Change) from the Work with Workloads display. For workloads that are measured, user-defined or predefined, that you would like to be considered as batch type, change the workload type to *BATCHJOB, and check the actual number of actie jobs has been typed on the Specify Objecties and Actie Jobs display. Conersion factors can be either CISC or RISC. For predefined CISC-to-RISC conersion Factors, see Editing CISC-to-RISC Conersion Factors on page 105. On the display shown in Figure 51 on page 76, use function key F6 (Work with Functions) to access the Work with Functions display, then select option 2 (Change) to access the Change Function display as shown in Figure 52. Change Function Workload...: INTERACTIV Measured from BEST1LAB (Q ) Function...: INTERACTIV Change fields, press Enter. Function text... Function of INTERACTIV Key/Think time Seconds Additional delays....0 Seconds Transaction Pool Transactions CPU Time Total Type ID Priority per Function (Secs) I/Os Bottom Transaction Type: 1=Interactie, 2=Non-interactie F3=Exit F6=Work with transactions F12=Cancel Figure 52. Change Function This display enables you to change for each transaction in a function: Key/Think time Additional delays Transaction priority Transactions per function Verify that the following parameters are correct: Key/think time is appropriate Distribution into storage pools is correct System or non-interactie transactions correlate with the interactie transactions Priorities are set correctly On this display one transaction has a priority of 11. On the iseries serer in the example there were no jobs running at this priority. The model approximates the Chapter 6. Model Analysis and Calibration 77

98 combined effect of a job and a task running in the same pool, by using a weighted aerage of their priorities. In this case the weighting is approximately 90% running at priority 10 and approximately 10% running at priority 20, to gie a resulting priority of 11. Jobs running at a priority 0 are not aeraged with jobs running at other priorities. Working with Transactions In order to change transaction details, you can access the Change Transaction display by pressing F6 (Work with Transactions) as shown in Figure 52 on page 77. This presents a similar display, as shown in Figure 53. Type a 2 in the Opt field to proceed to the Change Transaction details display shown in Figure 54 on page 79. You can also display the transaction by using option 5 (Display). Work with Transactions Workload...: INTERACTIV Measured from BEST1LAB (Q ) Function...: INTERACTIV Function of INTER Type options, press Enter. 2=Change 3=Copy 4=Delete 5=Display Transaction Pool Transactions CPU Time Total Opt Type ID Priority per Function (Secs) I/Os _ _ Bottom Transaction Type: 1=Interactie, 2=Non-interactie F3=Exit F6=Create transaction F12=Cancel Figure 53. Work with Transactions Display On the Work with Transactions display shown in Figure 53 you can use the following functions: Create a new transaction (function key F6) Copy a transaction (Option 3) Delete a transaction (Option 4) Display a transaction (Option 5) The Change Transaction display as shown in Figure 54 on page 79 enables you to display or change specific details of a transaction. 78 BEST/1 Capacity Planning Tool V5R1

99 Change Transaction Workload...: INTERACTIV Measured from MASCK1 (Q ) Function...: INTERACTIV Function of INTERACTIV Type choices, press Enter. Transaction Type =Inter, 2=Non Pool ID... 3 F4forlist CPU priority CPUtime Secs (on B10) Database time Secs (on B10) Permanent writes percent Chars transferred in Chars transferred out Exceptional wait....0 sec Application type... *DEFAULT F4 for list More... DB Reads DB Writes NDB Reads NDB Writes Sync I/Os Async I/Os F3=Exit F4=Prompt F6=Calculate B10 CPU time F12=Cancel F13=Change paging behaior Figure 54. Change Transaction Details Most of the fields in Figure 54 are described in detail in Chapter 2. Workload Concepts. Note: CPU seconds are gien as B10 CPU seconds, not CPU seconds for the current OS/400 model. See Function Definition more information on CPU seconds. Function key F6 proides a method for conerting CPU model-dependent CPU seconds shown on a Performance Tools report to B10 CPU seconds. The input to the Calculate B10 CPU Time display is in CPU milliseconds. A shortcut to specifying CPU time for the current OS/400 model is by typing in a negatie alue which then conerts the CPU seconds to the equialent in B10 seconds. If you are deleting, adding, or changing storage pools, you might hae to change a transaction s storage pool accordingly. Howeer, changing these alues is not recommended for the initial modeling process. Verifying the Number of Actie Jobs in the Workload After erifying that the workloads reflect the actual work on your system, you should ensure the objecties contain the number of actie jobs that represents the work on your system. The number of actie jobs calculated by BEST/1 may not be what you first expect, but is produced using the following methods: For workloads containing interactie jobs: 1. The actie seconds per branch (Local, LAN, WAN) of interactie jobs comprising this workload are summed. (Actie seconds are defined as seconds where the aerage transaction rate exceeds 1 transaction per 5 minutes) 2. Diide each total of actie seconds per branch by the total seconds in the measurement interal to produce the aerage actie jobs per branch. Chapter 6. Model Analysis and Calibration 79

100 For example, if the measurement interal was 300 seconds, and one workload had the following jobs: Table 3. Workloads Containing Interactie Jobs Job Seconds Job Transactions Job Actie Seconds Job Branch DSP Local DSP Local RDSP WAN Note: Workload totals: 300 Local actie seconds--> 1.0 actie job 150 WAN actie seconds --> 0.5 actie jobs The exception to this processing occurs when there are interactie jobs, but no actie seconds for a workload on a particular branch. In this situation the actie jobs for that branch in that workload is set to 0.1. In the aboe example, if the job DSP02 aboe had been LAN instead of Local, the workload would hae had 0.1 actie LAN jobs in addition to its other actie jobs. For workloads containing only non-interactie jobs and do not meet the criteria for *BATCHJOB workloads: For each branch where there is actiity, actie jobs are set to 1. For System-only workloads: Actie jobs are set to 1 Local job. For *BATCHJOB workloads: Actie jobs are set to the number of batch jobs obsered in the interal which contributed the workload. To iew the number of actie jobs, select option 2, (Specify Objecties and Actie Jobs) from the Work with BEST/1 Model display. The objecties are shown in Figure 55 on page BEST/1 Capacity Planning Tool V5R1

101 Specify Objecties and Actie Jobs Model/Text: BEST1MODEL Type changes, press Enter. Workload Actie ---Interactie---- Non-inter Workload Connect Type Jobs Rsp Time Thruput Thruput INTERACTIV *LOCAL *NORMAL INTERACTIV *LAN *NORMAL INTERACTIV *WAN *NORMAL BATCH *LOCAL *BATCHJOB BATCH *LAN *BATCHJOB BATCH *WAN *BATCHJOB QDEFAULT *LOCAL *NORMAL QDEFAULT *LAN *NORMAL QDEFAULT *WAN *NORMAL F3=Exit F11=Show positie quantities F12=Cancel F15=Sort by connect type F19=Work with Workloads Bottom Figure 55. Validate Model Objecties In the example shown in Figure 55, BEST/1 has calculated 10.2 actie local jobs for the INTER local workload. For non-interactie workloads with actiity, BEST/1 uses a alue of one or less for all work done by each group (local, LAN, and WAN). Interactie workloads, which can include non-interactie work, hae actie workstations for each group where BEST/1 detects interactie actiity. For *BATCHJOB workload types, the alue represents the number of concurrent actie jobs. Remember BEST/1 does actie job aeraging and does show fractional alues for the number of actie jobs. See Calibrating Other Resources on page 90 for details on ways to change the number of actie jobs to match your expectations. No WAN workstation jobs were actie during the period of performance data collection. BEST/1 does not fully model all communication elements that may affect non-local response times. For example, it assumes that all WAN workstation controllers hae identical characteristics. It deals similarly with local workstation and LAN controllers. BEST/1 does not model tape, diskette, or CD-ROM actiity. Note: If you are using measured data, you may want to use the Display Performance Data (DSPPFRDTA) command, Display communications details, and Display remote jobs options to assist you in erifying the aerage number of LAN and WAN workstation jobs shown by BEST/1. Unless all WAN or LAN workstations were ery busy during the collection period, the aerage number of actie remote jobs shown on the BEST/1 Specify Objecties and Actie Jobs display will be less than the number of Chapter 6. Model Analysis and Calibration 81

102 jobs shown by the DSPPFRDTA command. You hae to understand the WAN and LAN workstation application actiity to accept or reject the number shown by BEST/1. Changing the application type Beginning in V4R5, BEST/1 proides the capability to model the differences in workload scaling across different CPU models by adjusting transaction times according to application type. To enable this modeling, you must collect performance data by using one of the following methods. Each application type is adjusted differently depending on the CPU model on which the application is being run. By changing the application type, you can tune the modeling results. Note: The application type of each transaction can be determined only when you create a BEST/1 model with one of these methods: Use the performance monitor. Turn on the internal data parameter when starting the performance monitor. Use this command: STRPFRMON INTDTA(*YES). Specify the enhanced capacity planning category by using either of these methods: Use the Management Central Start Collection (QYPSSTRC) API and specify the enhanced capacity planning alue of *ENHCPCPLN. Use this command: CALL PGM(QYPSSTRC) PARM('*PFR ' '*ENHCPCPLN' X' ') Use Operations Naigator. Expand Management Central >expand endpoint system >expand Configuration and Serice >expand Collection Serices and right-click Start collecting >select Data to Collect tab from the Start Collection Serices page. Select the PEX Data - Processor Efficiency category. The performance monitor creates a performance explorer definition named QPFRINTDTA; Collection Serices creates a performance explorer definition named QPMIPEXEI. In all cases, if a definition already exists, it is deleted and re-created. The performance monitor and Collection Serices both start a performance explorer collection. Performance monitor starts session id QPFRMON and Collection Serices starts session id QPMINTPEXD. In all cases, the collection name can conflict with other performance explorer collections. To change the application type, press F13 (Select application type) from the Change Workload display. You hae to press F24 (More keys) to see F BEST/1 Capacity Planning Tool V5R1

103 Select Application Type CPU model...: 23BB ( ) Type option, press Enter. 1=Select CPU Time Application Adjustment Opt Type Factor *DEFAULT 1.00 *OLTP 1.02 *GEN_DB 1.13 *EOD_DB 1.18 *GEN_CA 1.23 *COLLABRTV 1.23 *APPSERVER 1.23 *COMPUTE 1.19 *APPLTYPE *APPLTYPE F12=Cancel Bottom Figure 56. Select Application Type If the performance monitor data (not Collection Serices data) indicates that the jobs within a workload hae significant deiations in CPU and DASD usage from what BEST/1 normally assumes, BEST/1 uses the adjustment factors to do capacity planning functions. This actiity is an extension to what BEST/1 did when it modeled CISC-to-RISC migrations. If you do not use any of the preious methods to create a BEST/1 model, then BEST/1 characterizes the workload as *DEFAULT and performs the same work as it did in preious releases. The application types that are described coer a range of application types, but they do not coer eery possible application. Choose an application type from the list that best describes your work. *DEFAULT This application type is used if no type is specified or if measurement data does not include application type information. Prior to V5R1, the *DEFAULT alue was always the application type when the performance data was collected with Collection Serices. CPU serice time and I/O counts are not adjusted for transactions with this application type. *OLTP The On Line Transaction Processing (*OLTP) type is highly interactie with many transactions of short duration. It is primarily comprised of interactions with the database and interactions with the end users displays. This alue includes the interactie applications from the character-based interface, simple ODBC, and other low CPU and low database resource usage applications. *GEN_DB The Generic Database (*GEN_DB) type is similar to *OLTP except that it can also include complex transactions and background work. At least some Chapter 6. Model Analysis and Calibration 83

104 Calibrating the Model part of this workload does not contain interactie transactions. This is the most common application type. It combines transaction processing with batch database processing. *EOD_DB The End of Day Database (*EOD_DB) type coers the situation where a relatiely small number of jobs process a large amount of data. It does not hae to run at the end of the day. It uses the system resources in a similar way to end-of-day or end-of-week applications. Some query applications fit this category as well as background batch jobs and oernight jobs that process from an OS/400 database. *GEN_CA The Generic Client Access (*GEN_CA) type is similar to *OLTP and *GEN_DB except that more of the application requirements are satisfied by client requests to a database serer. Applications that are associated with this type are transaction processing with Jaa, Client Access processing that uses small to medium queries, and Web-based enironments. *COLLABTRV The Collaboratie processing (*COLLABTRV) type is typical of, but not limited to, Domino applications. This type can be characterized as haing a large number of end user jobs that interact with the system often but that do not require significant use of an OS/400 database. *APPSERVER The Application Serer (*APPSERVER) type is similar to *COLLABRTV except that a significant amount of processing is required for each interaction with the user. This is similar to many middle-tier applications of a three-tier enironment where the system spends significant time processing and formatting information on behalf of end user client systems and primary database serers. *COMPUTE The Compute Intensie (*COMPUTE) type is an enironment where substantial CPU is required for each unit of work. The processor light should be running at or near 100% while processing a request of this kind of workload. Some Jaa-based applications are associated with this application type. *APPLTYPE1 This alue is resered. *APPLTYPE2 This alue is resered. Model calibration generally refers to the process of checking and reising a model so that it represents the system you are modeling in a way that is necessary for the study you are conducting. Specific items you can change include calculated response time and resource utilization. The predicted and the measured alues should match as closely as possible. The throughput remains unchanged during this process. Naturally, there are assumptions that the model makes in predicting response time and other utilization leels. Because of this, there may be a difference between measured and predicted response time, IOP utilization, and so on. When this happens, and the difference is more than 10% of measured resource utilization and 84 BEST/1 Capacity Planning Tool V5R1

105 20% or 0.5 seconds for response times, the model is not calibrated. For *BATCHJOB workloads, measured and predicted throughput should be within 10%. Differences may be caused by many factors. BEST/1 is not able to model program dependent factors, such as long waits for objects, record locks, seize locks, or sae/restore actiity on a multifunction IOP. BEST/1 assumes data is eenly spread across all disk arms. This is often not the case, and may cause small discrepancies between measured and predicted. Within the performance data, the speed of a communications line is determined from the line configuration. The modem speed can be different from this configured speed. This may cause the line utilization to be calculated based on an incorrect line speed. On communication lines with utilizations below 10%, the percent line oerhead is set to 2%. This occurs so that polling on lines with little actiity will not be oerstated when the communications actiity increases. Due to this adjustment, communications IOP and lines may show discrepancies between measured and predicted. Workload type can affect calibration of any or all resources, and other workload response times. For example, if *BATCHJOB is your workload type, then it should hae the behaior appropriate for batch workloads, as described in Working with Functions on page 76. Comparing Measured and Predicted Data Analyze the model with option 5 (Analyze current model) or option 7 (Specify workload growth and analyze model). If you use option 7, be sure to specify one period to analyze and set Determine configuration changes to N. Select option 5 (Display) next to Measured and Predicted Comparison on the Work with Results display. This line is only displayed if your model has neer been saed. If this line is not displayed, then select option 5 (Display next to Analysis Summary). On the Display Analysis Summary display ( Figure 63 on page 93), press F11. Either method displays the measured and predicted alues to facilitate comparison of these alues. Note: You can perform additional modeling functions that are not described in this chapter. See Chapter 5. System Configuration for configuration functions and Chapter 7. Modeling Changes to the System for growth functions. A large difference between measured and predicted resource utilization or response time should be examined to determine if the measured data is appropriate for further modeling efforts. If the difference between measured and predicted resource utilization is greater than 10% or the difference in response time is greater than 20% or.5 seconds, the model is not calibrated. The Measured and Predicted Comparison option on the Work with Results display or the Analysis Summary display proides an easy way to compare resource utilization and response time. Notes: 1. The measured utilizations for the LAN IOA and WAN IOA fields are blank because this information is not aailable from the performance data. 2. Measured alues for disk, multifunction, LAN, and WAN IOP utilizations are determined differently than in prior releases of BEST/1. Chapter 6. Model Analysis and Calibration 85

106 Measured and Predicted Comparison Measured Predicted Total CPU util...: Database util...: Disk IOP util...:.0.0 Disk arm util...:.1.0 Disk IOs per second...: Multifunction IOP util...:.8.0 Disk IOA util...:.9.1 LANIOAutil...:.0 WANIOAutil...:.0 Integrated PC Serer IOA util...:.0.0 Interactie: CPUutil...:.0.0 Int rsp time (seconds)...: Transactions per hour...: Non-interactie thruput...: Performance estimates -- Press help to see disclaimer. F3=Exit F6=Print F9=Work with spooled files F12=Cancel F17=Calibrate response time More... Figure 57. Measured and Predicted Comparison Display If non-interactie throughput is not within 10%, change *BATCHJOB workloads to *NORMAL and reanalyze the model. If you wish to hae response time differences automatically calibrated you can press F17 (Calibrate response time) on the Measured and Predicted Comparison display. This is discussed in Calibrating Response Time on page 87, and is possible when predicted response is less than measured. To calibrate resource utilization, press F22 (Calibrate model) from the Work with BEST/1 Model display. For more information, see Calibrating Other Resources on page 90. The following information discusses how to perform the calibration process. Howeer, anytime there are significant differences between measured and predicted alues, you must thoroughly reiew other Performance Tools reports to determine if an application design problem needs to be resoled or if you need to make different start and stop time choices from the performance data. If your model initially had large deiations between measured and predicted alues, the following are recommended actions: Inestigate application design bottlenecks such as object or record locks or enironment restrictions, such as communications line or disk error retries. The Start Serice Tools (STRSST) command functions proide an interface to error log information and the Performance Tools Resource Interal report proides good information, including communications line actiity details. The Transaction Report - Job Summary can identify exceptional wait conditions, but requires that you issue the Start Performance Trace (STRPFRTRC) command. Create another model using a different time period or a different production enironment when particular processing, such as month-end query or sae/restore, is not actie. Change *BATCHJOB workloads to *NORMAL and reanalyze the model. 86 BEST/1 Capacity Planning Tool V5R1

107 After you create a model, go to the Work with All Spooled Files display by pressing F9 (Work with spooled files) on the Measured and Predicted Comparison display. Look at the CRTBESTMDL file with the User Data description of your model name. This proides information about problems in the performance data. Run the Analyze Performance Data (ANZPFRDTA) command against the data. You can compare both models and more easily determine what kind of calibration is needed. Calibrating Response Time Response time calibration attempts to make the measured and predicted response times agree. Compare these alues and if the difference between the predicted and measured response times is greater than 20% or.5 seconds, consider calibrating the response time. The difference between predicted and measured interactie and non-interactie transactions should be within 10% before you begin calibrating response times. If predicted response is less than measured response, initiate the calibration process by pressing F17 (Calibrate response time) on the Measured and Predicted Comparison display in Figure 58 on page 88. BEST/1 automatically spreads exceptional wait times across all the interactie workload transactions, which increases the predicted response time from 0.5 seconds to 1.7 seconds. If you hae created your model by selecting option 5 (Create BEST/1 model from performance data) from the BEST/1 main menu, then Response times are automatically calibrated if predicted response times are less than measured. If predicted response time is greater than measured response time, the F17 (Calibrate response time) will not be displayed. Note: The measured utilizations for the LAN IOA and WAN IOA fields are blank because this information is not aailable from the performance data. Chapter 6. Model Analysis and Calibration 87

108 Measured and Predicted Comparison Measured Predicted Total CPU util...: Disk IOP util...: Disk arm util...: Disk IOs per second...: Multifunction IOP util...: Disk IOA util...: LANIOAutil...: 8.7 WANIOAutil...: 25.1 Integrated PC Serer IOA util...: LANIOPutil...: LAN line util....: WANIOPutil...: WAN line util....: Interactie: CPUutil...: Int rsp time (seconds)...: Transactions per hour...: Non-interactie thruput...: F3=Exit F6=Print F9=Work with spooled files F12=Cancel F17=Calibrate response time Figure 58. Measured and Predicted Comparison for Calibration After BEST/1 automatically calibrates the response time, it reanalyzes the model. A message at the bottom of the Measured and Predicted Comparison display indicates Transaction exceptional wait times processed to calibrate response time. After analysis is complete, compare against measured data again and you will see internal response time in seconds adjusted as shown in Figure 59 on page 89. Note: The measured utilizations for the LAN IOA and WAN IOA fields are blank because this information is not aailable from the performance data. 88 BEST/1 Capacity Planning Tool V5R1

109 Measured and Predicted Comparison Measured Predicted Total CPU util...: Disk IOP util...: Disk arm util...: Disk IOs per second...: Multifunction IOP util...: Disk IOA util...: LANIOAutil...: 8.7 WANIOAutil...: 25.1 Integrated PC Serer IOA util...: LANIOPutil...: LAN line util....: WANIOPutil...: WAN line util....: Interactie: CPUutil...: Int rsp time (seconds)...: Transactions per hour...: Non-interactie thruput...: F3=Exit F6=Print F9=Work with spooled files F12=Cancel F17=Set all exceptional wait alues to 0 Figure 59. Measured and Predicted Comparison (After Calibration) The exact exceptional wait time as determined by the model can be displayed by iewing the transaction detail. In the example in Figure 60 on page 90 the exceptional wait time is milliseconds (approximately 1.2 seconds). Once you hae had response time calibration performed and had the model re-analyzed, any exceptional wait time will be spread against all interactie non-*lic transactions. Response time will show the larger alue and the Exceptional wait field will contain the exceptional wait time in milliseconds that was added to achiee the measured data results. Analyze model and analysis summary can be used to identify differences in predicted ersus measured resource utilizations and response time. This can be used to estimate exceptional wait time. Howeer, large differences (20% or.5 seconds) in predicted ersus measured information may jeopardize the integrity of the model. Chapter 6. Model Analysis and Calibration 89

110 Change Transaction Workload...: INTER Measured from TESTLIB Function...: INTER Function of INTER Type choices, press Enter. Transaction Type =Inter, 2=Non Pool ID... 4 F4forlist CPU Priority CPUtime Secs (on B10) Permanent writes percent Chars transferred in Chars transferred out Exceptional wait Msec Paging behaior... *GENERIC F4 for list Database Non-database----- Reads Writes Reads Writes Sync I/Os Async I/Os F3=Exit F4=Prompt F6=Calculate B10 CPU time F12=Cancel F13=Change paging behaior Figure 60. Display (Change) the Transaction Detail After Calibration Calibrating Other Resources For measured data there may be some cases with a greater than 10% difference between predicted and measured alues for CPU, disk IOP, and disk arm utilizations and the number of disk I/Os per second. The first action should be to reiew the measured time interals selected and determine if some one-of-a-kind processing was being done, such as a long running query or a long running sae and restore function. Consider changing the time interals selected first. If that does not resole the differences you may need to take actions discussed in the remainder of this section. BEST/1 enables you to manually calibrate resource utilizations and disk I/Os by adjusting workload functions and objecties, until the predicted resource utilization or I/Os is within 10% of the measured alue. Manual calibration requires thorough knowledge of the parameters you are changing, especially when you are dealing with transaction details. Function key F22 (Calibrate model) on the Work with BEST/1 Model display (Figure 61 on page 91), starts the manual calibration process. In this mode, changes are interpreted as fine-tuning the model to reflect actual conditions as opposed to normal What-if...? analysis mode. Your measured and predicted throughput should match closely before you proceed with manual calibration. Utilization depends primarily on throughput and serice time. If throughput measured and predicted alues do not match, check recommendations for saturation. If your throughput matches at this point, then your next option to calibrate resource utilization is to change serice time. 90 BEST/1 Capacity Planning Tool V5R1

111 You can use manual calibration when your model is already calibrated. For example, if you want to change functions per user into a alue that is based on actual use, such as 27 loan updates per hour, you can change functions per user to 27 and still keep the total number of transactions constant. The following changes to the model hae no effect on workload throughput or resource utilization, which remains the same in manual calibration mode. Number of functions per user Number of actie jobs Analyze your model and display the Analysis Summary. Press F11 to compare against measured alues and you will see both the measured and predicted alues. When you are finished calibrating your model manually, you can press F22 again to return to the normal What-if...? analysis mode, where changes are interpreted as What-ifs...?. For example, What if the number of workload jobs are doubled? Doubling the number of workload jobs in this mode will double the workload arrials, and more transactions will be processed. Note: In manual calibration mode, measured transaction throughputs are maintained. Work with BEST/1 Model Performance data...: Model/Text...: SIZING Complex Sizing Scenario Select one of the following: 1. Work with workloads 2. Specify objecties and actie jobs 5. Analyze current model 6. Analyze current model and gie recommendations 7. Specify workload growth and analyze model 10. Configuration menu 11. Work with results More... Selection or command ===> F3=Exit F4=Prompt F9=Retriee F12=Cancel F15=Sae current model F17=Analyze using ANZBESTMDL F22=Calibrate model F24=More keys Model Analysis Results Figure 61. Work with BEST/1 Model - Calibrate Model When satisfied that the model is calibrated, return to the normal What-if...? analysis mode by pressing F22 again on the Work with BEST/1 Model display. After determining that workload definitions and objecties are acceptable in comparison to your actual system, select option 5 (Analyze current model) or option 6 (Analyze current model and gie recommendations) on the Work with BEST/1 Model display shown in Figure 61. The Work with Results display appears with a message at the bottom of the display that indicates when analysis has completed. Chapter 6. Model Analysis and Calibration 91

112 Work with Results Printed report text... Type options, press Enter. 5=Display 6=Print Opt Report Name Measured and predicted comparison Analysis Summary Recommendations Workload Report ASP and Disk Arm Report Disk Resources Report Main Storage Pool Report Communications Resources Report All of the aboe Bottom F3=Exit F12=Cancel F14=Select saed results F15=Sae current results F18=Graph current results F19=Append saed results F24=More keys Figure 62. Work with Results Model Analysis Note: If your reiew of the analysis results is satisfactory, you can sae the current results (F15) and graph the current results (F18). You may also append saed results (F19) to include in a multiple results graph. See Chapter 10. Printing Model Reports and Graphs on page 229 for more information on BEST/1 graphics support. Select saed results (F14) lets you stop reiewing the current results and reiew a preiously saed set of results. Analysis Summary The analysis summary shows oerall hardware configuration, resource utilization, response time, and transactions per hour (throughput). Examine the following: Hardware utilizations ASP I/O rate Interactie throughput Interactie response time Non-interactie throughput It is optional whether you also compare the BEST/1 analysis summary to the System and Component reports. 92 BEST/1 Capacity Planning Tool V5R1

113 Display Analysis Summary CPU Model / release leel...: 2D6C V4R5M0 Main Storage...: MB Quantity Predicted Util CPU...: 8/8.2 Database...:.2 Disk IOPs...: 4.1 Disk ctls...: 8.0 Disk arms...: More... Interactie Non-interactie CPU utilization %...:.0.2 Transactions per Hour...: Local response time (seconds)...:.0.2 LAN response time (seconds)...:.0.0 WAN response time (seconds)...:.0.0 Performance estimates -- Press help to see disclaimer. F3=Exit F10=Re-analyze F11=Measured and predicted comparison F12=Cancel F15=Configuration menu F17=Analyze multiple points F24=More keys BEST/1 CPU model 740 2D6C refers to IBMCPU model Figure 63. Analysis Summary Display for Calibration Recommendations You can reiew the BEST/1 recommendations where you will see messages suggesting pool size or actiity leel changes and indicating if any resource is oer the utilization guidelines. If you use option 6 (Analyze the current model and gie recommendations), you also see additional recommendations if any specified performance objectie has not been satisfied. Alternatiely, if you use option 7 (Specify workload growth and analyze model) with Determine new configuration set to Y, you also see configuration changes to fix any specified performance objectie that has not been satisfied. Typically these additional configuration changes or recommendations describe in detail out CPU model and storage size and disk hardware features, including the IOP feature and disk arm feature numbers and the numbers of each IOP and disk arm. Figure 64 on page 94 is a sample display of recommendations. Chapter 6. Model Analysis and Calibration 93

114 Display Recommendations ***** Analysis Exceptions ***** Utilization of for communications IOP CC03 exceeds objectie of Utilization of for communications IOP CC05 exceeds objectie of ***** Analysis Recommendations ***** Moe 3 Communication lines from IOP CC03 to CIOP1 Moe 4 Communication lines from IOP CC05 to CIOP2 Create communications IOP(s) Moe 1 Communication lines from IOP CC03 to CC01 Moe 1 Communication lines from IOP CC05 to CC04 Bottom Performance estimates -- Press help to see disclaimer. F3=Exit F10=Change to recommended configuration and re-analyze F12=Cancel F15=Configuration menu F17=Analyze multiple points F24=More keys Figure 64. Model Recommendations A detailed discussion of the recommendations and how to specify performance objecties is discussed in Chapter 7. Modeling Changes to the System. Workload Report The workload report shows, for each workload, CPU utilization, transaction throughput, LAN and WAN response time, and response time components. Response time components are CPU, disk I/O, pool, communications, and other, as seen in Figure 66 on page 95. A large other indicates that some kind of exceptional wait state (object lock,...), or additional delays are present. Figure 65 on page 95 is a sample screen of the workload report. 94 BEST/1 Capacity Planning Tool V5R1

115 Display Workload Report Period: Analysis CPU Thruput Response Times (Secs) Workload Type Util per Hour Internal Local LAN WAN INTER BATCH QDEFAULT Type: 1=Interactie, 2=Non-interactie, 3=*BATCHJOB Performance estimates -- Press help to see disclaimer. F3=Exit F10=Re-analyze F11=Response time details F12=Cancel F15=Configuration menu F17=Analyze multiple points F24=More keys Bottom Figure 65. Model Workload Report The non-interactie workloads and the non-interactie transactions work contained in interactie workload INTER for this example show zero for response time (shown as Transaction Type 2 in the Type field). The WAN column shows there were no WAN workstation jobs actie during the performance data collection period. Function key F11 proides a iew of response time that shows CPU, disk I/O, pool, comm, and other components of response time. Display Workload Report Period: Analysis CPU Total Rsp Time Secs spent in Workload Type Connect Rsp Time CPU I/O Pool Comm Other INTER 1 *LOCAL BATCH 3 *LOCAL QDEFAULT 2 *LOCAL Type: 1=Interactie, 2=Non-interactie, 3=*BATCHJOB Performance estimates -- Press help to see disclaimer. F3=Exit F10=Re-analyze F11=Response time details F12=Cancel F15=Configuration menu F17=Analyze multiple points F24=More keys Bottom Figure 66. Model Workload Report - Response Time Components If growth for multiple periods had been analyzed, the report would show information for each period. You can page to iew periods not displayed. Chapter 6. Model Analysis and Calibration 95

116 ASP and Disk Arm Report This report shows, for each ASP, the number of disk arms and a set of disk arm statistics, such as percent busy and I/Os per second. Figure 67 is an example of the disk report. Display ASP and Disk Arm Report Period: Analysis I/Os Disk Disk Subsystem Aerage ASP Arms per Sec Pct Busy Msecs per I/O Performance estimates -- Press help to see disclaimer. F3=Exit F10=Re-analyze F11=Display Disk Resource report F12=Cancel F15=Configuration menu F17=Analyze multiple points F24=More keys Bottom Figure 67. Disk ASP and Disk Arm Report If growth for multiple periods had been analyzed, the report would show information for each period. Disk Resources Report This report shows, for each disk IOP and IOA, IOP or IOA utilization, number of disk arms, and the same disk arm statistics shown under the Disk ASP and Arm Report. The information is shown in Figure 68 on page BEST/1 Capacity Planning Tool V5R1

117 Display Disk Resources Report Period: Analysis I/Os Disk Disk Subsystem Aerage Resource Type Arms per Sec Util Pct Busy Msecs per I/O CMB01 *MFIOP DI10 *IOA SI04 *IOP Bottom Performance estimates -- Press help to see disclaimer. F3=Exit F10=Re-analyze F11=Display ASP and Disk Arm report F12=Cancel F15=Configuration menu F17=Analyze multiple points F24=More keys Figure 68. Disk Resources Report If growth for multiple periods had been analyzed, the report would show information for each period. Main Storage Pool Report This report shows for each pool, size and actiity leel, actie-to-ineligible alues, and number of synchronous database and nondatabase reads per second. The number of synchronous reads per second is used as an approximation of the number of database and nondatabase page faults per second. The Work Management and Performance Tools for iseries books contain guidelines for page faults per second. For more information on how synchronous reads relate to page faults, see Editing Sync Reads Guidelines on page 103. An example is shown in Figure 69 on page 98. Chapter 6. Model Analysis and Calibration 97

118 Display Main Storage Pool Report Period: Analysis Pool Act Size Ineligible -----Ag Number----- Sync Reads ID Ll (KB) Wait (sec) Actie Ineligible per Sec Bottom Performance estimates -- Press help to see disclaimer. F3=Exit F10=Re-analyze F12=Cancel F15=Configuration menu F17=Analyze multiple points F18=Specify objecties F24=More keys Figure 69. Main Storage Report In this example, the number of synchronous reads per second is 1.2 for pool 1 (machine pool). This is greater than the good alue of less than 1 shown in the Work Management book for the machine pool. BEST/1 will make a recommendation to increase the size of this pool. See Memory Modeling on page 135 for additional details on BEST/1 memory modeling. Communications Resources Report This report shows communications IOP and IOA utilization and line resource information including utilization, response time per transaction, number of lines, and line speed. A line resource can represent one or more lines, all of which hae the same speed. This alue is shown in the Number of Lines column. 98 BEST/1 Capacity Planning Tool V5R1

119 Display Comm Resources Report Period: Analysis Oerhead Rsp Time Per Nbr of Line Speed Resource Type Util Util Trans (Sec) Lines (Kbit/sec) CC01 *IOP 15.9 LANLINE1 *LINE CC02 *IOP.0 WANLINE1 *LINE CMB01 *MFIOP 5.8 LIN19 *IPCS 7.2 D27DBF0101 *LINE LIN21 *IOA 29.1 CMN08 *LINE LIN25 *IOA 21.1 QESLINE *LINE F3=Exit F10=Re-analyze F12=Cancel F15=Configuration menu F17=Analyze multiple points F18=Specify objecties F24=More keys Bottom Saing Results Figure 70. Communications Resource Report BEST/1 enables you to sae the results of the current analysis. The results can be saed in two types of files: Internal Format File (binary) Externally Described File (EDF) You can sae results (and models) to a results file to use the results again, in other modeling scenarios. You can also sae results (and models) to EDF members to access them using other OS/400 products, such as Query, BGU, or Client Access file transfer. You can choose to sae the results with or without the EDF member. On the Work with Results display, press F15 (Sae current results) to sae the current results. The display shown in Figure 71 on page 100 appears. Chapter 6. Model Analysis and Calibration 99

120 Change alues if desired, press Enter. Sae Current Results Sae to Results member: Member... RESULTS Name Library... JONES Name Text... Replace... N Y=Yes, N=No Period name... Analysis Name Externally described member information: Sae... N Y=Yes, N=No Member... *MEMBER Name, *MEMBER Library... *LIB Name, *LIB Text... Replace... *REP Y=Yes, N=No, *REP EDF processing program... *NONE Name, *NONE Library... *LIBL Name, *CURLIB, *LIBL F12=Cancel Figure 71. Sae Current Results If you want to rename the Results member, type a new name in the Member field. The Library field indicates in which library the member will be saed. If you are renaming your results, leae the default of N in the Replace field, otherwise type Y to replace the current member. If you use option 5 or 6 to analyze your model, the Period Name field uses a predefined name of Analysis to name a single period in the current results. If you append multiple single period results, rename the period name or all the periods will hae the same name. If you want to sae Externally described member information, as well as the Results member, type a Y in the Sae field. Name the member and the library in which the externally described member will be saed. In the Replace field, enter Y to replace the current externally described member. Type N if you only want the information in a BEST/1 internal file. Type *REP to use the same alue specified in the results member replace field. If the EDF processing program is not *NONE, and EDF results are saed, the specified program is called to process the EDF results member that was saed. For example, you can specify the BGS-written exit program BEST1TOVIZ to create an input file member for BEST/1 Visualizer from the EDF results member. A similar display to sae the current model can be accessed from the Work with BEST/1 Model display using F15 (Sae current model). 100 BEST/1 Capacity Planning Tool V5R1

121 Chapter 7. Modeling Changes to the System This chapter shows some of the changes you can make to your model to meet your objecties. By adding growth to your workloads, editing system guidelines and thresholds, and changing system resources you can ask What-if...? questions which help you with performance prediction. After you analyze the model, you can iew the results in seeral reports. Specifying Performance Objecties This section discusses how to specify the performance objecties for your workloads. The Analysis Parameters menu enables you to select options to edit utilization and synchronous read guidelines, as well as edit paging behaior alues. To access the Analysis Parameters menu, select option 60 (More BEST/1 Options) on the BEST/1 for the AS/400 main menu. On the More BEST/1 Options display select option 11 (Analysis Parameters menu) and the display shown in Figure 72 appears. Note: Any changes the users makes to these objects can be saed using the F15 function key. (Sae analysis parameters). The customized parameters can then be reactiated during future BEST/1 sessions using the F14 function key (Replace with sae analysis parameters). Select one of the following: Analysis Parameters 1. Edit utilization guidelines 2. Edit sync reads guidelines 3. Edit paging behaior alues 4. Edit CISC-to-RISC conersion factors Selection or command ===> F3=Exit F4=Prompt F9=Retriee F12=Cancel F14=Replace with saed analysis parameters F24=More keys Figure 72. Analysis Parameters Menu Note: The More BEST/1 Options menu can also be accessed by pressing F20 from the Work with BEST/1 Model or Configuration menus, or from the Work with Results display. Copyright IBM Corp. 1998,

122 Editing Utilization Guidelines and Thresholds The Edit Utilization Guidelines display enables you to change the resource ealuator alues used to determine configuration changes. Some of the alues you can change on this display are: Max Hardware Util The alues for this field are *GUIDE (Guideline) and *THRESH (Threshold). If you choose *THRESH alues the system will be allowed to become busier than with *GUIDE alues, before upgrades are recommended. Priority for CPU util The maximum CPU priority leel for jobs, which BEST/1 uses during analysis, is defined in this field. CPU upgrade recommendations are based on the jobs with equal or better priority. To change this alue do the following: 1. From the Analysis Parameters menu, select option 1, Edit Utilization Guidelines. This takes you to the display shown in Figure Change the field Priority for CPU util to the alue that you wish to use. In the example shown in Figure 73, a alue of 20 is shown. Any job with a priority oer 30 will not be used for determining CPU upgrade requirements. 3. If you wish to use these alues again, sae them by pressing F15 from the Analysis Parameters menu. Type changes, press Enter. Edit Utilization Guidelines Values are used for Analysis recommendations. Max Hardware Util... *GUIDE *GUIDE, *THRESH Priority for CPU util Guideline Threshold CPUutil Database util Disk IOP util Disk arm util Communications IOP util Communications line util Disk IOA util Comm IOA util Integrated PC Serer IOA util F3=Exit F12=Cancel Bottom Figure 73. Changing Analysis Guidelines If you sae the new guidelines to a member called DEFAULT, BEST/1 will automatically use these customized alues each time you use the STRBEST command. The member must be called DEFAULT and it must reside in your BESTDTALIB library, which you must refer to when you use the STRBEST command. When you start BEST/1 the current library is used, unless you name 102 BEST/1 Capacity Planning Tool V5R1

123 another library with the STRBEST command. If BEST/1 cannot find the analysis parameters member in your current BEST/1 library, it uses the default member from the QPFR library. The changed guidelines can be saed and later reused by pressing F14 (Replace with saed analysis parameters) on the Analysis Parameters menu. Editing Sync Reads Guidelines The Edit Sync Reads Guidelines display, as shown in Figure 74 enables you to change synchronous read guidelines based on CPU relatie performance and architecture. The alues in the CISC column are used when the CPU model being analyzed has a CISC architecture. The alues in the RISC column are used for RISC architecture. Edit Sync Reads Guidelines Type changes, press Enter. Values are used for Analysis recommendations. Check sync reads... Y Y=Yes, N=No Pool 1 (*MACH) CPU relatie performance CISC RISC 2.0 or less Greater than All Other Pools CPU relatie performance CISC RISC 2.0 or less or less or less or less or less or less Greater than F3=Exit F12=Cancel *CISC CPU MODELS USE *GUIDE VALUES, *RISC CPU MODELS USE *THRESH VALUES Bottom Figure 74. Edit Sync Reads Guidelines As page faults rise, performance suffers because jobs hae to wait for more synchronous reads to complete. When the number of synchronous reads exceeds guideline alue for the appropriate architecture type, BEST/1 automatically suggests memory upgrades. Default alues for synchronous reads CISC and RISC guidelines correspond to the alues for page faults in the Work Management book. You can set the guideline alues to appropriate alues for your systems. BEST/1 supports only one set of alues for each architecture, and defaults are set to guidelines alues (as opposed to threshold alues). The complete set of CISC and RISC guidelines and thresholds are shown in the following table: Chapter 7. Modeling Changes to the System 103

124 Pool 1 (*MACH) CISC RISC Guideline Threshold CPU RelPerf Guideline Threshold 2.0 or less More than All Other Pools CISC RISC Guideline Threshold CPU RelPerf Guideline Threshold < < < < < < > Figure 75. CISC and RISC Guidelines and Thresholds Prior to CISC/RISC support, the maximum sync reads fields determined which alue (guideline or threshold) was used to compare against results. Now there is no effectie difference between haing *GUIDE or *THRESH in the maximum sync reads field. This is because the guidelines alues are used if you hae a CISC CPU model and the threshold alues are used if you hae a RISC CPU model. Note: Experiments hae shown that page faults and synchronous reads generally change in the same proportion as the load on memory changes. Howeer, the ratio of the number of synchronous reads per second to the number of page faults per second may not necessarily be one-to-one, and you should take this ratio into account when setting the synchronous reads guidelines and thresholds. For example: If you hae twice as many synchronous reads as page faults, you should use a two to one ratio. For guidelines of 30 page faults per second, set sync reads guidelines to 60. You can disable memory upgrades due to excessie synchronous reads by setting the Max sync reads field to *NONE. For more information on editing sync read guidelines, see Techniques for Achieing Effectie Storage Recommendations on page 139. Editing Paging Behaior Values The Edit Paging Behaior Values display, as shown in Figure 76 on page 105 show the predefined paging behaior alues for specific paging behaiors and enables you to change the paging exponent and working set size alues. 104 BEST/1 Capacity Planning Tool V5R1

125 Type changes, press Enter. Edit Paging Behaior Values Paging -----Paging Exponent----- Working Set Size (MB) Behaior Database Non-Database CISC RISC *GENERIC *OFFICE *RAMPC *SQLRTW F3=Exit F12=Cancel Bottom Figure 76. Edit Paging Behaior Values Note: The RISC alues under the Working Set Size (MB) appears on a PowerPC AS processor. Any change to these alues results in a global change to paging alues so that any transaction that has a paging behaior that is not *USER uses the new alues. You can change the following fields on this display: Paging Exponent The paging exponent is used to determine the effects of changes in memory demands on paging and synchronous read rates. Working Set Size (MB) The working set size of a transaction is the number of pages in the resident set at which the transactions hae an acceptable number of page faults. You can change paging behaior for indiidual transactions on the Edit Transactions or the Change Paging Behaior displays. For more information on paging behaior alues, see Memory Modeling Terminology on page 136. Editing CISC-to-RISC Conersion Factors The Edit CISC-to-RISC Conersion Factors display, as shown in Figure 77 on page 106 shows the predefined CISC-to-RISC conersion factors for specific workload types and enables you to change the factors for CPU serice time, working set size, or I/O counts. Chapter 7. Modeling Changes to the System 105

126 Type changes, press Enter. Edit CISC-to RISC Conersion Factors Workload CPU Working I/O Type Time Set Size Counts *NORMAL *TRNNORM *TRNNORM *TRNNORM *BATCHJOB *TRNBAT *TRNBAT *TRNBAT F3=Exit F12=Cancel Bottom Figure 77. Edit CISC-to-RISC Conersion Factors These alues are used when analyzing a CISC-based workload with a RISC-based configuration, or a RISC-based workload with a CISC-based configuration. The workload type of the workload determines which set of conersion factors are used on the transactions of that workload. Changing this panel has a global effect on all analysis done during the BEST/1 session. You can change the following fields on this display: CPU Time The CPU time conersion factor is used to conert the transaction CPU serice time. For example, if the alue is.5 for CISC-based workload and a RISC-based configuration is being analyzed, then the transaction requires half as much CPU serice time. Working Set Size The working set size conersion factor is used to conert the transaction working set size. For example, if the alue is 2.0 for an CISC-based workload and a RISC-based configuration is being analyzed, then the transaction requires twice as much memory. IO Counts The IO counts conersion factor is used to represent the effect of decreased IO counts, and conerts the transaction IO count. For example, if the alues is 0.75 for an CISC-based workload and a RISC-based configuration is being analyzed, then the transaction calls only 3/4 of the I/Os. The workload type can hae the following possible alues: *NORMAL *TRNNORM1 *TRNNORM2 *TRNNORM3 *BATCHJOB *TRNBAT1 *TRNBAT2 *TRNBAT3 106 BEST/1 Capacity Planning Tool V5R1

127 The first four types represent normal workloads and the second four types represent batch workloads. The difference with each group of four are the different CISC-to-RISC conersion factors which are used during analysis to model the transition between CISC- and RISC-based models. For more information on CISC-to-RISC conersion factors, see Modeling Transitions Between CISC and RISC on page 175. To specify a workload type as *BATCHJOB or *TRNBATx, you should keep in mind the following: Batch jobs are few and long running. A batch job runs throughout the measurement interal. The amount of work done by the batch job will increase if other actiity is reduced or additional resources are added. The amount of work done by the batch job will decrease if other actiity is increased or some resources are remoed from the system. BEST/1 batch workloads must hae the following characteristics: Only one function. One non-interactie transaction that runs at less than 0 priority and running in a pool of only non-interactie transactions. One or more non-interactie transactions running at 0 priority. Note: If the workload does not meet these conditions, the workload type must be specified as *NORMAL or *TRNNORMx. Performance Objecties for Interactie and Non-interactie Actiity Actie jobs are expressed as the number of local, LAN, and WAN jobs that require work to be done. Objecties are expressed in terms of response time, and throughput (transactions per hour), both for interactie and non-interactie work. In BEST/1, a job is considered actie if it does some processing during a fie minute interal. Performance objecties for each workload include the following: Aerage external response time (secs) This is the time taken for the system, including communications delay, to process one transaction. Aerage throughput (transactions per hour) This is the number of transactions that the system is required to process in one hour. Figure 78 on page 108 shows the display for changing workload objecties. If response time or throughput objecties are set to zero, then the model takes this as no restriction. Chapter 7. Modeling Changes to the System 107

128 Specify Objecties and Actie Jobs Model/Text: Type changes, press Enter. Workload Actie ---Interactie---- Non-inter Workload Connect Type Jobs Rsp Time Thruput Thruput WORKLOAD01 *LOCAL *NORMAL WORKLOAD01 *LAN *NORMAL WORKLOAD01 *WAN *NORMAL Bottom F3=Exit F11=Show positie quantities F12=Cancel F15=Sort by connect type F19=Work with Workloads WAN jobs present with no WAN configuration Figure 78. Specify Objecties and Actie Jobs When objecties hae been changed, the model must be analyzed again. If the response time or throughput objecties cannot be satisfied, there will be warning messages on the recommendation display. As a good starting point, leae response time and throughput objecties at zero, and set them after you hae done your first analysis. This will gie you a reasonable indication as to what can be expected with your current workload without placing undue restrictions on the model. You may specify response time or throughput objecties, or both. If you do so, the ealuator considers this information when recommending changes. If you specify response time objecties that are too short, it is possible that BEST/1 will recommend a system configuration that is well below the guideline alues and possibly oer-designed. That is why user-defined response time and throughput objecties are optional, and it is not recommended that they be entered for the initial system analysis. If you hae *BATCHJOB work for which there are minimum throughput requirements, specifying non-interactie throughput is an effectie way to force BEST/1 to make performance decisions which support adequate batch performance. Analyzing the Model When you are satisfied with the changes you hae made to the model, you are ready to analyze the model by selecting from options 5, 6, or 7. Note: You can also analyze the model using the ANZBESTMDL command. The ANZBESTMDL command reads an existing model, performs growth analysis, and saes the results to a results member in a binary and optionally an externally described file (EDF). 108 BEST/1 Capacity Planning Tool V5R1

129 Work with BEST/1 Model Performance data...: Model/Text...: BEST1DATA BEST1MODEL Select one of the following: 1. Work with workloads 2. Specify objecties and actie jobs 5. Analyze current model 6. Analyze current model and gie recommendations 7. Specify workload growth and analyze model 10. Configuration menu 11. Work with results More... Selection or command ===> F3=Exit F4=Prompt F9=Retriee F12=Cancel F15=Sae current model F17=Analyze using ANZBESTMDL F22=Calibrate model F24=More keys Figure 79. Work with BEST/1 Model Display A brief reiew of these options follows: Analyze current model Analyze current model takes the current hardware configuration and workload definitions and analyzes this data. The Work with Results display lets you look at seeral categories of results, such as analysis summary, recommendations, and workload reports. This menu option is only aailable at the adanced user leel. This option is equialent to using Option 7 (Specify workload growth and analyze model) and specifying 1 period to analyze with Determine configuration changes set to N. Analyze current model and gie recommendations Analyze with recommendations uses additional CPU and makes recommendations for new hardware and pool size alues if any guidelines are exceeded or any objecties are not met. Hardware changes identify CPU model and memory size, disk IOP and disk arm quantities, disk feature numbers, communications IOPs, and communications line speeds. This option takes longer to run than option 5. This menu option is only aailable at the adanced user leel. This option is equialent to using Option 7 (Specify workload growth and analyze model) and specifying 1 period to analyze with Determine configuration changes set to Y. Specify workload growth and analyze model You may specify the workload growth rates, number of periods to model, and whether you want BEST/1 to automatically upgrade hardware according to its guidelines/thresholds. The functions accessed from this option are termed manual growth, ersus automatic growth. For more information see Chapter 6. Model Analysis and Calibration. Chapter 7. Modeling Changes to the System 109

130 Modeling Workload Growth This section discusses techniques for modeling projected growth in workloads. The projected growth may be a result of an anticipated increase in transaction olumes oer time or due to a mixture of workloads. The percentage growth can be applied to all workloads or at different rates for each workload, for up to 10 periods. Growth is normally expressed using a compound change for each period. The two ways of growing a workload are: manual and automatic. When BEST/1 attempts to model workload growth, system saturation may occur. If this situation occurs, BEST/1 eliminates work based on transaction priorities. In other words, low priority work will not be done in order to satisfy work requests by higher priority work. This represents the power of BEST/1 in modeling actual OS/400 characteristics. For specific techniques on modeling batch jobs, see Modeling Batch on page 154. Growing a Workload Manually Manual growth support is one of the most powerful functions of BEST/1. BEST/1 lets you specify growth at time periods and growth rates that correspond to a company s unique business cycles. An example of different business cycle growth rates would be summer slow-down and fall and winter peak for skiing equipment. The BEST/1 user can specify an oerall system growth rate or unique growth rates for specific workloads. The procedure to grow a workload is as follows: 1. On the Work with BEST/1 Model display, shown in Figure 80, select option 7 to access the Specify Growth of Workload Actiity display. Work with BEST/1 Model Performance data...: Model/Text...: BEST1DATA BEST1MODEL Select one of the following: 1. Work with workloads 2. Specify objecties and actie jobs 5. Analyze current model 6. Analyze current model and gie recommendations 7. Specify workload growth and analyze model 10. Configuration menu 11. Work with results More... Selection or command ===> 7 F3=Exit F4=Prompt F9=Retriee F12=Cancel F15=Sae current model F17=Analyze with ANZBESTMDL F22=Calibrate model F24=More keys Figure 80. Work with BEST/1 Model 2. The first field in Figure 81 on page 111 tells BEST/1 to do an automatic upgrade to your configuration if your model does not meet specified performance objecties. Specify Y or N depending on your requirement. The default alue for this field is Y (perform an automatic upgrade as necessary). If hardware is 110 BEST/1 Capacity Planning Tool V5R1

131 changed during the growth analysis, you must reiew the recommendations and analysis summary to determine what the changes were. Specify Growth of Workload Actiity Type information, press Enter to analyze model. Determine new configuration... Y Y=Yes, N=No Periods to analyze Period 1... Period 1 Name Period 2... Period 2 Name Period 3... Period 3 Name Period 4... Period 4 Name Period 5... Period 5 Name Percent Change in Workload Actiity Workload Period 1 Period 2 Period 3 Period 4 Period 5 *ALL Bottom F3=Exit F11=Specify growth by workload F12=Cancel F13=Display periods 6 to 10 F17=Analyze using ANZBESTMDL Figure 81. Specify Growth of Workload Actiity 3. The second field defines the number of growth periods. Up to 10 periods can be specified. Type the number of periods for which you want to grow your workload. The default is 5 periods, with period 1 representing the current workload. Use function key F13 to work with periods 6 to 10. Growth rate is compounded. If 10% growth in a certain period is specified, the throughput will be increased by 10% oer that of the preious period. 4. The default period name is Period n where n represents the period number. You can oerride these names by using your own names. You could use a meaningful name in the period field to indicate the time span represented or the name of the month, such as MARCH. 5. The user is responsible for assigning a business cycle meaning for each period. A period can be any amount of time defined purely by the growth factor, and how the period is named. It is possible to define a one month, three month, one year, and three-year outlook, all for one set of periods. 6. BEST/1 defaults to: The first fie periods. All periods are grown by 20% compound (except the first period which is deemed to be the current period). All workloads are grown equally by the specified period growth. 7. To specify growth by workload use function key F11. This allows different growth percentages to be specified by workload for each period. 8. Type the growth percentages for the required periods. When you hae finished press the Enter key and the model will be reanalyzed. 9. On the display shown in Figure 82, select option 5 to reiew the results of the report of your choice. Chapter 7. Modeling Changes to the System 111

132 Printed report text... Work with Results Type options, press Enter. 5=Display 6=Print Opt _ Report Name Measured and predicted comparison Analysis Summary Recommendations Workload Report ASP and Disk Arm Report Disk Resources Report Main Storage Pool Report Communications Resource Report All of the aboe Bottom F3=Exit F12=Cancel F14=Select saed results F15=Sae current results F18=Graph current results F19=Append saed results F24=More keys Model has been analyzed Figure 82. Work with Results Sae the current results with function key F15, if you think you are going to need the results in some form. This could sae haing to reanalyze the model later. Specifying Growth for a Single Workload If you are interested in one period of growth you may feel more comfortable growing the number of jobs or increasing the throughput for a particular workload. You can do so by changing your workload s objecties by choosing option 2 (Specify Objecties and Actie Jobs) as shown in Figure 83 on page 113 from the Work with BEST/1 Model menu. This menu option is only aailable at the adanced user leel. 112 BEST/1 Capacity Planning Tool V5R1

133 Model/Text: BEST1MODEL Type changes, press Enter. Specify Objecties and Actie Jobs Workload Actie ----Interactie---- Non-inter Workload Connect Type Jobs Rsp Time Thruput Thruput WORKLOAD01 *LOCAL *NORMAL WORKLOAD01 *LAN *NORMAL WORKLOAD01 *WAN *NORMAL Bottom F3=Exit F11=Show all quantities F12=Cancel F15=Sort by connect type F19=Work with Workloads Figure 83. Display New Objecties After you hae changed the objecties you hae to reanalyze the model. If you use option 6 (Analyze current model and gie recommendations) then, at this point, you might choose to change the recommended configuration and reanalyze using function key F10 (Re-analyze) from the Display Analysis Summary display. Pressing F10 from this display changes the CPU to a and reanalyzes the model. **** Analysis Exceptions ***** CPU is saturated ***** Analysis Recommendations ***** Change CPU model to Display Recommendations Bottom Performance estimates -- Press help to see disclaimer. F3=Exit F10=Change to recommended configuration and re-analyze F12=Cancel F15=Configuration menu F17=Analyze multiple points F24=More keys Figure 84. Display Recommendations Display Chapter 7. Modeling Changes to the System 113

134 Growing a Workload Automatically Performing a single analysis using option 5 or 6, as seen in Figure 85, produces only one set of performance alues. This does not allow you to do any trend analysis. A table of alues can be generated using the automatic growth option. The sequence of ten workload growth factors is predefined. If you want to define the factors yourself or use a different number, see Growing a Workload Manually on page 110. When resource constraints begin to show up, you hae to carefully analyze some results that seem to contradict your common sense. You must remember that BEST/1 uses weighted aerages of priorities sometimes resulting in non-interactie jobs with higher priority than interactie jobs. In a CPU constrained system this might lead to decreased interactie throughput at higher CPU utilizations. Use the following steps as a guide: 1. Analyze the model using either option 5 or 6 as shown in the display in Figure 85. Work with BEST/1 Model Performance data...: Model/Text...: BEST1MODEL Select one of the following: 1. Work with workloads 2. Specify objecties 5. Analyze current model 6. Analyze current model and gie recommendations 7. Specify workload growth and analyze model 10. Configuration menu 11. Work with results More... Selection or command ===> 6 F3=Exit F4=Prompt F9=Retriee F12=Cancel F15=Sae current model F17=Analyze with ANZBESTMDL F22=Calibrate model F24=More keys Figure 85. Work with BEST/1 Model Display 2. From the display shown in Figure 86, select option 5 to display the analysis summary. 114 BEST/1 Capacity Planning Tool V5R1

135 Printed report text... Work with Results Type options, press Enter. 5=Display 6=Print Opt Report Name _ Measured and predicted comparison 5 Analysis Summary _ Recommendations _ Workload Report _ ASP and Disk Arm Report _ Disk Resources Report _ Main Storage Pool Report _ All of the aboe Bottom F3=Exit F12=Cancel F14=Select saed results F15=Sae current results F18=Graph current results F19=Append saed results F24=More keys Model has been analyzed Figure 86. Work with Results 3. From the display shown in Figure 87 use function key F17 to analyze multiple points. Display Analysis Summary CPU Model / release leel...: V4R1M0 Actie Processors...: 4 Main Storage...: MB Quantity Predicted Util CPU...: Disk IOPs...: Disk ctls...: Disk arms...: Local WS ctls...: 1.4 Interactie Non-interactie CPU utilization %...: Transactions per Hour...: Local response time (seconds)...: LAN response time (seconds)...:.0.0 WAN response time (seconds)...:.0.0 Bottom Performance estimates -- Press help to see disclaimer. F3=Exit F10=Re-analyze F11=Measured and predicted comparison F12=Cancel F15=Configuration menu F17=Analyze multiple points F24=More keys Figure 87. Display Analysis Summary BEST/1 does a ten-point growth analysis with no new configuration, and with the following growth percentages: 50%, 75%, 100%, 125%,...275%, as compared to baseline. The Specify Growth of Workload Actiity display does not use growth alues compared to baseline, but the alues are cumulatie from period to period. The growth percentages used are equialent linear growth factors. The current alue is always be the third period in the table. Chapter 7. Modeling Changes to the System 115

136 Note: Using F17 (Analyze multiple points), uses considerable CPU resources, and may seerely affect other interactie users. Figure 88 shows a table that was generated using the multiple point analysis option (F17 on the Display Analysis Summary display). Display Analysis Summary Stor CPU -Disk IOPs-- -Disk Ctls-- -Disk Arms-- Period CPU Model (MB) Util Nbr Util Nbr Util Nbr Util Period Period Period Non-Inter Rsp Time Non-Inter Release *Actie Period Local LAN WAN CPU Util Trans/Hr Leel Procs Period V5R1M0 4 Period V5R1M0 4 Period V5R1M0 4 Period V5R1M0 4 Period V5R1M0 8 Bottom F3=Exit F10=Re-analyze F11=Alternatie iew F12=Cancel F15=Configuration menu F17=Analyze multiple points F24=More keys Figure 88. Display Analysis Display for Multiple Points By paging this display, you can see resource restrictions are shown in periods 8 and 9. Additional information about these restrictions is shown on the recommendation report. Notice that the interactie throughput drops off in period 9, while non-interactie continues to grow. This situation is a direct result of transaction priorities. When guidelines and thresholds hae been exceeded, and system resources are near or at saturation, use the results at these throughputs cautiously, because they may be inaccurate (for example, not representatie of how one actual system behaes under the same stress). Detailed analysis of the Workload Report would show high priority non-interactie work being done, and lower priority interactie work being reduced. From this display it is possible to use arious function keys to go to indiidual displays where you can change the configuration, workloads, and objecties. Then you can use F10 to reanalyze the model. Changing Functions and Transactions An issue to consider if you are adding users to your system is are they all the same type of users and are they all doing the same type of work? If you are doubling the amount of users, but they will use the system differently, then simply doubling your workload is not enough. You should change functions and transactions associated with that workload. Use the Change Function display if a function requires more transactions. You can access the Change Function display by pressing F6 (Work with functions) on the Change Workload display. The Work with Functions display appears. Type a BEST/1 Capacity Planning Tool V5R1

137 (Change) in Opt field next to the function you want to change, and the Change Function display appears. Change Function Workload...: QDEFAULT Summary query Function...: QDEFAULT Change fields, press Enter. Function text... Summary query Key/Think time....0 Seconds Additional delays....0 Seconds Transaction Pool Transactions CPU Time Total Type ID Priority per Function (Secs) I/Os Transaction Type: 1=Interactie, 2=Non-interactie Bottom F3=Exit F6=Work with transactions F12=Cancel Figure 89. Change Function Display If you change the usage mode, you will notice that the key/think time and the number of functions per user per hour will be scaled depending on the existing usage mode and the new usage mode. You can access the Change Transaction display by pressing F6 on the Change Function display. The Work with Transactions display appears. Type a 2 (Change) in the Opt field and the Change Transaction display appears. Chapter 7. Modeling Changes to the System 117

138 Change Transaction Workload...: QDEFAULT Measured from QPFRDATA (Q ) Function...: QDEFAULT Function of QDEFAULT Type choices, press Enter. Transaction Type =Inter, 2=Non Pool ID... 3 F4forlist CPU Priority CPUtime Secs (on B10) Permanent writes percent Chars transferred in Chars transferred out Exceptional wait....0 sec Paging behaior... *GENERIC F4 for list Application Type... *DEFAULT F4 for list DB Reads DB Writes NDB Reads NDB Writes Sync I/Os Async I/Os F3=Exit F4=Prompt F6=Calculate B10 CPU time F12=Cancel F13=Change paging behaior Figure 90. Change Transaction Display Changes you might make to transactions include the following: Redistribute memory by assigning transactions to run in different pools Change the I/O characteristics for each transaction. The fields on the Change Transaction display are discussed in detail in Transaction Definition on page 26. To iew and edit all transaction attributes in a workload, use the Edit Transactions display. From the Work with Workloads display select option 9 (Edit transactions) and the display shown in Figure 91 appears. 118 BEST/1 Capacity Planning Tool V5R1

139 Edit Transactions Workload...: QDEFAULT Measured from ACCOUNTING Workload type..: *NORMAL CPU architecture : *RISC Type changes, press Enter. Trans Pool Transactions CPU Time DB Time Function Type ID Priority per Function (Secs) (Secs) QDEFAULT QDEFAULT QDEFAULT Trans Type: 1=Interactie, 2=Non-interactie Bottom F3=Exit F11=Alternatie iew F12=Cancel F14=Read I/Os F15=Write I/Os F16=Paging alues F17=Application types F18=Chars transferred Figure 91. Edit Transactions Display Changing System Resources You can use the function keys on this display to iew and edit seeral attributes of the transactions, including paging behaiors, characters transferred, and read and write I/Os. This section discusses techniques to change CPU and other system resources and some of the effects these changes might hae on your model. Automatic Hardware Changes with Manual Growth Figure 92 on page 120 shows an example of the output that results when you explicitly specify growth rates manually and allow BEST/1 to automatically change hardware when resource utilizations exceed guidelines. Each time a hardware upgrade is made, the response time will improe (be lowered). As the workload rate grows response time again is raised until another hardware upgrade is made. In this example 10 periods of growth were used with growth rates of 100% for period 1 and 10% growth for each period 2 through 10. CPU model upgrades were made at period 1 (MERGEBAS) because of 100% growth and at period 5 (Q4) and at period 8 (Q7 - not shown). Displaying the results of the growth shows hardware changes and other details, such as interactie and non-interactie transactions per hour. Hardware upgrades are highlighted. Chapter 7. Modeling Changes to the System 119

140 Display Analysis Summary CPU Stor CPU -Disk IOPs-- -Disk Ctls-- -Disk Arms-- Period Model (MB) Util Nbr Util Nbr Util Nbr Util MERGEBAS E Q1 E Q2 E Q3 E Q4 E Q5 E Q6 E More Inter Non-Inter Inter Rsp Time-- CPU CPU Period Local WAN Util Trans/Hr Util Trans/Hr MERGEBAS Q Q Q Q More... F3=Exit F10=Re-analyze F11=Alternatie iew F12=Cancel F15=Configuration menu F17=Analyze multiple points F24=More keys Figure 92. Manual Growth - Display Results of Automatic Hardware Upgrade Note: The Display Analysis Summary display proides a picture of the performance results and most hardware changes. From this results display, you can go to other displays to make configuration changes, and then return to this display. To see the results of these additional hardware changes, you must reanalyze with F10. Figure 93 is a graphic example that dramatically shows the effect of hardware changes to interactie response time for each interactie workload name while continuing to increase interactie throughput (transactions per hour). 120 BEST/1 Capacity Planning Tool V5R1

141 Figure 93. Manual Growth - Graph of Automatic Hardware Upgrade Figure 93 shows the workloads with interactie transactions (S36BAS, PCBAS, INTBAS) as lines aboe the X-axis. Response time decreases due to configuration changes. Changing CPU and Other Resource Values This display enables you to change the OS/400 system type (9402, 9404, 9406), the OS/400 model number, the main storage for the current model, and the release leel. The CPU model, the main memory, and release leel selections can be prompted by pressing F4 (Prompt). If you change the alue of one resource you may hae to make other changes as well. For example, if you change the CPU type, it may force additional memory which requires changes to the pool sizes, disk types, and so on. BEST/1 displays messages to indicate changes that need to be made, and proides other methods to alidate the configuration. You can change the number of local and WAN workstation controllers, and LAN controllers, on the display shown in Figure 94. Chapter 7. Modeling Changes to the System 121

142 Change CPU and Other Resource Values Model/Text: BEST1MODEL Sample BEST/1 Model Type choices, press Enter. M System unit , 9404, 9406 CPU odel... 2D6C F4 for list System storage (MB) F4 for list Release leel... V4R5M0 F4 for list Actie processors... 8 Unaailable PCI slots... 0 F3=Exit F4=Prompt F9=Specify other logical partitions F12=Cancel BEST/1 CPU model 740 2D6C refers to IBMCPU model Figure 94. Change CPU and Other Resource Values BEST/1 makes the following assumptions: Workstations are eenly distributed across all controllers within a group (local, LAN, or WAN). WAN workstation controllers and LAN controllers are equally distributed across the aailable WAN and LAN lines. All local workstation controllers hae the same serice times, as do all LAN controllers and WAN workstation controllers. Selecting a CPU Figure 95 on page 123 shows the display for the selection of a new CPU model. Other useful information is presented as well, including relatie performance and main storage maximum. If the CPU that you wish to select is not in the Select CPU list, press F12 to return to the Configuration menu. Press F20 (More BEST/1 Options). Select option 10, Hardware Characteristics. This will display the Hardware Characteristics menu. Press F16 (Add Saed Hardware Characteristics). This will display the aailable hardware tables. Selecting one of these tables will add CPU models to the current list. BEST/1 assigns CPU power to specific models using the Relatie Internal Processor Performance rating as measured by IBM. In some cases, the rating for a specific CPU model or feature will differ from other published reports which quote the Relatie Performance of the system based on a specific benchmark. Note: The performance of RISC-based CPU models is now published by IBM using the CPW rating. BEST/1 continues to use the Relatie Internal Processor Performance rating. The Serer Relatie Performance field on the Select CPU display shows the relatie speed of the system when processing serer work. For a BEST/1 model, serer work is considered to be all non-interactie transactions in the workloads being analyzed. BEST/1 recognizes that these non-interactie transactions (Type 2) 122 BEST/1 Capacity Planning Tool V5R1

143 should be considered at the faster speed during analysis. The alue shown in the field is relatie to the speed of the B10. The relatie internal performance figures are reported to two decimal places. When rounded to one decimal place they agree with the published figures. Type option, press Enter. 1=Select Select CPU Archi Relatie Performance Number of Max Opt CPU Model tecture Interact Database Processor Processors Stor B10 *CISC *CISC *CISC *CISC A6A *RISC A6B *RISC A6C *RISC A6D *RISC A6E *RISC A6F *RISC B6A *RISC B6B *RISC B6C *RISC More... F11=Show CPU models which support partitioning F12=Cancel Figure 95. CPU Selection If your current CPU cannot support more than one logical partition and if your actie processors are more than the total, then all CPU models are included in the list. Howeer, if your current CPU can support more than one logical partition and if your actie processors are less than the total, you see only CPU models that can support logical partitioning in the list. Selecting Main Storage Size You can access Figure 96 on page 124 from the Change CPU and Other Resource Values display. Press F4 (Prompt) on the Main storage field. Chapter 7. Modeling Changes to the System 123

144 Select Storage Size for CPU Model CPUModel...: 2144 System Unit...: 9406 Type option, press Enter. 1=Select Opt Size (MB) Opt Size (MB) Opt Size (MB) _ 256 _ 320 _ 384 _ 512 _ 576 _ 640 _ 768 _ 1024 F12=Cancel Selecting Release Leel Figure 96. Selecting Main Storage Size A list of alid memory sizes is presented for selection, depending upon the current CPU model. You can access the display shown in Figure 97 from the Change CPU and Other Resource Values display. Press F4 (Prompt) on the Release leel field. CPU Model...: 2152 Select Release Leel Type option, press Enter. Some CPU models hae performance improements depending on which release leel is run. 1=Select Opt Release Performance _ Leel Improement Pct _ V3R6M0 0 _ V3R7M0 20 F12=Cancel Figure 97. Selecting Release Leel A list of alid release leels is presented for selection, depending on the current CPU model. 124 BEST/1 Capacity Planning Tool V5R1

145 Changing Disk Resources Disk resources are diided into the following types: Input/output processor (IOP) Input/output adapter (IOA) Disk controller Disk arms Use F6 to create a new IOP. If the current CPU connects to multifunction IOPs, which in turn can connect disk IOAs, then you see the Create Multifunction IOP display. This display allows you to specify: IOP name, feature, and serice time Disk IOA feature Number of disk arms, drie feature, ASP, serice time, and blocks transferred If the current CPU does not connect to multifunction IOPs, which in turn can connect disk IOAs, then you see the Create IOP display. You can specify on this display all of the preious information except disk IOA feature. Use the Create IOP display to specify either disk IOPs or multifunction IOPs that do not support disk IOAs. Disk IOAs can hae arms with different drie features under them; disk controllers must hae arms with the same drie feature as the controller feature. Add more disk arms to an IOP, an IOA, or a controller by selecting option 3 (Copy) or option 8 (Create disk arms). Resource names are initially set to those used in the Work with Hardware Products (WRKHDWPRD) resource tables, but you can call your IOP any name you choose. Disk arm names are assigned by the system, but can also be renamed. For high aailability only: If the name of a disk arm begins with an underscore (_), this indicates that this arm contains RAID-5 parity data. When a model is created from performance data, BEST/1 will add the underscore for any arm which contains parity data. If you are renaming a disk arm, BEST/1 interprets the presence of an underscore (_) at the beginning of the disk name as indicating that the arm contains RAID-5 parity data. Therefore, to change an arm from haing it to not haing it, you would remoe the underscore. If you want to model the arm as haing parity data, you would add an underscore. BEST/1 checks whether any arms can hae RAID-5 parity data. BEST/1 also checks for a alid number of arms with RAID-5 parity data on each array. By using option 2 (Change) or option 8 (Create disk arms), disk arms can be associated with a specific ASP. Chapter 7. Modeling Changes to the System 125

146 Work with Disk Resources Model/Text: BEST1MODEL Sample BEST/1 model Position to... IOP name, *TOP, *BOT Type options, press Enter. 2=Change 3=Copy 4=Delete 7=Rename 8=Create disk arms RAID Serice Time Opt Resource Feature Type ASP Array (Msecs per IO) _ CMB *MFIOP.9 _ DI *IOA 1.7 DD *ARM DD *ARM DD *ARM DD *ARM _ SI *IOP 1.4 _ ARRAY *CTL DD *ARM DD *ARM More... F3=Exit F4=Prompt F6=Create IOP F9=Select resources to change features F12=Cancel Figure 98. Working with Disk Resources The column Serice Time is deried from performance data and is application dependent. It is not merely the hardware serice time. It has an extra component that is deried from the actual application that is being run. For different applications, expect to see different serice times. The disk arm serice times should match the Performance Tools System Report, under the heading Aerage Time per I/O and Serice column. Disk IOP serice times should equal the alues shown in the Wait column. Note: When adding more IOPs, disk IOAs, or disk arms,if the copy function is used, the serice times are similar to current model alues. These are probably good alues to use. Howeer, if new hardware is added using the create functions and the defaults are taken, then the predefined serice times will be used (which usually are significantly different (lower) than those obtained using measured data). Wheneer possible, conert existing deices (or copies of existing deices) to new deice types so that BEST/1 can estimate the new disk serice time for you. The serice times can be manually entered with the sequence of Work with Disk Resources and Change Disk Resource displays. If an ASP in your actual system has increased its number of arms, you might consider a full sae and reload before measuring your workload. In this case you would get improed arm usage and minimized data fragmentation with faster and more consistent seek times. You can change the following by using F9 (Select resources to change features): Many IOPs to a single IOP feature Many disk IOAs to a single IOA feature Many controllers (with attached arms) to a single drie type. 126 BEST/1 Capacity Planning Tool V5R1

147 Select Resources to Change Features New IOP feature... F4forlist New IOA feature... F4forlist New ctl feature... F4forlist NewASP... *SAME *SAME, 1-99 Type options, press Enter. 1=Select Resource Opt Resource Feature Type Arms ASP CMB *MFIOP 7 DI *IOA 4 1 SI *IOP 16 ARRAY *CTL 10 1 More... ASP: ** = mixed F3=Exit F4=Prompt F12=Cancel Figure 99. Select Resources to Change Features For more information about BEST/1 hardware names, see Appendix H. BEST/1 Hardware Name Mapping on page 313. Changing ASP Disk Protection Figure 100 shows the display for changing the data protection mode of an Auxiliary Storage Pool (ASP). The protection leel of each ASP can be separately defined as *NONE, *MIRROR, or *CHECKSUM. Model/Text: INS Type changes, press Enter. Edit ASPs Number of Data Compression Utilization ASP Disk Arms Drie Feature Protection Actie Guideline 1 65 ** *MIRROR N *STD 10 6 ** *NONE Y *STD *NONE N *STD 2 6 ** *MIRROR N *STD 3 4 ** *NONE N *STD 4 6 ** *MIRROR N *STD Drie Feature: ** = mixed Data Protection: *NONE, *MIRROR, *CHECKSUM Compression Actie: Y=Yes, N=No Utilization Guideline: 1-100, *STD=from Edit Utilization Guidelines F3=Exit F12=Cancel F14=Work with disk resources Bottom Figure 100. Changing ASP Data Protection Chapter 7. Modeling Changes to the System 127

148 For High Aailability Disk Models (such as or ), the ASP cannot use data protection type *CHECKSUM. This is because the iseries serer does not proide a second leel of checksum. Howeer, the disk subsystem has internal checksum protection. The default serice times for High Aailability Disks Models and the Base Models are different. The serice time for High Aailability Models depends on the proportion of write operations, but BEST/1 accounts for the additional disk writes when using *CHECKSUM and *MIRROR. Changing Main Storage Pools Note: It is possible to mix high aailability dries in an ASP with *MIRROR, so the drie feature may show ** with *MIRROR, when high aailability dries are present. BEST/1 models all I/Os properly. Figure 101 shows the display to edit pool data. Each pool is modeled indiidually. Changing the pool sizes and actiity leels can hae a significant effect on the resources used by different workloads. Pools can be created using function key F6. Edit Main Storage Pools Model/Text: BEST1MODEL Sample BEST/1 model Main storage size...: 80 M B KB Type changes, press Enter. To delete a pool, set size to *NOSTG. Actiity Size Pool ID Pool Name Leel (KB) F3=Exit F6=Create F12=Cancel F17=Re-scale pool sizes Bottom Figure 101. Changing Main Storage Pools If main storage (in total) is increased or decreased, and the total system storage size does not equal the sum of the pools, you can scale up or down in the same proportion as the pools appear on the display. This is accomplished by pressing function key F17 (Re-scale pool sizes). Note: BEST/1 enforces the minimum RISC machine pool requirement of 16 MB (regardless of total system mainstore memory size) at all times, including CISC-to-RISC upgrades. In extreme cases, as discussed below, this will cause excess memory to be recommended during a growth analysis because BEST/1 preseres the ratio of the machine pool to total mainstore memory as the other pools are increased in size due to workload growth. 128 BEST/1 Capacity Planning Tool V5R1

149 Scaling of all pool sizes may not always be appropriate, since one of the reasons for adding additional main storage may be to increase a specific memory pool (for example, for interactie jobs). Therefore, when adding or remoing memory from the system, add or subtract memory from indiidual pools in roughly estimated appropriate amounts. Then if the pools do not add up to the total size of main storage, you can still use F17 to let the system calculate the exact amount of storage needed to add up, but respecting the selected proportions. Because the BEST/1 analysis process may recommend more memory than you actually need, when modeling pool actiity leels and pool sizes, it is necessary to adjust actiity leels in system hardware configurations supplied with BEST/1. This would minimize the number of change pool size and change actiity leel recommendations following a model analysis. See Techniques for Achieing Effectie Storage Recommendations on page 139 for additional information. Adjusting Actiity Leels When increasing the amount of main storage, it is also adisable to adjust the actiity leels. This is not done automatically when the re-scale option (function key F17) is used. In the OS/400 actiity leels restrict the number of jobs that can run concurrently in a memory pool. If you hae increased the main storage in the pool, and increased the number of jobs in the workload, but the actiity leel is still set low, then the results that you obtain may be inaccurate. You can type a alue of 0 into the actiity leel field, een though this is not possible on the actual iseries serer. This special alue means there is no limitation to the number of jobs running in that pool. This may be an erroneous assumption and may not reflect your enironment properly, leading you to wrong conclusions. For pool 1, the machine pool, setting the actiity leel to 0 has no effect. Howeer, zero in any other storage pool has a significant effect on subsequent modeling results. BEST/1 does not recommend changes to actiity leels except when the pool is so small that BEST/1 recommends it is set to 1. Carefully adjust the size of the machine pool (pool 1). If it is made too small, excess paging may occur. In reality, there is always a minimum size for the machine pool. This alue is shown on the display when using the Work with System Status (WRKSYSSTS) command, under the column heading Resered. BEST/1 will not allow the machine pool to be less than one-tenth of total main storage. When using measured data you should be aware that for modeling purposes BEST/1 uses aerage storage pool sizes and actiity leels. If significant changes to pool sizes or actiity leels occurred during the selected period, the whole memory model may not reflect the ongoing actiity. You should also consider setting system alue QPFRADJ to 0 and deactiating automatic memory tuners while measuring for modeling purposes to keep memory size stable during data collection. Changing Communications Resources This display shows all the communications IOPs and line resources in the current configuration for both LANs and WANs. Use this display to change the capacity of communications lines, either by changing line speeds, number of lines, or creating new line resources. Chapter 7. Modeling Changes to the System 129

150 Work with Communications Resources 2=Change 3=Copy 4=Delete 7=Rename 8=Create line resources Nbr of Line Speed Pct Line Opt Resource Feature Lines Type (Kbit/sec) Oerhead CC *IOP LANLINE1 1 *LINE CC *IOP WANLINE2 6 *LINE CMB *MFIOP LIN *IPCS D27DBF0101 *LINE LIN *IOA CMN08 *LINE LIN *IOA QESLINE 1 *LINE F3=Exit F6=Create IOP F12=Cancel Bottom Figure 102. Changing Communications Resources Multifunction IOPs appear on this display when they are capable of supporting communications actiity. They also appear on the Work with Disk Resources display when they are capable of supporting disk actiity. Not all multifunction IOPs can support disk actiity, especially some of the new features that connect to communications IOAs. Note: BEST/1 uses a fictitious LAN IOP called the 613L to represent a 6130 with LAN communications lines. The 6130 can support either WAN or LAN communications lines, but earlier ersions of BEST/1 required any communications IOP in the hardware table to be exclusiely WAN or LAN. The hardware table includes a 6130, which supports WAN line speeds, and a 613L which supports LAN line speeds. Understanding Recommendations BEST/1 determines the communications IOP type by whether the minimum line speed supported by a IOP is less than 4 MB. An IOP type with a minimum line speed of 4 MB or greater is considered LAN. An IOP type with a minimum line speed of less than 4 MB is considered WAN. When you create a model from performance data, the lines speed for the lines attached to a 6130 determine whether it is listed as a 6130 or 613L. If you choose to analyze the model and gie recommendations, you will get recommendations for configuration changes based on the alues used for resource utilization limits, as well as alues entered for performance objecties. Some of the recommended changes might be changing CPUs, creating, changing, or deleting disk resources or IOPs. If you are analyzing multiple periods, changes and recommendations are indicated separately for each period. Figure 103 on page 131 is a sample display of recommendations. 130 BEST/1 Capacity Planning Tool V5R1

151 Display Recommendations ***** Analysis Exceptions ***** Utilization of for communications IOP CC03 exceeds objectie of Utilization of for communications IOP CC05 exceeds objectie of ***** Analysis Recommendations ***** Moe 3 Communication lines from IOP CC03 to CIOP1 Moe 4 Communication lines from IOP CC05 to CIOP2 Create communications IOP(s) Moe 1 Communication lines from IOP CC03 to CC01 Moe 1 Communication lines from IOP CC05 to CC04 Bottom Performance estimates -- Press help to see disclaimer. F3=Exit F10=Change to recommended configuration and re-analyze F12=Cancel F15=Configuration menu F17=Analyze multiple points F24=More keys Figure 103. Display Recommendations This report contains two types of information: exceptions and recommendations. Exceptions are conditions which BEST/1 has identified as indicators of poor performance according to the objecties or guidelines. Recommendations are suggested configuration changes from BEST/1 that will cause the desired performance to be achieed. Exceptions There are fie basic types of exceptions: 1. utilization of... exceeds objectie... The predicted utilization of the identified hardware component has exceeded the guideline for that type of component, according to the analysis guidelines in effect is saturated The predicted utilization of the identified hardware component has exceeded 100%. This usually indicates a seere oercommitment of the hardware resource. Additionally this condition indicates that some of the work presented to the system to process was not able to be processed, and the predicted throughputs will be less than the requested throughputs. 3. sync reads per second exceeded The predicted sync reads rate has exceeded the guideline for that pool or pool group according to the sync read guidelines in effect. Sync reads exceptions indicate a memory contention problem because they are related to page faults. Note: The machine pool is treated separately from all other pools. All non-machine pools are treated as one group. 4. response time for workload exceeds objectie The predicted response time for the workload has exceeded the user-specified objectie. Chapter 7. Modeling Changes to the System 131

152 5. workload throughput is less than objectie The predicted transactions throughput for the workload has not met the user-specified objectie. Suggestions for Handling Exceptions The following are suggestions for handling exceptions: Hae BEST/1 recommend a configuration that eliminates exceptions. Reduce load objecties or increase response time objecties. Manually change resources, pool sizes, transaction assignments to pools, transaction priorities, data protection for pools, and so on. Reiew or edit guidelines if they are not appropriate for the performance study you are performing. See the How Utilizations are Predicted on page 133 for information on how BEST/1 predicts utilizations for arious hardware components. Refer to Memory Modeling on page 135 for specific suggestions on how to understand and change sync read guidelines. Reiew the Specify Objecties and Actie Jobs display to see if the specified response time and throughput objecties are realistic. These objecties are specified in terms of total transaction throughput per hour for the entire workload. Recommendations Any time recommendations hae been requested using option 6 (Analyze current model and gie recommendations) or option 7 (Specify workload growth and analyze model), and one or more exceptions hae occurred, BEST/1 makes specific reconfiguration suggestions. These suggestions hae one of two possible origins: Primary. The reconfiguration is specifically indicated in order to alleiate one or more performance exceptions. Secondary. Additional reconfiguration is required by OS/400 configuration requirements. For example, if the CPU utilization guideline is exceeded, BEST/1 will most likely recommend installation of a new CPU. If that CPU has different IOP requirements than the CPU originally being analyzed, BEST/1 also details the necessary new IOPs. In another situation, BEST/1 identifies that the sync reads guidelines hae been exceeded and recommends that additional main storage be acquired. If that amount of storage cannot be configured on the CPU originally being analyzed, a new CPU will be recommended as well. BEST/1 also tries combinations of reconfiguration elements if a single upgrade will not satisfy the performance objectie. For example, if proiding the maximum allowed memory on the current CPU does not result in an elimination of the synchronous reads exception, BEST/1 recommends a CPU upgrade so that more memory can be added to the system. If BEST/1 cannot find a combination that works, it will output the special recommendation Unable to find configuration that met all specified objecties. Note: Sometimes BEST/1 recommends memory upgrades prematurely, or recommends a large amount of memory, which in turn may necessitate a CPU upgrade. This typically happens because the sync reads guidelines and thresholds are too conseratie. In this situation, you should examine the sync reads guidelines and threshold alues to ensure that they are appropriate for your system. For more information, see Editing Sync Reads Guidelines on page 103 and Memory Modeling on page BEST/1 Capacity Planning Tool V5R1

153 It is possible that your system can sustain more synchronous reads per second without appreciably deteriorating response times or perceied serice leels. If this is true, change sync reads guideline and threshold alues on the Edit Sync Reads Guidelines display, to hopefully aoid a CPU upgrade. BEST/1 only recommends hardware reconfigurations that are both: Adequately/completely defined in the hardware table Marked as currently aailable (Y) You may often hae access to hardware that is either out-of-date, that is, IBM does not currently sell it, or aailable from a third party endor. In these cases, you should modify the hardware table to reflect the actual configuration options (see Adding a Newly Announced CPU to the Hardware Characteristics File on page 218 for an example of how to edit the hardware table). An exception to this rule is when no components of the type needed are currently aailable. How Utilizations are Predicted When BEST/1 predicts hardware utilizations, it considers many parameters in the model. The most important elements are identified below for each type of hardware resource. CPU CPU use is determined by BEST/1 for each workload by using workloads, actie jobs, functions per user, transactions per function, and transaction CPU time. These are added across all workloads. Additionally, when the architecture of the CPU and the architecture of one or more workloads differ, BEST/1 applies the CISC-to-RISC conersion factors to the transaction CPU times for the appropriate workloads. See Modeling Transitions Between CISC and RISC on page 175 for more information. BEST/1 also applies the performance improement percentage based on the CPU model and release leel in the configuration. See Modeling Release Leel Performance Improements on page 178 for more information. Additionally, BEST/1 accounts for CPU use depending on any increase in I/Os, including increase in I/Os due to mirroring, system checksum, and page faults. All of these items are considered by BEST/1 to determine utilization per processor. Only the CPU utilization for workloads (or portions of workloads) executing at or aboe the specified priority guideline is considered when generating a CPU utilization exception. Disk Arms Disk use is determined by BEST/1 for each workload by using actie jobs, functions per user, transactions per function per hour, and I/Os per transaction. I/Os per transaction is the total of all I/Os: synchronous, asynchronous, DB and non-db. These are kept separately for each ASP, and are added across all workloads. Additionally, BEST/1 accounts for I/O use depending on increase in I/O due to: RAID-5 technique (use of HA dries) ASP mirroring Chapter 7. Modeling Changes to the System 133

154 ASP checksum Predicted synchronous reads All of these are added together to produce total I/Os for each ASP. Within each ASP, the total I/Os for that ASP are assumed to be eenly spread across all arms. Utilization for each is determined by I/Os per arm and disk serice times per arm per I/O. The disk serice time per I/O is specific to each arm (see these alues on the Work with Disk Resources display). IOP and Disk IOA IOP and disk IOA disk utilization are determined by BEST/1 using the I/Os per arm, and the IOP or disk IOA serice time per I/O. IOP or disk IOA serice time per I/O is specific to each IOP or each disk IOA. See these alues on the Work with Disk Resources display. Utilization for each IOP or disk IOA is determined by adding the IOP or IOA use of all arms attached to it. Communications Use of communication resources, such as controllers, IOPs and IOAs, for each workload is determined by BEST/1 using total number of characters transferred, using functions per user, transactions per function, and characters per transaction. The actie jobs in the workload for each group (local, LAN, and WAN) indicate which type of communications resource will process these characters. Characters per transaction is the total of all characters transferred in and out. When communications lines are present, the number of characters is kept separately for each line. These are added across all workloads. Local and WAN Workstation Controllers, and LAN Controllers: Utilization of local workstation controllers is determined by BEST/1 using total workload characters, local actie jobs, and the number and serice time of local workstation controllers. Local workstation controller serice time is an aerage across all local workstations (see this alue on the Change CPU and Other Resource Values display). Utilization for LAN and WAN controllers is determined similarly using LAN and WAN actie jobs. This method is based on the assumption that an aerage serice time is representatie and that the traffic is eenly spread among all controllers of a particular type. LAN and WAN IOPs and Communications IOAs: Use of LAN IOPs is determined by attached communications lines. Each line s contribution depends on the total LAN characters (determined preiously for each workload), frame size, and IOP serice time per frame. All attached lines are added together to calculate total IOP utilization. LAN IOP serice time per frame is specific to each IOP (see these alues on the Work with Communications Resources display.) Line frame size is specific to each communications line (see these alues on the Change Communications Line display). 134 BEST/1 Capacity Planning Tool V5R1

155 Memory Modeling Utilization for WAN IOPs is determined similarly by using the total WAN characters and number of WAN IOPs for WAN utilizations. Using the total characters for the lines connected to each IOA and the number of each type of IOA determines the utilization for the communications IOAs. The communications IOAs include LAN, WAN, and Integrated Netfinity Serer. Communications Lines: Utilization of a LAN communications line is determined using the total LAN characters (determined preiously for each workload), line oerhead and line speed. Utilization alues are aeraged across all lines in a line resource. Line oerhead and line speed in kilobits per second is specific to each communications line (see these alues on the Change Communications Line display). Utilization for WAN lines are determined similarly by using the total WAN characters per line. Multifunction IOPs: Adding together the utilization for each type of actiity determines the utilization for a multifunction IOP. For example, you could add the utilization due to disk actiity plus utilization due to communications actiity. The goal of memory modeling is to determine the effect of load, storage size, and working set size on performance, in general, and on paging in particular. When recommendations concerning pools and storage size are made, BEST/1 considers a wide ariety of factors. The principles of how BEST/1 makes these recommendations follow. Each job (transaction) uses a certain amount of storage, depending on the size of the programs and data areas it uses. In the eent of abundant memory, the amount of real storage gien to the job in a particular pool would be the maximum amount of storage it would eer need. In this situation, the job would not experience any aoidable faults, that is, all portions of the program and data would almost always be loaded in real storage. Practically, this situation almost neer occurs because there are many jobs running on the system simultaneously and there is rarely enough storage to satisfy all of their maximum needs simultaneously. Therefore, only a part of the data and program areas for a job are in memory at the same time. The term resident set size, which is used in this section, refers to how much real storage is actually aailable for the job. The ideal resident set size is called working set size, which indicates how much real storage the job requires to achiee satisfactory performance. (Working set size is shown on the Change Paging Behaiors display.) Each time a job requests portion of the program or data that is not memory resident, the nonmemory resident item must be retrieed from a direct access storage deice (DASD) while the job waits. This is when a page fault occurs. Using this underlying idea of how jobs behae, BEST/1 employs the following strategy for memory modeling. Upon reading a newly created model: Chapter 7. Modeling Changes to the System 135

156 Determine what the resident set is for each set of jobs in a pool in the original configuration. The resident set is the actual amount of main storage that is aailable for the job when it is running. Because resident set sizes for jobs are not measured for non-machine pools, BEST/1 computes them by estimating the aerage number of jobs that hae pages in the pool. It uses the number of display stations, pool actiity leel, and the aerage number of jobs actiely waiting for CPU and disk resources in this estimation. BEST/1 also takes into account the transactions paging rates to determine the resident set size for different transactions that share the same pool. Calculate paging coefficients for transactions using measured synchronous reads per transaction, resident set size, CISC-to-RISC working set size conersion factors, and specified paging behaior (such as paging exponents). When analyzing a What-if...? scenario for subsequent ealuations: Determine what the new resident set is for each set of jobs in a pool (for example, if demand has gone up, resident sets will be smaller, if demand has reduced or storage resources are more plentiful, resident sets will be larger). Determine the new number of page faults per transaction and collect those results by pool, using the specified paging behaior characteristics and calculated paging coefficients for each transaction. Determine the effects on the workloads response time and the system as a whole due to changed faulting (for example, additional I/O and CPU oerhead which increases utilizations and response times). Compare the number of faults with the specified guidelines (for the appropriate CPU model architecture) and output synchronous read exceptions when guidelines are not met (machine pool and other pools are considered separately). See Editing Sync Reads Guidelines on page 103 for more information on how synchronous reads correspond to page faults. If synchronous reads exceptions are identified, add storage on a pool-by-pool basis until architecture-based guidelines hae been satisfied. The resulting pool additions are combined, rounded up to the next configurable storage increment, and that amount of storage is then output as a recommendation. The decisions are made pool-by-pool: the pool that needs the most storage (because it has the largest synchronous reads) receies it and a pool that has no synchronous read problem receies a little or no additional storage. This approach minimizes the total amount of storage recommended. Note: BEST/1 only makes recommendations if you choose the analysis options that include recommendations. Memory Modeling Terminology Resident set refers to how much real storage is aailable for the job. Depending on the access patterns within the job, the percentage of the maximum requirement that the resident set represents, and the processing rate, the fault rate for that job aries as seen in Figure 104 on page 137. Generally, as the resident set decreases, paging increases, eentually dramatically. As the resident set increases, paging decreases, eentually leeling off as the resident set (real storage) approaches the total storage requirement. 136 BEST/1 Capacity Planning Tool V5R1

157 Figure 104. Resident Set s. Page Faults or Sync Reads For each transaction, the paging cure shown in Figure 104 can generally be represented by the following mathematical equation: SR = cput x pcoeff x (RSS) - (pexpo) Where: SR Number of sync reads per transaction cput CPU time per transaction (in B10 seconds) rss Resident Set Size for the transaction pcoeff Paging coefficient for the transaction pexpo Paging exponent for the transaction If the pexpo is 2, then doubling the resident set size (RSS) decreases paging by a factor of 4. If there are two transactions T1 and T2, which had the same parameters except that pcoeff for T2 was twice the pcoeff for T1, then the number of page faults per transaction for T2 will be twice that of T1. The working set of a transaction is the number of pages in the resident set at which the transactions hae an acceptable number of page faults. As you can see, working set size and resident set size are related but hae different alues and concepts. 1 In the iseries serer, two separate types of pages faults exist: database (DB) and nondatabase (NDB), which BEST/1 computes separately. BEST/1 assumes the same RSS alue for the aboe equation for DB and NDB faults, but allows for separate paging coefficients (pcoeff) and exponents (pexpo) for each. 1. In the excess memory situation, BEST/1 assumes that a transaction cannot make effectie use of memory larger than 2.0 x working set. For example, een if the amount of aailable memory is large, for paging calculations the RSS cannot exceed 2.0 x working set. This assumption enables BEST/1 to effectiely deal with the fact that the performance data does not measure resident or working sets for transactions. Chapter 7. Modeling Changes to the System 137

158 BEST/1 calculates the RSS and paging coefficients from performance measurements using heuristic algorithms and user-proided (or default) paging exponents and working sets. To simplify the task of estimating and proiding paging exponents and working sets for transactions, BEST/1 proides default alues for some popular applications and a generic default. These alues are referred to as paging behaior. Paging behaior proides paging exponent and working set size by indiidual transactions. You can select the following types of predefined paging behaior from BEST/1: *GENERIC: A generic behaior in which DB and NDB are treated the same. This is the default behaior. *OFFICE: A behaior for a workload with paging characteristics similar to the IBM Office workload. *RAMPC: A behaior for a workload with paging characteristics similar to the IBM RAMP-C workload. *SQLRTW: A behaior for a workload with paging characteristics similar to the IBM SQLRTW workload. Figure 105 shows the relationship of the types of paging behaior by showing the effect on synchronous reads per transaction. This is caused by changes in the amount of memory aailable for a job in a pool (RSS). This figure primarily shows the effect of the paging exponents for corresponding workloads (paging behaiors). Figure 105. Relatie Change in Resident Set Size Figure 106 on page 139 shows the actual changes in synchronous reads per transaction at arious RSS sizes for RAMP-C, OFFICE, and SQL-RTW. This figure shows that each workload has a different WSS, and different paging exponents. 138 BEST/1 Capacity Planning Tool V5R1

159 Figure 106. Synchronous Reads/Transaction s. Resident Set Size If you change any transaction paging alue on the Change Paging Behaior display, as shown in Figure 107 the paging behaior is changed to *USER. This display shows the current paging alues for the transaction, which you can Change Paging Behaior Paging behaior...: *GENERIC Type changes, press Enter. If any alues are changed, Paging Behaior field is set to *USER. If working sets or paging exponents are changed, paging coefficients are set to 0. Working set size M B Database Non-DB Paging exponent Paging coefficient F3=Exit F12=Cancel Figure 107. Change Paging Behaior Display change. Changing any alue will set the Paging Behaior field to *USER. To change global paging alues use the Edit Paging Behaior display. You can also change paging behaior alues from the Edit Transactions display. Techniques for Achieing Effectie Storage Recommendations You can see from the preious oeriew that many factors are inoled in the sophisticated methodology BEST/1 uses for predicting storage requirements. Many Chapter 7. Modeling Changes to the System 139

160 of these can be iewed, changed, or both, as the analyst has additional information for BEST/1 to consider. Edit Sync Reads Guidelines Type changes, press Enter. Values are used for Analysis recommendations. Check sync reads... Y Y=Yes, N=No Pool 1 (*MACH) CPU relatie performance Guideline Threshold 2.0 or less Greater than All Other Pools CPU relatie performance Guideline Threshold 2.0 or less or less or less or less or less or less Greater than F3=Exit F12=Cancel *CISC CPU MODELS USE *GUIDE VALUES, *RISC CPU MODELS USE *THRESH VALUES Bottom Figure 108. Editing Sync Reads Guidelines Change the guidelines for the appropriate CPUs by the ratio of synchronous reads to pool faults. For example, if the measured synchronous reads are 50 and the pool faults are 30, the ratio is 1.67 and you should raise the guidelines by 67%. Dealing with conseratie Work Management Guidelines Your experience may indicate that the performance at your installation can be satisfactory with higher page fault rates than what is recommended in the Work Management book. If the work management CISC and RISC guidelines and thresholds are too conseratie, increase the alues on the Edit Sync Reads Guidelines display to reflect a higher number of sustainable sync reads. If you are analyzing only CISC CPU models, then only the alues in the Guideline column need to be increased. If you are analyzing only RISC CPU models, then only the alues in the Threshold column need to be increased. Note: Consider using *NONE or *NONE combined with specific workload response time and throughput objecties to oerride memory upgrade analysis. Dealing with synchronous reads that are not due to page faults BEST/1 considers synchronous reads to be caused by page faults. You can use one of the two approaches when there is a substantial difference between the measured number of pool faults and synchronous reads (as seen in the performance monitor report or in the CRTBESTMDL job log). 1. Edit the sync reads guidelines to reflect the actual ratio of synchronous reads to pool faults. You can find this ratio of synchronous reads to page faults for each pool in the CRTBESTMDL job log. This is appropriate because the alues normally seen in the Edit Sync Reads Guidelines display, as seen in Figure 108 are work management guidelines for pool faults whereas BEST/1 is comparing 140 BEST/1 Capacity Planning Tool V5R1

161 the number of sync reads with guidelines for faults. You can access the Edit Sync Reads Guidelines display by selecting option 11 (Analysis parameters menu) from the More BEST/1 options display. Then select option 2 (Edit sync reads guidelines). 2. If a substantial percentage of synchronous reads are not affected by aailability of memory, then you should moe those synchronous reads to synchronous writes so that the number will not change as load on memory changes, and set the paging coefficient to zero. The paging coefficient is recalculated next time the model is analyzed. See Changing Functions and Transactions on page 116 for more information on the Change Transaction display. If 40% of synchronous reads are not related to memory congestion, moe 40% of the sync reads to sync writes. After the paging coefficient has been set to zero and the model reanalyzed, the sync read alues on the Main Storage Pool Report should match the measured pool fault rate. This may affect DASD results adersely if you are modeling RAID, mirroring, or checksum protection because IOs are added for all writes or permanent writes. Notes: a. Do not use this approach if checksum or mirroring protection is being modeled, or when modeling high aailability disks (such as 9337, 660x-070 models). b. Make these changes to the baseline model only. Do not make them after you hae made What-if...? changes, such as a change in the configuration or workload objectie. Dealing with transaction specific paging behaior BEST/1 uses the indicated paging behaior profile for each transaction to determine the effect of reduced storage on each transactions sync reads rate. Reiew the paging behaior indicated for each transaction (particularly for transactions that run in the pools which are predicted to hae substantial sync read rates) to see if the types are appropriate. If they are not appropriate, proide better alues for paging exponent and working set size. If you change paging exponent and working set size, the paging behaior changes to *USER automatically. Use the Change Paging Behaior display, as shown in Figure 107 on page 139 which you can reach from the Change or Create Transaction displays by pressing F13 (Change paging behaior). After making these changes, be sure to set the paging coefficient to zero for the transaction. On the Change Paging Behaior display, decreasing the working set size alue means transactions require less memory, therefore paging will decrease. Conersely, increasing the working set size means transactions require more memory therefore paging increases with less memory aailable. The higher the paging exponent, the quicker the fault rate increases as aailable memory decreases as seen in Figure 109 on page 142. Chapter 7. Modeling Changes to the System 141

162 Figure 109. Resident Sets with Paging Exponents Note: Make these changes to the baseline model only. Do not make them after you hae made What-if...? changes, such as a change in the configuration or workload objectie. Dealing with inappropriately sized pools and actiity leels When calculating resident set sizes for transactions, BEST/1 uses the pool actiity leel, in addition to the pool size, aerage number actie in the pool and the number of actie jobs in the pool. If the pool actiity leel is set without regard to aailable memory in the pool, then these calculations might be incorrect. Check and set the pool actiity leel to roughly the number of jobs that can run concurrently in the pool, while maintaining reasonable paging performance. You should also proide the working set size estimate for the transactions to guard against the problems that arise when the pool contains excessie amounts of memory as compared to what is required for the specified actiity leel. 2 Change the paging coefficient to zero after making these changes. When BEST/1 is making pool-by-pool determinations of which pools need how much additional storage, it will neer decide to remoe storage from a pool. If a pool is excessiely configured, the analyst should remoe the excess storage and thus possibly reduce BEST/1 s oerall storage recommendation. 2. The difficulty arises due to lack of measurement data to indicate the amount of memory a transaction receies in a pool. BEST/1 estimates this alue, based in part upon actiity leels that the user can modify, to deal with two opposite situations: Suppose pool 3 is used by only one job whose working set is 2 MB. The pool actiity leel is 10 and pool size is 2 MB. BEST/1 assumes it should allocate 2 MB to a larger number of jobs (between 1 and 10, approximately 4) and gies the job about 600 KB. Howeer, in the real system the job would hae gotten all of the 2 MB. The solution in this case is to set the pool actiity leel to 1. Suppose pool 4 has 20 MB of memory with an actiity leel of 1, but in the measured interal only 1 job was actie that has a 4 MB working set. If all of the pool 4 memory is allocated to that single job, it will get a 20 MB resident set. In a What-if...? situation when 1 more actie job is added, BEST/1 reduces the amount of memory that each job gets to perhaps 10 MB and computes large page fault counts for each of them (4 times for each job). Howeer, in a real system for each job, there would hae been no change in the number of page faults. The solution in this case is to proide the working set size (4 MB) for the transaction as part of the paging behaior for the transaction. 142 BEST/1 Capacity Planning Tool V5R1

163 Note: Make these changes to the baseline model only. Do not make them after you hae made What-if...? changes, such as a change in the configuration or workload objectie. Chapter 7. Modeling Changes to the System 143

164 144 BEST/1 Capacity Planning Tool V5R1

165 Chapter 8. Selected Modeling Topics This chapter shows the basic procedures for special modeling topics including: Client Access Batch Communications Data protection CISC-RISC transition ASP and Journaling Release leel performance improements The information in this chapter assumes all preious chapters hae been reiewed, particularly Chapter 3. Building a Model Using Measured Data, Chapter 6. Model Analysis and Calibration, and Chapter 7. Modeling Changes to the System. Not all displays that are used when modeling measured data are shown. Howeer, the displays that hae some relationship to Client Access functions are shown with comments. In this example, performance data included other work in addition to Client Access work. This is done so that the entire system enironment is modeled, not just Client Access functions. Modeling Client Access This section shows a basic procedure for modeling Client Access workloads. Strategy for Defining Workloads First, collect your performance data when the Client Access functions, and any other work you want to model are actie. When modeling Client Access functions, you should understand that almost all are grouped under the *CLIENTAC4 job type. Client Access Functions not included in this job type are the original client Submit Remote Command and Shared Folders type 0 or 1, which are counted as DDM Serers (*DDM). If you want to separate WSF work and Client Access functions such as file transfer and shared folders, you should collect data when only WSF jobs or only Shared Folder jobs or only file transfer jobs, are actie. Then you can easily group these separate and distinct functions into separate workloads. On the other hand if you want to include Submit Remote Command and Shared Folders type 0 or 1, you should collect data when there is no other DDM actiity in the system. You could then assign jobs with type *DDM to the Client Access workload. Use Create BEST/1 Model, Select Performance Member, Job Classification, Edit Job Classifications, and Assign Jobs to Workload displays to assign *AUTOSTART and *BATCH job types to the BATCH workload, *CLIENTAC4 job types to the CA4 workload and *INTERACTV job types to the INTER workload. If during the measurement period only Shared Folders Type 0/1 or original client Submit Remote Command functions were using DDM, you might want to assign Copyright IBM Corp. 1998,

166 *DDM to the CA4 workload to account for Shared Folders type 0 and 1 and original client Submit Remote Command work. Assign Jobs to Workloads Workload... Type options, press Enter. Unassigned jobs become part of workload QDEFAULT. 1=Assign to aboe workload 2=Unassign Number of CPU I/O Opt Workload Job Type Transactions Seconds Count _ BATCH *AUTOSTART _ BATCH *BATCH _ CA4 *CLIENTAC _ INTER *INTERACTV *MONITOR *SYSTEM *LIC *WRITER *SCPF Bottom F3=Exit F12=Cancel F15=Sort by workload F16=Sort by job type F17=Sort by transactions F18=Sort by CPU seconds F19=Sort by I/O count Figure 110. Client Access Example Assign Job Types to Workloads Generally, when modeling Client Access workloads, do the following: Assign *CLIENTAC4 Job Types to the CA4 Workload you name. Assign *DDM Job Types to a DDM workload to account for target DDM actiity, including actual DDM and Client Access functions implemented using DDM interfaces. Assign other job types to other workloads as required. Allow *LIC work to be spread across all defined workloads, including QDEFAULT. Do not manually assign *LIC to a system workload. Reiewing the Number of Actie Jobs in the New Model Return to the Work with BEST/1 Model display to choose and iew the Specify objecties and actie jobs option. Verify that the current model s identification of actie local, LAN, and WAN jobs per workload is reasonable. In the example shown in Figure 111 on page 147, which is a lightly loaded system, note that there were, on the aerage, 1 local job running Client Access and 1.6 LAN jobs running Client Access 146 BEST/1 Capacity Planning Tool V5R1

167 Specify Objecties and Actie Jobs Model/Text: PWSGEN03 Type changes, press Enter. ---Interactie---- Workload Actie Rsp Non-inter Workload Connect Type Jobs Time Thruput Thruput CA4 *LOCAL *NORMAL CA4 *LAN *NORMAL CA4 *WAN *NORMAL Bottom F3=Exit F11=Show all quantities F12=Cancel F15=Sort by connect type F19=Work with Workloads Figure 111. Display Objecties of Newly Created Model Reiewing the Workloads Verify that all workloads in this newly created model are reasonable, as well. Use option 2 in the option field as shown in Figure 112. Work with Workloads Model/Text: PWSGEN03 PWS general workload Type options, press Enter. 1=Create 2=Change 3=Copy 4=Delete 5=Display 6=Print 7=Rename 8=Sae workload to workload member 9=Edit transactions Opt Workload Text 2 BATCH Measured from QPFRDATA (SHAREDFLDR) 2 INTER Measured from QPFRDATA (SHAREDFLDR) 2 CA4 Measured from QPFRDATA (SHAREDFLDR) 2 QDEFAULT Measured from QPFRDATA (SHAREDFLDR) Bottom F3=Exit F6=Add saed workload F9=Add predefined workload F12=Cancel F13=Combine workloads Figure 112. Reiew Workloads This section concentrates on the CA4 workload, but you should reiew the rest of the workloads and make the appropriate changes if necessary. Chapter 8. Selected Modeling Topics 147

168 Figure 113 displays the transaction detail for the Client Access Workload. From the Transaction Type you can see that the workload is made up of interactie (WSF) and non-interactie transactions. Pool 5 contains non-interactie transactions from jobs and tasks related to QCMN (communications) subsystem. Pool 2 contains non-interactie transactions from jobs and tasks related to Shared Folder actiities. Interactie jobs (WSF) run at priority 20 in pool 4. Change Function Workload...: CA4 Measured from QPFRDATA (SHAREDFLDR) Function...: CA4 Change fields, press Enter. Function text... Function of CA4 Key/Think time Seconds Additional delays....0 Seconds Transaction Pool Transactions CPU Time Total Type ID Priority per Function (Secs) I/Os Transaction Type: 1=Interactie, 2=Non-interactie Bottom F3=Exit F6=Work with transactions F12=Cancel Figure 113. Reiew CA4 Workload BEST/1 has aeraged the priority of Client Access functions to a priority of 14. This implies that some percent of the work is done at priority 0 and some other at 20. Work Station Function (WSF) is modeled as an interactie type job, with a ery small non-interactie component. This non-interactie component is so small (CPU time = and Total I/Os = 0.0) that it cannot be shown on the display due to the size of the numbers being smaller than the number of aailable decimal places. Analyzing the Client Access Model After the workloads and objecties hae been reiewed and considered reasonable, select option 5 or 6 on the Work with BEST/1 Model display to analyze the model with or without recommendations. Understanding Results When analyzing growth be prepared to obtain less interactie throughput at higher CPU utilizations due to weighted aeraging of Shared Folders Type 2 work. This may lead to interactie response times suffering, due to a non-interactie job running at a higher priority than interactie. 148 BEST/1 Capacity Planning Tool V5R1

169 Howeer, if a large number of Client Access Shared Folder Type 2 jobs are actie on an actual system and they are copying large files to shared folders (rather than seeral small files), it is possible that they will take oer the system from priority 20 interactie jobs at peak actiity, causing interactie response time and throughput to degrade while shared folder throughput increases. BEST/1 weighted aerage implementation allows it to predict this occurrence when modeling excessie growth rates with workloads based on Shared Folder Type 2 measured data. The OS/400 file sering implementation is ery efficient copying files and uses relatiely little CPU. Howeer, in certain mixed interactie and file copy enironments, the customer may need to consider using Shared Folder Type 0/1 support or the optimized client shared folder support which allows full user control oer the shared folder job s priority setting. Modeling Non-interactie Work Many of the most isible workloads on commercial computer systems today are generated by interactie workstations. Howeer, non-interactie work still constitutes a large portion of the total workload at many commercial sites and can be just as critical to performance as interactie work. These sections deals with both non-interactie and batch work. Non-interactie work is any work that does not inole an input and output dialogue between theiseries serer and a workstation operator. In many cases, the work being done inoles significant CPU or disk resource consumption, but it could include work being drien by entries on a data or message queue where a minimum amount of CPU and disk resource utilization occurs while awaiting the queue. Batch work can be performed within an interactie or batch job and is usually characterized by significant CPU or disk resource consumption. In this chapter, batch work is considered a special part of OS/400 non-interactie work. Defining Non-Interactie Transactions When creating a model from performance data, non-interactie transactions can be grouped together or separated into meaningful units of work. As seen in Figure 114 on page 150, transactions can be defined by resources used or a user-defined unit of work. Meaningful definition of transactions are particularly recommended for *BATCHJOB workloads. See Chapter 3. Building a Model Using Measured Data for more information. You can choose different work units for each workload that has non-interactie transactions. If you choose a work unit and the job does not perform any operation of the work unit you hae chosen, the system defaults to an arbitrary alue. interpreting the results in terms of transactions. See Chapter 2. Workload Concepts for more information. Chapter 8. Selected Modeling Topics 149

170 Define Non-Interactie Transactions Job classification category...: Subsystem Type choices, press Enter. ---Actiity Counted as Transaction--- Total Transactions Workload Type Quantity when Type = *NONE QDEFAULT *LGLIO BATCH3 *LGLIO BATCH2 *LGLIO BATCH1 *CPUSEC Bottom Type: *LGLIO, *CMNIO, *CPUSEC, *PRINT, *NONE F3=Exit F12=Cancel Figure 114. Define Non-interactie Transactions Modeling Interactie Transactions Linked to Non-Interactie Sometimes interactie transactions initiate non-interactie jobs that do work in the background. For example, one application may hae an interactie order entry transaction that starts a non-interactie inoice printing job. The two actiities are related and dependent on one another. BEST/1 is not able to establish a dependency connection, but you can emulate this by defining an interactie and a non-interactie transaction in the same function. While this works well for a one-to-one relationship, if the non-interactie job is sering many workstations, you should increase the workload carefully because the non-interactie job may actually become a bottleneck. BEST/1 is not able to model this software dependency. The following example illustrates this technique: In Figure 115 on page 151 the workload ORDER represents an order entry interactie job. In order to model the new job that has a non-interactie job linked to it, go into the ORDER workload and enter option 2 to change it. 150 BEST/1 Capacity Planning Tool V5R1

171 Model/Text: GROWTH Work with Workloads Type options, press Enter. 1=Create 2=Change 3=Copy 4=Delete 5=Display 6=Print 7=Rename 8=Sae workload to workload member Opt Workload Text _ BATCH Measured from TESTLIB (Q ) 2 ORDER Measured from TESTLIB (Q ) _ QDEFAULT Measured from TESTLIB (Q ) Bottom F3=Exit F6=Add saed workload F9=Add predefined workload F12=Cancel F13=Combine workloads Figure 115. Work with Workloads From the display shown in Figure 116 press F6 (Work with functions). Workload...: ORDER CPU architecture...: *CISC Change Workload Type changes, press Enter. Workload text... Measured from TESTLIB (Q ) Workload Type...: *NORMAL F4 for list Usage mode =Casual 2=Interrupted 3=Steady 4=N/A Functions Ag K/T Tns per Function Function Text per User (secs) Inter Non-inter Function of ORDER Bottom F3=Exit F6=Work with functions F9=Specify Chars to Comm Line Resources F10=Specify I/Os to ASPs F11=Show functions with olume F12=Cancel Figure 116. Change Workload Select option 2 in Figure 117 on page 152 to change the ORDER workload functions. Chapter 8. Selected Modeling Topics 151

172 Work with Functions Workload: ORDER Measured from TESTLIB (Q ) Type options, press Enter. 1=Create 2=Change 3=Copy 4=Delete 7=Rename Opt Function Text 2 ORDER Function of ORDER F3=Exit F12=Cancel Bottom Figure 117. Work with Functions Press F6 (Work with transactions) from the display shown in Figure 118. Change Function Workload...: ORDER Measured from TESTLIB (Q ) Function...: ORDER Change fields, press Enter. Function text... Function of ORDER Key/Think time Seconds Additional delays....0 Seconds Transaction Pool Transactions CPU Time Total Type ID Priority per Function (Secs) I/Os Transaction Type: 1=Interactie, 2=Non-interactie F3=Exit F6=Work with transactions F12=Cancel Bottom Figure 118. Change Function Press F6 in Figure 119 on page 153 to create a new transaction. Note that there are already some non-interactie transactions linked to the ORDER interactie workload. These are system related tasks running in pool 1 at priority BEST/1 Capacity Planning Tool V5R1

173 Work with Transactions Workload...: ORDER Measured from TESTLIB (Q ) Function...: ORDER Function of ORDER Type options, press Enter. 2=Change 3=Copy 4=Delete 5=Display Transaction Pool Transactions CPU Time Total Opt Type ID Priority per Function (Secs) I/Os _ _ _ Transaction Type: 1=Interactie, 2=Non-interactie Bottom F3=Exit F6=Create transaction F12=Cancel Figure 119. Work with Transactions Type in the transaction details in Figure 120. You need to know the characteristics of the batch transaction that you are creating. The IBM-supplied workloads may help in this regard. The only difference between this and an interactie transaction definition will be the transaction type (2 for batch and 1 for interactie). Press the Enter key twice to return to the Change Function display. In the Transactions per function field type the same number (249.65) as you hae for interactie transactions to link non-interactie transactions to each interactie transaction. Create Transaction Workload...: ORDER Measured from TESTLIB (Q ) Function...: ORDER Function of ORDER Type choices, press Enter. Transaction Type =Inter, 2=Non Pool ID... 2 F4forlist CPU Priority CPUtime Secs (on B10) Permanent writes percent Chars transferred in Chars transferred out Exceptional wait....0 sec Paging behaior... *GENERIC F4 for list Application Type... *DEFAULT F4 for list DB Reads DB Writes NDB Reads NDB Writes Sync I/Os Async I/Os F3=Exit F4=Prompt F6=Calculate B10 CPU time F12=Cancel F13=Change paging behaior Bottom Figure 120. Create Transaction Chapter 8. Selected Modeling Topics 153

174 Modeling Batch Workloads of type *BATCHJOB contain transactions that are performed by jobs that are always actie and long-running. The throughput rate of these transactions depends on the aailability of the resources to perform them. *BATCHJOB transactions are normally performed by non-interactie jobs, but can also be thought of as the work done by interactie jobs without interention of workstation operators. Isolation of Batch into an Independent Workload With BEST/1, batch jobs can be grouped into independent workloads. This proides a means to model batch in a way similar to interactie. Throughput and response time for non-interactie transactions are reported, similar to interactie reporting. When the workload represents one or more batch jobs that are concurrently and constantly actie, BEST/1 automatically creates the workload with the special workload type *BATCHJOB. Alternatiely, you may manually designate a workload with these characteristics as workload type *BATCHJOB and the appropriate number of actie jobs. This designation instructs BEST/1 to increase or decrease the number of transactions processed per job as the system performance improes or deteriorates. For more information, see Chapter 3. Building a Model Using Measured Data. Changes can be made to the batch workload and the results of these changes can be analyzed. It is possible to grow the batch workload while keeping other workloads constant. For *BATCHJOB work, transactions processed per job increase automatically, as changes to system performance permit. For any non-interactie work, increasing the number of actie jobs represents an increase in demand for that kind of work. From the Create and Change Workload displays, you can specify your workload type as *BATCHJOB, but you need to keep in mind the following considerations: Batch jobs are few and are long running. A batch job runs throughout the measurement interal. It is doing as much work as the system allows. The amount of work done by the batch job will increase if other actiity is reduced or additional resources are added. Conersely, the amount of work done by the batch job will decrease if other actiity is increased or some resources are remoed from the system. Note: Serer jobs typically should not be specified as *BATCHJOB workloads because they do not meet the criteria where a change in system actiity or configuration will change the throughput of the serer job. Serer jobs are dependent upon the number of work requests receied. If a serer job workload is characterized as *BATCHJOB, BEST/1 assigns unexpectedly high CPU utilization to that workload that does not compare accurately to measured performance data. BEST/1 *BATCHJOB workloads must hae the following characteristics: Only one function No interactie transactions 154 BEST/1 Capacity Planning Tool V5R1

175 One non-interactie transaction that runs at less than 0 priority in a pool with only non-interactie transactions One or more non-interactie transactions running at 0 priority Special Considerations when you collect data The performance monitor is a batch job, so all the actiity associated with the QPFRMON job is counted as regular batch unless you explicitly define a separate workload for this job. Normally this job uses little CPU time, but this amount might be significant if you are collecting trace data or if the time between samples is too short. All the actiity associated with Collection Serices is processed with the QYPSPFRCOL job. Since capacity planning methods deal with aerages, trends and oerall system behaior, your measurement samples will probably be in the minute range. This will not include trace or 5494 remote response time data, and in this case the QPFRMON job will not be noticeable. Howeer, if the Performance Monitor was started with either TRACE(*ALL) or the RRSPTIME(*SYS) or RRSPTIME(time boundary alues) parameters the work done on behalf of the Performance Monitor may significantly affect any batch modeling work you do. If no 5494 Remote Control Units with microcode release 1.1 are aried on, the RRSPTIME parameter does not cause the Performance Monitor to use significant CPU. STRPFRMON TRACE(*ALL) can affect disk I/O and space on a heaily loaded (busy) system, but the biggest effect is when the trace table is being dumped to disk. You can ENDPFRMON DMPTRC(*NO) to delay the dumping of the trace table until a less busy time. If you collected trace data with the Start Performance Trace (STRPFRTRC) command, you can use the End Performance Trace (ENDPFRTRC) command to dump the trace data. Use the Performance Tools Component report to determine the effect of the performance job (QPFRMON or QYPSPFRCOL) on your system. If you need to exclude the performance job work from your batch workload, there are at least fie ways to do so: Classifying the QPFRMON job by subsystem This is the easiest way. You just hae to follow these steps the first time. 1. Create your own job queue. 2. Create your own subsystem. 3. Add your job queue to the subsystem. 4. Add the appropriate routing entries to the subsystem. 5. Change STRPFRMON command to hae your job queue as default. Before you start collecting data your subsystem must be actie and the subsystem should hae no actiity besides the performance monitor. When creating the model from performance data, classify jobs by subsystem instead of default classification (see Classifying Jobs into Workloads on page 39). Assign your subsystem to its own workload, such as QPFRMON. All other subsystem work can be assigned as you wish. After the model has been created, delete the QPFRMON workload. Classifying jobs by functional areas Chapter 8. Selected Modeling Topics 155

176 You hae to create a functional area with QPFRMON or QYPSPFRCOL as the only job. Assign the QPFRMON or QYPSPFRCOL functional area to one workload. You may want to create your own functional areas and assign them to different workloads. Proceed as in the preious procedure to delete the QPFRMON or QYPSPFRCOL workload. Classifying jobs by job name The procedure is almost identical to the preious one, except that you are selecting jobs. Classifying jobs by job number The only difference with preious procedures is that you hae to record QPFRMON or QYPSPFRCOL job number. Classifying jobs by type and by job name First you hae to assign all batch jobs to one workload and create the model as usual, but defining your own work units by putting *NONE as type and an arbitrary alue such as as the number of total transactions as shown in Figure 114 on page 150. Create another model assigning QPFRMON or QYPSPFRCOL to its own workload, using the same work units of the preious step. Reiew transaction details of QPFRMON or QYPSPFRCOL transactions that are running in pool 2; see Figure 119 on page 153 as an example of the information displayed. Change your original model batch transaction running in pool 2, subtracting the CPU time and I/O recorded in the preious step. Inclusion of Batch in CPU Model Recommendation One of the model analysis options is Analyze current model and gie recommendations. Recommendations for CPU upgrades are made for jobs which fall under a particular priority grouping. A default priority of 20 is used. Howeer, this can be changed to other alues to include non-interactie work. For example, you hae priority 30 non-interactie work that works on behalf of interactie users and you need to include it in the analysis with recommendations. Calibrating *BATCHJOB Workloads As discussed in Chapter 6. Model Analysis and Calibration, *BATCHJOB workloads should be carefully obsered during calibration. If the predicted throughput is not within 10% of the measured transaction throughput, *BATCHJOB may not be an appropriate workload type. If this is the case, change the workload type to *NORMAL, and see if the calibration behaior of other workloads improes. If you set the *BATCHJOB workload type, check that the number of actie jobs has been set appropriately. Also, it is recommended that the main storage pool that the workload uses: Not be used by any other workloads Set their actiity leels to the number of actie jobs Note: *BATCHJOB workloads that are comprised of serer jobs generally do not calibrate because they do not meet the criteria where a change in system 156 BEST/1 Capacity Planning Tool V5R1

177 actiity or configuration changes the throughput of the workload. Serer jobs are dependent upon the number of work requests receied. If a serer job workload is characterized as *BATCHJOB, BEST/1 assigns unexpectedly high CPU utilization to that workload that does not compare accurately to measured performance data. Predicting Batch Transaction Throughput Example This section shows an example of modeling batch with the primary intention to estimate elapsed run time changes. There is no explicit batch window modeling in BEST/1. To illustrate how to estimate batch job run time, run a batch job in its own pool, performing a DSPOBJD OBJ(*ALL) OBJTYPE(*FILE) OUTPUT(*OUTFILE) OUTFILE(MYLIB/DSPOBJD). Use DSPOBJD, which is unlike any real user batch input stream, but includes significant disk time, which is common in many OS/400 commercial enironments. The D45 system takes 41 minutes to complete this job in a non-dedicated enironment. The objectie is to estimate how long the job takes on an E50 with same memory and disk configuration. Anticipate ery little improement because the job is I/O bound, and not CPU bound. 1. Build a model with the needed batch job. It is important to include a period long enough to coer the main processor of the job, but not the actie job start or end. The job started at 14:23 and ended at 15:04, so take the period shown in Figure 121. Record the job number to classify it in its own category as shown in Figure 122 on page 158. Create Model from Performance Data Model...: DSPOBJD Type choices, press Enter. Text... Performance member... DSPOBJ1 Name, F4 for list Library... QPFRAAID05 Name Start time... 14:30:00 Time, *FIRST, *SELECT Start date... *FIRST Date, *FIRST Stop time... 15:00:00 Time, *LAST Stop date... *LAST Date, *LAST F3=Exit F4=Prompt F12=Cancel Figure 121. Create Model from Performance Data - Batch Run Time Chapter 8. Selected Modeling Topics 157

178 Edit Job Classifications Enter workload names and category alues which are assigned to each workload, press Enter. Jobs with unassigned alues become part of workload QDEFAULT. Workload Job Number Workload Job Number Workload Job Number DSPOBJD F3=Exit F9=Display alues from data F12=Cancel If you want to display alues from the performance data, press F9 More... Figure 122. Edit Job Classifications - Batch Run Time 2. When the model is created, the workload type is *BATCHJOB. which indicates transaction backlog workload ( Figure 123). Use a alue of 3 for the pool s actiity leel in which the job is running and change all the other transactions that are running on this pool to use another one. This ensures that only the batch job to be modeled is using the storage pool exclusiely. If pool assignments hae been changed, reset the paging coefficients by pressing F22 (Calibrate model) on the Work with BEST/1 Model display. Analyze the model, and press F22 again to return to what-if analysis mode. Analyzing in manual calibration mode recalculates and resets the paging coefficients. 158 BEST/1 Capacity Planning Tool V5R1

179 Specify Objecties and Actie Jobs Model/Text: DSPOBJD DSPOBJD (From 14:23 to 15:04) Type changes, press Enter. Workload Actie ----Interactie---- Non-inter Workload Connect Type Jobs Rsp Time Thruput Thruput DSPOBJDD *LOCAL *BATCHJOB QDEFAULT *LOCAL *NORMAL Bottom F3=Exit F11=Show all quantities F12=Cancel F15=Sort by connect type F19=Work with Workloads Figure 123. Specify Objecties - Batch Run Time 3. Reanalyze the model, and the predicted batch throughput for our current model (D45) is 13 as shown in Figure 124. Display Workload Report Period: Analysis CPU Thruput Response Times (Secs) Workload Type Util per Hour Internal Local LAN WAN QDEFAULT DSPOBJD QDEFAULT Type: 1=Interactie, 2=Non-interactie, 3=*BATCHJOB Performance estimates -- Press help to see disclaimer. F3=Exit F11=Response time detail F12=Cancel Bottom Figure 124. Display Workload Report - Batch Run Time 4. Change the CPU model to E50 and reanalyze the model. The job throughput increased from 13 to 15. Anticipate that our current batch window time of 41 minutes is decreased in the same proportion, that is 41*(13/15) = 35.5 minutes. A manual approach for predicting batch job run time is shown in Appendix E. Manual Batch Window Modeling. Chapter 8. Selected Modeling Topics 159

180 Batch Window Modeling Often customers are faced with questions like: How long will my batch thread take to run? What model of OS/400 do I need to reduce the batch thread s run time? How much more throughput can I get by upgrading to a particular system model? What changes will occur if more or different disks are used? A batch modeling tool is expected to be able to help answer questions like these. Seeral different approaches are possible, depending on the characteristics of the jobs in the thread. If these are one or more jobs whose run time is substantial, or a large portion of the batch window: 1. Construct a model for each job using the technique shown in the Predicting Batch Transaction Throughput Example on page Predict the new run time for each job using its specific model. 3. Add the results for each job together to get the length of the batch thread. If there are many jobs or mostly smaller jobs: 1. Construct a model from data, coering the entire thread. 2. Isolate a storage pool for the thread to use, and set the actiity leel to Predict the new throughput. If the start time for a job depends on more jobs than just the job before it in the batch thread: 1. Construct a model for each job or batch thread. 2. Use technique 1 or 2 to predict run time for each thread. 3. Use the length of the longest thread as the run time for that portion of the window. Basic Procedure for Batch Window Modeling After deciding which approach is most suitable, use the following basic procedure in BEST/1: 1. Build a workload that contains only the batch job or batch thread that needs to be modeled. This can be done by classifying jobs by job name and selecting the batch jobs specifically. Use different workloads to include other interactie concurrent jobs, if necessary. Note that the job classification is only aailable when using measured data. Use a meaningful definition for non-interactie transaction count wheneer possible. 2. Use workload type *BATCHJOB if you want BEST/1 to automatically increase throughput as conditions permit. Use *NORMAL if you would like to specifically indicate the amount of workload growth. If *BATCHJOB has been indicated, set the actie jobs to the actual number of concurrent jobs. For example, if a thread of jobs run one after another, but none eer run at the same time, the number of jobs is one. 3. Verify that the actiity leel in the main storage pool associated with the batch workload is the same as the actual number of concurrent jobs (as measured for the workload). BEST/1 uses the actiity leel as an indication of how many jobs are competing for resources concurrently. 160 BEST/1 Capacity Planning Tool V5R1

181 Communications Support 4. Make sure that there is no other actiity in the main storage pool (from other workloads). If pool assignments hae been changed to accomplish this, reset the paging coefficients by pressing F22 (Calibrate model) on the Work with BEST/1 Model display. Analyze the model, and press F22 again to return to what-if analysis mode. Analyzing in manual calibration mode recalculates and resets the paging coefficients. 5. Analyze the model with your current configuration and look at the batch workload throughput. Check the predicted throughput if *BATCHJOB workloads are present. If calculated throughputs are not within 10% of measured, the *BATCHJOB behaior may not be descriptie of this work. 6. If *BATCHJOB workloads are being used, increase the actie jobs and pool actiity leel only if the actual number of concurrent jobs increases. Otherwise, these alues should not be changed. For *NORMAL workloads, increase the number of jobs manually, or use option 7 (Specify workload growth and analyze model) on the Work with BEST/1 Model display. In either case, if a minimum throughput is required, use option 2 (Specify objecties and actie jobs) on the Work with BEST/1 Model display, to state your requirements. 7. Change the system configuration to the one being ealuated. 8. Analyze the model and interpret the results as follows: If you get a higher batch throughput rate, the batch run time will be reduced in the same proportion. That is, if the throughput rate has doubled, the batch job will take half the time to complete. Using the batch throughput rate, estimate the number of hours required to complete the job. Round the time off to the nearest hour. If faster hardware resources fails to show increased throughput from the *BATCHJOB workloads, check the Main Storage Pool Report to make sure the Actiity Leel setting is correct (See Step 6). 9. Repeat the aboe procedure until the configuration proides a suitable estimated batch job run time, batch window size and system capacity. For CPU bound jobs, when the CPU is upgraded, the oerall throughput will increase depending on the utilization of the CPU. If the CPU is not saturated before the upgrade, the throughput will stay approximately the same, or improe modestly, irrespectie of the power of the new model. If the CPU is saturated, the more powerful model will result in higher batch throughput. For I/O bound jobs, changes in the CPU hae little effect on batch throughput. In these cases you can improe the throughput by changing the application, using faster disks or adding more memory. This was illustrated in the Predicting Batch Transaction Throughput Example on page 157 where an 80% increase in CPU power resulted in only a 14% improement in throughput. Communications support refers to modeling how users are connected to the system. Users can be connected to the iseries serer one of three ways: Locally (direct connection) Local Area Network (LAN) Wide Area Network (WAN) Communications lines (LAN or WAN) can affect response time. The work that traels through these connections might add contention or increase utilization in Chapter 8. Selected Modeling Topics 161

182 the system. The purpose of this section is to explain BEST/1 communications support, the hardware and configuration displays for communications modeling, and how to use them. When modeling and interpreting results, the following assumptions should be taken into account: All controllers are equally distributed across all communications lines for LAN and WAN. All local workstation controllers hae the same serice time. All LAN controllers hae the same serice time. All WAN workstation controllers hae the same serice time. Hardware Characteristics This section describes some of the hardware displays which include communications support. This includes the following displays: Work with Communications IOP Features Work with Line Speeds Specify Connections to Communications IOPs In order to access the hardware characteristics for communications, take the following steps: 1. From the BEST/1 for the AS/400 display select option 60 (More BEST/1 options) and press the Enter key. The More BEST/1 Options display appears. Select one of the following: More BEST/1 Options 1. Work with job classification members 2. Work with workload members 3. Work with configuration members 4. Work with hardware members 5. Work with results members 6. Work with analysis parameters members 10. Hardware characteristics menu 11. Analysis parameters menu 20. Conert MDLSYS files 21. Migrate S/36 workload 51. Moing from MDLSYS to BEST/1 Selection or command ===> 10 F3=Exit F4=Prompt F9=Retriee F12=Cancel Figure 125. More BEST/1 Options Menu 2. Select option 10 (Hardware characteristics menu) and press Enter. The Hardware Characteristics display appears. 162 BEST/1 Capacity Planning Tool V5R1

183 Select one of the following: Hardware Characteristics 1. Work with CPU models 2. Work with Disk IOP features 3. Work with Disk Drie features 4. Work with Communications IOP features 5. Work with Communications line speeds 6. Work with Multifunction IOP features 7. Work with IOA features Selection or command ===> 4 F3=Exit F4=Prompt F9=Retriee F12=Cancel F14=Replace with saed hardware characteristics F24=More keys Figure 126. Hardware Characteristics Menu 3. From this menu, select option 4 (Work with Communications IOP features) and press the Enter key. The Work with Communications IOP Features display appears as show in Figure 127. Work with Communications IOP Features Type option, press Enter. 1=Create 2=Change 3=Copy 4=Delete 7=Rename Max ----Line Speed----- IOP Currently Opt Feature Lines Minimum Maximum Type Aailable *WAN N *WAN Y *LAN Y *LAN Y *WAN Y *LAN N *LAN Y *LAN N *WAN N *WAN N *WAN N Currently Aailable: Y=Yes, N=No More... F3=Exit F12=Cancel Figure 127. Work with Communications IOP Features This display enables you to work with the indiidual communications IOP features defined in BEST/1 and their associated parameters, such as the maximum number of lines to which the feature can be connected, and the minimum and maximum line speed. Chapter 8. Selected Modeling Topics 163

184 Note: An IOP with a minimum line speed of 4 MB or greater is considered LAN. An IOP with minimum line speed of less than 4 MB is considered WAN. Communications IOPs can connect to one or more communications lines with the minimum and maximum line speed entered as kilobits per second. You can change a communications IOP feature if it is no longer aailable, or create a new communications IOP if you want to model newly announced hardware. To create or delete line speeds, select option 5 on the Hardware Characteristics menu to access the Work with Line Speeds display as shown in Figure 128. A similar display is used to select minimum and maximum line speeds when creating or changing a communications IOP feature. Type options, press Enter. 1=Create 4=Delete Work with Line Speeds Opt Line Speed Opt Line Speed Opt Line Speed F3=Exit F12=Cancel Bottom Figure 128. Work with Line Speeds In order to specify CPU connections to communications IOPs and lines, you can use the Specify Connections to Comm IOPs display, as shown in Figure 129 on page 165, if you press F13 on either the Change or Create CPU Model display. 164 BEST/1 Capacity Planning Tool V5R1

185 Specify Connections to Comm IOPs CPUModel...: B10 System Unit...: 9404 Type changes, press Enter. To remoe a connection to a Comm IOP feature, set Max Lines to 0. This will not affect the characteristics of the Comm IOP feature. Max number of LAN IOPs... 1 Max number of WAN IOPs... 2 Max number of WAN lines... 8 Max -----Line Speed----- IOP Currently Feature Lines Minimum Maximum Type Aailable *WAN N *LAN N *LAN N *LAN N Currently Aailable: Y=Yes, N=No Bottom F3=Exit F9=Add IOP feature F12=Cancel Figure 129. Specify Connections to Comm IOPs This display enables you to determine how many IOP types a CPU can support. IOP types can be either LAN or WAN based on the minimum line speed supported by the communications IOP feature. If the communications IOP can connect to a specific CPU, than the line speed supported by the IOP will be alid for that CPU. Communications Configuration This section describes the configuration displays which include communications support. This includes the following displays: Work with Communications Resources Create Multifunction IOP Create IOP Create Communications Line Resource BEST/1 supports I/O adapters (IOAs). BEST/1 recognizes that only multifunction IOPs can connect to IOAs. All disk IOPs, all communications IOPs, and some multifunction IOPs cannot connect to IOAs. As in preious ersions, BEST/1 shows communications lines connected directly to communications IOPs and multifunction IOPs that do not support IOAs. Multifunction IOPs that do support IOAs show connections to IOAs, and these IOAs show connections to the communications lines. To determine which multifunction IOPs allow connections to IOAs, go to the More BEST/1 Options menu and select option 10 to work with hardware characteristics. Then select option 6 to work with multifunction IOP features. This display shows the maximum number of both disk and communications IOAs allowed for each multifunction IOP feature. The other display relates to non-multifunction IOPs and multifunction IOPs that do not support IOAs. Likewise, if a communications IOP is already connected to a line, you cannot change its feature to a multifunction IOP that supports IOAs. For Chapter 8. Selected Modeling Topics 165

186 some functions, there is a separation between IOPs that support IOAs (always multifunction IOPs) and IOPs that do not support IOAs. When you are changing a configuration, there are parallel displays for selecting IOP features and creating IOPs. One display relates to multifunction IOPs that support IOAs. The other display relates to non-multifunction IOPs that do not support IOAs. To access the configuration menu for communications, take the following steps: 1. From the BEST/1 for the AS/400 display select option 1 (Work with BEST/1 Models) and press the Enter key. The Work with BEST/1 Models display appears. 2. Type a 5 (Work with) in the Opt column next to the model you want to use and press the Enter key. The Work with BEST/1 Model menu appears. Work with BEST/1 Model Performance data...: Model/Text...: QPFRDATA (Q ) TEST Select one of the following: 1. Work with workloads 2. Specify objecties and actie jobs 5. Analyze current model 6. Analyze current model and gie recommendations 7. Specify workload growth and analyze model 10. Configuration menu 11. Work with results Selection or command ===> 10 F3=Exit F4=Prompt F9=Retriee F12=Cancel F15=Sae current model F17=Analyze with ANZBESTMDL F22=Calibrate model F24=More keys Model TEST has been read Figure 130. Work with BEST/1 Model Menu 3. Select option 10 (Configuration menu) and press the Enter key. The Configuration display appears. 166 BEST/1 Capacity Planning Tool V5R1

187 Configuration M CPU odel...: 23DE Comm IOPs...: 0 Processors...: 8/8 LANlines...: 14 Main stor (MB)...: WAN lines...: 31 Main stor pools...: 4 Disk IOPs...: 0 Multifunction IOPs...: 21 Disk ctls...: 0 Disk IOAs...: 9 Disk arms...: 89 Comm IOAs...: 28 ASPs...: 6 IPCS IOAs...: 0 Select one of the following: 1. Change CPU and other resource alues 2. Work with disk resources 3. Edit ASPs 4. Edit main storage pools 5. Work with communications resources Selection or command ===> F14=Replace with saed configuration F15=Sae current configuration F20=More BEST/1 options F24=More keys BEST/1 CPU model DE refers to IBMCPU model Figure 131. Configuration Menu The Configuration menu enables you to work with all the configuration elements in the current model, such as CPU models, disk resources, storage pools, and communications resources. 4. Select option 5 (Work with communications resources). The Work with Communications Resources display appears, as shown in Figure 132. Work with Communications Resources Type options, press Enter. 2=Change 3=Copy 4=Delete 7=Rename 8=Create line resources Nbr of Line Speed Pct Line Opt Resource Feature Lines Type (Kbit/sec) Oerhead CC *IOP LANLINE1 1 *LINE CC *IOP WANLINE1 6 *LINE CMB *MFIOP LIN19 1 *IPCS D27DBF0101 *LINE LIN *IOA CMN08 1 *LINE LIN *IOA QESLINE 1 *LINE F3=Exit F6=Create IOP F12=Cancel Bottom Figure 132. Work with Communications Resources This display shows all the IOPs that can support communications actiities, as well as communications IOAs, and line resources in the current configuration. You can create or change communications resource parameters. These Chapter 8. Selected Modeling Topics 167

188 parameters include the IOP feature, its aerage LAN or WAN serice time, line speed, and the number of lines connected to each IOP and IOA. Note: In BEST/1, a line resource represents one or more communications lines, all of which hae the same line speed. Consequently, a communications IOP and IOA can connect to one or more line resources. 5. To create an IOP for communications actiity, press F6 (Create IOP). You see either the Create Multifunction IOP display (Figure 133) or the Create IOP display (Figure 134). Create Multifunction IOP Type information, press Enter. Line resources with 0 lines are not created. IOP... Name IOP feature... F4forlist LAN serice time....0 Msecs per frame WAN serice time....0 Msecs per frame IOA... Name IOA feature... F4forlist Serice time....0 Msecs per frame Line Nbr of Line Speed Pct Line Frame Size Resource Lines (Kbit/sec) Oerhead (Bytes) Duplex Duplex: *HALF, *FULL Bottom F3=Exit F4=Prompt F6=Create line resource F11=Create IOP F12=Cancel Figure 133. Create Multifunction IOP Create IOP Type changes, press Enter. Line resources with 0 lines are not created. IOPname... Feature... F4forlist LAN serice time....0 Msecs per frame WAN serice time....0 Msecs per frame Line Nbr of Line Speed Pct Line Frame Size Resource Lines (Kbit/sec) Oerhead (Bytes) Duplex Duplex: *HALF, *FULL Bottom F3=Exit F4=Prompt F6=Create line resource F11=Create Multifunction IOP F12=Cancel Figure 134. Create IOP 168 BEST/1 Capacity Planning Tool V5R1

189 Note: F11 (Create Multifunction IOP) is only displayed on the Create IOP display when the CPU model in your BEST/1 model can connect to at least one multifunction IOP that can in turn connect to communications IOAs. You can attach one or more communications lines to the current communications IOP or IOA with the aerage line speed that is specified in kilobits per second. Fill in the necessary parameters for the communications IOP and possibly IOA, such as name, feature, and serice times. You also need to fill in information for the first line resource that is displayed. Examples of this information are the number of lines that the line resource represents and an indication as to whether the data is sent half duplex or full duplex. Pct Line Oerhead represents the amount of noninformation bytes that aresent oer a line resource, expressed as a percentage of the information bytes. For example, if 800 information bytes and 200 noninformation bytes are transferred, the oerhead is 25%. Depending on the type of line, noninformation bytes could represent items such as protocol oerhead, or error transmissions. A high alue for line oerhead may indicate error conditions. Notes: a. For lines with less than 10% utilization, the default alue for Pct Line Oerhead is 2%. b. As the traffic on the line increases, the percentage alue for Pct Line Oerhead remains the same. Therefore, whether 800 or 8000 information bytes are transferred, if the alue for Pct Line Oerhead is set to 5%, it will remain at 5%. The aerage size of the information frame that is transferred across the line during the measurement interal determines the frame size. If more frames are transferred, the result is higher IOP (and possibly IOA) utilization. Duplex represents half or full duplex lines. Half duplex lines can only send or receie data at any one time, whereas full duplex can both send and receie at the same time. This means that using full duplex can double the actual line speed of the line. The reason is that data can flow in either direction at the current line speed. 6. Press F6 (Create line resource) to add additional line resources to this new communications IOP (and possibly IOA). 7. To add line resources to an existing communications IOP, select option 8 (Create line resources) on the Work with Communications Resources display to access the Create Communications Lines display, as shown in Figure 135 on page 170. Chapter 8. Selected Modeling Topics 169

190 Create Communications Lines IOPname...: IOAname...: Type changes, press Enter. CMB01 LIN21 Line resources with 0 lines are not created. Line Nbr of Line Speed Pct Line Frame Size Resource Lines (Kbit/sec) Oerhead (Bytes) Duplex *HALF Duplex: *HALF, *FULL Bottom F3=Exit F4=Prompt F6=Create line resource F12=Cancel Figure 135. Create Communications Lines 8. To change characteristics of a communications IOP or IOA or a line resource, select option 2 next to the element you want to change on the Work with Communications Resources display, shown preiously. Distribution of Characters Transferred Across Line Resources In order to show how much a line resource is being utilized, and whether you should redistribute some work, you can show the distribution of transaction characters, in a specific workload, transferred across communications line resources. Distribution is expressed as a relatie count as opposed to an percentage. For example, if the relatie count for line resource LINE0001 is 2 and for LINE0002 is 1, then twice as many characters are being transferred across LINE0001. Access the Specify Chars to Comm Line Resources display as show in Figure 136 on page 171, by pressing the F9 key on the Change or Create Workload display. 170 BEST/1 Capacity Planning Tool V5R1

191 Workload...: INTERACTIV Type changes, press Enter. Specify Chars to Comm Line Resources Nbr of Line Speed Line Resource Connect Lines (Kbit/sec) Relatie Count LANLINE1 *LAN WANLINE1 *WAN WANLINE2 *WAN F3=Exit F10=Set relatie counts to 1 F11=Show all line resources F12=Cancel F17=Set relatie counts to line capacity Bottom Figure 136. Specify Chars to Comm Line Resources A Line resource represents one or more communications lines and can be added or deleted from the Work with Communications IOP Features display. Line speed is represented in kilobits per second, and can be changed on the Change Communications Resource display. Relatie count is the relatie number of characters transferred across the communications line resource. The alues are relatie to each other and are not percentages. Relatie counts for WAN are calculated separate from the relatie counts for LAN. For example, Figure 136 shows all LAN traffic going across LANLINE1, and two-thirds of the WAN traffic going across WANLINE1. For example: You hae 5 actie jobs on WANLINE1, and you add 10 new jobs, split between WANLINE1 and WANLINE2. WANLINE1 has twice as many jobs as WANLINE2, represented by the relatie count of 2 to 1 (see Figure 136). Note: Communications actiity will be represented in your workloads regardless of which job classification category is used, because this actiity, in terms of characters transferred, will be apportioned across all transactions according to their relatie resource consumption. Communications Workload BEST/1 creates two types of communications workloads to represent communications actiity: For communications lines with traffic detected on them but no associated jobs, BEST/1 creates a workload named QCMN, which represents traffic on those lines. QCMN workload contains no I/O and CPU utilization. For workloads that show non-interactie actiity in a group, with no corresponding interactie actiity in that same group, BEST/1 creates a communications workload. The name of the workload is your workload name plus the letters QLAN or QWAN (QL or QW if the name is too long). Chapter 8. Selected Modeling Topics 171

192 Modeling Data Protection This workload contains only non-interactie actiity. BEST/1 creates this workload because it could not show non-interactie actiity for that group in your original workload without showing corresponding interactie actiity, which would misrepresent the actiity of your workload. The iseries serer offers seeral methods for protecting data and BEST/1 enables you to ealuate the relatie change to performance for each. This section describes how to model each protection method, what to expect for results, and compares each method. Then, particular modeling assumptions about the behaior of the 9337 Disk Array Subsystem are discussed. Comparing Performance for Data Protection Methods RAID (9337, 660x, 671x, or 690x Disk Array Subsystems), system checksum, and mirroring are discussed below. Performance for each method is compared with performance when no protection is used, followed by how the arious protection methods compare with each other. In all cases, BEST/1 changes I/O and CPU automatically, and the resulting predicted response times reflect the result of those changes. Mirroring Use the Work with BEST/1 Model, Configuration Menu, and Edit ASPs displays to mark each desired ASP with Data Protection of *MIRROR. Analyze the model. Each write I/O generates one additional mirror I/O. Therefore, the new results show an increase in the number of I/Os. An increase in CPU utilization for support of the additional I/Os might be seen. For systems with a large percentage of write I/Os, the change in I/O rate can be quite large. Note: High aailability dries that are part of mirrored ASPs do not cause extra mirror I/Os because they hae their own data protection. High Aailability Disk Array Subsystem Hardware Checksum High aailability dries are listed in Appendix H. BEST/1 Hardware Name Mapping on page 313. High aailability dries are typically 9337-xx2, 9337-xx7, 660x-070, 671x-070, and 690x-070. Each write I/O to one of these dries generates three additional checksum I/Os. Therefore, the results will show an increase in the number of I/Os. This increase is seen at the arm leel only because the IOP is not inoled in the checksum I/Os. CPU utilization is not affected because the checksum actiity is handled by the disk hardware. For systems with a large percentage of write I/Os, the change in I/O can be quite large. Relatie Changes for Data Protection Methods System checksum produces the largest increase in CPU because the system oerhead for checksum is fairly large. Mirroring can produce some increase in CPU, but it is usually fairly small. Hardware checksum does not affect CPU utilization at all. 172 BEST/1 Capacity Planning Tool V5R1

193 Hardware checksum increases the number of I/Os more than system checksum because all writes are protected by hardware checksum, but only permanent writes are protected by system checksum. Mirroring protects all writes, so it will increase I/O less than hardware checksum but might increase it more than system checksum, if there are a high proportion of temporary writes. Additional Modeling Considerations for 9337 Disk Array Subsystem You can consider or possibly change some of the BEST/1 assumptions about the behaior of 9337 Disk Array Subsystems. Read-Ahead Buffers The 9337 Disk Array Subsystems read-ahead buffers are designed to reduce I/O serice time for applications which access data sequentially. Wheneer a read is sericed at a deice, additional data is read ahead and placed in the buffer. When a future read request is made, the data might already be in the buffer and can be retrieed directly, without accessing the physical deice. The primary effectieness of this method depends on the data access patterns present in the applications running on the system. It also depends on the load placed on the 9337 Disk Array Subsystems because the read ahead phase is shortened or eliminated altogether anytime there is an I/O waiting to use that deice. BEST/1 does not explicitly model read-ahead actiity. Howeer, the hardware characteristics of the 9337 Disk Array Subsystem in the BEST/1 hardware table reflect some degree of read-ahead success. Thus, if a prediction is made from a non-read-ahead deice to a 9337 Disk Array Subsystem, the predicted results reflect only a small benefit from the read-ahead buffers. In actuality, faorable read data access patterns and not too heay use of the 9337 Disk Array Subsystem might show much better performance than that predicted. You could change the Serice Time (using the Work with Disk Resources display) to a more optimistic alue to approximate this effect. If a prediction is made from a 9337 Disk Array Subsystem enironment that performs well to a more heaily loaded enironment, the predicted results reflect continued benefit from the read-ahead buffers. In actuality, the increased load might not hae the same faorable data access patterns, or heay use of the 9337 Disk Array Subsystem could considerably curtail read-ahead buffer loading and show much worse performance than predicted. The user should obsere the measurements of current read-ahead success and possibly change the Serice Time (using Work with Disk Resources) to a more conseratie alue to approximate this effect. Write Assist Deice (WAD) The Write Assist Deice actually serices all incoming write I/Os. The actual write to a specific deice and the three checksum I/Os are all handled after the original write has occurred on the WAD and the program requesting the write has proceeded to other tasks. The WAD does not serice any other I/Os, such as reads or checksums so that it can proide good response to any incoming write. BEST/1 does not model the WAD explicitly, and it is not reported by the performance data. Therefore, in normal operations when the WAD is proiding good serice to writes, BEST/1 will report response time from the other seen arms as the write response time, which is possibly an oerstatement. Chapter 8. Selected Modeling Topics 173

194 If the WAD becomes oerloaded and bottlenecked due to a ery large number of incoming writes, BEST/1 does not predict the performance degradation specifically due to the WAD. Note: The WAD applies only to , 120, and 140 models. Write Cache The xx models employ a write cache designed to reduce I/O serice time for incoming writes by sericing these requests in controller memory (instead of at a rotating arm). This is a performance improement oer the preious architecture which instead used a Write Assist Deice (WAD) for this purpose. The cache offers additional potential for improed performance by freeing up the eighth arm for use as a normal data arm. The primary determinant of how much performance improement will be obsered is the proportion of writes to reads. BEST/1 does not explicitly model this proportion of writes effect. The serice time per I/O alue it uses from the hardware table (when analyzing arm upgrades or additional arms) assumes that about 1/3 of the I/Os are writes. If the actual proportion of writes is higher, BEST/1 will report less of an improement than would actually be obsered. If the actual proportion of writes is less than 1/3, BEST/1 will report more improement than would actually be achieed. To approximate these possible effects, you can change: The Serice Time to a higher or lower alue (using the Work with Disk Resources display), or alternatiely, before performing the arm upgrade. Change the seek time in the hardware table (using the Work with Drie Features display). Write Cache and RAID Considering the High Aailability models (9337-xx2, 9337-xx7, 660x-070, 671x-070, or 690x-070), another element of performance in addition to the proportion of writes, is relatie cache efficiency. Cache efficiency describes the relationship of incoming requests for write I/Os and how many physical writes this actually generates at an arm. If 1000 writes are directed to the deice, 1000 are written to the cache. If only 500 physical writes to the arm occur, this would result in a cache efficiency of 50%. A lower number of physical writes might occur because: Information is getting updated in the cache due to subsequent writes of the same information. Since the information is already in the cache, no physical I/O is inoled. When the cache becomes full, data has to be physically written to disk, and the related pieces of information located near each other on the disk are merged into one I/O. The relatie cache efficiency has a large effect on the RAID (hardware checksum) actiity at the arm, because only the physical writes generate physical checksum actiity. BEST/1 reduces the additional arm I/Os due to checksum actiity based on the current cache efficiency. For example, a alue of 50% would generate only half of the otherwise expected additional checksum I/O actiity. In actuality, arious workloads experience cache efficiencies ranging from about 5 to 95%. Thus, if the High Aailability models (9337-xx2, 9337-xx7, 660x-070, 671x-070, or 690x-070), arms and the workloads being modeled would produce a less faorable (lower) alue than the current alue for that controller, actual 174 BEST/1 Capacity Planning Tool V5R1

195 performance will be worse than predicted. If the workloads being modeled would produce a good (higher) alue, actual performance will be better than predicted. Cache efficiency alues are set in the following ways: If the model was created from performance data with 9337-xx2, 9337-xx7, 660x-070, 671x-070, or 690x-070), controllers, the cache efficiency is determined by the actual data. If the controller or disk IOA was created in the Work with Disk Resources display, the cache efficiency is taken from the hardware table alue. If the controller was copied from another controller, the cache efficiency alue is the same as the controller being copied. If the disk IOA was copied from another disk IOA, the cache efficiency alue is the same as the disk IOA being copied. In all cases, the alue BEST/1 uses in its analysis can be changed by doing a change on a 9337-xx2, 9337-xx7, 660x-070, 671x-070, or 690x-070 model, controller or disk IOP connected to one or more of these drie features, and changing the cache efficiency alue found on the display. This enables the user to perform sensitiity analysis. This includes trying a range of possible alues to see if this particular parameter substantially changes results for a particular study. If a specific alue can be estimated, use it to make a more releant analysis. Note: In all cases the hardware serice time per I/O BEST/1 uses (when arm upgrades or additions are analyzed) reflects a 1/3 write proportion and about 10% cache efficiency. To approximate different assumptions, you could change this Serice Time to a higher or lower alue depending on how you think your enironment differs by using the Work with Disk Resources display. Arm Failure BEST/1 assumes that all arms are operating. Arm failure of the WAD, or any other of the seen arms, can degrade performance but cannot be explicitly modeled. It can be estimated by seerely degrading the serice time of one of the arms, and degrading the serice time of the other arms in the set. Modeling Transitions Between CISC and RISC Support for processing differences between CISC-based CPU models and RISC-based CPU models can be diided into three primary areas: CPU time:a RISC processor has different types of instructions requiring different serice times compared to an CISC processor. Working set size:the page size of a RISC processor is 4KB and the page size of an CISC processor is 512 bytes. This will affect the amount of memory a transaction needs to run satisfactorily. Also, the program objects and working areas are larger on the RISC architecture. I/O:The page size of a RISC processor is 4KB and the page size of an CISC processor is 512 bytes. Although the number of IOs called by a transaction is decreased, the aerage size of each IO is bigger. For more information on CISC-to-RISC conersion factors, see Editing CISC-to-RISC Conersion Factors on page 105. CISC-to-RISC conersion factors relate to each of these areas and correspond to a specific workload type, like *NORMAL or *TRNBAT2. There are eight workload Chapter 8. Selected Modeling Topics 175

196 types with four normal ersion and four batchjob ersions. Each workload type has its own set of conersion factors which can be modified, saed, and read. The conersion factors are used when a workload has a different CPU architecture (*CISC or *RISC) than the CPU model in the model s configuration. When a workload s CPU architecture is *CISC and the CPU is a RISC model, then each transaction s CPU serice time is multiplied by the CPU serice time conersion factor during analysis. If the workload s CPU architecture is *RISC and the CPU is an CISC model, then each transaction s CPU serice time is diided by the CPU time conersion factor during analysis. The same general procedure applies to both the working set size and the number of I/Os for the transaction. *NORMAL and *BATCHJOB are the recommended settings for workload type. These types will refer to conersion factors which are expected to proide good results on most general purpose customer configurations. The *TRNxxxxx workload types represent specific workload characteristics, and are proided here for users who understand how they match the workloads in their model. Table 4. Workload Types Description Normal Batch General purpose workload type *NORMAL *BATCHJOB CPU intensie workloads where the CPU per *TRNNORM1 *TRNBAT1 I/O rate is high (see table) I/O intensie workloads where the CPU per *TRNNORM2 *TRNBAT2 I/O rate is low (see table) Deelopment workload where compile and debug is the bulk of the work *TRNNORM3 *TRNBAT3 To help you determine if a workload is CPU or I/O intensie, the following table illustrates some sample CPU per I/O alues for arious DASD response times. You can analyze your BEST/1 workload details to determine if any of your workload types should be changed. Calculate the CPU per I/O alue by diiding the CPU seconds per transaction by the total reads and writes per transaction. For example, if the workload has a single function executing 1 function per user, and the function defines a single transaction executing 1 transaction per function, and the transaction specifies 100 I/Os and 5 CPU seconds, then it has a CPU per I/O alue of.05 (5 / 100 =.05). If the aerage DASD response time for the configuration is 20 milliseconds, then this would indicate that *NORMAL is the correct setting for this workload. Note: If there is more than 1 transaction definition in the workload, then you will need to include the number of transactions in the calculation, so that the CPU per I/O alue is a weighted aerage. If 10 transactions hae a alue of.05 and 40 transactions hae a alue of.15, then the aerage alue is.13). Table 5. Sample CPU per I/O Values and The Appropriate Workload Type Setting Aerage I/O Response Time I/O Intensie *TRNNORM2 or *TRNBAT2 *NORMAL or *BATCHJOB CPU Intensie *TRNNORM1 or *TRNBAT1 10 msec less than to.040 greater than msec less than to.080 greater than msec less than to.120 greater than BEST/1 Capacity Planning Tool V5R1

197 A workload s CPU architecture can not be changed directly. Howeer, when you are saing a workload, you can specify the CPU architecture of the resulting workload. If the original workload is CISC-based and you are saing it as RISC-based, the following changes are made to all transitions in the resulting workload: CPU time becomes original CPU time multiplied by the CPU time conersion factor of the workload type. The count of each type of I/O becomes the corresponding original I/O count multiplied by the I/O counts conersion factor of the workload type. Working set size becomes original working set size multiplied by the working set size conersion factor of the workload type. Each paging coefficient becomes the corresponding original paging coefficient multiplied by the working set size conersion factor of the workload type raised to the power of the appropriate paging exponent. The paging behaior may change based on the current paging exponent and resulting working set size. RISC-based CPU models do not support system checksumming. When you hae system checksumming on one or more ASPs: If you change your CPU model to a RISC-based CPU, you will not be able to analyze your model. When you analyze with either recommendations or configuration changes and your CISC-based CPU needs to be upgraded, BEST/1 will not upgrade to a RISC-based CPU. The recommendations will indicate the RISC-based CPU which would hae been sufficient had system checksumming not been actie. Refer to Appendix J. Upgrading CISC-to-RISC Example on page 321 for an example that shows how to upgrade from CISC to RISC processor. Modeling ASPs and Journaling Modeling new auxiliary storage pools (ASPs) with BEST/1 requires that you change the configuration and assign workload actiity to the new ASP. How much I/O to assign to the ASP requires careful consideration. You can change the configuration by working with the disk resources and changing some of the disk resources to reside in the new ASP. If you are planning to buy new dries, create and assign them to the new ASP. Existing ASPs that were present during your data collection should already be represented properly in your model. You can assign workload actiity by working with the workloads. Editing the workloads causes actiity to occur in the new ASP. You can then use the F10 function key to assign I/Os to ASPs. Careful consideration is needed when deciding how much of a workload s I/O should be modeled into the different ASPs. This decision always depends on each customer s unique situation. The example used here is based on reading Chapter 8 of the AS/400 Performance Capabilities Reference. In this guide, the journaling oerhead stated for the RTW workload is 12%. If you look at the detailed measurements you can see that the effect is on both CPU and DASD utilization. This example uses this as a guide for adjusting the BEST/1 workloads that cause journaling to occur. Chapter 8. Selected Modeling Topics 177

198 Because work is being added to the system, first add the work to the workload, then make the I/O to ASP assignments. The transaction details within the workload needs to be changed. Use the following formulas for each transaction detail: New CPU = Old CPU * 1.12 New Sync DB write = Old Sync DB write + Old Async DB write To determine the new I/O to ASP settings, you need to use the following formulas to understand what percent of the writes for the workload will go to the new ASP. These formulas require you to add all writes from all transactions in a workload. OLD wkld writes = Old Sync DB write + Old Async DB write + Old Sync non-db write + Old Async non-db write NEW wkld writes = New Sync DB write + Old Async DB write + Old Sync non-db write + Old Async non-db write %I/0 to OLD ASPs = Old wkld writes/new wkld writes %I/O to NEW ASPs = 1 - (Old wkld writes/new wkld writes) The last two numbers in the example will guide you when you use the F10 function key against the workload to specify I/O to ASPs. This example shows increasing the I/O and CPU to account for journaling. The extra I/O was considered to be Sync writes. Sync writes can cause exceptional wait which can be added to the transaction details. A note of interest is when an application is journaling, the journal I/O is done synchronous, but counted as asynchronous by the job and in the performance data file. Commitment control is another consideration. Specifying commitment control moes the additional I/O from Sync to Async, but also adds approximately one (1) additional Sync write per commit checkpoint, and carries a 21% CPU increase oer the base case (an extra 10% oerhead on top of journaling). Modeling Release Leel Performance Improements From one release to the next there are improements made in the operating system that can affect performance. With most of the changes being made in the operating system, it is unlikely that one system enironment will yield the same improements as the next enironment. Therefore, the improement factor is a alue accessible to the user to best match the improement factor with the specific enironment being analyzed. The alue is accessed with the Change CPU Model display using F14 (Specify performance improements) as shown in Figure 137 on page BEST/1 Capacity Planning Tool V5R1

199 Change CPU Model CPU model...: 2156 Min/Max storage size (MB)...: Type information, press Enter. System unit , 9404, 9406 Architecture... *RISC *CISC, *RISC Relatie performance (B10 = 1.0): Normal Serer (Blank if not Serer) Number of processors... 4 Currently aailable... N Y=Yes, N=No Family... *POWERSRV Name Upgrade to family... *POWERSRV *NONE, name Minimum Maximum Disk IOPs Multifunction IOPs More... 13=Specify connections to comm IOPs F14=Specify performance improements F16=Specify connections to multifunction IOPs F24=More keys Figure 137. Change CPU Model Display Figure 138 shows the alid releases for the selected CPU along with the improement factor from the preious release. It should be noted that improement factors are additie. That means if the system is currently at release N and the analysis is for release N+2, the tool first calculates performance at release N+1 and uses that result as input to calculate performance at N+2. Specify Performance Improements CPUModel...: 2156 System Unit...: 9406 Type changes, press Enter. Specify the percentage of improement when a release leel is run, as compared to the preious leel. Release Performance Leel Improement Pct V3R6M0 0 V3R7M0 20 V4R1M0 15 V4R2M0 0 F3=Exit F12=Cancel Figure 138. Specify Performance Improements Display This function proides a mechanism to show how the same workload performs on a different release of the operating system. It is important to note that some workloads benefit more from the improements of a release than other workloads. Chapter 8. Selected Modeling Topics 179

200 Therefore, the default alues represent aerage improements between releases for aerage customer enironments. Appendix K. Tuning Performance Improement Factors on page 335 discusses fine tuning the improement numbers based on specific enironment characteristics for each release. Note: It is recommended that the improement numbers be changed only with a strong understanding of the enironment being analyzed. To model the effects of installing a new release, change the CPU configuration information: 1. On the configuration menu select option 1 (Change CPU and other resource alues). 2. Change the Release leel alue to the release to be modeled. When the model is analyzed, the improement factor is applied to all the workloads in the model. 180 BEST/1 Capacity Planning Tool V5R1

201 Chapter 9. Capacity Planning Examples The capacity planning examples shown in the following sections demonstrate some of the ways you can use the capacity planning function: Creating models from performance data Adding throughput to the current workload Projecting future system needs as a result of oerall system growth and indiidual workload growth Adding new applications to a known workload Graphing results Adding a newly announced CPU to the hardware characteristics file If you are working with data from preious releases, it is recommended that you conert the base performance data and then re-create the associated models. This will ensure that all the functional enhancements made to BEST/1 are aailable in the resulting models. Performance Tips When Doing What-if...? Analysis BEST/1 proides thorough analysis and recommendations. As a result, some of its functions use significant CPU utilization and CPU elapsed time. These functions are: Create model. On the Edit Job Classifications display, the query of the QAPMJOBS file (performance monitor) or the QAPMJOBL file (Collection Serices), for classifications such as Job type. This is accessed by pressing F9 (Display alues from data) on the Edit Job Classifications display. Analyze current model and gie recommendations from the Work with Model display. Growth analysis, using F17 (Analyze multiple points) from arious report displays. Growth analysis, using option 7 (Specify workload growth and analyze model) on the Work with BEST/1 Model display. You can shorten the time and CPU seconds used for measured data by collecting data continuously. When doing growth analysis, use as few periods as is really necessary. Fie periods is a good standard. Performance Tip #1. Use an iseries serer with floating point hardware for best results. Performance Tip #2. Do not do any modeling on a production system where performance is already an issue. If you must run the capacity planning tool on a heaily utilized system, reschedule your time or job to hae minimal effect. For example, use off-peak time, when interactie users are not using the system. Performance Tip #3. If you plan to run in an enironment where multiple users are performing BEST/1 modeling at the same time, you should do some benchmarking to determine acceptability of the What-if...? elapsed time. Copyright IBM Corp. 1998,

202 Performance Tip #4. If you are building a model from measured data on a heaily loaded system, consider selecting a subset of the total data collection time span. You may create and analyze the model in batch mode. Performance Tip #5. BEST/1 does some of its analysis on a per workloadbasis. By using the combine workload function on the Work with Workloads display, you can shorten the analysis time. Performance Tip #6. Use the performance CL command ANZBESTMDL, to read a model, perform growth analysis, and sae a model, all done in batch mode. Performance Tip #7. If pool actiity leels are unlikely to be reached or if limiting the number of jobs in a pool is not necessary, set the actiity leel of any such pool to 0. This is a special alue indicating there is no limit to the number of jobs running in the pool. Creating a BEST/1 Model from Performance Data To create a BEST/1 model from performance data, follow these steps: 1. Enter the performance data member you want to use to create the model. 2. Select the time interal in the performance data member. Items 3, 4, 5, and 6 are skipped if you hae selected option 5 (Create BEST/1 model from performance data) on the BEST/1 main menu. 3. Choose the job classification category you want to use to classify the jobs in the data into workloads. 4. For each job in the data specify to which workload it will belong. Multiple workloads can be specified at one time. Jobs which are not assigned to a workload are automatically assigned to the QDEFAULT workload. 5. Optionally, supply a transaction definition for non-interactie jobs. The default transaction definition for non-interactie jobs is that 100 logical disk I/Os is a transaction. 6. Sae the completed job classification to create models from different time interals. 7. Confirm the creation of the BEST/1 model. 182 BEST/1 Capacity Planning Tool V5R1

203 Chapter 9. Capacity Planning Examples 183

204 Creating a Model from Existing Performance Data Basic The following scenario shows the short method for creating a model from existing performance data: 1. Start BEST/1 for the *BASIC user leel using one of the following methods: Type STRBEST USRLVL(*BASIC) Use the menu interface. You are shown the (STRBEST) command causes the BEST/1 for the AS/400 disclaimer. Press the Enter key. Initialization takes place, and the BEST/1 for the AS/400 display appears. BEST/1 for the AS/400 Select one of the following: 1. Work with BEST/1 models 5. Create BEST/1 model from performance data 10. Work with results 50. General information and tutorial 60. More BEST/1 options Selection or command ===>1 F3=Exit F4=Prompt F9=Retriee F12=Cancel Figure 139. Creating a BEST/1 Model Basic 2. Select option 5 (Create BEST/1 model from performance data). Press Enter. The Create Model from Performance Data display appears. 184 BEST/1 Capacity Planning Tool V5R1

205 Create BEST/1 Model from Performance Data Type choices, press Enter. Use *SLTHOUR to select an hour-long time period or use *SLTITV to select select first and last interal of a one to two hour time period. The time period selected should be representatie of your peak processing actiity. Performance data: Member... Name, Library... QPFRDATA Name Start time... *SLTHOUR Time, *FIRST, *SLTHOUR, *SLTITV Start date... *FIRST Date, *FIRST Stop time... *LAST Time, *LAST Stop date... *LAST Date, *LAST F3=Exit F4=Prompt F12=Cancel 3. Identify the performance data member you want to analyze. Press F4 for a list of aailable members in the selected library. In this example, press F4 in the Member field, and the Select Performance Member display appears. Library... QPFRDATA Name Type option, press Enter. 1=Select Select Performance Member Opt Member Text Date Time 1 MAR10AM MAR. 10, morning actiity 03/11/93 14:33:06 _ FEB24PMPerformance monitor, Feb 24 pm 02/24/93 12:17:33 _ FEB24AMPerformance monitor, Feb 24 am 02/24/93 10:17:26 _ RTCOMB70 RTCOMB70 Trace 02/15/93 12:17:17 Bottom F3=Exit F5=Refresh F12=Cancel F15=Sort by name F16=Sort by text F19=Sort by date and time 4. Type a 1 in the Opt column next to the member you want to use (in this case, MAR10AM) and press the Enter key. You return to the Create BEST/1 Model from Performance Data display. Chapter 9. Capacity Planning Examples 185

206 Create BEST/1 Model from Performance Data Type choices, press Enter. Use *SLTHOUR to select an hour-long time period or use *SLTITV to select select first and last interal of a one to two hour time period. The time period selected should be representatie of your peak processing actiity. Performance data: Member... MAR10AM Name, Library... QPFRDATA Name Start time... *SLTHOUR Time, *FIRST, *SLTHOUR, *SLTITV Start date... *FIRST Date, *FIRST Stop time... *LAST Time, *LAST Stop date... *LAST Date, *LAST F3=Exit F4=Prompt F12=Cancel 5. The recommended way to specify a time period is to use the *SLTHOUR option. Howeer, you can also use the *SLTITV to exactly specify which interals to include. Alternatiely, you can specify an exact start and stop time. This example uses *SLTHOUR. Press Enter. The Select Hour-Long Period display appears. Select Hour-Long Period Library...: QPFRDATA Performance member..: MAR10AM Type option, press Enter. Select an hour-long period representatie of your peak processing actiity. Each time period is the sum of a one-hour performance monitor data collection. The time stamp shown is that of the last interal in the time period. 1=Select ---Transaction--- --CPU Util--- I/Os per Sec Opt Date Time Count Rsp Time Total Inter Sync Async 1 03/10/93 10:37: _ 03/10/93 10:52: _ 03/10/93 11:07: _ 03/10/93 11:22: _ 03/10/93 11:32: Bottom F3=Exit F12=Cancel F15=Sort by interal F16=Sort by count F17=Sort by rsp time F18=Sort by total CPU util F19=Sort by total I/Os Figure 140. Select Sample Periods 6. The periods on the display are sorted by CPU utilization with the first period already selected. Use the busiest period to model the worst case scenario. Using this approach shows what needs the system must address during the heaiest 186 BEST/1 Capacity Planning Tool V5R1

207 period of demand. After pressing Enter, the Confirm Creation of BEST/1 Model display appears. Type choices, press Enter. Confirm Creation of BEST/1 Model Model name... Name Library... BEST1 Name Text... M AR. 10, morning actiity Replace... N Y=Yes, N=No F12=Cancel 7. Gie the model a name. The text defaults to the text of the performance member. Press Enter. The model creation is done interactiely. Once the model is created, it is analyzed. The Work with BEST/1 Model menu appears. The menu shown here is for the basic user leel. Work with BEST/1 Model Performance data...: QPFRDATA (MAR10AM0 Model/Text...: BEST1MODEL MAR. 10, morning actiity Select one of the following: 7. Specify workload growth and analyze model 10. Configuration menu 11. Work with results 50. General information and tutortial More... Selection or command ===> F3=Exit F4=Prompt F9=Retriee F12=Cancel F15=Sae current model F17=Analyze with ANZBESTMDL F22=Calibrate model F24=More keys Model has been created and analyzed Figure 141. Work with BEST/1 Model Menu Basic Scenario You may require more control oer how your model is created from performance data, such as needing to specify how jobs are classified into workloads, or defining non-interactie transactions. If this is the case, then use the adanced scenario. Chapter 9. Capacity Planning Examples 187

208 Creating a Model from Existing Performance Data Adanced The following scenario shows a more detailed scenario for creating a model from existing performance data: 1. Issuing the Start BEST/1 (STRBEST) command causes the BEST/1 for the AS/400 disclaimer to appear. Press the Enter key. Initialization takes place, and the BEST/1 for the AS/400 display appears. Note: When you start BEST/1 from the menu interface, you are using the user leel of *BASIC. To access the adanced options, you must use the command interface. 2. Select 1 (Work with BEST/1 models) and press the Enter key. BEST/1 for the AS/400 Select one of the following: 1. Work with BEST/1 models 5. Create BEST/1 model from performance data 10. Work with results 50. General information and tutorial 60. More BEST/1 options Selection or command ===>1 F3=Exit F4=Prompt F9=Retriee F12=Cancel The Work with BEST/1 Models display appears. 188 BEST/1 Capacity Planning Tool V5R1

209 Work with BEST/1 Models Library... QPFRDATA Name Type options, press Enter. 1=Create 3=Copy 4=Delete 5=Work with 6=Print 7=Rename Opt Model Text Date Time 1 FIRSTMODEL _ RRC040 RAMP-C on a D50 02/15/93 17:58:48 _ RAMP passthru source (RAMP-C) 02/11/93 19:36:30 _ BATCHMODEL High priority batch 02/05/93 20:31:43 _ MODELTEST Model test 02/04/93 21:38:35 Command ===> F3=Exit F4=Prompt F5=Refresh F9=Retriee F12=Cancel F15=Sort by model F16=Sort by text F19=Sort by date and time Bottom 3. Type a 1 (Create) in the Opt column. Type the name of your model in the Model column. In this example, type the name FIRSTMODEL. Press the Enter key. The Create BEST/1 Model display appears. Note: You may create a model from any combination of measured data, predefined workloads, or user-defined workloads. Select one of the following: Create BEST/1 Model 1. Create from performance data 2. Create from predefined and user-defined workloads Selection 1 F12=Cancel 4. To create the model from the performance data, select 1 (Create from performance data) and press the Enter key. The Create BEST/1 Model from Performance Data display appears. Chapter 9. Capacity Planning Examples 189

210 Create BEST/1 Model from Performance Data Model...: FIRSTMODEL Type choices, press Enter. Use *SLTHOUR to select an hour-long time period or use *SLTITV to select select first and last interal of a one to two hour time period. The time period selected should be representatie of your peak processing actiity. Text.... Performance data: Member... Name, Library... QPFRDATA Name Start time... *SLTHOUR Time, *FIRST, *SLTHOUR, *SLTITV Start date... *FIRST Date, *FIRST Stop time... *LAST Time, *LAST Stop date... *LAST Date, *LAST F3=Exit F4=Prompt F12=Cancel 5. Identify the Performance Data member and the interal you wish to analyze. Press F4 for a list of aailable members in the selected library. Optionally, enter a description in the Text field. In this example, select performance member MAR10AM from the QPFRDATA library by pressing F4 in the Performance member field. 6. The Select Performance Member display appears. Library... QPFRDATA Name Type option, press Enter. 1=Select Select Performance Member Opt Member Text Date Time 1 MAR10AM MAR. 10, morning actiity 03/11/93 14:33:06 _ FEB24PMPerformance monitor, Feb 24 pm 02/24/93 12:17:33 _ FEB24AMPerformance monitor, Feb 24 am 02/24/93 10:17:26 _ RTCOMB70 RTCOMB70 Trace 02/15/93 12:17:17 Bottom F3=Exit F5=Refresh F12=Cancel F15=Sort by name F16=Sort by text F19=Sort by date and time 7. Type a 1 in the Opt column next to the member you want to use (in this case, MAR10AM) and press the Enter key. You return to the Create Model from Performance Data display. 190 BEST/1 Capacity Planning Tool V5R1

211 Create BEST/1 Model from Performance Data Model...: FIRSTMODEL Type choices, press Enter. Use *SLTHOUR to select an hour-long time period or use *SLTITV to select select first and last interal of a one to two hour time period. The time period selected should be representatie of your peak processing actiity. Text.... MAR. 10, morning actiity Performance data: Member... MAR10AMName, Library... QPFRDATA Name Start time... *SLTHOUR Time, *FIRST, *SLTHOUR, *SLTITV Start date... *FIRST Date, *FIRST Stop time... *LAST Time, *LAST Stop date... *LAST Date, *LAST F3=Exit F4=Prompt F12=Cancel The recommended way to specify a time period is to use the *SLTHOUR option. Howeer, you can also use the *SLTITV option to exactly specify which interals to include. Alternatiely, you can specify an exact start and stop time. This example uses *SLTHOUR. Press Enter. The Select Hour-Long Period display appears. Select Hour-Long Period Library...: QPFRDATA Performance member..: MAR10AM Type option, press Enter. Select an hour-long period representatie of your peak processing actiity. Each time period is the sum of a one-hour performance monitor data collection. The time stamp shown is that of the last interal in the time period. 1=Select ---Transaction--- --CPU Util--- I/Os per Sec Opt Date Time Count Rsp Time Total Inter Sync Async 1 03/10/93 10:37: _ 03/10/93 10:52: _ 03/10/93 11:07: _ 03/10/93 11:22: _ 03/10/93 11:32: Bottom F3=Exit F12=Cancel F15=Sort by interal F16=Sort by count F17=Sort by rsp time F18=Sort by total CPU util F19=Sort by total I/Os Figure 142. Select Sample Periods The periods on the display are sorted by CPU utilization with the first period already selected. Because it is recommended to use the busiest period, press Enter. The Classify Jobs menu appears. Chapter 9. Capacity Planning Examples 191

212 Classify Jobs Select one of the following: 1. Use default job classification 2. Classify jobs into workloads 3. Use existing job classifications Selection 2 F3-Exit F12=Cancel 8. Select 2 (Classify jobs into workloads) and press the Enter key. Option 1 uses the default classification, through which four workloads are created representing interactie, non-interactie, Client Access, and QDEFAULT. Option 3 reuses a preiously saed job classification. The Specify Job Classification Category display appears. Specify Job Classification Category Type choice, press Enter. Category =User ID 2=Job type 3=Job name 4=Account code 5=Job number 6=Subsystem 7=Pool 8=Control unit 9=Comm line 10=Functional area F3=Exit F12=Cancel 9. Select the category that will be used to classify jobs into workloads. For further information on these categories, see the online help information for this display. In this example, type a 2 in the Opt column to select the Job Type category, and press the Enter key. The Edit Job Classifications display appears. 192 BEST/1 Capacity Planning Tool V5R1

213 Edit Job Classifications Enter workload names and category alues which are assigned to each workload, press Enter. Jobs with unassigned alues become part of workload QDEFAULT. Workload Job Type Workload Job Type Workload Job Type F3=Exit F9=Display alues from data F12=Cancel To display alues from the performance data, press F9 More... The Edit Job Classifications display lets you assign jobs to workloads if you already know the job types you wish to use. If you do not know the job type, press F9 (Display alues from data) to see a display that shows the list of job types that were actie during the collection of performance data. Note: Each job in the system can belong only to one workload. Unassigned jobs will be included in workload QDEFAULT. 10. Display alues from data by pressing F9. The Assign Jobs to Workloads display appears. Assign Jobs to Workloads Workload... INTER Type options, press Enter. Unassigned jobs become part of workload QDEFAULT. 1=Assign to aboe workload 2=Unassign Number of CPU I/O Opt Workload Job Type Transactions Seconds Count 1 *INTERACTV _ *LIC *PTHRUTGT _ *BATCH _ *AUTOSTART _ *EVOKE *CLIENTAC _ *WRITER *PTHRUSRC _ *SYSTEM *DDM More. F3=Exit F12=Cancel F15=Sort by workload F16=Sort by job type F17=Sort by transactions F18=Sort by CPU seconds F19=Sort by I/O count Use this display to assign jobs to workloads. For each workload you want to create, enter its name in the Workload field and then select the jobs that correspond to it by typing a 1 in the Opt field. Press the Enter key. Repeat this process until no more workloads need to be created. Chapter 9. Capacity Planning Examples 193

214 Note: We recommend that you do not explicitly select *LIC jobs so the resources used by those jobs are automatically distributed proportionally to the other workloads. This is only true for *LIC jobs. In this example, create two workloads corresponding to INTERACTIVE and BATCH. QDEFAULT will contain the unassigned jobs. Jobs with types *INTERACTV, *PTHRUTGT, *PTHRUSRC, *CLIENTAC4 and *DDM will be assigned to a workload called INTER. Jobs with a job type of *BATCH will be assigned to a workload called BATCH, and the remaining jobs will be assigned to QDEFAULT. Note: Values that hae unprintable characters will not be included in this list and will be automatically assigned to workload QDEFAULT during the creation of a model. 11. Type the workload name INTER in the Workload field. Type a 1 in the Opt column for the *INTERACTV, *PTHRUTGT, *PTHRUSRC, *CLIENTAC4, and *DDM job types and press the Enter key. The Workload column will change to INTER for the job types that were assigned. Repeat the same procedure for the workload BATCH. Type the workload name BATCH in the Workload field. Type a 1 in the Opt column next to *BATCH job type and press the Enter key. The Workload column will change to BATCH for the job type that was assigned. Press the Enter key. The Specify Paging Behaiors display appears. From the Specify Paging Behaiors display you can choose the paging Type option, press Enter. Specify Paging Behaiors Workload QDEFAULT BATCH INTER Paging Behaior *GENERIC *GENERIC *GENERIC F3=Exit F4=Prompt F12=Cancel Bottom behaior you want to assign to all transactions within each workload. The choices are *GENERIC, *OFFICE, *RAMPC, and *SQLRTW. After you choose the appropriate paging behaior, press the Enter key. The Define Non-Interactie Transactions display appears. 194 BEST/1 Capacity Planning Tool V5R1

215 Define Non-Interactie Transactions Job classification category...: Job Type Type choices, press Enter. ---Actiity Counted as Transaction--- Total Transactions Workload Type Quantity when Type = *NONE QDEFAULT *LGLIO BATCH *LGLIO INTER *LGLIO Bottom Type: F3=Exit *LGLIO, *CMNIO, *CPUSEC, *PRINT, *NONE F12=Cancel Use of this display is optional. BEST/1 classifies all jobs running in the system as either interactie or non-interactie. The number of transactions issued by the interactie jobs is a measurable quantity that is carried into the model. Howeer, the same is not true for non-interactie jobs. To model the load that these jobs place on system resources, BEST/1 needs to know how many non-interactie transactions these jobs create. When system tasks are spread out oer the workloads, interactie jobs contain non-interactie components. Therefore, when interactie jobs grow, resource consumption of non-interactie jobs also grows. The number of non-interactie jobs is also dependent upon the job category that is chosen. The sole function of this display is to tell BEST/1 what measurable actiity performed by the non-interactie jobs should be used to equate to a non-interactie transaction. This association can be made on the basis of: Logical I/Os issued Communications I/Os issued CPU seconds Print lines Actual number of transactions When *NONE is selected, you are asked to supply an actual count for the number of non-interactie transactions created by the workload. If no changes are made, BEST/1 associates each 100 logical I/O issued by a non-interactie job with a single non-interactie transaction. This means that the Display Workload Report display shows many non-interactie transactions based on this default. A logical I/O occurs when a program does a read or write operation to a file. 12. Press the Enter key to accept the defaults. The Sae Job Classification Member display appears. Chapter 9. Capacity Planning Examples 195

216 Sae Job Classification Member Change alues if desired, press Enter. Member... BYTYPE Name Library... BEST1 Name Text... Job Classification by job type Replace... N Y=Yes, N=No F12=Cancel 13. Type BYTYPE in the Member field and optional text in the Text field. Press the Enter key to sae the job classification member. Once saed, a job classification member can be reused with other performance data. The Confirm Creation of BEST/1 Model display appears. Type choices, press Enter. Confirm Creation of BEST/1 Model Model... FIRSTMODEL Name Library... BEST1 Name Text... Model used in the documentation Replace... N Y=Yes, N=No Jobname... CRTBESTMDL Name, *JOBD Job description... QPFRJOBD Name, *NONE, *USRPRF Library... QPFR Name, *LIBL, *CURLIB F12=Cancel 14. Press the Enter key to submit the batch job that will create the model. The Work with BEST/1 Models display reappears with the message that the job has been submitted. Once the model is created, it appears on the Work with BEST/1 Models display. Note: Press F5 (Refresh) to refresh the display, if you do not see the newly created model displayed in the model list. 196 BEST/1 Capacity Planning Tool V5R1

217 Library... BEST1 Name Work with BEST/1 Models Type options, press Enter. 1=Create 3=Copy 4=Delete 5=Work with 6=Print 7=Rename Opt Model Text Date Time _ FIRSTMODEL Model used in the documentation 03/10/93 09:17:29 _ RRC040 RAMP-C on a D50 02/15/93 17:58:48 _ RAMP passthru source (RAMP-C) 02/11/93 19:36:30 _ BATCHMODEL High priority batch 02/05/93 20:31:43 _ MODELTEST Model test 02/04/93 21:38:35 Command ===> F3=Exit F4=Prompt F5=Refresh F9=Retriee F12=Cancel F15=Sort by model F16=Sort by text F19=Sort by date and time Adding Throughput to an Existing System Note: The following three examples all begin with a BEST/1 model specifying B60 for CPU Model to demonstrate some of the BEST/1 capacity planning functions. Only the second example can be followed with the basic user leel. If you plan to increase the number of display stations/jobs, but plan on running the same workload per user, there are seeral steps you need to take to plan for the increased throughput. First, collect your performance data to measure your current system performance. Data is collected about the internal response time, throughput, resource utilizations, and system configuration parameters. For more information on performance data collection, see the Performance oeriew topic in the iseries Information Center. Next, use the CRTBESTMDL or STRBEST command to build a BEST/1 model based on the collected data. The capacity planning model is used in predicting system performance for projected needs. For more information on building a BEST/1 model, see Creating a BEST/1 Model from Performance Data on page 182. Then follow these steps to add throughput to the current system: 1. Enter the STRBEST command to begin working with BEST/1, the capacity planning tool. The display that shows the BEST/1 for the AS/400 disclaimer appears. 2. Press the Enter key. The BEST/1 for the AS/400 display appears. Chapter 9. Capacity Planning Examples 197

218 BEST/1 for the AS/400 Select one of the following: 1. Work with BEST/1 models 5. Create BEST/1 model from performance data 10. Work with results 50. General information and tutorial 60. More BEST/1 options Selection or command ===> 1 F3=Exit F4=Prompt F9=Retriee F12=Cancel 3. On this display, select option 1 to work with BEST/1 models. Press the Enter key. The Work with BEST/1 Models display appears. Library... BEST1 Name Work with BEST/1 Models Type options, press Enter. 1=Create 3=Copy 4=Delete 5=Work with 6=Print 7=Rename Opt Model Text Date Time 5 FIRSTMODEL Model used in the documentation 03/10/93 09:17:29 _ RRC040 RAMP-C on a D50 02/15/93 17:58:48 _ RAMP passthru source (RAMP-C) 02/11/93 19:36:30 _ BATCHMODEL High priority batch 02/05/93 20:31:43 _ MODELTEST Model test 02/04/93 21:38:35 Command ===> F3=Exit F4=Prompt F5=Refresh F9=Retriee F12=Cancel F15=Sort by model F16=Sort by text F19=Sort by date and time 4. In this example, the model FIRSTMODEL is used, which consists of three workloads (BATCH, INTER, and QDEFAULT). On this display, type a 5 (Work with) in the Option column next to FIRSTMODEL. Press the Enter key. The Work with BEST/1 Model display appears. 198 BEST/1 Capacity Planning Tool V5R1

219 Work with BEST/1 Model Performance data...: QPFRDATA (MAR10AM) Model/Text...: FIRSTMODEL Model used in the documentation Select one of the following: 1. Work with workloads 2. Specify objecties and actie jobs 5. Analyze current model 6. Analyze current model and gie recommendations 7. Specify workload growth and analyze model 10. Configuration menu 11. Work with results More... Selection or command ===> 2 F3=Exit F4=Prompt F9=Retriee F12=Cancel F15=Sae current model F17=Analyze using ANZBESTMDL F22=Calibrate model F24=More keys Model FIRSTMODEL has been read 5. To iew the current workload objecties, select 2 (Specify objecties and actie jobs) and press the Enter key. The Specify Objecties and Actie Jobs display appears. Model/Text: Type changes, press Enter. Specify Objecties and Actie Jobs Workload Actie ---Interactie---- Non-inter Workload Connect Type Jobs Rsp Time Thruput Thruput BATCH *LOCAL *NORMAL INTER *LOCAL *NORMAL QDEFAULT *LOCAL *NORMAL F3=Exit F11=Show all quantities F12=Cancel F15=Sort by connect type F19=Work with Workloads Bottom This display shows that the BATCH and INTER workloads were measured at 1 and 35 non-lan local jobs, respectiely. 6. To erify that you hae a good model, compare measured results with those predicted by BEST/1. To do this, press the Enter key to display the Work with BEST/1 Model display again. Select option 5 (Analyze current model). Press the Enter key. After the system ealuates the model, the Work with Results display appears. Chapter 9. Capacity Planning Examples 199

220 Work with Results Type options, press Enter. 5=Display 6=Print Opt Report Name 5 Measured and predicted comparison _ Analysis Summary _ Recommendations _ Workload Report _ ASP and Disk Arm Report _ Disk Resources Report _ Main Storage Pool Report _ Communications Resource Report _ All of the aboe Bottom F3=Exit F12=Cancel F14=Select saed results F15=Sae current results F18=Graph current results F19=Append saed results Model has been analyzed 7. Type a 5 (Display) next to Measured and predicted comparison and press Enter. The Measured and Predicted Comparison display appears. If the Measured and predicted comparison row is not aailable on the Work with Results display, then type a 5 (Display) next to Analysis Summary to display summary statistics. Press Enter. Display Analysis Summary display appears. M Display Analysis Summary CPU Model / release leel...: B60 V2R3M0 Main Storage...: 48 B Quantity Predicted Util CPU...: Disk IOPs...: Disk ctls...: Disk arms...: Local WS ctls...: 3.1 More... Non-interactie Interactie CPU utilization %...: Transactions per Hour...: Local response time (seconds)...: LAN response time (seconds)...:.0.0 WAN response time (seconds)...: Bottom Performance estimates -- Press help to see disclaimer. F3=Exit F10=Re-analyze F11=Measured and predicted comparison F12=Cancel F15=Configuration menu F17=Analyze multiple points F24=More keys Press F11 to compare measured and predicted alues. The Measured and Predicted Comparison display appears. Note: The measured alues for the LAN IOA and WAN IOA fields are blank because this information is not aailable from the performance data. 200 BEST/1 Capacity Planning Tool V5R1

221 Measured and Predicted Comparison Measured Predicted Total CPU util...: Disk IOP util...: Disk arms util...: Disk IOs per second...: Multifunction IOP util...: Disk IOA util...: LANIOAutil...: 8.7 WANIOAutil...: 25.1 Integrated PC Serer IOA util...: LANIOPutil...:.0.0 LAN line util....:.0.0 WANIOPutil...: WAN line util....: Interactie CPUUtil...: Internal response time...: Transactions per hour....: Non-interactie throughput...: Bottom F3=Exit F6=Print F9=Work with spooled files F12=Cancel F17=Calibrate response time Do not expect the modeled system results to be exactly the same as those measured. If some of the BEST/1 assumptions are not being met, or if actiity is not properly recorded in the performance database, (for instance, file locking, internal waits, and so on), the predicted interactie response time may differ from the measured response time. If the predicted response time is lower than that measured, you may press F17 (Calibrate response time) to let BEST/1 add the internal delays that were not captured in the measurement data. These delays will be added as exceptional wait to the transaction details. A model is considered calibrated if resource utilization and workload throughputs are within 10% of measured alues, and workload response times are within 20% or 0.5 seconds of measured alues at throughputs below saturation. By default, the CRTBESTMDL command distributes workload I/O to ASPs in proportion to the ASP I/O count. If some of your workload I/O is relatiely skewed toward specific ASPs, you should change I/O distribution across ASPs on the Specify I/Os to ASPs display (press F10 on the Create Workload display). 8. Press the Enter key or F3 to return to the Work with Results display to select other options and get more information on the performance of the system resources. The Work with Results display appears. Chapter 9. Capacity Planning Examples 201

222 Printed report text... Work with Results Type options, press Enter. 5=Display 6=Print Opt _ Report Name Measured and predicted comparison Analysis Summary Recommendations Workload Report ASP and Disk Arm Report Disk Resources Report Main Storage Pool Report Communications Resources Report All of the aboe Bottom F3=Exit F12=Cancel F14=Select saed results F15=Sae current results F18=Graph current results F19=Append saed results F24=More keys 9. Once you hae erified that the predicted results reflect the measured results, press F3 to go back to the Work with BEST/1 Model display to change the workload objecties to add additional work. Select option 2 (Specify objecties and actie jobs). Press the Enter key. The Specify Objecties and Actie Jobs display appears. Specify Objecties and Actie Jobs Model/Text: FIRSTMODEL Model used in the documentation Type changes, press Enter. Workload Actie ----Interactie---- Non-inter Workload Connect Type Jobs Rsp Time Thruput Thruput BATCH *LOCAL *NORMAL INTER *LOCAL *NORMAL QDEFAULT *LOCAL *NORMAL F3=Exit F11=Show all quantities F12=Cancel F15=Sort by connect type F19=Work with Workloads Bottom 10. To determine the effect of increasing the number of local jobs in the INTER workload from 35 to 50, type 50 in the Actie Jobs column and press the Enter key. The Work with BEST/1 Model display appears. 202 BEST/1 Capacity Planning Tool V5R1

223 Work with BEST/1 Model Performance data...: QPFRDATA (MAR10AM) Model/Text...: FIRSTMODEL Model used in the documentation Select one of the following: 1. Work with workloads 2. Specify objecties and actie jobs 5. Analyze current model 6. Analyze current model and gie recommendations 7. Specify workload growth and analyze model 10. Configuration menu 11. Work with results More... Selection or command ===> 6 F3=Exit F4=Prompt F9=Retriee F12=Cancel F15=Sae current model F17=Analyze using ANZBESTMDL F22=Calibrate model F24=More keys 11. Select option 6 (Analyze current model and gie recommendations) and press the Enter key. The Work with Results display appears after the model has been analyzed. Type options, press Enter. 5=Display 6=Print Work with Results Opt Report Name _ Measured and predicted comparison 5 Analysis Summary _ Recommendations _ Workload Report _ ASP and Disk Arm Report _ Disk Resources Report _ Main Storage Pool Report _ Communications Resources Report _ All of the aboe Bottom F3=Exit F12=Cancel F14=Select saed results F15=Sae current results F18=Graph current results F19=Append saed results Model has been analyzed 12. Type a 5 in the Opt column next to Analysis Summary to display the Analysis Summary report. Press the Enter key. The Display Analysis Summary display appears. Chapter 9. Capacity Planning Examples 203

224 Display Analysis Summary M CPU Model / release leel....: B60 V2R3M0 Main Storage...: 48 B Quantity Predicted Util CPU...: Disk IOPs...: Disk ctls...: Disk arms...: Local WS ctls....: 3.1 More... Interactie Non-interactie CPU utilization %...: Transactions per Hour...: Local response time (seconds)...:.0.0 LAN response time (seconds)...: WAN response time (seconds)...: Bottom Performance estimates -- Press help to see disclaimer. F3=Exit F10=Re-analyze F11=Measured and predicted comparison F12=Cancel F15=Configuration menu F17=Analyze multiple points F24=More keys This time, howeer, the proposed workload rather than the original measured workload is modeled. The configured hardware does not gie the required performance. The predicted IOP utilization of SI03, SI04, and SI07 exceeds the utilization guideline of 50% as indicated on the Display Recommendations display. The lines are highlighted to indicate the areas where objecties are not being met. Press the Enter key or F12 to return to the Work with Results display, and type a 5 in the Opt column next to Recommendations to see the ealuator recommendation. The Display Recommendations display appears. Display Recommendations ***** Analysis Exceptions ***** Disk IOP utilization of for IOP SI03 exceeds objectie of Disk IOP utilization of for IOP SI04 exceeds objectie of Disk IOP utilization of for IOP SI07 exceeds objectie of ***** Analysis Recommendations ***** Create IOP(s) Change CPU model to E50 Change storage size to 64 MB Create IOP(s) Create disk ctl(s) Create arms(s) Bottom Performance estimates -- Press help to see disclaimer. F3=Exit F10=Change to recommended configuration and re-analyze F12=Cancel F15=Configuration menu F17=Analyze multiple points F24=More keys The ealuator message shows that upgrading the processor and increasing main storage, along with some IOP changes, are required to achiee a balanced system. 204 BEST/1 Capacity Planning Tool V5R1

225 13. To accept the changes, press F10. The changes are made to the existing configuration, and the analysis is run again. 14. When the analysis is complete, the Work with Results display appears. Type options, press Enter. 5=Display 6=Print Work with Results Opt Report Name _ Measured and predicted comparison 5 Analysis Summary _ Recommendations _ Workload Report _ ASP and Disk Arm Report _ Disk Resources Report _ Main Storage Pool Report _ Communications Resources Report _ All of the aboe F3=Exit F12=Cancel F14=Select saed results F15=Sae current results F18=Graph current results F19=Append saed results F24=More keys Configuration has been changed Bottom 15. Type a 5 next to Analysis Summary to display the effects of the new analysis. Press the Enter key. The Display Analysis Summary display appears. Display Analysis Summary M CPU Model / release leel....: E50 V2R3M0 Main Storage...: 64 B Quantity Predicted Util CPU...: Disk IOPs...: Disk ctls...: Disk arms...: Local WS ctls...: 3.1 More... Interactie Non-interactie CPU utilization %...: Transactions per Hour...: Local response time (seconds)...:.0.0 LAN response time (seconds)...:.5.0 WAN response time (seconds)...:.7.0 Bottom Performance estimates -- Press help to see disclaimer. F3=Exit F10=Re-analyze F11=Measured and predicted comparison F12=Cancel F15=Configuration menu F17=Analyze multiple points F24=More keys By changing the CPU model to E50 and the main storage to 64MB, along with the IOP changes, the workload objecties in this example are met. 16. Press the Enter key to return to the Work with Results display. Type a 5 next to All of the aboe to iew all of the reports. Press the Enter key. 17. The Display Analysis Summary display appears. Press the Enter key. Chapter 9. Capacity Planning Examples 205

226 18. The Display Recommendations display appears. Press the Enter key. The Display Workload Report display appears. Display Workload Report Period: Analysis CPU Thruput Response Times (Secs) Workload Type Util per Hour Internal Local LAN WAN BATCH INTER INTER QDEFAULT Type: 1=Interactie, 2=Non-interactie, 3-*BATCHJOB Performance estimates -- Press help to see disclaimer. F3=Exit F10=Re-analyze F11=Response time details F12=Cancel F13=Preious period F14=Next period F24=More keys Bottom Note: Non-interactie throughput is based on the default alue of 100 logical I/Os equal one transaction. You may change this alue on the Define Non-Interactie Transactions display. 19. Press the Enter key. The Display ASP and Disk Arm Report display appears. Display ASP and Disk Arm Report Period: Analysis I/Os Disk Disk Subsystem Aerage ASP Arms per Sec Pct Busy Msecs per I/O Performance estimates -- Press help to see disclaimer. F3=Exit F10=Re-analyze F11=Display Disk Resources report F12=Cancel F15=Configuration menu F17=Analyze multiple points F24=More keys Bottom 20. Press the Enter key. The Display Disk Resources Report display appears. 206 BEST/1 Capacity Planning Tool V5R1

227 Display Disk Resources Report Period: Analysis I/Os Disk Disk Subsystem Aerage Resource Type Arms per Sec Util Pct Busy Msecs per I/O CMB01 *MFIOP SI04 *IOP Bottom Performance estimates -- Press help to see disclaimer. F3=Exit F10=Re-analyze F11=Display ASP and Disk Arm report F12=Cancel F15=Configuration menu F17=Analyze multiple points F24=More keys 21. Press the Enter key. The Display Main Storage Pool Report display appears. Display Main Storage Pool Report Period: Analysis Pool Act Size Ineligible -----Ag Number----- Sync Reads ID Ll (KB) Wait (sec) Actie Ineligible per Sec Performance estimates -- Press help to see disclaimer. F3=Exit F10=Re-analyze F12=Cancel F15=Configuration menu F17=Analyze multiple points F18=Specify objecties F24=More keys Bottom 22. Press the Enter key. The Display Comm Resources Report display appears. Chapter 9. Capacity Planning Examples 207

228 Display Comm Resources Report Period: Analysis Oerhead Rsp Time per Nbr of Line Speed Resource Type Util Util Trans (Sec) Lines (Kbit/sec) CC01 *IOP 15.9 LANLINE1 *LINE CC02 *IOP.0 WANLINE1 *LINE CMB01 *MFIOP 5.8 LIN19 *IPCS 7.2 D27DBF0101 *LINE LIN21 *IOA 29.1 CMN08 *LINE LIN25 *IOA 21.1 QESLINE *LINE F3=Exit F10=Re-analyze F12=Cancel F15=Configuration menu F17=Analyze multiple points F18=Specify objecties F24=More keys Bottom Projecting Future System Needs as a Result of Oerall System Growth Follow these steps to plan your future system needs: 1. To determine what system upgrades are required to sustain a projected growth rate, select option 7 (Specify workload growth and analyze model) on the Work with BEST/1 Model display and press the Enter key. Work with BEST/1 Model Performance data...: QPFRDATA (MAR10AM) Model/Text...: FIRSTMODEL Model used in the documentation Select one of the following: 1. Work with workloads 2. Specify objecties and actie jobs 5. Analyze current model 6. Analyze current model and gie recommendations 7. Specify workload growth and analyze model 10. Configuration menu 11. Work with results More... Selection or command ===> 7 F3=Exit F4=Prompt F9=Retriee F12=Cancel F15=Sae current model F17=Analyze using ANZBESTMDL F22=Calibrate model F24=More keys 2. The Specify Growth of Workload Actiity display appears. 208 BEST/1 Capacity Planning Tool V5R1

229 Specify Growth of Workload Actiity Type information, press Enter to analyze model. Determine new configuration... Y Y=Yes, N=No Periods to analyze Period 1... Period 1 Name Period 2... Period 2 Name Period 3... Period 3 Name Period 4... Period 4 Name Period 5... Period 5 Name Percent Change in Workload Actiity Workload Period 1 Period 2 Period 3 Period 4 Period 5 *ALL Bottom F3=Exit F11=Specify growth by workload F12=Cancel F13=Display periods 6 to 10 F17=Analyze using ANZBESTMDL 3. Specify whether you want BEST/1 to configure a system that can handle the projected load by typing Y (Yes) in the Determine new configuration field. If you type N (No), BEST/1 shows what the performance of the current system will be. Note: When BEST/1 determines a new configuration, the model at the end of the analysis contains your current configuration and not the new configuration. 4. Identify the number of periods you would like to analyze. In this example, enter a 4 (to represent the four quarters of the calendar year). Name these periods Q1, Q2, Q3, and Q4. Enter an estimate for your processing growth rate in each of these four periods. Base this estimate on reasons such as: Gross sales Acquisitions of, or mergers with, other companies Addition of new processes or functions Number of employees (especially those who use data processing equipment) 5. Enter a growth rate of 10% for each of the four periods. Do this by entering 10.0 in Period 1 (Q1), 10.0 in Period 2 (Q2), 10.0 in Period 3 (Q3), and 10.0 in Period 4 (Q4). The growth for each period is cumulatie. Note: If you are interested in analyzing the effect of growth for a particular workload, press F11. This action will cause the display to include all the workloads in the model. Enter the desired percentage change for each workload. Periods with no alue indicate that the workload s actiity has not changed from the preious period. Negatie alues may be used to represent a reduction in workload actiity from the preious period. In addition to studying future growth, you can use this display to perform a sensitiity analysis of the current system by Typing N in the Determine new configuration field Proiding growth rates with a mid-point of 0, to do a fie point sensitiity analysis Chapter 9. Capacity Planning Examples 209

230 For example, if you want growth rates of -20, -10, 0, 10, and 20, enter -20, 12.5, 11.1, 10, and 9 for Periods 1 5. These are approximate alues compared to your current actiity and reflect cumulatie growth. Specify Growth of Workload Actiity Type information, press Enter to analyze model. Determine new configuration... Y Y=Yes, N=No Periods to analyze Period 1... Q1 Name Period 2... Q2 Name Period 3... Q3 Name Period 4... Q4 Name Period 5... Period 5 Name Percent Change in Workload Actiity Workload Period 1 Period 2 Period 3 Period 4 Period 5 *ALL Bottom F3=Exit F11=Specify growth by workload F12=Cancel F13=Display periods 6 to 10 F17=Analyze using ANZBESTMDL 6. Press the Enter key. After the model has been analyzed, the Work with Results display appears. Type options, press Enter. 5=Display 6=Print Work with Results Opt Report Name _ Measured and predicted comparison 5 Analysis Summary _ Recommendations _ Workload Report _ ASP and Disk Arm Report _ Disk Resources Report _ Main Storage Pool Report _ Communications Resources Report _ All of the aboe F3=Exit F12=Cancel F14=Select saed results F15=Sae current results F18=Graph current results F19=Append saed results F24=More keys Model has been analyzed Bottom 7. Enter a 5 next to Analysis Summary to display the results of the ealuation. Press the Enter key to see the Display Analysis Summary display. 210 BEST/1 Capacity Planning Tool V5R1

231 Display Analysis Summary Stor CPU -Disk IOPs -Disk Ctls -Disk Arms Period CPU Model (MB) Util Nbr Util Nbr Util Nbr Util Q1 E Q2 E Q3 E Q4 E Inter Non-Inter Inter Rsp Time-- CPU CPU Period Local WAN Util Trans/Hr Util Trans/Hr Q Q Q Q F3=Exit F10=Re-analyze F11=Alternatie iew F12=Cancel F15=Configuration menu F17=Analyze multiple points F24=More keys Bottom Bottom 8. The Display Analysis Summary display shows the hardware required to sustain the 10% growth rate specified for the four periods selected (Q1 through Q4). Hardware changes from one growth period to the next are highlighted on the display. In this example, BEST/1 calculated that the CPU model B60 must be upgraded to an E50 in Q1 to sustain the 10% growth rate. Graphing Results When a model is analyzed, BEST/1 creates a set of results that can be displayed or printed in report format, or displayed graphically. These results, which can pertain to a single period or to multiple periods if you specified a workload growth scenario, can be saed to an external file member by pressing F15 (Sae current results) from the Work with Results display. Graphs can be created for the current model analysis or from the results saed from a preious analysis. Notes: 1. Graphs are displayed as character graphs on nongraphics terminals. Howeer, when a graph is printed or plotted, the result is graphics output. 2. You cannot graph IOA utilizations. Displaying Graphs from the Current Model To display graphs from the current model analysis, follow these steps: Chapter 9. Capacity Planning Examples 211

232 Work with Results Printed report text... Type options, press Enter. 5=Display 6=Print Opt _ Report Name Measured and predicted comparison Analysis Summary Recommendations Workload Report ASP and Disk Arm Report Disk Resources Report Main Storage Pool Report Communications Resources Report All of the aboe Model has been analyzed F3=Exit F12=Cancel F14=Select saed results F15=Sae current results F18=Graph current results F19=Append saed results F24=More keys 1. From the Work with Results display, press F18 (Graph current results). The Work with Graph Formats display appears. Library... QPFR Name Work with Graph Formats Type option, press Enter. 1=Create 2=Change 3=Copy 4=Delete 5=Display graph 6=Print graph format 7=Rename 8=Print graph 17=Plot graph Opt Member Text Date Time _ DIOSBYASP Aerage Disk I/O Rate by ASP 03/04/93 14:01:34 5 RSPBYPRD Workload Response Time by Period 02/19/93 14:43:30 _ THRUBYRSP Line: Intrctie Rsponse Time s. Thruput 01/30/93 11:13:49 _ BSYBYASP Bar: Aerage Disk Utilization by ASP 01/30/93 11:12:16 _ WIOSBYPRD Workload I/O Rate by Period 01/28/93 09:44:25 _ BSYBYIOP Disk IOP Utilization 01/28/93 09:44:25 _ THRUBYWKL Interactie Throughput by Workload 01/28/93 09:44:25 _ CPUBYWKL CPU Utilization by Workload 01/28/93 09:44:24 Bottom Command ===> 4 F3=Exit F4=Prompt F5=Refresh F6=Select results for oerlay F9=Retriee F12=Cancel F15=Sort by member F24=More keys 2. Type a 5 (Display graph) in the Opt column next to RSPBYPRD and press the Enter key. A display of the graph appears. 212 BEST/1 Capacity Planning Tool V5R1

233 Press Enter to continue F3=Exit F12=Cancel F16=Print GDF Note: If the scale of the graph appears to be high, you can change the axis range, by using the Change Axis Range display. Press F13 (Change axis range) on the Create or Change Graph Format displays to access the Change Axis Range display. See Changing the Axis Range on page 238 for more information. Displaying Graphs from a Preious Model To display graphs from a preious model analysis, follow these steps: 1. From the BEST/1 for the AS/400 display, select option 10 (Work with results). The Select Results Member display lists members containing preiously saed results. Note: You can sae results of an analysis by pressing F15 (Sae current results) on the Work with Results display. Chapter 9. Capacity Planning Examples 213

234 Library... BEST1 Name Type option, press Enter. 1=Select Select Results Member Opt Member Text Date Time 1 RESULTS3 Upgrade to D80 03/10/93 18:44:25 _ RESULTS2 Upgrade to D60 03/09/93 16:17:01 _ RESULTS1 Original B60 03/09/93 12:02:37 Bottom F3=Exit F5=Refresh F12=Cancel F15=Sort by member F16=Sort by text F19=Sort by date and time 2. Type a 1 in the Opt column next to RESULTS3. The Work with Results display is shown. 3. Press F18 (Graph current results). The Work with Graph Formats display is shown. Library... QPFR Name Work with Graph Formats Type option, press Enter. 1=Create 2=Change 3=Copy 4=Delete 5=Display graph 6=Print graph format 7=Rename 8=Print graph 17=Plot graph Opt Member Text Date Time _ DIOSBYASP Aerage Disk I/O Rate by ASP 03/04/93 14:01:34 _ RSPBYPRD Workload Response Time by Period 02/19/93 14:43:30 _ THRUBYRSP Line: Intrctie Rsponse Time s. Thruput 01/30/93 11:13:49 _ BSYBYASP Bar: Aerage Disk Utilization by ASP 01/30/93 11:12:16 _ WIOSBYPRD Workload I/O Rate by Period 01/28/93 09:44:25 _ BSYBYIOP Disk IOP Utilization 01/28/93 09:44:25 _ THRUBYWKL Interactie Throughput by Workload 01/28/93 09:44:25 5 CPUBYWKL CPU Utilization by Workload 01/28/93 09:44:24 Bottom F3=Exit F4=Prompt F5=Refresh F6=Select results for oerlay F9=Retriee F12=Cancel F15=Sort by member F24=More keys 4. Type a 5 in the Opt column next to CPUBYWKL and press the Enter key. A display of the graph appears. 214 BEST/1 Capacity Planning Tool V5R1

235 Creating Your Own Graphs Graph formats are templates or outlines used by the graphics routines of BEST/1 to display graphs in a user-defined format. BEST/1 proides a set of predefined graph formats for you to use. These graph formats can be modified and new formats can be added by performing the following steps: 1. Library... BEST1 Name Work with Graph Formats Type option, press Enter. 1=Create 2=Change 3=Copy 4=Delete 5=Display graph 6=Print graph format 7=Rename 8=Print graph 17=Plot graph Opt Member Text Date Time 1 NEWGRAPH _ DIOSBYASP Aerage Disk I/O Rate by ASP 03/04/93 14:01:34 _ RSPBYPRD Workload Response Time by Period 02/19/93 14:43:30 _ THRUBYRSP Line: Intrctie Rsponse Time s. Thruput 01/30/93 11:13:49 Bottom F3=Exit F4=Prompt F5=Refresh F6=Select results for oerlay F9=Retriee F12=Cancel F15=Sort by member F24=More keys Chapter 9. Capacity Planning Examples 215

236 2. On the Work with Graph Formats display type a 1 (Create) in the Opt column and the name NEWGRAPH in the Member field. Press the Enter key. The Create Graph Format display is shown. Graph format...: NEWGRAPH Type choices, press Enter. Create Graph Format Text... *BLANK Title... Disk IOP Utilization Subtitle... *BLANK Graph type... *LINE *LINE, *BAR, *PIE, *SURFACE Area fill... N Y=Yes, N=No X-axis: Variable.. F4 for list Title... Y-axis: Variable.. F4 for list Title... Bottom F3=Exit F4=Prompt F6=Print graph F12=Cancel F13=Change axis range F17=Plot graph 3. Type the title to display on the graph (for example, Disk IOP Utilization) in the Title field. You may choose line, bar, pie, or surface for the Graph type field. To choose the X-axis ariable, press F4 in the Variable field for the list of ariables. The Select X-Axis Variable display appears. See Appendix G. Graphic Support Variables for a list of the graphic support ariables. Type option, press Enter. 1=Select Select X-Axis Variable Opt Variable ID Variable Text _ 1 Period _ 10 CPU Util _ 11 Workload CPU Util _ 12 Disk Busy _ 13 Disk IOP Busy _ 20 Workload Inter Trans/hr _ 21 Workload Non-inter Trans/hr _ 22 Total Trans/hr _ 23 Workload I/Os per Sec _ 24 Disk I/Os per Sec _ 25 Disk IOP I/Os per Sec _ 26 Actie Jobs _ 30 Rsp Time by Workload _ 31 Disk Rsp Time per I/O _ 32 Aerage Response Time F12=Cancel More Type a 1 in the Opt column next to the ariable you would like to select and press the Enter key. You return to the Create Graph Format display. 5. Repeat the aboe steps for the Y-axis ariable. When you hae completed filling in the fields, press the Enter key. 216 BEST/1 Capacity Planning Tool V5R1

237 6. The Sae Graph Format Member display is shown. Type Disk IOP Utilization in the Text field and press the Enter key to sae the graph format to the specified library. Change alues if desired, press Enter. Sae Graph Format Member Member... NEWGRAPH Name Library... BEST1 Name Text... Disk IOP Utilization Replace... N Y=Yes, N=No F12=Cancel The Work with Graph Formats display appears again. Library... BEST1 Name Work with Graph Formats Type option, press Enter. 1=Create 2=Change 3=Copy 4=Delete 5=Display graph 6=Print graph format 7=Rename 8=Print graph 17=Plot graph Opt Member Text Date Time _ NEWGRAPH Disk IOP utilization 03/10/93 12:01:34 _ DIOSBYASP Aerage Disk I/O Rate by ASP 03/04/93 14:01:34 _ RSPBYPRD Workload Response Time by Period 02/19/93 14:43:30 _ THRUBYRSP Line: Intrctie Rsponse Time s. Thruput 01/30/93 11:13:49 Bottom F3=Exit F4=Prompt F5=Refresh F6=Select results for oerlay F9=Retriee F12=Cancel F15=Sort by member F24=More keys 7. Type a 5 (Display graph) in the Opt column next to the newly created graph format to iew the graph. You may change the graph format by entering a 2 in the Opt column. Chapter 9. Capacity Planning Examples 217

238 Adding a Newly Announced CPU to the Hardware Characteristics File This example shows how to add a fictitious newly announced CPU (the 2172) to the list of CPUs recognized by BEST/1. The 2172 CPU is a 9406 System Unit similar to the 2136 in terms of the I/O deices to which it can connect, but capable of haing up to 640MB of main storage with a 25% improement in processor performance. Note: The 2172 is only an example model; it does not exist. BEST/1 assigns CPU power to specific models using the Relatie Internal Processor Performance rating as measured by IBM. In some cases, the rating for a specific CPU model or feature will differ from other published reports which quote the Relatie Performance of the system based on specific benchmarks. 1. From the BEST/1 for the AS/400 display select option 60 (More BEST/1 options) and press the Enter key. BEST/1 for the AS/400 Select one of the following: 1. Work with BEST/1 models 5. Create BEST/1 model from performance data 10. Work with results 50. General information and tutorial 60. More BEST/1 Options Selection or command ===> 60 F3=Exit F4=Prompt F9=Retriee F12=Cancel 2. The More BEST/1 Options display appears. 218 BEST/1 Capacity Planning Tool V5R1

239 More BEST/1 Options Select one of the following: 1. Work with job classification members 2. Work with workload members 3. Work with configuration members 4. Work with hardware members 5. Work with results members 6. Work with analysis parameters members 10. Hardware characteristics menu 11. Edit Analysis Parameters 20. Conert MDLSYS files 21. Migrate S/36 workload 51. Moing from MDLSYS to BEST/1 Selection or command ===> 10 F3=Exit F4=Prompt F9=Retriee F12=Cancel 3. Select option 10 (Hardware characteristics menu) and press the Enter key. The Hardware Characteristics display appears. Select one of the following: Hardware Characteristics 1. Work with CPU models 2. Work with Disk IOP features 3. Work with Disk Drie features 4. Work with Communications IOP features 5. Work with Communications line speeds 6. Work with Multifunction IOP features 7. Work with IOA features Selection or command ===> 1 F3=Exit F4=Prompt F9=Retriee F12=Cancel F14=Replace with saed hardware characteristics F24=More keys 4. Select option 1 (Work with CPU models) and press the Enter key. The Work with CPU Models display appears. Chapter 9. Capacity Planning Examples 219

240 Work with CPU Models Type option, press Enter. 1=Create 2=Change 3=Copy 4=Delete 7=Rename System Archi- -Relatie Perf-- Number of Max Stor Opt CPU Model Unit tecture Normal Serer Processors (MB) B *CISC *RISC *RISC *RISC S *RISC S *RISC S *RISC S *RISC S *RISC S *RISC S *RISC S *RISC S *RISC More... F3=Exit F12=Cancel Note: The first column under CPU Model appears for PowerPC AS processors and for 2xxx CISC-based processors. The Work with CPU Models display shows a list of CPUs recognized by BEST/1. 5. Type a 3 (Copy) in the Opt column next to 2136 to copy a CPU model and press the Enter key. 6. The Copy CPU Model display appears. Copy CPU Model To copy, type New Name, press Enter. Current name...: 2136 New name F3=Exit F12=Cancel 7. Type 2172 in the New name field and press the Enter key. The Work with CPU Models display appears. 220 BEST/1 Capacity Planning Tool V5R1

241 Work with CPU Models Type option, press Enter. 1=Create 2=Change 3=Copy 4=Delete 7=Rename System Archi- -Relatie Perf-- Number of Max Stor Opt CPU Model Unit tecture Normal Serer Processors (MB) B *CISC *RISC *RISC *RISC S *RISC S *RISC S *RISC S *RISC S *RISC S *RISC S *RISC S *RISC S *RISC F3=Exit F12=Cancel More Locate the 2172 and type a 2 (Change) in the Opt column next to 2172 and then press the Enter key. The Change CPU Model display appears. Change CPU Model CPU model...: 2172 Min/Max storage size (MB)...: Type information, press Enter. Currently aailable... Y Y=Yes, N=No Relatie performance (B10 = 1.0): Interactie Database... Processor Number of processors... 1 Maximum logical partitions... 1 Family... *FROM_ANY *FROM_ANY, name Upgrade to family... *INVADER *NONE, *ANY, name Architecture... *RISC *CISC, *RISC More... Minimum Maximum Disk IOPs Multifunction IOPs F3=Exit F6=Specify storage sizes F9=Specify connections to disk IOPs F11=Specify connections to disk dries F12=Cancel F24=More keys This display allows you to change a CPU model and specify its components. 9. In the Relatie Performance field, type (approximately 25% faster than a 2136). This number indicates the performance of this CPU relatie to that of a B10 CPU model. 10. Press F6 (Specify storage sizes). The Specify Storage Sizes for CPU Model display appears. Chapter 9. Capacity Planning Examples 221

242 Specify Storage Sizes for CPU Model CPUModel...: 2172 System Unit...: 9406 Type options, press Enter. 1=Create 4=Delete Opt Size (MB) Opt Size (MB) Opt Size (MB) F3=Exit F12=Cancel Bottom This display is used to enter the alid storage increments for this CPU model. The display shows that 128, 192, 256, 320, 384, 448, and 512 are existing storage sizes from the copied CPU model. Type a 1 (Create) in the Opt column and 576 in the Size column to add 576MB as a storage size and press the Enter key. Do the same to add 640MB as a storage size. 11. Press the Enter key to return to the Change CPU Model display. Change CPU Model CPU model...: 2172 Min/Max storage size (MB)...: Type information, press Enter. Currently aailable... Y Y=Yes, N=No Relatie performance (B10 = 1.0): Interactie Database... Processor Number of processors... 1 Maximum logical partitions... 1 Family... *FROM_ANY *FROM_ANY, name Upgrade to family... *INVADER *NONE, *ANY, name Architecture... *RISC *CISC, *RISC More... Minimum Maximum Disk IOPs Multifunction IOPs F3=Exit F6=Specify storage sizes F9=Specify connections to disk IOPs F11=Specify connections to disk dries F12=Cancel F24=More keys 12. Because this CPU has a maximum number of 0 disk IOPs, it is not necessary to press F9 to specify connections to disk IOPs. Because this CPU must connect to one multifunction IOP, you can now specify the multifunction IOP features that can be connected to this CPU. Press F16 (Specify connections to multifunction IOPs). You see the specify Connections to Multifunction IOPs display. This display shows the multifunction IOP features that are currently 222 BEST/1 Capacity Planning Tool V5R1

243 connected to this CPU, and enables you to add and delete connections to IOP features. CPUModel...: 2172 System Unit...: 9406 Specify Connections to Multifunction IOPs Type changes, press Enter. To remoe, set Maximum Number to 0. IOP Maximum Drie Feature --Max IOAs-- Bus Currently Feature Number Mixing Allowed DIOA CIOA Type Aailable Y 4 9 *SPD Y Mixing Allowed, Currently Aailable: Y=Yes, N=No Bottom F3=Exit F9=Add IOP feature F12=Cancel 13. If you need to add an IOP feature, press F9 (Add IOP feature) to select an additional IOP feature. (In this example, we do not need to add an IOP feature.) The Select Multifunction IOP Feature display appears. Type a 1 in the Opt field next to the IOP feature you want to add and press the Enter key. The Specify Connections to Multifunction IOPs display appears again showing the new IOP feature. Press the Enter key to return to the Change CPU Model display. Type option, press Enter. 1=Select Select Multifunction IOP Feature ----Serice Times (Msecs)---- IOP Per LAN Per WAN --Max IOAs-- Bus Currently Opt Feature Per I/O Frame Frame DIOA CIOA Type Aailable *SPD N *SPD N *SPD N *SPD N *SPD Y *SPD Y *SPD N *SPD N *SPD N *SPD N *SPD Y Currently Aailable: Y=Yes, N=No Bottom F12=Cancel 14. From the Change CPU Model display, press F11 (Specify connections to disk dries). The Specify Connections to Disk Dries display appears. This display Chapter 9. Capacity Planning Examples 223

244 shows the disk drie features that are connected to this CPU and enables you to type the maximum number of arms that can be connected. Specify Connections to Disk Dries CPUModel...: 2172 System Unit...: 9406 Type information, press Enter. Drie Max Number Drie Max Number Drie Max Number Feature of Arms Feature of Arms Feature of Arms Bottom F3=Exit F12=Cancel 15. You can change the maximum number of arms, or accept the alues on this display. Press the Enter key to accept the alues return to the Change CPU Model display. 16. From the Change CPU Model display, press F13 (Specify Connections to Comm IOPs). The Specify Connections to Comm IOPs display appears. On this display you can specify the maximum number of LAN and WAN IOPs, and communications lines that can be connected to this CPU. Specify Connections to Comm IOPs CPUModel...: 2172 System Unit...: 9406 Type changes, press Enter. To remoe a connection to a Comm IOP feature, set Max Lines to 0. This will not affect the characteristics of the Comm IOP feature. Max number of LAN IOPs... 8 Max number of WAN IOPs Max number of WAN lines IOP Max Line Speed IOP Currently Feature Lines Minimum Maximum Type Aailable *LAN Y *LAN Y *LAN Y *WAN Y Currently Aailable: Y=Yes, N=No More.. F3=Exit F9=Add IOP feature F12=Cancel 17. From the Change CPU Model display, press F14 (Specify performance improements). The Specify Performance Improements display appears. 224 BEST/1 Capacity Planning Tool V5R1

245 Specify Performance Improements CPUModel...: 2172 System Unit...: 9406 Type changes, press Enter. Specify the percentage of improement when a release leel is run, as compared to the preious leel. Release Leel V4R1M0 V4R2M0 Performance Improement Pct 0 0 F3=Exit F12=Cancel On this display you can specify the performance improement this CPU model experiences for each release leel which it can run. 18. When you hae completed typing the information, press the Enter key twice. The Work with CPU Models display appears and the CPU model is created. Work with CPU Models Type option, press Enter. 1=Create 2=Change 3=Copy 4=Delete 7=Rename System Archi- -Relatie Perf-- Number of Max Stor Opt CPU Model Unit tecture Normal Serer Processors (MB) B *CISC *RISC *RISC *RISC S *RISC S *RISC S *RISC S *RISC S *RISC S *RISC S *RISC S *RISC S *RISC More... F3=Exit F12=Cancel 19. Press F3 to return to the Hardware Characteristics display. Chapter 9. Capacity Planning Examples 225

246 Select one of the following: Hardware Characteristics 1. Work with CPU models 2. Work with Disk IOP features 3. Work with Disk Drie features 4. Work with Communications IOP features 5. Work with Communications line speeds 6. Work with Multifunction IOP features 7. Work with IOA features Selection or command ===> F15=Sae current hardware characteristics F24=More keys 20. To sae the changed hardware characteristics, press F15 (Sae current hardware characteristics). The Sae Hardware Characteristics display appears. Change alues if desired, press Enter. Sae Hardware Characteristics Member... DEFAULT Name Library... BEST1 Name Text... Replace... N Y=Yes, N=No F12=Cancel 21. In the Member field, type the member name. In the Library field, type the library in which to sae the new hardware characteristics. Press the Enter key. The new hardware characteristics are saed. You can read in this saed hardware characteristics member by pressing F14 on the Hardware Characteristics display and selecting the member. If you want to read this hardware characteristics member during initialization of the program, the member must be named DEFAULT. You must specify the name of the library (if the library is not current) when using the STRBEST command, for example, STRBEST BEST BEST/1 Capacity Planning Tool V5R1

247 Note: When BEST/1 is initializing, it checks for the existence of both hardware and analysis parameter members, which are both called DEFAULT in the current BEST/1 library. The current BEST/1 library is either the library which was typed as a parameter when using the STRBEST command, or your current library if no library was specified. If either of the members do not exist in the current library, the production ersion contained in QPFR will be read instead. Leaing the Current Model Once you hae completed the capacity planning analysis for the current model, press F3 (Exit) on the Work with BEST/1 Models display. The Exit BEST/1 Model display appears. Type choice, press Enter. Exit BEST/1 Model Option... _ 1=Sae and exit 2=Exit without saing 3=Resume F12=Cancel To sae the model you hae created, type a 1 (Sae and exit) and press the Enter key. To exit without saing the model, type a 2 (Exit without saing) and press the Enter key. To return to the Work with BEST/1 Models type a 3 (Resume) and press the Enter key. If you choose to sae the model, the Sae Current Model display appears. Chapter 9. Capacity Planning Examples 227

248 Change alues if desired, press Enter. Sae Current Model Sae to Model member: Member... FIRSTMODEL Name Library... BEST/1 Name Text... June 10 morning, claims actiity Replace... N Y=Yes, N=No Externally described member information: Sae... N Y=Yes, N=No Member... *MEMBER Name, *MEMBER Library... *LIB Name, *LIB Text... Replace... *REP Y=Yes, N=No, *REP F12=Cancel You can sae the model to a BEST/1 internal file and optionally, as an externally defined file (EDF). Type your choices and press the Enter key. Note: To sae a model during the capacity planning analysis, press F15 (Sae current model) on the Work with BEST/1 Model or Create BEST/1 Model displays. 228 BEST/1 Capacity Planning Tool V5R1

249 Chapter 10. Printing Model Reports and Graphs Printed Reports Once you hae analyzed a model you can obtain results which can be iewed as reports or graphs. The following sections describe these features. The Work with Results display has options to display or print reports when a model is analyzed. BEST/1 includes the appropriate model text in the spooled file. You can access the files from the Work with Spooled Files display. The User Data field contains either the model or results member name. Table 6. Spool Names for Printed Reports Spool name Report name B1SUMRPT Analysis Summary Report B1RECRPT Exceptions and Recommendations Report B1WKLRPT Workload Detail Report B1ASPRPT ASP and Disk Arm Report B1IOPRPT Disk Resources Report B1POOLRPT Main Storage Pool Report B1CMNRPT Communications Resource Report B1MEASRPT Measured and Predicted Comparison Report B1RESULTS All reports (*ALL) Note: If you created the model from Performance Data, then the Measured and Predicted Comparison report can also be produced, but only while you are working with the model. Sample Printed Output You can also print out the model details separately. This identifies the workload, function, and transaction details and the hardware configuration. You can print out the contents of the following members by using option 6 (Print) on the appropriate displays. Workloads Configurations Hardware Analysis parameters Job classifications Graph Formats The following figures show the reports that can be obtained after analyzing a Capacity Planning model. Some reports hae been edited for clarity. Analysis Summary Report Copyright IBM Corp. 1998,

250 M Analysis Summary Report CPU model / release leel : V4R10 Main storage : 512 B Quantity Predicted Util CPU : Disk IOPs : Disk controllers : Disk arms : Local WS controllers..... : Multifunction IOPs : Disk IOAs : LAN IOAs : 1.0 WAN IOAs : 2.0 Integrated PC Serer IOAs... : 0.0 LAN IOPs : 1.0 LAN lines : LAN controllers : WAN IOPs : 1.0 WAN lines : 8.0 WAN WS controllers : 8.0 Interactie Non-interactie CPU utilization % : Transactions per Hour : Local response time (seconds) : LAN response time (seconds) : WAN response time (seconds) :.0.0 Figure 143. Analysis Summary Report Note: The printed output identifies the model and text. If you are working with results outside of a model, the output identifies the results member name and text. Recommendations Report ***** Analysis Exceptions ***** All the specified objecties hae been met Recommendations Figure 144. Recommendations Report Workload Report Workload Report Period : Analysis CPU Total Rsp Times (Secs) Local Rsp Time Secs spent in Workload Type Util Trn/hr Internal Local LAN WAN CPU I/O Pool Comm Other CLIENTAC INTERACTIV CLIENTAC INTERACTIV NONINTER QDEFAULT LAN Rsp Time Secs spent in WAN Rsp Time Secs spent in Workload Type CPU I/O Pool Comm Other CPU I/O Pool Comm Other CLIENTAC INTERACTIV CLIENTAC INTERACTIV NONINTER QDEFAULT Workload type: 1=Interactie, 2=Non-interactie, 3=*BATCHJOB Figure 145. Workload Report 230 BEST/1 Capacity Planning Tool V5R1

251 ASP and Disk Arm Report ASP and Disk Arm Report Period : Analysis I/Os Disk Disk Subsystem Aerage ASP Arms per Sec Pct Busy Msecs per I/O Figure 146. ASP and Disk Arm Report Disk Resources Report Disk Resources Report Period : Analysis I/Os Disk Disk Subsystem Aerage Type Arms per Sec Util Pct Busy Msecs per I/O CMB01 *MFIOP DI10 *IOA SI10 *IOP Figure 147. Disk Resources Report Main Storage Pool Report Main Storage Pool Report Period : Analysis Sync Reads Act Size Ineligible -----Aerage Number per Pool ID Ll (KB) Wait (sec) Actie Ineligible Sec Figure 148. Main Storage Pool Report Comm Resources Report Comm Resources Report Period: Analysis Thruput Rsp Time per Nbr of Line Speed Resource Util (Kbit/sec) Trans (Msec) Lines (Kbit/sec) CC01.0 LANLINE CC02.0 WANLINE CMB LIN19.0 D27DBF LIN21.0 CMN LIN25.0 QESLINE Figure 149. Communications Resources Report Chapter 10. Printing Model Reports and Graphs 231

252 Model Report Performance data : Model/Text : V4R2IBMDT3 (Q ) BEST1M ODEL Model Objecties and Actie Jobs Workload Actie Interactie Non-inter Workload Connect Type Jobs Rsp Time Thruput Thruput CLIENTAC4 *LAN *NORMAL INTERACTIV *LOCAL *NORMAL INTERACTIV *LAN *NORMAL NONINTER *LOCAL *NORMAL QCMN *LAN *NORMAL QCMN *WAN *NORMAL QDEFAULT *LOCAL *NORMAL Workload Workload/Text : CLIENTAC4 Workload type : *NORM AL Workload CPU architecture. : *RISC Usage mode : 2 Usage mode: 1=Casual, 2=Interrupted, 3=Steady, 4=N/A ----Relatie Counts----- ASP Reads Writes Chars to Comm Line Resources Workload : CLIENTAC4 Nbr of Line Speed Line Resource Connect Lines (Kbit/sec) Relatie Count CMN08 *WAN D27DBF0101 *LAN Function Function/Text : CLIENTAC4 Function of CLIENTAC4 Functions per user : 1.00 Ag Key/Think (secs) : Additional delays (secs) :.0 Inter tns per function : Non-inter tns per function : Transaction Pool Transactions CPU Time Permanent -Chars Transferred- Exceptional Type ID Priority per Function (Secs) Write Pct In Out Wait (Msec) Synchronous Asynchronous Transaction Pool Total DB DB NDB NDB DB DB NDB NDB Type ID I/Os Read Write Read Write Read Write Read Write Transaction Pool Paging Working Set -----Paging Exponent Paging Coefficient---- Type ID Behaior Size (MB) Database Non-Database Database Non-Database 2 2 *GENERIC *GENERIC *GENERIC Figure 150. Printout of Model Detail Part BEST/1 Capacity Planning Tool V5R1

253 M M Configuration CPU odel : 2181 ultifunction IOPs : 1 Main storage (MB) : 512 Disk IOAs : 1 Main storage pools : 4 Comm IOAs : 3 Disk IOPs : 1 Integrated PC Serer IOAs : 0 Disk ctls : 2 Local WS ctls : 40 Disk arms : 20 LAN ctls : 20 ASPs : 1 WAN WS ctls : 8 Release leel : V4R1M 0 Sc Time (M sec/kbit): Comm IOPs : 2 Local WS ctls : 1.50 LAN lines : 2 LAN ctls : 2.00 WAN lines : 8 WAN WS ctls : 2.00 RAID Serice Time Resource Feature Type ASP Array (Msecs per IO) CMB *MFIOP.9 DI *IOA 1.7 _DD *ARM _DD *ARM _DD *ARM _DD *ARM SI *IOP.9 ARRAY *CTL _DD *ARM _DD *ARM _DD *ARM _DD *ARM _DD *ARM _DD *ARM _DD *ARM _DD *ARM DD *ARM DD *ARM ARRAY *CTL _DD *ARM _DD *ARM _DD *ARM _DD *ARM DD *ARM DD *ARM Number of Data ASP Disk Arms Drie Feature Protection 1 20 ** *NONE Drie Feature: ** = mixed Figure 151. Printout of Model Detail Part 2 Nbr of Line Speed Pct Line Frame Size ----Sc Time (Msecs)---- Resource Feature Lines Type (Kbit/sec) Oerhead Duplex (Bytes) LAN Frames WAN Frames CC *IOP LANLINE1 1 *LINE *HALF CC *IOP WANLINE1 6 *LINE *HALF CMB *MFIOP LIN *IOA *HALF D27DBF *LINE *HALF LIN *IOA *HALF CMN08 1 *LINE *HALF LIN *IOA *HALF F QESLINE 1 *LINE *HALF Actiity Size Pool ID Pool Name Leel (KB) Figure 152. Printout of Model Detail Part 3 Chapter 10. Printing Model Reports and Graphs 233

254 Analysis Parameters Analysis Guidelines Max Hardware Util *GUIDE *GUIDE, *THRESH Priority for CPU util Guideline Threshold CPU util Disk IOP util Disk arm util Communications IOP util Communications line util Local WS controller util LAN controller util WAN WS controller util Disk IOA util Comm IOA util Integrated PC Serer IOA util Sync Reads Guidelines Values are used for Analysis recommendations. Check sync reads : N Y=Yes, N=No Pool 1 (*MACH) CPU relatie performance CISC RISC 2.0 or less : 2 10 Greater than : All Other Pools CPU relatie performance CISC RISC 2.0 or less : or less : or less : or less : or less : or less : Greater than : Paging Behaior Values Paging -----Paging Exponent----- Working Set Size (MB) Behaior Database Non-Database CISC RISC *GENERIC *OFFICE *RAMPC *SQLRTW Note: The RISC alues under the Working Set Size (MB) appear on a PowerPC AS processor. CISC-to-RISC Conersion Factors Workload CPU Working I/O Type Time Set Size Counts *NORMAL *TRNNORM *TRNNORM *TRNNORM *BATCHJOB *TRNBAT *TRNBAT *TRNBAT Figure 153. Analysis Parameters 234 BEST/1 Capacity Planning Tool V5R1

255 Graph Format Workload I/Os by period Graph Format Graph format..... : WIOSBYPRD Text : Workload I/Os by period Title : Workload I/Os by period Subtitle : *BLANK Graph type..... : *LINE *LINE, *BAR, *PIE, *SURFACE Area fill : Y Y=Yes, N=No X-axis: Variable. : Workload I/Os per Sec Title... : Workload I/Os per Sec Y-axis: Variable. : Workload I/Os per Sec Title... : Workload I/Os per Sec Variable Title Minimum Maximum X-axis Period Period *MIN *MAX Y-axis Workload I/Os per Sec Workload I/Os per Sec *MIN *MAX Figure 154. Printout of Graph Format Details Graphical Output BEST/1 comes with a set of IBM-supplied graph formats or you can create your own formats by copying and then changing the IBM-supplied format. Graphic support is for the 5250 family of display deices, including 5250 Work Station Function graphics support under DOS. There is no WSF 5250 graphics support directly under OS/2 and 3270 graphic data streams are not supported. Howeer, BEST/1 supports generating a GDF (Graphics Data Format) file that can be subsequently used on a VM or MVS-based machine and attached 3270 graphics deices. Under BEST/1, a GDF file is stored as a member in file QACYGDFS. You assign the member name (GDF file name) and library. You may use the Send Network File (SNDNETF) command to route the file to a VM or MVS-based system if you hae AS/400 VM/MVS Bridge support configured. Bridge support is part of licensed program 57xx-CM1, Communication Utilities. In addition to generating a GDF file, BEST/1 graphics support proides printing and plotting of the graph. This BEST/1 support is consistent with the other graphics support aailable with the Performance Tools licensed program. Graphics design should be done either with a graphics display or a PC with a graphics monitor. If you do not hae graphics support on your display screen, BEST/1 displays the graph using standard characters to simulate line and bar graphs. BEST/1 separates the graph data from the graph formats to gie greater flexibility in selection of graphical output. Use the current modeled results or select a preiously saed set of results from the Select Results Member display. You can access graphics support by pressing F18 (Graph current results) on the Work with Results display. The following lists the-ibm supplied graph formats. Disk busy by ASP Disk IOP busy CPU util by workload Disk I/O by ASP Workload rsp time by period Chapter 10. Printing Model Reports and Graphs 235

256 Response time by trans/hr Interactie workload trans/hr Workload I/Os by period The following display appears after you press F18. Work with Graph Formats Library... QPFR Name Type option, press Enter. 1=Create 2=Change 3=Copy 4=Delete 5=Display graph 6=Print graph format 7=Rename 8=Print graph 17=Plot graph Opt Member Text Date Time THRUBYWKL Interactie workload trans/hr 07/27/93 10:55:58 BSYBYIOP Disk IOP busy 07/27/93 10:55:58 WIOSBYPRD Workload I/Os by period 07/27/93 10:55:58 THRUBYRSP Response time by trans/hr 07/27/93 10:55:58 BSYBYASP Disk busy by ASP 07/27/93 10:55:57 RSPBYPRD Workload rsp time by period 07/27/93 10:55:57 CPUBYWKL CPU util by workload 07/27/93 10:55:57 DIOSBYASP Disk I/O by ASP 07/27/93 10:55:57 Bottom Command ===> 4 F3=Exit F4=Prompt F5=Refresh F6=Select results for oerlay F9=Retriee F12=Cancel F15=Sort by member F24=More keys Figure 155. IBM-Supplied Graph Formats Display the graph by typing a 5 in the Opt column. The example shows the list of IBM-supplied graphs from library QPFR. The IBM-supplied graphs include pie, bar, line, and surface types. The type of some of the supplied formats might need to be changed for the way you want to commonly iew the data. For example, CPU utilization may be defaulted to a pie chart. You might want to iew the data as a bar or line graph. Note: Pie and surface graphs require graphics capable deices. On character based terminals, pie, and surface graphs will be plotted as bar and line, respectiely. You can create your own graph formats by: Copying an IBM-supplied format and changing the copy. Building one from the arious parameters supplied as shown in Figure 156 on page BEST/1 Capacity Planning Tool V5R1

257 Create Graph Format Graph format...: TEST Type choices, press Enter. Text... Your text Title... Your title Subtitle... *BLANK Graph type... *LINE *LINE, *BAR, *PIE, *SURFACE Area fill... N Y=Yes, N=No X-axis: Variable.. F4 for list Title... Y-axis: Variable.. F4 for list Title... F3=Exit F4=Prompt F6=Print graph F12=Cancel F13=Change axis range F17=Plot graph Bottom Figure 156. BEST/1 Create Graph Format Examples of many of the IBM-supplied and user-generated graph formats are in Sample Custom Graphs on page 243. Figure 157 shows the X and Y axis ariables that can be used to create your own format. Additional ariables are: LAN IOP util, LAN line resource util, WAN IOP util, and Type option, press Enter. 1=Select Select X-Axis Variable Opt Variable ID Variable Text 1 Period 10 CPU Util 11 Workload CPU Util 12 Disk Busy 13 Disk IOP Busy 20 Workload Inter Trans/hr 21 Workload Non-inter Trans/hr 22 Total Trans/hr 23 Workload I/Os per Sec 24 Disk I/Os per Sec 25 Disk IOP I/Os per Sec 26 Actie Jobs 30 Resp Time by Workload 31 Disk Rsp Time per I/O 32 Aerage Response Time F12=Cancel More... Figure 157. BEST/1 Graphic Support Variables WAN line resource util. Note: You cannot graph IOA utilizations. Chapter 10. Printing Model Reports and Graphs 237

258 Changing the Axis Range BEST/1 assigns default axis ranges, which are set to the smallest and largest alue in the data. You may oerride this alue by performing the following steps: 1. On the Work with Graph Formats display, select option 2 (Change) next to a graph format member and press the Enter key. The Change Graph Format display appears. 2. On the Change Graph Formats display, press F13 (Change axis range). The Change Axis Ranges display appears. Change Axis Ranges Graph format...: THRUBYWKL Text...: Interactie workload trans/hr X-axis ariable...: Y-axis ariable...: Period Workload Inter Trans/hr Type changes, press Enter. X-axis: Minimum... *MIN Value, *MIN Maximum... *MAX Value, *MAX Y-axis: Minimum... *MIN Value, *MIN Maximum... *MAX Value, *MAX F3=Exit F12=Cancel Figure 158. Change Axis Ranges Display 3. You can change *MIN and *MAX for either or both the X and Y-axis. *MIN and *MAX represent the lowest and highest number in the data, respectiely. You type a specific alue to represent the minimum and maximum numbers on the axis to more accurately represent your data. Graphing a Single Set of Model Results Figure 159 on page 239 is an example of graphing Interactie Response Time and Interactie Throughput: 238 BEST/1 Capacity Planning Tool V5R1

259 Figure 159. Single Results, Multiple Workload Graph Example The output is based on a modeled D45 with fie growth periods. Local work station work is included in workload INTBAS and remote work is included in workload EVKBAS. Workload EVKBAS response time is shown in the example as response time 4 through 6 seconds. Workload INTBAS is much lighter and is shown with response times below.5 seconds. Oerlaying Graphs of Two Results BEST/1 enables you to oerlay multiple sets of results on the same display, plot, or printed output. The following describes a technique to oerlay two graphs. You must use the same type of graph for oerlay results. To oerlay two sets of results you can use two saed model results or select one saed results to combine with the current model you are using. Function keys F18 (Graph current results) and F6 (Select results for oerlay) must be used in the proper sequence. If you want to show only one workload in each model results pair (if you are using a workload graph format), you must either combine workloads (a function key on the Work with Workloads display) or delete the other workloads and keep the workload you are working on. Oerlaying Two Graphs Scenario Perform the following steps in the order shown. 1. Analyze the data and graph the results. 2. Sae the results, if you want to use them for further study. If you do not sae the results, the oerlay legend will use the current name as the results name. 3. Begin working with the saed model. 4. Change hardware, growth, and so on. Analyze the data and graph the results. Chapter 10. Printing Model Reports and Graphs 239

260 5. When satisfied, sae the results with a new name. Sae the results and new model with a meaningful name, such as MDLE90. You now hae a second set of results in main memory. 6. From the Work with Results Display, press F18 (Graph current results). The Work with Graph Formats display appears. 7. On this display, press F6 (Select result to oerlay). Select up to fie results, including the first saed member. Press the Enter key. A message displays if BEST/1 needs to rename duplicate period names. The Work with Graph Formats display appears again. 8. Type 5 (Display graph) next to the graph format of your choice (line only) and press Enter. The oerlay graph appears. You can see separate lines for each component of each result as shown in Figure 160. Figure 160. Oerlay, Multiple Workload Graph Example Refer to Saing Results on page 99 for information describing how to sae a BEST/1 results file for use on a personal computer for further data or graphic manipulation. Notes: 1. You need to use a graphics terminal to display oerlayed graphs. If you are on a non-graphics terminal, the message displays Character graphs can not be displayed when results members are oerlayed. 2. Aoid using duplicate period names within a result member. If you do, BEST/1 checks for duplicated period names and renames them temporarily. 3. You can oerlay a maximum of fie members. 4. If you oerlay two graphs, the legends from both graphs are combined to reflect the new oerlay graph. Therefore, do not read in results members from different libraries with the same name because it results in an incorrect legend. BEST/1 uses the results member to identify the component name. An example is if the results member name is E50CFG and the workload name is SPOOL the 240 BEST/1 Capacity Planning Tool V5R1

261 legend name will read E50CFG-SPOOL. Results which hae been analyzed instead of read in as results members are identified as *CURRENT. 5. Oerlay graphs can be line format only. Printing Graphs in BEST/1 You can print graphs from seeral displays in BEST/1. From the Work with Graph Format Screen, select option 8 (Print graph) in the Opt field next to the desired graph format. The Specify Printer display appears. Type choices, press Enter. Specify Printer Printer deice... 1=5224/5225 printer 2=4214 printer 3=4234 printer 4=IPDS printer Printer file... QPGDDMName Library... QSYS Name, *LIBL Spool output data... Y Y=Yes, N=No Change default printer options... Y Y=Yes, N=No F3=Exit F12=Cancel Figure 161. Specify Printer In general, using the default printer file, QPGDDM, will print the graph correctly on the specified printer. When shipped, QPGDDM is set up for *SCS printer with a page size of 99 lines per page and 132 characters per line with 10 characters per inch. For an Intelligent Printer Data Stream (IPDS) printer, the page size is 48 lines per page, and 150 characters per line with 15 characters per inch. If the defaults do not work on your printer, you can use the Change Printer Options display as shown in Figure 162 on page 242, to change printer options, such as page size, form type and number of copies. This display appears when you select Y for the change default printer options parameter. Once you hae determined the defaults you wish to use, you can create a new printer file with the appropriate options. You can then use this file name in the Printer file field on the Specify Printer display. When you do this, you will not need to remember to change the printer options each time you print a graph. Note: OS/400 can conert Adanced Function Printer Data Stream (AFPDS) to Printer Control Language (PCL). In preious releases, AFPDS application output to be printed required an Intelligent Printer Data Stream (IPDS) printer. Since BEST/1 utilizes Graphical Data Display Manager (GDDM) it is an AFPDS application. Chapter 10. Printing Model Reports and Graphs 241

262 Howeer, there is a limitation to this OS/400 print support in that it does not handle Graphic Object Content Architecture (GOCA) (the printable graphics architecture generated by GDDM calls). Consequently, BEST/1 graphical output will not be able to take adantage of this support and still requires the use of IPDS printers. Change Printer Options Printer file...: QPGDDMLibrary...: QSYS Type choices, press Enter to print. Page size: Length of page Width of page for 10 CPI for 15 CPI Characters per inch (CPI) Oerflow line For IPDS printers: Degree of page rotation... *AUTO *AUTO, *DEVD, *CORR 0, 90, 180, 270 Output queue... *JOB Name, *JOB, *DEV Library... *LIBL Name, *LIBL For choice *DEV: Printer deice name... Name, *JOB Number of copies Form type... *STD Name, *STD F3=Exit F12=Cancel Figure 162. Change Printer Options You can also print from the graph display with F6 (Print graph), or from the Change or Create Graph Format displays. Printed output will always be graphics output, een if you are printing at a non-graphics terminal. Plotting Graphs in BEST/1 You can plot graphs from seeral displays in BEST/1. From the Work with Graph Format Display, select option 17 (Plot graph) in the Opt field next to the desired graph format. The Specify Plotter appears. 242 BEST/1 Capacity Planning Tool V5R1

263 Specify Plotter Type choices, press Enter. Plotter address Change default plotter options... Y Y=Yes, N=No F3=Exit F12=Cancel Figure 163. Specify Plotter If you specify Y in the Change default plotter options field the Change Plotter Options display appears. You can change the pen speed, pen width, paper orientation, or page size. The options you can change will depend on the type of plotter that is attached to the terminal. The plotter must be attached to same the terminal as your BEST/1 session. Sample Custom Graphs The following graphs can be defined using the graphing functions in BEST/1. There are a number of standard graph formats which are shipped with the product, but changes were made to make them more useful. The following graphs show the potential of the graphics package, and should meet your requirements for graphing. In general, there are no descriptions of the graphs shown in this section. Chapter 10. Printing Model Reports and Graphs 243

264 Figure 164. Disk Utilization by Total Workload Figure 165. Disk IOP Utilization by Total Workload 244 BEST/1 Capacity Planning Tool V5R1

265 Figure 166. CPU Utilization by Non-Interactie Throughput Figure 167. CPU Utilization by Interactie Throughput Chapter 10. Printing Model Reports and Graphs 245

266 Figure 168. Response Time ersus Interactie Throughput Figure 169. Response Time by Workload 246 BEST/1 Capacity Planning Tool V5R1

267 Figure 170. CPU Utilization Component Breakdown Figure 171. Sample Bar Chart Chapter 10. Printing Model Reports and Graphs 247

268 248 BEST/1 Capacity Planning Tool V5R1

269 Appendix A. BEST/1 Workload Groups for Capacity Planning This appendix supplies additional information about the following workload groups used in the BEST/1 capacity planning tool: COMMERCIAL SPOOL BATCH OFFICE SERVER INDUSTRY COMMERCIAL Workload Group BEST/1 includes the following workloads in the COMMERCIAL workload group. RAMP-C is a generic interactie commercial application that is diided into transaction types called classes 1, 2, 3, and 4. Each transaction type represents a different complexity of workload. Table 7 on page 250 lists the characteristics for each transaction type. You can mix these transaction types in any combination to resemble an application that you would like to analyze. Each mixture of transaction types becomes a different RAMP-C predefined profile in the BEST/1. For example, if your application is ery simple, the Inquiry transaction type might be sufficient to describe that application. This would become one of your RAMP-C predefined profiles. If another application has simple menus, in addition to other displays, with increased complexity or file actiity, use the Inquiry or Simple Update transaction types with the complex ones, such as Multiple Entry Update, to create another predefined profile. IBM designed the RAMP-C generic application to measure and compare system performance capabilities. The initial default alue that BEST/1 uses for the transaction type mixture is the most common mixture used in marketing performance literature. This default mix of the transaction types is considered representatie of a typical data processing application. To hae the RAMP-C predefined profile resemble your commercial application, change the default mixture accordingly. A sample end user equialent of each of the four transaction types follows: Inquiry (Class 1) Looking up a part price using the part number as a key. Simple Updates (Class 2) Entering an accounts receiable or entering an order consisting of one line item. Multiple Entry Updates (Class 3) Entering an order consisting of six line items. Complex Processing (Class 4) Entering an order consisting of 10 line items or updating 10 items in an inentory file. Copyright IBM Corp. 1998,

270 Table 7 shows the RAMP-C characteristics, according to class. Table 7. RAMP-C Characteristics (by Class) RAMP-C Characteristics Inquiry (Class 1) Simple Updates (Class 2) Multiple Entry Updates (Class 3) Complex Processing (Class 4) Database Files (per Program) Read by Key Read Sequential Update Add (to Single Logging File) Display Files Fields Input 1 5 Constant Output Input/Output Characters Input Constant Output Input/Output COBOL Statements Run (Aerage per Transaction) Program Size (COBOL Statements) SQL RTW Workload BEST/1 includes the Relational Transaction Workload (RTW) as part of the Commercial Workloads group. RTW is an interactie transaction processing workload that simulates functions and transactions found in an inentory tracking and stock control application. Although this workload is a realistic database application, it does not represent all applications. Performance leels in different enironments can ary significantly. RTW is a much less complex workload than RAMP-C. RTW consists of six different transactions that range from simple to medium complexity. Each transaction consists of: A separate application that is called from a main application A single input and output operation from an interactie display, with no additional transfer between menus or displays between transactions Two of the transactions perform inentory tracking functions, while the other four transactions perform stock control functions. Each RTW work station performs all six transactions according to a standard mix. RTW Transaction Details The applications in this workload are written in COBOL using static SQL statements to perform the necessary I/O functions. All SQL I/O operations are tuned to achiee optimum performance, and no full open or close operations of 250 BEST/1 Capacity Planning Tool V5R1

271 files occur in the workload. In addition, no keyed fields are updated during these measurements except during delete and insert operations, so maintenance of indexes is minimal. Part Location and Inentory This transaction reports part location and information on inentory aailability. This transaction is a read-only operation against two tables in the inentory tracking database. Select an item type and a description from the item number table: SELECT FROM WHERE ITMTYPEC, ITMDESCR INTO :ITM-TYPEC, :ITM-DESCR ITMNUMBR ITMITEMN = :TRAN-ITEM-KEY Fetch the item status information in the item location table: DECLARE C1 CURSOR FOR SELECT OPEN C1 ITLLOCAN, ITLTENTR, ITLTLEAV, ITLSTENT, ITLSTLEV, ITLSTATC, ITLALTWC FROMITLOCATN WHERE ITLITEMN = :TRAN-ITEM-KEY FETCH C1 INTO (7 fields aboe -- aerage of 16 times) CLOSE C1 Update In-Process Inentory This transaction records the completion of labor operations on manufactured items and updates employee actiity records. The information proided by these transactions allows the construction time for an item on the manufacturing shop floor to be tracked as the item moes from work station to work station. Two labor operations are recorded by the same employee for each in-process item as that item moes through two different work centers. The transaction is started from the manufacturing shop floor by the employee who has completed the unit of work. This transaction includes read, update, insert, and delete operations against eight tables in the inentory tracking database. Select information on an employee s department and shift: SELECT EMPDEPTN, EMPSHIFT INTO :EMPDEPTN, :EMPSHIFT FROMEMPLOYEE WHERE EMPEMPLN = :TRAN-EMP-KEY Ensure that the item number is alid before adding it to the labor statistics table: SELECT COUNT(*) INTO :ITEM-COUNT FROM ITMNUMBR WHERE ITMITEMN = :TRAN-ITEM-KEY Insert the employee data and the item number into the labor statistics table: INSERT INTO LBRSTATS (this employee, unique time-stamp, item) Select information regarding where the work is being performed: SELECT INTO PRTDESCR, LABDEPTN, LABEFFBD, LABEFFED :PRTDESCR, :LABDEPTN, :LABEFFBD, :LABEFFED Appendix A. BEST/1 Workload Groups for Capacity Planning 251

272 FROMPRTNUMBR, LABOROPS WHERE LABPARTN = :TRAN-PART-KEY AND PRTPARTN = :TRAN-PART-KEY AND LABORERS = :WORK-LABOR-KEY Validate the work center and department: SELECT COUNT(*) INTO :WKCTR-COUNT FROMWKCENTER WHERE WKCDEPTN = :EMPDEPTN AND WKCWKCEN = :TRAN-WKCTR-KEY Declare, open, and fetch for an update of a tracking record for the processing item. This updating is repeated because two labor operations are performed by a single employee as the item moes through two work centers: DECLARE C2 CURSOR FOR SELECT (17 fields) FROMTRKOPRNS WHERE TRKITEMN = :TRAN-ITEM-KEY AND TRKOPKEY = :TRAN-OPER-KEY FOR UPDATE OF (17 fields) OPEN C2 FETCH C2 INTO (17 fields) UPDATE TRKOPRNS SET (12 of 17 fields) WHERE CURRENT OF C2 CLOSE C2 Repeat the select, open, fetch, update, and close step aboe: INSERT INTO ACTIVLOG (this item, date) INSERT INTO ACTIVLOG (this item, date) DELETE FROMACTIVLOG (this item, date) DELETE FROMACTIVLOG (this item, date) DELETE FROMLBRSTATS (this item, date) Order Inquiry This transaction displays the contents of outstanding orders in the stock control database. There is an aerage of seen parts in each order. The input consists of customer and order numbers, and the output is similar in format to the original order placed with the endor. This transaction is a read-only operation against one table in the stock control database. Select information about an employee s department and shift: DECLARE C1 CURSOR FOR SELECT OPAPARTN, OPADELAY, OPAFILLD FROMOPARTS00 WHERE OPARNMBR = :TRAN-ORDER-KEY OPEN C1 FETCH C1 INTO :OPAPARTN, :OPADELAY, :OPAFILLD (ag of 7 times) CLOSE C1 252 BEST/1 Capacity Planning Tool V5R1

273 Receiing and Processing If a part is no longer required in the database, it is deleted if it does not hae any outstanding orders. Updating the stock and maintaining orders is done by the receiing and processing side of the application. Deleting orders from the database is done in a batch process after the order is flagged in the online system. The input to this transaction consists of: The order number A list of part numbers The quantity receied for each against the order The following is a retrieal and update transaction against three tables in the stock control database: Fetch and update the status of an order DECLARE C1 CURSOR FOR SELECT ORDQUANT, ORDSTATS, ORDREQND, ORDCODES FROMORDER000 WHERE ORDRNMBR = :TRAN-ORDER-KEY FOR UPDATE OF ORDQUANT, ORDSTATS OPEN C1 FETCH C1 INTO :ORDQUANT, :ORDSTATS, :ORDREQND, :ORDCODES UPDATE ORDER000 SET ORDQUANT = :ORDQUANT, ORDSTATS = :ORDSTATS WHERE CURRENT OF C1 CLOSE C1 Cursor C2 fetches seen times for a part on order. Cursor C3 opens, fetches, updates and closes for each part: DECLARE C2 CURSOR FOR SELECT OPAPARTN FROMOPARTS00 WHERE OPARNMBR = :TRAN-ORDER-KEY DECLARE C3 CURSOR FOR SELECT PARSECOQ, PARRTVLT FROMPARTS000 WHERE PARPARTN = :OPAPARTN FOR UPDATE OF PARSECOQ OPEN C2 FETCH C2 INTO :OPAPARTN OPEN C3 Fetch and update the secondary quantity aailable in the parts table for each part on order: FETCH C3 INTO :PARSECOQ, :PARRTVLT UPDATE PARTS000 SET PARSECOQ = :PARSECOQ WHERE CURRENT OF C3 CLOSE C3 Loop to fetch C2 seen times until all parts for order are processed: CLOSE C2 Appendix A. BEST/1 Workload Groups for Capacity Planning 253

274 Parts Delete This transaction is a database maintenance function. Among many reasons to delete existing parts from the stock control database, one of the most common is the replacement of an existing part by a new one. Before a part can be remoed from the database, a check is made against the order table to ensure that it has no existing orders. If there are no outstanding orders, the part is deleted from the parts table and all suppliers of the part are deleted from the supplier table. This transaction performs read, update, delete and insert operations against three tables in the stock control database. If the part to delete is on order, do not delete the part and exit the program. If the part to delete is not on order: SELECT COUNT(*) INTO :PARTS-COUNTER FROMOPARTS00 WHERE OPAPARTN = :PART-DELETE If the part is on order (count > 0), do not delete the part on order and discontinue this process. Otherwise, fetch and lock the part to delete, and delete the part and the supplier if there is no quantity on hand. DECLARE C2 CURSOR FOR SELECT PARPARTN, PARSECOQ, PARNUMPC FROMPARTS000 WHERE PARPARTN = :PART-DELETE FOR UPDATE OF PARPARTN OPEN C2 FETCH C2 INTO :PARPARTN, :PARSECOQ, :PARNUMPC Fetch and delete all the suppliers of the part: DECLARE C3 CURSOR FOR SELECT SUPSUPPN FROMSUPPLIER WHERE SUPPARTN = :PART-DELETE FOR UPDATE OF SUPSUPPN OPEN C3 FETCH C3 INTO :SUPSUPPN DELETE FROMSUPPLIER WHERE CURRENT OF C3 Loop to fetch until all the suppliers are deleted: CLOSE C3 After the suppliers are deleted, you can also delete the part: DELETE FROMPARTS000 WHERE CURRENT OF C2 CLOSE C2 Check to see if an order was placed for the part that was deleted. If the part was ordered, then discontinue this process (rollback work): SELECT COUNT(*) INTO :PARTS-COUNTER FROMOPARTS00 WHERE OPAPARTN = :PART-DELETE If the part was not ordered, continue this process. Insert all the delete operations again to preent the workload from degrading: 254 BEST/1 Capacity Planning Tool V5R1

275 INSERT INTO PARTS000 (part deleted) INSERT INTO SUPPLIER (all suppliers deleted) Parts Inquiry This transaction is used to report on the status of parts required throughout the manufacturing process. This transaction is a read-only operation against one table in the stock control database. Check to see if parts are on order: SELECT COUNT(*) INTO :PARTS-COUNTER FROMOPARTS00 WHERE OPAPARTN = :TRAN-PARTN-KEY RTW Transaction Summary The transaction types in Table 8 are the following: 1 Part Location and Inentory 2 Update In-Process Inentory 3 Order Inquiry 4 Receiing and Processing 5 Parts Delete 6 Parts Inquiry Table 8. RTW Transaction Summary Transaction Type SELECT Statements INSERT Statements DELETE Statements UPDATE Statements Frequency % RTW Tables and Indexes The inentory tracking transactions operate against a separate database from the stock control transactions and hae different indexes for data retrieal. The inentory tracking transactions operate against nine different tables using a total of 18 different indexes to access the data. These nine tables range in size from 500 to records. The stock control transactions operate against four different tables using a total of six different indexes. These four tables range in size from 400 to records. See Table 9 for a summary of the tables and see Table 10 on page 256 for a summary of the indexes used by the RTW workload Table 9. Tables Used by the RTW Workload Table Name Row Size Rows Columns Indexes Access Inentory Tracking Database ACTIVLOG R/W EMPLOYEE R/O ITLOCATN R/W ITNUMBR R/W LABOROPS R/W Appendix A. BEST/1 Workload Groups for Capacity Planning 255

276 Table 9. Tables Used by the RTW Workload (continued) Table Name Row Size Rows Columns Indexes Access LBRSTATS R/O PRTNUMBR R/W TRKOPRNS R/W WKCENTER R/O Stock Control Database OPARTS R/W ORDER R/W PARTS R/O SUPPLIER R/W Table 10. Indexes Used by the RTW Workload Index Name Table Name Key Fields Entries Index Type Inentory Tracking Database XACTIT ACTIVLOG ACTITEMN Not unique ACTVDATE XDEPDE DEPTMENT DEPDEPTN 100 Unique XEMPDE EMPLOYEE EMPDEPTN Not unique XEMPEM EMPLOYEE Unique XEMPSH EMPLOYEE EMPSHIFT Not unique XITLIT ITLOCATN ITLITEMN Unique ITLLOCAN XITLLO ITLOCATN ITLLOCAN Not unique XITMIT ITMNUMBR ITMITEMN Unique XLABPA LABOROPS LABPARTN Unique LABOPERS XLBREM LBRSTATS LBREMPLN Unique LBRTSTPF XPRTPA PRTNUMBR PRTPARTN Unique XPRTMA PRTNUMBR PRTMATRL Not Unique XPRTM1 PRTNUMBR PRTMTRL Not unique XPRTM2 PRTNUMBR PRTMTRL Not unique XPRTM3 PRTNUMBR PRTMTRL Not unique XTRKIT TRKOPRNS TRKITEMN Unique TRKOPKEY XTRKOP TRKOPRNS TRKOPEKY Not unique XWKCDE WKCENTER WKCDEPTN 500 Unique WKCWKCEN XWKCWK WKCENTER WKCWKCEN 500 Not unique Stock Control Database XOPAPA OPARTS00 OPAPARTN 4000 Unique OPARNMBR XOPARN OPARTS00 OPARNMBR 4000 Not unique XORDRN ORDER000 ORDERNMBR 400 Unique XORDVE ORDER000 ORDVENDN 400 Unique ORDRNMBR XPARPA PARTS000 PARPARTN Unique XSUPPA SUPPLIER SUPPARTN Not unique 256 BEST/1 Capacity Planning Tool V5R1

277 SPOOL Workload Group BATCH Workload Group BEST/1 includes the following workloads in the SPOOL workload group. Simple Print; AFP(*NO) This workload represents the majority of printing done on the iseries serer, which is simple text printing without any Adanced Function Printing support for data conersions. For this workload a 200-page document was printed and each page had 4000 bytes. The printer ran at approximately 1500 lines per minute oer a 10-minute period. Simple Print; AFP(*YES) This workload represents the same print image as the Simple Print AFP(*NO) workload except this workload supports Adanced Function Printing for data conersions, allowing access to high speed printers. Only page printers are supported as AFP(*YES). For this workload four documents were printed. Each was 200 pages long and each page had 4000 bytes. The printer was running at about 80 pages per minute (or 5760 lines per minute), oer a 10-minute period. Complex print; AFP(*YES) This workload represents complex printing in high-speed printing enironment. Only page printers are supported as AFP(*YES). This workload can be used to characterize the printing of more complex jobs including image, oerlays, and graphics. The print data can either be created on the iseries serer or it can come from a System/370. AFP Utilities licensed program proides the capability to create adanced resources like oerlays on the iseries serer and merge them with OS/400-created data to create complex print applications. Printers configured AFP(*YES) require more OS/400 resources for printing because Adanced Function Printing supports higher speed printers and print data conersions. The AFP(*YES) workload specifically represents a complex print image which contains bytes per page and prints at a rate of 40 pages per minute, or 2880 lines per minute, oer a 10-minute period. The following workloads are proided with BEST/1 for the Batch Workload group: Background batch serer Commercial orders Deelopment Complex query Summary query Sort query Background batch serer Background batch serer is a synthetic batch workload of processing often associated with commercial data processing. It represents a job running at priority 50 which is pulling requests off of a data queue. It identifies work orders assigned to a particular warehouse and processes a set of those orders. It is a medium weight transaction that has a relatiely low frequency of execution. The job is intended to represent a longer running transaction that would normally be run in the background (batch) instead of running at an interactie work station. Appendix A. BEST/1 Workload Groups for Capacity Planning 257

278 Commercial Orders Commercial orders is a synthetic batch workload of batch processing often associated with commercial data processing. It concentrates on retrieing, resequencing, and organizing data from seeral files with a relatiely small amount of analysis of the data within the files, much like many end-of-day or end-of-month jobs. It is a heay-weight transaction. It can also include jobs that run at the same time with interactie work where the work is submitted to batch because it requires a large amount of disk I/O. The commercial orders workload operates on 18 physical files of arious sizes and record lengths. Each file has 10 logical iews using nine different indexes built oer it. The indexes allow physical access to the files sequentially, randomly, or some combination of sequential from a random starting point (skip-sequential). The job consists of three functions: Order alidation simulation A combination of reading and updating an order header file with skip-sequential accesses (blocks of 20 starting at a random location), and then reading through Order Detail, Customer, and Item files in a combination of skip-sequential and random accesses to build a print report of orders in error. The associated processing is a combination of array-handling, moes, simple arithmetic operations, and comparisons. Order processing simulation Reads the Header and Detail files in skip-sequential mode and then accesses the Customer and Item files randomly for updates. This simulation then reads through a Shipping file and uses the information to update a series of statistics files and to insert new records into two historical files. It completes by building a printed report of orders processed. File Copy Copies a record file into a temporary file. Deelopment The deelopment workload is a synthetic batch workload of the type of processing that might occur when application deelopment actiities run at the same time with normal production work. It includes a mixture of compile and library sae operations as follows: Large compilation RPG program with 2700 statements 2656 statements are Calc statements External Data Description Specifications (DDS) for 19 files Small compilation RPG program with 233 statements 217 statements are Calc statements External DDS for 6 files Sae procedure Clears a sae file Saes a library to the sae file - Holds 54 objects - Holds a total size of 2.86MB - Saes of access paths and uses data compression 258 BEST/1 Capacity Planning Tool V5R1

279 Repeats small compilation Repeats sae procedure The deelopment workload tends to be processing unit-intensie during the compilations, but includes a mixture of processing unit and synchronous disk I/O during the sae procedures. Complex Query The complex query workload is a predefined query that runs oer a database of records. It is the type of query that would run at the same time with normal production work and that is intense enough that it would likely be run as a batch job. The query has the following characteristics: Creates a new result field Selects 12 of the 28 possible fields for reporting Sorts output based on the result field Selects 30% of the records based on a Range specification Changes the report column formatting Uses all report summary functions on two fields and two summary functions on a third field. Creates a query report and places it on a spool queue The complex query tends to be processing unit-intensie. Summary Query (medium complexity) The summary query job workload is a query from a customer application that is run against a data file of approximately records. It represents the type of query that is dominated by field selection for summary data, without many additional functions. This type of query is often run as a part of end-of-day processing, but can also run at the same time with normal production work. The following are characteristics of the query: Selection of all records in the file Selection of six out of a possible 49 fields for reporting Selection of all summary options for four of the fields and three summary options for the remaining two Creates a query report and places it on a spool queue The summary query job workload tends to be processing unit-intensie. Sort Query (medium complexity) The Sort Query job is a query from a customer application that is run against a data file of approximately records. It represents the type of query that is needed to see a different iew (sort sequence) of data in a file with limited other functions. This type of query is often run along with normal production work to assist in decision-making processes, but can also be run as a part of end-of-day processing. The characteristics of the query are as follows: Selection of all records in the file Selection of nine out of a possible 10 fields for reporting Selection of two fields that are not the primary keys for the file as the sort fields for the query Selection of only one summary option on one field Appendix A. BEST/1 Workload Groups for Capacity Planning 259

280 Creates a query report and places it on a spool queue The Sort Query Job tends to be processing unit-intensie. I/O Workload Characteristics Depending on the size of the system, arious workloads hae the approximate characteristics shown in Table 11 when running as the only actiity on the system: Table 11. Approximate Workload Characteristics I/O Logical I/Os Synchronous I/Os Asynchronous I/Os Background batch per second 2 8 per second 6 20 per second serer Commercial orders per second 7 20 per second per second Deelopment 2 25 per second 3 35 per second 1 10 per second Complex query per second 2 15 per second 3 30 per second Summary query per second 1 12 per second 1 15 per second Sort query per second 2 15 per second 3 20 per second OFFICE Workload Group 260 BEST/1 Capacity Planning Tool V5R1 Note: Larger systems hae a higher I/O rate because the I/Os are requested more quickly, not because the disk dries are faster at processing I/Os. The office workload group contains workload that are characterized by seeral functions. A range of functions is performed by an aerage professional office software user and is not intended to be all-inclusie. The workload is based on the IBM OfficeVision for OS/400 licensed program. Each function consists of one or more related steps, and begins and ends with the initial office display, menu, or starting position. The functions include the following: Update One Calendar. Similar to Update Calendar (Single) in the office functions prior to Version 1 Release 3. View the user s calendar. Add and delete a meeting. Update Group Calendar. Similar to Update Calendar (Group) in the office functions prior to Version 1 Release 3. View the group s calendars. Add and delete a meeting. View One Calendar. Similar to View Calendar (Single) in the office functions prior to Version 1 Release 3. View the user s calendar. Process Heay Mail. Similar to Work with Mail in the office functions prior to Version 1 Release 3. Create a note and mail it to other users. View note. Delete note. View the list of mail items receied. View a note, forward it to other users, and delete it. Print document. Process Light Mail. Similar to Create and Send Note in the office functions prior to Version 1 Release 3.

281 Create a note and mail it to other users. View note. Delete note. View the list of mail items receied. View note. Delete note. Create Small Document. Similar to Word Processing Create in the office functions prior to Version 1 Release 3. Get prestored document format. Type in document text. Sae, print, and delete the document. Reise Small Document. Similar to Word Processing Simple Reise in the office functions prior to Version 1 Release 3. Get an existing document. Moe a paragraph once. Delete and insert a paragraph. End the edit session. Sae the document. Mail the changed document to other users. Reise Large Document. Similar to Word Processing Complex Reise in the office functions prior to Version 1 Release 3. Get an existing document. Go to a particular page. Find and replace a word. Find a phrase and copy a sentence. Delete a sentence. Go to another page. Delete, get, and moe different paragraphs. Check spelling on a particular page. Paginate, sae, and delete a document. View Directory Entry. Similar to View Directory in the office functions prior to Version 1 Release 3. Search the user directory for a specific user name and iew the person s telephone number. End/Begin Office. Similar to End Begin Office in the office functions prior to Version 1 Release 3. Leae the office main menu. Wait. Begin office (go back to the office main menu). Signoff/Signon System. Not in the office functions prior to Version 1 Release 3. Sign off the system. Wait. Sign on the system. Each function may take seeral transactions (Enter keys or command keys) to be processed. The ratio of transactions per function is different for the arious functions. See Table 12 on page 262 for a representation of this relationship. Appendix A. BEST/1 Workload Groups for Capacity Planning 261

282 Table 12. Transactions per Office Function Office Function 1 Transactions per Function Update One Calendar 7 Update Group Calendar 17 View One Calendar 3 Process Heay Mail 32 Process Light Mail 19 Create Small Document 15 Reise Small Document 15 Reise Large Document 56 View Directory Entry 6 End/Begin Office 2 Signoff/Signon System 3 : 1 Based on the IBM Office Benchmark Version 2 Office Functions An office profile is defined by assigning a function ratio and a key/think time to each of the functions. BEST/1 for the AS/400 system (BEST/1) conerts the function ratio to the appropriate transaction ratios. BEST/1 also displays the calculated aerage number of transactions per selected function mix. You can use this alue to calibrate the transaction throughput information that BEST/1 calculates. Each of the fie workload types proides a set of default function ratios for the arious OfficeVision functions. These defaults are listed in the workload type tables that follow. These default workload types span the range of typical office users, from word processing operators to managers. You can select another, user-defined, workload type to define your own function ratios for the arious tasks. Use this option if none of the default workload types represent your usage. Each of the three user types (steady, interrupted, and not frequent) proides a default key/think time for the functions. A steady user type is a word processing operator typing at a rapid pace with few breaks. An interrupted user type performs one-half the processing of the steady user type, and a not-frequent user type performs one-third the processing of a steady user type. You can select another user type, such as user-defined, to define your own key/think times. Table 13 shows office function mixes for the IBM Office Benchmark ersion 2 workload type. Table 13. IBM Office Benchmark Workload Type (Version 2) Office Function Function Ratio Transaction Ratio Update One Calendar 4 28 View One Calendar 4 12 Process Heay Mail Process Light Mail 5 95 Create Small Document 2 30 Reise Small Document 2 30 View Directory Entry 6 36 End/Begin Office 1 2 Signoff/Signon System 1 3 Totals BEST/1 Capacity Planning Tool V5R1

283 Table 14 shows office function mixes for the secretarial workload type. Table 14. Secretarial Workload Type Office Function 1 Function Ratio Transaction Ratio Update Group Calendar 1 17 Process Heay Mail 1 32 Reise Large Document 1 56 View Directory Entry 1 6 Totals Table 15 shows office function mixes for the IBM managerial workload type. Table 15. Managerial Workload Type Office Function 1 Function Ratio Transaction Ratio View One Calendar 2 6 Process Heay Mail 1 32 Process Light Mail 1 19 View Directory Entry 2 12 Totals 6 69 Table 16 shows office function mixes for the professional workload type. Table 16. Professional Workload Type Office Function 1 Function Ratio Transaction Ratio View One Calendar 2 6 Process Heay Mail 1 32 Process Light Mail 1 19 View Directory Entry 2 12 Totals 6 69 Table 17 shows office function mixes for the correspondence center workload type. Table 17. Correspondence Center Workload Type Office Function 1 Function Ratio Transaction Ratio Create Small Document 5 75 Reise Small Document 3 45 Reise Large Document Totals SERVER Workload Group The following workloads assume an OS/2 client. If you plan to use a window or UNIX client, additional OS/400 resources may be required. Refer to the AS/400 Performance Capabilities Reference. Client/Serer Simple OLTP This workload is based on a simple OLTP (on-line transaction processing) application. It was written using a client-based 4GL which uses APPC to communicate with the iseries serer. All database accesses are done using natie database by a serer job. This benchmark does three database retrieals (each from a different file) and one database insert (to a separate file). The database record size for the retrieals is 100 bytes and the update operation record size is 50 bytes. The three database files accessed for the retriee operations are 1 million records Appendix A. BEST/1 Workload Groups for Capacity Planning 263

284 for the first file, 1000 records for the second file, and 100 records for the third. The client application consists of minimal processing. Client/Serer Medium OLTP (DQ) This workload belongs to the application serer category meaning there is an application program running on the iseries serer that is exchanging information with an application program running on the PC. This particular workload contains modifications and extensions of the host-centric TPC-C Benchmark (it contains the same basic transactions as the TPC-C Benchmark, but it cannot be directly compared with results from other implementations of the TPC-C public standard.) The benchmark simulates an on-line transaction processing application that performs fie business transactions of arying complexity. Processing of a business transaction is defined as proiding input menu, handling operator input selection, the processing to support that particular business function, and displaying the final output result. This client/serer workload separates the processing of a business transaction between the PC and the iseries serer. The PC handles all the processing for interaction with the operator. The PC processing includes displaying the input menu, handling the operator input, alidating the operator input, doing all internal calculations it can for that particular transaction, and displaying the final output. The iseries serer retriees and updates all database files and does any calculations that can not wait to be done on the PC. It maintains integrity of the database information by using commitment control and journaling. The method of communication between PC and iseries serer is Client Access Data Queues API (hence the (DQ) designation in the workload name). Client Access LU 6.2. Heay USF/400 Multimedia User This workload represents the tasks of a ery actie user of the USF/400 functions of OS/400 operating system. The workload includes the following tasks: View 40 bitmap images, display one eery 30 seconds (approximately 125KB aerage size) using a USF sequence object. View 12 minutes of digital ideo at 150 FB/second (150 KB/second is considered a medium quality ideo deliery rate). Play 12 minutes of 16 bit mono audio sampled at 22Khz. Initiate 20 query by object calls to the multimedia repository. Initiate 10 query by container calls (opens 10 containers). Create 5 new digital ideo objects (approximately 20 seconds each). Delete 5 digital ideo objects. Create 5 new image objects using Digital Video Interactie (DVI). Delete 5 image objects. Heay Image Slide Show (Shared Folders) This workload represents the tasks of a USF/400 user displaying an image eery 15 seconds using a USF sequence object. The aerage size of the images is 150KB. This workload assumes that all data comes directly from the OS/400 QDLS file system (no file serer I/O processor hardware assistance). Heay Image Slide Show (IPCS) This workload represents the tasks of a USF/400 user displaying an image eery 15 seconds using a USF sequence object. The aerage size of the images is 150KB. This workload assumes that the data comes from the AS/400 Integrated xseries Serer for iseries, also known as file serer I/O processor and FSIOP. It is 264 BEST/1 Capacity Planning Tool V5R1

285 important that all communications traffic associated with this workload is properly associated with the line resource associated with the FSIOP hardware. Heay Image and Audio Slide Show This workload represents the tasks of a USF/400 user displaying an image eery 15 seconds using a USF sequence object. The aerage size of the images is 150KB. In addition, an audio clip (16 bit 22KHz) plays continuously in the background while the images are displaying. Medium Continuous Video (Shared Folders) This workload represents the tasks of a USF/400 user iewing a continuous ideo. The ideo is deliered at a rate of 150 KB/second to achiee a medium quality ideo image leel. This workload assumes that all data comes directly from the OS/400 QDLS file system (no FSIOP hardware assistance). Medium Continuous Video (FSIOP) This workload represents the tasks of a USF/400 user iewing a continuous ideo. The ideo is deliered at a rate of 150 KB/second to achiee a medium quality ideo image leel. This workload assumes that the data comes ia assistance from the OS/400 FSIOP. It is important that all communications traffic associated with this workload be properly directed to the line resource associated with FSIOP hardware. INDUSTRY Workload group The Industry workload group proides a set of OS/400 workload definitions which are a composite sketch of real iseries serer. The BEST/1 models hae been built based on performance data collected on iseries serer world-wide, then summarized by Industry. The summarized data was then use to create BEST/1 models. No direct mapping of specific application packages to OS/400 performance can be established within this data. As always the most accurate BEST/1 model will be one created from data specific to the application package being considered. Workload members are proided for the following industries: Communications Computer Serices Consultants/CPA/Legal Apparel and Retail Distribution Higher Education Finance State and Local Goernment Health/Medical Wholesale Distribution and Serices Media Consumer Goods Manufacturing Insurance Petroleum Process Chemical/Pharmaceutical K-12 Education Securities Appendix A. BEST/1 Workload Groups for Capacity Planning 265

286 Transportation Public Utilities Aerospace 266 BEST/1 Capacity Planning Tool V5R1

287 Appendix B. Query to Print JOB/TASK Types and CPU Utilization The following is the source for two query programs which together produce a report which shows: Job Name Job User Job Number Job Type Aerage Response Time CPU Seconds The report that is generated, is ery similar in layout to the Performance Tools Component Report, but gies additional information such as CPU seconds for each job/task. It would be straightforward to extend this report to show information relating to information such as transaction per hour, Logical I/Os, Priority, and Pool ID. The file queried is QAPMJOBS. 5769QU1 V4R2M IBM Query for iseries ABSYSTEM 6/17/97 15:15:21 Page 1 Query QRY1 Library BEST1 Query text Query CCSID Collating sequence Hexadecimal Processing options Use rounding Yes (default) Ignore decimal data errors..... No (default) Ignore substitution warnings.... Yes Special conditions *** All records selected by default *** Selected files ID File Library Member Record Format T01 QAPMJOBS BEST1 NEILPWS1 QAPMJOBR Ordering of selected fields Field Sort Ascending/ Break Field Name Priority Descending Leel Text JBNAME 10 A 1 Job Name JBUSER 20 A 1 Job User JBNBR 30 A 1 Job Number JBTYPE 1 Job Type JBSTYP Job Subtype JBCPU CPU Seconds JBRSP Total Response Seconds JBNTR Interactie Transactions Report column formatting and summary functions Summary functions: 1-Total, 2-Aerage, 3-Minimum, 4-Maximum, 5-Count Oerrides Field Summary Column Dec Null Dec Numeric Name Functions Spacing Column Headings Len Pos Cap Len Pos Editing JBNAME 0 10 Job Name JBUSER 2 10 Job User Figure 172. Query 1 Copyright IBM Corp. 1998,

288 IBMQuery for iseries 6/17/97 15:15:21 Page 2 Report column formatting and summary functions (continued) Summary functions: 1-Total, 2-Aerage, 3-Minimum, 4-Maximum, 5-Count Oerrides Field Summary Column Dec Null Dec Numeric Name Functions Spacing Column Headings Len Pos Cap Len Pos Editing JBNBR 2 6 Job Number JBTYPE 2 1 Job Type JBSTYP 2 1 Job Subtype JBCPU CPU Seconds JBRSP 1 2 Total Response Seconds JBNTR Interactie Transactions Report breaks Break New Suppress Break Leel Page Summaries Text 1 No No Selected output attributes Output type Database file Form of output Summary only Line wrapping No Database file output File CA4QRY Library BEST1 Member *FILE Data in file Replace file For a new file: Authority *LIBCRTAUT Text about the file CA4 QRY Print definition No Figure 173. Query 1 IBMQuery for iseries 6/17/97 15:15:21 Page 3 Output file record format Output record length Field list: Field Begin Len Dec Null Data Type Text BREAKLVL 1 1 Character BREAK LEVEL OVERFLOW 2 1 Character OVERFLOW FLAG JBNAME 3 10 Character Job Name JBUSER Character Job User JBNBR 23 6 Character Job Number JBTYPE 29 1 Character Job Type JBCPU Zoned decimal JBCPU TOTAL JBRSP Zoned decimal JBRSP TOTAL JBNTR Zoned decimal JBNTR TOTAL Figure 174. Query BEST/1 Capacity Planning Tool V5R1

289 5769QU1 V4R2M IBM Query for iseries ABSYSTEM 6/17/97 15:15:22 Page 1 Query QRY2 Library BEST1 Query text Query CCSID Collating sequence Hexadecimal Processing options Use rounding Yes (default) Ignore decimal data errors..... No (default) Ignore substitution warnings.... Yes Special conditions *** All records selected by default *** ***. is the decimal separator character for this query *** Selected files ID File Library Member Record Format T01 CA4QRY BEST1 CA4QRY CA4QRY Result fields Name Expression Column Heading Len Dec RES1 jbrsp01/(jbntr ) RT 8 3 CPU jbcpu01/1000 CPU seconds 6 3 Ordering of selected fields Field Sort Ascending/ Break Field Name Priority Descending Leel Text JBNAME Job Name JBUSER Job User JBNBR Job Number JBTYPE Job Type RES1 CPU Figure 175. Query 2 (page 1 of 2) IBMQuery for iseries 6/17/97 15:15:22 Page 2 Report column formatting and summary functions Summary functions: 1-Total, 2-Aerage, 3-Minimum, 4-Maximum, 5-Count Oerrides Field Summary Column Dec Null Dec Numeric Name Functions Spacing Column Headings Len Pos Cap Len Pos Editing JBNAME 0 10 Job Name JBUSER 2 10 Job User JBNBR 2 6 Job Number JBTYPE 2 1 Job Type RES1 2 RT 8 3 CPU 2 CPU 6 3 seconds Selected output attributes Output type Display Form of output Detail Line wrapping No Figure 176. Query 2 (page 2 of 2) Appendix B. Query to Print JOB/TASK Types and CPU Utilization 269

290 06/23/97 17:03:11 PAGE 1 RT CPU Job Job Job Job seconds Name User Number Type #-0100 V #A0005 V #B005A V #B005E V #B0056 V #B006D V #B0060 V #S000E V #T000C V #T0010 V #T0020 V #T0021 V #T0022 V #T0023 V #T0024 V #T0025 V #30002 V #40046 V #40047 V #50004 V #7004F V CCIOMV CPMGR V CPPS V DBIO00 V DBIO01 V DBIO02 V DBIO03 V DBIO04 V DBIO05 V DBIO06 V DBIO07 V DSP08 ITSCID I DSP08 ITSCID I ERRLOG V FLRTR V FS0001 V GRAPHICS GSID B GRAPHICS GSID B GRAPHICSS1 GSID I GRAPHICSS2 GSID I GUIPS2 ITSCID B GUIPS2 ITSCID B GUIPS2S1 QSECOFR I PRT03 QSPLJOB W QALERT QSYS S QBATCH QSYS M QCMN QSYS M QCTL QSYS M QDBSRV1 QSYS S QDBSRV2 QSYS S QDCPOBJ1 QSYS S QDCPOBJ2 QSYS S QDIA QSNADS B QDIAHSTPRT QSNADS B Figure 177. Sample Query Output (edited for clarity) 270 BEST/1 Capacity Planning Tool V5R1

291 Appendix C. Conerting BEST/1 Models and Migrating Data This appendix includes information on configuration changes to pre-v4r2 BEST/1 models and how to migrate data from System/36 to the AS/400 System/36 Enironment. For more information on CISC-to-RISC conersion factors, see Editing CISC-to-RISC Conersion Factors on page 105. Configuration Changes to Pre-V4R2 BEST/1 Models The following table describes the configuration changes. The configuration of a pre-v4r2 model can be changed when read into BEST/1. This is generally done to add IOAs to the configuration that are required in V4R2 but were not supported in earlier releases. Some IOP features support disk actiity (disk IOPs and some multifunction IOPs) and some IOP features support communications actiity (communications IOPs and multifunction IOPs). BEST/1 can change IOP connections when the original configuration is not compatible with the current hardware specifications. For example, if a multifunction IOP is attached to disk controllers, but the hardware table shows that the IOP does not support disk actiity, the controllers and arms are deleted. These types of changes are indicated by either change, create, or delete messages. In addition, one or more of the following messages can be displayed after a model is read: Table 18. Read Conersion Messages Message ID First-Leel Text When Message Is Displayed PCY1 IOP FEATURE <feature> DOES NOT SUPPORT DISK OPERATIONS. When an IOP shows connections to either disk controllers or disk IOAs, and the feature is either a communications IOP or a multifunction IOP which does not allow disk connections. In this situation, all disk controllers, disk IOAs, and disk arms are deleted from the IOP. PCY2 IOP FEATURE <feature> DOES NOT SUPPORT COMMUNICATIONS OPERATIONS. When an IOP shows connections to communications IOAs and/or communications lines, and the IOP is a disk IOP. In this situation, all communications IOAs and lines are deleted from the IOP. Copyright IBM Corp. 1998,

292 Table 18. Read Conersion Messages (continued) PCY3 PCY4 PCY5 PCY6 IOP FEATURE <feature> CAN ONLY CONNECT TO DISK IOAS, NOT DISK CONTROLLERS. IOP FEATURE <feature> CAN ONLY CONNECT TO DISK CONTROLLERS, NOT DISK IOAS. IOP FEATURE <feature> CAN ONLY CONNECT TO LINE RESOURCES THROUGH COMMUNICATIONS IOAS. IOP FEATURE <feature> CANNOT CONNECT TO COMMUNICATIONS IOAS. When a multifunction IOP shows connections to disk controllers, and the IOP feature only allows connections to disk arms through disk IOAs. In this situation, the first disk controller is changed to a disk IOA. If the multifunction IOP feature allows connections to more than one disk IOA, additional disk controllers are changed to disk IOAs. Once the maximum number of disk IOAs hae been changed from disk controllers, arms under any remaining disk controllers are connected to one of the disk IOAs. This message is displayed when you are reading a pre-v4r2 model containing a V4R1 multifunction IOP. When an IOP shows connections to disk IOAs, and the IOP feature only allows connections to disk arms through disk controllers. In this situation, the first disk IOA is changed to a disk controller whose feature matches the feature of the first disk arm. Additional controllers are created for each different disk arm feature. When a multifunction IOP shows direct connections to communications lines, and the IOP feature requires communications connections through a communications IOA. In this situation, communications IOAs are created under the multifunction IOP and the communications lines are connected to the new communications IOAs. When an IOP shows connections to communications IOAs, and the IOP feature does not support connections to communications IOAs. In this situation, communications IOAs are deleted under the multifunction IOP and the communications lines are connected directly to the IOP. System/36 Migration Utility When migrating an application from System/36 to the System/36 Enironment, the performance depends on the System/36 application structure. The BEST/1 System/36 Migration Utility uses the System/36 measurement performance data, and through modeling, translates the data into performance data for the OS/400 capacity planning tool (BEST/1). The BEST/1 System/36 Migration Utility translates System/36 measured performance data into OS/400 performance data for BEST/1 based on the following assumptions: The BEST/1 Migration Utility should only be used to measure and model those applications that will be migrated to the System/36 Enironment There is no Multiple Requester Terminal (MRT) program bottleneck on the System/36. If there is a bottleneck, the performance tool s results may be incorrect because of incorrect workload oerheads. The incorrect results are usually optimistic, which means the predicted external response times are low. The batch actiity on the System/36 is at a minimum. 272 BEST/1 Capacity Planning Tool V5R1

293 The LAN and WAN throughput is proportional to the number of actie LAN and WAN workstation operations measured on the System/36 using the System Measurement Facility (SMF). The number of actie LAN and WAN display stations are proportional to the number of LAN and WAN workstation operations. The assumptions in BEST/1 Assumptions and Conditions still apply. The information in Selecting Data for Capacity Planning Measured Workloads is of particular importance. The ability of the BEST/1 System/36 Migration Utility to translate System/36 measured performance data into System/36 Enironment performance data for BEST/1 is limited by the following: The System/36 migration package is used for migration to the System/36 Enironment on the iseries serer. BEST/1 is not a disk storage capacity sizer. It does not predict the disk storage capacity needed, but it predicts the number of disk arms needed for performance. BEST/1 does not model the wait time for the MRT programs. Too many display stations attached to a MRT program on the System/36 Enironment may result in excessie wait times, which are not shown in the model results. Migration Utility Instructions for the System/36 MIGUTL Procedure Use the Migration Utility to help select a comparable OS/400 configuration when you are migrating from the System/36 to the System/36 Enironment. Before you use the Migration Utility on the System/36, be sure the program temporary fix (PTF) leel DK3700 is installed. This PTF allows additional, necessary counters to be captured by SMF. To check whether the PTF leel is correct, type DUMP PTF,CRT on the System/36 and check the DK leel in the top right portion of the display. The MIGUTL procedure performs the following functions: Runs SMF to collect system measurement data. Note: SMF runs for 2 hours and requires approximately 2000 blocks of disk space for the files. Runs the SMFDATA procedure. Saes the file on diskettes with a VOLID of MIGUTL. The sae checks for the correct VOLID of MIGUTL and issues an error if the correct diskette is not in slot 1. Deletes the data collection files created by SMF. If the measurement process is run with remote communications such as DDM, ICF, and so on, the modeled response time per transaction for your interactie display stations may be high because system communications actiity is included with the interactie workload. Howeer, the total system workload will be characterized. Run the Migration Utility during a peak workload period for the workload to be migrated. To use the Migration Utility, follow these instructions: 1. Format three diskettes (either 8 inch or 5-1/4 inch) with a VOLID of MIGUTL by entering the following command: Appendix C. Conerting BEST/1 Models and Migrating Data 273

294 INIT MIGUTL,,FORMAT2,S1,S3 Note: The diskettes may be remoed while MIGUTL is running but they must be replaced when SMF stops running (2 hours). 2. Enter the following command at any workstation: // EVOKE MIGUTL This makes the job a batch job. Note: Should any stops occur while running SMF, select option 2 so the other job steps continue. Stops may indicate that the SMF data file is full or the SMF task is not actie. 3. Hae the diskettes taken to the iseries serer for capacity planning with BEST/1. When the measurement is running, there should be a significant amount of interactie work present. For example, do not take the measurement oer a lunch hour period when few users are actie. Otherwise, the measurement data will not be representatie of the workload that will be migrated to the iseries serer. Example of Migrating System/36 Measured Data This example shows you how to use the BEST/1 System/36 Migration Utility to translate System/36 measured data, through modeling, into System/36 Enironment performance data for BEST/1. Note: The numbers shown in this example are for demonstration purposes only and do not represent any real results. 1. Follow the instructions in Migration Utility Instructions for the System/36 MIGUTL Procedure on page Put the first diskette, with the VOLID of MIGUTL, into the OS/400 diskette drie. Verify the name of the diskette unit on the system. 3. Enter the Start BEST/1 (STRBEST) command to begin working with the BEST/1, the capacity planning tool. You see the display with the BEST/1 disclaimer. 4. Press the Enter key. The BEST/1 for the AS/400 main menu appears. 274 BEST/1 Capacity Planning Tool V5R1

295 BEST/1 for the AS/400 Select one of the following: 1. Work with BEST/1 models 5. Create BEST/1 model from performance data 10. Work with results 50. About BEST/1 60. More BEST/1 options Selection or command ===> 60 F3=Exit F4=Prompt F9=Retriee F12=Cancel 5. From this menu, select option 60 (More BEST/1 options). The More BEST/1 options menu appears. Select one of the following: More BEST/1 Options 1. Work with job classification members 2. Work with workload members 3. Work with configuration members 4. Work with hardware members 5. Work with results members 6. Work with analysis parameters members 10. Hardware characteristics menu 11. Edit Analysis Parameters 20. Conert MDLSYS files 21. Migrate S/36 workload 51. Moing from MDLSYS to BEST/1 Selection or command ===> 21 F3=Exit F4=Prompt F9=Retriee F12=Cancel 6. Select menu option 21 (Migrate S/36 workload). The Migrate S/36 Workload (QCY36MU) display appears. Appendix C. Conerting BEST/1 Models and Migrating Data 275

296 Type choices, press Enter. Migrate S/36 Workload (QCY36MU) Model Name... EXAMPLE36 Name Model Library... QPFRDATA Name Model Description... Migrate S/36 model Deice Name... TAP01 Name Bottom F3=Exit F4=Prompt F5=Refresh F12=Cancel F13=How to use this display F24=More keys 7. Type a model member name in the Model name field. Optionally, you may type a description of the model in the Model description field, oerride the source deice in the Deice name field and oerride the target library in the Model library field. The last field on the display appears if the deice you are using is a tape rather than diskette. In this example, EXAMPLE36 is typed as the model name and Migrate S/36 model to BEST/1 is typed as the description. 8. Press the Enter key. A model named EXAMPLE36 is created in the QPFRDATA library and the More BEST/1 Options menu appears again. 9. To use the model, press F12 to return to the BEST/1 for the AS/400 main menu. Select one of the following: 1. Work with BEST/1 models BEST/1 for the AS/ Create BEST/1 model from performance data 10. Work with results 50. About BEST/1 60. More BEST/1 options Selection or command ===> 1 F3=Exit F4=Prompt F9=Retriee F12=Cancel 10. Select menu option 1 (Work with BEST/1 models). The Work with BEST/1 Models display appears. 276 BEST/1 Capacity Planning Tool V5R1

297 Library... QPFRDATA Name Work with BEST/1 Models Type options, press Enter. 1=Create 2=Change 3=Copy 4=Delete 5=Work with 6=Print 7=Rename Opt Model Text Date Time 5 MIGRATE36 02/05/92 09:02:58 _ V2R1M /03/92 11:05:15 Command ===> F3=Exit F4=Prompt F5=Refresh F9=Retriee F12=Cancel F15=Sort by model F16=Sort by text F19=Sort by date and time Bottom 11. On the Work with BEST/1 Models display, the name of the S/36 migration model should be displayed. Note: If the newly created model does not appear in the list, ensure that the appropriate library is specified in the LIBRARY field at the top of the display. To work with the model: a. Type a 5 in the Opt field by the appropriate model name. b. Press the Enter key. The Work with BEST/1 Model menu appears. Work with BEST/1 Model Performance data...: Model/Text: MIGRATE36 QPFRDATA (MAR10AM) Select one of the following: 1. Work with workloads 2. Specify objecties and actie jobs 5. Analyze current model 6. Analyze current model and gie recommendations 7. Specify workload growth and analyze model 10. Configuration menu 11. Work with results More... Selection or command ===> 10 F3=Exit F4=Prompt F9=Retriee F12=Cancel F15=Sae current model F17=Analyze using ANZBESTMDL F22=Calibrate model F24=More keys 12. You can change the model configuration at this point. BEST/1 defaults to the B10 which is the slowest processor. A possible starting point for the configuration would be a current 9402 configuration. Seeral 9402 configurations are supplied in BEST/1. Appendix C. Conerting BEST/1 Models and Migrating Data 277

298 13. To change to a sample configuration: a. Select option 10 (Configuration menu). The Configuration menu appears. Configuration CPU M odel...: B10 Comm IOPs...: 0 Main stor (MB)...: 72 LAN lines...: 0 Main stor pools...: 4 WAN lines...: 0 Disk IOPs...: 1 Multifunction IOPs...: 0 Disk ctls...: 3 Disk IOAs...: 0 Disk arms...: 3 Comm IOAs...: 0 ASPs...: 1 IPCS IOAs...: 0 Select one of the following: 1. Change CPU and other system alues 2. Work with disk resources 3. Edit ASPs 4. Edit main storage pools 5. Work with communications resources Selection or command ===> F3=Exit F4=Prompt F9=Retriee F12=Cancel F13=Check configuration F17=Correct configuration F24=More keys b. Press F14 (Replace with saed configuration). c. Change the Library field at the top of the display to QPFR. d. Type a 1 in the Opt field, next to the desired configuration. e. Press Enter. This will be the configuration that is used in the model. 14. You can use this as you would any other BEST/1 model. 15. To analyze the model, select any of the Analyze menu options. Notes: 1. Because of the limited amount of data aailable at conersion, there are seeral areas within the model that should be reiewed before the model is analyzed. 2. Disk serice times should be examined to assure that they are not excessiely large. The original data does not include information about serice times, so the serice times are deried from the IOP and arm utilizations. 3. The permanent write percentage in some transactions could be calculated to be 100%. This should not be a big factor in the modeling unless checksumming, mirroring, or other methods of data protection will be modeled. 4. The ratio of read to writes might not be appropriate. The information in the original data supplies BEST/1 with the percentage of writes found in the data. This percentage is applied across all workload. In reality, different transaction streams could hae significantly different read to write ratios. 5. Some communications details might be missing and should be added before the model is analyzed. 6. The main storage pools sizes might need to be adjusted. 278 BEST/1 Capacity Planning Tool V5R1

299 Appendix D. BEST/1 Principles When you use BEST/1 capacity planning you should hae some knowledge of the principles used in the program. You should also understand the relationship between system resource utilization and system performance. This section presents a basic explanation of the queuing equation concepts used in capacity planning. The BEST/1 queuing equations combine the input data, which shows the uses of the system by interactie and batch processing, into a set of estimates to show the contention for the system resources: Processing unit (CPU) Main storage Disk Communication lines When multiple jobs simultaneously need a resource, contention occurs. The result is that a job takes longer to complete its task than it would in a dedicated enironment where no other jobs are contending for the resource. In many instances, where resource contention occurs, each requester has the same chance as any other to use the resource. This occurs, for example, in the system when seeral interactie jobs need to use the processing unit, disk, or main storage, and these jobs run at the same priority. When contention occurs, the jobs that cannot get the resource must wait for a period of time until it becomes aailable. This resource wait time increases the total time required to use the resource (for example, from the time it is requested until the time it is released). The amount of time a job must wait for the resource (the queuing time) depends on the utilization of the resource. Assume that in a noncontention (or dedicated) enironment, an interactie transaction normally uses a half-second of processing unit time before it completes. If the processing unit is 50% utilized (on the aerage) by a number of jobs, all with the same priority, you can use queuing theory to calculate that the job requires 1 second to complete (the total time is the sum of the processing unit serice time and the processing unit queuing time). The job still uses a half-second of processing unit time, but because of the queuing effect, it takes twice as long to use that half-second. This multiplying effect, called the queuing multiplier (QM), can be estimated by the equation shown in Figure QM= where u is the utilization of the resource (1 - u) (50% utilization is a u of 0.5) Figure 178. Estimating the Queuing Multiplier From this equation you can see that the lower the resource utilization, the lower the alue of QM. Other alues for QM for a gien u are shown in Figure 179 on page 280. Copyright IBM Corp. 1998,

300 Figure 179. Queuing Multiplier for Gien Utilization of the Resource The alues shown for the QM indicate that the higher the utilization of a resource, the larger the QM alue. Consequently, it takes longer for each requester to obtain serice from the resource. In any system, the higher the utilization of a resource, the longer each request waits to use that resource. When total time for a single-serer, single-queue serice (such as a disk drie) is calculated, the QM equation is used. When multiple-serer, single-queue serice time (such as the actiity leel slots within a storage pool) or single-serer, multiple-queue serice time (such as the OS/400 processing unit) are calculated, the equations for the QM are different. Howeer, the principle and the effect are the same. Note: The alue for the QM is independent of the speed of operation of the serer (the resource); the QM alue is the same for a gien utilization of a serer. The preceding example forms the basis for the calculations performed by capacity planning. Using system measurements as input, capacity planning output closely parallels system performance data. In some cases the output may not match, but it is close enough to be useful. The primary function of BEST/1 is to apply queuing equations to the input data to determine the contention for system resources. The output shows the total system utilization of these resources, including an estimate of batch utilization of resources (using the assumption that batch runs at a lower priority than interactie). Deiations between predictions and reality are most often obsered when one or more of the following conditions are present: Utilization of a resource exceeds 90%, particularly the CPU. 280 BEST/1 Capacity Planning Tool V5R1

301 Response Time Variation Wide ariations in system load or configuration existed within the set of selected measured interals. Large ariations in the nature of transaction with a workload exist. Important aspects of a workload can not be detected or modeled. For example, an application code that is single-threaded, actual working set size, or actual paging cure. BEST/1 does not consider separately the application design, file and record contention, transaction types, or ariations in interactie load oer a period of time. Instead, the input data of transaction processing unit time and disk I/O proide the effect of the design, the system load, and the system configuration. For this reason, any system input to capacity planning should be from a system that is properly tuned and running under expected conditions of loading. The transaction response times on a system ary to some degree around the aerage transaction response time. At high utilizations, interactie response times ary significantly around the aerage alue, and in some cases may fluctuate widely. You need to consider the effect of the response time ariations from the aerage. If you are achieing your objecties for interactie response time, you need to understand the effect of serer utilization and queuing on your objecties. If you install additional interactie workload on a system that is currently proiding satisfactory response time, the additional workload could cause the total interactie processing unit utilization to increase. Depending on the amount of additional load, both the aerage response time for current applications and the amount of ariation from the aerage may increase. Appendix D. BEST/1 Principles 281

302 282 BEST/1 Capacity Planning Tool V5R1

303 Appendix E. Manual Batch Window Modeling Basic Concepts and Formulas This appendix shows a manual approach for calculating batch job run time. The basic equation for batch job run-time is: Job Run Time = CPU Response + Disk I/O Response + Other Wait time The last part of the formula takes into account data base contention, tape waiting time and other object contentions. For simplicity, most models take into account only the first two terms of the equation. Assuming the time the job expends waiting for asynchronous disk I/Os is negligible, the formula can be stated as: Batch Run Time = [(CPU Serice Time x CPUQM) + x Disk Serice Time x DISKQM)] x Calibrating Factor (PDIO Where: CPU = Total CPU time used by the job CPUQM= CPU Queuing Multiplier PDIO = Total number of Synchronous Physical Disk I/O operations performed by the job DISKQM= Disk Queuing Multiplier Figure 180. General Batch Run Time Formula PDIO should include all the I/O that the job has to wait for, including asynchronous disk I/O that was waited on and pending disk I/O operation page faults which are usually not counted under synchronous I/O figures in the reports. One common unit of batch workload is the Logical Disk I/O (LDIO) operation. This unit of work is sometimes preferred oer Physical Disk I/O (PDIO) operation. If a job processes the same data in multiple runs without changing the application, the number of records processed or the file blocking, the LDIO counter would remain unchanged. On the other hand, If the run enironment aries from one run to the next for the same job, you may find that the number of PDIO issued by the job aries also. In terms of LDIOs the preceding formula can be stated as: Run Time = (LDIO x CPUQMx (CPU/LDIO) + ( (PDIO/LDIO) x Disk Serice Time x DISKQM) ) x Calibrating Factor Figure 181. Detailed Batch Run Time Formula Queuing Multipliers CPU and Disk Queuing multipliers reflect the effect of concurrent access to the same serer. The theory behind both multipliers is the same, but CPU Queuing Copyright IBM Corp. 1998,

304 multiplier formula is somewhat more cumbersome because has to reflect different access priorities and seeral serers. U1 = CPU utilization for all jobs at higher priority U2= CPU utilization at the current priority leel N = Number of jobs competing for the CPU at the current priority leel p = number of processors (E90 = 3, E80 and D80 = 2) Figure 182. CPU Queuing Multiplier Formula 1 DISKQM= 1 - (Util x (n-1)/n) Util = Disk utilization n = Number of concurrent requests to the disk. If batch job is running stand-alone DISKQM= 1 Figure 183. Disk Queuing Multipliers Example To use the formula in Figure 180 on page 283 we need Total CPU, PDIO, CPU and disk utilizations. Total CPU for the job can be found in the system report (PRTSYSRPT) selecting exclusiely the specific batch job. The releant system report section is shown in Figure 185 on page 285. There is no way to get the total alue for PDIO from the Performance Tools reports. You may get the actual alue by performing a query to the QAPMJOBS file. In Figure 184 you can find the SQL ersion of such a query but you might use Query for iseries or any other query product. If you hae only the Performance Tools reports you can get a lower bound for PDIO looking at the system report for the specific job as shown in Figure 186 on page 285. SELECT SUM(JBDBR + JBNDB + JBNDW + JBDBW + JBIPF + JBWIO) FROM MYLIB/QAPMJOBS WHERE JBNBR = 'xxxxxx' GROUP BY JBNBR Figure 184. SQL Query to Calculate PDIO - Batch Run Time CPU and disk utilization can be found in the same report for the total workload, but selecting only the period of time in which the job ran, (see Figure 187 on page 285). 284 BEST/1 Capacity Planning Tool V5R1

305 System Report 7/27/92 15:10:16 Workload Page 0001 DSPOBJ 1 Member... : DSPOBJ1 Model/Serial.. : D45/10-A1002 Main storage.. : 80.0 M Started.... : 07/23/92 14:16:48 Library.. : QPFRAAID05 System name... : ABSYSTEM Version/Release : 2/ 2.0 Stopped.... : 07/23/92 15:07:59 Non-Interactie Workload Job Number Logical DB Printer Communications CPU Per Logical Type Of Jobs I/O Count Lines Pages I/O Count Logical I/O I/O /Second Batch Total/ Aerage Total CPU Utilization : 13.3 Figure 185. Non-Interactie Workload - One Batch Job Selected System Report 7/27/92 15:10:16 Resource Utilization Expansion Page 0003 DSPOBJ 1 Member... : DSPOBJ1 Model/Serial.. : D45/10-A1002 Main storage.. : 80.0 M Started.... : 07/23/92 14:16:48 Library.. : QPFRAAID05 System name... : ABSYSTEM Version/Release : 2/ 2.0 Stopped.... : 07/23/92 15:07:59 Job CPU Cum Disk I/O CPU Per I/O DIO /Sec -- Priority Type Util Util Sync Async Sync Async Sync Async Batch ,195 28, Total/Aerage 78,195 28, Figure 186. Resource Utilization Expansion - One Batch Job Selected System Report 7/27/92 15:07:29 Resource Utilization Expansion Page 0003 DSPOBJ 1 Member... : DSPOBJ1 Model/Serial.. : D45/10-A1002 Main storage.. : 80.0 M Started.... : 07/23/92 14:16:48 Library.. : QPFRAAID05 System name... : ABSYSTEM Version/Release : 2/ 2.0 Stopped.... : 07/23/92 15:07:59 Job CPU Cum Disk I/O CPU Per I/O DIO /Sec -- Priority Type Util Util Sync Async Sync Async Sync Async Batch ,106 1, System , Client Access Interactie Batch Spool Interactie S/ Client Access , Batch AutoStart System Client Access , Spool Batch AutoStart System Client Access Batch ,689 31, Eoke System System Total/Aerage 105,939 33, Figure 187. Resource Utilization Expansion - All Jobs Appendix E. Manual Batch Window Modeling 285

306 System Report 7/27/92 15:07:29 Disk Utilization Page 0005 DSPOBJ 1 Member...: DSPOBJ1 Model/Serial.. : D45/10-A1002 Main storage..: 80.0 MStarted...: 07/23/92 14:16:48 Library..: QPFRAAID05 System name...: ABSYSTEMVersion/Release : 2/ 2.0 Stopped...: 07/23/92 15:07:59 Size IOP IOP ASP CSS --Percent-- Op Per K Per Aerage Time Per I/O Unit Type (M) Util ID ID ID Full Util Second I/O Serice Wait Response Aerage Figure 188. Disk Utilization - Batch Run Time Computing Batch Run Time for Current Configuration Total CPU time can be computed multiplying Logical DB I/O count by CPU per logical I/O as shown in Figure 185 on page 285, that is 637 * = seconds. To calculate the CPU queuing multiplier, U1 and U2 can be obtained from Figure 187 on page 285. U1 is in the row before the job s priority under the title Cum Util, which is 34.5 in our example. U2 is found in the row with the batch job s priority under the title CPU Util, which is 14.3 in our example. Jobs with the same priority of our batch job were almost negligible, so we are going to take N=1 in the formula in Figure 182 on page 284 and thus CPUQM=1/( )= Disk response time (DISKQM * Disk Base Serice Time) can be obtained directly from Figure 188, under the column response in the row Aerage. In our example this alue is seconds. PDIOs are calculated using the query in Figure 184 on page 284 for the specific member and job number. In our example this alue is 80,926. So our model predicts: Batch Run Time = x ,926 x = = 2322 seconds = 38.7 minutes Our actual batch job took 41 minutes, so our model is in the 15% error range, which is considered acceptable. To calibrate the model we hae to multiply the results of our model by (41/38.7) for our example. This alue is called the calibrating factor. Computing Batch Run Time for a Different CPU If we consider an upgrade to an E50, only the first term of the equation in Figure 180 on page 283 aries, assuming that no changes to disk configuration hae occurred. We hae to calculate new Total CPU time and CPU Queuing multipliers for the new model. Total CPU time would decrease if the new model is more powerful and the decrease factor is gien by: (Relatie Performance Current Model)/Pc CPU Time = Decrease Factor (Relatie Performance New Model)/Pn 286 BEST/1 Capacity Planning Tool V5R1

307 Where Pc = Number of processors in current model Pn = Number of processors in new model Note: You hae to consider that adding more processors increases your Relatie CPU power, but does not necessarily decrease your job s total CPU time, which depends on the speed of each processor. Using the alues in Relatie CPU Power Table, it follows that total CPU time in a model E50 would be x (3.7/6.2) = Queuing multipliers must also be changed to reflect new CPU power. If there are at least as many jobs as processors in the system, CPU utilization would decrease proportionally to the Relatie CPU Power, that is: (Relatie Performance Current Model) CPU Utilization = Decreasing Factor (Relatie Performance New Model) Multiplying U1 and U2 by the decreasing factor allows us to calculate our new CPU Queuing multiplier, which is in our example. The final computation for the batch run time in our new model E50 is: Batch Run Time = ( ( x 1.259) ) x (Calibrating Factor) = x (41/38.7) = seconds = 35.4 Minutes Relatie CPU Power Table The following relatie CPU power table is proided for assistance in batch modeling. Appendix E. Manual Batch Window Modeling 287

308 CPU Relatie CPU Relatie Model Performance Model Performance B E B E B E B E B E B E B E B E B E C E C E C E C E C F D F D F D F D F D F D F D F D F D F D F D F D F E F Relatie CPU Multiplier Figure 189. Batch Example: Relatie CPU Performance Multipliers 288 BEST/1 Capacity Planning Tool V5R1

309 Appendix F. Externally Described Files BEST/1 results and models can be saed in Externally Described Files (EDF). BEST/1 uses the QACYEDF template from library QPFR when it saes results and models as EDF file members. EDF results and models can be read in both interactiely and from other OS/400 applications. OS/400 query or user-created logical files enable you to access data in EDF file members. EDF results are saed as members of QACYRESE file in a user-specified library. They are saed in the following format: 1. Analysis Summary Report records: RECKEY Record key SUBKEY 400 INTERS1 Memory size INTERS3 Number of disk IOPs INTRES4 Number of disk controllers INTRES5 Number of disks INTRES6 Number of WAN IOPS INTRES7 Number of local WS controllers INTRES8 Number of WAN WS controllers INTRES9 Number of CPU processors INTRES10 Number of LAN IOPs INTRES11 Number of WAN lines INTRES12 Number of LAN lines INTRES13 Number of LAN controllers INTRES14 Number of multifunction IOPs INTRES15 Number of disk IOAs Copyright IBM Corp. 1998,

310 INTRES16 Number of LAN IOAs INTRES17 Number of WAN IOAs INTRES18 Number of IPCS IOAs FLOATRES1 CPU util FLOATRES2 Disk IOP util FLOATRES3 Disk controller util FLOATRES4 Disk arm util FLOATRES5 WAN IOP util FLOATRES6 Local WS controller util FLOATRES7 WAN WS controller util FLOATRES8 Interactie CPU util FLOATRES9 Non-interactie CPU util FLOATRES10 Interactie throughput FLOATRES11 Non-interactie throughput FLOATRES12 Interactie local response time FLOATRES13 Interactie WAN response time FLOATRES14 Interactie LAN response time FLOATRES15 Non-interactie local response time FLOATRES16 Non-interactie WAN response time FLOATRES17 Non-interactie LAN response time FLOATRES18 LAN IOP util FLOATRES19 WAN line util 290 BEST/1 Capacity Planning Tool V5R1

311 FLOATRES20 LAN line util FLOATRES21 LAN controller util FLOATRES22 Multifunction IOP util FLOATRES23 Disk IOA util FLOATRES24 LAN IOA util FLOATRES25 WAN IOA util FLOATRES26 IPCS IOA util SHSTRRES1 CPU model SHSTRRES2 Period name SHSTRRES3 Release leel HUGESTRRES Printed report text 2. Workload Report records: RECKEY Record key SUBKEY 401 FLOATRES1 Interactie CPU util FLOATRES2 Non-interactie CPU util FLOATRES3 Interactie throughput FLOATRES4 Non-interactie throughput FLOATRES5 Internal interactie response time FLOATRES6 Local interactie response time FLOATRES7 WAN interactie response time FLOATRES8 Local interactie CPU response time FLOATRES9 Local interactie I/O response time Appendix F. Externally Described Files 291

312 FLOATRES10 Local interactie storage response time FLOATRES11 Local interactie other response time FLOATRES12 WAN interactie CPU response time FLOATRES13 WAN interactie I/O response time FLOATRES14 WAN interactie storage response time FLOATRES15 WAN other interactie response time FLOATRES16 Interactie I/O rate FLOATRES17 Non-interactie I/O rate FLOATRES18 Actie jobs FLOATRES19 Number of transactions FLOATRES20 LAN interactie response time FLOATRES21 LAN interactie CPU response time FLOATRES22 LAN interactie I/O response time FLOATRES23 LAN interactie storage response time FLOATRES24 LAN interactie other response time FLOATRES25 LAN interactie communications response time FLOATRES26 Local interactie communications response time FLOATRES27 WAN interactie communications response time FLOATRES28 Local non-interactie response time FLOATRES29 Local non-interactie CPU response time FLOATRES30 Local non-interactie response time FLOATRES31 Local non-interactie storage response time 292 BEST/1 Capacity Planning Tool V5R1

313 FLOATRES32 Local non-interactie other response time FLOATRES33 Local non-interactie communications response time FLOATRES34 WAN non-interactie response time FLOATRES35 WAN non-interactie CPU response time FLOATRES36 WAN non-interactie I/O response time FLOATRES37 WAN non-interactie storage response time FLOATRES38 WAN non-interactie other response time FLOATRES39 WAN non-interactie communications response time FLOATRES40 LAN non-interactie response time FLOATRES41 LAN non-interactie CPU response time FLOATRES42 LAN non-interactie I/O response time FLOATRES43 LAN non-interactie storage response time FLOATRES44 LAN non-interactie other response time FLOATRES45 LAN non-interactie communications response time SHSTRRES1 Workload name 3. ASP Report records: RECKEY Record key SUBKEY 402 SHSTRRES1 ASP number INTRES1 Number of arms FLOATRES1 ASP I/O rate FLOATRES2 ASP arm util FLOATRES3 Resered Appendix F. Externally Described Files 293

314 FLOATRES4 ASP arm response time FLOATRES5 Resered 4. Disk Resources Report records: RECKEY Record key SUBKEY 403 SHSTRRES1 IOP or IOA name INTRES1 Number of arms INTRES2 Resource type (0=IOP, 1=MFIOP, 3=IOA) FLOATRES1 IOP or IOA I/O rate FLOATRES2 IOP or IOA util FLOATRES3 IOP or IOA arm util FLOATRES4 Resered FLOATRES5 IOP or IOA arm response time FLOATRES6 Resered 5. POOL Report records: RECKEY Record key SUBKEY 404 SHSTRRES1 Pool name FLOATRES1 Ineligible wait FLOATRES2 Aerage actie FLOATRES3 Aerage ineligible FLOATRES4 Sync reads per second FLOATRES5 Pool size 294 BEST/1 Capacity Planning Tool V5R1

315 FLOATRES6 Pool actiity leel 6. Communications Report records: RECKEY Record key SUBKEY 407 SHSTRRES1 Communications resource name FLOATRES1 Communications resource utilization INTRES1 Communications resource type 7. Line Resource Report records: RECKEY Record key SUBKEY 408 SHSTRRES1 Line resource name SHSTRRES2 Communications IOP name FLOATRES1 Line oerhead util FLOATRES2 Line response time FLOATRES3 Line util FLOATRES4 Line speed INTRES1 Number of lines INTRES4 Resource type (0=Line, 1=IOA) 8. Recommendation Report RECKEY Record key SUBKEY 406 SHSTRRES1 Message ID HUGESTRRES Message EDF models are saed as members of QACYMDLE file in a user-specified library. They are saed in the following format: Appendix F. Externally Described Files 295

316 1. CPU model record: RECKEY Record key SUBKEY 100 INTRES1 Number of processors INTRES2 Memory size INTRES3 Number of LAN controllers INTRES4 Resered INTRES5 Resered INTRES6 Aerage line speed INTRES7 Number of WAN WS controllers INTRES8 Number of local WS controllers FLOATRES1 Measured CPU util FLOATRES2 Resered FLOATRES3 Resered FLOATRES4 Resered FLOATRES5 Measured interactie CPU util FLOATRES6 Measured IOP util FLOATRES7 Measured disk arm util FLOATRES8 Measured disk arm I/O rate FLOATRES9 Measured interactie response time FLOATRES10 Measured interactie throughput FLOATRES11 Measured non-interactie throughput FLOATRES12 Measured LAN line util 296 BEST/1 Capacity Planning Tool V5R1

317 FLOATRES13 Measured WAN line util FLOATRES14 Measured LAN IOP util FLOATRES15 Measured WAN IOP util FLOATRES16 Local WS controller serice time FLOATRES17 WAN WS controller serice time FLOATRES18 LAN controller serice time FLOATRES19 Measured multifunction IOP util FLOATRES20 Measured Disk IOA util FLOATRES21 Measured LAN IOA util FLOATRES22 Measured WAN IOA util FLOATRES23 Measured IPCS IOA util SHSTRRES1 System name SHSTRRES2 CPU model SHSTRRES3 Resered SHSTRRES4 Resered SHSTRRES5 Resered SHSTRRES6 Resered NAME1 Release leel NAME2 Name of the EDF processing program NAME3 Name of the EDF processing program library 2. Growth record: RECKEY Record key SUBKEY 113 Appendix F. Externally Described Files 297

318 INTRES1 Number of periods to analyze INTRES2 Change configuration flag INTRES3 Growth all periods flag FLOATRES1 Period 1 growth FLOATRES2 Period 2 growth FLOATRES3 Period 3 growth FLOATRES4 Period 4 growth FLOATRES5 Period 5 growth FLOATRES6 Period 6 growth FLOATRES7 Period 7 growth FLOATRES8 Period 8 growth FLOATRES9 Period 9 growth FLOATRES10 Period 10 growth NAME1 Period 1 name NAME2 Period 2 name NAME3 Period 3 name NAME4 Period 4 name NAME5 Period 5 name NAME6 Period 6 name NAME7 Period 7 name NAME8 Period 8 name NAME9 Period 9 name 298 BEST/1 Capacity Planning Tool V5R1

319 NAME10 Period 10 name NAME11 Current period name 3. ASP records: RECKEY Record key SUBKEY 101 INTRES1 Data Protection FLOATRES1 Measured ASP util FLOATRES2 Measured ASP queue length FLOATRES3 Measured ASP I/O rate SHSTRRES1 ASP number 4. IOP records: RECKEY Record key SUBKEY 102 FLOATRES1 Measured IOP util FLOATRES2 Resered FLOATRES3 Disk serice time FLOATRES4 LAN serice time FLOATRES5 Frame size FLOATRES6 Resered FLOATRES7 Resered FLOATRES8 Resered FLOATRES9 WAN serice time SHSTRRES1 IOP name Appendix F. Externally Described Files 299

320 SHSTRRES2 IOP feature 5. Disk controller and IOA records: RECKEY Record key SUBKEY 103 INTRES1 Cache efficiency INTRES2 Flag (1=DSC, 0=IOA) FLOATRES1 Resered FLOATRES2 Resered FLOATRES3 Resered FLOATRES4 Measured IOA util SHSTRRES1 Controller or IOA name SHSTRRES2 Disk drie or IOA feature 6. Line records: RECKEY Record key SUBKEY 111 INTRES1 Number of lines INTRES2 Resered INTRES3 Duplex flag INTRES4 Frame size FLOATRES1 Line speed FLOATRES2 Line oerhead SHSTRRES1 Line name SHSTRRES2 Line type 7. Arm records: 300 BEST/1 Capacity Planning Tool V5R1

321 RECKEY Record key SUBKEY 104 INTRES1 Blocks transferred INTRES2 RAID array ID FLOATRES1 Resered FLOATRES2 Msec per I/O FLOATRES3 Resered FLOATRES4 Resered FLOATRES5 Resered FLOATRES6 Resered SHSTRRES1 Disk arm name SHSTRRES2 Disk drie feature 8. Pool records: RECKEY Record key SUBKEY 105 INTRES1 Pool actiity leel INTRES2 Pool size SHSTRRES1 Pool ID SHSTRRES2 Pool name 9. System-IOP records: RECKEY Record key SUBKEY 106 SHSTRRES1 System name Appendix F. Externally Described Files 301

322 SHSTRRES2 IOP name 10. IOP-disk controller records: RECKEY Record key SUBKEY 107 SHSTRRES1 IOP name SHSTRRES2 Controller name 11. IOP-line records: RECKEY Record key SUBKEY 112 SHSTRRES1 IOP name SHSTRRES2 Line name 12. Disk controller-arm records: RECKEY Record key SUBKEY 108 SHSTRRES1 Controller name SHSTRRES2 Disk arm name 13. ASP-arm records: RECKEY Record key SUBKEY 109 SHSTRRES1 ASP number SHSTRRES2 Disk arm name 14. Workload-ASP records: RECKEY Record key SUBKEY 206 FLOATRES1 Read relatie count 302 BEST/1 Capacity Planning Tool V5R1

323 FLOATRES2 Write relatie count SHSTRRES1 Workload name SHSTRRES2 ASP number 15. Workload-line records: RECKEY Record key SUBKEY 208 FLOATRES1 Relatie count SHSTRRES1 Workload name SHSTRRES2 Line name 16. Workload records: RECKEY Record key SUBKEY 200 INTRES1 Resered INTRES2 Usage mode INTRES3 Workload type INTRES4 CPU architecture FLOATRES1 Number of local jobs FLOATRES2 Number of WAN jobs FLOATRES3 Number of LAN jobs FLOATRES4 Local interactie response time objectie FLOATRES5 WAN interactie response time objectie FLOATRES6 Local interactie throughput objectie FLOATRES7 WAN interactie throughput objectie Appendix F. Externally Described Files 303

324 FLOATRES8 Local non-interactie throughput objectie FLOATRES9 WAN non-interactie throughput objectie FLOATRES10 Measured local response time FLOATRES11 Measured WAN response time FLOATRES12 Measured interactie local throughput FLOATRES13 Measured interactie WAN throughput FLOATRES14 Measured non-interactie local throughput FLOATRES15 Measured non-interactie WAN throughput FLOATRES16 Period 1 growth FLOATRES17 Period 2 growth FLOATRES18 Period 3 growth FLOATRES19 Period 4 growth FLOATRES20 Period 5 growth FLOATRES21 Period 6 growth FLOATRES22 Period 7 growth FLOATRES23 Period 8 growth FLOATRES24 Period 9 growth FLOATRES25 Period 10 growth FLOATRES26 LAN response time objectie FLOATRES27 Interactie LAN throughput objectie FLOATRES28 Non-interactie LAN throughput objectie FLOATRES29 Measured interactie LAN response time 304 BEST/1 Capacity Planning Tool V5R1

325 FLOATRES30 Measured interactie LAN throughput FLOATRES31 Measured non-interactie LAN throughput SHSTRRES1 Workload name HUGESTRRES Workload description 17. Function records: RECKEY Record key SUBKEY 201 INTRES1 Internal function ID SHSTRRES1 Function name HUGESTRRES Function description FLOATRES1 Resered 18. Transaction records: RECKEY Record key SUBKEY 202 INTRES1 Internal transaction ID INTRES2 Transaction type FLOATRES1 CPU time FLOATRES2 Async DB reads FLOATRES3 Sync DB reads FLOATRES4 Async NDB reads FLOATRES5 Sync Ndb reads FLOATRES6 Async DB writes FLOATRES7 Sync DB writes Appendix F. Externally Described Files 305

326 FLOATRES8 Async NDB writes FLOATRES9 Sync NDB writes FLOATRES10 Permanent writes FLOATRES11 Resered FLOATRES12 Working set size FLOATRES13 Exceptional wait FLOATRES14 Characters transferred in FLOATRES15 Resered FLOATRES16 Resered FLOATRES17 DB paging exponent FLOATRES18 NDB paging exponent FLOATRES19 DB paging coefficient FLOATRES20 NDB paging coefficient FLOATRES21 Resered FLOATRES22 Working set size FLOATRES23 Characters transferred out FLOATRES24 Resered FLOATRES25 Resered SHSTRRES1 Internal transaction ID SHSTRRES2 Paging behaior 19. Workload-function records: RECKEY Record key SUBKEY BEST/1 Capacity Planning Tool V5R1

327 INTRES1 Internal function ID FLOATRES1 Function count FLOATRES2 Think time FLOATRES3 Delay time SHSTRRES1 Workload name 20. Function-transaction records: RECKEY Record key SUBKEY 205 INTRES1 Internal function ID INTRES2 Internal transaction ID FLOATRES1 Transactions per function FLOATRES2 CPU priority SHSTRRES1 Pool ID Appendix F. Externally Described Files 307

328 308 BEST/1 Capacity Planning Tool V5R1

329 Appendix G. Graphic Support Variables X-axis Variables This appendix lists the X-axis and Y-axis ariables. Note: You cannot graph IOA utilizations. 1 Period The name gien to an amount of time defined by the growth factor. 10 CPU Util The total utilization of the CPU; the percent of total time the CPU was busy running all jobs, both interactie and non-interactie. 11 Workload CPU Util The total utilization of the CPU; the percent of total time the CPU was busy running all jobs, both interactie and non-interactie within a workload. 12 Disk Busy The percent of time each disk arm was busy processing I/Os aeraged across all disk arms. 13 Disk IOP Busy The percent of time each disk IOP was busy processing I/Os aeraged across all disk IOPs. 20 Workload Inter Trans/hr The rate of interactie transactions processed per hour for each workload totaled across all workloads. 21 Workload Non-inter Trans/hr The rate of non-interactie transactions processed per hour for each workload totaled across all workloads. 22 Total Trans/hr The rate of all transactions (both interactie and non-interactie) processed per hour totaled across all workloads. 23 Workload I/Os per Sec The rate of I/Os per second processed for each workload totaled across all workloads. 24 Disk I/Os per Sec The rate of I/Os per second processed by each disk arm totaled across all workloads. 25 Disk IOP I/Os per Sec The rate of I/Os per second processed by each disk IOP totaled across all workloads. 26 Actie Jobs The total number of actie jobs for all workloads. This is the sum of all local, LAN, and WAN actie jobs totaled across all workloads, and can be found on the Specify Objecties and Actie Jobs display. 30 Rsp Time by Workload The aerage internal response time of interactie transactions aeraged Copyright IBM Corp. 1998,

330 Y-axis Variables across transactions for all workloads. This does not include any communications time. This alue is calculated by summing this alue for each workload and diiding the result by the total number of interactie transactions, and is gien in seconds. 31 Disk Rsp Time per I/O The total response time per I/O for all disk arms diided by the total number of I/Os for all disk arms. This includes both serice time and time spent waiting for the disk arm to be aailable, and is gien in milliseconds. 32 Aerage Interactie Response Time The oerall aerage external response times aeraged across interactie transactions for all workloads. This alue is gien in seconds. 40 LAN IOP util The percent of time each LAN IOP was busy transferring characters aeraged across all LAN IOPs. 41 LAN line util The percent of time each LAN line was busy transferring characters aeraged across all LAN lines. 42 WAN IOP util The percent of time each WAN IOP was busy transferring characters aeraged across all WAN IOPs. 43 WAN line util The percent of time each WAN line was busy transferring characters aeraged across all WAN lines. Note: X-axis ariables always return a single alue per period (whereas Y-axis ariables may return a alue for each indiidual component). 10 CPU Util The total utilization of the CPU; the percent of total time the CPU was busy running all jobs, both interactie and non-interactie. 11 Workload CPU Util The utilization of the CPU broken down by workload; the percent of time the CPU was busy running all jobs for each workload. 12 Disk Busy The percent of time each disk was busy processing I/Os. 13 Disk IOP Busy The percent of time each disk IOP was busy processing I/Os. 20 Workload Inter Trans/hr The rate of interactie transactions processed per hour for each workload. 21 Workload Non-inter Trans/hr The rate of non-interactie transactions processed per hour for each workload. 22 Total Trans/hr The rate of all interactie transactions processed per hour and the rate of all non-interactie transactions processed per hour. 23 Workload I/Os per Sec The rate of I/Os per second processed for each workload. 310 BEST/1 Capacity Planning Tool V5R1

331 24 Disk I/Os per Sec The rate of I/Os per second processed by each disk arm. 25 Disk IOP I/Os per Sec The rate of I/Os per second processed by each disk IOP. 26 Actie Jobs The total number of actie jobs for each workload. This is the sum of local, LAN, and WAN actie jobs, which are found on the Specify Objecties and Actie Jobs display. 30 Rsp Time by Workload The aerage internal response time of interactie transactions for each workload. This does not include any communications time, and is gien in seconds. 31 Disk Rsp Time per I/O The aerage response time per I/O for each disk arm. This includes both serice time and time spent waiting for the disk to be aailable, and is gien in milliseconds. 32 Aerage Interactie Response Time The aerage external response times for local, LAN, and WAN interactie transactions. This alue is gien in seconds. 40 LAN IOP util The percent of time each LAN IOP was busy transferring characters. 41 LAN line util The percent of time each LAN line was busy transferring characters. 42 WAN IOP util The percent of time each WAN IOP was busy transferring characters. 43 WAN line util The percent of time each WAN line was busy transferring characters. Appendix G. Graphic Support Variables 311

332 312 BEST/1 Capacity Planning Tool V5R1

333 Appendix H. BEST/1 Hardware Name Mapping This appendix lists the special representations of DASD technologies from the BEST/1 hardware table. The names are handled appropriately within the BEST/1 modeling algorithms. Table 19. BEST/1 Hardware Name Mapping OS/400 Model Name BEST/1 Model Name Capacity Supports Write Cache MB N N MB Y N MB Y Y MB N N MB Y N MB Y Y MB N N MB Y N MB Y Y MB N N MB Y N MB Y Y MB N N MB Y N MB Y Y MB N N MB Y N MB Y Y MB N N MB Y N MB Y Y MB N N MB Y N MB Y Y MB Y Y MB Y Y MB Y Y MB Y Y MB Y Y MB Y Y MB Y Y MB Y Y MB Y Y Supports RAID-5 1 Copyright IBM Corp. 1998,

334 Table 19. BEST/1 Hardware Name Mapping (continued) OS/400 Model Name BEST/1 Model Name Capacity Supports Write Cache MB Y Y MB Y Y Note: 1 RAID-5 refers to High aailability (HA-RAID 5 protection). 2 Order features for the 6602 are 6653, 4652, 1211, 1213, 4211, and Supports RAID Order features for the 6603 are 6650, 4650, 1212, 1214, 4212, and Order features for the 6605 are 6605, and Order features for the 6606 are 6606, 4606, 1206, 4206, 8606, and Order features for the 6607 are 6607, 4607, 1207, 4207, 8607, and High Aailability DASD: Table 20. BEST/1 Model Name OS/400 Model Name Write-Cache RAID-5 Option Installed Note: 1 RAID-5 refers to High aailability (HA-RAID 5 protection). DASD IOP Mapping: B502 and 6502 are the same except the B502 s are restricted to eight arms. B522 and 6502 are the same except the B522 s are restricted to eight arms. B523 and 6523 are the same except the B523 s are restricted to eight arms. B530 and 6530 are the same except the B530 s are restricted to eight arms. Communications IOP Mapping: The 613L is the same as the 6130 except the 613L IOP connects to *LAN lines and the 6130 IOP connects to *WAN lines. Model Mapping: 314 BEST/1 Capacity Planning Tool V5R1 BEST/1 models based on the unique CPU feature code. For older CPU names, the CPU model name is used as the unique CPU feature code (for example, F95). For

335 newer CPU names, some BEST/1 panels and reports will show both the CPU name and the CPU feature code (for example: ). The following shows the CISC CPU and models: Table 21. CISC CPU and Models CISC CPU Model CISC CPU Model 20S P P S S 2412 The following shows the RISC CPU and models: Table 22. RISC CPU and Models RISC CPU Model RISC CPU Model 40S S S S S S S S S S S S S S S S 2154 S S 2155 S S 2156 S S 2157 S Appendix H. BEST/1 Hardware Name Mapping 315

336 Table 22. RISC CPU and Models (continued) RISC CPU Model RISC CPU Model SB SB BEST/1 Capacity Planning Tool V5R1

337 Appendix I. Building Performance Profiles Creating performance profiles for solutions is a key step in improing customer satisfaction. Properly sized systems fulfill properly set performance expectations. Solution Proiders are responsible for proiding accurate performance profiles of their package. This information can be proided many different ways and follow many different procedures. Listed below is an example of an approach which will satisfy the minimum requirements for performance profiles. Fie Steps to Enabling Proper System Sizing This exercise can be thought of as a continuously improing cycle with fie steps: 1. Data collection 2. Model creation 3. Model erification 4. Model usage 5. Model improements. The data collection can be done on any system. Once the data is collected, it can be moed to a system which has the Performance Tools licensed program from IBM. Data Collection 1. Collect performance data on the target machine during a time when the system is running at a load which represents normal customer usage by using one of the following methods: Management Central APIs. CALL PGM(QYPSSTRC) PARM('*PFR ' '*STANDARDP' X' ') Start Performance Monitor (STRPFRMON) command. STRPFRMON MBR(Custname) TEXT(Description) INTERVAL(5) HOUR(1) Management Central from the Operations Naigator interface. Option 2 (Collect performance data) from the GO PERFORM menu (IBM Performance Tools for AS/400). 2. In the case where you use the STRPFRMON command, you summarize the data on 5 minute interals for a period of one hour. The data will reside in library QPFRDATA. The actiities present on the machine during the 1 hour collection period will be used to build the performance model. It is important that the actiities on the machine represent the real load that is typical for this solution. Create Baseline Model 1. Use CRTBESTMDL command to create a BEST/1 model: CRTBESTMDL MODEL(Custname) PFRDTAMBR(Custname) MODELLIB(QPFRDATA) 2. This will submit a batch job to create a BEST/1 model from the collected performance data. Copyright IBM Corp. 1998,

338 Verify Baseline Model Use BEST/1 to erify that the model created will produce results consistent with the performance expectations you hae experienced. This is a three step process that first compares modeled results against the measured data, then a what-if analysis is done where workload growth is projected against the same hardware used in the measurement, and finally a what-if analysis is done where the workload growth is projected against the same hardware, or any additional hardware required to satisfy the demands from the extra work. This section explains how to judge this model s ability to predict performance accurately. 1. STRBEST MODELLIB(QPFRDATA) 2. Menu option 1-Workwith models 3. Option 5-Workwith model Custname 4. Option 5 - Analyze current model 5. Option 5 - Display Analysis Summary Report 6. F11 - Compare Against Measured Values Typical guidelines call for predicted and measure alues to be within 10% of each other for resource utilizations. For response times 20% of the measured alue or.5 seconds is a good alue to look for. If the predicted response time is much lower than the measured, then use the F17 key to calibrate the response times properly. 7. F12 - Analysis Summary report 8. F12 - Work with Reports menu 9. F15 - Sae current results to membername Custname in lib QPFRDATA with a description indicating these are from the base model. 10. ENTER - To confirm the sae of the results 11. Option 6 - Print all reports 12. F12 - Return to work with model 13. F15 - Sae current model to membername Custname in lib QPFRDATA with a description indicating this is the base performance profile. 14. ENTER - To confirm the sae of the results Workload and Hardware Changes Use BEST/1 to analyze the base model against other hardware configurations and other workload settings. Try to use the base model as any salesperson would. Start with the base model, identify the amount of work to be done, and try to find the best hardware configuration to meet the customer s current and future needs. This section explains how to produce results for a workload growth scenario where the hardware is not upgraded. These results should help you determine the accuracy of this model when used to project other leels of workloads. Comparing these projected results against other measured data is the best way to judge this accuracy. 1. This assumes you are already in BEST/1 and working with the model 2. Option 7 - Specify workload growth and analyze model for 10 periods. Be sure to set the determine new configuration field to N, then press enter. 3. F15 - Sae current results to membername CustnameGN in lib QPFRDATA with a description indicating these are for growth with update=n. 4. ENTER - To confirm the sae of the results 318 BEST/1 Capacity Planning Tool V5R1

339 5. Option 6 - Print all reports 6. F12 - Return to work with model This section explains how to produce results for a workload growth scenario where the hardware may be upgraded. These results should help you determine the accuracy of this model when used to project other leels of workloads. Comparing these projected results against other measured data or your expectations of what systems are required for arious workload leels is a good way to judge the accuracy of this model. 1. This assumes you are already in BEST/1 and working with the model 2. Option 7 - Specify workload growth and analyze model for 10 periods. Be sure to set the Determine new configuration field to Y, then press enter. 3. F15 - Sae current results to membername CustnameGY in lib QPFRDATA with a description indicating these are for growth with update=y. 4. ENTER - To confirm the sae of the results 5. Option 6 - Print all reports 6. F12 - Return to work with model 7. F3 - Sae and exit the model Use the Model for Future System Sizings It is possible to change any of the characteristics of the baseline model while you are working with it. The three key elements are the Workload (option 1), the Objecties (option 2), and the Configuration (option 10). The Workload and Configuration can een be saed separately to be called into other models later. Sending the Performance Profiles to IBM Once you hae a model, or a set of models which you feel accurately portray the performance characteristics of your solutions. Sae the library to tape and send in to IBM for inclusion in our collection of solution performance models. Please sae all the information in one library with the SAVLIB command. Send printed reports and proide any additional description you can gie about the solution. Number of users, unique hardware requirements, suggestions for sizing Client systems used to attach to the AS/400, etc. All of this information can be useful to a person trying to use the sizing information you are proiding. You can send the library and hardcopy information to: Partners in Deelopment - SI&S IBMCorporation Dept. 292, building 658-D Hwy 52 & NW 37 St Rochester MN Appendix I. Building Performance Profiles 319

340 320 BEST/1 Capacity Planning Tool V5R1

341 Appendix J. Upgrading CISC-to-RISC Example The examples proided below are intended to demonstrate how to model transitions between CISC and RISC processors utilizing BEST/1 s conersion factors. Table 23. CISC-to-RISC Conersion Factors Workload Type CPU Time Working Set Size I/O Counts *NORMAL *TRNNORM *TRNNORM *TRNNORM *BATCHJOB *TRNBAT *TRNBAT *TRNBAT IBM supplied alues may be different than what is listed in Table 23 depending on the ersion or PTF leel of BEST/1 being used as OS/400 continues to be enhanced. One can manually upgrade CISC systems to a RISC processor model or let BEST/1 automatically recommend the upgrades. The following sections demonstrate both methods. In all cases, the following RISCXX01 BEST/1 model is utilized. The RISCXX01 model was created using the default job classification and contains a D60 CISC-based CPU model. Note: The model listing is from a preious release. The differences in listings between the preious release and the current release are not releant to this example. Copyright IBM Corp. 1998,

342 PFRRES95/QACYMDLS(RISCXX01) Page 1 xxxxpt1 VxRxM RCHXXXXX 09/28/96 08:53:56 Base Model to model RISC TEAMXX Disclaimer: The performance estimates presented are approximations which are belieed to be sound. The degree of success which you may achiee in the use of IBMequipment and programs is dependent upon a number of factors, many of which are not under IBM's and BMC Software's control. Thus IBMand BMC Software neither warrant nor guarantee that you can or will achiee similar results. It is your responsibility to alidate the estimates furnished and to determine their releance to your operation. Any configuration recommended by the capacity planner should be erified since the capacity planner does not consider all attachable deices. BEST/1 is a registered trademark of BMC Software, Inc., Houston, TX, USA. (c) Copyright , as an unpublished work. All rights resered. Contains confidential information and trade secrets proprietary to BMC Software, Inc. and one or more third parties. Disassembly or decompilation of the software is prohibited. PFRRES95/QACYMDLS(RISCXX01) Page 2 xxxpt1 VxRxM RCHXXXXX 09/28/96 08:53:56 Base Model to model RISC TEAMXX Model Performance data : PFRRES95 (SA071595) Model/Text : RISCXX01 Base Model to model RISC TEAMXX PFRRES95/QACYMDLS(RISCXX01) Page 3 xxxxpt1 VxRxM RCHXXXXX 09/28/96 08:53:56 Base Model to model RISC TEAMXX Objecties and Actie Jobs Workload Actie Interactie Non-inter Workload Connect Type Jobs Rsp Time Thruput Thruput CLIENTAC4 *LAN *NORMAL NONINTER *LOCAL *NORMAL QDEFAULT *LOCAL *NORMAL Workload Workload/Text : CLIENTAC4 Measured from PFRRES95 (SA071595) Workload type : *NORM AL CPU architecture : *CISC Usage mode : 2 Usage mode: ----Relatie Counts----- ASP Reads Writes =Casual, 2=Interrupted, 3=Steady, 4=N/A PFRRES95/QACYMDLS(RISCXX01) Page 4 xxxxpt1 VxRxM RCHXXXXX 09/28/96 08:53:56 Base Model to model RISC TEAMXX Chars to Comm Line Resources Workload : CLIENTAC4 Nbr of Line Speed Line Resource Connect Lines (Kbit/sec) Relatie Count ITSCTRN *LAN Figure 190. RIXCXX01 Model (Part 1 of 4) 322 BEST/1 Capacity Planning Tool V5R1

343 PFRRES95/QACYMDLS(RISCXX01) Page 5 xxxxpt1 VxRxM RCHXXXXX 09/28/96 08:53:56 Base Model to model RISC TEAMXX Function Function/Text : CLIENTAC4 Function of CLIENTAC4 Functions per user : 1.00 Ag Key/Think (secs) : 18.2 Additional delays (secs) :.0 Inter tns per function : Non-inter tns per function : Transaction Pool Transactions CPU Time Permanent -Chars Transferred- Exceptional Type ID Priority per Function (Secs) Write Pct In Out Wait (Msec) Synchronous Asynchronous Transaction Pool Total DB DB NDB NDB DB DB NDB NDB Type ID I/Os Read Write Read Write Read Write Read Write Transaction Pool Paging Working Set -----Paging Exponent Paging Coefficient---- Type ID Behaior Size (MB) Database Non-Database Database Non-Database 2 2 *GENERIC *GENERIC *GENERIC Workload Workload/Text : NONINTER Measured from PFRRES95 (SA071595) Workload type : *NORM AL CPU architecture : *CISC Usage mode : 4 Usage mode: ----Relatie Counts----- ASP Reads Writes =Casual, 2=Interrupted, 3=Steady, 4=N/A PFRRES95/QACYMDLS(RISCXX01) Page 6 xxxxpt1 VxRxM RCHXXXXX 09/28/96 08:53:56 Base Model to model RISC TEAMXX Function Function/Text : NONINTER Function of NONINTER Functions per user : 1.00 Ag Key/Think (secs) : N/A Additional delays (secs) :.0 Inter tns per function :.00 Non-inter tns per function : Transaction Pool Transactions CPU Time Permanent -Chars Transferred- Exceptional Type ID Priority per Function (Secs) Write Pct In Out Wait (Msec) Synchronous Asynchronous Transaction Pool Total DB DB NDB NDB DB DB NDB NDB Type ID I/Os Read Write Read Write Read Write Read Write Transaction Pool Paging Working Set -----Paging Exponent Paging Coefficient---- Type ID Behaior Size (MB) Database Non-Database Database Non-Database 2 2 *GENERIC *GENERIC *GENERIC Workload Workload/Text : QDEFAULT Measured from PFRRES95 (SA071595) Workload type : *NORM AL CPU architecture : *CISC Usage mode : 4 Usage mode: 1=Casual, 2=Interrupted, 3=Steady, 4=N/A ----Relatie Counts----- ASP Reads Writes Figure 190. RIXCXX01 Model (Part 2 of 4) Appendix J. Upgrading CISC-to-RISC Example 323

344 M PFRRES95/QACYMDLS(RISCXX01) Page 7 xxxxpt1 VxRxM RCHXXXXX 09/28/96 08:53:56 Base Model to model RISC TEAMXX Function Function/Text : QDEFAULT Function of QDEFAULT Functions per user : 1.00 Ag Key/Think (secs) : N/A Additional delays (secs) :.0 Inter tns per function :.00 Non-inter tns per function : Transaction Pool Transactions CPU Time Permanent -Chars Transferred- Exceptional Type ID Priority per Function (Secs) Write Pct In Out Wait (Msec) Synchronous Asynchronous Transaction Pool Total DB DB NDB NDB DB DB NDB NDB Type ID I/Os Read Write Read Write Read Write Read Write Transaction Pool Paging Working Set -----Paging Exponent Paging Coefficient---- Type ID Behaior Size (MB) Database Non-Database Database Non-Database 2 1 *GENERIC *GENERIC PFRRES95/QACYMDLS(RISCXX01) Page 8 xxxxpt1 VxRxM RCHXXXXX 09/28/96 08:53:56 Base Model to model RISC TEAMXX Configuration CPU odel : D60 Comm IOPs : 3 Disk IOPs : 3 Comm lines : 3 Disk ctls : 13 Local WS ctls : 7 Disk arms : 27 LAN ctls : 2 ASPs : 1 WAN WS ctls : 1 Main storage (MB) : 80 Sc Time (M sec/kbit): Main storage pools : 4 Local WS ctls : 1.50 Release leel : V3R7M 0 LAN ctls : 2.00 WAN WS ctls : 2.00 Serice Time Blocks Cache Resource Feature Text ASP (Msecs per IO) Transferred Efficiency CMB Disk IOP 2.9 DC Disk ctl DD Disk arm DC Disk ctl DD Disk arm DC Disk ctl DD Disk arm DC Disk ctl DD Disk arm SI Disk IOP 3.2 DC Disk ctl DD Disk arm DD Disk arm DC Disk ctl DD Disk arm DD Disk arm DC Disk ctl DD Disk arm DD Disk arm DC Disk ctl DD Disk arm DD Disk arm DC Disk ctl DD Disk arm DD Disk arm DC Disk ctl DD Disk arm DD Disk arm DC Disk ctl DD Disk arm DD Disk arm DC Disk ctl DD Disk arm DD Disk arm Figure 190. RIXCXX01 Model (Part 3 of 4) 324 BEST/1 Capacity Planning Tool V5R1

345 SI Disk IOP 3.4 DC Disk ctl DD Disk arm DD Disk arm DD Disk arm DD Disk arm DD Disk arm PFRRES95/QACYMDLS(RISCXX01) Page 9 xxxxpt1 VxRxM RCHXXXXX 09/28/96 08:53:56 Base Model to model RISC TEAMXX Serice Time Blocks Cache Resource Feature Text ASP (Msecs per IO) Transferred Efficiency DD Disk arm DD Disk arm Number of Data ASP Disk Arms Drie Feature Protection 1 27 ** *NONE Drie Feature: ** = mixed Nbr of Line Speed Pct Line Frame Size Sc Time Resource Feature Lines Text (Kbit/sec) Oerhead Duplex (Bytes) (Msec/Frame) CC LAN IOP *HALF ITSCTRN 1 Comm line(s) *HALF 219 CC LAN IOP *HALF TRNFSIOP1 1 Comm line(s) *HALF 1994 CMB WAN IOP *HALF QTIPALINE 1 Comm line(s) *HALF 256 Actiity Size Pool ID Leel (KB) Figure 190. RIXCXX01 Model (Part 4 of 4) Manual Upgrade to a RISC System 1. From the Work with BEST/1 Model display select option 10 (Configuration menu). 2. Select option 1 (Change CPU and other resource alues). 3. Change the CPU Model to a Change the Main Storage size to 64MB since 80MB is not alid for the 2141 CPU. 5. Press Enter and then press F17=Re-scale pool sizes. Note: BEST/1 requires a system to be configured with a minimum machine pool size of 16MB for RISC CPU models. 6. Return to the Configuration display and then press F13=Check configuration to ensure the existing configuration is alid. In this example, the following disk resources are not alid: Disk IOP feature 2615 is not allowed on this CPU Number of 2615 disk IOPs exceeds CPU limit of 0 Number of 2800 arms exceeds CPU limit of 0 Number of arms exceeds CPU limit of 0 7. Press F17=Correct configuration to hae BEST/1 automatically correct the configuration to a alid one. In this example, BEST/1 takes the following actions: IOP(s) deleted IOP(s) created arm(s) created disk ctl(s) deleted disk ctl(s) created disk ctl(s) deleted disk ctl(s) created 8 arm(s) remoed from ASP 1 Appendix J. Upgrading CISC-to-RISC Example 325

346 8. Select any of the options from the Configuration display to manually change the system configuration beyond what BEST/1 recommends after using F17=Correct configuration. Configuration CPU M odel...: 2141 Comm IOPs...: 2 Main stor (MB)...: 64 LAN lines...: 1 Main stor pools...: 4 WAN lines...: 2 Disk IOPs...: 2 Multifunction IOPs...: 1 Disk ctls...: 9 Disk IOAs...: 0 Disk arms...: 19 Comm IOAs...: 0 ASPs...: 1 IPCS IOAs...: 07 Select one of the following: 1. Change CPU and other resource alues 2. Work with disk resources 3. Edit ASPs 4. Edit main storage pools 5. Work with communications resources Selection or command ===> F3=Exit F4=Prompt F9=Retriee F12=Cancel F13=Check configuration F17=Correct configuration F24=More keys 9. Return to the Work with BEST/1 Model display. 10. Select option 6 (Analyze current model and gie recommendations). 11. Select option 5=Display or option 6=Print on the Work with Results display for both the Analysis Summary report and the Recommendations Report. 326 BEST/1 Capacity Planning Tool V5R1

347 M PFRRES95/QACYMDLS(RISCXX01) Page 1 xxxxpt1 VxRxM RCHXXXXX 09/29/96 10:16:00 Base Model to model RISC TEAMXX Disclaimer: The performance estimates presented are approximations which are belieed to be sound. The degree of success which you may achiee in the use of IBMequipment and programs is dependent upon a number of factors, many of which are not under IBM's and BMC Software's control. Thus IBMand BMC Software neither warrant nor guarantee that you can or will achiee similar results. It is your responsibility to alidate the estimates furnished and to determine their releance to your operation. Any configuration recommended by the capacity planner should be erified since the capacity planner does not consider all attachable deices. BEST/1 is a registered trademark of BMC Software, Inc., Houston, TX, USA. (c) Copyright , as an unpublished work. All rights resered. Contains confidential information and trade secrets proprietary to BMC Software, Inc. and one or more third parties. Disassembly or decompilation of the software is prohibited. PFRRES95/QACYMDLS(RISCXX01) Page 2 xxxxpt1 VxRxM RCHXXXXX 09/29/96 10:16:00 Base Model to model RISC TEAMXX Analysis Summary Report CPU model / release leel : 2141 V3R7M0 Main storage : 64 B Quantity Predicted Util CPU : Disk IOPs : Disk controllers : Disk arms : Local WS controllers..... : 7.0 LAN IOPs : LAN lines : LAN controllers : WAN IOPs : WAN lines : 1.0 WAN WS controllers : 1.0 Interactie Non-interactie CPU utilization % : Transactions per Hour : Local response time (seconds) :.0.1 LAN response time (seconds) : WAN response time (seconds) :.0.0 Figure 191. Analysis Summary Report PFRRES95/QACYMDLS(RISCXX01) Page 1 xxxxpt1 VxRxM RCHXXXXX 09/29/96 10:16:02 Base Model to model RISC TEAMXX Disclaimer: The performance estimates presented are approximations which are belieed to be sound. The degree of success which you may achiee in the use of IBMequipment and programs is dependent upon a number of factors, many of which are not under IBM's and BMC Software's' control. Thus IBMand BMC Software neither warrant nor guarantee that you can or will achiee similar results. It is your responsibility to alidate the estimates furnished and to determine their releance to your operation. Any configuration recommended by the capacity planner should be erified since the capacity planner does not consider all attachable deices. BEST/1 is a registered trademark of BMC Software, Inc., Houston, TX, USA. (c) Copyright , as an unpublished work. All rights resered. Contains confidential information and trade secrets proprietary to BMC Software, Inc. and one or more third parties. Disassembly or decompilation of the software is prohibited ṖFRRES95/QACYMDLS(RISCXX01) Page 2 xxxxpt1 VxRxM RCHXXXXX 09/29/96 10:16:02 Base Model to model RISC TEAMXX Recommendations ***** Analysis Exceptions ***** All the specified objecties hae been met Figure 192. Recommendations Report Note: BEST/1 is not recommending any action be taken; the model is a suitable replacement for the D60. Appendix J. Upgrading CISC-to-RISC Example 327

348 Automatic Upgrade to a RISC System BEST/1 is currently configured to allow automatic upgrades to RISC systems. The mechanisms that control the upgrade path are the Upgrade to family parameter for each CISC CPU model and the Currently aailable parameter for the RISC CPU models. When RISC CPU models are currently aailable and the Upgrade to family parameter is *POWERAS for the appropriate CISC CPU models, BEST/1 upgrades to a RISC CPU model. Determining Which Conersion Factors to Use In the preious conersion examples, the default *NORMAL Workload Type was used by BEST/1. Table 23 on page 321 directs BEST/1 to do its upgrade calculations using the same CPU time, the same I/O counts, but twice the mainstore memory. Depending on the characteristics of the workloads in a particular enironment, howeer, one might want to consider directing BEST/1 to use another set of conersion factors for a gien specific workload. Again, in V3R1 these conersion factors are IBM supplied and could not be changed, but starting with V3R6 the user may change these alues to better reflect their unique enironment. The default workload types *NORMAL and *BATCHJOB are expected to be used most of the time. If one suspects they hae the need to use other conersion factors use Table 4 on page 176 as a starting point to make this determination. One can, furthermore, quantitatiely analyze their BEST/1 workload detail to determine if any of the workload conersion factors should be changed based on workload type. To aid in the classification of a workload, Table 5 on page 176 illustrates some CPU per I/O alues at arious DASD response times for each workload type. Once again, as with the preious examples in this appendix, using the RISCXX01 model: 1. From the Work with BEST/1 Model display select option 1 (Work with workloads). 2. Select option 5=Display for the Client Access/400 workload: Opt Workload Text 5 CLIENTAC4 Measured from PFRRES95 (SA071595) NONINTER Measured from PFRRES95 (SA071595) QDEFAULT Measured from PFRRES95 (SA071595) 3. Select option 5=Display for the Client Access/400 function: Opt Function Function Text 5 CLIENTAC4 Function of CLIENTAC4 Display Function Workload...: CLIENTAC4 Measured from PFRRES95 (SA071595) Function...: CLIENTAC4 Function of CLIENTAC4 Type options, press Enter. 5=Display Transaction Pool Transactions CPU Time Total Opt Type ID Priority per Function (Secs) I/Os Transaction Type: 1=Interactie, 2=Non-interactie F3=Exit F12=Cancel Bottom 328 BEST/1 Capacity Planning Tool V5R1

349 In this case, there are three transactions which comprise the CLIENTAC4 function so it is necessary to calculate the weighted aerage CPU per I/O. 4. Calculate the CPU per I/O. a. Calculate the CPU per I/O for each transaction type in the workload function: CPU per I/O = CPU secs per transaction / Total I/Os per transaction For this specific example this is: CPU per I/O = / 1.2 = CPU per I/O = / 4.5 = CPU per I/O = / = Calculate the weighted aerage CPU per I/O. WA CPU per I/O = SUM(CPU per I/O * # of transactions) / Total # of transactions For this specific example this is: WA CPU per I/O = ((0.089 * ) + (0.078 * ) + (0.016 * 1.00)) / = Note the milliseconds per I/O: a. Return to the Work with BEST/1 Model display. b. Select option 5 (Analyze current model). c. Select option 5=Display for the ASP and Disk Arm Report. d. Note the Msecs per I/O alue, in this specific example it is 24.5 Msecs. 7. Reference Table 5 on page 176 to determine the appropriate workload type. Gien a 24.5 Msec aerage response time per I/O alue and a CPU per I/O alue, the CLIENTAC4 workload is characterized by a *TRNNORM1 workload type, meaning the workload is CPU intensie. 8. Repeat Step 2 on page 328 through Step 7 for workloads NONINTER and QDEFAULT. The results will be: Workload Aerage I/O CPU per I/O Workload Type Setting Response Time CLIENTAC Msecs *TRNNORM1 NONINTER 24.5 Msecs *BATCHJOB QDEFAULT 24.5 Msecs *TRNNORM1 9. After returning to the Work with Workloads display, Select option=2 for the CLIENTAC4 and QDEFAULT workloads: Appendix J. Upgrading CISC-to-RISC Example 329

350 Work with Workloads Model/Text: RISCXX01 Base Model to model RISC TEAMXX Type options, press Enter. 1=Create 2=Change 3=Copy 4=Delete 5=Display 6=Print 7=Rename 8=Sae workload to workload member 9=Edit transactions Opt Workload Text 2 CLIENTAC4 Measured from PFRRES95 (SA071595) NONINTER Measured from PFRRES95 (SA071595) 2 QDEFAULT Measured from PFRRES95 (SA071595) Bottom F3=Exit F6=Add saed workload F9=Add predefined workload F12=Cancel F13=Combine workloads 10. For the CLIENTAC4 workload change the Workload type parameter to *TRNNORM1 from *NORMAL. Change Workload Workload...: CLIENTAC4 Type changes, press Enter. Workload text... Measured from PFRRES95 (SA071595) Workload type... *TRNNORM1 *NORMAL, *BATCHJOB, *TRNxxxxx Usage mode =Casual, 2=Interrupted, 3=Steady, 4=N/A Functions Ag K/T Tns per Function Function Text per User (secs) Inter Non-inter Function of CLIENTAC Bottom F3=Exit F6=Work with functions F9=Specify chars to comm line resources F10=Specify I/Os to ASPs F11=Show functions with olume F12=Cancel 11. Similarly change the QDEFAULT Workload type parameter to *TRNNORM1 from *NORMAL. 12. Return to the Work with BEST/1 Model display. 13. Select option 7 (Specify workload growth and analyze model). 14. Specify the workload growth as shown in the following screen: Specify Growth of Workload Actiity Type information, press Enter to analyze model. Determine new configuration... Y Y=Yes, N=No Periods to analyze Period 1... Period1 Name Period 2... Period2 Name Period 3... Period3 Name Period 4... Period4 Name Period 5... Period5 Name Percent Change in Workload Actiity Workload Period 1 Period 2 Period 3 Period 4 Period 5 *ALL Bottom F3=Exit F11=Specify total growth F12=Cancel F13=Display periods 6 to 10 F17=Analyze using ANZBESTMDL 330 BEST/1 Capacity Planning Tool V5R1

351 15. Select option 5=Display or option 6=Print on the Work with Results display for both the Analysis Summary report and the Recommendations Report. PFRRES95/QACYMDLS(RISCXX01) Page 1 xxxxpt1 VxRxM RCHXXXXX 09/29/96 15:57:37 Base Model to model RISC TEAMXX Disclaimer: The performance estimates presented are approximations which are belieed to be sound. The degree of success which you may achiee in the use of IBMequipment and programs is dependent upon a number of factors, many of which are not under IBM's and BMC Software's control. Thus IBMand BMC Software neither warrant nor guarantee that you can or will achiee similar results. It is your responsibility to alidate the estimates furnished and to determine their releance to your operation. Any configuration recommended by the capacity planner should be erified since the capacity planner does not consider all attachable deices. BEST/1 is a registered trademark of BMC Software, Inc., Houston, TX, USA. (c) Copyright , as an unpublished work. All rights resered. Contains confidential information and trade secrets proprietary to BMC Software, Inc. and one or more third parties. Disassembly or decompilation of the software is prohibited. PFRRES95/QACYMDLS(RISCXX01) Page 2 xxxxpt1 VxRxM RCHXXXXX 09/29/96 15:57:37 Base Model to model RISC TEAMXX Analysis Summary Report CPU Storage CPU --Disk IOPs--- --Disk Ctls--- --Disk Arms Local WS Ctls--- Period Model (MB) Util Nbr Util Nbr Util Nbr Util Nbr Util Period 1 D Period 2 D Period 3 D Period Period Inter Rsp Time Non-Inter Rsp Time Inter Non-Inter Period Local LAN WAN Local LAN WAN CPU Util Trans/Hr CPU Util Trans/Hr Period Period Period Period Period LAN IOPS--- --LAN Lines LAN Ctls WAN IOPS--- --WAN Lines WAN Ctls--- Release Period Nbr Util Nbr Util Nbr Util Nbr Util Nbr Util Nbr Util Leel Period V3R1M0 Period V3R1M0 Period V3R1M0 Period V3R7M0 Period V3R7M0 Figure 193. Analysis Summary Report Appendix J. Upgrading CISC-to-RISC Example 331

352 PFRRES95/QACYMDLS(RISCXX01) Page 1 xxxxpt1 VxRxM RCHXXXXX 09/29/96 15:57:39 Base Model to model RISC TEAMXX Disclaimer: The performance estimates presented are approximations which are belieed to be sound. The degree of success which you may achiee in the use of IBMequipment and programs is dependent upon a number of factors, many of which are not under IBM's and BMC Software's control. Thus IBMand BMC Software neither warrant nor guarantee that you can or will achiee similar results. It is your responsibility to alidate the estimates furnished and to determine their releance to your operation. Any configuration recommended by the capacity planner should be erified since the capacity planner does not consider all attachable deices. BEST/1 is a registered trademark of BMC Software, Inc., Houston, TX, USA. (c) Copyright , as an unpublished work. All rights resered. Contains confidential information and trade secrets proprietary to BMC Software, Inc. and one or more third parties. Disassembly or decompilation of the software is prohibited. PFRRES95/QACYMDLS(RISCXX01) Page 2 xxxxpt1 VxRxM RCHXXXXX 09/29/96 15:57:39 Base Model to model RISC TEAMXX Recommendations ***** Period 1 Growth: 0.00 percent ***** ***** Period 1 Initial Exceptions ***** All the specified objecties hae been met Recommendations ***** Period 2 Growth: percent ***** ***** Period 2 Initial Exceptions ***** All the specified objecties hae been met Recommendations ***** Period 3 Growth: percent ***** ***** Period 3 Initial Exceptions ***** All the specified objecties hae been met Recommendations ***** Period 4 Growth: percent ***** ***** Period 4 Initial Exceptions ***** CPU utilization of for priority 20 and higher exceeds objectie of 70 ***** Period 4 Configuration Changes ***** CPU model changed to 2142 Check that each workload has appropriate workload type Run Upgrade Assistant for accurate DASD expansion requirements Storage size changed to 128 MB Pool 1 size changed to KB Pool 2 size changed to KB Pool 3 size changed to 6400 KB Pool 4 size changed to KB IOP(s) deleted IOP(s) created arm(s) created disk ctl(s) deleted disk ctl(s) created disk ctl(s) deleted disk ctl(s) created 8 arm(s) remoed from ASP 1 Recommendations ***** Period 5 Growth: percent ***** ***** Period 5 Initial Exceptions ***** PFRRES95/QACYMDLS(RISCXX01) Page 3 xxxxpt1 VxRxM RCHXXXXX 09/29/96 15:57:39 Base Model to model RISC TEAMXX All the specified objecties hae been met Figure 194. Recommendations Report Note: The *TRNNORM1 workload type is characterized by a CPU time conersion factor of 0.5 ersus a CPU time conersion factor of 1.0 for the *NORMAL workload type is reflected in the Analysis Summary Report comparison below. When the D60 is upgraded to a 2142 using the *TRNNORM1 workload type the CPU utilization is less than when using the *NORMAL workload type. 332 BEST/1 Capacity Planning Tool V5R1

353 PFRRES95/QACYMDLS(RISCXX01) Page 2 xxxxpt1 VxRxM RCHXXXXX 09/29/96 10:53:19 Base Model to model RISC TEAMXX Analysis Summary Report CPU Storage CPU --Disk IOPs--- --Disk Ctls--- --Disk Arms Local WS Ctls--- Period Model (MB) Util Nbr Util Nbr Util Nbr Util Nbr Util Period 1 D Period 2 D Period 3 D Period Period Figure 195. Analysis Summary Report *NORMAL PFRRES95/QACYMDLS(RISCXX01) Page 2 xxxxpt1 VxRxM RCHXXXXX 09/29/96 15:57:37 Base Model to model RISC TEAMXX Analysis Summary Report CPU Storage CPU --Disk IOPs--- --Disk Ctls--- --Disk Arms Local WS Ctls--- Period Model (MB) Util Nbr Util Nbr Util Nbr Util Nbr Util Period 1 D Period 2 D Period 3 D Period Period Figure 196. Analysis Summary Report *TRNNORM1 Appendix J. Upgrading CISC-to-RISC Example 333

354 334 BEST/1 Capacity Planning Tool V5R1

355 Appendix K. Tuning Performance Improement Factors Although not all the performance improements affect modeling, this appendix proides an oeriew of improements made from V3R6 to V4R2. The release changes of OS/400 proide broad-based performance improements. One of these changes is the rewriting of key components of the operating system to use Feedback Directed Programming Restructuring (FDPR) technology on the Vertical Licensed Internal Code. The range of performance improement aries from 10-50% for traditional commercial transaction processing applications that do significant database processing in conjunction with journaling and commitment control. The amount of improement aries by processor model and by the characteristics of a gien application. Other areas that gain from the performance improements are APPC and TCP/IP communications, OPM and ILE application compile times, and sae and restore times. It is important to understand the details of an application to understand how much performance gain will be seen by installing the new release of the OS/400. To help you better understand the enironments that will see performance improements, the following sections explain the details of the applications that will benefit the most from V3R7. Traditional Commercial Transaction Processing Applications Most interactie, commercial enironments will see a performance improement when installing the V3R7 release. The amount of performance improement aries by enironment characteristics and by processor models. Those enironments that will see the most improement (20%+) are those that use the following operating system functions and hae the following characteristics. Journaling Commitment control High contention High CPU utilization (90%+) The following table shows the ranges of performance improement across the processor line. The percentage improements are for the specific enironment described in the preious paragraph. Table 24. Percentage Performance Improement by Processor Model way Model way Model way Models 510 Models 500 and % to 50% 40% 20% 15% 10% to 15% Communications Enironments Communications performance is improed for both APPC and TCP/IP. The improement in CPU time reduction for APPC is 10-15% and 15-20% for TCP/IP. These improements are only for the CPU time associated with communications. This improement should only be anticipated for the portion of your system s Copyright IBM Corp. 1998,

356 Compile Enironments Sae/Restore Enironments oerall communications CPU time. The performance improement in communication CPU time is the same across the processor line, unlike commercial workloads. Compile times are also improed. Compiles that are run with optimal memory configured enironments will see an improement in the range of 10-15%. The improement for compiles run in a constrained memory enironment are een greater. These improements apply to both OPM and ILE compiles and are the same across the processor line. The performance of saes and restores is enhanced. The improements range from 5% to 65%, depending on the type of data being saed and restored and the type of tape drie that is inoled. At the low-end, saing and restoring of small objects is improed for 1/4-inch cartridge tape dries. The improements range from 30% for sae times and 35% for restore times for these small objects. The maximum sae and restore rates for these dries remain unchanged from V3R6. At the high-end, the performance of saes and restores with the 3590 tape drie is improed. The following table shows the ranges of performance improement by object type for this tape drie. The three categories of object type are: Typical sae and restore rates (User Mix) Maximum sae and restore rates (Large Files) Small objects, such as source files (Small Files) Table 25. Percentage Performance Improement by Object Type with the 3590 Tape Drie User Mix Large Files Small Files Sae Rates 15% 10% 5% Restore Rates 20% 25% 10% The tape block size for the 3590 tape drie is increased to allow significant performance gains oer sae and restore rates in V3R6. The following table shows the ranges of performance improements for what is considered a typical sae and restore rate (User Mix) and the maximum sae and restore (Large Files). Table 26. Percentage Performance Improement by Object Type with Increased Block Size on the 3590 User Mix Large Files Sae Rates 50% 45% Restore Rates 65% 60% 336 BEST/1 Capacity Planning Tool V5R1

357 Appendix L. Untranslated Messages The following is a partial list of untranslated messages that are usually displayed by message PCY9999: Table 27. Untranslated Messages Message ID First-Leel Text When Message Is Displayed PCY1 IOP FEATURE <feature> DOES NOT SUPPORT DISK OPERATIONS. You see this message after a BEST/1 model is read, and an IOP shows connections to either disk controllers or disk IOAs, and the feature is either a communications IOP or a multifunction IOP that does not allow disk connections. In this situation, all disk controllers, disk IOAs, and disk arms are deleted from the IOP. PCY2 PCY3 PCY4 PCY5 IOP FEATURE <feature> DOES NOT SUPPORT COMMUNICATIONS OPERATIONS. IOP FEATURE <feature> CAN ONLY CONNECT TO DISK IOAS, NOT DISK CONTROLLERS. IOP FEATURE <feature> CAN ONLY CONNECT TO DISK CONTROLLERS, NOT DISK IOAS. IOP FEATURE <feature> CAN ONLY CONNECT TO LINE RESOURCES THROUGH COMMUNICATIONS IOAS. You see this message after a BEST/1 model is read, and an IOP shows connections to communications IOAs or communications lines, and the IOP is a disk IOP. In this situation, all communications IOAs and lines are deleted from the IOP. You see this message after a BEST/1 model is read, and a multifunction IOP shows connections to disk controllers, and the IOP feature only allows connections to disk arms through disk IOAs. In this situation, the first disk controller is changed to a disk IOA. If the multifunction IOP feature allows connections to more than one disk IOA, additional disk controllers are changed to disk IOAs. Once the maximum number of disk IOAs hae been changed from disk controllers, arms under any remaining disk controllers are connected to one of the disk IOAs. This message is displayed when you are reading a pre-v4r2 model containing a V4R1 multifunction IOP. You see this message after a BEST/1 model is read, and an IOP shows connections to disk IOAs, and the IOP feature only allows connections to disk arms through disk controllers. In this situation, the first disk IOA is changed to a disk controller whose feature matches the feature of the first disk arm. Additional controllers are created for each different disk arm feature. You see this message after a BEST/1 model is read, and a multifunction IOP shows direct connections to communications lines, and the IOP feature requires communications connections through a communications IOA. In this situation, communications IOAs are created under the multifunction IOP and the communications lines are connected to the new communications IOAs. Copyright IBM Corp. 1998,

358 Table 27. Untranslated Messages (continued) PCY6 IOP FEATURE <feature> CANNOT CONNECT TO COMMUNICATIONS IOAS. You see this message after a BEST/1 model is read, and an IOP shows connections to communications IOAs, and the IOP feature does not support connections to communications IOAs. In this situation, communications IOAs are deleted under the multifunction IOP and the communications lines are connected directly to the IOP. 338 BEST/1 Capacity Planning Tool V5R1

359 Bibliography The following manuals contain information you may need. The manuals are listed with their full title and base order number. Work Management, SC , proides information about how to create and change a work management enironment. Other topics include a description of tuning the system, collecting performance data including information on record formats and contents of the data being collected, working with system alues to control or change the oerall operation of the system, and a description of how to gather data to determine who is using the system and what resources are being used. For the most current information about work management, go to the Work Management topic in the Information Center. Performance Tools for iseries, SC , proides the programmer with information about what performance management is, gies an oeriew of the tools, and describes how the tools can be used to help manage system performance. The manual gies instructions on how to approach the analysis of system performance and how to do system performance measurement, reporting, and application analysis. AS/400 Performance Capabilities Reference proides information about performance and tuning factors. You can request a copy of this document at You can iew or download this document with Adobe Acrobat. The Adobe Acrobat reader plug-in is aailable at: Copyright IBM Corp. 1998,

360 340 BEST/1 Capacity Planning Tool V5R1

361 Index Special Characters *BATCHJOB calibration 156 *BATCHJOB workloads 33, 76 *BATCHJOB workloads, calibrating 156 *BATCHJOB workloads, definition 154 *NORMAL workloads 33, 76 Numerics x-070 Disk Array Subsystem 4 660x-070 serice x-070 Disk Array Subsystem 4 671x-070 serice x-070 Disk Array Subsystem 4 690x-070 serice Disk Array Subsystem disk array subsystem considerations additional modeling modeling serice 128 A actie job default to 1 81 in the new model 146 non-interactie work 81 objecties 32 erify 79 actie jobs, number of 107 actiity leel 4 adding throughput to an existing system 197 adisor 2 analysis parameters 234 performance tips 181 analysis and calibration, model 71 analysis parameters 234 Analysis Parameters menu 101 analysis summary 14, 92 analysis summary report 229 analyzing the model 108 application types 28 changing 82 architecture 175 arm failure 175 ASP aerage disk I/O operations 6 changing 127 edit 66 modeling 4 report 14 ASP and Disk Arm Report 96, 231 ASP report 96 ASPs and journaling modeling 177 assign jobs to workloads display 193 assigning jobs to workloads serer jobs 44 assumptions, BEST/1 6 automatic growth 114 automatic hardware changes with manual growth 119 automatic hardware upgrade 111 automatic upgrade to RISC system 328 axis range, changing the 238 B B10 CPU seconds 25, 27, 79 B10 database time 28 Background batch serer 257 basic concepts and formulas 283 batch in CPU model recommendation 156 modeling examples 157 transaction throughput example, predicting 157 BATCH workload group 257 batch modeling batch window 8 capabilities 149 caution 43 guidelines 156 run time 8 batch run time for a different CPU, computing 286 for current configuration, computing 286 modeling 160 modeling example 157 modeling using BEST/1 157 batch window modeling 160 batch workload into an independent workload, isolation of 154 BATCH workload group 257 BEST/1 considerations 16 equations 279 for the AS/400 display 188, 197, 218 how to start 1 job types 20 licensed internal code tasks 42 modeling process 8 options 15 options for modeling with 9 performance statistics 5 plotting graphs in 242 principles 279 printing graphs in 241 BEST/1 model creating 182 creating from performance data 182 BEST/1 Visualizer input 100 buffers, read-ahead 173 building performance profile 317 C cache, write 174 calibrating *BATCHJOB workloads 156 other resources 90 resource utilization and disk I/Os 90 response time 87 calibration *BATCHJOB 84, 156 manual 14, 85 model analysis and 71 modeling problems 86 response time 14, 85 results 91 calibration, model 84 capabilities, BEST/1 3 capacity considerations 2 definition 1 migrating from System/ migration assumptions 272, 273 migration example 274, 278 process 2 steps 2 when to use 2 capacity planning examples 181 leaing the tool 227 measured workloads 35 process 2 when to use 2 capacity planning, workload groups for 249 Capacity Planning System/36 Migration Utility MIGUTL (Migration Utility) function 273 category, job name 45 change CPU model display 222 change CPU Model display 221 changes to the system, modeling 101 changing application types 82 changing guidelines 156 changing storage pools 128 characteristics I/O workload 260 characteristics file, adding a newly announced CPU to the hardware 218 characters transferred characters transferred 28 in/out 28 characters transferred across line resources, distribution of 170 checksum disk array subsystem hardware 172 CISC modeling transitions 175 CISC-to-RISC modeling 175 Copyright IBM Corp. 1998,

362 CISC-to-RISC conersion factors alues, editing 105 CL command 8 classification default job 40 defining a job 41 job type 41 using the default job 40 classification, job 19 classify jobs display 191 Client Access, modeling 145 Client Access job type classification 44 Client Access model, analyzing the 148 Client Access results 148 Client/Serer workload group 263 Collection Serices special considerations 155 combining workloads 24 comm resources report 231 command, CL create BEST/1 Model (CRTBESTMDL) 35 CRTBESTMDL (Create BEST/1 Model) 35 commercial orders 258 COMMERCIAL workload group 249 communications assign jobs to workloads by 46 configuration 165 IOA utilization 14 IOP utilization 14 line modeling 161 resources 68 resources, work with 68 resources changing 129 resources report 14, 98 resources report display 207 support 161 workload 171 communications workload 171 complex query 259 concepts selecting data for capacity planning measured workloads 35 workload 19 concepts and formulas, basic 283 conditions batch modeling 7 BEST/1 6 miscellaneous 8 configuration changes 62 changes, warning 62 communications 165 computing batch run time for current 286 IBM-supplied 61 menu, system 62 restriction 8 system 61 Confirm Creation of BEST/1 Model display 196 considerations when you collect data with Collection Serices 155 with performance monitor 155 Copy CPU Model display 220 correspondence center workload type 263 CPU adding a newly announced 218 changing other resource alues 121 computing batch run time for a different 286 other resource alues, change 63 priority 27 Relatie performance 122 selecting 122 CPU model recommendation, inclusion of batch in 156 CPU power table, relatie 287 CPU seconds 79 B10 25 CPU serice time 175 CPU time 27 CPU utilization query to print JOB/TASK types and 267 CPW performance rating 122 Create BEST/1 Model display 189 create BEST/1 model from performance data CRTBESTMDL (Create BEST/1 Model) command 35 using BEST/1 displays 36 Create Graph Format display 216 creating BEST/1 model 182 from performance data 35 using BEST/1 displays 36 using CRTBESTMDL command 35 performance data model adanced method 36 basic 36 the model 50 your own graphs 215 CRTBESTMDL (Create BEST/1 Model) command 35 current configuration, computing batch run time for 286 current model displaying graphs from the 211 leaing the 227 custom graphs, sample 243 D data building a model using measured 35 comparing measured and predicted 85 creating a BEST/1 model from performance 182 creating a model using performance 36 for capacity planning measured workloads, concepts for selecting 35 data protection, modeling 172 data protection methods changes for 172 comparing performance for 172 default growth 114 default job classification 40 default workload 41 classification 39 defining non-interactie transactions 149, 194 defining workloads, strategy for 145 definition function 24 job classification 41 transaction 26 workload 22 delete, parts 254 deelopment 258 deice (WAD), write assist 173 disk arm report 96 I/O operations per ASP, IOP, and IOA 6 disk arm report 14 disk arm report 96 Disk Arm Report 231 disk array subsystem additional modeling considerations for hardware checksum 172 disk configuration, cautions 126 disk I/O operations ASP, aerage 6 IOA, aerage 6 IOP, aerage 6 disk resources, changing 125 disk resources, work with 66 Disk Resources Report 14, 96, 231 disk serice time 126, 128 disk serice time caution 126 display assign jobs to workloads 193 BEST/1 for the AS/ , 197, 218 change CPU model 221, 222 classify jobs 191 Confirm Creation of BEST/1 Model 196 Copy CPU Model 220 Create BEST/1 Model 189 Create Graph Format 216 Create Model from Performance Data display 189 define non-interactie transactions 194 Display Analysis Summary 200, 203, 205, 210 Display ASP and Disk Arm Report 206 Display Disk Resources Report 206 Display Main Storage Pool Report 207 Display Recommendations 204 Display Workload Report 206 Edit Job Classifications 192 Exit BEST/1 227 Exit Capacity Planning 227 hardware characteristics 219 Measured and Predicted Comparison 200 More BEST/1 Options 218 Sae Current Model 227 Sae Graph Format Member BEST/1 Capacity Planning Tool V5R1

363 display (continued) Sae Job Classification Member 195 Select Performance Member display 185, 190 Select Results Member display 213 Select X-Axis Variable display 216 Specify Growth of Workload Actiity 210 Specify Growth of Workload Actiity display 208 Specify Job Classification Category display 192 Specify Objecties and Actie Jobs 199, 202 Specify Storage Sizes for CPU Model 221 Work with BEST/1 Model 198, 208 Work with BEST/1 models 198 Work with BEST/1 Models 188, 196 Work with CPU Models 219, 220, 225 Work with Graph Formats 212, 214, 217 Work with Results 91, 199, 201, 203, 205, 210, 211 Display Analysis Summary display 200, 203, 205, 210 Display Disk Resources Report display 206 Display Main Storage Pool Report display 207 Display Recommendations display 204 Display Workload Report display 206 distribution of characters transferred across line resources 170 E EDF (externally described file) 99 EDF processing program 100 edit ASPs 66, 128 Edit Job Classifications display 192 edit transactions 118 editing storage pools 67 equations, queuing 279 estimating using queuing multiplier, the 279 example batch job, query 284 batch modeling 157 capacity planning 181 graphing results 211 migrating System/36 measured data 274 mixing workloads 52 predicting batch transaction throughput 157 workloads, functions and transactions 30 exceptional wait 28, 87 existing system, adding throughput to an 197 Exit BEST/1 227 Exit BEST/1 display 227 Exit Capacity Planning display 227 external response time 5, 107, 108 externally described file (EDF) 99 externally described files 289 F file adding a newly announced CPU to the hardware characteristics 218 used by BEST/1 16 formulas basic concepts and 283 function changing 116 definition 24 transactions, example showing workloads 30 workload 76 functions and transactions, changing 116 G GDF file 235 graph format 235 graphic selecting data 35 graphic support ariables 309 graphical output 235 graphics leaing the capacity planning tool from 229 planning leaing the capacity planning tool 229 graphing results example 211 graphs creating your own 215 from a preious model, displaying 213 from the current model, displaying 211 in plotting BEST/1 242 in printing BEST/1 241 oerlaying 239 printing model reports and 229 sample custom 243 scenario, oerlaying two 239 group BATCH workload 257 Client/Serer workload 263 COMMERCIAL workload 249 Industry 265 SPOOL workload 257 workload 260 workload for capacity planning 249 growing interactie and non-interactie transactions together 30 growth automatic 14, 114 automatic hardware changes with manual 119 default 114 specifying a user-defined sequence of workload 110 workload 26 guidelines changing job priority 156 guidelines, changing 102 guidelines, editing sync reads 103 guidelines, saing and reusing 102 guidelines and thresholds, editing utilization 102 H hardware changes with manual growth, automatic 119 characteristics 25 disk array subsystem, checksum 172 hardware characteristics 162 Hardware Characteristics display 219 hardware characteristics file adding a newly announced CPU to the 218 hardware mapping 313 hardware utilization 5 how to start BEST/1 1 I I/O 175 I/O operations DB 28 NDB 28 I/O workload characteristics 260 Idle (CPU utilization) 247 in/out characters transferred 28 independent workload, isolation of batch into an 154 indexes, RTW tables and 255 Industry workload group 265 inquiry, order 252 inquiry, parts 255 interactie throughput 108 throughput, aerage 6 interactie actiity performance objecties 107 interactie transaction linked to non-interactie, modeling 150 internal code tasks, licensed 42 internal response time 5 inentory part location and 251 update in-process 251 IOA aerage disk I/O operations 6 creating communications IOA 165 creating disk IOA 125 report, communications 98, 207, 231 report, disk 96, 206 report, disk resources 231 utilization 134 IOP aerage disk I/O operations 6 report, communications 98, 207, 231 report, disk 96, 206 report, disk resources 231 utilization 134 J job actie 32 Index 343

364 job (continued) categories 10, 39 classifications 10 classifying into workloads 39 priority 4 types 10 workload 17 job categories 19 job classification by control unit 46 by line 46 default 40 defining a 41 using the default 40 workloads 19, 39 job name, assign jobs to workloads by 44 job name, assign serer jobs to workloads by 44 job name category 45 JOB/TASK types CPU utilization, query to print 267 job type assign jobs to workloads by 43 BEST/1 20 classification 41 jobs 146 jobs in the new model, reiewing the number of actie 146 jobs per storage pool, aerage number of 6 journaling 177 L Licensed Internal Code tasks (*LIC) 42 Licensed Internal Code tasks, BEST/1 42 line resources, distribution of characters transferred across 170 location and inentory, part 251 logical partitions specifying 64 M main storage changing pools 128 editing pools 67 pool report 14, 97, 231 selecting size 123 major options 9 managerial workload type 263 manual batch window modeling 283 manual growth, automatic hardware upgrade 111 mapping hardware 313 Measured and Predicted Comparison display 200 measured and predicted data, comparing 85 measured data building a model using 35 measured workloads, criteria for selecting data 35 memory apportioning 129 memory (continued) modeling 130 modeling terminology 136 memory modeling 135 menu system configuration 62 message PCY1 271 PCY2 271 PCY3 271 PCY4 271 PCY5 271 PCY6 271 read conersion 271 methods changes for data protection 172 comparing performance for data protection 172 migrating data 271 migrating measured data example 274 migration BEST/1 migration utility 272 procedure 273 Migration Utility (MIGUTL) function 273 migration utility, System/ MIGUTL (Migration Utility) function 273 mirroring 172 mixing predefined workloads and measured workloads 55 mixing workload example 52 mixing workloads from different systems 51, 55 model analyzing the 108 analyzing the Client Access 148 calibration 84 creating from performance data 182 creating the 50 defining work to the 21 displaying graphs from a preious 213 displaying graphs from the current 211 leaing the current 227 recommendation, inclusion of batch in CPU 156 reiewing the number of actie jobs in the new 146 using measured data building 35 building a 35 using performance data creating 36 using predefined workloads 55 model, BEST/1 9 model analysis and calibration 71 model report example 232 model reports printing 229 model results, graphing a single set of 238 modeling ASPs and journaling 177 auxiliary storage pool (ASP) 177 batch run time 160 batch window 160 changes to the system 101 Client Access 27, 145 considerations for 9337 disk array subsystem, additional 173 data protection 172 growth 110 manual batch window 283 memory 135 non-interactie work 149 release leel performance improements 178 remote communications 161 shared folders 148 terminology, memory 136 transitions between CISC and RISC 175 modeling and calibration 86 modeling process BEST/1 8 modeling topics, selected 145 modeling with BEST/1, options for 9 More BEST/1 Options display 218 multipliers, queuing 283 N name assign jobs to workloads by job 44 assign serer jobs to workloads by job 44 category, job 45 non-interactie defining transactions 48 modeling 149 modeling interactie transaction linked to 150 performance objecties actiity 107 throughput, aerage 6 transaction 30 transactions, defining 149 work, modeling 149 note, mixing workloads from different systems 51 Notices ix number of actie jobs in the new model, reiewing the 146 number of jobs per storage pool, aerage 6 O objecties performance interactie 107 specifying performance 101 summary of workloads 34 erify 79 office workload group 260 Office Benchmark workload type 262 OfficeVision current functions BEST/1 Capacity Planning Tool V5R1

365 OfficeVision (continued) office 260 transactions per office function 262 workload types 260 operations per ASP, IOP and IOA, aerage disk I/O 6 options for modeling with BEST/1 9 order inquiry 252 orders commercial 258 output graphical 235 sample printed 229 P page fault modeling 14, 97, 98 paging behaior 136 behaiors, specifying 48 coefficient 136 exponent 136 paging behaior definition 28 specifying 48 alues, editing 104 parameter MSRPRF (Measured Profile) 35 parameters analysis 234 part location and inentory 251 parts delete 254 parts inquiry 255 PCY1 message 271 PCY2 message 271 PCY3 message 271 PCY4 message 271 PCY5 message 271 PCY6 message 271 PCYnnnn message recommendations 130 PCYnnnn messages 130 percentage of physical writes to permanent objects 28 performance 8 CL command 8 for data protection methods, comparing 172 measured workloads 35 selecting data for 35 performance data creating a BEST/1 model from 182 creating a model using 36 performance factor relatie 25 performance improements modeling release leel 178 performance monitor special considerations 155 performance objecties for interactie and non-interactie actiity 107 specifying 101 performance profile building 317 performance statistics, BEST/1 5 performance tips 181 when doing what-if...? analysis 181 period 111 period name 111 planning process, the capacity 2 when to use capacity 2 workload groups for capacity 249 plotting graphs in BEST/1 242 pool apportioning 129 aerage number of jobs per storage 6 changing main storage 128 editing main storage 67 in which the transaction resides 27 sync read rate per storage 6 predefined workload building a model 55 caution 55 groups 55 select 58 using 55 using BATCH 57 predicted data, comparing measured and 85 preious model, displaying graphs from a 213 print JOB/TASK types and CPU utilization, query to 267 print spooling 8 printed output sample 229 printed reports 229 printed results report - model name 111 printing graphs in BEST/1 241 model reports and graphs 229 process BEST/1 modeling 8 processing, receiing and 253 professional workload type 263 protection, modeling data 172 protection methods changes for data 172 comparing performance for data 172 Q QM (queuing multiplier) 279 query complex 259 medium complexity, sort 259 medium complexity, summary 259 print JOB/TASK types and CPU utilization 267 queue time 279 queuing theory 279 queuing equations 279 queuing multipliers 283 R RAID write cache 174 RAMP-C characteristics (by class) 250 workload 249 RAMP-C characteristics (by class) 250 range, changing the axis 238 rate per storage pool, sync read 6 read-ahead buffers 173 read conersion messages 62, 271 read rate per storage pool, sync 6 receiing and processing 253 recommendations Best/1 93 BEST/1 8, 14 for achieing effectie storage 139 report 230 understanding results and 130 Relational Transaction Workload (RTW) description 23 predefined workload 23 relatie CPU power table 287 relatie performance factor 25, 122 release leel 124 modeling performance improements 178 report analysis summary 210, 229 ASP and disk arm 96 ASP and Disk Arm 231 communications resources 98, 207 Communications Resources 231 disk resources 96, 206 Disk Resources 231 display ASP and disk arm 206 Graph Format 235 main storage pool 97, 207 Main Storage Pool 231 printed 229 recommendations 204, 230 workload 206, 230 report, workload 94 report Model 232 reports and graphs, printing model 229 resource alues change CPU and other 63 changing 63 changing CPU and other 121 resources calibrating other 90 changing communications 129 changing disk 125 changing system 119 distribution of characters transferred across line 170 work with communications 68 work with disk 66 resources report communications 98, 231 disk 96, 206, 231 response time 5, 92 calibrating 87 external 5, 108 internal 5 ariation 281 response time, internal and external 5 Index 345

366 response time ariation 281 results graphing 14 graphing a single set of model 238 graphing the results 211 oerlaying graphs of two 239 saing 14, 99 selecting/appending 14 results, graphing 211 results, work with 13 results and recommendations understanding 130 reiewing the workloads 147 RISC modeling transitions 175 RISC system automatic upgrade 328 RTW tables and indexes 255 transaction summary 255 RTW transaction details 250 run time for current configuration, computing batch 286 S sample custom graphs 243 sample printed output 229 Sae Current Model display 227 Sae Graph Format Member display 217 Sae Job Classification Member display 195 saing results 99 workloads 24 scenario, oerlaying two graphs 239 secondary paging 35 secretarial workload type 263 Select Performance Member display 185, 190 select predefined workload 58 Select Results Member display 213 Select X-Axis Variable display 216 selecting release leel 124 selecting data for capacity planning measured workloads, concepts for 35 serer background 257 serer jobs assigning workload 44 definition 44 independent workload 154 serice time, CPU 175 serice time adjustment 128 set of model results, graphing a single 238 shared folder modeling 148 single workload, specifying growth for a 112 size selecting main storage 123 SMF (System Measurement Facility) 273 sort query (medium complexity) 259 specify actie jobs objecties 32 objecties 146 Specify Growth of Workload Actiity display 208, 210 Specify Job Classification Category display 192 Specify Objecties and Actie Jobs display 199, 202 Specify Storage Sizes for CPU Model display 221 specifying logical partitions 64 spool workload group 257 SPOOL workload group 257 spooling, print 8 SQL RTW workload 250 SQL RTW workload 250 start BEST/1, how to 1 starting BEST/1 1 storage recommendations for achieing effectie 139 storage pool apportioning 129 aerage, number of jobs per 6 changing main 128 editing main 67 report, main 231 sync read rate per 6 storage pool report, main 97 storage size selecting main 123 strategy for defining workloads 145 subsystem additional modeling considerations for 9337 disk array 173 hardware checksum, disk array 172 summary of workloads, functions, transactions, and objecties 34 RTW transaction 255 summary query (medium complexity) 259 summary report, analysis 229 sync read rate per storage pool 6 sync reads guidelines, editing 103 synchronous reads 103 guidelines, editing 103 synchronous reads per second 14, 97, 98 system adding throughput to 197 analytic model 6 growth 208 projecting future needs 208 jobs 21 mixing workloads 51 mixing workloads from different 51 modeling changes to the 101 projecting future needs 208 work 21 system, adding throughput to an existing 197 System/36 migration, utility 272 system configuration IBM-supplied configurations 62 system configuration menu 62 system resources, changing 119 system sizing 317 T table relatie CPU power 287 tables and indexes, RTW 255 tasks licensed internal code 42 terminology memory modeling 136 thrashing 35 thresholds editing utilization guidelines and 102 throughput adding to an existing system 197 aerage interactie and non-interactie 6 interactie 92, 108 time calibrating response 87 internal and external response 5 response external 108 response time, ariations 281 time for a different CPU, computing batch run 286 tips when doing what-if...? analysis 181 tool leaing the capacity planning from graphics 229 topics, selected modeling 145 transaction change 78 changing 116 define non-interactie 194 defining non-interactie 48, 149 definition 26 details, RTW 250 example showing workloads, functions and 30 non-interactie 26 per hour 107 summary of workloads 34 type 27 transaction summary RTW 255 transaction throughput example, predicting batch 157 tuning characteristics 4 two graphs scenario, oerlaying 239 type assign jobs to workloads by job 43 U update in-process inentory 251 upgrading to RISC system 328 use capacity planning, when to 2 user-defined sequence of workload growth, specifying a 110 utilization communications lines BEST/1 Capacity Planning Tool V5R1

367 utilization (continued) controllers 5 hardware 5 Integrated Netfinity Serer 5 IOP 5 utilization, hardware 5 utilization guidelines and thresholds, editing 102 V alues change CPU and other resource 63 changing CPU and other resource 121 alues, editing CISC-to-RISC conersion factors 105 alues, editing paging behaior 104 ariation response time 281 erify objecties 79 W WAD, (write assist deice) 173 weighted aerages 27 weighting factor 77 window modeling batch 160 manual batch 283 work, modeling non-interactie 149 work classification 19 work to the model, defining 21 Work with BEST/1 Model 208 adanced user leel 11 basic user leel 11 Work with BEST/1 Model display 198 work with BEST/1 models 71 Work with BEST/1 Models display 9, 188, 196, 198 Work with CPU Models display 219, 220, 225 work with disk resources 66 Work with Graph Formats display 212, 214, 217 work with results 13 Work with Results display 199, 201, 203, 205, 210, 211 working set 136 working set size 175 working with functions 76 workload *BATCHJOB 33, 76 *BATCHJOB definition 154 *NORMAL 33, 76 actiity leel 129 automatically, growing a 114 building a model using predefined 55 by job name, assign jobs to 44 by job name, assign serer jobs to 44 by job type, assigning jobs to 43 calibrating *BATCHJOB 156 change transactions 78 classifying jobs into 39 combining 24 communications 171 workload (continued) communications, assign jobs to 46 concepts 19 concepts for selecting data for capacity 35 correspondence center type 263 data selecting 35 default 39 definition 22 description 23 from different systems, mixing 51 functions, transactions, and objecties, summary of 34 functions and transactions, example 30 group, BATCH 257 group, SPOOL 257 groups 23 growing automatically 114 INDUSTRY 24 isolation of batch into an independent 154 managerial type 263 manually growing a 110 OfficeVision 260 OfficeVision Benchmark type 262 portability 79 predefined 23, 55 batch workload 23 RAMP-C 23 predefined workload 23 printing spooled printing 23 report 94 reiewing the 147 saing 24 secretarial type 263 select predefined 58 SERVER 23 specifying a user-defined sequence 110 specifying growth for a single 112 SQL RTW 250 strategy for defining 145 transactions 78 type correspondence center 263 managerial 263 secretarial 263 using BATCH predefined 57 using predefined 55 erify the 74 working with functions 76 workload, default 41 workload characteristics, I/O 260 workload functions, working with 76 workload group Client/Serer 263 COMMERCIAL 249 Industry 265 predefined 55 SPOOL 257 workload groups for capacity planning 249 workload growth specifying a user-defined sequence of 110 workload report 230 workload type professional 263 write assist deice (WAD) 173 write cache 174 write cache, RAID 174 Index 347

368 348 BEST/1 Capacity Planning Tool V5R1

369 Readers Comments We d Like to Hear from You iseries BEST/1 Capacity Planning Tool Version 5 Publication No. SC Oerall, how satisfied are you with the information in this book? Very Satisfied Satisfied Neutral Dissatisfied Very Dissatisfied Oerall satisfaction h h h h h How satisfied are you that the information in this book is: Very Satisfied Satisfied Neutral Dissatisfied Very Dissatisfied Accurate h h h h h Complete h h h h h Easy to find h h h h h Easy to understand h h h h h Well organized h h h h h Applicable to your tasks h h h h h Please tell us how we can improe this book: Thank you for your responses. May we contact you? h Yes h No When you send comments to IBM, you grant IBM a nonexclusie right to use or distribute your comments in any way it beliees appropriate without incurring any obligation to you. Name Address Company or Organization Phone No.

370 Readers Comments We d Like to Hear from You SC SC Fold and Tape Please do not staple Fold and Tape BUSINESS REPLY MAIL FIRST-CLASS MAIL PERMIT NO. 40 ARMONK, NEW YORK POSTAGE WILL BE PAID BY ADDRESSEE IBM CORPORATION ATTN DEPT HWY 52 N ROCHESTER MN NO POSTAGE NECESSARY IF MAILED IN THE UNITED STATES Fold and Tape Please do not staple Fold and Tape Cut or Fold Along Line Cut or Fold Along Line

371

372 Printed in the United States of America on recycled paper containing 10% recoered post-consumer fiber. SC