System Performance Feature Reference Volume I

Tivoli® Decision Support for OS/390®

System Performance Feature ReferenceVolume IVersion 1.6

SH19-6819-07

��

Note

Before using this information and the product it supports, read the information in “Notices” on page 935.

Eighth Edition (June 2003)

This edition applies to version 1, release 6 of Tivoli Decision Support for OS/390 (product number 5695-101) and toall subsequent releases and modifications until otherwise indicated in new editions.

This edition replaces SH19-6819-06.

© Copyright International Business Machines Corporation 1993, 2003. All rights reserved.

Note to U.S. Government Users Restricted Rights—Use, duplication or disclosure restricted by GSA ADP ScheduleContract with IBM Corporation.

Contents

Figures . . . . . . . . . . . . . . . v

Preface . . . . . . . . . . . . . . . xiWho Should Read This Book. . . . . . . . . xiWhat This Book Contains . . . . . . . . . . xiPublications . . . . . . . . . . . . . . xiiContacting software support . . . . . . . . xivConventions used in this book . . . . . . . . xvChanges in this edition . . . . . . . . . . xvi

Part 1. Introduction . . . . . . . . . 1

Chapter 1. Implementing the SystemPerformance feature . . . . . . . . . 3Understanding the System Performance feature. . . 3Installing and customizing the System Performancefeature . . . . . . . . . . . . . . . . 7Understanding data flow . . . . . . . . . . 15Understanding log and record definitions . . . . 18Understanding data tables, views, and lookup tables 19Understanding reports. . . . . . . . . . . 22

Part 2. Tivoli Storage Manager(ADSM) component . . . . . . . . 27

Chapter 2. Data tables . . . . . . . . 29ADSM_ACCOUNT_T, _H, _D, _W . . . . . . 29

Chapter 3. Reports . . . . . . . . . 31ADSM report descriptions . . . . . . . . . 32

Part 3. DB2 component . . . . . . 43

Chapter 4. Customization . . . . . . . 45Make input data available . . . . . . . . . 45Review the DRLJCOLL job . . . . . . . . . 45Update lookup tables . . . . . . . . . . . 46

Chapter 5. Data flow . . . . . . . . . 47Lookup tables . . . . . . . . . . . . . 48

Chapter 6. Log and record definitions 49

Chapter 7. Data tables and lookuptables . . . . . . . . . . . . . . . 51Data tables . . . . . . . . . . . . . . 51Lookup tables . . . . . . . . . . . . . 115

Chapter 8. Reports . . . . . . . . . 117DB2 report descriptions . . . . . . . . . . 117

Part 4. DFSMS component . . . . 183

Chapter 9. Customization . . . . . . 185Make input data available . . . . . . . . . 185Modify DRLJCOLL . . . . . . . . . . . 186Update lookup tables. . . . . . . . . . . 186

Chapter 10. Data flow . . . . . . . . 189Lookup tables . . . . . . . . . . . . . 191

Chapter 11. Log and record definitions 193Record procedure . . . . . . . . . . . . 194

Chapter 12. Data tables and lookuptables. . . . . . . . . . . . . . . 195Data tables . . . . . . . . . . . . . . 195Lookup tables . . . . . . . . . . . . . 212

Chapter 13. Reports . . . . . . . . 219DFSMS report descriptions . . . . . . . . . 219

Part 5. DFSMS/RMM component 257

Chapter 14. Customization. . . . . . 259Make input data available . . . . . . . . . 259Modify the collect job . . . . . . . . . . 260Update lookup table . . . . . . . . . . . 261

Chapter 15. Data flow . . . . . . . . 263Lookup table . . . . . . . . . . . . . 263

Chapter 16. Log and recorddefinitions. . . . . . . . . . . . . 265

Chapter 17. Data tables and lookuptable . . . . . . . . . . . . . . . 267Data tables . . . . . . . . . . . . . . 268Lookup table . . . . . . . . . . . . . 275

Chapter 18. Reports . . . . . . . . 277DFRMM report descriptions . . . . . . . . 277

Part 6. MVS component . . . . . . 283

Chapter 19. Customization. . . . . . 287Make input data available . . . . . . . . . 287Review the DRLJCOLL job . . . . . . . . . 287Update lookup tables. . . . . . . . . . . 287

Chapter 20. Data flow . . . . . . . . 293

iii

Lookup tables . . . . . . . . . . . . . 295

Chapter 21. Log and recorddefinitions. . . . . . . . . . . . . 297Record procedures. . . . . . . . . . . . 300

Chapter 22. Data tables, views, andlookup tables . . . . . . . . . . . 303Data tables . . . . . . . . . . . . . . 303Views . . . . . . . . . . . . . . . . 373Lookup tables . . . . . . . . . . . . . 397

Chapter 23. Reports . . . . . . . . 405MVS problem reports. . . . . . . . . . . 408MVS overview reports . . . . . . . . . . 414TSO reports . . . . . . . . . . . . . . 441Summary job reports . . . . . . . . . . . 449Detailed job reports . . . . . . . . . . . 453Program reports . . . . . . . . . . . . 456IPL reports . . . . . . . . . . . . . . 465Processor reports . . . . . . . . . . . . 467Storage reports . . . . . . . . . . . . . 488Paging reports . . . . . . . . . . . . . 510Device reports . . . . . . . . . . . . . 513Printer reports . . . . . . . . . . . . . 527OAM reports . . . . . . . . . . . . . 532OpenEdition reports . . . . . . . . . . . 553

Part 7. MVS AvailabilityComponent . . . . . . . . . . . 561

Chapter 24. Customization. . . . . . 563Make input data available . . . . . . . . . 563Review the DRLJCOLL job . . . . . . . . . 563Update lookup tables. . . . . . . . . . . 563Update AVAILABILITY_PARM table . . . . . 564Update MVS_AVAIL_RESOURCE table. . . . . 565Update MVS_SYSPLEX table . . . . . . . . 565

Chapter 25. Data Flow. . . . . . . . 567Lookup Tables . . . . . . . . . . . . . 567

Chapter 26. Log and recorddefinitions. . . . . . . . . . . . . 569

Chapter 27. Data tables and lookuptables. . . . . . . . . . . . . . . 571Lookup tables . . . . . . . . . . . . . 571

Chapter 28. Reports . . . . . . . . 573MVS availability report descriptions . . . . . . 573

Part 8. MVS performancemanagement component . . . . . 577

Chapter 29. Customization. . . . . . 581Make input data available . . . . . . . . . 581Review the DRLJCOLL job . . . . . . . . . 584Update lookup tables. . . . . . . . . . . 584

Chapter 30. Data flow . . . . . . . . 589Lookup tables . . . . . . . . . . . . . 591

Chapter 31. Log and recorddefinitions. . . . . . . . . . . . . 595Record procedures. . . . . . . . . . . . 599

Chapter 32. Data tables, views, andlookup tables . . . . . . . . . . . 601Data tables . . . . . . . . . . . . . . 601Views . . . . . . . . . . . . . . . . 722Lookup tables . . . . . . . . . . . . . 786MVSPM_DEVICE_ADDR . . . . . . . . . 786MVSPM_TIME_RES . . . . . . . . . . . 787MVSPM_UNIT_TYPE . . . . . . . . . . 788

Chapter 33. Reports . . . . . . . . 789Daily performance overview reports. . . . . . 791Processor and storage resources reports . . . . 803Application use of resources reports . . . . . . 835I/O subsystem performance reports . . . . . . 868OpenEdition performance reports . . . . . . 917

Part 9. Appendixes . . . . . . . . 933

Notices . . . . . . . . . . . . . . 935Trademarks . . . . . . . . . . . . . . 937

List of abbreviations . . . . . . . . 939

Glossary . . . . . . . . . . . . . 945

Index . . . . . . . . . . . . . . . 947

iv Tivoli Decision Support for OS/390: System Performance Feature Reference Volume I

||||||||||||||

||||

|||||

||||

Figures

1. Administration and customization tasks . . . 72. DRLJCOLL job (Part 1 of 2) . . . . . . . 103. DRLJCOLL job (Part 2 of 2) . . . . . . . 114. Tables window . . . . . . . . . . . 125. Tables window edit pull-down . . . . . . 126. Editing a lookup table . . . . . . . . . 137. Daily steps involved in using Tivoli Decision

Support for OS/390 . . . . . . . . . . 148. Organizing and presenting system

performance data . . . . . . . . . . 169. Overview of Tivoli Decision Support for

OS/390 data flow . . . . . . . . . . 1710. Example report description . . . . . . . 2311. Example of an ADSM Session Statistics, Detail

report . . . . . . . . . . . . . . 3212. Example of an ADSM Activities Statistics,

Detail report . . . . . . . . . . . . 3413. Example of an ADSM Data Statistics, Detail

report . . . . . . . . . . . . . . 3614. Example of an ADSM Activities Statistics,

Overview report . . . . . . . . . . . 3815. Example of an ADSM Data Statistics,

Overview report . . . . . . . . . . . 4016. DB2 component data flow . . . . . . . 4717. Lookup table data . . . . . . . . . . 4818. Example of a DB2 Application Response

Times, Detail report . . . . . . . . . 11819. Example of a DB2 Application Response

Times, Overview report . . . . . . . . 12020. Example of a DB2 Application Response

Times, Trend report . . . . . . . . . 12121. Example of a DB2 Transaction Statistics,

Detail report . . . . . . . . . . . . 12222. Example of a DB2 Transaction Statistics,

Overview report . . . . . . . . . . 12523. Example of a DB2 Transaction Statistics,

Trend report . . . . . . . . . . . . 12624. Example of a DB2 System Services Statistics,

Detail report . . . . . . . . . . . . 12725. Example of a DB2 Database Services

Statistics, Detail report . . . . . . . . 12926. Example of a DB2 System Statistics, Overview

report . . . . . . . . . . . . . . 13127. Example of a DB2 System CPU % by Address

Space, Overview report . . . . . . . . 13328. Example of a DB2 System Statistics, Trend

report . . . . . . . . . . . . . . 13529. Example of a DB2 General Measure by

Profile, Overview report . . . . . . . . 13730. Example of a DB2 Application Profiles,

Overview report . . . . . . . . . . 13831. Example of a DB2 Application Profiles, Trend

report . . . . . . . . . . . . . . 14032. Example of a DB2 Buffer Pool Statistics,

Detail report . . . . . . . . . . . . 142

33. Example of a DB2 Buffer Pool Statistics,Overview report . . . . . . . . . . 144

34. Example of a DB2 EDM Pool Statistics, Detailreport . . . . . . . . . . . . . . 146

35. Example of a DB2 EDM Pool Statistics,Overview report . . . . . . . . . . 148

36. Example of a DB2 Buffer Pool Exceptionsreport . . . . . . . . . . . . . . 150

37. Example of a DB2 System Parameters report 15238. Example of a partial DB2 Package report 15539. Example of a DB2 Package report . . . . . 15640. Example of a partial DB2 Buffer Pool report 15741. Example of a partial DB2 Data Sharing

Locking report . . . . . . . . . . . 15942. Example of a DB2 Group Buffer Pool

Accounting, Overview report . . . . . . 16143. Example of a partial DB2 Data Sharing

Locking Accounting report . . . . . . . 16344. Example of a DB2 User Defined Functions,

Detail report . . . . . . . . . . . . 16545. Example of a DB2 User Defined Functions,

Overview report . . . . . . . . . . 16746. Example of a DB2 Triggers, Detail report 16947. Example of a DB2 Triggers, Overview report 17148. Example of a DB2 Row ID, Detail report 17349. Example of a DB2 Row ID, Overview report 17550. Example of a DB2 Secondary Group Buffer

Pool Statistics, Detail report . . . . . . . 17751. Example of a DB2 Application Wait Times,

Detail report . . . . . . . . . . . . 17952. Example of a DB2 Application Wait Times,

Overview report . . . . . . . . . . 18153. Example of a DB2 Application Wait Times,

Trend report . . . . . . . . . . . . 18254. DFSMS component data flow . . . . . . 19055. Lookup table data . . . . . . . . . . 19156. DFSMS record procedure . . . . . . . 19457. Example of a DFSMS Active/Migrat/Backup

Storage, Daily Trend report . . . . . . . 22058. Example of a DFSMS

Allocated/Used/Unused Storage, Daily Trendreport . . . . . . . . . . . . . . 222

59. Example of a DFSMS Backup Storage onDASD/Tape, Daily Trend report . . . . . 224

60. Example of a DFSMS DASD Exceptionsreport . . . . . . . . . . . . . . 226

61. Example of a DFSMS Data Not Migrated butEligible, Daily Trend report . . . . . . . 228

62. Example of a DFSMS Free Space by StorageGroup, Daily Trend report . . . . . . . 229

63. Example of a DFSMS Migration and BackupActivities, Daily Trend report . . . . . . 230

64. Example of a DFSMS Projects Allocating MostDASD report. . . . . . . . . . . . 232

65. Example of a DFSMS Projects Using MostDASD for Backup report . . . . . . . . 233

v

66. Example of a DFSMS Projects Using MostDASD for Migration report . . . . . . . 234

67. Example of a DFSMS Projects Wasting MostDASD report. . . . . . . . . . . . 235

68. Example of a DFSMS Storage Groups MeetingTarget Threshold report . . . . . . . . 237

69. Example of a DFSMS Storage Used forMigration on ML1/ML2 report . . . . . 239

70. Example of a DFSMS Tape forMigration/Backup/Dump, Daily Trend report 241

71. Example of a DFSMS Target/TriggerMigration Values report . . . . . . . . 243

72. Example of a DFSMS Total DASD Usage,Daily Trend report . . . . . . . . . . 245

73. Example of a DFSMS Total Storage Used byManagement Class report . . . . . . . 247

74. Example of a DFSMS Total Storage Used byProject report . . . . . . . . . . . 249

75. Example of a DFSMS Total Storage Used byStorage Class report . . . . . . . . . 251

76. Example of a DFSMS Total Storage Used byStorage Group report . . . . . . . . . 252

77. Example of a DFSMS Volumes not MeetingTarget Threshold report . . . . . . . . 253

78. Example of a DFSMS VTOC Information byVolume report . . . . . . . . . . . 255

79. DRLJCRMM job . . . . . . . . . . 26080. DFSMS/RMM component data flow . . . . 26381. Lookup table data . . . . . . . . . . 26482. Example of a DFRMM Location Statistics,

Detail report . . . . . . . . . . . . 27883. Example of a DFRMM Error Statistics, Detail

report . . . . . . . . . . . . . . 27984. Example of a DFRMM Volumes by Location,

Monthly Trend report . . . . . . . . . 28085. Example of a DFRMM Project Statistics,

Detail report . . . . . . . . . . . . 28186. Example of a DFRMM Space Usage by

Storage Group, Daily Trend report . . . . 28287. MVS component data flow . . . . . . . 29488. Lookup table data . . . . . . . . . . 29589. Record procedures . . . . . . . . . . 30190. Example of an MVS Exceptions, Daily report 40891. Example of an MVS No of System Abends by

Abend Code, Monthly report . . . . . . 40992. Example of an MVS No of User Abends by

Abend Code, Monthly report . . . . . . 41093. Example of an MVS Percent Abended Jobs by

User Group, Monthly report . . . . . . 41194. Example of an MVS No of Canceled Batch

Jobs by User Group, Daily report . . . . . 41295. Example of an MVS Abended Jobs by User

Group, Daily report . . . . . . . . . 41396. Example of an MVS System Overview,

Monthly Trend report . . . . . . . . . 41597. Example of an MVS Average No of Address

Spaces, Monthly Trend report . . . . . . 41798. Example of an MVS Activity by User Group,

Daily Overview report . . . . . . . . 41899. Example of an MVS Activity for a User

Group, Daily Trend report . . . . . . . 419

100. Example of an MVS Users Swapped Out andReady, Daily Profile report . . . . . . . 420

101. Example of an MVS Workload by WorkloadType, Monthly Trend report . . . . . . . 421

102. Example of an MVS Sysplex Overview,Monthly Trend report . . . . . . . . . 423

103. Example of an MVS Availability by Sysplex,Monthly Trend report . . . . . . . . . 424

104. Example of an MVS Workload for a ResourceGroup, Daily Trend report . . . . . . . 426

105. Example of an MVS Workload by ResourceGroup, Daily Overview report . . . . . . 428

106. Example of an MVS Response (Goal in %),Daily Trend report . . . . . . . . . . 430

107. Example of an MVS Response (Goal in %),Daily Overview report . . . . . . . . 432

108. Example of an MVS Response (Goal in sec),Daily Trend report . . . . . . . . . . 434

109. Example of an MVS Response (Goal in sec),Daily Overview report . . . . . . . . 435

110. Example of an MVS Exec Velocity (Goal in%), Daily Trend report . . . . . . . . 436

111. Example of an MVS Exec Velocity (Goal in%), Daily Overview report . . . . . . . 437

112. Example of an MVS Response TimeDistribution, Daily Overview report . . . . 440

113. Example of an MVS TSO Response Time byWorkload, Daily Profile report . . . . . . 441

114. Example of an MVS TSO Response Time byWorkload, Daily Trend report . . . . . . 443

115. Example of an MVS TSO Response Time,Peak Hour, Daily Trend report . . . . . . 444

116. Example of an MVS Number of TSO Users,Daily Profile report . . . . . . . . . 445

117. Example of an MVS TSO Transactions byWorkload, Daily Profile report . . . . . . 446

118. Example of an MVS TSO Transactions byWorkload, Daily Trend report . . . . . . 447

119. Example of an MVS TSO Transactions, PeakHour, Daily Trend report. . . . . . . . 448

120. Example of an MVS Job Statistics by UserGroup, Monthly Overview report . . . . . 449

121. Example of an MVS Job Statistics for a UserGroup, Daily Trend report . . . . . . . 450

122. Example of an MVS Number of Jobs withTape Mounts, Daily Trend report . . . . . 451

123. Example of an MVS Job Statistics by Periodand User Group, Daily report . . . . . . 452

124. Example of an MVS Jobs with RACF S913Abends, Daily report . . . . . . . . . 453

125. Example of an MVS Jobs with Input QueueTime > 10 Min, Daily report . . . . . . 454

126. Example of an MVS Jobs with Tape, Dailyreport . . . . . . . . . . . . . . 455

127. Example of an MVS Most CPU ConsumingPrograms, Monthly Overview report . . . . 456

128. Example of an MVS Most I/O IntensivePrograms, Monthly Overview report . . . . 458

129. Example of an MVS Most CPU LosingPrograms, Monthly Overview report . . . . 460

vi Tivoli Decision Support for OS/390: System Performance Feature Reference Volume I

||

130. Example of an MVS CPU Usage by JobAccount Field, Daily report . . . . . . . 461

131. Example of part of an MVS Interval AccountStatistics, Detail report . . . . . . . . 463

132. Example of an MVS Number of IPLs, DailyTrend report . . . . . . . . . . . . 465

133. Example of an MVS IPLs by Reason Code,Daily report . . . . . . . . . . . . 466

134. Example of an MVS CPU Load by Period,Monthly Trend report . . . . . . . . . 467

135. Example of an MVS CPU Load by WorkloadType, Monthly Trend report . . . . . . . 470

136. Example of an MVS CPU Load by WorkloadType, Peak Hour, Daily report . . . . . . 471

137. Example of an MVS CPU Load by WorkloadType, Daily Profile report . . . . . . . 473

138. Example of an MVS Average and MaximumCPU Load, Daily Profile report . . . . . 474

139. Example of MVS MIPS for System ID HourlyList . . . . . . . . . . . . . . . 478

140. Example of MVS MIPS for System ID List -Daily Trend . . . . . . . . . . . . 480

141. Example of MVS MIPS for System ID List -Monthly Trend . . . . . . . . . . . 482

142. Example of MVS CPU Load by LPAR,Monthly Trend per MIPS. . . . . . . . 484

143. Example of MVS CPU Load by LPAR, DailyTrend per MIPS . . . . . . . . . . . 486

144. Example of an MVS Available CS, inMegabytes, Daily Profile report . . . . . 489

145. Example of an MVS CS by Workload Type,Peak Hour, Daily Trend report . . . . . . 490

146. Example of an MVS ES by Workload Type,Peak Hour, Daily Trend report . . . . . . 492

147. Example of an MVS Storage by WorkloadType, Peak Hour, Daily report . . . . . . 494

148. Example of an MVS CS by Workload Type,Monthly Trend report . . . . . . . . . 496

149. Example of MVS Paging by Subsystem, DailyTrend . . . . . . . . . . . . . . 510

150. Example of an MVS Paging Rates, DailyTrend report . . . . . . . . . . . . 512

151. Example of an MVS DASD I/O by UserGroup, Monthly Overview report . . . . . 513

152. Example of an MVS I/O Rates by UserGroup, Peak Hour, Daily report . . . . . 514

153. Example of an MVS Tape I/O by User Group,Monthly Overview report . . . . . . . 515

154. Example of an MVS Tape Demounts/MVSSystem, Monthly Overview report . . . . 516

155. Example of an MVS Tape Errors by Device,Monthly Overview report . . . . . . . 517

156. Example of an MVS Tape Errors by Volume,Monthly Overview report . . . . . . . 518

157. Example of an MVS MAGSTAR VTSConfiguration report . . . . . . . . . 519

158. Example of an MVS MAGSTAR VTS PhysicalDrive Mount Daily report . . . . . . . 521

159. Example of an MVS MAGSTAR VTS VirtualDrive Mount Daily report . . . . . . . 523

160. Example of an MVS MAGSTAR VTSUtilization Daily report . . . . . . . . 525

161. Example of an MVS Printer Activity, MonthlyOverview report . . . . . . . . . . 527

162. Example of an MVS Print Activity by UserGroup, Monthly Overview report . . . . . 529

163. Example of an MVS Printer Forms Usage,Monthly Overview report . . . . . . . 531

164. Example of an OSREQ Function InvocationStatistics, Detail report . . . . . . . . 532

165. Example of an OAM/OSMC ActivitiesStatistics, Daily report. . . . . . . . . 534

166. Example of an OAM/OSMC ActivitiesStatistics, Monthly report . . . . . . . 538

167. Example of a LCS Opt Disk Volume R/W/DStatistics, Detail report . . . . . . . . 541

168. Example of an LCS Opt Disk Volume R/W/DStatistics, Daily report. . . . . . . . . 543

169. Example of an LCS Optical R/W/LogD/Phys D Reqs, Daily report . . . . . . 545

170. Example of an LCS Optical R/W/LogD/Phys D Reqs, Monthly report . . . . . 546

171. Example of an LCS Tape R/W/Log DRequests, Daily report . . . . . . . . 547

172. Example of an LCS Tape R/W/Log DRequests, Monthly report . . . . . . . 548

173. Example of an OAM Tape Vol R/W Stats atDemount, Daily report . . . . . . . . 549

174. Example of an OAM Tape Vol R/W Stats atDemount, Monthly report . . . . . . . 551

175. Example of an MVS OpenEdition CPU Usageby Group, Daily report . . . . . . . . 553

176. Example of an MVS OpenEdition I/OActivity by Group, Daily report . . . . . 554

177. Example of an MVS OpenEdition File SystemLookups by Group, Daily report . . . . . 556

178. Example of an MVS OpenEdition ChildProcess Listing for Job report . . . . . . 558

179. MVS availability component data flow 567180. Lookup table data . . . . . . . . . . 568181. Example of an MVS Availability not within

Target, Daily Trend report . . . . . . . 573182. Example of an MVS Availability, Daily Trend

report . . . . . . . . . . . . . . 574183. Example of an MVS Availability for a Sysplex,

Daily Trend report . . . . . . . . . . 575184. MVS performance management component

data flow . . . . . . . . . . . . . 590185. Lookup table data . . . . . . . . . . 593186. Record procedures . . . . . . . . . . 599187. Example of an MVSPM Workload

Descriptions report. . . . . . . . . . 791188. Example of an MVSPM Goal mode Workload

Descriptions report. . . . . . . . . . 792189. Example of an MVSPM CPU and Processor

Storage Activity Overview report . . . . . 793190. Example of an MVSPM Workload Resource

Utilization Overview report . . . . . . . 795191. Example of an MVSPM Workload Response

Time Components Overview report . . . . 797

Figures vii

|||||||||||||||

|||||||||||||

192. Example of an MVSPM Response Time Goalsvs Actuals Overview report . . . . . . . 799

193. Example of an MVSPM Execution VelocityGoals & Actuals Overview report . . . . . 800

194. Example of an MVSPM DASD ActivityOverview report . . . . . . . . . . 801

195. Example of an MVSPM Average CPU Busy,Hourly Trend report . . . . . . . . . 803

196. Example of an MVSPM Average CPU BusyProfile, Hourly Trend report . . . . . . 805

197. Example of an MVSPM CPU Busy and OtherIndicators, Hourly Trend report . . . . . 806

198. Example of an MVSPM System CentralStorage Map, Hourly Trend report . . . . 808

199. Example of an MVSPM System ExpandedStorage Map, Hourly Trend report . . . . 810

200. Example of an MVSPM Minimum AvailableExp Storage, Hourly Trend report . . . . . 812

201. Example of an MVSPM Average High UICProfile, Hourly Trend report . . . . . . 813

202. Example of an MVSPM Page Data SetResponse Time, Hourly Trend report . . . . 814

203. Example of an MVSPM Page Data Set DeviceResp Time, Hourly Trend report . . . . . 815

204. Example of an MVSPM Page Data Set BusyTime, Hourly Trend report . . . . . . . 816

205. Example of an MVSPM System StoragePaging Rates, Hourly Trend report . . . . 817

206. Example of an MVSPM CPU Busy ProfileShared LPARs, Hourly Trend report . . . . 818

207. Example of an MVSPM CPU Busy by SharedLPARs, Hourly Trend report . . . . . . 819

208. Example of an MVSPM Percent of Share Usedby LPARs, Hourly Trend report . . . . . 820

209. Example of an MVSPM LPAR ManagementTime, Hourly Trend report . . . . . . . 821

210. Example of an MVSPM Avg CF Busy Profile,Hourly Trend report . . . . . . . . . 822

211. Example of an MVSPM Avg CF StorageUsage, Hourly Trend report . . . . . . . 823

212. Example of an MVSPM CF, Processor andStorage, Overview report . . . . . . . 824

213. Example of an MVSPM CF, Request Rate,Overview report . . . . . . . . . . 826

214. Example of an MVSPM CF, System Details,Overview report . . . . . . . . . . 827

215. MVSPM CF, Structures Details, OverviewReport . . . . . . . . . . . . . . 829

216. Example of MVSPM MIPS for Machine ModelList . . . . . . . . . . . . . . . 831

217. Example of MVSPM MIPS for specific SystemID . . . . . . . . . . . . . . . 832

218. Example of MVSPM MIPS for System IDHourly List . . . . . . . . . . . . 833

219. Example of MVSPM Total CPU MIPS perLPAR and System . . . . . . . . . . 834

220. Example of an MVSPM System Resources byWorkload Type report. . . . . . . . . 835

221. Example of an MVSPM CPU Busy byWorkload Types, Hourly Trend report . . . 837

222. Example of an MVSPM CPU Busy byWorkload PGNs, Hourly Trend report . . . 838

223. Example of an MVSPM Storage Used byWorkload Type, Hourly Trend report. . . . 839

224. Example of an MVSPM Storage Used byWorkload PGNs, Hourly Trend report . . . 840

225. Example of an MVSPM I/O Rate byWorkload Types, Hourly Trend report . . . 841

226. Example of an MVSPM CPU per I/O byWorkload Type, Hourly Trend report. . . . 842

227. Example of an MVSPM CPU per I/O byWorkload PGNs, Hourly Trend report . . . 843

228. Example of an MVSPM Page-ins by WorkloadTypes, Hourly Trend report . . . . . . . 844

229. Example of an MVSPM Paging Activity byWorkload, Hourly Trend report . . . . . 845

230. Example of an MVSPM Resp Time byWorkload Types, Hourly Trend report . . . 847

231. Example of an MVSPM Workload Resp TimeComponents, Hourly trend report. . . . . 848

232. Example of an MVSPM BMF Member PageReads/Hits, Hourly Trend report . . . . . 850

233. Example of an MVSPM BMF Directory PageReads/Hits, Hourly Trend report . . . . . 851

234. Example of an MVSPM APPC, CPU and I/Oby Transaction Class report . . . . . . . 852

235. Example of an MVSPM APPC, Execution andQueueing, Hourly Trend report . . . . . 853

236. Example of an MVSPM VLF Usage and HitRatio, Hourly Trend report . . . . . . . 854

237. Example of an MVSPM VLF DataspaceUsage, Hourly Trend report . . . . . . . 856

238. Example of an MVSPM Applications Waitingon ENQs, Hourly Trend report. . . . . . 858

239. Example of an MVSPM Applications Waitingon ENQs, Worst Case report . . . . . . 859

240. Example of an MVSPM Response Time Goals& Actuals, Hourly Trend report . . . . . 860

241. Example of an MVSPM Response TimeDistribution report . . . . . . . . . . 862

242. Example of an MVSPM Served ServiceClasses Overview report . . . . . . . . 863

243. Example of an MVSPM Response TimeBreakdown Overview report . . . . . . 864

244. Example of an MVSPM Response TimeBreakdown, Hourly Trend report . . . . . 866

245. Example of an MVSPM Channel Path Busyreport . . . . . . . . . . . . . . 868

246. Example of an MVSPM I/O Rate for LCUs,Hourly Trend report . . . . . . . . . 870

247. Example of an MVSPM I/O Response Timefor LCUs, Hourly Trend report. . . . . . 871

248. Example of an MVSPM I/O Response TimeComponents for LCUs report . . . . . . 872

249. Example of an MVSPM No of Users Waitingfor Device, Daily Trend report . . . . . . 874

250. Example of an MVSPM I/O Response TimeComponents, DASD Devices report . . . . 875

251. Example of an MVSPM I/O Rate for Devicesby Workload Type report . . . . . . . 877

viii Tivoli Decision Support for OS/390: System Performance Feature Reference Volume I

||||||||||||

252. Example of an MVSPM I/O Response Timefor Device, Hourly Trend report . . . . . 879

253. Example of an MVSPM Cache Hit Rates byCU, Hourly Trend report. . . . . . . . 881

254. Example of an MVSPM DFW Hit Rates byCU, Hourly Trend . . . . . . . . . . 883

255. Example of an MVSPM Staging Rates by CU,Hourly Trend report . . . . . . . . . 885

256. Example of an MVSPM Overall Effectivenessby CU, Daily Overview report . . . . . . 887

257. Example of an MVSPM Highest Hit RateVolumes, Daily Overview report . . . . . 889

258. Example of an MVSPM Highest Staging RateVolumes, Daily Overview report . . . . . 891

259. Example of an MVSPM Cache CU Operationsby CU, Daily Overview report . . . . . . 893

260. Example of an MVSPM Cache CUOperations, Hourly Trend report . . . . . 895

261. Example of an MVSPM I/O Response Timefor Devices by Workload report . . . . . 897

262. Example of an MVSPM I/O Rate byWorkload on Selected Devices report. . . . 899

263. Example of an MVSPM XCF Statistics bySystem, Overview report. . . . . . . . 900

264. Example of an MVSPM XCF Signal Rates,Hourly Trend report . . . . . . . . . 902

265. Example of an MVSPM XCF Activity by Pathand System, Overview report . . . . . . 903

266. Example of an MVSPM Data Set ActivityOverview report . . . . . . . . . . 905

267. Example of an MVSPM Data Set I/O Rate &Resp Time, Hourly Trend report . . . . . 907

268. Example of an MVSPM Data Set I/O RateProfile, Hourly Trend report . . . . . . 909

269. Example of an MVSPM Data Set Resp TimeProfile, Hourly Trend report . . . . . . 910

270. Example of an MVSPM Storage Class RespTime, Hourly Trend report . . . . . . . 911

271. Example of an MVSPM Storage Class I/ORate, Hourly Trend report . . . . . . . 912

272. Example of an MVSPM Volume Activity byStorage Class, Overview report . . . . . 913

273. Example of an MVSPM Channel Path Busy,Extended Mode report . . . . . . . . 915

274. Example of an MVSPM OpenEdition HFSGlobal Statistics report . . . . . . . . 917

275. Example of an MVSPM OpenEdition HFSBuffer Statistics report . . . . . . . . 919

276. Example of an MVSPM OpenEdition HFSStatistics report . . . . . . . . . . . 921

277. Example of an MVSPM OpenEdition FileStatistics report . . . . . . . . . . . 923

278. Example of an MVSPM OpenEdition KernelSystem Calls Activity report . . . . . . 925

279. Example of an MVSPM OpenEdition KernelProcess Activity report . . . . . . . . 926

280. Example of an MVSPM OpenEdition KernelProcess Communication report . . . . . . 928

281. Example of an MVSPM OpenEdition KernelMemory Statistics report . . . . . . . . 930

Figures ix

x Tivoli Decision Support for OS/390: System Performance Feature Reference Volume I

Preface

The IBM Tivoli® Decision Support for OS/390® System Performance Feature Referenceis divided into two volumes. This book is Volume I.

This book provides reference information for the System Performance feature ofIBM Tivoli Decision Support for OS/390 (hereafter referred to as Tivoli DecisionSupport for OS/390). It is a source of reference for:v Installation and customization procedures for the System Performance featurev Log records that the System Performance feature supportsv Record definitions that the System Performance feature uses to map performance

data into Tivoli Decision Support for OS/390 DATABASE 2™ (DB2®) tablesv DB2 tables that Tivoli Decision Support for OS/390 uses to store performance

datav Predefined reports that Tivoli Decision Support for OS/390 creates from

performance data

You should use this book in conjunction with the Tivoli Decision Support for OS/390:System Performance Feature Guide.

Tivoli Decision Support for OS/390 was previously known as Tivoli PerformanceReporter for OS/390.

The terms MVS™ and OS/390 are used interchangeably throughout this book.

Who Should Read This BookSystem Performance Feature Reference Volume I is intended for those who analyze theperformance of Multiple Virtual Storage (MVS) and Virtual Machine (VM) systems,and for those who are responsible for establishing or meeting organization-wideservice-level objectives for MVS or VM systems. System Performance FeatureReference Volume I is intended for both Tivoli Decision Support for OS/390administrators (primarily as a reference to table and column descriptions) andusers with a variety of backgrounds who want to use Tivoli Decision Support forOS/390 to analyze MVS or VM performance data.

What This Book ContainsThis book is organized in parts:v Part I introduces the components of the System Performance feature, and

presents information that is common to all of the components. It also providesinstructions on installation, implementation, and customization.

v Parts II through VII contain information about the following SystemPerformance feature components:

Part II, Tivoli Storage Manager (ADSM) componentPart III, DB2 componentPart IV, DFSMS componentPart V, DFSMS/RMM™ componentPart VI, MVS componentPart VII, MVS Availability componentPart VIII, MVS performance management component

xi

|

Each part describes one component and provides some or all of the followinginformation about that component:– “Customization” describes the steps necessary to set up the component for

your installation.– “Data flow” describes the flow of data from log records to reports for the

component.– “Log and record definitions” lists the supported logs and the records used

from the logs.– “Data tables and lookup tables” describes the DB2 tables in the Tivoli

Decision Support for OS/390 database provided with the component.– “Reports” describes each report supplied with the component.

v Part IX contains a list of abbreviations, glossary, and index.

PublicationsThis section lists publications in the Tivoli Decision Support for OS/390 library andany other related documents. It also describes how to access Tivoli publicationsonline and how to order Tivoli publications.

Tivoli Decision Support for OS/390 LibraryThe following documents are available in the Tivoli Decision Support for OS/390library:v Administration Guide, SH19-6816

Provides information about initializing the Tivoli Decision Support for OS/390database and customizing and administering Tivoli Decision Support forOS/390.

v Guide to the Reporting Dialog, SH19-6842Provides information for users who display existing reports, for users who createand modify reports, and for administrators who control reporting dialog defaultfunctions and capabilities.

v Language Guide and Reference, SH19-6817Provides information for adminstrators, performance analysts, and programmerswho are responsible for maintaining system log data and reports.

v User’s Guide for the Viewer, SH19-4517Provides information about how use the graphical interface for Tivoli DecisionSupport for OS/390.

v Messages and Problem Determination, SH19-6902Provides information to help operators and system programmers understand,interpret, and respond to Tivoli Decision Support for OS/390 messages andcodes.

v Accounting Feature for the Host, SH19-4495Provides information for users who want to use Tivoli Decision Support forOS/390 to collect and report performance data generated by the Accountingfeature.

v Accounting Feature for the Workstation, SH19-4516Provides information for users who want to use the Accounting WorkstationOption to manage, process, and analyze financial data on a workstation.

v AS/400 System Performance Feature Guide and Reference, SH19-4019Provides information for administrators and users about collecting and reportingperformance data generated by AS/400® systems.

xii Tivoli Decision Support for OS/390: System Performance Feature Reference Volume I

v CICS Performance Feature Guide and Reference, SH19-6820Provides information for administrators and users about collecting and reportingperformance data generated by Customer Information and Control System(CICS®).

v Distributed Systems Performance Feature Guide and Reference, SH19-4018Provides information for administrators and users about collecting and reportingperformance data generated by operating systems and applications running on aworkstation.

v IMS Performance Feature Guide and Reference, SH19-6825Provides information for administrators and users about collecting and reportingperformance data generated by Information Management System (IMS™).

v Network Performance Feature Installation and Administration, SH19-6901Provides information for network analysts or programmers who are responsiblefor setting up the network reporting environment.

v Network Performance Feature Reference, SH19-6822Provides information for network analysts or programmers who are responsiblefor setting up the network reporting environment.

v Network Performance Feature Reports, SH19-6821Provides information for network analysts or programmers who use theNetwork Performance feature reports.

v System Performance Feature Guide, SH19-6818Provides information for performance analysts and system programmers whoare responsible for meeting the service-level objectives established in yourorganization.

v System Performance Feature Reference, Volume I, SH19-6819Provides information for administrators and users with a variety of backgroundswho want to use Tivoli Decision Support for OS/390 to analyze Multiple VirtualStorage (MVS) or Virtual Machine (VM) performance data.

v System Performance Feature Reference, Volume II, SH19-4494Provides information for administrators and users with a variety of backgroundswho want to use Tivoli Decision Support for OS/390 to analyze Multiple VirtualStorage (MVS) or Virtual Machine (VM) performance data.

v IBM Online Library Omnibus Edition OS/390 Collection Kit, SK2T-6700CD containing all OS/390 documentation.

v IBM Online Library z/OS Software Products Collection Kit, SK3T-4270CD containing all z/OS™ documentation.

Using LookAt to look up message explanationsLookAt is an online facility that lets you look up explanations for most messagesyou encounter, as well as for some system abends and codes. Using LookAt to findinformation is faster than a conventional search because in most cases LookAt goesdirectly to the message explanation.

You can access LookAt from the Internet at:http://www.ibm.com/eserver/zseries/zos/bkserv/lookat/ or from anywhere inz/OS or z/OS.e where you can access a TSO/E command line (for example,TSO/E prompt, ISPF, z/OS UNIX® System Services running OMVS).

The LookAt Web site also features a mobile edition of LookAt for devices such asPocket PCs, Palm OS, or Linux-based handhelds. So, if you have a handheld

Preface xiii

http://www.ibm.com/servers/eserver/zseries/zos/bkserv/lookat/lookat.html

device with wireless access and an Internet browser, you can now access LookAtmessage information from almost anywhere.

Accessing publications onlineIBM posts publications for this and all other Tivoli products, as they becomeavailable and whenever they are updated, to the Tivoli Software InformationCenter Web site. The Tivoli Software Information Center is located at the followingWeb address:

http://publib.boulder.ibm.com/tividd/td/tdprodlist.html

Click the Tivoli Decision Support for OS/390 link to access the product library.

These publications are available in PDF or HTML format, or both. Translateddocuments are also available for some products.

Note: If you print PDF documents on other than letter-sized paper, select the Fit topage check box in the Adobe Acrobat Print dialog. This option is availablewhen you click File ” Print. Fit to page ensures that the full dimensions of aletter-sized page print on the paper that you are using.

Ordering PublicationsYou can order many Tivoli publications online at the following Web site:http://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgi

You can also order by telephone by calling one of these numbers:v In the United States: 800-879-2755v In Canada: 800-426-4968

In other countries, see the following Web site for a list of telephone numbers:

http://www.ibm.com/software/tivoli/order-lit/

AccessibilityAccessibility features help users with a physical disability, such as restrictedmobility or limited vision, to use software products successfully. With this product,you can use assistive technologies to hear and navigate the interface.You can alsouse the keyboard instead of the mouse to operate all features of the graphical userinterface.

For additional information, see the Accessibility Appendix in the AdministrationGuide.

Contacting software supportIf you have a problem with any Tivoli product, refer to the following IBM SoftwareSupport Web site:

http://www.ibm.com/software/sysmgmt/products/support/

If you want to contact software support, see the IBM Software Support Guide at thefollowing Web site: http://techsupport.services.ibm.com/guides/handbook.html

xiv Tivoli Decision Support for OS/390: System Performance Feature Reference Volume I

http://publib.boulder.ibm.com/tividd/td/tdprodlist.html

http://www.elink.ibmlink.ibm.com/public/applications/publications/

http://www.elink.ibmlink.ibm.com/public/applications/publications/

http://www.ibm.com/software/tivoli/order-lit/

http://www.ibm.com/software/sysmgmt/products/support/

http://techsupport.services.ibm.com/guides/handbook.html

The guide provides information about how to contact IBM Software Support,depending on the severity of your problem, and the following information:v Registration and eligibilityv Telephone numbers and e-mail addresses, depending on the country in which

you are locatedv Information you must have before contacting IBM Software Support

Note: For Tivoli NetView® for OS/390 customers only, additional support isavailable on the NETVIEW CFORUM (Customer Forum) through the IBMLink system. This forum is monitored by NetView developers who answerquestions and provide guidance. When a problem with the code is found,you are asked to open an official problem management record (PMR) toobtain resolution.

Conventions used in this bookThis guide uses several conventions for special terms and actions, operatingsystem-dependent commands and paths, and margin graphics.

The term z/OS is used in this book to mean z/OS and OS/390 operating systems.Where the term OS/390 does appear, the related information applies only toOS/390 operating systems.

Typeface conventionsThis guide uses the following typeface conventions:

Bold

v Lowercase commands and mixed case commands that are otherwisedifficult to distinguish from surrounding text

v Interface controls (check boxes, push buttons, radio buttons, spinbuttons, fields, folders, icons, list boxes, items inside list boxes,multicolumn lists, containers, menu choices, menu names, tabs, propertysheets), labels (such as Tip:, and Operating system considerations:)

v Column headings in a tablev Keywords and parameters in text

Italic

v Citations (titles of books, diskettes, and CDs)v Words defined in textv Emphasis of words (words as words)v Letters as lettersv New terms in text (except in a definition list)v Variables and values you must provide

Monospace

v Examples and code examplesv File names, programming keywords, and other elements that are difficult

to distinguish from surrounding textv Message text and prompts addressed to the userv Text that the user must typev Values for arguments or command options

Preface xv

Changes in this editionThe following changes appear in this edition of System Performance FeatureReference:v The MVS Availability component section has been added.v In the MVS Component and in the MVS Performance Component new tables

and changes to the existing ones as well as new reports have been added.

Except for editorial changes, updates to this edition are marked with a vertical barto the left of the change.

xvi Tivoli Decision Support for OS/390: System Performance Feature Reference Volume I

|

||

Part 1. Introduction

Chapter 1. Implementing the System Performancefeature . . . . . . . . . . . . . . . . 3Understanding the System Performance feature. . . 3Installing and customizing the System Performancefeature . . . . . . . . . . . . . . . . 7

Installing the feature and its components . . . . 8Customizing the components . . . . . . . . 8Testing the installation. . . . . . . . . . 13Putting Tivoli Decision Support for OS/390 intoproduction . . . . . . . . . . . . . 14

Understanding data flow . . . . . . . . . . 15Understanding log and record definitions . . . . 18Understanding data tables, views, and lookup tables 19

Naming standard for data tables . . . . . . 20Naming standard for views . . . . . . . . 21Naming standard for lookup tables . . . . . 21Common tables . . . . . . . . . . . . 21Table descriptions . . . . . . . . . . . 21

Understanding reports. . . . . . . . . . . 22Heading . . . . . . . . . . . . . . 23Description . . . . . . . . . . . . . 23Report ID . . . . . . . . . . . . . . 23Report group . . . . . . . . . . . . . 24Source . . . . . . . . . . . . . . . 24Attributes . . . . . . . . . . . . . . 24Variables . . . . . . . . . . . . . . 24Example report . . . . . . . . . . . . 25Column descriptions . . . . . . . . . . 25

1

2 Tivoli Decision Support for OS/390: System Performance Feature Reference Volume I

Chapter 1. Implementing the System Performance feature

IBM Tivoli Decision Support for OS/390 (hereafter referred to as Tivoli DecisionSupport for OS/390) is a reporting system that collects performance data logged bycomputer systems, summarizes the data, and presents it in a variety of forms foruse in systems management.

Tivoli Decision Support for OS/390 consists of the Tivoli Decision Support forOS/390 base product and several optional features:v Accounting feature for the Hostv Accounting feature for the Workstationv AS/400 System Performance featurev CICS Performance featurev Distributed Systems Performance featurev IMS Performance featurev Network Performance featurev System Performance feature

The Tivoli Decision Support for OS/390 base product provides two dialogs forworking with Tivoli Decision Support for OS/390:v Administration dialog

The administration of Tivoli Decision Support for OS/390 includes installing thefeatures and components, customizing the product, and maintaining the TivoliDecision Support for OS/390 database. For complete information on using theadministration dialog, refer to the Administration Guide.

v Reporting dialogThe reporting dialog lets you display, create, and modify reports. For completeinformation on using the reporting dialog, refer to the Guide to the ReportingDialog.

This chapter describes how to get started with the System Performance feature. Italso describes the information given in this book for each component. It containsthese sections:v “Installing and customizing the System Performance feature”v “Understanding data flow”v “Understanding log and record definitions”v “Understanding data tables, views, and lookup tables”v “Understanding reports”

Understanding the System Performance featureEach Tivoli Decision Support for OS/390 feature consists of components. Eachcomponent provides support for a specific operating system, licensed program, ortask.

The components of the System Performance feature are:

DB2 The DB2 component collects data from the SMF log and stores datarelevant to DB2 performance. You can create reports that show DB2response times, transaction statistics, system statistics, buffer pool andEDM pool statistics, and DB2 exceptions.

3

DFSMSThe Data Facility Storage Management System (DFSMS) component usesdata from DCOLLECT to create reports about active data set storage,volume usage, and Data Facility Storage Management Subsystemhierarchical storage manager (DFSMShsm™) backup and migration storage.You can use these reports to manage your storage subsystem on variouslevels and for capacity planning.

DFSMS/RMMThe Data Facility Storage Management System/Removable MediaManagement (DFSMS/RMM) component collects records from the extractdataset file for volume and dataset records in DB2 tables.

DominoThe Domino component collects data from the SMF log and stores it in theDB2 database. You can create reports that show DOMINO response times,transactions, server, traffic, and buffer pool statistics. Refer to Tivoli DecisionSupport for OS/390: System Performance Feature Reference, Volume II for moredetails.

EREP The EREP component includes reports that complement the more detailedreports produced by the Environmental Record and Editing Printing(EREP) program. These reports provide management overview trendreports on hardware errors for DASD and virtual telecommunicationsaccess method (VTAM®) controlled devices, and initial program loads(IPLs) of the processors.

The input log to Tivoli Decision Support for OS/390 is the history file fromEREP on MVS or the corresponding file in VM.

(Refer to System Performance Feature Reference, Volume II.)

Internet Connection Secure ServerThe Internet Connection Secure Server component enables you to displayreports on configuration and performance data retrieved from the InternetConnection Secure Server application for OS/390.

For more information on ICSS, refer to System Performance Feature Reference,Volume II and the Tivoli Decision Support for OS/390: Webmaster Guide forOS/390 V2R2 (GC31-8490).

IXFP IXFP is the host software that helps you manage the IBM RAMAC® VirtualArray Storage. You can use IXFP to provide extended facilities foradministering, configuring and obtaining reports. These reports provideinformation about the performance of RAMAC Virtual Array (RVA)subsystems, about the performance of traditional DASD subsystems, andabout the cache effectiveness of certain non-RVA subsystems. (Refer toSystem Performance Feature Reference, Volume II.)

Message analysis/automationThe message analysis/automation component reports contain messagestatistics based on system log (SYSLOG) data (from Job Entry Subsystem 2(JES2) or JES3 systems), and data from the NetView log. You can use thereports to get statistics on message types and IDs, message rates, messagesuppression, and automation. The reports also indicate which messages arecandidates to be suppressed, passed to NetView, or not passed to NetView.(Refer to System Performance Feature Reference, Volume II)

Implementing the System Performance Feature


||||||

MQSeries®

The MQSeries component collects records from the SMF data set and storesthis data in the DB2 database. (Refer to System Performance FeatureReference, Volume II.)

MVS The MVS component includes reports that help you monitor and report onthe system management functions such as utilization, and capacity. Youcan use the reports to see trends of the most important measurements andreport on system management areas.

This component includes exceptions reports, and detail, overview, andtrend reports for analyzing response times and resource usage; job, TimeSharing Option (TSO) session, and started-task statistics; initial programload (IPL) details; and program, device, and printer statistics. It alsoincludes all the objects needed to collect Linux for 390 data.

MVS availabilityThe MVS availability component provides collects availability statistics onthe Sysplex, the MVS system, and for user-defined address spaces. Thiscomponent includes overview and detailed reports to show specificavailability problems.

MVS performance managementThe MVS performance management component reports show the use ofmajor system resources on both system and workload levels. You can usethe MVS performance management component to analyze and manageprocessor, processor storage, and I/O subsystem resources. This componentincludes overview reports for assessing overall system performance, anddetailed reports that help you investigate particular performance problems.

OPC The Operations Planning and Control (OPC, now known as TivoliWorkload Scheduler) component provides reports on the Tivoli WorkloadScheduler (previously known as Operation Planning and Control) product.The OPC component collects OPC track log data and stores it in the TivoliDecision Support for OS/390 database. You can use the Tivoli DecisionSupport for OS/390 reporting dialog to create reports based on this data.(Refer to System Performance Feature Reference, Volume II.)

RACF®

The Resource Access Control Facility (RACF) component reports areintended for the security administrator and resource owners. Use theRACF component as a complement to the RACF Report Writer. The reportscontain auditing data. The RACF component supports both OS/390 andVM log data. (Refer to System Performance Feature Reference, Volume II.)

TCP/IPThe TCP/IP component collects records from the SMF data set and storesthis data in the DB2 database. (Refer to System Performance FeatureReference, Volume II.)

Tivoli Service DeskThe Tivoli Service desk component contains reports for problem andchange management. You can use these reports to analyze the number ofchanges and problems, and determine how many there have been, whatcaused them, and how long it took to resolve them. (Refer to SystemPerformance Feature Reference, Volume II.)

Tivoli Storage Manager (ADSM)The Tivoli Storage Manager (ADSM) component collects records from theSMF data set and stores data about the ADSM client.


Chapter 1. Implementing the feature 5

|||||

|||||||

||||||||

VM accountingThe VM accounting component provides reports on your VM users. Youcan use these reports to analyze the resources being used and who is usingthem. (Refer to System Performance Feature Reference, Volume II.)

VMPRFThe Virtual Machine Performance Reporting Facility (VMPRF) componentprovides reports on virtual machine processor usage and response times,system performance characteristics, and system configuration. You can usethis data for response-time analysis or for a breakdown of user or usergroup activity. (Refer to System Performance Feature Reference, Volume II.)

WebSphere®

The WebSphere component collects data from the SMF log and stores it inthe DB2 database. You can create reports that show server statistics, webapplication response times, and complete activity metrics with differentlevels of detail (class, method). Refer to Tivoli Decision Support for OS/390:System Performance Feature Reference, Volume II for more details.

Table 1 shows the products and releases supported by the System Performancefeature.

Table 1. Products and Releases supported by the System Performance Feature

Product Releases supported

Cache RMF™ Reporter 1.3, 1.4, 1.6

DB2 6, 7

DFSMS/MVS® 1.2, 1.3, 1.4, 1.5

DFSMS/OAM 1.5

DFSMS/RMM 1.5

EREP 3.5

Internet Connection Secure Server 2.1

IXFP 2.2

JES2/JES3 OS/390 2.10 and z/OS 1.1, 1.2, 1.3, 1.4

LINUX SUSE for OS/390 7.0

LINUX SUSE 7.1

LINUX REDHAT 7.1

LOTUS DOMINO 5.1, 5.3, 5.6, 6.0

TURBOLINUX 6.5

MQSeries 5.2

MQSeries for MVS 1.1.4, 1.2, 2.1

MVS/DFP™ 3.2, 3.3

NetView 2.1, 2.2, 2.3, 2.4

OPC/ESA 2.1, 2.2, 2.3

OS/390 2.10

OS/390 Security Server 2.10

RMF for OS/390 2.1

RMF for z/OS OS/390 2.10 and z/OS 1.1, 1.2, 1.3, 1.4

TCP/IP 3.2, 3.3 and OS/390 2.5



||||||

|

|

|

|

|

|

|

Table 1. Products and Releases supported by the System Performance Feature (continued)

Product Releases supported

Tivoli Service Desk 1.2

Tivoli Storage Manager for MVS and OS/390 (ADSM)

Tivoli Workload Scheduler for z/OS 8.1

VM/ESA® 1.1, 1.2

VM/XA SP™ 1.2

VMPRF 1.2

z/OS 1.1, 1.2, 1.3, 1.4

WEBSPHERE 4.01

Installing and customizing the System Performance featureFigure 1 shows the steps involved in the administration and customization of theSystem Performance feature.

These sections describe these tasks in more detail:v “Installing the feature and its components”v “Customizing the components”v “Testing the installation”v “Putting Tivoli Decision Support for OS/390 into production”

Planning and installingfeature components

Customizing supportedproducts and Tivoli Decision

Support for OS/390

Testing the feature

Moving system intoproduction

Maintaining Tivoli DecisionSupport for OS/390

Modifyingthe feature

Figure 1. Administration and customization tasks



|

|

Installing the feature and its componentsAfter your system programmer installs the Tivoli Decision Support for OS/390base and does the SPM/E installation of the System Performance feature, you caninstall the components you want to use.

Each component of the System Performance feature is optional to install. So, youmust decide which components of the feature you want to install.

You install all Tivoli Decision Support for OS/390 features and components in thesame way. Using the administration dialog, you select which components of theSystem Performance feature to install.

When you install a component, Tivoli Decision Support for OS/390 executesdefinitions in the component to define all its logs, records, tables, and reports.Then you can use the component to collect, store, and create reports on the logdata that it supports.

For detailed information on installing or migrating the feature and its components,refer to the Administration Guide.

Customizing the componentsIf you are migrating customized components, refer to the Administration Guide.

After you install the components, you must perform these steps:1. Customize the supported products to make input data available.2. Set up collect jobs.3. Update Tivoli Decision Support for OS/390 lookup tables.

The “Customization” chapter for each component contains details relevant to thatcomponent.

The following sections outline the general procedures for these steps.

Making input data availableEach of the products supported by the System Performance feature gathersperformance and management data and writes that information to a log or data set(for example, SMF log, DCOLLECT log, EREP history file, and VMPRF SUMMARYfile). You customize these products to create the data you need at regular intervals.

This step ensures that the necessary data is available to Tivoli Decision Support forOS/390 for processing. For example, if you install the DB2 component, you mustensure that the accounting and statistics traces are started in DB2. If you install theVMPRF component, ensure that you collect VM monitor data, process it withMONWRITE and VMPRF, and transfer the resulting summary file to MVS forprocessing by Tivoli Decision Support for OS/390. The “Customization” chapterfor each component gives the details for this step.

After customizing the products, verify that the appropriate records needed foryour Tivoli Decision Support for OS/390 tables and reports are being generated.

Setting up the collect jobYou must create a job control language (JCL) job to collect data from the necessarylogs.



Tivoli Decision Support for OS/390 provides these sample collect jobs that you canmodify and use to collect data:v DRLJCOLL

The DRLJCOLL job (member DRLJCOLL in the SDRLCNTL library) is a genericcollect job that you can use to collect most IBM system-generated data. This dataincludes that written to SMF, DCOLLECT, EREP, SYSLOG, NetView, OPC,AIX®*, OS400, VM accounting, and VMPRF log data sets. Figure 2 on page 10and Figure 3 on page 11 show DRLJCOLL.

v DRLJCOINDRLJCOIN is a sample collect job for collecting data from theInformation/Management database. See the "Customization" section of the"Tivoli Service Desk" chapter in the System Performance Feature Reference, VolumeII, for more information about this job.

Refer to the Administration Guide for information on setting up collect procedures.



//DRLJCOLL JOB (ACCT#),’COLLECT’//***************************************************************//* Licensed Materials - Property of IBM *//* 5695-101 (C) Copyright IBM Corporation 1993, 2003 *//* See Copyright Instructions. *//***************************************************************//* Name: DRLJCOLL *//* *//* Status: Tivoli Decision Support for OS/390 1.6.0 *//* *//* Function: *//* Tivoli Decision Support for OS/390 collect job. *//* *//* Replace "COLLECT SMF" below with one of the following *//* statements to collect other logs: *//* *//* COLLECT DCOLLECT *//* WHERE DCUDATE > DATE(LOOKUP LAST_DCOLLECT_TIME *//* IN DRL.DFSMS_LAST_RUN *//* WHERE DCUSYSID = MVS_SYSTEM_ID *//* AND DCURCTYP = RECORD_TYPE); *//* (replace DRL with the table prefix you use) *//* (the lookup table DFSMS_LAST_RUN must be initialized *//* before the first collect as described in the DFSMS *//* customization chapter of the SP Feature Reference) *//* *//* COLLECT EREP; *//* *//* SET JES_COMPLEX = ’ ’; *//* COLLECT SYSLOG_JES2; *//* *//* For operations log (OPERLOG) produced using the System *//* Logger, use the COLLECT statement above and change the *//* //DRLLOG statement as follows: *//* //DRLLOG DD DSN=SYSPLEX.OPERLOG,DISP=SHR, *//* SUBSYS=(LOGR,, *//* ’FROM=(1995/152,00:00),TO=(1995/153,23:59,GMT’)*//* *//* SET JES_COMPLEX = ’JES3COMP’; *//* COLLECT SYSLOG_JES3; *//* (replace JES3COMP with the name of the JES3 complex) *//* *//* SET MVS_SYSTEM_ID = ’MVS1’; *//* COLLECT NETVIEW; *//* (replace MVS1 with the name of the MVS system) *//* *//* COLLECT OPC; *//* *//* SET VMID = ’VM1’; *//* COLLECT VMACCT; *//* (replace VM1 with the name of the VM system) *//* *//* COLLECT VMPRF; *//* COLLECT UNIX; *//* *//* COLLECT OS400_JOURNAL; *//* COLLECT OS400_CONFIG; *//* COLLECT OS400_HISTORY; *//* COLLECT OS400_PM_DISK; *//* COLLECT OS400_PM_POOL; *//* COLLECT OS400_PM_SYS; *//* *

Figure 2. DRLJCOLL job (Part 1 of 2)



Follow the instructions in the comments section of this job to modify theappropriate JCL statements.

Updating lookup tablesTo make the reports more useful, you can specify data specific to your installationthrough lookup tables. Lookup tables contain user-defined data that describes youroperating environment. You can specify:v Resource groupsv User groupsv Workload typesv Project groupsv Thresholdsv Code conversions

First, you must decide how you want data grouped. You do this by developing aperformance and service-level strategy; refer to the System Performance FeatureGuide for information.

After developing your strategy, you can modify the lookup tables for eachcomponent to implement your strategy. Update the lookup tables and provideuser-defined data to organize the system data collected from SMF and other logs.Tivoli Decision Support for OS/390 uses this data when collecting data into tablesand when creating reports.

The “Customization” chapter for each component provides details on whichlookup tables you must edit and the information you must supply.

Using the administration dialog, edit the lookup tables using the ISPF editor byperforming these steps:

Note: If you are editing a lookup table directly from the online installationprocedure, go to Step 4 on page 13.

1. From the Administration window, select 4 (Tables).

//* For some logs, special collect jobs are required: *//* DRLJCOIM IMS log *//* DRLJCOVP Network configuration data *//* DRLJCOIN Information/Management data *//* *//* Notes: *//* Before you submit the job: *//* - Check the Tivoli Decision Support for OS/390 *//* and DB2 data set names. *//* - Check the DB2 subsystem name (default is DSN) *//* and the Tivoli Decision Support for OS/390 system *//* table prefix (default is DRLSYS). *//* - Insert the correct collect statement in DRLIN *//* (as described above). *//* - Specify the name of the log data set in DRLLOG. *//***************************************************************//COLLECT EXEC PGM=DRLPLC,PARM=(’SYSTEM=DSN SYSPREFIX=DRLSYS’)//STEPLIB DD DISP=SHR,DSN=DRL160.SDRLLOAD// DD DISP=SHR,DSN=DSN610.DSNLOAD//DRLIN DD *

COLLECT SMF;

//DRLLOG DD DISP=SHR,DSN=log-data-set//DRLOUT DD SYSOUT=*,DCB=(RECFM=F,LRECL=80)//DRLDUMP DD SYSOUT=*,DCB=(RECFM=VB,LRECL=32756)/*

Figure 3. DRLJCOLL job (Part 2 of 2)



Tivoli Decision Support for OS/390 displays the Tables window (see Figure 4).

2. Select the table you want to edit, but do not press Enter.3. Select 3 (ISPF editor) from the Edit pull-down (see Figure 5), and press Enter.

Tivoli Decision Support for OS/390 copies the table rows to a sequential fileand accesses the ISPF editor. An ISPF EDIT window (see Figure 6 on page 13) isdisplayed.

Table Utilities Edit View Other Help----------------------------------------------------------------------

Tables ROW 366 TO 376 OF 413

Select one or more tables. Then press Enter to Open table definition.

/ Tables Prefix Type_ PERIOD_PLAN DRLSYS TABLE_ RACF_COMMAND_T DRL TABLE_ RACF_EVENT_CODE DRL TABLE_ RACF_LOGON_T DRL TABLE_ RACF_OPERATION_T DRL TABLE_ RACF_RES_OWNER DRL TABLE_ RACF_RESOURCE_T DRL TABLE/ RACF_USER_OWNER DRL TABLE_ SAMPLE_H DRL TABLE_ SAMPLE_M DRL TABLE_ SAMPLE_USER DRL TABLE_ SCHEDULE DRLSYS TABLE_ SPECIAL_DAY DRLSYS TABLE

Command ===> ______________________________________________________________F1=Help F2=Split F3=Exit F5=Updates F6=PurCond F7=BkwdF8=Fwd F9=Swap F10=Actions F11=Display F12=Cancel

Figure 4. Tables window

Figure 5. Tables window edit pull-down



4. Edit the data in the lookup table.The first part of the window shows column labels. You cannot change thecolumn labels.Type in values in the data area below the column labels to add site-specificinformation.

5. Press F3 (End) when you finish editing the table.The rows are inserted into the DB2 table and you return to the Tables window.

6. Select another lookup table to edit, or press F3 (Exit).If you select F3, you return to the Administration window.

Note: You must use the Query Management Facility (QMF)™ to edit tables widerthan 255 characters. For detailed instructions on using the QMF table editor,refer to the Query Management Facility: Learner’s Guide.

As the needs of your organization change, so will your service-level strategy.Update the lookup tables periodically to reflect these changes.

Testing the installationBefore starting daily use of the System Performance feature, you should run a fewtests to ensure that the installation was successful. This step verifies that TivoliDecision Support for OS/390 is collecting the right data, storing the data correctly,and using the proper data to create the reports. Testing the installation alsoconfirms that the lookup tables contain the appropriate groups, classes, andservice-level objectives.

As part of the test, perform these steps:1. Run a collect job to collect data from a log data set and review any messages.2. Display a table to ensure that it exists and contains the correct information.3. Create and display a report to ensure it is correctly installed.

For information on running these tests or additional tests, refer to theAdministration Guide. After you run the tests and verify that the installation issuccessful, you are ready to put Tivoli Decision Support for OS/390 intoproduction.

EDIT ---- XLLOYDA.DRLTAB ------------------------------------- COLUMNS 001 072****** ***************************** TOP OF DATA ******************************==MSG> USE TAB KEY TO POSITION TO THE NEXT COLUMN====== SYST|CLASS |PROFILE_NAME |G|RESPONSI|SE====== EM_I| | |E|BLE_USER|EL====== D | | |N| |====== | | |E| |====== | | |R| |====== | | |I| |====== | | |C| |====== ------------------------------------------------------------------------’’’’

-----------------------------------------------------------------------! Use Tab Key to position to the next column. The decimal separator is!! a period.’ !-----------------------------------------------------------------------

’****** **************************** BOTTOM OF DATA ****************************COMMAND ===> SCROLL ===> 0020F1=HELP F2=SPLIT F3=END F4=RETURN F5=RFIND F6=RCHANGEF7=UP F8=DOWN F9=SWAP F10=LEFT F11=RIGHT F12=RETRIEVE

Figure 6. Editing a lookup table



Putting Tivoli Decision Support for OS/390 into productionFigure 7 shows the daily steps involved in using Tivoli Decision Support forOS/390.

Making logs available to Tivoli Decision Support for OS/390In some cases, Tivoli Decision Support for OS/390 cannot directly access the logdata sets from which it collects data. You must make the logs available to thecollect function. You must perform this step for these log data sets:

SMF dataMany of the software products supported by the System Performancefeature write records to the SMF log data set. Tivoli Decision Support forOS/390 cannot read this SMF log data set directly. So, you must copy thelog records from the virtual storage access method (VSAM) data set to asequential log data set for use by Tivoli Decision Support for OS/390. Usethe SMF dump program to do this. Refer to OS/390 MVS SystemManagement Facilities (SMF) for information on this program.

VM dataThe VM components write records to VM log (CMS) files. You must sendthese log files to your MVS system for processing by Tivoli DecisionSupport for OS/390. If your VM and MVS systems are not directlyconnected, you can create a tape using the VM FILEDEF and MOVEFILEcommands and load the tape onto the MVS system.

For the components that support other logs and record types, you need notperform this step.

Collecting data from logsYou must submit jobs regularly to collect data from log data sets and store the datain the Tivoli Decision Support for OS/390 database. You can set up automaticprocedures for collecting data. Monitor Tivoli Decision Support for OS/390 collectactivity so you can optimize collect performance.

Make logs availableto Tivoli DecisionSupport for OS/390

Collect data fromlogs

Perform databasemaintenance

Create reports

Figure 7. Daily steps involved in using Tivoli Decision Support for OS/390



Maintaining Tivoli Decision Support for OS/390Maintaining the Tivoli Decision Support for OS/390 database includes purging oldand obsolete data, reorganizing the database, updating DB2 statistics, backing updata, updating views of the DB2 catalogs, and protecting the integrity of data bycontrolling access to it.

Regular maintenance tasks include:1. Running a purge job.

To control database size, purge data regularly. The Tivoli Decision Support forOS/390 PURGE statement lets you delete obsolete data while keepingsummarized data. In most cases, Tivoli Decision Support for OS/390summarizes hourly and daily data in weekly or monthly tables. Purging dailydata does not affect data summarized by month. Using the PURGE statementminimizes the space used and improves collect time.

2. Running the REORG utility.The DB2 REORG utility reorganizes table spaces and indexes to improve DB2access performance and space utilization. Use the REORG utility after a purgejob to free the space of the purged data.

3. Running a backup job.Back up the database periodically.

4. Updating views on the DB2 catalog.Update views on the DB2 catalog whenever DB2 parameters change, such aswhen adding a new database or a new prefix for Tivoli Decision Support forOS/390 tables, to give all dialog users access to DB2 catalog information.

For more information about database maintenance, refer to the AdministrationGuide.

Creating reportsThe final step in your daily routine is creating reports. For frequently requestedreports, you can set up batch jobs that create reports on a regular schedule. Youcan use the reporting dialog to specify the batch settings for a report. You willwant to create other reports on an as-needed basis. You can run these reportsinteractively.

Refer to the Administration Guide and the Guide to the Reporting Dialog, forinformation on creating reports.

Understanding data flowTivoli Decision Support for OS/390 and the System Performance feature collectonly the data required to meet users’ needs, combine that data with informationthat you provide, and present the data in the form of reports.

Input for the Tivoli Decision Support for OS/390 database consists of sequentiallog data sets, such as SMF and DCOLLECT system logs. Tivoli Decision Supportfor OS/390 processes data collected from the input logs, summarizes and stores thedata in the Tivoli Decision Support for OS/390 database, and produces reportsbased on that data.

Figure 8 on page 16 illustrates how data is organized to be presented in TivoliDecision Support for OS/390 reports.



Figure 9 on page 17 shows the general flow of data within a component. Itillustrates the steps involved in processing data. Some System Performance featurecomponents use all of these steps when processing data; others do not. The “Dataflow” chapter for each component describes the flow of data within thatcomponent in more detail.

O p e r a t i n g s y s t e m

TivoliDecisionSupportfor OS/390SystemPerformancefeature

Tivoli DecisionSupport for

OS/390 records

Tivoli DecisionSupport for

OS/390 tables

User supplieddata

Report Report Report

System data

Data writtento various logs

Only required datacollected by TivoliDecision Supportfor OS/390

Data summarizedin Tivoli DecisionSupport for OS/390database

Required datapresented in reportformat

Logs

Figure 8. Organizing and presenting system performance data



The data flow follows these steps:1. The operating system or other program writes data to a sequential log data

set, which is the input to Tivoli Decision Support for OS/390.2. You initiate the collect either through the dialog, or by using a Tivoli Decision

Support for OS/390 language statement in a job, identifying a specific logtype definition.

1

2

4

Log data

log definition log procedure

record proceduresrecord definitions

update definitions

update definitionsData tables

SQL queries

Reports

lookup tables

lookup tables

3a

3b

5a

5b

7

9a

9b

1110

12

Tivoli Decision Support for OS/390

COLLECT

6

8

Figure 9. Overview of Tivoli Decision Support for OS/390 data flow



3. Optionally, the log definition might process the log data with a user-exitprogram, a log procedure. If the log definition calls a log procedure:a. The log procedure receives each record in the log as input.b. Output from a log procedure varies in format, and is usually a record

mapped by a Tivoli Decision Support for OS/390 record definition.4. Tivoli Decision Support for OS/390 looks for record definitions associated

with the log definition in its system tables. It applies those record definitionsto specific record types from the log or log procedure.

5. Optionally, a record definition might require processing by a user-exitprogram, a record procedure. If a record definition requires processing by arecord procedure:a. The record procedure receives a specific record type only and is not called

for other record types.b. Output from a record procedure varies in format, and is usually a record

mapped by a Tivoli Decision Support for OS/390 record definition.6. Tivoli Decision Support for OS/390 applies a specific update definition to each

known record type and performs the data manipulations and databaseupdates as specified.

7. Tivoli Decision Support for OS/390 often selects data from lookup tables tofulfill the data manipulations that update definitions require.

8. Tivoli Decision Support for OS/390 writes non summarized and first-levelsummarized data to data tables specified by the update definitions.

9. Tivoli Decision Support for OS/390 uses updated tables as input for updatingother, similar tables that are for higher summary levels. If update definitionsspecify data summarization:a. Tivoli Decision Support for OS/390 selects data from the first table as

required by the update definitions and performs required datasummarization.

b. Tivoli Decision Support for OS/390 updates other data tables as requiredby the update definitions.

(Tivoli Decision Support for OS/390 might select data from lookup tablesduring this process, but this step is not shown in Figure 9 on page 17.)

10. Once Tivoli Decision Support for OS/390 stores the data from a collect, youcan display reports on the data. Tivoli Decision Support for OS/390 uses aquery to select the data for the report.

11. Optionally, Tivoli Decision Support for OS/390 might select data from lookuptables specified in the query.

12. Tivoli Decision Support for OS/390 creates report data, displaying, printing,or saving it as you requested.

Refer to the Administration Guide for more information on collecting data.

Understanding log and record definitionsEach component uses log definitions, which are stored in the Tivoli DecisionSupport for OS/390 system tables, to define each log to the System Performancefeature. A log definition describes the layout and format of one of the logssupported by the System Performance feature.



A log must be defined to Tivoli Decision Support for OS/390 before any data canbe collected. You can create your own log definitions using the administrationdialog. Using the administration dialog, you can perform various tasks for logdefinitions, including:v View a list of log data sets collectedv Display contents of a logv Collect data from a logv Create a report on a recordv Create a log definitionv View and modify a log definitionv Delete a log definition

Each record in a log belongs to some record type. To process records of a certaintype, the record must be described to the log collector. This is done with recorddefinitions. Record definitions for all records used by the System Performancefeature components are provided with the Tivoli Decision Support for OS/390base. The Tivoli Decision Support for OS/390 base also provides record definitionsfor additional records from logs supported by the features. For a complete list ofthe record definitions provided, refer to the Administration Guide.

Using the administration dialog, you can perform various tasks for recorddefinitions, including:v View and modify a record definitionv Create a record definitionv Display update definitions associated with a recordv Delete a record definition

Refer to the Administration Guide and the Language Guide and Reference forinformation on working with log and record definitions.

The “Log and record definitions” chapter for each component lists the log andrecords used by that component.

In some cases in the System Performance feature, a component takes two or morerecords from a log and creates one record that includes data from the inputrecords. The component uses a record procedure to do this. The record proceduredefines which fields to take from each of the input records and what data theoutput record contains.

Understanding data tables, views, and lookup tablesThe Tivoli Decision Support for OS/390 database is a collection of DB2 tables. Eachcomponent includes a set of predefined tables. The “Data tables and lookup tables”chapter for each component describes the tables used by that component.

The process of entering data into the DB2 tables consists of several stages. The datafrom the log is first summarized in one table. Then, the contents of that table aresummarized into another table, and so on. An update definition specifies how datafrom one source (a record or table) is entered into one target (always a table).

Typically, a component first stores the collected data in an hourly table, whichretains data for the shortest time period. The component then summarizes the datafrom the hourly table into the daily, weekly, and monthly tables. Each table retainsdata for successively longer periods and each is used for different reportingperiods. In some cases, the data is not summarized. This data is stored innonsummarized tables (_T).



Table 2 lists the typical retention periods for each type of database table.

Table type Suffix Retention period

Hourly _H 7 days

Daily _D 30 days

Weekly _W 375 days

Monthly _M 765 days

Nonsummarized _T 30 days

You can change the retention period for any database table. Refer to theAdministration Guide for information on changing retention periods.

You can use the administration dialog to perform various tasks in tables, including:v Open a table to display columnsv Display and modify the update definitionsv Display table spacev Create a new tablev Administer user access to tablesv Generate documentation of tables

A component can include data tables, views, and lookup tables. Data tables containdata collected from the input logs. Views are alternative representations of datatables. Lookup tables contain user-defined data.

The “Data tables and lookup tables” chapter for each component describes thetables provided with that component. Each chapter presents the tables inalphabetical order.

Some features use common data tables, lookup tables, and control tables. Thesetables are described in the Administration Guide.

Naming standard for data tablesNames of the System Performance feature data tables are in this format:

component_content_suffix

where:v component is a prefix that indicates the component name, which can be DB2,

DFSMS, EREP, INFOMAN, INT, MQS, MSG, MVS, MVSPM, OPC, RACF,TCP, VMACCT, or VMPRF.

v content is a description (for example, WORKLOAD for workload statistics ordata).

v suffix indicates the summarization level of the data in the table (for example, Hfor data summarized by hour).A table name can have these summarization-level suffixes:T The table holds nonsummarized data (timestamped data).H The table holds data summarized by hour.D The table holds data summarized by day.W The table holds data summarized by week.M The table holds data summarized by month.



Naming standard for viewsSome components include views, which are alternative representations of datafrom one or more tables. A view can include all or some of the columns containedin the table on which it is defined.

Views follow the same naming convention as data tables, except a V is added tothe table name. If more than one view exists for a data table, a sequential numberis also added to the name. For example:

MVS_WORKLOAD_DV1MVS_WORKLOAD_DV2MVS_WORKLOAD_DV3MVS_WORKLOAD_DV4

The description of a view includes the key columns and only the data columnsspecific to the view. All other data columns appear in the description of theoriginal data table.

Naming standard for lookup tablesNames of the System Performance feature lookup tables are in this format:

component_content

where:v component is a prefix that indicates the component name, which can be DB2,

DFSMS, EREP, INT, IXFP, MQS, MSG, MVS, MVSPM, OPC, RACF, TCP,TSD, VMACCT, or VMPRF.

v content is a description (for example, DS_OWNER for data set owners).

Common tablesThe System Performance feature also uses some tables that are common to severalTivoli Decision Support for OS/390 features. The names of these tables do notbegin with a component prefix. The common tables include control tables, datatables, and lookup tables. Refer to the Administration Guide for completedescriptions of the common tables.

Table descriptionsEach of the data and lookup table descriptions includes information about thetable, a description of each of the key columns, and a description of each of thedata columns.

Key columns are marked with a k.

Data columns come after the last key column and are sorted in alphabetic order,with any underscores ignored.

The descriptions of most key columns and data columns contain references to thefields from which they are derived in the SMF record, such as From BRFFLRTY.For an explanation of such fields, refer to the applicable product documentation.

The tables appear in alphabetic order, with any underscores ignored.



Note: Tables with similar contents (that is, tables with the same name but differentsuffixes) are described under one heading. For example,“DB2_APPL_DIST_H, _W” on page 51 contains information about twosimilar tables:DB2_APPL_DIST_HDB2_APPL_DIST_W

Except for the DATE column and TIME column, the contents of these two tablesare identical. Differences in the contents of similar tables are explained in thecolumn descriptions.

The DATE and TIME information is stored in the standard Structured QueryLanguage (SQL) format and displayed in the local format. The DATE columncontains the first day of the week for weekly (_W) tables, and the first day of themonth for monthly (_M) tables.

Hexadecimal codes in log records are stored as character data in DB2 tables. Forexample, a 2-byte field X'FFFF' is stored as a 4-byte character string FFFF.

Understanding reportsThe ultimate goal of all data collection and processing in the System Performancefeature is the creation of reports. Reports show essential performance data in clearand easily understandable formats. Because users have different needs, the SystemPerformance feature reports present a variety of data in several formats. You canselect the data you need and the format in which you want to see the data.

You can create reports using the host reporting dialog. the host reporting dialogruns in an MVS environment and the For information on creating reports with thehost reporting dialog, refer to the Guide to the Reporting Dialog.

You can use the reporting dialog to perform various tasks with reports, including:v Create new reportsv Search for reportsv Display a reportv Save report datav View information about a reportv Print a reportv Delete a reportv Modify a report

The “Reports” chapter of each component describes each predefined report. Eachreport description contains this information:v Headingv Descriptionv Report IDv Report groupv Sourcev Attributesv Variablesv Example reportv Column descriptions

Figure 10 on page 23 shows an example report description



HeadingMost reports are available for several different time periods. Because these reportsare almost identical, they are described together and only one example is included.The heading lists the different time periods for which the report is available.

DescriptionThe report description briefly discusses the information presented in the report. Insome cases, the description contains information on how to interpret the report orgives sources for more information.

Report IDTivoli Decision Support for OS/390 assigns each report a unique report identifier.Each report ID consists of these parts:

component_nnn

where:v component is a prefix that indicates the component name, for example, DB2,

DFSMS, EREP, INT, IXFP, MQS, MSG, MVS, MVSPM, OPC, RACF, TCP,TSD, VMACCT, or VMPRF.

DB2 Application Response Times, Detail report

This report shows response times by application, as defined in the DB2_APPLICATION lookup table. For more information on using this report, refer to the System Performance Feature Guide.This information identifies the report:

Report ID DB201

Report group DB2 reports

Source DB2_APPLICATION_H

Attributes DB2, Performance, Response, Application

Variables MVS_system_ID, DB2_system_ID, From_date, To_date

DB2 Application Response Times, Detail reportThis report shows response times by application, as defined in the DB2_APPLICATION lookup table. For more information on using thisreport, refer to the System Performance Feature Guide.

DB2 Application Response Times, DetailSystem: ’MVS1’ DB2 ID: ’DB2A’

Date: ’1999-11-19’ to ’2000-03-09’Elapsed Elapsed Elapsed

Application seconds seconds seconds Commit Abortname Profile avg max min count count

------------ ----------- ---------- ---------- -------- ------------ ------

T.D.S./390 QUERY 9.39 23.27 0.16 13218 18QMF QUERY 7.83 25.20 0.13 7876 8SPUFI RR QUERY 4.60 21.14 0.31 73 5

Tivoli Decision Support for OS/390 Report: DB201

Example of a DB2 Application Response Times, Detail reportThe report contains this information:

Application name The application name, as defined in the DB2_APPLICATION lookup table.

Profile The type of application (transaction, query, batch and so on) as defined in the DB2_APPLICATION lookup table.

Elapsed seconds avg The average elapsed time during the report interval, in seconds. Calculated as: SUM(ELAPSED_SEC) / (SUM(COMMIT_COUNT) +SUM(ABORT_COUNT)).

Elapsed seconds max The maximum elapsed time during the report interval, in seconds. Calculated as: MAX((ELAPSED_SEC) / (COMMIT_COUNT +ABORT_COUNT)).

Elapsed seconds min The minimum elapsed time during the report interval, in seconds. Calculated as: MIN((ELAPSED_SEC) / (COMMIT_COUNT +ABORT_COUNT)).

Commit count The number of commits that occurred during the report interval.

Abort count The number of aborts that occurred during the report interval.

Figure 10. Example report description



v nnn is a sequential number given to the report in a component.

Examples:MVSPM07DB2011VMACCT01

When the report description includes reports for more than one time period, thedescription lists the report IDs for all time periods and identifies the time periodfor which each applies.

Report groupTo make it easier to find reports, the System Performance feature organizes reportsinto report groups, which correspond to the feature components. For example, allof the reports in the RACF component belong to the RACF report group. You cancreate your own report groups by saving selected reports as a group.

SourceThe sources listed are the database tables from which the System Performancefeature extracts data to create the report. If the component uses information fromlookup tables, those are listed as well. When the report description includes reportsfor more than one time period, the description lists the source tables for all timeperiods and identifies the time period for which each applies.

AttributesThe attributes are keys that you can use to search for a particular report. For eachreport, an attribute indicates the area to which the report belongs (for example,OS/390, VM, or RACF).

The report descriptions also specify the following attributes, where appropriate:v Resource types reported (for example, storage or processor)v Performance issue reported (for example, availability or response)v Presentation forms (for example, trend or overview)v Time resolution in the report (hourly, daily, weekly, or monthly)

VariablesWhen you select a report to create, Tivoli Decision Support for OS/390 promptsyou for the variables listed in this section. When the report description includesreports for more than one time period, the description lists variables for all timeperiods and identifies the time period for which each applies.

For monthly reports, you must specify the From_month and To_month variables.The month must be specified as the date of the first day of the month. Forexample, enter 1993-01-01 (or a date in another format that is supported by DB2) torequest information for the month of January 1993. The From_month andTo_month values appear on the reports as the date of the first day of the month(for example, 1993-01-01 means the data is for the entire month of January).

You can enter date and time values in any format supported by DB2. The valuesare displayed in the local format, which you define in DB2. The sample reports inthis book use the ISO format (yyyy-mm-dd).



If you do not specify a value for a variable, the variable name appears on thereport. For example, if Tivoli Decision Support for OS/390 prompts you for astorage class, but you do not specify one, STORAGE_CLASS appears on the report.

For complete information on creating reports, refer to the Guide to the ReportingDialog.

Example reportThe example illustrates a typical report. When the report description includesreports for more than one time period, the description only includes an example ofa report for one time period.

Note that exponential notation is used for some data in the reports. For example,123.45E+04 means 1234500.

Column descriptionsThe column descriptions describe each column in the report in detail. Data in areport comes directly from data tables or is the result of calculations performed inviews or in the SQL query used to create the report. If the column contains acalculated value, the formula used for the calculation is included.

Some of these calculations are a simplified version of the SQL query rather thanthe exact calculation. For an exact description of the calculation, refer to the SQLquery.

To see the SQL query, use the Tivoli Decision Support for OS/390 reporting dialog.Select the report and then select Open report definition in the Reports pull-downmenu. Then press F5 (Query/Fm) and Tivoli Decision Support for OS/390 displaysthe SQL query.

When views are used, you may need to refer to the view descriptions to find moreinformation not included in the calculations.



Part 2. Tivoli Storage Manager (ADSM) component

Chapter 2. Data tables . . . . . . . . . . 29ADSM_ACCOUNT_T, _H, _D, _W . . . . . . 29

Chapter 3. Reports . . . . . . . . . . . 31ADSM report descriptions . . . . . . . . . 32

ADSM Session Statistics, Detail report . . . . 32ADSM Activities Statistics, Detail report . . . . 34ADSM Data Statistics, Detail report . . . . . 36ADSM Activities Statistics, Overview report . . 38ADSM Data Statistics, Overview report . . . . 40

27

Chapter 2. Data tables

This chapter describes the data tables used by the Tivoli Storage Manager (ADSM)component. For descriptions of common data tables, lookup tables, and controltables used by the System Performance feature, refer to the Administration Guide.

ADSM_ACCOUNT_T, _H, _D, _WThese tables provide time stamped data from the OS/390 ADSM server via theSMF type 42, subtype 14 records.

The default retention periods for these tables are:ADSM_ACCOUNT_T 7 daysADSM_ACCOUNT_H 14 daysADSM_ACCOUNT_D 30 daysADSM_ACCOUNT_W 375 days

Column name Data type Description

REC_DATE k DATE Date when the records were collected by SMF.

REC_TIME k TIME Time when the records were collected by SMF. Time appliesonly to the _T and _H tables. In the _H table, time is roundedto the hour.

PERIOD_NAME k CHAR(8) Name of the period.

MVS_SYSTEM_ID k CHAR(4) MVS system ID. This is the SMF system ID. From SM101SID.

ACCT_DATE k DATE Accounting date. It applies only to the _T table.

ACCT_TIME k TIME Accounting time. It applies only to the _T table.

ADSM_NODE k CHAR(30) ADSM node name.

DURATION FLOAT Session duration, in seconds.

ARCHIVE_INSERTS FLOAT Archive DB objects inserted.

BACKUP_INSERTS FLOAT Backup DB objects inserted.

ARCHIVE_KB FLOAT Archived files, in KB.

BACKUP_KB FLOAT Backed-up files, in KB.

DATA_COMM_KB FLOAT Data communicated, in KB, this session.

CLIENT_OWNER CHAR(8) Client owner name.

NODE_TYPE CHAR(8) Node type.

COMM_METHOD CHAR(8) Communication method.

ARCHIVE_RETRIEVE FLOAT Archived DB objects retrieved.

BACKUP_RETRIEVE FLOAT Backed-up DB objects retrieved.

SPACE_ARC_RTRV FLOAT Space, in KB, retrieved by archived objects.

SPACE_BAK_RTRV FLOAT Space, in KB, retrieved by backed-up objects.

IDLE_TIME FLOAT Idle wait time, in seconds.

WAIT_TIME FLOAT Communication wait time, in seconds.

MEDIA_TIME FLOAT Media wait time, in seconds.

CPU_TIME FLOAT CPU time, in seconds.

29


AUTH_METHOD FLOAT Authentication method used.

TERM_INDICATOR FLOAT Normal termination indicator (= hex 01).

SPACEDB_INSERT FLOAT Number of space-managed DB objects inserted during session.

SPACEKB_SENT FLOAT Amount of space-managed data (KB) sent by the client to theserver.

SPACEDB_RETRIEVE FLOAT Number of space-managed DB objects retrieved duringsession.

SPACEKB_RETRIEVE FLOAT Amount of space (KB) retrieved by space-managed objects.


Chapter 3. Reports

The Tivoli Storage Manager (ADSM) component provides these reports:v ADSM Session Statistics, Detail reportv ADSM Activities Statistics, Detail reportv ADSM Data Statistics, Detail reportv ADSM Activities Statistics, Overview reportv ADSM Data Statistics, Overview report

31

ADSM report descriptionsThis section describes the reports provided with the ADSM component.

ADSM Session Statistics, Detail reportThis report shows statistics and characteristics of the sessions related to eachADSM client node. The information is displayed hour by hour for a specific date.

This information identifies the report:

Report ID ADSM01

Report group ADSM reports

Source ADSM_ACCOUNT_H

Attributes ADSM, Statistics, Session

Variables Date, MVS_system_ID

The report contains this information:

Time The time when the record was moved into the SMFbuffer.

ADSM node The node name of the ADSM client.

Client owner The client owner name (UNIX).

Node type The node type.

Communication method The communication method used for the session.

Idle wait time (sec) The amount of Idle wait time during the session.

ADSM Session Statistics Report, DetailMVS system:’TSM1’DATE: 1999-10-29

Client Node CommunicationTime ADSM Node owner type method

-------- ------------------------------ -------- -------- -------------10.00.00 C48045_CEDRIC Win95 Tcp/Ip10.00.00 C48834_CHRIS Win95 Tcp/Ip11.00.00 C48834_CHRIS Win95 Tcp/Ip11.00.00 054532_TP755 Win95 Tcp/Ip12.00.00 C48045_CEDRIC Win95 Tcp/Ip12.00.00 C48834_CHRIS Win95 Tcp/Ip16.00.00 028393_JOHN Win95 Tcp/Ip17.00.00 C48045_CEDRIC Win95 Tcp/Ip19.00.00 085204_CSSCLAN OS/2 Tcp/Ip

Idle wait Communication Media wait CPU timetime (sec) wait time(sec) time (sec) (sec)---------- -------------- ---------- ----------

34 0 0 01197 0 0 3154 0 0 3

1118 380 0 376825 5042 0 576493 274 0 34182 109 0 12

5882 4505 0 6011008 392 0 164

Tivoli Decision Support for OS/390 Report: ADSM01

Figure 11. Example of an ADSM Session Statistics, Detail report

Reports


Communication wait time (sec)The amount of Communications wait time duringthe session.

Media wait time (sec) The amount of Media wait time during the session.

CPU time (sec) The amount of CPU time used by the server forbasic client activity related to each ADSM clientnode.

Reports

Chapter 3. Reports 33

ADSM Activities Statistics, Detail reportThis report shows activities, for example, retrieve and insert, related to each ADSMnode. The information is displayed hour by hour for a specific date.


Report ID ADSM02



Attributes ADSM, Activities





Archive objects inserted The number of archive database objects insertedduring the session.

Backup objects inserted The number of backed-up database objects insertedduring the session.

Archived objects retrieved The number of archived database objects retrievedduring the session.

Backed up objects retrieved The number of backed-up database objectsretrieved during the session.

ADSM Activities Statistics Report, DetailMVS system:’TSM1’DATE: 1999-10-29

Archive Backup Archivedobjects objects objects

Time ADSM Node inserted inserted retrieved-------- ------------------------------ --------- ---------- ----------10.00.00 C48045_CEDRIC 0 0 010.00.00 C48834_CHRIS 0 0 011.00.00 C48834_CHRIS 0 0 011.00.00 054532_TP755 0 241 012.00.00 C48045_CEDRIC 10194 0 012.00.00 C48834_CHRIS 0 105 016.00.00 028393_JOHN 0 8 017.00.00 C48045_CEDRIC 12318 0 019.00.00 085204_CSSCLAN 0 717 0

Backed up Space managed Space managedobjects DB objects DB objects

retrieved inserted retrieved---------- -------------- --------------

0 0 02 0 00 0 00 0 00 0 00 0 00 0 00 0 00 0 0


Figure 12. Example of an ADSM Activities Statistics, Detail report

Reports


Space managed DB objects insertedThe number of space-managed database objectsinserted during the session.

Space managed DB objects retrievedThe number of space-managed database objectsretrieved during the session.

Reports


ADSM Data Statistics, Detail reportThis report shows space statistics related to each ADSM node activity. Theinformation is displayed hour by hour for a specific date.


Report ID ADSM03



Attributes ADSM, Space, Data





Archived files(KB) The number of archived files, in kilobytes, sent bythe client to the server.

Backed up files(KB) The number of backed-up files, in kilobytes, sentby the client to the server.

Data(KB) communicated The amount of data, in kilobytes, communicatedbetween a client node and the server during thissession.

ADSM Data Statistics Report, DetailMVS system:’TSM1’DATE: 1999-10-29

ADSM Archived Backed upTime node files(KB) files(KB)

-------- ------------------------------ ---------- ----------10.00.00 C48045_CEDRIC 0 010.00.00 C48834_CHRIS 0 011.00.00 C48834_CHRIS 0 011.00.00 054532_TP755 0 5037112.00.00 C48045_CEDRIC 0 97794012.00.00 C48834_CHRIS 0 15512116.00.00 028393_JOHN 0 979817.00.00 C48045_CEDRIC 0 124036619.00.00 085204_CSSCLAN 0 187225

Space(KB) Space(KB) Space(KB) Space(KB)Data(KB) archived backed up mng data mng data

Communicated objects objects sent recv------------ ---------- ---------- ---------- ----------

2 0 0 0 0109 0 2 0 0104 0 0 0 0

51549 0 0 0 0980369 0 0 0 0155165 0 0 0 09815 0 0 0 0

1243285 0 0 0 0236775 0 0 0 0


Figure 13. Example of an ADSM Data Statistics, Detail report

Reports


Space(KB) archived objects The amount of space, in kilobytes, retrieved byarchived objects.

Space(KB) backed up objects The amount of space, in kilobytes, retrieved bybacked-up objects.

Space(KB) mng data sent The amount of space-managed data, in kilobytes,sent by the client to the server.

Space(KB) mng data recv The amount of space, in kilobytes, retrieved by theclient from the server.

Reports


ADSM Activities Statistics, Overview reportThis report shows activities, for example, retrieve and insert, related to each ADSMnode. The information is displayed as a summary across an interval between astart date and an end date.


Report ID ADSM04


Source ADSM_ACCOUNT_D

Attributes ADSM, Activities, Daily

Variables From_date, To_date, MVS_system_ID


ADSM Activities Statistics Report, OverviewMVS system:’TSM1’

Date: ’1999-10-29’ to ’2000-04-10’

Archive Backup ArchivedADSM objects objects objectsnode inserted inserted retrieved------------------------------ ---------- ---------- ----------C27715_GREMLIN 0 1864 0C48045_CEDRIC 0 22512 0C48834_CHRIS 0 3682 0003407_NIGEL 0 3 0006351_ANDY 0 606 0020039_MDUFTPAD 0 294 0022003_BRUCE 0 12 0028393_JOHN 0 16 0044074_PC 0 715 0046212_MARK 0 638 0054532_TP755 0 731 0054932_JACKIE 0 0 0060914_DEREK 0 180 0082807_STICKPAD 0 2065 0085204_CSSCLAN 0 10840 0085204_STEVE 0 9805 0085204_STEVE 0 9805 0093562_THINKPAD 0 241 0

Backed up Space managed Space managedobjects DB objects DB objects

retrieved inserted retrieved---------- ------------- -------------

0 0 00 0 03 0 00 0 02 0 00 0 02 0 00 0 01 0 00 0 00 0 00 0 00 0 00 0 02 0 07 0 07 0 00 0 0


Figure 14. Example of an ADSM Activities Statistics, Overview report

Reports



Archive objects inserted The number of archive database objects insertedduring the session.

Backup objects inserted The number of backed-up database objects insertedduring the session.

Archived objects retrieved The number of archived database objects retrievedduring the session.

Backed up objects retrieved The number of backed-up database objectsretrieved during the session.

Space managed DB objects insertedThe number of space-managed database objectsinserted during the session.

Space managed DB objects retrievedThe number of space-managed database objectsretrieved during the session.

Reports


ADSM Data Statistics, Overview reportThis report shows space statistics related to each ADSM node activity. Theinformation is displayed as a summary across an interval between a start date andan end date.


Report ID ADSM05


Source ADSM_ACCOUNT_D

Attributes ADSM, Space, Data, Daily




ADSM Data Statistics Report, OverviewMVS system:’TSM1’

Date: ’1999-10-29’ to ’1999-11-12’

ADSM Archived Backed up Data(KB)node files(KB) files(KB) Communicated------------------------------ ---------- ---------- ------------C27715_GREMLIN 0 330939 342054C48045_CEDRIC 0 2218306 2223658C48834_CHRIS 0 272892 275385003407_NIGEL 0 6708 6716006351_ANDY 0 61305 69011020039_MDUFTPAD 0 70798 70953022003_BRUCE 0 91877 92059028393_JOHN 0 19708 19742044074_PC 0 4763 9006046212_MARK 0 1457126 1459263054532_TP755 0 182088 187536054932_JACKIE 0 0 2060914_DEREK 0 106845 111284082807_STICKPAD 0 258132 261087085204_CSSCLAN 0 2924538 3183961085204_STEVE 0 1039165 1132221085204_STEVE 0 1039165 1132221093562_THINKPAD 0 63131 64129

Space(KB) Space(KB) Space(KB) Space(KB)archived backed up mng data mng dataobjects objects sent recv

---------- ---------- ---------- ----------0 0 0 00 0 0 00 2 0 00 0 0 00 1 0 00 0 0 00 30 0 00 0 0 00 144 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 213 0 00 1 0 00 1 0 00 0 0 0


Figure 15. Example of an ADSM Data Statistics, Overview report

Reports


Archived files(KB) The amount of archived files, in kilobytes, sent bythe client to the server.

Backed up files(KB) The amount of backed-up files, in kilobytes, sentby the client to the server.

Data(KB) communicated The amount of data, in kilobytes, communicatedbetween a client node and the server during thissession.

Space(KB) archived objects The amount of space, in kilobytes, retrieved byarchived objects.

Space(KB) backed up objects The amount of space, in kilobytes, retrieved bybacked-up objects.

Space(KB) mng data sent The amount of space-managed data, in kilobytes,sent by the client to the server.

Space(KB) mng data recv The amount of space, in kilobytes, retrieved by theclient from the server.

Reports


Reports


Part 3. DB2 component

Chapter 4. Customization . . . . . . . . . 45Make input data available . . . . . . . . . 45Review the DRLJCOLL job . . . . . . . . . 45Update lookup tables . . . . . . . . . . . 46

Chapter 5. Data flow . . . . . . . . . . . 47Lookup tables . . . . . . . . . . . . . 48

Chapter 6. Log and record definitions. . . . . 49

Chapter 7. Data tables and lookup tables . . . 51Data tables . . . . . . . . . . . . . . 51

DB2_APPL_DIST_H, _W . . . . . . . . . 51DB2_APPLICATION_H, _W . . . . . . . . 52DB2_BP_SHARING_T . . . . . . . . . . 53DB2_BPATTR_SHR_T . . . . . . . . . . 56DB2_BUFFER_POOL_T . . . . . . . . . 58DB2_DATABASE_T. . . . . . . . . . . 63DB2_LOCK_SHARING_T. . . . . . . . . 73DB2_PACKAGE_H, _D, _W . . . . . . . . 75DB2_SHARING_INIT . . . . . . . . . . 77DB2_SYS_PARAMETER . . . . . . . . . 78DB2_SYSTEM_DIST_T. . . . . . . . . . 81DB2_SYSTEM_T . . . . . . . . . . . . 84DB2_TRAN_DIST_D, _W . . . . . . . . . 91DB2_TRANSACTION_D, _W . . . . . . . 92DB2_US_TRAN_SHAR_H . . . . . . . . 93DB2_USER_AP_DIST_H, _W . . . . . . . 95DB2_USER_APPL_H, _W. . . . . . . . . 96DB2_USER_DIST_H, _D, _W . . . . . . . 97DB2_USER_TRAN_H, _D, _W. . . . . . . 101

Lookup tables . . . . . . . . . . . . . 115DB2_APPLICATION . . . . . . . . . . 115

Chapter 8. Reports . . . . . . . . . . . 117DB2 report descriptions . . . . . . . . . . 117

DB2 Application Response Times, Detail report 117DB2 Application Response Times, Overviewreport . . . . . . . . . . . . . . . 120DB2 Application Response Times, Trend report 121DB2 Transaction Statistics, Detail report . . . 122DB2 Transaction Statistics, Overview report . . 125DB2 Transaction Statistics, Trend report. . . . 126DB2 System Services Statistics, Detail report . . 127DB2 Database Services Statistics, Detail report 129DB2 System Statistics, Overview report . . . . 131DB2 System CPU % by Address Space,Overview report . . . . . . . . . . . 133DB2 System Statistics, Trend report . . . . . 135DB2 General Measure by Profile, Overviewreport . . . . . . . . . . . . . . . 137DB2 Application Profiles, Overview report . . 138DB2 Application Profiles, Trend report . . . . 140DB2 Buffer Pool Statistics, Detail report . . . 142DB2 Buffer Pool Statistics, Overview report . . 144

DB2 EDM Pool Statistics, Detail report . . . . 146DB2 EDM Pool Statistics, Overview report . . 148DB2 Buffer Pool Exceptions report . . . . . 150DB2 System Parameters report . . . . . . 152DB2 Packages Class 7,8 Times, Overview report 155DB2 DBRMs Class 7,8 Times, Overview report 156DB2 Group Buffer Pool Statistics, Detail report 157DB2 Data Sharing Locking Statistics, Detailreport . . . . . . . . . . . . . . . 159DB2 Group Buffer Pool Accounting, Overviewreport . . . . . . . . . . . . . . . 161DB2 Data Sharing Locking Accounting,Overview report . . . . . . . . . . . 163DB2 User Defined Functions, Detail report . . 165DB2 User Defined Functions, Overview report 167DB2 Triggers, Detail report . . . . . . . . 169DB2 Triggers, Overview report . . . . . . 171DB2 Row ID, Detail report . . . . . . . . 173DB2 Row ID, Overview report. . . . . . . 175DB2 Secondary Group Buffer Pool Statistics,Detail report. . . . . . . . . . . . . 177DB2 Application Wait Times, Detail report. . . 179DB2 Application Wait Times, Overview report 181DB2 Application Wait Times, Trend report . . . 182

43

Chapter 4. Customization

Before you can use the DB2 component to collect data and create reports, you mustcustomize and test the installation. This chapter describes the steps you mustperform to customize the DB2 component:1. Make input data available.2. Review the DRLJCOLL job.3. Update lookup tables.

Make input data availableDB2 tables are based on the DB2 accounting and statistics traces. Accounting datais written for each connection to DB2, and can be used for analyzing responsetimes and resource usage. The statistics (usually written every 30 minutes, which isthe DB2 installation default) provide data for the entire DB2 subsystem (systemservices and database services).

The permanent activation of the DB2 statistics and accounting class 1 traces isassumed, since the overhead created by these is considered negligible (2% to 5%).The activation of accounting class 2 and class 3 traces in a selected time frame (forexample, 10 minutes per day) is also assumed.

Most of the counters and timers in the DB2 statistics records are accumulatedtotals. The counters and timers are reset to zero only at DB2 restart time.

Tivoli Decision Support for OS/390 processes the IFCID 106 record from theperformance trace record (SMF type 102 record). DB2 writes this record when youissue a -START TRACE command (at DB2 startup). The IFCID 106 record containscurrent DB2 system parameter settings.

Ensure that DB2 statistics and accounting records are present in the SMF data set,by performing these steps:1. Ensure that the accounting and statistics traces are started in DB2. For

accounting, at least class 1 must be active. Activating accounting class 2 andclass 3 traces makes more data available in Tivoli Decision Support for OS/390tables, but also increases DB2 overhead. Refer to the IBM DATABASE 2Administration Guide for information about starting the traces.

2. Ensure that SMF type 100, 101, and 102 records are not suppressed by SMF orany of its exits.

Review the DRLJCOLL jobBefore running the Tivoli Decision Support for OS/390 collect job, you shouldreview the DRLJCOLL member, as described in “Setting up the collect job” onpage 8.

45

Update lookup tablesIf you want your data grouped by applications, you can update theDB2_APPLICATION lookup table. This lookup table contains DB2 plan names andtheir corresponding application names and application types (for example,transaction, query, and batch).

Using the administration dialog, update the DB2_APPLICATION lookup table.

Table name Description Key columns Data columns

DB2_APPLICATION Converts DB2 plans toapplication names andapplication profiles.

MVS_SYSTEM_IDDB2_SYSTEM_IDAPPLICATION_NAMEDB2_PLAN

PROFILE

For a complete description and example of this lookup table, see“DB2_APPLICATION_H, _W” on page 52.

The DB2 component also uses the PERIOD_PLAN control table when updatingdata tables. The PERIOD_PLAN table defines the partition of a day into periods(such as shifts). Ensure that this control table includes the correct periods. For acomplete description of the control table and an example of its contents, refer tothe Administration Guide.

For information on using the administration dialog to update lookup tables, see“Updating lookup tables” on page 11.

DB2 customization


Chapter 5. Data flow

The DB2 component collects SMF log data recorded by DB2 and stores the data inthe Tivoli Decision Support for OS/390 database. You can then use the reportingdialog to create reports based on this data.

Figure 16 shows an overview of the flow of data from the DB2 licensed program,through the DB2 component of Tivoli Decision Support for OS/390, and finallyinto usable reports.

DB2

SMF

Recorddefinitions

Data tables

Lookup andcontrol tables

DB2_APPLICATIONPERIOD_PLAN

SMF_100_0SMF_100_1SMF_100_2SMF_100_3SMF_101SMF_101_1SMF_102

DB2_APPL_DIST_xDB2_APPLICATION_xDB2_BUFFER_POOL_TDB2_DATABASE_TDB2_SYS_PARAMETERDB2_SYSTEM_DIST_TDB2_SYSTEM_TDB2_TRAN_DIST_xDB2_TRANSACTION_xDB2_USER_AP_DIST_xDB2_USER_APPL_xDB2_USER_DIST_xDB2_USER_TRAN_x


Collect

Reports

Figure 16. DB2 component data flow

47

Lookup tablesAfter collecting data, the DB2 component stores the data in data tables in the TivoliDecision Support for OS/390 database. As it updates the tables, the DB2component uses the DB2_APPLICATION lookup table to convert DB2 plans toapplication names and application profiles. Figure 17 shows which data tablescontain values from the lookup table.

The DB2 component uses the PERIOD_PLAN common control table to update datatables. For information on the common control tables, refer to the AdministrationGuide.

For detailed information about the data tables the component updates, and thelookup table it uses, see Chapter 7, “Data tables and lookup tables”, on page 51.

Figure 17. Lookup table data

DB2 data flow


Chapter 6. Log and record definitions

DB2 writes trace records to SMF type 100, 101, and 102 records. Each record has aninstrumentation facility component ID (IFCID) that describes exactly what data therecord contains. See your DSNxxx.DSNSAMP(DSNWMSGS) data set for adescription of each IFCID record.

The DB2 component processes these records from the SMF log data set:

SMFrecordtype Subtype

DB2IFCID

TivoliDecisionSupport forOS/390 recorddefinition Description

100 0 0001 SMF_100_0 This is a system services statisticsrecord that contains system-widedata collected at preset intervals(default = 30 minutes).

100 1 0002 SMF_100_1 This is a database statistics recordthat contains system-wide datacollected at preset intervals (default =30 minutes).

100 2 0202 SMF_100_2 This is a statistics DYNAMICZPARM record that containssystem-wide data collected at presetintervals (default = 30 minutes).

100 3 0230 SMF_100_3 This is a global statistics record thatcontains system-wide data collectedat preset intervals.

101 0003 SMF_101 This is an accounting record thatcontains transaction data writtenwhen the thread terminates or whenthe authorization ID changes (threadis reused).

101 1 0239 SMF_101_1 This is an accounting record thatcontains information aboutPACKAGE/DBRM. The record iswritten when the agent has executedmore than 10 packages.

102 0106 SMF_102 This is a performance record thatcontains system parameters in effectwhen an explicit or implicit (at DB2startup) START TRACE statement isissued.

Refer to the IBM DATABASE 2 Administration Guide for details about the SMFrecords written by DB2.

49

Chapter 7. Data tables and lookup tables

This chapter describes the data tables and lookup tables used by the DB2component. For descriptions of common data tables, lookup tables, and controltables used by the System Performance feature, refer to the Administration Guide.

Data tablesThis section describes the data tables for the DB2 component.

DB2_APPL_DIST_H, _WThese tables provide hourly and weekly statistics on DDF distributed addressspace grouped by application. They contain accounting and response-time databased on SMF type 101 records (DB2 accounting, IFCID 0003).

These tables are updated by the DB2_APPLICATION lookup table.

The default retention periods for these tables are:DB2_APPL_DIST_H 30 daysDB2_APPL_DIST_W 375 days


DATE k DATE Date when the accounting records were collected by SMF. Forthe _W table, this is the date of the first day of the week.From SM101DTE.

TIME k TIME Time when the accounting records were collected by SMF. Itapplies only to the _H table. From SM101TME®.

PERIOD_NAME k CHAR(8) Name of the period. This is derived by using fieldsSM100DTE and SM100TME as parameters in the PERIODfunction.


DB2_SYSTEM_ID k CHAR(4) DB2 system ID. This is the SMF subsystem ID. FromSM101SSI.

LOCAL_LOCATION k CHAR(16) Location name of the local location associated with theaccounting records. From QWHSLOCN.

REMOTE_LOCATION k CHAR(16) Location name of the remote location associated with theaccounting records. For DRDA® connections, this columncontains the string DRDA REMOTE LOCS. FromQLACLOCN.

APPLICATION_NAME k CHAR(18) Name of the application. From APPLICATION_NAME in theDB2_APPLICATION lookup table.

Note: Only the key columns of these tables are described here. These tables alsocontain all the data columns described in “DB2_USER_DIST_H, _D, _W” onpage 97.

51

DB2_APPLICATION_H, _WThese tables provide hourly and weekly statistics on DB2 transactions grouped byapplication. They contain accounting and response-time data based on SMF type101 records (DB2 accounting, IFCID 0003).


The default retention periods for these tables are:DB2_APPLICATION_H 30 daysDB2_APPLICATION_W 375 days



TIME k TIME Time (rounded down to the nearest hour) when theaccounting records were collected by SMF. It applies only tothe _H table. From SM101TME.





Note: Only the key columns of these tables are described here. These tables alsocontain all the data columns described in “DB2_USER_TRAN_H, _D, _W”on page 101.

DB2 data tables


DB2_BP_SHARING_TThis table provides statistics related to the Group buffer pool interactions.

The default retention period for this table is 30 days.


DATE k DATE Date when the system statistics record was collectedby SMF. From SM100DTE.

TIME k TIME Time when the system statistics record was collectedby SMF. From SM100TME.

TIMESTAMP k TIMESTAMP Date and time when the system address spacestatistics record was collected by SMF. FromSM100DTE and SM100TME.

SEQ_NO k INTEGER Sequence number for the SMF100 record. FromQWHSISEQ.

PERIOD_NAME k CHAR(8) Name of the period. This is derived by using fieldsSM100DTE and SM100TME as parameters in thePERIOD function.

MVS_SYSTEM_ID k CHAR(4) MVS system ID. This is the SMF system ID. FromSM100SID.


BUFFER_POOL_ID k INTEGER DB2 buffer pool ID. 0 to 49 = BP0 to BP49; 80 =BP32K; and 81 to 89 = BP32K1 to BP32K9. FromQBGLGN.

ASYN_READ_RETURN INTEGER Number of coupling facility reads for prefetch, inwhich data was returned from the coupling facility.From QBGLAD for the buffer pool.

ASYN_READ_RW_INIT INTEGER Number of coupling facility reads for prefetch, inwhich data was not returned from the coupling facilityand a coupling facility directory entry was created if itdid not already exist. From QBGLAR for the bufferpool.

CASTOUT_CLASS_THRS INTEGER Number of times group buffer pool castout wasinitiated due to the class castout threshold beingdetected. From QBGLCT for the buffer pool.

CASTOUT_ENG_UNAVAI INTEGER Number of times the castout engine was not available.From QBGLCN for the buffer pool.

CHG_PGS_ASYN_WRT INTEGER Number of changed pages asynchronously writtenfrom the member virtual pool to the group bufferpool. From QBGLAW for the buffer pool.

CHG_PGS_READ_RPL INTEGER Number of coupling facility reads to retrieve achanged page from the group buffer pool. FromQBGLAY for the buffer pool.

CHG_PGS_SYN_WRTN INTEGER Number of changed pages synchronously written fromthe member virtual pool to the group buffer pool.From QBGLSW for the buffer pool.

CLEAN_PGS_ASYN_WRT INTEGER Number of clean pages asynchronously written fromthe member virtual pool to the group buffer pool.From QBGLAC for the buffer pool.

DB2 data tables

Chapter 7. Data tables and lookup tables 53


CLEAN_PGS_READ_RPL INTEGER Number of coupling facility reads to retrieve a cleanpage from the group buffer pool. From QBGLAZ forthe buffer pool.

CLEAN_PGS_SYN_WRTN INTEGER Number of clean pages synchronously written fromthe member virtual pool to the group buffer pool.From QBGLSC for the buffer pool.

GBP_CHK_TRIGGERED INTEGER Number of GBP checkpoints triggered by this member.From QBGLCK for the buffer pool.

GBP_REBUILDS INTEGER Number of GBP rebuilds in which this memberparticipated. From QBGLRB for the buffer pool.

GET_PAGES INTEGER Number of GetPages for GBP Dep pages. FromQBGLGG, DB2 V7 or later.

GROUPBP_CAST_THRS INTEGER Number of times group buffer pool castout wasinitiated due to the group buffer pool castoutthreshold being detected. From QBGLGT for the bufferpool.

HOUR TIME Time (rounded down to the nearest hour) when therecord was collected by SMF. From SM100TME.

IXLCACHE_DEL_NAME INTEGER IXLCACHE delete-name requests. From QBGLDN.

IXLCACHE_RD_DIRINF INTEGER IXLCACHE read-dirinfo requests. From QBGLRD.

IXLCACHE_RDCST_CL INTEGER IXLCACHE read-castout-class requests. FromQBGLCC.

IXLCACHE_RDCST_ST INTEGER IXLCACHE read-castout-stats requests. FromQBGLCS.

IXLCACHE_UNLK_CST INTEGER IXLCACHE unlock-castout requests. From QBGLUN.

OTHER_REQUESTS INTEGER Number of coupling facility requests that are notcounted in any of the above fields.

PAGES_CASTOUT INTEGER Number of pages cast out from the group buffer poolto DASD. From QBGLRC for the buffer pool.

PRIM_IXL_ASYNCH INTEGER Asynchronous IXLCACHE invocations for primaryGPB. From QBGLHS, DB2 V7 or later.

READ_FAILED_NOSTOR INTEGER Number of coupling facility read requests that couldnot complete due to a lack of coupling facility storageresources. From QBGLRF for the buffer pool.

REG_PG_LIST_RPL INTEGER Number of requests to register a page list in thecoupling facility. From QBGLAX for the buffer pool.

REGISTER_PAGE_RQ INTEGER Number of register page requests. From QBGLRG.

SEC_CHECKS_SUSP INTEGER The number of completion checks for writes to thesecondary GBP that were suspended because the writehad not yet completed. From QBGL2S. DB2 V6 orlater.

SEC_CHG_PGS_FAILED INTEGER The number of writes of changed pages to thesecondary GBP that failed due to a lack of storage.From QBGL2F. DB2 V6 or later.

SEC_CHG_PGS_WRTN INTEGER The number of writes of changed pages to thesecondary GBP for duplexing. From QBGL2W. DB2 V6or later.

SEC_IXL_ASYNCH INTEGER Asynchronous IXLCACHE invocations for secondaryGPB. From QBGL2H, DB2 V7 or later.

DB2 data tables



SEC_IXL_DEL_NAME INTEGER IXLCACHE delete-name requests to the secondaryGBP. From QBGL2N. DB2 V6 or later.

SEC_IXL_DEL_NAME_L INTEGER IXLCACHE delete-name-list requests to the secondaryGBP. From QBGL2D. DB2 V6 or later.

SEC_IXL_RDCST_ST INTEGER IXLCACHE read-castout-stats requests to thesecondary GBP. From QBGL2R. DB2 V6 or later.

SYN_READ_NF_RETURN INTEGER Number of synchronous coupling facility read requestsnecessary because the requested page was not foundin the buffer pool. Data was returned from thecoupling facility. From QBGLMD for the buffer pool.

SYN_READ_NF_RW_INT INTEGER Number of synchronous coupling facility read requestsnecessary because the requested page was not foundin the buffer pool. Data is not returned from the groupbuffer pool but from DASD. From QBGLMR for thebuffer pool.

SYN_READ_XI_RETURN INTEGER Number of synchronous coupling facility read requestscaused by the page marked invalid in the memberbuffer pool. Data is returned from the group bufferpool. From QBGLXD for the buffer pool.

SYN_READ_XI_RW_INT INTEGER Number of synchronous coupling facility read requestscaused by the page marked invalid in the memberbuffer pool. Data is not returned from the groupbuffer pool but from DASD. From QBGLXR for thebuffer pool.

UNREGIST_PAGE_RQ INTEGER Number of unregistered page requests. FromQBGLDG.

WEEK_START_DATE DATE Date of the first day of the week. From SM100DTE.

WRIT_FAILED_NOSTOR INTEGER Number of coupling facility write requests that couldnot complete due to a lack of coupling facility storageresources. From QBGLWF for the buffer pool.

WRITE_ENG_UNAVAIL INTEGER Number of times that a coupling facility write enginewas not available for coupling facility writes. FromQBGLSU for the buffer pool.

DB2 data tables


DB2_BPATTR_SHR_TThis table provides detailed DB2 statistics related to Group buffer pool attributes(IFCID 230).



DATE k DATE Date when the system statistics record was collected bySMF. From SM100DTE.

TIME k TIME Time when the system statistics record was collected bySMF. From SM100TME.

TIMESTAMP k TIMESTAMP Date and time when the system address space statisticsrecord was collected by SMF. From SM100DTE andSM100TME.

SEQ_NO k INTEGER Sequence number for the SMF100 record. From QWHSISEQ.




BUFFER_POOL_ID k INTEGER DB2 buffer pool ID. 0 to 49 = BP0 to BP49; 80 = BP32K;and 81 to 89 = BP32K1 to BP32K9. From QBGBGN.

ALLOC_GBPOOL_SIZE FLOAT Allocated size of the group buffer pool in number of 4KBblocks. From QBGBGSZ for the buffer pool.

ALLOC_SEC_GBP_SIZE FLOAT The allocated size of the secondary group buffer pool, if thegroup buffer pool is duplexed. New with DB2 V6. FromQBGBSZ2.

CASTOUT_CLASS_TRS INTEGER Castout class level threshold. From QBGBGCT for the bufferpool.

CURRENT_DIR_ENTRY CHAR(6) Number of current directory entry / data entry ratio. FromQBGBGR1 for the buffer pool.

DATA_ALL_SEC_GBP FLOAT The number of allocated data entries in the secondarygroup buffer pool, if the group buffer pool is duplexed.New with DB2 V6. From QBGBGDT2.

DATA_ENTRIES_ALLOC FLOAT Actual number of allocated data entries. From QBGBGDTfor the buffer pool.

DIRECT_ALL_SEC_GBP FLOAT The number of allocated directory entries in the secondarygroup buffer pool, if the group buffer pool is duplexed.New with DB2 V6. From QBGBGDR2.

DIRECT_ENTR_ALLOC FLOAT Actual number of allocated directory entries. FromQBGBGDR for the buffer pool.

GBP_CASTOUT_TRS INTEGER Group buffer pool level threshold. From QBGBGGT for thebuffer pool.

GBP_CHECKPOINT_INT INTEGER Group buffer pool checkpoint interval in minutes. FromQBGBGCK for the buffer pool.

HOUR TIME Time (rounded down to the nearest hour) when the recordwas collected by SMF. From SM100TME.

PENDING_DIR_ENTRY CHAR(6) Number of pending directory entry / data entry ratio. FromQBGBGR2 for the buffer pool.

DB2 data tables




DB2 data tables


DB2_BUFFER_POOL_TThis table provides detailed DB2 buffer pool statistics. It contains statistics databased on SMF type 100, subtype 1 records (DB2 database services, IFCID 0002).










BUFFER_POOL_ID k INTEGER DB2 buffer pool ID. 0 to 49 = BP0 to BP49; 80 = BP32K;and 81 to 89 = BP32K1 to BP32K9. From QBSTPID.

ASYNC_PREFETCH_IO FLOAT Number of asynchronous PREFETCH read I/Os for thebuffer pool. From QBSTPIO for the buffer pool.

ASYNC_WRITE_IO FLOAT Number of asynchronous write I/Os for the buffer pool.This is the number of asynchronous write I/O operationsperformed by media manager. From QBSTWIO for thebuffer pool.

BP_EXPANSIONS INTEGER Number of buffer pool expansions required. This columnis only valid for DB2 V2. From QBSTBPX for the bufferpool.

BP_EXPANSIONS_FAIL INTEGER Number of buffer pool expansion failures because ofstorage shortage or because the maximum buffer poollimit was reached, or both. This is the sum of QBSTXFLand QBSTXFV for the buffer pool.

BUFFERS_MAX FLOAT Maximum number of allocated buffers. This column isvalid from DB2 V3 R1. From QBSTALX.

BUFFERS_NONSTEAL INTEGER Number of currently active buffers. This is the number ofbuffers in the buffer pool that were active (non stealable)at the end of the statistics interval. From QBSTCBA forthe buffer pool.

BUFFER_UPDATES FLOAT Number of times buffer update occurred for systempages. This is the number of updates performed against apage in the buffer pool. From QBSTSWS for the bufferpool.

DATASET_OPENS FLOAT Number of data set open operations performedsuccessfully for the buffer pool. From QBSTDSO for thebuffer pool.

DB2 data tables



DMTH_REACHED INTEGER Number of times that the data manager buffer criticalthreshold (DMTH) was reached for the buffer pool. FromQBSTDMC for the buffer pool.

DWQT_REACHED INTEGER Number of times that the deferred write threshold(DWQT) was reached for the buffer pool. FromQBSTDWT for the buffer pool.

DYN_PREFETCH FLOAT Number of DYNAMIC PREFETCH requests issued. Thiscolumn is valid from DB2 V3 R1. From QBSTDPF.

DYN_PREFETCH_IO FLOAT Number of asynchronous read I/Os because of thedynamic prefetch. This column is valid from DB2 V3 R1.From QBSTDIO.

DYN_PREFETCH_PAGES FLOAT Number of asynchronous page reads because of thedynamic prefetch. This column is valid from DB2 V3 R1.From QBSTDPP.

DYN_PREFETCH_ZERO INTEGER Number of times SEQUENTIAL PREFETCH was disabledfor work files because the dynamic prefetch quantity waszero. From QBSTWKPD for the buffer pool.

GETPAGE FLOAT Number of conditional and unconditional GETPAGErequests issued. From QBSTGET for the buffer pool.

GETPAGE_COND_UN FLOAT Number of times conditional GETPAGE requests couldnot be satisfied for this buffer pool. This column is validfrom DB2 V3 R1. From QBSTNGT.

GETPAGE_SEQ FLOAT Number of GETPAGE requests issued by sequentialaccess requesters. This column is valid from DB2 V3 R1.From QBSTSGT.


HPOOL_BUFFERS FLOAT Number of buffers allocated for a hiperpool. This columnis valid from DB2 V3 R1. From QBSTHPL.

HPOOL_BUFFERS_ES FLOAT Number of hiperpool buffers that are currently backed byexpanded storage. This column is valid from DB2 V3 R1.From QBSTHBE.

HPOOL_EXPAND_CONTR FLOAT Number of successful hiperpool expansions orcontractions because of the -ALTER BUFFERPOOLcommand. This column is valid from DB2 V3 R1. FromQBSTHPA.

HPOOL_READ_ADMF FLOAT Number of pages successfully moved from the hiperpoolto the virtual buffer pool by the asynchronous data moverfacility. This column is valid from DB2 V3 R1. FromQBSTARA.

HPOOL_READ_ADMF_UN FLOAT Number of pages for which a read request, using theasynchronous data mover facility, failed because thebacking expanded storage was stolen or some other erroroccurred. This column is valid from DB2 V3 R1. FromQBSTARF.

HPOOL_READ_ASYNC FLOAT Number of pages moved successfully from a hiperpool tothe virtual buffer pool asynchronously. This column isvalid from DB2 V3 R1. From QBSTHRA.

HPOOL_READ_SYNC FLOAT Number of successful synchronous requests to move apage from a hiperpool to a virtual buffer pool. Thiscolumn is valid from DB2 V3 R1. From QBSTHRE.

DB2 data tables



HPOOL_READ_UNSUCC FLOAT Number of pages for which a read request failed becausethe backing expanded storage was stolen by the system.This column is valid from DB2 V3 R1. From QBSTHRF.

HPOOL_WRIT_ADMF_UN FLOAT Number of pages for which a write request, using theasynchronous data mover facility, failed because thebacking expanded storage was stolen or some other erroroccurred. This column is valid from DB2 V3 R1. FromQBSTAWF.

HPOOL_WRITE_ADMF FLOAT Number of pages moved successfully from the virtualbuffer pool to the hiperpool by the asynchronous datamover facility. This column is valid from DB2 V3 R1.From QBSTAWA.

HPOOL_WRITE_ASYNC FLOAT Number of pages moved successfully from the virtualbuffer pool to the hiperpool asynchronously. This columnis valid from DB2 V3 R1. From QBSTHWA.

HPOOL_WRITE_SYNC FLOAT Number of successful synchronous requests to move apage from the virtual buffer pool to the hiperpool. Thiscolumn is valid from DB2 V3 R1. From QBSTHWR.

HPOOL_WRITE_UNSUCC FLOAT Number of pages for which a write request failed becauseof a shortage of expanded storage in the system. Thiscolumn is valid from DB2 V3 R1. From QBSTHWF.

LIST_PREFETCH FLOAT Number of LIST PREFETCH requests issued for thebuffer pool. This column is valid from DB2 V2 R3.For DB2 V2 R3, this also includes DYNAMICPREFETCH requests issued. From QBSTLPF for the bufferpool.

LIST_PREFETCH_IO FLOAT Number of asynchronous read I/Os because of the listprefetch. This column is valid from DB2 V3 R1. FromQBSTLIO.

LIST_PREFETCH_PAGE FLOAT Number of asynchronous page reads because of the listprefetch. This column is valid from DB2 V3 R1. FromQBSTLPP.

NO_READ_ENGINE INTEGER Number of times SEQUENTIAL PREFETCH was disabledbecause of unavailable read engine for the buffer pool.From QBSTREE for the buffer pool.

NO_WORKFILE INTEGER Number of times that the work files required were toomany and could not be created because of insufficientbuffer pool resources. From QBSTWMAX (if DB2 V2 R2)or QBSTMAX (from DB2 V2 R3).

NO_WRITE_ENGINE INTEGER Number of times no write engine was available forasynchronous write I/O for the buffer pool. FromQBSTWEE for the buffer pool.

PAGES_UPDATED FLOAT Number of updated pages in deferred write stage. Thiscolumn is valid from DB2 V3 R1. From QBSTDWC.

PAGES_UPDATED_MAX FLOAT Maximum number of updated pages in deferred writestage. This column is valid from DB2 V3 R1. FromQBSTDWX.

PAGES_WRITTEN FLOAT Number of pages written for the buffer pool. This is thenumber of pages in the buffer pool written to DASD.From QBSTPWS for the buffer pool.

DB2 data tables



PAR_GROUP_NO_BFR FLOAT Total number of times during this statistics interval thatDB2 could not allocate the requested number of bufferpages to allow a parallel group to run to the planneddegree. This column is valid from DB2 V3 R1. FromQBSTPQF.

PAR_IO_PFQ_HALF FLOAT Total number of times that the prefetch quantity forprocessing queries in parallel was reduced from normalto one-half of the normal quantity. This column is validfrom DB2 V3 R1. From QBSTPL1.

PAR_IO_PFQ_QUARTER FLOAT Total number of times that the prefetch quantity forprocessing queries in parallel was reduced from one-halfof the normal to one-quarter of the normal quantity. Thiscolumn is valid from DB2 V3 R1. From QBSTPL2.

PAR_IO_REQUESTS FLOAT Total number of I/O requests made for processing queriesin parallel in this buffer pool. This column is valid fromDB2 V3 R1. From QBSTPQQ.

PAR_IO_STREAMS_DEN FLOAT Total number of requested prefetch I/O streams that weredenied because of storage shortage in the buffer pool.This column is valid from DB2 V3 R1. From QBSTJIS.

PAR_IO_STREAMS_MAX FLOAT Maximum number of concurrent prefetch I/O streamsthat were allocated for supporting queries processed inparallel in this buffer pool. This column is valid fromDB2 V3 R1. From QBSTXIS.

SEQ_PREFETCH_CONC INTEGER Number of times SEQUENTIAL PREFETCH was disabledbecause of concurrent sequential prefetch requests to thesame data set. This column is valid only for DB2 V2 R2.From QBSTPFDC for the buffer pool.

SEQ_PREFETCH_PAGES FLOAT Number of pages read because of SEQUENTIALPREFETCH requests issued for the buffer pool. FromQBSTSPP for the buffer pool.

SEQ_PREFETCH_REQ FLOAT Number of SEQUENTIAL PREFETCH requests issued forthe buffer pool. For DB2 V2 R2, this also includes LISTPREFETCH requests issued. From QBSTSEQ for thebuffer pool.

SPTH_REACHED INTEGER Number of times SEQUENTIAL PREFETCH was disabledbecause of unavailable buffers. The sequential prefetchthreshold (SPTH) was reached for the buffer pool. FromQBSTSPD for the buffer pool.

SYNC_READ_IO FLOAT Number of synchronous read I/O operations performed.From QBSTRIO for the buffer pool.

SYNC_READ_IO_SEQ FLOAT Number of synchronous read I/Os issued by sequentialaccess requesters. This column is valid from DB2 V3 R1.From QBSTSIO.

SYNC_WRITE_IO FLOAT Number of immediate (synchronous) write I/Os for thebuffer pool. From QBSTIMW for the buffer pool.

VDWQT_REACHED FLOAT Number of times the vertical deferred write threshold(VDWQT) was reached. This column is valid fromDB2 V3 R1. From QBSTDWV.

VPOOL_BUFFERS FLOAT Number of buffer pools allocated for a virtual buffer pool.This column is valid from DB2 V3 R1. From QBSTVPL.

DB2 data tables



VPOOL_EXPAND_CONTR FLOAT Number of successful virtual buffer pool expansions orcontractions because of the -ALTER BUFFERPOOLcommand. This column is valid from DB2 V3 R1. FromQBSTVPA.


DB2 data tables


DB2_DATABASE_TThis table provides detailed DB2 database address space statistics. It containsdatabase statistics data based on SMF type 100, subtype 1 records (DB2 databaseservices, IFCID 0002).



DATE k DATE Date when the database statistics record was collected bySMF. From SM100DTE.

TIME k TIME Time when the database statistics record was collected bySMF. From SM100TME.






ACTIV_ROW_TRIGGER INTEGER Number of times a row trigger was activated. New withDB2 V6. From QXROWTRG.

ACTIV_SQL_TRIGGER INTEGER Number of times a statement trigger was activated. Newwith DB2 V6. From QXSTTRG.

AUTH_ADD_FAILED INTEGER Number of times DB2 was not able to add an entry to theroutine authorization cache. New with DB2 V6. FromQTRACNAC.

AUTH_CHECK_ATTEMPT INTEGER Number of authorization check attempts. This is thenumber of authorization checks performed for a plan.From QTAUCHK.

AUTH_CHECKS_NO_CAT INTEGER Number of successful authorization checks that did notuse the catalog. This includes plan cache checks andpublic authorization checks. From QTAUCCH.

AUTH_CHECKS_PUBLIC INTEGER Number of successful authorization checks based onexecute authority granted to the public. From QTAUPUB.

AUTH_CHECKS_RT_NCH INTEGER Number of authorization checks for routines that couldnot make use of the routine authorization cache. Newwith DB2 V6. From QTRACNOT.

AUTH_CHECKS_RT_NCT INTEGER Number of successful authorization checks for routinesthat did not use the catalog. This includes authorizationchecks using routine authorization information from thecache and public authorization checks. New with DB2 V6.From QTRACAUT.

AUTH_CHECKS_RT_PUB INTEGER Number of successful authorization checks for routinesbased on execute authorization granted to public. Newwith DB2 V6. From QTRACPUB.

AUTH_CHECKS_SUCC INTEGER Number of successful authorization checks performed fora plan. From QTAUSUC.

DB2 data tables



AUTH_ID_OVRWRTTN INTEGER Number of times DB2 overwrote an authorization ID inthe routine authorization cache. New with DB2 V6. FromQTRACOW1.

AUTH_RTN_OVRWRTTN INTEGER Number of times DB2 overwrote a routine entry in theroutine authorization cache. New with DB2 V6. FromQTRACOW2.

AUTO_BIND_ATTEMPTS INTEGER Number of times automatic bind was attempted. FromQTABINDA.

AUTO_BINDS_INV_ID INTEGER Number of automatic binds with invalid resource IDs.This is the number of automatic bind attempts that didnot complete successfully because of a nonexistent planID. From QTINVRID.

AUTO_BINDS_SUCC INTEGER Number of successful automatic binds. This is the numberof automatic bind attempts that completed successfully.From QTABIND.

BIND_ADD_SUBC INTEGER Number of bind ADD subcommands issued (successful orunsuccessful). From QTBINDA.

BIND_REPLACE_SUBC INTEGER Number of bind REPLACE subcommands (successful orunsuccessful). From QTBINDR.

BINDS_TEST INTEGER Number test binds. This is the number of bindsubcommands issued without a plan ID. From QTTESTB.

CHANGE_REQUESTS FLOAT Number of IRLM change requests issued. FromQTXACHG.

CLAIMS FLOAT Number of claim requests issued. This column is validfrom DB2 V3 R1. From QTXACLNO.

CLAIMS_UNSUCC FLOAT Number of unsuccessful claim requests issued. Thiscolumn is valid from DB2 V3 R1. From QTXACLUN.

CPU_HIGH_USED INTEGER Highest CPU time (in 16-microsecond timer units) used ina successful DB2 call, rather than a single SQL call. This isthe maximum of QTXACHUS.

CPU_LIMIT INTEGER Maximum CPU 16-microsecond timer units that can beused for a thread. From QTXACLMT.

DATASETS_OPEN_CUR INTEGER Number of data sets currently open. From QTDSOPN.

DATASETS_OPEN_MAX INTEGER Maximum number of data sets concurrently opened sincethe time DB2 was last started. This is the maximum ofQTMAXDS.

DB2_SKIPPED INTEGER Number of times that the parallelism coordinator had tobypass a DB2 when distributing tasks because there wasnot enough buffer pool storage on one or more DB2members. From QXXCSKIP.

DCL_GLB_TEMP_TBL INTEGER Number of DECLARE GLOBAL TEMPORARY TABLEstatements executed. From QXDCLGTT, DB2 V7 or later.

DEADLOCKS INTEGER Number of times deadlocks were detected. FromQTXADEA.

DRAINS FLOAT Number of drain requests issued. This column is validfrom DB2 V3 R1. From QTXADRNO.

DRAINS_UNSUCC FLOAT Number of unsuccessful drain requests issued. Thiscolumn is valid from DB2 V3 R1. From QTXADRUN.

EDM_INS_DYN_CACHE INTEGER Number of INSERTS for dynamic cache. From QISEDSI.

DB2 data tables



EDM_LOAD_CT_SECT FLOAT Number of EDM load cursor table sections from DASD.From QISECTL.

EDM_LOAD_DBD FLOAT Number of EDM load database descriptors from DASD.From QISEDBDL.

EDM_LOAD_PT_SECT FLOAT Number of EDM load package table sections from DASD.From QISEKTL.

EDM_PAGES_CT FLOAT Number of pages used for the cursor tables. FromQISECT.

EDM_PAGES_DBD FLOAT Number of pages used for database descriptors. FromQISEDBD.

EDM_PAGES_FREE FLOAT Number of pages in the free chain. From QISEFREE.

EDM_PAGES_PT FLOAT Number of pages used for the package table. FromQISEKT.

EDM_PAGES_SKCT FLOAT Number of pages used for skeleton cursor tables. FromQISESKCT.

EDM_PAGES_SKPT FLOAT Number of pages used for the skeleton package table.From QISEKPT.

EDM_PG_DYN_CACHE INTEGER Number of PAGES used for dynamic cache. FromQISEDSC.

EDM_POOL_FULL INTEGER Number of failures because the EDM pool was full. FromQISEFAIL.

EDM_POOL_SIZE FLOAT Number of pages in the EDM pool. From QISEPAGE.

EDM_REQ_CT_SECT FLOAT Number of EDM requests for cursor table sections. FromQISECTG.

EDM_REQ_DBD FLOAT Number of EDM requests for database descriptors. FromQISEDBDG.

EDM_REQ_DYN_CACHE INTEGER Number of REQUESTS for dynamic cache. FromQISEDSG.

EDM_REQ_PT_SECT FLOAT Number of EDM requests for package table sections.From QISEKTG.

FREE_ATTEMPTS INTEGER Number of attempts to free a plan. This column can havea value larger than that in FREE_SUBC because multipleplan IDs can be specified on a single FREE subcommand.From QTFREEA.

FREE_SUBC INTEGER Number of FREE subcommands issued. From QTFREE.

GLB_TT_PAR_GROUPS INTEGER Total number of parallel groups that are part of a queryblock using a UDF and executed on a single DB2 due tothe existence of a Declared Temporary Table in theapplication process. From QXDEGDTT, DB2 V7 or later.


INCREMENTAL_BINDS INTEGER Number of incremental binds excluding prepares. FromQXINCRB.

LATCH_SUSPENDS FLOAT Number of latch suspends. This is the number of times alock could not be obtained because of a latch conflict andthe unit of work was suspended. From QTXASLAT.

LOCK_ESCAL_EXCL INTEGER Number of lock escalations to exclusive mode. FromQTXALEX.

DB2 data tables



LOCK_ESCAL_SHARED INTEGER Number of lock escalations to shared mode. FromQTXALES.

LOCK_REQUESTS FLOAT Number of IRLM lock requests issued. From QTXALOCK.

LOCK_SUSPENDS INTEGER Number of lock suspends. This is the number of times alock could not be obtained because of a lock conflict andthe unit of work was suspended. From QTXASLOC.

LOCK_TIMEOUTS INTEGER Number of lock time-outs. This is the number of times aunit of work was suspended for a time that exceeded thetime-out value. From QTXATIM.

MAX_NESTING_SQL INTEGER Maximum level of nesting of user-defined functions,stored procedures and triggers. New with DB2 V6. FromQXCASCDP.

MAX_STORAGE_LOB INTEGER Maximum storage used for LOB values, in MB. New withDB2 V6. From QXSTLOBV.

OTHER_IRLM_REQ FLOAT Number of other IRLM requests issued. FromQTXAIRLM.

OTHER_SUSPENDS FLOAT Number of other suspends. This is the number of times alock could not be obtained because of a conflict otherthan a lock or latch conflict. From QTXASOTH.

PAGE_LOCKS_MAX INTEGER Maximum number of page locks concurrently heldagainst all table spaces by a single application when itwas executed. This is the maximum of QTXANPL.

PAR_COORD INTEGER Total number of parallel groups that were processed on asingle DB2 due to the COORDINATOR subsystemparameter being set to NO. From QXCOORNO.

PAR_DEGREE_AS_PLAN INTEGER Total number of parallel groups that were processed tothe planned parallel degree. This column is valid fromDB2 V3 R1. From QXNORGRP.

PAR_DEGREE_LT_PLAN INTEGER Total number of parallel groups that were processed to aparallel degree less than planned because of storageshortage or contention on the buffer pool. This column isvalid from DB2 V3 R1. From QXREDGRP.

PAR_DEGREE_MAX INTEGER Maximum degree of parallel I/O processing executedamong all parallel groups. This indicates the extent towhich queries were processed in parallel. This column isvalid from DB2 V3 R1. From QXMAXDEG.

PAR_FALLBACK_BFR INTEGER Total number of parallel groups that fall back tosequential operation due to storage shortage or contentionon a buffer pool. This column is valid from DB2 V3 R1.From QXDEGBUF.

PAR_FALLBACK_ESA INTEGER Total number of parallel groups that fall back tosequential operation due to a lack of ESA sort support.This column is valid from DB2 V3 R1. From QXDEGESA.

PAR_FALLBACK_UPDEL INTEGER Total number of parallel groups that fall back tosequential operation due to a cursor that can be used forupdate or delete. From QXDEGCUR.

PAR_GRP_EXECUTED INTEGER Total number of parallel groups that were processed. Thiscolumn is valid from DB2 V3 R1. From QXTOTGRP.

PAR_ISOL INTEGER Total number of parallel groups that were processed on asingle DB2 due to repeatable-read or read-stabilityisolation. From QXISORR.

DB2 data tables



PAR_TO_RUN INTEGER Total number of parallel groups that were intended to runacross the data sharing group. This count is incrementedonly on the parallelism coordinator at run time. FromQXXCBPNX.

PAR_UNAVAIL INTEGER Total number of parallel groups that were processed insequential mode due to the unavailable enclave service.From QXDEGENC.

PKG_ALLOC_ATTEMPTS INTEGER Number of attempts to allocate a package. (A packageallocation is a request to allocate a bound package for anagent.) From QTPKALLA.

PKG_ALLOCATED INTEGER Number of packages successfully allocated. FromQTPKALL.

PKG_AUTOBIND_ATT INTEGER Number of automatic binds attempted on a package.From QTAUTOBA.

PKG_AUTOBOUND INTEGER Number of successful automatic bind packages. FromQTPKABND.

PKG_BIND_ADD_SUBC INTEGER Number of bind ADD PACKAGE subcommands issued(successful or unsuccessful). From QTBINDPA.

PKG_BIND_REPL_SUBC INTEGER Number of bind REPLACE PACKAGE subcommandsissued (successful or unsuccessful). From QTBINDPA.

PKG_BOUND INTEGER Number of packages successfully bound and kept forfuture package allocations. From QTPKGBD.

PKG_FREE_ATTEMPTS INTEGER Number of attempts to free a package. The value in thiscolumn can be greater than that in PKG_FREE_SUBCbecause you can free multiple packages in a singlesubcommand. From QTFREEAP.

PKG_FREE_SUBC INTEGER Number of FREE PACKAGE subcommands issued. FromQTFREEP.

PKG_FREED INTEGER Number of packages successfully freed. FromQTPKGFRD.

PKG_REBIND_ATTEMPT INTEGER Number of attempts to rebind a package. The value inthis column can be larger than that inPKG_REBIND_SUBC because you can rebind multiplepackages in a single subcommand. From QTRBNDPA.

PKG_REBIND_SUBC INTEGER Number of rebind PACKAGE subcommands issued. FromQTRBINDP.

PKG_REBOUND INTEGER Number of packages successfully rebound. FromQTPKGRBD.

PLAN_ALLOC_ATTEMPT INTEGER Number of plan allocation attempts. This is the numberof times DB2 was requested to create a thread by theattachment facility for the user. From QTALLOCA.

PLAN_ALLOC_SUCC INTEGER Number of successful plan allocations. This is the numberof times DB2 successfully completed the request to createa thread by the attachment facility for the user. FromQTALLOC.

PLANS_BOUND INTEGER Number of plans successfully bound and kept for futureagent allocations. From QTPLNBD.

PLANS_FREED INTEGER Number of plans freed. This is the number of freeattempts that completed successfully. From QTPLNFRD.

DB2 data tables



PLANS_REBOUND INTEGER Number of plans rebound. This is the number of rebindattempts that completed successfully. From QTPLNRBD.

PREPARE_DISC_PARM INTEGER Number of times that an application process executablecopy of a prepared statement was discarded due to theMAXKEEPD system limit being exceeded. FromQXSTDEXP.

PREPARE_DISC_PROG INTEGER Number of times that a prepared statement was purgedfrom the cache because a DROP, ALTER, or REVOKEstatement was issued on a dependent object. FromQXSTDINV.

PREPARE_FOUND INTEGER Number of times a PREPARE request was satisfied bymaking a copy from the prepared statement cache. FromQXSTFND.

PREPARE_IMPLICIT INTEGER Number of times an implicit PREPARE request wasperformed because the KEEPDYNAMIC(YES) option wasused but DB2 no longer had a valid copy of theexecutable version of the prepared statement. FromQXSTIPRP.

PREPARE_NOT_FOUND INTEGER Number of times a PREPARE request was received but amatching statement was not found in the preparedstatement cache. Cache search is done only for DML SQLand only if cache option is active. From QXSTNFND.

PREPARE_OLD_VALID INTEGER Number of times that a PREPARE request was avoidedbecause KEEPDYNAMIC(YES) was used along withprepare statement caching and DB2 still had theapplication process copy of the executable version of theprepared statement. From QXSTNPRP.

QUERY_REQUESTS FLOAT Number of IRLM query requests issued. From QTXAQRY.

REBIND_ATTEMPTS INTEGER Number of attempts to rebind a plan. This column cancontain a value larger than that in REBIND_SUBCbecause multiple plan IDs can be specified on a singleREBIND subcommand. From QTRBINDA.

REBIND_SUBC INTEGER Number of REBIND subcommands issued. FromQTREBIND.

REFORM_PAR_GRP_1 INTEGER Number of parallel groups for which DB2 reformulatedthe parallel plan because the sysplex configurationchanged at run time from the sysplex configuration atbind time. New with DB2 V6. From QXREPOP1.

REFORM_PAR_GRP_2 INTEGER Number of parallel groups for which DB2 reformulatedthe parallel plan because the buffer pool resourceschanged at run time from the buffer pool resources atbind time. New with DB2 V6. From QXREPOP2.

RID_LIST_EXCEEDS INTEGER Number of times one or more RID lists were not used fora given RID list process because the number of RIDsexceeded one or more internal limits. This column is validfrom DB2 V2 R3. From QXMRMIAP.

RID_LIST_NOT_USED INTEGER Number of times a RID list was not used for a given RIDlist process because no storage was available to hold thelist of RIDs. This column is valid from DB2 V2 R3. FromQXNSMIAP.

DB2 data tables



RID_LIST_USED INTEGER Number of times RID list processing was used. Thiscolumn is incremented once for a given table access whenRID list processing is used for index access with listprefetch or for multiple index access. This column is validfrom DB2 V2 R3. From QXMIAP.

ROWID_ACC_TO_IDX INTEGER Number of times that DB2 tried to use direct row accessbut used an index instead. New with DB2 V6. FromQXROIIDX.

ROWID_ACC_TO_TS INTEGER Number of times that DB2 tried to use direct row accessbut used a table space scan instead. New with DB2 V6.From QXROITS.

ROWID_SUCC_ACC INTEGER Number of times that DB2 used direct row accesssuccessfully. New with DB2 V6. From QXROIMAT.

SERVICE_UNIT_LIMIT INTEGER Maximum number of MVS service units that can be usedfor a thread. From QTXASLMT.

SQL_ALLOC_CURSOR INTEGER Number of SQL ALLOCATE CURSOR statements issued.From QXALOCC.

SQL_ALTER_DATABASE INTEGER Number of SQL ALTER DATABASE statements issued.From QXALDAB.

SQL_ALTER_FUNCTION INTEGER Number of ALTER FUNCTION (alter user-definedfunction) statements executed. New with DB2 V6. FromQXALUDF.

SQL_ALTER_INDEX INTEGER Number of SQL ALTER INDEX statements issued. FromQXALTIX.

SQL_ALTER_PROC INTEGER Number of ALTER PROCEDURE statements executed.New with DB2 V6. From QXALPRO.

SQL_ALTER_STOGROUP INTEGER Number of SQL ALTER STOGROUP statements issued.From QXALTST.

SQL_ALTER_TABLE INTEGER Number of SQL ALTER TABLE statements issued. FromQXALTTA.

SQL_ALTER_TS INTEGER Number of SQL ALTER TABLESPACE statements issued.From QXALTTS.

SQL_ASSOC_LOC INTEGER Number of SQL ASSOCIATE LOCATOR statementsissued. From QXALOCL.

SQL_CALL INTEGER Number of SQL CALL statements executed. FromQXCALL.

SQL_CALL_ABNRM_END INTEGER Number of times an SQL CALL statement abnormallyended. From QXCALLAB.

SQL_CALL_REJECTED INTEGER Number of times an SQL CALL statement was rejected.From QXCALLRJ.

SQL_CALL_TIMED_OUT INTEGER Number of times an SQL CALL statement timed outwaiting to be scheduled. From QXCALLTO.

SQL_CLOSE INTEGER Number of SQL CLOSE cursor statements issued. FromQXCLOSE.

SQL_COMMENT_ON INTEGER Number of SQL COMMENT ON statements issued. FromQXCMTON.

SQL_CONNECT_TYPE1 INTEGER Number of SQL CONNECT type 1 statements issued.This column is valid from DB2 V3 R1. From QXCON1.

DB2 data tables



SQL_CONNECT_TYPE2 INTEGER Number of SQL CONNECT type 2 statements issued.This column is valid from DB2 V3 R1. From QXCON2.

SQL_CREATE_ALIAS INTEGER Number of SQL CREATE ALIAS statements issued. FromQXCRALS.

SQL_CREATE_AUX INTEGER Number of CREATE AUXILIARY TABLE statementsexecuted. New with DB2 V6. From QXCRATB.

SQL_CREATE_DATABAS INTEGER Number of SQL CREATE DATABASE statements issued.From QXCRDAB.

SQL_CREATE_FUNCT INTEGER Number of CREATE FUNCTION (create user-definedfunction) statements executed. New with DB2 V6. FromQXCRUDF.

SQL_CREATE_GLOBAL INTEGER Number of SQL CREATE GLOBAL statements issued.From QXCRGTT.

SQL_CREATE_INDEX INTEGER Number of SQL CREATE INDEX statements issued. FromQXCRINX.

SQL_CREATE_STG INTEGER Number of SQL CREATE STOGROUP statements issued.From QXCRSTG.

SQL_CREATE_SYNONYM INTEGER Number of SQL CREATE SYNONYM statements issued.From QXCRSYN.

SQL_CREATE_TABLE INTEGER Number of SQL CREATE TABLE statements issued. FromQX1CRTAB

SQL_CREATE_TRIGGER INTEGER Number of CREATE TRIGGER statements executed. Newwith DB2 V6. From QXCTRIG.

SQL_CREATE_TS INTEGER Number of SQL CREATE TABLESPACE statementsissued. From QXCTABS.

SQL_CREATE_VIEW INTEGER Number of SQL CREATE VIEW statements issued. FromQXDEFVU.

SQL_CRT_DIST_TYPE INTEGER Number of CREATE DISTINCT TYPE statementsexecuted. New with DB2 V6. From QXCDIST.

SQL_CRT_PROCEDURE INTEGER Number of CREATE PROCEDURE statements executed.New with DB2 V6. From QXCRPRO.

SQL_DELETE INTEGER Number of SQL DELETE statements issued. FromQXDELET.

SQL_DESCRIBE INTEGER Number of SQL DESCRIBE statements issued. FromQXDESC.

SQL_DESCRIBE_TABLE INTEGER Number of SQL DESCRIBE TABLE statements issued.This column is valid from DB2 V2 R3. From QXDSCRTB.

SQL_DROP_ALIAS INTEGER Number of SQL DROP ALIAS statements issued. FromQXDRPAL.

SQL_DROP_DATABASE INTEGER Number of SQL DROP DATABASE statements issued.From QXDRPDB.

SQL_DROP_DIST_TYPE INTEGER Number of DROP DISTINCT TYPE statements executed.New with DB2 V6. From QXDDIST.

SQL_DROP_FUNCTION INTEGER Number of DROP FUNCTION (drop user-definedfunction) statements executed. New with DB2 V6. FromQXDRPFN.

SQL_DROP_INDEX INTEGER Number of SQL DROP INDEX statements issued. FromQXDRPIX.

DB2 data tables



SQL_DROP_PACKAGE INTEGER Number of SQL DROP PACKAGE statements issued.From QXDRPPKG.

SQL_DROP_PROCEDURE INTEGER Number of DROP PROCEDURE statements executed.New with DB2 V6. From QXDRPPR.

SQL_DROP_STOGROUP INTEGER Number of SQL DROP STOGROUP statements issued.From QXDRPST.

SQL_DROP_SYNONYM INTEGER Number of SQL DROP SYNONYM statements issued.From QXDRPSY.

SQL_DROP_TABLE INTEGER Number of SQL DROP TABLE statements issued. FromQXDRPTA.

SQL_DROP_TRIGGER INTEGER Number of DROP TRIGGER statements executed. Newwith DB2 V6. From QXDRPTR.

SQL_DROP_TS INTEGER Number of SQL DROP TABLESPACE statements issued.From QXDRPTS.

SQL_DROP_VIEW INTEGER Number of SQL DROP VIEW statements issued. FromQXDRPVU.

SQL_FETCH INTEGER Number of SQL FETCH cursor statements issued. FromQXFETCH.

SQL_FREE_LOCATOR INTEGER Number of FREE LOCATOR statements executed. Newwith DB2 V6. From QXFREEL.

SQL_GRANT INTEGER Number of SQL GRANT statements issued. FromQXGRANT.

SQL_HOLD_LOCATOR INTEGER Number of HOLD LOCATOR statements executed. Newwith DB2 V6. From QXHOLDL.

SQL_INSERT INTEGER Number of SQL INSERT statements issued. FromQXINSRT.

SQL_LABEL_ON INTEGER Number of SQL LABEL ON statements issued. FromQXLABON.

SQL_LOCK_TABLE INTEGER Number of SQL LOCK TABLE statements issued. FromQXLOCK.

SQL_OPEN INTEGER Number of SQL OPEN cursor statements issued. FromQXOPEN.

SQL_PREPARE INTEGER Number of SQL PREPARE statements issued. FromQXPREP.

SQL_RELEASE INTEGER Number of SQL RELEASE statements issued. This columnis valid from DB2 V3 R1. From QXREL.

SQL_RENAME INTEGER Number of SQL RENAME statements issued. FromQXRNTAB.

SQL_REVOKE INTEGER Number of SQL REVOKE statements issued. FromQXREVOK.

SQL_SELECT INTEGER Number of SQL SELECT statements issued. FromQXSELECT.

SQL_SET_CONNECTION INTEGER Number of SQL SET CONNECTION statements issued.This column is valid from DB2 V3 R1. From QXSETCON.

SQL_SET_CUR_DEGREE INTEGER Number of SQL SET CURRENT DEGREE statementsissued. This column is valid from DB2 V3 R1. FromQXSETCDG.

DB2 data tables



SQL_SET_CURR_PATH INTEGER Number of SET CURRENT PATH statements executed.New with DB2 V6. From QXSETPTH.

SQL_SET_CURR_PREC INTEGER Number of SQL SET CURRENT PRECISION statementsexecuted. From QXSETCPR, DB2 V7 or later.

SQL_SET_CUR_RULES INTEGER Number of SQL SET CURRENT RULES statementsissued. From QXSETCRL.

SQL_SET_CUR_SQLID INTEGER Number of SQL SET CURRENT SQLID statements issued.From QXSETSQL.

SQL_SET_HOST_VAR INTEGER Number of SQL SET HOST VARIABLE statements issued.This column is valid from DB2 V2 R3. From QXSETHV.

SQL_UPDATE INTEGER Number of SQL UPDATE statements issued. FromQXUPDTE.

TRIGGER_ERRORS INTEGER Number of times an error occurred during execution of atriggered action. New with DB2 V6. From QXTRGERR.

UDF_ABENDED INTEGER Number of times a user-defined function abnormallyterminated. New with DB2 V6. From QXCAUDAB.

UDF_EXECUTED INTEGER Number of user-defined functions executed. New withDB2 V6. From QXCAUD.

UDF_REJECTED INTEGER Number of times a user-defined function was rejected.New with DB2 V6. From QXCAUDRJ.

UDF_TIMED_OUT INTEGER Number of times a user-defined function timed outwaiting to be scheduled. New with DB2 V6. FromQXCAUDTO.

UNLOCK_REQUESTS FLOAT Number of IRLM unlock requests issued. FromQTXAUNLK.


DB2 data tables


DB2_LOCK_SHARING_TThis table provides detailed DB2 statistics related to data sharing locks.










ASYN_XES_RESOURCES INTEGER Number of resources propagated by IRLM to MVS XESasynchronously. This number indicates the number oflock-related requests that were propagated to XESasynchronously. From QTGSKIDS for the buffer pool.


INCOMP_RETAIN_LOCK INTEGER Number of global lock or change requests denied due toan incompatible retained lock. From QTGSDRTA for thebuffer pool.

LOCK_CHNG_DUR_NEG INTEGER Number of CHANGEP requests issued. From QTGSCHNPfor the buffer pool.

LOCK_NOTIFY_ENGIN INTEGER Maximum number of engines available for P-lock exitrequests or notify exit requests. From QTGSPEMX for thebuffer pool.

LOCK_NTFY_ENG_AV INTEGER Number of times an engine is not available for a P-lockexit request or a notify exit request. From QTGSPEQW forthe buffer pool.

NOTIFY_MSG_REC INTEGER Number of notify messages received. From QTGSNTFR forthe buffer pool.

NOTIFY_MSG_SENT INTEGER Number of notify messages sent. From QTGSNTFY for thebuffer pool.

OTHER_LOCK_NEG INTEGER Number of times this DB2 was driven to negotiate anotherP-lock type (other than pageset/partition or page). FromQTGSOTPE for the buffer pool.

P_LOCK_REQ_CHANGE INTEGER Number of change requests issued for physical locks. FromQTGSCPLK for the buffer pool.

P_LOCK_REQ_LOCK INTEGER Number of lock requests issued for physical locks. FromQTGSLPLK for the buffer pool.

DB2 data tables



P_LOCK_REQ_UNLOCK INTEGER Number of unlock requests issued for physical locks. FromQTGSUPLK for the buffer pool.

PAGE_NEGOTIATION INTEGER Number of times this DB2 was driven to negotiate a pageP-lock to negotiate a page P-lock contention. FromQTGSPGPE for the buffer pool.

PSET_PART_NEGOTIAT INTEGER Number of times this DB2 was driven to negotiate apageset/partition P-lock due to changing inter-DB2 interestlevels on the pageset/partition. From QTGSPPPE for thebuffer pool.

SYNCH_XES_CHANGE INTEGER Number of logical and physical change requestspropagated to MVS XES synchronously. From QTGSCSLMfor the buffer pool.

SYNCH_XES_LOCK INTEGER Number of logical and physical lock requests propagatedto MVS XES synchronously. From QTGSLSLM for thebuffer pool.

SYNCH_XES_UNLOCK INTEGER Number of logical and physical unlock requestspropagated to MVS XES synchronously. From QTGSUSLMfor the buffer pool.

TOTAL_SUSPENDS INTEGER Total number of suspensions caused by IRLM globalresource contention, MVS XES global resource contention,and false contention. From(QTGSIGLO+QTGSSGLO+QTGSFLSE) for the buffer pool.


DB2 data tables


DB2_PACKAGE_H, _D, _WThese tables provide hourly, daily, and weekly statistics on DB2 Packages/DBRMsgrouped by DB2 Plan, Package collection ID, and Package. They containaccounting and response-time data based on SMF type 101 records (DB2accounting, IFCID 0003, 0239).

The default retention periods for these tables are:DB2_PACKAGE_H 7 daysDB2_PACKAGE_D 30 daysDB2_PACKAGE_W 375 days







DB2_PLAN k CHAR(8) Plan name. From QWHCPLAN.

PKG_COLN_ID k CHAR(18) Package collection ID value. From QPACCOLN.

DB2_PACKAGE k CHAR(18) Package name. From QPACPKID.

PACKAGE_SQL REAL Number SQL issued by Package/DBRM. From QPACSQLC.

PKG_ARCH_LOG_SEC REAL Wait time for Archive read from tape. From QPACAWAR.

PKG_ARCH_QUI_SEC REAL Wait time caused by processing ARCHIVE LOG(QUIESCE)commands. From QPACALOG.

PKG_DRN_LOCK_SEC REAL Wait time for a drain lock. From QPACAWDR.

PKG_DRN_WAIT_SEC REAL Wait time for a drain when waiting for claims to be released.From QPACAWCL.

PKG_ELAPSED_SEC REAL Total elapsed time. From QPACSCT.

PKG_IO_SEC REAL I/O wait time for Thread while executing thePackage/DBRM. From QPACAWTI.

PKG_LATCH_SEC REAL Lock and latch wait times. From QPACAWTL.

PKG_PAGE_LATCH_SEC REAL Page latch contention wait time. From QPACAWTP.

PKG_READ_IO_SEC REAL Wait time for read I/O. From QPACAWTR.

PKG_S_SWITCH_SEC REAL Time spent waiting due to synchronous execution switch toDB2 services. From QPACAWTE.

PKG_SH_IRLMNFY_SEC REAL Accumulated elapsed waiting time sending of IRLM notifymessages. This value is calculated if accounting class 8 isstarted and if DB2 is a member of a DB2 DATA SHARINGgroup. From QPACAWTG.

PKG_SH_LCKCONT_SEC REAL Accumulated elapsed waiting time due to global lockcontentions for parent L-locks. This value is calculated ifaccounting class 8 is started and if DB2 is a member of a DB2DATA SHARING group. From QPACAWTJ.

DB2 data tables



PKG_SP_SCHEDUL_SEC REAL Accumulated elapsed waiting time for stored procedures tobe scheduled. This value is calculated for STOREDPROCEDURES if accounting class 8 is started. FromQPACCAST.

PKG_TCB_SEC REAL Total TCB time. From QPACTJST.

PKG_TOT_WAIT_SEC REAL Total waiting times for all class 8 suspensions. From(QPACAWTI + QPACAWTL + QPACAWTR + QPACAWTW +QPACAWTE + QPACAWCL + QPACAWDR + QPACAWTP +QPACAWAR + QPACALOG).

PKG_WRITE_IO_SEC REAL Wait time for write I/O. From QPACAWTW.

PKG_UDF_SCHEDL_SEC REAL Total elapsed time spent waiting for an available TCB beforethe user-defined function could be scheduled. This value iscalculated for user defined functions if accounting class 8 isstarted. New with DB2 V6. From QPACUDST

SUSP_COUNT REAL Number of suspensions. From QWACABRT.

DB2 data tables


DB2_SHARING_INITThis table provides statistics on the Data Sharing group initialization parametersblock. It contains data from SMF type 102 records (DB2 system parameters,IFCID 0106).



DATE k DATE Date when the system parameters records were collected by SMF.From SM102DTE.

TIME k TIME Time when the system parameters records were collected by SMF.From SM102TME.


DB2_SYSTEM_ID k CHAR(4) DB2 system ID. This is the SMF subsystem ID. From SM102SSI.

GROUP_NAME CHAR(8) Name of a new or existing DB2 Data Sharing group. FromQWPAGRPN.

IMMED_WRITE_FL CHAR(1) IMMEDWRITE override flag. From QWPAIMMW, DB2 V7 or later.Values for all plans or packages are:Y YESP PH1N or other value

NO (default)

MAX_NR_MEMBERS INTEGER Maximum number of members. It is set to 248. FromQWPAMAXM.

MEMBER_NAME CHAR(8) Name of a new or existing DB2 Data Sharing member. FromQWPAMBRN.

PARALLEL_COORD CHAR(1) Indicates whether this DB2 can be a parallelism coordinator. If thisvalue is Y, this DB2 member can send parallel tasks to eligible DB2members. From QWPACOOR.

DB2 data tables


DB2_SYS_PARAMETERThis table provides statistics on DB2 system start-up parameters in effect whentrace started (DSNZPARM). It contains performance data from SMF type 102records (DB2 system parameters, IFCID 0106).



DATE k DATE Date when the system parameters records were collected bySMF. From SM102DTE.

TIME k TIME Time when the system parameters records were collectedby SMF. From SM102TME.



ACCTG_TRACE_CLASS CHAR(8) SMF start trace option for accounting trace classes. FromQWP1SMFA.

ALLIED_THREADS_MAX INTEGER Maximum number of concurrent allied threads. Thisincludes threads for IMS, CICS, TSO (foreground andbatch), utilities, and database access threads. FromQWP1CT.

ARCHIVE_OPTION CHAR(1) Indicates whether the archive log initialization option isused. This is set to X'80' (yes) or X'00' (no). FromQWP2OPT2.

AUDIT_TRACE_CLASS CHAR(8) Start trace option for audit trace classes. From QWP1AUDT.

BATCH_CONNECTS_MAX INTEGER Maximum number of concurrent connections from batchjobs and utilities. From QWP1IDB.

BP0_SIZE_MAX INTEGER Maximum size of buffer pool 0, in number of 4-kilobytebuffers. This column is valid only for DB2 V2. FromQWP5BPMX when the buffer pool ID (QWP5BPID) = 0.

BP0_SIZE_MIN INTEGER Minimum size of buffer pool 0, in number of 4-kilobytebuffers. This column is valid only for DB2 V2. FromQWP5BPMN when the buffer pool ID (QWP5BPID) = 0.







DB2 data tables



CHECKPOINT_FREQ INTEGER Number of log records written between checkpoints. FromQWP1LOGL.

DATASETS_OPEN_MAX INTEGER Maximum number of concurrently open data sets beforethe deferred close process of DB2. From QWP4DSMX.

EDM_POOL_DSIZE_MAX INTEGER Maximum size of the EDM pool data space. Calculatedduring installation. New with DB2 V6. From QWP4EDDS.

EDMPOOL_MAX_DATSP INTEGER Maximum size of the EDM pool data space. FromQ7P4EDMX, DB2 V7 or later.

EDM_POOL_SIZE_MAX INTEGER Maximum size of the EDM pool, in kilobytes. FromQWP4EDPL.

GLOBAL_TRACE_CLASS CHAR(8) Start trace option for global trace classes. From QWP1TRST.

KB_LOB_AGENT INTEGER The kilobytes for LOB values, per agent. New with DB2 V6.From QWP1LVA.

LOCKS_ALL_MAX INTEGER Maximum number of page locks that can be heldconcurrently by a thread against all table spaces in thesystem. From QWP4LKUS.

LOCKS_SINGLE_MAX INTEGER Maximum number of page locks that can be heldconcurrently by a thread against a single table space. FromQWP4LKTS.

LOG_INPUT_BFR_SIZE INTEGER Log input buffer pool size, in kilobytes. From QWP2IBPS.

LOG_OPTION CHAR(1) Active log and BSDS initialization option used. First optionis SINGLE or DUAL ACTIVE LOG. Second option isOFFLOAD ON or OFF. Third option is SINGLE or DUALBSDS. From QWP2OPT1.

LOG_OPUT_BFR_SIZE INTEGER Log output buffer pool size for writing active log data sets,in kilobytes. From QWP2OBPS.

LOG_THRESHOLD INTEGER Log output buffer threshold value (1 to 256; the default is20). This is the number of log output buffers to be filledbefore starting an asynchronous log output buffer write.From QWP2WRTH.

MAX_CONN_REM_THRDS INTEGER Maximum number of connected remote threads. FromQWP1CDB.

MAX_DRDA_QR_BL_REQ INTEGER The maximum number of extra DRDA query blocks forDB2 requester. New with DB2 V6. From QWP1EXBR.

MAX_DRDA_QR_BL_SVR INTEGER The maximum number of extra DRDA query blocks forDB2 server. New with DB2 V6. From QWP1EXBS.

MAX_STG_FAST_LOG INTEGER The maximum DSN1DBM1 storage for fast log apply. Newwith DB2 V6. From QWP1FLBZ.

MB_LOB_SYSTEM INTEGER The megabytes for LOB values, per system. New with DB2V6. From QWP1LVS.

MONITOR_BFR_SIZE INTEGER Monitor trace buffer size, in kilobytes. This can range from8K to 1024K, in 4K increments. From QWP1MONS.

MON_TRACE_CLASS CHAR(8) Start trace option for monitor trace classes. FromQWP1MON.

NPAGES_THRESH INTEGER NPages threshold for optimizer. From Q7P4NPAG, DB2 V7or later.

ONLIN_ZPAR_CORRID CHAR(12) Corr ID monitor for online ZParm. From Q7P4OZCI, DB2V7 or later.

DB2 data tables



ONLIN_ZPAR_TIMES CHAR(8) Online ZParm time changed. From Q7P4OZTM, DB2 V7 orlater.

ONLIN_ZPAR_TYPE CHAR(1) Online ZParm type. From Q7P4OZTP, DB2 V7 or later.

ONLIN_ZPAR_UID CHAR(8) User ID monitor for online ZParm. From Q7P4OZUS, DB2V7 or later.

PARTIT_KEY_UPD CHAR(1) Allow update of partitioning key: Y, N, or S. FromQ7P4PKYU, DB2 V7 or later.

POOL_THR_TIMEOUT INTEGER Pool thread timeout value. From QWP9INAC, DB2 V7 orlater.

REMOTE_THREADS_MAX INTEGER Maximum number of concurrent remote threads(concurrent database access threads, which are allocated ata location on behalf of a remote SQL request). FromQWP1RMT.

RES_TRACE_SIZE INTEGER Size of the resident trace table, in multiples of 4 kilobytes.From QWP1TRSZ.

SERVICE_UNIT_LIMIT INTEGER Maximum number of MVS service units that can be usedfor a thread. From QWP1RLFN.

SMS_DCLASS_FSTSP CHAR(8) SMS DataClass - File Tablespace. From Q7P4DCFS, DB2 V7or later.

SMS_DCLASS_IXTSP CHAR(8) SMS DataClass - Index Tablespace. From Q7P4DCIX, DB2V7 or later.

SP_ALLOWED_ABNDS INTEGER Number of allowable abnormal ends for a storedprocedure. From QWP1SPAB.

SP_TIMEOUT_VALUE INTEGER Timeout value of a stored procedure. From QWP1SPTO.

STAR_JOIN_RATIO INTEGER Star join ratio. From Q7P4SJRT, DB2 V7 or later.

STAT_HIST CHAR(1) Statistics history default. From Q7P4STHT, DB2 V7 or later.

STATISTIC_INTERVAL INTEGER Time interval between statistics collection, in minutes (1 to1440). The default is 30 minutes. From QWP1STIM.

STAT_ROLLUP CHAR(1) Statistics rollup default. From Q7P4STRL, DB2 V7 or later.

STAT_TRACE_CLASS CHAR(8) SMF start trace option for statistics trace classes. FromQWP1SMFS.

SYNCHVAL CHAR(2) Synchval specification in minutes. Acceptable values areNO (if no synchronization is specified) or any value in therange 0 - 59. DB2 V7 or later.

T1_INACT_THRDS_MAX INTEGER The maximum number of type 1 inactive threads. Newwith DB2 V6. From QWP9MAX1.

TCPIP_KEEPALIV_OV INTEGER TCP/IP KEEPALIVE override. From QWP9TCKA, DB2 V7or later.

TSO_CONNECTS_MAX INTEGER Maximum number of concurrent connections from TSOforeground sessions. From QWP1IDF.

URLOG_WRIT_THRES REAL Written threshold for UR log record. From QWP1LWCK,DB2 V7 or later.

DB2 data tables


DB2_SYSTEM_DIST_TThis table provides detailed DB2 distributed address space statistics. It containsdistributed data facility statistics data based on SMF type 100, subtype 0 records(DB2 system services, IFCID 0001).





TIMESTAMP k TIMESTAMP Date and time when the system statistics record wascollected by SMF. From SM100DTE and SM100TME.





LOCAL_LOCATION k CHAR(16) Location name of the local location associated with thestatistics records. From QWHSLOCN.

REMOTE_LOCATION k CHAR(16) Location name of the remote location associated with thestatistics record, or for DRDA connections, this columncontains the string DRDA REMOTE LOCS. FromQLSTLOCN.

ABORTS_RECEIVED INTEGER Number of abort requests received from the requesterlocation. From QLSTABRR.

ABORTS_SENT INTEGER Number of abort requests sent to the server location.From QLSTABRS.

BACKOUT_COORD_RCV INTEGER Number of backout requests received from thecoordinator. This column is valid only for two-phasecommit operations. From QLSTBKRC.

BACKOUT_COORD_SENT INTEGER Number of backout responses sent to the coordinator.This column is valid only for two-phase commitoperations. From QLSTVNSE.

BACKOUT_PART_RCV INTEGER Number of backout responses received from theparticipant. This column is valid only for two-phasecommit operations. From QLSTVNRC.

BACKOUT_PART_SENT INTEGER Number of backout requests sent to the participant. Thiscolumn is valid only for two-phase commit operations.From QLSTBKSE.

BLOCK_FETCH_RCV INTEGER Number of blocks received using block fetch. The value inthis column is maintained at the requester location. FromQLSTBRBF.

BLOCK_FETCH_ROWS INTEGER Number of rows transmitted or received in the messagebuffers using block fetch. From QLSTBROW.

DB2 data tables



BLOCK_FETCH_SENDS INTEGER Number of blocks transmitted using block fetch. Thevalue in this column is maintained at the server location.From QLSTBTBF.

BOUNDS_FOR_REMOTE INTEGER Number of SQL statements that were bound for remoteaccess. This applies only to private DB2 connections.From QLSTRBND.

BYTES_RECEIVED INTEGER Number of bytes of data received from the serverlocation. From QLSTBYTR.

BYTES_SENT INTEGER Number of bytes of data sent to the requester location.From QLSTBYTS.

COMMIT_COUNT INTEGER Number of commit operations performed with the remotelocation as the coordinator. This column is valid only fortwo-phase commit operations. From QLSTCPTR.

COMMITS_RECEIVED INTEGER Number of commit requests received from the serverlocation. From QLSTCOMR.

COMMITS_SENT INTEGER Number of commit requests sent to the server location.From QLSTCOMS.

COMMIT2_COORD_RCV INTEGER Number of commit requests received from thecoordinator. This column is valid only for two-phasecommit operations. From QLSTCRRC.

COMMIT2_COORD_SENT INTEGER Number of request-commit responses sent to thecoordinator. This column is valid only for two-phasecommit operations. From QLSTVYSE.

COMMIT2_PART_RCV INTEGER Number of request-commit responses received from theparticipant. This column is valid only for two-phasecommit operations. From QLSTVYRC.

COMMIT2_PART_SENT INTEGER Number of commit requests sent to the participant. Thiscolumn is valid only for two-phase commit operations.From QLSTCRSE.

CONT_TO_LIMIT_BLK INTEGER Number of times a switch was made from continuousblock mode to limited block mode (private DB2connections only). From QLSTCBLB.

CONVERS_INIT_FROM INTEGER Number of conversations that were initiated from therequester (remote) location to the server location. FromQLSTCNVR.

CONVERS_INIT_TO INTEGER Number of conversations that were initiated from therequester (local) location. From QLSTCNVS.

CONVERS_QUEUED INTEGER Number of conversation requests queued by thedistributed data facility that are waiting for allocation.From QLSTCNVQ.

DBAT_CREATE_RCV INTEGER Number of transactions migrated from the location. Thisis the number of create database access thread requestsreceived by the server location from the requester alliedagent. From QLSTTRNR.

DBAT_CREATE_SENT INTEGER Number of transactions migrated to the location. This isthe number of create database access thread requests sentto the server location by the requester allied agent. FromQLSTTRNS.

FORGETS_COORD_SENT INTEGER Number of forget responses sent to the coordinator. Thiscolumn is valid only for two-phase commit operations.From QLSTRRSE.

DB2 data tables



FORGETS_PART_RCV INTEGER Number of forget responses received from the participant.This column is valid only for two-phase commitoperations. From QLSTRRRC.


INDOUBT_COUNT INTEGER Number of threads that became indoubt with the remotelocation as the coordinator. This column is valid only fortwo-phase commit operations. From QLSTINDT.

LAST_AGENTS_RCV INTEGER Number of last agent requests received from thecoordinator This column is valid only for two-phasecommit operations. From QLSTLARC.

LAST_AGENTS_SENT INTEGER Number of last agent requests sent to the coordinator.This column is valid only for two-phase commitoperations. From QLSTLASE.

MESSAGES_RECEIVED INTEGER Number of messages received from the location. FromQLSTMSGR.

MESSAGES_SENT INTEGER Number of messages sent to the location. FromQLSTMSGS.

PREPARES_RECEIVED INTEGER Number of prepare requests received from thecoordinator. This column is valid only for two-phasecommit operations. From QLSTPRRC.

PREPARES_SENT INTEGER Number of prepare requests sent to the participant. Thiscolumn is valid only for two-phase commit operations.From QLSTPRSE.

ROLLBACK_COUNT INTEGER Number of rollback operations performed with theremote location as the coordinator. This column is validonly for two-phase commit operations. From QLSTRBTR.

ROWS_RECEIVED INTEGER Number of rows of data retrieved from the serverlocation. This does not include the SQLDA or SQLCA ifthey were transmitted. From QLSTROWR.

ROWS_SENT INTEGER Number of rows of data sent to the requester location.This includes the SQLDA. From QLSTROWS.

SQL_STMT_RECEIVED INTEGER Number of SQL statements received from the requesterlocation. From QLSTSQLR.

SQL_STMT_SENT INTEGER Number of SQL statements sent to the server location.From QLSTSQLS.


DB2 data tables


DB2_SYSTEM_TThis table provides detailed DB2 system address space statistics. It contains systemstatistics data based on SMF type 100, subtype 0 records (DB2 system services,IFCID 0001).



DATE k DATE Date when the system address space statistics record wascollected by SMF. From SM100DTE.

TIME k TIME Time when the system address space statistics record wascollected by SMF. From SM100TME.






ABORT_COUNT INTEGER Number of successful abort requests. This is the number oftimes a unit of recovery backed out for reasons such asapplication program abnormal end, application canceledby operator, and thread abnormal end because of resourceshortage. From Q3STABRT.

ACT_INACT_DBATS INTEGER Maximum number of active and inactive database accessthreads that existed. From QDSTHWDT.

ACTIVE_DBATS INTEGER Current number of active database access threads. FromQDSTCNAT.

ACTIVE_DBATS_MAX INTEGER Maximum number of active database access threads thatexisted. From QDSTHWAT.

ALTER_BUFFERPOOL INTEGER Number of -ALTER BUFFERPOOL commands issued. Thisincludes normal or abnormal completion of the command.This column is valid from DB2 V3 R1. From Q9STCTRN.

ALTER_GROUPBPOOL INTEGER Number of -ALTER GROUPBUFFERPOOL commandsissued. From Q9STCTRS.

ALTER_UTILITY INTEGER Number of -ALTER UTILITY commands issued. FromQ9STCTRY.

ARCH_READ_ALLOC INTEGER Number of archive log read allocations. From QJSTALR.

ARCH_WRITE_ALLOC INTEGER Number of archive log write allocations. From QJSTALW.

ARCHIVE_LOG INTEGER Number of -ARCHIVE LOG commands issued. Thisincludes normal or abnormal completion of the command.This column is valid from DB2 V2 R3. From Q9STCTRM.

BSDS_ACCESS INTEGER Number of bootstrap data set access requests processed.From QJSTBSDS.

DB2 data tables



CANCEL_DDF_THREAD INTEGER Number of -CANCEL DDF THREAD commands issued.This includes normal or abnormal completion of thecommand. From Q9STCTRK.

COLD_START_COUNT INTEGER Number of cold-start connections with all remote locations.This column is valid only for two-phase commitoperations. From QDSTCSTR.

COMMAND_COUNT FLOAT Sum of all DB2 commands issued. This includes normal orabnormal completion of the commands. This is the sum ofall Q9STCTxx.

COMMITS_PHASE1 INTEGER Number of phase 1 prepare to commit requests. This is thenumber of successful requests for commit phase 1 of atwo-phase commit. From Q3STPREP.

COMMITS_PHASE2 INTEGER Number of successful phase 2 end commit requests. FromQ3STCOMM.

COMMITS_READ_ONLY INTEGER Number of read-only commit requests. From Q3STRDON.

COMMITS_SINGLE INTEGER Number of successful single-phase (synchronized) commitrequests. From Q3STSYNC.

CONTROL_INT_COUNT INTEGER Number of active log output control intervals created.From QJSTBFFL.

CONTROL_INT_OFFL INTEGER Number of control intervals off-loaded. This column isvalid from DB2 V3 R1. From QJSTCIOF.

CONVERS_DEALLOC INTEGER Number of conversations that were de-allocated becausethe ZPARM limit was reached for maximum concurrentremote threads. This column is valid only for two-phasecommit operations. From QDSTQCRT.

CREATE_THREAD INTEGER Number of successful create thread requests. This is thenumber of threads created, excluding database accessthreads. From Q3STCTHD.

CREATE_THREAD_WAIT INTEGER Number of create thread requests queued. This does notinclude database access threads. From Q3STCTHV.

DBAT_QUEUED_COUNT INTEGER Number of times that a database access thread was queuedbecause the limit for the maximum number of databaseaccess threads was reached. From QDSTQDBT.

DBATS_INACTIVE INTEGER Current number of inactive database access threads. Thiscolumn is valid only for two-phase commit operations.From QDSTQCIT.

DBATS_INACTIVE_T2 INTEGER Current number of type 2 inactive threads. FromQDSTCIN2. DB2 V6 or later.

DBATS_INACT_MAX_T2 INTEGER Maximum number of type 2 inactive threads reached.From QDSTMIN2. DB2 V6 or later.

DIS_GROUP INTEGER Number of -DISPLAY GROUP commands issued. FromQ9STCTRX.

DISPLAY_ARCHIVE INTEGER Number of -DISPLAY ARCHIVE commands issued. Thisincludes normal or abnormal completion of the command.This column is valid from DB2 V3 R1. From Q9STCTRQ.

DISPLAY_BUFFERPOOL INTEGER Number of -DISPLAY BUFFERPOOL commands issued.This includes normal or abnormal completion of thecommand. This column is valid from DB2 V3 R1. FromQ9STCTRO.

DB2 data tables



DISPLAY_DATABASE INTEGER Number of -DISPLAY DATABASE commands issued. Thisincludes normal or abnormal completion of the command.From Q9STCTR0.

DISPLAY_FUNCTION INTEGER Number of -DISPLAY FUNCTION commands issued. FromQ9STCTRZ. DB2 V6 or later.

DISPLAY_GROUPBP INTEGER Number of -DISPLAY GROUPBUFFERPOOL commandsissued. From Q9STCTRT.

DISPLAY_LOCATION INTEGER Number of -DISPLAY LOCATION commands issued. Thisincludes normal or abnormal completion of the command.From Q9STCTRL.

DISPLAY_LOG INTEGER Number of -DISPLAY LOG commands issued. FromQ9STCTX3. DB2 V6 or later.

DISPLAY_PROCEDURE INTEGER Number of -DISPLAY PROCEDURE commands issued.From Q9STCTRU.

DISPLAY_RLIMIT INTEGER Number of -DISPLAY RLIMIT commands issued. Thisincludes normal or abnormal completion of the command.From Q9STCTRG.

DISPLAY_THREAD INTEGER Number of -DISPLAY THREAD commands issued. Thisincludes normal or abnormal completion of the command.From Q9STCTR1.

DISPLAY_TRACE INTEGER Number of -DISPLAY TRACE commands issued. Thisincludes normal or abnormal completion of the command.From Q9STCTRC.

DISPLAY_UTILITY INTEGER Number of -DISPLAY UTILITY commands issued. Thisincludes normal or abnormal completion of the command.From Q9STCTR2.

DSN3EXIT INTEGER Number of successful DSN3 exit requests. From Q3STEXIT.


IDENTIFY INTEGER Number of successful identify requests. This is the numberof successful connections to DB2 by TSO, IMS, CICS, CAF,or by a DB2 utility. From Q3STIDEN.

INDOUBT_UOR INTEGER Number of indoubt units of recovery. A unit of recovery isindoubt when a failure occurs after a successful prepare tocommit but before a successful commit. From Q3STINDT.

MODIFY_TRACE INTEGER Number of -MODIFY TRACE commands issued. Thisincludes normal or abnormal completion of the command.From Q9STCTRH.

MOUNTS INTEGER Number of successful look-ahead tape mounts. Thiscolumn is valid from DB2 V3 R1. From QJSTLAMS.

MOUNTS_ATTEMPTED INTEGER Number of look-ahead tape mounts attempted. Thiscolumn is valid from DB2 V3 R1. From QJSTLAMA.

PHYSICAL_SUSPENDS INTEGER Number of physical suspends. From QVASSUSP.

QUEUED_REQUESTS INTEGER Number of queued receive requests for type 2 inactivethreads plus requests for new connection that werereceived after max remote active was reached. FromQDSTQIN2. DB2 V6 or later.

DB2 data tables



QUEUED_INACT_T2 INTEGER Current number of type 2 inactive threads queued, waitingto process. It includes both receive requests completed fora type 2 inactive thread and requests for new connectionsreceived after maximum remote active reaching. FromQDSTNQR2. DB2 V6 or later.

QUEUED_INACTT2_MAX INTEGER Maximum number of type 2 inactive threads that werequeued waiting to process. It includes both receiverequests completed for a type 2 inactive thread andrequests for new connections received after maximumremote active reaching. From QDSTMQR2. DB2 V6 or later.

READS_ACTIVE_LOG INTEGER Number of log reads satisfied from active log data sets.From QJSTRACT.

READS_ARCHIVE_LOG INTEGER Number of log reads satisfied from archive log data sets.From QJSTRARH.

READS_DELAYED_LIM INTEGER Number of log reads delayed because the archiveallocation limit was reached. This column is valid only forDB2 V2. From QJSTWTL.

READS_DELAYED_TAPE INTEGER Number of read accesses delayed because of tape volumecontention. This column is valid from DB2 V3 R1. FromQJSTTVC.

READS_DELAYED_UNAV INTEGER Number of read accesses delayed because of unavailableresources, such as not having enough tape units allocated.This column is valid from DB2 V3 R1. From QJSTWUR.

READS_OUTPUT_BFR INTEGER Number of log reads satisfied from output buffers. FromQJSTRBUF.

RECOVER_BSDS INTEGER Number of -RECOVER BSDS commands issued. Thisincludes normal or abnormal completion of the command.From Q9STCTR3.

RECOVER_INDOUBT INTEGER Number of -RECOVER INDOUBT commands issued. Thisincludes normal or abnormal completion of the command.From Q9STCTR4.

RESET_INDOUBT INTEGER Number of -RESET INDOUBT commands issued. Thisincludes normal or abnormal completion of the command.This column is valid from DB2 V3 R1. From Q9STCTRR.

RESOLVE_INDOUBT INTEGER Number of successful resolve indoubt requests. This is thenumber of times requests to handle an indoubt work unitwere successfully processed. From Q3STRIUR.

RESYNC_ATTEMPTS INTEGER Number of re-synchronization connections attempted withall remote locations. This column is valid only fortwo-phase commit operations. From QDSTRSAT.

RESYNC_SUCCEEDS INTEGER Number of re-synchronization connections that succeededwith all remote locations. This column is valid only fortwo-phase commit operations. From QDSTRSSU.

SET_ARCHIVE INTEGER Number of -SET ARCHIVE commands issued. Thisincludes normal or abnormal completion of the command.This column is valid from DB2 V3 R1. From Q9STCTRP.

SET_LOG INTEGER Number of -SET LOG commands issued. From Q9STCTX2.DB2 V6 or later.

SET_SYSPARM INTEGER Number of -SET SYSPARM commands issued. FromQ9STCTX4. DB2 V7 or later.

DB2 data tables



SIGNON INTEGER Number of successful sign-on requests. This is the numberof times the user signed on to identify a new user for IMSand CICS. From Q3STSIGN.

SLOTS_NOT_IN_USE INTEGER Current number of active DBAT slots that are not in use.The slot will be assigned when either a queued receiverequest completes or a request for a new connection isreceived. From QDSTNADS. DB2 V6 or later.

SLOTS_NOTINUSE_MAX INTEGER Maximum number of DBAT slots that were not in usebecause no processing was required either to complete aqueued receive request or to establish a new connection.From QDSTMADS. DB2 V6 or later.

SRB_TIME_DBM1 FLOAT CPU time used for DB2 database address space SRB, inseconds. Calculated as QWSASRBT/4 096 000 000 whenQWSAPROC = DBM1.

SRB_TIME_DIST FLOAT CPU time used for DDF DB2 distributed address spaceSRB, in seconds. Calculated as QWSASRBT/4 096 000 000when QWSAPROC = DIST.

SRB_TIME_IRLM FLOAT CPU time used for IRLM address space SRB, in seconds.Calculated as QWSASRBT/4 096 000 000 whenQWSAPROC = IRLM.

SRB_TIME_MSTR FLOAT CPU time used for DB2 system address space SRB, inseconds. Calculated as QWSASRBT/4 096 000 000 whenQWSAPROC = MSTR.

SSI_CALLS INTEGER Number of SSI calls processed. From Q3STSSSI.

START_DATABASE INTEGER Number of -START DATABASE commands issued. Thisincludes normal or abnormal completion of the command.From Q9STCTR5.

START_DDF INTEGER Number of -START DDF commands issued. This includesnormal or abnormal completion of the command. FromQ9STCTRI.

START_FUNCTION INTEGER Number of -START FUNCTION commands issued. FromQ9STCTX0. DB2 V6 or later.

START_PROCEDURE INTEGER Number of -START PROCEDURE commands issued. FromQ9STCTRV.

START_RLIMIT INTEGER Number of -START RLIMIT commands issued. Thisincludes normal or abnormal completion of the command.From Q9STCTRE.

START_SUBSYS INTEGER Number of -START SUBSYSTEM commands issued. Thisincludes normal or abnormal completion of the command.From Q9STCTR7.

START_TRACE INTEGER Number of -START TRACE commands issued. Thisincludes normal or abnormal completion of the command.From Q9STCTR6.

STOP_DATABASE INTEGER Number of -STOP DATABASE commands issued. Thisincludes normal or abnormal completion of the command.From Q9STCTR8.

STOP_DDF INTEGER Number of -STOP DDF commands issued. This includesnormal or abnormal completion of the command. FromQ9STCTRJ.

STOP_FUNCTION INTEGER Number of -STOP FUNCTION commands issued. FromQ9STCTX1. DB2 V6 or later.

DB2 data tables



STOP_PROCEDURE INTEGER Number of -STOP PROCEDURE commands issued. FromQ9STCTRW.

STOP_RLIMIT INTEGER Number of -STOP RLIMIT commands issued. This includesnormal or abnormal completion of the command. FromQ9STCTRF.

STOP_SUBSYS INTEGER Number of -STOP SUBSYSTEM commands issued. Thisincludes normal or abnormal completion of the command.From Q9STCTRA.

STOP_TRACE INTEGER Number of -STOP TRACE commands issued. This includesnormal or abnormal completion of the command. FromQ9STCTR9.

SUBSYSTEM_EOM INTEGER Subsystem allied memory end-of-memory count. This isthe number of times non-DB2 address space was deletedby MVS while connected to DB2. From Q3STMEOM.

SUBSYSTEM_EOT INTEGER Subsystem allied memory end-of-tasks. This is the numberof times non-DB2 tasks abnormally ended while connectedto DB2. From Q3STMEOT.

TCB_TIME_DBM1 FLOAT CPU time used for DB2 database address space TCB, inseconds. Calculated as QWSAEJST/4 096 000 000 whenQWSAPROC = DBM1.

TCB_TIME_DIST FLOAT CPU time used for DDF DB2 distributed address spaceTCB, in seconds. Calculated as QWSAEJST/4 096 000 000when QWSAPROC = DIST.

TCB_TIME_IRLM FLOAT CPU time used for IRLM address space TCB, in seconds.Calculated as QWSAEJST/4 096 000 000 when QWSAPROC= IRLM.

TCB_TIME_MSTR FLOAT CPU time used for DB2 system address space TCB, inseconds. Calculated as QWSAEJST/4 096 000 000 whenQWSAPROC = MSTR.

TERM_COUNT INTEGER Number of connections that were terminated rather thanmade type 1 inactive because the maximum of type 1inactive was reached. From Q9STNITC. DB2 V6 or later.

TERM_UTILITY INTEGER Number of -TERM UTILITY commands issued. Thisincludes normal or abnormal completion of the command.From Q9STCTRB.

TERMINATE_THREAD INTEGER Number of successful terminate thread requests. This is thenumber of times threads were terminated. FromQ3STTERM.

THREADS_INACT_MAX INTEGER Maximum number of inactive database access threadsreached. This column is valid only for two-phase commitoperations. From QDSTQMIT.

UNRECOGNIZED_CMD INTEGER Number of unrecognized commands issued. This includesnormal or abnormal completion of the command. FromQ9STEROR.

WAITS_NO_BUFFER INTEGER Number of waits because of unavailable output log buffer.From QJSTWTB.

WARM_START_COUNT INTEGER Number of warm-start connections with all remotelocations. This column is valid only for two-phase commitoperations. From QDSTWSTR.


WRITES_ACTIVE_LOG INTEGER Number of calls to the log write routine. From QJSTBFWR.

DB2 data tables



WRITES_BUF_PGIN INTEGER Number of times a log-write buffer had to be paged-inbefore it could be used. From QJSTBPAG, DB2 V7 or later.

WRITES_FORCE INTEGER Number of log write (with force) requests processed. Forcemeans write the log record to the log buffer and force thebuffer to be written to the log data set on DASD. FromQJSTWRF.

WRITES_NOWAIT INTEGER Number of log write (with no wait) requests processed. Nowait means write the log record to the log buffer and donot wait for it to get written to the log data set. FromQJSTWRNW.

WRITES_SERCI_REWR INTEGER Number of serial log-write requests for CI rewrite. FromQJSTSERW, DB2 V7 or later.

WRITES_SUSPEND INTEGER Number of times a log request resulted in a SUSPEND fora log-write to occur. From QJSTLSUS, DB2 V7 or later.

WRITES_THRS_RCHD INTEGER Number of times a log-write request was scheduledbecause the log-write threshold was reached. FromQJSTTHRW, DB2 V7 or later.

WRITES_TOT_CIS_WR INTEGER Total number of log CIs written. From QJSTCIWR, DB2 V7or later.

WRITES_TOT_IOREQS INTEGER Total number of log-write I/O requests. From QJSTLOGW,DB2 V7 or later.

DB2 data tables


DB2_TRAN_DIST_D, _WThese tables provide daily and weekly statistics on DDF distributed address spacegrouped by transaction. They contain accounting and response-time data based onSMF type 101 records (DB2 accounting, IFCID 0003).

The default retention periods for these tables are:DB2_TRAN_DIST_D 30 daysDB2_TRAN_DIST_W 375 days


DATE k DATE Date when the accounting records were collected by SMF. For the_W table, this is the date of the first day of the week. FromSM101DTE.

PERIOD_NAME k CHAR(8) Name of the period. This is derived by using fields SM100DTEand SM100TME as parameters in the PERIOD function.




REMOTE_LOCATION k CHAR(16) Location name of the remote location associated with theaccounting records. For DRDA connections, this column containsthe string DRDA REMOTE LOCS. From QLACLOCN.

CORRELATION_ID k CHAR(12) Correlation ID value. From QWHCCV.



DB2 data tables


DB2_TRANSACTION_D, _WThese tables provide daily and weekly statistics on DB2 transactions grouped bytransaction. They contain accounting and response-time data based on SMF type101 records (DB2 accounting, IFCID 0003).

The default retention periods for these tables are:DB2_TRANSACTION_D 30 daysDB2_TRANSACTION_W 375 days


DATE k DATE Date when the accounting records were collected by SMF. For the _Wtable, this is the date of the first day of the week. From SM101DTE.

PERIOD_NAME k CHAR(8) Name of the period. This is derived by using fields SM101DTE andSM101TME as parameters in the PERIOD function.



CORRELATION_ID k CHAR(12) Correlation ID value. From QWHCCV.



DB2 data tables


DB2_US_TRAN_SHAR_HThis table provides hourly statistics on DB2 transactions grouped by user andtransaction. It contains accounting data related to DATA SHARING based on SMFtype 101 records (DB2 accounting, IFCID 0003).



DATE k DATE Date when the accounting records were collected by SMF.For the _W table, this is the date of the first day of the week.From SM101DTE.





PRIMARY_AUTH_ID k CHAR(8) Primary authorization ID value. From QWHCOPID.

CORRELATION_ID k CHAR(12) Correlation ID value. It applies only to the _H table. FromQWHCCV.

APPLICATION_NAME k CHAR(18) Name of the application. From APPLICATION_NAME in theDB2_APPLICATION lookup table. It applies only to the _Htable.

PROFILE k CHAR(12) Profile. From PROFILE in the DB2_APPLICATION lookuptable. It applies only to the _H table.


CHANGED_PAGES REAL Number of changed pages written to the group buffer pool.This is the sum of QBGASW.

CLEAN_PAGES REAL Number of clean pages written to the group buffer pool. Thisis the sum of QBGAWC.

GET_PAGES INTEGER Number of GetPages for GBP Dep pages. From QBGAGG,DB2 V7 or later.

GROUP_BPOOL_ID INTEGER ID of the group buffer pool. This is the sum of QBGAGN.

PRIM_IXL_ASYNCH INTEGER Asynchronous IXLCACHE invocations for primary GPB.From QBGAHS, DB2 V7 or later.

RREQ_FOR_INVALID1 REAL Number of sychronous SES reads necessary due to buffercross invalidation (XI) in which data was returned. This isthe sum of QBGAXD.

RREQ_FOR_INVALID2 REAL Number of SES reads necessary due to buffer XI in whichdata was not returned from SES and directory entryassignment was not suppressed. This the sum of QBGAXR.

RREQ_FOR_PGNOTFND1 REAL Number of SES reads necessary due to the requested pagenot being found in the buffer pool in which data wasreturned from SES. This is the sum of QBGAMD.

RREQ_FOR_PGNOTFND2 REAL Number of SES reads necessary due to the requested pagenot being found in the buffer pool in which data was notreturned and directory entry assignment was not suppressed.This is the sum of QBGAMR.

DB2 data tables



RREQ_FOR_PGNOTFND3 REAL Number of pages read from GBP due to prefetch under thecontrol of the agent. This is the sum of QBGAMN.

SEC_CHANGED_PAGES INTEGER The number of writes of changed pages to the secondaryGBP for duplexing. From QBGA2W. DB2 V6 or later.

SEC_CHECKS_SUSP INTEGER The number of completion checks for writes to the secondaryGBP that were suspended because the write had not yetcompleted. From QBGA2S. DB2 V6 or later.

SEC_IXL_ASYNCH INTEGER Asynchronous IXLCACHE invocations for secondary GPB.From QBGA2H, DB2 V7 or later.

SH_CHANGE_REQS REAL Number of change requests for physical locks. This is thesum of QTGACPLK.

SH_CHANGE_XEST REAL Number of change requests propagated to MVS XES. This isthe sum of QTGACSLM.

SH_INCOMP_LOCK REAL Number of global lock or change requests denied due to anincompatible retained lock. This is from QTGADRTA.

SH_LOCK_REQS REAL Number of lock requests for physical locks. This is the sumof QTGALPLK.

SH_LOCK_XEST REAL Number of lock requests propagated to MVS XES. This is thesum of QTGALSLM.

SH_NOTIFY_SENT REAL Number of notify messages sent. This is from QTGANTFY.

SH_SUSP_FALSE REAL Number of suspensions due to false contention. This happenswhen different resource names hash to the same entry in thecoupling facility lock table. This is from QTGAFLSE.

SH_SUSP_IRLM REAL Number of suspensions due to IRLM global resourcecontention (IRLM lock states were in conflict). This is thesum of QTGAIGLO.

SH_SUSP_XES REAL Number of suspensions due to MVS XES global resourcecontention (MVS XES lock states were in conflict, whereasIRLM lock states were not). This is from QTGASGLO.

SH_UNLOCK_REQS REAL Number of unlock requests for physical locks. This is thesum of QTGAUPLK.

SH_UNLOCK_XEST REAL Number of unlock requests propagated to MVS XES. This isthe sum of QTGAUSLM.

UNREG_PAGES_REQS REAL Number of unregistered page requests. This is the sum ofQBGADC.

DB2 data tables


DB2_USER_AP_DIST_H, _WThese tables provide hourly and weekly statistics on DDF distributed addressspace grouped by user and application. They contain accounting and response-timedata based on SMF type 101 records (DB2 accounting, IFCID 0003).


The default retention periods for these tables are:DB2_USER_AP_DIST_H 30 daysDB2_USER_AP_DIST_W 375 days



TIME k TIME Time when the accounting records were collected by SMF. Itapplies only to the _H table. From SM101TME.




LOCAL_LOCATION k CHAR(16) Location name of the local location associated with the accountingrecords. From QWHSLOCN.

REMOTE_LOCATION k CHAR(16) Location name of the remote location associated with theaccounting records. For DRDA connections, this column containsthe string DRDA REMOTE LOCS. From QLACLOCN.

PRIMARY_AUTH_ID k CHAR(8) Initial primary authorization ID. This is the logon ID, user ID, orsign-on ID. From QWHCOPID.



DB2 data tables


DB2_USER_APPL_H, _WThese tables provide hourly and weekly statistics on DB2 transactions grouped byuser and application. They contain accounting and response-time data based onSMF type 101 records (DB2 accounting, IFCID 0003).


The default retention period for these tables are:DB2_USER_APPL_H 30 daysDB2_USER_APPL_W 375 days



TIME k TIME Time (rounded down to the nearest hour) when the accountingrecords were collected by SMF. It applies only to the _H table.From SM101TME.







DB2 data tables


DB2_USER_DIST_H, _D, _WThese tables provide hourly, daily, and weekly statistics on DDF distributedaddress space grouped by user and application. They contain accounting andresponse-time data based on SMF type 101 records (DB2 accounting, IFCID 0003).


Note: The data columns of these tables are also used by the DB2_APPL_DIST_x,DB2_TRAN_DIST_x, and DB2_USER_AP_DIST_x tables.

The default retention periods for these tables are:DB2_USER_DIST_H 7 daysDB2_USER_DIST_D 30 daysDB2_USER_DIST_W 375 days


DATE k DATE Date when the accounting records were collected by SMF.For the _W table, this is the date of the first day of theweek. From SM101DTE.

TIME k TIME Time when the accounting records were collected by SMF.It applies only to the _H table. From SM101TME.





REMOTE_LOCATION k CHAR(16) Location name of the remote location associated with theaccounting records. For DRDA connections, this columncontains the string DRDA REMOTE LOCS. FromQLACLOCN.

PRIMARY_AUTH_ID k CHAR(8) Initial primary authorization ID. This is the logon ID, userID, or sign-on ID. From QWHCOPID.


APPLICATION_NAME k CHAR(18) Name of the application. From APPLICATION_NAME inthe DB2_APPLICATION lookup table. It applies only tothe _H table.



ABORTS_RECEIVED INTEGER Number of abort requests received from the requesterlocation. From QLACABRR.

ABORTS_SENT INTEGER Number of abort requests sent to the server location. FromQLACABRS.

BACKOUT_COORD_RCV INTEGER Number of backout requests received from the coordinator.This column is valid only for two-phase commitoperations. This is the sum of QLSTBKRC.

DB2 data tables



BACKOUT_COORD_SENT INTEGER Number of backout responses sent to the coordinator. Thiscolumn is valid only for two-phase commit operations.This is the sum of QLSTVNSE.

BACKOUT_PART_RCV INTEGER Number of backout responses received from theparticipant. This column is valid only for two-phasecommit operations. This is the sum of QLSTVNRC.

BACKOUT_PART_SENT INTEGER Number of backout requests sent to the participant. Thiscolumn is valid only for two-phase commit operations.This is the sum of QLSTBKSE.

BLOCK_FETCH_RCV INTEGER Number of blocks received using block fetch. The value inthis column is maintained at the requester location. Thiscolumn is valid from DB2 V2 R3. From QLACBRBF.

BLOCK_FETCH_ROWS INTEGER Number of rows transmitted or received in the messagebuffers using block fetch. This column is valid fromDB2 V2 R3. From QLACBROW.

BLOCK_FETCH_SENDS INTEGER Number of blocks transmitted using block fetch. The valuein this column is maintained at the server location. Thiscolumn is valid from DB2 V2 R3. From QLACBTBF.

BOUNDS_FOR_REMOTE INTEGER Number of SQL statements that were incrementally boundfor remote access. This applies only to private DB2connections. This column is valid from DB2 V2 R3. FromQLACRBND.

BYTES_RECEIVED FLOAT Number of bytes of data received from the server location.From QLACBYTR.

BYTES_SENT FLOAT Number of bytes of data sent to the requester location.From QLACBYTS.

COMMIT_COUNT INTEGER Number of commit operations performed with the remotelocation as the coordinator. This column is valid only fortwo-phase commit operations. This is the sum ofQLSTCPTR.

COMMITS_RECEIVED INTEGER Number of commit requests received from the serverlocation. From QLACCOMR.

COMMITS_SENT INTEGER Number of commit requests sent to the server location.From QLACCOMS.

COMMIT2_COORD_RCV INTEGER Number of commit requests received from the coordinator.This column is valid only for two-phase commitoperations. This is the sum of QLSTCRRC.

COMMIT2_COORD_SENT INTEGER Number of request-commit responses sent to thecoordinator. This column is valid only for two-phasecommit operations. This is the sum of QLSTVYSE.

COMMIT2_PART_RCV INTEGER Number of request-commit responses received from theparticipant. This column is valid only for two-phasecommit operations. This is the sum of QLSTVYRC.

COMMIT2_PART_SENT INTEGER Number of commit requests sent to the participant. Thiscolumn is valid only for two-phase commit operations.This is the sum of QLSTCRSE.

CONT_TO_LIMIT_BLK INTEGER Number of times a switch was made from continuousblock mode to limited block mode (private DB2connections only). This column is valid from DB2 V2 R3.From QLACCBLB.

DB2 data tables



CONVERS_ALLOCATED INTEGER Number of successful conversation allocations. Thiscolumn is valid from DB2 V2 R3. This is the sum ofQLACCNVA.

CONVERS_INIT_FROM INTEGER Number of conversations that were initiated from therequester (remote) location to the server location. FromQLACCNVR.

CONVERS_INIT_TO INTEGER Number of conversations that were initiated from therequester (local) location. From QLACCNVS.

CONVERS_OPEN_MAX INTEGER Maximum number of conversations open at any time. Thisis the largest (QLACCNVA − QLACCNVT) valuecalculated when QLACCNVA is incremented. This columnis valid from DB2 V2 R3. This is the maximum ofQLACCIEL.

CONVERS_QUEUED INTEGER Number of conversation requests queued by thedistributed data facility that are waiting for allocation.From QLACCNVQ.

CONVERS_TERMINATED INTEGER Number of conversations terminated. The value in thiscolumn might not be the same as that inCONVERS_ALLOCATED because not all conversationsmight be terminated when the accounting record iswritten. This column is valid from DB2 V2 R3. This is thesum of QLACCNVT.

CPU_REMOTE_SEC FLOAT Database access agent CPU time at the serving (remote)location, in seconds. This column is not valid for DRDAflows and can be misleading if both private DB2 andDRDA flows are used. Calculated as the sum ofQLACDBAT/4 096 000 000.

DBAT_CREATE_RCV INTEGER Number of transactions migrated from the location. This isthe number of create database access thread requestsreceived by the server location from the requester alliedagent. From QLACTRNR.

DBAT_CREATE_SENT INTEGER Number of transactions migrated to the location. This isthe number of create database access thread requests sentto the server location by the requester allied agent. FromQLACTRNS.

ELAPSED_LOCAL_SEC FLOAT Elapsed time at the requester (local) location spent waitingfor completion of work by a database access agent, inseconds. This includes DB2 and VTAM processing times,and network time. Calculated as the sum ofQLACCPUL/4 096 000 000.

ELAPSED_REMOTE_SEC FLOAT Elapsed database access agent time at the serving (remote)location, in seconds. This column is not valid for DRDAflows and can be misleading if both private DB2 andDRDA flows are used. Calculated as the sum ofQLACCPUR/4 096 000 000.

FORGETS_COORD_SENT INTEGER Number of forget responses sent to the coordinator. Thiscolumn is valid only for two-phase commit operations.This is the sum of QLSTRRSE.

FORGETS_PART_RCV INTEGER Number of forget responses received from the participant.This column is valid only for two-phase commitoperations. This is the sum of QLSTRRRC.

DB2 data tables



INDOUBT_COUNT INTEGER Number of threads that became indoubt with the remotelocation as the coordinator. This column is valid only fortwo-phase commit operations. This is the sum ofQLSTINDT.

LAST_AGENTS_RCV INTEGER Number of last-agent requests received from thecoordinator. This column is valid only for two-phasecommit operations. This is the sum of QLSTLARC.

LAST_AGENTS_SENT INTEGER Number of last-agent requests sent to the coordinator. Thiscolumn is valid only for two-phase commit operations.This is the sum of QLSTLASE.

MESSAGES_RECEIVED INTEGER Number of messages received from the location. FromQLACMSGR.

MESSAGES_SENT INTEGER Number of messages sent to the location. FromQLACMSGS.

PREPARES_RECEIVED INTEGER Number of prepare requests received from the coordinator.This column is valid only for two-phase commitoperations. This is the sum of QLSTPRRC.

PREPARES_SENT INTEGER Number of prepare requests sent to the participant. Thiscolumn is valid only for two-phase commit operations.This is the sum of QLSTPRSE.

PRODUCT_ID_REMOTE CHAR(8) Product ID of the remote location. This column is validfrom DB2 V3 R1. This is the last of QLACPRID.

ROLLBACK_COUNT INTEGER Number of rollback operations performed with the remotelocation as the coordinator. This column is valid only fortwo-phase commit operations. This is the sum ofQLSTRBTR.

ROWS_RECEIVED INTEGER Number of rows of data retrieved from the server location.This does not include the SQLDA or SQLCA if they weretransmitted. From QLACROWR.

ROWS_SENT INTEGER Number of rows of data sent to the requester location. Thisincludes the SQLCA. This is the sum of QLACROWS.

SQL_STMT_RECEIVED INTEGER Number of SQL statements received from the requesterlocation. This is the sum of QLACSQLR.

SQL_STMT_SENT INTEGER Number of SQL statements sent to the server location. Thisis the sum of QLACSQLS.

TOT_DBAA_WAIT_SEC REAL Total elapsed time, in seconds, that a database access agentspent waiting because the maximum number of databaseaccess threads has been exceeded. New with DB2 V6.Calculated as the sum of QLACMDWT/4 096 000 000.

DB2 data tables


DB2_USER_TRAN_H, _D, _WThese tables provide hourly, daily, and weekly statistics on DB2 transactionsgrouped by user and transaction. They contain accounting and response-time databased on SMF type 101 records (DB2 accounting, IFCID 0003).


Note: The data columns of these tables are also used by the DB2_USER_APPL_x,DB2_APPLICATION_x, and DB2_TRANSACTION_x tables.

The default retention periods for these tables are:DB2_USER_TRAN_H 7 daysDB2_USER_TRAN_D 30 daysDB2_USER_TRAN_W 375 days


DATE k DATE Date when the accounting records were collected by SMF.For the _W table, this is the date of the first day of theweek. From SM101DTE.







APPLICATION_NAME k CHAR(18) Name of the application. From APPLICATION_NAME inthe DB2_APPLICATION lookup table. It applies only to the_H table.



ABNORMAL INTEGER Number of DB2 threads that completed unsuccessfully. Thisis the count of SMF type 101 accounting records withunsuccessful completion (QWACRINV >= 20).

ABORT_COUNT FLOAT Number of abort requests. This is the sum of QWACABRT.

ACTIV_ROW_TRIGGER INTEGER Number of times a row trigger was activated. New withDB2 V6. From QXROWTRG.

ACTIV_SQL_TRIGGER INTEGER Number of times a statement trigger was activated. Newwith DB2 V6. From QXSTTRG.

ARC_LOGREAD_EVENTS FLOAT Number of wait trace events processed for archive reads.This column is valid from DB2 V3 R1. This is the sum ofQWACANAR.

ARC_LOGREAD_SEC FLOAT Accumulated wait time for archive reads from tape, inseconds. This column is valid from DB2 V3 R1. Calculatedas the sum of QWACAWAR/4 096 000 000.

DB2 data tables



ARC_LOGWAIT_EVENTS FLOAT Number of wait trace events processed because of archivelog mode (QUIESCE) commands that caused a waitsuspension. This column contains a value only if accountingclass 3 is started. This is the sum of QWACALCT.

ARC_LOGWAIT_SEC FLOAT Accumulated wait time because of archive log mode(QUIESCE) commands processed. This column, valid fromDB2 V2 R3, contains a value only if accounting class 3 isstarted. Calculated as the sum ofQWACALOG/4 096 000 000.

ASY_IXL_WAIT_EVT INTEGER Number of wait trace events for asynchronous IXLCACHEor IXLFCOMP invocations, or both. This number representsthe true number of events and is not doubled as are otherwait events. From QXAXIXLE, DB2 V7 or later.

ASY_IXL_WAIT_SEC REAL Accumulated wait time for IXLCACHE and IXLFCOMPasynchronous requests, in seconds. From QXAXIXLT, DB2V7 or later.

AVOID_PREP_FORKD REAL Number of times that a PREPARE was avoided becauseKEEPDYNAMIC(YES) was used along with preparedstatement caching and DB2 still had the application processcopy of the executable version of the prepared statement.This is the sum of QXSTNPRP.

BP32_COND_GETP_UN FLOAT Number of times conditional GETPAGE requests could notbe satisfied for this size of buffer pools. This column is validfrom DB2 V3 R1. This is the sum of QBACNGT when thebuffer pool ID (QBACPID) is between 80 and 89.

BP32_DYN_PREFETCH FLOAT Number of DYNAMIC PREFETCH requests issued. Thiscolumn is valid from DB2 V3 R1. This is the sum ofQBACDPF when the buffer pool ID (QBACPID) is between80 and 89.

BP32_EXPANSIONS FLOAT Number of buffer pool expansions required. This is the sumof QBACBPX when the buffer pool ID (QBACPID) isbetween 80 and 89.

BP32_GETPAGE FLOAT Number of GETPAGE requests issued. This is the sum ofQBACGET when the buffer pool ID (QBACPID) is between80 and 89.

BP32_HPOOL_AREAD FLOAT Number of pages that were moved asynchronously from ahiperpool to a virtual buffer pool because of prefetch underthe agent’s control. This column is valid from DB2 V3 R1.This is the sum of QBACHPG when the buffer pool ID(QBACPID) is between 80 and 89.

BP32_HPOOL_READ_SU FLOAT Number of successful synchronous read requests to move apage from a hiperpool to a virtual buffer pool. This columnis valid from DB2 V3 R1. This is the sum of QBACHREwhen the buffer pool ID (QBACPID) is between 80 and 89.

BP32_HPOOL_READ_UN FLOAT Number of unsuccessful synchronous read requests to movea page from a hiperpool to a virtual buffer pool. Thiscolumn is valid from DB2 V3 R1. This is the sum ofQBACHRF when the buffer pool ID (QBACPID) is between80 and 89.

BP32_HPOOL_WRIT_SU FLOAT Number of successful synchronous write requests to move apage from a virtual buffer pool to a hiperpool. This columnis valid from DB2 V3 R1. This is the sum of QBACHWRwhen the buffer pool ID (QBACPID) is between 80 and 89.

DB2 data tables



BP32_HPOOL_WRIT_UN FLOAT Number of unsuccessful write requests to move a page froma virtual buffer pool to a hiperpool. This column is validfrom DB2 V3 R1. This is the sum of QBACHWF when thebuffer pool ID (QBACPID) is between 80 and 89.

BP32_LIST_PREFETCH FLOAT Number of LIST PREFETCH requests issued. This column isvalid from DB2 V2 R3. This is the sum of QBACLPF whenthe buffer pool ID (QBACPID) is between 80 and 89.

BP32_SEQ_PREFETCH FLOAT Number of SEQUENTIAL PREFETCH requests issued. Thisis the sum of QBACSEQ when the buffer pool ID(QBACPID) is between 80 and 89.

BP32_SYNC_READ_IO FLOAT Number of synchronous read I/Os. This is the number ofmedia manager synchronous physical read requests issued.This is the sum of QBACRIO when the buffer pool ID(QBACPID) is between 80 and 89.

BP32_SYNC_WRITE_IO FLOAT Number of immediate (synchronous) write I/Os. This is thesum of QBACIMW when the buffer pool ID (QBACPID) isbetween 80 and 89.

BP32_UPDATES FLOAT Number of times buffer update occurred for system pages.This is the sum of QBACSWS when the buffer pool ID(QBACPID) is between 80 and 89.

BP32_VPOOL_AREAD FLOAT Number of pages read asynchronously by prefetch underthe control of the agent. This column is valid fromDB2 V3 R1. This is the sum of QBACSIO when the bufferpool ID (QBACPID) is between 80 and 89.

BP4K_COND_GETP_UN FLOAT Number of times conditional GETPAGE requests could notbe satisfied for this size of buffer pools. This column is validfrom DB2 V3 R1. This is the sum of QBACNGT when thebuffer pool ID (QBACPID) is between 0 and 49.

BP4K_DYN_PREFETCH FLOAT Number of DYNAMIC PREFETCH requests issued. Thiscolumn is valid from DB2 V3 R1. This is the sum ofQBACDPF when the buffer pool ID (QBACPID) is between0 and 49.

BP4K_EXPANSIONS FLOAT Number of buffer pool expansions required. This is the sumof QBACBPX when the buffer pool ID (QBACPID) isbetween 0 and 49.

BP4K_GETPAGE FLOAT Number of GETPAGE requests issued. This is the sum ofQBACGET when the buffer pool ID (QBACPID) is between0 and 49.

BP4K_HPOOL_AREAD FLOAT Number of pages that were moved asynchronously from ahiperpool to a virtual buffer pool because of prefetch underthe agent’s control. This column is valid from DB2 V3 R1.This is the sum of QBACHPG when the buffer pool ID(QBACPID) is between 0 and 49.

BP4K_HPOOL_READ_SU FLOAT Number of successful synchronous read requests to move apage from a hiperpool to a virtual buffer pool. This columnis valid from DB2 V3 R1. This is the sum of QBACHREwhen the buffer pool ID (QBACPID) is between 0 and 49.

BP4K_HPOOL_READ_UN FLOAT Number of unsuccessful synchronous read requests to movea page from a hiperpool to a virtual buffer pool. Thiscolumn is valid from DB2 V3 R1. This is the sum ofQBACHRF when the buffer pool ID (QBACPID) is between0 and 49.

DB2 data tables



BP4K_HPOOL_WRIT_SU FLOAT Number of successful synchronous write requests to move apage from a virtual buffer pool to a hiperpool. This columnis valid from DB2 V3 R1. This is the sum of QBACHWRwhen the buffer pool ID (QBACPID) is between 0 and 49.

BP4K_HPOOL_WRIT_UN FLOAT Number of unsuccessful write requests to move a page froma virtual buffer pool to a hiperpool. This column is validfrom DB2 V3 R1. This is the sum of QBACHWF when thebuffer pool ID (QBACPID) is between 0 and 49.

BP4K_LIST_PREFETCH FLOAT Number of LIST PREFETCH requests issued. This column isvalid from DB2 V2 R3. This is the sum of QBACLPF whenthe buffer pool ID (QBACPID) is between 0 and 49.

BP4K_SEQ_PREFETCH FLOAT Number of SEQUENTIAL PREFETCH requests issued. Thisis the sum of QBACSEQ when the buffer pool ID(QBACPID) is between 0 and 49.

BP4K_SYNC_READ_IO FLOAT Number of synchronous read I/Os. This is the number ofmedia manager synchronous physical read requests issued.This is the sum of QBACRIO when the buffer pool ID(QBACPID) is between 0 and 49.

BP4K_SYNC_WRITE_IO FLOAT Number of immediate (synchronous) write I/Os. This is thesum of QBACIMW when the buffer pool ID (QBACPID) isbetween 0 and 49.

BP4K_UPDATES FLOAT Number of times buffer update occurred for system pages.This is the sum of QBACSWS when the buffer pool ID(QBACPID) is between 0 and 49.

BP4K_VPOOL_AREAD FLOAT Number of pages read asynchronously by prefetch underthe control of the agent. This column is valid fromDB2 V3 R1. This is the sum of QBACSIO when the bufferpool ID (QBACPID) is between 0 and 49.

CALL_STAT_REJECTS REAL Number of times an SQL CALL statement was rejected dueto the procedure being in the STOP ACTION(REJECT) state.This is the sum of QXCALLRJ.

CALL_STAT_TIMEOUTS REAL Number of times a CALL statement timed out waiting to bescheduled. This is the sum of QXCALLTO.

CHANGE_REQUESTS FLOAT Number of IRLM change requests issued. This is the sum ofQTXACHG.

CLAIM_WAIT_EVENTS FLOAT Number of wait trace events processed for waits for claimsto be released. This column is valid from DB2 V3 R1. Thisis the sum of QWACARNC.

CLAIMS FLOAT Number of claim requests issued. This column is valid fromDB2 V3 R1. This is the sum of QTXACLNO.

CLAIMS_UNSUCC FLOAT Number of unsuccessful claim requests issued. This columnis valid from DB2 V3 R1. This is the sum of QTXACLUN.

COMMIT_COUNT FLOAT Number of successful commits. This is the sum ofQWACCOMM.

CPU_HIGH_USED INTEGER Highest CPU time (in 16-microsecond timer units) used in asuccessful DB2 call, rather than a single SQL call. This is themaximum of QTXACHUS.

CPU_LIMIT INTEGER Maximum CPU 16-microsecond timer units that can be usedfor a thread. This is from QTXACLMT.

CRE_GLBL_TEMP_TAB REAL Number of CREATE GLBL TEMP TABLE. This is the sum ofQXCRGTT.

DB2 data tables



DCL_GLB_TEMP_TBL INTEGER Number of DECLARE GLOBAL TEMPORARY TABLEstatements executed. From QXDCLGTT, DB2 V7 or later.

DEADLOCKS FLOAT Number of times deadlocks were detected. This is the sumof QTXADEA.

DISC_PREP_MAXKEEPD REAL Number of times that an application process executablecopy of a prepared statement was discarded due to theMAXKEEPD system limit being exceeded. This is the sumof QXSTDEXP.

DRAIN_LOCK_EVENTS FLOAT Number of wait trace events processed for waits for drainlocks. This column is valid from DB2 V3 R1. This is thesum of QWACARND.

DRAIN_LOCK_SEC FLOAT Accumulated wait time for a drain lock, in seconds. Thiscolumn is valid from DB2 V3 R1. Calculated as the sum ofQWACAWDR/4 096 000 000.

DRAIN_WAIT_SEC FLOAT Accumulated wait time for a drain when waiting for claimsto be released, in seconds. This column is valid fromDB2 V3 R1. Calculated as the sum ofQWACAWCL/4 096 000 000.

DRAINS FLOAT Number of drain requests issued. This column is valid fromDB2 V3 R1. This is the sum of QTXADRNO.

DRAINS_UNSUCC FLOAT Number of unsuccessful drain requests issued. This columnis valid from DB2 V3 R1. This is the sum of QTXADRUN.

ELAPSED_DB2_SEC FLOAT Accumulated DB2 elapsed time, in seconds. This columncontains a value only if accounting class 2 is started.Calculated as the sum of QWACASC/4 096 000 000.

ELAPSED_SEC FLOAT Total elapsed time (class 1) of the application, in seconds.Calculated as the sum of the time intervals from QWACBSCto QWACESC.

ENTRY_EXIT_EVENTS FLOAT Number of DB2 entry and exit events processed. Thiscolumn contains a value only if accounting class 3 is started.This is the sum of QWACARNA.

GLB_TT_PAR_GROUPS INTEGER Total number of parallel groups that are part of a queryblock using a UDF and executed on a single DB2 due to theexistence of a Declared Temporary Table in the applicationprocess. From QXDEGDTT, DB2 V7 or later.

IMPLICIT_PREP REAL Number of times an implicit prepare was performedbecause KEEPDYNAMIC(YES) option was used and anOPEN, EXECUTE, or DESCRIBE of a dynamic statementoccurred but DB2 no longer had a valid copy of theprepared statement. This is the sum of QXSTIPRP.

INCREMENTAL_BINDS FLOAT Number of incremental binds excluding prepares. This isthe sum of QXINCRB.

IO_WAIT_DB_EVENTS INTEGER Number of wait trace events processed for waits fordatabase I/O, under the thread being reported. This field isnew with DB2 V6. It is calculated as the sum ofQWACARNE. It contains a value only if accounting class 3is started.

IO_WAIT_DB_SEC REAL Accumulated DB2 I/O elapsed wait time for database I/O,done under the thread being reported, in seconds. This fieldis new with DB2 V6. It is calculated as the sum ofQWACAWTI/4096E000000. It contains a value only isaccounting class 3is started.

DB2 data tables



IO_WAIT_EVENTS FLOAT Number of I/O wait trace requests processed for the threadbeing reported. This column contains a value only ifaccounting class 3 is started. This is the sum ofQWACARNE.

IO_WAIT_LOGWRT_EVT INTEGER Number of wait trace events processed for waits for logwrite I/O, under the thread being reported. This field isnew with DB2 V6. It is calculated as the sum ofQWACARLG. It contains a value only if accounting class 3is started.

IO_WAIT_LOGWRT_SEC REAL Accumulated DB2 I/O elapsed wait time for log write I/O,done under the thread being reported, in seconds. This fieldis new with DB2 V6. It is calculated as the sum ofQWACAWLG/4096E000000. It contains a value only isaccounting class 3 is started.

IO_WAIT_SEC FLOAT Accumulated DB2 I/O elapsed wait time for the threadbeing reported, in seconds. This column contains a valueonly if accounting class 3 is started. Calculated as the sumof QWACAWTI/4 096 000 000.

LATCH_SUSPENDS FLOAT Number of latch suspends. This is the number of times alock could not be obtained because of a latch conflict andthe unit of work was suspended. This is the sum ofQTXASLAT.

LOCK_CONT_WAITNUM REAL Number of wait trace events processed for waits for globallock contention. This is the sum of QWACARNJ.

LOCK_CONT_WAITSEC REAL Accumulated elapsed waiting time caused by thesuspension of an IRLM lock request due to a global lockcontention. Calculated as the sum ofQWACAWTJ/4 096 000 000.

LOCK_ESCAL_EXCL FLOAT Number of lock escalations to exclusive mode. This is thesum of QTXALEX.

LOCK_ESCAL_SHARED FLOAT Number of lock escalations to shared mode. This is the sumof QTXALES.

LOCK_LATCH_EVENTS FLOAT Number of lock and latch wait trace events processed. Thiscolumn contains a value only if accounting class 3 is started.This is the sum of QWACARNL.

LOCK_LATCH_SEC FLOAT Accumulated DB2 lock and latch elapsed time for the threadbeing reported, in seconds. This column contains a valueonly if accounting class 3 is started. Calculated as the sumof QWACAWTL/4 096 000 000.

LOCK_REQUESTS FLOAT Number of IRLM lock requests issued. This is the sum ofQTXALOCK.

LOCK_SUSPENDS FLOAT Number of lock suspends. This is the number of times alock could not be obtained because of a lock conflict and theunit of work was suspended. This is the sum ofQTXASLOC.

LOCK_TIMEOUTS FLOAT Number of lock time-outs. This is the number of times aunit of work was suspended for a time that exceeded thetime-out value. This is the sum of QTXATIM.

MAX_NESTING_SQL INTEGER Maximum level of nesting of user-defined functions, storedprocedures and triggers. New with DB2 V6. FromQXCASCDP.

DB2 data tables



MAX_STORAGE_LOB INTEGER Maximum storage used for LOB values, in MB. New withDB2 V6. From QXSTLOBV.

NORMAL INTEGER Number of DB2 threads that completed successfully. This isthe count of SMF type 101 accounting records withsuccessful completion (QWACRINV =< 16).

OTHER_IRLM_REQ FLOAT Number of other IRLM requests issued. This is the sum ofQTXAIRLM.

OTHER_READ_EVENTS FLOAT Number of wait trace events processed for waits for readI/O under a thread other than the thread being reported.This column contains a value only if accounting class 3 isstarted. This is the sum of QWACARNR.

OTHER_READ_SEC FLOAT Accumulated wait time for read I/O done under a threadother than the thread being reported, in seconds. Thiscolumn, valid from DB2 V2 R3, contains a value only ifaccounting class 3 is started. Calculated as the sum ofQWACAWTR/4 096 000 000.

OTHER_SUSPENDS FLOAT Number of other suspends. This is the number of times alock could not be obtained because of a conflict other than alock or latch conflict. This is the sum of QTXASOTH.

OTHER_WRITE_EVENTS FLOAT Number of wait trace events processed for waits for writeI/O under a thread other than the thread being reported.This column contains a value only if accounting class 3 isstarted. This is the sum of QWACARNW.

OTHER_WRITE_SEC FLOAT Accumulated wait time for write I/O done under a threadother than the thread being reported, in seconds. Thiscolumn, valid from DB2 V2 R3, contains a value only ifaccounting class 3 is started. Calculated as the sum ofQWACAWTW/4 096 000 000.

PAGE_LATCH_EVENTS FLOAT Number of wait trace events processed for page latchcontention. This column is valid from DB2 V3 R1. This isthe sum of QWACARNH.

PAGE_LATCH_SEC FLOAT Accumulated wait time because of page latch contention, inseconds. This column is valid from DB2 V3 R1. Calculatedas the sum of QWACAWTP/4 096 000 000.

PAGE_LOCKS_MAX INTEGER Maximum number of page locks concurrently held againstall table spaces by a single application when it wasexecuted. This is the maximum of QTXANPL.

PAR_DEGREE_AS_PLAN FLOAT Total number of parallel groups that were processed to theplanned parallel degree. This column is valid fromDB2 V3 R1. This is the sum of QXNORGRP.

PAR_DEGREE_LT_PLAN FLOAT Total number of parallel groups that were processed to aparallel degree less than planned because of storageshortage or contention on the buffer pool. This is the sum ofQXREDGRP. This column is valid from DB2 V3 R1.

PAR_DEGREE_MAX FLOAT Maximum degree of parallel I/O processing executedamong all parallel groups. It indicates the extent to whichqueries were processed in parallel. This column is validfrom DB2 V3 R1. This is the maximum of QXMAXDEG.

PAR_FALLBACK_BFR FLOAT Total number of parallel groups that fall back to sequentialoperation due to storage shortage or contention on a bufferpool. This column is valid from DB2 V3 R1. This is the sumof QXDEGBUF.

DB2 data tables



PAR_FALLBACK_ESA FLOAT Total number of parallel groups that fall back to sequentialoperation due to lack of ESA sort support. This column isvalid from DB2 V3 R1. This is the sum of QXDEGESA.

PAR_FALLBACK_UPDEL FLOAT Total number of parallel groups that fall back to sequentialoperation due to a cursor that can be used for update ordelete. This column is valid from DB2 V3 R1. This is thesum of QXDEGCUR.

PAR_GRP_EXECUTED FLOAT Total number of parallel groups that were executed. Thiscolumn is valid from DB2 V3 R1. This is the sum ofQXTOTGRP.

PARAL_GRPS_IN_BIND REAL Total number of parallel groups that were executed on asingle DB2 due to the COORDINATOR subsystemparameter being set to NO. When the statement was bound,the COORDINATOR subsystem parameter was set to YES.This is the sum of QXCOORNO.

PARAL_GRPS_IN_RR REAL Total number of parallel groups that were executed on asingle DB2 due to repeatable-read or read-stability isolation.This is the sum of QXISORR.

PARAL_SUBTASK_NUM REAL Number of parallel/subtasks created. For parallel/subtasks,this value is 0. This is the sum of QWACPCNT.

PARGRP_FELL_UNENCL REAL Total number of parallel groups that were executed insequential mode due to the unavailable enclave service. Thisis the sum of QXDEGENC.

PARGRP_IN_DSGRP REAL Total number of parallel groups that were intended to runacross the data sharing group. This count is incrementedonly on the parallelism coordinator at run time. This is thesum of QXXCBPNX.

PKGS_DBRMS_NUMBER INTEGER Number of packages or DBRMs for which accounting datawas collected. This is the sum of QWACPKGN.

PREP_FND_IN_CACHE REAL Number of times a PREPARE request was satisfied bymaking a copy from the prepared statement cache. This isthe sum of QXSTFND.

PRIOR_ENCL_TCB_SEC REAL The accumulated TCB time consumed prior to enclavecreation time. This value is new with DB2 V6. Calculated asthe sum of QWACPECT/4 096 000 000.

PURGED_PREP REAL Number of times that a prepared statement was purgedfrom the cache because a DROP, ALTER, or REVOKEstatement was issued on a dependent object. This is the sumof QXSTDINV.

QUERY_PARAL_FLAG INTEGER If non-zero, Query Parallelism is disabled by the RLF for atleast one dynamic SELECT statement in this thread. Thisfield is for accounting IFCID 0003 and does not apply toIFCID 0002. From QXRL FDPA.

QUERY_REQUESTS FLOAT Number of IRLM query requests issued. This is the sum ofQTXAQRY

REFORM_PAR_GRP_1 INTEGER Number of parallel groups for which DB2 reformulated theparallel plan because the sysplex configuration changed atrun time from the sysplex configuration at bind time. Newwith DB2 V6. From QXREPOP1.

DB2 data tables



REFORM_PAR_GRP_2 INTEGER Number of parallel groups for which DB2 reformulated theparallel plan because the buffer pool resources changed atrun time from the buffer pool resources at bind time. Newwith DB2 V6. From QXREPOP2.

REOPT_NUM REAL Total number of times re-optimization occurs. This fielddoes not apply to IFCID 0002. This is the sum ofQXSTREOP.

RID_LIST_EXCEEDS FLOAT Number of times one or more RID lists were not used for agiven RID list process because the number of RIDs exceededone or more internal limits. This column is valid fromDB2 V2 R3. This is the sum of QXMRMIAP.

RID_LIST_NOT_USED FLOAT Number of times a RID list was not used for a given RIDlist process because no storage was available to hold the listof RIDs. This column is valid from DB2 V2 R3. This is thesum of QXNSMIAP.

RID_LIST_USED FLOAT Number of times RID list processing was used. This columnis incremented once for a given table access when RID listprocessing is used for index access with LIST PREFETCH,or for multiple index access. This column is valid fromDB2 V2 R3. This is the sum of QXMIAP.

ROWID_ACC_TO_IDX INTEGER Number of times that DB2 tried to use direct row access butused an index instead. New with DB2 V6. From QXROIIDX.

ROWID_ACC_TO_TS INTEGER Number of times that DB2 tried to use direct row access butused a table space scan instead. New with DB2 V6. FromQXROITS.

ROWID_SUCC_ACC INTEGER Number of times that DB2 used direct row accesssuccessfully. New with DB2 V6. From QXROIMAT.

SEND_MSG_WAITNUM REAL Number of wait trace events processed for sendingmessages to other members in the data sharing group. Thisis the sum of QWACARNG.

SEND_MSG_WAITSEC REAL Accumulated elapsed waiting time due to suspensionscaused by sending notify messages to other members in thedata sharing group. Calculated as the sum ofQWACAWTG/4 096 000 000.

SERVICE_TASK_SEC FLOAT Accumulated wait time because of synchronous unitswitching to DB2 services, in seconds. This column, validfrom DB2 V2 R3, contains a value only if accounting class 3is started. Calculated as the sum ofQWACAWTE/4 096 000 000.

SERVICE_UNIT_LIMIT INTEGER Maximum number of MVS service units that can be usedfor a thread. This is from QTXASLMT.

SERV_TASK_CA_EVT INTEGER Number of wait trace events processed for waits forsynchronous execution unit switching to the DB2 commit orabort service tasks. New with DB2 V6. This value is set byaccounting class 3 trace. Calculated as the sum ofQWACARNS.

SERV_TASK_CA_SEC REAL Accumulated wait time due to synchronous execution unitswitch to the DB2 commit phase 2, abort or de-allocationprocessing services. New with DB2 V6. This value is set byaccounting class 3 trace. Calculated as the sum ofQWACAWTE/4 096 000 000.

DB2 data tables



SERV_TASK_DS_EVT INTEGER Number of wait trace events processed for waits forsynchronous execution unit switching to DataspaceManager service task. New with DB2 V6. This value is setby accounting class 3 trace. Calculated as the sum ofQWAXDSNS.

SERV_TASK_DS_SEC REAL Accumulated wait time due to synchronous execution unitswitch to the DB2 Dataspace Manager Services, whichinclude Define, Extend, Delete or Reset data set. New withDB2 V6. From ACCTG class 3 trace. Calculated as the sumof QWAXDSSE/4 096 000 000.

SERV_TASK_EVENTS FLOAT Number of wait trace events processed for waits forsynchronous unit switching to DB2 service tasks. Thiscolumn contains a value only if accounting class 3 is started.This is the sum of QWACARNS.

SERV_TASK_OC_EVT INTEGER Number of wait trace events processed for waits forsynchronous execution unit switching to the DB2Open/Close service. New with DB2 V6. This value is set byaccounting class 3 trace. Calculated as the sum ofQWAXOCNS.

SERV_TASK_OC_SEC REAL Accumulated wait time due to synchronous execution unitswitch to the DB2 Open/Close data set service or the HSMrecall service. New with DB2 V6. This value is set byaccounting class 3 trace. Calculated as the sum ofQWAXOCSE/4 096 000 000.

SERV_TASK_OTH_EVT INTEGER Number of wait trace events processed for waits forsynchronous execution unit switching to service tasks otherthan the ones reported in the previous columns. New withDB2 V6. This value is set by acctg class 3 trace. Calculatedas the sum of QWAXOTNS.

SERV_TASK_OTH_SEC REAL Accumulated wait time due to synchronous execution unitswitch to DB2 service tasks other than the ones reported inthe previous columns. New with DB2 V6. From ACCTGclass 3 trace. Calculated as the sum of QWAXOTSE/4 096000 000.

SERV_TASK_SYS_EVT INTEGER Number of wait trace events processed for waits forsynchronous execution unit switching to the DB2SYSLGRNG recording service. New with DB2 V6. Thisvalue is set by accounting class 3 trace. Calculated as thesum of QWAXSLNS.

SERV_TASK_SYS_SEC REAL Accumulated wait time due to synchronous execution unitswitch to the DB2 SYSLGRNG recording service. New withDB2 V6. This value is set by accounting class 3 trace.Calculated as the sum of QWAXSLSE/4 096 000 000.

SKIPDB2_FOR_NOSTOR REAL Number of times the parallelism coordinator had to bypassa DB2 when distributing tasks because there was notenough buffer pool storage on one or more DB2 members.This is the sum of QXXCSKIP.

SP_ENTR_EX_EVENTS REAL Number of SQL entry or exit events performed by storedprocedures. This is the sum of QWACSPNE.

SP_TCBSCHED_SEC REAL Total elapsed waiting time available TCB before the storedprocedure could be scheduled. Calculated as the sum ofQWACCAST/4 096 000 000.

DB2 data tables



SQL_ALLOCATE_CRS REAL Number of SQL ALLOCATE CURSOR statements issued.This is the sum of QXALOCC.

SQL_ALTER FLOAT Number of SQL ALTER statements issued. Calculated as thesum of QXALTST + QXALTTS + QXALTTA + QXALTIX +QXALDAB.

SQL_ALTER_OTH REAL Number of SQL ALTER statements issued, to alter one ofthe following objects (new with DB2 V6): user-definedfunction and procedure. Calculated as the sum ofQXALUDF + QXALPRO.

SQL_ASSOC_LOCATOR REAL Number of SQL ASSOCIATE LOCATOR statements issued.This is the sum of QXALOCL.

SQL_CALL REAL Number of SQL CALL statements issued. This is the sum ofQXCALL.

SQL_CLOSE FLOAT Number of SQL CLOSE cursor statements issued. This is thesum of QXCLOSE.

SQL_COMMENT_ON FLOAT Number of SQL COMMENT ON statements issued. This isthe sum of QXCMTON.

SQL_CONNECT_TYPE1 FLOAT Number of SQL CONNECT type 1 statements issued. Thiscolumn is valid from DB2 V3 R1. This is the sum ofQXCON1.

SQL_CONNECT_TYPE2 FLOAT Number of SQL CONNECT type 2 statements issued. Thiscolumn is valid from DB2 V3 R1. This is the sum ofQXCON2.

SQL_CREATE FLOAT Number of SQL CREATE statements issued. Calculated asthe sum of QXCRTAB + QXCRINX + QXCTABS +QXCRSYN + QXCRDAB + QXCRSTG + QXDEFVU +QXCRALS.

SQL_CREATE_OTH REAL Number of SQL CREATE statements issued, to create one ofthe following objects (new with DB2 V6): trigger, distincttype, user-defined function, procedure and auxiliary table.Calculated as the sum of QXCTRIG + QXCDIST +QXCRUDF + QXCRPRO + QXCRATB.

SQL_DELETE FLOAT Number of SQL DELETE statements issued. This is the sumof QXDELET.

SQL_DESCRIBE FLOAT Number of SQL DESCRIBE statements issued. This is thesum of QXDESC.

SQL_DESCRIBE_TABLE FLOAT Number of SQL DESCRIBE TABLE statements issued. Thiscolumn is valid from DB2 V2 R3. This is the sum ofQXDSCRTB.

SQL_DROP FLOAT Number of SQL DROP statements issued. Calculated as thesum of QXDRPIX + QXDRPTA + QXDRPTS + QXDRPTB +QXDRPSY + QXDRPST + QXDRPVU + QXDRPAL +QXDRPPKG.

SQL_DROP_OTH REAL Number of SQL DROP statements issued, to drop one of thefollowing objects (new with DB2 V6): trigger, user-definedfunction, procedure and distinct type. Calculated as the sumof QXDRPTR + QXDRPFN + QXDRPPR + QXDDIST.

SQL_ELAPS_INSP_SEC REAL The total elapsed time spent for stored procedures inexecuting SQL. This value is new with DB2 V6. Calculatedas the sum of QWACSPEB/4 096 000 000.

DB2 data tables



SQL_FETCH FLOAT Number of SQL FETCH cursor statements issued. This isthe sum of QXFETCH.

SQL_FREE_LOCATOR REAL Number of FREE LOCATOR statements executed. New withDB2 V6. From QXFREEL.

SQL_GRANT FLOAT Number of SQL GRANT statements issued. This is the sumof QXGRANT.

SQL_HOLD_LOCATOR REAL Number of HOLD LOCATOR statements executed. Newwith DB2 V6. From QXHOLDL.

SQL_INSERT FLOAT Number of SQL INSERT statements issued. This is the sumof QXINSRT.

SQL_LABEL_ON FLOAT Number of SQL LABEL ON statements issued. This is thesum of QXLABON.

SQL_LOCK_TABLE FLOAT Number of SQL LOCK TABLE statements issued. This is thesum of QXLOCK.

SQL_OPEN FLOAT Number of SQL OPEN cursor statements issued. This is thesum of QXOPEN.

SQL_PREPARE FLOAT Number of SQL PREPARE statements issued. This is thesum of QXPREP.

SQL_RELEASE FLOAT Number of SQL RELEASE statements issued. This column isvalid from DB2 V3 R1. This is the sum of QXREL.

SQL_RENAME_TAB REAL Number of SQL RENAME TABLE statements issued. Thisthe sum of QARNTAB.

SQL_REVOKE FLOAT Number of SQL REVOKE statements issued. This is the sumof QXREVOK.

SQL_SELECT FLOAT Number of SQL SELECT statements issued. This is the sumof QXSELECT.

SQL_SET_CONNECTION FLOAT Number of SQL SET CONNECTION statements issued. Thiscolumn is valid from DB2 V3 R1. This is the sum ofQXSETCON.

SQL_SET_CUR_DEGREE FLOAT Number of SQL SET CURRENT DEGREE statements issued.This column is valid from DB2 V3 R1. This is the sum ofQXSETCDG.

SQL_SET_CURR_PATH REAL Number of SET CURRENT PATH statements executed. Newwith DB2 V6. From QXSETPTH.

SQL_SET_CURR_PREC INTEGER Number of SQL SET CURRENT PRECISION statementsexecuted. From QXSETCPR, DB2 V7 or later.

SQL_SET_CUR_RULES REAL Number of SQL SET CURRENT RULES statements issued.This is the sum of QXSETCRL.

SQL_SET_CUR_SQLID FLOAT Number of SQL SET CURRENT SQLID statements issued.This is the sum of QXSETSQL.

SQL_SET_HOST_VAR FLOAT Number of SQL SET HOST VARIABLE statements issued.This column is valid from DB2 V2 R3. This is the sum ofQXSETHV.

SQL_UPDATE FLOAT Number of SQL UPDATE statements issued. This is the sumof QXUPDTE.

SQLCALL_SEC_INSP REAL Accumulated TCB time for processing SQL CALLstatements in the DB2 stored-procedures address space.Calculated as the sum of QWACSPCP/4 096 000 000.

DB2 data tables



SQLCALL_WAIT_NUM REAL Number of times an SQL CALL statement had to wait foran available TCB, before the stored procedure could bescheduled. This is the sum of QWACCANM.

SQLSTAT_SEC_INSP REAL Accumulated TCB time in DB2 for processing SQLstatements issued by stored procedures. Calculated as thesum of QWACSPTT/4 096 000 000.

SRB_DB2_SEC FLOAT Accumulated DB2 SRB time, in seconds. This columncontains a value only if accounting class 2 is started.Calculated as the sum of QWACASRB/4 096 000 000.

SRB_SEC FLOAT Total CPU time (class 1) spent for SRB execution, inseconds. Calculated as sum of the time intervals fromQWACBSRB to QWACESRB.

STOR_PROC_ABENDS REAL Number of times a CALL statement timed out waiting to bescheduled. This is the sum of QXCALLAB.

SU_COVERS_FACTOR REAL This field contains the SU conversion factor. This value isuseful for accounting monitors that attempt to roll up CPUexecution times across multiple DB2s running on differentmachines. From QWACSUCV.

SVPOINT_REQ INTEGER Number of save-point requests. This value is new with DB2V7.

SVPOINT_RLS_REQ INTEGER Number of release save-point requests. This value is newwith DB2 V7.

SVPOINT_ROLLB_REQ INTEGER Number of rollbacks to save-point requests. This value isnew with DB2 V7.

TCB_DB2_SEC FLOAT Accumulated DB2 TCB time, in seconds. This columncontains a value only if accounting class 2 is started.Calculated as the sum of QWACAJST/4 096 000 000.

TCB_SEC FLOAT Total CPU time (class 1) spent for TCB execution, inseconds. Calculated as the sum of the time intervals fromQWACBJST to QWACEJST.

TOT_ELAPS_INSP_SEC REAL The total elapsed time spent in stored procedures, includingthe time in executing SQL. This value is new with DB2 V6.Calculated as the sum of QWACSPEA/4 096 000 000.

TRIG_ENCL_EPS_SEC REAL The accumulated elapsed time expended in executingtriggers under an enclave. This value is new with DB2 V6.Calculated as the sum of QWACTREE/4 096 000 000.

TRIG_ENCL_TCB_SEC REAL The accumulated TCB time consumed in executing triggersunder an enclave. This value is new with DB2 V6.Calculated as the sum of QWACTRTE/4 096 000 000.

TRIGGER_ERRORS INTEGER Number of times an error occurred during execution of atriggered action. New with DB2 V6. From QXTRGERR.

TRIG_NENCL_EPS_SEC REAL The accumulated elapsed time expended in executingtriggers not under an enclave. This value is new with DB2V6. Calculated as the sum of QWACTRET/4 096 000 000.

TRIG_NENCL_TCB_SEC REAL The accumulated TCB time consumed in executing triggersnot under an enclave. This value is new with DB2 V6.Calculated as the sum of QWACTRTT/4 096 000 000.

UDF_ABENDED INTEGER Number of times a user-defined function abnormallyterminated. New with DB2 V6. From QXCAUDAB.

DB2 data tables



UDF_ENTR_EX_EVENTS INTEGER The number of SQL entry or exit events performed byuser-define functions. This value, new with DB2 V6, is setonly when accounting trace class 2 is active. Calculated asthe sum of QWACUDNE.

UDF_EXECUTED INTEGER Number of user-defined functions executed. New with DB2V6. From QXCAUD.

UDF_REJECTED INTEGER Number of times a user-defined function was rejected. Newwith DB2 V6. From QXCAUDRJ.

UDF_REQUESTS_SEC REAL The accumulated TCB time used to satisfy user-definedfunction requests processed in a DB2 stored-procedure/WLM address space. This value, new with DB2V6, is set only when accounting trace class 1 is active.Calculated as the sum of QWACUDCP/4 096 000 000.

UDF_SQL_ELAPS_SEC REAL The total elapsed time spent by user-defined functionsprocessing SQL. This value, new with DB2 V6, is set onlywhen accounting trace class 2 is active. Calculated as thesum of QWACUDEB/4 096 000 000.

UDF_SQLSTAT_SEC REAL The accumulated TCB time consumed in DB2 for processingSQL statements issued by user-defined functions. Includedin UDF_REQUESTS_SEC. This value, new with DB2 V6, isset only when accounting trace class 2 is active. Calculatedas the sum of QWACUDTT/4 096 000 000.

UDF_TCBSCHED_SEC REAL The total elapsed time spent waiting for an available TCB,before the user-defined function could be scheduled. Thisvalue, new with DB2 V6, is set only when accounting traceclass 3 is active. Calculated as the sum of QWACUDST/4096 000 000.

UDF_TOT_ELAPS_SEC REAL The total elapsed time spent in user-defined functions,including time spent by user-defined functions processingSQL. This value, new with DB2 V6, is set only whenaccounting trace class 1 is active. Calculated as the sum ofQWACUDEA/4 096 000 000.

UDF_TIMED_OUT INTEGER Number of times a user-defined function timed out waitingto be scheduled. New with DB2 V6. From QXCAUDTO.

UNLOCK_REQUESTS FLOAT Number of IRLM unlock requests issued. Calculated as thesum of QTXAUNLK.

DB2 data tables


Lookup tablesThis section describes the lookup table specific to the DB2 component.

DB2_APPLICATIONThis lookup table contains DB2 plan names and their corresponding applicationand profile names. It converts the DB2 plan name into an application name to beused as key in some of the DB2 component tables.

This lookup table updates these tables:DB2_APPLICATION_xDB2_APPL_DIST_xDB2_USER_APPL_xDB2_USER_AP_DIST_x




APPLICATION_NAME k CHAR(18) Application name used for an application group.

DB2_PLAN k CHAR(8) DB2 plan name. From QWHCPLAN.

PROFILE CHAR(12) Profile for the plan. You can use this column for furthergrouping of DB2 plans into profiles such as transaction, query,batch, and so on.

Example of table contents

MVS DB2SYSTEM SYSTEM APPLICATION DB2

ID ID NAME PLAN PROFILE------ ------ ------------------ -------- -------% % QMF QMF311 QUERY% % QMF QMF310 QUERY% % QMF QMF240 QUERY% % QMF QMF230 QUERY% % QMF DSQPLAN QUERY% % AS DQ* QUERY% % BATCH SQL DSNTEP2 BATCH% % SPUFI CS DSNESPCS QUERY% % SPUFI RR DSNESPRR QUERY% % CATALOG QUERY DSNQCATV QUERY% % DIST SERVER DISTSERV SERVER% % TIVOLI DECISION SUPPORT FOR OS/390

DRLPLAN QUERY% % OTHER * OTHER

DB2 lookup tables


DB2 lookup tables


Chapter 8. Reports

The DB2 component provides reports that can help you assess the general status ofyour DB2 subsystem.

The DB2 component provides these reports:v DB2 Application Response Times, Detail reportv DB2 Application Response Times, Overview reportv DB2 Application Response Times, Trend reportv DB2 Transaction Statistics, Detail reportv DB2 Transaction Statistics, Overview reportv DB2 Transaction Statistics, Trend reportv DB2 System Services Statistics, Detail reportv DB2 Database Services Statistics, Detail reportv DB2 System Statistics, Overview reportv DB2 System CPU % by Address Space, Overview reportv DB2 System Statistics, Trend reportv DB2 General Measure by Profile, Overview reportv DB2 Application Profiles, Overview reportv DB2 Application Profiles, Trend reportv DB2 Buffer Pool Statistics, Detail reportv DB2 Buffer Pool Statistics, Overview reportv DB2 EDM Pool Statistics, Detail reportv DB2 EDM Pool Statistics, Overview reportv DB2 Buffer Pool Exceptions reportv DB2 System Parameters reportv DB2 Packages Class 7,8 Times, Overview reportv DB2 DBRMs Class 7,8 Times, Overview reportv DB2 Group Buffer Pool Statistics, Detail reportv DB2 Data Sharing Locking Statistics, Detail reportv DB2 Group Buffer Pool Accounting, Overview reportv DB2 Data Sharing Locking Accounting, Overview reportv DB2 User Defined Functions, Detail reportv DB2 User Defined Functions, Overview reportv DB2 Triggers, Detail reportv DB2 Triggers, Overview reportv DB2 Row ID, Detail reportv DB2 Row ID, Overview reportv DB2 Secondary Group Buffer Pool Statistics, Detail reportv DB2 Application Wait Times, Detail reportv DB2 Application Wait Times, Overview reportv DB2 Application Wait Times, Trend report

DB2 report descriptionsThis section describes the reports provided with the DB2 component.

DB2 Application Response Times, Detail reportThis report shows response times by application, as defined in theDB2_APPLICATION lookup table. For more information on using this report, referto the System Performance Feature Guide.

117


Report ID DB201



Attributes DB2, Performance, Response, Application



Application name The application name, as defined in theDB2_APPLICATION lookup table.

Profile The type of application (transaction, query, batchand so on) as defined in the DB2_APPLICATIONlookup table.

Elapsed seconds avg The average elapsed time during the reportinterval, in seconds. Calculated as:SUM(ELAPSED_SEC) / (SUM(COMMIT_COUNT)+ SUM(ABORT_COUNT)).

Elapsed seconds max The maximum elapsed time during the reportinterval, in seconds. Calculated as:MAX((ELAPSED_SEC) / (COMMIT_COUNT +ABORT_COUNT)).

Elapsed seconds min The minimum elapsed time during the reportinterval, in seconds. Calculated as:MIN((ELAPSED_SEC) / (COMMIT_COUNT +ABORT_COUNT)).

DB2 Application Response Times, DetailSystem: ’MVS1’ DB2 ID: ’DB2A’

Date: ’1999-11-19’ to ’2000-03-09’

Elapsed Elapsed ElapsedApplication seconds seconds seconds Commit Abort

name Profile avg max min count count------------ ----------- ---------- ---------- -------- ------------ ------TDS/OS/390 QUERY 9.39 23.27 0.16 13218 18QMF QUERY 7.83 25.20 0.13 7876 8SPUFI RR QUERY 4.60 21.14 0.31 73 5


Figure 18. Example of a DB2 Application Response Times, Detail report

DB2 reports


Commit count The number of commits that occurred during thereport interval.

Abort count The number of aborts that occurred during thereport interval.

DB2 reports


DB2 Application Response Times, Overview reportThis report shows application response times. One bar in the chart represents oneapplication as defined in the DB2_APPLICATION lookup table. You can selectapplications by name using the Appl_name_list variable. If you do not select anyapplication names, the report shows the 15 most-frequent (highest commit-count)applications. Use the Max_rows variable to limit the number of elements shown inthe chart.


Report ID DB202



Attributes DB2, Performance, Response, Application, Overview

Variables MVS_system_ID, DB2_system_ID, From_date, To_date,Appl_name_list, Max_rows


Application name The application name as defined in theDB2_APPLICATION lookup table.

Elapsed seconds avg The average elapsed time during the reportinterval, in seconds. Calculated as:SUM(ELAPSED_SEC) / (SUM(COMMIT_COUNT)+ SUM(ABORT_COUNT)).

Figure 19. Example of a DB2 Application Response Times, Overview report

DB2 reports


||||||

DB2 Application Response Times, Trend reportThis report shows application response times over a period of time. Each line inthe chart represents one application as defined in the DB2_APPLICATION lookuptable. You can select applications by name using the Appl_name_list variable. Ifyou do not select any applications names, the report shows all applications.


Report ID DB203


Source DB2_APPLICATION_W

Attributes DB2, Performance, Response, Application, Trend, Weekly

Variables MVS_system_ID, DB2_system_ID, From_date, To_date,Appl_name_list


Week start date The first day of the week of the measurement.

Elapsed seconds The average elapsed time, in seconds. Calculatedas: SUM(ELAPSED_SEC) /(SUM(COMMIT_COUNT) +SUM(ABORT_COUNT)).

Application name The application name as defined in theDB2_APPLICATION lookup table.

Figure 20. Example of a DB2 Application Response Times, Trend report

DB2 reports


DB2 Transaction Statistics, Detail reportThis report shows transaction statistics details for every DB2 plan. This reportrequires that accounting class 2 and class 3 traces were active during the reportinterval. Plans are ordered by number of commits in descending order. For moreinformation on using this report, refer to the System Performance Feature Guide.


Report ID DB204


Source DB2_TRANSACTION_D

Attributes DB2, Performance, DB2_plan, Transaction



DB2 plan The DB2 plan name. DB2 command threads have ablank DB2 plan name.

Elapsed seconds avg The average elapsed time, in seconds. Calculatedas: SUM(ELAPSED_SEC) /(SUM(COMMIT_COUNT) +SUM(ABORT_COUNT)).

CPU seconds avg The total average CPU time during the reportinterval, in seconds. Calculated as: SUM(TCB_SEC)/ (SUM(COMMIT_COUNT) +SUM(ABORT_COUNT)).

DB2 CPU seconds avg The average CPU time spent in DB2 during thereport interval, in seconds. Accounting trace class 2

DB2 04 Transaction Statistics, DetailSystem: ’MVS1’ DB2 ID: ’DB2A’

Date: ’2000-01-11’ to ’2000-03-09’

DB2 Lock ServiceElapsed CPU DB2 CPU CPU(SRB) CPU(SRB) IO wait latch waitseconds seconds seconds seconds seconds seconds seconds seconds

DB2 plan avg avg avg avg avg avg avg avg-------- -------- ------- ------- -------- -------- ------- -------- -------DB2PM211 0.88 0.006 0.004 0.000 0.000 0.000 0.000 0.000DRLPLAN 21.68 7.332 4.019 0.009 0.000 0.017 0.019 0.000QMF310 12.90 0.680 0.165 0.004 0.000 0.001 0.001 0.000DSNUTIL 0.46 0.028 0.000 0.003 0.000 0.000 0.000 0.000DISTSERV 2128.04 0.647 0.004 1.164 0.002 0.001 0.000 0.000DSNESPRR 6.15 0.115 0.002 0.002 0.000 0.000 0.000 0.000

Archive Archivelogwait logread Drainseconds seconds seconds Commit Abort

avg avg avg count count------- ------- ------- ------ -----0.000 0.000 0.000 50983 00.000 0.000 0.000 7098 1230.000 0.000 0.000 4227 620.000 0.000 0.000 1391 110.000 0.000 0.000 95 00.000 0.000 0.000 55 4

====== =====63849 200


Figure 21. Example of a DB2 Transaction Statistics, Detail report

DB2 reports


is required. Calculated as: SUM(TCB_DB2_SEC) /(SUM(COMMIT_COUNT) +SUM(ABORT_COUNT)).

CPU(SRB) seconds avg The total average SRB time during the reportinterval, in seconds. This time reflects the SRB timefor the entire address space. So, it is valid only foragents running single users or tasks per addressspace (such as, TSO, batch jobs, or IMS MPPs).Calculated as: SUM(SRB_SEC) /(SUM(COMMIT_COUNT) +SUM(ABORT_COUNT)).

DB2 CPU(SRB) seconds avg The average SRB time spent in DB2 during thereport interval, in seconds. This time reflects theDB2 SRB time for the entire address space. So, it isvalid only for agents running single users or tasksper address space (such as TSO, batch jobs, or IMSMPPs). Accounting trace class 2 is required.Calculated as: SUM(SRB_DB2_SEC) /(SUM(COMMIT_COUNT) +SUM(ABORT_COUNT)).

IO wait seconds avg The average I/O wait time during the reportinterval, in seconds. Accounting trace class 3 isrequired. Calculated as: SUM(IO_WAIT_SEC +OTHER_READ_SEC + OTHER_WRITE_SEC) /(SUM(COMMIT_COUNT) +SUM(ABORT_COUNT)).

Lock latch seconds avg The average time spent in lock/latch managementwithin DB2, in seconds. Accounting trace class 3 isrequired. Calculated as: SUM(LOCK_LATCH_SEC)/ (SUM(COMMIT_COUNT) +SUM(ABORT_COUNT)).

Service wait seconds avg The average wait time due to synchronous unitswitching to DB2 services, in seconds. Accountingtrace class 3 is required. Calculated as:SUM(SERVICE_TASK_SEC) /(SUM(COMMIT_COUNT) +SUM(ABORT_COUNT)).

Archive logwait seconds avg The average wait time due to processing ofARCHIVE LOG MODE(QIUESCE) commands, inseconds. Accounting trace class 3 is required.Calculated as: SUM(ARC_LOGWAIT_SEC) /(SUM(COMMIT_COUNT) +SUM(ABORT_COUNT)).

Archive logread seconds avg The average wait time for an archive read fromtape, in seconds. Accounting trace class 3 isrequired. This value is available only with DB2Version 3 Release 1. Calculated as:SUM(ARC_LOGREAD_SEC) /(SUM(COMMIT_COUNT) +SUM(ABORT_COUNT)).

DB2 reports


Drain seconds avg The average wait time for a drain or a drain lock,in seconds. Accounting trace class 3 is required.This value is available only with DB2 Version 3Release 1. Calculated as: SUM(DRAIN_WAIT_SEC+ DRAIN_LOCK_SEC) /(SUM(COMMIT_COUNT) +SUM(ABORT_COUNT)).



DB2 reports


DB2 Transaction Statistics, Overview reportThis report shows the number of commits and aborts that occurred for the mostfrequent plan names. Use the Maxrows variable to limit the number of elementsshown in the chart.


Report ID DB205


Source DB2_TRANSACTION_D

Attributes DB2, Performance, DB2_plan, Transaction, Overview

Variables MVS_system_ID, DB2_system_ID, From_date, To_date, Max_rows


DB2 plan The DB2 plan name.



Figure 22. Example of a DB2 Transaction Statistics, Overview report

DB2 reports


DB2 Transaction Statistics, Trend reportThis report shows the number of commits for the most frequently used DB2 plans.You can select plan names using the DB2_plan_list variable. If you do not selectany plan names, the report shows all plans.


Report ID DB206


Source DB2_TRANSACTION_W

Attributes DB2, Performance, Transaction, Weekly, Trend

Variables MVS_system_ID, DB2_system_ID, From_date, To_date,DB2_plan_list


DB2 plan The DB2 plan name.


Commit count The number of commits that occurred during theweek.

x

x

x

x

x

x

x

x

x

x

+++

++

+

++

+

+

Figure 23. Example of a DB2 Transaction Statistics, Trend report

DB2 reports


DB2 System Services Statistics, Detail reportThis report contains DB2 system services information. It shows the main activitieshandled by the DB2 system service address space.


Report ID DB207


Source DB2_SYSTEM_T

Attributes DB2, Performance, System, Hourly, Detail

Variables MVS_system_ID, DB2_system_ID, Date, Period_name_list


Time The time of the measurement.

Identify requests The number of successful identify requests. This isthe number of successful connections to DB2 byTSO, IMS, CICS, CAF, or a DB2 utility.

Signon requests The number of successful sign-on requests by IMSor CICS.

Create threads The number of successful create thread requests.This is the number of threads created, excludingdatabase access threads.

CICS/IMS commits The number of successful phase 2 end commitrequests.

TSO/CAF commits The number of successful single-phase(synchronized) commit requests.

DB2 System Services Statistics, DetailSystem: ’MVS1’ DB2 ID: ’DB2A’

Date: ’2000-01-11’ Period(s): (’PRIME’)

LogIdentify Signon Create CICS/IMS TSO/CAF Abort writes DB2

Time requests requests threads commits commits count (total) commands------------- --------- -------- --------- -------- ------ --------- --------08.00 0 0 6 0 0 0 0 009.00 0 0 18 0 0 0 0 010.00 1 0 1 0 0 0 0 011.00 80 0 125 0 577 5 66681 212.00 26 0 180 0 1040 0 272426 613.00 19 9 17 0 0 0 10769 014.00 1 1 35 1 0 0 33 015.00 14 10 303 45 0 0 2270 016.00 1 1 1028 245 0 1 12908 0

======== ========= ======== ========= ======== ====== ========= ========142 21 1713 291 1617 6 365087 8


Figure 24. Example of a DB2 System Services Statistics, Detail report

DB2 reports


Abort count The number of successful abort requests. This isthe number of times a unit of recovery backed outfor reasons such as application program abend,application canceled by operator, or thread abendbecause of resource shortage.

Log writes (total) The total number of log write requests processed.Calculated as: SUM(WRITES_NOWAIT) +SUM(WRITES_FORCE).

DB2 commands The sum of all DB2 commands issued. Thisincludes normal or abnormal completion of thecommands.

DB2 reports


DB2 Database Services Statistics, Detail reportThis report contains DB2 database services statistics. It shows the main activitieshandled by the DB2 database services address space. For more information onusing this report, refer to the System Performance Feature Guide.


Report ID DB208


Source DB2_DATABASE_T

Attributes DB2, Performance, Database, Hourly, Detail




SQL stmts DML The sum of data manipulation language (DML)type SQL statements.

SQL stmts DDL The sum of data definition language (DDL) typeSQL statements.

SQL stmts control The sum of control type SQL statements.

Plan allocations The number of successful plan allocations. This isthe number of times DB2 successfully completedrequests by the user to create a thread by theattachment facility.

Binds (plans + pkgs) The number of plans and packages successfullybound. Calculated as: (PLANS_BOUND +PKG_BOUND).

Rebinds (plans + pkgs) The number of plans and packages successfullyrebound. Calculated as: (PLANS_REBOUND +PKG_REBOUND).

DB2 Database Services Statistics, DetailSystem: ’MVS1’ DB2 ID: ’DB2A’


SQL SQL SQL Plan Binds Rebinds Lock Lock Lockstmts stmts stmts alloca- (plans (plans Lock Dead- suspen- time- escala-

Time DML DDL control tions + pkgs) + pkgs) requests locks sions outs tions----- --------- ------- ------- ------- ------- ------- ---------- ------ ------- ------ -------08.00 207018 0 0 129 0 0 170576 0 0 0 009.00 1380067 23 5 221 0 0 711376 0 2 0 010.00 158480 0 0 97 0 0 48496 0 0 0 011.00 198293 12 3 233 0 0 167216 1 4 0 012.00 1105511 29 0 197 0 0 1024144 0 23 5 013.00 15191 0 0 73 0 0 138800 0 13 8 014.00 49482 257 0 166 0 0 1600352 0 14 9 015.00 185172 182 38 244 0 0 1883536 1 20 2 016.00 146239 231 8 90 0 0 915632 0 0 0 0

========= ======= ======= ======= ======= ======= ========== ====== ======= ====== =======3445453 734 54 1450 0 0 6660128 2 76 24 0


Figure 25. Example of a DB2 Database Services Statistics, Detail report

DB2 reports


Lock requests The number lock requests issued.

Deadlocks The number of times deadlocks were detected.

Lock suspensions The number of lock suspends. This is the numberof times a lock could not be obtained because of alock conflict and the unit of work was suspended.

Lock timeouts The number of lock timeouts. This is the number oftimes a unit of work was suspended because atime exceeded the time-out value.

Lock escalations The total number of lock escalations. Calculated as:(LOCK_ESCAL_EXCL + LOCK_ESCAL_SHARED).

DB2 reports


DB2 System Statistics, Overview reportThis report shows thread reuse, log manager efficiency, and a commit profileindicating load origin (TSO/CAF or CICS/IMS). For more information on usingthis report, refer to the System Performance Feature Guide.


Report ID DB209


Source DB2_SYSTEM_T

Attributes DB2, Performance, System, Overview



Thread reuse The value showing an indication of whatpercentage of the threads are being reused (onlyapplicable to CICS and IMS threads). If the reportquery calculation generates a negative value(which is possible), a zero value will be shown.Calculated as: (SUM(SIGNON) −SUM(CREATE_THREAD)) * 100 / SUM(SIGNON).

Log write efficiency The log write efficiency. Calculated as: (1 −SUM(WRITES_FORCE) / (SUM(WRITES_FORCE)+ SUM(WRITES_NOWAIT))) * 100.

Figure 26. Example of a DB2 System Statistics, Overview report

DB2 reports


Log read efficiency The log read efficiency. This is the percentage ofthe total number of log reads from the log outputbuffers. Calculated as:SUM(READS_OUTPUT_BFR) * 100 /(SUM(READS_OUTPUT_BFR) +SUM(READS_ACTIVE_LOG) +SUM(READS_ARCHIVE_LOG)).

Commit profile TSO/CAF vs CICS/IMSThe percentage of the commits originating fromTSO/CAF. It is 100 percent if neither IMS nor CICSis used with DB2. Calculated as:SUM(COMMITS_SINGLE) * 100 /(SUM(COMMITS_SINGLE) +SUM(COMMITS_PHASE2)).

DB2 reports


DB2 System CPU % by Address Space, Overview reportThis report shows the relative processor usage by an address space for one or moreDB2 systems. You can select DB2 system IDs using the DB2_system_list variable.For more information on using this report, refer to the System Performance FeatureGuide.


Report ID DB210


Source DB2_SYSTEM_T

Attributes DB2, Performance, CPU, Overview

Variables MVS_system_ID, DB2_system_list, From_date, To_date


DB2 system The DB2 system ID.

DBM1 The relative CPU (TCB + SRB) consumption for theDB2 database services (DBM1) address space.Calculated as: (TCB_TIME_DBM1 +SRB_TIME_DBM1) / (TCB + SRB).

MSTR The relative CPU (TCB + SRB) consumption for theDB2 system services (MSTR) address space.Calculated as: (TCB_TIME_MSTR +SRB_TIME_MSTR) / (TCB + SRB).

DIST The relative CPU (TCB + SRB) consumption for the

Figure 27. Example of a DB2 System CPU % by Address Space, Overview report

DB2 reports


DB2 distributed data facility (DIST) address space.Calculated as: (TCB_TIME_DIST +SRB_TIME_DIST) / (TCB + SRB).

IRLM The relative CPU (TCB + SRB) consumption for theIMS resource lock manager (IRLM) address space.Calculated as: (TCB_TIME_IRLM +SRB_TIME_IRLM) / (TCB + SRB).

DB2 reports


DB2 System Statistics, Trend reportThis report contains DB2 system services statistics for a specified time period. Itshows the main activities handled by the DB2 system services address space.


Report ID DB211


Source DB2_SYSTEM_T

Attributes DB2, Performance, System, Global, Weekly, Trend




Identifies The number of successful identify requests. This isthe number of successful connections to DB2 byTSO, IMS, CICS, CAF, or a DB2 utility.

Signons The number of successful sign-on requests by IMSor CICS.

Create threads The number of successful create thread requests.This is the number of threads created, excludingdatabase access threads.

X

XX X X X X X X

Figure 28. Example of a DB2 System Statistics, Trend report

DB2 reports


Term threads The number of terminate thread requests. This isthe number of times that threads were terminated.

Commits phase 2 The number of successful phase 2 end commitrequests. IMS and CICS use the two-phase commitprotocol.

Commits single The number of successful single-phase(synchronized) commit requests. TSO and CAFconnections use the single-phase commit protocol.

DB2 reports


DB2 General Measure by Profile, Overview reportThis report shows the elapsed time (class 1) compared with the logical I/O(GETPAGE). It attempts to find a simple measure that indicates the general statusof a DB2 system. This measure is valid only for transaction applications.


Report ID DB212


Source DB2_APPLICATION, DB2_TRANSACTION_D

Attributes DB2, Performance, General, Overview

Variables MVS_system_ID, DB2_system_ID, From_date, To_date, Profile_list


Profile The name of the group into which DB2 plans aregrouped, as defined in the DB2_APPLICATIONlookup table. These groups can be transaction,batch, query, and so on.

Logical I/O (GETPAGE) The number of GETPAGE requests.

Elapsed time The DB2 elapsed time (class 1), in milliseconds.

X

X

X

X

X

X

X

X

X

X

Figure 29. Example of a DB2 General Measure by Profile, Overview report

DB2 reports


DB2 Application Profiles, Overview reportThis report shows the response-time components for existing application profiles,as defined in the DB2_APPLICATION lookup table. The report requires thataccounting class 2 and class 3 traces be active during the report interval.


Report ID DB213


Source DB2_APPLICATION, DB2_APPLICATION_H

Attributes DB2, Performance, Application, Profile, Overview



Profile The name of the group into which DB2 plans aregrouped, as defined in the DB2_APPLICATIONlookup table. These groups can be transaction,batch, query, and so on.

Elapsed DB2 time The accumulated DB2 elapsed time as a percentageof the total elapsed time (class 1). Accounting traceclass 2 is required. Calculated as:SUM(ELAPSED_DB2_SEC) / SUM(ELAPSED_SEC)* 100.

Figure 30. Example of a DB2 Application Profiles, Overview report

DB2 reports


DB2 TCB time The accumulated DB2 TCB time as a percentage ofthe total elapsed time (class 1). Accounting traceclass 2 is required. Calculated as:SUM(B.TCB_DB2_SEC) / SUM(TCB_DB2_SEC) *100.

I/O wait time The accumulated elapsed time for all I/O activitiesas a percentage of the total elapsed time (class 1).Accounting trace class 3 is required. Calculated as:(SUM(B.IO_WAIT_SEC) /SUM(B.ELAPSED_DB2_SEC) +SUM(B.OTHER_READ_SEC) /SUM(B.ELAPSED_DB2_SEC) +SUM(B.OTHER_WRITE_SEC) /SUM(B.ELAPSED_DB2_SEC)) * 100.

Lock latch time The accumulated DB2 lock and latch time as apercentage of the total elapsed time (class 1).Accounting trace class 3 is required. Calculated as:SUM(B.LOCK_LATCH_SEC) /SUM(B.ELAPSED_DB2_SEC) * 100.

Service wait time The accumulated DB2 service time as a percentageof the total elapsed time (class 1). Accounting traceclass 3 is required. Calculated as:(SUM(SERVICE_TASK_SEC) /SUM(ELAPSED_DB2_SEC) +SUM(ARC_LOGWAIT_SEC) /SUM(ELAPSED_DB2_SEC) +SUM(ARC_LOGREAD_SEC) /SUM(ELAPSED_DB2_SEC)) * 100.

Other time The accumulated other DB2 time as a percentage ofthe total elapsed time (class 1). Accounting traceclass 3 is required. Calculated as:(SUM(ELAPSED_DB2_SEC) − SUM(TCB_DB2_SEC)− SUM(IO_WAIT_SEC) −SUM(LOCK_LATCH_SEC) −SUM(ARC_LOGREAD_SEC) −SUM(OTHER_READ_SEC) −SUM(OTHER_WRITE_SEC) −SUM(SERVICE_TASK_SEC) −SUM(ARC_LOGWAIT_SEC)) * 100 /SUM(ELAPSED_DB2_SEC).

DB2 reports


DB2 Application Profiles, Trend reportThis report shows the response-time components for a specific application as apercentage of the total elapsed time (class 1) over a specified time period. Thereport requires that accounting class 2 and class 3 traces be active during the reportinterval. For more information on using this report, refer to the System PerformanceFeature Guide.


Report ID DB214


Source DB2_APPLICATION, DB2_APPLICATION_W

Attributes DB2, Performance, Application, Profile, Trend

Variables MVS_system_ID, DB2_system_ID, From_date, To_date, Profile



Profile The name of the group into which DB2 plans aregrouped, as defined in the DB2_APPLICATIONlookup table. These groups can be transaction,batch, or query.

X XX

X

X

X XX

++ +

++

+

+

+

X

+

Figure 31. Example of a DB2 Application Profiles, Trend report

DB2 reports


Elapsed DB2 time The accumulated DB2 elapsed time as a percentageof the total elapsed time (class 1). Accounting traceclass 2 is required. Calculated as:SUM(ELAPSED_DB2_SEC) / SUM(ELAPSED_SEC)* 100.

DB2 TCB time The accumulated DB2 TCB time as a percentage ofthe total elapsed time (class 1). Accounting traceclass 2 is required. Calculated as:SUM(B.TCB_DB2_SEC) / SUM(TCB_DB2_SEC) *100.

DB2 SRB time The accumulated DB2 SRB time as a percentage ofthe total elapsed time (class 1). This time reflectsthe DB2 SRB time for the entire address space. So,it is valid only for agents running single users ortasks per address space (such as TSO users, batchjobs, or IMS MPPs). Accounting trace class 2 isrequired. Calculated as: SUM(B.SRB_DB2_SEC) /SUM(SRB_DB2_SEC) * 100.

I/O wait time The accumulated elapsed time for I/O activities asa percentage of the total elapsed time (class 1).Accounting trace class 3 is required. Calculated as:(SUM(IO_WAIT_SEC) / SUM(ELAPSED_DB2_SEC)+ SUM(OTHER_READ_SEC) /SUM(ELAPSED_DB2_SEC) +SUM(OTHER_WRITE_SEC) /SUM(ELAPSED_DB2_SEC)) * 100.

Lock latch time The accumulated DB2 lock and latch time as apercentage of the total elapsed time (class 1).Accounting trace class 3 is required. Calculated as:SUM(LOCK_LATCH_SEC) /SUM(ELAPSED_DB2_SEC) * 100.

Service wait time The accumulated DB2 service time as a percentageof the total elapsed time (class 1). Accounting traceclass 3 is required. Calculated as:(SUM(SERVICE_TASK_SEC) /SUM(ELAPSED_DB2_SEC) +SUM(ARC_LOGWAIT_SEC) /SUM(ELAPSED_DB2_SEC) +SUM(ARC_LOGREAD_SEC) /SUM(ELAPSED_DB2_SEC)) * 100.

Other time The accumulated other DB2 time as a percentage ofthe total elapsed time (class 1). Accounting traceclass 3 is required. Calculated as:(SUM(ELAPSED_DB2_SEC) − SUM(TCB_DB2_SEC)− SUM(IO_WAIT_SEC) −SUM(LOCK_LATCH_SEC) −SUM(OTHER_READ_SEC) −SUM(OTHER_WRITE_SEC) −SUM(SERVICE_TASK_SEC) −SUM(ARC_LOGWAIT_SEC −SUM(ARC_LOGREAD_SEC)) * 100 /SUM(ELAPSED_DB2_SEC).

DB2 reports


DB2 Buffer Pool Statistics, Detail reportThis report shows buffer pool activities per hour and individual buffer pool. Formore information on using this report, refer to the System Performance Feature Guide.


Report ID DB215


Source DB2_BUFFER_POOL_T

Attributes DB2, Performance, Buffer, Hourly, Detail



BP ID The buffer pool ID.


Get pages The number of GETPAGE requests.

Sync reads The number of synchronous read I/O operations.

Seq prefetch requests The number of sequential prefetch requests issued.For DB2 Version 2 Release 2, this includes listprefetch requests.

Seq prefetch pages read The number of pages read as a result of sequentialprefetch requests.

List prefetch requests The number of list prefetch requests issued. This isnot valid for DB2 Version 2 Release 2 (see Seqprefetch requests).

Buffer updates The number of times a buffer update occurred for

DB2 Buffer Pool Statistics, DetailSystem: ’MVS1’ DB2 ID: ’DB2A’


SeqSeq prefetch List

BP Get Sync prefetch pages prefetch Buffer Pages Async DatasetID Time pages reads requests read requests updates written writes opens--- ----- ----------- --------- --------- --------- --------- --------- --------- --------- -------0 08.00 502272 576 1422 8412 2 167936 8379 473 3309.00 2759424 879 34178 4330 19 509207 15459 955 2210.00 1194496 2386 41965 21670 1 172015 27516 994 011.00 501504 3322 6913 16254 80 173381 17154 769 912.00 2695424 1936 33497 3612 16 209910 4994 441 413.00 400896 409 17455 4320 52 35425 8694 324 014.00 2403072 758 17160 1007 5 68959 2631 320 4315.00 2571264 1588 8082 6592 23 148817 9707 785 13416.00 1404928 325 1768 1761 23 108096 4755 517 102

----------- --------- --------- --------- --------- --------- --------- --------- -------BP0 tot: 14433280 12179 162440 67958 221 1593746 99289 5578 347

=========== ========= ========= ========= ========= ========= ========= ========= =======Total: 14433280 12179 162440 67958 221 1593746 99289 5578 347


Figure 32. Example of a DB2 Buffer Pool Statistics, Detail report

DB2 reports


system pages. This is the number of updatesperformed against a page in the buffer pool.

Pages written The number of pages written for the buffer pool.This is the number of pages in the buffer poolwritten to DASD.

Async writes The number of asynchronous write I/Os for thebuffer pool.

Data set opens The number of data set OPENs performedsuccessfully for the buffer pool.

DB2 reports


DB2 Buffer Pool Statistics, Overview reportThis report shows buffer pool statistics key values. For more information on usingthis report, refer to the System Performance Feature Guide.


Report ID DB216



Attributes DB2, Performance, Buffer, Overview



Buffer pool ID The buffer pool ID(s).

Read efficiency The hit ratio within the buffer pool (for example,how often DB2 finds the required page in thebuffer pool). Calculated as: (SUM(GETPAGE) −SUM(SYNC_READ_IO)) * 100 / SUM(GETPAGE).

Prefetch availability The availability of the sequential prefetchmechanism. It should always be close to 100%.Calculated as: (1 − (SUM(SPTH_REACHED) +SUM(NO_READ_ENGINE)) /SUM(SEQ_PREFETCH_REQ)) * 100.

Figure 33. Example of a DB2 Buffer Pool Statistics, Overview report

DB2 reports


DASD write efficiency The DASD write efficiency. Calculated as: (1 −(SUM(SYNC_WRITE_IO) +SUM(ASYNC_WRITE_IO)) /SUM(PAGES_WRITTEN)) * 100.

Buffer update efficiency The buffer update efficiency. Calculated as: (1 −SUM(PAGES_WRITTEN) /SUM(BUFFER_UPDATES)) * 100.

Access profile READ vs WRITEThe value showing how much of the DB2 loadcomes from logical reading. A high figure indicateshigh logical reading activity. A low figure indicateshigh logical update activity. Calculated as:SUM(GETPAGE) * 100 / (SUM(GETPAGE) +SUM(PAGES_WRITTEN)).

DB2 reports


DB2 EDM Pool Statistics, Detail reportThis report shows daily EDM pool statistics per hour.


Report ID DB217



Attributes DB2, Performance, EDM, Pool, Detail




DBD requests The number of EDM requests for databasedescriptors.

DBD loads The number of EDM database descriptors loadsfrom DASD.

Cursor table section requests The number of EDM requests for cursor tablesections.

Cursor table section loads The number of EDM cursor table section loadsfrom DASD.

Package table section requestsThe number of EDM requests for package tablesections. This value is not valid for DB2 Version 2Release 2.

Package table section loads The number of EDM package table section loadsfrom DASD. This value is not valid for DB2Version 2 Release 2.

DB2 EDM Pool Statistics, DetailSystem: ’MVS1’ DB2 ID: ’DB2A’


Cursor Cursor Package Packagetable table table table EDM

DBD DBD section section section section poolTime requests loads requests loads requests loads full----- --------- ------- --------- ------- --------- ------- ------08.00 344 1 432 0 0 0 009.00 832 5 516 0 0 0 010.00 204 0 186 0 0 0 011.00 548 7 557 0 5 0 012.00 1094 7 285 0 9 0 013.00 575 1 200 0 4 0 014.00 1196 21 289 0 1 0 015.00 2400 55 750 0 0 0 016.00 448 26 162 0 1 0 0

========= ======= ========= ======= ========= ======= ======7641 123 3377 0 20 0 0


Figure 34. Example of a DB2 EDM Pool Statistics, Detail report

DB2 reports


EDM pool full The number of failures because the EDM pool wasfull.

DB2 reports


DB2 EDM Pool Statistics, Overview reportThis report shows buffer usage and hit ratios (for example, how often these objectsare already in the EDM pool, thus avoiding extra I/O) for database descriptors,cursor tables, and package tables. For more information on using this report, referto the System Performance Feature Guide.


Report ID DB218



Attributes DB2, Performance, EDM, Pool, Overview

Variables MVS_system_ID, DB2_system_list, From_date, To_date


DB2 system ID The DB2 system ID(s).

DBD read efficiency The hit ratio for database descriptors (DBD) withinthe EDM pool (for example, how often DB2 findsthe required DBD in the EDM pool). Calculated as:(SUM(EDM_REQ_DBD) −SUM(EDM_LOAD_DBD)) * 100 /SUM(EDM_REQ_DBD).

Figure 35. Example of a DB2 EDM Pool Statistics, Overview report

DB2 reports


Cursor table read efficiency The hit ratio for cursor table sections within theEDM pool (for example, how often DB2 finds therequired cursor table section in the EDM pool).Calculated as: (SUM(EDM_REQ_CT_SECT) −SUM(EDM_LOAD_CT_SECT)) * 100 /SUM(EDM_REQ_CT_SECT).

Package table read efficiency The hit ratio for package table sections within theEDM pool (for example, how often DB2 finds therequired package table section in the EDM pool).This value is not valid for DB2 Version 2 Release 2.Calculated as: (SUM(EDM_REQ_PT_SECT) −SUM(EDM_LOAD_PT_SECT)) * 100 /SUM(EDM_REQ_PT_SECT).

EDM pool utilization The utilization percentage of the EDM pool (forexample, what percentage of the EDM pool is usedfor database descriptors, cursor table sections, andpackage table sections). Calculated as:(SUM(EDM_POOL_SIZE) −SUM(EDM_PAGES_FREE)) * 100 /SUM(A.EDM_POOL_SIZE).

DB2 reports


DB2 Buffer Pool Exceptions reportThis report lists DB2 buffer pool exceptions. For more information on using thisreport, refer to the System Performance Feature Guide.


Report ID DB219



Attributes DB2, Performance, Exceptions



Date The date the exception occurred.

Time The time the exception occurred.

BP ID The buffer pool ID. This identifies the buffer poolfor which the exception occurred.

Defer write thrsh reached The number of times that the deferred writethreshold was reached for the buffer pool.

DB2 Buffer Pool ExceptionsSystem: ’MVS1’ DB2 ID: ’DB2A’

Date: ’2000-01-01’ to ’2000-03-09’

Deferwrite Sync Seq No

BP thrsh write prefetch write NoDate Time ID reached I/Os disabled engine workfile---------- -------- -- -------- -------- -------- -------- --------

2000-01-14 07.56.40 0 0 231 0 0 014.25.24 0 8 0 0 0 016.24.49 0 2 0 0 0 0

-------- -------- -------- -------- --------2000-01-14 total: 10 231 0 0 0

2000-01-19 10.28.21 0 157 0 0 0 011.59.53 0 53 0 0 0 013.57.33 0 59 0 0 0 014.28.55 0 3 0 0 0 015.27.05 0 18 0 0 0 015.57.03 0 24 0 0 0 0

-------- -------- -------- -------- --------2000-01-19 total: 314 0 0 0 0

2000-03-02 13.09.09 0 182 0 0 0 013.39.09 0 83 0 0 0 014.09.22 0 87 0 0 0 014.40.34 0 22 0 0 0 016.39.14 0 2 0 0 0 022.07.14 0 15 0 0 0 022.40.31 0 13 0 0 0 0

-------- -------- -------- -------- --------2000-03-02 total: 404 0 0 0 0

======== ======== ======== ======== ========Total: 728 231 0 0 0


Figure 36. Example of a DB2 Buffer Pool Exceptions report

DB2 reports


Sync write I/Os The number of immediate (synchronous) writeI/Os for the buffer pool.

Seq prefetch disabled The number of times that the sequential prefetchwas disabled because of unavailable buffers for thebuffer pool.

No write engine The number of times that no write engine wasavailable for the asynchronous write I/O for thebuffer pool.

No workfile The number of times that the work files requiredwere too many and could not be created because ofinsufficient buffer pool resources.

DB2 reports


DB2 System Parameters reportThis report shows the latest DB2 system start-up parameters in effect when a tracewas started. The DB2_system_list variable lets you choose which DB2 systemstart-up parameters you want to display. For more information about the start-upparameters, refer to the IBM DATABASE 2 Administration Guide.


Report ID DB220


Source DB2_SYS_PARAMETER

Attributes DB2, Performance, System, Parameters

Variables MVS_system_ID, DB2_system_list

DB2 System ParametersSystem: ’9X92’

DB2 System: V71K Date: 2000-10-28Time: 10.31.48

Resident trace table size : 16 (4K units)Checkpoint frequency : 5000 recordsBatch connects max : 20 jobsTSO connects max : 100 usersAllied threads max : 70Remote threads max : 40Statistic interval : 1440 minutesGlobal trace class : 00000000Statistics trace class : B8000000Accounting trace class : 80000000Audit trace class : 00000000Service unit limit : 0Monitor trace class : 00000000Monitor trace buffer size : 8192 bytesLog option : AArchive option : 0Log output buffer size : 800 kilobytesLog input buffer size : 0 kilobytesLog buffer threshold : 20 buffersEDM pool size max : 5120000 kilobytesDatasets open max : 2000Locks single max : 1000 page locksLocks all max : 10000 page locksBP0 size min : - buffersBP0 size max : - buffersBP1 size min : - buffersBP1 size max : - buffersBP2 size min : - buffersBP2 size max : - buffersBP32 size min : - buffersBP32 size max : - buffersKB for LOB per agent : 2048 KBMB for LOB per system : 2048 MBSyncval : NO minutesURlog written threshold : 0NPages threshold : 0Star join ratio : -1SNS Dclass file tspace :SMS Dclass idex tspace :EDM pool max datsp : 1073741824TCPIP keepalive ov : 0Pool thread timeout : 120

Tivoli Decision Support for OS/390: DB220

Figure 37. Example of a DB2 System Parameters report

DB2 reports



RES_TRACE_SIZE Size of the resident trace table, in multiples of 4kilobytes.

CHECKPOINT_FREQ Number of log records written betweencheckpoints.

BATCH_CONNECTS_MAX Maximum number of concurrent connections frombatch jobs and utilities.

TSO_CONNECTS_MAX Maximum number of concurrent connections fromTSO foreground sessions.

ALLIED_THREADS_MAX Maximum number of concurrent allied threads.This includes threads for IMS, CICS, TSO(foreground and batch), utilities, and databaseaccess threads.

REMOTE_THREADS_MAX Maximum number of concurrent remote threads(concurrent database access threads, which areallocated at a location on behalf of a remote SQLrequest).

STATISTIC_INTERVAL Time interval between statistics collections, inminutes.

GLOBAL_TRACE_CLASS Start trace option for global trace classes.

STAT_TRACE_CLASS SMF start trace option for statistics trace classes.

ACCTG_TRACE_CLASS SMF start trace option for accounting trace classes.

AUDIT_TRACE_CLASS Start trace option for audit trace classes.

SERVICE_UNIT_LIMIT Maximum number of MVS service units that canbe used for a thread.

MON_TRACE_CLASS Start trace option for monitor trace classes.

MONITOR_BFR_SIZE Monitor trace buffer size, in kilobytes.

LOG_OPTION Active log and BSDS initialization option that isused.

ARCHIVE_OPTION Indicates whether the archive log initializationoption is used.

LOG_OPUT_BFR_SIZE Log output buffer pool size for writing active logdata sets, in kilobytes.

LOG_INPUT_BFR_SIZE Log input buffer pool size, in kilobytes.

LOG_THRESHOLD Log output buffer threshold value. The number oflog output buffers to be filled before starting anasynchronous log output buffer write.

EDM_POOL_SIZE_MAX Maximum size of the EDM pool, in kilobytes.

DATASETS_OPEN_MAX Maximum number of concurrently open data setsbefore the deferred close process of DB2.

LOCKS_SINGLE_MAX Maximum number of page locks that can be heldconcurrently by a thread against a single tablespace.

LOCKS_ALL_MAX Maximum number of page locks that can be heldconcurrently by a thread against all table spaces inthe system.

BP0_SIZE_MIN Minimum size of buffer pool 0, in number of4-kilobyte buffers.

DB2 reports


BP0_SIZE_MAX Maximum size of buffer pool 0, in number of4-kilobyte buffers.







KB_LOB_AGENT Kilobytes for LOB values, per agent.

MB_LOB_SYSTEM Megabytes for LOB values, per system.

SYNCVAL SYNCVAL specification in minutes. Values are NO(if no synchronization is specified) or 0 - 59minutes.

URLOG_WRIT_THRES UR LOG RECORD WRITTEN THRESHOLD.

NPAGES_THRESH NPAGES threshold for Optimizer.

STAR_JOIN_RATIO Star join ratio.

SMS_DCLASS_FSTSP SMS DataClass - File Tablespace.

SMS_DCLASS_IXTSP SMS DataClass - Index Tablespace.

EDMPOOL_MAX_DATSP EDM POOL MAX DATA SPACE SIZE.

TCPIP_KEEPALIV_OV TCP/IP KEEPALIVE OVERRIDE.

POOL_THR_TIMEOUT POOL THREAD TIMEOUT VALUE.

DB2 reports


DB2 Packages Class 7,8 Times, Overview reportThis report shows information related to the DB2 Packages activity. The data isgrouped by rows with Package_Collection ID that is not blank.


Report ID DB221


Source DB2_PACKAGE_H

Attributes DB2, Package, Response, Application, Overview, System



Plan_Name The name of the plan.

Package_Collection ID The identifier of the package collection.

Package Name The name of the package.

Package_SQL Stmts The number of SQL issued by the package.

PKG_Elapsed_sec The total elapsed time in seconds.

PKG_TCB sec The total TCB time in seconds.

PKG_TOT_WAIT sec The total waiting times for all class 8 suspensionsin seconds.

DB2 Packages Class 7,8 Times, OverviewMVS System :’SY4B’ DB2 System :’DB2G’Date: ’2000-03-19’ to ’2000-03-19’

PKG PKGPlan Package Package Elapsed PKG TOTName Collection ID Package Name SQL Stmts sec TCB sec WAIT sec-------- ------------------ ------------------ ---------- ---------- ---------- ----------JEEPONE JEEPACK JEEPONE 9998 47 36 7

---------- ---------- ---------- --------* 9998 47 36 7

========== ========= ========== ==========9998 47 36 7


Figure 38. Example of a partial DB2 Package report

DB2 reports


DB2 DBRMs Class 7,8 Times, Overview reportThis report shows information related to the DB2 DBRMs activity. The data isgrouped by rows with blank Package_Collection ID.


Report ID DB222


Source DB2_PACKAGE_H

Attributes DB2, DBRM, Response, Application, Overview, System



Plan_Name The name of the plan.

Package Name The name of the package.

Package_SQL Stmts The number of SQL issued by the package.

PKG_Elapsed_sec The total elapsed time in seconds.

PKG_TCB sec The total TCB time in seconds.

PKG_TOT_WAIT sec The total waiting times for all class 8 suspensionsin seconds.

DB2 DBRMs Class 7,8 Times, OverviewMVS System :’SY4B’ DB2 System :’DB2G’Date: ’2000-03-19’ to ’2000-03-19’

PKG PKGPlan Package Elapsed PKG TOTName Package Name SQL Stmts sec TCB sec WAIT sec------- ---------------- --------- ---------- ---------- --------JEEPONE JEEPONE 9998 47 36 7

--------- ---------- ---------- --------* 9998 47 36 7

========= ========== ========== ========9998 47 36 7


Figure 39. Example of a DB2 Package report

DB2 reports


DB2 Group Buffer Pool Statistics, Detail reportThis report shows group buffer pool activities per hour and individual buffer poolrelated to data sharing.


Report ID DB223


Source DB2_BP_SHARING_T

Attributes DB2, DataSharing, Group, Buffer, Hourly, Detail



BP_ID Buffer pool ID.

SYN_READS(XI) Number of synchronous coupling facility readrequests caused by the page in the member bufferpool that is marked invalid. Data is returned fromthe group buffer pool. Calculated as(SYN_READ_XI_RETURN +SYN_READ_XI_RW_INT).

SYN_READS(NF) The number of synchronous coupling facility readrequests necessary because the requested page wasnot found in the buffer pool. Data was returnedfrom the coupling facility. Calculated as(SYN_READ_NF_RETURN +SYN_READ_NF_RW_INT).

ASYN_READS The number of coupling facility reads for prefetch,in which data was returned from the couplingfacility. Calculated as (ASYN_READ_RETURN +ASYN_READ_RW_INIT).

CHANGED_PAGES_SYNC_WRITTENThe number of changed pages synchronouslywritten from the member virtual pool to the groupbuffer pool.

DB2 Group Buffer Pol Statistics, DetailSystem: ’SY4B DB2 ID: ’DB2G’

Date: ’2000-03-19’ eriod(s): (’NIGHT ’)

CHANGED CLEAN UP CHANGED READ WRITEPAGES PAGES CASTOUT PAGES FAILED FAILED

ASYN SYNC ASYNC CLASS OUT ASYNC PAGES NO NOREADS WRITTEN WRITTEN THRESHOL HOLD WRITTN CASTOUT STORAGE STORAGE

--------- --------- --------- -------- ---- ------- --------- ---------- ----------0 0 0 0 0 0 0 0

--------- --------- --------- -------- ---- ------- --------- ---------- ----------0 0 0 0 0 0 0 0

========= ========= ========= ======== ==== ======= ========= ========== ==========0 0 0 0 0 0 0 0

Performance eporter: DB223

Figure 40. Example of a partial DB2 Buffer Pool report

DB2 reports


CLEAN_PAGES_ASYNC_WRITTENThe number of clean pages synchronously writtenfrom the member virtual pool to the group bufferpool.

CASTOUT_CLASS_THRESHOLDThe number of times group buffer pool castout wasinitiated due to the class castout threshold beingdetected.

GROUP_BP_CASTOUT_THRESHOLDThe number of times group buffer pool castout wasinitiated due to the group buffer pool castoutthreshold being detected.

CHANGED_PAGES_ASYNC_WRITTNThe number of changed pages asynchronouslywritten from the member virtual pool to the groupbuffer pool.

PAGES_CASTOUT The number of pages cast out from the groupbuffer pool to DASD.

READ_FAILED_NO_STORAGEThe number of coupling facility read requests thatcould not complete due to a lack of couplingfacility storage resources.

WRITE_FAILED_NO_STORAGEThe number of coupling facility write requests thatcould not complete due to a lack of cf storageresources.

REG._PAGE_LIST_REQUEST The number of requests to register a page list inthe coupling facility.

CLEAN_PAGES_READ_AFTER_RPLThe number of coupling facility reads to retrieve aclean page from the group buffer pool.

DB2 reports


DB2 Data Sharing Locking Statistics, Detail reportThis report shows statistics related to data sharing locking.


Report ID DB224


Source DB2_LOCK_SHARING_T

Attributes DB2, DataSharing, Locking, Hourly, Detail



LOCK_REQUESTS_(P-LOCKS)The number of lock requests for physical locks.

UNLOCK_REQUESTS_(P-LOCKS)The number of unlock requests for physical locks.

CHANGE_REQUESTS_(P-LOCKS)The number of change requests for physical locks.

SYNCH XES-LOCK_REQUESTSThe number of logical and physical lock requestspropagated to MVS XES synchronously.

SYNCH XES-UNLOCK_REQUESTSThe number of logical and physical unlock requestspropagated to MVS XES synchronously.

SYNCH XES-CHANGE_REQUESTSThe number of logical and physical changerequests propagated to MVS XES synchronously.

DB2 Data Sharing Locking Statistics, DetailSystem: ’SY4B’ DB2 ID: ’DB2G’

Date: ’2000-03-19’ Period(s): (’NIGHT ’)

SUSPENDUNLOCK CHANGE ASYNCH IRLM INCOMPATI NOTIFY

REQUESTS REQUESTS SYNCH XES SYNCH XES SYNCH XES XES GLOBAL RETAINED MESSAGES(P-LOCKS) (P-LOCKS) REQUESTS REQUESTS REQUESTS RESOURCES CONT LOCK SENT--------- --------- --------- --------- --------- --------- ------- --------- ----------

1 1 7 8 1 0 0 0 0========= ========= ========= ========= ========= ========= ======= ========= ==========

1 1 7 8 1 0 0 0 0


Figure 41. Example of a partial DB2 Data Sharing Locking report

DB2 reports


ASYNCH_XES_RESOURCES The number of resources propagated by IRLM toMVS XES asynchronously. This number indicatesthe number of lock-related requests that werepropagated to XES asynchronously.

SUSPENDS_IRLM_GLOBAL_CONTThe total number of suspensions caused by IRLMglobal resource contention, MVS XES globalresource contention, and false contention.

INCOMPATIBLE_RETAINED_LOCThe number of global lock or change requestsdenied due to an incompatible retained lock.

NOTIFY_MESSAGES_SENT The number of notify messages sent

NOTIFY_MESSAGES_REC The number of notify messages received

PAGE_NEGOTIATION The number of times this DB2 was driven tonegotiate a page P-lock to negotiate a page P-lockcontention.

DB2 reports


DB2 Group Buffer Pool Accounting, Overview reportThis report shows group buffer pool accounting per hour and individual bufferpool related to data sharing.


Report ID DB225


Source DB2_US_TRAN_SHAR_H

Attributes DB2, DataSharing, Accounting Group, Buffer, Pool, Overview

Variables MVS_system_ID, DB2_system_ID, To_date, From_date


TIME The hour of the data.

DB2_SYSTEM_ID The DB2 system name.

GROUP_BPOOL_ID The ID of the group buffer pool.

READ(XI)_DATA_RETUR The number of sychronous SES reads necessarydue to buffer cross invalidation (XI) in which datawas returned.

READ(XI)_DATA_NORET The number of SES reads necessary due to bufferXI in which data was not returned from SES anddirectory entry assignment was not suppressed.

READ(NF)_DATA_RETUR The number of SES reads necessary due to therequested page not being found in the buffer poolin which data was returned from SES.

DB2 Group Buffer Pool Accounting, OverviewSystem: ’3090’ DB2 ID: ’V61A’

DATE: ’1999-07-22’ TO ’1999-07-22’

DB2 GROUP READ(XI) READ(XI) READ(NF) READ(NF) SECONDARY CLEAN UNREGSYSTEM BPOOL DATA DATA DATA DATA READ(GBP) CHANGED CHANGED PAGES PAGES

Time ID ID RETUR NORET RETUR NORET PREFETCH PAGES PAGES WRITTEN REQS----- ------ ----- -------- -------- -------- -------- --------- ------- --------- ------- -----14.00 V61A - - - - - - - - - -13.00 V61A - - - - - - - - - -13.00 V61A - - - - - - - - - -11.00 V61A 11 19 5 7 11 17 124 0 0 311.00 V61A 11 3 0 6 39 1 14 0 35 3110.00 V61A 120 0 0 0 17 0 10 0 18 7510.00 V61A 11 0 1 0 23 0 19 0 21 2710.00 V61A 0 0 0 0 1 0 18 0 0 010.00 V61A 0 13 4 1 12 11 124 0 0 2

======== ======== ======== ======== ========= ======= ========= ======= =====Total: 35 10 14 103 29 309 0 74 138


Figure 42. Example of a DB2 Group Buffer Pool Accounting, Overview report

DB2 reports


READ(NF)_DATA_NORET The number of SES-reads necessary due to therequested page not being found in the buffer poolin which data was not returned and directory entryassignment was not suppressed.

READ(GBP)_PREFETCH The number of pages read from GBP due toprefetch under the control of the agent.

CHANGED_PAGES The number of changed pages written to the groupbuffer pool

SECONDARY_CHANGED_PAGESThe number of changed pages written to thesecondary group buffer pool, for duplexing.

CLEAN_PAGES_WRITTEN The number of clean pages written to the groupbuffer pool

UNREG_PAGES_REQS The number of unregister page requests.

DB2 reports


DB2 Data Sharing Locking Accounting, Overview reportThis report shows accounting related to data sharing locking.


Report ID DB226


Source DB2_US_TRAN_SHAR_H

Attributes DB2, DataSharing, Accounting Group, Buffer, Pool, Overview

Variables MVS_system_ID, DB2_system_ID, To_date, From_date


DB2_SYSTEM_ID The DB2 system name.

LOCK_REQUEST The number of lock requests for physical locks.

UNLOCK_REQUEST The number of unlock requests for physical locks

CHANGE_REQUEST The number of change requests for physical locks.

LOCK_XES The number of lock requests propagated to MVSXES.

UNLOCK_XES The number of unlock requests propagated to MVSXES.

CHANGE_XES The number of change requests propagated to MVSXES.

SUSP_IRLM The number of suspensions due to IRLM globalresource contention (IRLM lock states were inconflict).

SUSP_XES The number of suspensions due to MVS XES globalresource contention (MVS XES lock states were inconflict whereas IRLM lock states were not).

SUSP_FALSE The number of suspensions due to false contention.This happens when different resource names hashto the same entry in the coupling facility lock table.

INCOMP._LOCK The number of global lock or change requestsdenied due to an incompatible retained lock.

DB2 Data Sharing Locking Accounting, OverviewSystem: ’SY4B’ DB2 ID: ’DB2G’

DATE: ’2000-03-19’ TO ’2000-03-19’

LOCK UNLOCK CHANGE LOCK UNLOCK CHANGE SUSP SUSP SUSPREQUEST REQUEST REQUEST XES XES XES IRLM XES FALSE

--------- --------- --------- --------- --------- --------- ------- --------- ----------53 0 24 159 77 24 0 0 0

========= ========= ========= ========= ========= ======= ========= ==========Total: 0 24 159 77 24 0 0 0


Figure 43. Example of a partial DB2 Data Sharing Locking Accounting report

DB2 reports


NOTIFY_SENT The number of notify messages sent.

DB2 reports


DB2 User Defined Functions, Detail reportThis report shows User Defined Functions information on an hourly basis, per DB2plan.


Report ID DB227


Source DB2_US_TRAN_H

Attributes DB2, UDF, Hourly, Detail

Variables Date, MVS_system_ID, DB2_system_ID, DB2_plan


DB2_plan The DB2 plan name.

Date The date of measurement.

Time The time of measurement.

UDF_executed_(total) The total number of user defined functions thatwere executed.

UDF_abended_(total) The total number of times that a user definedfunction abended.

UDF_timed_out_(total) The total number of times that a user definedfunction timed out while waiting to be scheduled.

UDF_rejected_(total) The total number of times that a user definedfunction was rejected.

UDF_executed_(avg) The average number of user defined functions thatwere executed.

UDF_abended_(avg) The average number of times that a user definedfunction abended.

UDF_timed_out_(avg) The average number of times that a user definedfunction timed out while waiting to be scheduled.

UDF_rejected_(avg) The average number of times that a user definedfunction was rejected.

DB2 User Defined Functions, DetailSystem: ’3090’ DB2 ID: ’V61A’

Date: ’2000-07-22’

UDF UDFUDF UDF UDF TCB UDF elapsed

UDF UDF timed UDF UDF UDF timed UDF TCB sec elapsed secDB2 executed abended out rejected executed abended out rejected sec for sec forplan Time (total) (total) (total) (total) (avg) (avg) (avg) (avg) total SQL total SQL-------- -------- -------- ------- ------- -------- -------- ------- ----- -------- ----- ---- ------- -------DSNESPCS 10.00.00 12 12 0 0 12 12 0 0 4.52 0.00 44.80 0.00DSNESPCS 11.00.00 2 2 0 0 2 2 0 0 0.18 0.00 37.90 0.00DSNESPCS 13.00.00 0 0 0 0 0 0 0 0 0.00 0.00 0.00 0.00DSNESPCS 14.00.00 6 6 0 0 6 6 0 0 0.33 0.00 51.19 0.00

======== ======= ======= ======== ===== ==== ======= =======Total: 20 20 0 0 5.03 0.00 133.90 0.00


Figure 44. Example of a DB2 User Defined Functions, Detail report

DB2 reports


UDF_TCB_sec_total The accumulated TCB time spent in DB2 by userdefined functions.

UDF_TCB_sec_for_SQL The accumulated TCB time spent in DB2 by userdefined functions for processing SQL statements.

UDF_elapsed_sec_total The total elapsed time spent by user definedfunctions.

UDF_elapsed_sec_for_SQL The total elapsed time spent by user definedfunctions for processing SQL statements.

DB2 reports


DB2 User Defined Functions, Overview reportThis report shows User Defined Functions information grouped by DB2 plan.


Report ID DB228



Attributes DB2, UDF, Overview

Variables From_date, To_date, MVS_system_ID, DB2_system_ID



UDF_executed_(total) The total number of user defined functions thatwere executed.

UDF_abended_(total) The total number of times that a user definedfunction abended.

UDF_timed_out_(total) The total number of times that a user definedfunction timed out while waiting to be scheduled.

UDF_rejected_(total) The total number of times that a user definedfunction was rejected.

UDF_executed_(avg) The average number of user defined functions thatwere executed.

UDF_abended_(avg) The average number of times that a user definedfunction abended.

UDF_timed_out_(avg) The average number of times that a user definedfunction timed out while waiting to be scheduled.

UDF_rejected_(avg) The average number of times that a user definedfunction was rejected.

UDF_TCB_sec_total The accumulated TCB time spent in DB2 by userdefined functions.

UDF_TCB_sec_for_SQL The accumulated TCB time spent in DB2 by userdefined functions for processing SQL statements.

DB2 User Defined Functions, OverviewSystem: ’3090’ DB2 ID: ’V61A’

From Date: ’2000-07-22’ To Date: ’2000-07-22’

UDFUDF TCB UDF UDF

UDF UDF UDF UDF UDF UDF UDF UDF TCB sec elapsed elapsedDB2 executed abended timed out rejected executed abended timed out rejected sec for sec secplan (total) (total) (total) (total) (avg) (avg) (avg) (avg) total SQL total for SQL-------- -------- ------- --------- -------- -------- -------- --------- -------- ----- ---- ------- -------DSNESPCS 20 20 0 0 5 5 0 0 5.03 0.00 133.90 0.00DSNTEP61 0 0 0 0 0 0 0 0 0.00 0.00 0.00 0.00DSNUTIL - - - - - - - - 0.00 0.00 0.00 0.00DS36A611 34 34 0 0 34 34 0 0 4.63 0.00 103.90 0.00

======== ======= ========= ======== ==== ==== ======= =======Total: 54 54 0 0 9.66 0.00 237.80 0.00


Figure 45. Example of a DB2 User Defined Functions, Overview report

DB2 reports


UDF_elapsed_sec_total The total elapsed time spent by user definedfunctions.

UDF_elapsed_sec_for_SQL The total elapsed time spent by user definedfunctions for processing SQL statements.

DB2 reports


DB2 Triggers, Detail reportThis report shows triggers information on an hourly basis, per DB2 plan.


Report ID DB229



Attributes DB2, Trigger, Hourly, Detail




Dat The date of measurement.


Stmt_trigger_activated_(total) The total number of times that a statement triggerwas activated.

Row_trigger_activated_(total) The total number of times that a row trigger wasactivated.

Trigger_errors_(total) The total number of times that an SQL erroroccurred during the execution of a trigger action.

Stmt_trigger_activated_(avg) The average number of times that a statementtrigger was activated.

Row_trigger_activated_(avg) The average number of times that a row triggerwas activated.

Trigger_errors_(avg) The average number of times that an SQL erroroccurred during the execution of a trigger action.

TCB_sec_not_under_enclave The accumulated TCB time spent in executingtriggers not under an enclave.

Elapsed_sec_not_under_enclaveThe elapsed TCB time spent in executing triggersnot under an enclave.

DB2 Triggers, DetailSystem: ’3090’ DB2 ID: ’V61A’

DATE: ’2000-07-22’

Stmt Row Stmt Row Elapsed Elapsedtrigger trigger Trigger trigger trigger Trigger TCB sec sec TCB sec sec

DB2 activated activated errors activated activated errors not under not under under underplan Time (total) (total) (total) (avg) (avg) (avg) enclave enclave enclave enclave-------- -------- --------- --------- ------- --------- --------- ------- --------- --------- ------- -------DSNESPCS 10.00.00 0 31 0 0 31 0 0.18 0.24 0.00 0.00DSNESPCS 11.00.00 0 6 0 0 6 0 0.15 0.16 0.00 0.00DSNESPCS 13.00.00 0 0 0 0 0 0 0.00 0.00 0.00 0.00DSNESPCS 14.00.00 0 18 0 0 18 0 0.81 0.90 0.00 0.00

========= ========= ======= ========= ======= =======Total: 0 55 0 1.30 0.00 0.00


Figure 46. Example of a DB2 Triggers, Detail report

DB2 reports


TCB_sec_under_enclave The accumulated TCB time spent in executingtriggers under an enclave.

Elapsed_sec_under_enclave The elapsed TCB time spent in executing triggersunder an enclave.

DB2 reports


DB2 Triggers, Overview reportThis report shows triggers information grouped by DB2 plan.


Report ID DB230



Attributes DB2, Trigger, Overview




Stmt_trigger_activated_(total) The total number of times that a statement triggerwas activated.

Row_trigger_activated_(total) The total number of times that a row trigger wasactivated.

Trigger_errors_(total) The total number of times that an SQL erroroccurred during the execution of a trigger action.

Stmt_trigger_activated_(avg) The average number of times that a statementtrigger was activated.

Row_trigger_activated_(avg) The average number of times that a row triggerwas activated.

Trigger_errors_(avg) The average number of times that an SQL erroroccurred during the execution of a trigger action.

TCB_sec_not_under_enclave The accumulated TCB time spent in executingtriggers not under an enclave.

Elapsed_sec_not_under_enclaveThe elapsed TCB time spent in executing triggersnot under an enclave.

TCB_sec_under_enclave The accumulated TCB time spent in executingtriggers under an enclave.

DB2 Triggers, OverviewSystem: ’3090’ DB2 ID: ’V61A’

From Date: ’2000-07-22’ To Date: ’2000-07-22’

Stmt Row Stmt Row Elapsed Elapsedtrigger trigger Trigger trigger trigger Trigger TCB sec sec TCB sec sec

DB2 activated activated errors activated activated errors not under not under under underplan (total) (total) (total) (avg) (avg) (avg) enclave enclave enclave enclave-------- --------- --------- --------- --------- --------- ------- --------- --------- ------- -------DSNESPCS 0 55 0 0 13 0 1.14 1.30 0.00 0.00DSNTEP61 0 0 0 0 0 0 0.00 0.00 0.00 0.00DSNUTIL - - - - - - 0.00 0.00 0.00 0.00DS36A611 0 19 0 0 19 0 0.08 4.81 0.00 0.00

========= ========= ========= ========= ========= ======= =======Total: 0 74 0 1.22 6.11 0.00 0.00


Figure 47. Example of a DB2 Triggers, Overview report

DB2 reports


Elapsed_sec_under_enclave The elapsed TCB time spent in executing triggersunder an enclave.

DB2 reports


DB2 Row ID, Detail reportThis report shows information on the direct row access method, on an hourlybasis, per DB2 plan.


Report ID DB231



Attributes DB2, RowID, Direct, Access, Hourly, Detail




Date The date of measurement.


Row_ID_dir_access_successful_(total)The total number of times that direct row accesswas successful.

Row_ID_index_used_instead_(total)The total number of times that DB2 tried to usedirect row access to find a record but used anindex instead.

Row_ID_ts_used_instead_(total)The total number of times that DB2 tried to usedirect row access to find a record but used a tablespace scan instead.

Row_ID_dir_access_successful_(avg)The average number of times that direct row accesswas successful.

DB2 Row ID, DetailSystem: ’3090’ DB2 ID: ’V61A’

DATE: ’2000-07-22’

Row ID Row ID Row ID Row ID Row ID Row IDdir access index used ts used dir access index used ts used

DB2 successful instead instead successful instead insteadPlan Time (total) (total) (total) (avg) (avg) (avg)-------- ---------- ---------- ---------- ---------- ---------- ---------- ----------DSNESPCS 10.00.00 14 0 0 14 0 0DSNESPCS 11.00.00 3 0 0 3 0 0DSNESPCS 13.00.00 0 0 0 0 0 0DSNESPCS 14.00.00 9 0 0 9 0 0

========== ========== ==========Total: 26 0 0


Figure 48. Example of a DB2 Row ID, Detail report

DB2 reports


Row_ID_index_used_instead_(avg)The average number of times that DB2 tried to usedirect row access to find a record but used anindex instead.

Row_ID_ts_used_instead_(avg)The average number of times that DB2 tried to usedirect row access to find a record but used a tablespace scan instead.

DB2 reports


DB2 Row ID, Overview reportThis report shows information on the direct row access method, grouped by DB2plan.


Report ID DB232



Attributes DB2, RowID, Direct, Access, Overview




Row_ID_dir_access_successful_(total)The total number of times that direct row accesswas successful.

Row_ID_index_used_instead_(total)The total number of times that DB2 tried to usedirect row access to find a record but used anindex instead.

Row_ID_ts_used_instead_(total)The total number of times that DB2 tried to usedirect row access to find a record but used atablespace scan instead.

Row_ID_dir_access_successful_(avg)The average number of times that direct row accesswas successful.

Row_ID_index_used_instead_(avg)The average number of times that DB2 tried to usedirect row access to find a record but used anindex instead.

DB2 Row ID, OverviewSystem: ’3090’ DB2 ID: ’V61A’

From Date: ’2000-07-22’ To Date: ’2000-07-22’

Row ID Row ID Row ID Row ID Row ID Row IDdir access index used ts used dir access index used ts used

DB2 successful instead instead successful instead insteadplan (total) (total) (total) (avg) (avg) (avg)-------- ---------- ---------- ---------- ---------- ---------- ----------

- - - - - -DSNESPCS 26 0 0 6 0 0DSNTEP61 0 0 0 0 0 0DSNUTIL - - - - - -DS36A611 6 0 0 6 0 0

========== ========== ==========Total: 32 0 0


Figure 49. Example of a DB2 Row ID, Overview report

DB2 reports


Row_ID_ts_used_instead_(avg)The average number of times that DB2 tried to usedirect row access to find a record but used a tablespace scan instead.

DB2 reports


DB2 Secondary Group Buffer Pool Statistics, Detail reportThis report shows secondary group buffer pool (GBP) activities per hour andindividual buffer pool.


Report ID DB233


Source DB2_BP_SHARING_T

Attributes DB2, DataSharing, Secondary, GBP, Group, Buffer, Pool, Statistics,Hourly, Detail

Variables Date, MVS_system_ID, DB2_system_ID, Period_name_list

DB2 Secondary Group Buffer Pool Statistics, DetailSystem: ’3090’ DB2 ID: ’V61A’

Date: ’2000-07-22’ Period(s): (’PRIME ’)

ReadWrite to Completion Delete Delete castout

Write to secondary checks name list name statsBP secondary GBP writes to secondary secondary secondaryID Time GBP failed sec GBP GBP GBP GBP

--- ----- ---------- ---------- ---------- ---------- ---------- ----------0 10.00 5 0 3 0 0 111.00 0 0 0 0 0 012.00 6 1 0 1 1 013.00 0 0 0 0 0 014.00 4 0 2 1 1 1

---------- ---------- ---------- ---------- ---------- ----------* 14 1 5 2 2 2

1 10.00 0 0 0 0 0 011.00 0 0 0 0 0 012.00 0 0 0 0 0 013.00 0 0 0 0 0 014.00 0 0 0 0 0 0

---------- ---------- ---------- ---------- ---------- ----------* 0 0 0 0 0 0

11 10.00 4 1 0 1 0 011.00 0 0 3 0 1 012.00 3 1 3 0 0 013.00 0 0 0 0 1 014.00 0 0 0 1 0 0

---------- ---------- ---------- ---------- ---------- ----------* 7 2 6 2 2 0========== ========== ========== ========== ========== ==========

Total: 21 3 11 4 4 2


Figure 50. Example of a DB2 Secondary Group Buffer Pool Statistics, Detail report

DB2 reports



BP_ID The buffer pool ID.


Write_to_secondary_GBP The number of changed pages written to thesecondary GBP for duplexing.

Write_to_secondary_GBP_failedThe number of writes of changed pages to thesecondary GBP that failed due to a lack of storage.

Completion_checks_write_to_ sec_ GBPThe number of completion checks for writes to thesecondary GBP suspended because the write hadnot yet completed.

Delete_name_list_secondary_GBPIXLCACHE delete-name-list requests to thesecondary GBP.

Delete_name_secondary_GBP IXLCACHE delete-name requests to the secondaryGBP.

Read_castout_stats_secondary_GBPIXLCACHE read-castout-stats requests to thesecondary GBP.

DB2 reports


DB2 Application Wait Times, Detail reportThis report shows application wait times by application, as defined in theDB2_APPLICATION lookup table. Starting from DB2 Version 6 the wait times arereported more clearly, helping to determine which activities are contributing to thetotal wait time.


Report ID DB234



Attributes DB2, Application, Profile, Wait, Times, Detail



Application_name The application name, as defined in theDB2_APPLICATION lookup table.

Profile The type of application (transaction, query, batchand so on) as defined in the DB2_APPLICATIONlookup table.

IO_wait_seconds_for_log_write_(avg)The average wait time for log write I/O during thereport interval, in seconds. Calculated as:SUM(IO_WAIT_LOGWRT_SEC)/(SUM(COMMIT_COUNT) + SUM(ABORT_COUNT)).

IO_wait_seconds_for_database_(avg)The average wait time for database I/O during thereport interval, in seconds. Calculated as:SUM(IO_WAIT_DB_SEC)/(SUM(COMMIT_COUNT) + SUM(ABORT_COUNT)).

DB2 Application Wait Times, DetailSystem: ’3090’ DB2 ID: ’V61A’

From Date: ’2000-07-22’ To Date: ’2000-07-22’

IO wait IO wait Service Serviceseconds seconds wait for Service Service wait for Service Servicefor log for IO wait commit/ wait for wait for Dataspace wait for wait

Application write database seconds abort open/close SYSLGRNX Manager other seconds Commit Abortname Profile (avg) (avg) (avg) (avg) ds (avg) (avg) (avg) (avg) (avg) count count----------- ------- ------- -------- ------- -------- ---------- -------- --------- -------- ------- ------ -----OTHER OTHER 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 153 0SPUFI CS QUERY 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 40 14

====== =====Total: 193 14


Figure 51. Example of a DB2 Application Wait Times, Detail report

DB2 reports


IO_wait_seconds_(avg) The average wait time for I/O during the reportinterval, in seconds. Calculated as:SUM(IO_WAIT_SEC)/(SUM(COMMIT_ COUNT) +SUM(ABORT_COUNT)).

Service_wait_for_commit/abort_(avg)The average wait time for commit phase 2 or abortduring the report interval, in seconds. Calculatedas: SUM(SERV_TASK_CA_SEC)/(SUM(COMMIT_COUNT) + SUM(ABORT_COUNT)).

Sservice_wait_for_open/close_ds_(avg)The average wait time for open or close servicetask (including HSM recall) during the reportinterval, in seconds. Calculated as:SUM(SERV_TASK_OC_SEC)/(SUM(COMMIT_COUNT) + SUM(ABORT_COUNT)).

Service_wait_for_SYSLGRNX_(avg)The average wait time for SYSLGRNX recordingservice task during the report interval, in seconds.Calculated as:SUM(SERV_TASK_SYS_SEC)/(SUM(COMMIT_COUNT) + SUM(ABORT_COUNT))sdAverage.

Service_wait_for_Dataspace_Manager_(avg)The average wait time for data set extend, delete ordefine service task during the report interval, inseconds. Calculated as:SUM(SERV_TASK_DS_SEC)/(SUM(COMMIT_COUNT) + SUM(ABORT_COUNT)).

Service_wait_for_other_(avg) The average wait time for other service tasksduring the report interval, in seconds. Calculatedas: SUM(SERV_TASK_OTH_SEC)/(SUM(COMMIT_COUNT) + SUM(ABORT_COUNT)).

Service_wait_seconds_ (avg) The average wait time for service task during thereport interval, in seconds. Calculated as:SUM(SERVICE_TASK_SEC)/(SUM(COMMIT_COUNT) + SUM(ABORT_COUNT)).

Commit_count The number of commits that occurred during thereport interval.

Abort_count The number of aborts that occurred during thereport interval.

DB2 reports


DB2 Application Wait Times, Overview reportThis report shows application wait times by application, as defined in theDB2_APPLICATION lookup table. Starting from DB2 Version 6 the wait times arereported more clearly, helping to determine which activities are contributing to thetotal wait time. You can select applications by name using the Appl_name_listvariable. If you do not select any application names, the report shows the mostfrequent (highest commit-count) applications. Use the Maxrows variable to limitthe number of elements shown in the chart.


Report ID DB235



Attributes DB2, Application, Wait, Times, Overview

Variables From_date, To_date, MVS_system_ID, DB2_system_ID,Appl_name_list, Maxrows


Application_name The application name, as defined in theDB2_APPLICATION lookup table.

IO_wait_seconds_(avg) The average wait time for I/O during the reportinterval, in seconds. Calculated as:SUM(IO_WAIT_SEC)/(SUM(COMMIT_COUNT) +SUM(ABORT_COUNT)).

Service_wait_seconds_ (avg) The average wait time for service task during thereport interval, in seconds. Calculated as:SUM(SERVICE_TASK_SEC)/(SUM(COMMIT_COUNT) + SUM(ABORT_COUNT)).

Commit_count The number of commits that occurred during thereport interval.

Abort_count The number of aborts that occurred during thereport interval.

DB2 Application Wait Times, OverviewSystem: ’3090’ DB2 ID: ’V61A’

From Date: ’2000-07-22’ To Date: ’2000-07-22’

ServiceIO wait wait

Application seconds seconds Commit AbortName (avg) (avg) count count------------------ ------------ ------------ ---------- ----------OTHER 0.00 0.00 153 0SPUFI CS 0.00 0.00 40 14


Figure 52. Example of a DB2 Application Wait Times, Overview report

DB2 reports


|||||||

DB2 Application Wait Times, Trend reportThis report shows application wait times by application, as defined in theDB2_APPLICATION lookup table, over a period of time. Starting from DB2Version 6 the wait times are reported more clearly, helping to determine whichactivities are contributing to the total wait time. You can select applications byname using the Appl_name_list variable. If you do not select any applicationnames, the report shows all applications.


Report ID DB236


Source DB2_APPLICATION_W

Attributes DB2, Application, Wait, Times, Trend

Variables From_date, To_date, MVS_system_ID, DB2_system_ID,Appl_name_list


Week_start_date The first day of the week of the measurement.

Elapsed_wait_seconds The elapsed wait time for I/O during the reportinterval, in seconds. Calculated as:SUM(IO_WAIT_SEC)/(SUM(COMMIT_COUNT) +SUM(ABORT_COUNT)). This information isavailable as a breakdown by Application name andas a total for all applications.

DB2 Application Wait Times, TrendSystem: ’3090’ DB2 ID: ’V61A’

Date: ’2000-07-19’ to ’2000-07-19’

<---------Application name----------><-----OTHER------> <----SPUFI CS----> <-----TOTAL------>

Elapsed Elapsed ElapsedWeek start wait wait waitdate seconds seconds seconds---------- ---------- ---------- ----------2000-07-19 21.00 35.30 56.30

========== ========== ==========21.00 35.30 56.30


Figure 53. Example of a DB2 Application Wait Times, Trend report

DB2 reports


Part 4. DFSMS component

Chapter 9. Customization. . . . . . . . . 185Make input data available . . . . . . . . . 185Modify DRLJCOLL . . . . . . . . . . . 186Update lookup tables. . . . . . . . . . . 186

Update DFSMS_DS_OWNER . . . . . . . 186Update DFSMS_LAST_RUN . . . . . . . 187Update DFSMS_MIGRATE_DAYS . . . . . 187Update DFSMS_PLANNED_CAP. . . . . . 187Update DFSMS_THRESHOLD. . . . . . . 188Update DFSMS_VOL_STORGRP . . . . . . 188

Chapter 10. Data flow . . . . . . . . . . 189Lookup tables . . . . . . . . . . . . . 191

Chapter 11. Log and record definitions . . . . 193Record procedure . . . . . . . . . . . . 194

Chapter 12. Data tables and lookup tables. . . 195Data tables . . . . . . . . . . . . . . 195

DFSMS_ACTIVITY_D, _M . . . . . . . . 195DFSMS_BACKUP_D, _M . . . . . . . . 197DFSMS_DASD_CAP_D . . . . . . . . . 199DFSMS_DASD_CAP_M . . . . . . . . . 200DFSMS_DATASET_D. . . . . . . . . . 201DFSMS_DATASET_M . . . . . . . . . 203DFSMS_DCOLLECT_T . . . . . . . . . 205DFSMS_MIGRATION_D, _M . . . . . . . 206DFSMS_TAPE_CAP_D, _M . . . . . . . . 208DFSMS_VOLUME_D . . . . . . . . . . 209DFSMS_VOLUME_M. . . . . . . . . . 210

Lookup tables . . . . . . . . . . . . . 212DFSMS_DS_OWNER . . . . . . . . . . 212DFSMS_LAST_RUN . . . . . . . . . . 213DFSMS_MIGRATE_DAYS . . . . . . . . 214DFSMS_PLANNED_CAP . . . . . . . . 215DFSMS_THRESHOLD . . . . . . . . . 216DFSMS_VOL_STORGRP. . . . . . . . . 217

Chapter 13. Reports . . . . . . . . . . 219DFSMS report descriptions . . . . . . . . . 219

DFSMS Active/Migrat/Backup Storage,Daily/Monthly Trend report . . . . . . . 220DFSMS Allocated/Used/Unused Storage, DailyTrend report . . . . . . . . . . . . . 222DFSMS Backup Storage on DASD/Tape, DailyTrend report . . . . . . . . . . . . . 224DFSMS DASD Exceptions report . . . . . . 226DFSMS Data Not Migrated but Eligible, DailyTrend report . . . . . . . . . . . . . 227DFSMS Free Space by Storage Group,Daily/Monthly Trend report . . . . . . . 229DFSMS Migration and Backup Activities, DailyTrend report . . . . . . . . . . . . . 230DFSMS Projects Allocating Most DASD report 232

DFSMS Projects Using Most DASD for Backupreport . . . . . . . . . . . . . . . 233DFSMS Projects Using Most DASD forMigration report . . . . . . . . . . . 234DFSMS Projects Wasting Most DASD report . . 235DFSMS Storage Groups Meeting TargetThreshold report . . . . . . . . . . . 237DFSMS Storage Used for Migration onML1/ML2 report . . . . . . . . . . . 239DFSMS Tape for Migration/Backup/Dump,Daily Trend report. . . . . . . . . . . 241DFSMS Target/Trigger Migration Values report 243DFSMS Total DASD Usage, Daily/MonthlyTrend report . . . . . . . . . . . . . 245DFSMS Total Storage Used by ManagementClass report . . . . . . . . . . . . . 247DFSMS Total Storage Used by Project report . . 249DFSMS Total Storage Used by Storage Classreport . . . . . . . . . . . . . . . 251DFSMS Total Storage Used by Storage Groupreport . . . . . . . . . . . . . . . 252DFSMS Volumes Not Meeting Target Thresholdreport . . . . . . . . . . . . . . . 253DFSMS VTOC Information by Volume report 255

183


Before you can use the DFSMS component to collect data and create reports, youmust customize and test the installation. This chapter describes the steps you mustperform to customize the DFSMS component:1. Make input data available.2. Modify DRLJCOLL.3. Update lookup tables.

Make input data availableDCOLLECT lets you collect data set, volume usage, and migration utilityinformation. You can use this information for accounting, planning, statistical, andother purposes.

You can run DCOLLECT against a list of volumes, a generic volume serial, a list ofSMS storage groups, the migration control data set (MCDS), or the backup controldata set (BCDS). For more information, refer to DFSMS/MVS Version 1 Release 1,Access Method Services for the ICF, Special Supplement for DCOLLECT.

Ensure that DCOLLECT provides the data that you want Tivoli Decision Supportfor OS/390 to collect and process. Before putting the DFSMS component intoproduction, determine what data you want Tivoli Decision Support for OS/390 tocollect, then set up the associated DCOLLECT command parameters, which are:

MIGRATEDATASpecifies that information on migrated data sets be collected fromDFHSM’s MCDS.

BACKUPDATASpecifies that information on backed-up data sets be collected fromDFHSM’s BCDS.

CAPPLANDATASpecifies that capacity planning information for migration volumes beincluded in the output data set.

SMSDATA(SCDSNAME (entryname) / ACTIVE)Specifies that SMS configuration data is to be included in the DCOLLECToutput data set. This parameter will create one or more of theseDCOLLECT record types; DC, SC, MC, BC, SG, VL, AG, DR, and LB.

NODATAINFOSpecifies that data set information records not be generated or written tothe output data set (that is, you do not want DCOLLECT to produce dataabout active data sets from the VTOCs).

NOVOLUMEINFOSpecifies that volume information records not be generated or written tothe output data set (that is, you do not want DCOLLECT to produceVTOC data).

185

Modify DRLJCOLLBefore running the Tivoli Decision Support for OS/390 collect member, you mustupdate the DRLJCOLL job, as described in “Setting up the collect job” on page 8.

Update lookup tablesThe DFSMS component uses several lookup tables when updating data tables inthe Tivoli Decision Support for OS/390 database. You must update the lookuptables to include parameters specific to your installation.

Using the administration dialog, update these lookup tables:


DFSMS_DS_OWNER Groups data sets intoprojects.

MVS_SYSTEM_IDDS_QUALIFIER1DS_QUALIFIER2DS_QUALIFIER3

PROJECT DESCRIPTION

DFSMS_LAST_RUN Contains date and timeof last DCOLLECT run.

MVS_SYSTEM_IDRECORD_TYPE

LAST_DCOLLECT_TIME

DFSMS_MIGRATE_DAYSStores the number ofdays a data set shouldremain on a level-1volume before it ismigrated to a level-2volume. This should bethe same value asspecified in MLIDAYSin DFHSM.

MVS_SYSTEM_IDMANAGEMENT_CLASS

MIGRATE_DAYS

DFSMS_PLANNED_CAPContains the value forthe DASD capacityplanned for a systemfor a specific month.

DATEMVS_SYSTEM_IDSTORAGE_GROUP

SPACE_PLANNED

DFSMS_THRESHOLD Stores threshold valuesfor various DASDvolume exceptionalconditions in yourstorage subsystem.

MVS_SYSTEM_IDVOLSER

DSCB_FREE_MINEXTENTS_FREE_MINFRAGMENT_INDEX_MAXSPACE_FREE_MIN_PCTVIR_FREE_MIN

DFSMS_VOL_STORGRP Provides informationabout which storagegroup a volumebelongs to.

MVS_SYSTEM_IDVOLSER

STORAGE_GROUPVOLUME_LEVEL


Update DFSMS_DS_OWNERBefore running the first collect job, you must initialize this lookup table withsearch patterns by which your installation’s data sets can be grouped into projects.The effort of initializing this lookup table depends on the existing data set namingconvention used in your installation. You must supply search patterns for eachMVS system that you plan to collect data from through DCOLLECT and theDFSMS component.

For example, if you want to group all the data sets on system MVS1, starting withthe three characters DRL, into a project called PERFMGMT, insert a row in theDFSMS_DS_OWNER lookup table with these values:MVS1 DRL% % % PERFMGMT

DFSMS Customization


These values result in all data sets starting with DRL2, DRL3, DRLV, and so on,being grouped into one project called PERFMGMT.

These are other examples:MVS1 SYS% % % SYSTEMMVS1 OPC% % % OPER

You can group your data sets by the high-level qualifier content, and by thesecond- and third-level qualifiers. You can create a very detailed project structure.

If you do not group your data into projects, the data set’s high-level qualifier isused as project values in Tivoli Decision Support for OS/390’s data tables. Thismay result in too many rows in your data tables, especially if you have manyhigh-level qualifiers in your system. The DFSMS_DS_OWNER lookup table helpsyou collect data into projects, rather than collecting data for each individual dataset.

See “DFSMS_DS_OWNER” on page 212 for a complete description of the lookuptable and for an example of the contents of the table.

Update DFSMS_LAST_RUNBefore running the first collect job, you must initialize the date and time of the lastDCOLLECT run in the DFSMS_LAST_RUN lookup table. Set it to a date earlierthan the date and time of the first DCOLLECT run. If you do not set this date, thecollect job may fail. See “DFSMS_LAST_RUN” on page 213 for an example of thecontents of the table and for the exact format of the date and timestamp.

Update DFSMS_MIGRATE_DAYSBefore running the first collect job, initialize this lookup table with the number ofdays that a data set that has been assigned a particular management class willreside on a migration level 1 (ML1) volume before it becomes eligible for migrationto a migration level 2 (ML2) volume. This value may be different for differentmanagement classes in your installation, so enter one row for each managementclass on each MVS system that you plan to collect data from.

See “DFSMS_MIGRATE_DAYS” on page 214 for a complete description of the tableand for an example of the contents of the table.

Update DFSMS_PLANNED_CAPWhen tracking the use of different storage groups, use this lookup table to includecurrent and future planned storage capacity on each MVS system and storagegroup. By inserting the planned capacity values in this lookup table, with the dateswhen they are planned to occur, it is easier to see if the actual usage of the storagegroups matches the planned capacity increases.

See “DFSMS_PLANNED_CAP” on page 215 for an example of how to initializethis lookup table. Update this table every time storage plans are revised.

The old values from this lookup table should be deleted regularly (for example,once a year).

DFSMS Customization

Chapter 9. Customization 187

Update DFSMS_THRESHOLDWhen various kinds of storage exceptions should be created in the commonEXCEPTION_T table, you must add rows in this lookup table to define thethreshold values. Different threshold values can be specified for different systems,volumes, and groups of volumes.

See “DFSMS_THRESHOLD” on page 216 for examples of how to initialize thislookup table.

If no threshold values are specified in this lookup table, no exceptions will begenerated in the EXCEPTION_T table.

Update DFSMS_VOL_STORGRPThe Tivoli Decision Support for OS/390 collect process updates theDFSMS_VOL_STORGRP lookup table with information derived from theDCOLLECT volume records (type V) and the DCOLLECT capacity records (typeC).

Because type V records do not contain information on the volume level (L0 orML1), you must add this information to the DFSMS_VOL_STORGRP lookup table.

Also, because type C records do not contain information on the storage group thata volume belongs to, you must add this information to theDFSMS_VOL_STORGRP lookup table. For example, you can add this informationafter the first collect run. Later, you can update this table whenever there are majorchanges in the DASD configuration.

When you create reports based on the DFSMS_DASD_CAP table, theDFSMS_VOL_STORGRP lookup table must be up-to-date. Otherwise, the datareported per storage group or volume level will not be accurate.

You can also use this table to pool volumes not managed by DFSMS into storagepools. Tivoli Decision Support for OS/390 can then show capacity reports based onthis pooling.

For a complete description of this lookup table and an example of its contents, see“DFSMS_VOL_STORGRP” on page 217.

DFSMS Customization



The DFSMS component collects records from the DCOLLECT facility, whichextracts data from VTOCs and the DFHSM control data sets. The component thenstores the information in tables in the Tivoli Decision Support for OS/390 databaseand creates reports from these tables.

Figure 54 on page 190 shows an overview of the flow of data within the DFSMScomponent.

189


Collect

Recorddefinitions

DCOLLECT_ADCOLLECT_BDCOLLECT_CDCOLLECT_AGDCOLLECT_BCDCOLLECT_DCDCOLLECT_DRDCOLLECT_VL

DCOLLECT_MDCOLLECT_TDCOLLECT_VDCOLLECT_LBDCOLLECT_MCDCOLLECT_SCDCOLLECT_SG

DFSMS_ACTIVITY_xDFSMS_BACKUP_xDFSMS_DASD_CAP_xDFSMS_DATASET_xDFSMS_DCOLLECT_TDFSMS_MIGRATION_xDFSMS_TAPE_CAP_xDFSMS_VOLUME_xEXCEPTION_T

DFSMS_DS_OWNERDFSMS_LAST_RUNDFSMS_MIGRATE_DAYSDFSMS_THRESHOLDDFSMS_VOL_STORGRP

DFSMS_PLANNED_CAPDFSMS_VOL_STORGRP

Recordprocedure

Recorddefinition

DRL2DCOL

DCOLLECT_DA

Data tables

VTOC DFHSM

DCOLLECT

Lookup tables

Lookup tables

Reports

Figure 54. DFSMS component data flow

DFSMS data flow


Lookup tablesDuring the collect process, the DFSMS component checks the DFSMS_LAST_RUNlookup table to prevent every table from being updated more than once a day. TheDFSMS_ACTIVITY_x and DFSMS_DASD_CAP_x tables are updated only ifactivity (migration or backup) has occurred since the last DCOLLECT run. TheDFSMS_LAST_RUN lookup table is automatically updated during the collect. TheDFSMS_VOL_STORGRP table is partially updated throughout the collect process,but the update is not totally automatic. The table needs updating periodically. See“Update DFSMS_VOL_STORGRP” on page 188 for more information on updatingthis table.

As it updates the tables, the DFSMS component uses lookup tables to addinformation that makes the subsequent reports more useful. Figure 55 shows whichdata tables contain information from lookup tables.

For more information about the tables the component updates and the lookuptables it uses, see Chapter 12, “Data tables and lookup tables”, on page 195.


DFSMS data flow

Chapter 10. Data flow 191


Tivoli Decision Support for OS/390’s DFSMS component uses the DFP DCOLLECTfacility to extract information for system-managed and nonsystem-managedstorage, including active data set storage, volume usage, DFHSM backup andmigration storage, and DFHSM DASD and tape capacity planning. The DFSMScomponent processes these records from the DCOLLECT log:

DCOLLECTrecord type Record definition Description

A DCOLLECT_A Contains VSAM association information. The data includes the dataset name, the data set cluster name, and first and second byteinformation flags. DCOLLECT creates one record for each VSAMcomponent found on a processed volume.

AG DCOLLECT_AG Define DCOLLECT Aggregate Group definition record.

B DCOLLECT_B Contains data set backup version information, including the dataset name, the migration level, and the date and time of the data setmigration. DCOLLECT creates one B record for each backupversion found in the BCDS.

BC DCOLLECT_BC Define DCOLLECT Base Configuration information record.

C DCOLLECT_C Contains information on DASD capacity planning. The dataincludes the DASD volume serial number and the total volumecapacity (in tracks). DCOLLECT creates one C record for each L0and ML1 volume for each day that there is activity informationstored in the MCDS.

D DCOLLECT_D Contains information on the active data set, including the data setname, the data set block length, and the storage class and storagegroup names. DCOLLECT creates one D record for each data setfound on a processed volume.

DC DCOLLECT_DC Define DCOLLECT Data Class Construct record.

DR DCOLLECT_DR Define DCOLLECT Optical Drive information record.

LB DCOLLECT_LB Define DCOLLECT Optical Library information record.

M DCOLLECT_M Contains migration data set information such as the data set name,the device class of backup volume, and the date and time of thelatest backup version. DCOLLECT creates one M record for eachmigrated data set found in the MCDS.

MC DCOLLECT_MC Define DCOLLECT Management Class Construct record.

SC DCOLLECT_SC Define DCOLLECT Storage Class Construct record.

SG DCOLLECT_SG Define DCOLLECT Storage Group Construct record.

T DCOLLECT_T Contains tape capacity planning information, including the numberof full migration volumes and the number of empty dumpvolumes. DCOLLECT creates three T records, one for ML2 tapes,one for incremental backup tapes, and one for full volume dumptapes.

V DCOLLECT_V Contains general volume information such as the volume serialnumber, volume usage, and volume device number. DCOLLECTcreates one V record for each volume processed.

VL DCOLLECT_VL Define DCOLLECT SMS Volume information record.

193

DCOLLECTrecord type Record definition Description

D, A DCOLLECT_DA Contains data from both the DCOLLECT_D and DCOLLECT_Arecords. In this record, the VSAM component name has beenconverted to a cluster name (see “Record procedure”).

Refer to MVS/DFP: Access Method Services for the Integrated Catalog Facility fordetails on these records. You can also find information on these records in DFSMSPlanning and Reporting with DCOLLECT.

Record procedureThe DFSMS component uses a record procedure to combine data from theDCOLLECT_A and DCOLLECT_D records into one record, DCOLLECT_DA.Figure 56 illustrates this step in the collect process. The VSAM component name inDCOLLECT_D is converted to the associated cluster name in DCOLLECT_A.Moreover, the routine gets VSAM space allocation and utilization from record typeA and puts them into record type DA.

Tivoli Decision Support for OS/390 uses the output record DCOLLECT_DA toupdate the DFSMS_DATASET_x tables.

For more information on the records processed by the DFSMS component, seeChapter 11, “Log and record definitions”, on page 193.

Figure 56. DFSMS record procedure

DFSMS log and record definitions



This chapter describes the data tables and lookup tables used by the DFSMScomponent. For descriptions of common data tables, lookup tables, and controltables used by the System Performance feature, refer to the Administration Guide.

Data tablesThis section describes the data tables for the DFSMS component.

DFSMS_ACTIVITY_D, _MThese tables provide daily and monthly statistics on migration and backupactivities on the system. They contain data written by the DFSMS DCOLLECTfacility as DCOLLECT type M and B records. Only activities since the lastDCOLLECT run are recorded.

These tables are updated by the DFSMS_DS_OWNER lookup table.

The default retention periods for these tables are:DFSMS_ACTIVITY_D 30 daysDFSMS_ACTIVITY_M 765 days


DATE k DATE Date when the data set was migrated or backed-upfrom a level-0 volume. For the _M table, this is thedate of the first day of the month. From UMDATE orUBDATE.

MVS_SYSTEM_ID k CHAR(4) MVS system ID. This is the ID of the system runningDCOLLECT. From DCUSYSID.

PROJECT k CHAR(8) Name of the project the data set is related to. FromPROJECT in the DFSMS_DS_OWNER lookup table.This is derived using field DCUSYSID and the data setqualifiers as key. If no match is found, the firstqualifier in UMDSNAM or UBDSNAM is used.

STORAGE_CLASS k VARCHAR(30) Storage class name of the data set. From UMSCLAS orUBSCLAS.

MANAGEMENT_CLASS k VARCHAR(30) Management class name of the data set. FromUMMCLAS or UBMCLAS.

ACTIVITY_TYPE k CHAR(2) Type of recorded activity. This is M for a migrationactivity and B for a backup activity. From DCURCTYP.

ACTIVITIES_DASD INTEGER Number of migrated data sets or backup versions onDASD. This is the count of versions whose migrationor backup volume device class is equal to D (fromUMDEVCL or UBDEVCL).

ACTIVITIES_TAPE INTEGER Number of migrated data sets or backup versions ontape. This is the count of versions whose migration orbackup volume device class is equal to T (fromUMDEVCL or UBDEVCL).

195


ACTIVITIES_TOTAL INTEGER Total number of migrated data sets or backup versionson both DASD and tape. This is the count ofUMMDATE or UBBDATE. Use this column tocalculate averages.

ASIZE_DASD_MAX INTEGER Maximum size of a migrated data set or backupversion on DASD, in kilobytes. This is the maximumof UMDSIZE or UBDSIZE for the migrated data setsor backup versions whose volume device class isequal to D (from UMDEVCL or UBDEVCL).

ASIZE_DASD_MIN INTEGER Minimum size of a migrated data set or backupversion on DASD, in kilobytes. This is the minimumof UMDSIZE or UBDSIZE for the migrated data setsor backup versions whose volume device class isequal to D (from UMDEVCL or UBDEVCL).

ASIZE_MAX INTEGER Maximum size of a migrated data set or backupversion on DASD or tape, in kilobytes. This is themaximum of UMDSIZE or UBDSIZE.

ASIZE_MIN INTEGER Minimum size of a migrated data set or backupversion on DASD or tape, in kilobytes. This is theminimum of UMDSIZE or UBDSIZE.

ASIZE_TAPE_MAX INTEGER Maximum size of a migrated data set or backupversion on tape, in kilobytes. This is the maximum ofUMDSIZE or UBDSIZE for the migrated data sets orbackup versions whose volume device class is equal toT (from UMDEVCL or UBDEVCL).

ASIZE_TAPE_MIN INTEGER Minimum size of a migrated data set or backupversion on tape, in kilobytes. This is the minimum ofUMDSIZE or UBDSIZE for the migrated data sets orbackup versions whose volume device class is equal toT (from UMDEVCL or UBDEVCL).

ASPACE_DASD FLOAT Amount of space on DASD used for the migrated datasets or backup versions, in kilobytes. This is the sumof UMDSIZE (UBDSIZE) for the migrated data sets orbackup versions whose volume device class is equal toD (from UMDEVCL or UBDEVCL).

ASPACE_TAPE FLOAT Amount of space on tape used for the migrated datasets or backup versions, in kilobytes. This is the sumof UMDSIZE (UBDSIZE) for the migrated data sets orbackup versions whose volume device class is equal toT (from UMDEVCL or UBDEVCL).

ASPACE_TOTAL FLOAT Total amount of space on both DASD and tape usedfor the migrated data sets or backup versions, inkilobytes. This is the sum of UMDSIZE or UBDSIZE.

DFSMS data tables


DFSMS_BACKUP_D, _MThese tables provide daily and monthly statistics on backed-up data sets thatreside on the system. They contain data written by the DFSMS DCOLLECT facilityas DCOLLECT type B records.

These tables are updated by the DFSMS_DS_OWNER lookup table.

The default retention periods for these tables are:DFSMS_BACKUP_D 30 daysDFSMS_BACKUP_M 765 days.


DATE k DATE Date when DCOLLECT was run. For the _M table,this is the date of the first day of the month. FromDCUDATE.


PROJECT k CHAR(8) Name of the project the backup versions are relatedto. From PROJECT in the DFSMS_DS_OWNERlookup table. This is derived using field DCUSYSIDand the data set qualifiers as key. If no match isfound, the first qualifier in UBDSNAM is used.

STORAGE_CLASS k VARCHAR(30) Storage class name for the backup versions. FromUBSCLAS.

MANAGEMENT_CLASS k VARCHAR(30) Management class name for the backup versions.From UBMCLAS.

AGE_BACKUP_AVG FLOAT Average age of backup versions, in days. This is theaverage of the difference between DCUDATE andUBDATE.

AGE_BACKUP_MAX INTEGER Maximum age of a backup version, in days. This isthe maximum of the difference between DCUDATEand UBDATE.

AGE_BACKUP_MIN INTEGER Minimum age of a backup version, in days. This isthe minimum of the difference between DCUDATEand UBDATE.

BACKUPS_DASD INTEGER Number of backup versions on DASD. This is thecount of versions whose backup volume device classis equal to D (from UBDEVCL).

BACKUPS_TAPE INTEGER Number of backup versions on tape. This is thecount of versions whose backup volume device classis equal to T (from UBDEVCL).

BACKUPS_TOTAL INTEGER Number of backup versions. This is the count ofUBBDATE. Use this to calculate averages.

BSIZE_DASD_MAX INTEGER Maximum size of a backup version on DASD, inkilobytes. This is the maximum of UBDSIZE for thebackup versions whose backup volume device classis equal to D.

BSIZE_DASD_MIN INTEGER Minimum size of a backup version on DASD, inkilobytes. This is the minimum of UBDSIZE for thebackup versions whose backup volume device classis equal to D.

BSIZE_MAX INTEGER Maximum size of a backup version, in kilobytes. Thisis the maximum of UBDSIZE.

DFSMS data tables



BSIZE_MIN INTEGER Minimum size of a backup version, in kilobytes. Thisis the minimum of UBDSIZE.

BSIZE_TAPE_MAX INTEGER Maximum size of a backup version on tape, inkilobytes. This is the maximum of UBDSIZE for thebackup versions whose backup volume device classis equal to T.

BSIZE_TAPE_MIN INTEGER Minimum size of a backup version on tape, inkilobytes. This is the minimum of UBDSIZE for thebackup versions whose backup volume device classis equal to T.

BSPACE_DASD FLOAT Amount of space on DASD used for the backupversions, in kilobytes. This is the sum of UBDSIZEfor the backup versions whose backup volume deviceclass is equal to D (from UBDEVCL).

BSPACE_TAPE FLOAT Amount of space on tape used for the backupversions, in kilobytes. This is the sum of UBDSIZEfor the backup versions whose backup volume deviceclass is equal to T (from UBDEVCL).

BSPACE_TOTAL FLOAT Total amount of space used for the backup versions,in kilobytes. This is the sum of UBDSIZE.

DCOLLECT_RUNS INTEGER Number of DCOLLECT runs during the month. Usethis to create monthly averages. This column appliesonly to the _M table.

SPACE_ALLOC_TOTAL FLOAT Total amount of space originally allocated for thebackup versions, in kilobytes. This is the sum ofUBALLSP.

SPACE_FOR_RECOVERY FLOAT Estimated amount of space required for recovery, inkilobytes. This is the sum of UBRECSP.

SPACE_USED_TOTAL FLOAT Total amount of space originally used for the backupversions, in kilobytes. This is the sum of UBUSESP.

DFSMS data tables


DFSMS_DASD_CAP_DThis table provides daily statistics on volume utilization intended for DASDcapacity planning. It contains data extracted from DFHSM and written by theDFSMS DCOLLECT facility as type C records. Only activities since the last collectare recorded.



DATE k DATE Date when the DFHSM statistics were collected for thevolume. Only days with activity for the volume are recorded.From UCCOLDT.


VOLUME_LEVEL k CHAR(3) Level of the volume. This is L0 for level-0 volumes, and ML1for migration level-1 volumes. From UCFLAG1.

VOLSER k CHAR(6) Volume serial number. From UCVOLSR.

CAPACITY_TOTAL FLOAT Total capacity of the volume, in kilobytes. From UCTOTAL.

INT_MIGRATIONS INTEGER Number of times interval migration was run against thevolume. From UCNINTV.

OCC_AFTER_DSM INTEGER Occupancy of the volume after DFHSM space managementprocessing, as a percentage of the total capacity. FromUCAFOCC.

OCC_BEFORE_DSM INTEGER Occupancy of the volume before DFHSM space managementprocessing, as a percentage of the total capacity. FromUCBFOCC.

OCC_NOT_MIGRATED INTEGER Occupancy not migrated, in percent. This is the percentage ofthe volume data eligible to migrate but which was notmigrated because DFHSM space management had reachedthe target occupancy. From UCNOMIG.

OCC_REQUIREMENT INTEGER Total occupancy requirement, in percent. Calculated as thedifference between UCAFOCC and UCNOMIG.

OCC_TARGET INTEGER Specified target occupancy, or low threshold, assigned to thevolume, in percent. The target occupancy is the percentage ofthe volume that is desired to contain data after migrationprocessing. From UCTGOCC.

OCC_TRIGGER INTEGER Specified trigger occupancy, or high threshold, assigned tothe volume. The trigger occupancy is the percentage of thevolume that indicates that interval migration should be run.From UCTROCC.

TARGET_METS INTEGER Number of times the target occupancy was met for thevolume during interval migration. From UCINTVM.

DFSMS data tables


DFSMS_DASD_CAP_MThis table provides monthly statistics on volume utilization intended for DASDcapacity planning. It contains data extracted from DFHSM and written by theDFSMS DCOLLECT facility as type C records. Only activities since the last collectare recorded.



DATE k DATE Date when the DFHSM statistics were collected for thevolume. This is the date of the first day of the month.Only days with activity for the volume are recorded. FromUCCOLDT.


VOLUME_LEVEL k CHAR(3) Level of the volume. This is L0 for level-0 volumes, andML1 for migration level-1 volumes. From UCFLAG1.

VOLSER k CHAR(6) Volume serial number. From UCVOLSR.

CAPACITY_TOTAL FLOAT Total capacity of the volume, in kilobytes. FromUCTOTAL.

INT_MIGRATIONS_AVG FLOAT Average number of times interval migration was runagainst the volume. This is the average of UCNINTV.

OCC_AFTER_DSM_AVG FLOAT Average occupancy of the volume after DFHSM spacemanagement processing, as a percentage of the totalcapacity. This is the average of UCAFOCC.

OCC_BEFORE_DSM_AVG FLOAT Average occupancy of the volume before DFHSM spacemanagement processing, as a percentage of the totalcapacity. This is the average of UCBFOCC.

OCC_NOT_MIGR_AVG FLOAT Average occupancy not migrated, in percent. This is theaverage percentage of the volume data eligible to migratebut which was not migrated because DFHSM spacemanagement had reached the target occupancy. This is theaverage of UCNOMIG.

OCC_REQUIRE_AVG FLOAT Average occupancy requirement, in percent. This is theaverage of the difference between UCAFOCC andUCNOMIG.

OCC_TARGET_AVG FLOAT Average specified target occupancy, or low threshold,assigned to the volume, in percent. The target occupancyis the percentage of the volume that is desired to containdata after migration processing. This is the average ofUCTGOCC.

OCC_TRIGGER_AVG FLOAT Average specified trigger occupancy, or high threshold,assigned to the volume. The trigger occupancy is thepercentage of the volume that indicates that intervalmigration should be run. This is the average ofUCTROCC.

TARGET_METS_AVG FLOAT Average number of times the target occupancy was metfor the volume during interval migration. This is theaverage of UCINTVM.

VOL_COUNT INTEGER Number of times the volume has been referenced. This isthe count of UCVOLSR. This is the counter used forcalculating averages in this table.

DFSMS data tables


DFSMS_DATASET_DThis table provides daily statistics on active data sets residing in DASD volumes. Itcontains data written by the DFSMS DCOLLECT facility as type D and type Arecords. A record procedure processes the D and A records and outputs theDCOLLECT_DA record.



DATE k DATE Date when DCOLLECT was run against the volume.From DCUDATE.


PROJECT k CHAR(8) Name of the project the data set is related to. FromPROJECT in the DFSMS_DS_OWNER lookup table.This is derived using field DCUSYSID and the dataset qualifiers as key. If no match is found, the firstqualifier in DCAASSOC is used.

STORAGE_GROUP k VARCHAR(30) Storage group name for the data set. FromDCDSTOGP.

STORAGE_CLASS k VARCHAR(30) Storage class name for the data set. FromDCDSCLAS.

MANAGEMENT_CLASS k VARCHAR(30) Management class name for the data set. FromDCDMCLAS.

VOLSER k CHAR(6) Volume serial number. From DCDVOLSR.

AGE_AVG FLOAT Average age of data sets, in days. This is the averageof the difference between DCUDATE andDCDCREDT.

AGE_MAX INTEGER Maximum age of a data set, in days. This is themaximum of the difference between DCUDATE andDCDCREDT.

AGE_MIN INTEGER Minimum age of a data set, in days. This is theminimum of the difference between DCUDATE andDCDCREDT.

AGE_NOBACKUP_AVG FLOAT Average age since the last backup of the data sets, indays. This is the average of the difference betweenDCUDATE and DCDLBKDT.

AGE_NOBACKUP_MAX INTEGER Maximum age since the last backup of a data set, indays. This is the maximum of the difference betweenDCUDATE and DCDLBKDT.

AGE_NOBACKUP_MIN INTEGER Minimum age since the last backup of a data set, indays. This is the minimum of the difference betweenDCUDATE and DCDLBKDT.

AGE_NONREF_AVG FLOAT Average age of non-referenced data sets, in days.This is the average of the difference betweenDCUDATE and DCDLSTRF.

AGE_NONREF_MAX INTEGER Maximum age of the nonreferenced data sets, indays. This is the maximum of the difference betweenDCUDATE and DCDLSTRF.

AGE_NONREF_MIN INTEGER Minimum age of the nonreferenced data sets, indays. This is the minimum of the difference betweenDCUDATE and DCDLSTRF.

DFSMS data tables



BLOCK_LENGTH FLOAT Average block length, in bytes. This is the average ofDCDBKLNG.

BLOCKS_UNUSED INTEGER Total amount of space that is unused because ofnon-optimal block size or because of unused trackson allocated cylinders, in kilobytes. This is the sumof DCDNMBLK.

DATASETS_COMPR INTEGER The number of compressed non-VSAM extendedformat data sets. This is the count of data sets withDCDEXFLG indicating valid sizes (bit 0 ofDCDEXFLG is 0).

DATASETS_RACF INTEGER Number of data sets that were defined by RACF.This is the count of data sets with the RACF bit setin DCDFLAG1.

DATASETS_SMS INTEGER Number of data sets that were defined by the SMSsystem. This is the count of data sets with the SMSbit set in DCDFLAG1.

DATASETS_TOTAL INTEGER Total number of data sets. Calculated as the count ofDCAASSOC. Use this column to calculate averages.

DDM_INFO INTEGER The number of data sets for this project that haveDDM information in the catalog. From DCDFLAG3.

EXTFORM_COMP_RATIO FLOAT Average compression ratio for non-VSAM extendedformat data sets. This is the average ofDCDCUDSZ/DCDUDSIZ.

OPENMVS_FILES INTEGER The number of POSIX files that exist for this project.From DCDFLAG3.

RECORD_LENGTH FLOAT Average record length, in bytes. This is the averageof DCDLRECL.

SAM_STRIPE_DS INTEGER The number of SAM stripe data sets that exist forthis project. From DCDFLAG3.

SPACE_ALLOC_MAX INTEGER Maximum amount of space allocated to a data set, inkilobytes. This is the maximum of DCDALLSP.

SPACE_ALLOC_MIN INTEGER Minimum amount of space allocated to a data set, inkilobytes. This is the minimum of DCDALLSP.

SPACE_ALLOC_TOTAL FLOAT Total amount of space allocated to the data sets, inkilobytes. This is the sum of DCDALLSP. For VSAMdata sets, DCALLSP=DCAHARBA/1024.

SPACE_USED_TOTAL FLOAT Total amount of allocated space actually used by thedata sets, in kilobytes. This is the sum ofDCDUSESP. For VSAM data sets,DCDUSESP=DCAHURBA/1024.

VSAM_RELEASE_SPACE FLOAT Total amount of space that can be released forVSAM extended format data sets, in kilobytes. FromDCDOVERA.

DFSMS data tables


DFSMS_DATASET_MThis table provides monthly statistics on active data sets residing in DASDvolumes. It contains data written by the DFSMS DCOLLECT facility as type D andtype A records. A record procedure processes the D and A records and outputs the_DA record.



DATE k DATE Date when DCOLLECT was run against the volume.This is the date of the first day of the month. FromDCUDATE.


PROJECT k CHAR(8) Name of the project the data set is related to. FromPROJECT in the DFSMS_DS_OWNER lookup table.This is derived using field DCUSYSID and the dataset qualifiers as key. If no match is found, the firstqualifier in DCAASSOC is used.

STORAGE_GROUP k VARCHAR(30) Storage group name for the data set. FromDCDSTOGP.

STORAGE_CLASS k VARCHAR(30) Storage class name for the data set. FromDCDSCLAS.

MANAGEMENT_CLASS k VARCHAR(30) Management class name for the data set.DCDMCLAS.

VOLSER k CHAR(6) Volume serial number. From DCDVOLSR.

AGE_AVG FLOAT Average age of data sets, in days. This is the averageof the difference between DCUDATE andDCDCREDT.

AGE_MAX INTEGER Maximum age of a data set, in days. This is themaximum of the difference between DCUDATE andDCDCREDT.

AGE_MIN INTEGER Minimum age of a data set, in days. This is theminimum of the difference between DCUDATE andDCDCREDT.

AGE_NOBACKUP_AVG FLOAT Average age since the last backup of the data sets, indays. This is the average of the difference betweenDCUDATE and DCDLBKDT.

AGE_NOBACKUP_MAX INTEGER Maximum age since the last backup of a data set, indays. This is the maximum of the difference betweenDCUDATE and DCDLBKDT.

AGE_NOBACKUP_MIN INTEGER Minimum age since the last backup of a data set, indays. This is the minimum of the difference betweenDCUDATE and DCDLBKDT.

AGE_NONREF_AVG FLOAT Average age of nonreferenced data sets, in days. Thisis the average of the difference between DCUDATEand DCDLSTRF.

AGE_NONREF_MAX INTEGER Maximum age of the nonreferenced data sets, indays. This is the maximum of the difference betweenDCUDATE and DCDLSTRF.

DFSMS data tables



AGE_NONREF_MIN INTEGER Minimum age of the nonreferenced data sets, indays. This is the minimum of the difference betweenDCUDATE and DCDLSTRF.

BLOCK_LENGTH FLOAT Average block length, in bytes. This is the average ofDCDBKLNG.

BLOCKS_UNUSED INTEGER Total amount of space that is unused because ofnon-optimal block size or because of unused trackson allocated cylinders, in kilobytes. This is the sumof DCDNMBLK.

DATASETS_RACF INTEGER Number of data sets that were defined by RACF.This is the count of data sets with the RACF bit setin DCDFLAG1.

DATASETS_SMS INTEGER Number of data sets that were defined by the SMSsystem. This is the count of data sets with the SMSbit set in DCDFLAG1.

DATASETS_TOTAL INTEGER Total number of data sets. Calculated as the count ofDCAASSOC. Use this column to calculate averages.

DCOLLECT_RUNS INTEGER Number of DCOLLECT runs during the month. Usethis to create monthly averages.

DDM_INFO INTEGER Average number of data sets for this project thathave DDM information in the catalog. FromDCDFLAG3.

EXTFORM_COMP_RATIO FLOAT Average compression ratio for non-VSAM extendedformat data sets. This is the sum of theDCDCUDSZ/DCDUDSIZ averages.

OPENMVS_FILES INTEGER Average number of POSIX files for this project. FromDCDFLAG3.

RECORD_LENGTH FLOAT Average record length, in bytes. This is the averageof DCDLRECL.

SAM_STRIPE_DS INTEGER Average number of SAM stripe data sets for thisproject. From DCDFLAG3.

SPACE_ALLOC_MAX INTEGER Maximum amount of space allocated to a data set, inkilobytes. This is the maximum of DCDALLSP.

SPACE_ALLOC_MIN INTEGER Minimum amount of space allocated to a data set, inkilobytes. This is the minimum of DCDALLSP.

SPACE_ALLOC_TOTAL FLOAT Total amount of space allocated to the data sets, inkilobytes. This is the sum of DCDALLSP. For VSAMdata sets, DCALLSP=DCAHARBA/1024.

SPACE_USED_TOTAL FLOAT Total amount of allocated space actually used by thedata sets, in kilobytes. This is the sum ofDCDUSESP. For VSAM data sets, For VSAM datasets, DCDUSESP=DCAHURBA/1024.

VSAM_RELEASE_SPACE FLOAT Average amount of space that can be released forVSAM extended format data sets, in kilobytes. Thisis the sum of DCDOVERA.

DFSMS data tables


DFSMS_DCOLLECT_TThis table provides detailed statistics on the number of DCOLLECT runs perrecord type. It contains data written by the DFSMS DCOLLECT facility as type B,D, M, and T records. This table is used with other DFSMS month (_M) tables tocreate averages.



TIMESTAMP k TIMESTAMP Time when DCOLLECT was run. From DCUDATE andDCUTIME.


DATE DATE Date when the record was written. This is the date of thefirst day of the month. From DCUDATE.

DCOLLECT_RUN_B INTEGER Indicates that record type B was written by DCOLLECT. Thisis set to 1 if record type B was written; otherwise, set to null.

DCOLLECT_RUN_D INTEGER Indicates that record type D was written by DCOLLECT. Thisis set to 1 if record type D was written; otherwise, set to null.

DCOLLECT_RUN_M INTEGER Indicates that record type M was written by DCOLLECT.This is set to 1 if record type M was written; otherwise, set tonull.

DCOLLECT_RUN_T INTEGER Indicates that record type T was written by DCOLLECT. Thisis set to 1 if record type T was written; otherwise, set to null.

DFSMS data tables


DFSMS_MIGRATION_D, _MThese tables provide daily and monthly statistics on migrated data sets that resideon the system. They contain data written by the DFSMS DCOLLECT facility asDCOLLECT type M records.

These tables are updated by the DFSMS_DS_OWNER andDFSMS_MIGRATE_DAYS lookup tables.

The default retention periods for these tables are:DFSMS_MIGRATION_D 30 daysDFSMS_MIGRATION_M 765 days


DATE k DATE Date when DCOLLECT was run. For the _M table,this is the date of the first day of the month. FromDCUDATE.


LEVEL k CHAR(3) Identifies the migration level wherein the migrateddata set currently resides. This is either ML1 or ML2.From UMFLAG1.

PROJECT k CHAR(8) Name of the project the migrated data set is related to.From PROJECT in the DFSMS_DS_OWNER lookuptable. This is derived using field DCUSYSID and thedata set qualifiers as key. If no match is found, thefirst 8 characters in UMDSNAM are used.

STORAGE_CLASS k VARCHAR(30) Storage class name for the migrated data set. FromUMSCLAS.

MANAGEMENT_CLASS k VARCHAR(30) Management class name for the migrated data set.From UMMCLAS.

AGE_LASTREF_AVG FLOAT Average number of days since a migrated data set waslast referenced. This is the average of the differencebetween DCUDATE and UMLRFDT.

AGE_MIGRATED_AVG FLOAT Average age of migrated data sets, in days. This is theaverage of the difference between DCUDATE andUMDATE.

AGE_MIGRATED_MAX INTEGER Maximum age of a migrated data set, in days. This isthe maximum of the difference between DCUDATEand UMDATE.

AGE_MIGRATED_MIN INTEGER Minimum age of a migrated data set, in days. This isthe minimum of the difference between DCUDATEand UMDATE.

DCOLLECT_RUNS INTEGER Number of DCOLLECT runs during the month. Usethis to create monthly averages. This column appliesonly to the _M table.

MIGRATIONS_DASD INTEGER Number of migrated data sets on DASD. This is thecount of migrated data sets whose migration volumedevice class is equal to D (from UMDEVCL).

MIGRATIONS_EXCEED INTEGER Number of migrated data sets that exceeded thespecified number of days (in lookup tableDFSMS_MIGRATE_DAYS) that the data set shouldremain migrated to a level-1 volume before it ismigrated to a level-2 volume.

DFSMS data tables



MIGRATIONS_TAPE INTEGER Number of migrated data sets on tape. This is thecount of migrated data sets whose migration volumedevice class is equal to T (from UMDEVCL).

MIGRATIONS_TOTAL INTEGER Total number of migrated data sets on both DASD andtape. This is the count of UMMDATE. Use this columnto calculate averages.

MSIZE_DASD_MAX INTEGER Maximum size of a migrated data set on DASD, inkilobytes. This is the maximum of UMDSIZE for themigration data sets whose migration volume deviceclass is equal to D (from UMDEVCL).

MSIZE_DASD_MIN INTEGER Minimum size of a migrated data set on DASD, inkilobytes. This is the minimum of UMDSIZE for themigration data sets whose migration volume deviceclass is equal to D (from UMDEVCL).

MSIZE_TAPE_MAX INTEGER Maximum size of a migrated data set on tape, inkilobytes. This is the maximum of UMDSIZE for themigration data sets whose migration volume deviceclass is equal to T (from UMDEVCL).

MSIZE_TAPE_MIN INTEGER Minimum size of a migrated data set on tape, inkilobytes. This is the minimum of UMDSIZE for themigration data sets whose migration volume deviceclass is equal to T (from UMDEVCL).

MSPACE_DASD FLOAT Amount of space on DASD used for the migrated datasets, in kilobytes. This is the sum of UMDSIZE for themigrated data sets whose migration volume deviceclass is equal to D (from UMDEVCL).

MSPACE_EXCEED INTEGER Amount of space used for the data sets that exceededthe target occupancy on a level-1 volume, in kilobytes.This is the sum of UMDSIZE for data sets whosemigration time exceeded the number of days specifiedin lookup table DFSMS_MIGRATE_DAYS.

MSPACE_TAPE FLOAT Amount of space on tape used for the migrated datasets, in kilobytes. This is the sum of UMDSIZE for themigrated data sets whose migration volume deviceclass is equal to T (from UMDEVCL).

MSPACE_TOTAL FLOAT Total amount of space on both DASD and tape usedfor the migrated data sets, in kilobytes. This is thesum of UMDSIZE.

SPACE_ALLOC_TOTAL FLOAT Total amount of space originally allocated for themigrated data sets, in kilobytes. This is the sum ofUMALLSP.

SPACE_FOR_RECALL FLOAT Total amount of space estimated for a recall of themigrated data sets, in kilobytes. This is the sum ofUMRECSP.

SPACE_USED_TOTAL FLOAT Total amount of space originally used for the migrateddata sets, in kilobytes. This is the sum of UMUSESP.

TIMES_MIGRATED INTEGER Number of times the data sets have been migrated.This is the sum of UMNMIG.

DFSMS data tables


DFSMS_TAPE_CAP_D, _MThese tables provide daily and monthly statistics on DFHSM tape capacity. Theycontain data extracted from DFHSM and written by the DFSMS DCOLLECTfacility as type T records. The information is intended for capacity planning.

The default retention periods for these tables are:DFSMS_TAPE_CAP_D 30 daysDFSMS_TAPE_CAP_M 765 days


DATE k DATE Date when DCOLLECT was run. For the _M table, this isthe date of the first day of the month. From DCUDATE.


TAPE_TYPE k CHAR(1) Type of tape capacity planning record. This is B for backuptapes, D for dump tapes, and M for migration tapes. FromUTSTYPE.

DCOLLECT_RUNS INTEGER Number of DCOLLECT runs during the month. Use this tocreate monthly averages. This applies only to the _M table.

VOLUMES_EMPTY INTEGER Number of tapes (volumes) that are empty. This is the sumof UTEMPTY.

VOLUMES_FULL INTEGER Number of tapes (volumes) that are marked full. This is thesum of UTFULL.

VOLUMES_PART_FULL INTEGER Number of tapes (volumes) that are marked partially full.This is the sum of UTPART.

VOLUMES_TOTAL INTEGER Total number of tapes (volumes). This is the sum of emptyvolumes, full volumes, and partially full volumes. Calculatedas the sum of UTEMPTY + UTFULL + UTPART.

DFSMS data tables


DFSMS_VOLUME_DThis table provides daily statistics on DASD volumes. It contains data written bythe DFSMS DCOLLECT facility as type V records. Use this table for trendreporting on the overall utilization of DASD space.

The default retention periods for this table is 30 days.


DATE k DATE Date when DCOLLECT was run against the volume.From DCUDATE.


STORAGE_GROUP k VARCHAR(30) Storage group name for the volume. FromDCVSTGGP or set to the character string NON-SMS.

VOLSER k CHAR(6) Volume serial number. From DCVVOLSR.

CAPACITY_TOTAL FLOAT Total capacity of the volume, in kilobytes. FromDCVVLCAP.

DS_CTRL_BLOCKS FLOAT Total number of free data set control blocks in theVTOC. From DCVFDSCB.

EXTENT_MAX FLOAT Largest extent in the volume, in kilobytes. FromDCVLGEXT.

EXTENTS_FREE FLOAT Total number of free extents in the volume. FromDCVFREXT.

FRAGMENT_INDEX FLOAT Fragmentation index of the volume. FromDCVFRAGI.

SPACE_ALLOC_TOTAL FLOAT Total amount of allocated space in the volume, inkilobytes. From DCVALLOC.

SPACE_FREE_PCT FLOAT Total amount of free space in the volume, as apercentage of the total volume capacity. FromDCVPERCT.

SPACE_FREE_TOTAL FLOAT Total amount of free space in the volume, inkilobytes. From DCVFRESP.

VTOC_INDEX_RECORDS FLOAT Total number of free VTOC index records in thevolume. From DCVFVIRS.

DFSMS data tables


DFSMS_VOLUME_MThis table provides monthly statistics for DASD volumes. It contains data writtenby the DFSMS DCOLLECT facility as type V records. Use this table for trendreporting on the overall utilization of DASD space.



DATE k DATE Date when DCOLLECT was run against the volume.This is the date of the first day of the month. FromDCUDATE.


STORAGE_GROUP k VARCHAR(30) Storage group name for the volume. FromDCVSTGGP or set to the character string NON-SMS.


CAPACITY_TOTAL FLOAT Total capacity of the volume, in kilobytes. FromDCVVLCAP.

DS_CTRL_BLOCKS_AVG FLOAT Average number of free data set control blocks in theVTOC.

EXTENT_MAX INTEGER Largest extent in the volume, in kilobytes. This is themaximum of EXTENT_MAX in theDFSMS_VOLUME_D table.

EXTENTS_FREE_AVG FLOAT Average number of free extents in the volume.

FRAGMENT_INDEX_AVG FLOAT Average fragmentation index of the volume.

SPACE_ALLOC_AVG FLOAT Average amount of allocated space in the volume, inkilobytes.

SPACE_ALLOC_MAX INTEGER Maximum amount of allocated space in the volume,in kilobytes. This is the maximum ofSPACE_ALLOC_TOTAL in the DFSMS_VOLUME_Dtable.

SPACE_ALLOC_MIN INTEGER Minimum amount of allocated space in the volumein kilobytes. This is the minimum ofSPACE_ALLOC_TOTAL in the DFSMS_VOLUME_Dtable.

SPACE_FREE_AVG FLOAT Average amount of free space in the volume, inkilobytes.

SPACE_FREE_AVG_PCT FLOAT Average amount of free space in the volume, as apercentage of the total volume capacity.

SPACE_FREE_MAX_PCT INTEGER Maximum amount of free space in the volume, as apercentage of the total volume capacity. Calculatedas the maximum of SPACE_FREE_PCT in theDFSMS_VOLUME_D table.

SPACE_FREE_MIN_PCT INTEGER Minimum amount of free space in the volume, as apercentage of the total volume capacity. Calculatedas the minimum of SPACE_FREE_PCT in theDFSMS_VOLUME_D table.

VOL_COUNT INTEGER Number of times the volume has been referenced.This is the count of DCVVOLSR. This is the counterused for calculating averages in this table.

DFSMS data tables



VTOC_INDEX_REC_AVG FLOAT Average number of free VTOC index records in thevolume.

DFSMS data tables


Lookup tablesThis section describes the lookup tables specific to the DFSMS component.

DFSMS_DS_OWNERThis lookup table groups data sets into user-defined categories such as projects.The grouping is based on your local naming standard used for the first threequalifiers of the data set name.


MVS_SYSTEM_ID k CHAR(4) MVS system ID.

DS_QUALIFIER1 k CHAR(8) First-level qualifier. This is the first-level name of the data setto be related to the project name.

DS_QUALIFIER2 k CHAR(8) Second-level qualifier. This is the second-level name of thedata set to be related to the project name.

DS_QUALIFIER3 k CHAR(8) Third-level qualifier. This is the third-level name of the dataset to be related to the project name.

DESCRIPTION VARCHAR(30) Descriptive text. This is used for documentation purposesonly.

PROJECT CHAR(8) Name of the project the data set is related to.


MVSSYSTEM DS DS DS

ID QUALIFIER1 QUALIFIER2 QUALIFIER3 PROJECT DESCRIPTION------ ---------- ---------- ---------- -------- ------------------MVS1 A% % % PROJ1MVS1 B% % % PROJ2MVS1 C% % % PROJ3MVS1 D% % % PROJ4

DFSMS lookup tables


DFSMS_LAST_RUNThis lookup table controls the records to be selected into the DFSMS tables byrecording the timestamp of the last DCOLLECT run for each system ID and recordtype. The timestamps are used to prevent the tables from being updated more thanonce a day.




RECORD_TYPE k CHAR(2) Record type for the DCOLLECT record. This can be A(association), B (backup), C (capacity planning), D (dataset), M (migration), T (tape), or V (volume). FromDCURCTYP.

LAST_DCOLLECT_TIME TIMESTAMP Date and time of the last DCOLLECT run for the recordtype. This is automatically updated during collect. FromDCUDATE and DCUTIME.


MVS LASTSYSTEM RECORD DCOLLECT

ID TYPE TIME------ ------ --------------------------MVS1 A 1999-01-01-00.00.01.000000MVS1 B 1999-01-01-00.00.01.000000MVS1 C 1999-01-01-00.00.01.000000MVS1 D 1999-01-01-00.00.01.000000MVS1 M 1999-01-01-00.00.01.000000MVS1 T 1999-01-01-00.00.01.000000MVS1 V 1999-01-01-00.00.01.000000MVSE A 1999-01-01-00.00.01.000000MVSE B 1999-01-01-00.00.01.000000MVSE C 1999-01-01-00.00.01.000000MVSE D 1999-01-01-00.00.01.000000MVSE M 1999-01-01-00.00.01.000000MVSE T 1999-01-01-00.00.01.000000MVSE V 1999-01-01-00.00.01.000000NRD1 A 1999-01-01-00.00.01.000000NRD1 B 1999-01-01-00.00.01.000000

DFSMS lookup tables


DFSMS_MIGRATE_DAYSThis lookup table stores the number of days a data set should reside in a level-1volume before it is migrated into a level-2 volume. The number of days specifiedin this table should be the same as that specified with the ML1DAYS parameter inDFHSM.



MANAGEMENT_CLASS k VARCHAR(30) Management class name.

MIGRATE_DAYS INTEGER Number of days that the data set should reside in alevel-1 volume before it is migrated into a level-2volume. Use the same value as that specified withML1DAYS in DFHSM.


MVSSYSTEM MANAGEMENT MIGRATE

ID CLASS DAYS------ ------------------------------ -----------MVS1 MCNORM 10MVSE MCNOMIG 20NRD1 MCBKUP 30

DFSMS lookup tables


DFSMS_PLANNED_CAPThis lookup table contains the value for the DASD capacity planned for a systemfor a specific month. It is for comparing allocated and installed space with plannedspace, and is used with the DFSMS_VOLUME_x tables during reporting.


DATE k DATE Date that the planned space applies to. This is the date of thefirst day of the month.


STORAGE_GROUP k VARCHAR(30) Storage group name.

SPACE_PLANNED INTEGER DASD space planned for the system, in kilobytes.


MVSSYSTEM STORAGE SPACE

DATE ID GROUP PLANNED---------- ------ ------------------------------ -----------2000-01-01 MVS1 LARGE 560000002000-02-01 MVS1 LARGE 560000002000-03-01 MVS1 LARGE 460000002000-04-01 MVS1 LARGE 460000002000-05-01 MVS1 LARGE 460000002000-06-01 MVS1 LARGE 560000002000-07-01 MVS1 LARGE 56000000

DFSMS lookup tables


DFSMS_THRESHOLDThis lookup table stores threshold values for various DASD volume exceptionalconditions in your storage subsystem. You can set these threshold values so thatearly warning information can be collected and reported for your DASD volumes.



VOLSER k CHAR(6) Volume serial number.

DSCB_FREE_MIN DECIMAL(4,0) Minimum number of free data set control blocksallowed for the volume.

EXTENTS_FREE_MIN DECIMAL(3,0) Minimum number of free extents allowed for thevolume.

FRAGMENT_INDEX_MAX DECIMAL(3,0) Maximum fragmentation index allowed for thevolume.

SPACE_FREE_MIN_PCT DECIMAL(3,0) Minimum free space allowed for the volume, as apercentage of the volume capacity.

VIR_FREE_MIN DECIMAL(3,0) Minimum number of free VTOC index recordsallowed for the volume.


SPACEMVS FRAGMENT EXTENTS DSCB VIR FREESYSTEM INDEX FREE FREE FREE MIN

ID VOLSER MAX MIN MIN MIN PCT------ ------ -------- ------- ------- ------ ------MVS1 T% 600 100 150 100 15MVS1 LARG% 500 50 100 50 30SYS2 % 400 150 200 150 10

DFSMS lookup tables


DFSMS_VOL_STORGRPThis lookup table provides information about which storage group a volumebelongs to. Use this table to include storage group information in reports.




STORAGE_GROUP VARCHAR(30) Storage group name for the volume. From DCVSTGGP or setto the character string NON-SMS.

VOLUME_LEVEL CHAR(3) Level of the volume. This is L0 for level-0 volumes, and ML1for migration level-1 volumes. From UCFLAG1.


MVSSYSTEM STORAGE VOLUME

ID VOLSER GROUP LEVEL------ ------ ------------------------------ ------NRD1 PRI000 PRIMARY L0NRD1 PRI001 PRIMARY L0NRD1 LRG000 LARGE L0NRD1 LRG001 LARGE L0NRD1 OLD001 NONSMS L0NRD1 OLD002 NONSMS L0NRD1 MIG001 DFHSM ML1NRD1 MIG002 DFHSM ML1

DFSMS lookup tables


DFSMS lookup tables


Chapter 13. Reports

The DFSMS component provides these reports:v DFSMS Active/Migrat/Backup Storage, Daily/Monthly Trend reportv DFSMS Allocated/Used/Unused Storage, Daily Trend reportv DFSMS Backup Storage on DASD/Tape, Daily Trend reportv DFSMS DASD Exceptions reportv DFSMS Data Not Migrated but Eligible, Daily Trend reportv DFSMS Free Space by Storage Group, Daily/Monthly Trend reportv DFSMS Migration and Backup Activities, Daily Trend reportv DFSMS Projects Allocating Most DASD reportv DFSMS Projects Using Most DASD for Backup reportv DFSMS Projects Using Most DASD for Migration reportv DFSMS Projects Wasting Most DASD reportv DFSMS Storage Groups Meeting Target Threshold reportv DFSMS Storage Used for Migration on ML1/ML2 reportv DFSMS Tape for Migration/Backup/Dump, Daily Trend reportv DFSMS Target/Trigger Migration Values reportv DFSMS Total DASD Usage, Daily/Monthly Trend reportv DFSMS Total Storage Used by Management Class reportv DFSMS Total Storage Used by Project reportv DFSMS Total Storage Used by Storage Class reportv DFSMS Total Storage Used by Storage Group reportv DFSMS Volumes Not Meeting Target Threshold reportv DFSMS VTOC Information by Volume report

DFSMS report descriptionsThis section describes the reports provided with the DFSMS component of theSystem Performance feature.

219

DFSMS Active/Migrat/Backup Storage, Daily/Monthly Trendreport

These reports show the daily or monthly trend for active data, migrated data onDASD and tape, and backup data on DASD and tape in your installation, inmegabytes. For more information on using these reports, refer to the SystemPerformance Feature Guide.


Report ID DFSMS16 (daily), DFSMS15 (monthly)

Report group Storage management reports

Source DFSMS_DATASET_D (daily), DFSMS_DATASET_M (monthly)

Attributes DFSMS, Performance, Operations, Allocated, Migration, Backup,Daily, Monthly, Trend

Variables MVS_system_ID, From_date and To_date (daily), From_month andTo_month (monthly)


Date/month The date (daily) or the date of the first day of themonth (monthly) of the measurement.

Bspace tape (Mbytes) The average amount of backup space on tapevolumes, in megabytes. It is an average over thenumber of DCOLLECT runs per month.

Bspace DASD (Mbytes) The average amount of backup space on DASD

Figure 57. Example of a DFSMS Active/Migrat/Backup Storage, Daily Trend report

DFSMS reports


volumes, in megabytes. It is an average over thenumber of DCOLLECT runs per month.

Mspace tape (Mbytes) The average amount of migration space on tapevolumes, in megabytes. It is an average over thenumber of DCOLLECT runs per month.

Mspace DASD (Mbytes) The average amount of migration space on DASDvolumes, in megabytes. It is an average over thenumber of DCOLLECT runs per month.

Space allocated (Mbytes) The average amount of allocated space on primaryvolumes, in megabytes. It is an average over thenumber of DCOLLECT runs per month.

DFSMS reports


DFSMS Allocated/Used/Unused Storage, Daily Trend reportThis report shows the daily trend for allocated, used, and unused storage in aselected storage group, in megabytes. The values for unused space are calculatedas the difference between the space allocated and the space used values. The valuefor unused space is further adjusted with the amount of extended format VSAMspace that can be released. You can also use this report to produce a graph thatshows the total picture for all the storage groups defined in your installation. Formore information on using this report, refer to the System Performance Feature Guide.


Report ID DFSMS17


Source DFSMS_DATASET_D

Attributes DFSMS, Performance, Operations, Allocated, Used, Unused, Daily,Trend

Variables MVS_system_ID, From_date, To_date, Storage_group


Date The date of the measurement.

Space allocated (Mbytes) The total space allocated in the volumes in theselected storage group, in megabytes.

Figure 58. Example of a DFSMS Allocated/Used/Unused Storage, Daily Trend report

DFSMS reports


Space used (Mbytes) The total space used in the volumes in the selectedstorage group, in megabytes.

Space unused (Mbytes) The total space unused in the volumes in theselected storage group, in megabytes. Calculated asthe difference between space allocated and spaceused.

DFSMS reports


DFSMS Backup Storage on DASD/Tape, Daily Trend reportThis report shows the daily trend for the total amount of backup storage, inmegabytes, for the selected storage class. This report also shows how much of thisbackup storage is located on DASD volumes and tape volumes. You can use thisreport to follow the development on your backup volumes, so you can track whenit is time to move backup versions of your data to the less expensive tape medium.


Report ID DFSMS20


Source DFSMS_BACKUP_D

Attributes DFSMS, Performance, Operations, Backup, DASD, Tape,Utilization, Daily, Trend

Variables MVS_system_ID, From_date, To_date, Storage_class



Bspace Tape (Mbytes) The total amount of backup storage on tape for theselected storage class, in megabytes. Calculated as:BSPACE_TAPE / 1024.

Figure 59. Example of a DFSMS Backup Storage on DASD/Tape, Daily Trend report

DFSMS reports


Bspace DASD (Mbytes) The total amount of backup storage on DASD forthe selected storage class, in megabytes. Calculatedas: BSPACE_DASD / 1024.

Bspace total (Mbytes) The total amount of backup storage for the selectedstorage class, in megabytes. Calculated as:BSPACE_TOTAL / 1024.

DFSMS reports


DFSMS DASD Exceptions reportThis report shows a list of exceptions that occurred in your storage subsystemduring the specified period. The exceptions are recorded in the EXCEPTION_Tcommon table, and the exceptions related to the DFSMS component are identifiedby all having the Area column set to STORAGE. For more information on usingthis report, refer to the System Performance Feature Guide.


Report ID DFSMS10


Source EXCEPTION_T

Attributes DFSMS, Performance, DASD, Exceptions

Variables MVS_system_ID, Area, From_date, To_date


Date The date when the exception occurred.

System ID The system on which the exception occurred.

Area The major area the exception is related to. This isset to STORAGE for exceptions related to thestorage subsystem.

Severity The severity of the problem. This is user-defined.The default set by the DFSMS component is 04.

Exception description The text that describes the exception.

DFSMS DASD ExceptionsSystem: ’MVS1’

Date: ’2000-02-13’ to ’2000-02-20’

System ExceptionDate ID Area Severity description---------- ------ -------- -------- -------------------------------------------

2000-02-13 MVS1 STORAGE 04 Free VIRs for volume TSO004 low: 712000-02-14 MVS1 STORAGE 04 Free extents for volume TSO004 low: 232000-02-15 MVS1 STORAGE 04 Free space in volume TSO003 low: 02000-02-16 MVS1 STORAGE 04 Free DSCBs for volume TSO003 low: 30332000-02-17 MVS1 STORAGE 04 Fragment index for volume TSO003 high:7102000-02-18 MVS1 STORAGE 04 Free VIRs for volume TSO003 low: 722000-02-19 MVS1 STORAGE 04 Free extents for volume TSO003 low: 142000-02-20 MVS1 STORAGE 04 Free space in volume TSO002 low: 3

Tivoli Decision Support for OS/390 Report: DFSMS10

Figure 60. Example of a DFSMS DASD Exceptions report

DFSMS reports


DFSMS Data Not Migrated but Eligible, Daily Trend reportThis report shows the average percentage of space in each storage group that iseligible for migration, but is not migrated. The space is not migrated becauseDFHSM stops migration during daily space management or during intervalmigration when the target migration threshold has been reached for a particularvolume. This happens regardless of whether there are more data sets eligible formigration. Large percentages over a reasonable time period can indicate that thestorage group is too large, because volumes in the storage group meet their targetthresholds before eligible data sets have actually been migrated. Conversely, smallpercentages can indicate that a storage group may run out of capacity, since thereare fewer eligible data sets to migrate, to meet the target thresholds for thevolumes. There can be large differences between volumes in a storage group, soyou must analyze potential problems on a volume level also.

After Tivoli Decision Support for OS/390 collect (but before you create this report),you must update the DFSMS_VOL_STORGRP table with the correct storage groupnames. This table combines information from type V and type C DCOLLECTrecords. Storage group names for volumes found in type C records must be addedin the DFSMS_VOL_STORGRP table before you display this report. Likewise, youmay want to add a storage group name to all DFHSM’s migration level 1 volumesin this table, if you want to display this report for your ML1 volumes. For moreinformation on using this report, refer to the System Performance Feature Guide.


Report ID DFSMS12


Source DFSMS_DASD_CAP_D, DFSMS_VOL_STORGRP

Attributes DFSMS, Performance, Operations, Capacity, Daily

Variables MVS_system_ID, From_date, To_date, Storage_group, Volume_level

DFSMS reports




Storage group The storage group name (for example, TEST, ST,and LARGE).

Avg occup not migrated but eligibleThe average percentage of volume capacity notmigrated in a storage group, but which is eligiblefor migration.

The eligibility to migrate a data set depends on thenumber of days since the data set was lastreferenced, and the migration rules defined inDFHSM.

If you have volumes with different capacities in astorage group, this average percentage becomesless meaningful, because the absolute capacity ofthe volume is not weighed into the calculations;volumes with small capacities can distort theaverage values.

Figure 61. Example of a DFSMS Data Not Migrated but Eligible, Daily Trend report

DFSMS reports


DFSMS Free Space by Storage Group, Daily/Monthly Trendreport

These reports show the average free space percentage daily or monthly trend inthe storage groups defined in your installation. For more information on usingthese reports, refer to the System Performance Feature Guide.




Source DFSMS_VOLUME_D (daily), DFSMS_VOLUME_M (monthly)

Attributes DFSMS, Performance, Utilization, Storage_group, Free_space, Daily,Monthly



Date/month The date (daily), or the date of the first day of themonth (monthly) of the measurement.

Storage group The storage group name.

Avg free space (%) The average free space in the storage group, as apercentage of the total capacity of the volumes inthe storage group.

Figure 62. Example of a DFSMS Free Space by Storage Group, Daily Trend report

DFSMS reports


DFSMS Migration and Backup Activities, Daily Trend reportThis report shows the daily trend of migration and backup activities performed byDFHSM in your installation. This report shows how many backup versionsDFHSM created each day, and the number of migrations performed by DFHSMeach day. You can use this report to follow the amount of migration and backupwork performed by DFHSM each day, pinpointing extraordinarily busy days whenlots of migration and backup activities occur. For more information on using thisreport, refer to the System Performance Feature Guide.


Report ID DFSMS22


Source DFSMS_ACTIVITY_D

Attributes DFSMS, Performance, Operations, Migration, Backup, Datasets

Variables MVS_system_ID, From_date, To_date



Backup data sets The total number of backup activities. FromACTIVITIES_TOTAL when TYPE is equal to B(backup).

Migrated data sets The total number of migration activities. FromACTIVITIES_TOTAL when TYPE is equal to M(migration).

Figure 63. Example of a DFSMS Migration and Backup Activities, Daily Trend report

DFSMS reports


Activities total The total number of backup and migrationactivities.

DFSMS reports


DFSMS Projects Allocating Most DASD reportThis report shows the 10 projects in your installation that allocate the most storageon DASD, in descending megabyte order, on a selected day.

The projects are defined by the DFSMS_DS_OWNER lookup table, and depend onthe data set naming convention in your installation. For more information on usingthe report, refer to the System Performance Feature Guide.


Report ID DFSMS23



Attributes DFSMS, Performance, Operations, Allocated, Project, DASD, Worst

Variables MVS_system_ID, Date


Allocated space (Mbytes) The total amount of allocated space on primaryvolumes (L0 volumes) for the project’s data sets, inmegabytes. Calculated as: SPACE_ALLOC_TOTAL/ 1024.

Project The project name, as defined by theDFSMS_DS_OWNER lookup table.

Figure 64. Example of a DFSMS Projects Allocating Most DASD report

DFSMS reports


DFSMS Projects Using Most DASD for Backup reportThis report shows the 10 projects in your installation that allocate the most storageon DASD for backup versions, in descending megabyte order, on a selected day.

The projects are defined by the DFSMS_DS_OWNER lookup table, and depend onthe data set naming convention in your installation. For more information on usingthis report, refer to the System Performance Feature Guide.


Report ID DFSMS25


Source DFSMS_BACKUP_D

Attributes DFSMS, Performance, Operations, Project, Backup, DASD, Worst



Bspace DASD (Mbytes) The total amount of backup space on DASD for theproject’s backup data sets, in megabytes.Calculated as: BSPACE_DASD / 1024.


Figure 65. Example of a DFSMS Projects Using Most DASD for Backup report

DFSMS reports


DFSMS Projects Using Most DASD for Migration reportThis report shows the 10 projects in your installation that allocate the most storageon DASD for migration, in descending megabyte order, on a selected day.

The projects are defined by the DFSMS_DS_OWNER lookup table, and depend onthe data set naming convention in your installation.


Report ID DFSMS24


Source DFSMS_MIGRATION_D

Attributes DFSMS, Performance, Operations, Project, Migration, DASD, Worst




Mspace DASD (Mbytes) The total amount of migration space on DASD forthe project’s migrated data sets, in megabytes. Theunused space value is also adjusted with theamount of extended format VSAM space that canbe released. Calculated as: MSPACE_DASD / 1024.

DFSMS Projects Using Most DASD for MigrationSystem: ’MVS1’

Date: ’1999-10-02’

MspaceDASD

Project (Mbytes)-------- ----------ABC19 3 499ABC4 2 288ABC5 1 809ABC14 662ABC18 370ABC13 277ABC9 138ABC22 126ABC11 74ABC2 10


Figure 66. Example of a DFSMS Projects Using Most DASD for Migration report

DFSMS reports


DFSMS Projects Wasting Most DASD reportThis report shows the allocated and unused amount of DASD storage for thedifferent projects in your installation. The projects are defined by theDFSMS_DS_OWNER lookup table and depend on the installation’s data setnaming standard. The report shows the 10 most storage-wasting projects indescending order with the worst project at the top (the project with most unusedDASD storage). For more information on using this report, refer to the SystemPerformance Feature Guide.


Report ID DFSMS11



Attributes DFSMS, Performance, Utilization, Waste, DASD, Project



Space allocated (Mbytes) The total amount of allocated space, in megabytes,for the project’s data sets.

Figure 67. Example of a DFSMS Projects Wasting Most DASD report

DFSMS reports


Space unused (Mbytes) The total amount of unused space, in megabytes,for the project’s data sets. The unused space valueis also adjusted with the amount of extendedformat VSAM space that can be released.Calculated as the difference between the total spaceallocated for the project’s data sets and the totalused space by the project’s data sets.


DFSMS reports


DFSMS Storage Groups Meeting Target Threshold reportThis report tracks the volumes in the storage groups defined in your installationthat met or did not meet their target thresholds after daily space management. Thereport shows the average difference between the target volume occupation and thevolume occupation after daily space management. Negative values indicate dayswhen the volumes in a storage group did not meet the target thresholds, onaverage. To find the problem, analyze individual volumes in detail that contributeto this problem in the storage group.

After the Tivoli Decision Support for OS/390 collect (but before you create thisreport), you must update the DFSMS_VOL_STORGRP table with the correctstorage group names. This table combines information from type V and type CDCOLLECT records. Storage group names for volumes found in type C recordsmust be added in the DFSMS_VOL_STORGRP table before you display this report.Likewise, you may want to add a storage group name to all DFHSM’s migrationlevel 1 volumes in this table, if you want to display this report for your ML1volumes. For more information on using this report, refer to the System PerformanceFeature Guide.


Report ID DFSMS13



Attributes DFSMS, Performance, Operations, Storage_group, Daily, Threshold


Figure 68. Example of a DFSMS Storage Groups Meeting Target Threshold report

DFSMS reports





Avg target occupancy (%) The average target occupancy for the volumes inthe storage group, that is the average lowmigration threshold for the volumes.

Avg occupancy after dsm (%) The average occupancy after daily spacemanagement for the volumes in the storage group.

Avg thresholds met (%) The average thresholds met. This is calculated asthe difference between the average OCC_TARGETvalues and the average OCC_AFTER_DSM values.

If a storage group contains volumes with differentcapacities, these average occupancy percentagesbecome less meaningful, because the calculationsdo not weigh in the absolute volume capacities. So,volumes with small capacities affect the averagestorage group values as much as volumes withlarge capacities.

DFSMS reports


DFSMS Storage Used for Migration on ML1/ML2 reportThis report shows the daily trend for the total amount of migration storage, inmegabytes, for the selected storage class. This report also shows how much of thismigration storage is migration level 1 (ML1) and migration level 2 (ML2) storage.You can use this report to follow the development on your migration volumes, soyou can track if the number of days that data sets reside on ML1 volumes isoptimally set for the various storage classes in your installation. For moreinformation on using this report, refer to the System Performance Feature Guide.


Report ID DFSMS21


Source DFSMS_MIGRATION_D

Attributes DFSMS, Performance, Operations, Migration, Level1, Level2,Utilization

Variables MVS_system_ID, From_date, To_date, Storage_class



Mspace ML2 (Mbytes) The total migration level 2 storage for the selectedstorage class, in megabytes. Calculated as:MSPACE_TOTAL / 1024, when LEVEL is set toML2.

Figure 69. Example of a DFSMS Storage Used for Migration on ML1/ML2 report

DFSMS reports


Mspace ML1 (Mbytes) The total migration level 1 storage for the selectedstorage class, in megabytes. Calculated as:MSPACE_TOTAL / 1024, when LEVEL is set toML1.

Mspace total (Mbytes) The total migration storage for the selected storageclass, in megabytes. Calculated as:MSPACE_TOTAL / 1024.

DFSMS reports


DFSMS Tape for Migration/Backup/Dump, Daily Trend reportThis report shows a daily trend for tape usage for migrations, backup versions anddump tapes processed by DFHSM. You can use this report to determine the statusand size of your DFHSM tape pool; when too many tape volumes are onlypartially full, you can schedule a DFHSM tape recycling job. Normally this isperformed periodically by DFHSM, by the period you have defined for yourinstallation. It may have to be revised, based on this trend report. Likewise, if thenumber of unused tapes becomes too small, you can consider adding more tapevolumes to DFHSM’s tape pool. For more information on using this report, refer tothe System Performance Feature Guide.


Report ID DFSMS19


Source DFSMS_TAPE_CAP_D

Attributes DFSMS, Performance, Operations, Tape, Migration, Backup, Dump,Utilization, Daily, Trend

Variables MVS_system_ID, From_date, To_date, Tape_type



Volumes full The number of full tape volumes.

Volumes partially full The number of partially full tape volumes.

Figure 70. Example of a DFSMS Tape for Migration/Backup/Dump, Daily Trend report

DFSMS reports


Volumes empty Number of empty tape volumes.

DFSMS reports


DFSMS Target/Trigger Migration Values reportThis report shows the average daily trend for target and trigger occupancypercentages (low and high thresholds) for the volumes in a selected storage group.The report also shows the average occupancy percentage for data that is eligiblefor migration, but which was not migrated by DFHSM, because the targetthreshold was met during migration processing. See also “DFSMS Data NotMigrated but Eligible, Daily Trend report” on page 227. For more information onusing this report, refer to the System Performance Feature Guide.


Report ID DFSMS18



Attributes DFSMS, Performance, Operations, Migration, Target, Trigger




Occupancy not migr (%) The average percentage of volume capacities notmigrated in the selected storage group, but whichis eligible for migration. Calculated as the averageof OCC_NOT_MIGRATED.

Figure 71. Example of a DFSMS Target/Trigger Migration Values report

DFSMS reports


The eligibility to migrate a data set depends on thenumber of days since the data set was lastreferenced, and the migration rules defined inDFHSM.

If you have volumes with different capacities in astorage group, these average percentages becomeless meaningful, since the absolute capacity of thevolumes are not weighed into the calculations;volumes with small capacities may distort theaverage values.

Trigger occupancy (%) The average trigger occupancy (the high threshold)for the volumes in the selected storage group.Calculated as the average of OCC_TRIGGER.

Target occupancy (%) The average target occupancy (the low threshold)for the volumes in the selected storage group.Calculated as the average of OCC_TARGET.

DFSMS reports


DFSMS Total DASD Usage, Daily/Monthly Trend reportThese reports show the total allocation on the DASD volumes the DCOLLECTfacility has processed, on a daily basis. The reports also show the total (maximum)capacity of the same DASD volumes. For more information on using these reports,refer to the System Performance Feature Guide.




Source DFSMS_VOLUME_D (daily), DFSMS_VOLUME_M (monthly),DFSMS_PLANNED_CAP

Attributes DFSMS, Performance, Utilization, Storage, Daily, Monthly, Trend




Total capacity (Mbytes) The total capacity, in megabytes, of the volumesthat DCOLLECT processed.

Figure 72. Example of a DFSMS Total DASD Usage, Daily Trend report

DFSMS reports


Space allocated (Mbytes) The total space allocated, in megabytes, on thevolumes that DCOLLECT processed.

Space planned (Mbytes) The DASD space planned, in megabytes, for thesystem. This value appears only in the monthlyreport (DFSMS02).

DFSMS reports


DFSMS Total Storage Used by Management Class reportThis report shows the allocation situation for the management classes defined inyour installation, on a selected date.


Report ID DFSMS07


Source DFSMS_DATASET_D, DFSMS_MIGRATION_D,DFSMS_BACKUP_D

Attributes DFSMS, Performance, Utilization, Management_class, Storage,Daily



Management class The management class name.

Total storage (Mbytes) The sum of primary storage, migration storage(DASD and tape), and backup storage (DASD andtape), in megabytes, for the management class.

Allocated space (Mbytes) The total primary storage, in megabytes, for themanagement class.

Mspace DASD (Mbytes) The total DASD storage used by migrated data, inmegabytes, for the management class.

Mspace tape (Mbytes) The total tape storage used by migrated data, inmegabytes, for the management class.

Bspace DASD (Mbytes) The total DASD storage used by backup data, inmegabytes, for the management class.

Bspace tape (Mbytes) The total tape storage used by backup data, inmegabytes, for the management class.

DFSMS Total Storage Used by Management ClassSystem: ’MVS1’

Date: ’1999-10-02’

Total Allocated Mspace Mspace Bspace Bspace Migration BackupManagement storage space DASD tape DASD tape ratio ratioclass (Mbytes) (Mbytes) (Mbytes) (Mbytes) (Mbytes) (Mbytes) (%) (%)

--------------- ---------- ---------- ---------- ---------- ------------ -------- ---------- ----------2 747 7 0 0 2 739 0 0,0 16,6

EMNB3CD8 1 595 437 1 158 0 0 0 78,2 0,0LMMBY2 11 955 2 125 4 271 0 5 559 0 36,1 18,3LMMB3Y2 1 653 415 315 0 922 0 28,4 9,2LMMB3Y3 47 21 0 0 25 0 0,1 1,9LMNB3Y1 901 0 901 0 0 0 8,5 0,0NMMB3ND 421 129 0 0 292 0 0,0 17,6NMNB3ND 26 26 0 0 0 0 0,0 0,0NMNB3UD3 23 23 0 0 0 0 0,0 0,0UMMB3Y1 4 184 0 1 167 0 3 016 0 44,2 55,7UMMB3Y2 1 031 190 261 0 581 0 29,2 14,0UMNB5U30 877 0 877 0 0 0 72,0 0,0UMNB5Y3 526 192 334 0 0 0 60,6 0,0


Figure 73. Example of a DFSMS Total Storage Used by Management Class report

DFSMS reports


Migration ratio (%) The total migration storage on DASD and tape as apercentage of the total originally allocated primarystorage.

Backup ratio (%) The total backup storage on DASD and tape as apercentage of the total originally allocated primarystorage.

DFSMS reports


DFSMS Total Storage Used by Project reportThis report shows the storage usage situation for the projects in your installation.The projects are defined by the DFSMS_DS_OWNER lookup table and depend onthe installation’s data set naming standards. The report shows the usage of yourprimary volumes and your DFHSM migration and backup volumes. The reportalso shows, as a percentage of the original allocation on primary volumes, howmuch space is occupied by the project’s data sets on migration and backupvolumes. For more information on using this report, refer to the System PerformanceFeature Guide.


Report ID DFSMS05



Attributes DFSMS, Performance, Utilization, Project, Storage, Daily



Project The project name, as defined in theDFSMS_DS_OWNER lookup table.

Total storage (Mbytes) The sum of primary storage, migration storage(DASD and tape), and backup storage (DASD andtape), in megabytes, for the project.

Space allocated (Mbytes) The total primary storage, in megabytes, for theproject.

Mspace DASD (Mbytes) The total DASD storage used by migrated data, inmegabytes, for the project.

DFSMS Total Storage Used by ProjectSystem: ’NRD1’

Date: ’1999-10-02’

Total Space Mspace Mspace Bspace Bspace Migration Backupstorage allocated DASD tape DASD tape ratio ratio

Project (Mbytes) (Mbytes) (Mbytes) (Mbytes) (Mbytes) (Mbytes) (%) (%)-------- ---------- ---------- ---------- ---------- ---------- ---------- ---------- ----------ABC11 437 90 74 0 273 0 12,0 11,5ABC12 114 34 10 0 69 0 4,3 5,2ABC13 381 101 277 0 2 0 77,5 1,2ABC14 1 354 384 662 0 308 0 61,7 6,3ABC15 103 69 5 0 29 0 11,1 6,0ABC16 6 2 1 0 3 0 73,0 48,6ABC18 874 9 370 0 495 0 57,4 48,2ABC19 13 768 2 123 3 499 0 8 147 0 33,0 24,0ABC2 57 5 10 0 41 0 45,0 19,2ABC22 336 1 126 0 210 0 64,0 18,8ABC3 356 150 5 0 201 0 7,9 10,8ABC4 3 328 485 2 288 0 555 0 18,0 17,1ABC5 3 936 26 1 809 0 2 101 0 52,6 22,9ABC6 39 5 9 0 25 0 59,7 43,0ABC9 896 83 138 0 675 0 22,5 7,0


Figure 74. Example of a DFSMS Total Storage Used by Project report

DFSMS reports


Mspace tape (Mbytes) The total tape storage used by migrated data, inmegabytes, for the project.

Bspace DASD (Mbytes) The total DASD storage used by backup data, inmegabytes, for the project.

Bspace tape (Mbytes) The total tape storage used by backup data, inmegabytes, for the project.

Migration ratio (%) The total migration storage on DASD and tape, asa percentage of the total originally allocatedprimary storage.

Backup ratio (%) The total backup storage on DASD and tape, as apercentage of the total originally allocated primarystorage.

DFSMS reports


DFSMS Total Storage Used by Storage Class reportThis report shows the allocation situation on a selected date for the storage classesdefined in your installation. For more information on using this report, refer to theSystem Performance Feature Guide.


Report ID DFSMS06



Attributes DFSMS, Performance, Utilization, Storage_class, Storage, Daily



Storage class The storage class name.

Total storage (Mbytes) The sum of primary storage, migration storage(DASD and tape) and backup storage (DASD andtape), in megabytes, for the storage class.

Space allocated (Mbytes) The total primary storage, in megabytes, for thestorage class.

Mspace DASD (Mbytes) The total DASD storage used by migrated data, inmegabytes, for the storage class.

Mspace tape (Mbytes) The total tape storage used by migrated data, inmegabytes, for the storage class.

Bspace DASD (Mbytes) The total DASD storage used by backup data, inmegabytes, for the storage class.

Bspace tape (Mbytes) The total tape storage used by backup data, inmegabytes, for the storage class.

Migration ratio (%) The total migration storage on DASD and tape, asa percentage of the total originally allocatedprimary storage.

Backup ratio (%) The total backup storage on DASD and tape, as apercentage of the total originally allocated primarystorage.

DFSMS Total Storage Used by Storage ClassSystem: ’MVS1’

Date: ’1999-10-02’

Total Space Mspace Mspace Bspace Bspace Migration BackupStorage storage allocated DASD tape DASD tape ratio ratioclass (Mbytes) (Mbytes) (Mbytes) (Mbytes) (Mbytes) (Mbytes) (%) (%)

------- ---------- ---------- --------- --------- --------- --------- --------- ------SNMN 22 818 3 430 9 285 0 10 103 0 30,3 19,7SYQR 421 129 0 0 292 0 0,0 17,6


Figure 75. Example of a DFSMS Total Storage Used by Storage Class report

DFSMS reports


DFSMS Total Storage Used by Storage Group reportThis report shows the allocation situation in the storage groups defined in yourinstallation, on a selected date.


Report ID DFSMS04


Source DFSMS_VOLUME_D

Attributes DFSMS, Performance, Utilization, Storage_group, Storage, Daily

Variables MVS_system_ID, Date, Storage_group


Storage group The name of the storage group.

Volumes The number of volumes in the storage group.

Capacity (Mbytes) The total capacity of the volumes in the storagegroup, in megabytes.

Allocated space (Mbytes) The total allocated space in the volumes in thestorage group.

Free space (Mbytes) The total free space available in the storage group,in megabytes.

Largest extent (Kbytes) The largest used extent in the storage group, inkilobytes.

DFSMS Total Storage Used by Storage GroupSystem: ’NRD1’

Date: ’1999-10-02’Storage group: STORAGE_GROUP

Allocated Free LargestStorage Capacity space space extentgroup Volumes (Mbytes) (Mbytes) (Mbytes) (Kbytes)

------------------------------ ---------- ---------- ---------- ---------- ----------ST 2 5 413 3 446 1 967 421 660

========== ========== ========== ========== ==========Total 2 5 413 3 446 1 967 421 660


Figure 76. Example of a DFSMS Total Storage Used by Storage Group report

DFSMS reports


DFSMS Volumes Not Meeting Target Threshold reportThis report shows volume occupancy values on the selected date. The triggeroccupancy is the high threshold value that initiates interval migration by DFHSM.The target occupancy is the low threshold that DFHSM attempts to reach duringinterval migration or during daily space management. Occupancies before andafter DFHSM’s daily space management are also reported. The right-most columnindicates whether the volume met the target occupancy (low threshold), by listingthe difference between target occupancy and occupancy after daily spacemanagement. A positive value indicates that the target occupancy has been met; anegative value indicates that the target occupancy was not met. The report issorted in ascending sequence of the right-most column.

After a Tivoli Decision Support for OS/390 collect (but before you create thisreport), you must update the DFSMS_VOL_STORGRP table with the correctstorage group names. This table combines information from type V and type CDCOLLECT records. Storage group names for volumes found in type C recordsmust be added in the DFSMS_VOL_STORGRP table before you display this report.Likewise, you may want to add a storage group name to all DFHSM’s migrationlevel 1 volumes in this table, if you want to display this report for your ML1volumes. For more information on using this report, refer to the System PerformanceFeature Guide.


Report ID DFSMS14



Attributes DFSMS, Performance, Operations, Volume, Daily, Threshold



Volser The volume serial number.


DFSMS Volumes Not Meeting Target ThresholdSystem: ’MVS1’

Date: ’1999-12-10’

Occup Occup ThresholdTarget Trigger before after met/

Storage occupancy occupancy dsm dsm not metVolser group (%) (%) (%) (%) (%)------ ------------------------------ ----------- ----------- ----------- ----------- -----------TST003 TEST 50 70 67 67 -17TST005 TEST 50 70 61 60 -10TST004 TEST 50 70 54 54 -4PRI004 ST 60 80 72 63 -3TST000 TEST 50 70 54 52 -2PRI006 ST 60 80 64 59 1PRI008 ST 60 80 60 59 1PRI013 ST 60 80 49 48 12PRI010 ST 60 80 47 47 13LRG000 LARGE 50 70 31 31 19


Figure 77. Example of a DFSMS Volumes not Meeting Target Threshold report

DFSMS reports


Target occupancy (%) The specified target occupancy (low threshold)assigned to the volume, in percent. The targetoccupancy is the percentage of the total volumecapacity that is desired to contain data afterDFHSM’s migration processing.

Trigger occupancy (%) The specified trigger occupancy (high threshold)assigned to the volume, in percent. The triggeroccupancy is the percentage of the total volumecapacity that indicates that interval migrationshould be run by DFHSM.

Occup before dsm (%) The volume’s occupancy, in percent, before dailyspace management.

Occup after dsm (%) The volume’s occupancy, in percent, after dailyspace management.

Threshold met/not met (%) The thresholds met or not met. This is thedifference between the volume’s target occupancyand the occupancy after daily space management.Calculated as: OCC_TARGET −OCC_AFTER_DSM.

DFSMS reports


DFSMS VTOC Information by Volume reportThis report shows VTOC information for selected DASD volumes, on the selecteddate. Different aspects of each volume’s usage are reported, such as fragmentationindex, free data set control blocks, and free space in megabytes and in percentageof total volume capacity. For more information on using this report, refer to theSystem Performance Feature Guide.


Report ID DFSMS03


Source DFSMS_VOLUME_D

Attributes DFSMS, Performance, VTOC, Unused, Storage, Volume

Variables MVS_system_ID, Date, Volser


Volser The volume serial number of the volume

Fragment index The fragmentation index of the volume. This is anumber between 000 and 999. The higher thenumber, the more fragmented the volume.

Free extents The number of free extents available in the volume.

Free DSCBs The number of free data set control blocksavailable in the volume.

Free VIRs The number of free VTOC index records availablein the volume.

Free space (%) The free space in the volume, as a percentage ofthe volume capacity.

Free space (Mbytes) The free space in the volume, in megabytes.

DFSMS VTOC Information by VolumeSystem: ’MVS1’

Date: ’2000-02-05’Volser: ’TSOL__’

Free FreeFragment Free Free Free space space

Volser index extents DSCBs VIRs (%) (Mbytes)------ ----------- ----------- ----------- ----------- ----------- -----------TSOL01 514 257 3 028 257 24 442TSOL02 541 199 3 346 264 18 329TSOL03 489 171 3 255 268 19 358TSOL04 637 225 3 063 256 16 300TSOL05 242 100 3 158 262 19 363

=========== =========== =========== =========== =========== ===========Average 485 190 3 170 261 19 358


Figure 78. Example of a DFSMS VTOC Information by Volume report

DFSMS reports


DFSMS reports


Part 5. DFSMS/RMM component

Chapter 14. Customization . . . . . . . . 259Make input data available . . . . . . . . . 259Modify the collect job . . . . . . . . . . 260Update lookup table . . . . . . . . . . . 261

Chapter 15. Data flow . . . . . . . . . . 263Lookup table . . . . . . . . . . . . . 263

Chapter 16. Log and record definitions . . . . 265

Chapter 17. Data tables and lookup table . . . 267Data tables . . . . . . . . . . . . . . 268

DFRMM_DATASET_D . . . . . . . . . 268DFRMM_DATASET_M . . . . . . . . . 269DFRMM_VOLUME_D . . . . . . . . . 270DFRMM_VOLUME_M . . . . . . . . . 272

Lookup table . . . . . . . . . . . . . 275DFSMS_DS_OWNER . . . . . . . . . . 275

Chapter 18. Reports . . . . . . . . . . 277DFRMM report descriptions . . . . . . . . 277

DFRMM Location Statistics, Detail report . . . 278DFRMM Error Statistics, Detail report . . . . 279DFRMM Volumes by Location, Monthly Trendreport . . . . . . . . . . . . . . . 280DFRMM Project Statistics, Detail report. . . . 281DFRMM Space Usage by Storage Group, DailyTrend report . . . . . . . . . . . . . 282

257


Before you can use the DFSMS/RMM component to collect data and create reports,you must customize and test the installation. This chapter describes the steps youmust perform to customize the DFSMS/RMM component:1. Make input data available.2. Modify the collect job.3. Update lookup table.

Make input data availableTo ensure that the DFSMS/RMM component collects the correct data, perform thefollowing steps:1. Create an EXTRACT DATASET using the EDGHSKP program with RPTEXT

parameter. You can submit a job with JCL as shown://HSKP EXEC PGM=EDGHSKP,// PARM=’RPTEXT,DATEFORM(E)’//MESSAGE DD DISP=SHR,DSN=HSKP.MESSAGES//REPTEXT DD DISP=SHR,DSN=MASTER.EXTRACT

Use the DATEFORM parameter to specify the format for date fields in thereport extract data set. The DATEFORM parameter can take any of thefollowing values:

Value Language Format Example

A American mm/dd/yyyy 12/15/1999

E European dd/mm/yyyy 15/12/1999

I ISO yyyy/mm/dd 1999/12/15

J Julian yyyy/ddd 1999/349

D default Initially set to Julian

For more information, refer to DFSMS/MVS DFSMSrmm™ Implementation andCustomization Guide.

2. Run the DRLERRME preprocessor exec to add a collect date (COLLECTDATEparameter) field and a collect dateform (DATEFORM parameter) field to eachrecord in the RMM extract data set.The DATEFORM parameter specified in the DRLERRME exec must be the samevalue as specified in the DATEFORM parameter of the EDGHSKP program andmust be one of the following values:

A American date format (default)

E European date format

I ISO date format

J Julian date format

The COLLECTDATE parameter is a REXX expression and must have a REXXstandard date format (yyyymmdd) as a collect date. The default is DATE(’S’),that is, the current date. The previous date can be expressed asDATE(″S″,DATE(″B″)-1,″B″).

259

Modify the collect jobThe DFSMS/RMM component uses the DRLJCRMM job for collecting controlrecords. This job has two steps as shown in Figure 79 on page 260:1. Run the DRLERRME preprocessor for EXTRACT data set.2. Run Tivoli Decision Support for OS/390 Collect.

Before running the DRLJCRMM job:v Create an EXTRACT data set.v Change the dataset names according to the naming convention of your

installation.v Check the DB2 SYSTEM and SYSPREFIX names.v Allocate DDNAME RMMIN for the EXTRACT data set.v Change the DATEFORM and COLLECTDATE parameters according to your date

rules.

The DRLJCRMM job writes the processed EXTRACT dataset to a temporary dataset, which is deleted when the job completes. If you want to save the data, changethe DRLJCRMM job.

//DRLJCRMM JOB (ACCT#),’RMM’//***************************************************************//* Licensed Materials - Property of IBM *//* 5695-101 (C) Copyright IBM Corporation 1993, 2003 *//* See Copyright Instructions. *//***************************************************************//************************************************ *//* STEP 1 OF 2: RMM EXTRACT FILE PRE PROCESSOR *//************************************************ *//REXXISPF EXEC PGM=IKJEFT01,DYNAMNBR=25 *//SYSPROC DD DISP=SHR,DSN=drl.sdrlexec *//SYSPRINT DD SYSOUT=* *//SYSTSPRT DD SYSOUT=* *//SYSTSIN DD * *

%DRLERRME + *DATEFORM = E COLLECTDATE = DATE("S",DATE("B")-1,"B") *

//RMMIN DD DISP=SHR,DSN=extract-dataset *//RMMOUT DD DSN=&&RMM,DISP=(NEW,PASS),SPACE=(TRK,(30,10)), *// UNIT=SYSDA,DCB=(RECFM=VB,LRECL=1000) */* *//****************************************************** *//* STEP 2 OF 2: RUN Tivoli Decision Support for OS/390 COLLECT *//****************************************************** *//IFRC1 IF RC=0 THEN *//RUNLOG EXEC PGM=DRLPLC,PARM=(’SYSTEM=DSN’, *// ’SYSPREFIX=DSN’) *//STEPLIB DD DISP=SHR,DSN=DRL160.SDRLLOAD *// DD DISP=SHR,DSN=DSN610.DSNLOAD *//DRLOUT DD SYSOUT=* *//DRLLOG DD DSN=&&RMM,DISP=(OLD,DELETE) *//DRLDUMP DD SYSOUT=* *//DRLIN DD * *

COLLECT DFRMM_EXTRACT *REPROCESS; *

//IFRC2 ENDIF *

Figure 79. DRLJCRMM job

DFSMS/RMM Customization


Update lookup tableThe DFSMS/RMM component uses one lookup table when updating data tables inthe Tivoli Decision Support for OS/390 database. You must update the lookuptable to include parameters specific to your installation.

Using the administration dialog, update this lookup table:


DFSMS_DS_OWNER Groups data sets intoprojects.


PROJECTDESCRIPTION


DFSMS/RMM Customization



The DFSMS/RMM component extracts the control data set. The component thenstores the information in tables in the Tivoli Decision Support for OS/390 databaseand creates reports from these tables.

Figure 80 shows an overview of the flow of data within the DFSMS/RMMcomponent.

Lookup tableDuring the collect process, the DFSMS/RMM component checks theDFSMS_DS_OWNER lookup table to organize the data set into user-definedgroups, for example, PROJECTS. The grouping is based on the local namingstandard that is used for the first three qualifiers of data set names.

Figure 81 shows which data table contain information from the lookup table.

DFSMS/RMM

Reports

Extract dataset from control file

Tivoli DecisionSupport for OS/390record definition

Data tables

Lookup table

DFRMM_DATASETDFRMM_VRSDFRMM_OWNERDFRMM_PRODUCTDFRMM_RACKDFRMM_SLBINDFRMM_VOLUME

DFRMM_DATASET_DDFRMM_DATASET_MDFRMM_VOLUME_DDFRMM_VOLUME_M

DFSMS_DS_OWNER

Figure 80. DFSMS/RMM component data flow

263

For more information about the table the component updates and the lookup tableit uses, see “DFSMS_DS_OWNER” on page 275.

DFSMS_DS_OWNER DFRMM_DATASET_D

PROJECTDESCRIPTION



DFSMS/RMM Data Flow



The DFSMS/RMM component extracts information from the EXTRACT data set.The EXTRACT data set gets information from the CONTROL data set that containsthe complete inventory of removable media library and the defined movement andretention policies. In the CONTROL data set, the component records all changesmade to the inventory, for example, adding or deleting volumes. TheDFSMS/RMM component processes the following records:

DFSMSrmmrecord type Record definition Description

D DFRMM_DATASET Contains the data set name record in the RMM extract file asmapped by the DFSMS macro EDGRDEXT.

V DFRMM_VOLUME Contains the volume record in the RMM extract file as mapped bythe DFSMS macro EDGRVEXT.

The DFSMS/RMM component provides record mappings for the following recordsbut does not use them:

DFSMSrmmrecord type Record definition Description

K DFRMM_VRS Contains the vital specification record in the RMM extract file asmapped by the DFSMS macro EDGRKEXT.

O DFRMM_OWNER Contains the owner record in the RMM extract file as mapped bythe DFSMS macro EDGROEXT.

P DFRMM_PRODUCT Contains the product record in the RMM extract file as mapped bythe DFSMS macro EDGRPEXT.

R DFRMM_RACK Contains the rack number record in the RMM extract file asmapped by the DFSMS macro EDGRREXT.

S DFRMM_SLBIN Contains the storage and shelf location in the RMM extract file asmapped by the DFSMS macro EDGRSEXT.

265

DFSMS/RMM Log and record definitions


Chapter 17. Data tables and lookup table

This chapter describes the data tables and lookup table used by the DFSMS/RMMcomponent. For descriptions of common data tables, lookup tables, and controltables used by the System Performance feature, refer to the Administration Guide.

267

Data tablesThis section describes the data tables for the DFSMS/RMM component.

DFRMM_DATASET_DThis table provides daily statistics on data set records in the RMM extract file.

This table is updated by the DFSMS_DS_OWNER lookup table.



DATE k DATE Date by preprocessor exec DRLERRME.

MVS_SYSTEM_ID k CHAR(8) MVS system ID. From RVCRSID.

PROJECT k CHAR(8) Lookup in the DFSMS_DS_OWNER lookup table.

CR_UNIT k CHAR(4) Creating drive address. From RDUNITAD.

DS_OWNER k CHAR(8) Owner of the data set. From RDOWNDSN.

MGMT_CLASS k CHAR(8) SMS management class. From RDMCNAME.

STORAGE_GROUP k CHAR(8) SMS storage group name. From RDSGNAME.

STORAGE_CLASS k CHAR(8) SMS storage class name. From RDSCNAME.

DATA_CLASS k CHAR(8) SMS data class name. From RDDCNAME.

VRS_TYPE k CHAR(1) Matching VRS type. From RDVRSTYP. One of: D-DATASET,S-SMSMC, V-VRSMV, M-DATASET AND VRSMV, C-DATASETAND SMSMC.

DATASET_COUNT INTEGER Number of data sets. Calculated as the count of RDDSNAME.

DATASET_NONEXP_CNT INTEGER Number of data sets not expired.

AGE_CREATE_SUM INTEGER Sum of days since creation. From RDCRDATE.

AGE_CHANGE_SUM INTEGER Sum of days since change. From RDLCDATE.

COMPACT_COUNT INTEGER Number of data sets using compaction. From RDCOMP.

BLOCK_COUNT_SUM FLOAT Sum of blocks. From RDBLKCNT.

AGE_READ_SUM INTEGER Sum of days since read. From RDLRDDAT.

AGE_WRITE_SUM INTEGER Sum of days since write. From RDLRDDAT.

EXPDT_DAYS_SUM INTEGER Sum of days until expedite. From RDRETDAT.

DS_SIZE_KB_SUM FLOAT Sum of data sets size in kilobytes. From RDRETDAT.

ABEND_COUNT INTEGER Number of data sets closed by abend. From RDABEND.

CAT_COUNT INTEGER Number of data sets used via catalog. From RDCAT.

RETAIN_VRS_COUNT INTEGER Number of data sets retained by VRS. From RDVRS.

DFSMS data tables


DFRMM_DATASET_MThis table provides monthly statistics on data set records in the RMM extract file.



DATE k DATE Date rounded to month.


PROJECT k CHAR(8) Project.

CR_UNIT k CHAR(4) Creating drive address.

DS_OWNER k CHAR(8) Owner of the data set.

MGMT_CLASS k CHAR(8) SMS management class.

STORAGE_GROUP k CHAR(8) SMS storage group name.

STORAGE_CLASS k CHAR(8) SMS storage class name.

DATA_CLASS k CHAR(8) SMS data class name.

VRS_TYPE k CHAR(1) VRS type.

DAYS_COLLECTED INTEGER Number of days collected in the month.

DATASET_COUNT INTEGER Sum of data sets.

DATASET_NONEXP_CNT INTEGER Sum of data sets not expired.

AGE_CREATE_SUM INTEGER Sum of days since creation.

AGE_CHANGE_SUM INTEGER Sum of days since change.

COMPACT_COUNT INTEGER Sum of data sets using compaction.

BLOCK_COUNT_SUM FLOAT Sum of blocks.

AGE_READ_SUM INTEGER Sum of days since read.

AGE_WRITE_SUM INTEGER Sum of days since write.

EXPDT_DAYS_SUM INTEGER Sum of days until expedite.

DS_SIZE_KB_SUM FLOAT Sum of data sets size in kilobytes.

ABEND_COUNT INTEGER Sum of data sets closed by abend.

CAT_COUNT INTEGER Sum of data sets used via catalog.

RETAIN_VRS_COUNT INTEGER Sum of data sets retained by VRS.

DATASET_MAX INTEGER Maximum of data sets.

DATASET_NONEXP_MAX INTEGER Maximum of data sets not expired.

AGE_CREATE_MAX INTEGER Maximum of days since creation.

AGE_CHANGE_MAX INTEGER Maximum of days since change.

COMPACT_MAX INTEGER Maximum of data sets using compaction.

BLOCK_COUNT_MAX FLOAT Maximum of blocks.

AGE_READ_MAX INTEGER Maximum of days since read.

AGE_WRITE_MAX INTEGER Maximum of days since write.

EXPDT_DAYS_MAX INTEGER Maximum of days until expedite.

DS_SIZE_KB_MAX FLOAT Maximum of data sets size in kilobytes.

ABEND_MAX INTEGER Maximum of data sets closed by abend.

CAT_MAX INTEGER Maximum of data sets used via catalog.

RETAIN_VRS_MAX INTEGER Maximum of data sets retained by VRS.

DFSMS data tables

Chapter 17. Data tables and lookup table 269

DFRMM_VOLUME_DThis table provides daily statistics on volume records in the RMM extract file.



DATE k DATE Date set by the preprocessor exec DRLERRME.

MVS_SYSTEM_ID k CHAR(8) MVS system ID. From RVCRSID.

DENSITY k CHAR(4) Recording density from RVDEN.

LOCATION k CHAR(8) Current location name. From RVSTORID.

BIN_NUMBER k CHAR(6) Bin location number. From RVSTBIN.

LOAN_LOCATION k CHAR(8) Loan location. From RVLONLOC.

VOLUME_OWNER k CHAR(8) User ID of the volume owner. From RVOWNID.

VOLUME_STATUS k CHAR(8) Volume status. From RVSTATUS.

LABEL_TYPE k CHAR(3) Label type. From RVLABEL.

LAST_USED_DRIVE k CHAR(4) Last used drive. From RVLUDEV.

VOLUME_COUNT INTEGER Number of volumes.

VOLUME_NONEXP_CNT INTEGER Number of volumes not expired.

AGE_CREATE_SUM INTEGER Sum of days since creation. From RVCRDATE.

AGE_CHANGE_SUM INTEGER Sum of days since change. From RVCRDATE.

EXPDT_DAYS_SUM INTEGER Sum of days until expedite for non-expired volumes.From RVEXPDT.

COMPACT_COUNT INTEGER Number of volumes using compaction. From RVCOMP.

DATASETS_SUM INTEGER Sum of data sets on volumes. From RVDSNNO.

TAPE_KB_SUM FLOAT Sum of kilobytes used on volumes. From RVTUSE.

USE_COUNT_SUM INTEGER Sum of use count on volumes. From RVUSE.

AGE_READ_SUM INTEGER Sum of days since last read. From RVLRDDAT.

AGE_WRITE_SUM INTEGER Sum of days since last write. From RVLWDAT.

PEND_REL_COUNT INTEGER Number of volumes pending release. From RVPENDRS.

RETAIN_VRS_COUNT INTEGER Number of volumes retained by VRS. From RVVRS.

LOAN_COUNT INTEGER Number of volumes on loan. From RVLOAN.

OPEN_COUNT INTEGER Number of volumes open. From RVOPEN.

REC_O_C_EOV_COUNT INTEGER Number of volumes recorded by O / C / EOV. FromRVOCER.

PARMLIB_RETPD_COUNT INTEGER Number of volumes that used the PARMLIB default.From RVDEFRET.

PP_TAPE_COUNT INTEGER Number of volumes for program products. FromRVPPTAPE.

BLP_COUNT INTEGER Number of volumes last written BLP. From RVBLP.

VM_USE_COUNT INTEGER Number of volumes for VM use. From RVVMUSE.

MVS_USE_COUNT INTEGER Number of volumes for MVS use. From RVMVSUSE.

TEMP_RERR_SUM INTEGER Sum of temporary read errors. From RVTRERR.

TEMP_WERR_SUM INTEGER Sum of temporary write errors. From RVTWERR.

PERM_RERR_SUM INTEGER Sum of permanent read errors. From RVPRERR.

DFSMS data tables



PERM_WERR_SUM INTEGER Sum of permanent write errors. From RVPWERR.

RETURN_SCRTC_COUNT INTEGER Number of volumes pending scratch. From RVACTSCR.

REPLACE_COUNT INTEGER Number of volumes pending replace. From RVACTREP.

RETURN_OWNER_COUNT INTEGER Number of volumes pending return to owner. FromRVACTRET.

INIT_COUNT INTEGER Number of volumes pending initialize. FromRVACTINI.

ERASE_COUNT INTEGER Number of volumes pending erase. From RVACTERA.

NOTIFY_COUNT INTEGER Number of volumes pending notify. From RVACTNOT.

ABEND_COUNT INTEGER Number of volumes with data set closed by abend.From RVABEND.

IGNORE_EXPDT_COUNT INTEGER Number of volumes that ignored EXPDT. FromRVRELIXD.

SCRATCH_IMMED_CNT INTEGER Number of volumes scratch immediate. From RVRELSI.

DFSMS data tables


DFRMM_VOLUME_MThis table provides monthly statistics for volume records in the RMM extract file.



DATE k DATE Date rounded to first day in month.


DENSITY k CHAR(4) Recording density.

LOCATION k CHAR(8) Current location name.

BIN_NUMBER k CHAR(6) Bin number.

LOAN_LOCATION k CHAR(8) Loan location.

VOLUME_OWNER k CHAR(8) User ID of the volume owner.

VOLUME_STATUS k CHAR(8) Volume status.

LABEL_TYPE k CHAR(3) Label type.

LAST_USED_DRIVE k CHAR(4) Last used drive.

DAYS_COLLECTED INTEGER Number of days collected in the month.

VOLUME_SUM INTEGER Sum of volumes.

VOLUME_NONEXP_SUM INTEGER Sum of volumes not expired.

AGE_CREATE_SUM INTEGER Sum of days since creation.

AGE_CHANGE_SUM INTEGER Sum of days since change.

EXPDT_DAYS_SUM INTEGER Sum of days until expedite for nonexpired volumes.

COMPACT_SUM INTEGER Sum of volumes using compaction.

DATASETS_SUM INTEGER Sum of data sets on volumes.

TAPE_KB_SUM FLOAT Sum of kilobytes used on volumes.

USE_COUNT_SUM INTEGER Sum of use count on volumes.

AGE_READ_SUM INTEGER Sum of days since last read.

AGE_WRITE_SUM INTEGER Sum of days since last write.

PEND_REL_SUM INTEGER Sum of volumes pending release.

RETAIN_VRS_SUM INTEGER Sum of volumes retained by VRS.

LOAN_SUM INTEGER Sum of volumes on loan.

OPEN_SUM INTEGER Sum of volumes open.

REC_O_C_EOV_SUM INTEGER Sum of volumes recorded by O / C / EOV.

PARMLIB_RTPD_SUM INTEGER Sum of volumes that used the PARMLIB defaultRETPD.

PP_TAPE_SUM INTEGER Sum of volumes for program products.

BLP_SUM INTEGER Sum of volumes last written BLP.

VM_USE_SUM INTEGER Sum of volumes for VM use.

MVS_USE_SUM INTEGER Sum of volumes for MVS use.

TEMP_RERR_SUM INTEGER Sum of temporary read errors.

TEMP_WERR_SUM INTEGER Sum of temporary write errors.

PERM_RERR_SUM INTEGER Sum of permanent read errors.

PERM_WERR_SUM INTEGER Sum of permanent write errors.

DFSMS data tables



RETURN_SCRTC_SUM INTEGER Sum of volumes pending scratch.

REPLACE_SUM INTEGER Sum of volumes pending replace.

RETURN_OWNER_SUM INTEGER Sum of volumes pending return to owner.

INIT_SUM INTEGER Sum of volumes pending initialize.

ERASE_SUM INTEGER Sum of volumes pending erase.

NOTIFY_SUM INTEGER Sum of volumes pending notify.

ABEND_SUM INTEGER Sum of volumes with data set closed by abend.

IGNORE_EXPDT_SUM INTEGER Sum of volumes that ignored EXPDT.

SCRATCH_IMMED_SUM INTEGER Sum of volumes scratch immediate.

VOLUME_MAX INTEGER Maximum of volumes.

VOLUME_NONEXP_MAX INTEGER Maximum of volumes not expired.

AGE_CREATE_MAX INTEGER Maximum of days since creation.

AGE_CHANGE_MAX INTEGER Maximum of days since change.

EXPDT_DAYS_MAX INTEGER Maximum of days until expedite for nonexpiredvolumes.

COMPACT_MAX INTEGER Maximum of volumes using compaction.

DATASETS_MAX INTEGER Maximum of data sets on volumes.

TAPE_KB_MAX FLOAT Maximum of kilobytes used on volumes.

USE_COUNT_MAX INTEGER Maximum of use count on volumes.

AGE_READ_MAX INTEGER Maximum of days since last read.

AGE_WRITE_MAX INTEGER Maximum of days since last write.

PEND_REL_MAX INTEGER Maximum of volumes pending release.

RETAIN_VRS_MAX INTEGER Maximum of volumes retained by VRS.

LOAN_MAX INTEGER Maximum of volumes on loan.

OPEN_MAX INTEGER Maximum of volumes open.

REC_O_C_EOV_MAX INTEGER Maximum of volumes recorded by O / C / EOV.

PARMLIB_RTPD_MAX INTEGER Maximum of volumes that used the PARMLIB defaultRETPD.

PP_TAPE_MAX INTEGER Maximum of volumes for program products.

BLP_MAX INTEGER Maximum of volumes last written BLP.

VM_USE_MAX INTEGER Maximum of volumes for VM use.

MVS_USE_MAX INTEGER Maximum of volumes for MVS use.

TEMP_RERR_MAX INTEGER Maximum of temporary read errors.

TEMP_WERR_MAX INTEGER Maximum of temporary write errors.

PERM_RERR_MAX INTEGER Maximum of permanent read errors.

PERM_WERR_MAX INTEGER Maximum of permanent write errors.

RETURN_SCRTC_MAX INTEGER Maximum of volumes pending scratch.

REPLACE_MAX INTEGER Maximum of volumes pending replace.

RETURN_OWNER_MAX INTEGER Maximum of volumes pending return to owner.

INIT_MAX INTEGER Maximum of volumes pending initialize.

ERASE_MAX INTEGER Maximum of volumes pending erase.

DFSMS data tables



NOTIFY_MAX INTEGER Maximum of volumes pending notify.

ABEND_MAX INTEGER Maximum of volumes with data set closed by abend.

IGNORE_EXPDT_MAX INTEGER Maximum of volumes that ignored EXPDT.

SCRATCH_IMMED_MAX INTEGER Maximum of volumes scratch immediate.

DFSMS data tables


Lookup tableThis section describes the lookup table specific to the DFSMS/RMM component.

DFSMS_DS_OWNERThis lookup table groups data sets into user-defined categories such as projects.The grouping is based on your local naming standard used for the first threequalifiers of the data set name.



DS_QUALIFIER1 k CHAR(8) First-level qualifier. This is the first-level name of the data set to berelated to the project name.

DS_QUALIFIER2 k CHAR(8) Second-level qualifier. This is the second-level name of the data setto be related to the project name.

DS_QUALIFIER3 k CHAR(8) Third-level qualifier. This is the third-level name of the data set tobe related to the project name.

DESCRIPTION VARCHAR(30) Descriptive text. This is used for documentation purposes only.

PROJECT CHAR(8) Name of the project to which the data set is related.

Example of table contentsMVSSYSTEM DS DS DS

ID QUALIFIER1 QUALIFIER2 QUALIFIER3 PROJECT DESCRIPTION------ ----------- ----------- ----------- -------- -----------MVS1 A% % % PROJ1MVS1 B% % % PROJ2MVS1 C% % % PROJ3MVS1 D% % % PROJ4

DFSMS lookup tables


DFSMS lookup tables


Chapter 18. Reports

The DFSMS/RMM component provides these reports:v DFRMM Location Statistics, Detail reportv DFRMM Error Statistics, Detail reportv DFRMM Volumes by Location, Monthly Trend reportv DFRMM Project Statistics, Detail reportv DFRMM Space Usage by Storage Group, Daily Trend report

DFRMM report descriptionsThis section describes the reports provided with the DFSMS/RMM component ofthe System Performance feature.

277

DFRMM Location Statistics, Detail reportThis report shows detailed location statistics.


Report ID DFRMM01

Report group DFRMM reports

Source DFRMM_VOLUME_D

Attributes DFRMM, Location, Volume, Tape, Daily, Detail

Variables From_date, To_date


Date The collect date.

Location The name of the location.

Volume Status The status of the volume.

Volume count The number of volumes.

Volume NONEXP count The number of non-expired volumes.

Creation age avg The average of volumes created for the day.Calculated as SUM(FLOAT(AGE_CREATE_SUM))/ SUM(VOLUME_COUNT)

Change age avg The average of volumes changed for the day.Calculated as SUM(FLOAT(AGE_CHANGE_SUM))/ SUM(VOLUME_COUNT)

Expire days avg The average of expired volumes for the day.

Dataset count The number of data sets.

Tape KB sum Total amount of tape usage, in kilobytes.

DFRMM Location statistics, DetailFrom date: ’2000-02-09’ to date: ’2000-02-09’

Volume Creation Change Expire TapeVolume Volume NONEXP age age days Dataset KB

Date Location Status count count avg avg avg count sum---------- -------- -------- ------ ------ -------- -------- -------- -------- ----------2000-02-09 SHELF ENTRY 2 0 1295.5 521.5 0.0 1 11656162000-02-09 SHELF MASTER 2 0 925.0 83.5 0.0 2 2867142000-02-09 SHELF SCRATCH 1007 0 596.7 447.5 0.0 1130 367854692000-02-09 TSSMLIB1 MASTER 412 0 1700.7 141.1 0.0 454 2820060912000-02-09 TSSMLIB1 SCRATCH 106 0 1187.7 402.8 0.0 231 175178022000-02-09 TSSMLIB1 USER 326 0 573.9 511.0 0.0 1917 30089257

Tivoli Decision Support for OS/390 Report: DFRMM01

Figure 82. Example of a DFRMM Location Statistics, Detail report

DFSMS/RMM reports


DFRMM Error Statistics, Detail reportThis report shows error statistics based on the date, the recording density, and thedrive that was used.


Report ID DFRMM02


Source DFRMM_VOLUME_D

Attributes DFRMM, Error, Density, Drive, Volume, Tape, Daily, Detail



Date The collect date.

Density The recording density.

Last used drive The drive that was used.

Volume count The total number of volumes.

Temp read error The number of temporary read errors.

Temp write error The number of temporary write errors.

Perm read error The number of permanent read errors.

Perm write error The number of permanent write errors.

DFRMM Error statistics, DetailFrom date: ’2000-02-09’ to date: ’2000-02-09’

Last Temp Temp Perm Permused Volume read write read write

Date Density drive count error error error error---------- -------- -------- ------ ------ ------ ------ ------2000-02-09 * 913 0 0 0 02000-02-09 * 0690 9 0 0 0 02000-02-09 IDRC 9 0 0 0 02000-02-09 IDRC 0682 1 0 0 0 02000-02-09 IDRC 0683 1 0 0 0 02000-02-09 IDRC 0685 1 0 0 0 02000-02-09 IDRC 0690 516 27 1491 0 12000-02-09 IDRC 0691 151 0 381 0 22000-02-09 3480 47 0 0 0 02000-02-09 3480 0684 2 0 0 0 0


Figure 83. Example of a DFRMM Error Statistics, Detail report

DFSMS/RMM reports


DFRMM Volumes by Location, Monthly Trend reportThis report shows the monthly trend for volumes by location.


Report ID DFRMM03


Source DFRMM_VOLUME_M

Attributes DFRMM, Volume, Tape, Location, Trend, Monthly

Variables From_date, To_date, Volume_status


Date The date of the measurement, rounded to the firstday of the month.

Volumes The number of volumes for the location.

Figure 84. Example of a DFRMM Volumes by Location, Monthly Trend report

DFSMS/RMM reports


DFRMM Project Statistics, Detail reportThis report shows detailed statistics for projects.


Report ID DFRMM04


Source DFRMM_DATASET_D

Attributes DFRMM, Project, Volume, Tape, SMS, Daily, Detail



Project The project group from the DFSMS_DS_OWNERlookup table.

Mgmt class The name of the management class.

Storage class The name of the storage class.

Storage group The name of the storage group.

Data class The name of the data class.

Dataset count The total number of data sets for the project.

Dataset KB sum The total size of the data sets, in kilobytes.

DFRMM Project statistics, DetailDate: 2000-02-16 SystemID ’TSM1 ’

DatasetMgmt Storage Storage Data Dataset KB

Project class class group class count sum-------- -------- -------- -------- -------- -------- ----------ADSMD 4 828982ADSMP STD LIBRARY LIBRARY1 TAPE2C 223 217919915ARGOS 2 161860BACKUP 58 9630414BOCSMF 5 1926556CART 1 13152CLOTHD 3 23841CPP 125 0CSDUTL 5 2970925DAIWA 1 29624


Figure 85. Example of a DFRMM Project Statistics, Detail report

DFSMS/RMM reports


DFRMM Space Usage by Storage Group, Daily Trend reportThis report shows the daily space usage by storage group.


Report ID DFRMM05


Source DFRMM_DATASET_D

Attributes DFRMM, Volume, Tape, SMS, Trend, Daily




Storage Group The name of the storage group.

Megabytes The number of megabytes used by the storagegroup.

Figure 86. Example of a DFRMM Space Usage by Storage Group, Daily Trend report

DFSMS/RMM reports


Part 6. MVS component

Chapter 19. Customization . . . . . . . . 287Make input data available . . . . . . . . . 287Review the DRLJCOLL job . . . . . . . . . 287Update lookup tables. . . . . . . . . . . 287

Update MVS_ABEND_CODE table . . . . . 288Update MVS_MIPS_T table. . . . . . . . 288Update MVS_PRINTER_LOC table . . . . . 288Update MVS_SYSPLEX table . . . . . . . 289Update MVS_WORKLOAD_TYPE table . . . 289Run DRLEMWLT utility program . . . . . 290Update MVS_WORKLOAD2_TYPE table . . . 291Update USER_GROUP table . . . . . . . 292Update control tables . . . . . . . . . . 292


Chapter 21. Log and record definitions . . . . 297Record procedures. . . . . . . . . . . . 300

Chapter 22. Data tables, views, and lookuptables . . . . . . . . . . . . . . . 303Data tables . . . . . . . . . . . . . . 303

MVS_ACCNT_PGM_T . . . . . . . . . 303MVS_ACCNT23_PGM_T . . . . . . . . 305MVS_ADDRDISTR_H, _D, _M . . . . . . 306MVS_ADDRSPACE_T,_D, _M . . . . . . . 311MVS_ADDRSPACE_T . . . . . . . . . 317MVS_COMPCODE_D, _M . . . . . . . . 324MVS_ENCLAVE_H, _D, _M . . . . . . . 325MVS_GOAL_ACT_D, _M . . . . . . . . 326MVS_IPL_T . . . . . . . . . . . . . 328MVS_LPAR_D, _M . . . . . . . . . . 329MVS_MOUNT_D, _M . . . . . . . . . 332MVS_OAM_CARTR_D . . . . . . . . . 333MVS_OAM_CARTR_T . . . . . . . . . 334MVS_OAM_DRVVARY_T . . . . . . . . 335MVS_OAM_LIBVARY_T. . . . . . . . . 336MVS_OAM_OSMC_D, _M . . . . . . . . 337MVS_OAM_OSREQ_T . . . . . . . . . 339MVS_OAM_RWD_D, _M . . . . . . . . 340MVS_OAM_TAPDMNT_D, _M . . . . . . 341MVS_OAM_TAPERWD_D, _M . . . . . . 342MVS_OMVSADDR_T . . . . . . . . . 343MVS_OMVSADIS_T . . . . . . . . . . 345MVS_PRINTER_D, _M . . . . . . . . . 347MVS_PROGRAM_M . . . . . . . . . . 349MVS_SYSTEM_H, _D, _M . . . . . . . . 350MVS_TAPE_M . . . . . . . . . . . . 353MVS_VTS_CONF . . . . . . . . . . . 354MVS_VTS_H, _D, _M . . . . . . . . . 355MVS_VTS_ACTDATA_H . . . . . . . . 361MVS_VTS_PLCY_MGT_H . . . . . . . . 362MVS_VTS_POOLS_H. . . . . . . . . . 364MVS_VTS_MEDIA_H . . . . . . . . . 365

MVS_WORKLOAD_H, _D, _M . . . . . . 367MVS_WORKLOAD2_H, _D, _M . . . . . . 370

Views . . . . . . . . . . . . . . . . 373MVS_LPAR_DV . . . . . . . . . . . 373MVS_LPAR_MV . . . . . . . . . . . 375MVS_RESOURCE_HV . . . . . . . . . 377MVS_RESOURCE_DV . . . . . . . . . 378MVS_RESOURCE_MV . . . . . . . . . 379MVS_WORKLOAD_HV1 . . . . . . . . 380MVS_WORKLOAD_HV2 . . . . . . . . 380MVS_WORKLOAD_HV3 . . . . . . . . 381MVS_WORKLOAD_HV4 . . . . . . . . 381MVS_WORKLOAD_DV1 . . . . . . . . 382MVS_WORKLOAD_DV2 . . . . . . . . 383MVS_WORKLOAD_DV3 . . . . . . . . 384MVS_WORKLOAD_DV4 . . . . . . . . 385MVS_WORKLOAD_MV1 . . . . . . . . 386MVS_WORKLOAD_MV2 . . . . . . . . 387MVS_WORKLOAD_MV3 . . . . . . . . 388MVS_WORKLOAD_MV4 . . . . . . . . 389MVS_WORKLOAD2_HV2 . . . . . . . . 390MVS_WORKLOAD2_HV4 . . . . . . . . 392MVS_WORKLOAD2_DV2 . . . . . . . . 393MVS_WORKLOAD2_DV4 . . . . . . . . 394MVS_WORKLOAD2_MV2 . . . . . . . . 395MVS_WORKLOAD2_MV4 . . . . . . . . 396

Lookup tables . . . . . . . . . . . . . 397MVS_ABEND_CODE. . . . . . . . . . 397MVS_MIPS_T . . . . . . . . . . . . 399MVS_PRINTER_LOC. . . . . . . . . . 400MVS_SYSPLEX . . . . . . . . . . . . 401MVS_WORKLOAD_TYPE . . . . . . . . 402MVS_WORKLOAD2_TYPE. . . . . . . . 403

Chapter 23. Reports . . . . . . . . . . 405MVS problem reports. . . . . . . . . . . 408

MVS Exceptions, Daily report . . . . . . . 408MVS No of System Abends by Abend Code,Monthly report . . . . . . . . . . . . 409MVS No of User Abends by Abend Code,Monthly report . . . . . . . . . . . . 410MVS Percent Abended Jobs by User Group,Monthly report . . . . . . . . . . . . 411MVS No of Canceled Batch Jobs by User Group,Daily report . . . . . . . . . . . . . 412MVS Abended Jobs by User Group, Daily report 413

MVS overview reports . . . . . . . . . . 414MVS System Overview, Monthly Trend report 415MVS Average No of Address Spaces, MonthlyTrend report . . . . . . . . . . . . . 417MVS Activity by User Group, Daily/MonthlyOverview report . . . . . . . . . . . 418MVS Activity for a User Group, Daily Trendreport . . . . . . . . . . . . . . . 419MVS Users Swapped Out and Ready, DailyProfile report . . . . . . . . . . . . 420

283

||

||||||||

||

MVS Workload by Workload Type, MonthlyTrend report . . . . . . . . . . . . . 421MVS Sysplex Overview, Monthly Trend report 423MVS Availability by Sysplex, Monthly Trendreport . . . . . . . . . . . . . . . 424MVS Workload for a Resource Group,Daily/Monthly Trend report . . . . . . . 426MVS Workload by Resource Group,Daily/Monthly Overview report . . . . . . 428MVS Response (Goal in %), Daily/MonthlyTrend report . . . . . . . . . . . . . 430MVS Response (Goal in %), Daily/MonthlyOverview report . . . . . . . . . . . 432MVS Response (Goal in sec), Daily/MonthlyTrend report . . . . . . . . . . . . . 434MVS Response (Goal in sec), Daily/MonthlyOverview report . . . . . . . . . . . 435MVS Exec Velocity (Goal in %), Daily/MonthlyTrend report . . . . . . . . . . . . . 436MVS Exec Velocity (Goal in %), Daily/MonthlyOverview report . . . . . . . . . . . 437MVS Response Time Distribution,Daily/Monthly Overview report . . . . . . 439

TSO reports . . . . . . . . . . . . . . 441MVS TSO Response Time by Workload, DailyProfile report . . . . . . . . . . . . 441MVS TSO Response Time by Workload,Daily/Monthly Trend report . . . . . . . 443MVS TSO Response Time, Peak Hour, DailyTrend report . . . . . . . . . . . . . 444MVS Number of TSO Users, Daily Profile report 445MVS TSO Transactions by Workload, DailyProfile report . . . . . . . . . . . . 446MVS TSO Transactions by Workload,Daily/Monthly Trend report . . . . . . . 447MVS TSO Transactions, Peak Hour, Daily Trendreport . . . . . . . . . . . . . . . 448

Summary job reports . . . . . . . . . . . 449MVS Job Statistics by User Group, MonthlyOverview report . . . . . . . . . . . 449MVS Job Statistics for a User Group, DailyTrend report . . . . . . . . . . . . . 450MVS Number of Jobs with Tape Mounts, DailyTrend report . . . . . . . . . . . . . 451MVS Job Statistics by Period and User Group,Daily report . . . . . . . . . . . . . 452

Detailed job reports . . . . . . . . . . . 453MVS Jobs with RACF S913 Abends, Daily report 453MVS Jobs with Input Queue Time > 10 Min,Daily report . . . . . . . . . . . . . 454MVS Jobs with Tape, Daily report . . . . . 455

Program reports . . . . . . . . . . . . 456MVS Most CPU Consuming Programs, MonthlyOverview report . . . . . . . . . . . 456MVS Most I/O Intensive Programs, MonthlyOverview report . . . . . . . . . . . 458MVS Most CPU Losing Programs, MonthlyOverview report . . . . . . . . . . . 460MVS CPU Usage by Job Account Field andProgram, Daily report . . . . . . . . . 461MVS Interval Account Statistics, Detail report 463

IPL reports . . . . . . . . . . . . . . 465MVS Number of IPLs, Daily Trend report . . . 465MVS IPLs by Reason Code, Daily report . . . 466

Processor reports . . . . . . . . . . . . 467MVS CPU Load by Period, Daily/MonthlyTrend report . . . . . . . . . . . . . 467MVS CPU Load by Workload Type,Daily/Monthly Trend report . . . . . . . 469MVS CPU Load by Workload Type, Peak Hour,Daily report . . . . . . . . . . . . . 471MVS CPU Load by Workload Type, DailyProfile report . . . . . . . . . . . . 473MVS Average and Maximum CPU Load, DailyProfile report . . . . . . . . . . . . 474MVS CPU Load by LPAR, Daily/Monthly Trendreport . . . . . . . . . . . . . . . 476MVS MIPS for System ID, Hourly list . . . . 478MVS MIPS for System ID List, Daily Trend . . 480MVS MIPS for System ID List, Monthly Trend 482MVS CPU Load by LPAR, Monthly Trend perMIPS . . . . . . . . . . . . . . . 484MVS CPU Load by LPAR, Daily Trend perMIPS . . . . . . . . . . . . . . . 486

Storage reports . . . . . . . . . . . . . 488MVS Available CS, in Megabytes, Daily Profilereport . . . . . . . . . . . . . . . 489MVS CS by Workload Type, Peak Hour, DailyTrend report . . . . . . . . . . . . . 490MVS ES by Workload Type, Peak Hour, DailyTrend report . . . . . . . . . . . . . 492MVS Storage by Workload Type, Peak Hour,Daily report . . . . . . . . . . . . . 494MVS CS by Workload Type, Monthly Trendreport . . . . . . . . . . . . . . . 496MVS ES by Workload Type, Monthly Trendreport . . . . . . . . . . . . . . . 498MVS Storage by Workload Type, Monthly Trendreport . . . . . . . . . . . . . . . 500MVS CS by Type, Peak Hour, Daily Trendreport . . . . . . . . . . . . . . . 502MVS ES by Type, Peak Hour, Daily Trend report 504MVS Central Storage by Type, Monthly Trendreport . . . . . . . . . . . . . . . 506MVS Expanded Storage by Type, Monthly Trendreport . . . . . . . . . . . . . . . 508

Paging reports . . . . . . . . . . . . . 510MVS Paging by Subsystem, Daily Trend report 510MVS Paging Rates, Daily Trend report . . . . 512

Device reports . . . . . . . . . . . . . 513MVS DASD I/O by User Group, MonthlyOverview report . . . . . . . . . . . 513MVS I/O Rates by User Group, Peak Hour,Daily report . . . . . . . . . . . . . 514MVS Tape I/O by User Group, MonthlyOverview report . . . . . . . . . . . 515MVS Tape Demounts/MVS System, MonthlyOverview report . . . . . . . . . . . 516MVS Tape Errors by Device, Monthly Overviewreport . . . . . . . . . . . . . . . 517MVS Tape Errors by Volume, MonthlyOverview report . . . . . . . . . . . 518


||||||||||||

MVS MAGSTAR VTS Configuration report . . 519MVS MAGSTAR VTS Physical Drive MountDaily report . . . . . . . . . . . . . 521MVS MAGSTAR VTS Virtual Drive MountDaily report . . . . . . . . . . . . . 523MVS MAGSTAR VTS Utilization Daily report 525

Printer reports . . . . . . . . . . . . . 527MVS Printer Activity, Monthly Overview report 527MVS Print Activity by User Group, MonthlyOverview report . . . . . . . . . . . 529MVS Printer Forms Usage, Monthly Overviewreport . . . . . . . . . . . . . . . 531

OAM reports . . . . . . . . . . . . . 532OSREQ Function Invocation Statistics, Detailreport . . . . . . . . . . . . . . . 532OAM/OSMC Activities Statistics, Daily report 533OAM/OSMC Activities Statistics, Monthlyreport . . . . . . . . . . . . . . . 537LCS Opt Disk Volume R/W/D Statistics, Detailreport . . . . . . . . . . . . . . . 541LCS Opt Disk Volume R/W/D Statistics, Dailyreport . . . . . . . . . . . . . . . 543LCS Optical R/W/Log D/Phys D Reqs, Dailyreport . . . . . . . . . . . . . . . 545LCS Optical R/W/Log D/Phys D Reqs,Monthly report . . . . . . . . . . . . 546LCS Tape R/W/Log D Requests, Daily report 547LCS Tape R/W/Log D Requests, Monthlyreport . . . . . . . . . . . . . . . 548OAM Tape Vol R/W Stats at Demount, Dailyreport . . . . . . . . . . . . . . . 549OAM Tape Vol R/W Stats at Demount, Monthlyreport . . . . . . . . . . . . . . . 551

OpenEdition reports . . . . . . . . . . . 553MVS OpenEdition CPU Usage by Group, Dailyreport . . . . . . . . . . . . . . . 553MVS OpenEdition I/O Activity by Group, Dailyreport . . . . . . . . . . . . . . . 554MVS OpenEdition File System Lookups byGroup, Daily report . . . . . . . . . . 556MVS OpenEdition Child Process Listing for Jobreport . . . . . . . . . . . . . . . 558

Part 6. MVS component 285


Before you can use the MVS component to collect data and create useful reports,you must customize and test the installation. This chapter describes the steps youmust perform to customize the MVS component:1. Make input data available.2. Review the DRLJCOLL job.3. Update lookup tables.

Make input data availableFirst, ensure that the appropriate SMF record types are not suppressed by SMF orany of its exits. For example, RMF monitor I must be active to produce SMF type70, 71, and 72 records. See “Log and record definitions” for a complete list of theSMF records used by this component.

If you want data collected into the MVS_ADDRDISTR_x tables, you must specifyinterval recording. You can specify interval recording for only one subsystem, suchas, started tasks (STC). Here, only started tasks will be recorded in theMVS_ADDRDISTR_x tables.

You must associate subsystem names with performance group numbers in theIEAICSxx member. You can use the subsystem name to select batch, TSO, orstarted tasks in a number of MVS component reports. If you do not specifysubsystem IDs in the IEAICSxx member, the SUBSYSTEM_ID column in theMVS_WORKLOAD_x tables will be blank.

For MVS 5.1 and later, WORKLOAD_x tables are used only in compatibility mode.


Update lookup tablesThe MVS component uses several lookup tables when storing data in the TivoliDecision Support for OS/390 database. You must update the lookup tables toinclude parameters specific to your installation.



MVS_ABEND_CODE Converts systemabend codes todescriptions.

ABEND_CODE EXPLANATION

MVS_MIPS_T This table associatesMVS system IDs andCPUs model with anumber of MIPS

MVS_SYSTEM_IDCPU_MODEL_NOCPU_SUB_MODEL

MIPS DESCRIPTIONS

287

|


MVS_PRINTER_LOC Contains the locationof each printer.

MVS_SYSTEM_IDPRINTER_NAME

PRINTER_LOCATION

MVS_SYSPLEX Associates MVSsystem IDs andsystem names with asysplex name and adescription.

MVS_SYSTEM_IDSYSTEM_NAME

DESCRIPTIONSYSPLEX_NAME

MVS_WORKLOAD_TYPE Convertsperformance groupsand periods intoworkload types. Italso contains theresponse-timeobjectives for theworkload types.

MVS_SYSTEM_IDPERF_GROUP_NOPERF_GROUP_PERIODDOMAIN

DESCRIPTIONRESPONSE_TIME_OBJWORKLOAD_TYPE

MVS_WORKLOAD2_TYPE Converts MVSworkload groups andservice classes toworkload types.

MVS_SYSTEM_IDWORKLOAD_GROUPSERVICE_CLASSSERV_CLASS_PERIOD

DESCRIPTIONWORKLOAD_TYPE

The MVS component uses the USER_GROUP common lookup table. Thecomponent also uses the DAY_OF_WEEK, PERIOD_PLAN, SCHEDULE, andSPECIAL_DAY control tables. Check these common tables and update them asneeded.

Refer to the Administration Guide for information on the common lookup tables andthe control tables.

For information on updating the lookup tables using the administration dialog, see“Updating lookup tables” on page 11.

Update MVS_ABEND_CODE tableThis lookup table converts the most common system abend codes to descriptionsthat you can use when you create reports using the MVS_ADDRSPACE_T andMVS_COMPCODE_x tables. This lookup table initially contains a number ofsystem abend codes (see “MVS_ABEND_CODE” on page 397). You can add moreabend codes using SQL INSERT statements.

Update MVS_MIPS_T tableThis lookup table contains the MIPS information and must be updated with correctinformation about the machine. The lookup table associates MVS System IDs andCPU Model with a number of MIPS for the specific machine-processors. MIPS isthe unit commonly used to give the rate at which a processor performsinstructions. It is used as the benchmark to compare different machines or models.The information about MIPS is machine model-specific to all models of themachine and can be found in the technical documentation for the machine.

Update MVS_PRINTER_LOC tableThis table is used to group printer names into locations. Grouping lets youproduce printer statistics by locations (for example, for different cities).

For more information on this lookup table, see “MVS_PRINTER_LOC” onpage 400.

MVS customization


|

|||||||

Update MVS_SYSPLEX tableThe MVS_SYSPLEX lookup table converts MVS_SYSTEM_ID and/orSYSTEM_NAME to SYSPLEX_NAME. You need this table because some SMFrecords do not contain the name of the sysplex. MVS_SYSTEM_ID andSYSTEM_NAME can contain global search characters.

For a complete description of the lookup table and an example of its contents, see“MVS_SYSPLEX” on page 401.

Update MVS_WORKLOAD_TYPE tableThis lookup table converts the MVS performance group numbers and performancegroup periods, found in SMF type 30 and type 72 (subtypes 1 and 2) records, intomeaningful mnemonics designating the workload type. This lets you combinemultiple performance groups and performance group periods into one workloadtype. This mapping technique gives you three levels of detail; performance group,performance period, and workload type.

Both the MVS component and the MVS performance management component usethis lookup table. They do not use the table in exactly the same way. The minordifferences are shown here.

Note: The MVS component uses this lookup table for processing only SMF type 72subtype 1 records.

The MVS_WORKLOAD_TYPE lookup table contains these columns:

MVS_SYSTEM_IDThe actual SMF system ID. The rest of the information applies only to thatsystem. A percent sign (%) in this field matches any system ID.

PERF_GROUP_NOThe 3-character performance group number for this workload type.

PERF_GROUP_PERIODThe 1-character performance group period for this performance groupnumber.

SMF type 30 records do not include data on each performance groupperiod for a performance group number. SMF type 72 subtype 1 recordscontain data for the performance group periods. In the default tablesupplied, performance group period 0 is used for all SMF type 30 records.SMF type 30 records do not report on performance group periods. TheMVS performance management component uses PG period 0 whentranslating PGN in SMF 30 to workload type. SMF type 72 subtype 1records contains data for PG periods. So, for TSO work, you may havethese workload types defined:

Workload type PGN PG period Description

TSO 2 0 TSO (from type 30 records)

TSOS 2 1 TSO simple (from type 72 records)

TSOC 2 % TSO complex — not period 1 (from type 72records)

DOMAINThe 3-character domain number for this performance group number. Thisis useful in differentiating between TSO trivial and complex commands.

MVS customization


Note: The MVS component does not use the DOMAIN value.

WORKLOAD_TYPEThe 8-character workload type with which to associate this performancegroup number, performance group period, and domain.

RESP_TIME_OBJThe response-time objective for this workload type. This is a 4-decimalvalue. For example, 0.30 indicates a 0.3-second response time.

Note: The MVS performance management component does not use theRESP_TIME_OBJ value.

DESCRIPTIONThis field lets you document more information about the workload type.This field serves no function within Tivoli Decision Support for OS/390.

For a complete description of the lookup table and an example of its contents, see“MVS_WORKLOAD_TYPE” on page 402.

Run DRLEMWLT utility programTivoli Decision Support for OS/390 provides a utility program that helps youinitialize the MVS_WORKLOAD_TYPE lookup table. The input is taken from theICS/IPS members on SYS1.PARMLIB. The performance group and domainnumbers are extracted and formatted to DB2 update statements, which are writtento a data set or a PDS member. You must then edit the data and assign workloadtypes to the different performance groups before the MVS_WORKLOAD_TYPEtable can be initialized.

To run the utility program, follow these steps:1. Complete the JCL (job statement and data set name) for job DRLJMWL1. This

job reads the IEAICS00 and IEAIPS00 members on SYS1.PARMLIB. The jobcreates SQL INSERT statements to initialize the MVS_WORKLOAD_TYPElookup table. DRLEMWLT accepts these parameters:

SYSTEM_IDThe MVS system ID that the IEAICS00 and IEAIPS00 members belongto.

PREFIXThe prefix of the Tivoli Decision Support for OS/390 table definitions(the default is DRL).

2. Manually edit the output data set from step 1. Assign names to the workloadtypes you want Tivoli Decision Support for OS/390 to report on. Try to limitthe number of workload names. Having fewer workload types improves TivoliDecision Support for OS/390 collect and report performance. The program instep 1 assigns default workload names to all performance group numbers,periods, and domains defined in the IEAICS and IEAIPS. The program in step1 assigns these workload names as defaults:

SYSTEMUsed for performance group number 0.

R-nnnnUsed for report groups, where nnnn is the report performance groupnumber.

MVS customization


C-nnn-pUsed for control groups, where nnn is the performance group numberand p is the period.

C-nnn-0Created for all performance group numbers. It is used by tables basedon SMF type 30 records.

Change these names to your own workload names. Save the edited data set inyour own library for later reference.

3. Complete the JCL (job statement and data set name) for job DRLJMWL2. Checkand, if necessary, change the DB2 SYSTEM name and the Tivoli DecisionSupport for OS/390 SYSPREFIX on the EXEC statement. Then run the job toexecute the SQL statements and update the MVS_WORKLOAD_TYPE lookuptable.

Repeat these steps for all MVS systems you are going to collect data and reportfrom.

Update MVS_WORKLOAD2_TYPE tableThis lookup table converts the MVS workload group, service class, and serviceclass periods, found in SMF type 30 and type 72 (subtypes 3) records, intomeaningful mnemonics designating the workload type. This lets you combinemultiple service classes and service class periods into one workload type. Thismapping technique gives you four levels of detail; workload group, service class,service class periods, and workload type.

Both the MVS component and the MVS performance management component usethis lookup table. They do not use the table in exactly the same way. The minordifferences are shown here.

Note: The MVS component uses this lookup table for processing only SMF type 72subtype 3 records.

The MVS_WORKLOAD2_TYPE lookup table contains these columns:

MVS_SYSTEM_IDMVS system ID. This can contain global search characters.

WORKLOAD_GROUPName of the workload group. This can contain global search characters.

SERVICE_CLASSName of the service class. This can contain global search characters.

SERV_CLASS_PERIODService class period for the service class. This can contain global searchcharacters; usually %, except for short TSO transactions.

SMF type 30 records do not include data on each service class (SC) periodfor a service class. SMF type 72 subtype 3 records contain data for theservice class periods. In the default table supplied, service class period 0 isused for all SMF type 30 records. SMF type 30 records do not report onservice class periods. The MVS performance management component usesSC period 0 when translating workload group and service class in SMF 30to workload type. SMF type 72 subtype 3 records contain data for SCperiods. So, for TSO work, you may have these workload types defined:

MVS customization


Workload typeWorkloadgroup SC SC period Description

TSO TSO % 0 TSO (from type 30 records)

TSOS TSO % 1 TSO simple (from type 72records)

TSOC TSO % % TSO complex — not period1 (from type 72 records)

DESCRIPTIONThis field lets you document more information about the workload type.This field serves no function within Tivoli Decision Support for OS/390.

For a complete description of the lookup table and an example of its contents, see“MVS_WORKLOAD2_TYPE” on page 403.

Update USER_GROUP tableThis lookup table groups users into user groups. You can also assign division anddepartment names to the user groups. For a description of this lookup table and anexample of its contents, refer to the Administration Guide.

Update control tablesThe MVS component also uses these control tables when updating data tables:

DAY_OF_WEEKThis control table defines the day type for each day of the week.

PERIOD_PLANThis control table defines the partition of a day into periods (such asshifts).

SPECIAL_DAYThis control table defines the day type for special days (such as holidays).

Ensure that these control tables include the correct information. For descriptions ofthese control tables and examples of their contents, refer to the AdministrationGuide.

MVS customization



The MVS component collects records from the SMF data set and stores extractedand summarized data in the Tivoli Decision Support for OS/390 database. Thereporting function extracts data from the database and creates reports that yourequest through the Tivoli Decision Support for OS/390 reporting dialogs. You canuse the reports to perform detailed analysis of system performance and to identifyproblem areas in your system.

Figure 87 on page 294 shows an overview of the flow of data through the MVScomponent.

293

MVS

SMF log

SMF_000SMF_006SMF_007SMF_021SMF_025SMF_026SMF_030SMF_070SMF_071SMF_072_1SMF_072_3SMF_085SMF_090SMF_094SMF_094_2

Recorddefinitions

Recordprocedures

Recorddefinitions

DRL2S030DRL2S030ADRL2S30ODRL2S070

SMF_030_OMVS_XSMF_030_XSMF_030_2_3_XSMF_030_4_XSMF_070_X

Data tables

EXCEPTION_TMVS_ADDRDISTR_xMVS_ACCNT_PGM_TMVS_ACCNT23_PGM_TMVS_ADDRSPACE_xMVS_COMPCODE_xMVS_ENCLAVE_xMVS_GOAL_ACT_xMVS_IPL_TMVS_LPAR_xMVS_OAM_CARTR_xMVS_OAM_DRVVARY_TMVS_OAM_LIBVARY_TMVS_OAM_OSMC_xMVS_OAM_OSREQ_TMVS_OAM_RWD_xMVS_OAM_TAPDMNT_xMVS_OAM_TAPERWD_x

MVS_OMVSADIS_TMVS_OMVSADDR_TMVS_MOUNT_xMVS_PRINTER_xMVS_PROGRAM_MMVS_SYSTEM_xMVS_TAPE_MMVS_VTS_xMVS_VTS_CONFMVS_VTS_ACTDATA_HMVS_VTS_MEDIA_HMVS_VTS_POOLS_HMVS_VTS_PLCY_MGT_HMVS_WORKLOAD_xMVS_WORKLOAD2_x


DAYS_OF_WEEKMVS_MIPS_TMVS_PRINTER_LOCMVS_SYSPLEXMVS_WORKLOAD_TYPEMVS_WORKLOAD2_TYPEPERIOD_PLANSPECIAL_DAYUSER_GROUP

Reports MVS_ABEND_CODEMVS_SYSPLEX


Collect

Figure 87. MVS component data flow

MVS data flow


|

|||

Lookup tablesWhen collecting SMF records, the MVS component uses update definitions todetermine which records and fields in the records to use when updating the tables.As it updates the tables, the component uses lookup tables to convert MVSperformance groups to workload names (for example, TSO or CICS). It also uses alookup table to specify the jobs and started tasks for which availability is to betracked. Figure 88 shows which data tables contain information from lookup tables.

Lookup tables Data tables

MVS_ABEND_CODE

MVS_PRINTER_LOC MVS_PRINTER_D

MVS_ACCNT_PGM_TMVS_ACCNT23_PGM_TMVS_ADDRSPACE_TMVS_COMPCODE_DMVS_PRINTER_DMVS_PROGRAM_M

MVS_SYSPLEX

MVS_SYSTEM_ID

MVS_SYSTEM_IDPRINTER_NAME

MVS_SYSTEM_IDPERF_GROUP_NOPERF_GROUP_PERIOD


SYSPLEX_NAME

PRINTER_LOCATION

MVS_WORKLOAD_TYPE

WORKLOAD_TYPE

WORKLOAD_TYPE

MVS_WORKLOAD_H

MVS_GOAL_ACT_DMVS_WORKLOAD2_H

MVS_WORKLOAD2_TYPE

Reports only

MVS_MIPS_T MVS_SYSTEM_H


CPU_BUSY_MIPS

MVS_MIPS_T MVS_LPAR_D


CPU_BUSY_MIPSMIPS_PER_LOG_CPMIPS_PER_LPARPHYS_PROC_LPAR

MIPS

MIPS


MVS data flow


The MVS component uses the RESPONSE_TIME_OBJ column in theMVS_WORKLOAD_TYPE table to determine if the EXCEPTION_T table should beupdated. The MVS component updates the EXCEPTION_T table when TSOresponse time is above the response-time objective.

The MVS component uses these control tables when updating all of the hourlytables:v DAY_OF_WEEKv PERIOD_PLANv SPECIAL_DAY

It uses the USER_GROUP common lookup table when updating theMVS_ADDRDISTR_H, MVS_ADDRSPACE_T, and MVS_PRINTER_D tables.

For information on the common lookup tables and control tables, refer to theAdministration Guide.

For more information about the data tables the component updates, and thelookup tables it uses, see Chapter 22, “Data tables, views, and lookup tables”, onpage 303.

MVS data flow



The MVS component collects records from the system management facilities (SMF)log. The MVS operating system writes records that contain information aboutconfiguration, paging activity, and workload. Job-related records includeinformation on the CPU time, SYSOUT activity, and data set activity of each jobstep, job, APPC/MVS transaction program, and TSO/E session.

The MVS component processes these records from the SMF log:


Tivoli DecisionSupport forOS/390 recorddefinition Description

0 SMF_000 IPL—MVS writes this record after every IPL ofthe system and includes the virtual and central(real) storage sizes and some of the SMF optionsin effect.

6 SMF_006 JES output writer—This record identifies theoutput writer by SYSOUT class and formnumber. It also identifies the job according to thejob log identification, JES2/JES3-assigned jobnumber, and user ID.

7 SMF_007 Data lost—This record tracks the number ofrecords lost when the SMF data sets and SMFbuffers become full and records are dumped.

21 SMF_021 Error statistics by volume—This record containsthe statistics for the entire volume during theperiod that the volume is mounted.

25 SMF_025 JES3 device allocation—This record contains theallocation-related information for each job thatcompletes JES3 converter/interpreter (C/I)processing.

26 SMF_026 JES2 job purge—This record identifies thejob-by-job identification, JES2-assigned jobnumber, and programmer’s name.

297



30 SMF_030 Common address space work—This recordcontains operation information such as the joband step start and end times, step CPU time,step termination status, number of records in DDDATA and DD * data sets processed by the stepand job, device allocation start time, problemprogram start time, and storage protect key. Therecord contains the number of page-ins,page-outs, swap-ins, and swap-outs for bothvirtual input output (VIO) and non-VIO datasets. The record contains information on thenumber of hiperspace page moves and themovement of pages between expanded storageand central (real) storage. This data can be usedin resource planning. Information is added toaccount for time spent in hiperspace processingon a step basis. The record contains an entry foreach data set defined by a DD statement ordynamic allocation. Each entry lists the deviceclass, unit type, device number, the executechannel program (EXCP) count, and deviceconnect time for the data set. The record alsocontains remote system data for each system thatexecuted work under a multisystem enclave.

30 2, 3 SMF_030_X This record contains a processor section that isadded to SMF type 30 extension records. Theseextension records are created if several EXCPsection lengths would exceed the maximumlength (only for MVS releases prior to 5.1). Thisrecord also contains enclave data as perSMF_030.

30 2, 3 SMF_030_2_3_X This record contains data from subtypes 2(activity since previous interval ended) and 3(activity for the last interval before steptermination) of SMF type 30 records with theaccounting fields that are lined up with the jobaccounting fields (SMF 30 subtype 1). This recordalso contains enclave data as per SMF_030.

30 4 SMF_030_4_X This record contains data from subtype 4 (steptotal) of SMF type 30 records with the stepaccounting fields that are lined up with the jobaccounting fields (SMF 30, subtype 1). Thisrecord also contains enclave data as perSMF_030.

30 2, 3, 4, 5 SMF_030_OMVS_XThis record contains data from subtypes 2, 3, 4,and 5. One record is built for each open MVSprocess section.

70 SMF_070 RMF CPU activity—MVS writes this record foreach measurement interval and when the sessionterminates. The record includes generalinformation on CPU use during the interval (forexample, wait time) and address space use.

MVS log and record definitions


||||||



70 SMF_070_X A subtype 20 record is built for each PR/SM™*partition. A subtype 10 record is built for eachprocessor section, and the associated PR/SMlogical processor data section and PR/SMpartition data section (subtype 10).

71 SMF_071 RMF paging activity—This record containsinformation about the demands made on thesystem paging facilities and the usage ofprocessor storage and auxiliary storage duringthe reporting interval.

72 1 SMF_072_1 Created by RMF if the workload activitymeasurements are activated.

72 3 SMF_072_3 Created by RMF monitor I if the workloadactivity measurements are activated and thesystem runs in goal mode.

85 SMF_085 Created by OAM to account OAM activityduring object support. These records provideOAM performance measurements capability atthe application programming interface level (theOSREQ macro interface).

90 SMF_090 System status—MVS creates this record foroperator tracking and reporting of reliabilitydata, and allows the installation to establishavailability statistics.

94 1 SMF_094 34xx Tape Library Dataserver report statistics.The system-managed tape library accumulatesstatistics over a period of one hour. Thesestatistics represent the activity of the IBM 34xxTape Library Dataserver that results from allhosts attached to the library.

At the end of the hour, the system calculatescomposite statistics about the activity of alldevices in the library and writes an SMF type 94record. The information in this record represents:

v Current information—the value of the statisticsat the point the record is written

v Summary of last hour information—statisticsover the most recent hour for which compositestatistics have been calculated.

The record also contains import/export statisticsand VTS enhanced library statistics.





94 2 SMF_094_2 The tape library accumulates statistics over aperiod of one hour. These statistics represent theactivity of the IBM Tape Library Dataserverresulting from all hosts attached to the library. Atthe end of the hour, the system calculatescomposite statistics about the activity of alldevices in the library and writes an SMF type 94record.

When FC 4001 is installed and Outboard PolicyManagement is enabled, a new SMF94 recordwill be recorded. The new record is an SMF94subtype 2, and will be recorded in addition tothe existing SMF94 subtype 1. The SMF94subtype 2 record is used to record Volume PoolStatistics.

The existing subtype 1 record is also changed.When FC 4001 is installed and Outboard PolicyManagement is enabled, some existing statisticswill not be reported. The unreported fields willcontain binary zero. Existing field SMF94HSF insubtype 1 records will contain the value 2 whenFC 4001 is installed and Outboard PolicyManagement is enabled.

Refer to MVS/ESA System Management Facilities for a detailed description of theSMF records.

Record proceduresThe MVS component processes some SMF records through record procedures. Therecord procedures add additional data needed to create meaningful reports.Figure 89 on page 301 lists the records affected by record procedures and theresulting records.



|||||||||||

|||||||

||||||||

The MVS component then stores data from the new records in tables in the TivoliDecision Support for OS/390 database.

SMF_030 SMF_070

DRL2S030(prior to MVS 5.1)

DRL2S070 DRL2S070

Adds a processor sectionto the SMF 30 extensionrecords (subtypes 2 and3) that are created ifthere are many EXCPsections whose lengthwould exceed themaximum length

Builds a recordfor each PR/SMpartition

Builds a recordfor each processorsection, and theassociated PR/SMlogical processordata section andPR/SM partitiondata section

SMF_030_x(subtypes 2 and 3 only)

SMF_070_X(subtype 20)

SMF_030_2_3_XSMF_030_4_X


Input record

Recordprocedure

Outputrecord

DRL2S30AReplaces activity sinceprevious interval endedaccounting fields (subtype 2),activity for the last intervalbefore step terminationaccounting step accountingfields (subtype 3) and stepaccounting fields (subtype 4)with job accounting fields(subtype 1)

DRL25300

Builds a record for eachOPENMVS process section

SMF_030_OMVS_X

Figure 89. Record procedures



Chapter 22. Data tables, views, and lookup tables

This chapter describes the data tables, views, and lookup tables used by the MVScomponent. For descriptions of common data tables, lookup tables, and controltables used by the System Performance feature, refer to the Administration Guide.

Data tablesThis section describes the data tables for the MVS component.

MVS_ACCNT_PGM_TThis table provides detailed statistics on programs used by jobs and started tasks.It contains data from SMF type 30, subtypes 4 records processed through a recordprocedure (DRL2S30A). It contains one row for each program, within each job,with job accounting fields and detailed resource utilization.

This table is updated by the MVS_SYSPLEX lookup table.


303


TIMESTAMP k TIMESTAMP Date and time when the initiator selected the step(program) of the job. From SMF30STD and SMF30SIT.

JOB_NAME k CHAR(8) Name of the job. From SMF30JBN.

CPU_TOTAL_SECONDS FLOAT Total amount of CPU time consumed for the program, inseconds. This is the sum of all valid CPU times.

JOB_ACCNT_FIELD_1 VARCHAR(8) First job accounting field. Extracted from the job level ofSMF30ACT by DRL2030A record procedure.

JOB_ACCNT_FIELD_2 VARCHAR(8) Second job accounting field. Extracted from the job level ofSMF30ACT by DRL2030A record procedure.

JOB_ACCNT_FIELD_3 VARCHAR(8) Third job accounting field. Extracted from the job level ofSMF30ACT by DRL2030A record procedure.

JOB_ACCNT_FIELD_4 VARCHAR(8) Fourth job accounting field. Extracted from the job level ofSMF30ACT by DRL2030A record procedure.

JOB_ID_NUM CHAR(8) Job identification number. From SMF30JNM.

JOB_ID_TIME TIMESTAMP Date and time the reader recognized job card. FromSMF30RSD and SMF30RST

MVS_SYSTEM_ID CHAR(4) MVS system ID. This is the SMF system ID. FromSMF30SID.

PROGRAM_NAME CHAR(8) Name of the program. From SMF30PGM.

STEP_NAME CHAR(8) Name of the step. From SMF30STM.

STEP_NUM INTEGER Number of the step. From SMF30STN.

SYSPLEX_NAME CHAR(8) This is the name of the sysplex. From SYSPLEX_NAME inthe MVS_SYSPLEX lookup table.

MVS data tables


MVS_ACCNT23_PGM_TThis table provides detailed statistics on programs used by jobs and started tasks.It contains data from SMF type 30 (subtypes 2,3) records processed through arecord procedure (DRL2S30A).




START_TIMESTAMP k TIMESTAMP Date and time when the initiator selected the step(program) of the job. From SMF30STD and SMF30SIT, if set.Otherwise, from end timestamp SMF30DTE andSMF30TME.

END_TIMESTAMP k TIMESTAMP Date and time when the initiator selected the step(program) of the job. From SMF30DTE and SMF30TME.

JOB_NAME k CHAR(8) Name of the job. From SMF30JBN.

CPU_TOTAL_SECONDS FLOAT Total amount of CPU time consumed for the program, inseconds. This is the sum of all valid CPU times.

INTERVAL_LENGTH FLOAT Interval length between start timestamp and end timestampin seconds.

JOB_ACCNT_FIELD1 VARCHAR(8) First job accounting field. Extracted from the job level ofSMF30ACT by DRL2030A record procedure.

JOB_ACCNT_FIELD2 VARCHAR(8) Second job accounting field. Extracted from the job level ofSMF30ACT by DRL2030A record procedure.

JOB_ACCNT_FIELD3 VARCHAR(8) Third job accounting field. Extracted from the job level ofSMF30ACT by DRL2030A record procedure.

JOB_ACCNT_FIELD4 VARCHAR(8) Fourth job accounting field. Extracted from the job level ofSMF30ACT by DRL2030A record procedure.

JOB_ID_NUM CHAR(8) Job identification number. From SMF30JNM.


PROGRAM_NAME CHAR(8) Name of the program. From SMF30PGM.


MVS data tables

Chapter 22. Data tables, views, and lookup tables 305

MVS_ADDRDISTR_H, _D, _MThese tables provide hourly, daily, and monthly statistics on address spaces. Theycontain data from SMF type 30, subtypes 2 and 3 records.

These tables are updated by the USER_GROUP lookup table.

The default retention periods for these tables are:MVS_ADDRDISTR_H 7 daysMVS_ADDRDISTR_D 30 daysMVS_ADDRDISTR_M 765 days


DATE k DATE Date when the activities occurred. For the _M table, this is thedate of the first day of the month. From (description)SMF30ISS and SMF30IET for GMT time. The UPDATEdefinition can be customized for local time by usingSMF30IDT and SMF30IST.

TIME k TIME Time (rounded down to the nearest hour) when the activitiesoccurred. It applies only to the _H table. From (description)SMF30ISS and SMF30IET for GMT time. The UPDATEdefinition can be customized for local time by usingSMF30IDT and SMF30IST.

PERIOD_NAME k CHAR(8) Name of the period. This is derived using fields SMF30SID,SMF30IDT, SMF30IST, SMF30DTE, and SMF30TME asparameters in the PERIOD function.

MVS_SYSTEM_ID k CHAR(4) MVS system ID. This is the SMF system ID. From SMF30SID.

SUBSYSTEM_ID k CHAR(4) Name of the subsystem. From SMF30WID.

USER_ID k CHAR(8) ID of the user for whom the activity is recorded. FromSMF30RUD.

USER_GROUP k CHAR(8) Name of the group that the user belongs to. FromGROUP_NAME in the USER_GROUP lookup table; if nomatch is found, this column gets its value from SMF30RUD.

For a description of the USER_GROUP lookup table, refer tothe Administration Guide.

BLOCKS_IN_AUX FLOAT Number of blocks that were paged in from auxiliary storage.This is the sum of SMF30KIA.

BLOCKS_IN_ES FLOAT Number of blocks that were paged in from expanded storage.This is the sum of SMF30KIE.

BLOCKS_OUT_AUX FLOAT Number of blocks that were paged out to auxiliary storage.This is the sum of SMF30KOA.

BLOCKS_OUT_ES FLOAT Number of blocks that were paged out to expanded storage.This is the sum of SMF30KOE.

BLOCKS_TRANSFERRED FLOAT Total number of blocks transferred. This is the accumulatedEXCP counts. This is the sum of SMF30TEP.

BYTES_RCV FLOAT Amount of data received by the transaction program, in bytes.This is the sum of SMF30DAR.

BYTES_SENT FLOAT Amount of data sent by the transaction program, in bytes.This is the sum of SMF30DAT.

CARDS_READ INTEGER Number of card-image records in DD DATA and DD * datasets read by the reader. This is the sum of SMF30INP.

MVS data tables



CONNECT_INVALID CHAR(1) Indicates that the device connect time (CONNECT_MSEC)might be incorrect. This is set to 1 if the device connect timemight be incorrect. This is the maximum of bit 0 inSMF30DCF.

CONNECT_MSEC FLOAT Total device connect time for the address space, inmilliseconds. This is the sum of SMF30TCN.

CONVERS_ACTIVE FLOAT Number of active conversations. This is the sum ofSMF30TAC.

CONVERS_ALLOC FLOAT Number of conversations allocated. This is the sum ofSMF30CNA.

CONVERS_TOT FLOAT Total number of conversations associated with the transactionprogram ID, both currently active and deallocated. This is thesum of SMF30CN.

CPU_ENQ_PROMOT_SEC FLOAT CPU time consumed for an address space or job whileenqueue promoted in seconds. Calculated as SUMSMF30CEP/1024.

CPU_HIPER_SECONDS FLOAT Processor time used to support data transfer to and from ahiperspace backed by expanded storage, in seconds.Calculated as the sum of SMF30HPT/100 for records wherebit 0 or bit 10 of SMF30TFL is 0.

CPU_INTR_SECONDS FLOAT Processor time used to process I/O interrupts, in seconds.Calculated as the sum of SMF30IIP/100 for records where bit0 or bit 9 of SMF30TFL is 0.

CPU_PAGE_SECONDS FLOAT Number of processor page seconds for the address space, inpage second units. Calculated as the sum of SMF30PSC*0.001.

CPU_RCT_SECONDS FLOAT Processor time used by the region control task, in seconds.Calculated as the sum of SMF30RCT/100 for records where bit0 or bit 11 of SMF30TFL is 0.

CPU_TOTAL_SECONDS FLOAT Total processor time, in seconds. This is the sum of all validprocessor times.

CS_FRAME_SECONDS FLOAT Active frame time for frames in central storage, in seconds.Calculated as the sum ofSMF30RES*SMF30PSC*1024/(SMF30CPT*10 000 000).

DASD_BLOCKS FLOAT Number of blocks transferred to and from disk devices. This isthe sum of SMF30BLK, where SMF30DEV = X'20'.

ENCLAVE_ACTIVE_SEC FLOAT Enclave transaction active time, in seconds. This is the sum ofSMF30ETA.

ENCLAVE_SECONDS FLOAT CPU time used by enclaves, in seconds. This value is alsoincluded in TCB_STEP_SECONDS. Calculated as the sum ofSMF30ENC/100 for records where bit 0 or bit 13 of SMF30TFLis 0.

ICSF_INSTRUCTIONS FLOAT Integrated Cryptographic Service Facility/MVS (ICSF/MVS)service count. This is the number of cryptographic instructionsexecuted on behalf of caller (within caller’s address space).Calculated as the sum of SMF30CSC.

INELIGIBLE_TIME_1 FLOAT Job ineligible for execution time, in seconds. The schedulingenvironment is not available. This is the sum of SMF30RQT.

INELIGIBLE_TIME_2 FLOAT Job ineligible for execution time, in seconds. Job hold, job classhold, job queue hold, duplicate jobname, or job class executionlimits. This is the sum of SMF30HQT.

MVS data tables


|


MEMLIMIT_MB FLOAT Memlimit value (in MB). This is the maximum occurrence ofSMF30MEM.

PA_GT16MB_BYTES FLOAT Maximum private area size above 16 megabytes, in bytes. Thisis the maximum of SMF30ERG.

PA_LT16MB_BYTES FLOAT Maximum private area size below 16 megabytes, in bytes. Thisis the maximum of SMF30RGB.

PAGEINS FLOAT Number of pages that were paged in from auxiliary storage.This is the sum of SMF30PGI.

PAGEINS_BLK_AUX FLOAT Number of blocked pages that were paged in from auxiliarystorage. This is the sum of SMF30BIA.

PAGEINS_BLK_ES FLOAT Number of blocked pages that were paged in from expandedstorage. This is the sum of SMF30BIE.

PAGEINS_COMMON FLOAT Number of common area page-ins (LPA + CSA). This is thesum of SMF30CPI.

PAGEINS_HIPER FLOAT Number of hiperspace page-ins from auxiliary to processorstorage. This is the sum of SMF30HPI.

PAGEINS_LPA FLOAT Number of LPA page-ins. This is the sum of SMF30LPI.

PAGEINS_SHARED FLOAT Number of IARVSERV shared pages that were paged in fromauxiliary storage in this address space. This is the sum ofSMF30PAI.

PAGEINS_SHARED_ES FLOAT Number of IARVSERV shared pages that were paged in fromexpanded storage in this address space. This is the sum ofSMF30PEI.

PAGEINS_UNBLK_ES FLOAT Number of unblocked pages that were paged in fromexpanded storage. This is the sum of SMF30PIE.

PAGEINS_VIO FLOAT Number of VIO page-ins. This is the sum of SMF30VPI.

PAGEOUTS FLOAT Number of pages that were paged out to auxiliary storage.This is the sum of SMF30PGO.

PAGEOUTS_BLK_AUX FLOAT Number of blocked pages that were paged out to auxiliarystorage. This is the sum of SMF30BOA.

PAGEOUTS_BLK_ES FLOAT Number of blocked pages that were paged out to expandedstorage. This is the sum of SMF30BOE.

PAGEOUTS_HIPER FLOAT Number of hiperspace page-outs from processor to auxiliarystorage. This is the sum of SMF30HPO.

PAGEOUTS_UNBLK_ES FLOAT Number of unblocked pages that were paged out to expandedstorage. This is the sum of SMF30POE.

PAGEOUTS_VIO FLOAT Number of VIO page-outs. This is the sum of SMF30VPO.

PAGES_STOLEN FLOAT Number of pages stolen from the address space. This is thesum of SMF30PST.

PAGES_SWAPPED_IN FLOAT Number of pages swapped in. This is the sum of SMF30PSI.

PAGES_SWAPPED_OUT FLOAT Number of pages swapped out. This is the sum of SMF30PSO.

PREPARATION_TIME FLOAT Job preparation time, in seconds. This is the elapsed timebefore the job was first queued for execution. This is the sumof SMF30JQT.

RECEIVE_CALLS FLOAT Number of times the transaction program issued a receive call.This is the sum of SMF30REC.

REGION_SIZE_MAX_KB FLOAT Maximum region size established, in kilobytes. This is themaximum of SMF30RGN.

MVS data tables


|


SCHEDULING_ENV CHAR(16) Scheduling environment name. This field is left blank if noscheduling environment is specified. From SMF30PFL.

SEND_CALLS FLOAT Number of times the transaction program issued a send call.This is the sum of SMF30SEN.

SERVICE_UNITS_CPU FLOAT Processor service units. This is the sum of SMF30CSU.

SERVICE_UNITS_ENCL FLOAT Enclave CPU service units. This is the sum of SMF30ESU.

SERVICE_UNITS_IO FLOAT I/O service units. This is the sum of SMF30IO.

SERVICE_UNITS_MSO FLOAT MSO service units. This is the sum of SMF30MSO.

SERVICE_UNITS_SRB FLOAT SRB service units. This is the sum of SMF30SRB.

SERVICE_UNITS_TOT FLOAT Total service units. This is the sum of SMF30SRV.

SHARED_PAGE_SEC FLOAT Number of CPU page seconds for the IARVSERV sharedcentral storage frames in use by this address space, in pagesecond units. This is the sum of SMF30PSF*0.001.

SRB_INIT_SECONDS FLOAT Initiator processor time under SRB, in seconds. Calculated asthe sum of SMF30ISB/100 for records where bit 0 or bit 5 ofSMF30TFL is 0.

SRB_PREEMP_SECONDS FLOAT Additional CPU time accumulated by the preemptable SRBsand client SRBs for this job, in seconds. This value is alsoincluded in the value in TCB_STEP_SECONDS. Calculated asthe sum of SMF30ASR/100 for records where bit 0 or bit 12 ofSMF30TFL is 0.

SRB_STEP_SECONDS FLOAT Step processor time under SRB, in seconds. Calculated as thesum of SMF30CPS/100 for records where bit 0 or bit 2 ofSMF30TFL is 0.

STOR_PRIV_BOT_KB INTEGER Largest amount of storage used from the bottom of the privatearea, in kilobytes. This is the maximum of SMF30PRV.

STOR_PRIV_TOP_KB INTEGER Largest amount of storage used from the top of the privatearea, in kilobytes. This is the maximum of SMF30SYS.

SWAP_SEQUENCES FLOAT Number of address space swap sequences. This is the sum ofSMF30NSW.

TAPE_BLOCKS FLOAT Number of blocks transferred to and from tape devices. Thisis the sum of SMF30BLK, where SMF30DEV = X'80'.

TCB_INIT_SECONDS FLOAT Initiator processor time under TCB, in seconds. Calculated asthe sum of SMF30ICU/100 for records where bit 0 or bit 6 ofSMF30TFL is 0.

TCB_STEP_SECONDS FLOAT Step processor time under TCB, in seconds. Calculated as thesum of SMF30CPT/100 for records where bit 0 or bit 1 ofSMF30TFL is 0.

TGET_COUNT INTEGER Number of TGETs for a TSO session. This is the sum ofSMF30TGT.

TPUT_COUNT INTEGER Number of TPUTs for a TSO session. This is the sum ofSMF30TPT.

TRAN_ACTIVE_SEC FLOAT SRM transaction active time, in seconds. Calculated as thesum of SMF30TAT*0.001 024.

TRAN_PROGRAMS FLOAT Number of APPC/MVS transaction programs scheduled bythe APPC/MVS transaction scheduler (ASCH). This is the sumof SMF30ATR.

TRAN_RESIDENT_SEC FLOAT SRM transaction residency time, in seconds. Calculated as thesum of SMF30RES*0.001 024.

MVS data tables



TRANSACTIONS FLOAT Number of SRM transactions. This is the sum of SMF30TRS.

TRANSACTIONS_ENCL FLOAT Enclave transaction count. This is the sum of SMF30ETC.

VA_INIT_SECONDS FLOAT Initiator vector affinity time, in seconds. Calculated as the sumof SMF30IVA/100 for records where bit 0 or bit 8 ofSMF30TFL is 0.

VA_STEP_SECONDS FLOAT Step vector affinity time, in seconds. Calculated as the sum ofSMF30JVA/100 for records where bit 0 or bit 4 of SMF30TFLis 0.

VIO_RECLAIMS FLOAT Number of VIO reclaims. This is the sum of SMF30VPR.

VS_LSQA_SWA_GT16MB FLOAT Maximum virtual storage above 16 megabytes allocated fromthe LSQA and SWA subpools, in bytes. This is the maximumof SMF30EAR.

VS_LSQA_SWA_LT16MB FLOAT Maximum virtual storage below 16 megabytes allocated fromthe LSQA and SWA subpools, in bytes. This is the maximumof SMF30ARB.

VS_USER_GT16MB FLOAT Maximum virtual storage above 16 megabytes allocated fromthe user subpools, in bytes. This is the maximum ofSMF30EUR.

VS_USER_LT16MB FLOAT Maximum virtual storage below 16 megabytes allocated fromthe user subpools, in bytes. This is the maximum ofSMF30URB.

VU_INIT_SECONDS FLOAT Initiator vector usage time, in seconds. Calculated as the sumof SMF30IVU/100 for records where bit 0 or bit 7 ofSMF30TFL is 0.

VU_STEP_SECONDS FLOAT Step vector usage time, in seconds. Calculated as the sum ofSMF30JVU/100 for records where bit 0 or bit 3 of SMF30TFLis 0.

WAITING_TIME FLOAT Job waiting for an initiator, in seconds. This is the sum ofSMF30SQT.

MVS data tables


MVS_ADDRSPACE_T,_D, _MThese tables provide daily and monthly address space statistics based on data fromSMF types 6, 25, 26, and 30 (subtypes 4 and 5) records. They contain consolidateddata from the MVS_ADDRSPACE_T table.

These tables are updated by the MVS_SYSPLEX and USER_GROUP lookup tables.

The default retention periods for these tables are:MVS_ADDRSPACE_D 30 daysMVS_ADDRSPACE_M 765 days


DATE k DATE Date when the jobs, TSO sessions, started tasks, orAPPC/MVS transaction programs were recognized by thereader. For the _M table, this is the date of the first day of themonth. From JOB_TIMESTAMP in the MVS_ADDRSPACE_Ttable.

PERIOD_NAME k CHAR(8) Name of the period. This is derived using columnsMVS_SYSTEM_ID and JOB_TIMESTAMP in theMVS_ADDRSPACE_T table as parameters in the PERIODfunction.

MVS_SYSTEM_ID k CHAR(4) MVS system ID. This is the SMF system ID. From SMF6SID,SMF25SID, SMF26SID, or SMF30SID.


USER_ID k CHAR(8) ID of the user for whom the activity is recorded. This is theRACF user ID. From SMF30RUD.

USER_GROUP k CHAR(8) Name of the group that the user belongs to. FromGROUP_NAME in the USER_GROUP lookup table; if nomatch is found, this column gets its value from SMF30RUD.


BLOCKS_IN_AUX FLOAT Number of blocks that were paged in from auxiliary storage.This is the sum of SMF30KIA.

BLOCKS_IN_ES FLOAT Number of blocks that were paged in from expanded storage.This is the sum of SMF30KIE.

BLOCKS_OUT_AUX FLOAT Number of blocks that were paged out to auxiliary storage.This is the sum of SMF30KOA.

BLOCKS_OUT_ES FLOAT Number of blocks that were paged out to expanded storage.This is the sum of SMF30KOE.

BLOCKS_TRANSFERRED FLOAT Number of blocks transferred. This is the sum of SMF30TEP.

BYTES_RCV FLOAT Amount of data received by the transaction program, in bytes.This is the sum of SMF30DAR.


CARDS_PUNCHED INTEGER Number of punched cards generated to the spool file. This isthe sum of SMF26XPU.

CARDS_READ INTEGER Number of card-image records in DD DATA and DD * datasets read by the reader. This is the sum of SMF30INP.

MVS data tables



CONNECT_INVALID CHAR(1) Indicates that the device connect time (CONNECT_MSEC)might be incorrect. This is set to 1 if the device connect timemight be incorrect. This is the maximum of bit 0 inSMF30DCF.

CONNECT_MSEC FLOAT Device connect time for the address space, in milliseconds.This is the sum of SMF30TCN.



CONVERS_TOT FLOAT Total number of conversations associated with the transactionprogram ID, both currently active and deallocated. This is thesum of SMF30CN.

CPU_ENQ_PROMOT_SEC FLOAT CPU time consumed for an address space or job whileenqueue promoted in seconds. Calculated as SUMSMF30CEP/1024.

CPU_HIPER_SECONDS FLOAT Processor time used to support data transfer to and from ahiperspace backed by expanded storage, in seconds.Calculated as the sum of SMF30HPT/100 for records wherebit 0 or bit 10 of SMF30TFL is 0.

CPU_INTR_SECONDS FLOAT Processor time used to process I/O interrupts, in seconds.Calculated as the sum of SMF30IIP/100 for records where bit0 or bit 9 of SMF30TFL is 0.

CPU_LOST_SECONDS FLOAT Total processor time lost because of abends or jobs canceled.This is the sum of all valid processor times for jobs that didnot complete normally.

CPU_PAGE_SECONDS FLOAT Number of processor page seconds. Calculated as the sum ofSMF30PSC*0.001.

CPU_RCT_SECONDS FLOAT Processor time used by the region control task, in seconds.Calculated as the sum of SMF30RCT/100 for records where bit0 or bit 11 of SMF30TFL is 0.

CPU_TOTAL_SECONDS FLOAT Total processor time, in seconds. This is the sum of all validprocessor times.

CS_FRAME_SECONDS FLOAT Active frame-time for frames in central storage, in seconds.Calculated as the sum ofSMF30RES*SMF30PSC*1024/(SMF30CPT*10 000 000).

DASD_BLOCKS FLOAT Number of blocks transferred to and from disk devices. This isthe sum of SMF30BLK, where SMF30DEV = X'20'.

ELAPSED_SECONDS FLOAT Total elapsed time spent for jobs, in seconds. Calculated as thesum of JOB_END_TIME − JOB_START_TIME.

ELAPSED_WRITER_SEC FLOAT Writer elapsed time, in seconds. This is the sum of the timeintervals from SMF6WSD and SMF6WST to SMF6DTE andSMF6TME.

ENCLAVE_ACTIVE_SEC FLOAT Enclave transaction active time, in seconds. This is the sum ofSMF30ETA.

ENCLAVE_SECONDS FLOAT CPU time used by enclaves, in seconds. This value is alsoincluded in TCB_STEP_SECONDS. Calculated as the sum ofSMF30ENC/100 for records where bit 0 or bit 13 of SMF30TFLis 0.

MVS data tables


|


ICSF_INSTRUCTIONS FLOAT Integrated Cryptographic Service Facility/MVS (ICSF/MVS)service count. This is the number of cryptographic instructionsexecuted on behalf of caller (within caller’s address space).Calculated as the sum of SMF30CSC.

INELIGIBLE_TIME_1 FLOAT Job ineligible for execution time, in seconds. The schedulingenvironment is not available. This is the sum of SMF30RQT.

INELIGIBLE_TIME_2 FLOAT Job ineligible for execution time, in seconds. Job hold, job classhold, job queue hold, duplicate jobname, or job class executionlimits. This is the sum of SMF30HQT.

JOB_QUEUE_SECONDS FLOAT Total time spent for jobs in the input queue, in seconds.Calculated as the sum ofJOB_START_TIME − JOB_TIMESTAMP.

JOBS INTEGER Number of jobs. This is a count of records from theMVS_ADDRSPACE_T table.

JOBS_CANCELED INTEGER Number of jobs canceled by the operator. This is the numberof times the JOB_CANCELED_IND column is 1 in theMVS_ADDRSPACE_T table.

JOBS_FLUSHED INTEGER Number of jobs that were flushed. This is the number of timesthe JOB_FLUSHED_IND column has a value other than nullin the MVS_ADDRSPACE_T table.

JOBS_MET_DEADLINE INTEGER Number of jobs for which deadline scheduling was specifiedand the deadline was met. This is the number of times theDEADLINE_MET_IND column is 1 in theMVS_ADDRSPACE_T table.

JOBS_RERUN INTEGER Number of jobs that were rerun. This is the number of timesthe RERUN_IND column is 1 in the MVS_ADDRSPACE_Ttable.

JOBS_WITH_DEADLINE INTEGER Number of jobs for which deadline scheduling was specified.This is the number of times the DEADLINE_USED_INDcolumn is 1 in the MVS_ADDRSPACE_T table.

LINES_PRINTED FLOAT Number of logical records written. This is the sum ofSMF6LNR.

LINES_TO_SPOOL INTEGER Number of output lines generated to the spool file. This is thesum of SMF26XLN.

LOST_BLOCKS_TRANS INTEGER Number of blocks transferred for abended jobs. This is thesum of SMF30TEP for jobs that did not complete normally.

LOST_ELAPSED_SEC FLOAT Total elapsed time spent for abended jobs, in seconds.Calculated as the sum ofJOB_END_TIME − JOB_START_TIME for jobs that did notcomplete normally.

MEMLIMIT_MB FLOAT Memlimit value (in MB). This is the maximum occurency ofSMF30MEM.

PA_GT16MB_BYTES FLOAT Maximum private area size above 16 megabytes, in bytes. Thisis the maximum of SMF30ERG.

PA_LT16MB_BYTES FLOAT Maximum private area size below 16 megabytes, in bytes. Thisis the maximum of SMF30RGB.

PAGEINS FLOAT Number of pages that were paged in from auxiliary storage.This is the sum of SMF30PGI.

PAGEINS_BLK_AUX FLOAT Number of blocked pages that were paged in from auxiliarystorage. This is the sum of SMF30BIA.

MVS data tables



PAGEINS_BLK_ES FLOAT Number of blocked pages that were paged in from expandedstorage. This is the sum of SMF30BIE.

PAGEINS_COMMON FLOAT Number of common area page-ins (LPA + CSA). This is thesum of SMF30CPI.

PAGEINS_HIPER FLOAT Number of hiperspace page-ins from auxiliary to processorstorage. This is the sum of SMF30HPI.


PAGEINS_SHARED FLOAT Number of IARVSERV shared pages that were paged in fromauxiliary storage in this address space. This is the sum ofSMF30PAI.

PAGEINS_SHARED_ES FLOAT Number of IARVSERV shared pages that were paged in fromexpanded storage in this address space. This is the sum ofSMF30PEI.





PAGEOUTS_BLK_ES FLOAT Number of blocked pages that were paged out to expandedstorage. This is the sum of SMF30BOE.

PAGEOUTS_HIPER FLOAT Number of hiperspace page-outs from processor to auxiliarystorage. This is the sum of SMF30HPO.

PAGEOUTS_UNBLK_ES FLOAT Number of unblocked pages that were paged out to expandedstorage. This is the sum of SMF30POE.


PAGES_PRINTED FLOAT Number of physical pages printed. This is the sum ofSMF6PGE.

PAGES_STOLEN FLOAT Number of pages stolen. This is the sum of SMF30PST.

PAGES_SWAPPED_IN FLOAT Number of pages swapped in. This is the sum of SMF30PSI.

PAGES_SWAPPED_OUT FLOAT Number of pages swapped out. This is the sum of SMF30PSO.

PREPARATION_TIME FLOAT Job preparation time, in seconds. This is the elapsed timebefore the job was first queued for execution. This is the sumof SMF30JQT.

PROCESSING_NODE CHAR(8) Processing network node name. From SMF26NXN.

RECEIVE_CALLS FLOAT Number of times the transaction program issued a receive call.This is the sum of SMF30REC.


SCHEDULING_ENV CHAR(16) Scheduling environment name. This field is left blank if noscheduling environment is specified. From SMF30PFL.

SEND_CALLS FLOAT Number of times the transaction program issued a send call.This is the sum of SMF30SEN.

SERVICE_UNITS_CPU FLOAT Processor service units. This is the sum of SMF30CSU.



MVS data tables



SERVICE_UNITS_LOST FLOAT Total service units lost because of abends or jobs canceled.This is the sum of SMF30SRV for jobs that did not completenormally.




SHARED_PAGE_SEC FLOAT Number of CPU page seconds for the IARVSERV sharedcentral storage frames in use by this address space, in pagesecond units. This is the sum of SMF30PSF*0.001.

SRB_INIT_SECONDS FLOAT Initiator processor time under SRB, in seconds. Calculated asthe sum of SMF30ISB/100 for records where bit 0 or bit 5 ofSMF30TFL is 0.

SRB_PREEMP_SECONDS FLOAT Additional CPU time accumulated by the preemptable SRBsand client SRBs for this job, in seconds. This value is alsoincluded in the value in TCB_STEP_SECONDS. Calculated asthe sum of SMF30ASR/100 for records where bit 0 or bit 12 ofSMF30TFL is 0.

SRB_STEP_SECONDS FLOAT Step processor time under SRB, in seconds. Calculated as thesum of SMF30CPS/100 for records where bit 0 or bit 2 ofSMF30TFL is 0.

STEPS INTEGER Number of steps. This is the sum of SMF30STN.

STOR_DATA_SPACE_MB FLOAT Maximum amount of data space storage used, in megabytes.This is the maximum of SMF30DSV.

STOR_PRIV_BOT_KB INTEGER Largest amount of storage used from the bottom of the privatearea, in kilobytes. This is the maximum of SMF30PRV.

STOR_PRIV_TOP_KB INTEGER Largest amount of storage used from the top of the privatearea, in kilobytes. This is the maximum of SMF30SYS.

SWAP_SEQUENCES FLOAT Number of address space swap sequences. This is the sum ofSMF30NSW.

SYSPLEX_NAME CHAR(8) Sysplex name. This is the name of the sysplex. FromSYSPLEX_NAME in the MVS_SYSPLEX lookup table.

SYSTEM_ABENDS INTEGER Number of jobs that had a system abend. This is the numberof times the SYSTEM_ABEND_CODE column has a valueother than null in the MVS_ADDRSPACE_T table.

TAPE_BLOCKS FLOAT Number of blocks transferred to and from tape devices. Thisis the sum of SMF30BLK, where SMF30DEV = X'80'.

TAPE_MOUNTS INTEGER Number of tape mounts. Calculated as the sum of SMF25NTM+ SMF30PTM + SMF30TPR.

TCB_INIT_SECONDS FLOAT Initiator processor time under TCB, in seconds. Calculated asthe sum of SMF30ICU/100 for records where bit 0 or bit 6 ofSMF30TFL is 0.

TCB_STEP_SECONDS FLOAT Step processor time under TCB, in seconds. Calculated as thesum of SMF30CPT/100 for records where bit 0 or bit 1 ofSMF30TFL is 0.



MVS data tables



TRAN_ACTIVE_SEC FLOAT SRM transaction active time, in seconds. Calculated as thesum of SMF30TAT*0.001 024.

TRAN_PROGRAMS FLOAT Number of APPC/MVS transaction programs scheduled bythe APPC/MVS transaction scheduler (ASCH). This is the sumof SMF30ATR.

TRAN_RESIDENT_SEC FLOAT SRM transaction residency time, in seconds. Calculated as thesum of SMF30RES*0.001 024.

TRANSACTIONS FLOAT Number of SRM transactions. This is the sum of SMF30TRS.


USER_ABENDS INTEGER Number of jobs that had a user abend. This is the number oftimes the USER_ABEND_CODE column has a value otherthan null in the MVS_ADDRSPACE_T table.

VA_INIT_SECONDS FLOAT Initiator vector affinity time, in seconds. Calculated as the sumof SMF30IVA/100 for records where bit 0 or bit 8 ofSMF30TFL is 0.

VA_STEP_SECONDS FLOAT Step vector affinity time, in seconds. Calculated as the sum ofSMF30JVA/100 for records where bit 0 or bit 4 of SMF30TFLis 0.


VS_LSQA_SWA_GT16MB FLOAT Maximum virtual storage above 16 megabytes allocated fromthe LSQA and SWA subpools, in bytes. This is the maximumof SMF30EAR.

VS_LSQA_SWA_LT16MB FLOAT Maximum virtual storage below 16 megabytes allocated fromthe LSQA and SWA subpools, in bytes. This is the maximumof SMF30ARB.

VS_USER_GT16MB FLOAT Maximum virtual storage above 16 megabytes allocated fromthe user subpools, in bytes. This is the maximum ofSMF30EUR.

VS_USER_LT16MB FLOAT Maximum virtual storage below 16 megabytes allocated fromthe user subpools, in bytes. This is the maximum ofSMF30URB.

VU_INIT_SECONDS FLOAT Initiator vector usage time, in seconds. Calculated as the sumof SMF30IVU/100 for records where bit 0 or bit 7 ofSMF30TFL is 0.

VU_STEP_SECONDS FLOAT Step vector usage time, in seconds. Calculated as the sum ofSMF30JVU/100 for records where bit 0 or bit 3 of SMF30TFLis 0.


MVS data tables


MVS_ADDRSPACE_TThis table provides detailed address space statistics. It contains data from SMFtypes 6, 25, 26, and 30 (subtypes 4 and 5) records.

This table is updated by the MVS_SYSPLEX and USER_GROUP lookup tables.

The default retention period for this table is 7 days for jobs that ended normally,and 45 days for abended jobs.


JOB_TIMESTAMP k TIMESTAMP Date and time when the job, TSO session, started task, orAPPC/MVS transaction program was recognized by thereader. From SMF6RSD and SMF6RST, or SMF25RSD andSMF25RST, or SMF26RSD and SMF26RST, or SMF30RSDand SMF30RST.

JOB_NAME k CHAR(8) Job name, TSO user ID, name of the started task, or nameof the APPC/MVS session. From SMF6JBN, SMF25JBN,SMF26JBN, or SMF30JBN.

ACCOUNT_FIELD1 VARCHAR(8) First accounting field. This is the first occurrence ofSMF30ACT.

ACCOUNT_FIELD2 VARCHAR(8) Second accounting field. This is the second occurrence ofSMF30ACT.

ACCOUNT_FIELD3 VARCHAR(8) Third accounting field. This is the third occurrence ofSMF30ACT.

ACCOUNT_FIELD4 VARCHAR(8) Fourth accounting field. This is the fourth occurrence ofSMF30ACT.

BLOCKS_IN_AUX FLOAT Number of blocks that were paged in from auxiliarystorage. This is the sum of SMF30KIA.

BLOCKS_IN_ES FLOAT Number of blocks that were paged in from expandedstorage. This is the sum of SMF30KIE.

BLOCKS_OUT_AUX FLOAT Number of blocks that were paged out to auxiliarystorage. This is the sum of SMF30KOA.

BLOCKS_OUT_ES FLOAT Number of blocks that were paged out to expandedstorage. This is the sum of SMF30KOE.

BLOCKS_TRANSFERRED FLOAT Number of blocks transferred. This is the sum ofSMF30TEP.

BYTES_RCV FLOAT Amount of data received by the transaction program, inbytes. This is the sum of SMF30DAR.


CARDS_PUNCHED INTEGER Number of punched cards generated to the spool file. Thisis the sum of SMF26XPU.

CARDS_READ INTEGER Number of card-image records in DD DATA and DD *data sets read by the reader. This is the sum of SMF30INP.

CONNECT_INVALID CHAR(1) Indicates that the device connect time (CONNECT_MSEC)might be incorrect. This is set to 1 if the device connecttime might be incorrect. This is the maximum of bit 0 inSMF30DCF.

CONNECT_MSEC FLOAT Device connect time for the address space, in milliseconds.This is the sum of SMF30TCN.

MVS data tables





CONVERS_TOT FLOAT Total number of conversations associated with thetransaction program ID, both currently active anddeallocated. This is the sum of SMF30CN.

CPU_HIPER_INVALID CHAR(1) Indicates that the CPU time used to support data transferto and from a hiperspace backed by expanded storage isinvalid for any step. This is set to 1 if this CPU time isinvalid. This is the maximum of bit 10 of SMF30TFL if bit0 of SMF30TFL is 1.

CPU_HIPER_SECONDS FLOAT Processor time used to support data transfer to and from ahiperspace backed by expanded storage, in seconds.Calculated as the sum of SMF30HPT/100 for recordswhere bit 0 or bit 10 of SMF30TFL is 0.

CPU_INTR_INVALID CHAR(1) Indicates that the CPU time used to process I/O interruptsis invalid for any step. This is set to 1 if the CPU timeused to process I/O interrupts is invalid. This is themaximum of bit 9 of SMF30TFL if bit 0 of SMF30TFL is 1.

CPU_INTR_SECONDS FLOAT CPU time used to process I/O interrupts, in seconds.Calculated as the sum of SMF30IIP/100 for records wherebit 0 or bit 9 of SMF30TFL is 0.

CPU_PAGE_SECONDS FLOAT Number of CPU page seconds for the address space. Thisis the sum of SMF30PSC*0.001.

CPU_RCT_INVALID CHAR(1) Indicates that the CPU time used by the region controltask is invalid for any step. This is set to 1 if the CPU timeused by the RCT is invalid. This is the maximum of bit 11of SMF30TFL if bit 0 of SMF30TFL is 1.

CPU_RCT_SECONDS FLOAT CPU time used by the region control task, in seconds.Calculated as the sum of SMF30RCT/100 for recordswhere bit 0 or bit 11 of SMF30TFL is 0.

CPU_TOTAL_SECONDS FLOAT Total processor time, in seconds. This is the sum of allvalid processor times.

CS_FRAME_SECONDS FLOAT Active frame-time for frames in central storage, inseconds. Calculated as the sum ofSMF30RES*SMF30PSC*1024/(SMF30CPT*10 000 000).

DASD_BLOCKS FLOAT Number of blocks transferred to and from disk devices.This is the sum of SMF30BLK where SMF30DEV=X'20'.

DEADLINE_MET_IND CHAR(1) Indicates whether the job met the deadline. This is set to 1if DEADLINE_USED_IND is 1 and the job met thedeadline; 0 if not. This is the maximum of bit 2 ofSMF26IN3 (JES3 only).

DEADLINE_TIME TIMESTAMP Deadline schedule date and time. This is the maximumtimestamp from SMF6DDT and SMF6DTM if deadlinescheduling (JES3 only) is specified.

DEADLINE_USED_IND CHAR(1) Indicates whether deadline scheduling (JES3 only) isspecified. This is set to 1 if deadline scheduling isspecified; 0 if not. This is the maximum of bit 1 ofSMF26IN3.

DISPATCH_PRIORITY SMALLINT Dispatching priority for the last step. This is the lastoccurrence of SMF30PTY.

MVS data tables



ELAPSED_SECONDS FLOAT Elapsed time spent for the job, in seconds. Calculated asJOB_END_TIME - JOB_START_TIME.

ELAPSED_WRITER_SEC FLOAT Writer elapsed time, in seconds. Calculated as the sum ofthe time interval from SMF6WSD and SMF6WST, toSMF6DTE and SMF6TME.

ENCLAVE_ACTIVE_SEC FLOAT Enclave transaction active time, in seconds. This is thesum of SMF30ETA.

ENCLAVE_SECONDS FLOAT CPU time used by enclaves, in seconds. This value is alsoincluded in TCB_STEP_SECONDS. Calculated as the sumof SMF30ENC/100 for records where bit 0 or bit 13 ofSMF30TFL is 0.

ICSF_INSTRUCTIONS FLOAT Integrated Cryptographic Service Facility/MVS(ICSF/MVS) service count. This is the number ofcryptographic instructions executed on behalf of the caller(within the caller’s address space). Calculated as the sumof SMF30CSC.

JOB_CANCELED_IND CHAR(1) Indicates that the job was canceled by the operator. This isset to Y (yes) if the last bit of SMF26INF is set.

JOB_CLASS CHAR(1) Job class. From SMF30CLS.

JOB_END_TIME TIMESTAMP Date and time when the last step was completed. This isthe last timestamp from SMF30DTE and SMF30TME.

JOB_FLUSHED_IND CHAR(1) Indicates that a step was flushed. This is set to Y (yes) ifbit 7 of SMF30STI is set for any step.

JOB_QUEUE_SECONDS FLOAT Time spent by the job in the input queue, in seconds.Calculated as JOB_START_TIME - JOB_TIMESTAMP.

JOB_START_TIME TIMESTAMP Date and time when the initiator selected the first step.This is the first timestamp from SMF30STD and SMF30SIT.

LINES_PRINTED FLOAT Number of logical records written. This is the sum ofSMF6LNR.

LINES_TO_SPOOL INTEGER Number of output lines generated to the spool file. This isthe sum of SMF26XLN.


ORIGINAL_NODE CHAR(8) Original network node name. From SMF26NON.

PAGEINS FLOAT Number of pages that were paged in from auxiliarystorage. This is the sum of SMF30PGI.

PAGEINS_BLK_AUX FLOAT Number of blocked pages that were paged in fromauxiliary storage. This is the sum of SMF30BIA.

PAGEINS_BLK_ES FLOAT Number of blocked pages that were paged in fromexpanded storage. This is the sum of SMF30BIE.

PAGEINS_COMMON FLOAT Number of common area page-ins (LPA + CSA). This isthe sum of SMF30CPI.

PAGEINS_HIPER FLOAT Number of hiperspace page-ins from auxiliary toprocessor storage. This is the sum of SMF30HPI.


PAGEINS_SHARED FLOAT Number of IARVSERV shared pages that were paged infrom auxiliary storage in this address space. This is thesum of SMF30PAI.

MVS data tables



PAGEINS_SHARED_ES FLOAT Number of IARVSERV shared pages that were paged infrom expanded storage in this address space. This is thesum of SMF30PEI.





PAGEOUTS_BLK_ES FLOAT Number of blocked pages that were paged out toexpanded storage. This is the sum of SMF30BOE.

PAGEOUTS_HIPER FLOAT Number of hiperspace page-outs from processor toauxiliary storage. This is the sum of SMF30HPO.

PAGEOUTS_UNBLK_ES FLOAT Number of unblocked pages that were paged out toexpanded storage. This is the sum of SMF30POE.


PAGES_PRINTED FLOAT Number of physical pages written. This is the sum ofSMF6PGE.

PAGES_STOLEN FLOAT Number of pages stolen from the address space. This isthe sum of SMF30PST.

PAGES_SWAPPED_IN FLOAT Number of pages swapped in. This is the sum ofSMF30PSI.

PAGES_SWAPPED_OUT FLOAT Number of pages swapped out. This is the sum ofSMF30PSO.

PA_GT16MB_BYTES FLOAT Maximum private area size above 16 megabytes, in bytes.This is the maximum of SMF30ERG.

PA_LT16MB_BYTES FLOAT Maximum private area size below 16 megabytes, in bytes.This is the maximum of SMF30RGB.

PERF_GROUP_NO CHAR(4) Performance group number. This field is zero when inworkload management goal mode. From SMF30PGN.

PROCESSING_NODE CHAR(8) Processing network node name. From SMF26NXN.

PROGRAMMER_NAME CHAR(20) Name of the programmer. From SMF30USR.

PURGE_TIME TIMESTAMP Date and time when the job was purged. From SMF26DTEand SMF26TME.

RACF_GROUP_ID CHAR(8) RACF group ID. From SMF30GRP.

RACF_TERMINAL_ID CHAR(8) RACF terminal ID. From SMF30TID.

RACF_USER_ID CHAR(8) RACF user ID. From SMF30RUD.

REASON_CODE INTEGER Reason code for the last step that had a system abend.This is set to null if all steps completed without a systemabend. This is the last occurrence of SMF30ARC when thefirst hexadecimal digit of SMF30SCC is 0 and bit 6 ofSMF30STI is 1.

RECEIVE_CALLS FLOAT Number of times the transaction program issued a receivecall. This is the sum of SMF30REC.


MVS data tables



REPORT_CLASS CHAR(8) Report class name. This field is blank when in workloadmanagement compatibility mode. From SMF30RCN.

RERUN_IND CHAR(1) Indicates that the job was rerun. This is set to Y (yes) if bit6 in SMF26INF is set.

RETURN_CODE INTEGER Maximum return code for steps that completed normally.This is the maximum of SMF30SCC when bits 6 and 7 ofSMF30STI are 0.

SEND_CALLS FLOAT Number of times the transaction program issued a sendcall. This is the sum of SMF30SEN.

SERVICE_CLASS CHAR(8) Service class name. This field is blank when in workloadmanagement compatibility mode. From SMF30SCN.

SERVICE_UNITS_CPU FLOAT CPU service units. This is the sum of SMF30CSU.






SHARED_PAGE_SEC FLOAT Number of CPU page seconds for the IARVSERV sharedcentral storage frames in use by this address space, inpage second units. This is the sum of SMF30PSF*0.001.

SRB_INIT_INVALID CHAR(1) Indicates that the initiator CPU time under SRB is invalidfor any step. This is set to 1 if the initiator CPU timeunder SRB is invalid. This is the maximum of bit 5 ofSMF30TFL if bit 0 of SMF30TFL is 1.

SRB_INIT_SECONDS FLOAT Initiator CPU time under SRB, in seconds. Calculated asthe sum of SMF30ISB/100 for records where bit 0 or bit 5of SMF30TFL is 0.

SRB_PREEMP_SECONDS FLOAT Additional CPU time accumulated by the preemptableSRBs and client SRBs for this job, in seconds. This value isalso included in the value in TCB_STEP_SECONDS.Calculated as the sum of SMF30ASR/100 for recordswhere bit 0 or bit 12 of SMF30TFL is 0.

SRB_STEP_INVALID CHAR(1) Indicates that the step CPU time under SRB is invalid forany step. This is set to 1 if the step CPU time under SRBis invalid. This is the maximum of bit 2 of SMF30TFL ifbit 0 of SMF30TFL is 1.

SRB_STEP_SECONDS FLOAT Step CPU time under SRB, in seconds. Calculated as thesum of SMF30CPS/100 for records where bit 0 or bit 2 ofSMF30TFL is 0.

STEPS INTEGER Number of steps. From SMF30STN.

STOR_DATA_SPACE_MB FLOAT Maximum amount of data space storage used, inmegabytes. This is the maximum of SMF30DSV.

STOR_PRIV_BOT_KB INTEGER Largest amount of storage used from the bottom of theprivate area, in kilobytes. This is the maximum ofSMF30PRV.

STOR_PRIV_TOP_KB INTEGER Largest amount of storage used from the top of theprivate area, in kilobytes. This is the maximum ofSMF30SYS.

SUBSYSTEM_ID CHAR(4) Subsystem identifier. From SMF30WID.

MVS data tables



SWAP_SEQUENCES FLOAT Number of address space swap sequences. This is the sumof SMF30NSW.


SYSTEM_ABEND_CODE CHAR(3) System abend code issued. This is set to null if no systemabend occurred. This is the last occurrence of SMF30SCCwhen the first hexadecimal digit of SMF30SCC is 0 and bit6 of SMF30STI is 1.

TAPE_BLOCKS FLOAT Number of blocks transferred to and from tape devices.This is the sum of SMF30BLK where SMF30DEV=X'80'.

TAPE_MOUNTS INTEGER Number of tape mounts. Calculated as the sum ofSMF25NTM + SMF30PTM + SMF30TPR.

TCB_INIT_INVALID CHAR(1) Indicates that the initiator CPU time under TCB is invalidfor any step. This is set to 1 if the initiator CPU timeunder TCB is invalid. This is the maximum of bit 6 ofSMF30TFL if bit 0 of SMF30TFL is 1.

TCB_INIT_SECONDS FLOAT Initiator CPU time under TCB, in seconds. Calculated asthe sum of SMF30ICU/100 for records where bit 0 or bit 6of SMF30TFL is 0.

TCB_STEP_INVALID CHAR(1) Indicates that the step CPU time under TCB is invalid forany step. This is set to 1 if the step CPU time under TCBis invalid. This is the maximum of bit 1 of SMF30TFL ifbit 0 of SMF30TFL is 1.

TCB_STEP_SECONDS FLOAT Step CPU time under TCB, in seconds. Calculated as thesum of SMF30CPT/100 for records where bit 0 or bit 1 ofSMF30TFL is 0.

TERMINAL_NAME CHAR(8) Terminal symbolic name. From SMF30TSN.



TRAN_ACTIVE_SEC FLOAT SRM transaction active time, in seconds. Calculated as thesum of SMF30TAT*0.001024.

TRAN_PROGRAMS FLOAT Number of APPC/MVS transactions programs scheduledby the APPC/MVS transaction scheduler (ASCH). This isthe sum of SMF30ATR.

TRAN_RESIDENT_SEC FLOAT SRM transaction residency time, in seconds. Calculated asthe sum of SMF30RES*0.001024.

TRANSACTIONS FLOAT Number of SRM transactions. This is the sum ofSMF30TRS.


USER_ABEND_CODE INTEGER User abend code issued. This is set to null if no userabend occurred. This is the last occurrence of SMF30SCCwhen the first hexadecimal digit of SMF30SCC is 8 and bit6 of SMF30STI is 1.

USER_GROUP CHAR(8) Name of the group that the user belongs to. FromGROUP_NAME in the USER_GROUP lookup table.

MVS data tables



VA_INIT_INVALID CHAR(1) Indicates that the initiator vector affinity time is invalidfor any step. This is set to 1 if the initiator vector affinitytime is invalid. This is the maximum of bit 8 of SMF30TFLif bit 0 of SMF30TFL is 1.

VA_INIT_SECONDS FLOAT Initiator vector affinity time, in seconds. Calculated as thesum of SMF30IVA/100 for records where bit 0 or bit 8 ofSMF30TFL is 0.

VA_STEP_INVALID CHAR(1) Indicates that the step vector affinity time is invalid forany step. This is set to 1 if the step vector affinity time isinvalid. This is the maximum of bit 4 of SMF30TFL if bit 0of SMF30TFL is 1.

VA_STEP_SECONDS FLOAT Step vector affinity time, in seconds. Calculated as thesum of SMF30JVA/100 for records where bit 0 or bit 4 ofSMF30TFL is 0.


VS_LSQA_SWA_GT16MB FLOAT Maximum virtual storage above 16 megabytes allocatedfrom the LSQA and SWA subpools, in megabytes.Calculated as the maximum of SMF30EAR/1048576.

VS_LSQA_SWA_LT16MB FLOAT Maximum virtual storage below 16 megabytes allocatedfrom the LSQA and SWA subpools, in megabytes.Calculated as the maximum of SMF30ARB/1048576.

VS_USER_GT16MB FLOAT Maximum virtual storage above 16 megabytes allocatedfrom the user subpools, in megabytes. Calculated as themaximum of SMF30EUR/1048576.

VS_USER_LT16MB FLOAT Maximum virtual storage below 16 megabytes allocatedfrom the user subpools, in megabytes. Calculated as themaximum of SMF30URB/1048576.

VU_INIT_INVALID CHAR(1) Indicates that the initiator vector usage time is invalid forany step. This is set to 1 if the initiator vector usage timeis invalid. This is the maximum of bit 7 of SMF30TFL ifbit 0 of SMF30TFL is 1.

VU_INIT_SECONDS FLOAT Initiator vector usage time, in seconds. Calculated as thesum of SMF30IVU/100 for records where bit 0 or bit 7 ofSMF30TFL is 0.

VU_STEP_INVALID CHAR(1) Indicates that the step vector usage time is invalid for anystep. This is set to 1 if the step vector usage time isinvalid. This is the maximum of bit 3 of SMF30TFL if bit 0of SMF30TFL is 1.

VU_STEP_SECONDS FLOAT Step vector usage time, in seconds. Calculated as the sumof SMF30JVU/100 for records where bit 0 or bit 3 ofSMF30TFL is 0.

WORKLOAD_GROUP CHAR(8) MVS workload group name. This field is blank when inworkload management compatibility mode. FromSMF30WLM.

MVS data tables


MVS_COMPCODE_D, _MThese tables provide daily and monthly statistics on job completion on MVSsystems. They contain one row for each system abend code, user abend code, andreturn code, based on SMF type 30, subtype 4 records. The data comes from theMVS_ADDRSPACE_T table.

These tables are updated by the MVS_SYSPLEX lookup table.

The default retention periods for these tables are:MVS_COMPCODE_D 30 daysMVS_COMPCODE_M 765 days


DATE k DATE Date when the jobs, TSO sessions, or started tasks were recognizedby the reader. For the _M table, this is the date of the first day ofthe month. From SMF30RSD.

PERIOD_NAME k CHAR(8) Name of the period. This is derived using the MVS_SYSTEM_IDand JOB_TIMESTAMP columns in the MVS_ADDRSPACE_T tableas parameters in the PERIOD function.



COMPLETION_TYPE k CHAR(1) Step completion type. This is S if any step abended, U if any stephad a user abend, F if any step was flushed, or C if all stepscompleted normally.

COMPLETION_CODE k CHAR(5) Depending on the value in COMPLETION_TYPE, this is thesystem abend code for the last step that had a system abend, theuser abend code for the last step that had a user abend, or themaximum return code for the job. From SMF30SCC.

JOBS INTEGER Number of jobs. This is the count of all combinations ofCOMPLETION_TYPE and COMPLETION_CODE.


MVS data tables


MVS_ENCLAVE_H, _D, _MThese tables provide hourly, daily, and monthly statistics on MVS enclave activityby MVS system ID, subsystem ID, and remote system. They contain data fromSMF type 30, subtypes 2 and 3 records.

The default retention periods for these tables are:MVS_ENCLAVE_H 7 daysMVS_ENCLAVE_D 45 daysMVS_ENCLAVE_M 765 days


DATE k DATE Date of the mid-measurement. From SMF30ISS and SMF30IET.

TIME k TIME Time of the mid-measurement. From SMF30ISS and SMF30IET. Itapplies only to the _H table.



JOB_NAME k CHAR(8) Job or session name. The job name, time and date that the readerrecognized the JOB card (for this job) constitute the job logidentification. From SMF30JBN.

PGM_NAME k CHAR(8) Program name (taken from the PGM parameter on the EXECcard). If a backward reference has been used, this field containsPGM=*.DD. From SMF30PGM.

SYSTEM_NAME k CHAR(8) Name of the system on which enclaves created by this addressspace are executed. From SMF30MRS.

ENCL_DEP_CPU_SEC FLOAT Number of seconds accumulated by dependent enclaves thatexecuted on the system named by SMF30MRS. FromSMF30MRD. For the _D table, this is the sum of the hourlyvalues. For the _M table, this is the sum of the daily values.

ENCL_INDEP_CPU_SEC FLOAT Number of seconds accumulated by independent enclaves thatexecuted on the system named by SMF30MRS. From SMF30MRI.For the _D table, this is the sum of the hourly values. For the _Mtable, this is the sum of the daily values.

MEASURED_SEC FLOAT Measured time period in seconds. This is the sum of timeintervals from SMF30ISS and SMF30IET.

MVS data tables


MVS_GOAL_ACT_D, _MThese tables provide daily and monthly statistics on MVS response time goals andactuals by workload type and service class. These tables will be updated onlywhen in workload management goal mode. They contain data from SMF type 72,subtype 3 records.

These tables are updated by the MVS_WORKLOAD2_TYPE lookup table.

The default retention periods for these tables are:MVS_GOAL_ACT_D 30 daysMVS_GOAL_ACT_M 765 days


DATE k DATE Date when the transactions occurred. For the _M table, this isthe date of the first day of the month. From SMF72DAT,SMF72IST, and SMF72INT.

PERIOD_NAME k CHAR(8) Name of the period. This is derived using fields SMF72DAT,SMF72IST, and SMF72INT from the record as parameters in thePERIOD function.

SYSPLEX_NAME k CHAR(8) Sysplex name. This is the name of the sysplex. FromSMF72XNM.

MVS_SYSTEM_ID k CHAR(4) MVS system identification. From SMF72SID.

WORKLOAD_TYPE k CHAR(8) MVS workload type name. From WORKLOAD_TYPE in theMVS_WORKLOAD2_TYPE lookup table.

WORKLOAD_GROUP k CHAR(8) MVS workload group name. From R723MWNM.

SERVICE_POLICY k CHAR(8) Service policy name. From R723MNSP.

SERVICE_CLASS k CHAR(8) Service or report class name. From R723MCNM.

SERV_CLASS_PERIOD k CHAR(1) Service or report class period number. From R723CPER.

GOAL_PERCENTAGE k SMALLINT Defines the maximum percentage of a goal (that is 50, 70, 200,and so on). From R723TRDB.

AVERAGE_GOAL_SEC FLOAT Average response time goal, in seconds. From R723CVAL(converted to seconds using R723CRTF) if R723CRGF is equalto X'40', otherwise set to zero.

GOAL_FLAG SMALLINT Goal flag; 0=percentile response time goal, 1=average responsetime goal, 2=execution velocity goal, 3=discretionary goal,4=system specified goal. From R723CRGF.

GOAL_IMPORTANCE SMALLINT Relative importance of the goal to be achieved for this serviceclass period (1=highest–5=lowest). Calculated as the maximumof R723CIMP.

GOAL_PERCENTILE SMALLINT Percentile response time goal, in percent. From R723CPCT ifR723CRGF is equal to X'80', otherwise set to zero.

PERCENT_GOAL_SEC FLOAT Response time goal, in seconds. From R723CVAL (converted toseconds using R723CRTF) if R723CRGF is equal to X'80',otherwise set to zero. GOAL_PERCENTILE percent of alltransactions should be completed withinPERCENT_GOAL_SEC seconds.

REPORT_PERIOD_FLAG CHAR(1) Report class period flag: 1=Heterogeneous class (more than oneservice class for the same report class), 0=Homogeneous reportclass period (only one service class for this report class). Blankif this is a service class period. From R723CRS1.

MVS data tables


|

|


SERV_CLASS_TYPE CHAR(1) Service class (SC) type. This can be C (control), or R (reporting).All data in reporting SCs is also reported in a control SC. So,when summaries are produced, only control SCs should beselected. From R723MSCF.

SERV_FOR_REPORT CHAR(8) Service class that last contributed to this report class. Blank ifthis is a service class. From R723CLSC.

SYSTEM_NAME CHAR(8) MVS system name. This is the MVS system name. FromSMF72SNM.

TRANSACTIONS INTEGER Number of transactions that ended within X percent of theresponse time goal. X is the value in columnGOAL_PERCENTAGE. This is the sum of R723TRDB.

MVS data tables


|

MVS_IPL_TThis table provides system IPL statistics. It contains data from SMF type 90,subtype 8 records.



DATE k DATE Date when the IPL occurred. From SMF90DTT.

TIME k TIME Time when the IPL occurred. From SMF90ITM.


IPL_REASON CHAR(65) Reason for the IPL. From SMF90RSN.

OPERATOR_NAME CHAR(20) Name of the operator that performed the system IPL. FromSMF90OPR.

SYSTEM_DOWN_TIME CHAR(8) System down time entered by the operator. From SMF90DTM.

MVS data tables


MVS_LPAR_D, _MThese tables provide daily and monthly statistics on logical partitions andprocessor activity in a PR/SM environment. They contain data from SMF type 70records processed through a record procedure (DRL2S070).

The default retention periods for these tables are:MVS_LPAR_D 45 daysMVS_LPAR_M 765 days

These tables are updated by the MVS_MIPS_T lookup table.


DATE k DATE Date of the mid measurement. For the _M table, this is thedate of the first day of the month. From SMF70DAT,SMF70IST, and SMF70INT.

PERIOD_NAME k CHAR(8) Name of the period. This is derived using fields SMF70DAT,SMF70IST, and SMF70INT from the record as parameters inthe PERIOD function.


LPAR_NAME k CHAR(8) Name of the logical partition. From SMF70LPM.

PROCESSOR_TYPE k CHAR(3) Name of the logical processor type (CP for general purposeprocessor or ICF for integrated coupling processor). FromSMF70CIX.

CAPACITY_LIMIT_MSU FLOAT Defined capacity limit of the partition in MSUs per hour. Avalue of 0 indicates that the partition is not under control ofthe License Manager. From SMF70MSU.

CENTRAL_STOR_FRAME INTEGER Central storage frames assigned to this partition. Calculatedas MAX of SMF70CSF.

COMPLEX_SEC FLOAT Total processor complex time, in seconds. Processors CP andICF are considered separately.

COUNT_SHR INTEGER Number of occurrences of LPROC shared.

CPU_BUSY_MIPS FLOAT Virtual processor busy MIPS time, in seconds. Calculated asthe sum of (SMF70PDT/1000000.)* MIPS_PER_LPAR.

CPU_DISPATCH_SEC FLOAT Logical processor dispatch time, in seconds. Calculated as thesum of SMF70PDT/1 000 000.

CPU_EFF_DISP_SEC FLOAT Logical processor effective dispatch time (excluding LPARmanagement time), in seconds. Calculated as the sum ofSMF70EDT/1 000 000.

CPU_MODEL_NO SMALLINT CPU model number. From SMF70MOD.

CPU_SERIAL_NO CHAR(5) Last 4 digits of the CPU serial number. From SMF70SER.

CPU_WAIT_SEC FLOAT Processor wait time, in seconds. This is set to zero if theprocessor was run in LPAR mode and wait completion wasnot enabled. Calculated as the sum ofSMF70WAT/4 096 000 000.

DEDICAT_PROC_LPAR SMALLINT Number of dedicated processors for this LPAR. Calculated asthe MAX of LPDEDICF (ICF) or LPDEDCP (CP).

DEDICATED_PROC_IND SMALLINT Indicates whether the partition has been assigned one ormore dedicated processors; 1 = yes, or 0 = no. FromSMF70BPS.

MVS data tables


|

|

|

|

|

|

|


DISPATCH_INTERVAL FLOAT Dispatch interval time, in seconds. A zero value indicates thatthe interval was dynamically determined. Calculated as thesum of SMF70GTS/1000.

EXPAND_STOR_FRAME INTEGER Expanded storage frames assigned to this partition.Calculated as maximum of SMF70CSF.

FROM_LPAR_NO SMALLINT Number of the logical partition that wrote the record. FromSMF70PTN.

LOGICAL_PROCESSORS SMALLINT Number of logical processors assigned to the partition. FromSMF70BDN.

LPAR_FLAGS CHAR(2) LPAR flags. 80 = partition deactivated during interval, 40 =number of logical processors changed. From SMF70PFG.

LPAR_NO SMALLINT Number of the logical partition. From SMF70LPN.

LPAR_WEIGHT INTEGER Logical partition processor resource weight factor. Thiscolumn is set to zero if the weight factor is X'FFFF'. FromSMF70BPS.

LPAR_WEIGHT_TOT INTEGER Sum of all partition processor resource weight factors. This iscalculated by the record procedure DRL2S070. FromTOTCPWGT for CP and from TOTICFWGT for ICFprocessors.

LPROC_CP_SHARED FLOAT Average number of CP logical processors active for this LPARduring the interval. From LPSHRCP. For z/OS system withWLM (workload manager) active is the average ofSMF70BDA/SMF70DSA.

LPROC_ICF_SHARED FLOAT Average number of ICF logical processors active for thisLPAR during the interval. From LPSHRICF. For z/OS systemwith WLM active is the average of SMF70BDA/SMF70DSA.

LPROC_ONLINE-SEC FLOAT Total logical processor online seconds for this LPAR. FromSMF70INT/1000. For z/OS system is SMF70ONT/ 1000000.

LPROC_SEC FLOAT Available logical processor time, in seconds. This is the timeavailable for all nondedicated processors. Processors CP andICF are considered separately.

MEASURED_SEC FLOAT Measured time period, in seconds. This is the duration of theRMF measurement intervals. From SMF70INT/1000.

MIPS_PER_LOG_CP FLOAT Number of MIPS per single logical CPU.

MIPS_PER_LPAR FLOAT Total number of MIPS per LPAR. The number of MIPS istaken from a specific lookup table MVS_MIPS_T

NONDED_PROCESSORS SMALLINT Total number of processors that were not assigned asdedicated in the processor complex. Processors CP and ICFare considered separately

NUM_CONSUMED_MSU FLOAT Actual number of consumed MSUs. Calculated asSum(SMF70PDT)*3600*16/(SMF70CPA*SMF70INT*1000).

PHYS_PROCESSORS SMALLINT Total number of physical processors (CP+ICF) assigned foruse by PR/SM. From TOTCPPRO+TOTICFPRO.

PHY_PROCESSORS_CP SMALLINT Total number of CP physical processors assigned for use byPR/SM. From TOTCPPRO.

PHY_PROCESSORS_ICF SMALLINT Total number of ICF physical processors assigned for use byPR/SM. From TOTICFPRO.

PHYS_PROC_LPAR FLOAT Total number of physical CPUs utilized in LPAR.

MVS data tables


|

|

|

|

|

|

|

|

|

|

|

|

|

|

|


PROCESSOR_FLAGS CHAR(2) Logical processor flags. 80 = wait state assist enabled; 40 =wait state assist changed; 20 = relative share changed; 10 =partition capping is enabled; and 08 = partition cappingstatus changed. From SMF70VPF.

PRSM_FLAGS CHAR(2) PR/SM flags. 80 = diagnose X'204' failure; 40 = number ofphysical processors changed; 20 = global time slice valuechanged; and 10 = physical partition included. FromSMF70INB.

RECORD_LEVEL SMALLINT SMF record level change number. This column enablesprocessing of SMF record level changes in an existing release.From SMF70SRL.

WEIGHT_ACTUAL FLOAT Actual weighting of the shared processor resources. Validonly for z/OS system with WLM active. Calculated as theaverage of SMF70ACS / SMF70DSA.

WLM_CAPPING_PCT FLOAT Percentage of WLM capping of the partition. Calculated asthe MAX of (SMF70NSW/SMF70DSA) * 100.

MVS data tables


|

|

MVS_MOUNT_D, _MThese tables provide daily and monthly statistics on tape library activity. Theycontain data from SMF type 94 records.

The default retention periods for these tables are:MVS_MOUNT_D 30 daysMVS_MOUNT_M 765 days


DATE k DATE Date when the activity occurred. For the _M table, this is thedate of the first day of the month. From SMF94DTE.

PERIOD_NAME k CHAR(8) Name of the period. This is derived using fields SMF94SID,SMF94DTE and SMF9HHI in the record as parameters in thePERIOD function.


TAPE_LIBRARY k CHAR(12) System managed tape library sequence number. FromSMF94SNO.

AUDIT_OPER_SEC_AVG FLOAT Average amount of time, in seconds, required to perform asingle audit operation. This is the average of SMF94AT3.

AUDITS INTEGER Number of audits. This is the sum of SMF94ATO.

DEMOUNT_OP_SEC_AVG FLOAT Average amount of time, in seconds, required to perform anysingle demount operation. This is the average of SMF94DT3.

DEMOUNTS INTEGER Total number of demounts. This is the sum of SMF94DTO.

DEMOUNTS_PND_AVG FLOAT Average number of demount requests pending. This is theaverage of SMF94DP3.

DRIVES_MOUNTED_AVG FLOAT Average number of drives mounted. This is the average ofSMF94LM3.

EJECT_OPER_SEC_AVG FLOAT Average amount of time, in seconds, required to perform asingle eject operation. This is the average of SMF94ET3.

EJECTS FLOAT Number of ejects. This is the sum of SMF94ETO.

EJECTS_PND_AVG FLOAT Average number of eject requests pending. This is the averageof SMF94EP3.

INDEX_DEMOUNTS INTEGER Number of index demounts. This is the sum of SMF94DIN.

INDEX_MOUNTS INTEGER Number of index mounts. This is the sum of SMF94MIN.

INSERTS INTEGER Number of insert stores. This is the number of volumesmoved from an input station to a location inside the systemmanaged library. This is the sum of SMF94INS.

MOUNTED_SEC_AVG FLOAT Average amount of time, in seconds, that all tape volumeswere mounted on drives. This is the average of SMF94LT3.

MOUNT_OPER_SEC_AVG FLOAT Average amount of time, in seconds, required to perform asingle mount operation. This is the average of SMF94MT3.

MOUNTS INTEGER Number of mounts. This is the sum of SMF94MTO.

MOUNTS_PND_AVG FLOAT Average number of mount requests pending. This is theaverage of SMF94MP3.

POST_DEMOUNTS INTEGER Number of post-demounts. This is the sum of SMF94DPM.

PRE_MOUNTS INTEGER Number of pre-mounts. This is the sum of SMF94MPM.

SAMPLES INTEGER Number of samples. This is the number of records.

SYSTEM_NAME CHAR(8) MVS system name. This is the MVS system name. FromSMF94MVS.

MVS data tables


MVS_OAM_CARTR_DThis table provides data about LCS optical cartridge/volume activities from theOS/390 DFSMS/OAM subsystem. In particular, this table refers to Optical VolumeDemount function invocation. The table contains data from SMF type 85, subtype73 records.



REC_DATE k DATE Date that the record was presented to SMF.


OPT_LIB_NAME k CHAR(8) The real optical library name for the operator-accessibledrive.

OPT_LIB_DEV_NUM k CHAR(4) MVS device number corresponding to the optical library.

VOL_SER k CHAR(6) Volume serial number.

VOL_SER_OPP k CHAR(6) Volume serial number of the opposite side of the opticaldisk.

STG_GROUP_NAME k CHAR(8) Storage group name.

FUNCT_ELAPS_TIME FLOAT Elapsed time of the function in milliseconds (.001 secondunits).

NUM_OBJ_WRIT FLOAT Number of objects written to this optical disk volumewhile it was mounted.

NUM_KB_OBJ_WRIT FLOAT Number of kilobytes of object data written to this opticaldisk volume while it was mounted.

NUM_KB_OBJ_READ FLOAT Number of kilobytes of object data read from this opticaldisk volume while it was mounted.

NUM_KB_OBJ_DEL FLOAT Number of kilobytes of object data deleted from thisoptical disk volume while it was mounted.

NUM_OBJ_DEL FLOAT Number of objects deleted from this optical disk volumewhile it was mounted.

NUM_OBJ_READ FLOAT Number of objects read from this optical disk volumewhile it was mounted.

TIME_MOUNTED FLOAT Elapsed time in milliseconds that the optical disk volumewas mounted.

MVS data tables


MVS_OAM_CARTR_TThis table provides data about LCS optical cartridge/volume activities from theOS/390 DFSMS/OAM subsystem. In particular, this table refers to Optical VolumeDemount function invocation. The table contains data from SMF type 85, subtype73 records.



REC_TIME k TIME Time since midnight (in hundredths of a second) that therecord was presented to SMF.






VOL_SER_OPP k CHAR(6) Volume serial number of the opposite side of the opticaldisk.



NUM_OBJ_WRIT FLOAT Number of objects written to this optical disk volumewhile it was mounted.

NUM_KB_OBJ_WRIT FLOAT Number of kilobytes of object data written to this opticaldisk volume while it was mounted.

NUM_OBJ_READ FLOAT Number of objects read from this optical disk volumewhile it was mounted.

NUM_KB_OBJ_READ FLOAT Number of kilobytes of object data read from this opticaldisk volume while it was mounted.

NUM_OBJ_DEL FLOAT Number of objects deleted from this optical disk volumewhile it was mounted.

NUM_KB_OBJ_DEL FLOAT Number of kilobytes of object data deleted from thisoptical disk volume while it was mounted.

OPT_LIB_DEV_TYPE CHAR(8) Optical library device type.

OPT_DRV_DEV_TYPE CHAR(8) Optical drive device type.

OPT_DRV_NAME CHAR(8) Optical drive name.

OPT_DRV_DEV_NUM CHAR(4) MVS device number corresponding to the optical drive.

TIME_MOUNTED FLOAT Elapsed time in milliseconds that the optical disk volumewas mounted.

MVS data tables


MVS_OAM_DRVVARY_TThis table provides data about LCS optical drive activities from the OS/390DFSMS/OAM subsystem. In particular, this table refers to Drive VaryOnline/Offline function invocation. The table contains data from SMF type 85(subtypes 64, 65) records.







OPT_LIB_DEV_TYPE k CHAR(8) Optical library device type.


OPT_DRV_NAME k CHAR(8) Optical drive name.

OPT_DRV_DEV_TYPE k CHAR(8) Optical drive device type.

OPT_DRV_DEV_NUM k CHAR(4) MVS device number corresponding to the optical drive.

CURR_MOUNT_VOLSER CHAR(6) Volume serial number of the currently mounted volume.

FUNCT_ELAPS_TIME FLOAT Elapsed time of the function in seconds.

LCS_DQ_TIME FLOAT LCS dispatcher-queued time. The amount of time inmilliseconds that this request has spent on the LCSdispatcher queue waiting to be processed.

LCS_EQ_TIME FLOAT LCS execution-queued time. The amount of time inmilliseconds that this request has spent on the LCSexecution queue waiting to be processed.

OPT_MEDIA_TYPE CHAR(14) Optical media type.

OPT_DRV_TYPE CHAR(16) Optical drive type.

OPT_VOL_TYPE CHAR(16) Optical volume type.

STG_GROUP_NAME CHAR(8) Storage group name.

VOL_SER_OPP CHAR(6) Volume serial number of the opposite side of thecurrently mounted volume.

MVS data tables


MVS_OAM_LIBVARY_TThis table provides data about LCS optical drive activities from the OS/390DFSMS/OAM subsystem. In particular, this table refers to Library VaryOnline/Offline function invocation. The table contains data from SMF type 85(subtypes 66, 67) records.







OPT_LIB_DEV_TYPE k CHAR(8) Optical library device type.



LCS_DQ_TIME FLOAT LCS dispatcher-queued time. The amount of time inmilliseconds that this request has spent on the LCSdispatcher queue waiting to be processed.

LCS_EQ_TIME FLOAT LCS execution-queued time. The amount of time inmilliseconds that this request has spent on the LCSexecution queue waiting to be processed.

LCS_TQ_TIME FLOAT LCS library task queue time. The amount of time inmilliseconds that this request has spent on the LCSlibrary queue waiting to be processed. Normally, this fieldrepresents the cartridge transport mechanism wait time,that is, the time spent waiting for the cartridge transportmechanism to become available within the automatedoptical disk library.

LCS_TP_TIME FLOAT LCS library task processing time. The amount of time inmilliseconds that this request took to be processed by thelibrary task. Normally, this field represents the cartridgetransport mechanism service time, that is, the time spentby the cartridge transport mechanism within theautomated optical disk library performing mechanicalmotion to move cartridges within the optical disk library.

MVS data tables


MVS_OAM_OSMC_D, _MThese tables provide data about OAM/OSREQ activity from the OS/390DFSMS/OAM subsystem. The tables contain data from SMF type 85 (subtypes 32,33) records.

The OSMC storage management activities that are supported with these tables are:v Storage group processingv DASD space management processing

The default retention periods for these tables are:MVS_OAM_OSMC_D 30 daysMVS_OAM_OSMC_M 765 days




OBJECT_SG_NAME k CHAR(8) The object or object backup storage group name.

CARTR_EXPIRED FLOAT Number of expired cartridges.

DASD_PO_WRIT FLOAT Number of primary objects written to DASD.

DASD_PO_WRIT_KB FLOAT Number of kilobytes of primary object data written toDASD.

DASD_PO_READ FLOAT Number of primary objects read from DASD.

DASD_PO_READ_KB FLOAT Number of kilobytes of primary object data read fromDASD.

DASD_PO_DEL FLOAT Number of primary objects deleted from DASD.

DASD_PO_DEL_KB FLOAT Number of kilobytes of primary object data deleted fromDASD.

DIR_TBL_ROWS_UPD FLOAT Number of rows updated in the Object Directory table.

DIR_TBL_ROWS_DLT FLOAT Number of rows deleted from the Object Directory table.


OPT_PO_WRIT FLOAT Number of primary objects written to optical.

OPT_PO_WRIT_KB FLOAT Number of kilobytes of primary object data written tooptical.

OPT_PO_READ FLOAT Number of primary objects read from optical.

OPT_PO_READ_KB FLOAT Number of kilobytes of primary object data read fromoptical.

OPT_PO_DEL FLOAT Number of primary objects deleted from optical.

OPT_PO_DEL_KB FLOAT Number of kilobytes of primary object data deleted fromoptical.

OPT_BO_WRIT FLOAT Number of backup objects written to optical.

OPT_BO_WRIT_KB FLOAT Number of kilobytes of backup object data written tooptical.

OPT_BO_READ FLOAT Number of backup objects read from optical.

OPT_BO_READ_KB FLOAT Number of kilobytes of backup object data read fromoptical.

OPT_BO_DEL FLOAT Number of backup objects deleted from optical.

MVS data tables



OPT_BO_DEL_KB FLOAT Number of kilobytes of backup object data deleted fromoptical.

OPT_B2O_WRIT FLOAT Number of backup2 objects written to optical.

OPT_B2O_WRIT_KB FLOAT Number of kilobytes of backup2 object data written tooptical.

OPT_B2O_READ FLOAT Number of backup2 objects read from optical.

OPT_B2O_READ_KB FLOAT Number of kilobytes of backup2 object data read fromoptical.

OPT_B2O_DEL FLOAT Number of backup2 objects deleted from optical.

OPT_B2O_DEL_KB FLOAT Number of kilobytes of backup2 object data deleted fromoptical.

ST4K_ROWS_INS FLOAT Number of rows inserted into the 4K Object Storage table.

ST4K_ROWS_DLT FLOAT Number of rows deleted from the 4K Object Storage table.

ST32K_ROWS_INS FLOAT Number of rows inserted into the 32K Object Storagetable.

ST32K_ROWS_DLT FLOAT Number of rows deleted from the 32K Object Storagetable.

TAPE_BO_WRIT FLOAT Number of backup objects written to tape.

TAPE_BO_WRIT_KB FLOAT Number of kilobytes of backup object data written totape.

TAPE_BO_READ FLOAT Number of backup objects read from tape.

TAPE_BO_READ_KB FLOAT Number of kilobytes of backup object data read fromtape.

TAPE_BO_DEL FLOAT Number of backup objects deleted from tape.

TAPE_PO_WRIT FLOAT Number of primary objects written to tape.

TAPE_PO_WRIT_KB FLOAT Number of kilobytes of primary object data written totape.

TAPE_PO_READ FLOAT Number of primary objects read from tape.

TAPE_PO_READ_KB FLOAT Number of kilobytes of primary object data read fromtape.

TAPE_PO_DEL FLOAT Number of primary objects deleted from tape.

TAPE_PO_DEL_KB FLOAT Number of kilobytes of primary object data deleted fromtape.

TAPE_B2O_WRIT FLOAT Number of backup2 objects written to tape.

TAPE_B2O_WRIT_KB FLOAT Number of kilobytes of backup2 object data written totape.

TAPE_B2O_READ FLOAT Number of backup2 objects read from tape.

TAPE_B2O_READ_KB FLOAT Number of kilobytes of backup2 object data read fromtape.

TAPE_B2O_DEL FLOAT Number of backup2 objects deleted from tape.

TAPE_B2O_DEL_KB FLOAT Number of kilobytes of backup2 object data deleted fromtape.

TAPE_BO_DEL_KB FLOAT Number of kilobytes of backup object data deleted fromtape.

MVS data tables


|

|

|

|

|

|

|

|

|

|

|

|

|

MVS_OAM_OSREQ_TThis table provides data about OAM/OSREQ function invocation from the OS/390DFSMS/OAM subsystem. It contains data from SMF type 85, subtypes 2 to 6records.






OSREQ_FUNCTION k CHAR(8) The OSREQ function that was invoked.

COLLECTION_NAME CHAR(44) Collection name.


MNGMNT_CLASS_NAME CHAR(8) Management class name.

OBJECT_NAME CHAR(44) Object name.

STRG_GROUP_NAME CHAR(8) Storage group name.

STRG_CLASS_NAME CHAR(8) Storage class name.

TRANSACTION_NAME CHAR(8) The transaction name for subtypes 2 to 6: CICS - Thename of the CICS transaction that invoked the OSREQmacro. IMS - The name of the IMS transaction thatinvoked the OSREQ macro. OTHER - This field containsblanks, if the OSREQ macro was invoked from any otherenvironment.

VOL_SER CHAR(6) Volume serial number.

MVS data tables


MVS_OAM_RWD_D, _MThese tables provide data about LCS optical library activities from the OS/390DFSMS/OAM subsystem. In particular, these tables refer to Optical Write, Read,Logical Delete, Physical Delete function invocation. The table contains data fromSMF type 85, subtypes 74 to 77 records.

The default retention periods for these tables are:MVS_OAM_RWD_D 30 daysMVS_OAM_RWD_M 765 days







REQUEST k CHAR(16) LCS tape request.


TOT_NUM_OBJ FLOAT Total number of objects in this request. The maximumvalue for this field is 280.

TOT_NUM_KB_OBJ FLOAT Total number of kilobytes of object data in this request.

TOT_NUM_OBJ_SUCC FLOAT Total number of objects in this request that processedsuccessfully.

TOT_NO_KB_SUCC FLOAT Total number of kilobytes of object data in this requestthat processed successfully.

MVS data tables


MVS_OAM_TAPDMNT_D, _MThese tables provide data about OAM tape activities from the OS/390DFSMS/OAM subsystem. In particular, these tables refer to OAM Tape VolumeDemount (Subtype 87) function invocation. The table contains data from SMF type85, subtype 87 records.

The default retention periods for these tables are:MVS_OAM_TAPDMNT_D 30 daysMVS_OAM_TAPDMNT_M 765 days





OBJ_STG_GR_NAME k CHAR(8) Name of the Object or Object Backup storage group.

TAPE_DEV_NUM k CHAR(4) MVS device number that corresponds to the tape drive onwhich the volume was mounted.

TAPE_V_UNIT_NAME k CHAR(8) Unit name associated with the tape volume and used toallocate the tape drive.

TAPE_VOL_TYPE k CHAR(8) Tape volume type.


NO_OBJ_WRIT FLOAT Number of objects written to this tape volume while itwas mounted.

NO_KB_OBJ_WRIT FLOAT Number of logical kilobytes of object data written to thistape volume while it was mounted.

NO_OBJ_READ FLOAT Number of objects read from this tape volume while itwas mounted.

NO_KB_OBJ_READ FLOAT Number of kilobytes of object data read from this tapevolume while it was mounted.

TIME_MNT FLOAT Elapsed time in milliseconds that the tape volume wasmounted, measured from the time that the first DFPOPEN macro completed to the time that the tape volumewas unallocated by an SVC 99 dynamic unallocationrequest.

MVS data tables


MVS_OAM_TAPERWD_D, _MThese tables provide data about LCS tape activities from the OS/390DFSMS/OAM subsystem. In particular, these tables refer to LCS Tape Write andRead Request function invocation. The table contains data from SMF type 85(subtypes 78, 79, 88) records.

The default retention periods for these tables are:MVS_OAM_TAPERWD_D 30 daysMVS_OAM_TAPERWD_M 765 days




TAPE_DRV_NAME k CHAR(8) Tape drive unit name.

TAPE_DEV_NUM k CHAR(4) MVS device number of the tape drive.

STG_GROUP_NAME k CHAR(8) Name of the Object or Object Backup storage group towhich the tape volume belongs.

REQUEST k CHAR(16) LCS tape request.

FUNCT_ELAPS_TIME FLOAT Elapsed time of the function in milliseconds (.001secondunits).

TOT_NUM_OBJ FLOAT Total number of objects in this request. The maximumvalue for this field is 280. When there are 280 objects inthis record, the maximum SMF record size for subtype 78is 32 744 bytes.

TOT_NUM_KB_OBJ FLOAT Total number of kilobytes of object data in this request.

TOT_NUM_OBJ_SUCC FLOAT Total number of objects in this request that processedsuccessfully.

TOT_NO_KB_SUCC FLOAT Total number of kilobytes of object data in this requestthat processed successfully.

MVS data tables


MVS_OMVSADDR_TThis table provides detailed statistics for OpenMVS address space activity. Itcontains data from SMF type 30, subtype 5 records processed through a recordprocedure (DRL2S30O). It contains one row for each OpenMVS process, withineach address space, with I/O statistics, CPU usage and process identification.




JOB_TIMESTAMP k TIMESTAMP Date and time when the job, TSO session, started task, orAPPC/MVS transaction program was recognized by thereader. From SMF30RSD and SMF30RST.

JOB_NAME k CHAR(8) Job name, TSO user ID, name of the started task, or nameof the APPC/MVS session. From SMF30JBN.


USER_GROUP k CHAR(8) Name of the group of the user. From GROUP_NAME inthe USER_GROUP lookup table.

PROCESS_ID k INTEGER OpenMVS process ID. From SMF30OPI.

PROCESS_GID k INTEGER OpenMVS process group ID. From SMF30OPG.

PROCESS_UID k INTEGER OpenMVS process user ID. From SMF30OUI.

PROCESS_UGID k INTEGER OpenMVS process user group ID. From SMF30OUG.

PROCESS_SID k INTEGER OpenMVS process session ID. From SMF30SID.

PARENT_ID k INTEGER OpenMVS parent ID. From SMF30OPP.

CPU_TIME FLOAT Total amount of CPU time accumulated by OpenMVSservices requested by the processes. This is the sum ofSMF30OST/100.

DIRECTORY_BLOCK FLOAT Total number of directory blocks read for the processes.This is the sum of SMF30ODR.

MSGQUEUE_SENT FLOAT Total number of bytes that the message queue sent. This isthe sum of SMF30OMS.

MSGQUEUE_RECEIVE FLOAT Total number of bytes that the message queue received.This is the sum of SMF30OMR.


NET_SOCKET_READ FLOAT Total number of reads for network sockets. This is the sumof SMF30OKR.

NET_SOCKET_WRITE FLOAT Total number of writes for network sockets. This is the sumof SMF30OKW.

NUMBER_SYNC FLOAT Total number of sync () functions that were called. This isthe sum of SMF30OSY.

PATHNAME_LOOK_LFS FLOAT Total number of pathname look calls to the logical filesystem. This is the sum of SMF30OLL.

PATHNAME_LOOK_PFS FLOAT Total number of pathname look calls to the physical filesystem. This is the sum of SMF30OLP.

PATHNAME_GEN_LFS FLOAT Total number of pathname generation calls to the logicalfile system. This is the sum of SMF30OGL.

MVS data tables



PATHNAME_GEN_PFS FLOAT Total number of pathname generation calls to the physicalfile system. This is the sum of SMF30OGP.

PIPE_READ FLOAT Total number of I/O blocks read for pipe files by theprocesses. This is the sum of SMF30OPR.

PIPE_WRITE FLOAT Total number of I/O blocks written for pipe files by theprocesses. This is the sum of SMF30OPW.


SYSCALL_NUMBER FLOAT Total number of system calls requested by the processes.This is the sum of SMF30OSC.

STD_FILE_READ FLOAT Total number of I/O blocks read for standard files by theprocesses. This is the sum of SMF30OFR.

STD_FILE_WRITE FLOAT Total number of I/O blocks written for standard files bythe processes. This is the sum of SMF30OFW.

SPECIAL_FILE_READ FLOAT Total number of I/O blocks read for special files by theprocesses. This is the sum of SMF30OSR.

SPECIAL_FILE_WRITE FLOAT Total number of I/O blocks written for special files by theprocesses. This is the sum of SMF30OSW.

MVS data tables


MVS_OMVSADIS_TThis table provides detailed statistics for OpenMVS address space activity. Itcontains data from SMF type 30 (subtype 2,3) records processed through a recordprocedure (DRL2S30O). It contains one row for each OpenMVS process, withineach address space, with I/O statistics, CPU usage and process identification.




JOB_TIMESTAMP k TIMESTAMP Date and time when the job, TSO session, started task, orAPPC/MVS transaction program was recognized by thereader. From SMF30RSD and SMF30RST.

JOB_NAME k CHAR(8) Job name, TSO user ID, name of the started task, or nameof the APPC/MVS session. From SMF30JBN.


USER_GROUP k CHAR(8) Name of the group of the user. From GROUP_NAME inthe USER_GROUP lookup table.

PROCESS_ID k INTEGER OpenMVS process ID. From SMF30OPI.

PROCESS_GID k INTEGER OpenMVS process group ID. From SMF30OPG.

PROCESS_UID k INTEGER OpenMVS process user ID. From SMF30OUI.

PROCESS_UGID k INTEGER OpenMVS process user group ID. From SMF30OUG.

PROCESS_SID k INTEGER OpenMVS process session ID. From SMF30SID.

PARENT_ID k INTEGER OpenMVS parent ID. From SMF30OPP.

CPU_TIME FLOAT Total amount of CPU time accumulated by OpenMVSservices requested by the processes. This is the sum ofSMF30OST/100.

DIRECTORY_BLOCK FLOAT Total number of directory blocks read for the processes.This is the sum of SMF30ODR.

MSGQUEUE_SENT FLOAT Total number of bytes that the message queue sent. This isthe sum of SMF30OMS.

MSGQUEUE_RECEIVE FLOAT Total number of bytes that the message queue received.This is the sum of SMF30OMR.


NET_SOCKET_READ FLOAT Total number of reads for network sockets. This is the sumof SMF30OKR.

NET_SOCKET_WRITE FLOAT Total number of writes for network sockets. This is the sumof SMF30OKW.

NUMBER_SYNC FLOAT Total number of sync () functions that were called. This isthe sum of SMF30OSY.

PATHNAME_GEN_LFS FLOAT Total number of pathname generation calls to the logicalfile system. This is the sum of SMF30OGL.

PATHNAME_GEN_PFS FLOAT Total number of pathname generation calls to the physicalfile system. This is the sum of SMF30OGP.

PATHNAME_LOOK_LFS FLOAT Total number of pathname look calls to the logical filesystem. This is the sum of SMF30OLL.

MVS data tables



PATHNAME_LOOK_PFS FLOAT Total number of pathname look calls to the physical filesystem. This is the sum of SMF30OLP.

PIPE_READ FLOAT Total number of I/O blocks read for pipe files by theprocesses. This is the sum of SMF30OPR.

PIPE_WRITE FLOAT Total number of I/O blocks written for pipe files by theprocesses. This is the sum of SMF30OPW.

SYSCALL_NUMBER FLOAT Total number of system calls requested by the processes.This is the sum of SMF30OSC.

STD_FILE_READ FLOAT Total number of I/O blocks read for standard files by theprocesses. This is the sum of SMF30OFR.

STD_FILE_WRITE FLOAT Total number of I/O blocks written for standard files bythe processes. This is the sum of SMF30OFW.

SPECIAL_FILE_READ FLOAT Total number of I/O blocks read for special files by theprocesses. This is the sum of SMF30OSR.

SPECIAL_FILE_WRITE FLOAT Total number of I/O blocks written for special files by theprocesses. This is the sum of SMF30OSW.


MVS data tables


MVS_PRINTER_D, _MThese tables provide daily and monthly statistics on MVS printer activity. Theycontain JES2/JES3 output writer, external writer, and Print Services Facility™ (PSF)data from SMF type 6 records.

These tables are updated by the MVS_PRINTER_LOC, MVS_SYSPLEX, andUSER_GROUP lookup tables.

The default retention periods for these tables are:MVS_PRINTER_D 30 daysMVS_PRINTER_M 765 days


DATE k DATE Date when the printer activities occurred. For the _M table, thisis the date of the first day of the month. From SMF6WSD.

PERIOD_NAME k CHAR(8) Name of the period. This is derived using fields SMF6SID,SMF6WSD, and SMF6WST as parameters in the PERIODfunction.


PRINTER_NAME k CHAR(8) Name of the printer. For JES2 or JES3, this is the logical outputdevice name. For Print Services Facility, this is the VTAMlogical unit name or printer device name. For external writers,this is set to X'0000' (blank). From SMF6OUT.

PRINTER_LOCATION k CHAR(12) Name of the place where the printer is located. FromPRINTER_LOCATION in the MVS_PRINTER_LOC lookuptable.

FORM_NUMBER k CHAR(8) Output form number. From SMF6EFMN.

USER_ID k CHAR(8) User ID. From SMF6USID.

USER_GROUP k CHAR(8) Name of the group that the user belongs to. FromGROUP_NAME in the USER_GROUP lookup table; if no matchis found, this column gets its value from SMF6USID.


DATASETS INTEGER Number of data sets processed by the printer. If multiple copiesare produced, each copy is counted. This is the sum ofSMF6NDS.

ELAPSED_WRITER_SEC FLOAT Writer elapsed time, in seconds. Calculated as the sum of thetime intervals from SMF6WSD and SMF6WST to SMF6DTE andSMF6TME. This column is not useful for buffered printers suchas the IBM 3820.

FEET_PRINTED INTEGER Number of feet of paper printed by the printer. For printersthat do not report paper size, this column is set to zero. It isonly valid for the Print Services Facility. This is the sum ofSMF6FEET.

JOBS INTEGER Number of jobs processed by the printer. A job here means anyunique job-form-sysout combination; that is, one JES job canproduce several jobs. This is the count of SMF type 6 records.

JOBS_RESTARTED INTEGER Number of jobs that were restarted for the printer. For JES2,this is the count of records where bit 3 or 4 of SMF6DCI is set.For JES3, Print Services Facility, and external writers, this is thecount of records where bit 3, 4, or 5 of SMF6DCI is set.

MVS data tables



LG_PAGES_PRINTED INTEGER Number of logical pages processed. The logical page is an areadefined by the page definition for line data or by structuredfields for MO:DCA data. This value is new with Print ServicesFacility Version 3 Release 1.0. It is the sum of SMF6LPGE.

LINES_PRINTED INTEGER Number of lines printed by the printer. For external writers,this column is set to zero. This is the sum of SMF6NLR.

PAGES_PRINTED INTEGER Approximate number of physical pages printed by the printer.This is the sum of SMF6PGE.

SIDES_PRINTED INTEGER Number of sides of sheets of paper printed by the printer,including duplicates and separators. This is the number oflogical impressions. It is only valid for the Print ServicesFacility. This is the sum of SMF6IMPS.


TOTAL_BYTES_SENT INTEGER Total bytes sent during the file transfer of the datasets to thetarget system. Introduced with a Type 6 enhancement, it isvalid for Print Services Facility and PrintWay™. For PrintWay itis the number of bytes transmitted or attempted to transmit.Calculated as the sum of SMF6BYTE.

MVS data tables


MVS_PROGRAM_MThis table provides monthly statistics on programs used by jobs and started tasks.It contains data from SMF type 30, subtype 4 records.




DATE k DATE Date when the initiator selected the steps. This is the date ofthe first day of the month. From SMF30STD.

PERIOD_NAME k CHAR(8) Name of the period. This is derived using fields SMF30SID,SMF30STD, and SMF30SIT from the record as parameters inthe PERIOD function.


PROGRAM_NAME k CHAR(8) Program name. From SMF30PGM.

BLOCKS_TRANSFERRED FLOAT Total number of blocks transferred. This is the accumulatedEXCP counts. This is the sum of SMF30TEP.

CPU_LOST_SECONDS FLOAT Amount of processor time spent for the steps that did notcomplete normally, in seconds. This is the sum of all validCPU times, where bit 6 or bit 7 of SMF30STI is 1.

CPU_TOTAL_SECONDS FLOAT Total amount of processor time spent for the program, inseconds. This is the sum of all valid CPU times.

ELAPSED_SECONDS FLOAT Total elapsed time, in seconds. This is the sum of the timeintervals from SMF30STD and SMF30SIT to SMF30DTE andSMF30TME.

LOST_ELAPSED_SEC FLOAT Amount of elapsed time spent for the steps that did notcomplete normally, in seconds. This is the sum of the timeintervals from SMF30STD and SMF30SIT to SMF30DTE andSMF30TME, where bit 6 or bit 7 of SMF30STI is 1.

STEPS_FLUSHED INTEGER Number of steps flushed. This is the number of times bit 6 ofSMF30STI is 0, and bit 7 of SMF30STI is 1.

STEPS_NORMAL INTEGER Number of steps that completed normally. This is the numberof times bits 6 and 7 of SMF30STI are zeros.

STEPS_TOTAL INTEGER Total number of steps. This is the count of SMF30SCC.


SYSTEM_ABENDS INTEGER Number of system abends. This is the number of times bit 6of SMF30STI is 1, and the first hexadecimal digit ofSMF30SCC is 0.

USER_ABENDS INTEGER Number of user abends. This is the number of times bit 6 ofSMF30STI is 1, and the first hexadecimal digit of SMF30SCCis 8.

MVS data tables


MVS_SYSTEM_H, _D, _MThese tables provide hourly statistics on processor activity, paging and swappingactivities, IPLs, and lost SMF data. They contain data from SMF types 0, 7, 70, 71,and 72 records.

The default retention periods for these tables are:MVS_SYSTEM_H 45 daysMVS_SYSTEM_D 45 daysMVS_SYSTEM_M 765 days

These tables are updated by the MVS_MIPS_T lookup table.


DATE k DATE Date when the activity occurred. For the _M table, this is thedate of the first day of the month. From SMF0DTE orSMF7STD; or calculated from SMFxxDAT, SMFxxIST, andSMFxxINT; (where xx is the record type 70, 71, or 72).

TIME k TIME Time (rounded down to the nearest hour) when the activityoccurred. It applies only to the _H table. From SMF0TME orSMF7STM; or calculated from SMFxxDAT, SMFxxIST, andSMFxxINT; (where xx is the record type 70, 71, or 72).

PERIOD_NAME k CHAR(8) Name of the period. This is derived using the SMF systemID, date, and time in the record as parameters in thePERIOD function.

MVS_SYSTEM_ID k CHAR(4) MVS system ID. This is the SMF system ID. From SMF0SID,SMF7SID, SMF70SID, SMF71SID, or SMF71SID.

BATCH_JOBS_AVG FLOAT Average number of batch jobs run for the system. Calculatedas the average of SMF70BTT/SMF70SAM.

CAPACITY_COEFF FLOAT Coefficient used to calculate total processor capacity.Calculated as the maximum of SMF72CSD/16 000000/SMF72ADJ or when in workload management goalmode, as the maximum of R723MCPU*1600/R723MADJ.This column applies only to the _H table.

CAPACITY_CPU_SU FLOAT Total processor capacity, in processor service units.Calculated as the sum ofSMF72INT*SMF72CSD/16000/SMF72ADJ or when inworkload management goal mode, as the maximum ofSMF72INT*R723MCPU*1.6/R723MADJ. This column appliesonly to the _M table.

CPU_BUSY_SEC FLOAT Processor busy time for all processors, in seconds. This iscalculated as the sum of (SMF70INT/1000) -(SMF70WAT*0.000001/4096); or (SMF70PDT*0.000001) -(SMF70WAT*0.000001/4096); or SMF70PDT*0.000001.

CPU_BUSY_MIPS FLOAT MIPS for single CPU. Calculated as(MIPS/SMF70BNP)*CPU_BUSY_SEC. MIPS is a columncontained in the MVS_MIPS_T lookup table. SMF70BNP isthe total number of CPUs.

CPU_LOAD_MAX_PCT FLOAT Maximum processor load, in percent. Calculated as themaximum of (CPU_BUSY_SEC/(SMF70INT/1000))*100.

CPU_LOAD_MIN_PCT FLOAT Minimum processor load, in percent. Calculated as theminimum of (CPU_BUSY_SEC/(SMF70INT/1000))*100.

CPU_ONLINE_SEC FLOAT Sum of the measured time period times the number ofonline processors, in seconds. Calculated as the sum ofSMF70INT/1000.

MVS data tables


|

|


FRAMES_CSA_CS_AVG FLOAT Average number of CSA frames in central storage. This isthe average of SMF71AVP.

FRAMES_CSA_ES_AVG FLOAT Average number of CSA frames in expanded storage. This isthe average of SMF71CAE.

FRAMES_CS_AVG FLOAT Average number of available frames in central storage. Thisis the average of SMF71AVF.

FRAMES_CS_MAX FLOAT Maximum number of available frames in central storage.This is the average of SMF71MXF.

FRAMES_CS_MIN FLOAT Minimum number of available frames in central storage.This is the average of SMF71MNF.

FRAMES_ES_AVG FLOAT Average number of available frames in expanded storage.This is the average of SMF71ASA.

FRAMES_ES_MAX FLOAT Maximum number of available frames in expanded storage.This is the average of SMF71AMX.

FRAMES_ES_MIN FLOAT Minimum number of available frames in expanded storage.This is the average of SMF71AMN.

FRAMES_LPA_CS_AVG FLOAT Average number of LPA frames in central storage. This is theaverage of SMF71ALP.

FRAMES_LPA_ES_AVG FLOAT Average number of LPA frames in expanded storage. This isthe average of SMF71LAE.

FRAMES_LSQA_CS_AVG FLOAT Average number of LSQA frames in central storage. This isthe average of SMF71ALR.

FRAMES_LSQA_ES_AVG FLOAT Average number of LSQA frames in expanded storage. Thisis the average of SMF71ALE.

FRAMES_NUCLEUS_AVG FLOAT Average number of frames in the nucleus. This is theaverage of SMF71FIN.

FRAMES_SQA_CS_AVG FLOAT Average number of SQA frames in central storage. This isthe average of SMF71ASR.

FRAMES_SQA_ES_AVG FLOAT Average number of SQA frames in expanded storage. This isthe average of SMF71ASE.

FRAMES_USER_CS_AVG FLOAT Average number of private frames in central storage. This isthe average of SMF71AVS.

FRAMES_USER_ES_AVG FLOAT Average number of private frames in expanded storage. Thisis the average of SMF71RAE.

IN_AVG FLOAT Average number of IN address spaces. This is a count of allswapped-in address spaces including address spaces readyto execute and not ready to execute. Calculated as theaverage of SMF70ITT/SMF70SAM.

IPL_COUNT SMALLINT Number of IPLs for the system. This is the count of SMFtype 0 records.

MEASURED_SEC FLOAT Measured time period, in seconds. This is the duration ofthe RMF measurement interval. Calculated as the sum ofSMF70INT/1000.

OUT_READY_AVG FLOAT Average number of out and ready address spaces.Calculated as the average of SMF70OTT/SMF70SAM.

PAGEINS INTEGER Number of non-VIO, non-swap, and hiperspace page-ins.Calculated as the sum of (SMF71PIN + SMF71HIN).

PAGEINS_VIO INTEGER Number of VIO page-ins. This is the sum of SMF71VIN.

MVS data tables



PAGEOUTS INTEGER Number of non-VIO, non-swap, and hiperspace page-outs.Calculated as the sum of (SMF71POT + SMF71HOT).

PAGEOUTS_VIO INTEGER Number of VIO page-outs. This is the sum of SMF71VOT.

PAGES_MIGRATED INTEGER Number of pages migrated from expanded storage toauxiliary storage. This is the sum of SMF71PEA.

PAGES_MOVED INTEGER Number of pages moved to expanded storage. This is thesum of SMF71PES.

PAGES_READ FLOAT Number of pages read from expanded storage. This is thesum of SMF71RES.

PAGES_SWAPPED_IN INTEGER Number of pages swapped in. This is the sum of SMF71SIN.

PAGES_SWAPPED_OUT INTEGER Number of pages swapped out. This is the sum ofSMF71SOT.

RECORDS_LOST INTEGER Number of SMF records lost because no SMF data sets wereavailable for recording. This is the sum of SMF7NRO.

RECORDS_LOST_HOURS FLOAT Number of hours SMF records were lost because no SMFdata sets were available for recording. Calculated from thetime stamp as (SMF7STD and SMF7STM - SMF7DTE andSMF7TME)/3600.

SAMPLES_SMF70 FLOAT Number of RMF samples taken for processor activity. This isthe sum of SMF70SAM.

SAMPLES_SMF71 FLOAT Number of RMF samples taken for paging activity. This isthe sum of SMF71SAM.

SRB_SECONDS FLOAT SRB execution time, in seconds. Calculated asSMF72STS*SMF72ADJ/16 000 000/SMF72SSD, or when inworkload management goal mode, asR723CSRB*R723MADJ/1600/R723MSRB.

STARTED_TASKS_AVG FLOAT Average number of started tasks for the system. Calculatedas the average of SMF70STT/SMF70SAM.

SWAP_SEQUENCES INTEGER Number of address space swap sequences. A swap sequenceconsists of an address space swap-out and swap-in. This isthe sum of SMF71SSQ.

SYSPLEX_NAME CHAR(8) Sysplex name. This is the name of the sysplex. FromSMF70XNM.


TCB_SECONDS FLOAT TCB execution time, in seconds. Calculated asSMF72CTS*SMF72ADJ/16 000 000/SMF72CSD, or when inworkload management goal mode, asR723CCPU*R723MADJ/1600/R723MCPU.

TSO_USERS_AVG FLOAT Average number of TSO users for the system. Calculated asthe average of SMF70TTT/SMF70SAM.

TSO_USERS_MAX INTEGER Maximum number of concurrent TSO users for the system.This is the maximum of SMF70TMM.

MVS data tables


MVS_TAPE_MThis table provides monthly statistics on magnetic tape volumes. It contains datafrom SMF type 21 records.



DATE k DATE Date when the records were moved to the SMF buffer. This isthe date of the first day of the month. From SMF21DTE.

PERIOD_NAME k CHAR(8) Name of the period. This is derived using fields SMF21SID,SMF21DTE, and SMF21TME from the record as parameters inthe PERIOD function.

MVS_SYSTEM_ID k CHAR(4) MVS system ID. From SMF21SID.

VOLSER k CHAR(8) Volume serial number. From SMF21VOL.

DEVICE_NUMBER k CHAR(4) Device number. From SMF21CA.

BYTES_READ_KB INTEGER Number of kilobytes read. Calculated as the sum of SMF21BR*4.

BYTES_WRITTEN_KB INTEGER Number of kilobytes written. Calculated as the sum ofSMF21BW*4.

CLEANER_ACTIONS INTEGER Number of cleaner actions. This is the sum of SMF21CLN.

DEMOUNTS INTEGER Number of times a data set on magnetic tape was demounted.This is the count of SMF type 21 records.

DENSITY INTEGER Density of the magnetic tape. This can be 200, 556, 800, 1600, or6250 bpi. From SMF21DEN.

ERASE_GAPS INTEGER Number of erase gaps. This is the sum of SMF21ERG.

NOISE_BLOCKS INTEGER Number of noise blocks. This is the sum of SMF21NB.

NUMBER_OF_IO INTEGER Number of I/Os initiated on the current volume. Valid only ifSMF21LB is on. Calculated as the sum of SMF21LST.

PERM_READ_ERRORS INTEGER Number of permanent read errors. This is the sum of SMF21PR.

PERM_WRITE_ERRORS INTEGER Number of permanent write errors. This is the sum ofSMF21PW.

SSCH_COUNT INTEGER Number of SSCH instructions. This is the sum of SMF21SIO.

TEMP_READ_ERRORS INTEGER Number of temporary read errors. Calculated as the sum ofSMF21TR + SMF21TRF + SMF21TRB.

TEMP_WRITE_ERRORS INTEGER Number of temporary write errors. Calculated as the sum ofSMF21TW + SMF21TWF.

MVS data tables


MVS_VTS_CONFThis table provides daily configuration data on Virtual Tape Server activity. Itcontains data from SMF type 94 records.



DATE k DATE Date when the activity occurred.

HOUR k TIME Time when the activity occurred.

MVS_SYSTEM_ID k CHAR(4) This is the SMF system ID.

TAPE_LIBRARY k CHAR(12) System managed tape library sequence number.

LIB_SEQ_NUM k CHAR(5) Library sequence number of the library segment for which theVTS statistics are being reported.

PHY_TAPE_DEV_INST INTEGER Number of underlying physical tape devices currently installed inthe VTS subsystem.

PHY_TAPE_DEV_AVAI INTEGER Number of underlying physical tape devices currently availablefor use by the VTS subsystem.

SYSTEM_NAME CHAR(8) This is the MVS system name.

VIRT_DEV_CONF INTEGER The number of virtual devices configured in this VTS at the timethe request for statistics was received (current).

VTS_TVC_NUM FLOAT The number of virtual volumes in Tape Volume Cache at the endof reported period.

MVS data tables


MVS_VTS_H, _D, _MThis table provides hourly, daily, and monthly statistics on Virtual Tape Serveractivity. It contains data from SMF type 94 records.

The default retention periods for this table are:MVS_VTS_H 7 daysMVS_VTS_D 30 daysMVS_VTS_M 765 days


DATE k DATE Date when the workload activity occurred. For the _M table,this is the date of the first day of the month.

HOUR k TIME Time when the activity occurred.

MVS_SYSTEM_ID k CHAR(4) This is the SMF system ID.

TAPE_LIBRARY k CHAR(12) System managed tape library sequence number.

LIB_SEQ_NUM k CHAR(5) Library sequence number of the library segment for which theVTS statistics are being reported.

BYTES_HOSTCH_WRITE FLOAT The total number of bytes written successfully through hostchannels to virtual volumes in an integral multiple of 4096bytes during the reported period. If the number of byteswritten is not an integer multiple of 4096, the number isrounded up.

BYTES_HOSTCH_READ FLOAT The total number of bytes read successfully through hostchannels to virtual volumes in an integral multiple of 4096bytes during the reported period. If number of bytes written isnot an integer multiple of 4096, the number is rounded up.

BYTES_PHYATT_WRITE FLOAT The total number of bytes written successfully by VTS to itsattached physical drives, in an integral multiple of 4096 bytes,during the reported period. If number of bytes written is notan integer multiple of 4096, the number is rounded up.

BYTES_PHYATT_READ FLOAT The total number of bytes read successfully by VTS to itsattached physical drives, in an integral multiple of 4096 bytes,during the reported period. If number of bytes written is notan integer multiple of 4096, the number is rounded up.

IART_FR_MNT_AVG_T REAL IART Average Fast Ready Mount Time. Calculated as FIRSToccurrence of S94OPM_IARTAFRT.

IART_FR_MOUNTS INTEGER IART Fast-Ready Mounts. Calculated as FIRST occurrence ofS94OPM_IARTFRM.

IART_CAHTMNT_AVG_T REAL IART Average Cache Hit Mount Time. Calculated as FIRSToccurrence of S94OPM_IARTCHMT.

IART_CACHIT_MOUNTS INTEGER IART Cache Hit Mounts. Calculated as FIRST occurrence ofS94OPM_IARTCHM.

IART_CAMSMNT_AVG_T REAL IART Average Cache Miss Mount Time. Calculated as FIRSToccurrence of S94OPM_IARTCMMT.

IART_CACMIS_MOUNTS INTEGER IART Cache Miss Mounts. Calculated as FIRST occurrence ofS94OPM_IARTCMM.

MB_WRN_PRMRY_POOL REAL Data Written to a Primary Pool. Calculated as the sum ofS94OPM_PPWRITN1 and S94OPM_PPWRITN2.

MB_WRN_SCNDRY_POOL REAL Data Written to a Secondary Pool. Calculated as the sum ofS94OPM_SPWRITN1 and S94OPM_SPWRITN2.

MVS data tables


|

|

|

|

|

|

|

|


PHY_TAPE_DEV_MAX FLOAT Maximum number of underlying physical tape devicesmounted concurrently in this VTS during the reported period.

PHY_TAPE_DEV_MIN FLOAT Minimum number of underlying physical tape devicesmounted concurrently in this VTS during the reported period.

PHY_TAPE_DEV_AVG FLOAT Average number of underlying physical tape devices mountedconcurrently in this VTS during the reported period.

PHY_MOUNT_MAX_SEC FLOAT Maximum time, in seconds, used by the library to perform amount request for a physical drive in the VTS in the reportedperiod.

PHY_MOUNT_MIN_SEC FLOAT Minimum time, in seconds, used by the library to perform amount request for a physical drive in the VTS in the reportedperiod.

PHY_MOUNT_AVG_SEC FLOAT Minimum time, in seconds, used by the library to perform amount request for a physical drive in the VTS in the reportedperiod.

PHY_STAGE_MOUNT FLOAT The number of physical mount requests completed in thereported period to satisfy stage mounts.

PHY_MIGRA_MOUNT FLOAT The number of physical mount requests completed in thereported period to satisfy migrate requests.

PHY_RECLA_MOUNT FLOAT The number of physical mount requests completed in thereported period to satisfy reclamation mounts.

SYSTEM_NAME CHAR(8) This is the MVS system name.

VIRT_DEV_MAX FLOAT The maximum number of virtual drives that wereconcurrently mounted in this VTS during the reported period.

VIRT_DEV_MIN FLOAT The minimum number of virtual drives that were concurrentlymounted in this VTS during the reported period.

VIRT_DEV_AVG FLOAT The average number of virtual drives that were concurrentlymounted in this VTS during the reported period.

VIRT_DRIVE_MAX_SEC FLOAT The maximum time, in seconds, that a virtual drive wasmounted in this VTS during the reported period.

VIRT_DRIVE_MIN_SEC FLOAT The minimum time, in seconds, that a virtual drive wasmounted in this VTS during the reported period.

VIRT_DRIVE_AVG_SEC FLOAT The average time, in seconds, that a virtual drive wasmounted in this VTS during the reported period.

VIRT_MOUNT_MAX_SEC FLOAT The maximum time, in seconds, used to complete a mountrequest on a virtual drive in the reported period.

VIRT_MOUNT_MIN_SEC FLOAT The minimum time, in seconds, used to complete a mountrequest on a virtual drive in the reported period.

VIRT_MOUNT_AVG_SEC FLOAT The average time, in seconds, used to complete a mountrequest on a virtual drive in the reported period.

VTS_FRF_NUM FLOAT The number of virtual mounts, in the reported period, usingthe VTS Fast-Ready facility.

VTS_MOUNT_SPEC_VOL FLOAT The number of virtual mounts, in the reported period, thatwere completed for specific requested volume found residentin Tape Volume Cache (specific mount hits).

VTS_MOUNT_SPEC_LOG FLOAT The number of virtual mounts, in the reported period, thatwere completed for specific requested logical volume stagedfrom a physical tape back into Tape Volume Cache.

MVS data tables



VTS_PREMIGRATION FLOAT The number of virtual volumes for which a pre-migrateoperation was completed in the reported period.

VTS_TVC_AVG_AGE FLOAT The average age in minutes of virtual volumes in TapeVolume Cache at the end of the reported period.

VTS_TVC_SIZE_AVG FLOAT The average size of virtual volumes in Tape Volume Cache inan integral multiple of 1 048 576 bytes (1 MB), at the end ofthe reported period. Virtual volumes smaller than 1 MB arerounded up to 1 MB.

VTS_TVC_NUM FLOAT The number of virtual volumes in Tape Volume Cache at theend of the reported period.

VTS_BYTES_ACTIVE FLOAT The number of bytes of active data managed by the VTS in anintegral multiple of 1 048 576 bytes (1 MB), as determined asof the previous midnight.

VTS_LOGVOL_ACTIVE FLOAT The number of logical volumes managed by the VTS thatcontain active data as of the previous midnight.

VTS_TOTAL_STOR_CAP FLOAT The total estimated amount of storage capacity provided bythe empty 3590 cart managed by VTS, in an integral multipleof 1 048 576 bytes (1 MB) as of the previous midnight.

VTS_ENH_BSRAT SMALLINT Backstore compression ratio. From S94BSRAT.

VTS_ENH_HARAT SMALLINT Host adapter compression ratio. From S94BHRAT.

VTS_ENH_TVCS SMALLINT Tape volume cache size. From S94TVCS.

VTS_ENH_ESCON® SMALLINT Number of ESCON channels. From S94ESCON.

VTS_ENH_SCSI SMALLINT Number of SCSI channels. From S94SCSI.

VTS_ENH_NUMBS SMALLINT Channel blocks written. From S94NUMBS.

VTS_ENH_0KB SMALLINT Percentage of 0 to 2K channel blocks written. From S940KB.

VTS_ENH_2KB SMALLINT Percentage of greater than 2K to 4K channel blocks written.From S942KB.





VTS_ENH_64KB SMALLINT Percentage of greater than 64K channel blocks written. FromS9464KB.

VTS_ENH_RCPRT SMALLINT Recall predominate throttling percentage. From S94RCPRT.

VTS_ENH_WROVT SMALLINT Write overrun predominate throttling percentage. FromS94WROVT.

VTS_ENH_AVCRT FLOAT Average recall throttle value. From S94AVRCT.

VTS_ENH_AVWOT FLOAT Average write overrun throttle value. From S94AVWOT.

VTS_ENH_TOTAT FLOAT Overall average throttle value. From S94TOTAT.

VTS_ENH_MAXFR SMALLINT Maximum fast-ready mount time. From S94MAXFR.

VTS_ENH_MINFR SMALLINT Minimum fast-ready mount time. From S94MINFR.

VTS_ENH_AVGFR FLOAT Average fast-ready mount time. From S94AVGFR.

MVS data tables



VTS_ENH_MAXCH SMALLINT Maximum cache-hit mount time. From S94MAXCH.

VTS_ENH_MINCH SMALLINT Minimum cache-hit mount time. From S94MINCH.

VTS_ENH_AVGCH FLOAT Average cache-hit mount time. From S94AVGCH.

VTS_ENH_MAXRM SMALLINT Maximum recall-mount time. From S94MAXRM.

VTS_ENH_MINRM SMALLINT Minimum recall-mount time. From S94MINRM.

VTS_ENH_AVGRM FLOAT Average recall-mount time. From S94AVGRM.

VTS_ENH_ADV05 SMALLINT Number of volumes containing 0 to 5 percent active data.From S94ADV05.

VTS_ENH_ADV10 SMALLINT Number of volumes containing greater than 5 to 10 percentactive data. From S94ADV10.



















VTS_ENH_THRES SMALLINT Reclaim threshold percentage. From S94THRES.

MVS data tables



VTS_ENH_SRTCT SMALLINT Scratch stacked volume count. From S94SRTCT.

VTS_ENH_PRICT SMALLINT Private stacked volume count. From S94PRICT.

VTS_ENH_MTVCA FLOAT Maximum tape volume cache age. From S94MTVCA.

VTS_ENH_CLLVC FLOAT Composite library logical volumes to be copied. FromS94CLLVC.

VTS_ENH_CLDTC FLOAT Composite library data yet to be copied. From S94CLDTC.

VTS_ENH_CLMT0 SMALLINT Composite library mounts completed for B18-0. FromS94CLMT0.

VTS_ENH_CLMT1 SMALLINT Composite library mounts completed for B18-1. FromS94CLMT1.

VTS_ENH_CLDC0 FLOAT Data copied by AX0 number 0. From S94CLDC0.

VTS_ENH_CLVC0 FLOAT Volumes copied by AX0 number 0. From S94CLVC0.

VTS_ENH_CLRD0 FLOAT Read data transferred through AX0 number 0. FromS94CLRD0.

VTS_ENH_CLWD0 FLOAT Write data transferred through AX0 number 0. FromS94CLWD0.

VTS_ENH_CLCM0 SMALLINT Category mounts for AX0 number 0. From S94CLCM0.

VTS_ENH_CLSM0 SMALLINT Specific cache mounts for AX0 number 0. From S94CLSM0.

VTS_ENH_CLRM0 SMALLINT Specific recall mounts for AX0 number 0. From S94CLRM0.

















VTS_ENH_CLDC4 FLOAT Data copied by AXO number 4.

VTS_ENH_CLRD4 FLOAT Read data transferred through AX0 number 4.

VTS_ENH_CLVC4 FLOAT Volumes copied by AX0 number 4.

VTS_ENH_CLWD4 FLOAT Write data transferred through AX0 number 4.

MVS data tables


|

|

|

|


VTS_ENH_CLCM4 SMALLINT Category mounts for AX0 number 4.

VTS_ENH_CLSM4 SMALLINT Specific cache mounts for AX0 number 4.

VTS_ENH_CLRM4 SMALLINT Specific recall mounts for AX0 number 4.

VTS_ENH_CLDC5 FLOAT Data copied by AX0 number 5.


























MVS data tables


|

|

MVS_VTS_ACTDATA_HThis table provides hourly data on Virtual Tape Server pool active data andreclaimation. It reports the number of full private stacked volumes in the volumepool that contains active data by the percentage (5% granularity) of active dataremaining on the volumes. This table contains data from SMF type 94, subtype 2records.



DATE k DATE Date when the activity occurred. From SMF94S2_DTE.

HOUR k TIME Time when the activity occurred. From SMF94S2_HHI.

MVS_SYSTEM_ID k CHAR(4) MVS system ID. This is the SMF system ID. From SMF94S2_SID.

LIB_SEQ_NUM k CHAR(5) Library sequence number. From SMF94S2_LIBID.

VOLUME_POOL_SET k SMALLINT This column specifies which set of volume pools are beingreported. If the set specified is 0, the first 16 volume pools arereported, if 1, the next 16 and so on. From SMF94S2_VPSET.

POOL_NUMBER k SMALLINT Pool Number. This column contains the volume pool number.Pools are numbered starting with 1. From SMF94S2_VPN.

RECLAIM_POOL_NUM k SMALLINT Reclaimation Pool. This column contains the pool number to beused for the target for data that is reclaimed. Pools arenumbered starting with 1. From SMF94S2_RPN.

NUMV_ACTDAT_PCT_00 SMALLINT 0-5% Active Data Distribution. From SMF94S2_ADD00

NUMV_ACTDAT_PCT_05 SMALLINT >5-10% Active Data Distribution. From SMF94S2_ADD05



















RECLAIM_THRSH_PCT SMALLINT Volume pool reclaim threshold percentage (Current value). Thiscolumn contains the current reclaim threshold percentage set forthe volume pool. From SMF94S2_VPRTP

MVS data tables


|

|||||

|

|||||

||||

||||

||||

||||

||||||

|||||

||||||

||||

||||

||||

||||

||||

||||

||||

||||

||||

||||

||||

||||

||||

||||

||||

||||

||||

||||

||||

||||

||||||

|

MVS_VTS_PLCY_MGT_HThis table provides hourly Preference Level Virtual Mounts and Cache statistics. Itcontains data from SMF type 94, subtype 1 records.



DATE k DATE Date when the activity occurred. From SMF94DTE.

HOUR k TIME Time when the activity occurred. From SMF94HHI.


TAPE_LIBRARY k CHAR(12) System managed tape library sequence number. FromSMF94SNO.

LIB_SEQ_NUM k CHAR(5) Library sequence number for the library segment for which theVTS statistics are being reported. From SMF94VLS.

PREF_MGMT_CONTROL k CHAR(3) Preference Management control. This column containsinformation about how the preference level is managed. Possiblevalues: Least Recently Used (LRU) Managed or Largest SizeManaged (LSM). From S94OPM_PMC.

CACHE_HIT_MOUNTS REAL Number of cache hit mounts. This column contains the numberof mount requests that were completed by the VTS subsystem inthe last hour because the required volume was resident in theTVC. From S94OPM_CHMNTS.

CACHE_MISS_MOUNTS REAL Number of cache miss mounts. This column contains thenumber of mount requests that were completed by the VTS inthe last hour that required a logical volume to be recalled from astacked volume back into the TVC. From S94OPM_CMMNTS.

CACHE_SPACE_UTL_MB REAL Data resident in TVC. This column contains a count of theamount of cache space (Mbytes) used by the volumes assignedto the preference level that are still cache resident. FromS94OPM_DRIC.

CCHMIS_AVG_MNT_SEC REAL Average Cache Miss Mount Time. It contains the average time(in sec.) that the VTS took to complete the execution of a mountrequest for a virtual device where the requested volume had tobe recalled from a stacked volume. From S94OPM_CMTIME.

CCHHIT_AVG_MNT_SEC REAL Average Cache Hit Mount Time. This column contains theaverage time (in seconds) that the VTS subsystem took tocomplete the execution of a mount request for a virtual devicewhere the requested volume was in the TVC. FromS94OPM_CHTIME.

FR_AVG_MOUNT_SEC REAL Average Fast Ready Mount Time. This column contains theaverage time, in seconds, that the VTS subsystem took tocomplete the execution of a fast-ready mount request for avirtual device. From S94OPM_FRMT.

FAST_READY_MOUNTS REAL Fast-Ready Mounts. This column contains the number of mountrequests completed using the Fast-Ready facility by the VTSsubsystem in the last hour. From S94OPM_FRMNTS.

LVOL_MGRT_LAST4H REAL Volumes migrated from TVC in last 4 hours. This columncontains the number of logical volumes assigned to thepreference level that were migrated from the cache over the last4 hours. From S94OPM_VM4.

MVS data tables


|

||

|

|||||

||||

||||

||||

|||||

|||||

|||||||

|||||||

|||||||

|||||||

|||||||

||||||||

|||||||

||||||

|||||||


LVOL_MGRT_LAST48H REAL Volumes migrated from TVC in last 48 hours. This columncontains the number of logical volumes assigned to thepreference level that were migrated from the cache over the last48 hours. From S94OPM_VM48.

LVOL_MGRT_LAST35D REAL Volumes migrated from TVC in last 35 days. This columncontains the number of logical volumes assigned to thepreference level that were migrated from the cache over the last35 days. From S94OPM_VM35.

ROLLAVG_CACHAG_4H REAL 4 Hour Rolling average TVC age. This column contains a rollingaverage cache age, in hours, of the logical volumes that wereassigned to the preference level when the volume was migratedfrom the cache. From S94OPM_TVCA4/60.

ROLLAVG_CACHAG_48H REAL 48 Hour Rolling average TVC age. This column contains arolling average cache age, in hours, of the logical volumes thatwere assigned to the preference level when the volume wasmigrated from the cache. From S94OPM_TVCA48/60.

ROLLAVG_CACHAG_35D REAL 35 Day Rolling average TVC age. This column contains a rollingaverage cache age, in hours, of the logical volumes that wereassigned to the preference level when the volume was migratedfrom the cache. From S94OPM_TVCA35/60.

VIRT_VOLUMES_CACHE REAL Virtual volumes in TVC. This column contains a count of thenumber of volume assigned to the preference level that are stillcache resident. From S94OPM_VVIC.

MVS data tables


||||

|||||||

|||||||

|||||||

|||||||

|||||||

||||||

|

MVS_VTS_POOLS_HThis table provides hourly statistics on Virtual Tape Volume poolset activity. Itcontains data from SMF type 94, subtype 2 records.





MVS_SYSTEM_ID k CHAR(4) MVS system ID. This is the SMF system ID. FromSMF94S2_SID.

VOLUME_POOL_SET k SMALLINT This column specifies which set of volume pools are beingreported. If the set specified is 0, the first 16 volume pools arereported, if 1, the next 16 and so on. From SMF94S2_VPSET.


LAST_RCONCILE_TIME CHAR(10) Last Reconcile Time and Date. This column contains the lasttime and date a reconcile was automatically completed by theVTS. Some of next metrics are calculated at this point. FromSMF94S2_LRTD.

MAX_POOLS_ALLOWED SMALLINT Maximum number of volume pools allowed in the partition.From SMF94S2_MNVP.

MEDIA_TYPE_0 CHAR(8) Common Scratch Pool Media Identifier 0. FromSMF94S2_BPMIO.

MEDIA_TYPE_1 CHAR(8) Common Scratch Pool Media Identifier 1. FromSMF94S2_BPMI1.



NUM_SCRTCH_STCK_M0 INTEGER Common Scratch Pool Stacked Volume Count Media Identifier0. This column contains the number of scratch stackedvolumes, of a type identified by Media Identifier 0, assignedto the common volume pool. From SMF94S2_BPSVCO.

NUM_SCRTCH_STCK_M1 INTEGER Common Scratch Pool Stacked Volume Count Media Identifier1. This column contains the number of scratch stackedvolumes, of a type identified by Media Identifier 1, assignedto the common volume pool. From SMF94S2_BPSVC1.



MVS data tables


|

||

|

|||||

||||

||||

|||||

||||||

||||

|||||||

|||||

|||||

|||||

|||||

|||||

|||||||

|||||||

|||||||

|||||||

|

MVS_VTS_MEDIA_HThis table provides hourly statistics on Virtual Tape Server Volume Pool mediaactivity. It contains data from SMF type 94, subtype 2 records.





MVS_SYSTEM_ID k CHAR(4) MVS system ID. This is the SMF system ID. FromSMF94S2_SID.

VOLUME_POOL_SET k SMALLINT This column specifies which set of volume pools is beingreported. If the set specified is 0, the first 16 volume pools arereported, if 1, the next 16 and so on. From SMF94S2_VPSET.


POOL_NUMBER k SMALLINT Pool Number. This column contains the volume pool number.Pools are numbered starting with 1. From SMF94S2_VPN.

RECLAIM_POOL_NUM k SMALLINT Reclamation Pool. This column contains the pool number tobe used for the target for data that is reclaimed. Pools arenumbered starting with 1. From SMF94S2_RPN.

AVG_FULL_VOL_DAYS INTEGER Average age of the full private stacked volumes. This columncontains the average age, in days, of the private stackedvolumes in the volume pool at the completion of the lastreconcile. From SMF94S2_AAOFPSV.

AVG_RES_DATA_DAYS INTEGER Average age of residual data. This column contains theaverage age, in days, of the residual data that resides on thestacked volumes assigned to the pool at the completion of thelast reconcile. From SMF94S2_AAORD.

BRROW_PRVAT_MDIA0 INTEGER Pool Borrowed Private Stacked Volume Count MediaIdentifier 0. This column contains the number of mediaidentifier 0 volumes that are assigned to the volume poolthrough borrowing that contain active data. FromSMF94S2_PBPSVC0.

BRROW_PRVAT_MDIA1 INTEGER Pool Borrowed Private Stacked Volume Count MediaIdentifier 1. This column contains the number of mediaidentifier 1 volumes that are assigned to the volume poolthrough borrowing that contain active data. FromSMF94S2_PBPSVC1.

BRROW_SCRTH_MDIA0 INTEGER Pool Borrowed Scratch Stacked Volume Count MediaIdentifier 0. This column contains the number of mediaidentifier 0 volumes that were assigned to the volume poolthrough borrowing and are in scratch status. FromSMF94S2_PBSSVC0.

BRROW_SCRTH_MDIA1 INTEGER Pool Borrowed Scratch Stacked Volume Count MediaIdentifier 1. This column contains the number of mediaidentifier 1 volumes that were assigned to the volume poolthrough borrowing and are in scratch status. FromSMF94S2_PBSSVC1.

DATA_ACT_V_POOL_MB REAL Active data in volume pool. This column contains the numberof Mbytes of logical volume image data managed by thevirtual tape server in the volume pool. From SMF94S2_ADIVP.

MVS data tables


|

||

|

|||||

||||

||||

|||||

||||||

||||

|||||

||||||

|||||||

|||||||

||||||||

||||||||

||||||||

||||||||

||||||


DATA_WRTTN_POOL_MB REAL Data written to the pool in the last hour. This column containsthe number of MBytes premigrated from the tape volumecache to the pool during the last hour. FromSMF94S2_DWTPLH.

LOGICAL_ACT_V_POOL REAL Active logical volumes in pool. This column contains thenumber of logical volume images resident in the volume pool.From SMF94S2_ALVIP.

MAX_FULL_VOL_DAYS INTEGER Maximum age of the full private stacked volumes. Thiscolumn contains the maximum age, in days, of the privatestacked volumes in the volume pool at the completion of thelast reconcile. From SMF94S2_MAOFPSV.

MAX_RES_DATA_DAYS INTEGER Maximum age of residual data. This column contains themaximum age, in days, of the residual data that resides on thestacked volumes assigned to the pool at the completion of thelast reconcile. From SMF94S2_MAORD.

POOL_DEVICE_CLASS CHAR(8) Pool Device Class Identifier. This column contains the deviceclass identifier for the volume pool. From SMF94S2_PDCI.

STATC_SCRTH_MDIA0 INTEGER Pool Static Scratch Stacked Volume Count Media Identifier 0.This column contains the number of media identifier 0volumes that were statically assigned to the volume pool andare in scratch status. From SMF94S2_PSSSVC0.

STATC_PRVAT_MDIA0 INTEGER Pool Static Private Stacked Volume Count Media Identifier 0.This column contains the number of media identifier 0volumes that were statically assigned to the volume pool andcontain active data. From SMF94S2_PSPSVC0.

STATC_SCRTH_MDIA1 INTEGER Pool Static Scratch Stacked Volume Count Media Identifier 1.This column contains the number of media identifier 1volumes that were statically assigned to the volume pool andare in scratch status. From SMF94S2_PSSSVC1.

STATC_PRVAT_MDIA1 INTEGER Pool Static Private Stacked Volume Count Media Identifier 1.This column contains the number of media identifier 1volumes that were statically assigned to the volume pool andcontain active data. From SMF94S2_PSPSVC1.

MVS data tables


||||

|||||||

||||||

|||||||

|||||||

|||||

|||||||

|||||||

|||||||

|||||||

MVS_WORKLOAD_H, _D, _MThese tables provide hourly, daily, and monthly statistics on MVS workloadactivity by performance group and performance period. They contain data fromSMF type 72, subtype 1 records.

These tables are updated by the MVS_WORKLOAD_TYPE lookup table.

The default retention periods for these tables are:MVS_WORKLOAD_H 45 daysMVS_WORKLOAD_D 45 daysMVS_WORKLOAD_M 765 days


DATE k DATE Date when the workload activities occurred. For the _M table,this is the date of the first day of the month. From SMF72DATand SMF72IST.

TIME k TIME Time (rounded down to the nearest hour) when the workloadactivities occurred. It applies only to the _H table. FromSMF72DAT and SMF72IST.

PERIOD_NAME k CHAR(8) Name of the period. This is derived using fields SMF72SID,SMF72DAT, SMF72IST, and SMF72INT from the record asparameters in the PERIOD function.


WORKLOAD_TYPE k CHAR(8) Workload type associated with the performance group andperformance period. From WORKLOAD_TYPE in theMVS_WORKLOAD_TYPE lookup table.

PERF_GROUP_NO k CHAR(4) Performance group number. From SMF72SUB.

PERF_GROUP_PERIOD k CHAR(1) Performance group period number. This is from the sequentialnumber of the performance group period data section(SMF72PGP).

PERF_GROUP_TYPE k CHAR(1) Performance group (PG) type. This can be: C for control, or Rfor reporting. All data in reporting PGs is also reported in acontrol PG, so when summaries are produced, only control PGsshould be selected. From SMF72FGI.

SUBSYSTEM_ID k CHAR(4) Name of the subsystem associated with the performance group.From SMF72SYS.

AVG_FOREIGN_ENCL FLOAT Average number of foreign enclaves during the interval. This isthe average of R723CFEA.

AVG_INDEPEND_ENCL FLOAT Average number of independent enclaves during the interval.This is the average of R723CIEA.

AVG_MULTISYS_ENCL FLOAT Average number of multisystem enclaves during the interval.This is the average of R723CXEA.

CAPACITY_CPU_SU FLOAT Total processor capacity, in processor service units. Calculatedas the sum of SMF72INT*SMF72CSD*16 000/SMF72ADJ.

CS_FRAME_SECONDS FLOAT Active frame-time for frames in central storage, in seconds.Calculated as the sum of (SMF72TF − SMF72ER)*0.001 024.

ES_FRAME_SECONDS FLOAT Active frame time for frames in expanded storage. Calculatedas the sum of SMF72ER*0.001 024 if SMF72ER is present in therecord; otherwise, calculated from TOT_FRAME_SECONDSand CS_FRAME_SECONDS.

HIPER_SERVICE_SEC FLOAT Time used for hiperspace service, in seconds. Calculated as thesum of SMF72HST/1 000 000.

MVS data tables



IO_COUNT FLOAT Number of I/Os calculated from the number of I/O serviceunits. Calculated as the sum of SMF72ITS/SMF72ISD.

IOINTR_SECONDS FLOAT Time used for processing I/O interrupts, in seconds. Calculatedas the sum of SMF72IIT/1 000 000.

MEASURED_SEC FLOAT Measured time period, in seconds. This is the duration of theRMF measurement intervals. Calculated as the sum ofSMF72INT/1000.

PAGEINS FLOAT Number of page-ins. This includes page-ins of hiperspaces.Calculated as the sum of SMF72PIN + SMF72HIN.

PAGEINS_SHARED FLOAT Total shared page-ins from auxiliary storage. This is the sum ofSMF72SPA.

PAGEINS_SHARED_ES FLOAT Total shared page-ins from expanded storage. This is the sumof SMF72SPE.

RCT_SECONDS FLOAT Region control task time, in seconds. Calculated as the sum ofSMF72RCT/1 000 000.

RESIDENT_SHR_SEC FLOAT Total shared page residency, in seconds. Calculated as the sumof SMF72SRS*0.001024.

SERVICE_UNITS_CPU FLOAT Total processor service units. This is the sum of SMF72CTS.

SERVICE_UNITS_IO FLOAT Total I/O service units. This is the sum of SMF72ITS.

SERVICE_UNITS_MS FLOAT Total main-storage service units. This is the sum of SMF72MTS.

SERVICE_UNITS_SRB FLOAT Total SRB service units. This is the sum of SMF72STS.

SERVICE_UNITS_TOT FLOAT Total service units used in all transactions. This is the sum ofSMF72SER.

SRB_SECONDS FLOAT SRB processor time calculated from the number of processorservice units, in seconds. Calculated as the sum ofSMF72STS*SMF72ADJ/16 000 000/SMF72SSD.

SYSPLEX NAME CHAR(8) Sysplex name. This is the name of the sysplex. FromSMF72XNM.

SYSTEM NAME CHAR(8) MVS system name. This is the MVS system name. FromSMF72SNM.

SWAP_SEQUENCES FLOAT Number of address space swap sequences. A swap sequenceconsists of an address space swap-out and swap-in. This is thesum of SMF72SPP.

TCB_SECONDS FLOAT TCB processor time calculated from the number of processorservice units, in seconds. Calculated as the sum ofSMF72CTS*SMF72ADJ/16 000 000/SMF72CSD.

TOT_FRAME_SECONDS FLOAT Active frame-time for all frames in central and expandedstorage, in seconds. Calculated as the sum ofSMF72FT*0.001 024.

TRAN_ACTIVE_SEC FLOAT Active time of all transactions, in seconds. This includes thetotal time that each transaction was in central storage plus anyswapped-out time (long wait state time is not included).Calculated as the sum of SMF72ACT*0.001 024.

TRAN_ELAPSED_SEC FLOAT Elapsed time accumulated by all transactions that ended in thisperformance group period, in seconds. Calculated as the sumof SMF72TTM*0.001 024.

TRAN_RESIDENCY_SEC FLOAT Transaction residency time, in seconds. This includes the totaltime that each transaction was in central storage. Calculated asthe sum of SMF72TAT*0.001 024.

MVS data tables


|

|


TRANSACTIONS INTEGER Number of transactions ended. This is the sum of SMF72TTX.

MVS data tables


MVS_WORKLOAD2_H, _D, _MThese tables provide hourly, daily, and monthly statistics on MVS activity byworkload type and service class, when the system is running in goal mode. Theycontain data from SMF type 72, subtype 3 records.

These tables are updated by the MVS_WORKLOAD2_TYPE lookup table.

The default retention period for these tables are:MVS_WORKLOAD2_H 7 daysMVS_WORKLOAD2_D 30 daysMVS_WORKLOAD2_M 765 days


DATE k DATE Date when the workload activity occurred. For the _Mtable, this is the date of the first day of the month. FromSMF72DAT, SMF72IST, and SMF72INT.

TIME k TIME Time (rounded down to nearest hour) when the workloadactivity occurred. It applies only to the _H table, FromSMF72DAT, SMF72IST, and SMF72INT.









AVERAGE_GOAL_SEC FLOAT Average response time goal, in seconds. From R723CVAL(converted to seconds using R723CRTF) if R723CRGF isequal to X'40', otherwise set to zero.

AVG_FOREIGN_ENCL FLOAT Average number of foreign enclaves during the interval.This is the average of R723CFEA.

AVG_INDEPEND_ENCL FLOAT Average number of independent enclaves during theinterval. This is the average of R723CIEA.

AVG_MULTISYS_ENCL FLOAT Average number of multisystem enclaves during theinterval. This is the average of R723CXEA.

CAPACITY_CPU_SU FLOAT Total processor capacity, in processor service units.Calculated as the sum ofSMF72INT*R723MCPU*1.6/R723MADJ.

CPU_RGCAP_SU_MAX FLOAT Maximum capacity in unweighted processor service units.Calculated as the sum of R723GGMX*SMF72INT/1000.

CPU_RGCAP_SU_MIN FLOAT Minimum capacity in unweighted processor service units.Calculated as the sum of R723GGMN*R723INT/1000.

CPU_USE_CNT FLOAT Number of samples when processor was used. This is thesum of R723CCUS.

CS_FRAME_SECONDS FLOAT Active frame-time for frames in central storage, in seconds.Calculated as the sum of (R723CPRS - R723CERS)*0.001024.

MVS data tables


|


ES_FRAME_SECONDS FLOAT Active frame-time for frames in expanded storage.Calculated as the sum of R723CERS*0.001024.

EXEC_VEL_GOAL_PCT INTEGER Execution velocity goal, in percent. From R723CVAL ifR723CRGF is equal to X'20', otherwise set to zero.

GOAL_FLAG SMALLINT Goal flag; 0=percentile response time goal, 1=averageresponse time goal, 2=execution velocity goal,3=discretionary goal, 4=system specified goal. FromR723CRGF.

GOAL_IMPORTANCE SMALLINT Relative importance of the goal to be achieved for thisservice class period (1=highest, 5=lowest). Calculated as themaximum of R723CIMP.

GOAL_PERCENTILE INTEGER Percentile response time goal, in percent. From R723CPCT ifR723CRGF is equal to X'80', otherwise set to zero.

HIPER_SERVICE_SEC FLOAT Time used for hiperspace service, in seconds. Calculated asthe sum of R723CHST/1 000 000.

IO_COUNT FLOAT Number of I/Os calculated from the number of I/O serviceunits. Calculated as the sum of 10000*R723CIOC/R723MIOC.

IOINTR_SECONDS FLOAT Time used for processing I/O interrupts, in seconds.Calculated as the sum of R723CIIT/1 000 000.


MVS_RESOURCE_GROUP CHAR(8) Resource group name. From R723GGNM.

PAGEINS_SHARED FLOAT Total shared page-ins from auxiliary storage. This is the sumof R723CSPA.

PAGEINS_SHARED_ES FLOAT Total shared page-ins from expanded storage. This is thesum of R723CSPE.

PERCENT_GOAL_SEC FLOAT Response time goal, in seconds. From R723CVAL (convertedto seconds using R723CRTF) if R723CRGF is equal to X'80',otherwise set to zero. GOAL_PERCENTILE percent of alltransactions should be completed withinPERCENT_GOAL_SEC seconds.

RCT_SECONDS FLOAT Region control task time, in seconds. Calculated as the sumof R723CRCT/1 000 000.

REPORT_PERIOD_FLAG CHAR(1) Report class period flag: 1=Heterogeneous class (more thanone service class for the same report class), 0=Homogeneousreport class period (only one service class for this reportclass). Blank if this is a service class period. FromR723CRS1.

RESIDENT_SHR_SEC FLOAT Total shared page residency, in seconds. Calculated as thesum of R723CSRS*0.001024.

SERV_CLASS_TYPE CHAR(1) Service class (SC) type. This can be C (control), or R(reporting). All data in reporting SCs is also reported in acontrol SC. So, when summaries are produced, only controlSCs should be selected. From R723MSCF.

SERV_FOR_REPORT CHAR(8) Service class that last contributed to this report class. Blankif this is a service class. From R723CLSC.

SERVICE_UNITS_CPU FLOAT Total processor weighted service units. This is the sum ofR723CCPU.

MVS data tables


|

|


SERVICE_UNITS_IO FLOAT Total I/O service units. This is the sum of R723CIOC.

SERVICE_UNITS_MS FLOAT Total main-storage service units. This is the sum ofR723CMSO.

SERVICE_UNITS_SRB FLOAT Total SRB weighted service units. This is the sum ofR723CSRB.

SERVICE_UNITS_TOT FLOAT Total service units used in all transactions. This is the sumof R723CSRV.

SRB_SECONDS FLOAT SRB processor time calculated from the number of processorservice units, in seconds. Calculated as the sum ofR723CSRB*R723MADJ/1600/R723MSRB.

SUBSYSTEM_ID CHAR(4) Name of the subsystem associated with the service class.From R723RTYP.

SU_UNWEIGHT_CPU FLOAT Total processor unweighted service units. Calculated as thesum of R723CCPU*10 000/R723MCPU.

SU_UNWEIGHT_SRB FLOAT Total SRB unweighted service units. Calculated as the sumof R723CSRB*10 000/R723MSRB.

SWAP_SEQUENCES FLOAT Number of address space swap sequences. A swap sequenceconsists of an address space swap-out and swap-in. This isthe sum of R723CSWC.


TCB_SECONDS FLOAT TCB processor time calculated from the number ofprocessor service units, in seconds. Calculated as the sum ofR723CCPU*R723MADJ/1600/R723MCPU.

TOTAL_DELAY_CNT FLOAT Number of delay samples. This is the sum of R723CTOT.

TOTAL_USING_SAMPLE REAL Total using samples. For the velocity formula, see OS/390MVS Planning: Workload Management. Calculated as the sumof R723CTOU.

TOT_FRAME_SECONDS FLOAT Active frame-time for frames in central and expandedstorage, in seconds. Calculated as the sum ofR723CPRS*0.001024.

TRAN_ACTIVE_SEC FLOAT Active time of all transactions, in seconds. This includes thetotal time that each transaction was in central storage plusany swapped-out time (long wait state time is notincluded). Calculated as the sum of R723CTAT*0.001024.

TRAN_ELAPSED_SEC FLOAT Elapsed time accumulated by all transactions that ended inthis performance group period, in seconds. Calculated asthe sum of R723CTET*0.001024.

TRAN_EXECUTION_SEC FLOAT Execution time accumulated by all transactions that endedin this performance group period, in seconds. Calculated asthe sum of R723CXET*0.001024.

TRAN_RESIDENCY_SEC FLOAT Transaction residency time, in seconds. This includes thetotal time that each transaction was in central storage.Calculated as the sum of R723CTRR*0.001024.

TRANSACTIONS INTEGER Number of transactions ended. This is the sum ofR723CRCP.

TRANSACTIONS_BELOW INTEGER Number of transactions ended, within response time goal.This is the sum of R723TRDB for GOAL_PERCENTAGE <=100.

MVS data tables


ViewsThis section describes the views for the MVS component.

MVS_LPAR_DVThis view provides daily statistics on logical partitions and processor activity in aPR/SM environment. It is based on the MVS_LPAR_D table, and its data comesfrom SMF type 70 records processed through a record procedure (DRL2S070).

Note: Aside from the calculated columns described here, this view also contains allthe data columns described in “MVS_LPAR_D, _M” on page 329.


DATE k DATE Date of the mid measurement. From SMF70DAT, SMF70IST,and SMF70INT.





ALLOWED_SEC FLOAT Allowed time for the processor partition, in seconds. Calculatedas ((MEASURED_SEC*DEDICAT_PROC_LPAR) + LPROC_SEC*LPAR_WEIGHT/LPAR_WEIGHT_TOT)

COMPLEX_UTIL_PCT FLOAT Total processor complex utilization for the partition, in percent.Calculated as 100*(CPU_DISPATCH_SEC - CPU_WAIT_SEC) /COMPLEX_SEC.

LPAR_BUSY_PCT FLOAT Busy time for the logical partition, as a percentage of theelapsed time. This value can be greater that 100% if more thanone processor is assigned to the partition. Calculated as100*CPU_DISPATCH_SEC/MEASURED_SEC.

LPAR_DISPATCH_PCT FLOAT Time that the logical partition was dispatched, as a percentageof the allowed time. Calculated as100*CPU_DISPATCH_SEC/ALLOWED_SEC.

LPAR_EFF_DISP_PCT FLOAT Time that the logical partition was dispatched, as a percentageof the allowed time. Calculated as100*CPU_DISPATCH_SEC/ALLOWED_SEC

LPAR_MGMT_PCT FLOAT Logical partition management time, in percent. This is thepercentage of physical LPAR management time if the partitionname is *PHYSCAL. Calculated as 100*(CPU_DISPATCH_SEC-CPU_ EFF_DISP_SEC) /LPROC_SEC.

LPAR_SPARE_PCT FLOAT Spare time for the logical partition, as a percentage of theallowed time for this partition. A minus sign for this valuemeans that more than the allowed time was used. Calculated as100*(ALLOWED_SEC − CPU_DISPATCH_SEC)/ALLOWED_SEC.

LPROC_BUSY_PCT FLOAT Average logical processor busy time for the partition, inpercent. Calculated as100*CPU_DISPATCH_SEC/LP_ONLINE_SEC.

MVS views


|

|

|

|

|

|

|


LPROC_DISPATCH_PCT FLOAT Logical processor dispatch time, as a percentage of the timeavailable for nondedicated processors. Calculated as100*CPU_DISPATCH_SEC/LPROC_SEC.

LPROC_EFF_DISP_PCT FLOAT Effective dispatch time for the logical processor, as a percentageof the time available for nondedicated processors. Calculated as100*CPU_EFF_DISP_SEC/LPROC_SEC.



MVS views


|

|

|

|

MVS_LPAR_MVThis view provides monthly statistics on logical partitions and processor activity ina PR/SM environment. It is based on the MVS_LPAR_M table, and its data comesfrom SMF type 70 records processed through a record procedure (DRL2S070).

Note: Aside from the calculated columns described here, this view also contains allthe data columns described in “MVS_LPAR_D, _M” on page 329.


DATE k DATE Date of the mid measurement. This is the date of the first day ofthe month. From SMF70DAT, SMF70IST, and SMF70INT.





ALLOWED_SEC FLOAT Allowed time for the processor partition, in seconds. Calculatedas ((MEASURED_SEC*DEDICAT_PROC_LPAR) + LPROC_SEC*LPAR_WEIGHT/LPAR_WEIGHT_TOT)

COMPLEX_UTIL_PCT FLOAT Total processor complex utilization for the partition, in percent.Calculated as 100*(CPU_DISPATCH_SEC - CPU_WAIT_SEC) /COMPLEX_SEC.

LPAR_BUSY_PCT FLOAT Busy time for the logical partition, as a percentage of the elapsedtime. This value can be greater that 100% if more than oneprocessor is assigned to the partition. Calculated as100*CPU_DISPATCH_SEC/MEASURED_SEC.

LPAR_DISPATCH_PCT FLOAT Time that the logical partition was dispatched, as a percentage ofthe allowed time. Calculated as100*CPU_DISPATCH_SEC/ALLOWED_SEC.

LPAR_EFF_DISP_PCT FLOAT Time that the logical partition was dispatched, as a percentage ofthe allowed time. Calculated as100*CPU_DISPATCH_SEC/ALLOWED_SEC

LPAR_MGMT_PCT FLOAT Logical partition management time, in percent. This is thepercentage of physical LPAR management time if the partitionname is *PHYSCAL. Calculated as 100*(CPU_DISPATCH_SEC-CPU_ EFF_DISP_SEC) /LPROC_SEC.

LPAR_SPARE_PCT FLOAT Spare time for the logical partition, as a percentage of theallowed time for this partition. A minus sign for this valuemeans that more than the allowed time was used. Calculated as100*(ALLOWED_SEC − CPU_DISPATCH_SEC)/ALLOWED_SEC.

LPROC_BUSY_PCT FLOAT Average logical processor busy time for the partition, in percent.Calculated as 100*CPU_DISPATCH_SEC/LP_ONLINE_SEC.


LPROC_EFF_DISP_PCT FLOAT Effective dispatch time for the logical processor, as a percentageof the time available for nondedicated processors. Calculated as100*CPU_EFF_DISP_SEC/LPROC_SEC.

MVS views


|

|

|

|

|

|

|

|

|




MVS views


|

|

MVS_RESOURCE_HVThis view provides hourly statistics on processor activity and capacity by resourcegroup. It is based on the MVS_WORKLOAD2_H table.


DATE k DATE Date when the activity occurred. From SMF72DAT, SMF72IST,and SMF72INT.

TIME k TIME Time (rounded down to nearest hour) when the activityoccurred. From SMF72DAT, SMF72IST, and SMF72INT.






CPU_RGCAP_SU_MAX FLOAT Maximum capacity in unweighted CPU service units.Calculated as the sum of R723GGMX*SMF72INT/1000.

CPU_RGCAP_SU_MIN FLOAT Minimum capacity in unweighted CPU service units.Calculated as the sum of R723GGMN*SMF72INT/1000.

MEASURED_SEC FLOAT Measured time period, in seconds. This is the duration of theRMF measurement interval. Calculated as the sum ofSMF72INT/1000.

SU_UNWEIGHT_CPU FLOAT Total consumed CPU unweighted service units. Calculated asthe sum of R723CCPU*10 000/R723MCPU.

SU_UNWEIGHT_SRB FLOAT Total consumed SRB unweighted service units. Calculated asthe sum of R723CSRB*10 000/R723MSRB.

Note: The data columns in this view are grouped by the key columns listed andthe column MVS_RESOURCE_GROUP.

MVS views


MVS_RESOURCE_DVThis view provides daily statistics on processor activity and capacity by resourcegroup. It is based on the MVS_WORKLOAD2_D table.


DATE k DATE Date when the activity occurred. From SMF72DAT, SMF72IST,and SMF72INT.












MVS views


MVS_RESOURCE_MVThis view provides monthly statistics on processor activity and capacity byresource group. It is based on the MVS_WORKLOAD2_M table.


DATE k DATE Date when the activity occurred. This is the date of the firstday of the month. From SMF72DAT, SMF72IST, andSMF72INT.












MVS views


MVS_WORKLOAD_HV1This view provides hourly statistics on MVS workload activity by subsystem ID. Itis based on the MVS_WORKLOAD_H table.


DATE k DATE Date when the workload activities occurred. From SMF72DAT andSMF72IST.

TIME k TIME Time (rounded down to the nearest hour) when the workloadactivities occurred. From SMF72DAT and SMF72IST.

PERIOD_NAME k CHAR(8) Name of the period. This is derived using fields SMF72SID,SMF72DAT, SMF72IST, and SMF72INT from the record as parametersin the PERIOD function.


SUBSYSTEM_ID k CHAR(4) Name of the subsystem associated with the performance group. FromSMF72SYS.

Note: Aside from the key columns described here, this view also contains all thedata columns described in “MVS_WORKLOAD_H, _D, _M” on page 367.

MVS_WORKLOAD_HV2This view provides hourly statistics on MVS workload activity by MVS system ID.It is based on the MVS_WORKLOAD_H table.







MVS views


MVS_WORKLOAD_HV3This view provides hourly statistics on MVS workload activity (TSO workloadonly) by workload type and performance group type. It is based on theMVS_WORKLOAD_H table.







PERF_GROUP_TYPE k CHAR(1) Performance group (PG) type. This can be: C for control, or R forreporting. All data in reporting PGs is also reported in a control PG,so when summaries are produced, only control PGs should beselected. From SMF72FGI.


MVS_WORKLOAD_HV4This view provides hourly statistics on MVS workload activity by workload typeand performance group type. It is based on the MVS_WORKLOAD_H table.









MVS views


MVS_WORKLOAD_DV1This view provides daily statistics on MVS workload activity by subsystem ID. It isbased on the MVS_WORKLOAD_D table.







MVS views


MVS_WORKLOAD_DV2This view provides daily statistics on MVS workload activity by MVS system ID. Itis based on the MVS_WORKLOAD_D table.






MVS views


MVS_WORKLOAD_DV3This view provides daily statistics on MVS workload activity (TSO workload only)by workload type and performance group type. It is based on theMVS_WORKLOAD_D table.








MVS views


MVS_WORKLOAD_DV4This view provides daily statistics on MVS workload activity by workload typeand performance group type. It is based on the MVS_WORKLOAD_D table.








MVS views


MVS_WORKLOAD_MV1This view provides monthly statistics on MVS workload activity by subsystem ID.It is based on the MVS_WORKLOAD_M table.


DATE k DATE Date when the workload activities occurred. This is the date of the firstday of the month. From SMF72DAT and SMF72IST.





MVS views


MVS_WORKLOAD_MV2This view provides monthly statistics on MVS workload activity by MVS systemID. It is based on the MVS_WORKLOAD_M table.






MVS views


MVS_WORKLOAD_MV3This view provides monthly statistics on MVS workload activity (TSO workloadonly) by workload type and performance group type. It is based on theMVS_WORKLOAD_M table.


DATE k DATE Date when the workload activities occurred. This is the date of thefirst day of the month. From SMF72DAT and SMF72IST.






MVS views


MVS_WORKLOAD_MV4This view provides monthly statistics on MVS workload activity by workload typeand performance group type. It is based on the MVS_WORKLOAD_M table.


DATE k DATE Date when the workload activities occurred. This is the date of thefirst day of the month. From SMF72DAT and SMF72IST.






MVS views


MVS_WORKLOAD2_HV2This view provides hourly statistics on MVS activity by MVS system ID, when thesystem is running in goal mode. It is based on the MVS_WORKLOAD2_H table.


DATE k DATE Date when the workload activity occurred. From SMF72DAT,SMF72IST, and SMF72INT.

TIME k TIME Time (rounded down to nearest hour) when the workloadactivity occurred. From SMF72DAT, SMF72IST, andSMF72INT.




CPU_USE_CNT FLOAT Number of samples when the processor was used. This is thesum of R723CCUS.

CS_FRAME_SECONDS FLOAT Active frame-time for frames in central storage, in seconds.Calculated as the sum of (R723CPRS - R723CERS)*0.001024.

ES_FRAME_SECONDS FLOAT Active frame-time for frames in expanded storage. Calculatedas the sum of R723CERS*0.001024.

HIPER_SERVICE_SEC FLOAT Time used for hiperspace service, in seconds. Calculated as thesum of R723CHST/1 000 000.

IO_COUNT FLOAT Number of I/Os calculated from the number of I/O serviceunits. Calculated as the sum of 10 000*R723CIOC/R723MIOC.

IOINTR_SECONDS FLOAT Time used for processing I/O interrupts, in seconds.Calculated as the sum of R723CIIT/1 000 000.


RCT_SECONDS FLOAT Region control task time, in seconds. Calculated as the sum ofR723CRCT/1 000 000.

SERVICE_UNITS_CPU FLOAT Total processor weighted service units. This is the sum ofR723CCPU.



SERVICE_UNITS_SRB FLOAT Total SRB weighted service units. This is the sum ofR723CSRB.

SERVICE_UNITS_TOT FLOAT Total service units used in all transactions. This is the sum ofR723CSRV.

SRB_SECONDS FLOAT SRB processor time calculated from the number of processorservice units, in seconds. Calculated as the sum ofR723CSRB*R723MADJ/1600/R723MSRB.

SU_UNWEIGHT_CPU FLOAT Total processor unweighted service units. Calculated as thesum of R723CCPU*10 000/R723MCPU.

SU_UNWEIGHT_SRB FLOAT Total SRB unweighted service units. Calculated as the sum ofR723CSRB*10 000/R723MSRB.

MVS views



SWAP_SEQUENCES FLOAT Number of address space swap sequences. A swap sequenceconsists of an address space swap-out and swap-in. This is thesum of R723CSWC.

TCB_SECONDS FLOAT TCB processor time calculated from the number of processorservice units, in seconds. Calculated as the sum ofR723CCPU*R723MADJ/1600/R723MCPU.

TOTAL_DELAY_CNT FLOAT Number of delay samples. This is the sum of R723CTOT.

TOT_FRAME_SECONDS FLOAT Active frame-time for frames in central and expanded storage,in seconds. Calculated as the sum of R723CPRS*0.001024.

TRAN_ACTIVE_SEC FLOAT Active time of all transactions, in seconds. This includes thetotal time that each transaction was in central storage plus anyswapped-out time (long wait state time is not included).Calculated as the sum of R723CTAT*0.001024.

TRAN_ELAPSED_SEC FLOAT Elapsed time accumulated by all transactions that ended inthis performance group period, in seconds. Calculated as thesum of R723CTET*0.001024.

TRAN_EXECUTION_SEC FLOAT Execution time accumulated by all transactions that ended inthis performance group period, in seconds. Calculated as thesum of R723CXET*0.001024.

TRAN_RESIDENCY_SEC FLOAT Transaction residency time, in seconds. This includes the totaltime that each transaction was in central storage. Calculated asthe sum of R723CTRR*0.001024.

TRANSACTIONS INTEGER Number of transactions ended. This is the sum of R723CRCP.

TRANSACTIONS_BELOW INTEGER Number of transactions ended, within response time goal.This is the sum of R723TRDB for GOAL_PERCENTAGE <=100.

MVS views


MVS_WORKLOAD2_HV4This view provides hourly statistics on MVS activity by MVS system ID, when thesystem is running in goal mode. It is based on the MVS_WORKLOAD2_H table.



TIME k TIME Time (rounded down to nearest hour) when the workload activityoccurred. From SMF72DAT, SMF72IST, and SMF72INT.




Note: Aside from the key columns described here, this view also contains all thedata columns described in “MVS_WORKLOAD2_HV2” on page 390.

MVS views


MVS_WORKLOAD2_DV2This view provides daily statistics on MVS activity by MVS system ID, when thesystem is running in goal mode. It is based on the MVS_WORKLOAD2_D table.






MVS views


MVS_WORKLOAD2_DV4This view provides daily statistics on MVS activity by MVS system ID, when thesystem is running in goal mode. It is based on the MVS_WORKLOAD2_D table.







MVS views


MVS_WORKLOAD2_MV2This view provides monthly statistics on MVS activity by MVS system ID, whenthe system is running in goal mode. It is based on the MVS_WORKLOAD2_Mtable.


DATE k DATE Date when the workload activity occurred. This is the date of thefirst day of the month. From SMF72DAT, SMF72IST, and SMF72INT.




MVS views


MVS_WORKLOAD2_MV4This view provides monthly statistics on MVS activity by MVS system ID, whenthe system is running in goal mode. It is based on the MVS_WORKLOAD2_Mtable.


DATE k DATE Date when the workload activity occurred. This is the date of thefirst day of the month. From SMF72DAT, SMF72IST, and SMF72INT.





MVS views


Lookup tablesThis section describes the lookup tables specific to the MVS component.

MVS_ABEND_CODEThis lookup table converts the most common system abend codes to descriptionsthat you can use when you create reports using the MVS_ADDRSPACE_T andMVS_COMPCODE_x tables. It is initialized with the abend codes listed under“Example of table contents”. If you want to add more system abend codes, useSQL INSERT statements.


ABEND_CODE k CHAR(4) System abend code to be converted.

EXPLANATION VARCHAR(30) Short description of the abend code. Refer to the System Codesmanual for a complete description of the codes.


ABENDCODE EXPLANATION----- ------------------------------001 I/O ERROR AT END-OF-VOLUME002 I/O ERROR FOR SEQUENTIAL FILES003 I/O ERROR AT END-OF-BLOCK004 OPEN ERROR, CONFLICTING DCB005 I/O ERROR, INV DECB FOR BSAM008 ERROR IN EXECUTING SYNAD013 OPEN ERROR014 CLOSE ERROR FOR BDAM020 OPEN ERROR FOR BDAM04E DB2 ERROR04F DB2 ERROR0C1 OPERATION EXCEPTION0C2 PRIVILIG-OPER EXCEPTION0C3 EXECUTE EXCEPTION0C4 INVALID VIRTUAL ADDRESS0C5 ADDRESSING EXCEPTION0C6 SPECIFICATION EXCEPTION0C7 DATA EXCEPTION0C8 FIXED-POINT OVERFLOW0C9 FIXED-POINT DIVIDE EXCEPTION0CA DECIMAL OVERFLOW EXCEPTION0CB DECIMAL DIVIDE EXCEPTION0CC EXPONENT OVERFLOW EXCEPTION0CD EXPONENT UNDERFLOW EXCEPTION0CE SIGNIFICANCE EXCEPTION0CF FLOAT-POINT DIVIDE EXCEPTION104 GETMAIN ERROR FOR AUTH PGM106 LINK, LOAD, ATTACH, XCTL ERROR10A GETMAIN ERROR FOR AUTH PGM213 OPEN ERROR ON DASD214 CLOSE ERROR ON TAPE

222 OPERATOR CANCEL305 FREEMAIN ERROR30A FREEMAIN ERROR313 OPEN ERROR ON DASD314 CLOSE ERROR ON DASD322 EXCEEDED TIME40A FREEMAIN ERROR413 OPEN ERROR ON TAPE414 CLOSE ERROR ON DASD

MVS lookup tables


513 OPEN ERROR ON TAPE522 WAIT TIME LIMIT EXCEEDED613 OPEN ERROR ON TAPE614 CLOSE ERROR ON DASD622 TSO TASK ENDED ABNORMALLY706 LINK, LOAD, ATTACH, XCTL ERROR713 OPEN ERROR ON TAPE714 CLOSE ERROR ON TAPE804 GETMAIN ERROR806 LINK, LOAD, ATTACH, XCTL ERROR80A GETMAIN ERROR813 OPEN ERROR ON TAPE906 LINK, LOAD, ATTACH, XCTL ERROR913 OPEN ERRORA13 OPEN ERROR ON TAPEA14 CLOSE ERROR ON DASDB37 NO SPACE AVAILABLE ON VOLUMEC13 OPEN ERROR FOR CONCAT PDSD13 OPEN ERROR FOR GRAPHIC DCBD37 NO MORE PRIMARY SPACEE37 NO SPACE AVAILABLE ON VOLUME

MVS lookup tables


MVS_MIPS_TThis lookup table contains the MIPS information and must be updated with correctinformation about the machine. The lookup table associates MVS System IDs andCPU Model with a number of MIPS for the specific machine-processors. MIPS isthe unit commonly used to give the rate at which a processor performsinstructions. It is used in the benchmark to compare different machines or models.The information about MIPS is specific to all models of the machine and it can befound in the machine technical documentation.


MVS_SYSTEM_ID k CHAR(4) The MVS system ID. It can contain global search characters. FromSMF70SID.

CPU_MODEL_NO k SMALLINT The CPU model number. From SMF70MOD.

CPU_SUB_MODEL k CHAR(16) The CPU model identifier. From SMF70MDL.

MIPS FLOAT The number of MIPS associated to this specific CPU modelnumber and CPU identifier.

DESCRIPTION VARCHAR(50) Your comments about the CPU.

ExampleMVS CPU CPUSYSTEM MODEL SUBID NO MODEL MIPS DESCRIPTION------ ------ ---------------- ---------- ----------------------2DEV 2064 110 1.110E+00 -2DEV 2064 210 2.000E+00 FOR ALL 2002

MVS lookup tables


|

|||||||

|||||

|||||

||||

||||

|||||

|||||

|||||||

MVS_PRINTER_LOCThis lookup table defines the name of the place where each printer is located.


MVS_SYSTEM_ID k CHAR(4) MVS system ID that the printer is associated with. This cancontain global search characters.

PRINTER_NAME k CHAR(8) Name of the printer. For JES2 or JES3, this is the logical outputdevice name. For Print Services Facility, this is the VTAM logicalunit name or printer device name. For external writers, this isX'0000'. This can contain global search characters.

PRINTER_LOCATION CHAR(12) Name of the place where the printer is located.


MVSSYSTEM PRINTER PRINTER

ID NAME LOCATION------ -------- ------------% STO% STOCKHOLM% UP% UPPSALA% SU% SUNDSVALL% MA% MALMOE

MVS lookup tables


MVS_SYSPLEXThis lookup table associates MVS system IDs and system names with a sysplexname and a description.


MVS_SYSTEM_ID k CHAR(4) MVS system ID. This can contain global search characters.

SYSTEM_NAME k CHAR(8) MVS system name. This can contain global search characters.

DESCRIPTION VARCHAR(32) Description to be associated with the MVS system ID or theMVS system name.

SYSPLEX_NAME CHAR(8) The sysplex name to be associated with the MVS system ID orthe MVS system name.


MVSSYSTEM SYSTEM SYSPLEX

ID NAME NAME DESCRIPTION------ -------- -------- --------------------------------C00 C00 SYSPLEX0 MVS C00C01 C01 SYSPLEX0 MVS C01C02 C02 SYSPLEX0 MVS C02C03 C03 SYSPLEX0 MVS C03C% C% SYSPLEX8 MVS C80 to C88

MVS lookup tables


MVS_WORKLOAD_TYPEThis lookup table converts MVS performance groups and periods (or domains) toworkload types such as TSO, CICS, and so on. It also contains the response-timeobjectives for the workload types.



PERF_GROUP_NO k CHAR(4) MVS performance group number for the workload type.This can contain global search characters.

PERF_GROUP_PERIOD k CHAR(1) Performance group period for the performance group. Thiscan contain global search characters; usually a percentsign (%), except for short TSO transactions.

DOMAIN k CHAR(3) Domain number for the performance group. This is used fordata from SMF type 72, subtype 2 records, which does nothave performance group period. This can contain globalsearch characters; usually %, except for short TSOtransactions.

DESCRIPTION VARCHAR(32) Description of the workload type.

RESPONSE_TIME_OBJ DECIMAL(4,2) Response-time objective for the workload type, in seconds.

WORKLOAD_TYPE CHAR(8) Name of the workload type to be associated with theperformance group and period (or domain).


MVS PERF PERF RESPONSESYSTEM GROUP GROUP WORKLOAD TIME

ID NO PERIOD DOMAIN TYPE OBJ DESCRIPTION------ ----- ------ ------ -------- -------- --------------------------------% 0 % % SYSTEM - MASTER% 1 % % BATCH - BATCH ALL PERIODS% 2 0 0 TSO - TSO (SMF 30 RECORDS)% 2 1 3 TSOS 0.50 TSO SHORT% 2 % % TSOC 1.00 TSO COMPLEX% 6 % % IMS - IMS% 7 % % CICS - CICS% % % % OTHER - OTHER

MVS lookup tables


MVS_WORKLOAD2_TYPEThis lookup table converts MVS workload groups and service classes to workloadtypes, such as TSO and CICS.

This table applies to MVS version 5, running in goal mode.



WORKLOAD_GROUP k CHAR(8) Name of the workload group. This can contain global searchcharacters.

SERVICE_CLASS k CHAR(8) Name of the service class. This can contain global searchcharacters.

SERV_CLASS_PERIOD k CHAR(1) Service class period for the service class. This can containglobal search characters.

DESCRIPTION VARCHAR(32) Description of the workload type.

WORKLOAD_TYPE CHAR(8) Name of the workload type to be associated with theworkload group, service class, and period.


MVS SERVSYSTEM WORKLOAD SERVICE CLASS WORKLOAD

ID GROUP CLASS PERIOD TYPE DESCRIPTION------ -------- -------- ------ -------- ---------------------% SYSTEM % % SYSTEM MASTER% BATCH % % BATCH BATCH ALL PERIODS% TSO % 0 TSO TSO (SMF 30 RECORDS)% TSO % 1 TSOS TSO SHORT% TSO % % TSOC TSO COMPLEX% IMS % % IMS IMS% CICS % % CICS CICS% % % % OTHER OTHER

MVS lookup tables


MVS lookup tables


Chapter 23. Reports

The MVS component provides these reports:v MVS problem reports

– MVS Exceptions, Daily report– MVS No of System Abends by Abend Code, Monthly report– MVS No of User Abends by Abend Code, Monthly report– MVS Percent Abended Jobs by User Group, Monthly report– MVS No of Canceled Batch Jobs by User Group, Daily report– MVS Abended Jobs by User Group, Daily report

v MVS overview reports– MVS System Overview, Monthly Trend report– MVS Average No of Address Spaces, Monthly Trend report– MVS Activity by User Group, Daily/Monthly Overview report– MVS Activity for a User Group, Daily Trend report– MVS Users Swapped Out and Ready, Daily Profile report– MVS Workload by Workload Type, Monthly Trend report– MVS Sysplex Overview, Monthly Trend report– MVS Availability by Sysplex, Monthly Trend report– MVS Workload for a Resource Group, Daily/Monthly Trend report– MVS Workload by Resource Group, Daily/Monthly Overview report– MVS Response (Goal in %), Daily/Monthly Trend report– MVS Response (Goal in %), Daily/Monthly Overview report– MVS Response (Goal in sec), Daily/Monthly Trend report– MVS Response (Goal in sec), Daily/Monthly Overview report– MVS Exec Velocity (Goal in %), Daily/Monthly Trend report– MVS Exec Velocity (Goal in %), Daily/Monthly Overview report– MVS Response Time Distribution, Daily/Monthly Overview report

v TSO reports– MVS TSO Response Time by Workload, Daily Profile report– MVS TSO Response Time by Workload, Daily/Monthly Trend report– MVS TSO Response Time, Peak Hour, Daily Trend report– MVS Number of TSO Users, Daily Profile report– MVS TSO Transactions by Workload, Daily Profile report– MVS TSO Transactions by Workload, Daily/Monthly Trend report– MVS TSO Transactions, Peak Hour, Daily Trend report

v Summary job reports– MVS Job Statistics by User Group, Monthly Overview report– MVS Job Statistics for a User Group, Daily Trend report– MVS Number of Jobs with Tape Mounts, Daily Trend report– MVS Job Statistics by Period and User Group, Daily report

v Detailed job reports– MVS Jobs with RACF S913 Abends, Daily report– MVS Jobs with Input Queue Time > 10 Min, Daily report– MVS Jobs with Tape, Daily report

v Program reports– MVS Most CPU Consuming Programs, Monthly Overview report– MVS Most I/O Intensive Programs, Monthly Overview report– MVS Most CPU Losing Programs, Monthly Overview report– MVS CPU Usage by Job Account Field and Program, Daily report– MVS Interval Account Statistics, Detail report

405

v IPL reports– MVS Number of IPLs, Daily Trend report– MVS IPLs by Reason Code, Daily report

v Processor reports– MVS CPU Load by Period, Daily/Monthly Trend report– MVS CPU Load by Workload Type, Daily/Monthly Trend report– MVS CPU Load by Workload Type, Peak Hour, Daily report– MVS CPU Load by Workload Type, Daily Profile report– MVS Average and Maximum CPU Load, Daily Profile report– MVS CPU Load by LPAR, Daily/Monthly Trend report– MVS MIPS for System ID, Hourly list– MVS MIPS for System ID List, Daily Trend– MVS MIPS for System ID List, Monthly Trend– MVS CPU Load by LPAR, Monthly Trend per MIPS– MVS CPU Load by LPAR, Daily Trend per MIPS

v Storage reports– MVS Available CS, in Megabytes, Daily Profile report– MVS CS by Workload Type, Peak Hour, Daily Trend report– MVS ES by Workload Type, Peak Hour, Daily Trend report– MVS Storage by Workload Type, Peak Hour, Daily report– MVS CS by Workload Type, Monthly Trend report– MVS ES by Workload Type, Monthly Trend report– MVS Storage by Workload Type, Monthly Trend report– MVS CS by Type, Peak Hour, Daily Trend report– MVS ES by Type, Peak Hour, Daily Trend report– MVS Central Storage by Type, Monthly Trend report– MVS Expanded Storage by Type, Monthly Trend report

v Paging reports– MVS Paging by Subsystem, Daily Trend report– MVS Paging Rates, Daily Trend report

v Device reports– MVS DASD I/O by User Group, Monthly Overview report– MVS I/O Rates by User Group, Peak Hour, Daily report– MVS Tape I/O by User Group, Monthly Overview report– MVS Tape Demounts/MVS System, Monthly Overview report– MVS Tape Errors by Device, Monthly Overview report– MVS Tape Errors by Volume, Monthly Overview report– MVS MAGSTAR VTS Configuration report– MVS MAGSTAR VTS Physical Drive Mount Daily report– MVS MAGSTAR VTS Virtual Drive Mount Daily report– MVS MAGSTAR VTS Utilization Daily report

v Printer reports– MVS Printer Activity, Monthly Overview report– MVS Print Activity by User Group, Monthly Overview report– MVS Printer Forms Usage, Monthly Overview report

v OAM reports– OSREQ Function Invocation Statistics, Detail report– OAM/OSMC Activities Statistics, Daily report– OAM/OSMC Activities Statistics, Monthly report– LCS Opt Disk Volume R/W/D Statistics, Detail report– LCS Opt Disk Volume R/W/D Statistics, Daily report– LCS Optical R/W/Log D/Phys D Reqs, Daily report– LCS Optical R/W/Log D/Phys D Reqs, Monthly report– LCS Tape R/W/Log D Requests, Daily report

MVS reports


|||||

– LCS Tape R/W/Log D Requests, Monthly report– OAM Tape Vol R/W Stats at Demount, Daily report– OAM Tape Vol R/W Stats at Demount, Monthly report

v OpenEdition® reports– MVS OpenEdition CPU Usage by Group, Daily report– MVS OpenEdition I/O Activity by Group, Daily report– MVS OpenEdition File System Lookups by Group, Daily report– MVS OpenEdition Child Process Listing for Job report

MVS reports


MVS problem reportsThe MVS problem reports show user and system abends, canceled batch jobs, andexceptions for a selected period of time.

MVS Exceptions, Daily reportThis report lists exceptions in the EXCEPTION_T table. The EXCEPTION_T table isupdated when TSO response time is above target for a performance group periodand when SMF data is lost.


Report ID MVS71

Report group MVS reports

Source EXCEPTION_T

Attributes MVS, Problem, Abend, Daily, Detail



Date The date when the exception occurred.

Time The time when the exception occurred.

Exception ID The short description of the exception type.

Severity The severity of the problem.

Problem flag Indicates whether a problem record wasautomatically generated for the exception. N meansno.

Exception description The text that describes the exception.

MVS Exceptions, DailySystem: ’MVS1’ Date: ’2000-06-01’ to ’2000-06-15’

Exception Seve- Problem ExceptionDate Time ID rity flag description---------- -------- ------------------ ---- ------- ------------------------------2000-06-03 15.00.00 TSO response time 04 N PGN 2 Period 1 : 131 msec2000-06-03 15.00.00 TSO response time 04 N PGN 2 Period 2 : 675 msec2000-06-08 10.00.00 TSO response time 04 N PGN 2 Period 2 : 522 msec2000-06-09 21.00.00 TSO response time 04 N PGN 2 Period 3 : 1675 msec

Tivoli Decision Support for OS/390 Report: MVS71

Figure 90. Example of an MVS Exceptions, Daily report

MVS reports


MVS No of System Abends by Abend Code, Monthly reportThis report shows a list of the system abend codes issued for a specified period.You can limit the number of elements in this chart using the Row_count variable.


Report ID MVS45


Source MVS_COMPCODE_M, MVS_ABEND_CODE

Attributes MVS, Abend, System, Monthly

Variables From_month, To_month, Sysplex_name, MVS_system_ID,Row_count


Abend code The system abend code.

Explanation A short description of the system abend code.

Abends The number of jobs with this system abend code.

MVS No of System Abends by Abend Code, MonthlySysplex: ’SYSPLEX1’ System: ’MVS1’Month: ’1999-10-01’ to ’2000-02-01’

Abendcode Explanation Abends---------- ------------------------------ -----------222 OPERATOR CANCEL 86622 622 NOT IN ABEND_CODE TABLE 70806 LINK, LOAD, ATTACH, XCTL ERROR 380C4 INVALID VIRTUAL ADDRESS 31322 EXCEEDED TIME 18C03 C03 NOT IN ABEND_CODE TABLE 13E37 NO SPACE AVAILABLE ON VOLUME 11013 OPEN ERROR 704F 04F NOT IN ABEND_CODE TABLE 7522 522 NOT IN ABEND_CODE TABLE 70C1 OPERATION EXCEPTION 6002 I/O ERROR FOR SEQUENTIAL FILES 6


Figure 91. Example of an MVS No of System Abends by Abend Code, Monthly report

MVS reports


||

MVS No of User Abends by Abend Code, Monthly reportThis report lists the number of user abend codes issued during a specified period.You can limit the number of elements in this chart using the Row_count variable


Report ID MVS46


Source MVS_COMPCODE_M

Attributes MVS, Abend, User, Monthly

Variables From_month, To_month, Sysplex_name, MVS_system_ID,Row_count


Abend code The user abend code.

Abends The number of jobs with this user abend code.

MVS No of User Abends by Abend Code, MonthlySysplex: ’SYSPLEX1’ System: ’MVS1’Month: ’1999-10-01’ to ’2000-02-01’

Abendcode Abends---------- -----------2 653999 223033 123285 51002 5106 42102 4102 23000 13019 13031 1311 1


Figure 92. Example of an MVS No of User Abends by Abend Code, Monthly report

MVS reports


MVS Percent Abended Jobs by User Group, Monthly reportThis report shows how many of the jobs within each user group have abended as apercentage of the total number of jobs within the user group.


Report ID MVS47


Source MVS_ADDRSPACE_M

Attributes MVS, Job, Problem, Abend, System, User, Percent, User_group,Monthly

Variables From_month, To_month, Sysplex_name, MVS_system_ID


User group The name of the user group.

System abends (%) The number of jobs with any system abend code,in percent. Calculated as: 100 * (SYSTEM_ABENDS/ JOBS).

User abends (%) The number of jobs with any user abend code, inpercent. Calculated as: 100 * (USER_ABENDS /JOBS).

Jobs total The total number of jobs.

MVS Percent Abended Jobs by User Group, MonthlySysplex: ’SYSPLEX1’ System: ’MVS1’Date: ’1999-10-01’ to ’2000-02-01’

System UserUser abends abends Jobsgroup (%) (%) total-------- -------- -------- --------GROUP1 0.31 0.00 961GROUP2 6.25 0.00 64GROUP3 5.71 5.24 1470GROUP4 7.33 0.00 191GROUP5 4.43 1.85 2484


Figure 93. Example of an MVS Percent Abended Jobs by User Group, Monthly report

MVS reports


MVS No of Canceled Batch Jobs by User Group, Daily reportThis report shows how many of the jobs within each user group have beencanceled by the operator. The number is the same as the number of S122 and S222abends.


Report ID MVS48


Source MVS_ADDRSPACE_T

Attributes MVS, Job, Problem, Cancel, User_group, Daily

Variables From_date, To_date, Sysplex_name, MVS_system_ID



Canceled jobs The number of canceled jobs for this user group.

MVS No of Canceled Batch Jobs by User Group, DailySysplex: ’SYSPLEX1’ System: ’MVS1’Date: ’1999-10-01’ to ’2000-02-01’

User Canceledgroup jobs-------- -----------GROUP3 29GROUP5 16GROUP1 1


Figure 94. Example of an MVS No of Canceled Batch Jobs by User Group, Daily report

MVS reports


MVS Abended Jobs by User Group, Daily reportThis report shows a list of abended jobs for one or more user groups.


Report ID MVS49



Attributes MVS, Job, Problem, Abend, User_group, Daily, Detail

Variables From_date, To_date, Sysplex_name, MVS_system_ID,User_group_list



Account field1 The first accounting field.

Job name The job name.

Job class The job class.

Job start date The date when the initiator selected the first step.

Job start time The time when the initiator selected the first step.

Elapsed (sec.) The elapsed time spent for the job, in seconds,

Abend code The system abend code or user abend code.

Steps The number of steps.

Blocks transferred The number of blocks transferred.

CPU total (sec.) The total CPU time, in seconds.

Tape mounts The number of tape mounts.

MVS Abended Jobs by User Group, DailySysplex: ’SYSPLEX1’ System: ’MVS1’Date: ’1999-10-01’ to ’2000-02-01’

Job Job Blocks CPUUser Account Job Job start start Elapsed Abend trans total Tapegroup field1 name class date time (sec) code Steps ferred (sec) mounts-------- -------- -------- ----- ---------- -------- ------- ----- ----- ---------- ------- ------GROUP1 876902 JOB24 B 1992-06-11 14:43:50 1 S806 4 16 2 0

GROUP2 876903 JOBA E 1992-06-11 13:09:36 2 S0C1 1 180 3 0JOBB E 1992-06-11 13:16:38 2 S013 1 49 1 0


Figure 95. Example of an MVS Abended Jobs by User Group, Daily report

MVS reports


MVS overview reportsThe MVS overview reports show key MVS measurements, batch and TSO activity,processor time consumed, and so on, for a selected time period.

MVS reports


MVS System Overview, Monthly Trend reportThis report shows key MVS measurements.

Note: To run this report you also need to have the MVS Availability componentinstalled.


Report ID MVS01


Source MVS_SYSTEM_M, MVS_ADDRSPACE_M, MVS_PRINTER_M,AVAILABILITY_M

Attributes MVS, Batch, TSO, Address_space, Printer, Lines, Pages, Monthly,Trend

Variables From_month, To_month, MVS_system_ID, Period_name


Month start date The date of the first day of the month of themeasurement.

IPL count The number of IPLs.

Up in schedule (%) The time, in percent, of scheduled hours, when theMVS system was up and running. When decidingwhat schedule to use, Tivoli Decision Support forOS/390 uses resource type MVS and resourcename SYSTEM. The AVAILABILITY_PARM table isused to connect the resource type and name to theschedule.

Up time total (hours) The time, in hours, when the MVS system was upand running during the period. If no period wasspecified, this is the total for the month.

CPU busy (hours) The processor time, in hours.

Batch jobs (1000) The number of batch jobs, in thousands.

Abends The number of system and user abends for batchjobs only.

Lines printed (1000) The number of lines printed, in thousands.

MVS System Overview, Monthly TrendSystem: ’MVS1’ Period: ’PRIME’

Up in Up time CPU Batch Lines PagesMonth IPL schedule total busy jobs printed printed

start date count (%) (hours) (hours) (1000) Abends (1000) (1000)---------- ----- -------- ------- ------- ------ ------ ------- -------1999-06-01 2 99.5 691 105 23 322 967 271999-07-01 1 100.0 702 112 21 301 924 251999-08-01 2 99.9 680 108 29 297 903 231999-09-01 3 100.0 695 113 27 312 1121 29


Figure 96. Example of an MVS System Overview, Monthly Trend report

MVS reports


||

Pages printed (1000) The number of pages printed, in thousands.

MVS reports


MVS Average No of Address Spaces, Monthly Trend reportThis report shows the average number of batch address spaces, started tasks, andTSO users by month.


Report ID MVS04


Source MVS_SYSTEM_M

Attributes MVS, Batch, Started_task, TSO, Address_space, Monthly, Trend




Started tasks The average number of active address spacesrunning started tasks.

TSO The average number of address spaces runningTSO sessions.

Batch The average number of active address spacesrunning batch jobs.

Figure 97. Example of an MVS Average No of Address Spaces, Monthly Trend report

MVS reports


MVS Activity by User Group, Daily/Monthly Overview reportThese reports show a summary of the batch and TSO activity for each user groupduring one day.


Report ID MVS05 (daily), MVS06 (monthly)


Source MVS_ADDRSPACE_D (daily), MVS_ADDRSPACE_M (monthly)

Attributes MVS, Batch, TSO, Response, CPU, User_group, Daily, Monthly,Overview

Variables Date (daily), Month (monthly), Sysplex_name, MVS_system_ID,Period_name



Jobs The number of ended batch jobs.

TSO sessions The number of ended TSO sessions.

TSO transactions (1000) The total number of TSO transactions, inthousands.

TSO resp-time (sec) The average response time for TSO transactions, inseconds.

Job CPU (hours) The CPU time consumed for batch jobs, in hours.

TSO CPU (hours) The CPU time consumed for TSO sessions, inhours.

CPU total (hours) CPU time consumed for this user group (batch andTSO), in hours.

MVS Activity by User Group, Daily OverviewSysplex: ’SYSPLEX1’ System: ’MVS1’Date: ’2000-04-05’ Period: ’PRIME’

TSO TSO Job TSO CPUUser TSO transactions resp-time CPU CPU totalgroup Jobs sessions (1000) (sec) (hours) (hours) (hou-------- ------ -------- ------------ --------- ------- ------- -------GROUP1 13 2 0.1 0.57 0.00 0.00 0.01GROUP2 18 6 2.8 0.97 0.20 0.09 0.29GROUP3 288 57 55.9 0.75 3.21 1.05 4.27GROUP4 35 2 2.6 0.44 1.46 0.03 1.49GROUP5 272 44 3.3 0.62 0.60 0.67 1.27


Figure 98. Example of an MVS Activity by User Group, Daily Overview report

MVS reports


MVS Activity for a User Group, Daily Trend reportThis report shows a summary of the batch and TSO activity for a specific userbetween specified dates.


Report ID MVS07


Source MVS_ADDRSPACE_D

Attributes MVS, Batch, TSO, Response, CPU, User_group, Daily, Trend

Variables From_date, To_date, Sysplex_name, MVS_system_ID, Period_name,User_group


Date The date the jobs and transactions ran.

Jobs The number of ended batch jobs.

TSO sessions The number of ended TSO sessions.

TSO transactions (1000) The total number of TSO transactions, inthousands.

TSO resp-time (sec) The average response time for TSO transactions, inseconds.

Job CPU (hours) The CPU time consumed for batch jobs, in hours.

TSO CPU (hours) The CPU time consumed for TSO sessions, inhours.

Total CPU (hours) The CPU time consumed for this user group (batchand TSO), in hours.

MVS Activity for a User Group, Daily TrendSysplex: ’SYSPLEX1’ System: ’MVS1’Period: ’PRIME’ User group: ’GROUP5’

TSO TSO Job TSO TotalTSO transactions resp-time CPU CPU CPU

Date Jobs sessions (1000) (sec) (hours) (hours) (ho---------- ------ -------- ------------ --------- ------- ------- -------2000-06-01 168 29 44.1 0.87 4.03 1.11 5.142000-06-02 158 78 181.3 0.47 0.89 3.47 4.352000-06-03 221 64 14.7 0.51 0.74 0.32 1.052000-06-04 107 53 29.2 0.68 0.17 0.85 1.032000-06-05 185 104 39.6 0.61 0.79 0.96 1.75


Figure 99. Example of an MVS Activity for a User Group, Daily Trend report

MVS reports


MVS Users Swapped Out and Ready, Daily Profile reportThis report shows the number of users swapped out and ready to execute, by hour.The data is averaged over all days you specify.


Report ID MVS08


Source MVS_SYSTEM_H

Attributes MVS, Address_space, Swap, Ready, Daily, Profile

Variables From_date, To_date, MVS_system_ID, Period_name_list


Time of day The hour of the day of the measurement.

Out ready avg The average number of address spaces swappedout and ready to execute.

Figure 100. Example of an MVS Users Swapped Out and Ready, Daily Profile report

MVS reports


MVS Workload by Workload Type, Monthly Trend reportThis report shows consumed processor time (TCB and SRB) per workload type, inmillions of service units. The data is from SMF type 72 records. The report alsoshows the processor time as recorded in the SMF type 70 records converted toservice units. This value is higher than the TCB and SRB service units becausesome processor time is not captured in SMF type 72 records.

The report also shows the total processor capacity, which is the number of serviceunits that would be consumed if processor usage is 100%.


Report ID MVS10


Source MVS_WORKLOAD_M, MVS_WORKLOAD2_M, MVS_SYSTEM_M

Attributes MVS, CPU, Utilization, Workload, Trend, Monthly




Workload type The workload type associated with theperformance group and performance period.

USED The total CPU service units consumed on the

Figure 101. Example of an MVS Workload by Workload Type, Monthly Trend report

MVS reports


system. Calculated as: (SERVICE_UNITS_SRB +SERVICE_UNITS_CPU) * (CPU_BUSY_SEC) /(SRB_SECONDS + TCB_SECONDS) / 1E6.

CAPACITY The total CPU service unit capacity of the system.Calculated as: (CAPACITY_CPU_SU *PROCESSORS) / 1E6.

CPU service units by workload typeThe TCB and SRB time, in millions of service units.Calculated as: (SERVICE_UNITS_CPU +SERVICE_UNITS_SRB) / 1E6.

MVS reports


MVS Sysplex Overview, Monthly Trend reportThis report gives you an overview of the activity for all MVS systems in a sysplex.


Report ID MVS75


Source MVS_SYSTEM_M, MVS_ADDRSPACE_M, MVS_PRINTER_M

Attributes MVS, Sysplex, CPU, Abends, Printer, Lines, Pages, Monthly, Trend

Variables From_month, To_month, Sysplex_name, Period_name



MVS system ID The MVS system ID.



Batch jobs (1000) The number of batch jobs, in thousands.

Abends The number of system and user abends for batchjobs only.



MVS Sysplex Overview, Monthly TrendSysplex: ’SYSPLEX1’ Period: ’PRIME’

MVS CPU Batch Lines PagesMonth system IPL busy jobs printed printed

start date ID count (hours) (1000) Abends (1000) (1000)---------- ---------- ----- ------- ------ ------ ------- -------2000-02-01 MVS1 1 107 25 307 962 252000-02-01 MVS2 - 85 16 211 745 19

----- ------- ------ ------ ------- -------Total 1 192 41 518 1707 44

2000-03-01 MVS1 1 113 32 299 986 272000-03-01 MVS2 - 89 18 207 765 21

----- ------- ------ ------ ------- -------Total 1 202 50 506 1751 48

===== ======= ====== ====== ======= =======Total 2 394 91 1024 3458 92


Figure 102. Example of an MVS Sysplex Overview, Monthly Trend report

MVS reports


MVS Availability by Sysplex, Monthly Trend reportThis report shows sysplex availability. A sysplex is available whenever one or moreMVS systems in the sysplex are available.

Note: To run this report you also need to have the MVS Availability componentinstalled.


Report ID MVS76


Source MVS_SYSTEM_M, MVS_AVAILABILITY_M

Attributes MVS, Sysplex, CPU, Availability, Monthly, Trend

Variables From_month, To_month



Sysplex name The name of the sysplex.

Up in schedule (%) The time within the schedule, in percent ofscheduled hours, when one or more of the MVSsystems in the sysplex are up and running. Whendeciding what schedule to use, Tivoli DecisionSupport for OS/390 uses resource type ’MVS’,resource name ’SYSTEM’, area ’MVS’ and systemID ’SYSPLEX’. Resource group contains the sysplexname. The AVAILABILITY_PARM table is used toconnect these columns to the schedule.

Up in schedule (hours) The time within the schedule, in hours, when oneor more of the MVS systems in the sysplex are upand running. When deciding what schedule to use,Tivoli Decision Support for OS/390 uses resourcetype ’MVS’, resource name ’SYSTEM’, area ’MVS’and system ID ’SYSPLEX’. Resource group containsthe sysplex name. The AVAILABILITY_PARM tableis used to connect these columns to the schedule.

Up time total (%) The total time, in percent, when one or more of theMVS systems in the sysplex are up and running.

MVS Availability by Sysplex, Monthly Trend

Month Up in Up in Up time Up time CPUstart Sysplex schedule schedule total total busydate name (%) (hours) (%) (hours) (hours)---------- ---------- -------- -------- ------- ------- -------2000-01-01 SYSPLEX1 100 198.0 96 713.5 1623

SYSPLEX2 98 194.0 99 716.1 745

2000-02-01 SYSPLEX1 100 220.0 98 658.6 1584SYSPLEX2 100 220.0 100 672.0 735


Figure 103. Example of an MVS Availability by Sysplex, Monthly Trend report

MVS reports


||

Up time total (hours) The total time, in hours, when one or more of theMVS systems in the sysplex are up and running.


MVS reports


MVS Workload for a Resource Group, Daily/Monthly Trendreport

These reports show unweighted TCB and SRB service units used in a resourcegroup and minimum and maximum capacity specified for the resource group.

These reports are available only when the MVS system is running in goal mode.


Report ID MVS79 (daily), MVS80 (monthly).


Source MVS_RESOURCE_DV (daily), MVS_RESOURCE_MV (monthly)

Attributes MVS, Service_units, Resource_group, Daily, Monthly, Trend

Variables From_date (daily), To_date (daily), From_month (monthly),To_month (monthly), Period_name, Sysplex_name,Resource_group, Service_policy


Date/Month start date The date (daily), or the date of the first day of themonth (monthly) of the measurement.

Resource group The name of the resource group.

Min SUs /sec Minimum unweighted TCB and SRB service unitsspecified for the resource group.

Figure 104. Example of an MVS Workload for a Resource Group, Daily Trend report

MVS reports


Total SUs /sec Total unweighted TCB and SRB service units usedfor the resource group.

Max SUs /sec Maximum unweighted TCB and SRB service unitsspecified for the resource group.

MVS reports


MVS Workload by Resource Group, Daily/Monthly Overviewreport

These reports show unweighted TCB and SRB service units used for resourcegroups and minimum and maximum capacity specified for the resource groups.



Report ID MVS81 (daily), MVS82 (monthly).

Report group MVS System Reports

Source MVS_RESOURCE_DV (daily), MVS_RESOURCE_MV (monthly)

Attributes MVS, Service_units, Resource_group, Daily, Monthly, Overview

Variables Date_(daily), Month_(monthly), Period_name, Sysplex_name,Service_policy



Resource group The name of the resource group.

Min SUs /sec Minimum unweighted TCB and SRB service unitsspecified for the resource group.

Figure 105. Example of an MVS Workload by Resource Group, Daily Overview report

MVS reports


Total SUs /sec Total unweighted TCB and SRB service units usedfor the resource group.

Max SUs /sec Maximum unweighted TCB and SRB service unitsspecified for the resource group.

MVS reports


MVS Response (Goal in %), Daily/Monthly Trend reportThese reports show response time statistics. They report by service class andservice class period the number of transactions, in percent with a response timeless than the response time goal specified. They also show the specified goal, inpercent.





Source MVS_WORKLOAD2_D (daily), MVS_WORKLOAD2_M (monthly)

Attributes MVS, Transactions, Response, Percentile, Service_class, Daily,Monthly, Trend

Variables From_date (daily), To_date (daily), From_month (monthly),To_month (monthly), Period_name, Sysplex_name, Service_policy,Workload_group



Workload group The name of the workload group.

Service class The name of the service class.

Serv class period The service class period number.

Percent goal (sec) The specified response time goal, in seconds.

Goal (%) This column shows the number of transactions, inpercent, that should have a response time less thanthe value in the column percent goal (sec).

Actual (%) This column shows the number of transactions, inpercent, with a response time less than the value inthe column percent goal (sec).

MVS Response (Goal in %), Daily TrendSysplex: ’SYSPLEX1’ Policy: ’PRIME’

Period: ’PRIME’

Serv PercentWorkload Service class goal Goal Actual Goal

Date group class period (sec) (%) (%) importance---------- -------- -------- ------ ------- ---- ------ ----------2000-02-01 CICS CICSDE 1 0.11 60 64 2

CICSHR 1 0.24 65 62 2CICSIT 1 0.35 60 67 2CICSOE 1 0.50 60 75 2

2000-02-02 CICS CICSDE 1 0.11 60 58 2CICSHR 1 0.24 65 69 2CICSIT 1 0.35 60 62 2CICSOE 1 0.50 60 73 2


Figure 106. Example of an MVS Response (Goal in %), Daily Trend report

MVS reports


Goal importance Relative importance of the goal to be achieved.(1=highest, 2=high, 3=medium, 4=low, 5=lowest.)

MVS reports


MVS Response (Goal in %), Daily/Monthly Overview reportThese reports show response time statistics. They report by service class andservice class period the number of transactions, in percent with a response timeless than the response time goal specified. They also show the specified goal, inpercent.






Attributes MVS, Transactions, Response, Percentile, Service_class, Daily,Monthly, Overview

Variables Date_(daily), Month_(monthly), Period_name, Sysplex_name,Service_policy, Workload_group





Period The service class period number.

Figure 107. Example of an MVS Response (Goal in %), Daily Overview report

MVS reports


Goal (sec) The specified response time goal, in seconds.

Goal (%) Goal (%) shows the number of transactions, inpercent, that should have a response time less thanthe value in Goal (sec).

Actual (%) Actual (%) shows the number of transactions, inpercent, with a response time less than the value inGoal (sec).

MVS reports


MVS Response (Goal in sec), Daily/Monthly Trend reportThese reports show response time statistics. They report by service class andservice class period the average response time, in seconds, and the goal specified.






Attributes MVS, Transactions, Response, Average, Service_class, Daily,Monthly, Trend






Service class period The service class period number.

Goal (sec) The specified average response time goal, inseconds.

Average response (sec) Average response time, in seconds.


MVS Response (Goal in sec), Daily TrendSysplex: ’SYSPLEX1’ Policy: ’PRIME’

Period: ’PRIME’

Service AverageWorkload Service class Goal response Goal

Date group class period (sec) (sec) importance---------- -------- -------- -------- -------- -------- ----------2000-02-01 PRODUCTN TSOSTC 1 0.30 0.22 1

2 0.90 0.76 23 2.00 1.34 3

2000-02-01 PRODUCTN TSOSTC 1 0.30 0.19 12 0.90 0.71 23 2.00 1.28 3


Figure 108. Example of an MVS Response (Goal in sec), Daily Trend report

MVS reports


MVS Response (Goal in sec), Daily/Monthly Overview reportThese reports show response time statistics. They report by service class andservice class period the average response time, in seconds, and the goal specified.






Attributes MVS, Transactions, Response, Average, Service_class, Daily,Monthly, Overview

Variables Date (daily), Month (monthly), Period_name, Sysplex_name,Service_policy, Workload_group






Goal (sec) The specified average response time goal, inseconds.

Average response (sec) Average response time, in seconds.

Figure 109. Example of an MVS Response (Goal in sec), Daily Overview report

MVS reports


MVS Exec Velocity (Goal in %), Daily/Monthly Trend reportThese reports show execution velocity statistics. They report by service class andservice class period the execution velocity, in percent, and the goal specified.






Attributes MVS, Execution, Velocity, Service_class, Daily, Monthly, Trend






Service class period The service class period number.

Goal (%) The specified execution velocity goal, in percent.

Exec velocity (%) Execution velocity, in percent.


MVS Exec Velocity (Goal in %), Daily TrendSysplex: ’SYSPLEX1’ Policy: ’PRIME’

Period: ’PRIME’

Service ExecWorkload Service class Goal velocity Goal

Date group class period (%) (%) importance---------- -------- -------- -------- -------- -------- ----------2000-02-01 PRODUCTN BATCH 1 55 60 3

2 30 41 3HOTBATCH 1 80 78 2

2000-02-01 PRODUCTN BATCH 1 55 64 32 30 37 3

HOTBATCH 1 80 81 2


Figure 110. Example of an MVS Exec Velocity (Goal in %), Daily Trend report

MVS reports


MVS Exec Velocity (Goal in %), Daily/Monthly Overview reportThese reports show execution velocity statistics. They report by service class andservice class period the execution velocity, in percent, and the goal specified.






Attributes MVS, Execution, Velocity, Service_class, Daily, Monthly, Overview

Variables Date (daily), Month (monthly), Period_name, Sysplex_name,Service_policy, Workload_group






Figure 111. Example of an MVS Exec Velocity (Goal in %), Daily Overview report

MVS reports


Goal (%) The specified execution velocity goal, in percent.

Exec velocity (%) Execution velocity, in percent.

MVS reports


MVS Response Time Distribution, Daily/Monthly Overviewreport

These reports show the response time distribution for one or more service classesand periods.

For example:

The vertical value that corresponds to a horizontal value of 50 is the percentage oftransactions that have a response time of less than 50% of the response time goal.

The vertical value that corresponds to a horizontal value of 60 is the percentage oftransactions that have a response time of between 50% and 60% of the responsetime goal.

The vertical value that corresponds to a horizontal value of 32 767 is thepercentage of transactions that have a response time greater than 400% of theresponse time goal.

The legend shows the service class name and period, and the response time goal,in seconds.





Source MVS_GOAL_ACT_D (daily), MVS_GOAL_ACT_M (monthly)

Attributes MVS, Transactions, Response, Percentile, Service_class, Period,Daily, Monthly, Overview

Variables Date (daily), Month (monthly), Period name, Sysplex name, Servicepolicy, Workload group, Serv class list, Serv class period

MVS reports



Percentage of response time goalThe percentage of response time goal achieved

Transactions in percent The number of transactions, in percent.

Report key The service class name and period, and theresponse time goal (in seconds).

Figure 112. Example of an MVS Response Time Distribution, Daily Overview report

MVS reports


TSO reportsThe TSO reports show TSO response times, users, and transactions for a selectedtime period.

MVS TSO Response Time by Workload, Daily Profile reportThis report shows average TSO response times per workload type. The responsetimes are given by hour and averaged over the number of days you specify.


Report ID MVS11


Source MVS_WORKLOAD_H

Attributes MVS, TSO, Response, Workload, Daily, Profile

Variables From_date, To_date, MVS_system_ID, Workload_typelist,Period_name_list



Workload type The workload types for which TSO response timeis reported.

TSO response time The TSO response time, in seconds, for the

Figure 113. Example of an MVS TSO Response Time by Workload, Daily Profile report

MVS reports


workload type. Calculated as:TRAN_ELAPSED_SEC / TRANSACTIONS.

MVS reports


MVS TSO Response Time by Workload, Daily/Monthly Trendreport

These reports show TSO response times per day and workload type for a givenperiod.




Source MVS_WORKLOAD_D (daily), MVS_WORKLOAD_M (monthly)

Attributes MVS, TSO, Response, Workload, Daily, Monthly, Trend

Variables From_date and To_date (daily), From_month and To_month(monthly), MVS_system_ID, Period_name, Workload_typelist


Date/month start date The date (daily), or the date of the first day of themonth (monthly) of the measurement.


TSO response time The TSO response time, in seconds, for theworkload type. Calculated as:TRAN_ELAPSED_SEC / TRANSACTIONS.

Figure 114. Example of an MVS TSO Response Time by Workload, Daily Trend report

MVS reports


MVS TSO Response Time, Peak Hour, Daily Trend reportThis report shows the TSO response times per workload type during the peakhour. The peak hour is the hour with the maximum number of TSO transactions.


Report ID MVS13



Attributes MVS, TSO, Response, Workload, Peak, Daily, Trend

Variables From_date, To_date, MVS_system_ID, Workload_typelist



Hour The peak hour for the day.


TSO response time The TSO response time, in seconds, for theworkload type. Calculated as:TRAN_ELAPSED_SEC / TRANSACTIONS.

Figure 115. Example of an MVS TSO Response Time, Peak Hour, Daily Trend report

MVS reports


MVS Number of TSO Users, Daily Profile reportThis report shows the average number of TSO users. The average numbers aregiven by hour and averaged over the number of days you specify.


Report ID MVS15


Source MVS_SYSTEM_H

Attributes MVS, TSO, Logged_on, Daily, Profile




TSO users avg The average number of TSO users.

Figure 116. Example of an MVS Number of TSO Users, Daily Profile report

MVS reports


MVS TSO Transactions by Workload, Daily Profile reportThis report shows the average number of TSO transactions. The average numbersare given by hour and workload type, and averaged over the number of days youspecify.


Report ID MVS16



Attributes MVS, TSO, Transactions, Workload, Daily, Profile

Variables From_date, To_date, MVS_system_ID, Workload_typelist,Period_name_list



Workload type The workload types for which the number oftransactions are reported.

Transactions The average number of TSO transactions.

Figure 117. Example of an MVS TSO Transactions by Workload, Daily Profile report

MVS reports


MVS TSO Transactions by Workload, Daily/Monthly Trendreport

These reports show the number of TSO transactions by day and workload type.




Source MVS_WORKLOAD_D (daily), MVS_WORKLOAD_M (monthly)

Attributes MVS, TSO, Transactions, Workload, Daily, Monthly, Trend

Variables From_date and To_date (daily), From_month and To_month(monthly), MVS_system_ID, Period_name, Workload_typelist




Transactions The number of TSO transactions.

Figure 118. Example of an MVS TSO Transactions by Workload, Daily Trend report

MVS reports


MVS TSO Transactions, Peak Hour, Daily Trend reportThis report shows the number of TSO transactions during the peak hours. Thepeak hour is the hour with the maximum number of TSO transactions.


Report ID MVS18



Attributes MVS, TSO, Transactions, Workload, Peak, Daily, Trend

Variables From_date, To_date, MVS_system_ID, Workload_typelist



Hour The peak hour for the day.


Transactions The number of transactions.

Figure 119. Example of an MVS TSO Transactions, Peak Hour, Daily Trend report

MVS reports


Summary job reportsThe summary job reports show job statistics by user groups and for user groupsfor a selected time period.

MVS Job Statistics by User Group, Monthly Overview reportThis report shows job statistics (number of jobs, number of failed jobs, total CPUtime, and CPU time lost because of failed jobs) by user group.


Report ID MVS50


Source MVS_ADDRSPACE_M

Attributes MVS, Job, Abend, Cancel, CPU, User_group, Monthly, Overview




Jobs The number of jobs for this user group.

Steps The number of steps.

Failed count The number of failed jobs. Calculated as:SYSTEM_ABENDS + USER_ABENDS +JOBS_CANCELED.

Failed (%) The number of failed jobs, as a percentage of thetotal number of jobs. Calculated as:(SYSTEM_ABENDS + USER_ABENDS +JOBS_CANCELED) * 100 / JOBS.

CPU total (hours) The total CPU time, in hours.

CPU lost (hours) The total CPU time lost because of abends or jobscanceled. This value includes all CPU time spentfor the job, including previous steps that completednormally.

MVS Job Statistics by User Group, Monthly OverviewSysplex: ’SYSPLEX1’ System: ’MVS1’Month: ’1999-10-01’ to ’2000-02-01’

CPU CPUUser Failed Failed total lostgroup Jobs Steps count (%) (hours) (hours)-------- ------- ------- ------ ------- ---------- ----------GROUP1 1032 1127 14 1.30 3.23 0.15GROUP2 113 157 13 11.50 6.44 0.61GROUP3 1821 3460 418 22.90 14.12 3.23GROUP4 224 470 31 13.80 0.41 1.68GROUP5 3261 6535 570 17.40 25.56 12.22


Figure 120. Example of an MVS Job Statistics by User Group, Monthly Overview report

MVS reports


MVS Job Statistics for a User Group, Daily Trend reportThis report shows the job statistics (number of jobs, number of failed jobs, totalCPU time, and CPU time lost because of failed jobs) for a specific user group.


Report ID MVS51



Attributes MVS, Job, Abend, Cancel, CPU, User_group, Daily, Trend

Variables From_date, To_date, Sysplex_name, MVS_system_ID, User_group



Jobs The number of jobs run on this date.

Steps The number of steps run on this date.

Failed count The number of failed jobs. Calculated as:SYSTEM_ABENDS + USER_ABENDS +JOBS_CANCELED.

Failed (%) The number of failed jobs, as a percentage of thetotal number of jobs. Calculated as:(SYSTEM_ABENDS + USER_ABENDS +JOBS_CANCELED) * 100 / JOBS.

CPU total (hours) The total CPU time, in hours.

CPU lost (hours) The total CPU time lost because of abends or jobscanceled. This value includes all CPU time spentfor the job, including previous steps that completednormally.

MVS Job statistics for a User Group, Daily TrendSysplex: ’SYSPLEX1’ System: ’MVS1’

User group: ’GROUP7’

CPU CPUFailed Failed total lost

Date Jobs Steps count (%) (hours) (hours)---------- ------- ------- ------ ------- -------- --------1999-11-15 346 901 98 28.32 1.15 0.711999-11-16 5527 18482 1226 22.18 11.39 6.451999-11-17 5574 18428 1105 19.82 11.15 8.051999-11-18 5636 18945 1307 23.19 36.36 31.971999-11-19 5211 17332 1203 23.09 11.94 7.62


Figure 121. Example of an MVS Job Statistics for a User Group, Daily Trend report

MVS reports


MVS Number of Jobs with Tape Mounts, Daily Trend reportThis report shows the number of jobs that required tape mounts for a specific usergroup by date and hour.


Report ID MVS52



Attributes MVS, Job, Operations, Tape, Daily, Trend




Hour The hour of the measurement.

Jobs The number of jobs that required tape mounts.

MVS Number of Jobs with Tape Mounts, Daily TrendSysplex: ’SYSPLEX1’ System: ’MVS1’

User group: ’GROUP7’

<------------------------------- Hour -------------------------------><- 7 -> <- 9 -> < 11 -> < 12 -> < 13 -> < 14 -> < 15 -> < 18 -> TOTAL

Date---------- ----- ----- ----- ----- ----- ----- ----- ----- -----1999-06-03 1 11999-06-11 2 21999-06-15 5 2 1 1 91999-07-28 1 1 21999-08-04 1 2 31999-08-05 2 2

===== ===== ===== ===== ===== ===== ===== ===== =====Total 1 8 4 1 2 1 1 1 19


Figure 122. Example of an MVS Number of Jobs with Tape Mounts, Daily Trend report

MVS reports


MVS Job Statistics by Period and User Group, Daily reportThis report shows job statistics (job queue time and elapsed time spent for jobs) byperiod and user group.


Report ID MVS53



Attributes MVS, Job, Input_queue, Elapsed, User_group, Daily, Trend




Period name The name of the period.


Jobs The number of jobs.

Avg job queue (hours) The average time spent by a job in the inputqueue, in hours. Calculated as:JOB_QUEUE_SECONDS / JOBS.

Total job queue (hours) The total time spent for jobs in the input queue, inhours.

Avg elapsed (hours) The average elapsed time spent for a job, in hours.Calculated as: (ELAPSED_SECONDS / JOBS) /3600.

Total elapsed (hours) The total elapsed time spent for jobs, in hours.

MVS Job Statistics by Period and User Group, DailySysplex: ’SYSPLEX1’ System: ’MVS1’

Avg Totaljob job Avg Total

Period User queue queue elapsed elapsedDate name group Jobs (hours) (hours) (hours) (hours)---------- -------- -------- ------ -------- -------- -------- --------1999-11-16 NIGHT GROUPA 301 0.010 3.64 0.150 54.22

GROUPB 1509 0.012 18.07 0.181 272.39PRIME GROUPA 804 0.004 5.47 0.123 114.23

GROUPB 4018 0.007 27.15 0.144 579.87

1999-11-17 NIGHT GROUPA 326 0.011 4.82 0.179 59.54GROUPB 1615 0.015 24.42 0.185 298.71

PRIME GROUPA 802 0.003 2.98 0.139 113.78GROUPB 3959 0.003 11.87 0.145 574.69


Figure 123. Example of an MVS Job Statistics by Period and User Group, Daily report

MVS reports


Detailed job reportsThe detailed job reports show detailed lists of jobs ending in security violations,jobs with input queue times longer than 10 minutes, and jobs that required tapemounts for a selected time period.

MVS Jobs with RACF S913 Abends, Daily reportThis report gives a list of jobs that ended in security violations.


Report ID MVS54



Attributes MVS, Job, Problem, Security, Violation, Daily, Detail





RACF user ID The RACF user ID.


Date The date when the job was recognized by thereader.

Time The time when the job was recognized by thereader.


MVS Jobs with RACF S913 Abends, DailyDate: ’2000-06-14’ to ’2000-06-18

MVSsystem User RACF Account JobID group user ID field1 Date Time name

------ -------- -------- -------- ---------- -------- --------MVS1 GROUP3 USER322 312333 2000-06-16 16.35.56 ABC001

GROUP5 USER512 523455 2000-06-15 09.37.27 DEF002USER518 533356 2000-06-16 11.17.14 GHI003


Figure 124. Example of an MVS Jobs with RACF S913 Abends, Daily report

MVS reports


MVS Jobs with Input Queue Time > 10 Min, Daily reportThis report shows a list of jobs that had an input queue time longer than 10minutes.


Report ID MVS55



Attributes MVS, Job, Problem, Input_queue, Worst, Daily, Detail

Variables From_date, To_date, Sysplex_name, MVS_system_ID, Jobclass






Job class The job class.

Date job input The date when the job was recognized by thereader.

Time job input The time when the job was recognized by thereader.

Job queue (sec) The time spent by the job in the input queue, inseconds.

Elapsed (sec) The elapsed time spent for the job, in seconds.

MVS Jobs with Input Queue Time > 10 Min, DailySysplex: ’SYSPLEX1’ System: ’MVS1’Date: ’1999-06-01’ to ’1999-06-30’

User RACF Account Job Job job job queue Elapsedgroup user ID field1 name class input input (sec) (sec)-------- -------- -------- -------- ----- ---------- -------- ------ --------GROUP1 OPERATO 934002 MDBDC06 C 1999-06-05 13.12.22 691 415

934002 MLCSDL1 C 1999-06-05 13.12.23 689 487934002 MLCSP01 C 1999-06-05 13.12.25 688 311934002 MLCSP02 C 1999-06-05 13.12.26 1362 219

GROUP5 WS10 934002 WCLEAR4 C 1999-06-15 09.18.54 1102 287934002 WSYSMXA C 1999-06-15 09.18.55 1389 378


Figure 125. Example of an MVS Jobs with Input Queue Time > 10 Min, Daily report

MVS reports


MVS Jobs with Tape, Daily reportThis report gives a list of jobs that required tape mounts.


Report ID MVS56



Attributes MVS, Job, Operations, Tape, Daily, Detail







Date job input The date when the job was recognized by thereader.

Time job input The time when the job was recognized by thereader.

Tape mounts The number of tape mounts.

MVS Jobs with Tape, DailySysplex: ’SYSPLEX1’ System: ’MVS1’Date: ’1999-06-01’ to ’1999-06-30’

Date TimeUser RACF Account Job job job Tapegroup user ID field1 name input input mounts-------- -------- -------- -------- ---------- -------- ------GROUP1 OPERATO 934002 MCOR105 1999-06-05 13.12.18 1

934002 MCOR106 1999-06-05 13.12.19 1934002 MDBDC05 1999-06-05 13.12.21 1934002 MDBDC06 1999-06-05 13.12.22 2934002 MLCSDL1 1999-06-05 13.12.23 2


Figure 126. Example of an MVS Jobs with Tape, Daily report

MVS reports


Program reportsThe program reports show the most and least CPU consuming programs and themost I/O intensive programs for a selected time period.

MVS Most CPU Consuming Programs, Monthly Overviewreport

This report shows the programs that consumed the most processor time. Theprograms are listed in the order of the processor time used. You can limit thenumber of elements in this chart using the Row_count variable.


Report ID MVS57


Source MVS_PROGRAM_M

Attributes MVS, Program, CPU, Abend, Worst, Monthly, Overview

Variables From_month, To_month, Sysplex_name, MVS_system_ID,Period_name, Row_count


Program name The program name.

CPU (hours) The total amount of CPU time consumed for theprogram, in hours. Calculated as:CPU_TOTAL_SECONDS / 3600.

Elapsed (hours) The total elapsed time, in hours. Calculated as:ELAPSED_SECONDS / 3600.

Steps The number of steps (that is, the number of timesthe program was executed.)

System abends The number of system abends for this program.

User abends The number of user abends for this program.

MVS Most CPU Consuming Programs, Monthly OverviewSysplex: ’SYSPLEX1’ System: ’MVS1’

Date: ’1999-11-01’ to ’1999-11-01’ Period: ’PRIME’

CPU Lost BlocksProgram CPU Elapsed System User lost elapsed transname (hours) (hours) Steps abends abends (hours) (hours)

-------- ------- ------- ------- ------ ------ ------- ------- ----------IKJEFT01 3.60 310 622 0 0 0.00 0 2.212E+06IDCAMS 2.66 21 372 0 0 0.00 0 2.057E+05DRAWRBLD 2.20 32 334 0 0 0.00 0 1.514E+07DFSRRC00 1.12 112 945 0 0 0.00 0 2.526E+06IEBGENER 1.10 11 8992 0 0 0.00 0 5.056E+05IFASMFDP 0.91 12 56 0 0 0.00 0 6.158E+06DICREATE 0.65 10 11 0 0 0.00 0 2.502E+06Y1458 0.62 4 6124 0 0 0.00 0 2.442E+05IEBCOPY 0.55 9 811 0 0 0.00 0 2.575E+06DFSMVRC0 0.42 670 33 0 0 0.00 0 6.282E+05


Figure 127. Example of an MVS Most CPU Consuming Programs, Monthly Overview report

MVS reports


CPU lost (hours) The amount of CPU time consumed for the stepsthat did not complete normally, in hours.Calculated as: CPU_LOST_SECONDS / 3600.

Lost elapsed (hours) The amount of elapsed time consumed for thesteps that did not complete normally, in hours.Calculated as: LOST_ELAPSED_SEC / 3600.

Blocks transferred The total number of blocks transferred.

MVS reports


MVS Most I/O Intensive Programs, Monthly Overview reportThis report shows the programs that transferred the most I/O blocks. Theprograms are listed in the order of the number of I/O blocks transferred. You canlimit the number of elements in this chart using the Row_count variable.


Report ID MVS58



Attributes MVS, Program, I/O, Abend, Worst, Monthly, Overview







Steps The number of steps (that is, the number of timesthe program was executed).



MVS Most I/O Intensive Programs, Monthly OverviewSysplex: ’SYSPLEX1’ System: ’MVS1’


Blocks CPU LostProgram trans CPU Elapsed System User lost elapsedname ferred (hours) (hours) Steps abends abends (hours) (hours)

-------- ---------- ------- ------- ------- ------ ------ ------- -------DRAWRBLD 1.514E+07 2.20 31 334 0 0 0.00 0IFASMFDP 6.158E+06 1.09 12 66 0 0 0.00 0DMSDDLR 3.411E+06 0.41 4 4331 0 0 0.00 0IEBCOPY 2.575E+06 0.52 11 821 0 0 0.00 0DFSRRC00 2.526E+06 1.22 112 895 0 0 0.00 0DICREATE 2.502E+06 0.62 9 9 0 0 0.00 0IKJEFT01 2.212E+06 3.61 310 622 0 0 0.00 0DFSMVRC0 6.282E+05 0.44 689 28 0 0 0.00 0IEBGENER 5.056E+05 1.10 7 9982 0 0 0.00 0ARCPRLOG 2.919E+05 0.06 3 13 0 0 0.00 0


Figure 128. Example of an MVS Most I/O Intensive Programs, Monthly Overview report

MVS reports




MVS reports


MVS Most CPU Losing Programs, Monthly Overview reportThis report lists the programs that lost the most processor time. The list appears indescending order. You can limit the number of elements in this chart using theRow_count variable.


Report ID MVS59



Attributes MVS, Program, CPU, Abend, Worst, Monthly, Overview








Steps The number of steps (that is, the number of timesthe program was executed).




MVS Most CPU Losing Programs, Monthly OverviewSysplex: ’SYSPLEX1’ System: ’MVS1’


CPU Lost BlocksProgram lost elapsed CPU Elapsed System User transname (hours) (hours) (hours) (hours) Steps abends abends ferred

-------- ------- ------- ------- ------- ------- ------ ------ ----------Y1122 9.23 1009 9.34 10737 38 6 0 4.225E+05Y0377 3.14 17 7.52 279 882 43 2 9.002E+06TESTLC 1.29 4 3.76 12 299 8 55 3.244E+05


Figure 129. Example of an MVS Most CPU Losing Programs, Monthly Overview report

MVS reports


MVS CPU Usage by Job Account Field and Program, Dailyreport

This report shows CPU usage by job account field and program.


Report ID MVS101


Source MVS_ACCNT_PGM_T

Attributes MVS, CPU, Account, Daily, Detail

Variables From_date, To_date, Sysplex, MVS_system_ID


Job account field First job accounting field.

Program name The name of the executed program.

Program start date The date of program execution.

MVS CPU usage by Account field, dailySysplex: ’SYSPLEX1’ System: ’MVS1’Date: ’1999-07-27’ to ’1999-07-27’

Job Program Program CPUaccount Program start start usagefield1 name date time (seconds)-------- -------- ---------- -------- ------------------- IEFBR14 1999-07-27 16.31.53 0.0

IEFBR14 1999-07-27 16.31.53 0.0IEFBR14 1999-07-27 16.31.53 0.0

ACCT1234 IEFBR14 1999-07-27 16.26.22 0.0IEFBR14 1999-07-27 16.26.22 0.0

A11 IEFBR14 1999-07-27 16.25.42 0.0IEFBR14 1999-07-27 16.25.42 0.0

JOBX IEFBR14 1999-07-27 16.19.00 0.0IEFBR14 1999-07-27 16.19.00 0.0IEFBR14 1999-07-27 16.19.00 0.0IFASMFDP 1999-07-27 16.19.57 0.2IFASMFDP 1999-07-27 16.27.19 0.2IFASMFDP 1999-07-27 16.32.07 2.3

TEST HEWL 1999-07-27 16.14.35 0.3

888102 DRLPLC 1999-07-27 16.14.59 23.4DRLPLC 1999-07-27 16.20.40 22.1DRLPLC 1999-07-27 16.27.55 22.9DRLPLC 1999-07-27 16.32.44 24.8

Tivoli Decision Support for OS/390: MVS101

Figure 130. Example of an MVS CPU Usage by Job Account Field, Daily report

MVS reports


Program start time The time of program execution.

CPU usage (seconds) The amount of CPU consumed for the program.

MVS reports


MVS Interval Account Statistics, Detail reportThis report shows CPU usage by job, by program, interval and job account field.


Report ID MVS105


Source MVS_ACCNT23_PGM_T

Attributes MVS, Account, Interval, CPU

Variables Date, Sysplex_Name, MVS_system_ID


Program name The name of the executed program.

Interval start time The Interval Start Time for which the statistics aretracked.

Interval end time The Interval End Time for which the statistics aretracked.

Interval Duration The time between the start timestamp and the endtimestamp in seconds.

MVS Interval Account Statistics, DetailSYSPLEX: ’SYSPLEX1’ SYSTEM: ’2A96’

DATE: 1999-12-15

Interval Interval JobProgram Start End Interval Accnt CPU UsageName Time Time Duration Field1 Seconds-------- -------- -------- ---------- -------- ------------------IEBGENER 23.56.38 00.02.15 5.625 - 0.10BPXPINPR 23.48.56 00.02.55 13.984 - 0.00ETPPRFMT 23.46.43 00.03.12 16.484 - 0.20SDI6150 23.53.18 00.04.48 11.484 - 0.00DFHSIP 23.59.00 00.05.09 6.159 - 11.70IKTCAS00 23.51.58 00.05.57 13.982 - 0.00SNALINK 23.52.38 00.06.37 13.982 - 0.00GFTEMTCP 23.52.53 00.06.52 13.981 - 0.00DFHSIP 23.59.00 00.08.30 9.502 - 6.90IEEMB860 23.59.00 00.09.00 9.998 - 13.50IEAVTDSV 23.59.00 00.09.00 9.999 - 0.00IXZIX00 23.59.00 00.09.00 9.998 - 0.00IFASMF 23.59.00 00.09.00 9.998 - 0.10IGG0CLX0 23.59.00 00.09.00 9.999 - 17.20

CTSMAIN 23.59.00 00.09.00 9.999 - 0.00LANDMARK 23.59.00 00.09.00 9.999 - 382.10SARSTCBT 23.59.00 00.09.00 9.999 - 3.40DFHSIP 23.59.00 00.09.00 9.999 - 0.60OUTBOUND 23.59.00 00.09.00 9.999 - 0.90NSIGHTPC 23.56.20 00.10.44 14.402 - 0.00

Tivoli Decision Support for OS/390: MVS105

Figure 131. Example of part of an MVS Interval Account Statistics, Detail report

MVS reports


Job Accnt Field1 The first job accounting field.

CPU Usage Seconds The total amount of CPU time used for theprogram, in seconds. This is the sum of all validCPU times.

MVS reports


IPL reportsThe IPL reports show the number of IPLs and the IPL reason codes for a selectedtime period.

MVS Number of IPLs, Daily Trend reportThis report shows number of IPLs by MVS system ID and date.


Report ID MVS60


Source MVS_SYSTEM_D

Attributes MVS, Operations, IPL, Daily, Trend

Variables Sysplex_name, From_date, To_date




Date The date the IPL occurred.


MVS Number of IPLs, Daily Trend

MVSSysplex system IPLname ID Date count

------- ------ ---------- -----------SYSPLEX1 MVSE 1999-06-11 1

SYSPLEX2 MVS1 1999-08-05 2

SYSPLEX3 MVS4 1999-06-11 1


Figure 132. Example of an MVS Number of IPLs, Daily Trend report

MVS reports


MVS IPLs by Reason Code, Daily reportThis report shows a detailed list of all IPLs.


Report ID MVS61


Source MVS_IPL_T

Attributes MVS, Operations, IPL, Daily, Detail



Date The date the IPL occurred.

Time The time the IPL occurred.


System downtime The time when the system went down, as enteredby the operator.

IPL reason The reason for the IPL.

Operator name The name of the operator.

MVS IPLs by Reason Code, DailyDate: ’1999-09-15’ to ’1999-09-30’

MVS Systemsystem down IPL Operator

Date Time ID time reason name---------- ---------- ------ ---------- --------------- --------------------1999-09-27 05.10.00 MVS1 03.00.00 Planned nn


Figure 133. Example of an MVS IPLs by Reason Code, Daily report

MVS reports


Processor reportsThe processor reports show processor loads by period and workload, and theaverage and maximum processor load for a selected time period.

MVS CPU Load by Period, Daily/Monthly Trend reportThese reports show total CPU time in percent of measured time multiplied bynumber of processors, by period and month for monthly, and by day for daily.




Source MVS_SYSTEM_D(daily), MVS_SYSTEM_M(monthly)

Attributes MVS, CPU, Utilization, Period, Daily, Monthly, Trend

Variables From_date and To_date (daily), From_month and To_month(monthly), MVS_system_ID

Figure 134. Example of an MVS CPU Load by Period, Monthly Trend report

MVS reports




Period name The period names for which CPU load is reported.

CPU time (percent) The total CPU time used, in percent of themeasured time multiplied by the number ofprocessors. Calculated as: (100 * CPU_BUSY_SEC)/ CPU_ONLINE_SEC.

MVS reports


MVS CPU Load by Workload Type, Daily/Monthly Trend reportThese reports show total CPU time in percent of measured time multiplied bynumber of processors, by workload type and month for monthly, and by day fordaily.

These reports also show the total CPU time as measured in the SMF type 70record. The difference between the total CPU time and the sum of all workloads isCPU time not captured in the SMF type 72 record.




Source MVS_WORKLOAD_D, MVS_WORKLOAD2_D, andMVS_SYSTEM_D (daily), MVS_WORKLOAD_M,MVS_WORKLOAD2_M, and MVS_SYSTEM_M (monthly)

Attributes MVS, CPU, Utilization, Workload, Daily, Monthly, Trend

Variables From_date and To_date (daily), From_month and To_month(monthly), MVS_system_ID, Period_name

MVS reports



Date/month start date The date (daily report) or the date of the first dayof the month (monthly report) of the measurement.

Workload type The workload types for which the CPU load isreported.

Total CPU time (percent) The total CPU time, in percent of measured timemultiplied by the number of processors. Calculatedas: 100 * CPU_BUSY_SEC / CPU_ONLINE_SEC.

CPU time (percent) The percentage of CPU time used for eachworkload type. Calculated as: 100 *(TCB_SECONDS + SRB_SECONDS) /CPU_ONLINE_SEC.

Figure 135. Example of an MVS CPU Load by Workload Type, Monthly Trend report

MVS reports


MVS CPU Load by Workload Type, Peak Hour, Daily reportThis report shows the total CPU time in percent of measured time multiplied bythe number of processors, by workload type during the peak hours. Peak hour isthe hour during the period with the maximum CPU load.


Report ID MVS28


Source MVS_WORKLOAD_H, MVS_WORKLOAD2_H, andMVS_SYSTEM_H

Attributes MVS, CPU, Utilization, Workload, Peak, Daily, Trend

Variables From_date, To_date, MVS_system_ID, Period_name

Figure 136. Example of an MVS CPU Load by Workload Type, Peak Hour, Daily report

MVS reports




Hour The peak hour of the day.

Workload type The workload types for which the CPU load isreported.


MVS reports


MVS CPU Load by Workload Type, Daily Profile reportThis report shows total CPU time in percent of measured time multiplied bynumber of processors, by workload type each hour during an average day. Thevalues are averaged over all days selected by the user.


Report ID MVS29


Source MVS_WORKLOAD_H, MVS_WORKLOAD2_H, andMVS_SYSTEM_H

Attributes MVS, CPU, Utilization, Workload, Daily, Profile




Workload type The workload types for which CPU load isreported.


Figure 137. Example of an MVS CPU Load by Workload Type, Daily Profile report

MVS reports


MVS Average and Maximum CPU Load, Daily Profile reportThis report shows the average and maximum CPU load, in percent, for each hourduring an average day. The values are averaged over all days selected by the user.Average is total CPU time in percent of measured time multiplied by number ofprocessors. Maximum is the largest percentage calculated for all processors andRMF intervals during one hour.


Report ID MVS24


Source MVS_SYSTEM_H

Attributes MVS, CPU, Utilization, Daily, Profile


Figure 138. Example of an MVS Average and Maximum CPU Load, Daily Profile report

MVS reports




Max The maximum CPU time, in percent of interval asmeasured by the SMF type 70 record.

Avg The average CPU time for all processors in percentof measured time multiplied by number ofprocessors. Calculated as: 100.0 * CPU_BUSY_SEC/ CPU_ONLINE_SEC.

MVS reports


MVS CPU Load by LPAR, Daily/Monthly Trend reportThese reports show CPU usage by logical partition in percent of the total CPUcapacity for all shared processors.




Source MVS_LPAR_D (daily), MVS_LPAR_M (monthly)

Attributes MVS, LPAR

Variables From_date and To_date (daily), From_month and To_month(monthly), MVS_system_ID, Period_name, Processor_type

Processor type: All

MVS reports




LPAR name The name of the logical partition.

CPU time (percent) The total CPU usage in percent including LPARmanagement time. When associated with thephysical partition, this is the physical processorresource used by the LPAR scheduler to managethe physical configuration.

MVS reports


MVS MIPS for System ID, Hourly listThis report shows the list of the MIPS for the System.


Report ID MVSM1

Report group MVS System reports

Source MVS_SYSTEM_H

Attributes MVS, MIPS, System

Variables From_date, To_date, Time, Period_name,MVS_system_ID

MVS Mips for System ID Hourly ListFrom date: All To date: All

System ID: All

Cpu CpuSystem busy busy

Date Time Period ID sec mips---------- -------- -------- ------ ---------- ----------2001-12-19 17.00.00 NIGHT 2DEV 2.477E+04 2.749E+032001-12-19 18.00.00 NIGHT 2DEV 1.932E+04 2.144E+032001-12-19 19.00.00 NIGHT 2DEV 1.620E+04 1.798E+032001-12-19 20.00.00 NIGHT 2DEV 1.817E+04 2.017E+032001-12-19 21.00.00 NIGHT 2DEV 1.405E+04 1.559E+032001-12-19 22.00.00 NIGHT 2DEV 1.713E+04 1.901E+032001-12-19 23.00.00 NIGHT 2DEV 1.650E+04 1.832E+032001-12-20 00.00.00 NIGHT 2DEV 1.577E+04 1.750E+032001-12-20 01.00.00 NIGHT 2DEV 1.553E+04 1.723E+032001-12-20 02.00.00 NIGHT 2DEV 1.574E+04 1.747E+03

Figure 139. Example of MVS MIPS for System ID Hourly List

MVS reports


|

|

|

||

||

||

||

|||

||




Period The name of the period.

System ID The SMF system ID.

CPU busy sec CPU busy time, in seconds.

CPU busy MIPS MIPS for System ID.

MVS reports


|

||

||

||

||

||

||

MVS MIPS for System ID List, Daily TrendThis report shows the list and the daily trend of the MIPS for all the machines.


Report ID MVSM2


Source MVS_SYSTEM_D

Attributes MVS, MIPS, System, Daily, Trend.

Variables From_date, To_date, Period_name, MVS_system_ID

MVS Mips for System ID List - Daily TrendFrom date: All To date: All

System ID: AllCpu Cpu

System busy busyDate Period ID sec mips---------- -------- ------ ---------- ----------2001-12-19 NIGHT 2DEV 2.523E+05 2.800E+042001-12-20 NIGHT 2DEV 1.870E+05 2.076E+042001-12-20 PRIME 2DEV 2.512E+05 2.789E+04

Figure 140. Example of MVS MIPS for System ID List - Daily Trend

MVS reports


|

|

|

||

||

||

||

||

||


Date The date of the first day of the measurement.





MVS reports


|

||

||

||

||

||

MVS MIPS for System ID List, Monthly TrendThis report shows the list and the monthly trend of the MIPS for all the machines.


Report ID MVSM3


Source MVS_SYSTEM_M

Attributes MVS, MIPS, System, Monthly, Trend.

Variables From_date, To_date, Period_name, MVS_system_ID

MVS Mips for System ID List - Monthly TrendFrom date: All To date: All

System ID: AllCpu Cpu

System busy busyDate Period ID sec mips---------- -------- ------ ---------- ----------2001-12-01 NIGHT 2DEV 4.393E+05 4.876E+042001-12-01 PRIME 2DEV 2.512E+05 2.789E+04

Tivoli Decision Support: MVSM3

Figure 141. Example of MVS MIPS for System ID List - Monthly Trend

MVS reports


|

|

|

||

||

||

||

||

||







MVS reports


|

||

||

||

||

||

MVS CPU Load by LPAR, Monthly Trend per MIPSThis report shows the information about MIPS Monthly Trend for all the LPARexisting in an MVS System.


Report ID MVS118


Source MVS_LPAR_M


Variables From_month, To_month, MVS_System_ID(required), Period_Name, Processor_type

MVS CPU Load by LPAR, Monthly Trend per MIPSSystem: ’2DEV’ Period: AllProcessor type: All

<-------------------------- LPAR_name ---------------------------><- *PHYSCAL --> <- LIFEPROD --> <---- SY1 ----> <---- SY2 ----->

CPU CPU CPU CPUMonth busy busy busy busy

start date mips mips mips mips---------- ------------- ------------- ------------- -------------2001-12-01 0.00 38117715.84 32031776.46 2143448707.49

Tivoli Decision Support: MVS118

Figure 142. Example of MVS CPU Load by LPAR, Monthly Trend per MIPS

MVS reports


|

||

|

||

||

||

||

|||

||


Month start date The first day of the month.

LPAR name The name of the LPAR.

CPU busy MIPS CPU busy MIPS for LPAR.

MVS reports


|

||

||

||

MVS CPU Load by LPAR, Daily Trend per MIPSThis report shows the information about MIPS Daily Trend for all the LPARexisting in an MVS System.


Report ID MVS119


Source MVS_LPAR_D


Variables From_date, To_date, MVS_System_ID (required),Period_Name, Processor_type

MVS CPU Load by LPAR, Daily Trend per MIPSSystem: ’2DEV’ Period: All

Processor type: All

<-------------------------- LPAR_name ---------------------------><- *PHYSCAL --> <- LIFEPROD --> <---- SY1 ----> <---- SY2 ---->

CPU CPU CPU CPUbusy busy busy busy

Date mips mips mips mips---------- ------------- ------------- ------------- -------------2001-12-19 0.00 10073962.88 8599420.31 549420825.662001-12-20 0.00 28043752.96 23432356.14 1594027881.83

Tivoli Decision Support: MVS119

Figure 143. Example of MVS CPU Load by LPAR, Daily Trend per MIPS

MVS reports


|

||

|

||

||

||

||

|||

||


Date The date.

LPAR name The name of the LPAR.

CPU busy MIPS CPU busy MIPS for LPAR.

MVS reports


|

||

||

||

Storage reportsThe storage reports show central and expanded storage information for a selectedtime period. This information includes the total number of storage frames allocatedand the average number of frames by type during a peak hour.

MVS reports


MVS Available CS, in Megabytes, Daily Profile reportThis report shows average and minimum available central storage megabytes eachhour during an average day. The values are averaged over all days that youspecify.


Report ID MVS30


Source MVS_SYSTEM_H

Attributes MVS, Central, Storage, Available, Daily, Profile




CS MB avg The average number of megabytes available forcentral storage.

CS MB min The minimum number of megabytes available forcentral storage.

Figure 144. Example of an MVS Available CS, in Megabytes, Daily Profile report

MVS reports


MVS CS by Workload Type, Peak Hour, Daily Trend reportThis report shows the total number of central storage frames allocated to aworkload type during the peak hours. The peak hour is the hour during the periodwhen the maximum number of central storage frames is allocated.

Specify:v GOAL_MODE=YES for MVS release 5.1 (and later) running in goal modev GOAL_MODE=NO for MVS release 5.1 (and later) running in compatibility

modev GOAL_MODE=NO for MVS releases prior to 5.1

For more information on using this report, refer to the System Performance FeatureGuide.


Report ID MVS31


Source MVS_WORKLOAD_H and MVS_WORKLOAD2_H

Attributes MVS, Central, Storage, Utilization, Workload, Peak, Daily, Trend

Variables From_date, To_date, MVS_system_ID, Period_name, Goal_mode

Figure 145. Example of an MVS CS by Workload Type, Peak Hour, Daily Trend report

MVS reports





Workload type The workload types for which central storage datais reported.

Central storage The total number of megabytes of central storageallocated to the workload type. Calculated as:(CS_FRAME_SECONDS / MEASURED_SEC) /256.

MVS reports


MVS ES by Workload Type, Peak Hour, Daily Trend reportThis report shows the total number of expanded storage frames allocated to aworkload type during the peak hours. The peak hour is the hour during the periodwhen the maximum number of expanded storage frames is allocated.




Report ID MVS32



Attributes MVS, Expanded, Storage, Utilization, Workload, Peak, Daily, Trend





Figure 146. Example of an MVS ES by Workload Type, Peak Hour, Daily Trend report

MVS reports


Workload type The workload types for which expanded storagedata is reported.

Expanded storage The total number of megabytes of expandedstorage allocated for the workload type. Calculatedas: (ES_FRAME_SECONDS / MEASURED_SEC) /256.

MVS reports


MVS Storage by Workload Type, Peak Hour, Daily reportThis report shows the total number of central and expanded storage framesallocated to a workload type during the peak hours. The peak hour is the hourduring the period when the maximum number of central and expanded storageframes is allocated.




Report ID MVS33



Attributes MVS, Storage, Utilization, Workload, Peak, Daily, Trend





Figure 147. Example of an MVS Storage by Workload Type, Peak Hour, Daily report

MVS reports


Workload type The workload types for which processor storagedata is reported.

Processor storage The total number of megabytes of processorstorage (central and expanded) allocated for theworkload type. Calculated as:(TOT_FRAME_SECONDS / MEASURED_SEC) /256.

MVS reports


MVS CS by Workload Type, Monthly Trend reportThis report shows the total number of central storage frames allocated to aworkload type.




Report ID MVS34


Source MVS_WORKLOAD_M, MVS_WORKLOAD2_M

Attributes MVS, Central, Storage, Utilization, Workload, Monthly, Trend

Variables From_month, To_month, MVS_system_ID, Period_name,Goal_mode

Figure 148. Example of an MVS CS by Workload Type, Monthly Trend report

MVS reports




Workload type The workload types for which central storage datais reported.

Central storage The total number of megabytes of central storageallocated to the workload type. Calculated as:(CS_FRAME_SECONDS / MEASURED_SEC) /256.

MVS reports


MVS ES by Workload Type, Monthly Trend reportThis report shows the total number of expanded storage frames allocated to aworkload type.





Report ID MVS35



Attributes MVS, Expanded, Storage, Utilization, Workload, Monthly, Trend


MVS reports




Workload type The workload types for which expanded storagedata is reported.

Expanded storage The total number of megabytes of expandedstorage allocated for the workload type. Calculatedas: (ES_FRAME_SECONDS / MEASURED_SEC) /256.

MVS reports


MVS Storage by Workload Type, Monthly Trend reportThis report shows the total number of central and expanded storage framesallocated to a workload type.




Report ID MVS36



Attributes MVS, Storage, Utilization, Workload, Monthly, Trend


MVS reports




Workload type The workload types for which processor storagedata is reported.

Processor storage The total number of megabytes of processorstorage (central and expanded) allocated for theworkload type. Calculated as:(TOT_FRAME_SECONDS / MEASURED_SEC) /256.

MVS reports


MVS CS by Type, Peak Hour, Daily Trend reportThis report shows the average number of central storage frames by type (nucleus,CSA, SQA, LSQA, LPA, user, and available) during the peak hour. The peak houris the hour during the period when the maximum number of used frames isallocated.


Report ID MVS39


Source MVS_SYSTEM_H

Attributes MVS, Central, Storage, Utilization, LPA, SQA, CSA, Nucleus, User,Peak, Daily, Trend




Peak hour The hour during the period when the maximumnumber of frames is allocated.

Avail The average number of available megabytes incentral storage, during the peak hour.

User The average number of megabytes of centralstorage used for user pages, during the peak hour.

MVS reports


LPA The average number of megabytes of centralstorage used for the LPA, during the peak hour.

LSQA The average number of megabytes of centralstorage used for the LSQA, during the peak hour.

SQA The average number of megabytes of centralstorage used for the SQA, during the peak hour.

CSA The average number of megabytes of centralstorage used for the CSA, during the peak hour.

Nucleus The average number of megabytes of centralstorage used for the nucleus, during the peak hour.

MVS reports


MVS ES by Type, Peak Hour, Daily Trend reportThis report shows the average number of expanded storage frames by type (CSA,SQA, LSQA, LPA, user, and available) during the peak hour. The peak hour is thehour during the period when the maximum number of used frames is allocated.


Report ID MVS40


Source MVS_SYSTEM_H

Attributes MVS, Expanded, Storage, Utilization, LPA, SQA, CSA, User, Peak,Daily, Trend




Peak hour The hour during the period when the maximumnumber of frames is allocated.

MVS reports


Avail The average number of megabytes available inexpanded storage, during the peak hour.

User The average number of megabytes of expandedstorage used for user pages, during the peak hour.

LPA The average number of megabytes of expandedstorage used for LPA pages, during the peak hour.

LSQA The average number of megabytes of expandedstorage used for LSQA pages, during the peakhour.

SQA The average number of megabytes of expandedstorage used for SQA pages, during the peak hour.

CSA The average number of megabytes of expandedstorage used for CSA pages, during the peak hour.

MVS reports


MVS Central Storage by Type, Monthly Trend reportThis report shows the average number of central storage frames by type (nucleus,CSA, SQA, LSQA, LPA, user, and available).


Report ID MVS41


Source MVS_SYSTEM_M

Attributes MVS, Central, Storage, Utilization, LPA, SQA, CSA, Nucleus, User,Monthly, Trend




Avail The average number of megabytes available incentral storage.

MVS reports


User The average megabytes of central storage used foruser pages.

LPA The average megabytes of central storage used forLPA pages.

LSQA The average megabytes of central storage used forLSQA pages.

SQA The average megabytes of central storage used forSQA pages.

CSA The average megabytes of central storage used forCSA pages.

Nucleus The average megabytes of central storage used fornucleus pages.

MVS reports


MVS Expanded Storage by Type, Monthly Trend reportThis report shows the average number of expanded storage frames by type (CSA,SQA, LSQA, LPA, user, and available).


Report ID MVS42


Source MVS_SYSTEM_M

Attributes MVS, Expanded, Storage, Utilization, LPA, SQA, CSA, User,Monthly, Trend




CSA The average megabytes of expanded storage usedfor CSA pages.

MVS reports


SQA The average megabytes of expanded storage usedfor SQA pages.

LSQA The average megabytes of expanded storage usedfor LSQA pages.

LPA The average megabytes of expanded storage usedfor LPA pages.

User The average megabytes of expanded storage usedfor user pages.

Avail The average number of megabytes available inexpanded storage.

MVS reports


Paging reportsThe paging reports show different types of paging and paging activity for aselected time period.

MVS Paging by Subsystem, Daily Trend reportThis report shows an overall split of the total MVS paging activity by subsystem. Itcan be used to identify the subsystems with storage constraints.


Report ID MVS43



Attributes MVS, Paging, Swap, Ready, Resident, Wait, Subsystem, Daily,Trend




Subsystem The name of the subsystem.

Paging total (1000) The number of pages that were paged in from andpaged out to auxiliary storage, in thousands.Calculated as: (PAGEINS + PAGEOUTS) / 1000.

Pageins VIO (1000) The number of VIO page-ins, in thousands.

Pageouts VIO (1000) The number of VIO page-outs, in thousands.

Swap sequences (1000) The number of address space swap sequences, inthousands.

Outready (hours) The total time that address spaces were swapped

MVS Paging by Subsystem, Daily TrendSystem: ’MVS1’ Period: ’PRIME’

Paging Pagein Pageout Swap Residenttotal VIO VIO sequences Outready wait

Date Subsystem (1000) (1000) (1000) (1000) (hours) (hours)---------- --------- ------ ------ ------- --------- -------- --------2000-01-18 JES2 662 44 39 6 4.08 146.76

STC 263 0 0 49 19.35 65.85TSO 3831 0 0 640 28.01 186.17

------ ------ ------- --------- -------- --------* 4756 44 39 695 51.44 398.78

2000-01-19 JES2 598 40 35 5 3.62 132.34STC 239 0 0 44 17.12 59.21TSO 3456 0 0 580 25.23 168.58

------ ------ ------- --------- -------- --------* 4293 40 35 629 45.97 360.13

====== ====== ======= ========= ======== ========9049 84 74 1323 97.41 758.91


Figure 149. Example of MVS Paging by Subsystem, Daily Trend

MVS reports


out and ready to execute, in hours. Calculated as:(TRAN_ACTIVE_SEC − TRAN_RESIDENT_SEC) /3600.

Resident wait (hours) The total time that address spaces were residentbut not executing, in hours. Calculated as:(TRAN_RESIDENT_SEC − TCB_STEP_SECONDS −SRB_STEP_SECONDS) / 3600.

MVS reports


MVS Paging Rates, Daily Trend reportThis report shows different types of paging for a given number of days.


Report ID MVS44


Source MVS_SYSTEM_D

Attributes MVS, Paging, Swap, Migration, Daily, Trend




Pageins per second The number of non-VIO, non-swap, and hiperspacepage-ins per second. Calculated as: PAGEINS /MEASURED_SEC.

Pageouts per second The number of non-VIO, non-swap, and hiperspacepage-outs per second. Calculated as: PAGEOUTS /MEASURED_SEC.

Swap sequences/second The number of address swap sequences persecond. Calculated as: SWAP_SEQUENCES /MEASURED_SEC.

Pages read/second The number of pages read from expanded storageper second. Calculated as: PAGES_READ /MEASURED_SEC.

Pages moved/second The number of pages moved to expanded storageper second. Calculated as: PAGES_MOVED /MEASURED_SEC.

Pages migrated/second The number of pages migrated from expandedstorage to auxiliary storage per second. Calculatedas: PAGES_MIGRATED / MEASURED_SEC.

MVS Paging Rates, Daily TrendSystem: ’MVS1’ Period: ’PRIME’

Pageins Pageouts Swap Pages Pages Pagesper per sequences/ read/ moved/ migrated/

Date second second second second second second---------- ------- -------- ---------- -------- -------- ----------1999-11-02 0.01 0.00 0.27 42.77 51.10 0.001999-11-03 0.06 0.00 0.21 42.05 48.80 0.221999-11-04 0.06 0.00 0.24 44.33 52.38 0.321999-11-05 0.00 0.00 0.16 30.94 35.68 0.001999-11-06 0.22 0.04 0.30 58.42 67.86 0.57


Figure 150. Example of an MVS Paging Rates, Daily Trend report

MVS reports


Device reportsThe device reports show tape errors by device, user groups sorted by blockstransferred to and from disk devices, and tape demounts for a selected timeperiod.

MVS DASD I/O by User Group, Monthly Overview reportThis report gives a list of user groups sorted by number of blocks transferred toand from DASD. You can limit the number of elements in this chart using theRow_count variable.


Report ID MVS62


Source MVS_ADDRSPACE_M, MVS_SYSTEM_M

Attributes MVS, DASD, I/O, User_group, Monthly, Overview

Variables Month, MVS_system_ID, Period_name, Row_count



DASD blocks/second The number of blocks transferred to and fromDASD per second.

MVS DASD I/O by User Group, Monthly OverviewSystem: ’MVS1’ Month: ’2000-06-01’

Period: ’PRIME’

DASDUser blocks/group second-------- --------GROUP5 26.95GROUP3 23.69GROUP1 19.73GROUP2 16.74GROUP4 10.64


Figure 151. Example of an MVS DASD I/O by User Group, Monthly Overview report

MVS reports


MVS I/O Rates by User Group, Peak Hour, Daily reportThis report shows the I/O rate by user group during a peak hour for a given dayand period. Peak hour is the hour during the period when the number of blockstransferred are at a maximum. You can limit the number of elements in this chartusing the Row_count variable.


Report ID MVS63


Source MVS_ADDRDISTR_H, MVS_WORKLOAD_H

Attributes MVS, DASD, I/O, User_group, Peak, Daily, Overview



Hour The peak hour, which is the hour during theperiod when the number of blocks transferred is ata maximum.


Total blocks/second The total number of blocks transferred per second.

MVS I/O Rates by User Group, Peak Hour, DailySystem: ’MVS1’ Date: ’2000-06-03’

Period: ’PRIME’

TotalUser blocks/

Hour group second---- -------- --------10 GROUP5 94.30

GROUP3 51.83GROUP1 23.53GROUP2 5.78GROUP4 2.38


Figure 152. Example of an MVS I/O Rates by User Group, Peak Hour, Daily report

MVS reports


MVS Tape I/O by User Group, Monthly Overview reportThis report gives a list of user groups sorted by number of blocks transferred toand from tape devices. You can limit the number of elements in this chart usingthe Row_count variable.


Report ID MVS64


Source MVS_ADDRSPACE_M, MVS_SYSTEM_M

Attributes MVS, Tape, I/O, User_group, Monthly, Overview




Tape blocks/second The number of blocks transferred to and from tapedevices per second.

MVS Tape I/O by User Group, Monthly OverviewSystem: ’MVS1’ Month: ’2000-06-01’

Period: ’PRIME’

TapeUser blocks/group second-------- --------GROUP5 4.58GROUP3 2.24


Figure 153. Example of an MVS Tape I/O by User Group, Monthly Overview report

MVS reports


MVS Tape Demounts/MVS System, Monthly Overview reportThis report shows the number of tape demounts by month and MVS system.


Report ID MVS65


Source MVS_TAPE_M

Attributes MVS, Operations, Tape, Monthly, Overview

Variables From_month, To_month, Period_name



MVS System ID The MVS system ID.

Demounts The number of tape demounts.

MVS Tape Demounts/MVS System, Monthly OverviewPeriod: ’PRIME’

Month MVSstart date system ID Demounts---------- ---------- ----------1999-11-01 SYSB 140

----------* 140

==========Total 140


Figure 154. Example of an MVS Tape Demounts/MVS System, Monthly Overview report

MVS reports


MVS Tape Errors by Device, Monthly Overview reportThis report shows number of tape errors by month and device.


Report ID MVS66


Source MVS_TAPE_M

Attributes MVS, Operations, Problem, Tape, Monthly, Overview

Variables From_month, To_month, MVS_system_ID


MVS System ID The MVS system ID.

Device number The device number.

Temp read errors The number of temporary read errors.

Temp write errors The number of temporary write errors.

Perm read errors The number of permanent read errors.

Perm write errors The number of permanent write errors.

Cleaner actions The number of cleaner actions.

MVS Tape Errors by Device, Monthly OverviewMonth: ’1999-11-01’ to ’1999-11-01’

Temp Temp Perm PermMVS Device read write read write Cleaner

system ID number errors errors errors errors actions---------- ------ ------- ------- ------- ------- -------SYSB 0441 0 15 0 3 0

0448 1 36 1 4 10


Figure 155. Example of an MVS Tape Errors by Device, Monthly Overview report

MVS reports


MVS Tape Errors by Volume, Monthly Overview reportThis report shows the number of tape errors by month and volume. The volumeswith the most errors are shown first. You can limit the number of elements in thischart using the Row_count variable.


Report ID MVS67


Source MVS_TAPE_M

Attributes MVS, Operations, Problem, Tape, Monthly, Overview

Variables From_month, To_month, MVS_system_ID, Row_count


Volser The volume serial number.

Temp read errors The number of temporary read errors.

Temp write errors The number of temporary write errors.

Perm read errors The number of permanent read errors.

Perm write errors The number of permanent write errors.

MVS Tape Errors by Volume, Monthly OverviewSystem: ’SYSB’ Month: ’1999-11-01’ to ’1999-11-01’

Temp Temp Perm Permread write read write

Volser errors errors errors errors------ ------- ------- ------- -------846887 0 35 0 5JFA074 1 16 0 2846860 0 0 1 0


Figure 156. Example of an MVS Tape Errors by Volume, Monthly Overview report

MVS reports


MVS MAGSTAR VTS Configuration reportThis report shows the VTS configuration for a specific date, specified at report run.

The following information identifies the report:

Report ID MVS97


Source MVS_VTS_CONF

Attributes MVS, Virtual, Tape, Server, Configuration, Overview, VTS

Variables Date, MVS_SYSTEM_ID, TAPE_LIBRARY, LIB_SEQ_NUM,SYSTEM_NAME

The report contains the following information:

Hour Time when the activity occurred.

MVS_SYSTEM_ID This is the SMF system ID.

TAPE_LIBRARY System managed tape library sequence number.

LIBRARY_SEQU_NUMBER Library sequence number of the library segmentfor which the VTS statistics are being reported.

SYSTEM_NAME This is the MVS system name.

PHYSICAL_TAPE_DEVICE_INSTALLEDNumber of underlying physical tape devicescurrently installed in the VTS subsystem.

PHYSICAL_TAPE_DEVICE_AVAILABLENumber of underlying physical tape devicescurrently available for use by the VTS subsystem.

MVS MAGSTAR VTS Configuration Report

VIRTUAL VIRTUALPHYSICAL PHYSICAL VOLUMES

MVS LIBRA TAPE TAPE VIRTUAL INSYSTEM TAPE SEQU SYSTEM DEVICE DEVICE DEVICE TAPE

HOUR ID LIBRARY NUMBE NAME INSTALLED AVAILABLE CONFIGURED VOL CACHE-------- ------ ------------ ----- -------- ----------- ---------- ---------- ----------00.00.00 SYSB 000000060222 60222 MVSESA59 6 6 32 1.420E+02


Figure 157. Example of an MVS MAGSTAR VTS Configuration report

MVS reports


VIRTUAL_DEVICE_CONFIGUREDThe number of virtual devices configured in thisVTS at the time the request for statistics wasreceived (current).

VIRTUAL_VOLUMES_IN__TAPE_VOL_CACHEThe number of virtual volumes in Tape VolumeCache at the end of the reported hour.

MVS reports


MVS MAGSTAR VTS Physical Drive Mount Daily reportThis report shows the VTS physical drive mount daily statistics for a specific date,specified at report run.


Report ID MVS98


Source MVS_VTS_H

Attributes MVS, Virtual, Tape, Server, VTS, Physical, Drive, Mount, Daily,Overview



HOUR Time when the activity occurred.

MVS_SYSTEM_ID This is the SMF System ID.




PHY_TAPE_DEV_MAX_NUMBERMaximum number of underlying physical tapedevices mounted concurrently in this VTS duringthe reported hour.

PHY_TAPE_DEV_MIN_NUMBERMinimum number of underlying physical tapedevices mounted concurrently in this VTS duringthe reported hour.

MVS MAGSTAR VTS Physical Drive Mount Daily report

PHY PHYTAPE TAPE

MVS LIBRA DEV DEVSYSTEM TAPE SEQU SYSTEM MAX MIN

HOUR ID LIBRARY NUMBE NAME NUMBER NUMBER-------- ------ ------------ ----- -------- ------ ------00.00.00 SYSB 000000060222 60222 MVSESA59 6.000 6.000

PHY PHY PHYPHY MAX MIN AVG PHY PHY PHY

TAPE SEC SEC SEC MOUNT MOUNT MOUNTDEV FOR FOR FOR FOR STAGE FOR MIGRA FOR RECLAAVG MOUNT MOUNT MOUNT REQUEST REQUEST REQUEST

NUMBER REQUEST REQUEST REQUEST NUMBER NUMBER NUMBER--------- --------- --------- --------- --------- --------- ---------

6.000 2.900E+01 2.900E+01 2.900E+01 1.000 0.000 0.000


Figure 158. Example of an MVS MAGSTAR VTS Physical Drive Mount Daily report

MVS reports


PHY_TAPE_DEV_AVG_NUMBERAverage number of underlying physical tapedevices mounted concurrently in this VTS duringthe reported hour.

PHY_MAX_SEC_FOR_MOUNT_REQUESTMaximum time, in seconds, used by the library toperform a mount request for a physical drive in theVTS in the reported hour.

PHY_MIN_SEC_FOR_MOUNT_REQUESTMinimum time, in seconds, used by the library toperform a mount request for a physical drive in theVTS in the reported hour.

PHY_AVG_SEC_FOR_MOUNT_REQUESTAverage time, in seconds, used by the library toperform a mount request for a physical drive in theVTS in the reported hour.

PHY_MOUNT_FOR_STAGE_REQUEST_NUMBERThe number of physical mount requests completedin the reported hour to satisfy stage mounts.

PHY_MOUNT_FOR_MIGRA_REQUEST_NUMBERThe number of physical mount requests completedin the reported hour to satisfy migrate mounts.

PHY_MOUNT_FOR_RECLA_REQUEST_NUMBERThe number of physical mount requests completedin the reported hour to satisfy reclamation mounts.

MVS reports


MVS MAGSTAR VTS Virtual Drive Mount Daily reportThis report shows the VTS virtual drive mount daily statistics for a specific date,specified at report run.


Report ID MVS99


Source MVS_VTS_H

Attributes MVS, Virtual, Tape, Server, VTS, Drive, Mount, Daily, Overview








VIRT_DEV_MAX_NUMBER The maximum number of virtual drives that wereconcurrently mounted in this VTS during thereported hour.

MVS MAGSTAR VTS Virtual Drive Mount Daily report

VIRT VIRTMVS LIBRA DEV DEVSYSTEM TAPE SEQU SYSTEM MAX MIN

HOUR ID LIBRARY NUMBE NAME NUMBER NUMBER-------- ------ ------------ ----- -------- ---------- ----------00.00.00 SYSB 000000060222 60222 MVSESA59 1.300E+01 1.000E+01

VIRT VIRT VIRTVIRT DRIVE DRIVE DRIVE VIRT VIRTDEV MOUNTED MOUNTED MOUNTED MOUNT MOUNTAVG MAX MIN AVG MAX MIN

NUMBER SEC SEC SEC SEC SEC---------- ---------- ---------- ---------- ---------- ----------1.100E+01 4.263E+03 2.600E+01 6.310E+02 3.020E+02 1.000

VIRT VIRTMOUNT MOUNT

VIRT SPEC SPECVIRT MOUNT VOL LOG

MOUNT NUM IN TAPE IN TAPE VIRTAVG USING VOL VOL PREMIGRATIONSEC FRF CACHE CACHE NUMBER

---------- ---------- ---------- ---------- ------------2.100E+01 1.000E+01 7.000 2.000 1.10000E+01


Figure 159. Example of an MVS MAGSTAR VTS Virtual Drive Mount Daily report

MVS reports


VIRT_DEV_MIN_NUMBER The minimum number of virtual drives that wereconcurrently mounted in this VTS during thereported hour.

VIRT_DEV_AVG_NUMBER The average number of virtual drives that wereconcurrently mounted in this VTS during thereported hour.

VIRT_DRIVE_MOUNTED_MAX_SECMaximum time, in seconds, that a virtual drivewas mounted in this VTS during the reported hour.

VIRT_DRIVE_MOUNTED_MIN_SECMinimum time, in seconds, that a virtual drive wasmounted in this VTS during the reported hour.

VIRT_DRIVE_MOUNTED_AVG_SECAverage time, in seconds, that a virtual drive wasmounted in this VTS during the reported hour.

VIRT_MOUNT_MAX_SEC Maximum time, in seconds, used to complete amount request on a virtual drive in the reportedhour.

VIRT_MOUNT_MIN_SEC Minimum time, in seconds, used to complete amount request on a virtual drive in the reportedhour.

VIRT_MOUNT_AVG_SEC Average time, in seconds, used to complete amount request on a virtual drive in the reportedhour.

VIRT_MOUNT_NUM_USING_FRFThe number of virtual mounts in reported hourusing the VTS Fast-Ready facility.

VIRT_MOUNT_SPEC_VOL_IN TAPE_VOL_CACHEThe number of virtual mounts, in the reportedhour, that were completed for specific requestedvolume found resident in Tape Volume Cache(specific mount hits).

VIRT_MOUNT_SPEC_LOG_IN_TAPE_VOL_CACHEThe number of virtual mounts, in the reportedhour, that were completed for specific requestedlogical volume staged from a physical tape backinto Tape Vol Cache.

VIRT_PREMIGRATION_NUMBERThe number of virtual volumes for which apremigrate operation was completed in thereported hour.

MVS reports


MVS MAGSTAR VTS Utilization Daily reportThis report shows the number of tape errors by month and volume. The volumeswith the most errors are shown first.


Report ID MVS100


Source MVS_VTS_H

Attributes MVS, Virtual, Tape, Server, VTS, Utilization, Mount, Daily,Overview





TAPE_LIBRARY System managed tape library sequence number.LIBRARY_SEQU_NUMBER. Library sequencenumber of the library segment for which the VTSstatistics are being reported.


BYTES_WRITTEN_THROUGH_HOST_CHANNELThe total number of bytes written successfully

MVS MAGSTAR VTS Utilization Daily report

BYTES BYTESWRITTEN READ

MVS LIBRA THROUGH THROUGHSYSTEM TAPE SEQU SYSTEM HOST HOST

HOUR ID LIBRARY NUMBE NAME CHANNEL CHANNEL-------- ------ ------------ ----- -------- ---------- ----------00.00.00 SYSB 000000060222 60222 MVSESA59 1.142E+06 7.523E+05

NUMBERBYTES BYTES AVERAGE AVERAGE NUMBER OF

WRITTEN READ AGE SIZE OF LOGTO TO IN IN ACTIVE VOLUMES

ATTACHED ATTACHED TAPE TAPE DATA WITHPHYS PHYS VOLUME VOLUME BYTES ACTIVE

DRIVES DRIVES CACHE CACHE MANAGED DATA---------- ---------- ---------- ---------- ---------- ----------8.827E+05 2.659E+05 2.450E+02 4.350E+02 2.054E+06 4.727E+03

TOTALAMOUNT

OFSTORAGE

CAPACITY----------1.368E+07


Figure 160. Example of an MVS MAGSTAR VTS Utilization Daily report

MVS reports


through host channels to virtual volumes in anintegral multiple of 4096 bytes, during the reportedhour. If the number of bytes written is not aninteger multiple of 4096, the number is roundedup.

BYTES_READ_THROUGH_HOST_CHANNELThe total number of bytes read successfullythrough host channels to virtual volumes in anintegral multiple of 4096 bytes, during the reportedhour. If the number of bytes written is not aninteger multiple of 4096, the number is roundedup.

BYTES_WRITTEN_TO_ATTACHED_PHYS_DRIVESThe total number of bytes written successfully byVTS to its attached physical drives in an integralmultiple of 4096 bytes, during the reported hour. Ifthe number of bytes written is not an integermultiple of 4096, the number is rounded up.

BYTES_READ_TO_ATTACHED_PHYS_DRIVESThe total number of bytes read successfully by VTSto its attached physical drives in an integralmultiple of 4096 bytes, during the reported hour. Ifthe number of bytes written is not an integermultiple of 4096, the number is rounded up.

AVERAGE_AGE_IN_TAPE_VOLUME_CACHEThe average age in minutes of virtual volumes inTape Volume Cache at the end of the reportedhour.

AVERAGE_SIZE_IN_TAPE_VOLUME_CACHEThe average size of virtual volumes in TapeVolume Cache in an integral multiple of 1 048 576bytes (1MB) at the end of reported hour. Virtualvolumes smaller than 1MB are rounded up to 1MB.

NUMBER_OF_ACTIVE_DATA_BYTES_MANAGEDThe number of bytes of active data managed bythe VTS in an integral multiple of 1 045 576 bytes(1MB) as determined as of the previous midnight.

NUMBER_OF_LOG_VOLUMES_WITH_ACTIVE_DATAThe number of logical volumes managed by theVTS that contain active data as of the previousmidnight.

TOTAL_AMOUNT_OF_STORAGE_CAPACITYThe total estimated amount of storage capacityprovided by the empty 3590 cart managed by VTSin an integral multiple of 1 048 576 bytes (1 MB) asof the previous midnight.

MVS reports


Printer reportsThe printer reports show printer activity and printer forms usage for a selectedtime period.

MVS Printer Activity, Monthly Overview reportThis report shows printer activity by printer location, printer name, and formsnumber.


Report ID MVS68


Source MVS_PRINTER_M

Attributes MVS, Operations, Printer, Monthly, Overview

Variables From_month, To_month, Sysplex_name, MVS_system_ID, Periodname


Printer location The name of the location, where the printer islocated.

Printer name The name of the printer.

Form number The form number.

Data sets The number of printed data sets.


MVS Printer Activity, Monthly OverviewSysplex: ’SYSPLEX1’ System: ’MVS1’


Logical TotalPages Lines Elapsed pages bytes

Printer Printer Form Data printed printed writer printed sentlocation name number sets (1000) (1000) (hours) (1000) (KB)------------ -------- -------- -------- -------- -------- ------- -------- -----FS1FAR3A FS1FAR3A STANDARD 82 1 25 4.65

STD 27 0 4 0.753820 268 4 147 18.92

-------- -------- -------- --------* 377 4 175 24.31

-------- -------- -------- --------** 377 4 175 24.31

FS1FAR3B FS1FAR3B STANDARD 204 1 41 14.69STD 17 0 1 0.543820 252 1 43 10.22

-------- -------- -------- --------* 473 2 84 25.45

-------- -------- -------- --------** 473 2 84 25.45

======== ======== ======== ========35361 295 13606 1330.92


Figure 161. Example of an MVS Printer Activity, Monthly Overview report

MVS reports



Elapsed writer (hours) The writer elapsed time, in hours. This value is notuseful for buffered printers.

Logical pages printed (1000) The number of logical pages printed, in thousands.The logical page is an area defined by the pagedefinition for line data or by structured fields forMO:DCA data. This information is provided byPrint Services Facility Version 3 Release 1.0.

Total bytes sent (KB) The total bytes sent during the file transfer of thedata sets to the target system, in kilobytes.Introduced with a Type 6 enhancement, it is validfor Print Services Facility and PrintWay. ForPrintWay it is the number of bytes transmitted orattempted to transmit.

MVS reports


MVS Print Activity by User Group, Monthly Overview reportThis report shows printer activity by user group and printer name.


Report ID MVS69



Attributes MVS, Operations, User_group, Printer, Monthly, Overview

Variables From_month, To_month, Sysplex_name, MVS_system_ID,Period_name



Printer name The name of the printer.

Data sets The number of printed data sets.



Elapsed writer (hours) The writer elapsed time, in hours. This value is notuseful for buffered printers.

MVS Print Activity by User Group, Monthly OverviewSysplex: ’SYSPLEX1’ System: ’MVS1’


Logical TotalPages Lines Elapsed pages bytes

User Printer Data printed printed writer printed sentgroup name sets (1000) (1000) (hours) (1000) (KB)-------- -------- -------- -------- -------- -------- -------- -----GROUP4 FS1FAR3A 6 0 7 0.66

FS1FAR3B 1 0 1 0.36FS1FOR3E 12 0 1 0.37

-------- -------- -------- --------* 19 0 10 1.38

GROUP5 FS1FAR3A 371 4 168 23.65FS1FAR3B 472 2 83 25.09

-------P8415PR1 325 0 742 11.08

-------- -------- -------- --------* 35342 295 13596 1329.53

======== ======== ======== ========Total 35361 295 13606 1330.92


Figure 162. Example of an MVS Print Activity by User Group, Monthly Overview report

MVS reports



Total bytes sent (KB) The total bytes sent during the file transfer of thedata sets to the target system, in kilobytes.Introduced with a Type 6 enhancement, it is validfor Print Services Facility and PrintWay. ForPrintWay it is the number of bytes transmitted orattempted to transmit.

MVS reports


MVS Printer Forms Usage, Monthly Overview reportThis report shows printer forms usage. The report shows the least-used forms first.


Report ID MVS70



Attributes MVS, Operations, User_group, Forms, Monthly, Overview



Form number The form number.




MVS Printer Forms Usage, Monthly OverviewSysplex: ’SYSPLEX1’ System: ’MVS1’Month: ’1999-11-01’ to ’1999-11-01’

LogicalPages Lines pages

Form printed printed printednumber (1000) (1000) (1000)-------- -------- -------- --------7806 2 80STD 3 157STANDARD 25 14313820 72 4436

======== ========Total 102 6104


Figure 163. Example of an MVS Printer Forms Usage, Monthly Overview report

MVS reports


OAM reportsThe OAM reports provide information about OAM activities.

OSREQ Function Invocation Statistics, Detail reportThis report shows statistics for OAM/OSREQ activities.


Report ID MVS107


Source MVS_OAM_OSREQ_T

Attributes MVS, OAM, OSREQ, Function

Variables DATE, MVS_SYSTEM_ID


TIME The time when the record was written. From TME.

DATE The date when the record was written. From DTE.

MVS_SYSTEM_ID The MVS system ID of the subsystem on which therecords were collected.

OSREQ_FUNCTION The OSREQ function that was invoked.

FUNCTION_ELAPSED_TIMEThe elapsed time of the function in seconds.

TRANSACTION_NAME The name of the transaction that invoked theOSREQ macro.

COLLECTION_NAME The collection name.

OBJECT_NAME The object name.

STORAGE_GROUP_NAME The storage group name.

STORAGE_CLASS_NAME The storage class name.

MANAGEMENT_CLASS_NAMEThe management class name.

VOL_SER The volume serial number.

Figure 164. Example of an OSREQ Function Invocation Statistics, Detail report

MVS reports


OAM/OSMC Activities Statistics, Daily reportThis report shows statistics for OAM/OSMC storage management activities.


Report ID MVS108


Source MVS_OAM_OSMC_D

Attributes MVS, OAM, OSMC, DASD, Storage, Group

Variables From_date, To_date, MVS_SYSTEM_ID, Storage_group

MVS reports



DATE The date when the record was written.

DASD_PRIM_OBJ_WRITTENThe number of primary objects written to DASD.

DASD_PRIM_OBJ_WRITTEN_(KB)The number of kilobytes of primary object datawritten to DASD.

DASD_PRIM_OBJ_READ The number of primary objects read from DASD.

Figure 165. Example of an OAM/OSMC Activities Statistics, Daily report

MVS reports


DASD_PRIM_OBJ_READ_(KB)The number of kilobytes of primary object dataread from DASD.

DASD_PRIM_OBJ_DELETEDThe number of primary objects deleted fromDASD.

DASD_PRIM_OBJ_DELETED_(KB)The number of kilobytes of primary object datadeleted from DASD.

OPTICAL_PRIM_OBJ_WRITTENThe number of primary objects written to optical.

OPTICAL_PRIM_OBJ_WRITTEN_KBThe number of kilobytes of primary object datawritten to optical.

OPTICAL_PRIM_OBJ_READ The number of primary objects read from optical.

OPTICAL_PRIM_OBJ_READ_(KB)The number of kilobytes of primary object dataread from optical.

OPTICAL_PRIM_OBJ_DELETEDThe number of primary objects deleted fromoptical.

OPTICAL_PRIM_OBJ_DELETED_(KB)The number of kilobytes of primary object datadeleted from optical.

TAPE_PRIM_OBJ_WRITTEN The number of primary objects written to tape.

TAPE_PRIM_OBJ_WRITTEN_(KB)The number of kilobytes of primary object datawritten to tape.

TAPE_PRIM_OBJ_READ The number of primary objects read from tape.

TAPE_PRIM_OBJ_READ_KB The number of kilobytes of primary object dataread from tape.

TAPE_PRIM_OBJ_DELETED The number of primary objects deleted from tape.

TAPE_PRIM_OBJ_DELETED_KBThe number of kilobytes of primary object datadeleted from tape.

OPTICAL_BACKUP_OBJ_WRITTENThe number of backup objects written to optical.

OPTICAL_BACKUP_OBJ_WRITTEN_(KB)The number of kilobytes of backup object datawritten to optical.

OPTICAL_BACKUP_OBJ_READThe number of backup objects read from optical.

OPTICAL_BACKUP_OBJ_READ_(KB)The number of kilobytes of backup object data readfrom optical.

MVS reports


OPTICAL_BACKUP_OBJ_DELETEDThe number of backup objects deleted from optical.

OPTICAL_BACKUP_OBJ_DELETED_(KB)The number of kilobytes of backup object datadeleted from optical.

TAPE_BACKUP_OBJ_WRITTENThe number of backup objects written to tape.

TAPE_BACKUP_OBJ_WRITTEN_(KB)The number of kilobytes of backup object datawritten to tape.

TAPE_BACKUP_OBJ_READ The number of backup objects read from tape.

TAPE_BACKUP_OBJ_READ_(KB)The number of kilobytes of backup object data readfrom tape.

TAPE_BACKUP_OBJ_DELETEDThe number of backup objects deleted from tape.

TAPE_BACKUP_OBJ_DELETED_KBThe number of kilobytes of backup object datadeleted from tape.

MVS reports


OAM/OSMC Activities Statistics, Monthly reportThis report shows statistics for OAM/OSMC storage management activities.


Report ID MVS109


Source MVS_OAM_OSMC_D

Attributes MVS, OAM, OSMC, DASD, Storage, Group


MVS reports




DASD_PRIM_OBJ_WRITTENThe number of primary objects written to DASD.

DASD_PRIM_OBJ_WRITTEN_(KB)The number of kilobytes of primary object datawritten to DASD.

DASD_PRIM_OBJ_READ The number of primary objects read from DASD.

Figure 166. Example of an OAM/OSMC Activities Statistics, Monthly report

MVS reports


DASD_PRIM_OBJ_READ_(KB)The number of kilobytes of primary object dataread from DASD.

DASD_PRIM_OBJ_DELETEDThe number of primary objects deleted fromDASD.

DASD_PRIM_OBJ_DELETED_(KB)The number of kilobytes of primary object datadeleted from DASD.

OPTICAL_PRIM_OBJ_WRITTENThe number of primary objects written to optical.

OPTICAL_PRIM_OBJ_WRITTEN_KBThe number of kilobytes of primary object datawritten to optical.

OPTICAL_PRIM_OBJ_READ The number of primary objects read from optical.

OPTICAL_PRIM_OBJ_READ_(KB)The number of kilobytes of primary object dataread from optical.

OPTICAL_PRIM_OBJ_DELETEDThe number of primary objects deleted fromoptical.

OPTICAL_PRIM_OBJ_DELETED_(KB)The number of kilobytes of primary object datadeleted from optical.

TAPE_PRIM_OBJ_WRITTEN The number of primary objects written to tape.

TAPE_PRIM_OBJ_WRITTEN_(KB)The number of kilobytes of primary object datawritten to tape.

TAPE_PRIM_OBJ_READ The number of primary objects read from tape.

TAPE_PRIM_OBJ_READ_KB The number of kilobytes of primary object dataread from tape.

TAPE_PRIM_OBJ_DELETED The number of primary objects deleted from tape.

TAPE_PRIM_OBJ_DELETED_KBThe number of kilobytes of primary object datadeleted from tape.

OPTICAL_BACKUP_OBJ_WRITTENThe number of backup objects written to optical.

OPTICAL_BACKUP_OBJ_WRITTEN_(KB)The number of kilobytes of backup object datawritten to optical.

OPTICAL_BACKUP_OBJ_READThe number of backup objects read from optical.

OPTICAL_BACKUP_OBJ_READ_(KB)The number of kilobytes of backup object data readfrom optical.

MVS reports


OPTICAL_BACKUP_OBJ_DELETEDThe number of backup objects deleted from optical.

OPTICAL_BACKUP_OBJ_DELETED_(KB)The number of kilobytes of backup object datadeleted from optical.

TAPE_BACKUP_OBJ_WRITTENThe number of backup objects written to tape.

TAPE_BACKUP_OBJ_WRITTEN_(KB)The number of kilobytes of backup object datawritten to tape.

TAPE_BACKUP_OBJ_READ The number of backup objects read from tape.

TAPE_BACKUP_OBJ_READ_(KB)The number of kilobytes of backup object data readfrom tape.

TAPE_BACKUP_OBJ_DELETEDThe number of backup objects deleted from tape.

TAPE_BACKUP_OBJ_DELETED_KBThe number of kilobytes of backup object datadeleted from tape.

MVS reports


LCS Opt Disk Volume R/W/D Statistics, Detail reportThis report shows statistics for LCS optical volume activities (calculated atdemount time).


Report ID MVS110


Source MVS_OAM_CARTR_T

Attributes MVS, OAM, LCS, Optical, Cartridge

Variables Date, MVS_SYSTEM_ID, Storage_group, Vol_ser


TIME The time when the record was written.


OPT_LIB_NAME The optical library name.

OPT_LIB_DEV_NUM The MVS device number that corresponds to theoptical library.


VOL_SER_OPP_SIDE The volume serial number of the opposite side ofthe optical disk.


OPT_LIB_DEV_TYPE The optical library device type.

OPT_DRV_DEV_TYPE The optical drive device type.

OPT_DRV_NAME The optical drive name.

OPT_DRV_DEV_NUM The MVS device number that corresponds to theoptical drive.

Figure 167. Example of a LCS Opt Disk Volume R/W/D Statistics, Detail report

MVS reports


FUNCT_ELAPSED_TIME The elapsed time of the function in seconds.

TIME_MOUNTED The elapsed time in milliseconds that the opticaldisk volume was mounted.

NUM_OBJ_WRITTEN The number of objects written to this optical diskvolume while it was mounted.

OBJ_WRITTEN_(KB) The number of kilobytes of object data written tothis optical disk volume while it was mounted.

NUM_OBJ_READ The number of objects read from this optical diskvolume while it was mounted.

OBJ_READ_(KB) The number of kilobytes of object data read fromthis optical disk volume while it was mounted.

NUM_OBJ_DELETED The number of objects deleted from this opticaldisk volume while it was mounted.

OBJ_DELETED_(KB) The number of kilobytes of object data deletedfrom this optical disk volume while it wasmounted.

MVS reports


LCS Opt Disk Volume R/W/D Statistics, Daily reportThis report shows statistics for LCS optical volume activities (calculated atdemount time).


Report ID MVS111


Source MVS_OAM_CARTR_T

Attributes MVS, OAM, LCS, Optical, Cartridge

Variables From_date, To_date, MVS_SYSTEM_ID, Storage_group, Vol_ser



OPT_LIB_NAME The optical library name.

OPT_LIB_DEV_NUM The MVS device number that corresponds to theoptical library.


VOL_SER_OPP_SIDE The volume serial number of the opposite side ofthe optical disk.


TIME_MOUNTED The elapsed time in milliseconds that the opticaldisk volume was mounted.

NUM_OBJ_WRITTEN The number of objects written to this optical diskvolume while it was mounted.

OBJ_WRITTEN_(KB) The number of kilobytes of object data written tothis optical disk volume while it was mounted.

NUM_OBJ_READ The number of objects read from this optical diskvolume while it was mounted.

OBJ_READ_(KB) The number of kilobytes of object data read fromthis optical disk volume while it was mounted.

NUM_OBJ_DELETED The number of objects deleted from this opticaldisk volume while it was mounted.

Figure 168. Example of an LCS Opt Disk Volume R/W/D Statistics, Daily report

MVS reports


OBJ_DELETED_(KB) The number of kilobytes of object data deletedfrom this optical disk volume while it wasmounted.

MVS reports


LCS Optical R/W/Log D/Phys D Reqs, Daily reportThis report shows statistics for LCS Optical Write, Read, Logical Delete, andPhysical Delete activities.


Report ID MVS112


Source MVS_OAM_RWD_D

Attributes MVS, OAM, LCS, Optical, Requests




OPTICAL_LIBRARY_NAME The optical library name.

OPTICAL_LIBRARY_DEV_NUMThe MVS device number that corresponds to theoptical library.


REQUEST The LCS optical request.

OBJECTS_IN_CURRENT_REQUEST_(NUMBER)Total number of objects in this request.

OBJECTS_IN_CURRENT_REQUEST_(KB)Total number of kilobytes of object data in thisrequest.

OBJECTS_IN_REQ_SUCC_PROCESSED_(NUMBER)Total number of objects in this request thatprocessed successfully.

OBJECTS_IN_REQ_SUCC_PROCESSED_(KB)Total number of kilobytes of object data in thisrequest that processed successfully.

Figure 169. Example of an LCS Optical R/W/Log D/Phys D Reqs, Daily report

MVS reports


LCS Optical R/W/Log D/Phys D Reqs, Monthly reportThis report shows statistics for LCS Optical Write, Read, Logical Delete, andPhysical Delete activities.


Report ID MVS113


Source MVS_OAM_RWD_M

Attributes MVS, OAM, LCS, Optical, Requests




OPTICAL_LIBRARY_NAME The optical library name.

OPTICAL_LIBRARY_DEV_NUMThe MVS device number that corresponds to theoptical library.


REQUEST The LCS optical request.





Figure 170. Example of an LCS Optical R/W/Log D/Phys D Reqs, Monthly report

MVS reports


LCS Tape R/W/Log D Requests, Daily reportThis report shows statistics for LCS Object Tape Write, Read, and Logical Deleteactivities.


Report ID MVS114


Source MVS_OAM_TAPERWD_D

Attributes MVS, OAM, LCS, Tape, Requests




TAPE_DRIVE_NAME The tape drive unit name.

TAPE_DEVICE_NUM The MVS device number of the tape drive.

STORAGE_GROUP_NAME The name of the Object or Object Backup storagegroup to which the tape volume belongs.

REQUEST The LCS tape request.






Figure 171. Example of an LCS Tape R/W/Log D Requests, Daily report

MVS reports


LCS Tape R/W/Log D Requests, Monthly reportThis report shows statistics for LCS Object Tape Write, Read, and Logical Deleteactivities.


Report ID MVS115


Source MVS_OAM_TAPERWD_M

Attributes MVS, OAM, LCS, Tape, Requests




TAPE_DRIVE_NAME The tape drive unit name.


STORAGE_GROUP_NAME The name of the Object or Object Backup storagegroup to which the tape volume belongs.

REQUEST The LCS tape request.






Figure 172. Example of an LCS Tape R/W/Log D Requests, Monthly report

MVS reports


OAM Tape Vol R/W Stats at Demount, Daily reportThis report shows statistics for LCS object tape volume at demount time.


Report ID MVS116


Source MVS_OAM_TAPDMNT_D

Attributes MVS, OAM, Tape, Volume, Demount





TAPE_VOLUME_UNIT_NAMEThe unit name associated with the tape volumeand used to allocate the tape drive.


TAPE_VOLUME_TYPE The tape volume type.

OBJECT_STORAGE_GROUP_NAMEThe name of the Object or Object Backup storagegroup.


TIME_MOUNTED The elapsed time, in milliseconds, that the tapevolume was mounted.

TAPE_VOLUME_OBJECTS_WRITTEN_(NUMBER)Number of objects written to this tape volumewhile it was mounted.

TAPE_VOLUME_OBJECTS_WRITTEN_(KB)Number of logical kilobytes of object data writtento this tape volume while it was mounted.

TAPE_VOLUME_OBJECTS_READ_(NUMBER)Number of objects read from this tape volumewhile it was mounted.

Figure 173. Example of an OAM Tape Vol R/W Stats at Demount, Daily report

MVS reports


TAPE_VOLUME_OBJECTS_READ_(KB)Number of logical kilobytes of object data readfrom this tape volume while it was mounted.

MVS reports


OAM Tape Vol R/W Stats at Demount, Monthly reportThis report shows statistics for LCS object tape volume at demount time.


Report ID MVS117


Source MVS_OAM_TAPDMNT_M

Attributes MVS, OAM, Tape, Volume, Demount





TAPE_VOLUME_UNIT_NAMEThe unit name associated with the tape volumeand used to allocate the tape drive.


TAPE_VOLUME_TYPE The tape volume type.

OBJECT_STORAGE_GROUP_NAMEThe name of the Object or Object Backup storagegroup.


TIME_MOUNTED The elapsed time, in milliseconds, that the tapevolume was mounted.

TAPE_VOLUME_OBJECTS_WRITTEN_(NUMBER)Number of objects written to this tape volumewhile it was mounted.

TAPE_VOLUME_OBJECTS_WRITTEN_(KB)Number of logical kilobytes of object data writtento this tape volume while it was mounted.

TAPE_VOLUME_OBJECTS_READ_(NUMBER)Number of objects read from this tape volumewhile it was mounted.

Figure 174. Example of an OAM Tape Vol R/W Stats at Demount, Monthly report

MVS reports


TAPE_VOLUME_OBJECTS_READ_(KB)Number of logical kilobytes of object data readfrom this tape volume while it was mounted.

MVS reports


OpenEdition reportsThe OpenEdition reports provide information about CPU usage, I/O activity, filesystem lookups, and child processes.

MVS OpenEdition CPU Usage by Group, Daily reportThis report shows a list of jobs using OpenEdition system calls and related CPUusage.


Report ID MVS102


Source MVS_OMVSADDR_T

Attributes MVS, Job, OMVS, OpenEdition, Daily, Detail



Mvs system ID The MVS system ID.

User group The RACF user group.

Racf user ID The RACF user ID.



Jobname The jobname.

Syscall CPU total (/sec) Total CPU time spent for OpenEdition system calls,in seconds.

MVS OpenEdition CPU Usage by Group, DailySysplex: All System: All

Date: All to All

Mvs Syscallsystem User Racf CPU totalID group user ID Date Time Jobname (/sec)---------- -------- -------- ---------- -------- ---------- ---------ES88 RACFID2 RACFID2 1999-09-08 09.25.24 ETCINIT9 0.032

1999-09-08 09.29.08 INETD3 0.017

ROOT ROOT 1999-09-08 09.29.17 ROOT5 0.8321999-09-08 09.29.17 ROOT6 0.7471999-09-08 09.29.17 ROOT7 0.0321999-09-08 09.29.21 ROOT8 0.9371999-09-08 09.29.43 ROOT9 0.0031999-09-08 09.29.49 ROOT1 0.027


Figure 175. Example of an MVS OpenEdition CPU Usage by Group, Daily report

MVS reports


MVS OpenEdition I/O Activity by Group, Daily reportThis report shows a list of jobs using OpenEdition and related I/O activity.


Report ID MVS103



Attributes MVS, Job, OMVS, OpenEdition, Daily, Detail








Stdfile read blocks Number of reads from the OpenMVS HFS regularfile.

Stdfile write blocks Number of writes to the OpenMVS HFS regularfile.

Pipe read blocks Number of reads from the OpenMVS HFS pipe file.

MVS OpenEdition I/O Activity by Group, DailySysplex: All System: ES38

Date: 1999-09-08 to 1999-09-09

StdfileUser Racf readgroup user ID Date Time Jobname blocks-------- -------- ---------- -------- -------- ----------NOBODY NOBODY 1999-09-08 09.29.56 NOBODY 5514

1999-09-08 09.30.01 NOBODY 9354

RACFID2 RACFID2 1999-09-08 09.25.24 ETCINIT9 721999-09-08 09.29.08 INETD3 72

Special Special Network NetworkStdfile Pipe Pipe file file socket socketwrite read write read write read write

blocks blocks blocks blocks blocks blocks blocks-------- ---------- ---------- ---------- ---------- ---------- ---------

0 24 12 0 0 0 00 72 36 0 0 0 0

0 0 12 0 0 132 60 0 12 0 0 114 6


Figure 176. Example of an MVS OpenEdition I/O Activity by Group, Daily report

MVS reports


Pipe write blocks Number of writes to the OpenMVS HFS pipe file.

Special file read blocks Number of reads from the OpenMVS HFS specialfile.

Special file write blocks Number of writes to the OpenMVS HFS specialfile.

Network socket read blocks Number of reads for network socket.

Network socket write blocks Number of writes for the network socket.

MVS reports


MVS OpenEdition File System Lookups by Group, Daily reportThis report provides information about OpenEdition file system lookups.


Report ID MVS104



Attributes MVS, Job, OMVS, OpenEdition, Daily, Detail, Lookups



Mvs system ID The MVS system ID.






Pathname lookups LFS The number of pathname lookup calls to thelogical file system.

MVS OpenEdition File System Lookups by Group, DailySysplex: All System: ES80

Date: ’1999-09-08’ to ’1999-09-09’

Mvs Racfsystem User userID group ID Date Time Jobname------ -------- -------- ---------- -------- --------ES80 NOBODY NOBODY 1999-09-08 09.29.56 NOBODY

1999-09-08 09.33.26 NOBODY21999-09-08 09.34.42 NOBODY2

ROOT ROOT 1999-09-08 09.29.17 ROOT51999-09-08 09.29.43 ROOT91999-09-08 09.29.49 ROOT11999-09-08 09.29.56 ROOT2

Pathname Pathname Pathname Pathnamelookups lookups generation generation

LFS PFS LFS PFS--------- ---------- ---------- ----------

138 768 0 018 108 6 3018 108 6 30

42 84 0 0102 438 6 12114 552 6 1272 306 18 36


Figure 177. Example of an MVS OpenEdition File System Lookups by Group, Daily report

MVS reports


Pathname lookups PFS The number of pathname lookup calls to thephysical file system.

Pathname generation LFS The number of pathname generation calls to thelogical file system.

Pathname generation PFS The number of pathname generation calls to thephysical file system.

MVS reports


MVS OpenEdition Child Process Listing for Job reportThis report lists address space and all related processes, directly created by inputjob, due a fork () or a spawn () OpenEdition function.


Report ID MVS106


Source MVS_OMVSADIS_T

Attributes MVS, Fork, Spawn, Process, OpenEdition, OpenMVS

Variables Job_name, From_date, To_date, From_time, To_time, Sysplex_name,MVS_system_ID


Job name The child jobname.

User ID The child RACF user ID.

User group The child RACF user group.

Process ID The child process ID.

Process group ID The child process group ID.

Process user ID The child process user ID.

Process user group ID The child process user group ID.

MVS OpenEdition Child Process Listing for JobSysplex: All System: ES80

Date: ’1999-01-01’ to ’2000-03-10’Time: ’09:00:00’ to ’12:00:00’

Job name: ’ROOT4’

User User Process Process ProcessJob name ID group ID group ID user ID-------- -------- -------- ----------- ----------- -----------ROOT1 ROOT ROOT 268435478 33554457 0ROOT2 ROOT ROOT 30 33554457 0ROOT3 ROOT ROOT 16777246 33554457 0ROOT4 ROOT ROOT 33 33554457 0ROOT5 ROOT ROOT 184549398 33554457 0ROOT6 ROOT ROOT 201326614 33554457 0ROOT7 ROOT ROOT 218103830 33554457 0ROOT8 ROOT ROOT 234881046 33554457 0ROOT9 ROOT ROOT 251658262 33554457 0

Processuser Process Parent

group ID session ID ID----------- ----------- -----------

0 33554457 335544570 33554457 335544570 33554457 335544570 33554457 335544570 33554457 335544570 33554457 335544570 33554457 335544570 33554457 335544570 33554457 33554457


Figure 178. Example of an MVS OpenEdition Child Process Listing for Job report

MVS reports


Process session ID The child process session ID.

Parent ID The parent process ID.

MVS reports


MVS reports


Part 7. MVS Availability Component

561


Before you can use the MVS availability component to collect data and createuseful reports, you must customize and test the installation. This chapter describesthe steps you must perform to customize the MVS availability component:1. Make input data available.2. Review the DRLJCOLL job.3. Update lookup tables.

Make input data availableFirst, ensure that the appropriate SMF record types are not suppressed by SMF orany of its exits. See Chapter 26, “Log and record definitions”, on page 569 for acomplete list of the SMF records used by this component.

Then specify interval recording for tracking availability for one or more resources(address spaces). If these address spaces are started tasks, you need intervalrecording for only started tasks (STC).

You must associate subsystem names with performance group numbers in theIEAICSxx member. You can use the subsystem name to select batch, TSO, orstarted tasks.


Update lookup tablesThe MVS availability component uses several lookup tables when storing data inthe Tivoli Decision Support for OS/390 database. You must update the lookuptables to include parameters specific to your installation.



AVAILABILITY_PARM Specifies schedulenames andavailability objectivesto use for thedifferent resources inthe system

SYSTEM_ID AREARESOURCE_TYPERESOURCE_NAMERESOURCE_GROUP

AVAIL_OBJ_PCTSCHEDULE_NAME

MVS_AVAIL_RESOURCE Specifies the addressspaces (jobs, startedtasks, or TSOsessions) to trackavailability for, andassociates theseaddress spaces witha resource name anda resource type.

MVS_SYSTEM_IDSUBSYSTEM_IDJOB_NAME

RESOURCE_NAMERESOURCE_TYPE

563

|

|

|||

|

|

|

||

|||

|||

|||

||

|||

||

|||

|

|||||

|||||||

||||

||

||||||||||

|||

||




DESCRIPTIONSYPLEX_NAME

For information on using the administration dialog to update the lookup tables, see“Updating lookup tables” on page 11.

Update AVAILABILITY_PARM tableThis lookup table sets availability parameters. It contains the schedule names andavailability objectives to use for the different resources in the system.

You can either use the sample value in the AVAILABILITY_PARM lookup table,which connects all resources to a standard schedule, or update the lookup table toestablish your own schedule for different resources.

When updating the lookup table, you must consider what values the MVScomponent stores in the AVAILABILTY_T table.

SYSTEM_ID will contain one of these:v The MVS system ID from SMF30SID, when tracking resources specified in

MVS_AVAIL_RESOURCEv The MVS system ID from SMF70SID, when tracking one MVS systemv The text string SYSPLEX, when tracking a complete sysplex

AREA will always contain the text string MVS.

RESOURCE_TYPE will contain either:v The value specified in MVS_AVAIL_RESOURCE, when tracking resources

specified in MVS_AVAIL_RESOURCE, orv The text string MVS, when tracking one MVS system, or a complete sysplex

RESOURCE_NAME will contain either:v The value specified in MVS_AVAIL_RESOURCE, when tracking resources

specified in MVS_AVAIL_RESOURCE, orv The text string SYSTEM, when tracking one MVS system, or a complete sysplex

RESOURCE_GROUP will contain one of these:v SYSPLEX_NAME from the MVS_SYSPLEX lookup table, or if no match is found,

blanks when tracking resources specified in MVS_AVAIL_RESOURCEv The sysplex name from SMF70XNM, or blanks when running an MVS version

earlier than 5.1, when tracking one MVS system or a complete sysplex.

These values will be matched with the values you specify in theAVAILABILITY_PARM lookup table, when deciding what schedule name to use,and the availability objective.

For a description of the lookup table and an example of its contents, refer to TivoliDecision Support for OS/390: Administration Guide.


||||

||||||

||||

|

||

||

||

|||

||

|

||

|

|

|

|

||

|

|

||

|

|

||

||

|||

||

Update MVS_AVAIL_RESOURCE tableThis table is used to specify the resources for which availability should be tracked.A resource is an address space, and SMF type 30 (subtypes 2 and 3) records areused to track the availability of that address space. In the lookup table, specify thesubsystem ID of the address space (for example, STC, JESx, TSO, APPC), thatwould be STC in most cases, and the name of the address space. TheAVAILABILITY_T table is updated if column SUBSYSTEM_ID inMVS_AVAIL_RESOURCE matches field SMF30WID in SMF type 30 (subtypes1,2,3,5) records and column JOB_NAME in AVAIL_RESOURCE matches fieldSMF30JBN in SMF type 30 (subtypes 1,2,3,5) records. RESOURCE_TYPE andRESOURCE_NAME found in MVS_AVAIL_RESOURCE is used whenAVAILABILITY_T table is updated. See “MVS_AVAIL_RESOURCE” on page 571for a description of the lookup table.

This is an example of the MVS_AVAIL_RESOURCE table:MVS SUBSYSTEM JOB RESOURCE RESOURCE

SYSTEM ID NAME TYPE NAMEID% STC TCAS ST_TASK TSO% STC JES2 ST_TASK JES2

If you use this example, you will track availability for two started tasks: TCAS andJES2. In the AVAILABILITY_x tables, RESOURCE_TYPE will be ST_TASK for bothTCAS and JES2. RESOURCE_NAME will be TSO for the started task TCAS andJES2 for the started task JES2.

Update MVS_SYSPLEX tableThe MVS_SYSPLEX lookup table converts MVS_SYSTEM_ID and/orSYSTEM_NAME to SYSPLEX_NAME. You need this table because some SMFrecords do not contain the name of the sysplex. MVS_SYSTEM_ID andSYSTEM_NAME can contain global search characters.

For a complete description of the lookup table and an example of its contents, see“MVS_SYSPLEX” on page 401.


||

||||||||||||

|

|||||

||||

||

||||

||

Chapter 25. Data Flow

The MVS availability component collects records from the SMF data set, and storesthe data in the Tivoli Decision Support for OS/390 database. You can then use thereporting dialog to create reports based on this data.

Figure 179 shows an overview of the flow of data through the MVS availabilitycomponent.

Lookup TablesWhen collecting SMF records, the MVS availability component uses updatedefinitions to determine which records and fields in the records to use whenupdating the tables. As it updates the tables, the MVS availability component useslookup tables to add information that makes the subsequent reports more useful.Figure 180 on page 568 shows which data tables contain information from lookuptables.

MVS

SMF log

SMF_030SMF_070

Recorddefinitions


AVAILABILITY_PARMMVS_AVAIL_RESOURCEMVS_SYSPLEX

Reports


Collect

AVAILABILITY_X

Data Tables

Figure 179. MVS availability component data flow

567

|

|

|||

||||

||

|||||||

For detailed information about the data tables updated by the component, and thelookup table the component uses, see Chapter 27, “Data tables and lookup tables”,on page 571.


AVAILABILITY_PARM

AVAILABILITY_TMVS_SYSPLEX

MVS_SYSTEM_ID

SYSPLEX_NAME

AVAILABILITY_D,_W,_M

RESOURCE_NAMERESOURCE_TYPE

MVS_AVAIL_RESOURCE AVAILABILITY_T

MVS_SYSTEM_IDSUBSYSTEM_IDJOB_NAME

SYSTEM_IDAREARESOURCE_TYPERESOUCE_NAMERESOURCE_GROUP

SCHEDULE_HOURSUP_IN_SCHEDULESTARTS_IN_SCHEDULESTOPS_IN_SCHEDULEAVAIL_OBJ_PCT



|

|||||||


The MVS availability component collects records from the system managementfacilities (SMF) log. In particular, the collected records are those related to theaddress space work and the CPU activity of the MVS operating system.

SMF recordtype Subtype

Tivoli DecisionSupport for OS/390record definition Description

30 SMF_030 Common address space work-This record contains operationinformation such as the job and step start and end times, stepCPU time, step termination status.

70 SMF_070 RMF CPU activity-MVS writes this record for eachmeasurement interval and when the session terminates. Therecord includes general information on CPU use during theinterval (for example, wait time) and address space use.

Refer to MVS/ESA System Management Facilities for a detailed description of theSMF records.

569


This chapter describes the lookup tables used by the MVS availability component.For descriptions of common data tables, lookup tables, and control tables used bythe System Performance feature, refer to Tivoli Decision Support for OS/390:Administration Guide.

Lookup tablesThis section describes the lookup tables specific to the MVS availabilitycomponent.

MVS_AVAIL_RESOURCEThis lookup table defines which resources the jobs, started tasks, or TSO sessionsshould be associated with. These definitions are used for tracking resourceavailability.


MVS_SYSTEM_ID k CHAR(4) MVS system ID the resource is associated with. This cancontain global search characters.

SUBSYSTEM_ID k CHAR(4) Subsystem ID the resource is associated with. This cancontain global search characters.

JOB_NAME k CHAR(8) Name of the job, started task, or TSO session to beassociated with the resource. This can contain global searchcharacters.

RESOURCE_NAME CHAR(8) Name of the resource the job, started task, or TSO sessionwill be associated with.

RESOURCE_TYPE CHAR(8) Name of the resource type the job, started task, or TSOsession will be associated with.


MVSSYSTEM SUBSYSTEM JOB RESOURCE RESOURCEID ID NAME TYPE NAME------ --------- -------- -------- --------% % % OTHER OTHERMVS1 STC TSO SUBSYS TSOMVS1 STC OMVS SUBSYS OMVSMVS1 STC JES2 SUBSYS JES2MVS1 STC VTAM% SUBSYS VTAMMVS1 TSO % SUBSYS TSOMVS1 OMVS % SUBSYS OMVSMVS1 JES2 % SUBSYS JES2MVS1 VTAM % SUBSYS VTAM

571

|

|

||||

||

||

|

|||

|||||

|||||

|||||

||||||

|||||

||||||

|||||||||||||||

|

MVS_SYSPLEXThis lookup table associates MVS system IDs and system names with a sysplexname and a description.



SYSTEM_NAME k CHAR(8) MVS system name. This can contain global search characters.

DESCRIPTION VARCHAR(32) Description to be associated with the MVS system ID or theMVS system name.

SYSPLEX_NAME CHAR(8) The sysplex name to be associated with the MVS system ID orthe MVS system name.


MVSSYSTEM SYSTEM SYSPLEXID NAME NAME DESCRIPTION------ -------- -------- --------------------------------C00 C00 SYSPLEX0 MVS C00C01 C01 SYSPLEX0 MVS C01C02 C02 SYSPLEX0 MVS C02C03 C03 SYSPLEX0 MVS C03C% C% SYSPLEX8 MVS C80 to C88


|

||

|||||

||||

||||

|||||

||||||

|||||||||||

|

Chapter 28. Reports

The MVS availability component provides these three reports:v MVS Availability not within Target, Daily Trend reportv MVS Availability, Daily/Monthly Trend reportv MVS Availability for a Sysplex, Daily/Monthly Trend report

MVS availability report descriptionsThis section describes the reports provided with the MVS availability component.

MVS Availability not within Target, Daily Trend reportThis report shows resources which are available for less than the given objective inthe schedule. Resources are the MVS system measured by SMF type 70 record andstarted tasks or jobs measured by SMF type 30 (subtypes 2 and 3) records.


Report ID MVS74

Report group MVSAVL reports

Source AVAILABILITY_D

Attributes MVS, Exception, Availability



Date The date of the measurement



Resource Type The name of the resource type.

Up in schedule (hour) The time the resource was up within the schedule,in hours.

Up in schedule (%) The time the resource was up within the schedule,as a percent age of scheduled time.

Objective The target for the resource to be up within theschedule, as a percent age of the scheduled time.

MVS Availability not within Target, Daily TrendDate: ’1999-11-15’ to ’1999-11-30’

MVS Up in Up inSysplex system Resource Resource schedule schedule Objective

Date name ID Type Name (hour) (%) (%)--------- --------- ------- -------- --------- --------- --------- ---------1999-11-20 SYSPLEX1 SYSB MVS SYSTEM 8.49 94.3 95.81999-11-20 SYSPLEX1 SYSB ST_TASK TSO 8.45 94.8 95.8


Figure 181. Example of an MVS Availability not within Target, Daily Trend report

573

|

|

|

|

|

|

||

|

|

|||

|

||

||

||

||

||

|

|

||

||

||

||

|||

|||

|||

MVS Availability, Daily/Monthly Trend reportThese reports show daily availability for one or more resources. For resource type,you can specify one of the resource types defined in the MVS_AVAIL_RESOURCElookup table or ″MVS,″ which gives availability of MVS as measured by SMF type70 records. If you do not specify a resource type, the reports will contain all theresource names.




Source AVAILABILITY_D (daily), AVAILABILITY_M (monthly)

Attributes MVS, Availability, Daily, Monthly, Trend

Variables From_date and To_date (daily), From_month and To_month(monthly), MVS_system_ID, Resource_type



Resource name The name of the resource or resources for whichavailability is shown.

Availability percent The availability within schedule, as a percentage,for the resources shown.

Resource Type The name of the resource type.

Figure 182. Example of an MVS Availability, Daily Trend report


|

|||

|

|||||

|

||

||

||

||

|||

|

|

|||

|||

|||

||

Up in schedule (hour) The time the resource was up within the schedule,in hours.

Up in schedule (%) The time the resource was up within the schedule,as a percentage of the scheduled time.

Objective The target for the resource to be up within theschedule, as a percentage of the scheduled time.

MVS Availability for a Sysplex, Daily/Monthly Trend reportThis report shows availability for one sysplex and all MVS systems in that sysplex.




Source MVS_AVAILABILITY_D (daily), MVS_AVAILABILITY_M(monthly)

Attributes MVS, Availability, Daily, Monthly, Trend

Variables From_date (daily), To_date (daily), From_month (monthly),To_month (monthly), Sysplex_name



Figure 183. Example of an MVS Availability for a Sysplex, Daily Trend report


|

|||

|||

|||

|||

|

|

|

||

||

|||

||

|||

|

|

|||

MVS system ID The name of the MVS system ID or ’SYSPLEX’(meaning all MVS systems combined).

Availability Availability within schedule, as a percentage.


|||

||

Part 8. MVS performance management component

Chapter 29. Customization . . . . . . . . 581Make input data available . . . . . . . . . 581

Performance group numbers or service classes 581Interval recording . . . . . . . . . . . 582Cache RMF Reporter record number . . . . 584

Review the DRLJCOLL job . . . . . . . . . 584Update lookup tables. . . . . . . . . . . 584

Update MVSPM_DEVICE_ADDR table . . . . 585Update MVSPM_TIME_RES table . . . . . 586Update MVSPM_UNIT_TYPE table . . . . . 587Update MVS_MIPS_T table. . . . . . . . 587Update MVS_SYSPLEX table . . . . . . . 587Update MVS_WORKLOAD_TYPE table . . . 587Update MVS_WORKLOAD2_TYPE table . . . 587Update control tables . . . . . . . . . . 587


Chapter 31. Log and record definitions . . . . 595Record procedures. . . . . . . . . . . . 599

Chapter 32. Data tables, views, and lookuptables . . . . . . . . . . . . . . . 601Data tables . . . . . . . . . . . . . . 601

MVSPM_APPC_H . . . . . . . . . . . 601MVSPM_APPL_H . . . . . . . . . . . 604MVSPM_BMF_H . . . . . . . . . . . 609MVSPM_CACHE_H . . . . . . . . . . 610MVSPM_CF_PROC_H . . . . . . . . . 614MVSPM_CF_REQUEST_H . . . . . . . . 616MVSPM_CF_LINK_H . . . . . . . . . 619MVSPM_CF_TO_CF_H . . . . . . . . . 620MVSPM_CHANNEL_H . . . . . . . . . 621MVSPM_CLUSTER_H . . . . . . . . . 624MVSPM_CPU_H . . . . . . . . . . . 626MVSPM_CRYPTO_PCI_H . . . . . . . . 628MVSPM_CRYPTO_CCF_H . . . . . . . . 630MVSPM_DATASET_H . . . . . . . . . 632MVSPM_DEVICE_AP_H . . . . . . . . 634MVSPM_DEVICE_H . . . . . . . . . . 635MVSPM_ENQUEUE_H . . . . . . . . . 638MVSPM_FICON_H . . . . . . . . . . 639MVSPM_GOAL_ACT_H . . . . . . . . 640MVSPM_HS_CHAN_H . . . . . . . . . 642MVSPM_LPAR_H . . . . . . . . . . . 644MVSPM_OMVS_BUF_H. . . . . . . . . 647MVSPM_OMVS_FILE_H . . . . . . . . 648MVSPM_OMVS_GHFS_H . . . . . . . . 650MVSPM_OMVS_HFS_H. . . . . . . . . 651MVSPM_OMVS_KERN_H . . . . . . . . 653MVSPM_OMVS_MOUNT_H . . . . . . . 658MVSPM_PAGE_DS_H . . . . . . . . . 660MVSPM_PAGING_H . . . . . . . . . . 662MVSPM_RAID_RANK_H . . . . . . . . 669

MVSPM_STORAGE_H . . . . . . . . . 671MVSPM_STORCLASS_H . . . . . . . . 673MVSPM_SWAP_H. . . . . . . . . . . 674MVSPM_SYSTEM_H . . . . . . . . . . 676MVSPM_VLF_H . . . . . . . . . . . 679MVSPM_VOLUME_H . . . . . . . . . 680MVSPM_VS_CSASQA_H . . . . . . . . 683MVSPM_VS_PRIVATE_H . . . . . . . . 700MVSPM_VS_SUBPOOL_H . . . . . . . . 704MVSPM_WLM_SERVED_H . . . . . . . 705MVSPM_WLM_STATE_H . . . . . . . . 706MVSPM_WORKLOAD_H . . . . . . . . 708MVSPM_WORKLOAD2_H . . . . . . . . 711MVSPM_XCF_MEMBER_H. . . . . . . . 717MVSPM_XCF_PATH_H . . . . . . . . . 718MVSPM_XCF_SYS_H. . . . . . . . . . 720

Views . . . . . . . . . . . . . . . . 722MVSPM_APPL_HV . . . . . . . . . . 722MVSPM_CACHE_HV . . . . . . . . . 727MVSPM_CF_PROC_HV . . . . . . . . . 734MVSPM_CF_REQ_HV . . . . . . . . . 735MVSPM_CF_TO_CF_HV . . . . . . . . 737MVSPM_CLUSTER_HV . . . . . . . . . 738MVSPM_CPU_HV. . . . . . . . . . . 739MVSPM_CRYPTO_PC_HV . . . . . . . . 740MVSPM_CRYPTO_CC_HV . . . . . . . . 742MVSPM_DATASET_HV . . . . . . . . . 744MVSPM_DEVICE_AP_HV . . . . . . . . 746MVSPM_DEVICE_AP_PV . . . . . . . . 747MVSPM_DEVICE_HV . . . . . . . . . 748MVSPM_ENQUEUE_HV . . . . . . . . 751MVSPM_LPAR_HV . . . . . . . . . . 752MVSPM_PAGE_DS_HV . . . . . . . . . 754MVSPM_PAGING_HV . . . . . . . . . 756MVSPM_RAID_RANK_HV. . . . . . . . 760MVSPM_STORAGE_HV. . . . . . . . . 762MVSPM_STORCLASS_HV . . . . . . . . 764MVSPM_SWAP_HV . . . . . . . . . . 766MVSPM_SYSTEM_HV . . . . . . . . . 770MVSPM_SYSTEM_PV . . . . . . . . . 772MVSPM_WORKLOAD_HV . . . . . . . 773MVSPM_WORKLOAD2_HV . . . . . . . 776MVSPM_WORKLOADX_HV . . . . . . . 779MVSPM_XCF_PATH_HV . . . . . . . . 783MVSPM_XCF_SYS_HV . . . . . . . . . 784

Lookup tables . . . . . . . . . . . . . 786MVSPM_DEVICE_ADDR . . . . . . . . . 786

Example of table contents . . . . . . . . 786MVSPM_TIME_RES . . . . . . . . . . . 787

Example of table contents . . . . . . . . 787MVSPM_UNIT_TYPE . . . . . . . . . . 788

Example of table contents . . . . . . . . 788

Chapter 33. Reports . . . . . . . . . . 789Daily performance overview reports. . . . . . 791

MVSPM Workload Descriptions report . . . . 791

577

||

||||

||

||||

||

||

||||

||||

MVSPM Goal mode Workload Descriptionsreport . . . . . . . . . . . . . . . 792MVSPM CPU and Processor Storage ActivityOverview report . . . . . . . . . . . 793MVSPM Workload Resource UtilizationOverview report . . . . . . . . . . . 795MVSPM Workload Response Time ComponentsOverview report . . . . . . . . . . . 797MVSPM Response Time Goals vs Actuals,Overview report . . . . . . . . . . . 799MVSPM Execution Velocity Goals & Actuals,Overview report . . . . . . . . . . . 800MVSPM DASD Activity Overview report . . . 801

Processor and storage resources reports . . . . 803MVSPM Average CPU Busy, Daily/HourlyTrend report . . . . . . . . . . . . . 803MVSPM Average CPU Busy Profile, HourlyTrend report . . . . . . . . . . . . . 805MVSPM CPU Busy and Other Indicators,Hourly Trend report . . . . . . . . . . 806MVSPM System Central Storage Map, HourlyTrend report . . . . . . . . . . . . . 808MVSPM System Expanded Storage Map, HourlyTrend report . . . . . . . . . . . . . 810MVSPM Minimum Available Exp Storage,Hourly Trend report . . . . . . . . . . 812MVSPM Average High UIC Profile, HourlyTrend report . . . . . . . . . . . . . 813MVSPM Page Data Set Response Time, HourlyTrend report . . . . . . . . . . . . . 814MVSPM Page Data Set Device Resp Time,Hourly Trend report . . . . . . . . . . 815MVSPM Page Data Set Busy Time, HourlyTrend report . . . . . . . . . . . . . 816MVSPM System Storage Paging Rates, HourlyTrend report . . . . . . . . . . . . . 817MVSPM CPU Busy Profile Shared LPARs,Hourly Trend report . . . . . . . . . . 818MVSPM CPU Busy by Shared LPARs, HourlyTrend report . . . . . . . . . . . . . 819MVSPM Percent of Share Used by LPARs,Hourly Trend report . . . . . . . . . . 820MVSPM LPAR Management Time, HourlyTrend report . . . . . . . . . . . . . 821MVSPM Avg CF Busy Profile, Hourly Trendreport . . . . . . . . . . . . . . . 822MVSPM Avg CF Storage Usage, Hourly Trendreport . . . . . . . . . . . . . . . 823MVSPM CF, Processor and Storage, Overviewreport . . . . . . . . . . . . . . . 824MVSPM CF, Request Rate, Overview report . . 826MVSPM CF, System Details, Overview report 827MVSPM CF, Structures Details, Overview report 829MVSPM MIPS for Machine Model List report 830MVSPM MIPS for specific System ID report . . 832MVSPM MIPS for System ID Hourly List report 832MVSPM Total CPU MIPS per LPAR and Systemreport . . . . . . . . . . . . . . . 834

Application use of resources reports . . . . . . 835MVSPM System Resources by Workload Typereport . . . . . . . . . . . . . . . 835

MVSPM CPU Busy by Workload Types, HourlyTrend report . . . . . . . . . . . . . 837MVSPM CPU Busy by Workload PGNs, HourlyTrend report . . . . . . . . . . . . . 838MVSPM Storage Used by Workload Type,Hourly Trend report . . . . . . . . . . 839MVSPM Storage Used by Workload PGNs,Hourly Trend report . . . . . . . . . . 840MVSPM I/O Rate by Workload Types, HourlyTrend report . . . . . . . . . . . . . 841MVSPM CPU per I/O by Workload Type,Hourly Trend report . . . . . . . . . . 842MVSPM CPU per I/O by Workload PGNs,Hourly Trend report . . . . . . . . . . 843MVSPM Page-ins by Workload Types, HourlyTrend report . . . . . . . . . . . . . 844MVSPM Paging Activity by Workload, HourlyTrend report . . . . . . . . . . . . . 845MVSPM Resp Time by Workload Types, HourlyTrend report . . . . . . . . . . . . . 847MVSPM Workload Resp Time Components,Hourly Trend report . . . . . . . . . . 848MVSPM BMF Member Page Reads/Hits,Hourly Trend report . . . . . . . . . . 850MVSPM BMF Directory Page Reads/Hits,Hourly Trend report . . . . . . . . . . 851MVSPM APPC, CPU and I/O by TransactionClass report . . . . . . . . . . . . . 852MVSPM APPC, Execution and Queueing,Hourly Trend report . . . . . . . . . . 853MVSPM VLF Usage and Hit Ratio,Hourly/Daily Trend report . . . . . . . . 854MVSPM VLF Dataspace Usage, Hourly/DailyTrend report . . . . . . . . . . . . . 856MVSPM Applications Waiting on ENQs, HourlyTrend report . . . . . . . . . . . . . 858MVSPM Applications Waiting on ENQs, WorstCase report . . . . . . . . . . . . . 859MVSPM Response Time Goals & Actuals,Hourly Trend report . . . . . . . . . . 860MVSPM Exec. Velocity Goals & Actuals, HourlyTrend report . . . . . . . . . . . . . 861MVSPM Response Time Distribution report . . 862MVSPM Served Service Classes, Overviewreport . . . . . . . . . . . . . . . 863MVSPM Response Time Breakdown, Overviewreport . . . . . . . . . . . . . . . 864MVSPM Response Time Breakdown, HourlyTrend report . . . . . . . . . . . . . 866

I/O subsystem performance reports . . . . . . 868MVSPM Channel Path Busy report . . . . . 868MVSPM I/O Rate for LCUs, Hourly Trendreport . . . . . . . . . . . . . . . 870MVSPM I/O Response Time for LCUs, HourlyTrend report . . . . . . . . . . . . . 871MVSPM I/O Response Time Components forLCUs report . . . . . . . . . . . . . 872MVSPM No of Users Waiting for Device, DailyTrend report . . . . . . . . . . . . . 874MVSPM I/O Response Time Components,DASD Devices report. . . . . . . . . . 875


|||||||||

MVSPM I/O Rate for Devices by WorkloadType report . . . . . . . . . . . . . 877MVSPM I/O Response Time for Device, HourlyTrend report . . . . . . . . . . . . . 879MVSPM Cache Hit Rates by CU, Hourly Trendreport . . . . . . . . . . . . . . . 881MVSPM DFW Hit Rates by CU, Hourly Trendreport . . . . . . . . . . . . . . . 883MVSPM Staging Rates by CU, Hourly Trendreport . . . . . . . . . . . . . . . 885MVSPM Overall Effectiveness by CU, DailyOverview report . . . . . . . . . . . 887MVSPM Highest Hit Rate Volumes, DailyOverview report . . . . . . . . . . . 889MVSPM Highest Staging Rate Volumes, DailyOverview report . . . . . . . . . . . 891MVSPM Cache CU Operations by CU, DailyOverview report . . . . . . . . . . . 893MVSPM Cache CU Operations, Hourly Trendreport . . . . . . . . . . . . . . . 895MVSPM I/O Response Time for Devices byWorkload report . . . . . . . . . . . 897MVSPM I/O Rate by Workload on SelectedDevices report . . . . . . . . . . . . 899MVSPM XCF Statistics by System, Overviewreport . . . . . . . . . . . . . . . 900MVSPM XCF Signal Rates, Hourly Trend report 902MVSPM XCF Activity by Path and System,Overview report . . . . . . . . . . . 903MVSPM Data Set Activity, Overview report . . 905MVSPM Data Set I/O Rate & Resp Time,Hourly Trend report . . . . . . . . . . 907MVSPM Data Set I/O Rate Profile, HourlyTrend report . . . . . . . . . . . . . 909MVSPM Data Set Resp Time Profile, HourlyTrend report . . . . . . . . . . . . . 910MVSPM Storage Class Resp Time, Hourly Trendreport . . . . . . . . . . . . . . . 911MVSPM Storage Class I/O Rate, Hourly Trendreport . . . . . . . . . . . . . . . 912MVSPM Volume Activity by Storage Class,Overview report . . . . . . . . . . . 913MVSPM Channel Path Busy, Extended Modereport . . . . . . . . . . . . . . . 915

OpenEdition performance reports . . . . . . 917MVSPM OpenEdition HFS Global Statisticsreport . . . . . . . . . . . . . . . 917MVSPM OpenEdition HFS Buffer Statisticsreport . . . . . . . . . . . . . . . 919MVSPM OpenEdition HFS Statistics report . . 921MVSPM OpenEdition File Statistics report. . . 923MVSPM OpenEdition Kernel System CallsActivity report . . . . . . . . . . . . 925MVSPM OpenEdition Kernel Process Activityreport . . . . . . . . . . . . . . . 926MVSPM OpenEdition Kernel ProcessCommunication report . . . . . . . . . 928MVSPM OpenEdition Kernel Memory Statisticsreport . . . . . . . . . . . . . . . 930

Part 8. MVS performance management component 579


Before you can use the MVS performance management component to collect dataand create reports, you must customize and test the installation. This chapterdescribes the steps you must perform to customize the MVS performancemanagement component:1. Make input data available.2. Review the DRLJCOLL job.3. Update lookup tables.

Make input data availableEnsure that SMF records are written and can be processed by Tivoli DecisionSupport for OS/390 for performance management purposes. The performancemanagement tables provided are based on the assumption that these SMF recordsare written to the SMF data set:v 30 (subtypes 2 and 3)v 33 (subtype 1)v 41 (subtype 3)v 42 (subtypes 1, 2, 3, 4, 5, and 6)v 70 (subtypes 1 and 2)v 71v 72 (subtypes 1, 2, 3, and 4)v 73v 74 (subtypes 1, 2, 3, 4, 5, 6, and 7)v 75v 77v 78 (subtypes 1, 2, and 3)v 79v 92 (subtypes 1, 2, 4, 5, 6, 10, and 11)v Cache RMF Reporter record (usually SMF 245)

The usefulness of performance reports depends on how well your data isorganized. MVS provides ways to group data according to shifts, workload types,users, or departments. To improve the quality of your reporting:v Define shifts—hours in the dayv Define workloads—groups of performance groups

High-quality data is required for high-quality analysis, so consider implementingperformance group numbers (PGNs) and interval recording at your installation toimprove the quality of measurements in the performance management tables.

Performance group numbers or service classesYou can use performance group numbers (PGNs) to determine which applicationsuse what data processing resources. SMF type 30, type 72, and type 42 (subtype 6)records contain performance group numbers.

The amount of detail that PGNs give you depends on your installation’s IPS. Forexample, if all batch work is put into a single performance group, you will not beable to determine the individual resource use of financial, personnel, engineering,or development batch. The same applies to TSO, system functions (such as JES,

581

|

VTAM, RMF), and online systems. Because Tivoli Decision Support for OS/390allows summaries of detailed resource use, you can specify much more detail inthe IPS without having to deal with large RMF listings. Exploit this capability in away that serves you best.

Adding performance groups does not affect users. The new performance groupscan use the same domains, objectives, and priorities as they did before. You shouldtry to get reports that give you information about each user group.

The installation control specification (ICS) allows an installation to assign a PGNbased on job name, program name, or TSO transaction, rather than using thedefault values. In addition, data can be reported many times and in many ways.TSO response time could be reported by business unit, then reported again bycommand name. As in the case of the IPS, you can use this feature without havingto handle large RMF reports.

You can do one or more of these to improve the accessibility of your data:v Identify those PGNs containing workloads that are more diverse than you

would like.v Generate new PGNs to give you a greater level of detail. Use the same domains

and objectives that were used in the original performance group.v Associate users with the new PGNs through:

– IEAICS changes (preferably)– Changes to TSO UADS (if possible)– JCL changes (if all else fails)

v Change the lookup tables to reflect the new IPS/ICS.

The syntax for constructing the IPS is discussed in the Initialization and TuningGuide for your system.

If you have MVS 5.1 or later, consider running MVS in goal mode and definingservice classes (SCs) instead of PGNs.

PGNs and SCs can be mapped into workload types using lookup tables (see“MVS_WORKLOAD_TYPE” on page 402 and “MVS_WORKLOAD2_TYPE” onpage 403). This means that compatible workload reports can be produced evenafter switching to goal mode operation. Also, several new reports by service classmake it possible to compare the actual achieved performance with the specifiedgoal.

For more information about service classes, refer to the MVS/ESA Planning:Workload Management.

Interval recordingThere is tremendous value in using SMF type 30 records with interval recordingfor performance analysis. You can identify the users of data processing resources(processors, storage, and I/O devices). You can also collect data without intervalrecording. However, the results can be misleading when analyzing long-runningwork, such as CICS, IMS, and DB2. A measurement indicating that somewhere in a16-hour period CICS suffered 14 967 page faults is rather inconclusive. It is mucheasier to understand information based on more frequent intervals.

By defining a time resolution for each row of data stored in a set of tables, you canspecify that data be summarized by time intervals shorter than 1 hour. When

MVS performance management customization


choosing the time interval, you should consider factors such as the job and stepstart and end times, the step CPU time, and so on. For more information on settingtime intervals, see “Update MVSPM_TIME_RES table” on page 586.

The selected time resolution for a table should not be less than the interval atwhich the SMF records are written. For example, if the RMF interval (used for SMFtype 70 through 79 records) is 15 minutes, the time resolution for the MVSperformance management tables based on these SMF records must be a multiple of15 minutes (15, 30, 45, 60, and so on).

SMF interval records used by MVS performance management tables are 41, 42, 30(subtypes 2 and 3), and 70 through 79. The RMF Cache reporter SMF record usesthe same interval as RMF. The SMF type 41 record is written at a fixed interval of15 minutes. The interval for the SMF type 42 record is specified in the IGDSMSxxparmlib member. The SMF type 30 record interval is defined by the SMFPRMxxmember through the INTERVAL option of the SYS or SUBSYS keywords.

From MVS/ESA 4.3 it is also possible to request that the SMF type 30 recordintervals be synchronized with the RMF intervals. The quality of the reports willbe improved if this function is used. The RMF interval is defined in theERBRMFxx member in SYS1.PARMLIB.

Use the same time resolution for all MVS performance management tables.Otherwise, it will be difficult to create views or reports that correlate data fromdifferent MVS performance management tables.

The default time resolution is 60 minutes. If you increase the time to 120 minutes,the size of MVS performance management tables will be decreased to a half, butyou will not be able to analyze your system performance in as great a detail asyou would be able to if you selected a shorter time resolution. It is also possible tohave a short time resolution for prime shifts and a longer time resolution for othershifts when the system performance is not so critical.

By default, Tivoli Decision Support for OS/390 summarizes data by hour. Thisinterval is suitable for performance management. Setting the proper interval forSMF type 30 records requires a trade-off between accuracy and system overhead.The accuracy can be summarized quite simply:v With a 60-minute interval, the information in a type 30 record can be up to 30

minutes out of date. There is a 50% chance that it will be reported in the wronghour. With a 30-minute interval, the data can be 15 minutes off, and there is a25% chance that the data will be recorded in the wrong hour.

v There is little overhead in writing additional records unless there are manylong-running users in the system. Overhead concerns are warranted only onTSO systems. Even on TSO, if there is a 15-minute interval for 150 users, theoverhead of writing 600 additional SMF records per hour is not excessive.

To record interval data:1. Allow recording of SMF records supported by the Tivoli Decision Support for

OS/390 performance management tables. These are record types 30 (subtypes 2and 3), 70 to 75, 77, and the record number you specified for the cache RMFreporter.

2. Allow the recording of SMF type 30 records by interval.3. Evaluate the usefulness of the recorded data.4. Make permanent changes based on your evaluation.



The records to be written and the interval to be used for recording SMF type 30records are specified in the SMFPRMxx member of SYS1.PARMLIB.

Cache RMF Reporter record numberIf you use a different SMF record number than 245 for cache records, use thisprocedure to ensure that Tivoli Decision Support for OS/390 records cache datacorrectly:1. Copy member DRLRS245 (a record definition) from the DEFS library to your

LOCAL.DEFS library.2. Change IDENTIFIED BY SMFFnTYP = 245 to the correct record number for all

cache records, where n can be 5, 7, 8, and 9.3. Use the administration dialog to process the record definition.

Select Process Tivoli Decision Support for OS/390 statements from the Otherpulldown menu in the dialog. Process member DRLRS245 from yourLOCAL.DEFS library.

Starting from MVS 5.2.2, a new subtype 5 record for SMF type 74 supplies cachinginformation.


Update lookup tablesThe MVS performance management component uses several lookup tables whenstoring data in the Tivoli Decision Support for OS/390 database. You need toupdate the lookup tables to include parameters specific to your installation.





MVSPM_DEVICE_ADDR Converts MVS deviceaddresses. Used togroup certain deviceaddresses into one.

MVS_SYSTEM_IDLCU_NUMBERDEVICE_NUMBER

CACHE_SUBSYSTEM_IDDESCRIPTIONDEVICE_NUMBER_CONVVOLSER

MVSPM_TIME_RES Defines the timeperiod for whichdata is to berecorded.

HOURPERIOD_NAMETABLE_SET_NAME

TIME_RESOLUTION

MVSPM_UNIT_TYPE Converts MVS unitcodes to a deviceclass and unit type.

UNIT_CODE DESCRIPTIONDEVICE_CLASSUNIT_TYPE

MVS_MIPS_T This table associatesMVS system IDs andCPUs model with anumber of MIPS.


MIPSDESCRIPTION



DESCRIPTIONSYSPLEX_NAME

MVS_WORKLOAD_TYPE Converts MVSperformance groupsto workload types. Italso contains theresponse-timeobjectives for theworkload types.

MVS_SYSTEM_IDPERF_GROUPPERF_GROUP_PERIODDOMAIN

DESCRIPTIONWORKLOAD_TYPERESPONSE_TIME_OBJ

MVS_WORKLOAD2_TYPE Converts MVSworkload groups andservice classes toworkload types.


DESCRIPTIONWORKLOAD_TYPE

For information on updating the lookup tables using the administration dialog, see“Updating lookup tables” on page 11.

Update MVSPM_DEVICE_ADDR tableThe MVSPM_DEVICE_ADDR lookup table converts MVS device numbers to asynonym. You can use this table if you do not want detail information about eachtape device, but want to summarize by control unit. You can also use it to matchthe cache subsystem ID with the logical control unit number for DASD controlunits.

You need not update this lookup table unless you have special needs.

The MVSPM_DEV_ADDR lookup table contains these columns:

MVS_SYSTEM_ID The actual SMF system ID. The rest of theinformation in the table applies only to thatsystem.

DEVICE_NUMBER The 4-character device number (in hexadecimal).

LCU_NUMBER The 2-character MVS logical control unit number.This can contain global search characters.

CACHE_SUBSYSTEM_ID The 4-character 3390 cache subsystem ID.



|

DESCRIPTION The description for the LCU number or devicenumber.

DEVICE_NUMBER_CONV The MVS device number that should substitute thenumber matching the MVS_SYSTEM_ID andLCU_NUMBER or DEVICE_NUMBER, or both.

VOLSER The volume serial number that should be usedinstead of the volume serial in the RMF deviceactivity records. Any EBCDIC character can beused. If this field is blank, the volume serialnumber is not changed.

There are no defaults for any of these columns.

Following is an example of how the MVSPM_DEVICE_ADDR table might look.MVS DEVICE CACHESYSTEM LCU DEVICE NUMBER SUBSYSTEMID NUMBER NUMBER CONV ID VOLSER DESCRIPTION------- ------ ------- ------- --------- ------ -----------------MVS1 09 011_ - 0036 - UNIT=3390 CachedMVS1 0F 014_ - 0040 - UNIT=3390 CachedMVS1 0F 015_ - 0040 - UNIT=3390 CachedMVS1 0F 016_ - 0040 - UNIT=3390 CachedMVS1 0F 017_ - 0040 - UNIT=3390 CachedMVS1 1A 054_ 0540 - TAPE1A UNIT=3490MVS1 22 056_ 0560 - TAPE22 UNIT=3480MVS1 27 059_ 0590 - TAPE27 UNIT=3420MVS1 30 07A_ 07A0 - TAPE30 UNIT=3480

The first five rows are used to put the CACHE_SUBSYSTEM_ID into theMVSPM_DEVICE_H table. This makes it possible to correlate reports about deviceand cache performance. The next four rows are used to group all tape devicestatistics by control unit instead of by device.

Update MVSPM_TIME_RES tableThe MVSPM_TIME_RES lookup table defines the time resolution to use for eachrow of data stored in a set of tables. You can use this lookup table to specify thatdata should be recorded for a time period other than 1 hour.

All MVS performance management component tables are, by default, designed tocontain hourly data, but you can tailor the tables to use other time periods for allor selected hours.

You can use any time period that is a multiple of 60 (for example, 120 providesone row for every 2 hours of input data). Time periods of 30, 20, 15, 12, 10 or 6minutes also can be used. However, the time periods are dependent upon thelength of the RMF interval. Do not select a time period less than the RMF intervalor the SMF type 30 record interval. The period length is specified in theMVSPM_TIME_RES lookup table in the TIME_RESOLUTION column.

The MVSPM_TIME_RES lookup table contains these columns:

HOUR The hour of the day that the time resolutionapplies to (for example, 00 to 23).

PERIOD_NAME Name of the period.

SYSTEM_ID The name of the system for which the timeresolution is defined.



TABLE_SET_NAME The name that identifies the set of tables the timeresolution is defined for.

TIME_RESOLUTION The time resolution, in minutes, for the set oftables. This defines the time period for which datais to be recorded. Valid values are 1, 2, 3, 5, 6, 10,12, 15, 20, 30, and any multiple of 60. The timeresolution value should be an even multiple of theintervals used by the SMF type 30, 42, 41 (uses15-minute fixed intervals), and the cache reporterrecords. Do not specify a value less than the RMFinterval.

If this table is left empty, all MVS performance management tables will have onerow per hour. In this example, all MVS performance management tables have a30-minute time resolution for the prime shift and 2 hours for all other shifts.

TABLEPERIOD SYSTEM SET TIME

HOUR NAME ID NAME RESOLUTION---- -------- ------ ------------------- ----------% PRIME % MVSPM% 30% % % MVSPM% 120

Update MVSPM_UNIT_TYPE tableThe default table shipped with the System Performance feature is usually sufficientfor most installations. You need not update this lookup table.

Update MVS_MIPS_T tableBoth the MVS component and the MVS performance management component usethis lookup table. For details on updating this table, see “Update MVS_MIPS_Ttable” on page 288.

Update MVS_SYSPLEX tableBoth the MVS component and the MVS performance management component usethis lookup table. For details on updating this table, see “Update MVS_SYSPLEXtable” on page 289.

Update MVS_WORKLOAD_TYPE tableBoth the MVS component and the MVS performance management component usethis lookup table. For details on updating this table, see “UpdateMVS_WORKLOAD_TYPE table” on page 289.

Update MVS_WORKLOAD2_TYPE tableBoth the MVS component and the MVS performance management component usethis lookup table. For details on updating this table, see “UpdateMVS_WORKLOAD2_TYPE table” on page 291.

Update control tablesThe MVS performance management component also uses these control tables whenupdating data tables:

DAY_OF_WEEK This control table defines the day type for each dayof the week.



|

|||

PERIOD_PLAN This control table defines the partition of a day intoperiods (such as shifts).

SPECIAL_DAY This control table defines the day type for specialdays (such as holidays).

Ensure that these control tables include the correct information. For descriptions ofthese control tables and examples of their contents, refer to the AdministrationGuide.




The MVS performance management component collects records from the SMF dataset, and stores the data in the Tivoli Decision Support for OS/390 database. Thereporting function extracts data from the database and creates reports that yourequest through the Tivoli Decision Support for OS/390 reporting dialogs. You canuse the reports to perform detailed analysis of system performance and to identifyproblem areas in your system.

Figure 184 on page 590 shows an overview of the flow of data through the MVSperformance management component.

589

MVS

SMF log

SMF_030SMF_033_1SMF_041_3SMF_042_1SMF_042_5SMF_042_6

SMF_070SMF_070_1SMF_070_2SMF_071SMF_072_1SMF_072_2SMF_072_3SMF_072_4

Recorddefinitions

Recordprocedures

Recorddefinitions

DRL2S030DRL2S070DRL2S078DRL2542VDRL2S702

SMF_030_XSMF_042_6_XSMF_42_5_XSMF_070_XSMF_070_2_XSMF_074_6SMF_92

Data tables

MVSPM_APPC_H

MVSPM_CACHE_HMVSPM_CF_LINK_H

MVSPM_APPL_HMVSPM_BMF_H

MVSPM_CF_PROC_HMVSPM_CF_REQUEST_HMVSPM_CF_TO_CF_HMVSPM_CHANNEL_HMVSPM_CLUSTER_HMVSPM_CPU_HMVSPM_CRYPTO_PCI_HMVSPM_CRYPO_CCF_HMVSPM_DATASET_HMVSPM_DEVICE_AP_HMVSPM_DEVICE_HMVSPM_ENQUEUE_HMVSPM_FICON_HMVSPM_GOAL_ACT_HMVSPM_HS_CHAN_HMVSPM_LPAR_HMVSPM_OMVS_BUF_HMVSPM_OMVS_FILE_HMVSPM_OMVS_GHFS_HMVSPM_OMVS_HFS_H

Lookup andcontrol tablesMVSPM_TIME_RESMVSPM_DEVICE_ADDRMVS_MIPS_TMVS_WORKLOAD_TYPEMVS_WORKLOAD2_TYPEMVS_SYSPLEXMVSPM_UNIT_TYPEPERIOD_PLANDAY_OF_WEEKSPECIAL_DAY

Reports


Collect

SMF_073SMF_074_1SMF_074_2SMF_074_3SMF_074_4SMF_074_5SMF_074_6SMF_074_7SMF_075SMF_077SMF_078_1SMF_078_2SMF_078_3SMF_079SMF_CACHE

MVSPM_OMVS_KERN_HMVSPM_OMVS_MOUNT_HMVSPM_PAGE_DS_HMVSPM_PAGING_HMVSPM_RAID_RANK_HMVSPM_STORAGE_HMVSPM_STORCLASS_HMVSPM_SWAP_HMVSPM_SYSTEM_HMVSPM_VLF_HMVSPM_VOLUME_HMVSPM_VS_CSASQA_HMVSPM_VS_PRIVATE_HMVSPM_VS_SUBPOOL_HMVSPM_WLM_SERVED_HMVSPM_WLM_STATE_HMVSPM_WORKLOAD_HMVSPM_WORKLOAD2_HMVSPM_XCF_MEMBER_HMVSPM_XCF_PATH_HMVSPM_XCF_SYS_H

Figure 184. MVS performance management component data flow

MVS performance management data flow


Lookup tablesAfter collecting the necessary records and generating intermediate records, TivoliDecision Support for OS/390 stores the data in the Tivoli Decision Support forOS/390 database.



As it updates the tables, the MVS performance management component useslookup tables to convert MVS performance groups to workload names (forexample, TSO or CICS), and to convert device addresses. Figure 185 on page 593shows which data tables contain information from lookup tables.




MVS_SYSTEM_IDPERF_GROUP_NOPERF_GROUP_PERIODDOMAIN

MVS_SYSTEM_IDLCU_NUMBERDEVICE_NUMBER

CACHE_SUBSYSTEM_IDDEVICE_NUMBER_CONVVOLSER



MVSPM_APPL_HMVSPM_DATASET_HMVSPM_STORAGE_HMVSPM_WORKLOAD_H

MVSPM_DEVICE_AP_H

MVSPM_DEVICE_H

MVS_WORKLOAD_TYPE

MVSPM_DEVICE_ADOR

WORKLOAD_TYPE

SYSPLEX_NAMEMVS_SYSPLEX MVSPM_APPL_H

MVSPM_APPL_HMVSPM_DEVICE_AP_HMVSPM_GOAL_ACT_HMVSPM_WLM_SERVED_HMVSPM_WLM_STATE_HMVSPM_WORKLOAD2_H

MVS_WORKLOAD2_TYPE

MVSPM_UNIT_TYPEMVSPM_DEVICE_HMVSPM_DEVICE_AP_H

WORKLOAD_TYPE

TIME_RESOLUTION

UNIT_CODE

DEVICE_CLASSUNIT_TYPE

HOURPERIOD_NAMESYSTEM_IDTABLE_SET_NAME

MVSPM_TIME_RES

MVSPM_APPC_HMVSPM_APPL_HMVSPM_BMF_HMVSPM_CACHE_HMVSPM_CF_LINK_HMVSPM_CF_PROC_HMVSPM_CF_REQUEST_HMVSPM_CF_TO_CF_HMVSPM_CHANNEL_HMVSPM_CLUSTER_HMVSPM_CPU_HMVSPM_CRYPTO_CCF_HMVSPM_CRYPTO_PCI_HMVSPM_DATASET_HMVSPM_DEVICE_AP_HMVSPM_DEVICE_HMVSPM_ENQUEUE_HMVSPM_FICON_HMVSPM_GOAL_ACT_HMVSPM_HS_CHAN_HMVSPM_LPAR_HMVSPM_OMVS_BUF_H

MVSPM_OMVS_FILE_HMVSPM_OMVS_GHFS_HMVSPM_OMVS_HFS_HMVSPM_OMVS_KERN_HMVSPM_OMVS_MOUNT_HMVSPM_PAGE_DS_HMVSPM_PAGING_H

MVSPM_STORCLASS_HMVSPM_SWAP_HMVSPM_SYSTEM_HMVSPM_VLF_HMVSPM_VS_CSAQSA_HMVSPM_VS_PRIVATE_HMVSPM_VS_SUBPOOL_HMVSPM_WLM_SERVED_HMVSPM_WLM_STATE_HMVSPM_WORKLOAD_HMVSPM_WORKLOAD2_HMVSPM_XCF_MEMBER_HMVSPM_XCF_PATH_HMVSPM_XCF_SYSTEM_H

MVSPM_RAID_RANK_HMVSPM_STORAGE_H


CPU_BUSY_MIPSMVS_MIPS_T MVSPM_CPU_H

MVSPM_SYSTEM_H


CPU_BUSY_MIPSMIPS_PER_LOG_CPMIPS_PER_LPARPHYS_PROC_LPAR

MVS_MIPS_T MVSPM_LPAR_HMIPS

MIPS




The MVS performance management component uses the DAY_OF_WEEK,PERIOD_PLAN, and SPECIAL_DAY control tables when updating all of the hourlytables. For information on the common control tables, refer to the AdministrationGuide.

For more information about the tables the component updates, and the lookuptables it uses, see Chapter 32, “Data tables, views, and lookup tables”, on page 601.




The MVS performance management component collects records from the systemmanagement facilities (SMF) log. The MVS operating system writes records thatcontain information about configuration, paging activity, and workload. Job-relatedrecords include information on the CPU time, SYSOUT activity, and ddnameactivity of each job step, job, APPC/MVS transaction program, and TSO/E session.

The MVS performance management component processes these records from theSMF log:

595


Recorddefinition Description

30 SMF_030 Common address space work—This record contains operationinformation such as the job and step start and end times, step CPUtime, step termination status, number of records in DD DATA andDD * data sets processed by the step and job, device allocation starttime, problem program start time, and storage protect key. Therecord contains the number of page-ins, page-outs, swap-ins, andswap-outs for both virtual input output (VIO) and non-VIO datasets. The record contains information on the number of hiperspacepage moves and the movement of pages between expanded storageand central (real) storage. This data can be used in resourceplanning. Information is added to account for time spent inhiperspace processing on a step basis. The record contains an entryfor each data set defined by a DD statement or dynamic allocation.Each entry lists the device class, unit type, device number, executechannel program (EXCP) count, and device connect time for the dataset.Note: This record can be synchronized to the global interval (Seerecord type 42, subtype 5).

30 2, 3 SMF_030_X This record contains a processor section, which is added to SMF type30 extension records. These extension records are created if severalEXCP section lengths would exceed the maximum length (only forMVS releases prior to 5.1).

33 1 SMF_033_1 APPC/MVS TP accounting—MVS writes this record whenAPPC/MVS inbound conversions create work scheduled by theAPPC/MVS transaction scheduler.

41 3 SMF_041_3 DIV ACCESS/UNACCESS—This record provides resource usageinformation regarding data-in-virtual (DIV) objects. Subtype 3collects virtual lookaside facility (VLF) statistics and is written every15 minutes.

42 1 SMF_042_1 DFP statistics and configuration—MVS creates this record on a timedinterval to collect device statistics. This record summarizes, on astorage-class basis, the buffer manager 'hits' (number of page-readrequests handled by the buffer manager).

42 2 SMF_042_2 SMF_042_2 is created on a timed interval to collect device cachestatistics. This records contains metrics for each cache control unit(Model 3990-3) having at least one Storage.

42 3 SMF_042_3 SMF_042_3 for Operational Services event audit records written eachtime the SMS configuration changes when:

1. Operator issues VARY SMS, or

2. ISMF ’ACTIVATES’ or activates via SETSMS, or

3. ENF event occurred after VARY of SMS managed volume.

42 4 SMF_042_4 SMF_042_4 is written to collect System Data Mover session statisticsfor a concurrent copy sessin or for an extended sequent data wheninterfacing with the backup program.

42 5 SMF_042_5 DFP statistics and configuration—MVS creates this record on a timedinterval to collect device statistics. This record includes storage classI/O statistics. This subtype is written when the global SMF intervalexpires. The global SMF interval is specified via the INTVALparameter in the SMF PARMLIB member. If INTVAL is not specified,the system does not write subtype 5.Note: Record type 30 can also be synchronized to the global interval.

MVS performance management log and record definitions


||||||

|||||

|

|

|

||||||



42 5 SMF_042_5_X This record is built by record procedure for each storage classvolume header section.

42 6 SMF_042_6 DFP statistics and configuration—MVS creates this record on a timedinterval to collect device statistics. Subtype 6 records the data setlevel I/O statistics. These two events cause subtype 6 to begenerated:

v Close.

v Immediately after the recording of the type 30 interval record. Thisis on subtype 6 for each type 30 interval record.

42 6 SMF_042_6_X This record is built by record procedure for each data set section.

70 SMF_070 RMF CPU activity—MVS writes this record for each measurementinterval and when the session terminates. The record includesgeneral information on CPU use during the interval (for example,wait time) and address space use. The record also contains data forlogical partition (LPAR) management.

70 2 SMF_070_2 RMF Cryptographic Hardware Activity. MVS writes this record foreach measurement interval and when the session terminates. Itcontains measurement data for PCI cryptographic coprocessors andaccelerators.

70 SMF_070_X A subtype 20 record is built for each PR/SM partition. A subtype 10record is built for each processor section, and the associated PR/SMlogical processor data section and PR/SM partition data section.

70 2 SMF_070_2_X A record is built by new DRL2S702 record procedure for each PCIcryptographic accelerator (PCICA) data section.

71 SMF_071 RMF paging activity—This record contains information about thedemands made on the system paging facilities and the utilization ofcentral storage and expanded storage during the reporting interval.The record also contains details of ESAME mode.

72 1 SMF_072_1 RMF workload activity—MVS writes this record for eachperformance group (PG) defined in the installation performancespecifications (IPS) and contains data on each PG period for a PGnumber. It contains the workload level, service units, and other datafor all transactions.

72 2 SMF_072_2 RMF storage data—This record includes storage data, grouped bydomain and control performance groups.

72 3 SMF_072_3 This record is created by RMF Monitor I if workload activitymeasurements are activated and the system is running in goal mode.

72 4 SMF_072_4 This record is written for a system running in goal mode from theMonitor III Data Gatherer for each service class period of eachservice class defined in the active service policy.

73 SMF_073 RMF channel path activity—MVS writes this record when channelpath activity measurement is requested. It creates entries for all validchannel paths in the system. The record also contains details ofdynamic channel management (DCM).



|

|

|



74 1 SMF_074_1 RMF device activity—This record contains general information onthe number of devices and types. It contains the volume serialnumber for tape and direct access devices, number of requests on thedevice, total active, pending and connect time to service thoserequests, the number of requests enqueued for the device and thedevice number, class and type and other data collected about thedevice. The record also contains details of PAV support.

74 2 SMF_074_2 RMF XCF activity—Monitor III Cross-System Coupling Facility (XCF)measurement writes this subtype. This record contains controlinformation for splitting and reassembling of the XCF records. Itdescribes the message traffic between the local system (where RMF isrunning) and the remote systems on a system level, the messagetraffic broken down by signalling paths connecting the local systemwith the remote systems, the message traffic on a member basis formembers on the local system and members communicating with thelocal system.

74 3 SMF_074_3 RMF OMVS Kernel Activity—Monitor III Data Gatherer collectsOpen Edition MVS measurements data. The record also containsdetails of UNIX support.

74 4 SMF_074_4 RMF XES/CF activity. This record stores coupling facility data. Onerecord is written for each coupling facility by each member in thesysplex. For any particular coupling facility, all data sections arepresent in each record.

74 5 SMF_074_5 RMF Cache Subsystem Device Activity—One record is written foreach cache subsystem and all devices attached to this control unit.This record also contains data for the redundant array ofindependent disks (RAID) rank.

74 6 SMF_074_6 RMF Hierarchical File System statistics—Monitor III Data Gatherercollects Open Edition HFS statistics MVS measurement data.

74 7 SMF_074_7 FICON™ director activities—data statistics.

75 SMF_075 RMF page data set activity—MVS writes this record for each pagedata set monitored during each RMF measurement interval.

77 SMF_077 RMF enqueue activity—This record contains an enqueue controlsection containing the status indicator and an enqueue data sectionidentifying any contentions that occurred during each measurementinterval.

78 1 SMF_078_1 RMF Monitor I activity—This record reports I/O querying activityfor the 4381 processor.

78 2 SMF_078_2 RMF Monitor I activity—This record reports virtual storage activity.

78 2 SMF_078_2_X This record is built for each virtual storage private data section.

78 3 SMF_078_3 RMF Monitor I activity—This record reports I/O querying activityfor the 3090™ and ES/9000® Series processors. The record alsocontains details of dynamic change management (DCM).

79 SMF_079 RMF Monitor II activity—This record is written at each measurementinterval and when the session is terminated. It contains a section thatis identical for all Monitor II requests and a subtype section.

92 1, 2, 4, 5, 6,10, 11

SMF_092 OpenMVS File System activity—This record contains detailedinformation about HFS OpenEdition activity, for example, mount,unmount and remount, quiesce and unquiesce. It also containsinformation about open and close of a single file.





245* SMF_CACHE Cache RMF Reporter SMF record

* This record is user-defined (that is, it is not part of the standard IBM records in the range 0-127). However, it iswritten by an IBM licensed program. The default record number is shown above.

Note: To collect the new SMF records type 70, subtype 2 correctly, the RMF aparOW49808 must be installed.

Refer to MVS/ESA System Management Facilities for a detailed description of theserecords.

Record proceduresThe MVS performance management component processes some SMF recordsthrough record procedures. The record procedures add additional data needed tocreate meaningful reports. Figure 186 lists the records affected by recordprocedures and the resulting records.

The MVS performance management component then uses the new records toupdate tables in the Tivoli Decision Support for OS/390 database.

Input record

Recordprocedure

Outputrecord

SMF_030 SMF_042_5 SMF_070 SMF_078_2

DRL2S030(prior to MVS 5.1)

DRL2S42VBuilds onerecord foreach volumereader storageclass(VTOC, VVDS)

Adds a processor sectionto the SMF 30 extensionrecords (subtypes 2 and3) that are created ifthere are many EXCPsections whose lengthwould exceed themaximum length

DRLS2070Builds a recordfor each PR/SMpartition

Builds a recordfor each processorsection, and theassociated PR/SMlogical processordata section andPR/SM partitiondata section

DRL2S070 DRL2S078Builds one recordfor each virtualstorage privatearea datasection

SMF_030_X(subtypes 2 and 3 only)


SMF_070_X(subtype 10) SMF_078_2_XSMF_042_5_X

Builds a recordfor eachcryptographicacceleratordata sections

DRL2S702

SMF_070_2_X

SMF_042_6

DRL2S042

Builds one recordfor each data setsection

SMF_042_6_X

Figure 186. Record procedures



||

Chapter 32. Data tables, views, and lookup tables

This chapter describes the data tables, views, and lookup tables used by the MVSperformance management component. For descriptions of common data tables,lookup tables, and control tables used by the System Performance featurecomponents, refer to the Administration Guide.

Data tablesThis section describes the data tables for the MVS performance managementcomponent.

MVSPM_APPC_HThis table provides statistics on work created by APPC/MVS inboundconversations. It contains transaction program data from SMF type 33, subtype 1records.

This table is updated by the MVSPM_TIME_RES lookup table.


601


DATE k DATE Date of the intervals when the APPC activities weremeasured. From SMF33TST and SMF33TED.

TIME k TIME Start time of the intervals when the APPC activities weremeasured. From SMF33TST and SMF33TET.

PERIOD_NAME k CHAR(8) Name of the period. This is derived using field SM33SIDand the interval start time (derived from SMF33TST,SMF33TSD, SMF33TET, and SMF33TED) as parameters inthe PERIOD function.

MVS_SYSTEM_ID k CHAR(4) MVS system ID. This is the SMF system ID. FromSMF33SID.

TP_CLASS k CHAR(8) Transaction program class. This is a general grouping oftransaction programs with related scheduling properties.From SMF33TPC.

TP_TYPE k SMALLINT APPC/MVS transaction program schedule type. FromSMF33TSC.

USER_ID k CHAR(8) RACF user ID of the requesting user. From SMF33UID.

LOCAL_LU_NAME k CHAR(17) Local logical unit name for the transaction program. FromSMF33LLU.

PARTNER_LU_NAME k CHAR(17) Partner logical unit name for the user’s use of thetransaction program. From SMF33PLU.

BYTES_RECEIVED FLOAT Total amount of data received, in bytes. This is the sum ofSMF33DAR distributed from SMF33TSD and SMF33TSTto SMF33TED and SMF33TET.

BYTES_SENT FLOAT Total amount of data sent, in bytes. This is the sum ofSMF33DAS distributed from SMF33TSD and SMF33TSTto SMF33TED and SMF33TET.

CONVERS_ALLOCATED INTEGER Total number of conversations allocated. This is the sumof SMF33CNA distributed from SMF33TSD andSMF33TST to SMF33TED and SMF33TET.

CONNECT_MSEC FLOAT Total device connect time, in milliseconds. This is the sumof SMF33DCT distributed from SMF33TSD andSMF33TST to SMF33TED and SMF33TET.

CONVERSATIONS INTEGER Total number of conversations. This is the sum ofSMF33CN distributed from SMF33TSD and SMF33TST toSMF33TED and SMF33TET.

ELAPSED_EXEC_SEC FLOAT Total elapsed time from the time the request started itsexecution to the time its execution ended, in seconds. Thisis the sum of the time intervals from SMF33TSD andSMF33TST to SMF33TED and SMF33TET.

ELAPSED_FMH_SEC FLOAT Total elapsed time from the time the request wasrecognized by the functional manager header 5 to thetime it was placed in the scheduler work queue, inseconds. This is the sum of the time intervals fromSMF33FMD and SMF33FMT to SMF33TQD andSMF33TQT.

ELAPSED_QUEUE_SEC FLOAT Total elapsed time from the time the request was placedin the scheduler work queue to the time its executionstarted, in seconds. This is the sum of the time intervalsfrom SMF33TQD and SMF33TQT to SMF33TSD andSMF33TST.

MVS performance management data tables



EXCP_COUNT FLOAT Total number of EXCPs. This is the sum of SMF33EXPdistributed from SMF33TSD and SMF33TST to SMF33TEDand SMF33TET.

RECEIVES INTEGER Total number of receives issued. This is the sum ofSMF33REC distributed from SMF33TSD and SMF33TST toSMF33TED and SMF33TET.

SENDS INTEGER Total number of sends issued. This is the sum ofSMF33SEN distributed from SMF33TSD and SMF33TST toSMF33TED and SMF33TET.

SRB_SECONDS FLOAT Total service request block time, in seconds. Calculated asthe sum of 0.01*SMF33SRB distributed from SMF33TSDand SMF33TST to SMF33TED and SMF33TET.

TCB_SECONDS FLOAT Total task control block time, in seconds. Calculated asthe sum of 0.01*SMF33TCB distributed from SMF33TSDand SMF33TST to SMF33TED and SMF33TET.

TIME_RESOLUTION SMALLINT Time resolution used for this table, in minutes. Thedefault is 60 minutes. From TIME_RESOLUTION in theMVSPM_TIME_RES lookup table.

TP_USE_COUNT INTEGER Number of times the transaction program was used bythe user. This is the sum of SMF33UCT.



MVSPM_APPL_HThis table provides statistics on application activity by workload type for batchjobs, TSO sessions, started tasks, and APPC sessions. It contains data from SMFtype 30, subtypes 2 and 3 records.

This table is updated by the MVS_SYSPLEX, MVSPM_TIME_RES,MVS_WORKLOAD_TYPE, and MVS_WORKLOAD2_TYPE lookup tables.



DATE k DATE Date of the mid measurement. From SMF30IDT,SMF30IST, SMF30DTE, and SMF30TME (or SMF30ISSand SMF30IET according to the UPDATE definitions youhave customized for local or GMT time).

TIME k TIME Time (rounded down as specified in theMVSPM_TIME_RES table) of the mid measurement.From SMF30IDT, SMF30IST, SMF30DTE, andSMF30TME.

PERIOD_NAME k CHAR(8) Name of the period. This is derived using fieldsSMF30IDT, SMF30IST, SMF30DTE, and SMF30TME fromthe record as parameters in the PERIOD function.


WORKLOAD_TYPE k CHAR(8) MVS workload type name. From WORKLOAD_TYPE inthe MVS_WORKLOAD_TYPE orMVS_WORKLOAD2_TYPE lookup table.

PERF_GROUP_NO k CHAR(4) Performance group number. This field is zero when inworkload management goal mode. From SMF30PGN.

SERVICE_CLASS k CHAR(8) Service class name. This field is blank when in workloadmanagement compatibility mode. From SMF30SCN.

BLOCKS FLOAT Number of blocks transferred to or from the data set, ordata sets if concatenation is used. This is the sum ofSMF30TEP.

BLOCKS_IN_AUX FLOAT Number of blocks that were paged in from auxiliarystorage. This is the sum of SMF30KIA.

BLOCKS_IN_ES FLOAT Number of blocks that were paged in from expandedstorage. This is the sum of SMF30KIE.

BLOCKS_OUT_AUX FLOAT Number of blocks that were paged out to auxiliarystorage. This is the sum of SMF30KOA.

BLOCKS_OUT_ES FLOAT Number of blocks that were paged out to expandedstorage. This is the sum of SMF30KOE.

CONNECT_MSEC FLOAT Device connect time for the address space, inmilliseconds. This is the sum of SMF30TCN.

CPU_ENQ_PROMOT_SEC FLOAT CPU time consumed for an address space or job whileenqueue promoted in seconds. Calculated as sumSMF30CEP/1024.

CPU_HIPER_SECONDS FLOAT CPU time used to support data transfer to and from ahiperspace backed by expanded storage, in seconds.Calculated as the sum of SMF30HPT/100 for recordswhere bit 0 or bit 10 of SMF30TFL is 0.



|


CPU_INTR_SECONDS FLOAT CPU time used to process I/O interrupts, in seconds.Calculated as the sum of SMF30IIP/100 for recordswhere bit 0 or bit 9 of SMF30TFL is 0.

CPU_RCT_SECONDS FLOAT CPU time used by the region control task, in seconds.Calculated as the sum of SMF30RCT/100 for recordswhere bit 0 or bit 11 of SMF30TFL is 0.

CS_FRAME_SECONDS FLOAT Active frame time for frames in central storage, inseconds. Calculated as the sum of (1024E-7*SMF30RES*SMF30PSC/SMF30CPT).

DATA_SPACE_STOR_MB FLOAT Amount of user key data space and hiperspace virtualstorage (high water mark) used during the step or job, inmegabytes. This is the maximum of SMF30DSV.

ENCLAVE_ACTIVE_SEC FLOAT Enclave transaction active time, in seconds. This is thesum of SMF30ETA.

ENCLAVE_SECONDS FLOAT CPU time used by enclaves, in seconds. This value isalso included in TCB_STEP_SECONDS. Calculated asthe sum of SMF30ENC/100 for records where bit 0 or bit13 of SMF30TFL is 0.

ICSF_INSTRUCTIONS FLOAT Integrated Cryptographic Service Facility/MVS(ICSF/MVS) service count. This is the number ofcryptographic instructions executed on behalf of thecaller (within the caller’s address space). Calculated asthe sum of SMF30CSC.

INELIGIBLE_TIME_1 FLOAT Job ineligible for execution time, in seconds. Schedulingenvironment is not available. This is the sum ofSMF30RQT.

INELIGIBLE_TIME_2 FLOAT Job ineligible for execution time, in seconds. Job hold,job class hold, job queue hold, duplicate jobname, or jobexecution limits. This is the sum of SMF30HQT.

INPUT_RECORDS INTEGER Number of input records collected from the input log.

MEASURED_SEC FLOAT Measured time period, in seconds. This is the sum of thetime intervals from SMF30DTE and SMF30TME toSMF30IDT and SMF30IST.

MEMLIMIT_MB FLOAT Memlimit value (in MB). This is the maximumoccurrenceof SMF30MEM.

PAGEINS FLOAT Number of pages that were paged in from auxiliarystorage. This is the sum of SMF30PGI.

PAGEINS_BLK_AUX FLOAT Number of blocked pages that were paged in fromauxiliary storage. This is the sum of SMF30BIA.

PAGEINS_BLK_ES FLOAT Number of blocked pages that were paged in fromexpanded storage. This includes the first page of eachblock. This is the sum of SMF30BIE.

PAGEINS_COMMON FLOAT Number of common area page-ins (LPA + CSA). This isthe sum of SMF30CPI.

PAGEINS_HIPER FLOAT Number of hiperspace page-ins from auxiliary toprocessor storage. This is the sum of SMF30HPI.


PAGEINS_SHARED FLOAT Number of IARVSERV shared pages that were paged infrom auxiliary storage in this address space. This is thesum of SMF30PAI.



|


PAGEINS_SHARED_ES FLOAT Number of IARVSERV shared pages that were paged infrom expanded storage in this address space. This is thesum of SMF30PEI.

PAGEINS_UNBLK_ES FLOAT Number of unblocked pages that were paged in fromexpanded storage. This includes the first page of eachblock. This is the sum of SMF30PIE.


PAGEOUTS FLOAT Number of pages that were paged out to auxiliarystorage. This is the sum of SMF30PGO.

PAGEOUTS_BLK_AUX FLOAT Number of blocked pages that were paged out toauxiliary storage. This is the sum of SMF30BOA.

PAGEOUTS_BLK_ES FLOAT Number of blocked pages that were paged out toexpanded storage. This is the sum of SMF30BOE.

PAGEOUTS_HIPER FLOAT Number of hiperspace page-outs from processor toauxiliary storage. This is the sum of SMF30HPO.

PAGEOUTS_UNBLK_ES FLOAT Number of unblocked pages that were paged out toexpanded storage. This is the sum of SMF30POE.

PAGEOUTS_VIO FLOAT Number of VIO page-outs. This is the sum ofSMF30VPO.

PAGES_SWAPPED_IN FLOAT Number of pages swapped in. This is the sum ofSMF30PSI.

PAGES_SWAPPED_OUT FLOAT Number of pages swapped out. This is the sum ofSMF30PSO.

PREPARATION_TIME FLOAT Job preparation time, in seconds. This is the elapsed timebefore the job was first queued for execution. This is thesum of SMF30JQT.

PRIORITY FLOAT sum of the weighted priorities. This is the sum ofSMF30PTY*SMF30CPT/100.

READ_MISSES_HIPER FLOAT Number of hiperspace read misses (a read miss is anattempt to read a frame that is not in expanded storage).This is the sum of SMF30CPM.

REPORT_CLASS CHAR(8) Report class name. This field is blank when in workloadmanagement compatibility mode. From SMF30RCN.

SCHEDULING_ENV FLOAT Scheduling environment name. This field is blank if noscheduling environment is specified. From SMF30PFL.

SERVICE_UNITS_ENCL FLOAT Enclave CPU service units. This is the sum ofSMF30ESU.

SHARED_PAGE_SEC FLOAT Number of CPU page seconds for the IARVSERV sharedcentral storage frames in use by this address space, inseconds. This is the sum of SMF30PSF*0.001.

SMF_INTERVAL FLOAT Duration of the SMF measurement interval, in minutes.Calculated as SMF30DTE and SMF30TME, minusSMF30IDT and SMF30IST, divided by 60.

SRB_INIT_SECONDS FLOAT Initiator CPU time under SRB, in seconds. Calculated asthe sum of SMF30ISB/100 for records where bit 0 or bit5 of SMF30TFL is 0.




SRB_PREEMP_SECONDS FLOAT Additional CPU time accumulated by the preemptableSRBs and client SRBs for this job, in seconds. This valueis also included in the value in TCB_STEP_SECONDS.Calculated as the sum of SMF30ASR/100 for recordswhere bit 0 or bit 12 of SMF30TFL is 0.


SWAP_SEQUENCES FLOAT Number of address space swap sequences. This is thesum of SMF30NSW.


TCB_INIT_SECONDS FLOAT Initiator CPU time under TCB, in seconds. Calculated asthe sum of SMF30ICU/100 for records where bit 0 or bit6 of SMF30TFL is 0.

TCB_STEP_SECONDS FLOAT Step CPU time under TCB, in seconds. Calculated as thesum of SMF30CPT/100 for records where bit 0 or bit 1of SMF30TFL is 0.

TGET_COUNT FLOAT Number of TGETs for a TSO session. This is the sum ofSMF30TGT.


TPUT_COUNT FLOAT Number of TPUTs for a TSO session. This is the sum ofSMF30TPT.

TRAN_ACTIVE_SEC FLOAT SRM transaction active time, in seconds. Calculated asthe sum of SMF30TAT*0.001024.

TRAN_RESIDENT_SEC FLOAT SRM transaction residency time, in seconds. Calculatedas the sum of SMF30RES*0.001024.

TRANSACTIONS FLOAT Number of transactions. This is the sum of SMF30TRS ifSMF30WID = TSO, or this is the sum of 1 if SMF30STP =3. Otherwise, nothing is added.


VA_INIT_SECONDS FLOAT Initiator vector affinity time, in seconds. Calculated asthe sum of SMF30IVA/100 for records where bit 0 or bit8 of SMF30TFL is 0.

VA_STEP_SECONDS FLOAT Step vector affinity time, in seconds. Calculated as thesum of SMF30JVA/100 for records where bit 0 or bit 4 ofSMF30TFL is 0.

VS_LSQA_SWA_GT16MB FLOAT Maximum virtual storage above 16 megabytes allocatedfrom the LSQA and SWA subpools, in megabytes. This isthe maximum of SMF30EAR.

VS_LSQA_SWA_LT16MB FLOAT Maximum virtual storage below 16 megabytes allocatedfrom the LSQA and SWA subpools, in megabytes. This isthe maximum of SMF30ARB.

VS_USER_GT16MB FLOAT Maximum virtual storage above 16 megabytes allocatedfrom the user subpools, in megabytes. This is themaximum of SMF30EUR.

VS_USER_LT16MB FLOAT Maximum virtual storage below 16 megabytes allocatedfrom the user subpools, in megabytes. This is themaximum of SMF30URB.




VU_INIT_SECONDS FLOAT Initiator vector usage time, in seconds. Calculated as thesum of SMF30IVU/100 for records where bit 0 or bit 7 ofSMF30TFL is 0.

VU_STEP_SECONDS FLOAT Step vector usage time, in seconds. Calculated as thesum of SMF30JVU/100 for records where bit 0 or bit 3 ofSMF30TFL is 0.

WAITING_TIME FLOAT Job waiting for an initiator, in seconds. This is the sumof SMF30SQT.

WORKLOAD_GROUP CHAR(8) MVS workload group name. This field is blank when inworkload management compatibility mode. FromSMF30WLM.



MVSPM_BMF_HThis table provides statistics on the overall performance of the Buffer ManagerFacility (BMF). It contains data from SMF type 42, subtype 1 records.




DATE k DATE Date of the mid measurement. From SMF42DTE,SMF42TME, and SMF42TMT.

TIME k TIME Time (rounded down as specified in theMVSPM_TIME_RES lookup table) of the midmeasurement. From SMF42DTE, SMF42TME, andSMF42TMT.

PERIOD_NAME k CHAR(8) Name of the period. This is derived using fieldsSMF42DTE, SMF42TME, and SMF42TMT from the recordas parameters in the PERIOD function.


STORAGE_CLASS k VARCHAR(30) Storage class name. From SMF42PNN.

BMF_INTERVAL INTEGER Length of the BMF measurement interval, in seconds.From SMF42TMT.

DPAGE_READ_HITS FLOAT Number of directory data page read hits handled byBuffer Manager Facility. This is the sum of SMF42SDH.

DPAGE_READS FLOAT Number of directory data page reads. This is the sum ofSMF42SDT.

MEASURED_SEC FLOAT Measured time period, in seconds. This is the duration ofthe BMF measurement intervals. This is the sum ofSMF42TMT.

MPAGE_READ_HITS FLOAT Number of member data page read hits handled by BufferManager Facility. This is the sum of SMF42SRH.

MPAGE_READS FLOAT Number of member data page reads. This is the sum ofSMF42SRT.

TIME_RESOLUTION INTEGER Time resolution used for this table, in minutes. The defaultis 60 minutes. From TIME_RESOLUTION in theMVSPM_TIME_RES lookup table.



MVSPM_CACHE_HThis table provides statistics on the activity of cache subsystems (IBM 3880 Model13 or Model 23, and IBM 3990 Model 03 or Model 06 cache controllers). It containsdata written by the Cache RMF Reporter as user-defined type (the default is 245)SMF records or by the SMF type 74, subtype 5 records.




DATE k DATE Date of the mid measurement. From SMFFxDTE,SMFFxTME, and SMFFxINT.

TIME k TIME Time (rounded down as specified in theMVSPM_TIME_RES lookup table) of the midmeasurement. From SMFFxDTE, SMFFxTME, andSMFFxINT.

PERIOD_NAME k CHAR(8) Name of the period. This is derived using fieldsSMFFxDTE, SMFFxTME, and SMFFxINT from therecord as parameters in the PERIOD function.

MVS_SYSTEM_ID k CHAR(4) MVS system ID. This is the SMF system ID. FromSMFFxSID.

VOLSER k CHAR(6) Volume serial ID of the device. From RDF9VOL,RDF8VOL, RF7VOL, or RF5VOL.

DEVICE_NUM k CHAR(4) Device number. From RDF9UNIT, RDF8UNIT,RF7UNIT1, RF5UNIT1 or RDF9DEVN, RDF8DEVN,RDF7DEVN if 4 bytes device address.

BOUND_TRACK_READS FLOAT Number of read requests to bound tracks. This is thesum of RDF5RRBT.

BOUND_TRACK_WRITES FLOAT Number of write requests to bound tracks. This is thesum of RDF5WRBT.

BYPASS_CACHE_REQ FLOAT Number of bypass cache I/O requests. This is the sumof RDF9BPCR, RDF8BPCR, RDF7BPCR, or R745DBCR.

CACHE_CHAN_XFER FLOAT Number of cache-to-channel data transfer operations.This is the sum of RDF7CCDT.

CACHE_DASD_XFER FLOAT Number of cache-to-DASD data transfer operations.This is the sum of RDF9CDTO, RDF8CDTO, orR745DCTD.

CACHE_SUBSYSTEM_ID CHAR(4) For a 3990 model 3 or 6, this is the ID for the cachesubsystem; for a 3880 model 23 or 13, this is thestorage director ID. From RDF9SSID, RDF8SSID,RF7SDID, or R745DSID.

CACHING_ACTIVE_IND CHAR(3) Indicates whether caching is active for the DASDvolume. This is YES or NO. From RDF9DEV1,RDF8DEV1, or R745DVS1. For a 3880 Model 23 or 13,this is set to NO if the number of read I/Os is greaterthan 200, and the sum of normal and sequential hits is0.

CFW_READ_HITS FLOAT Number of cache fast write read hits. This is the sumof RDF9SRCH, RDF8SRCH, or R745DNRH.

CFW_READ_REQ FLOAT Number of cache fast write read requests. This is thesum of RDF9SRCD, RDF8SRCD, or R745DRNR.




CFW_WRITE_HITS FLOAT Number of cache fast write hits. This is the sum ofRDF9WCDH, RDF8WCDH, or R745DWNH.

CFW_WRITE_REQ FLOAT Number of cache fast write requests. This is the sum ofRDF9WCD, RDF8WCD, or R745DWNR.

CONTROL_UNIT_MODEL CHAR(8) Model number of the cache subsystem. FromR745CCMT.

DASD_CACHE_CH_XFER FLOAT Number of DASD-to-cache-and-channel data transferoperations. This is the sum of RDF7DCCT.

DASD_CACHE_XFER FLOAT Number of DASD-to-cache data transfer operations.This is the sum of RDF7DCCD.

DASD_CHANNEL_XFER FLOAT Number of DASD-to-channel data transfer operations.This is the sum of RF7DCDT.

DEVICES SMALLINT Number of devices under the cache subsystem. FromSMFFxNDV or SMF745DN.

DFW_ACTIVE_IND CHAR(3) Indicates whether DASD fast write is active for theDASD volume. This is YES or NO. From RDF9DEV1,RDF8DEV1, or R745DVS1.

DFW_INHIBIT_REQ FLOAT Number of DASD fast write inhibit requests (only3990). Calculated as RDFxWCR + RDFxWSR -RDFxFWCR - RDFxFWSR or R745DWRC - R745DFWC+ R745DWSR - R745DFWS.

DFW_NORMAL_REQ FLOAT Number of DASD fast write normal caching requests.This is the sum of RDF9FWCR, RDF8FWCR, orR745DFWC.

DFW_RETRIES FLOAT Number of DASD fast write retries. This is the sum ofRDF9FWDC, RDF8FWDC, or R745DFWB.

DFW_SEQ_REQ FLOAT Number of DASD fast write sequential requests. This isthe sum of RDF9FWSR, RDF8FWSR, or R745DFWS.

DFW_STAGES FLOAT Number of DASD fast write staging operations (only3990). Calculated as RDFxFWCR + RDFxFWSR -RDFxWCRH - RDFxWSRH - RDFxFWDC orR745DFWC - R745DWCH + R745DFWS - R745DWSH.

DUALCOPY_PRIMARY CHAR(3) Indicates whether the DASD volume is a primaryvolume in a duplex pair. This is YES or NO. FromRDF9DEV1, RDF8DEV1, or R745DVS1.

DUALCOPY_SECONDARY CHAR(3) Indicates whether the DASD volume is a secondaryvolume in a duplex pair. This is YES or NO. FromRDF9DEV1, RDF8DEV1, or R745DVS1.

INHIBIT_CACHE_LOAD FLOAT Number of inhibit cache loading requests. This is thesum of RDF9ICLR, RDF8ICLR, RF7ICLR, RF5ICLR, orR745DICL.

INPUT_RECORDS FLOAT Number of SMF records collected during the timeperiod specified in the TIME_RESOLUTION column.

MEASURED_SEC FLOAT Measured time period, in seconds. This is the durationof the RMF measurement intervals. This is the sum ofSMFFxINT or R745CINT.




NONCACHED_VOL_REQ FLOAT Number of I/O requests against a DASD volume withcaching disabled (only 3990). Calculated as RDFxSRCR+ RDFxRSR + RDFxWCR + RDFxWSR + RDFxSRCD +RDFxWCD + RDFxICLR + RDFxBPCR or R745DRCR +R745DWSR + R745DICL + R745DRSR + R745DRNR +R745DBCR + R745DWRC + R745DWNR.

NORM_DASD_TO_CACHE FLOAT Number of normal DASD-to-cache data transferoperations. This is the sum of RDF9DCTO,RDF8DCTO, RF7DCTO, RF5DCTO or R745DNTD.

NORM_READ_HITS FLOAT Number of normal read request hits. From RDF9SRRH,RDF8SRRH, RF7SRCRH, RF5SRCH, or R745DCRH.

NORM_READ_REQ FLOAT Number of normal read requests. This is the sum ofRDF9SRCR, RDF8SRCR, RF7SRCR, RF5SRCR, orR745DRCR.

NORM_READ_STAGES FLOAT Number of normal read DASD staging operations.Calculated as RDF8SRCR - RDF8SRRH, RDF9SRCR -RDF9SRRH, or R745DRCR - R745DCRH.

NORM_WRITE_HITS FLOAT Number of normal write request hits. FromRDF9WCRH, RDF8WCRH, or R745DWCH.

NORM_WRITE_REQ FLOAT Number of normal write requests. This is the sum ofRDF9WCR, RDF8WCR, RF7WCR, RF5WCR, orR745DWRC.

NORM_WRITE_STAGES FLOAT Number of normal write staging operations. Calculatedas RDF8WCR - RDF8WCRH, RDF9WCR -RDF9WCRH, or R745DWRC - R745DWCH.

NORM_WRITE_THRU FLOAT Number of normal write through requests. Calculatedas RDF8WCR - RDF8FWCR, RDF9WCR - RDF9FWCR,or R745DWRC - R745DWCH.

SEQ_DASD_TO_CACHE FLOAT Number of sequential DASD-to-cache data transferoperations. This is the sum of RDF9SCTO, RDF8SCTO,RDF7SCTO, or R745DTC.

SEQ_READ_HITS FLOAT Number of sequential read hits. From RDF9RSRH,RDF8RSRH, RF7RSRH, or R745DRSH.

SEQ_READ_REQ FLOAT Number of sequential read requests. This is the sum ofRDF9RSR, RDF8RSR, RF7RSR, or R745DRSR.

SEQ_READ_STAGES FLOAT Number of sequential read DASD staging operations.Calculated as RDF8RSR - RDF8RSRH, RDF9RSR -RDF9RSRH, or R745DRSR - R745DRSH.

SEQ_WRITE_HITS FLOAT Number of sequential write request hits. FromRDF9WSRH, RDF8WSRH, or R745DWSH.

SEQ_WRITE_REQ FLOAT Number of sequential write requests. This is the sumof RDF9WSR, RDF8WSR, RF7WSR, RF5WSR, orR745DWSR.

SEQ_WRITE_STAGES FLOAT Number of sequential write staging operations (only3990). Calculated as RDFxWSR - RDFxWSRH,RDFxWSR - RDFxWSRH, or R745DWSR - R745DWSH.

SEQ_WRITE_THRU_REQ FLOAT Number of sequential write through requests.Calculated as RDF8WSR - RDF8FWSR, RDF9WSR -RDF9FWSR, or R745DWSR - R745DWSH.




STATISTICS_INT_SEC FLOAT Time that passed since the cache subsystem statisticswere last reported, in seconds. From SMFFxINT orR745CINT.

SUBSYS_STOR_AVAIL FLOAT Amount of subsystem storage available for caching, inmegabytes. From BSAVAIL, CSAVAIL, GSAVAIL,SSAVAIL, or R745SAVL.

SUBSYS_STOR_CONFIG FLOAT Configured subsystem storage, in megabytes. This isthe amount of storage that exists in the cache for thesubsystem. From BSCONF, CSCONF, GSCONF,SSCONF, or R745SCNF.

TIME_RESOLUTION INTEGER Time resolution used for this table, in minutes. Thedefault is 60 minutes. From TIME_RESOLUTION inthe MVSPM_TIME_RES lookup table.



MVSPM_CF_PROC_HThis table provides data about coupling facility processor and storage utilization ina sysplex. It contains data from SMF type 74, subtype 4 records.




DATE k DATE Date of the mid measurement. From SMF74DAT,SMF74IST, and SMF74INT.

TIME k TIME Time (rounded down as specified in theMVSPM_TIME_RES table) of the mid measurement.From SMF74DAT, SMF74IST, and SMF74INT.

PERIOD_NAME k CHAR(8) Name of the period. This is derived using fieldsSMF74DAT, SMF74IST, and SMF74INT from the recordas parameters in the PERIOD function.


SYSPLEX_NAME k CHAR(8) Sysplex name (as defined in ECVTSPLX). FromSMF74XNM.

CF_NAME k CHAR(8) Name of coupling facility. From R744FNAM.

ALLOC_DUMP_STOR_MB FLOAT Average amount of dump space allocated in megabytes.Calculated as the average of R744GDSA/256.

CF_LEVEL SMALLINT Level of coupling facility. From R744FLVL.

CF_MODEL CHAR(4) Model of coupling facility. From R744FMOD.

CF_STOR_DEF_MB FLOAT Average amount of CF storage defined, in megabytes.Calculated as the average of R744GTSD/256.

CF_STOR_FREE_MB FLOAT Average amount of free CF storage, in megabytes.Calculated as the average of R744GTSF/256.

CF_VERSION CHAR(4) Version of coupling facility. From R744FVER.

CPU_BUSY_SEC FLOAT Processor busy time in seconds. Calculated as the sumof R744PBSY/1 000 000.

CPU_WAIT_SEC FLOAT Processor wait time in seconds. Calculated as the sumof R744PWAI/1 000 000.

CTRL_STOR_DEF_MB FLOAT Average amount of control storage defined, inmegabytes. Calculated as the average ofR744GCSD/256.

CTRL_STOR_FREE_MB FLOAT Average amount of free control storage, in megabytes.Calculated as the average of R744GCSF/256.

FREE_DUMP_STOR_MB FLOAT Average amount of free dump space in megabytes.Calculated as the average of R744GDSF/256.

MAX_DUMP_STOR_MB FLOAT Maximum amount of dump space requested, inmegabytes. Calculated as the maximum of R744GDSR.

MEASURED_SEC FLOAT Measured time period, in seconds. This is the durationof the RMF measurement intervals. Calculated as thesum of SMF74INT/1000.

PROCESSORS SMALLINT Number of processors in the coupling facility.Calculated as the maximum of SMF744PN.

SYSTEM_NAME CHAR(8) Name of this system (from IEASYSxx parmlib member,SYSNAME parameter). From R744FSYS.




TIME_RESOLUTION SMALLINT The time resolution used for this table, in minutes. Thedefault is 60 minutes. From TIME_RESOLUTION in theMVSPM_TIME_RES lookup table.



MVSPM_CF_REQUEST_HThis table provides data about coupling facility utilization in a sysplex. It containsdata from SMF type 74, subtype 4 records.










STRUCTURE_NAME k CHAR(16) Name of structure connected to this system or allocatedin this coupling facility. From R744QSTR or R744SNAM.




COMPL_ASYNC_REQ FLOAT Total Number of asynchronous requests completed.Calculated as the sum of R744STAC.

COMPLETED_REQUEST FLOAT Total number of requests completed. Calculated as thesum of R744STRC.

DUMP_SERIAL_NO FLOAT Number of times dump serialization was found for thisstructure (only for list and cache structures). Calculatedas the sum of R744SDMP.

LIST_ENT_LIM FLOAT List structure only: limit on number of list entries.Calculated as the maximum of R744SLEL.

LIST_ENT_USED_MAX FLOAT List structure only: maximum number of list entries usedduring interval. Calculated as the maximum ofR744SLEM.

LOCK_ENT_LIM FLOAT Lock structure only: limit on number of lock tableentries. Calculated as the maximum of R744SLTL.

LOCK_ENT_USED_MAX FLOAT Lock structure only: maximum number of lock tableentries used during interval. Calculated as the maximumof R744SLTM.


PATH_CONTENTION FLOAT Number of times CF request failed because the path wasbusy. From R744FPBC.




PEER_WAIT_CMP_NO FLOAT Count of waiting-for-peer-completion conditionsrequests. Valid only for duplexed structures. FromR744SCTC.

PEER_WAIT_CMP_SEC FLOAT Total waiting-for-peer-completion time in seconds. Validonly for duplexed structures. From R744SCST.

PEER_WAIT_SCH_NO FLOAT Count of waiting-for-peer-subchannel conditionsrequests. Valid only for duplexed structures. FromR744SPTC.

PEER_WAIT_SCH_SEC FLOAT Total peer-subchannel-wait time in seconds. Valid onlyfor duplexed structures. From R744SPST.

REQ_ASYNC_NO FLOAT Count of number of times for asynchronous requests.Calculated as the sum of R744SARC.

REQ_DELAYED_NO FLOAT Number of times requests were delayed due to dumpserialization. Calculated as the sum of R744SDRC.

REQ_DELAYED_SEC FLOAT Summed delay time for dump serialization, inmicroseconds. Calculated as the sum of R744SDTM.

REQ_DELAYED_SQ FLOAT Summed squares of delay time for dump serialization.Calculated as the sum of R744SDSQ.

REQ_FALSE_LOCK_NO FLOAT Number of times any request encountered false lockcontention (storage contention within the lock structure).Calculated as the sum of R744SFCN.

REQ_LOCK_NO FLOAT Number of times any request encountered lockcontention (lock structure only). Calculated as the sumof R744SCN.

REQ_QUEUED_NO FLOAT Count of number of times for queued requests.Calculated as the sum of R744SQRC.

REQ_SYNC_ASYNC FLOAT Number of requests changed from synchronous toasynchronous. Calculated as the sum of R744SSTA.

REQ_SYNC_NO FLOAT Count of number of times for synchronous requests.Calculated as the sum of R744SSRC.

REQ_WAIT_DUMP FLOAT Total number of requests waiting because dumpserialization is in progress. Calculated as the sum ofR744SDTO.

REQ_WAIT_DUMP_MAX FLOAT Maximum number of requests waiting because dumpserialization is in progress. Calculated as the maximumof R744SDMX.

REQ_WAIT_DUMP_MIN FLOAT Minimum number of requests waiting because dumpserialization is in progress. Calculated as the minimumof R744SDMN.

REQ_WAIT_LPRIO FLOAT Total number of requests waiting on the low priorityqueue. Calculated as the sum of R744SLTO.

REQ_WAIT_LPRIO_MAX FLOAT Maximum number of requests waiting on the lowpriority queue during the interval. Calculated as themaximum of R744SLMX.

REQ_WAIT_LPRIO_MIN FLOAT Minimum number of requests waiting on the lowpriority queue during the interval. Calculated as theminimum of R744SLMN.

REQ_WAIT_PRIO FLOAT Total number of requests waiting on the high priorityqueue. Calculated as the sum of R744SHTO.



|

|

|

|


REQ_WAIT_PRIO_MAX FLOAT Maximum number of requests waiting on the highpriority queue during the interval. Calculated as themaximum of R744SHMX.

REQ_WAIT_PRIO_MIN FLOAT Minimum number of requests waiting on the highpriority queue during the interval. Calculated as theminimum of R744SHMN.

SERVICE_ASYNC_SEC FLOAT Summed service time for asynchronous requests, inmicroseconds. Calculated as the sum of R744SATM.

SERVICE_ASYNC_SQ FLOAT Summed squares of service time for asynchronousrequests. Calculated as the sum of R744SASQ.

SERVICE_QUEUED_SEC FLOAT Summed service time for queued requests, inmicroseconds. Calculated as the sum of R744SQTM.

SERVICE_QUEUED_SQ FLOAT Summed squares of service time for queued requests.Calculated as the sum of R744SQSQ.

SERVICE_SYNC_SEC FLOAT Summed service time for synchronous requests, inmicroseconds. Calculated as the sum of R744SSTM.

SERVICE_SYNC_SQ FLOAT Summed squares of service time for synchronousrequests. Calculated as the sum of R744SSSQ.

STRUCTURE_SIZE_MB FLOAT Average allocated size of structure, in megabytes.Calculated as the average of R744QSIZ/256.

STRUCTURE_STATUS CHAR(2) Status flags: X'80'=structure was connected at the end ofthe interval; X'40'=structure became active during theinterval. Derived from R744SFLG.

STRUCTURE_TYPE CHAR(2) Structure type Identifier. Calculated as the maximum ofR744STYP.

SUBCH_CONTENTION FLOAT Subchannel contention count (all subchannels busy).From R744FSCC.





MVSPM_CF_LINK_HThis table provides information about the type of links allocated and used by aCoupling Facility. It contains data from SMF type 74, subtype 4 records.

The default period for this table is 10 days.


DATE k DATE Date of the mid measurement. From SMF74DAT,SMF74IST and SMF74INT.






LINK_TYPE k CHAR(8) Type of the channel path. It can be SUBCH or the typefrom R744FTAP.

LINK_GEN_NO INTEGER Number of links that are defined. From R744FPIS.

LINK_USE_NO INTEGER Number of links MVS is currently using for couplingfacility requests. Calculated as COUNT(R744FTAP).


SUBCH_GEN_NO INTEGER Number of subchannel links that are defined. FromR744FSCG.

SUBCH_USE_NO INTEGER Number of subchannel links MVS is currently using forcoupling facility requests. From R744FSCU.





|

||

|

|||||

|||||

||||||

||||||

||||

|||||

||||

|||||

||||

|||||

||||||

|||||

|||||

|||||

||||||

MVSPM_CF_TO_CF_HThis table provides data about CF to CF activity. It contains data from SMF type74, subtype 4 records.









PEER_CF k CHAR(8) Name of the remote coupling facility. From R744RNAM.

DELAY_TIME_SEC FLOAT Total signal delay times, in seconds. From R744RSDT.

LINKS_NO INTEGER The number of links used for coupling facilitycommunication. From R744RPGS.


REQ_READY_EXEC_NO FLOAT The number of ready to execute signals from subject CFto the remote CF. From R744RRES.

REQ_READY_COMP_NO FLOAT The number of ready to complete signals from subjectCF to the remote CF. From R744RRCS.

REQ_HALT_EXEC_NO FLOAT The number of halt execution signals from subject CF tothe remote CF. From R744RHES.

REQ_SUPPRESS_NO FLOAT The number of requests for suppression signals fromsubject CF to the remote CF. From R744RRSS.

REQ_ASUPPRESS_NO FLOAT The number of requests for suppression accepted signalsfrom subject CF to the remote CF. From R744RRSA.

REQ_DELAYED_NO FLOAT The number of signals of all types that have experienceda delay in being sent from a subject CF to this remoteCF. From R744RDSC.

SERVICE_TIME_SEC FLOAT Total signal service times, in seconds. From R744RSST.





|

||

|

|||||

|||||

||||||

||||||

||||

|||||

||||

||||

||||

|||||

||||||

|||||

|||||

|||||

|||||

|||||

||||||

||||

|||||

||||||

MVSPM_CHANNEL_HThis table provides statistics on channel path activity on MVS systems. It containsdata from SMF type 73 records—measurements related to MVS physical channelsthat were online during the measurement interval.





TIME k TIME Time (rounded down as specified in theMVSPM_TIME_RES lookup table) of the midmeasurement. From SMF73DAT, SMF73IST, andSMF73INT.



CHANNEL_PATH_ID k CHAR(2) Channel path ID. From SMF73PID.

BUSCYCLE FLOAT Average of bus cycle count when the measurementgroup number is 2. Calculated as the average ofSMF73TCB.

BUSCYCLE_MAX_SEC FLOAT Maximum bus cycles per second when themeasurement group number is 2. Calculated as themaximum value of SMF73MBC.

CHANNEL_BUSY_MAX FLOAT Maximum percentage of time that the channel path wasbusy during an RMF interval. Calculated as themaximum of SMF73BSY*100/SMF73SMP.

CHANNEL_BUSY_PCT FLOAT Average percentage of time that the channel path wasbusy. Calculated as the average ofSMF73BSY*100/SMF73SMP.

CHANNEL_BUSY_TOT FLOAT Total channel path busy time in seconds when themeasurement group number is 1. Calculated as the sumof SMF73TUT/7.8125.

CHANNEL_FLAGS CHAR(10) Channel flag bits. From SMF73FG3 and SMF73FG4.

Bit Meaning when set0 ES connection channel1 ES connection director attached to the channel

path2 ES connection converter attached to this

channel3 Channel path modified4 Channel path deleted5 Channel path added6 Valid channel path7 Channel path is shared between logical

partitions8 CPMB entry is not valid9 Channel path is channel-to-channel

CHANNEL_TYPE CHAR(8) Type of channel. From SMF73ACR.




CHAN_READ_MB_TOT FLOAT Channel read in MB when the measurement groupnumber is 2. Calculated as the sum ofSMF73TRU*(SMF73US/1024E3).

CHAN_UNIT_MAX_SEC FLOAT Maximum channel work units per second when themeasurement group number is 2. Calculated as themaximum value of SMF73MCU.

CHAN_UNIT_TOT FLOAT Total channel work unit count when the measurementgroup Number is 2. Calculated as the sum ofSMF73TUC.

CHAN_WRITE_MB_TOT FLOAT Channel write in MB when the measurement groupnumber is 2. Calculated as the sum ofSMF73TWU*(SMF73US/1024E3).

CPMF_BUSY_SEC FLOAT Logical partitions channel path busy time as measuredby the channel path measurement facility (CPMF), inseconds. Calculated as the sum of SMF73PBY*0.001 024.

CPMF_GROUP SMALLINT CPMF channel measurement group. From SMF73CMG.

CPMF_INTERVAL_SEC FLOAT Sum of the interval times as measured by the channelpath measurement facility (CPMF), in seconds.Calculated as the sum of SMF73PTI*0.001 024.

LPAR_CHAN_UNIT_TOT FLOAT LPAR channel work unit count when the measurementgroup number is 2. Calculated as the sum ofSMF73PUC.

LPAR_READ_MB_TOT FLOAT LPAR read in MB when the measurement groupnumber is 2. Calculated as the sum ofSMF73PRU*(SMF73US/1024E3).

LPAR_WRITE_MB_TOT FLOAT LPAR write in MB when the measurement groupnumber is 2. Calculated as the sum ofSMF73PWU*(SMF73US/1024E6).


PART_CHAN_BUSY_MAX FLOAT Maximum percentage of time that the channel path wasbusy for the partition. Calculated as the maximum ofSMF73PBY*100/SMF73PTI.

PART_CHAN_BUSY_PCT FLOAT Average percentage of time that the channel path wasbusy for the partition. Calculated as the average ofSMF73PBY*100/SMF73PTI.

PART_CHAN_BUSY_TOT FLOAT LPAR channel path busy time in seconds when themeasurement group number is 1. Calculated as the sumof SMF73PUT/7.8125.

READ_MB_MAX_SEC FLOAT Maximum read data units per second when themeasurement group number is 2. Calculated as themaximum value of SMF73MRU.

RECORD_LEVEL INTEGER SMF record level change number. This column enablesprocessing of SMF record level changes in an existingrelease. From SMF73SRL.

SAMPLES FLOAT Number of store channel path status (STCP) samplestaken by SRM. This is the sum of SMF73SMP.

SAMPLES_BUSY FLOAT Number of store channel path status (STCP) samplestaken by SRM in which the channel path related to thisentry was found busy. This is the sum of SMF73BSY.




TIME_RESOLUTION INTEGER Time resolution used for this table, in minutes. Thedefault is 60 minutes. From TIME_RESOLUTION in theMVSPM_TIME_RES lookup table.

WRITE_MB_MAX_SEC FLOAT Maximum write data units per second when themeasurement group number is 2. Calculated as themaximum value of SMF73MWU.



MVSPM_CLUSTER_HThis table provides hourly LPAR views as well as aggregated views on LPARcluster level. It contains data from SMF type 70 records processed through a recordprocedure (DRL2S070).


The default retention periods for this table are 10 days.






CLUSTER_NAME k CHAR(8) Cluster name associated with the partition. FromSMF70SPN.


SYSTEM_NAME k CHAR(8) z/OS System Name. From SMF70STN.

CENTRAL_STOR_FRAME INTEGER Central storage frames assigned to this partition.Calculated as mximum of SMF70CSF.

COMPLEX_SEC FLOAT Total processors complex time, in seconds.


CPU_DISPATCH_SEC FLOAT Logical processor dispatch time, in seconds. Calculatedas the sum of SMF70PDT/1 000 000.

EXPAND_STOR_FRAME INTEGER Expanded storage frames assigned to this partition.Calculated as maximum of SMF70ESF

LP_ACTUAL FLOAT Average number of CP logical processors active for thisLPAR during the interval. Calculated as the average ofSMF70BDA/SMF70DSA.

LP_DEFINED SMALLINT Number of logical processors assigned to the partition.From SMF70BDN.

LP_ONLINE_SEC FLOAT Total logical processor online seconds for this LPAR.Calculated as the sum of SMF70ONT/1000000.

MEASURED_SEC FLOAT Measured time period, in seconds. This is the durationof the RMF measurement intervals. From SMF70INT.

WEIGHT_ACT_AVG FLOAT Average weighting of the shared processor resources.Calculated as the average of SMF70ACS /SMF70DSA.

WEIGHT_ACT_MIN_PCT FLOAT Percentage of the time when the partition was within abandwidth of 10% above the minimum weighting.Calculated as average of 100*SMF70NSI /SMF70DSA.

WEIGHT_ACT_MAX_PCT FLOAT Percentage of the time when the partition was within abandwidth of 10% below the maximum weighting.Calculated as average of 100*SMF70NSA / SMF70DSA.



|

|||

|

|

|||||

|||||

|||||||

||||||

|||||

|||||

||||

||||

|||||

||||

||||

|||||

|||||

||||||

|||||

|||||

|||||

|||||

||||||

||||||


WEIGHT_DEF_INIT INTEGER Defined initial weighting of the shared processorresources. From SMF70BPS.

WEIGHT_DEF_MIN INTEGER Minimum weighting of the shared processor resources.Calculated as minimum of SMF70MIS.

WEIGHT_DEF_MAX INTEGER Maximum weighting of the shared processor resources.Calculated as maximum of SMF70MAS.



||||

|||||

|||||

|||||

MVSPM_CPU_HThis table provides statistics on processor activity. It contains data from SMF type70 records processed through a record procedure (DRL2S070).

This table is updated by the MVSPM_TIME_RES and by the MVS_MIPS_T lookuptables.




TIME k TIME Time (rounded down as specified in the MVSPM_TIME_RESlookup table) of the mid measurement. From SMF70DAT,SMF70IST, and SMF70INT.



CPU_ID k SMALLINT CPU ID. From SMF70CID.

CPU_BUSY_SEC FLOAT CPU busy time, in seconds. Calculated as SMF70INT/1000 −SMF70WAT/4 096 000 000. For a non-dedicated processor inLPAR mode, this is calculated as (SMF70EDT orSMF70PDT)/1 000 000 − SMF70WAT/4 096 000 000.

CPU_BUSY_MIPS FLOAT MIPS for single CPU. Calculated as(MIPS/SMF70BNP)*CPU_BUSY_SEC. MIPS is a column in theMVS_MIPS_T lookup table. SMF70BNP is the total number ofCPUs.

CPU_DISPATCH_SEC FLOAT Logical processor dispatch time, in seconds. This is the sum ofSMF70PDT.

CPU_EFF_DISP_SEC FLOAT Logical processor effective dispatch time (excluding LPARmanagement time), in seconds. This is the sum of SMF70EDT.


CPU_WAIT_SEC FLOAT CPU wait time, in seconds. This is set to zero if the CPU wasrun in LPAR mode and wait completion was not enabled. Thisis the sum of SMF70WAT.

CPU_WEIGHT FLOAT Partition processor resource factor. From SMF70BPS.

IO_INTERRUPTS FLOAT Number of I/O interrupts the processor handled by entry intothe I/O interrupt handler. This is the sum of SMF70SLH.


PROCESSOR_FLAGS CHAR(2) Logical processor flags. 80 = Wait state assist enabled; 40 =Wait state assist changed; 20 = Relative share changed; 10 =Partition capping is enabled; and 08 = Partition capping statuschanged. From SMF70VPF.


SAMPLES FLOAT Number of RMF samples taken. This is the sum ofSMF70SAM.



|


SYSPLEX_NAME CHAR(8) This is the name of the sysplex. From SMF70XNM.

SYSTEM_NAME CHAR(8) MVS system name. From SMF70SNM.

TIME_RESOLUTION SMALLINT Time resolution used for this table, in minutes. The default is60 minutes. From TIME_RESOLUTION in theMVSPM_TIME_RES lookup table.

TPI_INTERRUPTS FLOAT Number of I/O interrupts the processor handled as a result ofissuing the TPI instruction with a completion code of 1. This isthe sum of SMF70TPI.

VECTOR_SAMPLES FLOAT Number of samples taken when the vector bit was on. This isthe sum of SMF70VFS.



MVSPM_CRYPTO_PCI_HThis table provides hourly measurement data for cryptographic hardware (PCICryptographic Coprocessors and Accelerators) on an LPAR basis. It contains datafrom the new SMF type 70, subtype 2 records.








ID_INDEX k SMALLINT PCICC or PCICA index. From R7023AX (PCICC) orR7024AX (PCICA).

ID_TYPE k CHAR(8) Indicates PCI Cryptographic hardware and can assumetwo values:

v PCICC for Coprocessor

v PCICA for Accelerators

CRT_1024_OP_EX_SEC FLOAT Execution time for 1024-bit CRT-format RSA operations.It is valid only for PCICA. Calculated as sum ofR7021CRT*R7024SF.

CRT_1024_OP_EX_NUM FLOAT Execution number of 1024-bit CRT-format RSAoperations. It is valid only for PCICA. Calculated as sumof R7021CRC.

CRT_2048_OP_EX_SEC FLOAT Execution time for 2048-bit CRT-format RSA operations.It is valid only for PCICA. Calculated as sum ofR7022CRT*R7024SF.

CRT_2048_OP_EX_NUM FLOAT Execution number of 2048-bit CRT-format RSAoperations. It is valid only for PCICA. Calculated as sumof R7022CRC.


ME_1024_OP_EX_SEC FLOAT Execution time for 1024-bit ME-format RSA operations. Itis valid only for PCICA. Calculated as sum ofR7021MET*R7024SF.

ME_1024_OP_EX_NUM FLOAT Execution number of 1024-bit ME-format RSAoperations. It is valid only for PCIC. Calculated as sumof R7021MEC.

ME_2048_OP_EX_SEC FLOAT Execution time for 2048-bit ME-format RSA operations. Itis valid only for PCICA. Calculated as sum ofR7022MET*R7024SF.

ME_2048_OP_EX_NUM FLOAT Execution number of 2048-bit ME-format RSAoperations. It is valid only for PCICA. Calculated as sumof R7022MEC.



|

|||

|

|

|||||

|||||

|||||||

||||||

|||||

|||||

|||||

|

|

||||||

||||||

||||||

||||||

||||

||||||

||||||

||||||

||||||


MEASURED_SEC INTEGER Measured time period, in seconds. This is the durationof the RMF measurement intervals. From SMF70INT.

OPERATION_EX_NUM FLOAT Execution time of all operations on the specifiedHardware. Calculated as sum of:

v PCICC: R7023C0*R7023SF

v PCICA: (R7021MEC + R7022MET + R7021CRC +R7022CRC

OPERATION_EX_TIME FLOAT Execution time of all operations on the specifiedHardware. Calculated as sum of:

v PCICC: R7023T0*R7023SF

v PCICA: (R7021MET + R7022MET + R7021CRT +R7022CRT)*R7024SF

RSA_KEY_GEN_EX_NUM FLOAT Execution number of RSA-key-generation. It is valid forPCICC only. Calculated as sum of R7023C1.



||||

|||||

|||||

|

||

|||||

|

||

|||||

MVSPM_CRYPTO_CCF_HThis table provides hourly statistics measurement data for the cryptographiccoprocessor facility. It contains data from the new SMF type 70, subtype 2 records.








DES_ENCR_S_CALLS FLOAT Single DES: number of calls to encipher the data.Calculated as sum of R702SNEC.

DES_ENCR_S_BYTES FLOAT Single DES: number of bytes of data enciphered.Calculated as sum of R702SNEB.

DES_ENCR_S_CMDIN FLOAT Single DES: number of instructions used to encipher thedata. Calculated as sum of R702SNEI.

DES_ENCR_T_CALLS FLOAT Triple DES: number of calls to encipher the data.Calculated as sum of R702TNEC.

DES_ENCR_T_BYTES FLOAT Triple DES: number of bytes of data enciphered.Calculated as sum of R702TNEB.

DES_ENCR_T_CMDIN FLOAT Triple DES: number of instructions used to encipher thedata. Calculated as sum of R702TNEI.

DES_DECR_S_CALLS FLOAT Single DES: number of calls to decipher the data.Calculated as sum of R702SNDC.

DES_DECR_S_BYTES FLOAT Single DES: number of bytes of data deciphered.Calculated as sum of R702SNDB

DES_DECR_S_CMDIN FLOAT Single DES: number of instructions used to decipher thedata. Calculated as sum of R702SNDI

DES_DECR_T_CALLS FLOAT Triple DES: number of calls to decipher the data.Calculated as sum of R702TNDC.

DES_DECR_T_BYTES FLOAT Triple DES: number of bytes of data deciphered.Calculated as sum of R702TNDB.

DES_DECR_T_CMDIN FLOAT Triple DES: number of instructions used to decipher thedata. Calculated as sum of R702TNDI.

HASH_CALLS FLOAT Number of calls to hash the data. Calculated as sum ofR702NHAC.

HASH_BYTES FLOAT Number of bytes of data that were hashed. Calculated assum of R702NHAB.

HASH_PCMF FLOAT Number of PCMF instructions used to hash the data.Calculated as sum of R702NHAI.



|

||

|

|

|||||

|||||

|||||||

||||||

|||||

|||||

|||||

|||||

|||||

|||||

|||||

|||||

|||||

|||||

|||||

|||||

|||||

|||||

|||||

|||||



MAC_GENERATE_CALLS FLOAT Number of calls to generate the message authenticationcode (MAC). Calculated as sum of R702NMGC.

MAC_GENERATE_BYTES FLOAT Number of bytes of data for which the MAC wasgenerated. Calculated as sum of R702NMGB.

MAC_GENERATE_PCMF FLOAT Number of PCMF instructions used to generate theMAC. Calculated as sum of R702NMGI.

MAC_VERIFY_CALLS FLOAT Number of calls to verify the message authenticationcode (MAC). Calculated as sum of R702NMVC.

MAC_VERIFY_BYTES FLOAT Number of bytes of data for which the MAC wasverified. Calculated as sum of R702NMVB.

MAC_VERIFY_PCMF FLOAT Number of PCMF instructions used to verify the MAC.Calculated as sum of R702NMVI.

MEASURED_SEC INTEGER Measured time period, in seconds. This is the durationof the RMF measurement intervals. From SMF70INT.

PIN_TRANSLAT_CALLS FLOAT Number of calls to translate the PIN. Calculated as sumof R702NPTC.

PIN_VERIFY_CALLS FLOAT Number of calls to verify the PIN. Calculated as sum ofR702NPVC.



||||

||||

|||||

|||||

|||||

|||||

|||||

|||||

|||||

|||||

|||||

MVSPM_DATASET_HThis table provides DFSMS data set level I/O statistics. It contains data from SMFtype 42, subtype 6 records.

This table is updated by the MVSPM_TIME_RES and MVS_WORKLOAD_TYPElookup tables.



DATE k DATE Date of the mid measurement. From SMF42PTE andSMF42PTS.

TIME k TIME Time (rounded down as specified in theMVSPM_TIME_RES table) of the mid measurement.From SMF42PTE and SMF42PTS.

PERIOD_NAME k CHAR(8) Name of the period. This is derived using fieldsSMF42SID, SMF42PTE and SMF42PTS from the recordas parameters in the PERIOD function.


WORKLOAD_TYPE k CHAR(8) MVS workload type name. From WORKLOAD_TYPEin the MVS_WORKLOAD_TYPE lookup table.

JOBNAME k CHAR(8) Job name. From S42JDJNM.

DATASET_NAME k CHAR(44) Data set name. From S42DSN.

ACTIVE_SEC FLOAT Data set active time (interval end or close time minusinterval start or open time), in seconds. Calculated asthe sum of the time intervals from SMF42PTS toSMF42PTE.

AVG_IO_DEV_ACT FLOAT Average I/O device only for active time

CACHE_CANDIDATE FLOAT Number of cache candidates. Calculated as the sum ofS42SCCND.

CACHE_CANDIDATE_WR FLOAT Number of write candidates. Calculated as the sum ofS42SCWCN.

CACHE_HITS FLOAT Number of cache hits. Calculated as the sum ofS42SCHIT.

CACHE_WRITE_HITS FLOAT Number of write hits. Calculated as the sum ofS42SCWHI.

CLOSE_RECORDS INTEGER Count of close records. Calculated from S42JDCOD.

CONNECT_AVG_MSEC FLOAT Average connect time, in milliseconds. Calculated as theaverage of S42DSIOC/7.8125.

CU_QUEUE_AVG_MSEC FLOAT Average control unit queue time, in milliseconds.Calculated as the average of S42DSIOQ/7.8125.

DATASET_TYPE CHAR(7) Data set type. From S42DSTYP.

DISCONN_AVG_MSEC FLOAT Average disconnect time, in milliseconds. Calculated asthe average of S42DSIOD/7.8125.

FIRST_OPEN CHAR(1) First data set entry since open. Calculated fromS42DSCOD.


INT_RECORDS INTEGER Count of interval records. Calculated from S42JDCOD.




IO_COUNT FLOAT Total number of I/O operations. Calculated as the sumof S42DSION.

MAX_DS_RES_TIME FLOAT Maximum data set I/O response time

MAX_DS_SER_TIME FLOAT Maximum data set service time

NUM_DS_READ FLOAT Number of dataset read

NUM_DS_WRITE FLOAT Number of dataset written

OPEN_MOD CHAR Type of opening

PENDING_AVG_MSEC FLOAT Average pending time, in milliseconds. Calculated asthe average of S42DSIOP/7.8125.

PERF_GROUP_NO CHAR(3) Job performance group number. From S42JDPGN.

QUE_WAIT_AVG_MSEC FLOAT Average queue time, in milliseconds. Calculated as theaverage of (S42DSIOR - S42DSIOC - S42DSIOP -S42DSIOD)/7.8125.

RESPONSE_AVG_MSEC FLOAT Average data set response time, in milliseconds.Calculated as the average of S42DSIOR/7.8125.

SUBSYSTEM_ID CHAR(8) Subsystem identification. From SMF42SSI.




MVSPM_DEVICE_AP_HThis table provides statistics on the I/O activity per workload type for batch jobs,TSO sessions, started tasks, and APPC sessions. The data comes from SMF type 30,subtypes 2 and 3 records

This table is updated by the MVSPM_DEVICE_ADDR, MVSPM_TIME_RES,MVSPM_UNIT_TYPE, MVS_WORKLOAD_TYPE, and MVS_WORKLOAD2_TYPElookup tables.



DATE k DATE Date of the mid measurement. From SMF30IDT, SMF30IST,SMF30DTE, and SMF30TME (or SMF30ISS and SMF30IETaccording to the UPDATE definitions you have customized forlocal or GMT time).

TIME k TIME Time (rounded down as specified in the MVSPM_TIME_RESlookup table) of the mid measurement. From SMF30IDT,SMF30IST, SMF30DTE, and SMF30TME.

PERIOD_NAME k CHAR(8) Name of the period. This is derived using fields SMF30IDT,SMF30IST, SMF30DTE, and SMF30TME from the record asparameters in the PERIOD function.


WORKLOAD_TYPE k CHAR(8) MVS workload type name. From WORKLOAD_TYPE in theMVS_WORKLOAD_TYPE or MVS_WORKLOAD2_TYPElookup table.

DEVICE_NUM k CHAR(4) Device number (virtual I/O has device number X'7FFF'). FromDEVICE_Number in the MVSPM_DEVICE_ADDR lookuptable, or from SMF30CUA if no match is found in the lookuptable.

BLOCKS FLOAT Number of blocks transferred to or from the data set, or datasets if concatenation is used. This is the sum of SMF30BLK.

BLOCK_SIZE FLOAT Largest block size of the data set. This is the maximum ofSMF30BSZ.

CONNECT_MSEC FLOAT Device connect time for the data set, in milliseconds. For theDIV object, the device connect time is zero, except in certaincases. For example, if a user is using a DIV data set and callsa VSAM utility to process it using the same DD statement,this will result in a device connect time being charged byVSAM to the DIV object. Calculated as the sum ofSMF30DCT*0.128.

DEVICE_CLASS CHAR(4) Device class. From DEVICE_CLASS in theMVSPM_UNIT_TYPE lookup table.

INPUT_RECORDS FLOAT Number of input records collected from the input log.

SMF_INTERVAL FLOAT Duration of the SMF measurement intervals, in minutes.Calculated as SMF30DTE and SMF30TME, minus SMF30IDTand SMF30IST, divided by 60.


UNIT_TYPE CHAR(8) Unit type. From UNIT_TYPE in the MVSPM_UNIT_TYPElookup table.



MVSPM_DEVICE_HThis table provides statistics on the I/O activity of MVS devices. It contains dataon all devices that were active during an RMF monitor 1 session. The data comesfrom SMF type 74, subtype 1 records.

This table is updated by the MVSPM_DEVICE_ADDR, MVSPM_TIME_RES, andMVSPM_UNIT_TYPE lookup tables.




TIME k TIME Time of the mid measurement. From SMF74DAT,SMF74IST, and SMF74INT.



DEVICE_NUM k CHAR(4) Device number. From MVS_ADDR in theMVSPM_DEVICE_ADDR lookup table, or fromSMF74NUM if no match is found in the lookup table.

ACTIVE_MSEC FLOAT Device active time, in milliseconds. This is sum ofSMF74ATV*0.128.

ALLOCATED_TAPE_MAX FLOAT Maximum number of mounts detected. This is themaximum of SMF74MTC.

ALLOCATIONS FLOAT For RMF 3.5.1 releases and later, this is the total numberof allocations in effect for the device. For RMF releasesearlier than 3.5.1, this is the total number of data setsopen on the device. This is the sum of SMF74NDA andSMF74DSO.

CACHE_SUBSYSTEM_ID CHAR(4) 3990 control unit subsystem ID. FromCACHE_SUBSYSTEM_ID in theMVSPM_DEVICE_ADDR lookup tabel using SMF74SIDand SMF74LCU as lookup argument.

CONNECT_MSEC FLOAT Device connect time, in milliseconds. This is the sum ofSMF74CNN*0.128.

CU_BUSY_DELAY FLOAT Control unit busy delay time, in milliseconds. This is thesum of SMF74CUB*0.128.

CU_NAME CHAR(8) Control unit name. This column is blank if control unitname cannot be determined. From SMF74CU.

CYCLE_LENGTH_MSEC FLOAT RMF sampling cycle length, in milliseconds. FromSMF74CYC.

DEVICE_BUSY_DELAY FLOAT Device busy delay time, in milliseconds. This is fromsubchannel information block (SCHIB). This is the sumof SMF74DVB*0.128.

DEVICE_CLASS CHAR(5) Device class code. From DEVICE_CLASS in theMVSPM_UNIT_TYPE lookup table. This is derived usingfield SMF74TYP from the record as key.

DISCONN_MSEC FLOAT Device disconnect time, in milliseconds. This is the sumof SMF74DIS*0.128.




DPB_MSEC FLOAT Amount of time, in milliseconds, during themeasurement interval that I/O requests to a device weredelayed because a director port was busy. This is thesum of SMF74DPB.

FLAGS CHAR(2) Flags for the device class; 80 = number option active, 40= SG option active, 20 = SG name changed during theinterval, 10 = Open mount at interval start, 08 = Openmount at interval end. From SMF74CLF.


LCU_Number CHAR(4) Logical control unit number. From SMF74LCU.

MEASUREMENT_EVENTS FLOAT Measurement event count. This is the number of SSCHinstructions for which connect, pending, and active timeswere stored. This is the sum of SMF74MEC.

MOUNTS_DETECTED FLOAT Number of mounts detected. This is the sum ofSMF74MTC.

NUM_UCB_PAV FLOAT Number of unit control blocks (UCB) for PAV. This is thesum of SMF74NUX.

PAV_SUCC_SAMPLES FLOAT Number of unsuccessful PAV sample counts. FromSMF74PCT.

PAV_TIME_SKIPPED FLOAT Time skipped because of a dynamic change of aliasvolumes for PAV devices, in milliseconds. FromSMF74TMS.

PENDING_MSEC FLOAT Device pending time, in milliseconds. This is the sum ofSMF74PEN*0.128.


REQUESTS_QUEUED FLOAT Number of requests queued in the IOS for the device.This is the sum of SMF74QUE.

RMF_INTERVAL FLOAT Duration of the RMF measurement interval, in minutes.Calculated as SMF74INT/60000. If there is a dynamicchange of alias on a PAV device, it is calculated as(SMF74INT − SMF74TMS) / 60000.

SAMPLES FLOAT Number of RMF samples taken. This is calculated as thesum of SMF74SAM.

SAMPLES_ALLOCATED FLOAT Number of samples that indicated that the device wasallocated. This is the sum of SMF74ALC.

SAMPLES_MOUNT_PEND FLOAT Number of samples that indicated a mount pendingcondition. This is the sum of SMF74MTP.

SAMPLES_NOT_READY FLOAT Number of samples that indicated that the device wasnot ready. This is the sum of SMF74NRT.

SAMPLES_RSV FLOAT Number of samples taken when the device was reserved.This is the sum of SMF74RSV.

SAMPLES_UTL FLOAT Number of samples taken when the device was reservedbut an SSCH instruction had not been issued to thedevice. This is the sum of SMF74UTL.

SSCH_COUNT FLOAT Start subchannel count. This is the number of SSCHinstructions. This is the sum of SMF74SSC.

STORAGE_GROUP CHAR(8) Storage group name. From SMF74SGN.



||

|





UNIT_TYPE CHAR(8) Device model name or unit type. From SMF74DEV orfrom UNIT_TYPE in the MVSPM_UNIT_TYPE lookuptable if SMF74DEV is missing.

VOLSER CHAR(6) Volume serial of the volume mounted on the device(tape or direct access device only). From VOLSER in theMVSPM_DEVICE_ADDR lookup table, or fromSMF74SER if VOLSER is missing or no match is foundin the lookup table.



MVSPM_ENQUEUE_HThis table provides statistics on enqueue activity on MVS systems. It contains datafrom SMF type 77 records.








QUEUE_NAME k CHAR(8) Major queue name of the resource. From SMF77QNM.

CONTENTION_EVENTS FLOAT Total number of contention events that occurred. This isthe sum SMF77EVT.

CONTENTION_MAX_SEC FLOAT Maximum resource contention time, in seconds.Calculated as the maximum of SMF77WTX*0.001 024.

CONTENTION_TOT_SEC FLOAT Total resource contention time, in seconds. Calculatedas the sum of SMF77WTT*0.001 024.


RECORD_LEVEL SMALLINT SMF record level change number. This column enablesprocessing of SMF record level changes in an existingrelease. From SMF77SRL.

RMF_INTERVAL FLOAT Duration of the RMF measurement intervals, inminutes. Calculated as the maximum ofSMF77INT/60 000.





WAITING_REQUESTS FLOAT Total number of waiting requests. In MVS/XA™, this isthe sum of SMF77QLT; in MVS/ESA, it is the sum ofSMF77AQL.



MVSPM_FICON_HThis table provides statistics on FICON director. It contains data from the SMFtype 74, subtype 7 records.








SWITCH_DEVICE k INTEGER The switch device number of the FICON director forwhich measurements are being reported. FromR747SDEV.

SWITCH_ID k SMALLINT The switch ID number of the FICON director that isassociated with this switch device. From R747SLSN.

PORT_NUM k CHAR(2) The number of the port in hexadecimal format. FromR747PNUM.

PORT_ID k SMALLINT The port address. From R747PADR.

ERROR_PCT FLOAT The percentage of errors that occurred during theinterval.

FRAME_PACING_AVG FLOAT The average time (in seconds) a frame had to wait beforeit could be transmitted.

FRAME_READ_AVG FLOAT The average frame size (in bytes) used to receive dataduring the interval.

FRAME_WRITE_AVG FLOAT The average frame size (in bytes) used to transmit dataduring the interval.


PORT_BANDWIDTH_RD FLOAT The rate (in MB/sec) of data that was received duringthe interval.

PORT_BANDWIDTH_WR FLOAT The rate (in MB/sec) of data that was transmittedduring the interval.

PORT_TYPE CHAR(8) Port type can assume the following values: NOT_UNI(not unique), CU, and CHPID. From R747PTFL.



|

||

|

|

|||||

|||||

|||||||

||||||

|||||

||||||

|||||

|||||

||||

|||||

|||||

|||||

|||||

||||||

|||||

|||||

|||||

MVSPM_GOAL_ACT_HThis table provides statistics on MVS response time goals and actuals by workloadtype and service class. It contains data from SMF type 72, subtype 3 records.

This table is updated by the MVS_WORKLOAD2_TYPE and MVSPM_TIME_RESlookup tables.




TIME k TIME Time (rounded down as specified in theMVSPM_TIME_RES table) of the mid measurement. FromSMF72DAT, SMF72IST, and SMF72INT.







GOAL_PERCENTAGE k SMALLINT Defines the maximum percentage of a goal (for example, 50,70, 200). From R723TRDB.

AVERAGE_GOAL_SEC FLOAT Average response time goal, in seconds. From R723CVAL(converted to seconds using R723CRTF) if R723CRGF isequal to X'40', otherwise set to 0.

GOAL_FLAG SMALLINT Zero if percentile response time goal, one if averageresponse time goal. From R723CRGF.

GOAL_IMPORTANCE SMALLINT Relative importance of the goal to be achieved for thisservice class period (1=highest, 5=lowest). Calculated as themaximum of R723CIMP.

GOAL_PERCENTILE SMALLINT Percentile response time goal, in percent. From R723CPCT ifR723CRGF is equal to X'80', otherwise set to 0.

PERCENT_GOAL_SEC FLOAT Percentile response time goal, in seconds. From R723CVAL(converted to seconds using R723CRTF) if R723CRGF isequal to X'80', otherwise set to 0. GOAL_PERCENTILEpercent of all transactions should be completed withinPERCENT_GOAL_SEC seconds.

REPORT_PERIOD_FLAG CHAR(1) Report class period flag: 1=Heterogeneous class (more thanone service class for the same report class), 0=Homogeneousreport class period (only one service class for this reportclass). Blank if this is a service class period. FromR723CRS1.

SERV_CLASS_TYPE CHAR(1) Service Class (SC) type. This can be C (control) or R(reporting). All data in reporting SCs is also reported in acontrol SC. So, when summaries are produced, only controlSCs should be selected. From R723MSCF.




|

|

|


SERVICE_POLICY CHAR(8) Service policy name. From R723MNSP.


SYSPLEX_NAME CHAR(8) Sysplex name (as defined in ECVTSPLX). From SMF72XNM.

SYSTEM_NAME CHAR(8) System name for current system (as defined inCVTSNAME). From SMF72SNM.


TRANSACTIONS INTEGER Number of transactions that ended within X percent of theresponse time goal. X is the value in columnGOAL_PERCENTAGE. This is the sum of R723TRDB.



|

MVSPM_HS_CHAN_HThis table provides statistics on HyperSockets channel path activity on MVSsystems. It contains data from SMF type 73 records measurements related to MVSphysical channels that were online during the measurement interval.

This table is updated by the MVSPM_TIME_RES lookup tables.







CHANNEL_PATH_ID k CHAR(2) Channel path ID. From SMF73PID.

CPMF_GROUP SMALLINT CPMF channel measurement group. From SMF73CMG.

CPMF_INTERVAL_SEC FLOAT sum of the interval times as measured by the channel pathmeasurement facility (CPMF), in seconds. Calculated as thesum of SMF73PTI*0.001024.

CHAN_LPAR_WRITE_RT FLOAT Channel partition write rate for HiperSockets. Calculated asthe average of SMF73PDS*SMF73PDU/(SMF73PTI*0.001024).

CHAN_TOT_WRITE_RT FLOAT Channel total write rate for HiperSockets. Calculated as theaverage of SMF73TDS*SMF73TDU/ (SMF73PTI*0.001024).

CHAN_LPAR_MSG_S_RT FLOAT Channel partition message sent rate. Calculated as theaverage of SMF73PMS*SMF73PUM/ (SMF73PTI*0.001024).

CHAN_TOT_MSG_S_RT FLOAT Channel total message sent rate. Calculated as the averageof SMF73TMS*SMF73TUM/ (SMF73PTI*0.001024).

CHAN_LPAR_MSG_SIZE FLOAT Average Channel partition message size (in bytes).Calculated as the average of SMF73PDS*SMF73PDU/SMF73PMS/SMF73PUM.

CHAN_TOT_MSG_SIZE FLOAT Average Channel total message size (in bytes). Calculated asthe average of SMF73TDS*SMF73TDU/SMF73TMS/SMF73TUM.

CHAN_LPAR_SND_FAIL FLOAT Channel partition message send failed rate. Calculated asthe average of SMF73PUS/ (SMF73PTI*0.001024).

CHAN_LPAR_RCV_FAIL FLOAT Channel partition message receive failed rate. Calculated asthe average of SMF73PUB/ (SMF73PTI*0.001024).

CHAN_TOT_RCV_FAIL FLOAT Channel total receive failed rate. Calculated as the averageof SMF73TUB/ (SMF73PTI*0.001024).

CHANNEL_FLAGS CHAR(10) Channel flag bits. From SMF73FG3 and SMF73FG4.

CHANNEL_TYPE CHAR(8) Type of channel. From SMF73ACR.

MEASURED_SEC FLOAT Measured time period, in seconds. This is the duration ofthe RMF measurement intervals. Calculated as the sum ofSMF73INT/1000.



|

|||

|

|

|||||

|||||

||||||

||||||

||||

||||

||||

||||||

||||||

|||||

|||||

|||||

||||||

||||||

|||||

|||||

|||||

||||

||||

||||||






||||

||||||

||||||

MVSPM_LPAR_HThis table provides statistics on logical partitions and processor activity in aPR/SM environment. It contains data from SMF type 70 records processed througha record procedure (DRL2S070).






PERIOD_NAME k CHAR(8) Name of the period. This is derived using fieldsSMF70DAT, SMF70IST, and SMF70INT from the record asparameters in the PERIOD function.



PROCESSOR_TYPE k CHAR(3) Name of the logical processor type (CP for generalpurpose processor or ICF for integrated couplingprocessor). From SMF70CIX.

CAPACITY_LIMIT_MSU FLOAT Defined capacity limit of the partition in MSUs per hour.A value of 0 indicates that the partition is not undercontrol of the License Manager. From SMF70MSU.

CENTRAL_STOR_FRAME INTEGER Central storage frames assigned to this partition.Calculated as maximum of SMF70CSF.

COMPLEX_SEC FLOAT Total processor complex time, in seconds. Processors CPand ICF are considered separately.


CPU_BUSY_MIPS FLOAT Virtual processor busy MIPS time, in seconds. Calculatedas the sum of (SMF70PDT/1000000.)* MIPS_PER_LPAR

CPU_DISPATCH_SEC FLOAT Logical processor dispatch time, in seconds. Calculated asthe sum of SMF70PDT/1 000 000.

CPU_EFF_DISP_SEC FLOAT Logical processor effective dispatch time (excluding LPARmanagement time), in seconds. Calculated as the sum ofSMF70EDT/1 000 000.


CPU_SERIAL_NO CHAR(5) Last 4 digits of the CPU serial number. From SMF70SER.

CPU_WAIT_SEC FLOAT Processor wait time, in seconds. This is set to zero if theprocessor was run in LPAR mode and wait completionwas not enabled. Calculated as the sum ofSMF70WAT/4 096 000 000.

DEDICAT_PROC_LPAR SMALLINT Number of dedicated processor for this LPAR. Calculatedas the maximum of LPDEDICF (ICF) or LPDEDCP (CP).



|

|

|

|

|

|

|


DEDICATED_PROC_IND SMALLINT Indicates whether the partition has been assigned one ormore dedicated processors; 1 = yes, 0 = no. FromSMF70BPS.

DISPATCH_INTERVAL FLOAT Dispatch interval time, in seconds. A zero value indicatesthat the interval was dynamically determined. Calculatedas the sum of SMF70GTS/1000.

EXPAND_STOR_FRAME INTEGER Expanded storage frames assigned to this partition.Calculated as maximum of SMF70CSF.

FROM_LPAR_NO SMALLINT Number of the logical partition that wrote the record.From SMF70PTN.

LOGICAL_PROCESSORS SMALLINT Number of logical processors assigned to the partition.From SMF70BDN.

LPAR_FLAGS CHAR(2) LPAR flags. 80 = Partition deactivated during interval, 40= Number of logical processors changed. FromSMF70PFG.

LPAR_NO SMALLINT Number of the logical partition. From SMF70LPN.

LPAR_WEIGHT INTEGER Logical partition processor resource weight factor. Thiscolumn is set to zero if the weight factor is X'FFFF'. FromSMF70BPS.

LPAR_WEIGHT_TOT INTEGER Sum of all partition processor resource weight factors.This is calculated by the record procedure DRL2S070.From TOTCPWGT for CP and from TOTICFWGT for ICFprocessors.

LPROC_CP_SHARED FLOAT Average number of CP logical processors active for thisLPAR during the interval. From LPSHRCP. For z/OSsystem with WLM active is the average ofSMF70BDA/SMF70DSA.

LPROC_ICF_SHARED FLOAT Average number of ICF logical processors active for thisLPAR during the interval. From LPSHRICF. For z/OSsystem with WLM active is the average ofSMF70BDA/SMF70DSA.

LP_ONLINE_SEC FLOAT Total logical processor online seconds for this LPAR. FromSMF70INT/1000. For z/OS system is SMF70ONT/1000000.

LPROC_SEC FLOAT Available logical processor time, in seconds. This is thetime available for all nondedicated processors. ProcessorsCP and ICF are considered separately.

MEASURED_SEC FLOAT Measured time period, in seconds. This is the duration ofthe RMF measurement intervals. From SMF70INT/1000.


MIPS_PER_LPAR FLOAT Total number of MIPS per LPAR. The number of MIPS istaken from a specific Look Up table MVS_MIPS_T

NONDED_PROCESSORS SMALLINT Total number of processors that were not assigned asdedicated in the processor complex. Processors CP andICF are considered separately

NUM_CONsumED_MSU FLOAT Actual number of consumed MSUs. Calculated assum(SMF70PDT)*3600*16 /(SMF70CPA*SMF70INT*1000).

PHYS_PROCESSORS SMALLINT Total number of physical processors (CP+ICF) assignedfor use by PR/SM. From TOTCPPRO+TOTICFPRO.



|

|

|

|

|

|

|

|

|

|

|

|


PHY_PROCESORS_CP SMALLINT Total number of CP physical processors assigned for useby PR/SM. From TOTCPPRO.

PHY_PROCESSORS_ICF SMALLINT Total number of ICF physical processors assigned for useby PR/SM. From TOTICFPRO.


PROCESSOR_FLAGS CHAR(2) Logical processor flags. 80 = Wait state assist enabled; 40= Wait state assist changed; 20 = Relative share changed;10 = Partition capping is enabled; and 08 = Partitioncapping status changed. From SMF70VPF.

PRSM_FLAGS CHAR(2) PR/SM flags. 80 = Diagnose X'204' failure; 40 = numberof physical processors changed; 20 = Global time slicevalue changed; 10 = PHYSICAL partition included. FromSMF70INB.



WEIGHT_ACTUAL FLOAT Actual weighting of the shared processor resources. Validonly for z/OS system with WLM active. Calculated as theaverage of SMF70ACS / SMF70DSA.

WLM_CAPPING_PCT FLOAT Percentage of WLM capping of the partition. Calculatedas the maximum of (SMF70NSW/SMF70DSA) * 100.



|

|

|

MVSPM_OMVS_BUF_HThis table provides information about OpenEdition buffers. It contains data fromSMF type 74, subtype 6 records.







BUFF_POOL FLOAT Total size of buffer pool, in MB. This is the sum ofR746GSBP/256.

BUFF_POOL_FIX FLOAT Total size of permanently-fixed buffers in the bufferpool, in MB. This is the sum of R746GSBF/256.

BUFF_POOL_IOFIX FLOAT Total number of buffers that are already fixed in thebuffer pool prior to an I/O request. This is the sum ofR746GBF.

BUFF_POOL_IONFIX FLOAT Total number of buffers that are not already fixed inthe buffer pool prior to an I/O request. This is thesum of R746GBNF.

BUFFER_NUM FLOAT Total number of buffers. This is the sum ofR746GSBP/R746GSB.

BUFFER_SIZE_MAX FLOAT Maximum size of buffers in buffer pool, in MB. This isthe maximum value of R746GSB/256.

BUFFER_SIZE_MIN FLOAT Minimum size of buffers in buffer pool, in MB. This isthe minimum value of R746GSB/256.

DATASPACE_AVG FLOAT Average value of dataspace used for buffer pool. Thisis the average of R746GNDS.


MEASURED_SEC FLOAT Measured time period, in seconds. This is the durationof the RMF measurement intervals. This is the sum ofSMF74INT/1000.

TIME_RESOLUTION SMALLINT The time resolution used for this table, in minutes.The default is 60 minutes. From TIME_RESOLUTIONin the MVSPM_TIME_RES lookup table.



MVSPM_OMVS_FILE_HThis table provides information data about hourly OpenMVS file activity. Itcontains data from SMF type 92, subtypes 10 and 11 records. I/O informationabout a single file is provided only when the file is closed.



DATE k DATE Date of the mid measurement. From SMF92DTE.

TIME k TIME Time (rounded down as specified in theMVSPM_TIME_RES table) of the mid measurement.From SMF92DTE and SMF92TME.

PERIOD_NAME k CHAR(8) Name of the period. This is derived using fieldsSMF92SID and SMF92DTE from the record asparameters in the PERIOD function.


JOB_NAME k CHAR(8) Job name. From SMF92JBN.

JOB_STEPNAME k CHAR(8) Job step name. From SMF92STM.

OPEN_TOKEN k INTEGER Open file token. It can be used to correlate open andclose records. From SMF92OTK or SMF92CTK.

FILE_NUM k INTEGER For each file system, a unique identifier for a file. Fileserial Numbers are unique throughout a file system.From SMF92CIN or SMF92OIN.

DEVICE_NUM k INTEGER A unique identifier for the file system. FromSMF92CDN or SMF92ODN.

SESSION_ID k INTEGER A unique identifier for the session. From SMF92SSD.

PROCESS_ID k INTEGER A unique identifier for the process. From SMF92PID.

PROCESS_GID k INTEGER A unique identifier for the group process. FromSMF92PGD.

FILE_DIR_BLK FLOAT Total number of directory I/O blocks read. This is thesum of SMF92CDI.

FILE_PATHNAME CHAR(64) File pathname. From SMF92CPN.

FILE_READ FLOAT Total number of read calls issued to the file. This isthe sum of SMF92CSR.

FILE_READ_BLK FLOAT Total number of I/O blocks read. This is the sum ofSMF92CIR.

FILE_READ_KB FLOAT Total number of KB read. This is the sum ofSMF92CBR/1024.

FILE_TYPE SMALLINT File type as defined in BPXYFTYP. From SMF92CTY orSMF92OTY.

FILE_WRITE FLOAT Total number of write calls issued to the file. This isthe sum of SMF92CSW.

FILE_WRITE_BLK FLOAT Total number of I/O blocks written. This is the sum ofSMF92CIW.

FILE_WRITE_KB FLOAT Total number of KB written. This is the sum ofSMF92CBW/1024.

RACF_GROUP CHAR(8) RACF group ID. From SMF92RGD.

RACF_USER_ID CHAR(8) RACF user ID. From SMF92RUD.




TIME_OPEN FLOAT Total open time file. This is either the sum of theinterval between SMF92CTC and SMF92CTO or thesum of the interval between SMF92CTC andSMF92OTO.



MVSPM_OMVS_GHFS_HThis table provides information about I/O activity of all hierarchical file systems. Itcontains data from SMF type 74, subtype 6 records.







FILE_IO_CACHE FLOAT Total number of times that the first page of a data filewas requested and found in virtual storage (cache).This is the sum of R746G1C.

FILE_IO_DASD FLOAT Total number of times that the first page of a data filewas requested and not found in virtual storage, andan I/O was necessary. This is the sum of R746G1NC.

FIXED_STG INTEGER Minimum value of fixed storage. This is the minimumvalue of R746GMNF.

FIXED_STG_USED FLOAT Total value of permanently-fixed storage used, in MB.This is the sum of R746GUSF/256.


METADATA_IO_CACHE FLOAT Total number of times that the metadata for a file wasfound in virtual storage (cache) during file lookup.This is the sum of R746GMC.

METADATA_IO_DASD FLOAT Total number of times that the metadata for a file wasnot found in virtual storage and an I/O was necessary.This is the sum of R746GMNC.


VIRTUAL_STG INTEGER Maximum value of virtual storage. This is themaximum value of R746GMXV.

VIRTUAL_STG_USED FLOAT Total value of virtual storage used, in MB. This is thesum of R746GUSV/256.



MVSPM_OMVS_HFS_HThis table provides information about the OpenMVS hierarchical file system (HFS).It contains data from SMF type 74, subtype 6 records.







FILE_SYSTEM_NAME k CHAR(44) The file system name (cataloged data set name). FromR746FSNM.

BUFF_CACHED_MB FLOAT Total of data buffer storage in MB cached by this filesystem. This is the sum of R746FPC/256.

FILE_CACHE FLOAT The number of the first page of a data file that wasrequested and found in virtual storage (cache). This isthe sum of R746F1C.

FILE_LOOKUP_CACHE FLOAT The number of metadata for a file that was found invirtual storage (cache) during file lookup. This is thesum of R746FMC.

FILE_LOOKUP_NCACHE FLOAT The number of metadata for a file that was not foundin virtual storage (cache) during file lookup. This isthe sum of R746FMNC.

FILE_NCACHE FLOAT The number of the first page of a data file that wasrequested and not found in virtual storage (cache) andan I/O was necessary. This is the sum of R746F1NC.

FS_ATTRIBUTE_DIR FLOAT Total of storage in MB used for the attribute directory.This is the sum of R746FPD/256.

FS_DATA_MB FLOAT Total of storage in MB used internally within HFS fordata files, directories, and HFS internal structures, forexample, the attribute directory (AD). This is the sumof R746FSP/256.

FS_SYSTEM_MB FLOAT Size of storage in MB allocated to this file system. Thisis the sum of R746FSF/256.

INDEX_JOINS FLOAT The number of times that HFS was able to combinetwo index pages into one, because enough indexrecords had been deleted in the two pages. This is thesum of R746FIJ.

INDEX_NEW_LEVEL FLOAT The number of times that HFS added a new level toits index structure. This is the sum of R746FINT.

INDEX_SPLITS FLOAT The number of times that an index page was split intotwo pages because new records were inserted. This isthe sum of R746FIS.

INDEX_READ_HITS FLOAT Number of index page read hits. This is the sum ofR746FIRH.




INDEX_READ_MISSES FLOAT Number of index page read misses. This is the sum ofR746FIRM.

INDEX_WRITE_HITS FLOAT Number of index page write hits. This is the sum ofR746FIWH.

INDEX_WRITE_MISSES FLOAT Number of index page write misses. This is the sum ofR746FIWM.



RANDOM_IO_REQ FLOAT An I/O that does not read or write the start of a file,and was not preceded by an I/O that read or wrotethe immediately preceding set of bytes. This is thesum of R746FRFI.

SEQUENTIAL_IO_REQ FLOAT Series of I/Os, where the first I/O started at the firstbyte of the file and each subsequent I/O was for thenext set of bytes. This is the sum of R746FSFI.




MVSPM_OMVS_KERN_HThis table provides data about OpenMVS kernel activity. It contains data from SMFtype 74, subtype 3 records.







CPU_MAX FLOAT Maximum CPU time spent processing syscalls inOpenMVS system during one cycle (in seconds). Thisis the sum of R743CTMX.

CPU_MIN FLOAT Minimum CPU time spent processing syscalls inOpenMVS system during one cycle (in seconds). Thisis the sum of R743CTMN.

CYCLE_MAX INTEGER Maximum number of cycle units elapsed between thefirst and last measured sample. This is the maximumvalue of R743CYCU.

CYCLE_MIN INTEGER Minimum number of cycle units elapsed between thefirst and last measured sample. This is the minimumvalue of R743CYCU.

CYCLE_TIME_MIN INTEGER Minimum cycle time value obtained from the RMFMonitor III option. This is the minimum value ofR743CYCT.

CYCLE_TIME_MIN INTEGER Maximum cycle time value obtained from the RMFMonitor III option. This is the maximum value ofR743CYCT.

CYCLE_TOTAL FLOAT Total number of cycle units for the measured time.This is the sum of R743CYCU.

FORKDUB_PROC_MAX INTEGER Maximum number of times that Fork/Dub failedbecause the maximum number of processes wasexceeded during one cycle. This is the maximum valueof R743OPMX.

FORKDUB_PROC_MIN INTEGER Minimum number of times that Fork/Dub failedbecause the maximum number of processes wasexceeded during one cycle. This is the minimum valueof R743OPMN.

FORKDUB_PROCUS_MAX INTEGER Maximum number of times that Fork/Dub failedbecause the maximum number of processes per userwas exceeded during one cycle. This is the maximumvalue of R743ORMX.

FORKDUB_PROCUS_MIN INTEGER Minimum number of times that Fork/Dub failedbecause the maximum number of processes per userwas exceeded during one cycle. This is the minimumvalue of R743ORMN.




FORKDUB_TOT_PROCUS FLOAT Count of the times that Fork/Dub failed because themaximum number of processes per user was exceededduring one cycle. This is the sum of R743OPRU.

FORKDUB_TOTAL_PROC FLOAT Count of the times that Fork/Dub failed because themaximum number of processes was exceeded duringone cycle. This is the sum of R743OPR.

FORKDUB_TOTAL_USER FLOAT Count of the times that Fork/Dub failed because themaximum number of users was exceeded during onecycle. This is the sum of R743OOUS.

FORKDUB_USER_MIN INTEGER Minimum number of times that Fork/Dub failedbecause the maximum number of users was exceededduring one cycle. This is the minimum value ofR743OUMN.

FORKDUB_USER_MAX INTEGER Maximum number of times that Fork/Dub failedbecause the maximum number of users was exceededduring one cycle. This is the maximum value ofR743OUMX.



MSGQUEUE_EXCEED FLOAT Total number of attempts to exceeded maximumnumber of message queue IDs during the interval.This is the sum of R743OMSG.

MSGQUEUE_MAX FLOAT Maximum number of message queue IDs. This is themaximum value of R743MMSG.

MSGQUEUE_TOTAL FLOAT Total number of message queue IDs during theinterval. This is the sum of R743CMSG.

MSGQUEUE_MAX_CYCLE FLOAT Maximum number of message queue IDs per cycle.This is the maximum value of R743CMMX.

MSGQUEUE_MIN_CYCLE FLOAT Minimum number of message queue IDs per cycle.This is the minimum value of R743CMMN.

MSGQUEUE_MIN_EXC FLOAT Minimum number of attempts to exceeded maximumnumber of message queue IDs per cycle. This is theminimum value of R743OMMN.

MSGQUEUE_MAX_EXC FLOAT Maximum number of attempts to exceededmaximumNumber of message queue IDs per cycle.This is the maximum value of R743OMMX.

MMAPPG_EXCEED FLOAT Total number of attempts to exceededmaximumNumber of memory map storage pagesduring the interval. This is the sum of R743OMAP.

MMAPPG_MAX FLOAT Maximum amount of memory map storage in MB.This is the maximum value of R743MMAP/256.

MMAPPG_MAX_CYCLE FLOAT Maximum amount of memory map storage in MB percycle. This is the maximum value of R743CAMX/256.

MMAPPG_MAX_EXCEED FLOAT Maximum number of attempts to exceeded maximumnumber of memory map storage pages per cycle. Thisis the maximum value of R743OAMX.

MMAPPG_MIN_CYCLE FLOAT Minimum amount of memory map storage in MB percycle. This is the minimum value of R743CAMN/256.




MMAPPG_MIN_EXCEED FLOAT Minimum number of attempts to exceeded maximumnumber of memory map storage pages per cycle. Thisis the minimum value of R743OAMN.

MMAPPG_TOTAL FLOAT Total amount of memory map storage in MB duringthe cycle. This is the sum of R743CMAP/256.

PROCESS_MAX SMALLINT Maximum number of OMVS processes as defined inparameter maximum PROCSYS ofSYS1.PARMLIB(BPXPRMxx). This is the first value ofR743 maximum P.

PROC_USER_MAX SMALLINT Maximum number of OMVS processes per user asdefined in parameter maximum PROCUSER ofSYS1.PARMLIB(BPXPRMxx). This is the first value ofR743MXPU.

PROCESS_AVG FLOAT Average number of OMVS processes during theinterval. This is the average of R743CURP.

PROCESS_MAX_CYCLE SMALLINT Maximum number of OMVS processes during onecycle. This is the maximum value of R743CPMX.

PROCESS_MIN_CYCLE SMALLINT Minimum number of OMVS processes during onecycle. This is the minimum value of R743CPMN.

QUESIG_MAX_ALLOWED FLOAT Maximum amount of queued signals allowed perprocess. Calculated as the maximum value ofR743MQDS.

QUESIG_MAX_EXCEED FLOAT Maximum number of attempts to exceed maximumamount of queued signals per cycle. Calculated as themaximum value of R743OQMX.

QUESIG_MIN_EXCEED FLOAT Minimum number of attempts to exceed maximumamount of queued signals per cycle. Calculated as theminimum value of R743OQMN.

QUESIG_SUM_EXCEED FLOAT Accumulated number of attempts to exceed maximumamount of queued signals per interval. Calculated asthe sum of R743OQDS.

SYSTEM_CALL_MIN FLOAT Minimum number of OpenMVS system calls duringone cycle. This is the minimum value of R743SCMN.

SYSTEM_CALL FLOAT Total number of OpenMVS system calls. This is thesum of R743SYSC.

SYSTEM_CALL_MAX FLOAT Maximum number of OpenMVS system calls duringone cycle. This is the maximum value of R743SCMX.

SEMAPH_TOTAL FLOAT Total number of semaphore IDs during the interval.This is the sum of R743CSEM.

SEMAPH_EXCEED FLOAT Total number of attempts to exceeded maximumnumber of semaphore IDs during the interval. This isthe sum of R743OSEM.

SEMAPH_MAX FLOAT Maximum number of semaphore IDs. This is themaximum value of R743MSEM.

SEMAPH_MAX_CYCLE FLOAT Maximum number of semaphore IDs per cycle. This isthe maximum value of R743CSMX.

SEMAPH_MIN_CYCLE FLOAT Minimum numbernumber of semaphore IDs per cycle.This is the minimum value of R743CSMN.




SEMAPH_MAX_EXC FLOAT Maximum number of attempts to exceededmaximumNumber of semaphore IDs per cycle. This isthe maximum value of R743OSMX.

SEMAPH_MIN_EXC FLOAT Minimum numbernumber of attempts to exceededmaximum number of semaphore IDs per cycle. This isthe minimum value of R743OSMN.

SHRLRE_MAX_STORAGE FLOAT Maximum amount of storage (MB) available for theshared library region. Calculated as the maximumvalue of R743MSLR.

SHRLRE_SUM_ALLOC FLOAT Accumulated amount of shared library storage (MB)allocated in one interval. Calculated as the maximumvalue of R743CSLR.

SHRLRE_MIN_ALLOC FLOAT Minimum amount of shared library storage (MB)allocated per cycle. Calculated as the maximum valueof R743CLMN.

SHRLRE_MAX_ALLOC FLOAT Maximum amount of shared library storage (MB)allocated per cycle. Calculated as the maximum valueof R743CLMX.

SHRLRE_SUM_EXCEED FLOAT Accumulated number of attempts to exceed maximumamount of shared library region size during oneinterval. Calculated as the sum of R743OSLR.

SHRLRE_MAX_EXCEED FLOAT Maximum number of attempts to exceed maximumamount of shared library region size per cycle.Calculated as the maximum value of R743OLMX.

SHRLRE_MIN_EXCEED FLOAT Minimum number of attempts to exceed maximumamount of shared library region size per cycle.Calculated as the minimum value of R743OLMN.

SHRMID_MAX FLOAT Maximum number of shared message IDs. This is themaximum value of R743MSHM.

SHRMPG_MAX FLOAT Maximum number of shared memory pages. This isthe maximum value of R743MSPG.

SHRMID_TOTAL FLOAT Total number of shared memory IDs during theinterval. This is the sum of R743CSHM.

SHRMID_MIN_CYCLE FLOAT Minimum number of shared memory IDs per cycle.This is the minimum value of R743CHMN.

SHRMID_MAX_CYCLE FLOAT Maximum number of shared memory IDs per cycle.This is the maximum value of R743CHMX.

SHRMID_EXCEED FLOAT Total number of attempts to exceeded maximumnumber of shared memory IDs during the interval.This is the sum of R743OSHM.

SHRMID_MAX_EXC FLOAT Maximum number of attempts to exceeded maximumnumber of shared memory IDs per cycle. This is themaximum value of R743OHMX.

SHRMID_MIN_EXC FLOAT Minimum number of attempts to exceeded maximumnumber of shared memory IDs per cycle. This is theminimum value of R743OHMN.

SHRMPG_MIN_CYCLE FLOAT Minimum amount of shared memory in MB per cycle.This is the minimum value of R743CGMN/256.

SHRMPG_EXCEED FLOAT Total number of attempts to exceeded maximumnumber of shared memory pages during the interval.This is the sum of R743OSGM.




SHRSPG_MAX FLOAT Maximum number of shared storage pages. This is themaximum value of R743MPAG.

SHRMPG_MAX_EXC FLOAT Maximum number of attempts to exceeded maximumnumber of shared memory pages per cycle. This is themaximum value of R743OGMX.

SHRMPG_MAX_CYCLE FLOAT Maximum amount of shared memory in MB per cycle.This is the maximum value of R743CGMX/256.

SHRMPG_MIN_EXC FLOAT Minimum number of attempts to exceeded maximumnumber of shared memory pages per cycle. This is theminimum value of R743OGMN.

SHRMPG_TOTAL FLOAT Total amount of shared memory in MB during theinterval. This is the sum of R743CSPG/256.

SHRSPG_TOTAL FLOAT Total amount of shared storage in MB during theinterval. This is the maximum value ofR743CPAG/256.

SHRSPG_MIN_CYCLE FLOAT Minimum amount of shared storage in MB per cycle.This is the minimum value of R743CXMN/256.

SHRSPG_MAX_CYCLE FLOAT Maximum amount of shared storage in MB per cycle.This is the maximum value of R743CXMX/256.

SHRSPG_EXCEED FLOAT Total number of attempts to exceeded maximumnumber of shared storage pages during the interval.This is the sum of R743OPAG.

SHRSPG_MIN_EXCEED FLOAT Minimum number of attempts to exceeded maximumnumber of shared storage pages per cycle. This is theminimum value of R743OXMN.

SHRSPG_MAX_EXCEED FLOAT Maximum number of attempts to exceeded maximumnumber of shared storage pages per cycle. This is themaximum value of R743OXMX.

TIME_RESOLUTION SMALLINT The time resolution used for this table in minutes. Thedefault is 60 minutes. From TIME_RESOLUTION inthe MVSPM_TIME_RES lookup table.

TOTAL_CPU FLOAT Total CPU time spent processing syscalls in OpenMVSsystem (in seconds). This is the sum of R743CPU.

USER_AVG FLOAT Average number of OMVS users during the interval.This is the average of R743CURU.

USER_MAX SMALLINT Maximum number of OMVS users as defined inparameter maximum UIDS ofSYS1.PARMLIB(BPXPRMxx). This is the first value ofR743MAXU.

USER_MAX_CYCLE SMALLINT Maximum number of OMVS users during one cycle.This is the maximum value of R743CUMX.

USER_MIN_CYCLE SMALLINT Minimum number of OMVS users during one cycle.This is the minimum value of R743CUMN.



MVSPM_OMVS_MOUNT_HThis table provides data about hourly OpenMVS file system activity. It containsdata from SMF type 92, subtypes 4, 5 and 6 records. I/O information about afully-mounted file system is provided only when the file system is unmounted.



DATE k DATE Date of the mid measurement. From SMF92DTE.

TIME k TIME Time (rounded down as specified in theMVSPM_TIME_RES table) of the mid measurement.From SMF92DTE and SMF92TME.

PERIOD_NAME k CHAR(8) Name of the period. This is derived using fieldsSMF92SID and SMF92DTE from the record asparameters in the PERIOD function.

SYSTEM_ID k CHAR(4) MVS system identification. From SMF92SID.

FILESYS_NAME k CHAR(44) File system name. From SMF92RFN for subtype 4 orSMF92UFN for subtypes 5 and 6.

FILESYS_ALLOC_MIN FLOAT Minimum file system allocated space in blocks.Minimum value from SMF92USU.

FILESYS_ALLOC_MAX FLOAT Maximum file system allocated space in blocks.Maximum value from SMF92USU.

FILESYS_DIR_BLK FLOAT Total number of file system I/O directory blocks. Thisis the sum of SMF92UDI.

FILESYS_FREE_MIN FLOAT Minimum file system free space in blocks. Minimumvalue from SMF92UST.

FILESYS_FREE_MAX FLOAT Maximum file system free space in blocks. Maximumvalue from SMF92UST.

FILESYS_READ READ Total number of file system read calls that are issued.This is the sum of SMF92USR.

FILESYS_TYPE CHAR(8) File system type name. From SMF92RTN for subtype 4or SMF92UTN for subtypes 5 and 6.

FILESYS_WRITE READ Total number of file system write calls that are issued.This is the sum of SMF92USW.

FILESYS_READ_BLK FLOAT Total number of file system I/O read blocks. This isthe sum of SMF92UIR.

FILESYS_WRITE_BLK FLOAT Total number of file system I/O write blocks. This isthe sum of SMF92UIW.

FILESYS_READ_KB FLOAT Total number of file system I/O read kilobytes. This isthe sum of SMF92UBR/1024.

FILESYS_WRITE_KB FLOAT Total number of file system I/O write kilobytes. Thisis the sum of SMF92UBW/1024.

QUIESCE INTEGER Total number of times that the file system is quiesced.Count from input records 92 subtype 4.

REMOUNT INTEGER Total number of remount commands that are issued.Count from input records 92 subtype 6.

TIME_MOUNT FLOAT Total time in seconds that the file system wasmounted. This is the sum of the differences betweentime unmounted from SMF92UTU and time mountedfrom SMF92UTM.




TIME_QUIESCE FLOAT Total time in minutes that the file system wasunavailable. This is the sum of the differences betweentime resumed from SMF92RTR and time suspendedfrom SMF92RTS.

UNMOUNT INTEGER Total number of unmount commands that are issued.Count from input records 92 subtype 5.



MVSPM_PAGE_DS_HThis table provides statistics on page data set and swap data set activities on MVSsystems. It contains data from SMF type 75 records.

This table is updated by the MVSPM_TIME_RES and MVSPM_UNIT_TYPE lookuptables.







DEVICE_Number k CHAR(4) Device number for the page data set. From SMF75CHA.

PAGE_SPACE_TYPE k CHAR(6) Type of page data set. This can be PLPA, COMMON,LOCAL, or SWAP. From SMF75PST.

DATASET_NAME k CHAR(44) Name of the page or swap data set. From SMF75DSN.

COMMON_IND SMALLINT Indicates whether the data set is a common page data set.This is set to 1 if it is COMMON; 0 if not. From SMF75PST.

CU_NAME CHAR(8) Control unit name. This column is blank if the control unitname cannot be determined. From SMF75CU.

DATASET_BUSY_SEC FLOAT Time that the page data set was busy, in seconds. Thisincludes the estimated queue time. Calculated as the sumof((SMF75USE*SMF75CYC/1000)*SMF75SAM)/(SMF75SAM− SMF75USE).

DATASET_FLAGS CHAR(1) Page data set flags. Bit 0 = data set accepts VIO pages; bit1 = data set is on a multiple-exposure device; bit 2 = dataset is on a device with an alternate control unit; bit 3 =SMF75DEV contains a valid device name. From SMF75FL2.

DATASET_USED_SEC FLOAT Time that the page data set was being used by theauxiliary storage manager, in seconds. Calculated as thesum of SMF75USE*SMF75CYC/1000.


IO_REQUESTS FLOAT Number of I/O requests for the page data set. This is thesum of SMF75SIO.

LOCAL_IND SMALLINT Indicates whether the data set is a local page data set. Thisis set to 1 if it is LOCAL; 0 if not. From SMF75PST.

MEASURED_SEC FLOAT Measured time period, in seconds. This is the sum of theRMF measurement intervals. Calculated as the sum ofSMF75INT/60 000.

PAGES_TRANSFERRED FLOAT Number of pages transferred to or from the page data set.This is the sum of SMF75PGX.




PLPA_IND SMALLINT Indicates whether the data set is a PLPA data set. This isset to 1 if it is PLPA; 0 if not. From SMF75PST.


RMF_INTERVAL FLOAT Duration of the RMF measurement intervals, in minutes.Calculated as SMF75INT/60 000.


SAMPLES_BUSY FLOAT Number of samples indicating that the page data set wasbeing used by the auxiliary storage manager. This is thesum of SMF75USE.

SAMPLES_REQUEST FLOAT Number of requests for the data set observed during RMFsampling. For single-exposure devices, this is the same asSAMPLES_BUSY. For multiple-exposure devices, this is thesum of all outstanding requests on all exposures. This isthe sum of SMF75REQ.

SLOTS_USED_AVG FLOAT Number of slots used. For page data sets, this is the sumof SMF75AVU. For swap data sets, this is calculated as thesum of SMF75AVU*12.

SWAP_IND SMALLINT Indicates whether the data set is a swap data set. This isset to 1 if it is SWAP; 0 if not. From SMF75PST.




UNIT_TYPE CHAR(8) Device model name or unit type. From SMF75DEV or fromUNIT_TYPE in the MVSPM_UNIT_TYPE lookup table ifSMF75DEV is missing.

VOLSER CHAR(6) Volume serial number of the volume mounted on thedevice. From SMF75VOL.



MVSPM_PAGING_HThis table provides statistics on paging activity on MVS systems. It contains datafrom SMF type 71 records.

This table is updated by the MVSPM_TIME_RES lookup tables.







BLOCKS_IN FLOAT Number of blocks that were paged in. This is the sumof SMF71BLK.

CSTOR_AVAILABLE_MB FLOAT Average number of unused (available) central (real)storage, in megabytes. Calculated as the average ofSMF71AVF/256.

CSTOR_CSA_MB FLOAT Average size of the CSA in central (real) storage, inmegabytes. Calculated as the average ofSMF71AVP/256.

CSTOR_LPA_MB FLOAT Average size of the LPA in central (real) storage, inmegabytes. Calculated as the average ofSMF71ALP/256.

CSTOR_LSQA_MB FLOAT Average LSQA size in central (real) storage, inmegabytes. Calculated as the average ofSMF71ALR/256.

CSTOR_PRIVATE_MB FLOAT Average pageable address space in central (real) storagein the private address space, in megabytes. Calculatedas the average of SMF71AVS/256.

CSTOR_SQA_MB FLOAT Average SQA size in central (real) storage, in megabytes.Calculated as the average of SMF71ASR/256.

ESTOR_AVAILABLE_MB FLOAT Average size of unused (available) expanded storage, inmegabytes. Calculated as the average ofSMF71ASA/256.

ESTOR_CSA_MB FLOAT Average size of the CSA in expanded storage, inmegabytes. Calculated as the average ofSMF71CAE/256.

ESTOR_HIPER_AVG_MB FLOAT Average expanded storage used for hiperspace pages, inmegabytes. Calculated as the average ofSMF71AHE/256.

ESTOR_HIPER_MAX_MB FLOAT Maximum expanded storage used for hiperspace pages,in megabytes. Calculated as the maximum ofSMF71XHE/256.




ESTOR_HIPER_MIN_MB FLOAT Minimum expanded storage used for hiperspace pages,in megabytes. Calculated as the minimum ofSMF71MHE/256.

ESTOR_LPA_MB FLOAT Average LPA size in expanded storage, in megabytes.Calculated as the average of SMF71LAE/256.

ESTOR_LSQA_MB FLOAT Average LSQA size in expanded storage, in megabytes.Calculated as the average of SMF71ALE/256.

ESTOR_ONL_MAX_MB FLOAT Maximum size of online expanded storage, inmegabytes. Calculated as the maximum ofSMF71OLE/256.

ESTOR_PRIVATE_MB FLOAT Average private area in expanded storage, in megabytes.Calculated as the average of SMF71RAE/256.

ESTOR_SQA_MB FLOAT Average SQA size in expanded storage, in megabytes.Calculated as the average of SMF71ASE/256.

ESTOR_VIO_AVG_MB FLOAT Average expanded storage used for VIO pages, inmegabytes. Calculated as the average ofSMF71AVE/256.

ESTOR_VIO_MAX_MB FLOAT Maximum expanded storage used for VIO pages, inmegabytes. Calculated as the maximum ofSMF71XVE/256.

ESTOR_VIO_MIN_MB FLOAT Minimum expanded storage used for VIO pages, inmegabytes. Calculated as the minimum ofSMF71MVE/256.

FPAGES_SHR_B16_AVG FLOAT Average number of shared page groups fixed below 16MB in the system. This is the average of SMF71AGB.

FPAGES_SHR_B16_MAX FLOAT Maximum number of shared page groups fixed below16 MB in the system. This is the maximum ofSMF71XGB.

FPAGES_SHR_B16_MIN FLOAT Minimum number of shared page groups fixed below16 MB in the system. This is the minimum ofSMF71MGB.

FPGS_16M_TO_2G_MIN FLOAT Minimum number of pages fixed between 16 MB and 2GB (ESAME mode). From SMF71MFB.

FPGS_16M_TO_2G_MAX FLOAT Maximum number of pages fixed between 16 MB and 2GB (ESAME mode). From SMF71XFB.

FPGS_16M_TO_2G_average FLOAT Average number of pages fixed between 16 MB and 2GB (ESAME mode). From SMF71AFB.

FRAMES_AV_CS_MIN FLOAT Minimum number of available central storage frames.This is from SMF71CAM.

FRAMES_AV_CS_MAX FLOAT Maximum number of available central storage frames.This is from SMF71CAX.

FRAMES_AV_CS_AVG FLOAT Average number of available central storage frames.This is from SMF71CAA.

FRAMES_LI_CS_MIN FLOAT Minimum number of low-impact central storage frames.This is from SMF71CLM.

FRAMES_LI_CS_MAX FLOAT Maximum number of low-impact central storage frames.This is from SMF71CLX.

FRAMES_LI_CS_AVG FLOAT Average number of low-impact central storage frames.This is from SMF71CLA.




FRAMES_MI_CS_MIN FLOAT Minimum number of medium-impact central storageframes. This is from SMF71CMM.

FRAMES_MI_CS_MAX FLOAT Maximum number of medium-impact central storageframes. This is from SMF71CMX.

FRAMES_MI_CS_AVG FLOAT Average number of medium-impact central storageframes. This is from SMF71CMA.

FRAMES_HI_CS_MIN FLOAT Minimum number of high-impact central storageframes. This is from SMF71CHM.

FRAMES_HI_CS_MAX FLOAT Maximum number of high-impact central storageframes. This is from SMF71CHX.

FRAMES_HI_CS_AVG FLOAT Average number of high-impact central storage frames.This is from SMF71CHA.

FRAMES_AV_ES_MIN FLOAT Minimum number of available expanded storageframes. This is from SMF71EAM.

FRAMES_AV_ES_MAX FLOAT Maximum number of available expanded storageframes. This is from SMF71EAX.

FRAMES_AV_ES_AVG FLOAT Average number of available expanded storage frames.This is from SMF71EAA.

FRAMES_LI_ES_MIN FLOAT Minimum number of low-impact expanded storageframes. This is from SMF71ELM.

FRAMES_LI_ES_MAX FLOAT Maximum number of low-impact expanded storageframes. This is from SMF71ELX.

FRAMES_LI_ES_AVG FLOAT Average number of low-impact expanded storageframes. This is from SMF71ELA.

FRAMES_MI_ES_MIN FLOAT Minimum number of medium-impact expanded storageframes. This is from SMF71EMM.

FRAMES_MI_ES_MAX FLOAT Maximum Number of medium-impact expandedstorage frames. This is from SMF71EMX.

FRAMES_MI_ES_AVG FLOAT Average number of medium-impact expanded storageframes. This is from SMF71EMA.

FRAMES_HI_ES_MIN FLOAT Minimum number of high-impact expanded storageframes. This is from SMF71EHM.

FRAMES_HI_ES_MAX FLOAT Maximum number of high-impact expanded storageframes. This is from SMF71EHX.

FRAMES_HI_ES_AVG FLOAT Average number of high-impact expanded storageframes. This is from SMF71EHA.

FRAMES_FREED_ES FLOAT Number of frames freed in expanded storage withoutmigration. This is the sum of SMF71FNM.

FSTOR_COMMON_MB FLOAT Average fixed frames in the common area (CSA andLPA), in megabytes. Calculated as the average ofSMF71AVC/256.

FSTOR_LPA_MB FLOAT Average size of fixed LPA storage, in megabytes.Calculated as the average of SMF71ALF/256.

FSTOR_LSQA_MB FLOAT Average size of LSQA fixed storage, in megabytes.Calculated as the average of SMF71ALS/256.

FSTOR_LT16MB FLOAT Average size of fixed storage below 16 megabytes, inmegabytes. Calculated as the average ofSMF71AVL/256.




FSTOR_PRIVATE_MB FLOAT Average non-LSQA fixed frames in the private addressspace, in megabytes. Calculated as the average ofSMF71AVR/256.

FSTOR_SQA_MB FLOAT Average size of SQA fixed storage, in megabytes.Calculated as the average of SMF71AVQ/256.

HIGH_UIC_AVG FLOAT Average high unreferenced interval count, in seconds.Calculated as the average of SMF71ACA/10.

HS_PAGES_FROM_ES FLOAT Total number of hiperspace pages read from expandedstorage. This is the sum of SMF71HRE.


LOGICAL_SWAPS FLOAT Total number of logical swaps directed to auxiliarystorage. Calculated as the sum of SMF71AXD +SMF71LAX + SMF71MIG.

MEASURED_SEC FLOAT Measured time period, in seconds. This is the durationof the RMF measurement intervals. This is the sum ofSMF71INT.

MIGRATION_AGE FLOAT Average migration age, in seconds. This is the time anunreferenced page remains in expanded storage beforeit is migrated to auxiliary storage. Calculated as theaverage of SMF71AMA/10.

PAGE_RECLAIMS_VIO FLOAT Number of virtual I/O page reclaims. This includespage reclaims required through a VIO request that wassatisfied without page-in through the explicit VIOreclaim interface. This is the sum of SMF71VRC.

PAGEINS FLOAT Number of non-VIO, nonswap page-ins. This includespage-ins required through page faults, specific pagerequests, and page fixes. It does not include pagereclaims, page-ins for VIO data sets, and pages swappedin. This is the sum of SMF71PIN.

PAGEINS_BLOCK FLOAT Number of blocked pages that were paged in. This doesnot include VIO or hiperspace pages. This is the sum ofSMF71BLP.

PAGEINS_COMMON FLOAT Number of non-VIO page-ins performed in the commonarea (LPA and CSA). This is the sum of SMF71SNI.

PAGEINS_HIPER FLOAT Number of hiperspace page-ins. This is the sum ofSMF71HIN.

PAGEINS_LPA FLOAT Number of non-VIO, nonswap page-ins performed inthe link pack area. This is the sum of SMF71LNI.

PAGEINS_SHARED FLOAT Number of page-ins from auxiliary storage for sharedpage groups. This is the sum of SMF71ASI.

PAGEINS_SHARED_ES FLOAT Number of page-ins from expanded storage for sharedpage groups. This is the sum of SMF71ESI.

PAGEINS_VIO FLOAT Number of virtual I/O page-ins. This includes page-insresulting from page faults or specific page requests on aVIO window. It does not include VIO swap-ins orpage-ins for the common area. This is the sum ofSMF71VIN.

PAGEOUTS FLOAT Number of non-VIO, nonswap page-outs. This includespage-outs required through specific page requests, andpages stolen by the paging supervisor throughinfrequent use. This is the sum of SMF71POT.




PAGEOUTS_COMMON FLOAT Number of non-VIO page-outs performed in thecommon area (LPA and CSA). This is the sum ofSMF71SNO.

PAGEOUTS_HIPER FLOAT Number of hiperspace page-outs. This is the sum ofSMF71HOT.

PAGEOUTS_SHARED FLOAT Number of page-outs to auxiliary storage for sharedpage groups. This is the sum of SMF71ASO.

PAGEOUTS_SHARED_ES FLOAT Number of page-outs to expanded storage for sharedpage groups. This is the sum of SMF71ESO.

PAGEOUTS_VIO FLOAT Number of virtual I/O page-outs. This includespage-outs resulting from specific page requests on aVIO window, and those pages stolen by the pagingsupervisor through infrequent use. This is the sum ofSMF71VOT.

PAGES_HIPER_TO_ES FLOAT Total number of hiperspace pages written to expandedstorage. This is the sum of SMF71HME.

PAGES_MIGR_HIPER FLOAT Total number of hiperspace pages migrated fromexpanded storage to auxiliary storage. This is the sumof SMF71HMG.

PAGES_MIGRATED_PWS FLOAT Number of primary working-set pages migrated fromexpanded storage. This is the sum of SMF71PWS.

PAGES_MIGRATED_TOT FLOAT Total number of pages migrated from expanded storageto auxiliary storage. This is the sum of SMF71PEA.

PAGES_MIGRATED_VIO FLOAT Total number of VIO pages migrated from expandedstorage. This is the sum of SMF71VMG.

PAGES_MOVED_ES FLOAT Total number of pages moved to expanded storage. Thisis the sum of SMF71PES.

PAGES_MOVED_TOT FLOAT Total number of pages moved. This is the sum ofSMF71PMV.

PAGES_READ_ES FLOAT Total number of pages read from expanded storage.This is the sum of SMF71RES.

PAGES_READ_VIO FLOAT Total number of VIO pages read from expanded storage.This is the sum of SMF71VRE.

PAGES_SHARED_AVG FLOAT Average number of shared page groups in the system.This is the average of SMF71AGT.

PAGES_SHARED_MAX FLOAT Maximum number of shared page groups in the system.This is the maximum of SMF71XGT.

PAGES_SHARED_MIN FLOAT Minimum number of shared page groups in the system.This is the minimum of SMF71MGT.

PAGES_SHR_CS_AVG FLOAT Average number of shared page groups in the centralstorage. This is the average of SMF71AGC.

PAGES_SHR_CS_MAX FLOAT Minimum number of shared page groups in the centralstorage. This is the maximum of SMF71XGC.

PAGES_SHR_CS_MIN FLOAT Minimum number of shared page groups in the centralstorage. This is the minimum of SMF71MGC.

PAGES_SHR_ES_AVG FLOAT Average number of shared page groups in the expandedstorage. This is the average of SMF71AGE.

PAGES_SHR_ES_MAX FLOAT Maximum number of shared page groups in theexpanded storage. This is the maximum of SMF71XGE.




PAGES_SHR_ES_MIN FLOAT Minimum number of shared page groups in theexpanded storage. This is the minimum of SMF71MGE.

PAGES_SHR_FIX_AVG FLOAT Average number of shared page groups fixed in thesystem. This is the average of SMF71AGF.

PAGES_SHR_FIX_MAX FLOAT Maximum number of shared page groups fixed in thesystem. This is the maximum of SMF71XGF.

PAGES_SHR_FIX_MIN FLOAT Minimum number of shared page groups fixed in thesystem. This is the minimum of SMF71MGF.

PAGES_SWAPPED_IN FLOAT Number of pages swapped in from auxiliary storage.This includes LSQA, fixed pages, and those pages thatthe storage manager determined to be active when theaddress space was swapped in. It does not include pagereclaims. This is the sum of SMF71SIN.

PAGES_SWAPPED_OUT FLOAT Number of pages swapped out to auxiliary storage. Thisincludes LSQA, private area fixed pages, and privatearea nonfixed changed pages. This is the sum ofSMF71SOT.

PAGES_VIO_TO_ES FLOAT Total number of VIO pages written to expanded storage.This is the sum of SMF71VME.



RSTORE_VIO_PG_MIN FLOAT Minimum number of VIO pages in real storage (ESAMEmode). From SMF71MVI.

RSTORE_VIO_PG_MAX FLOAT Maximum Number of VIO pages in real storage(ESAME mode). From SMF71XVI.

RSTORE_VIO_PG_AVG FLOAT Average Number of VIO pages in real storage (ESAMEmode). From SMF71AVI.

RSTORE_HYS_PG_MIN FLOAT Minimum number of hiperspace pages in real storage(ESAME mode). From SMF71MHI.

RSTORE_HYS_PG_MAX FLOAT Mximum number of hiperspace pages in real storage(ESAME mode). From SMF71XHI.

RSTORE_VIO_PG_WRT FLOAT Number of VIO pages written to real storage (ESAMEmode). From SMF71VWS.

RSTORE_VIO_PG_RDN FLOAT Number of VIO pages read from real storage (ESAMEmode). From SMF71VRS.

RSTORE_HYS_PG_WRT FLOAT Number of hiperspace pages written to real storage(ESAME mode). From SMF71HWS.

RSTORE_HYS_PG_RDN FLOAT Number of hiperspace pages read from real storage(ESAME mode). From SMF71HRS.


SLOTS_SHR_AUX_AVG FLOAT Average number of auxiliary slots in use for sharedpage groups. This is the average of SMF71AGA.

SLOTS_SHR_AUX_MAX FLOAT Maximum number of auxiliary slots in use for sharedpage groups. This is the maximum of SMF71XGA.




SLOTS_SHR_AUX_MIN FLOAT Minimum number of auxiliary slots in use for sharedpage groups. This is the minimum of SMF71MGA.

STOR_NUCLEUS_MB FLOAT Average size of the nucleus, in megabytes. Calculated asthe average of SMF71FIN/256.

SWAP_SEQUENCES FLOAT Number of address space swap sequences. (A swapsequence consists of an address space swap-out andswap-in.) This is the sum of SMF71SSQ.






MVSPM_RAID_RANK_HThis table provides hourly statistics and information about a redundant array ofindependent disks (RAID) rank, that is, a group of drives managed by the diskarray controller and configured to work as a defined set of host I/O operations. Itshows the physical characteristics of a RAID rank and the details for READ andWRITE requests.




DATE k DATE Date of the mid measurement. From SMFxDTE,SMFxTME, and R745CINT.

TIME k TIME Time (rounded down as specified in theMVSPM_TIME_RES lookup table) of the midmeasurement. From SMFxDTE, SMFxTME, andR745CINT.

PERIOD_NAME k CHAR(8) Name of the period. This is derived using fieldsSMFxDTE, SMFxTME, and R745CINT from the recordas parameters in the PERIOD function.


DEVICE_Number k CHAR(4) The ESA/390 term for a 4-character hexadecimalidentifier, for example, X'13A0'associated with a deviceto facilitate communication between the program andthe host operator. The device number is associated withthe subchannel. From R7451DVN.

RAID_RANK_ID k INTEGER RAID rank ID. From R7451RID.

DEVICE_ADAPTER_ID INTEGER ID of a physical subunit of a storage server thatprovides the facilities to attach to one or moreinterfaces that are used to communicate with theassociated storage devices. From R7451AID.

HDD_SECTOR_SIZE INTEGER Sector size of hard disk drive (HDD). Calculated as thefirst occurrences of R7451HSS.

INPUT_RECORDS INTEGER Number of SMF records collected during the timeperiod specified in the TIME_RESOLUTION column.

LOW_IO_RESP_TIME FLOAT Lower interface I/O response time, in seconds.Calculated as the minimum value of R7451RSV/1000.

MEASURED_SEC FLOAT Measured time period, in seconds. This is the sum ofthe RMF measurement intervals. Calculated as the sumof R745CINT.

NUM_HD_DRIVES INTEGER Number of HDDs in RAID rank. Calculated as the firstoccurrences of R7451HDD.

NVS_SPACE_ALLOCMAX FLOAT Maximum space allocated for nonvolatile storage.Calculated as the maximum value of R7451NVS.

RAID_TYPE CHAR(8) RAID rank type. It can assume one of the followingvalues: RAID-5, JBOD, and RAID0/1. From R7451RTY.

RECORD_MODE_READ_R FLOAT Record mode read requests. Calculated as the sum ofR7451RMR.

RR_FB_SECTOR_READ FLOAT FB sectors read for RAID rank. Calculated as the sumof R7451SR.



|

|

|

|


RR_FB_SECTOR_WRITE FLOAT FB sectors written for RAID rank. Calculated as thesum of R7451SW.

RR_READ_REQUESTS FLOAT Read requests of RAID rank. Calculated as the sum ofR7451RRQ.

RR_READ_RESP_TIME FLOAT Read response time of RAID rank, in seconds.Calculated as the sum of R7451RRT.

RR_WRITE_REQUESTS FLOAT Write requests of RAID rank. Calculated as the sum ofR7451WRQ.

RR_WRITE_RESP_TIME FLOAT Write response time of RAID rank, in seconds.Calculated as the sum of R7451WRT.


TRKS_TO_SEC_PPRC_V FLOAT Number of tracks transferred to secondary volume ofPeer-to-Peer-Remote-Copy (PPRC). Calculated as thesum of R7451TSP.

XRC_CC_CONTA_WRITE FLOAT Contaminated writes for Extended-Remote-Copy (XRC)or Concurrent-Copy (CC). Calculated as the sum ofR7451XCW.

XRC_CC_SF_READ_REQ FLOAT Read requests for XRC or CC side file. Calculated asthe sum of R7451XSF.



MVSPM_STORAGE_HThis table provides statistics on MVS storage activity by workload type andperformance group. It contains data from SMF type 72, subtype 2 records.

This table is updated by the MVS_WORKLOAD_TYPE and MVSPM_TIME_RESlookup tables.







WORKLOAD_TYPE k CHAR(8) MVS workload type name. From WORKLOAD_TYPE inthe MVS_WORKLOAD_TYPE lookup table.

PERF_GROUP_NO k CHAR(3) Performance group number. From R722PG.

ACTIVE_FRAMES_TOT FLOAT Number of all active frames. This is the sum ofR722ACTF.

ACTIVE_SAMPLES FLOAT Number of all active samples taken. This is the sum ofR722ACTS.

ACTIVE_USERS_TOT FLOAT Number of all active users found. This is the sum ofR722ACTV.


DIV_FRAMES_TOT FLOAT Number of all data-in-virtual frames used. This is thesum of R722DIV.

DIV_SAMPLES FLOAT Number of all data-in-virtual samples taken. This is thesum of R722DIVS.

ESTOR_IND CHAR(1) Indicates whether the system has expanded storage; 1 =yes, 0 = no. From the first bit of SMF72PRF.

FIXED_FRAMES_TOT FLOAT Number of all fixed frames held by users. This is thesum of R722FIX.

IDLE_FRAMES_TOT FLOAT Number of all idle frames. This is the sum of R722IDLE.

IDLE_SAMPLES FLOAT Number of all idle samples taken. This is the sum ofR722IDLS.


OUTREADY_USERS_TOT FLOAT Number of all out and ready samples taken. This is thesum of R722OUTR.

PAGEDEL_USERS_TOT FLOAT Number of users delayed for paging. This is the sum ofR722PAGE.

PAGEINS FLOAT Number of page-ins. This is the sum of R722PGIN.






SLOTS_USED FLOAT Number of auxiliary-storage slots used. This is the sumof R722SLOT.

SWAPDEL_USERS_TOT FLOAT Number of users delayed for swapping. This is the sumof R722SWAP.



TIME_RESOLUTION SMALLINT Time resolution used for this table, in minutes. Thedefault is 60 minutes. From TIME_RESOLUTION inMVSPM_TIME_RES lookup table.

USERS_TOT FLOAT Number of all users found. This is the sum ofR722USER.



MVSPM_STORCLASS_HThis table provides DFSMS storage class I/O statistics. It contains data from SMFtype 42, subtype 5 records.






PERIOD_NAME k CHAR(8) Name of the period. This is derived using fieldsSMF42SID, SMF42PTE and SMF42PTS from therecord as parameters in the PERIOD function.


STORAGE_CLASS k VARCHAR(32) Storage class name. From S42SCNAM.

CACHE_CANDIDATE FLOAT Number of cache candidates. Calculated as the sumof S42SCCND.

CACHE_CANDIDATE_WR FLOAT Number of write candidates. Calculated as the sumof S42SCWCN.

CACHE_HITS FLOAT Number of cache hits. Calculated as the sum ofS42SCHIT.

CACHE_WRITE_HITS FLOAT Number of write hits. Calculated as the sum ofS42SCWHI.

CONNECT_AVG_MSEC FLOAT Average connect time, in milliseconds. Calculated asthe average of S42SCIOC/7.8125.

CU_QUEUE_AVG_MSEC FLOAT Average control unit queue time, in milliseconds.Calculated as the average of S42SCIOQ/7.8125.

DISCONN_AVG_MSEC FLOAT Average disconnect time, in milliseconds. Calculatedas the average of S42SCIOD/7.8125.

INPUT_RECORDS INTEGER Number of input records collected from the inputlog.

IO_COUNT FLOAT Total number of I/O operations. Calculated as thesum of S42SCION.

PENDING_AVG_MSEC FLOAT Average pending time, in milliseconds. Calculatedas the average of S42SCIOP/7.8125.

QUE_WAIT_AVG_MSEC FLOAT Average queue time, in milliseconds. Calculated asthe average of (S42SCIOR - S42SCIOC - S42SCIOP -S42SCIOD)/7.8125.

RESPONSE_AVG_MSEC FLOAT Average storage class response time, in milliseconds.Calculated as the average of S42SCIOR/7.8125.


TIME_RESOLUTION SMALLINT Time resolution used for this table, in minutes. Thedefault is 60 minutes. From TIME_RESOLUTION inthe MVSPM_TIME_RES lookup table.



MVSPM_SWAP_HThis table provides statistics on swapping activity on MVS systems. It containsdata from SMF type 71 records.








SWAP_TYPE k CHAR(4) Acronym for the swap type. This is derived from the swapplacement section and can be one of these:

Acronym MeaningTOUT Terminal output waitTIN Terminal input waitLWT Long waitASTO Auxiliary storage shortageRSTO Central pageable storage shortageDWT Detected waitREQ Request swapENQ Enqueue exchangeEXCH Exchange on recommendation valueUNIL UnilateralTRAN Transition to non-swappableICSU Improve central storage usageISPR Improve system paging rateMRSI Make room to swap in a user who has been

swapped out too longAPPC APPC wait


LSWAPS_TO_AUX FLOAT Number of logical swaps physically swapped to auxiliarystorage. This is the sum of SMF71LAX.

LSWAPS_TO_ES FLOAT Number of logical swaps physically swapped to expandedstorage. This is the sum of SMF71LES.


PSWAPS_TO_AUX FLOAT Number of physical swaps directed to auxiliary storage. Thisis the sum of SMF71AXD.

PSWAPS_TO_ES FLOAT Number of physical swaps directed to expanded storage. Thisis the sum of SMF71ESD.






SWAP_CANDIDATES FLOAT Total number of swap candidates. This is the sum ofSMF71TOT.

SWAPS_MIGRATED FLOAT Total number of physical swaps that migrated from expandedstorage to auxiliary storage. This is the sum of SMF71MIG.




MVSPM_SYSTEM_HThis table provides statistics on address space and processor activity on MVSsystems. It contains data from SMF type 70 records processed through a recordprocedure (DRL2S070).








APPC_USERS_TOT FLOAT Total number of APPC scheduler users (or ASCHaddress spaces) for all samples. This is the sum ofSMF70PTT.

ASCH0_SAMPLES FLOAT Number of samples taken in which no ASCH addressspaces were found. This is the sum of SMF70P00.

AS1_WAIT_SAMPLES FLOAT Number of samples taken in which more than oneaddress space was found waiting. Calculated fromSMF70SAM and SMF70R0x.

AS2_WAIT_SAMPLES FLOAT Number of samples taken in which more than twoaddress spaces were found waiting. Calculated fromSMF70SAM and SMF70R0x.

AS3_WAIT_SAMPLES FLOAT Number of samples taken in which more than threeaddress spaces were found waiting. Calculated fromSMF70SAM and SMF70R0x.

BATCH_USERS_TOT FLOAT Total number of batch users for all samples. This is thesum of SMF70BTT.

CPC_MODEL_ID CHAR(16) CPC model identification (from the field SMF70MDL)

CPU_BUSY_MIPS FLOAT MIPS for single CPU. Calculated as(MIPS/SMF70BNP)*CPU_BUSY_SEC. MIPS is a columnin the MVS_MIPS_T lookup table. SMF70BNP is the totalnumber of CPUs.

CPU_BUSY_SEC FLOAT Processor busy time, in seconds. Calculated asSMF70INT/1000 − SMF70WAT/4 096 000 000. For anondedicated processor in LPAR mode, this is calculatedas (SMF70EDT or SMF70PDT)/1 000 000 −SMF70WAT/4 096 000 000.

CPU_DISPATCH_SEC FLOAT Logical processor dispatch time, in seconds. Calculatedas the sum of SMF70PDT/1 000 000.

CPU_EFF_DISP_SEC FLOAT Logical processor effective dispatch time (excludingLPAR management time), in seconds. Calculated as thesum of SMF70EDT/1 000 000.



|

|



CPU_ONLINE SMALLINT Number of online processors. This is the minimum ofSMF70CPN.

CPU_ONLINE_SEC FLOAT sum of the measured time periods times the number ofonline processors, in seconds. This is the sum ofSMF70INT.

CPU_VERSION SMALLINT CPU version number. From SMF70VER.

CPU_WAIT_SEC FLOAT Processor wait time, in seconds. This is set to zero if theprocessor was run in LPAR mode and wait completionwas not enabled. Calculated as the sum ofSMF70WAT/4 096 000 000.

INPUT_RECORDS SMALLINT Number of input records collected from the input log.

INREADY_USERS_TOT FLOAT Total number of in-ready users for all samples. This isthe sum of SMF70RTT.

INSTOR_USERS_TOT FLOAT Total number of in-storage users for all samples. This isthe sum of SMF70ITT.

IO_INTERRUPTS FLOAT Number of I/O interrupts the processor handled byentry into the I/O interrupt handler. This is the sum ofSMF70SLH.

LREADY_USERS_TOT FLOAT Total number of logical ready users for all samples. Thisis the sum of SMF70LTT.

LWAIT_USERS_TOT FLOAT Total number of logical wait users for all samples. Thisis the sum of SMF70ATT.

LWAIT0_SAMPLES FLOAT Number of samples taken in which no logical wait userswere found. This is the number of times that the logicalswap was turned off. This is the sum of SMF70A00.


MVS_LEVEL SMALLINT MVS software level. This is the acronym, versionnumber, release number, and modification level. FromSMF70MVS.

OUTREADY_USERS_TOT FLOAT Total number of out-ready users for all samples. This isthe sum of SMF70OTT.

OUTWAIT_USERS_TOT FLOAT Total number of out-wait users for all samples. This isthe sum of SMF70WTT.

PROCESSOR_FLAGS CHAR(2) Logical processor flags. 80 = wait state assist enabled; 40= wait state assist changed; 20 = relative share changed;10 = partition capping is enabled; and 08 = partitioncapping status changed. From SMF70VPF.


RMF_VERSION SMALLINT RMF version number, in the form VRL, where V is theversion number, R is the release number, and L is themodification level. From SMF70MFV.


STC_USERS_TOT FLOAT Total number of started users for all samples. This is thesum of SMF70STT.







TPI_INTERRUPTS FLOAT Number of I/O interrupts the processor handled as aresult of issuing the TPI instruction with a completioncode of 1. This is the sum of SMF70TPI.

TSO_USERS_TOT FLOAT Total number of TSO/E users for all samples. This is thesum of SMF70TTT.

VECTOR_SAMPLES FLOAT Number of samples taken in which the vector bit in thePSA image was on. This is the sum of SMF70VFS.



MVSPM_VLF_HThis table provides statistics on the activity of the virtual lookaside facility (VLF).It contains data from SMF type 41, subtype 3 records.




DATE k DATE Date of the mid measurement. From SMF41DTE,SMF41TME, and VLF_INTERVAL.

TIME k TIME Time (rounded down as specified in theMVSPM_TIME_RES lookup table) of the midmeasurement. From SMF41DTE, SMF41TME, andVLF_INTERVAL.

PERIOD_NAME k CHAR(8) Name of the period. This is derived using fieldsSMF41DTE, SMF41TME, and VLF_INTERVAL asparameters in the PERIOD function.


VLF_CLASS k CHAR(8) VLF class name. From SMF41CLS.


LARGEST_OBJECT_MB FLOAT Largest object that was attempted to be put in the dataspace, in megabytes. From SMF41LRG.

OBJECTS_ADDED FLOAT Number of objects added to the data space during theinterval. From SMF41ADD.

OBJECTS_DELETED FLOAT Number of objects deleted from the data space during theinterval. From SMF41DEL.

OBJECTS_FOUND FLOAT Number of objects found in the data space during theinterval. From SMF41FND.

OBJECTS_TRIMMED FLOAT Number of objects trimmed from the data space during theinterval. FROM SMF41TRM.

SEARCHES FLOAT Number of times the data space was searched during theinterval. From SMF41SRC.


VIRT_STOR_MAX FLOAT Maximum virtual storage (MAXVIRT) specified, inmegabytes. MaximumVIRT is a VLF parameter specified inthe COFVLFxx parmlib member. From SMF41MVT

VIRT_STOR_USED_AVG FLOAT Average amount of virtual storage being used, inmegabytes. Calculated as the average of SMF41USD/256.

VIRT_STOR_USED_MAX FLOAT Maximum amount of virtual storage being used, inmegabytes. Calculated as the maximum ofSMF41USD/256.

VIRT_STOR_USED_MIN FLOAT Minimum amount of virtual storage being used, inmegabytes. Calculated as the minimum of SMF41USD/256.

VLF_INTERVAL INTEGER Time interval used by VLF to write an SMF type 41,subtype 3 record. This is set to 15 minutes.



MVSPM_VOLUME_HThis table provides hourly I/O statistics on the storage class VTOC and VVDS. Itcontains data from SMF type 42, subtype 5 records.




TIME k TIME Time (rounded down as specified in theMVSPM_TIME_RES lookup table) of the midmeasurement. From SMF42PTE and SMF42PTS.

PERIOD_NAME k CHAR(8) Name of the period. This is derived using fieldsSMF42SID, SMF42PTE, and SMF42PTS from the recordas parameters in the PERIOD function.


VOLUME k CHAR(6) The volume serial identification. From S42VTSER.

CACHE_HIT_DATA FLOAT Total number of VTOC data cache hits. Calculated as thesum of S42VDHIT.

CACHE_WR_HIT_DATA FLOAT Total number of VTOC data write cache hits. Calculatedas the sum of S42VDWHI.

CACHE_HIT_IX FLOAT Total number of VTOC index cache hits. Calculated asthe sum of S42VXHIT.

CACHE_WR_HIT_IX FLOAT Total number of VTOC index write cache hits.Calculated as the sum of S42VXWHI.

CACHE_HIT_VVDS FLOAT Total number of VVDS index cache hits. Calculated asthe sum of S42VVHIT.

CACHE_WR_HIT_VVDS FLOAT Total number of VVDS index write cache hits. Calculatedas the sum of S42VVWHI.

CANDIDATE_DATA FLOAT Total number of VTOC data cache candidates. Calculatedas the sum of S42VDCND.

CANDIDATE_DATA_WR FLOAT Total number of VTOC data write cache candidates.Calculated as the sum of S42VDWCN.

CANDIDATE_IX FLOAT Total number of VTOC index cache candidates.Calculated as the sum of S42VXCND.

CANDIDATE_IX_WR FLOAT Total number of VTOC index write cache candidates.Calculated as the sum of S42VXWCN.

CANDIDATE_VVDS FLOAT Total number of VVDS cache candidates. Calculated asthe sum of S42VVCND.

CANDIDATE_VVDS_WR FLOAT Total number of VVDS index write cache candidates.Calculated as the sum of S42VVWCN.

CONNECT_DATA_AVG FLOAT Average VTOC data component connect time, inmilliseconds. Calculated as the average ofS42VDIOC/7.8125.

CONNECT_IX_AVG FLOAT Average VTOC index component connect time, inmilliseconds. Calculated as the average ofS42VXIOC/7.8125.

CONNECT_VVDS_AVG FLOAT Average VVDS component connect time, in milliseconds.Calculated as the average of S42VVIOC/7.8125.




DEVACT_DATA FLOAT Average VTOC data I/O device-active-only time.Calculated as the average of S42VDDAO.

DEVACT_IX FLOAT Average VTOC index I/O device-active-only time.Calculated as the average of S42VXDAO.

DEVACT_VVDS FLOAT Average VVDS index I/O device-active-only time.Calculated as the average of S42VVDAO.

DEVICE_Number SMALLINT The binary device number. From S42VTADR.

DISCONN_DATA_AVG FLOAT Average VTOC data component disconnect time, inmilliseconds. Calculated as the average ofS42VDIOD/7.8125.

DISCONN_IX_AVG FLOAT Average VTOC index component disconnect time, inmilliseconds. Calculated as the average ofS42VXIOD/7.8125.

DISCONN_VVDS_AVG FLOAT Average VVDS component disconnect time, inmilliseconds. Calculated as the average ofS42VVIOD/7.8125.

IN_CACHE_DATA FLOAT Total number of VTOC data inhibit cache load I/Ooperations. Calculated as the sum of S42VDICL.

IN_CACHE_IX FLOAT Total number of VTOC index inhibit cache load I/Ooperations. Calculated as the sum of S42VXICL.

IN_CACHE_VVDS FLOAT Total number of VVDS index inhibit cache load I/Ooperations. Calculated as the sum of S42VDICL.


IO_DATA_COUNT FLOAT Total number of VTOC data I/O operations. Calculatedas the sum of S42VDION.

IO_ESCAPED FLOAT Total count of I/O not captured by the VTOC or VVDScomponent. This is the sum of S42TUNC.

IO_IX_COUNT FLOAT Total number of VTOC index I/O operations. Calculatedas the sum of S42VXION.

IO_VVDS_COUNT FLOAT Total number of VVDS I/O operations. Calculated as thesum of S42VVION.

LEV_CACHE_DATA FLOAT Total number of VTOC data record level cache I/Ooperations. Calculated as the sum of S42VDRLC.

LEV_CACHE_IX FLOAT Total number of VTOC index record level cache I/Ooperations. Calculated as the sum of S42VXRLC.

LEV_CACHE_VVDS FLOAT Total number of VVDS index record level cache I/Ooperations. Calculated as the sum of S42VDRLC.

ONLINE CHAR(1) Indicates whether the device is online. This is Y (yes) ifbit 1 of S42VTFL1 is on; otherwise, N (no).

PENDING_DATA_AVG FLOAT Average VTOC data component pending time, inmilliseconds. Calculated as the average ofS42VDIOP/7.8125.

PENDING_IX_AVG FLOAT Average VTOC index component pending time, inmilliseconds. Calculated as the average ofS42VXIOP/7.8125.

PENDING_VVDS_AVG FLOAT Average VVDS component pending time, inmilliseconds. Calculated as the average ofS42VVIOP/7.8125.




QUEUE_DATA_AVG FLOAT Average VTOC data component control unit queue time,in milliseconds. Calculated as the average ofS42VDIOQ/7.8125.

QUEUE_IX_AVG FLOAT Average VTOC index component control unit queuetime, in milliseconds. Calculated as the average ofS42VXIOQ/7.8125.

QUEUE_VVDS_AVG FLOAT Average VVDS component control unit queue time, inmilliseconds. Calculated as the average ofS42VVIOQ/7.8125.

RESPONSE_DATA_AVG FLOAT Average VTOC data component response time, inmilliseconds. Calculated as the average ofS42VDIOR/7.8125.

RESPONSE_IX_AVG FLOAT Average VTOC index component response time, inmilliseconds. Calculated as the average ofS42VXIOR/7.8125.

RESPONSE_VVDS_AVG FLOAT Average VVDS component response time, inmilliseconds. Calculated as the average ofS42VVIOR/7.8125.

SEQ_IO_DATA FLOAT Total number of VTOC data sequential I/O operations.Calculated as the sum of S42VDSEQ.

SMS_VOLUME CHAR(1) Indicates whether the device is SMS managed. This is Y(yes) if bit 2 of S42VTFL1 is on; otherwise, N (no).


SEQ_IO_IX FLOAT Total number of VTOC index sequential I/O operations.Calculated as the sum of S42VXSEQ.

SEQ_IO_VVDS FLOAT Total number of VVDS index sequential I/O operations.Calculated as the sum of S42VVSEQ.




MVSPM_VS_CSASQA_HThis table provides hourly statistics on the usage of virtual storage in the CSA andSQA. It contains data from SMF type 78, subtype 2 records.








CSA_ALLOC_A16M_AVG FLOAT Average CSA allocated area size above 16 megabytes, inbytes. Calculated as the average of R782CSAL(VSDATOTL)/SMF78SAM.

CSA_ALLOC_A16M_MAX INTEGER Maximum CSA allocated area size above 16 megabytes,in bytes. This is the maximum of R782CSAL(VSDAMAX).

CSA_ALLOC_A16M_MIN INTEGER Minimum CSA allocated area size above 16 megabytes,in bytes. This is the minimum of R782CSAL(VSDAMIN).

CSA_ALLOC_B16M_AVG FLOAT Average CSA allocated area size below 16 megabytes,in bytes. Calculated as the average of R782CSAL(VSDBTOTL)/SMF78SAM.

CSA_ALLOC_B16M_MAX INTEGER Maximum CSA allocated area size below 16 megabytes,in bytes. This is the maximum of R782CSAL(VSDBMAX).

CSA_ALLOC_B16M_MIN INTEGER Minimum CSA allocated area size below 16 megabytes,in bytes. This is the minimum of R782CSAL(VSDBMIN).

CSA_BLK_A16MB_AVG FLOAT Average largest free block of CSA above 16 megabytes,in bytes. Calculated as the average of R782CSLF(VSDATOTL)/SMF78SAM.

CSA_BLK_A16MB_MAX INTEGER Maximum largest free block of CSA above 16megabytes, in bytes. This is the maximum of R782CSLF(VSDAMAX).

CSA_BLK_A16MB_MIN INTEGER Minimum largest free block of CSA above 16megabytes, in bytes. This is the minimum of R782CSLF(VSDAMIN).

CSA_BLK_B16MB_AVG FLOAT Average largest free block of CSA below 16 megabytes,in bytes. Calculated as the average of R782CSLF(VSDBTOTL)/SMF78SAM.

CSA_BLK_B16MB_MAX INTEGER Maximum largest free block of CSA below 16megabytes, in bytes. This is the maximum of R782CSLF(VSDBMAX).




CSA_BLK_B16MB_MIN INTEGER Minimum largest free block of CSA below 16megabytes, in bytes. This is the minimum of R782CSLF(VSDBMIN).

CSA_FREE_A16MB_avg FLOAT Average free CSA above 16 megabytes, in bytes.Calculated as the average of R782CSAF(VSDATOTL)/SMF78SAM.

CSA_FREE_A16MB_MAX INTEGER Maximum free CSA above 16 megabytes, in bytes. Thisis the maximum of R782CSAF (VSDAMAX).

CSA_FREE_A16MB_MIN INTEGER Minimum free CSA above 16 megabytes, in bytes. Thisis the minimum of R782CSAF (VSDAMIN).

CSA_FREE_B16MB_AVG FLOAT Average free CSA below 16 megabytes, in bytes.Calculated as the average of R782CSAF(VSDBTOTL)/SMF78SAM.

CSA_FREE_B16MB_MAX INTEGER Maximum free CSA below 16 megabytes, in bytes. Thisis the maximum of R782CSAF (VSDBMAX).

CSA_FREE_B16MB_MIN INTEGER Minimum free CSA below 16 megabytes, in bytes. Thisis the minimum of R782CSAF (VSDBMIN).

CSA_KEY0_A16MB_AVG FLOAT Average CSA used by storage key 0 above 16megabytes, in bytes. Calculated as the average ofR782CSAK (VSDBTOTL)/SMF78SAM.

CSA_KEY0_A16MB_MAX INTEGER Maximum CSA used by storage key 0 above 16megabytes, in bytes. This is the maximum ofR782CSAK (VSDBMAX).

CSA_KEY0_A16MB_MIN INTEGER Minimum CSA used by storage key 0 above 16megabytes, in bytes. This is the minimum of R782CSAK(VSDBMIN).

CSA_KEY0_B16MB_AVG FLOAT Average CSA used by storage key 0 below 16megabytes, in bytes. Calculated as the average ofR782CSAK (VSDBTOTL)/SMF78SAM.

CSA_KEY0_B16MB_MAX INTEGER Maximum CSA used by storage key 0 below 16megabytes, in bytes. This is the maximum ofR782CSAK (VSDBMAX).

CSA_KEY0_B16MB_MIN INTEGER Minimum CSA used by storage key 0 below 16megabytes, in bytes. This is the minimum of R782CSAK(VSDBMIN).












CSA_KEY8_A16MB_AVG FLOAT Average CSA used by storage keys 8–F above 16megabytes, in bytes. Calculated as the average ofR782CSAK (VSDBTOTL)/SMF78SAM.

CSA_KEY8_A16MB_MAX INTEGER Maximum CSA used by storage keys 8–F above 16megabytes, in bytes. This is the maximum ofR782CSAK (VSDBMAX).

CSA_KEY8_A16MB_MIN INTEGER Minimum CSA used by storage keys 8–F above 16megabytes, in bytes. This is the minimum of R782CSAK(VSDBMIN).

CSA_KEY8_B16MB_AVG FLOAT Average CSA used by storage keys 8–F below 16megabytes, in bytes. Calculated as the average ofR782CSAK (VSDBTOTL)/SMF78SAM.

CSA_KEY8_B16MB_MAX INTEGER Maximum CSA used by storage keys 8–F below 16megabytes, in bytes. This is the maximum ofR782CSAK (VSDBMAX).

CSA_KEY8_B16MB_MIN INTEGER Minimum CSA used by storage keys 8–F below 16megabytes, in bytes. This is the minimum of R782CSAK(VSDBMIN).

CSA_SP227_B16M_AVG FLOAT Average CSA used by subpool 227, all storage keysbelow 16 megabytes, in bytes. Calculated as the averageof the tenth occurrence of R782227K(VSDBTOTL)/SMF78SAM.

CSA_SP227_B16M_MAX INTEGER Maximum CSA used by subpool 227, all storage keysbelow 16 megabytes, in bytes. This is the maximum ofthe tenth occurrence of R782227K (VSDBMAX).

CSA_SP227_B16M_MIN INTEGER Minimum CSA used by subpool 227, all storage keysbelow 16 megabytes, in bytes. This is the minimum ofthe tenth occurrence of R782227K (VSDBMIN).













CSA_UNUSED_A16_AVG FLOAT Average allocated but not used CSA above 16megabytes, in bytes. Calculated as the average of(R782CSAL (VSDATOTL) − R782CSAU(VSDATOTL))/SMF78SAM.

CSA_UNUSED_A16_MAX INTEGER Maximum allocated but not used CSA above 16megabytes, in bytes. Calculated as the maximum of(R782CSAL (VSDATOTL) − R782CSAU(VSDATOTL))/SMF78SAM.

CSA_UNUSED_A16_MIN INTEGER Minimum allocated but not used CSA above 16megabytes, in bytes. Calculated as the minimum of(R782CSAL (VSDATOTL) − R782CSAU(VSDATOTL))/SMF78SAM.

CSA_UNUSED_B16_AVG FLOAT Average allocated but not used CSA below 16megabytes, in bytes. Calculated as the average ofR782CSAL (VSDBTOTL) − R782CSAU(VSDBTOTL)/SMF78SAM.

CSA_UNUSED_B16_MAX INTEGER Maximum allocated but not used CSA below 16megabytes, in bytes. Calculated as the maximum ofR782CSAL (VSDBTOTL) − R782CSAU(VSDBTOTL)/SMF78SAM.

CSA_UNUSED_B16_MIN INTEGER Minimum allocated but not used CSA below 16megabytes, in bytes. Calculated as the minimum ofR782CSAL (VSDBTOTL) − R782CSAU(VSDBTOTL)/SMF78SAM.

CSA_USAGE_A16M_AVG FLOAT Average CSA usage above 16 megabytes, in bytes.Calculated as the average of R782CSAU(VSDATOTL)/SMF78SAM.

CSA_USAGE_A16M_MAX INTEGER Maximum CSA usage above 16 megabytes, in bytes.This is the maximum of R782CSAU (VSDAMAX).

CSA_USAGE_A16M_MIN INTEGER Minimum CSA usage above 16 megabytes, in bytes.This is the minimum of R782CSAU (VSDAMIN).

CSA_USAGE_B16M_AVG FLOAT Average CSA usage below 16 megabytes, in bytes.Calculated as the average of R782CSAU(VSDBTOTL)/SMF78SAM.

CSA_USAGE_B16M_MAX INTEGER Maximum CSA usage below 16 megabytes, in bytes.This is the maximum of R782CSAU (VSDBMAX).




CSA_USAGE_B16M_MIN INTEGER Minimum CSA usage below 16 megabytes, in bytes.This is the minimum of R782CSAU (VSDBMIN).

CSA_227K0_B16M_AVG FLOAT Average CSA used by subpool 227 and storage key 0below 16 megabytes, in bytes. Calculated as the averageof the first occurrence of R782227K(VSDBTOTL)/SMF78SAM.

CSA_227K0_B16M_MAX INTEGER Maximum CSA used by subpool 227 and storage key 0below 16 megabytes, in bytes. This is the maximum ofthe first occurrence of R782227K (VSDBMAX).

CSA_227K0_B16M_MIN INTEGER Minimum CSA used by subpool 227 and storage key 0below 16 megabytes, in bytes. This is the minimum ofthe first occurrence of R782227K (VSDBMIN).

CSA_227K1_B16M_AVG FLOAT Average CSA used by subpool 227 and storage key 1below 16 megabytes, in bytes. Calculated as the averageof the second occurrence of R782227K(VSDBTOTL)/SMF78SAM.

CSA_227K1_B16M_MAX INTEGER Maximum CSA used by subpool 227 and storage key 1below 16 megabytes, in bytes. This is the maximum ofthe second occurrence of R782227K (VSDBMAX).

CSA_227K1_B16M_MIN INTEGER Minimum CSA used by subpool 227 and storage key 1below 16 megabytes, in bytes. This is the minimum ofthe second occurrence of R782227K (VSDBMIN).

CSA_227K2_B16M_AVG FLOAT Average CSA used by subpool 227 and storage key 2below 16 megabytes, in bytes. Calculated as the averageof the third occurrence of R782227K(VSDBTOTL)/SMF78SAM.

CSA_227K2_B16M_MAX INTEGER Maximum CSA used by subpool 227 and storage key 2below 16 megabytes, in bytes. This is the maximum ofthe third occurrence of R782227K (VSDBMAX).

CSA_227K2_B16M_MIN INTEGER Minimum CSA used by subpool 227 and storage key 2below 16 megabytes, in bytes. This is the minimum ofthe third occurrence of R782227K (VSDBMIN).

CSA_227K3_B16M_AVG FLOAT Average CSA used by subpool 227 and storage key 3below 16 megabytes, in bytes. Calculated as the averageof the fourth occurrence of R782227K(VSDBTOTL)/SMF78SAM.

CSA_227K3_B16M_MAX INTEGER Maximum CSA used by subpool 227 and storage key 3below 16 megabytes, in bytes. This is the maximum ofthe fourth occurrence of R782227K (VSDBMAX).

CSA_227K3_B16M_MIN INTEGER Minimum CSA used by subpool 227 and storage key 3below 16 megabytes, in bytes. This is the minimum ofthe fourth occurrence of R782227K (VSDBMIN).

CSA_227K4_B16M_AVG FLOAT Average CSA used by subpool 227 and storage key 4below 16 megabytes, in bytes. Calculated as the averageof the fifth occurrence of R782227K(VSDBTOTL)/SMF78SAM.

CSA_227K4_B16M_MAX INTEGER Maximum CSA used by subpool 227 and storage key 4below 16 megabytes, in bytes. This is the maximum ofthe fifth occurrence of R782227K (VSDBMAX).

CSA_227K4_B16M_MIN INTEGER Minimum CSA used by subpool 227 and storage key 4below 16 megabytes, in bytes. This is the minimum ofthe fifth occurrence of R782227K (VSDBMIN).




CSA_227K5_B16M_AVG FLOAT Average CSA used by subpool 227 and storage key 5below 16 megabytes, in bytes. Calculated as the averageof the sixth occurrence of R782227K(VSDBTOTL)/SMF78SAM.

CSA_227K5_B16M_MAX INTEGER Maximum CSA used by subpool 227 and storage key 5below 16 megabytes, in bytes. This is the maximum ofthe sixth occurrence of R782227K (VSDBMAX).

CSA_227K5_B16M_MIN INTEGER Minimum CSA used by subpool 227 and storage key 5below 16 megabytes, in bytes. This is the minimum ofthe sixth occurrence of R782227K (VSDBMIN).

CSA_227K6_B16M_AVG FLOAT Average CSA used by subpool 227 and storage key 6below 16 megabytes, in bytes. Calculated as the averageof the seventh occurrence of R782227K(VSDBTOTL)/SMF78SAM.

CSA_227K6_B16M_MAX INTEGER Maximum CSA used by subpool 227 and storage key 6below 16 megabytes, in bytes. This is the maximum ofthe seventh occurrence of R782227K (VSDBMAX).

CSA_227K6_B16M_MIN INTEGER Minimum CSA used by subpool 227 and storage key 6below 16 megabytes, in bytes. This is the minimum ofthe seventh occurrence of R782227K (VSDBMIN).

CSA_227K7_B16M_AVG FLOAT Average CSA used by subpool 227 and storage key 7below 16 megabytes, in bytes. Calculated as the averageof the eighth occurrence of R782227K(VSDBTOTL)/SMF78SAM.

CSA_227K7_B16M_MAX INTEGER Maximum CSA used by subpool 227 and storage key 7below 16 megabytes, in bytes. This is the maximum ofthe eighth occurrence of R782227K (VSDBMAX).

CSA_227K7_B16M_MIN INTEGER Minimum CSA used by subpool 227 and storage key 7below 16 megabytes, in bytes. This is the minimum ofthe eighth occurrence of R782227K (VSDBMIN).

CSA_227K8_B16M_AVG FLOAT Average CSA used by subpool 227 and storage keys8–F below 16 megabytes, in bytes. Calculated as theaverage of the ninth occurrence of R782227K(VSDBTOTL)/SMF78SAM.

CSA_227K8_B16M_MAX INTEGER Maximum CSA used by subpool 227 and storage keys8–F below 16 megabytes, in bytes. This is the maximumof the ninth occurrence of R782227K (VSDBMAX).

CSA_227K8_B16M_MIN INTEGER Minimum CSA used by subpool 227 and storage keys8–F below 16 megabytes, in bytes. This is the minimumof the ninth occurrence of R782227K (VSDBMIN).












SAMPLES INTEGER Number of RMF samples taken. This is the sum ofSMF78SAM.

SQA_ALLOC_A16M_AVG FLOAT Average SQA allocated area size above 16 megabytes,in bytes. Calculated as the average of R782SQAL(VSDATOTL)/SMF78SAM.

SQA_ALLOC_A16M_MAX INTEGER Maximum SQA allocated area size above 16 megabytes,in bytes. This is the maximum of R782SQAL(VSDAMAX).

SQA_ALLOC_A16M_MIN INTEGER Minimum SQA allocated area size above 16 megabytes,in bytes. This is the minimum of R782SQAL(VSDAMIN).

SQA_ALLOC_B16M_AVG FLOAT Average SQA allocated area size below 16 megabytes,in bytes. Calculated as the average of R782SQAL(VSDBTOTL)/SMF78SAM.

SQA_ALLOC_B16M_MAX INTEGER Maximum SQA allocated area size below 16 megabytes,in bytes. This is the maximum of R782SQAL(VSDBMAX).

SQA_ALLOC_B16M_MIN INTEGER Minimum SQA allocated area size below 16 megabytes,in bytes. This is the minimum of R782SQAL(VSDBMIN).

SQA_BLK_A16MB_AVG FLOAT Average largest free block of SQA above 16 megabytes,in bytes. Calculated as the average of R782SQLF(VSDATOTL)/SMF78SAM.

SQA_BLK_A16MB_MAX INTEGER Maximum largest free block of SQA above 16megabytes, in bytes. This is the maximum of R782SQLF(VSDAMAX).

SQA_BLK_A16MB_MIN INTEGER Minimum largest free block of SQA above 16megabytes, in bytes. This is the minimum of R782SQLF(VSDAMIN).

SQA_BLK_B16MB_AVG FLOAT Average largest free block of SQA below 16 megabytes,in bytes. Calculated as the average of R782SQLF(VSDBTOTL)/SMF78SAM.

SQA_BLK_B16MB_MAX INTEGER Maximum largest free block of SQA below 16megabytes, in bytes. This is the maximum of R782SQLF(VSDBMAX).




SQA_BLK_B16MB_MIN INTEGER Minimum largest free block of SQA below 16megabytes, in bytes. This is the minimum of R782SQLF(VSDBMIN).

SQA_EXP_A16MB_AVG FLOAT Average SQA expansion into CSA above 16 megabytes,in bytes. Calculated as the average of R782SQEX(VSDATOTL)/SMF78SAM.

SQA_EXP_A16MB_MAX INTEGER Maximum SQA expansion into CSA above 16megabytes, in bytes. This is the maximum of R782SQEX(VSDAMAX).

SQA_EXP_A16MB_MIN INTEGER Minimum SQA expansion into CSA above 16megabytes, in bytes. This is the minimum of R782SQEX(VSDAMIN).

SQA_EXP_B16MB_AVG FLOAT Average SQA expansion into CSA below 16 megabytes,in bytes. Calculated as the average of R782SQEX(VSDBTOTL)/SMF78SAM.

SQA_EXP_B16MB_MAX INTEGER Maximum SQA expansion into CSA below 16megabytes, in bytes. This is the maximum of R782SQEX(VSDBMAX).

SQA_EXP_B16MB_MIN INTEGER Minimum SQA expansion into CSA below 16megabytes, in bytes. This is the minimum of R782SQEX(VSDBMIN).

SQA_FREE_A16MB_AVG FLOAT Average free SQA above 16 megabytes, in bytes.Calculated as the average of R782SQAF(VSDATOTL)/SMF78SAM.

SQA_FREE_A16MB_MAX INTEGER Maximum free SQA above 16 megabytes, in bytes. Thisis the maximum of R782SQAF (VSDAMAX).

SQA_FREE_A16MB_MIN INTEGER Minimum free SQA above 16 megabytes, in bytes. Thisis the minimum of R782SQAF (VSDAMIN).

SQA_FREE_B16MB_AVG FLOAT Average free SQA below 16 megabytes, in bytes.Calculated as the average of R782SQAF(VSDBTOTL)/SMF78SAM.

SQA_FREE_B16MB_MAX INTEGER Maximum free SQA below 16 megabytes, in bytes. Thisis the maximum of R782SQAF (VSDBMAX).

SQA_FREE_B16MB_MIN INTEGER Minimum free SQA below 16 megabytes, in bytes. Thisis the minimum of R782SQAF (VSDBMIN).

SQA_SP226_B16M_AVG FLOAT Average usage of SQA subpool 226 below 16megabytes, in bytes. Calculated as the average ofR782226 (VSDBTOTL)/SMF78SAM.

SQA_SP226_B16M_MAX INTEGER Maximum usage of SQA subpool 226 below 16megabytes, in bytes. This is the maximum of R782226(VSDBMAX).

SQA_SP226_B16M_MIN INTEGER Minimum usage of SQA subpool 226 below 16megabytes, in bytes. This is the minimum of R782226(VSDBMIN).


SQA_SP239_B16M_MAX INTEGER Maximum usage of SQA subpool 239 below 16megabytes, in bytes. This is the maximum of R782239(VSDBMAX).






SQA_SP245_B16M_MAX INTEGER Maximum usage of SQA subpool 245 below 16megabytes, in bytes. Calculated as the maximum ofR782245 (VSDBMAX).


SQA_UNUSED_A16_AVG FLOAT Average SQA allocated but not used above 16megabytes, in bytes. Calculated as the average ofR782SQAL (VSDATOTL) − R782SQAU(VSDATOTL)/SMF78SAM.

SQA_UNUSED_A16_MAX INTEGER Maximum SQA allocated but not used above 16megabytes, in bytes. Calculated as the maximum ofR782CSAL (VSDATOTL) − R782CSAU(VSDATOTL)/SMF78SAM.

SQA_UNUSED_A16_MIN INTEGER Minimum SQA allocated but not used above 16megabytes, in bytes. Calculated as the minimum ofR782SQAL (VSDATOTL) − R782SQAU(VSDATOTL)/SMF78SAM.

SQA_UNUSED_B16_AVG FLOAT Average SQA allocated but not used below 16megabytes, in bytes. Calculated as the average ofR782SQAL (VSDBTOTL) − R782SQAU(VSDBTOTL)/SMF78SAM.

SQA_UNUSED_B16_MAX INTEGER Maximum SQA allocated but not used below 16megabytes, in bytes. Calculated as the maximum ofR782CSAL (VSDBTOTL) − R782CSAU(VSDBTOTL)/SMF78SAM.

SQA_UNUSED_B16_MIN INTEGER Minimum SQA allocated but not used below 16megabytes, in bytes. Calculated as the minimum ofR782SQAL (VSDBTOTL) − R782SQAU(VSDBTOTL)/SMF78SAM.

SQA_USAGE_A16M_AVG FLOAT Average SQA usage above 16 megabytes, in bytes.Calculated as the average of R782SQAU(VSDATOTL)/SMF78SAM.

SQA_USAGE_A16M_MAX INTEGER Maximum SQA usage above 16 megabytes, in bytes.This is the maximum of R782SQAU (VSDAMAX).

SQA_USAGE_A16M_MIN INTEGER Minimum SQA usage above 16 megabytes, in bytes.This is the minimum of R782SQAU (VSDAMIN).

SQA_USAGE_B16M_AVG FLOAT Average SQA usage below 16 megabytes, in bytes.Calculated as the average of R782SQAU(VSDBTOTL)/SMF78SAM.

SQA_USAGE_B16M_MAX INTEGER Maximum SQA usage below 16 megabytes, in bytes.This is the maximum of R782SQAU (VSDBMAX).

SQA_USAGE_B16M_MIN INTEGER Minimum SQA usage below 16 megabytes, in bytes.This is the minimum of R782SQAU (VSDBMIN).



MVSPM_VS_PRIVATE_HThis table provides hourly statistics on the usage of private virtual storage areas. Itcontains data from SMF type 78, subtype 2 records.








JOB_NAME k CHAR(8) Name of the monitored job or started task. FromR872JOBN.

GETM_LIMIT_A16MB INTEGER Getmain limit above 16 megabytes, in bytes. This is themaximum of R782GMLA.

GETM_LIMIT_B16MB INTEGER Getmain limit below 16 megabytes, in bytes. This is themaximum of R782GMLB.


REGION_REQUESTED INTEGER Region requested by the JCL, in bytes. This is the firstoccurrence of R782REGR.

RGN_ASSIGNED_A16MB INTEGER Region above 16 megabytes assigned by exits, in bytes.This is the first occurrence of R782RGAA.

RGN_ASSIGNED_B16MB INTEGER Region below 16 megabytes assigned by exits, in bytes.This is the first occurrence of R782RGAB.

SAMPLES INTEGER Number of RMF samples used. This is the sum ofR782SAMP.

SYS_AREA_A16MB_AVG FLOAT Average allocated system area size above 16 megabytes,in bytes. Calculated as the average of R782LSAL(VSDATOTL)/R782SAMP.

SYS_AREA_A16MB_MAX INTEGER Maximum allocated system area size above 16megabytes, in bytes. This is the maximum of R782LSAL(VSDAMAX).

SYS_AREA_A16MB_MIN INTEGER Minimum allocated system area size above 16megabytes, in bytes. This is the minimum of R782LSAL(VSDAMIN).

SYS_AREA_B16MB_AVG FLOAT Average allocated system area size below 16 megabytes,in bytes. Calculated as the average of R782LSAL(VSDBTOTL)/R782SAMP.

SYS_AREA_B16MB_MAX INTEGER Maximum allocated system area size below 16megabytes, in bytes. This is the maximum of R782LSAL(VSDBMAX).




SYS_AREA_B16MB_MIN INTEGER Minimum allocated system area size below 16megabytes, in bytes. This is the minimum of R782LSAL(VSDBMIN).

SYS_BLK_A16MB_AVG FLOAT Average largest system free block above 16 megabytes,in bytes. Calculated as the average of R782LSFB(VSDATOTL)/R782SAMP.

SYS_BLK_A16MB_MAX INTEGER Maximum largest system free block above 16megabytes, in bytes. This is the maximum of R782LSFB(VSDAMAX).

SYS_BLK_A16MB_MIN INTEGER Minimum largest system free block above 16megabytes, in bytes. This is the minimum of R782LSFB(VSDAMIN).

SYS_BLK_B16MB_AVG FLOAT Average largest system free block below 16 megabytes,in bytes. Calculated as the average of R782LSFB(VSDBTOTL)/R782SAMP.

SYS_BLK_B16MB_MAX INTEGER Maximum largest system free block below 16megabytes, in bytes. This is the maximum of R782LSFB(VSDBMAX).

SYS_BLK_B16MB_MIN INTEGER Minimum largest system free block below 16megabytes, in bytes. This is the minimum of R782LSFB(VSDBMIN).

SYS_FREE_A16MB_AVG FLOAT Average system area free pages above 16 megabytes, inbytes. Calculated as the average of R782LSFP(VSDATOTL)/R782SAMP.

SYS_FREE_A16MB_MAX INTEGER Maximum system area free pages above 16 megabytes,in bytes. This is the maximum of R782LSFP(VSDAMAX).

SYS_FREE_A16MB_MIN INTEGER Minimum system area free pages above 16 megabytes,in bytes. This is the minimum of R782LSFP(VSDAMIN).

SYS_FREE_B16MB_AVG FLOAT Average system area free pages below 16 megabytes, inbytes. Calculated as the average of R782LSFP(VSDBTOTL)/R782SAMP.

SYS_FREE_B16MB_MAX INTEGER Maximum system area free pages below 16 megabytes,in bytes. This is the maximum of R782LSFP(VSDBMAX).

SYS_FREE_B16MB_MIN INTEGER Minimum system area free pages below 16 megabytes,in bytes. This is the minimum of R782LSFP(VSDBMIN).

SYS_PAGES_A16M_AVG FLOAT Average allocated system pages above 16 megabytes, inbytes. Calculated as the average of R782LSPA(VSDATOTL)/R782SAMP.

SYS_PAGES_A16M_MAX INTEGER Maximum allocated system pages above 16 megabytes,in bytes. This is the maximum of R782LSPA(VSDAMAX).

SYS_PAGES_A16M_MIN INTEGER Minimum allocated system pages above 16 megabytes,in bytes. This is the minimum of R782LSPA(VSDAMIN).

SYS_PAGES_B16M_AVG FLOAT Average allocated system pages below 16 megabytes, inbytes. Calculated as the average of R782LSPA(VSDBTOTL)/R782SAMP.




SYS_PAGES_B16M_MAX INTEGER Maximum allocated system pages below 16 megabytes,in bytes. This is the maximum of R782LSPA(VSDBMAX).

SYS_PAGES_B16M_MIN INTEGER Minimum allocated system pages below 16 megabytes,in bytes. This is the minimum of R782LSPA(VSDBMIN).


USER_AREA_A16M_AVG FLOAT Average user region allocated area size above 16megabytes, in bytes. Calculated as the average ofR782USAL (VSDATOTL)/R782SAMP.

USER_AREA_A16M_MAX INTEGER Maximum user region allocated area size above 16megabytes, in bytes. This is the maximum ofR782USAL (VSDAMAX).

USER_AREA_A16M_MIN INTEGER Minimum user region allocated area size above 16megabytes, in bytes. This is the minimum of R782USAL(VSDAMIN).

USER_AREA_B16M_AVG FLOAT Average user region allocated area size below 16megabytes, in bytes. Calculated as the average ofR782USAL (VSDBTOTL)/R782SAMP.

USER_AREA_B16M_MAX INTEGER Maximum user region allocated area size below 16megabytes, in bytes. This is the maximum ofR782USAL (VSDBMAX).

USER_AREA_B16M_MIN INTEGER Minimum user region allocated area size below 16megabytes, in bytes. This is the minimum of R782USAL(VSDBMIN).

USER_BLK_A16MB_AVG FLOAT Average user region largest free block above 16megabytes, in bytes. Calculated as the average ofR782USFB (VSDATOTL)/R782SAMP.

USER_BLK_A16MB_MAX INTEGER Maximum user region largest free block above 16megabytes, in bytes. This is the maximum of R782USFB(VSDAMAX).

USER_BLK_A16MB_MIN INTEGER Minimum user region largest free block above 16megabytes, in bytes. This is the minimum of R782USFB(VSDAMIN).

USER_BLK_B16MB_AVG FLOAT Average user region largest free block below 16megabytes, in bytes. Calculated as the average ofR782USFB (VSDBTOTL)/R782SAMP.

USER_BLK_B16MB_MAX INTEGER Maximum user region largest free block below 16megabytes, in bytes. This is the maximum of R782USFB(VSDBMAX).

USER_BLK_B16MB_MIN INTEGER Minimum user region largest free block below 16megabytes, in bytes. This is the minimum of R782USFB(VSDBMIN).

USER_FREE_A16M_AVG FLOAT Average user region free pages above 16 megabytes, inbytes. Calculated as the average of R782USFP(VSDATOTL)/R782SAMP.

USER_FREE_A16M_MAX INTEGER Maximum user region free pages above 16 megabytes,in bytes. This is the maximum of R782USFP(VSDAMAX).




USER_FREE_A16M_MIN INTEGER Minimum user region free pages above 16 megabytes,in bytes. This is the minimum of R782USFP(VSDAMIN).

USER_FREE_B16M_AVG FLOAT Average user region free pages below 16 megabytes, inbytes. Calculated as the average of R782USFP(VSDBTOTL)/R782SAMP.

USER_FREE_B16M_MAX INTEGER Maximum user region free pages below 16 megabytes,in bytes. This is the maximum of R782USFP(VSDBMAX).

USER_FREE_B16M_MIN INTEGER Minimum user region free pages below 16 megabytes,in bytes. This is the minimum of R782USFP(VSDBMIN).

USER_PAGES_A16_AVG FLOAT Average user region allocated pages above 16megabytes, in bytes. Calculated as the average ofR782USPA (VSDATOTL)/R782SAMP.

USER_PAGES_A16_MAX INTEGER Maximum user region allocated pages above 16megabytes, in bytes. This is the maximum of R782USPA(VSDAMAX).

USER_PAGES_A16_MIN INTEGER Minimum user region allocated pages above 16megabytes, in bytes. This is the minimum of R782USPA(VSDAMIN).

USER_PAGES_B16_AVG FLOAT Average user region allocated pages below 16megabytes, in bytes. Calculated as the average ofR782USPA (VSDBTOTL)/R782SAMP.

USER_PAGES_B16_MAX INTEGER Maximum user region allocated pages below 16megabytes, in bytes. This is the maximum of R782USPA(VSDBMAX).

USER_PAGES_B16_MIN INTEGER Minimum user region allocated pages below 16megabytes, in bytes. This is the minimum of R782USPA(VSDBMIN).



MVSPM_VS_SUBPOOL_HThis table provides hourly statistics on the usage of private subpool virtual storageareas by subpool number. It contains data from SMF type 78, subtype 2 records.








JOB_NAME k CHAR(8) Name of the monitored job or started task. FromR782JOBN.

SUBPOOL_NUM k INTEGER Subpool number. From R782SPN.


SAMPLES INTEGER Number of RMF samples taken. This is the sum ofR782SAMP.

TIME_RESOLUTION SMALLINT Time resolution used for this table, in minutes. The defaultis 60 minutes. From TIME_RESOLUTION in theMVSPM_TIME_RES lookup table.

VS_ALLOCATED_AVG FLOAT Average virtual storage allocated to the subpool, in bytes.Calculated as the average of R782SPD(VSDBTOTL)/R782SAMP.

VS_ALLOCATED_MAX INTEGER Maximum virtual storage allocated to the subpool, inbytes. This is the maximum of R782SPD (VSDBMAX).

VS_ALLOCATED_MIN INTEGER Minimum virtual storage allocated to the subpool, in bytes.This is the minimum of R782SPD (VSDBMIN).



MVSPM_WLM_SERVED_HThis table provides data about served service classes in systems that are running ingoal mode. It contains data from SMF type 72, subtype 3 records.





TIME k TIME Time (rounded down as specified in the MVSPM_TIME_REStable) of the mid measurement. From SMF72DAT, SMF72IST,and SMF72INT.






SERVED_CLASS k CHAR(8) Name of service class being served. From R723SCSN.



SERVED_NO INTEGER Total number of times SERVED_CLASS was served bySERVICE_CLASS. Calculated as the sum of R723SSCÄ.


SYSPLEX_NAME CHAR(8) Sysplex name (as defined in ECVTSPLX). From SMF72XNM.

SYSTEM_NAME CHAR(8) System name for the current system (as defined inCVTSNAME). From SMF72SNM.




MVSPM_WLM_STATE_HThis table provides data about MVS systems in a sysplex. It contains data fromSMF type 72, subtype 3 records.








WORKLOAD_TYPE k CHAR(8) MVS workload type name. From WORKLOAD_TYPE inthe MVS_WORKLOAD2_TYPE lookup table.




PHASE k CHAR(3) Work/Resource manager flag. BTE represents statessampled in the begin-to-end phase. EXE represents statessampled in the execution phase. From R723RFLG.

ACTIVE_APPL_CNT FLOAT Total number of active application state samples (from thework manager perspective). From R723RAPP.

ACTIVE_STATE_CNT FLOAT Total number of active state samples. Calculated as thesum of R723RACT.

CON_LOC_STATE_CNT FLOAT Number of state samples representing transactions forwhich there are logical continuations on this MVS image.Calculated as the sum of R723RSSL.

CON_NET_STATE_CNT FLOAT Number of state samples representing transactions forwhich there are logical continuations somewhere withinthe network. Calculated as the sum of R723RSSN.

CON_SPX_STATE_CNT FLOAT Number of state samples representing transactions forwhich there are logical continuations on another MVSimage in the sysplex. Calculated as the sum of R723RSSS.

CONV_STATE_CNT FLOAT Total number of waiting for conversation state samples.Calculated as the sum of R723RWCO.

DISTR_STATE_CNT FLOAT Total number of waiting for distributed request statesamples. Calculated as the sum of R723RWDS.

IDLE_STATE_CNT FLOAT Total number of idle state samples. Idle indicates that nowork request is available to the work manager that isallowed to run. Calculated as the sum of R723RIDL.

IO_STATE_CNT FLOAT Total number of waiting for I/O state samples. Calculatedas the sum of R723RWIO.

LOCK_STATE_CNT FLOAT Total number of waiting for lock state samples. Calculatedas the sum of R723RWLO.



|


OTHER_STATE_CNT FLOAT Total number of samples taken when waiting for anotherproduct. Calculated as the sum of R723RWOS.

READY_STATE_CNT FLOAT Total number of ready state samples. Calculated as thesum of R723RRDY.

REGT_STATE_CNT FLOAT Total number of waiting for regular thread samples. FromR723RWRT.

REPORT_PERIOD_FLAG CHAR(1) Report class period flag: 1=Heterogeneous class (more thanone service class for the same report class),0=Homogeneous report class period (only one service classfor this report class). Blank if this is a service class period.From R723CRS1.

RWRK_STATE_CNT FLOAT Total number of waiting for registration to work table.From R723RWWR.




SES_LOC_STATE_CNT FLOAT Total number of samples taken when waiting for a sessionto be established locally. Calculated as the sum ofR723RWSL.

SES_NET_STATE_CNT FLOAT Total number of samples taken when waiting for a sessionto be established somewhere in the network. Calculated asthe sum of R723RWSN.

SES_SPX_STATE_CNT FLOAT Total number of samples taken when waiting for a sessionto be established somewhere in the sysplex. Calculated asthe sum of R723RWSS.

SSLT_STATE_CNT FLOAT Total number of waiting for SSL thread samples. FromR723RWST.


SYSPLEX_NAME CHAR(8) Sysplex name (as defined in ECVTSPLX). FromSMF72XNM.



TIMER_STATE_CNT FLOAT Total number of samples taken when waiting for a timer.Calculated as the sum of R723RWTM.

TOTAL_STATE_CNT FLOAT Total number of transaction states sampled. Calculated asthe sum of R723RESS.

UNIDENT_STATE_CNT FLOAT Total number of samples taken when waiting forunidentified resource. Calculated as the sum ofR723RWMS.

WLM_SAMPLES_TOT FLOAT Total number of times WLM sampling code ran. Calculatedas the sum of R723MTVÄ.



|

|

|

|

|

MVSPM_WORKLOAD_HThis table provides statistics on MVS activity by workload type and performancegroup. It contains data from SMF type 72, subtype 1 records.

This table is updated by the MVS_WORKLOAD_TYPE and MVSPM_TIME_RESlookup tables.













ELAPSED_SEC_SQSUM FLOAT sum of the squares of the elapsed times accumulated byall ended transactions, in square-seconds. Calculated asthe sum of SMF72ET1*0.000 001 048 576.

ES_FRAME_SECONDS FLOAT Expanded storage frame-residency time, in seconds. Thisis the active frame-time for frames in expanded storage.Calculated as the sum of SMF72ER*0.001 024.

ESTOR_IND CHAR(1) Indicates whether the system has expanded storage; 1 =yes, 0 = no. From the first bit of SMF72PRF.

HIPER_SERVICE_SEC FLOAT Time used for hiperspace service, in seconds. Calculatedas the sum of SMF72HST/1 000 000.


IO_RATE_FACTOR FLOAT Total I/O service units divided by the I/O servicedefinition coefficient. Calculated as the sum ofSMF72ITS/SMF72ISD.

IOINTR_SEC FLOAT Time used for processing I/O interrupts, in seconds.Calculated as the sum of SMF72IIT/1 000 000.

PAGEINS FLOAT Number of page-ins. This is the sum of SMF72PIN.

PAGEINS_BLK FLOAT Number of blocked pages that were paged in. This is thesum of SMF72BPI.




PAGEINS_BLK_AUX FLOAT Number of blocked pages that were paged in fromauxiliary storage. This is the sum of SMF72BKA.

PAGEINS_BLK_ES FLOAT Number of blocked pages that were page in fromexpanded storage. This does not include the first page ofeach block. This is the sum of SMF72BPE.

PAGEINS_BLK_ES_TOT FLOAT Total number of blocked pages that were paged in fromexpanded storage. This is the sum of SMF72BKE.

PAGEINS_HIPER FLOAT Number of page-ins of hyperspaces. This is the sum ofSMF72HIN.

PAGEINS_SHARED FLOAT Total shared page-ins from auxiliary storage. This is thesum of SMF72SPA.

PAGEINS_SHARED_ES FLOAT Total shared page-ins from expanded storage. This is thesum of SMF72SPE.

PAGEINS_UNBLK_ES FLOAT Total number of unblocked pages that were paged infrom expanded storage. This includes the first page ofeach block. This is the sum of SMF72PIE.

PERF_GROUP_TYPE CHAR(1) Performance group (PG) type. This can be: C for control,or R for reporting. All data in reporting PGs is alsoreported in a control PG, so when summaries areproduced, only control PGs should be selected. FromSMF72FGI.

RCT_SEC FLOAT Region control task time, in seconds. Calculated as thesum of SMF72RCT*1 000 000.

READ_MISSES_HIPER FLOAT Number of hiperspace read misses (a read miss is anattempt to read a frame that is not in expanded storage).This is the sum of SMF72HRM.


RESIDENT_SHR_SEC FLOAT Total shared page residency, in seconds. Calculated as thesum of SMF72SRS*0.001024.

RESPONSE_MAX_SEC FLOAT Maximum response time, in seconds. Calculated as themaximum of SMF72TTM/SMF72TTX.


RMF_VERSION SMALLINT RMF version number. From SMF72MFV.

SERVICE_UNITS_MAX FLOAT Maximum service units per CPU-second. Calculated asthe maximum of 16 000 000/SMF72ADJ.

SRB_TIME_FACTOR FLOAT Total SRB service units divided by the SRB servicedefinition coefficient. Calculated as the sum ofSMF72STS/SMF72SSD.

SUBSYSTEM_ID CHAR(4) Name of the subsystem associated with the performancegroup number. From SMF72SYS.

SWAP_SEQUENCES FLOAT Number of address space swap sequences. A swapsequence consists of an address space swap-out andswap-in. This is the sum of SMF72SPP.






TCB_TIME_FACTOR FLOAT Total CPU service units divided by the CPU servicedefinition coefficient. Calculated as the sum ofSMF72CTS/SMF72CSD.


TOT_FRAME_SECONDS FLOAT Active frame-time for all frames in central and expandedstorage, in seconds. Calculated as the sum ofSMF72FT*0.001 024.

TRAN_ACTIVE_SEC FLOAT Active time of all transactions, in seconds. This includesthe total time that each transaction was in central storageplus any swap-out time (long wait state time is notincluded). Calculated as the sum of SMF72ACT*0.001 024.

TRAN_ELAPSED_SEC FLOAT Elapsed time accumulated by all transactions that endedin this performance group period, in seconds. Calculatedas the sum of SMF72TTM*0.001 024.

TRAN_RESIDENT_SEC FLOAT Transaction residency time, in seconds. This includes thetotal time that each transaction was in central storage. Itdoes not include the time between job steps for batchtransactions. Calculated as the sum ofSMF72TAT*0.001 024.

TRAN_TOT_SEC FLOAT Total system transaction time of ended transactions, inseconds. This time is measured from the point of entry tothe point of termination. Calculated as the sum ofSMF72TST*0.001 024.

TRANSACTIONS FLOAT Number of transactions ended. This is the sum ofSMF72TTX.



MVSPM_WORKLOAD2_HThis table provides hourly statistics on MVS activity by workload type and serviceclass, when the system is running in goal mode. It contains data from SMF type 72,subtype 3 records.








WORKLOAD_TYPE k CHAR(8) MVS workload type name. From WORKLOAD_TYPEin the MVS_WORKLOAD2_TYPE lookup table.




AS_DELAY_CNT FLOAT Sum of sampled address space count number ofaddress spaces that contributed delay and usingsamples to this service class. These samples are notincluded in TOTAL_DELAY_CNT. Calculated as thesum of R723CSAC.

AVG_GOAL_SEC FLOAT Average response time goal, in seconds. FromR723CVAL (converted to seconds using R723CRTF) ifR723CRGF is equal to X'40', otherwise set to 0.

AVG_FOREIGN_ENCL FLOAT Average number of foreign enclaves during theinterval. This is the average of R723CFEA.



COMM_PG_DELAY_CNT FLOAT Number of auxillary page-ins to common area delaysamples. Calculated as the sum of R723CACO.

CRYPTO_CAM_USE_CNT FLOAT CAM crypto using samples: a TCB was foundexecuting on a Cryptographic Asynchronous Messageprocessor. From R723CAMU.

CRYPTO_CAM_DEL_CNT FLOAT CAM crypto delay samples: a TCB was found waitingfor a Cryptographic Asynchronous Message processor.From R723CAMD.

CRYPTO_AP_USE_CNT FLOAT AP crypto using samples: a TCB was found executingon a cryptographic Assist Processor. From R723APU.

CRYPTO_AP_DEL_CNT FLOAT AP crypto delay samples: a TCB was found waiting fora cryptographic Assist Processor. From R723APD.



|

|

|

|

|


CRYPTO_FQ_DEL_CNT FLOAT Feature queue delay samples: a TCB was found waitingon a processor Feature Queue associated with a CPU.This is a subset of CPU_DELAY_CNT.Note: CPU_USE_CNT includes feature queue usingsamples. From R723FQD.

CPU_CAP_DELAY_CNT FLOAT Number of CPU capping delay samples. A TCB or SRBis marked non-dispatchable because a resource groupmaximum is being enforced. Note that this column isNOT a subset of CPU_DELAY_CNT. Calculated as thesum of R723CCCA.

CPU_DELAY_CNT FLOAT Number of CPU delay samples. Calculated as the sumof R723CCDE.


CPU_RGCAP_SU_MIN FLOAT Minimum capacity in unweighted CPU service units.Calculated as the sum of R723GGMN*R723INT/1000.

CPU_USE_CNT FLOAT Number of CPU using samples. Calculated as the sumof R723CCUS.


DASD_DELAY_SAMPLES REAL DASD delay samples. Calculated as the sum ofR723CIOD.

DASD_IO_QUEUE_TIME FLOAT Total DASD IOS queue time, in seconds. Calculated asthe sum of R723CIOT.

DASD_NP_CNT_TIME FLOAT Total non-paging DASD connect time, in seconds.Calculated as the sum of R723CICT.

DASD_NP_WAIT_TIME FLOAT Total nonpaging DASD wait (queue + pending) time, inseconds. Calculated as the sum of R723CIWT.

DASD_NP_DSCNT_TIME FLOAT Total nonpaging DASD disconnect time, in seconds.This does not include IOS queue time. Calculated as thesum of R723CIDT.

DASD_NP_IO_SCHAN_N REAL Total nonpaging DASD I/O start subchannel count.Calculated as the sum of R723CIRC.

DASD_USING_SAMPLES REAL DASD using samples. Only nonpaging DASD I/O cancontribute to I/O using samples. Calculated as the sumof R723CIOU.

ELAPSED_SEC_SQsum FLOAT sum of the squares of the elapsed times accumulated byall ended transactions, in seconds squared. Calculatedas the sum of R723CETS*0.000001048576.

ES_FRAME_SECONDS FLOAT Expanded storage frame-residency time, in seconds.This is the active frame-time for frames in expandedstorage. Calculated as the sum of R723CERS*0.001024.

ESOHI_PG_DELAY_CNT FLOAT Number of auxiliary page-ins to ESO hiperspaces delaysamples. Calculated as the sum of R723CCHS.

ESTOR_IND CHAR(1) Indicates whether the system has expanded storage;1=yes, 0=no. From the first bit of SMF72PRF.

EXEC_VEL_GOAL_PCT INTEGER Execution velocity goal, in percent. From R723CVAL ifR723CRGF is equal to X'20', otherwise set to 0.



|


GOAL_FLAG SMALLINT Goal flag; 0=percentile response time goal, 1=averageresponse time goal, 2=execution velocity goal,3=discretionary goal, 4=system specified goal. FromR723CRGF.

GOAL_IMPORTANCE SMALLINT Relative importance of the goal to be achieved for thisservice class period (1=highest, 5=lowest). Calculated asthe maximum of R723CIMP.

GOAL_MISSES INTEGER Number of times the response time goal or theexecution velocity goal was not met for an RMFinterval. Calculated from R723CPCT and R723CVAL.

GOAL_PERCENTILE INTEGER Percentile response time goal, in percent. FromR723CPCT if R723CRGF is equal to X'80', otherwise setto 0.

HIPER_PG_DELAY_CNT FLOAT Number of auxiliary page-ins to standard hiperspacesdelay samples. Calculated as the sum of R723CHSP.

HIPER_SERVICE_SEC FLOAT Time used for hiperspace service, in seconds.Calculated as the sum of R723CHST/1 000 000.

HPRSPACE_PG_DLY_S REAL Paging delay samples for server hiperspace. Calculatedas the sum of R723CSHS.

IDLE_CNT FLOAT Number of samples taken when idle. Calculated as thesum of R723CIDL.


IO_COUNT FLOAT Total number of I/O operations. Calculated as the sumof 10 000*R723CIOC/R723MIOC.

IOINTR_SEC FLOAT Time used for processing I/O interrupts, in seconds.Calculated as the sum of R723CIIT/1 000 000.

MEASURED_SEC FLOAT Measured time period, in seconds. This is the durationof the RMF measurement interval. Calculated as thesum of SMF72INT/1000.

MPL_DELAY_CNT FLOAT Number of MPL delay samples. Calculated as the sumof R723CMPL.

MPL_DELAY_SAMPLES REAL Server MPL delay samples. Calculated as the sum ofR723CSMP.

MVS_RESOURCE_GROUP CHAR(8) MVS resource group name. From R723GGNM.

PAGEINS FLOAT Number of page-ins. This is the sum of R723CPIR.

PAGEINS_BLK FLOAT Number of blocked pages that were paged in. This isthe sum of R723CBPI.

PAGEINS_BLK_AUX FLOAT Number of blocked pages that were paged in fromauxiliary storage. This is the sum of R723CBKA.

PAGEINS_BLK_ES FLOAT Number of blocked pages that were paged in fromexpanded storage. This does not include the first pageof each block. This is the sum of R723CBPE.

PAGEINS_BLK_ES_TOT FLOAT Total number of blocked pages that were paged in fromexpanded storage. This is the sum of R723CBKE.

PAGEINS_HIPER FLOAT Number of page-ins of hiperspaces. This is the sum ofR723CHPI.

PAGEINS_SHARED FLOAT Total shared page-ins from auxiliary storage. This is thesum of R723CSPA.




PAGEINS_SHARED_ES FLOAT Total shared page-ins from expanded storage. This isthe sum of R723CSPE.

PAGEINS_UNBLK_ES FLOAT Total number of unblocked pages that were paged infrom expanded storage. This includes the first page ofeach block. This is the sum of R723CPIE.

PERCENT_GOAL_SEC FLOAT Response time goal, in seconds. From R723CVAL(converted to seconds using R723CRTF) if R723CRGF isequal to X'80', otherwise set to 0. GOAL_PERCENTILEpercent of all transactions should be completed withinPERCENT_GOAL_SEC seconds.

PRIV_PG_DELAY_CNT FLOAT Number of auxiliary page-ins to private area delaysamples. Calculated as the sum of R723CAPR.

PRVT_AREA_PG_DLY_S REAL Paging delay samples for server private area.Calculated as the sum of R723CSPV.

QUEUE_DELAY_SAMPLE REAL Queue delay samples, work is waiting for a server.Calculated as the sum of R723CQ.

QUEUE_DELAY_TIMEF FLOAT Total queue delay time, in seconds. Calculated as thesum of R723CQDT.

QUIESCE_DELAY_CNT FLOAT Number of delay samples taken due to quiesce.Calculated as the sum of R723CPQU.

RCT_SEC FLOAT Region control task time, in seconds. Calculated as thesum of R723CRCT/1 000 000.

READ_MISSES_HIPER FLOAT Number of hiperspace read misses (a read miss is anattempt to read a frame that is not in expandedstorage). This is the sum of R723CCRM.


REPORT_PERIOD_FLAG CHAR(1) Report class period flag: 1=Heterogeneous class (morethan one service class for the same report class),0=Homogeneous report class period (only one serviceclass for this report class). Blank if this is a service classperiod. From R723CRS1.

RES_CAP_DELAY_CNT FLOAT Number of delay samples taken due to resource groupcapping. Calculated as the sum of R723CPDE.

RESIDENT_SHR_SEC FLOAT Total shared page residency, in seconds. Calculated asthe sum of R723CSRS*0.001024.

RESPONSE_MAX_SEC FLOAT Maximum response time, in seconds. Calculated as themaximum of (R723CTET*0.001024)/R723CRCP.

RMF_INTERVAL FLOAT Duration of the RMF measurement interval, in minutes.From SMF72INT.

RMF_VERSION SMALLINT RMF version number. From SMF72MFV.

SERV_CLASS_TYPE CHAR(1) Service class (SC) type. This can be C (control), or R(reporting). All data in reporting SCs is also reported ina control SC. So, when summaries are produced, onlycontrol SCs should be selected. From R723MSCF.

SERVICE_CLASS_DUR INTEGER Service class period duration, in service units, or zerofor last period. Calculated as the maximum ofR723CDUR.



|


SERV_FOR_REPORT CHAR(8) Service class that last contributed to this report class.Blank if this is a service class. From R723CLSC.


SERVICE_UNITS FLOAT Total number of weighted service units. This is the sumof R723CSRV.

SERVICE_UNITS_CPU FLOAT Total CPU weighted service units. This is the sum ofR723CCPU.


SERVICE_UNITS_MAX FLOAT Maximum service units per CPU-second. Calculated asthe maximum of 16 000 000/R723MADJ.


SERVICE_UNITS_SRB FLOAT Total SRB weighted service units. This is the sum ofR723CSRB

SPACE_VIO_PG_DLY_S REAL Paging delay samples for server space VIO. Calculatedas the sum of R723CSVI.

SRB_SECONDS FLOAT SRB CPU time calculated from the number of CPUservice units, in seconds. Calculated as the sum ofR723CSRB*R723MADJ/160/R723MSRB.

SUBSYSTEM_ID CHAR(4) Name of the subsystem associated with the serviceclass. From R723RTYP.

SWAP_DELAY_CNT FLOAT Number of swap-in delay samples. Calculated as thesum of R723CSWI.

SWAP_DELAY_SAMPLES REAL Server swap-in delay samples. Calculated as the sum ofR723CSSW.

SWAP_SEQUENCES FLOAT Number of address space swap sequences. A swapsequence consists of an address space swap-out andswap-in. This is the sum of R723CSWC.

SYSPLEX_NAME CHAR(8) Sysplex name (as defined in ECVTSPLX). FromSMF72XNM.


TIME_BJ_INELIGIBLE FLOAT Total time, in seconds, that batch jobs were ineligible torun because a resource to which the job had affinitywas unavailable. Calculated as the sum of R723CADT.

TIME_BJ_JCL_CONVER FLOAT Total time, in seconds, that batch jobs spent in JCLconversion. Calculated as the sum of R723CCVT.

TIME_BJ_JOB_QUEUE FLOAT Total time, in seconds, that batch jobs spent on the jobqueue after JCL conversion, while ineligible to run onany system for reasons other than resource affinities.Calculated as the sum of R723CIQT.

TCB_SECONDS FLOAT TCB CPU time calculated from the number of CPUservice units, in seconds. Calculated as the sum ofR723CCPU*R723MADJ/160/R723MCPU.


TOTAL_DELAY_CNT FLOAT Number of total delay samples. Calculated as the sumof R723CTOT.



|


TOTAL_EXECUTION_S FLOAT Total execution samples. Calculated as the sum ofR723CTSA.

TOTAL_USING_SAMPLE REAL Total using samples. For the velocity formula, seeOS/390 MVS Planning: Workload Management. Calculatedas the sum of R723CTOU.

TOT_FRAME_SECONDS FLOAT Active frame-time for frames in central and expandedstorage, in seconds. Calculated as the sum ofR723CPRS*0.001024.

TRAN_ACTIVE_SEC FLOAT Active time of all transactions, in seconds. This includesthe total time that each transaction was in centralstorage plus any swap-out time (long wait state time isnot included). Calculated as the sum ofR723CTAT*0.001024.

TRAN_ELAPSED_SEC FLOAT Elapsed time accumulated by all transactions thatended in this service class period, in seconds.Calculated as the sum of R723CTET*0.001024.

TRAN_EXECUTION_SEC FLOAT Execution time accumulated by all transactions thatended in this service class period, in seconds.Calculated as the sum of R723CXET*0.001024.

TRAN_RESIDENT_SEC FLOAT Transaction residency time, in seconds. This includesthe total time that each transaction was in centralstorage. It does not include the time between job stepsfor batch transactions. Calculated as the sum ofR723CTRR*0.001024.

TRANSACTIONS INTEGER Count of transaction completions. This is the sum ofR723CRCP.

TRANSACTIONS_ABN INTEGER Count of transaction completed abnormally. This is thesum of R723CARC.

TRANSACTIONS_BELOW INTEGER Number of transactions that ended below or equal tothe response time goal. This is the sum of R723TRDBfor GOAL_PERCENTAGE <= 100.

TRANS_EXEC INTEGER Count of transactions that completed their executionphase. This is the sum of R723CNCP.

TRANS_EXEC_ABN INTEGER Count of transactions that completed their executionphase abnormally. This is the sum of R723CANC.

UNKNOWN_DELAY_CNT FLOAT Number of delay samples with unknown reason.Calculated as the sum of R723CUNK.

VIO_PG_DELAY_CNT FLOAT Number of auxiliary page-ins for VIO delay samples.Calculated as the sum of R723CVIO.

WLM_SAMPLE_INT FLOAT Current WLM sample interval, in milliseconds.Calculated as the maximum of R723MTVL.

WLM_SAMPLES_TOT FLOAT Total number of times WLM sampling code ran.Calculated as the sum of R723MTVÄ.

XMEM_PG_DELAY_CNT FLOAT Number of cross memory page-ins from common areadelay samples. Calculated as the sum of R723CAXM.



MVSPM_XCF_MEMBER_HThis table provides statistics on the XCF message traffic on a member basis formembers on the local system and members communicating with the local system.The data comes from SMF type 74, subtype 2 records written by Monitor III XCFmeasurement.








LOCAL_SYSTEM k CHAR(8) Name of the local system. From R742SNME in the section forthe local system.

OTHER_SYSTEM k CHAR(8) Name of the system where the member resides. FromR742MSYS.

MEMBER_GROUP k CHAR(8) Name of the group. From R742MGRP.

MEMBER k CHAR(16) Name of the member. From R742MMEM.



RECORD_LEVEL INTEGER SMF record level change number. This column enablesprocessing of SMF record level changes in an existing release.From SMF74SRL.

SIGNALS_RECEIVED FLOAT Number of signals received by the member. This is the sum ofR742MRCV.

SIGNALS_SENT FLOAT Number of signals sent by the member. This is the sum ofR742MSNT.

STATUS_FLAGS CHAR(8) Status flags. Bit 0 = the member became active during theinterval; bit 1 = the member became inactive during theinterval; bit 2 = the counts were reset by XCF during theinterval. From R742MSTF.

TIME_RESOLUTION INTEGER Time resolution used for this table, in minutes. The default is60 minutes. From TIME_RESOLUTION in theMVSPM_TIME_RES lookup table.



MVSPM_XCF_PATH_HThis table provides statistics on the XCF message traffic between signalling pathsconnecting the local system with remote systems. The data comes from SMF type74, subtype 2 records written by Monitor III XCF measurement.





TIME k TIME Time of the mid measurement. From SMF74DAT, SMF74IST,and SMF74INT.



LOCAL_SYSTEM k CHAR(8) Name of the local system. From R742PNME.

OTHER_SYSTEM k CHAR(8) Name of the system at the other end, if known; otherwise,this is blank. From R742PONA.

TRANSPORT_CLASS k CHAR(8) Transport class name. This is blank for an inbound path.From R742PTCN.

DIRECTION k CHAR(3) Direction of the path. IN = inbound path, or OUT = outboundpath. From R742PDIR.

DEVICE_NUM k CHAR(4) Device number. Blank if a XES list structure is being used.From R742PDEV.

OTHER_DEVICE_NO k CHAR(4) Number of the device at the other end, if known; otherwise,this is blank. From R742PODV.

STRUCTURE_NAME k CHAR(16) Name of XES list structure being used as a path, blank forCTCs. From R742PSTR.

AVG_IO_TRAN_TIME FLOAT Average I/O transfer time for the most recently receivedsignals for inbound paths, in seconds. From R742PIOT.

BUFFER_SPACE FLOAT Average maximum number of 1K-blocks of message bufferspace. This is the sum of R742PMXM.

BUFFER_SPACE_MAX FLOAT Maximum number of 1K-blocks of message buffer space. Thisis the maximum of R742PMXM.



PATH_TYPE CHAR(3) CTC if channel to channel or XES if an XES list structure isused. From R742PTYP.

RECORD_LEVEL INTEGER SMF record level change number. This column enablesprocessing of SMF record level changes in an existing release.From SMF74SRL.

RESTARTS FLOAT Number of restarts. This is the sum of R742PRST.

SIGNALS FLOAT Number of signals sent or received over the path. This is thesum of R742PSIG.




SIGNALS_PENDING FLOAT Number of outbound signals pending transfer on the path.This is the sum of R742PQLN.

SIGNALS_REFUSED FLOAT Number of inbound signals refused because the maximummessage limit was reached. This is the sum of R742PIBR.

STATUS_FLAGS CHAR(8) Path status. Bit 0 = starting; bit 1 = restarting; bit 2 =working; bit 3 = stopping; bit 4 = waiting for completion ofthe communication link; bits 5-7 = reserved. From R742PSTF.


TIME_RESOLUTION INTEGER Time resolution used for this table, in minutes. The default is60 minutes. From TIME_RESOLUTION in theMVSPM_TIME_RES lookup table.

TIMES_BUSY FLOAT Number of times the signalling path was busy when it wasselected to transfer a message. This is the sum of R742PAPP.

TIMES_NOT_BUSY FLOAT Number of times the signalling path was not busy when itwas selected to transfer a message. This is the sum ofR742PSUS.



MVSPM_XCF_SYS_HThis table provides statistics on the XCF message traffic between the local andremote systems. The data comes from SMF type 74, subtype 2 records written byMonitor III XCF measurement.








LOCAL_SYSTEM k CHAR(8) Name of the local system. From R742SNME in the sectionfor the local system.

OTHER_SYSTEM k CHAR(8) Name of the system at the other end. For local traffic, thisis the same as the local system. From R742SNME.

TRANSPORT_CLASS k CHAR(8) Transport class name. This is blank for inbound direction.From R742STCN.

DIRECTION k CHAR(3) Direction of the message traffic. IN = inbound (the systemsent messages to the local system); OUT = outbound (thesystem received messages from the local system); or LOC= local (the message traffic was within the local system).From R742SDIR.

BUFFER_SPACE FLOAT Average maximum number of 1K-blocks of messagebuffer space. For local or outbound direction, the count isfor the indicated transport class. This is the average ofR742SMXB.

BUFFER_SPACE_MAX FLOAT Maximum number of 1K-blocks of message buffer space.For local or outbound direction, the count is for theindicated transport class. This is the sum of R742SMXB.

FLOAT RMF sampling cycle length, in milliseconds. FromSMF74CYC.



MESSAGE_LENGTH FLOAT Message length for the transport class. This is zero forinbound direction. This is the maximum of R742STCL.

MESSAGES_BIG FLOAT Number of big-message conditions. This is zero forinbound direction. This is the sum of R742SBIG.

MESSAGES_DEGRADED FLOAT Number of big messages that exceeded the messagelength for which XCF was optimized. This is zero forinbound direction. This is the sum of R742SOVR.




MESSAGES_FIT FLOAT Number of message fit conditions. This is zero forinbound direction. This is the sum of R742SFIT.

MESSAGES_SMALL FLOAT Number of small-message conditions. This is zero forinbound direction. This is the sum of R742SSML.

NO_BUFFER_COND FLOAT Number of no buffer conditions. For local or outbounddirection, the count is for the indicated transport class.This is the sum of R742SBSY.

NO_PATH_COND FLOAT Number of no path conditions. This is zero for localdirection. For outbound direction, the count is for theindicated transport class. This is the sum of R742SNOP.




SIGNAL_PATHS FLOAT Current number of signalling paths in service. This is zerofor local direction. For outbound direction, the count isfor the indicated transport class. This is the maximum ofR742SPTH.

STATUS_FLAGS CHAR(8) Status flags. Bit 0 = the system became active during theinterval; bit 1 = the system became inactive during theinterval; bit 2 = the counts were reset by XCF during theinterval. From R742SSTF.





ViewsThis section describes the views for the MVS performance managementcomponent.

MVSPM_APPL_HVThis view provides statistics on application activity by workload type for batchjobs, TSO sessions, started tasks, and APPC sessions. It is based on theMVSPM_APPL_H table, and its data comes from SMF type 30, subtypes 2 and 3records.

Computed data columns in this view can contain incorrect values when the SMFdata is collected for only part of the time period specified in theTIME_RESOLUTION column. Normally, wrong calculations occur only on datacollected during the first or last hour. For example, if the SMF log contains datauntil 23:30, the calculations for the hour 23:00 will be wrong. But when the nextlog collected starts with data from 23:30, the calculations will be correct.


DATE k DATE Date of the mid measurement. From SMF30IDT, SMF30IST,SMF30DTE, and SMF30TME.

TIME k TIME Time (rounded down as specified in theMVSPM_TIME_RES lookup table) of the mid measurement.From SMF30IDT, SMF30IST, SMF30DTE, and SMF30TME.



WORKLOAD_TYPE k CHAR(8) MVS workload type name. From WORKLOAD_TYPE inthe MVS_WORKLOAD_TYPE orMVS_WORKLOAD2_TYPE lookup table.

PERF_GROUP_NO k CHAR(3) Performance group number. From SMF30PGN.

SERVICE_CLASS k CHAR(8) Service class name. This field is blank when in workloadmanagement compatibility mode. From SMF30SCN.

ASBLK_PAGEOUT_RATE FLOAT Number of blocked pages paged out to auxiliary storageper second. Calculated as PAGEOUTS_BLK_AUX/TIME_RESOLUTION*60.

BLK_PAGEIN_RATE FLOAT Number of blocked pages paged in from auxiliary storageper second. Calculated asPAGEINS_BLK_AUX/TIME_RESOLUTION*60.

BLOCKS_PER_TRAN FLOAT Number of blocks transferred to or from the data set (ordata sets if concatenation is used) per transaction.Calculated as BLOCKS/TRANSACTIONS.

CONNECT_PER_TRAN FLOAT Connect time per transaction, in seconds. Calculated as(CONNECT_MSEC/TRANSACTIONS)/1000.

CPU_BUSY_PCT FLOAT Total CPU time used, in percent. Calculated as the sum ofall CPU times divided by TIME_RESOLUTION*0.6.

CPU_ENQ_PROMOT_SEC FLOAT CPU time used for an address space or job while enqueuepromoted in seconds. Calculated as sum SMF30CEP/1024.

MVS performance management views


|


CPU_HIPER_PCT FLOAT Percentage of CPU time used to support data transfer toand from a hiperspace backed by expanded storage.Calculated as CPU_HIPER_SECONDS/TIME_RESOLUTION*0.6

CPU_IOINTR_PCT FLOAT Percentage of CPU time used for processing I/O interrupts.Calculated asCPU_INTR_SECONDS/TIME_RESOLUTION*0.6.

CPU_PER_TRAN FLOAT Average CPU time used per transaction, in seconds.Calculated as (TCB_STEP_SECONDS +SRB_STEP_SECONDS + TCB_INIT_SECONDS +SRB_INIT_SECONDS + CPU_INTR_SECONDS +CPU_RCT_SECONDS +CPU_HIPER_SECONDS)/TRANSACTIONS.

CPU_RCT_PCT FLOAT Percentage of CPU time used by the region control task.Calculated asCPU_RCT_SECONDS/TIME_RESOLUTION*0.6.

CPU_SRB_PCT FLOAT Percentage of CPU time spent under the service requestblock. Calculated as (SRB_STEP_SECONDS +SRB_INIT_SECONDS)/ (TIME_RESOLUTION*0.6).

CPU_TCB_PCT FLOAT Percentage of CPU time spent under the task control block.Calculated as (TCB_STEP_SECONDS +TCB_INIT_SECONDS)/ (TIME_RESOLUTION*0.6).

CSA_PAGEIN_RATE FLOAT Number of common storage area page-ins per second.Calculated asPAGEINS_COMMON/TIME_RESOLUTION*60.

CSA_PAGES_PER_TRAN FLOAT Number of CSA page-ins per transaction. Calculated asPAGEINS_COMMON/TRANSACTIONS.

DEM_PAGES_PER_TRAN FLOAT Number of demand pages per transaction. Calculated asPAGEINS/TRANSACTIONS.

EFFECTIVE_PRIORITY FLOAT Effective priority. Calculated as(PRIORITY/TCB_STEP_SECONDS)/16.

ES_PAGEOUT_RATE FLOAT Number of page-outs to expanded storage per second.Calculated asPAGEOUTS_UNBLK_ES/TIME_RESOLUTION*60.

ESBLK_PAGEIN_RATE FLOAT Number of blocked pages paged in from expanded storageper second. Calculated asPAGEINS_BLK_ES/TIME_RESOLUTION*60.

ESBLK_PAGEOUT_RATE FLOAT Number of blocked pages paged out to expanded storageper second. Calculated asPAGEOUTS_BLK_ES/TIME_RESOLUTION*60.

HS_PAGEIN_RATE FLOAT Number of hiperspace page-ins per second from auxiliarystorage. Calculated asPAGEINS_HIPER/TIME_RESOLUTION*60.

HS_PAGEOUT_RATE FLOAT Number of hiperspace page-outs per second. Calculated asPAGEOUTS_HIPER/TIME_RESOLUTION*60.

HS_PAGES_PER_TRAN FLOAT Number of hiperspace page-ins per transaction. Calculatedas PAGEINS_HIPER/TRANSACTIONS.

HS_READ_MISS_RATE FLOAT Number of hiperspace read misses per second. Calculatedas READ_MISSES_HIPER/TIME_RESOLUTION*60.

INELIGIBLE_TIME_1 FLOAT Job ineligible for execution time, in seconds. Schedulingenvironment is not available. This is the sum of SMF30RQT.




INELIGIBLE_TIME_2 FLOAT Job ineligible for execution time, in seconds. Job hold, jobclass hold, job queue hold, duplicate jobname, or jobexecution limits. This is the sum of SMF30HQT.

INSTORAGE_USERS FLOAT Average number of users in storage. Calculated asTRAN_RESIDENT_SEC /(TIME_RESOLUTION*60).

LPA_PAGEIN_RATE FLOAT Number of link pack area page-ins per second. Calculatedas PAGEINS_LPA/TIME_RESOLUTION*60.

LPA_PAGES_PER_TRAN FLOAT Number of LPA page-ins per transaction. Calculated asPAGEINS_LPA/TRANSACTIONS.

MEMLIT_MB FLOAT Memory limit value (in MB). This is the maximumoccurrence of SMF30MEM.

OUTREADY_PER_TRAN FLOAT Average out ready time used per transaction, in seconds.Calculated as (TRAN_ACTIVE_SEC −TRAN_RESIDENT_SEC)/ TRANSACTIONS.

OUTREADY_USERS FLOAT Average number of users that were swapped out but wereready. Calculated as (TRAN_ACTIVE_SEC −TRAN_RESIDENT_SEC)/(TIME_RESOLUTION*60).

PA_PAGEIN_RATE FLOAT Number of private area page-ins per second. Calculated asPAGEINS/TIME_RESOLUTION*60.

PAGEIN_RATE FLOAT Total number of non-VIO page-ins per second. Calculatedas (PAGEINS + PAGEINS_LPA + PAGEINS_COMMON)/TIME_RESOLUTION*60.

PAGEIN_TCB_RATE FLOAT Number of page-ins per TCB second. Calculated asPAGEINS/TCB_STEP_SECONDS.

PAGEINS_PER_TRAN FLOAT Total number of page-ins per transaction. Calculated as(PAGEINS_HIPER + PAGEINS + PAGEINS_LPA +PAGEINS_COMMON)/TRANSACTIONS.

PREPARATION_TIME FLOAT Job preparation time, in seconds. This is the elapsed timebefore the job was first queued for execution. This is thesum of SMF30JQT.

RESPONSE_SEC FLOAT Average transaction response time, in seconds. Calculatedas TRAN_ACTIVE_SEC/TRANSACTIONS.

SCALAR_USAGE_PCT FLOAT Percentage of scalar usage. Calculated as((TCB_STEP_SECONDS + SRB_STEP_SECONDS +TCB_INIT_SECONDS + SRB_INIT_SECONDS +CPU_INTR_SECONDS + CPU_RCT_SECONDS +CPU_HIPER_SECONDS) − (VU_STEP_SECONDS +VU_INIT_SECONDS)) /(TIME_RESOLUTION*0.6).

SCHEDULING_ENV FLOAT Scheduling environment name. This field is blank if noscheduling environment is specified. From SMF30PFL.

SHARED_PAGEIN_RATE FLOAT Number of page-ins for shared page groups per second.Calculated as PAGEINS_SHARED/TIME_RESOLUTION*60

STORAGE_USED_MB FLOAT Total storage used, in megabytes. Calculated as(TRAN_RESIDENT_SEC /(TIME_RESOLUTION*60))*((CS_FRAME_SECONDS /TRAN_RESIDENT_SEC)/256).

SHARED_PAGEIN_RATE FLOAT Number of page-ins for shared page groups per second.Calculated asPAGEINS_SHARED/TIME_RESOLUTION*60.

SHARED_PAGE_SEC FLOAT Number of CPU page seconds for the IARVSERV sharedcentral storage frames in use by this address space, inseconds. This is the sum of SMF30PSF*0.001.



|


SMF_INTERVAL FLOAT Duration of the SMF measurement interval, in minutes.Calculated as SMF30DTE and SMF30TME, minusSMF30IDT and SMF30IST, divided by 60.

SRB_INIT_SECONDS FLOAT Initiator CPU time under SRB, in seconds. Calculated as thesum of SMF30ISB/100 for records where bit 0 or bit 5 ofSMF30TFL is 0.

SRB_PREEMP_SECONDS FLOAT Additional CPU time accumulated by the preemptableSRBs and client SRBs for this job, in seconds. This value isalso included in the value in TCB_STEP_SECONDS.Calculated as the sum of SMF30ASR/100 for records wherebit 0 or bit 12 of SMF30TFL is 0.


STORAGE_USED_MB FLOAT Total storage used, in megabytes. Calculated as(TRAN_RESIDENT_SEC /(TIME_RESOLUTION*60)) *((CS_FRAME_SECONDS /TRAN_RESIDENT_SEC)/256).

SWAP_SEQUENCES FLOAT Number of address space swap sequences. This is the sumof SMF30NSW.


TGET_PER_TRAN FLOAT Number of TGETs per transaction. Calculated asTGET_COUNT/TRANSACTIONS.

THINK_SEC FLOAT Average think time per transaction, in seconds. Calculatedas (MEASURED_SEC −TRAN_ACTIVE_SEC)/TRANSACTIONS.

TPUT_PER_TRAN FLOAT Number of TPUTs per transaction. Calculated asTPUT_COUNT/TRANSACTIONS.

TRAN_PER_MIN FLOAT Number of transactions per minute. Calculated asTRANSACTIONS/TIME_RESOLUTION.

TRAN_PER_SEC FLOAT Number of transactions per second. Calculated asTRANSACTIONS/TIME_RESOLUTION*60.

UNBLK_PAGEIN_RATE FLOAT Number of unblocked pages paged in from expandedstorage per second. Calculated asPAGEINS_UNBLK_ES/TIME_RESOLUTION*60.

USERS FLOAT Average number of users logged on to the system.Calculated as MEASURED_SEC/(TIME_RESOLUTION*60).

VECTOR_AFFIN_PCT FLOAT Percentage of vector affinity time used. Calculated as(VA_STEP_SECONDS + VA_INIT_SECONDS)/(TIME_RESOLUTION*0.6).

VECTOR_FREE_PCT FLOAT Percentage of vector affinity that was not used. Calculatedas ((VA_STEP_SECONDS + VA_INIT_SECONDS) −(VU_STEP_SECONDS + VU_INIT_SECONDS))/(TIME_RESOLUTION*0.6).

VECTOR_USAGE_PCT FLOAT Percentage of vector time used. Calculated as(VU_STEP_SECONDS + VU_INIT_SECONDS)/(TIME_RESOLUTION*0.6).

VIO_PAGEIN_RATE FLOAT Number of virtual I/O page-ins per second. Calculated asPAGEINS_VIO/TIME_RESOLUTION*60.





WORKING_SET_MB FLOAT Average processor storage per user, in megabytes.Calculated asCS_FRAME_SECONDS/TRAN_RESIDENT_SEC/256.

Note: In addition to the calculated columns described here, this view also containsall the data columns described in “MVSPM_APPL_H” on page 604.



MVSPM_CACHE_HVThis view provides statistics on the activity of cache subsystems (IBM 3880 Model13 or Model 23, and IBM 3990 Model 03 cache controllers). It is based on theMVSPM_CACHE_H table, and its data comes from SMF records written by theCache RMF Reporter.


BOUND_TRACK_READS FLOAT Number of read requests to bound tracks. This is thesum of RDF5RRBT.

BOUND_TRACK_WRITES FLOAT Number of write requests to bound tracks. This is thesum of RDF5WRBT.

BYPASS_CACHE_RATE FLOAT Number of bypass cache I/O requests per second.Calculated as BYPASS_CACHE_REQ/MEASURED_SEC.

BYPASS_CACHE_REQ FLOAT Number of bypass cache I/O requests. This is the sum ofRDF9BPCR, RDF8BPCR or RDF7BPCR.

CACHE_CHAN_XFER FLOAT Number of cache-to-channel data transfer operations.This is the sum of RDF7CCDT.

CACHE_DASD_RATE FLOAT Number of cache-to-DASD data transfer operations persecond. Calculated asCACHE_DASD_XFER/MEASURED_SEC.

CACHE_DASD_XFER FLOAT Number of cache-to-DASD data transfer operations. Thisis the sum of RDF9CDTO or RDF8CDTO.

CACHE_HITS_ALL_PCT FLOAT Percentage of all I/O requests that are hits. Calculated as((NORM_READ_HITS + SEQ_READ_HITS +CFW_READ_HITS + NORM_WRITE_HITS +SEQ_WRITE_HITS +CFW_WRITE_HITS)/IO_REQUESTS_TOT)*100.

CACHE_HITS_PCT FLOAT Percentage of all catchable I/O requests that are hits.Calculated as ((all read hits + all write hits)/(IO_REQUESTS_TOT - BYPASS_CACHE_REQ -INHIBIT_CACHE_LOAD - NORM_WRITE_THRU -SEQ_WRITE_THRU_REQ - NONCACHED_VOL_REQ -DFW_INHIBIT_REQ))*100.

CACHE_RESOLVED_REQ FLOAT Number of I/O requests resolved in the cache.Calculated as NORM_READ_HITS + SEQ_READ_HITS +CFW_READ_HITS + NORM_WRITE_HITS +SEQ_WRITE_HITS + CFW_WRITE_HITS.

CACHE_RESOLVE_RATE FLOAT Number of I/O requests resolved in the cache persecond. Calculated as (NORM_READ_HITS +SEQ_READ_HITS + CFW_READ_HITS +NORM_WRITE_HITS + SEQ_WRITE_HITS +CFW_WRITE_HITS)/ MEASURED_SEC.

CACHE_SUBSYSTEM_ID CHAR(4) For a 3990 model 3 or 6, this is the ID for the cachesubsystem; for a 3880 model 23 or 13, this is the storagedirector ID. From RDF9SSID, RDF8SSID or RF7SDID.

CACHING_ACTIVE_IND CHAR(3) Indicates whether caching is active for the DASDvolume. This is YES or NO. From RDF9DEV1 orRDF8DEV1. For a 3880 Model 23 or 13, this is set to NOif the number of read I/Os is greater than 200, and thesum of normal and sequential hits is 0.




CFW_HIT_PCT FLOAT Percentage of cache fast write requests that are hits.Calculated as ((CFW_READ_HITS +CFW_WRITE_HITS)/ (CFW_READ_REQ +CFW_WRITE_REQ))*100.

CFW_HIT_RATE FLOAT Number of cache fast write hits per second. Calculated as(CFW_READ_HITS +CFW_WRITE_HITS)/MEASURED_SEC.

CFW_READ_HIT_RATE FLOAT Number of cache fast write read hits per second.Calculated as CFW_READ_HITS/MEASURED_SEC.

CFW_READ_HITS FLOAT Number of cache fast write read hits. This is the sum ofRDF9SRCH or RDF8SRCH.

CFW_READ_MISSES FLOAT Number of cache fast write read misses. Calculated asCFW_READ_REQ - CFW_READ_HITS.

CFW_READ_REQ FLOAT Number of cache fast write read requests. This is the sumof RDF9SRCD or RDF8SRCD.

CFW_WRITE_HIT_RATE FLOAT Number of cache fast write hits per second. Calculated asCFW_WRITE_HITS/MEASURED_SEC.

CFW_WRITE_HITS FLOAT Number of cache fast write hits. This is the sum ofRDF9WCDH or RDF8WCDH.

CFW_WRITE_MISSES FLOAT Number of cache fast write misses. Calculated asCFW_WRITE_REQ - CFW_WRITE_HITS.

CFW_WRITE_REQ FLOAT Number of cache fast write requests. This is the sum ofRDF9WCD or RDF8WCD.

CONTROL_UNIT_MODEL CHAR(8) Model number of the cache subsystem. From R745CCMT.

DASD_CACHE_CH_XFER FLOAT Number of DASD-to-cache-and-channel data transferoperations. This is the sum of RDF7DCCT.

DASD_CACHE_XFER FLOAT Number of DASD-to-cache data transfer operations. Thisis the sum of RDF7DCCD.

DASD_CHANNEL_XFER FLOAT Number of DASD-to-channel data transfer operations.This is the sum of RF7DCDT.

DASD_RESOLVED_REQ FLOAT Number of I/O requests resolved from the DASD.Calculated as ((IO_REQUESTS_TOT) -(NORM_READ_HITS + SEQ_READ_HITS +CFW_READ_HITS + NORM_WRITE_HITS +SEQ_WRITE_HITS + CFW_WRITE_HITS)).

DASD_RESOLVE_RATE FLOAT Number of I/O requests resolved from the DASD persecond. Calculated as ((IO_REQUESTS_TOT) -(NORM_READ_HITS + SEQ_READ_HITS +CFW_READ_HITS + NORM_WRITE_HITS +SEQ_WRITE_HITS + CFW_WRITE_HITS))/MEASURED_SEC.

DATE DATE Date of the mid measurement. From SMFFxDTE,SMFFxTME, and SMFFxINT.

DEVICE_NUM CHAR(4) Device number. From RDF9UNIT, RDF8UNIT,RF7UNIT1, RF5UNIT1 or RDF9DEVN, RDF8DEVN,RDF7DEVN if 4 bytes device address.

DEVICES SMALLINT Number of devices under the cache subsystem. FromSMFFxNDV.




DFW_ACTIVE_IND CHAR(3) Indicates whether DASD fast write is active for theDASD volume. This is YES or NO. From RDF9DEV1,RDF8DEV1.

DFW_HIT_RATE FLOAT Number of DASD fast write hits per second. Calculatedas (NORM_WRITE_HITS +SEQ_WRITE_HITS)/MEASURED_SEC.

DFW_HITS_PCT FLOAT Percentage of DASD fast write requests that are hits.Calculated as ((NORM_WRITE_HITS +SEQ_WRITE_HITS)/ (DFW_NORMAL_REQ +DFW_SEQ_REQ))*100.

DFW_INHIBIT_RATE FLOAT Number of DASD fast write inhibit requests per second.Calculated as DFW_INHIBIT_REQ/MEASURED_SEC.

DFW_INHIBIT_REQ FLOAT Number of DASD fast write inhibit requests (only 3990).Calculated as RDFxWCR + RDFxWSR - RDFxFWCR -RDFxFWSR.

DFW_NORMAL_REQ FLOAT Number of DASD fast write normal caching requests.This is the sum of RDF9FWCR or RDF8FWCR.

DFW_RETRIES FLOAT Number of DASD fast write retries. This is the sum ofRDF9FWDC or RDF8FWDC.

DFW_RETRY_RATE FLOAT Number of DASD fast write retries per second.Calculated as DFW_RETRIES/MEASURED_SEC.

DFW_SEQ_REQ FLOAT Number of DASD fast write sequential requests. This isthe sum of RDF9FWSR or RDF8FWSR.

DFW_STAGES FLOAT Number of DASD fast write staging operations (only3990). Calculated as RDFxFWCR + RDFxFWSR -RDFxWCRH - RDFxWSRH - RDFxFWDC.

DFW_STAGING_RATE FLOAT Number of DASD fast write staging operations persecond. Calculated as DFW_STAGES/MEASURED_SEC.

DUALCOPY_PRIMARY CHAR(3) Indicates whether the DASD volume is a primaryvolume in a duplex pair. This is YES or NO. FromRDF9DEV1 or RDF8DEV1.

DUALCOPY_SECONDARY CHAR(3) Indicates whether the DASD volume is a secondaryvolume in a duplex pair. This is YES or NO. FromRDF9DEV1 or RDF8DEV1.

INHIBIT_CACHE_LOAD FLOAT Number of inhibit cache loading requests. This is thesum of RDF9ICLR, RDF8ICLR, RF7ICLR, or RF5ICLR.

INHIBIT_CACHE_RATE FLOAT Number of inhibit cache loading requests per second.Calculated asINHIBIT_CACHE_LOAD/MEASURED_SEC.

INHIBIT_RATE FLOAT Number of inhibit cache loading and DASD fast writeinhibit requests per second. Calculated as(INHIBIT_CACHE_LOAD +DFW_INHIBIT_REQ)/MEASURED_SEC.

INHIBIT_REQ FLOAT Number of inhibit cache loading and DASD fast writeinhibit requests. Calculated as INHIBIT_CACHE_LOAD+ DFW_INHIBIT_REQ.

INPUT_RECORDS FLOAT Number of SMF records collected during the time periodspecified in the TIME_RESOLUTION column.




IO_REQUESTS_TOT FLOAT Total number of I/O operations. Calculated asNORM_READ_REQ + SEQ_READ_REQ +CFW_READ_REQ + NORM_WRITE_REQ +SEQ_WRITE_REQ + CFW_WRITE_REQ +BYPASS_CACHE_REQ + INHIBIT_CACHE_LOAD.

IO_TOT_RATE FLOAT Number of I/O operations per second. Calculated as(NORM_READ_REQ + SEQ_READ_REQ +CFW_READ_REQ + NORM_WRITE_REQ +SEQ_WRITE_REQ + CFW_WRITE_REQ +BYPASS_CACHE_REQ + INHIBIT_CACHE_LOAD)/MEASURED_SEC.

MEASURED_SEC FLOAT Measured time period, in seconds. This is the duration ofthe RMF measurement intervals. This is the sum ofSMFFxINT.

MVS_SYSTEM_ID CHAR(4) MVS system ID. This is the SMF system ID. FromSMFFxSID.

NONCACHED_VOL_RATE FLOAT Number of I/O operations per second against a DASDvolume with caching disabled. Calculated asNONCACHED_VOL_REQ/MEASURED_SEC.

NONCACHED_VOL_REQ FLOAT Number of I/O requests against a DASD volume withcaching disabled (only 3990). Calculated as RDFxSRCR +RDFxRSR + RDFxWCR + RDFxWSR + RDFxSRCD +RDFxWCD + RDFxICLR + RDFxBPCR.

NORM_DASD_CAC_RATE FLOAT Number of normal DASD-to-cache transfer operationsper second. Calculated asNORM_DASD_TO_CACHE/MEASURED_SEC.

NORM_DASD_TO_CACHE FLOAT Number of normal DASD-to-cache data transferoperations. This is the sum of RDF9DCTO, RDF8DCTO,RF7DCTO, or RF5DCTO.

NORM_DFW_HITS_PCT FLOAT Number of normal write request hits, as a percentage ofthe total number of normal DASD fast write requests.Calculated as(NORM_WRITE_HITS/DFW_NORMAL_REQ)*100.

NORM_READ_HIT_RATE FLOAT Number of normal read request hits per second.Calculated as NORM_READ_HITS/MEASURED_SEC.

NORM_READ_HITS FLOAT Number of normal read request hits. From RDF9SRRH,RDF8SRRH, RF7SRCRH, or RF5SRCH.

NORM_READ_HITS_PCT FLOAT Number of normal read request hits, as a percentage ofthe total number of normal read requests. Calculated as(NORM_READ_HITS/NORM_READ_REQ)*100.

NORM_READ_MISSES FLOAT Number of normal read request misses. Calculated asNORM_READ_REQ - NORM_READ_HITS.

NORM_READ_REQ FLOAT Number of normal read requests. This is the sum ofRDF9SRCR or RDF8SRCR, RF7SRCR, or RF5SRCR.

NORM_READ_STAGES FLOAT Number of normal read DASD staging operations.Calculated as RDF8SRCR - RDF8SRRH or RDF9SRCR -RDF9SRRH.

NORM_READ_STG_RATE FLOAT Number of normal DASD staging operations per second.Calculated as NORM_READ_STAGES/MEASURED_SEC.

NORM_WRITE_HITS FLOAT Number of normal write request hits. From RDF9WCRHor RDF8WCRH.




NORM_WRITE_MISSES FLOAT Number of normal write request misses. Calculated asNORM_WRITE_REQ - NORM_WRITE_HITS.

NORM_WRITE_REQ FLOAT Number of normal write requests. This is the sum ofRDF9WCR, RDF8WCR, RF7WCR, or RF5WCR.

NORM_WRITE_STAGES FLOAT Number of normal write staging operations. Calculatedas RDF8WCR - RDF8WCRH or RDF9WCR -RDF9WCRH.

NORM_WRITE_TH_RATE FLOAT Number of normal write through requests per second.Calculated as NORM_WRITE_THRU/MEASURED_SEC.

NORM_WRITE_THRU FLOAT Number of normal write through requests. Calculated asRDF8WCR - RDF8FWCR, or RDF9WCR - RDF9FWCR.

NORM_WRIT_HIT_RATE FLOAT Number of normal DASD fast write hits per second.Calculated as NORM_WRITE_HITS/MEASURED_SEC.

PERIOD_NAME CHAR(8) Name of the period. This is derived using fieldsSMFFxDTE, SMFFxTME, and SMFFxINT from the recordas parameters in the PERIOD function.

READ_HIT_RATE FLOAT Number of normal and sequential read hits per second.Calculated as (NORM_READ_HITS +SEQ_READ_HITS)/MEASURED_SEC.

READ_HITS_PCT FLOAT Percentage of all read requests that are hits. Calculated as((NORM_READ_HITS + SEQ_READ_HITS +CFW_READ_HITS)/(NORM_READ_REQ +SEQ_READ_REQ + CFW_READ_REQ))*100.

READ_REQUESTS_PCT FLOAT Percentage of all I/O operations that are read requests.Calculated as ((NORM_READ_REQ + SEQ_READ_REQ+ CFW_READ_REQ)/(IO_REQUESTS_TOT))*100.

READ_REQUESTS_TOT FLOAT Total number of read requests. Calculated asNORM_READ_REQ + SEQ_READ_REQ +CFW_READ_REQ.

SEQ_DASD_CAC_RATE FLOAT Number of sequential DASD-to-cache transfer operationsper second. Calculated asSEQ_DASD_TO_CACHE/MEASURED_SEC.

SEQ_DASD_TO_CACHE FLOAT Number of sequential DASD-to-cache data transferoperations. This is the sum of RDF9SCTO, RDF8SCTO orRDF7SCTO.

SEQ_DFW_HIT_PCT FLOAT Number of sequential write request hits, as a percentageof the total number of sequential DASD fast writerequests. Calculated as(SEQ_WRITE_HITS/DFW_SEQ_REQ)*100.

SEQ_READ_HIT_RATE FLOAT Number of sequential read hits per second. Calculated asSEQ_READ_HITS/MEASURED_SEC.

SEQ_READ_HITS FLOAT Number of sequential read hits. From RDF9RSRH,RDF8RSRH or RF7RSRH.

SEQ_READ_HITS_PCT FLOAT Number of sequential read request hits, as a percentageof the total number of sequential read requests.Calculated as (SEQ_READ_HITS/SEQ_READ_REQ)*100.

SEQ_READ_MISSES FLOAT Number of sequential read request misses. Calculated asSEQ_READ_REQ - SEQ_READ_HITS.

SEQ_READ_REQ FLOAT Number of sequential read requests. This is the sum ofRDF9RSR, RDF8RSR or RF7RSR.




SEQ_READ_STAGES FLOAT Number of sequential read DASD staging operations.Calculated as RDF8RSR - RDF8RSRH or RDF9RSR -RDF9RSRH.

SEQ_READ_STG_RATE FLOAT Number of sequential read DASD staging operations persecond. Calculated asSEQ_READ_STAGES/MEASURED_SEC.

SEQ_WRITE_HIT_RATE FLOAT Number of sequential write hits per second. Calculatedas SEQ_WRITE_HITS/MEASURED_SEC.

SEQ_WRITE_HITS FLOAT Number of sequential write request hits. FromRDF9WSRH or RDF8WSRH.

SEQ_WRITE_MISSES FLOAT Number of sequential write request misses. Calculated asSEQ_WRITE_REQ - SEQ_WRITE_HITS.

SEQ_WRITE_REQ FLOAT Number of sequential write requests. This is the sum ofRDF9WSR, RDF8WSR, RF7WSR, or RF5WSR.

SEQ_WRITE_STAGES FLOAT Number of sequential write staging operations (only3990). Calculated as RDFxWSR - RDFxWSRH orRDFxWSR - RDFxWSRH.

SEQ_WRITE_THR_RATE FLOAT Number of sequential write through requests per second.Calculated asSEQ_WRITE_THRU_REQ/MEASURED_SEC.

SEQ_WRITE_THRU_REQ FLOAT Number of sequential write through requests. Calculatedas RDF8WSR - RDF8FWSR or RDF9WSR - RDF9FWSR.

STAGES_TOT FLOAT Total number of staging operations. Calculated asNORM_READ_STAGES + SEQ_READ_STAGES +DFW_STAGES.

STAGING_RATE FLOAT Number of all staging operations per second. Calculatedas (NORM_READ_STAGES + SEQ_READ_STAGES +DFW_STAGES)/MEASURED_SEC.

STATISTICS_INT_SEC FLOAT Time that passed since the cache subsystem statisticswere last reported, in seconds. From SMFFxINT.

SUBSYS_STOR_AVAIL FLOAT Amount of subsystem storage available for caching, inmegabytes. From BSAVAIL, CSAVAIL, GSAVAIL, orSSAVAIL.

SUBSYS_STOR_CONFIG FLOAT Configured subsystem storage, in megabytes. This is theamount of storage that exists in the cache for thesubsystem. From BSCONF, CSCONF, GSCONF, orSSCONF.

TIME TIME Time (rounded down as specified in theMVSPM_TIME_RES lookup table) of the midmeasurement. From SMFFxDTE, SMFFxTME, andSMFFxINT.


VOLSER CHAR(6) Volume serial ID of the device. From RDF9VOL,RDF8VOL, RF7VOL, or RF5VOL.

WRITE_REQUESTS_TOT FLOAT Total Number of write requests. Calculated asNORM_WRITE_REQ + SEQ_WRITE_REQ +CFW_WRITE_REQ.




WRITE_THRU_RATE FLOAT Number of sequential write through requests and normalwrite through requests per second. Calculated as(NORM_WRITE_THRU +SEQ_WRITE_THRU_REQ)/MEASURED_SEC.

WRITE_THRU_REQ FLOAT Number of sequential write through requests and normalwrite through requests. Calculated asNORM_WRITE_THRU + SEQ_WRITE_THRU_REQ.

Note: In addition to the calculated columns described here, this view also containsall the data columns described in “MVSPM_CACHE_H” on page 610.



MVSPM_CF_PROC_HVThis view provides data about coupling facility processor and storage utilization ina sysplex. It is based on the MVSPM_CF_PROC_H table, and its data comes fromSMF type 74, subtype 4 records. It has the following fields:






SYSPLEX_NAME k CHAR(8) Sysplex name, as defined in ECVTSPLX. From SMF74SID.

CF_NAME k CHAR(8) Name of the coupling facility. From R744FNAM.

CF_LEVEL SMALLINT Level of the coupling facility. From R744FLVL.

CF_MODEL CHAR(4) Model of the coupling facility. From R744FMOD.

CF_STOR_DEF_MB FLOAT Average amount of coupling facility storage defined, inmegabytes. Calculated as the average of R744GTSD/256.

CF_STOR_FREE_MB FLOAT Average amount of free coupling facility storage, inmegabytes. Calculated as the average of R744GTSF/256.

CF_VERSION CHAR(3) Version of the coupling facility. From R744FVER.

PROCESSORS SMALLINT Number of processors in the coupling facility. Calculated asthe maximum of SMF744PN.

PROC_EFFECT FLOAT Number of effective available logical processors in a sharedenvironment. This value is useful only in a CFCCenvironment. Calculated as (CPU_BUSY_SEC +CPU_WAIT_SEC) / MEASURED_SEC.

PROC_UTIL FLOAT Percentage of processor utilization within the coupling facility.Calculated as (CPU_BUSY_SEC / (CPU_BUSY_SEC +CPU_WAIT_SEC)) * 100.



MVSPM_CF_REQ_HVThis view provides statistics about coupling facility in a sysplex. It is based on theMVSPM_CF_REQUEST_H table, and its data comes from SMF type 74, subtype 4records.






STRUCTURE_NAME k CHAR(16) Name of structure connected to this system or allocated inthis coupling facility. From R744QSTR or R744SNAM.

SYSPLEX_NAME k CHAR(8) Sysplex name (as defined in ECVTSPLX). From SMF74XNM.


ASYNC_AVG_SERV FLOAT Average time required to satisfy an asynchronous CFrequest, in microseconds. Calculated asSERVICE_ASYNC_SEC / REQ_ASYNC_NO.

ASYNC_RATE FLOAT Asynchronous requests completed per second. Calculated asREQ_ASYNC_NO / MEASURED_SEC.




CHANGED_OP_PERC FLOAT Percentage of operations changed from synchronous toasynchronous. Calculated as REQ_SYNC_ASYNC /(REQ_SYNC_NO + REQ_ASYNC_NO) * 100.

CHANGED_OP_RATE FLOAT Number of operations changed per second. Calculated asREQ_SYNC_ASYNC / MEASURED_SEC.

DEL_REQUEST_PERC FLOAT Percentage of delayed requests. Calculated as(PATH_CONTENTION + SUBCH_CONTENTION +REQ_QUEUED_NO + REQ_DELAYED_NO) /(REQ_SYNC_NO + REQ_ASYNC_NO +REQ_SYNC_ASYNC) * 100.

DUMP_DELAY_PERC FLOAT Percentage of delayed requests for dump serialization.Calculated as REQ_DELAYED_NO / (REQ_SYNC_NO +REQ_ASYNC_NO + REQ_SYNC_ASYNC) * 100.

PATH_BUSY_RATE FLOAT Number of requests rejected per second because path wasbusy. Calculated as PATH_CONTENTION /MEASURED_SEC.

PATH_DELAY_PERC FLOAT Percentage of requests delayed because path was busy.Calculated as PATH_CONTENTION / (REQ_SYNC_NO +REQ_ASYNC_NO + REQ_SYNC_ASYNC) * 100.

PEER_WAIT_SCH_PERC FLOAT Percentage of requests waiting for peer subchannelconditions. Valid only for duplexed structures. Calculated asPEER_WAIT_SCH_NO/(REQ_SYNC_NO+REQ_ASYNC_NO +REQ_SYNC_ASYNC)*100.



|


PEER_WAIT_CMP_PERC FLOAT Percentage of requests waiting for peer completionconditions. Valid only for duplexed structures. Calculated asPEER_WAIT_CMP_NO/(REQ_SYNC_NO+REQ_ASYNC_NO+ REQ_SYNC_ASYNC)*100.

QUEUE_DELAY_PERC FLOAT Percentage of delayed requests for queue. Calculated asREQ_QUEUED_NO / (REQ_SYNC_NO +REQ_ASYNC_NO + REQ_SYNC_ASYNC) * 100.

REQUEST_RATE FLOAT Number of times requests completed per second. Calculatedas (REQ_SYNC_NO + REQ_ASYNC_NO +REQ_SYNC_ASYNC) / MEASURED_SEC.

STRUCTURE_TYPE CHAR(2) Structure type identifier. Calculated as the maximum ofR744STYP.

SUBCH_BUSY_RATE FLOAT Number of requests rejected per second because subchannelwas busy. Calculated as SUBCH_CONTENTION /MEASURED_SEC.

SUBCH_DELAY_PERC FLOAT Percentage of requests delayed because subchannel wasbusy. Calculated as SUBCH_CONTENTION /(REQ_SYNC_NO + REQ_ASYNC_NO +REQ_SYNC_ASYNC) * 100.

SYNC_AVG_SERV FLOAT Average time required to satisfy a synchronous CF request,in micrseconds. Calculated as SERVICE_SYNC_SEC /REQ_SYNC_NO.

SYNC_RATE FLOAT Synchronous requests completed per second. Calculated asREQ_SYNC_NO / MEASURED_SEC.



|

MVSPM_CF_TO_CF_HVThis view provides data about CF to CF activity. It is based on theMVSPM_CF_TO_CF_H table and its data comes from SMF type 74, subtype 4records.

Note: As well as the calculated columns described here, this view also contains allthe data columns described in MVSPM_CF_TO_CF_H.






SYSPLEX_NAME k CHAR(8) Sysplex name, as defined in ECVTSPLX. From SMF74XNM.

CF_NAME k Name of coupling facility. From R744FNAM.

PEER_CF k CHAR(8) Name of the remote coupling facility. From R744RNAM.

DELAYED_TIME_AVG FLOAT Delay time average. Calculated asDELAY_TIME_SEC/REQUEST_NO.

REQUEST_NO FLOAT The total number of requests sent from the subject CF to thisremote CF. Calculated as(REQ_READY_EXEC_NO+REQ_READY_COMP_NO +REQ_HALT_EXEC_NO+REQ_SUPPRESS_NO+REQ_ASUPPRESS_NO).

REQ_DELAYED_PERC FLOAT Percentage of delayed requests. Calculated asREQ_DELAYED_NO/REQUEST_NO*100.

REQUEST_DATE FLOAT Number of requests per second. Calculated asREQUEST_NO/MEASURED_SEC.

SERVICE_TIME_AVG FLOAT Service time average. Calculated as (SERVICE_TIME_SEC-DELAY_TIME_SEC)/ REQUEST_NO.



|

|||

||

|||||

|||||

||||||

||||||

||||

||||

||||

||||

|||||

||||||||

|||||

|||||

|||||

MVSPM_CLUSTER_HVThis view provides hourly LPAR views as well as aggregated views on LPARcluster level. It is based on the MVSPM_CLUSTER_H table and its data comesfrom SMF type 70 records processed through a record procedure (DRL2S070).

Note: Aside from the calculated columns described here, this view also contains allthe data columns described in MVSPM_CLUSTER_H.






CLUSTER_NAME k CHAR(8) Cluster name associated with the partition. From SMF70SPN.


COMPLEX_UTIL_PCT FLOAT Total processor complex utilization for the partition, as apercentage. Calculated as 100* CPU_DISPATCH_SEC /COMPLEX_SEC.

LPROC_BUSY_PCT FLOAT Average logical processor busy time for the partition, as apercentage. Calculated as100*CPU_DISPATCH_SEC/LP_ONLINE_SEC.

REQ_DELAYED_PERC FLOAT Percentage of delayed requests. Calculated asREQ_DELAYED_NO/REQUEST_NO*100.

SYSTEM_NAME FLOAT z/OS System Name. From SMF70STN.



|

|||

||

|||||

||||||

||||||

||||||

||||

||||

||||

||||||

||||||

|||||

||||

MVSPM_CPU_HVThis view provides statistics on processor activity. It is based on theMVSPM_CPU_H table, and its data comes from SMF type 70 records processedthrough a record procedure (DRL2S070).






CPU_ID k SMALLINT CPU ID. From SMF70CID.

CPU_BUSY_MIPS FLOAT MIPS for single CPU. Calculated as(MIPS/SMF70BNP)*CPU_BUSY_SEC. MIPS is a column in theMVS_MIPS_T lookup table. SMF70BNP is the total number ofCPUs.

CPU_BUSY_PCT FLOAT CPU busy time, in percent. Calculated as(CPU_BUSY_SEC*100)/MEASURED_SEC.

CPU_WAIT_PCT FLOAT CPU wait time, in percent. Calculated as(CPU_WAIT_SEC*100)/MEASURED_SEC.

IO_INTR_RATE FLOAT Total number of interrupts handled per second. Calculated as(IO_INTERRUPTS + TPI_INTERRUPTS)/MEASURED_SEC.

TPI_INTR_PCT FLOAT Percentage of interrupts handled by the TPI instruction.Calculated as (TPI_INTERRUPTS*100)/(IO_INTERRUPTS +TPI_INTERRUPTS).

TPI_INTR_RATE FLOAT Number of interrupts handled by the TPI instruction persecond. Calculated as TPI_INTERRUPTS/MEASURED_SEC.

VFA_AFFINITY_PCT FLOAT Percentage of time the vector facility was used. Calculated as(VECTOR_SAMPLES*100)/SAMPLES.

Note: In addition to the calculated columns described here, this view also containsall the data columns described in “MVSPM_CPU_H” on page 626.



|

MVSPM_CRYPTO_PC_HVThis view provides hourly measurement data for cryptographic hardware (PCICryptographic Coprocessors and Accelerators) on an LPAR basis. It is based on theMVSPM_CRYPTO_PCI_H table and its data comes from SMF type 70, subtype 2records processed through a record procedure (DRL2S702).

Note: As well as the calculated columns described here, this view also contains allthe data columns described in MVSPM_CRYPTO_PCI_H.






ID_INDEX k SMALLINT PCICC or PCICA index. From R7023AX (PCICC) or R7024AX(PCICA).

ID_TYPE k CHAR(8) Indicate PCI Cryptographic hardware and can assume twovalues:

v PCICC for Coprocessor

v PCICA for Accelerators

CRT_1024_RATE FLOAT Rate for all operations in 1024-bit-CRT format. It is valid onlyfor PCICA device. Calculated as CRT_1024_OP_EX_NUM /MEASURED_SEC.

CRT_1024_EXEC_TIME FLOAT Execution time for all operations in 1024-bit-CRT format. It isvalid only for PCICA devices. Calculated asCRT_1024_OP_EX_SEC / CRT_1024_OP_EX_NUM.

CRT_1024_UTIL_PCT FLOAT Percentage of utilization for all operations in 1024-bit-CRTformat. It is valid only for PCICA devices. Calculated as100*CRT_1024_OP_EX_SEC / MEASURED_SEC.

CRT_2048_RATE FLOAT Rate for all operations in 2048-bit-CRT format. It is valid onlyfor PCICA devices. Calculated as CRT_2048_OP_EX_NUM /MEASURED_SEC.

CRT_2048_EXEC_TIME FLOAT Execution time for all operations in 2048-bit-CRT format. It isvalid only for PCICA devices. Calculated asCRT_2048_OP_EX_SEC / CRT_2048_OP_EX_NUM.

CRT_2048_UTIL_PCT FLOAT Percentage of utilization for all operations in 2048- bit-CRTformat. It is valid only for PCICA devices. Calculated as100*CRT_2048_OP_EX_SEC / MEASURED_SEC.

ME_1024_RATE FLOAT Rate for all operations in 1024-bit-ME format. It is valid onlyfor PCICA devices. Calculated as ME_1024_OP_EX_NUM /MEASURED_SEC.

ME_1024_EXEC_TIME FLOAT Execution time for all operations in 1024-bit-ME format. It isvalid only for PCICA devices. Calculated asME_1024_OP_EX_SEC / ME_1024_OP_EX_NUM.



|

||||

||

|||||

||||||

||||||

||||||

||||

|||||

|||||

|

|

||||||

||||||

||||||

||||||

||||||

||||||

||||||

||||||


ME_1024_UTIL_PCT FLOAT Percentage of utilization for all operations in 1024-bit-MEformat. It is valid only for PCICA devices. Calculated as100*ME_1024_OP_EX_SEC / MEASURED_SEC.

ME_2048_RATE FLOAT Rate for all operations in 2048-bit-ME format. It is valid onlyfor PCICA devices. Calculated as ME_2048_OP_EX_NUM /MEASURED_SEC.

ME_2048_EXEC_TIME FLOAT Execution time for all operations in 2048-bit-ME format. It isvalid only for PCICA devices. Calculated asME_2048_OP_EX_SEC / ME_2048_OP_EX_NUM.

ME_2048_UTIL_PCT FLOAT Percentage of utilization for all operations in 2048-bit-MEformat. It is valid only for PCICA devices. Calculated as100*ME_2048_OP_EX_SEC / MEASURED_SEC.

TOTAL_RATE FLOAT Rate of all operations. Calculated as OPERATION_EX_NUM /MEASURED_SEC.

TOTAL_EXEC_TIME FLOAT Average execution time (seconds) of all operations. Calculatedas OPERATION_EX_TIME / OPERATION_EX_NUM.

TOTAL_UTIL_PCT FLOAT Total utilization percentage. Calculated as100*OPERATION_EX_TIME / MEASURED_SEC.



||||

||||||

||||||

||||||

||||||

|||||

|||||

|||||

MVSPM_CRYPTO_CC_HVThis view provides hourly statistic measurement data for the cryptographiccoprocessor facility. It is based on the MVSPM_CRYPTO_CCF_H table and its datacomes from SMF type 70, subtype 2 records.

Note: as well as the calculated columns described here, this view also contains allthe data columns described in MVSPM_CRYPTO_CCF_H.






DES_ENCR_S_RATE FLOAT Rate of requests (calls) to encipher for single DES. Calculatedas DES_ENCR_S_CALLS / MEASURED_SEC.

DES_ENCR_S_SIZE CHAR(8) Average number of bytes per request that have beenenciphered with single-DES. Calculated asDES_ENCR_S_BYTES / DES_ENCR_S_CALLS.

DES_ENCR_T_RATE FLOAT Rate of requests (calls) to encipher for triple DES. Calculatedas DES_ENCR_T_CALLS / MEASURED_SEC.

DES_ENCR_T_SIZE FLOAT Average number of bytes per request that have beenenciphered with triple DES. Calculated asDES_ENCR_T_BYTES / DES_ENCR_T_CALLS.

DES_DECR_S_RATE FLOAT Rate of requests (calls) to decipher for single DES. Calculatedas DES_DECR_S_CALLS / MEASURED_SEC.

DES_DECR_S_SIZE FLOAT Average number of bytes per request that have beendeciphered with single DES. Calculated asDES_DECR_S_BYTES / DES_DECR_S_CALLS.

DES_DECR_T_RATE FLOAT Rate of requests (calls) to decipher for triple DES. Calculatedas DES_DECR_T_CALLS / MEASURED_SEC.

DES_DECR_T_SIZE FLOAT Average number of bytes per request that have beendeciphered with triple DES. Calculated asDES_DECR_T_BYTES / DES_DECR_T_CALLS.

HASH_RATE FLOAT Rate of requests to hash. Calculated as HASH_CALLS /MEASURED_SEC.

HASH_SIZE FLOAT Average number of bytes to be hashed per request. Calculatedas HASH_BYTES/HASH_CALLS.

MAC_GENERATE_RATE FLOAT Rate of requests to generate MACs. Calculated asMAC_GENERATE_CALLS / MEASURED_SEC.

MAC_GENERATE_SIZE FLOAT Average number of bytes per request for which MAC hasbeen generated. Calculated asMAC_GENERATE_BYTES/MAC_GENERATE_CALLS.

MAC_VERIFY_RATE FLOAT Rate of requests to verify MACs. Calculated asMAC_VERIFY_CALLS / MEASURED_SEC.



|

|||

||

|||||

||||||

||||||

||||||

||||

|||||

||||||

|||||

||||||

|||||

||||||

|||||

||||||

|||||

|||||

|||||

||||||

|||||


MAC_VERIFY_SIZE FLOAT Average number of bytes per request for which MAC hasbeen verified. Calculated as MAC_VERIFY_BYTES /MAC_VERIFY_CALLS.

PIN_TRANSLAT_RATE FLOAT Rate of requests to translate PIN. Calculated asPIN_TRANSLAT_CALLS/MEASURED_SEC.

PIN_VERIFY_RATE FLOAT Rate of requests to verify PIN. Calculated asPIN_VERIFY_CALLS/MEASURED_SEC.



||||

||||||

|||||

|||||

MVSPM_DATASET_HVThis view provides DFSMS data set level I/O statistics. It is based on theMVSPM_DATASET_H table, and its data comes from SMF type 42, subtypes 6records.



TIME k TIME Time (rounded down as specified in theMVSPM_TIME_RES table) of the mid measurement. FromSMF42PTE and SMF42PTS.

PERIOD_NAME k CHAR(8) Name of the period. This is derived using fieldsSMF42SID, SMF42PTE and SMF42PTS from the record asparameters in the PERIOD function.


JOBNAME k CHAR(8) Job name. From S42JDJNM.

DATASET_NAME k CHAR(44) Data set name. From S42DSN.

BYPASS_OFF_RATE FLOAT Bypass, inhibit, and off rate; in I/Os per second.Calculated as (IO_COUNT - CACHE_CANDIDATE)/(TIME_RESOLUTION*60).

CACHABLE_HITS_PCT FLOAT Cacheable hit percentage. Calculated as(100*CACHE_HITS)/CACHE_CANDIDATE.

CACHABLE_IO_PCT FLOAT Cacheable I/O percentage. Calculated as100*CACHE_CANDIDATE/IO_COUNT.

CACHABLE_RW_RATIO FLOAT Cacheable I/O read - write ratio. Calculated as(CACHE_CANDIDATE - CACHE_CANDIDATE_WR)/CACHE_CANDIDATE_WR.

CACHE_RESOLVE_RATE FLOAT The rate with which requests are resolved in the cache, inI/Os per second. Calculated asCACHE_HITS/(TIME_RESOLUTION*60).

CONNECT_AVG_MPL FLOAT Average number of users waiting because the path anddevice are busy. Calculated as(CONNECT_average_MSEC*IO_COUNT)/(TIME_RESOLUTION*60E3).

CU_WAIT_AVG_MPL FLOAT Average number of users waiting because the start I/O ispending on the control unit. Calculated as(CU_QUEUE_average_MSEC*IO_COUNT)/(TIME_RESOLUTION*60E3).

DASD_AVG_MPL FLOAT Average number of users waiting because of all reasons.Calculated as (RESPONSE_average_MSEC*IO_COUNT)/(TIME_RESOLUTION*60E3).

DASD_RESOLVE_RATE FLOAT Rate at which requests were resolved from DASD, in I/Osper second. Calculated as (IO_COUNT -CACHE_HITS)/(TIME_RESOLUTION*60).

DATASET_BUSY FLOAT Percentage of time the data set was busy. Calculated as((CONNECT_average_MSEC +DISCONN_average_MSEC)*IO_COUNT)/(TIME_RESOLUTION*60E1).

DFW_HIT_RATE FLOAT DASD fast write hit rate, in I/Os per second. Calculatedas CACHE_WRITE_HITS /(TIME_RESOLUTION*60).




DFW_HITS_PCT FLOAT Number of DASD fast write hits, in percent. Calculated as100*CACHE_WRITE_HITS /CACHE_CANDIDATE_WR.

DFW_STAGING_RATE FLOAT DASD fast write direct and sequential staging rate, inI/Os per second. Calculated as(CACHE_CANDIDATE_WR - CACHE_WRITE_HITS)/(TIME_RESOLUTION*60).

DISCONN_AVG_MPL FLOAT Average number of users waiting because the device isbusy. Calculated as(DISCONN_average_MSEC*IO_COUNT)/(TIME_RESOLUTION*60E3).

HITS_PCT FLOAT Total number of hits, in percent. Calculated as(100*CACHE_HITS)/IO_COUNT.

IO_RATE FLOAT I/O rate for each device, in I/Os per second. This is thenumber of requests serviced per second. Calculated asIO_COUNT/(TIME_RESOLUTION*60).


NORM_SEQ_STG_RATE FLOAT DASD normal and sequential staging rate, in I/Os persecond. Calculated as (CACHE_CANDIDATE -CACHE_CANDIDATE_WR - CACHE_HITS +CACHE_WRITE_HITS) /(TIME_RESOLUTION*60).

PENDING_AVG_MPL FLOAT Average number of users waiting because the start I/O ispending. Calculated as(PENDING_average_MSEC*IO_COUNT)/(TIME_RESOLUTION*60E3).

QUE_WAIT_AVG_MPL FLOAT Average number of users waiting because the start I/O isqueued in the system. Average MPL for UCB wait.Calculated as (QUE_WAIT_average_MSEC*IO_COUNT)/(TIME_RESOLUTION*60E3).

READ_HIT_RATE FLOAT Normal and sequential read hit rate, in I/Os per second.Calculated as (CACHE_HITS - CACHE_WRITE_HITS)/(TIME_RESOLUTION*60).

READ_HITS_PCT FLOAT Number of read hits, in percent. Calculated as100*(CACHE_HITS - CACHE_WRITE_HITS)/(CACHE_CANDIDATE - CACHE_CANDIDATE_WR).

SIO_AVG_MPL FLOAT Average number of users waiting for the start I/O tocomplete. Calculated as ((CONNECT_average_MSEC +DISCONN_average_MSEC)*IO_COUNT)/(TIME_RESOLUTION*60E3).

SIO_AVG_MSEC FLOAT Average device start I/O time per I/O request, inmilliseconds. Calculated as CONNECT_average_MSEC +DISCONN_average_MSEC.

STAGING_RATE FLOAT DASD staging rate, in I/Os per second. Calculated as(CACHE_CANDIDATE -CACHE_HITS)/(TIME_RESOLUTION*60).

Note: In addition to all the calculated columns described here, this view alsocontains all the data columns described in “MVSPM_DATASET_H” onpage 632.



MVSPM_DEVICE_AP_HVThis view provides statistics on the I/O activity per workload type for batch jobs,TSO sessions, started tasks, and APPC sessions. It is based on theMVSPM_DEVICE_AP_H table, and its data comes from SMF type 30, subtypes 2and 3 records.




TIME k TIME Time (rounded down as specified in the MVSPM_TIME_RESlookup table) of the mid measurement. From SMF30IDT,SMF30IST, SMF30DTE, and SMF30TME.



WORKLOAD_TYPE k CHAR(8) MVS workload type name. From WORKLOAD_TYPE in theMVS_WORKLOAD_TYPE or MVS_WORKLOAD2_TYPElookup table.

DEVICE_NUM k CHAR(4) Device number (virtual I/O has device number X'7FFF').From DEVICE_Number in the MVSPM_DEVICE_ADDRlookup table, or from SMF30CUA if no match is found in thelookup table.

CONNECT_AVG_MSEC FLOAT Average connect time per request, in milliseconds. Calculatedas CONNECT_MSEC/BLOCKS.

CONNECT_PCT FLOAT Percentage of time that the device was connected to theoperating system. Calculated asCONNECT_MSEC/(TIME_RESOLUTION*60 000).

IO_RATE FLOAT Number of input/output operations serviced per second.Calculated as BLOCKS/(TIME_RESOLUTION*60).

Note: In addition to the calculated columns described here, this view also containsall the data columns described in “MVSPM_DEVICE_AP_H” on page 634.



MVSPM_DEVICE_AP_PVThis view provides statistics on the total number of blocks transferred to or from adevice per period. You can use it to report on the most busy devices per period. Itis based on the MVSPM_DEVICE_AP_H table, and its data comes from SMF type30, subtypes 2 and 3 records.





DEVICE_NUM k CHAR(4) Device number (virtual I/O has device number X'7FFF'). FromDEVICE_Number in the MVSPM_DEVICE_ADDR lookup table,or from SMF30CUA if no match is found in the lookup table.

BLOCKS_TOT FLOAT Number of blocks transferred to or from a device. This is the sumof SMF30BLK.



MVSPM_DEVICE_HVThis view provides statistics on the I/O activity of MVS devices. It is based on theMVSPM_DEVICE_H table, and the data comes from SMF type 74, subtype 1records.







DEVICE_NUM k CHAR(4) Device number. From MVS_ADDR in theMVSPM_DEVICE_ADDR lookup table, or from SMF74NUMif no match is found in the lookup table.

ALLOCATIONS_AVG FLOAT Average number of data sets open for the device. Calculatedas (ALLOCATIONS/(TIME_RESOLUTION*60 000))*CYCLE_LENGTH_MSEC.

CONNECT_AVG_MPL FLOAT Average number of users waiting because the path anddevice are busy. Calculated as CONNECT_MSEC/(TIME_RESOLUTION*60 000).

CONNECT_AVG_MSEC FLOAT Average connect time per request, in milliseconds.Calculated asCONNECT_MSEC/MEASUREMENT_EVENTS.

CU_WAIT_AVG_MPL FLOAT Average number of users waiting because the control unit isbusy. Calculated as CU_BUSY_DELAY/(TIME_RESOLUTION*60 000).

CU_WAIT_AVG_MSEC FLOAT Average CU wait time per request, in milliseconds. This isthe average time that a request waited for the control unit.Calculated asCU_BUSY_DELAY/MEASUREMENT_EVENTS.

DASD_AVG_MPL FLOAT Average number of users waiting for the device. Calculatedas ((CONNECT_MSEC+DISCONN_MSEC +PENDING_MSEC) +(REQUESTS_QUEUED*CYCLE_LENGTH_MSEC) /(TIME_RESOLUTION*60 000)).

DEV_BUSY_PCT FLOAT Percentage of time the device is busy. Calculated as100*(CONNECT_MSEC + DISCONN_MSEC)/(TIME_RESOLUTION*60 000).

DEV_WAIT_AVG_MPL FLOAT Average number of users waiting because the device is busy.Calculated as DEVICE_BUSY_DELAY/(TIME_RESOLUTION*60 000).




DEV_WAIT_AVG_MSEC FLOAT Average device wait time per request, in milliseconds. Thisis the average time that a request waited for the device.Calculated as DEVICE_BUSY_DELAY/MEASUREMENT_EVENTS.

DISCONN_AVG_MPL FLOAT AVG number of users waiting because the device is busy.Calculated asDISCONN_MSEC/(TIME_RESOLUTION*60 000).

DISCONN_AVG_MSEC FLOAT Average disconnect time per request, in milliseconds.Calculated as DISCONN_MSEC/MEASUREMENT_EVENTS.

IO_RATE FLOAT Number of requests serviced per second. Calculated asMEASUREMENT_EVENTS /(TIME_RESOLUTION*60).Computed data columns in this view can contain incorrectvalues when the SMF

NUM_UCB_PAV FLOAT Number of unit control blocks (UCB) for PAV. This is thesum of SMF74NUX.

PAV_SUCC_SAMPLES FLOAT Number of unsuccessful PAV sample counts. FromSMF74PCT.

PAV_TIME_SKIPPED FLOAT Time skipped because of a dynamic change of alias volumesfor PAV devices, in milliseconds. From SMF74TMS.

PENDING_AVG_MPL FLOAT Average number of users waiting because the device orcontrol unit is busy. Calculated asPENDING_MSEC/(TIME_RESOLUTION*60 000).

PENDING_AVG_MSEC FLOAT Average pending time per request, in milliseconds. This isthe average time that a request waited for the device orcontrol unit. Calculated asPENDING_MSEC/MEASUREMENT_EVENTS.

QUE_WAIT_AVG_MPL FLOAT Average number of users waiting because the start I/O isqueued in the UCB. Calculated as((REQUESTS_QUEUED*CYCLE_LENGTH_MSEC)/(TIME_RESOLUTION*60 000)).

QUE_WAIT_AVG_MSEC FLOAT Average queue wait time, in milliseconds. This is theaverage time spent in the queue waiting for the UCB.Calculated as(REQUESTS_QUEUED*CYCLE_LENGTH_MSEC)/MEASUREMENT_EVENTS.

RESERVED_PCT FLOAT Percentage of time the device was reserved. Calculated as(SAMPLES_RSV/(TIME_RESOLUTION*60 000))*CYCLE_LENGTH_MSEC*100.

RESPONSE_AVG_MSEC FLOAT Average response time per request, in milliseconds.Calculated as ((CONNECT_MSEC + DISCONN_MSEC +PENDING_MSEC) +(REQUESTS_QUEUED*CYCLE_LENGTH_MSEC))/MEASUREMENT_EVENTS.

RMF_INTERVAL FLOAT Duration of the RMF measurement interval, in minutes.Calculated as SMF74INT/60000. If there is a dynamic changeof alias on a PAV device, it is calculated as (SMF74INT −SMF74TMS) / 60000.

RSV_NOT_BUSY_PCT FLOAT Percentage of time the device was reserved and not busy.Calculated as(SAMPLES_UTL/(TIME_RESOLUTION*60 000))*CYCLE_LENGTH_MSEC*100.



||

|


SIO_AVG_MPL FLOAT Average number of users waiting for the start I/O tocomplete. Calculated as (CONNECT_MSEC +DISCONN_MSEC/ (TIME_RESOLUTION*60 000)).

SIO_AVG_MSEC FLOAT Average SIO time spent per request, in milliseconds.Calculated as (CONNECT_MSEC + DISCONN_MSEC)/MEASUREMENT_EVENTS.

Note: In addition to the calculated columns described here, this view also containsall the data columns described in “MVSPM_DEVICE_H” on page 635.



MVSPM_ENQUEUE_HVThis view provides statistics on enqueue activity on MVS systems. It is based onthe MVSPM_ENQUEUE_H table, and its data comes from SMF type 77 records.







QUEUE_NAME k CHAR(8) Major queue name of the resource. From SMF77QNM.

ENQ_CONFLICT_RATE FLOAT Average number of enqueue conflicts per second. Calculatedas CONTENTION_TOT_SEC /(TIME_RESOLUTION*60).

WAITING_APPL FLOAT Average number of applications waiting on enqueue.Calculated as (WAITING_REQUESTS/CONTENTION_EVENTS)* CONTENTION_TOT_SEC/(TIME_RESOLUTION*60).

Note: In addition to the calculated columns described here, this view also containsall the data columns described in “MVSPM_ENQUEUE_H” on page 638.



MVSPM_LPAR_HVThis view provides statistics on logical partitions and processor activity in aPR/SM environment. It is based on the MVSPM_LPAR_H table, and its data comesfrom SMF type 70 records processed through a record procedure (DRL2S070).



TIME k TIME Time (rounded down as specified in theMVSPM_TIME_RES lookup table) of the mid measurement.From SMF70DAT, SMF70IST, and SMF70INT.





ALLOWED_SEC FLOAT Allowed time for the processor partition, in seconds.Calculated as ((MEASURED_SEC*DEDICAT_PROC_LPAR)+ LPROC_SEC*( LPAR_WEIGHT/LPAR_WEIGHT_TOT)

COMPLEX_SEC FLOAT Total processor complex time, in seconds. Calculated asMEASURED_SEC*PHYS_PROCESSORS.

COMPLEX_UTIL_PCT FLOAT Total processor complex utilization for the partition, as apercentage. Calculated as 100*(CPU_DISPATCH_SEC -CPU_WAIT_SEC) /COMPLEX_SEC.

CPU_BUSY_MIPS FLOAT Virtual processor busy MIPS time, in seconds. Calculated asthe sum of (SMF70PDT/1000000.)* MIPS_PER_LPAR

DEDICAT_PROC_LPAR SMALLINT Number of dedicated processors for this LPAR. Calculatedas the maximum of LPDEDICF (ICF) or LPDEDCP (CP).

LPAR_BUSY_PCT FLOAT Busy time for the logical partition, as a percentage of theelapsed time. This value can be greater that 100% if morethan one processor is assigned to the partition. Calculatedas 100*CPU_DISPATCH_SEC/MEASURED_SEC.

LPAR_DISPATCH_PCT FLOAT Time that the logical partition was dispatched, as apercentage of the allowed time. Calculated as100*CPU_DISPATCH_SEC/ALLOWED_SEC.

LPAR_EFF_DISP_PCT FLOAT Time that the logical partition was dispatched, as apercentage of the allowed time. Calculated as100*CPU_DISPATCH_SEC/ALLOWED_SEC

LPAR_MGMT_PCT FLOAT Logical partition management time, as a percentage. This isthe percentage of physical LPAR management time if thepartition name is *PHYSCAL. Calculated as100*(CPU_DISPATCH_SEC-CPU_ EFF_DISP_SEC)/LPROC_SEC.

LPAR_SPARE_PCT FLOAT Spare time for the logical partition, as a percentage of theallowed time for this partition. A minus sign for this valuemeans that more than the allowed time was used.Calculated as 100*(ALLOWED_SEC −CPU_DISPATCH_SEC)/ ALLOWED_SEC.



|

|

|

|

|

|

|

|


LPROC_BUSY_PCT FLOAT Average logical processor busy time for the partition, as apercentage. Calculated as100*CPU_DISPATCH_SEC/LP_ONLINE_SEC.


LPROC_EFF_DISP_PCT FLOAT Effective dispatch time for the logical processor, as apercentage of the time available for nondedicatedprocessors. Calculated as100*CPU_EFF_DISP_SEC/LPROC_SEC.


MIPS_PER_LPAR FLOAT Total number of MIPS per LPAR. The number of MIPS istaken from the lookup table MVS_MIPS_T


Note: In addition to the calculated columns described here, this view also containsall the data columns described in “MVSPM_LPAR_H” on page 644.



|

|

|

|

|

|

MVSPM_PAGE_DS_HVThis view provides statistics on page data set and swap data set activities on MVSsystems. It is based on the MVSPM_PAGE_DS_H table, and its data comes fromSMF type 75 records.






DEVICE_NUM k CHAR(4) Device number for the page data set. From SMF75CHA.

PAGE_SPACE_TYPE k CHAR(6) Type of page data set. This can be PLPA, COMMON,LOCAL, or SWAP. From SMF75PST.

DATASET_NAME k CHAR(44) Name of the page or swap data set. From SMF75DSN.

COMM_PAGES_PER_IO FLOAT Number of pages transferred to or from the common pagedata set per I/O request. Calculated asCOMMON_IND*PAGES_TRANSFERRED/IO_REQUESTS.

COMMON_PAGE_MSEC FLOAT Time spent per page transferred to or from a commonpage data set, in millisecond. Calculated asCOMMON_IND*1000*(DATASET_BUSY_SEC/IO_REQUESTS)/(PAGES_TRANSFERRED/IO_REQUESTS).

DATASET_BUSY_PCT FLOAT Average percentage of time that the page data set wasbusy. Calculated as100*DATASET_USED_SEC/MEASURED_SEC.

IO_RATE FLOAT Number of input/output requests serviced per second.Calculated as IO_REQUESTS/MEASURED_SEC.

IO_RESPONSE_MSEC FLOAT I/O response time, in milliseconds. Calculated as1000*DATASET_BUSY_SEC/IO_REQUESTS.

IO_SERVICE_MSEC FLOAT I/O service time, in milliseconds. Calculated as1000*DATASET_USED_SEC/IO_REQUESTS.

LOCAL_PAGE_MSEC FLOAT Time spent per page transferred to or from a local pagedata set, in milliseconds. Calculated asLOCAL_IND*1000*(DATASET_BUSY_SEC/IO_REQUESTS)/(PAGES_TRANSFERRED/IO_REQUESTS).

LOCAL_PAGES_PER_IO FLOAT Number of pages transferred to or from the local page dataset per I/O request. Calculated asLOCAL_IND*PAGES_TRANSFERRED/IO_REQUESTS.

PAGE_RATE FLOAT Number of pages transferred per second. Calculated asPAGES_TRANSFERRED/MEASURED_SEC.

PAGE_SERVICE_MSEC FLOAT Page service time, in milliseconds. Calculated as1000*DATASET_USED_SEC /PAGES_TRANSFERRED.

PAGES_PER_IO FLOAT Average number of pages transferred per I/O request.Calculated as PAGES_TRANSFERRED/IO_REQUESTS.




PLPA_PAGE_MSEC FLOAT Time spent per page transferred to or from a PLPA pagedata set, in milliseconds. Calculated asPLPA_IND*1000*(DATASET_BUSY_SEC/IO_REQUESTS)/(PAGES_TRANSFERRED/IO_REQUESTS).

PLPA_PAGES_PER_IO FLOAT Number of PLPA pages transferred per I/O request.Calculated as PLPA_IND*PAGES_TRANSFERRED/IO_REQUESTS.

RESP_COMMON_SEC FLOAT Common storage area paging response time, in seconds.Calculated as COMMON_IND*DATASET_BUSY_SEC/IO_REQUESTS.

RESPONSE_LOCAL_SEC FLOAT Local (or private) paging response time, in seconds.Calculated as LOCAL_IND*DATASET_BUSY_SEC/IO_REQUESTS.

RESPONSE_PLPA_SEC FLOAT PLPA paging response time, in seconds. Calculated asPLPA_IND*DATASET_BUSY_SEC /IO_REQUESTS.

RESPONSE_SWAP_SEC FLOAT Swap paging response time, in seconds. Calculated asSWAP*DATASET_BUSY_SEC /IO_REQUESTS.

Note: In addition to the calculated columns described here, this view also containsall the data columns described in “MVSPM_PAGE_DS_H” on page 660.



MVSPM_PAGING_HVThis view provides statistics on paging activity on MVS systems. It is based on theMVSPM_PAGING_H table, and its data comes from SMF type 71 records.






BLK_PAGEIN_RATE FLOAT Number of blocked pages that were paged in per second.Calculated as PAGEINS_BLOCK/MEASURED_SEC.

BLOCKS_IN_PER_SEC FLOAT Number of blocks paged in per second. Calculated asBLOCKS_IN/MEASURED_SEC.

CENTRAL_STORAGE_MB FLOAT Total size of online central (real) storage, in megabytes.Calculated as STOR_NUCLEUS_MB +CSTOR_PRIVATE_MB + CSTOR_LSQA_MB +CSTOR_CSA_MB + CSTOR_LPA_MB + CSTOR_SQA_MB+ CSTOR_AVAILABLE_MB.

COMMON_PAGE_RATE FLOAT Total number of page-ins and page-outs per second forthe common page data set. Calculated as(PAGEINS_COMMON + PAGEOUTS_COMMON −PAGEINS_LPA) /MEASURED_SEC.

DISCARD_ES_RATE FLOAT Number of pages discarded from expanded storage persecond. Calculated as (PAGES_MOVED_ES −PAGES_READ_ES)/MEASURED_SEC.

FPGS_16M_TO_2G_MIN FLOAT Minimum number of pages fixed between 16 MB and 2GB (ESAME mode). From SMF71MFB.

FPGS_16M_TO_2G_MAX FLOAT Maximum number of pages fixed between 16 MB and 2GB (ESAME mode). From SMF71XFB.

FPGS_16M_TO_2G_AVG FLOAT Average number of pages fixed between 16 MB and 2 GB(ESAME mode). From SMF71AFB.

FRAMES_AV_CS_MIN FLOAT Minimum number of available central storage frames.This is from SMF71CAM.

FRAMES_AV_CS_MAX FLOAT Maximum number of available central storage frames.This is from SMF71CAX.

FRAMES_AV_CS_AVG FLOAT Average number of available central storage frames. Thisis from SMF71CAA.

FRAMES_LI_CS_MIN FLOAT Minimum number of low-impact central storage frames.This is from SMF71CLM.

FRAMES_LI_CS_MAX FLOAT Maximum number of low-impact central storage frames.This is from SMF71CLX.

FRAMES_LI_CS_AVG FLOAT Average number of low-impact central storage frames.This is from SMF71CLA.




FRAMES_MI_CS_MIN FLOAT Minimum number of medium-impact central storageframes. This is from SMF71CMM.

FRAMES_MI_CS_MAX FLOAT Maximum number of medium-impact central storageframes. This is from SMF71CMX.

FRAMES_MI_CS_AVG FLOAT Average number of medium-impact central storageframes. This is from SMF71CMA.

FRAMES_HI_CS_MIN FLOAT Minimum Number of high-impact central storage frames.This is from SMF71CHM.

FRAMES_HI_CS_MAX FLOAT Maximum number of high-impact central storage frames.This is from SMF71CHX.

FRAMES_HI_CS_AVG FLOAT Average number of high-impact central storage frames.This is from SMF71CHA.

FRAMES_AV_ES_MIN FLOAT Minimum number of available expanded storage frames.This is from SMF71EAM.

FRAMES_AV_ES_MAX FLOAT Maximum number of available expanded storage frames.This is from SMF71EAX.

FRAMES_AV_ES_AVG FLOAT Average number of available expanded storage frames.This is from SMF71EAA.

FRAMES_LI_ES_MIN FLOAT Minimum number of low-impact expanded storageframes. This is from SMF71ELM.

FRAMES_LI_ES_MAX FLOAT Maximum number of low-impact expanded storageframes. This is from SMF71ELX.

FRAMES_LI_ES_AVG FLOAT Average number of low-impact expanded storage frames.This is from SMF71ELA.

FRAMES_MI_ES_MIN FLOAT Minimum number of medium-impact expanded storageframes. This is from SMF71EMM.

FRAMES_MI_ES_MAX FLOAT Maximum number of medium-impact expanded storageframes. This is from SMF71EMX.

FRAMES_MI_ES_AVG FLOAT Average number of medium-impact expanded storageframes. This is from SMF71EMA.

FRAMES_HI_ES_MIN FLOAT Minimum number of high-impact expanded storageframes. This is from SMF71EHM.

FRAMES_HI_ES_MAX FLOAT Maximum number of high-impact expanded storageframes. This is from SMF71EHX.

FRAMES_HI_ES_AVG FLOAT Average number of high-impact expanded storage frames.This is from SMF71EHA.

HS_MIGRATE_RATE FLOAT Number of hiperspace pages migrated to auxiliary storageper second. Calculated asPAGES_MIGR_HIPER/MEASURED_SEC.

HS_PAGE_FR_ES_RATE FLOAT Number of hiperspace pages read from expanded storageper second. Calculated asHS_PAGES_FROM_ES/MEASURED_SEC.

HS_PAGEIN_RATE FLOAT Number of hiperspace page-ins per second. Calculated asPAGEINS_HIPER/MEASURED_SEC.

HS_PAGEOUT_RATE FLOAT Number of hiperspace page-outs per second. Calculatedas PAGEOUTS_HIPER/MEASURED_SEC.

HS_PAGE_TO_ES_RATE FLOAT Number of hiperspace pages written to expanded storageper second. Calculated asPAGES_HIPER_TO_ES/MEASURED_SEC.




LOCAL_PAGE_RATE FLOAT Total number of page-ins and page-outs per second forthe local page data sets. Calculated as(PAGES_SWAPPED_OUT - PAGES_SWAPPED_IN +PAGEINS_VIO + PAGEOUTS_VIO + PAGEINS +PAGEOUTS)/MEASURED_SEC.

LSWAP_RATE FLOAT Number of logical swaps performed per second.Calculated as LOGICAL_SWAPS/MEASURED_SEC.

LSWAP_RATE_PCT FLOAT Number of logical swaps performed, as a percentage ofthe total number of swaps. Calculated asLOGICAL_SWAPS/(LOGICAL_SWAPS +SWAP_SEQUENCES)*100.

LSWAP_RATE_TOTAL FLOAT Total number of logical-swap requests per second.Calculated as (((PAGES_SWAPPED_IN/SWAP_SEQUENCES/256)*LOGICAL_SWAPS)*2)/MEASURED_SEC.

MOVE_CS_ES_RATE FLOAT Number of pages moved from central (real) storage toexpanded storage per second. Calculated asPAGES_MOVED_ES/MEASURED_SEC.

MOVE_ES_CS_RATE FLOAT Number of pages moved from expanded storage tocentral (real) storage per second. Calculated asPAGES_READ_ES/MEASURED_SEC.

PAGEIN_RATE FLOAT Total number of non-VIO page-ins per second. Calculatedas (PAGEINS + PAGEINS_HIPER)/MEASURED_SEC.

PAGEINS_CSA_RATE FLOAT Average number of CSA page-ins per second. Calculatedas (PAGEINS_COMMON -PAGEINS_LPA)/MEASURED_SEC.

PAGEINS_LPA_RATE FLOAT Average number of LPA page-ins per second. Calculatedas PAGEINS_LPA/MEASURED_SEC.

PAGEINS_PRIV_RATE FLOAT Average number of non-VIO page-ins performed persecond in the private area. Calculated as (PAGEINS -PAGEINS_COMMON)/MEASURED_SEC.

PAGE_MIGRATE_RATE FLOAT Number of pages moved from expanded storage toauxiliary storage per second. Calculated asPAGES_MIGRATED_TOT/MEASURED_SEC.

PAGE_MOVE_RATE FLOAT Number of pages moved per second. Calculated asPAGES_MOVED_TOT/MEASURED_SEC.

PSWAP_RATE FLOAT Number of physical swaps performed per second.Calculated as SWAP_SEQUENCES/MEASURED_SEC.

RSTORE_VIO_PG_MIN FLOAT Minimum number of VIO pages in real storage (ESAMEmode). From SMF71MVI.

RSTORE_VIO_PG_MAX FLOAT Maximum number of VIO pages in real storage (ESAMEmode). From SMF71XVI.

RSTORE_VIO_PG_AVG FLOAT Average number of VIO pages in real storage (ESAMEmode). From SMF71AVI.

RSTORE_HYS_PG_MIN FLOAT Minimum number of hiperspace pages in real storage(ESAME mode). From SMF71MHI.

RSTORE_HYS_PG_MAX FLOAT Maximum number of hiperspace pages in real storage(ESAME mode). From SMF71XHI.

RSTORE_VIOPG_WR_RT FLOAT Rate of VIO pages written to real storage (ESAME mode).Calculated as RSTORE_VIO_PG_WRT /MEASURED_SEC.




RSTORE_VIOPG_RD_RT FLOAT Rate of VIO pages read from real storage (ESAME mode).Calculated as RSTORE_VIO_PG_RDN /MEASURED_SEC.

RSTORE_HYSPG_WR_RT FLOAT Rate of hiperspace pages written to real storage (ESAMEmode). Calculated as RSTORE_VIO_PG_WRT /MEASURED_SEC.

RSTORE_HYSPG_RD_RT FLOAT Rate of hiperspace pages read from real storage (ESAMEmode). Calculated as RSTORE_VIO_PG_RDN /MEASURED_SEC.

SHARED_PAGEIN_RATE FLOAT Number of page-ins for shared page groups per second.Calculated as PAGEINS_SHARED/MEASURED_SEC.

STOR_AVAILABLE_MB FLOAT Average size of unused (available) storage, in megabytes.Calculated as ESTOR_AVAILABLE_MB +CSTOR_AVAILABLE_MB.

STOR_CSA_TOT_MB FLOAT Average size of the total central and expanded CSAstorage, in megabytes. Calculated as CSTOR_CSA_MB +ESTOR_CSA_MB.

STOR_LPA_TOT_MB FLOAT Average size of the total LPA storage, in megabytes.Calculated as CSTOR_LPA_MB + ESTOR_LPA_MB.

STOR_LSQA_TOT_MB FLOAT Average size of the total central, expanded and fixedLSQA storage, in megabytes. Calculated asCSTOR_LSQA_MB + ESTOR_LSQA_MB.

STOR_PRIV_TOT_MB FLOAT Average number of pageable address space frames in theprivate address space, in megabytes. Calculated asESTOR_PRIVATE_MB + CSTOR_PRIVATE_MB.

STOR_SQA_TOT_MB FLOAT Average size of the total central, expanded and fixed SQAstorage, in megabytes. Calculated as CSTOR_SQA_MB +ESTOR_SQA_MB.

SWAPIN_WORKING_SET FLOAT Average swap-in working set, in megabytes. Calculated asPAGES_SWAPPED_IN /SWAP_SEQUENCES/256.

SWAP_PAGE_RATE FLOAT Total number of pages swapped in or out to the swapdata sets per second. Calculated as2*PAGES_SWAPPED_IN/MEASURED_SEC.

SWAPS_TOTAL FLOAT Total number of swaps performed. Calculated asLOGICAL_SWAPS + SWAP_SEQUENCES.

VIO_MIGRATE_RATE FLOAT Number of VIO pages migrated from expanded storageper second. Calculated asPAGES_MIGRATED_VIO/MEASURED_SEC.

VIO_PAGEIN_RATE FLOAT Average number of VIO page-ins per second. Calculatedas PAGEINS_VIO/MEASURED_SEC.

VIO_READ_RATE FLOAT Number of VIO pages read from expanded storage persecond. Calculated asPAGES_READ_VIO/MEASURED_SEC.

VIO_TO_ES_RATE FLOAT Number of VIO pages written to expanded storage persecond. Calculated asPAGES_VIO_TO_ES/MEASURED_SEC.

Note: In addition to the calculated columns described here, this view also containsall the data columns described in “MVSPM_PAGING_H” on page 662.



MVSPM_RAID_RANK_HVThis view provides statistics and information about a redundant array ofindependent disks (RAID) rank. It is based on MVSPM_RAID_RANK_H table.


DATE k DATE Date of the mid measurement. From SMFxDTE,SMFxTME, and R745CINT.

TIME k TIME Time (rounded down as specified in theMVSPM_TIME_RES lookup table) of the midmeasurement. From SMFxDTE, SMFxTME, andR745CINT.

PERIOD_NAME k CHAR(8) Name of the period. This is derived using fieldsSMFxDTE, SMFxTME, and R745CINT from the recordas parameters in the PERIOD function.


DEVICE_NUM k CHAR(4) The ESA/390 term for a 4-character hexadecimalidentifier, for example, X'13A0'associated with a deviceto facilitate communication between the program andthe host operator. The device number is associated withthe subchannel. From R7451DVN.

RAID_RANK_ID k INTEGER RAID rank ID. From R7451RID.

DEVICE_ADAPTER_ID INTEGER ID of a physical subunit of a storage server thatprovides the facilities to attach to one or more interfacesthat are used to communicate with the associatedstorage devices. From R7451AID.

INPUT_RECORDS INTEGER Number of SMF records collected during the timeperiod specified in the TIME_RESOLUTION column.

MEASURED_SEC FLOAT Measured time period, in seconds. This is the sum ofthe RMF measurement intervals. Calculated as the sumof R745CINT.

RAID_TYPE CHAR(8) RAID rank type. It can assume one of the followingvalues: RAID-5, JBOD, and RAID0/1. From R7451RTY.

RR_READ_REQ_AVG_MB FLOAT Average number of megabytes read with an I/O.Calculated asHDD_SECTOR_SIZE*RR_FB_SECTOR_READ/RR_READ_REQUESTS.

RR_READ_REQ_MB_S FLOAT Average number of megabytes read per second.Calculated asHDD_SECTOR_SIZE*RR_FB_SECTOR_READ/MEASURED_SEC.

RR_READ_REQ_RATE FLOAT Read request rate of RAID rank. Calculated asRR_READ_REQUESTS/MEASURED_SEC.

RR_READ_REQ_RTIME FLOAT Average response time of a read request. Calculated asRR_READ_RESP_TIME /RR_READ_REQUESTS.

RR_WRITE_REQ_AVG_MB FLOAT Average number of megabytes written with an I/O.Calculated asHDD_SECTOR_SIZE*RR_FB_SECTOR_WRITE/RR_WRITE_REQUESTS.

RR_WRITE_REQ_MB_S FLOAT Average number of megabytes written per second.Calculated asHDD_SECTOR_SIZE*RR_FB_SECTOR_WRITE/MEASURED_SEC.



|

|


RR_WRITE_REQ_RATE FLOAT Write request rate of RAID rank. Calculated asRR_WRITE_REQUESTS/MEASURED_SEC.

RR_WRITE_REQ_RTIME FLOAT Average response time of a read request. Calculated asRR_WRITE_RESP_TIME /RR_WRITE_REQUESTS.




MVSPM_STORAGE_HVThis view provides statistics on MVS storage activity by workload type andperformance group. It is based on MVSPM_STORAGE_H table, and its data comesfrom SMF type 72, subtype 2 records.








PERF_GROUP_NO k CHAR(3) Performance group number. From R722PG.

ACTIVE_FRAMES FLOAT Average number of active storage frames. Calculated asACTIVE_FRAMES_TOT /(TIME_RESOLUTION*60 000)/CYCLE_LENGTH_MSEC.

ACTIVE_USERS FLOAT Average number of active users. Calculated asACTIVE_USERS_TOT/(TIME_RESOLUTION/RMF_INTERVAL).

DIV_ADDRESS_SPACES FLOAT Average number of data-in-virtual address spaces.Calculated asDIV_SAMPLES/(TIME_RESOLUTION*60 000)/CYCLE_LENGTH_MSEC.

DIV_FRAMES FLOAT Average data-in-virtual storage frames. Calculated asDIV_FRAMES_TOT /(TIME_RESOLUTION*60 000)/CYCLE_LENGTH_MSEC.

DIV_WORKING_SET_MB FLOAT Average data-in-virtual working set, in megabytes.Calculated as DIV_FRAMES_TOT/DIV_SAMPLES/256.

EXECUTING_USERS FLOAT Average number of users using the processor orperforming I/O operations. Calculated asACTIVE_USERS_TOT/(TIME_RESOLUTION/RMF_INTERVAL).

FIXED_FRAMES FLOAT Average number of fixed storage frames. Calculated asFIXED_FRAMES_TOT/(TIME_RESOLUTION*60 000)/CYCLE_LENGTH_MSEC.

INSTORAGE_USERS FLOAT Average number of users in storage. Calculated as(PAGEDEL_USERS_TOT + ACTIVE_USERS_TOT)/(TIME_RESOLUTION/RMF_INTERVAL).




LSW_WORKING_SET_MB FLOAT Average logical swap working set, in megabytes.Calculated as(IDLE_FRAMES_TOT/IDLE_SAMPLES)/256.

LSWAP_FRAMES FLOAT Average number of logical swap storage frames.Calculated as IDLE_FRAMES_TOT/(TIME_RESOLUTION*60 000)/CYCLE_LENGTH_MSEC.

OUTREADY_USERS FLOAT Average number of out and ready users. Calculated as(OUTREADY_USERS_TOT + SWAPDEL_USERS_TOT)/(TIME*RESOLUTION*60 000)/ CYCLE_LENGTH_MSEC.

PAGE_DELAYED_USERS FLOAT Users waiting on page faults. Calculated asPAGEDEL_USERS_TOT /(TIME_RESOLUTION*60 000)/CYCLE_LENGTH_MSEC.

PAGE_RESPONSE_MSEC FLOAT Response time per page, in milliseconds. Calculated as1000*(PAGEDEL_USERS_TOT/(TIME_RESOLUTION*60 000)/CYCLE_LENGTH_MSEC))/(PAGEINS/(TIME_RESOLUTION*60).

PAGEIN_RATE FLOAT Number of page-in operations per second. Calculated asPAGEINS/(TIME_RESOLUTION*60).

SWAPPING_IN_USERS FLOAT Average number of users swapping in. Calculated asSWAPDEL_USERS_TOT/(TIME_RESOLUTION*60 000)/CYCLE_LENGTH_MSEC.

THINKING_USERS FLOAT Average number of users thinking. Calculated asIDLE_SAMPLES /(TIME_RESOLUTION*60 000)/CYCLE_LENGTH_MSEC.

USERS FLOAT Average number of users in this performance group ordomain. Calculated asUSERS_TOT/(TIME_RESOLUTION /RMF_INTERVAL).

WAITING_USERS FLOAT Users waiting on RTO or MPL. Calculated asOUTREADY_USERS_TOT/(TIME_RESOLUTION*60 000)/CYCLE_LENGTH_MSEC.

WORKING_SET_MB FLOAT Average processor storage per user, in megabytes.Calculated as (ACTIVE_FRAMES_TOT/ACTIVE_SAMPLES)/256.

Note: In addition to the calculated columns described here, this view also containsall the data columns described in “MVSPM_STORAGE_H” on page 671.



MVSPM_STORCLASS_HVThis view provides DFSMS storage class I/O statistics. It is based on theMVSPM_STORCLASS_H table, and its data comes from SMF type 42, subtypes 5records.




PERIOD_NAME k CHAR(8) Name of the period. This is derived using fieldsSMF42SID, SMF42PTE and SMF42PTS from therecord as parameters in the PERIOD function.

STORAGE_CLASS k VARCHAR(32) Storage class name. From S42SCNAM.

BYPASS_OFF_RATE FLOAT Bypass, inhibit, and off rate; in I/Os per second.Calculated as (IO_COUNT - CACHE_CANDIDATE)/(TIME_RESOLUTION*60).

CACHABLE_HITS_PCT FLOAT Cacheable hit percentage. Calculated as(100*CACHE_HITS)/CACHE_CANDIDATE.

CACHABLE_IO_PCT FLOAT Cacheable I/O percentage. Calculated as100*CACHE_CANDIDATE/IO_COUNT.

CACHABLE_RW_RATIO FLOAT Cacheable I/O read - write ratio. Calculated as(CACHE_CANDIDATE -CACHE_CANDIDATE_WR)/CACHE_CANDIDATE_WR.

CACHE_RESOLVE_RATE FLOAT The rate with which requests are resolved in thecache, in I/Os per second. Calculated asCACHE_HITS/(TIME_RESOLUTION*60).

CONNECT_AVG_MPL FLOAT Average number of users waiting because the pathand device are busy. Calculated as(CONNECT_average_MSEC*IO_COUNT)/(TIME_RESOLUTION*60E3).

CU_WAIT_AVG_MPL FLOAT Average number of users waiting because the startI/O is pending on the control unit. Calculated as(CU_QUEUE_average_MSEC*IO_COUNT)/(TIME_RESOLUTION*60E3).

DASD_AVG_MPL FLOAT Average number of users waiting because of allreasons. Calculated as(RESPONSE_average_MSEC*IO_COUNT)/(TIME_RESOLUTION*60E3).

DASD_RESOLVE_RATE FLOAT Rate at which requests were resolved from DASD, inI/Os per second. Calculated as (IO_COUNT -CACHE_HITS) /(TIME_RESOLUTION*60).

DFW_HIT_RATE FLOAT DASD fast write hit rate, in I/Os per second.Calculated as CACHE_WRITE_HITS/(TIME_RESOLUTION*60).

DFW_HITS_PCT FLOAT Number of DASD fast write hits, in percent.Calculated as 100*CACHE_WRITE_HITS/CACHE_CANDIDATE_WR.




DFW_STAGING_RATE FLOAT DASD fast write direct and sequential staging rate, inI/Os per second. Calculated as(CACHE_CANDIDATE_WR - CACHE_WRITE_HITS)/(TIME_RESOLUTION*60).

DISCONN_AVG_MPL FLOAT Average number of users waiting because the deviceis busy. Calculated as(DISCONN_average_MSEC*IO_COUNT)/(TIME_RESOLUTION*60E3).

HITS_PCT FLOAT Total number of hits, in percent. Calculated as(100*CACHE_HITS)/IO_COUNT.

IO_RATE FLOAT I/O rate for each device, in I/Os per second. This isthe number of requests serviced per second.Calculated as IO_COUNT/(TIME_RESOLUTION*60).


NORM_SEQ_STG_RATE FLOAT DASD normal and sequential staging rate, in I/Osper second. Calculated as (CACHE_CANDIDATE -CACHE_CANDIDATE_WR - CACHE_HITS +CACHE_WRITE_HITS) /(TIME_RESOLUTION*60).

PENDING_AVG_MPL FLOAT Average number of users waiting because the startI/O is pending. Calculated as(PENDING_average_MSEC*IO_COUNT)/(TIME_RESOLUTION*60E3).

QUE_WAIT_AVG_MPL FLOAT Average number of users waiting because the startI/O is queued in the system. Average MPL for UCBwait. Calculated as(QUE_WAIT_average_MSEC*IO_COUNT)/(TIME_RESOLUTION*60E3).

READ_HIT_RATE FLOAT Normal and sequential read hit rate, in I/Os persecond. Calculated as (CACHE_HITS -CACHE_WRITE_HITS) /(TIME_RESOLUTION*60).

READ_HITS_PCT FLOAT Number of read hits, in percent. Calculated as100*(CACHE_HITS - CACHE_WRITE_HITS)/(CACHE_CANDIDATE -CACHE_CANDIDATE_WR).

SIO_AVG_MPL FLOAT Average number of users waiting for the start I/O tocomplete. Calculated as ((CONNECT_average_MSEC+ DISCONN_average_MSEC)*IO_COUNT)/(TIME_RESOLUTION*60E3).

SIO_AVG_MSEC FLOAT Average device start I/O time per I/O request, inmilliseconds. Calculated asCONNECT_average_MSEC +DISCONN_average_MSEC.

STAGING_RATE FLOAT DASD staging rate, in I/Os per second. Calculated as(CACHE_CANDIDATE -CACHE_HITS)/(TIME_RESOLUTION*60).

Note: In addition to all the calculated columns described here, this view alsocontains all the data columns described in “MVSPM_STORCLASS_HV” onpage 764.



MVSPM_SWAP_HVThis table provides statistics on swapping activity on MVS systems. It is based onthe MVSPM_SWAP_H table, and its data comes from SMF type 71 records.






SWAP_TYPE k CHAR(4) Acronym for the swap type. This is derived from theswap placement section and can be one of these:

Acronym MeaningTOUT Terminal output waitTIN Terminal input waitLWT Long waitASTO Auxiliary storage shortageRSTO Central pageable storage shortageDWT Detected waitREQ Request swapENQ Enqueue exchangeEXCH Exchange on recommendation valueUNIL UnilateralTRAN Transition to nonswappableICSU Improve central storage usageISPR Improve system paging rateMRSI Make room to swap in a user who has

been swapped out too longAPPC APPC wait

CAND_SWAP_RATE FLOAT Number of swap candidates that were logically swappedper second. Calculated as (SWAP_CANDIDATES −PSWAPS_TO_AUX −PSWAPS_TO_ES)/MEASURED_SEC.

CAND_SWAPPED_PCT FLOAT Number of swap candidates that were logically swapped,as a percentage of the total number of swap candidates.Calculated as (SWAP_CANDIDATES −PSWAPS_TO_AUX −PSWAPS_TO_ES)/(SWAP_CANDIDATES*0.01).

CANDIDATES_SWAPPED FLOAT Number of swap candidates that were logically swapped.Calculated as SWAP_CANDIDATES − PSWAPS_TO_AUX− PSWAPS_TO_ES.

LSWAP_EFF_ES_PCT FLOAT Effective number of logical swaps to expanded storage, asa percentage of the total number of swap candidates.Calculated as 100*(SWAP_CANDIDATES −PSWAPS_TO_AUX + LSWAPS_TO_AUX +SWAPS_MIGRATED)/ SWAP_CANDIDATES.




LSWAP_EFF_ES_RATE FLOAT Effective number of logical swaps to expanded storageper second. Calculated as (SWAP_CANDIDATES −PSWAPS_TO_AUX + LSWAPS_TO_AUX +SWAPS_MIGRATED)/MEASURED_SEC.

LSWAPS_EFF FLOAT Effective number of logical swaps. Calculated asSWAP_CANDIDATES − PSWAPS_TO_AUX +LSWAPS_TO_AUX + SWAPS_MIGRATED −PSWAPS_TO_ES + LSWAPS_TO_ES −SWAPS_MIGRATED.

LSWAPS_EFF_ES FLOAT Effective number of logical swaps to expanded storage.Calculated as SWAP_CANDIDATES −(PSWAPS_TO_AUX + LSWAPS_TO_AUX +SWAPS_MIGRATED).

LSWAPS_EFF_PCT FLOAT Effective number of logical swaps, as a percentage of thetotal number of candidates. Calculated as100*(SWAP_CANDIDATES − PSWAPS_TO_AUX +LSWAPS_TO_AUX + SWAPS_MIGRATED −PSWAPS_TO_ES + LSWAPS_TO_ES −SWAPS_MIGRATED)/ (SWAP_CANDIDATES −PSWAPS_TO_AUX − PSWAPS_TO_ES).

LSWAPS_EFF_RATE FLOAT Effective number of logical swaps per second. Calculatedas LSWAPS_EFF/MEASURED_SEC.

LSWAPS_TO_AUX_PCT FLOAT Number of logical swaps physically swapped to auxiliarystorage, as a percentage of the total number of swaps toauxiliary storage. Calculated asLSWAPS_TO_AUX/(PSWAPS_TO_AUX +LSWAPS_TO_AUX + SWAPS_MIGRATED).

LSWAPS_TO_AUX_RATE FLOAT Number of logical swaps physically swapped to auxiliarystorage per second. Calculated asLSWAPS_TO_AUX/MEASURED_SEC.

LSWAPS_TO_ES_PCT FLOAT Number of logical swaps physically swapped toexpanded storage, as a percentage of the total number ofswap candidates. Calculated asLSWAPS_TO_ES/(SWAP_CANDIDATES*0.01).

LSWAPS_TO_ES_RATE FLOAT Number of logical swaps physically swapped toexpanded storage per second. Calculated asLSWAPS_TO_ES/MEASURED_SEC.

PSWAPS_TO_AUX_PCT FLOAT Number of physical swaps directed to auxiliary storage,as a percentage of the total number of swap candidates.Calculated as PSWAPS_TO_AUX/(SWAP_CANDIDATES*0.01).

PSWAPS_TO_AUX_RATE FLOAT Number of physical swaps directed to auxiliary storageper second. Calculated asPSWAPS_TO_AUX/MEASURED_SEC.

PSWAPS_TO_ES_PCT FLOAT Number of physical swaps directed to expanded storage,as a percentage of the total number of swap candidates.Calculated asPSWAPS_TO_ES/(SWAP_CANDIDATES*0.01).

PSWAPS_TO_ES_RATE FLOAT Number of physical swaps directed to expanded storageper second. Calculated asPSWAPS_TO_ES/MEASURED_SEC.




SWAP_EFF_ES_RATE FLOAT Effective number of swaps to expanded storage persecond. Calculated as (PSWAPS_TO_ES +LSWAPS_TO_ES − SWAPS_MIGRATED)/MEASURED_SEC.

SWAP_MIGRATE_RATE FLOAT Number of physical swaps migrated from expandedstorage to auxiliary storage per second. Calculated asSWAPS_MIGRATED/MEASURED_SEC.

SWAP_RATE FLOAT Number of swap requests per second. Calculated asSWAP_CANDIDATES/MEASURED_SEC.

SWAPS_EFF_ES FLOAT Effective number of swaps to expanded storage.Calculated as PSWAPS_TO_ES + LSWAPS_TO_ES −SWAPS_MIGRATED.

SWAPS_EFF_ES_PCT FLOAT Effective number of swaps to expanded storage, as apercentage of the number of physical and logical swapsto expanded storage. Calculated as 100*(PSWAPS_TO_ES+ LSWAPS_TO_ES − SWAPS_MIGRATED)/(PSWAPS_TO_ES + LSWAPS_TO_ES).

SWAPS_MIGRATED_PCT FLOAT Number of physical swaps migrated from expandedstorage to auxiliary storage, as a percentage of thenumber of physical and logical swaps directed toexpanded storage. Calculated as(SWAPS_MIGRATED/(PSWAPS_TO_ES +LSWAPS_TO_ES))*100.

SWAPS_TO_AUX_PCT FLOAT Number of swaps to auxiliary storage, as a percentage ofthe total number of swap candidates. Calculated as(PSWAPS_TO_AUX + LSWAPS_TO_AUX +SWAPS_MIGRATED) /(SWAP_CANDIDATES*0.01).

SWAPS_TO_AUX_RATE FLOAT Number of swaps to auxiliary storage per second.Calculated as (PSWAPS_TO_AUX + LSWAPS_TO_AUX +SWAPS_MIGRATED)/MEASURED_SEC.

SWAPS_TO_AUX_TOT FLOAT Total number of swaps to auxiliary storage. Calculated asPSWAPS_TO_AUX + LSWAPS_TO_AUX +SWAPS_MIGRATED.

SWAPS_TO_ES_PCT FLOAT Number of swaps directed to expanded storage, as apercentage of the total number of swap candidates.Calculated as (PSWAPS_TO_ES + LSWAPS_TO_ES)/(SWAP_CANDIDATES*0.01).

SWAPS_TO_ES_RATE FLOAT Number of swaps directed to expanded storage persecond. Calculated as (PSWAPS_TO_ES +LSWAPS_TO_ES)/MEASURED_SEC.

SWAPS_TO_ES_TOT FLOAT Total number of swaps directed to expanded storage.Calculated as PSWAPS_TO_ES + LSWAPS_TO_ES.

SWAPS_TRANS_RATE FLOAT Number of swaps to auxiliary storage via transition persecond. Calculated as (LSWAPS_TO_AUX +SWAPS_MIGRATED)/MEASURED_SEC.

SWAPS_VIA_TRANS FLOAT Number of swaps to auxiliary storage via transition.Calculated as LSWAPS_TO_AUX + SWAPS_MIGRATED.

SWAPS_VIATRANS_PCT FLOAT Number of swaps to auxiliary storage via transition, as apercentage of the total number of swaps to auxiliarystorage. Calculated as ((LSWAPS_TO_AUX +SWAPS_MIGRATED)/ (PSWAPS_TO_AUX +LSWAPS_TO_AUX + SWAPS_MIGRATED))*100.



Note: In addition to the calculated columns described here, this view also containsall the data columns described in “MVSPM_SWAP_H” on page 674.



MVSPM_SYSTEM_HVThis view provides statistics on address space and processor activity. It is based onthe MVSPM_SYSTEM_H table, and its data comes from SMF type 70 recordsprocessed through a record procedure (DRL2S070).






APPC_USERS FLOAT Average number of APPC users (or ASCH address spaces).Calculated as APPC_USERS_TOT/SAMPLES.

BATCH_USERS FLOAT Average number of batch users. Calculated asBATCH_USERS_TOT/SAMPLES.

CPU_BUSY_PCT FLOAT CPU busy time, in percent. Calculated as100*CPU_BUSY_SEC/CPU_ONLINE_SEC.

CPU_WAIT_PCT FLOAT Processor wait time, in percent. Calculated as100*CPU_WAIT_SEC/CPU_ONLINE_SEC.

INREADY_USERS FLOAT Average number of in-ready users. Calculated asINREADY_USERS_TOT/SAMPLES.

INREADY1_WAIT_PCT FLOAT Percentage of time that the number of in-ready users washigher than the number of processors. Calculated as100*AS1_WAIT_SAMPLES/SAMPLES.

INREADY2_WAIT_PCT FLOAT Percentage of time that the number of in-ready users was 2or more higher than the number of processors. Calculated as100*AS2_WAIT_SAMPLES/SAMPLES.

INREADY3_WAIT_PCT FLOAT Percentage of time that the number of in-ready users was 3or more higher than the number of processors. Calculated as100*AS3_WAIT_SAMPLES/SAMPLES.

INWAIT_USERS FLOAT Average number of in-wait users. Calculated as(INSTOR_USERS_TOT −INREADY_USERS_TOT)/SAMPLES.

IO_INTR_RATE FLOAT Total number of I/O interrupts handled per second.Calculated as (IO_INTERRUPTS +TPI_INTERRUPTS)/MEASURED_SEC.

LREADY_USERS FLOAT Average number of logically swapped out, but ready users.Calculated as LREADY_USERS_TOT/SAMPLES.

LSWAP_PCT FLOAT Percentage of TSO/E users logically swapped. Calculated as100*(LWAIT_USERS_TOT + LREADY_USERS_TOT)/TSO_USERS_TOT.

LWAIT_USERS FLOAT Average number of logically swapped out and waiting users.Calculated as LWAIT_USERS_TOT/SAMPLES.

LWAIT0_PCT FLOAT Percentage of time that no logical wait users were found (thelogical swap was turned off). Calculated as100*LWAIT0_SAMPLES/SAMPLES.




OUTREADY_USERS FLOAT Average number of out-ready users. Calculated asOUTREADY_USERS_TOT/SAMPLES.

OUTWAIT_USERS FLOAT Average number of out-wait users. Calculated asOUTWAIT_USERS_TOT/SAMPLES.

STC_USERS FLOAT Average number of started users. Calculated asSTC_USERS_TOT/SAMPLES.

TPI_INTR_PCT FLOAT Percentage of interrupts handled by the TPI instruction.Calculated as (TPI_INTERRUPTS*100)/(IO_INTERRUPTS +TPI_INTERRUPTS).

TPI_INTR_RATE FLOAT Number of interrupts handled by the TPI instruction persecond. Calculated as TPI_INTERRUPTS/MEASURED_SEC.

TSO_USERS FLOAT Average number of TSO/E users. Calculated asTSO_USERS_TOT/SAMPLES.

VF_AFFINITY_PCT FLOAT Percentage of time the vector facility was used. Calculated as100*VECTOR_SAMPLES/SAMPLES.

Note: In addition to the calculated columns described here, this view also containsall the data columns described in “MVSPM_SYSTEM_H” on page 676.



MVSPM_SYSTEM_PVThis view, which is based on the MVSPM_SYSTEM_H table, provides the totalmeasured time per period. It is used in reports to calculate average rates orpercentages per period.


DATE k DATE Date of the mid measurement. From SMF70DAT, SMF70IST, andSMF70INT.



MEASURED_SEC FLOAT Measured time period, in seconds. This is the duration of the RMFmeasurement intervals. Calculated as the sum of SMF70INT/1000.



MVSPM_WORKLOAD_HVThis view provides statistics on MVS activity by workload type and performancegroup. It is based on the MVSPM_WORKLOAD_H table, and its data comes fromSMF type 72, subtype 1 records.












ACTIVE_USERS FLOAT Average number of users that were active. Calculated asTRAN_ACTIVE_SEC /(TIME_RESOLUTION*60).

BLK_PAGEIN_RATE FLOAT Number of blocked pages paged in per second.Calculated as PAGEINS_BLK/(TIME_RESOLUTION*60).

CPU_BUSY_PCT FLOAT Total CPU busy time, in percent. Calculated as100*((TCB_TIME_FACTOR /SERVICE_UNITS_MAX) +(SRB_TIME_FACTOR/SERVICE_UNITS_MAX) +RCT_SEC + IOINTR_SEC + HIPER_SERVICE_SEC)/(TIME_RESOLUTION*60).

CPU_HIPER_PCT FLOAT Percentage of CPU time used for hiperspace processing.Calculated as 100*HIPER_SERVICE_SEC/(TIME_RESOLUTION*60).

CPU_IOINTR_PCT FLOAT Percentage of CPU time used for processing I/Ointerrupts. Calculated as100*IOINTR_SEC/(TIME_RESOLUTION*60).




CPU_PER_TRAN FLOAT Total CPU time per transaction, in seconds. Calculated as((TCB_TIME_FACTOR /SERVICE_UNITS_MAX) +(SRB_TIME_FACTOR/SERVICE_UNITS_MAX) +RCT_SEC + IOINTR_SEC + HIPER_SERVICE_SEC)/TRANSACTIONS.

CPU_SRB_PCT FLOAT Percentage of SRB CPU time used. This is based on thenumber of CPU service units. Calculated as100*(SRB_TIME_FACTOR/ SERVICE_UNITS_MAX)/(TIME_RESOLUTION*60).

CPU_TCB_PCT FLOAT Percentage of TCB CPU time used. This is based on thenumber of CPU service units. Calculated as100*(TCB_TIME_FACTOR /SERVICE_UNITS_MAX)/(TIME_RESOLUTION*60).

CS_WORKING_SET_MB FLOAT Average central storage per user, in megabytes.Calculated as (TOT_FRAME_SECONDS −ES_FRAME_SECONDS)/ TRAN_RESIDENT_SEC/256.

CS_FRAME_SECONDS FLOAT Central storage active frame time, in seconds. Calculatedas TOT_FRAME_SECONDS − ES_FRAME_SECONDS.

CSTORAGE_USED_MB FLOAT Total central storage used, in megabytes. Calculated as(TOT_FRAME_SECONDS − ES_FRAME_SECONDS)/(TIME_RESOLUTION*60)/256.

DEM_PAGES_PER_TRAN FLOAT Number of demand pages per transaction. Calculated as(PAGEINS + READ_MISSES_HIPER)/TRANSACTIONS.

ES_WORKING_SET_MB FLOAT Average expanded storage per user, in megabytes.Calculated as ES_FRAME_SECONDS/(TIME_RESOLUTION*60)/256.

ESBLK_PAGEIN_RATE FLOAT Number of blocked pages paged in from expandedstorage. This does not include the first page of each block.Calculated asPAGEINS_BLK_ES/(TIME_RESOLUTION*60).

ESTORAGE_USED_MB FLOAT Total expanded storage used, in megabytes. Calculated asES_FRAME_SECONDS /(TIME_RESOLUTION*60)/256.

FRAMES_PER_USER FLOAT Average number of frames per swapped-in user.Calculated as ((TOT_FRAME_SECONDS −ES_FRAME_SECONDS) /TRAN_RESIDENT_SEC/256)*(TRAN_RESIDENT_SEC /(TIME_RESOLUTION*60)).

HS_PAGEIN_RATE FLOAT Number of hiperspace page-ins per second. Calculated asPAGEINS_HIPER/(TIME_RESOLUTION*60).

HS_READ_MISS_RATE FLOAT Number of hiperspace read misses per second. Calculatedas READ_MISSES_HIPER /(TIME_RESOLUTION*60).

INSTORAGE_USERS FLOAT Average number of users in storage. Calculated asTRAN_RESIDENT_SEC /(TIME_RESOLUTION*60).

IO_RATE FLOAT Number of input/output operations serviced per second.This is based on the number of I/O service units.Calculated asIO_RATE_FACTOR/(TIME_RESOLUTION*60).

OUTREADY_PER_TRAN FLOAT Average out and ready time per transaction, in seconds.Calculated as ((TRAN_ACTIVE_SEC/(TIME_RESOLUTION*60)) − (TRAN_RESIDENT_SEC/(TIME_RESOLUTION*60)))*(TRAN_ELAPSED_SEC/TRANSACTIONS)/(TRAN_ACTIVE_SEC /(TIME_RESOLUTION*60)).




OUTREADY_USERS FLOAT Average number of users that were swapped out, butwere ready. Calculated as (TRAN_ACTIVE_SEC −TRAN_RESIDENT_SEC) /(TIME_RESOLUTION*60).

PA_PAGEIN_RATE FLOAT Number of private area page-ins per second. Calculatedas PAGEINS/(TIME_RESOLUTION*60).

PAGEIN_RATE FLOAT Number of page-in operations per second. Calculated as(READ_MISSES_HIPER +PAGEINS)/(TIME_RESOLUTION*60).

RESP_VARIATION FLOAT Response-time variation. Calculated as(ELAPSED_SEC_SQsum −(TRAN_ELAPSED_SEC*TRAN_ELAPSED_SEC/TRANSACTIONS))/(TRANSACTIONS − 1).

RESPONSE_SEC FLOAT Average transaction response time, in seconds. Calculatedas TRAN_ELAPSED_SEC/TRANSACTIONS.

SHARED_PAGEIN_RATE FLOAT Number of page-ins for shared page groups per second.Calculated asPAGEINS_SHARED/TIME_RESOLUTION*60.

STORAGE_USED_MB FLOAT Total storage used, in megabytes. Calculated asTOT_FRAME_SECONDS/(TIME_RESOLUTION*60)/256.

SWAP_RATE FLOAT Average number of swap sequences per second.Calculated as SWAP_SEQUENCES/(TIME_RESOLUTION*60).

SWAPS_PER_TRAN FLOAT Average number of swap sequences per transaction.Calculated as SWAP_SEQUENCES/TRANSACTIONS.

TRAN_ACTIVE_MIN FLOAT Average active system time per transaction, in minutes.Calculated as TRAN_TOT_SEC/TRANSACTIONS/60.

TRAN_PER_MIN FLOAT Number of transactions per minute. Calculated asTRANSACTIONS/TIME_RESOLUTION.

TRAN_PER_SEC FLOAT Number of transactions per second. Calculated asTRANSACTIONS/(TIME_RESOLUTION*60).

UNBLK_PAGEIN_RATE FLOAT Number of unblocked pages paged in from expandedstorage per second. Calculated as PAGEINS_UNBLK_ES/(TIME_RESOLUTION*60).

WORKING_SET_MB FLOAT Average processor storage per user, in megabytes.Calculated as TOT_FRAME_SECONDS/256/TRAN_RESIDENT_SEC.

Note: In addition to the calculated columns described here, this view also containsall the data columns described in “MVSPM_WORKLOAD_H” on page 708.



MVSPM_WORKLOAD2_HVThis view provides statistics on MVS activity by workload type and service class,when the system is running in goal mode. It is based on theMVSPM_WORKLOAD2_H table, and contains data from SMF type 72, subtype 3records.











ACTIVE_USERS FLOAT Average number of users that were active. Calculated asTRAN_ACTIVE_SEC/MEASURED_SEC.

BLK_PAGEIN_RATE FLOAT Number of blocked pages paged in per second.Calculated as PAGEINS_BLK/MEASURED_SEC.

CPU_BUSY_PCT FLOAT Total CPU busy time, in percent. Calculated as100*(TCB_SECONDS + SRB_SECONDS + IOINTR_SEC +RCT_SEC + HIPER_SERVICE_SEC)/MEASURED_SEC.

CPU_HIPER_PCT FLOAT Percentage of CPU time used for hiperspace processing.Calculated as100*HIPER_SERVICE_SEC/MEASURED_SEC.

CPU_IOINTR_PCT FLOAT Percentage of CPU time used processing I/O interrupts.Calculated as 100*IOINTR_SEC/MEASURED_SEC.

CPU_PER_TRAN FLOAT Total CPU time per transaction, in seconds. Calculated as(TCB_SECONDS + SRB_SECONDS + IOINTR_SEC +RCT_SEC + HIPER_SERVICE_SEC)/TRANSACTIONS.

CPU_SRB_PCT FLOAT Percentage of SRB CPU time used. Based on service units.Calculated as 100*SRB_SECONDS/MEASURED_SEC.

CPU_TCB_PCT FLOAT Percentage of TCB CPU time used. This is based on thenumber of CPU service units. Calculated as100*TCB_SECONDS/MEASURED_SEC.

CS_FRAME_SECONDS FLOAT Central storage active frame time, in seconds. Calculatedas TOT_FRAME_SECONDS - ES_FRAME_SECONDS.

CSTORAGE_USED_MB FLOAT Total central storage used, in megabytes. Calculated as(TOT_FRAME_SECONDS - ES_FRAME_SECONDS) /MEASURED_SEC/256.




CS_WORKING_SET_MB FLOAT Average central storage per user, in megabytes.Calculated as (TOT_FRAME_SECONDS -ES_FRAME_SECONDS) /TRAN_RESIDENT_SEC/256.

DEM_PAGES_PER_TRAN FLOAT Number of demand pages per transaction. Calculated as(PAGEINS + READ_MISSES_HIPER)/TRANSACTIONS.

ESBLK_PAGEIN_RATE FLOAT Number of blocked pages paged in from expandedstorage. This does not include the first page of each block.Calculated as PAGEINS_BLK_ES/MEASURED_SEC.

ESTORAGE_USED_MB FLOAT Total expanded storage used, in megabytes. Calculated asES_FRAME_SECONDS/MEASURED_SEC/256.

ES_WORKING_SET_MB FLOAT Average expanded storage per user, in megabytes.Calculated asES_FRAME_SECONDS/MEASURED_SEC/256.

FRAMES_PER_USER FLOAT Average number of frames per swapped-in user.Calculated as ((TOT_FRAME_SECONDS -ES_FRAME_SECONDS) /TRAN_RESIDENT_SEC/256) *(TRAN_RESIDENT_SEC/MEASURED_SEC).

HS_PAGEIN_RATE FLOAT Number of hiperspace page-ins per second. Calculated asPAGEINS_HIPER/MEASURED_SEC.

HS_READ_MISS_RATE FLOAT Number of hiperspace read misses per second. Calculatedas READ_MISSES_HIPER/MEASURED_SEC.

INSTORAGE_USERS FLOAT Average number of users in storage. Calculated asTRAN_RESIDENT_SEC/MEASURED_SEC.

IO_RATE FLOAT Number of input/output operations serviced per second.Based on I/O service units. Calculated asIO_COUNT/MEASURED_SEC.

OUTREADY_PER_TRAN FLOAT Average out and ready time per transaction, in seconds.Calculated as ((TRAN_ACTIVE_SEC/MEASURED_SEC) -(TRAN_RESIDENT_SEC/MEASURED_SEC)) *(TRAN_ELAPSED_SEC/TRANSACTIONS) /(TRAN_ACTIVE_SEC/MEASURED_SEC).

OUTREADY_USERS FLOAT Average number of users that were swapped out, butwere ready. Calculated as (TRAN_ACTIVE_SEC -TRAN_RESIDENT_SEC)/MEASURED_SEC.

PAGEIN_RATE FLOAT Number of page-in operations per second. Calculated as(READ_MISSES_HIPER + PAGEINS)/MEASURED_SEC.

PA_PAGEIN_RATE FLOAT Number of private area page-ins per second. Calculatedas PAGEINS/MEASURED_SEC.

RESPONSE_SEC FLOAT Average transaction response time, in seconds. Calculatedas TRAN_ELAPSED_SEC/TRANSACTIONS.

RESP_VARIATION FLOAT Response time variation. Calculated as(ELAPSED_SEC_SQsum -(TRAN_ELAPSED_SEC*TRAN_ELAPSED_SEC/TRANSACTIONS)) (TRANSACTIONS-1).

SHARED_PAGEIN_RATE FLOAT Number of page-ins for shared page groups per second.Calculated as PAGEINS_SHARED/MEASURED_SEC.

STORAGE_USED_MB FLOAT Total storage used, in megabytes. Calculated asTOT_FRAME_SECONDS /MEASURED_SEC/256.

SWAP_RATE FLOAT Average number of swap sequences per second.Calculated as SWAP_SEQUENCES/MEASURED_SEC.




SWAPS_PER_TRAN FLOAT Average number of swap sequences per transaction.Calculated as SWAP_SEQUENCES/TRANSACTIONS.

TRAN_ACTIVE_MIN FLOAT Average active system time per transaction. in minutes.Calculated as TRAN_ACTIVE_SEC/TRANSACTIONS/60.

TRAN_PER_MIN FLOAT Number of transactions per minute. Calculated as60*TRANSACTIONS/MEASURED_SEC.

TRAN_PER_SEC FLOAT Number of transactions per second. Calculated asTRANSACTIONS/MEASURED_SEC.

UNBLK_PAGEIN_RATE FLOAT Number of unblocked pages paged in from expandedstorage per second. Calculated asPAGEINS_UNBLK_ES/MEASURED_SEC.

WORKING_SET_MB FLOAT Average processor storage per user, in megabytes.Calculated as TOT_FRAME_SECONDS/256/TRAN_RESIDENT_SEC.

Note: In addition to all the calculated columns described here, this view alsocontains all the data columns described in “MVSPM_WORKLOAD2_H” onpage 711.



MVSPM_WORKLOADX_HVThis view provides statistics on MVS activity by workload type and service class,when the system is running in goal mode. It is based on theMVSPM_WORKLOAD2_H table, and contains data from SMF type 72, subtype 3records.









SCLASS_AND_PERIOD k CHAR(1) Service class name and service class period numberconcatenated. Calculated as SERVICE_CLASS +SERV_CLASS_PERIOD



CAPPING_PCT FLOAT Percentage of CPU capping delay samples. Calculated as100*CPU_CAP_DELAY_CNT/TOTAL_EXECUTION_S.

CPU_DELAY_PCT FLOAT Percentage of CPU delay samples. Calculated as100*CPU_DELAY_CNT/TOTAL_EXECUTION_S.

CPU_USE_PCT FLOAT Percentage of CPU using samples. Calculated as100*CPU_USE_CNT/TOTAL_EXECUTION_S.

CRYPTO_USE_PCT FLOAT Percentage of all cryptographic processors using samples.Calculated as 100*(CRYPTO_CAM_USE_CNT+CRYPTO_AP_USE_CNT)/TOTAL_EXECUTION_S.

CRYPTO_DEL_PCT FLOAT Percentage of all cryptographic processors delay samples.Calculated as 100*(CRYPTO_CAM_DEL_CNT+CRYPTO_AP_DEL_CNT+CRYPTO_FQ_DEL_CNT)/TOTAL_EXECUTION_S.

DASD_CONNECT_TIME FLOAT Average DASD connect time. Calculated asDASD_NP_CNT_TIME/DASD_NP_IO_SCHAN_N.

DASD_DELAY_SAMPLES REAL DASD delay samples. Calculated as the sum ofR723CIOD.

DASD_DISCONCT_TIME FLOAT Average DASD diconnect time. Calculated asDASD_NP_DSCNT_TIME/DASD_NP_IO_SCHAN_N.

DASD_IOS_QUE_TIME FLOAT Average DASD IOS queue time. Calculated asDASD_IO_QUEUE_TIME/DASD_NP_IO_SCHAN_N.

DASD_IO_QUEUE_TIME FLOAT Total DASD IOS queue time, in seconds. Calculated as thesum of R723CIOT.



|

|

|


DASD_NP_CNT_TIME FLOAT Total nonpaging DASD connect time, in seconds.Calculated as the sum of R723CICT.

DASD_NP_WAIT_TIME FLOAT Total nonpaging DASD wait (queue + pending) time, inseconds. Calculated as the sum of R723CIWT.

DASD_NP_DSCNT_TIME FLOAT Total nonpaging DASD disconnect time, in seconds. Thisdoes not include IOS queue time. Calculated as the sumof R723CIDT.

DASD_NP_IO_SCHAN_N REAL Total nonpaging DASD I/O start subchannel count.Calculated as the sum of R723CIRC.

DASD_PENDING_TIME FLOAT Average DASD pending time. Calculated asDASD_NP_WAIT_TIME/DASD_NP_IO_SCHAN_N.

DASD_RESPONSE_TIME FLOAT Average DASD response time. Calculated as(DASD_NP_CNT_TIME+DASD_NP_WAIT_TIME+DASD_NP_DSCNT_TIME+DASD_IO_QUEUE_TIME)/DASD_NP_IO_SCHAN_N).

DASD_USING_SAMPLES REAL DASD using samples. Only nonpaging DASD I/O cancontribute to I/O using samples. Calculated as the sum ofR723CIOU.

ESTOR_IND CHAR(1) Indicates whether the system has expanded storage;1=yes, 0=no. From the first bit of SMF72PRF.

EXECUTION_VELOCITY FLOAT Execution velocity in percentage. Calculated as100*TOTAL_USING_SAMPLE/(TOTAL_USING_SAMPLE+TOTAL_DELAY_CNT).

HPRSPACE_PG_DLY_S REAL Paging delay samples for server hiperspace. Calculated asthe sum of R723CSHS.

IDLE_PCT FLOAT Percentage of idle delay samples. Calculated as100*IDLE_CNT/TOTAL_EXECUTION_S.


IO_DELAY_PCT FLOAT I/O delay in percentage. Calculated as100*DASD_DELAY_SAMPLES/TOTAL_EXECUTION_S.

IO_USING_PCT FLOAT Percentage of I/O using samples. Calculated as100*DASD_USING_SAMPLES/TOTAL_EXECUTION_S.


MPL_DELAY_PCT FLOAT Percentage of MPL delay samples. Calculated as100*MPL_DELAY_CNT/TOTAL_EXECUTION_S.

MPL_DELAY_SAMPLES REAL Server MPL delay samples. Calculated as the sum ofR723CSMP.

MVS_RESOURCE_GROUP CHAR(8) MVS resource group name. From R723GGNM.

PRVT_AREA_PG_DLY_S REAL Paging delay samples for server private area. Calculatedas the sum of R723CSPV.

QUEUE_DELAY_TIMEF FLOAT Total queue delay time, in seconds. Calculated as the sumof R723CQDT.

QUEUE_DELAY_SAMPLE REAL Queue delay samples, work is waiting for a server.Calculated as the sum of R723CQ.

QUEUE_PCT FLOAT Queue delay in percentage. Calculated as100*QUEUE_DELAY_SAMPLE/TOTAL_EXECUTION_S.




RECORD_LEVEL SMALLINT SMF record level change Number. This column enablesprocessing of DMF record level changes in an existingrelease. From R72SRL.

REPORT_PERIOD_FLAG CHAR(1) Report class period flag: 1=Heterogeneous class (morethan one service class for the same report class),0=Homogeneous report class period (only one serviceclass for this report class). Blank if this is a service classperiod. From R723CRS1.

RMF_INTERVAL FLOAT Duration of the RMF measurement interval, in minutes.From SMF72INT.

RMF_VERSION SMALLINT RMF version number. From R72MFV.

SERV_CLASS_TYPE CHAR(1) Service class (SC) type. This can be C (control), or R(reporting). All data in reporting SCs is also reported in acontrol SC. So, when summaries are produced, onlycontrol SCs should be selected. From R723MSCF.

SERV_FOR_REPORT CHAR(8) Service class that last contributed to this report class.Blank if this is a service class. From R723CLSC.

SERVER_DELAY_PCT FLOAT Total server delay in percentage. Calculated as100*(PRVT_AREA_PG_DLY_S+SPACE_VIO_PG_DLY_S+HPRSPACE_PG_DLY_S+MPL_DELAY_SAMPLES+SWAP_DELAY_SAMPLES)/TOTAL_EXECUTION_S).


SPACE_VIO_PG_DLY_S REAL Paging delay samples for server space VIO. Calculated asthe sum of R723CSVI.

SWAP_DELAY_SAMPLES REAL Server swap-in delay samples. Calculated as the sum ofR723CSSW.

SYSTEM_NAME CHAR(8) System name for the current system (as defined inCVTSNAME). From R723SNM.

SYSPLEX_NAME CHAR(8) Sysplex name (as defined in ECVTSPLX). FromR723XNM.


SWAP_DELAY_PCT FLOAT Percentage of swap delay samples. Calculated as100*SWAP_DELAY_CNT/TOTAL_EXECUTION_S.


TIME_BJ_INELIGIBLE FLOAT Total time, in seconds, that batch jobs were ineligible torun because a resource to which the job had affinity wasunavailable. Calculated as the sum of R723CADT.

TIME_BJ_JCL_CONVER FLOAT Total time, in seconds, that batch jobs spent in JCLconversion. Calculated as the sum of R723CCVT.

TIME_BJ_JOB_QUEUE FLOAT Total time, in seconds, that batch jobs spent on the jobqueue after JCL conversion, while ineligible to run on anysystem for reasons other than resource affinities.Calculated as the sum of R723CIQT.

TOTAL_EXECUTION_S FLOAT Total execution samples. Calculated as the sum ofR723CTSA.



|

|


TOTAL_USING_SAMPLE REAL Total using samples. For the velocity formula, see OS/390MVS Planning: Workload Management. Calculated as thesum of R723CTOU.

START_SUBCHAN_RATE FLOAT Start subchannel rate. Calculated asDASD_NP_IO_SCHAN_N/MEASURED_SEC.

STORAGE_PCT FLOAT Percentage of global storage samples. Calculated as100*(PRIV_PG_DELAY_CNT+COMM_PG_DELAY_CNT+XMEM_PG_DELAY_CNT+VIO_PG_DELAY_CNT+HIPER_PG_DELAY_CNT+ESOHI_PG_DELAY_CNT)/TOTAL_EXECUTION_S).

UNKNOWN_PCT FLOAT Percentage of delay samples with unknown reason.Calculated as100*UNKNOWN_DELAY_CNT/TOTAL_EXECUTION_S.

UNKNOWN_PCT FLOAT Percentage of delay samples with unknown reason.Calculated as100*UNKNOWN_DELAY_CNT/TOTAL_EXECUTION_S.

TRAN_AFFINITY_D_TM FLOAT Average delay time that transactions were ineligiblebecause of unavailable resource affinities. Calculated asTIME_BJ_INELIGIBLE/TRANSACTIONS.

TRAN_INELIG_QUE_TM FLOAT Average time that ineligible transactions spent on the jobqueue. Calculated asTIME_BJ_JOB_QUEUE/TRANSACTIONS.

TRAN_JCL_CONVER_TM FLOAT Average time that transactions spent in JCL conversion.Calculated as TIME_BJ_JCL_CONVER/TRANSACTIONS.

TRAN_QUEUE_TIME FLOAT Average time that a transaction spent on the job queue.Calculated as QUEUE_ DELAY_TIME/TRANSACTIONS.



MVSPM_XCF_PATH_HVThis view provides statistics on the XCF message traffic between signalling pathsconnecting the local system with remote systems. It is based on theMVSPM_XCF_PATH_H table, and its data comes from SMF type 74, subtype 2records written by Monitor III XCF measurement.






LOCAL_SYSTEM k CHAR(8) Name of the local system. From R742PNME.

OTHER_SYSTEM k CHAR(8) Name of the system on the other end, if known; otherwise,this is blank. From R742PONA.

TRANSPORT_CLASS k CHAR(8) Transport class name. This is blank for an inbound path.From R742PTCN.

DIRECTION k CHAR(3) Direction of the path. IN = inbound path, or OUT =outbound path. From R742PDIR.

DEVICE_NUM k CHAR(4) Device number. Blank if XES list structure is being used.From R742PDEV.

OTHER_DEVICE_NO k CHAR(4) Number of the device on the other end, if known;otherwise, this is blank. From R742PODV.

STRUCTURE_NAME k CHAR(16) Name of XES list structure being used as a path, blank forCTCs. From R742PSTR.

AVG_IO_TRAN_TIME FLOAT Average I/O transfer time for the most recently receivedsignals for inbound paths, in seconds. From R742PIOT.

SIGNAL_RATE FLOAT Number of XCF signals sent or received per second.Calculated as SIGNALS/MEASURED_SEC.

TIMES_BUSY_PCT FLOAT Percentage of times the signalling path was busy when itwas selected to transfer a message. Calculated as100*TIMES_BUSY/SIGNALS.

TIMES_NOT_BUSY_PCT FLOAT Percentage of times the signalling path was not busy whenit was selected to transfer a message. Calculated as100*TIMES_NOT_BUSY/SIGNALS.

Note: In addition to the calculated columns described here, this view also containsall the data columns described in “MVSPM_XCF_PATH_H” on page 718.



MVSPM_XCF_SYS_HVThis view provides statistics on the XCF message traffic between the local andremote systems. It is based on the MVSPM_XCF_PATH_H table, and its datacomes from SMF type 74, subtype 2 records written by Monitor III XCFmeasurement.






LOCAL_SYSTEM k CHAR(8) Name of the local system. From R742SNME in the sectionfor the local system.

OTHER_SYSTEM k CHAR(8) Name of the system at the other end. For local traffic, thisis the same as the local system. From R742SNME.

TRANSPORT_CLASS k CHAR(8) Transport class name. This is blank for inbound direction.From R742STCN.

DIRECTION k CHAR(3) Direction of the message traffic. IN = inbound (the systemsent messages to the local system); OUT = outbound (thesystem received messages from the local system); or LOC= local (the message traffic was within the local system).From R742SDIR.

MESSAGE_RATE FLOAT Total number of messages sent or received per second.Calculated as (MESSAGES_BIG + MESSAGES_FIT +MESSAGES_SMALL)/MEASURED_SEC.

MESSAGES_BIG_PCT FLOAT Number of big-message conditions, as a percentage of thetotal number of messages. This is zero for inbounddirection. Calculated as100*MESSAGES_BIG/(MESSAGES_BIG + MESSAGES_FIT+ MESSAGES_SMALL).

MESSAGES_DEGR_PCT FLOAT Number of big messages that exceeded the messagelength for which XCF was optimized, as a percentage ofthe total number of big messages. This is zero forinbound direction. Calculated as100*MESSAGES_DEGRADED /MESSAGES_BIG.

MESSAGES_FIT_PCT FLOAT Number of message fit conditions, as a percentage of thetotal number of messages. This is zero for inbounddirection. Calculated as100*MESSAGES_FIT/(MESSAGES_BIG + MESSAGES_FIT+ MESSAGES_SMALL).

MESSAGES_SMALL_PCT FLOAT Number of small-message conditions, as a percentage ofthe total number of messages. This is zero for inbounddirection. Calculated as100*MESSAGES_SMALL/(MESSAGES_BIG +MESSAGES_FIT + MESSAGES_SMALL).




MESSAGES_TOT FLOAT Total number of messages sent or received. Calculated asMESSAGES_BIG + MESSAGES_FIT +MESSAGES_SMALL.

Note: In addition to the calculated columns described here, this view also containsall the data columns described in “MVSPM_XCF_SYS_H” on page 720.



Lookup tablesThis section describes the lookup tables specific to the MVS performancemanagement component.

MVSPM_DEVICE_ADDRThis lookup table converts MVS device Numbers to a synonym. It is also used toassociate the cache subsystem ID with the logical control unit number for DASDdevices.

Converting device Numbers to a synonym is useful in accounting for devices (suchas tape units, communication devices, and printers) as a group, rather than byindividual device number. This reduces the number of rows in the device tables,and improves collect and report performance.

This table updates the MVSPM_DEVICE_H and MVSPM_DEVICE_AP_H tables.


MVS_SYSTEM_ID k CHAR(4) MVS system ID. This can contain global searchcharacters.

LCU_NUM k CHAR(4) MVS logical control unit number. This can containglobal search characters.

DEVICE_NUM k CHAR(4) MVS device number. This can contain global searchcharacters.

CACHE_SUBSYSTEM_ID CHAR(4) 3390 cache subsystem ID.

DESCRIPTION VARCHAR(30) Description for the LCU number or device number.

DEVICE_NUM_CONV CHAR(4) MVS device number that should substitute thenumber matching the MVS_SYSTEM_ID andLCU_NUM or DEVICE_NUM, or both.

VOLSER CHAR(6) Volume serial number to be used.


MVS DEVICE CACHESYSTEM LCU DEVICE Number SUBSYSTEM

ID Number Number CONV ID VOLSER DESCRIPTION------ ------ ------ ------- --------- ------ ----------------MVS1 09 011_ - 0036 - UNIT=3390 CachedMVS1 0F 014_ - 0040 - UNIT=3390 CachedMVS1 0F 015_ - 0040 - UNIT=3390 CachedMVS1 0F 016_ - 0040 - UNIT=3390 CachedMVS1 0F 017_ - 0040 - UNIT=3390 CachedMVS1 1A 054_ 0540 - TAPE1A UNIT=3490MVS1 22 056_ 0560 - TAPE22 UNIT=3480MVS1 27 059_ 0590 - TAPE27 UNIT=3420

MVS performance management lookup tables


MVSPM_TIME_RESThis lookup table defines the time resolution to use for each row of data stored ina set of tables. This enables you to specify that data should be recorded for a timeperiod other than 1 hour.


HOUR k SMALLINT Hour of the day (that the time resolution applies to); 00 to 23.

PERIOD_NAME k CHAR(8) Name of the period. This can contain global search characters.

SYSTEM_ID k CHAR(8) Name of the system. This can contain global search characters.

TABLE_SET_NAME k CHAR(18) Name that identifies the set of tables the time resolution isdefined for.

TIME_RESOLUTION SMALLINT Time resolution for the set of tables, in minutes. This definesthe time period for which data is to be recorded. Valid valuesare 1, 2, 3, 5, 6, 10, 12, 15, 20, and 30 or any multiple of 60.


TABLEPERIOD SYSTEM SET TIME

HOUR NAME ID NAME RESOLUTION---- -------- -------- ------------------ ----------% PRIME % MVSPM% 30% % % MVSPM% 120



MVSPM_UNIT_TYPEThis lookup table converts MVS unit codes to a device class and a unit type. Thistable updates the MVSPM_DEVICE_H and MVSPM_DEVICE_AP_H tables.


UNIT_CODE k CHAR(4) MVS unit code as defined by the last 2 bytes of the UCB unittype field. This can contain global search characters.

DESCRIPTION VARCHAR(30) Description for the unit code.

DEVICE_CLASS CHAR(5) Mnemonic for the MVS device class.

UNIT_TYPE CHAR(8) Mnemonic for the MVS device type. This can be DASD, TAPE,GRAPH, UR, or COMM.


UNIT DEVICE UNITCODE CLASS TYPE DESCRIPTION---- ------ -------- --------------------------------2002 DASD 3370 IBM direct access storage2006 DASD 2305 IBM fixed head storage200A DASD 3340 IBM direct access storage200D DASD 3330-11 IBM disk storage200E DASD 3380-A,B IBM direct access storage200F DASD 3390 IBM direct access storage device201E DASD 3380-D IBM direct access storage2024 DASD 3390-3 IBM direct access storage device20__ DASD ???? Unknown DASD unit8001 TAPE 2400 IBM magnetic tape8080 TAPE 3480 IBM magnetic tape subsystem80__ TAPE ???? Unknown tape unit0808 UR 1403 IBM printer0809 UR 3211 IBM printer080E UR 3800 IBM printing subsystem0810 UR 2671 IBM paper tape reader0819 UR 3895 IBM document reader inscriber081B UR 1287 IBM optical reader08__ UR ???? Unknown unit record1002 GRAPH 2250 IBM display unit



Chapter 33. Reports

The MVS performance management component provides these reports:v Daily performance overview

– MVSPM Workload Descriptions report– MVSPM Goal mode Workload Descriptions report– MVSPM CPU and Processor Storage Activity Overview report– MVSPM Workload Resource Utilization Overview report– MVSPM Workload Response Time Components Overview report– MVSPM Response Time Goals vs Actuals, Overview report– MVSPM Execution Velocity Goals & Actuals, Overview report– MVSPM DASD Activity Overview report

v Processor and storage resources– MVSPM Average CPU Busy, Daily/Hourly Trend report– MVSPM Average CPU Busy Profile, Hourly Trend report– MVSPM CPU Busy and Other Indicators, Hourly Trend report– MVSPM System Central Storage Map, Hourly Trend report– MVSPM System Expanded Storage Map, Hourly Trend report– MVSPM Minimum Available Exp Storage, Hourly Trend report– MVSPM Average High UIC Profile, Hourly Trend report– MVSPM Page Data Set Response Time, Hourly Trend report– MVSPM Page Data Set Device Resp Time, Hourly Trend report– MVSPM Page Data Set Busy Time, Hourly Trend report– MVSPM System Storage Paging Rates, Hourly Trend report– MVSPM CPU Busy Profile Shared LPARs, Hourly Trend report– MVSPM CPU Busy by Shared LPARs, Hourly Trend report– MVSPM Percent of Share Used by LPARs, Hourly Trend report– MVSPM LPAR Management Time, Hourly Trend report– MVSPM Avg CF Busy Profile, Hourly Trend report– MVSPM Avg CF Storage Usage, Hourly Trend report– MVSPM CF, Processor and Storage, Overview report– MVSPM CF, Request Rate, Overview report– MVSPM CF, System Details, Overview report– MVSPM CF, Structures Details, Overview report– MVSPM MIPS for Machine Model List report– MVSPM MIPS for specific System ID report– MVSPM MIPS for System ID Hourly List report– MVSPM Total CPU MIPS per LPAR and System report

v Application use of resources– MVSPM System Resources by Workload Type report– MVSPM CPU Busy by Workload Types, Hourly Trend report– MVSPM CPU Busy by Workload PGNs, Hourly Trend report– MVSPM Storage Used by Workload Type, Hourly Trend report– MVSPM Storage Used by Workload PGNs, Hourly Trend report– MVSPM I/O Rate by Workload Types, Hourly Trend report– MVSPM CPU per I/O by Workload Type, Hourly Trend report– MVSPM CPU per I/O by Workload PGNs, Hourly Trend report– MVSPM Page-ins by Workload Types, Hourly Trend report– MVSPM Paging Activity by Workload, Hourly Trend report– MVSPM Resp Time by Workload Types, Hourly Trend report– MVSPM Workload Resp Time Components, Hourly Trend report– MVSPM BMF Member Page Reads/Hits, Hourly Trend report

789

||||

– MVSPM BMF Directory Page Reads/Hits, Hourly Trend report– MVSPM APPC, CPU and I/O by Transaction Class report– MVSPM APPC, Execution and Queueing, Hourly Trend report– MVSPM VLF Usage and Hit Ratio, Hourly/Daily Trend report– MVSPM VLF Dataspace Usage, Hourly/Daily Trend report– MVSPM Applications Waiting on ENQs, Hourly Trend report– MVSPM Applications Waiting on ENQs, Worst Case report– MVSPM Response Time Goals & Actuals, Hourly Trend report– MVSPM Exec. Velocity Goals & Actuals, Hourly Trend report– MVSPM Response Time Distribution report– MVSPM Served Service Classes, Overview report– MVSPM Response Time Breakdown, Overview report– MVSPM Response Time Breakdown, Hourly Trend report

v I/O subsystem performance– MVSPM Channel Path Busy report– MVSPM I/O Rate for LCUs, Hourly Trend report– MVSPM I/O Response Time for LCUs, Hourly Trend report– MVSPM I/O Response Time Components for LCUs report– MVSPM No of Users Waiting for Device, Daily Trend report– MVSPM I/O Response Time Components, DASD Devices report– MVSPM I/O Rate for Devices by Workload Type report– MVSPM I/O Response Time for Device, Hourly Trend report– MVSPM Cache Hit Rates by CU, Hourly Trend report– MVSPM DFW Hit Rates by CU, Hourly Trend report– MVSPM Staging Rates by CU, Hourly Trend report– MVSPM Overall Effectiveness by CU, Daily Overview report– MVSPM Highest Hit Rate Volumes, Daily Overview report– MVSPM Highest Staging Rate Volumes, Daily Overview report– MVSPM Cache CU Operations by CU, Daily Overview report– MVSPM Cache CU Operations, Hourly Trend report– MVSPM Applications Waiting on ENQs, Worst Case report– MVSPM I/O Response Time for Devices by Workload report– MVSPM I/O Rate by Workload on Selected Devices report– MVSPM XCF Statistics by System, Overview report– MVSPM XCF Signal Rates, Hourly Trend report– MVSPM XCF Activity by Path and System, Overview report– MVSPM Data Set Activity, Overview report– MVSPM Data Set I/O Rate & Resp Time, Hourly Trend report– MVSPM Data Set I/O Rate Profile, Hourly Trend report– MVSPM Data Set Resp Time Profile, Hourly Trend report– MVSPM Storage Class Resp Time, Hourly Trend report– MVSPM Storage Class I/O Rate, Hourly Trend report– MVSPM Volume Activity by Storage Class, Overview report– MVSPM Channel Path Busy, Extended Mode report

v OpenEdition performance– MVSPM OpenEdition HFS Global Statistics report– MVSPM OpenEdition HFS Buffer Statistics report– MVSPM OpenEdition HFS Statistics report– MVSPM OpenEdition File Statistics report– MVSPM OpenEdition Kernel System Calls Activity report– MVSPM OpenEdition Kernel Process Activity report– MVSPM OpenEdition Kernel Memory Statistics report

MVS performance management reports


Daily performance overview reportsThe daily performance overview reports summarize your system’s performance.

MVSPM Workload Descriptions reportThis report shows the workloads that are defined for the selected MVS system, asdefined in the MVS_WORKLOAD_TYPE lookup table.


Report ID MVSPM01

Report group MVS performance management reports

Source MVS_WORKLOAD_TYPE

Attributes MVS, Performance, Overview, Workload

Variables MVS_system_ID


MVS system ID The MVS system ID selected in the reportingdialog.

Workload type The workload type defined for the selected MVSsystem ID.

Performance group no The performance group number assigned to theworkload type.

Performance period The performance group period number.

Description A brief description of the workload type as definedin the MVS_WORKLOAD_TYPE lookup table.

MVSPM Workload Descriptions

MVS Workload Performance Performancesystem ID type group no period Description--------- -------- ----------- ----------- --------------------------------SYS1 OTHER % % OTHERSYS1 SYSTEM 0 % MASTERSYS1 BTCH_L 1 % BATCH OTHER PERIODSSYS1 BATCH 1 0 BATCH (SMF 30 RECORDS)SYS1 BTCH_S 1 1 BATCH PERIOD 1SYS1 BTCH_M 1 2 BATCH PERIOD 2SYS1 TSO_L 2 % TSO LONGSYS1 TSO 2 0 TSO (SMF 30 RECORDS)SYS1 TSO_S 2 1 TSO SHORTSYS1 TSO_M 2 2 TSO MEDIUMSYS1 HOT_BTCH 3 % HOT BATCHSYS1 LOW_PRTY 4 % LOW PRIORITY BATCH

Tivoli Decision Support for OS/390 Report: MVSPM01

Figure 187. Example of an MVSPM Workload Descriptions report



MVSPM Goal mode Workload Descriptions reportThis report shows how the workloads are defined to Tivoli Decision Support forOS/390. This definition is only valid if the MVS system is running in goal mode.


Report ID MVSPM70


Source MVS_WORKLOAD2_TYPE

Attributes MVS, Performance, Overview, Workload, Goal mode

Variables MVS system ID



Workload type The Tivoli Decision Support for OS/390 workloadtype.

Workload group The WLM workload group.

Service class The WLM service class.

Service class period The WLM service class period.

Description A brief description of the workload.

MVSPM Goal mode Workload Descriptions

MVS Workload Workload Service Servicesystem ID type group class class period Description--------- -------- -------- -------- ------------ --------------------------------% BATCH BATCH % % BATCH ALL PERIODS% CICS CICS % % CICS% IMS IMS % % IMS% OTHER % % % OTHER% SYSTEM SYSTEM % % MASTER% TSO TSO % 0 TSO (SMF 30 RECORDS)% TSOC TSO % % TSO COMPLEX% TSOS TSO % 1 TSO SHORT


Figure 188. Example of an MVSPM Goal mode Workload Descriptions report



MVSPM CPU and Processor Storage Activity Overview reportThis report shows a summary overview of processor storage utilization by hour.For more information on using this report, refer to the System Performance FeatureGuide.


Report ID MVSPM02

Report group MVS Performance management reports

Source MVSPM_SYSTEM_HV, MVSPM_PAGING_HV,MVSPM_ENQUEUE_HV, MVSPM_STORAGE_HV

Attributes MVS, Performance, RMF, CPU, Overview, Processor_storage

Variables Date, MVS_system_ID, Period_name

MVSPM CPU and Processor Storage Activity OverviewSystem: ’MVS1’ Date:’1999-11-19’

Period: PERIOD_NAME

CPU 1 or more Average Average Average Avg page ES->CS Page Avg Avg Avg Logical AveragePeriod busy inready inready inwait outready delayed pages migrate TSO lready lwait swaps waitingname Time (%) wait (%) users users users users (/sec) (/sec) users users users (%) enqueue

------- ----- ---- --------- ------- ------- -------- -------- ------ ------- ----- ------ ----- ------- -------MORNING 00:00 20.4 0.3 0.8 65.7 0.0 0.0 0.7 0.0 9.6 0.6 43.8 0.0 0.0

01:00 4.6 0.2 0.1 65.0 0.0 0.0 0.0 0.0 9.0 0.3 44.6 0.0 0.002:00 4.3 0.1 0.1 65.0 0.0 0.0 0.0 0.0 9.0 0.3 44.6 0.0 0.003:00 8.0 0.2 0.3 65.9 0.0 0.0 0.1 0.0 9.0 0.3 43.7 0.0 0.004:00 9.9 0.2 0.4 66.4 0.0 0.0 1.0 0.0 9.0 0.4 44.8 0.0 0.005:00 6.3 0.2 0.2 65.7 0.0 0.0 1.8 0.0 9.4 0.5 46.0 0.0 0.006:00 8.1 0.3 0.3 66.1 0.0 0.0 1.4 0.0 10.0 1.0 45.7 0.0 0.007:00 8.6 0.3 0.3 66.5 0.0 0.0 6.0 0.0 15.7 0.6 47.7 0.0 0.0

PRIME 08:00 32.2 0.9 1.3 68.0 0.1 0.0 20.6 0.0 39.4 1.3 38.9 0.0 0.009:00 35.5 2.8 1.5 72.0 0.4 0.0 125.3 5.3 78.8 1.3 33.4 1.3 0.110:00 60.6 20.5 3.3 73.7 0.9 0.0 262.5 5.2 102.8 1.2 21.2 1.0 0.111:00 50.2 12.8 2.7 76.0 0.8 0.0 239.1 3.7 102.7 1.2 19.8 0.6 0.012:00 70.3 28.8 4.0 76.4 1.2 0.0 313.2 8.8 110.0 1.1 17.6 1.3 0.013:00 40.7 8.9 2.2 74.9 1.5 0.0 294.3 7.8 117.0 1.5 23.4 1.6 0.114:00 59.7 34.3 4.0 58.6 0.7 0.0 197.3 0.0 62.1 0.7 18.5 0.0 0.015:00 41.0 11.7 2.3 60.2 0.4 0.0 181.2 2.0 92.1 0.7 25.3 0.1 0.316:00 41.3 14.6 2.5 57.8 0.3 0.0 119.0 0.0 87.8 0.7 29.2 0.0 0.1

NIGHT 17:00 48.2 9.3 2.5 57.9 0.4 0.0 152.7 0.0 67.2 0.6 16.1 0.0 0.018:00 27.6 1.1 1.2 56.7 0.0 0.0 22.6 0.0 50.3 0.7 32.5 0.0 0.019:00 33.3 1.5 1.4 56.2 0.1 0.0 38.1 0.0 42.3 0.7 32.3 0.0 0.020:00 24.8 0.7 1.1 57.2 0.0 0.0 23.7 0.0 35.3 0.8 36.6 0.0 0.021:00 20.1 0.4 0.8 55.4 0.1 0.0 20.7 0.1 26.3 0.6 38.9 0.3 0.022:00 13.7 0.2 0.5 53.2 0.0 0.0 2.1 0.0 18.2 0.5 46.1 0.0 0.023:00 11.4 0.1 0.4 52.2 0.0 0.0 0.6 0.0 11.1 0.3 39.2 0.0 0.0

Tivoli Decision Support for OS/390 Report:MVSPM02

Figure 189. Example of an MVSPM CPU and Processor Storage Activity Overview report






CPU busy percent The CPU busy time, in percent.

1 or more inready wait (%) The percentage of time that the number of in-readyusers was higher than the number of processors.Calculated as: 100 * AS2_WAIT_SAMPLES /SAMPLES.

Average inready users The average number of in-ready users. Calculatedas: INREADY_USERS_TOT / SAMPLES.

Average inwait users The average number of in-wait users. Calculatedas: (INSTOR_USERS_TOT −INREADY_USERS_TOT) / SAMPLES.

Average outready users The average number of in-ready users. Calculatedas: INREADY_USERS_TOT / SAMPLES.

Avg page delayed users The users waiting on page faults. Calculated as:PAGEDEL_USERS_TOT / (TIME_RESOLUTION *60000) / CYCLE_LENGTH_MSEC.

ES->CS pages (/sec) The number of pages moved from expandedstorage to central storage per second. Calculatedas: PAGES_READ_ES / MEASURED_SEC.

Page migrate (/sec) The number of pages moved from expandedstorage to auxiliary storage per second. Calculatedas: PAGES_MIGRATED_TOT / MEASURED_SEC.

Avg TSO users The average number of TSO/E users. Calculatedas: TSO_USERS_TOT / SAMPLES.

Avg lready users The average number of logically swapped out butready users. Calculated as: LREADY_USERS_TOT/ SAMPLES.

Avg lwait users The average number of logically swapped out andwaiting users. Calculated as: LWAIT_USERS_TOT/ SAMPLES.

Logical swaps (%) The number of logical swaps performed, as apercentage of the total number of swaps.Calculated as: LOGICAL_SWAPS /(LOGICAL_SWAPS + SWAP_SEQUENCES) * 100.

Average waiting enqueue The average number of applications waiting onenqueue. Calculated as: (WAITING_REQUESTS /CONTENTION_EVENTS) *CONTENTION_TOT_SEC / (TIME_RESOLUTION* 60).



MVSPM Workload Resource Utilization Overview reportThis report shows the resource utilization for each workload. The rows markedwith an asterisk (*) are the totals for all workloads for the period. This reportworks for goal mode and compatibility mode. Refer to the glossary for definitionsof these terms.



Report ID MVSPM03


Source MVSPM_WORKLOAD_HV, MVSPM_SYSTEM_H,MVSPM_WORKLOAD2_HV

Attributes MVS, Performance, RMF, CPU, Overview, Workload




Workload type The MVS workload type name.

CPU usage (%) The total processor busy time, in percent.

MVSPM Workload Resource Utilization OverviewSystem: ’MVS1’ Date: ’1999-11-19’

Period: PERIOD_NAME

CPU System Page- Cent Exp I/O In OutPeriod Workload usage usage ins stor stor rate stor readyname type (%) (%) (/sec) (MB) (MB) (/sec) users users

-------- -------- ----- ------ ------ ----- ----- ------ ----- -----MORNING BATCH 6.9 1.7 0.0 17.8 0.0 13.33 1.4 0.0

CICS 0.9 0.2 0.0 29.4 2.3 6.84 15.8 0.4STC 10.9 2.7 0.0 279.7 28.3 88.78 43.8 0.1SYSTEM 1.2 0.3 0.0 7.4 1.5 0.05 5.0 0.0TSOC 1.6 0.4 0.0 0.3 0.0 2.42 0.1 0.0TSOS 0.1 0.0 0.0 0.0 0.0 0.12 0.0 0.0

----- ------ ------ ----- ----- ------ ----- -----* 21.5 5.4 0.0 334.7 31.8 111.53 66.1 0.5

NIGHT BATCH 57.2 14.3 0.0 29.0 0.0 179.81 3.4 0.0CICS 0.6 0.2 0.0 17.9 2.3 4.88 5.4 0.5STC 6.8 1.7 0.0 249.5 34.9 9.58 41.8 0.1SYSTEM 2.5 0.6 0.0 7.3 2.1 0.06 5.0 0.0TSOC 14.8 3.7 0.0 3.0 0.0 31.80 0.9 0.0TSOS 1.4 0.4 0.0 0.3 0.0 2.58 0.1 0.0

----- ------ ------ ----- ----- ------ ----- -----* 83.2 20.8 0.0 307.1 39.4 228.72 56.6 0.7

PRIME BATCH 64.5 16.1 0.0 29.1 0.0 183.54 4.5 0.1CICS 2.7 0.7 0.2 24.8 2.3 21.58 13.8 1.1STC 18.7 4.7 1.2 213.8 50.7 47.94 42.0 0.4SYSTEM 4.2 1.1 0.0 6.8 2.1 0.14 4.8 0.0TSOC 58.6 14.6 0.2 8.6 0.0 57.58 2.1 0.1TSOS 3.9 1.0 0.1 0.7 0.0 7.04 0.3 0.0

----- ------ ------ ----- ----- ------ ----- -----* 152.6 38.2 1.8 283.7 54.1 317.82 67.6 1.7


Figure 190. Example of an MVSPM Workload Resource Utilization Overview report



Calculated as: 100 * ((TCB_TIME_FACTOR /SERVICE_UNITS_MAX) + (SRB_TIME_FACTOR /SERVICE_UNITS_MAX) + IOINTR_SEC +RCT_SEC + HIPER_SERVICE_SEC) /(TIME_RESOLUTION * 60).

System usage (%) The total processor busy time, in percent, dividedby the number of online processors. Calculated as:(100 *((TCB_TIME_FACTOR/SERVICE_UNITS_MAX) +(SRB_TIME_FACTOR/SERVICE_UNITS_MAX) +IOINTR_SEC + RCT_SEC + HIPER_SERVICE_SEC)/ (TIME_RESOLUTION * 60)) / CPU_ONLINE.

Page-ins (/sec) The number of private area page-ins per second.Calculated as: PAGEINS / (TIME_RESOLUTION *60).

Cent stor (MB) The total central storage used, in megabytes.Calculated as: (TOT_FRAME_SEC −ES_FRAME_SEC) / (TIME_RESOLUTION * 60) /256.

Note: For releases of MVS/ESA SP before Version4, this value is the total processor (centraland expanded) storage.

Exp stor (MB) The total expanded storage used, in megabytes.Calculated as: ES_FRAME_SEC /(TIME_RESOLUTION * 60) / 256.

I/O rate (/sec) The number of input/output operations servicedper second. This is based on I/O service units.Calculated as: IO_RATE_FACTOR /(TIME_RESOLUTION * 60).

In stor users The average number of users in storage. Calculatedas: TRAN_RESIDENT_SEC / (TIME_RESOLUTION* 60).

Outready users The average number of users that were swappedout but were ready. Calculated as:(TRAN_ACTIVE_SEC − TRAN_RESIDENT_SEC) /(TIME_RESOLUTION * 60).



MVSPM Workload Response Time Components Overviewreport

This report shows response time components for workloads that have more than0.5 transactions per minute. This report works for goal mode and compatibilitymode. Refer to the glossary for definitions of these terms.



Report ID MVSPM04


Source MVSPM_WORKLOAD_HV, MVSPM_PAGE_DS_HV,MVSPM_WORKLOAD2_HV

Attributes MVS, Performance, RMF, CPU, Overview, Workload,Response_time





Transactions (/min) The average number of transactions per minute.Calculated as: TRANSACTIONS /TIME_RESOLUTION.

Max response (sec) The maximum response time, in seconds.

Average response (sec) The average transaction response time, in seconds.Calculated as: TRAN_ELAPSED_SEC /TRANSACTIONS.

MVSPM Workload Response Time Components OverviewSystem: ’MVS1’ Date: ’1999-11-19’

Period: PERIOD_NAME

Trans- Max Average CPU Out PagingPeriod Workload actions response response time ready timename type (/min) (sec) (sec) (sec) (sec) (sec)

-------- -------- ------- --------- -------- ----- ----- ------MORNING BATCH 0.8 114.9 47.1 6.0 0.4 0.00

TSOC 3.4 22.6 2.3 0.3 0.0 0.00TSOS 3.6 0.1 0.0 0.0 0.0 0.00

NIGHT BATCH 0.8 630.4 238.6 59.0 0.5 0.00TSOC 24.8 111.9 2.3 0.3 0.0 0.00TSOS 55.1 0.6 0.0 0.0 0.0 0.00

PRIME BATCH 1.4 465.8 131.4 31.6 2.3 0.04TSOC 59.9 363.0 2.7 0.6 0.1 0.00TSOS 148.5 0.7 0.1 0.0 0.0 0.00


Figure 191. Example of an MVSPM Workload Response Time Components Overview report



CPU time (sec) From column CPU_PER_TRAN in viewMVSPM_WORKLOAD_HV.

The total CPU time per transaction, in seconds.Calculated as: ((TCB_TIME_FACTOR /SERVICE_UNITS_MAX) + (SRB_TIME_FACTOR /SERVICE_UNITS_MAX) + IOINTR_SEC +RCT_SEC + HIPER_SERVICE_SEC) /TRANSACTIONS.

Out ready (sec) The average out and ready time per transaction, inseconds. Calculated as: ((TRAN_ACTIVE_SEC /(TIME_RESOLUTION * 60)) −(TRAN_RESIDENT_SEC / (TIME_RESOLUTION *60)) * (TRAN_ELAPSED_SEC / TRANSACTIONS)/ (TRAN_ACTIVE_SEC / (TIME_RESOLUTION *60)).

Paging time (sec) The average time spent paging, in seconds.Calculated as: RESPONSE_LOCAL_SEC *DEM_PAGES_PER_TRAN.



MVSPM Response Time Goals vs Actuals, Overview reportThis report shows the average response time and corresponding goal for all serviceclasses that have a goal assigned. The report can show a summary for the wholesysplex or for a selected MVS system. This report is available only when the MVSsystem is running in goal mode.


Report ID MVSPM72


Source MVSPM_WORKLOAD2_H

Attributes MVS, Performance, RMF, Overview, Workload, Response_time,Goal mode, Sysplex

Variables Date, Sysplex name, MVS system ID, Period name


Goal imp Goal importance.

Service class Service class name.

SC per Service class period.

Goal misses Number of RMF intervals that the goal was notmet.

Avg resp time(s) Average response time. Calculated as:TRAN_ELAPSED_SEC/TRANSACTIONS.

Tx’s within goal(%) Percent of transactions that had a response timeless than or equal to the goal. Calculated as:100*TRANSACTIONS_BELOW/TRANSACTIONS.

No of tx’s Total number of transactions.

Goal The average response time goal or percent oftransactions that should end within a certainresponse time.

MVSPM Response Time Goals vs Actuals, OverviewSysplex: ’SYSPLEX1’ System: MVS1Date: ’2000-02-01’ Period: ’PRIME’

Avg Tx’sGoal Service SC Goal resp within No ofimp class per misses time(s) goal(%) tx’s Goal---- -------- --- ------ ------- ------- ------- -----------------------------

1 VIP_USER 1 1 1.0 91.0 1209 Avg resp time < 0001.20 sec.

2 CICS-1 1 8 3.5 62.0 1664 060% within 0001.00 sec.CICS-2 1 8 9.3 15.0 1215 065% within 0002.00 sec.CICS-5 1 8 18.5 12.0 1501 Avg resp time < 0001.00 sec.CICS-6 1 9 19.4 6.0 1396 Avg resp time < 0002.00 sec.CICSTRX 1 9 2.7 69.0 9314 Avg resp time < 0003.00 sec.BATCH-1 1 1 677.1 40.0 15 090% within 0600.00 sec.

3 TRANS_1 5 5 14.0 5.0 19 Avg resp time < 0010.00 sec.


Figure 192. Example of an MVSPM Response Time Goals vs Actuals Overview report



MVSPM Execution Velocity Goals & Actuals, Overview reportThis report shows the average execution velocity and corresponding goal for allservice classes that have a goal assigned. The report can show a summary for thewhole sysplex or for a selected MVS system. This report is available only when theMVS system is running in goal mode.


Report ID MVSPM75



Attributes MVS, Performance, RMF, Overview, Goal mode, Execution,Velocity, Service_class, Sysplex

Variables Date, Sysplex name, MVS system ID, Period name



Goal imp Goal importance.

Service class Service class name.

SC per Service class period.

Goal misses Number of RMF intervals that the goal was notmet.

Velocity actual(%) This is the actual execution velocity. Calculated as:100*CPU_USE_CNT/(CPU_USE_CNT +TOTAL_DELAY_CNT).

Velocity goal(%) The execution velocity goal. FromEXEC_VEL_GOAL_PCT.

No of tx’s Number of transactions ended during the period.

MVSPM Execution Velocity Goals & Actuals, OverviewSysplex: ’SYSPLEX1’ System: MVS_SYSTEM_ID

Date: ’2000-02-01’ Period: ’PRIME’

Goal Service SC Goal Velocity Velocity No ofimp class per misses actual(%) goal(%) tx’s---- -------- ---- ------ --------- -------- --------

1 MVSSUBSY 1 1 91.6 91.0 1002 BATCH 1 3 35.0 30.0 2230

CICSREGS 1 4 82.5 80.0 2001IMSREGS 1 7 79.7 80.0 451MONITORS 1 3 48.7 50.0 313ST_TOOLS 1 2 55.8 57.0 733

3 APPC 1 1 80.0 75.0 91ASCH 1 5 60.0 55.0 13

4 VEL3 1 9 10.0 3.0 512


Figure 193. Example of an MVSPM Execution Velocity Goals & Actuals Overview report



MVSPM DASD Activity Overview reportThis report shows the daily DASD activity of the most used DASD devices. Youneed a report for each period of the day. You can select this report for each MVSsystem, or for a whole sysplex. Use the Maxrows variable to limit the number ofelements shown in the chart. For more information on using this report, refer tothe System Performance Feature Guide.


Report ID MVSPM05

Report group MVS performance manage ent reports

Source MVSPM_DEVICE_HV

Attributes MVS, Performance, RMF, Response time, Daily, Overview, DASD,Sysplex

Variables Date, MVS_system_ID, Period_name, Maxrows, Sysplex_name


Unit type The unit type.

LCU number The logical control unit number.

Device number The device number of the logical control unit.

Volser The volume serial ID of the volume mounted onthe device.

DASD mpl The average number of users waiting for thedevice. The multiprogramming level (MPL)indicates the maximum number of users who areactive at any one time.

I/O-rate (/sec) The number of requests serviced per second.

Response (msec) The average response time per request, inmilliseconds.

Queue wait (msec) The average queue wait time, in milliseconds. Thisis the average time spent in the queue waiting forthe UCB.

MVSPM DASD Activity, OverviewSysplex: ’SYSPLEX1’ Date: ’2000-04-13’

Period: ’NIGHT ’

Unit LCU Dev MVS DASD I/O-rate Response Que wait Connect Disconn Pending Alloca- Busytype num num Volser ID mpl (/sec) (msec) (msec) (msec) (msec) (msec) tions (%)------- ---- ---- ------ ---- ----- -------- -------- -------- ------- ------- ------- ------- -----9345-2 3B EEC1 DBDC05 MVS3 0.16 3.74 42.4 3.0 2.5 1.9 34.9 0 14.09345-2 35 EEC1 DBDC05 MVS1 0.14 3.08 46.6 0.5 2.5 2.6 41.0 0 13.433902 2F CC9C XA0CAT MVS1 0.10 9.00 11.0 0.3 2.7 0.4 7.6 3 9.39345-2 3B EEC1 DBDC05 MVS2 0.10 1.94 50.9 6.1 2.6 3.8 38.5 0 8.033902 33 CC9A X80CAT MVS3 0.09 21.83 4.3 0.7 1.3 0.4 1.9 7 7.033902 33 CC9B X90CAT MVS2 0.09 5.74 16.3 0.4 3.7 0.4 11.8 3 8.933903 11 660F TSOL05 MVS2 0.07 0.94 73.7 1.3 5.9 66.5 0.1 20 0.69345-2 3B EED1 XYZED1 MVS2 0.06 1.39 40.0 3.8 10.4 0.3 25.4 3 5.09345-2 35 EED1 XYZED1 MVS1 0.05 1.06 46.5 4.6 11.5 0.3 30.0 3 4.433903 11 660F TSOL05 MVS3 0.05 1.83 25.4 1.1 4.8 19.4 0.1 19 0.9


Figure 194. Example of an MVSPM DASD Activity Overview report



Connect (msec) The average connect time per request, inmilliseconds.

Disconn (msec) The average disconnect time per request, inmilliseconds.

Pending (msec) The average pending time per request, inmilliseconds. This is the average time that arequest waited for the device or control unit.

Allocations The average number of data sets open for thedevice.

Busy (%) The percentage of time the device is busy.



Processor and storage resources reportsThese reports show hourly and daily processor utilization information, storageallocations, and response times for page or swap data sets.

MVSPM Average CPU Busy, Daily/Hourly Trend reportThese reports show the daily or hourly trend of the processor usage for one ormore MVS systems. If the processor complex has more than one processor, this isthe average processor usage. If you are using PR/SM to run more than one systemin the same complex, you should also look at the reports showing the processorusage per LPAR (logical partition). You can select these reports for each MVSsystem, or for a whole sysplex. For more information on using these reports, referto the System Performance Feature Guide.


Report ID MVSPM06 (daily), MVSPM07 (hourly)


Source MVSPM_SYSTEM_HV

Attributes MVS, Performance, RMF, CPU, Daily, Hourly, Overview, Sysplex

Variables From_date, To_date, Date, MVS_system_ID, Period_name,Sysplex_name

Perc

ent

0

10

20

30

40

50

60

70

80

Time of day07:

0008:

0009:

0010:

0011:

0012:

0013:

0014:

0015:

0016:

0017:

0018:

00

MVS1MVS2MVS3

Figure 195. Example of an MVSPM Average CPU Busy, Hourly Trend report





MVS system IDThe MVS system ID.

CPU busy percentThe processor busy time, in percent. Calculated as:(CPU_BUSY_SEC * 100) / CPU_ONLINE_SEC.



MVSPM Average CPU Busy Profile, Hourly Trend reportThis report shows the processor usage over a several days, by hour. Here you cansee when the peak hours occurred and choose an average day to analyze in moredetail.


Report ID MVSPM08



Attributes MVS, Performance, RMF, CPU, Hourly, Overview, Profile




Time of day The time of the measurement.

CPU busy percent The CPU busy time, in percent. Calculated as:(CPU_BUSY_SEC * 100) / CPU_ONLINE_SEC.

Perc

ent

0

10

20

30

40

50

60

70

80

Time of day00:

0001:

0002:

0003:

0004:

0005:

0006:

0007:

0008:

0009:

0010:

0011:

0012:

0013:

0014:

0015:

0016:

0017:

0018:

0019:

0020:

0021:

0022:

0023:

00

1999-08-041999-08-051999-08-061999-08-071999-08-101999-08-121999-08-13

Figure 196. Example of an MVSPM Average CPU Busy Profile, Hourly Trend report



MVSPM CPU Busy and Other Indicators, Hourly Trend reportThis report shows both CPU and processor storage contention indicators. The linefor “1 or more wait” represents the percentage of time that all processors weredispatched, but there were still one or more address spaces waiting to bedispatched. The “2 or more wait” line is the same, except that two or more addressspaces were waiting. For more information on using this report, refer to the SystemPerformance Feature Guide.


Report ID MVSPM09



Attributes MVS, Performance, RMF, CPU, Hourly, Overview, Paging




Pageins (/sec) The total non-VIO page rate.

Pages migrated (/sec) The number of pages migrated, per second, fromexpanded storage to auxiliary storage.

Outready users The average number of out-ready users. Calculatedas: OUTREADY_USERS_TOT / SAMPLES.

Percent/Number/Rate

0

5

10

15

20

25

30

35

40

Time of day00:

0001:

0002:

0003:

0004:

0005:

0006:

0007:

0008:

0009:

0010:

0011:

0012:

0013:

0014:

0015:

0016:

0017:

0018:

0019:

0020:

0021:

0022:

0023:

00

Page-ins(/sec)

Pagesmigrated(/sec)

Outreadyusers

2 or morewait (%)

1 or morewait (%)

CPUbusy (%)

Figure 197. Example of an MVSPM CPU Busy and Other Indicators, Hourly Trend report



2 or more wait (%) The percentage of time that the number of userswas 2 or more higher than the number ofprocessors.

1 or more wait (%) The percentage of time that the number of userswas higher than the number of processors.

CPU busy percent The CPU busy time, in percent. Calculated as:(CPU_BUSY_SEC * 100) / CPU_ONLINE_SEC.



MVSPM System Central Storage Map, Hourly Trend reportThis report shows the central storage allocations per hour. For more information onusing this report, refer to the System Performance Feature Guide.


Report ID MVSPM10


Source MVSPM_PAGING_HV

Attributes MVS, Performance, RMF, CPU, Hourly, Overview, Central_storage




Nucleus The average number of nucleus pages in central storage, inmegabytes.

Private The average number of private pages in central storage, inmegabytes.

LSQA The average number of LSQA pages in central storage, inmegabytes.

CSA The average number of CSA pages in central storage, inmegabytes.

LPA The average number of LPA pages in central storage, in megabytes.

SQA The average number of SQA pages in central storage, inmegabytes.

Mega

byte

s

0

20

40

60

80

100

Time of day00.

00.00

01.00.

00

02.00.

00

03.00.

00

04.00.

00

05.00.

00

06.00.

00

07.00.

00

08.00.

00

09.00.

00

10.00.

00

11.00.

00

12.00.

00

13.00.

00

14.00.

00

15.00.

00

16.00.

00

17.00.

00

18.00.

00

19.00.

00

20.00.

00

21.00.

00

22.00.

00

23.00.

00

NucleusPrivateLSQACSALPASQAAvail

Figure 198. Example of an MVSPM System Central Storage Map, Hourly Trend report



Avail The average number of available pages in central storage, inmegabytes.



MVSPM System Expanded Storage Map, Hourly Trend reportThis report shows the expanded storage allocations per hour. For more informationon using this report, refer to the System Performance Feature Guide.


Report ID MVSPM11



Attributes MVS, Performance, RMF, CPU, Hourly, Expanded_storage




Private The average number of private pages in expanded storage, inmegabytes.

LSQA The average number of LSQA pages in expanded storage, inmegabytes.

CSA The average number of CSA pages in expanded storage, inmegabytes.

LPA The average number of LPA pages in expanded storage, inmegabytes.

SQA The average number of SQA pages in expanded storage, inmegabytes.

Megabytes

0

100

200

300

400

500

Time of day00:

0001:

0002:

0003:

0004:

0005:

0006:

0007:

0008:

0009:

0010:

0011:

0012:

0013:

0014:

0015:

0016:

0017:

0018:

0019:

0020:

0021:

0022:

0023:

00

PrivateLSQACSALPASQAAvail

Figure 199. Example of an MVSPM System Expanded Storage Map, Hourly Trend report



Avail The average number of available pages in expanded storage, inmegabytes.



MVSPM Minimum Available Exp Storage, Hourly Trend reportThis report shows the minimum available expanded storage per hour overmultiple days. It can be used to identify when jobs that require large amounts ofexpanded storage should be scheduled (for example, hipersorts).


Report ID MVSPM12



Attributes MVS, Performance, RMF, CPU, Hourly, Overview,Expanded_storage

Variables To_date, From_date MVS_system_ID, Period_name


From date/To date The dates of the measurement.


Minimum available expanded storage (MB)The minimum amount of available expandedstorage, in megabytes.

Mega

byte

s

0

50

100

150

200

250

300

350

400

Time of day00:

0001:

0002:

0003:

0004:

0005:

0006:

0007:

0008:

0009:

0010:

0011:

0012:

0013:

0014:

0015:

0016:

0017:

0018:

0019:

0020:

0021:

0022:

0023:

00

1999-08-041999-08-051999-08-061999-08-071999-08-121999-08-131999-08-14

Figure 200. Example of an MVSPM Minimum Available Exp Storage, Hourly Trend report



MVSPM Average High UIC Profile, Hourly Trend reportThis report shows the unreferenced interval count (UIC) for a number of days. TheUIC is one indicator that can be used to determine the level of storage contention.A low UIC indicates that the user’s working set has been trimmed down by pagestealing. For more information on using this report, refer to the System PerformanceFeature Guide.


Report ID MVSPM14



Attributes MVS, Performance, RMF, CPU, Hourly, Overview, UIC



From date/To date The dates of the measurement.


Average high UIC The average high UIC, in seconds.

Seconds

0

50

100

150

200

250

300

Time of day00:

0001:

0002:

0003:

0004:

0005:

0006:

0007:

0008:

0009:

0010:

0011:

0012:

0013:

0014:

0015:

0016:

0017:

0018:

0019:

0020:

0021:

0022:

0023:

00

1999-08-121999-08-131999-08-14

Figure 201. Example of an MVSPM Average High UIC Profile, Hourly Trend report



MVSPM Page Data Set Response Time, Hourly Trend reportThis report shows the average response times for page or swap data set types. Formore information on using this report, refer to the System Performance Feature Guide.


Report ID MVSPM15


Source MVSPM_PAGE_DS_HV

Attributes MVS, Performance, RMF, CPU, Paging, Response, Hourly

Variables Date, MVS_system_ID, Period_name, Page_space_type



Page data set The type of page data set (for example, PLPA,LOCAL, or COMMON).

I/O response time The I/O response time, in milliseconds. Calculatedas: 1000 * (DATASET_BUSY_SEC) /IO_REQUESTS.

Milliseconds

0

10

20

30

40

50

60

Time of day00:

0001:

0002:

0003:

0004:

0005:

0006:

0007:

0008:

0009:

0010:

0011:

0012:

0013:

0014:

0015:

0016:

0017:

0018:

0019:

0020:

0021:

0022:

0023:

00

COMMONLOCALPLPA

Figure 202. Example of an MVSPM Page Data Set Response Time, Hourly Trend report



MVSPM Page Data Set Device Resp Time, Hourly Trend reportThis report shows the average response times for each page or swap data set.


Report ID MVSPM16



Attributes MVS, Performance, RMF, CPU, Paging, Response, Device, Hourly




Page data set type and device numberThe type of page data set (for example, PLPA,COMMON, LOCAL, or SWAP) and the associateddevice number.

I/O response time The I/O response time, in milliseconds. Calculatedas: 1000 * (DATASET_BUSY_SEC) /IO_REQUESTS.

Milliseconds

0

20

40

60

80

100

Time of day00:

0001:

0002:

0003:

0004:

0005:

0006:

0007:

0008:

0009:

0010:

0011:

0012:

0013:

0014:

0015:

0016:

0017:

0018:

0019:

0020:

0021:

0022:

0023:

00

LOCAL 020BLOCAL 0200LOCAL 0202LOCAL 0204

Figure 203. Example of an MVSPM Page Data Set Device Resp Time, Hourly Trend report



MVSPM Page Data Set Busy Time, Hourly Trend reportThis report shows the percent busy for selected page data sets. High usage for apage data set may result in bad response times.


Report ID MVSPM17



Attributes MVS, Performance, RMF, CPU, Paging, Busy, Hourly




Page data set type and device numberThe type of page data set (for example, PLPA,COMMON, LOCAL, or SWAP) and the devicenumber for the page data set.

Data set busy percent The average percentage of time that the page dataset was busy. Calculated as: 100 *DATASET_USED_SEC / MEASURED_SEC.

Percent

0

1

2

3

4

5

6

7

8

Time of day00:

0001:

0002:

0003:

0004:

0005:

0006:

0007:

0008:

0009:

0010:

0011:

0012:

0013:

0014:

0015:

0016:

0017:

0018:

0019:

0020:

0021:

0022:

0023:

00

COMMON 0206LOCAL 020BLOCAL 0200LOCAL 0202LOCAL 0204PLPA 0206

Figure 204. Example of an MVSPM Page Data Set Busy Time, Hourly Trend report



MVSPM System Storage Paging Rates, Hourly Trend reportThis report shows how effectively expanded storage is used on a system. Thepage-in rate from auxiliary storage is also shown for comparison.


Report ID MVSPM18



Attributes MVS, Performance, RMF, CPU, Paging, Hourly




Page-ins (/sec) The total non-VIO page rate.

Pages migrated (/sec) The number of pages moved from expanded toauxiliary storage per second.

Moved CS->ES (/sec) The number of pages moved from central storageto expanded storage per second. Calculated as:PAGES_MOVED_ES / MEASURED_SEC.

Moved ES->CS (/sec) The number of pages moved from expandedstorage to central storage per second. Calculatedas: PAGES_READ_ES / MEASURED_SEC.

Pages per Second

0

50

100

150

200

250

300

350

Time of day00:

0001:

0002:

0003:

0004:

0005:

0006:

0007:

0008:

0009:

0010:

0011:

0012:

0013:

0014:

0015:

0016:

0017:

0018:

0019:

0020:

0021:

0022:

0023:

00

Page-ins(/sec)

Pagesmigrated(/sec)

MovedCS->ES(/sec)

MovedES->CS(/sec)

Figure 205. Example of an MVSPM System Storage Paging Rates, Hourly Trend report



MVSPM CPU Busy Profile Shared LPARs, Hourly Trend reportThis report shows the CPU busy profile for all shared logical partitions as apercentage of the total capacity for all shared processors (partitions assigneddedicated processors are not included). For more information on using this report,refer to the System Performance Feature Guide.


Report ID MVSPM20


Source MVSPM_LPAR_HV

Attributes MVS, Performance, RMF, CPU, LPAR, Hourly

Variables From_date, To_date, MVS_system_ID, Period_name, Processor_type




Complex usage percent The total processor complex usage for all sharedpartitions, in seconds. Calculated as: 100 *(CPU_DISPATCH_SEC − CPU_WAIT_SEC) /(MEASURED_SEC * PHYS_PROCESSORS).

Percent

0

10

20

30

40

50

60

70

Time of day00:

0001:

0002:

0003:

0004:

0005:

0006:

0007:

0008:

0009:

0010:

0011:

0012:

0013:

0014:

0015:

0016:

0017:

0018:

0019:

0020:

0021:

0022:

0023:

00

2000-06-042000-06-052000-06-062000-06-072000-06-102000-06-12

Type: ALL

Figure 206. Example of an MVSPM CPU Busy Profile Shared LPARs, Hourly Trend report



MVSPM CPU Busy by Shared LPARs, Hourly Trend reportThis report shows the CPU busy for all shared logical partitions including thephysical LPAR management time. For more information on using this report, referto the System Performance Feature Guide.


Report ID MVSPM21




Variables Date, MVS_system_ID, Period_name, Processor_type



MVS system ID The MVS system ID. This is the SMF system ID.

LPAR name The name of the shared logical partition.

Complex usage percent The total processor complex usage for the partition,in seconds. Calculated as: 100 *(CPU_DISPATCH_SEC − CPU_WAIT_SEC) /(MEASURED_SEC * PHYS_PROCESSORS).

Percent

0

10

20

30

40

50

60

70

80

90

Time of day00:

0001:

0002:

0003:

0004:

0005:

0006:

0007:

0008:

0009:

0010:

0011:

0012:

0013:

0014:

0015:

0016:

0017:

0018:

0019:

0020:

00

*PHYSCALMVS1MVS4VM0VM1MVS9SYS1SYS2

Processor type: All

Figure 207. Example of an MVSPM CPU Busy by Shared LPARs, Hourly Trend report



MVSPM Percent of Share Used by LPARs, Hourly Trend reportThis report shows how much of the allowed share each logical partition is usingbased on the LPAR weight factors. For more information on using this report, referto the System Performance Feature Guide.


Report ID MVSPM22




Variables Date, MVS_System_ID, LPAR_name, Period_name, Processor_type




LPAR dispatch percent The time that the logical partition was dispatched,as a percentage of the allowed time. Calculated as:100 * CPU_DISPATCH_SEC / ((MEASURED_SEC *DEDICATED_PROC_IND) + MEASURED_SEC *NONDED_PROCESSORS * (LPAR_WEIGHT /LPAR_WEIGHT_TOT) * (1 −DEDICATED_PROC_IND)).

Perc

ent

0

50

100

150

200

250

300

350

Time of day00:

0001:

0002:

0003:

0004:

0005:

0006:

0007:

0008:

0009:

0010:

0011:

0012:

0013:

0014:

0015:

0016:

0017:

0018:

0019:

0020:

0021:

0022:

0023:

00

MVS1MVS4VM0VM1MVS9SYS1SYS2

Processor type: All

Figure 208. Example of an MVSPM Percent of Share Used by LPARs, Hourly Trend report



MVSPM LPAR Management Time, Hourly Trend reportThis report shows the percent LPAR management time for each logical partitionand the percentage of time needed for the management of the physicalconfiguration. The total utilization of the whole LPAR system is also shown as aline graph on the chart. The total utilization is divided by 10 in order to use thesame scale on the x-axis.


Report ID MVSPM23




Variables Date, MVS_system_ID, Period_name, Processor_type




LPAR management percent The logical partition management time, in percent.This is the percentage of physical LPARmanagement time if the partition name is*PHYSCAL. Calculated as: 100 *(CPU_DISPATCH_SEC − CPU_EFF_DISP_SEC) /(MEASURED_SEC * NONDED_PROCESSORS).

Percent

0

2

4

6

8

Time of day00:

0001:

0002:

0003:

0004:

0005:

0006:

0007:

0008:

0009:

0010:

0011:

0012:

0013:

0014:

0015:

0016:

0017:

0018:

0019:

0020:

00

.CPU%/10*PHYSCALMVS1MVS4VM0VM1MVS9SYS1SYS2

Processor type: All

Figure 209. Example of an MVSPM LPAR Management Time, Hourly Trend report



MVSPM Avg CF Busy Profile, Hourly Trend reportThis report shows the coupling facility utilization over several days.


Report ID MVSPM68


Source MVSPM_CF_PROC_H

Attributes MVS, Performance, RMF, CF, Hourly, Trend, Profile, Sysplex

Variables From date, To date, Sysplex name, CF name, Period name




Percent busy The average coupling facility utilization in percent.Calculated as:100*CPU_BUSY_SEC/MEASURED_SEC.

Percent

0

1

2

3

4

5

6

Time of day17:

0018:

0019:

0020:

0021:

0022:

0023:

00

2000-02-012000-02-022000-02-03

Figure 210. Example of an MVSPM Avg CF Busy Profile, Hourly Trend report



MVSPM Avg CF Storage Usage, Hourly Trend reportThis report shows the hourly trend of the coupling facility storage usage.


Report ID MVSPM69


Source MVSPM_CF_PROC_H

Attributes Mvs, Performance, Rmf, CF, Hourly, Overview, Profile, Sysplex,Storage

Variables Date, Sysplex name, CF name, Period name




Used dump stor (MB) Used dump storage. Calculated as:ALLOC_DUMP_STOR_MB -FREE_DUMP_STOR_MB.

Used CF stor (MB) Total used coupling facility storage. Calculated as:CF_STOR_DEF_MB - CF_STOR_FREE_MB +ALLOC_DUMP_STOR_MB.

Free dump stor (MB) Free dump storage. From FREE_DUMP_STOR_MB.

Free CF stor (MB) Free storage. From: CF_STOR_FREE_MB.

Mega

byte

s

0

20

40

60

80

100

120

140

160

Time of day17:

0018:

0019:

0020:

0021:

0022:

0023:

00

153 153 153 153 153 153 153

Used dumpstor (MB)

Used CFstor (MB)

Free dumpstor (MB)

Free CFstor (MB)

Figure 211. Example of an MVSPM Avg CF Storage Usage, Hourly Trend report



MVSPM CF, Processor and Storage, Overview reportThis report shows an overview of the connected coupling facilities with theiroverall processors and storage utilization.


Report ID MVSPM86


Source MVSPM_CF_PROC_HV

Attributes MVS, Performance, CF, COUPLING_FACILITY

Variables FROM_DATE, TO_DATE, SYSPLEX




CF name The name of the coupling facility.

CF model The model of the coupling facility.

CF version The version of the coupling facility.

CF level The level of the coupling facility.

MVSPM CF, Processor and Storage, OverviewSYSPLEX NAME: ’SYSPLEX1’

DATE: ’2000-07-13’ TO ’2000-07-13’

STORAGE STORAGECF CF CF CF PROC PROC PROC SIZE AVAIL

DATE TIME NAME MODEL VERS LEV UTIL DEFINED EFFECT MB MB---------- -------- ---- ----- ---- ---- ----- ------- ------ ------- -------2000-07-13 00.00.00 CF01 9672 E03 4 4.4 6 0.9 489.0 309.72000-07-13 00.00.00 CF02 9672 E03 4 5.2 6 0.9 489.0 124.22000-07-13 01.00.00 CF01 9672 E03 4 4.4 6 0.9 489.0 309.72000-07-13 01.00.00 CF02 9672 E03 4 5.2 6 0.9 489.0 124.22000-07-13 02.00.00 CF01 9672 E03 4 4.4 6 0.9 489.0 309.72000-07-13 02.00.00 CF02 9672 E03 4 5.2 6 0.9 489.0 124.22000-07-13 03.00.00 CF01 9672 E03 4 4.4 6 0.9 489.0 309.72000-07-13 03.00.00 CF02 9672 E03 4 5.2 6 0.9 489.0 124.22000-07-13 04.00.00 CF01 9672 E03 4 4.4 6 0.9 489.0 309.72000-07-13 04.00.00 CF02 9672 E03 4 5.2 6 0.9 489.0 124.22000-07-13 05.00.00 CF01 9672 E03 4 4.5 6 0.9 489.0 309.72000-07-13 05.00.00 CF02 9672 E03 4 5.2 6 0.9 489.0 124.22000-07-13 06.00.00 CF01 9672 E03 4 4.6 6 0.9 489.0 309.72000-07-13 06.00.00 CF02 9672 E03 4 5.3 6 0.9 489.0 124.22000-07-13 07.00.00 CF01 9672 E03 4 4.6 6 0.9 489.0 309.72000-07-13 07.00.00 CF02 9672 E03 4 5.3 6 0.9 489.0 124.22000-07-13 08.00.00 CF01 9672 E03 4 4.7 6 0.9 489.0 309.72000-07-13 08.00.00 CF02 9672 E03 4 5.4 6 0.9 489.0 124.2

Tivoli Decision Support for OS/390: MVSPM86

Figure 212. Example of an MVSPM CF, Processor and Storage, Overview report



Proc util (%) The percentage of processor utilization within thecoupling facility. Calculated as (CPU_BUSY_SEC /(CPU_BUSY_SEC + CPU_WAIT_SEC)) * 100.

Proc effect The number of effective available logical processorsin a shared environment. This value is useful onlyin a CFCC environment. Calculated as(CPU_BUSY_SEC + CPU_WAIT_SEC) /MEASURED_SEC.

Storage size (MB) The average size of CF storage defined, inmegabytes.

Storage avail (MB) The average amount of free CF storage, inmegabytes.



MVSPM CF, Request Rate, Overview reportThis report shows an overview of the connected coupling facilities with theirrequest rate,


Report ID MVSPM87


Source MVSPM_CF_REQ_HV







CF model The model of the coupling facility.

CF version The version of the coupling facility.

CF level The level of the coupling facility.

Request rate The number of requests completed per second.Calculated as (REQ_SYNC_NO +REQ_ASYNC_NO + REQ_SYNC_ASYNC) /MEASURED_SEC.

MVSPM CF, Request Rate, OverviewSYSPLEX NAME: ’SYSPLEX1’

DATE: ’2000-07-13’ TO ’2000-07-13’

CF CF CF CF REQUESTDATE TIME NAME MODEL VERSION LEVEL RATE

---------- -------- -------- ----- ------- ------ ------------------2000-07-13 00.00.00 CF01 9672 E03 4 1.52000-07-13 00.00.00 CF02 9672 E03 4 2.12000-07-13 01.00.00 CF01 9672 E03 4 1.52000-07-13 01.00.00 CF02 9672 E03 4 2.12000-07-13 02.00.00 CF01 9672 E03 4 1.52000-07-13 02.00.00 CF02 9672 E03 4 2.12000-07-13 03.00.00 CF01 9672 E03 4 1.52000-07-13 03.00.00 CF02 9672 E03 4 2.12000-07-13 04.00.00 CF01 9672 E03 4 1.52000-07-13 04.00.00 CF02 9672 E03 4 2.12000-07-13 05.00.00 CF01 9672 E03 4 1.62000-07-13 05.00.00 CF02 9672 E03 4 2.22000-07-13 06.00.00 CF01 9672 E03 4 2.02000-07-13 06.00.00 CF02 9672 E03 4 2.52000-07-13 07.00.00 CF01 9672 E03 4 2.02000-07-13 07.00.00 CF02 9672 E03 4 2.62000-07-13 08.00.00 CF01 9672 E03 4 2.12000-07-13 08.00.00 CF02 9672 E03 4 2.8


Figure 213. Example of an MVSPM CF, Request Rate, Overview report



MVSPM CF, System Details, Overview reportThis report shows data about the systems connected to all coupling facilities in asysplex.


Report ID MVSPM88









MVS system ID The MVS system identification.

MVSPM CF, Systems detailsSYSPLEX NAME: ’SYSPLEX1’

DATE: ’2000-07-13’ TO ’2000-07-13’

MVS SYNC ASYNCCF SYSTEM SYNC AVG ASYNC AVG

DATE TIME NAME ID RATE SERV RATE SERV---------- -------- -------- ------ ----- ----- ----- ------2000-07-13 00.00.00 CF01 SC68 0.0 11.2 1.5 78.1

CF02 SC68 0.0 30.8 2.0 99.0

2000-07-13 01.00.00 CF01 SC68 0.0 12.5 1.5 78.6CF02 SC68 0.0 34.6 2.0 99.2

2000-07-13 02.00.00 CF01 SC68 0.0 11.4 1.5 77.6CF02 SC68 0.0 32.2 2.0 98.9

2000-07-13 03.00.00 CF01 SC68 0.0 12.1 1.5 78.8CF02 SC68 0.0 33.2 2.0 171.2

2000-07-13 04.00.00 CF01 SC68 0.0 12.2 1.5 80.1CF02 SC68 0.0 32.2 2.0 102.3

2000-07-13 05.00.00 CF01 SC68 0.0 13.0 1.6 77.8CF02 SC68 0.0 31.9 2.1 288.6

2000-07-13 06.00.00 CF01 SC68 0.0 11.8 2.0 76.0CF02 SC68 0.0 30.9 2.4 98.0

2000-07-13 07.00.00 CF01 SC68 0.0 12.4 2.0 77.6CF02 SC68 0.1 32.0 2.5 362.8

2000-07-13 08.00.00 CF01 SC68 0.0 12.4 2.1 74.7CF02 SC68 0.1 31.5 2.7 133.9


Figure 214. Example of an MVSPM CF, System Details, Overview report



Sync rate The number of synchronous requests completedper second. Calculated as REQ_SYNC_NO /MEASURED_SEC.

Sync avg serv The average time required to satisfy a synchronousCF request, in microseconds. Calculated asSERVICE_SYNC_SEC / REQ_SYNC._NO:

Async rate The number of asynchronous requests completedper second. coupling facility. Calculated as(CPU_BUSY_SEC / (CPU_BUSY_SEC +CPU_WAIT_SEC)) * 100.

Async avg serv The average time required to satisfy anasynchronous CF request, in microseconds.Calculated as SERVICE_ASYNC_SEC /REQ_ASYNC._NO.



MVSPM CF, Structures Details, Overview reportThis report shows data about the structures within the systems for all couplingfacilities in a sysplex.


Report ID MVSPM89




Variables From_date, To_date, Sysplex.





Structure name The name of the structure allocated in thiscoupling facility.

MVSPM CF, Structures detailsSYSPLEX NAME: ’SYSPLEX1’

DATE: ’2000-07-13’ TO ’2000-07-13’

MVS SYNC ASYNCCF STRUCTURE STRUCTURE SYSTEM SYNC AVG ASYNC AVG

DATE TIME NAME NAME TYPE ID RATE SERV RATE SERV---------- -------- -------- ---------------- --------- ------ ----- ----- ------ ------2000-07-13 00.00.00 CF01 DSNDSGA_LOCK1 03 SC68 0.0 0.0 0.0

DSNDSGA_SCA 01 SC68 0.0 0.0 0.0DSNDSGC_GBP0 04 SC68 0.0 0.0 0.0DSNHGHG_GBP0 04 SC68 0.0 0.0 0.0DSNHGHG_GBP3 04 SC68 0.0 0.0 0.0DSNHGHG_GBP32K 04 SC68 0.0 0.0 0.0DSNHGHG_LOCK1 03 SC68 0.0 0.0 0.0IEFAUTOS 02 SC68 0.0 0.0 0.0IMT0EMHQ 02 SC68 0.0 0.0 0.0IMT0LOCK1 03 SC68 0.0 0.0 0.0IMT0LOGEMHQ 01 SC68 0.0 0.0 0.0IMT0LOGMSGQ 01 SC68 0.0 0.0 0.0IMT0MSGQ 02 SC68 0.0 0.0 0.0IXC_DEFAULT_2 01 SC68 0.0 0.0 26.6JES2CKPT_2 02 SC68 0.0 0.0 0.0LOG_DFHSHUNT_P01 01 SC68 0.0 0.0 0.0SYSTEM_LOGREC 01 SC68 0.0 191.0 0.0

CF02 CACHECICS 04 SC68 0.0 0.0 0.0CICS_CACHE 04 SC68 0.0 0.0 0.0DSNDSGC_LOCK1 03 SC68 0.0 0.0 0.0DSNDSGC_SCA 01 SC68 0.0 0.0 0.0DSNHGHG_SCA 01 SC68 0.0 0.0 0.0IGWLOCK00 03 SC68 0.0 0.0 0.0ISGLOCK 03 SC68 0.7 126.0 0.0ISTGENERIC 02 SC68 0.0 0.0 0.0ISTMNPS 01 SC68 0.0 0.0 0.0IXC_DEFAULT_1 01 SC68 0.0 0.0 27.0JES2CKPT_1 02 SC68 0.0 0.0 0.0LOG_DFHLOG_P01 01 SC68 0.0 0.0 0.0SYSTEM_OPERLOG 01 SC68 0.0 275.1 0.0


Figure 215. MVSPM CF, Structures Details, Overview Report



Structure type The structure type identifier.

Sync rate The number of synchronous requests completedper second. Calculated as REQ_SYNC_NO /MEASURED_SEC.

Sync avg serv The average time required to satisfy a synchronousCF request, in microseconds. Calculated asSERVICE_SYNC_SEC / REQ_SYNC._NO:

Async rate The number of asynchronous requests completedper second. coupling facility. Calculated as(CPU_BUSY_SEC / (CPU_BUSY_SEC +CPU_WAIT_SEC)) * 100.

Async avg serv The average time required to satisfy anasynchronous CF request, in microseconds.Calculated as SERVICE_ASYNC_SEC /REQ_ASYNC._NO.

MVSPM MIPS for Machine Model List reportThis report shows the list of the MIPS for all the machines with the CPU_IDindication.


Report ID MVSPMM1


Source MVSPM_CPU_H

Attributes MVS, Performance, MIPS.

Variables From_date, To_date, Time, Period_name, MVS_system_ID,CPU_ID.



|

||

|

||

||

||

||

|||

|




Period The name of the period. This is derived usingfields date from the record as parameters in thePERIOD function.


Cpu model NO The CPU model number.

Cpu ID CPU identifier.

Cpu busy sec CPU busy time, in seconds.

Cpu busy MIPS MIPS for single CPU ID.

MVSPM Mips for Machine Model ListFrom date: All To date: All

System ID: All

Cpu Cpu CpuSystem Model Cpu busy busy

Date Time Period ID NO ID sec mips---------- -------- -------- ------ ------ ------ ---------- ----------2001-12-19 17.00.00 NIGHT 2DEV 2064 0 1.441E+03 1.599E+02

1 1.430E+03 1.587E+022 1.413E+03 1.568E+023 1.387E+03 1.540E+024 1.352E+03 1.500E+025 1.310E+03 1.454E+026 1.259E+03 1.397E+027 1.204E+03 1.336E+028 1.151E+03 1.277E+029 1.092E+03 1.212E+02

2001-12-19 17.55.00 NIGHT 2DEV 2064 0 2.797E+03 3.104E+021 2.763E+03 3.067E+022 2.716E+03 3.015E+023 2.653E+03 2.945E+024 2.573E+03 2.857E+025 2.476E+03 2.749E+026 2.360E+03 2.620E+027 2.239E+03 2.485E+028 2.126E+03 2.360E+029 2.005E+03 2.226E+02

Tivoli Decision Support: MVSPMM1

Figure 216. Example of MVSPM MIPS for Machine Model List



||||||||||||||||||||||||||||||||||||

||

||

||||

||

||

||

||

||

MVSPM MIPS for specific System ID reportThis report shows the list of the MIPS for all the machines.


Report ID MVSPMM2


Source MVSPM_CPU_H

Attributes MVS, Performance, MIPS, specific.

Variables From_date, To_date, Time, Period_name, MVS_system_ID.







Cpu ID CPU identifier.


Cpu busy MIPS MIPS for single CPU ID.

MVSPM MIPS for System ID Hourly List reportThis report shows the list of the MIPS for all the machines.


Report ID MVSPMM3

MVSPM Mips for specific System IDFrom date: ’1999-01-01’ To date: ’2002-12-12’

System ID: 2DEVCpu Cpu Cpu

System Model Cpu busy busyDate Time Period ID NO ID sec mips---------- -------- -------- ------ ------ ------ ---------- ----------2001-12-19 17.00.00 NIGHT 2DEV 2064 0 2.797E+03 3.104E+02

1 2.763E+03 3.067E+022 2.716E+03 3.015E+023 2.653E+03 2.945E+024 2.573E+03 2.857E+025 2.476E+03 2.749E+026 2.360E+03 2.620E+027 2.239E+03 2.485E+028 2.126E+03 2.360E+029 2.005E+03 2.226E+02

========== ==========2.471E+04 2.743E+03


Figure 217. Example of MVSPM MIPS for specific System ID



|

|

|

||

||

||

||

||

|

|

||

||

||

||

||

||

||

||

|

|

|

||


Source MVSPM_SYSTEM_H

Attributes MVS, Performance, MIPS, Specific.




Period The name of the period. This is derived usingfields date from the record as parameters in thePERIOD function.



Cpu ID The CPU model number.


Cpu busy MIPS The MIPS for single system ID.

MVSPM Mips for System ID Hourly ListFrom date: All To date: All

System ID: AllCpu Cpu Cpu

System Model busy busyDate Time Period ID NO sec mips---------- -------- -------- ------ ------ ---------- ----------2001-12-19 17.00.00 NIGHT 2DEV 2064 2.477E+04 2.749E+032001-12-19 18.00.00 NIGHT 2DEV 2064 1.932E+04 2.144E+032001-12-19 19.00.00 NIGHT 2DEV 2064 1.620E+04 1.798E+032001-12-19 20.00.00 NIGHT 2DEV 2064 1.817E+04 2.017E+032001-12-19 21.00.00 NIGHT 2DEV 2064 1.405E+04 1.559E+032001-12-19 22.00.00 NIGHT 2DEV 2064 1.713E+04 1.901E+032001-12-19 23.00.00 NIGHT 2DEV 2064 1.650E+04 1.832E+032001-12-20 00.00.00 NIGHT 2DEV 2064 1.577E+04 1.750E+032001-12-20 01.00.00 NIGHT 2DEV 2064 1.553E+04 1.723E+032001-12-20 02.00.00 NIGHT 2DEV 2064 1.574E+04 1.747E+032001-12-20 03.00.00 NIGHT 2DEV 2064 1.487E+04 1.650E+032001-12-20 04.00.00 NIGHT 2DEV 2064 1.041E+04 1.156E+032001-12-20 05.00.00 NIGHT 2DEV 2064 9.729E+03 1.080E+032001-12-20 06.00.00 NIGHT 2DEV 2064 1.363E+04 1.513E+032001-12-20 07.00.00 NIGHT 2DEV 2064 1.905E+04 2.115E+032001-12-20 08.00.00 PRIME 2DEV 2064 2.347E+04 2.605E+032001-12-20 09.00.00 PRIME 2DEV 2064 2.702E+04 2.999E+032001-12-20 10.00.00 PRIME 2DEV 2064 2.793E+04 3.100E+032001-12-20 11.00.00 PRIME 2DEV 2064 2.887E+04 3.205E+032001-12-20 12.00.00 PRIME 2DEV 2064 2.729E+04 3.029E+032001-12-20 13.00.00 PRIME 2DEV 2064 2.958E+04 3.283E+032001-12-20 14.00.00 PRIME 2DEV 2064 2.936E+04 3.259E+032001-12-20 15.00.00 PRIME 2DEV 2064 2.976E+04 3.304E+032001-12-20 16.00.00 PRIME 2DEV 2064 2.795E+04 3.102E+03


Figure 218. Example of MVSPM MIPS for System ID Hourly List



||||||||||||||||||||||||||||||||||||

||

||

||

||

|

||

||

||||

||

||

||

||

||

MVSPM Total CPU MIPS per LPAR and System reportThis report shows the list of the MIPS for all the machines.


Report ID MVSPM0A


Source MVSPM_SYSTEM_H

Attributes MVS, Performance, MIPS, System.




MVS System ID The SMF system ID.

LPAR_NAME The LPAR name for the specific system ID.

Phys Proc LPAR Total number of physical CPUs utilized in LPAR.

MIPS per LPAR Total number of MIPS per LPAR. The MIPSnumber is taken from the specific lookup table.

MIPS per logical CP Number of MIPS per single logical CPU.

CPU busy MIPS Vurtual processor MIPS time, in seconds.

MVSPM Total CPU Mips per LPAR and SystemSYSTEM: ’2DEV’ DATE: All TO All

MIPS CPUMVS PHYS MIPS PER BUSYSYSTEM LPAR PROC PER LOG MIPS

DATE TIME ID NAME LPAR LPAR CP---------- -------- ------ -------- ---------- ---------- ---------- ---------2001-12-20 00.00.00 2DEV *PHYSCAL 0.000E+00 0.000E+00 0.000E+00 0.000E+00

LIFEPROD 1.500E+00 2.904E+02 1.815E+01 8.952E+05SY1 1.000E+00 1.936E+02 1.210E+01 2.691E+05SY2 7.500E+00 1.452E+03 9.075E+01 2.289E+07

2001-12-20 01.00.00 2DEV *PHYSCAL 0.000E+00 0.000E+00 0.000E+00 0.000E+00LIFEPROD 1.500E+00 2.904E+02 1.815E+01 1.251E+05SY1 1.000E+00 1.936E+02 1.210E+01 2.551E+05SY2 7.500E+00 1.452E+03 9.075E+01 8.182E+07

Figure 219. Example of MVSPM Total CPU MIPS per LPAR and System



|

|

|

||

||

||

||

||

|

||

||

||

||

||

|||

||

||

Application use of resources reportsThese reports shows system resources and processor usage by workload,performance group, and transaction class, for a selected time period.

MVSPM System Resources by Workload Type reportThis report shows how the major system resources are consumed by the differentworkloads in the system. Expanded storage resources are reported only fromMVS/ESA System Performance Version 4 and later. In earlier versions, the centralstorage chart shows total processor storage (both central and expanded). Thisreport shows the resources used by the workload type as a percentage of the totalresources used. You can select this report for each MVS system, or for a wholesysplex. This report works for goal mode and compatibility mode. Refer to theglossary for definitions of these terms. For more information on using this report,refer to the System Performance Feature Guide.


Report ID MVSPM24


Source MVSPM_WORKLOAD_HV, MVSPM_WORKLOAD2_HV

Attributes MVS, Performance, RMF, CPU, Workload, Storage, I/O, Sysplex

Variables Date, MVS_system_ID, Period_name, Sysplex_name



20%

40%12%

27%1%

47%

10%5%

36%2% 1%

5%3%

75%

16% 1%13%10%

30%

45%

CPUtime

I/Ooperations

Centralstorage

Expandedstorage

BATCH CICS IMS OTHER SYSTEM

Figure 220. Example of an MVSPM System Resources by Workload Type report



CPU time The percentage of the total processor busy time foreach workload type. Calculated as:(CPU_BUSY_SEC * 100) / CPU_ONLINE_SEC.

I/O operations The percentage of the total number of I/Ooperations serviced per second for each workloadtype. This is based on I/O service units. Calculatedas: IO_RATE_FACTOR / (TIME_RESOLUTION *60).

Central storage The percentage of the total central storage used foreach workload type. Calculated as:(TOT_FRAME_SEC − ES_FRAME_SEC) /(TIME_RESOLUTION * 60) / 256.

Expanded storage The percentage of the total expanded storage usedfor each workload type. Calculated as:ES_FRAME_SEC / (TIME_RESOLUTION * 60) /256.



MVSPM CPU Busy by Workload Types, Hourly Trend reportThis report shows the hourly trend for the CPU busy percent for all workloads.This report works for goal mode and compatibility mode. Refer to the glossary fordefinitions of these terms. For more information on using this report, refer to theSystem Performance Feature Guide.


Report ID MVSPM25


Source MVSPM_WORKLOAD_HV, MVSPM_SYSTEM_H,MVSPM_WORKLOAD2_HV

Attributes MVS, Performance, RMF, CPU, Workload, Hourly





CPU busy percent The average CPU busy percent of the total system.Calculated as: CPU_BUSY_PCT / CPU_ONLINE.

Percent

0

10

20

30

40

50

Time of day08:

0009:

0010:

0011:

0012:

0013:

0014:

0015:

0016:

00

17

25

3027

14

21

42

47 47

BATCHCICSSTCSYSTEMTSOCTSOS

Figure 221. Example of an MVSPM CPU Busy by Workload Types, Hourly Trend report



MVSPM CPU Busy by Workload PGNs, Hourly Trend reportThis report can be used to show how much CPU is spent by each performancegroup. You may select the report by one or more workloads. For more informationon using this report, refer to the System Performance Feature Guide.

Report ID MVSPM26


Source MVSPM_WORKLOAD_HV

Attributes MVS, Performance, RMF, CPU, Workload, Perf_group_no, Hourly

Variables Date, MVS_system_ID, Period_name, Workload_mask



Perf group no The performance group number.

CPU busy percent The average CPU busy time per processor, inpercent.

Percent of processor

0

20

40

60

80

100

Time of day08:

0009:

0010:

0011:

0012:

0013:

0014:

0015:

0016:

00

33

51

6053

29

41

84

94 93

01236

Figure 222. Example of an MVSPM CPU Busy by Workload PGNs, Hourly Trend report



MVSPM Storage Used by Workload Type, Hourly Trend reportThis report shows the processor storage used by different workload types. Bothcentral and expanded storage are included. This report works for goal mode andcompatibility mode. Refer to the glossary for definitions of these terms.



Report ID MVSPM27



Attributes MVS, Performance, RMF, CPU, Workload, Storage, Hourly





Storage used (megabytes) The total storage used, in megabytes. Calculated as:TOT_FRAME_SEC / (TIME_RESOLUTION * 60) /256.

Mega

byte

s

0

50

100

150

200

250

Time of day00:

0001:

0002:

0003:

0004:

0005:

0006:

0007:

0008:

0009:

0010:

0011:

0012:

0013:

0014:

0015:

0016:

0017:

0018:

0019:

0020:

0021:

0022:

0023:

00

90

24

106109106108110123

132144

171183189

211218207196

180

84

49 51 55 50 51 BATCHCICSSTCSYSTEMTSOCTSOS

Figure 223. Example of an MVSPM Storage Used by Workload Type, Hourly Trend report



MVSPM Storage Used by Workload PGNs, Hourly Trend reportThis report shows the processor storage used by different performance groups.Both central and expanded storage are included. The report can be shown for aselected workload type or all workload types. For more information on using thisreport, refer to the System Performance Feature Guide.


Report ID MVSPM28


Source MVSPM_WORKLOAD_HV

Attributes MVS, Performance, RMF, Workload, Perf_group_no, Storage,Hourly

Variables Date, MVS_system_ID, Period_name, Workload_mask




Storage used (megabytes) The total storage used, in megabytes. Calculated as:TOT_FRAME_SEC / (TIME_RESOLUTION * 60) /256.

Megabytes

0

50

100

150

200

250

Time of day00:

0001:

0002:

0003:

0004:

0005:

0006:

0007:

0008:

0009:

0010:

0011:

0012:

0013:

0014:

0015:

0016:

0017:

0018:

0019:

0020:

0021:

0022:

0023:

00

90

24

106109106108110123

132144

171183189

211218

207196

180

84

49 51 55 50 51

01236

Figure 224. Example of an MVSPM Storage Used by Workload PGNs, Hourly Trend report



MVSPM I/O Rate by Workload Types, Hourly Trend reportThis report shows the I/O rate for all workloads or a selected workload. The I/Orate is calculated from the I/O service units in SMF records 72. This report worksfor goal mode and compatibility mode. Refer to the glossary for definitions ofthese terms.


Report ID MVSPM29



Attributes MVS, Performance, RMF, I/O rate, Workload, Hourly

Variables Date, MVS_system_ID, Period_name, Workload_type




I/Os per second The number of I/O operations serviced per second.

I/Os per second

0

20

40

60

80

100

120

140

160

Time of day08:

0009:

0010:

0011:

0012:

0013:

0014:

0015:

0016:

00

BATCHCICSSTCSYSTEMTSOCTSOS

Figure 225. Example of an MVSPM I/O Rate by Workload Types, Hourly Trend report



MVSPM CPU per I/O by Workload Type, Hourly Trend reportThis report shows the CPU time per I/O operation for a selected workload or theaverage for all workload types. This report works for goal mode and compatibilitymode. Refer to the glossary for definitions of these terms.


Report ID MVSPM30


Source MVSPM_WORKLOAD_HV, MVSPM_SYSTEM_HV,MVSPM_WORKLOAD2_HV

Attributes MVS, Performance, RMF, CPU, Workload, I/O, Hourly

Variables From_date, To_date, MVS_system_ID, Period_name,Workload_type




CPU per I/O The average CPU used per I/O operation.Calculated as: 0.01 * CPU_BUSY_PCT / IO_RATE.CPU_BUSY_PCT is the CPU busy time in percent.IO_RATE is the number of I/O operations servicedper second.

Seconds

0.0000

0.0020

0.0040

0.0060

0.0080

0.0100

0.0120

0.0140

0.0160

Time of day08.

0009.

0010.

0011.

0012.

0013.

0014.

0015.

0016.

00

1999-08-041999-08-051999-08-061999-08-071999-08-101999-08-12

Figure 226. Example of an MVSPM CPU per I/O by Workload Type, Hourly Trend report



MVSPM CPU per I/O by Workload PGNs, Hourly Trend reportThis report shows the CPU time per I/O operation by different performancegroups. The report can be shown for a selected workload type or all workloadtypes.


Report ID MVSPM31


Source MVSPM_WORKLOAD_HV MVSPM_SYSTEM_HV

Attributes MVS, Performance, RMF, Workload, Perf_group_no, I/O, Hourly





CPU per I/O The average CPU used per I/O operation.Calculated as: 0.01 * CPU_BUSY_PCT / IO_RATE.

Seco

nds

0.000

0.050

0.100

0.150

0.200

0.250

0.300

0.350

Time of day00:

0001:

0002:

0003:

0004:

0005:

0006:

0007:

0008:

0009:

0010:

0011:

0012:

0013:

0014:

0015:

0016:

0017:

0018:

0019:

0020:

0021:

0022:

0023:

00

01236

Figure 227. Example of an MVSPM CPU per I/O by Workload PGNs, Hourly Trend report



MVSPM Page-ins by Workload Types, Hourly Trend reportThis report shows the number of page-ins by different workload types. This reportworks for goal mode and compatibility mode. Refer to the glossary for definitionsof these terms.



Report ID MVSPM32



Attributes MVS, Performance, RMF, Workload, Paging, Hourly





Page-in rate The number of page-in operations per second.Calculated as: (READ_MISSES_HIPER + PAGEINS)/ (TIME_RESOLUTION * 60).

Pages per seconds

0.00

0.50

1.00

1.50

2.00

Time of day00:

0001:

0002:

0003:

0004:

0005:

0006:

0007:

0008:

0009:

0010:

0011:

0012:

0013:

0014:

0015:

0016:

0017:

0018:

0019:

0020:

0021:

0022:

0023:

00

BATCHSTCCICSSYSTEMTSOCTSOS

Figure 228. Example of an MVSPM Page-ins by Workload Types, Hourly Trend report



MVSPM Paging Activity by Workload, Hourly Trend reportThis report shows the different types of page-in activity per hour and workloadtype. If your system has a paging problem, you can use this report to investigatewhich workload causes the paging activity and at what time the different types ofpaging occur.


Report ID MVSPM19


Source MVSPM_APPL_H, MVSPM_APPL_H

Attributes MVS, Performance, Workload, Paging, Hourly





Non block page-in rate (/s) The normal page-in rate, excluding block, VIO,swap, and hiper page-in. Calculated as: (PAGEINS- BLOCKS_IN_AUX)/(TIME_RESOLUTION*60).

Block page-in rate (/s) The page-in rate for blocked pages that were pagedin from auxiliary storage. Calculated as:(PAGEINS_BLK_AUX)/(TIME_RESOLUTION*60).

VIO page-in rate (/s) The page-in rate caused by virtual I/O. Calculatedas: PAGEINS_VIO/(TIME_RESOLUTION*60).

Swap page-in rate (/s) The page-in rate due to swapping. Calculated as:PAGES_SWAPPED_IN/(TIME_RESOLUTION*60).

Hiper page-in rate (/s) The hiperspace page-in rate. Calculated as:PAGEINS_HIPER/(TIME_RESOLUTION*60).

Common page-in rate (/s) The common area (LPA + CSA) page-in rate.

MVSPM Paging Activity by Workload, Hourly TrendSystem: ’MVS1’ Date: ’2000-02-20’

Period: ’PRIME’ Workload: All

Non block Block VIO Swap Hiper Common Sharedpage-in page-in page-in page-in page-in page-in page-in

Time rate (/s) rate (/s) rate (/s) rate (/s) rate (/s) rate (/s) rate (/s)----- --------- --------- --------- --------- --------- --------- ---------12:00 6.54 24.29 4.13 34.61 0.00 0.40 0.0013:00 4.83 7.50 0.42 146.07 0.00 0.22 0.0014:00 2.88 14.49 6.55 36.66 0.00 0.14 0.0015:00 4.12 10.12 6.11 77.31 0.00 0.31 0.0016:00 3.18 17.05 0.87 46.05 0.00 0.17 0.0017:00 4.99 4.39 0.12 137.31 0.00 0.10 0.0018:00 3.38 37.50 0.02 46.06 0.00 0.07 0.00

========= ========= ========= ========= ========= ========= =========4.27 16.48 2.60 74.87 0.00 0.20 0.00


Figure 229. Example of an MVSPM Paging Activity by Workload, Hourly Trend report



Calculated as:PAGEINS_COMMON/(TIME_RESOLUTION*60).

Shared page-in rate (/s) The page-in rate for shared pages. Calculated as:PAGEINS_SHARED/(TIME_RESOLUTION*60).



MVSPM Resp Time by Workload Types, Hourly Trend reportThis report shows the average response time profile for a selected workload. Thisreport works for goal mode and compatibility mode. Refer to the glossary fordefinitions of these terms.


Report ID MVSPM33



Attributes MVS, Performance, RMF, CPU, Workload, Response_time, Hourly

Variables From_date, To_date, MVS_system_ID, Period_name,Workload_type




Response time seconds The average transaction response time, in seconds.Calculated as: TRAN_ELAPSED_SEC /TRANSACTIONS.

Seco

nds

0

1

2

3

4

5

6

7

Time of day08:

0009:

0010:

0011:

0012:

0013:

0014:

0015:

0016:

00

1999-08-041999-08-051999-08-061999-08-071999-08-101999-08-12

Figure 230. Example of an MVSPM Resp Time by Workload Types, Hourly Trend report



MVSPM Workload Resp Time Components, Hourly Trendreport

This report shows the response time components for a selected workload type.This report works for goal mode and compatibility mode. Refer to the glossary fordefinitions of these terms.


Report ID MVSPM34


Source MVSPM_WORKLOAD_HV, MVSPM_PAGE_DS_HV,MVSPM_WORKLOAD2_HV

Attributes MVS, Performance, RMF, CPU, Workload, Response_time, Hourly




CPU time The total CPU time per transaction, in seconds.Calculated as: ((TCB_TIME_FACTOR /SERVICE_UNITS_MAX) + (SRB_TIME_FACTOR /SERVICE_UNITS_MAX) + IOINTR_SEC +RCT_SEC + HIPER_SERVICE_SEC) /TRANSACTIONS).

Out ready The average out and ready time per transaction, inseconds. Calculated as ((TRAN_ACTIVE_SEC /(TIME_RESOLUTION * 60)) -

Seconds

0.000

0.020

0.040

0.060

0.080

0.100

0.120

Time of day08:

0009:

0010:

0011:

0012:

0013:

0014:

0015:

0016:

00

0.0

0.0

0.1 0.1 0.10.1

0.1

0.1

0.1

CPUtime

Outready

PagingOther

Figure 231. Example of an MVSPM Workload Resp Time Components, Hourly trend report



(TRAN_RESIDENT_SEC / TIME_RESOLUTION *60)) * (TRAN_ELAPSED_SEC / TRANSACTIONS)/ (TRAN_ACTIVE_SEC / (TIME_RESOLUTION *60)).

Paging The average time per transaction waiting forpage-ins. Calculated as: RESPONSE_LOCAL_SEC *DEM_PAGES_PER_TRAN.

Other The total time per transaction, in seconds.Calculated as: RESPONSE_SEC −(CPU_PER_TRAN - OUTREADY_PER_TRAN−(RESPONSE_LOCAL_SEC *DEM_PAGES_PER_TRAN)).



MVSPM BMF Member Page Reads/Hits, Hourly Trend reportThis report shows the number of PDSE member page reads and PDSE memberpage read hits, by storage class, for the selected period. Read hits can occur whena member page is cached in hiperspace by BMF. Only high performance andcommonly shared PDSE data sets are optionally cached in hiperspace. The absolutenumber of member page read hits is not meaningful by itself, because severalfactors may cause hit ratios to go both up and down. The hit ratio can be used tomonitor and evaluate DFP changes over time and also to evaluate and test goodcandidates for hiperspace caching.


Report ID MVSPM60


Source MVSPM_BMF_H

Attributes MVS, Performance, BMF, Read_hits, Reads, Hourly, Member_page,PDSE

Variables Date, MVS_system_ID, Period_name, Storage_class

The columns in this report contain this information:


Member page read hits The number of member data page read hitshandled by BMF.

Member page reads The number of member page reads.

400

600

800

1,000

1,200

1,400

1,600

Time of day08:

0010:

0012:

0014:

0016:

00

Memberpageread hits

Memberpagereads

Figure 232. Example of an MVSPM BMF Member Page Reads/Hits, Hourly Trend report



MVSPM BMF Directory Page Reads/Hits, Hourly Trend reportThis report shows the number of PDSE directory page reads and PDSE directorypage read hits, by storage class, for the selected period. Read hits can occur whena directory page is already cached in a data space by BMF. Directory pages forPDSE data sets are always read into BMF’s data space. The absolute number ofdirectory page read hits is not meaningful by itself, because several factors maycause hit ratios to go both up and down. The read hit ratio can be used to monitorand evaluate DFP changes over time and also to evaluate and test the accessbehavior of PDSE candidates.


Report ID MVSPM61


Source MVSPM_BMF_H

Attributes MVS, Performance, BMF, Read_hits, Reads, Hourly, Directory_page,PDSE

Variables Date, MVS_system_ID, Period_name, Storage_class

The columns in this report contain this information:


Directory page read hits The number of directory data page read hitshandled by BMF.

Directory page reads The number of directory data page reads.

2,000

4,000

6,000

8,000

10,000

12,000

Time of day08:

0010:

0012:

0014:

0016:

00

Directorypageread hits

Directorypagereads

Figure 233. Example of an MVSPM BMF Directory Page Reads/Hits, Hourly Trend report



MVSPM APPC, CPU and I/O by Transaction Class reportThis report shows CPU and I/O used by APPC transaction programs, grouped bytransaction class.


Report ID MVSPM62


Source MVSPM_APPC_H

Attributes MVSPM, APPC





TP class The transaction program class.

TP type The transaction program schedule type.

TCB seconds The total task control block time, in seconds.

SRB seconds The total service request block time, in seconds.

Excp count The total number of EXCPs.

MVSPM APPC, CPU and I/O by Transaction ClassSystem: ’SYS1’ Date: ’2000-03-03’ to ’2000-03-04’

TP TP TCB SRB ExcpDate Period class type seconds seconds count---------- -------- -------- ---- -------- -------- ------------2000-03-03 PRIME STANDARD 0 76 1 64

-------- -------- ------------* 76 1 64

-------- -------- ------------** 76 1 64

-------- -------- ------------*** 76 1 64

2000-03-04 NIGHT STANDARD 0 37 1 26-------- -------- ------------

* 37 1 26

-------- -------- ------------** 37 1 26

PRIME STANDARD 0 1291 48 1010-------- -------- ------------

* 1291 48 1010

-------- -------- ------------** 1291 48 1010

-------- -------- ------------*** 1328 49 1036


Figure 234. Example of an MVSPM APPC, CPU and I/O by Transaction Class report



MVSPM APPC, Execution and Queueing, Hourly Trend reportThis report shows execution and queue elapsed time for APPC transactionprograms in a specific transaction program class.


Report ID MVSPM63


Source MVSPM_APPC_H

Attributes MVSPM, APPC

Variables Date, MVS_system_ID, Period_name, TP_class



Elapsed exec sec The total elapsed time from the time the requeststarted its execution to the time its executionended, in seconds.

Elapsed queue sec The total elapsed time from the time the requestwas placed in the scheduler work queue to thetime its execution started, in seconds.

Figure 235. Example of an MVSPM APPC, Execution and Queueing, Hourly Trend report



MVSPM VLF Usage and Hit Ratio, Hourly/Daily Trend reportThis report shows usage and hit ratio by hour for a VLF class. The hit percent forLLA (CSVLLA) should always be 100% since LLA manages which objects VLFhandles for it and it only requests those that it gives to VLF.


Report ID MVSPM64 (hourly), MVSPM66 (daily)


Source MVSPM_VLF_H

Attributes MVS, Performance, Trend, Hourly, Daily, VLF, Lookaside

Variables Date, From_date, To_date, MVS_system_ID, VLF_class,Period_name


VLF Class The name of the VLF class.


Hit (%) The number of objects found in the dataspace, inpercent of the total number of searches.

Searches /min The number of times the dataspace was searchedper minute.

Hits /min The number of objects found in the dataspace perminute.

Objects added The number of objects added to the dataspace.

MVSPM VLF Usage and Hit Ratio, Hourly TrendSystem: ’NRD1’ Period: PERIOD_NAME

Date: ’1999-10-09’

VLF Hit Searches Hits Objects Objects ObjectsClass Time (%) /min /min added deleted trimmed-------- ----- ------ -------- -------- ------- ------- -------CSVLLA 02:00 100 145.6 145.6 173 0 17

03:00 100 47.6 47.6 10 0 004:00 99 26.0 25.8 3 0 005:00 100 36.5 36.5 11 0 606:00 100 25.1 25.1 0 0 007:00 100 103.4 103.3 32 0 008:00 100 152.9 152.9 40 0 109:00 100 110.2 110.2 65 0 1810:00 100 77.7 77.7 114 292 011:00 100 73.0 73.0 42 0 012:00 100 138.5 138.5 63 0 013:00 100 129.6 129.6 55 0 014:00 100 107.0 107.0 23 0 015:00 100 101.3 101.3 20 0 016:00 100 72.6 72.6 1 0 017:00 100 69.0 69.0 2 0 018:00 100 35.9 35.9 0 0 019:00 100 11.4 11.4 0 0 020:00 100 7.4 7.4 0 0 021:00 100 5.9 5.9 0 0 022:00 100 6.0 6.0 0 0 023:00 100 19.7 19.7 2 0 0


Figure 236. Example of an MVSPM VLF Usage and Hit Ratio, Hourly Trend report



Objects deleted The number of objects deleted from the dataspace.

Objects trimmed The number of objects trimmed from thedataspace.



MVSPM VLF Dataspace Usage, Hourly/Daily Trend reportThese reports show dataspace usage by hour for a VLF class. For more informationon using these reports, refer to the System Performance Feature Guide.


Report ID MVSPM65 (hourly), MVSPM67 (daily)


Source MVSPM_VLF_H

Attributes MVS, Performance, Trend, Hourly, Daily, VLF, Lookaside

Variables Date, From_date, To_date, MVS_system_ID, VLF_class,Period_name


VLF Class The name of the VLF class.


Storage used avg (%) The average virtual storage used for dataspace, inpercent of the maximum dataspace size.

MVSPM VLF Dataspace Usage, Hourly TrendSystem: ’NRD1’ Period: PERIOD_NAME

Date: ’1999-10-09’

Storage Storage Storage Storage LargestVLF used avg MAXVIRT used min used max used avg object

Class Time (%) (MB) (MB) (MB) (MB) (MB)-------- ----- -------- ------- -------- -------- -------- --------CSVLLA 02:00 92 16.0 14.578 14.961 14.706 2.488

03:00 91 16.0 14.586 14.602 14.598 2.48804:00 92 16.0 14.613 14.668 14.641 2.48805:00 91 16.0 13.434 14.992 14.603 2.48806:00 84 16.0 13.434 13.434 13.434 2.48807:00 89 16.0 13.859 14.297 14.178 2.48808:00 87 16.0 12.750 14.984 13.848 2.48809:00 92 16.0 14.473 14.809 14.643 2.48810:00 16 16.0 0.000 4.832 2.584 2.48811:00 36 16.0 5.406 6.148 5.750 2.48812:00 41 16.0 6.391 6.867 6.598 2.48813:00 57 16.0 8.582 9.242 9.063 2.48814:00 62 16.0 9.242 10.879 9.986 2.48815:00 79 16.0 12.055 13.609 12.624 2.48816:00 85 16.0 13.609 13.625 13.617 2.48817:00 85 16.0 13.625 13.633 13.629 2.48818:00 85 16.0 13.633 13.633 13.633 2.48819:00 85 16.0 13.633 13.633 13.633 2.48820:00 85 16.0 13.633 13.633 13.633 2.48821:00 85 16.0 13.633 13.633 13.633 2.48822:00 85 16.0 13.633 13.633 13.633 2.48823:00 85 16.0 13.664 13.664 13.664 2.488


Figure 237. Example of an MVSPM VLF Dataspace Usage, Hourly Trend report



MAXVIRT (MB) MAXVIRT is a parameter specified in theCOFVLFLxx parmlib member, and specifies themaximum amount of virtual storage (max dataspace size) that VLF can use to store objects for theclass.

Storage used min (MB) The minimum virtual storage used for dataspace.

Storage used max (MB) The maximum virtual storage used for dataspace.

Storage used avg (MB) The average virtual storage used for dataspace.

Largest object (MB) The largest object that was attempted to be put inthe dataspace.



MVSPM Applications Waiting on ENQs, Hourly Trend reportThis report shows the hourly trend for applications waiting on enqueuedresources. The resource names can be found from report MVSPM52 (see “MVSPMApplications Waiting on ENQs, Worst Case report” on page 859).


Report ID MVSPM55


Source MVSPM_ENQUEUE_HV

Attributes MVS, Performance, RMF, CPU, ENQ, Hourly

Variables Date, MVS_system_ID, Period_name, Queue_name_list



Queue name The major queue name of the resource.

Average number of requests waitingThe average number of applications waiting onenqueue. Calculated as: (WAITING_REQUESTS /CONTENTION_EVENTS) *CONTENTION_TOT_SEC / (TIME_RESOLUTION* 60).

Aver

age

numb

er o

f re

ques

ts w

aiti

ng

0.00

0.50

1.00

1.50

2.00

2.50

3.00

00:0003:

0004:

0005:

0006:

0007:

0008:

0009:

0010:

0011:

0012:

0013:

0014:

0015:

0016:

0017:

0018:

0019:

0020:

0021:

0022:

00

SYSDSNSYSIEFSDSYSZDRKSYSZTIOT

Figure 238. Example of an MVSPM Applications Waiting on ENQs, Hourly Trend report



MVSPM Applications Waiting on ENQs, Worst Case reportThis report shows the resources that cause the most wait time for applications. Theenqueue names shown here can be used as input for report MVSPM55, whichshows the hourly trend for waiting applications. Use the Maxrows variable to limitthe number of elements shown in the chart. For more information on using thisreport, refer to the System Performance Feature Guide.


Report ID MVSPM52


Source MVSPM_ENQUEUE_HV

Attributes MVS, Performance, RMF, CPU, ENQ, Worst_case

Variables Date, MVS_system_ID, Period_name, Maxrows


Major queue name The major queue name of the resource.

Average applications waiting The average number of applications waiting onenqueue. Calculated as: (WAITING_REQUESTS /CONTENTION_EVENTS) *CONTENTION_TOT_SEC / (TIME_RESOLUTION* 60).

Average applications waiting

0.00

0.20

0.40

0.60

0.80

1.00

Major queue nameSYSIEFSD SYSDSN SYSZTIOT SYSZDRK SYSZVVDS

1.00

0.20

0.00 0.00 0.00

Figure 239. Example of an MVSPM Applications Waiting on ENQs, Worst Case report



MVSPM Response Time Goals & Actuals, Hourly Trend reportThis report shows the trend of the average response time and corresponding goalfor selected service classes. The report can show a summary for the whole sysplexor for a selected MVS system. This report is available only when the MVS systemis running in goal mode.


Report ID MVSPM78



Attributes MVS, Goal_actual, Response, Service_class, Trend, Sysplex, Goalmode

Variables Date, Sysplex name, MVS system ID, Serv class list, Serv classperiod, Period name




Service class/period Service class name and service period number.

Response time (sec) Average response time. Calculated as:TRAN_ELAPSED_SEC/TRANSACTIONS.

Goal (s) The response time goal.

Resp

onse

tim

e (s

ec)

Time of day

Figure 240. Example of an MVSPM Response Time Goals & Actuals, Hourly Trend report



MVSPM Exec. Velocity Goals & Actuals, Hourly Trend reportThis report shows the trend for the average execution velocity and correspondinggoal for selected service classes. The report can show a summary for the wholesysplex or for a selected MVS system. This report is available only when the MVSsystem is running in goal mode.


Report ID MVSPM76



Attributes MVS, Execution, Velocity, Service_class, Trend, Goal_actual, Goalmode, Sysplex

Variables Date, Sysplex name, MVS system ID, Serv class list, Serv classperiod, Period name




Service class/period Service class name and service class period.

Execution velocity(%) This is the actual execution velocity. Calculated as:100*CPU_USE_CNT/(CPU_USE_CNT +TOTAL_DELAY_CNT).

Velocity goal (%) The execution velocity goal. FromEXEC_VEL_GOAL_PCT.



MVSPM Response Time Distribution reportThis report shows the response time distribution for a selected shift and serviceclass. This report is available only when the MVS system is running in goal mode.


Report ID MVSPM74


Source MVSPM_GOAL_ACT_H

Attributes MVS, Performance, Goal mode, Response, Sysplex

Variables Date, Sysplex name, Service class, Serv class period, MVS systemID, Period name




Sysplex name The sysplex name.

Serv cl The service class name.

SCP The service class period.

Response time (sec) The response time.

Percent The percent of transactions within thecorresponding response time interval.

Goal The response time goal for this service class.

Percent transactions

Response time (sec)

3

9

13

20

109

87

65

43

21

Figure 241. Example of an MVSPM Response Time Distribution report



MVSPM Served Service Classes, Overview reportThis report shows how service classes were served by other service classes. Thisreport is available only when the MVS system is running in goal mode.


Report ID MVSPM79


Source MVSPM_WLM_SERVED_H, MVSPM_WORKLOAD2_H

Attributes MVS, Served, Service_class, Overview, Sysplex, Goal mode

Variables Date, Sysplex name, MVS system ID, Workload group, Serviceclass, Period name



Workload group The workload group name.

Service class Name of the service class that provides the service.

Served class Name of the service class that receives the service.

No of times served Number of times the service was provided.

No of tx’s Number of transactions.

No of times served per tx Number of times per transaction the service classrequested service. Calculated as:SERVED_NO/TRANSACTIONS.

MVSPM Served Service Classes, OverviewSysplex: ’SYSPLEX1’ System: MVS_SYSTEM_IDDate: ’2000-02-01’ Period: ’PRIME’

Workload Service Served No of times No of No of timesgroup class class served tx’s served per tx-------- -------- -------- ------------ ------------ --------------CICS CICSREGS CICS-1 15227 664 22.9

CICS-2 6405 215 29.8CICS-3 24992 1251 20.0CICS-4 87155 1501 58.1CICSTRX 67769 9314 7.3


Figure 242. Example of an MVSPM Served Service Classes Overview report



MVSPM Response Time Breakdown, Overview reportThis report shows how much the various transaction states contribute to theaverage response time. This report is available when the MVS system is running ingoal mode and when the subsystem is CICS or IMS.


Report ID MVSPM73


Source MVSPM_WLM_STATE_H

Attributes MVS, Performance, RMF, Overview, Workload, Response_time,Sysplex

Variables Date, Sysplex name, Subsystem ID, Workload group, Service class,Period name



Workload group Workload group name.

Subsystem ID Subsystem ID name.

Service class /Period Service class name and period.

Ph Phase, BTE; ″Begin To End″ or EXE; ″Execution″.

MVS sys ID MVS system ID.

Total state (%) Total percentage of state samples for this serviceclass. Calculated as:100*TOTAL_STATE_CNT/WLM_SAMPLES_TOT).

Active state (%) Percent of samples when a program was active forthis service class. Calculated as:100*ACTIVE_STATE_CNT/WLM_SAMPLES_TOT).

Ready state (%) Percent of samples when a program was ready to

MVSPM Response Time Breakdown, OverviewSysplex: ’SYSPLEX1’ Subsystem: SUBSYSTEMDate: ’2000-02-01’ Period: ’PRIME’

Service MVS Total Activ Ready Idle Lock I/O Conv Distr Local Netw Syspl Timer Other MiscWorkload class sys state state state state wait wait wait wait wait wait wait wait wait waitgroup /Period Ph ID (%) (%) (%) (%) (%) (%) (%) (%) (%) (%) (%) (%) (%) (%)

-------- ---------- --- ---- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- -----CICS CICS-1 /1 BTE CA0 6.6 0.0 0.0 0.0 0.0 0.0 6.5 0.0 0.0 0.0 0.0 0.0 0.0 0.0

C80 29.4 0.0 0.0 0.0 0.0 0.0 14.7 0.0 0.0 0.0 0.0 0.0 14.6 0.0C90 3.8 0.4 1.3 1.5 0.0 0.2 0.5 0.0 0.0 0.0 0.0 0.0 0.0 0.0

----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- -----* 13.3 0.1 0.5 0.5 0.0 0.1 7.2 0.0 0.0 0.0 0.0 0.0 4.9 0.0

/1 EXE CA0 16.0 0.1 0.2 0.1 0.0 15.5 0.0 0.0 0.0 0.0 0.0 0.0 0.1 0.0C80 14.9 0.1 0.1 0.1 0.0 3.7 0.0 0.0 0.0 0.0 0.0 0.0 11.0 0.0C90 14.0 1.6 4.5 4.8 0.0 3.2 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0

----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- -----* 14.9 0.6 1.6 1.7 0.0 7.4 0.0 0.0 0.0 0.0 0.0 0.0 3.7 0.0

IMS IMS-1 /1 EXE CA0 20.7 0.4 0.7 0.0 0.0 0.0 19.6 0.0 0.0 0.0 0.0 0.0 0.0 0.0C80 1.1 0.2 0.1 0.7 0.0 0.1 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0C90 22.2 5.3 11.9 1.2 0.0 0.2 3.6 0.0 0.0 0.0 0.0 0.0 0.0 0.0

----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- -----* 14.7 2.0 4.2 0.6 0.0 0.1 7.8 0.0 0.0 0.0 0.0 0.0 0.0 0.0


Figure 243. Example of an MVSPM Response Time Breakdown Overview report



execute. Calculated as:100*READY_STATE_CNT/WLM_SAMPLES_TOT).

Idle state (%) Percent of idle state samples. No work wasallowed to run. Calculated as:100*IDLE_STATE_CNT/WLM_SAMPLES_TOT).

Lock wait (%) Percentage of waiting for lock samples. Calculatedas:100*LOCK_STATE_CNT/WLM_SAMPLES_TOT).

I/O wait (%) Percentage of waiting for I/O samples. Calculatedas: 100*IO_STATE_CNT/WLM_SAMPLES_TOT).

Conv wait (%) Percentage of waiting for conversation samples.Calculated as:100*CONV_STATE_CNT/WLM_SAMPLES_TOT).

Distr wait (%) Percentage of waiting for distributed requestsamples. Calculated as:100*DISTR_STATE_CNT/WLM_SAMPLES_TOT).

Local wait (%) Percentage of waiting for a session to beestablished locally state samples. Calculated as:100*SES_LOC_STATE_CNT/WLM_SAMPLES_TOT).

Netw wait (%) Percentage of waiting for a session to beestablished somewhere in the network statesamples. Calculated as:100*SES_NET_STATE_CNT/WLM_SAMPLES_TOT).

Syspl wait (%) Percentage of waiting for a session to beestablished somewhere in the sysplex statesamples. Calculated as:100*SES_SPX_STATE_CNT/WLM_SAMPLES_TOT).

Timer wait (%) Percentage of waiting for a timer samples.Calculated as:100*TIMER_STATE_CNT/WLM_SAMPLES_TOT).

Other wait (%) Percentage of waiting for a another productsamples. Calculated as:100*OTHER_STATE_CNT/WLM_SAMPLES_TOT).

Misc wait (%) Percentage of waiting for a unidentified resourcesamples. Calculated as:100*UNIDENT_STATE_CNT/WLM_SAMPLES_TOT).



MVSPM Response Time Breakdown, Hourly Trend reportThis report shows the average transaction response time trend and how thevarious transaction states contribute to it. The sum of the different states adds upto the average execution time. The difference between the response time and theexecution time is mainly made up of switch time, for example the time thetransactions spend being routed to another region for processing. This report isavailable when the MVS system is running in goal mode and when the subsystemis CICS or IMS.


Report ID MVSPM71


Source MVSPM_WORKLOAD2_H, MVSPM_WLM_STATE_H

Attributes MVS, Goal_actual, Response, Service_class, Trend, Breakdown,Goal mode, Sysplex

Variables Date, Sysplex name, MVS system ID, Service class, Serv classperiod




Response time(s) The average response time. Calculated as:TRAN_ELAPSED_SEC/TRANSACTIONS.

Reso

nse

time

(se

c)

Time of day

Figure 244. Example of an MVSPM Response Time Breakdown, Hourly Trend report



Execution time(s) The average execution time. Calculated as:TRAN_EXECUTION_SEC/TRANS_EXEC. IfTRANS_EXEC is zero, column TRANSACTIONS isused instead. This calculation is used below tocalculate time spent in each state.

Active Average time spent executing instructions.Calculated as: Executiontime*ACTIVE_STATE_CNT/TOTAL_STATE_CNT.

Ready Average time the program is ready to execute.Calculated as: Executiontime*READY_STATE_CNT/TOTAL_STATE_CNT.

Idle Average time that no work is allowed to run.Calculated as: Executiontime*IDLE_STATE_CNT/TOTAL_STATE_CNT.

Lock wait Average time spent waiting for a lock. Calculatedas: Executiontime*LOOK_STATE_CNT/TOTAL_STATE_CNT.

I/O wait Average time spent waiting for I/O. Calculated as:Executiontime*IO_STATE_CNT/TOTAL_STATE_CNT.

Conv wait Average time spent waiting for conversation.Calculated as: Executiontime*CONV_STATE_CNT/TOTAL_STATE_CNT.

Distr wait Average time spent waiting for distributed requestsamples. Calculated as: Executiontime*DISTR_STATE_CNT/TOTAL_STATE_CNT.

Sess wait Average time spent waiting for a session to beestablish. Calculated as: Execution time*(SES_LOC_STATE_CNT + SES_NET_STATE_CNT +SES_SPC_STATE_CNT) /TOTAL_STATE_CNT.

Timer wait Average time spent waiting for a timer. Calculatedas: Executiontime*TIMER_STATE_CNT/TOTAL_STATE_CNT.

Other wait Average time spent waiting for another product.Calculated as: Executiontime*OTHER_STATE_CNT/TOTAL_STATE_CNT.

Misc wait Average time spent waiting for unidentifiedresource. Calculated as: Executiontime*UNIDENT_STATE_CNT/TOTAL_STATE_CNT.



I/O subsystem performance reportsThe I/O subsystem reports provide information on your channel paths, logicalcontrol units, and storage devices. The reports show overall response times,response time components, and I/O rates. They also report on the effectiveness ofcaching in your I/O subsystem.

MVSPM Channel Path Busy reportThis report shows the average and maximum busy percentage for the most usedchannel paths. If channels are shared between logical partitions in an PR/SMenvironment, the logical partitions share of the busy percentage is also shown. Usethe Maxrows variable to limit the number of elements shown in the chart. Formore information on using this report, refer to the System Performance Feature Guide.


Report ID MVSPM38


Source MVSPM_CHANNEL_H

Attributes MVS, Performance, RMF, Channel



Channel path The channel path ID.

Channel type The type of multiplexer channel.

Channel avg busy The average percentage of time that the channelpath was busy.

Channel path ID/Channel type

6BCNC SHR

6FCNC

73CVC

7ECNC SHR

7ACTC

% busy0 10 20 30 40 50 60 70 80 90

7756

6666

5656

1910

19

Channelavg busy

Part chanavg busy

Channelmax busy

Part chanmax busy

Figure 245. Example of an MVSPM Channel Path Busy report



Part chan avg busy The average percentage of time that the channelpath was busy for the partition.

Channel max busy The maximum percentage of time that the channelpath was busy during an RMF interval.

Part chan max busy The maximum percentage of time that the channelpath was busy for the partition.



MVSPM I/O Rate for LCUs, Hourly Trend reportThis report shows the hourly I/O rate trend for selected DASD or tape controlunits. For more information on using this report, refer to the System PerformanceFeature Guide.


Report ID MVSPM39



Attributes MVS, Performance, RMF, Control unit, Hourly, I/O rate

Variables Date, MVS_system_ID, Period_name, LCU_number_list, Deviceclass




I/Os per second The number of requests served per second by thecontrol unit.

I/Os

per

sec

ond

0

20

40

60

80

100

120

140

Time of day08:

0009:

0010:

0011:

0012:

0013:

0014:

0015:

0016:

00

0B1B112655

Figure 246. Example of an MVSPM I/O Rate for LCUs, Hourly Trend report



MVSPM I/O Response Time for LCUs, Hourly Trend reportThis report shows the hourly I/O response time trend for selected DASD or tapecontrol units. For more information on using this report, refer to the SystemPerformance Feature Guide.


Report ID MVSPM40



Attributes MVS, Performance, RMF, Control unit, Hourly, I/O response

Variables Date, Period_name, MVS_system_ID, LCU_number_list,Device_class




Response time The average response time for the LCU to service arequest, in milliseconds.

I/O response time (msec)

0

10

20

30

40

50

Time of day08:

0009:

0010:

0011:

0012:

0013:

0014:

0015:

0016:

00

0F09192451

Figure 247. Example of an MVSPM I/O Response Time for LCUs, Hourly Trend report



MVSPM I/O Response Time Components for LCUs reportThis report shows the I/O response time components for selected control units.You can limit the number of LCUs in this chart using the Maxrows variable. TheLCUs are sorted in the order of the highest I/O rates first. For more informationon using this report, refer to the System Performance Feature Guide.


Report ID MVSPM41



Attributes MVS, Performance, RMF, Control unit, I/O response

Variables Date, MVS_system_ID, Period_name, LCU_number_list,Device_class, Maxrows


CU name The control unit name.


Disconnect time The average disconnect time per request, inmilliseconds. This is the average time the devicewas disconnected while locating the data on thedevice.

Connect time The average connect time per request, inmilliseconds. This is the time spent passing thedata to or from the device.

Milliseconds

0

5

10

15

20

25

30

35

40

CU name/LCU number

3990-21B

3990-311

3990-326

3990-255

3990-20B

35.4

11.213.6

25.727.9

Disconnecttime

Connecttime

Pendingtime

Queuewait time

Figure 248. Example of an MVSPM I/O Response Time Components for LCUs report



Pending time The average pending time per request, inmilliseconds. This is the average time that arequest waited for the device to be ready. Duringthis time, the device was being used by anapplication on a different system or the path wasbusy.

Queue wait time The average queue wait time, in milliseconds. Thisis the average time spent in the queue waiting forthe UCB. During this time, the device was beingused by an application on the same system.



MVSPM No of Users Waiting for Device, Daily Trend reportThis chart shows the average number of users waiting for a device. You can eitherspecify a list of volume serial names or a mask for group of volumes, such asTSO%. The number of selected volumes for this report must be less than 16(otherwise the chart may be unreadable). Use the Volser_list or Volser_maskvariables to limit the number of volumes shown in the report. For moreinformation on using this report, refer to the System Performance Feature Guide.


Report ID MVSPM42



Attributes MVS, Performance, RMF, DASD, I/O

Variables From_date, To_date, MVS_system_ID, Period_name, Volser_list,Volser_mask




Average number of requests waitingThe average number of applications waiting for thedevice.

Aver

age

numb

er o

f re

ques

ts w

aiti

ng

0.00

0.50

1.00

1.50

2.00

2.50

1999-1

2-07

1999-1

2-08

1999-1

2-09

1999-1

2-10

1999-1

2-11

2.42.5

2.12.3

2.1

DBDC05TSOL05TSO008TSO009TSO010

Figure 249. Example of an MVSPM No of Users Waiting for Device, Daily Trend report



MVSPM I/O Response Time Components, DASD Devicesreport

This report shows the I/O response time components for selected DASD devices.You can select the devices by control unit number, a list of volume serial names, ora group of volumes using global search characters. Use the Maxrows variable tolimit the number of devices shown in the chart. The devices are sorted indescending I/O rate order. For more information on using this report, refer to theSystem Performance Feature Guide.


Report ID MVSPM43



Attributes MVS, Performance, RMF, DASD, I/O response, Worst case

Variables Date, MVS_system_ID, Period_name, LCU_number, Volser_list,Volser_mask, Maxrows


Model name The device unit type. This column is blank if thedevice name cannot be determined.


LCU/Device number The logical control unit number and the devicenumber.

Disconnect time The average disconnect time per request, in

Milliseconds

0

10

20

30

40

50

60

70

Model name - Volser - LCU/Device number

3390-2TSO0081B/22F

3390-2TSO0091B/232

3390-3DBDC0555/904

3390-2TSO0101B/233

3390TSOL0511/148

63.8

40.1

27.4

51.3

39.4

Disconnecttime

Connecttime

Pendingtime

Queuewait time

Figure 250. Example of an MVSPM I/O Response Time Components, DASD Devices report



milliseconds. This is the average time the devicewas disconnected while locating the data on thedevice.






MVSPM I/O Rate for Devices by Workload Type reportThis report shows the I/O rate caused by a specified workload compared to thetotal I/O rate. The devices are sorted in descending I/O rate order caused by theselected workload. Use the Maxrows variable to limit the number of devicesshown in the chart (the chart can show up to 12 devices). For more information onusing this report, refer to the System Performance Feature Guide.


Report ID MVSPM44


Source MVSPM_DEVICE_AP_H, MVSPM_SYSTEM_PVMVSPM_DEVICE_H, MVSPM_DEVICE_AP_PV

Attributes MVS, Performance, DASD, I/O_rate, Workload, Worst_case

Variables Date, MVS_system_ID, Period_name, Workload_type, Maxrows




Workload type The workload type for which data is reported.

Device number/Volser

022FTSO008

0148TSOL05

0232TSO009

0230TSO006

0904DBDC05

I/Os per second0 2 4 6 8 10 12 14 16

7.915.0

7.211.0

5.214.0

4.77.5

4.54.9

WorkloadI/O rate

TotalI/O rate

Figure 251. Example of an MVSPM I/O Rate for Devices by Workload Type report



Workload I/O rate The number of I/O instructions executed persecond for the selected workload type.

Total I/O rate The number of I/O instructions executed persecond for all workload types.



MVSPM I/O Response Time for Device, Hourly Trend reportThis report shows the hourly response time trend for a selected device. You selectthe device either by device number or by volser name. For more information onusing this report, refer to the System Performance Feature Guide.


Report ID MVSPM45



Attributes MVS, Performance, RMF, DASD, I/O response

Variables Date, MVS_system_ID, Period_name, Volser, Device_number





Mill

isec

onds

0

10

20

30

40

50

60

70

80

Time of day08:

0009:

0010:

0011:

0012:

0013:

0014:

0015:

0016:

00

57 55

47

6067 67 70

66

74

Disconnecttime

Connecttime

Pendingtime

Queue waittime

Figure 252. Example of an MVSPM I/O Response Time for Device, Hourly Trend report



MVSPM Cache Hit Rates by CU, Hourly Trend reportThis report shows cache hit rates for selected cache controllers. The cache hit rateis composed of normal cache hits (random reads), sequential cache hits (sequentialreads), DASD fast write hits, and cache fast write hits. When I/O’s are resolved inthe cache, the channel does not disconnect from the device and thus there is nodisconnect time associated with the I/O operation. Having a high percentage ofI/O’s resolved in the cache will lead to lower response times for devices.

This report shows the total cache hit rates for the controllers. If a controller isshared, the data reflects the aggregate rate of all systems accessing this controller.For more information on using this report, refer to the System Performance FeatureGuide.


Report ID MVSPM46


Source MVSPM_CACHE_HV

Attributes MVS, Performance, Trend, Hourly, Cache, DASD, Hit, Rate

Variables Date, MVS_system_ID, Period_name, Subsystem_ID_list

Cache hits per second

0

100

200

300

400

500

600

Time of day00:

0001:

0002:

0003:

0004:

0005:

0006:

0007:

0008:

0009:

0010:

0011:

0012:

0013:

0014:

0015:

0016:

0017:

0018:

0019:

0020:

0021:

0022:

0023:

00

00040014001600250026

Figure 253. Example of an MVSPM Cache Hit Rates by CU, Hourly Trend report





Cache subsystem ID The cache subsystem ID for a 3990 Model 3, or thestorage director ID for a 3880 Model 23 or 13.

Cache resolve rate The number of I/O requests resolved in the cacheper second.



MVSPM DFW Hit Rates by CU, Hourly Trend reportThis report shows the DASD fast write hit rates for selected cache controllers. TheDASD fast write hit rate is a subset of the cache hit rate (see report MVSPM46).This provides insight into when and how many of the write I/O’s are beingresolved successfully in the cache by DASD fast writes. If there is no activity on acontroller, it indicates that either the feature does not exist or DASD fast write isnot turned on.

This report shows the total DASD fast write hit rates for the controllers. If acontroller is shared, the data reflects the aggregate rate of all systems accessing thiscontroller. For more information on using this report, refer to the SystemPerformance Feature Guide.


Report ID MVSPM47





DASD

fas

t wr

ite

hits

per

sec

ond

0

20

40

60

80

100

120

140

Time of day00:

0001:

0002:

0003:

0004:

0005:

0006:

0007:

0008:

0009:

0010:

0011:

0012:

0013:

0014:

0015:

0016:

0017:

0018:

0019:

0020:

0021:

0022:

0023:

00

00040014001600250026

Figure 254. Example of an MVSPM DFW Hit Rates by CU, Hourly Trend






DFW hit rate The number of DASD fast write hits per second.



MVSPM Staging Rates by CU, Hourly Trend reportThis report shows the cache stage rates for selected cache controllers. The cachestage rate is how many of the DASD read and fast write operations are NOT beingsuccessfully resolved in the cache. Data stages are caused when the data is notlocated in the cache. When this occurs, the data must be staged into the cache so itwill be available on a subsequent I/O operation. This I/O stage rate can be causedby an overcommitted cache, an insufficient amount of cache storage, or a badlocality of reference for the data being cached. Compare this report to the reportshowing cache hit rates by CU (MVSPM46). This comparison will help determinethe effectiveness of the cache by showing how many operations were resolved inthe cache as opposed to those that were not.

This report shows the total staging rates for the controllers. If a controller isshared, the data reflects the aggregate rate of all systems accessing this controller.For more information on using this report, refer to the System Performance FeatureGuide.


Report ID MVSPM48





Cach

e st

ages

per

sec

ond

0

5

10

15

20

25

30

35

Time of day00:

0001:

0002:

0003:

0004:

0005:

0006:

0007:

0008:

0009:

0010:

0011:

0012:

0013:

0014:

0015:

0016:

0017:

0018:

0019:

0020:

0021:

0022:

0023:

00

00040014001600250026

Figure 255. Example of an MVSPM Staging Rates by CU, Hourly Trend report






Staging rate The number of all staging operations per second.



MVSPM Overall Effectiveness by CU, Daily Overview reportThis report summarizes the overall effectiveness of the cache subsystem.

This report shows the total DASD resolve rate and cache resolve rate for thecontrollers. If a controller is shared, the data will reflect the aggregate rate of allsystems accessing this controller. For more information on using this report, referto the System Performance Feature Guide.


Report ID MVSPM49






Model The control unit model number of the cachesubsystem.

Cache size The configured subsystem storage, in megabytes.This is the amount of storage that exists in thecache for the subsystem.

SSID The cache subsystem ID for a 3990 Model 3, or thestorage director ID for a 3880 Model 23 or 13.

I/O´s per second

Model / cache size / SSID

184

54

116

56

126

Figure 256. Example of an MVSPM Overall Effectiveness by CU, Daily Overview report



Cache resolve rate All I/O operations that resulted in the data beingresolved in the cache. These include normal andsequential cache hits, DASD fast write (DFW) hits,and cache fast write hits.

DASD resolve rate All I/O operations not satisfied in the cache. Theseinclude staging, DASD fast write retry, inhibit,bypass, non-DFW write through, and operationsfor devices turned off to the cache.



MVSPM Highest Hit Rate Volumes, Daily Overview reportThis report shows the top DASD volumes based on the total cache hit rate acrossall or selected cache controllers. For each volume in the report, the I/O rate foreach type of cache hit operation plus a summary of the cache miss operations areshown. Cache hits include normal and sequential cache hits (read hit rate), DASDfast write hits (DFW hit rate), and cache fast write hits (CFW hit rate). DASDresolve rate denotes the operations where the data is not resolved in the cache. Inaddition, the cache DASD rate value is reported. It represents the I/O rate to thesecondary volume of a duplex pair for volumes using the dual copy option of the3990, or anticipatory destage from cache to DASD so that nonvolatile storage(NVS) can be freed. This latter activity is an asynchronous operation.

This report shows the total hit rate for the volumes. If a controller is shared, thedata reflects the aggregate rate of all systems accessing this controller. Use theMaxrows variable to limit the number of elements shown in the chart. For moreinformation on using this report, refer to the System Performance Feature Guide.


Report ID MVSPM50




Variables Date, MVS_system_ID, Period_name, Subsystem_ID_list, Maxrows

SSID / volser

00250025YCOM04YCOM0400040004YTSO26YTSO2600040004YCIC00YCIC0000040004YIMSP1YIMSP100040004YTSO36YTSO3600140014OPRDB0OPRDB000160016YSPL14YSPL1400040004YTSO38YTSO3800140014OPRDA0OPRDA000260026TST000TST000

I/O´s per second

24

22

21

15

12

11

12

11

11

12

Report: MVSPM50

Figure 257. Example of an MVSPM Highest Hit Rate Volumes, Daily Overview report






Read hit rate The normal and sequential cache hits.

DFW hit rate The DASD fast write hits.

CFW hit rate The cache fast write hits.

DASD resolve rate All I/O operations not satisfied in the cache. Theseinclude staging, DASD fast write retry, inhibit,bypass, non-DFW write thru, and operations fordevices turned off to the cache.

Cache DASD rate The I/O rate to the secondary volume of a duplexpair for volumes using the dual copy option of the3990, or anticipatory destage from cache to DASDso that nonvolatile storage (NVS) can be freed. Thislatter activity is an asynchronous operation.



MVSPM Highest Staging Rate Volumes, Daily Overview reportThis report shows the top DASD volumes based on the staging rate across all orselected cache controllers. For each volume in the report, the I/O rate for each typeof cache miss operation is shown along with cache hits and asynchronousoperations. Use the Maxrows variable to limit the number of elements shown inthe chart.

This report shows the total staging rate for the volumes. If a controller is shared,the data reflects the aggregate rate of all systems accessing this controller. For moreinformation on using this report, refer to the System Performance Feature Guide.


Report ID MVSPM51




Variables Date, MVS_system_ID, Period_name, Subsystem_ID_list, Maxrows




SSID / volser

0026BKP0020004YCIC020026BKP0060024YCOM140004YHKO260025YCOM040004YIMS040008YCOM320004YIMSP10004YIMS03

I/O´s per second

3

10

2

5

5

24

6

6

15

7

Report: MVSPM51

Figure 258. Example of an MVSPM Highest Staging Rate Volumes, Daily Overview report



Staging rate The data not found in the cache. This is accessedfrom DASD along with staging the rest of the trackinto the cache.

DFW retry rate The write operations that would have resulted in aDFW hit; however, nonvolatile storage (NVS) wasoverutilized causing writes to be sent directly toDASD. (DFW retries are also called DFW bypassesor forces).

Write thru rate The write activity for devices not turned on forDFW.

Bypass cache rate The data is accessed from the DASD device even ifthe data is currently in the cache.

Inhibit rate The data is accessed from the cache if in the cache;otherwise, accessed from the DASD device and notmoved into the cache.

Noncached volume rate The I/O activity to devices disabled to cacheoperations.

Cache DASD rate The I/O rate to the secondary volume of a duplexpair for volumes using the dual copy option of the3990, or anticipatory destage from cache to DASDso that nonvolatile storage (NVS) can be freed up.This latter activity is an asynchronous operation.

Cache resolve rate The I/O rate of all I/O operations that resulted inthe data being resolved in the cache. These includenormal and sequential cache hits, DASD fast write(DFW) hits, and cache fast write hits.



MVSPM Cache CU Operations by CU, Daily Overview reportThis report shows how the I/O operations are being satisfied within the cachesubsystem.

This report shows the total rate for the controllers. If a controller is shared, thedata reflects the aggregate rate of all systems accessing this controller.


Report ID MVSPM58






Model The control unit model number of the cachesubsystem.

Cache size The configured subsystem storage, in megabytes.This is the amount of storage that exists in thecache for the subsystem.

SSID The cache subsystem ID for a 3990 Model 3, or thestorage director ID for a 3880 Model 23 or 13.

I/O´s per second

Model / cache size / SSID

187

55

123

58

130

Figure 259. Example of an MVSPM Cache CU Operations by CU, Daily Overview report







DFW retry rate The write operations that would have resulted in aDFW hit; however, nonvolatile storage (NVS) wasoverutilized causing writes to be sent directly toDASD. (DFW retries are also known as DFWbypasses or forces.)

Write thru rate Write activity for devices not turned on for DFW.

Bypass cache rate The data accessed from the DASD device whetheror not the data is currently in the cache.

Inhibit cache rate The data accessed from the cache if in the cache;otherwise, accessed from the DASD device and notmoved into the cache.


Cache DASD rate The I/O rate to the secondary volume of a duplexpair for volumes using the dual copy option of the3990, or anticipatory destage from cache to DASDso that nonvolatile storage (NVS) can be freed up.This latter activity is an asynchronous operation.



MVSPM Cache CU Operations, Hourly Trend reportThis report shows how the I/O operations are being satisfied within the cachesubsystem.

This report show the total rate for the controllers. If a controller is shared, the datawill reflect the aggregate rate of all systems accessing this controller.


Report ID MVSPM59




Variables Date, MVS_system_ID, Period_name, Subsystem_ID







DFW retry rate The write operations that would have resulted in aDFW hit; however, nonvolatile storage (NVS) wasoverutilized causing writes to be sent directly toDASD. (DFW retries are also known as DFWbypasses or forces.)

I/O´s per second

0

100

200

300

400

500

600

Time of day00:

0001:

0002:

0003:

0004:

0005:

0006:

0007:

0008:

0009:

0010:

0011:

0012:

0013:

0014:

0015:

0016:

0017:

0018:

0019:

0020:

0021:

0022:

0023:

00

Read hitRead hitrate

DFW hitDFW hitrate

CFW hitCFW hitrate

StagingStagingrate

DFW retryDFW retryrate

WriteWritethru rate

BypassBypasscache rate

InhibitInhibitcache rate

NoncachedNoncachedvolume rate

CacheCacheDASD rate

Figure 260. Example of an MVSPM Cache CU Operations, Hourly Trend report



Write thru rate The write activity for devices not turned on forDFW.

Bypass cache rate The data accessed from the DASD device whetheror not the data is currently in the cache.

Inhibit cache rate The data accessed from the cache if in the cache;otherwise, accessed from the DASD device and notmoved into the cache.


Cache DASD rate The I/O rate to the secondary volume of a duplexpair for volumes using the dual copy option of the3990, or anticipatory destage from cache to DASDso that nonvolatile storage (NVS) can be freed up.The latter activity is an asynchronous operation.



MVSPM I/O Response Time for Devices by Workload reportThis report shows the response time components for selected devices. The devicesare selected either by workload type or volume, or a combination of the two. Ifyou specify only a workload type, the devices with the highest I/O rate caused bythis workload are selected. However, the response times shown on the chart arethe average for all workloads using this device. Use the Maxrows variable to limitthe number of elements shown in the chart.


Report ID MVSPM53


Source MVSPM_DEVICE_AP_H, MVSPM_DEVICE_HV

Attributes MVS, Performance, DASD, I/O response, Workload

Variables Maxrows, Date, Period_name, MVS_system_ID, Volser_list,Volser_mask, Workload_type





Connect time The average connect time per request, in

Milliseconds

0

10

20

30

40

50

60

70

Device number/Volser022FTSO008

0148TSOL05

0232TSO009

0230TSO006

0904DBDC05

63.8

39.3 40.1

25.0 27.3

Disconnecttime

Connecttime

Pendingtime

Queue waittime

Figure 261. Example of an MVSPM I/O Response Time for Devices by Workload report



milliseconds. This is the time spent passing thedata to or from the device.



Milliseconds The average response time for the device to servicea request, in milliseconds.



MVSPM I/O Rate by Workload on Selected Devices reportThis report shows the I/O rates for the different workloads on selected DASDdevices. You select the devices by a list of volser names, device numbers, or avolser mask.


Report ID MVSPM54


Source MVSPM_DEVICE_AP_HV, MVSPM_DEVICE_H

Attributes MVS, Performance, DASD, I/O rate, Workload

Variables Date, MVS_system_ID, Period_name, Volser_list, Volser_mask,Device_number_list



Volser The volume serial of the volume mounted on thedevice.

Workload type The workload types that used the devices.

I/Os per second The number of requests serviced by the device persecond.

I/Os

per

sec

ond

0

2

4

6

8

10

12

14

16

Device number/Volser0148TSOL05

022FTSO008

0232TSO009

0233TSO010

0904DBDC05

11.5

14.913.7

7.5

4.9 BATCHCICSSTCTSO

Figure 262. Example of an MVSPM I/O Rate by Workload on Selected Devices report



MVSPM XCF Statistics by System, Overview reportThis report shows the outbound message traffic statistics for systems in an XCFcomplex.


Report ID MVSPM37


Source MVSPM_XCF_SYS_HV

Attributes MVS, Performance, RMF, CPU, XCF, SYSPLEX, Overview



Outbound from-to system The names of the local system and the system atthe other end.

Transport class The transport class name.

Message rate (/sec) The total number of messages sent or received persecond.

Messages big (%) The number of big-message conditions, as apercentage of the total number of messages. This iszero for the inbound direction.

Messages fit (%) The number of message-fit conditions, as apercentage of the total number of messages. This iszero for the inbound direction.

Messages small (%) The number of small-message conditions, as apercentage of the total number of messages. This iszero for the inbound direction.

Messages degraded (%) The number of big messages that exceeded themessage length for which XCF was optimized, as apercentage of the total number of big messages.This is zero for the inbound direction.

Signal paths The number of signalling paths currently inservice.

MVSPM XCF Statistics by System, OverviewSystem ID: MVS_SYSTEM_ID Date: ’1999-12-29’

Period: ’PRIME’

Message Messages Messages Messages Messages No No Buffer MessageOutbound Transport rate big fit small degraded Signal buffer path space length

From-to system class (/sec) (%) (%) (%) (%) paths condition condition (KB) (bytes)-------------- --------- ------- -------- -------- -------- -------- ------ --------- --------- ------ -------SYSA -SYSB DEFAULT 81 0 0 100 0 4 0 0 5120 5120

------- -------- -------- -------- -------- ------ --------- --------- ------ -------* 81 0 0 100 0 4 0 0 5120 5120

------- -------- -------- -------- -------- ------ --------- --------- ------ -------** 81 0 0 100 0 4 0 0 5120 5120

SYSB -SYSA DEFAULT 81 0 0 100 0 4 0 0 5120 5120------- -------- -------- -------- -------- ------ --------- --------- ------ -------

* 81 0 0 100 0 4 0 0 5120 5120------- -------- -------- -------- -------- ------ --------- --------- ------ -------

** 81 0 0 100 0 4 0 0 5120 5120


Figure 263. Example of an MVSPM XCF Statistics by System, Overview report



No buffer condition The number of no buffer conditions for thetransport class.

No path condition The number of no path conditions for the transportclass.

Buffer space (KB) The average maximum number of 1K-blocks ofmessage buffer space.

Message length (bytes) The message length for the transport class, inbytes.



MVSPM XCF Signal Rates, Hourly Trend reportThis report shows the XCF inbound or outbound signal rate trend. You can use itto show the rates for a selected group, a selected member, or both, or the totalrates by system. Specify:

DIRECTION = IN to select INBOUND traffic

DIRECTION = OUT to select OUTBOUND traffic


Report ID MVSPM56


Source MVSPM_XCF_MEMBER_H

Attributes MVS, Performance, RMF, CPU, XCF, Sysplex, Hourly

Variables Date, MVS_system_ID, Period_name, Member_group, Member,Direction




Local system --> other system The names of the local system and where themember resides.

Signals per second The number of signals sent and received persecond. Calculated as: the sum of (SIGNALS_SENT/ MEASURED_SEC) or the sum of(SIGNALS_RECEIVED / MEASURED_SEC).

Signals per second

0

50

100

150

200

250

Time of day08:

0009:

0010:

0011:

0012:

0013:

0014:

0015:

0016:

00

SYSA ->SYSBSYSA ->SYSCSYSA ->SYSD

Figure 264. Example of an MVSPM XCF Signal Rates, Hourly Trend report



||

||

MVSPM XCF Activity by Path and System, Overview reportThis report shows the XCF outbound signal statistics by path, transport class, andsystem.


Report ID MVSPM57


Source MVSPM_XCF_PATH_HV

Attributes MVS, Performance, RMF, CPU, XCF, Path, Sysplex, Overview



Outbound from-to system The names of the local system and the system atthe other end. If the other system is unknown, thisarea is blank.

Transport class The transport class name. This is blank for aninbound path.

Path from-to device number The local device number and the number of thedevice at the other end. If the device number of thesystem at the other end is unknown, this area isblank.

Structure name The name of the coupling facility structure.

Signal rate (/sec) The number of XCF signals sent or received persecond.

Times busy (%) The percentage of times the signalling path wasbusy when it was selected to transfer a message.

Times not busy (%) The percentage of times the signalling path wasnot busy when it was selected to transfer amessage.

MVSPM XCF Activity by Path and System, OverviewSystem: ’MVS1’ Date: 2000-02-02

Period: ’PRIME’

Path Timesfrom-to Signal Times not Buffer

Outbound Transpor device Structure rate busy busy Signals spacefrom-to system class number name (/sec) (%) (%) pending (KB)----------------- -------- --------- ---------------- ------ ------ ------ --------- ------C80 -CA0 DEFAULT - IXCPLEX_PATH1 79 65.8 34.2 3102 500

- IXCPLEX_PATH2 76 67.2 32.8 3102 50006BE-06BE 2 48.1 51.9 874 500

------ ------ ------ --------- ------* 158 60.3 39.7 7078 500

TCGRS 069E-069E 5 0.0 100.0 30 500------ ------ ------ --------- ------

* 5 0.0 100.0 30 500

------ ------ ------ --------- ------** 163 36.2 43.8 7108 400


Figure 265. Example of an MVSPM XCF Activity by Path and System, Overview report



Signals pending The total number of signals pending.

Buffer space (KB) The average maximum number of 1K-blocks ofmessage buffer space.



MVSPM Data Set Activity, Overview reportThis report shows some of the most important measurements for the most useddata sets for a selected workload type. The table is sorted by DASD MPL indescending order. This report is used to identify the most critical data set for aparticular workload. This report requires a variable, PERIOD_HOURS, as input.(The variable represents the number of hours expressed as an integer.) It is neededbecause the SMF records are written only when the data set is active, but thelength of the reported period is needed in order to calculate the rates correctly. Usethe Maxrows variable to limit the number of elements shown in the chart.


Report ID MVSPM80

Report group MVS performance management reports MVS PerformanceManagement Reports

Source MVSPM_DATASET_HV

Attributes MVS, Performance, Response_time, Daily, Overview, Dataset,Workload

Variables Date, MVS system ID, Workload type, Period name, Period hours,Maxrows



Dataset name The data set name.

Dataset type The data set type.

DASD mpl The data set multiprogramming level. Calculatedas: RESPONSE_AVG_MSEC*IO_COUNT/PERIOD_HOURS*3 600 000.

I/O-rate (/sec) The data set I/O rate. Calculated as:IO_COUNT/PERIOD_HOURS*3 600 000.

MVSPM Data Set Activity, OverviewSystem: ’MVS1’ Workload: ’OTHER ’

Date: ’2000-02-02’ Period: ’NIGHT ’

Dataset DASD I/O-rate Response Que wait Connect Disconn Pending Busy Cache hitsDataset name type mpl (/sec) (ms) (ms) (ms) (ms) (ms) (%) (/sec)------------------------ ------- ------ -------- -------- -------- ------- ------- ------- ----- ----------SYSPLEX2.T235900.BOAF23V PHY_SEQ 0.0052 0.010 52.9 18.0 1.4 0.0 33.5 0.0 0.010SYSPLEX2.T235900.BOAF23V OTHER 0.0038 0.013 28.2 20.5 1.5 0.0 6.2 0.0 0.013SYSPLEX2.T235720.TBLF23V OTHER 0.0033 0.009 36.1 26.7 1.5 0.0 7.8 0.0 0.009SYSPLEX.COUPLE00 EXCP 0.0025 0.005 53.0 32.5 16.0 4.4 0.1 0.0 0.000SYSPLEX.COUPLE10 EXCP 0.0023 0.005 50.2 29.2 18.2 2.7 0.1 0.0 0.000

====== ======== ======== ======== ======= ======= ======= ====== =========0.0014 0.004 37.2 23.4 6.3 6.2 1.3 0.0 0.003


Figure 266. Example of an MVSPM Data Set Activity Overview report



Response (ms) The average response time. Calculated as:SUM(RESPONSE_AVG_MSEC*IO_COUNT)/SUM(IO_COUNT).

Que wait (ms) The average queue time. Calculated as:SUM(QUE_WAIT_AVG_MSEC*IO_COUNT)/SUM(IO_COUNT).

Connect (ms) The average connect time. Calculated as:SUM(CONNECT_AVG_MSEC*IO_COUNT)/SUM(IO_COUNT).

Disconn (ms) The disconnect time. Calculated as:SUM(DISCONN_AVG_MSEC*IO_COUNT)/SUM(IO_COUNT).

Pending (ms) The pending time. Calculated as:SUM(PENDING_AVG_MSEC*IO_COUNT)/SUM(IO_COUNT).

Busy (%) The data set busy percentage. Calculated as:SUM((CONNECT_AVG_MSEC+DISCONN_AVG_MSEC) *IO_COUNT)/ PERIOD_HOURS*3 600 000.

Cache hit (/sec) The cache hit rate. Calculated as:SUM(CACHE_HITS)/PERIOD_HOURS*36 000).

DASD acc (/sec) The DASD access rate. Calculated as:SUM(IO_COUNT-CACHE_HITS)/PERIOD_HOURS*36 000).

Hit rate (%) The overall cache hit percentage. Calculated as:100*CACHE_HITS/IO_COUNT.

Cache hits (%) The cache hit percentage (of cache candidates).Calculated as:100*CACHE_HITS/CACHE_CANDIDATE.



MVSPM Data Set I/O Rate & Resp Time, Hourly Trend reportThis report shows the data set response time components and I/O rate by hour ofthe day.


Report ID MVSPM81



Attributes MVS, Performance, Dataset, Response_time, I/O_rate, Trend

Variables Date, MVS system ID, Dataset name




Data set The data set name.

I/O rate The data set I/O rate. Calculated as the sum ofIO_RATE.

Disconnect time The average disconnect time. Calculated as theaverage of DISCONN_AVG_MSEC.

Connect time The average connect time. Calculated as theaverage of CONNECT_AVG_MSEC.

Pending time The average pending time. Calculated as theaverage of PENDING_AVG_MSEC.

Mill

isec

onds

I/Os

per

sec

ond

0

2

4

6

8

10

12

14

16

Time of day01:

0002:

0003:

0004:

0005:

0006:

0007:

0008:

0009:

0010:

0011:

0012:

0013:

0014:

0015:

0016:

0016:

0017:

0017:

0018:

0018:

00

10 10 10 1112 12 12

13 14 14 14

1314 14

13

1111

10

I/O rate

Disconnecttime

Connecttime

Pendingtime

Queue waittime

Figure 267. Example of an MVSPM Data Set I/O Rate & Resp Time, Hourly Trend report



Queue wait time The average pending time. Calculated as theaverage of QUE_WAIT_AVG_MSEC.



MVSPM Data Set I/O Rate Profile, Hourly Trend reportThis report shows the hourly I/O rate trend over several days for a selected dataset. This report is useful in order to understand the access pattern for a data sets.


Report ID MVSPM82



Attributes MVS, Performance, Dataset, Profile, I/O_rate, Trend

Variables From date, To date, MVS system ID, Dataset name




I/Os per second. This is the I/O rate for the data set. Calculated asthe sum of I/O_RATE.

I/Os per second

0

2

4

6

8

10

Time of day01:

0002:

0003:

0004:

0005:

0006:

0007:

0008:

0009:

0010:

0011:

0012:

0013:

0014:

0015:

0016:

0017:

00

2000-02-022000-02-032000-02-04

Figure 268. Example of an MVSPM Data Set I/O Rate Profile, Hourly Trend report



MVSPM Data Set Resp Time Profile, Hourly Trend reportThis report shows the hourly I/O response time trend over several days for aselected data set. This report makes it easy to spot unexpected variations in theresponse time for a data sets.


Report ID MVSPM83


Source MVSPM_DATASET_H

Attributes MVS, Performance, Dataset, Profile, Response_time, Trend

Variables From date, To date, MVS system ID, Dataset name




I/O response time. The average I/O response time.(RESPONSE_AVG_MSEC*IO_COUNT)/IO_COUNT.

I/O

resp

onse

tim

e (m

sec)

0

10

20

30

40

50

Time of day01:

0002:

0003:

0004:

0005:

0006:

0007:

0008:

0009:

0010:

0011:

0012:

0013:

0014:

0015:

0016:

0017:

00

2000-02-022000-02-032000-02-04

Figure 269. Example of an MVSPM Data Set Resp Time Profile, Hourly Trend report



MVSPM Storage Class Resp Time, Hourly Trend reportThis report shows the average hourly response time trend for storage classes.


Report ID MVSPM84


Source MVSPM_STORCLASS_H

Attributes MVS, Performance, Storage_class, Response_time, Trend

Variables Date, MVS system ID, Storage class





Response time The average storage class I/O response time.Calculated as:RESPONSE_AVG_MSEC*IO_COUNT/IO_COUNT.

I/O response time (msec)

0

10

20

30

40

50

Time of day01:

0002:

0003:

0004:

0005:

0006:

0007:

0008:

0009:

0010:

0011:

0012:

0013:

0014:

0015:

0016:

0017:

00

CICSSCTEMPSTSO4

Figure 270. Example of an MVSPM Storage Class Resp Time, Hourly Trend report



MVSPM Storage Class I/O Rate, Hourly Trend reportThis report shows the average hourly I/O rate trend for storage classes.


Report ID MVSPM85


Source MVSPM_STORCLASS_HV

Attributes MVS, Performance, Storage_class, I/O_rate, Trend

Variables Date, MVS system ID, Storage class





I/O rate The average storage class I/O rate. Calculated asthe sum of IO_RATE.

I/Os per second

0

100

200

300

400

500

600

Time of day01:

0002:

0003:

0004:

0005:

0006:

0007:

0008:

0009:

0010:

0011:

0012:

0013:

0014:

0015:

0016:

0017:

00

CICSSCTEMPSTSO4

Figure 271. Example of an MVSPM Storage Class I/O Rate, Hourly Trend report



MVSPM Volume Activity by Storage Class, Overview reportThis report shows shows some of most important I/O statistics for volume ofstorage class VTOC (data and index) and VVDS. Use the Maxrows variable to limitthe number of elements shown in the chart.


Report ID MVSPM98


Source MVSPM_VOLUME_H

Attributes MVS, Performance, Response_time, Daily, Overview, Volume




Volume The volume name.


I/O rate (/sec) The volume I/O rate. Calculated as:SUM(IO_DATA_COUNT) + SUM(IO_IX_COUNT)+ SUM(IO_VVDS_COUNT) /(TIME_RESOLUTION*60).

MVSPM Volume Activity by Storage Class, OverviewSystem: ’ES88’ Period: ’PRIME’

Date: ’2000-03-07’

Device I/O-rate Response Connect Disconn PendingVolume number (/sec) (ms) (ms) (ms) (ms)------ ------ -------- -------- -------- -------- --------DSK27A 256 0.218 3.860 1.923 0.000 0.256DSK27B 257 0.050 0.000 0.000 0.000 0.000DSK27D 259 0.070 4.122 1.938 0.000 0.261DSK27P 260 0.764 8.275 3.949 0.133 0.384NPM00A 262 0.030 66.678 61.515 1.884 2.111NPM00B 263 0.054 4.957 2.571 0.488 0.258NPM00C 264 0.013 7.892 3.242 0.000 0.256OE27S1 261 0.000 0.000 0.000 0.000 0.000PP1MVS 278 0.000 0.000 0.000 0.000 0.000PP5MVS 277 0.000 0.000 0.000 0.000 0.000

======== ======== ======== ======== ========0.120 9.579 7.514 0.251 0.353

Queue Cache hit Volume(ms) (/sec) acc (/sec)

-------- --------- ----------0.000 0.000 0.2180.000 0.000 0.0500.000 0.000 0.0700.000 0.000 0.7640.000 0.000 0.0300.000 0.000 0.0540.000 0.000 0.0130.000 0.000 0.0000.000 0.000 0.0000.000 0.000 0.000

======== ========= ==========0.000 0.000 0.120


Figure 272. Example of an MVSPM Volume Activity by Storage Class, Overview report



Response (ms) The average response time. Calculated as:SUM(RESPONSE_DATA_AVG*IO_DATA_COUNT)/ SUM(IO_DATA_COUNT) +SUM(RESPONSE_IX_AVG*IO_IX_COUNT) /SUM(IO_IX_COUNT) +SUM(RESPONSE_VVDS_AVG*IO_VVDS_COUNT)/ SUM(IO_VVDS_COUNT)

Connect (ms) The average connect time. Calculated as:SUM(CONNECT_DATA_AVG*IO_DATA_COUNT)/ SUM(IO_DATA_COUNT) +SUM(CONNECT_IX_AVG*IO_IX_COUNT) /SUM(IO_IX_COUNT) +SUM(CONNECT_VVDS_AVG*IO_VVDS_COUNT)/ SUM(IO_VVDS_COUNT)

Disconn (ms) The average disconnect time. Calculated as:SUM(DISCONN_DATA_AVG*IO_DATA_COUNT)/ SUM(IO_DATA_COUNT) +SUM(DISCONN_IX_AVG*IO_IX_COUNT) /SUM(IO_IX_COUNT) +SUM(DISCONN_VVDS_AVG*IO_VVDS_COUNT)/ SUM(IO_VVDS_COUNT)

Pending (ms) The average pending time. Calculated as:SUM(PENDING_DATA_AVG*IO_DATA_COUNT)/ SUM(IO_DATA_COUNT) +SUM(PENDING_IX_AVG*IO_IX_COUNT) /SUM(IO_IX_COUNT) +SUM(PENDING_VVDS_AVG*IO_VVDS_COUNT)/ SUM(IO_VVDS_COUNT)

Queue (ms) The average pending time. Calculated as:SUM(QUEUE_DATA_AVG*IO_DATA_COUNT) /SUM(IO_DATA_COUNT) +SUM(QUEUE_IX_AVG*IO_IX_COUNT) /SUM(IO_IX_COUNT) +SUM(QUEUE_VVDS_AVG*IO_VVDS_COUNT) /SUM(IO_VVDS_COUNT)

Cache hit (/sec) The cache hit rate. Calculated as:SUM(CACHE_HIT_DATA) +SUM(CACHE_HIT_IX) +SUM(CACHE_HIT_VVDS) /(TIME_RESOLUTION*60).

Volume acc (/sec) The volume access rate. Calculated as:(SUM(IO_DATA_COUNT-CACHE_HIT_DATA) +SUM(IO_IX_COUNT-CACHE_HIT_IX) +SUM(IO_VVDS_COUNT-CACHE-HIT_VVDS)) /(TIME_RESOLUTION*60).



MVSPM Channel Path Busy, Extended Mode reportThis report shows channel path measurement data for all channels included inchannel path measurement group 2. Statistics are collected by the Channel PathMeasurement Facility (CPMF).


Report ID MVSPM99


Source MVSPM_CHANNEL_H

Attributes MVS, Performance, RMF, Channel, Extended, CPMF




Channel path The channel path ID.

Channel type The type of multiplexer channel.

Channel busy avg The average percentage of time that the channelpath was busy.

Channel lpar busy avg The average percentage of time that the channelpath was busy for the partition.

MVSPM Channel Path Busy, Extended ModeSystem: ’S57A’ Date: ’2000-03-18’

Period: ’NIGHT’

ChannelChannel Channel lpar Bus Channelpath Channel busy busy cycle busy

Time ID type avg avg avg (max)-------- -------- -------- -------- -------- -------- --------01.00.00 F0 FCV 12.50 0.00 0.00 13

F1 FCV 0.68 0.00 0.00 1F5 FCV 54.82 0.00 0.00 55

02.00.00 F0 FCV 4.81 0.00 0.00 6F1 FCV 1.32 0.00 0.00 1F5 FCV 47.71 0.00 0.00 49

Channellpar Bus Channel Lpar Channel Lparbusy cycle write write read read

(max) (max) (Mb/sec) (Mb/sec) (Mb/sec) (Mb/sec)------- -------- -------- -------- -------- --------

0 32226 0.560 0.132 0.120 0.0150 32226 0.018 0.012 0.009 0.0070 32226 0.000 0.000 0.000 0.0000 32226 0.389 0.330 0.948 0.810

0 32226 0.207 0.122 0.030 0.0140 32226 0.017 0.012 0.009 0.0070 32226 0.000 0.000 0.000 0.0000 32226 0.155 0.093 0.916 0.778


Figure 273. Example of an MVSPM Channel Path Busy, Extended Mode report



Bus cycle avg The average percentage of time that the bus cyclewas busy.

Channel busy (max) The maximum percentage of time that the channelpath was busy during an RMF interval.

Channel lpar busy (max) The maximum percentage of time that the channelpath was busy for the partition during an RMFinterval.

Bus cycle (max) The maximum percentage of time that the buscycle was busy during an RMF interval.

Channel write (Mb/sec) Write data transfer rates from the control unit tothe channel for the entire system. Calculated asCHAN_WRITE_MB_TOT/MEASURED_SEC.

Lpar write (Mb/sec) Write data transfer rates from the control unit tothe channel for this individual logical partition.Calculated asLPAR_WRITE_MB_TOT/MEASURED_SEC.

Channel read (Mb/sec) Read data transfer rates from the control unit tothe channel for the entire system. Calculated asCHAN_READ_MB_TOT/MEASURED_SEC.

Lpar read (Mb/sec) Read data transfer rates from the control unit tothe channel for this individual logical partition.Calculated asLPAR_READ_MB_TOT/MEASURED_SEC.



OpenEdition performance reportsThe Open Edition reports provide details of file system activity, kernel activity, andhierarchical file system (HFS) statistics.

MVSPM OpenEdition HFS Global Statistics reportThis report shows an overview of I/O activity for all hierarchical file systems.


Report ID MVSPM90


Source MVSPM_OMVS_GHFS_H

Attributes MVS, Performance, HFS, OpenEdition, OMVS




Virtual storage used (MB) Virtual storage used in MB.

Fixed storage used (MB) Permanently-fixed storage used in MB.

File I/O Cache Number of pages of a data file that were found invirtual storage (cache).

File I/O Cache rate (/sec) Pages found in cache per second. Calculated asFILE_IO_CACHE/MEASURED_SEC.

MVSPM OpenEdition HFS Global StatisticsSystem: ’ES88’ Period: All

Date: ’2000-01-02’

Virtual Fixed Filestorage storage I/O Cache

used used File I/O rate File I/OTime (MB) (MB) Cache (/sec) DASD

----- -------- -------- ---------- ---------- ----------02.00 2.0 0.0 0 0.000 003.00 6.0 0.0 0 0.000 004.00 4.0 0.0 0 0.000 005.00 2.0 0.0 0 0.000 006.00 4.0 0.0 134 0.037 007.00 4.0 0.0 126 0.035 0

File Metadata MetadataDasd I/O Hit Metadata I/O Cache Metadata DASD I/O Hit

rate ratio I/O rate I/O rate ratio(/sec) (%) Cache (/sec) Dasd (/sec) (%)

---------- ------ ---------- ---------- ---------- ---------- ------0.000 0.0 0 0.000 0 0.000 0.00.000 100.0 0 0.000 0 0.000 0.00.000 0.0 0 0.000 0 0.000 0.00.000 0.0 0 0.000 0 0.000 0.00.000 98.5 13 0.004 2 0.001 86.70.001 98.4 13 0.004 0 0.000 100.0


Figure 274. Example of an MVSPM OpenEdition HFS Global Statistics report



File I/O DASD Number of pages of a data file that were not foundin virtual storage and an I/O was necessary.

File Dasd I/O rate (/sec) Pages not found in cache per second. Calculated asFILE_IO_DASD/MEASURED_SEC.

Hit ratio (%) The percentage of file I/O cache-found requests.Calculated as100*FILE_IO_CACHE/(FILE_IO_CACHE+FILE_IO_DASD)

Metadata I/O Cache Numbers of metadata for a data file that werefound in virtual storage during file lookup.

Metadata I/O Cache rate (/sec)Metadata cached per second. Calculated asMETADATA_IO_CACHE/MEASURED_SEC.

Metadata I/O Dasd Numbers of metadata for a data file that were notfound in virtual storage during file lookup and anindex call was necessary that may result in an I/O.

Metadata I/O DASD rate (/sec)Metadata not cached per second. Calculated asMETADATA_IO_DASD/MEASURED_SEC.

Hit ratio (%) The percentage of metadata cache-found requests.Calculated as 100*METADATA_IO_CACHE/(METADATA_IO_CACHE+METADATA_IO_DASD)



MVSPM OpenEdition HFS Buffer Statistics reportThis report shows an overview of OpenEdition buffer statistics.


Report ID MVSPM91


Source MVSPM_OMVS_BUF_H

Attributes MVS, Performance, HFS, OpenEdition, Buffer, OMVS




Avg. Buffer number Average number of buffers. Calculated asBUFFER_NUMBER/INPUT_RECORDS.

Avg. Buffer pool (MB) Average size of buffer pool in MB. Calculated asBUFF_POOL/INPUT_RECORDS.

Buffer pool fixed (%) Percentage of buffers that are permanently fixed.Calculated as100*BUFF_POOL_FIX/(BUFF_POOL+BUFF_POOL_FIX).

I/O activity Total number of buffers for which I/Os wereissued. Calculated as sum ofBUFF_POOL_IOFIX+BUFF_POOL_IONFIX.

MVSPM OpenEdition HFS Buffer StatisticsSystem: ’ES88’ Period: All

Date: ’2000-01-02’

I/OAvg. Buffer I/O fixed

Avg. Buffer pool fixed bufferBuffer pool fixed I/O buffer pool

Time number (Mb) (%) activity pool (%)-------- ---------- ---------- ------ ---------- ---------- ------02.00.00 30 0.597 0.0 32 0 0.003.00.00 30 0.597 0.0 148 0 0.004.00.00 30 0.597 0.0 100 0 0.005.00.00 30 0.597 0.0 40 0 0.006.00.00 30 0.606 0.0 193 0 0.007.00.00 31 0.662 0.0 553 89 16.1


Figure 275. Example of an MVSPM OpenEdition HFS Buffer Statistics report



I/O fixed buffer pool Total number of times a buffer was already fixedprior to an I/O request.

I/O fixed buffer pool (%) Percentage of fixed I/Os. Calculated as100*BUFF_POOL_IOFIX /(BUFF_POOL_IOFIX+BUFF_POOL_IONFIX).



MVSPM OpenEdition HFS Statistics reportThis report shows an overview of I/O activity and storage usage for a singlehierarchical file system.


Report ID MVSPM92


Source MVSPM_OMVS_HFS_H

Attributes MVS, Performance, HFS, OpenEdition, OMVS




File System Name Name of file system.

File I/O Cache Number of pages requested and found in virtualstorage.

File I/O DASD Number of pages requested that were not found invirtual storage and I/Os were requested.

File I/O Hit (%) Percentage of cache-found requests. Calculated as100*FILE_CACHE)/(FILE_CACHE+FILE_NCACHE).

Metadata I/O Cache Number of times that metadata for a file wasfound in virtual storage during file lookup.

MVSPM OpenEdition HFS StatisticsSystem: ’ES88’ Period: All

Date: ’2000-01-02’

FileFile File I/OI/O I/O Hit

Time File System Name Cache DASD (%)----- ------------------------------ ---------- ---------- --------06.00 OMVS.ROOT 128 2 98.5

OMVS.ETC 6 0 100.0

07.00 OMVS.ROOT 122 2 98.4OMVS.ETC 4 0 100.0

08.00 OMVS.ROOT 6 4 60.0OMVS.ETC 13 3 81.3

Metadata Metadata Metadata Index Index I/OI/O I/O I/O I/O I/O Hit

Cache DASD Hit (%) Cache Dasd (%)---------- ---------- -------- ---------- ---------- --------

12 2 85.7 49 0 100.01 0 100.0 2 0 100.0

12 0 100.0 742 0 100.01 0 100.0 2 0 100.0

16 7 69.6 1082 1 99.92 1 66.7 8 0 100.0


Figure 276. Example of an MVSPM OpenEdition HFS Statistics report



Metadata I/O DASD Number of times that metadata for a file was notfound in virtual storage during file lookup and anindex call was necessary that may result in an I/O.

Metadata I/O Hit (%) Percentage of cache-found requests. Percentage ofcache-found requests. Calculated as100*FILE_LOOKUP_CACHE /(FILE_LOOKUP_CACHE+FILE_LOOKUP_NCACHE).

Index I/O Cache Number of index page read/write hits. Calculatedas the sum of INDEX_READ_HITS +INDEX_WRITE_HITS.

Index I/O DASD Number of index page read/write misses.Calculated as the sum of INDEX_READ_MISSES +INDEX_WRITE_MISSES.

Index I/O Hit (%) Percentage of index page read/write hits.Calculated as 100(INDEX_READ_HITS +INDEX_WRITE_HITS) / (INDEX_READ_HITS +INDEX_WRITE_HITS + INDEX_READ_MISSES +INDEX_WRITE_MISSES).



MVSPM OpenEdition File Statistics reportThis report shows an overview of I/O activity for a single file in a hierarchical filesystem group by MVS system, RACF group , RACF user ID, and jobname.


Report ID MVSPM93


Source MVSPM_OMVS_FILE_H

Attributes MVS, Performance, File, OpenEdition, OMVS


MVSPM OpenEdition File StatisticsSystem: ’ES38’Date: ’1999-09-20’

Mvs Racfsystem Racf user File FileID group ID Jobname type pathname------ -------- -------- -------- ---- ------------------------------ES38 NPM WS1 MDBDC01 2 /dev/ptyp0000

3 /bin/fomtlinp3 /etc/profile3 /u/ws1/.sh_history

MDBDC02 3 /bin/fomtlinc3 /etc/utmpx

MDBDC03 3 /bin/tty

MDBDC04 3 /bin/fomtlout3 /etc/utmpx

TimeFile File ofread write open(KB) (KB) (/sec)

---------- ---------- ----------45.185 0.010 22.817

146.688 0.000 0.4465.272 0.000 0.1010.094 0.007 0.292

143.547 0.000 1.9190.516 0.129 0.955

18.184 0.000 1.778

143.906 0.000 1.8020.258 0.129 0.022


Figure 277. Example of an MVSPM OpenEdition File Statistics report





Racf group The RACF group.


Jobname The job name.

File type The OpenEdition file type.

File pathname The file pathname.

File read (KB) Total number of kilobytes read.

File write (KB) Total number of kilobytes written.

Time of open (/sec) Total time of open in seconds.



MVSPM OpenEdition Kernel System Calls Activity reportThis report shows an overview of OpenEdition system calls activity.


Report ID MVSPM94


Source MVSPM_OMVS_KERN_H

Attributes MVS, Performance, OpenEdition, Kernel, OMVS




System call Total number of OpenEdition system calls.

System call min Minimum number of OpenEdition system callsissued during a cycle of measurement.

System call max Maximum number of OpenEdition system callsissued during a cycle of measurement.

Syscall rate (/sec) Number of OpenEdition system calls per second.Calculated as theSYSTEM_CALL/MEASURED_SEC.

Total CPU (/sec) Total CPU time spent for OpenEdition system calls.

MVSPM OpenEdition Kernel System Calls ActivitySystem: ’ES88’ Period: All

Date: ’2000-01-02’

System System Syscall TotalSystem call call rate cpu

Time call min max (/sec) (/sec)-------- ---------- ------- ------- ------- -------03.00.00 4312 0 24 1.28 0.0504.00.00 2821 0 24 1.28 0.0405.00.00 1967 1 21 2.19 0.0306.00.00 9331 0 311 2.59 0.1107.00.00 6358 0 149 1.77 0.0708.00.00 5981 0 61 1.66 0.0809.00.00 5666 0 18 1.57 0.0610.00.00 5739 0 19 1.59 0.07


Figure 278. Example of an MVSPM OpenEdition Kernel System Calls Activity report



MVSPM OpenEdition Kernel Process Activity reportThis report shows an overview of OpenEdition process activity.


Report ID MVSPM95



Attributes MVS, Performance, OpenEdition, Kernel, OMVS




User Maximum number of OpenEdition users.

Proc Maximum number of OpenEdition processes.

Proc per user Maximum number of OpenEdition processes peruser.

Current user (avg) Average number of OpenEdition users during thetime of measurement.

Current user min Minimum number of OpenEdition users duringone cycle of measurement.

Current user max Maximum number of OpenEdition users duringone cycle of measurement.

MVSPM OpenEdition Kernel Process ActivitySystem: ’ES88’ Period: All

Date: ’2000-01-02’

Proc Current Current Currentper user user user Overrun

Time User Proc user (avg) (min) (max) user-------- ----- ----- ----- ---------- ------- ------- -------03.00.00 50 200 25 1120 1 1 004.00.00 50 200 25 1100 1 1 005.00.00 50 200 25 899 1 1 006.00.00 50 200 25 1799 1 1 007.00.00 50 200 25 1799 1 1 008.00.00 50 200 25 1799 1 1 0

Current CurrentCurrent process process

Current Current Current process per perprocess process process Overrun per user user(avg) (min) (max) process user (min) (max)

---------- ------- ------- ------- ------- ------- -------31370 28 29 0 0 0 030786 28 28 0 0 0 027869 31 31 0 0 0 054978 23 31 0 0 0 053554 23 31 0 0 0 056231 31 34 0 0 0 0


Figure 279. Example of an MVSPM OpenEdition Kernel Process Activity report



Overrun user Total number of times that a Fork/Dub failedbecause the maximum number of OpenEditionusers was exceeded.

Current process (avg) Average number of OpenEdition processes duringthe time of measurement.

Current process min Minimum number of OpenEdition processesduring one cycle of measurement.

Current process max Maximum number of OpenEdition processesduring one cycle of measurement.

Overrun process Total number of times that a Fork/Dub failedbecause the maximum number of OpenEditionprocesses was exceeded.

Current process per user Total number of OpenEdition processes per user.

Current process per user min Minimum number of OpenEdition processes peruser during one cycle of measurement.

Current process per user max Maximum number of OpenEdition processes peruser during one cycle of measurement.



MVSPM OpenEdition Kernel Process Communication reportThis report shows an overview of OpenEdition interprocess communication.


Report ID MVSPM96



Attributes MVS, Performance, HFS, OpenEdition, Kernel, OMVS




Msgqueue (avg) Average number of message queue IDs during thetime of measurement. Calculated asMSGQUEUE_TOTAL/INPUT_RECORDS.

Semaphore ID (avg) Average number of semaphore IDs during the timeof measurement. Calculated asSEMAPH_TOTAL/INPUT_RECORDS.

Shared memory ID (avg) Average number of shared memory IDs during thetime of measurement. Calculated asSHRMID_TOTAL/INPUT_RECORDS.

Shared memory pages (avg) Average number of shared memory pages duringthe time of measurement. Calculated asSHRMPG_TOTAL/INPUT_RECORDS.

Msgqueue overruns (/sec) Number of attempts per second to exceedmaximum number of message queue IDs.

MVSPM OpenEdition Kernel Process CommunicationSystem: ’ES88’ Period: All

Date: ’2000-01-02’

Shared SharedSemaphore memory memory

Msgqueue ID ID pagesTime (avg) (avg) (avg) (avg)

-------- ------------ ------------ ------------ ------------03.00.00 1140525910 2344 89420 3746004.00.00 1137709440 2678 93720 2247005.00.00 1142001410 39 4320 1978006.00.00 1143153410 450 670 2380

Semaphore Shared SharedMsgqueue ID memory ID memoryoverruns overruns overruns overruns(/sec) (/sec) (/sec) (avg)

--------- ---------- ---------- ----------33.0 0.0 0.0 0.00047.0 0.0 0.0 0.00032.0 0.0 0.0 0.000

170.0 0.0 0.0 0.000


Figure 280. Example of an MVSPM OpenEdition Kernel Process Communication report



Calculated asMSGQUEUE_EXCEED/MEASURED_SEC.

Semaphore ID overruns (/sec) Number of attempts per second to exceedmaximum number of semaphore IDs. Calculated asSEMAPH_EXCEED/MEASURED_SEC.

Shared memory ID overruns (/sec)Number of attempts per second to exceedmaximum number of shared memory IDs.Calculated asSHRMID_EXCEED/MEASURED_SEC.

Shared memory overruns (avg)Number of attempts per second to exceedmaximum number of shared memory pages.Calculated asSHRMPG_EXCEED/MEASURED_SEC.



MVSPM OpenEdition Kernel Memory Statistics reportThis report shows an overview of OpenEdition storage usage.


Report ID MVSPM97



Attributes MVS, Performance, HFS, OpenEdition, Kernel, OMVS





Memory map (max Mb) Maximum amount of data space storage in MB thatcan be allocated for memory mappings of HFS filesas defined by the MAXMMAPAREA parameter.

Memory map used (avg Mb) Average amount of data space storage in MB.Calculated asMMAPPG_TOTAL/INPUT_RECORDS.

Memory map overrun (avg) Average number of attempts to exceed data spacestorage. Calculated asMMAPPG_EXCEED/INPUT_RECORDS.

Shared storage (max Mb) Maximum amount of shared storage pages that canbe concurrently in use as defined in theMAXSHAREPAGES parameter. Shared storagepages use ESQA storage.

MVSPM OpenEdition Kernel Memory StatisticsSystem: ’ES88’ Period: All

Date: ’2000-01-02’

Memory map Memory mapMemory map used overrun

Date Time (max Mb) (avg Mb) (avg)---------- -------- ---------- -------------- ----------2000-01-02 03.00.00 16 0.000 02000-01-02 04.00.00 16 0.000 02000-01-02 05.00.00 16 0.000 02000-01-02 06.00.00 16 0.000 0

0

Shared SharedShared storage storage

storage used overrun(max Mb) (avg Mb) (avg)

---------- -------------- ----------512 4584483.490 0512 4573488.000 0512 4591628.710 0512 4595741.990 0


Figure 281. Example of an MVSPM OpenEdition Kernel Memory Statistics report



Shared storage used (avg Mb)Average amount of shared storage pages in MB.Calculated as SHRSPG_TOTAL/INPUT_RECORDS.

Shared storage overrun (avg) Average number of attempts to exceed sharedstorage page. Calculated asSHRSPG_EXCEED/INPUT_RECORDS.



Part 9. Appendixes

933

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 inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user’s responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

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

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

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

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

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION ″AS IS″ WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certaintransactions, therefore, this statement might not apply to you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.

935

IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

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

IBM Corporation2Z4A/10111400 Burnet RoadAustin, TX 78758U.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 document and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

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

COPYRIGHT LICENSE:

This information contains sample application programs in source language, whichillustrate programming techniques on various operating platforms. You may copy,modify, and distribute these sample programs in any form without payment toIBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operatingplatform for which the sample programs are written. These examples have notbeen thoroughly tested under all conditions. IBM, therefore, cannot guarantee orimply reliability, serviceability, or function of these programs. You may copy,modify, and distribute these sample programs in any form without payment toIBM for the purposes of developing, using, marketing, or distributing applicationprograms conforming to IBM’s application programming interfaces.

Each copy or any portion of these sample programs or any derivative work, mustinclude a copyright notice as follows:

© (your company name) (year). Portions of this code derived from IBM Corp.Sample Programs. © Copyright IBM Corp. _enter the year or years_. All rightsreserved.

If you are viewing this information in softcopy form, the photographs and colorillustrations might not appear.


TrademarksDB2, DB2 Universal Database, IBM, the IBM logo, Tivoli, Tivoli Enterprise, TivoliEnterprise Console, AIX, AS/400, CICS, DFSMS/MVS, DFSMShsm, DFSMSdfp,DFSMSdss, DRDA, ESCON, ES/9000, IMS, MVS, MVS/DFP, MVS/XA, FICON,MQseries, Netview, OpenEdition, OS/390, PR/SM, Print Services, Facility,Printway, QMF, RAMAC, RACF, RMF, SF, TME, VTAM, VM/ESA, WebSphere,3090 and z/OS are trademarks or registered trademarks of International BusinessMachines Corporation in the United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks ofMicrosoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and othercountries.

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

Notices 937

List of abbreviations

These abbreviations appear in this book:

AP Assist Processor

APPC advanced program-to-program communications

APPC/MVS advanced program-to-program communications/Multiple VirtualStorage

APPC/VM advanced program-to-program communications/Virtual Machine

APPL application

APPN Advanced peer to peer networking.

ASCH APPC/MVS scheduler

BCDS backup control data set

BMF Buffer Manager Facility

BP buffer pool

BSAM basic sequential access method

BSDS bootstrap data set

CAF DB2 call attachment facility

CAM Cryptographic Asynchronous Message

CF Coupling Facility

CFW cache fast write

C/I converter/interpreter

CICS Customer Information Control System

CP Control Program

CPC Central Processor Complex

CPI_C Common program interface for communications

CPMB channel path measurement block

CPMF channel path measurement facility

CPU central processing unit

CS central storage

CSA common system area

CT cursor table

CTC channel-to-channel

CVC converter channel

DASD direct access storage device

DBAT database access thread

DBD database descriptors

939

||

||

||

||

||

||

DB2 DATABASE 2

DCOLLECT DFP Data Collection Facility

DDF data dictionary facilities or distributed data facility

DDL data definition language

DES Data Encryption Standard

DFHSM Data Facility Hierarchical Storage Manager

DFP Data Facility Product

DFSMS Data Facility Storage Management Subsystem

DFW DASD fast write

DIV data-in-virtual

DML data manipulation language

DMTH data management threshold

DRDA Distributed Relational Data Architecture

DSCB data set control block

DSN data set name

DWQT deferred write threshold

EBCDIC extended binary coded decimal interchange code

EDM environmental description manager

ENQ enqueued exchange resources

EREP Environmental Record and Editing Printing

ES expanded storage

EXCP execute channel program

GMT Greenwich mean time

ICF integrated control facility

ID identifier

IFCID instrumentation facility component ID

IMS Information Management System

I/O input/output

IOS I/O supervisor

IPL initial program load

IPS installation performance specifications

IRLM IMS resource lock manager

ISPF Interactive System Productivity Facility

JCL job control language

JES job entry subsystem

LCU logical control unit

LLA library lookaside


||

LOGREC logout recorder

LPA link pack area

LPAR logical partition

LSQA local system queue area

LU logical unit

MAC Message Authentication Codes

MAXVIRT maximum virtual storage

MCDS migration control data set

MPL multiprogramming level

MS main storage

MSS mass storage subsystem

MVS Multiple Virtual Storage

MVS/DFP Multiple Virtual Storage/Data Facility Product

MVS/ESA Multiple Virtual Storage/Enterprise System Architecture

MVS/XA Multiple Virtual Storage/Extended Architecture

NPM/IP NetView Performance Monitor for IP

NVS nonvolatile storage

OAM Object Access Method

OPC Operations Planning and Control

OPC Operations Planning and Control

OTMA Open transaction manager access

PA private area

PAV Parallel Access Volumes

PDSE partitioned data set extended

PG performance group

PGN performance group number

PIN Personal Identification Number

PLPA pageable link pack area

PR/SM Processor Resource/Systems Manager™

PSF Print Services Facility

PT package table

QMF Query Management Facility

RACF Resource Access Control Facility

RCT region control task

RMF Resource Management Facility

SC service class or storage class

SIO start I/O

List of abbreviations 941

||

||

||

||

||

SKCT skeleton cursor table

SKPT skeleton package table

SMF system management facilities

SMS system-managed storage

SPTH sequential prefetch threshold

SQ Shared queue IMS

SQA system queue area

SQL Structured Query Language

SRB service request block

SRM System Resources Manager

SSCH start subchannel

SSI subsystem interface

STC started task

STCP store channel path status

SYSLOG system log

TCB task control block

TP transaction program

TSO Time Sharing Option

TSO/E Time Sharing Option Extensions

TVC Tape Volume Cache

TWS Tivoli Workload Scheduler

UADS user attribute data set

UCB unit control block

UIC unreferenced interval count

UR unit record

VA vector affinity

VDWQT vertical deferred write threshold

VF vector facility

VIO virtual input/output

VIR VTOC index records

VLF Virtual Lookaside Facility

VM Virtual Machine

VM/ESA Virtual Machine/Enterprise System Architecture

VM/XA Virtual Machine/Extended Architecture

VMPRF VM Performance Reporting Facility

VOLSER volume serial

VS virtual storage


||

||

||

VSAM virtual storage access method

VTAM virtual telecommunications access method

VTOC volume table of contents

VTS Virtual Tape Server

VU vector usage

XCF Cross-System Coupling Facility

WLM Workload Manager

List of abbreviations 943

||

||

Glossary

Aadministration. A Tivoli Decision Support for OS/390task that includes maintaining the database, updatingenvironment information, and ensuring the accuracy ofdata collected.

administration dialog. A set of host windows used toadminister Tivoli Decision Support for OS/390.

Ccollect. A process used by Tivoli Decision Support forOS/390 to read data from input log data sets, interpretrecords in the data set, and store the data in DB2 tablesin the Tivoli Decision Support for OS/390 database.

compatibility mode. A mode of processing, in whichthe IEAIPSxx and IEAICSxx members ofSYS1.PARMLIB determine system resourcemanagement. For more information about MVSWorkload Manager, refer to MVS/ESA Planning:Workload Management

component. An optionally installable part of a TivoliDecision Support for OS/390 feature.

control table. A predefined Tivoli Decision Supportfor OS/390 table that controls results returned by somelog collector functions.

Ddata table. A Tivoli Decision Support for OS/390 tablethat contains performance data used to create reports.

DFHSM. In this book, DFHSM is referred to by itsnew product name. See DFSMShsm.

DFSMShsm. Data Facility Storage ManagementSubsystem hierarchical storage management facility. Afunctional component of DFSMS/MVS used to back upand recover data, and manage space on volumes in thestorage hierarchy.

DFSMS/MVS. Data Facility Storage ManagementSubsystem/MVS. An IBM licensed program thatconsists of DFSMSdfp™, DFSMSdss™, and DFSMShsm.

Eenvironment information. All of the information thatis added to the log data to create reports. Thisinformation can include data such as performancegroups, shift periods, installation definitions, and so on.

Ggoal mode. A mode of processing where the activeservice policy determines system resource management.For more information about MVS Workload Manager,refer to MVS/ESA Planning: Workload Management

Hhost. The MVS system where Tivoli Decision Supportfor OS/390 runs collect and where the Tivoli DecisionSupport for OS/390 database is installed.

Kkey columns. The columns of a DB2 table thattogether constitute the key.

Llog collector. A Tivoli Decision Support for OS/390program that processes log data sets and providesother Tivoli Decision Support for OS/390 services.

log data set. Any sequential data set that is used asinput to Tivoli Decision Support for OS/390.

log definition. The description of a log data setprocessed by the log collector.

log procedure. A program module that is used toprocess all record types in certain log data sets.

lookup table. A Tivoli Decision Support for OS/390DB2 table that contains grouping, conversion, orsubstitution information.

PTivoli Decision Support for OS/390 database. A set ofDB2 tables that includes data tables, lookup tables,system tables, and control tables.

Rrecord definition. The description of a record typecontained in the log data sets used by Tivoli DecisionSupport for OS/390, including detailed record layoutand data formats.

record procedure. A program module that is called toprocess some types of log records.

945

record type. The classification of records in a log dataset.

report group. A collection of Tivoli Decision Supportfor OS/390 reports that can be referred to by a singlename.

reporting dialog. A set of host or workstationwindows used to request reports.

resource group. A collection of network resources thatare identified as belonging to a particular departmentor division. Resources are organized into groups toreflect the structure of an organization.

Ssection. A structure within a record that contains oneor more fields and may contain other sections.

service class. A group of work which has the sameperformance goals, resource requirements, or businessimportance. For workload management, you assign aservice goal and optionally a resource group, to aservice class. For more information about MVSWorkload Manager, refer to MVS/ESA Planning:Workload Management

source. In an update definition, the record or DB2table that contains the data used to update a TivoliDecision Support for OS/390 DB2 table.

sysplex. A set of MVS systems communicating andcooperating with each other through certainmultisystem hardware components and softwareservices to process customer workloads.

system table. A DB2 table that stores information thatcontrols log collector processing, Tivoli DecisionSupport for OS/390 dialogs, and reporting.

Ttarget. In an update definition, the DB2 table in whichTivoli Decision Support for OS/390 stores data fromthe source record or table.

threshold. The maximum or minimum acceptablelevel of usage. Usage measurements are compared withthreshold levels.

Uupdate definition. Instructions for entering data intoDB2 tables from records of different types or from otherDB2 tables.

Vview. An alternative representation of data from oneor more tables. A view can include all or some of thecolumns contained in the table on which it is defined.


Index

Aabend code conversion 397accessibility xivactive data sets 201, 203, 268, 269address spaces 195, 306

Bbackup statistics 195, 197books

feedback xiionline xiiordering xii

Ccustomer support xivcustomization

DB2 componentmake input data available 45update lookup tables 46

DFSMS componentmake input data available 185,

259, 260update lookup tables 186, 261

MVS analysis componentmake input data available 287update lookup tables 287

MVS performance managementcomponent

make input data available 581update lookup tables 584

DDASD planned capacity 215DASD volume utilization 199, 200DASD volumes, statistics 209, 270data flow

DB2 component 47description 15DFSMS component

lookup tables 191, 263record procedure 194

MVS analysis componentlookup tables 295


lookup tables 591record procedure 300, 599

data sets, active 201, 203, 268, 269data sets, grouping 212, 275data tables

DB2 componentDB2_APPL_DIST_H, _W 29, 51DB2_APPLICATION_H, _W 52DB2_BP_SHARING_T 53DB2_BPATTR_SHR_T 56DB2_BUFFER_POOL_T 58

data tables (continued)DB2 component (continued)

DB2_DATABASE_T 63DB2_LOCK_SHARING_T 73DB2_PACKAGE_H, _D, _W 75DB2_SHARING_INIT 77DB2_SYS_PARAMETER 78DB2_SYSTEM_DIST_T 81DB2_SYSTEM_T 84DB2_TRAN_DIST_D, _W 91DB2_TRANSACTION_D, _W 92DB2_US_TRAN_SHAR_H 93DB2_USER_AP_DIST_H, _W 95DB2_USER_APPL_H, _W 96DB2_USER_DIST_H, _W 97DB2_USER_TRAN_H, _D,

_W 101description 19DFSMS component

DFSMS_ACTIVITY_D, _M 195DFSMS_BACKUP_D, _M 197DFSMS_DASD_CAP_D 199DFSMS_DASD_CAP_M 200DFSMS_DATASET_D 201, 268DFSMS_DATASET_M 203, 269DFSMS_DCOLLECT_T 205DFSMS_MIGRATION_D, _M 206DFSMS_TAPE_CAP_D, _M 208DFSMS_VOLUME_D 209, 270DFSMS_VOLUME_M 210, 272

MVS analysis componentMVS_ACCNT_PGM_T 303, 305,

333, 334, 335, 336, 337, 339, 340,341, 342, 343, 345, 571

MVS_ADDRDISTR_H, _D,_M 306

MVS_ADDRSPACE_D, _M 311MVS_ADDRSPACE_T 317MVS_COMPCODE_D, _M 324,

325MVS_GOAL_ACT_D, _M 326MVS_IPL_T 328MVS_LPAR_D, _M 329MVS_MOUNT_D, _M 332MVS_PRINTER_D, _M 347MVS_PROGRAM_M 349MVS_SYSTEM_H, _D, _M 350MVS_TAPE_M 353MVS_VTS_CONF 354, 361, 362MVS_VTS_H, _D, _M 355, 364,

365MVS_WORKLOAD_H, _D,

_M 367MVS_WORKLOAD2_H, _D,

_M 370MVS performance management

componentMVSPM_APPC_H 601MVSPM_APPL_H 604MVSPM_BMF_H 609MVSPM_CACHE_H 610

data tables (continued)MVS performance management

component (continued)MVSPM_CF_PROC_H 614MVSPM_CF_REQUEST_H 616MVSPM_CHANNEL_H 621MVSPM_CPU_H 626MVSPM_DATASET_H 632MVSPM_DEVICE_AP_H 634MVSPM_DEVICE_H 635MVSPM_ENQUEUE_H 638MVSPM_GOAL_ACT_H 640, 642,

647, 648, 650, 651, 653, 658MVSPM_LPAR_H 644MVSPM_PAGE_DS_H 660MVSPM_PAGING_H 662MVSPM_STORAGE_H 669, 671,

760MVSPM_STORCLASS_H 673MVSPM_SWAP_H 674MVSPM_SYSTEM_H 676MVSPM_VLF_H 679, 680MVSPM_VS_CSASQA_H 683MVSPM_VS_PRIVATE_H 700MVSPM_VS_SUBPOOL_H 704MVSPM_WLM_SERVED_H 705MVSPM_WLM_STATE_H 706MVSPM_WORKLOAD_H 708MVSPM_WORKLOAD2_H 711MVSPM_XCF_MEMBER_H 717MVSPM_XCF_PATH_H 718MVSPM_XCF_SYS_H 720

DB2 componentcustomization

make input data available 45update lookup tables 46

data flowlookup tables 48

data tablesDB2_APPL_DIST_H, _W 29, 51DB2_APPLICATION_H, _W 52DB2_BP_SHARING_T 53DB2_BPATTR_SHR_T 56DB2_BUFFER_POOL_T 58DB2_DATABASE_T 63DB2_LOCK_SHARING_T 73DB2_PACKAGE_H, _D, _W 75DB2_SHARING_INIT 77DB2_SYS_PARAMETER 78DB2_SYSTEM_DIST_T 81DB2_SYSTEM_T 84DB2_TRAN_DIST_D, _W 91DB2_TRANSACTION_D, _W 92DB2_US_TRAN_SHAR_H 93DB2_USER_AP_DIST_H, _W 95DB2_USER_APPL_H, _W 96DB2_USER_DIST_H, _W 97DB2_USER_TRAN_H, _D,

_W 101description 3log definitions 49

947

DB2 component (continued)lookup tables

DB2_APPLICATION 115record definitions

SMF_100_0 49SMF_100_1 49SMF_100_2 49SMF_100_3 49SMF_101 49SMF_101_1 49SMF_102 49

report IDsDB201 32, 34, 36, 38, 40, 118DB202 120DB203 121DB204 122DB205 125DB206 126DB207 127DB208 129DB209 131DB210 133DB211 135DB212 137DB213 138DB214 140DB215 142DB216 144DB217 146DB218 148DB219 150DB220 152DB221 155DB222 156DB223 157DB224 159DB225 161DB226 163, 165, 167, 169, 171,

173, 175, 177, 179, 181, 182reports

DB2 Application Profiles,Overview report 138

DB2 Application Profiles, Trendreport 140

DB2 Application Response Times,Detail report 32, 34, 36, 38, 40,117

DB2 Application Response Times,Overview report 120

DB2 Application Response Times,Trend report 121

DB2 Buffer Pool Exceptionsreport 150

DB2 Buffer Pool Statistics, Detailreport 142

DB2 Buffer Pool Statistics,Overview report 144

DB2 Data Sharing LockingAccounting, Overviewreport 163, 165, 167, 169, 171,173, 175, 177, 179, 181, 182

DB2 Data Sharing LockingStatistics, Detail report 159

DB2 Database Services Statistics,Detail report 129

DB2 DBRMs Class 7,8 Times,Overview report 156

DB2 component (continued)reports (continued)

DB2 EDM Pool Statistics, Detailreport 146

DB2 EDM Pool Statistics,Overview report 148

DB2 General DB2 Measure byProfile, Overview report 137

DB2 Group Buffer PoolAccounting, Overviewreport 161

DB2 Group Buffer Pool Statistics,Detail report 157

DB2 Packages Class 7,8 Times,Overview report 155

DB2 System CPU % by AddressSpace, Overview report 133

DB2 System Parametersreport 152

DB2 System Services Statistics,Detail report 127

DB2 System Statistics, Overviewreport 131

DB2 System Statistics, Trendreport 135

DB2 Transaction Statistics, Detailreport 122

DB2 Transaction Statistics,Overview report 125

DB2 Transaction Statistics, Trendreport 126

DB2_APPL_DIST_H, _W 29, 51DB2_APPLICATION 115DB2_APPLICATION_H, _W 52DB2_BP_SHARING_T 53DB2_BPATTR_SHR_T 56DB2_BUFFER_POOL_T 58DB2_DATABASE_T 63DB2_LOCK_SHARING_T 73DB2_PACKAGE_H, _D, _W 75DB2_SHARING_INIT 77DB2_SYS_PARAMETER 78DB2_SYSTEM_DIST_T 81DB2_SYSTEM_T 84DB2_TRAN_DIST_D, _W 91DB2_TRANSACTION_D, _W 92DB2_US_TRAN_SHAR_H 93DB2_USER_AP_DIST_H, _W 95DB2_USER_APPL_H, _W 96DB2_USER_DIST_H, _W 97DB2_USER_TRAN_H, _D, _W 101DCOLLECT records

DCOLLECT_A 193, 265DCOLLECT_AG 193DCOLLECT_B 193DCOLLECT_BC 193DCOLLECT_C 193DCOLLECT_D 193DCOLLECT_DC 193DCOLLECT_DR 193DCOLLECT_LB 193DCOLLECT_M 193DCOLLECT_MC 193DCOLLECT_SC 193DCOLLECT_SG 193DCOLLECT_T 193DCOLLECT_V 193

DCOLLECT records (continued)DCOLLECT_VL 193

DCOLLECT statistics 205DFSMS component

customizationmake input data available 185,

259, 260update lookup tables 186, 261

data flowlookup tables 191, 263record procedure 194

data tablesDFSMS_ACTIVITY_D, _M 195DFSMS_BACKUP_D, _M 197DFSMS_DASD_CAP_D 199DFSMS_DASD_CAP_M 200DFSMS_DATASET_D 201, 268DFSMS_DATASET_M 203, 269DFSMS_DCOLLECT_T 205DFSMS_MIGRATION_D, _M 206DFSMS_TAPE_CAP_D, _M 208DFSMS_VOLUME_D 209, 270DFSMS_VOLUME_M 210, 272

description 4log definitions 193, 265lookup tables

DFSMS_DS_OWNER 212, 275DFSMS_LAST_RUN 213DFSMS_MIGRATE_DAYS 214DFSMS_PLANNED_CAP 215DFSMS_THRESHOLD 216DFSMS_VOL_STORGRP 217

record definitionsDCOLLECT_A 193, 265DCOLLECT_AG 193DCOLLECT_B 193DCOLLECT_BC 193DCOLLECT_C 193DCOLLECT_D 193DCOLLECT_DC 193DCOLLECT_DR 193DCOLLECT_LB 193DCOLLECT_M 193DCOLLECT_MC 193DCOLLECT_SC 193DCOLLECT_SG 193DCOLLECT_T 193DCOLLECT_V 193DCOLLECT_VL 193

report IDsDFSMS01 245DFSMS02 245DFSMS03 255, 278, 279, 280, 281,

282DFSMS04 252DFSMS05 249DFSMS06 251DFSMS07 247DFSMS08 229DFSMS09 229DFSMS10 226DFSMS11 235DFSMS12 227DFSMS13 237DFSMS14 253DFSMS15 220DFSMS16 220


DFSMS component (continued)report IDs (continued)

DFSMS17 222DFSMS18 243DFSMS19 241DFSMS20 224DFSMS21 239DFSMS22 230DFSMS23 232DFSMS24 234DFSMS25 233

reportsDFSMS Active/Migrat/Backup

Storage, Daily/Monthly Trendreport 220

DFSMS Allocated/Used/UnusedStorage, Daily Trend report 222

DFSMS Backup Storage onDASD/Tape, Daily Trendreport 224

DFSMS DASD Exceptionsreport 226

DFSMS Data Not Migrated butEligible, Daily Trend report 227

DFSMS Free Space by StorageGroup, Daily/Monthly Trendreport 229

DFSMS Migration and BackupActivities, Daily Trendreport 230

DFSMS Projects Allocating MostDASD report 232

DFSMS Projects Using Most DASDfor Backup report 233

DFSMS Projects Using Most DASDfor Migration report 234

DFSMS Projects Wasting MostDASD report 235

DFSMS Storage Groups MeetingTarget Threshold report 237

DFSMS Storage Used for Migrationon ML1/ML2 report 239

DFSMS Tape forMigration/Backup/Dump/3 1,Daily Trend report 241

DFSMS Target/Trigger MigrationValues report 243

DFSMS Total Storage Used byManagement Class report 247

DFSMS Total Storage Used byProject report 249

DFSMS Total Storage Used byStorage Class report 251

DFSMS Total Storage Used byStorage Group report 252

DFSMS Volumes not MeetingTarget Threshold report 253

Total DASD Usage, Daily/MonthlyTrend report 245

VTOC Information by Volumereport 255, 278, 279, 280, 281,282

DFSMS_ACTIVITY_D, _M 195DFSMS_BACKUP_D, _M 197DFSMS_DASD_CAP_D 199DFSMS_DASD_CAP_M 200DFSMS_DATASET_D 201, 268

DFSMS_DATASET_M 203, 269DFSMS_DCOLLECT_T 205DFSMS_DS_OWNER 212, 275DFSMS_LAST_RUN 213DFSMS_MIGRATE_DAYS 214DFSMS_MIGRATION_D, _M 206DFSMS_PLANNED_CAP 215DFSMS_TAPE_CAP_D, _M 208DFSMS_THRESHOLD 216DFSMS_VOL_STORGRP 217DFSMS_VOLUME_D 209, 270DFSMS_VOLUME_M 210, 272

EEREP component

description 4

Ggrouping data sets 212, 275

Hhow to use this book xi

IInformation/Management component

description 4Internet Connection Secure Server

componentdescription 4

Llog definitions

DB2 component 49description 18DFSMS component 193, 265MVS analysis component 297MVS performance management

component 595LookAt message retrieval tool xiiilookup tables

DB2 componentDB2_APPLICATION 115

description 19DFSMS component

DFSMS_DS_OWNER 212, 275DFSMS_LAST_RUN 213DFSMS_MIGRATE_DAYS 214DFSMS_PLANNED_CAP 215DFSMS_THRESHOLD 216DFSMS_VOL_STORGRP 217

MVS analysis componentMVS_ABEND_CODE 397MVS_PRINTER_LOC 400MVS_SYSPLEX 401, 572MVS_WORKLOAD_TYPE 402MVS_WORKLOAD2_TYPE 403


MVSPM_DEVICE_ADDR 786MVSPM_TIME_RES 787

lookup tables (continued)MVS performance management

component (continued)MVSPM_UNIT_TYPE 788

Mmanuals


Message analysis/automation componentdescription 4

message retrieval tool, LookAt xiiimigrated data sets 206MQSeries component

description 5MVS analysis component

CPU reportsMVS Average and Maximum CPU

Load, Daily Profile report 474MVS CPU Load by LPAR,

Monthly/Daily Trendreport 476, 478, 480, 482, 484,486

MVS CPU Load by Period,Daily/Monthly Trendreport 467

MVS CPU Load by WorkloadType, Daily Profile report 473

MVS CPU Load by WorkloadType, Daily/Monthly Trendreport 469

MVS CPU Load by WorkloadType, Peak Hour, Dailyreport 471

customizationmake input data available 287update lookup tables 287

data flowlookup tables 295

data tablesMVS_ACCNT_PGM_T 303, 305,

333, 334, 335, 336, 337, 339, 340,341, 342, 343, 345, 571

MVS_ADDRDISTR_H, _D,_M 306

MVS_ADDRSPACE_D, _M 311MVS_ADDRSPACE_T 317MVS_COMPCODE_D, _M 324,

325MVS_GOAL_ACT_D, _M 326MVS_IPL_T 328MVS_LPAR_D, _M 329MVS_MOUNT_D, _M 332MVS_PRINTER_D, _M 347MVS_PROGRAM_M 349MVS_SYSTEM_H, _D, _M 350MVS_TAPE_M 353MVS_VTS_CONF 354, 361, 362MVS_VTS_H, _D, _M 355, 364,

365MVS_WORKLOAD_H, _D,

_M 367MVS_WORKLOAD2_H, _D,

_M 370description 5

Index 949

MVS analysis component (continued)detailed job reports

MVS Jobs with Input Queue Time> 10 Min, Daily report 454

MVS Jobs with RACF S913 AbendsDaily report 453

MVS Jobs with Tape, Dailyreport 455

device reportsMVS DASD I/O by User Group,

Monthly Overview report 513MVS I/O Rates by User Group,

Peak Hour, Daily report 514MVS MAGSTAR VTS

Configuration report 519MVS MAGSTAR VTS Physical

Drive Mount Daily report 521MVS MAGSTAR VTS Utilization

Daily report 525MVS MAGSTAR VTS Virtual Drive

Mount Daily report 523MVS Tape Demounts/MVS

System, Monthly Overviewreport 516

MVS Tape Errors by Device,Monthly Overview report 517

MVS Tape Errors by Volume,Monthly Trend report 518

MVS Tape I/O by User Group,Monthly Overview report 515

IPL reportsMVS IPLs by Reason Code, Daily

report 466MVS Number of IPLs, Daily Trend

report 465log definitions 297lookup tables

MVS_ABEND_CODE 397MVS_PRINTER_LOC 400MVS_SYSPLEX 401, 572MVS_WORKLOAD_TYPE 402MVS_WORKLOAD2_TYPE 403

MVS overview reportsMVS Activity by User Group,

Daily/Monthly Overviewreport 418

MVS Activity for a User Group,Daily Trend report 419

MVS Availability by Sysplex,Monthly Trend report 424

MVS Average No of AddressSpaces, Monthly Trendreport 417

MVS Exec Velocity (Goal in %),Daily/Monthly Overviewreport 437

MVS Exec Velocity (Goal in %),Daily/Monthly Trendreport 436

MVS Response (Goal in %),Daily/Monthly Overviewreport 432

MVS Response (Goal in %),Daily/Monthly Trendreport 430

MVS analysis component (continued)MVS overview reports (continued)

MVS Response (Goal in sec),Daily/Monthly Overviewreport 435

MVS Response (Goal in sec),Daily/Monthly Trendreport 434

MVS Response Time Distribution,Daily/Monthly Overviewreport 439

MVS Sysplex Overview, MonthlyTrend report 423

MVS System Overview, MonthlyTrend report 415

MVS Users Swapped Out andReady, Daily Profile report 420

MVS Workload by ResourceGroup, Daily/Monthly Overviewreport 428

MVS Workload by Workload Type,Monthly Trend report 421

MVS Workload for a ResourceGroup, Daily/Monthly Trendreport 426

MVS problem reportsMVS Abended Jobs by User

Group, Daily report 413MVS Exceptions, Daily

report 408, 573MVS No of Canceled Batch Jobs by

User Group, Daily report 412MVS No of System Abends by

Abend Code, Monthlyreport 409

MVS No of User Abends by AbendCode, Monthly report 410

MVS Percent Abended Jobs byUser Group, Monthly report 411

paging reportsMVS Paging by Subsystem, Daily

Trend report 510MVS Paging Rates, Daily Trend

report 512printer reports

MVS Print Activity by User Group,Monthly Overview report 529

MVS Printer Activity, MonthlyOverview report 527, 532, 533,537, 541, 543, 545, 546, 547, 548,549, 551, 553, 554, 556, 558

MVS Printer Forms Usage,Monthly Overview report 531

program reportsMVS CPU Usage by Account Field

and Program, Daily report 461,463

MVS Most CPU ConsumingPrograms, Monthly Overviewreport 456

MVS Most I/O IntensivePrograms, Monthly Overviewreport 458, 460

record definitionsSMF_000 297, 569SMF_006 297, 569SMF_007 297

MVS analysis component (continued)record definitions (continued)

SMF_021 297SMF_025 297SMF_026 297SMF_030 298SMF_070 298SMF_071 299SMF_072_1 299SMF_072_3 299SMF_090 299SMF_094 299

report groupsCPU reports 467detailed job reports 453device reports 513IPL reports 465MVS overview reports 414MVS problem reports 408paging reports 510printer reports 527, 532, 553program reports 456storage reports 488summary job reports 449TSO reports 441

report IDsMVS01 415MVS04 417MVS05 418MVS06 418MVS07 419MVS08 420MVS10 421MVS100 525MVS101 461, 463MVS11 441MVS12 443MVS13 444MVS14 443MVS15 445MVS16 446MVS17 447MVS18 448MVS19 447MVS21 467MVS22 467MVS23 474MVS25 469MVS26 469MVS28 471MVS29 473MVS30 489MVS31 490MVS32 492MVS33 494MVS34 496MVS35 498MVS36 500MVS39 502MVS40 504MVS41 506MVS42 508MVS43 510MVS44 512MVS45 409MVS46 410MVS47 411


MVS analysis component (continued)report IDs (continued)

MVS48 412MVS49 413MVS50 449MVS51 450MVS52 451MVS53 452MVS54 453MVS55 454MVS56 455MVS57 456MVS58 458MVS59 460MVS60 465MVS61 466MVS62 513MVS63 514MVS64 515MVS65 516MVS66 517MVS67 518MVS68 527, 532, 533, 537, 541,

543, 545, 546, 547, 548, 549, 551,553, 554, 556, 558

MVS69 529MVS70 531MVS71 408, 573, 574, 575MVS72 476, 478, 480, 482, 484,

486MVS73 476, 478, 480, 482, 484,

486MVS75 423MVS76 424MVS79 426MVS80 426MVS81 428MVS82 428MVS83 430MVS84 430MVS85 432MVS86 432MVS87 434MVS88 434MVS89 435MVS90 435MVS91 436MVS92 436MVS93 437MVS94 437MVS95 439MVS96 439MVS97 519MVS98 521MVS99 523

storage reportsMVS Available CS in Megabytes,

Daily Profile report 489MVS Central Storage by Type,

Monthly Trend report 506MVS CS by Type, Peak Hour,

Daily Trend report 502MVS CS by Workload Type,

Monthly Trend report 496MVS CS by Workload Type, Peak

Hour, Daily Trend report 490

MVS analysis component (continued)storage reports (continued)

MVS ES by Type, Peak Hour, DailyTrend report 504

MVS ES by Workload Type,Monthly Trend report 498

MVS ES by Workload Type, PeakHour, Daily Trend report 492

MVS Expanded Storage by Type,Monthly Trend report 508

MVS Storage by Workload Type,Monthly Trend report 500

MVS Storage by Workload Type,Peak Hour, Daily Trendreport 494

summary job reportsMVS Job Statistics by Period and

User Group, Daily report 452MVS Job Statistics by User Group,

Monthly Overview report 449MVS Job Statistics for a User

Group, Daily Trend report 450MVS Number of Jobs with Tape

Mounts, Daily Trend report 451TSO reports

MVS Number of TSO Users, DailyProfile report 445

MVS TSO Response Time byWorkload, Daily Profilereport 441

MVS TSO Response Time byWorkload, Daily/Monthly Trendreport 443

MVS TSO Response Time, Peakhour, Daily Trend report 444

MVS TSO Transactions byWorkload, Daily Profilereport 446

MVS TSO Transactions byWorkload, Daily/Monthly Trendreport 447

MVS TSO Transactions, Peak Hour,Daily Trend report 448

viewsMVS_LPAR_DV 373MVS_LPAR_MV 375MVS_RESOURCE_DV 378MVS_RESOURCE_HV 377MVS_RESOURCE_MV 379MVS_WORKLOAD_DV1 382MVS_WORKLOAD_DV2 383MVS_WORKLOAD_DV3 384MVS_WORKLOAD_DV4 385MVS_WORKLOAD_HV1 380MVS_WORKLOAD_HV2 380MVS_WORKLOAD_HV3 381MVS_WORKLOAD_HV4 381MVS_WORKLOAD_MV1 386MVS_WORKLOAD_MV2 387MVS_WORKLOAD_MV3 388MVS_WORKLOAD_MV4 389MVS_WORKLOAD2_DV2 393MVS_WORKLOAD2_DV4 394MVS_WORKLOAD2_HV2 390MVS_WORKLOAD2_HV4 392MVS_WORKLOAD2_MV2 395MVS_WORKLOAD2_MV4 396


application use of resourcesMVSPM APPC, CPU and I/O by

Transaction Class report 852MVSPM APPC, Execution and

Queueing, Hourly Trendreport 853

MVSPM Applications Waiting onENQs, Hourly Trend report 858

MVSPM BMF Directory PageReads/Hits, Hourly Trendreport 851

MVSPM BMF Member PageReads/Hits, Hourly Trendreport 850

MVSPM CPU Busy by WorkloadPGNs, Hourly Trend report 838

MVSPM CPU Busy by WorkloadTypes, Hourly Trend report 837

MVSPM CPU per I/O byWorkload PGNs, Hourly Trendreport 843

MVSPM CPU Per I/O byWorkload Type, Hourly Trendreport 842

MVSPM Exec. Velocity Goals &Actuals, Hourly Trendreport 861

MVSPM I/O Rate by WorkloadType, Hourly Trend report 841

MVSPM Page-ins by WorkloadType, Hourly Trend report 844

MVSPM Paging Activity byWorkload, Hourly Trendreport 845

MVSPM Response TimeBreakdown Overviewreport 864

MVSPM Response TimeBreakdown, Hourly Trendreport 866

MVSPM Response Time byWorkload, Hourly Trendreport 847

MVSPM Response TimeDistribution report 862

MVSPM Response Time Goals &Actuals, Hourly Trendreport 860

MVSPM Served Service ClassesOverview report 863

MVSPM Storage Used byWorkload PGNs, Hourly Trendreport 840

MVSPM Storage Used byWorkload Type, Hourly Trendreport 839

MVSPM System Resources byWorkload Type report 835

MVSPM VLF Dataspace Usage,Hourly/Daily Trend report 856

MVSPM VLF Usage and Hit Ratio,Hourly/Daily Trend report 854

MVSPM Workload Resp TimeComponents, Hourly Trendreport 848

Index 951

MVS performance managementcomponent (continued)

CPU and storage resourcesMVSPM Average CPU Busy

Profile, Hourly Trend report 805MVSPM Average CPU Busy,

Daily/Hourly Trend report 803MVSPM Average High UIC Profile,

Hourly Trend report 813MVSPM Avg CF Busy Profile,

Hourly Trend report 822MVSPM Avg CF Storage Usage,

Hourly Trend report 823MVSPM CPU Busy and Other

Indicators, Hourly Trendreport 806

MVSPM CPU Busy by SharedLPARs, Hourly Trendreport 819

MVSPM CPU Busy Profile SharedLPARS, Hourly Trendreport 818

MVSPM LPAR Management Time,Hourly Trend report 821

MVSPM Minimum Available ExpStorage, Hourly Trendreport 812

MVSPM Page Data Set Busy Time,Hourly Trend report 816

MVSPM Page Data Set DeviceResp Time, Hourly Trendreport 815

MVSPM Page Data Set ResponseTime, Hourly Trend report 814

MVSPM Percent of Share Used byLPARS, Hourly Trendreport 820

MVSPM System Central StorageMap, Hourly Trend report 808

MVSPM System Expanded StorageMap, Hourly Trend report 810

MVSPM System Storage PagingRates, Hourly Trend report 817

customizationmake input data available 581update lookup tables 584

daily performance overviewMVSPM CPU and Processor

Storage Activity Overviewreport 793

MVSPM DASD Activity Overviewreport 801

MVSPM Data Set ActivityOverview report 905

MVSPM Execution Velocity Goals& Actuals Overview report 800

MVSPM Goalmode WorkloadDescriptions report 792

MVSPM Response Time Goals vsActuals Overview report 799

MVSPM Workload Descriptionsreport 791

MVSPM Workload ResourceUtilization Overview report 795


daily performance overview(continued)

MVSPM Workload Response TimeComponents Overviewreport 797, 917, 919, 921, 923,925, 926, 928, 930

data flowlookup tables 591record procedure 300, 599

data tablesMVSPM_APPC_H 601MVSPM_APPL_H 604MVSPM_BMF_H 609MVSPM_CACHE_H 610MVSPM_CF_PROC_H 614MVSPM_CF_REQUEST_H 616MVSPM_CHANNEL_H 621MVSPM_CPU_H 626MVSPM_DATASET_H 632MVSPM_DEVICE_AP_H 634MVSPM_DEVICE_H 635MVSPM_ENQUEUE_H 638MVSPM_GOAL_ACT_H 640, 642,

647, 648, 650, 651, 653, 658MVSPM_LPAR_H 644MVSPM_PAGE_DS_H 660MVSPM_PAGING_H 662MVSPM_STORAGE_H 669, 671,

760MVSPM_STORCLASS_H 673MVSPM_SWAP_H 674MVSPM_SYSTEM_H 676MVSPM_VLF_H 679, 680MVSPM_VS_CSASQA_H 683MVSPM_VS_PRIVATE_H 700MVSPM_VS_SUBPOOL_H 704MVSPM_WLM_SERVED_H 705MVSPM_WLM_STATE_H 706MVSPM_WORKLOAD_H 708MVSPM_WORKLOAD2_H 711MVSPM_XCF_MEMBER_H 717MVSPM_XCF_PATH_H 718MVSPM_XCF_SYS_H 720

description 5I/O subsystem performance

MVSPM Applications Waiting onENQs, Worst Case report 859

MVSPM Cache CU Operations byCU, Daily Overview report 893

MVSPM Cache CU Operations,Hourly Trend report 895

MVSPM Cache Hit Rates by CU,Hourly Trend report 881

MVSPM CF, Processor andStorage, Overview report 824

MVSPM CF, Request Rate,Overview report 826

MVSPM CF, Structures Details,Overview report 829, 830, 832,834

MVSPM CF, System Details,Overview report 827

MVSPM Channel Path Busyreport 868, 915


I/O subsystem performance(continued)

MVSPM Data Set I/O Rate & RespTime, Hourly Trend report 907

MVSPM Data Set I/O Rate Profile,Hourly Trend report 909

MVSPM Data Set Resp TimeProfile, Hourly Trend report 910

MVSPM DFW Hit Rates by CU,Hourly Trend report 883

MVSPM Highest Hit RateVolumes, Daily Overviewreport 889

MVSPM Highest Stating RateVolumes, Daily Overviewreport 891

MVSPM I/O Rate by Workload onSelected Devices report 899

MVSPM I/O Rate for Devices byWorkload Type report 877

MVSPM I/O Rate for LCUs,Hourly Trend report 870

MVSPM I/O Response TimeComponents for LCUsreport 872

MVSPM I/O Response TimeComponents, DASD Devicesreport 875

MVSPM I/O Response Time forDevice, Hourly Trendreport 879

MVSPM I/O Response Time forDevices by Workload report 897

MVSPM I/O Response Time forLCUs, Hourly Trend report 871

MVSPM No of Users Waiting forDevice, Daily Trend report 874

MVSPM Overall Effectiveness byCU, Daily Overview report 887

MVSPM Stating Rates by CU,Hourly Trend report 885

MVSPM Storage Class I/O Rate,Hourly Trend report 912, 913

MVSPM Storage Class Resp Time,Hourly Trend report 911

MVSPM XCF Activity by Path andSystem, Overview report 903

MVSPM XCF Signal Rates, HourlyTrend report 902

MVSPM XCF Statistics by System,Overview report 900

log definitions 595lookup tables

MVSPM_DEVICE_ADDR 786MVSPM_TIME_RES 787MVSPM_UNIT_TYPE 788

record definitionsSMF_030 596SMF_033_1 596SMF_041_3 596SMF_042_1 596SMF_042_5 596, 597SMF_042_6 597SMF_070 597SMF_071 597



record definitions (continued)SMF_072_1 597SMF_072_2 597SMF_072_3 597SMF_072_4 597SMF_073 597SMF_074_1 598SMF_074_2 598SMF_074_3 598SMF_074_4 598SMF_074_5 598SMF_075 598SMF_077 598SMF_078_1 598SMF_078_2 598SMF_078_3 598SMF_079 598SMF_CACHE 599

report groupsapplication use of resources 835CPU and storage resources 803daily performance overview 791,

917I/O subsystem performance 868

report IDsMVSPM01 791MVSPM02 793MVSPM03 795MVSPM04 797, 913, 917, 919, 921,

923, 925, 926, 928, 930MVSPM05 801MVSPM06 803MVSPM07 803MVSPM08 805MVSPM09 806MVSPM0A 834MVSPM10 808MVSPM11 810MVSPM12 812MVSPM14 813MVSPM15 814MVSPM16 815MVSPM17 816MVSPM18 817MVSPM19 845MVSPM20 818MVSPM21 819MVSPM22 820MVSPM23 821MVSPM24 835MVSPM25 837MVSPM26 838MVSPM27 839MVSPM28 840MVSPM29 841MVSPM30 842MVSPM31 843MVSPM32 844MVSPM33 847MVSPM34 848MVSPM37 900MVSPM38 868, 915MVSPM39 870MVSPM40 871MVSPM41 872


report IDs (continued)MVSPM42 874MVSPM43 875MVSPM44 877MVSPM45 879MVSPM46 881MVSPM47 883MVSPM48 885MVSPM49 887MVSPM50 889MVSPM51 891MVSPM52 859MVSPM53 897MVSPM54 899MVSPM55 858MVSPM56 902MVSPM57 903MVSPM58 893MVSPM59 895MVSPM60 850MVSPM61 851MVSPM62 852MVSPM63 853MVSPM64 854MVSPM65 856MVSPM66 854MVSPM67 856MVSPM68 822MVSPM69 823MVSPM70 792MVSPM71 866MVSPM72 799MVSPM73 864MVSPM74 862MVSPM75 800MVSPM76 861MVSPM78 860MVSPM79 863MVSPM80 905MVSPM81 907MVSPM82 909MVSPM83 910MVSPM84 911MVSPM85 912, 913MVSPM86 824MVSPM87 826MVSPM88 827MVSPM89 829, 830, 832, 834MVSPMM3 832

viewsMVSPM_APPL_HV 722MVSPM_CACHE_HV 727MVSPM_CF_PROC_HV 734MVSPM_CF_REQ_HV 735MVSPM_CPU_HV 739MVSPM_DATASET_HV 744MVSPM_DEVICE_AP_HV 746MVSPM_DEVICE_AP_PV 747MVSPM_DEVICE_HV 748MVSPM_ENQUEUE_HV 751MVSPM_LPAR_HV 752MVSPM_PAGE_DS_HV 754MVSPM_PAGING_HV 756MVSPM_STORAGE_HV 762MVSPM_STORCLASS_HV 764


views (continued)MVSPM_SWAP_HV 766MVSPM_SYSTEM_HV 770, 773MVSPM_SYSTEM_PV 772MVSPM_WORKLOAD2_HV 776,

779MVSPM_XCF_PATH_HV 783MVSPM_XCF_SYS_HV 784

MVS_ABEND_CODE 397MVS_ACCNT_PGM_T 303, 305, 333,

334, 335, 336, 337, 339, 340, 341, 342,343, 345, 571

MVS_ADDRDISTR_H, _D, _M 306MVS_ADDRSPACE_D, _M 311MVS_ADDRSPACE_T 317MVS_COMPCODE_D, _M 324, 325MVS_GOAL_ACT_D, _M 326MVS_IPL_T 328MVS_LPAR_D, _M 329MVS_LPAR_DV 373MVS_LPAR_MV 375MVS_MOUNT_D, _M 332MVS_PRINTER_D, _M 347MVS_PRINTER_LOC 400MVS_PROGRAM_M 349MVS_RESOURCE_DV 378MVS_RESOURCE_HV 377MVS_RESOURCE_MV 379MVS_SYSPLEX 401, 572MVS_SYSTEM_H, _D, _M 350MVS_TAPE_M 353MVS_VTS_CONF 354, 361, 362MVS_VTS_H, _D, _M 355, 364, 365MVS_WORKLOAD_DV1 382MVS_WORKLOAD_DV2 383MVS_WORKLOAD_DV3 384MVS_WORKLOAD_DV4 385MVS_WORKLOAD_H, _D, _M 367MVS_WORKLOAD_HV1 380MVS_WORKLOAD_HV2 380MVS_WORKLOAD_HV3 381MVS_WORKLOAD_HV4 381MVS_WORKLOAD_MV1 386MVS_WORKLOAD_MV2 387MVS_WORKLOAD_MV3 388MVS_WORKLOAD_MV4 389MVS_WORKLOAD_TYPE 402MVS_WORKLOAD2_DV2 393MVS_WORKLOAD2_DV4 394MVS_WORKLOAD2_H, _D, _M 370MVS_WORKLOAD2_HV2 390MVS_WORKLOAD2_HV4 392MVS_WORKLOAD2_MV2 395MVS_WORKLOAD2_MV4 396MVS_WORKLOAD2_TYPE 403MVSPM_APPC_H 601MVSPM_APPL_H 604MVSPM_APPL_HV 722MVSPM_BMF_H 609MVSPM_CACHE_H 610MVSPM_CACHE_HV 727MVSPM_CF_PROC_H 614MVSPM_CF_PROC_HV 734MVSPM_CF_REQ_HV 735MVSPM_CF_REQUEST_H 616

Index 953

MVSPM_CHANNEL_H 621MVSPM_CPU_H 626MVSPM_CPU_HV 739MVSPM_DATASET_H 632MVSPM_DATASET_HV 744MVSPM_DEVICE_ADDR 786MVSPM_DEVICE_AP_H 634MVSPM_DEVICE_AP_HV 746MVSPM_DEVICE_AP_PV 747MVSPM_DEVICE_H 635MVSPM_DEVICE_HV 748MVSPM_ENQUEUE_H 638MVSPM_ENQUEUE_HV 751MVSPM_GOAL_ACT_H 640, 642, 647,

648, 650, 651, 653, 658MVSPM_LPAR_H 644MVSPM_LPAR_HV 752MVSPM_PAGE_DS_H 660MVSPM_PAGE_DS_HV 754MVSPM_PAGING_H 662MVSPM_PAGING_HV 756MVSPM_STORAGE_H 669, 671, 760MVSPM_STORAGE_HV 762MVSPM_STORCLASS_H 673MVSPM_STORCLASS_HV 764MVSPM_SWAP_H 674MVSPM_SWAP_HV 766MVSPM_SYSTEM_H 676MVSPM_SYSTEM_HV 770MVSPM_SYSTEM_PV 772MVSPM_TIME_RES 787MVSPM_UNIT_TYPE 788MVSPM_VLF_H 679, 680MVSPM_VS_CSASQA_H 683MVSPM_VS_PRIVATE_H 700MVSPM_VS_SUBPOOL_H 704MVSPM_WLM_SERVED_H 705MVSPM_WLM_STATE_H 706MVSPM_WORKLOAD_H 708MVSPM_WORKLOAD_HV 773MVSPM_WORKLOAD2_H 711MVSPM_WORKLOAD2_HV 776, 779MVSPM_XCF_MEMBER_H 717MVSPM_XCF_PATH_H 718MVSPM_XCF_PATH_HV 783MVSPM_XCF_SYS_H 720MVSPM_XCF_SYS_HV 784

Oonline publications xivOPC component

description 5ordering publications xiv

Ppublications


RRACF component

description 5

record definitionsDB2 component

SMF_100_0 49SMF_100_1 49SMF_100_2 49SMF_100_3 49SMF_101 49SMF_101_1 49SMF_102 49


DCOLLECT_A 193, 265DCOLLECT_AG 193DCOLLECT_B 193DCOLLECT_BC 193DCOLLECT_C 193DCOLLECT_D 193DCOLLECT_DC 193DCOLLECT_DR 193DCOLLECT_LB 193DCOLLECT_M 193DCOLLECT_MC 193DCOLLECT_SC 193DCOLLECT_SG 193DCOLLECT_T 193DCOLLECT_V 193DCOLLECT_VL 193

MVS analysis componentSMF_000 297, 569SMF_006 297, 569SMF_007 297SMF_021 297SMF_025 297SMF_026 297SMF_030 298SMF_070 298SMF_071 299SMF_072_1 299SMF_072_3 299SMF_090 299SMF_094 299


SMF_033_1 596SMF_041_3 596SMF_042_1 596SMF_042_5 596, 597SMF_042_6 597SMF_070 597SMF_071 597SMF_072_1 597SMF_072_2 597SMF_072_3 597SMF_072_4 597SMF_073 597SMF_074_1 598SMF_074_2 598SMF_074_3 598SMF_074_4 598SMF_074_5 598SMF_075 598SMF_077 598SMF_078_1 598SMF_078_2 598SMF_078_3 598SMF_079 598SMF_30 596

record definitions (continued)MVS performance management

component (continued)SMF_CACHE 599

report groupsMVS analysis component

CPU reports 467detailed job reports 453device reports 513IPL reports 465MVS overview reports 414MVS problem reports 408paging reports 510printer reports 527, 532, 553program reports 456storage reports 488summary job reports 449TSO reports 441


application use of resources 835CPU and storage resources 803daily performance overview 791,

917I/O subsystem performance 868

reportsDB2 component

DB2 Application Profiles,Overview report 138

DB2 Application Profiles, Trendreport 140

DB2 Application Response Times,Detail report 32, 34, 36, 38, 40,117

DB2 Application Response Times,Overview report 120

DB2 Application Response Times,Trend report 121

DB2 Buffer Pool Exceptionsreport 150

DB2 Buffer Pool Statistics, Detailreport 142

DB2 Buffer Pool Statistics,Overview report 144

DB2 Data Sharing LockingAccounting, Overviewreport 163, 165, 167, 169, 171,173, 175, 177, 179, 181, 182

DB2 Data Sharing LockingStatistics, Detail report 159

DB2 Database Services Statistics,Detail report 129

DB2 DBRMs Class 7,8 Times,Overview report 156

DB2 EDM Pool Statistics, Detailreport 146

DB2 EDM Pool Statistics,Overview report 148

DB2 General DB2 Measure byProfile, Overview report 137

DB2 Group Buffer PoolAccounting, Overviewreport 161

DB2 Group Buffer Pool Statistics,Detail report 157

DB2 Packages Class 7,8 Times,Overview report 155


reports (continued)DB2 component (continued)

DB2 System CPU % by AddressSpace, Overview report 133

DB2 System Parametersreport 152

DB2 System Services Statistics,Detail report 127

DB2 System Statistics, Overviewreport 131

DB2 System Statistics, Trendreport 135

DB2 Transaction Statistics, Detailreport 122

DB2 Transaction Statistics,Overview report 125

DB2 Transaction Statistics, Trendreport 126


DFSMS Active/Migrat/BackupStorage, Daily/Monthly Trendreport 220

DFSMS Allocated/Used/UnusedStorage, Daily Trend report 222

DFSMS Backup Storage onDASD/Tape, Daily Trendreport 224

DFSMS DASD Exceptionsreport 226

DFSMS Data Not Migrated butEligible, Daily Trend report 227

DFSMS Free Space by StorageGroup, Daily/Monthly Trendreport 229

DFSMS Migration and BackupActivities, Daily Trendreport 230

DFSMS Projects Allocating MostDASD report 232

DFSMS Projects Using Most DASDfor Backup report 233

DFSMS Projects Using Most DASDfor Migration report 234

DFSMS Projects Wasting MostDASD report 235

DFSMS Storage Groups MeetingTarget Threshold report 237

DFSMS Storage Used for Migrationon ML1/ML2 report 239

DFSMS tape formigration/backup/dump, DailyTrend report 241

DFSMS Target/Trigger MigrationValues report 243

DFSMS Total Storage Used byManagement Class report 247

DFSMS Total Storage Used byProject report 249

DFSMS Total Storage Used byStorage Class report 251

DFSMS Total Storage Used byStorage Group report 252

DFSMS Volumes not MeetingTarget Threshold report 253

Total DASD Usage, Daily/MonthlyTrend report 245

reports (continued)DFSMS component (continued)

VTOC Information by Volumereport 255, 278, 279, 280, 281,282

MVS analysis component 451MVS Abended Jobs by User

Group, Daily report 413MVS Activity by User Group,

Daily/Monthly Overviewreport 418

MVS Activity for a User Group,Daily Trend report 419

MVS Availability by Sysplex,Monthly Trend report 424

MVS Available CS in Megabytes,Daily Profile report 489

MVS Average and Maximum CPULoad, Daily Profile report 474

MVS Average No of AddressSpaces, Monthly Trendreport 417

MVS Central Storage by Type,Monthly Trend report 506

MVS CPU Load by LPAR,Monthly/Daily Trendreport 476, 478, 480, 482, 484,486

MVS CPU Load by Period,Daily/Monthly Trendreport 467

MVS CPU Load by WorkloadType, Daily Profile report 473

MVS CPU Load by WorkloadType, Daily/Monthly Trendreport 469

MVS CPU Load by WorkloadType, Peak Hour, Dailyreport 471

MVS CPU Usage by Account Fieldand Program, Daily report 461,463

MVS CS by Type, Peak Hour,Daily Trend report 502

MVS CS by Workload Type,Monthly Trend report 496

MVS CS by Workload Type, PeakHour, Daily Trend report 490

MVS DASD I/O by User Group,Monthly Overview report 513

MVS ES by Type, Peak Hour, DailyTrend report 504

MVS ES by Workload Type,Monthly Trend report 498

MVS ES by Workload Type, PeakHour, Daily Trend report 492

MVS Exceptions, Dailyreport 408, 573

MVS Exec Velocity (Goal in %),Daily/Monthly Overviewreport 437

MVS Exec Velocity (Goal in %),Daily/Monthly Trendreport 436

MVS Expanded Storage by Type,Monthly Trend report 508

reports (continued)MVS analysis component (continued)

MVS I/O Rates by User Group,Peak Hour, Daily report 514

MVS IPLs by Reason Code, Dailyreport 466

MVS Job Statistics by Period andUser Group, Daily report 452

MVS Job Statistics by User Group,Monthly Overview report 449

MVS Job Statistics for a UserGroup, Daily Trend report 450

MVS Jobs with Input Queue Time> 10 Min, Daily report 454

MVS Jobs with RACF S913 AbendsDaily report 453

MVS Jobs with Tape, Dailyreport 455

MVS Most CPU ConsumingPrograms, Monthly Overviewreport 456

MVS Most I/O IntensivePrograms, Monthly Overviewreport 458, 460

MVS No of Canceled Batch Jobs byUser Group, Daily report 412

MVS No of System Abends byAbend Code, Monthlyreport 409

MVS No of User Abends by AbendCode, Monthly report 410

MVS Number of IPLs, Daily Trendreport 465

MVS Number of TSO Users, DailyProfile report 445

MVS Paging by Subsystem, DailyTrend report 510

MVS Paging Rates, Daily Trendreport 512

MVS Percent Abended Jobs byUser Group, Monthly report 411

MVS Print Activity by User Group,Monthly Overview report 529

MVS Printer Activity, MonthlyOverview report 527, 532, 533,537, 541, 543, 545, 546, 547, 548,549, 551, 553, 554, 556, 558

MVS Printer Forms Usage,Monthly Overview report 531

MVS Response (Goal in %),Daily/Monthly Overviewreport 432

MVS Response (Goal in %),Daily/Monthly Trendreport 430

MVS Response (Goal in sec),Daily/Monthly Overviewreport 435

MVS Response (Goal in sec),Daily/Monthly Trendreport 434

MVS Response Time Distribution,Daily/Monthly Overviewreport 439

MVS Storage by Workload Type,Monthly Trend report 500

Index 955

reports (continued)MVS analysis component (continued)

MVS Storage by Workload Type,Peak Hour, Daily Trendreport 494

MVS Sysplex Overview, MonthlyTrend report 423

MVS System Overview, MonthlyTrend report 415

MVS Tape Demounts/MVSSystem, Monthly Overviewreport 516

MVS Tape Errors by Device,Monthly Overview report 517

MVS Tape Errors by Volume,Monthly Trend report 518

MVS Tape I/O by User Group,Monthly Overview report 515

MVS TSO Response Time byWorkload, Daily Profilereport 441

MVS TSO Response Time byWorkload, Daily/Monthly Trendreport 443

MVS TSO Response Time, Peakhour, Daily Trend report 444

MVS TSO Transactions byWorkload, Daily Profilereport 446

MVS TSO Transactions byWorkload, Daily/Monthly Trendreport 447

MVS TSO Transactions, Peak Hour,Daily Trend report 448

MVS Users Swapped Out andReady, Daily Profile report 420

MVS Workload by ResourceGroup, Daily/Monthly Overviewreport 428

MVS Workload by Workload Type,Monthly Trend report 421

MVS Workload for a ResourceGroup, Daily/Monthly Trendreport 426


MVSPM APPC, CPU and I/O byTransaction Class report 852

MVSPM APPC, Execution andQueueing, Hourly Trendreport 853

MVSPM Applications Waiting onENQs, Hourly Trend report 858

MVSPM Applications Waiting onENQs, Worst Case report 859

MVSPM Average CPU BusyProfile, Hourly Trend report 805

MVSPM Average CPU Busy,Daily/Hourly Trend report 803

MVSPM Average High UIC Profile,Hourly Trend report 813

MVSPM Avg CF Busy Profile,Hourly Trend report 822

MVSPM Avg CF Storage Usage,Hourly Trend report 823

reports (continued)MVS performance management

component (continued)MVSPM BMF Directory Page

Reads/Hits, Hourly Trendreport 851

MVSPM BMF Member PageReads/Hits, Hourly Trendreport 850

MVSPM Cache CU Operations byCU, Daily Overview report 893

MVSPM Cache CU Operations,Hourly Trend report 895

MVSPM Cache Hit Rates by CU,Hourly Trend report 881

MVSPM CF, Processor andStorage, Overview report 824

MVSPM CF, Request Rate,Overview report 826

MVSPM CF, Structures Details,Overview report 829, 830, 832,834

MVSPM CF, System Details,Overview report 827

MVSPM Channel Path Busyreport 868, 915

MVSPM CPU and ProcessorStorage Activity Overviewreport 793

MVSPM CPU Busy and OtherIndicators, Hourly Trendreport 806

MVSPM CPU Busy by SharedLPAR, Hourly Trend report 819

MVSPM CPU Busy by WorkloadPGNs, Hourly Trend report 838

MVSPM CPU Busy by WorkloadTypes, Hourly Trend report 837

MVSPM CPU Busy profile SharedLPARs, Hourly Trendreport 818

MVSPM CPU per I/O byWorkload PGNs, Hourly Trendreport 843

MVSPM CPU Per I/O byWorkload Type, Hourly Trendreport 842

MVSPM DASD Activity Overviewreport 801

MVSPM Data Set ActivityOverview report 905

MVSPM Data Set I/O Rate & RespTime, Hourly Trend report 907

MVSPM Data Set I/O Rate Profile,Hourly Trend report 909

MVSPM Data Set Resp TimeProfile, Hourly Trend report 910

MVSPM DFW Hit Rates by CU,Hourly Trend report 883

MVSPM Exec. Velocity Goals &Actuals, Hourly Trendreport 861

MVSPM Execution Velocity Goals& Actuals Overview report 800

MVSPM Goalmode WorkloadDescriptions report 792


component (continued)MVSPM Highest Hit Rate

Volumes, Daily Overviewreport 889

MVSPM Highest Stating RateVolumes, Daily Overviewreport 891

MVSPM I/O Rate by Workload onSelected Devices report 899

MVSPM I/O Rate by WorkloadType, Hourly Trend report 841

MVSPM I/O Rate for Devices byWorkload Type report 877

MVSPM I/O Rate for LCUs,Hourly Trend report 870

MVSPM I/O Response TimeComponents for LCUsreport 872

MVSPM I/O Response TimeComponents, DASD Devicesreport 875

MVSPM I/O Response Time forDevice, Hourly Trendreport 879

MVSPM I/O Response Time forDevices by Workload report 897

MVSPM I/O Response Time forLCUs, Hourly Trend report 871

MVSPM LPAR Management Time,Hourly Trend report 821

MVSPM Minimum Available ExpStorage, Hourly Trendreport 812

MVSPM No of Users Waiting forDevice, Daily Trend report 874

MVSPM Overall Effectiveness byCU, Daily Overview report 887

MVSPM Page Data Set Busy Time,Hourly Trend report 816

MVSPM Page Data Set DeviceResp Time, Hourly Trendreport 815

MVSPM Page Data Set ResponseTime, Hourly Trend report 814

MVSPM Page-ins by WorkloadType, Hourly Trend report 844

MVSPM Paging Activity byWorkload, Hourly Trendreport 845

MVSPM Percent of Share Used byLPARS, Hourly Trendreport 820

MVSPM Response TimeBreakdown Overviewreport 864

MVSPM Response TimeBreakdown, Hourly Trendreport 866

MVSPM Response Time byWorkload, Hourly Trendreport 847

MVSPM Response TimeDistribution report 862



component (continued)MVSPM Response Time Goals &

Actuals, Hourly Trendreport 860

MVSPM Response Time Goals vsActuals Overview report 799

MVSPM Served Service ClassesOverview report 863

MVSPM Stating Rates by CU,Hourly Trend report 885

MVSPM Storage Class I/O Rate,Hourly Trend report 912, 913

MVSPM Storage Class Resp Time,Hourly Trend report 911

MVSPM Storage Used byWorkload PGNs, Hourly Trendreport 840

MVSPM Storage Used byWorkload Type, Hourly Trendreport 839

MVSPM System Central StorageMap, Hourly Trend report 808

MVSPM System Expanded StorageMap, Hourly Trend report 810

MVSPM System Resources byWorkload Type report 835

MVSPM System Storage PagingRates, Hourly Trend report 817

MVSPM VLF Dataspace Usage,Hourly/Daily Trend report 856

MVSPM VLF Usage and Hit Ratio,Hourly/Daily Trend report 854

MVSPM Workload Descriptionsreport 791

MVSPM Workload ResourceUtilization Overview report 795

MVSPM Workload Resp TimeComponents, Hourly Trendreport 848

MVSPM Workload Response TimeComponents Overviewreport 797, 917, 919, 921, 923,925, 926, 928, 930

MVSPM XCF Activity by Path andSystem, Overview report 903

MVSPM XCF Signal Rates, HourlyTrend report 902

MVSPM XCF Statistics by System,Overview report 900

predefined report groups 24report attributes 24report ID 23source 24variables 24

SSMF records 596

type 0 297, 569type 100

subtype 0 49subtype 1 49subtype 2 49subtype 3 49

type 101 49

SMF records (continued)subtype 1 49

type 102 49type 21 297type 25 297type 26 297type 30 298type 33

subtype 1 596type 41

subtype 3 596type 42

subtype 1 596subtype 5 596, 597subtype 6 597

type 6 297, 569type 7 297type 70 298, 597type 71 299, 597type 72

subtype 1 299, 597subtype 2 597subtype 3 299

type 73 597type 74

subtype 1 598subtype 2 598subtype 3 598subtype 4 598subtype 5 598

type 75 598type 77 598type 78

subtype 1 598subtype 2 598subtype 3 598

type 79 598type 90 299type 94 299type CACHE 599

software support xivstorage group information in

reports 217

Ttables

data tablesDB2 component 29, 51DFSMS component 195, 268MVS analysis component 303MVS performance management

component 601description 19lookup tables

DB2 component 115DFSMS component 212, 275MVS analysis component 397MVS performance management

component 786naming standards, data tables 20naming standards, lookup tables 21table-name suffixes 20

tape capacity, statistics 208TCP/IP component

description 5

Tivoli Decision Support for OS/390components

DB2 component 3DFSMS component 4EREP component 4Information/Management

component 4Internet Connection Secure

Server 4Message analysis/automation 4MQSeries 5MVS analysis component 5MVS performance management

component 5OPC component 5RACF component 5TCP/IP 5Tivoli Service Desk 5Tivoli Storage Manager

(ADSM) 5VM accounting component 6VMPRF component 6

customization installationinstall the component 8make input data available 8put into production 14test the installation 13update lookup tables 11

data flowdatabase tables 19description 15record procedures 19

data tablesnaming standard, data tables 20table-name suffixes 20

description 3log definitions, description 18lookup tables

naming standard, lookuptables 21

table-name suffixes 20record definitions, description 18report groups reports

description 22predefined report groups 24report attributes 24report ID 23source 24variables 24

tablesdescription 19naming standard, data tables 20naming standard, lookup

tables 21table-name suffixes 20

Tivoli Service Desk componentdescription 5

Tivoli Storage Manager (ADSM)component

description 5

Vviews

MVS analysis componentMVS_LPAR_DV 373MVS_LPAR_MV 375

Index 957

views (continued)MVS analysis component (continued)

MVS_RESOURCE_DV 378MVS_RESOURCE_HV 377MVS_RESOURCE_MV 379MVS_WORKLOAD_DV1 382MVS_WORKLOAD_DV2 383MVS_WORKLOAD_DV3 384MVS_WORKLOAD_DV4 385MVS_WORKLOAD_HV1 380MVS_WORKLOAD_HV2 380MVS_WORKLOAD_HV3 381MVS_WORKLOAD_HV4 381MVS_WORKLOAD_MV1 386MVS_WORKLOAD_MV2 387MVS_WORKLOAD_MV3 388MVS_WORKLOAD_MV4 389MVS_WORKLOAD2_DV2 393MVS_WORKLOAD2_DV4 394MVS_WORKLOAD2_HV2 390MVS_WORKLOAD2_HV4 392MVS_WORKLOAD2_MV2 395MVS_WORKLOAD2_MV4 396


MVSPM_APPL_HV 722MVSPM_CACHE_HV 727MVSPM_CF_PROC_HV 734MVSPM_CF_REQ_HV 735MVSPM_CPU_HV 739MVSPM_DATASET_HV 744MVSPM_DEVICE_AP_HV 746MVSPM_DEVICE_AP_PV 747MVSPM_DEVICE_HV 748MVSPM_ENQUEUE_HV 751MVSPM_LPAR_HV 752MVSPM_PAGE_DS_HV 754MVSPM_PAGING_HV 756MVSPM_STORAGE_HV 762MVSPM_STORCLASS_HV 764MVSPM_SWAP_HV 766MVSPM_SYSTEM_HV 770, 773MVSPM_SYSTEM_PV 772MVSPM_WORKLOAD2_HV 776,

779MVSPM_XCF_PATH_HV 783MVSPM_XCF_SYS_HV 784

VM accounting componentdescription 6

VMPRF componentdescription 6

volume utilization, DASD 199volumes, DASD 200, 210, 272


��

Program Number: 5695-101

Printed in U.S.A.

SH19-6819-07

System Performance Feature Reference Volume I

Documents

Transcript of System Performance Feature Reference Volume I