AS400 Server Performance Tools

AS/400e series IBM

Performance Tools for AS/400Version 4

SC41-5340-00

AS/400e series IBM

Performance Tools for AS/400Version 4

SC41-5340-00

Note

Before using this information and the product it supports, be sure to read the general information under “Notices” on page xiii.

First Edition (February 1998)

| This edition applies to the licensed programs IBM Performance Tools for AS/400 (Program 5769-PT1), Version 4 Release 2 Modifica-| tion 0; IBM Operating System/400 (Program 5769-SS1), Version 4 Release 2 Modification 0, and to all subsequent releases and| modifications until otherwise indicated in new editions. This edition applies only to reduced instruction set computer (RISC) systems.

Copyright International Business Machines Corporation 1998. All rights reserved.Note to U.S. Government Users — Documentation related to restricted rights — Use, duplication or disclosure is subject torestrictions set forth in GSA ADP Schedule Contract with IBM Corp.

Contents

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiiProgramming Interface Information . . . . . . . . . . . . . . . . . . . . . . . . . xivTrademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

About Performance Tools (SC41-5340) . . . . . . . . . . . . . . . . . . . . . . xviiWho should read this book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviiAS/400 Operations Navigator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviiPrerequisite and related information . . . . . . . . . . . . . . . . . . . . . . . . xviii

| Information available on the World Wide Web . . . . . . . . . . . . . . . . . . . xix| How to send your comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix

| Summary of Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi

| Chapter 1. Introduction to Performance Tools . . . . . . . . . . . . . . . . . 1-1| Why Manage Performance? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1| Performance Capabilities—OS/400 and Performance Tools . . . . . . . . . . . 1-2| OS/400 Has Performance Management Basics . . . . . . . . . . . . . . . . . 1-2| Performance Tools Builds on OS/400 Function . . . . . . . . . . . . . . . . . 1-2| Manager Features and Agent Features . . . . . . . . . . . . . . . . . . . . . 1-3| Performance Tools Makes Performance Management Possible . . . . . . . 1-3| Performance Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3| A Recommended Approach for Setting an Objective . . . . . . . . . . . . . . 1-5| Performance Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6| Capacity Planning—Manager Feature . . . . . . . . . . . . . . . . . . . . . . . . 1-6| Capacity Planning—Agent Feature . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6| Performance Analysis—Manager Feature . . . . . . . . . . . . . . . . . . . . . . 1-7| Performance Analysis—Agent Feature . . . . . . . . . . . . . . . . . . . . . . . 1-7| Performance Analysis Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8

Chapter 2. Starting Performance Tools . . . . . . . . . . . . . . . . . . . . . 2-1Installing Performance Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1How Performance Tools Counts Users . . . . . . . . . . . . . . . . . . . . . . . 2-1Printer File and Output Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1Start Performance Tools (STRPFRT) Command . . . . . . . . . . . . . . . . . . 2-2Displaying the System or Job Status—Manager Feature . . . . . . . . . . . . . 2-3

Chapter 3. Collecting System Performance Data . . . . . . . . . . . . . . . 3-1| Why Collect Performance Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

When to Collect Performance Data . . . . . . . . . . . . . . . . . . . . . . . . . 3-1When to End Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3Collecting Sample or Trace Data . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

Using System Defaults to Collect Data . . . . . . . . . . . . . . . . . . . . . . 3-7Using Menus to Collect Data . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8Using the STRPFRMON Command to Collect Trace Data . . . . . . . . . 3-10

Collecting Performance Data Automatically . . . . . . . . . . . . . . . . . . . . 3-11Performance Collection Setup . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13

Summary of Data Collection and Report Commands—Manager Feature . . . 3-13System-Level Analysis—Manager Feature . . . . . . . . . . . . . . . . . . . 3-13Job Trace Analysis—Manager Feature . . . . . . . . . . . . . . . . . . . . . 3-15File Use and Database Structure Analysis—Manager Feature . . . . . . . 3-16

Copyright IBM Corp. 1998 iii

Job Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16

Chapter 4. Advisor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1Collecting the Right Performance Data . . . . . . . . . . . . . . . . . . . . . . . 4-2Requesting an Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Selecting a Member . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4Selecting Time Intervals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4Using a Histogram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5Analyzing Trace Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7

Using the Advisor’s Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7Understanding Recommendations . . . . . . . . . . . . . . . . . . . . . . . . 4-8Changing System Tuning Values . . . . . . . . . . . . . . . . . . . . . . . . 4-10Understanding Conclusions . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11Understanding Interval Conclusions . . . . . . . . . . . . . . . . . . . . . . 4-12

Tune System by Advisor’s Recommendations . . . . . . . . . . . . . . . . . . 4-14

Chapter 5. Displaying Performance Data . . . . . . . . . . . . . . . . . . . . 5-1Display Performance Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Display Performance Data by Subsystem . . . . . . . . . . . . . . . . . . . . 5-4Display Performance Data by Job Type . . . . . . . . . . . . . . . . . . . . . 5-4Display Performance Data by Interval . . . . . . . . . . . . . . . . . . . . . . 5-5Display Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6Display Job Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7

Display Performance Data for System Resources . . . . . . . . . . . . . . . . . 5-8Display Pool Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8Display Pool Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9Display Disk Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10Display Disk Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11Display Communications Line Detail . . . . . . . . . . . . . . . . . . . . . . 5-11Display Remote Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12Display Communications Interval Data . . . . . . . . . . . . . . . . . . . . . 5-13Display Remote Interval Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14Display Network Interface Data . . . . . . . . . . . . . . . . . . . . . . . . . 5-15Display Channel Interval Data . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16Display Maintenance Channel Data . . . . . . . . . . . . . . . . . . . . . . . 5-18

Chapter 6. System Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1Work with System Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Single-Processor System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3Multiple-Processor System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3Automatic Refresh Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4Monitoring Specific Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5Working with Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6Displaying Different Information Types . . . . . . . . . . . . . . . . . . . . . . 6-7Accessing Work Management Functions . . . . . . . . . . . . . . . . . . . . . 6-8Content of Database File QAITMON . . . . . . . . . . . . . . . . . . . . . . . 6-8

Print Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9Summary Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10Detail Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12

Chapter 7. Performance Reports—Manager Feature . . . . . . . . . . . . . 7-1A Performance Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Performance Report Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2Available Performance Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3

iv Performance Tools V4R2

Which Report Do I Want? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5Printing Performance Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5

Using Menus to Print Performance Reports . . . . . . . . . . . . . . . . . . . 7-6Using Defaults to Print Performance Reports . . . . . . . . . . . . . . . . . 7-11Why Performance Reports May Seem Inconsistent . . . . . . . . . . . . . 7-15

System Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17Printing the System Report . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17What Is the System Report? . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17Workload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-18Resource Utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-19Resource Utilization Expansion . . . . . . . . . . . . . . . . . . . . . . . . . 7-19Storage Pool Utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-19Disk Utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-19Communications Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-19Report Selection Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-20

Sample System Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-20Workload Section: Interactive Workload–Sample . . . . . . . . . . . . . . 7-20Workload Section: Noninteractive Workload–Sample . . . . . . . . . . . . 7-21Resource Utilization (First Part)–Sample . . . . . . . . . . . . . . . . . . . . 7-21Resource Utilization (Second Part)–Sample . . . . . . . . . . . . . . . . . . 7-21Resource Utilization Expansion (First Part)–Sample . . . . . . . . . . . . . 7-21Resource Utilization Expansion (Second Part)–Sample . . . . . . . . . . . 7-22Storage Pool Utilization–Sample . . . . . . . . . . . . . . . . . . . . . . . . 7-22Disk Utilization–Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-22Communications Summary–Sample . . . . . . . . . . . . . . . . . . . . . . 7-23System Report Selection Criteria: Select Parameters–Sample . . . . . . . 7-24System Report Selection Criteria: Omit Parameters–Sample . . . . . . . . 7-24Report Selection Criteria: Selected Start/End Time/Date–Sample . . . . . 7-25Report Selection Criteria: Date/Time Intervals–Sample . . . . . . . . . . . 7-25

Component Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-25Printing the Component Report . . . . . . . . . . . . . . . . . . . . . . . . . 7-25What Is the Component Report? . . . . . . . . . . . . . . . . . . . . . . . . 7-25Component Interval Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-25Job Workload Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-26Storage Pool Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-26Disk Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-26Input/Output Processor (IOP) Utilizations . . . . . . . . . . . . . . . . . . . 7-26Local Work Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-26Remote Work Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-27Exception Occurrence Summary and Interval Counts . . . . . . . . . . . . 7-27Database Journaling Summary . . . . . . . . . . . . . . . . . . . . . . . . . 7-27Report Selection Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-28

Sample Component Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-29Component Interval Activity–Sample . . . . . . . . . . . . . . . . . . . . . . 7-29Job Workload Activity–Sample . . . . . . . . . . . . . . . . . . . . . . . . . 7-29Storage Pool Activity–Sample . . . . . . . . . . . . . . . . . . . . . . . . . . 7-31Disk Activity–Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-31IOP Utilizations–Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-32Local Work Stations–Response Time Buckets–Sample . . . . . . . . . . . 7-33Remote Work Stations–Response Time Buckets–Sample . . . . . . . . . . 7-33Exception Occurrence Summary and Interval Counts–Sample . . . . . . . 7-34Database Journaling Summary–Sample . . . . . . . . . . . . . . . . . . . . 7-34Component Report Selection Criteria: Select Parameters–Sample . . . . 7-35Component Report Selection Criteria: Omit Parameters–Sample . . . . . 7-36

Contents v

Transaction Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-36Printing the Transaction Report . . . . . . . . . . . . . . . . . . . . . . . . . 7-36What Is the Transaction Report? . . . . . . . . . . . . . . . . . . . . . . . . 7-37Job Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-38

Interactive Throughput Section . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-40Interactive CPU Utilization Section . . . . . . . . . . . . . . . . . . . . . . . . . 7-40Interactive Response Time Section . . . . . . . . . . . . . . . . . . . . . . . . 7-40Scatter Diagram Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-41Interactive Program Transaction Statistics Section . . . . . . . . . . . . . . . 7-41Seize/Lock Conflicts by Object Section . . . . . . . . . . . . . . . . . . . . . . 7-41Special System Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-41

To Print . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-41Priority-Jobtype-Pool Statistics Section . . . . . . . . . . . . . . . . . . . . . 7-42Job Statistics Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-42Interactive Program Statistics Section . . . . . . . . . . . . . . . . . . . . . 7-42Individual Transaction Statistics Section . . . . . . . . . . . . . . . . . . . . 7-43Longest Seize/Lock Conflicts Section . . . . . . . . . . . . . . . . . . . . . 7-43Longest Holders of Seize/Lock Conflicts Section . . . . . . . . . . . . . . . 7-44Batch Job Analysis Section . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-44Concurrent Batch Job Statistics . . . . . . . . . . . . . . . . . . . . . . . . . 7-44Report Selection Criteria Section . . . . . . . . . . . . . . . . . . . . . . . . 7-45

Transaction Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-45To Print . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-45Job Summary Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-46

Transition Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-46To Print . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-46Transition Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-46

Sample Transaction Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-49Job Summary–Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-49System Summary Data (First Part)–Sample . . . . . . . . . . . . . . . . . . 7-50System Summary Data (Second Part)–Sample . . . . . . . . . . . . . . . . 7-51System Summary Data (Third Part)–Sample . . . . . . . . . . . . . . . . . 7-52Distribution of Simple, Medium, and Complex Processing Unit

Transactions–Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-52Transaction Significance–Sample . . . . . . . . . . . . . . . . . . . . . . . . 7-53Interactive Transactions by 5-Minute Intervals–Sample . . . . . . . . . . . 7-54Interactive Throughput by 5-Minute Intervals–Sample . . . . . . . . . . . . 7-54Interactive CPU Utilization by 5-Minute Intervals–Sample . . . . . . . . . . 7-55Interactive Response Time by 5-Minute Intervals–Sample . . . . . . . . . 7-55Scatter Diagram of Interactive Transactions by 5-Minute Intervals–Sample 7-55Interactive Program Statistics–Sample . . . . . . . . . . . . . . . . . . . . . 7-56Summary of Seize/Lock Conflicts by Object–Sample . . . . . . . . . . . . . 7-57Priority-Jobtype-Pool Statistics–Sample . . . . . . . . . . . . . . . . . . . . 7-58Job Statistics–Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-58Interactive Program Statistics–Sample . . . . . . . . . . . . . . . . . . . . . 7-59Individual Transaction Statistics–Sample . . . . . . . . . . . . . . . . . . . . 7-59Longest Seize/Lock Conflicts–Sample . . . . . . . . . . . . . . . . . . . . . 7-59Longest Holders of Seize/Lock Conflicts–Sample . . . . . . . . . . . . . . . 7-60Batch Job Analysis–Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-60

| Concurrent Batch Job Statistics–Sample . . . . . . . . . . . . . . . . . . . . 7-61Report Selection Criteria-Sample . . . . . . . . . . . . . . . . . . . . . . . . 7-61Transaction Report Option–Sample . . . . . . . . . . . . . . . . . . . . . . . 7-62Transition Report Option–Sample . . . . . . . . . . . . . . . . . . . . . . . . 7-62

Lock Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-63

vi Performance Tools V4R2

Printing the Lock Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-63What Is the Lock Report? . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-64Analyzing Seize/Lock Conflicts . . . . . . . . . . . . . . . . . . . . . . . . . 7-64

| Thread Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-65Sample Lock Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-65

Lock Report–Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-66Lock Report–Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-66

Job Interval Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-66Printing the Job Interval Report . . . . . . . . . . . . . . . . . . . . . . . . . 7-66What Is the Job Interval Report? . . . . . . . . . . . . . . . . . . . . . . . . 7-67Interactive Job Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-67Noninteractive Job Summary . . . . . . . . . . . . . . . . . . . . . . . . . . 7-67Interactive Job Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-67Noninteractive Job Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-68Report Selection Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-68

Sample Job Interval Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-68Interactive Job Summary–Sample . . . . . . . . . . . . . . . . . . . . . . . 7-68Noninteractive Job Summary–Sample . . . . . . . . . . . . . . . . . . . . . 7-69Interactive Job Detail–Sample . . . . . . . . . . . . . . . . . . . . . . . . . . 7-69Noninteractive Job Detail –Sample . . . . . . . . . . . . . . . . . . . . . . . 7-70Job Interval Report Selection Criteria: Select Parameters–Sample . . . . . 7-71Job Interval Report Selection Criteria: Omit Parameters–Sample . . . . . 7-72

Pool Interval Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-72Printing the Pool Interval Report . . . . . . . . . . . . . . . . . . . . . . . . 7-73What Is the Pool Interval Report? . . . . . . . . . . . . . . . . . . . . . . . . 7-73Subsystem Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-73Pool Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-73Report Selection Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-73

Sample Pool Interval Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-73Subsystem Activity–Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-74Pool Activity–Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-74Report Selection Criteria–Sample . . . . . . . . . . . . . . . . . . . . . . . . 7-75

Resource Interval Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-76Printing the Resource Interval Report . . . . . . . . . . . . . . . . . . . . . 7-76What Is the Resource Interval Report? . . . . . . . . . . . . . . . . . . . . . 7-76Disk Utilization Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-77Disk Utilization Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-77Communications Line Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-77IOP Utilizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-78Local Work Station Response Times . . . . . . . . . . . . . . . . . . . . . . 7-79Remote Work Station Response Times . . . . . . . . . . . . . . . . . . . . 7-79

Sample Resource Interval Reports . . . . . . . . . . . . . . . . . . . . . . . . . 7-80Disk Utilization Summary–Sample . . . . . . . . . . . . . . . . . . . . . . . 7-80Disk Utilization Detail–Sample . . . . . . . . . . . . . . . . . . . . . . . . . . 7-80Communications Line Detail–SDLC Sample . . . . . . . . . . . . . . . . . . 7-81Communications Line Detail–X.25 Sample . . . . . . . . . . . . . . . . . . 7-82Communications Line Detail–TRLAN Sample . . . . . . . . . . . . . . . . . 7-82Communications Line Detail–ELAN Sample . . . . . . . . . . . . . . . . . . 7-83Communications Line Detail–DDI Sample . . . . . . . . . . . . . . . . . . . 7-84Communications Line Detail–FRLY Sample . . . . . . . . . . . . . . . . . . 7-84Communications Line Detail–ASYNC Sample . . . . . . . . . . . . . . . . . 7-84Communications Line Detail–BSC Sample . . . . . . . . . . . . . . . . . . 7-85Communications Line Detail–ISDN Network Interface Sample . . . . . . . 7-85Communications Line Detail–NWI Maintenance Sample . . . . . . . . . . . 7-86

Contents vii

Communications Line Detail–IDLC Samples . . . . . . . . . . . . . . . . . . 7-87IOP Utilizations–Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-87Local Work Station Response Times–Sample . . . . . . . . . . . . . . . . . 7-88Remote Work Station Response Times–Sample . . . . . . . . . . . . . . . 7-89

Batch Job Trace Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-89Printing the Batch Job Trace Report . . . . . . . . . . . . . . . . . . . . . . 7-90What Is the Batch Job Trace Report? . . . . . . . . . . . . . . . . . . . . . 7-90Job Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-90

Job Summary Report–Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-90Performance Trace Database Files . . . . . . . . . . . . . . . . . . . . . . . . 7-90

QTRTSUM and QTRJOBT Files . . . . . . . . . . . . . . . . . . . . . . . . 7-91QTRJSUM File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-94QTRDMPT File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-96QAPTLCKD File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-101

Performance Report Columns . . . . . . . . . . . . . . . . . . . . . . . . . . 7-102

Chapter 8. Transaction Boundaries—Manager Feature . . . . . . . . . . . 8-1Display I/O Transaction Boundary Information . . . . . . . . . . . . . . . . . . . 8-1SNA Performance Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3

Correlation Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4Connection Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4Device Description Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5T2 Station I/O Manager Task Fields . . . . . . . . . . . . . . . . . . . . . . . 8-5Session Traffic Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6Sending Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7Receiving Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10Intermediate Session Traffic Work Load . . . . . . . . . . . . . . . . . . . . 8-11Control Traffic Work Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11Comparing Different Priority Levels . . . . . . . . . . . . . . . . . . . . . . . 8-11

APPN Control Point Performance Measurements . . . . . . . . . . . . . . . . 8-11APPN Work Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-12Session Setup Work Activities . . . . . . . . . . . . . . . . . . . . . . . . . . 8-17

APPC Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-21From System A's Perspective . . . . . . . . . . . . . . . . . . . . . . . . . . 8-21From System B's Perspective . . . . . . . . . . . . . . . . . . . . . . . . . . 8-22APPC Performance Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-22

Performance Measurement and SNADS . . . . . . . . . . . . . . . . . . . . . 8-23SNADS Transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-23

SNADS Sample Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-29Sample Data Interpretation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-29

SNADS Performance Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-32OS/400 File Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-33Pass-Through Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-34

Pass-Through Performance Notes . . . . . . . . . . . . . . . . . . . . . . . 8-35Data Queue Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-35

Chapter 9. Performance Graphics . . . . . . . . . . . . . . . . . . . . . . . . 9-1Summary—Manager Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1Work with Graph Formats and Packages—Manager Feature . . . . . . . . . . 9-2

Create Graph Format—Manager Feature . . . . . . . . . . . . . . . . . . . . 9-4Graph Types—Manager Feature . . . . . . . . . . . . . . . . . . . . . . . . . 9-4Data Types—Manager Feature . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6Legends—Manager Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-9Create Graph Package—Manager Feature . . . . . . . . . . . . . . . . . . . 9-9

viii Performance Tools V4R2

Change Graph Formats and Packages—Manager Feature . . . . . . . . . 9-10Copy Graph Formats and Packages—Manager Feature . . . . . . . . . . . 9-11Delete Graph Formats and Packages—Manager Feature . . . . . . . . . . 9-12Display Sample Graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-12Display Package Contents—Manager Feature . . . . . . . . . . . . . . . . 9-12

Work with Historical Data—Manager Feature . . . . . . . . . . . . . . . . . . . 9-13Create Historical Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-14Delete Historical Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-15

Display Graphs and Packages—Manager Feature . . . . . . . . . . . . . . . 9-15Display Performance Graphs—Manager Feature . . . . . . . . . . . . . . . 9-16Display Sample Graph—Manager Feature . . . . . . . . . . . . . . . . . . . 9-17Display Graph Package—Manager Feature . . . . . . . . . . . . . . . . . . 9-17Select Performance Data Member—Manager Feature . . . . . . . . . . . . 9-17Select Categories for Performance Graphs—Manager Feature . . . . . . . 9-18Specify Graph Options—Manager Feature . . . . . . . . . . . . . . . . . . 9-18Display Historical Graphs—Manager Feature . . . . . . . . . . . . . . . . . 9-20

Display Graph Overlay—Manager Feature . . . . . . . . . . . . . . . . . . . . 9-21

Chapter 10. Performance Utilities—Manager Feature . . . . . . . . . . . . 10-1Job Traces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1File and Process Access Group (PAG) Utilities . . . . . . . . . . . . . . . . . 10-2Analyzing Job Flow and Transaction Performance . . . . . . . . . . . . . . . 10-2

Start Job Trace (STRJOBTRC) Command . . . . . . . . . . . . . . . . . . 10-3End Job Trace (ENDJOBTRC) Command . . . . . . . . . . . . . . . . . . . 10-3Print Job Trace (PRTJOBTRC) Command . . . . . . . . . . . . . . . . . . . 10-4

Analyzing the Relationship of Programs and Database Files . . . . . . . . . . 10-9Analyze Program (ANZPGM) Command . . . . . . . . . . . . . . . . . . . . 10-9Analyze Database File (ANZDBF) Command . . . . . . . . . . . . . . . . 10-11Analyze Database File Keys (ANZDBFKEY) Command . . . . . . . . . . 10-13

Analyzing Process Information . . . . . . . . . . . . . . . . . . . . . . . . . . 10-16Display Access Group (DSPACCGRP) Command . . . . . . . . . . . . . 10-16Analyze Process Access Group (ANZACCGRP) Command . . . . . . . . 10-18

Chapter 11. Performance Explorer . . . . . . . . . . . . . . . . . . . . . . . 11-1Do I Need Performance Explorer? . . . . . . . . . . . . . . . . . . . . . . . . . 11-1

Who Needs Performance Explorer . . . . . . . . . . . . . . . . . . . . . . . 11-1When You Need Performance Explorer . . . . . . . . . . . . . . . . . . . . 11-2

Comparison of Explorer to Other Performance Tools . . . . . . . . . . . . . . 11-2Performance Explorer and Advisor Functions . . . . . . . . . . . . . . . . . 11-2Performance Explorer and Performance Monitor . . . . . . . . . . . . . . . 11-2

Benefits of Performance Explorer . . . . . . . . . . . . . . . . . . . . . . . . . 11-3How Performance Explorer Works . . . . . . . . . . . . . . . . . . . . . . . . . 11-3Performance Explorer Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 11-4

General Flow of the Performance Explorer . . . . . . . . . . . . . . . . . . 11-5Creating a Performance Explorer Definition . . . . . . . . . . . . . . . . . . . . 11-6Starting the Performance Explorer . . . . . . . . . . . . . . . . . . . . . . . . . 11-7Ending the Performance Explorer . . . . . . . . . . . . . . . . . . . . . . . . . 11-7Deleting Performance Explorer Data . . . . . . . . . . . . . . . . . . . . . . . . 11-8

| Creating and Printing Performance Explorer Reports . . . . . . . . . . . . . . 11-8Finding Your Performance Explorer Definitions . . . . . . . . . . . . . . . . . 11-9Types of Performance Explorer Reports . . . . . . . . . . . . . . . . . . . . . 11-9

Common Report Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-9Report-Specific Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-15

Mapping OPM High-Level Language (HLL) Statements to Source Code . . 11-35

Contents ix

Chapter 12. Managing the Performance Tools Configuration . . . . . . . 12-1Work with Functional Areas—Manager Feature . . . . . . . . . . . . . . . . . 12-2

Creating a Functional Area—Manager Feature . . . . . . . . . . . . . . . . 12-3Changing a Functional Area—Manager Feature . . . . . . . . . . . . . . . 12-4Deleting a Functional Area—Manager Feature . . . . . . . . . . . . . . . . 12-5Copying a Functional Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5

Delete Performance Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5Copy Performance Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-7Convert Performance Data (CVTPFRDTA) Command . . . . . . . . . . . . . 12-8

Chapter 13. A Problem Analysis Case Study . . . . . . . . . . . . . . . . . 13-1Introduction to Performance Analysis . . . . . . . . . . . . . . . . . . . . . . . 13-1The Case Study . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2

The Players . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2The Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3The Problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3Checking the System’s Performance . . . . . . . . . . . . . . . . . . . . . . 13-4Reviewing the End-User Survey Results . . . . . . . . . . . . . . . . . . . 13-10Analyzing System Performance . . . . . . . . . . . . . . . . . . . . . . . . 13-11Understanding the Symptoms of the Problem . . . . . . . . . . . . . . . . 13-21Analyzing the Data—Manager Feature . . . . . . . . . . . . . . . . . . . . 13-23Case Study Data Reports—Manager Feature . . . . . . . . . . . . . . . . 13-28Finding the Cause and Correcting the Problem . . . . . . . . . . . . . . . 13-32Final Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-33

Chapter 14. Working with Historical Data—Agent Feature . . . . . . . . 14-1Create Historical Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-2Delete Historical Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-3

Chapter 15. Managing the Performance Data—Agent Feature . . . . . . 15-1Delete Performance Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1Copy Performance Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2Convert Performance Data (CVTPFRDTA) Command . . . . . . . . . . . . . 15-4

| Convert Performance Thread Data (CVTPFRTHD) Command . . . . . . . . . 15-6

Appendix A. Performance Tools CL Commands . . . . . . . . . . . . . . A-1ADDPEXDFN (Add Performance Explorer Definition) Command . . . . . . . A-2ANZACCGRP (Analyze Access Group) Command . . . . . . . . . . . . . . . A-5ANZDBF (Analyze Database File) Command . . . . . . . . . . . . . . . . . . . A-6ANZDBFKEY (Analyze Database File Keys) Command . . . . . . . . . . . . A-7ANZPFRDTA (Analyze Performance Data) Command . . . . . . . . . . . . . A-7ANZPGM (Analyze Program) Command . . . . . . . . . . . . . . . . . . . . . A-8CHGFCNARA (Change Functional Area) Command . . . . . . . . . . . . . . A-9CHGGPHFMT (Change Graph Format) Command . . . . . . . . . . . . . . . A-10CHGGPHPKG (Change Graph Package) Command . . . . . . . . . . . . . . A-13CHGJOBTYP (Change Job Type) Command . . . . . . . . . . . . . . . . . . . A-14CHGPEXDFN (Change Performance Explorer Definition) Command . . . . . A-14CPYFCNARA (Copy Functional Area) Command . . . . . . . . . . . . . . . . A-17CPYGPHFMT (Copy Graph Format) Command . . . . . . . . . . . . . . . . . A-17CPYGPHPKG (Copy Graph Package) Command . . . . . . . . . . . . . . . . A-18CPYPFRDTA (Copy Performance Data) Command . . . . . . . . . . . . . . . A-19CRTFCNARA (Create Functional Area) Command . . . . . . . . . . . . . . . A-20CRTGPHFMT (Create Graph Format) Command . . . . . . . . . . . . . . . . A-21CRTGPHPKG (Create Graph Package) Command . . . . . . . . . . . . . . . A-24

x Performance Tools V4R2

CRTHSTDTA (Create Historical Data) Command . . . . . . . . . . . . . . . . A-25DLTFCNARA (Delete Functional Area) Command . . . . . . . . . . . . . . . . A-26DLTGPHFMT (Delete Graph Format) Command . . . . . . . . . . . . . . . . . A-27DLTGPHPKG (Delete Graph Package) Command . . . . . . . . . . . . . . . A-27DLTHSTDTA (Delete Historical Data) Command . . . . . . . . . . . . . . . . A-28DLTPEXDTA (Delete Performance Explorer Data) Command . . . . . . . . . A-29DLTPFRDTA (Delete Performance Data) . . . . . . . . . . . . . . . . . . . . . A-29DSPACCGRP (Display Access Group) Command . . . . . . . . . . . . . . . . A-30DSPHSTGPH (Display Historical Graph) Command . . . . . . . . . . . . . . . A-32DSPPFRDTA (Display Performance Data) Command . . . . . . . . . . . . . . A-35DSPPFRGPH (Display Performance Graph) Command . . . . . . . . . . . . A-36ENDJOBTRC (End Job Trace) Command . . . . . . . . . . . . . . . . . . . . A-41ENDPEX (End Performance Explorer) Command . . . . . . . . . . . . . . . . A-42PRTACTRPT (Print Activity Report) Command . . . . . . . . . . . . . . . . . A-43PRTCPTRPT (Print Component Report) Command . . . . . . . . . . . . . . . A-45PRTJOBRPT (Print Job Report) Command . . . . . . . . . . . . . . . . . . . . A-48PRTJOBTRC (Print Job Trace) Command . . . . . . . . . . . . . . . . . . . . A-51PRTLCKRPT (Print Lock Report) Command . . . . . . . . . . . . . . . . . . . A-52PRTPEXRPT (Print Performance Explorer Report) Command . . . . . . . . . A-53PRTPOLRPT (Print Pool Report) Command . . . . . . . . . . . . . . . . . . . A-56PRTRSCRPT (Print Resource Report) Command . . . . . . . . . . . . . . . . A-59PRTSYSRPT (Print System Report) Command . . . . . . . . . . . . . . . . . A-60PRTTNSRPT (Print Transaction Report) Command . . . . . . . . . . . . . . . A-64PRTTRCRPT (Print Trace Report) Command . . . . . . . . . . . . . . . . . . A-66RMVPEXDFN (Remove Performance Explorer Definition) Command . . . . . A-67STRJOBTRC (Start Job Trace) Command . . . . . . . . . . . . . . . . . . . . A-68STRPEX (Start Performance Explorer) Command . . . . . . . . . . . . . . . . A-69STRPFRG (Start Performance Graphics) Command . . . . . . . . . . . . . . A-70STRPFRT (Start Performance Tools) Command . . . . . . . . . . . . . . . . . A-70WRKFCNARA (Work with Functional Areas) Command . . . . . . . . . . . . A-71WRKSYSACT (Work with System Activity) Command . . . . . . . . . . . . . A-72

Appendix B. Defining Transaction Boundaries . . . . . . . . . . . . . . . B-1Elements of Response Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1Differences in the Transaction Response Reports . . . . . . . . . . . . . . . . B-2

Operational Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4

Appendix C. Correlation of the System/36 and AS/400 SystemPerformance Parameters—Manager Feature . . . . . . . . . . . . . . . . . C-1

Appendix D. Comparison of Performance Tools . . . . . . . . . . . . . . D-1Comparison of Functions, Menu Options, and Commands . . . . . . . . . . . D-1

Appendix E. Managing AS/400 System Performance in a Network . . . E-1Planning the Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1Implementing the Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1Additional Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-4

Appendix F. Performance Checklist—Manager Feature . . . . . . . . . . . F-1Planning for Performance and Tuning . . . . . . . . . . . . . . . . . . . . . . . . F-1Basic Tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-2

| Work with System Status Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . F-2| Work with Disk Status Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-3| Work with System Activity Tips . . . . . . . . . . . . . . . . . . . . . . . . . . F-3

Contents xi

General Tuning Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-4General Performance Facts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-4

Bibliography . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . X-1

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . X-3

xii Performance Tools V4R2

Notices

This information was developed for products and services offered in the U.S.A. IBMmay not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on the pro-ducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right may beused instead. However, it is the user's responsibility to evaluate and verify the oper-ation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not give you anylicense to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM Corporation500 Columbus AvenueThornwood, NY 10594U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia CorporationLicensing2-31 Roppongi 3-chome, Minato-kuTokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law: INTERNA-TIONAL 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 OFNON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULARPURPOSE. Some states do not allow disclaimer of express or implied warranties incertain 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 beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in this publicationat any time without notice.

Licensees of this program who wish to have information about it for the purpose ofenabling: (i) the exchange of information between independently created programsand other programs (including this one) and (ii) the mutual use of the informationwhich has been exchanged, should contact:

Copyright IBM Corp. 1998 xiii

IBM CorporationSoftware Interoperability Coordinator3605 Highway 52 NRochester, MN 55901-7829U.S.A.

Such information may be available, 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 avail-able for it are provided by IBM under terms of the IBM Customer Agreement or anyequivalent agreement between us.

Any performance data contained herein was determined in a controlled environ-ment. Therefore, the results obtained in other operating environments may vary sig-nificantly. Some measurements may have been made on development-levelsystems and there is no guarantee that these measurements will be the same ongenerally available systems. Furthermore, some measurement may have been esti-mated through extrapolation. Actual results may vary. Users of this documentshould verify the applicable data for their specific environment.

This information contains examples of data and reports used in daily business oper-ations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, whichillustrates programming techniques on various operating platforms. You may copy,modify, and distribute these sample programs in any form without payment to IBM,for the purposes of developing, using, marketing or distributing application pro-grams conforming to the application programming interface for the operating plat-form for which the sample programs are written. These examples have not beenthoroughly tested under all conditions. IBM, therefore, cannot guarantee or implyreliability, serviceability, or function of these programs. You may copy, modify, anddistribute these sample programs in any form without payment to IBM for the pur-poses of developing, using, marketing, or distributing application programs con-forming to IBM's application programming interfaces.

If you are viewing this information softcopy, the photographs and color illustrationsmay not appear.

Programming Interface InformationThis publication is intended to help you to achieve high system performance. Thispublication documents General-Use Programming Interface and Associated Guid-ance Information provided by IBM Performance Tools for AS/400 (5769-PT1).

General-Use programming interfaces allow the customer to write programs thatobtain the services of IBM Performance Tools for AS/400 and IBM OperatingSystem/400 licensed programs.

xiv Performance Tools V4R2

This publication documents Product-Sensitive Programming Interface and Associ-ated Guidance Information.

Product-Sensitive programming interfaces allow the customer installation to performtasks such as diagnosing, modifying, monitoring, repairing, tailoring, or tuning ofthis IBM software product. Use of such interfaces creates dependencies on thedetailed design or implementation of the IBM software product. Product-Sensitiveprogramming interfaces should be used only for these specialized purposes.Because of their dependencies on detailed design and implementation, it is to beexpected that programs written to such interfaces may need to be changed in orderto run with new product releases or versions, or as a result of service.

TrademarksThe following terms are trademarks of the IBM Corporation in the United States orother countries or both:

Advanced Function PrintingAdvanced 36AFPApplication System/400APPNAS/400AS/400eC/400Client AccessIBMInformation AssistantIntelligent Printer Data StreamIPDSMVSOfficeVision/400Operating System/400OS/400Personal Computer ATPersonal System/2RPG/400System/36SystemView400

Microsoft, Windows, Windows NT, and the Windows 95 logo are registered trade-marks of Microsoft Corporation.

UNIX is a registered trademark in the United States and other countries licensedexclusively through X/Open Company Limited

Java and HotJava are trademarks of Sun Microsystems, Inc.

Other company, product, and service names may be trademarks or service marksof others.

Notices xv

xvi Performance Tools V4R2

About Performance Tools (SC41-5340)

This book explains how to use performance tools to collect data about the perform-ance of a system, job, or program. It also explains how to analyze and print thedata to help identify and correct any problems.

The book addresses both the Manager feature and the Agent feature. Mostsections are marked to indicate the feature to which the information applies. If asection is not marked as Manager feature or Agent feature, the section applies toboth.

Who should read this bookThis book is intended for anyone who has to perform data collections and analyzeperformance data.

In this book, personal computer means an IBM Personal Computer such as a 5170Personal Computer AT or an 8560 Personal System/2.

The performance estimates presented are approximations which are believed to besound. The degree of success that you may achieve in the use of IBM equipmentand programs is dependent upon a number of factors, many of which are not underIBM's control. Thus, IBM neither warrants nor guarantees that you can or willachieve similar results. It is your responsibility to validate the estimates furnishedand to determine their relevance to your operation.

Any configuration recommended by the capacity planner of the Manager featureshould be verified with your marketing representative because the capacity plannerdoes not consider all attachable devices.

AS/400 Operations NavigatorAS/400 Operations Navigator is a powerful graphical interface for Windows 95/NTclients. With AS/400 Operations Navigator, you can use your Windows 95/NT skillsto manage and administer your AS/400 systems. You can work with databaseadministration, file systems, Internet network administration, users, and usergroups. You can even schedule regular system backups and display your hardwareand software inventory. Figure 0-1 on page xviii shows an example of the display.

Copyright IBM Corp. 1998 xvii

Figure 0-1. AS/400 Operations Navigator Display

IBM recommends that you use this new interface. It is simple to use and has greatonline information to guide you.

You can access the AS/400 Operations Navigator from the Client Access folder bydouble-clicking the AS/400 Operations Navigator icon. You can also drag this iconto your desktop for even quicker access.

While we develop this interface, you will still need to use the familiar AS/400 “greenscreens” to do some of your tasks. You can find information to help you in thisbook and online.

Prerequisite and related informationYou should be familiar with the information about performance analysis asdescribed in the Work Management book before using this book.

The menus and displays shown in this book are used by the Manager feature.Displayes used by the Agent feature may contain fewer options than those shownfor the Manager feature.

For information about Advanced 36 publications, see the Advanced 36 InformationDirectory, SC21-8292, in the AS/400 Softcopy Library.

| For information about other AS/400 publications (except Advanced 36), see either| of the following:

| � The Publications Reference, SC41-5003, in the AS/400 Softcopy Library.

| � The AS/400 online library is available on the World Wide Web at the following| uniform resource locator (URL) address:

| http://as4ððbks.rochester.ibm.com/

For a list of related publications, see the “Bibliography” on page X-1.

xviii Performance Tools V4R2

| Information available on the World Wide Web| In addition to the AS/400 online library on the World Wide Web, you can access| other information from the AS/400 Technical Studio at the following URL address:

| http://www.as4ðð.ibm.com/techstudio

| How to send your comments| Your feedback is important in helping to provide the most accurate and high-quality| information. If you have any comments about this book or any other AS/400 doc-| umentation, 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 give the form to the| local IBM branch office or IBM representative for postage-paid mailing.

| � If you prefer to send comments by FAX, use either of the following numbers:

| – United States and Canada: 1-800-937-3430

| – Other countries: 1-507-253-5192

| � If you prefer to send comments electronically, use this network ID:

| – IBMMAIL, to IBMMAIL(USIB56RZ)

| – [email protected]

| Be sure to include the following:

| � The name of the book.

| � The publication number of the book.

| � The page number or topic to which your comment applies.

About Performance Tools (SC41-5340) xix

xx Performance Tools V4R2

| Summary of Changes

| Changes to this book for Version 4 Release 2 include the following:

| � Removal of Chapter 3, Performance Tuning. This chapter was a duplicate of| Chapter 14 in the Work Management book. The Performance Tuning chapter| remains in the Work Management book.

| � Removal of the parameter descriptions for the CL commands. The syntax dia-| grams, purpose description, and examples remain in the appendix.

| � You can stop the automatic refresh function on the Work with System Activity| display by pressing a function key.

| � A brief description of the Convert Performance Thread Data (CVTPFRTHD)| command. The details are in the Work Management book.

| � The *LGLDBIO value was added to the Y axis (YAXIS) parameter on the| Create Graph Format (CRTGPHFMT) command and the Change Graph Format| (CHGGPHFMT) command. This value displays the logical I/Os for a particular| job.

| � The concept of what constitutes a job is changed with the introduction of thread| information. A job contains one or more threads, one initial thread and sec-| ondary threads. The Work with System Activity display shows thread informa-| tion.

| � Changes to Reports:

| – Thread information is reflected in many of the reports when the collections| contain thread information. Some reports add the thread identifier to the| user name column when the report shows a secondary thread. The user| name in this case is the user name portion of the qualified job name that is| running the thread. Other reports show a separate thread identifier column.

| – The line speeds for the Ethernet adapter and the token-ring adapter show| as half duplex or full duplex.

| – The line speed for asynchronous transfer mode (ATM) shows as half| duplex or full duplex.

| – The Batch Thread Analysis section of the Transaction Report was renamed| to Concurrent Batch Job Statistics.

| – Disk CPU utilization is reported under the Dsk CPU Util column.

| � Performance explorer improves the filtering capabilities for collected trace data.

| � Performance explorer provides an OUTFILE parameter on the Print Perform-| ance Explorer Report command. The OUTFILE parameter allows you to write| queries against the trace data.

| � Performance explorer provides a new report format, *BASIC. The *BASIC| Report provides summary information that includes the definition, run, and task| information sections for any of the other report types.

Copyright IBM Corp. 1998 xxi

xxii Performance Tools V4R2

| Chapter 1. Introduction to Performance Tools

| How much do you invest in managing the performance of your system? The needs| of your business change, sometimes sooner than you expect. To respond to busi-| ness changes effectively, your system must change too. Managing your system, at| first glance, might seem like just another time-consuming job. But the systems man-| agement investment pays off soon because the system runs more efficiently and| this is reflected in your business. It is efficient because changes are planned and| managed.

| Using Performance Tools helps you gain insight into the many built-in performance| management features already working for you in OS/400. These features include| dynamic tuning, expert cache, job priorities, activity levels, and pool sizes. You can| also identify ways to use these services better. You might find specific actions for| your system that the “built-in” OS/400 features do not address.

| Why Manage Performance?| Does your system perform as well as it could? If it can handle today's jobs, is that| enough? What about the future—are you prepared for growth?

| Sometimes good performance just happens. In those cases, the system has plenty| of resources to get the job done. But there will be times when those resources are| not in the right place. Maybe you have added systems and clients to the network,| or the production has increased and the workload is significantly changed. Or, more| often, workload changes in small, nearly invisible increments and one day perform-| ance just is not as good anymore. That is why you have to plan ahead for your| system to be at peak performance, especially in a quick-paced business.

| As a result, it is important to manage performance effectively for both the long term| and the short term. In the short term, understanding the performance components| of your system helps you react quickly when a performance problem occurs at a| crucial time. It may also allow you to defer upgrading for a few months. In the long| term, if you plan for a more efficient system, you prevent potential performance| problems from developing. You also ensure that you have enough capacity on the| system to handle your workloads. In addition, your users get the service they| expect. Maintaining good performance requires that you understand, plan, and| manage performance.

| Effectively managing performance really comes in the form of your own perform-| ance plan. Performance management is necessary to optimize the use of a system| and its associated services, such as the efficiency of communications lines. Per-| formance management is a strategy for planning, implementing, controlling, and| measuring computer-based tasks to achieve performance that is acceptable. But| the concept of acceptable performance is relative to where your business started| and where it is going, as well as the users and their needs.

Copyright IBM Corp. 1998 1-1

| Performance Capabilities—OS/400 and Performance Tools| Managing performance includes tasks like collecting data, monitoring, and tuning.| OS/400 provides these basic functions. Performance Tools builds on these basic| components to help you more thoroughly assess current performance needs and| plan for future capacity needs.

| OS/400 Has Performance Management Basics| Before understanding Performance Tools, you should thoroughly understand the| performance components of OS/400 and have a good understanding of work man-| agement. OS/400 can do basic collecting, monitoring, and tuning.

| For Collecting| The OS/400 performance monitor collects the data as a batch job that is run by the| operating system.

| For Monitoring| OS/400 provides three commands that display or print performance-related| information:

| � Work with Active Jobs (WRKACTJOB)

| � Work with Disk Status (WRKDSKSTS)

| � Work with System Status (WRKSYSSTS)

| For Tuning| Did you know that the system can tune itself dynamically? A system value, perform-| ance adjust (QPFRADJ), allows you to have the system tuned dynamically. Per-| formance tuning is the ability to adjust some components on the system to better| manage your workloads, manually or automatically.

| The expert cache function of OS/400 is the method of tuning to automatically adjust| the storage pool paging. Also, the QDYNPTYSCD (dynamic priority scheduling)| system value allows you to turn on and off the dynamic priority scheduler.

| Examples of adjustments include the following:

| � Changing system shared pools such as *MACHINE, *BASE, or *INTERACT

| � Changing a pool's activity level

| Performance Tools Builds on OS/400 Function| Performance Tools builds on the basic collecting, monitoring, and tuning capabilities| of OS/400. For example, you can collect performance data by using the perform-| ance monitor; then Performance Tools provides the capability of:

| � Analyzing performance data

| � Summarizing it into reports

| � Creating graphs to show trends

| � Advising how to adjust the system components to achieve better performance

| Also, although the OS/400 commands display data on a real-time basis, they are| tedious. They require repetitive use for an operator who also needs to determine

1-2 Performance Tools V4R2

| the problem areas and can only make a limited set of changes. The Work with| System Activity (WRKSYSACT) command can automatically refresh and use less| system resource than the Work with Active Jobs (WRKACTJOB) command. To| determine the causes of problems you find, you need Performance Tools to effec-| tively and quickly analyze the data.

| Finally, the tuning function you have through OS/400 is minimal in detail when com-| pared to Performance Tools. Often small adjustments can be made. However, if| you have a complex system network, the problems with performance are often not| isolated enough to solve through adjusting storage pools and activity levels. You| need a more thorough analysis of performance data to find the cause of the prob-| lems and optimize performance.

| Manager Features and Agent Features| Similar to the way that the Performance Tools product builds on the base of| OS/400, the Performance Tools Manager feature builds on the Agent feature. The| Performance Tools Manager feature is a full-function package, intended to be used| on the central site system in a distributed environment or on a single system.

| The Performance Tools Agent feature, with a subset of the Manager function, is a| lower-priced package with the more basic functions. In a distributed environment,| the Agent feature works well for managed systems in the network because the data| can be sent to the Manager if detailed analysis is required. It is also an effective| tool for sites that need a reasonable level of self-sufficiency but have no expert| skills available.

| Performance Tools Makes Performance Management Possible| Performance Tools makes this planning possible. More specifically, they are tools| that:

| � Predict performance that is based on your workloads and configurations and| models of your growth.

| � Collect, access, and work with performance data. The performance data avail-| able through these tools includes real-time graphical and character-based dis-| plays, historical data, charted graphs, interactive displays, printed reports, and| detailed trace data. The various forms make several types of analysis possible.

| � Use an expert system that assesses the situation and offers advice to optimize| performance.

| � Track system use and growth at each location by using long-term historical| graphs.

| � Identify applications and system resources that are causing problems with| system performance.

| Performance Objectives| Before you use Performance Tools, however, you must establish performance| objectives for:

| � Throughput and response time for interactive jobs

| � Throughput for batch jobs

| � Resource utilizations for the system

Chapter 1. Introduction to Performance Tools 1-3

| Figure 1-1. Performance Tools Helps You Achieve Peak Performance

| You should realize that by concentrating on one objective, you could adversely| affect another. For example, if your users want fast response time, you need to| design and operate your system so that your users receive stable response time| over a range of system loads. This choice, however, could cause batch jobs to run| slower.

| Note: Two types of response time are discussed in this guide. Internal response| time is the AS/400 system host response time. External response time is| the end-user response time and includes communications time for both| locally and remotely attached display stations.

| When response time is mentioned, unless stated otherwise, assume that it is| internal response time .

| For additional information, see “Elements of Response Time” on page B-1.


| After you set the performance objectives for interactive and batch jobs, install and| use Performance Tools. The primary functions of Performance Tools, as described| in the following sections, are related. Use each function to make the greatest use of| your system’s performance.

| A Recommended Approach for Setting an Objective| Managing performance means performing the following items to monitor your| system. Once you have collected and analyzed the data, the changes you make| should be small. If you make slight changes, you can determine the affect of each| specific change. Also, you should prioritize the changes. Continue making changes| and measuring performance until you reach your objectives.

| 1. Set performance goals

| � Set goals that match the demands of your business

| � Identify areas of the system where an improvement in performance can| make an impact on your business

| � Make the goals reasonable and ones that can be measured

| 2. Collect performance data

| � Record performance measurement daily or weekly

| – Always save performance measurement data before installing a| new software release, a major hardware upgrade, a new applica-| tion, or a large number of additional workstations or jobs .

| – Each measurement period should include "typical" medium to heavy| workloads.

| – A good starting measurement period is two hours with 15 minutes| samples. You should use separate measurement periods if there are| significantly different workloads or job types that are based on time of| day. If you are trying to solve a problem, 5-minute intervals are better| for “catching” the problem.

| � Check and analyze performance data

| – Summarize the collected data

| - Compare the data to objectives or resource guidelines.

| – Perform monthly trend analysis that includes at least the previous three| months of summarized data

| - As time progresses, include at least six months of summary data to| ensure that a trend is consistent. Make decisions based on at least| three months of trend information and your knowledge of upcoming| system demands.

| � Tune performance

| – Tune performance whenever guidelines are not met.

| – Analyze performance data to catch situations before they become prob-| lems.

| - Performance data indicates objectives that have not been met

| - Trend analysis indicates if resource consumption is increasing sig-| nificantly or performance objectives are at or past guideline values


| – Plan capacity when:

| - Trend analysis shows a significant growth in resource utilization

| - A major new application or set of additional jobs will be added to| the current hardware configuration. This could include additional| interactive workstations or new batch jobs.

| - Business plans are reviewed, and change is expected

| Performance Measurement| When you first start to use Performance Tools, use the Start Performance Tools| (STRPFRT) command to show the IBM Performance Tools menu. You should| collect performance data (by using the Start Performance Monitor (STRPFRMON)| command). When you use the Manager feature, you can produce a system report| so you have a measure of how your system currently operates. Use the Print| System Report (PRTSYSRPT) command. “Using Defaults to Print Performance| Reports” on page 7-11 describes this process. When you use the Manager feature,| you can collect performance data automatically by using either the Work with Per-| formance Collection (WRKPFRCOL) command or the job scheduling functions.

| Collecting and analyzing performance data regularly determines if you meet your| performance objectives. In this way, you accumulate a history of system perform-| ance. This history is important in managing system performance, especially if your| environment is one of growth and change. By monitoring system performance, you| may avoid excessive use of your system’s resources.

| For more information, see Chapter 3, Collecting System Performance Data.

| Capacity Planning—Manager Feature| To estimate your system resource utilization as your workload or environment| grows, use the capabilities of BEST/1** for the AS/400 system. BEST/1 is the| capacity planning tool for the AS/400 system. Following BEST/1 recommendations| will help you maintain satisfactory system performance and system resource utiliza-| tions.

| Do capacity planning before you make changes, such as adding new applications| or altering the system configuration. See the BEST/1 Capacity Planning Tool book| for more information.

| Capacity Planning—Agent Feature| The Agent feature provides the ability to create BEST/1 models from performance| data. These models can be analyzed by using the BEST/1 support in the Manager| feature.

| See the BEST/1 Capacity Planning Tool book for more information.


| Performance Analysis—Manager Feature| After you review the performance measurements, you might want to see more| detailed performance data. Use the Print System Report (PRTSYSRPT) and Print| Component Report (PRTCPTRPT) commands to help you decide if further analysis| is necessary. Chapter 7, Performance Reports—Manager Feature shows examples| of these reports.

| To provide more detail, you can also produce reports that use trace data (specify| TRACE(*ALL) on the STRPFRMON command). Use the Print Transaction Report| (PRTTNSRPT) command to help you do further analysis of performance problems| you may be experiencing.

| The advisor, that is described in Chapter 4, Advisor, analyzes collected perform-| ance data and produces conclusions and recommendations for improving system| performance. You can have the advisor put the recommendations into effect. You| can use the conclusions and recommendations to help you decide how to adjust| system tuning values.

| See Chapter 10, Performance Utilities—Manager Feature, for an explanation and| examples of other utilities you can use to analyze the performance of applications| on your system. See Chapter 5, Displaying Performance Data, for an explanation| on interactively displaying performance data.

| The performance explorer is a tool that finds the causes of performance problems| that cannot be identified by using tools that do general performance monitoring.| Chapter 11, Performance Explorer describes the performance explorer.

| “Summary of Data Collection and Report Commands—Manager Feature” on| page 3-13 provides a summary of data collection commands and reporting com-| mands.

| Performance Analysis—Agent Feature| The advisor, that is described in Chapter 4, Advisor , analyzes collected perform-| ance data and produces conclusions and recommendations for improving system| performance. You can have the advisor put the recommendations into effect. You| can use the conclusions and recommendations to help you decide how to adjust| system tuning values.

| See Chapter 5, Displaying Performance Data, for an explanation on interactively| displaying performance data.

| The performance explorer is a tool that finds the causes of performance problems| that cannot be identified by using tools that do general performance monitoring.| Chapter 11, Performance Explorer describes the performance explorer.

| See Chapter 14, Working with Historical Data—Agent Feature, for an explanation| on how to use the option to create historical data from performance data. The his-| torical data will help show the trends in your system performance.

| See Appendix E, Managing AS/400 System Performance in a Network, for an| example of automating performance data collection and analysis.


| Performance Analysis Overview| Performance analysis is a method for investigating, measuring, and correcting defi-| ciencies so that system performance meets the user’s expectations. It does not| matter much that the system is a computer; it could be an automobile or a washing| machine. The problem-solving approach is essentially the same:

| 1. Understand the symptoms of the problem.

| 2. Use tools to measure and define the problem.

| 3. Isolate the cause.

| 4. Correct the problem.

| 5. Use tools to verify the correction.

| Initially, the analyst knows that the user is not satisfied with the way the system is| working. It is running “too slow,” “too noisy,” or “too hot,” and so on. The analyst,| mechanic, or repair person must first understand what the problem really is. The| best way to find out is to observe the problem condition firsthand. Can you confirm| the user’s complaint? If you cannot, get as much information as possible from users| who have experienced the problem. Look and listen for the problem descriptions| most in common among the users.

| The key to success with any performance issue is to have a clear definition of the| users’ performance criteria. In other words, given the application mix, what do users| want from the system in terms of interactive response time, batch throughput, and| processing requirements? For example, a system that supports an interactive order| entry application may have a response time criterion to ensure that customers do| not perceive abnormal delays. Another criterion may require that end-of-day proc-| essing be completed by a specific time. With these requirements, you can establish| performance objectives around system resource utilization guidelines. With a clear| statement of goals and objectives, performance analysis can proceed on a firm| basis.

| Once you understood the objectives, it is important to assess whether the hardware| configuration is adequate to support the workload. Is there enough CPU capacity?| Is the main storage sufficient for the application mix? Answering these questions| first, perhaps through capacity modeling techniques, prevents needless effort later.

| With an understanding of the symptoms of the problem and the objectives to be| met, the analyst can formulate a hypothesis that may explain the cause of the| problem. The analyst can use certain Operating System/400 (OS/400) commands| and the Performance Tools to measure the system performance.

| Reviewing the measured data helps to further define the problem and helps to vali-| date or reject the hypothesis. Once the apparent cause or causes have been iso-| lated, a solution can be proposed. When you handle one solution at a time, you| can re-design and test programs. Again, the analyst’s tools can, in many cases,| measure the effectiveness of the solution and look for possible side-effects.

| To achieve optimum performance, one must recognize the interrelationship among| the critical system resources and attempt to balance these resources, namely CPU,| disk, main storage, and, for communications, remote lines. Each of these resources| may cause a performance degradation.


| Improvements to system performance, whether to interactive throughput, interactive| response time, batch throughput, or some combination, may take many forms, from| simply adjusting activity level or pool size to changing the application code itself. In| this instance, an activity level is a characteristic of a subsystem that specifies the| maximum number of jobs that can compete at the same time for the processing| unit.

| Ultimately, however, any improvement can come only through analysis of the crit-| ical resources (CPU, main storage, disk, and remote lines) and contention for| system and application objects.



Chapter 2. Starting Performance Tools

This chapter explains how to install and set up your Performance Tools. Informa-tion on how to use the Start Performance Tools (STRPFRT) command is also pro-vided.

Installing Performance ToolsTo install the Performance Tools product, you need a user profile with save system(*SAVSYS) authority. You can use the system operator profile to obtain thisauthority.

Performance Tools must run in a library named QPFR. If a library by this name ison your system, rename it before you install Performance Tools, using the RenameObject (RNMOBJ) command. This step will ensure the proper operation of the Per-formance Tools.

Use the following command to place the Performance Tools in library QPFR:

RSTLICPGM LICPGM(5769PT1) DEV(NAME) OPTION(\BASE)

You must then perform one of the following:

� If you have purchased the Manager feature, use the following command:

RSTLICPGM LICPGM(5769PT1) DEV(tape-device-name) OPTION(1)

� If you have purchased the Agent feature, use the following command:

RSTLICPGM LICPGM(5769PT1) DEV(NAME) OPTION(2)

If you have several tapes to install, the following situation may occur. Afterinstalling the first tape, you may receive a message saying that the licensedproduct is restored but no language objects were restored. If this occurs, load thenext tape and enter the following:

RSTLICPGM LICPGM(5769PT1) DEV(NAME) RSTOBJ(\LNG) OPTION(\BASE)

Another method for installing the Performance Tools product is to type GO LICPGMand use the menu options.

How Performance Tools Counts UsersPerformance Tools is a processor-based product. The usage type is concurrent.The product is installed with a usage limit *NOMAX.

Printer File and Output QueuesThe Performance Tools printer files have a default forms size of 8-1/2 x 11 inches,an overflow line number of 60, and a characters-per-inch setting of 10 or 15 (thissetting depends on whether the report is 80 or 132 characters wide). If the printerfile characteristics you want are different from the supplied printer file character-istics, use the Change Printer File (CHGPRTF) command to alter them. Use of thegeneric name, QP*, on this command changes all printer files in library QPFR tothe new form size.


The default output queue on the performance job description (QPFRJOBD) isQPFROUTQ. Reports, submitted as batch jobs, use this job description as thedefault. If you want to use a different output queue from the queue established byPerformance Tools, use the Change Job Description (CHGJOBD) command.Specify the output queue you want to use for the OUTQ parameter on theCHGJOBD command.

Start Performance Tools (STRPFRT) CommandUse the STRPFRT command to start Performance Tools. After you enter thecommand, the IBM Performance Tools menu for your Manager feature or Agentfeature appears. From this display, you can either choose one of the menuselections, or enter a command:

à ð PERFORM IBM Performance Tools for AS/4ðð

System: ABSYSTEM

Select one of the following:

1. Select type of status

2. Collect performance data

3. Print performance report

4. Capacity planning/modeling

5. Performance utilities

6. Configure and manage tools

7. Display performance data

8. System activity

9. Performance graphics

1ð. Advisor

7ð. Related commands

Selection or command

===>

F3=Exit F4=Prompt F9=Retrieve F12=Cancel F13=Information Assistant

F16=System main menu

á ñ

Press F3 (Exit) or F12 (Cancel) to exit the IBM Performance Tools menu.

Enter commands on the command line. Use F4 (Prompt) and F9 (Retrieve) toprompt for or retrieve commands that you enter on the command line.

To review any messages that are returned to you on the message line, position thecursor on the message line and press the Help key for additional detail. PressingF10 (Display messages in job log) from this detail display allows you to view all ofthe messages currently in the job log.

Each time you use STRPFRT, the following occurs:

� The library QPFR is added to the library list (between the system and userpositions of the library list).

� The IBM Performance Tools menu appears.

When you finish using Performance Tools, press F3 (Exit). When you do so, thelibrary QPFR is removed from the job’s library list.


Once you use the STRPFRT command to start the Performance Tools, any furtherattempt to use the command from within the operating environment for Perform-ance Tools fails. If you try to start the Performance Tools program when it isalready operating from your job, a message appears that indicates that the oper-ating environment for Performance Tools is already active. Multiple jobs may usePerformance Tools at the same time but only one performance monitor (data col-lection job) can be active at any given time.

Displaying the System or Job Status—Manager FeatureIf you choose option 1 (Select type of status) on the IBM Performance Tools menu,the Select Type of Status display appears:

à ðSelect Type of Status to Display


1. Work with system status

2. Work with subsystem

3. Work with current job

4. Work with submitted job(s)

5. Work with specified job(s)

6. Work with active jobs

7. Work with disk status

On the Select Type of Status display, you can use a set of OS/400 commands toprovide you with information about the performance of the system or a particularjob.

Each option on the Select Type of Status display has a corresponding commandassociated with it, as shown in the following list. To use a function, such as workingwith the system status, either enter option 1 on the command line of the SelectType of Status display or enter WRKSYSSTS on any command line.

Table 2-1. Type of Status Option with Corresponding Command

Type of Status Option Corresponding Command

Work with system status WRKSYSSTS

Work with subsystem WRKSBS

Work with current job WRKJOB

Work with submitted job(s) WRKSBMJOB

Work with specified job(s) WRKJOB

Work with active job(s) WRKACTJOB

Work with disk status WRKDSKSTS

Chapter 2. Starting Performance Tools 2-3


Chapter 3. Collecting System Performance Data

| The Performance Tools program uses data that is collected by the OS/400| program. OS/400 gathers data about system performance by using a batch job that| is called the performance monitor. The performance monitor tracks the activity on| the system and collects relative data. After the performance monitor collects data,| the monitor provides a set of files that contain data about the performance of the| system. In a distributed AS/400 client/server environment, this data can be col-| lected on managed (or remote, distributed) systems. You can then send the data to| the central site system where the skills and the tools exist to analyze the collected| data.

This chapter describes how to collect data using the Start Performance Monitor(STRPFRMON) command. For the Manager feature, other ways of collecting datausing Performance Tools are described in Chapter 10, PerformanceUtilities—Manager Feature, and Chapter 6, System Activity. The figures shown inthe sections following “Summary of Data Collection and ReportCommands—Manager Feature” on page 3-13 show the Performance Tools datacollection commands, and describe when you use each in analyzing the perform-ance of your system.

The STRPFRMON command is used by both the Agent feature and the Managerfeature. The STRPFRMON command is important in the overall analysis of yoursystem. Use it to collect data about resources that influence the performance ofyour system (processing unit, main storage, auxiliary storage, and communi-cations).

The STRPFRMON command is provided with the OS/400 program. The Work Man-agement book contains additional information on collecting performance data andthe database files that result and database file descriptions.

| Why Collect Performance Data| Collecting data is really the first step toward improving performance. It is a way to| capture the performance status of the system, or set of systems, involved in getting| your work done. The collection of data provides a context, or a starting point, for| any comparisons and analysis that can be done later. When you use your first data| collections, you have a benchmark for future improvements and a start on| improving your performance today. Performance problem analysis often begins| with a simple question: “What changed?” Performance data helps you answer this| question.

When to Collect Performance DataYou should collect performance data regularly to establish a record of system per-formance. If you know the performance characteristics of your system, you canjudge the effect of a change in system workload before you make the change.

Use the STRPFRMON command to collect sample data to establish this perform-ance history. With the Manager feature, use the PRTSYSRPT command to producea report from this data. The report provides an overview of the performance vari-


ables that should be tracked in the system’s history. To see an example of theSystem Report, see “System Report” on page 7-17.

With the Agent feature, use the Advisor and Work with Historical Data options toanalyze and summarize the performance data collected. See Appendix E, Man-aging AS/400 System Performance in a Network, for an example.

Collect sample data regularly, so you can make valid comparisons of information.Collect the data during similar system workloads.

| Note: The performance reports have no exact restrictions on the amount of per-| formance data that they can process. However, it is recommended that a| collection be no longer than one week in length. In fact, the optimal col-| lection strategy is to run a new collection every day.

Also collect sample data before and after major changes, such as installing a newapplication. This data provides valuable information on changes to system resourceutilizations as a result of the workload changes. When you review this data, limityour observations to the differences in the active workloads on the system. Look atthe utilizations for the processing unit, disk, main storage, and communications. Ifany of these resources is consistently overcommitted, you should determine thereason.

To determine the reason for consistent overcommitment of a given resource, collecttrace data. The performance monitor trace data provides more detailed informationon the jobs, programs, and individual transactions that run on the system. If you areusing the Manager feature, depending on the resource, you might use some of theadditional analysis tools. See Chapter 10, Performance Utilities—Manager Feature.

With the Manager feature you can use the PRTTNSRPT command, as described in“Transaction Report” on page 7-36, to specify the trace data you want to see. Youcan determine the elements of transaction response time from these reports. Inaddition, you can identify the level of resource use for the measured transactions.

For both the Manager feature and the Agent feature, the length of time you collectdata depends on whether you collect only sample data, or a combination of sampleand trace data. The length of time you collect data can generally be longer whenyou collect only sample data. When you collect sample data, you want it to reflectthe changes that occur when the various interactive and batch workloads go fromlight to moderate to heavy activity, and back to light activity again.

When you collect trace data, you may want to reduce the length of time for themeasurement, because the area where the trace data is stored is limited in size,and can contain between 40 000 and 60 000 transactions. The trace collectionends automatically when this area is filled. Thus, the length of time you collect datadepends on the activity on your system and the volume of trace records that result.However, because you collect trace data to observe the high utilization of a givenresource, you should try to collect data for workload periods that correspond tothose in which you have seen excessive utilization occur. If you trace data for alonger period of time, increase the size of the component trace table.


When to End Data CollectionUse the End Performance Monitor (ENDPFRMON) command to end the data col-lection. The collected data can automatically be transferred from the collection areainto a database file specified on the DMPTRC parameter on the ENDPFRMONcommand. The collected data can be processed by a user-written exit programspecified on the EXITPGM parameter on the ENDPFRMON command. If you arecollecting only sample data, no additional system overhead is associated with stop-ping the monitor. You can stop the monitor at any time. If you are collecting tracedata, there is additional system overhead and you should try to schedule the end ofthe measurement to coincide with a lighter workload period, or use the Dump Trace(DMPTRC) command to transfer the data at a later time. For example, schedule theperformance monitor collection to end at noon if there is a heavy workload meas-urement during the morning.

Collecting Sample or Trace Data| The performance monitor provides for the collection of sample data and trace data.

| Trace Trace data is detailed, and can be collected when detailed applications| or job analysis is required. Trace data is collected as it happens for| each transaction and results in a large amount of very detailed data that| is useful in problem analysis. When you collect trace data, it places| additional demands on your AS/400 system.

| Use the trace parameter on the STRPFRMON command to control the| collection of trace data. Trace data resides in the QAPMDMPT database| file.

| Sample Also called summary data or system data, this data is collected for| normal trend analysis and performance analysis. The data relates to the| following:

| � All jobs on the system

| � Devices attached to the system

| � Storage pools

| � Communications I/O processors

| � Disk I/O processors

| � Local workstation I/O processors

| � Workstation response times

| Sample data is collected at system, resource, job, and device levels and| on an interval basis. The default collection interval is 15 minutes, but the| interval can range from 5 - 120 minutes. This means that a performance| data record is produced for each job and resource on the system at| each interval. For example, once every 15 minutes.

You control the time between samples by using the interval parameter on theSTRPFRMON command. Sample data is collected and stored in the following data-base files:

Chapter 3. Collecting System Performance Data 3-3

Table 3-1 (Page 1 of 2). Database Files that Store Sample Data

File Type of Data

QAPMAPPN Advanced peer-to-peer networking data

QAPMASYN Asynchronous (ASYNC) data

QAPMBSC Binary synchronous communicatios (BSC) data

QAPMBUS Bus counter data

QAPMCIOP Communications controller data

QAPMCONF System configuration data

QAPMDBMON 1 Monitoring data

QAPMDDI Distributed data interface (DDI) data

QAPMDIOP Storage device controller data

QAPMDISK Direct access storage device (DASD) data

| QAPMECL| Token-ring LAN protocol data for asynchronous transfer mode (ATM) ports that| support token-ring LAN emulation and for token-ring ports.

| QAPMETH| Ethernet statistics data for asynchronous transfer mode (ATM) ports that| support Ethernet LAN emulation and for Ethernet ports

QAPMFRLY Frame relay data

QAPMHDLC High-level data link control (HCLC) data

QAPMHDWR Hardware configuration data

QAPMIDLC ISDN data link control (IDLC) B-channel data

QAPMIOPD Communications processor performance data

QAPMJOBS Job data

QAPMLAPD ISDN D-Channel statistics data

QAPMLIOP Local workstation controller (WSC) data

| QAPMMIOP| Multifunction controller data. This file includes processing time for token-ring| and Ethernet LAN emulation.

QAPMPOOL Main storage data

QAPMRESP Local workstation response time data

QAPMRWS Remote workstation response time data

| QAPMSAP| Service access point (SAP) data for token-ring, Ethernet, DDI, and frame relay| ports. The file also reports data for asynchronous transfer mode ports that| support token-ring and Ethernet LAN emulation.

QAPMSBSD Subsystem description

QAPMSNA SNA performance measurements data

QAPMSNADS SNA distribution services (SNADS) data

QAPMSTND DDI station counter data

| QAPMSTNE| Ethernet link station data for asynchronous transfer mode ports that support| Ethernet LAN emulation and for Ethernet ports

| QAPMSTNL| Token-ring LAN link station data for asynchronous transfer mode ports that| support token-ring LAN emulation and for token-ring ports

QAPMSTNY Frame relay station counter data

QAPMSYS System data


Table 3-1 (Page 2 of 2). Database Files that Store Sample Data

File Type of Data

QAPMTSK Task related performance data

QAPMX25 X.25 data

Note:

1 QAPMDBMON is an optional file that is created or updated when the start database monitorparameter (STRDBMON) is *YES on the STRPFRMON command.

Whenever you use the STRPFRMON command, you collect sample data, but youcan also collect trace data. You generally choose to collect trace data to gain addi-tional detailed information about specific jobs and transactions. By collecting tracedata, you can often gain insight into other problems involving job contention,program resource use, transaction delays, and so on.

The Manager feature allows you to use the Print System Report (PRTSYSRPT)and Print Component Report (PRTCPTRPT) commands to print the sample datayou collect. To review examples of these reports, see “System Report” onpage 7-17 and “Component Report” on page 7-25.

With the Manager feature, you can use the Print Transaction Report(PRTTNSRPT), the Print Lock Report (PRTLCKRPT), and the Print Trace Report(PRTTRCRPT) commands to see the data collected through trace. Refer to “Trans-action Report” on page 7-36 and to “Lock Report” on page 7-63 to review the infor-mation provided from trace data collection.

For the Manager feature, some of the commands described in Chapter 10, Per-formance Utilities—Manager Feature , make use of trace data collected using theSTRPFRMON command. See “Summary of Data Collection and ReportCommands—Manager Feature” on page 3-13 for more information on the com-mands that use the trace data.

For the Agent feature, you will need to use the Performance Tools Manager featureto analyze trace data. See Appendix D, Comparison of Performance Tools , formore information.

For the Manager feature, the Performance Tools program has additional functionsto analyze performance data, including printing of performance reports and perform-ance utilities. See Appendix D, Comparison of Performance Tools, for more infor-mation.

Note: You may receive unpredictable results using Performance Tools if the per-formance monitor is running and a Performance Tools CL command isusing the same member that is collected at that time.

To free up disk space used to save performance data you no longer need, you canuse the Delete Performance Data (DLTPFRDTA) command.

The remaining sections in this chapter describe when and how you collect datausing the STRPFRMON command.

To collect sample or trace data, follow these steps:


1. Enter the Start Performance Tools (STRPFRT) command on any command lineto show the IBM Performance Tools menu.


System: ABSYSTEM









8. System activity


1ð. Advisor



===>



(C) COPYRIGHT IBM CORP.

á ñ

2. Choose the Collect performance data option on the IBM Performance Toolsmenu, and press the Enter key. The Collect Performance Data display appears.

à ðCollect Performance Data RCHASRðD

ð5/26/95ð7:ð7:27

Performance monitor status:

Status . . . . . . . . . . . . : Not running


1. Start collecting data

2. Stop collecting data

3. Work with performance collection

Note: Only one performance monitor function can be active in the system. Thecurrent status of the performance monitor is shown.

3. Choose the Start collecting data option, and press the Enter key. The StartCollecting Data display appears.


à ðStart Collecting Data


1. Collect data with defaults

2. Collect data with menus

3. Collect data with command

On this display, there are three ways to start the performance monitor to collectdata. Any option you choose results in the collection of performance data usingSTRPFRMON. Options 1 and 2 are designed for a new user of PerformanceTools (they provide more guidance in starting the performance monitor). Theseoptions are discussed in the following sections. If you choose option 3 (Collectdata with command), a prompt for the STRPFRMON command appears asthough you entered the command and pressed F4 (Prompt).

Using System Defaults to Collect DataIf you choose option 1 (Collect data with defaults) on the Start Collecting Datadisplay, the Collect Data with Defaults display appears.

à ðCollect Data with Defaults

Type choices, press Enter.

Member . . . . . . . . \GEN Name

Library . . . . . . QPFRDATA Name

Text . . . . . . . . .

Time duration:

Hours . . . . . . . 2 ð-999

Minutes . . . . . . ð ð-6ð

1. Type the name of the member and library where you want to store the perform-ance data. *GEN creates a member name based on the date and time. Thedefault for Library is QPFRDATA.

2. Type a description for the sample data in the Text field.

3. Enter the length of time you want to collect performance data in the Time dura-tion field.

4. Press the Enter key, and the data collection process begins. The defaults forthe other STRPFRMON command parameters are used.

See the CL Reference for more information about the STRPFRMON commandparameters.


Using Menus to Collect DataYou can change the defaults for the STRPFRMON command by entering thecommand directly, or by selecting option 2 (Collect data with menus) on the StartCollecting Data display.

If you choose option 2, the Collect Data with Menus display appears.

à ðCollect Data with Menus


Member . . . . . . . . \GEN Name

Library . . . . . . QPFRDATA Name

Text . . . . . . . . .

1. Type the member and library name where you want to store the performancedata. The default for Library is QPFRDATA.

2. Enter a description of the performance data in the Text field, if appropriate.

3. Press the Enter key. The Collect Additional Data display appears.

à ðCollect Additional Data

Type options, press Enter.

1=Collect

Option Type of Data

Trace data

1 Communication data

4. To indicate that you want to collect trace data, type a 1 in the Option columnnext to Trace Data, and press the Enter key.

Notes:

a. When this trace starts, all existing traces stop. Only one trace can be activein the operating system.

b. The Agent feature does not analyze or report on trace data. To analyze orreport on trace data that is collected by the Agent feature, the data must besent to a system that has the Manager feature installed.

5. To indicate that you want to collect performance data for communications linesand objects, type a 1 in the Option column next to Communications Data, andpress the Enter key.

The Set Data Collection Time display appears.


à ðSet Data Collection Time


Number of minutes between

collections . . . . . . 15 5-6ð (increments of 5)

End time option . . . . . 1 1=Elapsed time

2=Time of day

3=No maximum

6. Type how often data should be collected in the Number of minutes betweencollections field. Fifteen minutes is usually an adequate sample interval forproblem analysis. This is the sample rate for sample data collection.

7. Type when you want data collection to stop in the End time option field. If youchoose option 1 (Elapsed time), go to step 9. If you choose option 2 (Time ofday) for this prompt, the Set End Time display appears.

à ðSet End Time


Number of days from today . . . . . . . . . . ð ð-9

Time of day . . . . . . . . . . . . . . . . . ðð:ðð:ðð HH:MM:SS

8. Indicate the number of days you want to collect data in the Number of daysfrom today field. Also indicate when you want data collection to stop in theTime of day field.

9. If you choose option 1 (Elapsed time) for the End time option prompt on theCollect Additional Data display, the Set Length of Time to Collect Data displayappears.

à ðSet Length of Time to Collect Data


Length of time to collect data:

Hours . . . . . . . . . 2 ð-999

Minutes . . . . . . . . ð ð-6ð

10. Type the length of time you want to collect data in the Length of time to collectdata fields.

After you press the Enter key, the data collection process begins.

For information on how to print various sample and trace data reports using theManager feature, refer to Chapter 7, Performance Reports—Manager Feature.


Using the STRPFRMON Command to Collect Trace DataIf you choose option 3 (Collect data with command) on the Start Collecting Datadisplay, the Start Performance Monitor (STRPFRMON) display is shown.

à ðStart Performance Monitor (STRPFRMON)


Member . . . . . . . . . . . . . \GEN Name, \GEN

Library . . . . . . . . . . . . > QPFRDATA Name

Text 'description' . . . . . . . \SAME

Time interval (in minutes) . . . 15 5, 1ð, 15, 2ð, 25, 3ð, 35...

Stops data collection . . . . . \ELAPSED \ELAPSED, \TIME, \NOMAX

Days from current day . . . . . ð ð-9

Hour . . . . . . . . . . . . . . 2 ð-999

Minutes . . . . . . . . . . . . ð ð-99

Data type . . . . . . . . . . . \ALL \ALL, \SYS

Select jobs. . . . . . . . . . . \ALL \ALL, \ACTIVE

Trace type . . . . . . . . . . . \NONE \NONE, \ALL

Dump the trace . . . . . . . . . \YES \YES, \NO

Job trace interval . . . . . . . .5 .5 - 9.9 seconds

Job types . . . . . . . . . . . \DFT \NONE, \DFT, \ASJ, \BCH...

+ for more values

More...

F3=Exit F4=Prompt F5=Refresh F12=Cancel F13=How to use this disp

F24=More keys

á ñ

Attention

You need to be aware that only one trace can be active in the operatingsystem. If *ALL is specified on the TRACE parameter while another trace isrunning, the other trace is canceled and its data collection is lost.

The parameters that you should consider are:

� Trace type (TRACE)

Specifies that all of the internal traces that contain performance related informa-tion are started. If another trace is running at the same time this commandspecifying TRACE(*ALL) is issued, the other trace is canceled.

� Dump the trace (DMPTRC)

Specifies whether or not the trace is dumped when the data collection ends. Ifyou choose to dump the trace at a later time, you can use the Dump Trace(DMPTRC) command. Use DMPTRC(*NO) with caution. Do not wait too long todump the trace after the monitor has ended. Object addresses in the trace dataresolve to names when DMPTRC is called. Any objects that are deletedbetween the time the trace data is collected and the time the trace data isdumped will not resolve. You will see addresses (which are not useful) insteadof names.

Using DMPTRC(*NO) is illustrated in the following example:

1. On Monday at 8 am, Person A specifies the following:


STRPFRMON TRACE(\ALL)

MBR(one)

DMPTRC(\NO)

2. On Monday at 2 pm, Person A ends the performance monitor (ENDPFRMON).

3. On Monday at 3 pm, Person B specifies the following:

STRPFRMON TRACE(\ALL)

MBR(two)

Note: When Person B starts to run another trace, the trace data for memberone is destroyed.

4. On Monday at 4 pm, Person B ends the performance monitor (ENDPFRMON).

5. On Monday at 10 pm, Person A dumps the trace data.

DMPTRC MBR(one)

Based on this example, the trace data in MBR(one) will actually be the same as thetrace data in MBR(two). The trace data for MBR(one) will not correspond with thesample data from MBR(one). For example, PRTSYSRPT(one) andPRTTNSRPT(one) will contain conflicting information.

Collecting Performance Data AutomaticallyNote: If you are using automatic data collection for the first time, refer to “Perform-

ance Collection Setup” on page 3-13 before you begin.

You can choose to have your system automatically collect performance data on aweekly schedule. Automatic performance collection allows you to select specificdays of the week on which automatic data collection is to occur using the OS/400performance monitor.

On the IBM Performance Tools menu, choose the Collect performance data

option and press the Enter key. The Collect Performance Data display appears.


à ðCollect Performance Data ABSYSTEM

11/ð7/95 ð8:ð7:27

Performance monitor status:

Status . . . . . . . . . . . . : Not running






===> 3

F3=Exit F4=Prompt F5=Refresh F9=Retrieve F12=Cancel

á ñ

Choose option 3 (Work with performance collection) and press the Enter key. TheWork with Performance Collection display appears. (You can also use theWRKPFRCOL command to access the Work with Performance Collection display.)

à ðWork with Performance Collection


1=Add 2=Change 3=Hold 4=Remove 5=Display 6=Release

Performance

Opt Collection Status Description

_ __________

_ A RLS

_ Fð9ðð RLS

_ Sð9ðð RLS

Bottom

F3=Exit F5=Refresh F12=Cancel

á ñ

A list of the existing performance collections is displayed. The Performance Col-lection column specifies the details about when to collect performance data auto-matically.


To add a new collection, type a 1 (Add) in the Opt column and press the Enter key.The Add Performance Collection (ADDPFRCOL) display appears. (You can alsouse the ADDPFRCOL command to access the Add Performance Collection(ADDPFRCOL) display.)

Performance Collection SetupAutomatic performance collection requires a batch job (QPFRCOL) that queries theschedule created by the Add Performance Collection function and submits the StartPerformance Monitor (STRPFRMON) command at the appropriate times. This jobexists as an autostart job entry in the IBM-supplied subsystems QBASE and QCTL.The Work Management book contains more information about autostart job entries.

When the job QPFRCOL is started and there are no performance collectionsdefined that are in a released status, the job ends. Therefore, anytime you add acollection and there are no existing performance collections in a released status,start the performance collection as follows:

STRPFRCOL JOBQ(QSYS/QCTL)

You can type this command on any command line. Performance data is collecteduntil all the performance collections are removed or held, or until you enterENDPFRCOL. You need to start performance collection again if you add performancecollections later.

Summary of Data Collection and Report Commands—Manager FeatureTable 3-2 through Table 3-5 in the following sections present the commands forvarious levels of data collection. These figures also show the related report com-mands, show the type of data collected, provide a summary of the information con-tained in the reports, and describe when you might use these commands.

Refer to the figures indicated for information on the following data collection levels:

� System ( Table 3-2)

� Job ( Table 3-3 on page 3-16)

� File use and structure ( Table 3-4 on page 3-16)

� Application ( Table 3-5 on page 3-17)

If you use the Performance Tools menus and displays to collect data and producereports, these figures may help you understand, at a glance, the capabilities of Per-formance Tools. If you bypass the menus and displays by entering commands onthe available command entry lines, these figures may serve as a reference for theavailable commands.

System-Level Analysis—Manager FeatureSystem-level data collection and analysis provides you with a comprehensive viewof how the system operates. This information ranges from a system operationaloverview to an analysis of individual transactions. System-level data collection andanalysis also provides you with system modeling functions for capacity planningand performance prediction.

Use system-level data to identify what additional collection and analysis should bedone.


A summary of system data collection and report commands is shown in Table 3-2on page 3-14.

Table 3-2 (Page 1 of 2). System Data Collection (STRPFRMON Command) and Report Commands

Level of DataType ofData

ReportCommand

Information Shown onthe Reports

When to Use theCommand

Job DiskSystem

Sample data ANZPFRDTA Contention analysis andrecommendations

Processing trendsSystem modelWorkload projectionHardware growth Processing unit Main storage Disk

Job DiskSystem

Sample data PRTSYSRPTPRTCPTRPT

Workload Utili- zation Processing unit Disk Main storage CommunicationsModel parametersExternal response times

Processing trendsSystem modelWorkload projectionHardware growth Processing unit Main storage Disk

System JobProgram

Trace data PRTTNSRPT Workload Utili- zation Processing unitExceptional waitsTransaction detailTop ten reportsObject contentionConcurrent batch jobsSystem model parametersTransaction summary and detail

Workload projectionHardware growthPool configurationOvercommitmentApplication designFile contentionTransaction Significance ClassificationProgram useSystem modelProcessing trends

System JobProgram FilesDisk

Trace data PRTTRCRPT Resources usedExceptionsState transitions

Progression of batch jobstraced through time

Job ProgramFiles Disk

Sample data STRBEST System performance projectionsCapacity planningConfiguration planning

Before installingWhen growth is anticipated, either in hardware or workloadWhen a new application is to be installedPerformance analysis


Table 3-2 (Page 2 of 2). System Data Collection (STRPFRMON Command) and Report Commands

Level of DataType ofData

ReportCommand

Information Shown onthe Reports



Trace data PRTLCKRPT File, record, or object contention by: Object name Holding or requesting job Time

To reduce or remove object contentionProblem analysis


Sample data PRTJOBRPT Utilization Processing unit Disk CommunicationsWorkload

Problem analysis


Sample data PRTPOLRPT Utilization Main StorageWorkload Subsystem

Problem analysis


Sample data PRTRSCRPT Utilization I/O Processing unit DiskExternal response times

Problem analysis

Application orProgram

Statis- ticsProfileTrace

PRTPEXRPT Program and procedure statistics on calls, CPU usage and I/OSampling of CPU usage of program and procedure instructionsDetailed record of performance related events as they occurred

When general performance monitoring cannot find problemsProblem analysis

For more information on the report commands shown in this figure, see Chapter 7,Performance Reports—Manager Feature. The Start BEST/1 (STRBEST) commandis described in the BEST/1 Capacity Planning Tool book. The PRTLCKRPTcommand is described in “Lock Report” on page 7-63.

Job Trace Analysis—Manager FeatureJob trace analysis enhances the operating system’s standard trace job reports andprovides a summary of job operation and transaction processing. The primary usefor job trace analysis is to determine application flow. You can determine what partsof a job use the most resources, and measure the effect of program changes rela-tive to previous trace data. Do not use job trace analysis to determine accurate jobor transaction processing times.


A summary of job trace data collection and report commands is shown in Table 3-3on page 3-16.

For more information about the data collection or report commands, seeChapter 10, Performance Utilities—Manager Feature.

Table 3-3. Job Trace Data Collection (STRJOBTRC Command) and Report Commands

Level of Data Type of Data Report CommandInformation Shown onthe Reports


Job ProgramFiles

Trace data PRTJOBTRCENDJOBTRC

Program name Control flow I/O operations Full/shared opens Exceptions Message handling

Disk I/O summary

For program devel-opmentTo identify jobs orprograms thatperform poorly

File Use and Database Structure Analysis—Manager FeatureThe commands shown in Table 3-4 provide an overview of the program file useand the database file structure of an application.

The following contain information for analyzing file use database structure:

� “Analyze Program (ANZPGM) Command” on page 10-9

� “Analyze Database File (ANZDBF) Command” on page 10-11

� “Analyze Database File Keys (ANZDBFKEY) Command” on page 10-13

Table 3-4. File Use and Structure Data Report Commands

Level of Data Report CommandInformation Shown onthe Reports


Program File use structure ANZPGM Program file For application use anal-ysis

Program File use structure ANZDBF Physical file structure For application analysis

Program File use structure ANZDBFKEY Logical file structure For file analysis

Job AnalysisJob analysis provides you with a view of the operational environment for all jobs, ora group of jobs, in the system at a given time. Use the information from a specificprocess analysis to improve the performance of the process. This analysis can helpyou improve the program environment to reduce the number of the following:

� Open files

� File buffer and work space sizes

� File open placement in a program

� Active programs

A summary of job data collection and report commands is shown in Table 3-5 onpage 3-17.


For more information about the DSPACCGRP command, see “Display AccessGroup (DSPACCGRP) Command” on page 10-16.

Table 3-5. Process Data Collection (DSPACCGRP Command) and Report Commands

Level of Data Report CommandInformation Shown onthe Reports


Job Program Files DSPACCGRPANZACCGRP

File useFiles used at thesame timeOpen Data Path Buffer size Formats (size

and number) I/O counts Duplicates PAG size Active programs

Reduce program sizeReduce number ofopen files

Reduce processaccess group (PAG)I/ODetermine group jobcandidates



Chapter 4. Advisor

The advisor provides an easy-to-use way to improve many of the performancecharacteristics of your system.

The advisor fits into the set of Performance Tools between automatic system tuningand the more specialized tools provided in Performance Tools (such as the StartBest/1 (STRBEST) command) and the reports (such as a Print System Report).Appendix D, Comparison of Performance Tools, provides more information aboutthe functions provided in Performance Tools.

Automatic system tuning is a useful method for maintaining the basic conditions forgood performance. If it is set to work at each IPL, it resets the basic tuning valuesto the recommended settings for the system configuration and controlling sub-system. Dynamic automatic system tuning adjusts only pool sizes and activity levelsof shared pools based on system activity as measured at user-specified intervals.To adjust the system, the tuner uses a guideline that is calculated based on thenumber of jobs.

The advisor can help you to define specific tuning values and other parts of a proc-essing environment to provide better performance for specific processing conditionson your system.

The advisor analyzes performance data you collect with the performance monitorand it can produce recommendations and conclusions to help improve perform-ance. The advisor might recommend changes to basic system tuning values, andmight list conclusions about conditions that could cause performance problems.

You can choose to have the advisor change system tuning values as it recom-mends, or you can decide to make only the changes you select. You can use theadvisor’s conclusions to make changes to your system, to guide further perform-ance data collection, or to help you request performance reports containing moreinformation and explanations.

The advisor can help you to improve system performance, but it will not identify orcorrect all performance problems. The performance information analyzed includes:

� Storage pool sizes

� Activity levels

� Disk and CPU utilization

� Communications utilizations and error rates

� Input/output processor utilization

� Unusual job activities—exceptions or excessive use of system resources

� Interactive trace data (when available) (Manager feature)

The advisor does not:

� Make any recommendations for changing specific application programs toimprove their performance

� Analyze noninteractive trace data


The advisor is a good first tool to use to improve system performance. In manyinstances, it will be the only tool required to make the improvements you need. Thischapter takes you through the process for using the advisor. In general, thisprocess consists of the following steps:

1. Identify when the performance problems occur.

2. Use the performance monitor to collect data during the time periods when eachproblem seems to occur.

3. Request the advisor to analyze the data.

4. Use the advisor’s output to change system tuning values, to guide further datacollection, or to request other more detailed performance reports.

5. Observe the effects of any tuning changes, and decide if another cycle throughthis process is required to further improve performance or to eliminateunwanted side effects.

Notes:

1. The examples in this chapter show how to use the advisor, but they do notcontain specific solutions for any performance problems that might exist on aparticular AS/400 system.

2. Sometimes an analysis of data collected during normal system operation canhelp in selecting the advisor recommendations to implement to solve perform-ance problems occurring at other times.

3. At times the advisor will suggest additional analysis using tools available only inthe Manager feature.

4. When the advisor makes no significant recommendations or conclusions andthe system's performance remains unacceptable, analysis at the applicationlevel is required. In this case, the advisor has ruled out many tuning, communi-cations, and disk problems.

5. When making recommendations, the advisor takes into consideration someguidelines and threshold values from the BEST/1 hardware table.

Collecting the Right Performance DataBefore collecting performance data, you should clearly describe the problem to beinvestigated. From system users’ comments or your own experience, you can beginto formulate a description of the problem. The problem description does not need tobe overly detailed or technical, just try to simply describe one problem. Forexample:

� Interactive (or batch) processing seems too slow.

� File updating should go faster.

� At times the entire system seems to be sluggish.

Next, determine when the problem is most likely to occur. Maybe interactive work isslow first thing in the morning. Perhaps batch processing seems slow late in theafternoon.

When you can clearly describe the problem and have determined when it seems tooccur, you are ready to collect performance data to be analyzed by the advisor.


If possible, focus on collecting data for one problem at a time. Of course, try tocollect the data when the problem seems to occur most often. You can decide laterhow much of the data you want the advisor to analyze. For more information aboutwhen to collect performance data and how much to collect, see the first few pagesof Chapter 3, Collecting System Performance Data.

The performance monitor is used to collect performance data. It can be run usingthe default data collection values. Information about how to use the performancemonitor is in Chapter 3, Collecting System Performance Data.

Requesting an AnalysisAfter performance data is collected for the time periods near when a problemseems to occur, you request the advisor to analyze all or part of that data.

To start the advisor, you can select the Advisor option on the IBM PerformanceTools menu, or type the Analyze Performance Data (ANZPFRDTA) command onany command line.

Note: To analyze performance data from a library other than QPFRDATA whenusing the ANZPFRDTA command, type the command and press F4(Prompt) to change the library name.


System: ABSYSTEM









8. System activity


1ð. Advisor



===> 1ð



(C) COPYRIGHT IBM CORP.

á ñ

The next two steps in requesting a performance data analysis are:

� Select the member containing the performance data to analyze.

� Select the time intervals of data to analyze.

Chapter 4. Advisor 4-3

Selecting a MemberWhen the Advisor option is selected, or the ANZPFRDTA command is run, theSelect Member for Analysis display appears.

à ðSelect Member for Analysis

Library . . . . QPFRDATA

Type option, press Enter.

1=Select 5=Display

Option Member Text Date Time

Q95ð221115 11/ð1/98 22:ð1:ð7

Q983611411 12/27/98 14:11:25

Q98346ð7ð8 12/12/98 ð7:ð8:43

Q9834116ð4 12/ð7/98 16:ð4:23

Q98341142ð 12/ð7/98 14:2ð:22

Q983411411 12/ð7/98 14:11:ð9

BOTTOM

F3=Exit F12=Cancel F15=Sort by name F16=Sort by text

F19=Sort by date/time

(C) COPYRIGHT IBM CORP. 1981, 1998.

á ñ

To request an analysis, select only one member that contains performance datacollected during a time when the problem occurred. When you select a memberand press the Enter key, a Select Time Intervals to Analyze display appears.

Notes:

1. When you return to the Select Member for Analysis display, the 1 typed for themember remains. This is a reminder that you may want to display this member.

2. When the monitor is running and using one of the members shown in theSelect Member for Analysis display, this member may appear with blank Dateand Time fields until the first interval is collected.

Selecting Time Intervals


à ðSelect Time Intervals to Analyze

Member . . . . . . . : Q95ð221115 Library . . . . . . : QPFRDATA


1=Select

Transaction --CPU Util--- --High--- -Pool Fault- Excp

Opt Date Time Count Rsp Tot Int Bch Dsk Unit Mch Usr ID Util

11/ð5 15:29 1ð41 3.1 24 15 6 14 ððð5 2 31 ð4 1

11/ð5 15:59 1ð9ð .2 8 4 2 4 ðð15 ð 6 ð2 ð

11/ð5 16:28 1ð34 .3 7 4 2 5 ððð8 ð 9 ð2 ð

11/ð5 16:58 1412 .3 12 6 4 6 ððð7 ð 11 ð2 ð

11/ð5 17:28 842 .5 1ð 5 3 6 ððð5 ð 8 ð2 ð

11/ð5 17:58 457 .4 6 2 2 3 ððð1 ð 4 ð2 ð

11/ð5 18:28 221 .2 3 1 ð 2 ðð12 ð 1 ð2 ð

11/ð5 18:58 286 .2 4 1 1 2 ððð2 ð 2 ð2 ð

11/ð5 19:28 145 .3 3 1 1 2 ððð7 ð 3 ð2 ð

11/ð5 19:58 1 1.ð ð ð ð 1 ððð1 ð 1 ð2 ð

11/ð5 2ð:28 ð .ð ð ð ð 1 ððð1 ð ð ð2 ð

More...

F3=Exit F5=Refresh F11=Display histogram F12=Cancel F13=Select all

F14=Deselect all

á ñ

The Select Time Intervals to Analyze display lists all the time intervals of perform-ance data collected in the library member selected on the Select Member for Anal-ysis display. To analyze a different member, press F12 (Cancel) to return to theSelect Member for Analysis display.

The columns on the Select Time Intervals to Analyze display can help you focusthe analysis on time intervals when the suspected performance problem seems tohave occurred. If there are no obvious reasons to select only some of the displayedtime intervals, you can select them all for analysis by pressing F13 (Select all).

When one or more time intervals are selected for analysis, press the Enter key torequest the analysis by the advisor.

| Note: The Transaction Count field does not include the number of DDM I/Os that| were generated. Use the Display Performance Data (DSPPFRDTA)| command to display the value for the logical database I/O for DDM jobs.

Using a HistogramSometimes a graph of the data for one of the performance values in the datamakes it easier to select specific time intervals of data for analysis. To define anddisplay a graph (called a histogram ), press F11 (Display histogram) on the SelectTime Intervals to Analyze display. The display then changes to include the SelectHistogram window.



............................................

: Select Histogram : ary . . . . . . : QPFRDATA

: :

: Type option, press Enter. :

: 1=Select :

: :

: Opt View : --High--- -Pool Fault- Excp

: Transaction count : Dsk Unit Mch Usr ID Util

: Transaction response time : 22 ðð19 3 13 ð4 6

: Total CPU utilization : 27 ðð26 2 9 ð4 7

: 1 Interactive CPU utilization : 29 ðð19 1 11 ð5 7

: Batch CPU utilization : 21 ðð12 1 13 ð4 7

: High disk utilization : 22 ðð16 2 14 ð4 6

: More... : 17 ðð16 2 9 ð7 5

: F3=Exit F12=Cancel : 18 ððð9 1 14 ð5 3

: : 15 ðð26 1 13 ð4 4

:..........................................: 21 ðð19 2 14 ð7 5

11/ð1 12:ð6 389 1.ð 96 25 63 19 ðð19 1 13 ð7 11

11/ð1 12:11 281 1.3 93 16 68 23 ðð19 3 18 ð7 5

More...


F14=Deselect all

á ñ

The View column lists the performance values that can be selected to define the Y(vertical) histogram axis. The X (horizontal) histogram axis always shows the timeintervals contained in the member.

As an example, to make it easier to see the time intervals where CPU utilization isthe highest, you could select one of the CPU utilization views. A sample histogramfor Interactive CPU Utilization follows:

à ðSelect Time Intervals from Histogram

Type a '1' under each interval to select, press Enter.

Interactive CPU utilization

48 :

44 :

4ð :\ \

36 :\ \

32 :\ \ \ \

28 :\ \ \\ \\ \

24 :\\ \ \ \\\ \\\ \

2ð :\\\\\ \ \ \\\\ \\\ \

16 :\\\\\\ \\\\\\\\\ \\\\\\

12 :\\\\\\\\\\\\\\\\\\\\\\\

8 :\\\\\\\\\\\\\\\\\\\\\\\

4 :\\\\\\\\\\\\\\\\\\\\\\\

ð :\\\\\\\\\\\\\\\\\\\\\\\

11111111111111111111111

+-------+-------+-------+-------+-------+-------+-------+-------+

11:21 12:ð1 12:41


F14=Deselect all

á ñ

On this example, it is easy to see and select the time intervals of greatest interac-tive processing unit use. The number 1 is entered to select each time interval to be


analyzed. All of the intervals can be quickly selected by pressing F13 (Select all),as shown in the example.

After the Enter key is pressed on the Select Time Intervals to Analyze display or onthe Select Time Intervals from Histogram display, the advisor analyzes the perform-ance data for the selected time intervals.

Notes:

1. An analysis of large amounts of performance data can take a long time andcould affect system performance for other users.

2. The analysis performed by the advisor includes all of the types of performancedata for the selected time intervals, and is not limited to the type of dataselected to create the histogram.

Analyzing Trace DataThe advisor can analyze interactive transactions when the performance monitor isrun with the option TRACE *ALL for the selected member. The file QTRTSUM,produced from the *FILE option of the Transaction report, is analyzed. If the filedoes not already exist, the advisor creates QTRTSUM using the default options.Otherwise, the existing QTRTSUM file is processed.

The command CHGJOBTYP can be run to change the job type of noninteractivejobs to interactive. After the job types have been changed, the *FILE option of theTransaction report can be run so that the advisor analyzes the jobs listed as inter-active.

The performance information analyzed from trace data includes:

� Exceptions by job

� Transactions with long seize/lock wait times

� Unusual transaction activities—excessive wait times

The default is analyzing trace data when it is available. To avoid analyzing tracedata, use the ANZPFRDTA command, press F4 (Prompt), and press F10 (Addi-tional parameters) to change the value of the DATATYPE parameter to *SAMPLE.

Note: Caution should be used when analyzing an existing QTRTSUM file. The filemay not include time intervals that match the intervals that were picked forthe advisor to analyze.

Using the Advisor’s ResultsDepending on the content of the selected performance data, the advisor canproduce recommendations, conclusions, and interval conclusions. What these areand how you can use them are explained as you look at the following examples.

When a performance data analysis has completed, the Display Recommendationsdisplay shows the results.


à ð Display Recommendations

System: ABSYSTEM


System . . . . . . . : ABSYSTEM Version/Release . . : 4/ 2.ð

Start date . . . . . : 11/17/98 Model . . . . . . . : ðð -ð142

Start time . . . . . : ð8:44:ð7 Serial number . . . : 1ð-11AðD

QPFRADJ . . . . . . : ð QDYNPTYSCD . . . . . : 1


5=Display details

Option Recommendations and conclusions Recommendations

Decrease pool size for listed pools.

5 Increase pool size for listed pools.

Decrease activity level in listed pools.

Add more main storage.

ASP space capacity exceeded guideline of 8ð.ð%.

Conclusions

Pool fault rates exceeded guideline.

Pool fault rates below guideline.

SDLC utilizations exceeded 5ð% guideline.

More...

F3=Exit F6=Print F9=Tune system F12=Cancel F21=Command line

á ñ

Understanding RecommendationsThe Recommendations section of this display deals with conditions that significantlyaffect system performance. The recommendations result from comparing thesystem values and conditions in the analyzed performance data to the basicAS/400 performance guidelines.

The recommendations suggest changes to the basic system tuning values that canimprove performance. They also list problems that can be solved by other actions.In this example, the recommendations about changing pool sizes can be carried outby changing system tuning values. But, the recommendation about ASP (auxiliarystorage pool) space capacity might require redefining the use of system disk spaceor adding to system disk capacity. You might need technical assistance to completethis type of recommendation. Auxiliary storage pool can be one or more storageunits defined from the disk units or disk unit subsystems that make up auxiliarystorage. ASPs provide a means of isolating certain objects on specific disk units toprevent the loss of data due to disk media failures on other disk units.

To see more details about a recommendation, type 5 in the Option column. As anexample, the following displays show the details for the example recommendationIncrease pool size for listed pools.


à ðDisplay Detailed Recommendation

Recommendation:

Increase pool size for listed pools.

Detailed recommendation:

PFR2567

Technical description . . . . . . . . : The following table shows the

pool identifier, the current pool size, and the suggested pool size.

Pool From To Pool From To

1 1ð238 12193

Increasing the pool size will reduce the page fault rate which will

More...

Press Enter to continue.

F3=Exit F12=Cancel

á ñ

In this example only pool 1 should be increased in size. The text beginning at thebottom of this display and continuing on the following displays discusses the effectsof changing a pool’s size.

à ðDisplay Detailed Recommendation

Recommendation:


Detailed recommendation:

improve the response time and throughput of jobs in this pool.

Decreasing the pool size will free storage that may in turn be given to

pools with high fault rates.

Removing a pool will free storage that may in turn be given to pools with

high fault rates.

A pool will be increased by at least ten percent of its current size.

Pools that are decreased will all be decreased by the same percentage,

with ten percent of the current size as the maximum amount of decrease.

For example, if a 15ððK pool needs storage, and a 2ðððK and 1ðððK pool can

More...


F3=Exit F12=Cancel

á ñ

Many recommendations include this type of information to help you choose the rightchanges to make to your system.


Changing System Tuning ValuesTo see and select the tuning changes related to the recommendations, press F9(Tune system) on the Display Recommendations display. A display similar to thefollowing appears:

à ðSelect Tuning Recommendations

Advisor Current Data

Name/ Recommended System Collection

Value To Be Changed Number Value Value Value

POOLSIZE (K) \MACHINE 12193 942ð 11ð85

ACTIVITY LEVEL \BASE 6 7 6

POOLSIZE (K) \INTERACT 7ð755 39683 7ð755

ACTIVITY LEVEL \INTERACT 27 21 31

POOLSIZE (K) \SPOOL 8ð 49 8ð

ACTIVITY LEVEL \SPOOL 3 2 3

Bottom


1. Tune to advisor’s recommendations

2. Restore system to data collection values

Selection

F3=Exit F12=Cancel

á ñ

On this Select Tuning Recommendations display you have several choices:

� Select menu option 1 (Tune to advisor’s recommendations) to have the advisormake all the changes shown in the Advisor Recommended Value column.Usually this is a good choice to make when starting to solve a performanceproblem.

� Leave the values as they are listed in the Current System Value column.

� Select menu option 2 (Restore system to data collection values) to have theadvisor set the values as they were when the analyzed performance data wascollected (shown in the Data Collection Value column).

� Write down the tuning values that fit your needs, and use the appropriatesystem commands to change the values individually.

Notes:

1. The analysis and recommendations are based on the Data Collection Values.The Current System Value column is there for your reference and in case youwant to reset your configuration to what it was at the time of data collection. Ifthe Advisor Recommended Value equals the Data Collection Value, then theadvisor is saying that this is an adequate setting for the workload analyzed. Ifthe Advisor Recommended Value does not equal the Data Collection Value,then you will see recommendations and conclusions as to what should bechanged.

2. When the dynamic tuning support is active (the system value is 2 or 3), thestorage pool sizes and activity levels are automatically changed. Because ofthis automatic change, the advisor is unable to process the tuning request.


Understanding ConclusionsThe Conclusions section of the Display Recommendations display lists conditionsthat could have affected performance when the analyzed data was collected. Theseconditions can include thresholds reached, save and restore activities, transmissionline errors, and so on.


System: ABSYSTEM



Start date . . . . . : ð5/17/98 Model . . . . . . . : ðð -ð142




5=Display details

Option Recommendations and conclusions Recommendations

Decrease pool size for listed pools.


Decrease activity level in listed pools.

Add more main storage.

ASP space capacity exceeded guideline of 8ð.ð%.

Conclusions

5 Pool fault rates exceeded guideline.

Pool fault rates below guideline.

SDLC utilizations exceeded 5ð% guideline.

More...


á ñ

Some conclusions describe conditions that caused the advisor to make particularrecommendations. Other conclusions not related to recommendations can be usedas guides for collecting more performance data, or for adjusting the system.

To see more details about a conclusion, type 5 in the Option column. The followingexample is the display showing details for the conclusion Pool fault rates exceededguideline that supports the recommendation to increase the size of pool 1.


à ðDisplay Detailed Conclusion

Conclusion:

Pool fault rates exceeded guideline.

Detailed conclusion:

PFR2513


pool identifier, the maximum fault rate over all the intervals, the fault

rate guideline, the number of intervals the guideline was exceeded out of

1 intervals, and the date and time the maximum fault rate occurred. For

pool 2 (\BASE) the guideline is based on the fact that there are no user

jobs running in \BASE.

ID Rate Guide Intervals Date Time

1 3.6 3.ð 3 11/ð1/98 12:31:ð4

More...


F3=Exit F12=Cancel

á ñ

In this example, the guideline of 3 faults was exceeded for pool 1 in three of theanalyzed time intervals. The maximum fault rate was 3.6.

Understanding Interval ConclusionsThe Interval Conclusions section of the Display Recommendations display containsthe detailed data to support the conclusions for the analyzed time intervals.


System: ABSYSTEM



Start date . . . . . : ð5/17/98 Model . . . . . . . : ðð -ð142




5=Display details

Option Recommendations and conclusions Interval Conclusions

5 Pool fault rates above guideline.

Total disk I/O was 225. (179 Reads and 46 Writes)

No performance problems found on listed TRLAN lines.

Total system fault rate above 5ð.ð guideline.

Thrashing may have occurred.

Bottom


á ñ

To see more details about an interval conclusion, type 5 in the Option column. Thefollowing example is the display showing details for the sample interval conclusion,


Pool fault rates above guideline, which supports the conclusion that pool fault ratesexceeded the guideline.

à ðDisplay Detailed Interval Conclusion

Interval conclusion:

Pool fault rates above guideline.

Detailed interval conclusion:

PFR2553


pool identifier, the fault rate, and the time the fault rate exceeded the

guideline.

Id Rate Guide Date Time

1 3.ð 3.ð 11/ð1/98 11:21:13

1 3.1 3.ð 11/ð1/98 12:11:ð6

1 3.6 3.ð 11/ð1/98 12:31:ð4

Bottom


F3=Exit F12=Cancel

á ñ

In this example we see exactly when, and by how much, the fault rate guidelinewas exceeded for pool 1 in the analyzed time intervals.

Following is the details display for another type of sample interval conclusion, Totaldisk I/O was 225:

à ðDisplay Detailed Interval Conclusion

Interval conclusion:

Total disk I/O was 225. (179 Reads and 46 Writes)

Detailed interval conclusion:

PFR2847

Cause . . . . . : This is the sum of all the disk I/O for all the

selected intervals for all the disk devices. This does not indicate a

problem; this data is provided simply for reference.

Bottom


F3=Exit F12=Cancel

á ñ


An interval conclusion like this one provides information but does not support aconclusion or recommendation. It does not report a problem but provides informa-tion that can be helpful in understanding how your system is performing.

Tune System by Advisor’s RecommendationsAfter you request a performance analysis, and look over the results, often the nextstep is to have the advisor tune the system as it recommends. Do this by selectingmenu option 1 (Tune to advisor’s recommendations) on the Select Tuning Recom-mendations display.

Next, observe the effects of the changes. Use the performance monitor to collectmore performance data during the next time period when you expect the problem tooccur. Also, observe the system and watch for the usual symptoms of the problem.Ask users who experienced the problem if they still notice it. Watch for any pos-sible unwanted side effects from the tuning changes. These can occur if thechanges are not fully compatible with some of your processing requirements, or ifseveral problems are being worked on.

The first attempt to solve a basic performance problem can be successful. Butsometimes the steps described in this chapter must be repeated until the best pos-sible performance is achieved for your system and your processing requirements.

The original problem may continue or new problems may occur. The advisor mighthave no further recommendations or conclusions that you can use. At this time youcould use other performance reports and commands to work on the problem. Theseare described in Work Management.

Sometimes tuning alone will not solve performance problems. To handle theintended work load, a system might need additional main storage, disk storage, orprocessing speed. BEST/1 can be used to determine if system processing capaci-ties should be increased. For more information about BEST/1 and capacity plan-ning, see the BEST/1 Capacity Planning Tool book.


Chapter 5. Displaying Performance Data

This chapter describes how to interactively view the performance data collected bythe Start Performance Monitor (STRPFRMON) command. This Display Perform-ance Data function can be used either while the performance monitor is active orafter the collection is completed.

Note: The data collection does not need to contain the trace data in order to usethis display function. Trace data may be required, however, to furtheranalyze performance problems isolated by this function.

Display Performance DataTo interactively display sample performance data, you can do one of the following:

� Type the Display Performance Data (DSPPFRDTA) command on anycommand line using the default value of *SELECT for the member parameter.

� Type the DSPPFRDTA command on any command line specifying a memberfor the MBR parameter.

Note: If you specify a member on the DSPPFRDTA command, you do not seethe Select Performance Member display or the Select Time Intervals toDisplay display. The Display Performance Data function starts to readthe performance database files.

� If you are using the Manager feature, select the Display performance data

option on the IBM Performance Tools menu.

� If you are using the Agent feature, select the Advisor option on the IBM Per-formance Tools menu. Then select option 5 from the next menu.

à ðSelect Performance Member

Library . . . . QPFRDATA


1=Select


_ Q983221324 11/17/98 13:24:ð6

_ Q9831ð1458 11/ð5/98 14:58:2ð

_ Q983ð81ðð9 11/ð3/98 1ð:ð9:13

_ Q983ð7ð759 11/ð2/98 ð7:59:25

Bottom

F3=Exit F12=Cancel F15=Sort by name F16=Sort by text



á ñ

The member name, a text description, and the date and time you collected eachset of performance data appear on this display. If you cannot find the data you


want to display, use the Roll keys to page through the list of members or use theappropriate function key to sort the sets of performance data. You can sort the databy member name, text description, or by the date and time the member wascreated. When you find the performance data you want to display, for the Managerfeature type a 1, or for the Agent feature type a 5, in the corresponding Option field.

Note: When the monitor is running and using one of the members shown in theSelect Performance Member display, this member may appear with blankDate and Time fields until the first interval is collected.

If you are searching for a member located in a library that is different from the onecurrently listed in the Library field at the top of the display, type a new library namein the field and press the Enter key. A list of the performance members available inthe library you specified appears. You can then select to display one of them.

After you select a performance member to display, the Select Time Intervals toDisplay display appears.

à ðSelect Time Intervals to Display

Member . . . . . . . : Q983221324 Library . . . . . . : QPFRDATA


1=Select

Transaction --CPU Util--- --High--- -Pool Fault- Excp

Opt Date Time Count Rsp Tot Int Bch Dsk Unit Mch Usr ID Util

11/17 13:39 427 2.2 1ð 4 4 4 ððð1 ð 6 ð2 1

11/17 13:54 441 .9 12 7 3 6 ððð5 ð 6 ð2 ð

11/17 14:ð9 16ð .6 6 3 2 4 ððð5 ð 6 ð2 ð

11/17 14:24 189 .5 5 2 1 4 ððð5 ð 6 ð2 ð

11/17 14:39 328 .5 8 3 3 6 ððð5 1 8 ð2 ð

11/17 14:54 167 .5 5 1 3 4 ððð5 ð 5 ð2 ð

11/17 15:ð9 282 .6 8 3 3 4 ðð1ð ð 5 ð2 ð

11/17 15:19 167 .3 7 3 2 5 ððð5 ð 6 ð2 ð

Bottom


F14=Deselect all

á ñ

Select the time interval for which you want to display performance data.

The Display Performance Data function then starts to read the performance data-base files. All the performance information required by this function is processednow, so there is reasonable response time when moving between displays later.

Note: The initial processing may cause a noticeable delay in presenting the firstdisplay.

After all the data is processed, the main display for the Display Performance Datafunction appears.


à ðDisplay Performance Data

Member . . . . . . . . Q983221324 F4 for list

Library . . . . . . QPFRDATA

Elapsed time . . . . : ðð:54:16 Version . . . . . . : 4

System . . . . . . . : MACHINE1 Release . . . . . . : 2.ð

Start date . . . . . : 11/17/98 Model . . . . . . . : 2ðð-2ð51

Start time . . . . . : 13:24:ð6 Serial number . . . : 1ð-1288312


CPU utilization (priority) . . . . . . . . . . . : 42.ð1

CPU utilization (other) . . . . . . . . . . . . : 34.92

Job count . . . . . . . . . . . . . . . . . . . : 539

Transaction count . . . . . . . . . . . . . . . : 1ð836

Transactions per hour . . . . . . . . . . . . . : 1198ð

Average response (seconds) . . . . . . . . . . . : 1.74

Disk utilization (percent) . . . . . . . . . . . : 5.24

Disk I/O per second . . . . . . . . . . . . . . : 138.9

Logical DB I/Os for DDM jobs . . . . . . . . . . : 52.ð

F3=Exit F4=Prompt F5=Refresh F6=Display all jobs F1ð=Command entry

F12=Cancel F24=More keys

á ñ

On this display you can change both the Member and Library fields. If you type anew member name in the Member field and press the Enter key, the data in thatmember appears on the display. If you type a new library name in the Library fieldand press the Enter key, the program tries to locate the member in the specifiedlibrary. If you press F4 (Prompt) after you enter the library name, the Select Per-formance Member display uses the specified library to present a list of data col-lections.

The Display Performance Data function helps you analyze the performance data. Ithighlights the values on this display that exceed the threshold values.

Therefore, if the interactive CPU utilization or the disk utilization exceeds thethreshold, the field is highlighted on the display.

To access a command line after you start the Display Performance Data function,press F10 (Command entry). This allows you to work from a command entrydisplay without exiting the display function. Once you exit the command entry, youare immediately returned to the Display Performance Data display without having toexperience the initial processing delay.

To better understand system performance, you might want to view the data sortedby category. The second set of function keys on this display allows you to groupthe performance data by subsystem, job type, or interval.

�

�

�

F13=Display by subsystem F14=Display by job type F15=Display by interval

F24=More keys

á ñ

Chapter 5. Displaying Performance Data 5-3

By categorizing the data, you might be able to isolate a group of jobs that requirefurther analysis. If you do, you can then display the performance statistics for indi-vidual jobs.

The next sections describe the displays that show the performance data separatedinto the subsystem, job type, and interval categories.

Display Performance Data by SubsystemIf you press F13 on the Display Performance Data display, the Display by Sub-system display appears.

à ðDisplay by Subsystem

Member . . . . . . . : Q983221324 Elapsed time . . . . : ðð:54:16

Library . . . . . : QPFRDATA

Type options, press Enter. Press F6 to display all jobs.

5=Display jobs

CPU Job Tns Average Disk

Option Subsystem Util Count Count Response I/O

_ \MACHINE 9.86 13ð ð .ðð 42933

_ QBASE .ðð 1 ð .ðð 29

_ QBATCH 17.99 32 ð .ðð 23337

_ QCTL 2.35 3 295 .71 1ð937

_ QINTER 4ð.28 355 1ð221 1.77 79822

_ QSNADS .ðð ð ð .ðð ð

_ QSPL 5.33 145 ð .ðð 22639

Bottom

F3=Exit F6=Display all jobs F12=Cancel F14=Display by job type

F15=Display by interval

á ñ

This display categorizes the performance data according to the subsystem in whichthe activity occurred.

From this display you may be able to isolate a single subsystem or group of sub-systems that are of particular interest. To view the performance data for the jobs inparticular subsystems, type a 5 in the appropriate Option fields and press the Enterkey. If you do not want to select a particular subsystem, but would rather view thedata for all the jobs in the measurement, press F6 (Display all jobs).

Display Performance Data by Job TypeIf you press F14 on the Display Performance Data display, the Display by Job Typedisplay appears.


à ðDisplay by Job Type




5=Display jobs


Option Job Type Util Count Count Response I/O

_ Autostart .ðð ð ð .ðð ð

_ Batch 19.65 69 ð .ðð 33769

_ Evoke .ðð ð ð .ðð ð

_ Interactive 4ð.94 354 1ð5ð2 1.74 81815

_ LIC 9.66 127 ð .ðð 42347

_ Pass-Through .ð8 3 14 2.42 195

_ Sbs Monitor .97 4 ð .ðð 2984

_ System .2ð 3 ð .ðð 586

_ Writer 4.32 1ð7 ð .ðð 18ðð1

Bottom

F3=Exit F6=Display all jobs F12=Cancel F13=Display by subsystem

F15=Display by interval

á ñ

This display categorizes the performance data according to the job types of thejobs running on your system.

From this display you may be able to isolate a single job type or group of job typesthat are of particular interest. To view the performance data for the jobs of partic-ular job types, type a 5 in the appropriate Option fields and press the Enter key. Ifyou do not want to select a particular job type, but would rather view the data for allthe jobs in the measurement, press F6 (Display all jobs).

Display Performance Data by IntervalIf you press F15 on the Display Performance Data display, the Display by Intervaldisplay appears.


à ðDisplay by Interval




5=Display jobs


Option Date Time Util Count Count Response I/O

_ ð9/19/98 14:ð1:48 71.35 212 957 1.7ð 12644

_ ð9/19/98 14:ð6:47 82.68 22ð 982 1.87 12893

_ ð9/19/98 14:11:47 87.27 229 955 1.96 14717

_ ð9/19/98 14:16:46 63.ð5 236 921 1.83 11693

_ ð9/19/98 14:21:46 55.34 2ð7 823 2.11 9715

_ ð9/19/98 14:26:45 54.79 2ð4 885 2.54 9585

_ ð9/19/98 14:31:45 49.17 2ð9 8ð6 1.37 9787

_ ð9/19/98 14:36:44 58.54 215 1ð21 1.31 11ð73

_ ð9/19/98 14:41:45 71.72 241 12ð7 1.56 151ð3

_ ð9/19/98 14:46:44 71.ð4 222 1ð89 1.6ð 15ð18

More...


F14=Display by job type

á ñ

This display categorizes the performance data according to the collection intervalsthat occurred during the measurement.

From this display, you may be able to isolate a single interval or group of intervalsthat are of particular interest. To view the performance data for the jobs in particularintervals, type a 5 in the appropriate Option fields and press the Enter key. If youdo not want to select a particular interval, but would rather view the data for all thejobs in the measurement, press F6 (Display all jobs).

Display JobsIf you selected a subsystem on the Display by Subsystem display, selected a jobtype on the Display by Job Type display, selected an interval on the Display byInterval display, or pressed F6 (Display all jobs) on any of these or the DisplayPerformance Data display, the Display Jobs display appears.


à ð Display Jobs

Subsystem . . . . : QINTER Member . . . . . : Q983221324

Elapsed time . . : ðð:54:16 Library . . . . : QPFRDATA


5=Display job detail

Job CPU Tns Avg Disk

Option Job User Number Type Util Count Rsp I/O

_ DSPð1 QSECOFR ð2222ð INT 1.15 2ð2 1.2 941

_ DSP1ðð QPGMR ð22213 INT .7ð 155 1.4 694

_ DSP89 QPGMR ð22219 INT .64 75 3.6 674

_ DSPð2 QSYSOPR ð22222 INT .63 127 2.2 956

_ DSP47 QPGMR ð2221ð INT .62 164 1.1 888

_ DSPð9 QSECOFR ð22215 INT .59 129 1.2 661

_ DSP57 QPGMR ð22223 INT .56 151 2.ð 625

_ DSP38 QPGMR ð22217 INT .56 52 2.7 2177

_ DSP92 QPGMR ð222ð7 INT .55 163 2.3 7ð6

_ DSPð3 QSYSOPR ð22168 INT .52 96 1.8 1235

More...

F3=Exit F12=Cancel F15=Sort by job F16=Sort by job type

F19=Sort by CPU F24=More keys

á ñ

This display appears when you request to view the jobs in a particular subsystem.If you request a job type or interval, the Subsystem indicator at the top of thedisplay is replaced by a Job Type or a Interval indicator. Also, if you selected aparticular job type, the Job Type column does not appear because all the jobs havethe same type as indicated by the Job Type field at the top of the display. If yourequest to see all the jobs (by pressing F6 on the Display by Subsystem, theDisplay by Job Type, or the Display by Interval displays) the appropriate indicator(Subsystem, Job Type, or Interval) appears at the top of the display showing avalue of ‘*ALL’ and the Job Type column is present. If F6 is pressed from theDisplay Performance Data display, there is no indicator, such as subsystem, jobtype, or interval, at the top of the display. Also, in this case, the Job Type columnwould be present.

Display Job DetailIf you type a 5 in the Option field next to a job on either the Display Jobs display orthe Display Remote Jobs display (see page 5-12), and press the Enter key, theDisplay Job Detail display appears.


à ðDisplay Job Detail

Job . . . . . . . . : DSPð1 Job type . . . . . . : INT

User . . . . . . . : QSECOFR Subsystem . . . . . : QINTER

Number . . . . . . : ð2222ð Pool . . . . . . . . : ð4

Member . . . . . . . : Q983221324 Priority . . . . . . : 2ð

Library . . . . . : QPFRDATA Elapsed time . . . . : ðð:54:16

CPU Tns Average Disk Act-> Wait-> Act->

Interval Seconds Count Response I/O Wait Inel Inel

14:ð1:48 .ððð ð .ð ð .ð .ð .ð

14:ð6:47 .ððð ð .ð ð .ð .ð .ð

14:11:47 .883 2 3.ð 293 .8 .ð .ð

14:16:46 4.93ð 18 2.8 138 3.6 .ð .ð

14:21:46 12.935 43 1.7 116 8.6 .ð .ð

14:26:45 1.938 25 .4 67 5.ð .ð .ð

14:31:45 .693 1ð .5 28 2.ð .ð .ð

More...


F3=Exit F11=View 2 F12=Cancel F15=Sort by interval

F24=More keys

á ñ

The Display Job Detail display provides you with the performance data for a partic-ular job, broken down by collection intervals. This display presents the performanceinformation using three different views, which can be accessed by function keys.F11 shows you the next view in the series.

Display Performance Data for System ResourcesWhen you are on the Display Performance Data display, you may want to view theperformance data specifically related to storage pools, disk units, or communi-cations lines, instead of the job-related information previously discussed. The thirdset of function keys, as shown below, allows you to do this.

�

�

�

F19=Display pool detail F2ð=Display disk detail

F21=Display communications detail F24=More keys

á ñ

Display Pool DetailIf you press F19 on the Display Performance Data display, the Display Pool Detaildisplay appears.


à ðDisplay Pool Detail




5=Display pool intervals

Size Act Tns Avg Expert

Opt Pool (K) Lvl Count Rsp Cache

_ ð1 22528 ð ð .ð ð

_ ð2 4ð96 32767 449 3.2 ð

_ ð3 3ð72 5ð ð .ð ð

_ ð4 6ð416 72 1ð387 1.6 ð

_ ð5 8192 3ð ð .ð ð

Bottom

F3=Exit F11=Display faults and pages F12=Cancel F15=Sort by pool

F24=More keys

á ñ

The Display Pool Detail display presents performance information for each pool inthe measurement. Two views are used in order to present all the pool information.

Although the Display Pool Detail display presents the pool information as totals forthe entire measurement, you may want to examine the data for a particular poolover time. Using the Display pool intervals option allows you to view the same poolinformation broken down into the time intervals in which it occurred.

Display Pool IntervalBy typing a 5 in the Option field next to a pool and pressing the Enter key, theDisplay Pool Interval display appears with performance information for that pool.


à ðDisplay Pool Interval

Pool . . . . . . . . : ð4 Member . . . . . . . : Q983221324

Elapsed time . . . . : ðð:54:16 Library . . . . . : QPFRDATA

Size Act Tns Avg DB DB Non-DB Non-DB

Interval (K) Lvl Count Rsp Faults Pages Faults Pages

14:ð1:48 6ð416 72 895 1.7 2.7 135.ð 12.7 56.8

14:ð6:47 6ð416 72 915 1.9 2.2 176.3 13.ð 52.7

14:11:47 6ð416 72 936 1.9 2.4 119.9 14.7 6ð.7

14:16:46 6ð416 72 886 1.8 2.1 167.7 14.8 76.6

14:21:46 6ð416 72 811 2.1 2.6 237.6 13.2 54.5

14:26:45 6ð416 72 861 1.4 2.ð 1ð5.3 13.8 93.6

14:31:45 6ð416 72 794 1.3 2.1 125.2 12.7 53.6

14:36:44 6ð416 72 942 1.3 2.1 154.ð 13.6 54.ð

14:41:45 6ð416 72 1146 1.5 2.7 159.5 16.4 69.4

14:46:44 6ð416 72 1ð77 1.6 2.5 157.5 16.ð 64.7

14:51:44 6ð416 72 1124 1.4 2.8 136.2 15.6 2ð9.2

Bottom


F3=Exit F11=Display transitions F12=Cancel F15=Sort by interval

F24=More keys

á ñ

The Display Pool Interval display presents the same columns of information as theDisplay Pool Detail display, except that the data is broken down by time intervals. Asecond view (not shown here) also exists for the Display Pool Interval display,which presents the data for the state transitions.

Display Disk DetailIf you press F20 on the Display Performance Data display, the Display Disk Detaildisplay appears.

à ðDisplay Disk Detail




5=Display disk intervals

----Activity Per Second-----

Unit Size ASP % % Read Read Write Write

Opt Unit Name (M) ID Used Busy Rqs (K) Rqs (K)

_ ððð1 DDðð1 427 ð1 6ð.7 6.5 1.ð 2.3 1.8 1.6

_ ððð2 DDðð2 427 ð1 6ð.8 5.5 .8 2.2 1.7 1.1

_ ððð3 DDðð3 427 ð2 68.5 .5 .ð .ð .2 .3

_ ððð4 DDðð4 427 ð2 68.5 .4 .ð .ð .2 .2

_ ððð5 DDðð5 427 ð1 6ð.8 6.8 1.2 4.6 1.8 1.3

_ ððð6 DDðð6 427 ð1 6ð.8 6.9 1.3 4.4 1.7 1.2

_ ððð7 DDðð7 427 ð1 6ð.8 6.8 1.2 4.ð 1.9 1.4

_ ððð8 DDðð8 427 ð2 68.5 .5 .ð .ð .2 .3

_ ððð9 DDðð9 427 ð1 6ð.8 7.4 1.2 4.1 2.ð 1.5

More...

F3=Exit F11=View 2 F12=Cancel F15=Sort by unit F22=Sort by % used

F23=Sort by % busy

á ñ


The Display Disk Detail display presents performance information for each disk unitattached to the system on which the data collection was performed.

Although the Display Disk Detail display presents the disk information as totals forthe entire measurement, you may want to examine the data for a particular diskunit over time. Using the Display disk intervals option allows you to view the samedisk information broken down into the time intervals in which it occurred.

Display Disk IntervalBy typing a 5 in the Option field next to a disk unit and pressing the Enter key, theDisplay Disk Interval display appears with performance information for that diskunit.

à ðDisplay Disk Interval

Unit . . . . . . . . : ððð1 Member . . . . . . . : Q983221324

Size (M) . . . . . . : 427 Library . . . . . : QPFRDATA

Unit name . . . . . : DDðð1 Elapsed time . . . : ðð:54:16

-------Activity Per Second-------

ASP % % Read Read Write Write

Interval ID Used Busy Rqs (K) Rqs (K)

14:ð1:48 ð1 6ð.6 7.8 1.4 2.6 2.1 1.8

14:ð6:47 ð1 6ð.6 5.7 .8 1.4 1.5 1.3

14:11:47 ð1 6ð.6 4.7 .7 1.8 1.9 1.3

14:16:46 ð1 6ð.6 4.5 .9 2.7 1.2 .9

14:21:46 ð1 6ð.6 5.3 .7 1.6 1.4 1.1

14:26:45 ð1 6ð.7 4.ð .8 1.7 .7 .7

14:31:45 ð1 6ð.7 5.1 .9 2.ð 1.4 1.3

14:36:44 ð1 6ð.7 5.3 .7 2.ð 1.6 1.8

14:41:44 ð1 6ð.7 12.8 1.5 4.2 3.3 3.1

More...


F3=Exit F12=Cancel F15=Sort by interval F22=Sort by % used

F23=Sort by % busy

á ñ

The Display Disk Interval display presents the same columns of information as theDisplay Disk Detail display, except that the data is broken down by time intervals.

Note: The Size (M) field is at the top of the display because the size of the diskunit cannot change from one interval to the next.

Display Communications Line DetailIf you press F21 on the Display Performance Data display, the Display Communi-cations Line Detail display appears.

Note: The data in the following figures are examples only and should not be usedto tune any system.


à ðDisplay Communications Line Detail




5=Display remote jobs 7=Display communications interval data

Line Line Line Tns Average Job %

Option ID Type Speed Count Response Count Busy

_ BSC41 BSC 2.4 ð .ðð ð .ð

_ BSC2ð BSC 2.4 ð .ðð ð .ð

_ SDLCLINEA1 SDLC 9.6 13ð1 1.8ð 56 52.ð

_ SDLC1ðð SDLC 9.6 1ð47 1.22 71 3ð.6

_ SDLCB SDLC 9.6 558 1.16 28 2ð.3

_ SDLCLINEð2 SDLC 9.6 1168 2.85 45 44.8

_ SDLCLINEð3 SDLC 9.6 1ð24 1.34 34 3ð.3

_ SDLC15ðð SDLC 9.6 1556 1.74 45 58.7

_ SDLC1ððð SDLC 9.6 1317 2.35 96 5ð.4

Bottom

F3=Exit F12=Cancel F15=Sort by line ID F2ð=Sort by transactions

F24=More keys

á ñ

Figure 5-1. Display Communications Line Detail

The Display Communications Line Detail display presents performance informationfor each communications line attached to the system.

The Display Communications Line Detail display presents the totals for each line inthe measurement. One of the options on this display lets you view performancedata for the jobs using a communications line. The other option displays the timeinterval performance data for a communications line.

Display Remote JobsIf you type a 5 (Display remote jobs) on the Display Communications Line Detaildisplay in the Option field next to a communications line and press the Enter key,the Display Remote Jobs display appears with the performance information for thatline listed by job.


à ðDisplay Remote Jobs

Line . . . . . . . . : SDLCLINEA1 Member . . . . . . . : Q983221324

Line type . . . . . : SDLC Library . . . . . : QPFRDATA

Line speed . . . . . : 9.6 Elapsed time . . . . : ðð:54:16





_ DSP92 QPGMR ð222ð7 INT .55 163 2.3 7ð6

_ DSP79 QPGMR ð22191 INT .52 71 2.6 734

_ DSP13 QPGMR ð22ð75 INT .5ð 1ð4 2.2 776

_ DSP41 QSECOFR ð22123 INT .36 1ð8 1.6 7ð4

_ DSP63 QPGMR ð222ð3 INT .31 46 2.2 785

_ DSP85 QSECOFR ð22193 INT .26 58 2.3 527

_ DSPð8 QSYSOPR ð2212ð INT .21 53 2.1 397

_ DSP54 QPGMR ð22175 INT .2ð 51 1.7 275

_ DSP5ð QPGMR ð22172 INT .17 41 1.9 261

More...



á ñ

Figure 5-2. Display Remote Jobs

If you type a 5 in the Option column, you can display more detailed information forthe remote job. This option calls the Display Job Detail display, just as option 5 didfrom the Display Jobs display. Refer to “Display Job Detail” on page 5-7 for infor-mation on the performance data that will be shown.

Display Communications Interval DataTo see a display of performance data for a communications line by time interval,type a 7 (Display communications interval data) in the Option field next to the com-munications line on the Display Communications Line Detail display, and press theEnter key. The resulting Display Communications Interval Data display lists the per-formance averages and totals for that communications line for the time intervals inthe current performance data member.

From the Display Communications Interval Data display you can request data aboutthe jobs using the communications line during any of the listed time intervals. To dothis, type a 5 in the Option column by the selected time interval.

Each communications protocol has its own type of Display Communications IntervalData display, but all are quite similar. An example and description for synchronousdata link control (SDLC) is shown in Figure 5-3 on page 5-14. Other communi-cations protocols are:

� X.25

� Token-ring LAN area network (TRLAN)

� Ethernet local area network (ELAN)

� Distributed data interface (DDI)

� Frame relay (FRLY)

� Binary synchronous communications (BSC)


� Asynchronous data link control (ASYNC)

Note: Option 7 (Display communications interval data) is not valid for IDLC lines.To view ISDN and IDLC line information, press F13 (Display network inter-face data).

à ðDisplay Communications Interval Data

Line ID . . . . . . . . : MPLSCHI Member . . . . . . . . . : MONDAY

Line type . . . . . . . : SDLC Library . . . . . . . : QPFRDATA

Line speed . . . . . . . : 19.2 Elapsed time . . . . . . : ðð:24:5ð

IOP name . . . . . . . . : CMBð1

Type options, press Enter,

5=Display remote jobs

Pct Pct

I Frames Frames

Itv Line I Frames Trnsmitd Frames Recd

Option End Util Trnsmitd in Error Recd in Error

13:ð8:ðð 78 1,818 ð9 1,818 ð2

13:23:ðð 78 1,818 ð7 1,818 ðð

13:38:ðð 78 1,818 ðð 1,818 ðð

13:53:ðð 78 1,818 ðð 1,818 ðð

14:ð8:ðð 78 1,818 ðð 1,818 ðð

Bottom

F3=Exit F11=View 2 F12=Cancel F15=Sort by itv end

F2ð=Sort by line util F24=More keys

á ñ

Figure 5-3. Display Communications Interval Data for SDLC

Display Remote Interval JobsThis display lists information about the jobs using a communications line during atime interval. To request it, type a 5 (Display remote jobs) in the Option column bya time interval on a Display Communications Interval Data display, and press theEnter key. The following display appears:


à ðDisplay Interval Remote Jobs

Interval . . . . . . . . : 13:ð8 Member . . . . . . . . . : MONDAY

Line ID . . . . . . . . : MPLSCHI Library . . . . . . . : QPFRDATA

Line type . . . . . . . : SDLC Elapsed time . . . . . . : ðð:24:5ð

Line speed . . . . . . . : 19.2

Line utilization . . . . : 78%


Job User Number Type Util Count Rsp I/O

DSP15 Xð7733 ð3ð191 DDM .16 19 .ð 23ð

DSP4ð SMITH ð3ð275 INT .24 24ð 3.5 1598

DSP43 U5531 ð3ð212 DDM .ðð ð .ð 76

Bottom



á ñ

The end time for the selected time interval, the line name, line type, line speed, andaverage use during the time interval are shown in the fields Interval, Line ID, Linetype, Line speed and Line utilization at the top of this display. The columndescriptions are the same as for Figure 5-2 on page 5-13.

Display Network Interface DataTo see a display of performance data for Integrated Services Digital Network(ISDN) network interfaces, press F13 (Display network interface data) on theDisplay Communications Line Detail display.

Note: F13 is shown only if your data collection contains ISDN data.

This display shows performance information for each ISDN network interface andchannel pair configured on the system that data was collected for. From thisdisplay, you can view the data on a per-interval basis by typing a 7 by the networkinterface and channel you want to see.

More information regarding ISDN can be found in the ISDN Support book.


à ðDisplay Network Interface Data

Member . . . . . . . : ISDN1 Elapsed time . . . . : ð1:54:39

Library . . . . . : V4R2CT


7=Display channel interval data

Transmit/ Percent Percent

Receive/ Total Frames Total Frames

Network Average Frames Trnsmitd Frames Received

Option Interface Channel Line Util Trnsmitd Again Received in Error

ISDNSS_A B1 ð1/ð1/ð1 8778 ð 88ð2 ð

ISDNSS_B B1 13/17/15 85ð6 7 9859 9

ISDNSS_A B2 ðð/ðð/ðð 3758 ð 3779 ð

ISDNSS_B B2 ðð/ðð/ðð 3779 ð 3736 ð

ISDNSS_A D 11/15/13 1318 4ð 143ð 38

ISDNSS_B D ðð/ðð/ðð 994 ð 993 ð

Bottom

F3=Exit F12=Cancel F15=Sort by network interface F16=Sort by channel


á ñ

Figure 5-4. Display Network Interface Data

Display Channel Interval DataTo see a display of performance data for a specific ISDN network interface andchannel by time interval, type a 7 (Display channel interval data) in the Option fieldnext to the network interface on the Display Network Interface Data display andpress the Enter key. The resulting Display Channel Interval Data display lists theperformance averages and totals for that network interface and channel for the timeintervals in the current performance data member.

Each channel type has its own type of Display Channel Interval Data display. Anexample and description of this display for each channel type follow.


à ðDisplay Channel Interval Data

Network Interface . : ISDNSS_B Member . . . . . . . : ISDN1

Channel . . . . . . : B1 Library . . . . . : QPFRDATA

Line speed . . . . . : 64.ð Elapsed time . . . . : ð1:54:39

IOP name . . . . . . : CMBð1


5=Display remote jobs

Transmit/ Percent Percent

Receive/ Total Frames Total Frames

Itv Line Average Frames Trnsmitd Frames Received

Opt End ID Line Util Trnsmitd Again Received in Error

14:33:11 ISDNSS_B1 99/99/99 347 33 13ð 39

14:36:22 ISDNSS_B1 99/99/99 35 1ðð 75 1ðð

14:44:54 ISDNSS_B1 27/99/7ð 376 52 578 34

14:5ð:55 ISDNSS_B2 ðð/ð1/ðð 256 ð 255 ð

14:56:19 ISDNSS_B2 24/39/31 238 15 286 25

More... F3=Exit F11=View2 F12=Cancel F15=Sort by itv end F19=Sort by line ID


á ñ

Figure 5-5. Display Channel Interval Data for B-channel

From this display you can request data about the jobs using the communicationsline listed during any of the time intervals. To do this, type a 5 in the Option columnby the selected time interval.

à ðDisplay Channel Interval Data

Network Interface . : ISDNSS_A Member . . . . . . . : ISDN1

Channel . . . . . . : D Library . . . . . : QPFRDATA

Line speed . . . . . : 16.5 Elapsed time . . . . : ð1:54:39

IOP name . . . . . . : CMBð1

Transmit/ Loss

Receive/ -Outgoing Calls- -Incoming Calls- of

Itv Average Total Percent Total Percent Frame

End Line Util Calls Rejected Calls Rejected Alignment

14:46:2ð 12/21/16 42 28 15 26 452

15:ð1:19 2ð/ð6/13 74 74 33 1ðð 135

15:16:17 ðð/ðð/ðð ð ð 5 ð ð

15:21:17 ðð/ðð/ðð ð ð 2 ð ð

15:31:16 ðð/ðð/ðð ð ð 2 ð ð

15:46:14 ð7/1ð/ð9 21 1ðð 34 1ðð 348

More...


F3=Exit F11=View 2 F12=Cancel F13=Display maintenance channel

F24=More keys

á ñ

Figure 5-6. Display Channel Interval Data for D-channel


Display Maintenance Channel DataThis display shows performance data for the ISDN maintenance channel. Torequest it, press F13 (Display maintenance channel) on the Display ChannelInterval Data for D-channels display.

Note: F13 is shown only if the system you collected data for had its ISDN mainte-nance channel active.

à ðDisplay Maintenance Channel Data

Network Interface . : ISDNSS_A Member . . . . . . . : ISDN1

Line speed . . . . . : 16.5 Library . . . . . : QPFRDATA

IOP name . . . . . . : CMBð1 Elapsed time . . . . : ð1:54:39

Percent

Percent Severely Far

Itv Errored Errored DTSE DTSE End Code

End Seconds Seconds In Out Violation

14:46:2ð 5ð 36 734 83 32

15:ð1:19 6 24 32 14 52

15:16:17 ð ð ð ð ð

15:21:17 ð ð ð ð ð

15:31:16 ð ð ð ð ð

15:46:14 99 99 36 45 66

16:ð1:13 95 8ð 11 9 1

More...


F3=Exit F12=Cancel F15=Sort by itv end F2ð=Sort by DTSE in

F21=Sort by DTSE out F22=Sort by percent severely errored seconds

á ñ

Figure 5-7. Display Maintenance Channel Data


Chapter 6. System Activity

This chapter describes the functions that allow you to work with performance datafor the jobs and Licensed Internal Code tasks currently running on the system.These functions provide the ability to interactively view and collect the data in aQAITMON database file using the Work with System Activity (WRKSYSACT)command and to print reports based on the collected data (print activity report).These functions are available as AS/400 commands or through option 8 (Systemactivity) on the IBM Performance Tools menu. If you select option 8, the SystemActivity menu appears.

à ð System Activity


1. Work with system activity

2. Print activity report

�

�

�

Refer to “Work with System Activity” and “Print Activity Report” on page 6-9 for adescription of both selections shown on the System Activity menu.

Work with System ActivityThe Work with System Activity (WRKSYSACT) command allows you to view andcollect performance data in a realtime fashion. This data, which consists of CPUutilizations, synchronous and asynchronous I/O counts, storage amounts, andmore, is reported for any job or task that is currently active on the system.

Note: To be considered active, a job or task must use at least one-tenth of 1%(.1%) of the processing unit or perform one I/O operation.

Similar to the performance monitor started by the Start Performance Monitor(STRPFRMON) command, only one call of the Work with System Activity functioncan be active at one time. If this function is currently active when the WRKSYSACTcommand is run, you receive a message indicating that:

� The function is already active

� The name of the user profile who is running the command.

The performance statistics reported by this function represent activity that hasoccurred during the elapsed time since a previous collection. Notice that this maycontrast with other system functions that generally provide cumulative values untilspecifically reset. In most cases the time interval between data collections rangesfrom 1 second to several minutes, depending on how often you want to view orcollect new data. On systems with very little activity, a subsecond refresh intervalmay be possible.


Depending on the value specified for the OUTPUT parameter of the Work withSystem Activity command, the data gathered by this function is processed in one ofthe following methods:

� Shown on the display station only

� Written to a database file only

� Shown on the display station and written to a database file

When the data is written to a database file only, this function submits a batch jobunder the name WRKSYSACT. When the data is written to a file and shown on thedisplay, the statistics are put in the file each time the display is refreshed. Thisdoes not include the data presented on the initial display of the Work with SystemActivity display. See the file descriptions in Table 6-1 on page 6-8.

When the data is being directed to the display station (either the first or thirdmethod), the first display that appears resembles the following:

à ðWork with System Activity

ð2/ð8/96 1ð:45:19

Automatic refresh in seconds . . . . . . . . . . . . . . . . . 5

Elapsed time . . . . : ðð:ðð:ð2 Overall CPU . . . : 74.1


1=Monitor job 5=Work with job

Total Total

Job or CPU Sync Async PAG

Opt Task User Number Thread Pty Util I/O I/O Fault

_ DSP25 QPGMR ðð8124 2ð 56.1 12 4 ð

_ DSPð1 QSECOFR ðð8122 2ð 6.4 5 2 ð

_ DSPð7 QSYSOPR ðð8123 2ð 4.4 1 ð ð

_ DSPð4 QSECOFR ðð8119 1 3.7 ð ð ð

_ #AðððA ð 1.ð ð ð ð

_ #5ððð9 ð .6 ð ð ð

_ SMAIð3 ð .3 ð ð ð

_ ROUTð4 ð .3 ð ð ð


_ #Aððð3 ð .3 ð ð ð

More...

F3=Exit F1ð=Update list F11=View 2 F12=Cancel F19=Automatic refresh

F24=More keys

á ñ

Figure 6-1. System with Single Processor

The input-capable field Automatic refresh in seconds at the top of the display con-trols the amount of time between display refreshes when the automatic refreshfeature is active. Refer to “Automatic Refresh Mode” on page 6-4 for more informa-tion on this field. The second field at the top of the display, Elapsed time, reflectsthe length of time in which the currently shown performance statistics occurred.Described in a different way, this value represents the time between the last displayrefresh and the next-to-last display refresh.

Note: The Work with System Activity display automatically gathers the data twicebefore displaying the first display. Therefore, the initial Elapsed time shouldbe approximately 2 seconds, which means that the statistics shownoccurred in the 2 seconds previous to the current display.


Single-Processor SystemThe Overall CPU represents the CPU utilization for the entire system during theelapsed time. This value does not always equal the sum of the individual CPU utili-zations shown in the list, since a job or task could use an extremely small amountof processing unit time, thus affecting the overall utilization, but not use enoughCPU resource to be included in the list of active jobs. (Refer to the requirements forbeing considered active at the beginning of this chapter.) The discrepancy in CPUutilizations, however, is small and should have little effect on the usability of thisfunction.

Also, the Overall CPU could exceed 100% on extremely busy systems, becausethe data collection process does not occur instantaneously. However, you shouldbe aware that overall CPU utilizations slightly over 100% are an acceptable possi-bility.

Multiple-Processor SystemFor a multiple-processor system, Overall CPU field is replaced by these fields:

� Minimum CPU util

� Maximum CPU util

� Average CPU util

� Number of CPUs

For each of the CPU utilization fields, the value shown is the total CPU utilizationdivided by the number of processors shown in the Number of CPUs field.Figure 6-2 shows the Work with System Activity display for a system with morethan one processor:

à ðWork with System Activity ABSYSTEM

ð2/ð8/96 1ð:45:19


Elapsed time . . . . . . : ðð:ð1:ð2 Average CPU util . . : 97.ð

Minimun CPU util . . . . : 94.1 Maximum CPU util . . : 99.9

Number of CPUs . . . . . : 4



Total Total



QPADEVððð7 SUSTAITA ð29844 1 25.2 ð ð ð

QPADEVðð12 PATO ð29845 1 24.ð ð ð ð

QPADEVðð15 SOFIACN ð29846 1 25.5 ð ð ð

QPADEVðð6ð BRLEON ð29849 1 24.8 4 212 ð

Bottom


F24=More keys

á ñ

Figure 6-2. System with Multiple Processors

The two options shown on the Work with System Activity allow you to analyze spe-cific jobs and tasks that appear in the list. Refer to “Monitoring Specific Jobs” onpage 6-5 and “Working with Jobs” on page 6-6 for more information on theseoptions.

Chapter 6. System Activity 6-3

| The jobs and tasks are presented on this display in decreasing order of a number| of different methods. This order is initially controlled by the Sequence (SEQ)| parameter on the Work with System Activity command. The default is to sort the| jobs and tasks by CPU utilization. Once the function has been started, however,| F16 (Sequence by xxx) serves as a switch between the sorting methods.

| The Work with System Activity function uses different views to present all the per-| formance statistics. Pressing F11 shows you the next view in the series and| pressing F10 refreshes the current view.

Note: As mentioned above, the Job or Task column is shown only whenINFTYPE(*ALL) is specified. This value for the Information type parameterinstructs the function to display both jobs and tasks. SpecifyingINFTYPE(*JOBS) causes the Job or Task column, to be replaced by theJob column because only jobs are to be displayed. Similarly, specifyingINFTYPE(*TASKS) causes the Job or Task column to be replaced by theTask column since only tasks are to be displayed. Later sections of thischapter describe how to switch between these information types through theuse of function keys.

Automatic Refresh ModeAutomatic Refresh mode represents an important feature of the Work with SystemActivity function. Once started, this mode continually updates the display withoutrequiring further user intervention.

To start the Automatic Refresh mode, first enter the desired number of secondsbetween refreshes in the Automatic refresh in seconds field. This value, which hasan initial default of 5 seconds, can range from a minimum of 1 second to amaximum of 900 seconds (15 minutes).

Note: Setting the Automatic refresh seconds at 5 or greater generally results inthe Work with System Activity function using reasonably small amounts ofthe processing unit, depending on the size of the system being monitored.Setting this value lower than 5 seconds causes this function to use largeramounts of the processing unit, and therefore, is not recommended.

Once you have established the desired refresh interval, pressing F19 (Automaticrefresh) starts the automatic refresh mode. Automatic refresh continues to displaythe same view and type of information that was previously selected. For example, ifyou had been examining both jobs and tasks using View 1, the display appears asfollows.



1ð/ð1/98 ð9:51:48


Elapsed time . . . . : ðð:ðð:ð2 Overall CPU util . . : 1.6



Total Total



1 QPADEVðððI AABB ð54145 ðððððððC 1 .9 2 ð ð

1 CFINTð1 ð .1 ð ð ð

1 QUMBVROUTR AABBCCDD ð53919 ðððððð19 5ð .1 ð ð ð

1 QCQEPMON QSVMSS ð53243 ððððððð1 5ð .1 ð ð ð

1 QPFRADJ QSYS ð53184 ððððððð1 ð .1 ð ð ð

Bottom


F24=More keys

á ñ


| The Automatic Refresh function attempts to maintain even refresh intervals by com-| pensating for the time required to process, display, and, possibly, write the perform-| ance data. Therefore, you may occasionally notice that the elapsed time does not| exactly match the value specified for the Automatic refresh in seconds field. Press| F19 to end the automatic refresh function.

Monitoring Specific JobsWhile using the Work with System Activity function, you may want to view the per-formance statistics for a set of jobs and tasks on the system. By typing a 1 in theOpt column before a list entry, that job or task is selected for monitoring. You maymonitor as many as 20 jobs and tasks at a single time. If five jobs and tasks areselected for monitoring, the Work with System Activity display appears as follows:



1ð/ð1/978 ð9:51:48


Elapsed time . . . . : ðð:ðð:ð2 Overall CPU util . . : 1.6



Total Total



1 QPADEVðððI AABB ð54145 ðððððððC 1 .9 2 ð ð

1 CFINTð1 ð .1 ð ð ð

1 QUMBVROUTR AABBCCDD ð53919 ðððððð19 5ð .1 ð ð ð

1 QCQEPMON QSVMSS ð53243 ððððððð1 5ð .1 ð ð ð

1 QPFRADJ QSYS ð53184 ððððððð1 ð .1 ð ð ð

Bottom


F24=More keys

á ñ


Once you have selected jobs and tasks for monitoring, the Work with SystemActivity function is placed in a subset mode. While in this mode, you see perform-ance data for only the selected jobs and tasks whenever the display is refreshed.Also in this mode, you can use option 5 (Work with job) on a job and the jobremains in the selected group. To remove a single job or task from the selectedgroup (as long as it is not the last or only selected entry), blank out the option fieldand press the Enter key. This causes a new group to be built from those entriesthat still have a 1 in the Opt field.

To return to normal operating mode, press either F13 (Jobs and tasks), F14 (Jobsonly), or F15 (Tasks only). These function keys are the only way to end the moni-toring feature without exiting the Work with System Activity function.

Working with JobsBy typing a 5 in the option field next to a job and pressing the Enter key, the Workwith Job (WRKJOB) command is started for that job. Selecting more than one jobbefore pressing the Enter key causes the WRKJOB command to be started multipletimes.

Note: Option 5 (Work with job) is valid only with jobs. This function cannot bestarted for tasks.

Refer to the CL Reference or the Work Management book for further information onthe Work with Job command.


Displaying Different Information TypesAs previously mentioned, you can control the type of information being shown onthe display. This control comes through the use of the INFTYPE (Information type)parameter or through the use of F13 (Display jobs and tasks), F14 (Display jobsonly), or F15 (Display tasks only).

If you specify INFTYPE(*ALL) on the Work with System Activity command or pressF13, statistics for both jobs and tasks are shown. Column headings and functionkeys similar to the following appear on the Work with System Activity display:

Total Total



_ DSP25 QPGMR ðð8124 2ð 56.1 12 4 ð




.

.

.

F14=Display jobs only F15=Display tasks only F16=Sequence by I/O

F24=More keys

á ñ

If you specify INFTYPE(*JOBS) or press F14, statistics for jobs only are shown.Column headings and function keys similar to the following appear on the Workwith System Activity display:

Total Total

CPU Sync Async PAG

Opt Job User Number Thread Pty Util I/O I/O Fault

_ DSP25 QPGMR ðð8124 2ð 56.1 12 4 ð


.

.

.

F13=Display jobs and tasks F15=Display tasks only F16=Sequence by I/O

F24=More keys

á ñ

And finally, if you specify INFTYPE(*TASKS) or press F15, statistics for tasks onlyare shown. Column headings and function keys similar to the following appear onthe Work with System Activity display:

Total Total

CPU Sync Async PAG

Opt Task Thread Pty Util I/O I/O Fault



.

.

.

F13=Display jobs and tasks F14=Display jobs only F16=Sequence by I/O

F24=More keys

á ñ


Accessing Work Management FunctionsTo assist you in analyzing the performance of the system, function keys F20through F23 have been set up to provide access to several Work Managementfunctions. The third set of function keys appears on the Work with System Activitydisplay as follows:

F2ð=Work with active jobs F21=Work with system status

F22=Work with subsystems F23=Work with disk status F24=More keys

á ñ

F20 starts the Work with Active Jobs (WRKACTJOB) command. F21 starts theWork with System Status (WRKSYSSTS) command. F22 starts the Work with Sub-systems (WRKSBS) command, and F23 starts the Work with Disk Status(WRKDSKSTS) command. Refer to the Work Management book for further infor-mation on these commands.

Content of Database File QAITMONThe collected performance data is stored in the file QAITMON located in the libraryspecified by the LIB parameter on the Work with System Activity command. Eachperformance collection, which is stored in a member determined by the MBRparameter, contains one record for each active job or task in an interval.

Table 6-1 describes the content of a single record in QAITMON.

Table 6-1 (Page 1 of 2). File QAITMON

Field Name Attributes Description

LVLID CHAR(7) The level of the module that collected this data and the level ofthis file in the form VVRRRFF, where VV = version number, RRR= release number, and FF = file level.

DTETIM CHAR(13) The date (CMMDDYY) and time (HHMMSS) that the data was col-lected.

ITVTIM PACKED(11,0) The time between data collections, where one unit equals 4096microseconds.

CPUTOT PACKED(11,0) The total processing unit time used by all tasks and jobs duringthe interval, where one unit equals 4096 microseconds. Formultiple-processor systems, this is the average use by allprocessors.

NAME CHAR(10) The job or task name for this entry.JOBUSR CHAR(10) The user profile associated with a job.JOBNBR CHAR(6) The number assigned to the job.PTY CHAR(3) The priority of the job or task when the data was collected.CPUDLT PACKED(11,0) The processing unit time used by this task or job during the

interval, where one unit equals 4096 microseconds. For multiple-processor systems, this is the average use by all processors.

IOTOT PACKED(11,0) The total physical I/O operations (synchronous and asynchronous)performed by this job or task.

SDBR PACKED(11,0) The number of synchronous database reads.SNDBR PACKED(11,0) The number of synchronous nondatabase reads.SDBW PACKED(11,0) The number of synchronous database writes.SNDBW PACKED(11,0) The number of synchronous nondatabase writes.ADBR PACKED(11,0) The number of asynchronous database reads.


Table 6-1 (Page 2 of 2). File QAITMON

Field Name Attributes Description

ANDBR PACKED(11,0) The number of asynchronous nondatabase reads.ADBW PACKED(11,0) The number of asynchronous database writes.ANDBW PACKED(11,0) The number of asynchronous nondatabase writes.PAGFLT PACKED(11,0) The number of process access group faults.RSRV2 PACKED(11,0) Reserved.JTFLAG CHAR(1) A flag indicating whether this record represents a job or task

where ‘00’X = job and ‘80’X = task.RSRV1 CHAR(4) Reserved.PERMW PACKED(11,0) The number of writes that were for permanent objects.IOPND PACKED(11,0) The number of I/O-pending page faults.SMSYNC PACKED(11,0) The number of waits for asynchronous I/O operations to complete.OVRTOT PACKED(11,0) The total number of binary, decimal, and floating point overflow

exceptions.CPU11 PACKED(11,0) For multiple-processor systems, the time used in processor one by

jobs and tasks during the interval. One unit of time equals 4096microseconds.

CPU21 PACKED(11,0) For multiple-processor systems, the time used in processor two byjobs and tasks during the interval. One unit of time equals 4096microseconds.

CPUCNT PACKED(3,0) The number of active processors in the system during data col-lection.

CPU31 PACKED(11,0) For multiple-processor systems, the time used in processor threeby jobs and tasks during the interval. One unit of time equals 4096microseconds.

CPU41 PACKED(11,0) For multiple-processor systems, the time used in processor four byjobs and tasks during the interval. One unit of time equals 4096microseconds.

CPU5–CPU32 PACKED(11,0) For multiple-processor systems, the time used in processor n byjobs and tasks during the interval. One unit of time equals 4096microseconds.

| THDID| CHAR(8)| The thread identifier assigned to a job. When a task is running,| this field is blank.| STGALC| PACKED(11,0)| Reserved.| STGDLC| PACKED(11,0)| Reserved.

Notes:

1 Even though these fields are no longer shown on the Work with System Activity display, youcan query the QAITMON file after running WRKSYSACT OUTPUT(\FILE) or WRKSYSACTOUTPUT(\BOTH).

Print Activity ReportThe Print Activity Report (PRTACTRPT) command creates a report using the per-formance data collected by the Work with System Activity (WRKSYSACT)command. This report is produced in the spooled file QPITACTR.

Depending on the value specified for the Report Type (RPTTYPE) option on thePrint Activity Report command, one of two report types, or both, are created. Thesummary report provides the top 10 listings showing the most CPU-intensive andthe most I/O-intensive entries over the entire specified period. The detailed reportshows a selected number of entries for each interval in the specified period. Theseentries are ordered according to a user selected field. Refer to the followingsections for more detail on each of these report types.


Summary Activity ReportThe Summary Activity Report consists of two sections. The first lists (in decreasingorder) the top 10 entries according to CPU utilization during the specified period,and the second lists (also in decreasing order) the top 10 entries according to totalI/O activity performed during the specified period. The value used for total I/O isactually the sum of the total synchronous I/O and the total asynchronous I/O. If 10active jobs or tasks are not present in the specified period, these sections list asmany entries as are available.

The following represents a sample Summary Activity Report:

System Activity Report 3/3ð/98 11:ð6:26

Page 1

Member . . . . : QAITMON Report Type . . . . : SUMMARY Version . . . . : 4 Started . . . . : ð3/3ð/98 1ð:56:22

Library . . . . : QPFRDATA Release . . . . : 2.ð Stopped . . . . : ð3/3ð/98 1ð:57:ð9

Order by CPU Utilization:

Total Total -------Synchronous I/O----- ------Asynchronous I/O------

Job or CPU Sync Async PAG DB DB Non-DB Non-DB DB DB Non-DB Non-DB

Task User Number Pty Util I/O I/O Fault Read Write Read Write Read Write Read Write

---------- ---------- ------ --- ---- ----- ----- ----- ----- ----- ------ ------ ----- ----- ------ ------

QCQSARTR QSVCCS ð93261 35 17.9 45ð 21 7 35 ð 387 28 4 2 ð 15

QCQRCVDS QSVMSS ð93254 2ð 2.7 156 128 ð ð ð 152 4 ð ð ð 128

QPADEVððð3 PITA ð93215 2ð 2.3 291 43 3 ð ð 186 1ð5 ð 1 ð 42

QPADEVððð4 ALDO ð93219 2ð 1.8 157 29 2 ð ð 127 3ð ð ð ð 29

CFINT1 ð 1.2 ð ð ð ð ð ð ð ð ð ð ð

WRKSYSACT RAMON ð93253 1 .7 45 2ð ð ð 3ð 1 14 ð 2ð ð ð

SMPOððð2 ð .2 24 ð ð ð ð ð 24 ð ð ð ð

QSYSWRK QSYS ð9313ð ð .1 24 ð ð ð ð 4 2ð ð ð ð ð

QTGTELNETS QTCP ð93172 2ð .1 ð ð ð ð ð ð ð ð ð ð ð

QPADEVððð5 MUTH ð932ð5 2ð .ð 9 ð ð 2 ð 7 ð ð ð ð ð

Order by Total I/O:




---------- ---------- ------ --- ---- ----- ----- ----- ----- ----- ------ ------ ----- ----- ------ ------

QDCPOBJ2 QSYS ð93115 6ð .ð ð ð ð ð ð ð ð ð ð ð ð

QDCPOBJ1 QSYS ð93114 6ð .ð ð ð ð ð ð ð ð ð ð ð ð

SCPF QSYS ðððððð 4ð .ð 17 5 ð 2 6 7 2 ð 1 ð 4

LCTRS ð .ð ð ð ð ð ð ð ð ð ð ð ð

SMASPTASK ð .ð ð ð ð ð ð ð ð ð ð ð ð

SMPOððð3 ð .ð 73 ð ð ð 1 ð 72 ð ð ð ð

SMPOððð2 ð .2 24 ð ð ð ð ð 24 ð ð ð ð

SMPOððð1 ð .ð 49 ð ð ð 1 ð 48 ð ð ð ð

QPADEVðð15 RAMON ð93231 2ð .ð ð ð ð ð ð ð ð ð ð ð ð

QTGTELNETS QTCP ð93172 2ð .1 ð ð ð ð ð ð ð ð ð ð ð

Figure 6-5. Sample Summary Activity Report

The header portion of this report contains the following information:

Report title The title of the report.

Current date and time The date and time when this report was printed.

Report page number The page number currently being printed.

User-selected report title The title specified by the user on the TITLE parameterof the Print Activity Report command.

Member The name of the member in QAITMON that contained the performancedata.

Library The library where QAITMON was located.

Report type The type of report, either summary or detail, being printed.

Version The version of the Performance Tools licensed program that collectedthe data.


Release The release level of the Performance Tools licensed program that col-lected the data.

Period start date and time The start date and time of the period during which theperformance statistics being printed were collected.

Period end date and time The end date and time of the period during which theperformance statistics being printed were collected.

The columns in the summary activity report are:

Job or Task The name of the job or task for which the performance statistics arebeing printed.

User The user profile associated with the job.

Number The number assigned to the job.

Pty The priority at which the job or task was running when the performancestatistics were first collected.

CPU Util The percentage of the specified period during which the processing unitwas used by the job or task. For a multiple-processor system, this is thetotal utilization divided by the number of processors.

Total Sync I/O The total number of synchronous physical disk I/O operations per-formed by the job or task during the specified period. This value is thesum of the synchronous database/nondatabase reads and writes.

Total Async I/O The total number of asynchronous physical disk I/O operationsstarted by the job or task during the specified period. This value is thesum of the asynchronous database/nondatabase reads and writes.

PAG Fault The number of process access group (PAG) faults caused by the job ortask during the specified period.

Synchronous I/O DB Read The number of synchronous database read operationsperformed by the job or task during the specified period.

Synchronous I/O DB Write The number of synchronous database write operationsperformed by the job or task during the specified period.

Synchronous I/O Non-DB Read The number of synchronous nondatabase readoperations performed by the job or task during the specified period.

Synchronous I/O Non-DB Write The number of synchronous nondatabase writeoperations performed by the job or task during the specified period.

Asynchronous I/O DB Read The number of asynchronous database read oper-ations started by the job or task during the specified period.

Asynchronous I/O DB Write The number of asynchronous database write oper-ations started by the job or task during the specified period.

Asynchronous I/O Non-DB Read The number of asynchronous nondatabase readoperations started by the job or task during the specified period.

Asynchronous I/O Non-DB Write The number of asynchronous nondatabase writeoperations started by the job or task during the specified period.

Note: The asynchronous I/O operations are performed by system asynchronousI/O tasks.


Detail Activity ReportFor each interval available in the specified period, the Detail Activity Report lists theperformance statistics for the number of entries specified by the Number of Jobs(NBRJOBS) parameter. The entries are ordered according to the Sequence (SEQ)parameter.

The following represents a sample Detail Activity Report.

System Activity Report 5/3ð/98 11:ð6:38

Page 1

Member . . . . : QAITMON Report Type . . . . : DETAIL Version . . . . : 4 Started . . . . : ð5/3ð/98 1ð:56:22

Library . . . . : QPFRDATA Sequence . . . . . : CPU Release . . . . : 2.ð Stopped . . . . : ð5/3ð/98 1ð:57:ð9

Time . . . . : 1ð:56:22 Total CPU Utilization . . . . . . . . . . . : .ð




---------- ---------- ------ --- ---- ----- ----- ----- ----- ----- ------ ------ ----- ----- ------ ------

WRKSYSACT RAMON ð93253 1 .2 ð ð ð ð ð ð ð ð ð ð ð

RMSRVCTKLO ð .ð ð ð ð ð ð ð ð ð ð ð ð

LIDMGR-TAS K--AHT ð .ð ð ð ð ð ð ð ð ð ð ð ð


SMASPAGENT TASK ð .ð ð ð ð ð ð ð ð ð ð ð ð

SMCFGVALID ATER ð .ð ð ð ð ð ð ð ð ð ð ð ð

SMCFGUPDAT ER ð .ð ð ð ð ð ð ð ð ð ð ð ð

SMSLSSERVI CETASK ð .ð ð ð ð ð ð ð ð ð ð ð ð

IOPI-HRI-P ERS-IO ð .ð ð ð ð ð ð ð ð ð ð ð ð

XMERRLOGER ð .ð ð ð ð ð ð ð ð ð ð ð ð

Time . . . . : 1ð:56:27 Total CPU Utilization . . . . . . . . . . . : .ð




---------- ---------- ------ --- ---- ----- ----- ----- ----- ----- ------ ------ ----- ----- ------ ------

WRKSYSACT RAMON ð93253 1 .7 8 2 ð ð 3 1 4 ð 2 ð ð

QPADEVððð5 MUTH ð932ð5 2ð .5 9 ð ð 2 ð 7 ð ð ð ð ð

QLZPSERV QUSER ð93239 2ð .ð ð ð ð ð ð ð ð ð ð ð ð

RMSRVCTKLO ð .ð ð ð ð ð ð ð ð ð ð ð ð

LIDMGR-TAS K--AHT ð .ð ð ð ð ð ð ð ð ð ð ð ð


SMASPAGENT TASK ð .ð ð ð ð ð ð ð ð ð ð ð ð

SMCFGVALID ATER ð .ð ð ð ð ð ð ð ð ð ð ð ð

SMCFGUPDAT ER ð .ð ð ð ð ð ð ð ð ð ð ð ð

SMSLSSERVI CETASK ð .ð ð ð ð ð ð ð ð ð ð ð ð

Figure 6-6. Sample Detail Activity Report

The header portion of this report contains the same information as found on thesummary report, except for the Sequence field, which defines the order of theentries listed for each interval. The value found in this field corresponds to thevalue specified for the sequence (SEQ) parameter on the Print Activity Reportcommand.

The body of the Detail Activity Report contains the same columns of informationfound on the summary report. There are, however, two additional fields associatedwith the statistics for each interval:

Time The end time for the collection interval.

Total CPU Utilization The processing unit use for the entire system during the col-lection interval.

For a multiple-processor system, this is the total utilization divided by the number ofprocessors.


Chapter 7. Performance Reports—Manager Feature

Performance reports provide a way for you to effectively research areas of thesystem that are causing performance problems. After you have collected perform-ance data over time, different reports offer you ways to see how and where systemresources are used. Performance reports can direct you to specific application pro-grams, users, or inefficient workloads that are causing lower overall responsetimes.

| Note: While the performance reports have no exact restrictions on the amount of| performance data that they can process, in general, it is recommended that| a collection be no longer than one week in length. In fact, the optimal col-| lection strategy is to run a new collection every day.

Several types of performance reports show data focusing on different aspects ofthe system. For example, one report identifies CPU use and another identifies com-munications use. These reports help identify various performance problems: if youget complaints that the user sign-ons are taking longer than they should, you coulduse a Transaction Report to find out how many CPU seconds are used by thesign-on. You could then use a Transition Report to more closely identify how thoseCPU seconds are used.

A Performance Report

| System Report 3/2ð/98 14:ð6:27

| Disk Utilization Page ððð5

| Sample System Report

| Member . . . : Q98224ð9ð3 Model/Serial . : 4ðð-2133/1ð-3594G Main storage . . : 96.ð M Started . . . . : ð3/12/98 ð9:ð4:28

| Library . . : QPFRDATA System name . . : ABSYSTEM Version/Release : 4/ 2.ð Stopped . . . . : ð3/12/98 ð9:ð4:35

| Unit Size IOP IOP Dsk CPU ASP --Percent-- Op Per K Per - Average Time Per I/O --

| Unit Name Type (M) Util Name Util ID Full Util Second I/O Service Wait Response

| ---- ---------- ---- ------- ---- ------------ ------- --- ---- ---- --------- --------- ------- ------ --------

| ððð1 DDðð1 66ð6 1,967 47.3 CMBð1 .ð ð1 76.9 33.3 3ð.2ð 4.8 .ð11ð .ðð37 .ð147

| ððð2 DDðð2 66ð6 1,967 47.3 CMBð1 .ð ð1 74.2 44.4 31.25 7.3 .ð142 .ðð35 .ð177

| ððð3 DDðð3 66ð6 1,967 47.3 CMBð1 .ð ð1 74.ð .ð 25.4ð 4.3 .ðððð .ðððð .ðððð

| ððð4 DDðð4 66ð6 1,967 47.3 CMBð1 .ð ð1 74.2 33.3 29.2ð 6.7 .ð114 .ð19ð .ð3ð4

| Total 7,868

| Average 74.9 27.7 28.89 5.8 .ðð95 .ðð68 .ð163

| Unit -- Disk arm identifier

| Unit Name -- Disk arm resource name

| Type -- Type of disk

| Size (M) -- Disk space capacity in millions of bytes

| IOP Util -- Percentage of utilization for each Input/Output Processor

| IOP Name -- Input/Output Processor resource name

| Dsk CPU Util -- Percentage of Disk Processor Utilization

| ASP ID -- Auxiliary Storage Pool ID

| Percent Full -- Percentage of disk space capacity in use

| Percent Util -- Average disk operation utilization (busy)

| Op per Second -- Average number of disk operations per second

| K Per I/O -- Average number of kilobytes (1ð24) transferred per disk operation

| Average Service Time -- Average disk service time per I/O operation

| Average Wait Time -- Average disk wait time per I/O operation

| Average Response Time -- Average disk response time per I/O operation

Figure 7-1. A Performance Report

Note: This report is only provided as an example of the layout of a report. Seeeach specific report example for current report details.


Performance Report HeaderEach report, regardless of the type or section, contains information in the header ofthe report that identifies characteristics of the data:

Report title The first line identifies the type of performance report. The second lineidentifies the section of the report.

Current date and time Is the date and time the report was printed.

Report page number Identifies the page of the report.

User-selected report title Is the name assigned to the report by a user.

Data member name Is the performance data member used in the report. Thisname corresponds to the name used on the MBR parameter of the StartPerformance Monitor (STRPFRMON) command.

Library name Is the library where the performance data used in the report islocated.

Model number 4ðð is the model number and 2133 is the feature code of theAS/400 system on which the performance data was collected for thisreport.

Serial number 1ð-3594G is the serial number of the system unit in this example.The serial number can be 10 characters.

System name ABSYSTEM is the name of the system on which the performance datawas collected for this report.

Main storage size Is the size of the main storage on the AS/400 system on whichthe performance data was collected in this example.

OS/400 version and release level x/ x.ð indicates which version and releaselevel that the AS/400 system was running.

Data collection start date and time Is the date and time the performance monitorstarted collecting performance data in this example. Depending onwhether or not you select specific intervals or a specific starting time,you could see the following:

� If you specify no intervals at which to run the report, the start dateand time is the date and time at which the data was collected.

� If you specify specific intervals at which to run the report, the startdate and time is the date and time at which the data was collected.

Note: For the system report only, you should consult the ReportSelection Criteria section to find out which intervals wereselected.

Data collection stop date and time Is the date and time the performance monitorstopped collecting performance data in this example. Depending onwhether or not you select specific intervals or a specific ending time, youcould see the following:

� If you specify no intervals at which to run the report, the stop dateand time is the date and time at which the data was collected.

� If you specify specific intervals at which to run the report, the stopdate and time is the date and time at which the data was collected.


Note: For the system report only, you should consult the ReportSelection Criteria section to find out which intervals wereselected.

Column headings Each report also has several columns that make up the informa-tion of the report. Some are specific to a particular report and others areconsistent between reports. In this example, IOP Util is one of thecolumn headings. For short descriptions of these columns, see “Per-formance Report Columns” on page 7-102.

Available Performance ReportsSystem Report This report has the following sections:

� Workload

� Resource Utilization

� Resource Utilization Expansion

� Storage Pool Utilization

� Disk Utilization

� Communications Summary

� Report Selection Criteria

Component Report This report has the following sections:

� Component Interval Activity

� Job Workload Activity

� Storage Pool Activity

� Disk Activity

� IOP Utilizations

� Local Work Stations–Response Time Buckets

� Remote Work Station–Response Time Buckets

� Exception Occurrence Summary and Interval Counts

� Database Journaling Summary


Transaction Report This report has the following sections:

� Job Summary Report

– Job Summary

– System Summary Data

– Distribution of Transactions by CPU/Transaction

– Transaction Significance

– Interactive Transactions by 5-Minute Intervals

– Interactive Throughput by 5-Minute Intervals

– Interactive CPU

– Interactive Response Time by 5-Minute Intervals

Chapter 7. Performance Reports—Manager Feature 7-3

– Scatter diagram

– Interactive Program Transaction Statistics

– Summary of Seize/Lock Conflict by Object

– Report Selection Criteria

The default for the OPTION parameter on the PRTTNSRPTcommand is *SS (special system information). If you leave thisdefault, the following special summary sections print:

– Priority-Jobtype-Pool Statistics

– Job Statistics

– Interactive Program Statistics

– Individual Transaction Statistics

– Longest Seize/Lock Conflicts

– Longest Holders of Seize/Lock Conflicts

– Batch Job Analysis

| – Concurrent Batch Job Statistics

� Transaction Report

� Transition Report

Lock Report

Job Interval Report This report has the following sections:

� Interactive Job Summary

� Noninteractive Job Summary

� Interactive Job Detail

� Noninteractive Job Detail


Pool Interval Report This report has the following sections:

� Subsystem Activity

� Pool Activity


Resource Interval Report This report has the following sections:

� Disk Utilization Summary

� Disk Utilization Detail

� Communications Line Detail

– SDLC Protocol

– X.25 Protocol

– TRLAN Protocol

– ELAN Protocol

– ASYNC Protocol

– BSC Protocol


– ISDN Network Interface

– Network Interface Maintenance Channel for ISDN

– IDLC Protocol

– DDI Protocol

– Frame Relay Protocol

� IOP Utilizations

� Local Work Station Response Times

� Remote Work Station Response Times

Batch Job Trace Report This report has the following sections:

� Job Summary

Which Report Do I Want?The “System Report” on page 7-17 supplies you with an overview of how thesystem is operating. It contains summary information on the workload, resourceuse, storage pool utilization, disk utilization, and communications. This is a goodreport to run and print often, giving you a general idea of system use. You can printselected sections of this report.

The “Component Report” on page 7-25 supplies you with information about thesame components of system performance as a System Report, but at a greaterlevel of detail. This report helps you find which jobs are consuming high amounts ofsystem resources, such as CPU, disk, and so on.

The “Job Interval Report” on page 7-66, “Pool Interval Report” on page 7-72, and“Resource Interval Report” on page 7-76 provide the same information as theSystem Report and Component Report do, but on an interval-by-interval basis.

The “Lock Report” on page 7-63 provides information about lock and seize conflictsduring system operation.

The “Batch Job Trace Report” on page 7-89 shows the progression of different jobtypes (for example, batch jobs) traced through time.

The “Transaction Report” on page 7-36 provides detailed information about thetransactions that occurred during the performance data collection.

Printing Performance ReportsYou can print reports using the performance data collected with the Start Perform-ance Monitor (STRPFRMON) command.

Use the following commands to print reports:

� Print System Report (PRTSYSRPT)

� Print Component Report (PRTCPTRPT)

� Print Transaction Report (PRTTNSRPT)

� Print Lock Report (PRTLCKRPT)


� Print Job Report (PRTJOBRPT)

� Print Pool Report (PRTPOLRPT)

� Print Resource Report (PRTRSCRPT)

� Print Trace Report (PRTTRCRPT)

Using Menus to Print Performance Reports1. To start Performance Tools, use the Start Performance Tools (STRPFRT)

command or type go perform on a command line.

2. To print selected information from the data you collect, choose option 3 (Printperformance report) on the IBM Performance Tools menu. The Print Perform-ance Report display appears.

The member name, a text description, and the date and time you collectedeach set of performance data appear on this display. If you cannot find the datayou want to print in a report, use the appropriate function key to sort the sets ofperformance data. You can sort them by member name, text description, or bythe date and time the member was created.

3. When you find the performance data, select the type of report you want bytyping one of the following options that corresponds to the type of report:

Option Description

1 System Report

2 Component Report

3 Transaction Report

4 Lock Report

5 Job Report

6 Pool Report

7 Resource Report

8 Batch Job Trace Report

à ðPrint Performance Report



1=System report 2=Component report 3=Transaction report 4=Lock report

5=Job report 6=Pool report 7=Resource report 8=Batch job trace report


1 TUEDTA ð3/17/98 12:2ð:29

_ DLTTEST18 ð3/17/98 1ð:1ð:2ð

_ DLTTEST17 ð3/17/98 1ð:1ð:ð2

_ DLTTEST16 ð3/17/98 1ð:ð9:42

_ DLTTEST15 ð3/17/98 1ð:ð9:32

_ DLTTEST14 ð3/17/98 1ð:ð9:22

_ DLTTEST13 ð3/17/98 1ð:ð9:ð4

_ DLTTEST11 ð3/17/98 1ð:ð8:56

_ DLTTEST1ð ð3/17/98 1ð:ð8:49

_ DLTTEST9 ð3/17/98 1ð:ð8:44

_ DLTTEST8 ð3/17/98 1ð:ð8:35

More...

F3=Exit F5=Refresh F11=Work with your spooled output files F12=Cancel

F15=Sort by member F16=Sort by text


Note: When the monitor is running and using one of the members shown inthe Print Performance Report display, this member may appear withblank Date and Time fields until the first interval is collected.

4. To print a Transaction Report, Lock Report, or Batch Job Trace Report, pressthe Enter key and the parameters for the corresponding command appear.

The Select Sections for Report display appears when you select to print theJob Report (PRTJOBPRT).

à ðSelect Sections for Report

Member . . . . . . . . . . . : Q961ð3ð917

Type options, press Enter. Press F6 to print entire report.

1=Select

Option Section Workload

Resource Utilization

Resource Utilization Expansion

Storage Pool Utilization

Disk Utilization

Communication Summary

Bottom F3=Exit F6=Print entire report F12=Cancel

The Select Categories for Report display appears when you select to print oneof the following reports:

� System Report

Note: The Select Sections for Report display is shown first, followed bythe Select Categories for Report display.

� Component Report

� Job Report

� Pool Report

� Resource Report


à ðSelect Categories for Report

Member . . . . . . . . . . . : TUEDTA


1=Select

Option Category

_ Time interval

_ Job

_ User ID

_ Subsystem

_ Pool

_ Communications line

_ Control unit

_ Functional area

Bottom

F3=Exit F6=Print entire report F12=Cancel

The name of the performance data member you chose on the Print Perform-ance Report display appears at the top of the Select Categories for Reportdisplay.

5. To include all categories of information in your report, Press F6. To limit theamount of information in the report, type a 1 in the Option column next to thosecategories of information for which you want performance data. Press the Enterkey.

For example, if you choose the Time interval option, the Select Time Intervalsdisplay appears. This display shows an interactive view of some of the key per-formance parameters of the data collected. The member name you typed onthe Print Performance Reports display appears in the Performance data field.The intervals you defined to collect the performance data appear.

à ðSelect Time Intervals

Library . . . . . : QPFRDATA Performance data . . . . . : TUEDTA


1=Select

CPU High Pool

Transaction -Utilization- --Util-- -Fault/Sec-

Opt Date Time Count Resp Tot Inter Bch Dsk Unit Mch User ID Excp

_ ð3/17 12:39 33 1.5 3 2 ð 2 ðð17 ð 1 ð3 77

_ ð3/17 12:44 26 .9 1 1 ð 1 ððð2 ð ð ð3 7

_ ð3/17 12:49 2ð .2 1 ð ð 1 ððð9 ð ð ð3 7


F13=Sort (date/time) F14=Sort (count) F24=More keys

6. Use the Select Time Intervals display to choose specific time intervals from theperformance data to produce a report. You should select specific time intervalsto help you manage the volume of data associated with the performance meas-urement. The Select Time Intervals display allows you to interactively select the


time intervals of interest. This selection reduces the amount of processingrequired to produce the requested report, and also reduces the size of theresulting report.

To select time intervals to print on your report, type a 1 in the Opt column nextto the appropriate intervals. When you select multiple intervals, they are com-bined to create a single report.

If it is difficult to find the time interval you need, you can sort the intervals differ-ently before making your selection. You can choose to sort the time intervals inany of the following ways:

� Date/time

� Transaction count

� Response time

� Total processing unit time

� Interactive processing unit time

� Batch processing unit time

� Disk utilization

� Machine pool faults

� User pool faults

� Exceptions

If you choose to print the report with only certain categories of information, adisplay appears for each category. For example, if you choose Pool, the Selector Omit Pools display appears.

7. Use the Select or Omit Pools display to select pools to include or omit fromyour report. To use this display, type the number for the pools you want toselect or omit. If you do not know the pool numbers to select, press F4(Prompt) to see a list of pools that were active during the collection of perform-ance data.

à ðSelect or Omit Pools

Member . . . . . . . . . . . : TUEDTA


1=Select 2=Omit

Option Pool Text

_ ð1 Machine pool

_ ð2 Base pool

_ ð3

_ ð4

Bottom

F12=Cancel

Type a 1 in the Option column next to the items you want to include in yourreport. Or type a 2 if you want certain items omitted from your report.


Note: You cannot use both the Select and Omit options at the same time. Youmust indicate either the items to select or the items to omit.

To include all the items in the report, leave the Option column blank, and pressthe Enter key.

For each category you choose on the Select Categories for Report display, youmust complete one of the following corresponding displays:

� Select Time Intervals

� Select or Omit Pools

� Select or Omit Jobs

� Select or Omit User IDs

� Select or Omit Subsystems

� Select or Omit Communications Lines

� Select or Omit Control Units

� Select or Omit Functional Areas

When you choose the information you want to appear on your report from theoptions shown on these displays, the Select Report Options display appears.Following is an example of the display that appears if you did not use theSelect Time Intervals display to choose any time intervals:

à ðSpecify Report Options


Report title . . . . New data entry in production_________________

Start:

Day . . . . . . . \FIRST__ \FIRST, MM/DD/YY

Time . . . . . . . \FIRST__ \FIRST, HH:MM:SS

Stop:

Day . . . . . . . \LAST___ \LAST, MM/DD/YY

Time . . . . . . . \LAST___ \LAST, HH:MM:SS

Omit system tasks . \YES \YES, \NO

8. Specify the start and stop date and time. If you do not specify the start andstop date and time, the report includes data from the first (or only) date thatdata was collected, to the last (or only) date that data was collected. You mayalso type a report title in the Report title field and specify whether or not youwant your report to include the system tasks. Press the Enter key to processand print your report.

Note: The Omit system tasks field appears only if you requested printing of aSystem Report.

If you made use of the Select Time Intervals display, the following version ofthe Select Report Options display appears instead:




Report title . . . . _________________________________________________

Omit system tasks . \YES \YES, \NO

If you so choose, type a report title in the Report title field. Also, you canspecify whether or not to include the system tasks in your report. Press theEnter key to process and print your report.

Using Defaults to Print Performance ReportsThe example in this section describes how to collect performance data and print aSystem Report using the default values on the displays shown.

Note: These values are the defaults for the STRPFRMON and PRTSYSRPT com-mands.

Use the Start Performance Tools (STRPFRT) command to start Performance Tools.

à ð

PERFORM IBM Performance Tools for AS/4ðð

System: RCHXXXXX









8. System activity


1ð. Advisor


Make the choices shown on the following displays to collect performance data andprint a System Report using the system defaults.

1. To start collecting performance data, choose option 2 (Collect performancedata) on the IBM Performance Tools menu, and press the Enter key. TheCollect Performance Data display appears.

à ðCollect Performance Data





2. Choose option 1 (Start collecting data).

3. Press the Enter key. The Start Collecting Data display appears.


à ðStart Collecting Data


1. Collect data with defaults

2. Collect data with menus

3. Collect data with command

4. Choose option 1 (Collect data with defaults).

5. Press the Enter key. The Collect Data with Defaults display appears.

à ð

Collect Data with Defaults


Member . . . . . . . . Thursdata_ Name

Library . . . . . . QPFRDATA__ Name

Text . . . . . . . . . System performance for Thursday

Time duration:

Hours . . . . . . . 9 ð-999

Minutes . . . . . . ð ð-6ð

6. Type an appropriate name for the performance data in the Member field. In thisexample, the performance data is called Thursdata.

7. Type an appropriate description for the performance data you want to collect inthe Text field. In this example, the description is System performance for

Thursday.

8. Type how long you want to collect performance data in the Time duration fields.In this example, 9 is typed in the Hours field so performance data is collectedfor 9 hours.

9. Press the Enter key to start the data collection process.

10. Press F3 (Exit).

Wait for the data collection process to end before you complete the next steps.In this example, you would wait for 9 hours before you would continue.

11. Once the data collection process is complete, use the STRPFRT command tostart Performance Tools.

12. Choose option 3 (Print performance report) on the IBM Performance Toolsmenu. The Print Performance Report display appears.

à ðPrint Performance Report



1=System report 2=Component report 3=Transaction report 4=Lock report

5=Job report 6=Pool report 7=Resource report 8=Batch job trace report


1 THURSDATA System performance for Thursday ð3/19/98 12:2ð:29

DLTTEST18 ð3/19/98 1ð:1ð:2ð

DLTTEST17 ð3/19/98 1ð:1ð:ð2


13. Type a 1 in the Option column, next to the performance member calledTHURSDATA, to indicate that you want to print a System Report from this perform-ance data.

14. Press the Enter key. The Select Categories for Report display appears.

à ðSelect Categories for Report

Member . . . . . . . . . . . : THURSDATA


1=Select

Option Category

_ Time interval

_ Job

_ User ID

_ Subsystem

_ Pool


_ Control unit

_ Functional area

15. Press F6 to indicate that you do not want to restrict the categories for thisreport. The Specify Report Options display appears.



Report title . . . . System performance for Thursday

Start:

Day . . . . . . . \FIRST \FIRST, MM/DD/YY

Time . . . . . . . \FIRST \FIRST, HH:MM:SS

Stop:

Day . . . . . . . \LAST \LAST, MM/DD/YY

Time . . . . . . . \LAST \LAST, HH:MM:SS

16. Press the Enter key to submit a batch request to print a System Report for theentire data collection period.

17. Press F3 (Exit) to go to the IBM Performance Tools menu.

The batch request you submit takes a period of time to complete, depending onthe amount of data collected. Use the Work with Submitted Job (WRKSBMJOB)command to check the status of the request.

After the System Report has been produced, you can view it online and direct itto an active writer by following steps 18 through 21.



System: ABSYSTEM









8. System activity


1ð. Advisor



===> WRKSPLF____________________________________________________________

________________________________________________________________________



á ñ

18. Type WRKSPLF on the command entry line, and press the Enter key.

The Work with All Spooled Files display appears.

à ðWork with All Spooled Files


2=Change 3=Hold 4=Delete 5=Display 6=Release 8=Attributes

Device or Total Cur

Opt File User Queue User Data Sts Pages Page Copy

2 QPPTSYSR USERID QSYSPRT RDY 7 1

Parameters for option 2 or command

===> OUTQ(outqname)_____________________________________________________

F3=Exit F1ð=View 3 F11=View 2 F12=Cancel F24=More keys

á ñ

On this display you could choose option 5, for example, to view the SystemReport online.

19. For this example, type a 2 under the Opt column to change the output queuefor the System Report (the QPPTSYSR file). In this example, you might want tomove the report to an output queue that has an active writer, so the reportprints on the device the writer is associated with.

20. Type the new output queue name. To do this, type OUTQ(outqname) on thecommand entry line.

21. Press the Enter key. The System Report prints when a device is available.


Why Performance Reports May Seem InconsistentPerformance Tools pulls data from the various performance monitor database filesto create the performance reports. As a result, some values in the report's columnsare inconsistent between reports where it seems like they should match.

For example, the Communications Summary report (System Report) uses theQAPMJOBS file. QAPMJOBS file records batch use for jobs that are not related tocommunications. As a result, batch use of a line or TCP use does not show up inthe QAPMJOBS file. Because the QAPMJOBS file only shows transactions for jobs,and the communications line connected to the job is classified as interactive, nobatch use for communications is recorded by the QAPMJOBS file.

Note: The Communications Summary (System Report) only shows interactiveresults. Besides this section only takes information from the records whichhave data in the line description, communications line name, or in the sec-ondary line description, pass-through and emulation (only "virtual" type con-nection).

Another example is the IOP Utilizations Component report section, which uses theQAPMCIOP file. This file has field values for the idle loop count and the idle looptime. These values make up the data that is used to calculate the IOP utilizationvalue that shows up in this report. The IOP utilization result is just the percentageof CPU used in the IOP. When the communication IOP utilization shows a valuedifferent than 0, it does not necessarily mean that the IOP is doing any data trans-fers, it may just be overhead of an active line.

Another confusing example is how Client Access transactions show up on theSystem report. Client Access jobs show up in the interactive category, but someClient Access functions show up in batch or evoke categories. In addition, lots ofClient Access activity never become a real job. This can have some effect on trans-action counting. For example, the Interactive Workload System report sectionshows the different job types (Interactive, Client Access, DDM Server, Passthru,and so on). Each of these job types has a column with the corresponding total oftransactions for each one. This report pulls data from the QAPMSYS file, where theperformance monitor assigns different classifications of data for the different jobtypes. The performance monitor code checks for certain attributes and flags on thesystem to determine which types they are. For example, Client Access jobs areidentified by a flag. The flag is turned on when a Client Access application sets aClient Access bit in the work control block (WCB). The performance monitor thenrecognizes this job as Client Access and classifies it as such.

As a result, the number of transactions that show up on the Interactive Workloadsection differs from the number of transactions that show up on the Communi-cations Summary System report section. The Communications Summary Systemreport section only shows the number of interactive transactions on the communi-cation line over a period of time (which includes Client Access transactions). Thetransactions that are unrelated to the communications line do not show up in thissection of the report.

Performance Tools reports show the data based on the contents of the perform-ance monitor database files. In some cases, this causes slight inconsistenciesbetween reports.


| Table 7-1 on page 7-16 identifies the type of workload that is running on the| system and shows how the System Report (SYS), the Component Report (CPT),| and the Transaction Report (TNS) report the job type for the QAPMJOBS database| file.

| The abbreviations for the field value headings include the following:

| � JBTYPE - job type

| � JBSTYP - job subtype

| � JBPTTF - target pass-through flag

| � JBPTSF - source pass-through flag

| � JBEAF - emulation active flag

| � JBPCSF - Client Access flag

| � JBDDMF - target DDM job flag

| The Desc column identifies the type of workload that is running on the system. This| column contains a number that is associated with the following descriptions:

| � 1 - 5250 twinaxial data link control, remote workstation support, or 3270 remote| attach

| � 2 - APPC 5250 emulation (Client Access)

| � 3 - Target APPC display station pass-through

| � 4 - Target TELNET 5250

| � 5 - Source pass-through

| � 6 - Target distributed data management (DDM)

| � 7 - APPC router

| � 8 - Host server ("Client Access"), pre-started job

| � 9 - APPC, batch evoke

| � 10 - Normal batch job

| � 11 - Auto start job

| � 12 - Subsystem monitor

| � 13 - Spool writer

| � 14 - Spool print driver

| � 15 - Other system jobs

| � 16 - typical secondary thread

| You can find the descriptions for the one-character and two-character abbreviations| used in the table under the Typ column description at the end of this chapter.

| Table 7-1 (Page 1 of 2). Job Types

| Desc| Jobtype Listed in| Reports| QAPMJOBS Field Values 1

| SYS| CPT| TNS| JBTYPE| JBSTYP| JBPTTF| JBPTSF| JBEAF| JBPCSF| JBDDMF

| 1| I2| I| I| I| b| 0| 0| 0| 0| 0


| Table 7-1 (Page 2 of 2). Job Types

| Desc| Jobtype Listed in| Reports| QAPMJOBS Field Values 1

| SYS| CPT| TNS| JBTYPE| JBSTYP| JBPTTF| JBPTSF| JBEAF| JBPCSF| JBDDMF

| 2| CA2,3| C| I| I| b| 1| 0| 0| 1| 0

| 3| PT2,4| P| I| I| b| 1| 0| 0| 0| 0

| 4| PT2,4| P| I| I| b| 1| 0| 0| 0| 0

| 5| NA| NA| NA| NA| b| 0| 1| 0| 0| 0

| 6| DDM| server5| D| BE| B| E| 1| 1| 0| 0| 1

| 7| Batch5| E| BE| B| E| 0| 0| 0| 1| 0

| 8| Batch5| C| BJ| B| J| 0| 0| 0| 1| 0

| 9| Batch5| C| B| B| b| 0| 0| 0| 0| 0

| 10| Batch5| B| B| B| b| 0| 0| 0| 0| 0

| 11| Auto| start5| A| A| A| b| 1| 1| 0| 0| 0

| 12| System5| M| M| M| b| 0| 0| 0| 0| 0

| 13| Spool5| W| W| W| b| 0| 0| 0| 0| 0

| 14| Spool5| W| WP| W| P| 0| 0| 0| 0| 0

| 15| Batch5| S| S| S| b| 0| 0| 0| 0| 0

| 16| Batch5| B| BD| B| D| 0| 0| 0| 0| 0

| 1 A lowercase b indicates the field is blank.

| 2 Interactive workload

| 3 CA represents Client Access

| 4 PT represents pass-through

| 5 Non-interactive workload

System Report

Printing the System ReportPrint the System Report using the Print System Report (PRTSYSRPT) command,or select option 1 (System report) on the Print Performance Reports display.

What Is the System Report?The System Report is an overview of system operation during the data collectionperiod. Produce and save this report periodically so you have a record of the work-load and resource utilization (for example, how your system meets the users’ needsand at what cost). Use the reports to see what processing trends are developing,and to project when you might need to make application, system, or operationalchanges to accommodate changing workloads.

Every System Report includes the Workload, Resource Utilization, and ResourceUtilization Expansion sections. However, the Storage Pool Utilization, Disk Utiliza-


tion, and Communications Summary sections are omitted when certain report cate-gories are selected on the Select Categories for Report display. Table 7-2 onpage 7-18 shows the categories that cause these sections to be omitted.

Table 7-2. Report Categories that Cause System Report Sections to be Omitted

Report Category Report Section Omitted

Time Interval None

Job Storage Pool UtilizationDisk UtilizationCommunications Summary

User ID Storage Pool UtilizationDisk UtilizationCommunications Summary

Subsystem Storage Pool UtilizationDisk UtilizationCommunications Summary

Pool Disk UtilizationCommunications Summary

Communications line Storage Pool UtilizationDisk Utilization

Control unit Storage Pool UtilizationDisk Utilization

Functional area Storage Pool UtilizationDisk UtilizationCommunications Summary

For samples of each section of the System Report, see “Sample System Reports”on page 7-20.

For definitions of specific columns in the reports, see “Performance ReportColumns” on page 7-102.

Workload

Interactive WorkloadThe first part of the Workload section shows the interactive workload of the system.

See the sample report shown in Figure 7-2 on page 7-20.

Noninteractive WorkloadThe second part of the Workload section shows the noninteractive workload of thesystem.



Resource UtilizationThe Resource Utilization section shows the average resource utilization per interac-tive transaction. Use it to note changes in resource utilization from one measure-ment period to another and to determine resource utilization trends.

Resource Utilization (First Part)See the sample report shown in Figure 7-4 on page 7-21.

Resource Utilization (Second Part)See the sample report shown in Figure 7-5 on page 7-21.

Resource Utilization ExpansionThe Resource Utilization Expansion section gives the average resource use pertransaction by job type.

Resource Utilization Expansion (First Part)See the sample report shown in Figure 7-6 on page 7-21.

Resource Utilization Expansion (Second Part)The second part of the Resource Utilization Expansion section contains CPU andI/O utilization information.


Storage Pool UtilizationUse the Storage Pool Utilization section of the System Report, along with theguidelines provided in the Work Management book, to help you set the storagepool size and activity level.


Disk UtilizationThe Disk Utilization section of the System Report shows the utilization for eachdisk.


Communications SummaryThe Communications Summary section of the System Report shows the use of thecommunications lines and processors.

See the sample report in Figure 7-10 on page 7-23.

Note: The line utilization in the system report shown in Figure 7-10 on page 7-23does not correspond with the “Component Report: IOP Utilizations” for anIOP running SDLC remote work stations. A low SDLC line utilization valueresults in a high IOP utilization value due to polling. However, because theSDLC line transfers a larger percentage of user data, an IOP polls less fre-quently. Usually this results in an overall increase in IOP utilization. In somecases, though, especially when the SDLC lines have a low utilization, thisresults in an overall decrease in IOP utilization. Thus, a high IOP utilizationvalue is significant only if at least one of the attached SDLC lines is active.


Report Selection Criteria

Report Selection Criteria (Selected Start/End Time/Date)The Selected Start/End Time/Date Criteria section gives the range of of time thereport must generate. If you use no SELECT Start/End Time/Date, the message NoSelect Time/Date were chosen appears.

A sample report is shown in Figure 7-13 on page 7-25.

Report Selection Criteria (Date/Time Intervals)The Selected Date/Time Intervals Criteria section gives the interval number Dateand time of the intervals selected to generate the report. If you use no SELECTDate/Time Intervals, the message All Intervals were chosen appears.


Report Selection Criteria (Select Parameters)The Report Selection Criteria section gives the selection values you chose toproduce the report. If you use no SELECT parameters, the message No Select

parameters were chosen appears.


Report Selection Criteria (Omit Parameters)If you did not use OMIT parameters, the message No Omit parameters were

chosen appears.

See the sample report showing the OMIT parameters on the Report Selection Cri-teria section of the System Report in Figure 7-12 on page 7-24.

Sample System ReportsSee “Performance Report Columns” on page 7-102 for an alphabetized list con-taining definitions for each column in the reports.

Workload Section: Interactive Workload–Sample

| System Report 9/15/98 1ð:5ð:4ð

| Workload Page ððð1


| Member . . . : ONE Model/Serial . : 436-21ð6/1ð-1ðBDA Main storage . . : 256.ð M Started . . . . : ð9/1ð/98 ðð:16:22

| Library . . : DFLBUGDL1 System name . . : ABSYSTEM Version/Release : 4/ 2.ð Stopped . . . . : ð9/1ð/98 23:5ð:ð8

| QPFRADJ . . . : 2 QDYNPTYSCD . . : 1

| Interactive Workload

| Job Number Average Logical DB -------- Printer ---------- Communications MRT

| Type Transactions Response I/O Count Lines Pages I/O Count Max Time

| ------------- ---------------- -------- ----------------- ------------- ---------- -------------- --------

| Interactive 28 2.96 188 ð ð ð ð

| PassThru 2ð1 .64 481 1,ð4ð 23 ð ð

| Total 229 669 1,ð4ð 23 ð

| Average .93

Figure 7-2. Workload Section: Interactive Workload


Workload Section: Noninteractive Workload–Sample

| Non-Interactive 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 256 13,859 175,589 3,291 ð 2.ð3ð6 .1

| Spool 1 155 ð ð ð .ð19ð .ð

| AutoStart 3 12,743 ð ð ð .ðð14 .1

| Total 26ð 26,757 175,589 3,291 ð

| Average 1.ð525 .3

| Total CPU Utilization . . . . . . : 99.9

Figure 7-3. Workload Section: Noninteractive Workload

Resource Utilization (First Part)–Sample


| Resource Utilization Page ððð2




| -------------------- Average Per Transaction --------------------

| Sync Async

| Job Response CPU Disk Disk DB

| Type Seconds Seconds I/O I/O I/O

| -------------- -------- ------- ------- -------- ---------

| Interactive 2.96 .21 134.2 14.ð 6.7

| PassThru .64 .ð9 36.2 2.9 2.3

| Average .93 .1ð 48.2 4.2 2.9

Figure 7-4. Resource Utilization

Resource Utilization (Second Part)–Sample

| Tns Active -------------------------- Disk I/O Per Second ---------------------------

| Job CPU /Hour Jobs Per Total --------- Synchronous -------- -------- Asynchronous --------

| Type Util Rate Interval I/O DBR DBW NDBR NDBW DBR DBW NDBR NDBW

| -------------- ---- -------------- -------- ------- ----- ----- ----- ----- ----- ----- ----- -----

| Interactive .ð 1 1 .ð .ð .ð .ð .ð .ð .ð .ð .ð

| PassThru .ð 8 1 .ð .ð .ð .ð .ð .ð .ð .ð .ð

| Average .ð 9 11 .1 .ð .ð .1 .ð .ð .ð .ð .ð

Figure 7-5. Resource Utilization

Resource Utilization Expansion (First Part)–Sample


| Resource Utilization Expansion Page ððð3




| -------------------------------------------- Average Per Transaction --------------------------------------------

| --------------------- Physical Disk I/O ------------------------ -------- Logical --------- -- Communications --

| Job --------- Synchronous --------- -------- Asynchronous --------- ----- Data Base I/O ------ I/O

| Type DBR DBW NDBR NDBW DBR DBW NDBR NDBW Read Write Other Get Put

| -------------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ----- -----

| Interactive 3.71 1.5ð 122.14 6.92 .75 1.71 .ð7 11.5ð 5.92 .28 .5ð .ð .ð

| PassThru .35 .33 33.19 2.33 .59 .2ð .ð7 2.ð2 2.27 .11 .ðð .ð .ð

| Average .76 .47 44.ð7 2.89 .61 .38 .ð7 3.18 2.72 .13 .ð6 .ð .ð

Figure 7-6. Resource Utilization Expansion


Resource Utilization Expansion (Second Part)–Sample

| Job CPU Cum ------- Disk I/O ------- ----- CPU Per I/O ------ -- DIO /Sec --

| Priority Type Util Util Sync Async Sync Async Sync Async

| -------- -------------- ---- ----- ----------- ----------- ---------- ---------- ----- -----

| ððð Batch .ð .ð 7,238 3,8ð1 .ðð52 .ðð99 .ð .ð

| System 66.6 66.6 8,262 67,3ð4 6.8427 .8399 .ð .7

| ðð5 Batch .ð 66.7 8,269 2,134 .ðð77 .ð299 .ð .ð

| ðð9 System .ð 66.7 12 ð .ððð5 .ðððð .ð .ð

| ð1ð Interactive .ð 66.7 157 ð .ððð4 .ðððð .ð .ð

| ð16 System .ð 66.7 15 ð .ððð4 .ðððð .ð .ð

| ð19 PassThru .ð 66.7 572 79 .ðð28 .ð2ð7 .ð .ð

| ð2ð Interactive .ð 66.7 3,6ð3 393 .ðð16 .ð15ð .ð .ð

| Client Access .ð 66.7 ð ð .ðððð .ðððð .ð .ð

| PassThru .ð 66.8 6,7ð8 5ð4 .ðð25 .ð341 .ð .ð

| Batch .ð 66.8 2,ð73 323 .ð377 .2425 .ð .ð

| AutoStart .ð 66.8 ð ð .ðððð .ðððð .ð .ð

| .

| .

| .

| Total 1,1ðð,764 23ð,28ð 12.9 2.7

Figure 7-7. Resource Utilization Expansion (Second Part)

Storage Pool Utilization–Sample


| Storage Pool Utilization Page ððð5




| ---------- Avg Per Second --------- ---- Avg Per Minute -----

| Pool Expert Size Act CPU Number Average ------ DB ------ ---- Non-DB ---- Act- Wait- Act-

| ID Cache (K) Lvl Util Tns Response Fault Pages Fault Pages Wait Inel Inel

| ---- ------- ----------- ----- ----- ----------- -------- ------- ------- ------- ------- -------- ------- -------

| \ð1 ð 58,112 ð 66.6 ð .ðð .ð .ð .6 .6 5 ð ð

| \ð2 ð 175,2ð4 44 33.2 1 2.ðð .ð .ð 2.6 8.8 241 ð ð

| ð3 ð 2,62ð 1 .ð ð .ðð .ð .ð .ð .ð ð ð ð

| \ð4 ð 26,2ð8 18 .ð 228 .92 .ð .ð .ð .1 ð ð ð

| Total 262,144 99.9 229 .ð .ð 3.3 9.6 247 ð ð

| Average

| .93

| \ The pool did not exist for all of run, or the size or activity level

| changed during run.

| Pool ID -- Pool identifier

| Expert Cache -- Method used by the system to tune the storage pool

| Size (K) -- Size of the pool in kilobytes at the time of the first sample interval

| Act Lvl -- Activity level at the time of the first sample interval

| CPU Util -- Percentage of available CPU time used. This is the average of all processors

| Number Tns -- Number of transactions processed by jobs in this pool

| Average Response -- Average transaction response time

| DB Fault -- Average number of data base faults per second

| DB Pages -- Average number of data base pages per second

| Non-DB Fault -- Average number of non-data base faults per second

| Non-DB Pages -- Average number of non-data base pages per second

| Act-Wait -- Average number of active to wait job state transitions per minute

| Wait-Inel -- Average number of wait to ineligible job state transitions per minute

| Act-Inel -- Average number of active to ineligible job state transitions per minute

Figure 7-8. Storage Pool Utilization

Disk Utilization–Sample


| System Report 11/11/98 8:2ð:ð8

| Disk Utilization Page ððð6

| STD I, B, then java/threads

| Member . . . : Q98315ð757 Model/Serial . : 51ð-2144/1ð-16CAD Main storage . . : 512.ð M Started . . . . : 11/11/98 ð7:58:ð1

| Library . . : PFRRES42 System name . . : ABSYSTEM Version/Release : 4/ 2.ð Stopped . . . . : 11/11/98 ð8:18:43

| Unit Size IOP IOP Dsk CPU ASP --Percent-- Op Per K Per - Average Time Per I/O --

| Unit Name Type (M) Util Util

| Name ID Full Util Second I/O Service Wait Response

| ---- ---------- ---- ------- ---- ------------ ------- --- ---- ---- --------- --------- ------- ------

| --------

| ððð1A DDð1ð 66ð6 1,967 1.8 CMBð1 .ð ð1 77.2 1.8 1.43 5.6 .ð125 .ðð14 .ð139

| ððð1B DDðð2 66ð6 1,967 1.8 CMBð1 .ð ð1 77.2 1.5 1.64 5.4 .ðð91 .ððð6 .ðð97

| ððð3 DDðð3 66ð6 1,475 6.5 SIð3 .ð ð1 74.6 .4 1.86 6.5 .ðð21 .ðððð .ðð21

| ððð4 DDðð4 66ð6 1,475 6.5 SIð3 .ð ð1 74.3 .9 2.27 5.8 .ðð39 .ððð4 .ðð43

| ððð5 DDðð5 66ð6 1,475 6.5 SIð3 .ð ð1 74.6 .8 1.65 6.ð .ðð48 .ðððð .ðð48

| ððð6 DDðð6 66ð6 1,475 6.5 SIð3 .ð ð1 74.1 .8 2.45 6.ð .ðð32 .ðððð .ðð32

| ððð7 DDð18 66ð7 3,145 6.5 SIð3 .ð ð1 74.ð 2.ð 7.9ð 6.1 .ðð25 .ððð1 .ðð26

| ððð8 DDð2ð 66ð7 3,145 6.5 SIð3 .ð ð1 74.4 .6 2.11 6.ð .ðð28 .ððð5 .ðð33

| ððð9 DDð16 66ð7 3,145 6.5 SIð3 .ð ð1 74.ð 5.ð 2ð.88 6.2 .ðð23 .ððð4 .ðð27

| ðð1ð DDð11 66ð7 3,145 6.5 SIð3 .ð ð1 74.2 .5 1.72 6.7 .ðð28 .ðððð .ðð28

| Total 22,414

| Average 74.8 1.4 4.39 6.1 .ðð31 .ððð5 .ðð36


| Unit Name -- Disk arm resource name

| Type -- Type of disk

| Size (M) -- Disk space capacity in millions of bytes

| IOP Util -- Percentage of utilization for each Input/Output Processor

| IOP Name -- Input/Output Processor resource name

| Dsk CPU Util -- Percentage of Disk Processor Utilization

| ASP ID -- Auxiliary Storage Pool ID

| Percent Full -- Percentage of disk space capacity in use

| Percent Util -- Average disk operation utilization (busy)

| Op per Second -- Average number of disk operations per second

| K Per I/O -- Average number of kilobytes (1ð24) transferred per disk operation



| Average Response Time -- Average disk response time per I/O operation

Figure 7-9. Disk Utilization

Communications Summary–Sample

| System Report 5/19/96 12:ð3:48

| Communications Summary Page ððð6


| Member . . . : CAJð5ð3 Model/Serial . : 51ð-2144/1ð-ð8BCD Main storage . . : 384.ð M Started . . . . : ð5/ð3/96 14:59:32

| Library . . : QPFRDATA System name . . : ABSYSTEM Version/Release : 3/ 7.ð Stopped . . . . : ð5/ð3/96 15:ð4:31

| IOP Name/ Line Avg Max Active Number Average ------ Bytes Per Second ----

| Line Protocol Speed Util Util Devices Transactions Response Received Transmitted

| -------------------- -------- --------- ---- ---- ------- ------------ -------- ---------- -----------

| CCð1 (2619)

| TRLINLð5 TRLAN 16ððð.ð ð ð ð ð .ðð .ð .ð

| IOP Name/Line -- IOP Resource name and model number, Line ID

| Protocol -- Line protocol (SDLC, ASYNC, BSC, X25, TRLAN, ELAN, IDLC, DDI, FRLY)

| Line Speed -- Line speed (1ððð bits per second)

| (For IDLC this is the maximum over the measurement)

| Avg Util -- Average line utilization

| Max Util -- Maximum line utilization in all measurement intervals

| Active Devices -- Average number of active devices on the line

| Number Transactions -- Number of transactions

| Average Response -- Average system response (service) time (seconds)

| Bytes /Sec Received -- Average number of bytes received per second

| Bytes /Sec Transmitted -- Average number of bytes transmitted per second

Figure 7-10. Communications Summary


System Report Selection Criteria: Select Parameters–Sample


Selected Start/End Time/Date:

- No Select Time/Date were chosen.

Selected Date/Time Intervals:

- All Intervals were chosen.

Select Parameters

Pools - ð1 ð2 ð3 ð4 ð5 ð6 ð7 ð8 ð9 1ð 11 12 13 14 15 16

Jobs - ð12345/Useridwxyz/Jobname123

987654/Useridabcd/Jobname456

User IDs - User1 User2 User3 User4 User5 User6

User7 User8 User9 User1ð User11 User12

Subsystems - Subsystem1 Subsystem2 Subsystem3 Subsystem4 Subsystem5 Subsystem6

Subsystem7 Subsystem8 Subsystem9 Subsystema Subsystemb Subsystemc

Communications Lines - Line1 Line2 Line3 Line4 Line5 Line6

Line7 Line8 Line9 Line1ð Line11 Line12

Control Units - Ctlr1 Ctlr2 Ctlr3 Ctlr4 Ctlr5 Ctlr6

Ctlr7 Ctlr8 Ctlr9 Ctlr1ð Ctlr11 Ctlr12

Functional Areas - Accounting Payroll Research

Development ProjectX MrNolansStaff

- No Select parameters were chosen.

Figure 7-11. Report Selection Criteria: Select Parameters

System Report Selection Criteria: Omit Parameters–Sample





- All Intervals were chosen.

Omit Parameters














- No Omit parameters were chosen.

Figure 7-12. Report Selection Criteria: Omit Parameters


Report Selection Criteria: Selected Start/End Time/Date–Sample


Start Date/Time: 12/27/95 15:13:42

End Date/Time: 12/27/95 17:38:42


Figure 7-13. Report Selection Criteria: Start/End Time/Date

Report Selection Criteria: Date/Time Intervals–Sample




Interval

Number Date Time

2 12/27 16:13

3 12/27 17:13

4 12/27 17:38

Figure 7-14. Report Selection Criteria: Date/Time Intervals

Component Report

Printing the Component ReportUse the Print Component Report (PRTCPTRPT) command, or select option 2(Component report) on the Print Performance Reports display.

What Is the Component Report?This series of reports, like the System Report, is produced from the sample datayou collect with the STRPFRMON command. It expands on the detail for eachcomponent of system performance shown on the System Report. Data is shown foreach sample interval, or in some cases, for each job. Because the report can belengthy, you may want to use the Select Time Intervals display when requestingthis report to select only those measurement intervals of interest to you.

Note: The Component Report does not show information for Client Accessdevices for the Job Workload Activity, IOP Utilizations, and the RemoteWork Stations – Response Time Buckets sections.

For samples of each section of the Component Report, see “Sample ComponentReports” on page 7-29.


Component Interval ActivityThe Component Interval Activity section of the Component Report gives the use ofthe processing unit, disks, and pools at various time intervals.



Job Workload ActivityThe Job Workload Activity section of the Component Report gives the total numberof transactions, the transactions per hour, the average response time, the numberof disk operations, the number of communications operations, the number of PAGfaults, the number of arithmetic overflows, and the number of permanent writes foreach job.


Storage Pool ActivityThe Storage Pool Activity section of the Component Report gives detailed informa-tion for each storage pool. This information includes the storage pool activity level,as well as the number of transactions processed in each pool.

The Pool Identifier, shown at the top of the Storage Pool Activity section, specifiesthe storage pool identifier (the value can be from 01 through 16). A separateStorage Pool Activity section exists for each pool that was in use during the meas-urement period and was selected on the PRTCPTRPT command.


Disk ActivityThe Disk Activity section of the Component Report gives the average disk activityper hour and the disk capacity for each disk.


Input/Output Processor (IOP) UtilizationsThe IOP Utilizations section of the Component Report gives the input/outputprocessor (IOP) utilization for communications, direct access storage devices(DASDs), multifunction (DASD, communication, and local work stations). Con-sistent utilization, at or above the threshold value of the DASD IOP and multifunc-tion IOP, will affect system performance and cause longer response times or lessthroughput.

See the utilization guidelines and thresholds in BEST/1 Capacity Planning Toolbook for a list of threshold values.


Note: The total for the I/O processor utilization oftentimes does not match the sumof the three columns (IOP Processor Util Comm, IOP Processor Util LWSC,and IOP Processor Util DASD). This mismatch is caused by the utilization ofother small components, such as system time.

Local Work StationsThe Local Work Stations section of the Component Report gives the utilization ofeach controller, the range of response times for each device, and the averageresponse time for each device.


The response time intervals are set up on the system STRPFRMON command.The values for the response times may vary depending on the values you use inthe command.


Remote Work StationsThe Remote Work Stations section of the Component Report gives the range ofresponse times for each device on the displayed controllers and the averageresponse time for each device.


Note: This section appears only if 5494 remote work station data is included in thedata collection.


Exception Occurrence Summary and Interval CountsThe Exception Occurrence Summary and Interval Counts section of the ComponentReport gives the number of exceptions that occurred and the frequency of theseexceptions.

In some cases these exception counts can be high even under normal systemoperation.


Database Journaling SummaryThe Database Journaling section of the Component Report provides informationabout the journal activity on the system. This information is helpful in understandingthe trade-offs between the following:

� The affects of extensive journaling.

� The time required to rebuild access paths during an IPL following an abnormalsystem end.

For more information on journaling, see the Backup and Recovery book.

The Database Journaling section summarizes the journaling activity resulting fromuser-initiated activities and from system-managed access-path protection (SMAPP)support. This includes the following information:

� The number of start and stop journaling operations performed.

� The number of journal entry deposits made on behalf of objects for which auser started journaling.

� The number of journal entry deposits made on behalf of objects for which thesystem started journaling.

The report contains the following fields for the number of journal deposits resultingfrom system-initiated journaling:


� The total number of deposits.

� A subset of the total number of deposits made to journals created by a user.

The remaining journal entries were deposited to internal system journals.Internal system journals are created and maintained by the system.

As journal entries are deposited to the journals, the system attempts to group theseentries into larger bundles to provide more efficient I/O. The number of bundleswritten to user-created journals can be compared to the number of bundles writtento system-created journals. This proportion indicates how efficiently the system per-forms I/O to the journal receivers.

When SMAPP is active on the system, the following information is also available:

� The number of exposed access paths.

� An estimate of the time in minutes required to rebuild the exposed accesspaths following an abnormal system end.

� The number of adjustments made by the system to internal journal tuningtables.

Note: The estimated rebuild time is rounded to the nearest full minute. Theestimate is available only on a system-wide basis, not by auxiliarystorage pool (ASP), even though access path recovery times may bespecified on an ASP basis.

The number of exposed access paths and their estimated rebuild exposure doesnot include the following:

� Access paths that are being journaled by a user

� Access paths that were created with the *REBLD maintenance option

See the Backup and Recovery book for more SMAPP considerations.

The estimated rebuild exposure is calculated two ways:

� Current estimated system exposure

� Estimated exposure if the system was not journaling any of the exposed accesspaths

These calculated values will be the same if the system access path recovery timeis set to *NONE. These values will also be the same if the system access pathrecovery time is set to a time greater than the current estimated exposure.


Report Selection CriteriaThe Report Selection Criteria section of the Component Report gives the selectionvalues you chose to produce the report.

If you did not use the SELECT parameters, the message No Select parameters

were chosen appears. If you did not use OMIT parameters, the message No Omit

parameters were chosen appears.



Sample Component ReportsSee “Performance Report Columns” on page 7-102 for an alphabetized list con-taining definitions for each column in the reports.

Component Interval Activity–Sample

| Component Report 11/11/98 8:2ð:28

| Component Interval Activity Page 1




| --- Disk I/O --- High Pool Excp

| Itv Tns Rsp DDM ---- CPU Utilization --- --- Per Second -- -Utilization- --- Faults/Sec -- per

| End /Hour /Tns I/O Total Inter Batch Sync Async Disk Unit Mch User ID Second

| ----- ----------- ----- ---------- ------ ----- ----- ------- ------- ---- ---- --- ---- -- -------

| ð8:ð3 314 2.ð3 ð 99.9 .5 98.4 4.8 2.8 2 ððð4 ð 3 ð2 7ð

| ð8:ð8 6ð9 1.94 ð 98.8 .4 97.ð 9.2 24.5 5 ððð9 ð ð ð2 81,846

| ð8:13 95 4.25 ð 98.2 .5 96.2 12.3 49.1 8 ððð9 ð 1 ð2 164,433

| ð8:18 348 .86 ð 98.4 .9 95.6 15.2 47.5 8 ððð9 ð 3 ð4 15ð,189

| ð8:18 9ð .ðð ð 99.4 .ð 98.ð 3.2 39.6 5 ððð9 ð ð ð2 11,932

| Itv End -- Interval end time (hour and minute)

| Tns /Hour -- Number of interactive transactions per hour

| Rsp /Tns -- Average interactive transaction response time in seconds

| DDM I/O -- Number of DDMs

| Total CPU Utilization -- Percentage of available CPU time used by interactive and batch jobs. This is the average

| of all processors

| Inter CPU Utilization -- Percentage of available CPU time used by interactive jobs. This is the average of all processors

| Batch CPU Utilization -- Percentage of available CPU time used by batch jobs. This is the average of all processors

| Sync Disk I/O Per Sec -- Average synchronous disk I/O operations per second

| Async Disk I/O Per Sec -- Average asynchronous disk I/O operations per second

| High Disk Utilization -- Percent of utilization of the most utilized disk arm during this interval

| High Utilization Unit -- Disk arm which had the most utilization during this interval

| Mch Pool Faults/Sec -- Average number of machine pool faults per second

| User Pool Faults/Sec -- Average number of user pool page faults per second,

| for the user pool with highest fault rate during this interval

| Pool ID -- User pool that had the highest page fault rate

| Excp -- Total number of program exceptions that occurred

Figure 7-15. Component Interval Activity

Job Workload Activity–Sample



| Job Workload Activity Page 2




| T P

| Job User Job y t CPU Tns ---------- Disk I/O --------- Cmn PAG Arith Perm

| Name Name Number p Pl y Util Tns /Hour Rsp Sync Async Logical I/O Fault Ovrflw Write

| ---------- ---------- ------ -- -- -- ------ ------- --------- ------- --------- --------- --------- --------- ----- ------- ------

| AM-ANSMGR L ð1 68 .ððð ð ð .ððð ð ð ð ð ð ð ð

| ASJ1LU QSNADS ð23ð84 B ð2 4ð .ððð ð ð .ððð 1 ð ð ð 1 ð ð

| CENTRAL QGATE ð23ð85 B ð2 4ð .ððð ð ð .ððð 4 ð ð ð 4 ð ð

| CFINTð1 L ð1 ðð .949 ð ð .ððð ð ð ð ð ð ð ð

| CHAINBCH QSYS ð234ð2 M ð5 ðð .ððð ð ð .ððð ð ð ð ð ð ð ð

| CHAINUPCW QPGMR ð234ð3 B ð5 5ð 31.698 ð ð .ððð 43ð2 192ð8 37ð73ð ð ð 2ð8385 11ð91

| CHAINUPCW QPGMR ð234ð4 B ð5 5ð 3ð.857 ð ð .ððð 43ð4 19ð12 357318 ð ð 1995ð3 11247

| DBDOU L ð1 2ð .ððð ð ð .ððð 5 ð ð ð ð ð ð

| DBIOðð L ð1 2ð .ððð ð ð .ððð ð ð ð ð ð ð ð

| .

| .

| .

| JO-EVALUAT P ð2 ðð .ð35 ð ð .ððð 3 382 ð ð ð ð ð

| JO-TUNING- P ð2 ðð .ððð ð ð .ððð ð ð ð ð ð ð ð

| .

| .

| .

| QINTER QSYS ð23ð38 M ð2 ðð .ð13 ð ð .ððð 146 19 ð ð 32 ð 31

| QIWVPPJT QUSER ð2314ð B ð2 2ð .ððð ð ð .ððð 5 ð ð ð 4 ð ð

| QJOBSCD QSYS ð22993 S ð2 ðð .ððð ð ð .ððð ð ð ð ð ð ð ð

| QJVACMDSRV COOK ð23416 B ð4 26 4.113 ð ð .ððð 575 51 ð ð 1 ð 117

| QJVACMDSRV COOK ð23417 B ð4 26 4.14ð ð ð .ððð 565 51 ð ð 1 ð 117

| QJVACMDSRV GLMS ð23264 B ð4 26 15.496 ð ð .ððð 14ð 1ð ð ð 6 ð 44

| QLUR QSYS ð22995 S ð2 ðð .ððð ð ð .ððð ð ð ð ð ð ð ð

| QLUS QSYS ð22982 S ð2 ðð .ððð ð ð .ððð ð ð ð ð ð ð ð

| QLZPSERV QUSER ð23ð53 C ð2 2ð .ððð ð ð .ððð 6 ð ð ð 1 ð ð

| QMSF QMSF ð23ð78 B ð2 35 .ððð ð ð .ððð 6 ð ð ð 5 ð ð

| QNETWARE QSYS ð23ð77 B ð2 5ð .ðð2 ð ð .ððð 4 ð ð ð 2 ð ð

| QNFTP QSNADS ð2311ð B ð2 4ð .ððð ð ð .ððð 5 ð ð ð 4 ð ð

| QNMAPINGD QUSER ð23ð47 B ð2 25 .ððð ð ð .ððð 4 ð ð ð 1 ð ð

| QNMAREXECD QUSER ð23ð49 B ð2 25 .ððð ð ð .ððð 3 ð ð ð 1 ð ð

| QNNDIRQS QNOTES ð23ð55 B ð2 35 .ðð1 ð ð .ððð 3 ð ð ð 2 ð ð

| .

| .

| .

| QPADEVðð16 COOK ð23399 P ð4 2ð .ð52 19 69 .1ð5 118 2ð 14 ð ð ð 12

| QPADEVðð16 COOK ð23414 P ð4 2ð .473 9 133 .111 57 9 ð ð ð ð 21

| QPADEVðð17 COOK ð23398 P ð4 2ð .ð61 35 127 5.828 134 17 1ð ð ð ð 25

| QPADEVðð17 COOK ð23415 P ð4 2ð .481 9 137 .111 43 7 ð ð 1 ð 16

| QPADEVðð19 GLMS ð23262 P ð4 2ð .ð8ð 38 11ð .ð78 38 4 ð ð 2 ð 5

| QPADEVðð2ð GLMS ð23291 P ð4 2ð .ðð8 ð ð .ððð 18 3 ð ð 4 ð 5

| QPASVRP QSYS ð23ð26 B ð2 5ð .ððð ð ð .ððð 5 ð ð ð 2 ð ð

| QPASVRS QSYS ð23ð66 B ð2 3ð .ððð ð ð .ððð 2 ð ð ð 2 ð ð

| .

| .

| .

| Column Total Average

| --------------------------- ---------------- ----------------

| CPU Util 98.787

| Tns 115

| Tns /Hour 333

| Resp 1.834

| Sync Disk I/O 13,5ð8

| Async Disk I/O 39,4ð7

| Logical Disk I/O 728,485

| Cmn I/O ð

| PAG Fault 115

| Arith Ovrflw 4ð7,888

| Perm Write 25,444

Figure 7-16. Job Workload Activity


Storage Pool Activity–Sample


| Storage Pool Activity Page 15




| Pool identifier . . . : ð5 Expert Cache . . . : 3

| Pool Avg ---------- Avg Per Second ----------- ----- Avg Per Minute -----

| Itv Size Act Total Rsp CPU ------ DB ------ ----- Non-DB ----- Act- Wait- Act-

| End (KB) Level Tns Time Util Faults Pages Faults Pages Wait Inel Inel

| ----- ----------- ----- ----------- ----- ---- ------- ------ ------- ------ ------ ------ ------

| ð8:ð3 66,ððð 3 ð .ðð 5.2 .1 2 .ð ð ð ð ð

| ð8:ð8 66,ððð 3 ð .ðð 5ð.8 .4 11 .ð ð ð ð ð

| ð8:13 66,ððð 3 ð .ðð 95.8 .ð 23 .ð ð ð ð ð

| ð8:18 66,ððð 3 ð .ðð 93.4 .ð 23 .ð ð ð ð ð

| ð8:18 66,ððð 3 ð .ðð 95.9 .ð 34 .ð ð ð ð ð

| .

| .

| .


| Pool Size (KB) -- Initial pool size in kilobytes (1ð24)

| Act Level -- Initial pool activity level

| Total Tns -- Number of transactions processed in this pool

| Avg Resp Time -- Average transaction response time

| CPU Util -- Percentage of available CPU time used by the job. This is the average of all processors

| DB Faults -- Database faults per second

| DB Pages -- Database pages per second

| Non-DB Faults -- Nondatabase faults per second

| Non-DB Pages -- Nondatabase pages per second

| Act-Wait -- Number of active-to-wait transitions per minute

| Wait-Inel -- Number of wait-to-ineligible transitions per minute

| Act-Inel -- Number of active-to-ineligible transitions per minute

Figure 7-17. Storage Pool Activity

Disk Activity–Sample



| Disk Activity Page 16




| ---------------- Average Disk Activity Per Hour ---------------- ----- Cache hit Statistics ----

| Srv ------------------ Disk Arm Seek Distance ---------------------- Device Controler Write -Disk Capacity-

| Unit Util Time ð 1/12 1/6 1/3 2/3 >2/3 Read Read Efficiency MB Percent

| ---- ---- ----- --------- --------- --------- --------- --------- --------- ------- --------- ---------- ------- -------

| ððð1 A 1.8 .ðð12 2,367 1,435 4ð6 75 574 95 .ð .ð .ð 446 22.6

| ððð1 B 1.5 .ððð9 2,375 1,897 5ð7 95 243 2 .ð .ð .ð 446 22.6

| ððð3 .4 .ððð2 3,156 87ð 435 1,131 1,618 217 17.ð .1 33.5 374 25.3

| ððð4 .9 .ððð3 3,457 1,395 69ð 983 1,757 4ð3 3ð.7 .ð 15.9 378 25.6

| ððð5 .8 .ððð4 3,272 887 51ð 936 1,746 362 18.6 .ð 14.9 374 25.3

| ððð6 .8 .ððð3 2,897 1,ð99 365 1,ð84 1,435 229 4ð.2 .1 39.4 381 25.8

| ððð7 2.ð .ððð2 6,329 2,294 1,ðð6 1,45ð 2,66ð 835 57.1 .1 59.4 814 25.8

| ððð8 .6 .ððð2 4,911 1,372 1,ð53 1,316 1,734 481 2ð.5 .1 49.8 8ð3 25.5

| ððð9 5.ð .ððð2 7,484 4,65ð 1,357 2,149 2,233 5ð1 73.9 .ð 81.8 814 25.8

| ðð1ð .5 .ððð2 4,832 2,ð39 76ð 1,433 1,644 3ð4 29.ð .1 2.2 811 25.7

| Column Total Average

| --------------------------- ---------------- ----------------

| Util 1.4

| Srv Time .ððð3

| Disk Arm Seek Distance

| ð 41,ð85

| 1/12 17,941

| 1/6 7,ð92

| 1/3 1ð,657

| 2/3 15,65ð

| >2/3 3,434

| Cache hit Statistics

| Device Read 52.8

| Controller Read .ð

| Write Efficiency 59.5

| Disk Capacity

| MB 5,641

| Percent 25.1


| Util -- Drive utilization

| Srv Time -- Average service time per request in seconds

| Disk Arm Seek Distance -- Average seek distance distributions per hour

| ð -- Number of zero seeks

| 1/12 -- Number of seeks between ð and 1/12 of the disk

| 1/6 -- Number of seeks between 1/12 and 1/6 of the disk



| >2/3 -- Number of seeks greater than 2/ 3 of the disk

| Cache hit Stastistics --

| Device Read -- Percent of Device Read Hits for each arm

| Controller Read -- Percent of Controller Cache Read Hits for each arm

| Write Efficiency -- Percent of Efficiency of write Cache

| Disk Capacity -- Average amount of disk space used or available

| MB -- Millions of bytes available on the disk

| Percent -- Percent of space available on the disk

Figure 7-18. Disk Activity

IOP Utilizations–Sample


| Component Report 9/15/98 1ð:51:38

| IOP Utilizations Page 29

| Sample Component Report



| --- IOP Processor Util --- DASD -- KBytes Transmitted -- Available

| IOP Total Comm LWSC DASD Ops/Sec IOP System Storage Util 2

| -------------------- ----- ----- ----- ----- ----------- ----------- ----------- ----------- ------

| CCð1 (2623) .2 .ð 94 ð 1,772,ð96 .ð

| CCð2 (2623) .2 .ð 94 ð 1,772,ð96 .ð

| CCð3 (2626) 28.4 28.4 488,619 316,ð44 287,972 .ð

| CCð4 (2626) .1 .ð 94 ð 1,772,216 .ð

| CCð5 (2619) 3.5 3.5 .ð .ð 191,623 1,191 1,864,336 .ð

| CMBð1 (918B) 3.6 .ð .ð 3.5 1,5ð6 7,89ð,496 2,122,56ð .ð

| SIð2 (6533) 2.7 .ð .ð 1.7 3,645 29,324 6,485,936 .ð

| WSð1 (2661) .6 63 39

| IOP -- Resource name and model number for each communications, DASD,

| multifunction, and local work station IOP

| IOP Processor Util Total -- Total utilization for IOP

| IOP Processor Util Comm -- Utilization of IOP due to communications activity

| IOP Processor Util LWSC -- Utilization of IOP due to local work station activity

| IOP Processor Util DASD -- Utilization of IOP due to DASD activity

| DASD Ops/Sec -- Disk operations per second

| KBytes Transmitted IOP -- Total Kbytes transmitted from an IOP to the system across the bus

| KBytes Transmitted System -- Total Kbytes transmitted to the IOP from the system across the bus

| Available Storage -- The average number of bytes of free local storage in the IOP

| Util 2 -- Utilization of co-processor

Figure 7-19. IOP Utilizations

Local Work Stations–Response Time Buckets–Sample


| Local Work Stations - Response Time Buckets Page 3ð




| Ctl/Device Util IOP Name

| --------------- ---- ------------

| CTLð1 .6 WSð1

| ð- 1.ð 1.ð- 2.ð 2.ð- 4.ð 4.ð- 8.ð > 8.ð Rsp Time

| ------ --------- --------- --------- ------ --------

| DSPð1 ð ð 1 ð ð 3.ðð

| DSPð2 23 1 2 1 2 2.89

| Total Responses 23 1 3 1 2 2.9ð

| Ctl -- Controller identifier

| Device -- Device identifier

| Util -- Controller utilization

| IOP Name -- Input/Output processor resource name

| ð- 1.ð -- Number of response times in this range

| 1.ð- 2.ð -- Number of response times in this range



| > 8.ð -- Number of response times in this range

| Rsp time -- Average external response time (in seconds)

| for this workstation(s)

Figure 7-20. Local Work Stations – Response Time Buckets

Remote Work Stations–Response Time Buckets–Sample


Component Report 9/24/98 7:38:ð5

Remote Work Stations - Response Time Buckets Page 18

Sample Component Report

Member . . . : TEST2ð Model/Serial . : 5ðð-2142/1ð-317CD Main storage . . : 128.ð M Started . . . . : ð9/19/98 16:47:34

Library . . : RWSDATA System name . . : ABSYSTEM Version/Release : 4/ 2.ð Stopped . . . . : ð9/19/98 17:12:36

Ctl/Device IOP Name

--------------- ------------

ABSYSTEM CCð2

ð- 1.ð 1.ð- 2.ð 2.ð- 4.ð 4.ð- 8.ð > 8.ð Rsp Time

------ --------- --------- --------- ------ --------

RCH5DSPð7 845 ð ð ð ð .ð2

Total Responses 845 ð ð ð ð .ð2

Ctl -- Controller identifier

Device -- Device identifier

IOP Name -- Input/Output processor resource name

ð- 1.ð -- Number of response times in this range

1.ð- 2.ð -- Number of response times in this range



> 8.ð -- Number of response times in this range

Rsp time -- Average external response time (in seconds)

for this workstation(s)

Figure 7-21. Remote Work Stations – Response Time Buckets

Exception Occurrence Summary and Interval Counts–Sample


| Exception Occurrence Summary and Interval Counts Page 31




| Exception Counts

| Exception

| Type Description Total

| ---------------- -------------------------------- -----------

| Size Size ð

| Binary Overflow Binary overflow ð

| Decimal Overflow Decimal overflow ð

| Flp Overflow Floating point overflow ð

| Decimal Data Decimal data ð

| Aut Lookup Authority lookup 4,811

| PAG Fault Process Access Group fault 3,819

| Seize Conflict Seize conflict 2,236

| Lock Conflict Lock conflict 344

| Verify Verify ð

| -------------------------------------------- Exceptions Per Second ---------------------------------------------

| Itv Binary Decimal Flp Decimal Aut PAG Seize Lock

| End Size Overflow Overflow Overflow Data Lookup Fault Conflict Conflict Verify

| ----- ------- -------- -------- -------- -------- -------- -------- -------- -------- --------

| ðð:31 .ð .ð .ð .ð .ð .ð .ð .ð .ð .ð

| ðð:46 .ð .ð .ð .ð .ð .1 .ð .ð .ð .ð

| ð1:ð1 .ð .ð .ð .ð .ð .ð .ð .ð .ð .ð

| .

| .

| .

Figure 7-22. Exception Occurrence Summary and Interval Counts

Database Journaling Summary–Sample



| Data Base Journaling Summary Page 34




| ------- Journal Operations ------ --- Journal Deposits --- Bundle Bundle --Exposed AP -- --Est Exposr --

| Itv User User System System User System System Writes Writes System Not Curr AP Not SMAPP

| End Starts Stops Starts Stops Total Total ToUser User System Jrnld Jrnld System Jrnld ReTune

| ----- ------ ------ ------ ------ ------- ------- ------- ------- -------- ------ ------ ------ ------ ------

| ðð:31 ð ð ð ð ð ð ð ð ð ð 25 19 19 ð

| ðð:46 ð ð ð ð 4 ð ð 4 ð ð 25 19 19 ð

| ð1:ð1 ð ð ð ð 34 ð ð 34 ð ð 25 19 19 ð

| ð1:16 ð ð ð ð ð ð ð ð ð ð 25 19 19 ð

| ð1:31 ð ð ð ð ð ð ð ð ð ð 25 19 19 ð

| .

| .

| .


| User Starts -- Start journal operations initiated by user

| User Stops -- Stop journal operations initiated by user

| System Starts -- Start journal operations initiated by system

| System Stops -- Stop journal operations initiated by system

| User Total -- Journal deposits resulting from user journaled

| objects

| System Total -- Journal deposits resulting from system journaled

| objects (total)

| System ToUser -- Journal deposits resulting from system journaled

| objects to user created journals

| Bundle Writes User -- Bundle writes to user created journals

| Bundle Writes System -- Bundle writes to internal system journals

| Exposed AP System Jrnld -- Exposed access paths currently being journaled

| by the system

| Exposed AP Not Jrnld -- Exposed access paths currently not being journaled

| Est Exposr Curr System -- System estimated access path recovery time

| exposure in minutes

| Est Exposr AP Not Jrnld -- System estimated access path recovery time

| exposure in minutes if no access

| paths were being journaled by the system

| SMAPP ReTune -- System Managed Access Path Protection tuning

| adjustments

Figure 7-23. Database Journaling Summary

Component Report Selection Criteria: Select Parameters–Sample

Component Report 11/2ð/95 1ð:ð6:31

Report Selection Criteria Page ðð14

Sample Component Report

Member . . . : CAJð5ð3 Model/Serial . : 51ð-2144/1ð-ð8BCD Main storage . . : 384.ð MB Started . . . . : ð5/ð3/96 14:59:32

Library . . : QPFRDATA System name . . : ABSYSTEM Version/Release : 3/ 7.ð Stopped . . . . : ð5/ð3/96 15:ð4:31

Select Parameters















Figure 7-24. Report Selection Criteria


Component Report Selection Criteria: Omit Parameters–Sample

Omit Parameters















Figure 7-25. Report Selection Criteria

Transaction Report

Printing the Transaction ReportUse the PRTTNSRPT command, or select option 3 (Transaction report) on the PrintPerformance Reports display. When you use the PRTTNSRPT command, you canchoose to print three types of reports using the report type (RPTTYPE) parameter

� Job Summary Report (*SUMMARY)

� Transaction Report (*TNSACT)

� Transition Report (*TRSIT)

The Transaction and Transition Reports provide detailed information. So, when youprint these reports, use the selection values available on the PRTTNSRPTcommand to select specific jobs, users, or time intervals. That way you can limit theoutput to relevant information only.

The PRTTNSRPT command uses trace output from the STRPFRMON command.The STRPFRMON command must be run first.

Notes:

1. In some instances, when a value is too large to fit in the allotted space, a 9 isprinted in each numeric field in the report. To see the actual value, you shouldspecify RPTTYPE(*FILE) on the PRTTNSRPT command.

2. The PRTTNSRPT command takes some CPU model values from the BEST/1hardware table to do some calculations.


Collecting Trace DataTo create trace data:

1. Start the performance monitor (use the STRPFRMON command) and specifytracing (TRACE(*ALL)).

2. When the monitor job completes, print the report. The value for the MBRparameter on the print command should be the same as the value for the LIBparameter on the print command.

Note: You can end the performance monitor before the specified interval hasended by using the End Performance Monitor (ENDPFRMON)command.

PRTTNSRPT Printer FilesThe PRTTNSRPT command uses the following printer files:

File Description

QPSPDJS Job summary report output

QPSPDTS Transaction report output

QPSPDTD Transition report output

What Is the Transaction Report?The following are the types of transaction reports:

� Job Summary Report provides general job information. Always request thisreport first.

� Transaction Report provides detailed information about each transaction thatoccurred in the job:

– Transaction response time

– Name of the program that is active at the time the transaction starts

– Processing unit time use

– Number of I/O requests

� Transition Report provides information similar to that of the TransactionReport, but the data (for example, processing unit time, I/O requests) is shownfor each job state transition, rather than just the transitions shown when the jobis waiting for work station input. The detail shown in this report helps you todetermine the program that ran during a transition, or to determine when anunsatisfied lock request occurred.

For samples of each section of the Transaction Report, see “Sample TransactionReports” on page 7-49.



Job Summary ReportThe Job Summary Report (RPTTYPE(*SUMMARY)) provides the followingsections:

� Job Summary

� System Summary Data

� Distribution of Transactions by CPU/Transaction

� Transaction Significance

� Interactive Transactions by 5-Minute Intervals

� Interactive Throughput by 5-Minute Intervals

� Interactive CPU Utilization by 5-Minute Intervals

� Interactive Response Time by 5-Minute Intervals

� Scatter Diagram of Interactive Transactions by 5-Minute Intervals

� Interactive Program Transaction Statistics

� Summary of Seize/Lock Conflicts by Object


Job Summary SectionThe Job Summary section of the Job Summary Report shows the following informa-tion for each job in the system:

� The name and type of job (for example, interactive, batch)

� The number of transactions in the job

� The average transaction response time

� The average processing unit time per transaction

� The average number of disk I/O requests per transaction

� The number of lock waits

� The number of seize conflicts

� The key/think time per transaction

If the Job Summary section shows jobs that have high response times, high diskI/O activity, high processing unit utilization, or a number of lock requests, use theTransaction Report to investigate further.

If the number of seizes or number of conflicts (Number Sze Cft or Number LckCft columns on this report) is “high,” look at the Transaction or Transition reportsfor the job to see how long the conflict lasted, the job that held the object, the nameand type of object being held, and what the job was waiting for.

The exact meaning of the term “high” is dependent on the application. Oneexample is the number of lock-waits . An application that has many usersaccessing a database at the same time could, under normal conditions, havenumerous lock-waits.

You must evaluate each situation individually. If the values are difficult to explain(an application should have very few locks and yet many are reported), then further


analysis will be required. The Transaction and Transition Reports can help in thisanalysis.

System Summary Data Section (First Part)The first part of the System Summary Data section of the Job Summary Reportincludes the following:

� Trace Periods for Trace Date

� CPU by Priority for All Jobs for Total Trace Period


System Summary Data (Second Part)The second part of the System Summary Data section of the Job Summary Reportincludes the following:

� CPU and Disk I/O per Job Type for All Jobs for Total Trace Period

� Interactive Transaction Averages by Job Type


System Summary Data (Third Part)The Analysis by Interactive Transaction Categories part of the System SummaryData section provides a breakdown of the transactions into the categories verysimple, simple, medium, and complex, relative to their processing unit utilization.

The boundary values that are used to categorize the transactions by processingunit model were updated to more accurately reflect a typical customer workload.The boundary values have almost doubled. For the typical customer workload, thisupdate causes the number of transactions categorized as simple and medium toincrease, and those categorized as complex and very complex to decrease. Thisdoes not change the data itself or how it is collected. The update only changes howindividual transactions are categorized by the Transaction Report.

Note: The Total/Avg is only a total or average of the simple, medium, andcomplex categories. The very simple category is a part of the simple cate-gory. The very complex category is a part of the complex category.

These transaction categories depend on the processing unit model. They are intro-duced here and in some of the following reports as a way to highlight the differ-ences that exist in the work being done on the system.

When you are considering adding new applications, determine the new application’stransaction characteristics. For example, determine if a high volume of complextransactions is typical with this new application. By analyzing the transaction char-acteristics of new applications, you may be able to foresee the need to acquireadditional hardware resources for the new application.

If you obtain a new application from a supplier, it is reasonable to ask for informa-tion about the application’s transaction characteristics.

The Analysis by Interactive Response Time part of the System Summary Datasection provides transaction information sorted by response time categories.


The Analysis by Interactive Key/Think Time part of the System Summary Datasection provides information about the key/think time.


Distribution by CPU/Transaction SectionThe Distribution of Transactions by CPU/Transaction section of the Job SummaryReport provides a graphical view of the distribution of simple, medium, and complextransactions. This chart shows the number of transactions versus the processingunit time per transaction in seconds.


Transaction Significance SectionThe Transaction Significance section of the Job Summary Report provides a graph-ical view of the processing unit use, categorized by simple, medium, and complextransactions. This chart shows the percent of available processing unit time usedversus the processing unit time per transaction in seconds.


Transactions by Intervals SectionThe Interactive Transactions by 5-Minute Intervals section of the Job SummaryReport provides a count of the number of active jobs during a 5-minute interval thatperformed at least one transaction. It also shows the number of jobs that weresigned on and off during the 5-minute intervals. Transaction rates per 5-minuteintervals are shown in several different formats.


Interactive Throughput SectionThe Interactive Throughput by 5-Minute Intervals section of the Job SummaryReport gives simple, medium, and complex transactions relative to the number oftransactions according to an interval end time.


Interactive CPU Utilization SectionThe Interactive CPU Utilization by 5-Minute Intervals section of the Job SummaryReport gives simple, medium, and complex transactions relative to their processingunit utilization.


Interactive Response Time SectionThe Interactive Response Time by 5-Minute Intervals section of the Job SummaryReport gives the response components relative to the resulting response time.



Scatter Diagram SectionThe Scatter Diagram section of the Job Summary Report gives the average ofmeasured response times for 5-minute intervals compared to transaction rates.


Interactive Program Transaction Statistics SectionThe Interactive Program Transaction Statistics section of the Job Summary Reportarranges the programs by the number of transactions associated with the pro-grams.


Seize/Lock Conflicts by Object SectionThe Summary of Seize/Lock Conflicts by Object section of the Job SummaryReport gives information about the locks and seizes associated with objects. Theunnamed object, shown as ADDR 00000E00, is the Licensed Internal Code data-base in-use table. It often appears in this report when there are a high number ofdatabase file opens and closes.


Special System InformationIn general, the information identifies exceptional conditions and events that occurover the measurement period. If you analyze these exceptions, you might find jobsand programs you need to examine. A summary of these sections of the JobSummary Report follows.

� Priority-Jobtype-Pool Statistics section

� Job Statistics section

� Interactive Program Statistics section

� Individual Transaction Statistics section

� Longest Seize/Lock Conflicts section

� Longest Holders of Seize/Lock Conflicts section

� Batch Job Analysis section

| � Concurrent Batch Job Statistics section

� Report Selection Criteria section

To PrintUse OPTION(*SS) on the PRTTNSRPT command.


Priority-Jobtype-Pool Statistics SectionThe Priority-Jobtype-Pool Statistics section of the Job Summary Report shows thetotal processing unit seconds and physical I/O requests for each category ofpriority-jobtype and pool combination recorded during the overall test period. Thenumber of total transactions is shown for job type I only.



Job Statistics SectionThe Job Statistics section of the Job Summary Report shows the 10 jobs with the:

� Most transactions (shown in Figure 7-40 on page 7-58)

� Largest average response time

� Largest average processing unit time per transaction

� Largest synchronous disk I/O per transaction

A synchronous disk I/O is a disk access operation that must complete beforeprogram operation can continue.

� Largest asynchronous disk I/O per transaction.

An asynchronous disk I/O is a disk access operation that is not expected tocomplete before program operation can continue.

� Most seize conflicts

� Most record lock conflicts

� Most active-to-ineligible occurrences

� Most wait-to-ineligible occurrences

� Most event wait occurrences



Interactive Program Statistics SectionThe Interactive Program Statistics section of the Job Summary Report gives addi-tional program information showing the top 10 programs with the largest average:

� Processing unit time per transaction (shown in Figure 7-41 on page 7-59)

� Synchronous disk I/O per transaction

� Asynchronous disk I/O per transaction

� Response time per transaction

� Synchronous database reads per transaction

� Synchronous database writes per transaction

� Synchronous nondatabase reads per transaction


� Synchronous nondatabase writes per transaction


Individual Transaction Statistics SectionThe Individual Transaction Statistics section of the Job Summary Report lists the 10transactions with the least or most:

� Response time (shown in Figure 7-42 on page 7-59)

� Processing unit service time

� Total synchronous disk I/O

� Total asynchronous disk I/O

� Synchronous database reads

� Synchronous database writes

� Synchronous nondatabase reads

� Synchronous nondatabase writes

� Asynchronous database reads

� Asynchronous database writes

� Asynchronous nondatabase reads

� Asynchronous nondatabase writes

� Short-wait-extended time

� Short-wait time

� Lock-wait time

� Excessive activity-level wait time

� Active time

� Binary overflow exceptions

� Decimal overflow exceptions

� Floating point overflow exceptions

� Process access group fault exceptions

� Permanent writes


See the sample report shown in Figure 7-42 on page 7-59

Longest Seize/Lock Conflicts SectionThe Longest Seize/Lock Conflicts section of the Job Summary Report shows the 30longest lock or seize conflicts during the trace period.




Longest Holders of Seize/Lock Conflicts SectionThe Longest Holders of Seize/Lock Conflicts section of the Job Summary Reportshows the holders of the longest lock or seize conflicts for all job types during thetrace period.



Batch Job Analysis SectionNote: The Batch Job Analysis section does not print if you also specify a value on

the select job (SLTJOB) parameter or the omit job (OMTJOB) parameter.

The Batch Job Analysis section of the Job Summary Report shows information onthe batch job workload during the trace period.



Concurrent Batch Job StatisticsThe Concurrent Batch Job Statistics section of the Job Summary Report showsinformation on the batch job workload during the trace period according to job sets.

By looking at the first lines for a particular priority, you can quickly determine if thesystem was fully utilizing all available batch activity levels during the trace period.

The performance monitor begins identifying concurrent jobs when the monitor isstarted. All jobs that are currently active are assigned to a job set. There will oftenbe several jobs that are continuously active during the trace period, such asautostart jobs for SNADS and the QPFRMON job itself.

If another job starts during the trace period and none of the original jobs haveended, it is assigned to a new job set. If a job ends and another job of the samepriority starts, the new job is considered to be a second job in the same job set.

For example, if the job queue entry for QBATCH has a MAXACT parameter of 3and you submit 8 jobs to QBATCH during the trace period, there will probably be 3job sets on the report with a total of 8 jobs shared between them.

The threads are sorted by job priority. Thus, for the above example where the firstthread was running for a total of 8 minutes and 50 seconds and the second threadwas running for a total of 6 minutes and 55 seconds, the order of reporting showsthe statistics for the second thread, then the third, and then the first and assignsthem sequential numbers.



Note: The Concurrent Batch Job Statistics section does not print if you alsospecify a value on the select job (SLTJOB) parameter or the omit job(OMTJOB) parameter.


Report Selection Criteria SectionThe Report Selection Criteria section of the Job Summary Report gives theselection values you chose to produce the report.

Use the SELECT parameters on the Report Selection Criteria Report to selectpools, jobs, user IDs or functional areas. Or use the OMIT parameters to omit them

If you did not use SELECT parameters, the No Select parameters were chosen

message appears.

If you did not use OMIT parameters, the No Omit parameters were chosen

message appears.

The options which were selected are also given.



Transaction ReportThe Transaction Report (RPTTYPE(*TNSACT)) provides detailed information abouteach transaction that occurred in the job:

� Transaction response time

� Name of the program that is active at the time the transaction starts

� Processing unit time use

� Number of I/O requests

The Transaction Report output has two parts:

� The details, which show data about each transaction in the job

� The summary, which shows data about overall job operation

To PrintUse RPTTYPE(*TNSACT) on the PRTTNSRPT command.



Job Summary DataThe Job Summary Data section of the Transaction Report includes averages of thejob data. Some of this information is also found in the Job Summary section of theJob Summary Report.

Transition ReportThe Transition Report (RPTTYPE(*TRSIT)) provides information similar to that ofthe Transaction Report, but the data (for example, processing unit time, I/Orequests) is shown for each job state transition, rather than just the transitionsshown when the job is waiting for work station input. The detail shown in this reporthelps you to determine the program that ran during a transition, or to determinewhen an unsatisfied lock request occurred.

The Transition Report is composed of two sections:

� Transition Detail, which shows each state transition made by the job (goingfrom one state to another, such as active-to-ineligible)

� Summary, which shows the same data as the summary output from the Trans-action Report

To PrintUse RPTTYPE(*TRSIT) on the PRTTNSRPT command.


Transition DetailThe job transitions for jobs using data queues are in the State column of the Tran-sition Detail report. If a job uses data queues (CALL QSNDDTAQ or CALLQRCVDTAQ), each access to the queue is marked with an EOT2-SOT2 pair. Ifdata is received by a queue when the data queue currently has no entries, thetransition detail report shows a job state of wait (W in the STATE column), but leavesthe job in the activity level up to a short wait time (2 seconds) or until the intervaltime set for the time slice end.

When either the time-out value of the QRCVDTAQ API ends or data is returnedfrom the queue, the transition report records an -->A in the STATE column.

If a job is doing interactive I/O operations to an ICF file, the transition detail recordsa W<-- and -->A pair under the STATE column for start (W) and completion (A) ofthe write or read operation. For example, if the job is doing APPC I/O operationswithin an interactive transition with a display device:

Time stamp SOT1Time stamp W<--Time stamp -->ATime stamp W<--Time stamp -->A| job processingTime stamp EOR1Time stamp EOT1


If the wait code column has an EORn, EOTn, or SOTn, the two program names onthe left are filled in with information from the transaction boundary trace record, andthe two program names on the right are blank.

The program name under Last contains the following information:

Transaction Name

Display I/O Display device

Data queue Data queue library

MRT Display device

Pass-through Device description

The program name under Second contains the following information:

Transaction Name

Display I/O Display file

Data queue Data queue

MRT Display file

Source pass-through Target control point

Target pass-through Source control point

WSF target pass-through Controller description

The values ADR=000000 or ADR=UNKWN can also appear as the program name.The ADR=000000 occurs when there was no program active at that level in the jobwhen the trace record was created. ADR=UNKWN indicates that the program didnot exist on the system at the time the trace record data was dumped to a data-base file. This happens if you have deleted (or replaced) the program beforedumping the file. The program names are put into the trace record when themonitor ends and the trace data is put into a database file or when the Dump Trace(DMPTRC) command is used.

SummaryThe summary section of the Transition Report shows the same information as thesummary section of the Transaction Report, described in “Job Summary Data” onpage 7-46.

Table 7-3 on page 7-48 shows jobs with a W← (wait) job state and 130 for adecimal qualifier. The job went from an active-to-wait state and dropped from theactivity level (this defines the end of a transaction in the report).


Table 7-3. W← Job States and Decimal Qualifiers

State W A I Wait Code Decimal Qualifier Description

W← – 130 Dequeue wait (Flag X'64).

W← EVT 130 Wait on event (Flag X'A4).

W← LKW 130 Lock wait (Flag X'34').

W← HDW 130 Hold wait (Flag X'2C').

Note: For the W← entry (going to long wait and not holding an activity level position) the WRITES value includesthe I/O to write the PAG to disk as well as any other write operations that have occurred since the lasttrace entry. You can verify this by comparing it to output from extended trace job by looking at theWRITES values across a WAIT entry (on the TRCJOB command).

You cannot exactly compare the times in the MPL trace data records with the times from TRCJOB or storagemanagement trace. Each uses a different method to convert to an HH:MM:SS.SSS value from an 8-bytehexadecimal clock.

Table 7-4 shows jobs with a W (wait) job state and a decimal qualifier of 134. Thejob went from active-to-wait state but stayed in the activity level (for example, ashort wait).

Table 7-4. W Job States and Decimal Qualifiers


W – 134 Dequeue wait (Flag X'64').

W EVT 134 Wait on event (Flag X'A4').

Table 7-5 shows jobs with an I (ineligible) job state.

Table 7-5. I Job States and Decimal Qualifiers


→I – 128 A new task cannot start.

→I – 132 Wait-to-ineligible transition.

→I TSE 136 Active-to-ineligible (time slice end).

Table 7-6 on page 7-49 shows jobs with an A (active) job state.


Table 7-6. A Job States and Decimal Qualifiers


A – 142 Wait-to-active but already in the activitylevel.

A← – 129 Ineligible-to-active transition.

A – 131 Message received while the task was inthe current MPL.

A – 133 Dequeue after time-out, task in currentMPL when message received.

→A – 135 Job went from wait-to-active state (thisdefines the beginning of a transaction inthe report).

A WTO 137 Wait timed out.

A TSE 139 Active-to-active (external time slice endbased on time slice value in class) Forexample, a time slice end occurred andno jobs were waiting for an activity level.

A TSE 145 Active-to-active (internal time slice endbased on time slice value defined onSTRPFRMON).

Sample Transaction ReportsSee “Performance Report Columns” on page 7-102 for an alphabetized list con-taining definitions for each column in the reports.

Job Summary–Sample


| Job Summary Report 11/11/98 8:35:42

| Job Summary Page ððð5


| Member . . . : Q98315ð757 Model/Serial . : 51ð-2144/1ð-16CAD Main storage . . : 512.ð M Started . . . . :11/11/98 ð7:58:1ð

| Library . . : PFRRES42 System name . . : ABSYSTEM Version/Release : 4/ 2.ð Stopped . . . . :11/11/98 ð8:18:45

| \On/Off\ T P P Tot Response Sec CPU Sec ---- Average DIO/Transaction ----- Number K/T

| Job User Name/ Job y t r Nbr ------------- ------------------ ------ Synchronous ----- --Async-- Cft /Tns

| Name Thread Number Pl p y g Tns Avg Max Util Avg Max DBR NDBR Wrt Sum Max Sum Max Lck Sze Sec

| ---------- ---------- ------ -- -- -- - ---- ------ ------ ---- ------ ------ ---- ---- ---- ---- ---- ---- ---- --- --- -----

| QPADEVðð1ð ITSCID38 \ð23413 ð4 I 2ð Y 6 .1 .3 .1 .ð7 .18 3 1 4 7 2 4 2

| QPADEVðð16 COOK \ð23414 ð4 I 2ð Y 44 1.ð 25.6 .4 .ð3 .54 1 1 22 3 3

| QPADEVðð17 COOK \ð23415 ð4 I 2ð Y 51 .5 7.5 .4 .ð2 .54 1 1 18 5 2

| QJVACMDSRV COOK ð23416 ð4 BD 2ð 7.3 1.9ð 574 51

| QJVACMDSRV COOK ð23417 ð4 BD 2ð 7.5 1.89 565 51

| QJVACMDSRV ððððððð6 ð23416 ð4 BD 2ð 54.9 .ð5 1

| QJVACMDSRV ððððððð7 ð23416 ð4 BD 2ð 1.6 .16 1

| QJVACMDSRV ððððððð8 ð23416 ð4 BD 2ð 1.ð .16

| QJVACMDSRV ððððððð9 ð23417 ð4 BD 2ð 52.ð .ð3

| QJVACMDSRV ðððððððA ð23417 ð4 BD 2ð 1.6 .16

| QJVACMDSRV ðððððððB ð23417 ð4 BD 2ð 1.ð .17 1

| .

| .

| .

| DOMINOð2 QSYS ð24859 ð2 M ðð

| QNNINSTS QNOTES ð2486ð ð2 B 2ð

| SERVER QNOTES ð24861 ð2 BD 2ð .ð3

| SERVER ðððððð12 ð24858 ð2 BD 2ð .13

| SERVER ðððððð13 ð24858 ð2 BD 2ð .1 .43

| REPLICA QNOTES ð24862 ð2 BD 2ð .ð5 1

| ROUTER QNOTES ð24863 ð2 BD 2ð .21 1

| UPDATE QNOTES ð24864 ð2 BD 2ð .ð6 1

| STATS QNOTES ð24865 ð2 BD 2ð .5 1.24 1

| .

| .

| .

| SERVER ðððððð12 ð24861 ð2 BD 2ð .13

| EVENT QNOTES ð24875 ð2 BD 2ð .ð8 1

| AMGR QNOTES ð24876 ð2 BD 2ð .21

| REPORT QNOTES ð24877 ð2 BD 2ð .15 13

| EVENT ðððððð3ð ð24875 ð2 BD 2ð .19 3

| EVENT ðððððð31 ð24875 ð2 BD 2ð .1 .4ð 1

| EVENT ðððððð32 ð24875 ð2 BD 2ð .1 .36



| EVENT ðððððð35 ð24875 ð2 BD 2ð .ð6 2


Figure 7-26. Job Summary: Job Summary

System Summary Data (First Part)–Sample


| Job Summary Report 9/ð5/98 14:ð8:5ð

| System Summary Data Page ðð8ð

| Transaction Report Summary

| Member . . . : Q981421246 Model/Serial . : 5ðð-2142/1ð-18ð3D Main storage . . : 128.ð M Started . . . . :ð5/22/98 12:47:42

| Library . . : THREAD1 System name . . : ABSYSTEM Version/Release : 4/ 2.ð Stopped . . . . :ð5/22/98 12:53:25

| TRACE PERIODS FOR TRACE DATE.

| Elapsed

| Started Stopped Seconds

| -------- -------- ---------

| 12.47.42 12.53.25 343

| CPU BY PRIORITY FOR ALL JOBS FOR TOTAL TRACE PERIOD.

| CPU Cum CPU CPU

| Pty CPU Util Util QM

| ---- -------------- ------ ------- -------

| ðð 65.354 19.ð5 19.ð5 1.235

| ð9 19.ð5 1.235

| 1ð 19.ð5 1.235

| 16 19.ð5 1.235

| 2ð 84.7ð6 24.69 43.74 1.777

| 25 .ð38 .ð1 43.75 1.777

| 3ð .ð31 43.75 1.777

| 35 .ð23 43.75 1.777

| 36 43.75 1.777

| 4ð .ð77 .ð2 43.77 1.778

| 49 43.77 1.778

| 5ð .125 .ð3 43.8ð 1.779

| 52 .ð29 43.8ð 1.779

| 6ð 43.8ð 1.779

| 68 2.32ð .67 44.47 1.8ðð

| 84 .396 .11 44.58 1.8ð4

| 98 .ðð9 44.58 1.8ð4

Figure 7-27. Job Summary: System Summary Data - 1

System Summary Data (Second Part)–Sample


| System Summary Data Page ðð81




| \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\

| CPU AND DISK I/O PER JOB TYPE FOR ALL JOBS FOR TOTAL TRACE PERIOD. \ USE CHGJOBTYP COMMAND FOR BLANK JOB TYPES \

| \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\

| Job Nbr CPU CPU --Disk I/O Requests-- CPU Sec/ Sync I/O

| Type Jobs Seconds Util Sync Async Sync DIO /Elp Sec

| --------------- ------- ---------- ----- --------- --------- -------- --------

| INTERACTIVE 8 1.3 .4 474 1 .ðð27 1.4

| BATCH A,B,C,D,X 84 12.6 3.7 15ð7 378 .ðð84 4.4

| SPOOL WTR/RDR ð .ð .ð ð ð .ðððð .ð

| SYSTEM JOBS 3458 84.7 24.7 1459 27 .ð581 4.3

| SYSTEM TASKS 174 54.4 15.9 872 25593 .ð624 2.5

| --------------- -------- ------------ ----- --------- --------- -------- --------

| \\ TOTALS \\ 3724 153.ð 44.7 4312 25999 .ð355 12.6

| DATA FOR SELECTED TIME INTERVAL (OR TOTAL TRACE PERIOD IF NO TIME SELECTION).

| INTERACTIVE TRANSACTION AVERAGES BY JOB TYPE.

| T Avg CPU/ ----- Sync Disk I/O Rqs/Tns ----- Async W-I Excp Key/ Active Est

| y Nbr Nbr Pct Tns Rsp Tns DB DB NDB NDB DIO Wait Wait Think K/T Of

| p Prg Jobs Tns Tns /Hour (Sec) (Sec) Read Write Read Write Sum /Tns /Tns /Tns /Tns /Tns AWS

| -- --- ---- ------ ----- ----- ------ ------ ----- ----- ----- ----- ----- ----- ------ ------- ------ ------ ---

| I YES 8 46 1ðð.ð 482 .354 .ð29 ð ð 1ð ð 1ð ð .ððð .ðð1 6.ð64 6.ð64 1

| EXCEPTIONAL WAIT BREAKDOWN BY JOB TYPE.

| A-I Short Short Seize Lock Event Excs EM327ð DDM Svr Other

| Wait Wait WaitX Wait Wait Wait ACTM Wait Wait Wait

| Type Purge /Tns /Tns /Tns /Tns /Tns /Tns /Tns /Tns /Tns /Tns

| ---- ----- ------ ------ ------ ------ ------ ------ ------ ------ ------- ------

| I YES .ððð .ððð .ððð .ððð .ððð .ððð .ðð1 .ððð .ððð .ððð



System Summary Data (Third Part)–Sample


| System Summary Data Page ðð82




| ANALYSIS BY INTERACTIVE TRANSACTION CATEGORIES.

| Avg Cum ----- Sync Disk I/O Rqs/Tns ----- Async Avg Excp Avg Est

| CPU CPU CPU DB DB NDB NDB DIO Nbr Pct Rsp Wait K/T Of

| Category /Tns Util Util Read Write Read Write Sum /Tns Tns Tns /Tns /Tns /Tns AWS

| ---------------- ------- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ------- ------- ------- ---

| VERY SIMPLE VS .ð18 .2 39 84.8 .ð31 .ðð1 1.113 1

| ----------------

| \\ SIMPLE S .ð18 .2 .2 1 1 44 95.7 .ð49 .ðð1 1.255 1

| -Boundary- .ð79

| \\ MEDIUM M .2

| -Boundary- .1ð7

| \\ COMPLEX X .261 .2 .4 224 224 1 2 4.3 7.ð56 111.852 1

| ----------------

| VERY COMPLEX VX

| ---------------- ------- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ------- ------- ------- ---

| Total/Avg of \\ .ð29 1ð 1ð 46 1ðð.ð .354 .ðð1 6.ð64 1

| ANALYSIS BY INTERACTIVE RESPONSE TIME.

| Avg Cum Avg Cum ----- Sync Disk I/O Rqs/Tns ----- Async Excp Avg

| Rsp Nbr Pct Pct CPU CPU CPU DB DB NDB NDB DIO Wait K/T

| Category /Tns Tns Tns Tns /Tns Util Util Read Write Read Write Sum /Tns /Tns /Tns

| ---------------- ------- ----- ----- ----- ------- ----- ----- ----- ----- ----- ----- ----- ----- ------- -------

| Sub-Second .ð49 44 95.7 95.7 .ð18 .2 .2 1 1 .ðð1 1.255

| 1 - 1.999 Sec 95.7 .2

| 2 - 2.999 Sec 95.7 .2

| 3 - 4.999 Sec 95.7 .2

| 5 - 9.999 Sec 7.ð56 2 4.3 1ðð.ð .261 .2 .4 224 224 1 111.852

| GE 1ð Seconds 1ðð.ð .4

| ANALYSIS BY INTERACTIVE KEY/THINK TIME.

| Avg Cum Avg Cum ----- Sync Disk I/O Rqs/Tns ----- Async Avg Excp

| K/T Nbr Pct Pct CPU CPU CPU DB DB NDB NDB DIO Rsp Wait

| Category /Tns Tns Tns Tns /Tns Util Util Read Write Read Write Sum /Tns /Tns /Tns

| ---------------- ------- ----- ----- ----- ------- ----- ----- ----- ----- ----- ----- ----- ----- ------- -------

| LT 2 Seconds .542 36 78.3 78.3 .ð18 .2 .2 .ð32 .ðð1

| 2 - 14.999 Sec 4.487 9 19.6 97.9 .ð54 .1 .3 3ð 3ð .957

| 15 - 29.999 Sec 97.9 .3

| 3ð - 59.999 Sec 97.9 .3

| 6ð - 299.999 Sec 219.ð4ð 1 2.2 1ðð.1 .2ð8 .1 .4 197 197 6.54ð

| GE 3ðð Seconds 1ðð.1 .4


Distribution of Simple, Medium, and Complex Processing UnitTransactions–Sample



| Distribution of Transactions by CPU/Transaction Page ðð83




| Number

| Of

| Tns

| ------

| 25+

| 24+

| 23+

| 22+

| 21+

| 2ð+

| 19+

| 18+

| 17+

| 16+

| 15+

| 14+

| 13+

| 12+ S

| 11+ S

| 1ð+ SS S

| 9+ SS S

| 8+ SS S

| 7+ SS S

| 6+ SS S

| 5+ SS S

| 4+ SSS S

| 3+ SSSSS S

| 2+ SSSSS S

| 1+ SSSSSSS X X

| 1- SSSSSSS X X

| +----+----+----+----+----+----+----+----+----+----+----+----+----+----+ +++

| .ððð .ð5ð .1ðð .15ð .2ðð .25ð .3ðð .35ð

| CPU/Transaction (Seconds)

| Transaction Categories:

| S = Simple Transactions

| m = Medium Transactions

| X = Complex Transactions

Figure 7-30. Job Summary: Distribution of Processing Unit Transactions

Transaction Significance–Sample



| Transaction Significance Page ðð84




| Percent

| CPU

| -------

| .1+ X

| .1+ X

| .1+ X

| .1+ S X

| .1+ S X

| .1+ S X

| .1+ S X

| .1+ S X

| .1+ S S X X

| .1+ S S X X

| .1+ S S X X

| .ð+ S S X X

| .ð+ S S X X

| .ð+ S S X X

| .ð+ S S X X

| .ð+ S S X X

| .ð+ SS S S X X

| .ð+ SS S S X X

| .ð+ SS S S X X

| .ð+ SS S S X X

| .ð+ SSSS S X X

| .ð+ SSSS S X X

| .ð+ SSSS S X X

| .ð+ SSSSSS X X

| .ð+ SSSSSSS X X

| .ð- SSSSSSS X X

| +----+----+----+----+----+----+----+----+----+----+----+----+----+----+ +++

| .ððð .ð5ð .1ðð .15ð .2ðð .25ð .3ðð .35ð

| CPU/Transaction (Seconds)

| Transaction Categories:

| S = Simple Transactions

| m = Medium Transactions

| X = Complex Transactions

Figure 7-31. Job Summary: Transaction Significance

Interactive Transactions by 5-Minute Intervals–Sample


| Interactive Transactions by 5 Minute Intervals Page ðð85




| --- Pct Of Tns --- Pct CPU By Nbr Nbr Sync Async Avg Excp Pct Seize Active Est

| Itv Active Nbr Tns --- Categories --- Categories Sign Sign DIO DIO Rsp Wait Ex-Wt Wait K/T Of

| End Jobs Tns /Hour %VS\ %S %M %X \%VX %S %M %X offs ons /Tns /Tns /Tns /Tns /Rsp /Tns /Tns AWS

| ----- ------ ----- ----- ---- --+--+-- ---- ---+--+--- ---- ---- ----- ----- ------- ------- ----- ------ ------ ---

| \\\

| 12.5ð\ 1 43 516 91\1ðð ð ð \ ð ð ð ð .ð35 .814

| 12.55\ 1 3 36 ð\ 33 ð 67 \ ð ð ð ð 153 4.918 75.ððð

| \ Denotes Partial Interval Data

Figure 7-32. Job Summary: Interactive Transactions by 5-Minute Intervals

Interactive Throughput by 5-Minute Intervals–Sample


Job Summary Report 5/ð7/98 13:52:1ð

Interactive Throughput by 5 Minute Intervals Page ðð1ð

Member . . . : CAJð5ð3 Model/Serial . : 51ð-2144/1ð-ð8BCD Main storage . . : 384.ð M Started . . . . : ð5 ð3 98 14:59:44

Library . . : QPFRDATA System name . . : ABSYSTEM Version/Release : 4/ 2.ð Stopped . . . . : ð5 ð3 98 15:ð4:36

Number Of Transactions Per Hour

Itv

End

ð 4ðð 8ðð 12ðð 16ðð 2ððð 24ðð 28ðð

----- +----+----+----+----+----+----+----+----+----+----+----+----+----+----+

\\\

15/ð5 XXXXXXXXXXXXXXXXXXSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS

Throughput Components:

S = Simple Transactions

m = Medium Transactions

X = Complex Transactions

Figure 7-33. Job Summary: Interactive Throughput by 5-Minute Intervals

Interactive CPU Utilization by 5-Minute Intervals–Sample


Interactive CPU Utilization by 5 Minute Intervals Page ðð11



Percent CPU Utilization

Itv

End ð 1ð 2ð 3ð 4ð 5ð 6ð 7ð 8ð 9ð 1ðð

----- +----+----+----+----+----+----+----+----+----+----+

\\\

15/ð5 XXXX

CPU Components:

S = Simple Transactions

m = Medium Transactions

X = Complex Transactions

Figure 7-34. Job Summary: Interactive CPU Utilization by 5-Minute Intervals

Interactive Response Time by 5-Minute Intervals–Sample


Interactive Response Time by 5 Minute Intervals Page ðð12



Average Response Time (Seconds)

Itv

End

ð 1.ðð 2.ðð 3.ðð 4.ðð 5.ðð 6.ðð 7.ðð

----- +----+----+----+----+----+----+----+----+----+----+----+----+----+----+

\\\

15/ð5 RRRRRRRRRRRR

Response Components:

R = CPU + Disk + Wait-to-Ineligible

w = Exceptional Wait

Figure 7-35. Job Summary: Interactive Response Time by 5-Minute Intervals

Scatter Diagram of Interactive Transactions by 5-MinuteIntervals–Sample



| Interactive Response Time by 5 Minute Intervals Page ðð88




| Average Response Time (Seconds)

| Itv

| End ð 1.ðð 2.ðð 3.ðð 4.ðð 5.ðð 6.ðð 7.ðð

| ----- +----+----+----+----+----+----+----+----+----+----+----+----+----+----+

| Response Components:

| R = CPU + Disk + Wait-to-Ineligible

| w = Exceptional Wait


| Scatter Diagram of Interactive Transactions by 5 Minute Intervals Page ðð89




| Response Time vs Number of Transactions per Hour

| ------------------------------------------------

| OVFLW

| -----

| 7.ðð+

| -

| R -

| E -

| S 6.ðð+

| P -

| O -

| N -

| S 5.ðð+

| E -

| -

| T -

| I 4.ðð+

| M -

| E -

| -

| I 3.ðð+

| N -

| -

| S -

| E 2.ðð+

| C -

| O -

| N -

| D 1.ðð+

| S -

| -

| - ð

| ð.ðð+----+----+----+----+----+----+----+----+----+----+----+----+----+----+:O

| ð 1ðð 2ðð 3ðð 4ðð 5ðð 6ðð 7ðð:F

| Number of Transactions per Hour

| Legend: 1-9 Indicates the Number of Occurrences.

| \ Indicates more than 9 Occurrences.

| ð Identifies Average of All Occurrences.

Figure 7-36. Job Summary: Interactive Transactions by 5-Minute Intervals

Interactive Program Statistics–Sample



Interactive Program Statistics Page ðð19



Cum ----- Sync Disk I/O Rqs/Tns ----- Async Short Seize Cum

Number Program CPU CPU CPU DB DB NDB NDB DIO Rsp Wait Wait Pct Pct

Rank Tns Name /Tns Util Util Read Write Read Write Sum /Tns /Tns /Tns /Tns Tns Tns

---- ------ ---------- ------ ---- ---- ----- ----- ----- ----- ----- ----- ------ ------ ------ ---- ----

1 147 QUIINMGR .ð85 4.3 4.3 1 4 11 15 1ð .792 .ð31 65.3 65.3

2 32 QSPDSPF .ðð7 .1 4.3 1 1 1 .ð47 14.2 79.6

3 19 QPTPRCSS .ð23 .2 4.5 1 1 .ð51 8.4 88.ð

4 17 QUYLIST .ð63 .4 4.9 11 2 13 2 .411 7.6 95.6

5 3 QSUBLDS .1ð1 .1 5.ð 32 32 1.ð21 1.3 96.9

6 2 QUOCPP .ð34 5.ð 6 5 11 2 .433 .ð35 .9 97.8

7 2 QUIALIST .ð13 5.ð 1 1 .ð34 .9 98.7

8 1 \TRACEOFF\ 9.5ð8 3.3 8.2 27 2ð9 1852 257ð 4658 2118 157.268 .ð39 .4 99.1

9 1 QMHDSMSS .ð62 8.3 3 3 .135 .4 99.6

1ð 1 QUOCMD .ð44 8.3 1 1 .ð68 .4 1ðð.ð

Figure 7-37. Job Summary: Interactive Program Statistics

Summary of Seize/Lock Conflicts by Object–Sample


Summary of Seize/Lock Conflicts by Object Page ðð32

Member . . . : MON3D7CRT Model/Serial . : 51ð-2144/1ð-ð8BCD Main storage . . : 384.ð M Started . . . . :ð5 13 98 11:14:15

Library . . : QPFRDATA System name . . : ABSYSTEM Version/Release : 4/ 2.ð Stopped . . . . :ð5 13 98 12:14:ð1

-------- Interactive Waiters --------- ------- Non-Interactive Waiters -------

----- Locks ----- ---- Seizes ----- ----- Locks ----- ----- Seizes -----

Type Library File Member Number Avg Sec Number Avg Sec Number Avg Sec Number Avg Sec

------ ---------- ---------- ---------- ------ -------- ------ -------- ------ -------- ------ --------

DS CVTV3R2CAJ QAPMJOBS 3 .ð8ð

DS CVTV3R2CAJ QAPMLIOP 2 .ðð1

DS CVTV3R2CAJ QAPMPOOL 2 .1ð6

DS CVTV3R2CAJ QAPMRESP 2 .ð87

DS QUSRSYS QASNADSQ 1 .4ð6

DSI CVTV3R2CAJ QAPMCONF 2 .ðð6

DSI CVTV3R2CAJ QAPMLIOP 2 .ð13

DSI CVTV3R2CAJ QAPMPOOL 1 .ð15

FILE QSPL Qð4ð79Nðð3 14 .428

JOBQ QSYS QNMSVQ 3 .ð17 1 .ð62

JOBQ QSYS QSYSNOMAX 8 .ð2ð

LIB QRECOVERY 2 .ð92

LIB QSPL 8 .ð46

LIB QSVMSS 14 .ð38

LIB QUSRSYS 8 .197

LIB SOFIACN 1

MI Q QUSRSYS QS2RRAPPN 2 1.263

MSGQ QSYS QHST 7 .ð38 8 .343

OUTQ QUSRSYS QEZJOBLOG 6 .ð21

SMIDX QSVMSS QCQJMSMI 2

SPLCB QSPSCB 6 2.556

USRPRF MORIHE 4 .ð71

USRPRF QDBSHR 22 .ð39

USRPRF QSVCCS 21 .ð43

USRPRF QSYS 1 .ð38

1Eð1ð1 1 .ð29

---------------------------------------------- ------ -------- ------ -------- ------ -------- ------ --------

\ Total Conflicts and Avg Sec/Conflict 36 .847 191 .ð65

------ ------

\ Total Transactions With Conflicts

------ ------

\ Averages Per Conflict Transaction

Figure 7-38. Job Summary: Summary of Seize/Lock Conflicts by Object


Priority-Jobtype-Pool Statistics–Sample


| Priority-Jobtype-Pool Statistics Page ðð9ð




| Job CPU --- Disk I/O Requests ---- Number

| Pty Type Pool Seconds Sync Async Tns

| --- ---- ---- ----------- ----------- ----------- ----------

| ðð B ð2 11.ð98 11ð4 358

| ðð L ð1 51.588 675 25569

| ðð L ð2 .156 14

| ðð M ð2 .ð22 26

| ðð S ð2 2.49ð 112

| ð9 S ð2

| 1ð B ð2

| 16 S ð2

| 2ð ð4 82.187 1321 27

| 2ð A ð2 .227 84 2ð

| 2ð B ð2 .658 11ð

| 2ð B ð4 .297 3

| 2ð BJ ð2

| 2ð I ð4 1.337 474 1 46

| 2ð L ð1

| 2ð S ð2

| 25 B ð2 .ð38 23

| 25 BJ ð2

| 3ð B ð2 .ð31 19

| 35 B ð2 .ð23 2ð

| 36 L ð1

| 4ð A ð2 .ðð6 7

| 4ð B ð2 .ð71 57

| 4ð X ð2

| 49 L ð1

| 5ð A ð2 .ðð7 6

| 5ð B ð2 .118 74

| 52 L ð1 .ð29 1ð 24

| 52 S ð2

| 6ð S ð2

| 68 L ð1 2.32ð 2

| 84 L ð1 .396 17ð

| 98 L ð1 .ðð9 1

Figure 7-39. Job Summary: Priority-Jobtype-Pool Statistics

Job Statistics–Sample


| Job Statistics Page ðð91




| JOBS WITH MOST TRANSACTIONS

| T P Cum Sync Async Number Cum

| Job User Name/ Job y t Nbr Rsp CPU CPU CPU DIO DIO Nbr Nbr Nbr Conflict Pct Pct

| Rank Name Thread Number Pl p y Tns /Tns /Tns Util Util /Tns /Tns W-I A-I Evt Lck Sze Tns Tns

| ---- ---------- ---------- ------ -- -- -- ----- ------ ------ ---- ---- ----- ----- --- --- --- --- --- ---- ----

| 1 QPADEVððð9 SUSTAITA ð13832 ð4 I 2ð 43 .ð35 .ð18 .2 .2 93.5 93.5

| 2 QPADEVðð26 SOLBERG ð13841 ð4 I 2ð 3 4.918 .179 .2 .4 154 6.5 1ðð.ð

| 3

| 4

| 5

| 6

| 7

| 8

| 9

| 1ð

| JOBS WITH LARGEST AVERAGE RESPONSE TIME

Figure 7-40. Job Summary: Job Statistics


Interactive Program Statistics–Sample


Interactive Program Statistics Page ðð2ð



PROGRAMS WITH HIGHEST CPU/TNS

Cum ----- Sync Disk I/O Rqs/Tns ----- Async Short Seize Cum

Number Program CPU CPU CPU DB DB NDB NDB DIO Rsp Wait Wait Pct Pct

Rank Tns Name /Tns Util Util Read Write Read Write Sum /Tns /Tns /Tns /Tns Tns Tns

---- ------ ---------- ------ ---- ---- ----- ----- ----- ----- ----- ----- ------ ------ ------ ---- ----

1 1 \TRACEOFF\ 1 4658 2118 157.268 .ð39 .4 .4

2 1

3 1

4 1

5 1

6 1

7 1

8 1

9 1

1ð 1

Figure 7-41. Job Summary: Interactive Program Statistics

Individual Transaction Statistics–Sample


| Individual Transaction Statistics Page ð1ð1




| TRANSACTIONS WITH LONGEST EXCESSIVE ACTIVITY LEVEL WAIT TIME

| Rank Value Time Program Job Name User Name Number Thread Pool Type Priority

| ---- ------------ ------------ ---------- ---------- ---------- ------ -------- ---- ---- --------

| 1 .ð18 12.48.15.8ð3 QUIINMGR QPADEVððð9 SUSTAITA ð13832 ð4 I 2ð

| 2 .ðð5 12.48.ð2.152 QUIINMGR QPADEVððð9 SUSTAITA ð13832 ð4 I 2ð

| 3

| 4

| 5

| 6

| 7

| 8

| 9

| 1ð

| TRANSACTIONS WITH LONGEST ACTIVE TIME

| Rank Value Time Program Job Name User Name Number Thread Pool Type Priority

| ---- ------------ ------------ ---------- ---------- ---------- ------ -------- ---- ---- --------

| 1 7.566 12.51.43.519 QUIINMGR QPADEVðð26 SOLBERG ð13841 ð4 I 2ð

| 2 6.536 12.51.28.115 QUIINMGR QPADEVðð26 SOLBERG ð13841 ð4 I 2ð

| 3 .642 12.51.31.29ð QUIINMGR QPADEVðð26 SOLBERG ð13841 ð4 I 2ð

| 4 .119 12.48.1ð.549 QUIINMGR QPADEVððð9 SUSTAITA ð13832 ð4 I 2ð

| 5 .ð84 12.47.49.115 QUIINMGR QPADEVððð9 SUSTAITA ð13832 ð4 I 2ð

| 6 .ð71 12.48.ð6.846 QUIINMGR QPADEVððð9 SUSTAITA ð13832 ð4 I 2ð




| 1ð .ð38 12.48.16.17ð QUIINMGR QPADEVððð9 SUSTAITA ð13832 ð4 I 2ð

Figure 7-42. Job Summary: Individual Transaction Statistics

Longest Seize/Lock Conflicts–Sample



| Longest Seize/Lock Conflicts Page ðð31




| Job User Name/ Job Holder- Job Name.. User Name. Number Pool Type Pty

| Rank Value Time Name Thread Number Pl Typ Pty S/L Object- Type.. Library... File...... Member.... RRN......

| ---- ------------ ------------ ---------- ---------- ------ -- --- --- --- ---------------------------------------------------------

| 1 2ð.679 ð8.ðð.43.582 QPADEVðð17 ðððððððD ð23398 ð4 I ð1 L HOLDER- QPADEVðð16 COOK ð23399 ð4 I 2ð

| OBJECT- DS PFREXP CSTFIL ððððð2ððð

| 2 15.999 ð8.ðð.ð9.324 QPADEVðð17 ðððððððD ð23398 ð4 I ð1 L HOLDER- QPADEVðð16 COOK ð23399 ð4 I 2ð


| 3 14.183 ð8.ð1.16.8ð7 QPADEVðð17 ðððððððD ð23398 ð4 I ð1 L HOLDER- QPADEVðð16 COOK ð23399 ð4 I 2ð


| 4 .ð34 ð8.ðð.25.331 QPADEVðð17 ðððððððD ð23398 ð4 I ð1 L HOLDER- QPADEVðð16 COOK ð23399 ð4 I 2ð

| OBJECT- DS PFREXP ITMFIL ððððð1ððð

| 5 .ð23 ð8.ð1.ð4.268 QPADEVðð17 ðððððððD ð23398 ð4 I ð1 L HOLDER- QPADEVðð16 COOK ð23399 ð4 I 2ð


| 6 .ð22 ð8.ð1.3ð.999 QPADEVðð17 ðððððððD ð23398 ð4 I ð1 L HOLDER- QPADEVðð16 COOK ð23399 ð4 I 2ð


Figure 7-43. Job Summary: Longest Seize/Lock Conflicts

Longest Holders of Seize/Lock Conflicts–Sample


| Longest Holders of Seize/Lock Conflicts Page ðð32




| Job User Name/ Job ---------------------- Object -----------------------

| Rank Value Time Name Thread Number Pl Typ Pty S/L Type Library File Member RRN

| ---- -------- ------------ ---------- ---------- ------ -- --- --- --- ------ ---------- ---------- ---------- ---------

| 1 2ð.679 ð8.ðð.43.581 QPADEVðð16 ðððððððD ð23399 ð4 I 2ð L DS PFREXP CSTFIL ððððð2ððð

| 2 15.999 ð8.ðð.ð9.324 QPADEVðð16 ðððððððD ð23399 ð4 I 2ð L DS PFREXP CSTFIL ððððð1ððð

| 3 14.183 ð8.ð1.16.8ð8 QPADEVðð16 ðððððððD ð23399 ð4 I 2ð L DS PFREXP CSTFIL ððððð3ððð

| 4 .ð34 ð8.ðð.25.332 QPADEVðð16 ðððððððD ð23399 ð4 I 2ð L DS PFREXP ITMFIL ððððð1ððð

| 5 .ð23 ð8.ð1.ð4.269 QPADEVðð16 ðððððððD ð23399 ð4 I 2ð L DS PFREXP ITMFIL ððððð2ððð

| 6 .ð22 ð8.ð1.3ð.999 QPADEVðð16 ðððððððD ð23399 ð4 I 2ð L DS PFREXP ITMFIL ððððð3ððð

Figure 7-44. Job Summary: Longest Holders of Seize/Lock Conflicts

Batch Job Analysis–Sample


| Batch Job Analysis Page ð1ð6




| T P Sync Async --- Synchronous --- Excp

| Job User Name/ Job y t Elapsed CPU CPU Disk Disk BCPU --DIO/Sec-- Wait

| Name Thread Number Pl p y Start Stop Seconds Seconds Util I/O I/O /DIO Elp Act Ded Sec

| ---------- ---------- ------ -- -- -- -------- -------- ---------- ---------- ----- -------- -------- -------- --- --- --- ---------

| QPASVRP QSYS ð13724 ð2 B 5ð 12.47.42 12.53.25 342.791 .ðð8 9 .ððð9 29 2.56

| QECS QSVSM ð13727 ð2 B 5ð 12.47.42 12.53.25 342.773 .ð58 21 .ðð28 1 28 319.27

| QNSCRMON QSVSM ð1373ð ð2 B 5ð 12.47.42 12.53.25 342.773 .ðð7 8 .ððð9 29 2.54

| QSYSSCD QPGMR ð13731 ð2 B 1ð 12.47.42 12.53.25 342.754 342.75

| QZDAINIT QUSER ð13733 ð2 BJ 2ð 12.47.42 12.53.25 342.742 342.74

| QPASVRS QSYS ð13732 ð2 B 3ð 12.47.42 12.53.25 342.721 .ð12 5 .ðð24 28 .55

| QPWFSERVSO QUSER ð13735 ð2 BJ 2ð 12.47.42 12.53.25 342.7ðð 342.7ð

| QPWFSERVS2 QUSER ð13736 ð2 BJ 2ð 12.47.42 12.53.25 342.685 342.68

| QPWFSERV QUSER ð13739 ð2 BJ 2ð 12.47.42 12.53.25 342.653 342.65

| QPWFSERV QUSER ð1374ð ð2 BJ 2ð 12.47.42 12.53.25 342.635 342.63

| QPWFSERV QUSER ð13742 ð2 BJ 2ð 12.47.42 12.53.25 342.618 342.61

| QZLSFILE QUSER ð13743 ð2 BJ 2ð 12.47.42 12.53.25 342.599 342.59

| QPASVRS QSYS ð13737 ð2 B 3ð 12.47.42 12.53.25 342.585 .ðð6 5 .ðð12 29 .68

| QNMAPINGD QUSER ð13746 ð2 BJ 25 12.47.42 12.53.25 342.561 342.56

| QNMAREXECD QUSER ð13748 ð2 BJ 25 12.47.42 12.53.25 342.522 342.52

| QPASVRS QSYS ð13747 ð2 B 3ð 12.47.42 12.53.25 342.5ð2 .ðð9 5 .ðð18 29 .43

| .

| .

| .

Figure 7-45. Job Summary: Batch Job Analysis


| Concurrent Batch Job Statistics–Sample


| Concurrent Batch Job Statistics Page ð1ð8




| Job Number Elapsed CPU Excp Sync Async

| Set Pty Jobs Seconds Seconds Wait Disk I/O Disk I/O

| ------ --- ------ -------- -------- -------- -------- --------

| 1 ðð 1 341.352 11.ð98 291.49ð 11ð4 358

| 2 1ð 1 342.754 342.75ð

| 3 2ð 1 .467 .ð11 .44ð

| 4 2ð 1 .555 .ð1ð .54ð

| 5 2ð 1 .657 .ð11 .6ðð

| 6 2ð 1 .787 .ð6ð .6ðð 1

| 7 2ð 1 .877 .ð11 .86ð

| 8 2ð 1 .971 .ð12 .95ð

| 9 2ð 1 1.ð79 .ð15 1.ð4ð 1

| 1ð 2ð 1 1.167 .ð12 1.13ð 1

| 11 2ð 1 1.25ð .ð1ð 1.23ð

| 12 2ð 1 1.341 .ð1ð 1.32ð

| 13 2ð 1 1.433 .ð11 1.41ð

| 14 2ð 1 1.514 .ð12 1.49ð

| 15 2ð 1 1.6ð4 .ð13 1.58ð

| 16 2ð 1 1.7ð8 .ð1ð 1.69ð

| .

| .

| .

Figure 7-46. Job Summary: Concurrent Batch Job Statistics

Report Selection Criteria-Sample

Job Summary Report ð5/ð7/95 13:4ð:32

Report Selection Criteria Page ðð14

Sample Transaction Report



Select Parameters


Jobs - Jobname1

Jobname2

Jobnum






Omit Parameters









Options Selected - SS Include Special Summary Reports

Figure 7-47. Job Summary Report: Report Selection Criteria


Transaction Report Option–Sample| Note: This Transaction Report ran a collection with thread activity. The report| header shows the thread identifier because the job is a secondary thread.

| Transaction Report 9/11/98 6:35:48

| Page ððð1



| Job name . . : QTMSNMPRCV User name . . . : QTCP Job number . . . : ð13771 TDE/Pl/Pty/Prg . : ð185/ð2/5ð/YES

| Thread . . . : ðððððððDF

| E T CPU ---- Physical I/O Counts ----- \\\\\ Transaction Response Time (Sec/Tns) \\\\\\ -BMPL-

| x y Sec ----- Synchronous ------ Async \\\\\\ - Activity Level Time - Inel Long C I Seize

| c Program p Per DB DB NDB NDB Disk \\\\ Short Seize Time Wait u n Hold Key/

| Time p Name e Tns Read Wrt Read Wrt Sum I/O \\ Active Wait Cft A-I/W-I Lck/Oth r l Time Think

| -------- - ---------- - ------- ---- ---- ---- ---- ---- ----- -------- ------- ------- ------- ------- ------- -- -- ----- ------

| 12.47.44 Y QSOSRV1 .ð11 5 5 ð .1ð9 .ð98 11 2.3

| -----------------------------------------------

| J O B S U M M A R Y D A T A (T O T A L S)

| -----------------------------------------------

| Average .ð11 ð ð 7 ð 7 ð .1ð9 .ð98 .ððð .ððð .ððð .ððð .ð 2.3

| Count 1 1 1

| Minimum .ð11 5 .1ð9 .ð98 2.3

| Maximum .ð11 5 .1ð9 .ð98 2.3

| Total/Job .ð11 5 ð 342.ð16 Elapsed .ð Percent CPU Utilization

Figure 7-48. Transaction Report

Transition Report Option–Sample| Note: This Transition Report ran a collection with thread activity. The report| header shows the thread identifier because the job is a secondary thread.

| Transition Report 9/11/98 6:34:3ð

| Page ððð1



| Job name . . : QTMSNMPRCV User name . . . : QTCP Job number . . . : ð13771 TDE/Pl/Pty/Prg . : ð185/ð2/5ð/YES

| Thread . . . : ððððððð5

| Job type . . : B Elapsed Time -- Seconds Sync/Async Phy I/O -MPL-

| ----------------------- ------------------------ C I Last 4 Programs in Invocation Stack

| State Wait Long Active Inel CPU DB DB NDB NDB u n -------------------------------------------

| Time W A I Code Wait /Rsp\ Wait Sec Read Wrt Read Wrt Tot r l Last Second Third Fourth

| ------------ ----- ---- ------- ------- ------- -------- ---- ---- ---- ---- ---- -- -- ---------- ---------- ---------- ----------

| 12.47.42.587 \TRACE ON

| 12.47.44.9ð4 ->A 2.317 .ð11 .ð11 5 11

| PAG= 4 PWrt= ð

| 12.47.45.ðð1 W<- .ð98 11 QSOKERN3 QSOKERN3 QSOSRV1 QTOSRCVR

| ---------- QSOSRV1 .1ð9\ .ð11 ð ð 5 ð 5\ PAG= 4 PWrt= ð

| 12.53.24.6ð3 /OFF .ðð4 2 PAG= 1 PWrt= ð

| 12.53.24.6ð3 \TRACE OFF

| -----------------------------------------------

| J O B S U M M A R Y D A T A (T O T A L S)

| -----------------------------------------------

| CPU ---- Physical I/O Counts ----- \\\\\ Transaction Response Time (Sec/Tns) \\\\\\ -BMPL-

| Sec ----- Synchronous ------ Async \\\\\\ - Activity Level Time - Inel Long C I Seize

| Per DB DB NDB NDB Disk \\\\ Short Seize Time Wait u n Hold Key/

| Tns Read Wrt Read Wrt Sum I/O \\ Active Wait Cft A-I/W-I Lck/Oth r l Time Think

| ------- ---- ---- ---- ---- ---- ----- -------- ------- ------- ------- ------- ------- -- -- ----- ------

| Average .ð11 ð ð 7 ð 7 ð .1ð9 .ð98 .ððð .ððð .ððð .ððð .ð 2.3

| Count 1 1 1

| Minimum .ð11 5 .1ð9 .ð98 2.3

| Maximum .ð11 5 .1ð9 .ð98 2.3

| Total/Job .ð11 5 ð 342.ð16 Elapsed .ð Percent CPU Utilization

Figure 7-49. Transition Report


Lock Report

Printing the Lock ReportUse the PRTLCKRPT command. The PRTLCKRPT command uses trace outputfrom the STRPFRMON command, so the STRPFRMON command must be runfirst.

Collecting Trace DataTo create the trace data:

1. Start the performance monitor (use the STRPFRMON command) and specifytracing (TRACE(*ALL)).

2. When the monitor job completes, print the report. The value for the MBRparameter on the print command should be the same as the value for the LIBparameter on the print command.

Note: You can end the performance monitor before the specified interval hasended by using the End Performance Monitor (ENDPFRMON)command.

When you use the PRTLCKRPT command, the following file is used as input:

File Description

QAPMDMPT Database file that is created by the STRPFRMON command andupdated by the PRTTNSRPT command.

See “QTRDMPT File” on page 7-96 for a description of the database file.

Following are the output files from the PRTLCKRPT command:

File Description

QPPTLCK Printer file

QAPTLCKD Database file

See “QAPTLCKD File” on page 7-101 for the database file description.

Note: In the following description, the term lock means lock or seize unless other-wise noted.

The PRTLCKRPT command produces several report formats. An optional detail listof the resource management trace records from QAPMDMPT prints first. This listmay be sorted by the times that a lock occurred, the name of the job requesting thelock, the name of the job holding the lock, or the name of the locked object. The listmay print four times (once for each of these sequences).

Consider the following points when you use the PRTLCKRPT command:

� The PRTTNSRPT output may show a high incidence of wait-to-ineligible statetransitions in the transaction summary output. If this situation occurs, it couldmean that many jobs are waiting for internal system object locks and holdingan activity level while waiting. The PRTLCKRPT report may identify these locks.

� The Detailed Lock Conflicts Report (shown in Figure 7-51 on page 7-66)shows each object lock conflict that meets the specified selection values. Do


not assume that each conflict shown for an object lock is associated with aseparate request for the object from the program that originally requested it.

When multiple requests (from multiple jobs) cause contention for an object, therequests are processed in the order received, by job priority. When conflictsoccur, multiple lock requests are made by internal programs in behalf of theprogram that originally made the request, until the lock is granted. Theseinternal requests appear on the summary, resulting in more conflicts than actu-ally occurred from the originating program’s viewpoint.

PRTLCKRPT processing does not analyze the internal lock conflicts and relatethem to the original request.

What Is the Lock Report?The Lock Report provides information about lock and seize conflicts during systemoperation. With this information you can determine if jobs are being delayed duringprocessing because of unsatisfied lock requests or internal machine seizes. Theseconditions are also called waits. If they are occurring, you can determine whichobjects the jobs are waiting for and the length of the wait.

Next, these summaries print detail listings summarized by:

� Requesting job

� Holding job

� Object name

Figure 7-51 on page 7-66 shows a sample of the detail listing, sorted by time ofday (in this case). The report options were selected to include only locks lasting atleast two seconds that occurred between 13:33:00 and 13:34:00 (as noted in thefooter printed at the bottom of the detail page).

Figure 7-52 on page 7-66 shows a sample of the Requesting Job Summarysection of the same report. The other summary sections have a similar format.

See “Sample Lock Reports” on page 7-65.

See “Performance Report Columns” on page 7-102 for definitions of specificcolumns in the reports.

Analyzing Seize/Lock ConflictsSeizes/locks are system-locking functions that ensure integrity during certain oper-ations. For example, the system uses a seize during logical file maintenance whenthe underlying physical files are changed.

Conflicts occur when one job has an object lock or seize and another job requestscontrol of the same object. A common example of a lock conflict is when a jobreads a record for update and a second job requests a lock for the same record.

If the Print Transaction Report (PRTTNSRPT) job summary output shows a highnumber for either the number of lock or the number of seize conflicts, look at theTransaction Detail Report and Transition Detail Report to further analyze the situ-


ation. You can also use the PRTLCKRPT command to print the Seize/Lock ConflictReport to see what conflicts occurred.

If the PRTTNSRPT command output shows several lock waits, or systemthroughput is low and the processing unit time and disk use is also low, these con-ditions could be caused by lock-wait conflicts occurring in jobs due to contention forfiles, records, or other objects. Analyze the resource management trace data usingthe PRTLCKRPT command to determine a cause.

You can normally expect to see some conflicts occur for a short period of time onsome objects. If you see several lock conflicts occur for nondatabase objects, itmay be a normal situation (such as writers and jobs contending for output queues).However, if the locks last a long time (more than 5 to 10 seconds), and they causeobjectionable delays to end users, this situation could indicate that you need tomake some changes to the operational environment.

If the report shows several database record locks that last for more than 5 to 10seconds, a program may have read a record for update and continued processingwithout releasing (writing) the record. This situation is normal in many applications.However, in a heavily loaded system, the job that holds the record lock may reachthe end of its time slice while it holds the lock. When this condition occurs, it delaysother jobs that need the record.

If the report shows several seizes that last for a period of time (over 1 second), thiscondition can indicate object contention problems. To ensure the accuracy of theobject, the system does not allow access to the object until all the necessarychanges are made.

| Thread Data| As you will see in the Lock Report examples, if the data collection contains thread| activity, and if the job is a secondary thread, the detail in the report shows the job| name/thread identifier/job number value. If there is no thread activity, the detail| shows the job name/user name/number value. Figure 7-50 shows a comparison| between a job that is a secondary thread and a job that is not a secondary thread.

| 9/24/98 7:4ð:ð8 Seize/Lock Wait Statistics by Time of Day Page 1

| TOD of Length Object Record

| Wait of Wait L Requestor's Job Name Holder's Job Name Type Object Name Number

| -------- ------- - ---------------------------- ---------------------------- ------ -------------------------------- ----------

| 13.ð1.28 179 MNTASK QPADEVððð9 SUSTAITA ð13917 LIB QUSRSYS

| 13.ð4.4ð 2ð TPCRTMAX ðððððð57 ð13922 TPCRTMAX SUSTAITA ð13923 LIB QUSRSYS

| Member LOCKDATA Library RWSDATA Period from ðð.ðð.ðð through 23.59.59 ð ms minimum wait

| 9/24/98 7:4ð:ð8 Seize/Lock Wait Statistics Summary Page 2

| Locks Seizes

| Requestor's Job Name Count Avg Length Count Avg Length

| ------------------------------------- ------------- ------------- ------------- -------------

| MNTASK 2 1ð4

| TPCRTMAX SUSTAITA ð13922 ððððððB8 1 193


| Figure 7-50. Example of a Detail Listing with Thread Data

Sample Lock ReportsSee “Performance Report Columns” on page 7-102 for an alphabetized list con-taining definitions for each column in the reports.


Lock Report–Detail| 9/24/98 7:4ð:ð8 Seize/Lock Wait Statistics by Time of Day Page 1

| TOD of Length Object Record

| Wait of Wait L Requestor's Job Name Holder's Job Name Type Object Name Number

| -------- ------- - ---------------------------- ---------------------------- ------ -------------------------------- ----------

| 13.ðð.43 29 MNTASK TPCRTMAX SUSTAITA ð13921 LIB QUSRSYS

| 13.ð1.28 179 MNTASK QPADEVððð9 SUSTAITA ð13917 LIB QUSRSYS

| 13.ð4.4ð 2ð TPCRTMAX ðððððð57 ð13922 TPCRTMAX SUSTAITA ð13923 LIB QUSRSYS

| 13.ð5.ð8 1ð TPCRTMAX ðððððð8C ð13922 TPCRTMAX SUSTAITA ð13924 LIB QUSRSYS

| 13.ð5.38 4 TPCRTMAX ðððððð5C ð13923 TPCRTMAX SUSTAITA ð13925 LIB QUSRSYS

| 13.ð5.57 2ðð TPCRTMAX ðððððð26 ð13924 TPCRTMAX SUSTAITA ð13925 LIB QUSRSYS

| 13.ð5.57 193 TPCRTMAX ððððððB8 ð13922 TPCRTMAX SUSTAITA ð13925 LIB QUSRSYS

| 13.ð7.58 1ðð TPCRTMAX ðððððð5B ð13923 TPCRTMAX SUSTAITA ð13925 LIB QUSRSYS



| Locks Seizes


| ------------------------------------- ------------- ------------- ------------- -------------

| MNTASK 2 1ð4

| TPCRTMAX SUSTAITA ð13922 ððððððB8 1 193

| TPCRTMAX SUSTAITA ð13922 ðððððð57 1 2ð

| TPCRTMAX SUSTAITA ð13922 ðððððð8C 1 1ð

| TPCRTMAX SUSTAITA ð13923 ðððððð5B 1 1ðð

| TPCRTMAX SUSTAITA ð13923 ðððððð5C 1 4

| TPCRTMAX SUSTAITA ð13924 ðððððð26 1 2ðð



| Locks Seizes

| Holder's Job Name Count Avg Length Count Avg Length

| ------------------------------------- ------------- ------------- ------------- -------------

| QPADEVðððB SUSTAITA ð79289 6 77,39ð

| QPADEVðððC SUSTAITA ð7929ð 3 129,ð22

| QPADEVðð15 SUSTAITA ð79291 3 114,954

| Member LOCKDATA Library RWSDATA Period from ðð.ðð.ðð through 23.59.59 5ðð ms minimum wait

Figure 7-51. Example of a Detail Listing

Lock Report–Summary

| 9/24/98 7:39:48 Seize/Lock Wait Statistics Summary Page 1

| Locks Seizes


| ------------------------------------- ------------- ------------- ------------- -------------

| QPADEVðððC SUSTAITA ð7929ð 4 9ð,394

| QPADEVðð15 SUSTAITA ð79291 4 117,47ð

| QPADEVðð25 SUSTAITA ð79139 4 91,2ð3



| Locks Seizes

| Holder's Job Name Count Avg Length Count Avg Length

| ------------------------------------- ------------- ------------- ------------- -------------

| QPADEVðððB SUSTAITA ð79289 6 77,39ð

| QPADEVðððC SUSTAITA ð7929ð 3 129,ð22

| QPADEVðð15 SUSTAITA ð79291 3 114,954



| Object Locks Seizes

| Type Object Name Count Avg Length Count Avg Length

| ------ -------------------------------- ------------- ------------- ------------- -------------

| DS QREXSRC SUSTAITA CRTETH 5 69,ð95

| MQLOCK QMH MESSAG E QUEUE LO 3 123,276

| PGM DMPSPC SUSTAITA 4 12ð,24ð


Figure 7-52. Example of Summary by Requesting Job

Job Interval Report

Printing the Job Interval ReportUse the Print Job Report (PRTJOBRPT) command, or select option 5 (Job report)on the Print Performance Reports display.


What Is the Job Interval Report?This report, like other similar reports, is produced from the sample data collectedwith the STRPFRMON command. The four major sections of this report show infor-mation on all or selected intervals and jobs, including detail and summary informa-tion for interactive jobs and for noninteractive jobs. Because the report can be long,you may want to limit the output by selecting the intervals and jobs you want toinclude. For example, you might want to specify OMTSYSTSK(*YES) on thePRTJOBPRT command to print only the user jobs and omit the system tasks. Or,you can specify OMTSYSTSK(*NO) and include the system tasks.

If a value is too large to fit in the allotted space, a 9 is printed in each numeric fieldin the report.

The following are sections of the Job Interval Report:

� Interactive Job Summary

� Noninteractive Job Summary

� Interactive Job Detail

� Noninteractive Job Detail


Interactive Job SummaryThe Interactive Job Summary section of the Job Interval Report lists one line for allselected interactive jobs that existed during each selected interval (a total of oneline per interval).

The information included in this section includes only valid interactive jobs withCPU activity different than zero, or with any I/O activity.


Noninteractive Job SummaryThe Noninteractive Job Summary section of the Job Interval Report lists one linefor all selected noninteractive jobs that existed during each selected interval (a totalof one line per interval).

The information included in this section includes only valid non-interactive jobs withCPU activity different than zero, or with any I/O activity.


Interactive Job DetailThe Interactive Job Detail section of the Job Interval Report gives detailed informa-tion by interval and job. One line is printed for each selected interactive job thatexisted during each selected interval (generally more than one line per interval).



Noninteractive Job DetailThe Noninteractive Job Detail section of the Job Interval Report gives detailed infor-mation by interval and job. One line is printed for each selected noninteractive jobthat existed during each selected interval (generally more than one line perinterval).


Report Selection CriteriaThe Report Selection Criteria section of the Job Interval Report gives the selectionvalues you chose to produce the report.


Sample Job Interval ReportsSee “Performance Report Columns” on page 7-102 for an alphabetized list con-taining definitions for each column in the reports.

Interactive Job Summary–Sample

| Job Interval Report ð9/15/98 1ð:51:36

| Interactive Job Summary Page 1

| Sample Job Report

| Member . . . : ONE Model/Serial . : 436-21ð6/1ð-1ðBDA Main storage . . : 256.ð M Started . . . : ð9/1ð/98 ðð:16:22

| Library . . : DFLBUGDL1 System name . . : ABSYSTEM Version/Release . : 4/2.ð Stopped . . . : ð9/1ð/98 23:5ð:ð8

| Itv Act Tns Rsp/ ------------------ Number of I/O -------------------- Tns/ CPU PAG Perm Arith

| End Jobs Count Tns DDM Sync Async Logical Cmn Hour Util Fault Write Ovrfl

| ----- ------ ---------- ------ --------- --------- --------- --------- --------- ---------- ---- ------ ------- ------

| ð9:46 2 34 2.41 ð 4ð73 399 188 ð 349 1.7 1ð 57ð ð

| 1ð:18 1 17 .41 ð 4ð1 62 63 ð 175 .3 1 1ð3 ð

| 1ð:33 2 24 1.ð8 ð 1247 151 159 ð 95 .3 3 85 ð

| 1ð:48 1 2 .ðð ð 43 4 ð ð 17 .ð ð 6 ð

| 11:ðð 1 3 .ðð ð 56 5 ð ð 981 1.8 1 1ð ð

| 11:46 1 7 .14 ð 23 3 ð ð 354 .3 1 11 ð

| 12:47 2 29 1.31 ð 2272 14 ð ð 1,11ð 5.9 11ð 25 ð

| 13:46 1 7 .14 ð 24 3 ð ð 354 .3 2 1ð ð

| 14:47 1 7 .14 ð 24 3 ð ð 35ð .3 ð 1ð ð

| 15:ð3 1 11 .9ð ð 513 22 4 ð 16ð .3 1 48 ð

| 15:18 2 9 2.11 ð 1425 89 47 ð 35 .1 12 1ð5 ð

| 15:33 2 6 2.16 ð 66ð 15ð 2ð8 ð 23 .1 11 183 ð

| 15:48 2 1ð .6ð ð 548 26 ð ð 39 .ð 16 35 ð

| 15:49 2 7 .28 ð 1ð6 6 ð ð 84ð .9 8 11 ð

| 16:24 1 ð .ðð ð 195 9 ð ð ð .ð 19 2ð ð

| 16:46 1 7 .14 ð 24 3 ð ð 35ð .3 1 11 ð

| 17:46 1 7 .14 ð 23 3 ð ð 354 .3 1 1ð ð

| 18:46 1 7 .14 ð 26 3 ð ð 354 .3 1 1ð ð

| 19:46 1 7 .14 ð 26 3 ð ð 35ð .3 2 1ð ð

| 2ð:46 1 7 .14 ð 23 3 ð ð 35ð .3 1 1ð ð

| 21:46 1 7 .14 ð 24 3 ð ð 354 .3 1 1ð ð

| 22:46 1 7 .ðð ð 25 3 ð ð 35ð .3 1 11 ð

| 23:46 1 7 .14 ð 48 9 ð ð 35ð .4 8 9 ð


| Act Jobs -- Number of active jobs in the interval

| Tns Count -- Number of transactions

| Rsp/Tns -- Average response time (seconds)

| DDM -- Number of logical DB I/O operations for DDM server jobs

| Sync -- Number of synchronous disk I/O operations

| Async -- Number of asynchronous disk I/O operations

| Logical -- Number of logical disk I/O operations

| Cmn -- Number of communications I/O operations

| Tns/Hour -- Average number of transactions per hour


| PAG Fault -- Number of faults involving the Process Access Group

| Perm Write -- Number of permanent writes

| Arith Ovrfl -- Number of arithmetic overflow exceptions

Figure 7-53. Interactive Job Summary Section


Noninteractive Job Summary–Sample


| Non-Interactive Job Summary Page 2

| Sample Job Report



| Itv Act CPU ---- Number of I/O Per Second ---- -- CPU/ I/O --- Line Page PAG Perm Arith

| End Jobs Util Sync Async Logical Cmn Sync Async Count Count Fault Write Ovrflw

| ----- ------- ---- ------- ------- ------- ------- ------- ------- --------- ------- ------- --------- -------

| ðð:31 34 31.8 3.8 .7 .1 .ð 82 428 2,611 46 1 1,1ð2 ð

| ðð:46 38 31.9 5.8 1.2 .2 .ð 55 258 2,619 5ð 4 1,954 ð

| ð1:ð1 41 31.7 5.6 1.ð .6 .ð 56 314 2,734 51 22 1,714 ð

| ð1:16 38 31.2 5.3 .8 .2 .ð 58 369 2,553 46 4 1,685 ð

| ð1:31 4ð 31.5 4.4 .8 .2 .ð 71 39ð 3,ð76 52 5 1,385 ð

| ð1:46 48 31.5 2.8 .7 .2 .ð 11ð 4ð7 3,728 68 63 1,113 ð

| ð2:ð1 47 31.6 1.7 .4 .2 .ð 184 666 3,924 75 4 664 ð

| ð2:16 42 32.ð 2.4 .5 .2 .ð 128 631 3,573 66 1ð 788 ð

| ð2:31 42 31.9 3.3 .7 .2 .ð 94 4ð2 3,228 61 1 1,14ð ð

| ð2:46 41 32.ð 2.ð .5 .2 .ð 156 563 2,916 57 4 777 ð

| ð3:ð1 37 31.7 5.7 1.ð .2 .ð 55 3ð9 2,776 52 2 1,741 ð

| ð3:16 37 32.ð 2.2 .4 .2 .ð 143 7ð3 2,771 51 ð 674 ð

| ð3:31 37 31.8 3.9 .8 .2 .ð 81 383 2,763 52 2 1,332 ð

| ð3:46 41 31.7 7.4 1.2 .2 .ð 42 257 2,8ð1 5ð 9 2,5ðð ð

| ð4:ð2 45 32.1 3.ð .5 .2 .ð 1ð6 568 3,47ð 61 9 1,ð23 ð

| ð4:17 46 32.ð 3.ð .6 .2 .ð 1ð6 483 4,ð15 72 18 1,ðð5 ð

| ð4:32 46 32.1 3.7 .9 .2 .ð 84 35ð 4,ð62 74 1ð 1,316 ð

| ð4:47 46 31.9 3.8 .8 .2 .ð 83 366 3,7ð5 72 6 1,349 ð

| ð5:ð2 4ð 32.1 .7 .1 .2 .ð 433 2,322 3,31ð 63 ð 279 ð

| ð5:17 41 32.ð 2.4 .5 .2 .ð 131 636 2,954 55 8 771 ð

| ð5:32 38 32.ð 3.9 1.ð .2 .ð 81 293 2,949 55 5 1,268 ð

| ð5:47 38 32.ð 1.8 .4 .2 .ð 172 771 2,895 53 5 688 ð

| ð6:ð2 41 31.8 3.2 .6 .2 .ð 98 458 2,9ðð 54 1 996 ð

| ð6:17 4ð 31.8 7.2 1.1 .2 .ð 44 284 2,956 54 2 2,382 ð

| ð6:32 48 32.1 3.3 .8 .2 .ð 95 375 3,732 67 12 1,13ð ð


| Act Jobs -- Number of jobs that were active during the interval


| Sync I/O Per Second -- Average number of synchronous disk I/O operations per second

| Async I/O Per Second -- Average number of asynchronous disk I/O operations per second

| Logical I/O Per Second -- Average number of logical disk I/O operations per second

| Cmn I/O Per Second -- Average number of communications I/O operations per second

| CPU/ Sync I/O -- Avg number of CPU milliseconds per synchronous disk I/O operation

| CPU/ Async I/O -- Avg number of CPU milliseconds per asynchronous disk I/O operation

| Line Count -- Number of lines printed

| Page Count -- Number of pages printed



| Arith Ovrflw -- Number of arithmetic overflow exceptions

Figure 7-54. Noninteractive Job Summary Section

Interactive Job Detail–Sample



| Non-Interactive Job Summary Page 2

| Sample Job Report



| Itv Act CPU ---- Number of I/O Per Second ---- -- CPU/ I/O --- Line Page PAG Perm Arith

| End Jobs Util Sync Async Logical Cmn Sync Async Count Count Fault Write Ovrflw

| ----- ------- ---- ------- ------- ------- ------- ------- ------- --------- ------- ------- --------- -------

| ðð:31 34 31.8 3.8 .7 .1 .ð 82 428 2,611 46 1 1,1ð2 ð

| ðð:46 38 31.9 5.8 1.2 .2 .ð 55 258 2,619 5ð 4 1,954 ð

| ð1:ð1 41 31.7 5.6 1.ð .6 .ð 56 314 2,734 51 22 1,714 ð

| ð1:16 38 31.2 5.3 .8 .2 .ð 58 369 2,553 46 4 1,685 ð

| ð1:31 4ð 31.5 4.4 .8 .2 .ð 71 39ð 3,ð76 52 5 1,385 ð

| ð1:46 48 31.5 2.8 .7 .2 .ð 11ð 4ð7 3,728 68 63 1,113 ð

| ð2:ð1 47 31.6 1.7 .4 .2 .ð 184 666 3,924 75 4 664 ð

| ð2:16 42 32.ð 2.4 .5 .2 .ð 128 631 3,573 66 1ð 788 ð

| ð2:31 42 31.9 3.3 .7 .2 .ð 94 4ð2 3,228 61 1 1,14ð ð

| ð2:46 41 32.ð 2.ð .5 .2 .ð 156 563 2,916 57 4 777 ð

| ð3:ð1 37 31.7 5.7 1.ð .2 .ð 55 3ð9 2,776 52 2 1,741 ð

| ð3:16 37 32.ð 2.2 .4 .2 .ð 143 7ð3 2,771 51 ð 674 ð

| ð3:31 37 31.8 3.9 .8 .2 .ð 81 383 2,763 52 2 1,332 ð

| ð3:46 41 31.7 7.4 1.2 .2 .ð 42 257 2,8ð1 5ð 9 2,5ðð ð

| ð4:ð2 45 32.1 3.ð .5 .2 .ð 1ð6 568 3,47ð 61 9 1,ð23 ð

| ð4:17 46 32.ð 3.ð .6 .2 .ð 1ð6 483 4,ð15 72 18 1,ðð5 ð

| ð4:32 46 32.1 3.7 .9 .2 .ð 84 35ð 4,ð62 74 1ð 1,316 ð

| ð4:47 46 31.9 3.8 .8 .2 .ð 83 366 3,7ð5 72 6 1,349 ð

| ð5:ð2 4ð 32.1 .7 .1 .2 .ð 433 2,322 3,31ð 63 ð 279 ð

| ð5:17 41 32.ð 2.4 .5 .2 .ð 131 636 2,954 55 8 771 ð

| ð5:32 38 32.ð 3.9 1.ð .2 .ð 81 293 2,949 55 5 1,268 ð

| ð5:47 38 32.ð 1.8 .4 .2 .ð 172 771 2,895 53 5 688 ð

| ð6:ð2 41 31.8 3.2 .6 .2 .ð 98 458 2,9ðð 54 1 996 ð

| ð6:17 4ð 31.8 7.2 1.1 .2 .ð 44 284 2,956 54 2 2,382 ð

| ð6:32 48 32.1 3.3 .8 .2 .ð 95 375 3,732 67 12 1,13ð ð


| Act Jobs -- Number of jobs that were active during the interval


| Sync I/O Per Second -- Average number of synchronous disk I/O operations per second

| Async I/O Per Second -- Average number of asynchronous disk I/O operations per second

| Logical I/O Per Second -- Average number of logical disk I/O operations per second

| Cmn I/O Per Second -- Average number of communications I/O operations per second



| Line Count -- Number of lines printed

| Page Count -- Number of pages printed



| Arith Ovrflw -- Number of arithmetic overflow exceptions

Figure 7-55. Job Interval Report: Interactive Job Detail Section

Noninteractive Job Detail –Sample



| Non-Interactive Job Detail Page 7

| Sample Job Report



| Itv Job User Job Elapsed CPU --- Nbr I/O /Sec -- -- CPU / I/O -- --- Printer ---

| End Name Name Number Pool Type Pty Time Util Sync Async Lgl Sync Async Lines Pages

| ----- ---------- ---------- ------ ---- ---- --- ------- ----- ----- ----- ----- ------- ------- --------- -------

| ðð:31 GCDJOB DHQB ð26331 2 B 99 15:ð2 .3ð ð ð ð ð ð ð ð

| ðð:31 LNEMONITOR C4STRESS ð26358 2 B ð5 15:ð2 .ðð ð ð ð 7 46 ð ð

| ðð:31 PPTJOB DHQB ð2633ð 2 B 99 15:ð2 .3ð ð ð ð ð ð ð ð

| ðð:31 QECS QSVSM ð26277 2 B 5ð 15:ð2 .ðð ð ð ð ð ð ð ð

| ðð:31 QNETWARE QSYS ð26287 2 B 5ð 15:ð2 .ðð ð ð ð ð ð ð ð

| ðð:31 QPFRMON QPGMR ð267ð6 2 B ðð 15:ð2 .ðð ð ð ð 5 47 ð ð

| ðð:31 QTFTPðð289 QTCP ð26413 2 B 25 15:ð2 .ðð ð ð ð ð ð ð ð

| ðð:31 QTFTPðð315 QTCP ð26414 2 B 25 15:ð2 .ðð ð ð ð 1ð3 1ð3 ð ð

| ðð:31 QTFTPðð324 QTCP ð26422 2 B 25 15:ð2 .ðð ð ð ð 56 113 ð ð

| ðð:31 QTFTPð1233 QTCP ð26433 2 B 25 15:ð2 .ðð ð ð ð 113 113 ð ð

| ðð:31 QTMSNMP QTCP ð264ð5 2 B 35 15:ð2 8.3ð ð ð ð ð ð ð ð

| ðð:31 QTMSNMPRCV QTCP ð264ð9 2 B 5ð 15:ð2 1.4ð ð ð ð ð ð ð ð

| ðð:31 QTSMTPSRVR QTCP ð264ð8 2 B 35 15:ð2 .ðð ð ð ð ð ð ð ð

| ðð:31 Q1PSCH QPM4ðð ð26284 2 A 5ð 15:ð2 .ðð ð ð ð ð ð ð ð

| ðð:31 SHNEPMð1 DHQB ð26326 2 B 5ð 15:ð2 13.ðð 3 ð ð 36 187 ð ð

| ðð:31 SHNEPMð2 DHQB ð26327 2 B 5ð 15:ð2 .ðð ð ð ð ð ð ð ð

| ðð:31 SNMP_DAD DHQB ð26697 2 B 5ð 15:ð2 .5ð ð ð ð 697 2,442 163 3

| ðð:31 SNMP_R5C DHQB ð26694 2 B 5ð 15:ð2 .ðð ð ð ð ð ð 26 ð

| ðð:31 SNMP_R7D DHQB ð26435 2 B 5ð 15:ð2 .5ð ð ð ð 1,538 4,616 163 2

| ðð:31 SNMP_R7D DHQB ð26456 2 B 5ð 15:ð2 .4ð ð ð ð 556 4,454 157 3




| ðð:31 SNMP_R7D DHQB ð26535 2 B 5ð 15:ð2 .4ð ð ð ð 249 4,485 162 3



| Job Name -- Job name

| User Name -- User name

| Job Number -- Job number

| Pool -- Pool in which the job ran

| Type -- Type and subtype of the job

| Pty -- Priority of the job

| Elapsed Time -- Elapsed time for job during interval (minutes and seconds)


| Sync I/O /Sec -- Average number of synchronous disk I/O operations per second

| Async I/O /Sec -- Average number of asynchronous disk I/O operations per second

| Lgl I/O /Sec -- Average number of logical disk I/O operations per second



| Printer Lines -- Number of lines printed

| Printer Pages -- Number of pages printed

Figure 7-56. Job Interval Report: Noninteractive Job Detail Section

Job Interval Report Selection Criteria: Select Parameters–Sample


Job Interval Report 11/19/95 13:28:36

Report Selection Criteria Page 3

User-Selected Report Title

Member . . . : R2162B Model/Serial . : 53ð-ðð1ð/1ð-16B7D Main storage . . : 4ð96.ð M Started . . . : ð3/21/96 ð8:37:14

Library . . : R21626ð827 System name . . : ABSYSTEM Version/Release . : 3/7.ð Stopped . . . : ð3/21/96 ð9:ð7:15

Select Parameters















Figure 7-57. Job Interval Report: Select Parameters

Job Interval Report Selection Criteria: Omit Parameters–Sample

Omit Parameters





nnnnnn User8 User9 User1ð User11 User12










Figure 7-58. Job Interval Report: Omit Parameters

Pool Interval Report


Printing the Pool Interval ReportUse the Print Pool Report (PRTPOLRPT) command, or select option 6 (Pool report)on the Print Performance Reports display.

What Is the Pool Interval Report?The Pool Report contains a section on subsystem activity and a section on poolactivity. Data is shown for each sample interval. Because the report can be long,you may want to limit the output by selecting the intervals and jobs you want toinclude.


Note: The Pool Report is produced from the sample data collected by theSTRPFRMON command.

For samples of each section of the Pool Report, see “Sample Pool IntervalReports.”


Subsystem ActivityThe Subsystem Activity section of the Pool Interval Report gives the performanceinformation on the subsystems during each selected interval. One line is printed foreach subsystem and active pool combination that existed during each selectedinterval.


Pool ActivityThe Pool Activity section of the Pool Interval Report gives the performance informa-tion on the storage pools at various time intervals. One line is printed for eachactive pool that existed during each selected interval.


Report Selection CriteriaThe Report Selection Criteria section of the Pool Interval Report gives the selectionvalues you chose to produce the report.


Sample Pool Interval ReportsSee “Performance Report Columns” on page 7-102 for an alphabetized list con-taining definitions for each column in the reports.


Subsystem Activity–Sample

| Pool Interval Report ð9/15/98 1ð:52:24

| Subsystem Activity Page 1

| Sample Pool Report



| --------- Physical I/O per Transaction -------- ---------------- Job Maximums ----------------

| Itv Subsystem CPU ----- Synchronous ----- ---- Asynchronous ----- CPU Phy

| End Name PL Util Tns DBR DBW NDBR NDBW DBR DBW NDBR NDBW Util I/O Tns Rsp A-W W-I A-I

| ----- ---------- -- ---- ---------- ----- ----- ----- ----- ----- ----- ----- ----- ---- ---------- ----- ------ ------ ---- ----

| ðð:31 QBATCH 2 22.ð ð 13.ð 3,877 ð .ðð 328 ð ð

| ðð:31 QSOC 2 .ð ð .ð ð ð .ðð 88 ð ð

| ðð:31 QSYSWRK 2 9.8 ð 8.3 6 ð .ðð 49,835 ð ð

| ðð:31 Q1PGSCH 2 .ð ð .ð 4ð ð .ðð 15 ð ð

| ðð:46 QBATCH 2 21.7 ð 12.5 5,182 ð .ðð 327 ð ð

| ðð:46 QSOC 2 .ð ð .ð ð ð .ðð 88 ð ð

| ðð:46 QSYSWRK 2 1ð.ð ð 8.4 339 ð .ðð 49,954 ð ð

| ðð:46 Q1PGSCH 2 .ð ð .ð 17ð ð .ðð 15 ð ð

| ð1:ð1 QBATCH 2 21.8 ð 12.4 4,ð88 ð .ðð 327 ð ð

| ð1:ð1 QSOC 2 .ð ð .ð ð ð .ðð 87 ð ð

| ð1:ð1 QSYSWRK 2 9.8 ð 8.2 93 ð .ðð 49,344 ð ð

| ð1:ð1 Q1PGSCH 2 .ð ð 8.8 164 ð .ðð 17 ð ð

| ð1:16 QBATCH 2 19.6 ð 1ð.8 4,864 ð .ðð 322 ð ð

| ð1:16 QSOC 2 .ð ð .ð ð ð .ðð 88 ð ð

| ð1:16 QSYSWRK 2 11.5 ð 9.7 4 ð .ðð 59,578 ð ð

| ð1:16 Q1PGSCH 2 .ð ð .ð 154 ð .ðð 15 ð ð

| ð1:31 QBATCH 2 2ð.6 ð 1ð.2 4,188 ð .ðð 323 ð ð

| ð1:31 QSOC 2 .ð ð .ð ð ð .ðð 88 ð ð

| ð1:31 QSYSWRK 2 1ð.8 ð 9.2 4 ð .ðð 54,293 ð ð


| Subsystem Name -- Subsystem name

| PL -- Pool in which the jobs in the subsystem ran

| CPU Util -- Average CPU utilization by the transactions in the subsystem. This is the average of all processors

| Tns -- Number of transactions in the subsystem

| Physical I/O per Trans -- Average physical disk I/O operations per transaction

| Synchronous DBR -- Average synchronous data base reads per transaction

| Synchronous DBW -- Average synchronous data base writes per transaction

| Synchronous NDBR -- Average synchronous non-data base reads per transaction

| Synchronous NDBW -- Average synchronous non-data base writes per transaction

| Asynchronous DBR -- Average asynchronous data base reads per transaction

| Asynchronous DBW -- Average asynchronous data base writes per transaction

| Asynchronous NDBR -- Average asynchronous non-data base reads per transaction

| Asynchronous NDBW -- Average asynchronous non-data base writes per transaction

| Job Maximums -- Maximum values by a job in the subsystem

| CPU Util -- Highest percentage CPU utilization

| Phy I/O -- Most physical disk I/O requests

| Tns -- Most transactions

| Rsp -- Highest average response time (seconds)

| A-W -- Most active-to-wait transitions

| W-I -- Most wait-to-ineligible transitions

| A-I -- Most active-to-ineligible transitions

Figure 7-59. Pool Interval Report: Subsystem Activity

Pool Activity–Sample


| Pool Interval Report ð9/15/98 1ð:52:24

| Pool Activity Page 12

| Sample Pool Report



| -------- Physical I/O per Transaction --------- ---------------- Job Maximums --------------

| Itv Act Size CPU ----- Synchronous ----- ----- Asynchronous ---- CPU Phy

| End PL Lvl (K) Util Tns DBR DBW NDBR NDBW DBR DBW NDBR NDBW Util I/O Tns Rsp A-W W-I A-I

| ----- -- ----- --------- ---- -------- ----- ----- ----- ----- ----- ----- ----- ----- ---- --------- ----- ------ ------ ---- ----

| ðð:31 2 44 1752ð4 31.8 ð 13.ð 3,877 ð .ðð 49,835 ð ð

| ðð:46 2 44 175976 31.9 ð 12.5 5,182 ð .ðð 49,954 ð ð

| ð1:ð1 2 44 177768 31.7 ð 12.4 4,ð88 ð .ðð 49,344 ð ð

| ð1:16 2 44 1785ðð 31.2 ð 1ð.8 4,864 ð .ðð 59,578 ð ð

| ð1:31 2 44 175364 31.5 ð 1ð.2 4,188 ð .ðð 54,293 ð ð

| ð1:46 2 44 1769ð8 31.5 ð 8.8 1,952 ð .ðð 48,791 ð ð

| ð2:ð1 2 44 176864 31.6 ð 8.8 1,355 ð .ðð 47,491 ð ð

| ð2:16 2 44 1776ð8 32.ð ð 11.2 2,223 ð .ðð 42,851 ð ð

| ð2:31 2 44 176896 31.9 ð 11.7 3,1ð9 ð .ðð 45,664 ð ð

| ð2:46 2 44 175756 32.ð ð 12.3 1,487 ð .ðð 47,998 ð ð

| ð3:ð1 2 44 175296 31.7 ð 12.2 5,628 ð .ðð 5ð,733 ð ð


| PL -- Pool identifier

| Act Lvl -- Activity level of the pool

| Size (K) -- Size of the pool (kilobytes)

| CPU Util -- Average CPU utilization by the transactions in the pool. This is the average of all processors

| Tns -- Number of transactions in the pool

| Physical I/O per Trans -- Average physical disk I/O operations per transaction in the pool

| Synchronous DBR -- Average synchronous data base reads per transaction

| Synchronous DBW -- Average synchronous data base writes per transaction

| Synchronous NDBR -- Average synchronous non-data base reads per transaction

| Synchronous NDBW -- Average synchronous non-data base writes per transaction

| Asynchronous DBR -- Average asynchronous data base reads per transaction

| Asynchronous DBW -- Average asynchronous data base writes per transaction

| Asynchronous NDBR -- Average asynchronous non-data base reads per transaction

| Asynchronous NDBW -- Average asynchronous non-data base writes per transaction

| Job Maximums -- Maximum values by a job in the pool

| CPU Util -- Highest percentage CPU utilization

| Phy I/O -- Most physical disk I/O requests

| Tns -- Most transactions

| Rsp -- Highest average response time (seconds)

| A-W -- Most active-to-wait transitions

| W-I -- Most wait-to-ineligible transitions

| A-I -- Most active-to-ineligible transitions

Figure 7-60. Pool Interval Report: Pool Activity

Report Selection Criteria–Sample


Pool Interval Report ð5/ð7/96 13:43:2ð

Report Selection Criteria Page 3


Member . . . : R2162B Model/Serial . : 53ð-ðð1ð/1ð-16B7D Main storage . . : 4ð96.ð M Started . . . : ð3/21/96 ð8:37:14

Library . . : R21626ð827 System name . . : ABSYSTEM Version/Release . : 3/7.ð Stopped . . . : ð3/21/96 ð9:ð7:15

Select Parameters















Omit Parameters





nnnnnn User8 User9 User1ð User11 User12










Figure 7-61. Pool Interval Report: Report Selection Criteria

Resource Interval Report

Printing the Resource Interval ReportUse the Print Resource Report (PRTRSCRPT) command, or select option 7(Resource report) on the Print Performance Reports display.

What Is the Resource Interval Report?The six major sections of the Resource Interval Report provide resource informationon all or selected intervals. Because the report can be long, you may want to limitthe output by selecting the intervals you want to include.



Sample Data: this report is produced from the sample data collected with theSTRPFRMON command.

Disk Utilization SummaryThe Disk Utilization Summary section of the Resource Interval Report givesdetailed disk information by time intervals.

Information is shown for all disk arms that are configured on the system. Also, thedisk arm with the highest utilization and the disk arm with the highest average seektime for each time interval are shown. Consistent disk arm utilization at or abovethe threshold value will affect system performance and cause longer responsetimes and/or less throughput.


Disk Utilization DetailThe Disk Utilization Detail section of the Resource Interval Report gives detaileddisk information for the selected time intervals.

Information is shown for each disk arm that is configured on the system. Con-sistent disk arm utilization at or above the threshold value will affect system per-formance and cause longer response times and/or less throughput.


Communications Line DetailA Communications Line Detail section of a Resource Interval Report contains infor-mation about the line activity when performance data was collected for the specifiedmember. One detail section is produced for each protocol in use on the lines forwhich data was collected. Figure 7-64 on page 7-82 through Figure 7-70 onpage 7-85 are samples of the detail sections for the communications protocols.

Note: Each section appears only if you have communications lines using that par-ticular protocol.

SDLC ProtocolFigure 7-64 on page 7-82 is a sample of the report section for communicationslines using the synchronous data link control (SDLC) protocol. The data in thisexample is sorted by the data collection interval end times.

X.25 ProtocolFigure 7-65 on page 7-82 is a sample of the report section for communicationslines using the X.25 protocol.

TRLAN ProtocolFigure 7-66 on page 7-83 is a sample of the report section for communicationslines using the token-ring local area network (TRLAN) protocol.


ELAN ProtocolFigure 7-67 on page 7-83 is a sample of the report section for communicationslines using the Ethernet local area network (ELAN) protocol.

DDI ProtocolFigure 7-68 on page 7-84 is a sample of the report section for communicationslines using the distributed data interface (DDI) protocol.

FRLY ProtocolFigure 7-69 on page 7-84 is a sample of the report section for communicationslines using the frame relay (FRLY) protocol.

ASYNC ProtocolFigure 7-70 on page 7-85 is a sample of the report section for communicationslines using the asynchronous (ASYNC) protocol.

Note: A protocol data unit (PDU) for asynchronous communications is a variable-length unit of data that is ended by a protocol control character or by thesize of the buffer.

BSC ProtocolFigure 7-71 on page 7-85 is a sample of the report section for communicationslines using the binary synchronous communications (BSC) protocol.

ISDN Network InterfaceFigure 7-72 on page 7-86 is a sample of the report section for the integrated ser-vices digital network (ISDN) network interface.

Network Interface Maintenance Channel for ISDNFigure 7-73 on page 7-86 is a sample of the report section for the network inter-face maintenance channel for the ISDN protocol.

IDLC ProtocolFigure 7-74 on page 7-87 and Figure 7-75 on page 7-87 are samples of the reportsection for communications lines using the ISDN data link control (IDLC) protocol.Figure 7-75 on page 7-87 indicates which B-channel the IDLC line was usingduring the interval.

Related Information

Information regarding ISDN can be found in the ISDN Support book.

IOP UtilizationsThe IOP Utilizations section of the Resource Interval Report contains a combinationof the following input/output processor (IOP) utilizations:

� Disk IOP utilizations

Gives input/output processor (IOP) utilization for direct access storage devices(DASDs). Consistent Disk IOP utilization at or above the threshold value affectssystem performance and causes longer response times and/or less throughput.

� Multifunction IOP utilizations


Gives input/output processor (IOP) utilization for DASD, communication, andlocal workstation devices. Consistent utilization at or above the threshold valueaffects system performance and causes longer response times and/or lessthroughput.

� Communications IOP utilizations

Gives communications input/output processor (IOP) utilization.

� Local work station IOP utilizations

Gives input/output processor (IOP) utilization for local workstation devices.

See the sample report shown in shown in Figure 7-76 on page 7-88.

Note: The total for the I/O processor utilization oftentimes does not match the sumof the three columns (IOP Processor Util Comm, IOP Processor Util LWSC,and IOP Processor Util DASD). This mismatch is caused by the utilization ofother small components, such as system time.

Local Work Station Response TimesThe local work station response times section provides the following for each datacollection interval:

� Local work station IOP utilization

� Number of work stations active on each controller

� Range of response times for the work stations

� Average response time for the work stations



Remote Work Station Response TimesThe remote work station response times section gives the following for each datacollection interval:

� Number of work stations active on each controller

� Range of response times for the work stations

� Average response time for the work stations


Note: This section appears only if a 5494 remote controller is included in the datacollection.



Sample Resource Interval ReportsSee “Performance Report Columns” on page 7-102 for an alphabetized list con-taining definitions for each column in the reports.

Disk Utilization Summary–Sample

| Resource Interval Report ð9/18/98 14:ð6:ðð

| Disk Utilization Summary Page 1

| Sample Resource Interval Report

| Member . . . : PMISTGA1 Model/Serial . : 5ðð-2142/1ð-18ð3D Main storage . . : 128.ð M Started . . . : ð8/11/98 13:ð9:ð4

| Library . . : PM42CRT System name . . : ABSYSTEM Version/Release . : 4/2.ð Stopped . . . : ð8/11/98 13:38:4ð

| Average Average Average High High High Disk

| Itv Average Reads Writes K Per Avg High Util Srv Srv Space

| End I/O /Sec /Sec /Sec I/O Util Util Unit Time Unit Used

| ----- --------- -------- -------- ------- ---- ---- ---- ----- ---- -----------

| 13:14 4ð.7 18.7 21.9 6.1 16.5 24.4 ððð2 .ð138 ððð2 9,682

| 13:19 32.7 16.3 16.3 5.6 13.2 2ð.3 ððð2 .ð153 ððð2 9,691

| 13:24 37.6 19.4 18.1 5.8 16.ð 22.7 ððð2 .ð143 ððð2 9,697

| 13:29 35.7 18.2 17.5 6.1 14.8 19.5 ððð2 .ð127 ððð2 9,7ð9

| 13:34 25.9 12.7 13.2 5.5 11.3 17.1 ððð2 .ð152 ððð2 9,718

| 13:38 38.3 17.8 2ð.4 6.1 16.9 24.7 ððð2 .ð158 ððð2 9,721

| --------- -------- -------- ------- ----

| Average: 35.1 17.2 17.9 5.9 14.8


| Average Phys I/O /Sec -- Average number of physical I/O operations per second

| Average Reads / Sec -- Average number of physical reads per second

| Average Writes /Sec -- Average number of physical writes per second

| Average K Per I/O -- Average number of kilobytes (1ð24) per I/O operation

| Avg Util -- Average percent utilization of all disk arms

| High Util -- Highest percent utilization for a disk arm

| High Util Unit -- Disk arm with the highest utilization percent

| High Srv Time -- Highest average service time in seconds

| High Srv Unit -- Disk arm with the highest service time

| Disk Space Used -- Total disk space used in millions of bytes

Figure 7-62. Resource Interval Report: Disk Utilization Summary

Disk Utilization Detail–Sample



| Disk Utilization Detail Page 2




| IOP Name/ ASP Itv -------- I/O Per Second --------- K Per Dsk CPU Queue Avg Time Per I/O

| Unit (Model) Id End Total Reads Writes I/O Util Util Length Service Wait

| ---- ----------------- --- ----- ---------- --------- --------- ------- ------- ---- ------- ------- ----

| ððð1 CMBð1 (66ð7) ð1 13:14 13.899 7.18ð 6.719 6.8 .ð 15.7 .24 .ð112 .ðð71

| 13:19 1ð.797 5.72ð 5.ð76 5.9 .ð 1ð.3 .15 .ðð95 .ðð53

| 13:24 12.61ð 6.943 5.666 6.2 .ð 14.8 .2ð .ð117 .ðð48

| 13:29 12.646 6.763 5.883 6.7 .ð 15.2 .26 .ð12ð .ðð97

| 13:34 8.744 5.5ð8 3.235 5.9 .ð 1ð.8 .15 .ð123 .ðð63

| 13:38 13.557 6.4ð9 7.147 6.1 .ð 15.7 .29 .ð115 .ð1ð6

| ---------- --------- --------- ------- ---- ------- ------- ----

| Unit Average: 12.ð13 6.419 5.594 6.3 13.7 .22 .ð113 .ðð73

| ððð2 CMBð1 (66ð7) ð1 13:14 17.685 6.719 1ð.966 6.ð .ð 24.4 .49 .ð137 .ð148

| 13:19 13.262 6.ððð 7.262 5.8 .ð 2ð.3 .32 .ð153 .ðð94

| 13:24 15.796 7.236 8.56ð 5.8 .ð 22.7 .37 .ð143 .ðð97

| 13:29 15.346 6.69ð 8.656 6.1 .ð 19.5 .31 .ð127 .ðð84

| 13:34 11.255 4.196 7.ð59 5.4 .ð 17.1 .25 .ð151 .ðð83

| 13:38 15.6ð5 6.653 8.952 6.3 .ð 24.7 .47 .ð158 .ð153

| ---------- --------- --------- ------- ---- ------- ------- ----

| Unit Average: 14.8ð7 6.24ð 8.567 5.9 21.4 .37 .ð144 .ð1ð9

| ððð3 CMBð1 (66ð6) ð1 13:14 9.13ð 4.882 4.247 5.3 .ð 9.5 .11 .ð1ð4 .ðð27

| 13:19 8.684 4.647 4.ð36 5.1 .ð 9.1 .11 .ð1ð4 .ðð35

| 13:24 9.223 5.3ðð 3.923 5.2 .ð 1ð.6 .15 .ð114 .ðð6ð

| 13:29 7.776 4.773 3.ðð3 5.4 .ð 9.8 .14 .ð126 .ðð61

| 13:34 5.96ð 3.ðð9 2.95ð 5.ð .ð 6.1 .ð8 .ð1ð2 .ðð46

| 13:38 9.177 4.819 4.357 5.6 .ð 1ð.3 .12 .ð112 .ðð32

| ---------- --------- --------- ------- ---- ------- ------- ----

| Unit Average: 8.3ð9 4.567 3.742 5.3 9.2 .12 .ð11ð .ðð43


| IOP Name/ -- Input/Output processor resource name and

| (Model) model number of the attached device

| ASP ID -- Auxiliary storage pool number


| I/O /Sec -- Average number of I/O operations per second

| Reads Per Second -- Average number of reads per second

| Writes Per Sec -- Average number of writes per second

| K Per I/O -- Average number of kilobytes (1ð24) per I/O operation

| Dsk CPU Util -- Percentage of Disk CPU Utilization

| Util -- Average percent of time disk was used (busy)

| Queue Length -- Average length of waiting queue



Figure 7-63. Resource Interval Report: Disk Utilization Detail

Communications Line Detail–SDLC Sample



| Communications Line Detail Page 3




| PROTOCOL = SDLC (SORT BY INTERVAL)

| Percent Percent Pct -- Congestion ---

| IOP Bytes Total I Frames Bytes Total Frames Poll Local Remote

| Itv Name/ Line Line Trnsmitd I Frames Trnsmitd Recd Frames Received Retry Not Not

| End Line Speed Util Per Sec Trnsmitd in Error Per Sec Recd in Error Time Ready Ready

| ----- ---------- -------- ------ ---------- ---------- ---------- ---------- -------- ---------- ------- ------- --------

| CCð9

| (26ð9)

| 13:14 PMSD1 19.2 4.6 49 322 ð 62 2,9ð9 ð ð ð ð

| 13:19 PMSD1 19.2 4.4 47 3ð1 ð 6ð 2,943 ð ð ð ð

| 13:24 PMSD1 19.2 5.4 56 399 ð 73 2,889 ð ð ð ð

| 13:29 PMSD1 19.2 4.ð 52 159 ð 45 3,ð29 ð ð ð ð

| 13:34 PMSD1 19.2 4.1 54 131 ð 43 3,ð74 ð ð ð ð

| 13:38 PMSD1 19.2 5.9 81 2ð6 ð 61 2,762 ð ð ð ð

| CC13

| (26ð9)

| 13:14 PMSD2 19.2 4.6 63 16ð ð 49 3,ð44 ð ð ð ð

| 13:19 PMSD2 19.2 4.4 6ð 151 ð 47 3,ð72 ð ð ð ð

| 13:24 PMSD2 19.2 5.4 73 2ðð ð 56 3,ð55 ð ð ð ð

| 13:29 PMSD2 19.2 4.ð 45 226 ð 52 2,971 ð ð ð ð

| 13:34 PMSD2 19.2 4.1 43 263 ð 55 2,966 ð ð ð ð

| 13:38 PMSD2 19.2 5.9 61 411 ð 8ð 2,587 ð ð ð ð

Figure 7-64. Resource Interval Report: Communications Line Detail - SDLC

Communications Line Detail–X.25 Sample






| PROTOCOL = X.25 (SORT BY INTERVAL)

| Transmit/ Percent Percent

| IOP Receive/ Bytes Total I Frames Bytes Total Frames ------Reset------

| Itv Name/ Line Average Trnsmitd I Frames Trnsmitd Recd Frames Recd -----Packets-----

| End Line Speed Line Util Per Sec Trnsmitd In Error Per Sec Recd In Err Trnsmitd Recd

| ----- ---------- -------- ----------- ---------- ---------- ---------- --------- -------- -------- -------- -------

| CC13

| (26ð9)

| 13:14 PMX21 19.2 ð2/ð2/ð2 61 535 ð 52 1,ð7ð ð ð ð

| 13:14 PMX22 19.2 ð1/ð2/ð2 44 535 ð 68 1,ð7ð ð ð ð

| 13:19 PMX21 19.2 ð2/ð2/ð2 57 5ð4 ð 48 1,ðð8 ð ð ð

| 13:19 PMX22 19.2 ð1/ð2/ð2 41 5ð4 ð 63 1,ðð8 ð ð ð

| 13:24 PMX21 19.2 ð2/ð2/ð2 64 564 ð 54 1,128 ð ð ð

| 13:24 PMX22 19.2 ð1/ð2/ð2 47 564 ð 71 1,128 ð ð ð

| 13:29 PMX21 19.2 ð1/ð2/ð1 32 391 ð 49 782 ð ð ð

| 13:29 PMX22 19.2 ð1/ð1/ð1 44 391 ð 37 782 ð ð ð

| 13:34 PMX21 19.2 ð1/ð2/ð2 38 467 ð 58 934 ð ð ð

| 13:34 PMX22 19.2 ð2/ð1/ð2 52 467 ð 44 934 ð ð ð

| 13:38 PMX21 19.2 ð2/ð4/ð3 69 751 ð 1ð6 1,5ð2 ð ð ð

| 13:38 PMX22 19.2 ð3/ð3/ð3 95 751 ð 8ð 1,5ð2 ð ð ð

Figure 7-65. Resource Interval Report: Communications Line Detail - X.25

Communications Line Detail–TRLAN Sample







| PROTOCOL = TRLAN (SORT BY INTERVAL)

| ------- Congestion -------

| IOP I Frames I Frames -- Local -- -- Remote -- Rsp Remote LAN

| Itv Name/ Line Line Trnsmitd Recd Not Seq Not Seq Frame Timer -- Pct Frames -- MAC

| End Line Speed Util Per Sec Per Sec Ready Error Ready Error Retry Ended Trnsmitd Recd Errors

| ----- ---------- -------- ------- ---------- ---------- ----- ----- ----- ----- ------- ------ -------- ---- -------

| CCð4

| (2619)

| 13:14 .ð .ð ð ð ð ð ð ð ð ð ð 97 ð

| 13:19 .ð .ð ð ð ð ð ð ð ð ð ð 98 ð

| 13:24 .ð .ð ð ð ð ð ð ð ð ð ð 98 ð

| 13:29 .ð .ð ð ð ð ð ð ð ð ð ð 98 ð

| 13:34 .ð .ð ð ð ð ð ð ð ð ð ð 98 ð

| 13:38 .ð .ð ð ð ð ð ð ð ð ð ð 97 ð

| CCð6

| (2626)

| 13:14 TRNLINE 16ððð.ð .ð ð ð ð ð ð ð ð ð 3 8ð ð

| 13:19 TRNLINE 16ððð.ð .ð ð ð ð ð ð ð ð ð 6 85 ð


| 13:29 TRNLINE 16ððð.ð .ð ð ð ð ð ð ð ð ð 4 83 3



| CCð7

| (2619)

| 13:14 PMEC1 16ððð.ð .ð 3 3 ð ð ð ð ð ð 1ðð 1ðð ð



Figure 7-66. Resource Interval Report: Communications Line Detail - TRLAN

Communications Line Detail–ELAN Sample


| Communications Line Detail Page 1ð




| PROTOCOL = ELAN (SORT BY INTERVAL)

| -------------- Congestion --------------

| IOP I Frames I Frames ----- Local ----- ----- Remote ----- Rsp

| Itv Name/ Line Line Trnsmitd Recd Not Seq Not Seq Frame Timer

| End Line Speed Util Per Sec Per Sec Ready Error Ready Error Retry Ended

| ----- ---------- -------- ------ ---------- ---------- ------- ------- ------- ------- ------- -------

| CCð3

| (2617)

| 13:14 PMET2 1ðððð.ð .ð 3 3 ð ð ð ð ð ð





| 13:38 PMET2 1ðððð.ð .ð ð ð ð ð ð ð ð ð

| CCð5

| (2617)






| 13:38 PMET1 1ðððð.ð .ð ð ð ð ð ð ð ð ð

Figure 7-67. Resource Interval Report: Communications Line Detail–ELAN


Communications Line Detail–DDI Sample






| PROTOCOL = DDI (SORT BY INTERVAL)

| ------- Congestion -------

| IOP I Frames I Frames -- Local -- -- Remote -- Rsp

| Itv Name/ Line Line Trnsmitd Recd Not Seq Not Seq Frame Timer MAC

| End Line Speed Util Per Sec Per Sec Ready Error Ready Error Retry Ended Errors

| ----- ---------- -------- ------ ---------- ---------- ----- ----- ----- ----- ------- ------ -------

| CCð1

| (2618)

| 13:14 PMDD1 1ððððð.ð .ð 3 3 ð ð ð ð ð ð ð

| 13:19 PMDD1 1ððððð.ð .ð ð ð ð ð ð ð ð ð ð





| CCð2

| (2618)







Figure 7-68. Resource Interval Report: Communications Line Detail–DDI

Communications Line Detail–FRLY Sample






| PROTOCOL = FRLY (SORT BY INTERVAL)

| ------- Congestion -------

| IOP I Frames I Frames -- Local -- -- Remote -- Rsp

| Itv Name/ Line Line Trnsmitd Recd Not Seq Not Seq Frame Timer MAC

| End Line Speed Util Per Sec Per Sec Ready Error Ready Error Retry Ended Errors

| ----- ---------- -------- ------ ---------- ---------- ----- ----- ----- ----- ------- ------ -------

| CC1ð

| (2666)

| 13:14 PMFR1 56.ð .ð ð ð ð ð ð ð ð ð ð






| CC11

| (2666)







Figure 7-69. Resource Interval Report: Communications Line Detail–FRLY

Communications Line Detail–ASYNC Sample







| PROTOCOL = ASYNC (SORT BY INTERVAL)

| IOP Bytes Bytes Total Pct PDUs

| Itv Name/ Line Line Transmitted Received PDUs Received

| End Line Speed Util Per Sec Per Sec Received in Error

| ----- ---------- -------- ------ --------------- ------------ ------------ ------------

| CCð9

| (26ð9)

| 13:14 PMAS1 1.2 17.6 26 ð 1ð6 ð

| 13:19 PMAS1 1.2 1ð.ð 14 ð 64 ð

| 13:24 PMAS1 1.2 7.5 11 ð 55 ð

| 13:29 PMAS1 1.2 13.2 19 ð 72 ð

| 13:34 PMAS1 1.2 11.8 17 ð 47 ð

| 13:38 PMAS1 1.2 7.8 11 ð 36 ð

| CC13

| (26ð9)

| 13:14 PMAS2 1.2 17.7 ð 26 79 ð

| 13:19 PMAS2 1.2 1ð.2 ð 15 47 ð

| 13:24 PMAS2 1.2 7.5 ð 11 32 ð

| 13:29 PMAS2 1.2 13.2 ð 19 57 ð

| 13:34 PMAS2 1.2 11.8 ð 17 54 1

| 13:38 PMAS2 1.2 7.8 ð 11 29 ð

Figure 7-70. Resource Interval Report: Communications Line Detail–ASYNC

Communications Line Detail–BSC Sample






| PROTOCOL = BSC (SORT BY INTERVAL)

| Pct Data Pct Data

| IOP Bytes Total Data Characters Bytes Total Data Characters

| Itv Name/ Line Line Transmitted Characters Transmitted Received Characters Received Line

| End Line Speed Util Per Sec Transmitted in Error Per Sec Received in Error Errors

| ----- ---------- -------- ------ ------------- ------------- ------------- ---------- ------------ ------------ --------

| CC13

| (26ð9)

| 13:14 PMBS1 19.2 .9 7 2,36ð ð 13 4,124 ð ð

| 13:14 PMBS2 19.2 .9 13 4,124 ð 7 2,36ð ð ð

| 13:19 PMBS1 19.2 1.1 9 2,99ð ð 17 5,226 ð ð

| 13:19 PMBS2 19.2 1.1 17 5,226 ð 9 2,99ð ð ð

| 13:24 PMBS1 19.2 .9 8 2,568 ð 15 4,488 ð ð

| 13:24 PMBS2 19.2 .9 15 4,488 ð 8 2,568 ð ð

| 13:29 PMBS1 19.2 1.1 1ð 3,1ð3 ð 18 5,423 ð ð

| 13:29 PMBS2 19.2 1.1 18 5,423 ð 1ð 3,1ð3 ð ð

| 13:34 PMBS1 19.2 1.2 11 3,424 ð 19 5,984 ð ð

| 13:34 PMBS2 19.2 1.2 19 5,984 ð 11 3,424 ð ð

| 13:38 PMBS1 19.2 1.ð 9 2,463 ð 15 4,3ð2 ð ð

| 13:38 PMBS2 19.2 1.ð 15 4,3ð2 ð 9 2,463 ð ð

Figure 7-71. Resource Interval Report: Communications Line Detail - BSC

Communications Line Detail–ISDN Network Interface Sample


Resource Interval Report ð9/23/98 ð6:14:ð4

Communications Line Detail Page 15

Sample Resource Interval Report

Member . . . : ISDNDATA Model/Serial . : 5ðð-2142/1ð-1ðDFD Main storage . . : 32ð.ð M Started . . . : ð8/14/98 13:3ð:23

Library . . : ISDNDATA System name . . : ABSYSTEM Version/Release . : 4/2.ð Stopped . . . : ð8/14/98 13:45:27

PROTOCOL = ISDN NETWORK INTERFACE (SORT BY INTERVAL)

IOP --Outgoing--- ---Incoming--- LAPD LAPD Pct LAPD LAPD Pct

Name/ ---Calls----- ----Calls----- Total Frames Total Frames Loss of Local

Itv Network Line Pct Pct Frames Trnsmitd Frames Recd Frame End Code Collision

End Interface Speed Total Retry Total Reject Trnsmitd Again Recd in Error Alignment Violation Detect

----- ---------- ----- ------ ----- ------ ------ -------- -------- ------- -------- --------- --------- ---------

CCð5

(26ð5)

13:35 X31Nðð 16.3 ð ð ð ð 6ð ð 6ð ð ð ð ð

13:35 X31Nð1 16.3 ð ð ð ð 6ð ð 6ð ð ð ð ð

13:4ð X31Nðð 16.3 ð ð ð ð 6ð ð 6ð ð ð ð ð

13:4ð X31Nð1 16.3 ð ð ð ð 6ð ð 6ð ð ð ð ð

13:45 X31Nðð 16.3 ð ð ð ð 6ð ð 6ð ð ð ð ð

13:45 X31Nð1 16.3 ð ð ð ð 6ð ð 6ð ð ð ð ð

Itv End -- End time of the data collection interval or time that vary

off occurred

IOP Name/ -- IOP resource name and model number, Network interface description

Network Interface

Line Speed -- Line speed (1ððð bits per second)

Outgoing Calls Total -- Number of outgoing call attempts

Outgoing Calls -- Percent of outgoing calls that were rejected by the network

Pct Retry

Incoming Calls Total -- Number of incoming call attempts

Incoming Calls -- Percent of incoming calls that were rejected

Pct Reject

LAPD Total Frames -- Number of frames transmitted (applies to D-channel only)

Trnsmitd

LAPD Pct Frames -- Percent frames re-transmitted due to error (applies to

Trnsmitd Again D-channel only)

LAPD Total Frames -- Number of frames received (applies to D-channel only)

Recd

LAPD Pct Frames -- Percent frames received in error (applies to D-channel only)

Recd in Error

Loss of Frame -- Number of times a time period equivalent to two 48 bit frames

Alignment elapsed without detecting valid pairs of line code violations

Local End Code -- Number of unintended code violations detected by the TE

Violation for frames received on the T interface

Collision Detect -- Number of times that a transmitted frame corrupted by

another frame was detected

Figure 7-72. Resource Interval Report: Communications Line Detail - ISDN Network Interface

Communications Line Detail–NWI Maintenance Sample

Resource Interval Report 11/1ð/95 ð8:ðð:33



Member . . . : MONDAY Model/Serial . : 2ðð-2ð5ð/1ð-15ðð5ðð Main storage . . : 16ð.ð M Started . . . : 11/ð2/95 14:31:23

Library . . : QPFRDATA System name . . : ABSYSTEM Version/Release . : 3/ 6.ð Stopped . . . : 11/ð2/95 16:26:12

PROTOCOL = NWI MAINTENANCE CHANNEL (SORT BY INTERVAL)

IOP Percent

Name/ Percent Severely -----Detected Access----- Far End

Itv Network Line Errored Errored ----Transmission Error--- Code

End Interface Speed Seconds Seconds In Out Violation

----- ---------- -------- ------- -------- ---------- ---------- ----------

CC11

(2623)

14:46 ISDNSS_A 16.3 5ð 36 734 83 32

15:ð1 ISDNSS_A 16.3 6 24 32 14 52

15:16 ISDNSS_A 16.3 ð ð ð ð ð

Figure 7-73. Resource Interval Report: Communications Line Detail - NWI Maintenance Channel


Communications Line Detail–IDLC Samples

Resource Interval Report ð5/22/96 1ð:29:4ð


Member . . . : ECL Model/Serial . : 5ðð-2142/1ð-1ðDFD Main storage . . : 32ð.ð M Started . . . : ð4/15/96 1ð:35:3ð

Library . . : PM37CT System name . . : ABSYSTEM Version/Release . : 3/7.ð Stopped . . . : ð4/15/96 12:35:32

PROTOCOL = IDLC (SORT BY INTERVAL)

IOP Transmit/ ---Frames---- ---Frames----

Name/ Receive/ Bytes -Transmitted- Bytes --Received--- Receive Short

Itv Network Line Line Average Trnsmitd Pct Recd Pct CRC Aborts Sequence Frame

End Interface Descriptn Speed Line Util Per Sec Total Err Per Sec Total Err Errors Recd Error Errors

----- ---------- ---------- ----- --------- -------- --------- --- ------- --------- --- ------- ------- -------- -------

CCð5

(26ð5)

11:43 ISDNA IDLCAð1 64.ð ðð/ðð/ðð 42 49 4 33 47 2 ð ð ð ð

11:43 ISDNB IDLCBð1 64.ð ðð/ðð/ðð 2 1 ð ð ð ð ð ð ð ð

Figure 7-74. Resource Interval Report: Communications Line Detail–IDLC

Resource Interval Report ð5/22/96 1ð:29:4ð


Member . . . : ECL Model/Serial . : 5ðð-2142/1ð-1ðDFD Main storage . . : 32ð.ð M Started . . . : ð4/15/96 1ð:35:3ð

Library . . : PM37CT System name . . : ABSYSTEM Version/Release . : 3/7.ð Stopped . . . : ð4/15/96 12:35:32

PROTOCOL = IDLC (SORT BY INTERVAL)

IOP

Name/

Itv Network Line

End Interface Description Channel

----- ---------- ----------- -------

CCð5

(26ð5)

11:43 ISDNA IDLCAð1 B1

11:43 ISDNB IDLCBð1 B1

Figure 7-75. Resource Interval Report: Communications Line Detail - IDLC

IOP Utilizations–Sample


| Resource Interval Report ð9/15/98 1ð:54:ð2

| IOP Utilizations Page 45




| IOP Name/ Itv - IOP Processor Utils - DASD Ops per sec - KB per I/O - KBytes Transmitted Avail Local

| (Model) End Total Comm LWSC DASD Reads Writes Read Write IOP System Storage (K) Util 2

| ----------------- ----- ----- ----- ----- ----- ----------- ----------- ------- ------- ----------- ----------- ----------- ------

| CCð1 (2623) ðð:31 .3 .ð 1 ð 1,73ð .ð

| ðð:46 .3 .ð 1 ð 1,73ð .ð

| ð1:ð1 .3 .ð 1 ð 1,73ð .ð

| ð1:16 .3 .ð 1 ð 1,73ð .ð

| ð1:31 .2 .ð 1 ð 1,73ð .ð

| ð1:46 .3 .ð 1 ð 1,73ð .ð

| ð2:ð1 .2 .ð 1 ð 1,73ð .ð

| ð2:16 .3 .ð 1 ð 1,73ð .ð

| ð2:31 .2 .ð 1 ð 1,73ð .ð

| ð2:46 .2 .ð 1 ð 1,73ð .ð

| ð3:ð1 .2 .ð 1 ð 1,73ð .ð

| ð3:16 .2 .ð 1 ð 1,73ð .ð

| ð3:31 .2 .ð 1 ð 1,73ð .ð

| ð3:46 .2 .ð 1 ð 1,73ð .ð

| ð4:ð2 .2 .ð 1 ð 1,73ð .ð

| ð4:17 .2 .ð 1 ð 1,73ð .ð

| ð4:32 .2 .ð 1 ð 1,73ð .ð

| ð4:47 .3 .ð 1 ð 1,73ð .ð

| ð5:ð2 .2 .ð 1 ð 1,73ð .ð

| ð5:17 .2 .ð 1 ð 1,73ð .ð

| ð5:32 .2 .ð 1 ð 1,73ð .ð

| ð5:47 .3 .ð 1 ð 1,73ð .ð

| ð6:ð2 .2 .ð 1 ð 1,73ð .ð

| ð6:17 .2 .ð 1 ð 1,73ð .ð

| ð6:32 .2 .ð 1 ð 1,73ð .ð

| ð6:47 .2 .ð 1 ð 1,73ð .ð




| IOP Processor Util Total -- Total utilization for IOP

| IOP Processor Util Comm -- Utilization of IOP due to communications activity

| IOP Processor Util LWSC -- Utilization of IOP due to local workstation activity

| IOP Processor Util DASD -- Utilization of IOP due to DASD activity

| DASD Ops per sec Reads -- Number of reads per second

| DASD Ops per sec Writes -- Number of writes per second

| K Per Read -- Average number of kilobytes (1ð24) per read operation

| K Per Write -- Average number of kilobytes (1ð24) per write operation

| IOP KBytes Transmitted -- Number of Kbytes transmitted from the IOP to the system across the bus

| System KBytes Transmitted-- Number of Kbytes transmitted from the system to the IOP cross the bus

| Avail Local Storage (K) -- Number of kilobytes (1ð24) of local storage that is free

| Util 2 -- Utilization of co-processor

Figure 7-76. Resource Interval Report: IOP Utilizations

Local Work Station Response Times–Sample


Resource Interval Report ð9/24/98 ð7:4ð:58

Local Work Station Response Times Page 8

Sample Resource Interval Report

Member . . . : TEST2ð Model/Serial . : 5ðð-2142/1ð-317CD Main storage . . : 128.ð M Started . . . : ð9/19/98 16:47:34

Library . . : RWSDATA System name . . : ABSYSTEM Version/Release . : 4/2.ð Stopped . . . : ð9/19/98 17:12:36

IOP Name/ Work Station Itv Active Rsp

(Model) Controller End Util Wrk Stn ð.ð- 1.ð 1.ð- 2.ð 2.ð- 4.ð 4.ð- 8.ð > 8.ð Time

----------------- ------------ ----- ---- ------- --------- --------- --------- --------- ------- ------

WSð1 (916A) 16:52 2.6 ð ð ð ð ð ð .ðð

16:57 2.6 ð ð ð ð ð ð .ðð

17:ð2 2.6 ð ð ð ð ð ð .ðð

17:ð7 2.6 ð ð ð ð ð ð .ðð

17:12 2.7 ð ð ð ð ð ð .ðð

--------- --------- --------- --------- ------- ------

Total Responses: ð ð ð ð ð .ðð

IOP Name/ -- Input/Output processor resource name and

(Model) model number of the attached device

Work Station Controller -- Work station controller description name

Itv End -- Interval end time (hour and minute)

Util -- Percentage of utilization for each IOP

Active Wrk Stn -- Number of work stations with activity

ð.ð- 1.ð -- Number of response times between ð.ð and 1.ð seconds

1.ð- 2.ð -- Number of response times between 1.ð and 2.ð seconds



> 8.ð -- Number of response times > 8.ð seconds

Rsp Time -- Average external response time (in seconds) for

work stations on this controller

Figure 7-77. Resource Interval Report: Local Work Station Response Times

Remote Work Station Response Times–Sample

| Resource Interval Report ð9/24/98 ð7:4ð:58

| Remote Work Station Response Times Page 9


| Member . . . : TEST2ð Model/Serial . : 5ðð-2142/1ð-317CD Main storage . . : 128.ð M Started . . . : ð9/19/98 16:47:34

| Library . . : RWSDATA System name . . : ABSYSTEM Version/Release . : 4/2.ð Stopped . . . : ð9/19/98 17:12:36

| IOP Name/ Work Station Itv Active Rsp

| (Model) Controller End Wrk Stn ð.ð- 1.ð 1.ð- 2.ð 2.ð- 4.ð 4.ð- 8.ð > 8.ð Time

| ----------------- ------------ ----- ------- --------- --------- --------- --------- ------- ------

| CCð2 ( ) ABSYSTEM 16:52 1 162 ð ð ð ð .ð2

| 16:57 1 174 ð ð ð ð .ð2

| 17:ð2 1 195 ð ð ð ð .ð3

| 17:ð7 2 314 ð ð ð ð .ð2

| ---------- ---------- ---------- ---------- ---------- ------

| Total Responses: 845 ð ð ð ð .ð2



| Work Station Controller -- Work station controller description name


| Active Wrk Stn -- Number of work stations with activity

| ð.ð- 1.ð -- Number of response times between ð.ð and 1.ð seconds

| 1.ð- 2.ð -- Number of response times between 1.ð and 2.ð seconds



| > 8.ð -- Number of response times > 8.ð seconds

| Rsp Time -- Average external response time (in seconds) for

| work stations on this controller

Figure 7-78. Resource Interval Report: Remote Work Station Response Times

Batch Job Trace Report


Printing the Batch Job Trace ReportUse the Print Trace Report (PRTTRCRPT) command. Before you print the BatchJob Trace Report, you must use the Start Performance Monitor (STRPFRMON)command with the JOBTRCITV and JOBTYPE options and the Print TransactionReport (PRTTNSRPT) command with the *FILE option. The PRTTNSRPTcommand creates the QTRJOBT file that the Batch Job Trace Report uses.

What Is the Batch Job Trace Report?The Batch Job Trace Report shows the progression of different job types (forexample, batch jobs) traced through time. Resources utilized, exceptions, and statetransitions are reported.

See “Performance Report Columns” on page 7-102 for definitions of specificcolumns in the reports.

Job SummaryThe Job Summary section of the Batch Job Trace Report gives the number oftraces, the number of I/O operations, the number of seize and lock conflicts, thenumber of state transitions for each batch job.

See the sample report shown in Figure 7-79.

Job Summary Report–Sample

| Batch Job Trace Report 9/ð5/98 14:15:1ð

| Job Summary Page 1

| Sample Job Trace Report

| Member . . . : Q981421246 Model/Serial . : 5ðð-2142/1ð-18ð3D Main storage . . : 128.ð M Started . . . . : ð5/22/98 12:47:35

| Library . . : THREAD1 System name . . : ABSYSTEM Version/Release : 4/ 2.ð Stopped . . . . : ð5/22/98 12:52:38

| ---- Physical ---- Seize --- State ---

| Job User Job -- Job -- Number CPU ---- I/O Count ---- and Lock --- Transitions ---

| Name Name Number Pool Type Pty Traces Util Sync Async Conflicts A-A A-I

| ---------- ---------- ------ ---- ---- --- ------ ---- ---------- ---------- --------- --------- ---------

| QPFRMON QPGMR ð13842 ð2 B ð 5 11.7 6ð4 235 ð 1 ð

| Job Name -- Name of the job

| User Name -- User name

| Job Number -- Job number

| Pool -- Pool in which the job ran

| Job Type -- Job type and subtype

| Job Pty -- Priority of the job

| Number Traces -- Number of traces


| Physical I/O Count

| Sync -- Number of synchronous I/O operations

| Async -- Number of asynchronous I/O operations

| Seize and Lock Conflicts -- Number of seize conflicts and lock waits

| State Transitions A-A -- Number of active-to-active transitions

| State Transitions A-I -- Number of active-to-ineligible transitions

Figure 7-79. Sample of Job Summary Report

Performance Trace Database FilesThe Print Transaction Report (PRTTNSRPT) command has options to build for-matted database files. These files can extend your performance analysis capabili-ties beyond what the standard trace reports provide.

Using parameters on this command, you can specify a combination of reports andfiles to be built in a single run, select specific time ranges and jobs, and limit the


amount of report and file data produced. If you specify *FILE on the RPTTYPEparameter of the PRTTNSRPT command, the transaction report creates the filesQTRTSUM, QTRJSUM, and QTRJOBT. If you specify *TRCDTA on the RPTTYPEparameter of the PRTTNSRPT command, the report creates the file QTRDMPT.

QTRTSUM and QTRJOBT FilesThe transaction summary file (QTRTSUM) and job TSE (time slice end)(QTRJOBT) files have the same format; however, they represent different types ofinformation.

� QTRTSUM (transaction summary) file contains one record for every interactivetransaction identified by the PRTTNSRPT command.

� QTRJOBT (job time slice end) file contains one record per time slice end for alljobs. Time slice end records are created if the job CPU usage reaches one ofthe following values:

– External CPU time slice value

– An internal time slice value defined by the Start Performance Monitor(STRPFRMON) command.

In the QTRTSUM file, the summary data represents the activity for the transaction.In the QTRJOBT file, the summary data represents activity that has occurred sincethe last TSE or other multiprogramming level trace record.

Table 7-7 (Page 1 of 4). QTRTSUM File

Field Name Description

TRNYEAR Transaction start year

TRNMONTH Transaction start month

TRNDAY Transaction start day

TRNHOUR Transaction start time hour

TRNMIN Transaction start time minute

TRNSEC Transaction start time second

TRNSECD Transaction start time decimal (milliseconds)

TRQUAL Trace qualifier (QTRJOBT file only)

� 139–Job external time slice end.

� 145–Job internal time slice end (the CPU time used). The value is specified in theJOBITVTRC parameter on the STRPFRMON command.

TSKJOB Job name

TSKUSR User name

TSKNUM Task number

TDENUM TDE number (system assigned)

TSPOOL Main storage pool in which the job ran

TPRTY Current job priority

TTYPE Job type and subtype.

Refer to explanation of the Typ field in “Job Summary Section” on page 7-38 for a list oftypes and subtypes.




TPURGE Purge attribute (Y/N). Defines whether or not the job is eligible to have its PAG purged atthe end of the transaction.

TRSP Response time (in seconds). The time from the first W→A transition to the last A→W tran-sition in the transaction.

TCPU CPU time (in seconds) used by this job during the transaction. It does not include the CPUtime for asynchronous server tasks such as Licensed Internal Code work station IOM,asynchronous disk I/O tasks, and others

TSDBRD Synchronous database reads (count)

TSDBWRT Synchronous database writes (count)

TSNDBRD Synchronous nondatabase reads (count)

TSNDBWRT Synchronous nondatabase writes (count)

TADBRD Asynchronous database reads (count)

Refer to the IOPND and SYSYNC fields in the QAITMON file created by theWRKSYSACT command or to the JBIPF and JBIOW fields in the QAPMJOBS sampledata file created by the STRPFRMON command for the job to see how many asynchro-nous disk reads were turned into synchronous reads.

TADBWRT Asynchronous database writes (count)

TANDBRD Asynchronous nondatabase reads (count) (See field TADBRD.)

TANDBWRT Asynchronous nondatabase writes (count)

TPAGFLT Process access group (PAG) faults (count)

TBIN Binary overflow count

TDEC Decimal overflow count

TEAOCNT Reserved

TCHKSUM Reserved

TACT Time in the activity level (in seconds)

TWAIT Short wait time in the activity level (in seconds)

TINELW Wait-to-ineligible (W→I) transition time waiting for activity level (in seconds). This occursafter coming out of a long wait such as start of transaction or the end of a lock wait.

TINELA Active-to-ineligible (A→I) time slice end (TSE) transition time waiting for activity level (inseconds). This occurs after leaving the activity level at external time slice end becauseother equal or higher priority jobs were waiting for an activity level.

TAICNT The number of active-to-ineligible (A→I) transitions. The number of external time sliceends that caused the job to leave the activity level because there were equal or higherpriority jobs waiting for an activity level.

TAACNT The number of active-to-active (A→A) transitions. The number of external time slice endsthat did not cause the job to leave the activity level because there were no equal or higherpriority jobs waiting for an activity level.




TEXWTM Total exceptional wait time (in seconds). Sum of the following fields:

TINELA Active-ineligible wait

TWAIT Short wait

TSWXTM Short wait extended

TSZTM Seize wait

TLCKTM Lock wait

T3270 3270 wait

TDDM DDM wait

TEVTM Event wait

TXATM Total excess active time (added only for interactive jobs)

TDELTM Delay time (added only for noninteractive jobs)

no-name Miscellaneous wait time. For example save/restore, diskette, or tape mount andrespond to mount message.

TSWTM Total short wait time (in seconds). Short wait time (SW time in the transaction reports) isthe time spent waiting for an event (such as work station output complete) while remainingin the active state. When the short wait ends (it ends automatically after 2 seconds), thejob goes into the short wait extended state.

TSWXTM Total short wait extended (short wait time-out) time (in seconds). See field TSWTM. Duringthe time a job is in short wait extended (abbreviated SWX in the transaction reports), itdoes not hold an activity level (it is in the wait state). The short wait is satisfied when thewaited-on event occurs.

TSWXCNT Total number of short waits extended. The number of short waits where the job was takenout of the activity level after 2 seconds and put into long wait (an A→W transition).

TSZTM Total seize conflict wait time (in seconds). Total time this job waited in the activity level forseize conflicts.

TLCKTM Total lock conflict wait time (in seconds). Total time this job waited outside the activitylevel for lock conflicts.

THOLDTM Total seize/lock conflict hold time to other jobs. The field contains the total time that otherjobs waited for objects held by this job. For example, when a job held an object for 2seconds and for that time two other jobs waited for the object, the THOLDTM value wouldbe 4.

TEVTM Total event wait time (in seconds)

TXATM Total excess active time (in seconds). A calculated value, not a measured value, thatrepresents the time a job was in the activity level, could not use the CPU, and is notaccounted for by other measurements. It can be the result of waiting behind equal orhigher priority jobs for the CPU, waiting to do disk I/O, or waiting for an internal, non-instrumented object such as the free space lock on storage management.

T3270 Total 3270 emulation wait time

TDDM Total DDM wait time (in seconds)

TMRT Total MRT wait time (in seconds)

TDELTM Total long wait time (in seconds) such as key/think wait time or delay time

TSZLCKCT Seize and lock conflicts encountered by this job (count)

TSZLCKRL Seize and lock releases done by this job when other jobs waited (count)

TBMPL Number of jobs holding an activity level in this job's pool at transaction start (count)




TIMPL Number of jobs waiting for activity level in this job's pool at transaction start (count)

TPGM1 First program name in stack at the end of transaction

TPGM2 Second program name in stack at the end of transaction

TPGM3 Third program name in stack at the end of transaction

TPGM4 Fourth program name in stack at the end of transaction

TPGM Program that caused transaction (one of these field names is the application in control ofthe transaction)

TELAP Elapsed time of transaction (in seconds)

TPVPGM Previous program name

TIPRTY Assigned job priority

| TTHID| Thread identifier

| TTHFLG| Secondary thread flag (0=primary thread, 1=secondary thread)

QTRJSUM FileThe job summary file QTRJSUM contains one record for each job or task listed onthe PRTTNSRPT job summary report.

Table 7-8. QTRJSUM File


TDENUM TDE number. Licensed Internal Code task dispatching element.

JOBID Job name or user name

| USERID| User ID

JOBNUM Job number

POOL Storage pool the job started in

JOBTYP Job type code


TRCPER Trace period sequence number (reserved)

JDATE Job start date MM/DD/YY

JSTART Job start time HH:MM:SS

JSTOP Job stop time HH:MM:SS

JELAP Job total elapsed time (in seconds)

JCPU Job total CPU time (in seconds)

JDBIO Job total disk database reads

JNDBIO Job total disk nondatabase reads

JWRTIO Job total disk writes


The following fields are totals for the duration of the job, unless the beginning or end time selection option wastaken on the PRTTNSRPT command. Then the values are for the selected time only.

TRNNUM Total number of transactions (type I jobs only)

JBEG Transaction report selection beginning time HHMMSS

JEND Transaction report selection ending time HHMMSS

JOBELP Total elapsed time (in seconds) for the job (job start to job end)

JOBCPU CPU time (in seconds) the job used

JOBDB Total disk database reads

JOBNDB Total disk nondatabase reads

JOBWRT Total disk writes

JARSP Average transaction response time (in seconds) (type I jobs only)

JMRSP Maximum transaction response time (in seconds) (type I jobs only)

JACPU Average CPU time per transaction (in seconds) (type I jobs only)

JMCPU Maximum CPU time by a transaction (in seconds) (type I jobs only)

JADBR Average disk database reads per transaction (type I jobs only)

JANDBR Average disk nondatabase reads per transaction (type I jobs only)

JAWRT Average disk writes per transaction (type I jobs only)

JAIO Average disk I/O per transaction (type I jobs only)

JMIO Maximum disk I/O by a transaction (type I jobs only)

JWI Total number of W→I transitions

JAI Total number of A→I transitions

JLCKS Total number of lock conflicts

JATM Total time the job was in an activity level (in seconds)

JWTM Total short wait time in an activity level (in seconds)

JINELW Total ineligible time as a result of wait-to-ineligible transitions (in seconds)

JINELA Total ineligible time as a result of active-to-ineligible transitions (in seconds)

JLKWTM Total wait time for short wait and short wait extended, QEM wait, DDM wait, andsave/restore, diskette, or tape wait.

JKYTK Total key/think time (in seconds)

TSKID Combined job name, user ID, and user name fields

JSPRTY Assigned job priority

| JTHID| Thread identifier

| JTHFLG| Secondary thread flag (0=primary thread, 1=secondary thread)


QTRDMPT FileThe QTRDMPT file is a version of the QAPMDMPT file formatted as a databasefile. It gives you access to each performance monitor trace record created. TheQAPMDMPT file is built when the performance monitor ends, tracing is specified,and the monitor is directed to dump the internal trace data to a database file. TheQAPMDMPT file can also be built with the DMPTRC command after the monitorshuts down.

The field names shown below without asterisks contain information taken directlyfrom the QAPMDMPT file. Field names shown below with an asterisk (*) in front ofthem contain information created by the transaction report. Unless otherwise speci-fied, numeric values are in decimal.

Table 7-9 (Page 1 of 4). QTRDMPT File


DSEQNM Sequence number in QAPMDMPT (relative record in file)

DTID Trace ID in hexadecimal

X'68' Resource management (seize/lock activity)X'70' MPL trace record (job state transitions)X'73' Trace control record (job/task start/stop/existence)X'AB' Transaction boundary trace recordX'AC' Transaction boundary trace record–source pass-through, target pass-through,and WSF (work station function) target pass-through

All other trace identifiers are ignored by the transaction report.




DTQUAL Trace qualifier

If DTID = X'68' seize/lock trace (Licensed Internal Code tasks or OS/400 jobs), the tracequalifiers are:

701 Job/task entered seize conflict wait1001 Job/task released seize that is being waited on903 Job entered lock conflict wait906 Job released lock that is being waited on

If DTID = X'70' MPL trace (OS/400 jobs only), the valid trace qualifiers for active statecodes are:

129 Ineligible-to-active transition131 Message received and job was in current activity level when the message wasreceived133 Dequeue after time-out; job in current activity level when the message wasreceived

135 Wait-to-active137 Wait timed out, no message received; wait-to-active139 Active-to-active (job external time slice end)142 Wait-to-active (job is already in activity level)145 STRPFRMON pseudo TSE; active-to-active

The trace qualifiers for wait state codes are:

128 Just initiated job cannot get into activity level130 Active-to-wait transition; drop from activity level132 Wait-to-ineligible transition134 Active-to-wait but stay in activity level136 Time slice end; active-to-ineligible

If DTID = X'73' control trace (OS/400 jobs and SLIC tasks), the valid qualifiers are:

130 Job started while trace was active133 Job ended while trace was active127 Job active at start of trace136 Job active at end of trace129 SLIC task started while trace was active132 SLIC task ended while trace was active126 SLIC task active at start of trace135 SLIC task active at end of trace

DTRDAT Transition date YYYYMMDD

DTRTM Transition time HHMMSSmmm

DTRHR Transition hour xx.xxxxxxx

DTRELP Elapsed seconds from previous state

*DPVDAT Previous transition date YYYYMMDD

*DPVTM Previous transition time HHMMSSmmm

*DPVHR Previous transition hour xx.xxxxxxx

DTDEHX TDE number in hexadecimal

DSPOOL Pool number in which job ran

DPRTY Current job priority

DTYPE Job type and subtype.





DPURGE Job purge attribute: 0=No, 1=Yes

DCPU Total CPU time (in seconds)

*DLPCPU CPU time since last job state transition (in seconds)

*DCPUPC Percentage of CPU usage since last job state transition

DJOBNM Job name

DUSRNM User name

DJOBNB Job number

*DTRSTA Transition to this state; this matches what is shown in the Transition Report

*DTRWAT Transition wait code; this matches what is shown in the Transition Report

DMPL Current number of pool activity levels in use

DIPL Number of ineligible jobs waiting for pool activity level

DCSDR Synchronous database reads (cumulative)

*DISDR Synchronous database reads (since last transition)

DCSDW Synchronous database writes (cumulative)

*DISDW Synchronous database writes (since last transition)

DCSNR Synchronous nondatabase reads (cumulative)

*DISNR Synchronous nondatabase reads (since last transition)

DCSNW Synchronous nondatabase writes (cumulative)

*DISNW Synchronous nondatabase writes (since last transition)

DCADR Asynchronous database reads (cumulative)

*DIADR Asynchronous database reads (since last transition)

DCADW Asynchronous database writes (cumulative)

*DIADW Asynchronous database writes (since last transition)

DCANR Asynchronous nondatabase reads (cumulative)

*DIANR Asynchronous nondatabase reads (since last transition)

DCANW Asynchronous nondatabase writes (cumulative)

*DIANW Asynchronous nondatabase writes (since last transition)

DCPAG Process access group (PAG) faults (cumulative)

*DIPAG Process access group (PAG) faults (since last transition)

DCEAO Reserved

*DIEAO Reserved

DCCKSM Reserved

*DICKSM Reserved

DCDEC Decimal overflow exceptions (cumulative)

*DIDEC Decimal overflow exceptions (since last transition)

DCBIN Binary overflow exceptions (cumulative)

*DIBIN Binary overflow exceptions (since last transition)

DCFLP Floating point overflow exceptions (cumulative)




*DIFLP Floating point overflow exceptions (since last transition)

DCPWT Permanent writes (cumulative)

*DIPWT Permanent writes (since last transition)

DPGM1 Program 1 (last) (DTID = X'70' only)

DPGM2 Program 2 (second from the last) (DTID = X'70' only)

DPGM3 Program 3 (third from the last) (DTID = X'70' only)

DPGM4 Program 4 (fourth from the last) (DTID = X'70' only)

Resource management data. The following three fields contain valid information only for records that haveDTID=X'68' (Resource Management Trace).

DSLJOB Job/task name of seize/lock waiter/holder

DSLUSR User name of seize/lock waiter/holder

DSLNBR Job number of seize/lock waiter/holder

The following five fields can have data that is not valid if the object was destroyed before the trace was dumpedto the QAPMDMPT file.

DSLOTY Seize/lock object type

Note: Object types and codes can be found in AS/400 Licensed Internal Code DiagnosticAids - Volume 1.

DSLOLB Seize/lock object library name (may be undefined for machine objects) A machine objectis a program object that has no defined storage form; the object is defined internally to themachine.

DSLOFL Seize/lock object file/object name (may be undefined for machine objects)

DSLOMB Seize/lock object member name (database files only)

DSLRRN Relative record number of the lock database file (if report is run on same system that itwas collected on and the file still exists)

DRSVD1 Reserved

DRSVD2 Reserved

Transaction boundary information. These fields contain valid information only for trace records with DTID = X'AB'or X'AC'.


DTNTY Transaction type (in decimal)

1 Display I/O2 Data queue

3 MRT4 Source pass-through5 Target pass-through6 WSF target pass-through

DTNSTY Transaction subtype (in decimal)

If DTNTY = 1, 2, or 3:

1 Start transaction2 End transaction3 End response time transaction (for DTNTY = 1 only)

IF DTNTY = 4, 5, or 6:

1 Start transaction2 End transaction3 Start session4 End session

DTNBIT Reserved

DTNNM1 Name of display device for display I/O transactionsName of data queue library for data queue transactionsName of display device for MRT transactionsName of device description for pass-through transactions

DTNNM2 Name of display file for display I/O transactionsName of data queue for data queue transactionsName of display file for MRT transactionsName of target control point for source pass-through transactionsName of source control point for target pass-through transactionsName of controller description for WSF target pass-through transactions

DTNNM3 Reserved

DTNNM4 Reserved

DTNDAT Date of transaction YYYYMMDD

DTNTM Time of transaction HHMMSSmmm

DTNHR Hour of transaction xx.xxxxxxx

*DTNBDY Transaction boundary flag:

Set to 1 if this trace record is at a transaction boundary; set to 0 if it is not at a transactionboundary.

DTNID Reserved

DIPRTY Assigned job priority

| DTHID| Thread identifier

| DTHFLG| Secondary thread flag (0=primary thread, 1=secondary thread)


QAPTLCKD FileQAPTLCKD is the file created by using the Print Lock Report (PRTLCKRPT) frominformation in the QAPMDMPT trace data file. This file contains data on seizes andlocks. Table 7-10 shows a description of each field in the QAPTLCKD file.

Table 7-10 (Page 1 of 2). QAPTLCKD File


SLWTOD Time of day (HH.MM.SS) that the requesting job REQNAM had either a seize or lock con-flict on the object OBJNAM that was held by job HLDNAM.

SLWLEN Length of time (in milliseconds) from the start of the object conflict until the holding jobreleased the object. This is not necessarily the amount of time that the requesting job isdelayed in getting the object. That time may be longer than the conflict delay.

SLCODE The type of conflict: blank = Seize, L = Lock. Seizes occur only in Licensed Internal Codeor implicitly within high-level MI instructions such as Create Object or Add to a File. Locksoccur in jobs running in the OS/400 program and can be explicitly requested.

REQTDE Requesting job's TDE number

REQNAM Requesting job's name, user ID, job number

Position Value

1-10 Job name

12-21 User name

23-28 Job number

| REQTTH| Requesting job's thread identifier

HLDTDE Holding job's TDE number

HLDNAM Holding job's name, user ID, job number

Position Value

1-10 Job name

12-21 User name

23-28 Job number

| HLDTTH| Holding job's thread identifier

OBJADR The address of the object

Position Value

1-8 Segment address

9-12 Offset

Note: AS/400 Licensed Internal Code Diagnostic Aids - Volume 1 contains a descriptionof the system's preassigned addresses.


Table 7-10 (Page 2 of 2). QAPTLCKD File


OBJNAM The object type, name, library (if applicable), and member (if applicable)

Position Value

1-6 Object type description

8-17 Name

19-28 Library

30-39 Member (database files and indexes)

In some cases the object type may not be translated; instead it may be a 2-bytehexadecimal code. If the object name is not meaningful, it is possible that the objectaddress is one of the system's preassigned addresses. AS/400 Licensed Internal CodeDiagnostic Aids - Volume 1contains more information on these objects and codes.

OBJRRN Database file record number. Valid only for type DS (data space) when the Print LockReport (PRTLCKRPT) command created the QAPTLCKD file on the same system that thedata was collected on.

Performance Report Columns>8.0 (Component) The number of times the response time was greater than 8

seconds.

---------- (pgmname) (Transaction) The transaction totals record. For example,---------- QUYLIST, as shown in Figure 7-49 on page 7-62. This reportline occurs each time the job has an active-to-wait transaction. Totalsare created for Rsp* (response time), CPU Secs, and I/O counts for thetransaction.

A-I Wait /Tns (Transaction) The average time, in seconds, of active-to-ineligiblewait time per transaction. If this value is high, it may be because thetime-slice value is set too low for many of the interactive jobs. Considerincreasing the time slice-value.

Aborts Recd (Resource Interval) The number of frames received that containedHDLC abort indicators. This indicates that the remote equipment endedframes before they were complete.

Act Jobs (Job Interval) The number of selected jobs (interactive or noninteractive,depending on the report section) that were active during the interval.

Act Level (Component) Initial pool activity level.

Act Lvl (System, Pool Interval) Activity level. For the Pool Activity section of thePool Interval Report, the activity level of the pool during the interval. Forthe Storage Pool Utilization section of the System Report, the activitylevel at the time of the first sample interval.

Act-Inel (System, Component) Average number of active-to-ineligible job statetransitions per minute.

Act-Wait (System, Component) Number of transitions per minute from active stateto wait state by processes assigned to this pool.

Active Devices (System) Average number of active devices on the line.


Active display stations (local or remote) (System) The number of local or remotedisplay stations entering transactions during the measurement period.

Active Jobs (Transaction) The number of interactive jobs that were active duringthe interval.

Active Jobs Per Interval (System) Average number of jobs of this type that wereactive per sample interval.

Active K/T /Tns (Transaction) An average think time and keying time (or the delaytime between the end of one transaction and the start of the next trans-action), in seconds, for the active work stations (described under Est ofAWS). Active K/T /TNS delay time differs from Key/Think /TNS delaytime in that any delay time greater than 600 seconds has been roundedto 600 seconds. This technique is used to reduce the effect of verycasual users (those who may do intermittent work or leave their workstations for long periods of time) on the estimate of active work stations.

Active Wrk Stn (Resource Interval) The number of work stations with activity.

Active/Rsp (Transaction) The time the job spends (either waiting or active) duringtransaction processing, while it holds an activity level.

Activity level (System) The sum of activity levels for all interactive pools that hadinteractive job activity running in them.

Activity Level Time (Transaction) A breakdown of the transaction time spentACTIVE, waiting on a SHORT WAIT, and waiting on a SEIZE/CFT(seize conflict). The SHORT WAIT and SEIZE CFT time are includedunder ACTIVITY LEVEL TIME, because the activity-level slot is notgiven up during these times. Note that the seize conflict time is includedin the active time, not added to it to get transaction/response time, as isthe case for waiting time.

Arith Ovrflw (Component, Job Interval) The number of arithmetic overflowexceptions that occurred for the selected interactive jobs during theinterval.

ASP ID (System, Resource Interval) Auxiliary storage pool identifier.

Async (System, Component, Transaction, Job Interval) The number of asyn-chronous disk I/O operations started by the selected interactive jobsduring the interval. The job that starts the I/O operation may continueprocessing without having to wait for the I/O operation to complete. TheI/O operation is completed by a background system test.

Async DIO /Tns (Transaction) The sum of the averages of the asynchronous DBREAD, DB WRITE, NDB READ, and NDB WRITE requests (the averagenumber of asynchronous I/O requests per transaction for the job).

Async Disk I/O (System, Component, Transaction) Number of asynchronous diskinput/output operations per transaction.

Async Disk I/O per Second (Component) Average asynchronous disk I/O oper-ations per second.

Async Disk I/O Requests (Transaction) The total number of asynchronous disk I/Orequests for the given combination of priority, job type, and pool.

Async I/O /Sec (Job Interval) The average number of asynchronous disk I/O oper-ations started per second by the job during the interval. This is calcu-lated by dividing the asynchronous disk I/O count by the elapsed time.


Async I/O Per Second (Job Interval) The average number of asynchronous diskI/O operations started per second by the selected noninteractive jobsduring the interval.

Async Max (Transaction) Listed under Average DIO/Transaction, the maximumnumber of asynchronous DBR, NDBR, and WRT I/O requests encount-ered for any single transaction by that job. If the job is not an interactiveor autostart job type, the total disk I/O for the job is listed here.

Async Sum (Transaction) Listed under Average DIO/Transaction, the sum of theaverages of the asynchronous DBR, NDBR, and WRT requests (theaverage number of asynchronous I/O requests per transaction for thejob).

Asynchronous DBR (System, Job Interval, Pool Interval) The average number ofasynchronous database read operations on the disk per transaction forthe job during the intervals. This is calculated by dividing the asynchro-nous database read count by the transactions processed. This field isnot printed if the jobs in the system did not process any transactions.For the Resource Utilization section of the System Report, it is thenumber of asynchronous database read operations per second.

Note: The asynchronous I/O operations are performed by system asyn-chronous I/O tasks.

Asynchronous DBW (System, Job Interval) The average number of asynchronousdatabase write operations on the disk per transaction for the selectedjobs during the interval. This is calculated by dividing the asynchronousdatabase write count by the transactions processed. This field is notprinted if the jobs in the system did not process any transactions. Forthe Resource Utilization section of the System Report, it is the numberof asynchronous database read operations per second.


Asynchronous disk I/O per transaction (System) The average number of asyn-chronous physical disk I/O operations per interactive transaction.

Asynchronous NDBR (System, Job Interval, Pool Interval) The average number ofasynchronous nondatabase read operations per transaction for the jobsin the system during the interval. This is calculated from the asynchro-nous nondatabase read count divided by the transactions processed.This field is not printed if the jobs in the system did not process anytransactions. For the Resource Utilization section of the System Report,it is the asynchronous nondatabase read operations per second.


Asynchronous NDBW (System, Job Interval, Pool Interval) The average numberof asynchronous nondatabase write operations per transaction for thejobs in the system during the interval. This is calculated from the asyn-chronous nondatabase write count divided by the transactions proc-essed. This field is not printed if the jobs in the system did not processany transactions. For the Resource Utilization section of the SystemReport, it is the number of asynchronous nondatabase write operationsper second.



Aut Lookup (Component) Number of authority lookups per second. An authoritylookup is the process whereby the Licensed Internal Code determineswhether a particular user ID is authorized to access a specific object.

| Beginning in V3R7, reduced instruction set computer (RISC) systems| store the most recent private authority lookup results in an authorization| lookup cache. If the next lookup is for one of the authorities stored in the| cache, the private authority lookup has a minimal performance degrada-| tion over public or owner authority performance.

| The cache can store up to 32 private authorities for objects and for| authorization lists. Whenever the system looks for a private authority,| the system queries the cache. Whenever an authority is granted or| revoked for a user, the cache is updated. Performing an IPL clears the| cache.

| The performance monitor counts each authority lookup. The advisor| function and the redbook, AS/400 Performance Management| V3R6/V3R7, SG24-4735, provide CPU utilization estimates based on the| number of lookups per second and the processor rating. Because of this| caching capability, the counts are incremented as if they were not| cached. Therefore, beginning with V3R7, the effect on the CPU utiliza-| tion counts could be much less than the advisor message and the| redbook would indicate.

Avail Local Storage (K) (Resource Interval) The number of kilobytes of free localstorage in the IOP.

Available Storage (Component) Available local storage (in bytes). The averagenumber of bytes of available main storage in the IOP. The free localstorage is probably not joined because it has broken into small pieces.

Average (Transaction) The average value of the item described in the column forall transactions.

Average Disk Activity Per Hour (Component) See Disk Arm Seek Distance

Average DIO/Transaction (Transaction) Seven columns of information about phys-ical disk I/O counts. Physical I/O contrasts with logical I/O shown else-where in these reports. A logical I/O is a request sent at the programlevel that might result in an access to auxiliary storage (DASD). A phys-ical I/O refers to those requests that actually result in access to auxiliarystorage.

� Synchronous DBR

� Synchronous NDBR

� Synchronous Wrt

� Synchronous Sum

� Synchronous Max

� Async Sum

� Async Max

Average K per I/O (Resource Interval) The average number of kilobytes trans-ferred during each disk read or write operation.


Average Phys I/O /Sec (Resource Interval) The average number of physical diskread and write operations per second made on all disks on the system.

Average Reads/Sec (Resource Interval) The average number of physical disk readoperations per second made on all disks on the system.

Average Response (System) Average response time (in seconds) for interactivetransactions. The Total/Average interactive response time does notinclude transactions for DDM server jobs.

Average Response Time (System) Average disk response time per I/O operation.

Average Response Time (seconds) (System) The average interactive responsetime.

Average Service Time (System) Average disk service time per I/O operation. Thisis the amount of time a request would take if there were no contention.

Average Wait Time (System) Average disk wait time per I/O operation. Normallydue to contention.

Average Writes/Sec (Resource Interval) The average number of physical disk writeoperations per second made on all disks on the system.

Avg CPU /Tns (Transaction) The average number of processing unit seconds pertransaction that fell in the given category.

Avg K/T /Tns (Transaction) The average think time and keying time (or the delaytime between transaction boundaries), in seconds, for the interactivejobs.

Avg Length (Lock) The average number of milliseconds a lock or seize was held.

Avg Rsp (Sec) (Transaction) The average transaction response time in seconds.

Avg Rsp /Tns (Transaction) The average response per transaction (in seconds) forthe transactions that fell into the given category.

Avg Rsp Time (Component) Average transaction response time.

Avg Sec Locks (Transaction) The average length of a lock in seconds attributed tointeractive or noninteractive waiters.

Avg Sec Seizes (Transaction) The average length of a seize in seconds attributedto interactive or noninteractive waiters.

Avg Time per Service (Resource Interval) The amount of time a disk arm uses toprocess a given request.

Avg Util (System, Resource Interval) On the Disk Utilization Summary of theResource Report, the average percentage of available time that diskswere busy. It is a composite average for all disks on the system. On theCommunications Summary of the System Report, the average per-centage of line capacity used during the measured time interval.

Batch asynchronous I/O per second (System) The average number of asynchro-nous physical disk I/O operations per second of batch processing.

Batch CPU seconds per I/O (System) The average number of system processingunit seconds used by all batch jobs for each I/O performed by a batchjob.


Batch CPU Utilization (Component) Percentage of available CPU time used by thefollowing types of jobs:

� Batch

� Autostart

� Evoke

� SCPF (Start CPF), spool reader/writer

Note: For a multiple-processor system, this is the average use acrossall processors.

Batch impact factor (System) Batch workload adjustment for modeling purposes.

Batch permanent writes per second (System) The average number of permanentwrite operations per second of batch processing.

Batch synchronous I/O per second (System) The average number of synchro-nous physical disk I/O operations per second of batch processing.

BCPU / Synchronous DIO (Transaction) The average number of batch processorunit seconds per synchronous disk I/O operation.

Bin (Transaction) The number of binary overflow exceptions.

Binary Overflow (Component) Number of binary overflows per second.

BMPL - Cur and Inl (Transaction) The number of jobs currently in the activity level(beginning current multiprogramming level), and the number of jobs onthe ineligible queue (beginning ineligible multiprogramming level) for thestorage pool that the job ran in when the job left the wait state (thebeginning of the transaction).

Note: Multiprogramming level (MPL) is used interchangeably withactivity level.

Bundle Writes System (Component) Number of bundle writes to internal systemjournals. A bundle write is a group of journal entries which are depositedtogether by the system.

Bundle Writes User (Component) Number of bundle writes to user-created jour-nals. A bundle write is a group of journal entries which are depositedtogether by the system.

Bytes per Second Received (System) Average number of bytes received persecond.

Bytes per Second Transmitted (System) Average number of bytes transmitted persecond.

Bytes Recd per Sec (Resource Interval) The average number of bytes receivedper second.

Bytes Trnsmitd per Sec (Resource Interval) The average number of bytes trans-mitted per second.

Category (Transaction) A group of transactions categorized together. In the Anal-ysis by Interactive Transaction Category, the transactions are categor-ized by the processing unit model. The boundary values that are used toseparate the transactions are given in the Avg CPU /Tns column. Forthe Analysis by Interactive Response Time, they are categorized by theirresponse time. For the Analysis by Interactive Key/Think Time, they arecategorized by their key/think time.


Cache Hit Statistics (Component) Statistics data about use of cache including:

� The percent of Device Cache Read Hit for each arm.

� The percent of Controller Cache Read Hit for each arm.

� The percent of efficiency of write cache

Device read Device Read is the number of Device Cache Read Hits(DSDCRH) divided by number of Device Read Operations(DSDROP), expressed as a percent

Controller read Controller Read is the number Controller Cache ReadHits (DSCCRH) divided by number of Read Commands(DSRDS), expressed as a percent.

Write efficiency Write efficiency is the difference between Write Com-mands (DSWRTS) and Device Write Operations (DSDWOP)divided by Write Commands (DSWRTS), expressed as apercent.

Channel (Resource Interval) The B-channel used by the IDLC line. (special condi-tion)

Cmn (Job Interval) The number of communications I/O operations performedby the selected interactive jobs during the interval.

Cmn I/O (Component) Number of communications operations (Get, Put).

Cmn I/O Per Second (Job Interval) The average number of communications I/Ooperations performed per second by the selected noninteractive jobsduring the interval.

Collision Detect (Resource Interval) The number of times that the terminal equip-ment (TE) detected that its transmitted frame had been corrupted byanother TE attempting to use the same bus.

Communications I/O Count (System) Number of communications I/O operations.

Communications I/O Get (System) Number of communication get operations pertransaction.

Communications I/O Put (System) Number of communication put operations pertransaction.

Communications Lines (System, Component, Job Interval, Pool Interval) For theReport Selection Criteria, the list of communications lines selected to beincluded (SLTLINE parameter) or excluded (OMTLINE parameter).These are the communications line names you specify.

Control Units (System, Component, Job Interval, Pool Interval) The list of controlunits selected to be included (SLTCTL parameter) or excluded(OMTCTL parameter). These are the controller names you specify.

Count (Transaction, Lock) The number of occurrences of the item in thecolumn. For example, in a lock report, it is the number of locks orseizes that occurred.

CPU (Transaction) The total processing unit seconds used by the jobs with agiven priority.

CPU /Tns (Transaction, Job Interval) The amount of available processing unit timeper transaction in seconds.


CPU Model (System) The processing unit model number.

CPU per I/O Async (System) CPU use per asynchronous I/O.

CPU per I/O Sync (System) CPU use per synchronous I/O.

CPU per Logical I/O (System) Processing unit time used for each logical disk I/Ooperation.

CPU QM (Transaction) The simple processing unit queuing multiplier.

CPU Sec (Transaction) The processing unit time used by the job in this state.

CPU Sec /Sync DIO (Transaction) The ratio of CPU seconds divided by synchro-nous disk I/O requests for each type of job.

CPU Sec Avg and Max (Transaction) The average processing unit time per trans-action for the job and the largest processing unit time used for a trans-action in the job. If the job is not an interactive or autostart job type,then only the total processing unit time for the job is listed under theMAX column heading.

CPU Sec per Tns (Transaction) The processing unit time per transaction.

CPU Seconds (System, Transaction, Component) Average processing unitseconds used per transaction. For System Summary Data, it is the totalavailable processing unit time used by the jobs during the trace period.For Priority-Jobtype-Pool Statistics, it is the total processing unitseconds used by the jobs with a given combination of priority, job type,and pool. For Batch Job Analysis, it is the amount of available processorunit time used by the job in seconds. For Concurrent Batch Job Statis-tics, it is the amount of available processor unit time used by the jobs inthe job set in seconds.

CPU seconds per transaction (System) The average processing unit seconds pertransaction.

CPU Util (System, Component, Transaction, Job Interval, Pool Interval, Batch JobTrace) Percentage of available processing unit time used. For multiple-processor systems, this is the total utilization divided by the number ofprocessors.

CPU Util per Transaction (Component) The result of the CPU Utilization dividedby the total number of transactions for the job.

CPU/Async I/O (Job Interval) The average number of milliseconds of processingunit time taken for each asynchronous disk I/O operation. This is calcu-lated by dividing the milliseconds of the processing unit time the jobused by the asynchronous disk I/O count.

CPU/Sync I/O (Job Interval) The average number of milliseconds of processing unittime taken for each synchronous disk I/O operation. This is calculatedfrom the milliseconds of the processing unit time used by the job dividedby the synchronous disk I/O count.

CPU/Tns (Transaction) The average number of processing seconds per trans-action for the job during the interval. This is calculated from the amountof processing unit time used divided by the number of transactions proc-essed.

Cpu/Tns (Sec) (Transaction) The number of processing unit seconds per trans-action.


Ctl (Component) Controller identifier.

Cum CPU Util (Transaction) The cumulative percentage of available processingunit time used by the transactions that have an average response timeper transaction equal to or less than the given category. For example, inCPU by Priority for All Jobs for Total Trace Period (System SummaryData), it is the unit time used by the jobs with a priority higher or equalto the given priority.

Cum Pct Tns (Transaction) Cumulative CPU percent per transaction. For systemsummary data, it is the cumulative CPU percentage of all transactionsthat have an average response time per transaction equal to or lessthan the given category. For Interactive Program Transactions Statistics,it is the cumulative CPU percentage of all transactions through the listedprogram. For Job Statistics section, it is the cumulative CPU percentageof total transactions through the listed job. For Interactive Program Sta-tistics section, it is the cumulative CPU percentage of all transactionsthrough the listed program.

Cum Util (System) Cumulative CPU use (a running total).

Note: This is taken from the individual jobs and may differ slightly fromthe total processing unit use on the workload page.

Cur Inl MPL (Transaction) The number of jobs waiting for an activity level (ineli-gible) in the storage pool.

Cur MPL (Transaction) The number of jobs holding an activity level in the storagepool.

DASD Ops/Sec (Component) Disk operations per second.

DASD Ops Per Sec Reads (Resource) Number of reads per second

DASD Ops Per Sec Writes (Resource) Number of writes per second

DB Fault (System, Component) Average number of database faults per second.

DB Pages (System, Component) Average number of database pages read persecond.

DB Read (Transaction) When listed in Physical I/O Counts column, it is thenumber of database read requests while the job was in that state. Whenlisted in the Sync Disk I/O Rqs/Tns column, it is the average number ofsynchronous database read requests per transaction.

DB Write (Transaction) When listed in the Sync Disk I/O Rqs/Tns column, it is theaverage number of synchronous database write requests per trans-action.

DB Wrt (Transaction) When listed in the Physical I/O Counts column, it is thenumber of database write requests while the job was in that state. Whenlisted in the Synchronous Disk I/O Counts column, it is the number ofsynchronous database write requests per transaction.

| DDM I/O (Component, Job Interval) The number of logical database I/O oper-| ations for a distributed data management (DDM) server job.

DDM Svr Wait /Tns (Transaction) The average time, in seconds, that a source dis-tributed data management (DDM) server job spent waiting for the targetsystem to respond to a request for data per transaction. This value


includes line time and time spent by the target system responding to therequest for data.

Dec (Transaction) The number of decimal overflow exceptions.

Decimal Data (Component) Data exception count per second. A data exceptionoccurs when data that is not valid is detected by arithmetic instructions.Examples are signs or digit codes that are not valid in decimalinstructions, or an insufficient number of farthest left zeros in multiplyinstructions.

Decimal Overflow (Component) Number of decimal overflows per second.

Description (Component) More detailed description of the exception type.

Detected Access Transmission Error (DTSE) In (Resource Interval) The numberof times the network termination 1 (NT1) end point notified the terminalequipment (TE) of an error in data crossing the ISDN U interface fromthe line transmission termination (LT) to the NT1 end point. The NT1end point reports the errors to the TE through the maintenance channelS1.

Detected Access Transmission Error (DTSE) Out (Resource Interval) Thenumber of times the network termination 1 (NT1) end point notified theterminal equipment (TE) of an error in data crossing the ISDN U inter-face from the NT1 end point to the LT. The NT1 end point reports theerrors to the TE through the maintenance channel S1.

Device (Component) Device identifier.

DIO/Sec Async (System) Number of asynchronous I/O operations per second.

DIO/Sec Sync (System) Number of synchronous I/O operations per second.

Disk Arm Seek Distance (Component) Average seek distance distributions perhour:

0 Number of zero seeks

1/12 Number of seeks between 0 and 1/12 of the disk

1/6 Number of seeks between 1/12 and 1/6 of the disk



>2/3 Number of seeks greater than 2/3 of the disk

Disk Arms (System) The number of disk arms for this IOP.

Disk Capacity (Component) Average amount of disk space used or available.

MB Millions of bytes available on the disk.

Percent Percent of space available on the disk.

Disk Controllers (System) The number of disk storage controllers for this IOP.

| Disk CPU Util (System, Resource Interval) The percentage of CPU used by the| disk unit.

Disk Feature (System) The type of disk (9332, 9335, and so on).

Disk I/O Async (System) Total number of asynchronous disk I/O operations.


Disk I/O per Second (System) Average number of physical disk I/O operations persecond.

Disk I/O Reads /Sec (Resource Interval) The average number of disk read oper-ations per second by the disk IOP.

Disk I/O Requests (Transaction) The total number of synchronous and asynchro-nous disk I/O requests issued by the jobs during the trace period.

Disk I/O Sync (System) Total number of synchronous disk I/O operations.

Disk I/O Writes /Sec (Resource Interval) The average number of disk write oper-ations per second by the disk IOP.

Disk IOPs (System) The number of disk IOP controllers.

Disk mirroring (System) Indicates whether disk mirroring is active.

Disk Space Used (Resource Interval) The total disk space used in millions of bytesfor the entire system.

Disk transfer size (KB) (System) The average number of kilobytes transferred perdisk operation.

Disk utilization (System) The fraction of the time interval that the disk arms wereperforming I/O operations.

Elapsed Seconds (Transaction, Component) The elapsed time in seconds. For theBatch Job Analysis section of the Transaction Report, it is the number ofseconds elapsed from when the job started to when the job ended. Forthe Concurrent Batch Job Statistics section of the Transaction Report, itis the total elapsed time of all jobs in that job set.

Elapsed Time (Job Interval) The amount of time (minutes and seconds) for whichthe job existed during the interval. This is the same as the intervallength unless the job started or ended during the interval, in which caseit is less.

Elapsed Time—Seconds (Transaction) Shows the time spent by the job, in the fol-lowing columns:

Long Wait Elapsed times in the state (such as waiting for the nexttransaction or lock-wait time).

Active/Rsp During transaction processing, the time the job spends(either waiting or active) while it holds an activity level. At theend of a transaction (on the transaction totals line), this is thetime the job spent processing the transaction in an activitylevel, for long waits caused by locks, and in the ineligiblestate.

Inel Wait The time the job spent in the ineligible wait state waiting foran activity level.

EM3270 Wait /Tns (Transaction) The average, in seconds, of the time spentwaiting on the host system communications for Systems Network Archi-tecture (SNA) and binary synchronous communications (BSC) 3270DEper transaction. Program logic is required to determine if the emulationprogram is communicating with the display or the host processing unit.Because there are requirements on event-wait processing, not all transi-tion combinations can be detected.


EORn (Transaction) Listed in the Wait Code column, End of response time fortransaction n. 1

EOTn (Transaction) Listed in the Wait Code column, End of transaction fortransaction for type n. 1

Estimated Exposr AP Not Jrnld (Component) System-estimated access pathrecovery time exposure in minutes if no access paths were being jour-naled by the system.

Estimated Exposr Curr System (Component) System-estimated access pathrecovery time exposure in minutes.

Est Of AWS (Transaction) An estimate of the number of active work stations forthe trace period or interval. Any delay time greater than 600 secondshas been rounded to 600 seconds. This technique is used to reduce theeffect of very casual users (those who may do intermittent work or leavetheir work stations for long periods of time) on the estimate of activework stations. This value is calculated as shown in Figure 7-80.

(AVGRSP + ACTIVE KEY/THINK)

AWS = TNS/HOUR x ─────────────────────────

36ðð

Figure 7-80. Equation for the Estimated Number of Active Work Stations

Event Wait /Tns (Transaction) The average time, in seconds, of the event-waittime per transaction.

Often requests made by a job that runs on the system are made toasynchronous jobs. These asynchronous jobs use an event to signalcompletion of the request back to the requester. The event-wait time isthe time the requesting job waits for such a signal.

EVT (Transaction) Listed in the Wait Code column, Event Wait. This is a longwait that occurs when waiting on a message queue.

Exception Type (Component) Type of program exception that results from theinternal microprogram instructions being run in internal microprograminstructions procedure. Because these exceptions are monitored at alow level within the system, it is difficult to associate these exceptionswith specific end-user operations. The counts are meaningful when theprocessing unit time required to process them affects system perform-ance. A variation in the counts may indicate a system change that couldaffect performance. For example, a large variation in seize or lockcounts may indicate a job scheduling problem or indicate that contentionexists between an old application and a new one that uses the sameresources.

| Note: To see the seize and lock counts, you should collect the trace| data by using the Start Performance Monitor (STRPFRMON)| command and specifying TRACE(*ALL). Run the Print Trans-| action Report (PRTTNSRPT) to list the objects and jobs that are| holding the locks.

1 These codes are in the wait code column, but they are not wait codes. They indicate transaction boundary trace records. For moreinformation see Chapter 8, “Transaction Boundaries—Manager Feature” on page 8-1.


Exceptional wait (System) The average exceptional wait time, in seconds, pertransaction. An exceptional wait is that portion of internal response timethat cannot be attributed to the use of the processor and disk. An excep-tional wait is caused by contention for internal resources of the system,for example, waiting for a lock on a database record.

Note: This is a calculated value. If the sum of the constant and vari-able wait time is greater than one second, you should runSTRPFRMON measurements with trace data collection andcompare the measured exceptional wait value, whichPRTTNSRPT provides, with this calculated value. If the valuesare significantly different, use the value from PRTTNSRPT,dividing it equally between constant and variable wait time.

Constant The portion of exceptional wait time held constant asthroughput increases.

Variable The portion of exceptional wait time that varies asthroughput increases.

Excp (Component, Transaction) For the Component Report, it is the totalnumber of program exceptions that occurred (see “Exception Occur-rence Summary and Interval Counts” on page 7-27). For the Trans-action Report, a Y in this column means that the transaction hadexceptions. The types of exceptions that are included are processaccess group exceptions, and decimal, binary, and floating point over-flow. See the transition report to see which exceptions the transactionhad.

Excp Wait (Transaction) The amount of exceptional wait time for the jobs in the jobset in seconds.

Excp Wait /Tns (Transaction) The average exceptional wait time, in seconds, pertransaction. This value is the sum of those waits listed under the Excep-tional Wait Breakdown by Job Type part.

Excp Wait Sec (Transaction) The total amount of exceptional wait time in secondsfor the job.

Excs ACTM /Tns (Transaction) The average time, in seconds, of the excessactivity level time per transaction (for example, time spent in the activestate but not using the processing unit). If enough activity levels areavailable and there is plenty of interactive work of higher priority to do, ajob waits longer for processing unit cycles. If the value is greater than .3,look at jobs that correspond to particular applications for more informa-tion. By looking at these jobs, you might be able to determine whichapplication’s jobs are contributing most to this value. Use the Trans-action and Transition Reports for these jobs for additional information.The formula for excessive activity-level time is shown in Figure 7-81.

| Active Time − [| (multiplier X CPU X Beginning Activity Level) +

| (Number of synchronous disk I/O operations X .ð1ð)]

Figure 7-81. Formula for Excessive Activity-Level Time

| Note: If the beginning activity level is greater than 1, the multiplier| equals 0.5. If the beginning activity level is any other value, the| multiplier equals 1.


Expert Cache (System, Component) Directs the system to determine which objectsor portions of objects should remain in a shared main storage poolbased on the reference patterns of data within the object. Expert cacheuses a storage management tuner, which runs independently of thesystem dynamic tuner, to examine overall paging characteristics andhistory of the pool.

| Some values that you might see in this column are associated with the| Work with Shared Pools (WRKSHRPOOL) command:

| � 0=*FIXED, which indicates the system does not dynamically adjust| the paging characteristics of the storage pool. The system uses| default values.

| � 3=*CALC, which indicates the system dynamically adjusts the| paging characteristics of the storage pool for optimum performance.

Exposed AP System Journaled (Component) The number of exposed accesspaths currently being journaled by the system.

Exposed AP System Not Journaled (Component) The number of exposed accesspaths currently not being journaled by the system.

| /F (System, Resource Interval) The line speed of the protocol reported as| full duplex. This indicator applies to the line speeds for an Ethernet| (ELAN) token-ring (TRLAN) line, or an asynchronous transfer mode line.

Far End Code Violation (Resource Interval) The number of unintended code vio-lations detected by the network termination 1 (NT1) end point for framestransmitted to the NT1 end point on the interface for the T referencepoint. The NT1 end point reports a violation to the termination equip-ment (TE) through the maintenance channel S1.

File (Transaction) The file that contains the object.

Flp (Transaction) The number of floating point overflow exceptions.

Flp Overflow (Component) Number of floating point overflows per second.

Frame Retry (Resource Interval) The number of attempts to retransmit a frame to aremote controller.

Frames Received Pct Err (Resource Interval) The percentage of frames receivedin error. Errors can occur when the host system has an error or cannotprocess received data fast enough.

Frames Received Total (Resource Interval) The total number of frames receivedincluding frames with errors and frames that are not valid.

Frames Transmitted Pct Err (Resource Interval) The percentage of framesretransmitted due to error.

Frames Transmitted Total (Resource Interval) The total number of frames trans-mitted.

Functional Areas (System, Component, Transaction, Job Interval, Pool Interval)For Report Selection Criteria, the list of functional areas selected to beincluded (SLTFCNARA parameter) or excluded (OMTFCNARA param-eter).

| /H (System, Resource Interval) The line speed of the protocol reported as| half duplex. This indicator applies to the line speeds for an Ethernet| (ELAN) token-ring (TRLAN) line, or an asynchronous transfer mode line.


HDW (Transaction) Listed in the Wait Code column, Hold Wait (job suspendedor system request). The job released a lock it had on the object namedon the next detail line of the report (OBJECT --). The job that waswaiting for the object is named on this line (WAITER --) along with theamount of time the job spent waiting for the lock to be released.

High Srv Time (Resource Interval) The highest average service time in seconds fora disk arm in the system.

High Srv Unit The disk arm with the highest service time.

High Util (Resource Interval) The percentage of use for the disk arm that has thehighest utilization.

High Util Unit (Component, Resource Interval) The disk arm with the highest utili-zation.

High Utilization Disk (Component) Percent of utilization of the most utilized diskarm during this interval.

High Utilization Unit (Component) Disk arm that had the most utilization duringthis interval.

Holder Job Name (Transaction) The name of the job that held the object.

Holder Number (Transaction) The number of the job that held the object.

Holder Pool (Transaction) The pool that held the job while it was running.

Holder Pty (Transaction) The priority of the holder’s job.

Holder Type (Transaction) The type and subtype of the holder’s job.

Holder User Name (Transaction) The name of the user that held the object.

Holder’s Job Name (Lock) The name of the job holding the lock.

I Frames Recd per Sec (Resource Interval) The number of information framesreceived per second.

I Frames Trnsmitd per Sec (Resource Interval) The number of information framestransmitted per second.

I/O Wait (Resource Interval) The amount of time in which a given I/O request isready to be processed, but the disk arm is not yet available to performthe request.

Incoming Calls Pct Retry (Resource Interval) The percentage of incoming callsthat were rejected by the network.

Incoming Calls Total (Resource Interval) The total number of incoming callattempts.

Inel Time A-I/W-I (Transaction) The amount of time the job spent in the ineligiblestate, either coming from time slice end (active-to-ineligible) or from thewait state (wait-to-ineligible).

Inel Wait (Transaction) Listed in the Elapsed Time—Seconds column, the time thejob spent in the ineligible wait state waiting for an activity level.

Inter CPU Utilization (Component) Percentage of available processing unit timeused by the following types of jobs:

� Interactive

� Multiple requester terminal (MRT)


� System/36 environment interactive

� Pass-through

� Target distributed data management (DDM) servers

� Client Access servers

Note: For a multiple-processor system, this is the average use acrossall processors.

IOP (Component) Input/output processor (IOP) Resource name and modelnumber for each communications IOP, DASD IOP, local workstationIOP, and multifunction IOP. Communications IOP is the percent of CPUused in the IOP. The percent does not necessarily mean that the IOP isdoing any data transfers. Some of the percent can be attributed to over-head of an active line.

IOP Name/Line (Resource Interval) Input/output (IOP) processor resource nameand model number line.

IOP Name(Model) (Resource Interval) The input/output processor (IOP) identifica-tion and the model number in parentheses.

IOP Name (System, Component) Input/Output processor (IOP) resource name.

IOP Name Network Interface (Resource Interval) The IOP name of the networkinterface.

IOP Processor Util Comm (Component, Resource) Utilization of IOP due to com-munications activity.

IOP Processor Util LWSC (Component, Resource) Utilization of IOP due to localworkstation activity.

IOP Processor Util DASD (Component, Resource) Utilization of IOP due to DASDactivity.

IOP Processor Util Total (Component, Resource Interval) The total percent of utili-zation for each local workstation, disk, and communications IOP.

IOP Util (System) For the Disk Utilization section of the System Report, it is thepercentage of utilization for each input/output processor (IOP).

Note: For the multifunction I/O processors, this is utilization due to diskactivity only, not communications activity. For the System ModelParameter section it is the fraction of the time interval the diskIOP was performing I/O operations.

Itv End (Component, Transaction, Job Interval, Pool Interval, Resource Interval)The time (hour and minute) when the data collection interval ended or avary off occurred. For the Exception Occurrence Summary and IntervalCounts of the Component Report, it is the ending time for the sampleinterval in which STRPFRMON recorded the exception.

Job Maximum A-I (Pool Interval) The highest number of active-state to ineligible-state transitions by a selected job in the pool or subsystem.

Job Maximum A-W (Pool) The highest number of active-to-wait state transitions bya selected job in the pool or subsystem.

Job Maximum CPU Util (Pool Interval) The highest percentage of available proc-essing unit time used by a selected job in the pool or subsystem.


Job Maximum Phy I/O (Pool Interval) The highest number of physical disk inputand output operations by a selected job in the pool or subsystem.

Job Maximum Rsp (Pool Interval) The highest response time in seconds per trans-action by a selected job in the pool or subsystem. The response time isthe amount of time spent waiting for and using the resources divided bythe number of transactions.

Job Maximum Tns (Pool Interval) The highest number of transactions by aselected job in the pool or subsystem.

Job Maximum W-I (Pool Interval) The highest number of wait-state to ineligible-state transitions by a selected job in the pool or subsystem.

Job Name (Component, Transaction, Job Interval, Batch Job Trace) Name of thejob. In the Job Summary Report of the Transaction Report, a job (iden-tical job name, user name, and job number) appears multiple times inthis list if the job uses the system Reroute Job (RRTJOB) command.

Job Number (Component, Transaction, Job Interval, Batch Job Trace) The numberof the job which the summary line describes. In the Transaction Report,an asterisk (*) before the job number indicates the job signed on duringthe measurement period. An asterisk (*) after the job number indicatesthe job signed off during the measurement period.

Job Pty (Batch Job Trace) Priority of the job.

| Job Set (Transaction) The number of job sets is the number of batch jobs that| could be active at any time during the trace period. If two jobs run| sequentially, they show up as two jobs in the same job set. If two jobs| run concurrently, they show up in two different job sets.

| Job Type (All Reports except where noted for the Transaction Report) Job typeand subtype.

Possible job type values include the following:

A Autostart

B Batch

| BD Batch immediate (Transaction only)

| Note: The batch immediate values are shown as BCI on the| Work with Active Job display and as BATCHI on the| Work with Subsystem Job display.

| BE Batch evoke (Transaction only)

| BJ Batch pre-start job (Transaction only)

C Programmable workstation application server, which includes5250 emulation over APPC and Client Access host serversrunning either APPC or TCP/IP

| A job is reported as a Client Access server if any of the fol-| lowing items are true:

| � Incoming APPC evoke requests one of the server| program names listed in the AS/400 Client Access Host| Servers. This also applies to the pre-started jobs for the| QSERVER, QCMN, and QSYSWRK subsystems that are| already waiting for the named program.


| � Incoming IP port number corresponds to one of the| service name-description-port-numbers documented in| AS/400 Client Access Host Servers. This also applies to| the pre-started jobs for the QSERVER, QCMN, and| QSYSWRK subsystems that are already waiting for the| assigned IP port number.

| � Incoming IPX socket number corresponds to one of the| service name-description-port-number documented in| AS/400 Client Access Host Servers. This also applies to| the pre-started jobs for the QSERVER, QCMN, and| QSYSWRK subsystems that are already waiting for the| assigned IPX port number.

| � Incoming 5250 display emulation jobs that come from| APPC data streams sent by 5250 emulation under OS/2| Communications Manager or WARP equivalent.

D Target distributed data management (DDM) server

| I Interactive. Interactive includes twinaxial data link control| (TDLC), 5250 remote workstation, and 3270 remote work-| station. For the Transaction Report, this includes twinaxial| data link control (TDLC), 5250 remote workstation, 3270| remote workstation, SNA pass-through, and 5250 TELNET.

L Licensed Internal Code task

M Subsystem monitor

| P SAN pass-through and 5250 TELNET pass-through. On the| Transaction Report, these jobs appear as I (interactive).

R Spool reader

S System

| W Spool writer, which includes the spool write job, and if| Advanced Function Printing (AFP) is specified, the print| driver job.

WP Spool print driver (Transaction only)

X Start system job

Possible job subtype values include the following:

D Batch immediate job

E Evoke (communications batch)

J Pre-start job

P Print driver job

T Multiple requester terminal (MRT) (System/36 environmentonly)

3 System/36

Noninteractive job types include:

� Autostart

� Batch


� Evoke

� Spool

Special interactive job categories include:

� Client Access server

� Distributed data management (DDM) server

� Interactive

� Multiple requester terminal (MRT)

� Pass-through

� System/36

Jobs (System, Component, Transaction, Pool Interval, Job Interval) The jobsyou specify. The format of the entries is jobnumber/username/jobname.For the Report Selection Criteria report, it is the list of jobs selected tobe included (SLTJOB parameter) or excluded (OMTJOB parameter).This does not include jobs selected by using the STLFCNARA orOMTFCNARA parameter.

K per I/O (System, Resource Interval) The average number of kilobytes (1024bytes) read or written for each disk I/O operation.

K/T /Tns Sec (Transaction) The average delay time, or time spent keying andthinking between transactions for the job, in seconds. The value repres-ents the time interval between active-to-wait and wait-to-active or wait-to-ineligible job state transitions.

KB per I/O Read (Resource Interval) The average number of kilobytes (1 KBequals 1024 bytes) transferred per read operation.

KB per I/O Write (Resource Interval) The average number of kilobytes (1024bytes) transferred per write operation.

KBytes Transmitted IOP (Component, Resource Interval) Total kilobytes trans-mitted from an IOP to the system across the bus.

KBytes Transmitted System (Component, Resource Interval) Total kilobytestransmitted to the IOP from the system across the bus.

Key/Think (Transaction) The amount of time spent waiting for the work station userby the program.

Key/Think /Tns (Transaction) The average think time and keying time (or the delaytime between transaction boundaries), in seconds, for the interactivejobs.

L (Lock) Whether this is a lock or seize conflict. The column contains an Lif lock, blank if seize.

LAPD Pct Frames Recd in Error (Resource Interval) The percentage of framesreceived in error (applies to D-channel only). Errors can occur when thehost system has an error or cannot process received data fast enough.

LAPD Pct Frames Trnsmitd Again (Resource Interval) The percentage of framesretransmitted due to error (applies to D-channel only).

LAPD Total Frames Recd (Resource Interval) The total number of frames receivedincluding frames with errors and frames that are not valid (applies toD-channel only).


LAPD Total Frames Trnsmitd (Resource Interval) The total number of framestransmitted (applies to D-channel only).

Last 4 Programs in Invocation Stack (Transaction) The last four programs in theprogram stack. For example, at the start of a transaction (such as whenthe work station operator presses the Enter key), you see the programnames QT3REQIO, QWSGET, and the program that issued a readoperation. At the end of the transaction (such as when the programwrites to the display), you see QT3REQIO, QWSPUT, and the programthat wrote the display. See Appendix B, Defining Transaction Bounda-ries, for more information about the transaction boundary.

Usually, the third or fourth program in the stack is the program shown inthe transaction summary PGMNAME data. However, if the Wait Codecolumn has a value, the program in the column labeled Last is the onethat caused the trace record.

If there is no program name in a column, the program name was thesame as the previous one in the column, and the name is omitted.

Length of Wait (Lock) The number of milliseconds the requestor waited for thelocked object.

Lgl I/O /Sec (Job Interval) The average number of logical disk I/O operations per-formed per second by the job during the interval. This is calculated fromthe logical disk I/O count divided by the elapsed time.

Library (Transaction) The library that contains the object.

Line Count (Job Interval) The number of lines printed by the selectednoninteractive jobs during the interval.

Line Descriptn (Resource Interval) Line description name.

Line Errors (Resource Interval) The total of all detected errors. Check the conditionof the line if this value increases greatly over time.

Line Speed (System, Resource Interval) The line speed in kilobits (1 kilobit = 1000bits) per second.

Line Util (Resource Interval) The percent of available line capacity used bytransmit and receive operations.

LKRL (Transaction) Lock Released. The job released a lock it had on theobject named on the next detail line of the report (OBJECT --). The jobthat was waiting for the object is named on this line (WAITER --) alongwith the amount of time the job spent waiting for the lock to be released.

LKW (Transaction) Listed in the Wait Code column, Lock Wait. If there are anumber of these, or you see entries with a significant length of time inthe ACTIVE/RSP* column, additional analysis is necessary. The LKWTreport lines that precede this LKW report line show you what object isbeing waited on, and who has the object.

LKWT (Transaction) Listed in the Wait Code column, Lock Conflict Wait. Thejob is waiting on a lock conflict. The time (*/ time /*) is the duration ofthe lock conflict and, though not equal to the LKW time, should be veryclose to it. The holder of the lock is named at the right of the report line(HOLDER --). The object being locked is named on the next report line(OBJECT --).


Local End Code Violation (Resource Interval) The number of times an unintendedcode violation was detected by the terminal equipment (TE) for framesreceived at the interface for the ISDN S/T reference point.

Local Not Ready (Resource Interval) The percent of all receive-not-ready framesthat were transmitted by the host system. A large percentage oftenmeans the host cannot process data fast enough (congestion).

Local work station IOP utilization The fraction of the time interval the workstation I/O processors are busy.

Local work station IOPs (System) The resource name and model number foreach local workstation IOP.

Lock Conflict (Component) Number of lock exceptions per second. Databaserecord contention is reflected in this count. For more information, run theperformance monitor with the TRACE(*ALL) option and use thePRTTNSRPT and PRTLCKRPT commands.

This count could be very high, even under normal system operation.Use the count as a monitor. If there are large variations or changes,explore these variations in more detail.

Lock Wait /Tns (Transaction) The average time, in seconds, of the lock-wait timeper transaction. If the value is high, investigate with the transactiondetail calculation and the PRTLCKRPT command.

Logical (Job Interval) The number of logical disk I/O operations performed bythe selected interactive jobs during the interval.

Logical Database I/O Other (System) Other logical database operations per trans-action. This includes operations such as update and delete.

Logical Database I/O Read (System) Logical database read operations per trans-action.

Logical Database I/O Write (System) Logical database write operations per trans-action.

Logical DB I/O (System) Average number of logical I/O operations per transaction.

Logical DB I/O Count (System) Number of database file input/output requests sentby programs for each job type.

Note: Logical I/O contrasts with physical I/O shown elsewhere in thesereports. A logical I/O is a request sent at the program level thatmight result in an access to auxiliary storage (DASD). A physicalI/O refers to those requests that result in access to auxiliarystorage.

Logical Disk I/O (Component) Number of logical disk operations (Get, Put, Update,Other).

Logical I/O /Second (System) Average number of logical disk I/O operations persecond.

Logical I/O Per Second (Job Interval) The average number of logical disk I/Ooperations performed per second by the selected noninteractive jobsduring the interval.


Long Wait (Transaction) The time the job spent waiting for a system resource. Anexample of a long wait would be a record-lock conflict. Also listed in theElapsed Time—Seconds column, it is the elapsed time in the state (suchas waiting for the next transaction or lock-wait time).

Long Wait Lck/Oth (Transaction) The amount of time the job spent waiting for asystem resource. An example of a long wait would be a record-lock con-flict.

Loss of Frame Alignment (Resource Interval) The number of times a time periodequivalent to two 48-bit frames elapsed without detecting valid pairs ofline code violations.

MAC Errors (Resource Interval) The number of medium access control (MAC)errors.

Main storage (MB) (System) The total main storage size, as measured in mega-bytes (10242).

Max Util (System) Consistent use at or above the threshold value given will affectsystem performance and cause longer response times or lessthroughput. See the BEST/1 Capacity Planning Tool for a list ofthreshold values.

Maximum (Transaction) The maximum value of the item that occurred in thecolumn.

Member (Transaction) The member that was involved in the conflict.

Minimum (Transaction) The minimum value of the item that occurred in thecolumn.

MRT Max Time (System) The time spent waiting, after MRTMAX is reached, byjobs routed to a multiple requester terminal.

Note: No value appears in this column if job type is not MRT.

Nbr A-I (Transaction) The number of active-to-ineligible state transitions by thejob. This column shows the number of times that the job exceeded thetime-slice value assigned to the job, and had to wait for an activity-levelslot before the system could begin processing the transaction. If a valueappears in this column, check the work that the job was doing, anddetermine if changes to the time-slice value are necessary.

Nbr Evt (Transaction) The number of event waits that occurred during the jobprocessing.

Nbr Jobs (Transaction) The number of jobs.

Nbr Sign offs (Transaction) The number of jobs that signed off during the interval.

Nbr Sign ons (Transaction) The number of jobs that signed on during the interval.

Nbr Tns (Transaction) The number of transactions in a given category.

Note: The values for transaction counts and other transaction-relatedinformation shown on the reports you produce using thePRTTNSRPT command may vary from the values shown on thereports you produce using the PRTSYSRPT and PRTCPTRPTcommands. These differences are caused because thePRTTNSRPT command uses trace data as input, while thePRTSYSRPT and PRTCPTRPT commands use sample data as


input. See Appendix B, Defining Transaction Boundaries, foradditional information.

If there are significant differences in the values for transaction-relatedinformation shown on these reports, do not use the data until you inves-tigate why these differences exist.

Nbr W-I (Transaction) The number of wait-to-ineligible state transitions by thejob. This column shows how many times the job had to wait for a trans-action.

NDB Read (Transaction) Listed in Physical I/O Counts column, it is the number ofnondatabase read requests while the job was in that state. Listed in theSync Disk I/O Rqs/Tns column, it is the average number of synchronousnondatabase read requests per transaction.

NDB Write (Transaction) Listed in the Sync Disk I/O Rqs/Tns column, it is theaverage number of synchronous nondatabase write requests per trans-action.

NDB Wrt (Transaction) Listed in Physical I/O Counts column, the number of non-database write requests while the job was in that state. Listed underSynchronous Disk I/O Counts column, it is the number of synchronousnondatabase write requests per transaction.

Non-DB Fault (System, Component) Average number of nondatabase faults persecond.

Non-DB Pages (System, Component) Average number of nondatabase pages readper second.

Number (Transaction) The number of the job with which the transaction is asso-ciated.

Number I/Os per Second (System) The number of I/Os per second for this partic-ular IOP.

Number Jobs (Transaction) The number of batch jobs in the job set.

Number Lck Cft (Transaction) The number of lock-wait (including database recordlock) state conflicts that occurred during the job processing. If thisnumber is high, look at the Transaction and Transition Reports for thejob to see how long the lock-wait state conflicts were lasting. In addition,you can do further investigation using the reports produced when youuse the PRTLCKRPT command.

Number Lck Conflict (Transaction) The number of times the job had a lock con-flict.

Number Locks (Transaction) The number of locks attributed to interactive ornoninteractive waiters.

Number of batch jobs (System) The average number of active batch jobs. A batchjob is considered active if it averages at least one I/O per 5 minutes.

Number of Jobs (System) Number of jobs.

Number Seizes (Transaction) The number of seizes attributed to interactive ornoninteractive waiters.

Number Sze Cft (Transaction) The number of seize/lock conflicts that occurredduring the job processing. If this number is high, look at the Transactionand Transition Reports for the job to see how long the conflicts lasted,


the qualified name of the job that held the object, the name and type ofobject being held, and what the job was waiting for.

Number Sze Conflict (Transaction) The number of times the job had a seize con-flict.

Number Tns (System, Transaction) Total number of transactions processed. Forexample, in the System Report it is the total number of transactionsprocessed by jobs in this pool. In the Transaction Report it is thenumber of transactions associated with the program.

Number Traces (Batch Job Trace) Number of traces.

Number Transactions (System) Total number of transactions processed.

Object File (Transaction) The file that contains the object.

Object Library (Transaction) The library that contains the object.

Object Member (Transaction) The member that was involved in the conflict.

Object Name (Lock) The name of the locked object.

Object RRN (Transaction) The relative record number of the record involved in theconflict.

Object Type (Transaction, Lock) The type of the locked object. The following arepossible object types:

AG Access group

CB Commit block

CBLK Commit block

CD Controller description

CLS Class

CMD Command

CTLD Controller description

CTX Context

CUD Control unit description

CUR Cursor

DEVD Device description

DS Data space

DSI Data space index

DTAARA Data area

EDTD Edit description

FILE File

JOBD Job description

JOBQ Job queue

JP Journal port

JRN Journal

JRNRCV Journal receiver


JS Journal space

LIB Library

LIND Line description

LUD Logical unit description

MBR Member

MEM Database file member

MSGF Message file

MSGQ Message queue

ND Network description

OCUR Database operational cursor

OUTQ Output queue

PGM Program

PROG Program

PRTIMG Print image

QDAG Composite piece - access group

QDDS Composite piece - data space

QDDSI Composite piece - dta spe index

QTAG Temporary - access group

QTDS Temporary - data space

QTDSI Temporary - data space index

SBSD Subsystem description

TBL Table

Omit Parameters (System, Component, Transaction, Job Interval, Pool Interval)The criteria used to choose the data records to be excluded from thereport. The criteria are generally specified using an OMTxxx parameterof the command. Only nondefault values (something other than *NONE)are printed. If a parameter was not specified, it does not appear on thereport.

Op per Second (System) Average number of disk operations per second.

Other Wait /Tns (Transaction) The average time, in seconds, spent waiting thatwas not in any of the previous categories per transaction. For example,the time spent waiting during a save/restore operation when the systemrequested new media (tape or diskette).

Outgoing Calls Pct Retry (Resource Interval) The percentage of outgoing callsthat were rejected by the network.

Outgoing Calls Total (Resource Interval) The total number of outgoing callattempts.

Over commitment ratio (System) The main storage over commitment ratio (OCR).

PAG (Transaction) The number of process access group faults.


PAG Fault (Component, Job Interval) In the Exception Occurrence Summary of theComponent Report, it is the total number of times the program accessgroup (PAG) was referred to, but was not in main storage. In the Excep-tion Occurrence Summary of the Component Report, it is the number offaults involving the process access group per second.

Page Count (Job Interval) The number of pages printed by the selectednoninteractive jobs during the interval.

Pct CPU By Categories (Transaction) The percentage of available processing unittime used by the transactions that fell into the various categories. Seethe ANALYSIS by Interactive Transaction Categories part of the SystemSummary Data Section for an explanation of the categories.

Pct Data Characters Received in Error (Resource Interval) The percent of datacharacters received with error.

Pct Data Characters Transmitted in Error (Resource Interval) The percent ofdata characters transmitted with error.

Pct Ex-Wt /Rsp (Transaction) The percentage of the response time that is due toexceptional wait.

Pct Of Tns Categories (Transaction) The percentage of all transactions that fellinto the various categories. See the Analysis by Interactive TransactionCategories part of the System Summary Data Section for an explanationof the categories.

Pct PDUs Received in Error (Resource Interval) The percent of protocol data units(PDUs) received in error during the time interval. These errors can occurif the host system has errors or cannot receive data fast enough (con-gestion).

Note: A protocol data unit (PDU) for asynchronous communications isa variable-length unit of data that is ended by a protocol controlcharacter or by the size of the buffer.

Pct Poll Retry Time (Resource Interval) The percent of the time interval the linewas unavailable while the IOP waited for a response from a work stationcontroller (or remote AS/400 system) that was in disconnect mode.

Note: To minimize this lost time:

� Vary on only the controllers that are turned on.

� Turn on all controllers.

� Use the Change Line Description (SDLC) (CHGLINSDLC) commandto set the connect poll timer to a small value (reduces wait time).

� Use the Change Controller Description (CHGCTLxxxx) command(where xxxx is APPC, FNC, RWS, or RTL, as appropriate) to set theNDMPOLLTMR value to a large value (increases time betweenpolls).

Pct Tns (Transaction) The percentage of the total transactions. For the SystemSummary section of the Job Summary Report, the transactions arewithin the given trace period with the given purge attribute. For the Inter-active Program Transaction Statistics section of the Job SummaryReport, the percentage of transactions that were associated with aprogram. For the Job Statistics section, it is the percentage of total


transactions that were due to this job. For the Interactive Program Sta-tistics section, it is all transactions that were associated to a program.

Percent Errored Seconds (Resource Interval) The percentage of seconds in whichat least one Detected Access Transmission (DTSE) in or out erroroccurred.

Percent Frames Received in Error (Resource Interval) The percent of all receivedframes that were received in error. Errors can occur when the hostsystem has an error or cannot process received data fast enough (con-gestion).

Percent Full (System) Percentage of disk space capacity in use.

Percent I Frames Trnsmitd in Error (Resource Interval) The percent of trans-mitted information frames that required retransmission. Retransmissionscan occur when a remote device has an error or cannot processreceived data fast enough (congestion).

Percent Severely Errored Seconds (Resource Interval) The percent of seconds inwhich at least three Detected Access Transmission (DTSE) in or outerrors occurred.

Percent transactions (dynamic no) (System) A measure of system main storageutilization. The percent of all interactive transactions that were done withthe purge attribute of dynamic NO.

Percent transactions (purge no) (System) A measure of system main storageutilization. The percent of all interactive transactions that were done withthe purge attribute of NO.

Percent transactions (purge yes) (System) A measure of system main storageutilization. The percent of all interactive transactions that were done withthe purge attribute of YES.

Percent Util (System) Average disk arm utilization (busy). Consistent use at orabove the threshold value provided for disk arm utilization affectssystem performance, which causes longer response times or lessthroughput. See utilization guidelines and thresholds in the BEST/1Capacity Planning Tool book for a list of threshold values.

Note: The percent busy value is calculated from data measured in theI/O processor. When comparing this value with percent busyreported by the Work with Disk Status (WRKDSKSTS)command, some differences may exist. The WRKDSKSTScommand estimates percent busy based on the number of I/Orequests, amount of data transferred, and type of disk unit.

The system-wide average utilization does not include data for mirroredarms in measurement intervals for which such intervals are either inresuming or suspended status.

Perm Write (Component, Job Interval) The number of permanent write operationsperformed for the selected jobs during the interval.

Permanent writes per transaction (System) The average number of permanentwrite operations per interactive transaction.

Physical I/O Count (Transaction, Batch Job Trace) For the Job Summary sectionof the Batch Job Trace Report, the number of synchronous and asyn-chronous disk operations (reads and writes). For the Transition Report,


the next five columns provide information about the number of synchro-nous and asynchronous disk I/O requests while the job was in the givenstate. The first line is the synchronous disk I/O requests, and the secondline is the asynchronous disk I/O requests.

DB Read The number of database read requests while the job was inthat state.

DB Wrt The number of database write requests while the job was inthat state.

NDB Read The number of nondatabase read requests while the job wasin that state.

NDB Wrt The number of nondatabase write requests while the job wasin that state.

Tot The total number of DB Read, DB Wrt, NDB Read, and NDBWrt requests.

Pl (Component, Transaction, Job Interval, Pool Interval) The number of thepool in which the subsystem or job ran.

Pool (Transaction, Job Interval, Batch Job Trace) The number of the poolcontaining the transaction (for example, in which the job ran.)

Pool ID (System) Pool identifier.

Pool ID Faults (Component) User pool that had the highest page fault rate.

Pool Mch Faults/Sec (Component) Average number of machine pool page faultsper second.

Pool size (KB) (System, Component) For the Storage Pool Activity section of theComponent Report it is the initial pool size in kilobytes (1024 bytes). Forthe System Model Parameters section of the System Report, it is thetotal size in kilobytes of all pools that incurred interactive job activity.

Pool User Faults/Sec (Component) Average number of user pool page faults persecond, for the user pool with highest fault rate during this interval.

Pools (System, Component, Transaction, Job Interval, Pool Interval) In theReport-Selection Criteria section, the list of pools selected to be included(SLTPOOLS parameter) or excluded (OMTPOOLS parameter). Other-wise, the pools you specify. The values can be from 1 through 16.

Prg (Transaction) The purge attribute of the jobs.

Printer Lines (System, Job Interval) The number of lines printed by the job duringthe interval.

Printer Pages (System, Job Interval) The number of pages printed by the jobduring the interval.

Priority (System, Transaction) The priority of the job.

Program (Transaction) The name of the program with which the transaction isassociated.

Program Name (Transaction) For the Job Summary section of the TransactionReport, the name of the program in control at the start of the trans-action. Other programs may be used during the transaction. For theTransaction Report section, the name of the program active at the startof the transaction. If ADR=UNKNWN (address unknown) is shown under


the column, the program was deleted before the trace data was dumpedto the database file. If ADR=000000 is shown under the column, therewas not enough trace data to determine the program name, or therewas no program active at that level in the job when the trace record wascreated.

Protocol (System) Line protocol.

� SDLC

� ASYNC

� BSC

� X25

� TRLAN

� ELAN (Ethernet)

� IDLC

� DDI

� FRLY

Pty (Component, Transaction, Job Interval) Priority of the job. For the Con-current Batch Job Statistics section of the Transaction Report, it is thepriority of the jobs in the job set.

Purge (Transaction) The purge attribute of the jobs.

PWrt (Transaction) The number of permanent write I/O operations.

Queue Length (Resource Interval) The average number of I/O requests that had towait in the queue for this unit.

Rank (Transaction) The order. For the Job Summary section, it is the order ofthe program according to the number of transactions. For the Job Statis-tics section, it is the order of the job. For the Interactive Program Statis-tics section, it is the order of the program. For the Individual TransactionStatistics section, it is the order of the transaction according to the databeing put in order by importance. For the Largest Seize/Lock Conflictssection, it is the order of the seize or lock conflict.

Ratio of write disk I/O to total disk I/O (System) The fraction of the total diskactivity that is due to writing data to the disks.

Reads per Second (Resource Interval) The average number of disk read oper-ations performed per second by the disk arm.

Receive CRC Errors (Resource Interval) The number of received frames that con-tained a cycle redundancy check (CRC) error. This indicates that thedata was not received error free.

Record Number (Lock) For database file members, the relative record number ofthe record within the database file member.

Remote LAN Pct Frames Recd (Resource Interval) The number of framesreceived from a local area network (LAN) connected to the locallyattached LAN.

Remote LAN Pct Frames Trnsmitd (Resource Interval) The number of framestransmitted to a local area network (LAN) connected to the locallyattached LAN.


Remote Not Ready (Resource Interval) The percentage of all receive-not-readyframes that were received by the host system. A large percentage oftenmeans the remote device cannot process data fast enough (congestion).

Remote Seq Error (Resource Interval) The percent of frames received out of orderby a remote device or system. This can occur when the remote deviceor system cannot process data fast enough.

Requestor’s Job Name (Lock) The name of the job requesting the locked object(the same as in the detail listing).

Reset Packets Recd (Resource Interval) The number of reset packets received bythe network. Reset packets are packets retransmitted because an erroroccurred.

Reset Packets Trnsmitd (Resource Interval) The number of reset packets trans-mitted by the network.

Response (System) Average system response (service) time.

Response Sec Avg and Max (Transaction) The average (AVG) and maximum(MAX) transaction response time, in seconds, for the job. The averageresponse time is calculated as the sum of the time between each pair ofwait-to-active and active-to-wait transitions divided by the number ofpairs that were encountered for the job. The MAX response time is thelargest response time in the job.

Response Seconds (System) Average response time in seconds per transaction.

Rsp (Component) Average interactive transaction response time in seconds.

Rsp Time (Component, Resource Interval) The average external response time (inseconds). For the Local Work Station IOP Utilizations section of theResource Interval Report, it is the response time for work stations onthis controller. For the Remote Work Stations section of the ComponentReport, it is the response time for this work station.

Rsp Timer Ended (Resource Interval) The number of times the response timerended waiting for a response from a remote device.

Rsp/Tns (Component, Transaction, Job Interval) The average response time(seconds) per transaction. For the Job Summary section of the JobInterval Report, it is the response time per transaction for the selectedinteractive jobs during the interval (the amount of time spent waiting foror using the system resources divided by the number of transactionsprocessed). This number will not be accurate unless at least severalseconds were spent processing transactions.

S/L (Transaction) Whether the conflict was a seize (S) or lock (L) conflict.

Seize and Lock Conflicts (Batch Job Trace) Number of seize conflicts and lockwaits.

Seize Conflict (Component) Number of seize exceptions per second. For moredetailed information, you can run the performance monitor with theTRACE(*ALL) option, and use the PRTTNSRPT or PRTLCKRPT com-mands.



Seize Hold Time (Transaction) The amount of time that the transaction held upother jobs in the system by a seize or lock on an object.

Seize Wait /Tns (Transaction) The average time, in seconds, for all seize-lock con-flicts that occur during an average transaction. More than one seize-lockconflict can occur during a single transaction for the same job. If thisnumber is high, investigate those jobs with seize conflicts. The Trans-action Report lists each conflict that occurs, the name of the holder, andthe name of the object held.

For the Transaction by 5-Minute Intervals section of the Job SummaryReport, it is the average seize wait time per transaction in seconds. Thisis the average amount of time that the transactions spent in a seize/lockconflict. If this number is high, look at the Transaction and TransitionReports for the jobs that are causing the excessive wait time.

Select Parameters (System, Component, Transaction, Job Interval, Pool Interval)The criteria used to choose the data records to be included in the report.The criteria are generally specified using an SLTxxx parameter of thecommand. Only nondefault values (something other than *ALL) areprinted. If a parameter is not specified, it does not appear on the report.

Sequence Error (Resource Interval) The number of frames received that containedsequence numbers indicating that frames were lost.

Short Frame Errors (Resource Interval) The number of short frames received. Ashort frame is a frame that has fewer octets between its start flag andend flag than are permitted.

Short Wait /Tns (Transaction) The average time, in seconds, of short (active) waittime per transaction.

For the Interactive Program Statistics section, if the value is high, it maybe due to the use of data queues or to the use of DFRWRT(*NO) orRSTDSP(*YES) in the program display files.

Short WaitX /Tns (Short wait extended) (Transaction) The average time, inseconds, of wait time per transaction that resulted due to a short (active)wait that exceeded 2 seconds, and caused a long wait transition tooccur. The activity level has been released but this time is still countedagainst your total response time. Waits on data queues or the use ofDFRWRT(*NO) and/or RSTDSP(*YES) in the display files could bereasons for this value to be high.

Size (Component) Decimal data overflow and underflow exceptions persecond. An indication of improper field size on numeric calculations.

Size (K) (System, Pool Interval) The size of the pool in kilobytes (1024 bytes).

Size (M) (System) Disk space capacity in millions of bytes.

SMAPP ReTune (Component) System-managed access path protection tuningadjustments.

SOTn (Transaction) Listed in the Wait Code column, Start of transaction n. 2



Spool CPU seconds per I/O (System) The average number of system processingunit seconds used by all spool jobs for each I/O performed by a spooljob.

Spool database reads per second (System) The average number of read oper-ations to database files per second of spool processing.

Spool I/O per second (System) The average number of physical disk I/O oper-ations per second of spool processing.

Srv Time (Component) Average disk service time per request in seconds notincluding the disk wait time. See Figure 7-9 on page 7-23 for diskresponse time.

Start (Transaction) The time the job started.

Started (Transaction) The time of the first record in the trace data, in the formHH.MM.SS (hours, minutes, seconds).

State (Transaction) The three possible job states are shown in Figure 7-82.

┌─────5 W (wait state) not holding an activity level

│

│ ┌───5 A (Active or wait state) holding an activity

│ │ level

│ │ ┌──5 I (ineligible state) waiting for an

│ │ │ activity level

│ │ │ The type of transition is shown below.

│ │ │ The direction and position of the arrow

│ │ │ indicates which transition was made.

│ │ │

│ │ │

W A I

────

Figure 7-82. Possible Job States

Figure 7-83 shows the possible job state transitions. For example, fromW to A is y, or yes, which means it is possible for a job to change fromthe wait state to the active state.

A

W

I

A

y

y

y

W

y

-

-

I

y

y

-

To stateAWI

= Active state= Wait state= Ineligible state

RV2S087-0

Fromstate

Figure 7-83. AS/400 Job State Transitions

State Transitions A-A (Batch Job Trace) Number of active-to-active transitions.

State Transitions A-I (Batch Job Trace) Number of active-to-ineligible transitions.

Stop (Transaction) The time the job ended.

Stopped (Transaction) The time of the last record in the trace data, in the formHH.MM.SS (hours, minutes, seconds).

Subsystem Name (Pool Interval) The name of the subsystem.


Subsystems (System, Component, Pool Interval) For the System Report, the sub-system names you specify. Each name is a 10-character name. For theComponent Report, the list of subsystems selected to be included(SLTSBS parameter) or excluded (OMTSBS parameter).

Sum (Transaction) Listed in the Sync Disk I/O Rqs/Tns column, the sum ofthe averages of the synchronous DB READ, DB WRITE, NDB READ,and NDB WRITE requests (the average number of synchronous I/Orequests per transaction for the job).

SWX (Transaction) Listed in the Wait Code column, Short Wait Extended. Theshort wait has exceeded a 2-second limit and the system has put thetransaction into a long wait. This long wait must be charged to the trans-action response time. In most cases, this active-to-wait transaction doesnot reflect a transaction boundary.

Sync (Job Interval) The number of synchronous disk I/O operations performedby the selected interactive jobs during the interval.

Sync DIO /Tns (Transaction) The average number of synchronous I/O requests pertransaction during the interval.

Sync Disk I/O (System, Component, Transaction) Synchronous disk I/O operations.

Sync Disk I/O per Second (Component) Average synchronous disk I/O operationsper second.

Sync Disk I/O Requests (Transaction) The total number of synchronous disk I/Orequests for the given combination of priority, job type, and pool.

Sync Disk I/O Rqs/Tns (Transaction) The next five columns provide informationabout the number of synchronous disk I/O requests per transaction:

DB Read The average number of synchronous database read requestsper transaction.

DB Write The average number of synchronous database write requestsper transaction.

NDB Read The average number of synchronous nondatabase readrequests per transaction.

NDB Write The average number of synchronous nondatabase writerequests per transaction.

Sum The sum of the averages of the synchronous DB READ, DBWRITE, NDB READ, and NDB WRITE requests (the averagenumber of synchronous I/O requests per transaction for thejob).

Sync I/O /Elp Sec (Transaction) The average number of synchronous disk I/Orequests for all jobs, per second of elapsed time used by the jobs.

Sync I/O /Sec (Job Interval) The average number of synchronous disk I/O oper-ations performed per second by the job during the interval. This is calcu-lated from the synchronous disk I/O count divided by the elapsed time.

Sync I/O Per Second (Job Interval) The average number of synchronous disk I/Ooperations performed per second by the selected noninteractive jobsduring the interval.


Synchronous DBR (System, Transaction, Job Interval, Pool Interval) The averagenumber of synchronous database read operations. It is the total synchro-nous database reads divided by the total transactions. For the PoolInterval and Job Interval Reports, it is calculated per transaction for thejob during the intervals. For the System Report, it is calculated persecond. For the Transaction (Job Summary) it is calculated per trans-action. Listed under Average DIO/Transaction, the average number ofsynchronous database read requests per transaction. This field is notprinted if the jobs in the system did not process any transactions.

Synchronous DBW (System, Transaction, Job Interval, Pool Interval) The averagenumber of synchronous database write operations. It is the total syn-chronous database writes divided by the total transactions. For the PoolInterval and Job Interval Reports, it is calculated per transaction for thejob during the intervals. For the System Report, it is calculated persecond. For the Transaction (Job Summary) it is calculated per trans-action. Listed under Average DIO/Transaction, the average number ofsynchronous database read requests per transaction. This field is notprinted if the jobs in the system did not process any transactions.

Synchronous DIO / Act Sec (System, Transaction) The number of synchronousdisk I/O operations per active second. The active time is the elapsedtime minus the wait times.

Synchronous DIO / Ded Sec (Transaction) The estimated number of synchronousdisk I/O operations per second as if the job were running in dedicatedmode. Dedicated mode means that no other job would be active or incontention for resources in the system.

Synchronous DIO / Elp Sec (Transaction) The number of synchronous disk I/Ooperations per elapsed second.

Synchronous Disk I/O Counts (Transaction) The next five columns provide infor-mation about the number of synchronous disk I/O requests pertransaction:

DB Read The number of synchronous database read requests pertransaction.

DB Wrt The number of synchronous database write requests pertransaction.

NDB Read The number of synchronous nondatabase read requests pertransaction.

NDB Wrt The number of synchronous nondatabase write requests pertransaction.

Sum The sum of the synchronous DB Read, DB Wrt, NDB Read,and NDB Wrt requests (the number of synchronous I/Orequests per transaction).

Synchronous disk I/O per transaction (System, Transaction) The averagenumber of synchronous physical disk I/O operations per interactivetransaction.

Synchronous Max (Transaction) The maximum number of synchronous DBR,NDBR, and WRT I/O requests encountered for any single transaction bythat job. If the job is not an interactive or autostart job type, the total diskI/O for the job is listed here.


Synchronous NDBR (System, Transaction, Job Interval, Pool Interval) Theaverage number of synchronous nondatabase read operations per trans-action for the jobs in the system during the interval. For the TransactionReport, the operations on the disk per transaction for the selected jobsin the pool. This is calculated from the synchronous nondatabase readcount divided by the transactions processed. This field is not printed ifthe jobs in the system did not process any transactions.

Synchronous NDBW (System, Job Interval, Pool Interval) The average number ofsynchronous nondatabase write operations on the disk per transactionfor the selected jobs in the pool. For the System Report, it is the oper-ations per transaction for the jobs in the system during the interval. Thisis calculated from the synchronous nondatabase write count divided bythe transactions processed. This field is not printed if the jobs in thesystem did not process any transactions.

Synchronous Sum (Transaction) The sum of the averages of the synchronousDBR, NDBR, and WRT requests (the average number of synchronousI/O requests per transaction for the job).

Synchronous wrt (Transaction) The average number of synchronous databaseand nondatabase write requests per transaction.

System CPU per transaction (seconds) (System) The average number of systemprocessing unit seconds per interactive transaction.

System disk I/O per transaction (System) The total number of physical disk I/Ooperations attributed to the system per interactive transaction.

System Starts (Component) The number of start journal operations initiated by thesystem.

System Stops (Component) The number of stop journal operations initiated by thesystem.

System Total (Component) The total number of journal deposits resulting from| system-journaled objects. These are the deposits performed by system-| managed access path protection (SMAPP).

System ToUser (Component) The number of journal deposits resulting fromsystem-journaled objects to user-created journals.

SZRL (Transaction) Listed in the Wait Code column, Seize/Lock Released.The job released a lock it had on the object named on the next detailline of the report (OBJECT --). The job that was waiting for the object isnamed on this line (WAITER --) along with the amount of time the jobspent waiting for the seize conflict to be released.

SZWT (Transaction) Listed in the Wait Code column, Seize/Lock Conflict Wait.The job is waiting on a seize/lock conflict. The time (*/ time /*) is theduration of the seize/lock conflict, and is included in the active time thatfollows it on the report. The holder of the lock is named at the right ofthe report line (HOLDER --). The object being held is named on thenext report line (OBJECT --).

| Thread (Job Summary, Transaction, Transition) A thread is a unique flow of| control within a process. Every job has an initial thread associated with| it. Each job can start one or more secondary threads. The user name| column changes to User name / Thread if a secondary thread is avail-| able.


| The system assigns the thread number to a job as follows:

| � The system assigns thread IDs sequentially. When a job is started| that uses a job structure that was previously active, the thread ID| that is assigned to the initial thread is the next number in the| sequence.

| � The first thread of a job is assigned a number.

| � Any additional threads from the same job are assigned a number| that is incremented by 1. For example:

| Job Name User Name/ Job Number

| Thread

| QJVACMDSRV SMITH ð23416

| QJVACMDSRV ððððððð6 ð23416



| A thread value greater than 1 does not necessarily mean the job| has had that many threads active at the same time. To determine| how many threads are currently active for the same job, use the| WRKACTJOB, WRKSBSJOB, or WRKUSERJOB commands to find| the multiple three-part identifiers with the same job name.

Time (Transaction) The time when the transaction completed, or when a seizeor lock conflict occurred. Also, a column heading that shows the time thetransition from one state to another occurred, in the HH.MM.SS.mmmarrangement.

Tns (Component, Pool Interval) The total number of transactions processedby the selected jobs in the pool or subsystem.

Tns Count (Component, Job Interval) The number of transactions performed by theselected interactive jobs during the interval.

Tns/Hour (Component, Transaction, Job Interval) The average number of trans-actions per hour processed by the selected interactive jobs during theinterval.

Tns/Hour Rate (System) Average number of transactions per hour.

TOD of Wait (Lock) The time of day of the start of the conflict.

Tot (Transaction) Listed in Physical I/O Counts column, the total number ofDB Read, DB Wrt, NDB Read, and NDB Wrt requests.

Tot Nbr Tns (Transaction) The total number of transactions the PRTTNSRPTprogram determined from the input data that were accomplished for thejob.

Total (Component) Total exception counts for the reporting period.

Total /Job (Transaction) The total (sum) of the items in the column for the job.

Total characters per transaction (System) The average number of characterseither read from or written to display station screens per interactivetransaction.

Total CPU Sec /Sync DIO (Transaction) The ratio of total CPU seconds divided bythe total synchronous disk I/O requests.


Total CPU Utilization (System, Component) Percentage of available processingunit time used by interactive jobs, batch jobs, all system jobs, andLicensed Internal Code tasks. For a multiple-processor system this isthe average use across all processors.

For a multiple-processor system, Total CPU Utilization is replaced by autilization value for each processor in the system. Here is an example ofthis part of the display for a system with two processors:

Average CPU utilization . . . . . : 41.9

CPU 1 utilization . . . . . . . . : 41.7

CPU 2 utilization . . . . . . . . : 42.2

Note: This value is taken from a system counter. Other processing unituses are taken from the individual job work control blocks(WCBs). These totals may differ slightly.

Total Data Characters Received (Resource Interval) The number of data charac-ters received successfully.

Total Data Characters Transmitted (Resource Interval) The number of data char-acters transmitted successfully.

Total fields per transaction (System) The average number of display station fieldseither read from or written to per interactive transaction.

Total Frames Recd (Resource Interval) The number of frames received, includingframes with errors and frames that are not valid.

Total I Frames Trnsmitd (Resource Interval) The total number of informationframes transmitted.

Total I/O (System) Sum of the read and write operations.

Total PDUs Received (Resource Interval) The number of protocol data units(PDUs) received during the time interval.

Note: A protocol data unit (PDU) for asynchronous communications isa variable-length unit of data that is ended by a protocol controlcharacter or by the size of the buffer.

Total Physical I/O per Second (Resource Interval) The average number of phys-ical disk I/O operations performed per second by the disk arm.

Total Responses (Component, Resource Interval) The total number of transactionscounted along with the average response time for all active workstations or devices on this controller for the report period.

Total Seize/Wait Time (Component) The response time in milliseconds for eachjob.

Total Tns (Component) Number of transactions processed in this pool.

Transaction Response Time (Sec/Tns) (Transaction) The response time inseconds for each transaction. This value includes no communicationsline time. Response times measured at the work station exceed this timeby the data transmission time (the time required to transmit data fromthe work station to the processing unit and to transmit the response databack to the work station from the processing unit).

Transactions per hour (local) (System) The interactive transactions per hour attri-buted to local display stations.


Transactions per hour (remote) (System) The interactive transactions per hourattributed to remote display stations.

Transmit/Receive/Average Line Util (Resource Interval) In duplex mode, the per-centage of transmit line capacity used, the percentage of receive linecapacity used, and the average of the transmit and receive capacities.

TSE (Transaction) Listed in the Wait Code column, Time Slice End. Theprogram shown in the stack entry labeled LAST is the program that wentto time slice end.

| Typ (Component, Transaction) The system job type and subtype. The Com-| ponent Report allows only one character in this column. The Transaction| Report allows two characters. The Transaction Report reports the job| type and job subtype directly from the QAPMJOBS fields. The Compo-| nent Report takes the job type and job subtype values and converts it to| a character that may or may not be the value from the QAPMJOBS| field. Table 7-1 on page 7-16 shows the following information in table| format. The possible job types are:

A Autostart

B Batch

| BD Batch immediate (Transaction only)

| Note: The batch immediate values are shown as BCI on the| Work with Active Job display and as BATCHI on the| Work with Subsystem Job display.

| BE Batch evoke (Transaction only)

| BJ Batch pre-start job (Transaction only)

C Programmable work station application server, which includes5250 emulation over APPC and Client Access host serversrunning either APPC or TCP/IP

| A job is reported as a Client Access server if any of the fol-| lowing items are true:

| � Incoming APPC evoke requests one of the server| program names listed in the AS/400 Client Access Host| Servers. This also applies to the pre-started jobs for the| QSERVER, QCMN, and QSYSWRK subsystems that are| already waiting for the named program.

| � Incoming IP port number corresponds to one of the| service name-description-port-numbers documented in| AS/400 Client Access Host Servers. This also applies to| the pre-started jobs for the QSERVER, QCMN, and| QSYSWRK subsystems that are already waiting for the| assigned IP port number.

| � Incoming IPX socket number corresponds to one of the| service name-description-port-number documented in| AS/400 Client Access Host Servers. This also applies to| the pre-started jobs for the QSERVER, QCMN, and| QSYSWRK subsystems that are already waiting for the| assigned IPX port number.


| � Incoming 5250 display emulation jobs that come from| APPC data streams sent by 5250 emulation under OS/2| Communications Manager or WARP equivalent.

D Target distributed data management (DDM) server

| I Interactive. For the Component Report, this includes twinaxial| data link control (TDLC), 5250 remote workstation, and 3270| remote workstation. For the Transaction Report, this includes| twinaxial data link control (TDLC), 5250 remote workstation,| 3270 remote workstation, SNA pass-through, and 5250| TELNET

L Licensed Internal Code Task

M Subsystem monitor

| P SNA pass-through and 5250 TELNET pass-through. On the| Transaction Report, these jobs appear as I (interactive).

R Spool reader

S System

| W Spool writer, which includes the spool write job, and if| Advanced Function Printing (AFP) is specified, the print| driver job.

| WP Spool print driver (Transaction only)

X Start the system

The possible job subtypes are:

D Batch immediate job

E Evoke (communications batch)

J Pre-start job

P Print driver job

T Multiple requester terminal (MRT) (System/36 environmentonly)

3 System/36

Notes:

| 1. Job subtypes do not appear on the Component Report.

2. If the job type is blank or you want to reassign it, use the ChangeJob Type (CHGJOBTYP) command to assign an appropriate jobtype.

Type (System, Transaction, Job Interval) One of the transaction types listed inthe description of the DTNTY field in Table 7-9 on page 7-96.

(System) The disk type.

(Transaction) The type and subtype of the job.

(Transaction) For the Seize/Lock Conflicts by Object section, the typeof seize/lock conflict.


Unit (System, Component, Resource Interval) The number assigned by thesystem to identify a specific disk unit or arm. An ‘A’ or ‘B’ following theunit number indicates that the disk unit is mirrored. (For example, 0001Aand 0001B are a mirrored pair.)

Unit Name The resource name of the disk arm.

User ID (System, Component, Transaction, Job Interval, Pool) The list of usersselected to be included (SLTUSRID parameter) or excluded(OMTUSRID parameter).

User Name (Component, Transaction, Job Interval, Batch Job Trace) Name of theuser involved (submitted the job, had a conflict, and so on.)

| User Name/Thread (Transaction) If the job information contains a secondary| thread, then this column shows the thread identifier. If the job informa-| tion does not contain a secondary thread, then the column shows the| user name.

| The system assigns the thread number to a job as follows:

| � The system assigns thread IDs sequentially. When a job is started| that uses a job structure that was previously active, the thread ID| that is assigned to the initial thread is the next number in the| sequence.

| � The first thread of a job is assigned a number.

| � Any additional threads from the same job are assigned a number| that is incremented by 1. For example:

| Job Name User Name/ Job Number

| Thread

| QJVACMDSRV SMITH ð23416




| A thread value greater than 1 does not necessarily mean the job| has had that many threads active at the same time. To determine| how many threads are currently active for the same job, use the| WRKACTJOB, WRKSBSJOB, or WRKUSERJOB commands to find| the multiple three-part identifiers with the same job name.

User Starts (Component) The number of start journal operations initiated by theuser.

User Stops (Component) The number of stop journal operations initiated by theuser.

User Total (Component) The total number of journal deposits resulting fromsystem-journaled objects.

Util (Component, Resource Interval) The percent of utilization for each localwork station, disk, or communications IOP, controller, or drive.

Note: The system-wide average utilization does not include data formirrored arms in measurement intervals for which such intervalsare either in resuming or suspended status.

Util 2 (Component, Resource) Utilization of co-processor.


Value (Transaction) For the Individual Transaction Statistics section of the JobSummary report, it is the value of the data being compared for the trans-action. For the Longest Seize/Lock Conflicts section, it is the number ofseconds in which the seize or lock conflict occurred.

Verify (Component) Number of verify exceptions per second. Verify exceptionsoccur when a pointer needs to be resolved, when blocked MIinstructions are used at security levels 10, 20, or 30, and when an unre-solved symbolic name is called.


W-I Wait/Tns (Transaction) The average time, in seconds, of wait-to-ineligible timeper transaction. This value is an indication of what effect the activitylevel has on response time. If this value is low, the number of wait-to-ineligible transitions probably has little effect on response time. If thevalue is high, adding additional interactive pool storage and increasingthe interactive pool activity level should improve response time. If youare unable to increase the interactive pool storage (due to limited avail-able storage), increasing the activity level may also improve responsetime. However, increasing the activity level might result in excessivefaulting within the storage pool.

Wait Code (Transaction) The job state transition that causes the trace record to beproduced. The values can be as follows:

EVT Event Wait. A long wait that occurs when waiting on amessage queue.

EOTn End of transaction for transaction for type n. 3

EORn End of response time for transaction n. 3

HDW Hold Wait (job suspended or system request).

LKRL Lock Released. The job released a lock it had on the objectnamed on the next detail line of the report (OBJECT --). Thejob that was waiting for the object is named on this line(WAITER --) along with the amount of time the job spentwaiting for the lock to be released.

LKW Lock Wait. If there are a number of these, or you see entrieswith a significant length of time in the ACTIVE/RSP* column,additional analysis is necessary. The LKWT report lines thatprecede this LKW report line show you what object is beingwaited on, and who has the object.

LKWT Lock Conflict Wait. The job is waiting on a lock conflict. Thetime (*/ time /*) is the duration of the lock conflict and,though not equal to the LKW time, should be very close to it.The holder of the lock is named at the right of the report line(HOLDER --). The object being locked is named on the nextreport line (OBJECT --).



SOTn Start of transaction n. 3

SWX Short Wait Extended. The short wait has exceeded a2-second limit and the system has put the transaction into along wait. This long wait must be charged to the transactionresponse time. In other words, this active-to-wait transactiondoes not reflect a transaction boundary.

SZRL Seize/Lock Released. The job released a lock it had on theobject named on the next detail line of the report(OBJECT --). The job that was waiting for the object isnamed on this line (WAITER --) along with the amount oftime the job spent waiting for the seize conflict to bereleased.

SZWT Seize/Lock Conflict Wait. The job is waiting on a seize/lockconflict. The time (*/ time /*) is the duration of the seize/lockconflict, and is included in the active time that follows it onthe report. The holder of the lock is named at the right of thereport line (HOLDER --). The object being held is named onthe next report line (OBJECT --).

TSE Time Slice End. The program shown in the stack entrylabeled LAST is the program that went to time slice end.Every time a job uses 0.5 seconds of CPU time (0.2 secondson the faster processors) between long waits, the systemchecks if there are jobs of equal priority on the CPU queue. Ifthere are, then the next job with equal priority is granted theCPU and the interrupted job is moved to the queue as thelast of equal priority. The job, however, retains its activitylevel. This is an internal time slice end.

When a job reaches the external time slice value, there canbe a job state transition from active to ineligible if another jobis waiting for an activity level. When a job is forced out of itsactivity level, its pages are liable to be stolen by other jobs,and cause additional I/O when the job regains an activitylevel.

The IBM-supplied default values of 2 seconds for interactivejobs and 5 seconds for batch jobs may often be too high,especially for the high-end processors. As an initial value, setthe time slice at 3 times the average CPU seconds per trans-action.

WTO Wait Timed Out. The job has exceeded the wait time-out limitdefined for a wait (such as a wait on a lock, a messagequeue, or a record).

Wait-Inel (System, Component) Average number of wait-to-ineligible job statetransitions per minute.

Work Station Controller (Resource Interval) The name of the remote work stationcontroller.

Working set size (KB) (System) An estimate of the main storage size, in kilobytes,required by a single interactive job running the transactions described bythis report.


Writes per Second (Resource Interval) The average number of disk write oper-ations performed per second by the disk arm.

WTO (Transaction) Listed in the Wait Code column, Wait Timed Out. The jobhas exceeded the wait time-out limit defined for a wait (such as a waiton a lock, a message queue, or a record).

0.0-1.0 (Component, Resource Interval) The number of times the response timewas between 0 and 1 second.

1.0-2.0 (Component, Resource Interval) The number of times the response timewas between 1 and 2 seconds.




Chapter 8. Transaction Boundaries—Manager Feature

A transaction is a basic unit of work done on a system. The type of work varies,depending on what kind of work it is or who is doing the work. Performance Toolsreports capture information about many kinds of system transactions; you can thenuse these reports to analyze system performance.

When the Transaction Report counts transactions, it uses only state transactions.For example, when a job goes from wait to active state, this marks the beginning ofa transaction. When a job goes from active to wait, the transaction is consideredended. For the display I/O transactions and the data queue transactions, you canspecify values *DI and *DQ. These values use existing transaction boundary tracerecords to count transactions instead of the wait-to-active state transition.

This chapter provides information about the following types of system transactions:

� Display I/O information

� SNA performance measurements

� APPN control point performance

� APPC protocol

� Performance measurement and SNADS

� SNADS sample data

� SNADS performance notes

� Pass-through

� Licensed Internal Code server

� Data queue transactions

Display I/O Transaction Boundary InformationThe transaction boundary information in Figure 8-1 shows how a display I/O trans-action uses system resources by showing the relationship between transactionresponse time and resource usage time.

6

1

4

3

5

2

Workstation AS/400

Application

RV2S090-1

Figure 8-1. Example: Display I/O Transaction

The numbers 1 through 6 in the following list refer to the same numbers inFigure 8-1.

1 The user presses the Enter key or a function key. This begins theresponse time period perceived by the user. However, the system doesnot recognize the beginning of the transaction until step 2.


Delays are typical on a remote communication line. They are dependenton the following:

� The amount of current data traffic to and from other work stations onthe line.

� How frequently the system polls the control unit for input data.

2 Start of Transaction (SOT) 1

Identifies the beginning of the System Measured Response Time. Work-station I/O Management (WSIOM) processes input from the displaystation. This also represents the beginning of application-input queuingtime.

This is a trace data point.

3 Start of Resource Utilization Time (SOR)

The application must issue an input operation or accept an input opera-tion. An application program receives the data from WSIOM and beginsusing system resources to process the transaction. The application-inputqueuing time ends at this point. Normally, application-input queuing time,like activity-level waiting time, is only a few milliseconds.

4 End of Resource Utilization Time (EOR) 1

The application program completes using system resources. Thisnormally coincides with the End of Transaction (EOT).

At this point, the program has performed an operation that causes workstation I/O to send data to the display station. The following userprogram operations cause the data to be sent to the display station:

� Read or invite input operation following one or more output oper-ations with the defer write (DFRWRT) parameter set to *YES in thedisplay file description.

� Output operation with DFRWRT(*NO) in the display file description.

� Output operation with the DDS INVITE keyword.

� Combined output/input operation. For example, an EXFMT operationin an RPG/400 program and a SNDRCVF command in a control lan-guage (CL) program.

� End of program.

This is a sample data point.

5 End of Transaction (EOT) 1

The end of the System Measured Response Time. The next transactionmay begin. Resource usage by the transaction is measured at this point.This may coincide with the End of Resource Utilization Time (EOR). AnyActive-Wait transition is included here.

This is a trace data point.

6 System response displayed to user.

1 The SOT, EOR, and EOT abbreviations appear on the Transition Report. For an example of a Transition Report, see Figure 7-49on page 7-62.


1→6 Display I/O Transaction Path

The complete path taken by the transaction. This is the time from whenthe user presses the Enter key or a function key to the time when theuser receives a response. This is the user's perception of the responsetime.

2→3 Application Input Queuing Time

This is the time the input data waits before the system resources aremade available to it. Examples are input data waiting on:

� an activity level

� the program to issue an input operation

� the program to accept input.

The total application queuing time (in hundredths of a second) is storedin the JBAIQT field in the QAPMJOBS file. The number of applicationqueuing transactions is stored in the JBNAIQ field in the QAPMJOBSfile. These fields are also updated by data queue transactions.

3→4 Transaction Resource Usage

The period when system resources are used for processing includingperiods of waiting, such as object seize/lock conflicts and resourcequeuing.

The total resource usage time (in seconds) is stored in the JBRUT fieldin the QAPMJOBS file. The number of resource usage transactions isstored in the JBNRU field in the QAPMJOBS file. These fields are alsoupdated by data queue transactions.

2→5 System Response Time

The total transaction time (in seconds) is stored in the JBRSP field inthe QAPMJOBS file. The number of transactions (5250 only) is stored inthe JBNTR field in the QAPMJOBS file. These fields are also updatedby Client Access shared folders transactions and by pass-through trans-actions.

1→2 Components of response time are not recorded by the system.

5→6 Components of response time are not recorded by the system.

SNA Performance MeasurementsThe SNA performance measurements provide a different set of internal perform-ance data for each APPC and host controller description. These measurementsinclude the activity created by attached device descriptions and APPN intermediatesessions.

Performance data is collected for a controller description only after the controller isvaried on and at least one connection has been established with the adjacentsystem. Performance data is not collected after the controller description is variedoff.

The QAPMSNA file contains the SNA performance measurements. The fields in theQAPMSNA file are categorized as follows:

� Correlation fields

Chapter 8. Transaction Boundaries—Manager Feature 8-3

� Connection fields

� Device description fields

� T2 station I/O manager task fields

� Session traffic fields

Correlation FieldsCorrelation fields include external configuration names and internal task names thatallow the performance measurements to be correlated to other parts of the system.

Correlating the SNA performance measurements with other parts of the system isimportant. The following correlation fields are defined:

SCTLNM Names the APPC or host controller description.

SLINNM Names the line description that is attached to the controller description.If *LOCAL is specified for the link type parameter on an APPC controllerdescription, this field is blank.

STSKNM Identifies the T2 station IOM task that provides services for the controllerdescription. The QAPMJOBS performance monitor file contains informa-tion about processing unit use and disk unit accesses for this task.

SLIOMT Identifies the line IOM task that provides services for the line description.The QAPMJOBS performance monitor file contains information aboutprocessing unit use and disk unit accesses for this task.

Note: Because the line IOM task could service multiple station IOMtasks, the processing unit use and disk unit access data may notbe attributed to a single station IOM task or controllerdescription. For example, multiple controller descriptions areoften attached to a single LAN line description.

SACPNM Names the adjacent control point. If the controller description is notAPPN capable, this field may be blank. The adjacent CP name can beused to correlate with data displayed by the Display APPN Information(DSPAPPNINF) command.

SANWID Names the adjacent network ID. The adjacent network ID can be usedto correlate with data displayed by the DSPAPPNINF command.

SAPPN Indicates whether or not the controller description is APPN capable. Ifthe system uses the APPN support, additional performance measure-ments can be found in the QAPMAPPN performance monitor file.

SCTYP Indicates whether the controller description is an APPC or host con-troller.

Connection FieldsConnection fields measure the frequency with which connections are establishedwith the adjacent system.

A connection is established with the adjacent system when the status of the con-troller description goes from varied off or vary on pending to varied on or active.You can view this status using the Work with Configuration Status (WRKCFGSTS)command.


On a non-switched line, the connection is established after the line and controllerdescription are varied on, assuming the adjacent system is ready to establish theconnection. The non-switched connection remains until the controller is varied off,an irrecoverable line error occurs, or the adjacent system drops the connection.

On a switched line, the connection is not established until a communicationsprogram needs to use the connection (for example, the program acquires asession). The switched connection is usually dropped after the connection has beeninactive (for example, all sessions are unbound) for a period of time.

The following connection fields are defined:

STLLBU Indicates the date and time when the most recent connection was estab-lished.

SNLBU Indicates the number of connections that were established with the adja-cent system in the time interval. Dropping and re-establishing a con-nection frequently can degrade performance. Using switched lines, youmay frequently re-connect if you have an inappropriate Switched discon-nect parameter value on the controller description or irrecoverable lineerrors.

Device Description FieldsDevice description fields measure device-related activity. APPN automaticallycreates, varies on, and deletes devices.

The following device description fields are defined:

STACVO Indicates the cumulative elapsed time in milliseconds required to auto-matically create and vary on APPN devices.

SNACVO Indicates the number of APPN devices that were automatically createdor varied on.

SNADD Indicates the number of APPN devices that were automatically deleted.

Note: If devices are automatically created or deleted excessively, your system'sperformance can be degraded. Increasing the number of minutes specifiedon the Autodelete device parameter on the controller description reducesthe frequency with which APPN automatically deletes devices.

T2 Station I/O Manager Task FieldsThese task fields give an estimate of how much work is being done by the T2 (PUtype 2) station I/O manager task.

The T2 SIOM task provides services for the controller description. The processingunit utilization and disk unit accesses for the T2 SIOM task are contained in theQAPMJOBS performance monitor file. A description of that file can be found in theWork Management book.

The following T2 SIOM task fields are defined:

SNWAIN Indicates the number of internal task messages that are received by theT2 SIOM task. This field is an approximation of the amount of work per-formed by the T2 SIOM task.

SNWAOU Indicates the number of internal task messages that are sent by the T2SIOM task.


Session Traffic FieldsSession traffic fields measure the sending and receiving of session traffic. A sepa-rate set of identical session traffic fields is collected for each session type and pri-ority level combination.

There are two session types: end point and intermediate sessions. End pointsession traffic is created by the following device types:

� APPC devices

� Host devices (for example: 3270 emulation, RJE)

� DHCF display devices

� NRF display and printer devices

Intermediate session traffic is created by the following:

� APPN intermediate sessions

� SNA pass-through devices

There are four priority levels: network, high, medium and low. Network prioritysession traffic is created by the following:

� APPN

� SNA change to the number of sessions

� Alert support

High priority session traffic is created by the following:

� APPC devices


Medium priority session traffic is created by the following:

� APPC devices

� Host devices (for example, 3270 emulation, RJE)

� DHCF display devices

� NRF display and printer devices

� SNA pass-through devices


Low priority session traffic is created by the following:

� APPC devices


Therefore eight different sets of session traffic fields are collected.

The first two characters of the session traffic field name represent the session typeand priority level. The first character specifies the session type:

E End point

I Intermediate


The second character specifies the priority level:

N Network

H High

M Medium

L Low

The remaining four characters represent the function of the field. Figure 8-2 onpage 8-8 shows the layout of the session traffic fields in the QAPMSNA file.

Note: Throughout the remainder of this section, the first two characters of thesession traffic fields are replaced with the prefix tp to generically refer toany session type and priority level combination.

Number of Sessions Started and EndedThe tpNSS and tpNSE fields count the number of sessions that are started andended, respectively. A session starts when the positive response to an SNA bindcommand is sent or received. A session ends when an SNA unbind command issent or received, or the session is abnormally ended (for example, the line fails).Starting and ending sessions can cause significant system overhead.

Number of Brackets Started and EndedThe tpNBB and tpNEB fields count the number of SNA brackets that are startedand ended. For sessions that are not LU 6.2, the delimiters for the start and end ofa bracket are the bind and unbind command. For LU 6.2, the delimiters for the startand end of a bracket are the begin bracket indicator (BBI) and conditional endbracket indicator (CEBI) in the request header (RH). An LU 6.2 bracket is roughlyequivalent to a conversation that is started when a program issues an ICF evokeoperation or Common Programming Interface Communications (CPI-C) allocateverb and ends when the Common Programming Interface Communications programissues an ICF detach operation or Common Programming Interface Communi-cations (CPI-C) deallocate verb. An example is a DSPT (display station pass-through) or SNADS session.

Sending DataThe SNA processing required to send data can be classified into the followingstages:

� Session-level pacing

� Internal session-level pacing

� Transmission priority

� Line transmission

Session-Level PacingSession-level pacing is a technique that allows a receiving session to control therate at which it receives request units on the normal flow. It is used primarily toprevent a receiver with unprocessed requests from overloading because the sendercan create requests faster than the receiver can process them.

The following session-level pacing fields are defined:


ENffff

EHffff

EMffff

ELffff

INffff

IHffff

IMffff

ILffff

End Point Session/Network Priority

End Point Session/High Priority

End Point Session/Medium Priority

End Point Session/Low Priority

Intermediate Session/Network Priority

Intermediate Session/High Priority

Intermediate Session/Medium Priority

Intermediate Session/Low Priority

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

ffff = 1 to 4 character functional name RV2S070-0

Figure 8-2. Layout of Session Traffic Fields

tpSPWT Specifies the cumulative amount of time that application data waswaiting for a pacing response to be received.

tpSPNW Specifies the number of times that application data was waiting for apacing response to be received.

tpSPPW Specifies the total number of pacing windows, which is the potentialnumber of times that application data could have waited for a pacingresponse to be received.

tpSPWS Specifies the cumulative pacing window size.

The following information can be derived from the session-level pacing fields:

� The average amount of time spent waiting for a pacing response to be receivedis: tpSPWT/tpSPNW.

� The percentage of times application data waited for a pacing response to arriveis: (tpSPNW*100)/tpSPPW.

� The average pacing window size is: tpSPWS/tpSPPW.

If excessive waiting is caused by session-level pacing, the OUTPACING (localsystem) and INPACING (remote system) parameters in the mode description mayneed to be increased. However, if the average pacing window size is 7 or more, theexcessive waiting may be caused by a slow remote system or a slow remoteprogram.


Internal Session-Level PacingFor APPN and APPC sessions that are adaptively paced, internal session-levelpacing is used to limit the amount of bandwidth used by a particular session. It onlycontrols internal flow and does not have any external line flows. A sending sessionis allowed to transmit a limited number of request units and is not allowed totransmit additional request units until a request unit is successfully delivered to theadjacent system.

The INPACING and OUTPACING parameters in the mode description are used tocalculate the limit. The limit used for a given session is (2*n)-1, where n is theINPACING or OUTPACING parameter. On a slow speed line, it may be necessaryto configure a small limit for batch traffic and a larger limit for interactive traffic toensure acceptable interactive response time.

The following internal session-level pacing fields are defined:

tpIPWT Specifies the cumulative amount of time that application data waswaiting, because of internal session-level pacing.

tpIPNW Specifies the number of times that application data was waiting,because of internal session-level pacing.

The following information can be derived from the internal session-level pacingfields:

� The average amount of time spent waiting because of internal session-levelpacing is: tpIPWT/tpIPNW.

If excessive waiting is caused by internal session-level pacing and it is not desir-able to limit the amount of bandwidth used, the OUTPACING and INPACINGparameters in the mode description may need to be increased.

Transmission PriorityTransmission priority determines the criteria for being selected for transmission tothe adjacent system by allowing different priority levels to be assigned to sessiontraffic. Three user-defined priorities are defined: high, medium and low. Network pri-ority is reserved for APPN and SNA control traffic. Interactive traffic is typicallyassigned high priority, and batch traffic is typically assigned medium or low priority.

The following transmission priority fields are defined:

tpQNRE Specifies the number of request units that entered the transmission pri-ority queue.

tpQLRE Specifies the cumulative length of data that entered the transmission pri-ority queue.

tpQNRL Specifies the number of request units leaving the transmission priorityqueue to be sent to data link control for transmission to the adjacentsystem.

tpQLRL Specifies the cumulative length of data leaving the transmission priorityqueue to be sent to data link control for transmission to the adjacentsystem.

tpQTRR Specifies the cumulative amount of time that request units waited in thetransmission priority queue.


The following information can be derived from the transmission priority fields:

� The average length of a request unit entering the transmission priority queue is:tpQLRE/tpQNRE.

� The average length of a request unit leaving the transmission priority queue is:tpQLRL/tpQNRL.

� The average amount of time a request unit waited in a transmission priorityqueue is: tpQTRR/tpQNRL.

Excessive waiting in a transmission priority queue may occur if:

� The data is preempted by higher priority data

� The line is a slow speed line

� Frequent retransmissions are required due to an error-prone line

Note: The average wait time for higher priority data should typically be less thanlower priority data.

Line TransmissionPerformance data is collected to quantify the amount of time required to success-fully transmit data to the adjacent system. This measurement period begins afterthe data leaves the transmission priority queue and ends when the data is success-fully delivered to the adjacent system.

The following line transmission fields are defined:

tpNRUD Specifies the number of request units delivered to the adjacent system.

tpLRUD Specifies the cumulative length of data delivered to the adjacent system.

tpTRUD Specifies the cumulative amount of time in milliseconds to deliver datato the adjacent system.

The following information can be derived from the line transmission fields:

� The average length of a delivered request unit is: tpLRUD/tpNRUD.

� The average amount of time to deliver a request unit is: tpTRUD/tpNRUD.

Note: This data does not provide an accurate measurement of line utilizationbecause only a portion of the data being transmitted on the line is meas-ured.

Receiving DataPerformance data is collected to record the number of request units and cumulativelength of data that is received.

The following fields are defined:

tpNRUR Specifies the number of request units received from the adjacentsystem.

tpLRUR Specifies the cumulative length of request units received from the adja-cent system.

The following information can be derived:

� The average length of a received request unit is: tpLRUR/tpNRUR.


Intermediate Session Traffic Work LoadThe work load caused by intermediate session traffic can be estimated because aseparate set of session traffic fields is defined for intermediate and end pointsession traffic. The values from the corresponding intermediate session field foreach priority level can be added together to determine the overall system workload. For example, INNRUR+IHNRUR+IMNRUR+ILNRUR is the total number ofrequest units received on all intermediate sessions.

The intermediate session work load can be reduced by decreasing the maximumintermediate sessions parameter in the network attributes, or decreasing the pacingcounts configured on the end point systems. The AS/400 system configures thepacing counts on the OUTPACING and INPACING parameters on the modedescription.

Control Traffic Work LoadThe work load caused by control traffic can be estimated by examining the networkpriority session traffic fields. Network priority is reserved for control traffic. High,medium and low priority are used by user traffic. APPN control traffic uses endpoint sessions only. Operations that change the number of sessions and alertcontrol traffic may use both end point and intermediate sessions.

Comparing Different Priority LevelsThe SNA performance measurements allow the proportion of network, high,medium and low priority traffic to be analyzed. High priority is typically reserved forinteractive jobs that require good response time and medium and low priority isassigned to batch jobs.

The priority level is configured in the Transmission priority parameter on the class-of-service description.

APPN Control Point Performance MeasurementsThe primary purpose of the APPN control point is to allow applications on onesystem to dynamically establish sessions with applications on another system.Because of the dynamics involved in APPN, there are many work activities that anAPPN network node or end node needs to perform to maintain the informationrequired to establish sessions. Refer to the APPN Support book for backgroundinformation and terminology for APPN.

The APPN performance measurements provide a granular breakdown of thesework activities. The file QAPMAPPN does not contain any data regarding proc-essing unit utilization or disk unit accesses. Information regarding processing unitutilization and disk unit accesses for the tasks that perform APPN functions can befound in the QAPMJOBS performance monitor file. A performance analyst can thendetermine the activities that APPN was performing (to better understand theresource utilization found in the QAPMJOBS file). Use the QAPMAPPN file withthe QAPMJOBS file to determine the effect of APPN functions on a system's per-formance.

The QAPMAPPN file does not contain any information regarding session traffic.APPN session traffic data is maintained in the file QAPMSNA. There is a set ofmeasurements for each active controller description on the system. The


QAPMSNA file data provides performance measurements to give a breakdown ofintermediate routing and session endpoint traffic. The session traffic data provides abreakdown based on the different transmission priorities that can be used. Refer to“Session Traffic Fields” on page 8-6 for more information on session traffic.

APPN Work ActivitiesThe following are the various APPN work activities:

� Topology maintenance

� Directory services registration and deletion requests

� Configuration changes

� Control point session activation and deactivation

� Control point presentation services

� Session setup activities

Topology MaintenanceThese work activities maintain the APPN topology database. The APPN topologydatabase allows routes through the APPN network to be calculated, based on aclass-of-service selected by the user initiating a session. You can display how oftenthe topology database is viewed using the Display APPN information(DSPAPPNINF) command.

Topology maintenance can account for a large amount of processing unit and diskunit accesses. In general, the amount of resource required for topology mainte-nance grows as networks become larger and as the APPN network becomesunstable. The instability of a network is caused by frequently activating and deacti-vating transmission groups or by having line failures and systems failures in thenetwork. Following are some key terms regarding topology maintenance and ashort explanation of how these work activities affect performance:

Transmission group (TG) update A TG update occurs when a controllerdescription on the local system has a status change (for example, itchanges from inactive to active). When the TG defines a connectionbetween two network nodes, this causes the local system to send atopology database update.

Topology database update (TDU) A TDU is the device used to broadcast a statuschange of a resource in the intermediate routing portion of an APPNnetwork. An AS/400 system sends TDUs for several different reasons. ATDU is a general data stream (GDS) variable that can block informationabout multiple resources into a single entity. Thus, if the topologyrouting services (TRS) component receives multiple TG updates, it canblock these together into a single TDU. TDUs are distributed to everynetwork node in the APPN network that is connected to the remainingsystems in the network using control point sessions.

Node congestion updates These occur when a network node has a status changein its capacity for performing intermediate routing. On the AS/400system, node congestion is based simply on the number of intermediatesessions that are currently active. Node congestion updates cause thelocal system to send TDUs.


Received TDUs APPN network nodes receive TDUs as well as send them. If TDUsare received frequently, this can degrade system performance. Thecounts maintained for received TDUs provide a breakdown between newand old resources.

One count tracks the number of times the most frequently used nodewas included in received TDUs during an interval. When many TDUsare received and the same node is always listed in the APPN perform-ance data, this could indicate a configuration problem where the listednode has updates sent continuously. This situation can have a seriouseffect on performance. For more details see the APPN Support book.

Initial topology exchange An initial topology exchange is an examination of theresources in the intermediate routing portion of the topology databasethat occurs any time control point sessions are established between twonetwork nodes. Any of the resources that have changed status or forwhich a TDU has been received are sent to the partner network node ina TDU. If one of the systems has refreshed its topology database or ifthis is the first initial topology exchange with the partner network nodesince performing a system IPL, the entire intermediate routing portion ofthe APPN topology database is sent.

Obsolete Topology Entry Removal Once every 24 hours the topology database isexamined to determine if any entries in the local system have not beenupdated in the past 15 days. The entries that have not been updatedare deleted. If the local system is a network node, the system sends aTDU once every five days (so other nodes do not delete the localsystem from their topology database).

Display APPN information (DSPAPPNINF) Each time the Display APPN Informa-tion (DSPAPPNINF) command is run with *TOPOLOGY specified for theinformation type (INFTYPE) parameter, every entry in the APPNtopology database is examined. In networks with a large amount oftopology, this can account for a significant number of read operationsfrom disk units.

Note: This does not directly affect topology maintenance.

Directory Services Registration and Deletion RequestsAPPN end nodes register and delete their local location names with their networknode server. For end nodes, these configuration change requests are trackedbecause configuration changes cause an end node to send the registration anddeletion requests.

These measurements are maintained on a network node to show the effort involvedin processing received location registration and deletion requests from attached endnodes. Various conditions cause an end node to send in registration and deletionrequests (for example, the activation of a control point session, or a configurationchange). The conditions that cause an end node to send these requests can befound in the configuration and control point session performance measurements.Multiple locations can be included in a single registration request (such as when anend node is registering all of its locations following control point session activation).

In general, registration and deletion requests should not cause a performanceburden on a network node because this type of information is not distributed toevery network node in the network.


Configuration ChangesThese work activities cause the APPN control point to update configuration informa-tion and can at times cause an update to be sent to one or more systems. Theactivities included in this section are:

� Change network attributes processing

� Local location list updates

� Remote location list updates

� Mode description updates

� Class-of-service description

Change network attributes (CHGNETA) All of the APPN tasks are involved inprocessing a Change Network Attributes (CHGNETA) command so localinformation can be updated. The topology routing services task sendsout a TDU if the local system is a network node and the route additionresistance (RAR) is changed. Changing the local system node type,local network ID, or local control point name can cause the APPNtopology and APPN directory databases to be deleted. This can indi-rectly affect performance (because additional processing is required toreconstruct these databases).

APPN local location list updates These cause a local location to be added to ordeleted from the APPN directory database. If the local system is an endnode with a CP-CP session established to a network node server, thesecause a registration or deletion request to be sent to the server.

APPN remote location list updates These cause a remote location to be added toor deleted from the APPN directory database.

Mode updates These cause the control point manager (CPMGR) task to update itsmode tables to reflect the addition, deletion, or update of a modedescription.

Class-of-service updates These cause the control point manager (CPMGR) andtopology routing services (TRS) tasks to update their class-of-servicetables to reflect the addition, deletion, or update of a class-of-servicedescription.

Control Point Session Activation and DeactivationThese work activities track the number of control point sessions that are startedand ended. These counts are classified as the locally controlled (contention winner)CP-CP sessions or the remotely controlled (contention loser) CP-CP sessions.

There are various details associated with the activation and deactivation of controlpoint sessions. Contention winner control point sessions are primarily used forsending data (TDUs, directory searches). Contention loser control point sessionsare used to receive control point data from other systems. The activation of a con-tention winner CP session has many similarities to the activation of a user session.The steps involved with the activation of a session (single hop route requests, acti-vate route requests, device selection) are discussed in “Session Setup WorkActivity Details” on page 8-19.

When the local system is an end node and it activates a control point session to itsnetwork node server, all of the local locations are registered with the network node.


The control point session performance measurements also provide counts of thenumber of control point sessions that are currently active. Variations in thesecounts can help explain changes in resource utilization over different time intervals.Because the number of active control point sessions can affect the number ofsystems involved in TDU search procedures, the APPN tasks that provide themajority of the function for control point session activation and deactivation arecontrol point manager (CPMGR) and control point presentation services (CPPS).

Control Point Presentation Services (CPPS)Control point presentation services handles all of the data transfer that occurs onthe CP-CP sessions for the other APPN tasks. Analysis of these counts provides asummary of the types of activities in which the APPN control point is involved overa given set of time intervals. This information is classified into data sent and datareceived for the various APPN transaction programs. These transaction programsare:

� Control point (CP) capabilities

� Topology database update

� Directory services for search processing

� Registration/deletion

To best utilize the APPN performance measurements, the control point presentationservices measurements (CPPS) should be analyzed first. These measurementsprovide a summary of the data traffic over the control point sessions for the variousAPPN transaction programs. This summary discusses on the correct APPN workactivities and isolates any APPN performance problems. For example, if a timeinterval shows a high number of directory services transactions and only a limitednumber of topology database updates, the session setup measurements, instead ofthe topology maintenance measurements, should be checked.

The control point presentation services measurements provide:

� The number of data received requests (data received from other networklocations that are directly connected to each other).

� The amount of data received.

� The number of send data requests (data sent to other network locations thatare directly connected to each other).

� The amount of data sent.

This information is provided for all of the different APPN transaction programs.These transaction programs are:

Control point (CP) capabilities Used to send and receive control point capabilitiesto adjacent systems immediately after activating control point sessions.In general, running CP capability transaction programs should onlyslightly affect system performance.

Topology database update Used to send and receive TDUs. TDUs are sent oncontention winner CP sessions and received on contention loser CPsessions. TDUs can significantly affect performance for network nodes.If the CPPS measurements seem abnormally high (compared to othertime intervals), check the topology maintenance data to determine thecause of the increase.


Directory services (DS) Used to send and receive search requests to other nodesin the network. Search processing can significantly affect performancefor network nodes, but generally it only slightly affects end nodes.Search requests and responses are sent asynchronously by the APPNdirectory services task. If the CPPS measurements seem abnormallyhigh (compared to other time intervals), check the session setup per-formance measurements to determine the cause of the increase.

Registration and deletion Used to send location registration and deletion requests(from an end node to a network node server). In general, registrationand deletion requests should not significantly affect performance.However, if a several requests are causing the CPPS and DS tasks toincrease processing unit use, check the directory services registrationand deletion requests measurements.

Session Setup ActivitiesThese measurements provide information on the various steps that are taken bythe APPN control point to process session initiation requests. Because establishingan APPN session is a highly distributed function, the measurements provide abreakdown of the work activity details based on the role a system plays in estab-lishing a session. For example, a network node performs certain functions to allowlocal users to establish sessions. However, a network node also performs func-tions to allow attached end nodes to establish sessions. The performance measure-ments in each case are separated so you can find where the resources are used.

The activities performed and the resources used vary between APPN end nodesand network nodes. Because APPN session setup is a function distributed betweenmultiple systems, it is necessary to classify session setup work into different workactivities.

Each of these work activities causes different types of work to run on the localsystem. Refer to “Session Setup Work Activities” on page 8-17 for a description ofthe session setup work activities. Refer to “Session Setup Work Activity Details” onpage 8-19 for a description of measurable work details associated with sessionsetup. Many of these details are common between the different work activities. Thesample data for session setup keeps separate counts and cumulative elapsed timesfor the different work activities being performed.

Following is some terminology used to describe various work activities performedby APPN. The definitions of these terms are based on the context of this dis-cussion.

Bind command The request unit sent by a node to set up the LU-LU session.

Broadcast search A search sent by a network node and eventually forwarded toevery network node in the network (connected by one or more CP-CPsessions).

Directed search A directory search sent by one network node to a single networknode. A network node sends this search if it has information in its direc-tory database that indicates the destination network node was the pre-vious owner or network node server of the end node that owns thelocation. A directed search may flow through multiple network nodesalong the way (these are intermediate nodes on a directed search). Onlythe destination of the directed search performs additional search logic.


Domain broadcast A search sent by a network node to its adjacent end nodes thatspecified they want these searches. Currently, the only time an AS/400system sends these to other AS/400 systems is in a multiple networkenvironment.

NNS(OLU) A network node serving an end node that is initiating a session setuprequest.

NNS(DLU) A network node serving an end node that is the destination of a sessionsetup request.

One hop search A search sent from an end node to a network node or from anetwork node to an end node. This search is only sent to a single node.

Session Setup Work ActivitiesFollowing is a list of the session setup work activities. Each work activity hasvarious detailed measurements associated with it. For each work activity, there is acumulative elapsed time measurement and a count of the number of times a givenwork activity was successful. The start time and end time measured (accounting forthe cumulative elapsed time measurements) and the criteria for counting a givenwork activity successful are listed with the work activity.

1. Locally started sessions (source)

Description: Sessions that are started on the local system, including explicitsession initiation requests by a user as well as internal session initiationrequests (for example, sessions started for session limit negotiation or alerttraffic).

Start: The system determines the APPC device description to use for sessioninitiation request.

End: The system provides information regarding the APPC device descriptionrequest. The information is either a list of devices or an error code.

Success: One or more device descriptions are returned to the operatingsystem.

2. Receiver of search requests (local system = EN)

Description: The local system, an end node, receives a search request fromits network node server.

Start: The directory services task receives a locate request from the CPPStask.

End: Directory services (DS) returns the locate search response to the CPPStask or the CP session when the system that sent the search fails.

Success: Directory services returns a positive response to the search requestit had received.

3. Search processing on for attached EN (local system = NN)

Description: The local system, a network node, has received a search requestfrom a served end node that is initiating a session. The local system is respon-sible for searching for the target system and then calculating a route to thedestination control point.

Start: The DS task receives a request from CPPS and determines it is asearch request from a served end node.


End: DS returns the locate search response to CPPS or the CP session withthe end node that sent the message indicating that the search had failed.

Success: DS sends a positive response to the locate search request, androuting information is supplied to the end node.

4. Intermediate node on a directed search

Description: The local system, a network node, has received a directed searchrequest from another network node. The only functions that need to be per-formed in this case are forwarding the search to the next hop of the route, andalso forwarding the search response to the system that had sent the search tothe local system.

Start: DS receives a directed search request from CPPS and realizes the localsystem is not the destination network node.

End: DS returns the locate search response to the system it received thesearch from or the CP session ends between the local system and either thesystem that sent the search to the local system or the system that the localsystem forwarded the search to.

Success: DS successfully sends the directed search, receives a positiveresponse, and successfully returns the directed search response to the systemthat had originally sent the search request.

5. Destination NN on a directed search - NNS(DLU)

Description: The local system, a network node, has received a directed searchrequest from another network node. In this case, the local system is the targetof the directed search because the location being searched for had at one timeresided on the local system or on an end node that was being served by thelocal system.

Start: DS receives a directed search request from CPPS and realizes the localsystem is the destination network node.

End: DS returns a positive response to the system that had sent the search tothe local system or the CP session ends with that system.

Success: The response given by DS to the system that had sent the search tothe local system is positive.

6. Broadcast search received

Description: Broadcast searches are processed only by network nodes. Whenthe local system receives a broadcast search, it sends the search to all of itsadjacent network node partners and it also determines if the location beingsearched for resides on the local system or on a served end node. Broadcastsearches are the most costly search types from a performance standpointbecause of the number of systems that are involved.

Start: DS receives a broadcast search request from CPPS.

End: DS has forwarded the search response to the system that sent the broad-cast search to the local system and it has processed all search responses fromsystems to which the local system forwarded the broadcast search.

Success: The response sent back to the system that sent the search to thelocal system is positive.

7. NN processing a received search from a node in a non-AS/400 network


Description: This work activity tracks the number of searches processed thatare started by systems in a different APPN network (based on network identi-fier). Only searches received from network nodes in another network arecounted. Note that only the systems on the boundaries of the network willmaintain these measurements.

Start: DS receives a search request from CPPS and determines it is from anode in another network.

End: DS returns the locate search response to CPPS or the CP session withthe non-AS/400 node that sent the message indicating that the search hadfailed.

Success: DS sends a positive response to the non-AS/400 node that sent thesearch request to the local system.

8. Network node processing a received bind from a node in the AS/400 (local)network without routing information

Description: The local system, a network node, is responsible for determiningthe control point that the target system resides on, calculating a route to thedestination control point, and forwarding the bind on to the next hop of theroute.

Start: The control point receives a bind request from the session connectormanager (the part responsible for establishing intermediate sessions) anddetermines that the request was received from a node in the AS/400 networkand that routing information does not exist.

End: The control point returns a response to the session connector managertask.

Success: The request for the intermediate session initiation is returned with apositive response (which means the link for the next hop of the route has beenlocated and is active).

Note: Work activities 9, 10, and 11 have the same start, end, and successdefinitions as work activity 8. Work activities 10 and 11 do not requireany search processing or route computation processing.

9. NN processing a received bind from a node in a non-AS/400 network withoutrouting information

10. NN processing a received bind from a node in the AS/400 network withrouting information

11. NN processing a received bind from a node in a non-AS/400 network withrouting information

Session Setup Work Activity DetailsFor APPN, session setup involves details such as:

� Initial screening to determine if existing sessions may be used

� Directory search processing to determine which system in the network owns thedestination location desired

� Route selection to determine the optimal route based on class of servicethrough the network

� Switched link activation

� Device selection and/or creation of a new device


These detailed measurements are stored separately for each distinct work activityin which the measurement can occur. For example, the system can issue a directedsearch as a result of several different work activities (in this case work activities 1,3, 7, 8, and 9). Therefore, five different sets of detailed measurements for directedsearches are there so that the person analyzing the data can determine whichactivities are causing the directed searches to run.

Following are explanations of some of the key terms of the work activity details:

Initial screening These measurements are functions performed by the locationmanager and the control point manager tasks. These measurementsindicate how many new sessions need to be started (which require fullcontrol point services to complete the request) and session requests sat-isfied by using existing bound sessions. There are also measurementsto count session initiation requests that get pended by the control point.The pending of session initiation requests improves performancebecause the directory search, route selection, and switched link acti-vation phases need only be done once for multiple session initiationrequests received.

Directory search processing This step involves determining the control point thatowns the target system of a session initiation request. The APPN partsthat are most affected by directory search processing are DS andCPPS. The effect of search processing on performance is greater on anetwork node than on an end node because of the various roles that anetwork node can have in search processing. Because a network nodeprocesses the first positive response it receives on a search request andsends this to the search originator, a network node can still process asearch request after the work activity that started the request has com-pleted. Even though the bind for a session may have already been sent,a network node may still be processing subsequent search responsesreceived from other nodes. The directory search processing phase canbe an asynchronous process if searches are sent to other systems,which can account for increased values in various cumulative elapsedtime measurements.

Route selection Route selection is carried out by the TRS task. There are differenttypes of routes that TRS calculates. A single hop route is done by anend node (when an end node has not received routing information froma network node server). A single hop route is also done for establishinga control point session. Request route processing is done by networknodes for establishing end-to-end routes based on a particular class-of-service.

Switched link activation This processing is primarily carried out by the machineservices control point (MSCP) task. MSCP receives activate routerequests to start switched link activation sequences. There are manyreasons for delays in this step (such as waiting for operator interventionto answer a message or dial a switched connection). This step can alsocause a controller description to be automatically created by the oper-ating system (which can also cause a delay).

Device selection This processing measures the number of times that the T2station IOM task is requested to select a device description. This stepcan lead to the automatic creation and/or vary on of device descriptions.


The measurements for automatic creation and/or vary on of devicedescriptions can be found in the QAPMSNA performance monitor file.

APPC ProtocolFor APPC, there are two types of transactions for which the Performance Toolscollect sample data: inbound and outbound.

An outbound transaction begins when the request is issued and ends when thecomplete response is received. An inbound transaction begins when a request isreceived and ends when a response is sent.

The transaction timings provide a picture of how much time is spent in processing atransaction on the local and remote systems.

Comm IOP

Program

Comm IOP

Program

Comm line

Comm line

1 2 45

Remote System B

36

RV2S089-3

System A

Figure 8-3. Using APPC Protocol Communications

From System A's PerspectiveSystem A is sending data to system B and is expecting a response from system B.Figure 8-3 shows the steps in system A’s outbound transaction.

1. System A puts , or transmits, data

2. System B gets , or receives, the data from system A

3. A program on system B processes the data and produces new data inresponse

4. System B puts the new data, which is its response to system A

5. System A receives the data, which is the response from system B

6. The program on system A processes data, determines the next request, andreturns to step 1

The following ratios of fields found in the QAPMJOBS file are effective performanceindicators:

JBPUTA/JBPUTN The average number of bytes per put operation. Larger valuesindicate greater efficiency because fewer put operations are necessary.

JBPUTA/JBRTI The average number of bytes buffered per transmit (request). Putoperations made by system A go into a communications buffer. Thesystem transmits the contents of the buffer when it fills up with oper-


ations requiring data to flow to the remote system. The higher thisnumber is, the better the buffer is utilized. When the buffer is used moreefficiently, the lower communications layers are called less often and theresult is better performance.

From System B's PerspectiveSystem B is receiving information from system A and will be sending a response tosystem A. In Figure 8-3 on page 8-21, steps 2, 3, and 4 make up system B'sinbound transaction. This is a subset of system A's outbound transaction.

2. System B gets, or receives, the data from system A3. A program on system B processes the data and produces new data inresponse4. System B puts the new data, which is its response to system A

Conversely, steps 4, 5, 6, 1, and 2 can be considered system B's outbound trans-action. Steps 5, 6, and 1 make up system A's inbound transaction, which is asubset of system B's outbound transaction.

The following ratios of fields found in the QAPMJOBS file are effective performanceindicators:

JBGETA/JBGETN The average number of bytes per get operation. Larger valuesindicate greater efficiency because fewer get operations are necessary.

JBGETA/JBRRI The average number of bytes made available to the program in abuffer. The receiving system buffers data received until the buffer fills upor until an operation (on the transmitting system) requires the immediatedelivery of data to the receiving program.

Notes:

1. A series of multiple put operations can be created by system A. At the end ofthese put operations, system A effectively passes control to system B through achange direction (CD) operation. System B can complete its first get operationwhen a buffer of data arrives from system A. It can process subsequent putoperations from system A as it receives them. However, it cannot send anydata back to system A until it receives the change direction (CD) indication.

2. System A's put operations can overlap system B's get operations.

APPC Performance NotesA complete end-to-end analysis of APPC performance includes the followingelements:

� Communications time

� IOP time on system A (outgoing and incoming)

� Line time (from system A to system B, and from system B to system A)

� IOP time on system B (incoming and outgoing)

� Processing time on system B

Knowledge of the application design, along with performance data from bothsystem A and system B, allows you to analyze the application's performance. Usingthe outbound time (in the JBPGIL field in the QAPMJOBS file) on the local system


and the inbound time (in the JBGGIL field in the QAPMJOBS file) on the remotesystem, the amount of time the local system spent waiting for the remote system torespond to its request can be determined. With the addition of information such asthe number of input and output operations plus the amount of data sent andreceived, average transaction times can be determined. The line speed can beused to determine how much the line slows processing and the effect of changingthis. The processing unit in the application can be used on a per transaction basis(where communications activity is continuous) to determine the effects of modelupgrades.

The Work Management book contains complete information on all the APPC infor-mation collected by the performance monitor.

Performance Measurement and SNADSIn general, SNADS sample data does not provide any direct performance tuningcapabilities. There are no distribution parameters that can be adjusted to affectSNADS performance (with a minor exception for distribution queue attributes andSNADS senders). However, the customer can do normal system job tuning andmeasure the results in distribution throughput using the sample data.

Performance tuning for SNADS jobs may involve adjusting the job priority or otherattributes contained in the job class or job description. A description of each joband the characteristics important for performance analysis and tuning is provided inWork Management. Unless otherwise noted in the detailed sections, SNADS jobshave the following common characteristics:

� All are submitted using the QSNADS job description.

� A separate routing entry exists in the QSNADS subsystem for each type ofSNADS job. This allows the customer to identify different job classes (priority)for each. The default is class QSNADS, which has a run priority of 40.

� All run under the QSNADS or QGATE user profile.

� All internal distribution objects (those not visible to the user) created by SNADSare owned by the QSNADS user profile. This identifies how much systemstorage is being used by distribution activities.

SNADS TransactionA SNADS transaction and a distribution within a SNADS job generally have a one-to-one relationship. A SNADS transaction is the processing done by a SNADS jobas it handles a distribution. Each distribution processed is considered a transaction,including both distributions processed successfully and distributions processed witherrors.

The following functions in a SNADS transaction are described in this section:

� Router

� Receiver

� Sender

� Gateway senders


Notes:

1. Distribution processing that ends with errors may result in another attempt ofthe same distribution. Thus, a single distribution may cause the transactioncount to be incremented multiple times. For example, the line drops during atransmission. Each send attempt counts as a transaction even though the samedistribution is being processed each time. Each transaction (ending with anerror) accounts for resources expended in the distribution attempt.

2. The number of transactions ending with errors is included in the error countprovided in the sample data.

Table 8-1. SNADS Transaction Types

Transaction Type SNADS Function

'01' SNADS Router

'02' SNADS Receiver

'03' SNADS Sender

'04' SystemView Distribution Services (SVDS) Receiver

'05' SVDS Sender

SNADS Gateway Senders

'08' SNADS DLS Gate (Document Library Services)

'09' SNADS Gate (VM/MVS Bridge, SMTP, X.400)

SNADS RouterThe QSNADS router function is the heart of SNADS. All distributions that flowthrough SNADS are processed by the router. It uses the system directory and dis-tribution services configuration to determine what queue or queues to put the dis-tribution on.

A distribution with multiple destinations may have a distribution copy placed on alocal delivery queue and multiple distribution queues. This is called fan-out . Somedestinations may be routed successfully while others result in router errors.

A router transaction begins when the router finds a distribution on its queue. Thetransactions ends when the distribution has been placed on all applicable queuesand removed from the router queue.

The SNADS router function has the following characteristics:

� The SNADS router function is a job that runs in the QSNADS subsystem and isstarted by the SNADS startup job (QZDSTART).

� The job name is QROUTER.

� The job's user profile and job description are QSNADS.

� The subsystem routing entry compare value is 'QROUTER'.

� The router job should remain active as long as the QSNADS subsystem isactive. If the router ends or is canceled, the subsystem must be stopped andrestarted to start the router.


� The router function can support only one router job.

SNADS ReceiverThe SNADS receiver function is a job that runs in response to a SNADS remotesender opening a session and doing an APPC evoke operation. The SNADSreceiver manages the receive side communications protocol for the SNADS conver-sation.

A receiver transaction begins when the receiver receives distribution data from thesender. The distribution data is separated and stored in an internal control block. Afile server object is created if the distribution carried one. The distribution is put onan internal queue for the SNADS router to process. The receiver then logs andsends confirmation to the sender function. The transaction ends when the confir-mation request is complete or the job ends for any reason (for example, a commu-nications error).

A SNADS receiver job has the following characteristics:

� It runs in the subsystem configured for the communications device that wasstarted by a remote sender. The default is QCMN subsystem.

� The job name is the same as the communications device name.

� The job's user profile, job description, and so on are determined by the subsys-tem's communications entry and routing entries. These normally default to theQSNADS user profile, QSNADS job description, and PGMEVOKE subsystemrouting entry.

� A receiver job runs until one of the following occurs:

– The evoking sender no longer has data to send.

– An error is detected by either the sender or receiver.

– The session ends abnormally (for example, the line fails).

� A receiver may be started repetitively over time by a job on the sending system(probably the same sender job).

� SNADS imposes no limits on the number of receiver jobs that can be active atthe same time. Multiple receivers can be active for the same device.

� The QSNADS subsystem does not have to be active. Receivers can queue dis-tributions for the router job regardless of the state of the router or QSNADSsubsystem.

SNADS SenderThe SNADS sender function manages the send side communications protocol forthe SNADS conversation. It starts the remote receiver and sends any available dis-tributions (queued on its distribution queue) to the remote system. SNADS sendersservice *SNADS type distribution queues.

The sender is sensitive to the following:

� The state (held or waiting) of the distribution queue.

� The state (held or waiting) of the queue entries.

� The send conditions configured for the queue.


The sender does not establish a communications session or send any distributionunless its distribution-queue conditions or states allow it.

When send conditions are met or they end, a certain amount of overhead isrequired to establish or end communications. This is not included in the sendertransaction (resource use time); it is, however, included in the overall job statistics.If errors occur during this activity, the sample data error count is incremented alongwith the active transition count but no other transaction data or counts will change.

A sender transaction begins when the sender dequeues the next distribution to besent (send conditions were previously met and a session is active). Distributiondata is put into code and sent to the receiver. If a file server object is present, thatdata is read and sent with the distribution. The sender waits for the receiver toconfirm the distribution, at which time it is logged and removed from the distributionqueue. This ends the transaction. The transaction can also be ended by any errorthat is detected during processing.

The SNADS sender function has the following characteristics:

� The SNADS sender function is a job that runs in the QSNADS subsystem andis started by the SNADS startup job (QZDSTART). One job is started for eachdistribution queue (type *SNADS) configured. Sender jobs may also be startedby configuration (CFGDSTSRV) as distribution queues are added, and by oper-ations (WRKDSTQ) if the operator starts a send operation.

� The job name is the same as the remote location name configured with thedistribution queue.

� The job's user profile and job description are QSNADS. The subsystem routingentry compare value is 'QSENDER'.

� The sender job should remain active as long as the QSNADS subsystem isactive, if no errors are detected. Sender jobs for queues with no time or depthspecified end as soon as the queue is empty. If the sender is detecting errorsand the retry count configured for the queue is exceeded, the sender job ends.The sender can be restarted by selecting the Send queue option on theWRKDSTQ display or issuing the SNDDSTQ command.

� There can be as many sender jobs as there are distribution queues.

� The sender function can support only one sender job per distribution queue.(Multiple sender jobs may sometimes be started for a particular queue but theywill eventually cancel each other until only one is left.)

� SNADS senders can be started (evoked as an APPC application) by remoteSNADS receivers. Although this function is supported by AS/400 senders, thereis no known SNADS implementation where a receiver will start a sender.

SVDS ReceiverThe SVDS receiver function is a job that runs in response to an SVDS remotesender opening a session and doing an APPC evoke operation. The SVDS receivermanages the receive side communications protocol for the SVDS conversation.

A receiver transaction begins when the receiver receives distribution data from thesender. The distribution data is separated and stored in an internal control block. Afile server object is created if the distribution carried one. The distribution is put onan internal queue for the SNADS router to process. The receiver puts a completionreport message unit on a queue. This ends the transaction. The transaction can


also be ended by an error detected during processing. The receiver will send thecompletion report message unit to the sender after the sender sends a changedirection (CD) indication. The receiver processes any other transactions from thesender. After the sender sends a CD indication, the receiver sends the completionreport message unit.

An SVDS receiver job has the following characteristics:

� It runs in the subsystem configured for the communications device that wasstarted by a remote sender. The default is QCMN subsystem.

� The job name is the same as the communications device name.

� The job's user profile, job description, and so on are determined by the subsys-tem's communications entry and routing entries. These normally default to theQGATE user profile, QSNADS job description, and PGMEVOKE subsystemrouting entry.

� A receiver job runs until one of the following occurs:

– The evoking sender no longer has data to send.

– An error is detected by either the sender or receiver.

– The session ends abnormally (for example, the line fails).

� A receiver may be started repetitively over time by a job on the sending system(probably the same sender job).

� There can be only one receiver job active per connection.

� The QSNADS subsystem does not have to be active. Receivers can queue dis-tributions for the router job regardless of the state of the router or QSNADSsubsystem.

SVDS SenderThe SVDS sender function manages the send side communications protocol for theSVDS conversation. It starts the remote receiver and sends any available distrib-utions (queued on its distribution queue) to the remote system. SVDS sendersservice *SVDS type distribution queues.

The sender is sensitive to the following:

� The state (held or ready) of the distribution queue.

� The state (held, ready, pending, or suspended) of the queue entries.

� The send conditions configured for the queue.

The sender does not establish a communications session or send any distributionunless its distribution-queue conditions or states allow it.

When send conditions are met or they end, a certain amount of overhead isrequired to establish or end communications. This is not included in the sendertransaction (resource use time); it is, however, included in the overall job statistics.If errors occur during this activity, the sample data error count is increased alongwith the active transition count. No other transaction data or counts will change.

A sender transaction begins when the sender dequeues the next distribution to besent (send conditions were previously met and a session is active). Distribution


data is put into code and sent to the receiver. If a file server object is present, thatdata is read and sent with the distribution.

The SVDS sender function has the following characteristics:

� The SVDS sender function is a job that runs in the QSNADS subsystem and isstarted by the SNADS startup job (QZDSTART). One job is started for eachdistribution queue (type *SVDS) configured. Sender jobs may also be startedby configuration (CFGDSTSRV) as distribution queues are added, and by oper-ations (WRKDSTQ) if the operator starts a send operation.

� The job name is the same as the remote location name configured with thedistribution queue.

� The job's user profile is QGATE. The job description is QSNADS. The sub-system routing entry compare value is 'QSVDSSND'.

� The sender job should remain active as long as the QSNADS subsystem isactive, if no errors are detected. Sender jobs for queues with no time or depthspecified end as soon as the queue is empty. If the sender is detecting errorsand the retry count configured for the queue is exceeded, the sender job issuspended. The sender can be restarted by selecting the Send queue optionon the WRKDSTQ display or issuing the SNDDSTQ command.

� There can be as many sender jobs as there are distribution queues.

� The sender function can support only one sender job per distribution queue.(Multiple sender jobs may sometimes be started for a particular queue but theywill eventually cancel each other until only one is left.)

� SVDS senders can be started (evoked as an APPC application) by remoteSVDS receivers. Although this function is supported by AS/400 senders, thereis no known SNADS implementation where a receiver will start a sender.

SNADS Gateway Senders (DLS Gate and VM/MVS Bridge)Gateway senders are not a function of SNADS architecture. AS/400 SNADSsupport provides distribution queuing and scheduling support for other distributionfunctions. This support is provided through distribution queues (queue types *DLSand *RPDS) and the SNADS gateway sender function.

Gateway senders are similar in every respect to SNADS senders except thatSNADS does not handle any communications nor does it matter if the distributionever leaves the local system. Based on the same queuing controls as SNADSsenders, distributions are handed over to the appropriate bridge function. When thebridge function confirms that it has successfully received (or processed) the distrib-ution, the distribution is removed from the SNADS queue.

The transaction begins when it is time to send and a distribution is found on thequeue. The distribution data is put into code for the bridge function along with anyfile server object. The gate sender waits for a response from the bridge indicatingthe distribution was sent; then the distribution is logged and removed from thequeue. This ends the transaction. Any error detected by the gateway sender or anerror response from the bridge would also end the transaction.

Gateway senders have the same characteristics as the SNADS senders except:

� The job's user profile is QGATE.

� The subsystem routing entry compare value is 'QGATEWAY'.


� The bridge function may or may not completely process the distribution underthe gateway sender job. All current implementations process the distribution inother jobs. Therefore, the sample data only reflects the resource required tohand over the distribution. One possible exception is the resource use time.This may reflect total time, depending on when the bridge function acknowl-edges receipt of the distribution.

Table 8-2. Sample Data for Each SNADS Function

Data FieldDescription Field Name

SNADSRouter

SNADS orSVDSReceiver

SNADS orSVDSSender

SNADSDLS Gate

SNADSRPDSGate

Transactioncount

SNNTR X X X X X

Resource usetime

SNRUT X X X X X

FSO count SNFSO X X X X X

FSO byte count SNFSOB X X X X X

Transaction time SNTRT X X X X X

Error count SNERR X X X X X

Active transi-tions count

SNATN X X X X X

Recipient count SNNRC X X X X X

Fan-out count SNFOC X – – – –

Local distributioncount

SNLDC X – – – –

SNADS Sample DataThis section describes the sample data provided by SNADS. The data collected isthe same for all SNADS jobs (that is, the sample data format does not change).However, not all entries apply to every SNADS function (sample data subtype).Data that does not apply to a function will be zero when the data is written.

Table 8-2 summarizes the sample data supported for each SNADS function.

Sample Data InterpretationThe primary purpose of the SNADS specific sample data is performance planning.This data provides statistics on what SNADS activity is taking place over time. Itindicates the amount, size, and location of the distribution load on the system.

This sample data does not include resources used for local distribution (from a localuser to a local user). SNADS involvement is limited to asynchronous remote distrib-ution. This includes remote systems sending mail to the local system, the local sys-tem's role as an intermediate node, and local distribution to a remote system.

The following are various SNADS jobs described by transaction type:

� The router job (type X'01') indicates the total amount of mail being handled bythe system. This reflects distributions from receivers, distributions originated


locally, distributions arriving from one of the SNADS bridge interfaces, as wellas DSNX-PC activity. Assuming there is not substantial bridge activity, thenumber of distributions originating locally is the difference between the distrib-utions routed and the distributions received.

� SNADS receiver jobs (type X'02') and SVDS receiver jobs (type X'04') indi-cate the amount of mail arriving on the local system from remote SNADSsources. Specific receiver jobs indicate the amount arriving from the associatedlocation. Receiver jobs must be processed in an aggregate because thesending system evokes a receiver job whenever it has something to send. Thiscauses receiver jobs to start and stop often.

� SNADS sender jobs (type X'03'), SNADS gateway sender jobs (types X'08'and X'09'), and SVDS sender jobs (type X'05') represent distributions leavingthe system. These may originate from all the same sources as described abovefor the router. Because there may be multiple paths off a system (connectionsto multiple destinations), a single distribution processed by the router may becopied to multiple distribution queues and therefore represent a sender trans-action in multiple sender jobs.

For SNADS receivers, routers, and senders, the job data reflects the real proc-essing time, and for receivers and senders it also reflects the APPN/APPCresources used. Gateway senders are a little different in that the data is onlyhanded over to a bridge function; there may be additional processing in other jobs.No communications take place in a gateway sender.

Note: Although SVDS senders are defined with user profile QGATE, they do usecommunications.

SNADS Sample Data Field DescriptionsTransaction count (SNNTR): Under normal conditions, the transaction count indi-cates how many distributions have been processed by the respective jobs. In thecase of the router, it also indicates how many SNADS distributions are flowingthrough the system.

Transaction count is not an absolute distribution count:

� A router error indicates one or more recipients failed. If no recipients wererouted successfully, the distribution goes no further. If at least one recipientwas valid, the distribution is placed on one or more queues.

� Receiver and sender errors usually represent distribution attempts that failedrather than distributions that failed (for example, when the line goes down); atsome future time, the distribution will be successful. Therefore, when this typeof error has occurred, the transaction count is incremented once when the dis-tribution attempt is successful and one or more times when it fails. Note,however, that certain irrecoverable errors can occur and result in the deletion ofthe distribution.

� Distributions can be deleted from queues by operator action. This can occurduring distribution or between distribution attempts.

� Transaction count is not updated when an error occurs prior to the start of thetransaction—even though the error count may be updated.

Resource Use Time (SNRUT): This indicates how long it took the job to processthe transaction. It is a function of system loading, relative job priorities, and commu-nications line speed (receivers/senders). Another important cause is the size of the


distribution. Distributions that carry large amounts of data (see FSO count ) takelonger to send and receive.

Longer resource use times (especially for senders) also mean longer transactiontimes for subsequent queued distributions.

Size (FSO) (SNTRT): Some distributions are very small (for example, messages)and do not require much communications resource to transfer. Other distributionscan carry data objects or documents. In addition to the obvious effect on communi-cations, these distributions require added resource and processing time to bestored on or copied from the local system (only one copy is made).

The amount of data being carried increases all resources and measurements asso-ciated with the job.

The FSO count (SNFSO) provides a comparison between the number of trans-actions with and without file server objects. Message distributions do not file serverobjects associated with them. The FSO byte count (SNFSOB) also indicates howmuch data is being moved by the distributions carrying FSOs.

Errors: The error count should normally be very low or 0. Some router errors maybe expected and reflect an user ID that is not valid or a system that was notentered in the routing table. Some sender errors may be expected if the remotesystem is down or there is a line problem.

In this case, the error count (SNERR) and active transitions count (SNATN)increase without affecting other transaction counts and data.

If line performance is a problem, error rates for senders and receivers may indicatethat the line is not staying up long enough to complete sending of a distribution,causing distributions to be sent multiple times.

Recipients: The recipient count (SNNRC) indicates how many users are in thedestination list of the distribution. These may be individual users or names of dis-tribution lists that expand at the destination systems. The number of recipients hasa major effect on the router but little effect on senders and receivers.

Distributions with multiple recipients may go to multiple destination systems throughdifferent distribution queues as well as to the local system. One distribution copy isplaced on each queue regardless of how many recipients belong to that queue. Therouter fan-out count (SNFOC) and local distribution count (SNLDC) indicatewhere distributions are going (remote/local) and to how many different queues.

Transitions and Queuing Time: The active transitions count indicates how oftenthe job was waiting for a distribution to process (provided other controls did notprevent activity) or how often a sequence of one or more distributions was proc-essed. Queuing time is a measure of distribution delay. Queuing time is the differ-ence between transaction time and resource use time.

� For the router, job transitions are not expensive. A high transition rate indicatesthat the router is moving distributions quickly. A low transition rate combinedwith longer queuing times may indicate that the router's job priority is too lowfor the distribution rate.


� Senders do not send unless queue conditions are met. These include: queue isready, time is within from/to time, queue depth is reached, and distributions arein the queue. When the conditions are met, the sender does the following:

– Passes to an active state (queue state changes from Waiting to Sending).

– Tries to establish a session.

– Tries to start the remote receiver.

Because this is substantial additional distribution overhead (and the most errorprone), the active transitions count was provided.

If the transition count represents a high percentage of sender transactions, andperformance is vital, an increase to the queue depth should be considered.Queuing time can be used to balance the distribution delay on the send queueas opposed to the number of transitions.

A high sender transition rate accompanied by high error counts might also indi-cate that the sender is experiencing difficulty establishing communications andis in a wait-retry recovery loop.

� On a target system, a receiver job is started every time the sender job makesan active transition. This is additional overhead that is also reduced by reducingthe remote sender transitions as described above.

The transition count for receiver jobs parallels the transition count for the asso-ciated remote sender. A high transition count relative to the number of distrib-utions received from a remote location may indicate a need to make someremote sender adjustments or consider using prestart jobs for SNADSreceivers.

SNADS Performance Notes1. The run priority of SNADS jobs can be changed by changing the class of the

corresponding subsystem routing entry.

� The router's priority can be raised to increase throughput when there areperiods of heavy interactive activity using SNADS. System performancemay be satisfactory even if the router has a priority higher than interactive.However, if a system problem occurs (for example, a loop), the router couldtake over the system.

� The receiver's priority can be raised by adding a routing entry with acompare value of 'QZDRCVR' at position 37 of the routing data.

2. When distributions continually arrive on a sender queue, but at a rate slowerthan required to send, system resource will be wasted, constantly starting andstopping sessions on both local and remote systems as well as starting jobs onthe remote system.

� The queue depth can be used to allow some number of distributions intothe queue before sending begins. This also has the benefit of allowingadditional distributions to arrive on the queue while the queue is beingemptied. However, the distribution is delayed until enough distributionsaccumulate to satisfy the send conditions. Distribution rates, queuing times,and queue active (send) transitions are available in the sample data tomeasure this.


� Prestart jobs can be used on the remote system to reduce receiver jobstartup overhead.

3. Activity to or from a particular remote location can be determined by looking atthe data for the senders and/or receivers associated with that remote location.The job name is used to select these jobs.

Each sender is named by the remote location name specified in the SNADSconfiguration and the corresponding device. Each receiver job name is thesame as the device carrying the conversation. If device names are the same asthe remote location name (usually true), all send and receive activity to a partic-ular remote location can be observed using the remote location as the jobname.

OS/400 File ServerTransaction information is collected for two types of file server shared folders trans-actions. Both transaction types are handled within the Licensed Internal Code. Thetransaction types are the following:

� Requests from personal computers; the transaction type is *TNS (Transaction).

� Replies sent to the personal computer through T2; the transaction type is*QUEUE (Measuring queuing times).

For the first transaction type (request from a personal computer), both the time therequest is received and the time the request is finished are logged. For theLicensed Internal Code requests, the times should be very short. Locks/Unlockstypically are only one or two milliseconds. Reads/Writes depend on how muchinput/output needs to be done. Change End of File, Force Buffers, and Resets offiles are also handled.

The OS/400 program handles the following requests:

� Create

� Delete

� Open

� Close

� Directory (List file attributes)

� Make directory

� Remove directory

These requests are not logged for transaction data.

Personal computer functions like the copy or type function are classified into mul-tiple requests (usually list file attributes, open file, read/write, and close). Only thetimes for read and write requests are logged.

The second transaction type described (replies sent to the personal computer) logsthe amount of time it takes for T2 to respond to the file server stating that the reply(from the file server to the personal computer) has been sent. This is done for com-mands handled by both the OS/400 program and the Licensed Internal code. Also,a single command from the personal computer, like a read request, could result in


multiple queuing operations. These times should also be short. Figure 8-4 onpage 8-34 shows this transaction type.

23

4

7

1

T2

5

6

8

AS/400 System

Server

RV2S072-3

PC Application

Personal Computer

Figure 8-4. T2 transaction type

1. PC application sends request to T2

2. T2 sends the request to Licensed Internal Code server

3. Server logs the following

a. Start of transaction

b. End of transaction

c. Start of queue transaction

4. Licensed Internal Code server sends reply to T2

5. T2 sends the reply to PC application

6. T2 sends acknowledgment to Licensed Internal Code server

7. Licensed Internal Code server logs the end-of-queue transaction

8. PC application receives a reply

The transaction times start after the server gets the request and end before a replyis sent.

The total transaction time (in seconds) is stored in the JBRSP field in theQAPMJOBS file. The number of transactions (5250 only) is stored in the JBNTRfield in the QAPMJOBS file. These fields are also updated by display I/O trans-actions and by pass-through transactions.

OS/400 file server jobs run in the QSERVER subsystem.

Pass-Through Transactions

Enter

ViewDisplay

Source System Target System

RV2S071-1

3 4

4

1 2

6 5

Figure 8-5. Source Pass-through Transaction Path


Figure 8-5 shows the flow of data for a pass-through transaction. The followingoccurs:

1 A user presses the Enter key, sending a request for data.

2 The request for data is then sent to the target system.

3 The transaction data leaves the source system.

4 The transaction data is on the network.

5 The transaction data is sent from the target system to the sourcesystem.

6 Data appears on the display.

1→2 Data is in the source system Pass-through is processing data

2→3 Service time

3→5 Display wait time

5→6 Data is in the source system

1→6 Transaction

Pass-Through Performance NotesThe target program on a session time includes only trace points (no sample data).Here are some useful formulas:

Display wait time (3→5) The time from when the source system sends a requestto when it receives the data from the target system.

Service time (2→3) The time from when the source system sends a request fordata to the target system until the requests are on the network.

Transaction time (1→6) The time from when a user presses the Enter key until anew display appears.

The total transaction time (in seconds) is stored in the JBRSP field inthe QAPMJOBS file. The number of transactions (5250 only) is stored inthe JBNTR field in the QAPMJOBS file. These fields are also updatedby display I/O transactions and by Client Access shared folders trans-actions.

Data Queue TransactionsData queues provide a means for one job to start a work activity in another serverjob. A data queue transaction identifies and provides a means of measurement forthis server work activity with the following boundaries:

Program A Program B

Data Queue RV2S091-1

Figure 8-6. Data Queue Transaction


1. Program A sends data to the data queue. This is the start of the applicationinput queuing time.

2. Program B dequeues the data. This ends the application input queuing time.

The total application queuing time (in hundredths of a second) is stored in theJBAIQT field in the QAPMJOBS file. The number of application queuing trans-actions is stored in the JBNAIQ field in the QAPMJOBS file. These fields arealso updated by display I/O transactions. This also starts the resource utiliza-tion time.

3. Program B dequeues the next data. This ends the resource utilization time.

The total resource usage time (in seconds) is stored in the JBRUT field in theQAPMJOBS file. The number of resource usage transactions is stored in theJBNRU field in the QAPMJOBS file. These fields are also updated by displayI/O transactions.


Chapter 9. Performance Graphics

This chapter describes the functions that allow you to work with performance datain a graphical format. The performance data is collected using the Start Perform-ance Monitor (STRPFRMON) command. The graphs can be displayed interactively,printed, plotted, or saved to a graphics data format (GDF) file for use by other utili-ties, such as the Business Graphics Utility (BGU).

Note: This chapter does not refer to Capacity Planning graphics. For informationabout using the graphics feature of the capacity planner, see the BEST/1Capacity Planning Tool book.

Summary—Manager FeatureTwo distinct types of graphs can be displayed: performance graphs and historicalgraphs. Performance graphs use the performance data collected from a single runof the performance monitor. Performance graphs are useful for singling out jobsthat are performing poorly or evaluating the activities performed by a user or classof users on the system during a specified period.

Historical graphs use performance data collected from several runs of the perform-ance monitor. Historical data is the summary of the performance data created bythe STRPFRMON command. The Create Historical Data (CRTHSTDTA) commandis used to summarize the performance data for use by the historical graphs. Histor-ical graphs are used to show how the performance of a system has changed overtime.

1. Create a graph format using the Create Graph Format (CRTGPHFMT)command. (Graph formats are reusable.)

2. Collect performance data using the STRPFRMON command.

3. Display the graph using the Display Performance Graph (DSPPFRGPH)command.

Use the following steps to display a historical graph:

1. Create a graph format using the CRTGPHFMT command. (Graph formats arereusable.)

2. Collect performance data using the STRPFRMON command.

3. Create the historical data using the CRTHSTDTA command.

4. Display the graph using the Display Historical Graph (DSPHSTGPH) command.

When you select option 9 (Performance graphics) on the IBM Performance Toolsmenu, the Performance Tools Graphics menu appears.


à ð PERFORMG Performance Tools Graphics

System: ABSYSTEM


1. Work with graph formats and packages

2. Work with historical data

3. Display graphs and packages



===> __________________________________________________________________

_______________________________________________________________________



á ñ

You can also reach this menu by typing the Start Performance Graphics(STRPFRG) command on the command line of any display. From this menu, youcan work with performance data in a graphical format.

Work with Graph Formats and Packages—Manager FeatureGraph formats are templates or outlines used by the DSPPFRGPH and theDSPHSTGPH commands to display graphs in a user-defined format. Table 9-1shows the 15 predefined graph formats included in QPFRDATA, the IBM-suppliedperformance library.

Table 9-1 (Page 1 of 2). QPFRDATA Graph Formats

Graph Format Name Description

QIBMASYNC Asynchronous disk I/O per second againsttime

QIBMCMNIOP Communications IOP use against timeQIBMCMNLIN Maximum communications line use against

timeQIBMCPUPTY Processor unit use of jobs with priorities

0-19, 20-39, 40-59, 60-79, and 80-99against time

QIBMCPUTYP Processor unit use of batch, interactive, andsystem jobs against time

QIBMDSKARM Disk arm use against timeQIBMDSKIOP Disk IOP use against timeQIBMLWSIOP Local work station IOP use against timeQIBMMFCIOP Multifunction communications IOP use

against timeQIBMMFDIOP Multifunction disk IOP use against timeQIBMDSKOCC Percentage of disk occupied against timeQIBMRSP Interactive response time against timeQIBMTOTDSK Total disk I/O per second against time


Graph packages allow you to group several graph formats into a single entity. Thisis useful for printing, displaying, or plotting a number of graphs at once. Instead ofhaving to issue several DSPPFRGPH or DSPHSTGPH commands to print severalgraphs, you can use the package name (one command) to print all of the graphs inthe graph package. Also included in QPFRDATA is a predefined graph package,QIBMPKG, which contains the 15 IBM standard graph formats.

If you select option 1 (Work with graph formats and packages) on the PerformanceTools Graphics menu, the Work with Graph Formats and Packages displayappears.

à ðWork with Graph Formats and Packages

Library . . . . . . . . . . . QPFRDATA


1=Create graph format 2=Change 3=Copy 4=Delete

5=Display sample graph 6=Create package 8=Display package contents

Format/

Option Package Type Text

_ __________ _________________________________________

_ PACKAGE1 PACKAGE Graph Package containing format w/ func. areas

_ QIBMPKG PACKAGE IBM Graph Package

_ FORMAT1 FORMAT CPU Utilization vs. Time-Functional Areas

_ NWCTEST FORMAT

_ QIBMASYNC FORMAT Asynchronous Disk I/O per Second vs. Time

_ QIBMCMNIOP FORMAT Communications IOP Utilization vs. Time

_ QIBMCPUPTY FORMAT CPU Utilization vs. Time (Priority)

_ QIBMCPUTYP FORMAT CPU Utilization vs. Time (Job Type)

_ QIBMDSKARM FORMAT Disk Arm Utilization vs. Time

More...

F3=Exit F5=Refresh F12=Cancel F15=Sort by format F16=Sort by text

á ñ

This display shows you the graph formats and graph packages that exist in thelibrary specified in the Library field. The graph format or graph package name, aformat or package indicator, and a text description appear on the display. If youcannot find the format or package you want to work with, use the appropriate func-tion key to sort the formats and packages. You can sort them by name, type, ortext description. When you find the graph format or package you want to work with,select the function you want to perform by typing the appropriate option in theOption field and pressing the Enter key.

If you are searching for a graph format or graph package located in a library that isdifferent from the one currently listed in the Library field at the top of the display,type a new library name in the field and press the Enter key. A list of the graphformats and graph packages available in the library you specified appears. You canthen select one of them to work with.

Table 9-1 (Page 2 of 2). QPFRDATA Graph Formats

Graph Format Name Description

QIBMTNS Transactions per hour against timeQIBMSYNC Synchronous disk I/O per second against

time

Chapter 9. Performance Graphics 9-3

Create Graph Format—Manager FeatureTo create a new graph format, type a 1 (Create graph format), the graph formatname, and the description on the first line under the Option, Format/Package, andDescription columns, and press the Enter key. The CRTGPHFMT command promptappears.

Specify how your graphs are displayed by selecting from the following options:

� Titles

� X-axis data

� Y-axis data

� Data type

� Individual line breakdown

� Graph type

Graph Types—Manager FeatureThe graph types available are:

� Line

� Scatter plot

� Surface

� Floating bar

� Composite bar

Line GraphsUse line graphs to show change occurring over time. Line graphs can representincreases, decreases, trends, and general fluctuations of quality.

BatchInteractSystem

RV2S084-0

80

70

60

50

40

30

20

10

0

CPUUtilization

18:0016:0014:0012:0010:0008:00Time

Monday’s Performance DataCPU Utilization vs. Time (Job Type)

Press Enter to continue.F3=ExitF12=Cancel

F6=PrintF16=Save GDF

F9=OverlayF17=Plot

Figure 9-1. Line Graph: Data Represented as Lines

Each plotted point is shown by a marker; the plotted points are connected to form acontinuous line. Each line is assigned a different color. If lines overlap, the color ofthe last legend entry at that point is displayed.


Scatter PlotsScatter plots are similar to line graphs, except that the lines that connect the datapoints are not drawn.

x

x

x x

x x

xx x x x x

x xx xx xx x xx x x

xx x

x

x xx

x xx x

xx x x

+

+

+++

+

x

+

RV2S078-0

80706050403020100

Monday’s Performance DataCPU Utilization vs. Transactions per Hour

CPUUtilization

Transactions per Hour

x+

3000260022001800140010006002000

BatchInteractSystem



F9=OverlayF17=Plot

Figure 9-2. Scatter Plot: Data Represented as Markers

Surface GraphsUse surface graphs like line graphs to show changes occurring over time. Surfacegraphs emphasize volume by shading the area between the lines and the X-axis ifyou specify Y (yes) for the area fill option.

Note: If you do not use the area fill option in your surface graph, your graph willbe a cumulative line graph. If there is a legend entry with a value of zero toplot, its line covers the line plotted previously because there is no change toplot. Although shading requires more time to display or plot than simplydrawing the lines, the area fill option may show more clearly which legendentries represent the different areas, particularly in cases where a line ofone color may cover another.

Time

RV2S081-0

BatchInteractSystem

10:3010:0009:3009:0008:3008:00

5550454035302520151050

CPUUtilization

CPU Utilization vs. Time (Job Type)



F9=OverlayF17=Plot

Figure 9-3. Surface Graph: Data Represented as Shaded Regions


Bar GraphsUse bar graphs to show changes occurring over time, parts of an entity, relation-ships between variables, and comparisons.

Use composite-bar graphs to show how parts comprise the entity, and how theentity relates to other entities.

BatchInteractSystem

9080706050403020100

RV2S074-0

18:0016:0014:0012:0010:0008:00Time

CPUUtilization




F9=OverlayF17=Plot

Figure 9-4. Composite-Bar Graph

Floating-bar graphs are similar to composite-bar graphs, except that the first com-ponent is not shown. Use floating-bar graphs to show the lower limits of eachentity, in addition to the relationship of the elements that comprise the entity.

BatchInteractSystem

RV2S083-0

9080706050403020100

CPUUtilization


18:0016:0014:0012:0010:0008:00Time



F9=OverlayF17=Plot

Figure 9-5. Floating-Bar Graph

Data Types—Manager FeatureData types control the number of lines displayed in your graph. They are a meansof categorizing the information provided in your graph. For example, if you want thegraph CPU Over Time and want a separate line plotted for every priority data type,you would specify *PRIORITY as your data type. You would then be presentedwith a display that would allow you to enter 1 to 16 priority ranges for plotting in thisparticular graph. Data types, therefore, control the legend entries in your graph.

Data types available for graphing are:


All Jobs *ALL (default)

Job Type *JOBTYPE

Priority *PRIORITY

Functional Area *FCNARA

IOP (input/output processor) *IOP

Disk *DISK

Communications Lines *CMNLINE

Valid Data Types for Axis SelectionsTable 9-2 shows the possible combinations for X-axis and Y-axis values based onthe data type being graphed. For example, if you want to graph Time against DiskIOP Utilization, specify a data type of *IOP.

Table 9-2 (Page 1 of 3). Valid X-axis and Y-axis Values

Y-Axis

X-Axis

TimeCPUUtil

Transper

Hour

TotalNbrof

TransRespTime

SyncDiskI/OperSec

TotalSync

I/O

AsyncDiskI/OperSec

TotalAsync

I/O

TotalDiskI/OperSec

TotalDiskI/O

CPUUtil

X2 — X1 X1 X1 X1 X1 X1 X1 X1 X1

TransperHour

X2 X1 — X1 X1 X1 X1 X1 X1 X1 X1

TotalNumberofTrans

X2 X1 X1 — X1 X1 X1 X1 X1 X1 X1

Re-sponseTime

X2 X1 X1 X1 — X1 X1 X1 X1 X1 X1

SyncDiskI/O perSecond

X2 X1 X1 X1 X1 — X1 X1 X1 X1 X1

TotalSyncDiskI/O

X2 X1 X1 X1 X1 X1 — X1 X1 X1 X1

AsyncDiskI/O perSecond

X2 X1 X1 X1 X1 X1 X1 — X1 X1 X1

TotalAsyncDiskI/O

X2 X1 X1 X1 X1 X1 X1 X1 — X1 X1



Y-Axis

X-Axis

TimeCPUUtil

Transper

Hour

TotalNbrof

TransRespTime

SyncDiskI/OperSec

TotalSync

I/O

AsyncDiskI/OperSec

TotalAsync

I/O

TotalDiskI/OperSec

TotalDiskI/O

TotalDiskI/O perSecond

X2 X1 X1 X1 X1 X1 X1 X1 X1 — X1

TotalDiskI/O

X2 X1 X1 X1 X1 X1 X1 X1 X1 X1 —

ComIOP Util

X3 — — — — — — — — — —

DiskIOP Util

X3 — — — — — — — — — —

LocalWorkStationIOP Util

X3 — — — — — — — — — —

Multi-functionComIOP Util

X3 — — — — — — — — — —

Multi-functionDiskIOP Util

X3 — — — — — — — — — —

DiskArmUtil

X4 — — — — — — — — — —

DiskPercentOccu-pied

X4 — — — — — — — — — —

ComLineUtil

X5 — — — — — — — — — —

| Logical| data-| base| I/O

| X6| X6| X6| X6| X6| X6| X6| X6| X6| X6| X6



Y-Axis

X-Axis

TimeCPUUtil

Transper

Hour

TotalNbrof

TransRespTime

SyncDiskI/OperSec

TotalSync

I/O

AsyncDiskI/OperSec

TotalAsync

I/O

TotalDiskI/OperSec

TotalDiskI/O

Key:

1. A graph type of *SCATTER and data type of *ALL, *FCNARA, *JOBTYPE, or *PRIORITY are required.

2. A data type of *ALL, *FCNARA, *JOBTYPE, or *PRIORITY is required.

3. A data type of *IOP is required.

4. A data type of *DISK is required.

5. A data type of *CMNLINE is required.

| 6. A data type of *JOBTYPE and a job type of *DDM are required.

Legends—Manager FeatureThe legends displayed in the graph are controlled by the data type specified (forexample, *JOBTYPE). The maximum number of legend entries you can specify foreach data type is as follows:

Data Type Maximum Legend Entries

All 1

Job Type 16

Priority 16

Functional Area 16

IOP 2

Disk 2

Communications Line 16

Create Graph Package—Manager FeatureTo create a new graph package, type a 6 (Create graph package), the graphpackage name, and the text description on the first line under the Option,Format/Package, and Text columns, and press the Enter key. The Create GraphPackage display appears.


à ðCreate Graph Package

Graph package . . : PACKAGE2

Library . . . . : QPFRDATA


1=Select 5=Display sample graph

Option Format Text

_ FORMAT1 CPU Utilization vs. Time-Functional Areas

_ FORMAT2 Response Time vs. Time-Functional Areas

_ QIBMASYNC Asynchronous Disk I/O per Second vs. Time

_ QIBMCMNIOP Communications IOP Utilization vs. Time

_ QIBMCPUPTY CPU Utilization vs. Time (Priority)

_ QIBMCPUTYP CPU Utilization vs. Time (Job Type)

_ QIBMDSKARM Disk Arm Utilization vs. Time

_ QIBMDSKIOP Disk IOP Utilization vs. Time

_ QIBMDSKOCC Percentage of Disk Occupied vs. Time

_ QIBMLWSIOP Local Workstation IOP Utilization vs. Time

_ QIBMMFCIOP Multifunction IOP (Comm) Util vs. Time

More...

F3=Exit F5=Refresh F12=Cancel F16=Sort by text

á ñ

On this display, type a 1 (Select) by any graph formats that you want to include inthe graph package. If you are unsure about including a graph format in thepackage, type a 5 (Display sample graph) by the format in question. This displays asample graph using the format selected. When you have made all of yourselections and there are only 1’s in the Option column, press the Enter key tocreate the graph package.

Change Graph Formats and Packages—Manager FeatureTo change an existing graph format or graph package, type a 2 (Change) next tothe format or package name on the Work with Graph Formats and Packagesdisplay, and press the Enter key. If you are changing a graph format, the ChangeGraph Format (CHGGPHFMT) command prompt appears. Make your changes andpress the Enter key. If you are changing a graph package, the Change GraphPackage display appears.


à ðChange Graph Package



Text . . . . . : Text for package 1


1=Select 5=Display sample graph

Option Format Text

1 FORMAT1 CPU Utilization vs. Time-Functional Areas

1 FORMAT2 Response Time vs. Time-Functional Areas

1 QIBMASYNC Asynchronous Disk I/O per Second vs. Time








More...

F3=Exit F5=Refresh F1ð=Restore list F12=Cancel

F15=Sort by format F16=Sort by text

á ñ

On this display, 1’s appear next to the graph formats that are already included inthe graph package. To eliminate a graph format from the package, replace the 1with a blank. To add additional graph formats to the package, type a 1 (Select) nextto the graph formats you want to include. To display a sample of a graph format,type a 5 (Display sample graph) next to the graph format and press the Enter key.A sample graph using the graph format is displayed.

Note: You cannot change the IBM standard graph formats and graph package(QIBMxxxxxx).

Copy Graph Formats and Packages—Manager FeatureTo copy a graph format or graph package, type a 3 (Copy) next to the format orpackage name on the Work with Graph Formats and Packages display and pressthe Enter key.

à ðWork with Graph Formats and Packages



1=Create graph format 2=Change 3=Copy 4=Delete

5=Display sample graph 6=Create package 8=Display package contents

Either the Copy Graph Format (CPYGPHFMT) or Copy Graph Package(CPYGPHPKG) command prompt appears. You can copy a graph format orpackage to another library or into the same library under a different name. A graphformat or package that is created in a library cannot have the same name as agraph format or graph package that already exists in the library.

Copying graph formats and packages is useful for changing a base format orpackage, such as the IBM standard graph formats and package (QIBMxxxxxx).


Delete Graph Formats and Packages—Manager FeatureTo delete graph formats and graph packages, type a 4 (Delete) next to the formatand package names on the Work with Graph Formats and Packages display, andpress the Enter key.

If a graph format you selected to delete is contained in any graph packages, awarning message displays telling you that the format is in a package. If you deletethe graph format, the format is also removed from the graph package. If all thegraph formats in a graph package are deleted, the package is also deleted.

Note: You cannot delete the IBM standard graph formats and graph package(QIBMxxxxxx).

Display Sample GraphTo display a sample of a graph format, type a 5 (Display sample graph) next to thegraph format name on the Work with Graph Formats and Packages display, andpress the Enter key. A sample graph using the graph format is displayed.

Note: This option is not valid for graph packages.

Display Package Contents—Manager FeatureTo display the contents of a graph package, type an 8 (Display package contents)next to the graph package name on the Work with Graph Formats and Packagesdisplay, and press the Enter key. The Display Package Contents display appears.

Note: Option 8 (Display package contents) cannot be specified for graph formats.

à ðDisplay Package Contents




5=Display sample graph

Option Format Text

_ FORMAT1 CPU Utilization vs. Time-Functional Areas



Bottom


á ñ

On this display, type a 5 (Display sample graph) to see a sample graph displayedusing the graph format.


Work with Historical Data—Manager Feature The Display Historical Graph (DSPHSTGPH) command uses historical data toshow the changes in resource utilization on your system over time. Historical datais a summary of the performance data created by the performance monitor.

Notes:

1. Files are created to contain the historical data. For each performance memberwith historical data, there is a single value for each type of information that canbe graphed for each day of the member’s performance collection period. Thus,the amount of data is reduced and summarized into the historical files. Onceyou have historical data for a member, you may choose to delete the perform-ance data (DLTPFRDTA) created through the initial performance data collectionto free file storage space.

| 2. If you want to display a historical graph, select a performance data member| that contains less than 400 intervals.

| 3. Any time a collection extends beyond midnight, each day counts as one| member.

Because historical graphs can help show trends in your system’s performance, it isrecommended that you create historical data in a given library for members that arecollected at the same time. (For example, you might want to compare data that wasall collected on Wednesdays from 8:00 a.m. to 12:00 p.m., whereas you probablywould not want a historical graph with one member collected on Wednesday from8:00 a.m. to 12:00 p.m. and the other on Saturday from 1:00 to 5:00 p.m.)

If you select option 2 (Work with historical data) on the Performance ToolsGraphics menu, the Work with Historical Data display appears.

à ðWork with Historical Data



1=Create historical data 4=Delete historical data

Member Historical

Option Name Data Date Time

_ Q95318ð843 NO 11/14/95 ð8:43:15

_ Q953171ð5ð NO 11/13/95 1ð:51:ðð

_ SATDATA YES 11/11/95 1ð:42:48

_ TESTDATA YES 11/11/95 1ð:26:12

_ NOV111995 NO 11/11/95 ð9:57:27

_ Q95315ð955 NO 11/11/95 ð9:55:41

_ FRIDAY YES 11/1ð/95 11:17:ð3

_ Q953132332 YES 11/ð9/95 23:32:19

_ Q9531214ð7 YES 11/ð8/95 14:ð7:11

_ Q953121142 NO 11/ð8/95 11:42:3ð

_ Q953111538 NO 11/ð7/95 15:39:ð2

More...

F3=Exit F5=Refresh F11=Display text F12=Cancel

F15=Sort by member F16=Sort by text

á ñ

The member name, a historical data indicator, and the date and time you collectedeach set of performance data appear on this display. To display the member text


description, press F11 (Display text). If you cannot find the data you want to workwith, use the appropriate function key to sort the sets of performance and historicaldata. You can sort them by member name, text description, or by the date and timethe member was created. When you find the data you want to work with, indicatethe function you want to perform by typing the appropriate option.

If you are searching for performance or historical data located in a library that isdifferent from the one currently listed in the Library field at the top of the display,type a new library name in the Library field and press the Enter key. A list of per-formance and historical data members available in the library you specifiedappears. You can then select one of them to work with.

Note: All of the members in the historical data must have unique names. If youcreate a member that has the same name as a historical data member, youmay want to change the name by using the Copy Performance Data(CPYPFRDTA) command to use the new member for historical purposes.

It is best to use the created name option (*GEN) on the STRPFRMON command tomake sure that the names of your performance data members are unique.

Create Historical DataTo create historical data for performance members, type a 1 (Create) by themembers, and press the Enter key. The Confirm Create of Historical Data displayappears.

à ðConfirm Create of Historical Data


Press Enter to confirm your choices for 1=Create.

Press F12=Cancel to return to change your choices.

Member Historical

Option Name data Date Time

1 Q95318ð843 NO 11/14/95 ð8:43:15

1 Q953171ð5ð NO 11/13/95 1ð:51:ðð

1 SATDATA YES 11/11/95 1ð:42:48

Bottom

F11=Display text F12=Cancel

á ñ

On this display, press the Enter key to create historical data for the members. Oncehistorical data has been created for a member, you can delete the original perform-ance data using the Delete Performance Data (DLTPFRDTA) command if the datais not needed for performance analysis, capacity planning, or performancegraphing.


Delete Historical DataTo delete the historical data created by the Create Historical Data command, type a4 (Delete) by members that contain historical data, and press the Enter key. Thisdoes not delete the original performance data.

Note: If the performance data for a member no longer exists, you cannot re-createhistorical data for that member after the historical data has been deleted.

Display Graphs and Packages—Manager FeatureYou can view, print, or plot graphs from your display. You can also store a graph ina GDF file for use by other utilities, such as the BGU. This is done on the SpecifyGraph Options display.

If you select option 3 (Display Graphs and Packages) on the Performance ToolsGraphics menu, the Display Graphs and Packages display appears.

à ðDisplay Graphs and Packages


1. Display performance data graphs

2. Display historical data graphs


===> __________________________________________________________________

_______________________________________________________________________

F3=Exit F4=Prompt F9=Retrieve F12=Cancel

á ñ

Two distinct types of graphs can be displayed: performance graphs and historicalgraphs. Performance graphs use performance data collected from a single run ofthe performance monitor. Performance graphs are used to single out jobs that areperforming poorly or to evaluate which activities were performed by a user or classof users on the system during a specified period.

Historical graphs use performance data collected from several runs of the perform-ance monitor. Historical data is the summary of the performance data created bythe STRPFRMON command. The CRTHSTDTA command is used to summarizethe performance data for use by the historical graphs. Historical graphs are used toshow how the performance of a system has changed over time.

Note: It is best to collect the performance data used for historical graphs over thesame period of time. For example, if your normal working day is from 8:00a.m. to 5:00 p.m., you would not want to create a historical graph to eval-


uate system performance during working hours using system performancedata collected from 5:00 p.m. to 8:00 a.m.

If you want to collect data at predetermined times, use the Work with PerformanceCollection (WRKPFRCOL) command to schedule the running of the performancemonitor. See Chapter 3, Collecting System Performance Data, for more informationon this command.

Display Performance Graphs—Manager FeatureIf you select option 1 (Display performance data graphs) on the Display Graphs andPackages display, the Select Graph Formats and Packages display appears.

à ðSelect Graph Formats and Packages



1=Select 5=Display sample graph 8=Display package contents

Format/

Option Package Type Text

_ NEWPACKAGE PACKAGE Graph Package for Job Types

_ PACKAGE1 PACKAGE Graph Package containing IOP formats

_ QIBMPKG PACKAGE IBM Graph Package

_ FORMAT1 FORMAT CPU Utilization vs. Time-Functional Areas

_ FORMAT2 FORMAT Response Time vs. Time-Functional Areas

_ QIBMASYNC FORMAT Asynchronous Disk I/O per Second vs. Time

_ QIBMCMNIOP FORMAT Communications IOP Utilization vs. Time

_ QIBMCPUPTY FORMAT CPU Utilization vs. Time (Priority)

_ QIBMCPUTYP FORMAT CPU Utilization vs. Time (Job Type)

_ QIBMDSKARM FORMAT Disk Arm Utilization vs. Time

More...

F3=Exit F5=Refresh F12=Cancel F14=Sort by format F15=Sort by text

á ñ

This display shows you the graph formats and graph packages that exist in thelibrary you specified. The graph format or graph package name, a format orpackage indicator, and a text description appear on the display. If you cannot findthe format or package you want to use in your performance graph, use the appro-priate function key to sort the formats and packages. You can sort them by name,type, or text description. When you find the graph format or package you want touse in your performance graph, type a 1 in the corresponding Option field.

If you are searching for a graph format or graph package located in a library that isdifferent from the one currently listed in the Library field at the top of the display,type a new library name in the Library field, and press the Enter key. A list of graphformats and graph packages available in the library you specified appears. You canthen select one of them to use in your performance graph.

| Note: If you want to display a historical graph, select a performance data member| that contains less than 400 intervals.


Display Sample Graph—Manager FeatureTo display a sample of a graph format, type a 5 (Display sample graph) next to thegraph format, and press the Enter key. A sample graph using the graph formatappears.

Note: This option is not valid for graph packages.

Display Graph Package—Manager FeatureTo display the contents of a graph package, type an 8 (Display package contents)next to the graph package, and press the Enter key. A list of the graph formatscontained in the graph package appears.

Note: This option is not valid for graph formats.

Select Performance Data Member—Manager FeatureAfter you select a graph format or graph package to use in your performancegraph, the Select Performance Data Member display appears.

à ðSelect Performance Data Member



1=Select

Member

Option Name Text Date Time

_ Q95318ð843 11/14/95 ð8:43:15

_ Q953171ð5ð 11/13/95 1ð:51:ðð

_ SATDATA3 Saturday Data-third run 11/11/95 1ð:42:48

_ SATDATA2 Saturday Data-second run 11/11/95 1ð:26:12

_ SATDATA1 Saturday Data-first run 11/11/95 ð9:57:27

_ Q95315ð955 11/11/95 ð9:55:41

More...

F3=Exit F5=Refresh F12=Cancel F15=Sort by member

F16=Sort by text

á ñ

The member name, a text description, and the date and time you collected eachset of performance data appear on this display. If you cannot find the data youwant to display, use the appropriate function keys to sort the sets of performancedata. You can sort the data by member name, text description, or by the date andtime the member was created. When you find the performance data you want touse in your performance graph, type a 1 in the corresponding Option field.

If you are searching for a member located in a library that is different from the onecurrently listed in the Library field at the top of the display, type a new library namein the Library field and press the Enter key. A list of the performance membersavailable in the specified library appears. You can then select a member to display.


Select Categories for Performance Graphs—Manager FeatureIf the graph format or graph package you previously selected does not graph onlyIOP, disk, or communications line data, the Select Categories for PerformanceGraphs display appears.

à ðSelect Categories for Performance Graphs

Member . . . . . : MONDAYDATA


Type options, press Enter. Press F6 to include all data in the graph.

1=Select

Option Category

_ Job

_ User ID

_ Subsystem

_ Pool


_ Control unit

_ Functional area

Bottom

F3=Exit F6=Include all data in the graph F12=Cancel

á ñ

Type a 1 in the Option column next to the categories of information from which youwant performance data. Press the Enter key.

Note: Normally, you include all categories of information in your graph. To do this,do not type a 1 in any category. Instead, simply press F6.

If you choose to display the graph with only certain categories of information, adisplay appears that allows you to enter selection criteria for each category. This isthe same as selecting categories of information to include in performance reports.See Chapter 7, Performance Reports—Manager Feature, for more information onselecting and omitting.

Specify Graph Options—Manager FeatureWhen you have chosen the information you want to appear on your performancegraph, or if you selected a graph format with IOP, disk, or communications line datatype, the Specify Graph Options display appears.


à ðSpecify Graph Options


Graph title . . . \MBRTEXT

Graph subtitle . . CPU Utilization vs. Time

X-axis range:

First . . . . . \AUTO___ \SAME, \AUTO, Number

Last . . . . . . ________ Number

Y-axis range:


Last . . . . . . ________ Number

Area fill . . . . \NO \SAME, \YES, \NO

Start:

Day . . . . . . \FIRST \FIRST, MM/DD/YY

Time . . . . . . \FIRST \FIRST, HH:MM:SS

More...

F3=Exit F12=Cancel

á ñ

Figure 9-6. Specify Graph Options

Page down to view the rest of the graph options.



Stop:

Day . . . . . . \LAST \LAST, MM/DD/YY

Time . . . . . . \LAST \LAST, HH:MM:SS

Output . . . . . . \_______ \, \PRINT, \PLOT, \OUTFILE

Bottom

F3=Exit F12=Cancel

á ñ

On this display you can specify a new title, subtitle, axis ranges, area fill value, starttime and date, stop time and date, and output value for your performance graph. Ifyou selected a graph format for your performance graph, the values for the title,subtitle, axis ranges, and area fill defined in the graph format appear. Changing anyof the values on the Specify Graph Options display only changes the format for thegraph created. The graph format does not change. If you selected a graph packagefor your performance graph, *SAME appears for the title, subtitle, and axis ranges.


*SAME means to leave these values as they are defined in the individual graphformats in the package. If you specify any new values, the new values appear onall of the graphs in the package.

For example, if you type New Graph Title for the graph title and the graph packagecontained three graph formats, the resulting three graphs would have “New GraphTitle” as their title.

The area fill option allows you to override the area fill option on the graph format todisplay a graph more quickly. Filling in (or shading) an area is accomplished bydrawing several lines. Densely shaded patterns require more lines. Each line that isdrawn takes time. Consequently, the graph displays faster if area fill is not used. Ifthe area fill option on the graph format is *YES, then selecting *NO for the area filloption causes the area not to be filled.

You may specify the start and stop date and time for the performance data to beshown in the graph. If you do not specify the start and stop date and time, thegraph includes data from the first (or only) date that data was collected to the last(or only) date that data was collected.

The output option specifies how the graphs are to be displayed.

Press the Enter key to display your graph or graphs.

Display Historical Graphs—Manager FeatureHistorical graphs allow you to graphically see how your system performed duringmany runs of the performance monitor. This shows you how the performance ofyour system has changed over time. For example, it can show how processing unitutilization increased or fluctuated.

If you select option 2 (Display historical data graphs) on the Display Graphs andPackages display, the Select Graph Formats and Packages display appears. Thisis the same display that is shown for displaying performance graphs. (See “DisplayPerformance Graphs—Manager Feature” on page 9-16 for more information.) Afteryou select a graph format or graph package from the Select Graph Formats andPackages display, the Specify Graph Options display appears.




Graph title . . . \BLANK___________________________________________

Graph subtitle . . \BLANK___________________________________________

X-axis range:


Last . . . . . . ________ Number

Y-axis range:


Last . . . . . . ________ Number

Area fill . . . . \NO \SAME, \YES, \NO

Data library . . . QPFRDATA__ Name

More...

F3=Exit F12=Cancel

á ñ

Page down to view the rest of the graph options.



Start:

Day . . . . . . . . \FIRST__ \FIRST, \SELECT, MM/DD/YY

Stop:

Day . . . . . . . . \LAST___ \LAST, MM/DD/YY

Create historical

data . . . . . . . . . \NO_ \YES, \NO

Output . . . . . . . . \_______ \, \PRINT, \PLOT, \OUTFILE

Bottom

F3=Exit F12=Cancel

á ñ

Display Graph Overlay—Manager FeatureOnce you have a performance graph or historical graph displayed, you can defineone overlay by pressing F9 (Overlay). An overlay is a graph that is placed on top ofanother graph so that you can see both graphs at the same time. Overlays canhelp you compare one graph to another as shown below.

You must select a graph format with the same X-axis specified.


If you want to overlay a historical graph, you cannot display a graph format withfunctional area data type.

Note that when you overlay a graph, there is a maximum of 16 legend entriesbetween the two graphs. Therefore, if you are currently displaying a graph with twolegend entries, your overlaid graph may have only a maximum of 14 legend entries(if allowed for the data type in the graph format). See “Legends—Manager Feature”on page 9-9 for the maximum number of legend entries for the individual datatypes. If you are currently displaying a graph with 16 legend entries, you cannotoverlay a second graph.

Press F9 (Overlay), and the Select Graph Format display appears. Select the graphformat that you want to overlay above the graph that is currently displayed.

à ðSelect Graph Format



1=Select

Option Format Text









_ QIBMMFCIOP Multifunction IOP (Comm) Util vs. Time

_ QIBMMFDIOP Multifunction IOP (Disk) Util vs. Time

_ QIBMRSP Interactive Response Time vs. Time

More...


á ñ

Select a graph format and press the Enter key, and the Specify Graph OverlayOptions display appears.


à ðSpecify Graph Overlay Options


New graph title \BLANK________________________________________

New graph subtitle \BLANK________________________________________

Y-axis range:

First . . . . . \AUTO_____ \SAME, \AUTO, Number

Last . . . . . . __________ Number

Area fill . . . . \NO_ \YES, \NO

F3=Exit F12=Cancel

á ñ

Specify a title and subtitle for your new, overlaid graph on this display. If you donot specify a new title and subtitle, your new graph title and subtitle are left blank.

The Y-axis range value defaults to the value that was specified in the graph format.Here, again, you have the chance to change it. You may choose to have the samerange as defined in the graph format (*SAME), you may choose to have it automat-ically fit the range of values (*AUTO), or you may specify the range yourself bytyping in the numbers.

You also select whether to have area fill in the overlaid graph.

After you press the Enter key, your two graphs should be displayed. You can usethe function keys on the display to print or plot the overlay or send the overlayformat to a GDF file. Figure 9-7 shows an example of an overlay graph.

Press Enter to continue.F3=Exit F6=Print F9=OverlayF12=Cancel F16=Save GDF F17=Plot

3200280024002000160012008004000

9080706050403020100

08:00 10:00 14:00 16:00 18:00

RV2S077-0

CPUUtilization

Transactionsper Hour

Monday’s Performance Data CPUUtilization and Trans perHour vs. Time

12:00Time

BatchInteractSystem

Figure 9-7. Overlay Graph Example



Chapter 10. Performance Utilities—Manager Feature

This chapter describes the commands that you access with option 5 (Performanceutilities) on the IBM Performance Tools menu. When you choose option 5, the Per-formance Utilities display appears.

à ð Performance Utilities


1. Work with job traces

2. Work with Performance Explorer

3. Select file and access group utilities

The utilities shown on the Performance Utilities display provide you with support forthe detailed performance analysis of applications when you are working to under-stand or improve the performance of those applications.

See “Summary of Data Collection and Report Commands—Manager Feature” onpage 3-13 for an overview of the commands you use with Performance Tools, theirdata collection requirements, and their intended uses. For a description of the per-formance explorer function (option 2) see Chapter 11, Performance Explorer.

Job TracesIf you select option 1 (Work with job traces) on the Performance Utilities display,the Work with Job Traces display appears.

à ðWork with Job Traces


1. Start job trace

2. Stop job trace

3. Print job trace reports

On this display you can choose to start or stop a job trace. After you collect thetrace data, you can print job trace reports that show information about input/output(I/O) operations, file use, transaction timing, job flow, and so on.

The options in the Job Trace display and the corresponding commands are asfollows:

Job Traces Corresponding Command

Start Job Trace STRJOBTRC

Stop Job Trace ENDJOBTRC

Print Job Trace Reports PRTJOBTRC


For more information on job traces, see “Analyzing Job Flow and TransactionPerformance” on page 10-2.

File and Process Access Group (PAG) UtilitiesIf you choose option 3 (Select file and access group utilities) on the PerformanceUtilities menu, the Select File and Access Group Utilities display appears.

à ðSelect File and Access Group Utilities


1. Analyze program/file use

2. Analyze physical/logical file relationships

3. Analyze file key structure

4. Collect/display access group data

5. Analyze access group data

On this display you can choose to create reports that show the program-to-file use,the physical-to-logical file relationships, the file key structure, or access group data.You can also use this display to determine if the application programs use shareddisplay and database files, if the files are ordered by their frequency of use, if thefiles remain open but have no activity, or if programs free their static storage orkeep it active.

Notes:

1. Before you use option 3, be sure that the processing for option 2 has com-pleted. The output from option 2 is used as input for this function.

2. Option 5 is dependent on data collected by option 4. So you must take option 4first.

The options in the Select File and Access Group Utilities display and the corre-sponding commands are as follows:

For more information on file and PAG utilities, see “Analyzing the Relationship ofPrograms and Database Files” on page 10-9 and “Analyzing Process Information”on page 10-16.

File and Access Group Utilities CorrespondingCommand

Analyze Program/File Use ANZPGMAnalyze Physical/Logical File Relationships ANZDBFAnalyze File Key Structure ANZDBFKEYCollect/Display Access Group Data DSPACCGRPAnalyze Access Group Data ANZACCGRP

Analyzing Job Flow and Transaction PerformanceUse the job trace commands to collect trace information about a job. You can dothis while the job runs in the normal production environment, or you can set up aspecial test for a job or program and trace how it runs. Once you collect the traceinformation, print the reports (there are two summary reports and one detail report).The summary reports allow you to determine the overall performance of the job


without analyzing the detail report. Use the summary reports to guide you throughthe detail report.

Do not produce the detailed job analysis until you define which program or job youwant to analyze.

Job trace analysis enhances the operating system’s standard trace job reports andprovides a summary of job operation and transaction processing. The primary usefor job trace analysis is to determine how a job processes. You can determinewhat parts of a job use the most resources, and measure the effect of programchanges relative to previous trace data. Do not use job trace analysis to determineaccurate job or transaction processing times.

Start Job Trace (STRJOBTRC) CommandUse the STRJOBTRC command to start the job trace function. The End Job Trace(ENDJOBTRC) and Print Job Trace (PRTJOBTRC) commands provide summaryand detail reports of the job trace data.

Consider the following points when you use STRJOBTRC:

� The job trace function usually changes the paging characteristics of a job.Therefore, the trace reports may not show representative times for programoperation.

� To cancel the job trace without saving any of the collected data, use theTRCJOB SET(*END) command.

� The job trace function issues a Start Service Job (STRSRVJOB) command if ajob other than the current job is specified on the STRJOBTRC command.

End Job Trace (ENDJOBTRC) CommandUse the ENDJOBTRC command to do the following:

� Stop the job trace and direct the trace data into a user-defined database filemember.

� You may start the PRTJOBTRC command to print the reports that analyze thetrace data. These analysis reports provide an estimate of the response andprocessing times. They also show the number of database reads, nondatabasereads, and write I/O operations.

The database file QAPTTRCJ is created as output when you use the ENDJOBTRCcommand. Table 10-1 shows the names and descriptions of the fields in theQAPTTRCJ file.

Table 10-1 (Page 1 of 2). QAPTTRCJ File


SCFUNC Type of function

SCSTYP Subtype of function

SCFLD1 Column heading 1



SCTIME Time of trace record

Chapter 10. Performance Utilities—Manager Feature 10-3

The printer file created by this command is the same as that created by thePRTJOBTRC command, as described in Print Job Trace (PRTJOBTRC) Command.

Table 10-1 (Page 2 of 2). QAPTTRCJ File


SCSEQ Record sequence number

SCENT Entry machine interface (MI) instruction number

SCEXT Exit machine interface (MI) instruction number

SCINV Call level

SCCPU CPU time used

SCDB Database reads

SCPAG Nondatabase reads

SCWAIT Number of waits

SCRCEN Century. 0 indicates the twentieth century. 1 indicates the twenty-first century.

SCRDAT Date

SCRTIM Time

SCSYNM System name

Print Job Trace (PRTJOBTRC) CommandUse the PRTJOBTRC command to print a report of all, or a selected part, of the jobtrace data. The job trace data that prints comes from the database file member thatwas created when you ran the ENDJOBTRC command.

Note: There may be gaps in the sequence numbers on the report. These arecaused by undefined trace records that may contain unprintable characters.To view these records, use the TRCJOB report, which gives you ahexadecimal display of these fields.

The following printer files are the output when you use the PTRJOBTRC command:

File Description

QPPTTRC1 First part of the summary report (Trace Analysis Summary)

QPPTTRC2 Second part of the summary report (Trace Analysis I/O Summary)

QPPTTRCD Trace record detail report (Trace Job Information)

Both the Trace Analysis Summary Report and the Trace Analysis I/O SummaryReport show the job trace data detail by transaction. On these reports, two lines foreach transaction show all the trace records for that transaction. A transactionboundary is determined by consecutive trace records with these characteristics:

� The first trace record indicates a call to the program specified by the end oftransaction (ENDTNS) parameter.

� The second trace record indicates a return to the program specified by the startof transaction (STRTNS) parameter.

The default ENDTNS and STRTNS parameters cause the trace records to beshown by work station transactions on these reports. A transaction begins when auser presses the Enter key, or otherwise responds to a program prompt, and ends


when the program next requests input from the work station. You can change theseparameters in order to summarize other types of transactions, such as record proc-essing (useful when tracing a batch job), or communications I/O.

The summary reports show you the number and types of I/O operations thatoccurred for each transaction, the number of full and shared file opens and closes,the number of subfile operations, and the number of messages that occurred in thetransaction. Messages may be the result of normal operation or they may be due toprogram actions that you can avoid (full open/close, duplicate keys in a file, orincorrect subfile processing).

The summary reports also contain a reference to the detail report. Every detailrecord has a sequence number in it. The summaries show the starting and endingdetail report sequence numbers for each transaction summarized. The detail reportprogram can be limited to a range of sequence numbers. This feature allows you torun the summaries, then print only the detail you are interested in.

The collection of trace data takes a certain amount of processing time, the amountof which can vary depending on such factors as system load and model. Thisoverhead time is included in the trace data on which the PRTJOBTRC commandreports. The command attempts to subtract the overhead time from the reportedfigures, leaving only the time used for program processing. Due to the variability ofthe overhead time, this adjustment may not be accurate. This adjustment is anestimate only. Therefore, do not use reported processing times as an absolutemeasure of the response time of a program or set of programs.

Figure 10-1 on page 10-6 shows an example of the Trace Analysis SummaryReport.

The header of the Trace Analysis Summary Report shows the following values:

Title The title specified on the command.

FILE The name of the database file containing the trace data.

LIBRARY The library the database file is in.

MBR The database file member containing the trace data.

JOB The name of the job that was traced.

The columns in the detailed section of the Trace Analysis Summary Report are asfollows:

ACTIVE or WAIT-ACT The time between the ENDTNS and STRTNS programs islabeled Wait-Act. If you were tracing an interactive job and used thedefault STRTNS and ENDTNS parameters, this value is the time takento process the transaction.

SECONDS The approximate time the job was waiting or active.

CPU SECONDS The approximate processing unit time used for the transaction. Ifthe value is zero (or blank), you may have chosen the wrong value forthe model parameter.

DB READS The number of physical database reads that occurred.

NON-DB RDS The number of physical nondatabase reads that occurred.

WRITES The number of physical writes that occurred.


Title TRACE ANALYSIS SUMMARY 12/ð1/95

FILE-QAJOBTRC LIBRARY-QPFRDATA MBR-QAJOBTRC JOB- BYSINN .VLLXR239 .ðð3368

P H Y S I C A L I / O

SECONDS CPU SECONDS DB READS NON-DB RDS WRITES WAITS SEQUENCE

WAIT-ACT 4.852 .ðð9 16

ACTIVE 1.425 .788 33 5 1 1ð8

WAIT-ACT 4.ð93 .ð17 3 112

ACTIVE .247 .11ð 7 5 1 119

WAIT-ACT 3.736 .ðð9 123

ACTIVE .658 .572 8 5 1 18ð

WAIT-ACT 1.793 .ðð5 184

ACTIVE .512 .193 19 3 2 2ð6

WAIT-ACT 4.195 .ðð9 21ð

AVERAGE .711 .426 18 5 1 4

TOTAL 2.842 1.7ð3 7ð 18 5

Figure 10-1. Trace Analysis Summary Report

WAITS The number of waits that occurred.

SEQUENCE The job trace sequence number in the detail report that this summaryline refers to.

AVERAGE and TOTAL Averages and totals for the fields described above. Theentry on the Average line in the Sequence column shows the number ofSTRTNS and ENDTNS pairs encountered. For an interactive job, this isthe number of transactions entered while the trace was on if the defaultSTRTNS and ENDTNS values were used.

Figure 10-2 on page 10-7 shows an example of the Trace Analysis I/O SummaryReport.

The columns in the Trace Analysis I/O Summary Report are as follows:

Title The title specified on the command.

FILE The name of the database file containing the trace data.

LIBRARY The library the database file is in.

MBR The database file member containing the trace data.

JOB The name of the job that was traced.

WAIT-ACT The time that the job was inactive, probably due to typing or think timeby the user.

ACTIVE The time the job was processing.

SECONDS The time the job was waiting or active.

SEQNCE The job trace sequence number in the detail computer printout that thissummary line refers to.

PROGRAM NAME The name of the last program called that was not in the libraryQSYS before the end of a transaction.

PROGRAM CALL The number of non-QSYS library programs called during thestep. This is not the number of times that the program named in thePROGRAM NAME field was called.

PROGRAM INIT The number of times that the IBM-supplied initialization programwas called during the transaction. For RPG programs this is QRGXINIT,for COBOL it is QCRMAIN. Each time the user program ends with LR(RPG) or END (COBOL), the IBM-supplied program is also called. Thisis not the number of times the program named in the Program Name


Title TRACE ANALYSIS I/O SUMMARY 12/ð1/95


P R O G R A M \\\\\\\ PROGRAM DATA BASE I/O \\\\\\\ FULL SHARE SUBFILE

SECONDS SEQNCE NAME CALL INIT GETDR GETSQ GETKY GETM PUT PUTM UDR OPN CLS OPN CLS READS WRITES MSGS

WAIT-ACT 4.852 16

ACTIVE 1.425 1ð8 QPTPAGDð 1 1 11

WAIT-ACT 4.ð93 112

ACTIVE .247 119

WAIT-ACT 3.736 123

ACTIVE .658 18ð 11

WAIT-ACT 1.793 184

ACTIVE .512 2ð6 1

WAIT-ACT 4.195 21ð

AVERAGE .711 4 6

TOTAL 2.842 1 1 1 22

Figure 10-2. Trace Analysis I/O Summary Report

field was initialized. QCRMAIN is used for functions other than programinitialization (for example, blocked record I/O, some data conversions).

PROGRAM DATABASE I/O The number of times the IBM-supplied databasemodules were used during the transaction. The database module nameshave had the QDB prefix removed (PUT instead of QDBPUT). The typeof logical I/O operation performed by each is as follows:

GETDR Get direct

GETSQ Get sequential

GETKY Get by key

GETM Get multiple

PUT, PUTM Add a record

UDR Update, delete, or release a record

The values for OPENS and CLOSES in the programs are as follows:

FULL OPN The number of full opens for all types of files.

FULL CLS The number of full closes for all types of files.

SHARE OPN The number of shared opens for all types of files.

SHARE CLS The number of shared closes for all types of files.

The valid values for Subfile I/O are as follows:

SUBFILE READS The number of subfile reads.

SUBFILE WRITES The number of subfile writes.

MSGS The number of messages sent to the job during each transaction.

The Trace Job Information Report, shown in Figure 10-3 on page 10-8, has essen-tially the same format as the system-supplied trace job output. The AS/400Licensed Internal Code Diagnostic Aids - Volume 1 book contains additional infor-mation on trace jobs.

The columns in the Trace Job Information Report are as follows:

TIME The time of day for the trace entry. The time is sequentially given inhours, minutes, seconds, and fractions of a second.

SEQNBR The number of the trace entry.


Sample Job Trace Report TRACE JOB INFORMATION PAGE 1


TIME SEQNBR FUNCTION PROGRAM LIBRARY ENTRY EXIT INV CPU DB NON-DB WRITTEN WAITS

15 ð4 26 225

. ððððð1 RETURN QPTTRCJ1 QPFR ðð77 ððCF ð3 .ð12 1

15 ð4 26 262

. ððððð2 CALL QCLRTNE QSYS ððð1 ðð2D ð4 1

15 ð4 26 296

. ððððð3 XCTL QCLCLNUP QSYS ððð1 ðð48 ð4 .ð12

15 ð4 26 3ð7

. ððððð4 RETURN QPTTRCJ1 QPFR ððDð ððDð ð3 .ðð8

15 ð4 26 316

. ððððð5 RETURN QCMD QSYS ð16C ð153 ð2 .ð12

15 ð4 26 33ð

. ððððð6 CALL QMHRCMSS QSYS ððð1 ð37E ð3 .ð12 1

15 ð4 26 363

. ððððð7 CALL QMHGSD QSYS ððð1 ððF5 ð4 .ð12

15 ð4 26 372

. ððððð8 CALL QMHRTMSS QSYS ððð1 ð136 ð5 .ðð8

15 ð4 26 383

. ððððð9 RETURN QMHGSD QSYS ððF6 ð397 ð4 .ð16

15 ð4 26 397

. ðððð1ð CALL QWSPUT QSYS ððð1 ð8A6 ð5 .ð28

15 ð4 26 429

. ðððð11 XCTL QWSGET QSYS ððð1 ð27E ð5 .ð12

15 ð4 26 44ð

. ðððð12 CALL QT3REQIO QSYS ððð1 ðð55 ð6 .ð61 5 3 1

15 ð4 26.445 ðððð13 T3-ENTRY

15 ð4 26.447 ðððð14 T3REQIO-REQIO

15 ð4 31.285 ðððð15 T3DEQ-DEQ

Figure 10-3. Trace Job Information Report

FUNCTION This causes the trace entry to be recorded. The possible trace entriesare as follows:

Trace Entry Description

Call Call external.

Data A data trace.

Event Event handler.

EXTXHINV External exception handler.

EXTXHRET Call termination because of a return from an exception.

INTXHINV Internal exception handler.

INTXHRET Return from an exception.

INVEXIT Call because of a call exit routine.

ITERM Intervening call termination.

ITRMXRSG Call termination because of a resignaling exception.

PTRMTPP Process termination.

PTRMUNHX Termination because of an unhandled exception.

Return Return external.

RSMTRC Trace resumed.

SSPTRC Trace suspended.

XCTL Transfer control.

PROGRAM The name of the program for the entry.

LIBRARY The library name that contains the program associated with the traceentry.


ENTRY The instruction in the program where the program was given control.This is true when a program is nonobservant and observant.

EXIT The instruction number in the program where the program gave upcontrol.

INV The call level of the program.

CPU The approximation of the CPU used on this trace entry. This is a calcu-lated value based on the time used and the CPU model being run.

DB The number of physical database reads that occurred for the entry.

NON-DB The number of physical nondatabase reads that occurred for the entry.

WRITTEN The number of physical writes that occurred for the entry.

WAITS The number of waits that occurred for the entry.

The read and write counts do not include any asynchronous I/O operations. Thecounts indicate the number of I/O requests (either single or multiple page) sent tothe device, and describe the request queuing at the device.

Analyzing the Relationship of Programs and Database FilesUse the Analyze Program (ANZPGM) command and the Analyze Database File(ANZDBF) command to print an overview of the programs and files used in anapplication. The commands provide reports showing program-to-file use and phys-ical and logical file relationships in the libraries.

Use the Analyze Database File Keys (ANZDBFKEY) command to print an overviewof the key structure of logical files in an application.

These commands provide you with a file and program use overview and key defi-nition detail. It may be that your files or programs have changed since they werefirst written and the file use has changed. For example, there may now be morelogical files over your physical files than the application currently needs. This situ-ation can cause performance degradation, especially if many key field changes orrecord adds occur. Remove any unneeded logical views.

Although you may use these commands infrequently, it is recommended that youuse them periodically to get a good understanding of the program-to-file relation-ships and of the logical file structure used in the applications.

Analyze Program (ANZPGM) CommandUse the ANZPGM command to produce reports showing program-to-file and file-to-program relationships.

When you use the ANZPGM command, the following printer files are created asoutput:

File Description

QPPTANZP The program-to-file relationship report (Program-to-File Cross-Reference)

QPPTANZP The file-to-program relationship report (File-to-Program Cross-Reference)


Figure 10-4 on page 10-10 shows an example of the Program-to-File Cross-Reference Report.

12/ð1/95 13:37:ð9 Program to File Cross-Reference Page 1

File Usage

Record 1=In 2=Out

Library Program Program Text Description Object Library Format 4=Upd 8=?

---------- ---------- -------------------------------------------------- ----------- ----------- ---------- ----------

QPFR OLDPTCHGJR QAPMDMPT \LIBL 1

QDPTJTYP QPFR SFL 3

QDPTJTYP QPFR SFLCTL 3

QDPTJTYP QPFR QDPTF1 3



QDPTJTYP QPFR HELP1 3

QTRIDX QPFRDATA IDXREC 6

QJTYP1 QPFRTEMP IDXREC 1

QJTYP2 QPFRTEMP IDXREC 6

OLDPTTNSRP \FILE 8

QAPMJOBS 8

QSYSPRT 8

QTRIDX 8

QTRINTD 8

QTRINTU 8

QTRJOBI 8

QTRJOBO 8

QAPMDMPT &LIB 8

QAPMJOBS &LIB 8

QTRIDX &LIB 8

QTRJSUM &LIB 8

QTRTSUM &LIB 8

QDDSSRC \LIBL 1

QPTMPLST \LIBL

QPTTRIDX \LIBL

QDDSSRC QPFR 1

&TRCJOBS QTEMP 8

Figure 10-4. ANZPGM Program-to-File Cross-Reference Report

The ANZPGM Program-to-File Cross-Reference Report shows the followingcolumns:

Library and Program The name of the program that uses the file shown.

Program Text Description The program’s text description, if it was provided atprogram creation.

Object and Library The name of the object that the program refers to, and thename of the library the object is in.

Record Format The name of the formats in the file used by the program in the filebeing referred to.

File Usage The manner in which the file is used by the program (1—input,2—output, 4—update, 8—unknown, or any of the OR’d combinations ofthese, such as 3—input-output, 6—output-update). For more informa-tion and other values for the Display Database Relations (DSPDBR)command and the Display Program References (DSPPGMREF)command, see the CL Reference .

Figure 10-5 on page 10-11 shows an example of the ANZPGM File-to-ProgramCross-Reference Report.


12/ð1/95 13:37:15 File to Program Cross Reference Page 1

File Usage

Record 1=In 2=Out

Library Object Format Library Program Program Text Description 4=Upd 8=?

----------- ----------- ---------- ---------- ---------- -------------------------------------------------- ----------

QMNADDTO

QMNGOMNU

QMNMAIN

QPTBATCH

QPTCPTRP

QPTCPTSL

QPTCPTWK

QPTLCKQ

QPTPGMX2

QPTSLECT

QPTSYSRP

QPTSYSSL

QPTSYSWK

QPTTRCJ1 STRJOBTRC CPP 2

QPTTRIDX

QPTTST1

QPTSYSRP

\FILE QPFR OLDPTTNSRP 8

\FILE QPTTNSRB 8

\FILE QPTTNSRP 8

\FILE QPFRTEMP 8

\NONE QPFR QPTTRCJð ENDJOBTRC CPP

\NONE QPTTRCJ1 STRJOBTRC CPP

QAJOBTRC QPTTRCRP ENDJOBTRC CPP 8

QAPMDMPT QPTCHGJT 8

Figure 10-5. ANZPGM File-to-Program Cross-Reference Report

The ANZPGM File-to-Program Cross-Reference Report shows the followingcolumns:

Library and Object The name and library the file is in.

Record Format The names of the record formats in the file.

Library and Program The names and library of the programs that use the file.

Program Text Description The program text description.

File Usage The manner in which the file is used (1—input, 2—output, 4—update,8—unknown, and OR’d combinations of these values).

Analyze Database File (ANZDBF) CommandUse the ANZDBF command to print reports detailing physical and logical filerelationships.

When you use the ANZDBF command, the following files are created as output:

File Description

QPPTANZD The printer file that has the physical-to-logical database file relation-ships report (Database Relation Cross-Reference).

QPPTANZD The printer file that has the logical-to-physical database file relation-ships report (Logical File Listing).

QAPTAZDR The database file that serves as input to the ANZDBFKEY command.

Figure 10-6 on page 10-12 shows an example of the ANZDBF Database RelationCross-Reference Report.


| 12/ð1/95 14:29:31 Database Relation Cross Reference Page 1

| Type Depncy

| P=Phy Depnd Dependent Dependent Type

| L=Lgl File Library Count File Library D/A

| ----- ---------- ---------- ----- ---------- ---------- ------

| L QANSCRAL QSMU

| QANSCRA1

| QANSCRA2

| QANSCRA3

| QANSCRCL

| QANSCRL

| QANSCRML

| QANSCRM1

| QANSCRM2

| QANSCRM3

| QANSCRNL

| QANSCRN1

| QANSCR1

| QASVNUP

| P QANSCRAC 4 QANSCRAL QSMU D

| 4 QANSCRA1 QSMU D

| 4 QANSCRA2 QSMU D

| 4 QANSCRA3 QSMU D

| QANSCRAN 2 QANSCRNL QSMU D

| 2 QANSCRN1 QSMU D

| QANSCRCN 2 QANSCRCL QSMU D

| 2 QANSCRC1 QSMU D

| QANSCRCR 2 QANSCRL QSMU D

| 2 QANSCR1 QSMU D

| QANSCRMS 4 QANSCRML QSMU D

| 4 QANSCRM1 QSMU D

| 4 QANSCRM2 QSMU D

| 4 QANSCRM3 QSMU D

| QANSSRC

| QANSSRI

| QASVNUPP 1 QASVNUP QSMU D

| 32 records processed

Figure 10-6. ANZDBF Database Relation Cross-Reference Report

The ANZDBF Database Relation Cross-Reference Report has the followingcolumns:

Type The file type (P-Physical, L-Logical).

File The name of the file.

Library The library containing the file.

Depnd Count The number of logical files dependent on this file.

Dependent File The names of each dependent logical file.

Dependent Library The library the dependent logical files are in.

Depncy Type D/A D—Data share dependency. A—Access share dependency.

The entries in the Type, File, and Library columns are left blank if they are thesame as the previous line.

Figure 10-7 on page 10-13 shows an example of the ANZDBF Logical File Report.


| 12/ð1/95 14:29:34 Logical File Listing Page 1

| Depncy Type

| Dependent Dependent Type P=Phy

| File Library D/A File Library L=Lgl

| ---------- ---------- ------ ---------- ---------- -----

| QANSCRAL QSMU D QANSCRAC QSMU P

| QANSCRA1 QSMU D

| QANSCRA2 QSMU D

| QANSCRA3 QSMU D

| QANSCRNL QSMU D QANSCRAN QSMU P

| QANSCRN1 QSMU D

| QANSCRCL QSMU D QANSCRCN QSMU P

| QANSCRC1 QSMU D

| QANSCRL QSMU D QANSCRCR QSMU P

| QANSCR1 QSMU D

| QANSCRML QSMU D QANSCRMS QSMU P

| QANSCRM1 QSMU D

| QANSCRM2 QSMU D

| QANSCRM3 QSMU D

| QASVNUP QSMU D QASVNUPP QSMU P

| 15 records processed

Figure 10-7. ANZDBF Logical File Report

The ANZDBF Logical File Report shows the following:

Dependent File The names of each dependent logical file.

Dependent Library The library the dependent logical files are in.

Depncy Type D/A D—Data share dependency. A—Access share dependency.

File The name of the physical file.

Library The library containing the physical file.

Type The physical file type.

Analyze Database File Keys (ANZDBFKEY) CommandUse the ANZDBFKEY command to print a report showing the key structure oflogical files.

When you use the ANZDBFKEY command, the following input file is used:

File Description

QAPTAZDR Database file that is the output from the ANZDBF command.

Note: Because the ANZDBFKEY command uses the output from the ANZDBFcommand as its input, be sure the ANZDBF command is finished beforeyou use the ANZDBFKEY command. The ANZDBFKEY command tests theexistence of the ANZDBF output file and, if the file does not exist, theprogram ends.

When you use the ANZDBFKEY command, the following files are created asoutput:

File Description

QPPTANZK Printer file for the access path and record selection report (Key Fieldsand Select/Omit Listing).


QPPTANKM Printer file for the logical file key report (Analysis of Keys for DatabaseFiles).

The information provided in these reports may suggest ways of combining logicalfiles, for physical files with a number of logical files over them. This process ofcombining reduces the total number of logical files the system must maintain.

For example, consider an application that uses these two logical views of the samephysical file:

� Logical file FILEA with key FIELD1

� Logical file FILEB with keys FIELD1 and FIELD2

In this case, it is likely that you could delete FILEA and use FILEB instead.

Reducing the number of logical views an application uses can help the performanceof the application and of the system.

Figure 10-8 gives an example of the ANZDBFKEY Key Fields and Select/OmitListing.

This report lists the access path and selection (logical files only) values based onthe output produced by the Display File Description (DSPFD) command with asingle line for each key field or selection rule.

12/ð1/95 14:35:ð2 Key Fields and Select/Omit Listing Page 1

File Library Order Path Type Unique Maintenance

PHY QAOFCP QOFCFLS FIFO KEYED N \IMMED

Based on Format Key Field Seq Sign Zone Alt

NAME

JDATE SIGN

STIME SIGN

SEQ SIGN

EXT SIGN

GMTGNO SIGN

File Library Order Path Type Unique Maintenance

LGL QAOFCALL QOFCFLS FIFO KEYED N \IMMED

Based on Format Key Field Seq Sign Zone Alt

QAOFCP QOFCFLS CALRC1 MJDATE SIGN

MTIME SIGN

NAME

\\Record Selection\\ Format Field S/O Comp Values

CALRC1 MJDATE S GT +ð

MTIME A GT +ð

EXT A LE +2

O AL

Figure 10-8. ANZDBFKEY Key Fields and Select/Omit Listing

In the ANZDBFKEY Key Fields and Select/Omit Listing Report, the first output lineshows the following:

File The file name and, to the left of the name, the file type—physical (PHY)or logical (LGL).

Library The name of the library in which the file is contained.

Order Ascending or descending sequence for the keys (LIFO, FIFO).

Path Type The type of access path (ARRIVAL, KEYED, or SHARED).


Unique Whether unique keys are used (Y or N).

Maintenance *IMMED, *RBLD, or *DLY.

The second output line shows the following:

Based On The physical file name.

Format The format name in the logical file.

Key Field The name of the key field (can be one or more lines).

Seq The key sequence (blank is ascending, DES is descending).

Sign The key sign (blank, SIGN, or ABSV).

Zone The zone/digit specified (blank, ZONE, or DIGIT).

Alt The alternative collating sequence (YES or blank).

If record selection is used, the third output line shows the following:

Format The logical file format name.

Field The select/omit field name.

S/O Whether to select (S) or omit (O).

Comp The compare relation such as EQ, GT, LT, and AL (all).

Values The values to compare against.

Printer File QPPTANKM lists the file names, and for logical files, the key fields foreach format in descending order from major key to minor key.

You can use this list to find ways to combine logical files, when physical files havemany logical files over them. By combining files, you can reduce the number oflogical views an application requires and the total number of logical files the systemmust maintain. Having fewer files to maintain can improve the performance of theapplication and of the system.

Figure 10-9 on page 10-16 shows an example of the ANZDBFKEY Analysis ofKeys for Database Files Report.

The columns in the ANZDBFKEY Analysis of Keys for Database Files Report areas follows:

Physical File The name of the physical file.

Library The physical file library.

File The logical files over the physical file.

Library The library the file is in.

Logical Format The logical file format name.

Maint Maintenance. Specify I (immediate), R (rebuild), or D (delay).

Key Fields Major to Minor Up to seven key fields.

No. Keys The number of key fields in the file.

S/O Whether select/omit is specified for key. YES indicates it is specified.


12/ð1/95 14:35:ð2 Analysis of Keys for Database Files Page 1

Physical File QAOFCP Library QOFCFLS

Logical Maint No.

File Library Format \\\\\\\ Key Fields Major to Minor \\\\\\\ Keys S/O

QAOFCP QOFCFLS I NAME JDATE STIME SEQ EXT GMTGNO 6

QAOFCALL QOFCFLS CALRC1 I MJDATE MTIME NAME 3 YES

QAOFCL QOFCFLS MTGREC I GMTGNO NAME JDATE STIME SEQ EXT 6

Figure 10-9. ANZDBFKEY Analysis of Keys for Database Files Report

Analyzing Process InformationUse the Display and Analyze Access Group (DSPACCGRP and ANZACCGRP)commands to examine and analyze the process access group (PAG).

Use DSPACCGRP to report on PAG data for selected jobs. Use ANZACCGRP tofurther analyze the DSPACCGRP output.

Process access group analysis provides you with a view of the operational environ-ment for all jobs, or a group of jobs, in the system at a given time. Use the infor-mation from process analysis to tune your system. When you tune your system,you improve the program environment, causing a reduction in the number of thefollowing:

� Open files

� File buffer and work space sizes

� File open placement in a program

Display Access Group (DSPACCGRP) CommandUse the DSPACCGRP command to see the following:

� Size of a job’s PAG

� Open files

� I/O count for all files

When you use the DSPACCGRP command, the following output files are created:

File Description

QPPTPAGD Printer file

QAPTPAGD Database file (input to the ANZACCGRP command)

The following DSPACCGRP display appears only when you specify OUTPUT(*).


à ð6/16/96 Process Access Group Display DSPACCGRP

1ð:36:45 Sample Report

Job: QFILESYS1 User: QSYS Number: 144221 Type: S

PAG Size: 7ð4,512 Files: ð I/O count: ð

FILE LIBRARY MEMBER SIZE I/O COUNT

(No files open for this PAG)

F3=Exit F5=Refresh PRINT=QPPTPAGD

á ñ

When the PAG information is being displayed, the function key options toDSPACCGRP are as follows:

1. Press F3 (Exit) or the Enter key to end the program.

2. Press F5 (Refresh) to display the PAG again to show any changes thatoccurred since the current display was shown. If the job cannot be displayedbecause its structure is changing, or the job ended, a message appears andthe command ends.

3. Press the Print key to print the displayed job’s PAG data. The format is thesame as the format used when you select OUTPUT(*PRINT).

Figure 10-10 shows an example of the DSPACCGR Process Access Group Infor-mation Report. The fields on this report are the same as those on the display.

12/ð1/95 Process Access Group Information Page 1

15:ð1:59

Job: BYSINN User: VLLXR239 Number: ðð3368 Type: I

PAG Size: 164,352

FILE LIBRARY MEMBER SIZE I/O COUNT

---------- ---------- ---------- -------- ---------

QDGENDSP QSYS 9216 68

QRZLHEL3 QSYS QRZLHEL3 3ð72 1

QDPTPAGD QPFR 4ð96 3

Number of files: 3 Total I/O count: 72

Figure 10-10. Process Access Group Information

When you use the DSPACCGRP command, be aware of the following:

1. If the job you display is changing (such as calling and returning from programsor opening and closing files), DSPACCGRP may try again several times to getan accurate view of the PAG. DSPACCGRP tries five times before it stops anddisplays a message telling you to try the command again.


2. The command shows up to 999 file names and then stops. It tells you thatmore files exist, but could not be displayed.

3. The I/O count (shown for each file) might give you some unexpected results.For example, if you use subfiles on a display, several PUTs of records to thesubfile are included in the I/O count. This is in addition to the I/O operationagainst the subfile control record that causes the subfile to display.

4. PAG SIZE is the total in-use size of the PAG. Because there can be a numberof inactive programs (programs that have returned), the total allocated size ofthe PAG can be larger than the size currently in use. For example, a job thatwas previously using interactive debug, but is now doing some other function,could have an allocated size much larger than the in-use size.

5. To reduce the amount of main storage needed for the job PAG, group files thatare most frequently used. To do this, order the specification (or OPENs, ifexplicit open is used) of files based on their I/O count.

DSPACCGRP shows the files in the order the system opens them (the RPGimplicit OPEN opens the files in reverse order from their order in the program).It does not matter whether the most frequently used files are specified orexplicitly opened first or last, as long as they are grouped together by fre-quency of use.

Analyze Process Access Group (ANZACCGRP) CommandUse the ANZACCGRP command to determine whether:

� Application programs use shared display and database files

� Files are ordered by their frequency of use

� Files are remaining open but have no activity

All of these conditions can affect system performance, especially if the jobs havevery large PAGs.

Consider the size of the PAG when you decide whether to use the PURGE(*NO)job attribute when running an application. An application that requires fast responsetime and has frequent and steady operator interaction would be a candidate forrunning in a PURGE(*NO) environment.

The availability of main storage to dedicate to this application is the critical factor inthe decision to use PURGE(*NO). In general, the larger the PAG, the larger theamount of main storage that would need to be dedicated.

By using the DSPACCGRP command job selection, the ANZACCGRP commandallows you to analyze the PAG of a single job, a set of jobs, or all jobs in thesystem. It is most useful in examining a large number of PAGs collected using theJob(*All), Job(*Int), or Job(generic name) options of the DSPACCGRP command.

The ANZACCGRP command uses the QAPTPAGD database file (the output fromthe DSPACCGRP command) as input.

Note: Because the ANZACCGRP command uses the output from theDSPACCGRP command, be sure to run the DSPACCGRP command firstwith parameter OUTPUT(*FILE) or OUTPUT(*BOTH).


File Description

QSYSPRT Printer file

The ANZACCGRP command produces a three-part report:

� Environment Summary

� Job Summary

� File Summary

Figure 10-11 shows an example of the ANZACCGRP EnvironmentSummary. This section shows information for four categories of job types.

ANZACCGRP SUMMARY REPORT

Sample Report

DATA FROM: QPFRDATA /QAPTPAGD MBR: QAPAGDTA

DATE : 12/14/95 TIME : ð9:58:57

E N V I R O N M E N T S U M M A R Y

----------------------------------------

NUMBER AVERAGE # AVG # DUP AVG # DSP AVERAGE IO AVERAGE

JOB TYPE OF JOBS FILES/JOB FILES/JOB FILES/JOB COUNT/JOB PAG SIZE

------------------ ------- --------- --------- --------- ---------- --------

INTERACTIVE 4 2 2 44 2ð7872

BATCH/AUTOSTART 4 188 878ð8

READER/WRITER 1 3 35 126464

OTHER 6 5 75 135253

----- ----- ----- ---- ----------- --------

TOTAL/AVERAGE 15 3 2 94 14138ð

Figure 10-11. Environment Summary

The following columns appear on the Environment Summary:

JOB TYPE The type of jobs the summary line is for (Interactive,Batch/Autostart, Reader/Writer, or Other).

NUMBER OF JOBS The number of jobs of the corresponding type.

AVERAGE # FILES/JOB The average number of open files.

AVG # DUP FILES/JOB The average number of files open more than oncefor each job. If this number is high, it indicates that files arebeing opened with SHARE(*NO).

AVG # DSP FILES/JOB The average number of open display files for eachinteractive job. If this number is high, it indicates that display filesare defined SHARE(*NO) or that several display files are usedby an application. If there are not a large number of display fileformats that take a lot of PAG space, consider usingSHARE(*YES) and combining display files.

AVERAGE I/O COUNT/JOB The average number of file operations for allopen files, not opened since the job started.

AVERAGE PAG SIZE The average PAG size for each job type.

Figure 10-12 shows an example of the ANZACCGRP Job Summary. Thissection shows information for all selected jobs.




DATE : ð6/14/96 TIME : ð9:58:2ð

J O B S U M M A R Y

-----------------------

TOTAL DUP. DSP. SIZE OF SIZE OF MULT

JOB FILES FILE FILE TOTAL I/O SIZE OF DUP DSP ACT PGM

JOB NAME USER NAME NUMBER TP PAG SIZE USED USED USED COUNT FILES FILES FILES PGM CALL

---------- ---------- ------ -- ----------- ----- ---- ---- ------------- ----------- ----------- ----------- --- ----

QFILESYS1 QSYS 144221 S 7ð4512

QDBSRVXR QSYS 144222 S 421888 19 159 155648

Q4ððFILSVR QSYS 144223 S 516ð96

QQQTEMP1 QSYS 144224 S 258ð48

QQQTEMP2 QSYS 144225 S 253952

QDBSRVXR2 QSYS 144226 S 36ð448 7 2 4ð9 942ð8 53248

QSYSCOMM1 QSYS 144227 S 26624ð

QPADEVððð9 SOFIACN 144592 I 438272 2 2 29 28672 28672

QPADEVðð16 SOFIACN 144593 I 692224 7 2 35 65536 24576

QPADEVðð17 SOFIACN 144594 I 4ð14ð8 3 2 564 32768 28672

QPADEVðð15 LUPITA 144596 I 36864ð 1 1 3 2ð48ð 2ð48ð

QCTL QSYS 144229 M 9ð112ð

QSYSWRK QSYS 14423ð M 1ðð7616

QSTRUPJD QPGMR 144231 A 4ð96ðð

QSPL QSYS 144239 M 831488

QSERVER QSYS 14424ð M 999424

QPADEVððð3 REYNAGAG 1443ð3 I 413696 1 1 8 2ð48ð 2ð48ð

QZDAINIT QUSER 144242 B 1466368 4 32768

QSYSSCD QPGMR 144243 B 282624

QPWFSERVSO QUSER 144244 B 831488

QINTER QSYS 144245 M 888832

QSERVER QPGMR 144246 A 1134592

Figure 10-12. ANZACCGRP Job Summary

The Job Summary contains the following columns:

JOB NAME/USER NAME/JOB NUMBER The name of the job, name of theuser, and job numbers.

TP The type of job. The various types of codes and descriptionsfollow:

Job Type Code Job Type Description

A Autostart

B Batch

I Interactive

M Other

R Reader

S Other

W Writer

X Other

PAG SIZE The gross size of the PAG for the job.

TOTAL FILES USED The number of all open files for the job (includingdisplay and spooled files).


DUP. FILE USED The number of files with more than one ODP in the PAG.If this number is not zero, it indicates that files are being openedSHARE(*NO). If possible, the files should be combined andcreated with SHARE(*YES).

DSP. FILE USED The number of display files open for the job. If thisnumber is high, it indicates that the display files are beingopened SHARE(*NO) or that the application has multiple displayfiles. If possible, display files should be combined and createdwith SHARE(*YES).

TOTAL I/O COUNT The count of file operations (including OPEN andCLOSE) for all open files in the job. This, however, is not thetotal I/O count for the job.

SIZE OF FILES The amount of space in the PAG that is occupied by ODPsfor all open files.

SIZE OF DUP FILES The amount of space in the PAG that is occupied byODPs for files opened with SHARE(*NO). The first ODP for eachduplicate file is not included in this total. This value representsthe amount of space you will save if you use SHARE(*YES).

SIZE OF DSP FILES The amount of space in the PAG that is occupied byODPs for display files.

ACT PGM The number of programs in the call stack that are active.

MULT PGM CALL The number of active programs that appear more thanonce in the call stack.

Figure 10-13 shows an example of the ANZACCGRP File Summary. Thissection shows information for all open files.



Sample Report


DATE : 12/14/95 TIME : ð9:58:57

F I L E S U M M A R Y

-------------------------

FILE NUMBER NUMBER OF TOTAL AVERAGE

FILE NAME LIBRARY MEMBER TYPE OF JOBS TIMES OPEN I/O COUNT ODP SIZE

----------- ---------- ---------- ---- ------- ---------- ----------- --------

QRZPHELM QSYS QRZPHELM DB 1 1 256ð

QRZPHVPD QSYS QRZPHVPD DB 1 1 8 256ð

QRZPHDEL QSYS QRZPHDEL DB 1 1 256ð

QRZPHLOC QSYS QRZPHLOC DB 1 1 256ð

QRZPPTF QSYS QRZPPTF DB 1 1 256ð

QRZPLCG QSYS QRZPLCG DB 1 1 256ð

QRZPTCBL QSYS QRZPTCBL DB 1 1 256ð

QRZPTOEM QSYS QRZPTOEM DB 1 1 256ð

QRZPTSPC QSYS QRZPTSPC DB 1 1 256ð

QRZLHEL1 QSYS QRZLHEL1 DB 1 1 135 3ð72

QRZLHEL2 QSYS QRZLHEL2 DB 1 1 3ð72





QRZLHVP1 QSYS QRZLHVP1 DB 1 1 59 256ð

QRZLHVP2 QSYS QRZLHVP2 DB 1 1 3ð72

QRZLLOC1 QSYS QRZLLOC1 DB 1 1 256ð

QRZLTEL1 QSYS QRZLTEL1 DB 1 1 3ð72

QRZLTEL2 QSYS QRZLTEL2 DB 1 1 3ð72

QRZLHEDR QSYS QRZLHEDR DB 1 1 3ð72

QRZLDSUA QSYS QRZLDSUA DB 1 1 3ð72

QRZLDSU1 QSYS QRZLDSU1 DB 1 1 3ð72

QRZLPATH QSYS QRZLPATH DB 1 1 256ð

QRZLPTH1 QSYS QRZLPTH1 DB 1 1 3ð72

QRZLLCG1 QSYS QRZLLCG1 DB 1 1 3ð72

QRZLLCG2 QSYS QRZLLCG2 DB 1 1 256ð

QADBXREF QSYS QADBXREF DB 1 1 256ð

QADBFDEP QSYS QADBFDEP DB 1 1 256ð

QADBLDEP QSYS QADBLDEP DB 1 1 256ð

QADBLDNC QSYS QADBLDNC DB 1 1 3ð72

QADBXDIC QSYS QADBXDIC DB 1 1 256ð

QADBXFIL QSYS QADBXFIL DB 1 1 3ð72

QADBXOWN QSYS QADBXOWN DB 1 1 3ð72

QPSPLPRT QSYS DS 1 1 12 46ð8

Qð4ð79Nðð1 QSPL Q979578132 DB 1 1 2ð 256ð

QDSPUIM QSYS DS 2 4\ 67 19968

QDGENDSP QSYS DS 2 2 46 16384

QDDSPEXT QSYS DS 1 1 8 46ð8

QAPTPAGD QPFRDATA QAPAGDTA DB 1 1 57 256ð

NETFILE QNET DS 1 1 745 3584

NET38SPOOL QNETSPOOL VN6A633564 DB 1 1 7 13824

Figure 10-13. ANZACCGRP File Summary

The ANZACCGRP File Summary contains the following columns:

FILE NAME/LIBRARY/MEMBER Name of the open file ODP.

FILE TYPE One of the following:

DB Database or spooled file

DS Display or ICF file

SP Spooled file being created


NUMBER OF JOBS The total number of jobs using the file.

NUMBER OF TIMES OPEN The total number of times the file has beenopened. If this number is larger than the number of jobs (indi-cated by an *), the file has been created with SHARE(*NO).

TOTAL I/O COUNT The total number of file operations (including OPENand CLOSE) that have been performed by all jobs for currentlyopen files. If this number is very low, the applications should bechanged to open the file only when needed.

AVERAGE ODP SIZE The average amount of space in the PAG occupiedby each open occurrence of the file. In general, this numberrepresents the ODP size for the file.



Chapter 11. Performance Explorer

Performance explorer is a data collection tool that helps the user identify thecauses of performance problems that cannot be identified by collecting data usingthe performance monitor or by doing general trend analysis. Two reasons to useperformance explorer include:

� Isolating performance problems

� Modeling the performance of applications

| The collection functions and related commands of performance explorer are part of| the OS/400 operating system. The reporting function and its associated commands| are part of the Performance Tools for AS/400 licensed product, the Manager| feature. The AS/400 Performance Explorer Tips and Techniques, SG24-4781, pro-| vides additional examples of the performance explorer functions and examples of| the enhanced performance explorer trace support.

Do I Need Performance Explorer?Performance explorer is a tool that helps find the causes of performance problemsthat cannot be identified by using tools that do general performance monitoring. Asyour computer environment grows both in size and in complexity, it is reasonablefor your performance analysis to gain in complexity as well. The performanceexplorer addresses this growth in complexity by gathering data on complex per-formance problems.

This tool is designed for application developers who are interested in understandingor improving the performance of their programs. It is also useful for users know-ledgeable in performance management to help identify and isolate complex per-formance problems.

Note: If you are familiar with the Sampled Address Monitor (SAM) function or theTPST PRPQ, your transition to the performance explorer should be smooth.

Who Needs Performance ExplorerThe user that wants to use the performance explorer for application and programanalysis does not need to be an expert in the area of performance to make use ofthe performance explorer. The same level of expertise that was required whenusing SAM in V3R1 and earlier versions is what is needed with the performanceexplorer.

To use the performance explorer to isolate a performance problem, you shouldhave a good understanding of the performance issue. Using the performanceexplorer requires more performance specialized knowledge. You should also havean idea of where the problem might be on the system. You need to set up perform-ance explorer to collect data in specific areas of your system, and you will have tointerpret the data.


When You Need Performance ExplorerWhen you find that performance advisor is not telling you enough, you should con-sider the performance explorer. In short, performance explorer is the tool you needto use after you have tried the other tools. It gathers specific forms of data that canmore easily isolate the factors involved in a performance problem.

Comparison of Explorer to Other Performance ToolsA good way to understand performance explorer is to see it compared and con-trasted to other tools in the Performance Tools licensed program or in the OS/400operating system.

Performance Explorer and Advisor FunctionsThe performance advisor and the performance explorer are quite different functions.The explorer's main purpose is collecting specific data. To do this, it has its owncollecting facility. The advisor's role is assessing data collected by the performancemonitor. It produces, after its analysis, a list of conclusions and recommendationson ways you can improve your performance. The explorer does not do any analysisfor you.

If you are using the advisor, you are probably doing routine performance mainte-nance. If you are using the explorer, you know that you have a performanceproblem, and you are having a hard time identifying its cause.

Performance Explorer and Performance MonitorIn a sense, the performance explorer is much like the performance monitorbecause they both collect data. The main difference is that performance explorerprovides a much greater level of detail. Also, unlike the performance monitor, theperformance explorer allows you to specify particular areas of interest, and it allowsyou to focus the collection. The performance explorer collection can be tuned toinclude very specific data. It is the ability to tune, or specify, the data to be col-lected that makes the performance explorer effective in helping isolate performanceproblems.

| Note: You can run both collections of data at the same time. However, you should| keep this to a minimum because the system is significantly affected when| both collections are active.

This detail is good because many times the factors that contribute to performanceproblems are not isolated. Often, there are several contributing factors to theproblem. Since many factors are contributing to the problem, it is difficult to identifyindividual causes using tools that assess the whole system. You need a tool thatprovides the details.

Performance explorer can be used to isolate the factors behind a problem that youhave identified. This tool pulls the symptoms together. For example, a sluggishsystem could be caused by DASD reads and writes, or CPU, or a combination oftwo or more. With performance explorer, you can find the cause.


Benefits of Performance ExplorerPerformance explorer has advantages for people who need detailed performanceanalysis on an AS/400 system. Using performance explorer you can:

� Do a detailed analysis on one job without affecting the performance of otheroperations on the system.

� Analyze data on a system other than the one on which it was collected. Forexample, if you collect data on a managed system in your network, you cansend it to the central site system for analysis.

� Map performance information to code

Using performance explorer, you can map performance information back tosource lines of code to correlate the performance data generated with the codethat caused the data to be generated.

� Collect performance information on user-developed software.

To collect performance information on user-developed software, performancecollection must be enabled when the program is created. In general, all user-developed software is created with performance collection enabled.

For more information on how to enable or disable performance collection, referto the specific compiler documentation and refer to the Enable performance col-lection (ENBPFRCOL) parameter on the Create Bound C Program (CRTBNDC)command.

Programs can also be enabled or disabled using the ENBPFRCOL parameteron the Change Program (CHGPGM) command.

Note: The default for all ILE languages is to have the pre-defined trace pointsat the program-level enabled. However, some languages provide a com-piler option (ENBPFRCOL parameter) that allows you to turn the ena-bling off. Those languages that do not provide the option will have thepre-defined collection points enabled.

The significance of the collection mechanism is that:

– It is controlled by pre-defined collection points that are compiler generated.

– The pre-defined collection points are scalable.

– The system and all IBM code are shipped with these pre-defined tracepoints.

– The default for all compilers is to have these pre-defined collection pointsenabled.

How Performance Explorer Works1. You set up a performance explorer data collection using a definition.

2. You start performance explorer and it collects the data based on the definition.

3. You can create reports from the databases.

4. You can print those reports, if you want to.

You can access the commands associated with the performance explorer tool usingone of the following:

Chapter 11. Performance Explorer 11-3

� The command interface. Type the commands from the command line. All thecommands are part of the OS/400 operating system, except the PRTPEXRPTcommand.

� The Performance Tools menu options. Select option 5 (Performance utilities)from the IBM Performance Tools menu, then option 2 (Work with PerformanceExplorer).

à ðWork with Performance Explorer


1. Add Performance Explorer Definition (ADDPEXDFN)

2. Change Performance Explorer Definition (CHGPEXDFN)

3. Remove Performance Explorer Definition (RMVPEXDFN)

4. Start the Performance Explorer (STRPEX)

5. End the Performance Explorer (ENDPEX)

6. Print Performance Explorer Reports (PRTPEXRPT)

7. Delete Performance Explorer Data (DLTPEXDTA)


===>


á ñ

Performance Explorer DefinitionsThe performance explorer definitions are how you describe to the performanceexplorer the type of data that you want to collect. The definition is then used todefine the information that should be collected when the performance explorer isstarted. When you create a performance explorer definition, you are really justdescribing what you want collected. To help you understand how performanceexplorer works, scenarios are provided to help you understand the concepts of per-formance explorer. See “Creating a Performance Explorer Definition” on page 11-6.

The performance explorer provides the following types of data collection:

� Statistical

� Profile

� Trace

Each type gathers data in a different way and organizes it in a unique fashion.

| Statistical type identifies applications and IBM programs or modules that consume| excessive CPU use or that perform a high number of disk I/O operations. Typically,| you use the statistical type to identify programs that should be investigated further| as potential performance bottlenecks.


| You use the statistical type to find the high resource consuming programs and| modules that run during the performance collection. The objective is to determine if| there are specific programs or modules consuming most of the resource. If you| suspect that using a particular application is causing poor performance, use the| *STATS collection. The *STATS collection can determine which programs should| be examined based on the CPU statistics, disk statistics, and the number of times| the program was called.

| For example, you may find that the highest CPU utilization program or module is| called only once during the collection period. You can have another program or| module that uses a moderately high level of CPU utilization but is called hundreds| of times. You need to decide which program or module should be analyzed: the| one called only once or the one called hundreds of times.

The statistics can be structured in either a hierarchical or flattened manner.

� A hierarchical structure organizes the statistics into a call tree form in whicheach node in the tree represents a program procedure run by the job or task.

� A flattened structure organizes the statistics into a simple list of programs orprocedures, each with its own set of statistics.

| Profile type identifies high-level language (HLL) programs that consume excessive| CPU utilization based on source program statement numbers.

| You can also identify a program that is constantly branching between the start of| the program and subroutines at the end of the program. If the program is large| enough, this constant jumping back and forth can cause excessive page fault rates| on a system with limited main storage.

When a trace, statistics, or profile mode is selected, a number of options are pro-vided to limit the scope of the collected performance data. You can collect on spe-cific jobs, tasks, OS/400 programs, modules, and procedures.

Trace type gathers a historical trace of performance activity generated by one ormore jobs on the system. The trace type gathers very specific information aboutwhen and in what order events occurred. The trace type collects detailed program,Licensed Internal Code (LIC) task, OS/400 job, and object reference information.

General Flow of the Performance ExplorerThe following sections should help you become familiar with the natural paththrough the performance explorer. Figure 11-1 on page 11-6 shows a basic workcycle.


ADDPEXDFNCommand

QPEXDATADatabase

STRPEXCommand

ENDPEXCommand

PRTPEXRPTCommand

RunsCollections

RV3S161-0

Database

Figure 11-1. Performance Explorer Basic Flow Pattern

The work cycle is made up of these activities:

| � The first task in this cycle is to create a session definition that informs the| AS/400 system about what processes you want to collect performance data. On| the Add Performance Explorer Definition (ADDPEXDFN) command, specify the| collection type and a name for the definition. This definition is stored as a data-| base member by that name in the QAPEXDFN file in library QUSRSYS. The| name that you specify is used on the STRPEX command.

� The second task is to start collecting data (STRPEX command), which in turncreates a data file containing the specified performance data.

� The third task is to stop collecting the data and save it to database files foranalysis. Use the End Performance Explorer (ENDPEX) command to stop thecollection.

� The fourth task is to analyze the performance data. The PRTPEXRPTcommand provides unique reports for each type of data (statistical, profile, ortrace).

The other option for analysis is to write your own queries over the set of data-base files.

Creating a Performance Explorer DefinitionThe first task is to define what data is to be collected using the Add PerformanceExplorer Definition (ADDPEXDFN) command. After the definition is completed andsaved, you are ready to continue to the second task in the cycle of work.

Before creating a new definition, consider what kinds of information you want andthe amount of detail you need. In general, the three main types of collections havethe following characteristics:

� Statistics type definitions

– Using this definition results in collecting the same basic information as theTPST tool.

– Good for first order analysis of OS/400 original program model (OPM) pro-grams, procedures, and MI complex instructions.

- Gives number of invocations

- Gives both inline and cumulative CPU usage in microseconds


- Gives both inline and cumulative number of synchronous and asynchro-nous I/O

- Gives number of calls made

– Works well for short or long runs

– Size of the collected data is fairly small and constant for all runs

– Run time collection overhead of ILE procedures may be a problem due tothe frequency of calls. Although run time is degraded, performance explorerremoves most of the collection overhead from the data.

– Uses combined or separated data areas. The MRGJOB parameter on theAdd Performance Explorer Definition (ADDPEXDFN) command specifieswhether all program statistics are accumulated in one data area, or keptseparate (for example, one data area for each job).

� Profile type definitions

– Gives detailed breakdown of where you are spending time within a programor procedure

– Size of collection is fairly small and constant regardless of length of run

– Can narrow the scope of data collected to just a few programs of interest

– Limit of 16 MI programs means that you should use this as a second orderanalysis tool.

– Can vary overhead by changing sample interval. An interval of 2 millisec-onds seems a good first choice for benchmarks.

– No restrictions on pane size due to the number of programs specified orthe size of the programs specified.

� Trace type definitions

– Storage management and flow trace definitions

– Good for watching storage management activity on the system. Also showsMI complex instructions.

– Longer runs collect more data

Starting the Performance ExplorerTo start the performance explorer, use the Start Performance Explorer (STRPEX)command. You can specify to start a new performance explorer session or resumean already active session.

Note: You are allowed to have only one active session at a time. Multiple ses-sions are not allowed.

Ending the Performance ExplorerTo end the performance explorer session, use the End Performance Explorer(ENDPEX) command. The ENDPEX command performs the following actions onthe collected data:

| � Places the collected data in files QAYPExxx in the library that you specify.


| Use OPTION(*END) and DTAOPT(*LIB) to do this. The database member| name for all the QAYPExxx files uses the session name as the default unless| you specify a name for the DTAMBR parameter.

| You can specify RPLDTA(*NO) to erase data that was collected using this| session name or RPLDTA(*YES) to add the collected data to the existing data.| Unless you are a very sophisticated user, use RPLDTA(*NO).

| � Places the collected data into a single IBM-defined file.

| Use OPTION(*END) and DTAOPT(*FILE) to do this. Typically, you would use| *FILE only under the direction of an IBM service representative. Specifying the| *FILE value on the DTAOPT parameter saves the collection information into a| binary file. The binary file option should be used only if the data is going to be| shipped to IBM. The performance tools can analyze only the database files.

| � Discards the collected data.

| Use OPTION(*END) and DTAOPT(*DLT) to delete any collected data. You do| this when you determine the collected data cannot be used. For example, one| of the suspected jobs did not start as expected. If you choose the *DLT option,| the collected performance data for the session is never saved.

| � Saves the collected data.

| Use OPTION(*END) and DTAOPT(*LIB) to save the collection into a database| file. Use these values if you are sending data to a manager site.

| � Suspends the collection session but does not end it.

| Use OPTION(*SUSPEND) to do this. You can later start the data collection| again by issuing the STRPEX command with OPTION(*RESUME) for the spe-| cific session ID.

| Note: If you forget the active collection session name, you cannot end the| collection without powering off the system. To find the active session| name, use the ENDPEX SSNID(*SELECT) command.

Deleting Performance Explorer DataTo delete performance explorer data, use the Delete Performance Explorer Data(DLTPEXDTA) command. The DLTPEXDTA command discards performance datafrom a set of database files.

| Creating and Printing Performance Explorer ReportsYou create and print performance explorer reports by using the Print PerformanceExplorer Report (PRTPEXRPT) command.

| Use the OUTFILE parameter when you want to customize your Trace Report. The| performance explorer stores its collected data in the QAVPETRCI file, which is| located in the QPFR library. Type the following command to view the contents for a| single record:

| DSPFFD FILE(QPFR/QAVPETRCI)


Finding Your Performance Explorer DefinitionsThe SELECT parameter on the ENDPEX command provides a list of all active per-formance explorer sessions on the system. This parameter shows the Select Per-formance Explorer Session display.

à ðSelect Performance Explorer Session


1=Select

Event

Option Session User Type State Count

(No objects to display.)

Types of Performance Explorer Reports| Table 11-1 identifies the sections that are available for the individual performance| explorer reports. Some sections are common to all reports; some reports have| unique sections. The information that follows the table shows examples of each| section.

| Table 11-1. Sections that are available for the performance explorer reports

| Section| Statistics Report| Profile Report| Trace Report| Base Report

| Definition| X| X| X| X

| Run| X| X| X| X

| Task| X| X| X| X

| CPU Summary| X| X

| Library| X| X

| Main| X| X| X

Common Report SectionsThe following series of report examples show the sections that are common to theperformance explorer reports. Each section also contains the field descriptions foreach report.

Definition InformationYou define what kind of data to collect with the ADDPEXDFN command. The Defi-nition Information report reflects the definition that was used in collecting the data.This heading appears only once in any type of report.

| Figure 11-2 on page 11-10 shows an *STATS collection type as an example.


| Performance Explorer Report

| Definition Information Page 1

| Library . . : QPEXDATA

| Member. . . : STATSF

| Description : BLANK

| Type . . . . . . . . . . . . : STATISTICS

| Definition Name. . . . . . . : SFSTATSF

| Defined By . . . . . . . . . : FOLEY

| Definition Description . . . : stats job(\) task(\none) dtaorg(\flat)

| Data Organization. . . . . . : FLAT

| Overhead Subtraction . . . . : YES

| Merge Jobs . . . . . . . . . : YES

| Include Dependent Jobs . . . : YES

| Selected Jobs:

| Name User Number

| \

| Selected Task Names:

| \NONE

| Selected MI Complex Instructions:

| \ALL

| Figure 11-2. Example for *STATS Definition Information

The Definition Information shows the following values:

| Library The library that contains the collected data.

| Member The name of the member that contains the collected data.

Description The description of the data that was saved.

Type The method for collecting performance data.

Definition Name The name of the performance explorer definition.

Defined By The user ID that created the definition

Definition Description The description given to the definition

Include Dependent Jobs The tasks or jobs that are created on behalf of a task orjob that is currently part of the collection are part of the collection.

Selected Jobs The jobs that are included in the performance explorer data col-lection session. The “*” means the current job when the STRPEXcommand is issued.

Name The name of the job to include in the performance explorerdata collection session. You can specify up to 10 qualifiedjobs.

User The name of the job associated with a specific user. Whenyou specify a user name, you further qualify the job.

Number The number of the job. When you specify a job number, youfurther qualify the job.

Selected Task Names The name of the Licensed Internal Code (LIC) low-leveltask to be part of the collection. AS/400 Licensed Internal Code Diag-nostic Aids - Volume 1 contains a list of LIC tasks and descriptions.

Note: By default all task names are included in each collection.

Selected MI Complex Instructions The machine interface (MI) complexinstructions that are part of the collection. The MI complex instructionsrepresent all the high-level machine interface instructions used byOS/400 support. MI complex instructions include functions like finding


the pointer to an object, writing records sequentially to a file, or creatinga duplicate object.

Note: By default all MI instructions are included in each collection.

Sample Interval (ms) The rate, in milliseconds, that profile mode collectionssample the location for the currently running programs.

Selected Programs The programs listed as part of a profile type definition .

Pane Size The pane size is the number of consecutive program instruc-tion addresses assigned to each counter. Pane size canrange from 4 bytes to 4096 bytes. The default pane size is 4bytes. Valid values are 4, 8, 16, 32, 64, 128, 256, 512, 1024,2048, and 4096. The smaller the pane size, the moredetailed the program profile information will be.

For example, a pane size of 4 means one instruction. A panesize of 2048 means 512 instructions.

Library The library the program is in.

Program The program whose performance profile data will be col-lected.

Type The type of program specified, either a program (*PGM)object or a service program (*SRVPGM) object.

Module The specific module within the program or service programthat is to be profiled.

Procedure The specific procedure within the specified module that is tobe profiled.

Run InformationThis report provides general information about when the data was collected, thestate of the machine from which the data was collected, details about the length ofcollection, and who ran the collection. This heading appears only once in any typeof report.

Figure 11-3 on page 11-12 shows an example of the Run Information section. TheRun Information section provides the same information for each of the main reports,which is general system and session information.



| Run Information Page 2




| Sessions since IPL. . . . . . . . . . . . . : 1

| Session name. . . . . . . . . . . . . . . . : FOLEY

| Start time. . . . . . . . . . . . . . . . . : 1998-11-ð6-1ð.4ð.ð2.745ð8ð

| Stop time . . . . . . . . . . . . . . . . . : 1998-11-ð6-1ð.4ð.51.567576

| Total time DD-HH.MM.ss.uuuuuu. . . . . . . : ðð-ðð.ðð.48.822496

| Suspend time (us) . . . . . . . . . . . . . : 13,549,392

| Duration of trace . . . . . . . . . . . . . : 352731ð4

| Number of events. . . . . . . . . . . . . . : 2,332

| Trace wrap count. . . . . . . . . . . . . . : ð

| Missed events due to buffering. . . . . . . : ð

| Missed events while recording . . . . . . . : ð

| Job creating session. . . . . . . . . . . . : QPADEVðð29FOLEY 1ð1ð29

| Started by user . . . . . . . . . . . . . . : FOLEY

| Target system . . . . . . . . . . . . . . . : ABSYSTEM

| Serial number . . . . . . . . . . . . . . . : 1ð-18ð3D

| System type . . . . . . . . . . . . . . . . : 94ð6

| System model. . . . . . . . . . . . . . . . : 5ðð

| Total pages memory. . . . . . . . . . . . . : 32,768

| OS/4ðð level. . . . . . . . . . . . . . . . : 37ð

| Version . . . . . . . . . . . . . . . . . . : V4R2Mð

| Configured ASPs . . . . . . . . . . . . . . : 1

| Logical DASDs . . . . . . . . . . . . . . . : 4

| Jobs/tasks in session . . . . . . . . . . . : 1

| Jobs in session . . . . . . . . . . . . . . : 1

| Figure 11-3. *STATS Run Information Report

| The Run Information section shows the start, stop,and total run times of the col-| lection. You also see that the job ran the collection on system ABSYSTEM.

The Run Information shows the following values:

Library The library the database file is in.

Member The database file member containing the data.


Sessions since IPL The number of times that the performance explorer collecteddata since the last IPL

Session name The name of the session.

Start time The time that the session was started

Stop time The time that the session was stopped.

Total time The total elapsed time that data was being collected, including sus-pended time.

Suspend time (us) The amount of time, in microseconds, that the session was in asuspended state. It's possible for this field to show a number other thanzero even if you have not suspended the session.

| Duration of trace (us) The total active runtime minus the total suspended time.

Number of events The total number of events encountered during a session.

Trace wrap count The trace wraps to the beginning when the trace file is full. Theoldest trace records are written over by new ones as they are collected.This is the number of times the trace wrapped.


Notes:

1. Trace wrap count applies only to trace type session.

2. Specify the *STOPTRC value on the TRCFULL parameter of theADDPEXDFN command to avoid this wrapping.

| Missed events due to buffering The number of events that were not collected| during the session.

| Missed events due to recording The number of events that were not collected| during the session.

Job creating session The name of the job that issued the STRPEX command

Started by user The user ID that issued the STRPEX command

Target system The name of the system the data was collected on

Serial number The serial number of the system the data was collected on

System type The type of system the data was collected on

System model The model of system on which the data was collected

| Total pages memory The number of 4-K memory pages on the system on which| the data was collected. 98,304 means 384MB of main storage.

| 1. 98,3ð4 / 1ð24(1K) = 96

| 2. 96 \ 4 = 384

OS/400 level The OS/400 driver level of the system on which data was collectedThe OS/400 level relates to the latest level of cumulative package that isinstalled on your system.

Version The OS/400 release level of the system on which data was collected

Configured ASPs The number of ASPs on the system on which data was col-lected

Logical DASDs The physical number of disk drives attached to the system, if mir-roring is not used. If your system has mirrored protection active, the mir-rored disk pair count as one logical DASD.

Data areas The number of performance explorer internal data areas the collectionwas partitioned into. If you specify MRGJOB(*YES), the performanceexplorer stores the collected data for all jobs in a combined data area.

Jobs/tasks in session The total number of tasks and jobs that were included inthe session.

| Jobs in session The total number of jobs that were included in the session. In this| example, this number is equal to Jobs/tasks in session minus Jobs in| session. There is no correlation between jobs and LIC tasks. The col-| lections always contain all the LIC tasks of the system.

Task InformationThis report shows the jobs and task from which data was collected. AS/400Licensed Internal Code Diagnostic Aids - Volume 1 contains a list of LIC tasks anddescriptions.

| Figure 11-4 on page 11-14 shows an example of the Task Information section. The| Task Information section provides the same information for each of the main


| reports. If the task or job did meaningful work during the collection time period, the| values under the CPU (us) and CPU Percent are a number other than 0.


| Task Information Page 5




| Task ID Job/Task Name Pool Priority Existence Elapsed Time (us) CPU (us) CPU

| Start/End Percent

| ----------------------------------------------------------------------------------------------------------------------------------

| 6739 QPADEVðð29 FOLEY 1ð1ð29 4 163 Y Y 41897112 822ð96 2ð.97

| 1 CFINTð1 ð ð Y Y 4257ððð8 3ð98472 79.ð3

| ----------------------------------------------------------------------------------------------------------------------------------

| Figure 11-4. Task Information Report

The Task Information Report shows the following values:



Description The description of the data that was collected.

Task ID The system identifier for the task

Job/Task Name The name of the task or job under which the data was run.

Pool The system pool that the job or task in on the system.

Priority The relative LIC priority that the job or task runs at on the system.

Note: The priority column here is not the same as the job priority thatis shown on the Work with Active Jobs display. You can subtract140 from the non-SLIC tasks to find the RUNPTY value used onAS/400.

Existence Start Indicates if the job or task existed at the start of the collection(Y/N)

Existence End Indicates if the job or task existed at the end of the collection (Y/N)

Elapsed Time (us) The elapsed time (in microseconds) that the job or task existedduring the collection

CPU (us) The total amount of CPU time used (in microseconds) by the job or taskduring the collection.

CPU Percent The percentage of CPU used by this job or task as compared to thetotal CPU used by all the jobs or tasks in the collection.

| The Priority values that are shown do not correspond to the Run priority| (RUNPTY) parameter value. However, for OS/400 jobs with priority values of 1-99,| you can subtract 140 to correspond to the RUNPTY value.

| RUNPTY(15) is a typical priority for spooled writer jobs (class QSPL).

| For Licensed Internal Code (LIC) tasks, the user cannot change them. In most| cases LIC task priorities are higher than OS/400 jobs. However, some LIC tasks| run at the same priority as the user job for which they are performing a function.

| The disk drive tasks that start with prefix DBI or DBL typically run under the| RUNPTY value of the OS/400 job for which they are performing the function.


Report-Specific SectionsThis section shows examples of the main reports and also report sections that arespecific to certain reports.

Summary InformationSummary information provides a subset of the information shown in the mainreports. The Profile Report and the Statistics Report have their own Summary Infor-mation. The Trace Report does not include a Summary Information Report.

Performance Explorer Report 1/21/97 13:39:1ð

Profile CPU Summary Information Page

3

Library . . . . : COOL

Member. . . . . : RBPROF2PGM

Description . . : RBPROF-CMDCSTPEXH (CLCSTPEXHI, CSTPEX)

Total CPU . . . : 848ð864

Job CPU . . . . : 8256856 97.4 %

Task CPU. . . . : 224ðð8 2.6 %

-----------------------

Total Samples . : 7664

Total Hits. . . : 11ð8 14.5 %

Figure 11-5. Example for *PROFILE CPU Summary Information

The Profile CPU Summary Information Report shows the following values:



Description The description the user associated with the collected data

Total CPU The total amount of CPU used by the tasks and jobs that were collectedon (not the whole system CPU).

Job CPU The total amount of CPU used by the jobs that were collected on.

Task CPU The total amount of CPU used by the tasks that were collected on.

Total Samples The total number of samples collected during a session.

Total Hits The total number of samples that occurred within the programs the userspecified.

Performance Explorer Report 11/ð7/97 9:54:47

Stats CPU Summary Information Page 3

Library . . . . . : QPEXDATA

Member. . . . . . : STATSF

Job name. . . . . : ALL JOBS/TASKS IN SESSION

Description . . . : BLANK

Total Raw CPU . . : 392ð568

Overhead Removed. : 112381

Total CPU . . . . : 38ð8187

Task CPU. . . . . : 3ð98472 81.4 %

Job CPU . . . . . : 7ð9715 18.6 %

-----------------------

Pgm/Mod CPU. . : 31ð419 8.2 %

Unknown CPU. . : 399296 1ð.5 %

Figure 11-6. *STATS CPU Summary Information

The Statistics Summary shows the same fields as the Profile Summary with theaddition of the following values:

| Job name The job name, user ID, and job number. ALL JOBS/TASKS IN| SESSION is a special value.


Total Raw CPU The total amount of CPU used by tasks and jobs that was col-lected on (including any collector overhead).

Overhead Removed The difference between the total raw CPU and total CPU (inother words, adjusted CPU).

Total CPU The total amount of CPU used by tasks and jobs that were collected on(less any collection overhead that could be removed).

Pgm/Mod CPU The total CPU of the programs and modules that were collected onand reported on in the STATS INFORMATION section of the report.

Unknown CPU The difference between the Job CPU and the Pgm/Mod CPU.

Library InformationLibrary information - shows collection information for each library. Also providesdata on call and complex MI counts, CPU utilization, and disk I/O operations. Thissection is available for the statistical report only.

The library section identifies the libraries that contained the programs or modulesthat were active during the collection period. All CPU usage and disk I/O operationstatistics for all the programs or modules in a specific library are totaled for thatlibrary. It is common to have a cumulative CPU percent total that is higher than99.9%. In those cases, you see a CPU percent value of ****. The **** value is con-sidered normal in most cases. Figure 11-7 on page 11-17 shows a Library Sectionthat summarizes the CPU and disk I/O activity at the library level.

| One area of interest is the **Unknown category. You can start and stop a collection| at any time. You receive resource usage data, but depending on what the programs| in a job are doing, you may not see it accounted for accurately. When this| happens, the results end up in the **Unknown category and not in the program that| you thought was using all the resources.

| The shorter the time period that you run a collection, the greater the percentage| allocated to **Unknown may be. This occurs because performance explorer collects| data from the entry to a program and from the exit from a program. If the program| is already entered when you start the collection, the data that is collected is not| allocated to that specific program. Instead, the data gets counted and put into a| counter called **Unknown.

The Statistics Report, at the library level, shows the following values:




Name The Name of the library for which the statistics are being shown.

Times Called The number of times programs in that library were called.

Calls Made The number of calls programs in the library made

MI CPLX Issued The number of MI complex instructions that were called by aprogram or procedure. MI complex instructions are the architected MIinstructions of AS/400. They are identified in the report with a single “*”in front of the instruction name.

Inline Stats The statistics that were incurred directly by programs in the library.


Performance Explorer Report 11/ð7/97 9:54:47

Statistics Information Page 3

Library Section

Library . . : QPEXDATA

Member. . . : STATSF

Job name. . : ALL JOBS/TASKS IN SESSION

Description : BLANK

+----------------- Inline Stats ------------++-------------- Cumulative Stats -----------+

Times Calls MI CPLX CPU DB DB NDB NDB CPU DB DB NDB NDB Call

Name Called Made Issued (us) / % SIO AIO SIO AIO (us) / % SIO AIO SIO AIO Level

----------------------------------------------------------------------------------------------------------------------------------

\\LIC Task ð ð ð 3,ð98,472 81.4 ð ð ð ð 3,ð98,472 81.4 ð ð ð ð ð

\\Unknown ð ð ð 399,295 1ð.5 ð ð ð ð 399,295 1ð.5 ð ð ð ð ð

Figure 11-7. *STATS Information Library Section

CPU (us) The amount of CPU in microseconds used by programs inthe library

% The percentage of CPU used as compared to the Total CPUfound in the summary section.

DB SIO The number of database synchronous I/O operations per-formed by programs in the library.

DB AIO The number of database asynchronous I/O operations per-formed by programs in the library.

NDB SIO The number of non-database synchronous I/O operationsperformed by programs in the library.

NDB AIO The number of non-database asynchronous I/O operationsperformed by programs in the library.

| Cumulative Stats The statistics that were incurred both directly and indirectly by| programs in the library. This can occur through calls to other programs| in the other libraries in this list.

| Note: At the library level, cumulative statistics can be greater than| 100%. In this example, the \\\\ means that the percent is| greater than 100%.

| CPU (us) The cumulative amount of CPU in microseconds that is used| by programs in the library and other programs they called.

| % The percentage of cumulative CPU that is used as compared| to the Total CPU that is found in the summary section.

| DB SIO The cumulative number of database synchronous I/O oper-| ations that are performed by programs in the library and| other programs they called.

| DB AIO The cumulative number of database asynchronous I/O oper-| ations performed by programs in the library and other pro-| grams they called.

| NDB SIO The cumulative number of non-database synchronous I/O| operations that are performed by programs in the library and| other programs they called.

| NDB AIO The cumulative number of non-database asynchronous I/O| operations performed by programs in the library and other| programs they called.


| Call Level Shows the invocation call level in a hierarchical statistics col-| lection. Specify DATAORG(*HIER) on the ADDPEXDFN| command to show the data in a hierarchical format.

| Figure 11-8 shows a sample Library section from the Profile Information Report.

| Performance Explorer Report 6/ð1/95 1ð:34:15

| Profile Information Page 3

| Library Section

| Library . . : COOK

| Member. . . : RBPROF2PGM

| Description : RBPROF-CMDCSTPEXH (CLCSTPEXHI, CSTPEX)

| Histogram Hit Hit Cum Start Map Stmt Name

| Cnt % % Addr Flag Numb

| ----------------------------------------------------------------------------------------------------------------------------------

| \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ 11ð8 1ðð.ð 1ðð.ð 22B55B7DFDðð236ð MP 7 PFREXP

| Figure 11-8. Example for *PROFILE Library Section

The Profile Information Report shows the following values:




Histogram The histogram graphically illustrates the number of sample hits againstthis entry as compared with the total number of sample hits.

Hit Cnt The number of samples that occurred within this entry

Hit % The percent of hits for this line as compared to the total number ofsample hits.

Cum % The cumulative Hit % of this entry and all preceding entries.

| Start Addr The address of the first instruction. The Start Addr column is only filled| in for the Profile Information Report.

Map Flag The map flag indicates what this entry corresponds to. The possiblevalues for the map flag are:

� DS (distributed statement). This line represents multiple sourcestatements that were optimized into a single instruction.

� SS (single statement). This line represents a single source state-ment.

� MS (multiple statement). This line represents multiple source state-ments.

� MP (multiple procedures). This line represents multiple procedures.

Stmt Numb The MI statement number of the first instruction of this entry.

Notes:

1. To get a detailed Profile Information Report that shows the utilizationof your HLL program statements, you should specifyTYPE(*PROFILE) on the PRTPEXRPT command and summarizethe collected data by PROFILEOPT(*BLANK) orPROFILEOPT(*STATEMENT).


2. For information on how the source code maps to the statementnumber, see “Mapping OPM High-Level Language (HLL) Statementsto Source Code” on page 11-35.

Name The name of the program, module, and procedure associated with thisentry. If the report is summarized at the Module level, then the proce-dure will be left off. If the report is summarized at the Program level,then the module and the procedure names will be left off.

Statistics ReportThe Statistics Report provides general performance statistics to help identifyproblem areas. In partaicular, the statistics details show potential program perform-ance trouble spots of a job or system.

The report also shows a variety of other use statistics, such as invocations andnumber of disk I/Os. From the Statistics Report, you should be able to determinehow much resource the programs in your application are using. Using this informa-tion, you can determine if there is a performance problem that requires furtherinvestigation.

| If you notice a single library with a high level of CPU utilization or DASD I/O oper-| ations, you might want to focus on programs in that library. Libraries that you might| see could include the following:

| � QSYS, which stores most of the OS/400 modules.

| � QTCP, which provides TCP/IP support.

| � QIJS, which provides the Job Scheduler for OS/400 support.

| � QBRM, which provides the Backup Recovery and Media Services support.

See the “Library Information” on page 11-16 section for a discussion of the columndescriptions.


Performance Explorer Report

Statistics Information Page 6


Member. . . : STATSF

Job name. . : ALL JOBS/TASKS IN SESSION

Description : BLANK

+----------------- Inline Stats ------------++-------------- Cumulative Stats -----------+

Times Calls MI CPLX CPU DB DB NDB NDB CPU DB DB NDB NDB Call

Name Called Made Issued (us) / % SIO AIO SIO AIO (us) / % SIO AIO SIO AIO Level

----------------------------------------------------------------------------------------------------------------------------------

\\LIC Task ð ð ð 3,ð98,472 81.4 ð ð ð ð 3,ð98,472 81.4 ð ð ð ð ð

\\Unknown ð ð ð 399,295 1ð.5 ð ð ð ð 399,295 1ð.5 ð ð ð ð ð

\CRTS 9 ð ð 23,365 ð.6 ð ð 14 ð 23,365 ð.6 ð ð 14 ð ð

\DEQWAIT 1ð ð ð 22,5ð5 ð.6 ð ð 2 ð 22,5ð5 ð.6 ð ð 2 ð ð

\DESS 9 ð ð 13,7ð1 ð.4 ð ð 6 ð 13,7ð1 ð.4 ð ð 6 ð ð

\RSLVSP 37 ð ð 11,174 ð.3 ð ð ð ð 11,174 ð.3 ð ð ð ð ð

\MATPRMSG 68 ð ð 9,471 ð.2 ð ð ð ð 9,471 ð.2 ð ð ð ð ð

QWSPUT 23 6 26 9,157 ð.2 ð ð ð ð 15,3ð5 ð.4 ð ð ð ð ð

QSFPUT 15 1 ð 8,151 ð.2 ð ð ð ð 17,11ð ð.4 ð ð 3 ð ð

QMHRCVPM 24 3 115 7,611 ð.2 ð ð ð ð 71,841 1.9 ð ð 3 ð ð

QPTPRCSS 1 57 ð 7,591 ð.2 ð ð ð ð 66,ð43 1.7 ð ð 4 ð ð

\SETACST 2ð ð ð 7,517 ð.2 ð ð 6 2 7,517 ð.2 ð ð 6 2 ð

QYPEENDP 3 2ð 2ð 7,428 ð.2 ð ð 3 ð 142,7ð8 3.7 ð 2 4ð 4 ð

QMHGSD 6 48 24 7,192 ð.2 ð ð ð ð 6ð,865 1.6 ð ð 3 ð ð

\FNDINXEN 26 ð ð 7,174 ð.2 ð ð 1 ð 7,174 ð.2 ð ð 1 ð ð

QWSGET 17 9 17 7,ð99 ð.2 ð ð ð ð 34,884 ð.9 ð ð 2 ð ð

\SNDPRMSG 21 ð ð 6,886 ð.2 ð ð ð ð 6,886 ð.2 ð ð ð ð ð

QUIINMGR 6 12 ð 5,717 ð.2 ð ð ð ð 29,ð2ð ð.8 ð ð 2 ð ð

\MATPTR 1ð1 ð ð 5,462 ð.1 ð ð ð ð 5,462 ð.1 ð ð ð ð ð

\MODPRMSG 46 ð ð 5,251 ð.1 ð ð ð ð 5,251 ð.1 ð ð ð ð ð

QCAFLD 17 ð ð 4,976 ð.1 ð ð ð ð 4,976 ð.1 ð ð ð ð ð

QUIMGFLW 5 33 16 4,928 ð.1 ð ð ð ð 71,679 1.9 ð ð 7 ð ð

QLIDLOBJ 2 4 16 4,317 ð.1 ð ð 5 ð 17,ð39 ð.4 ð ð 13 ð ð

\MODS1 1ð ð ð 4,127 ð.1 ð ð ð ð 4,127 ð.1 ð ð ð ð ð

QUIEXFMT 6 23 3 4,ð44 ð.1 ð ð ð ð 5ð,525 1.3 ð ð 3 ð ð

\MATINVIF 135 ð ð 4,ðð2 ð.1 ð ð ð ð 4,ðð2 ð.1 ð ð ð ð ð

QUILIST 26 ð 8 3,885 ð.1 ð ð ð ð 4,449 ð.1 ð ð ð ð ð

QCMDEXC 4 22 18 3,571 ð.1 ð ð ð ð 3ð,858 ð.8 ð ð 3 ð ð

QCADRV2 11 4ð 1 3,439 ð.1 ð ð ð ð 16,1ð6 ð.4 ð ð ð ð ð

QMHSNDPM 1ð ð 43 3,239 ð.1 ð ð 1 ð 9,7ð1 ð.3 ð ð 1 ð ð

\MATSOBJ 2ð ð ð 3,ð66 ð.1 ð ð 1 ð 3,ð66 ð.1 ð ð 1 ð ð

QUIVPMGR 27 ð ð 2,933 ð.1 ð ð ð ð 2,933 ð.1 ð ð ð ð ð

QLICKOBJ 4 6 6 2,9ð7 ð.1 ð ð ð ð 11,398 ð.3 ð ð 2 ð ð

QCAPOS 7 ð ð 2,879 ð.1 ð ð ð ð 2,879 ð.1 ð ð ð ð ð

\MODADR 2 ð ð 2,838 ð.1 ð ð ð 2 2,838 ð.1 ð ð ð 2 ð

QWSSFLCT 5 ð ð 2,829 ð.1 ð ð ð ð 2,829 ð.1 ð ð ð ð ð

\REQIO 1ð ð ð 2,753 ð.1 ð ð ð ð 2,753 ð.1 ð ð ð ð ð

QUIOCNV 6 ð ð 2,736 ð.1 ð ð ð ð 2,736 ð.1 ð ð ð ð ð

QLIINSRT 2 1ð 28 2,645 ð.1 ð ð ð ð 27,4ð9 ð.7 ð 2 3 4 ð

\CRTDOBJ 1 ð ð 2,6ð5 ð.1 ð ð 1 ð 2,6ð5 ð.1 ð ð 1 ð ð

\LOCK 2ð ð ð 2,525 ð.1 ð ð ð ð 2,525 ð.1 ð ð ð ð ð

QMHRMVPM 14 ð 64 2,495 ð.1 ð ð ð ð 6,229 ð.2 ð ð ð ð ð

QSZGTPRD 4 6 18 2,484 ð.1 ð ð ð ð 8,3ðð ð.2 ð ð ð ð ð

QPTGTINP 3 12 6 2,226 ð.1 ð ð 1 ð 8,553 ð.2 ð ð 1 ð ð

QT3REQIO 13 ð 3ð 2,ð35 ð.1 ð ð ð ð 27,552 ð.7 ð ð 2 ð ð

Figure 11-9. *STATS Information

Profile ReportThe Profile Report provides output to show relative CPU time by procedure. Thisallows the user to identify where to focus efforts to provide overall performance ofthe application or program.

Note: You can also summarize profile counts at a procedure, module, or programlevel.

See the “Library Information” on page 11-16 section for a discussion of the columndescriptions.


| In this example, you can see that three statements were responsible for 71.75% of| the CPU costs. It would not be worthwhile to investigate other statements that| reported smaller percentages. In a real application program, the profile information| can show a high percentage of CPU cost for a single statement or similar percent-| ages for more than one statement. Look at the program source code to determine if| the high CPU cost is due to a single statement or a group of statements. A group| of statements can indicate a processing loop.

| Performance Explorer Report 1/21/97 13:39:1ð

| Profile Information Page 12

| Library . . : COOK

| Member. . . : RBPROF2PGM

| Description : RBPROF-CMDCSTPEXH (CLCSTPEXHI, CSTPEX)

| Histogram Hit Hit Cum Start Map Stmt Name

| Cnt % % Addr Flag Numb

| ----------------------------------------------------------------------------------------------------------------------------------

| \\\\\\\\\\\ 349 31.5 31.5 22B55B7DFDðð2E48 MP 45 CSTPEX

| \\\\\\\ 243 21.9 53.4 22B55B7DFDðð2DAð MP 42 CSTPEX

| \\\\\\ 2ð2 18.2 71.7 22B55B7DFDðð3E4ð MP 1ð6 CSTPEX

| \\ 82 7.4 79.1 22B55B7DFDðð2F2ð MP 46 CSTPEX

| \\ 81 7.3 86.4 22B55B7DFDðð2D6C MP 41 CSTPEX

| \ 53 4.8 91.2 22B55B7DFDðð3ECC MP 1ð7 CSTPEX

| \ 45 4.1 95.2 22B55B7DFDðð2E2C MP 44 CSTPEX

| 15 1.4 96.6 22B55B7DFDðð2F9ð MP 47 CSTPEX

| 1ð ð.9 97.5 22B55B7DFDðð3E38 MP 1ð5 CSTPEX

| 7 ð.6 98.1 22B55B7DFDðð2FAð MP 5ð CSTPEX

| 4 ð.4 98.5 22B55B7DFDðð236ð MP 7 CSTPEX

| 4 ð.4 98.8 22B55B7DFDðð25ðð MP 14 CSTPEX

| 2 ð.2 99.ð 22B55B7DFDðð23F4 MP 1ð CSTPEX

| 2 ð.2 99.2 22B55B7DFDðð2D48 MP 4ð CSTPEX

| 2 ð.2 99.4 22B55B7DFDðð31ðð MP 55 CSTPEX

| 2 ð.2 99.5 22B55B7DFDðð3288 MP 69 CSTPEX

| 2 ð.2 99.7 22B55B7DFDðð454C MP 128 CSTPEX

| 1 ð.1 99.8 3567AA4ð1Dðð24B8 MP 54ðð CLCSTPEXHI

| 1 ð.1 99.9 22B55B7DFDðð24Bð MP 13 CSTPEX

| 1 ð.1 1ðð.ð 22B55B7DFDðð2CCð MP 38 CSTPEX

| Figure 11-10. Example for *PROFILE Information

Trace ReportThe Trace Report provides a historical trace of performance activity generated byone or more jobs or tasks on the system.

Figure 11-11 on page 11-22 shows a sample Trace report.


572848

Performance Explorer Report

Trace Information Page 4


Member. . . : SFCALLRTN

Description : BLANK

Time Stamp. : 15.ð7.56.ð83ððð Task ID: ððððð9F5 Name: QPADEVððð4 FOLEY ð54858 Run Time (us): 484192 Percent: 84.52

P = Processor Number M = Missed Event Indicator Obj = Object Seg = Segment

T ST = Type Subtype NAGP = Non Access Group Pages NPgs = Number of Pages Unit = DASD Unit/Sub Unit

Sector = DASD Sector PI = Pool ID AI = ASP ID SKP = DASD Skip Operation

Span = DASD Sectors Spanned EXID = Exception ID IEID = IMPI Exception ID XCH = DASD Exchange

PTY = Apparent Task Priority WODSC = Wait Obj Description RS = Wait Obj Reason

PREFIX = S: Stealable Page PREFIX = A: PAG Data PREFIX = D: Data Base Data PREFIX = M: Mirrored DASD

PREFIX = P: Permanent Segment PREFIX = T: Temporary Segment PREFIX = E: E=R Address

Address Offset Object Name Obj Seg PRE NPgs LIC-Pgm--Offset MI-Pgm-----Offset NAGP PI AI

T ST T ST FIX Unit Sector Span SKP XCH EXID IEID

ss.mmm P M Task ID Parent-Pgm HLL-No CurrentPgm RC Delta Run Cycles Event PTY WaitSleep Cycles WODSC RS SNDTSK

----------------------------------------------------------------------------------------------------------------------------------

56.ð83 7 ð ððððð9F5 QMHSNDPM ððð15F \RSLVSP ð ð MISTR RESOLVE SYSTEM POINTER

56.ð83 7 ð ððððð9F5 QMHSNDPM ððð16ð \RSLVSP ð ð MIEND RESOLVE SYSTEM POINTER

56.ð83 7 ð ððððð9F5 QMHSNDPM ððð164 \RSLVSP ð ð MISTR RESOLVE SYSTEM POINTER

56.ð83 7 ð ððððð9F5 QMHSNDPM ððð165 \RSLVSP ð ð MIEND RESOLVE SYSTEM POINTER

56.ð83 7 ð ððððð9F5 QMHSNDPM ððð167 \TESTAU ð ð MISTR TEST AUTHORITY

56.ð83 7 ð ððððð9F5 QMHSNDPM ððð167 \TESTAU ð ð MIEND TEST AUTHORITY

56.ð83 7 ð ððððð9F5 QMHSNDPM ððð17E \FNDINXEN ð ð MISTR FIND INDEPENDENT INDEX ENTRY

56.ð83 7 ð ððððð9F5 QMHSNDPM ððð17F \FNDINXEN ð ð MIEND FIND INDEPENDENT INDEX ENTRY

56.ð83 7 ð ððððð9F5 QMHSNDPM ððð491 \MATINVIF ð ð MISTR MATERIALIZE INVOCATION INFO.

56.ð83 7 ð ððððð9F5 QMHSNDPM ððð492 \MATINVIF ð ð MIEND MATERIALIZE INVOCATION INFO.

56.ð83 7 ð ððððð9F5 QMHSNDPM ððð2ðF \MATINVIF ð ð MISTR MATERIALIZE INVOCATION INFO.

56.ð83 7 ð ððððð9F5 QMHSNDPM ððð21ð \MATINVIF ð ð MIEND MATERIALIZE INVOCATION INFO.

56.ð83 7 ð ððððð9F5 QMHSNDPM ððð6AD \SNDPRMSG ð ð MISTR SEND PROCESS MESSAGE

56.ð84 7 ð ððððð9F5 QMHSNDPM ððð6AE \SNDPRMSG ð ð MIEND SEND PROCESS MESSAGE

56.ð84 7 ð ððððð9F5 QMHSNDPM ð ð EXIT

56.ð84 7 ð ððððð9F5 QYPESTRP ð ð EXIT QYPESTRP/_CXX_PEP

56.ð84 7 ð ððððð9F5 QCMD ððð182 \TESTEXCP ð ð MISTR TEST EXCEPTION

56.ð84 7 ð ððððð9F5 QCMD ððð182 \TESTEXCP ð ð MIEND TEST EXCEPTION

56.ð84 7 ð ððððð9F5 QMHRCVPM ð ð ENTRY

56.ð84 7 ð ððððð9F5 QMHRCVPM ððð4CC \MATPRMSG ð ð MISTR MATERIALIZE PROCESS MESSAGE

56.ð84 7 ð ððððð9F5 QMHRCVPM ððð4CD \MATPRMSG ð ð MIEND MATERIALIZE PROCESS MESSAGE

56.ð84 7 ð ððððð9F5 QMHRCVPM ððð4E3 \MATINVIF ð ð MISTR MATERIALIZE INVOCATION INFO.

56.ð84 7 ð ððððð9F5 QMHRCVPM ððð4E4 \MATINVIF ð ð MIEND MATERIALIZE INVOCATION INFO.

56.ð84 7 ð ððððð9F5 QMHRCVPM ðððð36 \MATPRMSG ð ð MISTR MATERIALIZE PROCESS MESSAGE

56.ð84 7 ð ððððð9F5 QMHRCVPM ðððð37 \MATPRMSG ð ð MIEND MATERIALIZE PROCESS MESSAGE

56.ð84 7 ð ððððð9F5 QMHRCVPM ððð44C \MATINVIF ð ð MISTR MATERIALIZE INVOCATION INFO.

56.ð84 7 ð ððððð9F5 QMHRCVPM ððð44D \MATINVIF ð ð MIEND MATERIALIZE INVOCATION INFO.

56.ð84 7 ð ððððð9F5 QMHGSD ð ð ENTRY

56.ð84 7 ð ððððð9F5 QMHGSD ððð827 \MATPRMSG ð ð MISTR MATERIALIZE PROCESS MESSAGE

56.ð84 7 ð ððððð9F5 QMHGSD ððð828 \MATPRMSG ð ð MIEND MATERIALIZE PROCESS MESSAGE

56.ð84 7 ð ððððð9F5 QUIVPMGR ð ð ENTRY

56.ð84 7 ð ððððð9F5 QUIVPMGR ð ð EXIT

56.ð84 7 ð ððððð9F5 QUIVPMGR ð ð ENTRY

56.ð84 7 ð ððððð9F5 QUIVPMGR ð ð EXIT

56.ð84 7 ð ððððð9F5 QUILIST ð ð ENTRY

56.ð84 7 ð ððððð9F5 QUILIST ð ð EXIT


56.ð84 7 ð ððððð9F5 QMHGSD ððð81A \MATPRMSG ð ð MIEND MATERIALIZE PROCESS MESSAGE


56.ð84 7 ð ððððð9F5 QMHGSD ððð81A \MATPRMSG ð ð MIEND MATERIALIZE PROCESS MESSAGE

Figure 11-11. Trace Information Report

The Trace Report shows the following values:




Time stamp The full time of day delta from the start of the session for the firstevent on each page of the report.


Task ID The task ID (in hexadecimal) of the events on each page.

Note: This information appears only when the sort by *TASK value isspecified on the PRTPEXRPT command.

Name The name of the task associated with the events on each page.


Run Time (us) The total run time in microseconds of the task associated with theevents on each page.


Percent The percent value of the total run time of the task associated with theevents on each page.


ss.mmm The number of seconds.milliseconds of the event from the start of thesession.

P (Processor Number) The number of the processor.

M Missed event indicator. Events are missing because of the following:

B The collection mechanism overloaded.

U The collection mechanism is not available.

* Unknown reasons.

Task ID The task ID (in hexadecimal) of the task responsible for the event.

Program The name of the program associated with the event.

HLL-No The high-level language statement number (in hexadecimal) of theprogram where the MI complex instruction was issued.

CurrentPgm The name of the MI complex instruction or program associated withthe event.

RC Delta The difference between the current event run cycle value and the pre-vious event run cycle value.

Run Cycles The run cycle value for the event. Run cycles are the number of non-idle CPU cycles and are accumulated on a per job or task basis.

Event The 5-character event abbreviation that identifies what event occurred.

In addition to the previous columns that are shown for the Trace Report, you seethe following columns when you specify the TRCTYPE parameter.

Address Offset The hexadecimal representation of an address associated with theevent.

Object Name The name of the object associated with the event.

Obj T ST The object type and subtype (in hexadecimal) of the object associatedwith the event.


Seg T ST The segment type and subtype (in hexadecimal) of the address associ-ated with the event.

PREFIX Character flags that give more detail of the object associated with theevent.

S Stealable page

A PAG data

D Database data

M Mirrored DASD

P Permanent segment

T Temporary segment

E E=R address

NPgs The number of pages requested by the event.

LIC-Pgm--Offset The Licensed Internal Code (LIC) program identifier and instruc-tion offset associated with the event.

MI-Pgm Offset The program name and instruction offset associated with the event.

NAGP The number of non-activation group pages requested by the event.

PI The pool identifier associated with the event.

AI The auxiliary storage pool identifier associated with the event.

Unit The DASD unit number subunit number (in hexadecimal).

Sector The DASD sector address associated with the event.

Span The span of the DASD request associated with the event.

SKP XCH Y/N columns indicating whether the DASD event was a skip operation oran exchange operation.

EXID Exception identifier column (in hexadecimal).

IEID IMPI Exception identifier column (in hexadecimal).

| Trace Event Descriptions: The following tables describe each event available| when you specify SLTEVT(*YES) on the ADDPEXDFN command. The tables also| indicate the relationships between the TRCTYPE parameter and the events that are| included in the performance explorer definition.

| The data that is collected for the BASE events are placed in the QAYPEDTIDX and| QAYPEBASE files.

| Table 11-2 (Page 1 of 3). BASE event descriptions

| Event| TRCTYPE| Description

| PRCCRT| Process Create. An event is generated whenever an| AS/400 process is created during an active perform-| ance explorer collection session.

| PRCDLT| Process Delete. An event is generated whenever an| AS/400 process ends during an active performance| explorer collection session.




| TASKCRT| Task Create. An event is generated whenever an| AS/400 SLIC task is created during an active perform-| ance explorer collection session.

| TASKDLT| Task Delete. An event is generated whenever an| AS/400 SLIC task ends during an active performance| explorer collection session.

| TASKSWTIN| *TASKSWT| Task Switch In. An event is generated whenever an| AS/400 task is switched in and given processor time| during an active performance explorer collection| session.

| TASKSWTOUT| *TASKSWT| Task Switch Out. An event is generated whenever an| AS/400 task is switched out from the processor, due to| time-slice end, during an active performance explorer| collection session.

| PMCO| ALL TRCTYPES| Performance Measurement Counter Overflow. An| event is generated whenever this hardware counter| overflows during an active performance explorer col-| lection session. This hardware counter is used in con-| junction with the Sample rate parameter and can be| programmed to overflow and generate an event at the| specified sample rate interval.

| TASKSWTOUTQ| *TASKSWT| Task Switch Out Queueing. An event is generated| whenever an AS/400 task is switched out from the| processor, due to a lock condition, during an active| performance explorer collection session.

| TASKSWTOUTINT| *TASKSWT| Task Switch Out Interrup. An event is generated when-| ever an AS/400 task is switched out from the| processor, due to an interrupt, during an active per-| formance explorer collection session.

| TASKAVAIL| *TASKSWT| Task Available for Dispatch. An event is generated| whenever an AS/400 task is available to be dispatch to| the processor during an active performance explorer| collection session.

| ACTGRPACTPGM| *BASIC, *PGMACT| Activation Group Activate Program. An event is gener-| ated whenever an ILE program activation begins| during an active performance explorer collection| session.

| ACTGRPCRT| *BASIC, *PGMACT| Activation Group Create. An event is generated when-| ever an ILE program activation group is created during| an active performance explorer collection session.

| ACTGRPDLT| *BASIC, *PGMACT| Activation Group Delete. An event is generated when-| ever an ILE program activation group is destroyed| during an active performance explorer collection| session.

| EXCP| Exception. An event is generated whenever an excep-| tion occurs during an active performance explorer col-| lection session.

| MIEXCP| Mi Exception. An event is generated whenever an MI| exception occurs during an active performance| explorer collection session.




| EXTINTSTR| External Interrupt Start. An event is generated when-| ever a start of an external interrrupt occurs during an| active performance explorer collection session.

| EXTINTEND| External Interrupt End. An event is generated when-| ever an end of an external interrupt occurs during an| active performance explorer collection session.

| DCRINTSTR| Decrement Interrupt Star. An event is generated when-| ever a start of a decrement interrupt occurs during an| active performance explorer collection session.

| DCRINTEND| Decrement Interrupt End. An event is generated when-| ever an end of a decrement interrupt occurs during an| active performance explorer collection session.

| PGMDBG| *BASIC| Program Debug. This event is activated through the| Dedicated Service Tools (DST) interface

| Auxilary storage management (ASM) is responsible for the management of the| segment spaces for the single-level storage model of the AS/400.

| The data that is collected for the ASM events are placed in the QAYPETIDX and| QAYPEASM files.

| Table 11-3. Auxiliary storage management event descriptions


| CRTSEG| *BASIC, *DSKSTG, *VRTADR| Create Segment. An event is generated when-| ever a segment is created during an active per-| formance explorer collection session.

| DLTSEG| *BASIC, *DSKSTG| Destroy Segment. An event is generated when-| ever a segment is destroyed during an active| performance explorer collection session.

| EXDSEG| *BASIC, *DSKSTG| Extend Segment. An event is generated when-| ever a segment is extended during an active| performance explorer collection session.

| FNDSEGSIZ| *BASIC, *DSKSTG| Find Segment Size. An event is generated| whenever a request to find the segment size| occurs during an active performance explorer| collection session.

| TRUNCSEG| *BASIC, *DSKSTG| Truncate Segment. An event is generated| whenver a segment is truncated during an active| performance explorer collection session.

| Disk events trace I/O activity with the disk storages devices of the AS/400.

| The data that is collected for the Disk events are placed in the QAYPETIDX and| QAYPEDASD files.


| Table 11-4. Disk event descriptions


| READSTR| *BASIC, *DSKIO1, *DSKIO2,| *TASKSWT| Read Start. An event is generated whenever a| start of a physical read occurs during an active| performance explorer collection session.

| READEND| *DSKIO1, *DSKIO2, *TASKSWT| Read End. An event is generated whenever a| complete of a physical read occurs during an| active performance explorer collection session.

| WRTSTR| *BASIC, *DSKIO1, *DSKIO2,| *TASKSWT| Write Start. An event is generated whenever a| start of a physical write occurs during an active| performance explorer collection session.

| WRTEND| *DSKIO1, *DSKIO2, *TASKSWT| Write End. An event is generated whenever a| complete of a physical write occurs during an| active performance explorer collection session.

| PGREADSTR| Page Read Start. An event is generated when-| ever a start of a page read occurs during an| active performance explorer collection session.

| PGREADEND| Page Read End. An event is generated when-| ever a complete of a page read occurs during| an active performance explorer collection| session.

| PGWRTSTR| Page Write Start. An event is generated when-| ever a start of page write occurs during an| active performance explorer collection session.

| PGWRTEND| Page Write End. An event is generated when-| ever a complete of a page write occurs during| an active performance explorer collection| session.

| A page fault occurs whenever an address is referred to and is not in the main| storage of the AS/400 system.

| The data that is collected for the page fault events are placed in the QAYPETIDX| and QAYPEPGFLT files.

| Table 11-5. Page fault event descriptions


| STR| *BASIC, *DSKIO2| Start of Fault. An event is generated whenever a start| of a page fault occurs during an active performance| explorer collection session.

| ENDOK| End of Fault: OK. An event is generated whenever a| successful completion of a page fault occurs during an| active performance explorer collection session.

| ENDERR| End of Fault: Error. An event is generated whenever| an unsuccesful completion of a page fault occurs| during an active performance explorer collection| session.

| The mangagement of the MI interrupts are for the jobs or processes running on the| AS/400 system


| The data that is collected for the RMPM events are placed in the QAYPETIDX and| QAYPERMPM files.

| Table 11-6. Job or Process Events


| LWSTR| Machine Interface Long Wait Start. An event is gener-| ated whenever a start of a long wait occurs during an| active performance explorer collection session.

| LWEND| Machine Interface Long Wait End. An event is gener-| ated whenever a completion of a long wait occurs| during an active performance explorer collection| session.

| INELIGIBLE| Machine Interface Process Ineligible. An event is gen-| erated whenever a process moves from active state to| ineligible during an active performance explorer col-| lection session.

| ACTIVE| Machine Interface Process Active. An event is gener-| ated whenever a process moves from ineligible or wait| to active during an active performance explorer col-| lection session.

| INTERRUPT| Machine Interface Process Interrupt. An event is gen-| erated whenever a process interrupt occurs during an| active performance explorer collection session.

| MPLPOOLCHG| Machine Interface MPL Pool Change. An event is gen-| erated whenever the MPL pool changes during an| active performance explorer collection session.

| TOBCHMPLPOOL| Machine Interface Process To Batch MPL Pool. An| event is generated whenever an MI process is being| implicitly moved to the batch MPL pool defined for it| during an active performance explorer collection| session.

| TSLEND| Machine Interface Timeslice End. An event is gener-| ated whenever a process timeslice end occurs during| an active performance explorer collection session.

| The mangagement of the seizes and locks used for resource serialization that| occurr on the AS/400 system.

| The data that is collected for the RMSL events are placed in the QAYPETIDX and| QAYPERMSL files.

| Table 11-7. Seize Lock Events


| LWEND| Sieze Lock Long Seize Wait End. An event is gener-| ated whenever a long seize wait completes during an| active performance explorer collection session.

| The SAR events (give description here)

| The data that is collected for the SAR events are placed in the QAYPETIDX and| QAYPESAR files.


| Table 11-8 (Page 1 of 2). Segment Address Register Events


| CLR| *BASIC| Clear. An event is generated whenever a storage| clear operation is requested during an active perform-| ance explorer collection session.

| CLRPIN| *BASIC| Clear Pin. An event is generated whenever a storage| clear and pin operation is requested during an active| performance explorer collection session.

| EXCHCLR| *BASIC| Exchange Clear. An event is generated whenever a| storage exchange and clear operation is requested| during an active performance explorer collection| session.

| READ| *BASIC, *DSKIO2| Read. An event is generated whenever a storage| read operartion is requested during an active perform-| ance explorer collection session.

| READASYNC| *BASIC, *DSKIO2| Read Asynchronous. An event is generated whenever| a storage asynchronous read operartion is requested| during an active performance explorer collection| session.

| READASYNCCALL| *BASIC, *DSKIO2| Read Asynchronous Track Call. An event is gener-| ated whenever the storage manangement read asyn-| chronous tracked by a call function is accessed| during an active performance explorer collection| session.

| READPIN| *BASIC, *DSKIO2| Read Pin. An event is generated whenever a storage| read and pin operation is requested during an active| performance explorer collection session.

| EXCHREAD| *BASIC, *DSKIO2,| *FILEOPEN| Exchange Read. An event is generated whenever a| storage exchange read operation is requested during| an active performance explorer collection session.

| EXCHREADASYNC| *BASIC, *DSKIO2| Exchange Read Asynchronous. An event is generated| whenever a storage asynchronous exchange read| operation is requested during an active performance| explorer collection session.

| EXCHREAD-| ASYNCCALL| *BASIC, *DSKIO2| Exchange Read Asynchronous Track Call. An event| is generated whenever the storage manangement| exchange read asynchronous tracked by a call func-| tion is accessed during an active performance| explorer collection session.

| WRT| *BASIC, *DSKIO2| Write. An event is generated whenever a storage| write operation is requested during an active perform-| ance explorer collection session.

| WRTASYNC| *BASIC, *DSKIO2| Write Asynchronous. An event is generated whenever| a storage asynchronous write operation is requested| during an active performance explorer collection| session.

| WRTASYNCCALL| *BASIC, *DSKIO2| Write Asynchronous Track Call. An event is gener-| ated whenever the storage manangement write asyn-| chronous tracked by a call function is accessed| during an active performance explorer collection| session.


| Table 11-8 (Page 2 of 2). Segment Address Register Events


| WRTASYNCMSGQ| *BASIC, *DSKIO2| Write Asynchronous Track Message Queue. An event| is generated whenever the storage manangement| write asynchronous function is accessed during an| active performance explorer collection session.

| WRTASYNC-| MSGQLAST| *BASIC, *DSKIO2| Write Asynchronous Track Message QueueLast. An| event is generated whenever the storage| manangement write last asynchronous tracked by a| call is requested during an active performance| explorer collection session.

| WRTASYNCTASK| *DSKIO2| Write Asynchronous Track Task. An event is gener-| ated whenever the storage manangement write last| asynchronous tracked by the current task is| requested during an active performance explorer col-| lection session.

| WRTASYNCWAIT| Write Asynchronous Track Wait. An event is gener-| ated whenever the storage manangement write asyn-| chronous tracked by is requested during an active| performance explorer collection session.

| WRTRMV| *BASIC, *DSKIO2| Write Remove. An event is generated whenever a| storage write remove operation is requested during an| active performance explorer collection session.

| WRTPGOUT| *BASIC, *DSKIO2| Write For Page Out. An event is generated whenever| a storage write for page out operation is requested| during an active performance explorer collection| session.

| RMV| *BASIC| Remove. An event is generated whenever a storage| remove operation is requested during an active per-| formance explorer collection session.

| UNPIN| *BASIC| Unpin. An event is generated whenever a storage| unpin operation is requested during an active per-| formance explorer collection session.

| UNPINRMV| *BASIC| Unpin Remove. An event is generated whenever a| storage unpin remove operation is requested during| an active performance explorer collection session.

| UNPINWRT| *BASIC, *DSKIO2| Unpin Write. An event is generated whenever a| storage unpin write operation is requested during an| active performance explorer collection session.

| ENDOK| End of SAR event: OK. An event is generated when-| ever any specified SAR event completes successfully| during an active performance explorer collection| session.

| ENDERR| End of SAR event: Error. An event is generated| whenever any specified SAR event completes with an| error during an active performance explorer collection| session.

| STRASYNCTASK| Start Asynchronous Task. An event is generated| whenever during an active performance explorer col-| lection session.

| The DASD server events (give descriptions here)


| The data that is collected for the DASD server events are placed in the| QAYPETIDX and QAYPEDSRV files.

| Table 11-9. DASD Server Events


| CTLEND| *DSKSVR| Control End. An event is generated whenever a| server request to create or destroy session completes| during an active performance explorer collection| session.

| RQSACP| *DSKSVR| Request Accepted. An event is generated whenever| a server function request is accepted and will be| handled by a server task during an active perform-| ance explorer collection session.

| RQSRJT| *DSKSVR| Request Rejected. An event is generated whenever a| server function request is rejected because of an| error during an active performance explorer collection| session.

| SVRTASKSTR| *DSKSVR| Server Task Started. An event is generated whenever| a server task is created and is ready to process| requests during an active performance explorer col-| lection session.

| SVRTASKEND| *DSKSVR| Server Task Ended. An event is generated whenever| a server task is ended and will be removed from the| system during an active performance explorer col-| lection session.

| RQSRCV| *DSKSVR| Request Received. An event is generated whenever| a server task receives a request for work (read or| write) during an active performance explorer col-| lection session.

| RQSENDOK| *DSKSVR| Request Ended OK. An event is generated whenever| a server task completes the request with no errors| during an active performance explorer collection| session.

| RQSENDERR| *DSKSVR| Request Ended Error. An event is generated when-| ever a server task encounters an error while proc-| essing a request during an active performance| explorer collection session.

| Program bracket events trace the call flow of programs and procedures as well as| MI complex instructions. These events give information on when programs, proce-| dures and MI complex instruction are entered into (or called) and exited from (or| returned).

| The data that is collected for the dasd server events are placed in the QAYPETIDX| and QAYPEMBRKT files.

| Table 11-10 (Page 1 of 2). Program bracket events


| MIENTRY| *CALLRTN, *FILEOPEN,| *PGMACT| Entry. An event is generated whenever a program| or procedure that is enabled for performance col-| lection is entered or called during an active per-| formance explorer collection session.


| Table 11-10 (Page 2 of 2). Program bracket events


| MIEXIT| *CALLRTN, *FILEOPEN,| *PGMACT| Exit. An event is generated whenever a program| or procedure that is enabled for performance col-| lection exits or returns during an active perform-| ance explorer collection session.

| MISTR| *CALLRTN, *PGMACT| Machine Interface Instruction Start. An event is| generated whenever an MIcomplex instruction is| routed to or from a program during an active per-| formance explorer collection session.

| MIEND| *CALLRTN, *PGMACT| Machine Interface Instruction End. An event is| generated whenever an MI complex instruction| completes and returns to the program during an| active performance explorer collection session.

| MIPRECALL| Pre Call. An event is generated whenever a| program or procedure that is enabled for perform-| ance collection calls externally to another program| or procedure during an active performance| explorer collection session.

| MIPOSTCALL| Post Call. An event is generated whenever a| program or procedure that is enabled for perform-| ance collection has been returned to from an| external call to another program or procedure| during an active performance explorer collection| session.

| JVAENTRY| Java Entry. An event is generated whenever a| Java method is called during an active perform-| ance explorer collection session.

| JVAEXIT| Java Exit. An event is generated whenever a Java| method is returned from during an active perform-| ance explorer collection session.

| JVAPRECALL| Java Precall. An event is generated whenever a| Java method is about to call out some other func-| tion during an active performance explorer col-| lection session.

| JVAPOSTCALL| Java Postcall. An event is generated whenever a| Java method is returned from some other function| during an active performance explorer collection| session.

| JVANTVMTHSTR| Java Native Method Start. An event is generated| whenever a Java method calls an AS/400 method| during an active performance explorer collection| session.

| JVANTVMTHEND| Java Native Method End. An event is generated| whenever a Java method returns from an AS/400| method during an active performance explorer| collection session.

| Java events describe activity occurring in the Java virtual machine of the AS/400| system.

| The data that is collected for the DASD server events are placed in the| QAYPETIDX and QAYPEJAVA files.


| Table 11-11 (Page 1 of 2). Java events


| OBJCRT| Java object create. An event is generated whenever a| Java object instance is created during an active per-| formance explorer collection session.

| GBGCOL| Java garbage collection. An event is generated when-| ever Java is doing garbage collection during an active| performance explorer collection session.

| GBGCOLSWEEP| Java garbage collection sweep. An event is generated| whenever the garbage collection sweep completes| during an active performance explorer collection| session.

| THDCRT| Java thread create. An event is generated whenever a| Java thread is created during an active performance| explorer collection session.

| THDDLT| Java thread delete. An event is generated whenever a| Java thread is destructed during an active perform-| ance explorer collection session.

| THDSSP| Java thread suspend. An event is generated when-| ever a Java thread or thread group suspend is started| during an active performance explorer collection| session.

| THDRSM| Java thread resume - An event is generated when-| ever a java thread or thread group is resumed during| an active performance explorer collection session.

| THDWAIT| Java thread wai. An event is generated whenever an| Object::wait() used for thread synchronization is| started during an active performance explorer col-| lection session.

| THDNFY| Java thread notify. An event is generated whenever| an Object::notify() used for thread synchronization is| started during an active performance explorer col-| lection session.

| THDNFYALL| Java thread notify all. An event is generated when-| ever an Object::notifyAll() used for thread synchroniza-| tion is started during an active performance explorer| collection session.

| THDSTTCHG| Java thread state change. An event is generated| whenever a method that causes a thread state transi-| tion (for example, a thread block) is started during an| active performance explorer collection session.

| CLSLOAD| Java class load. An event is generated whenever a| Java class is loaded during an active performance| explorer collection session.

| CLSUNLOAD| Java class unload. An event is generated whenever a| Java class is unloaded during an active performance| explorer collection session.

| LIBOPR| Java class library operation. An event is generated| whenever a Java native method library is loaded or| unloaded during an active performance explorer col-| lection session.


| Table 11-11 (Page 2 of 2). Java events


| TFMSTR| Java transform start. An event is generated whenever| a Java program object generation step is started| during an active performance explorer collection| session.

| LCKSTR| Java lock. An event is generated whenever a synchro-| nize lock is requested during an active performance| explorer collection session.

| UNLCK| Java unlock. An event is generated whenever a syn-| chronize lock is released during an active perform-| ance explorer collection session.

| JVAEND| Java end. An event is generated whenever a previous| Java event is completed during an active performance| explorer collection session.

| Table 11-12. Selected MI complex instructions

| MI INST| TRCTYPE| Description

| *REQIO| *BASIC| Request IO complex MI

| *SNSEXCPD| *BASIC| Sense exception description

| *DEQ| *BASIC| Dequeue

| *ENQ| *BASIC| Enqueue

| *WAITEVT| *BASIC| Wait on event

| *RETEVTD| *BASIC| Retrieve event data

| *SUSPR| *BASIC| Suspend process

| *TERMPR| *BASIC| Terminate process

| *INITPR| *BASIC| Initiate process

| *RESPR| *BASIC| Resume process

| *SIGEVT| *BASIC| Signal event

| *UNLOCKSL| *BASIC| Unlock space location

| *LOCK| *BASIC| Lock object

| *LOCKSL| *BASIC| Lock space location

| *UNLOCK| *BASIC| Unlock object

| *DEQWAIT| *BASIC| Dequeue wait

| *DEACTPG| *BASIC, *PGMACT| De-activate program

| *DESAGP| *BASIC, *PGMACT| Destroy activation group

| Basic Report| The Basic Report provides summary information that includes the definition, run,| and task information sections for any of the previous types.


Mapping OPM High-Level Language (HLL) Statements to Source CodeNon-ILE compiled original program model (OPM) program HLL statements thatappear in the PRTPEXRPT *PROFILE report do not map the code source state-ments. To do the mapping, these programs need to be compiled with the *LISTgeneration option.

Note: This mapping only applies to the OPM compilers.

The HLL statements that appear in the report have to be converted to hexadecimaland matched up with the INST column in the Generated Output section of thecompile listing. The values under the Break column of the same section map thesource statement numbers of the program.

For example, the following CL program results in a partial listing as shown inFigure 11-12 on page 11-36:

CRTCLPGM PGM(QGPL/CLEXAMPLE)

SRCFILE(QGPL/QCLSRC) GENOPT(\LIST)

| To determine the actual source code statement numbers, do the following steps:

| 1. Compile the original program model (OPM) program with an *LIST generation| option. This listing includes the original HLL source statement numbers and the| corresponding MI instructions that were generated for this HLL statement.| These MI instructions are assigned their own INSTruction number on the listing.

| 2. Collect data that includes the OPM program.

| 3. Print the report by specifying:

| PRTPEXRPT TYPE(\PROFILE) PROFILEOPT(\SAMPLECOUNT \STATEMENT)

| 4. Find the highest count statement number for the OPM program and convert the| number to its corresponding hexadecimal value. For example, decimal 241 is| hexadecimal F1 ((F15 *16) + 1.

| 5. Scan the MI statement portion of the listing (Generate Output section) to find| the hexadecimal instruction number under the column heading INST. On the| right side of that same print line you see the HLL source statement number| under the Break column heading. Two lines before the matched INST line you| see BRK 'HLL source statement number' .

| 6. Find that statement number in your original source portion of the listing.


Control Language Source

SEQNBR \...+... 1 ...+... 2 ...+... 3 ...+... 4 ...+... 5 ...+... 6 ...+... 7 ...+... 8 ...+... 9 ...+. DATE

1ðð- /\------------------------------------------------------------------\/

2ðð- /\ Program : LOOPCL \/ ð8/27/95

3ðð- /\ \/

4ðð- /\ Example invocation : \/

5ðð- /\ \/

6ðð- /\ CALL QGPL/LOOPCL \/ ð8/27/95

7ðð- /\ \/

8ðð- /\ \/

9ðð- /\ \/

1ððð- /\ Parameters : none \/

11ðð- /\------------------------------------------------------------------\/

12ðð-

13ðð- PGM:

14ðð- DCL &LOOPCNT \DEC LEN(5 ð) VALUE(1ðððð) ð8/12/95

15ðð- DCL &VAR1 \DEC LEN(5 ð) VALUE(ð) ð8/27/95

16ðð- /\------------------------------------------------------------------\/

17ðð- /\ SIMPLE LOOP WITH SOME MATH COMPUTATIONS \/ ð8/27/95

18ðð- /\ \/ ð8/27/95

19ðð- /\------------------------------------------------------------------\/

2ððð- LOOP: ð7/28/95

21ðð- IF COND(&LOOPCNT \NE ð) THEN(DO) ð8/23/95

22ðð- CHGVAR VAR(&VAR1); VALUE(&LOOPCNT \ &VAR1); ð8/27/95

23ðð- CHGVAR VAR(&VAR1); VALUE(&VAR1 / &LOOPCNT); ð8/27/95

24ðð- CHGVAR &LOOPCNT (&LOOPCNT - 1) ð7/28/95

25ðð- GOTO LOOP ð7/28/95

26ðð- ENDDO ð7/28/95

27ðð- END:

\ \ \ \ \ E N D O F S O U R C E \ \ \ \ \

Figure 11-12 (Part 1 of 2). Mapping Control Language Source to Statement Numbers


5716SS1 V3R6Mð 95ð929 Generated Output ð8/27/95 11:25:31 Page 3

SEQ INST Offset Generated Code \... ... 1 ... ... 2 ... ... 3 ... ... 4 ... ... 5 ... ... 6 ... ... 7 ... ... 8 Break

ðððð1 ENTRY \ EXT ;

ðððð2 ððð1 ððððð4 2132 ðð25 ðð26 CPYBWP ?WCLSEPT@,?WWCBSEPT ;

ðððð3 ððð2 ðððððA ð132 ðð21 4ð27 213A CPYBWP ?QCLCLNUP,?WWLISEPT(ðð314) ;

ðððð4 ððð3 ðððð12 ð252 ðð21 ðð4A SETIEXIT ?QCLCLNUP,?WCLRARGLST ;

ðððð5 ððð4 ðððð18 ð283 4ð27 213C ðð4A CALLX ?WWLISEPT(ðð316),?WCLRARGLST,\ ;

ðððð

ðððð6 DCL DD ?CLPVARS(ððððððð7) CHAR(1) AUTO ;

ðððð7 BRK 'PGM ' ; PGM

ðððð8 PGM : ; PGM

ðððð9 BRK 'LOOP ' ; LOOP

ððð1ð LOOP : ; LOOP

ððð11 ððð5 ðððð22 23EF ðð1A ðð18 2ðð1 MODEXCPD ?FCEXCMON,?EMEMONAT,X'ð1' ; LOOP

ððð12 BRK '21ðð ' ; 21ðð

ððð13 ?RCLBLðððð1: ; 21ðð

ððð14 ððð6 ðððð2A 3ð42 ðð31 2ðð1 CPYNV ?WCLCSREI ,ðððð1 ; 21ðð

ððð15 ððð7 ðððð3ð 1846 Cððð ðð13 ððð6 CMPNV(I) &LOOPCNT,P'+ð'/NEQ(?4TEMPððð1); ; 21ðð

ðð16 21ðð

ððð16 ððð8 ðððð3A 1CC2 Cððð ðð16 2ðF1 CMPBLA(B) ?4TEMPððð1 ,C'1'/NEQ(?FLðððð1) ; 21ðð

ðð1ð 21ðð



ððð19 ððð9 ðððð44 3ð42 ðð31 2ðð2 CPYNV ?WCLCSREI ,ðððð2 ; 22ðð

ððð2ð ðððA ðððð4A 1ð4B ðð17 ðð13 ðð14 MULT ?4TEMPððð2,&LOOPCNT,&VAR1 ; 22ðð

ððð21 ðððB ðððð52 1ð42 ðð14 ðð17 CPYNV &VAR1 ,?4TEMPððð2 ; 22ðð

ððð22 ?ICLBLðððð2: ; 22ðð



ððð25 ðððC ðððð58 3ð42 ðð31 2ðð3 CPYNV ?WCLCSREI ,ðððð3 ; 23ðð

ððð26 ðððD ðððð5E 1ð4F ðð17 ðð14 ðð13 DIV ?4TEMPððð2,&VAR1,&LOOPCNT ; 23ðð

ððð27 ðððE ðððð66 1ð42 ðð14 ðð17 CPYNV &VAR1 ,?4TEMPððð2 ; 23ðð



ððð3ð ?RCLBLðððð4: ; 24ðð

ððð31 ðððF ðððð6C 3ð42 ðð31 2ðð4 CPYNV ?WCLCSREI ,ðððð4 ; 24ðð

ððð32 ðð1ð ðððð72 1ð47 ðð17 ðð13 ðððC SUBN ?4TEMPððð2,&LOOPCNT,P'+1'; ; 24ðð

ððð33 ðð11 ðððð7A 1ð42 ðð13 ðð17 CPYNV &LOOPCNT ,?4TEMPððð2 ; 24ðð



ððð36 ðð12 ðððð8ð 3ð11 ððð4 B LOOP ; 25ðð


ððð38 BRK 'END ' ; END

ððð39 END : ; END

ððð4ð BRK '27ðð ' ; 27ðð


Figure 11-12 (Part 2 of 2). Mapping Control Language Source to Statement Numbers



Chapter 12. Managing the Performance Tools Configuration

For the Manager feature, if you choose the Configure and manage tools option onthe IBM Performance Tools menu, the Configure and Manage Tools displayappears.

à ðConfigure and Manage Tools


1. Work with functional areas

2. Delete performance data

3. Copy performance data

4. Convert performance data


===> _____________________________________________________________________

__________________________________________________________________________


á ñ

From this display you can manage or change the objects used in the PerformanceTools.

For the Agent feature, choose option 2 (Manage performance data) on the IBMPerformance Tools menu.


à ðIBM Performance Tools for AS/4ðð



2. Manage Performance Data

3. Work with Historical Data

4. Advisor


===> _____________________________________________________________________

__________________________________________________________________________



á ñ

The Manage Performance Data display will appear.

à ðManage Performance Data






===> _____________________________________________________________________

__________________________________________________________________________


á ñ

From this display you can manage the objects used in the performance tools.

Work with Functional Areas—Manager FeatureFunctional areas provide a way to define and save selection values that you use onthe System and Component Reports. For example, you might save a set of jobs orusers as a functional area. Then each time you use the Print System Report(PRTSYSRPT) and Print Component Report (PRTCPTRPT) commands, youspecify the name of the functional area to use. Functional areas also work with thePrint Job Report (PRTJOBRPT), Print Pool Report (PRTPOLRPT), Print Trans-action Report (PRTTNSRPT), and Display Performance Graph (DSPPFRGPH)


commands. Specify these names on the select functional areas (SLTFCNARA) andthe omit functional areas (OMTFCNARA) parameters.

If you choose option 1 (Work with functional areas) on the Configure and ManageTools display, the Work with Functional Areas display appears.

à ðWork with Functional Areas



1=Create 2=Change 3=Copy 4=Delete

Functional

Option Area Text

1 My Func Area My department

ACCOUNTING Func Area for Accounting

DEPARTMENT A Func Area for Dept. A

DEPARTMENT B Func Area for Dept. B

DEPARTMENT C Func Area for Dept. C

DEPARTMENT D Func Area for Dept. D

MANAGEMENT Func Area for Managers

MANUFACTURING Func Area for Manufacturing

PAYROLL Func Area for Payroll

SALES FORCE Func Area for Sales Force

SECRETARIAL Func Area for Secretaries

More...


á ñ

This display shows the functional areas that exist in the library you specified. Tocreate a new functional area, type option 1, the name, and the description on thefirst line under the Functional Area and Text columns, and press the Enter key. Toselect an existing functional area, type a 2 (Change), 3 (Copy), or a 4 (Delete) inthe Option column next to the functional area of your choice.

Creating a Functional Area—Manager FeatureIf you choose to create a functional area, the Create Functional Area displayappears.

Chapter 12. Managing the Performance Tools Configuration 12-3

à ðCreate Functional Area

Functional Area . . . . . . : MY FUNC AREA


1=Select

Option Job User Option Job User

_ __________ __________ _ _________ __________

_ __________ __________ _ _________ __________

_ __________ __________ _ _________ __________

_ __________ __________ _ _________ __________

_ __________ __________ _ _________ __________

_ __________ __________ _ _________ __________

_ __________ __________ _ _________ __________

_ __________ __________ _ _________ __________

_ __________ __________ _ _________ __________

More...

F3=Exit F12=Cancel

á ñ

On this display you specify the job name and the user ID (or both) you want toinclude in the functional area. If you choose, you can specify only a job name, onlya user ID, a generic job name (of the form yyy*), or a generic user name. Thus,WS* in the Job column would include all jobs that have a job name starting withWS and any user ID name. You can leave a blank field in the Job or User columnto include all jobs with any job name or all jobs with any user ID name.

When you have finished entering all the job names and user IDs, press the Enterkey to create the functional area. Make sure you put a 1 in front of each job anduser you enter.

Changing a Functional Area—Manager FeatureIf you choose to change a functional area, the Change Functional Area displayappears.


à ðChange Functional Area

Functional Area . : DEPARTMENT A

Text . . . . . . . Func Area for Dept. A


1=Select 4=Delete

Option Job User Option Job User

1 JOB1 MARY

1 OPGMR

1 DSPð2 A\

1 M\

_ _________ __________ _ _________ _________

_ _________ __________ _ _________ _________

_ _________ __________ _ _________ _________

More...

F3=Exit F5=Refresh F12=Cancel F15=Sort by job name

F16=Sort by user name

á ñ

On this display you specify new job names and user IDs to include in the functionalarea by using option 1, or remove jobs and users from the functional area by usingoption 4. When you have made all of your entries, press the Enter key to changethe functional area.

Deleting a Functional Area—Manager FeatureIf you choose to delete a functional area, the Confirm Delete of Functional Areasdisplay appears, listing the functional areas you selected for deletion. Press theEnter key to delete them.

Copying a Functional AreaIf you choose to copy a functional area, the Copy Functional Area (CPYFCNARA)command prompt appears. Fill in the prompts and press the Enter key to copy thefunctional area.

Delete Performance DataUse the Delete performance data option on the Configure and Manage Toolsdisplay to delete performance data that you no longer need on your system. Whenyou choose option 2, the Delete Performance Data display appears.


à ðDelete Performance Data

Library . . . . . . QPFRDATA__


4=Delete


_ XYZ 12/15/95 14:ð5:55

_ PERFTESTC4 2 hours w/ 5 minute intervals 12/15/95 ð8:ð5:48

_ PERFTESTC3 Duration of 2 hours 12/14/95 ð9:21:44

_ PERFTESTC2 12/11/95 14:42:46

Bottom

F3=Exit F5=Refresh F12=Cancel F15=Sort by member F16=Sort by text

á ñ

The members that appear on this display are those used on the Start PerformanceMonitor (STRPFRMON) command for the keyword MBR when data was collected.To delete a member from this list, type a 4 (Delete) next to the appropriate memberand press the Enter key. The member you delete is deleted from the following datacollection files:

QAPGSUMDQAPMAPPNQAPMASYNQAPMBSCQAPMBUSQAPMCIOPQAPMCONFQAPMDBMONQAPMDDIQAPMDIOPQAPMDISKQAPMDMPTQAPMECLQAPMETHQAPMFRLYQAPMHDLCQAPMHDWRQAPMIDLCQAPMJOBSQAPMLAPDQAPMLIOPQAPMMIOP

QAPMIOPDQAPMPOOLQAPMRESPQAPMRWSQAPMSAPQAPMSBSDQAPMSNAQAPMSNADSQAPMSTNEQAPMSTNLQAPMSYSQAPMTJOBQAPMTSKQAPMX25QAPTLCKDQTRIDXQTRDMPTQTRJOBTQTRJSUMQTRSLWTQAPMSTNDQAPMSTNYQTRTSUM


Copy Performance DataUse the Copy performance data option on the Configure and Manage Tools displayto make copies of performance data members. When you choose option 3, theSelect Performance Member display appears.




1=Select


_ FRIDAY Performance Data for Friday 1ð/27/95 1ð:ð5:46

_ THURSDAY Performance Data for Thursday 1ð/26/95 12:ðð:34

1 WEDNESDAY Performance Data for Wednesday 1ð/25/95 13:5ð:15

1 TUESDAY Performance Data for Tuesday 1ð/24/95 13:55:ð8

1 MONDAY Performance Data for Monday 1ð/23/95 16:25:39

_ TESTRUN Test run of system 1ð/19/95 2ð:31:42

_ Q95291ð958 1ð/18/95 ð9:58:45

_ Q9529ð2ðð9 1ð/17/95 2ð:ð9:23

F3=Exit F12=Cancel F15=Sort by member F16=Sort by text


á ñ

The members that appear on this display are those used on the Start PerformanceMonitor (STRPFRMON) command for the keyword MBR when data was collected.To copy a member or members from the list, type a 1 (Select) next to the appro-priate member(s) and press the Enter key. The Copy Performance Data displayappears.


à ðCopy Performance Data Member


--------Copy From-------- --------Copy To--------

Member Library Member Library

MONDAY QPFRDATA MONDAY NEWLIB

TUESDAY QPFRDATA TUESDAY NEWLIB

WEDNESDAY QPFRDATA WEDNESDAY NEWLIB

Bottom

F3=Exit F12=Cancel

á ñ

This display shows you the members you selected to copy and where they are tobe copied to. For each member listed, type the name of the new member and thelibrary that contains it in the Copy To entries of the display, and then press theEnter key. When the copy completes, you have exact copies of the old perform-ance members in the new performance members for the following files:

QAPMAPPNQAPMASYNQAPMBSCQAPMBUSQAPMCIOPQAPMCONFQAPMDBMONQAPMDDIQAPMDIOPQAPMDISKQAPMDMPTQAPMECLQAPMETHQAPMFRLYQAPMHDLCQAPMHDWRQAPMIDLCQAPMIOPDQAPMJOBS

QAPMLAPDQAPMLIOPQAPMMIOPQAPMPOOLQAPMRESPQAPMRWSQAPMSAPQAPMSBSDQAPMSNAQAPMSNADSQAPMSTNDQAPMSTNEQAPMSTNLQAPMSTNYQAPMSYSQAPMTJOBQAPMTSKQAPMX25

Convert Performance Data (CVTPFRDTA) CommandUse the Convert performance data option on the Configure and Manage Toolsdisplay to convert performance data. The data is converted to the file formatsneeded to be processed by the current release of the performancemeasurement/analysis tools.


à ðConfigure and Manage Tools


1. Work with functional areas





===> 4________________________________________________________________________

______________________________________________________________________________


á ñ

When you select option 4, the Convert Performance Data (CVTPFRDTA) commandprompt display appears.

à ðConvert Performance Data (CVTPFRDTA)


From library . . . . . . . . . . ___________ Name

To library . . . . . . . . . . . ___________ Name

Job Description . . . . . . . . \USRPRF____ Name, \USRPRF, \NONE

Library . . . . . . . . . . . ___________ Name, \LIBL, \CURLIB

Bottom

F3=Exit F4=Prompt F5=Refresh F12=Cancel F13=How to use this display

F24=More keys

á ñ

The Convert Performance Data (CVTPFRDTA) command converts performancedata from the previous release to the formats needed to be processed by thecurrent release of the performance measurement/analysis tools. First, the releaselevel on which the data was collected is determined. Then, all members of all filesthat need conversion are converted to the appropriate format.

The following files must be present for the conversion to take place:


The following files are copied, or converted if necessary, if they are present:

The conversion can be done in the library in which the current data resides or in adifferent library. If the conversion is done in the same library, the current data isreplaced by the new data. If the conversion is done in a different library, the newdata exists in the new library while the current data continues to exist in the currentlibrary.

Notes:

1. If a different library is specified for the new data, those files in the currentlibrary that do not need conversion are copied to the new library.

2. If user-created logical files exist over any of these files, you must delete andre-create these logical files after the performance data has been converted.

3. Historical data cannot be converted without the performance monitor filesrequired for converting.

To convert performance data collected prior to the current release, complete thefollowing items on the display.

From library Specifies the library that contains the data being converted.

To library Specifies the library that contains the converted data.

Job Description Specifies the job description used to submit the file-conversion jobfor batch processing.

The possible job description values are:

*USRPRF The job description defined for the submitting job’s user profile.

job-description-name Specify the name of the job description to be used.

*NONE A batch job is not submitted. Processing continues interactively while theuser waits.

The possible library values are:

*LIBL The library list is used to locate the job description.

QAPMCIOPQAPMCONFQAPMDIOPQAPMDISKQAPMJOBS

QAPMLIOPQAPMPOOLQAPMRESPQAPMSYS

QACPCNFGQACPGPHFQACPPROFQACPRESPQAITMONQAPGHSTDQAPGHSTIQAPGPKGFQAPMASYNQAPMBSCQAPMBUS

QAPMDMPTQAPMECLQAPMETHQAPMHDLCQAPMIDLCQAPMLAPDQAPMMIOPQAPMSBSDQAPMTSKQAPMX25QAPTAPGP


*CURLIB The current library for the job is used to locate the job description. If nocurrent library entry exists in the library list, QGPL is used.

library-name The library where the job description is located.

Note: If the conversion takes place interactively, the user’s work station is notavailable for other use during this time, which can be significant for longjobs.



Chapter 13. A Problem Analysis Case Study

This chapter provides users of the AS/400 system with an initial approach to deter-mining the source of performance problems using available system tools (bothoperating system functions and additional licensed programs).

This example provides an introduction to performance analysis and shows yousome performance analysis techniques. The scenario describes how a user who isexperienced in performance analysis assists a company in resolving a performanceconcern. You can see how the expert identifies the real problem, isolates thecause, and provides the recommended solution.

You should read “Performance Analysis Overview” on page 1-8 before reading thiscase study.

Some of the tools discussed are not available in the Agent feature. Appendix D,Comparison of Performance Tools, provides additional information about Perform-ance Tools functions.

Note: Although the technique used represents just one of many differentapproaches to performance analysis, and the problem described is a smallsubset of the real-life possibilities, the example is designed to provide initialguidance in developing an overall strategy for performance problem anal-ysis. The names of people and the events described in this chapter are ficti-tious, and any likeness to actual people is purely coincidental. Becausecustomer applications and requirements vary, IBM makes no representationor warranty that the methodology described herein will solve or eliminateunique customer performance problems.

Introduction to Performance AnalysisPerformance problem analysis is a methodology for investigating, measuring, andcorrecting deficiencies so that system performance meets the user’s expectations. Itdoes not matter much that the “system” is a computer; it could be an automobile ora washing machine. The problem-solving approach is essentially the same:

1. Understand the symptoms of the problem.

2. Use tools to measure and define the problem.

3. Isolate the cause.

4. Correct the problem.

5. Use tools to verify that the problem is corrected.

Initially, the analyst knows the user is not satisfied with the way the system isworking. For example, it may be running too slow, too noisy, too hot, and so on.The analyst, mechanic, or repair person must first understand what the problemreally is. The best way to find out is to observe the problem condition personally.Can the analyst confirm the user’s complaint? If the analyst cannot, he should getas much information as possible from those users who have experienced theproblem. What are the most common problem descriptions?

The key to success with any performance issue is to have a clear definition of theusers’ performance criteria. In other words, given the application mix, what do the


users want from the system in terms of interactive response time, batch throughput,and processing requirements? For example, a system that supports an interactiveorder-entry application may have a response time criterion to ensure that customersdo not perceive abnormal delays. Another criterion may require that end-of-dayprocessing be completed by a specific time. Given these requirements, the analystcan establish performance objectives around system resource utilization guidelines.With a clear statement of goals and objectives, performance analysis can proceedon a firm basis.

When the objectives are understood, it is important to assess whether the hardwareconfiguration is adequate to support the workload. Is there enough processing unitcapacity? Is main storage sufficient for the application mix? It the analyst answersthese questions first, perhaps through capacity planning modeling techniques,needless effort can be avoided later.

With an understanding of the symptoms of the problem and the objectives to bemet, the analyst can formulate a hypothesis that may explain the cause of theproblem. The analyst can use certain OS/400 commands and Performance Tools tomeasure the system performance. The analyst should review the measured data tofurther define the problem and to validate or reject the hypothesis. When theapparent cause or causes have been isolated, a solution can be proposed. Theanalyst should deal with one solution at a time. Then changes can be made andtested. Again, the analyst’s tools can, in many cases, measure the effectiveness ofthe solution and look for possible side effects.

To achieve optimum performance, one must recognize the interrelationshipbetween the critical system resources and attempt to balance these resources,namely processing unit, disk, main storage, and, for communications, remote lines.Each of these resources may become a performance problem.

Improvements to system performance, whether to interactive throughput, interactiveresponse time, batch throughput, or some combination, may take many forms fromsimply adjusting activity level or pool size to changing the application code itself.Ultimately, however, any improvement will come only through analysis of the criticalresources (processing unit, main storage, disk, and remote lines) and contention forsystem and application objects.

The Case StudyThis scenario starts with a company called Armstrong Sporting Goods, Inc. (a ficti-tious company). As a distributor of sporting equipment throughout the southeasternUnited States, Armstrong selected the AS/400 system as a means for automatingmuch of their order-entry, accounting, inventory, and shipping operations. Highquality customer service is critical to the continued success of this company.

The PlayersSue Miller is the new data processing (DP) manager for Armstrong and is theperson who provided the IBM support team with most of the information regardingthe perceived performance problem. Having been the DP manager for just a shorttime, Sue is anxious to establish her credibility with the company by quicklyaddressing an end-user concern over system performance.


Bob Williams is the assigned IBM systems engineer. He has been asked by Sue toassist the DP staff in resolving the performance issue. In this scenario, he is theexpert.

As you read through the rest of this story, you can look over Bob’s shoulder as heobserves the symptoms of Armstrong’s performance problem and then proceeds toisolate the cause. Along the way, you will be introduced to additional people whoprove to be instrumental in getting the problem resolved.

The ConfigurationHere is the configuration of the system in this story:

� One AS/400 Model 510, 384 megabytes main storage

� Two communications lines

– A 2400 baud electronic customer support switched line

– A spare line that is currently unused

� One 6380 Tape Unit

� One 4028 Printer

� Twenty-four 3197 Display Stations

� Two 4224 Printers

� Four 6603 Disk Units

� One 6607 Disk Unit

| � OS/400 Version 4 Release 2 licensed program

With this information as the base for our example, let’s begin!

The ProblemIt was 9:00 a.m. Monday morning, and Sue Miller had just finished introducingherself as the new data processing manager to Bob Williams, a systems engineerfrom IBM. The two of them were in her office to review the systems managementprocedures currently in place at Armstrong. During the discussion, Sue mentionedthat no formal attempt was being made to monitor the system’s performance on aregular basis. Other activities, such as system backup and change management,had already been addressed by Armstrong, but Sue felt that she needed to have abetter understanding of how well their current system was handling the dailydemands of the company. This interest was actually prompted by concerns broughtup at a recent meeting with the department managers. Some of the end users hadcomplained that the system was running too slow and at times appeared to “go tosleep.”

Bob was happy to hear that Sue wanted to start developing a performance man-agement strategy for Armstrong. He remarked that he had worked with severalcompanies in the past who unfortunately waited until a serious situation occurredbefore starting to make an effort to better understand their system requirements.Without historical information to compare past performance, the problem analysisbecame much more difficult.

Bob and Sue then continued talking the rest of the morning about other topics ofinterest involving the data processing department. At the close of their discussion,

Chapter 13. A Problem Analysis Case Study 13-3

Bob suggested another meeting to further investigate the source of the perform-ance concerns. In the meantime, Sue was asked to do the following:

1. Read the Work Management book to better understand performance guidelinesand basic tuning techniques. This would help prepare Sue for the upcominganalysis activities that Bob would assist her with.

2. Use the error reporting functions, such as the Print Error Log (PRTERRLOG)command, to see if the system is experiencing hardware problems. Althoughthis should be a part of normal systems management, all performance analysisactivities should first ensure that the system is running error free.

3. Install the Performance Tools Manager feature that Armstrong had purchasedtwo weeks earlier. This would assist them in their investigation of the problem.

4. Survey

5. the end users to find out who was experiencing unsatisfactory system perform-ance and of what type (that is, interactive response time, batch throughput, andso forth). The performance objectives for those end users should then be deter-mined and put in writing.

With that, Bob left with the agreement that they would get together on Fridaymorning.

ReviewSue is new to Armstrong and is not familiar with the system’s performance history.She must quickly learn the objectives of the end users. How important is it thatcertain display station operators receive subsecond response time, and is it realisticgiven the requirements of the application? Are there any critical batch jobs thatmust be finished by the end of the day? These kinds of questions need to beanswered for Sue to determine if a problem exists.

As Bob mentioned, even though the AS/400 system provides software tools tomonitor performance, both in the operating system and in optional licensed pro-grams, many companies do not track their system’s resource usage. Using theAS/400 system’s ability to continuously collect performance data, a business canreview workload trends on a periodic basis.

At this point, Sue suspects a problem exists because of informal remarks by someof the end users. She has no solid evidence describing the problem and, therefore,cannot give Bob any concrete information to work with. We are not even sure ifthere is a performance problem. This is usually where many analysis experiencesbegin. Bob decided that before proceeding with the analysis, the customer shouldfirst review basic tuning guidelines, make sure an important software product herelies on (the Performance Tools Manager feature) is ready to use, check to see ifthe system is running without hardware problems, and gather more informationfrom the end users.

Checking the System’s PerformanceOn Friday morning, Bob returned to Armstrong to begin working with Sue on ana-lyzing the system’s performance. Two days earlier, Sue met with all of the depart-ment managers where she asked them to survey their staffs on how well theythought the system was performing. The results were to be returned to her by thefollowing Monday. Also, a review of the system error reports did not indicate thatthe system was having hardware problems.


Bob felt that the first step in analyzing system performance was to review data fromthe system interactively using the control language (CL) commands:

� Work with System Status (WRKSYSSTS)

� Work with Active Jobs (WRKACTJOB)

� Work with Disk Status (WRKDSKSTS)

Using these commands, he could quickly see if the system was able to handle therequests for processing unit, disk, and main storage adequately at that instant intime. He cautioned that because the results changed dynamically with the work-load, he could not determine for sure that the system had all the capacity it neededall the time. Also, it was important that the time selected to run these commandsdid not include work not normally running (for example, excessive sign-ons andsign-offs). Sue assured Bob that now would be a good time to look at the system.

The following illustrations show the results of the commands and how Bob inter-preted them. (All output was generated using the OS/400 Version 3 Release 7licensed program.)

First Bob issued the Work with System Status (WRKSYSSTS) command.

à ðWork with System Status SYS4ðð

ð7/ð7/98 ð9:31:43

% CPU used . . . . . . . : 55.7 Auxiliary storage:

Elapsed time . . . . . . : ðð:ð9:31 System ASP . . . . . . : 8.12 G

Jobs in system . . . . . : 1ð2 % used . . . . . . . . : 57.5494

% addresses used: Total . . . . . . . . : 8.12 G

Permanent . . . . . . : 2.483 Current unprotect used : 326 M

Temporary . . . . . . : .ð26 Maximum unprotect . . : 328 M

Type pool size and activity level changes, press Enter.

System Pool Reserved Max -----DB----- ---Non-DB---

Pool Size (K) Size (K) Active Fault Pages Fault Pages

1 1ð6564 29356 +++ .ð .ð .2 1.6

2 174544 ð 4 .9 2.9 1.8 4.6

3 5256 ð 4 .ð 1.3 .ð .4

4 1ð6852 ð 12 3.2 27.2 3.9 24.1

Bottom

Command

===>

F3=Exit F4=Prompt F5=Refresh F9=Retrieve F1ð=Restart

F11=Display transition data F12=Cancel F24=More keys

á ñ

� The overall processing unit use was 55.7 percent and did not reflect an exces-sively busy system.

� The elapsed time for measurement was greater than 5 minutes but less than15 minutes–a good choice when looking for valid data that is not skewed byshort surges of activity or long periods that tend to average out problems.

� The number of jobs in the system at first appeared high to Sue, but Bobexplained that this number reflected all the jobs the system was keeping trackof, even if they had finished but still had output yet to print (for example, joblogs).


� The fault rate of the machine storage pool (always system pool 1) did notexceed 1 fault per second, indicating that pool 1 was large enough. (More infor-mation on performance tuning is available in the Work Management book.)

� The fault rate of the rest of the machine storage pools (system pools 2 through4) was not too heavy ( database + nondatabase < 10) and the total faults of allthe pools was less than 15. In general, main storage did not appear to be over-committed.

Bob pressed F11 to select the second view.

à ðWork with System Status SYS4ðð

ð7/ð7/98 14:ð7:43

% CPU used . . . . . . . : 55.7 Auxiliary storage:

Elapsed time . . . . . . : ðð:ð9:31 System ASP . . . . . . : 8.12 G

Jobs in system . . . . . : 1ð2 % used . . . . . . . . : 57.5494

% addresses used: Total . . . . . . . . : 8.12 G

Permanent . . . . . . : 2.483 Current unprotect used : 326 M

Temporary . . . . . . : .ð26 Maximum unprotect . . : 328 M

Type pool size and activity level changes, press Enter.

System Pool Reserved Max Active-> Wait-> Active->

Pool Size (K) Size (K) Active Wait Inel Inel

1 1ð6564 29356 +++ .ð .ð .ð

2 174544 ð 4 2.5 .ð .ð

3 5256 ð 4 8.3 .ð .ð 4 1ð6852 ð 12 2ð.1 2.ð .ð

Bottom

Command

===>

F3=Exit F4=Prompt F5=Refresh F9=Retrieve F1ð=Restart

F11=Display transition data F12=Cancel F24=More keys

á ñ

� The ratio of Wait->Ineligible to Active->Wait for the interactive pool (system pool4) was approximately 10% and confirmed to Bob that the activity level was setproperly. He added that many customers set their activity levels so that theWait->Ineligible is always zero. The level could be too high, causing majorproblems during exceptionally busy periods.

� Active->Ineligible for system pool 4 was zero. Usually, any value greater thanzero in the interactive storage pool is a good indication that jobs are exceedingtheir time-slice values and may be candidates for submission to batch for proc-essing.

Bob then issued the Work with Active Jobs (WRKACTJOB) command.


à ðWork with Active Jobs SYS4ðð

ð7/ð7/98 ð9:47:3ð

CPU %: 57.2 Elapsed time: ðð:ð8:46 Active jobs: 35


2=Change 3=Hold 4=End 5=Work with 6=Release 7=Display message

8=Work with spooled files 13=Disconnect ...

Opt Subsystem/Job User Type CPU % Function Status

QBATCH QSYS SBS .ð DEQW

ARPOST ACTð7 BCH 24.4 PGM-AR32ð RUN

QCMN QSYS SBS .ð DEQW

QCTL QSYS SBS .ð DEQW

DSPð1 QSYSOPR INT .ð MNU-MAIN DSPW

QINTER QSYS SBS 1.ð DEQW

DSPð2 SHIPð1 INT 1.3 MNU-SMðð1 DSPW

DSPð9 SERVð2 INT .ð CMD-WRKSPLF DSPW

DSP1ð SERVð3 INT .7 PGM=CS11ð RUN

More...

Parameters or command

===>

F3=Exit F5=Refresh F1ð=Restart statistics F11=Display elapsed data

F12=Cancel F23=More options F24=More keys

á ñ

� The active job count was 35. When divided into the number of jobs in thesystem (102/35=3.0), the result showed that Armstrong was doing a good job ofcleaning up the job logs and keeping the number of jobs the system tracked toa minimum.

� No interactive jobs were using an excessive amount of processing unit use(more than 2 percent).

Next, Bob issued the Work with Disk Status (WRKDSKSTS) command.

à ðWork with Disk Status SYS4ðð

ð7/ð7/98 1ð:ð3:59

Elapsed time: ðð:ð9:11

Size % I/O Request Read Write Read Write %

Unit Type (M) Used Rqs Size (K) Rqs Rqs (K) (K) Busy 1 66ð3 1967 67.1 .7 6.3 .2 .4 8.3 5.3 9 2 66ð3 1967 56.6 1.1 4.5 .2 .8 5.ð 4.4 5 3 66ð7 4194 55.3 1.1 6.5 .5 .6 6.9 6.2 13

Bottom

Command

===>

F3=Exit F5=Refresh F12=Cancel F24=More keys

á ñ

� Except for disk unit 1 (load source unit), all the other units had approximatelythe same amount of space used, indicating an evenly distributed system, andnone of those units were over 75 percent full.


� No one drive was busy more than 13 percent of the time, and they were wellunder the threshold of 40 percent.

The net result of Bob’s initial observation of the system showed that the systemwas responding well to the workload at that moment in time. Sue again commentedthat this period of the day was a good representation of Armstrong’s normaldemands on the system.

Bob felt he had a good idea of what the overall system was doing, but he plannedto later validate his findings by using the Advisor option on the Performance Toolsmenu. The advisor is a tool that can be run over data gathered by the performancemonitor to provide conclusions and recommendations about system performance. Inthe meantime, with the feedback from the different departments still pending, Bobsuggested using another means of gathering performance data from the system.This could be done by starting the performance monitor using the Work with Per-formance Collection (WRKPFRCOL) command. With this command, informationsimilar to that provided by the earlier commands and additional detailed data on jobprocessing could be collected over a number of days (that is, with multiple datacollections) without operator intervention. Another way to start the performancemonitor would be to use the Start Performance Monitor (STRPFRMON) command,but this command does not allow for automatic data collection, which is what Boband Sue were after. The collected data could then be reviewed through commandsprovided by Performance Tools.

To begin the process of collecting performance data with the WRKPFRCOLcommand, Bob explained that first they would have to decide when to run the per-formance monitor and for how long. Without knowing exactly when the problem wasoccurring, Bob suggested they collect data for the entire first shift with 15-minutecollection intervals. Using this size interval time would help to identify peak work-loads that deserved further attention. Any longer intervals might mask a problem.Because Bob and Sue were still not sure of the type of problem that existed, thedata collection would not include trace information. Tracing is a process by whichinformation about each job state transition is recorded in a special table. The datamay later be dumped to a database file, which can then be processed by Perform-ance Tools. Tracing can result in a large amount of collected data, which couldaffect system performance when dumped. Normally, a more selective collectionprocess can be used during problem isolation to limit the amount of data.

Sue entered the WRKPFRCOL command and specified the values as shown in thefollowing display:


à ðWork with Performance Collection


1=Add 2=Change 3=Hold 4=Remove 5=Display 6=Release

Performance

Opt Collection Status Description

1 PERFPROB__

Bottom


á ñ

The following display was shown next. Sue typed the values that are highlighted.

à ðAdd Performance Collection (ADDPFRCOL)


Performance Collection . . . . . > PERFPROB Name

Collection days . . . . . . . . \MON \ALL, \MON, \TUE, \WED...

+ for more values \TUECollection start time . . . . . ð8ðð HHMM

Text 'description' . . . . . . . All day collectionLibrary . . . . . . . . . . . . QPFRDATA Name

Text 'description' . . . . . . . Unknown Performance ProblemTime interval (in minutes) . . . 15 5, 1ð, 15, 2ð, 25, 3ð, 35...

Stops data collection . . . . . \ELAPSED \ELAPSED, \TIME


Hour . . . . . . . . . . . . . . 1ð ð-168

Minutes . . . . . . . . . . . . ð ð-59


Trace type . . . . . . . . . . . \NONE \NONE, \ALL

Dump the trace . . . . . . . . . \YES \YES, \NO



+ for more values

More...


F24=More keys

á ñ

Sue added a collection for Monday and Tuesday from 8:00 a.m until 6:00 p.m. Acollection period of ten hours would include data on sign-offs and batch jobs at theend of the day. Bob commented to Sue that because this was the first time thatthey were adding a performance collection, they would have to submit the perform-ance collection job after using the ADDPFRCOL command by typing the followingcommand:

SBMJOB JOBD(QGPL/QPFRCOL) RQSDTA(\JOBD)

This command ensures that the performance monitor is started at the right times.


Bob left and planned to return at the end of the week to review the output with her.By that time, Sue should have collected data over two days and had time to goover the results of her end-user survey.

ReviewBob lacked information on who was experiencing the performance problem, so hedecided to take some preliminary steps in understanding how well the system wasresponding to the daily workload. He did this by using the standard system com-mands, which dynamically show usage of main storage, processing unit, and disk.The important point that Bob wanted Sue to understand was that these commandsonly displayed this information for a very specific point in time and could not beused to represent the system’s performance under all the different workloads it hadto handle. This was a quick means of looking for obvious resource problems.

The next step was to capture data over a longer period of time using the Work withPerformance Collection (WRKPRFCOL) command. Maybe the problem was occur-ring at a specific time of the day.

In most everyday situations, performance data could be collected over large periodsof time to get a good idea of system activity and trends. Sampling intervals oflonger duration (20 to 30 minutes) are fine for normal system tracking, but Bob andSue are investigating a possible problem. Shorter intervals (10 to 15 minutes)would help to highlight a problem.

Still critical to Bob’s investigation was the result of Sue’s survey. They still did notknow what kind of a problem they were facing. It is important to thoroughly definethe problem.

Reviewing the End-User Survey ResultsOn Tuesday, Sue received the final survey results from all the end users. Followingis a copy of the survey form Sue distributed.


Armstrong Computer End-User Survey

On a scale of 1 to 5, please rate how well the computer system meets yourneeds in the following categories:

1 = Excellent, 2 = Satisfactory, 3 = Average,4 = Needs some improvement, 5 = Needs much improvement

1. Availability of the computer ___

2. Interactive response time ___

3. Timeliness of printed output requests ___

4. Timeliness of batch run requests ___

For those items answered with a 4 or 5, please indicate any concernsyou might have.___________________________________________________________________________________________________________________________________________________________

(We will follow up this survey with personal interviews for thosewho would like to help the data processing department improve itsservices to all the end users.)

Thirty-seven surveys were returned. Sue decided to concentrate on only thereturned forms that indicated a 4 of 5 in any of the categories. She noticed thatonly two of the surveys had reflected a dissatisfaction with the system, and bothwere from the order-entry department. Also, the only category with negativeresponses was number two, Interactive response time. One of the two negativesurveys included the following comment: Ever since the new procedure, whichallowed customers to call in their orders, was put into use, the system seemed totake a very long time before the entry display appeared.

Sue met briefly with the order-entry department to discuss their survey responsesand to better understand their performance requirements. During the meeting, Suelearned that the department’s daily workload included both batch and interactiveprocessing. Their batch jobs ran mostly in the evenings unattended and were notpresenting a problem. The interactive jobs, however, were experiencing muchlonger response times than the department’s objective of 2 seconds. Sue reviewedsome basic application requirements, such as the average number of databaseread operations per transaction, and could not readily determine the source of theproblem. Sue then decided that it would be better to review her findings with Bobon Friday.

Analyzing System PerformanceOn Friday morning, Bob arrived to analyze the collected performance data. First,Sue updated him on the results of the survey. Bob was very interested in the con-cerns of the order-entry department and commented that they would investigate theorder-entry application. First, he would like to analyze the system performance oncemore using the advisor. Below is the sequence of events and displays that Bobused to perform the system analysis using the advisor.


Bob started at the Performance Tools menu and selected the Advisor option. Hethen selected the appropriate library and member and pressed the Enter key, whichtook him to the Select Time Intervals to Analyze display.


Member . . . . . . . . PERFPROB Library . . . . . . : QPFRDATA

Type options, press Enter

1=Select

---Tns---- --CPU Util--- High Util --Pool Fault/Sec--

Opt Date Time Cnt Rsp Tot Int Bch Dsk Unit Mch Usr ID Excp

_ ð1/15 ð8:15 3ð9 .84 16 1ð 3 1 ððð1 ð ð ð3 192ð

_ ð1/15 ð8:29 266 .46 6 3 1 1 ððð1 ð ð ð3 1ð15

_ ð1/15 ð8:44 635 .87 24 15 5 1 ððð1 ð ð ð3 1174

_ ð1/15 ð8:59 494 .92 53 3ð 15 1 ððð1 ð ð ð3 1229

_ ð1/15 ð9:14 318 .7ð 62 32 2ð 1 ððð1 ð ð ð3 11ð3

_ ð1/15 ð9:29 526 .89 71 4ð 25 1 ððð1 ð ð ð3 1573

_ ð1/15 ð9:44 574 .73 43 2ð 15 1 ððð1 ð ð ð3 1668

_ ð1/15 ð9:59 399 .94 48 2ð 19 1 ððð1 ð ð ð3 135ð

_ ð1/15 1ð:14 243 4.45 11 5 2 1 ððð1 ð ð ð3 192ð

_ ð1/15 1ð:29 246 1.49 24 15 3 1 ððð1 ð ð ð3 1834

Bottom

F3=Exit F5=Refresh F11=Display histogram F12 Cancel F13=Select all

á ñ

Bob suggested to Sue that they analyze all the intervals at this stage to get an ideaof overall system performance. Sue agreed and Bob pressed F13 (Select all) andpressed the Enter key.


Member . . . . . . . : PERFPROB Library . . . . . . : QPFRDATA

System . . . . . . . : SYS4ðð Version/release . . : 4/2.ð

Start date . . . . . : ð7/ð1/98 Model . . . . . . . : D45

Start time . . . . . : ð8:ðð:ð1 Serial number . . . . : XX-XXXX


5=Display details

Option Recommendations and conclusions

_ Recommendations

_ Examine error logs for indications of problems.

_ Conclusions

_ Pool 3 fault rate is well below guidelines of 25.ð

_ Pool 4 fault rate is well below guidelines of 25.ð

_ Pool 2 W->I transition zero. Fault rate within guidelines.

_ No performance problems were detected in system data file.

_ No performance problems found on SDLC line MCLINE

_ No performance problems found with DIOP(s)

_ No performance problems found with CIOP(s)

_ Interval Conclusions

_ ASP 1 arm % busy ranged from 21.9% on arm ððð8 to 1ð.2% on arm ððð4.

_ Total system I/O during all selected intervals was 4362ð3 .

More


á ñ

The Display Recommendations display showed Bob and Sue that the system wasperforming within the guidelines and that no system-related problems or errorswhere affecting the performance of the system. After having completed the system


analysis using the advisor, which confirmed his analysis earlier in the week, hementioned to Sue that another way to quickly analyze system data and view trendswas to use performance graphics.

Using Performance Graphics—Manager FeatureFollowing is the sequence of events that Bob specified to produce the graphs. Bobwent to the Performance Tools menu and selected Option 9 (Performancegraphics). Then the following display appeared:

à ðPERFORMG Performance Tools Graphics

System: SYS4ðð


1. Work with graph formats and packages

2. Work with historical data

3. Display graphs and packages



===> 3



á ñ

Bob explained to Sue that Performance Tools contains numerous pre-formattedgraphs for customers to user. Option 1 allows the user to work with the graphformats and packages, and option 2 allows the user to create historical data fromdata collected over different monitor runs (for example, once a week for a month).Historical data summarizes performance members so you can display eachmember as a point on the historical graph. Then a user can view system perform-ance trends in a graphical format. Because Armstrong had previously not been col-lecting performance data, Sue agreed to set up a collection schedule for once aweek to establish some historical data. Bob suggested they use the IBM-suppliedgraph formats to show performance graphs (rather than historical graphs), so theyselected option 3 (Display performance data graphs).


à ð

Display Graphs and Packages


1. Display performance data graphs

2. Display historical data graphs


===> 1


á ñ

Bob pointed out that the QIBMxxx formats are supplied by IBM. He commented thata good graph to begin with is the processing unit use versus time (by job type), sothey selected the QIBMCPUTYP member and pressed the Enter key.

à ðSelect Graph Formats and Packages



1=Select 5=Display sample graph 8=Display package contents

Format/

Option Package Type Description

QIBMPKG PACKAGE IBM GRAPH PACKAGE

QIBMASYNC FORMAT Asynchronous Disk I/O per Second vs. Time

QIBMCMNIOP FORMAT Communications IOP Utilization vs. Time

QIBMCPUPTY FORMAT CPU Utilization vs. Time (Priority)

1 QIBMCPUTYP FORMAT CPU Utilization vs. Time (Job Type)

QIBMDSKARM FORMAT Disk Arm Utilization vs. Time

QIBMDSKIOP FORMAT Disk IOP Utilization vs. Time

QIBMDSKOCC FORMAT Percentage of Disk Occupied vs. Time

QIBMLWSIOP FORMAT Local Workstation IOP Utilization vs. Time

QIBMMFCIOP FORMAT Multifunction IOP (Comm) Util vs. Time

QIBMMFDIOP FORMAT Multifunction IOP (Disk) Util vs. Time

More

F3=Exit F1ð=Restore list F12=Cancel F14=Sort by type F15=Sort by name

F16=Sort by Description

á ñ

On the following display Bob selected the performance data member to begraphed.


à ðSelect Performance Data Member



1=Select

Member

Option Name Description Date Time

1 PERFPROB ð7/ð7/98 14:33:24

Bottom

F3=Exit F5=Refresh F12=Cancel F15=Sort by member

F16=Sort by Description F19=Sort by date/time

á ñ

On the following display Bob pressed F6 (Include all data) and pressed the Enterkey and proceeded to the next display (Figure 13-1 on page 13-16) containing thegraph.

à ðSelect Categories for Performance Graphs

Member . . . . . : PERFPROB


Type options, press Enter. Press F6 to include all data in the graph.

1=Select

Option Category

Job

User ID

Subsystem

Pool

Communications line

Control unit

Functional area

Bottom

F3=Exit F6=Include all data F12=Cancel

á ñ


RV2S075-0

9080706050403020100

CPUUtilization


18:0016:0014:0012:0010:0008:00Time

BatchInteractSystem



F9=OverlayF17=Plot

Figure 13-1. CPU Utilization

Here Bob commented to Sue that he would only show the first two and one-halfhours of the collected data to give her a quick idea of what it would look like. Hedid this by changing the start and stop parameters to produce the following dis-plays. The following are the graphs that Bob and Sue elected to look at (that is,they followed the same previous steps to use the formats QIBMRSP,QIBMDSKARM, and QIBMDSKIOP).

Time

4.504.003.503.002.502.001.501.000.500.00

RV2S076-0

10:3010:0009:3009:0008:3008:00

InteractiveResponse Time Interactive Response Time vs Time

InteractPress Enter to continue.F3=ExitF12=Cancel


F9=OverlayF17=Plot

Time

MaximumAverage

RV2S080-0

10:3010:0009:3009:0008:3008:00

2220181614121086420

Disk ArmUtilization

Disk Arm Utilization vs. Time



F9=OverlayF17=Plot


09:00Time

Disk IOP Utilization vs. Time

MaximumAverage

RV2S079-0

24222018161412108642008:00 08:30 09:30 10:00 10:30

Disk IOPUtilization



F9=OverlayF17=Plot

Bob then explained the graphs that they had produced and commented to Sue thatthe processing unit use, disk arm use, and disk IOP use showed no resource prob-lems, and that the graphs were a quick way to pick up those types of problemswithout having to analyze the reports. The interactive response time graph,however, did show an abnormality just after 10:00 a.m., which should be investi-gated further. While the graphs gave a clear overview of how the system was per-forming, in Armstrong’s situation, more detailed analysis was required of thegathered data.

Another way to review the collected data was to use the Display Performance Data(DSPPFRDTA) command. They could quickly see a summary of all the data inter-actively and isolate data of interest, which they could explore further. Following isthe sequence of steps Bob used to perform further analysis.

à ðDisplay Performance Data

Member . . . . . . . . PERFPROB F4 for list


Elapsed time . . . . : ð9:53:52 Version . . . . . . : 4.ð

System . . . . . . . : SYS4ðð Release . . . . . . : 2.ð

Start date . . . . . : ð7/ð7/98 Model . . . . . . . : 51ð-2144

Start time . . . . . : ð8:ðð:ð1 Serial number . . . : XX-XXXXX

QPFRADJ. . . . . . . : ð QDYNPTYSCD . . . . . : 1

CPU utilization (priority) . . . . . . . . . . . : 23.55 CPU utilization (other) . . . . . . . . . . . . : 14.78 Job count . . . . . . . . . . . . . . . . . . . : 172 Transaction count . . . . . . . . . . . . . . . : 15ð98 Transactions per hour . . . . . . . . . . . . . : 1525 Average response (seconds) . . . . . . . . . . . : 1.45 Disk utilization (percent) . . . . . . . . . . . : 7.29 Disk I/O per second . . . . . . . . . . . . . . : 2ð.9 Logical DB I/O for DDM jobs. . . . . . . . . . . : 52.9

F3=Exit F4=Prompt F5=Refresh F6=Display all jobs F1ð=Command entry

F12=Cancel F24=More keys

á ñ

1. As in the earlier Work with Active Job (WRKACTJOB) and Work with DiskStatus (WRKDSKSTS) commands, Bob found that the overall use of the proc-


essing unit and disk was not exceptionally high. Also, Sue agreed with Bob thatthe average response time of 1.45 seconds was acceptable. (This valuereflects the internal response time of the system and does not include linetransmission time, which is usually not a big difference for local work stations.)

Bob then pressed F15 (Display by interval), which is available after pressingF24 (More keys).

à ðDisplay by Interval

Member . . . . . . . : PERFPROB Elapsed time . . . . : ð9:53:52



5=Display jobs


Option Date Time Util Count Count Response I/O

_ ð7/ð7/98 ð8:15:ðð 16.11 19 3ð9 .84 486

_ ð7/ð7/98 ð8:29:59 6.97 16 226 .46 2897

_ ð7/ð7/98 ð8:44:57 24.97 25 635 .87 117ð5

_ ð7/ð7/98 ð8:59:56 53.18 28 494 .92 16719

_ ð7/ð7/98 ð9:14:54 62.45 24 318 .7ð 17373

_ ð7/ð7/98 ð9:29:53 71.6ð 31 526 .89 2ð635

_ ð7/ð7/98 ð9:44:51 43.ð6 29 574 .73 9642

_ ð7/ð7/98 ð9:59:49 48.ð8 19 399 .94 94ð9

5 ð7/ð7/98 1ð:14:47 11.97 15 243 4.45 3ð76

_ ð7/ð7/98 1ð:29:45 24.45 23 246 1.49 12556

Bottom


F14=Display by job type

á ñ

The Display by Interval display showed that the system was performing well formost of the users. Bob quickly rolled through all the displays, searching for theintervals where the average response times seemed noticeably higher than theaverage from the previous Display Performance Data display. Bob explainedthat if an intermittent response time problem existed, the shorter samplinginterval should help to highlight it. This logic is not foolproof, he added,because high transaction counts could still reduce the average response timeand mask a problem.

2. Bob found several intervals where the average response exceeded the 1.45second average significantly. He reviewed the data to see who was having theworst response times by:

a. Selecting option 5 (Display jobs) on the Display by Interval display

b. Pressing F24 (More keys)

c. Pressing F21 (Sort by response)


à ð Display Jobs

Interval . . . . : 1ð:14:47 Member . . . . . : PERFPROB

Elapsed time . . : ð9:53:52 Library . . . . : QPFRDATA





5 DSP18 ORDENTRYð1 ð14273 INT .55 17 15.6 1695 DSP19 ORDENTRYð2 ð14274 INT 1.55 21 13.4 252

DSP38 CREDITð3 ð14343 INT .71 6 3.ð 389

DSP14 RECVð1 ð14337 INT .ð4 1 2.ð 54

DSP34 SALESð2 ð14339 INT .32 11 1.4 243

DSP41 CREDITð1 ð14285 INT 1.93 24 1.3 493

DSP11 SHIPPINGð1 ð14289 INT .34 8 1.3 251

DSPð1 QSYSOPR ð14276 INT 2.1ð 51 .8 832

DSP22 SALESð1 ð14322 INT .55 28 .7 311

DSP4ð ACTRCVð1 ð14329 INT 2.32 62 .3 216

Bottom



á ñ

DSP18 and DSP19 had very high average responses, but the total number ofdisk I/Os for each of these jobs did not appear to be high. Sue confirmed thatthese were the order-entry users that had been complaining.

3. Bob entered option 5 (Display job detail) on the Display Jobs display for boththese jobs to further investigate them.

à ðDisplay Job Detail

Job . . . . . . . . : DSP18 Job type . . . . . . : INT

User . . . . . . . : ORDENTRYð1 Subsystem . . . . . : QINTER

Number . . . . . . : ð14273 Pool . . . . . . . . : ð4

Member . . . . . . . : PERFPROB Priority . . . . . . : 2ð

Library . . . . . : QPFRDATA Elapsed time . . . . : ð9:53:52

CPU Tns Average Disk Act-> Wait-> Act->

Interval Seconds Count Response I/O Wait Inel Inel

1ð:14:47 2.ð7ð 17 15.6 169 .9 .ð .ð

Bottom


F3=Exit F11=View 2 F12=Cancel F15=Sort by interval F24=More keys

á ñ

The Display Job Detail display allowed Bob to review the job’s resourcerequirements in greater detail. There are actually three views that make up thetotal detail picture.


As Bob scanned the interval data for DSP18, he remarked that the I/O countsper transaction did not justify the high response time average. Also, theWait->Inel and the Act->Inel were both zero, indicating that the job wasobtaining and holding an activity level when needed.

DSP19 showed the same situation.

Bob proceeded to review all the detail information for those two jobs. The followingconclusions were drawn:

� Both jobs were experiencing extremely wide variations in average responsetimes.

� These variations were occurring between 9:30 a.m. and 4:00 p.m. on both ofthe days that data was collected.

� Resource utilizations (processing unit, disk, and main storage) were not exces-sively high at those times.

Bob mentioned to Sue that these two jobs were definite candidates for furtherinvestigation. The sample data, however, would not give them the detail to deter-mine the actual cause of the erratic response times. They would need to captureanother type of data using the Start Performance Monitor command. Trace datawould give them greater detail on individual transactions, such as the program thatwas most likely running. First, though, they would meet with the order-entry per-sonnel to get more information on how they use the system and what types ofproblems they were experiencing.

Sue made arrangements for all of them to meet.

ReviewBob reviewed the system performance by using the advisor to confirm his earlierconclusion about system performance. Bob and Sue then used the graphics toquickly see if there were intervals that showed particularly bad response times andhigh use of system resources (higher than the guidelines). This helped Bob andSue focus on certain time intervals rather than the whole time period.

Bob decided that another way to quickly review the daily workload and its effect onsystem resources was to use the Display Performance Data (DSPPFRDTA)command. Rather than scan a printed report, he could interactively scan the col-lected sample data and isolate individual jobs that might be experiencing poor per-formance.

Normally, sample data could be collected with longer intervals (20 to 30 minutes)over longer periods (possibly all day) and be used to track the system’s perform-ance trends. This would enable a company to better manage its system’s resourcesand perhaps prevent major performance surprises.

Though Sue informed Bob of the particular jobs to investigate, Bob decided to ini-tially use the Display Performance Data command to review the overall system sta-tistics. He then proceeded to focus on individual jobs. Bob could have just as easilyselected only the order-entry jobs to look at. With no previous data to look at, Bobwanted to view all the jobs to get a feel for Armstrong’s system usage.

Even with this type of data, more detail on what a job is doing must be gatheredusing the trace parameter of the Start Performance Monitor command if the cause


of the problem is to be isolated. Tracing, however, can generate a great deal ofdata and could affect the end users when dumping the trace tables. Tracing shouldonly be used when in problem analysis mode and for shorter periods of time thanwhen collecting just sample data. Bob wants to talk to the end users to help himunderstand the problem and hopefully trace the system at the most opportune time.

Understanding the Symptoms of the ProblemThe two order-entry clerks met with Bob and Sue. Bob questioned them on thetypes of operations they performed, the problems with the system, and the types ofadditions or changes made that may be related to their problems. The followingitems were the results of their discussion:

1. Karen and Tim work in the order-entry department as clerks, processing theorders that are mailed in daily. They have their own private work station area,which restricts them from viewing each other’s activities. Early in the morning,the orders are broken into two stacks. Each of the clerks takes a stack andtypes it into its own separate transaction file on the system. At the end of theday, a batch program posts both transaction files to the main order file. Bas-ically, the orders are not officially in the system until the day after they aretyped.

2. Armstrong gives its largest customers the ability to call in urgent orders.Normally, only Karen has the authority to take the call and run a menu optionthat allows her to enter the order directly into the order file without being firstheld in a transaction file. This type of action usually occurs about twelve totwenty times a day and requires very short interactive response times becausethe customer is on the telephone as the order is entered. In the past, Karenhas had no problem with completing an entire telephone order in under 40seconds.

3. Recently, Armstrong had changed its policy, allowing all of its customers theability to call in urgent orders and inquire about order status. This has causedthe number of telephone orders to increase to a point where, now, both Karenand Tim are authorized to take telephone orders and enter them directly intothe order file. Each of them currently averages 40 calls a day. It seems to themthat the same menu option that took less than a second to bring up the displaycan now take 30 to 40 seconds. This caused serious problems with customerswaiting on the telephone.

Bob suggested a plan to help find the cause of the intermittent response timeproblem. Because transferring collected trace data to a database file might affect allof the users on the system, his plan involved controlling both the amount of timethat the monitor ran and when the trace data would be dumped to a file.

Sue would run the Start Performance Monitor (STRPFRMON) command withtracing active for one hour, and she would have the option to dump the trace tablelater. At the end of each run, she would call Karen or Tim and ask if the problemoccurred. If it had, Sue would give Bob a call, and, at the end of the day, explicitlydump the trace table with the Dump Trace (DMPTRC) command. If the problemhad not occurred, Sue would restart the monitor for another hour (the trace table isoverlaid with the new data). The problem happened often enough, so it should onlytake a few attempts to capture the necessary data.


They all agreed that this would be the best approach to resolve the problem withoutaffecting the rest of the users. They would start the procedure that afternoon. Bobmade arrangements to be back on Monday morning.

The following shows how Sue entered the Start Performance Monitor(STRPFRMON) command that afternoon:

à ðStart Performance Monitor (STRPFRMON)


Member . . . . . . . . . . . . . oeproblem Name, \GEN

Library . . . . . . . . . . . . QPFRDATA Name

Text 'description' . . . . . . . Order Entry Problem - Trace On

Time interval (in minutes) . . . 5 5, 1ð, 15, 2ð, 25, 3ð, 35...

Stops data collection . . . . . \ELAPSED \ELAPSED, \TIME, \NOMAX


Hour . . . . . . . . . . . . . . 1 ð-999

Minutes . . . . . . . . . . . . ð ð-99


Select jobs . . . . . . . . . . \ALL \ALL, \ACTIVE

Trace type . . . . . . . . . . . \ALL \NONE, \ALL

Dump the trace . . . . . . . . . \NO \YES, \NO



+ for more values

More...

F3=Exit F4=Prompt F5=Refresh F1ð=Additional parameters F12=Cancel

F13=How to use this display F24=More keys

á ñ

Notice that Trace type was changed to *ALL and Dump the Trace was changed to*NO.

During the first monitor run that afternoon, the problem did not occur. After thesecond monitor run ended, Sue received word that Tim experienced two majorresponse time problems when trying to enter a telephone order. No more monitorruns would be needed. At the end of the day (after most of the users had signedoff), Sue issued the Dump Trace (DMPTRC) command to prepare the necessarydata for Bob. The command looked like this:


à ðDump Trace (DMPTRC)


Member . . . . . . . . . . . . . oeproblem Name


Job queue . . . . . . . . . . . QCTL Name, \NONE

Library . . . . . . . . . . . QSYS Name, \LIBL, \CURLIB

Text 'description' . . . . . . . \BLANK

Bottom


F24=More keys

á ñ

With that accomplished, Sue was ready for Bob’s visit on Monday.

Analyzing the Data—Manager FeatureBob returned that Monday. After Sue related the activities of Friday afternoon, thenext step was to begin analyzing the data. Because the Display Performance Datacommand could only show sample data, Bob chose to print a job summary reportusing the Print Transaction Report (PRTTNSRPT) command. To reduce the amountof printed output to be analyzed, the report was limited to only the order-entry jobs.

à ðPrint Transaction Report (PRTTNSRPT)


Member . . . . . . . . . . . . . > oeproblem NAME

Report title . . . . . . . . . . > Order Entry Problem - Trace On

Report type . . . . . . . . . . \SUMMARY \SUMMARY, \TNSACT, \TRSIT...

+ for more values

Time period for report:

Starting time . . . . . . . . \FIRST TIME, \FIRST

Ending time . . . . . . . . . \LAST TIME, \LAST

Additional Parameters

Library . . . . . . . . . . . . QPFRDATA NAME

Report option . . . . . . . . . \SS \SS, \SI, \OZ, \EV, \HV, ' '

\EV

More...



á ñ




Select jobs . . . . . . . . . . \ALL Character value, \ALL

+ for more values

Omit jobs . . . . . . . . . . . > \NONE Character value, \NONE

+ for more values

Select users . . . . . . . . . . ordentry\ Name, generic\, \ALL .

+ for more values

Omit users . . . . . . . . . . . \NONE Name, generic\, \NONE

+ for more values

Select pools . . . . . . . . . . \ALL 1-16, \ALL

+ for more values

Omit pools . . . . . . . . . . . \NONE 1-16, \NONE

+ for more values

Select functional areas . . . . \ALL

+ for more values

Omit functional areas . . . . . \NONE

More...



á ñ

The following pages show selected sections from the Print Transaction Reportoutput with areas that Bob highlighted and discussed with Sue.

Job SummaryThe job summary for the order-entry department had the report and results shownin Figure 13-2 on page 13-29.

The following information was extracted from this report:

� The average response time for ORDENTRY01 was 3.2 seconds and at leastone of its transactions lasted 38.2 seconds. ORDENTRY01 is Tim’s userprofile. What was happening to that job?

� The average processing unit time per transaction was .24 seconds with at leastone transaction using .42 processor seconds. These times could not be thereason for the poor performance.

� ORDENTRY01 showed an average of 15 disk I/O operations per transactionand a worst case of 51 disk I/Os per transaction. Using .05 seconds as anaverage disk I/O service time, these numbers do not justify the exceptionallylong response times.

Sue asked Bob about the two in the Lock Conflict column. Bob remarked that thisvalue indicated the number of times that ORDENTRY01 needed to wait for anobject being held by another job.

This first page of the report indicated to Bob that Tim was definitely experiencingpoor response times, especially because his workload was similar to Karen’s. Bobneeded further information on what components of the response time were causingthe problem.


System Summary DataBob scanned further down the report to look at interactive transaction averages andexceptional-wait breakdown by job type. See Figure 13-3 on page 13-29.

The following performance information was extracted from this report:

� The average response time for 57 transactions was 1.613 seconds. This doesnot appear to be too high.

� However, the amount of processing unit time and disk time per transaction donot justify the 1.613 response time.

� Of the 1.613 seconds, 1.314 is spent in what is known as exceptional wait.The Excp Wait/Tns time is that portion of response time that cannot be attri-buted to processing unit or disk usage and is caused by contention for internalsystem resources (for example, waiting for a message queue). Normally, thisvalue should be less than 10 percent of the total average response time.

� Almost all of the exceptional wait time is being spent in the Lock Wait category.(Remember Sue’s question?)

Bob saw further data supporting the existence of a problem. He explained to Suethat these high numbers still reflected averages.

Analysis by Interactive Response TimeThe next section Bob looked at in the report (Analysis by Interactive ResponseTime) would help define the makeup of the transactions as shown in Figure 13-5on page 13-29.

The following information regarding response time was extracted from this tracereport:

� Of the 57 transactions measured, only two were greater than 10 seconds, andtogether they averaged 36.664 seconds.

� Almost all of that time (36.497 seconds) was spent as exceptional wait time.Remember that exceptional wait time is nonproductive time. What were thosetwo transactions doing?

This section of the report allows Bob to help evaluate performance versus objec-tives. Bob sees that both jobs are actually getting excellent service most of thetime. Two transactions, however, seem to be the source of the high averages.

Individual Transaction StatisticsBob needed to find out more about those two transactions, so he scanned furtherdown the report to the Individual Transaction Statistics section as shown inFigure 13-4 on page 13-29.

This section lists the individual transactions of various statistics (longest responsetime, processing unit, service time, and so on).

� ORDENTRY01 had two very long response times during the collection period,one at 14:23:27 (38.157 seconds) and the other at 14:32:08 (35.171 seconds).

� Bob noticed that, at both of these times, the program involved in the transactionwas ORD110.


Transactions with Longest Lock Wait TimeBob then looked at the Transactions with the longest lock wait time.

At the same time as those long transactions, ORDENTRY01 experienced extremelylong lock waits. In fact, almost the entire time spent in the transactions was spentwaiting on locks. Again, program ORD110 was involved.

Bob and Sue now had an idea of what was causing the problem. But what kind oflock was it and why couldn’t ORDENTRY01 get that lock? More questions neededanswering.

Longest Seize/Lock ConflictsBob’s next step was to go to the Longest Seize/Lock Conflicts section of the JobSummary Report. An example of this section is in Figure 13-7 on page 13-30.

This section lists the longest seize/lock conflicts in descending order with the time ithappened, the requesting job, the holding job, and the held object.

� The two transactions with the long response times for ORDENTRY01 are listedhere as the two longest instances of a lock conflict. The times coincide withthose earlier in the report.

� The holding job (preventing ORDENTRY01 from obtaining the necessary lock)in both instances was ORDENTRY02 (Karen’s interactive job).

� The lock request is for a file called ORDCTL in library OELIB.

Bob narrowed the problem to a conflict between the two jobs ORDENTRY01 andORDENTRY02. However, Bob wanted to get a little more information on the trans-actions that both ORDENTRY01 and ORDENTRY02 were running during the lockconditions. Further detail on the transactions in question could be explored byrunning another Print Transaction Report, this time asking for transition detail infor-mation. This report normally produces a great deal of output. The report could beefficiently reviewed by selecting only the jobs and times involved with the problem.

Bob entered the Print Transaction Report (PRTTNSRPT) command to get the fol-lowing display:




Member . . . . . . . . . . . . . > OEPROBLEM Name

Report title . . . . . . . . . . > 'Order Entry Problem - Transitional Report'

Report type . . . . . . . . . . \TRSIT \SUMMARY, \TNSACT, \TRSIT...

+ for more values

Time period for report:

Starting time . . . . . . . . 142ððð TIME, \FIRST

Ending time . . . . . . . . . 1435ðð TIME, \LAST

Additional Parameters


Report option . . . . . . . . . \SS \SS, \SI, \OZ, \EV, \HV, ' '

+ for more values

More...



á ñ



Select jobs . . . . . . . . . . \ALL Character value, \ALL

+ for more values

Omit jobs . . . . . . . . . . . > \NONE Character value, \NONE

+ for more values

Select users . . . . . . . . . . ordentry\ Name, generic\, \ALL .

+ for more values

Omit users . . . . . . . . . . . \NONE Name, generic\ \NONE

+ for more values

Select pools . . . . . . . . . . \ALL 1-16, \ALL

+ for more values

Omit pools . . . . . . . . . . . \NONE 1-16, \NONE

+ for more values

Select functional areas . . . . \ALL

+ for more values

Omit functional areas . . . . . \NONE

Bottom



á ñ

Notice that this time the output had been reduced to only showing informationabout the ORDENTRY01 and ORDENTRY02 jobs between 14:20:00 and 14:35:00.


Transition Report for ORDENTRY01The example report in Figure 13-8 on page 13-31 shows sections of the TransitionReport resulting from the PRTTNSRPT command just issued.

First, Bob scanned the Transition Report for ORDENTRY01 and noticed:

� At 14.23.28.135, ORDENTRY01 went into a lock wait for 37.819 secondsbecause of a request for file ORDCTL, over which job ORDENTRY02 had alock.

� ORD110 appeared to be the order-entry program asking for the file. Programsstarting with the letter Q (for example, QDBGETSQ) are normally IBM-suppliedsystem service routines.

� The same condition appeared to be happening at 14.32.08.691.

Transition Report for ORDENTRY02Next, Bob scanned the Transition Report for ORDENTRY02 and noted that at thetimes surrounding the lock waits for ORDENTRY01 (14.23.17.455 to 14.24.05.954and 14.31.48.059 to 14.32.43.665), ORDENTRY02 was also running ORD110. Anexample of this report is in Figure 13-9 on page 13-32.

Bob felt that exploring program ORD110 might help them understand why the lockswere occurring. Sue took Bob to the data processing department to talk withArmstrong’s lead programmer.

ReviewBob and Sue together determined that they would first select only the order-entryjobs when producing the transaction summary reports. They could do this onlybecause they had a good idea of the jobs in question. Under different circum-stances, using all of the jobs as input to the report may be necessary. Limit thenumber of transactions to analyze whenever possible.

Through the different sections of the report, Bob was able to isolate not only the jobin trouble, but also the individual transactions, times, and programs involved in theproblem.

It is important to note that Bob did not stop at finding the job having a problem. It ismuch more critical that the cause of the problem be found. ORDENTRY01 is thejob preventing ORDENTRY02 from obtaining service. By looking at job transitioninformation and matching times, the suspected program (ORD110) was identified.

With this information, Bob and Sue could now approach the application developersfor a solution.

Case Study Data Reports—Manager FeatureAnalyzing the data in the following example reports helped Bob and Sue under-stand their problem.


Job Summary Reports

Job Summary Report ð7/ð7/98 1ð:33:42

Job Summary Page ððð1

Order-Entry Problem - Trace On

Member . . . : OEPROBLEM Model/Serial . . : 51ð-2144/XX-XXXXX Main storage . . : 384.ð M Started . . . . : ð5/13/98 14:ð3:19

Library . . : QPFRDATA System name . . . : SYS4ðð Version/Release : 4/ 2.ð Stopped . . . . : ð5/13/98 14:57:5ð

\On/Off\ T P P Tot Response Sec CPU Sec ---- Average DIO/Transaction ----- Number K/T

Job User Job y t r Nbr ------------- ------------------ ------ Synchronous ----- --Async-- Cft /Tns

Name Name Number Pl p y g Tns Avg Max Util Avg Max DBR NDBR Wrt Sum Max Sum Max Lck Sze Sec

---------- ---------- ------ -- -- -- - ---- ------ ------ ---- ------ ------ ---- ---- ---- ---- ---- ---- ---- ------ -----

DSP18 ORDENTRYð1 ð31288 ð2 I 2ð N 26 3.2 38.2 .4 .24 .42 4 8 3 15 51 1 13 2 2 85

DSP19 ORDENTRYð2 ð31289 ð2 I 2ð N 31 .3 2.ð .5 .26 .87 3 9 2 14 29 74

Figure 13-2. Job Summary: Order-Entry Problem - Trace On

DATA FOR SELECTED TIME INTERVAL (OR TOTAL TRACE PERIOD IF NO TIME SELECTION).

INTERACTIVE TRANSACTION AVERAGES BY JOB TYPE.

T Avg CPU/ ----- Sync Disk I/O Rqs/Tns ----- Async W-I Excp Key/ Active Est

y Nbr Nbr Pct Tns Rsp Tns DB DB NDB NDB DIO Wait Wait Think K/T Of

p Prg Jobs Tns Tns /Hour (Sec) (Sec) Read Write Read Write Sum /Tns /Tns /Tns /Tns /Tns AWS

-- --- ---- ------ ----- ----- ------ ------ ----- ----- ----- ----- ----- ----- ------ ------- ------ ------ ---

I NO 2 57 1ðð.ð 62 1.613 .253 3 2 8 1 14 ð .ððð 1.314 79.ð92 55.254

EXCEPTIONAL WAIT BREAKDOWN BY JOB TYPE.

A-I Short Short Seize Lock Event Excs EM327ð DDM Svr Other

Wait Wait WaitX Wait Wait Wait ACTM Wait Wait Wait

Type Purge /Tns /Tns /Tns /Tns /Tns /Tns /Tns /Tns /Tns /Tns

---- ----- ------ ------ ------ ------ ------ ------ ------ ------ ------- ------

I NO .ððð .ð33 .ððð .ðð3 1.277 .ððð .ðð1 .ððð .ððð .

Figure 13-3. Data for Selected Time Interval

Job Summary Report ð7/ð7/98 18:33:42

Individual Transaction Statistics Page ðð21




TRANSACTIONS WITH LONGEST RESPONSE TIMES

Rank Value Time Program Job Name User Name Number Pool Type Priority

---- -------- ------------ ---------- ---------- ---------- ------ ---- ---- ---------

1 38.157 14.23.27.921 ORD11ð DSP18 ORDENTRYð1 ð31288 ð2 I 2ð

2 35.171 14.32.ð8.618 ORD11ð DSP18 ORDENTRYð1 ð31288 ð2 I 2ð

3 2.274 14.36.11.625 QUIINMGR DSP18 ORDENTRYð1 ð31288 ð2 I 2ð

4 1.951 14.41.22.7ð5 QUIINMGR DSP19 ORDENTRYð2 ð31289 ð2 I 2ð

5 1.543 14.ð5.56.163 QUIINMGR DSP18 ORDENTRYð1 ð31288 ð2 I 2ð

6 1.ð41 14.ð5.47.886 QUIINMGR DSP18 ORDENTRYð1 ð31288 ð2 I 2ð

7 .777 14.35.55.734 QUIINMGR DSP18 ORDENTRYð1 ð31288 ð2 I 2ð

8 .567 14.33.ð8.82ð QUIINMGR DSP19 ORDENTRYð2 ð31289 ð2 I 2ð

9 .562 14.35.4ð.131 QUIINMGR DSP18 ORDENTRYð1 ð31288 ð2 I 2ð

1ð .491 14.29.15.ð71 QUIINMGR DSP19 ORDENTRYð2 ð31289 ð2 I 2ð

Figure 13-4. Individual Transaction Statistics

ANALYSIS BY INTERACTIVE RESPONSE TIME.

Avg Cum Avg Cum ----- Sync Disk I/O Rqs/Tns ----- Async Excp Avg

Rsp Nbr Pct Pct CPU CPU CPU DB DB NDB NDB DIO Wait K/T

Category /Tns Tns Tns Tns /Tns Util Util Read Write Read Write Sum /Tns /Tns /Tns

---------------- ------- ----- ----- ----- ------- ----- ----- ----- ----- ----- ----- ----- ----- ------- --------

Sub-Second .332 51 89.5 89.5 .229 .2 .2 1 1 2 4 .ð37 51.979

1 - 1.999 Sec 1.512 3 5.3 94.8 .498 .2 7 12 9 28 1 1ð.ð28

2 - 2.999 Sec 2.274 1 1.8 96.6 .419 .2 2 25 1 23 51 13 1.185

3 - 4.999 Sec 96.6 .2

5 - 9.999 Sec 96.6 .2

GE 1ð Seconds 36.664 2 3.5 1ðð.1 .ð91 .2 2 2 36.497 233

Figure 13-5. Analysis by Interactive Response Time


TRANSACTIONS WITH LONGEST LOCK WAIT TIME

Rank Value Time Program Job Name User Name Number Pool Type Priority

---- -------- ------------ ---------- ---------- ---------- ------ ---- ---- ---------

1 37.822 14.23.27.921 ORD11ð DSP18 ORDENTRYð1 ð31288 ð2 I 2ð

2 34.977 14.32.ð8.618 ORD11ð DSP18 ORDENTRYð1 ð31288 ð2 I 2ð

3

4

5

6

7

8

9

1ð

Figure 13-6. Transactions with Longest Wait Time

Job Summary Report ð7/ð7/98 1ð:33:42

Longest Seize/Lock Conflicts Page ðð26




Job User Job Holder- Job Name.. User Name. Number Pool Type Pty

Rank Value Time Name Name Number Pl Typ Pty S/L Object- Type.. Library... File...... Member.... RRN......

---- -------- ------------ ---------- ---------- ------ -- --- --- --- ---------------------------------------------------------

1 37.819 14.23.28.135 DSP18 ORDENTRYð1 ð31288 ð2 I 2ð L HOLDER- DSP19 ORDENTRYð2 ð31289 ð2 I 2

OBJECT- DS OELIB ORDCTL ORDCTL

2 34.974 14.32.ð8.691 DSP18 ORDENTRYð1 ð31288 ð2 I 2ð L HOLDER- DSP19 ORDENTRYð2 ð31289 ð2 I 2ð


3 .ð9ð 14.32.43.67ð DSP18 ORDENTRYð1 ð31288 ð2 I 2ð S HOLDER- DSP19 ORDENTRYð2 ð31289 ð2 I 2ð


4 .ð89 14.24.ð5.959 DSP18 ORDENTRYð1 ð31288 ð2 I 2ð S HOLDER- DSP19 ORDENTRYð2 ð31289 ð2 I 2ð


Figure 13-7. Longest Seize/Lock Conflicts

Transition Reports


Transition Report ð7/ð7/98 11:41:45

Order-Entry Problem - Trace On Page ððð1

Member . . . : OEPROBLEM Model/Serial . . : 51ð-2144/XX-XXXXX Main storage . . : 384.ð M Started . . . . : ð5/13/98 14:2ð:ðð

Library . . : QPFRDATA System name . . . : SYS4ðð Version/Release : 4/ 2.ð Stopped . . . . : ð5/13/98 14:35:ðð

Job name . . : DSP18 User name . . . . : ORDENTRYð1 Job number . . . : ð31288 TDE/Pl/Pty/Prg . : ð1B4 ð2 2ð

Job type . . : I Elapsed Time -- Seconds Sync/Async Phy I/O -MPL-

----------------------- ------------------------ C I Last 4 Programs in Invocation Stack

State Wait Long Active Inel CPU DB DB NDB NDB u n ------------------------------------------

Time W A I Code Wait /Rsp\ Wait Sec Read Wrt Read Wrt Tot r l Last Second Third Fourth

------------ ----- ---- ------- ------- ------- -------- ---- ---- ---- ---- ---- -- -- ---------- ---------- --------------------

\\\\\ NO Is The New Purge Attribute. -

14.23.27.921 ->A 1

14.23.28.135 LKWT \/ 37.819/\ HOLDER-- DSP19 ORDENTRYð2 ð31289


14.23.28.136 W<- LKW .215 .ð78 1 QDBGETSQ ORD11ð QUIMNDRV QUICMENU

14.24.ð5.957 ->A 37.822 2

14.24.ð5.959 SZWT \/ .ð89/\ HOLDER-- DSP19 ORDENTRYð2 ð31289


14.24.ð6.ð77 W<- .12ð .ð14 2 QT3REQIO QWSGET ORD11ð QUMNDRV

---------- ORD11ð 38.157\ .ð92 ð ð 4 ð 4\

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< Later in the report... >>>>>>>>>>>

;>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

14.32.ð8.618 ->A 167.297 1

14.32.ð8.691 LKWT \/ 34.974/\ HOLDER-- DSP19 ORDENTRYð2 ð31289


14.32.ð8.692 W<- LKW .ð75 .ð75 1 QDBGETSQ ORD11ð QUIMNDRV QUICMENU

14.32.43.669 ->A 34.977 2

14.32.43.67ð SZWT \/ .ð9ð/\ HOLDER-- DSP19 ORDENTRYð2 ð31289


14.32.43.788 W<- .119 .ð14 2 QT3REQIO QWSGET ORD11ð QUIMNDRV

---------- ORD11ð 35.171\ .ð89 ð ð ð ð ð\

14.33.24.8ð6 ->A 41.ð18 .ðð1 .ðð1 1

2

14.33.24.918 W .112 .ð19 1 QT3REQIO QWSCLOSE QDMCLOSE ORD11ð

PAG= ð XSum= ð PWrt= 2

14.33.24.949 A .ð3ð .ðð1 1

14.33.25.ð12 W .ð64 .ð57 1 QT3REQIO QWSPUT QUIMNDRV QUICMENU

14.33.25.ð72 A .ð59 .ðð1 1

14.33.25.ð87 W<- .ð15 .ð14 1 QT3REQIO QWSGET QUIMNDRV QUICMENU

---------- QUIMNDRV .281\ .ð93 ð 2 ð ð 2\ PAG= ð XSum= ð PWrt= 2

Figure 13-8. Transition Report for ORDENTRY01


Transition Report ð7/ð7/98 11:31:45

Order-Entry Problem - Trace On Page ððð3

Member . . . : OEPROBLEM Model/Serial . . : 51ð-2144/XX-XXXXX Main storage . . : 384.ð M Started . . . . : ð5/13/98 14:2ð:ðð

Library . . : QPFRDATA System name . . . : SYS4ðð Version/Release : 4/ 2.ð Stopped . . . . : ð5/13/98 14:35:ðð

Job name . . : DSP19 User name . . . . : ORDENTRYð2 Job number . . . : ð31289 TDE/Pl/Pty/Prg . : ð1C3 ð2 2ð

Job type . . : I Elapsed Time -- Seconds Sync/Async Phy I/O -MPL-

----------------------- ------------------------ C I Last 4 Programs in Invocation Stack

State Wait Long Active Inel CPU DB DB NDB NDB u n ------------------------------------------

Time W A I Code Wait /Rsp\ Wait Sec Read Wrt Read Wrt Tot r l Last Second Third Fourth

------------ ----- ---- ------- ------- ------- -------- ---- ---- ---- ---- ---- -- -- ---------- ---------- --------------------

\\\\\ NO Is The New Purge Attribute. -

14.22.44.ð88 A .ð27 .ðð1 1

14.22.44.145 W .ð57 .ð55 1 QT3REQIO QWSPUT QUIMNDRV QUICMENU

14.22.44.222 A .ð77 1

14.22.44.237 W<- .ð16 .ð14 1 QT3REQIO QWSGET QUIMNDRV QUICMENU

---------- QUIMNDRV .35ð\ .ð88 ð 2 ð 1 3\ PAG= ð XSum= ð PWrt= 3

14.23.17.455 ->A 33.217 .ðð1 .ðð1 1

14.23.17.538 W<- .ð83 .ð82 1 QT3REQIO QWSGET ORD11ð QUIMNDRV

---------- ORD11ð .ð84\ .ð83 ð ð ð ð ð\

14.24.ð5.885 ->A 48.347 1

14.24.ð5.954 LKRL WAITER- DSP18 ORDENTRYð1 ð31288 37.819 SECS


14.24.ð6.ð49 SZRL WAITER- DSP18 ORDENTRYð1 ð31288 .ð89 SECS


14.24.ð6.ð61 W .176 .ð18 2 QT3REQIO QWSCLOSE QDMCLOSE ORD11ð


14.24.ð6.ð94 A .ð33 .ðð1 1

14.24.ð6.151 W .ð57 .ð55 1 QT3REQIO QWSPUT QUIMNDRV QUICMENU

14.24.ð6.228 A .ð77 1

14.24.ð6.243 W<- .ð16 .ð15 1 QT3REQIO QWSGET QUIMNDRV QUICMENU

---------- QUIMNDRV .359\ .ð89 ð 2 ð 1 3\ PAG= ð XSum= ð PWrt= 3

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< Later in the report... >>>>>>>>>>>

;>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

---------- QUIMNDRV .219\ .135 ð ð ð ð ð\

14.31.48.ð59 ->A 148.91ð 1

14.31.48.138 W<- .ð79 .ð77 1 QT3REQIO QWSGET ORD11ð QUIMNDRV

---------- ORD11ð .ð79\ .ð77 ð ð ð ð ð\

14.32.43.598 ->A 55.46ð .ðð1 .ðð1 1

14.32.43.665 LKRL WAITER- DSP18 ORDENTRYð1 ð31288 34.974 SECS


14.32.43.76ð SZRL WAITER- DSP18 ORDENTRYð1 ð31288 .ð9ð SECS


2 1

14.32.43.773 W .175 .ð18 2 QT3REQIO QWSCLOSE QDMCLOSE ORD11ð


14.32.43.8ð6 A .ð34 .ðð1 1

14.32.43.865 W .ð58 .ð57 1 QT3REQIO QWSPUT QUIMNDRV QUICMENU

14.32.43.942 A .ð77 1

14.32.43.957 W<- .ð15 .ð14 1 QT3REQIO QWSGET QUIMNDRV QUICMENU

---------- QUIMNDRV .36ð\ .ð91 ð 2 ð 1 3\ PAG= ð XSum= ð PWrt= 3

Figure 13-9. Transition Report for ORDENTRY02

Finding the Cause and Correcting the ProblemMike Brown was the senior applications programmer for Armstrong. Although notdirectly responsible for the order-entry application code, he could get the necessarydocumentation on ORD110 for Bob so that the record lock problem could be ana-lyzed.

1. Mike and Bob reviewed the program’s flowchart and source code and wereable to determine that ORD110 is an RPG/400 program that opens four files:

CUSMSTL Customer master file, input only

ORD110D Work station display file, input and output

ORDFILL Open orders file, output only (add)


ORDCTL Order control file, update

2. When Enter a new order is selected, ORD110 gets the single control recordfrom ORDCTL, which contains the next order number. Every order must have aunique order number.

3. The order-entry clerk responds to a prompt from display file ORD110D, askingthe clerk for the customer number. This customer number is then used by theprogram to get customer information from the CUSMSTL logical file, which inturn is presented to the clerk.

4. The clerk enters the necessary order data. When finished, the data is added toORDFILL as a new order.

5. Finally, the order number field of the control record is incremented by one andwritten back to ORDCTL. This allows the next order entered to have the nexthigher order number.

To Bob and Mike, the record lock conflict for ORDCTL was very obvious. With onlyone clerk using ORD110, the lock on the control record for update did not presentany problem. Armstrong’s original policy of having Karen as the only authorizeduser of ORD110 ensured that only one clerk would use ORD110. The other ordersreceived through the mail would not be assigned an order number until the nighttime batch job.

With the change in policy allowing multiple clerks to access ORD110, two clerkscould now attempt to enter an order at the same time. Only one clerk, though,could have the ORD110D display available to them because they would first needan exclusive lock on the control record. This record would be locked for the entireorder process. The requesting job’s display would be inhibited while the holding jobcompleted its order. Because the process only lasted about 30 seconds, the controlrecord was released before another requesting job timed out (the default wait timeon a record lock is 60 seconds). Had the time-out occurred, a function check wouldhave alerted the data processing department to a lock problem much sooner.

Mike quickly created a coding correction for ORD110 such that the reading, incre-menting, and updating of the control record would be done at the end of the orderprocess. This would allow the records to be locked and released in an instant andallow other jobs to do the same. Later on, a more efficient technique, such as usinga data area to store the control information, could be further explored.

Bob suggested to Sue that she run the performance monitor again for the next dayto measure the results of the change. The tracing option would be off and themonitor should run for the whole day. The order-entry department was to notify herif the response time situation occurred again. At a later date, Bob would return towork with Sue on developing some system monitoring practices that Armstrongshould use with Performance Tools.

Final ReviewThe case study you just read is an example of one person’s approach to solving atypical application performance problem. The methodology was based on severallogical steps:

1. Understand the symptoms of the problem

Initially, Bob was made aware of a problem with very little information to helphim to solve it. His first actions involved using commands to determine how well


the system was reacting to the overall workload. By isolating the users havingproblems and talking to them, he was able to identify their objectives and sub-stantiate the existence of a problem. The information he collected through theinterview with the order-entry personnel was critical in effectively analyzing thesituation.

2. Use tools to measure and define the problem

Performance Tools proved instrumental in determining not only what jobs werepart of the problem, but also what programs were involved and at what times.Problems like poor response time have a definite cause and, in most cases, theavailable system tools can help capture and report the vital information.Selecting specific times and jobs enabled Bob to reduce the amount of datathat had to be analyzed.

3. Isolate the cause and correct the problem

Bob and Mike carefully analyzed the problem and examined the application anddatabase design to develop a solution. They also ensured that the solution didnot produce negative effects for other jobs or cause incorrect data in the busi-ness operations.

4. Use tools to verify the problem is corrected

As mentioned earlier, Sue was to run the Start Performance Monitor(STRPFRMON) command the next day to measure the results of the change. Ifnew problems appeared, the above steps would be repeated until the solutionbecame acceptable.

Armstrong’s story is an example of a single, isolated problem. In some cases, asystem may have many different problems occurring at the same time. Prioritizethe problems to select which items to investigate first. When those problems areresolved, go after the next in line until the situation no longer justifies the time andeffort.

Another situation may be that a big problem is the result of an accumulation ofmany little design flaws. Some poor programming techniques may not affect oneuser much, but if multiplied by many jobs running at the same time, the result canbe dramatic.

Finally, the fact may be that the resources are seriously overcommitted and that itis time for a model upgrade or another disk controller. Use the capacity planningoption of Performance Tools to help you determine the additional resources neededto meet the performance objectives.

Learn the proper usage of the tools available to you, and start to put into place astrategy that will help you get the most out of your AS/400 system.


Chapter 14. Working with Historical Data—Agent Feature

This chapter describes the commands used to maintain historical data. Historicaldata is a summary of the performance data created by the performance monitor.

The Agent feature allows you to create historical data, which may then be analyzedon another AS/400 system that has the Manager feature installed. You can alsoanalyze the data using your own programs or queries. Appendix E, ManagingAS/400 System Performance in a Network, provides a customer scenario whichillustrates how a customer can create historical data at remote AS/400 sites. Thehistorical data is then transmitted to a central AS/400 system for analysis using theManager feature. The Manager feature provides the capability to present historicaldata in the form of graphics. Appendix D, Comparison of Performance Tools pro-vides more information on the functions provided in Performance Tools.

Note: Files are created to contain the historical data. For each performancemember with historical data, there is a single value for each type of informa-tion that can be graphed for each day of the member’s performance col-lection period. Thus, the amount of data is reduced and summarized intothe historical files. Once you have historical data for a member, you maychoose to delete the performance data (DLTPFRDTA) created through theinitial performance data collection to free file storage space.

Since historical data can help show trends in your system’s performance, it isrecommended that you create historical data in a given library for members that arecollected at the same time. (For example, you might want to compare data that wasall collected on Wednesdays from 8:00 a.m. to 12:00 p.m., whereas you probablywould not want a historical data with one member collected on Wednesday from8:00 a.m. to 12:00 p.m. and the other on Saturday from 1:00 to 5:00 p.m.)

To simplify data management, consider using separate libraries for comparable col-lections of data.

If you select option 3 (Work with historical data) on the Performance ToolsGraphics menu, the Work with Historical Data display appears.


à ðWork with Historical Data



1=Create historical data 4=Delete historical data

Member Historical

Option Name Data Date Time

_ Q95318ð843 NO 11/14/95 ð8:43:15

_ Q953171ð5ð NO 11/13/95 1ð:51:ðð

_ SATDATA YES 11/11/95 1ð:42:48

_ TESTDATA YES 11/11/95 1ð:26:12

_ NOV111995 NO 11/11/95 ð9:57:27

_ Q95315ð955 NO 11/11/95 ð9:55:41

_ FRIDAY YES 11/1ð/95 11:17:ð3

_ Q953132332 YES 11/ð9/95 23:32:19

_ Q9531214ð7 YES 11/ð8/95 14:ð7:11

_ Q953121142 NO 11/ð8/95 11:42:3ð

_ Q953111538 NO 11/ð7/95 15:39:ð2

More...

F3=Exit F5=Refresh F11=Display text F12=Cancel F15=Sort by Member

F16=Sort by text

á ñ

The member name, a historical data indicator, and the date and time you collectedeach set of performance data appear on this display. To display the member textdescription, press F11 (Display text). If you cannot find the data you want to workwith, use the appropriate function key to sort the sets of performance and historicaldata. You can sort them by member name, text description, or by the date and timethe member was created. When you find the data you want to work with, indicatethe function you want to perform by typing the appropriate option.

If you are searching for performance or historical data located in a library that isdifferent from the one currently listed in the Library field at the top of the display,type a new library name in the Library field and press the Enter key. A list of per-formance and historical data members available in the library you specifiedappears. You can then select one of them to work with.

Note: All of the members in the historical data must have unique names. If youcreate a member that has the same name as a historical data member, youmay want to change the name by using the Copy Performance Data(CPYPFRDTA) command to use the new member for historical purposes.

It is best to use the created name option (*GEN) on the STRPFRMON command tomake sure that the names of your performance data members are unique.

Create Historical DataTo create historical data for performance members, type a 1 (Create) by themembers, and press the Enter key. The Confirm Create of Historical Data displayappears.


à ðConfirm Create of Historical Data


Press Enter to confirm your choices for 1=Create.

Press F12=Cancel to return to change your choices.

Member Historical

Option Name data Date Time

1 Q95318ð843 NO 11/14/95 ð8:43:15

1 Q953171ð5ð NO 11/13/95 1ð:51:ðð

1 SATDATA YES 11/11/95 1ð:42:48

Bottom

F11=Display text F12=Cancel

á ñ

On this display, press the Enter key to create historical data for the members. Oncehistorical data has been created for a member, you can delete the original perform-ance data using the Delete Performance Data (DLTPFRDTA) command if the datais not needed for performance analysis, capacity planning, or performancegraphing.

Delete Historical DataTo delete the historical data created by the Create Historical Data command, type a4 (Delete) by members that contain historical data, and press the Enter key. Thisdoes not delete the original performance data.

Note: If the performance data for a member no longer exists, you cannot re-createhistorical data for that member after the historical data has been deleted.

Chapter 14. Working with Historical Data—Agent Feature 14-3


Chapter 15. Managing the Performance Data—Agent Feature

If you choose the Manage performance data option on the IBM Performance Toolsmenu for the Agent feature, the Manage Performance Data display appears.

à ðManage Performance Data






===> _____________________________________________________________________

__________________________________________________________________________


á ñ

From this display you can manage the performance data collected by the perform-ance monitor.

Delete Performance DataUse option 1 (Delete performance data) on the Manage Performance Data displayto delete performance data that you no longer need on your system. When youchoose option 1, the Delete Performance Data display appears.


à ðDelete Performance Data



4=Delete


_ XYZ 12/15/95 14:ð5:55

_ PERFTESTC4 2 hours w/ 5 minute intervals 12/15/95 ð8:ð5:48

_ PERFTESTC3 Duration of 2 hours 12/14/95 ð9:21:44

_ PERFTESTC2 12/11/95 14:42:46

Bottom

F3=Exit F5=Refresh F12=Cancel F15=Sort by member F16=Sort by text

á ñ

The members that appear on this display are those used on the Start PerformanceMonitor (STRPFRMON) command for the keyword MBR when data was collected.To delete a member from this list, type a 4 (Delete) next to the appropriate memberand press the Enter key. The member you delete is deleted from the following datacollection files:

QAPGSUMDQAPMAPPNQAPMASYNQAPMBSCQAPMBUSQAPMCIOPQAPMCONFQAPMDBMONQAPMDDIQAPMDIOPQAPMDISKQAPMDMPTQAPMECLQAPMETHQAPMFRLY

QAPMHDLCQAPMHDWRQAPMIDLCQAPMIOPDQAPMJOBSQAPMLAPDQAPMLIOPQAPMMIOPQAPMPOOLQAPMRESPQAPMRWSQAPMSAPQAPMSBSDQAPMSNAQAPMSNADS

QAPMSTNDQAPMSTNEQAPMSTNLQAPMSTNYQAPMSYSQAPMTJOBQAPMTSKQAPMX25QAPTLCKDQTRDMPTQTRIDXQTRJOBTQTRJSUMQTRTSUM

Copy Performance DataUse option 2 (Copy performance data) on the Manage Performance Data display tomake copies of performance data members. When you choose option 2, the SelectPerformance Member display appears.





1=Select


_ FRIDAY Performance Data for Friday 1ð/27/95 1ð:ð5:46

_ THURSDAY Performance Data for Thursday 1ð/26/95 12:ðð:34

1 WEDNESDAY Performance Data for Wednesday 1ð/25/95 13:5ð:15

1 TUESDAY Performance Data for Tuesday 1ð/24/95 13:55:ð8

1 MONDAY Performance Data for Monday 1ð/23/95 16:25:39

_ TESTRUN Test run of system 1ð/19/95 2ð:31:42

_ Q95291ð958 1ð/18/95 ð9:58:45

_ Q9529ð2ðð9 1ð/17/95 2ð:ð9:23

F3=Exit F12=Cancel F15=Sort by member F16=Sort by text



á ñ

The members that appear on this display are those used on the Start PerformanceMonitor (STRPFRMON) command for the keyword MBR when data was collected.To copy a member or members from the list, type a 1 (Select) next to the appro-priate member(s) and press the Enter key.

The Copy Performance Data Member display appears.

à ðCopy Performance Data Member


--------Copy From-------- --------Copy To--------

Member Library Member Library

MONDAY QPFRDATA MONDAY NEWLIB

TUESDAY QPFRDATA TUESDAY NEWLIB

WEDNESDAY QPFRDATA WEDNESDAY NEWLIB

Bottom

F3=Exit F12=Cancel

á ñ

This display shows you the members you selected to copy and where they are tobe copied to. For each member listed, type the name of the new member and thelibrary that contains it in the Copy To entries of the display, and then press the

Chapter 15. Managing the Performance Data—Agent Feature 15-3

Enter key. When the copy completes, you have exact copies of the old perform-ance members in the new performance members for the following files:

QAPMAPPNQAPMASYNQAPMBSCQAPMBUSQAPMCIOPQAPMCONFQAPMDBMONQAPMDDIQAPMDIOPQAPMDISKQAPMDMPTQAPMECLQAPMETH

QAPMFRLYQAPMHDLCQAPMHDWRQAPMIDLCQAPMIOPDQAPMJOBSQAPMLAPDQAPMLIOPQAPMMIOPQAPMPOOLQAPMRESPQAPMRWS

QAPMSAPQAPMSBSDQAPMSNAQAPMSNADSQAPMSTNDQAPMSTNEQAPMSTNLQAPMSTNYQAPMSYSQAMPTJOBQAPMTSKQAPMX25

Convert Performance Data (CVTPFRDTA) CommandUse option 4 (Convert performance data) on the Configure and Manage Toolsdisplay.

When you select option 4, the Convert Performance Data (CVTPFRDTA) displayappears. You can also use the CVTPFRDTA command to select the CVTPFRDTAdisplay.

à ðConvert Performance Data (CVTPFRDTA)


From library . . . . . . . . . . ___________ Name

To library . . . . . . . . . . . ___________ Name

Job Description . . . . . . . . \USRPRF____ Name, \USRPRF, \NONE

Library . . . . . . . . . . . ___________ Name, \LIBL, \CURLIB

Bottom


F24=More keys

á ñ

The Convert Performance Data (CVTPFRDTA) command converts performancedata from the previous release to the formats needed to be processed by thecurrent release of the performance measurement/analysis tools. First, the releaselevel on which the data was collected is determined. Then, all members of all filesthat need conversion are converted to the appropriate format.


The following files must be present for the conversion to take place:

The following files are copied, or converted if necessary, if they are present:

The conversion can be done in the library in which the current data resides, or in adifferent library. If the conversion is done in the same library, the current data isreplaced by the new data. If the conversion is done in a different library, the newdata exists in the new library while the current data continues to exist in the currentlibrary.

Note: If a different library is specified for the new data, those files in the currentlibrary that do not need conversion are copied to the new library.

To convert performance data collected prior to the current release, complete thefollowing items on the display.

From library Specifies the library that contains the data being converted.

To library Specifies the library that contains the converted data.

Job Description Specifies the job description used to submit the file-conversion jobfor batch processing.

The possible job description values are:

*USRPRF The job description defined for the submitting job’s user profile.

job-description-name Specify the name of the job description to be used.

*NONE A batch job is not submitted. Processing continues interactively while theuser waits.

Note: The user’s work station is not available for other use during this time, whichcan be significant for long jobs.

The possible library values are:

*LIBL The library list is used to locate the job description.

*CURLIB The current library for the job is used to locate the job description. If nocurrent library entry exists in the library list, QGPL is used.

library-name The library where the job description is located.

QAPMCIOPQAPMCONFQAPMDIOP

QAPMDISKQAPMJOBSQAPMLIOP

QAPMPOOLQAPMRESPQAPMSYS

QACPCNFGQACPGPHFQACPPROFQACPRESPQAITMONQAPGHSTDQAPGHSTIQAPGPKGF

QAPMASYNQAPMBSCQAPMBUSQAPMDMPTQAPMECLQAPMETHQAPMHDLC

QAPMIDLCQAPMLAPDQAPMMIOPQAPMSBSDQAPMTSKQAPMX25QAPTAPGP

Chapter 15. Managing the Performance Data—Agent Feature 15-5

| Convert Performance Thread Data (CVTPFRTHD) Command| The Convert Performance Thread Data (CVTPFRTHD) command converts perform-| ance data records collected by the STRPFRMON command. The specified member| of database file QAPMJOBS contains records with thread-level performance data.| You can use the CVTPFRTHD command to convert the data and write the records| to a member in file QAPMTJOB. The output file member contains records with job-| level performance data which are a total of the performance information for all| threads running within the job.

| à| ð| Convert Pfr Thread Data (CVTPFRTHD)

| Type choices, press Enter.

| Member . . . . . . . . . . . . . Name

| Library . . . . . . . . . . . . QPFRDATA Name

| Replace . . . . . . . . . . . . \YES \YES, \NO

| Bottom

| F3=Exit F4=Prompt F5=Refresh F12=Cancel F13=How to use this display

| F24=More keys

| á| ñ


Appendix A. Performance Tools CL Commands

The following commands are part of the Performance Tools Manager feature. Youmust have the Manager feature of the Performance Tools licensed programinstalled to use these commands.

The following commands are part of the Performance Tools Agent feature as wellas the Performance Tools Manager feature.

The following commands relate to the performance explorer tool and are part of theOS/400 product (with the exception of the PRTPEXRPT command, which is part ofthe Performance Tools licensed program). You do not have to have the Perform-ance Tools licensed program installed to use these commands.

The following commands are part of the OS/400 product and are described in theCL Reference and the Programming Reference Summary book. You do not have tohave the Performance Tools licensed program installed to use these commands.

The following commands are BEST/1 Capacity Planning commands. They are partof the Performance Tools licensed program and are described in the BEST/1Capacity Planning Tool book. You must have the Performance Tools licensedprogram installed to use these commands.

� ANZBESTMDL (Manager feature only)

ANZACCGRPANZDBFANZDBFKEYANZPFRDTAANZPGMCHGFCNARACHGGPHFMTCHGGPHPKGCPYFCNARACPYGPHFMTCPYGPHPKGCPYPFRDTACRTFCNARACRTGPHFMTCRTGPHPKGCRTHSTDTADLTFCNARA

DLTGPHFMTDLTGPHPKGDLTHSTDTADLTPFRDTADSPACCGRPDSPHSTGPHDSPPFRDTADSPPFRGPHENDJOBTRCPRTACTRPTPRTCPTRPTPRTJOBRPTPRTJOBTRCPRTLCKRPT

PRTPOLRPTPRTRSCRPTPRTSYSRPTPRTTNSRPTPRTTRCRPTSTRJOBTRCSTRPFRGSTRPFRTWRKFCNARAWRKSYSACT

ANZPFRDTACPYPFRDTACRTHSTDTA

DLTHSTDTADLTPFRDTADSPPFRDTA

PRTPEXRPTSTRPFRTWRKSYSACT

ADDPEXDFNCHGPEXDFNDLTPEXDTA

ENDPEXRMVPEXDFNSTRPEX

ADDPFRCOLCHGPFRCOLCVTPFRDTACVTPFRTHD

DMPTRCENDPFRCOLENDPFRMON

STRPFRCOLSTRPFRMONWRKPFRCOL

Copyright IBM Corp. 1998 A-1

ADDPEXDFN

� CRTBESTMDL (Manager and Agent feature)

� DLTBESTMDL (Manager and Agent feature)

� STRBEST (Manager feature only)

See Table D-2 on page D-2 for a table showing all performance-related commandsand whether they are part of OS/400, part of the Manager feature of PerformanceTools, or part of the Agent feature of Performance Tools.

ADDPEXDFN (Add Performance Explorer Definition) Command

FormatJob: B,I Pgm: B,I REXX: B,I Exec

55─ ─ADDPEXDFN─ ──(P)─DFN(──definition-name──)─ ──┬ ┬──────────────────────── ────5 │ │┌ ┐─\STATS─── └ ┘ ─TYPE(─ ──┼ ┼─\TRACE─── ─)─ └ ┘─\PROFILE─

5─ ──┬ ┬────────────────────────── ──────────────────────────────────────────5 │ │┌ ┐─\─────────── └ ┘ ─JOB(─ ──┼ ┼─\ALL──────── ─)─ │ │┌ ┐───────────

└ ┘───6

┴─┤ Job ├─

5─ ──┬ ┬──────────────────────────────────────────── ────────────────────────5| │ │┌ ┐─\NONE────────────────────────| └ ┘| ─TASK(─| ──┼ ┼─\ALL───────────────────────── ─)─| │ │┌ ┐──────────────────────────| └ ┘| ──(2)───

6┴──┬ ┬─task-name──────────

| └ ┘─generic\-task-name─

5─ ──┬ ┬────────────────────────────────────────────────────────────── ──────5 │ │┌ ┐─────────────────────────────────────────────── │ ││ │┌ ┐─\LIBL/─── └ ┘─PGM(───(3) ──(4)───

6┴──┼ ┼────────── ─program-name──┤ PGM Details ├─ ─)─

└ ┘─library/─

5─ ──┬ ┬───────────────────────── ───────────────────────────────────────────5 │ │┌ ┐─\FLAT─ └ ┘ ─DTAORG(───(5) ──┴ ┴─\HIER─ ─)─

5─ ──┬ ┬──────────────────────────────────────────── ────────────────────────5 │ │┌ ┐─1ðððð─────────────────── └ ┘ ─MAXSTG(────(6, 7) ──┴ ┴─maximum-K-bytes-storage─ ─)─

5─ ──┬ ┬───────────────────────────── ──┬ ┬─────────────────────────── ────────5 │ │┌ ┐─\STOPTRC─ │ │┌ ┐─\YES─ └ ┘ ─TRCFULL(───(8) ──┴ ┴─\WRAP──── ─)─ └ ┘ ─INCDEPJOB(───(9) ──┴ ┴─\NO── ─)─

5─ ──┬ ┬───────────────────────── ───────────────────────────────────────────5 │ │┌ ┐─\YES─ └ ┘ ─MRGJOB(────(10) ──┴ ┴─\NO── ─)─

5─ ──┬ ┬───────────────────────────────────── ───────────────────────────────5 └ ┘ ─INTERVAL(──────(11, 12) ─── ──milliseconds─ ─)─

A-2 Performance Tools V4R2

ADDPEXDFN

5─ ──┬ ┬──────────────────────────────────── ──┬ ┬───────────────────────── ───5| │ │┌ ┐───────────────── │ │┌ ┐─\NO──| │ ││ │┌ ┐─\CALLRTN── └ ┘| ─SLTEVT(────(13) ──┴ ┴─\YES─ ─)─| └ ┘| ─TRCTYPE(─ ──┬ ┬───

6┴──┼ ┼─\BASIC──── ─)─

| │ │├ ┤─\DSKIO1───| │ │├ ┤─\DSKIO2───| │ │├ ┤─\DSKSVR───| │ │├ ┤─\DSKSTG───| │ │├ ┤─\VRTADR───| │ │├ ┤─\PGMACT───| │ │├ ┤─\FILEOPEN─| │ │├ ┤─\PRFDTA───| │ │└ ┘─\TASKSWT──| └ ┘─\SLTEVT───────────

5─ ──┬ ┬───────────────────────────── ───────────────────────────────────────5 │ │┌ ┐─\BLANK──────── └ ┘ ─TEXT(─ ──┴ ┴─'description'─ ─)─

5─ ──┬ ┬───────────────────────────────────────────────────── ───────────────5| │ │┌ ┐─\ALL────────────────────────────| └ ┘| ─MCHINST(────(14) ──┼ ┼─\NONE─────────────────────────── ─)─| │ │┌ ┐────────────────────────────| └ ┘───(15) ───

6┴─machine-instruction-name─

5─ ──┬ ┬───────────────────────────────────────── ───────────────────────────5| │ │┌ ┐─\NONE────────────────| └ ┘| ─BASEVT(────(16) ──┼ ┼─\ALL───────────────── ─)─| │ │┌ ┐────────────────────| └ ┘───

6┴─event-identifier─

5─ ──┬ ┬───────────────────────────────────────── ───────────────────────────5| │ │┌ ┐─\NONE────────────────| └ ┘| ─PGMEVT(────(17) ──┼ ┼─\ALL───────────────── ─)─| │ │┌ ┐────────────────────| └ ┘───


5─ ──┬ ┬───────────────────────────────────────── ───────────────────────────5| │ │┌ ┐─\NONE────────────────| └ ┘| ─STGEVT(────(18) ──┼ ┼─\ALL───────────────── ─)─| │ │┌ ┐────────────────────| └ ┘───


5─ ──┬ ┬───────────────────────────────────────── ───────────────────────────5| │ │┌ ┐─\NONE────────────────| └ ┘| ─DSKEVT(────(19) ──┼ ┼─\ALL───────────────── ─)─| ├ ┤─\ALLSTR──────────────| │ │┌ ┐────────────────────| └ ┘───


5─ ──┬ ┬─────────────────────────────────────────── ─────────────────────────5| │ │┌ ┐─\NONE────────────────| └ ┘| ─FAULTEVT(────(20) ──┼ ┼─\ALL───────────────── ─)─| │ │┌ ┐────────────────────| └ ┘───


5─ ──┬ ┬───────────────────────────────────────── ───────────────────────────5| │ │┌ ┐─\NONE────────────────| └ ┘| ─JOBEVT(────(21) ──┼ ┼─\ALL───────────────── ─)─| │ │┌ ┐────────────────────| └ ┘───


5─ ──┬ ┬───────────────────────────────────────── ───────────────────────────5| │ │┌ ┐─\NONE────────────────| └ ┘| ─LCKEVT(────(22) ──┼ ┼─\ALL───────────────── ─)─| │ │┌ ┐────────────────────| └ ┘───


Appendix A. Performance Tools CL Commands A-3

ADDPEXDFN

5─ ──┬ ┬───────────────────────────────────────── ───────────────────────────5| │ │┌ ┐─\NONE────────────────| └ ┘| ─SAREVT(────(23) ──┼ ┼─\ALL───────────────── ─)─| ├ ┤─\ALLSTR──────────────| │ │┌ ┐────────────────────| └ ┘───


5─ ──┬ ┬──────────────────────────────────────────── ────────────────────────5| │ │┌ ┐─\NONE────────────────| └ ┘| ─DSKSVREVT(────(24) ──┼ ┼─\ALL───────────────── ─)─| │ │┌ ┐────────────────────| └ ┘───


5─ ──┬ ┬───────────────────────────────────────── ──────────────────────────5%| │ │┌ ┐─\NONE────────────────| └ ┘| ─JVAEVT(────(25) ──┼ ┼─\ALL───────────────── ─)─| │ │┌ ┐────────────────────| └ ┘───


Job: ┌ ┐─\ALL/─────── ┌ ┐─\ALL/───────────────├─ ──(1) ──┼ ┼───────────── ──┼ ┼───────────────────── ──┬ ┬─job-name────────── ─────┤ └ ┘─job-number/─ ├ ┤─generic\-user-name/─ └ ┘─generic\-job-name─ └ ┘─user-name/──────────

PGM Details: ┌ ┐─\ALL──────── ┌ ┐─\ALL────── ┌ ┐─\PGM──── ┌ ┐─4─────────├─ ──── ──┴ ┴─module-name─ ──┴ ┴─procedure─ ──┴ ┴─\SRVPGM─ ──┴ ┴─pane-size─ ────────┤

Notes:P All parameters preceding this point can be specified in positional form.1 A maximum of 10 repetitions.

| 2 A maximum of 10 repetitions.3 Only valid when TYPE(*PROFILE) is specified.4 A maximum of 16 repetitions.5 Only valid when TYPE(*STATS) is specified.6 Only valid when TYPE(*TRACE) is specified.7 Valid values range from 1K to 4,000,000 K (4 gigabytes).8 Only valid when TYPE(*TRACE) is specified.9 This parameter is not valid if JOB(*ALL) is specified.10 Only valid when DTAORG(*FLAT) and TYPE(*STATS) are specified.11 Only valid when TYPE(*PROFILE) or TYPE(*TRACE) is specified.12 Valid values range from 1 to 100 milliseconds.

| 13 Only valid when TYPE(*TRACE) is specified.

| 14 Only valid when SLTEVT(*YES) is specified.

| 15 A maximum of 50 repetitions.












ANZACCGRP

PurposeThe Add Performance Explorer Definition (ADDPEXDFN) command adds a newperformance explorer definition to the system. Each definition is stored as amember in the QAPEXDFN file in library QUSRSYS. A performance explorer defi-nition identifies the performance data that is to be collected during a performanceexplorer session. A session can be started using the STRPEX (Start PerformanceExplorer) command. When starting a new session, a performance explorer defi-nition name must be provided.

ExamplesExample 1: Using TYPE(*TRACE)

ADDPEXDFN DFN(TEST1) TYPE(\TRACE)

JOB(\) MAXSTG(5ððð)

This command adds a new performance definition named TEST1, which will resultin a member named TEST1 being added to file QAPEXDFN in library QUSRSYS.When this definition is used to start a performance explorer session (STRPEXcommand), detailed trace information will be collected for the job that invoked theSTRPEX command. A maximum of 5000 kilobytes of trace data will be collected.When the trace record storage area is full no more trace records will be collected.

Example 2: Using TYPE(*PROFILE)

ADDPEXDFN DFN(TEST2) TYPE(\PROFILE)

PGM((MYLIB/MYSRVPGM1 \ALL \ALL \SRVPGM))

This command adds a new performance explorer definition named TEST2. Whenthis definition is used to start a performance explorer session (STRPEX command),performance profile information for service program MYSRVPGM1 in library MYLIBwill be collected.

ANZACCGRP (Analyze Access Group) Command


55─ ─ANZACCGRP─ ──┬ ┬────────────────────────── ──────────────────────────────5 │ │┌ ┐─QAPAGDTA──── └ ┘ ─MBR(─ ──┴ ┴─member-name─ ─)─

5─ ──┬ ┬─────────────────────────── ──┬ ┬─────────────────────────────── ──────5 │ │┌ ┐─QPFRDATA───── │ │┌ ┐─\BLANK───────── └ ┘ ─LIB(─ ──┴ ┴─library-name─ ─)─ └ ┘─TITLE(─ ──┴ ┴──'report-title' ─)─

5─ ──┬ ┬──────────────────────── ────────────────────────────────────────────5 │ │┌ ┐─ANZACCGRP─ └ ┘ ─JOB(─ ──┼ ┼─\MBR────── ─)─ └ ┘─job-name──

5─ ──┬ ┬─────────────────────────────────────────────────────────── ────────5% │ │┌ ┐─\LIBL/──────── ┌ ┐─QPFRJOBD───────────── └ ┘ ─JOBD(─ ──┬ ┬ ──┼ ┼─────────────── ──┴ ┴─job-description-name─ ─)─ │ │├ ┤─\CURLIB/────── │ │└ ┘─library-name/─ └ ┘─\NONE───────────────────────────────────────


ANZDBF

PurposeThe Analyze Access Group (ANZACCGRP) command produces a report that sum-marizes the Process Access Group (PAG) data collected earlier with the DisplayAccess Group (DSPACCGRP) command. The report is useful in examining theprocess access group data from a large number of jobs.

| The environment section of the report shows a summary of all job types, the| average number of files, duplicate files, display files, I/O counts, and process-| access group size for the different job types. The job section shows information for| each selected job. The file section shows, for each open file, the file name and| type, the number of jobs using the file, the number of opens, the I/O count, and the| average ODP (Open Data Path) size.

The report output is written to the printer file QSYSPRT.

ExampleANZACCGRP

This command produces a report from the PAG data previously stored in thedefault location, member QAPAGDTA of QPFRDATA/QAPTPAGD, by the DisplayAccess Group (DSPACCGRP) command.

ANZDBF (Analyze Database File) Command


┌ ┐────────────────55─ ─ANZDBF─ ──(P) ─LIBL(─ ──(1)───

6┴─library-name─ ─)─ ──┬ ┬─────────────────────── ────5

│ │┌ ┐─ANZDBF─── └ ┘ ─JOB(─ ──┴ ┴─job-name─ ─)─


Notes:1 A maximum of 10 repetitionsP All parameters preceding this point can be specified in positional form.

PurposeThe Analyze Database File (ANZDBF) command produces two reports that showthe physical and logical files in a set of libraries and the relationships between thefiles. It saves the information in a database file for further analysis by the AnalyzeDatabase File Keys (ANZDBFKEY) command. Both reports (physical to logical filerelationships and logical to physical file relationships) are written to the printer fileQPPTANZD (two printer files with the same name are produced; one printer filecontains summary data; the other contains detail data). The data is saved inmember QAPTAZDR of the database file QPFRDATA/QAPTAZDR.


ANZPFRDTA

ExampleANZDBF LIBL(APDTA ARDTA)

This command produces reports showing the relationships for all files in theAccounts Payable (APDTA) and Accounts Receivable (ARDTA) data libraries.

ANZDBFKEY (Analyze Database File Keys) Command


55─ ─ANZDBFKEY─ ──┬ ┬───────────────────────── ───────────────────────────────5 │ │┌ ┐─\NUMLF──── └ ┘ ─FILE(─ ──┴ ┴─file-name─ ─)─

5─ ──┬ ┬─────────────────────────── ──┬ ┬──────────────────────── ─────────────5 │ │┌ ┐─5────────── │ │┌ ┐─ANZDBFKEY─ └ ┘ ─NUMLF(─ ──┴ ┴─file-count─ ─)─ └ ┘ ─JOB(─ ──┴ ┴─job-name── ─)─


PurposeThe Analyze Database File Keys (ANZDBFKEY) command produces, from the datacreated by the ANZDBF command, two reports showing the key structure of thedatabase files.

One report is written to the printer file QPPTALNK, the other to QPPTKEYMTX.

ExampleANZDBFKEY FILE(\NUMLF) NUMLF(2)

This command produces reports on the keys for all files that reference physical fileswith at least two associated logical files.

ANZPFRDTA (Analyze Performance Data) Command

FormatJob: I Pgm: I REXX: I Exec


ANZPGM

55─ ─ANZPFRDTA─ ──┬ ┬────────────────────────── ──────────────────────────────5 │ │┌ ┐─\SELECT───── └ ┘ ─MBR(─ ──┴ ┴─member-name─ ─)─

5─ ──┬ ┬─────────────────────────── ──┬ ┬───────────────────── ────────────────5 │ │┌ ┐─QPFRDATA───── └ ┘─PERIOD(──┤ Period ├─ └ ┘ ─LIB(─ ──┴ ┴─library-name─ ─)─

5─ ──┬ ┬──────────────────────── ──┬ ┬────────────────────────── ─────────────5% │ │┌ ┐─\────── │ │┌ ┐─\ALL──── └ ┘ ─OUTPUT(─ ──┴ ┴─\PRINT─ ─)─ └ ┘ ─DTATYPE(─ ──┴ ┴─\SAMPLE─ ─)─

Period: ┌ ┐─\FIRST───── ┌ ┐─\FIRST─────├─ ──┼ ┼─\SELECT──── ──┼ ┼──────────── ─)─ ──┬ ┬────────────────────────────────── ─┤ └ ┘─start-time─ └ ┘─start-date─ │ │┌ ┐─\LAST──── ┌ ┐─\LAST──── └ ┘ ─(─ ──┴ ┴─end-time─ ──┼ ┼────────── ─)─ └ ┘─end-date─

PurposeThe Analyze Performance Data (ANZPFRDTA) command produces recommenda-tions to improve the performance of the user's system. In the interactive mode, youcan request that the system make the recommended changes. In the batch mode,the recommended changes are printed, and you must then must enter the indi-vidual commands to make the recommended changes.

ExampleANZPFRDTA

This command provides recommendations for improving the performance of thesystem.

ANZPGM (Analyze Program) Command


┌ ┐────────────────55─ ─ANZPGM─ ──(P) ─LIBL(─ ──(1)───

6┴─library-name─ ─)─ ──┬ ┬─────────────────────── ────5

│ │┌ ┐─ANZPGM─── └ ┘ ─JOB(─ ──┴ ┴─job-name─ ─)─


Notes:1 A maximum of 10 repetitionsP All parameters preceding this point can be specified in positional form.


CHGFCNARA

PurposeThe Analyze Program (ANZPGM) command produces a report that shows the pro-grams and files in a set of libraries and the relationships between them. Bothreports are written to the printer file QPPTANZP (two print files are produced withthe same name; one printer file contains summary data; the other contains detaildata).

ExampleANZPGM LIBL(APPGM ARPGM)

This command produces reports showing the program and file relationships for allprograms in the Accounts Payable (APPGM) and Accounts Receivable (ARPGM)program libraries.

CHGFCNARA (Change Functional Area) Command


55─ ─CHGFCNARA──FCNARA(──functional-area-name──)───────────────────────────5

5─ ──(P)──┬ ┬─────────────────────────── ──┬ ┬───────────────────────────── ──────5 │ │┌ ┐─QPFRDATA───── │ │┌ ┐─\SAME───────── └ ┘ ─LIB(─ ──┴ ┴─library-name─ ─)─ └ ┘ ─TEXT(─ ──┼ ┼─\BLANK──────── ─)─

└ ┘──'description'

5─ ──┬ ┬────────────────────────────────────────────────── ─────────────────5% │ │┌ ┐─\SAME─────────────────────────────── └ ┘ ─JOB(─ ──┼ ┼─\NONE─────────────────────────────── ─)─ │ │┌ ┐───────────────────────────────── └ ┘──(1)───

6┴─── ─ ──┬ ┬───────────── ─job name─

└ ┘ ─ user-name/─

Notes:P All parameters preceding this point can be specified in positional form.1 A maximum of 250 repetitions

PurposeThe Change Functional Area (CHGFCNARA) command allows the user to changefunctional areas on the system. Functional areas are used by Performance Toolsfor reports and graphics. A functional area is a pre-defined list of job names and/oruser names that are to be included in a report or graph.

ExamplesExample 1: Changing Functional Area to Three Entries

CHGFCNARA FCNARA(PERSONNEL)

JOB(DAN/\N MARCY/\N RANDY/QPG\)

This command changes the functional area PERSONNEL to three entries:

� The user DAN.

� The user MARCY.

� Any job beginning with QPG submitted by RANDY.


CHGGPHFMT

The functional area is changed in the QPFRDATA library.

Example 2: Changing Functional Area to Four Entries

CHGFCNARA FCNARA('Performance Tools') LIB(RPFT)

JOB(PRT\ TERESA/\N KAREN/\N JIM/QPFRMON)

This command changes the functional area 'Performance Tools' to four entries:

� Any job beginning with PRT.

� The user TERESA.

� The user KAREN.

� Any QPFRMON job submitted by JIM.

The functional area is created in library RPFT.

CHGGPHFMT (Change Graph Format) Command


┌ ┐─QPFRDATA/─────55─ ─CHGGPHFMT──GPHFMT(─ ──┼ ┼─────────────── ─format-name──)─────────────────5 └ ┘─library-name/─

5─ ──── (P, K) ──┬ ┬───────────────────────────── ───────────────────────────────────5 │ │┌ ┐─\SAME───────── └ ┘ ─TEXT(─ ──┼ ┼─\BLANK──────── ─)─ └ ┘─'description'─

5─ ──┬ ┬────────────────────────────── ──────────────────────────────────────5 │ │┌ ┐─\SAME───────── └ ┘ ─TITLE(─ ──┼ ┼─\BLANK──────── ─)─ ├ ┤─\MBRTEXT────── └ ┘─'graph-title'─

5─ ──┬ ┬──────────────────────────────────── ────────────────────────────────5 │ │┌ ┐─\SAME──────────── └ ┘ ─SUBTITLE(─ ──┼ ┼─\BLANK─────────── ─)─ ├ ┤─\MBRTEXT───────── └ ┘─'graph-subtitle'─

5─ ──┬ ┬─────────────────────────── ──┬ ┬───────────────────────────── ────────5 │ │┌ ┐─\SAME──── │ │┌ ┐─\SAME───── └ ┘ ─GPHTYPE(─ ──┼ ┼─\SURFACE─ ─)─ └ ┘ ─DATATYPE(─ ──┼ ┼─\ALL────── ─)─ ├ ┤─\LINE──── ├ ┤─\FCNARA─── ├ ┤─\CBAR──── ├ ┤─\JOBTYPE── ├ ┤─\FBAR──── ├ ┤─\PRIORITY─ └ ┘─\SCATTER─ ├ ┤─\IOP────── ├ ┤─\DISK───── └ ┘─\CMNLINE──

5─ ──┬ ┬───────────────────────── ───────────────────────────────────────────5 │ │┌ ┐─\SAME─ └ ┘ ─AREAFILL(─ ──┼ ┼─\NO─── ─)─ └ ┘─\YES──

5─ ──┬ ┬──────────────────────────────────────── ────────────────────────────5 │ │┌ ┐─\SAME───────────────── └ ┘ ─REFLINE(─ ──┼ ┼─\NONE───────────────── ─)─ └ ┘─reference-line-number─


CHGGPHFMT

5─ ──┬ ┬────────────────────── ──┬ ┬────────────────────── ────────────────────5 └ ┘─XAXIS(──┤ Xaxis ├──)─ └ ┘─YAXIS(──┤ Yaxis ├──)─

5─ ──┬ ┬────────────────────────── ──────────────────────────────────────────5 └ ┘─FCNARA(───(1) ─┤ Fcnara ├──)─

5─ ──┬ ┬──────────────────────────────────────────────────────────────────── ─5 │ │┌ ┐─\SAME─────────────────────────────────────────── │ ││ │┌ ┐───────────────────────────────────────────── └ ┘ ─JOBTYPE(───(3) ──┴ ┴──(4)───

6┴─(─ ──┬ ┬─\ALL─────── ──┬ ┬───────────────── ─)─ ─)─

├ ┤─\ALLINTER── └ ┘─┤ More Values ├─ ├ ┤─\ALLBATCH── ├ ┤─\ALLSYSTEM─ ├ ┤─\ASJ─────── ├ ┤─\BCH─────── ├ ┤─\CA4─────── ├ ┤─\DDM─────── ├ ┤─\EVK─────── ├ ┤─\INT─────── ├ ┤─\MRT─────── ├ ┤─\PCS─────── ├ ┤─\PDJ─────── ├ ┤─\PJ──────── ├ ┤─\PTH─────── ├ ┤─\RDR─────── ├ ┤─\S36─────── ├ ┤─\SBS─────── ├ ┤─\SYS─────── ├ ┤─\WTR─────── └ ┘─\OTHER─────

5─ ──┬ ┬──────────────────────────────────────────────────────────── ───────5% ├ ┤─PRIORITY(───(5) ─┤ Priority ├──)─────────────────────────────── │ │┌ ┐─\SAME───────────────────────────────────── │ ││ │┌ ┐─────────────────────────────────────── ├ ┤ ─IOP(───(7) ──┴ ┴──(8)───

6┴─(─ ──┬ ┬─\AVG─ ──┬ ┬───────────────── ─)─ ─)───

│ │└ ┘─\MAX─ └ ┘─┤ More Values ├─ │ │┌ ┐─\SAME────────────────────────────────────── │ ││ │┌ ┐─────────────────────────────────────── ├ ┤ ─DISK(───(9) ──┴ ┴───(10) ───

6┴─(─ ──┬ ┬─\AVG─ ──┬ ┬───────────────── ─)─ ─)─

│ │└ ┘─\MAX─ └ ┘─┤ More Values ├─ ├ ┤─CMNLINE(────(11) ─┤ Cmnline ├──)──────────────────────────────── │ │┌ ┐─\SAME─────────────── └ ┘ ─ALLDATA(────(13) ──┴ ┴──┬ ┬───────────────── ─)──────────────────── └ ┘─┤ More Values ├─

More Values:├─ ──┬ ┬──────────────────────────────────────────────────────────── ────────┤ │ │┌ ┐─\DFT────────── └ ┘ ──┼ ┼─\BLANK──────── ──┬ ┬───────────────────────────────────── └ ┘─'description'─ │ │┌ ┐─7────(14) ──────────── ┌ ┐─\───────── └ ┘ ──┴ ┴─line-type-number─ ──┼ ┼─────────── └ ┘─character─

Xaxis: ┌ ┐─\SAME─────├─ ──┼ ┼─\TIME───── ──┬ ┬────────────────────────────────────────────────── ───┤ ├ ┤─\CPU────── │ │┌ ┐─\SAME────────── ┌ ┐─\SAME──────────────────── ├ ┤─\TNS────── └ ┘ ──┼ ┼─\DFT─────────── ──┼ ┼────────────────────────── ├ ┤─\NBRTNS─── ├ ┤─\BLANK───────── ├ ┤─\AUTO──────────────────── ├ ┤─\RSP────── └ ┘─'x-axis-title'─ └ ┘ ─start-number──end-number─ ├ ┤─\SYNCIO─── ├ ┤─\NBRSYNC── ├ ┤─\ASYNCIO── ├ ┤─\NBRASYNC─ ├ ┤─\TOTDSKIO─ └ ┘─\NBRDSKIO─


CHGGPHFMT

Yaxis: ┌ ┐─\SAME──────├─ ──┼ ┼─\CPU─────── ──┬ ┬────────────────────────────────────────────────── ──┤ ├ ┤─\TNS─────── │ │┌ ┐─\SAME────────── ┌ ┐─\SAME──────────────────── ├ ┤─\NBRTNS──── └ ┘ ──┼ ┼─\DFT─────────── ──┼ ┼────────────────────────── ├ ┤─\RSP─────── ├ ┤─\BLANK───────── ├ ┤─\AUTO──────────────────── ├ ┤─\SYNCIO──── └ ┘─'y-axis-title'─ └ ┘ ─start-number──end-number─ ├ ┤─\NBRSYNC─── ├ ┤─\ASYNCIO─── ├ ┤─\NBRASYNC── ├ ┤─\TOTDSKIO── ├ ┤─\NBRDSKIO── ├ ┤─\CMNIOP──── ├ ┤─\DSKIOP──── ├ ┤─\LWSIOP──── ├ ┤─\MFCIOP──── ├ ┤─\MFDIOP──── ├ ┤─\DSKARM──── ├ ┤─\PCTDSKOCC─ └ ┘─\CMNLINE───

Fcnara: ┌ ┐─\SAME───────────────────────────────────────────────────── │ │┌ ┐───────────────────────────────────────────────────────├─ ──┴ ┴──(2)───

6┴─(─ ──┬ ┬─\OTHER─────────────── ──┬ ┬───────────────── ─)─ ─────────┤

└ ┘─functional-area-name─ └ ┘─┤ More Values ├─

Priority: ┌ ┐─\SAME───────────────────────────────────────────────────────── │ │┌ ┐───────────────────────────────────────────────────────────├─ ──┴ ┴──(6)───

6┴─(─ ──┬ ┬─\ALL───────────────────── ──┬ ┬───────────────── ─)─ ─────┤

├ ┤─\OTHER─────────────────── └ ┘─┤ More Values ├─ └ ┘ ─lower-limit──upper-limit─

Cmnline: ┌ ┐─\SAME────────────────────────────────────────────────────────── │ │┌ ┐───────────────────────────────────────────────────────────├─ ──┴ ┴───(12) ───

6┴─(─ ──┬ ┬─\MAX───────────────────── ──┬ ┬───────────────── ─)─ ────┤

└ ┘─communications-line-name─ └ ┘─┤ More Values ├─

Notes:P All parameters preceding this point can be specified in positional form.K All parameters preceding this point are key parameters.1 Valid only when DATATYPE(*FCNARA) is specified2 A maximum of 16 repetitions3 Valid only when DATATYPE(*JOBTYPE) is specified4 A maximum of 16 repetitions5 Valid only when DATATYPE(*PRIORITY) is specified6 A maximum of 16 repetitions7 Valid only when *DATATYPE(*IOP) is specified8 A maximum of 2 repetitions9 Valid only when DATATYPE(*DISK) is specified.10 A maximum of 2 repetitions11 Valid only when DATATYPE(*CMNLINE) is specified.12 A maximum of 16 repetitions13 Valid only when DATATYPE(*ALL) is specified.14 Solid line


CHGGPHPKG

PurposeThe Change Graph Format (CHGGPHFMT) command changes a graph formatused to display performance and historical graphs that are created from perform-ance data members.

ExampleCHGGPHFMT GRAPH(FORMAT1) DATATYPE(\ALL)

ALLDATA(ABCCOMPANY \DFT 7)

This command changes the graph format named FORMAT1 in the QPFRDATAlibrary and groups all the data together. The data legend description isABCCOMPANY, and it is represented on the graph with a solid line.

CHGGPHPKG (Change Graph Package) Command


┌ ┐─QPFRDATA/─────55──CHGGPHPKG─ ──── (P, K) ─GPHPKG(─ ──┼ ┼─────────────── ─package-name──)─ ───────────5 ├ ┤─\CURLIB/────── └ ┘─library-name/─

5─ ──┬ ┬───────────────────────────── ───────────────────────────────────────5 │ │┌ ┐─\SAME───────── └ ┘ ─TEXT(─ ──┼ ┼─\BLANK──────── ─)─

└ ┘──'description'

5─ ──┬ ┬─────────────────────────────────── ────────────────────────────────5% │ │┌ ┐─\SAME───────────── └ ┘ ─GPHFMT(─ ──┼ ┼─\SELECT───(1) ──────── ─)─ │ │┌ ┐─────────────── └ ┘──(2)───

6┴─format-name─

Notes:P All parameters preceding this point can be specified in positional form.K All parameters preceding this point are key parameters.1 *SELECT is not valid in batch.2 A maximum of 25 repetitions

PurposeThe Change Graph Package (CHGGPHPKG) command changes a graph packageto include one or more graph formats.

ExamplesExample 1: Changing Graph Package to Contain Three Formats

CHGGPHPKG GPHPKG(EXAMPLE) TEXT('THIS IS AN

EXAMPLE') GPHFMT(GPH1 GPH9 GPH12)

This command changes a graph package called EXAMPLE to contain threeformats, GPH1, GPH9, and GPH12. This package is located in the default library,QPFRDATA.


CHGPEXDFN

Example 2: Changing Graph Package to Contain Two Formats

CHGGPHPKG GPHPKG(MYLIB/MYPKG)

TEXT('MY PACKAGE') GPHFMT(MYGPH1 MYGPH2)

This command changes a graph package called MYPKG to contain the formats ofMYGPH1 and MYGPH2. MYPKG is located in the MYLIB library.

CHGJOBTYP (Change Job Type) Command


55─ ─CHGJOBTYP─ ─MBR(──performance-data-member-name──)──────────────────────5

5─ ──(P)──┬ ┬──────────────────────────────────────────── ─────────────────────5% │ │┌ ┐─QPFRDATA────────────────────── └ ┘ ─LIB(─ ──┴ ┴─performance-data-library-name─ ─)─

Note:P All parameters preceding this point can be specified in positional form.

PurposeThe Change Job Type (CHGJOBTYP) command allows you to change the job typefor jobs that appear on the reports you produce using the Print Transaction Report(PRTTNSRPT) command. With this command you can change the characteristicsof a job (for example, from batch to interactive), correct a missing job type, orassign a job type.

Examples Example 1: Start a New Session

CHGJOBTYP MBR(TEST)

LIB(QPFRDATA)

This command changes MBR TEST from a batch job to an interactive job.

CHGPEXDFN (Change Performance Explorer Definition) Command


55──CHGPEXDFN─ ──── (P, K)─DFN(──definition-name──)─ ──┬ ┬──────────────────────── ──5 │ │┌ ┐─\SAME──── └ ┘ ─TYPE(─ ──┼ ┼─\STATS─── ─)─ ├ ┤─\TRACE─── └ ┘─\PROFILE─

5─ ──┬ ┬──────────────────────────── ────────────────────────────────────────5 │ │┌ ┐─\SAME───────── └ ┘ ─JOB(─ ──┼ ┼─\───────────── ─)─ ├ ┤─\ALL────────── │ │┌ ┐───────────

└ ┘──(2)───6

┴─┤ Job ├─


CHGPEXDFN

5─ ──┬ ┬──────────────────────────────────────────── ────────────────────────5| │ │┌ ┐─\SAME────────────────────────| └ ┘| ─TASK(─| ──┼ ┼─\NONE──────────────────────── ─)─| ├ ┤─\ALL─────────────────────────| │ │┌ ┐──────────────────────────| └ ┘| ──(3)───

6┴──┬ ┬─task-name──────────

| └ ┘─generic\-task-name─

5─ ──┬ ┬──────────────────────────────────────────────────────────────── ────5 │ │┌ ┐─\SAME─────────────────────────────────────────── │ ││ │┌ ┐─────────────────────────────────────── │ ││ ││ │┌ ┐─\LIBL/─── └ ┘ ─PGM(───(4) ──┴ ┴─(─ ──(5)───

6┴──┼ ┼────────── ─program-name──┤ Pgm ├─ ─)─ ─)─

└ ┘─library/─

5─ ──┬ ┬───────────────────────── ───────────────────────────────────────────5 │ │┌ ┐─\SAME─ └ ┘ ─DTAORG(───(6) ──┼ ┼─\FLAT─ ─)─ └ ┘─\HIER─

5─ ──┬ ┬──────────────────────────────────────────── ────────────────────────5 │ │┌ ┐─\SAME─────────────────── └ ┘ ─MAXSTG(────(7, 8) ──┴ ┴─maximum-K-bytes-storage─ ─)─

5─ ──┬ ┬───────────────────────────── ──┬ ┬───────────────────────────── ──────5 │ │┌ ┐─\SAME──── │ │┌ ┐─\SAME─ └ ┘ ─TRCFULL(───(9) ──┼ ┼─\STOPTRC─ ─)─ └ ┘ ─INCDEPJOB(────(10) ──┼ ┼─\YES── ─)─ └ ┘─\WRAP──── └ ┘─\NO───

5─ ──┬ ┬────────────────────────── ──────────────────────────────────────────5 │ │┌ ┐─\SAME─ └ ┘ ─MRGJOB(────(11) ──┼ ┼─\YES── ─)─ └ ┘─\NO───

5─ ──┬ ┬────────────────────────────────────────── ──────────────────────────5 │ │┌ ┐─\SAME───────────── └ ┘ ─INTERVAL(──────(12, 13) ──┴ ┴─sampling-interval─ ─)─

5─ ──┬ ┬───────────────────────────────────── ───────────────────────────────5| │ │┌ ┐─\SAME───────────| └ ┘| ─TRCTYPE(────(14) ──┼ ┼─\SLTEVT────(15) ───── ─)─| │ │┌ ┐───────────────| └ ┘───

6┴┬ ┬─\CALLRTN──

| ├ ┤─\BASIC────| ├ ┤─\DSKIO1───| ├ ┤─\DSKIO2───| ├ ┤─\DSKSVR───| ├ ┤─\DSKSTG───| ├ ┤─\VRTADR───| ├ ┤─\PGMACT───| ├ ┤─\FILEOPEN─| ├ ┤─\PRFDTA───| └ ┘─\TASKSWT──

5─ ──┬ ┬───────────────────────────── ──────────────────────────────────────5% │ │┌ ┐─\SAME───────── └ ┘ ─TEXT(─ ──┼ ┼─\BLANK──────── ─)─ └ ┘─'description'─

Job: ┌ ┐─\ALL/─────── ┌ ┐─\ALL/───────────────├─ ──┼ ┼───────────── ──┼ ┼───────────────────── ──┬ ┬─job-name────────── ───────┤ └ ┘─job-number/─ ├ ┤─generic\-user-name/─ └ ┘─generic\-job-name─ └ ┘─user-name/──────────

Pgm: ┌ ┐─\ALL──────── ┌ ┐─\ALL────── ┌ ┐─\PGM──── ┌ ┐─4─────────├─ ──┼ ┼─\PGM──────── ──┴ ┴─procedure─ ──┴ ┴─\SRVPGM─ ──┴ ┴─pane-size─ ────────────┤ └ ┘─module-name─


CHGPEXDFN

Notes:1 Only valid when TYPE(*STATS) or TYPE(*TRACE) is specified.P All parameters preceding this point can be specified in positional form.K All parameters preceding this point are key parameters.2 A maximum of 10 repetitions.

| 3 A maximum of 10 repetitions.4 Only valid when TYPE(*PROFILE) is specified.5 A maximum of 16 repetitions.6 Only valid when TYPE(*STATS) is specified.7 Valid values range from 1K to 4000000K (4 gigabytes).8 Only valid when TYPE(*TRACE) is specified.9 Only valid when TYPE(*TRACE) is specified.10 This parameter is not valid if JOB(*ALL) is specified.11 Only valid when DTAORG(*FLAT) and TYPE(*STATS) are specified.12 Only valid when TYPE(*PROFILE) or TYPE(*TRACE) is specified.13 Valid values range from 1 to 100 milliseconds.

| 14 Only valid when TYPE(*TRACE) is specified.

| 15 TRCTYPE(*SLTEVT) valid only when SLTEVT(*YES) specified on ADDPEXDFN| command.

PurposeThe Change Performance Explorer Definition (CHGPEXDFN) command changesan existing performance explorer definition. The current values stored in an existingdefinition are inserted when the CHGPEXDFN command is prompted. Each defi-nition is stored as a member in the QAPEXDFN file in library QUSRSYS. A per-formance explorer definition identifies the performance data to be collected during aperformance explorer session. A session can be started using the Start Perform-ance Explorer (STRPEX) command. When starting a new session, a performanceexplorer definition name must be provided.

Examples Example 1: Using TYPE(*TRACE)

CHGPEXDFN DFN(TEST1) TYPE(\TRACE)

JOB(\) MAXSTG(5ððð)

This command changes the performance definition named TEST1. When this defi-nition is used to start a performance explorer session (STRPEX command),detailed trace information will be collected for the job that invoked the STRPEXcommand. A maximum of 5000 kilobytes of trace data will be collected. When thetrace record storage area is full no more trace records will be collected.

Example 2: Using TYPE(*PROFILE)

CHGPEXDFN DFN(TEST2) TYPE(\PROFILE)

PGM((MYLIB/MYSRVPGM1 \ALL \ALL \SRVPGM))

This command changes the performance explorer definition named TEST2. Whenthis definition is used to start a performance explorer session (STRPEX command),performance profile information for service program MYSRVPGM1 in library MYLIBwill be collected.


CPYGPHFMT

CPYFCNARA (Copy Functional Area) Command


55─ ─CPYFCNARA──FROMFCNARA(──functional-area-name──)───────────────────────5

5─ ──┬ ┬─────────────────────────────── ─────────────────────────────────────5 │ │┌ ┐─QPFRDATA───── └ ┘ ─FROMLIB(─ ──┴ ┴─library-name─ ─)─

5─ ──┬ ┬──────────────────────────────────────── ────────────────────────────5 │ │┌ ┐─\FROMFCNARA────────── └ ┘ ─TOFCNARA(─ ──┴ ┴─functional-area-name─ ─)─

5─ ──(P)──┬ ┬───────────────────────────── ──┬ ┬─────────────────────── ─────────5% │ │┌ ┐─\FROMLIB───── │ │┌ ┐─\NO── └ ┘ ─TOLIB(─ ──┴ ┴─library-name─ ─)─ └ ┘ ─REPLACE(─ ──┴ ┴─\YES─ ─)─


PurposeThe Copy Functional Area (CPYFCNARA) command allows the user to copy afunctional area over to a new functional area. Functional areas are used for Per-formance Tools reports and graphics. A functional area is a pre-defined list of jobnames and user names that are included in a report or graph.

ExamplesExample 1: Copying in the Same Library

CPYFCNARA FROMFCNARA(PERSONNEL) TOFCNARA(MIKE)

This command copies the functional area PERSONNEL to the functional areaMIKE. Both functional areas are in the QPFRDATA library.

Example 2: Copying to a Different Library

CPYFCNARA FROMFCNARA('Performance Tools')

TOFCNARA(MIKE) TOLIB(USRLIB)

This command copies the functional area 'Performance Tools' to the functional areaMIKE in library USRLIB.

CPYGPHFMT (Copy Graph Format) Command


┌ ┐─QPFRDATA/─────55─ ─CPYGPHFMT─ ──(P) ─FROMFMT(─ ──┼ ┼─────────────── ─format-name──)─ ─────────────5 ├ ┤─\CURLIB/────── └ ┘─library-name/─


CPYGPHPKG

5─ ──┬ ┬─────────────────────────────────────────────── ─────────────────────5 │ │┌ ┐─\FROMLIB/───── ┌ ┐─\FROMFMT──── └ ┘ ─TOFMT(─ ──┼ ┼─────────────── ──┴ ┴─format-name─ ─)─ ├ ┤─\CURLIB/────── └ ┘─library-name/─

5─ ──┬ ┬─────────────────────── ────────────────────────────────────────────5% │ │┌ ┐─\NO── └ ┘ ─REPLACE(─ ──┴ ┴─\YES─ ─)─


PurposeThe Copy Graph Format (CPYGPHFMT) command copies an existing graph formatinto a graph format specified by the user.

ExamplesExample 1: Sending a Copy to the Default Library

CPYGPHFMT FROMFMT(MYFMT) TOFMT(YOURFMT)

This command makes a copy of MYFMT and sends it to YOURFMT in theQPFRDATA library.

Example 2: Sending a Copy to a Specified Library

CPYGPHFMT FROMFMT(MYLIB/FMT1)

TOFMT(YOURLIB/FMT2)

This command makes a copy of FMT1 in the MYLIB library and sends it to FMT2 inthe YOURLIB library.

CPYGPHPKG (Copy Graph Package) Command


┌ ┐─QPFRDATA/─────55─ ─CPYGPHPKG─ ──(P) ─FROMPKG(─ ──┼ ┼─────────────── ─package-name──)─ ────────────5 ├ ┤─\CURLIB/────── └ ┘─library-name/─

5─ ──┬ ┬──────────────────────────────────────────────── ────────────────────5 │ │┌ ┐─\FROMLIB/───── ┌ ┐─\FROMPKG───── └ ┘ ─TOPKG(─ ──┼ ┼─────────────── ──┴ ┴─package-name─ ─)─ ├ ┤─\CURLIB/────── └ ┘─library-name/─

5─ ──┬ ┬─────────────────────── ────────────────────────────────────────────5% │ │┌ ┐─\NO── └ ┘ ─REPLACE(─ ──┴ ┴─\YES─ ─)─



CPYPFRDTA

PurposeThe Copy Graph Package (CPYGPHPKG) command copies an existing graphpackage into a graph package specified by the user.

ExamplesExample 1: Sending a Copy to the Default Library

CPYGPHPKG FROMPKG(MYPKG) TOPKG(YOURPKG)

This command makes a copy of MYPKG and sends it to YOURPKG in theQPFRDATA library.

Example 2: Sending a Copy to a Specified Library

CPYGPHPKG FROMPKG(MYLIB/PKG1)

TOPKG(YOURLIB/PKG2)

This command makes a copy of PKG1 in the MYLIB library and sends it to PKG2in the YOURLIB library.

CPYPFRDTA (Copy Performance Data) Command


55─ ─CPYPFRDTA─ ──┬ ┬────────────────────────────── ──────────────────────────5 │ │┌ ┐─\SELECT───(1) ── └ ┘ ─FROMMBR(─ ──┴ ┴─member-name─ ─)─

5─ ──(P)──┬ ┬─────────────────────────────── ──┬ ┬──────────────────────────── ───5 │ │┌ ┐─QPFRDATA───── │ │┌ ┐─\FROMMBR──── └ ┘ ─FROMLIB(─ ──┴ ┴─library-name─ ─)─ └ ┘ ─TOMBR(─ ──┴ ┴─member-name─ ─)─

5─ ──┬ ┬───────────────────────────── ───────────────────────────────────────5 │ │┌ ┐─\FROMLIB───── └ ┘ ─TOLIB(─ ──┴ ┴─library-name─ ─)─


Notes:1 *SELECT is not valid when submitting a batch job.P All parameters preceding this point can be specified in positional form.

PurposeThe Copy Performance Data (CPYPFRDTA) command creates a copy of a per-formance data member.


CRTFCNARA

ExamplesExample 1: Showing List of Performance Data Members

CPYPFRDTA

This command shows a display for selecting from all of the performance datamembers in the QPFRDATA library. From this list, the user can select performancedata members to copy.

Example 2: Copying Data

CPYPFRDTA FROMMBR(MEMBER1) TOLIB(NEWLIB)

This command copies performance member MEMBER1 in library QPFRDATA tolibrary NEWLIB. The new copy in library NEWLIB keeps the name MEMBER1.

CRTFCNARA (Create Functional Area) Command


55─ ─CRTFCNARA──FCNARA(──functional-area-name──)───────────────────────────5

5─ ──(P)──┬ ┬─────────────────────────── ──┬ ┬───────────────────────────── ──────5 │ │┌ ┐─QPFRDATA───── │ │┌ ┐─\BLANK──────── └ ┘ ─LIB(─ ──┴ ┴─library-name─ ─)─ └ ┘ ─TEXT(─ ──┴ ┴─'description'─ ─)─

5─ ──┬ ┬────────────────────────────────────────── ─)───────────────────────5% │ │┌ ┐─\NONE──────────────────────── │ ││ │┌ ┐──────────────────────────── └ ┘ ─JOB(─ ──(1)──┴ ┴───

6┴ ──┬ ┬──────────── ─job-name─

└ ┘ ─user-name/─

Notes:P All parameters preceding this point can be specified in positional form.1 A maximum of 250 repetitions

PurposeThe Create Functional Area (CRTFCNARA) command allows the user to createfunctional areas on the system. Functional areas are used by PerformanceTools/400 for reports and graphics. A functional area is a pre-defined list of jobnames and/or user names that are to be included in a report or graph.

ExamplesExample 1: Creating a Functional Area in the Default Library

CRTFCNARA FCNARA(PERSONNEL)

JOB(MIKE/\N ROSS/\N QPFR\)

This command creates the functional area PERSONNEL with three entries:

� The user MIKE

� The user ROSS

� Any job beginning with QPFR

The functional area is created in the QPFRDATA library.


CRTGPHFMT

Example 2: Creating a Functional Area in a Specified Library

CRTFCNARA FCNARA('Performance Tools')

LIB(RPFT) JOB(TODD/\N MARTY/\N DEB/QPFRMON)

This command creates the functional area 'Performance Tools' with three entries:

� The user TODD

� The user MARTY

� Any QPFRMON job submitted by DEB

The functional area is created in the RPFT library.

CRTGPHFMT (Create Graph Format) Command


┌ ┐─QPFRDATA/─────55─ ─CRTGPHFMT──GPHFMT(─ ──┼ ┼─────────────── ─format-name──)─────────────────5 └ ┘─library-name/─

5─ ──┬ ┬───────────────────────────── ──(P)──┬ ┬────────────────────────────── ───5 │ │┌ ┐─\BLANK──────── │ │┌ ┐─\BLANK──────── └ ┘ ─TEXT(─ ──┴ ┴─'description'─ ─)─ └ ┘ ─TITLE(─ ──┼ ┼─\MBRTEXT────── ─)─ └ ┘─'graph-title'─

5─ ──┬ ┬──────────────────────────────────── ────────────────────────────────5 │ │┌ ┐─\BLANK─────────── └ ┘ ─SUBTITLE(─ ──┼ ┼─\MBRTEXT───────── ─)─ └ ┘─'graph-subtitle'─

5─ ──┬ ┬─────────────────────────── ──┬ ┬───────────────────────────── ────────5 │ │┌ ┐─\SURFACE─ │ │┌ ┐─\ALL────── └ ┘ ─GPHTYPE(─ ──┼ ┼─\LINE──── ─)─ └ ┘ ─DATATYPE(─ ──┼ ┼─\FCNARA─── ─)─ ├ ┤─\CBAR──── ├ ┤─\JOBTYPE── ├ ┤─\FBAR──── ├ ┤─\PRIORITY─ └ ┘─\SCATTER─ ├ ┤─\IOP────── ├ ┤─\DISK───── └ ┘─\CMNLINE──

5─ ──┬ ┬──────────────────────── ────────────────────────────────────────────5 │ │┌ ┐─\NO── └ ┘ ─AREAFILL(─ ──┴ ┴─\YES─ ─)─

5─ ──┬ ┬──────────────────────────────────────── ──┬ ┬─────────────────── ─────5 │ │┌ ┐─\NONE───────────────── └ ┘─XAXIS(──┤ Xaxis ├─ └ ┘ ─REFLINE(─ ──┴ ┴─reference-line-number─ ─)─

5─ ──┬ ┬─────────────────── ──┬ ┬────────────────────────────────────── ───────5 └ ┘─YAXIS(──┤ Yaxis ├─ │ │┌ ┐──────────────────── └ ┘─FCNARA(───(1) ──(2)───

6┴─(──┤ Fcnara ├──)─ ─)─


CRTGPHFMT

5─ ──┬ ┬──────────────────────────────────────────────────────────────── ────5 │ │┌ ┐───────────────────────────────────────────── └ ┘ ─JOBTYPE(───(3) ──(4)───

6┴─(─ ──┬ ┬─\ALL─────── ──┬ ┬───────────────── ─)─ ─)─

├ ┤─\ALLINTER── └ ┘─┤ More Values ├─ ├ ┤─\ALLBATCH── ├ ┤─\ALLSYSTEM─ ├ ┤─\ASJ─────── ├ ┤─\BCH─────── ├ ┤─\CA4─────── ├ ┤─\DDM─────── ├ ┤─\EVK─────── ├ ┤─\INT─────── ├ ┤─\MRT─────── ├ ┤─\PCS─────── ├ ┤─\PDJ─────── ├ ┤─\PJ──────── ├ ┤─\PTH─────── ├ ┤─\RDR─────── ├ ┤─\S36─────── ├ ┤─\SBS─────── ├ ┤─\SYS─────── ├ ┤─\WTR─────── └ ┘─\OTHER─────

5─ ──┬ ┬──────────────────────────────────────────────────────────── ───────5% │ │┌ ┐──────────────── ├ ┤─PRIORITY(───(5) ─── ───(6)───

6┴─┤ Priority ├─ ─)─────────────────────

│ │┌ ┐─────────────────────────────────────── ├ ┤ ─IOP(───(7) ─── ───(8)───

6┴─(─ ──┬ ┬─\AVG─ ──┬ ┬───────────────── ─)─ ─)───

│ │└ ┘─\MAX─ └ ┘─┤ More Values ├─ │ │┌ ┐─────────────────────────────────────── ├ ┤ ─DISK(───(9) ─── ────(10) ───

6┴─(─ ──┬ ┬─\AVG─ ──┬ ┬───────────────── ─)─ ─)─

│ │└ ┘─\MAX─ └ ┘─┤ More Values ├─ │ │┌ ┐─────────────── ├ ┤─CMNLINE(────(11) ─── ────(12) ───

6┴─┤ Cmnline ├─ ─)─────────────────────

└ ┘ ─ALLDATA(────(13) ─── ───┬ ┬───────────────── ─)──────────────────── └ ┘─┤ More Values ├─

More Values:├─ ──┬ ┬──────────────────────────────────────────────────────────── ────────┤ │ │┌ ┐─\DFT────────── └ ┘ ──┼ ┼─\BLANK──────── ──┬ ┬───────────────────────────────────── └ ┘─'description'─ │ │┌ ┐─7────(14) ──────────── ┌ ┐─\───────── └ ┘ ──┴ ┴─line-type-number─ ──┼ ┼─────────── └ ┘─character─

Xaxis: ┌ ┐─\TIME─────├─ ──┼ ┼─\CPU────── ──┬ ┬────────────────────────────────────────────────── ─)──┤ ├ ┤─\TNS────── │ │┌ ┐─\DFT─────────── ┌ ┐─\AUTO──────────────────── ├ ┤─\NBRTNS─── └ ┘ ──┼ ┼─\BLANK───────── ──┼ ┼────────────────────────── ├ ┤─\RSP────── └ ┘─'x-axis-title'─ └ ┘ ─start-number──end-number─ ├ ┤─\SYNCIO─── ├ ┤─\NBRSYNC── ├ ┤─\ASYNCIO── ├ ┤─\NBRASYNC─ ├ ┤─\TOTDSKIO─ └ ┘─\NBROSKIO─

Yaxis:


CRTGPHFMT

┌ ┐─\CPU───────├─ ──┼ ┼─\TNS─────── ──┬ ┬────────────────────────────────────────────────── ─)──┤ ├ ┤─\NBRTNS──── │ │┌ ┐─\DFT─────────── ┌ ┐─\AUTO──────────────────── ├ ┤─\RSP─────── └ ┘ ──┼ ┼─\BLANK───────── ──┼ ┼────────────────────────── ├ ┤─\SYNCIO──── └ ┘─'y-axis-title'─ └ ┘ ─start-number──end-number─ ├ ┤─\NBRSYNC─── ├ ┤─\ASYNCIO─── ├ ┤─\NBRASYNC── ├ ┤─\TOTDSKIO── ├ ┤─\NBRDSKIO── ├ ┤─\CMNIOP──── ├ ┤─\DSKIOP──── ├ ┤─\LWSIOP──── ├ ┤─\MFCIOP──── ├ ┤─\MFDIOP──── ├ ┤─\DSKARM──── ├ ┤─\PCTDSKOCC─ ├ ┤─\CMNLINE───

| └ ┘─\LGLDBIO───

Fcnara:├─ ──┬ ┬─\OTHER─────────────── ──┬ ┬───────────────── ─────────────────────────┤ └ ┘─functional-area-name─ └ ┘─┤ More Values ├─

Priority:├──(─ ──┬ ┬─\ALL───────────────────── ──┬ ┬───────────────── ─)────────────────┤ ├ ┤─\OTHER─────────────────── └ ┘─┤ More Values ├─ └ ┘ ─lower-limit──upper-limit─

Cmnline:├──(─ ──┬ ┬─\MAX───────────────────── ──┬ ┬───────────────── ─)────────────────┤ └ ┘─communications-line-name─ └ ┘─┤ More Values ├─

Notes:P All parameters preceding this point can be specified in positional form.1 Valid only when DATATYPE(*FCNARA) is specified2 A maximum of 16 repetitions3 Valid only when DATATYPE(*JOBTYPE) is specified4 A maximum of 16 repetitions5 Valid only when DATATYPE(*PRIORITY) is specified6 A maximum of 16 repetitions7 Valid only when *DATATYPE(*IOP) is specified8 A maximum of 2 repetitions9 Valid only when DATATYPE(*DISK) is specified.10 A maximum of 2 repetitions11 Valid only when DATATYPE(*CMNLINE) is specified.12 A maximum of 16 repetitions13 Valid only when DATATYPE(*ALL) is specified.14 Solid line

PurposeThe Create Graph Format (CRTGPHFMT) command creates a graph format usedto display performance and historical graphs that are created from performancedata members.


CRTGPHPKG

ExampleCRTGPHFMT GPHFMT(FORMAT1) TITLE(\MBRTEXT)

DATATYPE(\FCNARA)

FCNARA((ACCOUNTING 'ACCOUNTING')

(SALES 'SALES' 7 #) (OFFICE 'OFFICE' 7 @))

This command creates a graph format named FORMAT1 in the QPFRDATA library.The member that is presented on the graph using this format supplies the title forthe graph. The graph is a surface graph with no area fill nor a reference line. Thejobs presented on the graph are grouped according to three functional areas:

1. ACCOUNTING

2. SALES

3. OFFICE

The functional area of accounting is represented on the graph with a solid line withthe label, ACCOUNTING. If the format is displayed on a non-graphics work station,the asterisk (*) symbol is used to graphically represent the functional area ofaccounting. The functional areas, sales and office, are formatted in the samemanner as accounting, except SALES is graphically represented with the # symbolon a non-graphics work station, and OFFICE is graphically represented with the at@ symbol on a non-graphics work station.

CRTGPHPKG (Create Graph Package) Command


┌ ┐─QPFRDATA/─────55─ ─CRTGPHPKG─ ──(P) ─GPHPKG(─ ──┼ ┼─────────────── ─package-name──)─ ─────────────5 ├ ┤─\CURLIB/────── └ ┘─library-name/─

5─ ──┬ ┬───────────────────────────── ───────────────────────────────────────5 │ │┌ ┐─\BLANK──────── └ ┘ ─TEXT(─ ──┴ ┴─'description'─ ─)─

5─ ──┬ ┬─────────────────────────────────── ────────────────────────────────5% │ │┌ ┐─\SELECT───(1) ──────── │ ││ │┌ ┐─────────────── └ ┘ ─GPHFMT(─ ──┴ ┴──(2)───

6┴─format-name─ ─)─

Notes:P All parameters preceding this point can be specified in positional form.1 *SELECT not in batch.2 A maximum of 25 repetitions

PurposeThe Create Graph Package (CRTGPHPKG) command creates a graph package ofone or more graph formats.


CRTHSTDTA

ExamplesExample 1: Creating a Package Containing Three Formats

CRTGPHPKG GPHPKG(EXAMPLE)

TEXT('THIS IS AN EXAMPLE')

GPHFMT(GPH1 GPH9 GPH12)

This command creates a graph package called EXAMPLE, which contains threeformats, GPH1, GPH9, and GPH12. This package is saved in the default library,QPFRDATA.

Example 2: Creating a Package Containing Two Formats

CRTGPHPKG GPHPKG(MYLIB/MYPKG)

TEXT('MY PACKAGE') GPHFMT(MYGPH1 MYGPH2)

This command creates a graph package called MYPKG which contains the formatsof MYGPH1 and MYGPH2. MYPKG is saved in library MYLIB.

CRTHSTDTA (Create Historical Data) Command


55─ ─CRTHSTDTA──MBR(──member-name──)─ ──(P)──┬ ┬─────────────────────────── ─────5 │ │┌ ┐─QPFRDATA───── └ ┘ ─LIB(─ ──┼ ┼─\CURLIB────── ─)─ └ ┘─library-name─

5─ ──┬ ┬─────────────────────── ─────────────────────────────────────────────5 │ │┌ ┐─\NO── └ ┘ ─REPLACE(─ ──┴ ┴─\YES─ ─)─



PurposeThe Create Historical Data (CRTHSTDTA) command creates the files required tocreate historical graphs. If the files already exist, this command updates the files tocontain the specified data of a member. Historical data is an ongoing summary ofthe system containing the members that have been summarized using thiscommand.


DLTFCNARA

ExamplesExample 1: Creating Files in Default Library

CRTHSTDTA MBR(MONDAY)

This command creates files containing historical data that contain the membernamed MONDAY.

Example 2: Creating Files in Specified Library

CRTHSTDTA MBR(TUESPM) LIB(MYLIB)

This command creates files containing historical data that contain the membernamed TUESPM located in library MYLIB.

DLTFCNARA (Delete Functional Area) Command


55─ ─DLTFCNARA──FCNARA(──functional-area-name──)───────────────────────────5

5─ ──(P)──┬ ┬─────────────────────────── ──────────────────────────────────────5% │ │┌ ┐─QPFRDATA───── └ ┘ ─LIB(─ ──┴ ┴─library-name─ ─)─


PurposeThe Delete Functional Area (DLTFCNARA) command allows the user to deletefunctional areas from the system. Functional areas are used by PerformanceTools/400 for reports and graphics. A functional area is a pre-defined list of jobnames and user names that are included in a report or graph.

ExamplesExample 1: Deleting the Functional Area from the Default Library

DLTFCNARA FCNARA(PERSONNEL)

This command deletes the functional area named PERSONNEL from libraryQPFRDATA.

Example 2: Deleting the Functional Area from a Specified Library

DLTFCNARA FCNARA('Performance Tools')

LIB(RPFT)

This command deletes the functional area named 'Performance Tools' from libraryRPFT.


DLTGPHPKG

DLTGPHFMT (Delete Graph Format) Command


┌ ┐─QPFRDATA/─────55─ ─DLTGPHFMT─ ──(P) ─GPHFMT(─ ──┼ ┼─────────────── ─format-name──)─ ─────────────5% ├ ┤─\CURLIB/────── └ ┘─library-name/─


PurposeThe Delete Graph Format (DLTGPHFMT) command deletes a specific graphformat. This command also deletes the specified graph format from any packagesthat contain it.

ExamplesExample 1: Deleting a Graph Format in a Specified Library

DLTGPHFMT GPHFMT(MYLIB/MYFMT)

This command deletes the graph format named MYFMT located in the MYLIBlibrary.

Example 2: Deleting a Graph Format in the Default Library

DLTGPHFMT GPHFMT(TESTFMT)

This command deletes the graph format named TESTFMT located in the defaultlibrary QPFRDATA.

DLTGPHPKG (Delete Graph Package) Command


┌ ┐─QPFRDATA/─────55─ ─DLTGPHPKG─ ──(P) ─GPHPKG(─ ──┼ ┼─────────────── ─package-name──)─ ────────────5% ├ ┤─\CURLIB/────── └ ┘─library-name/─



DLTHSTDTA

PurposeThe Delete Graph Package (DLTGPHPKG) command deletes a graph package.

ExamplesExample 1: Deleting a Package in a Specified Library

DLTGPHPKG GPHPKG(MYLIB/MYPKG)

This command deletes the graph package MYPKG from library MYLIB.

Example 2: Deleting a Package in the Default Library

DLTGPHPKG GPHPKG(TESTPKG)

This command deletes graph package TESTPKG from default library QPFRDATA.

DLTHSTDTA (Delete Historical Data) Command


55─ ─DLTHSTDTA─ ──┬ ┬──────────────────────────────── ────────────────────────5 │ │┌ ┐─\SELECT───(1) ──────── │ ││ │┌ ┐─────────────── └ ┘ ─MBR(─ ──┴ ┴──(2)───

6┴─member-name─ ─)─

5─ ──(P)──┬ ┬─────────────────────────── ───────────────────────────────────────5 │ │┌ ┐─QPFRDATA───── └ ┘ ─LIB(─ ──┴ ┴─library-name─ ─)─


Notes:1 *SELECT not valid in batch.2 A maximum of 50 repetitionsP All parameters preceding this point can be specified in positional form.

PurposeThe Delete Historical Data (DLTHSTDTA) command deletes historical data for thespecified members from the historical database files.

ExampleDLTHSTDTA MBR(TEST1)

This command deletes historical database file member TEST1 from the historicaldatabase files found in the library QPFRDATA. QPFRJOBD is used for the jobdescription of the job.


DLTPFRDTA

DLTPEXDTA (Delete Performance Explorer Data) Command


55─ ─DLTPEXDTA─ ──(P)─DTAMBR(──data-member-name──)─ ────────────────────────────5

5─ ──┬ ┬─────────────────────────────────── ────────────────────────────────5% │ │┌ ┐─QPEXDATA────────── └ ┘ ─DTALIB(─ ──┴ ┴─data-library-name─ ─)─


PurposeThe DLTPEXDTA (Delete Performance Explorer Data) command deletes data thatwas collected by the performance explorer tool and was saved across a set ofphysical files in a particular library.

Restriction: The user must have object existence authority for each performanceexplorer database file in the specified library.

ExampleDLTPEXDTA DTAMBR(STATS3)

DTALIB(TESTLIB)

This command will remove members named STATS3 from the performanceexplorer database files in library TESTLIB. These members could have beencreated when the user ended a performance explorer data collection session(ENDPEX CL command) specifying 'SSNID(STATS3) DTAOPT(*LIB)DTALIB(TESTLIB)'.

DLTPFRDTA (Delete Performance Data)



DSPACCGRP

55─ ─DLTPFRDTA─ ──┬ ┬──────────────────────────────── ────────────────────────5 │ │┌ ┐─\SELECT───(1) ──────── │ ││ │┌ ┐─────────────── └ ┘ ─MBR(─ ──┴ ┴──(2)───

6┴─member-name─ ─)─

5─ ──(P)──┬ ┬─────────────────────────── ───────────────────────────────────────5 │ │┌ ┐─QPFRDATA───── └ ┘ ─LIB(─ ──┴ ┴─library-name─ ─)─


Notes:1 *SELECT not valid in batch.2 A maximum of 50 repetitionsP All parameters preceding this point can be specified in positional form.

PurposeThe Delete Performance Data (DLTPFRDTA) command deletes performance datamembers from the performance database files.

Example DLTPFRDTA MBR(TEST1)

This command deletes performance data member TEST1 from the performancedatabase files found in library QPFRDATA. QPFRJOBD is used for the jobdescription of the job.

DSPACCGRP (Display Access Group) Command


55─ ─DSPACCGRP─ ──┬ ┬─────────────── ──┬ ┬─────────────────────────────── ──────5 └ ┘─JOB(──┤ Job ├─ │ │┌ ┐─\BLANK───────── └ ┘ ─TITLE(─ ──┴ ┴─'report-title'─ ─)─

5─ ──┬ ┬──────────────────────── ──┬ ┬────────────────────────── ──────────────5 │ │┌ ┐─\────── │ │┌ ┐─QAPAGDTA──── └ ┘ ─OUTPUT(─ ──┼ ┼─\PRINT─ ─)─ └ ┘ ─MBR(─ ──┴ ┴─member-name─ ─)─ ├ ┤─\FILE── └ ┘─\BOTH──

5─ ──┬ ┬─────────────────────────── ──┬ ┬───────────────────── ───────────────5% │ │┌ ┐─QPFRDATA───── │ │┌ ┐─\YES─ └ ┘ ─LIB(─ ──┴ ┴─library-name─ ─)─ └ ┘ ─CLEAR(─ ──┴ ┴─\NO── ─)─

Job:


DSPACCGRP

┌ ┐─\─────────────────────────────────────────────────────────────├─ ──┼ ┼─\SEC────────────────────────────────────────────────────────── ─)───┤ ├ ┤─\INT────────────────────────────────────────────────────────── └ ┘─── ─ ──┬ ┬─────────────────────────────────────────────────────── │ │┌ ┐─\ALL───── └ ┘ ──┬ ┬───────────────────────────────────── ──┴ ┴─job-name─ │ │┌ ┐─\ALL─────── └ ┘ ──┬ ┬───────────────── ──┴ ┴─user-name/─ │ │┌ ┐─\ALL──────── └ ┘ ──┴ ┴─job-number/─

PurposeThe Display Access Group (DSPACCGRP) command shows, for each selected job,the process access group (PAG) size, the names and I/O counts for all open files,and the program data storage used. It also optionally writes this information to adatabase file for further analysis by the Analyze Process Access Group(ANZACCGRP) command.

Jobs can be selected for the report using several criteria, including job type, jobname, user name, and job number. The job and user names may be generic; onlythe first characters of the corresponding information for a job must match the speci-fied value for selection of the job. Only jobs that match all specified criteria areselected.

ExamplesExample 1: Displaying Access Group Information

DSPACCGRP JOB(GL\)

This command selects all active jobs with names starting with GL (since GL* is notone of the special single values, it is interpreted as a three-part job identifier; sinceonly one part is given, it is taken to be the job name, and the job number and username default to *ALL). Since no OUTPUT value is specified, output is displayed ifthere is only one GL job. A report is spooled if there is more than one GL job.

Example 2: Writing Access Group Information to a Database File

DSPACCGRP JOB(\ALL) OUTPUT(\FILE) MBR(SAMPLE1)

This command writes the PAG information for all active jobs to member SAMPLE1of the database file QPFRDATA/QAPTPAGD for later analysis by the ANZACCGRPcommand.

Example 3: Displaying All Access Group Information for a Job

DSPACCGRP JOB(ðð1234/\ALL/\ALL)

This command displays the PAG information for job number 001234. Since the jobnumber is guaranteed to uniquely identify the job, a report cannot be spooled (nomore than one job can be selected).

Example 4: Displaying Access Group Information for a Job

DSPACCGRP JOB(WILLIAMS/AP\)

This command selects all jobs with a user name of WILLIAMS and a job namebeginning with AP.


DSPHSTGPH

DSPHSTGPH (Display Historical Graph) Command


┌ ┐─QPFRDATA/─────55─ ─DSPHSTGPH──GRAPH(─ ──┼ ┼─────────────── ──┬ ┬─format-name──── ─)───────────5 ├ ┤─\CURLIB/────── └ ┘─package-name───(1)

└ ┘─library-name/─

5─ ──(P)──┬ ┬─────────────────────────── ──┬ ┬────────────────────────────── ─────5 │ │┌ ┐─QPFRDATA───── │ │┌ ┐─\SAME───────── └ ┘ ─LIB(─ ──┴ ┴─library-name─ ─)─ └ ┘ ─TITLE(─ ──┼ ┼─\BLANK──────── ─)─ ├ ┤─\MBRTEXT────── └ ┘─'graph-title'─

5─ ──┬ ┬────────────────────────────── ──┬ ┬────────────────────────── ────────5 │ │┌ ┐─\SAME────── │ │┌ ┐─\──────── └ ┘ ─SUBTITLE(─ ──┼ ┼─\BLANK───── ─)─ └ ┘ ─OUTPUT(─ ──┼ ┼─\PRINT─── ─)─ ├ ┤─\MBRTEXT─── ├ ┤─\PLOT──── └ ┘─'subtitle'─ └ ┘─\OUTFILE─

5─ ──┬ ┬──────────────────────────────── ────────────────────────────────────5 │ │┌ ┐─4214───────── └ ┘ ─PRTDEV(───(2) ──┼ ┼─4234───────── ─)─ ├ ┤─522X───────── ├ ┤─\IPDS──────── ├ ┤─\NONGRAPHIC── └ ┘─printer-name─

5─ ──┬ ┬────────────────────────────────────────────────────── ──────────────5 │ │┌ ┐─\PRTDEV────────────────────────────── │ ││ │┌ ┐─\LIBL/──────── └ ┘ ─OUTQ(───(3) ──┴ ┴──┼ ┼─────────────── ─output-queue-name─ ─)─ └ ┘─library-name/─

5─ ──┬ ┬──────────────────────────── ──┬ ┬───────────────────────────────── ───5 │ │┌ ┐─\PRTDEV─ │ │┌ ┐─1ðð─────────── └ ┘ ─PAGELEN(───(4) ──┼ ┼─51────── ─)─ └ ┘ ─PLTSPD(───(5) ──┴ ┴─plotter-speed─ ─)─ └ ┘─66──────

5─ ──┬ ┬───────────────────────────── ───────────────────────────────────────5 │ │┌ ┐─3───────── └ ┘ ─PLTPEN(───(6) ──┴ ┴─pen-width─ ─)─

5─ ──┬ ┬─────────────────────────────────── ─────────────────────────────────5 │ │┌ ┐─1─────────────── └ ┘ ─PLTADR(───(7) ──┴ ┴─plotter-address─ ─)─

5─ ──┬ ┬───────────────────────────────────────────── ───────────────────────5 │ │┌ ┐─LIBL/───────── └ ┘ ─OUTFILE(───(8) ──┼ ┼─────────────── ─file-name──)─ ├ ┤─\CURLIB/────── └ ┘─library-name/─

5─ ──┬ ┬─────────────────────────────────────────── ─────────────────────────5 │ │┌ ┐─\FIRST────── ┌ ┐─\REPLACE─ └ ┘ ─OUTMBR(─ ──┴ ┴─member-name─ ──┼ ┼────────── ─)─ └ ┘─\ADD─────

5─ ──┬ ┬───────────────────────── ───────────────────────────────────────────5 │ │┌ ┐─\GPHFMT─ └ ┘ ─TYPE(───(9) ──┴ ┴─\GPHPKG─ ─)─


DSPHSTGPH

5─ ──┬ ┬────────────────────────────────────────── ──────────────────────────5 │ │┌ ┐─\FIRST───── ┌ ┐─\LAST──── └ ┘ ─PERIOD(─ ──┼ ┼─\SELECT────(10) ──┼ ┼────────── ─)─ └ ┘─start-date─ └ ┘─end-date─

5─ ──┬ ┬───────────────────────── ───────────────────────────────────────────5 │ │┌ ┐─\NO── └ ┘ ─CRTHSTDTA(─ ──┴ ┴─\YES─ ─)─

5─ ──┬ ┬─────────────────────────────────────────────── ─────────────────────5 │ │┌ ┐─\SAME────────────────────────── └ ┘ ─XAXIS(─ ──┼ ┼─\AUTO────────────────────────── ─)─ └ ┘ ─starting-number──ending-number─

5─ ──┬ ┬─────────────────────────────────────────────── ─────────────────────5 │ │┌ ┐─\SAME────────────────────────── └ ┘ ─YAXIS(─ ──┼ ┼─\AUTO────────────────────────── ─)─ └ ┘ ─starting-number──ending-number─

5─ ──┬ ┬───────────────────────── ──┬ ┬──────────────────────── ───────────────5 │ │┌ ┐─\SAME─ │ │┌ ┐─DSPHSTGPH─ └ ┘ ─AREAFILL(─ ──┼ ┼─\YES── ─)─ └ ┘ ─JOB(─ ──┴ ┴─job-name── ─)─ └ ┘─\NO───

5─ ──┬ ┬────────────────────────────────────────────────────────── ─────────5% │ │┌ ┐─\NONE─────────────────────────────────── │ ││ │┌ ┐─\LIBL/──────── └ ┘ ─JOBD(────(11) ──┴ ┴──┼ ┼─────────────── ─job-description-name─ ─)─ ├ ┤─\CURLIB/────── └ ┘─library-name/─

Notes:1 A package-name is not valid if OUTPUT(*OUTFILE) is specified.

TYPE(*GPHPKG) must be specified for graph packages.P All parameters preceding this point can be specified in positional form.2 The PRTDEV parameter is valid only when OUTPUT(*PRINT) is specified.3 The OUTQ parameter is valid only when OUTPUT(*PRINT) is specified and an

actual printer name, for example, PRT01, PRT02, and so on, is not specified.4 The PRTDEV parameter is valid only when OUTPUT(*PRINT) is specified.5 The PLTSPD, PLTPEN, and PLTADR parameters are valid only when

OUTPUT(*PLOT) is specified.6 The PLTSPD, PLTPEN, and PLTADR parameters are valid only when


OUTPUT(*PLOT) is specified.8 The OUTFILE parameter and the OUTMBR parameter are valid only when

OUTPUT(*OUTFILE) is specified.9 A package-name is not valid if OUTPUT(*OUTFILE) is specified.

TYPE(*GPHPKG) must be specified for graph packages.10 *SELECT cannot be used in batch environment.11 JOBD(*NONE) must be specified if OUTPUT(*) or OUTPUT(*PLOT) is specified.

PurposeThe Display Historical Graph (DSPHSTGPH) command produces a graph from thehistorical data created by the Create Historical Data (CRTHSTDTA) command. TheDSPHSTGPH command is intended to give the user a historical perspective of thesystem in a graphical representation.

The CRTHSTDTA command summarizes the performance data collected by theStart Performance Monitor (STRPFRMON) command. The graph format must have


DSPHSTGPH

been defined by the Create Graph Format (CRTGPHFMT) command. The graphcan be directed to a graphics terminal, non-graphics terminal, printer, plotter, and agraphics data format (GDF) file that can be used by other systems. Historical datamembers can be selectively included in the graph.

Note: It is important that the CRTHSTDTA command has been run for each of themembers that the user wants to include in the graph. If the CRTHSTDTAcommand has not been run for a member, it is not included in the graphunless CRTHSTDTA(*YES) is specified.

ExamplesExample 1: Displaying a Data File

DSPHSTGPH GRAPH(GRAPHLIB/CPU)

This command shows the historical data file in library QPFRDATA on the user'sscreen. It is shown using the graph format CPU in library GRAPHLIB. All of thehistorical information in library QPFRDATA is included in the graph.

Example 2: Saving a Graph

DSPHSTGPH GRAPH(GRAPHLIB/CPU) OUTPUT(\OUTFILE)

OUTFILE(USERLIB/USERFILE) OUTMBR(TEST)

JOBD(\LIBL/QPFRJOBD)

This command submits a job to save the graph in a GDF file. The graph is saved inthe file USERLIB/USERFILE/TEST.

Example 3: Printing a Graph

DSPHSTGPH GRAPH(GRAPHLIB/CPU) OUTPUT(\PRINT)

PRTDEV(PRTð3) JOBD(\LIBL/QPFRJOBD)

This command submits a job to print the graph on the system printer namedPRT03.

Example 4: Printing All Graphs in a Package

DSPHSTGPH GRAPH(GRAPHLIB/PACKAGE1)

OUTPUT(\PRINT) PRTDEV(PRTð3) TYPE(\GPHPKG)


This command submits a job to print all of the graphs defined in PACKAGE1 inGRAPHLIB. The print job is sent to the system printer named PRT03. It uses thehistorical data members in QPFRDATA for its information.

Example 5: Displaying a Graph

DSPHSTGPH GRAPH(GRAPHLIB/CPU) OUTPUT(\)

PERIOD(112788 1ðð989)

This command displays a graph of historical information from 27 NOV 1988 to 9OCT 1989.

Example 6: Selecting Members to be in a Graph

DSPHSTGPH GRAPH(GRAPHLIB/CPU) MBRLIB(MONDAY)

OUTPUT(\) PERIOD(\SELECT \N)


DSPPFRDTA

This command shows the historical members selection menu for the members inlibrary MONDAY. The user then selects the members to be shown in the graph.

DSPPFRDTA (Display Performance Data) Command


55─ ─DSPPFRDTA─ ──┬ ┬────────────────────────── ──────────────────────────────5 │ │┌ ┐─\SELECT───(1) ── └ ┘ ─MBR(─ ──┴ ┴─member-name─ ─)─

5─ ──(P)──┬ ┬─────────────────────────── ──┬ ┬───────────────────── ─────────────5% │ │┌ ┐─QPFRDATA───── └ ┘─PERIOD(──┤ Period ├─ └ ┘ ─LIB(─ ──┴ ┴─library-name─ ─)─

Period: ┌ ┐─\FIRST───── ┌ ┐─\FIRST─────├─ ──┼ ┼─\SELECT──── ──┼ ┼──────────── ─)─ ──┬ ┬────────────────────────────────── ─┤ └ ┘─start-time─ └ ┘─start-date─ │ │┌ ┐─\LAST──── ┌ ┐─\LAST──── └ ┘ ─(─ ──┴ ┴─end-time─ ──┼ ┼────────── ─)─ └ ┘─end-date─

Notes:1 *SELECT cannot be used in a batch environment.P All parameters preceding this point can be specified in positional form.

PurposeThe Display Performance Data (DSPPFRDTA) command uses a series of displaysto show the performance data collected by the Start Performance Monitor(STRPFRMON) command.

ExamplesExample 1: Displaying List of Members

DSPPFRDTA

This command uses the Select Performance Member display to list the membersavailable in the default library QPFRDATA so the user can select a member todisplay performance data.

Example 2: Displaying Performance Data

DSPPFRDTA MBR(JUNE1)

This command displays the performance data stored in member JUNE1 located inlibrary QPFRDATA.


DSPPFRGPH

DSPPFRGPH (Display Performance Graph) Command


┌ ┐─QPFRDATA/─────55─ ─DSPPFRGPH──GRAPH(─ ──┼ ┼─────────────── ──┬ ┬─format-name──── ─)───────────5 ├ ┤─\CURLIB/────── └ ┘─package-name───(1)

└ ┘─library-name/─

5──MBR(──member-name──)─ ──┬ ┬─────────────────────────── ───────────────────5 │ │┌ ┐─QPFRDATA───── └ ┘ ─LIB(─ ──┴ ┴─library-name─ ─)─

5─ ──(P)──┬ ┬────────────────────────────── ────────────────────────────────────5 │ │┌ ┐─\SAME───────── └ ┘ ─TITLE(─ ──┼ ┼─\BLANK──────── ─)─ ├ ┤─\MBRTEXT────── └ ┘─'graph-title'─

5─ ──┬ ┬──────────────────────────────────── ────────────────────────────────5 │ │┌ ┐─\SAME──────────── └ ┘ ─SUBTITLE(─ ──┼ ┼─\BLANK─────────── ─)─ ├ ┤─\MBRTEXT───────── └ ┘─'graph-subtitle'─

5─ ──┬ ┬────────────────────────── ──┬ ┬──────────────────────────────── ──────5 │ │┌ ┐─\──────── │ │┌ ┐─4214───────── └ ┘ ─OUTPUT(─ ──┼ ┼─\PRINT─── ─)─ └ ┘ ─PRTDEV(───(2) ──┼ ┼─4234───────── ─)─ ├ ┤─\PLOT──── ├ ┤─522X───────── └ ┘─\OUTFILE─ ├ ┤─\IPDS──────── ├ ┤─\NONGRAPHIC── └ ┘─printer-name─

5─ ──┬ ┬────────────────────────────────────────────────────── ──────────────5 │ │┌ ┐─\PRTDEV────────────────────────────── │ ││ │┌ ┐─\LIBL/──────── └ ┘ ─OUTQ(───(3) ──┴ ┴──┼ ┼─────────────── ─output-queue-name─ ─)─ └ ┘─library-name/─

5─ ──┬ ┬──────────────────────────── ──┬ ┬───────────────────────────────── ───5 │ │┌ ┐─\PRTDEV─ │ │┌ ┐─1ðð─────────── └ ┘ ─PAGELEN(───(4) ──┼ ┼─51────── ─)─ └ ┘ ─PLTSPD(───(5) ──┴ ┴─plotter-speed─ ─)─ └ ┘─66──────

5─ ──┬ ┬───────────────────────────── ───────────────────────────────────────5 │ │┌ ┐─3───────── └ ┘ ─PLTPEN(───(6) ──┴ ┴─pen-width─ ─)─

5─ ──┬ ┬─────────────────────────────────── ─────────────────────────────────5 │ │┌ ┐─1─────────────── └ ┘ ─PLTADR(───(7) ──┴ ┴─plotter-address─ ─)─

5─ ──┬ ┬───────────────────────────────────────────── ───────────────────────5 │ │┌ ┐─QPFRDATA/───── └ ┘ ─OUTFILE(───(8) ──┼ ┼─────────────── ─file-name──)─ ├ ┤─\LIBL/──────── ├ ┤─\CURLIB/────── └ ┘─library-name/─

5─ ──┬ ┬───────────────────────────────────────────── ───────────────────────5 │ │┌ ┐─\FIRST────── ┌ ┐─\REPLACE─ └ ┘ ─OUTMBR(───(9) ──┴ ┴─member-name─ ──┼ ┼────────── ─)─ └ ┘─\ADD─────


DSPPFRGPH

5─ ──┬ ┬────────────────────────── ──────────────────────────────────────────5 │ │┌ ┐─\GPHFMT─ └ ┘ ─TYPE(────(10) ──┴ ┴─\GPHPKG─ ─)─

5─ ──┬ ┬─────────────────────────────────────────────── ─────────────────────5 │ │┌ ┐─\SAME────────────────────────── └ ┘ ─XAXIS(─ ──┼ ┼─\AUTO────────────────────────── ─)─ └ ┘ ─starting-number──ending-number─

5─ ──┬ ┬─────────────────────────────────────────────── ─────────────────────5 │ │┌ ┐─\SAME────────────────────────── └ ┘ ─YAXIS(─ ──┼ ┼─\AUTO────────────────────────── ─)─ └ ┘ ─starting-number──ending-number─

5─ ──┬ ┬───────────────────────── ──┬ ┬────────────────────────────── ─────────5 │ │┌ ┐─\SAME─ └ ┘─PERIOD(────(11) ─(──┤ Period ├──)─ └ ┘ ─AREAFILL(─ ──┼ ┼─\YES── ─)─ └ ┘─\NO───

5─ ──┬ ┬─────────────────────────── ─────────────────────────────────────────5 ├ ┤─SLTJOB(────(12) ─┤ Sltjob ├──)─ └ ┘─OMTJOB(────(14) ─┤ Omtjob ├──)─

5─ ──┬ ┬────────────────────────────────────── ──────────────────────────────5 │ │┌ ┐─\ALL───────────── │ ││ │┌ ┐───────────── ├ ┤ ─SLTUSER(────(16) ──┴ ┴───(17) ───

6┴─user-name─ ─)─

│ │┌ ┐─\NONE───────── │ ││ │┌ ┐───────────── └ ┘ ─OMTUSER(────(18) ───(19) ──┴ ┴───


5─ ──┬ ┬───────────────────────────────────────────────────── ───────────────5 │ │┌ ┐─\ALL─────────────────────────── │ ││ │┌ ┐─────────────────────────── ├ ┤ ─SLTPOOLS(────(20) ──┴ ┴───(21) ───

6┴─storage-pool-identifier─ ─)─

│ │┌ ┐─\NONE─────────────────────── │ ││ │┌ ┐─────────────────────────── └ ┘ ─OMTPOOLS(────(22) ───(23) ──┴ ┴───


5─ ──┬ ┬────────────────────────────────────────── ──────────────────────────5 │ │┌ ┐─\ALL────────────────── │ ││ │┌ ┐────────────────── ├ ┤ ─SLTSBS(────(24) ──┴ ┴───(25) ───

6┴─subsystem-name─ ─)─

│ │┌ ┐─\NONE────────────── │ ││ │┌ ┐────────────────── └ ┘ ─OMTSBS(────(26) ───(27) ──┴ ┴───


5─ ──┬ ┬───────────────────────────────────────────────────── ───────────────5 │ │┌ ┐─\ALL──────────────────────────── │ ││ │┌ ┐──────────────────────────── ├ ┤ ─SLTLINE(────(28) ──┴ ┴───(29) ───

6┴─communications-line-name─ ─)─

│ │┌ ┐─\NONE──────────────────────── │ ││ │┌ ┐──────────────────────────── └ ┘ ─OMTLINE(────(30) ───(31) ──┴ ┴───


5─ ──┬ ┬─────────────────────────────────────────── ─────────────────────────5 │ │┌ ┐─\ALL─────────────────── │ ││ │┌ ┐─────────────────── ├ ┤ ─SLTCTL(────(32) ──┴ ┴───(33) ───

6┴─controller-name─ ─)─

│ │┌ ┐─\NONE─────────────── │ ││ │┌ ┐─────────────────── └ ┘ ─OMTCTL(────(34) ───(35) ──┴ ┴───


5─ ──┬ ┬─────────────────────────────────────────────────── ─────────────────5 │ │┌ ┐─\ALL──────────────────────── │ ││ │┌ ┐──────────────────────── ├ ┤ ─SLTFCNARA(────(36) ──┴ ┴───(37) ───

6┴─functional-area-name─ ─)─

│ │┌ ┐─\NONE──────────────────── │ ││ │┌ ┐──────────────────────── └ ┘ ─OMTFCNARA(────(38) ───(39) ──┴ ┴───



DSPPFRGPH

5─ ──┬ ┬──────────────────────── ────────────────────────────────────────────5 │ │┌ ┐─DSPPFRGPH─ └ ┘ ─JOB(─ ──┼ ┼─\MBR────── ─)─ └ ┘─job-name──

5─ ──┬ ┬────────────────────────────────────────────────────────── ─────────5% │ │┌ ┐─\NONE─────────────────────────────────── │ ││ │┌ ┐─\LIBL/──────── └ ┘ ─JOBD(────(40) ──┴ ┴──┼ ┼─────────────── ─job-description-name─ ─)─ ├ ┤─\CURLIB/────── └ ┘─library-name/─

Period: ┌ ┐─\FIRST───── ┌ ┐─\FIRST─────├─ ──┴ ┴─start-time─ ──┼ ┼──────────── ─)─ ──┬ ┬────────────────────────────────── ─┤ └ ┘─start-date─ │ │┌ ┐─\LAST──── ┌ ┐─\LAST──── └ ┘ ─(─ ──┴ ┴─end-time─ ──┼ ┼────────── ─)─ └ ┘─end-date─

Sltjob: ┌ ┐─\ALL───────────────────────────────────────────────── │ │┌ ┐─────────────────────────────────────────────────├─ ──┴ ┴───(13) ───

6┴─── ─ ──┬ ┬───────────────────────────── ─job-name─ ──────────────┤

└ ┘ ──┬ ┬───────────── ─user-name/─ └ ┘ ─job-number/─

Omtjob: ┌ ┐─\NONE───────────────────────────────────────────── │ │┌ ┐─────────────────────────────────────────────────├─ ───(15) ──┴ ┴───

6┴─── ─ ──┬ ┬───────────────────────────── ─job-name─ ──────────────┤


Notes:1 A package-name is not valid if OUTPUT(*OUTFILE) is specified.

TYPE(*GPHPKG) must be specified for graph packages.P All parameters preceding this point can be specified in positional form.2 The PRTDEV and PAGELEN parameters are valid only when OUTPUT(*PRINT)

is specified.3 The OUTQ parameter is valid only when OUTPUT(*PRINT) is specified and an

actual printer name, for example, PRT01, PRT02, and so on, is not specified.4 The PRTDEV and PAGELEN parameters are valid only when OUTPUT(*PRINT)

is specified.5 The PLTSPD, PLTPEN, and PLTADR parameters are valid only when



OUTPUT(*PLOT) is specified.8 The OUTFILE and OUTMBR parameters are valid only when

OUTPUT(*OUTFILE) is specified.9 The OUTFILE and OUTMBR parameters are valid only when

OUTPUT(*OUTFILE) is specified.10 A package-name is not valid if OUTPUT(*OUTFILE) is specified.

TYPE(*GPHPKG) must be specified for graph packages.11 PERIOD contains two lists of two elements each. *N must be specified for any

element that precedes the value(s) to be specified to maintain its position in theparameter value sequence.

12 The SLTJOB parameter and the OMTJOB parameter cannot be specified at thesame time.


DSPPFRGPH

13 A maximum of 50 repetitions14 The SLTJOB parameter and the OMTJOB parameter cannot be specified at the

same time.15 A maximum of 50 repetitions16 The SLTUSER parameter and the OMTUSER parameter cannot be specified at

the same time.17 A maximum of 50 repetitions18 The SLTUSER parameter and the OMTUSER parameter cannot be specified at

the same time.19 A maximum of 50 repetitions20 The SLTPOOLS parameter and the OMTPOOLS parameter cannot be specified

at the same time21 A maximum of 16 repetitions22 The SLTPOOLS parameter and the OMTPOOLS parameter cannot be specified

at the same time23 A maximum of 16 repetitions24 The SLTSBS parameter and the OMTSBS parameter cannot be specified at the

same time.25 A maximum of 50 repetitions26 The SLTSBS parameter and the OMTSBS parameter cannot be specified at the

same time.27 A maximum of 50 repetitions28 The SLTLINE parameter and the OMTLINE parameter cannot be specified at the


same time.31 A maximum of 50 repetitions32 The SLTCTL parameter and the OMTCTL parameter cannot be specified at the


same time.35 A maximum of 50 repetitions36 The SLTFCNARA parameter and the OMTFCNARA parameter cannot be speci-

fied at the same time.37 A maximum of 50 repetitions38 The SLTFCNARA parameter and the OMTFCNARA parameter cannot be speci-

fied at the same time.39 A maximum of 50 repetitions40 The JOBD parameter is valid only when OUTPUT(*) or OUTPUT(*PLOT) is not

specified.

PurposeThe Display Performance Graph (DSPPFRGPH) command produces a graph fromthe performance data collected by the Start Performance Monitor (STRPFRMON)command.

The graph format must have been defined on the Create Graph Format(CRTGPHFMT) command. The graph can be sent as output to a graphics terminal,


DSPPFRGPH

a non-graphics terminal, a printer, a plotter, or to a graphics data format (GDF) filethat can be used by other systems. Jobs can be selectively included or omittedfrom the graph.

ExamplesExample 1: Displaying Performance Data Files

DSPPFRGPH GRAPH(GRAPHLIB/CPU)

MBR(QPFRDATA/JUN1) TITLE(\MBRTEXT)

This command displays the performance data files in library QPFRDATA memberJUN1. It is displayed as specified by graph format CPU in library GRAPHLIB. Thereport title is taken from the text of the member.

Example 2: Saving a Graph


MBR(JUN1) OUTPUT(\OUTFILE)

OUTFILE(USERLIB/USERFILE) OUTMBR(TEST)


This command submits a job to save the graph of performance data from filemember JUN1, which is in library QPFRDATA, in a GDF file. The graph is saved infile USERLIB/USERFILE/TEST (file member TEST in file USRFILE, which is inlibrary USRLIB).

Example 3: Printing a Graph


MBR(JUN1) OUTPUT(\PRINT)


This command submits a job to print the graph of performance data from filemember JUN1, which is in library QPFRDATA, on the system printer namedPRT03.

Example 4: Printing All Graphs

DSPPFRGPH GRAPH(GRAPHLIB/PACKAGE1)

MBR(JUN1) OUTPUT(\PRINT)


TYPE(\GPHPKG)

This command submits a job to print all of the graphs defined in PACKAGE1 inGRAPHLIB. The print job is sent to system printer PRT03. It's data source is inperformance data member JUN1 in library QPFRDATA.



MBR(JUN1) OUTPUT(\)

PERIOD((233ð)(ð13ð))

This command displays a graph of the data collected from 11:30 PM on the firstday of collection through 1:30 AM on the last day of collection. However, if datacollection started and ended on the same day, an error message is printed,because the specified ending date and time precedes the specified starting dateand time.


ENDJOBTRC



MBR(JUN1) OUTPUT(\)

PERIOD((233ð)(ð13ð)) SLTUSER(D46\)

This command displays a graph of the performance data collected for all the jobswhose user ID starts with D46 from 11:30 PM on the first day of collection through1:30 AM on the last day of collection. However, if data collection started and endedon the same day, an error message is printed, because the specified ending dateand time precedes the specified starting date and time.

ENDJOBTRC (End Job Trace) Command


55─ ─ENDJOBTRC─ ──┬ ┬────────────────────────── ──────────────────────────────5 │ │┌ ┐─QAJOBTRC──── └ ┘ ─MBR(─ ──┴ ┴─member-name─ ─)─

5─ ──┬ ┬─────────────────────────── ──┬ ┬─────────────────────────── ──────────5 │ │┌ ┐─QPFRDATA───── │ │┌ ┐─\NONE──── └ ┘ ─LIB(─ ──┴ ┴─library-name─ ─)─ └ ┘ ─RPTTYPE(─ ──┼ ┼─\DETAIL── ─)─ ├ ┤─\SUMMARY─ └ ┘─\BOTH────

5─ ──(P)──┬ ┬─────────────────────────────── ───────────────────────────────────5 │ │┌ ┐─\BLANK───────── └ ┘ ─TITLE(─ ──┴ ┴─'report-title'─ ─)─

5─ ──┬ ┬───────────────────────────────── ───────────────────────────────────5 │ │┌ ┐─\FIRST────────── └ ┘ ─STRSEQ(─ ──┴ ┴─sequence-number─ ─)─

5─ ──┬ ┬───────────────────────────────── ───────────────────────────────────5 │ │┌ ┐─\LAST─────────── └ ┘ ─ENDSEQ(─ ──┴ ┴─sequence-number─ ─)─

5─ ──┬ ┬────────────────────────────── ──┬ ┬────────────────────────────── ────5 │ │┌ ┐─QT3REQIO───── │ │┌ ┐─QWSGET─────── └ ┘ ─ENDTNS(─ ──┴ ┴─program-name─ ─)─ └ ┘ ─STRTNS(─ ──┴ ┴─program-name─ ─)─

5─ ──┬ ┬──────────────────────── ────────────────────────────────────────────5 │ │┌ ┐─ENDJOBTRC─ └ ┘ ─JOB(─ ──┼ ┼─\MBR────── ─)─ └ ┘─job-name──




ENDPEX

PurposeThe End Job Trace (ENDJOBTRC) command turns off the OS/400 system jobtracing function that was started by the Start Job Trace (STRJOBTRC) command,saves all collected trace records in a database file, and optionally produces reportsused to analyze the data from a performance viewpoint (the Print Job Trace(PRTJOBTRC) command may subsequently be used to produce reports from thesource data).

ExamplesExample 1: Stopping Job Tracing

ENDJOBTRC

This command stops tracing and saves the created trace records inQPFRDATA/QAPTTRCJ, member QAJOBTRC. No reports are produced.

Example 2: Producing a Report of Job Records

ENDJOBTRC LIB(MYLIB) RPTTYPE(\DETAIL)

This command stops job tracing, saves the created trace records in memberQAJOBTRC of MYLIB/QAPTTRCJ, and produces a detail report. The use of aprivate library allows several users to trace jobs at the same time.

ENDPEX (End Performance Explorer) Command


55─ ─ENDPEX─ ──(P) ─SSNID(─ ─session-identifier──)─ ──────────────────────────────5

5─ ──┬ ┬────────────────────────── ──┬ ┬───────────────────────── ─────────────5 │ │┌ ┐─\END───── │ │┌ ┐─\LIB── └ ┘ ─OPTION(─ ──┴ ┴─\SUSPEND─ ─)─ └ ┘ ─DTAOPT(───(1) ──┼ ┼─\FILE─ ─)─ └ ┘─\DLT──

5─ ──┬ ┬────────────────────────────────────── ──────────────────────────────5 │ │┌ ┐─QPEXDATA────────── └ ┘ ─DTALIB(────(2, 3) ──┴ ┴─data-library-name─ ─)─

5─ ──┬ ┬───────────────────────────────────── ───────────────────────────────5 │ │┌ ┐─\SSNID─────────── └ ┘ ─DTAMBR(────(4, 5) ──┴ ┴─data-member-name─ ─)─

5─ ──┬ ┬─────────────────────────────────────────────────────────── ─────────5 │ │┌ ┐─QPEXDATA────────── ┌ ┐─\SSNID───────── └ ┘ ─DTAFILE(────(6, 7) ──┴ ┴─data-library-name─ ──┴ ┴─data-file-name─ ─)─

5─ ──┬ ┬──────────────────────── ──┬ ┬────────────────────────── ─────────────5% │ │┌ ┐─\NO── │ │┌ ┐─\BLANK──────── └ ┘ ─RPLDTA(───(8) ──┴ ┴─\YES─ ─)─ └ ┘ ─TEXT(─ ──┴ ┴─'description'─

Notes:P All parameters preceding this point can be specified in positional form.1 Only valid when OPTION(*END) is specified.2 Only valid when OPTION(*END) is specified.3 Only valid when DTAOPT(*LIB) is specified.4 Only valid when OPTION(*END) is specified.


PRTACTRPT

5 Only valid when DTAOPT(*LIB) is specified.6 Only valid when OPTION(*END) is specified.7 Only valid when DTAOPT(*FILE) is specified.8 Only valid when OPTION(*END) is specified.

PurposeThe End Performance Explorer (ENDPEX) command instructs the performanceexplorer tool to stop collecting data. The command expects a session name toaccompany the request which identifies which instance of the performance explorersession to end.

The user can either end the data collection session or suspend the data collectionsession. If the user chooses to end the session, the collected data is put into asingle physical file or multiple data base files, or it is deleted, based on the valuespecified for the DTAOPT parameter.

If the user chooses to suspend the collection of performance data, the sessionremains active. To resume data collection for a suspended session, the user canspecify OPTION(*RESUME) on a subsequent call of the STRPEX (Start Perform-ance Explorer) command.

Examples Example 1: End a Session and Save the Data

ENDPEX SSNID(TEST3) OPTION(\END)

DTAOPT(\LIB) DTAMBR(SYS1DATA)

This command ends the performance explorer session named TEST3 and savesthe data in a set of database files in library QPEXDATA. The member name to beused for each file is SYS1DATA.

Example 2: End a Session and Delete the Data

ENDPEX SSNID(TESTRUN)

OPTION(\END) DTAOPT(\DLT)

This command ends the performance explorer session named TESTRUN anddeletes the collected performance data.

PRTACTRPT (Print Activity Report) Command


55─ ─PRTACTRPT─ ──┬ ┬────────────────────────── ──────────────────────────────5 │ │┌ ┐─QAITMON───── └ ┘ ─MBR(─ ──┴ ┴─member-name─ ─)─

5─ ──┬ ┬─────────────────────────── ──(P)──┬ ┬─────────────────────────────── ────5 │ │┌ ┐─QPFRDATA───── └ ┘ ─TITLE(─ ──┬ ┬─\BLANK───────── ─)─ └ ┘ ─LIB(─ ──┴ ┴─library-name─ ─)─ └ ┘─'report-title'─


PRTACTRPT

5─ ──┬ ┬─────────────────────────── ──┬ ┬─────────────────────── ──────────────5 │ │┌ ┐─\SUMMARY─ └ ┘─PERIOD(───(1) ─┤ Period ├─ └ ┘ ─RPTTYPE(─ ──┼ ┼─\DETAIL── ─)─ └ ┘─\ALL─────

5─ ──┬ ┬───────────────────────── ──┬ ┬───────────────────────────────── ──────5 │ │┌ ┐─\CPU─────── │ │┌ ┐─1ð───────────── └ ┘ ─SEQ(─ ──┼ ┼─\JOBTASK─── ─)─ └ ┘ ─NBRJOBS(─ ──┼ ┼─\ALL─────────── ─)─ ├ ┤─\USER────── └ ┘─number-of-jobs─ ├ ┤─\PTY─────── ├ ┤─\TOTALIO─── ├ ┤─\SYNCIO──── ├ ┤─\ASYNCIO─── ├ ┤─\FAULT───── ├ ┤─\SDBREAD─── ├ ┤─\SDBWRITE── ├ ┤─\SNDBREAD── ├ ┤─\SNDBWRITE─ ├ ┤─\ADBREAD─── ├ ┤─\ADBWRITE── ├ ┤─\ANDBREAD── └ ┘─\ANDBWRITE─

5─ ──┬ ┬──────────────────────── ────────────────────────────────────────────5 │ │┌ ┐─PRTACTRPT─ └ ┘ ─JOB(─ ──┼ ┼─\MBR────── ─)─ └ ┘─job-name──



Notes:P All parameters preceding this point can be specified in positional form.1 *PERIOD contains two lists of two elements each. *N must be specified for any

element that precedes the value(s) specified to maintain its position in the param-eter value sequence.

PurposeThe Print Activity Report (PRTACTRPT) command generates reports based on thedata collected by the Work with System Activity (WRKSYSACT) command.

ExamplesExample 1: Generating a Summary Report

PRTACTRPT

This command submits a batch job that generates a summary activity report usingthe performance data found in the default member QAITMON located in the defaultlibrary QPFRDATA. The report covers the entire measurement period, and the titleof the report is left blank.

Example 2: Generating a Summary and Detailed Activity Report


PRTCPTRPT

PRTACTRPT MBR(JUNEð1)

TITLE('Activity Report for June 1st')

RPTTYPE(\ALL) SEQ(\CPU)

This command submits a batch job that generates both a summary and a detailedactivity report. The performance data comes from member JUNE01 located in thedefault library QPFRDATA. The report covers the entire measurement period, andthe title of the report is 'Activity Report for June 1st.' The detailed activity report liststen entries in descending order according to CPU utilization for each interval.

PRTCPTRPT (Print Component Report) Command


55─ ─PRTCPTRPT──MBR(──member-name──)─ ──┬ ┬─────────────────────────── ───────5 │ │┌ ┐─QPFRDATA───── └ ┘ ─LIB(─ ──┴ ┴─library-name─ ─)─

5─ ──(P)──┬ ┬─────────────────────────────── ──┬ ┬─────────────────────── ────────5 │ │┌ ┐─\MBR─────────── └ ┘─PERIOD(───(1) ─┤ Period ├─ └ ┘ ─TITLE(─ ──┴ ┴─'report-title'─ ─)─

5─ ──┬ ┬─────────────────────────────────────────────────────────── ─────────5 │ │┌ ┐─\ALL──────────────────────────────────── │ ││ │┌ ┐───────────────────────────────────── ├ ┤ ─SLTJOB(───(2) ──┴ ┴──(3)───

6┴──┬ ┬─job-name────────────────────── ─)─

│ │├ ┤─user-name/job name──────────── │ │└ ┘─job-number/user-name/job-name─ │ │┌ ┐─\NONE───────────────────────────────── │ ││ │┌ ┐───────────────────────────────────── └ ┘ ─OMTJOB(───(4) ──(5)──┴ ┴───

6┴──┬ ┬─job-name────────────────────── ─)─

├ ┤─user-name/job-name──────────── └ ┘─job-number/user-name/job-name─

5─ ──┬ ┬───────────────────────────────────── ───────────────────────────────5 │ │┌ ┐─\ALL──────────── │ ││ │┌ ┐───────────── ├ ┤ ─SLTUSRID(───(6) ──┴ ┴──(7)───


│ │┌ ┐─\NONE───────── │ ││ │┌ ┐───────────── └ ┘ ─OMTUSRID(───(8) ──(9)──┴ ┴───


5─ ──┬ ┬───────────────────────────────────────────────────── ───────────────5 │ │┌ ┐─\ALL─────────────────────────── │ ││ │┌ ┐─────────────────────────── ├ ┤ ─SLTPOOLS(────(10) ──┴ ┴───(11) ───


│ │┌ ┐─\NONE─────────────────────── │ ││ │┌ ┐─────────────────────────── └ ┘ ─OMTPOOLS(────(12) ───(13) ──┴ ┴───


5─ ──┬ ┬────────────────────────────────────────── ──────────────────────────5 │ │┌ ┐─\ALL────────────────── │ ││ │┌ ┐────────────────── ├ ┤ ─SLTSBS(────(14) ──┴ ┴───(15) ───


│ │┌ ┐─\NONE────────────── │ ││ │┌ ┐────────────────── └ ┘ ─OMTSBS(────(16) ───(17) ──┴ ┴───



PRTCPTRPT

5─ ──┬ ┬───────────────────────────────────────────────────── ───────────────5 │ │┌ ┐─\ALL──────────────────────────── │ ││ │┌ ┐──────────────────────────── ├ ┤ ─SLTLINE(────(18) ──┴ ┴───(19) ───


│ │┌ ┐─\NONE──────────────────────── │ ││ │┌ ┐──────────────────────────── └ ┘ ─OMTLINE(────(20) ───(21) ──┴ ┴───


5─ ──┬ ┬─────────────────────────────────────────── ─────────────────────────5 │ │┌ ┐─\ALL─────────────────── │ ││ │┌ ┐─────────────────── ├ ┤ ─SLTCTL(────(22) ──┴ ┴───(23) ───


│ │┌ ┐─\NONE─────────────── │ ││ │┌ ┐─────────────────── └ ┘ ─OMTCTL(────(24) ───(25) ──┴ ┴───


5─ ──┬ ┬─────────────────────────────────────────────────── ─────────────────5 │ │┌ ┐─\ALL──────────────────────── │ ││ │┌ ┐──────────────────────── ├ ┤ ─SLTFCNARA(────(26) ──┴ ┴───(27) ───


│ │┌ ┐─\NONE──────────────────── │ ││ │┌ ┐──────────────────────── └ ┘ ─OMTFCNARA(────(28) ───(29) ──┴ ┴───


5─ ──┬ ┬──────────────────────── ────────────────────────────────────────────5 │ │┌ ┐─PRTCPTRPT─ └ ┘ ─JOB(─ ──┼ ┼─\MBR────── ─)─ └ ┘─job-name──


Period: ┌ ┐─\FIRST───── ┌ ┐─\FIRST─────├─ ──┼ ┼─\SELECT──── ──┴ ┴─start-date─ ─)─ ──┬ ┬────────────────────────────────── ─┤ └ ┘─start-time─ │ │┌ ┐─\LAST──── ┌ ┐─\LAST──── └ ┘ ─(─ ──┴ ┴─end-time─ ──┼ ┼────────── ─)─ └ ┘─end-date─



2 The SLTJOB parameter and the OMTJOB parameter cannot be specified at thesame time.

3 A maximum of 50 repetitions4 The SLTJOB parameter and the OMTJOB parameter cannot be specified at the

same time.5 A maximum of 50 repetitions6 The SLTUSRID parameter and the OMTUSRID parameter cannot be specified at

the same time.7 A maximum of 50 repetitions8 The SLTUSRID parameter and the OMTUSRID parameter cannot be specified at

the same time.9 A maximum of 50 repetitions10 The SLTPOOLS parameter and the OMTPOOLS parameter cannot be specified

at the same time


PRTCPTRPT

11 A maximum of 16 repetitions.12 The SLTPOOLS parameter and the OMTPOOLS parameter cannot be specified

at the same time13 A maximum of 16 repetitions.14 The SLTSBS parameter and the OMTSBS parameter cannot be specified at the

same time.15 A maximum of 50 repetitions16 The SLTSBS parameter and the OMTSBS parameter cannot be specified at the





same time.25 A maximum of 50 repetitions26 The SLTFCNARA parameter and the OMTFCNARA parameter cannot be speci-

fied at the same time.27 A maximum of 50 repetitions28 The SLTFCNARA parameter and the OMTFCNARA parameter cannot be speci-

fied at the same time.29 A maximum of 50 repetitions

PurposeThe Print Component Report (PRTCPTRPT) command produces a report thatexpands on the detail for each component of system performance shown on theSystem Report. This report is produced from the performance data collected by theStart Performance Monitor (STRPFRMON) command and shows the data by job,user, pool, disk, local work station, and exception. This report is written to theprinter file QPPTCPTR. Jobs may be selectively included in the report or excludedfrom the report based on a variety of job details and interval times.

ExamplesExample 1: Printing a Component Report

PRTCPTRPT MBR(APRIL18)

This command prints a complete component report for the performance datamember APRIL18 in library QPFRDATA. The report title is the same as the text inthe member.

Example 2: Printing a Report With a Title

PRTCPTRPT MBR(NOV1) PERIOD(\SELECT)

TITLE('Intervals with Highest Response Times')


PRTJOBRPT

This command prints a component report for the data member NOV1 in libraryQPFRDATA. The user is presented with the interval-selection display, which allowssorting of the intervals according to various criteria and selection of only certainintervals to be included in the report. The title of the report is "Intervals with HighestResponse Times".

PRTJOBRPT (Print Job Report) Command


55─ ─PRTJOBRPT──MBR(──member-name──)─ ──┬ ┬─────────────────────────── ───────5 │ │┌ ┐─QPFRDATA───── └ ┘ ─LIB(─ ──┴ ┴─library-name─ ─)─

5─ ──(P)──┬ ┬─────────────────────────────── ──┬ ┬───────────────────────── ──────5 │ │┌ ┐─\MBRTXT──────── │ │┌ ┐─\SELECT───(1) ─ └ ┘ ─TITLE(─ ──┼ ┼─\BLANK───────── ─)─ └ ┘─PERIOD(─ ──┴ ┴─┤ Period ├─ └ ┘─'report-title'─

5─ ──┬ ┬────────────────────────── ──────────────────────────────────────────5 ├ ┤─SLTJOB(───(2) ─┤ Sltjob ├──)─ └ ┘─OMTJOB(───(4) ─┤ Omtjob ├──)─

5─ ──┬ ┬───────────────────────────────────── ───────────────────────────────5 │ │┌ ┐─\ALL──────────── │ ││ │┌ ┐───────────── ├ ┤ ─SLTUSRID(───(6) ──┴ ┴──(7)───


│ │┌ ┐─\NONE─────────── │ ││ │┌ ┐───────────── └ ┘ ─OMTUSRID(───(8) ──┴ ┴──(9)───


5─ ──┬ ┬───────────────────────────────────────────────────── ───────────────5 │ │┌ ┐─\ALL─────────────────────────── │ ││ │┌ ┐─────────────────────────── ├ ┤ ─SLTPOOLS(────(10) ──┴ ┴───(11) ───


│ │┌ ┐─\NONE────────────────────────── │ ││ │┌ ┐─────────────────────────── └ ┘ ─OMTPOOLS(────(12) ──┴ ┴───(13) ───


5─ ──┬ ┬────────────────────────────────────────── ──────────────────────────5 │ │┌ ┐─\ALL────────────────── │ ││ │┌ ┐────────────────── ├ ┤ ─SLTSBS(────(14) ──┴ ┴───(15) ───


│ │┌ ┐─\NONE───────────────── │ ││ │┌ ┐────────────────── └ ┘ ─OMTSBS(────(16) ──┴ ┴───(17) ───


5─ ──┬ ┬───────────────────────────────────────────────────── ───────────────5 │ │┌ ┐─\ALL──────────────────────────── │ ││ │┌ ┐──────────────────────────── ├ ┤ ─SLTLINE(────(18) ──┴ ┴───(19) ───


│ │┌ ┐─\NONE─────────────────────────── │ ││ │┌ ┐──────────────────────────── └ ┘ ─OMTLINE(────(20) ──┴ ┴───(21) ───


5─ ──┬ ┬─────────────────────────────────────────── ─────────────────────────5 │ │┌ ┐─\ALL─────────────────── │ ││ │┌ ┐─────────────────── ├ ┤ ─SLTCTL(────(22) ──┴ ┴───(23) ───


│ │┌ ┐─\NONE────────────────── │ ││ │┌ ┐─────────────────── └ ┘ ─OMTCTL(────(24) ──┴ ┴───(25) ───



PRTJOBRPT

5─ ──┬ ┬─────────────────────────────────────────────────── ─────────────────5 │ │┌ ┐─\ALL──────────────────────── │ ││ │┌ ┐──────────────────────── ├ ┤ ─SLTFCNARA(────(26) ──┴ ┴───(27) ───


│ │┌ ┐─\NONE─────────────────────── │ ││ │┌ ┐──────────────────────── └ ┘ ─OMTFCNARA(────(28) ──┴ ┴───(29) ───


5─ ──┬ ┬───────────────────────── ──┬ ┬──────────────────────── ───────────────5 │ │┌ ┐─\YES─ │ │┌ ┐─PRTJOBRPT─ └ ┘ ─OMTSYSTSK(─ ──┴ ┴─\NO── ─)─ └ ┘ ─JOB(─ ──┼ ┼─\MBR────── ─)─ └ ┘─job-name──



Sltjob: ┌ ┐─\ALL──────────────────────────────────────────────── │ │┌ ┐─────────────────────────────────────────────────├─ ──┴ ┴──(3)───

6┴─── ─ ──┬ ┬───────────────────────────── ─job-name─ ───────────────┤


Omtjob: ┌ ┐─\NONE─────────────────────────────────────────────── │ │┌ ┐─────────────────────────────────────────────────├─ ──┴ ┴──(5)───

6┴─── ─ ──┬ ┬───────────────────────────── ─job-name─ ───────────────┤


Notes:P All parameters preceding this point can be specified in positional form.1 *SELECT is valid only in the interactive environment.2 The SLTJOB parameter and the OMTJOB parameter are mutually exclusive.3 A maximum of 50 repetitions4 The SLTJOB parameter and the OMTJOB parameter are mutually exclusive.5 A maximum of 50 repetitions6 The SLTUSRID parameter and the OMTUSRID parameter are mutually exclu-

sive.7 A maximum of 50 repetitions8 The SLTUSRID parameter and the OMTUSRID parameter are mutually exclu-

sive.9 A maximum of 50 repetitions10 The SLTPOOLS parameter and the OMTPOOLS parameter are mutually exclu-


sive.13 A maximum of 16 repetitions


PRTJOBRPT

14 The SLTSBS parameter and the OMTSBS parameter are mutually exclusive.15 A maximum of 50 repetitions16 The SLTSBS parameter and the OMTSBS parameter are mutually exclusive.17 A maximum of 50 repetitions18 The SLTLINE parameter and the OMTLINE parameter are mutually exclusive.19 A maximum of 50 repetitions20 The SLTLINE parameter and the OMTLINE parameter are mutually exclusive.21 A maximum of 50 repetitions22 The SLTCTL parameter and the OMTCTL parameter are mutually exclusive.23 A maximum of 50 repetitions24 The SLTCTL parameter and the OMTCTL parameter are mutually exclusive.25 A maximum of 50 repetitions26 The SLTFNCARA parameter and the OMTFNCARA parameter are mutually

exclusive.27 A maximum of 50 repetitions28 The SLTFNCARA parameter and the OMTFNCARA parameter are mutually

exclusive.29 A maximum of 50 repetitions

PurposeThe Print Job Report (PRTJOBRPT) command produces a job-oriented report fromthe performance data collected by the Start Performance Monitor (STRPFRMON)command. The report, which is written to the printer file QPPTITVJ, shows job infor-mation by interval. Jobs are selected for inclusion in, or exclusion from, the reportbased on a variety of job details and interval times.

ExamplesExample 1: Submitting a Batch Job

PRTJOBRPT MBR(DTAð71588A)

This command submits a batch job to print a report on all jobs in all intervals in themember DTA071588A of the performance data files in library QPFRDATA. Thereport title is taken from the text of that member.

Example 2: Selecting Intervals to Include in Report

PRTJOBRPT MBR(DTAð71588A) PERIOD(\SELECT)

This command submits a job to print a report from the same data, but first shows ascreen where a user interactively selects which intervals to include.

Example 3: Reporting on a Specific Time Period

PRTJOBRPT MBR(DTAð71588A) PERIOD((233ð)(ð13ð))

This command submits a job to print a report on the data collected from 11:30 PMon the first day of collection through 1:30 AM on the last day of collection.However, if data collection started and ended on the same day, an error messageis printed instead, because the specified ending date and time is before the speci-fied starting date and time.

Example 4: Printing a Report Interactively


PRTJOBTRC

PRTJOBRPT MBR(DTAð71588A) SLTUSRID(D46\)

JOBD(\NONE)

This command interactively prints a report for all jobs with a user ID starting withD46.

Example 5: Printing a Report Interactively

PRTJOBRPT MBR(DTAð71588A) SLTJOB(D46\/\N)

JOBD(\NONE)

This command performs the same function as the previous example.

PRTJOBTRC (Print Job Trace) Command


55─ ─PRTJOBTRC─ ──┬ ┬────────────────────────── ──────────────────────────────5 │ │┌ ┐─QAJOBTRC──── └ ┘ ─MBR(─ ──┴ ┴─member-name─ ─)─

5─ ──┬ ┬─────────────────────────── ──┬ ┬─────────────────────────── ──────────5 │ │┌ ┐─QPFRDATA───── │ │┌ ┐─\BOTH──── └ ┘ ─LIB(─ ──┴ ┴─library-name─ ─)─ └ ┘ ─RPTTYPE(─ ──┼ ┼─\DETAIL── ─)─ └ ┘─\SUMMARY─

5─ ──(P)──┬ ┬─────────────────────────────── ───────────────────────────────────5 │ │┌ ┐─\BLANK───────── └ ┘ ─TITLE(─ ──┴ ┴─'report-title'─ ─)─

5─ ──┬ ┬───────────────────────────────── ───────────────────────────────────5 │ │┌ ┐─\FIRST────────── └ ┘ ─STRSEQ(─ ──┴ ┴─sequence-number─ ─)─

5─ ──┬ ┬───────────────────────────────── ───────────────────────────────────5 │ │┌ ┐─\LAST─────────── └ ┘ ─ENDSEQ(─ ──┴ ┴─sequence-number─ ─)─

5─ ──┬ ┬────────────────────────────── ──┬ ┬────────────────────────────── ────5 │ │┌ ┐─QT3REQIO───── │ │┌ ┐─QWSGET─────── └ ┘ ─ENDTNS(─ ──┴ ┴─program-name─ ─)─ └ ┘ ─STRTNS(─ ──┴ ┴─program-name─ ─)─

5─ ──┬ ┬─────────────────────────── ──┬ ┬──────────────────────── ─────────────5 │ │┌ ┐─\CUR─────── │ │┌ ┐─PRTJOBTRC─ └ ┘ ─MODEL(─ ──┴ ┴─model-code─ ─)─ └ ┘ ─JOB(─ ──┼ ┼─\MBR────── ─)─ └ ┘─job-name──




PRTLCKRPT

PurposeThe Print Job Trace (PRTJOBTRC) command produces performance-orientedreports used to analyze job trace data collected with the Start Job Trace(STRJOBTRC) and End Job Trace (ENDJOBTRC) commands.

ExamplePRTJOBTRC LIB(MYLIB) RPTTYPE(\DETAIL)

This command produces a detail report using data saved in member QAJOBTRC inlibrary MYLIB/QAPTTRCJ.

PRTLCKRPT (Print Lock Report) Command


55─ ─PRTLCKRPT──MBR(──member-name──)─ ──┬ ┬─────────────────────────── ───────5 │ │┌ ┐─QPFRDATA───── └ ┘ ─LIB(─ ──┴ ┴─library-name─ ─)─

5─ ──┬ ┬─────────────────────────────── ──(P)──┬ ┬─────────────────────── ────────5 │ │┌ ┐─\MBRTXT──────── │ │┌ ┐─\SUM─ └ ┘ ─TITLE(─ ──┼ ┼─\BLANK───────── ─)─ └ ┘ ─RPTTYPE(─ ──┼ ┼─\TOD─ ─)─ └ ┘─'report-title'─ ├ ┤─\RQS─ ├ ┤─\HLD─ ├ ┤─\OBJ─ └ ┘─\ALL─

5─ ──┬ ┬───────────────────── ───────────────────────────────────────────────5 │ │┌ ┐─\YES─ └ ┘ ─FIRST(─ ──┴ ┴─\NO── ─)─

5─ ──┬ ┬──────────────────────────────────────────── ────────────────────────5 │ │┌ ┐─\FIRST───── ┌ ┐─\LAST──── └ ┘ ─PERIOD(───(1) ──┴ ┴─start-time─ ──┼ ┼────────── ─)─ └ ┘─end-time─

5─ ──┬ ┬───────────────────────────────────────── ───────────────────────────5 │ │┌ ┐─5ðð──────────────────── └ ┘ ─MINWAIT(─ ──┴ ┴─number-of-milliseconds─ ─)─

5─ ──┬ ┬──────────────────────── ────────────────────────────────────────────5 │ │┌ ┐─PRTLCKRPT─ └ ┘ ─JOB(─ ──┼ ┼─\MBR────── ─)─ └ ┘─job-name──


Notes:P All parameters preceding this point can be specified in positional form.1 *PERIOD contains two lists of one element each. *N must be specified in place

of any omitted element that precedes the value(s) to be specified to maintain itsposition in the parameter value sequence.


PRTPEXRPT

PurposeThe Print Lock Report (PRTLCKRPT) command produces a report that shows lockand seize conflicts that occur during system operation. This report is produced fromthe resource management trace data collected by the Start Performance Monitor(STRPFRMON) command and formatted by the Print Transaction Report(PRTTNSRPT) command. This information can be used to determine whether jobsare being delayed during processing because of unsatisfied lock requests orinternal machine seizes; these conditions are also known as waits.

The input to this command is the output from a previous run of the commandsSTRPFRMON TRACE(*ALL) and PRTTNSRPT. The output from this command iswritten to the printer file QPPTLCK.

ExamplesExample 1: Producing a Summary Report

PRTLCKRPT MBR(RESTRC)

This command produces a summary report from the performance data saved inmember RESTRC of QPFRDATA/QAPMDMPT from a prior run of the Start Per-formance Monitor (STRPFRMON) and Print Transaction Report (PRTTNSRPT)commands.

Example 2: Including a Detail Listing Sorted By Time

PRTLCKRPT MBR(RESTRC) RPTTYPE(\TOD)

This command produces the same report as the previous example, except that itincludes a detail listing sorted by the time in which the lock/seize conflicts occurred.

PRTPEXRPT (Print Performance Explorer Report) Command


55─ ─PRTPEXRPT─ ──(P)─MBR(──member-name──)─ ──┬ ┬─────────────────────────── ─────5 │ │┌ ┐─QPEXDATA───── └ ┘ ─LIB(─ ──┴ ┴─library-name─ ─)─

5─ ──┬ ┬──────────────────────── ──┬ ┬────────────────────────── ──────────────5| │ │┌ ┐─\STATS─── │ │┌ ┐─\PRINT───| └ ┘| ─TYPE(─ ──┼ ┼─\TRACE─── ─)─ └ ┘| ─OUTPUT(─ ──┴ ┴─\OUTFILE─ ─)─

├ ┤─\PROFILE─| └ ┘─\BASIC───

5─ ──┬ ┬──────────────────────────────────────────────────── ────────────────5| │ │┌ ┐─\LIBL/────────| └ ┘| ─OUTFILE(─| ──┼ ┼─────────────── ─database-file-name──)─| ├ ┤─\CURLIB/──────| └ ┘─library-name/─

5─ ──┬ ┬─────────────────────────────────────────── ─────────────────────────5| │ │┌ ┐─\FIRST────── ┌ ┐─\REPLACE─| └ ┘| ─OUTMBR(─| ──┴ ┴─member-name─ ──┴ ┴─\ADD───── ─)─


PRTPEXRPT

5─ ──┬ ┬───────────────────────────────────────────────────────────────── ───5| │ │┌ ┐─\NONE─────────────| │ │┌ ┐─\TASK────── ┌ ┐─\NO── │ │┌ ┐───────────────| └ ┘| ─TRACEOPT(───(1)| ──┴ ┴─\TIMESTAMP─ ──┴ ┴─\YES─ ──┴ ┴──(2)───

6┴┬ ┬─\PGM────── ─)─

| ├ ┤─\LICPGM───| ├ ┤─\ASM──────| ├ ┤─\BASE─────| ├ ┤─\DISK─────| ├ ┤─\DSKSVR───| ├ ┤─\FAULT────| ├ ┤─\JOB──────| ├ ┤─\LOCK─────| ├ ┤─\SAR──────| ├ ┤─\MIBRKT───| ├ ┤─\LICBRKT──| ├ ┤─\DASD─────| ├ ┤─\DASDSRVR─| ├ ┤─\PAGEFLT──| ├ ┤─\RMPR─────| └ ┘─\RMSZ─────

5─ ──┬ ┬────────────────────────────────────── ──────────────────────────────5| │ │┌ ┐─\ALL────────────────| │ ││ │┌ ┐───────────────────| └ ┘| ─TRCTYPE(─ ──┴ ┴───

6┴──(3)──┬ ┬─\CALLRTN── ─)─

| ├ ┤─\BASIC────| ├ ┤─\DSKIO1───| ├ ┤─\DSKIO2───| ├ ┤─\DSKSVR───| ├ ┤─\DSKSTG───| ├ ┤─\VRTADR───| ├ ┤─\PGMACT───| ├ ┤─\FILEOPEN─| ├ ┤─\PRFDTA───| └ ┘─\TASKSWT──

5─ ──┬ ┬────────────────────────────────────────────────────── ──────────────5| │ │┌ ┐─\AVAIL─────| └ ┘| ─PERIOD(────(4, 5)| ─(─ ──┴ ┴─start-time─ ─┤ PERIOD details ├─| ─)─

5─ ──┬ ┬───────────────────────────────────────────────────────────── ───────5| │ │┌ ┐─\ALL──────────────────────────────────────| │ ││ │┌ ┐───────────────────────────────────────| │ ││ ││ │┌ ┐─\ALL/───────| ├ ┤| ─SLTJOB(───(6) ──┴ ┴──(7)───

6┴──┴ ┴─job-number/─ ─┤ SLTJOB details ├─ ─)─

| │ │┌ ┐─\NONE─────────────────────────────────────| │ ││ │┌ ┐───────────────────────────────────────| │ ││ ││ │┌ ┐─\ALL/───────| └ ┘| ─OMTJOB(───(8) ──┴ ┴──(9)───

6┴──┴ ┴─job-number/─ ─┤ OMTJOB details ├─ ─)─

5─ ──┬ ┬──────────────────────────────────────────────────── ────────────────5 │ │┌ ┐─\CPU──────────── ┌ ┐─\PROGRAM─ └ ┘ ─STATSOPT(────(10) ──┼ ┼─\PGMNAME──────── ──┼ ┼─\BLANK─── ─)─ ├ ┤─\INVCNT───────── └ ┘─\MODULE── ├ ┤─\DBSYNCIO─────── ├ ┤─\DBASYNCIO────── ├ ┤─\NDBSYNCIO────── ├ ┤─\NDBASYNCIO───── ├ ┤─\MICALLS──────── ├ ┤─\MIINST───────── ├ ┤─\CUMLCPU──────── ├ ┤─\CUMLDBSYNCIO─── ├ ┤─\CUMLDBASYNCIO── ├ ┤─\CUMLNDBSYNCIO── └ ┘─\CUMLNDBASYNCIO─


PRTPEXRPT

5─ ──┬ ┬─────────────────────────────────────────── ─────────────────────────5 └ ┘─PROFILEOPT(────(11) ─┤ PROFILEOPT details ├──)─

5─ ──┬ ┬──────────────────────────── ───────────────────────────────────────5% │ │┌ ┐─\DESCENDING─ └ ┘ ─ORDER(─ ──┴ ┴─\ASCENDING── ─)─

PERIOD details: ┌ ┐─\BEGIN───── ┌ ┐─\AVAIL─── ┌ ┐─\END─────├─ ──┼ ┼─\CURRENT─── ─)─ ─(─ ──┴ ┴─end-time─ ──┼ ┼─\CURRENT─ ─)────────────────────┤ └ ┘─start-date─ └ ┘─end-date─

SLTJOB details: ┌ ┐─\ALL/───────────────├─ ──┼ ┼─generic\-user-name/─ ──┬ ┬─job-name────────── ────────────────────────┤ └ ┘─user-name/────────── └ ┘─generic\-job-name─

OMTJOB details: ┌ ┐─\ALL/───────────────├─ ──┼ ┼─generic\-user-name/─ ──┬ ┬─job-name────────── ────────────────────────┤ └ ┘─user-name/────────── └ ┘─generic\-job-name─

PROFILEOPT details: ┌ ┐─\SAMPLECOUNT─ ┌ ┐─\PROGRAM─── ┌ ┐─ð─────────────────├─ ──┴ ┴─\ADDRESS───── ──┼ ┼─\BLANK───── ──┴ ┴─filter-percentage─ ───────────────┤ ├ ┤─\STATEMENT─ ├ ┤─\PROCEDURE─ └ ┘─\MODULE────

Notes:P All parameters preceding this point can be specified in positional form.1 The TRACEOPT parameter is valid only if TYPE(*TRACE) specified.

| 2 A maximum of 10 values can be specified.

| 3 A maximum of 10 values can be specified.

| 4 This parameter is valid only if TYPE(*TRACE) is specified.

| 5 *PERIOD contains two lists of two elements each. *N must be specified for any| element that precedes the value or values to be specified, to maintain its position| in the parameter value sequence.

| 6 The SLTJOB parameter and the OMTJOB parameter are mutually exclusive.

| 7 A maximum of 10 repetitions.

| 8 The SLTJOB parameter and the OMTJOB parameter are mutually exclusive.

| 9 A maximum of 10 repetitions.10 The STATSOPT parameter is valid only if TYPE(*TRACE) specified.11 The PROFILEOPT parameter is valid only if TYPE(*PROFILE) specified.

PurposeThe Print Performance Explorer Report (PRTPEXRPT) command prints a formattedlisting of the data that was collected by the performance explorer and saved acrossa set of physical files in a particular library.

Restriction: The user must have read authority for each performance explorerdatabase file in the specified library.


PRTPOLRPT

ExamplesExample 1: Statistics Report

PRTPEXRPT MBR(SAMPLE) LIBRARY(SAMPLELIB)

TYPE(\STATS) STATSOPT(\INVCNT \MODULE)

In this example, a statistics type report is generated based on data membersnamed SAMPLE in library SAMPLELIB. The data is arranged in descending orderbased on invocation counts and is summarized at the module level.

Example 2: Profile Report

PRTPEXRPT MBR(SAMPLE2) TYPE(\PROFILE)

PROFILEOPT(\SAMPLECOUNT \PROGRAM)

ORDER(\DESCENDING)

In this example, a profile type report is generated based on data members namedSAMPLE2 in the default library, QPEXDATA. The data is arranged in descendingorder based on the sample count and is summarized at the program level.

PRTPOLRPT (Print Pool Report) Command


55─ ─PRTPOLRPT──MBR(──member-name──)─ ──┬ ┬─────────────────────────── ───────5 │ │┌ ┐─QPFRDATA───── └ ┘ ─LIB(─ ──┴ ┴─library-name─ ─)─

5─ ──(P)──┬ ┬─────────────────────────────── ──┬ ┬─────────────────────── ────────5 │ │┌ ┐─\MBRTXT──────── └ ┘─PERIOD(───(1) ─┤ Period ├─ └ ┘ ─TITLE(─ ──┼ ┼─\BLANK───────── ─)─ └ ┘─'report-title'─

5─ ──┬ ┬────────────────────────── ──────────────────────────────────────────5 ├ ┤─SLTJOB(───(2) ─┤ Sltjob ├──)─ └ ┘─OMTJOB(───(4) ─┤ Omtjob ├──)─

5─ ──┬ ┬───────────────────────────────────── ───────────────────────────────5 │ │┌ ┐─\ALL──────────── │ ││ │┌ ┐───────────── ├ ┤ ─SLTUSRID(───(6) ──┴ ┴──(7)───


│ │┌ ┐─\NONE─────────── │ ││ │┌ ┐───────────── └ ┘ ─OMTUSRID(───(8) ──┴ ┴──(9)───


5─ ──┬ ┬───────────────────────────────────────────────────── ───────────────5 │ │┌ ┐─\ALL─────────────────────────── │ ││ │┌ ┐─────────────────────────── ├ ┤ ─SLTPOOLS(────(10) ──┴ ┴───(11) ───


│ │┌ ┐─\NONE────────────────────────── │ ││ │┌ ┐─────────────────────────── └ ┘ ─OMTPOOLS(────(12) ──┴ ┴───(13) ───


5─ ──┬ ┬────────────────────────────────────────── ──────────────────────────5 │ │┌ ┐─\ALL────────────────── │ ││ │┌ ┐────────────────── ├ ┤ ─SLTSBS(────(14) ──┴ ┴───(15) ───


│ │┌ ┐─\NONE───────────────── │ ││ │┌ ┐────────────────── └ ┘ ─OMTSBS(────(16) ──┴ ┴───(17) ───



PRTPOLRPT

5─ ──┬ ┬───────────────────────────────────────────────────── ───────────────5 │ │┌ ┐─\ALL──────────────────────────── │ ││ │┌ ┐──────────────────────────── ├ ┤ ─SLTLINE(────(18) ──┴ ┴───(19) ───


│ │┌ ┐─\NONE─────────────────────────── │ ││ │┌ ┐──────────────────────────── └ ┘ ─OMTLINE(────(20) ──┴ ┴───(21) ───


5─ ──┬ ┬─────────────────────────────────────────── ─────────────────────────5 │ │┌ ┐─\ALL─────────────────── │ ││ │┌ ┐─────────────────── ├ ┤ ─SLTCTL(────(22) ──┴ ┴───(23) ───


│ │┌ ┐─\NONE────────────────── │ ││ │┌ ┐─────────────────── └ ┘ ─OMTCTL(────(24) ──┴ ┴───(25) ───


5─ ──┬ ┬─────────────────────────────────────────────────── ─────────────────5 │ │┌ ┐─\ALL──────────────────────── │ ││ │┌ ┐──────────────────────── ├ ┤ ─SLTFCNARA(────(26) ──┴ ┴───(27) ───


│ │┌ ┐─\NONE─────────────────────── │ ││ │┌ ┐──────────────────────── └ ┘ ─OMTFCNARA(────(28) ──┴ ┴───(29) ───


5─ ──┬ ┬──────────────────────── ────────────────────────────────────────────5 │ │┌ ┐─PRTPOLRPT─ └ ┘ ─JOB(─ ──┼ ┼─\MBR────── ─)─ └ ┘─job-name──


Period: ┌ ┐─\SELECT──────────────────────────────────────────────────────── │ │┌ ┐─\FIRST───── ┌ ┐─\FIRST─────├─ ──┴ ┴ ──┴ ┴─start-time─ ──┼ ┼──────────── ──┬ ┬──────────────────────────── ─)──┤ └ ┘─start-date─ │ │┌ ┐─\LAST──── ┌ ┐─\LAST──── └ ┘ ──┴ ┴─end-time─ ──┼ ┼────────── └ ┘─end-date─

Sltjob: ┌ ┐─\ALL──────────────────────────────────────────────── │ │┌ ┐─────────────────────────────────────────────────├─ ──┴ ┴──(3)───

6┴─── ─ ──┬ ┬───────────────────────────── ─job-name─ ───────────────┤


Omtjob: ┌ ┐─\NONE─────────────────────────────────────────────── │ │┌ ┐─────────────────────────────────────────────────├─ ──┴ ┴──(5)───

6┴─── ─ ──┬ ┬───────────────────────────── ─job-name─ ───────────────┤


Notes:P All parameters preceding this point can be specified in positional form.1 PERIOD contains two lists of two elements each. *N must be specified for any


2 The SLTJOB parameter and the OMTJOB parameter are mutually exclusive.3 A maximum of 50 repetitions4 The SLTJOB parameter and the OMTJOB parameter are mutually exclusive.


PRTPOLRPT

5 A maximum of 50 repetitions6 The SLTUSRID parameter and the OMTUSRID parameter are mutually exclu-




sive.13 A maximum of 16 repetitions14 The SLTSBS parameter and the OMTSBS parameter are mutually exclusive.15 A maximum of 50 repetitions16 The SLTSBS parameter and the OMTSBS parameter are mutually exclusive.17 A maximum of 50 repetitions18 The SLTLINE parameter and the OMTLINE parameter are mutually exclusive.19 A maximum of 50 repetitions20 The SLTLINE parameter and the OMTLINE parameter are mutually exclusive.21 A maximum of 50 repetitions22 The SLTCTL parameter and the OMTCTL parameter are mutually exclusive.23 A maximum of 50 repetitions24 The SLTCTL parameter and the OMTCTL parameter are mutually exclusive.25 A maximum of 50 repetitions26 The SLTFNCARA parameter and the OMTFNCARA parameter are mutually



PurposeThe Print Pool Report (PRTPOLRPT) command produces a pool-oriented reportfrom the performance data collected by the Start Performance Monitor(STRPFRMON) command. The report is written to the printer file QPPTITVP. Thetwo sections of the report are subsystem activity and workload activity of storagepools. The information is presented according to interval order. Jobs may be selec-tively included in, or excluded from, the report based on a variety of job details andinterval times.

ExamplesExample 1: Printing a Report

PRTPOLRPT MBR(DTAð71588A)

This command submits a batch job to print a report on all jobs in all intervals in themember DTA071588A of the performance data files in library QPFRDATA. Thereport title is taken from the text of that member.


PRTRSCRPT


PRTPOLRPT MBR(DTAð71588A) PERIOD(\SELECT)

This command submits a job to print a report from the same data, but first shows adisplay from which the user interactively selects the intervals to include.

Example 3: Specifying Data Collection Time Period

PRTPOLRPT MBR(DTAð71588A) PERIOD((233ð)(ð13ð))

This command submits a job to print a report on the data collected from 11:30 PMon the first day of collection through 1:30 AM on the last day of collection.However, if data collection started and ended on the same day, an error messageis printed, because the specified ending date and time is before the specifiedstarting date and time.

Example 4: Specifying a User ID

PRTPOLRPT MBR(DTAð71588A) SLTUSRID(D46\)

JOBD(\NONE)

This command interactively prints a report for all jobs with a user ID starting withD46.

Example 5: Specifying a User ID

PRTPOLRPT MBR(DTAð71588A) SLTJOB(D46\/\N)

JOBD(\NONE)

This command performs the same function as the previous example.

PRTRSCRPT (Print Resource Report) Command


55─ ─PRTRSCRPT──MBR(──member-name──)─ ──┬ ┬─────────────────────────── ───────5 │ │┌ ┐─QPFRDATA───── └ ┘ ─LIB(─ ──┴ ┴─library-name─ ─)─

5─ ──(P)──┬ ┬─────────────────────────────── ──┬ ┬─────────────────────── ────────5 │ │┌ ┐─\MBRTXT──────── └ ┘─PERIOD(───(1) ─┤ Period ├─ └ ┘ ─TITLE(─ ──┼ ┼─\BLANK───────── ─)─ └ ┘─'report-title'─

5─ ──┬ ┬──────────────────────── ────────────────────────────────────────────5 │ │┌ ┐─PRTRSCRPT─ └ ┘ ─JOB(─ ──┼ ┼─\MBR────── ─)─ └ ┘─job-name──


Period:


PRTSYSRPT

┌ ┐─\SELECT───(2) ───────────────────────────────────────────────────── │ │┌ ┐─\FIRST───── ┌ ┐─\FIRST─────├─ ──┴ ┴ ──┴ ┴─start-time─ ──┼ ┼──────────── ──┬ ┬──────────────────────────── ─)──┤ └ ┘─start-date─ │ │┌ ┐─\LAST──── ┌ ┐─\LAST──── └ ┘ ──┴ ┴─end-time─ ──┼ ┼────────── └ ┘─end-date─



2 *SELECT is valid only in the interactive environment.

PurposeThe Print Resource Report (PRTRSCRPT) command produces a device resourceusage report from the performance data collected by the Start Performance Monitor(STRPFRMON) command. The report is written to the printer file, QPPTITVR, andshows device resource information by time interval. Resources may be selected forinclusion in, or exclusion from, the report based on interval times.


PRTRSCRPT MBR(DTAð71588A)

This command submits a batch job to print a report on all resources in all intervalsin the member DTA071588A of performance data files in library QPFRDATA. Thereport title is taken from the text of that member.


PRTRSCRPT MBR(DTAð71588A) PERIOD(\SELECT)

This command submits a job to print a report from the same data, but first shows ascreen from which the user interactively select which intervals to include.

Example 3: Specifying Data Collection Time Period

PRTRSCRPT MBR(DTAð71588A) PERIOD((233ð)(ð13ð))

This command submits a job to print a report on the data collected from 11:30 PMon the first day of collection through 1:30 AM on the last day of collection.

PRTSYSRPT (Print System Report) Command


55─ ─PRTSYSRPT──MBR(──member-name──)─ ──┬ ┬─────────────────────────── ───────5 │ │┌ ┐─QPFRDATA───── └ ┘ ─LIB(─ ──┴ ┴─library-name─ ─)─



PRTSYSRPT

5─ ──┬ ┬─────────────────────────────────── ──┬ ┬────────────────────────── ───5 │ │┌ ┐─\ALL──────────────── ├ ┤─SLTJOB(───(3) ─┤ Sltjob ├──)─ │ ││ │┌ ┐───────────────── └ ┘─OMTJOB(───(5) ─┤ Omtjob ├──)─ └ ┘ ─TYPE(─ ──┴ ┴──(2)───

6┴──┬ ┬─\WORKLOAD─ ─)─

├ ┤─\RSC────── ├ ┤─\RSCEXPN── ├ ┤─\POOL───── ├ ┤─\DISK───── └ ┘─\CMN──────

5─ ──┬ ┬────────────────────────────────────── ──────────────────────────────5 │ │┌ ┐─\ALL──────────── │ ││ │┌ ┐───────────── ├ ┤ ─SLTUSRID(───(7) ──┴ ┴──(8)───

6┴─user-name─ ─)──

│ │┌ ┐─\NONE──────────── │ ││ │┌ ┐───────────── └ ┘ ─OMTUSRID(───(9) ──┴ ┴───(10) ───


5─ ──┬ ┬───────────────────────────────────────────────────── ───────────────5 │ │┌ ┐─\ALL─────────────────────────── │ ││ │┌ ┐─────────────────────────── ├ ┤ ─SLTPOOLS(────(11) ──┴ ┴───(12) ───


│ │┌ ┐─\NONE────────────────────────── │ ││ │┌ ┐─────────────────────────── └ ┘ ─OMTPOOLS(────(13) ──┴ ┴───(14) ───


5─ ──┬ ┬────────────────────────────────────────── ──────────────────────────5 │ │┌ ┐─\ALL────────────────── │ ││ │┌ ┐────────────────── ├ ┤ ─SLTSBS(────(15) ──┴ ┴───(16) ───


│ │┌ ┐─\NONE───────────────── │ ││ │┌ ┐────────────────── └ ┘ ─OMTSBS(────(17) ──┴ ┴───(18) ───


5─ ──┬ ┬───────────────────────────────────────────────────── ───────────────5 │ │┌ ┐─\ALL──────────────────────────── │ ││ │┌ ┐──────────────────────────── ├ ┤ ─SLTLINE(────(19) ──┴ ┴───(20) ───


│ │┌ ┐─\NONE─────────────────────────── │ ││ │┌ ┐──────────────────────────── └ ┘ ─OMTLINE(────(21) ──┴ ┴───(22) ───


5─ ──┬ ┬─────────────────────────────────────────── ─────────────────────────5 │ │┌ ┐─\ALL─────────────────── │ ││ │┌ ┐─────────────────── ├ ┤ ─SLTCTL(────(24) ──┴ ┴───(25) ───


│ │┌ ┐─\NONE────────────────── │ ││ │┌ ┐─────────────────── └ ┘ ─OMTCTL(────(26) ──┴ ┴───(27) ───


5─ ──┬ ┬─────────────────────────────────────────────────── ─────────────────5 │ │┌ ┐─\ALL──────────────────────── │ ││ │┌ ┐──────────────────────── ├ ┤ ─SLTFCNARA(────(28) ──┴ ┴───(29) ───


│ │┌ ┐─\NONE─────────────────────── │ ││ │┌ ┐──────────────────────── └ ┘ ─OMTFCNARA(────(30) ──┴ ┴───(31) ───


5─ ──┬ ┬──────────────────────── ────────────────────────────────────────────5 │ │┌ ┐─PRTSYSRPT─ └ ┘ ─JOB(─ ──┼ ┼─\MBR────── ─)─ └ ┘─job-name──



PRTSYSRPT

Period: ┌ ┐─\SELECT──────────────────────────────────────────────────────── │ │┌ ┐─\FIRST───── ┌ ┐─\FIRST─────├─ ──┴ ┴ ──┴ ┴─start-time─ ──┼ ┼──────────── ──┬ ┬──────────────────────────── ─)──┤ └ ┘─start-date─ │ │┌ ┐─\LAST──── ┌ ┐─\LAST──── └ ┘ ──┴ ┴─end-time─ ──┼ ┼────────── └ ┘─end-date─

Sltjob: ┌ ┐─\ALL──────────────────────────────────────────────── │ │┌ ┐─────────────────────────────────────────────────├─ ──┴ ┴──(4)───

6┴─── ─ ──┬ ┬───────────────────────────── ─job-name─ ───────────────┤


Omtjob: ┌ ┐─\NONE─────────────────────────────────────────────── │ │┌ ┐─────────────────────────────────────────────────├─ ──┴ ┴──(6)───

6┴─── ─ ──┬ ┬───────────────────────────── ─job-name─ ───────────────┤




2 Specific report section with maximum of 6 repetitions.3 The SLTJOB parameter and the OMTJOB parameter cannot be specified at the

same time.4 A maximum of 50 repetitions.5 The SLTJOB parameter and the OMTJOB parameter cannot be specified at the

same time.6 A maximum of 50 repetitions.7 The SLTUSRID parameter and the OMTUSRID parameter cannot be specified at

the same time.8 A maximum of 50 repetitions.9 The SLTUSRID parameter and the OMTUSRID parameter cannot be specified at

the same time.10 A maximum of 50 repetitions.11 The SLTPOOLS parameter and the OMTPOOLS parameter cannot be specified

at the same time.12 A maximum of 16 repetitions.13 The SLTPOOLS parameter and the OMTPOOLS parameter cannot be specified

at the same time.14 A maximum of 16 repetitions.15 The SLTSBS parameter and the OMTSBS parameter cannot be specified at the

same time.16 A maximum of 50 repetitions.17 The SLTSBS parameter and the OMTSBS parameter cannot be specified at the

same time.18 A maximum of 50 repetitions.19 The SLTLINE parameter and the OMTLINE parameter cannot be specified at the

same time.20 A maximum of 50 repetitions.


PRTSYSRPT

21 The SLTLINE parameter and the OMTLINE parameter cannot be specified at thesame time.

22 A maximum of 50 repetitions.23 The SLTFCNARA parameter and the OMTFCNARA parameter cannot be speci-

fied at the same time.24 The SLTCTL parameter and the OMTCTL parameter cannot be specified at the

same time.25 A maximum of 50 repetitions.26 The SLTCTL parameter and the OMTCTL parameter cannot be specified at the

same time.27 A maximum of 50 repetitions.28 The SLTFCNARA parameter and the OMTFCNARA parameter cannot be speci-

fied at the same time.29 A maximum of 50 repetitions.30 The SLTFCNARA parameter and the OMTFCNARA parameter cannot be speci-

fied at the same time.31 A maximum of 50 repetitions.

PurposeThe Print System Report (PRTSYSRPT) command generates and prints a systemoperation overview report from the performance data collected by the Start Per-formance Monitor (STRPFRMON) command. The report is written to the printer fileQPPTSYSR. The system work load, resource utilization expansion, storage poolutilization, disk utilization, and communications summary are presented in thereport.


PRTSYSRPT MBR(APRIL18)

or

PRTSYSRPT MBR(APRIL18) SECTION(\ALL)

These commands print a complete system report for the performance data memberAPRIL18 in library QPFRDATA. The report title is the same as the text in themember.


PRTSYSRPT MBR(NOV1) PERIOD(\SELECT)

TITLE('Intervals with Highest Response Times')

This command prints a system report for the data member NOV1 in libraryQPFRDATA. The user is presented with the interval-selection screen, which allowssorting of the intervals according to various criteria and the selection of certainintervals to be included in the report. The title of the report is "Intervals with HighestResponse Times."

Example 3: Selecting Sections to Include in Report

PRTSYSRPT MBR(NOV1) SECTION(\DSKUTL)


PRTTNSRPT

This command prints only the Disk Utilization section of the system report for thedata member NOV1.

PRTTNSRPT (Print Transaction Report) Command


55─ ─PRTTNSRPT──MBR(──member-name──)─ ──┬ ┬─────────────────────────── ───────5 │ │┌ ┐─QPFRDATA───── └ ┘ ─LIB(─ ──┴ ┴─library-name─ ─)─

5─ ──┬ ┬─────────────────────────────── ─────────────────────────────────────5 │ │┌ ┐─\BLANK───────── └ ┘ ─TITLE(─ ──┴ ┴─'report-title'─ ─)─

5─ ──(P)──┬ ┬───────────────────────────────── ─────────────────────────────────5 │ │┌ ┐──────────────── │ ││ │┌ ┐─\SUMMARY─ └ ┘ ─RPTTYPE(─ ──(1)───

6┴──┼ ┼─\TNSACT── ─)─

├ ┤─\TRSIT─── ├ ┤─\FILE──── └ ┘─\TRCDTA──

5─ ──┬ ┬──────────────────────────────────────────── ────────────────────────5 │ │┌ ┐─\FIRST───── ┌ ┐─\LAST──── └ ┘ ─PERIOD(───(2) ──┴ ┴─start-time─ ──┼ ┼────────── ─)─ └ ┘─end-time─

5─ ──┬ ┬─────────────────────────── ──┬ ┬────────────────────────────────── ───5 │ │┌ ┐─────────── │ │┌ ┐─\ALL─────────── │ ││ │┌ ┐─\SS─ │ ││ │┌ ┐──────────── └ ┘ ─OPTION(─ ──(3)───

6┴──┼ ┼─\SI─ ─)─ ├ ┤ ─SLTJOB(───(4) ──┴ ┴──(5)───

6┴─job-name─ ─)─

├ ┤─\OZ─ │ │┌ ┐─\NONE────────── ├ ┤─\EV─ │ ││ │┌ ┐──────────── ├ ┤─\HV─ └ ┘ ─OMTJOB(───(6) ──┴ ┴──(7)───

6┴─job-name─ ─)─

├ ┤─\DI─ └ ┘─\DQ─

5─ ──┬ ┬──────────────────────────────────────────────────── ────────────────5 │ │┌ ┐─\ALL───────────────────────── │ ││ │┌ ┐────────────────────────── ├ ┤ ─SLTUSRID(───(8) ──┴ ┴──(9)───

6┴──┬ ┬─user-name────────── ─)───

│ │└ ┘─generic\-user-name─ │ │┌ ┐─\NONE───────────────────────── │ ││ │┌ ┐────────────────────────── └ ┘ ─OMTUSRID(────(10) ──┴ ┴───(11) ───

6┴──┬ ┬─user-name────────── ─)─

└ ┘─generic\-user-name─

5─ ──┬ ┬───────────────────────────────────────────────────── ───────────────5 │ │┌ ┐─\ALL─────────────────────────── │ ││ │┌ ┐─────────────────────────── ├ ┤ ─SLTPOOLS(────(12) ──┴ ┴───(13) ───


│ │┌ ┐─\NONE────────────────────────── │ ││ │┌ ┐─────────────────────────── └ ┘ ─OMTPOOLS(────(14) ──┴ ┴───(15) ───


5─ ──┬ ┬─────────────────────────────────────────────────── ─────────────────5 │ │┌ ┐─\ALL──────────────────────── │ ││ │┌ ┐──────────────────────── ├ ┤ ─SLTFCNARA(────(16) ──┴ ┴───(17) ───


│ │┌ ┐─\NONE─────────────────────── │ ││ │┌ ┐──────────────────────── └ ┘ ─OMTFCNARA(────(18) ──┴ ┴───(19) ───



PRTTNSRPT

5─ ──┬ ┬──────────────────────── ────────────────────────────────────────────5 │ │┌ ┐─PRTTNSRPT─ └ ┘ ─JOB(─ ──┼ ┼─\MBR────── ─)─ └ ┘─job-name──

5─ ──┬ ┬──────────────────────────────────────────────── ───────────────────5% │ │┌ ┐─\LIBL/──────── ┌ ┐─QPFRJOBD── └ ┘ ─JOBD(─ ──┬ ┬ ──┼ ┼─────────────── ──┴ ┴─jobd-name─ ─)─ │ │├ ┤─\CURLIB/────── │ │└ ┘─library-name/─ └ ┘─\NONE────────────────────────────

Notes:1 A maximum of 4 report typesP All parameters preceding this point can be specified in positional form.2 *PERIOD contains two lists of one element each. *N must be specified for any


3 A maximum of 5 repetitions4 The SLTJOB parameter and the OMTJOB parameter are mutually exclusive.5 A maximum of 50 repetitions6 The SLTJOB parameter and the OMTJOB parameter are mutually exclusive.7 A maximum of 50 repetitions8 The SLTUSRID parameter and the OMTUSRID parameter are mutually exclu-




sive.15 A maximum of 16 repetitions16 The SLTFNCARA parameter and the OMTFNCARA parameter are mutually



PurposeThe Print Transaction Report (PRTTNSRPT) command is used to create and printperformance reports that show detailed information about the transactions thatoccurred during the time that the performance data was collected. These reportsuse trace data collected by specifying TRACE(*ALL) on the Start PerformanceMonitor (STRPFRMON) command. Jobs may be selectively included in the reportsor excluded from the reports based on a variety of job details and interval times.


PRTTRCRPT

ExamplesExample 1: Printing a Summary Transaction Report

PRTTNSRPT MBR(TUESAM)

This command produces a summary transaction report. The data input to the reportis all the data that exists in member TUESAM in library QPFRDATA. The request issent to batch. The report output is directed to the output queue specified in the jobdescription, QPFRJOBD.

Example 2: Printing a Transaction Detail Report

PRTTNSRPT MBR(TUESAM) RPTTYPE(\TNSACT)

SLTJOB(WSð1)

This command produces a transaction detail report for the selected job, WS01. Therequest is sent to batch. The report output is directed to the output queue specifiedin the job description, QPFRJOBD.

PRTTRCRPT (Print Trace Report) Command


55─ ─PRTTRCRPT──MBR(──member-name──)─ ──┬ ┬─────────────────────────── ───────5 │ │┌ ┐─QPFRDATA───── └ ┘ ─LIB(─ ──┴ ┴─library-name─ ─)─


5─ ──┬ ┬──────────────────────── ────────────────────────────────────────────5 │ │┌ ┐─PRTTRCRPT─ └ ┘ ─JOB(─ ──┼ ┼─\MBR────── ─)─ └ ┘─job-name──


Period: ┌ ┐─\AVAIL───── ┌ ┐─\CURRENT───├─ ──┴ ┴─start-time─ ──┼ ┼─\BEGIN───── ─)─ ──┬ ┬────────────────────────────────── ─┤ └ ┘─start-date─ │ │┌ ┐─\AVAIL─── ┌ ┐─\CURRENT─ └ ┘ ─(─ ──┴ ┴─end-time─ ──┼ ┼────────── ─)─ ├ ┤─\END───── └ ┘─end-date─


element that precedes the value(s) to be specified, to maintain its position in theparameter value sequence.


RMVPEXDFN

PurposeThe Print Trace Report (PRTTRCRPT) command produces a report showingresources utilized, exceptions, and state transitions for batch jobs traced throughtime based on the trace data collected by the Performance Monitor when job typetracing is requested. This report runs against the specified member (in theQTRJOBT file of the QPFRDATA library) that was created when the Print Trans-action Report (PRTTNSRPT) command was run with the *FILE option.

ExamplesExample 1: Printing a Job Trace Summary Report

PRTTRCRPT MBR(JUNEð1)

This command submits a batch job that generates a Job Trace Summary reportusing the performance data found in the member JUNE01 of file QTRJOBT locatedin the default library QPFRDATA. The report covers the entire collection period, andthe title of the report is set to the name of the database file member.

Example 2: Specifying a Report Time Period

PRTTRCRPT MBR(NOV15)

PERIOD(('ð8ðð:ðð' '11/15/89')

('2359:59' '11/15/89'))

TITLE('Job Trace Reports for November 15')

This command submits a batch job that generates a Job Trace Summary report.The performance data comes from member NOV15 of file QTRJOBT of the defaultlibrary QPFRDATA. The report covers the time period 8:00 in the morning to mid-night of one day.

Note: The format for the date and time is determined by the system valuesQDATFMT and, because separators are used in this example, QDATSEP.

RMVPEXDFN (Remove Performance Explorer Definition) Command


55─ ─RMVPEXDFN─ ──(P)─DFN(─ ──┬ ┬─definition-name────────── ─)─ ──────────────────5% ├ ┤─generic\-definition-name─ └ ┘─\ALL─────────────────────


PurposeThe Remove Performance Explorer Definition (RMVPEXDFN) command removesone or more performance explorer definitions from the system. Each definition isstored as a member in the QAPEXDFN file in library QUSRSYS. The membername is the same as the definition name.

Restriction: The user must have object existence authority for file QAPEXDFN inlibrary QUSRSYS.


STRJOBTRC

ExamplesExample 1: Removing a Single Definition

RMVPEXDFN DFN(SAMPLE)

This command removes the member named SAMPLE from file QAPEXDFN inlibrary QUSRSYS that contains the performance explorer definition namedSAMPLE.

Example 2: Removing All Definitions that Start with SAM

RMVPEXDFN DFN(SAM\)

This command removes all definitions with names that start with SAM by removingall members that start with SAM from file QAPEXDFN in library QUSRSYS.

STRJOBTRC (Start Job Trace) Command


55─ ─STRJOBTRC─ ──(P)──┬ ┬───────────────────────────────── ─────────────────────5 │ │┌ ┐─1ð24──────────── └ ┘ ─MAXSTG(─ ──┴ ┴─maximum-K-bytes─ ─)─

5─ ──┬ ┬──────────────────────────────────────────────────────── ───────────5% └ ┘ ─JOB(─ ──┬ ┬─\───────────────────────────────────────── ─)─ └ ┘ ──┬ ┬───────────────────────────── ─job-name─ └ ┘ ──┬ ┬───────────── ─user-name/─ └ ┘ ─job-number/─


PurposeThe Start Job Trace (STRJOBTRC) command starts the OS/400 system job tracingfunction to collect performance statistics about the specified job. It issues the fol-lowing command:

TRCJOB MAXSTG(maxstg) TRCFULL(\STOPTRC)

The MAXSTG value used is either the STRJOBTRC default or a specified value.The STRJOBTRC command issues a Service Job (SRVJOB) command if a jobother than the current job is specified.

Once job tracing is started, a trace record is created for every external (program)call and return, exception, message, and work station wait in the job. At least two,and usually more, trace records are created for every I/O statement (open, close,read, or write) in a high-level language program.

After the target programs have been run, the End Job Trace (ENDJOBTRC)command is used to turn tracing off, record the collected information in a databasefile, and optionally produce reports used to analyze the data. The Print Job Trace(PRTJOBTRC) command may also be used to print the same report at any timethereafter. Alternatively, the command


STRPEX

TRCJOB SET(\CNL)

may be used to cancel the job trace (turn it off without recording any collecteddata).

Tracing has a significant impact on the performance of the current job. It alsoaffects the performance of the system in general, but to a lesser extent.

ExampleSTRJOBTRC MAXSTG(512)

This command starts collecting trace data for the current job. It uses a 512KB tracebuffer, which is large enough to hold about 7000 trace records.

STRPEX (Start Performance Explorer) Command


┌ ┐─\NEW─────55─ ─STRPEX─ ─SSNID(─ ─name──)─ ──(P)─OPTION─ ──┼ ┼─\INZONLY─ ─)─ ───────────────────5 └ ┘─\RESUME──

5─ ──┬ ┬───────────────────────────── ──────────────────────────────────────5% └ ┘ ─DFN(────(1, 2) ─definition-name──)─

Notes:P All parameters preceding this point can be specified in positional form.1 DFN parameter must be specified for OPTION(*NEW) and OPTION(*INZONLY).2 DFN parameter is not valid when OPTION(*RESUME) specified.

PurposeThe Start Performance Explorer (STRPEX) command starts a new performanceexplorer session or resumes a suspended performance explorer session.

Note: You are allowed to have only one performance explorer session at a time.Multiple sessions are not allowed.

Examples Example 1: Start a New Session

STRPEX SSNID(TESTRUN2)

DFN(NEWDESC) OPTION(\NEW)

This command starts a new session of the performance explorer using the criteriaidentified in a definition named NEWDESC. The new session name is TESTRUN2.

Example 2: Resume a Suspended Session

STRPEX SSNID(TESTRUN1)

OPTION(\RESUME)

This is a resume operation for an already existing session of the performanceexplorer named TESTRUN1.


STRPFRT

STRPFRG (Start Performance Graphics) Command


55─ ─STRPFRG─ ──┬ ┬────────────────────────────── ────────────────────────────5 │ │┌ ┐─QPFRDATA───── └ ┘ ─FMTLIB(─ ──┴ ┴─library-name─ ─)─

5─ ──(P)──┬ ┬────────────────────────────── ──┬ ┬─────────────────────── ─────────5 │ │┌ ┐─QPFRDATA───── │ │┌ ┐─\CMD───── └ ┘ ─PFRLIB(─ ──┴ ┴─library-name─ ─)─ └ ┘ ─JOB(─ ──┼ ┼─\MBR───── ─)─ └ ┘─job-name─



PurposeThe Start Performance Graphics (STRPFRG) command calls up the performancegraphics menu giving the user access to all available performance graphics. Thiscommand is valid only in an interactive environment.

ExampleSTRPFRG

This command displays the menu interface for Performance Tools graphics.Library QPFRDATA is used for storing and retrieving graph formats, graph pack-ages, and performance data for this session. Any requests that are submitted to runin batch use job description QPFRJOBD found in the library list.

STRPFRT (Start Performance Tools) Command



WRKFCNARA

55─ ─STRPFRT─ ──(P)──┬ ┬─────────────────────────── ──┬ ┬─────────────────────── ──5 │ │┌ ┐─QPFRDATA───── │ │┌ ┐─\CMD───── └ ┘ ─LIB(─ ──┴ ┴─library-name─ ─)─ └ ┘ ─JOB(─ ──┼ ┼─\MBR───── ─)─ └ ┘─job-name─



PurposeThe Start Performance Tools (STRPFRT) command calls the PerformanceTools/400 menu interface. This shows the Performance Tools main menu(PERFORM), which provides access to all of the Performance Tools.

ExampleSTRPFRT

This command calls the menu interface to Performance Tools. The library,QPFRDATA, is used in storing and getting the performance data for this session.Requests that are submitted to run in batch use the job description QPFRJOBD inthe library list.

WRKFCNARA (Work with Functional Areas) Command


55─ ─WRKFCNARA─ ──(P)──┬ ┬─────────────────────────── ──────────────────────────5% │ │┌ ┐─QPFRDATA───── └ ┘ ─LIB(─ ──┼ ┼────────────── ─)─ └ ┘─library-name─


PurposeThe Work with Functional Areas (WRKFCNARA) command allows the user tocreate, change, copy, and delete functional areas at the menu level.

ExampleWRKFCNARA

This command allows the user to create, change, and delete functional areas at themenu level. The library, QPFRDATA, is used for storing and retrieving functionalareas for this session.


WRKSYSACT

WRKSYSACT (Work with System Activity) Command

FormatJob: I Pgm: I Exec

55─ ─WRKSYSACT─ ──(P)──┬ ┬─────────────────────── ───────────────────────────────5 │ │┌ ┐─\───── └ ┘ ─OUTPUT(─ ──┼ ┼─\FILE─ ─)─ └ ┘─\BOTH─

5─ ──┬ ┬─────────────────────────────────── ──┬ ┬─────────────────── ──────────5 │ │┌ ┐─5─────────────── │ │┌ ┐─\CPU─ └ ┘ ─INTERVAL(─ ──┴ ┴─interval-length─ ─)─ └ ┘ ─SEQ(─ ──┴ ┴─\IO── ─)─

5─ ──┬ ┬───────────────────────── ───────────────────────────────────────────5 │ │┌ ┐─\ALL─── └ ┘ ─INFTYPE(─ ──┼ ┼─\JOBS── ─)─ └ ┘─\TASKS─

5─ ──┬ ┬───────────────────────────────────── ───────────────────────────────5 │ │┌ ┐─6ð────────────────── └ ┘ ─NBRITV(─ ──┴ ┴─number-of-intervals─ ─)─

5─ ──┬ ┬────────────────────────── ──┬ ┬─────────────────────────── ──────────5% │ │┌ ┐─QAITMON───── │ │┌ ┐─QPFRDATA───── └ ┘ ─MBR(─ ──┴ ┴─member-name─ ─)─ └ ┘ ─LIB(─ ──┴ ┴─library-name─ ─)─


PurposeThe Work with System Activity (WRKSYSACT) command allows you to work inter-actively with the jobs and tasks currently running in the system. Besides having thecapability to view this data on the display station, the user may also store the datain a database file.

Restriction:

The user must have *JOBCTL authority to use this command.

ExamplesExample 1: Working with Jobs and Tasks

WRKSYSACT

This command displays both jobs and tasks in descending order of processing timeused.

Example 2: Working with Jobs Only

WRKSYSACT OUTPUT(\BOTH) INFTYPE(\JOBS)

MBR(JOBACT)

This command displays jobs only and writes this information to member JOBACT ofdatabase file QAITMON located in default library QPFRDATA.


Appendix B. Defining Transaction Boundaries

Performance tools reports show different values for transaction service time andresource use, depending on what command you use to analyze the performancedata. These values vary because of differences in the data collected by the com-mands, and can supply different values for the transaction boundary start and endtimes. Be careful when you analyze and compare data collected for the same runusing different tools.

Some of the commands used in this appendix are available only in the Managerfeature. Appendix D, Comparison of Performance Tools, provides additional infor-mation about Performance Tools functions.

Elements of Response TimeThe elements of end-user (external) response time to interactive transactions arecomposed of communications time (input and output) and host (internal) responsetime, as shown in Figure B-1. For locally attached display stations, communicationstime managers the local Work Station Input/Output Processor (IOP) time. Forremotely attached display stations, communications time includes communicationsline time, communications IOP time, and Remote Work Station Controller time asappropriate.

%──────────────── End-User Response Time ─────────────────5

(External Response Time)

│ │ │ │

│─────────────┼────────────────────────────┼──────────────┤

│ │ │ │

Input Host Response Time Output

Communications (Internal Response Time) Communications

Time Time

Figure B-1. Elements of Interactive Response Time

The AS/400 system interactive response time values reported by the Work withActive Job (WRKACTJOB), Print System Report (PRTSYSRPT), Print ComponentReport (PRTCPTRPT), and Print Transaction Report (PRTTNSRPT) commandsrefer only to the host (internal) response time. (An exception to this is the LocalWork Station Report, shown in Figure 7-20 on page 7-33. This report does factorin local work station IOP time.)

For locally attached displays, the communications time is usually less than 1second. For remote displays, the communications time may be longer. To approxi-mate the actual time, use the line speed and number of characters sent andreceived, assuming that the line is not heavily loaded. If the line is heavily loaded,the external response time increases due to the queuing time. Review the lineutilization and data transmission values on the System Report, shown in “What Isthe System Report?” on page 7-17 to determine line component to approximateline time.

Copyright IBM Corp. 1998 B-1

You can also use the BEST/1 capacity planning tool to estimate external responsetimes at local and remote display stations, because BEST/1 projects both internaland external response times. BEST/1 supports only 5250-type devices that areattached either locally through twinaxial cable, remotely through SDLC communi-cations lines, or through LAN-attached work stations.

The host response time can, however, be shown in more detail, as in Figure B-2.

%─────────────────── Host Response Time ─────────────────5

(RT)

│ │ │ │

│ │ │ │

├───────────┼─────────────────────────────────────┼───────────┤

│ │ │ │

│ │ │ │

Ineligible │ Active Time │ EX-Wait

Time │ │ Time

(IT) │ │ (EW)

│ │ │ │ │ │

└─────┼───────┼──────┼───────┼────────┘

│ │ │ │

CPU Wait Disk Wait Wait

Time for CPU I/O for I/O in MPL

(CT) (CW) (DT) (DW) (MW)

Figure B-2. Elements of Host Response Time

Note: Multiprogramming Level (MPL) is a term used interchangeably with ActivityLevel.

The average ineligible time, processing unit time, wait in MPL time, and exceptionalwait time per transaction are available directly from the output of the PRTTNSRPTcommand.

Differences in the Transaction Response ReportsFigure B-3 on page B-3 compares the ways that the Print Job Trace(PRTJOBTRC) command, the PRTTNSRPT command, the PRTSYSRPTcommand, and the WRKACTJOB command determine transaction boundaries.

B-2 Performance Tools V4R2

(WRITE*)

PRTTNSRPT

PRTSYSRPT and WRKACTJOB

(W->A)or

(W->I)

PRTJOBTRC

Work Station I/O Manager(1) External I/O request received (PRTSYSRPT start)(2) Licensed internal code processing complete(3) Job put into activity level or ineligible state(4) Trace record generated (PRTTNSRPT start)

OS/400 System Application(5) Ineligible time complete (I-A)(6) Return to QWSGET (Start of transaction

on job trace)(7) Write to Work Station

Work Station I/O Manager(8) Call QT3REQIO (End of transaction on job trace,

Transaction response times, PRTSYSRPTtransaction end)

(9) Job goes to IOM to wait on I/O (PRTSYSRPTtransaction end)

(10) A-W trace recorded (PRTTNSRPT transaction end)

1 2 3 4 5 6 7 8 9 10

RV2S065-2

( I ->A) (A->W)

Figure B-3. Comparison of Transaction Boundary Definitions

PRTSYSRPT and WRKACTJOB define a transaction from the time it is processedby the Licensed Internal Code I/O manager (Licensed Internal Code IOM) until thesystem work station I/O program QT3REQIO is called to wait for input.

PRTTNSRPT defines a transaction from the time trace records are produced at thebeginning when the job state changes from wait-to-active or wait-to-ineligible (thestart) until the job goes to a long wait (active-to-wait).

Note: Values *DI and *DQ on the OPTION parameter use existing transactionboundary trace records to count transactions instead of the wait-to-activetransition.

These commands include the time the job spent in the ineligible state waiting for anactivity level as part of the transaction response time.

PRTJOBTRC defines a transaction from the time the job becomes eligible (forexample, it is granted an activity level) within the system work station input program(QWSGET), until the system work station I/O program QT3REQIO is called to waitfor input.

Note: This command does not include the time spent in the ineligible state waitingfor an activity level in the transaction boundary definition.

Appendix B. Defining Transaction Boundaries B-3

Operational ConsiderationsLimitations exist in the system’s ability to detect certain types of transactions.

When you review performance reports, be aware of when your system workloadconsists of any of the following types of work:

� Programmable work station servers

� Distributed data management (DDM) servers

� 3270 emulation jobs

� Finance terminals

� Pass-through jobs

Transaction-type data (such as the data collected for throughput and responsetime) is unavailable sometimes, and in some instances (such as for finance types ofwork), cannot be associated with the individual jobs or terminals that originated thetransactions.

When you find that differences exist between the sample data reports(PRTSYSRPT or PRTCPTRPT) and the trace data report (PRTTNSRPT), it is oftendue to the presence of one or more of these types of work. Use the Select/omitoption on the reporting commands to remove these types of jobs so the informationshown on the reports is more representative of your environment.

You may find that the performance tools transaction information is inaccurate forapplications such as RM/COBOL-85 for the AS/400 licensed program that do field-by-field processing. (Field-by-field processing implies that for every field in whichdata is entered, there is processing by the CPU as the field is exited.) The toolsreport each field processed as a transaction. Because these ‘field’ transactions maynot do much processing other than return to the screen to enable the next field tobe entered, the transaction information is skewed. When all of the fields on thescreen have been entered, what would be viewed as a normal transaction occurs,that is, all of the information is processed.

If the transaction information is skewed due to field by field processing, it cannot beused as input to BEST/1. BEST/1 uses the transaction information to establish itsbase information. It then uses the base information to predict the AS/400 modes,response time, transactions, and utilizations for a given number of work stations. Ifthe transaction information is skewed, BEST/1 may give incorrect results.

B-4 Performance Tools V4R2

Appendix C. Correlation of the System/36 and AS/400 SystemPerformance Parameters—Manager Feature

The differences that exist between the AS/400 system and System/36, both hard-ware and software, make it difficult to map performance parameters from onesystem to the other. Table C-1 shows the correlation for some of the keySystem/36 performance parameters. This information is intended for those newAS/400 system users who have a background in System/36 performance analysis.

Table C-1 (Page 1 of 2). Correlation of the System/36 and AS/400 System Performance Parameters

System/36 Parameter AS/400 Parameter

Main storage processorControl storage processor

These parameters correlate to the processor utilization reported by Perform-ance Tools.

See “Resource Utilization” on page 7-19 to see the format of this report. Thisis a portion of the System Report that is produced when you use the PrintSystem Report (PRTSYSRPT) command.

Disk (1-4) The System/36 disk information correlates to the disk utilization.

See “Disk Utilization” on page 7-19 to see the format of this report. This is aportion of the System Report that is produced when you use the PRTSYSRPTcommand.

There is also a Disk Activity Report that is a portion of the Component Report.You produce the Component Report when you use the Print ComponentReport (PRTCPTRPT) command.

Communications lines (1-8) See “Communications Summary” on page 7-19 to see the format of this report.This is a portion of the System Report that is produced when you use thePRTSYSRPT command.

More detailed information is shown in the Communications Report, which is aportion of the Component Report. You produce the Component Report whenyou use the PRTCPTRPT command.

Details about communications lines are in a Resource Interval Report: Commu-nications Line Summary report produced by the Print Resource Report(PRTRSCRPT) command (see “Resource Interval Report” on page 7-76 formore information).

Communications lines information can be displayed by using the Display Per-formance Data (DSPPFRDTA) command.

Translated transfer calls/loads Nothing on the AS/400 system correlates to these counters.User Area Disk Activity(UADA)

The closest correlation is shown in “Storage Pool Utilization” on page 7-19.

This report is a portion of the System Report that is produced when you usethe PRTSYSRPT command.

The faults per second statistics represent the measure of main storage utiliza-tion.

More detailed information can be found in “Storage Pool Activity” onpage 7-26. This report is a portion of the Component Report that is producedwhen you use the PRTCPTRPT command.

Copyright IBM Corp. 1998 C-1

Table C-1 (Page 2 of 2). Correlation of the System/36 and AS/400 System Performance Parameters

System/36 Parameter AS/400 Parameter

Number of disk record waits On the AS/400 system, the corresponding measure is given by seize/lock sta-tistics.

To obtain seize/lock statistics, you must collect trace data when running theperformance monitor. To do this, specify TRACE(*ALL) on the Start Perform-ance Monitor (STRPFRMON) command.

This information is shown as a portion of the special summary reports that arepart of the Transaction Report. To produce it, leave the OPTION(*SS) value onthe PRTTNSRPT command.

A more detailed analysis can also be made by using the Print Lock Report(PRTLCKRPT). See Chapter 10, Performance Utilities—Manager Feature forinformation on this command.

Work station controller utiliza-tion

The local work station controller is included in the IOP Utilizations Report.

This report is a portion of the Component Report that is produced when youuse the PRTCPTRPT command. The IOP Utilizations Report includes the con-troller time in the response times that it shows.

File placement File placement on the AS/400 system has little correlation to that of System/36.The AS/400 operating system, using algorithms to internally partition files,automatically spreads individual files across all available disk drives to balancedisk utilization. This removes the need to do any file placement analysis.

Disk seek operations greaterthan one-third of the disk

Because of the file placement actions taken by the AS/400 operating system,there is essentially no user control that can be applied to this measure (otherthan adding auxiliary disk space).

The statistic can be found as part of the Component Report.

C-2 Performance Tools V4R2

Appendix D. Comparison of Performance Tools

This appendix compares the functional capability of the Manager feature and theAgent feature. It specifically notes the differences in the supported menu optionsand performance commands. Appendix E, Managing AS/400 System Performancein a Network, describes an example of a customer using the Performance ToolsManager feature at a central site and Performance Tools Agent feature at a remotesite.

Comparison of Functions, Menu Options, and CommandsThe Agent feature of Performance Tools provides functions to simplify the col-lection, management, online display, data reduction, and analysis of performancedata on the AS/400 system. Also included in the Agent feature is the performanceexplorer tool (performance utilities). The major Performance Tools functions notcontained in the Agent feature are performance and trace reports, capacity plan-ning, performance utilities (job traces and select file and access group), systemactivity monitoring, and performance graphics.

If you require analysis of trace data, viewing data graphically, viewing systemactivity in real time, or managing and tracking system growth, the Manager featureof the Performance Tools licensed program is more useful.

Table D-1 on page D-2 shows the Performance Tools menu options supported bythe Agent feature.

Copyright IBM Corp. 1998 D-1

Table D-2 shows performance-related commands, and indicates whether they arepart of OS/400, part of the Manager feature of Performance Tools, or part of theAgent feature of Performance Tools.

Table D-1. Comparison of Menu Options

Performance Tools Menu Options Agent Feature

1. Select Type of Status No2. Collect Performance Data Yes3. Print Performance Reports No1. System Report2. Component Report3. Transaction Report4. Lock Report5. Job Report6. Pool Report7. Resource Report8. Batch Job Trace Report4. Capacity Planning No1. Create Best Model5. Performance Utilities1. Work with Job Traces2. Work with Performance Explorer3. Select File and Access Group6. Configure & Manage Tools1. Work with Functional Areas2. Delete Performance Data3. Copy Performance Data Yes4. Convert Performance Data Yes7. Display Performance Data Yes8. System Activity Yes9. Performance Graphics 1. Graph Formats No2. Work with Historical Data Yes3. Display Graphs and Packages No10. Advisor Yes

Table D-2 (Page 1 of 3). Comparison of Performance Commands

Command Description OS/400ManagerFeature

AgentFeature

ADDPEXDFN Add performance explorer definition X

ADDPFRCOL Add performance collection X

ANZACCGRP Analyze variable and file usage X

ANZBESTMDL Analyze BEST/1 model X

ANZDBF Analyze files to be used by a program X

ANZDBFKEY Analyze logical to physical database filerelationships

X

ANZPFRDTA Advisor X X

ANZPGM Analyze files used by a program X

CHGFCNARA Change functional area X

CHGGPHFMT Change graph format X

CHGGPHPKG Change graph package X

D-2 Performance Tools V4R2



AgentFeature

CHGPEXDFN Change performance explorer definition X

CHGPFRCOL Change performance collection X

CPYFCNARA Copy functional area X

CPYGPHFMT Copy graph format X

CPYGPHPKG Copy graph package X

CPYPFRDTA Copy performance data X X

CRTBESTMDL Create BEST/1 model X X

CRTFCNARA Create functional area X

CRTGPHFMT Create graph format X

CRTGPHPKG Create graph package X

CRTHSTDTA Create historical data X X

CVTPFRDTA Convert performance data from onerelease to another

X

| CVTPFRTHD| Convert performance data from thread-| level data to job-level data| X

DLTBESTMDL Delete BEST/1 model X X

DLTFCNARA Delete functional area X

DLTGPHFMT Delete graph format X

DLTGPHPKG Delete graph package X

DLTHSTDTA Delete historical data X X

DLTPEXDTA Delete performance explorer data X

DLTPFRDTA Delete performance data X X

DMPTRC Dump trace data X

DSPACCGRP Display variable and file usage for jobs X

DSPHSTGPH Display historical graph X

DSPPFRDTA View STRPFRMON sample data X X

DSPPFRGPH Display performance graph X

ENDJOBTRC End job data collection activity X

ENDPEX End Performance Explorer X

ENDPFRCOL End performance collection X

ENDPFRMON Stop performance monitor X

PRTACTRPT Print activity report X

PRTCPTRPT Print component report X

PRTJOBRPT Print job report X

PRTJOBTRC Print job trace report X

PRTLCKRPT Print lock report X

PRTPEXRPT Print performance explorer report X X

PRTPOLRPT Print pool report X

Appendix D. Comparison of Performance Tools D-3



AgentFeature

PRTRSCRPT Print resource report X

PRTSYSRPT Print system report X

PRTTNSRPT Print transaction report X

PRTTRCRPT Print batch job data collected by trace X

RMVPEXDFN Remove performance explorer defi-nition

X

STRPEX Start performance explorer X

STRBEST Capacity planning model X

STRJOBTRC Start job trace X

STRPFRCOL Start performance collection X

STRPFRG Start performance graphics X

STRPFRMON Start performance monitor X

STRPFRT Start Performance Tools X X

WRKACTJOB Job performance data X

WRKDSKSTS Disk space and busy X

WRKFCNARA Work with function areas X

WRKPFRCOL Work with performance collection X

WRKSYSACT Display or record task CPU and diskusage

X X

WRKSYSSTS Memory demand and workload rate X

D-4 Performance Tools V4R2

Appendix E. Managing AS/400 System Performance in aNetwork

The following is an example of fictitious Customer A who is managing the growthand performance of each of the 21 AS/400 systems in the company's network.Customer A has a Model D60 at the central site and D10 and D25 models atnumerous remote, worldwide sites. Customer A is interested in managing and mon-itoring the following:

� Transaction throughput

� Processing unit utilization, by job type and priority

� Communications line utilization and error rates

� Disk utilization and occupancy for each AS/400 system

To meet these objectives, Customer A plans to use the performance monitor andautomatic data collection, which are both features of the OS/400 operating system.In addition, they will use the Performance Tools licensed program at the central siteAS/400 system and on remote systems.

Planning the StrategyCustomer A has planned the following strategy:

� Set up automatic data collections at each site, which will include:

– Performance data being collected

– Historical data being created and transmitted to the central site

– The advisor being run, with the results transmitted to the central site

– Data, which was collected more than a month ago, being deleted

� Create monthly reports at the central site.

Note: These reports will be created using the performance graphics functionof Performance Tools.

Implementing the StrategyCustomer A will first set up automatic data collection at the central site by using theWork with Performance Collection (WRKPFRCOL) command to set up data col-lections for Monday’s accounts receivables processing, Wednesday afternoon’s“normal” workload, and for Friday’s accounts payable processing. These are thethree key workloads that Customer A wants to monitor. For each of these, Cus-tomer A specifies the day of the week, time of day to start data collection, and aunique library, using the defaults that are set for two-hour data collections and15-minute samples.

Once Customer A sets up the data collections at the central site, the following filesare sent to each remote system:

QPFRDATA/QAPMSCOL QPFRDATA/QAPMSSCD QPFRDATA/QAPMLSCD

Copyright IBM Corp. 1998 E-1

Customer A then sets up job QGPL/QPFRCOL as an automatic start job on eachsystem (QGPL/QPFRCOL is the default for QBASE and QCTL).

When Customer A is done setting up the data collections, sending the files, andsetting up the automatic start job, the performance monitor schedule is completed.

Note: If you do not already have a job scheduling function, you may be able touse OfficeVision calendar, the sample scheduler in QUSRTOOL, or asimple CL program to provide the function to automate this process.

At the remote site, job scheduling is used to schedule an analysis, data reduction,and a control language (CL) program to transmit data to the central site (seeFigure E-1 on page E-3 for a sample).

E-2 Performance Tools V4R2

START: PGM PARM(&LIB &TOPFRMGR &TOHOST);

/\ Runs the ANZPFRDTA (Advisor) and CRTHSTDTA (Create \/

/\ Historical Data) for the collected data. It then \/

/\ sends the results to the specified Userid at the \/

/\ specified central site. \/

/\ At the central site rename the historical data

/\ files and add the data to the library for each \/

/\ remote system name using RCVNETF. For example: \/

/\ RCVNETF FROMFILE(QAPGHSTD) \/

/\ TOFILE(systemname/\FROMFILE) + \/

/\ FROMMBR(systemname) TOMBR(QAPGHSTD) \/

DCL VAR(&LIB); TYPE(\CHAR) LEN(1ð)

/\ collection library \/

DCL VAR(&TOPFRMGR); TYPE(\CHAR) LEN(1ð)

/\ Host User ID \/

DCL VAR(&TOHOST); TYPE(\CHAR) LEN(1ð)

/\ central node ID \/

DCL VAR(&MBR); TYPE(\CHAR) LEN(1ð)

/\ most recent collection\/

DCL VAR(&SYSNAME); TYPE(\CHAR) LEN(1ð)

/\ system name \/

MONMSG MSGID(CPFðððð)

/\ Monitor for anything +

customize to local requirements \/

RTVMBRD FILE(&LIB/QAPMSYS); MBR(\LAST)

RTNMBR(&MBR);

RTVNETA SYSNAME(&SYSNAME); /\ Get unique system +

name to differentiate files

when received at central site\/

ANZPFRDTA MBR(&MBR); LIB(&LIB); OUTPUT(\PRINT)

/\ Analyze most recently +

collected data in library \/

SNDNETSPLF FILE(QPAVPRT) TOUSRID((&TOPFRMGR &TOHOST)); +

SPLNBR(\LAST) DTAFMT(\ALLDATA)

/\ Create historical data and summary files. \/

/\ The data is put in a new mbr because it will \/

/\ be accumulated at central site rather than this \/

/\ site. BE SURE to RCV the file with MBROPT \ADD \/

CRTHSTDTA MBR(&MBR); LIB(&LIB); JOBD(\NONE)

RMVM FILE(&LIB/QAPGHSTD); MBR(&SYSNAME);

/\ clean up old data \/

RMVM FILE(&LIB/QAPGHSTI); MBR(&SYSNAME);

/\ clean up old data \/

/\ Rename historical data so that a unique \/

/\ name is recognized back at the central site \/

/\ for later review and analysis \/

RNMM FILE(&LIB/QAPGHSTD); MBR(QAPGHSTD)

NEWMBR(&SYSNAME);

Appendix E. Managing AS/400 System Performance in a Network E-3

RNMM FILE(&LIB/QAPGHSTI); MBR(QAPGHSTI)

NEWMBR(&SYSNAME);

/* Send the SUMMARIZED Jobs and IOP data */ SNDNETF FILE(&LIB/QAPGHSTD); TOUSRID((TOPFRMGR &TOHOST)); SNDNETF FILE(&LIB/QAPGHSTI); TOUSRID((TOPFRMGR &TOHOST)); ENDIT: ENDPGM

Figure E-1. CL Program to Collect and Send Historical Data to the Central Site

Also at the remote site, Customer A uses job scheduling to schedule a CL programto regularly remove “old” performance data (see Figure E-2 for a sample).

At the central site, the job schedule function schedules the following:

� A CL program to receive and collect data from remote sites

� A CL program to print advisor reports from remote sites

� The regular generation of monthly historical graph packages, for example:

DSPHSTGPH QIBMPKG LIB (remotesystemname)

OUTPUT(\PRINT) TYPE (\GPHPKG)

� A CL program to perform a regular cleanup of “old” historical data collections

START: PGM PARM(&LIB);

/\ Remove first (oldest) data collection. \/

/\ Done regularly, starting X days after first \/

/\ collection and after each collection thereafter \/

/\ the collection the library will maintain a \/

/\ manageable size \/

DCL VAR (&LIB); TYPE (\CHAR) LEN(1ð)

/\ collection library \/

DCL VAR (&MBR); TYPE (\CHAR) LEN(1ð)

/\ oldest collection \/

MONMSG MSGID (CPFðððð)

/\ Monitor everything–customize as needed\/

RTVMBRD FILE (&LIB/QAPMSYS); MBR(\FIRST)

RTNMBR (&MBR);

DLTPFRDTA MBR (&MBR); LIB(&LIB); JOBD(\NONE)

ENDIT: ENDPGM

Figure E-2. CL Program to Regularly Remove Old Performance Data

Additional CapabilitiesAfter reviewing the advisor output and the historical graphs at the central site, Cus-tomer A may decide that additional detail is needed. This can be done severalways:

� To get more detailed graphics, Customer A could send the appropriateQAPMCONF and QAPGSUMD file members to the central site for processing.Using this method, Customer A could produce performance graphics of types*JOBTYPE, *PRIORITY, or *ALL. However, this method does not allow Cus-tomer A the capability of using select/omit criteria or functional areas.


� If Customer A wants more detailed reports, trace analyses, full modeling, or fullgraphical functions, the remote systems can create a library (using the CopyPerformance Data (CPYPFRDTA) command) containing only the data from thatparticular day. This library can then be transmitted to the central system orsaved to tape and sent to the central system. The central system can use thePerformance Tools program to process the data as if it were collected locally.

Appendix E. Managing AS/400 System Performance in a Network E-5


Appendix F. Performance Checklist—Manager Feature

You may find these checklists useful for planning system performance.

Planning for Performance and Tuning� Provide proper training:

– OS/400 structure, tailoring, basic tuning

– AS/400 performance analysis and capacity planning

� Set measurement criteria:

– Define performance objectives

– Set goals

– Take measurements (will you measure peaks or averages?)

– Review measurements

� Analyze the data.

This requires an understanding of:

– AS/400 commands for collecting data

– Performance Tools programs and reports

– Parameters that affect performance on the AS/400 system, such as:

- Storage pool size, paging

- Size of the process access group (PAG) and purge

- Activity levels

- Time slice

- Job states and transitions

� Schedule performance review meetings—as often as required to review logentries and trends.

� Tune the system using the QPFRADJ (performance adjust) system value. Thevalues could be 0, 1, 2, or 3.

0 QPFRADJ is off

1 QPFRADJ adjusts shared pools at IPL only

2 QPFRADJ automatically tunes the system at IPL and continually

3 QPFRADJ tunes continually, but not at IPL

QPFRADJ compares system performance to the IBM guidelines every 20seconds. If it is not within the guidelines on three consecutive comparisons,QPFRADJ changes the pool sizes, activity level, or both.

Note: You may want to complete QPFRADJ tuning (and then set to 0) beforeyou run Performance Tools.

� Print the error log (PRTERRLOG) for hardware problems, and start the systemservice tools (STRSST command) to display errors.

Copyright IBM Corp. 1998 F-1

Basic TuningYou can choose to let the system tune itself dynamically (QPFRADJ system valueset to 2 or 3), or you can tune it manually. To tune manually :

� For initial tuning before you begin performance analysis, compare the pool sizeand activity levels to the performance guidelines.

� After you complete the initial system tuning:

– Evaluate all changes by measuring.

– Make one change at a time.

� Use the OS/400 CL commands:

– WRKJOB (Work with Job)

– WRKSYSSTS (Work with System Status)

– WRKACTJOB (Work with Active Job)

– WRKDSKSTS (Work with Disk Status)

� If you have Performance Tools installed, use the WRKSYSACT (Work withSystem Activity) command.

Note: This command requires Performance Tools. It is an efficient way todisplay currently active jobs and Licensed Internal Code tasks that usedCPU or disk I/O operations since the last time the display wasrefreshed.

– It can monitor an individual job.

– One job on the system can use the command.

� Start the performance monitor to collect data. (Use the Start PerformanceMonitor (STRPFRMON) command.)

Note: The performance monitor runs without the Performance Tools program.However, Performance Tools is needed to create the reports.

– To collect sample data, suggested parameters on this command are:

- Specific member name

- 5-minute interval

- Trace data *NO

- Dump *YES

The duration depends on the requirements, but in general, the performancemonitor should run long enough to collect information that is meaningful.

– Trace data is collected for detailed performance problem analysis.

| Work with System Status Tips| The Work with System Status identifies page faulting and wait-to-ineligible transi-| tions for each main storage pool.

| � For interactive pools, typically you want the wait-to-ineligible transition values to| be very small (less than 10% of the active-to-wait value). If you see any wait-to-| ineligible value at all, increase the MAXACT value by 5 to 10 until the wait-to-| ineligible is 0. Remember to press F10 to reset the statistics. Wait 10 seconds| between refreshes.

F-2 Performance Tools V4R2

| � The machine pool (pool 1) should have fewer than 10 faults per second, which| is the sum of the database and nondatabase faults. You can ignore the Pages| column.

| � If only system jobs and subsystem monitors are running in *BASE, then the| fault rate for that pool should be less than 30 faults per second.

| � The basic method for tuning your storage pools is to move storage from pools| with good performance to pools with bad performance. In this situation, you| should measure performance in response time or as throughput. Continue to| move storage until the pool with the bad performance gets better, or until the| pool with the good performance gets worse. Do not decrease a pool by more| than 10% at a time.

| � Determining a good fault rate for the user pools can be complicated and will| vary from pool to pool and from system to system. The fault rate alone is not| necessarily a measure of good performance or bad performance.

| – For interactive jobs, look at how much the faults contribute to the end| response time (faults/transaction \ disk response).

| – For batch jobs, look at how much the faults add to the elapsed time of the| job (total faults \ disk response).

| � Use the following formula to calculate the approximate number of page faults| per transaction:

| [(db faults + ndb faults) / active->wait] X 6ð

| Work with Disk Status Tips| The Work with Disk Status shows the percentage of space used and the per-| centage of time that the disk arms are busy. If the average percent for the Busy| column is over 50%, you may need to install more disk arms. The suggestion to| install more disk arms assumes that any page faulting problems have been| addressed.

| Work with System Activity Tips| The Work with System Activity display lists active jobs that have used any CPU in| the last few seconds. The list is sorted in the order of the amount of CPU seconds| that are used, which is the default view. If a high priority job (low number) is using| a lot of CPU (>50%) for an extended period of time, then that job could cause the| entire system to have poor response times. Here are some suggestions for| improving your response time in this situation:

| � If a job or a small set of jobs seems to be using a large percentage of the| CPU, check the job priority (PTY). If the priority of the job is a lower number| than the jobs with poor performance, you may want to consider changing the| priority of the offending job or jobs. Use option 5 (Work with job), then option| 40 (Change job), and specify a larger RUNPTY value (greater than the priority| of the jobs that you want to ran faster).

| � If the offending job is an interactive job that is running a job that is better suited| to run in batch mode, you may want to contact the user and recommend one of| the following:

| – That they submit their work as a batch job

| – That they change the priority of the job to 50. 50 is the typical priority for a| batch job.

Appendix F. Performance Checklist—Manager Feature F-3

| � If the CPU utilization is high (>80%) and all jobs seem to have an equal, but| small, CPU percent, this situation could mean that you have too many active| jobs on the system.

General Tuning Tips� Favor output over input.

– The activity level should not be too high.

– Allow the work to finish.

� Do not mix different types of jobs and priorities in the same pool. (For example,do not mix class entries in subsystem descriptions.)

� Remove batch jobs from *BASE by creating another batch pool.

– Route batch jobs to *SHRPOOL1. One batch job to a pool is ideal. (Jobdescription (JOBD) for routing data; subsystem description (SBSD) forrouting entry).

� Remove programmers from the interactive pool (*INTERACT) by creatinganother interactive pool, *SHRPOOL2 (job description (JOBD) for routing data,subsystem description (SBSD) for routing entry).

General Performance Facts� The size of the process access group (PAG) affects memory utilization. Use the

Display Access Group (DSPACCGRP) command to see the current size.

� You can collect two types of data in Performance Tools:

– Sample Data allows you to print the following reports:

- Advisor Report

- System Report (Workload; Resource Utilization; Resource UtilizationExpansion; Storage Pool Utilization; Disk Utilization; CommunicationSummary)

- Component Report (Interval Activity; Job Workload; Storage Pool; DiskActivity; IOP Utilization; Local Workstation/Resp time)

– Trace Data allows you to print the following reports:

- Advisor Report

- Summary, Transaction, Transition Reports (more detail about trans-actions)

� QTOTJOB system value (QADLTOTJ amount added after original amount).

– Allocates space at IPL

– Sets permanent job structures (work control block table)

Note: QTOTJOB system value should be set at 10% higher than the highestnumber of total jobs in the system. Use the Work with System Status(WRKSYSSTS) command to display the jobs. Leave the value forQADLTOTJ as it is.

� QACTJOB system value (QADLACTJ amount added after original amount).

– Space for temporary job structures allocated at IPL.


– Should be set at highest active job number found. Use the Work with ActiveJobs (WRKACTJOB) command to display. Leave the value for QADLACTJas it is.

� QJOBSPLA remains unchanged.

� If you are in a Client Access environment with the QPFRADJ system value setto 2, the machine pool could be adjusted too low.

� Logical database I/O is one indicator of job activity. Batch or job run timedepends on the CPU time, number of disk operations, and number of excep-tional waits.

Appendix F. Performance Checklist—Manager Feature F-5


Bibliography

The following is a list of related printed information thatmay help you as you use this book.

The books below are listed with their full title and baseorder number.

� BEST/1 Capacity Planning Tool, SC41-5341, pro-vides information about determining your currentsystem performance and predicting your future dataprocessing needs by using BEST/1 to create amodel of your system and analyze it. This bookcontains scenarios that will help you get started withcapacity planning, plus in-depth information aboutspecific topics, such as memory modeling.

� CL Reference, SC41-5722, provides the applicationprogrammer or programmer with a description of theAS/400 control language (CL) and its commands.

(The commands that are specifically related tosystem performance are in Appendix A, “Perform-ance Tools CL Commands” on page A-1 of thisbook.)

� AS/400 Licensed Internal Code Diagnostic Aids -Volume 1, LY44-5900, provides the software servicerepresentative with an information source abouterror logs, dumps, and traces.

� Software Installation, SC41-5120, provides thesystem operator or system administrator with step-by-step procedures for installing the licensed pro-grams from IBM.

� Work Management, SC41-5306, provides the pro-grammer with information about how to create aninitial work management environment and how tochange it.

Copyright IBM Corp. 1998 X-1

X-2 Performance Tools V4R2

Index

Special Characters---------- (pgmname) column 7-102/F indicator 7-115/H indicator 7-115*DI

transaction boundary definitions B-3*DI value

Transaction Report 8-1*DQ

transaction boundary definitions B-3*DQ value

Transaction Report 8-1*SAVSYS (save system) authority 2-1>8.0 column 7-102

Numerics0.0-1.0 column 7-1441.0-2.0 column 7-1442.0-4.0 column 7-1444.0-8.0 column 7-144

AA-I Wait /Tns column 7-102Aborts Recd column 7-102access group

analyzing 10-2, A-5displaying A-30

access path report printer file 10-13accessing work management functions 6-8Act Jobs column 7-102Act Level column 7-102Act Lvl column 7-102Act-Inel column 7-102Act-Wait column 7-102Active Devices column 7-102active display stations (local or remote) 7-103active job

description 6-1interactive transactions count 7-40restrictions 6-1

Active Jobs column 7-103Active Jobs Per Interval column 7-103Active K/T /Tns column 7-103active state 7-133active task

restrictions 6-1Active Wrk Stn column 7-103Active/Rsp column 7-103activity level

definition 1-9

activity level (continued)MPL (multiprogramming level)

response time B-1transaction report (BMPL) 7-107

multiprogramming level (MPL) 7-46response time B-1transaction report (BMPL) 7-107

setting 7-19Activity level column 7-103Activity Level Time column 7-103activity report

printing A-43Add Performance Collection (ADDPFRCOL)

command 3-12Add Performance Collection (ADDPFRCOL)

display 3-12Add Performance Explorer Definition (ADDPEXDFN)

command 11-6, A-2adding

new performance collections 3-12performance explorer definition 11-6, A-2

ADDPEXDFN (Add Performance Explorer Definition)command 11-6, A-2

ADDPFRCOL (Add Performance Collection)command 3-12

address offset column 11-23advanced peer-to-peer networking (APPN)

configuration changes 8-14control point

performance measurements 8-11control point presentation services (CPPS) 8-15control point session activation and

deactivation 8-14directory services registration and deletion

requests 8-13local location list updates

configuration changes 8-14remote location list updates

configuration changes 8-14session setup activities 8-16session setup work activities 8-17session traffic

QAPMSNA file 8-11work activity

topology maintenance 8-12advanced program-to-program communications (APPC)

inbound and outbound transactions 8-21SNA performance measurements 8-3

advisor 4-8changing system tuning values 4-10conclusions, understanding 4-11description 4-1

Copyright IBM Corp. 1998 X-3

advisor (continued)histogram, using 4-5interval conclusions, understanding 4-12performance data, collecting 4-2requesting analysis 4-3restrictions 4-1selecting a member 4-4selecting time intervals 4-4starting 4-3trace data

analyzing 4-7tune system by recommendations of 4-14using results 4-7

Agent featurecomparison D-1relationship to Manager feature 1-3

AI column 11-24analysis by interactive key/think time 7-39analysis by interactive response time 7-39analysis by interactive transaction categories 7-39Analyze Access Group (ANZACCGRP)

command 10-18, A-5Analyze BEST/1 Model (ANZBESTMDL)

command A-2Analyze Database File (ANZDBF) command 10-9,

10-11, A-6Analyze Database File Keys (ANZDBFKEY)

command 10-13, A-7Analyze Performance Data (ANZPFRDTA)

command 4-3, A-7Analyze Program (ANZPGM) command 8-3, 10-9, A-8analyzing

access group 10-2, A-5database file 10-2, A-6database file keys 10-13, A-7file use 3-16job flow 10-2keys for database files report 10-16performance data A-7physical/logical file relationships 10-2process information 10-16program 8-3, 10-2, A-8program/file use 10-2relationships of programs 10-9seize/lock conflicts 7-64system problems, example 13-1trace data 4-7

ANZACCGRP (Analyze Access Group)command 10-18, A-5

ANZACCGRP summaryenvironment summary 10-19file summary 10-22job summary 10-20

ANZBESTMDL (Analyze BEST/1 Model)command A-2

ANZDBF (Analyze Database File) command 10-11,A-6

ANZDBFKEY (Analyze Database File Keys)command 10-13, A-7

ANZPFRDTA (Analyze Performance Data)command 4-3, A-7

ANZPGM (Analyze Program) command 8-3, 10-9, A-8APPC (advanced program-to-program communications)

controller description 8-3inbound and outbound transactions 8-21SNA performance measurements 8-3

APPN (advanced peer-to-peer networking)configuration changes 8-14control point

performance measurements 8-11control point presentation services (CPPS) 8-15control point session activation and

deactivation 8-14directory services registration and deletion

requests 8-13local location list updates

configuration changes 8-14remote location list updates

configuration changes 8-14session setup activities 8-16session setup work activities 8-17session traffic

QAPMSNA file 8-11work activity

topology maintenance 8-12area fill option 9-19Arith Ovrflw column 7-103AS/400 Business Graphics Utility (BGU) 9-1ASP ID column 7-103assigning

threads numbers 7-136ASYNC (asynchronous communications)

database file 3-1Async column 7-103Async DIO /Tns column 7-103Async Disk I/O column 7-103Async Disk I/O per Second column 7-103Async Disk I/O Requests column 7-103Async I/O /Sec column 7-103Async I/O Per Second column 7-104Async Max column 7-104Async Sum column 7-104asynchronous communications (ASYNC)

database file 3-1asynchronous communications data

database file 3-4Asynchronous DBR column 7-104Asynchronous DBW column 7-104Asynchronous disk I/O

definition 7-42


Asynchronous disk I/O per transaction column 7-104Asynchronous NDBR column 7-104Asynchronous NDBW column 7-104Aut Lookup column 7-105Authority Lookup

caching capability 7-105column 7-105definition 7-105

automaticdata collection E-1

performance 3-11setting up 3-13

refresh modeconsiderations 6-4restrictions 6-4updating the display 6-4

auxiliary storage managementtrace event descriptions 11-26

auxiliary storage pooldefinition 4-8

Avail Local Storage (K) column 7-105Available Storage column 7-105Average column 7-105Average DIO/Transaction column 7-105Average Disk Activity Per Hour column 7-105Average K per I/O column 7-105Average Phys I/O /Sec column 7-106Average Reads/Sec column 7-106Average Response column 7-106Average Response Time (seconds) column 7-106Average Response Time column 7-106Average Service Time column 7-106Average Wait Time column 7-106Average Writes/Sec column 7-106Avg CPU /Tns column 7-106Avg K/T /Tns column 7-106Avg Length column 7-106Avg Rsp /Tns column 7-106Avg Rsp (Sec) column 7-106Avg Rsp Time column 7-106Avg Sec Locks column 7-106Avg Sec Seizes column 7-106Avg Time per Service column 7-106Avg Util column 7-106

BBASE

trace event descriptions 11-24Batch asynchronous I/O per second column 7-106Batch CPU seconds per I/O column 7-106Batch CPU Utilization column 7-107Batch impact factor column 7-107Batch Job Analysis

sample report 7-60section description 7-44

Batch Job Trace Reportdescription 7-90Job Summary section 7-90printing 7-89, 7-90sample reports 7-90

Batch permanent writes per second column 7-107Batch synchronous I/O per second column 7-107BBI (begin bracket indicator) bracket delimiter

session traffic fields 8-7BCPU / Synchronous DIO column 7-107begin bracket indicator (BBI) bracket delimiter

session traffic fields 8-7BEST/1 capacity planner

agent feature 1-6introduction 1-6manager feature 1-6

BGU (Business Graphics Utility) 9-1Bin column 7-107Binary Overflow column 7-107binary synchronous communications (BSC)

database file 3-1binary synchronous communications data

database file 3-4bind command

definition 8-16session setup activities 8-16

BMPL - Cur and Inl column 7-107boundaries, transaction B-1boundary values 7-39broadcast search


broadcast search receivedsession setup work activity 8-18

BSC (binary synchronous communications)database file 3-1

Bundle Writes System column 7-107Bundle Writes User column 7-107bus counter database file 3-4Business Graphics Utility (BGU) 9-1Bytes per Second Received column 7-107Bytes per Second Transmitted column 7-107Bytes Recd per Sec column 7-107Bytes Trnsmitd per Sec column 7-107

Ccache

effect on authority lookups 7-105Cache Hit Statistics column 7-108call (external) 10-8call level column 11-18calls made column 11-16capacity planning

description 1-6

Index X-5

case study, performance analysis 13-1Category column 7-107CEBI (conditional end bracket indicator) bracket delim-

itersession traffic fields 8-7

central processing unit (CPU)See processing unit

central site data collection E-1Change Functional Area (CHGFCNARA)

command A-9Change Graph Format (CHGGPHFMT)

command 9-10, A-10Change Graph Package (CHGGPHPKG)

command A-13Change Graph Package display 9-10Change Job Description (CHGJOBD) command 2-1Change Job Type (CHGJOBTYP) command A-14Change Network Attributes (CHGNETA)

command 8-14Change Printer File (CHGPRTF) command 2-1Change Program (CHGPGM) command 11-3changing

functional area A-9graph format 9-10, A-10graph package A-13job description 2-1job type on Print Transaction Report (PRTTNSRPT)

command A-14network attributes 8-14printer file 2-1program 11-3system tuning values 4-10

Channel column 7-108checklist, performance and tuning F-1CHGFCNARA (Change Functional Area)

command A-9CHGGPHFMT (Change Graph Format)

command 9-10, A-10CHGGPHPKG (Change Graph Package)

command A-13CHGJOBD (Change Job Description) command 2-1CHGJOBTYP (Change Job Type) command A-14CHGNETA (Change Network Attributes)

command 8-14CHGPGM (Change Program) command 11-3CHGPRTF (Change Printer File) command 2-1class-of-service (COS) updates

configuration changes 8-14Client Access server

job types 7-118, 7-139Cmn column 7-108Cmn I/O column 7-108Cmn I/O Per Second column 7-108Collect Additional Data display 3-8, 3-9Collect Data with Defaults display 3-7, 7-12

Collect Data with Menus display 3-8Collect Performance Data display 3-6, 7-11collecting

data 3-7performance data

automatically 3-11STRPFRMON (Start Performance Monitor)

command 3-1sample data 3-3trace data

for Lock Report 7-63for Transaction Report 7-37length of time for measurement 3-2storage restrictions 3-2

collection points 11-3Collision Detect column 7-108command, CL

Add Performance Collection (ADDPFRCOL) 3-12Add Performance Explorer Definition

(ADDPEXDFN) 11-6, A-2ADDPEXDFN (Add Performance Explorer

Definition) 11-6, A-2ADDPFRCOL (Add Performance Collection) 3-12Analyze Access Group (ANZACCGRP) A-5Analyze BEST/1 Model (ANZBESTMDL)

command A-2Analyze Database File (ANZDBF) A-6Analyze Database File Keys (ANZDBFKEY) 10-13,

A-7Analyze Performance Data (ANZPFRDTA) A-7Analyze Performance Data (ANZPFRDTA)

command 4-3Analyze Program (ANZPGM) 10-9, A-8ANZACCGRP (Analyze Access Group) 10-18, A-5ANZBESTMDL (Analyze BEST/1 Model)

command A-2ANZDBF (Analyze Database File) 10-2, 10-11, A-6ANZDBFKEY (Analyze Database File Keys) 10-2,

10-13, A-7ANZPFRDTA (Analyze Performance Data) A-7ANZPFRDTA (Analyze Performance Data)

command 4-3ANZPGM (Analyze Program) 10-2, 10-9, A-8Change Functional Area (CHGFCNARA) A-9Change Graph Format (CHGGPHFMT) 9-10, A-10Change Graph Package (CHGGPHPKG) A-13Change Job Description (CHGJOBD) 2-1Change Job Type (CHGJOBTYP) A-14Change Network Attributes (CHGNETA) 8-14Change Printer File (CHGPRTF) 2-1Change Program (CHGPGM) 11-3CHGFCNARA (Change Functional Area) A-9CHGGPHFMT (Change Graph Format) 9-10, A-10CHGGPHPKG (Change Graph Package) A-13CHGJOBD (Change Job Description) 2-1CHGJOBTYP (Change Job Type) A-14


command, CL (continued)CHGNETA (Change Network Attributes) 8-14CHGPGM (Change Program) 11-3CHGPRTF (Change Printer File) 2-1Convert Performance Thread Data

(CVTPFRTHD) 15-6Copy Functional Area (CPYFCNARA) A-17Copy Graph Format (CPYGPHFMT) 9-11, A-17Copy Graph Package (CPYGPHPKG) 9-11, A-18Copy Performance Data (CPYPFRDTA) A-19CPYFCNARA (Copy Functional Area) A-17CPYGPHFMT (Copy Graph Format) 9-11, A-17CPYGPHPKG (Copy Graph Package) 9-11, A-18CPYPFRDTA (Copy Performance Data) A-19Create BEST/1 Model (CRTBESTMDL)

command A-2Create Bound C Program (CRTBNDC) 11-3Create Functional Area (CRTFCNARA) A-20Create Graph Format (CRTGPHFMT) A-21Create Graph Package (CRTGPHPKG) A-24Create Historical Data (CRTHSTDTA) A-25CRTBESTMDL (Create BEST/1 Model)

command A-2CRTBNDC (Create Bound C Program) 11-3CRTFCNARA (Create Functional Area) A-20CRTGPHFMT (Create Graph Format) A-21CRTGPHPKG (Create Graph Package) A-24CRTHSTDTA (Create Historical Data) A-25CVTPFRTHD (Convert Performance Thread

Data) 15-6Delete BEST/1 Model (DLTBESTMDL)

command A-2Delete Functional Area (DLTFCNARA) A-26Delete Graph Format (DLTGPHFMT) A-27Delete Graph Package (DLTGPHPKG) A-27Delete Historical Data (DLTHSTDTA) A-28Delete Performance Data (DLTPFRDTA) 9-14,

A-29Delete Performance Explorer Data

(DLTPEXDTA) A-29Display Access Group (DSPACCGRP) 10-2, A-30Display APPN Information (DSPAPPNINF) 8-13Display File Field Description (DSPFFD) 11-8Display Historical Graph (DSPHSTGPH) 9-2, A-32Display Performance Data (DSPPFRDTA) 5-1,

A-35Display Performance Graph (DSPPFRGPH) 9-2,

A-36DLTBESTMDL (Delete BEST/1 Model)

command A-2DLTFCNARA (Delete Functional Area) A-26DLTGPHFMT (Delete Graph Format) A-27DLTGPHPKG (Delete Graph Package) A-27DLTHSTDTA (Delete Historical Data) A-28DLTPEXDTA (Delete Performance Explorer

Data) A-29

command, CL (continued)DLTPFRDTA (Delete Performance Data) 9-14,

14-3, A-29DMPTRC (Dump Trace) 3-3DSPACCGRP (Display Access Group) 10-2, 10-16,

A-30DSPAPPNINF (Display APPN Information) 8-13DSPFFD (Display File Field Description) 11-8DSPHSTGPH (Display Historical Graph) 9-2, A-32DSPPFRDTA (Display Performance Data) 5-1,

A-35DSPPFRGPH (Display Performance Graph) 9-2,

A-36Dump Trace (DMPTRC) 3-3End Job Trace (ENDJOBTRC) 10-1, 10-3, A-41End Performance Explorer (ENDPEX) 11-7, A-42End Performance Monitor (ENDPFRMON) 3-3ENDJOBTRC (End Job Trace) 10-1, 10-3, A-41ENDPEX (End Performance Explorer) 11-7, A-42ENDPFRMON (End Performance Monitor) 3-3Print Activity Report (PRTACTRPT) 6-9, A-43Print Component Report (PRTCPTRPT) 3-5, 7-25,

A-45Print Job Report (PRTJOBRPT) 7-66, A-48Print Job Trace (PRTJOBTRC) 10-1, A-51Print Lock Report (PRTLCKRPT) 3-5, 7-63, A-52Print Performance Explorer Report

(PRTPEXRPT) 11-8, A-53Print Pool Report (PRTPOLRPT) 7-72, A-56Print Resource Report (PRTRSCRPT) 7-76, A-59Print System Report (PRTSYSRPT) 3-1, 3-5, A-60Print Trace Report (PRTTRCRPT) 3-5, A-66Print Transaction Report (PRTTNSRPT) 3-5, 7-36,

7-90, A-64PRTACTRPT (Print Activity Report) 6-9, A-43PRTCPTRPT (Print Component Report) 3-5, 7-25,

A-45PRTJOBRPT (Print Job Report) 7-66, A-48PRTJOBTRC (Print Job Trace) 10-1, 10-4, A-51PRTLCKRPT (Print Lock Report) 3-5, 7-63, A-52PRTPEXRPT (Print Performance Explorer

Report) 11-8, A-53PRTPOLRPT (Print Pool Report) 7-72, A-56PRTRSCRPT (Print Resource Report) 7-76, A-59PRTSYSRPT (Print System Report) 3-1, 3-5, A-60PRTTNSRPT (Print Transaction Report) 3-5, 7-36,

7-90, A-64PRTTRCRPT (Print Trace Report) 3-5, A-66Remove Performance Explorer Definition

(RMVPEXDFN) A-67Rename Object (RNMOBJ) 2-1RMVPEXDFN (Remove Performance Explorer Defi-

nition) A-67RNMOBJ (Rename Object) 2-1Start BEST/1 (STRBEST) command A-2Start Job Trace (STRJOBTRC) 10-3, A-68

Index X-7

command, CL (continued)Start Performance Explorer (STRPEX) 11-7, A-69Start Performance Graphics (STRPFRG) 9-2, A-70Start Performance Monitor (STRPFRMON) 3-1, 5-1Start Performance Tools (STRPFRT) 2-2, A-70Start Service Job (STRSRVJOB) 10-3STRBEST (Start BEST/1) command A-2STRJOBTRC (Start Job Trace) 10-1, 10-3, A-68STRPEX (Start Performance Explorer) 11-7, A-69STRPFRG (Start Performance Graphics) 9-2, A-70STRPFRMON (Start Performance Monitor) 3-1, 5-1STRPFRT (Start Performance Tools) 2-2, A-70STRSRVJOB (Start Service Job) 10-3Trace Job (TRCJOB) 10-4TRCJOB (Trace Job) 10-4Work with Active Jobs (WRKACTJOB) 2-3Work with Disk Status (WRKDSKSTS) 2-3Work with Functional Areas (WRKFCNARA) A-71Work with Job (WRKJOB) 2-3, 6-6Work with Performance Collection

(WRKPFRCOL) 3-12, 9-16, E-1Work with Spooled Files (WRKSPLF) 7-14Work with Submitted Jobs (WRKSBMJOB) 2-3,

7-13Work with Subsystems (WRKSBS) 2-3Work with System Activity (WRKSYSACT) 6-1, 6-2,

A-72Work with System Status (WRKSYSSTS) 2-3WRKACTJOB (Work with Active Jobs) 2-3WRKDSKSTS (Work with Disk Status) 2-3WRKFCNARA (Work with Functional Areas) A-71WRKJOB (Work with Job) 2-3, 6-6WRKPFRCOL (Work with Performance

Collection) 3-12, 9-16, E-1WRKSBMJOB (Work with Submitted Jobs) 2-3,

7-13WRKSBS (Work with Subsystems) 2-3WRKSPLF (Work with Spooled Files) 7-14WRKSYSACT (Work with System Activity) 6-1, 6-2,

A-72WRKSYSSTS (Work with System Status) 2-3

communications controller database file 3-4Communications I/O Count column 7-108Communications I/O Get column 7-108Communications I/O Put column 7-108communications interval data

displaying 5-13Communications IOP Utilizations

sample report 7-87communications line

displaying detail 5-11displaying interval performance data 5-11performance data time interval 5-13summary of usage 7-19

Communications Line DetailASYNC sample report 7-84

Communications Line Detail (continued)BSC sample report 7-85DDI sample report 7-84ELAN sample report 7-83FRLY sample report 7-84IDLC sample report 7-87ISDN Network Interface sample report 7-85NWI Maintenance sample report 7-86SDLC sample report 7-81section description 7-77TRLAN sample report 7-82X.25 sample report 7-82

Communications Lines column 7-108Communications Summary


communications time B-1Component Interval Activity


Component ReportComponent Interval Activity section 7-25Database Journaling Summary 7-27Database Journaling Summary section 7-27description 7-25Disk Activity section 7-26Exception Occurrence Summary and Interval Counts

section 7-27IOP (input/output processor) Utilizations

section 7-26Job Workload Activity section 7-26Local Work Stations section 7-26printing 7-25, A-45Remote Work Stations section 7-27Report Selection Criteria section 7-28sample reports 7-29Storage Pool Activity section 7-26

composite bar graph 9-6Concurrent Batch Job Statistics


conditional end bracket indicator (CEBI) bracket delim-iter

session traffic fields 8-7configuration changes

APPN local location list updates 8-14APPN remote location list updates 8-14class-of-service (COS) updates 8-14mode updates 8-14

Configure and Manage Tools display 12-1configured ASPs column 11-13Confirm Create of Historical Data display 9-14, 14-2connection fields

description 8-4SNA performance measurements 8-4


control point (CP) capabilitiescontrol point presentation services (CPPS) 8-15

control point presentation services (CPPS)APPN (advanced peer-to-peer networking) 8-15control point (CP) capabilities 8-15directory search (DS) 8-16registration and deletion 8-16topology database update 8-15

control point session activation and deactivationAPPN (advanced peer-to-peer networking) 8-14

control traffic work loadestimating 8-11

Control Units column 7-108controller description

APPC protocol 8-3Convert Performance Thread Data (CVTPFRTHD)

command 15-6converting

down-level performance data 12-9, 15-4historical data 12-10performance data

Agent feature 15-4Manager feature 12-8

thread data 15-6Copy Functional Area (CPYFCNARA) command A-17Copy Graph Format (CPYGPHFMT) command 9-11,

A-17Copy Graph Package (CPYGPHPKG) command 9-11,

A-18Copy Performance Data (CPYPFRDTA)

command A-19Copy Performance Data Member display 12-7, 15-3copying

functional area A-17graph format 9-11, A-17graph package 9-11, A-18performance data A-19

Agent feature 15-2Manager feature 12-7

correlation fieldsdescription 8-4SNA performance measurements 8-4

Count column 7-108counting

users 2-1CPU /Tns column 7-108CPU (central processing unit)

See processing unitCPU (us) column 11-14CPU column 7-108CPU Model column 7-109CPU per I/O Async column 7-109CPU per I/O Sync column 7-109CPU per Logical I/O column 7-109CPU percent column 11-14

CPU QM column 7-109CPU Sec /Sync DIO column 7-109CPU Sec Avg and Max column 7-109CPU Sec column 7-109CPU Sec per Tns column 7-109CPU Seconds column 7-109CPU seconds per transaction column 7-109CPU Util column 7-109CPU Util per Transaction 7-109CPU/Async I/O column 7-109CPU/Sync I/O column 7-109Cpu/Tns (Sec) column 7-109CPU/Tns column 7-109CPYFCNARA (Copy Functional Area) command A-17CPYGPHFMT (Copy Graph Format) command 9-11,

A-17CPYGPHPKG (Copy Graph Package) command 9-11,

A-18CPYPFRDTA (Copy Performance Data)

command A-19Create BEST/1 Model (CRTBESTMDL) command A-2Create Bound C Program (CRTBNDC) command 11-3Create Functional Area (CRTFCNARA)

command A-20Create Graph Format (CRTGPHFMT) command A-21Create Graph Package (CRTGPHPKG)

command A-24Create Graph Package display 9-9Create Historical Data (CRTHSTDTA) command A-25creating

functional area A-20graph format A-21graph package A-24historical data A-25ILE C/400 module 11-3

CRTBESTMDL (Create BEST/1 Model) command A-2CRTBNDC (Create Bound C Program) command 11-3CRTFCNARA (Create Functional Area)

command A-20CRTGPHFMT (Create Graph Format) command A-21CRTGPHPKG (Create Graph Package)

command A-24CRTHSTDTA (Create Historical Data) command A-25Ctl column 7-110cum % column 11-18Cum CPU Util column 7-110Cum Pct Tns column 7-110Cum Util column 7-110cumulative stats column 11-17Cur Inl MPL column 7-110Cur MPL column 7-110CurrentPgm column 11-23CVTPFRTHD (Convert Performance Thread Data)

command 15-6

Index X-9

DDASD Ops per sec column 7-110DASD Ops per sec reads column 7-110DASD Ops per sec writes column 7-110DASD server

trace event descriptions 11-31data (trace) 10-8data areas column 11-13data collection

automatic 3-11performance data 3-1sample 3-3setting the time 3-8setup 3-13summary 3-13system performance data 3-1system-level analysis 3-13trace 3-3using menus 3-8when to collect 3-1when to end 3-3

data queue (*DQ) value 8-1data types

valid for X- and Y-axis values 9-7database file

analyzing A-6high number of file opens and closes 7-41performance trace 7-90QAITMON (collected performance data) 6-1, 6-8QAPMASYN (asynchronous data) 3-4QAPMBSC (binary synchronous communications

data) 3-4QAPMBUS (bus counter data) 3-4QAPMCIOP (communications controller data) 3-4QAPMCONF (system configuration data) 3-4QAPMDBMON (Monitoring data) 3-4QAPMDDI (distributed data interface data) 3-4QAPMDIOP (storage device controller data) 3-4QAPMDISK (disk unit) 3-4QAPMDMPT (trace database file) 3-5, 7-63QAPMECL (establish communications link data) 3-4QAPMETH (Ethernet statistics data) 3-4QAPMFRLY (Frame relay data) 3-4QAPMHDLC (high-level data link control data) 3-4QAPMHDWR (hardware configuration data) 3-4QAPMIOPD (communications processor performance

data) 3-4QAPMJOBS (job data) 3-4QAPMLIOP (local work station controller data) 3-4QAPMMIOP (multifunction controller data) 3-4QAPMPOOL (main storage data) 3-4QAPMRESP (local work station response time

data) 3-4QAPMRWS (remote work station controller

data) 3-4

database file (continued)QAPMSNA (SNA performance measurements

data) 3-4QAPMSTND (DDI station counter data) 3-4QAPMSTNY (Frame relay station counter data) 3-4QAPMSYS (system data) 3-4QAPMTSK (task related performance data) 3-4QAPMX25 (X.25 data) 3-4QAPTAZDR (input file) 10-11, 10-13QAPTLCKD 7-101QAPTLCKD (input file) 7-63QAPTPAGD (input file) 10-18QAPTTRCJ (output file) 10-3QAVPETRCI (collected performance explorer

data) 11-8QPPTSYSR (System Report file) 7-14QTRDMPT 7-96QTRJOBT 7-91QTRJSUM 7-94QTRTSUM 7-91

database file keysanalyzing 10-13, A-7

Database Journaling Summarysample report 7-34section description 7-27

Database Relation Cross Reference Report 10-12database structure analysis 3-16DB Fault column 7-110DB Pages column 7-110DB Read column 7-110DB Write column 7-110DB Wrt column 7-110DDM I/O column 7-110DDM Svr Wait /Tns column 7-110Dec column 7-111Decimal Data column 7-111Decimal Overflow column 7-111default

forms sizeprinter files 2-1

output queueperformance job description 2-1

defaultsusing to print performance reports 7-11

defined by column 11-10definition description column 11-10Definition Information 11-9definition name column 11-10Delete BEST/1 Model (DLTBESTMDL) command A-2Delete Functional Area (DLTFCNARA) command A-26Delete Graph Format (DLTGPHFMT) command A-27Delete Graph Package (DLTGPHPKG) command A-27Delete Historical Data (DLTHSTDTA) command A-28Delete Performance Data (DLTPFRDTA)

command 9-14, 14-3, A-29


Delete Performance Data display 12-5, 15-1Delete Performance Explorer Data (DLTPEXDTA)

command A-29deleting

functional area A-26graph format A-27graph package A-27historical data A-28performance data A-29, E-4

Agent feature 15-1historical data 9-14Manager feature 12-5

performance explorer data A-29Description column 7-111, 11-10destination network node

session setup work activity 8-18Detail Activity Report 6-12Detected Access Transmission Error (DTSE) In

column 7-111Detected Access Transmission Error (DTSE) Out

column 7-111Device column 7-111device description fields


device selectiondefinition 8-20

DIO/Sec Async column 7-111DIO/Sec Sync column 7-111directed search


directory search (DS)control point presentation services (CPPS) 8-16

directory search processingdefinition 8-20

directory services registration and deletion requestsAPPN (advanced peer-to-peer networking) 8-13

diskdetail, displaying 5-10interval, displaying 5-11QAPMJOBS performance monitor file 8-11threshold valve 7-26trace event descriptions 11-26

Disk Activitysample report 7-31section description 7-26

disk activity per hour, average 7-26Disk Arm Seek Distance column 7-111Disk Arms column 7-111disk capacity 7-26Disk Capacity column 7-111Disk Controllers column 7-111Disk CPU Util column 7-111disk detail

displaying performance data 5-10

Disk Feature column 7-111Disk I/O Async column 7-111Disk I/O per Second column 7-112Disk I/O Reads /Sec column 7-112Disk I/O Requests column 7-112Disk I/O Sync column 7-112Disk I/O Writes /Sec column 7-112disk interval

displaying 5-11Disk IOPs column 7-112Disk mirroring column 7-112Disk Space Used column 7-112disk status

working with 2-3Disk transfer size (KB) column 7-112disk unit

displaying 5-11Disk Utilization


Disk utilization column 7-112Disk Utilization Detail


Disk Utilization Summarysample report 7-80section description 7-77

displayAdd Performance Collection (ADDPFRCOL) 3-12Change Graph Package 9-10Collect Additional Data 3-8Collect Data with Defaults 3-7, 7-12Collect Data with Menus 3-8Collect Performance Data 3-6, 7-11Configure and Manage Tools 12-1Confirm Create of Historical Data 9-14, 14-2Copy Performance Data Member 12-7, 15-3Create Graph Package 9-9Delete Performance Data 12-5, 15-1Display by Interval 5-5Display by Job Type 5-4Display by Subsystem 5-4Display Communications Interval Data 5-14Display Communications Line Detail 5-11Display Disk Detail 5-10Display Disk Interval 5-11Display Graphs and Packages 9-15Display Job Detail 5-7Display Jobs 5-6Display Package Contents 9-12Display Performance Data 5-2Display Pool Detail 5-8Display Pool Interval 5-9Display Remote Jobs 5-12IBM Performance Tools 2-2, 7-11Manage Performance Data 15-1

Index X-11

display (continued)Noninteractive Workload 7-138Performance Tools 2-2, 7-11Performance Tools Graphics 9-1Performance Utilities 10-1Print Performance Report 7-6, 7-12Process Access Group 10-16Select Categories for Performance Graphs 9-18Select Categories for Report 7-8Select File and Access Group Utilities 10-2Select Graph Format 9-21Select or Omit Pools 7-9Select Performance Data Member 9-17Select Performance Member 5-1, 12-7, 15-2Select Sections for Report 7-7Select Time Intervals 7-8Select Time Intervals to Analyze 4-4Select Time Intervals to Display 5-2Select Type of Status 2-3Set Data Collection Time 3-8Set End Time 3-9Set Length of Time to Collect Data 3-9Specify Graph Options 9-18Specify Graph Overlay Options 9-22Specify Report Options 7-10, 7-13Start Collecting Data 3-6, 7-11System Activity 6-1Work with All Spooled Files 7-14Work with Graph Formats and Packages 9-3Work with Historical Data 9-13, 14-1Work with Job Traces 10-1Work with Performance Collection 3-12Work with System Activity 6-2, 6-3

Display Access Group (DSPACCGRP)command 10-16, A-30

Display APPN Information (DSPAPPNINF)command 8-13

Display by Interval display 5-5Display by Job Type display 5-4Display by Subsystem display 5-4Display Communications Interval Data display

SDLC (synchronous data link control) 5-14Display Communications Line Detail display 5-11Display Disk Detail display 5-10Display Disk Interval display 5-11Display File Field Description (DSPFFD)

command 11-8Display Graphs and Packages display 9-15Display Historical Graph (DSPHSTGPH)

command 9-2, A-32display I/O (*DI) value 8-1Display Job Detail display 5-7Display Jobs display 5-6Display Package Contents display 9-12Display Performance Data (DSPPFRDTA)

command 5-1, A-35

Display Performance Data display 5-1Display Performance Graph (DSPPFRGPH)

command 9-2, A-36Display Pool Detail display 5-8Display Pool Interval display 5-9Display Remote Jobs display 5-12displaying

access group A-30communication interval data 5-13communications line detail 5-11database file contents 11-8graph

area fill option 9-19format options 9-4historical 9-20output option 9-20overlays 9-21performance 9-16sample data 9-17types 9-4types of data to be graphed 9-6

historical graph A-32information type 6-7performance data 5-1, A-35

by interval 5-5by job 5-6by job type 5-4by subsystem 5-4for system resources 5-8graph overlays 9-21how to use 5-1

performance graph A-36pool detail 5-8pool interval 5-9remote jobs 5-12

Distribution of Processing Unit Transactionssample report 7-52

distribution of transactionsgraphical view 7-40

Distribution of Transactions by CPU/Transactionsection description 7-40

DLTBESTMDL (Delete BEST/1 Model) command A-2DLTFCNARA (Delete Functional Area) command A-26DLTGPHFMT (Delete Graph Format) command A-27DLTGPHPKG (Delete Graph Package) command A-27DLTHSTDTA (Delete Historical Data) command A-28DLTPEXDTA (Delete Performance Explorer Data)

command A-29DLTPFRDTA (Delete Performance Data)

command 9-14, A-29DMPTRC (Dump Trace) command 3-3domain broadcast


down-level performance data, converting 15-4


DSPACCGRP (Display Access Group)command 10-16, A-30

DSPAPPNINF (Display APPN Information)command 8-13

DSPFFD (Display File Field Description)command 11-8

DSPHSTGPH (Display Historical Graph)command 9-2, A-32

DSPPFRDTA (Display Performance Data)command 5-1, A-35

DSPPFRGPH (Display Performance Graph)command 9-2, A-36

Dump Trace (DMPTRC) command 3-3dump trace file 7-96duration of trace (us) column 11-12

EECL (establish communications link) 3-4Elapsed Seconds column 7-112elapsed time (us) column 11-14Elapsed Time column 7-112Elapsed Time—Seconds column 7-112EM3270 Wait /Tns column 7-112Enable performance collection (ENBPFRCOL) param-

eter 11-3ENBPFRCOL (Enable performance collection) param-

eter 11-3End Job Trace (ENDJOBTRC) command 10-1, 10-3,

A-41End Performance Explorer (ENDPEX) command 11-7,

A-42End Performance Monitor (ENDPFRMON)

command 3-3end point session traffic field 8-6end-user (external) response time B-1ending

data collection 3-3job trace 10-1, A-41performance explorer 11-7performance explorer session A-42performance monitor 3-3

ENDJOBTRC (End Job Trace) command 10-3, A-41ENDPEX (End Performance Explorer) command 11-7,

A-42ENDPFRMON (End Performance Monitor)

command 3-3EORn column 7-113EOTn column 7-113Est Of AWS column 7-113establish communications link (ECL) 3-4Estimated Exposr AP Not Jrnld column 7-113Estimated Exposr Curr System column 7-113Ethernet statistics database file 3-4event (handler) 10-8

event column 11-23Event Wait /Tns column 7-113EVT column 7-113example

thread numbers 7-136Exception Occurrence Summary and Interval Counts


Exception Type column 7-113Exceptional wait

column 7-114definition 7-114

Excp column 7-114Excp Wait /Tns column 7-114Excp Wait column 7-114Excp Wait Sec column 7-114Excs ACTM /Tns column 7-114EXID column 11-24existence end column 11-14existence start column 11-14Expert Cache column 7-115Exposed AP System Journaled column 7-115Exposed AP System Not Journaled column 7-115external response (end user) time

definition 1-4external response time B-1EXTXHINV (external exception handler) 10-8EXTXHRET (call termination) 10-8

Ffacts, performance F-4Far End Code Violation column 7-115file

output 10-4File and Access Group Utilities commands

ANZDBF (Analyze Database File) 10-2DSPACCGRP (Display Access Group) 10-2

File column 7-115file use analysis 3-16file use and database structure report commands

summary 3-16File-to-Program Cross-Reference Report 10-11finding

performance explorer definitions 11-9floating-bar graph

description 9-6Flp column 7-115Flp Overflow column 7-115forms size, default 2-1Frame Retry column 7-115Frames Received Pct Err column 7-115Frames Received Total column 7-115Frames Transmitted Pct Err column 7-115Frames Transmitted Total column 7-115

Index X-13

full duplex indicator 7-115functional area

changing A-9copying A-17creating A-20deleting A-26working with 12-2, A-71

Functional Areas column 7-115

GGDF (graphics data format) file 9-1GETDR (get direct) operation 10-7GETKY (get by key) operation 10-7GETM (get multiple) operation 10-7GETSQ (get sequential) operation 10-7GO LICPGM menu 2-1graph

formatarea fill option 9-19changing 9-10creating 9-4displaying 9-15QIBMASYNC 9-2QIBMCMNIOP 9-2QIBMCPUTYP 9-2QIBMCPYPTY 9-2QIBMDSKARM 9-2QIBMDSKIOP 9-2QIBMDSKOCC 9-2QIBMLWSIOP 9-2QIBMMFCIOP 9-2QIBMMFDIOP 9-2QIBMPCTDSK 9-2QIBMPKG 9-3QIBMRSP 9-2QIBMSYNC 9-2QIBMTNS 9-2QIBMTOTDSK 9-2search for formats in the library 9-3select performance data member 9-17selecting categories for performance

graphs 9-18specifying graph options 9-18

optionarea fill 9-19output 9-20overlays 9-21

packagechanging 9-10copying 9-11creating 9-9deleting 9-12displaying 9-15QIBMPKG 9-3searching for packages in the library 9-3selecting performance data members 9-17

graph (continued)package (continued)

specifying graph options 9-18type

composite bar 9-6floating-bar 9-6line 9-4scatter plot 9-5surface 9-5

graph formatchanging A-10copying A-17creating A-21deleting A-27

graph packagechanging A-13copying A-18creating A-24deleting A-27

graphics, performancedisplaying 9-20

graph format options 9-4graph overlays 9-21graph package contents 9-12graph types 9-4graphs 9-15historical graphs 9-20maximum number of legend entries 9-9packages 9-15performance graphs 9-16sample graphs 9-12, 9-17types of data to be graphed 9-6

historical graphschanging package 9-10copying package 9-11creating formats 9-4creating historical data 9-14creating package 9-9deleting historical data 9-15deleting package 9-12displaying graphs and packages 9-15searching for data 9-14summary 9-1

performance graphschanging package 9-10copying package 9-11creating formats 9-4creating package 9-9deleting package 9-12displaying 9-16displaying graphs and packages 9-15output option 9-20summary 9-1


Hhalf duplex indicator 7-115HDW column 7-116high priority session traffic field 8-6High Srv Time column 7-116High Srv Unit column 7-116High Util column 7-116High Util Unit column 7-116High Utilization Disk column 7-116High Utilization Unit column 7-116hints, tuning F-4histogram 4-5histogram column 11-18historical data

converting 12-10creating 9-14, 14-2, A-25deleting 9-15, 14-3, A-28displaying 9-13displaying graphs 9-20

historical graphdisplaying A-32

hit % column 11-18hit cnt column 11-18HLL-No column 11-23Holder Job Name column 7-116Holder Number column 7-116Holder Pool column 7-116Holder Pty column 7-116Holder Type column 7-116Holder User Name column 7-116Holder’s Job Name column 7-116host (internal) response time B-1host controller description

SNA performance measurements 8-3

II Frames Recd per Sec column 7-116I Frames Trnsmitd per Sec column 7-116I/O Wait column 7-116IEID column 11-24ILE C/400 module

creating 11-3inbound and outbound transactions 8-22include dependent jobs column 11-10Incoming Calls Pct Retry column 7-116Incoming Calls Total column 7-116Individual Transaction Statistics


Inel Time A-I/W-I column 7-116Inel Wait column 7-116ineligible state 7-133information type

displaying 6-7

information type (INFTYPE) parameter 6-7INFTYPE (information type) parameter 6-7initial screening

definition 8-20initial topology exchange

topology maintenance 8-13inline stats column 11-16INPACING parameter 8-9input/output processor (IOP)

resource name and model number linecolumn 7-117

utilization 7-26installing Performance Tools

Agent feature 2-1GO License Program menu options 2-1Manager feature 2-1

integrated services digital network (ISDN)statistics data file

QAPMIDLC, B-channel 3-4QAPMLAPD, D-channel 3-4

Inter CPU Utilization column 7-116Interactive CPU Utilization by 5-Minute Intervals


Interactive Job Detailsection description 7-67

Interactive Job Detail sectionsample report 7-69

Interactive Job Summarysample report 7-68section description 7-67

interactive key/think time, analysis by 7-39Interactive Program Statistics


Interactive Program Transaction Statisticssample report 7-56section description 7-41

interactive response timeanalysis by 7-39Job Summary Report 7-40

Interactive Response Time by 5-Minute Intervalssample report 7-55section description 7-40

Interactive Throughput by 5-Minute Intervalssample report 7-54section description 7-40

interactive transaction averages by job type 7-39interactive transaction categories, analysis by 7-39Interactive Transactions by 5-Minute Intervals

sample report 7-54, 7-55section description 7-40

Interactive Workloadsample report 7-20section description 7-18

Index X-15

intermediate node on directed searchsession setup work activity 8-18

intermediate session traffic field 8-6intermediate session traffic work load

estimating 8-11internal (host) response time

definition 1-4elements B-1

internal session-level pacingdescription 8-9excessive waiting 8-9INPACING and OUTPACING parameters 8-8

INTXHINV (internal exception handler) 10-8INTXHRET (return from an exception) 10-8INVEXIT (call exit routine) 10-8IOP (input/output processor) Utilizations


IOP Name column 7-117IOP Name Network Interface column 7-117IOP Name/Line 7-117IOP Name(Model) column 7-117IOP Processor Util Comm column 7-117IOP Processor Util DASD column 7-117IOP Processor Util LWSC column 7-117IOP Processor Util Total column 7-117IOP Util column 7-117IOP Utilizations

section descriptioncommunications 7-78disk 7-78local work station 7-78multifunction 7-78

ITERM (intervening call termination) 10-8ITRMXRSG (resignaling exception) 10-8Itv End column 7-117

JJava

trace event descriptions 11-32job

database file 3-1flow 10-2operational environment 3-16remote 5-12restrictions on active 6-1trace event descriptions 11-28tracing 10-4working with 6-6

job CPU column 11-15job creating session column 11-13job data

merging areas 11-7separating areas 11-7

job descriptionchanging 2-1

Job Interval Report 7-132description 7-67Interactive Job Detail section 7-67Interactive Job Summary section 7-67Noninteractive Job Detail section 7-68Noninteractive Job Summary section 7-67printing 7-66Report Selection Criteria section 7-68sample reports 7-68

Job Maximum A-I column 7-117Job Maximum A-W column 7-117Job Maximum CPU Util column 7-117Job Maximum Phy I/O column 7-118Job Maximum Rsp column 7-118Job Maximum Tns column 7-118Job Maximum W-I column 7-118Job Name column 7-118, 11-15Job Number column 7-118Job Pty column 7-118job report

printing A-48job schedule function E-2Job Set column 7-118job states

active 7-133ineligible 7-133possible 7-46wait 7-133

Job Statisticsprinting 7-42sample report 7-58section description 7-42

Job Summary 7-45sample report 7-49section description 7-38

Job Summary Datasection description 7-46System Summary Data 7-39

job summary file 7-94Job Summary Report

Batch Job Analysis section 7-44Concurrent Batch Job Statistics section 7-44description 7-38Distribution of Transactions by CPU/Transaction

section 7-40including special system information 7-41Individual Transaction Statistics section 7-43Interactive CPU Utilization by 5-Minute Intervals

section 7-40Interactive Program Statistics section 7-42Interactive Program Transaction Statistics

section 7-41Interactive Response Time by 5-Minute Intervals

section 7-40


Job Summary Report (continued)Interactive Throughput by 5-Minute Intervals

section 7-40Interactive Transactions by 5-Minute Intervals

section 7-40Job Statistics section 7-42Job Summary section 7-38Longest Holders of Seize/Lock Conflicts

section 7-44Longest Seize/Lock Conflicts section 7-43output (QPSPDJS) 7-37printing 7-36Priority-Jobtype-Pool Statistics section 7-42Report Selection Criteria sample report 7-61Report Selection Criteria section 7-45RPTTYPE(*SUMMARY) option 7-38sample report 7-49Scatter Diagram section 7-41Summary of Seize/Lock Conflicts by Object

section 7-41System Summary Data sections 7-39Transaction Significance section 7-40

Job Summary—Batch Job Trace Reportsample report 7-90section description 7-90

job traceanalysis 3-15command

ENDJOBTRC (End Job Trace) 10-1PRTJOBTRC (Print Job Trace) 10-1STRJOBTRC (Start Job Trace) 10-1

data collection command summary 3-15database file 3-4ending 10-1, A-41flow 10-2printing 10-1, A-51report command summary 3-15starting 10-1, A-68statistics 7-42stopping 10-1working with 10-1

job typeaverage resource use per transaction 7-19changing on Print Transaction Report (PRTTNSRPT)

command A-14Job Type column 7-118Job Workload Activity


job/task name column 11-14Jobs column 7-120jobs in session column 11-13jobs/tasks in session column 11-13journal deposits

System Total column 7-136System ToUser column 7-136

KK per I/O column 7-120K/T /Tns Sec column 7-120KB per I/O Read column 7-120KB per I/O Write column 7-120Key Fields and Select/Omit Listing Report 10-14Key/Think /Tns column 7-120Key/Think column 7-120keys, software license 2-1

LL column 7-120LAPD Pct Frames Recd in Error column 7-120LAPD Pct Frames Trnsmitd Again column 7-120LAPD Total Frames Recd column 7-120LAPD Total Frames Trnsmitd column 7-121Last 4 Programs in Invocation Stack column 7-121legends

description 9-9maximum number of entries 9-9

Length of Wait column 7-121Lgl I/O /Sec column 7-121library

QGPL 12-11, 15-5QPFR 2-1, 2-2QPFRDATA 3-7, 9-2QSYS 10-6

Library column 7-121, 11-10, 11-11LIC-Pgm--Offset column 11-24license keys 2-1Licensed Internal Code

tasks 6-1Line Count column 7-121Line Descriptn column 7-121Line Errors column 7-121line graph 9-4Line Speed column 7-121line transmission

description 8-10limitations 8-10

Line Util column 7-121LKRL column 7-121LKW column 7-121LKWT column 7-121Local End Code Violation column 7-122Local Not Ready column 7-122local work station controller (WSC) 3-4Local work station IOP utilization column 7-122Local work station IOPs column 7-122local work station response time database file 3-4Local Work Station Response Times


Index X-17

Local Work Stations – Response Time Bucketssample report 7-33section description 7-26

locally started sessions (source)session setup work activity 8-17

lock 7-41analyzing conflicts 7-64conflicts by object 7-41longest conflicts 7-43longest holders of conflicts 7-44

Lock Conflict column 7-122Lock Report

description 7-64printing 3-5, 7-63, A-52resource management 7-63resource management and trace data 7-63sample detail report 7-66sample summary report 7-66Seize/Lock Statistics by Time of Day 7-64Seize/Lock Wait Statistics Summary 7-64trace data 7-63

Lock Wait /Tns column 7-122lock-wait 7-38Logical column 7-122logical DASDs column 11-13Logical Database I/O Other column 7-122Logical Database I/O Read column 7-122Logical Database I/O Write column 7-122Logical DB I/O column 7-122Logical DB I/O Count column 7-122Logical Disk I/O column 7-122logical file key report printer file 10-14Logical File Listing Report 10-13Logical I/O /Second column 7-122Logical I/O Per Second column 7-122Long Wait column 7-123Long Wait Lck/Oth column 7-123Longest Holders of Seize/Lock Conflicts


Longest Seize/Lock Conflictssample report 7-59section description 7-43

Loss of Frame Alignment column 7-123low priority session traffic field 8-6

MMAC Errors column 7-123machine object

definition 7-99main storage

database file 3-4Main storage (MB) column 7-123Manage Performance Data display 15-1

Manager featurecomparison D-1relationship to Agent feature 1-3

map flag column 11-18mapping

statements to source code 11-35Max Util column 7-123Maximum column 7-123measured response time

Job Summary Report 7-41medium priority session traffic field 8-6Member column 7-123, 11-10menus

GO LICPGM 2-1using to print performance reports 7-6

Merge job data (MRGJOB) parameter 11-7merging

job data 11-7MI complex instructions

trace event descriptions 11-34MI CPLX issued column 11-16MI-Pgm--Offset column 11-24Minimum column 7-123missed events due to buffering column 11-13missed events due to recording column 11-13mode updates

configuration changes 8-14module column 11-11monitoring specific jobs 6-5MPL (multiprogramming level)

in the activity level 7-107on the ineligible queue 7-107transaction report (BMPL) 7-107transition report 7-46

MRGJOB (Merge job data) parameter 11-7MRT Max Time column 7-123multifunction controller database file 3-4multiple processors 6-3, 6-12, 7-138multiprogramming level (MPL)

in the activity level 7-107on the ineligible queue 7-107transaction report (BMPL) 7-107transition report 7-46

NNAGP column 11-24name column 11-10, 11-19, 11-23Nbr A-I column 7-123Nbr Evt column 7-123Nbr Jobs column 7-123Nbr Sign offs column 7-123Nbr Sign ons column 7-123Nbr Tns column 7-123Nbr W-I column 7-124


NDB Read column 7-124NDB Write column 7-124NDB Wrt column 7-124network attributes

changing 8-14network node processing

session setup work activity 8-18network priority session traffic field 8-6network transmission priority 8-9NNS(DLU) network node


NNS(OLU) network nodedefinition 8-17session setup activities 8-17

node congestion updatestopology maintenance 8-12

Non-DB Fault column 7-124Non-DB Pages column 7-124Noninteractive Job Detail


Noninteractive Job Summarysample report 7-69section description 7-67

Noninteractive Workloadsample report 7-21

Notices xiiiNPgs column 11-24Number column 7-124, 11-10Number I/Os per Second column 7-124Number Jobs column 7-124Number Lck Cft column 7-124Number Lck Conflict column 7-124Number Locks column 7-124Number of batch jobs column 7-124number of brackets ended

tpNEB field 8-7number of brackets started

tpNBB field 8-7number of events column 11-12Number of Jobs column 7-124number of sessions ended

tpNSE field 8-7number of sessions started

tpNSS field 8-7Number Seizes column 7-124Number Sze Cft column 7-124Number Sze Conflict column 7-125Number Tns column 7-125Number Traces column 7-125Number Transactions column 7-125

OObj T ST column 11-23object

forms size 2-1renaming 2-1

Object File column 7-125Object Library column 7-125Object Member column 7-125Object Name column 7-125, 11-23Object RRN column 7-125Object Type column 7-125obsolete topology entry removal

topology maintenance 8-13OCR (over commitment ratio) 7-126OMIT parameter 7-45

Component Report 7-28Component Report sample 7-35System Report 7-20System Report sample 7-24

Omit Parameters column 7-126Omit system tasks field 7-10OMTCTL (control units excluded) parameter 7-108OMTFCNARA (functional areas excluded)

parameter 7-115OMTJOB (jobs excluded) parameter 7-120OMTLINE (communications lines excluded)

parameter 7-108OMTSBS (subsystems excluded) parameter 7-134OMTUSRID (users excluded) parameter 7-141one hop search

definition 8-17Op per Second column 7-126operational environment of jobs 3-16OPM (original program model) 11-35OPTION(*SS) 7-41original program model (OPM) 11-35OS/400

collecting data 1-2monitoring 1-2tuning 1-2

OS/400 level column 11-13OS/400 Performance Monitor 3-11Other Wait /Tns column 7-126Outgoing Calls Pct Retry column 7-126Outgoing Calls Total column 7-126OUTPACING parameter 8-9output

files 10-4option 9-20queue 2-1

Overcommitment ratio column 7-126overhead removed column 11-16overlays, graph 9-21

Index X-19

PP (Processor Number) column 11-23pacing response

average amount of time spent waiting 8-8pacing window size 8-8packages, graph

changing 9-10copying 9-11creating 9-9deleting 9-12displaying 9-15selecting performance data members 9-17specifying graph options 9-18

PAG (process access group)analysis 10-16utilities 10-2

PAG column 7-126PAG Fault column 7-127Page Count column 7-127page fault

trace event descriptions 11-27pane size column 11-11parameter

ENDTNS (end transaction) 10-4INFTYPE (information type) 6-7INPACING parameter 8-9OMIT 7-20OMTCTL (control units excluded) 7-108OMTJOB (jobs excluded) 7-120OMTLINE (communications lines excluded) 7-108OMTSBS (subsystems excluded) 7-134OMTUSRID (users excluded) 7-141OMTxxx (data records excluded) 7-132OUTPACING parameter 8-9RPTTYPE (report type) 7-36SELECT 7-20SEQ (sequence) 6-12SLTCTL (control units included) 7-108SLTJOB (jobs included) 7-120SLTLINE (communications lines included) 7-108SLTSBS (subsystems included) 7-134SLTUSRID (users included) 7-141SLTxxx (data records included) 7-132STRTNS (start transactions) 10-4TITLE (title) 6-10

pass-through transaction path 8-34Pct CPU By Categories column 7-127Pct Data Characters Received in Error column 7-127Pct Data Characters Transmitted in Error

column 7-127Pct Ex-Wt /Rsp column 7-127Pct Of Tns Categories column 7-127Pct PDUs Received in Error column 7-127Pct Poll Retry Time column 7-127

Pct Tns column 7-127percent column 11-23Percent Errored Seconds column 7-128Percent Frames Received in Error column 7-128Percent Full column 7-128Percent I Frames Trnsmitd in Error column 7-128Percent Severely Errored Seconds column 7-128Percent transactions (dynamic no) column 7-128Percent transactions (purge no) column 7-128Percent transactions (purge yes) column 7-128Percent Util column 7-128Percentage of Processing Unit by Transaction Catego-

riessample report 7-53

performanceanalysis 1-7, 13-1checklist F-1concepts 1-2correlation of System/36 and AS/400 performance

parameters C-1data

collection 3-1converting 15-4converting down level 15-4copying 15-2deleting 15-1, E-4

data collection 3-1displaying data

by interval 5-5by job 5-6by job type 5-4communications line detail 5-11disk interval 5-11graph overlays 9-21pool detail 5-8pool interval 5-9STRPFRMON (Start Performance Monitor)

command 5-1ending data collection 3-3managing in a network E-1measurement analysis 1-6objectives 1-3stopping data collection 3-3transaction 10-2why manage 1-1

performance analysisoverview 1-8PRTSYSRPT (Print System Report) command

overview 1-7performance collection

ENBPFRCOL (Enable performance collection) 11-3pre-defined collection points 11-3setup 3-13

performance dataanalyzing A-7converting 12-8


performance data (continued)converting obsolete 12-9copying 12-7, A-19deleting 12-5, A-29display by interval 5-5display by job 5-6display by job type 5-4display by subsystem 5-4displaying 5-1, A-35displaying graphs 9-16

performance exploreradding

definition 11-6, A-2database file

QAVPETRCI 11-8definition

changing A-14finding 11-9removing A-67

deletingdata A-29

ending 11-7session A-42

findingdefinition 11-9

mappingstatements to source code 11-35

reportsprinting 11-8

starting 11-7, A-69performance explorer report

column descriptionsaddress offset 11-23AI 11-24call level 11-18calls made 11-16configured ASPs 11-13CPU (us) 11-14CPU percent 11-14cum % 11-18cumulative stats 11-17CurrentPgm 11-23data areas 11-13defined by 11-10definition description 11-10definition name 11-10description 11-10duration of trace (us) 11-12elapsed time (us) 11-14event 11-23EXID 11-24existence end 11-14existence start 11-14histogram 11-18hit % 11-18hit cnt 11-18HLL-No 11-23

performance explorer report (continued)column descriptions (continued)

IEID 11-24include dependent jobs 11-10inline stats 11-16job CPU 11-15job creating session 11-13job name 11-15job/task name 11-14jobs in session 11-13jobs/tasks in session 11-13library 11-10, 11-11LIC-Pgm--Offset 11-24logical DASDs 11-13map flag 11-18member 11-10MI CPLX issued 11-16MI-Pgm--Offset 11-24missed events due to buffering 11-13missed events due to recording 11-13module 11-11NAGP 11-24name 11-10, 11-19, 11-23NPgs 11-24number 11-10number of events 11-12Obj T ST 11-23object name 11-23OS/400 level 11-13overhead removed 11-16P (Processor Number) 11-23pane size 11-11percent 11-23pgm/mod CPU 11-16PI 11-24pool 11-14PREFIX 11-24priority 11-14procedure 11-11program 11-11, 11-23RC Delta 11-23run cycles 11-23run time (us) 11-23sample interval (ms) 11-11sector 11-24Seg T ST 11-24selected jobs 11-10selected MI complex instructions 11-10selected programs 11-11selected task names 11-10serial number 11-13session name 11-12sessions since IPL 11-12SKP XCH 11-24span 11-24ss.mmm 11-23start addr 11-18

Index X-21

performance explorer report (continued)column descriptions (continued)

start time 11-12started by user 11-13stmt numb 11-18stop time 11-12suspend time (us) 11-12system model 11-13system type 11-13target system 11-13task CPU 11-15task ID 11-14, 11-23time stamp 11-22times called 11-16total CPU 11-15, 11-16total hits 11-15total pages memory 11-13total raw CPU 11-16total samples 11-15total time 11-12trace wrap count 11-12type 11-10, 11-11unit 11-24unknown CPU 11-16user 11-10version 11-13

printing A-53performance facts F-4performance graph

displaying A-36performance graphics

displayinggraph format options 9-4graph overlays 9-21graph package contents 9-12graph types 9-4graphs 9-15historical graphs 9-20legends, maximum number of entries 9-9packages 9-15performance graphs 9-16sample graphs 9-12, 9-17types of data to be graphed 9-6

historical graphschanging package 9-10copying package 9-11creating formats 9-4creating historical data 9-14creating package 9-9deleting historical data 9-15deleting package 9-12displaying 9-15, 9-20searching for data 9-14summary 9-1

performance graphschanging package 9-10copying package 9-11

performance graphics (continued)performance graphs (continued)

creating formats 9-4creating package 9-9deleting package 9-12displaying 9-16output option 9-20selecting categories 9-18summary 9-1

starting A-70performance history

collecting sample data 3-1report 3-1

performance indicators 8-21performance management

using OS/400 1-2performance measurement

collecting data 1-6producing a system report 1-6

Performance Measurement and SNADS 8-23performance monitor

ending 3-3job schedule function E-2starting 3-1

performance objectivesestablishing 1-3

performance parameterscorrelation of System/36 and AS/400 C-1description C-1

performance reportsanatomy of 7-1available 7-3choosing 7-5column descriptions 7-102Component Report 7-25general description 7-1header information 7-1Job Interval Report 7-67printing 7-6, 7-11Transaction Report 7-46using defaults to print 7-11using menus to print 7-6

Performance ToolsAgent feature 1-3and OS/400 function 1-2default output queue 2-1installing 2-1introduction 1-1Manager feature 1-3restrictions 1-3starting A-70

Performance Tools Graphics display 9-1Performance Tools menu 2-2, 7-11Performance Utilities display 10-1Perm Write column 7-128


Permanent writes per transaction column 7-128pgm/mod CPU column 11-16Physical I/O Count column 7-128PI (pool identifier) column 11-24Pl (Pool) column 7-129planning for performance tuning F-1planning, capacity 1-6pool

detail, displaying 5-8interval, displaying 5-9

Pool Activitysample report 7-74section description 7-73

Pool column 7-129, 11-14Pool ID column 7-129Pool ID Faults column 7-129Pool Interval Report

description 7-73Pool Activity 7-73printing 7-73Report Selection Criteria section 7-73sample reports 7-73Subsystem Activity section 7-73

Pool Mch Faults/Sec column 7-129pool report

printing A-56Pool size (KB) column 7-129Pool User Faults/Sec column 7-129Pools column 7-129pre-defined collection points 11-3PREFIX column 11-24Prg column 7-129Print Activity Report (PRTACTRPT) command 6-9,

A-43Print Component Report (PRTCPTRPT)

command 3-5, 7-25, A-45Print Job Report (PRTJOBRPT) command 7-66, A-48Print Job Trace (PRTJOBTRC) command 10-1, 10-4,

A-51Print Lock Report (PRTLCKRPT) command A-52

considerations 7-63lock conflicts 7-63seize conflicts 7-63viewing trace data 3-5

Print Performance Explorer Report (PRTPEXRPT)command 11-8

Print Performance Explorer Report(PRTPEXRPT) A-53

PRTPEXRPT (Print Performance ExplorerReport) A-53

Print Performance Report display 7-6, 7-12Print Pool Report (PRTPOLRPT) command 7-72, A-56Print Resource Report (PRTRSCRPT) command 7-76,

A-59Print System Report (PRTSYSRPT) command 3-1,

3-5, A-60

Print Trace Report (PRTTRCRPT) command 3-5, A-66Print Transaction Report (PRTTNSRPT)

command 3-5, 7-36, 7-90, A-64printer file 10-11

changing 2-1characteristics 2-1default forms size 2-1QAPTPAGD (input file) 10-16QPPTANKM 10-14, 10-15QPPTANZD

physical-to-logical database file 10-11QPPTANZK 10-13QPPTANZP 10-9QPPTLCK 7-63QPPTPAGD 10-16QPPTTRC1 10-4QPPTTRC2 10-4QPPTTRCD 10-4QPSPDJS 7-37QPSPDTD 7-37QPSPDTS 7-37

Printer Lines column 7-129Printer Pages column 7-129printing

activity report A-43Batch Job Trace Report 7-90Component Report 7-25, A-45Job Interval Report 7-66job report A-48Job Summary Report 7-36job trace 10-1, A-51Lock Report 7-63, A-52performance explorer report 11-8, A-53performance reports

using commands 7-5using defaults 7-11using menus 7-6, 7-11

Pool Interval Report 7-73pool report A-56Resource Interval Report 7-76resource report A-59System Report 7-17, A-60trace report A-66transaction report 3-5, 7-36, 7-90, A-64Transition Report 7-36

Priority column 7-129, 11-14Priority-Jobtype-Pool Statistics

sample report 7-58Priority-Jobtype-Pool Statistics section

Job Summary Report 7-42problem analysis example 13-1procedure column 11-11process

trace event descriptions 11-28process access group (PAG)

analysis 10-16

Index X-23

process access group (PAG) (continued)utilities 10-2

Process Access Group display 10-16Process Access Group Information Report 10-17process data collection command

summary 3-17process data collection report command

summary 3-17process information, analyzing 10-16processing unit

graphical view 7-40processing time 10-5processing unit 6-3trace entry 10-9utilization, Job Summary Report 7-40

processorsummary of usage 7-19

Profile CPU Summary Information Report 11-15Profile Information Report 11-18, 11-20program

analyzing A-8changing 11-3QCRMAIN 10-6QRGXINIT 10-6QWSGET B-3

program brackettrace event descriptions 11-31

Program column 7-129, 11-11, 11-23program environment 3-16Program Name column 7-129Program-to-File Cross-Reference Report 10-10program-to-file relationship report 10-9program-to-file relationships, analyzing 10-9Protocol column 7-130PRTACTRPT (Print Activity Report) command 6-9,

A-43PRTCPTRPT (Print Component Report)

command 3-5, 7-25, A-45PRTJOBRPT (Print Job Report) command 7-66, A-48PRTJOBTRC (Print Job Trace) command 10-1, A-51PRTLCKRPT (Print Lock Report) command A-52

considerations 7-63lock conflicts 7-63seize conflicts 7-63viewing trace data 3-5

PRTPEXRPT (Print Performance Explorer Report)command 11-8

Print Performance Explorer Report(PRTPEXRPT) A-53

PRTPEXRPT (Print Performance ExplorerReport) A-53

PRTPOLRPT (Print Pool Report) command 7-72, A-56PRTRSCRPT (Print Resource Report) command 7-76,

A-59PRTSYSRPT (Print System Report) command 3-1,

3-5, A-60

PRTTNSRPT (Print Transaction Report)command 3-5, 7-36, 7-90, A-64

PRTTRCRPT (Print Trace Report) command 3-5, A-66Pty column 7-130Purge column 7-130PUT (add a record) operation 10-7PUTM (add a record) operation 10-7PWrt column 7-130

QQAITMON database file 6-1, 6-8QAOMJOBS performance monitor file 8-11QAPMAPPN database file 3-4QAPMASYN database file 3-4QAPMBSC database file 3-4QAPMBUS database file 3-4QAPMCIOP database file 3-4QAPMCONF database file 3-4QAPMDBMON database file 3-4QAPMDDI database file 3-4QAPMDIOP database file 3-4QAPMDISK database file 3-4QAPMDMPT database file 3-5, 7-63QAPMECL database file 3-4QAPMETH database file 3-4QAPMFRLY database file 3-4QAPMHDLC database file 3-4QAPMHDWR database file 3-4QAPMIDLC database file 3-4QAPMIOPD database file 3-4QAPMJOBS database file 3-4QAPMLAPD database file 3-4QAPMLIOP database file 3-4QAPMMIOP database file 3-4QAPMPOOL database file 3-4QAPMRESP database file 3-4QAPMRWS database file 3-4QAPMSAP database file 3-4QAPMSBSD subsystem 3-4QAPMSNA database file 3-4, 8-3QAPMSNADS database file 3-4QAPMSTND database file 3-4QAPMSTNE database file 3-4QAPMSTNL database file 3-4QAPMSTNY database file 3-4QAPMSYS database file 3-4QAPMTSK database file 3-4QAPMX25 database file 3-4QAPTAZDR database file 10-13QAPTLCKD database file 7-63QAPTLCKD file 7-101QAPTPAGD database file 10-16, 10-18QAPTTRCJ database file 10-3QAVPETRCI database file 11-8


QBASE subsystem 3-13QCRMAIN program 10-6QCTL subsystem 3-13QDBPUT database module 10-7QGPL library 12-11, 15-5QIBMASYNC graph format 9-2QIBMCMNIOP graph format 9-2QIBMCPUTYP graph format 9-2QIBMCPYPTY graph format 9-2QIBMDSKARM graph format 9-2QIBMDSKIOP graph format 9-2QIBMDSKOCC graph format 9-2QIBMLWSIOP graph format 9-2QIBMMFCIOP graph format 9-2QIBMMFDIOP graph format 9-2QIBMPCTDSK graph format 9-2QIBMPKG graph package 9-3QIBMRSP graph format 9-2QIBMSYNC graph format 9-2QIBMTNS graph format 9-2QIBMTOTDSK graph format 9-2QPFR library 2-1, 2-2QPFRDATA library 3-7, 9-2QPITACTR spooled file 6-9QPPTANKM printer file 10-14, 10-15QPPTANZD

database file 10-11printer file 10-11

QPPTANZK printer file 10-13QPPTANZP printer file 10-9QPPTLCK printer file 7-63QPPTPAGD printer file 10-16QPPTSYSR database file 7-14QPPTTRC1 printer file 10-4QPPTTRC2 printer file 10-4QPPTTRCD printer file 10-4QPSPDJS (Job Summary Report output) 7-37QPSPDTD (Transition Report output) 7-37QPSPDTS (Transaction Report output) 7-37QRGZINIT program 10-6QSYS library 10-6QTRDMPT file 7-96QTRJOBT file 7-91QTRJSUM file 7-94QTRTSUM file 7-91Queue Length column 7-130QWSGET program B-3

RRank column 7-130Ratio of write disk I/O to total disk I/O column 7-130RC Delta column 11-23Reads per Second column 7-130Receive CRC Errors column 7-130

received TDUstopology maintenance 8-13

receiver of search requestssession setup work activity 8-17

receiving performance data 8-10recommendations, understanding 4-8Record Number column 7-130record selection report printer file 10-13reducing intermediate session work load 8-11refresh mode

automatic 6-4registration and deletion

control point presentation services (CPPS) 8-16remote job

displaying performance data 5-12Remote LAN Pct Frames Recd column 7-130Remote LAN Pct Frames Trnsmitd column 7-130Remote Not Ready column 7-131Remote Seq Error column 7-131Remote Work Station Response Times


Remote Work Stationssection description 7-27

Remote Work Stations – Response Time Bucketssample report 7-33

Remove Performance Explorer Definition(RMVPEXDFN) command A-67

removingperformance data E-4performance explorer data A-29performance explorer definition A-67

Rename Object (RNMOBJ) command 2-1renaming

object 2-1report

Analysis of Keys for Database Files 10-16ANZACCGRP Summary Report

environment summary 10-19file summary 10-22job summary 10-20

Batch Job Trace Reportdescription 7-90Job Summary 7-90Job Summary section 7-90

Component ReportReport Selection Criteria 7-28

Database Relation Cross Reference Report 10-12Definition Information 11-9Detail Activity Report 6-12File to Program Cross Reference 10-11Job Interval Report 7-67Job Summary Report

Concurrent Batch Job Statistics section 7-44Individual Transaction Statistics section 7-43Longest Holders of Seize/Lock Conflicts

section 7-44

Index X-25

report (continued)Job Summary Report (continued)

Report Selection Criteria 7-45Key Fields and Select/Omit Listing 10-14Lock Report 7-63Logical File Listing 10-13Pool Interval Report 7-73Print Activity 6-9Process Access Group Information 10-17Profile CPU Summary Information 11-15Profile Information 11-18, 11-20Program-to-File Cross-Reference 10-10Resource Interval Report 7-76Run Information 11-11Statistics CPU Summary Information 11-15Summary Activity 6-10System Report 7-17

Communications Summary 7-19Disk Utilization section 7-19Report Selection Criteria 7-20Resource Utilization 7-19Resource Utilization Expansion 7-19Storage Pool Utilization section 7-19Workload 7-18

Task Information 11-13Trace Analysis I/O Summary Report 10-6Trace Analysis Summary Report 10-5Trace Job Information Report 10-7Transaction Report 7-37transaction response, differences in B-2Transition Report

sample 7-46summary 7-46

report commandAnalyze Access Group (ANZACCGRP) 10-2ANZACCGRP (Analyze Access Group) 10-18ANZDBF (Analyze Database File) 10-11ANZPGM (Analyze Program) 10-2, 10-9Display Access Group (DSPACCGRP) 10-2DSPACCGRP (Display Access Group) 10-16summary 3-13

Report Selection CriteriaComponent Report description 7-28Component Report sample 7-35Job Interval Report 7-68Job Interval sample 7-71Job Summary description 7-45Pool Interval Report 7-73Pool Interval sample 7-75System Report description 7-20System Report sample 7-24

report type (RPTTYPE) parameter 7-36request header (RH) bracket delimiter

session traffic fields 8-7requesting a performance data analysis 4-3

Requestor’s Job Name column 7-131Reset Packets Recd column 7-131Reset Packets Trnsmitd column 7-131Resource Interval Report

Communications Line Detail section 7-77description 7-76Disk Utilization Detail section 7-77Disk Utilization Summary section 7-77IOP Utilizations section 7-78Local Work Station Response Times section 7-79printing 7-76Remote Work Station Response Times

section 7-79sample reports 7-80

resource reportprinting A-59

Resource Utilizationsample report 7-21, 7-22section description 7-19

Resource Utilization Expansionsample report 7-21section description 7-19

resources, systemauxiliary storage 3-1communications 3-1main storage 3-1processing unit 3-1

Response column 7-131Response Sec Avg and Max column 7-131Response Seconds column 7-131response time

components B-1description 1-4host (internal) B-1input communications time B-1internal 1-4

RH (request header) bracket delimitersession traffic fields 8-7

RMVPEXDFN (Remove Performance Explorer Defi-nition) command A-67

RNMOBJ (Rename Object) command 2-1route selection

definition 8-20RPTTYPE (report type) parameter 7-36Rsp column 7-131Rsp Time column 7-131Rsp Timer Ended column 7-131Rsp/Tns column 7-131run cycles column 11-23Run Information Report 11-11run time (us) column 11-23

SS/L column 7-131


SACPNM correlation fielddescription 8-4

sampledata collection 3-5

sample datadefinition 3-3how to collect 3-3SNADS 8-29

sample interval (ms) column 11-11sample report

Batch Job Analysis 7-60Communications IOP Utilizations 7-87Communications Line Detail–ANYNC 7-84Communications Line Detail–BSC 7-85Communications Line Detail–DDI 7-84Communications Line Detail–ELAN 7-83Communications Line Detail–FRLY 7-84Communications Line Detail–IDLC 7-87Communications Line Detail–ISDN 7-85Communications Line Detail–NWI

Maintenance 7-86Communications Line Detail–SDLC 7-81Communications Line Detail–TRLAN 7-82Communications Line Detail–X.25 7-82Communications Summary 7-23Component Interval Activity 7-29Concurrent Batch Job Statistics 7-61Database Journaling Summary 7-34Detail Activity Report 6-12Disk Activity 7-31Disk Utilization 7-22Disk Utilization Detail 7-80Disk Utilization Summary 7-80Distribution of Processing Unit Transactions 7-52Exception Occurrence Summary and Interval

Counts 7-34Individual Transaction Statistics 7-59Interactive CPU Utilization by 5-Minute

Intervals 7-55Interactive Job Detail section 7-69Interactive Job Summary 7-68Interactive Program Statistics 7-56, 7-59Interactive Response Time by 5-Minute

Intervals 7-55Interactive Throughput by 5-Minute Intervals 7-54Interactive Transactions by 5-Minute Intervals 7-54,

7-55Interactive Workload 7-20IOP (input/output processor) Utilizations 7-32Job Statistics 7-58Job Summary 7-49Job Summary Report: Report Selection

Criteria 7-61Job Summary—Batch Job Trace Report 7-90Job Workload Activity 7-29Local Work Station Reponse Times 7-88

sample report (continued)Local Work Stations – Response Time

Buckets 7-33Lock Report – Summary 7-66Lock Report–Detail 7-66Longest Holders of Seize/Lock Conflicts 7-60Longest Seize/Lock Conflicts 7-59Noninteractive Job Detail 7-70Noninteractive Job Summary 7-69Noninteractive Workload 7-21performance explorer

Definition Information 11-9Profile CPU Summary Information 11-15Profile Information 11-18, 11-20Run Information 11-11Statistics CPU Summary Information

Report 11-15Task Information Report 11-13Trace Information 11-21

Pool Activity 7-74Priority-Jobtype-Pool Statistics 7-58Remote Work Station Response Times 7-89Remote Work Stations – Response Time

Buckets 7-33Report Selection Criteria—Component Report 7-35Report Selection Criteria–Job Interval 7-71Report Selection Criteria–Job Summary

Report 7-61Report Selection Criteria–Pool Interval 7-75Report Selection Criteria–System Report 7-24Resource Utilization 7-21Resource Utilization Expansion 7-21Storage Pool Activity 7-31Storage Pool Utilization 7-22Subsystem Activity 7-74Summary Activity Report 6-10Summary of Seize/Lock Conflicts by Object 7-57System Summary Data 7-51, 7-52Transaction Report 7-62Transaction Significance 7-53Transition Report 7-62

SANWID correlation fielddescription 8-4

SAPPN correlation fielddescription 8-4

save system (*SAVSYS) authority 2-1Scatter Diagram section 7-41scatter plot 9-5scenario, performance analysis 13-1SCTLNM correlation field

description 8-4SCTYP correlation field

description 8-4search processing

session setup work activity 8-17

Index X-27

sector column 11-24Seg T ST column 11-24segment address register

trace event descriptions 11-28Seize and Lock Conflicts column 7-131Seize Conflict column 7-131Seize Hold Time column 7-132seize lock

trace event descriptions 11-28Seize Wait /Tns column 7-132seize/lock

analyzing conflicts 7-64conflicts by object 7-41longest conflicts 7-43longest holders of conflicts 7-44

Seize/Lock Conflicts by Object 7-41seize/lock data file 7-101Select Categories for Performance Graphs

display 9-18Select Categories for Report display 7-8Select File and Access Group Utilities display 10-2Select Graph Format display 9-21Select or Omit Pools display 7-9SELECT parameter

Component Report 7-28Component Report sample 7-35Job Summary Report 7-45System Report 7-20System Report sample 7-24

Select Parameters column 7-132Select Performance Data Member display 9-17Select Performance Member display 5-1, 12-7, 15-2Select Sections for Report display 7-7Select Time Intervals display 7-8Select Time Intervals to Analyze display 4-4Select Time Intervals to Display display 5-2Select Type of Status display 2-3selected jobs column 11-10selected MI complex instructions column 11-10selected programs column 11-11selected task names column 11-10selecting

a member 4-4performance data members 9-17time intervals 4-4

sending datainternal session-level pacing 8-7line transmission 8-10session-level pacing 8-7transmission priority 8-7

SEQ (sequence) parameter 6-12sequence (SEQ) parameter 6-12Sequence Error column 7-132serial number column 11-13session name column 11-12

session setup activitiesAPPN (advanced peer-to-peer networking) 8-16bind command 8-16broadcast search 8-16directed search 8-16domain broadcast 8-17NNS(DLU) network node 8-17NNS(OLU) network node 8-17session setup activities 8-17

session setup work activityAPPN (advanced peer-to-peer networking) 8-17broadcast search received 8-18destination network node 8-18device selection 8-20directory search processing 8-20initial screening 8-20intermediate node on directed search 8-18locally started sessions (source) 8-17network node processing 8-18receiver of search requests 8-17route selection 8-20search processing 8-17switched link activation 8-20

session traffic fieldsdescription 8-6number of sessions started and ended 8-7SNA performance measurements 8-6

session-level pacingdescription 8-7excessive waiting 8-9

sessions since IPL column 11-12Set Data Collection Time display 3-8Set End Time display 3-9Set Length of Time to Collect Data display 3-9setting

data collection time 3-8Short Frame Errors column 7-132Short Wait /Tns column 7-132Short WaitX /Tns (Short wait extended) column 7-132single-processor system

field restrictions 6-3Size (K) column 7-132Size (M) column 7-132Size column 7-132SKP XCH column 11-24SLINNM correlation field

description 8-4SLIOMT correlation field

description 8-4SLTCTL (control units included) parameter 7-108SLTFCNARA (functional areas included)

parameter 7-115SLTJOB (jobs included) parameter 7-120SLTLINE (communications lines included)

parameter 7-108


SLTSBS (subsystems included) parameter 7-134SLTUSRID (users included) parameter 7-141SLTxxx (select) parameter 7-132SMAPP ReTune column 7-132SNA performance measurements

APPC controller description 8-3comparing different traffic priority levels 8-11connection fields 8-4correlation fields 8-4device description fields 8-5host controller description 8-3QAPMSNA database file 8-3session traffic fields 8-6T2 station I/O manager task fields 8-5

SNA performance measurements datadatabase file 3-4

SNACVO device description fielddescription 8-5

SNADD device description fielddescription 8-5

SNADSperformance measurement 8-23performance notes 8-32sample data 8-29

SNADS transactiongateway senders 8-28SNADS receiver 8-25SNADS router 8-24SNADS sender 8-25SVDS receiver 8-26SVDS sender 8-27

SNLBU connection fielddescription 8-5

SNWAIN T2 station I/O manager task fielddescription 8-5

SNWAOU T2 station I/O manager task fielddescription 8-5

software license keys 2-1SOTn column 7-132source code

mapping with statements 11-35span column 11-24Specify Graph Options display 9-18Specify Graph Overlay Options display 9-22Specify Report Options display 7-10, 7-13Spool CPU seconds per I/O column 7-133Spool database reads per second column 7-133Spool I/O per second column 7-133spooled file

QPITACTR 6-9Srv Time column 7-133ss.mmm column 11-23SSPTRC (trace suspended) 10-8STACVO device description field

description 8-5

start addr column 11-18Start BEST/1 (STRBEST) command A-2Start Collecting Data display 3-6, 7-11Start column 7-133start database monitor (STRDBMON) parameter 3-4Start Job Trace (STRJOBTRC) command 10-1, 10-3,

A-68Start Performance Explorer (STRPEX) command 11-7,

A-69Start Performance Graphics (STRPFRG)

command 9-2, A-70Start Performance Monitor (STRPFRMON)

command 3-1, 5-1Start Performance Tools (STRPFRT) command 2-2,

A-70Start Service Job (STRSRVJOB) command 10-3start time column 11-12started by user column 11-13Started column 7-133starting

advisor 4-3job trace 10-1, 10-3, A-68performance explorer 11-7, A-69performance graphics 9-2, A-70performance monitor 3-1, 5-1Performance Tools 2-1, 2-2, A-70

State column 7-133State Transitions A-A column 7-133State Transitions A-I column 7-133Statistics CPU Summary Information Report 11-15STLLBU connection field

description 8-5stmt numb column 11-18Stop column 7-133stop time column 11-12Stopped column 7-133stopping

job trace 10-1storage device controller database file 3-4storage pool

displaying 5-8displaying performance data 5-9setting size 7-19

Storage Pool Activitysample report 7-31section description 7-26

Storage Pool Utilizationsample report 7-22section description 7-19

STRBEST (Start BEST/1) command A-2STRDBMON (start database monitor) parameter 3-4STRJOBTRC (Start Job Trace) command 10-3, A-68STRPEX (Start Performance Explorer) command 11-7,

A-69STRPFRG (Start Performance Graphics)

command 9-2, A-70

Index X-29

STRPFRMON (Start Performance Monitor)command 3-1, 5-1

STRPFRT (Start Performance Tools) command 2-2,A-70

STRSRVJOB (Start Service Job) command 10-3STSKNM correlation field

description 8-4submitted job

working with 2-3subsystem

database file, QAPMSBSD 3-4QBASE 3-13QCTL 3-13working with 2-3

Subsystem Activitysample report 7-74section description 7-73

Subsystem Name column 7-133Subsystems column 7-134Sum column 7-134Summary Activity Report 6-10Summary of Seize/Lock Conflicts by Object


surface graph 9-5suspend time (us) column 11-12SVDS receiver 8-26SVDS sender 8-27switched link activation

definition 8-20SWX column 7-134Sync column 7-134Sync DIO /Tns column 7-134Sync Disk I/O column 7-134Sync Disk I/O per Second column 7-134Sync Disk I/O Requests column 7-134Sync Disk I/O Rqs/Tns column 7-134Sync I/O /Elp Sec column 7-134Sync I/O /Sec column 7-134Sync I/O Per Second column 7-134Synchronous DBR column 7-135Synchronous DBW column 7-135Synchronous DIO / Act Sec column 7-135Synchronous DIO / Ded Sec column 7-135Synchronous DIO / Elp Sec column 7-135Synchronous disk I/O

definition 7-42Synchronous Disk I/O Counts column 7-135Synchronous disk I/O per transaction column 7-135Synchronous Max column 7-135Synchronous NDBR column 7-136Synchronous NDBW column 7-136Synchronous Sum column 7-136Synchronous wrt column 7-136system

activity 6-1

system (continued)analysis 13-1configuration database file 3-4database file 3-4performance parameters C-1two processors

example display 7-138system activity

working with 6-1, A-72System Activity menu 6-1System CPU per transaction (seconds) column 7-136system data collection command

summary 3-13system default

collecting data 3-7System disk I/O per transaction column 7-136system model column 11-13System Report

Communications Summary section 7-19description 7-17Disk Utilization section 7-19printing 3-1, 7-17, A-60Report Selection Criteria section 7-20Resource Utilization Expansion section 7-19Resource Utilization section 7-19sample reports 7-20Storage Pool Utilization section 7-19Workload section 7-18

system resource utilizationBEST/1 1-6

system resourcesauxiliary storage 3-1communications 3-1displaying performance data 5-8main storage 3-1processing unit 3-1

System Starts column 7-136System Stops column 7-136System Summary Data

interactive key/think time, analysis by 7-39interactive response time, analysis by 7-39interactive transaction averages by job type 7-39interactive transaction categories, analysis by 7-39section description 7-39trace periods for trace data 7-39

System Summary Data sectionexceptional wait breakdown by job type 7-39

System Total column 7-136System ToUser column 7-136system type column 11-13system use analysis 3-2system with two processors

definition 6-3example display 6-3utilization value 6-12


system-levelanalysis 3-13data collection 3-13

System/36 performance parametersAS/400 correlation C-1

SZRL column 7-136SZWT column 7-136

TT2 station I/O manager (IOM) task fields


target system column 11-13task CPU column 11-15task ID column 11-14, 11-23Task Information Report 11-13Thread column 7-136thread data

converting 15-6threads

definition 7-136threshold valve

multifunction IOP (input/output processor) 7-26Time column 7-137time intervals

selecting 4-4time stamp column 11-22times called column 11-16tips, tuning F-4Tns column 7-137Tns Count column 7-137Tns/Hour column 7-137Tns/Hour Rate column 7-137TOD of Wait column 7-137token-ring local area network database file 3-4topology database update

control point presentation services (CPPS) 8-15topology maintenance 8-12

topology maintenanceAPPN (advanced peer-to-peer networking) 8-12Display APPN Information (DSPAPPNINF)

command 8-13initial topology exchange 8-13node congestion updates 8-12obsolete topology entry removal 8-13received TDUs 8-13topology database update (TDU) 8-12transmission group (TG) update 8-12

Tot column 7-137Tot Nbr Tns column 7-137Total /Job column 7-137Total characters per transaction column 7-137Total column 7-137total CPU column 11-15, 11-16

Total CPU Sec /Sync DIO column 7-137Total CPU Utilization column 7-138Total Data Characters Received column 7-138Total Data Characters Transmitted column 7-138Total fields per transaction column 7-138Total Frames Recd column 7-138total hits column 11-15Total I Frames Trnsmitd column 7-138Total I/O column 7-138total pages memory column 11-13Total PDUs Received column 7-138Total Physical I/O per Second column 7-138total processing unit (TCPU) seconds

Job Summary Report 7-42total raw CPU column 11-16Total Responses column 7-138total samples column 11-15Total Seize/Wait Time column 7-138total time column 11-12Total Tns column 7-138tpIPNW internal session-level pacing field

description 8-9tpIPWT internal session-level pacing field

description 8-9tpLRUD line transmission field

description 8-10tpLRUR receiving data field

description 8-10tpNBB field

number of brackets started 8-7tpNEB field

number of brackets ended 8-7tpNRUD line transmission field

description 8-10tpNRUR receiving data field

description 8-10tpNSE field

number of sessions ended 8-7tpNSS field

number of sessions started 8-7tpQLRL transmission priority field

description 8-9tpQNRE transmission priority field

description 8-9tpQNRL transmission priority field

description 8-9tpQRRR transmission priority field

description 8-9tpSPNW session-level pacing field

description 8-8tpSPPW session-level pacing field

description 8-8tpSPST session-level pacing field

description 8-8tpSPWS session-level pacing field

description 8-8

Index X-31

tpSPWT session-level pacing fielddescription 8-7

tpTRUD line transmission fielddescription 8-10

trace analysis I/O summary 10-4Trace Analysis I/O Summary Report 10-6Trace Analysis Summary Report 10-5trace data

analyzing 4-7collecting 7-37, 7-63collection 3-2creating 7-37, 7-63database file 3-5definition 3-5how to collect

DMPTRC parameter 3-10TRACE parameter 3-10

storage restrictions 3-2trace event

descriptionauxiliary storage management 11-26BASE 11-24DASD server 11-31disk 11-26Java 11-32job 11-28MI complex instructions 11-34page fault 11-27process 11-28program bracket 11-31segment address register 11-28seize lock 11-28

Trace Job (TRCJOB) command 10-4trace job information 10-4Trace Job Information Report 10-7trace options

call (external) 10-8data (trace) 10-8event (handler) 10-8EXTXHINV (external exception handler) 10-8EXTXHRET (call termination) 10-8INTXHINV (internal exception handler) 10-8INTXHRET (return from an exception) 10-8INVEXIT (call exit routine) 10-8ITERM (intervening call termination) 10-8ITRMXRSG (resignaling exception) 10-8PTRMTPP (process termination) 10-8PTRMUNHX (unhandled exception) 10-8SSPTRC (trace suspended) 10-8

trace periods for trace data 7-39trace report

printing 3-5, A-66trace wrap count column 11-12tracing

job 10-4

traffic priority levelscomparing 8-11

transactionboundaries 8-1, 10-4, B-1Client Access shared folders 8-33conditions for number of 7-123OS/400 file server 8-33performance 10-2response reports B-2

Transaction Report*DI value 8-1*DQ value 8-1boundary values 7-39description 7-37Job Summary Data section 7-46output (QPSPDTS) 7-37printing 7-36, 7-90, A-64RPTTYPE (*TNSACT) option 7-37, 7-45sample report 7-49, 7-62

Transaction Response Time (Sec/Tns) column 7-138Transaction Significance


Transactions per hour (local) column 7-138Transactions per hour (remote) column 7-139Transition Report

description 7-46output (QPSPDTD) 7-37printing 7-36RPTTYPE (*TRSIT) option 7-37sample 7-46sample report 7-62summary 7-46

transmission group (TG) updatetopology maintenance 8-12

transmission prioritydescription 8-9user-defined transmission priority 8-9

transmission time B-1Transmit/Receive/Average Line Util column 7-139TRCJOB (Trace Job) command 10-4TSE column 7-139tuning

checklist F-1, F-2tips F-4

tuning systemadvisor recommendations 4-14

Typ column 7-139Type column 7-140, 11-10, 11-11

UUADA (user area disk activity) C-1UDR (update, delete, or release record) 10-7Unit column 7-141, 11-24


Unit Name column 7-141unknown CPU column 11-16update, delete, or release record (UDR) 10-7use analysis, system 3-2user area disk activity (UADA) C-1user column 11-10User ID column 7-141User Name column 7-141User Name/Thread column 7-141User Starts column 7-141User Stops column 7-141User Total column 7-141user-based pricing 2-1using the advisor's results 4-7Util 2 column 7-141Util column 7-141utilities, process access group (PAG) 10-2

Vvalid x-axis and y-axis values 9-7Value column 7-142Verify column 7-142version column 11-13

WW-I Wait/Tns column 7-142Wait Code column 7-142wait states

description 7-133Wait-Inel column 7-143work management functions

accessing 6-8Work Station Controller column 7-143Work with Active Jobs (WRKACTJOB) command

system values option 2-3Work with All Spooled Files display 7-14Work with Disk Status (WRKDSKSTS) command 2-3Work with Functional Areas (WRKFCNARA)

command A-71Work with Graph Formats and Packages display 9-3Work with Historical Data display 9-13, 14-1Work with Job (WRKJOB) command 2-3, 6-6Work with Job Traces display 10-1Work with Performance Collection (WRKPFRCOL)

command 3-12, 9-16, E-1Work with Performance Collection display 3-12Work with Spooled Files (WRKSPLF) command 7-14Work with Submitted Jobs (WRKSBMJOB)

command 2-3, 7-13Work with Subsystems (WRKSBS) command 2-3Work with System Activity (WRKSYSACT)

command A-72description 6-1

Work with System Activity display 6-2Work with System Status (WRKSYSSTS)

command 2-3Working set size (KB) column 7-143working with

disk status 2-3functional areas A-71jobs 6-6submitted jobs 2-3subsystems 2-3system activity A-72

Workloadsample report 7-20section description 7-18

Writes per Second column 7-144WRKACTJOB (Work with Active Jobs) command

system values option 2-3WRKDSKSTS (Work with Disk Status) command 2-3WRKFCNARA (Work with Functional Areas)

command A-71WRKJOB (Work with Job) command 2-3, 6-6WRKPFRCOL (Work with Performance Collection)

command 3-12, 9-16, E-1WRKSBMJOB (Work with Submitted Jobs)

command 2-3, 7-13WRKSBS (Work with Subsystems) command 2-3WRKSPLF (Work with Spooled Files) command 7-14WRKSYSACT (Work with System Activity)

command A-72description 6-1

WRKSYSSTS (Work with System Status)command 2-3

WSC (local work station controller) 3-4WTO column 7-144

XX.25 database file 3-4

Index X-33

Communicating Your Comments to IBM

AS/400e seriesPerformance Tools for AS/400Version 4

Publication No. SC41-5340-00

If you especially like or dislike anything about this book, please use one of the methodslisted below to send your comments to IBM. Whichever method you choose, make sure yousend your name, address, and telephone number if you would like a reply.

Feel free to comment on specific errors or omissions, accuracy, organization, subject matter,or completeness of this book. However, the comments you send should pertain to only theinformation in this manual and the way in which the information is presented. To requestadditional publications, or to ask questions or make comments about the functions of IBMproducts or systems, you should talk to your IBM representative or to your IBM authorizedremarketer.

When you send comments to IBM, you grant IBM a nonexclusive right to use or distributeyour comments in any way it believes appropriate without incurring any obligation to you.

If you are mailing a readers' comment form (RCF) from a country other than the UnitedStates, you can give the RCF to the local IBM branch office or IBM representative forpostage-paid mailing.

� If you prefer to send comments by mail, use the RCF at the back of this book.

� If you prefer to send comments by FAX, use this number:

– United States and Canada: 1-800-937-3430– Other countries: 1-507-253-5192

� If you prefer to send comments electronically, use this network ID:

– IBMMAIL(USIB56RZ) – [email protected]

Make sure to include the following in your note:

� Title and publication number of this book� Page number or topic to which your comment applies.

Readers' Comments — We'd Like to Hear from You

AS/400e seriesPerformance Tools for AS/400Version 4

Publication No. SC41-5340-00

Overall, how satisfied are you with the information in this book?

How satisfied are you that the information in this book is:

Please tell us how we can improve this book:

Thank you for your responses. May we contact you? Ø Yes Ø No

When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your commentsin any way it believes appropriate without incurring any obligation to you.

Name Address

Company or Organization

Phone No.

Very

Satisfied Satisfied Neutral DissatisfiedVery

Dissatisfied

Overall satisfaction Ø Ø Ø Ø Ø

Very

Satisfied Satisfied Neutral DissatisfiedVery

Dissatisfied

Accurate Ø Ø Ø Ø ØComplete Ø Ø Ø Ø ØEasy to find Ø Ø Ø Ø ØEasy to understand Ø Ø Ø Ø ØWell organized Ø Ø Ø Ø ØApplicable to your tasks Ø Ø Ø Ø Ø

Cut or FoldAlong Line

Cut or FoldAlong Line

Readers' Comments — We'd Like to Hear from YouSC41-5340-00 IBM

Fold and Tape Please do not staple Fold and Tape

NO POSTAGENECESSARYIF MAILED IN THEUNITED STATES

BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO. 40 ARMONK, NEW YORK

POSTAGE WILL BE PAID BY ADDRESSEE

IBM CORPORATIONATTN DEPT 542 IDCLERK3605 HWY 52 NROCHESTER MN 55901-7829

Fold and Tape Please do not staple Fold and Tape

SC41-5340-00

IBM

Printed in the United States of Americaon recycled paper containing 10%recovered post-consumer fiber.

SC41-534ð-ðð

Spine information:

IBM AS/400e series Performance Tools for AS/400 Version 4

Documents

AS400 Server Performance Tools