AS/400e series IBM

Performance Tools for AS/400

Version 4

SC41-5340-00
AS/400e series IBM
Performance Tools for AS/400
Version 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 to
restrictions set forth in GSA ADP Schedule Contract with IBM Corp.
 Contents
Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Programming Interface Information . . . . . . . . . . . . . . . . . . . . . . . . . xiv
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

About Performance Tools (SC41-5340) . . . . . . . . . . . . . . . . . . . . . . xvii

Who should read this book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii
AS/400 Operations Navigator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii
Prerequisite 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-1

Installing Performance Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
How Performance Tools Counts Users . . . . . . . . . . . . . . . . . . . . . . . 2-1
Printer File and Output Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Start Performance Tools (STRPFRT) Command . . . . . . . . . . . . . . . . . . 2-2
Displaying 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-1
When to End Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Collecting Sample or Trace Data . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Using System Defaults to Collect Data . . . . . . . . . . . . . . . . . . . . . . 3-7
Using Menus to Collect Data . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Using the STRPFRMON Command to Collect Trace Data . . . . . . . . . 3-10
Collecting Performance Data Automatically . . . . . . . . . . . . . . . . . . . . 3-11
Performance Collection Setup . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
Summary of Data Collection and Report Commands—Manager Feature . . . 3-13
System-Level Analysis—Manager Feature . . . . . . . . . . . . . . . . . . . 3-13
Job Trace Analysis—Manager Feature . . . . . . . . . . . . . . . . . . . . . 3-15
File Use and Database Structure Analysis—Manager Feature . . . . . . . 3-16

 Copyright IBM Corp. 1998 iii

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

Chapter 4. Advisor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Collecting the Right Performance Data . . . . . . . . . . . . . . . . . . . . . . . 4-2
Requesting an Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Selecting a Member . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Selecting Time Intervals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Using a Histogram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Analyzing Trace Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
Using the Advisor’s Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
Understanding Recommendations . . . . . . . . . . . . . . . . . . . . . . . . 4-8
Changing System Tuning Values . . . . . . . . . . . . . . . . . . . . . . . . 4-10
Understanding Conclusions . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
Understanding Interval Conclusions . . . . . . . . . . . . . . . . . . . . . . 4-12
Tune System by Advisor’s Recommendations . . . . . . . . . . . . . . . . . . 4-14

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

Display Performance Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Display Performance Data by Subsystem . . . . . . . . . . . . . . . . . . . . 5-4
Display Performance Data by Job Type . . . . . . . . . . . . . . . . . . . . . 5-4
Display Performance Data by Interval . . . . . . . . . . . . . . . . . . . . . . 5-5
Display Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
Display Job Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
Display Performance Data for System Resources . . . . . . . . . . . . . . . . . 5-8
Display Pool Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Display Pool Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
Display Disk Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
Display Disk Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
Display Communications Line Detail . . . . . . . . . . . . . . . . . . . . . . 5-11
Display Remote Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
Display Communications Interval Data . . . . . . . . . . . . . . . . . . . . . 5-13
Display Remote Interval Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
Display Network Interface Data . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
Display Channel Interval Data . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
Display Maintenance Channel Data . . . . . . . . . . . . . . . . . . . . . . . 5-18

Chapter 6. System Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Work with System Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Single-Processor System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Multiple-Processor System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Automatic Refresh Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
Monitoring Specific Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Working with Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
Displaying Different Information Types . . . . . . . . . . . . . . . . . . . . . . 6-7
Accessing Work Management Functions . . . . . . . . . . . . . . . . . . . . . 6-8
Content of Database File QAITMON . . . . . . . . . . . . . . . . . . . . . . . 6-8
Print Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9
Summary Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
Detail Activity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12

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

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

iv Performance Tools V4R2

Which Report Do I Want? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Printing Performance Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Using Menus to Print Performance Reports . . . . . . . . . . . . . . . . . . . 7-6
Using Defaults to Print Performance Reports . . . . . . . . . . . . . . . . . 7-11
Why Performance Reports May Seem Inconsistent . . . . . . . . . . . . . 7-15
System Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17
Printing the System Report . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17
What Is the System Report? . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17
Workload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-18
Resource Utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-19
Resource Utilization Expansion . . . . . . . . . . . . . . . . . . . . . . . . . 7-19
Storage Pool Utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-19
Disk Utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-19
Communications Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-19
Report Selection Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-20
Sample System Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-20
Workload Section: Interactive Workload–Sample . . . . . . . . . . . . . . 7-20
Workload Section: Noninteractive Workload–Sample . . . . . . . . . . . . 7-21
Resource Utilization (First Part)–Sample . . . . . . . . . . . . . . . . . . . . 7-21
Resource Utilization (Second Part)–Sample . . . . . . . . . . . . . . . . . . 7-21
Resource Utilization Expansion (First Part)–Sample . . . . . . . . . . . . . 7-21
Resource Utilization Expansion (Second Part)–Sample . . . . . . . . . . . 7-22
Storage Pool Utilization–Sample . . . . . . . . . . . . . . . . . . . . . . . . 7-22
Disk Utilization–Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-22
Communications Summary–Sample . . . . . . . . . . . . . . . . . . . . . . 7-23
System Report Selection Criteria: Select Parameters–Sample . . . . . . . 7-24
System Report Selection Criteria: Omit Parameters–Sample . . . . . . . . 7-24
Report Selection Criteria: Selected Start/End Time/Date–Sample . . . . . 7-25
Report Selection Criteria: Date/Time Intervals–Sample . . . . . . . . . . . 7-25
Component Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-25
Printing the Component Report . . . . . . . . . . . . . . . . . . . . . . . . . 7-25
What Is the Component Report? . . . . . . . . . . . . . . . . . . . . . . . . 7-25
Component Interval Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-25
Job Workload Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-26
Storage Pool Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-26
Disk Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-26
Input/Output Processor (IOP) Utilizations . . . . . . . . . . . . . . . . . . . 7-26
Local Work Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-26
Remote Work Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-27
Exception Occurrence Summary and Interval Counts . . . . . . . . . . . . 7-27
Database Journaling Summary . . . . . . . . . . . . . . . . . . . . . . . . . 7-27
Report Selection Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-28
Sample Component Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-29
Component Interval Activity–Sample . . . . . . . . . . . . . . . . . . . . . . 7-29
Job Workload Activity–Sample . . . . . . . . . . . . . . . . . . . . . . . . . 7-29
Storage Pool Activity–Sample . . . . . . . . . . . . . . . . . . . . . . . . . . 7-31
Disk Activity–Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-31
IOP Utilizations–Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-32
Local Work Stations–Response Time Buckets–Sample . . . . . . . . . . . 7-33
Remote Work Stations–Response Time Buckets–Sample . . . . . . . . . . 7-33
Exception Occurrence Summary and Interval Counts–Sample . . . . . . . 7-34
Database Journaling Summary–Sample . . . . . . . . . . . . . . . . . . . . 7-34
Component Report Selection Criteria: Select Parameters–Sample . . . . 7-35
Component Report Selection Criteria: Omit Parameters–Sample . . . . . 7-36

Contents v
 Transaction Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-36
Printing the Transaction Report . . . . . . . . . . . . . . . . . . . . . . . . . 7-36
What Is the Transaction Report? . . . . . . . . . . . . . . . . . . . . . . . . 7-37
Job Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-38
Interactive Throughput Section . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-40
Interactive CPU Utilization Section . . . . . . . . . . . . . . . . . . . . . . . . . 7-40
Interactive Response Time Section . . . . . . . . . . . . . . . . . . . . . . . . 7-40
Scatter Diagram Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-41
Interactive Program Transaction Statistics Section . . . . . . . . . . . . . . . 7-41
Seize/Lock Conflicts by Object Section . . . . . . . . . . . . . . . . . . . . . . 7-41
Special System Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-41
To Print . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-41
Priority-Jobtype-Pool Statistics Section . . . . . . . . . . . . . . . . . . . . . 7-42
Job Statistics Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-42
Interactive Program Statistics Section . . . . . . . . . . . . . . . . . . . . . 7-42
Individual Transaction Statistics Section . . . . . . . . . . . . . . . . . . . . 7-43
Longest Seize/Lock Conflicts Section . . . . . . . . . . . . . . . . . . . . . 7-43
Longest Holders of Seize/Lock Conflicts Section . . . . . . . . . . . . . . . 7-44
Batch Job Analysis Section . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-44
Concurrent Batch Job Statistics . . . . . . . . . . . . . . . . . . . . . . . . . 7-44
Report Selection Criteria Section . . . . . . . . . . . . . . . . . . . . . . . . 7-45
Transaction Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-45
To Print . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-45
Job Summary Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-46
Transition Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-46
To Print . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-46
Transition Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-46
Sample Transaction Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-49
Job Summary–Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-49
System Summary Data (First Part)–Sample . . . . . . . . . . . . . . . . . . 7-50
System Summary Data (Second Part)–Sample . . . . . . . . . . . . . . . . 7-51
System Summary Data (Third Part)–Sample . . . . . . . . . . . . . . . . . 7-52
Distribution of Simple, Medium, and Complex Processing Unit
Transactions–Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-52
Transaction Significance–Sample . . . . . . . . . . . . . . . . . . . . . . . . 7-53
Interactive Transactions by 5-Minute Intervals–Sample . . . . . . . . . . . 7-54
Interactive Throughput by 5-Minute Intervals–Sample . . . . . . . . . . . . 7-54
Interactive CPU Utilization by 5-Minute Intervals–Sample . . . . . . . . . . 7-55
Interactive Response Time by 5-Minute Intervals–Sample . . . . . . . . . 7-55
Scatter Diagram of Interactive Transactions by 5-Minute Intervals–Sample 7-55
Interactive Program Statistics–Sample . . . . . . . . . . . . . . . . . . . . . 7-56
Summary of Seize/Lock Conflicts by Object–Sample . . . . . . . . . . . . . 7-57
Priority-Jobtype-Pool Statistics–Sample . . . . . . . . . . . . . . . . . . . . 7-58
Job Statistics–Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-58
Interactive Program Statistics–Sample . . . . . . . . . . . . . . . . . . . . . 7-59
Individual Transaction Statistics–Sample . . . . . . . . . . . . . . . . . . . . 7-59
Longest Seize/Lock Conflicts–Sample . . . . . . . . . . . . . . . . . . . . . 7-59
Longest Holders of Seize/Lock Conflicts–Sample . . . . . . . . . . . . . . . 7-60
Batch Job Analysis–Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-60
| Concurrent Batch Job Statistics–Sample . . . . . . . . . . . . . . . . . . . . 7-61
Report Selection Criteria-Sample . . . . . . . . . . . . . . . . . . . . . . . . 7-61
Transaction Report Option–Sample . . . . . . . . . . . . . . . . . . . . . . . 7-62
Transition Report Option–Sample . . . . . . . . . . . . . . . . . . . . . . . . 7-62
Lock Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-63

vi Performance Tools V4R2

 Printing the Lock Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-63
What Is the Lock Report? . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-64
Analyzing Seize/Lock Conflicts . . . . . . . . . . . . . . . . . . . . . . . . . 7-64
| Thread Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-65
Sample Lock Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-65
Lock Report–Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-66
Lock Report–Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-66
Job Interval Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-66
Printing the Job Interval Report . . . . . . . . . . . . . . . . . . . . . . . . . 7-66
What Is the Job Interval Report? . . . . . . . . . . . . . . . . . . . . . . . . 7-67
Interactive Job Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-67
Noninteractive Job Summary . . . . . . . . . . . . . . . . . . . . . . . . . . 7-67
Interactive Job Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-67
Noninteractive Job Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-68
Report Selection Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-68
Sample Job Interval Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-68
Interactive Job Summary–Sample . . . . . . . . . . . . . . . . . . . . . . . 7-68
Noninteractive Job Summary–Sample . . . . . . . . . . . . . . . . . . . . . 7-69
Interactive Job Detail–Sample . . . . . . . . . . . . . . . . . . . . . . . . . . 7-69
Noninteractive Job Detail –Sample . . . . . . . . . . . . . . . . . . . . . . . 7-70
Job Interval Report Selection Criteria: Select Parameters–Sample . . . . . 7-71
Job Interval Report Selection Criteria: Omit Parameters–Sample . . . . . 7-72
Pool Interval Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-72
Printing the Pool Interval Report . . . . . . . . . . . . . . . . . . . . . . . . 7-73
What Is the Pool Interval Report? . . . . . . . . . . . . . . . . . . . . . . . . 7-73
Subsystem Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-73
Pool Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-73
Report Selection Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-73
Sample Pool Interval Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-73
Subsystem Activity–Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-74
Pool Activity–Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-74
Report Selection Criteria–Sample . . . . . . . . . . . . . . . . . . . . . . . . 7-75
Resource Interval Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-76
Printing the Resource Interval Report . . . . . . . . . . . . . . . . . . . . . 7-76
What Is the Resource Interval Report? . . . . . . . . . . . . . . . . . . . . . 7-76
Disk Utilization Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-77
Disk Utilization Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-77
Communications Line Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-77
IOP Utilizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-78
Local Work Station Response Times . . . . . . . . . . . . . . . . . . . . . . 7-79
Remote Work Station Response Times . . . . . . . . . . . . . . . . . . . . 7-79
Sample Resource Interval Reports . . . . . . . . . . . . . . . . . . . . . . . . . 7-80
Disk Utilization Summary–Sample . . . . . . . . . . . . . . . . . . . . . . . 7-80
Disk Utilization Detail–Sample . . . . . . . . . . . . . . . . . . . . . . . . . . 7-80
Communications Line Detail–SDLC Sample . . . . . . . . . . . . . . . . . . 7-81
Communications Line Detail–X.25 Sample . . . . . . . . . . . . . . . . . . 7-82
Communications Line Detail–TRLAN Sample . . . . . . . . . . . . . . . . . 7-82
Communications Line Detail–ELAN Sample . . . . . . . . . . . . . . . . . . 7-83
Communications Line Detail–DDI Sample . . . . . . . . . . . . . . . . . . . 7-84
Communications Line Detail–FRLY Sample . . . . . . . . . . . . . . . . . . 7-84
Communications Line Detail–ASYNC Sample . . . . . . . . . . . . . . . . . 7-84
Communications Line Detail–BSC Sample . . . . . . . . . . . . . . . . . . 7-85
Communications Line Detail–ISDN Network Interface Sample . . . . . . . 7-85
Communications Line Detail–NWI Maintenance Sample . . . . . . . . . . . 7-86

Contents vii
 Communications Line Detail–IDLC Samples . . . . . . . . . . . . . . . . . . 7-87
IOP Utilizations–Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-87
Local Work Station Response Times–Sample . . . . . . . . . . . . . . . . . 7-88
Remote Work Station Response Times–Sample . . . . . . . . . . . . . . . 7-89
Batch Job Trace Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-89
Printing the Batch Job Trace Report . . . . . . . . . . . . . . . . . . . . . . 7-90
What Is the Batch Job Trace Report? . . . . . . . . . . . . . . . . . . . . . 7-90
Job Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-90
Job Summary Report–Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-90
Performance Trace Database Files . . . . . . . . . . . . . . . . . . . . . . . . 7-90
QTRTSUM and QTRJOBT Files . . . . . . . . . . . . . . . . . . . . . . . . 7-91
QTRJSUM File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-94
QTRDMPT File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-96
QAPTLCKD File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-101
Performance Report Columns . . . . . . . . . . . . . . . . . . . . . . . . . . 7-102

Chapter 8. Transaction Boundaries—Manager Feature . . . . . . . . . . . 8-1

Display I/O Transaction Boundary Information . . . . . . . . . . . . . . . . . . . 8-1
SNA Performance Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Correlation Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
Connection Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
Device Description Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5
T2 Station I/O Manager Task Fields . . . . . . . . . . . . . . . . . . . . . . . 8-5
Session Traffic Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6
Sending Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7
Receiving Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10
Intermediate Session Traffic Work Load . . . . . . . . . . . . . . . . . . . . 8-11
Control Traffic Work Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11
Comparing Different Priority Levels . . . . . . . . . . . . . . . . . . . . . . . 8-11
APPN Control Point Performance Measurements . . . . . . . . . . . . . . . . 8-11
APPN Work Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-12
Session Setup Work Activities . . . . . . . . . . . . . . . . . . . . . . . . . . 8-17
APPC Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-21
From System A's Perspective . . . . . . . . . . . . . . . . . . . . . . . . . . 8-21
From System B's Perspective . . . . . . . . . . . . . . . . . . . . . . . . . . 8-22
APPC Performance Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-22
Performance Measurement and SNADS . . . . . . . . . . . . . . . . . . . . . 8-23
SNADS Transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-23
SNADS Sample Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-29
Sample Data Interpretation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-29
SNADS Performance Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-32
OS/400 File Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-33
Pass-Through Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-34
Pass-Through Performance Notes . . . . . . . . . . . . . . . . . . . . . . . 8-35
Data Queue Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-35

Chapter 9. Performance Graphics . . . . . . . . . . . . . . . . . . . . . . . . 9-1

Summary—Manager Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
Work with Graph Formats and Packages—Manager Feature . . . . . . . . . . 9-2
Create Graph Format—Manager Feature . . . . . . . . . . . . . . . . . . . . 9-4
Graph Types—Manager Feature . . . . . . . . . . . . . . . . . . . . . . . . . 9-4
Data Types—Manager Feature . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6
Legends—Manager Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-9
Create Graph Package—Manager Feature . . . . . . . . . . . . . . . . . . . 9-9

viii Performance Tools V4R2

 Change Graph Formats and Packages—Manager Feature . . . . . . . . . 9-10
Copy Graph Formats and Packages—Manager Feature . . . . . . . . . . . 9-11
Delete Graph Formats and Packages—Manager Feature . . . . . . . . . . 9-12
Display Sample Graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-12
Display Package Contents—Manager Feature . . . . . . . . . . . . . . . . 9-12
Work with Historical Data—Manager Feature . . . . . . . . . . . . . . . . . . . 9-13
Create Historical Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-14
Delete Historical Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-15
Display Graphs and Packages—Manager Feature . . . . . . . . . . . . . . . 9-15
Display Performance Graphs—Manager Feature . . . . . . . . . . . . . . . 9-16
Display Sample Graph—Manager Feature . . . . . . . . . . . . . . . . . . . 9-17
Display Graph Package—Manager Feature . . . . . . . . . . . . . . . . . . 9-17
Select Performance Data Member—Manager Feature . . . . . . . . . . . . 9-17
Select Categories for Performance Graphs—Manager Feature . . . . . . . 9-18
Specify Graph Options—Manager Feature . . . . . . . . . . . . . . . . . . 9-18
Display Historical Graphs—Manager Feature . . . . . . . . . . . . . . . . . 9-20
Display Graph Overlay—Manager Feature . . . . . . . . . . . . . . . . . . . . 9-21

Chapter 10. Performance Utilities—Manager Feature . . . . . . . . . . . . 10-1

Job Traces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1
File and Process Access Group (PAG) Utilities . . . . . . . . . . . . . . . . . 10-2
Analyzing Job Flow and Transaction Performance . . . . . . . . . . . . . . . 10-2
Start Job Trace (STRJOBTRC) Command . . . . . . . . . . . . . . . . . . 10-3
End Job Trace (ENDJOBTRC) Command . . . . . . . . . . . . . . . . . . . 10-3
Print Job Trace (PRTJOBTRC) Command . . . . . . . . . . . . . . . . . . . 10-4
Analyzing the Relationship of Programs and Database Files . . . . . . . . . . 10-9
Analyze Program (ANZPGM) Command . . . . . . . . . . . . . . . . . . . . 10-9
Analyze Database File (ANZDBF) Command . . . . . . . . . . . . . . . . 10-11
Analyze Database File Keys (ANZDBFKEY) Command . . . . . . . . . . 10-13
Analyzing Process Information . . . . . . . . . . . . . . . . . . . . . . . . . . 10-16
Display Access Group (DSPACCGRP) Command . . . . . . . . . . . . . 10-16
Analyze Process Access Group (ANZACCGRP) Command . . . . . . . . 10-18

Chapter 11. Performance Explorer . . . . . . . . . . . . . . . . . . . . . . . 11-1

Do I Need Performance Explorer? . . . . . . . . . . . . . . . . . . . . . . . . . 11-1
Who Needs Performance Explorer . . . . . . . . . . . . . . . . . . . . . . . 11-1
When You Need Performance Explorer . . . . . . . . . . . . . . . . . . . . 11-2
Comparison of Explorer to Other Performance Tools . . . . . . . . . . . . . . 11-2
Performance Explorer and Advisor Functions . . . . . . . . . . . . . . . . . 11-2
Performance Explorer and Performance Monitor . . . . . . . . . . . . . . . 11-2
Benefits of Performance Explorer . . . . . . . . . . . . . . . . . . . . . . . . . 11-3
How Performance Explorer Works . . . . . . . . . . . . . . . . . . . . . . . . . 11-3
Performance Explorer Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 11-4
General Flow of the Performance Explorer . . . . . . . . . . . . . . . . . . 11-5
Creating a Performance Explorer Definition . . . . . . . . . . . . . . . . . . . . 11-6
Starting the Performance Explorer . . . . . . . . . . . . . . . . . . . . . . . . . 11-7
Ending the Performance Explorer . . . . . . . . . . . . . . . . . . . . . . . . . 11-7
Deleting Performance Explorer Data . . . . . . . . . . . . . . . . . . . . . . . . 11-8
| Creating and Printing Performance Explorer Reports . . . . . . . . . . . . . . 11-8
Finding Your Performance Explorer Definitions . . . . . . . . . . . . . . . . . 11-9
Types of Performance Explorer Reports . . . . . . . . . . . . . . . . . . . . . 11-9
Common Report Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-9
Report-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-1
Work with Functional Areas—Manager Feature . . . . . . . . . . . . . . . . . 12-2
Creating a Functional Area—Manager Feature . . . . . . . . . . . . . . . . 12-3
Changing a Functional Area—Manager Feature . . . . . . . . . . . . . . . 12-4
Deleting a Functional Area—Manager Feature . . . . . . . . . . . . . . . . 12-5
Copying a Functional Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5
Delete Performance Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5
Copy Performance Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-7
Convert Performance Data (CVTPFRDTA) Command . . . . . . . . . . . . . 12-8

Chapter 13. A Problem Analysis Case Study . . . . . . . . . . . . . . . . . 13-1

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

Chapter 14. Working with Historical Data—Agent Feature . . . . . . . . 14-1

Create Historical Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-2
Delete Historical Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-3

Chapter 15. Managing the Performance Data—Agent Feature . . . . . . 15-1

Delete Performance Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1
Copy Performance Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2
Convert Performance Data (CVTPFRDTA) Command . . . . . . . . . . . . . 15-4
| Convert Performance Thread Data (CVTPFRTHD) Command . . . . . . . . . 15-6

Appendix A. Performance Tools CL Commands . . . . . . . . . . . . . . A-1

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

x Performance Tools V4R2

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

Appendix B. Defining Transaction Boundaries . . . . . . . . . . . . . . . B-1

Elements of Response Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
Differences in the Transaction Response Reports . . . . . . . . . . . . . . . . B-2
Operational Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4

Appendix C. Correlation of the System/36 and AS/400 System

Performance Parameters—Manager Feature . . . . . . . . . . . . . . . . . C-1

Appendix D. Comparison of Performance Tools . . . . . . . . . . . . . . D-1

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

Appendix E. Managing AS/400 System Performance in a Network . . . E-1

Planning the Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1
Implementing the Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1
Additional Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-4

Appendix F. Performance Checklist—Manager Feature . . . . . . . . . . . F-1

Planning for Performance and Tuning . . . . . . . . . . . . . . . . . . . . . . . . F-1
Basic 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-4
General 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. IBM
may not offer the products, services, or features discussed in this document in
other countries. Consult your local IBM representative for information on the pro-
ducts and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may be
used 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 matter
described in this document. The furnishing of this document does not give you any
license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing

IBM Corporation
500 Columbus Avenue
Thornwood, NY 10594
U.S.A.

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

IBM World Trade Asia Corporation

Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any other
country where such 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 OF
NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR
PURPOSE. Some states do not allow disclaimer of express or implied warranties in
certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors.

Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this publication
at any time without notice.

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

 Copyright IBM Corp. 1998 xiii

 IBM Corporation
Software Interoperability Coordinator
3605 Highway 52 N
Rochester, MN 55901-7829
U.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 any
equivalent 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-level
systems and there is no guarantee that these measurements will be the same on
generally available systems. Furthermore, some measurement may have been esti-
mated through extrapolation. Actual results may vary. Users of this document
should 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 the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which

illustrates programming techniques on 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 been
thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply
reliability, serviceability, or function of these programs. You may copy, modify, and
distribute 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 illustrations
may not appear.

Programming Interface Information

This publication is intended to help you to achieve high system performance. This
publication 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 that

obtain the services of IBM Performance Tools for AS/400 and IBM Operating
System/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 perform

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

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

Advanced Function Printing

Advanced 36
AFP
Application System/400
APPN
AS/400
AS/400e
C/400
Client Access
IBM
Information Assistant
Intelligent Printer Data Stream
IPDS
MVS
OfficeVision/400
Operating System/400
OS/400
Personal Computer AT
Personal System/2
RPG/400
System/36
SystemView
400

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 licensed
exclusively 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 marks
of 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 the
data to help identify and correct any problems.

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

Who should read this book

This book is intended for anyone who has to perform data collections and analyze
performance data.

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

The performance estimates presented are approximations which are believed to be

sound. The degree of success that you may achieve in the use of IBM equipment
and programs is dependent upon a number of factors, many of which are not under
IBM's control. Thus, IBM neither warrants nor guarantees that you can or will
achieve similar results. It is your responsibility to validate the estimates furnished
and to determine their relevance to your operation.

Any configuration recommended by the capacity planner of the Manager feature

should be verified with your marketing representative because the capacity planner
does not consider all attachable devices.

AS/400 Operations Navigator

AS/400 Operations Navigator is a powerful graphical interface for Windows 95/NT
clients. With AS/400 Operations Navigator, you can use your Windows 95/NT skills
to manage and administer your AS/400 systems. You can work with database
administration, file systems, Internet network administration, users, and user
groups. You can even schedule regular system backups and display your hardware
and 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 great
online information to guide you.

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

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

Prerequisite and related information

You should be familiar with the information about performance analysis as
described 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 shown
for the Manager feature.

For information about Advanced 36 publications, see the Advanced 36 Information

Directory, 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:
| [Link]

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:
| [Link]

| 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)
| – IDCLERK@[Link]
| 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.

1-4 Performance Tools V4R2

| 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

Chapter 1. Introduction to Performance Tools 1-5

| – 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.

1-6 Performance Tools V4R2

| 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.

Chapter 1. Introduction to Performance Tools 1-7

| 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.

1-8 Performance Tools V4R2

| 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 1. Introduction to Performance Tools 1-9

1-10 Performance Tools V4R2
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 Tools

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

Performance Tools must run in a library named QPFR. If a library by this name is
on your system, rename it before you install Performance Tools, using the Rename
Object (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. After
installing the first tape, you may receive a message saying that the licensed
product is restored but no language objects were restored. If this occurs, load the
next 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 LICPGM
and use the menu options.

How Performance Tools Counts Users

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

Printer File and Output Queues

The 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 (this
setting depends on whether the report is 80 or 132 characters wide). If the printer
file characteristics you want are different from the supplied printer file character-
istics, use the Change Printer File (CHGPRTF) command to alter them. Use of the
generic name, QP*, on this command changes all printer files in library QPFR to
the new form size.

 Copyright IBM Corp. 1998 2-1

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

Start Performance Tools (STRPFRT) Command

Use the STRPFRT command to start Performance Tools. After you enter the
command, the IBM Performance Tools menu for your Manager feature or Agent
feature appears. From this display, you can either choose one of the menu
selections, 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) to

prompt 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 the
cursor on the message line and press the Help key for additional detail. Pressing
F10 (Display messages in job log) from this detail display allows you to view all of
the 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 user
positions of the library list).
Ÿ The IBM Performance Tools menu appears.

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

2-2 Performance Tools V4R2

 Once you use the STRPFRT command to start the Performance Tools, any further
attempt 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 is
already operating from your job, a message appears that indicates that the oper-
ating environment for Performance Tools is already active. Multiple jobs may use
Performance 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 Feature

If 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

Select one of the following:

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 to
provide you with information about the performance of the system or a particular
job.

Each option on the Select Type of Status display has a corresponding command
associated with it, as shown in the following list. To use a function, such as working
with the system status, either enter option 1 on the command line of the Select
Type 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

2-4 Performance Tools V4R2
 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 data
using Performance Tools are described in Chapter 10, Performance
Utilities—Manager Feature, and Chapter 6, System Activity. The figures shown in
the sections following “Summary of Data Collection and Report
Commands—Manager Feature” on page 3-13 show the Performance Tools data
collection 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 Manager
feature. The STRPFRMON command is important in the overall analysis of your
system. Use it to collect data about resources that influence the performance of
your 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 and
the 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 Data

You should collect performance data regularly to establish a record of system per-
formance. If you know the performance characteristics of your system, you can
judge 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 produce
a report from this data. The report provides an overview of the performance vari-

 Copyright IBM Corp. 1998 3-1

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

With the Agent feature, use the Advisor and Work with Historical Data options to
analyze 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 new
application. This data provides valuable information on changes to system resource
utilizations as a result of the workload changes. When you review this data, limit
your observations to the differences in the active workloads on the system. Look at
the utilizations for the processing unit, disk, main storage, and communications. If
any of these resources is consistently overcommitted, you should determine the
reason.

To determine the reason for consistent overcommitment of a given resource, collect

trace data. The performance monitor trace data provides more detailed information
on the jobs, programs, and individual transactions that run on the system. If you are
using the Manager feature, depending on the resource, you might use some of the
additional 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. You
can determine the elements of transaction response time from these reports. In
addition, 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 collect
data depends on whether you collect only sample data, or a combination of sample
and trace data. The length of time you collect data can generally be longer when
you collect only sample data. When you collect sample data, you want it to reflect
the changes that occur when the various interactive and batch workloads go from
light 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 the
measurement, 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 collection
ends automatically when this area is filled. Thus, the length of time you collect data
depends 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 given
resource, you should try to collect data for workload periods that correspond to
those in which you have seen excessive utilization occur. If you trace data for a
longer period of time, increase the size of the component trace table.

3-2 Performance Tools V4R2

 When to End Data Collection
Use the End Performance Monitor (ENDPFRMON) command to end the data col-
lection. The collected data can automatically be transferred from the collection area
into a database file specified on the DMPTRC parameter on the ENDPFRMON
command. The collected data can be processed by a user-written exit program
specified on the EXITPGM parameter on the ENDPFRMON command. If you are
collecting 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 trace
data, there is additional system overhead and you should try to schedule the end of
the 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 the
performance 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 the
STRPFRMON 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

3-4 Performance Tools V4R2

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 monitor
parameter (STRDBMON) is *YES on the STRPFRMON command.

Whenever you use the STRPFRMON command, you collect sample data, but you
can also collect trace data. You generally choose to collect trace data to gain addi-
tional detailed information about specific jobs and transactions. By collecting trace
data, 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 data
you collect. To review examples of these reports, see “System Report” on
page 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 the
STRPFRMON command. See “Summary of Data Collection and Report
Commands—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 feature
to analyze trace data. See Appendix D, Comparison of Performance Tools , for
more information.

For the Manager feature, the Performance Tools program has additional functions
to 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 is
using the same member that is collected at that time.

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

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

To collect sample or trace data, follow these steps:

Chapter 3. Collecting System Performance Data 3-5

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

à ð
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
(C) COPYRIGHT IBM CORP.
á ñ

2. Choose the Collect performance data option on the IBM Performance Tools
menu, 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

Select one of the following:

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. The
current status of the performance monitor is shown.
3. Choose the Start collecting data option, and press the Enter key. The Start
Collecting Data display appears.

3-6 Performance Tools V4R2

 à ð
Start Collecting Data

Select one of the following:

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 collect
data. Any option you choose results in the collection of performance data using
STRPFRMON. Options 1 and 2 are designed for a new user of Performance
Tools (they provide more guidance in starting the performance monitor). These
options are discussed in the following sections. If you choose option 3 (Collect
data with command), a prompt for the STRPFRMON command appears as
though you entered the command and pressed F4 (Prompt).

Using System Defaults to Collect Data

If you choose option 1 (Collect data with defaults) on the Start Collecting Data
display, 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. The
default 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 for
the other STRPFRMON command parameters are used.
See the CL Reference for more information about the STRPFRMON command
parameters.

Chapter 3. Collecting System Performance Data 3-7

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

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

à ð
Collect Data with Menus

Type choices, press Enter.

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

Library . . . . . . QPFRDATA Name

Text . . . . . . . . .

1. Type the member and library name where you want to store the performance
data. 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 column
next to Trace Data, and press the Enter key.
Notes:
a. When this trace starts, all existing traces stop. Only one trace can be active
in the operating system.
b. The Agent feature does not analyze or report on trace data. To analyze or
report on trace data that is collected by the Agent feature, the data must be
sent to a system that has the Manager feature installed.
5. To indicate that you want to collect performance data for communications lines
and objects, type a 1 in the Option column next to Communications Data, and
press the Enter key.
The Set Data Collection Time display appears.

3-8 Performance Tools V4R2

à ð
Set Data Collection Time

Type choices, press Enter.

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 between
collections field. Fifteen minutes is usually an adequate sample interval for
problem 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 you
choose option 1 (Elapsed time), go to step 9. If you choose option 2 (Time of
day) for this prompt, the Set End Time display appears.

à ð
Set End Time

Type choices, press Enter.

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 days
from today field. Also indicate when you want data collection to stop in the
Time of day field.
9. If you choose option 1 (Elapsed time) for the End time option prompt on the
Collect Additional Data display, the Set Length of Time to Collect Data display
appears.

à ð
Set Length of Time to Collect Data

Type choices, press Enter.

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 collect
data 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 the
Manager feature, refer to Chapter 7, Performance Reports—Manager Feature.

Chapter 3. Collecting System Performance Data 3-9

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

à ð
Start Performance Monitor (STRPFRMON)

Type choices, press Enter.

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 operating
system. If *ALL is specified on the TRACE parameter while another trace is
running, 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 command
specifying 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. If
you 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 to
dump the trace after the monitor has ended. Object addresses in the trace data
resolve to names when DMPTRC is called. Any objects that are deleted
between the time the trace data is collected and the time the trace data is
dumped will not resolve. You will see addresses (which are not useful) instead
of names.

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

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

3-10 Performance Tools V4R2

 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 member
one 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 the
trace data in MBR(two). The trace data for MBR(one) will not correspond with the
sample data from MBR(one). For example, PRTSYSRPT(one) and
PRTTNSRPT(one) will contain conflicting information.

Collecting Performance Data Automatically

Note: 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 a
weekly schedule. Automatic performance collection allows you to select specific
days of the week on which automatic data collection is to occur using the OS/400
performance monitor.

On the IBM Performance Tools menu, choose the Collect performance data
option and press the Enter key. The Collect Performance Data display appears.

Chapter 3. Collecting System Performance Data 3-11

 à ð
Collect Performance Data ABSYSTEM
11/ð7/95 ð8:ð7:27
Performance monitor status:
Status . . . . . . . . . . . . : Not running

Select one of the following:

1. Start collecting data

2. Stop collecting data
3. Work with performance collection

Selection or command
===> 3

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

á ñ

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

à ð
Work with Performance Collection

Type options, press Enter.

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.

3-12 Performance Tools V4R2

 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 also
use the ADDPFRCOL command to access the Add Performance Collection
(ADDPFRCOL) display.)

Performance Collection Setup

Automatic performance collection requires a batch job (QPFRCOL) that queries the
schedule created by the Add Performance Collection function and submits the Start
Performance Monitor (STRPFRMON) command at the appropriate times. This job
exists 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 collections
defined that are in a released status, the job ends. Therefore, anytime you add a
collection 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 collected
until all the performance collections are removed or held, or until you enter
ENDPFRCOL. You need to start performance collection again if you add performance
collections later.

Summary of Data Collection and Report Commands—Manager Feature

Table 3-2 through Table 3-5 in the following sections present the commands for
various 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 produce
reports, 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 on
the available command entry lines, these figures may serve as a reference for the
available commands.

System-Level Analysis—Manager Feature

System-level data collection and analysis provides you with a comprehensive view
of how the system operates. This information ranges from a system operational
overview to an analysis of individual transactions. System-level data collection and
analysis also provides you with system modeling functions for capacity planning
and performance prediction.

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

Chapter 3. Collecting System Performance Data 3-13

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

Table 3-2 (Page 1 of 2). System Data Collection (STRPFRMON Command) and Report Commands
Type of Report Information Shown on When to Use the
Level of Data Data Command the Reports Command
Job Disk Sample data ANZPFRDTA Contention analysis and Processing trends
System recommendations System model
Workload
projection
Hardware growth
Processing unit
Main storage
Disk
Job Disk Sample data PRTSYSRPT Workload Utili- Processing trends
System PRTCPTRPT zation System model
Processing unit Workload
Disk projection
Main storage Hardware growth
Communications Processing unit
Model parameters Main storage
External response Disk
times
System Job Trace data PRTTNSRPT Workload Utili- Workload
Program zation projection
Processing unit Hardware growth
Exceptional waits Pool configuration
Transaction detail Overcommitment
Top ten reports Application design
Object contention File contention
Concurrent batch Transaction
jobs Significance
System model Classification
parameters Program use
Transaction summary System model
and detail Processing trends
System Job Trace data PRTTRCRPT Resources used Progression of batch jobs
Program Files Exceptions traced through time
Disk State transitions
Job Program Sample data STRBEST System performance Before installing
Files Disk projections When growth
Capacity planning is anticipated,
Configuration either in
planning hardware or
workload
When a new
application is
to be installed
Performance
analysis

3-14 Performance Tools V4R2

Table 3-2 (Page 2 of 2). System Data Collection (STRPFRMON Command) and Report Commands
Type of Report Information Shown on When to Use the
Level of Data Data Command the Reports Command
Job Program Trace data PRTLCKRPT File, record, or To reduce or
Files Disk object contention remove object
by: contention
Object name Problem analysis
Holding or
requesting job
Time
Job Program Sample data PRTJOBRPT Utilization Problem analysis
Files Disk Processing unit
Disk
Communications
Workload
Job Program Sample data PRTPOLRPT Utilization Problem analysis
Files Disk Main Storage
Workload
Subsystem
Job Program Sample data PRTRSCRPT Utilization Problem analysis
Files Disk I/O Processing
unit
Disk
External response
times
Application or Statis- PRTPEXRPT Program and When general
Program tics procedure performance
Profile statistics on monitoring
Trace calls, CPU usage cannot find
and I/O problems
Sampling of CPU Problem analysis
usage of program
and procedure
instructions
Detailed record
of performance
related events
as they
occurred

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

Job Trace Analysis—Manager Feature

Job trace analysis enhances the operating system’s standard trace job reports and
provides a summary of job operation and transaction processing. The primary use
for job trace analysis is to determine application flow. You can determine what parts
of 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 job
or transaction processing times.

Chapter 3. Collecting System Performance Data 3-15

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

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

Table 3-3. Job Trace Data Collection (STRJOBTRC Command) and Report Commands
Information Shown on When to Use the
Level of Data Type of Data Report Command the Reports Command
Job Program Trace data PRTJOBTRC Program name For program devel-
Files ENDJOBTRC Control flow opment
I/O operations To identify jobs or
Full/shared opens programs that
Exceptions perform poorly
Message handling
Disk I/O summary

File Use and Database Structure Analysis—Manager Feature

The commands shown in Table 3-4 provide an overview of the program file use
and 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

Information Shown on When to Use the
Level of Data Report Command the Reports Command
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 Analysis
Job analysis provides you with a view of the operational environment for all jobs, or
a group of jobs, in the system at a given time. Use the information from a specific
process analysis to improve the performance of the process. This analysis can help
you 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 on
page 3-17.

3-16 Performance Tools V4R2

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

Table 3-5. Process Data Collection (DSPACCGRP Command) and Report Commands
Information Shown on When to Use the
Level of Data Report Command the Reports Command
Job Program Files DSPACCGRP File use Reduce program size
ANZACCGRP Files used at the Reduce number of
same time open files
Open Data Path Reduce process
Buffer size access group (PAG)
Formats (size I/O
and number) Determine group job
I/O counts candidates
Duplicates
PAG size
Active programs

Chapter 3. Collecting System Performance Data 3-17

3-18 Performance Tools V4R2
Chapter 4. Advisor
The advisor provides an easy-to-use way to improve many of the performance
characteristics of your system.

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

Automatic system tuning is a useful method for maintaining the basic conditions for
good performance. If it is set to work at each IPL, it resets the basic tuning values
to the recommended settings for the system configuration and controlling sub-
system. Dynamic automatic system tuning adjusts only pool sizes and activity levels
of 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 the
number 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 conditions
on your system.

The advisor analyzes performance data you collect with the performance monitor
and it can produce recommendations and conclusions to help improve perform-
ance. The advisor might recommend changes to basic system tuning values, and
might 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 the
advisor’s conclusions to make changes to your system, to guide further perform-
ance data collection, or to help you request performance reports containing more
information and explanations.

The advisor can help you to improve system performance, but it will not identify or
correct 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 to
improve their performance
Ÿ Analyze noninteractive trace data

 Copyright IBM Corp. 1998 4-1

 The advisor is a good first tool to use to improve system performance. In many
instances, it will be the only tool required to make the improvements you need. This
chapter takes you through the process for using the advisor. In general, this
process 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 each
problem 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 data
collection, or to request other more detailed performance reports.
5. Observe the effects of any tuning changes, and decide if another cycle through
this process is required to further improve performance or to eliminate
unwanted side effects.

Notes:
1. The examples in this chapter show how to use the advisor, but they do not
contain specific solutions for any performance problems that might exist on a
particular AS/400 system.
2. Sometimes an analysis of data collected during normal system operation can
help 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 in
the Manager feature.
4. When the advisor makes no significant recommendations or conclusions and
the system's performance remains unacceptable, analysis at the application
level 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 some
guidelines and threshold values from the BEST/1 hardware table.

Collecting the Right Performance Data

Before collecting performance data, you should clearly describe the problem to be
investigated. From system users’ comments or your own experience, you can begin
to formulate a description of the problem. The problem description does not need to
be overly detailed or technical, just try to simply describe one problem. For
example:
Ÿ 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 is
slow first thing in the morning. Perhaps batch processing seems slow late in the
afternoon.

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

4-2 Performance Tools V4R2

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

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

Requesting an Analysis
After performance data is collected for the time periods near when a problem
seems 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 Performance
Tools menu, or type the Analyze Performance Data (ANZPFRDTA) command on
any command line.
Note: To analyze performance data from a library other than QPFRDATA when
using the ANZPFRDTA command, type the command and press F4
(Prompt) to change the library name.

à ð
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
===> 1ð

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

F16=System main menu
(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 Member
When the Advisor option is selected, or the ANZPFRDTA command is run, the
Select 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 [Link]
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 [Link]ð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 data
collected during a time when the problem occurred. When you select a member
and 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 the
member 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 the
Select Member for Analysis display, this member may appear with blank Date
and Time fields until the first interval is collected.

Selecting Time Intervals

4-4 Performance Tools V4R2

 à ð
Select Time Intervals to Analyze

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

Type options, press Enter.

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 the
Select Member for Analysis display.

The columns on the Select Time Intervals to Analyze display can help you focus
the analysis on time intervals when the suspected performance problem seems to
have occurred. If there are no obvious reasons to select only some of the displayed
time 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 to
request 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 Histogram
Sometimes a graph of the data for one of the performance values in the data
makes it easier to select specific time intervals of data for analysis. To define and
display a graph (called a histogram), press F11 (Display histogram) on the Select
Time Intervals to Analyze display. The display then changes to include the Select
Histogram window.

Chapter 4. Advisor 4-5

 à ð
Select Time Intervals to Analyze
............................................
: 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...
F3=Exit F5=Refresh F11=Display histogram F12=Cancel F13=Select all
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 time
intervals contained in the member.

As an example, to make it easier to see the time intervals where CPU utilization is
the highest, you could select one of the CPU utilization views. A sample histogram
for 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
F3=Exit F5=Refresh F11=Display histogram F12=Cancel F13=Select all
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

4-6 Performance Tools V4R2

 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 on
the 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 and
could affect system performance for other users.
2. The analysis performed by the advisor includes all of the types of performance
data for the selected time intervals, and is not limited to the type of data
selected to create the histogram.

Analyzing Trace Data

The advisor can analyze interactive transactions when the performance monitor is
run 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 file
does 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 noninteractive
jobs to interactive. After the job types have been changed, the *FILE option of the
Transaction 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 trace
data, 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 file
may not include time intervals that match the intervals that were picked for
the advisor to analyze.

Using the Advisor’s Results

Depending on the content of the selected performance data, the advisor can
produce recommendations, conclusions, and interval conclusions. What these are
and how you can use them are explained as you look at the following examples.

When a performance data analysis has completed, the Display Recommendations

display shows the results.

Chapter 4. Advisor 4-7

 à ð
Display Recommendations
System: ABSYSTEM

Member . . . . . . . : Q98137ð843 Library . . . . . . : QPFRDATA

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

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

Start time . . . . . : ð[Link]ð7 Serial number . . . : 1ð-11AðD

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

Type options, press Enter.

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 Recommendations
The Recommendations section of this display deals with conditions that significantly
affect system performance. The recommendations result from comparing the
system values and conditions in the analyzed performance data to the basic
AS/400 performance guidelines.

The recommendations suggest changes to the basic system tuning values that can
improve performance. They also list problems that can be solved by other actions.
In this example, the recommendations about changing pool sizes can be carried out
by changing system tuning values. But, the recommendation about ASP (auxiliary
storage pool) space capacity might require redefining the use of system disk space
or adding to system disk capacity. You might need technical assistance to complete
this type of recommendation. Auxiliary storage pool can be one or more storage
units defined from the disk units or disk unit subsystems that make up auxiliary
storage. ASPs provide a means of isolating certain objects on specific disk units to
prevent 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 an

example, the following displays show the details for the example recommendation
Increase pool size for listed pools.

4-8 Performance Tools V4R2

à ð
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 the
bottom of this display and continuing on the following displays discusses the effects
of changing a pool’s size.

à ð
Display Detailed Recommendation

Recommendation:

Increase pool size for listed pools.

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...
Press Enter to continue.

F3=Exit F12=Cancel

á ñ
Many recommendations include this type of information to help you choose the right
changes to make to your system.

Chapter 4. Advisor 4-9

Changing System Tuning Values
To see and select the tuning changes related to the recommendations, press F9
(Tune system) on the Display Recommendations display. A display similar to the
following 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
Select one of the following:

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 advisor
make all the changes shown in the Advisor Recommended Value column.
Usually this is a good choice to make when starting to solve a performance
problem.
Ÿ 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 the
advisor set the values as they were when the analyzed performance data was
collected (shown in the Data Collection Value column).
Ÿ Write down the tuning values that fit your needs, and use the appropriate
system 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 you
want to reset your configuration to what it was at the time of data collection. If
the Advisor Recommended Value equals the Data Collection Value, then the
advisor is saying that this is an adequate setting for the workload analyzed. If
the Advisor Recommended Value does not equal the Data Collection Value,
then you will see recommendations and conclusions as to what should be
changed.
2. When the dynamic tuning support is active (the system value is 2 or 3), the
storage pool sizes and activity levels are automatically changed. Because of
this automatic change, the advisor is unable to process the tuning request.

4-10 Performance Tools V4R2

Understanding Conclusions
The Conclusions section of the Display Recommendations display lists conditions
that could have affected performance when the analyzed data was collected. These
conditions can include thresholds reached, save and restore activities, transmission
line errors, and so on.

à ð
Display Recommendations
System: ABSYSTEM
Member . . . . . . . : Q98137ð843 Library . . . . . . : QPFRDATA
System . . . . . . . : ABSYSTEM Version/Release . . : 4/ 2.ð
Start date . . . . . : ð5/17/98 Model . . . . . . . : ðð -ð142
Start time . . . . . : ð[Link]ð7 Serial number . . . : 1ð-11AðD
QPFRADJ . . . . . . : ð QDYNPTYSCD . . . . . : 1

Type options, press Enter.

5=Display details

Option Recommendations and conclusions

Recommendations
Decrease pool size for listed pools.
Increase 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...
F3=Exit F6=Print F9=Tune system F12=Cancel F21=Command line

á ñ
Some conclusions describe conditions that caused the advisor to make particular
recommendations. Other conclusions not related to recommendations can be used
as 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 following
example is the display showing details for the conclusion Pool fault rates exceeded
guideline that supports the recommendation to increase the size of pool 1.

Chapter 4. Advisor 4-11

 à ð
Display Detailed Conclusion

Conclusion:

Pool fault rates exceeded guideline.

Detailed conclusion:
PFR2513
Technical description . . . . . . . . : The following table shows the
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 [Link]ð4

More...
Press Enter to continue.

F3=Exit F12=Cancel

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

Understanding Interval Conclusions

The Interval Conclusions section of the Display Recommendations display contains
the detailed data to support the conclusions for the analyzed time intervals.

à ð
Display Recommendations
System: ABSYSTEM
Member . . . . . . . : Q98137ð843 Library . . . . . . : QPFRDATA
System . . . . . . . : ABSYSTEM Version/Release . . : 4/ 2.ð
Start date . . . . . : ð5/17/98 Model . . . . . . . : ðð -ð142
Start time . . . . . : ð[Link]ð7 Serial number . . . : 1ð-11AðD
QPFRADJ . . . . . . : ð QDYNPTYSCD . . . . . : 1

Type options, press Enter.

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
F3=Exit F6=Print F9=Tune system F12=Cancel F21=Command line

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

4-12 Performance Tools V4R2

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

à ð
Display Detailed Interval Conclusion

Interval conclusion:

Pool fault rates above guideline.

Detailed interval conclusion:

PFR2553
Technical description . . . . . . . . : The following table shows the
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 [Link]

1 3.1 3.ð 11/ð1/98 [Link]ð6
1 3.6 3.ð 11/ð1/98 [Link]ð4

Bottom
Press Enter to continue.

F3=Exit F12=Cancel

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

Following is the details display for another type of sample interval conclusion, Total
disk 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
Press Enter to continue.

F3=Exit F12=Cancel

á ñ

Chapter 4. Advisor 4-13

 An interval conclusion like this one provides information but does not support a
conclusion 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 Recommendations

After you request a performance analysis, and look over the results, often the next
step is to have the advisor tune the system as it recommends. Do this by selecting
menu 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 collect
more performance data during the next time period when you expect the problem to
occur. 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 the
changes are not fully compatible with some of your processing requirements, or if
several problems are being worked on.

The first attempt to solve a basic performance problem can be successful. But
sometimes 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 might
have no further recommendations or conclusions that you can use. At this time you
could use other performance reports and commands to work on the problem. These
are described in Work Management.

Sometimes tuning alone will not solve performance problems. To handle the
intended work load, a system might need additional main storage, disk storage, or
processing 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.

4-14 Performance Tools V4R2

Chapter 5. Displaying Performance Data
This chapter describes how to interactively view the performance data collected by
the Start Performance Monitor (STRPFRMON) command. This Display Perform-
ance Data function can be used either while the performance monitor is active or
after the collection is completed.
Note: The data collection does not need to contain the trace data in order to use
this display function. Trace data may be required, however, to further
analyze performance problems isolated by this function.

Display Performance Data

To interactively display sample performance data, you can do one of the following:
Ÿ Type the Display Performance Data (DSPPFRDTA) command on any
command line using the default value of *SELECT for the member parameter.
Ÿ Type the DSPPFRDTA command on any command line specifying a member
for the MBR parameter.
Note: If you specify a member on the DSPPFRDTA command, you do not see
the Select Performance Member display or the Select Time Intervals to
Display display. The Display Performance Data function starts to read
the 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

Type option, press Enter.

1=Select

Option Member Text Date Time

_ Q983221324 11/17/98 [Link]ð6
_ Q9831ð1458 11/ð5/98 [Link]ð
_ Q983ð81ðð9 11/ð3/98 1ð:ð9:13
_ Q983ð7ð759 11/ð2/98 ð[Link]

Bottom
F3=Exit F12=Cancel F15=Sort by name F16=Sort by text
F19=Sort by date/time
(C) COPYRIGHT IBM CORP. 1981, 1998.
á ñ
The member name, a text description, and the date and time you collected each
set of performance data appear on this display. If you cannot find the data you

 Copyright IBM Corp. 1998 5-1

 want to display, use the Roll keys to page through the list of members or use the
appropriate function key to sort the sets of performance data. You can sort the data
by member name, text description, or by the date and time the member was
created. When you find the performance data you want to display, for the Manager
feature 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 the
Select Performance Member display, this member may appear with blank
Date 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 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 performance members available in
the 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 to
Display display appears.

à ð
Select Time Intervals to Display

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

Type options, press Enter.

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
F3=Exit F5=Refresh F11=Display histogram F12=Cancel F13=Select all
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 processed
now, so there is reasonable response time when moving between displays later.
Note: The initial processing may cause a noticeable delay in presenting the first
display.

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

5-2 Performance Tools V4R2

à ð
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 . . . . . : [Link]ð6 Serial number . . . : 1ð-1288312
QPFRADJ . . . . . . : ð QDYNPTYSCD . . . . . : 1

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 a
new member name in the Member field and press the Enter key, the data in that
member appears on the display. If you type a new library name in the Library field
and press the Enter key, the program tries to locate the member in the specified
library. 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. It
highlights the values on this display that exceed the threshold values.

Therefore, if the interactive CPU utilization or the disk utilization exceeds the
threshold, 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 entry
display without exiting the display function. Once you exit the command entry, you
are immediately returned to the Display Performance Data display without having to
experience the initial processing delay.

To better understand system performance, you might want to view the data sorted
by category. The second set of function keys on this display allows you to group
the 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 require
further 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 separated
into the subsystem, job type, and interval categories.

Display Performance Data by Subsystem

If 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 which
the 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 in
particular subsystems, type a 5 in the appropriate Option fields and press the Enter
key. If you do not want to select a particular subsystem, but would rather view the
data for all the jobs in the measurement, press F6 (Display all jobs).

Display Performance Data by Job Type

If you press F14 on the Display Performance Data display, the Display by Job Type
display appears.

5-4 Performance Tools V4R2

 à ð
Display by Job Type

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 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 the
jobs running on your system.

From this display you may be able to isolate a single job type or group of job types
that 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. If
you do not want to select a particular job type, but would rather view the data for all
the jobs in the measurement, press F6 (Display all jobs).

Display Performance Data by Interval

If you press F15 on the Display Performance Data display, the Display by Interval
display appears.

Chapter 5. Displaying Performance Data 5-5

 à ð
Display by Interval

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 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 [Link] 87.27 229 955 1.96 14717
_ ð9/19/98 [Link] 63.ð5 236 921 1.83 11693
_ ð9/19/98 [Link] 55.34 2ð7 823 2.11 9715
_ ð9/19/98 [Link] 54.79 2ð4 885 2.54 9585
_ ð9/19/98 [Link] 49.17 2ð9 8ð6 1.37 9787
_ ð9/19/98 [Link] 58.54 215 1ð21 1.31 11ð73
_ ð9/19/98 [Link] 71.72 241 12ð7 1.56 151ð3
_ ð9/19/98 [Link] 71.ð4 222 1ð89 1.6ð 15ð18
More...
F3=Exit F6=Display all jobs F12=Cancel F13=Display by subsystem
F14=Display by job type

á ñ
This display categorizes the performance data according to the collection intervals
that occurred during the measurement.

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

Display Jobs
If you selected a subsystem on the Display by Subsystem display, selected a job
type on the Display by Job Type display, selected an interval on the Display by
Interval display, or pressed F6 (Display all jobs) on any of these or the Display
Performance Data display, the Display Jobs display appears.

5-6 Performance Tools V4R2

 à ð
Display Jobs

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

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

Type options, press Enter.

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 the
display is replaced by a Job Type or a Interval indicator. Also, if you selected a
particular job type, the Job Type column does not appear because all the jobs have
the same type as indicated by the Job Type field at the top of the display. If you
request to see all the jobs (by pressing F6 on the Display by Subsystem, the
Display 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 a
value of ‘*ALL’ and the Job Type column is present. If F6 is pressed from the
Display Performance Data display, there is no indicator, such as subsystem, job
type, or interval, at the top of the display. Also, in this case, the Job Type column
would be present.

Display Job Detail

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

Chapter 5. Displaying Performance Data 5-7

 à ð
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 .ððð ð .ð ð .ð .ð .ð
[Link] .883 2 3.ð 293 .8 .ð .ð
[Link] 4.93ð 18 2.8 138 3.6 .ð .ð
[Link] 12.935 43 1.7 116 8.6 .ð .ð
[Link] 1.938 25 .4 67 5.ð .ð .ð
[Link] .693 1ð .5 28 2.ð .ð .ð
More...
Press Enter to continue.

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 performance
information 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 Resources

When you are on the Display Performance Data display, you may want to view the
performance data specifically related to storage pools, disk units, or communi-
cations lines, instead of the job-related information previously discussed. The third
set 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 Detail

If you press F19 on the Display Performance Data display, the Display Pool Detail
display appears.

5-8 Performance Tools V4R2

 à ð
Display Pool Detail

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

Library . . . . . : QPFRDATA

Type options, press Enter.

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 in
the 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 for
the entire measurement, you may want to examine the data for a particular pool
over time. Using the Display pool intervals option allows you to view the same pool
information broken down into the time intervals in which it occurred.

Display Pool Interval

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

Chapter 5. Displaying Performance Data 5-9

 à ð
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
[Link] 6ð416 72 936 1.9 2.4 119.9 14.7 6ð.7
[Link] 6ð416 72 886 1.8 2.1 167.7 14.8 76.6
[Link] 6ð416 72 811 2.1 2.6 237.6 13.2 54.5
[Link] 6ð416 72 861 1.4 2.ð 1ð5.3 13.8 93.6
[Link] 6ð416 72 794 1.3 2.1 125.2 12.7 53.6
[Link] 6ð416 72 942 1.3 2.1 154.ð 13.6 54.ð
[Link] 6ð416 72 1146 1.5 2.7 159.5 16.4 69.4
[Link] 6ð416 72 1ð77 1.6 2.5 157.5 16.ð 64.7
[Link] 6ð416 72 1124 1.4 2.8 136.2 15.6 2ð9.2
Bottom
Press Enter to continue.

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 the
Display Pool Detail display, except that the data is broken down by time intervals. A
second view (not shown here) also exists for the Display Pool Interval display,
which presents the data for the state transitions.

Display Disk Detail

If you press F20 on the Display Performance Data display, the Display Disk Detail
display appears.

à ð
Display Disk Detail

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

Library . . . . . : QPFRDATA

Type options, press Enter.

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

á ñ

5-10 Performance Tools V4R2

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

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

Display Disk Interval

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

à ð
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
[Link] ð1 6ð.6 4.7 .7 1.8 1.9 1.3
[Link] ð1 6ð.6 4.5 .9 2.7 1.2 .9
[Link] ð1 6ð.6 5.3 .7 1.6 1.4 1.1
[Link] ð1 6ð.7 4.ð .8 1.7 .7 .7
[Link] ð1 6ð.7 5.1 .9 2.ð 1.4 1.3
[Link] ð1 6ð.7 5.3 .7 2.ð 1.6 1.8
[Link] ð1 6ð.7 12.8 1.5 4.2 3.3 3.1
More...
Press Enter to continue.

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 the
Display 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 disk
unit cannot change from one interval to the next.

Display Communications Line Detail

If 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 used
to tune any system.

Chapter 5. Displaying Performance Data 5-11

 à ð
Display Communications Line Detail

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

Library . . . . . : QPFRDATA

Type options, press Enter.

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 information

for each communications line attached to the system.

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

Display Remote Jobs

If you type a 5 (Display remote jobs) on the Display Communications Line Detail
display 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 that
line listed by job.

5-12 Performance Tools V4R2

 à ð
Display Remote Jobs

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

Line type . . . . . : SDLC Library . . . . . : QPFRDATA
Line speed . . . . . : 9.6 Elapsed time . . . . : ðð:54:16

Type options, press Enter.

5=Display job detail

Job CPU Tns Avg Disk

Option Job User Number Type Util Count Rsp I/O
_ 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...
F3=Exit F12=Cancel F15=Sort by job F16=Sort by job type
F19=Sort by CPU F24=More keys

á ñ
Figure 5-2. Display Remote Jobs

If you type a 5 in the Option column, you can display more detailed information for
the remote job. This option calls the Display Job Detail display, just as option 5 did
from 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 Data

To 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 the
Enter key. The resulting Display Communications Interval Data display lists the per-
formance averages and totals for that communications line for the time intervals in
the current performance data member.

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

Each communications protocol has its own type of Display Communications Interval
Data display, but all are quite similar. An example and description for synchronous
data 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)

Chapter 5. Displaying Performance Data 5-13

 Ÿ 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
[Link]ðð 78 1,818 ð7 1,818 ðð
[Link]ðð 78 1,818 ðð 1,818 ðð
[Link]ðð 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 Jobs

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

5-14 Performance Tools V4R2

 à ð
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 CPU Tns Avg Disk

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
F3=Exit F12=Cancel F15=Sort by job F16=Sort by job type
F19=Sort by CPU F24=More keys

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

Display Network Interface Data

To see a display of performance data for Integrated Services Digital Network
(ISDN) network interfaces, press F13 (Display network interface data) on the
Display 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 and
channel pair configured on the system that data was collected for. From this
display, you can view the data on a per-interval basis by typing a 7 by the network
interface and channel you want to see.

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

Chapter 5. Displaying Performance Data 5-15

 à ð
Display Network Interface Data

Member . . . . . . . : ISDN1 Elapsed time . . . . : ð[Link]

Library . . . . . : V4R2CT

Type options, press Enter.

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
F2ð=Sort by line util F24=More keys

á ñ
Figure 5-4. Display Network Interface Data

Display Channel Interval Data

To see a display of performance data for a specific ISDN network interface and
channel by time interval, type a 7 (Display channel interval data) in the Option field
next to the network interface on the Display Network Interface Data display and
press the Enter key. The resulting Display Channel Interval Data display lists the
performance averages and totals for that network interface and channel for the time
intervals in the current performance data member.

Each channel type has its own type of Display Channel Interval Data display. An
example and description of this display for each channel type follow.

5-16 Performance Tools V4R2

à ð
Display Channel Interval Data

Network Interface . : ISDNSS_B Member . . . . . . . : ISDN1

Channel . . . . . . : B1 Library . . . . . : QPFRDATA
Line speed . . . . . : 64.ð Elapsed time . . . . : ð[Link]
IOP name . . . . . . : CMBð1

Type options, press Enter.

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
[Link] ISDNSS_B1 99/99/99 347 33 13ð 39
[Link] ISDNSS_B1 99/99/99 35 1ðð 75 1ðð
[Link] ISDNSS_B1 27/99/7ð 376 52 578 34
14:5ð:55 ISDNSS_B2 ðð/ð1/ðð 256 ð 255 ð
[Link] 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
F2ð=Sort by line util F24=More keys

á ñ
Figure 5-5. Display Channel Interval Data for B-channel

From this display you can request data about the jobs using the communications
line listed during any of the time intervals. To do this, type a 5 in the Option column
by the selected time interval.

à ð
Display Channel Interval Data

Network Interface . : ISDNSS_A Member . . . . . . . : ISDN1

Channel . . . . . . : D Library . . . . . : QPFRDATA
Line speed . . . . . : 16.5 Elapsed time . . . . : ð[Link]
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
[Link]ð 12/21/16 42 28 15 26 452
15:ð1:19 2ð/ð6/13 74 74 33 1ðð 135
[Link] ðð/ðð/ðð ð ð 5 ð ð
[Link] ðð/ðð/ðð ð ð 2 ð ð
[Link] ðð/ðð/ðð ð ð 2 ð ð
[Link] ð7/1ð/ð9 21 1ðð 34 1ðð 348
More...
Press Enter to continue.

F3=Exit F11=View 2 F12=Cancel F13=Display maintenance channel

F24=More keys

á ñ
Figure 5-6. Display Channel Interval Data for D-channel

Chapter 5. Displaying Performance Data 5-17

Display Maintenance Channel Data
This display shows performance data for the ISDN maintenance channel. To
request it, press F13 (Display maintenance channel) on the Display Channel
Interval 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 . . . . : ð[Link]

Percent
Percent Severely Far
Itv Errored Errored DTSE DTSE End Code
End Seconds Seconds In Out Violation
[Link]ð 5ð 36 734 83 32
15:ð1:19 6 24 32 14 52
[Link] ð ð ð ð ð
[Link] ð ð ð ð ð
[Link] ð ð ð ð ð
[Link] 99 99 36 45 66
16:ð1:13 95 8ð 11 9 1
More...
Press Enter to continue.

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

5-18 Performance Tools V4R2

Chapter 6. System Activity
This chapter describes the functions that allow you to work with performance data
for 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 a
QAITMON 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 (System
activity) on the IBM Performance Tools menu. If you select option 8, the System
Activity menu appears.

à ð
System Activity

Select one of the following:

1. Work with system activity

2. Print activity report
Ÿ
Ÿ
Ÿ

Refer to “Work with System Activity” and “Print Activity Report” on page 6-9 for a
description of both selections shown on the System Activity menu.

Work with System Activity

The Work with System Activity (WRKSYSACT) command allows you to view and
collect performance data in a realtime fashion. This data, which consists of CPU
utilizations, synchronous and asynchronous I/O counts, storage amounts, and
more, 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 function
can be active at one time. If this function is currently active when the WRKSYSACT
command 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 has
occurred during the elapsed time since a previous collection. Notice that this may
contrast with other system functions that generally provide cumulative values until
specifically reset. In most cases the time interval between data collections ranges
from 1 second to several minutes, depending on how often you want to view or
collect new data. On systems with very little activity, a subsecond refresh interval
may be possible.

 Copyright IBM Corp. 1998 6-1

 Depending on the value specified for the OUTPUT parameter of the Work with
System Activity command, the data gathered by this function is processed in one of
the 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 job
under the name WRKSYSACT. When the data is written to a file and shown on the
display, the statistics are put in the file each time the display is refreshed. This
does not include the data presented on the initial display of the Work with System
Activity 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 third
method), 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

Type options, press Enter.

1=Monitor job 5=Work with job
Total Total
Job or CPU Sync AsyncPAG
Opt Task User Number Thread Pty Util I/O I/OFault
_ 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 ð ð ð
_ SMAIð1 ð .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 refresh
feature 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, reflects
the length of time in which the currently shown performance statistics occurred.
Described in a different way, this value represents the time between the last display
refresh and the next-to-last display refresh.
Note: The Work with System Activity display automatically gathers the data twice
before displaying the first display. Therefore, the initial Elapsed time should
be approximately 2 seconds, which means that the statistics shown
occurred in the 2 seconds previous to the current display.

6-2 Performance Tools V4R2

Single-Processor System
The Overall CPU represents the CPU utilization for the entire system during the
elapsed 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 amount
of processing unit time, thus affecting the overall utilization, but not use enough
CPU resource to be included in the list of active jobs. (Refer to the requirements for
being considered active at the beginning of this chapter.) The discrepancy in CPU
utilizations, however, is small and should have little effect on the usability of this
function.

Also, the Overall CPU could exceed 100% on extremely busy systems, because
the data collection process does not occur instantaneously. However, you should
be aware that overall CPU utilizations slightly over 100% are an acceptable possi-
bility.

Multiple-Processor System
For 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 utilization
divided 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 more
than one processor:

à ð
Work with System Activity ABSYSTEM
ð2/ð8/96 1ð:45:19
Automatic refresh in seconds . . . . . . . . . . . . . . . . . 5
Elapsed time . . . . . . : ðð:ð1:ð2 Average CPU util . . : 97.ð
Minimun CPU util . . . . : 94.1 Maximum CPU util . . : 99.9
Number of CPUs . . . . . : 4

Type options, press Enter.

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
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
F3=Exit F1ð=Update list F11=View 2 F12=Cancel F19=Automatic refresh
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” on
page 6-5 and “Working with Jobs” on page 6-6 for more information on these
options.

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 when
INFTYPE(*ALL) is specified. This value for the Information type parameter
instructs the function to display both jobs and tasks. Specifying
INFTYPE(*JOBS) causes the Job or Task column, to be replaced by the
Job column because only jobs are to be displayed. Similarly, specifying
INFTYPE(*TASKS) causes the Job or Task column to be replaced by the
Task column since only tasks are to be displayed. Later sections of this
chapter describe how to switch between these information types through the
use of function keys.

Automatic Refresh Mode

Automatic Refresh mode represents an important feature of the Work with System
Activity function. Once started, this mode continually updates the display without
requiring further user intervention.

To start the Automatic Refresh mode, first enter the desired number of seconds
between refreshes in the Automatic refresh in seconds field. This value, which has
an initial default of 5 seconds, can range from a minimum of 1 second to a
maximum of 900 seconds (15 minutes).
Note: Setting the Automatic refresh seconds at 5 or greater generally results in
the Work with System Activity function using reasonably small amounts of
the processing unit, depending on the size of the system being monitored.
Setting this value lower than 5 seconds causes this function to use larger
amounts of the processing unit, and therefore, is not recommended.

Once you have established the desired refresh interval, pressing F19 (Automatic
refresh) starts the automatic refresh mode. Automatic refresh continues to display
the same view and type of information that was previously selected. For example, if
you had been examining both jobs and tasks using View 1, the display appears as
follows.

6-4 Performance Tools V4R2

 à ð
Work with System Activity ABSYSTEM
1ð/ð1/98 ð[Link]
Automatic refresh in seconds . . . . . . . . . . . . . . . . . 5
Elapsed time . . . . : ðð:ðð:ð2 Overall CPU util . . : 1.6

Type options, press Enter.

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
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
F3=Exit F1ð=Update list F11=View 2 F12=Cancel F19=Automatic refresh
F24=More keys
á ñ
Figure 6-3. System with Single Processor

| 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 Jobs

While 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 the
Opt column before a list entry, that job or task is selected for monitoring. You may
monitor as many as 20 jobs and tasks at a single time. If five jobs and tasks are
selected for monitoring, the Work with System Activity display appears as follows:

Chapter 6. System Activity 6-5

 à ð
Work with System Activity ABSYSTEM
1ð/ð1/978 ð[Link]
Automatic refresh in seconds . . . . . . . . . . . . . . . . . 5
Elapsed time . . . . : ðð:ðð:ð2 Overall CPU util . . : 1.6

Type options, press Enter.

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
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
F3=Exit F1ð=Update list F11=View 2 F12=Cancel F19=Automatic refresh
F24=More keys
á ñ
Figure 6-4. System with Single Processor

Once you have selected jobs and tasks for monitoring, the Work with System
Activity 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 job
remains in the selected group. To remove a single job or task from the selected
group (as long as it is not the last or only selected entry), blank out the option field
and press the Enter key. This causes a new group to be built from those entries
that still have a 1 in the Opt field.

To return to normal operating mode, press either F13 (Jobs and tasks), F14 (Jobs
only), 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 Jobs

By typing a 5 in the option field next to a job and pressing the Enter key, the Work
with Job (WRKJOB) command is started for that job. Selecting more than one job
before pressing the Enter key causes the WRKJOB command to be started multiple
times.
Note: Option 5 (Work with job) is valid only with jobs. This function cannot be
started for tasks.

Refer to the CL Reference or the Work Management book for further information on
the Work with Job command.

6-6 Performance Tools V4R2

Displaying Different Information Types
As previously mentioned, you can control the type of information being shown on
the 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 jobs
only), or F15 (Display tasks only).

If you specify INFTYPE(*ALL) on the Work with System Activity command or press
F13, statistics for both jobs and tasks are shown. Column headings and function
keys similar to the following appear on the Work with System Activity display:

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 ð
_ SMAIð3 ð .3 ð ð ð
_ ROUTð4 ð .3 ð ð ð
.
.
.
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 Work
with 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 ð
_ DSPð1 QSECOFR ðð8122 2ð 6.4 5 2 ð
.
.
.
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 only
are shown. Column headings and function keys similar to the following appear on
the Work with System Activity display:

Total Total
CPU Sync Async PAG
Opt Task Thread Pty Util I/O I/O Fault
_ SMAIð3 ð .3 ð ð ð
_ ROUTð4 ð .3 ð ð ð
.
.
.
F13=Display jobs and tasks F14=Display jobs only F16=Sequence by I/O
F24=More keys

á ñ

Chapter 6. System Activity 6-7

Accessing Work Management Functions
To assist you in analyzing the performance of the system, function keys F20
through F23 have been set up to provide access to several Work Management
functions. The third set of function keys appears on the Work with System Activity
display 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 the
Work 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 QAITMON

The collected performance data is stored in the file QAITMON located in the library
specified by the LIB parameter on the Work with System Activity command. Each
performance collection, which is stored in a member determined by the MBR
parameter, 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 of
this 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 4096
microseconds.
CPUTOT PACKED(11,0) The total processing unit time used by all tasks and jobs during
the interval, where one unit equals 4096 microseconds. For
multiple-processor systems, this is the average use by all
processors.
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.

6-8 Performance Tools V4R2

 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 4096
microseconds.
CPU21 PACKED(11,0) For multiple-processor systems, the time used in processor two by
jobs and tasks during the interval. One unit of time equals 4096
microseconds.
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 three
by jobs and tasks during the interval. One unit of time equals 4096
microseconds.
CPU41 PACKED(11,0) For multiple-processor systems, the time used in processor four by
jobs and tasks during the interval. One unit of time equals 4096
microseconds.
CPU5–CPU32 PACKED(11,0) For multiple-processor systems, the time used in processor n by
jobs and tasks during the interval. One unit of time equals 4096
microseconds.
| 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, you
can query the QAITMON file after running WRKSYSACT OUTPUT(\FILE) or WRKSYSACT
OUTPUT(\BOTH).

Print Activity Report

The 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 the
Print Activity Report command, one of two report types, or both, are created. The
summary report provides the top 10 listings showing the most CPU-intensive and
the most I/O-intensive entries over the entire specified period. The detailed report
shows a selected number of entries for each interval in the specified period. These
entries are ordered according to a user selected field. Refer to the following
sections for more detail on each of these report types.

Chapter 6. System Activity 6-9

Summary Activity Report
The Summary Activity Report consists of two sections. The first lists (in decreasing
order) 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 total
I/O activity performed during the specified period. The value used for total I/O is
actually the sum of the total synchronous I/O and the total asynchronous I/O. If 10
active jobs or tasks are not present in the specified period, these sections list as
many 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:
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
---------- ---------- ------ --- ---- ----- ----- ----- ----- ----- ------ ------ ----- ----- ------ ------
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 parameter
of the Print Activity Report command.
Member The name of the member in QAITMON that contained the performance
data.
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 collected
the data.

6-10 Performance Tools V4R2

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 the
performance statistics being printed were collected.
Period end date and time The end date and time of the period during which the
performance 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 are
being 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 performance
statistics were first collected.
CPU Util The percentage of the specified period during which the processing unit
was used by the job or task. For a multiple-processor system, this is the
total 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 the
sum of the synchronous database/nondatabase reads and writes.
Total Async I/O The total number of asynchronous physical disk I/O operations
started by the job or task during the specified period. This value is the
sum of the asynchronous database/nondatabase reads and writes.
PAG Fault The number of process access group (PAG) faults caused by the job or
task during the specified period.
Synchronous I/O DB Read The number of synchronous database read operations
performed by the job or task during the specified period.
Synchronous I/O DB Write The number of synchronous database write operations
performed by the job or task during the specified period.
Synchronous I/O Non-DB Read The number of synchronous nondatabase read
operations performed by the job or task during the specified period.
Synchronous I/O Non-DB Write The number of synchronous nondatabase write
operations 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 read
operations started by the job or task during the specified period.
Asynchronous I/O Non-DB Write The number of asynchronous nondatabase write
operations started by the job or task during the specified period.
Note: The asynchronous I/O operations are performed by system asynchronous
I/O tasks.

Chapter 6. System Activity 6-11

Detail Activity Report
For each interval available in the specified period, the Detail Activity Report lists the
performance 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 . . . . . . . . . . . : .ð
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
---------- ---------- ------ --- ---- ----- ----- ----- ----- ----- ------ ------ ----- ----- ------ ------
WRKSYSACT RAMON ð93253 1 .2 ð ð ð ð ð ð ð ð ð ð ð
RMSRVCTKLO ð .ð ð ð ð ð ð ð ð ð ð ð ð
LIDMGR-TAS K--AHT ð .ð ð ð ð ð ð ð ð ð ð ð ð
SMASPTASK ð .ð ð ð ð ð ð ð ð ð ð ð ð
SMASPAGENT TASK ð .ð ð ð ð ð ð ð ð ð ð ð ð
SMCFGVALID ATER ð .ð ð ð ð ð ð ð ð ð ð ð ð
SMCFGUPDAT ER ð .ð ð ð ð ð ð ð ð ð ð ð ð
SMSLSSERVI CETASK ð .ð ð ð ð ð ð ð ð ð ð ð ð
IOPI-HRI-P ERS-IO ð .ð ð ð ð ð ð ð ð ð ð ð ð
XMERRLOGER ð .ð ð ð ð ð ð ð ð ð ð ð ð
Time . . . . : 1ð:56:27 Total 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
---------- ---------- ------ --- ---- ----- ----- ----- ----- ----- ------ ------ ----- ----- ------ ------
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 ð .ð ð ð ð ð ð ð ð ð ð ð ð
SMASPTASK ð .ð ð ð ð ð ð ð ð ð ð ð ð
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 the
summary report, except for the Sequence field, which defines the order of the
entries listed for each interval. The value found in this field corresponds to the
value specified for the sequence (SEQ) parameter on the Print Activity Report
command.

The body of the Detail Activity Report contains the same columns of information
found on the summary report. There are, however, two additional fields associated
with 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 of
processors.

6-12 Performance Tools V4R2

 Chapter 7. Performance Reports—Manager Feature
Performance reports provide a way for you to effectively research areas of the
system that are causing performance problems. After you have collected perform-
ance data over time, different reports offer you ways to see how and where system
resources are used. Performance reports can direct you to specific application pro-
grams, users, or inefficient workloads that are causing lower overall response
times.
| 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 of

the system. For example, one report identifies CPU use and another identifies com-
munications use. These reports help identify various performance problems: if you
get complaints that the user sign-ons are taking longer than they should, you could
use a Transaction Report to find out how many CPU seconds are used by the
sign-on. You could then use a Transition Report to more closely identify how those
CPU 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. See
each specific report example for current report details.

 Copyright IBM Corp. 1998 7-1

Performance Report Header
Each report, regardless of the type or section, contains information in the header of
the report that identifies characteristics of the data:
Report title The first line identifies the type of performance report. The second line
identifies 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. This
name corresponds to the name used on the MBR parameter of the Start
Performance Monitor (STRPFRMON) command.
Library name Is the library where the performance data used in the report is
located.
Model number 4ðð is the model number and 2133 is the feature code of the
AS/400 system on which the performance data was collected for this
report.
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 data
was collected for this report.
Main storage size Is the size of the main storage on the AS/400 system on which
the performance data was collected in this example.
OS/400 version and release level x/ x.ð indicates which version and release
level that the AS/400 system was running.
Data collection start date and time Is the date and time the performance monitor
started collecting performance data in this example. Depending on
whether 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 date
and time is the date and time at which the data was collected.
Ÿ If you specify specific intervals at which to run the report, the start
date and time is the date and time at which the data was collected.
Note: For the system report only, you should consult the Report
Selection Criteria section to find out which intervals were
selected.
Data collection stop date and time Is the date and time the performance monitor
stopped collecting performance data in this example. Depending on
whether or not you select specific intervals or a specific ending time, you
could see the following:
Ÿ If you specify no intervals at which to run the report, the stop date
and time is the date and time at which the data was collected.
Ÿ If you specify specific intervals at which to run the report, the stop
date and time is the date and time at which the data was collected.

7-2 Performance Tools V4R2

 Note: For the system report only, you should consult the Report
Selection Criteria section to find out which intervals were
selected.
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 are
consistent between reports. In this example, IOP Util is one of the
column headings. For short descriptions of these columns, see “Per-
formance Report Columns” on page 7-102.

Available Performance Reports

System 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
Ÿ Report Selection Criteria
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 PRTTNSRPT
command is *SS (special system information). If you leave this
default, 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
Ÿ Report Selection Criteria
Pool Interval Report This report has the following sections:
Ÿ Subsystem Activity
Ÿ Pool Activity
Ÿ Report Selection Criteria
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

7-4 Performance Tools V4R2

 – 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 the
system is operating. It contains summary information on the workload, resource
use, storage pool utilization, disk utilization, and communications. This is a good
report to run and print often, giving you a general idea of system use. You can print
selected sections of this report.

The “Component Report” on page 7-25 supplies you with information about the
same components of system performance as a System Report, but at a greater
level of detail. This report helps you find which jobs are consuming high amounts of
system 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 the
System 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 conflicts
during system operation.

The “Batch Job Trace Report” on page 7-89 shows the progression of different job
types (for example, batch jobs) traced through time.

The “Transaction Report” on page 7-36 provides detailed information about the
transactions that occurred during the performance data collection.

Printing Performance Reports

You 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)

Chapter 7. Performance Reports—Manager Feature 7-5

 Ÿ Print Job Report (PRTJOBRPT)
Ÿ Print Pool Report (PRTPOLRPT)
Ÿ Print Resource Report (PRTRSCRPT)
Ÿ Print Trace Report (PRTTRCRPT)

Using Menus to Print Performance Reports

1. 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 (Print
performance 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 collected
each set of performance data appear on this display. If you cannot find the data
you want to print in a report, use the appropriate function key to sort the sets of
performance data. You can sort them by member name, text description, or by
the date and time the member was created.
3. When you find the performance data, select the type of report you want by
typing 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

ð
Library . . . . . . QPFRDATA

Type option, press Enter.

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

Option Member Text Date Time

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

7-6 Performance Tools V4R2

 Note: When the monitor is running and using one of the members shown in
the Print Performance Report display, this member may appear with
blank Date and Time fields until the first interval is collected.
4. To print a Transaction Report, Lock Report, or Batch Job Trace Report, press
the Enter key and the parameters for the corresponding command appear.
The Select Sections for Report display appears when you select to print the
Job 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 one
of the following reports:
Ÿ System Report
Note: The Select Sections for Report display is shown first, followed by
the Select Categories for Report display.
Ÿ Component Report
Ÿ Job Report
Ÿ Pool Report
Ÿ Resource Report

Chapter 7. Performance Reports—Manager Feature 7-7

 à Select Categories for Report
ð
Member . . . . . . . . . . . : TUEDTA

Type options, press Enter. Press F6 to print entire report.

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 Report
display.
5. To include all categories of information in your report, Press F6. To limit the
amount of information in the report, type a 1 in the Option column next to those
categories of information for which you want performance data. Press the Enter
key.
For example, if you choose the Time interval option, the Select Time Intervals
display appears. This display shows an interactive view of some of the key per-
formance parameters of the data collected. The member name you typed on
the 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

Type options, press Enter.

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

F3=Exit F5=Refresh F12=Cancel

F13=Sort (date/time) F14=Sort (count) F24=More keys

6. Use the Select Time Intervals display to choose specific time intervals from the
performance data to produce a report. You should select specific time intervals
to help you manage the volume of data associated with the performance meas-
urement. The Select Time Intervals display allows you to interactively select the

7-8 Performance Tools V4R2

 time intervals of interest. This selection reduces the amount of processing
required to produce the requested report, and also reduces the size of the
resulting report.
To select time intervals to print on your report, type a 1 in the Opt column next
to 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 in
any 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, a
display appears for each category. For example, if you choose Pool, the Select
or Omit Pools display appears.
7. Use the Select or Omit Pools display to select pools to include or omit from
your report. To use this display, type the number for the pools you want to
select 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

Type options, press Enter.

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 your
report. Or type a 2 if you want certain items omitted from your report.

Chapter 7. Performance Reports—Manager Feature 7-9

 Note: You cannot use both the Select and Omit options at the same time. You
must 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 press
the Enter key.
For each category you choose on the Select Categories for Report display, you
must 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 the
options shown on these displays, the Select Report Options display appears.
Following is an example of the display that appears if you did not use the
Select Time Intervals display to choose any time intervals:

à Specify Report Options

ð
Type choices, press Enter.

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 and
stop date and time, the report includes data from the first (or only) date that
data was collected, to the last (or only) date that data was collected. You may
also type a report title in the Report title field and specify whether or not you
want your report to include the system tasks. Press the Enter key to process
and print your report.
Note: The Omit system tasks field appears only if you requested printing of a
System Report.
If you made use of the Select Time Intervals display, the following version of
the Select Report Options display appears instead:

7-10 Performance Tools V4R2

 à Specify Report Options
ð
Type choices, press Enter.

Report title . . . . _________________________________________________

Omit system tasks . \YES \YES, \NO

If you so choose, type a report title in the Report title field. Also, you can
specify whether or not to include the system tasks in your report. Press the
Enter key to process and print your report.

Using Defaults to Print Performance Reports

The example in this section describes how to collect performance data and print a
System 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
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

Make the choices shown on the following displays to collect performance data and
print a System Report using the system defaults.
1. To start collecting performance data, choose option 2 (Collect performance
data) on the IBM Performance Tools menu, and press the Enter key. The
Collect Performance Data display appears.

à Collect Performance Data

ð
Select one of the following:

1. Start collecting data

2. Stop collecting data
3. Work with performance collection

2. Choose option 1 (Start collecting data).

3. Press the Enter key. The Start Collecting Data display appears.

Chapter 7. Performance Reports—Manager Feature 7-11

 à Start Collecting Data
ð
Select one of the following:

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

Type choices, press Enter.

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 this
example, the performance data is called Thursdata.
7. Type an appropriate description for the performance data you want to collect in
the 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 collected
for 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 to
start Performance Tools.
12. Choose option 3 (Print performance report) on the IBM Performance Tools
menu. The Print Performance Report display appears.

à Print Performance Report

ð
Library . . . . . . QPFRDATA

Type option, press Enter.

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

Option Member Text Date Time

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

7-12 Performance Tools V4R2

13. Type a 1 in the Option column, next to the performance member called
THURSDATA, 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

Type options, press Enter. Press F6 to print entire report.

1=Select

Option Category
_ Time interval
_ Job
_ User ID
_ Subsystem
_ Pool
_ Communications line
_ Control unit
_ Functional area

15. Press F6 to indicate that you do not want to restrict the categories for this
report. The Specify Report Options display appears.

à Specify Report Options

ð
Type choices, press Enter.

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 the
entire 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 on
the 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 it
to an active writer by following steps 18 through 21.

Chapter 7. Performance Reports—Manager Feature 7-13

 à 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
===> WRKSPLF____________________________________________________________
________________________________________________________________________
F3=Exit F4=Prompt F9=Retrieve F12=Cancel F13=Information Assistant
F16=System main menu

á ñ
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

ð
Type options, press Enter.
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 System
Report online.
19. For this example, type a 2 under the Opt column to change the output queue
for the System Report (the QPPTSYSR file). In this example, you might want to
move the report to an output queue that has an active writer, so the report
prints on the device the writer is associated with.
20. Type the new output queue name. To do this, type OUTQ(outqname) on the
command entry line.
21. Press the Enter key. The System Report prints when a device is available.

7-14 Performance Tools V4R2

Why Performance Reports May Seem Inconsistent
Performance Tools pulls data from the various performance monitor database files
to create the performance reports. As a result, some values in the report's columns
are inconsistent between reports where it seems like they should match.

For example, the Communications Summary report (System Report) uses the
QAPMJOBS file. QAPMJOBS file records batch use for jobs that are not related to
communications. As a result, batch use of a line or TCP use does not show up in
the QAPMJOBS file. Because the QAPMJOBS file only shows transactions for jobs,
and the communications line connected to the job is classified as interactive, no
batch use for communications is recorded by the QAPMJOBS file.
Note: The Communications Summary (System Report) only shows interactive
results. Besides this section only takes information from the records which
have 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 the
QAPMCIOP file. This file has field values for the idle loop count and the idle loop
time. These values make up the data that is used to calculate the IOP utilization
value that shows up in this report. The IOP utilization result is just the percentage
of CPU used in the IOP. When the communication IOP utilization shows a value
different 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 the

System report. Client Access jobs show up in the interactive category, but some
Client Access functions show up in batch or evoke categories. In addition, lots of
Client Access activity never become a real job. This can have some effect on trans-
action counting. For example, the Interactive Workload System report section
shows 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 of
transactions for each one. This report pulls data from the QAPMSYS file, where the
performance monitor assigns different classifications of data for the different job
types. The performance monitor code checks for certain attributes and flags on the
system to determine which types they are. For example, Client Access jobs are
identified by a flag. The flag is turned on when a Client Access application sets a
Client Access bit in the work control block (WCB). The performance monitor then
recognizes this job as Client Access and classifies it as such.

As a result, the number of transactions that show up on the Interactive Workload

section differs from the number of transactions that show up on the Communi-
cations Summary System report section. The Communications Summary System
report section only shows the number of interactive transactions on the communi-
cation line over a period of time (which includes Client Access transactions). The
transactions that are unrelated to the communications line do not show up in this
section 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 inconsistencies
between reports.

Chapter 7. Performance Reports—Manager Feature 7-15

| 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 QAPMJOBS Field Values1
| Reports
| SYS CPT TNS JBTYPE JBSTYP JBPTTF JBPTSF JBEAF JBPCSF JBDDMF
| 1 I2 I I I b 0 0 0 0 0

7-16 Performance Tools V4R2

| Table 7-1 (Page 2 of 2). Job Types
| Desc Jobtype Listed in QAPMJOBS Field Values1
| Reports
| 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 D BE B E 1 1 0 0 1
| server5
| 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 A A A b 1 1 0 0 0
| start5
| 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 Report

Print 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 collection
period. 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’ needs
and 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 operational
changes to accommodate changing workloads.

Every System Report includes the Workload, Resource Utilization, and Resource
Utilization Expansion sections. However, the Storage Pool Utilization, Disk Utiliza-

Chapter 7. Performance Reports—Manager Feature 7-17

 tion, and Communications Summary sections are omitted when certain report cate-
gories are selected on the Select Categories for Report display. Table 7-2 on
page 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 Utilization
Disk Utilization
Communications Summary
User ID Storage Pool Utilization
Disk Utilization
Communications Summary
Subsystem Storage Pool Utilization
Disk Utilization
Communications Summary
Pool Disk Utilization
Communications Summary
Communications line Storage Pool Utilization
Disk Utilization
Control unit Storage Pool Utilization
Disk Utilization
Functional area Storage Pool Utilization
Disk Utilization
Communications 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 Report

Columns” on page 7-102.

Workload

Interactive Workload
The 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 Workload
The second part of the Workload section shows the noninteractive workload of the
system.

See the sample report shown in Figure 7-3 on page 7-21.

7-18 Performance Tools V4R2

Resource Utilization
The 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 Expansion

The Resource Utilization Expansion section gives the average resource use per
transaction 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 and
I/O utilization information.

See the sample report shown in Figure 7-7 on page 7-22.

Storage Pool Utilization

Use the Storage Pool Utilization section of the System Report, along with the
guidelines provided in the Work Management book, to help you set the storage
pool size and activity level.

See the sample report shown in Figure 7-8 on page 7-22.

Disk Utilization
The Disk Utilization section of the System Report shows the utilization for each
disk.

See the sample report shown in Figure 7-9 on page 7-23.

Communications Summary
The Communications Summary section of the System Report shows the use of the
communications 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-23
does not correspond with the “Component Report: IOP Utilizations” for an
IOP running SDLC remote work stations. A low SDLC line utilization value
results in a high IOP utilization value due to polling. However, because the
SDLC 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 some
cases, though, especially when the SDLC lines have a low utilization, this
results in an overall decrease in IOP utilization. Thus, a high IOP utilization
value is significant only if at least one of the attached SDLC lines is active.

Chapter 7. Performance Reports—Manager Feature 7-19

 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 the
report must generate. If you use no SELECT Start/End Time/Date, the message No
Select 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 Date
and time of the intervals selected to generate the report. If you use no SELECT
Date/Time Intervals, the message All Intervals were chosen appears.

A sample report is shown in Figure 7-14 on page 7-25.

Report Selection Criteria (Select Parameters)

The Report Selection Criteria section gives the selection values you chose to
produce the report. If you use no SELECT parameters, the message No Select
parameters were chosen appears.

A sample report is shown in Figure 7-11 on page 7-24.

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 Reports

See “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
| Sample System 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
| 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

7-20 Performance Tools V4R2

 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

| System Report 9/15/98 1ð:5ð:4ð
| Resource Utilization Page ððð2
| Sample System 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
| -------------------- 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

| System Report 9/15/98 1ð:5ð:4ð
| Resource Utilization Expansion Page ððð3
| Sample System 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
| -------------------------------------------- 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

Chapter 7. Performance Reports—Manager Feature 7-21

 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

| System Report 9/15/98 1ð:5ð:4ð
| Storage Pool Utilization Page ððð5
| Sample System 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
| ---------- 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

7-22 Performance Tools V4R2

| 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 ð[Link]ð1
| Library . . : PFRRES42 System name . . : ABSYSTEM Version/Release : 4/ 2.ð Stopped . . . . : 11/11/98 ð[Link]
| 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 -- 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-9. Disk Utilization

Communications Summary–Sample
| System Report 5/19/96 12:ð3:48
| Communications Summary Page ððð6
| Sample System Report
| Member . . . : CAJð5ð3 Model/Serial . : 51ð-2144/1ð-ð8BCD Main storage . . : 384.ð M Started . . . . : ð5/ð3/96 [Link]
| 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

Chapter 7. Performance Reports—Manager Feature 7-23

System Report Selection Criteria: Select Parameters–Sample
Report Selection Criteria

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

Report Selection Criteria

Selected Start/End Time/Date:

- No Select Time/Date were chosen.

Selected Date/Time Intervals:

- All Intervals were chosen.

Omit 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 Omit parameters were chosen.

Figure 7-12. Report Selection Criteria: Omit Parameters

7-24 Performance Tools V4R2

Report Selection Criteria: Selected Start/End Time/Date–Sample
Selected Start/End Time/Date:
Start Date/Time: 12/27/95 [Link]
End Date/Time: 12/27/95 [Link]
Selected Date/Time Intervals:

Figure 7-13. Report Selection Criteria: Start/End Time/Date

Report Selection Criteria: Date/Time Intervals–Sample

Selected Start/End Time/Date:
- No Select Time/Date were chosen.
Selected Date/Time Intervals:
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 Report

Use 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 data
you collect with the STRPFRMON command. It expands on the detail for each
component of system performance shown on the System Report. Data is shown for
each sample interval, or in some cases, for each job. Because the report can be
lengthy, you may want to use the Select Time Intervals display when requesting
this report to select only those measurement intervals of interest to you.
Note: The Component Report does not show information for Client Access
devices for the Job Workload Activity, IOP Utilizations, and the Remote
Work Stations – Response Time Buckets sections.

For samples of each section of the Component Report, see “Sample Component
Reports” on page 7-29.

For definitions of specific columns in the reports, see “Performance Report

Columns” on page 7-102.

Component Interval Activity

The Component Interval Activity section of the Component Report gives the use of
the processing unit, disks, and pools at various time intervals.

See the sample report shown in Figure 7-15 on page 7-29.

Chapter 7. Performance Reports—Manager Feature 7-25

Job Workload Activity
The Job Workload Activity section of the Component Report gives the total number
of transactions, the transactions per hour, the average response time, the number
of disk operations, the number of communications operations, the number of PAG
faults, the number of arithmetic overflows, and the number of permanent writes for
each job.

See the sample report shown in Figure 7-16 on page 7-30.

Storage Pool Activity

The 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, specifies
the storage pool identifier (the value can be from 01 through 16). A separate
Storage Pool Activity section exists for each pool that was in use during the meas-
urement period and was selected on the PRTCPTRPT command.

See the sample report shown in Figure 7-17 on page 7-31.

Disk Activity
The Disk Activity section of the Component Report gives the average disk activity
per hour and the disk capacity for each disk.

See the sample report shown in Figure 7-18 on page 7-32.

Input/Output Processor (IOP) Utilizations

The IOP Utilizations section of the Component Report gives the input/output
processor (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 less
throughput.

See the utilization guidelines and thresholds in BEST/1 Capacity Planning Tool
book for a list of threshold values.

See the sample report shown in Figure 7-19 on page 7-33.

Note: The total for the I/O processor utilization oftentimes does not match the sum
of the three columns (IOP Processor Util Comm, IOP Processor Util LWSC,
and IOP Processor Util DASD). This mismatch is caused by the utilization of
other small components, such as system time.

Local Work Stations

The Local Work Stations section of the Component Report gives the utilization of
each controller, the range of response times for each device, and the average
response time for each device.

7-26 Performance Tools V4R2

 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 in
the command.

See the sample report shown in Figure 7-20 on page 7-33.

Remote Work Stations

The Remote Work Stations section of the Component Report gives the range of
response times for each device on the displayed controllers and the average
response 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 in
the command.
Note: This section appears only if 5494 remote work station data is included in the
data collection.

See the sample report shown in Figure 7-21 on page 7-34.

Exception Occurrence Summary and Interval Counts

The Exception Occurrence Summary and Interval Counts section of the Component
Report gives the number of exceptions that occurred and the frequency of these
exceptions.

In some cases these exception counts can be high even under normal system
operation.

See the sample report shown in Figure 7-22 on page 7-34.

Database Journaling Summary

The Database Journaling section of the Component Report provides information
about the journal activity on the system. This information is helpful in understanding
the trade-offs between the following:
Ÿ The affects of extensive journaling.
Ÿ The time required to rebuild access paths during an IPL following an abnormal
system end.
For more information on journaling, see the Backup and Recovery book.

The Database Journaling section summarizes the journaling activity resulting from
user-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 a
user started journaling.
Ÿ The number of journal entry deposits made on behalf of objects for which the
system started journaling.

The report contains the following fields for the number of journal deposits resulting
from system-initiated journaling:

Chapter 7. Performance Reports—Manager Feature 7-27

 Ÿ 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 these
entries into larger bundles to provide more efficient I/O. The number of bundles
written to user-created journals can be compared to the number of bundles written
to 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 access
paths following an abnormal system end.
Ÿ The number of adjustments made by the system to internal journal tuning
tables.
Note: The estimated rebuild time is rounded to the nearest full minute. The
estimate is available only on a system-wide basis, not by auxiliary
storage pool (ASP), even though access path recovery times may be
specified on an ASP basis.
The number of exposed access paths and their estimated rebuild exposure does
not 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 access
paths
These calculated values will be the same if the system access path recovery time
is set to *NONE. These values will also be the same if the system access path
recovery time is set to a time greater than the current estimated exposure.

See the sample report shown in Figure 7-23 on page 7-35.

Report Selection Criteria

The Report Selection Criteria section of the Component Report gives the selection
values 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.

See the sample report shown in Figure 7-24 on page 7-35.

7-28 Performance Tools V4R2

 Sample Component Reports
See “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
| STD I, B, then java/threads
| Member . . . : Q98315ð757 Model/Serial . : 51ð-2144/1ð-16CAD Main storage . . : 512.ð M Started . . . . : 11/11/98 ð[Link]ð1
| Library . . : PFRRES42 System name . . : ABSYSTEM Version/Release : 4/ 2.ð Stopped . . . . : 11/11/98 ð[Link]
| --- 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

Chapter 7. Performance Reports—Manager Feature 7-29

| Component Report 11/11/98 8:2ð:28
| Job Workload Activity Page 2
| STD I, B, then java/threads
| Member . . . : Q98315ð757 Model/Serial . : 51ð-2144/1ð-16CAD Main storage . . : 512.ð M Started . . . . : 11/11/98 ð[Link]ð1
| Library . . : PFRRES42 System name . . : ABSYSTEM Version/Release : 4/ 2.ð Stopped . . . . : 11/11/98 ð[Link]
| 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

7-30 Performance Tools V4R2

 Storage Pool Activity–Sample
| Component Report 11/11/98 8:2ð:28
| Storage Pool Activity Page 15
| STD I, B, then java/threads
| Member . . . : Q98315ð757 Model/Serial . : 51ð-2144/1ð-16CAD Main storage . . : 512.ð M Started . . . . : 11/11/98 ð[Link]ð1
| Library . . : PFRRES42 System name . . : ABSYSTEM Version/Release : 4/ 2.ð Stopped . . . . : 11/11/98 ð[Link]
| 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 .ð ð ð ð ð
| .
| .
| .
| Itv End -- Interval end time (hour and minute)
| 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

Chapter 7. Performance Reports—Manager Feature 7-31

| Component Report 11/11/98 8:2ð:28
| Disk Activity Page 16
| STD I, B, then java/threads
| Member . . . : Q98315ð757 Model/Serial . : 51ð-2144/1ð-16CAD Main storage . . : 512.ð M Started . . . . : 11/11/98 ð[Link]ð1
| Library . . : PFRRES42 System name . . : ABSYSTEM Version/Release : 4/ 2.ð Stopped . . . . : 11/11/98 ð[Link]
| ---------------- 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
| Unit -- Disk arm identifier
| 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
| 1/3 -- Number of seeks between 1/6 and 1/3 of the disk
| 2/3 -- Number of seeks between 1/3 and 2/3 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

7-32 Performance Tools V4R2

| Component Report 9/15/98 1ð:51:38
| IOP Utilizations Page 29
| Sample Component 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
| --- 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

| Component Report 9/15/98 1ð:51:38
| Local Work Stations - Response Time Buckets Page 3ð
| Sample Component 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
| 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
| 2.ð- 4.ð -- Number of response times in this range
| 4.ð- 8.ð -- 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

Chapter 7. Performance Reports—Manager Feature 7-33

 Component Report 9/24/98 [Link]ð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 [Link]
Library . . : RWSDATA System name . . : ABSYSTEM Version/Release : 4/ 2.ð Stopped . . . . : ð9/19/98 [Link]
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
2.ð- 4.ð -- Number of response times in this range
4.ð- 8.ð -- 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

| Component Report 9/15/98 1ð:51:38
| Exception Occurrence Summary and Interval Counts Page 31
| Sample Component 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
| 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

7-34 Performance Tools V4R2

| Component Report 9/15/98 1ð:51:38
| Data Base Journaling Summary Page 34
| Sample Component 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
| ------- 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 ð
| .
| .
| .
| Itv End -- Interval end time (hour and minute)
| 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 [Link]
Library . . : QPFRDATA System name . . : ABSYSTEM Version/Release : 3/ 7.ð Stopped . . . . : ð5/ð3/96 15:ð4:31

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-24. Report Selection Criteria

Chapter 7. Performance Reports—Manager Feature 7-35

Component Report Selection Criteria: Omit Parameters–Sample
Omit 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 Omit parameters were chosen.

Figure 7-25. Report Selection Criteria

Transaction Report

Printing the Transaction Report

Use the PRTTNSRPT command, or select option 3 (Transaction report) on the Print
Performance Reports display. When you use the PRTTNSRPT command, you can
choose 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 you
print these reports, use the selection values available on the PRTTNSRPT
command to select specific jobs, users, or time intervals. That way you can limit the
output 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 is
printed in each numeric field in the report. To see the actual value, you should
specify RPTTYPE(*FILE) on the PRTTNSRPT command.
2. The PRTTNSRPT command takes some CPU model values from the BEST/1
hardware table to do some calculations.

7-36 Performance Tools V4R2

 Collecting Trace Data
To create trace data:
1. Start the performance monitor (use the STRPFRMON command) and specify
tracing (TRACE(*ALL)).
2. When the monitor job completes, print the report. The value for the MBR
parameter on the print command should be the same as the value for the LIB
parameter on the print command.
Note: You can end the performance monitor before the specified interval has
ended by using the End Performance Monitor (ENDPFRMON)
command.

PRTTNSRPT Printer Files

The 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 this
report first.
Ÿ Transaction Report provides detailed information about each 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
Ÿ Transition Report provides information similar to that of the Transaction
Report, but the data (for example, processing unit time, I/O requests) is shown
for each job state transition, rather than just the transitions shown when the job
is waiting for work station input. The detail shown in this report helps you to
determine the program that ran during a transition, or to determine when an
unsatisfied lock request occurred.

For samples of each section of the Transaction Report, see “Sample Transaction
Reports” on page 7-49.

For definitions of specific columns in the reports, see “Performance Report

Columns” on page 7-102.

Chapter 7. Performance Reports—Manager Feature 7-37

Job Summary Report
The Job Summary Report (RPTTYPE(*SUMMARY)) provides the following
sections:
Ÿ 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
Ÿ Report Selection Criteria

Job Summary Section

The 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 disk
I/O activity, high processing unit utilization, or a number of lock requests, use the
Transaction Report to investigate further.

If the number of seizes or number of conflicts (Number Sze Cft or Number Lck
Cft columns on this report) is “high,” look at the Transaction or Transition reports
for the job to see how long the conflict lasted, the job that held the object, the name
and type of object being held, and what the job was waiting for.

The exact meaning of the term “high” is dependent on the application. One
example is the number of lock-waits. An application that has many users
accessing a database at the same time could, under normal conditions, have
numerous 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

7-38 Performance Tools V4R2

analysis will be required. The Transaction and Transition Reports can help in this
analysis.

System Summary Data Section (First Part)

The first part of the System Summary Data section of the Job Summary Report
includes the following:

Ÿ Trace Periods for Trace Date

Ÿ CPU by Priority for All Jobs for Total Trace Period

See the sample report shown in Figure 7-27 on page 7-51.

System Summary Data (Second Part)

The second part of the System Summary Data section of the Job Summary Report
includes the following:
Ÿ CPU and Disk I/O per Job Type for All Jobs for Total Trace Period
Ÿ Interactive Transaction Averages by Job Type

See the sample report shown in Figure 7-28 on page 7-51.

System Summary Data (Third Part)

The Analysis by Interactive Transaction Categories part of the System Summary
Data section provides a breakdown of the transactions into the categories very
simple, simple, medium, and complex, relative to their processing unit utilization.

The boundary values that are used to categorize the transactions by processing
unit model were updated to more accurately reflect a typical customer workload.
The boundary values have almost doubled. For the typical customer workload, this
update causes the number of transactions categorized as simple and medium to
increase, and those categorized as complex and very complex to decrease. This
does not change the data itself or how it is collected. The update only changes how
individual transactions are categorized by the Transaction Report.
Note: The Total/Avg is only a total or average of the simple, medium, and
complex 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’s
transaction characteristics. For example, determine if a high volume of complex
transactions is typical with this new application. By analyzing the transaction char-
acteristics of new applications, you may be able to foresee the need to acquire
additional 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 Data
section provides transaction information sorted by response time categories.

Chapter 7. Performance Reports—Manager Feature 7-39

 The Analysis by Interactive Key/Think Time part of the System Summary Data
section provides information about the key/think time.

See the sample report shown in Figure 7-29 on page 7-52.

Distribution by CPU/Transaction Section

The Distribution of Transactions by CPU/Transaction section of the Job Summary
Report provides a graphical view of the distribution of simple, medium, and complex
transactions. This chart shows the number of transactions versus the processing
unit time per transaction in seconds.

See the sample report shown in Figure 7-30 on page 7-53.

Transaction Significance Section

The Transaction Significance section of the Job Summary Report provides a graph-
ical view of the processing unit use, categorized by simple, medium, and complex
transactions. This chart shows the percent of available processing unit time used
versus the processing unit time per transaction in seconds.

See the sample report shown in Figure 7-31 on page 7-54.

Transactions by Intervals Section

The Interactive Transactions by 5-Minute Intervals section of the Job Summary
Report provides a count of the number of active jobs during a 5-minute interval that
performed at least one transaction. It also shows the number of jobs that were
signed on and off during the 5-minute intervals. Transaction rates per 5-minute
intervals are shown in several different formats.

See the sample report shown in Figure 7-32 on page 7-54.

Interactive Throughput Section

The Interactive Throughput by 5-Minute Intervals section of the Job Summary
Report gives simple, medium, and complex transactions relative to the number of
transactions according to an interval end time.

See the sample report shown in Figure 7-33 on page 7-55.

Interactive CPU Utilization Section

The Interactive CPU Utilization by 5-Minute Intervals section of the Job Summary
Report gives simple, medium, and complex transactions relative to their processing
unit utilization.

See the sample report shown in Figure 7-34 on page 7-55.

Interactive Response Time Section

The Interactive Response Time by 5-Minute Intervals section of the Job Summary
Report gives the response components relative to the resulting response time.

See the sample report shown in Figure 7-35 on page 7-55.

7-40 Performance Tools V4R2

 Scatter Diagram Section
The Scatter Diagram section of the Job Summary Report gives the average of
measured response times for 5-minute intervals compared to transaction rates.

See the sample report shown in Figure 7-36 on page 7-56.

Interactive Program Transaction Statistics Section

The Interactive Program Transaction Statistics section of the Job Summary Report
arranges the programs by the number of transactions associated with the pro-
grams.

See the sample report shown in Figure 7-37 on page 7-57.

Seize/Lock Conflicts by Object Section

The Summary of Seize/Lock Conflicts by Object section of the Job Summary
Report gives information about the locks and seizes associated with objects. The
unnamed 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 of
database file opens and closes.

See the sample report shown in Figure 7-38 on page 7-57.

Special System Information

In general, the information identifies exceptional conditions and events that occur
over the measurement period. If you analyze these exceptions, you might find jobs
and programs you need to examine. A summary of these sections of the Job
Summary 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 Print
Use OPTION(*SS) on the PRTTNSRPT command.

Chapter 7. Performance Reports—Manager Feature 7-41

Priority-Jobtype-Pool Statistics Section
The Priority-Jobtype-Pool Statistics section of the Job Summary Report shows the
total processing unit seconds and physical I/O requests for each category of
priority-jobtype and pool combination recorded during the overall test period. The
number of total transactions is shown for job type I only.

To Print
Use OPTION(*SS) on the PRTTNSRPT command.

See the sample report shown in Figure 7-39 on page 7-58.

Job Statistics Section

The 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 before
program operation can continue.
Ÿ Largest asynchronous disk I/O per transaction.
An asynchronous disk I/O is a disk access operation that is not expected to
complete 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

To Print
Use OPTION(*SS) on the PRTTNSRPT command.

See the sample report shown in Figure 7-40 on page 7-58.

Interactive Program Statistics Section

The 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

7-42 Performance Tools V4R2

 Ÿ Synchronous nondatabase writes per transaction

See the sample report shown in Figure 7-41 on page 7-59.

Individual Transaction Statistics Section

The Individual Transaction Statistics section of the Job Summary Report lists the 10
transactions 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

To Print
Use OPTION(*SS) on the PRTTNSRPT command.

See the sample report shown in Figure 7-42 on page 7-59

Longest Seize/Lock Conflicts Section

The Longest Seize/Lock Conflicts section of the Job Summary Report shows the 30
longest lock or seize conflicts during the trace period.

Chapter 7. Performance Reports—Manager Feature 7-43

 To Print
Use OPTION(*SS) on the PRTTNSRPT command.

See the sample report shown in Figure 7-43 on page 7-60.

Longest Holders of Seize/Lock Conflicts Section

The Longest Holders of Seize/Lock Conflicts section of the Job Summary Report
shows the holders of the longest lock or seize conflicts for all job types during the
trace period.

To Print
Use OPTION(*SS) on the PRTTNSRPT command.

See the sample report shown in Figure 7-44 on page 7-60.

Batch Job Analysis Section

Note: 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 on
the batch job workload during the trace period.

To Print
Use OPTION(*SS) on the PRTTNSRPT command.

See the sample report shown in Figure 7-45 on page 7-60.

Concurrent Batch Job Statistics

The Concurrent Batch Job Statistics section of the Job Summary Report shows
information 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 the
system was fully utilizing all available batch activity levels during the trace period.

The performance monitor begins identifying concurrent jobs when the monitor is
started. All jobs that are currently active are assigned to a job set. There will often
be several jobs that are continuously active during the trace period, such as
autostart jobs for SNADS and the QPFRMON job itself.

If another job starts during the trace period and none of the original jobs have
ended, it is assigned to a new job set. If a job ends and another job of the same
priority 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 3
and you submit 8 jobs to QBATCH during the trace period, there will probably be 3
job 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 first
thread was running for a total of 8 minutes and 50 seconds and the second thread
was running for a total of 6 minutes and 55 seconds, the order of reporting shows
the statistics for the second thread, then the third, and then the first and assigns
them sequential numbers.

7-44 Performance Tools V4R2

 To Print
Use OPTION(*SS) on the PRTTNSRPT command.
Note: The Concurrent Batch Job Statistics section does not print if you also
specify a value on the select job (SLTJOB) parameter or the omit job
(OMTJOB) parameter.

See the sample report shown in Figure 7-46 on page 7-61.

Report Selection Criteria Section

The Report Selection Criteria section of the Job Summary Report gives the
selection values you chose to produce the report.

Use the SELECT parameters on the Report Selection Criteria Report to select
pools, 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.

To Print
Use OPTION(*SS) on the PRTTNSRPT command.

See the sample report shown in Figure 7-47 on page 7-61.

Transaction Report
The Transaction Report (RPTTYPE(*TNSACT)) provides detailed information about
each 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 Print
Use RPTTYPE(*TNSACT) on the PRTTNSRPT command.

See the sample report shown in Figure 7-48 on page 7-62.

Chapter 7. Performance Reports—Manager Feature 7-45

Job Summary Data
The Job Summary Data section of the Transaction Report includes averages of the
job data. Some of this information is also found in the Job Summary section of the
Job Summary Report.

Transition Report
The Transition Report (RPTTYPE(*TRSIT)) provides information similar to that of
the Transaction Report, but the data (for example, processing unit time, I/O
requests) is shown for each job state transition, rather than just the transitions
shown when the job is waiting for work station input. The detail shown in this report
helps you to determine the program that ran during a transition, or to determine
when an unsatisfied lock request occurred.

The Transition Report is composed of two sections:

Ÿ Transition Detail, which shows each state transition made by the job (going
from 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 Print
Use RPTTYPE(*TRSIT) on the PRTTNSRPT command.

See the sample report shown in Figure 7-49 on page 7-62.

Transition Detail
The 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 CALL
QRCVDTAQ), each access to the queue is marked with an EOT2-SOT2 pair. If
data is received by a queue when the data queue currently has no entries, the
transition detail report shows a job state of wait (W in the STATE column), but leaves
the job in the activity level up to a short wait time (2 seconds) or until the interval
time set for the time slice end.

When either the time-out value of the QRCVDTAQ API ends or data is returned
from 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 records
a W<-- and -->A pair under the STATE column for start (W) and completion (A) of
the write or read operation. For example, if the job is doing APPC I/O operations
within an interactive transition with a display device:
Time stamp SOT1
Time stamp W<--
Time stamp -->A
Time stamp W<--
Time stamp -->A
| job processing
Time stamp EOR1
Time stamp EOT1

7-46 Performance Tools V4R2

If the wait code column has an EORn, EOTn, or SOTn, the two program names on
the left are filled in with information from the transaction boundary trace record, and
the 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 job
when the trace record was created. ADR=UNKWN indicates that the program did
not 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 before
dumping the file. The program names are put into the trace record when the
monitor ends and the trace data is put into a database file or when the Dump Trace
(DMPTRC) command is used.

Summary
The summary section of the Transition Report shows the same information as the
summary section of the Transaction Report, described in “Job Summary Data” on
page 7-46.

Table 7-3 on page 7-48 shows jobs with a W← (wait) job state and 130 for a
decimal qualifier. The job went from an active-to-wait state and dropped from the
activity level (this defines the end of a transaction in the report).

Chapter 7. Performance Reports—Manager Feature 7-47

 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 includes
the I/O to write the PAG to disk as well as any other write operations that have occurred since the last
trace entry. You can verify this by comparing it to output from extended trace job by looking at the
WRITES 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 storage
management trace. Each uses a different method to convert to an HH:MM:[Link] value from an 8-byte
hexadecimal clock.

Table 7-4 shows jobs with a W (wait) job state and a decimal qualifier of 134. The
job went from active-to-wait state but stayed in the activity level (for example, a
short wait).

Table 7-4. W Job States and Decimal Qualifiers

State W A I Wait Code Decimal Qualifier Description
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

State W A I Wait Code Decimal Qualifier Description
→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.

7-48 Performance Tools V4R2

 Table 7-6. A Job States and Decimal Qualifiers
State W A I Wait Code Decimal Qualifier Description
A – 142 Wait-to-active but already in the activity
level.
A← – 129 Ineligible-to-active transition.
A – 131 Message received while the task was in
the current MPL.
A – 133 Dequeue after time-out, task in current
MPL when message received.
→A – 135 Job went from wait-to-active state (this
defines the beginning of a transaction in
the report).
A WTO 137 Wait timed out.
A TSE 139 Active-to-active (external time slice end
based on time slice value in class) For
example, a time slice end occurred and
no jobs were waiting for an activity level.
A TSE 145 Active-to-active (internal time slice end
based on time slice value defined on
STRPFRMON).

Sample Transaction Reports

See “Performance Report Columns” on page 7-102 for an alphabetized list con-
taining definitions for each column in the reports.

Job Summary–Sample

Chapter 7. Performance Reports—Manager Feature 7-49

| Job Summary Report 11/11/98 [Link]
| Job Summary Page ððð5
| STD I, B, then java/threads
| Member . . . : Q98315ð757 Model/Serial . : 51ð-2144/1ð-16CAD Main storage . . : 512.ð M Started . . . . :11/11/98 ð[Link]ð
| Library . . : PFRRES42 System name . . : ABSYSTEM Version/Release : 4/ 2.ð Stopped . . . . :11/11/98 ð[Link]
| \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 ðððððð33 ð24875 ð2 BD 2ð .1 .37
| EVENT ðððððð34 ð24875 ð2 BD 2ð .1 .36
| EVENT ðððððð35 ð24875 ð2 BD 2ð .ð6 2
| EVENT ðððððð36 ð24875 ð2 BD 2ð .1 .36

Figure 7-26. Job Summary: Job Summary

System Summary Data (First Part)–Sample

7-50 Performance Tools V4R2

| 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 [Link]
| Library . . : THREAD1 System name . . : ABSYSTEM Version/Release : 4/ 2.ð Stopped . . . . :ð5/22/98 [Link]
| 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

| Job Summary Report 9/ð5/98 14:ð8:5ð
| System Summary Data Page ðð81
| Transaction Report Summary
| Member . . . : Q981421246 Model/Serial . : 5ðð-2142/1ð-18ð3D Main storage . . : 128.ð M Started . . . . :ð5/22/98 [Link]
| Library . . : THREAD1 System name . . : ABSYSTEM Version/Release : 4/ 2.ð Stopped . . . . :ð5/22/98 [Link]
| \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
| 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 .ððð .ððð .ððð

Figure 7-28. Job Summary: System Summary Data - 2

Chapter 7. Performance Reports—Manager Feature 7-51

 System Summary Data (Third Part)–Sample
| Job Summary Report 9/ð5/98 14:ð8:5ð
| System Summary Data Page ðð82
| Transaction Report Summary
| Member . . . : Q981421246 Model/Serial . : 5ðð-2142/1ð-18ð3D Main storage . . : 128.ð M Started . . . . :ð5/22/98 [Link]
| Library . . : THREAD1 System name . . : ABSYSTEM Version/Release : 4/ 2.ð Stopped . . . . :ð5/22/98 [Link]
| 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

Figure 7-29. Job Summary: System Summary Data - 3

Distribution of Simple, Medium, and Complex Processing Unit

Transactions–Sample

7-52 Performance Tools V4R2

| Job Summary Report 9/ð5/98 14:ð8:5ð
| Distribution of Transactions by CPU/Transaction Page ðð83
| Transaction Report Summary
| Member . . . : Q981421246 Model/Serial . : 5ðð-2142/1ð-18ð3D Main storage . . : 128.ð M Started . . . . :ð5/22/98 [Link]
| Library . . : THREAD1 System name . . : ABSYSTEM Version/Release : 4/ 2.ð Stopped . . . . :ð5/22/98 [Link]
| 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

Chapter 7. Performance Reports—Manager Feature 7-53

| Job Summary Report 9/ð5/98 14:ð8:5ð
| Transaction Significance Page ðð84
| Transaction Report Summary
| Member . . . : Q981421246 Model/Serial . : 5ðð-2142/1ð-18ð3D Main storage . . : 128.ð M Started . . . . :ð5/22/98 [Link]
| Library . . : THREAD1 System name . . : ABSYSTEM Version/Release : 4/ 2.ð Stopped . . . . :ð5/22/98 [Link]
| 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

| Job Summary Report 9/ð5/98 14:ð8:5ð
| Interactive Transactions by 5 Minute Intervals Page ðð85
| Transaction Report Summary
| Member . . . : Q981421246 Model/Serial . : 5ðð-2142/1ð-18ð3D Main storage . . : 128.ð M Started . . . . :ð5/22/98 [Link]
| Library . . : THREAD1 System name . . : ABSYSTEM Version/Release : 4/ 2.ð Stopped . . . . :ð5/22/98 [Link]
| --- 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

7-54 Performance Tools V4R2

 Job Summary Report 5/ð7/98 [Link]ð
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 [Link]
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

Job Summary Report 5/ð7/98 [Link]ð
Interactive CPU Utilization by 5 Minute Intervals Page ðð11
Member . . . : CAJð5ð3 Model/Serial . : 51ð-2144/1ð-ð8BCD Main storage . . : 384.ð M Started . . . . : ð5 ð3 98 [Link]
Library . . : QPFRDATA System name . . : ABSYSTEM Version/Release : 4/ 2.ð Stopped . . . . : ð5 ð3 98 15:ð4:36
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

Job Summary Report 5/ð7/968 [Link]ð
Interactive Response Time by 5 Minute Intervals Page ðð12
Member . . . : CAJð5ð3 Model/Serial . : 51ð-2144/1ð-ð8BCD Main storage . . : 384.ð M Started . . . . : ð5 ð3 98 [Link]
Library . . : QPFRDATA System name . . : ABSYSTEM Version/Release : 4/ 2.ð Stopped . . . . : ð5 ð3 98 15:ð4:36
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-Minute

Intervals–Sample

Chapter 7. Performance Reports—Manager Feature 7-55

| Job Summary Report 9/ð5/98 14:ð8:5ð
| Interactive Response Time by 5 Minute Intervals Page ðð88
| Transaction Report Summary
| Member . . . : Q981421246 Model/Serial . : 5ðð-2142/1ð-18ð3D Main storage . . : 128.ð M Started . . . . :ð5/22/98 [Link]
| Library . . : THREAD1 System name . . : ABSYSTEM Version/Release : 4/ 2.ð Stopped . . . . :ð5/22/98 [Link]
| Average Response Time (Seconds)
| Itv
| End ð 1.ðð 2.ðð 3.ðð 4.ðð 5.ðð 6.ðð 7.ðð
| ----- +----+----+----+----+----+----+----+----+----+----+----+----+----+----+
| Response Components:
| R = CPU + Disk + Wait-to-Ineligible
| w = Exceptional Wait
| Job Summary Report 9/ð5/98 14:ð8:5ð
| Scatter Diagram of Interactive Transactions by 5 Minute Intervals Page ðð89
| Transaction Report Summary
| Member . . . : Q981421246 Model/Serial . : 5ðð-2142/1ð-18ð3D Main storage . . : 128.ð M Started . . . . :ð5/22/98 [Link]
| Library . . : THREAD1 System name . . : ABSYSTEM Version/Release : 4/ 2.ð Stopped . . . . :ð5/22/98 [Link]
| 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

7-56 Performance Tools V4R2

 Job Summary Report 5/ð7/98 [Link]ð
Interactive Program Statistics Page ðð19
Member . . . : CAJð5ð3 Model/Serial . : 51ð-2144/1ð-ð8BCD Main storage . . : 384.ð M Started . . . . : ð5 ð3 98 [Link]
Library . . : QPFRDATA System name . . : ABSYSTEM Version/Release : 4/ 2.ð Stopped . . . . : ð5 ð3 98 15:ð4:36

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

Job Summary Report 5/ð7/968 [Link]ð
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 [Link]
Library . . : QPFRDATA System name . . : ABSYSTEM Version/Release : 4/ 2.ð Stopped . . . . :ð5 13 98 [Link]ð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

Chapter 7. Performance Reports—Manager Feature 7-57

 Priority-Jobtype-Pool Statistics–Sample
| Job Summary Report 9/ð5/98 14:ð8:5ð
| Priority-Jobtype-Pool Statistics Page ðð9ð
| Transaction Report Summary
| Member . . . : Q981421246 Model/Serial . : 5ðð-2142/1ð-18ð3D Main storage . . : 128.ð M Started . . . . :ð5/22/98 [Link]
| Library . . : THREAD1 System name . . : ABSYSTEM Version/Release : 4/ 2.ð Stopped . . . . :ð5/22/98 [Link]
| 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 Summary Report 9/ð5/98 14:ð8:5ð
| Job Statistics Page ðð91
| Transaction Report Summary
| Member . . . : Q981421246 Model/Serial . : 5ðð-2142/1ð-18ð3D Main storage . . : 128.ð M Started . . . . :ð5/22/98 [Link]
| Library . . : THREAD1 System name . . : ABSYSTEM Version/Release : 4/ 2.ð Stopped . . . . :ð5/22/98 [Link]
| 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

7-58 Performance Tools V4R2

 Interactive Program Statistics–Sample
Job Summary Report 5/ð7/98 [Link]ð
Interactive Program Statistics Page ðð2ð
Member . . . : CAJð5ð3 Model/Serial . : 51ð-2144/1ð-ð8BCD Main storage . . : 384.ð M Started . . . . : ð5 ð3 98 [Link]
Library . . : QPFRDATA System name . . : ABSYSTEM Version/Release : 4/ 2.ð Stopped . . . . : ð5 ð3 98 15:ð4:36
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

| Job Summary Report 9/ð5/98 14:ð8:5ð
| Individual Transaction Statistics Page ð1ð1
| Transaction Report Summary
| Member . . . : Q981421246 Model/Serial . : 5ðð-2142/1ð-18ð3D Main storage . . : 128.ð M Started . . . . :ð5/22/98 [Link]
| Library . . : THREAD1 System name . . : ABSYSTEM Version/Release : 4/ 2.ð Stopped . . . . :ð5/22/98 [Link]
| TRANSACTIONS WITH LONGEST EXCESSIVE ACTIVITY LEVEL WAIT TIME
| Rank Value Time Program Job Name User Name Number Thread Pool Type Priority
| ---- ------------ ------------ ---------- ---------- ---------- ------ -------- ---- ---- --------
| 1 .ð18 [Link]ð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 [Link] QUIINMGR QPADEVðð26 SOLBERG ð13841 ð4 I 2ð
| 2 6.536 [Link] QUIINMGR QPADEVðð26 SOLBERG ð13841 ð4 I 2ð
| 3 .642 [Link]ð QUIINMGR QPADEVðð26 SOLBERG ð13841 ð4 I 2ð
| 4 .119 12.48.1ð.549 QUIINMGR QPADEVððð9 SUSTAITA ð13832 ð4 I 2ð
| 5 .ð84 [Link] QUIINMGR QPADEVððð9 SUSTAITA ð13832 ð4 I 2ð
| 6 .ð71 12.48.ð6.846 QUIINMGR QPADEVððð9 SUSTAITA ð13832 ð4 I 2ð
| 7 .ð48 [Link] QUIINMGR QPADEVððð9 SUSTAITA ð13832 ð4 I 2ð
| 8 .ð46 [Link] QUIINMGR QPADEVððð9 SUSTAITA ð13832 ð4 I 2ð
| 9 .ð46 [Link] QUIINMGR QPADEVððð9 SUSTAITA ð13832 ð4 I 2ð
| 1ð .ð38 [Link]ð QUIINMGR QPADEVððð9 SUSTAITA ð13832 ð4 I 2ð

Figure 7-42. Job Summary: Individual Transaction Statistics

Longest Seize/Lock Conflicts–Sample

Chapter 7. Performance Reports—Manager Feature 7-59

| Job Summary Report 11/11/98 [Link]
| Longest Seize/Lock Conflicts Page ðð31
| STD I, B, then java/threads
| Member . . . : Q98315ð757 Model/Serial . : 51ð-2144/1ð-16CAD Main storage . . : 512.ð M Started . . . . :11/11/98 ð[Link]ð
| Library . . : PFRRES42 System name . . : ABSYSTEM Version/Release : 4/ 2.ð Stopped . . . . :11/11/98 ð[Link]
| 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ð
| OBJECT- DS PFREXP CSTFIL ððððð1ððð
| 3 14.183 ð8.ð1.16.8ð7 QPADEVðð17 ðððððððD ð23398 ð4 I ð1 L HOLDER- QPADEVðð16 COOK ð23399 ð4 I 2ð
| OBJECT- DS PFREXP CSTFIL ððððð3ððð
| 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ð
| OBJECT- DS PFREXP ITMFIL ððððð2ððð
| 6 .ð22 ð8.ð1.3ð.999 QPADEVðð17 ðððððððD ð23398 ð4 I ð1 L HOLDER- QPADEVðð16 COOK ð23399 ð4 I 2ð
| OBJECT- DS PFREXP ITMFIL ððððð3ððð

Figure 7-43. Job Summary: Longest Seize/Lock Conflicts

Longest Holders of Seize/Lock Conflicts–Sample

| Job Summary Report 11/11/98 [Link]
| Longest Holders of Seize/Lock Conflicts Page ðð32
| STD I, B, then java/threads
| Member . . . : Q98315ð757 Model/Serial . : 51ð-2144/1ð-16CAD Main storage . . : 512.ð M Started . . . . :11/11/98 ð[Link]ð
| Library . . : PFRRES42 System name . . : ABSYSTEM Version/Release : 4/ 2.ð Stopped . . . . :11/11/98 ð[Link]
| 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

| Job Summary Report 9/ð5/98 14:ð8:5ð
| Batch Job Analysis Page ð1ð6
| Transaction Report Summary
| Member . . . : Q981421246 Model/Serial . : 5ðð-2142/1ð-18ð3D Main storage . . : 128.ð M Started . . . . :ð5/22/98 [Link]
| Library . . : THREAD1 System name . . : ABSYSTEM Version/Release : 4/ 2.ð Stopped . . . . :ð5/22/98 [Link]
| 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

7-60 Performance Tools V4R2

| Concurrent Batch Job Statistics–Sample
| Job Summary Report 9/ð5/98 14:ð8:5ð
| Concurrent Batch Job Statistics Page ð1ð8
| Transaction Report Summary
| Member . . . : Q981421246 Model/Serial . : 5ðð-2142/1ð-18ð3D Main storage . . : 128.ð M Started . . . . :ð5/22/98 [Link]
| Library . . : THREAD1 System name . . : ABSYSTEM Version/Release : 4/ 2.ð Stopped . . . . :ð5/22/98 [Link]
| 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

Member . . . : CAJð5ð3 Model/Serial . : 51ð-2144/1ð-ð8BCD Main storage . . : 384.ð M Started . . . . : ð5 ð3 96 [Link]

Library . . : QPFRDATA System name . . : ABSYSTEM Version/Release : 3/ 7.ð Stopped . . . . : ð5 ð3 96 15:ð4:36

Select Parameters

Pools - ð1 ð2 ð3 ð4 ð5 ð6 ð7 ð8 ð9 1ð 11 12 13 14 15 16

Jobs - Jobname1
Jobname2
Jobnum

User IDs - User1 User2 User3 User4 User5 User6

User7 User8 User9 User1ð User11 User12

Functional Areas - Accounting Payroll Research

Development ProjectX MrNolansStaff

- No Select parameters were chosen.

Omit 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

Functional Areas - Accounting Payroll Research

Development ProjectX MrNolansStaff

- No Omit parameters were chosen.

Options Selected - SS Include Special Summary Reports

Figure 7-47. Job Summary Report: Report Selection Criteria

Chapter 7. Performance Reports—Manager Feature 7-61

 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/[Link]
| Page ððð1
| Member . . . :
Q981421246 Model/Serial . : 5ðð-2142/1ð-18ð3D Main storage . . : 128.ð M Started . . . . :ð5/22/98 [Link]
| Library . . :
THREAD1 System name . . : ABSYSTEM Version/Release : 4/ 2.ð Stopped . . . . :ð5/22/98 [Link]
| 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/[Link]ð
| Page ððð1
| Member . . . :
Q981421246 Model/Serial . : 5ðð-2142/1ð-18ð3D Main storage . . : 128.ð M Started . . . . :ð5/22/98 [Link]
| Library . . :
THREAD1 System name . . : ABSYSTEM Version/Release : 4/ 2.ð Stopped . . . . :ð5/22/98 [Link]
| 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
| ------------ ----- ---- ------- ------- ------- -------- ---- ---- ---- ---- ---- -- -- ---------- ---------- ---------- ----------
| [Link] \TRACE ON
| [Link]ð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= ð
| [Link]ð3 /OFF .ðð4 2 PAG= 1 PWrt= ð
| [Link]ð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

7-62 Performance Tools V4R2

Lock Report

Printing the Lock Report

Use the PRTLCKRPT command. The PRTLCKRPT command uses trace output
from the STRPFRMON command, so the STRPFRMON command must be run
first.

Collecting Trace Data

To create the trace data:
1. Start the performance monitor (use the STRPFRMON command) and specify
tracing (TRACE(*ALL)).
2. When the monitor job completes, print the report. The value for the MBR
parameter on the print command should be the same as the value for the LIB
parameter on the print command.
Note: You can end the performance monitor before the specified interval has
ended 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 and
updated 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 list
of the resource management trace records from QAPMDMPT prints first. This list
may be sorted by the times that a lock occurred, the name of the job requesting the
lock, the name of the job holding the lock, or the name of the locked object. The list
may 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 state
transitions in the transaction summary output. If this situation occurs, it could
mean that many jobs are waiting for internal system object locks and holding
an 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

Chapter 7. Performance Reports—Manager Feature 7-63

 not assume that each conflict shown for an object lock is associated with a
separate request for the object from the program that originally requested it.

When multiple requests (from multiple jobs) cause contention for an object, the
requests are processed in the order received, by job priority. When conflicts
occur, multiple lock requests are made by internal programs in behalf of the
program that originally made the request, until the lock is granted. These
internal 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 relate
them to the original request.

What Is the Lock Report?

The Lock Report provides information about lock and seize conflicts during system
operation. With this information you can determine if jobs are being delayed during
processing because of unsatisfied lock requests or internal machine seizes. These
conditions are also called waits. If they are occurring, you can determine which
objects 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 of
day (in this case). The report options were selected to include only locks lasting at
least two seconds that occurred between [Link] and [Link] (as noted in the
footer printed at the bottom of the detail page).

Figure 7-52 on page 7-66 shows a sample of the Requesting Job Summary
section 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 specific

columns in the reports.

Analyzing Seize/Lock Conflicts

Seizes/locks are system-locking functions that ensure integrity during certain oper-
ations. For example, the system uses a seize during logical file maintenance when
the underlying physical files are changed.

Conflicts occur when one job has an object lock or seize and another job requests
control of the same object. A common example of a lock conflict is when a job
reads 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 high
number for either the number of lock or the number of seize conflicts, look at the
Transaction Detail Report and Transition Detail Report to further analyze the situ-

7-64 Performance Tools V4R2

 ation. You can also use the PRTLCKRPT command to print the Seize/Lock Conflict
Report to see what conflicts occurred.

If the PRTTNSRPT command output shows several lock waits, or system

throughput 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 for
files, records, or other objects. Analyze the resource management trace data using
the PRTLCKRPT command to determine a cause.

You can normally expect to see some conflicts occur for a short period of time on
some objects. If you see several lock conflicts occur for nondatabase objects, it
may 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 cause
objectionable delays to end users, this situation could indicate that you need to
make some changes to the operational environment.

If the report shows several database record locks that last for more than 5 to 10
seconds, a program may have read a record for update and continued processing
without 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 reach
the end of its time slice while it holds the lock. When this condition occurs, it delays
other jobs that need the record.

If the report shows several seizes that last for a period of time (over 1 second), this
condition can indicate object contention problems. To ensure the accuracy of the
object, the system does not allow access to the object until all the necessary
changes 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
| Member LOCKDATA Library RWSDATA Period from ðð.ðð.ðð through 23.59.59 ð ms minimum wait

| Figure 7-50. Example of a Detail Listing with Thread Data

Sample Lock Reports

See “Performance Report Columns” on page 7-102 for an alphabetized list con-
taining definitions for each column in the reports.

Chapter 7. Performance Reports—Manager Feature 7-65

 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
| 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
| 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ðð
| 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 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
| 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 [Link] Seize/Lock Wait Statistics Summary Page 1
| Locks Seizes
| Requestor's Job Name Count Avg Length Count Avg Length
| ------------------------------------- ------------- ------------- ------------- -------------
| QPADEVðððC SUSTAITA ð7929ð 4 9ð,394
| QPADEVðð15 SUSTAITA ð79291 4 117,47ð
| QPADEVðð25 SUSTAITA ð79139 4 91,2ð3
| Member LOCKDATA Library RWSDATA Period from ðð.ðð.ðð through 23.59.59 5ðð ms minimum wait
| 9/24/98 [Link] Seize/Lock Wait Statistics Summary Page 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
| 9/24/98 [Link] Seize/Lock Wait Statistics Summary Page 3
| 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ð
| Member LOCKDATA Library RWSDATA Period from ðð.ðð.ðð through 23.59.59 5ðð ms minimum wait

Figure 7-52. Example of Summary by Requesting Job

Job Interval Report

Printing the Job Interval Report

Use the Print Job Report (PRTJOBRPT) command, or select option 5 (Job report)
on the Print Performance Reports display.

7-66 Performance Tools V4R2

What Is the Job Interval Report?
This report, like other similar reports, is produced from the sample data collected
with 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 to
include. For example, you might want to specify OMTSYSTSK(*YES) on the
PRTJOBPRT 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 field
in the report.

The following are sections of the Job Interval Report:

Ÿ Interactive Job Summary
Ÿ Noninteractive Job Summary
Ÿ Interactive Job Detail
Ÿ Noninteractive Job Detail
Ÿ Report Selection Criteria

Interactive Job Summary

The Interactive Job Summary section of the Job Interval Report lists one line for all
selected interactive jobs that existed during each selected interval (a total of one
line per interval).

The information included in this section includes only valid interactive jobs with
CPU activity different than zero, or with any I/O activity.

See the sample report shown in Figure 7-53 on page 7-68.

Noninteractive Job Summary

The Noninteractive Job Summary section of the Job Interval Report lists one line
for all selected noninteractive jobs that existed during each selected interval (a total
of one line per interval).

The information included in this section includes only valid non-interactive jobs with
CPU activity different than zero, or with any I/O activity.

See the sample report shown in Figure 7-54 on page 7-69.

Interactive Job Detail

The 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 that
existed during each selected interval (generally more than one line per interval).

See the sample report shown in Figure 7-55 on page 7-70.

Chapter 7. Performance Reports—Manager Feature 7-67

 Noninteractive Job Detail
The 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 job
that existed during each selected interval (generally more than one line per
interval).

See the sample report shown in Figure 7-56 on page 7-71.

Report Selection Criteria

The Report Selection Criteria section of the Job Interval Report gives the selection
values you chose to produce the report.

See the sample report shown in Figure 7-57 on page 7-72.

Sample Job Interval Reports

See “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 ð
| Itv End -- Interval end time (hour and minute)
| 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
| CPU Util -- Percentage of available CPU time used. This is the average of all processors
| 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

7-68 Performance Tools V4R2

 Noninteractive Job Summary–Sample
| Job Interval Report ð9/15/98 1ð:51:36
| Non-Interactive Job Summary Page 2
| 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 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ð ð
| Itv End -- Interval end time (hour and minute)
| Act Jobs -- Number of jobs that were active during the interval
| CPU Util -- Percentage of available CPU time used. This is the average of all processors
| 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
| PAG Fault -- Number of faults involving the Process Access Group
| Perm Write -- Number of permanent writes
| Arith Ovrflw -- Number of arithmetic overflow exceptions

Figure 7-54. Noninteractive Job Summary Section

Interactive Job Detail–Sample

Chapter 7. Performance Reports—Manager Feature 7-69

| Job Interval Report ð9/15/98 1ð:51:36
| Non-Interactive Job Summary Page 2
| 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 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ð ð
| Itv End -- Interval end time (hour and minute)
| Act Jobs -- Number of jobs that were active during the interval
| CPU Util -- Percentage of available CPU time used. This is the average of all processors
| 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
| PAG Fault -- Number of faults involving the Process Access Group
| Perm Write -- Number of permanent writes
| Arith Ovrflw -- Number of arithmetic overflow exceptions

Figure 7-55. Job Interval Report: Interactive Job Detail Section

Noninteractive Job Detail –Sample

7-70 Performance Tools V4R2

| Job Interval Report ð9/15/98 1ð:51:36
| Non-Interactive Job Detail Page 7
| 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 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 ð26473 2 B 5ð 15:ð2 .5ð ð ð ð 2,413 4,826 163 3
| ðð:31 SNMP_R7D DHQB ð26493 2 B 5ð 15:ð2 .5ð ð ð ð 1,527 2,291 163 3
| ðð:31 SNMP_R7D DHQB ð26511 2 B 5ð 15:ð2 .5ð ð ð ð 4,534 4,534 162 3
| ðð:31 SNMP_R7D DHQB ð26535 2 B 5ð 15:ð2 .4ð ð ð ð 249 4,485 162 3
| ðð:31 SNMP_R7D DHQB ð26555 2 B 5ð 15:ð2 .5ð ð ð ð 1,621 4,863 164 3
| Itv End -- Interval end time (hour and minute)
| 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)
| CPU Util -- Percentage of available CPU time used. This is the average of all processors
| 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
| 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
| 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

Chapter 7. Performance Reports—Manager Feature 7-71

 Job Interval Report 11/19/95 [Link]
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 ð[Link]
Library . . : R21626ð827 System name . . : ABSYSTEM Version/Release . : 3/7.ð Stopped . . . : ð3/21/96 ð9:ð7:15

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-57. Job Interval Report: Select Parameters

Job Interval Report Selection Criteria: Omit Parameters–Sample

Omit 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

nnnnnn 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 Omit parameters were chosen.

Figure 7-58. Job Interval Report: Omit Parameters

Pool Interval Report

7-72 Performance Tools V4R2

Printing the Pool Interval Report
Use 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 pool
activity. 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 to
include.

If a value is too large to fit in the allotted space, a 9 is printed in each numeric field
in the report.
Note: The Pool Report is produced from the sample data collected by the
STRPFRMON command.

For samples of each section of the Pool Report, see “Sample Pool Interval
Reports.”

For definitions of specific columns in the reports, see “Performance Report

Columns” on page 7-102.

Subsystem Activity
The Subsystem Activity section of the Pool Interval Report gives the performance
information on the subsystems during each selected interval. One line is printed for
each subsystem and active pool combination that existed during each selected
interval.

See the sample report shown in Figure 7-59 on page 7-74.

Pool Activity
The 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 each
active pool that existed during each selected interval.

See the sample report shown in Figure 7-60 on page 7-75.

Report Selection Criteria

The Report Selection Criteria section of the Pool Interval Report gives the selection
values you chose to produce the report.

See the sample report shown in Figure 7-61 on page 7-76.

Sample Pool Interval Reports

See “Performance Report Columns” on page 7-102 for an alphabetized list con-
taining definitions for each column in the reports.

Chapter 7. Performance Reports—Manager Feature 7-73

 Subsystem Activity–Sample
| Pool Interval Report ð9/15/98 1ð:52:24
| Subsystem Activity Page 1
| Sample Pool 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
| --------- 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 ð ð
| Itv End -- Interval end time (hour and minute)
| 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

7-74 Performance Tools V4R2

| Pool Interval Report ð9/15/98 1ð:52:24
| Pool Activity Page 12
| Sample Pool 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
| -------- 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 ð ð
| Itv End -- Interval end time (hour and minute)
| 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

Chapter 7. Performance Reports—Manager Feature 7-75

 Pool Interval Report ð5/ð7/96 [Link]ð
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 ð[Link]
Library . . : R21626ð827 System name . . : ABSYSTEM Version/Release . : 3/7.ð Stopped . . . : ð3/21/96 ð9:ð7:15

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.

Omit 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

nnnnnn 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 Omit parameters were chosen.

Figure 7-61. Pool Interval Report: Report Selection Criteria

Resource Interval Report

Printing the Resource Interval Report

Use 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 information
on all or selected intervals. Because the report can be long, you may want to limit
the output by selecting the intervals you want to include.

If a value is too large to fit in the allotted space, a 9 is printed in each numeric field
in the report.

7-76 Performance Tools V4R2

 Sample Data: this report is produced from the sample data collected with the
STRPFRMON command.

Disk Utilization Summary

The Disk Utilization Summary section of the Resource Interval Report gives
detailed disk information by time intervals.

Information is shown for all disk arms that are configured on the system. Also, the
disk arm with the highest utilization and the disk arm with the highest average seek
time for each time interval are shown. Consistent disk arm utilization at or above
the threshold value will affect system performance and cause longer response
times and/or less throughput.

See the sample report shown in Figure 7-62 on page 7-80.

Disk Utilization Detail

The Disk Utilization Detail section of the Resource Interval Report gives detailed
disk 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.

See the sample report shown in Figure 7-63 on page 7-81.

Communications Line Detail

A Communications Line Detail section of a Resource Interval Report contains infor-
mation about the line activity when performance data was collected for the specified
member. One detail section is produced for each protocol in use on the lines for
which data was collected. Figure 7-64 on page 7-82 through Figure 7-70 on
page 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 Protocol
Figure 7-64 on page 7-82 is a sample of the report section for communications
lines using the synchronous data link control (SDLC) protocol. The data in this
example is sorted by the data collection interval end times.

X.25 Protocol
Figure 7-65 on page 7-82 is a sample of the report section for communications
lines using the X.25 protocol.

TRLAN Protocol
Figure 7-66 on page 7-83 is a sample of the report section for communications
lines using the token-ring local area network (TRLAN) protocol.

Chapter 7. Performance Reports—Manager Feature 7-77

 ELAN Protocol
Figure 7-67 on page 7-83 is a sample of the report section for communications
lines using the Ethernet local area network (ELAN) protocol.

DDI Protocol
Figure 7-68 on page 7-84 is a sample of the report section for communications
lines using the distributed data interface (DDI) protocol.

FRLY Protocol
Figure 7-69 on page 7-84 is a sample of the report section for communications
lines using the frame relay (FRLY) protocol.

ASYNC Protocol
Figure 7-70 on page 7-85 is a sample of the report section for communications
lines 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 the
size of the buffer.

BSC Protocol
Figure 7-71 on page 7-85 is a sample of the report section for communications
lines using the binary synchronous communications (BSC) protocol.

ISDN Network Interface

Figure 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 ISDN

Figure 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 Protocol
Figure 7-74 on page 7-87 and Figure 7-75 on page 7-87 are samples of the report
section 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 using
during the interval.

Related Information

Information regarding ISDN can be found in the ISDN Support book.

IOP Utilizations
The IOP Utilizations section of the Resource Interval Report contains a combination
of 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 affects
system performance and causes longer response times and/or less throughput.
Ÿ Multifunction IOP utilizations

7-78 Performance Tools V4R2

 Gives input/output processor (IOP) utilization for DASD, communication, and
local workstation devices. Consistent utilization at or above the threshold value
affects system performance and causes longer response times and/or less
throughput.
Ÿ 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 sum
of the three columns (IOP Processor Util Comm, IOP Processor Util LWSC,
and IOP Processor Util DASD). This mismatch is caused by the utilization of
other small components, such as system time.

Local Work Station Response Times

The local work station response times section provides the following for each data
collection 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

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 in
the command.

See the sample report shown in Figure 7-77 on page 7-89.

Remote Work Station Response Times

The remote work station response times section gives the following for each data
collection interval:
Ÿ Number of work stations active on each controller
Ÿ Range of response times for the work stations
Ÿ Average response time for the work stations

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 in
the command.
Note: This section appears only if a 5494 remote controller is included in the data
collection.

See the sample report shown in Figure 7-78 on page 7-89.

Chapter 7. Performance Reports—Manager Feature 7-79

 Sample Resource Interval Reports
See “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 [Link]ð
| 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
| Itv End -- Interval end time (hour and minute)
| 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

7-80 Performance Tools V4R2

| Resource Interval Report ð9/18/98 14:ð6:ðð
| Disk Utilization Detail Page 2
| 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 [Link]ð
| 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
| Unit -- Disk arm identifier
| IOP Name/ -- Input/Output processor resource name and
| (Model) model number of the attached device
| ASP ID -- Auxiliary storage pool number
| Itv End -- Interval end time (hour and minute)
| 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
| Average Service Time -- Average disk service time per I/O operation
| Average Wait Time -- Average disk wait time per I/O operation

Figure 7-63. Resource Interval Report: Disk Utilization Detail

Communications Line Detail–SDLC Sample

Chapter 7. Performance Reports—Manager Feature 7-81

| Resource Interval Report ð9/18/98 14:ð6:ðð
| Communications Line Detail Page 3
| 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 [Link]ð
| 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

| Resource Interval Report ð9/18/98 14:ð6:ðð
| Communications Line Detail Page 5
| 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 [Link]ð
| 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

7-82 Performance Tools V4R2

| Resource Interval Report ð9/18/98 14:ð6:ðð
| Communications Line Detail Page 7
| 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 [Link]ð
| 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:24 TRNLINE 16ððð.ð .ð ð ð ð ð ð ð ð ð 5 85 ð
| 13:29 TRNLINE 16ððð.ð .ð ð ð ð ð ð ð ð ð 4 83 3
| 13:34 TRNLINE 16ððð.ð .ð ð ð ð ð ð ð ð ð 6 86 ð
| 13:38 TRNLINE 16ððð.ð .ð ð ð ð ð ð ð ð ð 6 86 ð
| CCð7
| (2619)
| 13:14 PMEC1 16ððð.ð .ð 3 3 ð ð ð ð ð ð 1ðð 1ðð ð
| 13:19 PMEC1 16ððð.ð .ð 3 2 ð ð ð ð ð ð 1ðð 1ðð ð
| 13:24 PMEC1 16ððð.ð .ð 1 1 ð ð ð ð ð ð 1ðð 1ðð ð

Figure 7-66. Resource Interval Report: Communications Line Detail - TRLAN

Communications Line Detail–ELAN Sample

| Resource Interval Report ð9/18/98 14:ð6:ðð
| Communications Line Detail 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 [Link]ð
| 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:19 PMET2 1ðððð.ð .ð 2 2 ð ð ð ð ð ð
| 13:24 PMET2 1ðððð.ð .ð 2 1 ð ð ð ð ð ð
| 13:29 PMET2 1ðððð.ð .ð 2 2 ð ð ð ð ð ð
| 13:34 PMET2 1ðððð.ð .ð 1 1 ð ð ð ð ð ð
| 13:38 PMET2 1ðððð.ð .ð ð ð ð ð ð ð ð ð
| CCð5
| (2617)
| 13:14 PMET1 1ðððð.ð .ð 3 3 ð ð ð ð ð ð
| 13:19 PMET1 1ðððð.ð .ð 2 2 ð ð ð ð ð ð
| 13:24 PMET1 1ðððð.ð .ð 1 2 ð ð ð ð ð ð
| 13:29 PMET1 1ðððð.ð .ð 2 2 ð ð ð ð ð ð
| 13:34 PMET1 1ðððð.ð .ð 1 1 ð ð ð ð ð ð
| 13:38 PMET1 1ðððð.ð .ð ð ð ð ð ð ð ð ð

Figure 7-67. Resource Interval Report: Communications Line Detail–ELAN

Chapter 7. Performance Reports—Manager Feature 7-83

 Communications Line Detail–DDI Sample
| Resource Interval Report ð9/18/98 14:ð6:ðð
| Communications Line Detail Page 12
| 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 [Link]ð
| 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ððððð.ð .ð ð ð ð ð ð ð ð ð ð
| 13:24 PMDD1 1ððððð.ð .ð 2 2 ð ð ð ð ð ð ð
| 13:29 PMDD1 1ððððð.ð .ð ð ð ð ð ð ð ð ð ð
| 13:34 PMDD1 1ððððð.ð .ð 1 1 ð ð ð ð ð ð ð
| 13:38 PMDD1 1ððððð.ð .ð ð ð ð ð ð ð ð ð ð
| CCð2
| (2618)
| 13:14 PMDD2 1ððððð.ð .ð 3 3 ð ð ð ð ð ð ð
| 13:19 PMDD2 1ððððð.ð .ð ð ð ð ð ð ð ð ð ð
| 13:24 PMDD2 1ððððð.ð .ð 2 2 ð ð ð ð ð ð ð
| 13:29 PMDD2 1ððððð.ð .ð ð ð ð ð ð ð ð ð ð
| 13:34 PMDD2 1ððððð.ð .ð 1 1 ð ð ð ð ð ð ð
| 13:38 PMDD2 1ððððð.ð .ð ð ð ð ð ð ð ð ð ð

Figure 7-68. Resource Interval Report: Communications Line Detail–DDI

Communications Line Detail–FRLY Sample

| Resource Interval Report ð9/18/98 14:ð6:ðð
| Communications Line Detail Page 14
| 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 [Link]ð
| 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.ð .ð ð ð ð ð ð ð ð ð ð
| 13:19 PMFR1 56.ð .ð ð ð ð ð ð ð ð ð ð
| 13:24 PMFR1 56.ð .ð ð ð ð ð ð ð ð ð ð
| 13:29 PMFR1 56.ð .ð ð ð ð ð ð ð ð ð ð
| 13:34 PMFR1 56.ð .ð ð ð ð ð ð ð ð ð ð
| 13:38 PMFR1 56.ð .ð ð ð ð ð ð ð ð ð ð
| CC11
| (2666)
| 13:14 PMFR2 56.ð .ð ð ð ð ð ð ð ð ð ð
| 13:19 PMFR2 56.ð .ð ð ð ð ð ð ð ð ð ð
| 13:24 PMFR2 56.ð .ð ð ð ð ð ð ð ð ð ð
| 13:29 PMFR2 56.ð .ð ð ð ð ð ð ð ð ð ð
| 13:34 PMFR2 56.ð .ð ð ð ð ð ð ð ð ð ð
| 13:38 PMFR2 56.ð .ð ð ð ð ð ð ð ð ð ð

Figure 7-69. Resource Interval Report: Communications Line Detail–FRLY

Communications Line Detail–ASYNC Sample

7-84 Performance Tools V4R2

| Resource Interval Report ð9/18/98 14:ð6:ðð
| Communications Line Detail Page 16
| 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 [Link]ð
| 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

| Resource Interval Report ð9/18/98 14:ð6:ðð
| Communications Line Detail Page 18
| 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 [Link]ð
| 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

Chapter 7. Performance Reports—Manager Feature 7-85

 Resource Interval Report ð9/23/98 ð[Link]ð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 [Link]
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
Communications Line Detail Page 13
User-Selected Report Title

Member . . . : MONDAY Model/Serial . : 2ðð-2ð5ð/1ð-15ðð5ðð Main storage . . : 16ð.ð M Started . . . : 11/ð2/95 [Link]
Library . . : QPFRDATA System name . . : ABSYSTEM Version/Release . : 3/ 6.ð Stopped . . . : 11/ð2/95 [Link]

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

7-86 Performance Tools V4R2

Communications Line Detail–IDLC Samples
Resource Interval Report ð5/22/96 1ð:29:4ð
Communications Line Detail Page 15
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 [Link]
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ð

Communications Line Detail Page 17
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 [Link]
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

Chapter 7. Performance Reports—Manager Feature 7-87

| Resource Interval Report ð9/15/98 1ð:54:ð2
| IOP Utilizations Page 45
| Sample Resource Interval 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
| 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 Name/ -- Input/Output processor resource name and
| (Model) model number of the attached device
| Itv End -- Interval end time (hour and minute)
| 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

7-88 Performance Tools V4R2

 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 [Link]
Library . . : RWSDATA System name . . : ABSYSTEM Version/Release . : 4/2.ð Stopped . . . : ð9/19/98 [Link]
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
2.ð- 4.ð -- Number of response times between 2.ð and 4.ð seconds
4.ð- 8.ð -- Number of response times between 4.ð and 8.ð 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
| Sample Resource Interval Report
| Member . . . : TEST2ð Model/Serial . : 5ðð-2142/1ð-317CD Main storage . . : 128.ð M Started . . . : ð9/19/98 [Link]
| Library . . : RWSDATA System name . . : ABSYSTEM Version/Release . : 4/2.ð Stopped . . . : ð9/19/98 [Link]
| 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
| 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)
| 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
| 2.ð- 4.ð -- Number of response times between 2.ð and 4.ð seconds
| 4.ð- 8.ð -- Number of response times between 4.ð and 8.ð 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

Chapter 7. Performance Reports—Manager Feature 7-89

 Printing the Batch Job Trace Report
Use the Print Trace Report (PRTTRCRPT) command. Before you print the Batch
Job Trace Report, you must use the Start Performance Monitor (STRPFRMON)
command with the JOBTRCITV and JOBTYPE options and the Print Transaction
Report (PRTTNSRPT) command with the *FILE option. The PRTTNSRPT
command 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 (for
example, batch jobs) traced through time. Resources utilized, exceptions, and state
transitions are reported.

See “Performance Report Columns” on page 7-102 for definitions of specific

columns in the reports.

Job Summary
The Job Summary section of the Batch Job Trace Report gives the number of
traces, the number of I/O operations, the number of seize and lock conflicts, the
number 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 [Link]ð
| 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 [Link]
| Library . . : THREAD1 System name . . : ABSYSTEM Version/Release : 4/ 2.ð Stopped . . . . : ð5/22/98 [Link]
| ---- 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
| CPU Util -- Percentage of available CPU time used. This is the average of all processors
| 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 Files

The 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 and
files to be built in a single run, select specific time ranges and jobs, and limit the

7-90 Performance Tools V4R2

 amount of report and file data produced. If you specify *FILE on the RPTTYPE
parameter of the PRTTNSRPT command, the transaction report creates the files
QTRTSUM, QTRJSUM, and QTRJOBT. If you specify *TRCDTA on the RPTTYPE
parameter of the PRTTNSRPT command, the report creates the file QTRDMPT.

QTRTSUM and QTRJOBT Files

The transaction summary file (QTRTSUM) and job TSE (time slice end)
(QTRJOBT) files have the same format; however, they represent different types of
information.
Ÿ QTRTSUM (transaction summary) file contains one record for every interactive
transaction identified by the PRTTNSRPT command.
Ÿ QTRJOBT (job time slice end) file contains one record per time slice end for all
jobs. Time slice end records are created if the job CPU usage reaches one of
the 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 since
the 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 the
JOBITVTRC 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 of
types and subtypes.

Chapter 7. Performance Reports—Manager Feature 7-91

 Table 7-7 (Page 2 of 4). QTRTSUM File
Field Name Description
TPURGE Purge attribute (Y/N). Defines whether or not the job is eligible to have its PAG purged at
the 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 CPU
time 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 the
WRKSYSACT command or to the JBIPF and JBIOW fields in the QAPMJOBS sample
data 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 occurs
after 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 (in
seconds). This occurs after leaving the activity level at external time slice end because
other 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 slice
ends that caused the job to leave the activity level because there were equal or higher
priority jobs waiting for an activity level.
TAACNT The number of active-to-active (A→A) transitions. The number of external time slice ends
that did not cause the job to leave the activity level because there were no equal or higher
priority jobs waiting for an activity level.

7-92 Performance Tools V4R2

Table 7-7 (Page 3 of 4). QTRTSUM File
Field Name Description
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 and
respond to mount message.
TSWTM Total short wait time (in seconds). Short wait time (SW time in the transaction reports) is
the time spent waiting for an event (such as work station output complete) while remaining
in the active state. When the short wait ends (it ends automatically after 2 seconds), the
job goes into the short wait extended state.
TSWXTM Total short wait extended (short wait time-out) time (in seconds). See field TSWTM. During
the time a job is in short wait extended (abbreviated SWX in the transaction reports), it
does not hold an activity level (it is in the wait state). The short wait is satisfied when the
waited-on event occurs.
TSWXCNT Total number of short waits extended. The number of short waits where the job was taken
out 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 for
seize conflicts.
TLCKTM Total lock conflict wait time (in seconds). Total time this job waited outside the activity
level for lock conflicts.
THOLDTM Total seize/lock conflict hold time to other jobs. The field contains the total time that other
jobs waited for objects held by this job. For example, when a job held an object for 2
seconds and for that time two other jobs waited for the object, the THOLDTM value would
be 4.
TEVTM Total event wait time (in seconds)
TXATM Total excess active time (in seconds). A calculated value, not a measured value, that
represents the time a job was in the activity level, could not use the CPU, and is not
accounted for by other measurements. It can be the result of waiting behind equal or
higher 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)

Chapter 7. Performance Reports—Manager Feature 7-93

 Table 7-7 (Page 4 of 4). QTRTSUM File
Field Name Description
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 of
the 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 File
The job summary file QTRJSUM contains one record for each job or task listed on
the PRTTNSRPT job summary report.

Table 7-8. QTRJSUM File

Field Name Description
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
Refer to explanation of the Typ field in “Job Summary Section” on page 7-38 for a list of
types and subtypes.
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

7-94 Performance Tools V4R2

 The following fields are totals for the duration of the job, unless the beginning or end time selection option was
taken 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, and
save/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)

Chapter 7. Performance Reports—Manager Feature 7-95

QTRDMPT File
The QTRDMPT file is a version of the QAPMDMPT file formatted as a database
file. It gives you access to each performance monitor trace record created. The
QAPMDMPT 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. The
QAPMDMPT file can also be built with the DMPTRC command after the monitor
shuts down.

The field names shown below without asterisks contain information taken directly
from the QAPMDMPT file. Field names shown below with an asterisk (*) in front of
them 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

Field Name Description
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 record
X'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.

7-96 Performance Tools V4R2

Table 7-9 (Page 2 of 4). QTRDMPT File
Field Name Description
DTQUAL Trace qualifier
If DTID = X'68' seize/lock trace (Licensed Internal Code tasks or OS/400 jobs), the trace
qualifiers are:
701 Job/task entered seize conflict wait
1001 Job/task released seize that is being waited on
903 Job entered lock conflict wait
906 Job released lock that is being waited on
If DTID = X'70' MPL trace (OS/400 jobs only), the valid trace qualifiers for active state
codes are:
129 Ineligible-to-active transition
131 Message received and job was in current activity level when the message was
received
133 Dequeue after time-out; job in current activity level when the message was
received
135 Wait-to-active
137 Wait timed out, no message received; wait-to-active
139 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 level
130 Active-to-wait transition; drop from activity level
132 Wait-to-ineligible transition
134 Active-to-wait but stay in activity level
136 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 active
133 Job ended while trace was active
127 Job active at start of trace
136 Job active at end of trace
129 SLIC task started while trace was active
132 SLIC task ended while trace was active
126 SLIC task active at start of trace
135 SLIC task active at end of trace
DTRDAT Transition date YYYYMMDD
DTRTM Transition time HHMMSSmmm
DTRHR Transition hour [Link]
DTRELP Elapsed seconds from previous state
*DPVDAT Previous transition date YYYYMMDD
*DPVTM Previous transition time HHMMSSmmm
*DPVHR Previous transition hour [Link]
DTDEHX TDE number in hexadecimal
DSPOOL Pool number in which job ran
DPRTY Current job priority
DTYPE Job type and subtype.
Refer to explanation of the Typ field in “Job Summary Section” on page 7-38 for a list of
types and subtypes.

Chapter 7. Performance Reports—Manager Feature 7-97

 Table 7-9 (Page 3 of 4). QTRDMPT File
Field Name Description
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)

7-98 Performance Tools V4R2

Table 7-9 (Page 4 of 4). QTRDMPT File
Field Name Description
*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 have
DTID=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 dumped
to the QAPMDMPT file.

DSLOTY Seize/lock object type

Note: Object types and codes can be found in AS/400 Licensed Internal Code Diagnostic
Aids - Volume 1.
DSLOLB Seize/lock object library name (may be undefined for machine objects) A machine object
is a program object that has no defined storage form; the object is defined internally to the
machine.
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 it
was 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'.

Chapter 7. Performance Reports—Manager Feature 7-99

 DTNTY Transaction type (in decimal)
1 Display I/O
2 Data queue
3 MRT
4 Source pass-through
5 Target pass-through
6 WSF target pass-through
DTNSTY Transaction subtype (in decimal)
If DTNTY = 1, 2, or 3:
1 Start transaction
2 End transaction
3 End response time transaction (for DTNTY = 1 only)
IF DTNTY = 4, 5, or 6:
1 Start transaction
2 End transaction
3 Start session
4 End session
DTNBIT Reserved
DTNNM1 Name of display device for display I/O transactions
Name of data queue library for data queue transactions
Name of display device for MRT transactions
Name of device description for pass-through transactions
DTNNM2 Name of display file for display I/O transactions
Name of data queue for data queue transactions
Name of display file for MRT transactions
Name of target control point for source pass-through
transactions
Name of source control point for target pass-through
transactions
Name 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 [Link]
*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 transaction
boundary.
DTNID Reserved
DIPRTY Assigned job priority
| DTHID Thread identifier
| DTHFLG Secondary thread flag (0=primary thread, 1=secondary thread)

7-100 Performance Tools V4R2

 QAPTLCKD File
QAPTLCKD is the file created by using the Print Lock Report (PRTLCKRPT) from
information in the QAPMDMPT trace data file. This file contains data on seizes and
locks. Table 7-10 shows a description of each field in the QAPTLCKD file.

Table 7-10 (Page 1 of 2). QAPTLCKD File

Field Name Description
SLWTOD Time of day ([Link]) 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 job
released the object. This is not necessarily the amount of time that the requesting job is
delayed 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 Code
or implicitly within high-level MI instructions such as Create Object or Add to a File. Locks
occur 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 description
of the system's preassigned addresses.

Chapter 7. Performance Reports—Manager Feature 7-101

 Table 7-10 (Page 2 of 2). QAPTLCKD File
Field Name Description
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-byte
hexadecimal code. If the object name is not meaningful, it is possible that the object
address is one of the system's preassigned addresses. AS/400 Licensed Internal Code
Diagnostic 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 Lock
Report (PRTLCKRPT) command created the QAPTLCKD file on the same system that the
data 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 report
line occurs each time the job has an active-to-wait transaction. Totals
are created for Rsp* (response time), CPU Secs, and I/O counts for the
transaction.
A-I Wait /Tns (Transaction) The average time, in seconds, of active-to-ineligible
wait time per transaction. If this value is high, it may be because the
time-slice value is set too low for many of the interactive jobs. Consider
increasing the time slice-value.
Aborts Recd (Resource Interval) The number of frames received that contained
HDLC abort indicators. This indicates that the remote equipment ended
frames 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 the
Pool Interval Report, the activity level of the pool during the interval. For
the Storage Pool Utilization section of the System Report, the activity
level at the time of the first sample interval.
Act-Inel (System, Component) Average number of active-to-ineligible job state
transitions per minute.
Act-Wait (System, Component) Number of transitions per minute from active state
to wait state by processes assigned to this pool.
Active Devices (System) Average number of active devices on the line.

7-102 Performance Tools V4R2

Active display stations (local or remote) (System) The number of local or remote
display stations entering transactions during the measurement period.
Active Jobs (Transaction) The number of interactive jobs that were active during
the interval.
Active Jobs Per Interval (System) Average number of jobs of this type that were
active per sample interval.
Active K/T /Tns (Transaction) An average think time and keying time (or the delay
time between the end of one transaction and the start of the next trans-
action), in seconds, for the active work stations (described under Est of
AWS). Active K/T /TNS delay time differs from Key/Think /TNS delay
time in that any delay time greater than 600 seconds has been rounded
to 600 seconds. This technique is used to reduce the effect of very
casual users (those who may do intermittent work or leave their work
stations 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) during
transaction processing, while it holds an activity level.
Activity level (System) The sum of activity levels for all interactive pools that had
interactive job activity running in them.
Activity Level Time (Transaction) A breakdown of the transaction time spent
ACTIVE, waiting on a SHORT WAIT, and waiting on a SEIZE/CFT
(seize conflict). The SHORT WAIT and SEIZE CFT time are included
under ACTIVITY LEVEL TIME, because the activity-level slot is not
given up during these times. Note that the seize conflict time is included
in the active time, not added to it to get transaction/response time, as is
the case for waiting time.
Arith Ovrflw (Component, Job Interval) The number of arithmetic overflow
exceptions that occurred for the selected interactive jobs during the
interval.
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 jobs
during the interval. The job that starts the I/O operation may continue
processing without having to wait for the I/O operation to complete. The
I/O operation is completed by a background system test.
Async DIO /Tns (Transaction) The sum of the averages of the asynchronous DB
READ, DB WRITE, NDB READ, and NDB WRITE requests (the average
number of asynchronous I/O requests per transaction for the job).
Async Disk I/O (System, Component, Transaction) Number of asynchronous disk
input/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/O
requests 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.

Chapter 7. Performance Reports—Manager Feature 7-103

 Async I/O Per Second (Job Interval) The average number of asynchronous disk
I/O operations started per second by the selected noninteractive jobs
during the interval.
Async Max (Transaction) Listed under Average DIO/Transaction, the maximum
number of asynchronous DBR, NDBR, and WRT I/O requests encount-
ered for any single transaction by that job. If the job is not an interactive
or 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 the
averages of the asynchronous DBR, NDBR, and WRT requests (the
average number of asynchronous I/O requests per transaction for the
job).
Asynchronous DBR (System, Job Interval, Pool Interval) The average number of
asynchronous database read operations on the disk per transaction for
the job during the intervals. This is calculated by dividing the asynchro-
nous database read count by the transactions processed. This field is
not printed if the jobs in the system did not process any transactions.
For the Resource Utilization section of the System Report, it is the
number 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 asynchronous
database write operations on the disk per transaction for the selected
jobs during the interval. This is calculated by dividing the asynchronous
database write count by the transactions processed. This field is not
printed if the jobs in the system did not process any transactions. For
the Resource Utilization section of the System Report, it is the number
of asynchronous database read operations per second.
Note: The asynchronous I/O operations are performed by system asyn-
chronous I/O tasks.
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 of
asynchronous nondatabase read operations per transaction for the jobs
in 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 any
transactions. For the Resource Utilization section of the System Report,
it is the asynchronous nondatabase read operations per second.
Note: The asynchronous I/O operations are performed by system asyn-
chronous I/O tasks.
Asynchronous NDBW (System, Job Interval, Pool Interval) The average number
of asynchronous nondatabase write operations per transaction for the
jobs 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 process
any transactions. For the Resource Utilization section of the System
Report, it is the number of asynchronous nondatabase write operations
per second.

7-104 Performance Tools V4R2

 Note: The asynchronous I/O operations are performed by system asyn-
chronous I/O tasks.
Aut Lookup (Component) Number of authority lookups per second. An authority
lookup is the process whereby the Licensed Internal Code determines
whether 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 local
storage in the IOP.
Available Storage (Component) Available local storage (in bytes). The average
number of bytes of available main storage in the IOP. The free local
storage is probably not joined because it has broken into small pieces.
Average (Transaction) The average value of the item described in the column for
all 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 program
level 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 auxiliary
storage.
Ÿ 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.

Chapter 7. Performance Reports—Manager Feature 7-105

 Average Phys I/O /Sec (Resource Interval) The average number of physical disk
read and write operations per second made on all disks on the system.
Average Reads/Sec (Resource Interval) The average number of physical disk read
operations per second made on all disks on the system.
Average Response (System) Average response time (in seconds) for interactive
transactions. The Total/Average interactive response time does not
include 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 response
time.
Average Service Time (System) Average disk service time per I/O operation. This
is 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. Normally
due to contention.
Average Writes/Sec (Resource Interval) The average number of physical disk write
operations per second made on all disks on the system.
Avg CPU /Tns (Transaction) The average number of processing unit seconds per
transaction that fell in the given category.
Avg K/T /Tns (Transaction) The average think time and keying time (or the delay
time between transaction boundaries), in seconds, for the interactive
jobs.
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) for
the 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 to
interactive or noninteractive waiters.
Avg Sec Seizes (Transaction) The average length of a seize in seconds attributed
to interactive or noninteractive waiters.
Avg Time per Service (Resource Interval) The amount of time a disk arm uses to
process a given request.
Avg Util (System, Resource Interval) On the Disk Utilization Summary of the
Resource Report, the average percentage of available time that disks
were busy. It is a composite average for all disks on the system. On the
Communications 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 processing
unit seconds used by all batch jobs for each I/O performed by a batch
job.

7-106 Performance Tools V4R2

Batch CPU Utilization (Component) Percentage of available CPU time used by the
following types of jobs:
Ÿ Batch
Ÿ Autostart
Ÿ Evoke
Ÿ SCPF (Start CPF), spool reader/writer
Note: For a multiple-processor system, this is the average use across
all processors.
Batch impact factor (System) Batch workload adjustment for modeling purposes.
Batch permanent writes per second (System) The average number of permanent
write 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 processor
unit 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 on
the ineligible queue (beginning ineligible multiprogramming level) for the
storage pool that the job ran in when the job left the wait state (the
beginning of the transaction).
Note: Multiprogramming level (MPL) is used interchangeably with
activity level.
Bundle Writes System (Component) Number of bundle writes to internal system
journals. A bundle write is a group of journal entries which are deposited
together 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 deposited
together by the system.
Bytes per Second Received (System) Average number of bytes received per
second.
Bytes per Second Transmitted (System) Average number of bytes transmitted per
second.
Bytes Recd per Sec (Resource Interval) The average number of bytes received
per 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 to
separate the transactions are given in the Avg CPU /Tns column. For
the Analysis by Interactive Response Time, they are categorized by their
response time. For the Analysis by Interactive Key/Think Time, they are
categorized by their key/think time.

Chapter 7. Performance Reports—Manager Feature 7-107

 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 Read
Hits (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 a
percent.
Channel (Resource Interval) The B-channel used by the IDLC line. (special condi-
tion)
Cmn (Job Interval) The number of communications I/O operations performed
by 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/O
operations performed per second by the selected noninteractive jobs
during the interval.
Collision Detect (Resource Interval) The number of times that the terminal equip-
ment (TE) detected that its transmitted frame had been corrupted by
another 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 per
transaction.
Communications I/O Put (System) Number of communication put operations per
transaction.
Communications Lines (System, Component, Job Interval, Pool Interval) For the
Report Selection Criteria, the list of communications lines selected to be
included (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 control
units 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 the
column. For example, in a lock report, it is the number of locks or
seizes that occurred.
CPU (Transaction) The total processing unit seconds used by the jobs with a
given priority.
CPU /Tns (Transaction, Job Interval) The amount of available processing unit time
per transaction in seconds.

7-108 Performance Tools V4R2

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/O
operation.
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 the
MAX column heading.
CPU Sec per Tns (Transaction) The processing unit time per transaction.
CPU Seconds (System, Transaction, Component) Average processing unit
seconds used per transaction. For System Summary Data, it is the total
available processing unit time used by the jobs during the trace period.
For Priority-Jobtype-Pool Statistics, it is the total processing unit
seconds used by the jobs with a given combination of priority, job type,
and pool. For Batch Job Analysis, it is the amount of available processor
unit 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 in
the job set in seconds.
CPU seconds per transaction (System) The average processing unit seconds per
transaction.
CPU Util (System, Component, Transaction, Job Interval, Pool Interval, Batch Job
Trace) Percentage of available processing unit time used. For multiple-
processor systems, this is the total utilization divided by the number of
processors.
CPU Util per Transaction (Component) The result of the CPU Utilization divided
by the total number of transactions for the job.
CPU/Async I/O (Job Interval) The average number of milliseconds of processing
unit time taken for each asynchronous disk I/O operation. This is calcu-
lated by dividing the milliseconds of the processing unit time the job
used by the asynchronous disk I/O count.
CPU/Sync I/O (Job Interval) The average number of milliseconds of processing unit
time taken for each synchronous disk I/O operation. This is calculated
from the milliseconds of the processing unit time used by the job divided
by 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 amount
of 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.

Chapter 7. Performance Reports—Manager Feature 7-109

 Ctl (Component) Controller identifier.
Cum CPU Util (Transaction) The cumulative percentage of available processing
unit time used by the transactions that have an average response time
per transaction equal to or less than the given category. For example, in
CPU by Priority for All Jobs for Total Trace Period (System Summary
Data), it is the unit time used by the jobs with a priority higher or equal
to the given priority.
Cum Pct Tns (Transaction) Cumulative CPU percent per transaction. For system
summary data, it is the cumulative CPU percentage of all transactions
that have an average response time per transaction equal to or less
than the given category. For Interactive Program Transactions Statistics,
it is the cumulative CPU percentage of all transactions through the listed
program. For Job Statistics section, it is the cumulative CPU percentage
of total transactions through the listed job. For Interactive Program Sta-
tistics section, it is the cumulative CPU percentage of all transactions
through the listed program.
Cum Util (System) Cumulative CPU use (a running total).
Note: This is taken from the individual jobs and may differ slightly from
the 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 storage
pool.
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 per
second.
DB Read (Transaction) When listed in Physical I/O Counts column, it is the
number of database read requests while the job was in that state. When
listed in the Sync Disk I/O Rqs/Tns column, it is the average number of
synchronous database read requests per transaction.
DB Write (Transaction) When listed in the Sync Disk I/O Rqs/Tns column, it is the
average number of synchronous database write requests per trans-
action.
DB Wrt (Transaction) When listed in the Physical I/O Counts column, it is the
number of database write requests while the job was in that state. When
listed in the Synchronous Disk I/O Counts column, it is the number of
synchronous 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 target
system to respond to a request for data per transaction. This value

7-110 Performance Tools V4R2

 includes line time and time spent by the target system responding to the
request for data.
Dec (Transaction) The number of decimal overflow exceptions.
Decimal Data (Component) Data exception count per second. A data exception
occurs when data that is not valid is detected by arithmetic instructions.
Examples are signs or digit codes that are not valid in decimal
instructions, or an insufficient number of farthest left zeros in multiply
instructions.
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 number
of times the network termination 1 (NT1) end point notified the terminal
equipment (TE) of an error in data crossing the ISDN U interface from
the line transmission termination (LT) to the NT1 end point. The NT1
end point reports the errors to the TE through the maintenance channel
S1.
Detected Access Transmission Error (DTSE) Out (Resource Interval) The
number of times the network termination 1 (NT1) end point notified the
terminal 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 the
errors 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 per
hour:
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
1/3 Number of seeks between 1/6 and 1/3 of the disk
2/3 Number of seeks between 1/3 and 2/3 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.

Chapter 7. Performance Reports—Manager Feature 7-111

 Disk I/O per Second (System) Average number of physical disk I/O operations per
second.
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 bytes
for the entire system.
Disk transfer size (KB) (System) The average number of kilobytes transferred per
disk operation.
Disk utilization (System) The fraction of the time interval that the disk arms were
performing I/O operations.
Elapsed Seconds (Transaction, Component) The elapsed time in seconds. For the
Batch Job Analysis section of the Transaction Report, it is the number of
seconds elapsed from when the job started to when the job ended. For
the Concurrent Batch Job Statistics section of the Transaction Report, it
is the total elapsed time of all jobs in that job set.
Elapsed Time (Job Interval) The amount of time (minutes and seconds) for which
the job existed during the interval. This is the same as the interval
length unless the job started or ended during the interval, in which case
it 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 next
transaction 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 the
end of a transaction (on the transaction totals line), this is the
time the job spent processing the transaction in an activity
level, for long waits caused by locks, and in the ineligible
state.
Inel Wait The time the job spent in the ineligible wait state waiting for
an activity level.
EM3270 Wait /Tns (Transaction) The average, in seconds, of the time spent
waiting on the host system communications for Systems Network Archi-
tecture (SNA) and binary synchronous communications (BSC) 3270DE
per transaction. Program logic is required to determine if the emulation
program 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.

7-112 Performance Tools V4R2

 EORn (Transaction) Listed in the Wait Code column, End of response time for
transaction n. 1
EOTn (Transaction) Listed in the Wait Code column, End of transaction for
transaction for type n. 1
Estimated Exposr AP Not Jrnld (Component) System-estimated access path
recovery time exposure in minutes if no access paths were being jour-
naled by the system.
Estimated Exposr Curr System (Component) System-estimated access path
recovery time exposure in minutes.
Est Of AWS (Transaction) An estimate of the number of active work stations for
the trace period or interval. Any delay time greater than 600 seconds
has been rounded to 600 seconds. This technique is used to reduce the
effect of very casual users (those who may do intermittent work or leave
their work stations for long periods of time) on the estimate of active
work 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-wait
time per transaction.
Often requests made by a job that runs on the system are made to
asynchronous jobs. These asynchronous jobs use an event to signal
completion of the request back to the requester. The event-wait time is
the time the requesting job waits for such a signal.
EVT (Transaction) Listed in the Wait Code column, Event Wait. This is a long
wait that occurs when waiting on a message queue.
Exception Type (Component) Type of program exception that results from the
internal microprogram instructions being run in internal microprogram
instructions procedure. Because these exceptions are monitored at a
low level within the system, it is difficult to associate these exceptions
with specific end-user operations. The counts are meaningful when the
processing unit time required to process them affects system perform-
ance. A variation in the counts may indicate a system change that could
affect performance. For example, a large variation in seize or lock
counts may indicate a job scheduling problem or indicate that contention
exists between an old application and a new one that uses the same
resources.
| 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 more
information see Chapter 8, “Transaction Boundaries—Manager Feature” on page 8-1.

Chapter 7. Performance Reports—Manager Feature 7-113

 Exceptional wait (System) The average exceptional wait time, in seconds, per
transaction. An exceptional wait is that portion of internal response time
that 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 run
STRPFRMON measurements with trace data collection and
compare the measured exceptional wait value, which
PRTTNSRPT provides, with this calculated value. If the values
are 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 as
throughput increases.
Variable The portion of exceptional wait time that varies as
throughput increases.
Excp (Component, Transaction) For the Component Report, it is the total
number 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 had
exceptions. The types of exceptions that are included are process
access group exceptions, and decimal, binary, and floating point over-
flow. See the transition report to see which exceptions the transaction
had.
Excp Wait (Transaction) The amount of exceptional wait time for the jobs in the job
set in seconds.
Excp Wait /Tns (Transaction) The average exceptional wait time, in seconds, per
transaction. 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 seconds
for the job.
Excs ACTM /Tns (Transaction) The average time, in seconds, of the excess
activity level time per transaction (for example, time spent in the active
state but not using the processing unit). If enough activity levels are
available and there is plenty of interactive work of higher priority to do, a
job 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 which
application’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.

7-114 Performance Tools V4R2

 Expert Cache (System, Component) Directs the system to determine which objects
or portions of objects should remain in a shared main storage pool
based on the reference patterns of data within the object. Expert cache