T l Tivoli Decision Support for z/OS - IBM...Figures 1. W ebSpher e MQ for z/OS (MQSeries) component...

Tivoli® Tivoli Decision Support for z/OS

System Performance Feature ReferenceVolume II

Version 1.8.1

SH19-4494-09

��

ii System Performance Feature Reference Volume II

Contents

IBM Tivoli Tivoli Decision Support forz/OS . . . . . . . . . . . . . . . . 1Figures . . . . . . . . . . . . . . . . 2Preface . . . . . . . . . . . . . . . . 7

Who should read this book . . . . . . . . 7What this book contains . . . . . . . . . 8Publications . . . . . . . . . . . . . 8Accessibility . . . . . . . . . . . . . 11Tivoli technical training . . . . . . . . . 11Support information . . . . . . . . . . 11Conventions used in this book . . . . . . . 12Changes in this edition . . . . . . . . . 13

WebSphere MQ for z/OS (MQSeries) component . . 13Customization . . . . . . . . . . . . 14Data flow . . . . . . . . . . . . . . 14Log and record definitions . . . . . . . . 16Data tables . . . . . . . . . . . . . 16Reports . . . . . . . . . . . . . . . 36

WebSphere Message Broker component . . . . . 50Customization . . . . . . . . . . . . 50Data flow . . . . . . . . . . . . . . 51Log and record definitions . . . . . . . . 51Data tables . . . . . . . . . . . . . 52Reports . . . . . . . . . . . . . . . 59

TCP/IP for z/OS component . . . . . . . . 64Customization . . . . . . . . . . . . 65Data flow . . . . . . . . . . . . . . 67Log and record definitions . . . . . . . . 69Data tables . . . . . . . . . . . . . 70Reports . . . . . . . . . . . . . . . 95

HTTP Server for z/OS (ICSS) component . . . . 111Customization . . . . . . . . . . . . 112Data flow. . . . . . . . . . . . . . 112Log and record definitions . . . . . . . . 114Data tables . . . . . . . . . . . . . 114Reports . . . . . . . . . . . . . . 118

EREP component . . . . . . . . . . . . 121Customization . . . . . . . . . . . . 121Data flow . . . . . . . . . . . . . 122Log and record definitions . . . . . . . . 124Data tables and lookup tables . . . . . . . 125Reports . . . . . . . . . . . . . . 130

Tivoli Information Management for z/OS(INFOMAN) component. . . . . . . . . . 136

Customization . . . . . . . . . . . . 137Data flow . . . . . . . . . . . . . 151Log and record definitions . . . . . . . . 153Data tables and lookup tables . . . . . . . 154Reports . . . . . . . . . . . . . . 158

IXFP component . . . . . . . . . . . . 169Customization . . . . . . . . . . . . 170Data tables . . . . . . . . . . . . . 171Reports . . . . . . . . . . . . . . 181

Message analysis/automation component . . . . 207Customization . . . . . . . . . . . . 208

Data flow . . . . . . . . . . . . . 210Log and record definitions . . . . . . . . 212Data tables, views, and lookup tables . . . . 213Reports . . . . . . . . . . . . . . 224

Tivoli Workload Scheduler for z/OS (OPC)component . . . . . . . . . . . . . . 240

Customization . . . . . . . . . . . . 241Data flow . . . . . . . . . . . . . 243Log and record definitions . . . . . . . . 244Data tables, views, and lookup tables . . . . 245Reports . . . . . . . . . . . . . . 258

RACF component . . . . . . . . . . . . 278Customization . . . . . . . . . . . . 280Data flow . . . . . . . . . . . . . 285Log and record definitions . . . . . . . . 287Data tables and lookup tables . . . . . . . 289Reports . . . . . . . . . . . . . . 321

VM accounting component . . . . . . . . . 362Customization . . . . . . . . . . . . 363Data flow . . . . . . . . . . . . . 363Log and record definitions . . . . . . . . 364Data tables . . . . . . . . . . . . . 365Reports . . . . . . . . . . . . . . 366

z/VM Performance component . . . . . . . 373Customization . . . . . . . . . . . . 375Data flow . . . . . . . . . . . . . 376Log and record definitions . . . . . . . . 377Data tables, views, and lookup tables . . . . 379Reports . . . . . . . . . . . . . . 403

Linux on zSeries component . . . . . . . . 441Customization . . . . . . . . . . . . 442Data flow . . . . . . . . . . . . . 448Data tables and lookup tables . . . . . . . 449Reports . . . . . . . . . . . . . . 464

Lotus Domino for z/OS component . . . . . . 472Customization . . . . . . . . . . . . 473Data flow . . . . . . . . . . . . . 474Log and record definitions . . . . . . . . 476Data tables and lookup table . . . . . . . 476Reports . . . . . . . . . . . . . . 486

WebSphere Application Server traditionalcomponent . . . . . . . . . . . . . . 496

Customization . . . . . . . . . . . . 497Log and record definitions . . . . . . . . 499Implementing the WebSphere ApplicationServer component . . . . . . . . . . . 505Data flow . . . . . . . . . . . . . 508Data tables and views . . . . . . . . . 512Reports . . . . . . . . . . . . . . 565

WebSphere Application Server Liberty component 576Customization . . . . . . . . . . . . 576Log and record definitions . . . . . . . . 577Data flow . . . . . . . . . . . . . 578Data tables and views . . . . . . . . . 580

z/OS Interval Job/Step Accounting component . . 584Customization . . . . . . . . . . . . 585

iii

Data flow . . . . . . . . . . . . . 586Data tables, views, and lookup tables . . . . 587Reports . . . . . . . . . . . . . . 600

Tivoli Performance Modeler for z/OS component 604Customization . . . . . . . . . . . . 604Data flow . . . . . . . . . . . . . 604Data tables . . . . . . . . . . . . . 605

TPM Extract function. . . . . . . . . . 607Appendixes . . . . . . . . . . . . . . 608

Appendix. Support information . . . . . . 608Notices . . . . . . . . . . . . . . 612Bibliography . . . . . . . . . . . . 615Glossary . . . . . . . . . . . . . . 616

iv System Performance Feature Reference Volume II

IBM Tivoli Tivoli Decision Support for z/OS

System Performance Feature Reference Volume II

SH19-4494–09

Note

Before using this information and the product it supports, read the information in Notices.

Eleventh Edition (October 2017)

This edition applies to version 1, release 8, modification level 1 of Tivoli Decision Support for z/OS (program number 5698-B06) and to all subsequent releases and modifications until otherwise indicated in new editions.

Copyright International Business Machines Corporation 2009, 2017.

US Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Topics:v “Figures” on page 2v “Preface” on page 7v “WebSphere MQ for z/OS (MQSeries) component” on page 13v “WebSphere Message Broker component” on page 50v “TCP/IP for z/OS component” on page 64v “HTTP Server for z/OS (ICSS) component” on page 111v “EREP component” on page 121v “Tivoli Information Management for z/OS (INFOMAN) component” on page

136v “IXFP component” on page 169v “Message analysis/automation component” on page 207v “Tivoli Workload Scheduler for z/OS (OPC) component” on page 240v “RACF component” on page 278v “VM accounting component” on page 362v “z/VM Performance component” on page 373v “Linux on zSeries component” on page 441v “Lotus Domino for z/OS component” on page 472v “WebSphere Application Server traditional component” on page 496v “WebSphere Application Server Liberty component” on page 576v “z/OS Interval Job/Step Accounting component” on page 584v “Tivoli Performance Modeler for z/OS component” on page 604v “Appendixes” on page 608

1

Figures1. WebSphere MQ for z/OS (MQSeries) component data flow2. Example of an MQSeries CICS Accounting, Daily Report3. Example of an MQSeries IMS Accounting, Daily Report (partial view)4. Example of an MQSeries MVS Accounting, Daily Report5. Example of an MQSeries Message Manager Statistics, Daily Report (partial

view)6. Example of an MQSeries Data Manager Statistics, Daily Report7. Example of an MQSeries Buffer Manager Statistics, Daily Report (partial view)8. Example of an MQSeries Log Manager Statistics, Daily Report9. Example of an MQSeries DB2 BLOB Statistics, Daily Report

10. Example of an MQSeries DB2 Manager Statistics, Daily Report11. Example of an MQSeries short on storage and log manager counts, Daily

Report12. Example of an MQSeries Wait and Suspend Times, Daily Report13. Example of an MQSeries Message Sizes, Daily Report14. Example of an MQSeries Data Manager Indicators, Daily Report15. WebSphere Message Broker component data flow16. Example of Daily accounting data for Message Flows17. Example of Daily accounting data for Nodes18. Example of Daily accounting data for Threads19. Example of Daily accounting data for Terminals (partial view)20. TCP/IP for z/OS component data flow21. Example of TCP/IP FTP Transmission report22. Example of a TCP/IP ICMP TCPIPSTATISTICS Input report23. Example of a TCP/IP ICMP TCPIPSTATISTICS Output report24. Example of a TCP/IP Interface Statistics report25. Example of a TCP/IP IP TCPIPSTATISTICS Error report26. Example of a TCP/IP IP TCPIPSTATISTICS hourly report27. Example of a TCP/IP TCPIPSTATISTICS Daily report28. Example of a TCP/IP TCP TCPIPSTATISTICS report29. Example of a TCP/IP TCP Connection Performance report30. Example of a TCP/IP TCP Server Port Connection Statistics report31. Example of TCP/IP TELNET Server Active Logon by Hour report32. Example of TCP/IP TELNET server bytes traffic report33. Example of TCP/IP TELNET AVG Connection Time to Application report34. Example of a TCP/IP UDP Sockets Traffic, Daily report35. Example of a TCP/IP UDP TCPIPSTATISTICS report36. HTTP Server for z/OS (ICSS) component data flow37. Example of an HTTP Server for z/OS (ICSS) configuration report (partial

view)38. Example of an HTTP Server for z/OS (ICSS) performance hourly report

(partial view)39. Example of an HTTP Server for z/OS (ICSS) performance daily report (partial

view)

2 System Performance Feature Reference Volume II

40. Example of an HTTP Server for z/OS (ICSS) performance monthly report(partial view)

41. EREP component data flow42. EREP lookup table data43. Example of an EREP DASD Errors by Device Type, Monthly Trend report44. Example of an EREP DASD Errors by DASD Group, Monthly Trend report45. Example of an EREP DASD Errors by Control Unit, Monthly Trend report46. Example of an EREP VTAM Errors by Resource, Monthly Trend report47. Example of an EREP IPL and Downtime Summary, Daily report48. Report format table DRLJRFT2 (Part 1 of 12)49. Report format table DRLJRFT2 (Part 2 of 12)50. Report format table DRLJRFT2 (Part 3 of 12)51. Report format table DRLJRFT2 (Part 4 of 12)52. Report format table DRLJRFT2 (Part 5 of 12)53. Report format table DRLJRFT2 (Part 6 of 12)54. Report format table DRLJRFT2 (Part 7 of 12)55. Report format table DRLJRFT2 (Part 8 of 12)56. Report format table DRLJRFT2 (Part 9 of 12)57. Report format table DRLJRFT2 (Part 10 of 12)58. Report format table DRLJRFT2 (Part 11 of 12)59. Report format table DRLJRFT2 (Part 12 of 12)60. DRLJCOIN job for collecting Tivoli Information Management for z/OS data61. Tivoli Information Management for z/OS (INFOMAN) component data flow62. Tivoli Information Management for z/OS (INFOMAN) lookup table data63. Example of an INFOMAN Problem Cause, Monthly Overview report64. Example of an INFOMAN Problems, Monthly Overview report65. Example of an INFOMAN Problems, Daily Trend report66. Example of an INFOMAN Problems Closed, Monthly Overview report67. Example of an INFOMAN Problems Not Closed, Weekly Overview report68. Example of an INFOMAN Change Successes, Monthly Overview report69. Example of an INFOMAN Changes, Monthly Overview report70. Example of an INFOMAN Changes, Daily Trend report71. Example of an INFOMAN Changes Closed, Monthly Overview report72. Example of an INFOMAN Changes Not Closed, Weekly Overview report73. Example of an INFOMAN Problems and Changes, Monthly Trend report74. Example of part of an IXFP Channel Interface Statistic, Overview report75. Example of part of an IXFP Device Performance per Device ID report76. Example of part of an IXFP Device Performance per Volser report77. Example of part of an IXFP Device Utilization, Hourly Trend report78. Example of an IXFP Device DASD/Cache Transfer, Daily Trend report79. Example of part of an IXFP Device Performance, Hourly Trend report80. Example of an IXFP Device Utilization, Monthly Trend report81. Example of part of an IXFP Drive Utilization, Hourly Trend report82. Example of an IXFP Drive Utilization, Daily Trend report83. Example of part of an IXFP Deleted Data Space Release, Daily Trend report

IBM Tivoli Tivoli Decision Support for z/OS 3

84. Example of an IXFP Subsystem Space Utilization, Daily Trend report85. Example of an IXFP Subsystem Information, Daily Trend report86. Example of part of an IXFP Space Utilization, Hourly Trend report87. Message analysis/automation component data flow88. Message analysis/automation lookup table data89. Example of an MAA Messages From Commands (JES2), Daily report90. Example of an MAA Messages by Console ID, Daily report91. Example of an MAA Most Frequent Messages (JES2), Daily report92. Example of an MAA Most Frequent Messages (JES3), Daily report93. Example of an MAA Messages Passed to NetView (JES2), Daily report94. Example of an MAA Most Frequent Messages With Text, Daily report95. Example of an MAA Most Frequent Nonsuppressed Messages, Daily report96. Example of an MAA Most Frequent Messages by Type (JES2), Daily report97. Example of an MAA Most Frequent Messages by Type (JES3), Daily report98. Example of an MAA Messages by Route Code (JES2), Daily report99. Example of an MAA Messages by Route Code (JES3), Daily report100. Example of an MAA Messages by JES Complex, Daily report101. Example of an MAA Most Frequent Messages (NetView), Daily report102. Example of an MAA Messages Passed via the SSI (NetView), Daily report103. Example of an MAA Messages by NetView Operator (NetView), Daily report104. Tivoli Workload Scheduler for z/OS (OPC) component data flow105. Tivoli Workload Scheduler for z/OS (OPC) lookup table data106. Example of an OPC Operations Ended-in-error by Workstation report107. Example of an OPC Operations Ended-in-error by Error Code report108. Example of an OPC Operation Events by Application Owner ID report109. Example of an OPC Operation Complete/Ended-in-error Events report110. Example of an OPC Operations for Specific Job Name report111. Example of an OPC Reruns per Application, Worst Case report112. Example of an OPC Number of Reruns, Monthly Trend report113. Example of an OPC MCP Events per Caller, Monthly Overview report114. Example of an OPC Missed-Feedback Operations, in Percent report115. Example of an OPC Number of Jobs Processed, Monthly Trend report116. Example of an OPC Tracking Times by Event Type, Daily Trend report117. Example of an OPC Missed Deadline by Application Owner ID report118. Example of an OPC Missed Deadline by Application Owner ID report119. Example of an OPC Reruns by Operation Number, Worst Case report120. RACF component structure121. RACF data flow122. RACF lookup table data123. Example of a RACF Logon/Job Failures report124. Example of a RACF Command Failures - Auditor report125. Example of a RACF SPECIAL User Commands - Auditor report126. Example of a RACF AUDITOR User Commands - Auditor report127. Example of a RACF OPERATIONS User Access - Auditor report128. Example of a RACF Resource Access Failures report


129. Example of a RACF Resource Accesses report130. Example of a RACF SUPERUSER Security Commands - Auditor report131. Example of a RACF OpenEdition Resource Accesses report132. Example of a RACF OpenEdition Resource Accesses Failures report133. Example of a RACF Initialization report134. Example of a RACF Class Initialization report135. Example of a RACF Terminals with Excessive Incorrect Passwords report136. Example of a RACF Users with Excessive Incorrect Passwords report137. Example of a RACF All Events for a Specific User report138. Example of a RACF Data Sets with a Specific Name Access report139. Example of a RACF Data Sets with Particular Authority report140. Example of a RACF Resources Accessed Because Installation Exit report141. Example of a RACF Resources Accessed Because Warning Mode report142. Example of a RACF Generic Profiles Used for Resource Access report143. Example of a RACF Number of Profiles in the Database report144. Example of a RACF Group List report145. Example of a RACF Users with Particular System Privileges report146. Example of a RACF Users with Particular Group Level Privileges report147. Example of a RACF Users Currently Revoked report148. Example of a RACF Users Last Defined report149. Example of a RACF Users with NOINTERVAL Specified report150. Example of a RACF Users with Too Many Group Connections report151. Example of a RACF Users Members of SYS1 report152. Example of a RACF Dataset Profiles for Each HLQ report153. Example of a RACF Dataset Profiles with UACC Other than NONE report154. Example of a RACF Dataset Profiles in WARNING Mode report155. Example of a RACF Dataset Standard ACL with ID(*) Not NONE report156. Example of a RACF Dataset Condit. ACL with ID(*) Not NONE report157. Example of a RACF GR Number of Profiles for Each Class report158. Example of a RACF GR Discrete Profiles with Wild Characters report159. Example of a RACF GR Profiles with UACC Other than NONE report160. Example of a RACF GR Profiles in WARNING Mode report161. Example of a RACF GR Profiles Standard ACL with ID(*) not NONE report162. Example of a RACF Dataset Condit. ACL with ID(*) Not NONE report163. VM accounting component data flow164. Example of a VM Accounting Users Grouped by Account Number report165. Example of a VM Accounting Users Grouped by CPU Usage report166. Example of a VM Accounting Total and Virtual CPU Usage report167. Example of a VM Accounting Users Grouped by Group Name report168. Example of a VM Accounting Summary Based on Group Name report169. z/VM Performance component data flow170. Example of a z/VM System Processor Usage, Hourly report171. Example of a VMPRF System Busy Distribution, Hourly report172. Example of a z/VM System Page and Spool Counts, Hourly report173. Example of a z/VM System Exp Stor and Paging Activity, Hourly report


174. Example of a z/VM System Instruction Rate, Hourly report175. Example of a z/VM System Instruction Counts, Hourly report176. Example of a z/VM System MIPS Capacity by LPAR, Daily report177. Example of a z/VM Processor Usage Distribution, Hourly report178. Example of a z/VM Processor Busy Distribution, Hourly report179. Example of a z/VM Processor Page and Spool Activity, Hourly report180. Example of a z/VM Processor Storage Activity, Hourly report181. Example of a z/VM Processor Instruction Rate, Hourly report182. Example of a z/VM Processor Instruction Counts, Hourly report183. Example of a z/VM User Real and Virt Processor Usage, Monthly report184. Example of a z/VM User Paging and Spooling, Monthly report185. Example of a z/VM User IUCV and VMCF Counts, Monthly report186. Example of a z/VM Heaviest Users of the Processor, Monthly report187. Example of a VMPRF Heaviest Users of DASD, Monthly report188. Example of a z/VM Heaviest Users of Paging, Monthly report189. Example of a z/VM Processor Usage by User Class, Monthly report190. Example of a z/VM Paging by User Class, Monthly report191. Example of a z/VM IUCV and VMCF Usage by User Class, Monthly report192. Example of a z/VM Most-Used DASD by Start Subchannel Rate report193. Example of a z/VM Slowest DASD by Response Time report194. Example of a z/VM DASD With Longest Queues report195. Example of a z/VM Least Used or not Used DASD Devices report196. Example of a z/VM Least Used DASD Devices report197. Example of a z/VM Configuration, Level and Storage, Daily report198. Example of a z/VM Configuration, Level and IPL, Daily report199. Linux on zSeries overview200. Linux on zSeries data flow201. Example of a zLinux Filesystem Usage Daily Trend report202. Example of a zLinux Processes Daily Breakdown report203. Example of a zLinux Acct Resource by User, Daily Overview report204. Example of a zLinux Acct User Connect Info, Daily Overview report205. Example of a zLinux Perf Statistics All Systems, Daily Overview report206. Example of a zLinux Perf Disk I/O for System, Daily Overview report207. Example of a zLinux Hardware Configuration, Daily Overview report208. Example of a zLinux Software Configuration, Daily Overview report209. Lotus Domino for z/OS component data flow210. Example of a Domino I/O &Access Statistics, Hourly Report211. Example of a Domino Messages Statistics, Daily Report212. Example of a Domino Transaction Statistics, Hourly Report213. Example of a Domino Server DB Cache and Buffer Pool Statistics Report214. Example of a Domino General Server Statistics, Daily Report215. Example of a WebSphere Application Server Statistics, Daily Trend report

(partial view)216. Example of a WebSphere Application Server Session Statistics, Daily Trend

(partial view)


217. Example of a WebSphere Application Server Workload Statistics, Daily Trend(partial view)

218. Example of a WebSphere Application Server JVM Heap Statistics, DailyTrend (partial view)

219. Example of a WebSphere Application Server User Credentials Statistics report(partial view)

220. Example of a WebSphere Application Server Web Application statistics, DailyTrend report (partial view)

221. Example of WebSphere Application Server HTTP Statistics, Daily Trend(partial view)

222. Example of a WebSphere J2EE Container Statistics, Daily Trend report223. WebSphere Application Server Liberty component data flow224. z/OS Interval Job/Step Accounting Data Flow225. Example of a Job Daily Resource Consumption report (partial view)226. Example of a Job Step Duration and CPU Consumption report227. Example of a Job Running Resource Consumption, Daily report (partial

view)

PrefaceThe System Performance Feature Reference is divided into two volumes. This book isVolume II.

This book provides reference information for the System Performance feature ofIBM® Tivoli® Decision Support for z/OS® (hereafter also referred to as TivoliDecision Support for z/OS). 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 z/OS DB2® tablesv DB2 tables that Tivoli Decision Support for z/OS uses to store performance datav Predefined reports that Tivoli Decision Support for z/OS creates from

performance data

You should use this book in conjunction with the System Performance Feature Guide.

The following terms are used interchangeably throughout this book:v MVS™, OS/390®, and z/OS.v OPC, OPC/ESA, Tivoli Workload Scheduler for z/OS, and TWS.v TCP/IP and TCP/IP for z/OS.v VM and z/VM® .v WebSphere® MQ for z/OS and MQSeries® .

Who should read this book

System Performance Feature Reference Volume II is intended for those who analyze theperformance of z/OS and z/VM systems, and for those who are responsible forestablishing or meeting organization-wide service-level objectives for z/OS orz/VM systems. System Performance Feature Reference Volume II is intended for bothTivoli Decision Support for z/OS administrators (primarily as a reference to table


and column descriptions) and users with a variety of backgrounds who want touse Tivoli Decision Support for z/OS to analyze z/OS or z/VM performance data.

The products monitored are listed in System Performance Feature Reference Volume I.

What this book containsThis book contains information about the following System Performance featurecomponents:v WebSphere MQ for z/OS (MQSeries) componentv WebSphere Message Broker componentv TCP/IP for z/OS componentv HTTP Server for z/OS (ICSS) componentv EREP componentv Tivoli Information Management for z/OS (INFOMAN) componentv IXFP componentv Message analysis/automation componentv Tivoli Workload Scheduler for z/OS (OPC) componentv RACF componentv VM accounting componentv z/VM Performance componentv Linux on zSeries componentv Lotus Domino for z/OS componentv WebSphere Application Server traditional componentv “WebSphere Application Server Liberty component” on page 576v z/OS Interval Job/Step Accounting componentv Tivoli Performance Modeler for z/OS component

Each part describes one component and provides some or all of the followinginformation for that component:v "Customization" describes the steps necessary to set up the component for your

installation.v "Data flow" describes the flow of data from log records to reports for the

component.v "Log and record definitions" lists the supported logs and the records used from

the logs.v "Data tables and lookup tables" describes the DB2 tables in the Tivoli Decision

Support for z/OS database provided with the component.v "Reports" describes each report supplied with the component.

PublicationsThis section lists publications in the Tivoli Decision Support for z/OS library andany other related documents. It also describes how to access Tivoli publicationsonline, how to order Tivoli publications, and how to submit comments on Tivolipublications.

Tivoli Decision Support for z/OS libraryThe following documents are available in the Tivoli Decision Support for z/OSlibrary:v Resource Accounting for z/OS, SH19-4495


Provides information for users who want to use Tivoli Decision Support forz/OS to collect and report performance data generated by the ResourceAccounting for z/OS.

v Administration Guide and Reference, SH19-6816Provides information about initializing the Tivoli Decision Support for z/OSdatabase and customizing and administering Tivoli Decision Support for z/OS.

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.

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 Guide to Reporting, 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 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 Language Guide and Reference, SH19-6817Provides information for administrators, performance analysts, andprogrammers who are responsible for maintaining system log data and reports.

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

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 Reference, 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 z/OS to analyze z/OS, z/VM®,zLinux, and their subsystems, performance data.

v System Performance Feature Reference Volume II, SH19-4494


Provides information for administrators and users with a variety of backgroundswho want to use Tivoli Decision Support for z/OS to analyze z/OS, z/VM,zLinux, and their subsystems, performance data.

v Usage and Accounting Collector User Guide, SC23-7966Provides information about the functions and features of the Usage andAccounting Collector.

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

Accessing terminology onlineThe Tivoli Software Glossary includes definitions for many of the technical termsrelated to Tivoli software. The Tivoli Software Glossary is available, in English only,at the following Web site:

http://publib.boulder.ibm.com/tividd/glossary/tivoliglossarymst.htm

The IBM Terminology Web site consolidates the terminology from IBM productlibraries in one convenient location. You can access the Terminology Web site at thefollowing Web address:

http://www.ibm.com/ibm/terminology

Using LookAt to look up message explanationsLookAt is an online facility that lets you look up explanations for most of the IBMmessages you encounter, as well as for some system abends (an abnormal end of atask) and codes. Using LookAt to find information is faster than a conventionalsearch because in most cases LookAt goes directly to the message explanation.

You can use LookAt from the following locations to find IBM messageexplanations from z/OS elements and features, z/VM, VSE/ESA™, and Clustersfor AIX® and Linux®:v The internet. You can access IBM message explanations directly from the LookAt

Web site at:http://www.ibm.com/eserver/zseries/zos/bkserv/lookat/

v Your z/OS TSO/E host system. You can install code on your z/OS or z/OS.esystems to access IBM message explanations, using LookAt from a TSO/Ecommand line (for example, TSO/E prompt, ISPF, or z/OS UNIX® SystemServices running OMVS).

v Your Microsoft® Windows® workstation. You can install code to access IBMmessage explanations on the (SK3T-4269), using LookAt from a MicrosoftWindows DOS command line.

v Your wireless handheld device. You can use the LookAt Mobile Edition with ahandheld device that has wireless access and an Internet browser (for example,Internet Explorer for Pocket PCs, Blazer, or Eudora for Palm OS, or Opera forLinux handheld devices.) Link to the LookAt Mobile Edition from the LookAtWeb site.

You can obtain code to install LookAt on your host system or Microsoft Windowsworkstation from:v A CD-ROM in the z/OS Collection, (SK3T-4269)v The z/OS and Software Products DVD Collection, (SK3T-4271)


http://publib.boulder.ibm.com/tividd/glossary/tivoliglossarymst.htm

http://www.ibm.com/ibm/terminology

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

v The LookAt Web site (click Download and then select the platform, release,collection, and location that suit your needs). More information is available inthe LOOKAT.ME files available during the download process.

Accessing publications onlineIBM posts publications for this and all other Tivoli products, as they becomeavailable and whenever they are updated, to the Tivoli software information centerWeb site. Access the Tivoli software information center by first going to the Tivolisoftware library at the following Web address:

http://www.ibm.com/software/tivoli/library/

Scroll down and click the Product manuals link. In the Tivoli Technical ProductDocuments Alphabetical Listing window, click the Tivoli Decision Support forz/OS link to access the product library at the Tivoli software information center.

Note: If you print PDF documents on other than letter-sized paper, set the optionin the File ” Print window that allows Adobe® Reader to print letter-sized pageson your local paper.

Ordering publicationsOrdering publications

You can order many Tivoli publications online at the following Web site:http://www.elink.ibmlink.ibm.com/publications/servlet/pbi.wss

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, contact your software account representative to order Tivolipublications.

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

Tivoli technical trainingFor Tivoli technical training information, refer to the following IBM TivoliEducation Web site:

http://www.ibm.com/software/tivoli/education/

Support informationIf you have a problem with your IBM software, you want to resolve it quickly. IBMprovides the following ways for you to obtain the support you need:v Searching knowledge bases: You can search across a large collection of known

problems and workarounds, Technotes, and other information.


http://www.ibm.com/software/tivoli/library/

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

http://www.ibm.com/software/tivoli/education/

v Obtaining fixes: You can locate the latest fixes that are already available for yourproduct.

v Contacting IBM Software Support: If you still cannot solve your problem, andyou need to work with someone from IBM, you can use a variety of ways tocontact IBM Software Support.

For more information about these three ways of resolving problems, see Appendix.Support information.

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

The following terms are used interchangeably throughout this book:v MVS, OS/390, and z/OS.v OPC, OPC/ESA, Tivoli Workload Scheduler for z/OS, and TWS.v TCP/IP and TCP/IP for z/OS.v VM and z/VM.v WebSphere MQ for z/OS and MQSeries.

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

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


Changes in this editionThis list summarizes the major changes made since the last release of TDS:

Part 15. WebSphere Application Server componentA new Request Activity Subcomponent has been added with:v A new input record added to Log and record definitions.v New WASACT_REQ*_H, _D, _M data tables & views have been added

to Data tables and views.

Part 17. Tivoli Performance Modeler for z/OS componentThis part has been added with:v Customization.v Data flow.v Data tables.v TPM Extract function.

WebSphere MQ for z/OS (MQSeries) componentCustomization

Making input data available

Data flow

Log and record definitions

Data tables

MQS_ACCNT_CICS_T, _D, _M

MQS_ACCNT_T, _D, _M

MQS_ACCNT_IMS_T, _D, _M

MQS_ACCNT_QUEUE_T, _D, _M

MQS_ACCNT_TASK_T, _D, _M

MQS_BUFFER_T, _D, _M

MQS_COUPL_FAC_T, _D, _M

MQS_DATA_T, _D, _M

MQS_DB2_T, _D, _M

MQS_LOCK_T, _D, _M

MQS_LOGMGR_T, _D, _M

MQS_MSG_T, _D, _M

MQS_STORAGE_T, _D, _M

Reports


MQSeries CICS Accounting, Daily

MQSeries IMS Accounting, Daily

MQSeries Accounting, Daily

MQSeries Message Manager Statistics, Daily

MQSeries Data Manager Statistics, Daily

MQSeries Buffer Manager Statistics, Daily

MQSeries Log Manager Statistics, Daily

MQSeries DB2 BLOB Statistics, Daily

MQSeries DB2 Manager Statistics, Daily

MQSeries Short On Storage and Log Manager Counts, Daily

MQSeries Wait and Suspend Times, Daily

MQSeries Message Sizes, Daily

MQSeries Data Manager Indicators, Daily

CustomizationBefore you can use the WebSphere MQ for z/OS (MQSeries) component to collectdata and create reports, you must customize the component by making input dataavailable.

Making input data availableEnsure that the appropriate SMF record types are written. Check that theCSQ6SYSP macro has the following two parameters set in the correct way:

SMFACCTSpecifies whether SMF accounting data is collected when WebSphere MQfor z/OS is started. (SMF type 116).

SMFSTATSpecifies whether SMF statistics data is collected when WebSphere MQ forz/OS is started. (SMF type 115).

Data flowThe WebSphere MQ for z/OS (MQSeries) component collects records from the SMFdata set and stores extracted and summarized data in the Tivoli Decision Supportfor z/OS database. The reporting function extracts data from the database andcreates the reports that you request through the reporting dialogs. Figure 1 showsan overview of the flow of data through the WebSphere MQ for z/OS (MQSeries)component.


Figure 1. WebSphere MQ for z/OS (MQSeries) component data flow


Log and record definitionsThe WebSphere MQ for z/OS (MQSeries) component collects records from thesystem management facility (SMF) logs. WebSphere MQ for z/OS writes recordsthat contain information about MQI requests, various object requests, buffermanager statistics, log manager data, DB2 manager data, coupling facility managerdata, and accounting data at queue and thread level.

MQS_115_1Contains system information related to the SMF logs and storage pools.

MQS_115_2Contains WebSphere MQ for z/OS information about the number ofmessages, the WebSphere MQ for z/OS buffer, paging information, andstatistics for lock manager, DB2 manager, and coupling facility manager.

MQS_116Contains accounting data for WebSphere MQ for z/OS message manager.

MQS_116_1Contains thread-level and queue-level accounting data for each task usingWebSphere MQ for z/OS.

MQS_116_2Contains additional queue-level accounting data (if the tasks used morequeues than could fit in the MQS_116_1 record).

For a complete description of these records, see the WebSphere MQ for z/OS SystemSetup Guide.

Data tablesThis chapter describes the data tables used by the WebSphere MQ for z/OS(MQSeries) component.

MQS_ACCNT_CICS_T, _D, _MThese tables provide detailed, daily, and monthly accounting data for the CICSapplication environment. They contain data from SMF type 116.

The default retention periods for these tables are:

MQS_ACCNT_CICS_T7 days

MQS_ACCNT_CICS_D30 days

MQS_ACCNT_CICS_M765 days

Column name Data type Description

DATE K DATE The date when the record was written. From DTE.

TIME K TIME The time when the record was written. From TME.Applies only to _T.

PERIOD_NAME K CHAR(8) The name of the period. It is derived using theSM116SID, SM116DTE, and SM116TME as parametersin the period function.

MVS_SYSTEM_ID K CHAR(4) The definition of the MVS subsystem on which therecords were collected.

MQSERIES_SUB_ID K CHAR(4) The WebSphere MQ for z/OS subsystem ID.



SUBSYSTEM_NAME K CHAR(4) The subsystem name.

USERID_MVS_JOB K CHAR(8) The user ID associated with the MVS job.

CONNECT_NAME K CHAR(8) The connection name.

USERID_TRANS K CHAR(8) The user ID associated with the transaction.

CICS_THREAD_NR K CHAR(8) The CICS thread number.

CICS_TRAN_NAME K CHAR(4) The CICS transaction name.

CICS_TASK_NR CHAR(8) The CICS task number.

INPUT_RECORDS INTEGER The number of records read.

CONNECTION CHAR(22) The type of connecting system.

CPU_TIME_SEC FLOAT The CPU time used in seconds.

MQPUT_REQ_A INTEGER The number of MQPUT requests for messages oflength 0 through 99 bytes.

MQPUT_REQ_B INTEGER The number of MQPUT requests for messages oflength 100 through 999 bytes.

MQPUT_REQ_C INTEGER The number of MQPUT requests for messages oflength 1000 through 9999 bytes.

MQPUT_REQ_D INTEGER The number of MQPUT requests for messages oflength greater than or equal to 10000 bytes.

MQGET_REQ_A INTEGER The number of MQGET requests for messages oflength 0 through 99 bytes.

MQGET_REQ_B INTEGER The number of MQGET requests for messages oflength 100 through 999 bytes.

MQGET_REQ_C INTEGER The number of MQGET requests for messages oflength 1000 through 9999 bytes.

MQGET_REQ_D INTEGER The number of MQGET requests for messages oflength greater than or equal to 10000 bytes.

MQS_ACCNT_T, _D, _MThese tables provide detailed, daily, and monthly accounting data for MVS batchor TSO environment. They contain data from SMF type 116.


MQS_ACCNT_T7 days

MQS_ACCNT_D30 days

MQS_ACCNT_M765 days











CONNECT_NAME K CHAR(8) Connection name.













MQS_ACCNT_IMS_T, _D, _MThese tables provide detailed, daily, and monthly accounting data for the IMSenvironment. They contain data from SMF type 116.


MQS_ACCNT_IMS_T7 days

MQS_ACCNT_IMS_D30 days

MQS_ACCNT_IMS_M765 days











CONNECT_NAME K CHAR(8) The connection name.


ACCOUNT_TOKEN K CHAR(22) The accounting token.


IMS_PST_REG_ID CHAR(4) The IMS partition specification table region identifier.

IMS_PSB_NAME CHAR(8) The IMS program specification block name.











MQS_ACCNT_QUEUE_T, _D, _MThese tables provide detailed, daily, and monthly accounting data. They containdata from SMF type 116, subtypes 1 and 2.


MQS_ACCNT_QUEUE_T7 days

MQS_ACCNT_QUEUE_D30 days

MQS_ACCNT_QUEUE_M765 days









CONNECTION_NAME K CHAR(8) Name of the connection.

ORIG_PRIM_AUTHID K CHAR(8) Original primary authorization ID.

RRS_CONN_NETW_ID K CHAR(17) Network ID for RRS connections.

MMOVER_CHAN_NAME K CHAR(20) Channel name for MVS mover.

MMOVER_LCONN_NAME K CHAR(48) Long connection name for MVS mover.

PRIMARY_AUTHID K CHAR(8) Primary authorization ID.

CORRELATOR_ID K CHAR(16) Correlator ID.

MQOPEN_QUEUE_NAME K CHAR(48) Queue name as specified in OD of MQOPEN request.

QUEUE_BASE_NAME K CHAR(48) Base queue name to which OBJNAME resolved.

TASK_CONNECTED CHAR(18) The connection type for this task:

v 0 - Internal task

v 1 - CICS Attach

v 2 - MVS/TSO Attach

v 3 - IMS Control region

v 4 - IMS MPP region

v 5 - Command Server

v 6 - MVS Mover

v 7 - RRS Stub

v 8 - IGQ agent

QUEUE_TYPE INTEGER Type of queue:

v 1 - MQQT_LOCAL

v 2 - MQQT_MODEL

v 3 - MQQT_ALIAS

v 6 - MQQT_REMOTE

v 7 - MQQT_CLUSTER

QUEUE_QSGDISP INTEGER The QSGDISP of the queue.

MQCLOS_CALLS INTEGER Number of MQCLOSE requests that were processed.

MQCLOS_CPU_TIME FLOAT Total CPU time that was spent performing MQCLOSErequests.

MQCLOS_ELAPS_TIME FLOAT Total elapsed time that was spent performingMQCLOSE requests.

MQOPEN_CALLS INTEGER Number of MQOPEN requests that were processed.

MQOPEN_CPU_TIME FLOAT Total CPU time that was spent performing MQOPENrequests.

MQOPEN_ELAPS_TIME FLOAT Total elapsed time that was spent performingMQOPEN requests.

MQGET_CALLS INTEGER Number of MQGET requests that were processed.

MQGET_CPU_TIME FLOAT Total CPU time that was spent performing MQGETrequests.



MQGET_ELAPS_TIME FLOAT Total elapsed time that was spent performing MQGETrequests.

MQGET_BROWSE_ANY INTEGER Number of MQGET BROWSE ANY requests.

MQGET_BROWSE_SPEC INTEGER Number of MQGET BROWSE SPECIFIC requests.

MQGET_DESTRU_ANY INTEGER Number of MQGET DESTRUCTIVE ANY requests.

MQGET_DESTRU_SPEC INTEGER Number of MQGET DESTRUCTIVE SPECIFICrequests.

MQGET_UNACCOUNTAB INTEGER Number of undeterminable MQGET requests.

MQGET_WRLOG_WTIME FLOAT Elapsed time waiting for log writes during MQGET.

MQGET_WRLOG_REQS INTEGER Number of log writes during MQGET.

MQGET_RDPGS_WTIME FLOAT Elapsed time waiting for pageset reads duringMQGET.

MQGET_RDPGS_REQS INTEGER Number of pageset reads during MQGET.

MQGET_SUSP_WTIME FLOAT Elapsed time suspended waiting for MQGET.

MQGET_SUSPENDS INTEGER Number of times suspended during MQGET.

MQGET_PAGES_SKIP INTEGER Number of pages skipped during MQGET.

MQGET_MSGS_SKIP INTEGER Number of messages skipped during MQGET.

MQGET_MSG_PERSIS INTEGER Number of persistent messages got by MQGET.

MQGET_EX_MSGS_PRC INTEGER Number of expired messages that were processedduring MQGETs.

MQGET_DESTRUCTIVE INTEGER Number of successful destructive MQGET calls.

MQGET_FORCE_WTIME FLOAT Elapsed time waiting for force log writes duringMQGET.

MQGET_FORCE_WRITE INTEGER Number of forced log writes during MQGET.

MQPUT_CALLS INTEGER Number of MQPUT requests that were processed.

MQPUT_CPU_TIME FLOAT Total CPU time that was spent performing MQPUTrequests.

MQPUT_ELAPS_TIME FLOAT Total elapsed time that was spent performing MQPUTrequests.

MQPUT_MSG_PERSIS INTEGER Number of persistent messages got by MQPUT.

MQPUT_WRLOG_WTIME FLOAT Elapsed time waiting for log writes during MQPUT.

MQPUT_WRLOG_REQS INTEGER Number of log writes during MQPUT.

MQPUT_SUSP_WTIME FLOAT Elapsed time suspended during MQPUT.

MQPUT_SUSPENDS INTEGER Number of times suspended during MQPUT.

MQPUT_PGSSUSP_TME FLOAT Elapsed time suspended on pageset during MQPUT.

MQPUT_PGSET_REQS INTEGER Number of pageset requests during MQPUT.

MQPUT_GET_WAITING INTEGER Number of MQPUT requests that were passed directlyto a waiting getter.

MQPUT_FORCE_WTIME FLOAT Elapsed time waiting for forced log writes duringMQPUT.

MQPUT_FORCE_WRITE INTEGER Number of forced log writes during MQPUT.

MQPUT1_CALLS INTEGER Number of MQPUT1 requests that were processed.

MQPUT1_CPU_TIME FLOAT Total CPU time that was spent performing MQPUT1requests.



MQPUT1_ELAPS_TIME FLOAT Total elapsed time that was spent performingMQPUT1 requests.

MQPUT1_MSG_PERSIS INTEGER Number of persistent messages got by MQPUT1.

MQPUT1_WRLOG_WTME FLOAT Elapsed time waiting for log writes during MQPUT1.

MQPUT1_WRLOG_REQS INTEGER Number of log writes during MQPUT1.

MQPUT1_SUSP_WTIME FLOAT Elapsed time suspended during MQPUT1.

MQPUT1_SUSPENDS INTEGER Number of times suspended during MQPUT1.

MQPUT1_PGSUSP_TME FLOAT Elapsed time suspended on pageset during MQPUT1.

MQPUT1_PGSET_REQS INTEGER Number of pageset requests during MQPUT1.

MQPUT1_GET_WAITING INTEGER Number of MQPUT1 requests that were passeddirectly to a waiting getter.

MQPUT1_FORCE_WTIME FLOAT Elapsed time waiting for forced log writes duringMQPUT1.

MQPUT1_FORCE_WRITE INTEGER Number of forced log writes during MQPUT1.

MQINQ_CALLS INTEGER Number of MQINQ requests that were processed.

MQINQ_CPU_TIME FLOAT Total CPU time that was spent performing MQINQrequests.

MQINQ_ELAPS_TIME FLOAT Total elapsed time that was spent performing MQINQrequests.

MQSET_CALLS INTEGER Number of MQSET requests that were processed.

MQSET_CPU_TIME FLOAT Total CPU time that was spent performing MQSETrequests.

MQSET_ELAPS_TIME FLOAT Total elapsed time that was spent performing MQSETrequests.

MQSET_WRLOG_WTME FLOAT Elapsed time waiting for log writes during MQSET.

MQSET_WRLOG_REQS INTEGER Number of log writes during MQSET.

MQSET_FORCE_WTIME FLOAT Elapsed time waiting for force log writes duringMQSET.

MQSET_FORCE_WRITE INTEGER Number of forced log writes during MQSET.

MQPUT1_BYTES_WRIT FLOAT Total number of bytes written during MQPUT1.

MQGET_BYTES_READ FLOAT Total number of data bytes read during MQGET.

MQPUT_SUCCESSFUL INTEGER Total number of successful puts.

MQGET_SUCCESSFUL INTEGER Total number of successful gets.

GENERATED_MSGS INTEGER Number of generated messages.

MQGET_MSG_SIZ_MAX INTEGER Maximum message size retrieved by MQGET.

MQGET_MSG_SIZ_MIN INTEGER Minimum message size retrieved by MQGET.

MQPUT_MSG_SIZ_MAX INTEGER Maximum message size written by MQPUT.

MQPUT_MSG_SIZ_MIN INTEGER Minimum message size written by MQPUT.

MSG_LATENCY_MAX FLOAT The elapsed time of a retrieved message that hasspent the maximum time on the queue.

MSG_LATENCY_MIN FLOAT The elapsed time of a retrieved message that hasspent the minimum time on the queue.

MSG_LATENCY_TOT FLOAT The total time spent on the queue of all the retrievedmessages.



QUEUE_CUR_HANDLES INTEGER The current number of handles resolving to thisOBJNAME/BASENAME queue.

QUEUE_CALLS_TOT INTEGER Total number of API calls resolving to this queue.

QUEUE_DEPTH_MAX INTEGER Maximum queue depth encountered duringPUT/GET.

MQS_ACCNT_TASK_T, _D, _MThese tables provide detailed, daily, and monthly accounting data for each task.They contain data from SMF type 116, subtype 1.


MQS_ACCNT_TASK_T7 days

MQS_ACCNT_TASK_D30 days

MQS_ACCNT_TASK_M765 days







CONNECTION_NAME K CHAR(8) Name of the connection.

ORIG_PRIM_AUTHID K CHAR(8) Original primary authorization ID.

RRS_CONN_NETW_ID K CHAR(17) Network ID for RRS connections.

MMOVER_CHAN_NAME K CHAR(20) Channel name for MVS mover.

MMOVER_LCONN_NAME K CHAR(48) Long connection name for MVS mover.

PRIMARY_AUTHID K CHAR(8) Primary authorization ID.

CORRELATOR_ID K CHAR(16) Correlator ID.

TASK_CONNECTED CHAR(18) The connection type for this task. Values are:

v 0 - Internal task

v 1 - CICS Attach

v 2 - MVS/TSO Attach

v 3 - IMS Control region

v 4 - IMS MPP region

v 5 - Command Server

v 6 - MVS Mover

v 7 - RRS Stub

v 8 - IGQ agent



TASK_BACKOU_CPUTM FLOAT Total CPU time that was spent processing backoutrequests.

TASK_BACKOU_ETIME FLOAT Total elapsed time that was spent processing backoutrequests.

TASK_BACKOU_NUM INTEGER Number of backout requests.

TASK_COMMIT_CPUTM FLOAT Total CPU time that was spent processing commitrequests.

TASK_COMMIT_ETIME FLOAT Total elapsed time that was spent processing commitrequests.

TASK_COMMIT_NUM INTEGER Number of commit requests.

TASK_DB2_ETME_SRV FLOAT Elapsed time spent by DB2SRVxx task executing DB2request.

TASK_DB2_ETME_THR FLOAT Elapsed time spent in DB2 resource manager underthe threads TCB (including time spent switched toserver TCB).

TASK_DB2_ET_SR_MX FLOAT Maximum STCK elapsed time seen for WTASDBES.

TASK_DB2_ET_TH_MX FLOAT Maximum STCK elapsed time seen for WTASDBET.

TASK_DB2_REQUESTS INTEGER Number of requests to the DB2 resource manager forthis thread.

TASK_DB2_TCB_THR FLOAT Thread TCB only time. (THR time - SRV time).

TASK_DB2_WRITE FLOAT Number of bytes written to DB2 by this thread.

TASK_DB2_READ FLOAT Number of bytes read from DB2 by this thread.

TASK_GET_PAGS_NEW INTEGER Number of new pages that were retrieved.

TASK_GET_PAGS_OLD INTEGER Number of old pages that were retrieved.

TASK_IXLLSTE_CALL INTEGER Number of IXLLSTE calls.

TASK_IXLLSTM_CALL INTEGER Number of IXLLSTM calls.

TASK_IXLLSTE_ETME FLOAT STCK differential time spent executing IXLLSTE calls.

TASK_IXLLSTM_ETME FLOAT STCK differential time spent executing IXLLSTM calls.

TASK_IXLLSTE_REDR INTEGER Number of IXLLSTE redrives.

TASK_IXLLSTM_REDR INTEGER Number of IXLLSTM redrives.

TASK_LOGWRI_BYTES INTEGER Number of bytes written to log.

TASK_LOGWRI_ETIME FLOAT Elapsed time that was spent waiting for log writes.

TASK_LOGWRI_NUM INTEGER Number of log writes.

TASK_LTCH01_W_NUM INTEGER Number of times that a wait occurred for latch class01.










TASK_LTCH_NUM_MAX INTEGER The latch class for which the longest waiting elapsedtime occurred.

TASK_LTCH01_WTIME FLOAT Elapsed time spent waiting for latch class 01.
































TASK_LTCH_WTM_MAX FLOAT Maximum elapsed time spent waiting on a latch class.

TASK_LWR_FDSD_NUM INTEGER Number of log forces.

TASK_LWR_FDSD_TME FLOAT Elapsed time spent waiting for log to be forced.



TASK_OTHCAL_CPUTM FLOAT Total CPU time that was spent processing Otherrequests.

TASK_OTHCAL_ETIME FLOAT Total elapsed time that was spent processing Otherrequests.

TASK_OTHCAL_NUM INTEGER Number of Other requests.

TASK_SUSPENDED INTEGER Number of times that a task was suspended.

TASK_SUSPEN_TIME FLOAT Total elapsed time that a task was suspended.

MQS_BUFFER_T, _D, _MThese tables provide detailed, daily, and monthly statistics data for buffer manager.They contain data from SMF type 115 and subtype 1.


MQS_BUFFER_T7 days

MQS_BUFFER_D30 days

MQS_BUFFER_M765 days







BUFFER_POOL_ID K INTEGER The Buffer pool identifier (0000-0003).

INPUT_RECORDS FLOAT The number of records read.

AVG_NR_BUF FLOAT The average number of buffers in this buffer pool.

LOWEST_NR_BUF FLOAT The lowest number of available buffers.

AVG_AVAIL_NR_BUF FLOAT The average number of available buffers.

PAGE_GETREQ_CUR FLOAT The number of page get requests where the currentpage contents are required.

PAGE_GETREQ_NEW FLOAT The number of get requests for a new or empty page.

PAGE_READ_DASD FLOAT The number of page read from DASD operations.

PAGE_UPDATES FLOAT The number of page updates.

PAGE_WRITE_DASD FLOAT The number of pages written to DASD.

PAGE_WRITE_OPER FLOAT The number of page write operations.

SYNCH_PAG_WRT_OP FLOAT The number of synchronous page write operations.

ASYNCH_WRT_OPER FLOAT The number of times that the asynchronous writeprocessor was started.



SYNCH_PAGE_OPER FLOAT The number of times that the synchronous pageprocessor was started because the synchronous writethreshold was reached.

PAG_GETREQ_NOTFND FLOAT The number of times that a page get request did notfind the page already in the buffer pool.

HASH_CHAIN_CHG FLOAT The number of times that the hash chain has beenchanged during a buffer steal.

NO_AVAIL_BUF FLOAT The number of times that NO available buffers werefound.

MQS_COUPL_FAC_T, _D, _MThese tables provide detailed, daily, and monthly statistics data for couplingfacility manager. They contain data from SMF type 115, subtype 2.


MQS_COUPL_FAC_T7 days

MQS_COUPL_FAC_D30 days

MQS_COUPL_FAC_M765 days







MQCPL_FULL_CNT INTEGER Number of ‘structure fulls’.

MQCPL_IXLLSTE_CNT INTEGER Number of IXLLSTE calls.

MQCPL_IXLLSTM_CNT INTEGER Number of IXLLSTM calls.

MQCPL_IXLLSTE_RED INTEGER Number of IXLLSTE redrives.

MQCPL_IXLLSTM_RED INTEGER Number of IXLLSTM redrives.

MQCPL_IXLLSTE_TM FLOAT Time spent doing IXLLSTE calls.

MQCPL_IXLLSTM_TM FLOAT Time spent doing IXLLSTM calls.

MQCPL_MAX_ELE_US INTEGER Maximum number of elements in use.

MQCPL_MAX_ENT_US INTEGER Maximum number of entries in use.

MQCPL_STRUCT_CNT INTEGER Number of structures.

MQS_DATA_T, _D, _MThese tables provide detailed, daily, and monthly statistics data for data manager.They contain data from SMF type 115, subtype 2.



MQS_DATA_T7 days

MQS_DATA_D30 days

MQS_DATA_M765 days







ENUM_SEL_REQ INTEGER The number of Enumerate/Select requests.

MSG_CNT_REQ INTEGER The number of message count requests.

MSG_GET_OFF_DISK INTEGER The number of Gets that obtained messages from thedisk.

MSG_GET_REQ INTEGER The number of message get requests.

MSG_PUT_REQ INTEGER The number of message put requests.

MSG_READ_BP INTEGER The number of Reads that obtained messages fromthe buffer pool.

OBJ_CREATE_REQ INTEGER The number of Object_Create requests.

OBJ_PUT_REQ INTEGER The number of Object_Put requests.

OBJ_DELETE_REQ INTEGER The number of Object_Delete requests.

OBJ_GET_REQ INTEGER The number of Object_Get requests.

OBJ_LOCATE_REQ INTEGER The number of Object_Locate requests.

READ_AHEAD_BPOOL INTEGER The number of Read aheads from the buffer pool.

READ_AHEAD_IO INTEGER The number of Read aheads during I/O.

REL_BRW_LOCK_REQ INTEGER The number of Release_Browse_Lock requests.

STGCLASS_CHG_REQ INTEGER The number of Stgclass requests.

MQS_DB2_T, _D, _MThese tables provide detailed, daily, and monthly statistics for DB2 manager. Theycontain data from SMF type 115, subtype 2.


MQS_DB2_T7 days

MQS_DB2_D30 days


MQS_DB2_M765 days







MQDB2_ABND_CNT INTEGER Number of DB2SRV task abends.

MQDB2_ACT_TASK INTEGER Number of active server tasks.

MQDB2_BLOB_READ INTEGER Number of DB2 BLOB read requests.

MQDB2_BLOB_INS INTEGER Number of DB2 BLOB insert requests.

MQDB2_BLOB_UPD INTEGER Number of DB2 BLOB update requests.

MQDB2_BLOB_DEL INTEGER Number of DB2 BLOB delete requests.

MQDB2_BLOB_LIST INTEGER Number of DB2 BLOB list requests.

MQDB2_CONN_CNT INTEGER Number of connect requests.

MQDB2_DEAD_CNT INTEGER Number of deadlock timeouts.

MQDB2_DELE_CNT INTEGER Number of delete requests.

MQDB2_DEL_THB_CUM FLOAT Cumulative Store Clock differential - Thread BLOBdelete.

MQDB2_DEL_THB_MAX FLOAT Cumulative Store Clock differential - Thread BLOBdelete.

MQDB2_DEL_SQB_CUM FLOAT Cumulative Store Clock differential - SQL BLOBdelete.

MQDB2_DEL_SQL_CUM FLOAT Cumulative Store Clock differential - SQL delete.

MQDB2_DEL_SQL_MAX FLOAT Maximum Store Clock differential - SQL delete.

MQDB2_DEL_THR_CUM FLOAT Cumulative Store Clock differential - Thread delete.

MQDB2_DEL_THR_MAX FLOAT Maximum Store Clock differential - Thread delete.

MQDB2_DHIG_MAX INTEGER Maximum request queue depth.

MQDB2_DISC_CNT INTEGER Number of disconnect requests.

MQDB2_LIST_CNT INTEGER Number of list requests.

MQDB2_LIST_SQB-CUM FLOAT Cumulative Store Clock differential - SQL BLOB list.

MQDB2_LIST_SQB-MAX FLOAT Cumulative Store Clock differential - SQL BLOB list.

MQDB2_LIST_SQL_CUM FLOAT Cumulative Store Clock differential - SQL list.

MQDB2_LIST_SQL_MAX FLOAT Maximum Store Clock differential - SQL list.

MQDB2_LIST_THB-CUM FLOAT Cumulative Store Clock differential - Thread BLOBlist.

MQDB2_LIST_THB-MAX FLOAT Cumulative Store Clock differential - Thread BLOBlist.

MQDB2_LIST_THR_CUM FLOAT Cumulative Store Clock differential - Thread list.

MQDB2_LIST_THR_MAX FLOAT Maximum Store Clock differential - Thread list.



MQDB2_NUM_TASK INTEGER Number of server tasks.

MQDB2_READ_CNT INTEGER Number of read requests.

MQDB2_READ_SQL_CUM FLOAT Cumulative Store Clock differential - SQL read.

MQDB2_READ_SQL_MAX FLOAT Maximum Store Clock differential - SQL read.

MQDB2_READ_THB_CUM FLOAT Cumulative Store Clock differential - Thread BLOBread.

MQDB2_READ_THB_MAX FLOAT Maximum Store Clock differential - Thread BLOBread.

MQDB2_READ_THR_CUM FLOAT Cumulative Store Clock differential - Thread read.

MQDB2_READ_THR_MAX FLOAT Maximum Store Clock differential - Thread read.

MQDB2_READ_SQB_CUM FLOAT Cumulative Store Clock differential - SQL BLOB read.

MQDB2_READ_SQB_MAX FLOAT Cumulative Store Clock differential - SQL BLOB read.

MQDB2_REQU_CNT INTEGER Number of request requeues.

MQDB2_SCSD_SQL_CUM FLOAT Cumulative Store Clock differential - SQL delete.

MQDB2_SCSD_SQL_MAX FLOAT Maximum Store Clock differential - SQL delete.

MQDB2_SCSD_THR_CUM FLOAT Cumulative Store Clock differential - Thread delete.

MQDB2_SCSD_THR_MAX FLOAT Maximum Store Clock differential - Thread delete.

MQDB2_SCSI_SQL_CUM FLOAT Cumulative Store Clock differential - SQL insert.

MQDB2_SCSI_SQL_MAX FLOAT Maximum Store Clock differential - SQL insert.

MQDB2_SCSI_THR_CUM FLOAT Cumulative Store Clock differential - Thread insert.

MQDB2_SCSI_THR_MAX FLOAT Maximum Store Clock differential - Thread insert.

MQDB2_SCSS_SQL_CUM FLOAT Cumulative Store Clock differential - SQL select.

MQDB2_SCSS_SQL_MAX FLOAT Maximum Store Clock differential - SQL select.

MQDB2_SCSS_THR_CUM FLOAT Cumulative Store Clock differential - Thread select.

MQDB2_SCSS_THR_MAX FLOAT Maximum Store Clock differential - Thread select.

MQDB2_SCST_BUF_FUL INTEGER SCST - Number of times that the buffer was toosmall.

MQDB2_SCST_DEL INTEGER SCST deletes - Shared Channel Status.

MQDB2_SCST_INS INTEGER SCST inserts - Shared Channel Status.

MQDB2_SCST_MAX_ROW INTEGER SCST - Maximum number of rows on query.

MQDB2_SCST_SEL INTEGER SCST selects - Shared Channel Status.

MQDB2_SCST_UPD INTEGER SCST updates - Shared Channel Status.

MQDB2_SCSU_SQL_CUM FLOAT Cumulative Store Clock differential - SQL update.

MQDB2_SCSU_SQL_MAX FLOAT Maximum Store Clock differential - SQL update.

MQDB2_SCSU_THR_CUM FLOAT Cumulative Store Clock differential - Thread update.

MQDB2_SCSU_THR_MAX FLOAT Maximum Store Clock differential - Thread update.

MQDB2_SSKD_SQL_CUM FLOAT Cumulative Store Clock differential - SQL delete.

MQDB2_SSKD_SQL_MAX FLOAT Maximum Store Clock differential - SQL delete.

MQDB2_SSKD_THR_CUM FLOAT Cumulative Store Clock differential - Thread delete.

MQDB2_SSKD_THR_MAX FLOAT Maximum Store Clock differential - Thread delete.

MQDB2_SSKI_SQL_CUM FLOAT Cumulative Store Clock differential - SQL insert.

MQDB2_SSKI_SQL_MAX FLOAT Maximum Store Clock differential - SQL insert.



MQDB2_SSKI_THR_CUM FLOAT Cumulative Store Clock differential - Thread insert.

MQDB2_SSKI_THR_MAX FLOAT Maximum Store Clock differential - Thread insert.

MQDB2_SSKS_SQL_CUM FLOAT Cumulative Store Clock differential - SQL select.

MQDB2_SSKS_SQL_MAX FLOAT Maximum Store Clock differential - SQL select.

MQDB2_SSKS_THR_CUM FLOAT Cumulative Store Clock differential - Thread select.

MQDB2_SSKS_THR_MAX FLOAT Maximum Store Clock differential - Thread select.

MQDB2_SSKT_DEL INTEGER SSKT deletes - Shared Sync Key.

MQDB2_SSKT_INS INTEGER SSKT inserts - Shared Sync Key.

MQDB2_SSKT_SEL INTEGER SSKT selects - Shared Sync Key.

MQDB2_UPDT_CNT INTEGER Number of update requests.

MQDB2_UPDT_SQB_CUM FLOAT Cumulative Store Clock differential - SQL BLOBupdate.

MQDB2_UPDT_SQB_MAX FLOAT Maximum Store Clock differential. SQL BLOB update.

MQDB2_UPDT_SQL_CUM FLOAT Cumulative Store Clock differential - SQL update.

MQDB2_UPDT_SQL_MAX FLOAT Maximum Store Clock differential - SQL update.

MQDB2_UPDT_THB_CUM FLOAT Cumulative Store Clock differential - Thread BLOBupdate.

MQDB2_UPDT_THB_MAX FLOAT Maximum Store Clock differential. Thread BLOBupdate.

MQDB2_UPDT_THR_CUM FLOAT Cumulative Store Clock differential - Thread update.

MQDB2_UPDT_THR_MAX FLOAT Maximum Store Clock differential - Thread update.

MQDB2_WRIT_CNT INTEGER Number of write requests.

MQDB2_WRIT_SQB_CUM FLOAT Cumulative Store Clock differential. SQL BLOB write.

MQDB2_WRIT_SQB_MAX FLOAT Maximum Store Clock differential. SQL BLOB write.

MQDB2_WRIT_SQL_CUM FLOAT Cumulative Store Clock differential - SQL write.

MQDB2_WRIT_SQL_MAX FLOAT Maximum Store Clock differential - SQL write.

MQDB2_WRIT_THB_CUM FLOAT Cumulative Store Clock differential. Thread BLOBwrite.

MQDB2_WRIT_THB_MAX FLOAT Maximum Store Clock differential. Thread BLOBwrite.

MQDB2_WRIT_THR_CUM FLOAT Cumulative Store Clock differential - Thread write.

MQDB2_WRIT_THR_MAX FLOAT Maximum Store Clock differential - Thread write.

MQS_LOCK_T, _D, _MThese tables provide detailed, daily, and monthly statistics data for lock manager.They contain data from SMF type 115, subtype 2.


MQS_LOCK_T7 days

MQS_LOCK_D30 days

MQS_LOCK_M765 days








MQLCK_GET INTEGER Number of Get Lock requests.

MQLCK_HELD INTEGER Number of times that lock held.

MQLCK_RELEASE INTEGER Number of Release Lock requests.

MQS_LOGMGR_T, _D, _MThese tables provide detailed, daily, and monthly statistics data for log manager.They contain data from SMF type 115, subtype 1.


MQS_LOGMGR_T7 days

MQS_LOGMGR_D30 days

MQS_LOGMGR_M765 days



TIME K TIME The time when the record was written. From TME.




ACTIVE_CI_CREATED INTEGER The number of active log control intervals that werecreated.

ALLOC_ARCH_LOG_RD INTEGER The number of times that an archive log data set wasallocated for a read request.

ALLOC_ARCH_LOG_WR INTEGER The number of times that an archive log data set wasallocated for a write request.

BSDS_ACCESS_REQ INTEGER Total number of bootstrap data set (BSDS) accessrequests.

CALLS_WRITTEN INTEGER The number of calls made that wrote to active logbuffers.

CHKPOINT_INVOKED INTEGER The number of times that checkpoint was invoked.

CI_OFFLOADED INTEGER Count of control intervals offloaded to the archivedata set.



DUAL_LOG_REWRITE INTEGER Number of serial log-write requests for controlinterval rewrite when dual logging.

LAHEAD_TAP_ATTEMPT INTEGER Number of look-ahead tape volume mountsattempted this field together with the fieldQJSTLAMS, shows how many times look-aheadmounting failed, thus negating potential significantperformance gains (new).

LAHEAD_TAP_FAILED INTEGER Number of look-ahead tape volume mounts thatfailed. MQSeries 5.2 or later.

LOG_CIS_WRITE INTEGER Total number of log control intervals written.

LOG_REQ_SUS INTEGER Number of times that a log request resulted in aSUSPEND for a log write to occur.

LOG_REQ_WRITE INTEGER Total number of log-write I/O requests.

LOGWRITE_REQ_PAGED INTEGER Number of times that a log-write buffer had to bepaged-in before it could be used.

LOGWRITE_REQ_SCHED INTEGER Number of times that a log-write request wasscheduled because the log-write threshold wasreached.

MSG_GET_REQ INTEGER The number of message get requests.

MSG_PUT_REQ INTEGER The number of message put requests.

READ_REQ_ACTIVE INTEGER Number of read log requests satisfied from the activelog data set.

READ_REQ_ARCHIVE INTEGER Number of read log requests satisfied from an archivelog data set.

READ_REQ_BUF INTEGER Number of read log requests satisfied from in thestorage buffers.

READ_REQ_DELAYED INTEGER Number of read log requests that were delayedbecause the MAXALLC parameter in CSQ6LOGPlimited the number of archive log data sets that couldbe used.

READ_REQ_UNAVAIL INTEGER Number of read accesses that were delayed due to anunavailable resource.

WAIT_COUNT_NO_BUF INTEGER Wait count for unavailable buffers. Number of timesthat a task was suspended because all the bufferswere waiting to be written.

WRITE_COUNT_FORCE INTEGER Write_request count - Force. Tasks are suspended untilall the log records for this unit of recovery are writtento the active log data set.

WRITE_REQ_WAIT INTEGER Write_request count - Wait. Tasks are suspended untilthe write to active log is complete.

WRITE_REQ_NO_WAIT INTEGER Write_request count - No wait. Tasks are notsuspended.

MQS_MSG_T, _D, _MThese tables provide detailed, daily, and monthly statistics data for messagemanager. They contain data from SMF type 115 and subtype 2.



MQS_MSG_T7 days

MQS_MSG_D30 days

MQS_MSG_M765 days







MQOPEN_REQ INTEGER The number of MQOPEN requests.

MQCLOSE_REQ INTEGER The number of MQCLOSE requests.

MQGET_REQ INTEGER The number of MQGET requests.

MQPUT_REQ INTEGER The number of MQPUT requests.

MQPUT1_REQ INTEGER The number of MQPUT1 requests.

MQINQ_REQ INTEGER The number of MQINQ requests.

MQSET_REQ INTEGER The number of MQSET requests.

CLOSE_HANDLE_REQ INTEGER The number of close handle requests.

MQS_STORAGE_T, _D, _MThese tables provide detailed, daily, and monthly statistics data for storagemanager. They contain data from SMF type 115, subtype 1.


MQS_STORAGE_T7 days

MQS_STORAGE_D30 days

MQS_STORAGE_M765 days









F_POOLS_CREATED INTEGER Number of fixed pools that were created.

F_POOLS_DEALLOC INTEGER Number of fixed pools that were deallocated.

F_POOL_SEG_CONTR INTEGER Number of fixed pool segments that were contracted.

F_POOL_SEG_EXPAND INTEGER Number of fixed pool segments that were expanded.

F_POOL_SEG_FREED INTEGER Number of fixed pool segments that were freed.

FREEM_DEALLOC_STO INTEGER Number of FREEMAINs that were issued todeallocate storage other than fixed and variableblocks.

GETM_ALLOC_STOR INTEGER Number of GETMAINs that were issued to allocatestorage other than fixed and variable blocks.

GM_FRM_NONZERO_RC INTEGER Number of nonzero return codes that were issued byGETMAIN, or FREEMAIN, or both.

SH_ON_STOR_ABENDS INTEGER Count of abends that were issued forshort-on-storage.

SH_ON_STOR_BIT_ON INTEGER Count of setting short-on-storage bit to On.

SH_ON_STOR_CNTR INTEGER Number of short-on-storage contractions that wereissued by CSQSCTL.

V_POOLS_CREATED INTEGER Number of variable pools that were created.

V_POOLS_DEALLOC INTEGER Number of variable pools that were deallocated.

V_POOL_SEG_CONTR INTEGER Number of variable pool segments that werecontracted.

V_POOL_SEG_EXPAND INTEGER Number of variable pool segments that wereexpanded.

V_POOL_SEG_FREED INTEGER Number of variable pool segments that were freed.

ReportsThis chapter describes the reports provided with the WebSphere MQ for z/OS(MQSeries) component.

MQSeries CICS Accounting, DailyThis report shows the daily accounting data for CICS environment.

The following information identifies the report:

Report ID:MQS01

Report group:WebSphere MQ for z/OS (MQSeries) reports

Source:MQS_ACCNT_CICS_T

Attributes:MQS, CICS, ACCOUNTING, MQPUT, MQGET, DAILY

Variables:DATE, MVS_SYSTEM_ID, MQSERIES_SUB_ID


The report contains the following information:

MQSeries IdThe WebSphere MQ for z/OS subsystem ID.

Job Id User ID associated with the MVS job.

Connect nameConnection name

Transact IdUser ID associated with the transaction.

Tran NameCICS transaction name

CPU secondsTotal number of CPU seconds per the day specified.

MQPUT totalTotal number of MQPUT requests per the day specified.

MQGET totalTotal number of MQGET requests per the day specified.

MQSeries IMS Accounting, DailyThis report shows the daily accounting data for IMS environment.


Report ID:MQS02


Source:MQS_ACCNT_IMS_T

Attributes:MQS, IMS, ACCOUNTING, MQPUT, MQGET, DAILY


MQSeries CICS Accounting, DailySystem: MVS

Date: 2000-02-13

MQSeries Job Connect Transact Tran CPU MQPUT MQGETId Id name Id Name seconds total total

-------- -------- -------- -------- ---- -------- -------- --------VICA PAICE IYAYECIC PAICE 0 0 0

IYAYECIC CICSUSER CKTI 0 0 0IYAYECIC CICSUSER GP19 2 0 828IYAYECIC CICSUSER PP15 2 833 0

Tivoli Decision Support for z/OS Report: MQS01

Figure 2. Example of an MQSeries CICS Accounting, Daily Report







Account tokenAccounting token

IMS PST idIMS partition specification table (PST) region identifier

IMS PSB nameIMS program specification block (PSB) name




MQSeries Accounting, DailyThis report shows the daily accounting data for MVS environment.


Report ID:MQS03


Source:MQS_ACCNT_T

Attributes:MQS, ACCOUNTING, MQPUT, MQGET, DAILY

MQSeries Accounting, DailySystem: ’MVSY’Date: 2000-02-14

IMS IMSMQSeries Job Connect Transact Account PST PSB

Id Id name Id token id name-------- -------- -------- -------- ---------------------- ---- --------VICA VICACHIN XXXX YYYY

VICACHIN * XXXX YYYY


Figure 3. Example of an MQSeries IMS Accounting, Daily Report (partial view)











MQSeries Message Manager Statistics, DailyThis report shows the daily message manager statistics.


Report ID:MQS04


Source:MQS_MSG_D

Attributes:MQS, STATISTICS, MQI, DAILY

MQSeries IMS Accounting, DailySystem: ’MVSY’

Date: 2000-02-14

MQSeries Job Connect Transact CPU MQPUT MQGETId Id name Id seconds total total

-------- -------- -------- -------- -------- -------- --------VICA VICACHIN 0 0 0

VICACHIN * 0 0 0

PAICE IYAYECIC PAICE 0 0 0

* VICACHIN * 0 0 0

PAICE PAICEM2 PAICE 2 1000 1000IYAYECIC CICSUSER 4 833 828PAICEPG PAICE 11 4000 4000


Figure 4. Example of an MQSeries MVS Accounting, Daily Report





MQOPEN requestsTotal number of MQOPEN requests per the day specified.

MQCLOSE requestsTotal number of MQCLOSE requests per the day specified.

MQGET requestsTotal number of MQGET requests per the day specified.

MQPUT requestsTotal number of MQPUT requests per the day specified.

MQPUT1 requestsTotal number of MQPUT1 requests per the day specified.

MQINQ requestsTotal number of MQINQ requests per the day specified.

MQSET requestsTotal number of MQSET requests per the day specified.

Close handle requestsTotal number of close handle requests per the day specified.

MQSeries Data Manager Statistics, DailyThis report shows the daily data manager statistics.


Report ID:MQS05


Source:MQS_DATA_D

Attributes:MQS, STATISTICS, DAILY

MQSeries Message Manager Statistics DailySystem: ’MVSY’Date: 2000-02-14

MQSeries MQOPEN MQCLOSE MQGET MQPUT MQPUT1 MQINQ MQSETId requests requests requests requests requests requests requests

-------- -------- -------- -------- -------- -------- -------- --------VICA 297984 298008 185580 184998 0 0 0


Figure 5. Example of an MQSeries Message Manager Statistics, Daily Report (partial view)





Object createTotal number of object create requests per the day specified.

Object putTotal number of object put requests per the day specified.

Object deleteTotal number of object delete requests per the day specified.

Object getTotal number of object get requests per the day specified.

Object locateTotal number of object locate requests per the day specified.

Stgclass changeTotal number of stgclass change requests per the day specified.

Number message get requestTotal number of message get requests per the day specified.

Number message put requestTotal number of message put requests per the day specified.

MQSeries Buffer Manager Statistics, DailyThis report shows the daily buffer manager statistics.


Report ID:MQS06

MQSeries Data Manager Statistics,DailySystem: ’MV41’Date: 2004-12-21

Number Numbermessage message

MQSeries Object Object Object Object Object Stgclass get putId create put delete get locate change request request-------- -------- -------- -------- -------- -------- -------- -------- --------MQ08 0 0 0 0 0 0 0 0

0 0 0 0 0 0 0 00 0 0 0 0 0 0 00 0 0 0 0 0 0 00 0 0 0 0 0 0 00 0 0 0 0 0 0 00 0 0 0 16 0 120 124

64 3 0 68 34 0 61 62


Figure 6. Example of an MQSeries Data Manager Statistics, Daily Report



Source:MQS_BUFFER_D





Buffer Pool idBuffer pool identifier (0-3)

Average number bufferAverage number of buffers in this buffer pool during the day.

Average avail bufferAverage number of buffer available in this buffer pool during the day.

Getpage new requestsTotal number of get requests for a new, or empty, page. No read operationis necessary.

Getpage current requestsTotal number of page get requests where the current page contents arerequired. This may involve a read DASD operation if the page is notcurrently in the buffer pool.

Getpage notfnd requestsTotal number of times a page get request did not find the page already inthe buffer pool.

Synch page writeTotal number of times the synchronous write processor was started.

MQSeries Buffer Manager StatisticsSystem: ’MVSY’Date: 2000-02-14

Buffer Average Average Getpage Getpage Getpage SynchMQSeries Pool number avail new current notfnd page

id id buffer buffer requests requests requests write-------- -------- -------- -------- -------- -------- -------- --------VICA 0 10000 9977 0 603384 0 6

1 10000 5318 142620 968868 42468 12

2 0 0 0 0 0 0

3 100000 0 0 0 0 0


Figure 7. Example of an MQSeries Buffer Manager Statistics, Daily Report (partial view)


Asynch page writeTotal number of times the asynchronous write processor was started.

Times buffer unavailTotal number of times that no available buffers were found.

MQSeries Log Manager Statistics, DailyThis report shows the daily log manager statistics.


Report ID:MQS07


Source:MQS_LOG_D





Log write requestsTotal number of log write requests.

Log read requestsTotal number of log read requests.

Wait countTotal number of wait requests. Tasks are suspended until the write toactive log is complete.

MQSeries Log Manager Statistics, DailySystem: ’MV41’

Date: 2003-12-21

NumberLog Log of

MQSeries write read Wait Read checkpointId requests requests count archive invoked-------- -------- -------- -------- -------- -----------MQ08 0 0 0 0 0

0 0 0 0 00 0 0 0 00 0 0 0 00 0 0 0 00 0 0 0 00 0 0 0 0

444 0 0 0 0


Figure 8. Example of an MQSeries Log Manager Statistics, Daily Report


Read archiveTotal number of read log requests satisfied from an archive log dataset.

Number of checkpoint invokedTotal number of times that checkpoint was invoked.

MQSeries DB2 BLOB Statistics, DailyThis report shows the daily DB2 BLOB statistics.


Report ID:MQS08

Report group:MQSeries Statistic and Accounting Reports

Source:MQS_DB2_T

Attributes:MQS, DB2, STATISTICS, MQPUT, MQGET, DAILY



Date The date(daily) of the measurement.


BLOB_read_requestsNumber of DB2 BLOB read requests.

BLOB_insert_requestsNumber of DB2 BLOB insert requests.

BLOB_update_requestsNumber of DB2 BLOB update requests.

BLOB_delete_requestsNumber of DB2 BLOB delete requests.

BLOB_list_requestsNumber of DB2 BLOB list requests.

MQSeries DB2 BLOB Statistics, DailySystem: ’MV3D’Date: 2002-07-26

BLOB BLOB BLOB BLOB BLOBMQSeries read insert update delete listId requests requests requests requests requests-------- ----------- ----------- ----------- ----------- -----------MQJH 15 56 0 15 0MQ5A - - - - -MQRC 0 0 0 0 0


Figure 9. Example of an MQSeries DB2 BLOB Statistics, Daily Report


MQSeries DB2 Manager Statistics, DailyThis report shows the daily DB2 Manager statistics.


Report ID:MQS09

Report group:MQSeries Statistic and Accounting Reports

Source:MQS_DB2_T

Attributes:MQS, DB2, STATISTICS, DAILY



Date The date(daily) of the measurement.

Period The name of the period.


Active_TasksNumber of active server tasks.

Connect_RequestsNumber of connect requests.

Delete_RequestsNumber of delete requests.

List_RequestsNumber of list requests.

MQSeries DB2 Manager Statistics, DailySystem: ’MV3D’Date: 2002-07-26

MQSeries Active Connect DeletePeriod ID Tasks Requests Requests-------- -------- -------- -------- --------PRIME MQ5A 0 0 0PRIME MQJH 33 0 0PRIME MQRC 22 0 0

List Read Update Write RequeueRequests Requests Requests Requests Requests-------- -------- -------- -------- --------

0 0 0 0 0176 0 0 0 0125 0 0 0 0


Figure 10. Example of an MQSeries DB2 Manager Statistics, Daily Report


Read_RequestsNumber of read requests.

Update_RequestsNumber of update requests.

Write_RequestsNumber of write requests.

Requeue_RequestsNumber of Requeue requests.

MQSeries Short On Storage and Log Manager Counts, DailyThis report can be used as a ‘health check’ showing the daily storage shortagesand log manager indicators.


Report ID:MQS10


Source:MQS_STORAGE_D, MQS_LOGMGR_D


Variables:Date, MVS_System_ID, MQSeries_Sub_ID

The following columns originate from table MQS_STORAGE_D:

SH_ON_STOR_CNTRNumber of short-on-storage contractions that were issued by CSQSCTL.

SH_ON_STOR_BIT_ONCount of setting short-on-storage bit to On.

SH_ON_STOR_ABENDSCount of abends that were issued for short-on-storage.

The following columns originate from table MQS_LOGMGR_D:

MQSeries Short On Storage & Log Mngr Counts, DailySystem: ’MV41’Date: 2005-07-27

CountCount Count Count of Waits Reads from No. of

MQSeries of SOS of SOS of SOS Unaval Archive Logs CheckpointsId Reductions bit set on Abends Buffer % of Total per hour

-------- ---------- ---------- ------ -------- ------------ -----------MQ07 0 0 0 4 0 0

Tivoli Decision Support: MQS10

Figure 11. Example of an MQSeries short on storage and log manager counts, Daily Report


WAIT_COUNT_NO_BUFNumber of times that a task was suspended because all the buffers werewaiting to be written.

READ_REQ_ARCHIVENumber of read log requests satisfied from an archive log data set,expressed as a percentage. This is calculated as: READ_REQ_ARCHIVE /(READ_REQ_BUF + READ_REQ_ACTIVE + READ_REQ_ARCHIVE) %

CHKPOINT_INVOKEDNumber of checkpoints per hour. This is calculated as:CHKPOINT_INVOKED / 24

MQSeries Wait and Suspend Times, DailyThis report can be used as a ‘health check’ showing wait times, suspend times, andother indicators based on the Accounting records (SMF 116).


Report ID:MQS11


Source:MQS_ACCNT_QUEUE_D

Attributes:MQS, ACCOUNTING, DAILY

Variables:MVS_System_ID, MQSeries_Sub_ID

The following columns originate from table MQS_ACCNT_QUEUE_D:

MQGET_WRLOG_WTIMEElapsed time waiting for log writes during MQGET.

MQGET_SUSP_WTIMEElapsed time suspended waiting for MQGET.

MQSeries Wait and Suspend Times, DailySystem: ’MV41’Date: 2005-07-27

Time Elapsed Times Elapsed Times Elapsed TimesWait Wait Time Susp. Wait Time Susp. Wait Time Susp.

MQSeries Log Susp. During Susp. During Susp. DuringId Writes MQGET MQGET MQPUT MQPUT MQPUT1 MQPUT1

-------- ------- --------- ------- --------- ------- --------- -------MQ07 0 1 46 86 106 0 0

MQ08 0 0 3 0 0 0 0


Figure 12. Example of an MQSeries Wait and Suspend Times, Daily Report


MQGET_SUSPENDSNumber of times suspended during MQGET.

MQPUT_SUSP_WTIMEElapsed time suspended waiting for MQPUT.

MQPUT_SUSPENDSNumber of times suspended during MQPUT.

MQPUT1_SUSP_WTIMEElapsed time suspended waiting for MQPUT1.

MQPUT1_SUSPENDSNumber of times suspended during MQPUT1.

MQSeries Message Sizes, DailyThis report can be used as a ‘health check’ showing message sizes and otherindicators based on the Accounting records (SMF 116).


Report ID:MQS12


Source:MQS_ACCNT_QUEUE_D

Attributes:MQS, ACCOUNTING, DAILY


The following columns originate from table MQS_ACCNT_QUEUE_D:

MQGET_EX_MSGS_PRCNumber of expired messages that were processed during MQGETs.

MQGET_MSG_SIZ_MAXMaximum message size retrieved by MQGET.

MQSeries Message Sizes, DailySystem: ’MV41’Date: 2005-07-27

Expired Kilo KiloMsg. Max.Size Min.Size Max.Size Min.Size Bytes Bytes

MQSeries Handled Msg Read Msg Read Msg Write Msg Write Written ReadId in MQGET MQGET MQGET MQPUT MQPUT MQPUT1 MQGET

-------- -------- -------- -------- --------- --------- ------- ------MQ07 1 4451857 954458 4608187 1113875 25107 24236

MQ08 6 16469 13320 12490 12418 13 292


Figure 13. Example of an MQSeries Message Sizes, Daily Report


MQGET_MSG_SIZ_MINMinimum message size retrieved by MQGET.

MQPUT_MSG_SIZ_MAXMaximum message size written by MQPUT.

MQPUT_MSG_SIZ_MINMinimum message size written by MQPUT.

MQPUT1_BYTES_WRITTotal number of bytes written during MQPUT1.

MQGET_BYTES_READTotal number of data bytes read during MQGET.

MQSeries Data Manager Indicators, DailyThis report can be used as a ‘health check’ showing the daily Data managerindicators based on Statistics records (SMF 115).


Report ID:MQS13


Source:MQS_DATA_D, MQS_DB2_D, MQS_COUPL_FAC_D



The following Column originates from table MQS_DATA_D:

MSG_GET_OFF_DISKThe number of Gets that obtained messages from the disk.

The following columns originate from table MQS_DB2_D:

MQSeries Data Manager Indicators, DailySystem: ’MV41’Date: 2005-07-27

Full CountCount of Max Req No. of Coupling Avg. Time Avg. Time

MQSeries Page Gets Queue Req Facility for IXLLSTE for IXLLSTMId from Disk Depth Requeues Structure Calls Calls

-------- --------- ------- -------- ---------- ----------- -----------MQ07 0 1 0 0 0 0

MQ08 0 1 0 0 0 0


Figure 14. Example of an MQSeries Data Manager Indicators, Daily Report


MQDB2_DHIG_MAXMaximum request queue depth.

MQDB2_REQU_CNTNumber of request requeues.

The following columns originate from table MQS_COUPL_FAC_D:

MQCPL_FULL_CNTNumber of ‘structure fulls’.

MQCPL_IXLLSTE_TM / MQCPL_IXLLSTE_CNTAverage time spent doing IXLLSTE calls.

MQCPL_IXLLSTM_TM / MQCPL_IXLLSTM_CNTAverage time spent doing IXLLSTM calls.

WebSphere Message Broker componentCustomizationv Making input data available

Data flow


Data tablesv WMB_MESSAGE_D,_Wv WMB_MESSAGE_Tv WMB_NODE_D,_Wv WMB_NODE_Tv WMB_TERMINAL_D,_Wv WMB_TERMINAL_Tv WMB_THREAD_D,_Wv WMB_THREAD_T

Reportsv Message Broker Flow Accounting and Statistics, Dailyv Message Broker Node Accounting and Statistics, Dailyv Message Broker Thread Accounting and Statistics, Dailyv Message Broker Terminal Accounting and Statistics, Daily

CustomizationWebSphere Message Broker produces message flow accounting and statistics datathat is written as z/OS SMF records. The data records contain information aboutmessage flows, threads, nodes and terminals.

IBM Tivoli Decision Support for z/OS 1.8.0 will collect both Archive and Snapshotdata.

Making input data availableBefore you can use the WebSphere Message Broker component, you must ensurethe z/OS SMF 117 records are made available for collection.


When configuring WebSphere Message Broker for the collection of message flowaccounting and statistics data, ensure the SMF target destination is selected.

For a complete description on how to activate the collection of message flowaccounting and statistics data, refer to the WebSphere Message Broker InformationCenter at http://publib.boulder.ibm.com/infocenter/wmbhelp/v6r0m0/index.jsp.

Data flowThe WebSphere Message Broker component collects records from the SMF data setand stores extracted and summarized data in the Tivoli Decision Support for z/OSdatabase. The reporting function extracts data from the database and creates thereports that you request through the reporting dialogs. Figure 15 shows anoverview of the flow of data through the WebSphere Message Broker component.

Log and record definitionsThe WebSphere Message Broker component collects records from the systemmanagement facility (SMF) logs. WebSphere Message Broker writes records thatcontain information about flows, threads, nodes and terminals.

Within the SMF_117 record, there are three main sections:

Type1Thread SectionThis section contains the accounting and statistics data for message flows(as held in BipSMFMessageFlow record) and threads (as held in theBipSMFThread record). This section occurs if the subtype is 1 (SM117STY =1) and the Triplet count is greater than 1 (SM117TCT > 1). For subtype 1

Figure 15. WebSphere Message Broker component data flow


records, the first occurrence of the BipSMFTriplet record relates to theBipSMFMessageFlow record whilst the second occurrence relates to theBipSMFThread record.

Type2Node SectionThis section contains the accounting and statistics data for message flows(as held in BipSMFMessageFlow record) and nodes (as held in theBipSMFNode record). This section occurs if the subtype is 2 (SM117STY =2) and the Triplet count is greater than 1 (SM117TCT > 1). For subtype 2records, the first occurrence of the BipSMFTriplet record relates to theBipSMFMessageFlow record whilst the second occurrence relates to theBipSMFNode record.

Type2Terminal SectionThis section contains the accounting and statistics data for message flows(as held in BipSMFMessageFlow record), nodes (as held in theBipSMFNode record) and terminals (as held in the BipSMFTerminalrecord). This section occurs if the subtype is 2(SM117STY = 2) and theTriplet count is greater than 2 (SM117TCT > 2). For subtype 2 records, thefirst occurrence of the BipSMFTriplet record relates to theBipSMFMessageFlow record, the second occurrence relates to theBipSMFNode record, and the third occurrence relates to theBipSMFTerminal record.

For a complete description of the SMF 117 record, refer to the WebSphere MessageBroker Information Center.

Data tablesThis chapter describes the data tables used by the WebSphere Message Brokercomponent.

WMB_MESSAGE_D,_WThese tables provide detailed daily and weekly accounting data for message flows.They contain data from SMF type 117 records.


WMB_MESSAGE_D90 days

WMB_MESSAGE_W400 days

Column name Key Data type Source

DATE K DATE Interval start date. From IMFLSTDT.

SYSTEM_ID K CHAR(4) System ID. From SM117SID.

COLLECT_TYPE K CHAR(1) Record type. Archive or Snapshot. From SM117SRT.

BROKER_NAME K CHAR(32) Broker name. From IMFLBKNM.

EXEC_GROUP_NAME K CHAR(32) Execution group name. From IMFLEXNM.

EXEC_GROUP_ID K CHAR(36) Execution group universal unique identifier. FromIMFLEXID.

MESSAGE_NAME K CHAR(32) Message flow name. From IMFLMFNM.

MAX_CPU_TIME REAL Maximum CPU time, in microseconds, spentprocessing an input message. From IMFLMXCP.



MAX_ELAPSED_TIME REAL Maximum elapsed time, in microseconds, spentprocessing an input message. From IMFLMXTM.

MAX_INPUT_SIZE REAL Maximum input message size (bytes). FromIMFLMXMG.

MAX_NO_THREADS INTEGER Number of times the maximum number of threads isreached. From IMFLTHDM.

MIN_CPU_TIME REAL Minimum CPU time, in microseconds, spentprocessing an input message. From IMFLMNCP.

MIN_ELAPSED_TIME REAL Minimum elapsed time, in microseconds, spentprocessing an input message. From IMFLMNTM.

MIN_INPUT_SIZE REAL Minimum input message size (bytes). FromIMFLMNMG.

NO_BACKOUTS INTEGER Number of transaction backouts. From IMFLBKOU.

NO_COMMITS INTEGER Number of transaction commits. From IMFLCMIT.

NO_MQGET_ERRORS INTEGER Number of MQGET errors (MQInput node) or Webservices errors (HTTPInput node). From IMFLERMQ.

NO_MSG_ERRORS INTEGER Number of messages that contain errors. FromIMFLERMG.

NO_PROC_ERRORS INTEGER Number of errors processing a message. FromIMFLERPR.

NO_TIMEOUTS INTEGER Number of timeouts processing a message.(AggregateReply node only). From IMFLTMOU.

NUMBER_MESSAGES INTEGER Total number of messages processed. FromIMFLTPMG.

NUMBER_THREADS INTEGER Number of threads in pool. From IMFLTHDP.

TOTAL_INPUT_SIZE REAL Total size of input messages (bytes). FromIMFLTSMG.

TOT_CPU_TIME REAL Total CPU time, in microseconds, spent processinginput messages. From IMFLTPCP.

TOT_ELAPSED_TIME REAL Total elapsed time, in microseconds, spent processinginput messages. From IMFLTPTM.

TOT_ELAPSED_WAIT_T REAL Total elapsed time, in microseconds, spent waiting forinput messages. From IMFLWTIN.

TOT_WAIT_TIME REAL Total CPU time, in microseconds, spent waiting forinput messages. From IMFLWTCP.

WMB_MESSAGE_TThis table provides detailed data for message flows at a Timestamp based interval.It contains data from SMF type 117 records.

The default retention period for table WMB_MESSAGE_T is 10 days.



TIME K TIME Interval start time. From IMFLSTTM.









ACCT_ORIGIN CHAR (32) Accounting origin. From IMFLACCT.

END_DATE DATE Interval end date. From IMFLENDT.

END_TIME TIME Interval end time. From IMFLENTM.

MAX_CPU_TIME REAL Maximum CPU time, in microseconds, spentprocessing an input message. From IMFLMXCP.

MAX_ELAPSED_TIME REAL Maximum elapsed time, in microseconds, spentprocessing an input message. From IMFLMXTM.

MAX_INPUT_SIZE REAL Maximum input message size (bytes). FromIMFLMXMG.

MAX_NO_THREADS INTEGER Number of times the maximum number of threads isreached. From IMFLTHDM.

MIN_CPU_TIME REAL Minimum CPU time, in microseconds, spentprocessing an input message. From IMFLMNCP.

MIN_ELAPSED_TIME REAL Minimum elapsed time, in microseconds, spentprocessing an input message. From IMFLMNTM.

MIN_INPUT_SIZE REAL Minimum input message size (bytes). FromIMFLMNMG.

NO_BACKOUTS INTEGER Number of transaction backouts. From IMFLBKOU.

NO_COMMITS INTEGER Number of transaction commits. From IMFLCMIT.

NO_MQGET_ERRORS INTEGER Number of MQGET errors (MQInput node) or Webservices errors (HTTPInput node). From IMFLERMQ.

NO_MSG_ERRORS INTEGER Number of messages that contain errors. FromIMFLERMG.

NO_PROC_ERRORS INTEGER Number of errors processing a message. FromIMFLERPR.

NO_TIMEOUTS INTEGER Number of timeouts processing a message.(AggregateReply node only). From IMFLTMOU.

NUMBER_MESSAGES INTEGER Total number of messages processed. FromIMFLTPMG.

NUMBER_THREADS INTEGER Number of threads in pool. From IMFLTHDP.

TOTAL_INPUT_SIZE REAL Total size of input messages (bytes). FromIMFLTSMG.

TOT_CPU_TIME REAL Total CPU time, in microseconds, spent processinginput messages. From IMFLTPCP.

TOT_ELAPSED_TIME REAL Total elapsed time, in microseconds, spent processinginput messages. From IMFLTPTM.

TOT_ELAPSED_WAIT_T REAL Total elapsed time, in microseconds, spent waiting forinput messages. From IMFLWTIN.

TOT_WAIT_TIME REAL Total CPU time, in microseconds, spent waiting forinput messages. From IMFLWTCP.


WMB_NODE_D,_WThese tables provide detailed daily and weekly accounting data for nodes. Theycontain data from SMF type 117 records.


WMB_NODE_D90 days

WMB_NODE_W400 days


DATE K DATE Interval start date .From IMFLSTDT.







NODE_NAME K CHAR(32) Name of node (Label). From INODNDNM

NODE_TYPE K CHAR(32) Type of node. From INODTYPE

MAX_CPU_TIME REAL Maximum CPU time, in microseconds, spentprocessing input messages. From INODMXCP

MAX_ELAPSED_TIME REAL Maximum elapsed time, in microseconds, spentprocessing input messages. From INODMXTM

MIN_CPU_TIME REAL Minimum CPU time, in microseconds, spentprocessing input messages. From INODMNCP

MIN_ELAPSED_TIME REAL Minimum elapsed time, in microseconds, spentprocessing input messages. From INODMNTM

NO_INPUT_TERMINALS INTEGER Number of input terminals. From INODNITL

NO_OUTPUT_TERMINALS INTEGER Number of output terminals. From INODNOTL

TOT_CPU_TIME REAL Total CPU time, in microseconds, spent processinginput messages. From INODTPCP

TOT_ELAPSED_TIME REAL Total elapsed time, in microseconds, spent processinginput messages. From INODTPTM

TOT_NO_MSGS INTEGER Total number of messages processed by this node.From INODTPMG

WMB_NODE_TThis table provides detailed accounting data for nodes at a Timestamp basedinterval. It contains data from SMF type 117 records.

The default retention period for table MB_NODE_T is 10 days.
















MAX_CPU_TIME REAL Maximum CPU time, in microseconds, spentprocessing input messages. From INODMXCP

MAX_ELAPSED_TIME REAL Maximum elapsed time, in microseconds, spentprocessing input messages. From INODMXTM

MIN_CPU_TIME REAL Minimum CPU time, in microseconds, spentprocessing input messages. From INODMNCP

MIN_ELAPSED_TIME REAL Minimum elapsed time, in microseconds, spentprocessing input messages. From INODMNTM

NO_INPUT_TERMINALS INTEGER Number of input terminals. From INODNITL

NO_OUTPUT_TERMINALS INTEGER Number of output terminals. From INODNOTL

TOT_CPU_TIME REAL Total CPU time, in microseconds, spent processinginput messages. From INODTPCP

TOT_ELAPSED_TIME REAL Total elapsed time, in microseconds, spent processinginput messages. From INODTPTM

TOT_NO_MSGS INTEGER Total number of messages processed by this node.From INODTPMG

WMB_TERMINAL_D,_WThese tables provide detailed daily and weekly accounting data for terminals. Theycontain data from SMF type 117 records.


WMB_TERMINAL_D90 days

WMB_TERMINAL_W400 days













TERMINAL_NAME K CHAR(32) Name of terminal. From ITRMTLNM

TERMINAL_TYPE K CHAR(8) Type of terminal, one of Input or Output. FromITRMTYPE

TOT_NO_INVOCATIONS REAL Total number of invocations. From ITRMTINV

WMB_TERMINAL_TThis table provides detailed accounting data for terminals at a Timestamp basedinterval. It contains data from SMF type 117 records.

The default retention period for table WMB_TERMINAL_T is 10 days.












TERMINAL_NAME K CHAR(32) Name of terminal. From ITRMTLNM

TERMINAL_TYPE K CHAR(8) Type of terminal, one of Input or Output. FromITRMTYPE



TOT_NO_INVOCATIONS REAL Total number of invocations. From ITRMTINV

WMB_THREAD_D,_WThese tables provide detailed daily and weekly accounting data for threads. Theycontain data from SMF type 117 records.


WMB_THREAD_D90 days

WMB_THREAD_W400 days







BROKER_NAME K CHAR(32) Broker name . From IMFLBKNM.




THREAD_NO K INTEGER Relative thread number in pool. From ITHDNBR

MAX_MSG_SIZE REAL Maximum size of input messages (bytes). FromITHDMXMG

MIN_MSG_SIZE REAL Minimum size of input messages (bytes). FromITHDMNMG

TOT_CPU_TIME REAL Total CPU time, in microseconds, spent processinginput messages. From ITHDTPCP

TOT_ELAPSED_TIME REAL Total elapsed time, in microseconds, spent processinginput messages. From ITHDTPTM

TOT_ELAPSED_WAIT_T REAL Total elapsed time, in microseconds, spent waiting forinput messages. From ITHDWTIN

TOT_MSG_IN_THREAD REAL Total number of messages processed by thread. FromITHDTPMG

TOT_MSG_SIZE REAL Total size of input messages (bytes). FromITHDTSMG

TOT_WAIT_TIME REAL Total CPU time, in microseconds, spent waiting forinput messages. From ITHDWTCP

WMB_THREAD_TThis table provides detailed accounting data for threads at a Timestamp basedinterval. It contains data from SMF type 117 records.

The default retention period for WMB_THREAD_T is 10 days.






BROKER_NAME K CHAR(32) Broker name . From IMFLBKNM.




THREAD_NO K INTEGER Relative thread number in pool. From ITHDNBR



MAX_MSG_SIZE REAL Maximum size of input messages (bytes). FromITHDMXMG



MIN_MSG_SIZE REAL Minimum size of input messages (bytes). FromITHDMNMG

TOT_CPU_TIME REAL Total CPU time, in microseconds, spent processinginput messages. From ITHDTPCP

TOT_ELAPSED_TIME REAL Total elapsed time, in microseconds, spent processinginput messages. From ITHDTPTM

TOT_ELAPSED_WAIT_T REAL Total elapsed time, in microseconds, spent waiting forinput messages. From ITHDWTIN

TOT_MSG_IN_THREAD REAL Total number of messages processed by thread. FromITHDTPMG

TOT_MSG_SIZE REAL Total size of input messages (bytes). FromITHDTSMG

TOT_WAIT_TIME REAL Total CPU time, in microseconds, spent waiting forinput messages. From ITHDWTCP

ReportsThis chapter describes the reports provided with the WebSphere Message Brokercomponent.

Message Broker Flow Accounting and Statistics, DailyThis report shows the daily accounting and statistics data for message flows.


Report ID:WMB01

Report group:Websphere Message Broker

Source:WMB_MESSAGE_D

Attributes:WMB, Message

Variables:DATE, SYSTEM_ID, BROKER_NAME, EXEC_GROUP_NAME



MVS SystemSystem ID

BrokerBroker name

Exec GroupExecution group name

Message NameMessage flow name

Total CPU TimeTotal CPU time spent processing input messages

Total Wait TimeTotal CPU time spent waiting for input messages

Total Elapsed TimeTotal elapsed time spent processing input messages

Total Elapsed Wait TimeTotal elapsed time spent waiting for input messages

Number of MessagesTotal number of messages processed

Total Input SizeTotal size of input messages(bytes)

Message Broker Node Accounting and Statistics, DailyThis report shows the daily accounting and statistics data for nodes.


Report ID:WMB02


Source:WMB_NODE_D

Daily accounting data for Message FlowsMVS system:’MVD0’Broker :’MQ06BRK’Exec Group:’ECOMPUTE1’Date :’2006-03-21’

Message Total Total Total Total Elapsed Number TotalName CPU Time Wait Time Elapsed Time Wait Time of Messages Input Size-------------- -------- --------- ------------ ------------- ----------- ----------fcompute1 0 16673 0 123 0 0

Tivoli Decision Support for z/OS Report: WMB001

Figure 16. Example of Daily accounting data for Message Flows


Attributes:WMB, Node

Variables:DATE, SYSTEM_ID, BROKER_NAME, EXEC_GROUP_NAME,MESSAGE_NAME


MVS SystemSystem ID

BrokerBroker name


Message NameMessage flow name

Node NameName of node (Label)



Total No MessagesTotal number of messages processed by this node

Number of Input TerminalsNumber of input terminals

Number of Output TerminalsNumber of Output terminals

Message Broker Thread Accounting and Statistics, DailyThis report shows the daily accounting and statistics data for threads.


Daily accounting data for Nodes

MVS system :’MVD0’Broker :’MQ06BRK’Exec Group :’ECOMPUTE1’Message Name:’fcompute1’Date :’2006-06-21’

Node Total Total Total Number of Number ofName CPU Time Elapsed Time No Messages Input Terminals Output Terminals------------------- -------- ------------ ----------- --------------- ----------------inputNode.......... 1271 24163 12 0 9outputFailure...... 0 0 0 3 6outputTrue......... 1625 1651 12 3 6


Figure 17. Example of Daily accounting data for Nodes


Report ID:WMB03


Source:WMB_THREAD_D

Attributes:WMB, Thread

Variables:DATE, SYSTEM_ID, BROKER_NAME, EXEC_GROUP_NAME,MESSAGE_NAME


MVS SystemSystem ID

BrokerBroker name


Message FlowMessage flow name

Thread NoRelative thread number in pool

Total Messages in ThreadTotal number of messages processed by thread



Total Wait TimeTotal CPU time spent waiting for input messages

Daily accounting data for ThreadsMVS system :’MVD0’

Broker :’MQ06BRK’Exec Group :’ECOMPUTE1’Message Flow:’fcompute1’Date :’2006-06-21’

Total Messages Total Total Total Total Elapsed TotalThread No in Thread Elapsed Time CPU Time Wait Time Wait Time Message Size--------- -------------- ------------ -------- --------- ------------- ------------

24 144 51628 5792 172942 5568430000 13776


Figure 18. Example of Daily accounting data for Threads


Total Elapsed Wait Timeotal elapsed time spent waiting for input messages

Total Message SizeTotal size of input messages (bytes)

Message Broker Terminal Accounting and Statistics, DailyThis report shows the daily accounting and statistics data for terminals.


Report ID:WMB04


Source:WMB_TERMINAL_D

Attributes:WMB, Terminal

Variables:DATE, SYSTEM_ID, BROKER_NAME, EXEC_GROUP_NAME,MESSAGE_NAME, NODE_NAME


MVS SystemSystem ID

BrokerBroker name


Message FlowMessage flow name

Daily accounting data for TerminalsMVS system : ’MVD0’

Broker : ’MQ06BRK’Exec Group : ’ECOMPUTE1’Message Flow: ’fcompute1’Node : ’inputNode’Date : ’2006-06-21’

Type of Total NumberTerminal Name Terminal of Invocations------------- -------- --------------catch Output 0failure Output 0out Output 12


Figure 19. Example of Daily accounting data for Terminals (partial view)


Node Name of node (Label)

Terminal NameName of terminal

Type of TerminalType of terminal, one of Input or Output

Total Number of InvocationsTotal number of invocations

TCP/IP for z/OS componentCustomizationv Making input data available

– Enabling SMF record type 119v Telnet serverv FTP serverv Reviewing the DRLJCOLL jobv Migrating from SMF record type 118 to 119

Data flow


Data tablesv TCP_API_CALLS_H, _D, _Wv TCP_FTP_CLIENT_T, _H, _D, _Wv TCP_FTP_SERVER_T, _H, _D, _Wv TCP_GEN_ICMP_H, _D, _Wv TCP_GEN_IP_H, _D, _Wv TCP_GEN_TCP_H, _D, _Wv TCP_GEN_UDP_H, _D, _Wv TCP_INTERFACE_H, _D, _Wv TCP_SERVER_CONN_H, _D, _Wv TCP_TCPSERV_PORT_H, _D, _Wv TCP_TN3270_CLNT_T, _H, _D, _Wv TCP_TN3270_SERV_T, _H, _D, _Wv TCP_TNSERV_LOGN_Hv TCP_UDP_SOCK_CLO_H, _D, _Wv TCP_UDPSERV_PORT_H, _D, _W

Reportsv TCP/IP FTP Transmission reportv TCP/IP ICMP TCPIPSTATISTICS Input reportv TCP/IP ICMP TCPIPSTATISTICS Output reportv TCP/IP Interface Statistics reportv TCP/IP IP TCPIPSTATISTICS Error reportv TCP/IP IP TCPIPSTATISTICS hourly reportv TCP/IP IP TCPIPSTATISTICS daily report


v TCP/IP TCP TCPIPSTATISTICS reportv TCP/IP TCP Connection Performance reportv TCP/IP TCP Server Port Connection Statistics reportv TCP/IP TELNET Server Active Logon by Hour reportv TCP/IP TELNET Server Bytes Traffic reportv TCP/IP TELNET AVG Connection Time to Application reportv TCP/IP UDP Sockets Traffic, Daily reportv TCP/IP UDP TCPIPSTATISTICS report

CustomizationBefore you can use the TCP/IP for z/OS component to collect data, you mustcustomize the component by making input data available.

Making input data availableThis section describes the SMF records for the Telnet and FTP servers, API calls,and FTP and Telnet client calls. The EZASMF76 macro in the TCP/IP SEZAMAClibrary can be used to map the TCP/IP SMF records. EZASMF76 producesassembler level DSECTs for the Telnet (Server and Client), FTP (Server and Client),and API SMF records.

To create the Telnet SMF Record layout, code:EZASMF76 TELNET=YES

To create the FTP SMF Record layout, code:EZASMF76 FTP=YES

To create the API SMF Record layout, code:EZASMF76 API=YES

To have all possible records created, use the SMFCONFIG statement to log the useof TCP by applications using SMF log records. Code the SMFCONFIG statement inthe TCP/IP profile member as follows:SMFCONFIG TCPINIT TCPTERM FTPCLIENT TN3270CLIENT.TCPIPSTATISTICS

You can log Telnet and FTP activity, and TCP API activity.

Enabling SMF record type 119:To enable SMF record type 119, perform the following steps:1. Code the SMFCONFIG statement in the TCP/IP profile member:

SMFCONFIGTYPE119 TCPINIT TCPTERM FTPCLIENT TN3270CLIENT TCPIPSTATISTICSIFSTATISTICS PORTSTATISTICS TCPSTACK UPDSTACK

To verify that the parameters have been enabled, use the command netstatconfig -f

2. In the TCP/IP FTPDATA member, add the following lines:SMF TYPE119;SMFAPPE TYPE119;SMFDEL TYPE119;SMFLOGN TYPE119;SMFREN TYPE119;SMFRETR TYPE119;


SMFSTOR TYPE119;SMFEXIT TYPE119;SMFJES TYPE119;SMFSQL TYPE119;

Telnet serverThe TCP/IP server provides services to many clients and, therefore, the systemadministrator needs access to information about the operation of the clients toresolve any problems and to manage the system. SMF provides logging records forsuch management purposes. TCP/IP SMF records are independent of the IPconnection. They are created for both offload host connections and regular hostconnections.

Use the SMF parameters, coded as SMFINIT STD and SMFTERM STD, in theTELNETPARMS statement to configure the Telnet server to write SMF records. IfSMF parameters are not coded in the TELNETPARMS statement, no SMF recordswill be written by the Telnet server.

FTP serverIf you want the FTP server to write type 118 (X'76') SMF records, code the SMFsubtype statement SMF STD in the FTP.DATA data set. If the SMF subtypestatement is not coded in the FTP.DATA data set, no SMF records are written bythe FTP server.

Reviewing the DRLJCOLL jobTo obtain the collect JCL:1. Select 2, Tivoli Decision Support for z/OS Administration from the Primary

Menu.2. Select 3, Logs.3. Select SMF from the list of logs.4. Select the Utilities pull-down and press Enter.5. Select 1, Collect.6. Type your installation-specific information in the displayed window and press

Enter.-OR-

7. Before running the Tivoli Decision Support for z/OS Collect job, update theDRLJCOLL job (a member in the DRLxxx.SDRLCNTL library) to include thecollection of TCP/IP log data sets. Follow the instructions in the commentssection of this job to modify the appropriate JCL statements.

Migrating from SMF record type 118 to 119With Tivoli Decision Support for z/OS 1.7, the SMF record type 119 has beenintroduced. You are recommended to modify your procedures to collect data sothat you use record type 119, instead of 118. For details about the changesintroduced by the record type 119, refer to the description of the data table fieldsin Data tables.

You can still use record type 118 on SMF log, by running the migration jobDRLJ118 (for details, refer to the Administration Guide and Reference). However, thisshould be only a temporary choice and you should migrate back to record type 119by running the migration job DRLJ119 (for details, refer to the Administration Guideand Reference).


Data flowThe TCP/IP for z/OS component collects records from the SMF data set and storesextracted and summarized data in the Tivoli Decision Support for z/OS database.The reporting function extracts data from the database and creates reports that yourequest through the reporting dialogs.

Figure 20 shows an overview of the flow of data from the TCPIP, through theTCP/IP for z/OS component of Tivoli Decision Support for z/OS, and finally intousable reports.


Figure 20. TCP/IP for z/OS component data flow


Log and record definitionsBy default, the TCP/IP for z/OS component includes the following log definitions:

Log Type SMF record type

SMF 119

SMF118 118

You can change the default settings by running the migration job DRLJ118, whichsets up the following condition:

Log Type SMF record type

SMF 118

SMF119 119

The TCP/IP for z/OS component processes the following records:

SMF record type SubtypeRecorddefinition Description

118 1 SMF_118_1 TCP/IP API INIT calls for sockets

118 2 SMF_118_1 TCP/IP API TERM calls for sockets

118 3 SMF_118_3 TCP/IP FTP CLIENT calls

118 4 SMF_118_4 TCP/IP TELNET CLIENT calls

118 5 SMF_118_5 TCP/IP General statistics

118 20 SMF_118_20 TCP/IP TELNET SERVER INIT calls

118 21 SMF_118_21 TCP/IP TELNET SERVER TERM calls

118 70 SMF_118_70 TCP/IP FTP SERVER - append

118 71 SMF_118_70 TCP/IP FTP SERVER - delete

118 72 SMF_118_70 TCP/IP FTP SERVER - log failed

118 73 SMF_118_70 TCP/IP FTP SERVER - rename

118 74 SMF_118_70 TCP/IP FTP SERVER - retrieve

118 75 SMF_118_70 TCP/IP FTP SERVER - store

119 1 SMF_119_1 TCP connection initiation

119 2 SMF_119_2 TCP connection termination

119 3 SMF_119_3 FTP client transfer

119 5 SMF_119_5 TCP/IP statistics

119 6 SMF_119_6 Interface statistics

119 7 SMF_119_7 Server port statistics

119 8 SMF_119_8 TCP/IP stack start/stop

119 10 SMF_119_10 UDP socket close

119 20 SMF_119_20 TN3270 Server SNA session initiation

119 21 SMF_119_21 TN3270 Server SNA session termination

119 22 SMF_119_22 TSO Telnet client connection initiation

119 23 SMF_119_23 TCP Telnet client connection termination

119 70 SMF_119_70 FTP Server transfer completion


SMF record type SubtypeRecorddefinition Description

119 72 SMF_119_72 FTP Server login failure

119 73 SMF_119_73 IPSec IKE Tunnel Activation/Refresh record

119 74 SMF_119_74 IPSec IKE Tunnel Deactivation/Expire record

119 75 SMF_119_75_80 IPSec Dynamic Tunnel Activation/Refresh

119 76 SMF_119_75_80 IPSec Dynamic Tunnel Deactivation record

119 77 SMF_119_75_80 IPSec Dynamic Tunnel Added record

119 78 SMF_119_75_80 IPSec Dynamic Tunnel Removed record

119 79 SMF_119_75_80 IPSec Manual Tunnel Activation record

119 80 SMF_119_75_80 IPSec Manual Tunnel Deactivation record

For a complete description of these records, see the z/OS Communication Server: IPConfiguration Reference.

Data tablesThis chapter describes the data tables used by the TCP/IP for z/OS component.

TCP_API_CALLS_H, _D, _WThis table provides hourly, daily, and weekly API CALLS statistics for z/OSTCP/IP. Data is based on SMF record type 118 (subtype 1) and SMF record type119 (subtypes 1 and 2).


TCP_API_CALLS_H7 days

TCP_API_CALLS_D30 days

TCP_API_CALLS_W365 days


DATE K DATE Date when the statistics record was written to SMF.From SMAPIDTE (record type 118) or SMFHDDTE(record type 119).

TIME K TIME Time when the statistics record was written to SMF.From SMAPITME (record type 118) or SMFHDTME(record type 119). Applies only to _H.

MVS_SYSTEM_ID K CHAR(4) MVS system ID. This is the SMF system ID. FromSMAPISID (record type 118) or SMFHDSID (recordtype 119).

SUB_SYSTEM_ID K CHAR(4) Subsystem identifier. This is the value set by theSUBSYS=option specified in the SMF macros. FromSMAPISSI (record type 118) or SMFHDSSI (recordtype 119).

LOCAL_IP_ADDR K VARCHAR(46) Fullword local IP address. From SMAPILIP (recordtype 118) or AP_TILIP (record type 119_1) orAP_TTLIP (record type 119_2).



LOCAL_PORT K INTEGER Local Port number. From SMAPILPN (record type118) or AP_TILPort (record type 119_1) orAP_TTLPort (record type 119_2).

FOREIGN_IP_ADDRESS K VARCHAR(46) Foreign IP address. From SMAPIFIP or (record type118) or AP_TIRIP (record type 119_1) or AP_TTRIP(record type 119_2).

FOREIGN_PORT K INTEGER Foreign Port number. From SMAPIFPN (record type118) or AP_TIRPort (record type 119_1) orAP_TTRPort (record type 119_2).

CONNECTION_STAT K CHAR(4) Status of the connection, INIT or TERM. FromSMAPISTS (record type 118) or the value INIT (recordtype 119_1) or the value TERM (record type 119_2).

SYSPLEX_NAME K CHAR(8) Sysplex name from SYSPLEX in COUPLExx. FromTI_SysplexName (record type 119) or $UNKNOWN(record type 118).

BYTES_IN FLOAT Bytes in. This is valid only for TERMINATION. FromSMAPIBIN (record type 118) or AP_TTInBytes (recordtype 119).

BYTES_OUT FLOAT Bytes out. This is valid only for TERMINATION.From SMAPIBOU (record type 118) orAP_TTOutBytes (record type 119).

JOB_DATE DATE Date, for HPNS application only, when the job wasstarted by the JES. It is in the form 0CYYDDDF,where C is 0 for 19yy and 1 for 20yy. FromSMAPISTD (record type 118). Otherwise, date whenthe connection was established. From AP_TIDate(record type 119_1) or AP_TTTDate (record type119_2).

JOB_ID CHAR(8) Job ID. The JES job identifier. From SMAPIJID (recordtype 118). Otherwise, the TCP socket resource ID(connection ID). From AP_TIConnID (record type119_1) or AP_TTConnID (record type 119_2).

JOB_NAME CHAR(8) Job name. For interactive TSO API is the user TSOuserid. For batch-submitted jobs: the name of the jobcard. For started procs: the name of the procedure.From SMAPIJNM (record type 118).For TCP socket resource name: name of the addressspace that established the TCP connection. FromAP_TIRName (record type 119_1) or AP_TTRName(record type 119_2).

JOB_START_TIME TIME Job start time. From SMAPISTT (record type 118).Otherwise, time when the connection was established.From AP_TITime (record type 119_1) or AP_TTTName(record type 119_2).

MVS_SYSTEM_NAME CHAR(8) System name from SYSNAME in IEASYSxx. FromTI_SYSName (record type 119 only).

TCPIP_STACK_NAME CHAR(8) TCP/IP stack name. From TI_Stack (record type 119only).


TCP_FTP_CLIENT_T, _H, _D, _WThis table provides detailed, hourly, daily, and weekly FTP Client statistics forz/OS TCP/IP. Data is based on SMF record type 118 (subtype 3) and SMF recordtype 119 (subtype 3).


TCP_FTP_CLIENT_T1 day

TCP_FTP_CLIENT_H7 days

TCP_FTP_CLIENT_D30 days

TCP_FTP_CLIENT_W365 days


DATE K DATE Date when the statistics record was written to SMF.From SFTPCDTE (record type 118) or SMFHDDTE(record type 119).

TIME K TIME Time when the statistics record was written to SMF.From SFTPCTME (record type 118) or SMFHDTME(record type 119). Applies only to _H and _T.

TIMESTAMP K TIMESTAMP Date and time when the record was written to SMF.SFTPCDTE and SFTPCTME (record type 118) orSMFHDDTE and SMFHDTME (record type 119).Applies only to _T.

MVS_SYSTEM_ID K CHAR(4) MVS system ID. This is the SMF system ID. FromSFTPCSID (record type 118) or SMFHDSID (recordtype 119).

SUB_SYSTEM_ID K CHAR(4) Subsystem identifier. This is the value set by theSUBSYS=option specified in the SMF macros. FromSFTPCSSI (record type 118) or SMFHDSSI (recordtype 119).

LOCAL_IP_ADDR K VARCHAR(46) Fullword local IP address. From SFTPCLIP (SMFrecord type 118) or FT_FCDLIP (SMF record type 119).

LOCAL_PORT K INTEGER Local Port number. From SFTPCLPN (record type 118)or FT_FCDLPort (record type 119).

FOREIGN_IP_ADDRESS K VARCHAR(39) Foreign IP address. From SFTPCFIP (SFM record type118) or FT_FCDRIP (SMF record type 119).

FOREIGN_PORT K INTEGER Foreign Port number. From SFTPCFPN (record type118) or FT_FCDRPort (record type 119).


BYTE_COUNT FLOAT Byte count of transmission. From SFTPCBYT (recordtype 118) or FT_FCBytes (record type 119).

DATA_FORMAT CHAR(1) Data format. A-ASCII, E_EBCDIC, and so on. FromSFTPCDTF (record type 118) or FT_FCType (recordtype 119).



DATASET_TYPE CHAR(1) Data Set Type (P-PDS, Blank-Sequential). FromSFTPCDSO (record type 118) or FT_FCDSType (recordtype 119).

END_TRANS_TIME TIME End Time of Transmission. From SFTPCETT (recordtype 118) or FT_FCETime (record type 119).

FTP_ID CHAR(1) FTP ID. This is C for a client. From SFTPCID (recordtype 118). For compatibility, it is set to C whencollecting record type 119.

FTP_SUBCOMMAND CHAR(4) FTP subcommand (for example RETR, STOR, APPE,REN, MDIR, DELE). From SFTPCSBC (record type118) or FT_FCCmd (record type 119).

FTP_USER_ID CHAR(8) User ID of the user of FTP. From SFTPCUSR (recordtype 118) or FT_FCLUser (record type 119).

HOST_ID CHAR(8) Host ID. From SFTPCHID (record type 118) orFT_FCHostname (record type 119).

LOCAL_DIRECTORY CHAR(44) Local directory, except for REN, where it is the TOargument. From SFTPCDIR (record type 118 only).

LOCAL_DS_NAME VARCHAR(254) Local dataset name. From SFTPCDSN (record type118) or FT_FCFNM (record type 119).


REMOTE_ID CHAR(8) Remote userid. From SFTPCREU (record type 118) orFT_FCRUser (record type 119).

START_TRANS_TIME TIME Start Time of Transmission. From SFTPCSTT (recordtype 118) or FT_FCSTime (record type 119).

TCPIP_STACK_NAME CHAR(8) TCP/IP stack name. From TI_Stack.

TRANSFER_FORMAT CHAR(1) Mode (S-Stream, B-Block, C-Compressed). FromSFTPCTRF (record type 118) or FT_FCMode (recordtype 119).

TCP_FTP_SERVER_T, _H, _D, _WThis table provides detailed, hourly, daily, and weekly FTP Server statistics forz/OS TCP/IP. Data is based on SMF record type 118 (subtype 70) and SMF recordtype 119 (subtype 70).


TCP_FTP_SERVER_T1 day

TCP_FTP_SERVER_H7 days

TCP_FTP_SERVER_D30 days

TCP_FTP_SERVER_W365 days


DATE K DATE Date when the statistics record was written to SMF.From SFTPSDTE (record type 118) or SMFHDDTE(record type 119).



TIME K TIME Time when the statistics record was written to SMF.From SFTPSTME (record type 118) or SMFHDTME(record type 119). Applies only to _H and _T.

TIMESTAMP K TIMESTAMP Date and time when the record was written to SMF.SFTPSDTE and SFTPSTME (record type 118) orSMFHDDTE and SMFHDTME (record type 119).Applies only to _T.

MVS_SYSTEM_ID K CHAR(4) MVS system ID. This is the SMF system ID. FromSFTPSSID (record type 118) or SMFHDSID (recordtype 119).

SUB_SYSTEM_ID K CHAR(4) Subsystem identifier. This is the value set by theSUBSYS=option specified in the SMF macros. FromSFTPSSSI (record type 118) or SMFHDSSI (record type119).

FULL_LOC_IP_ADDR K VARCHAR(46) Fullword local IP address. From SFTPSLIP. (recordtype 118) or FT_FSDLIP (record type 119)

LOCAL_PORT_ID K INTEGER Local port number. From SFTPSLPN (record type 118)or FT_FSCRPort (record type 119).


BYTE_COUNT REAL Byte count of transmission. From SFTPSBYT (recordtype 118) or FT_FSBytes (record type 119).

DATA_FORMAT CHAR(1) Data Format (A-ASCII, E-EBCDIC, and so on) FromSFTPSDTF (record type 118) or FT_FSType (recordtype 119).

DATASET_TYPE CHAR(1) Data Set Type (P-Partitioned, Blank-Sequential). FromSFTPSSDTY (record type 118) or FT_FSDsType (recordtype 119).

DS_NAME VARCHAR(254) DS name. From SFTPSLIN (record type 118) orFT_FSFILENAME1 (record type 119).

END_TRANS_TIME TIME End Time of Transmission. From SFTPSENT (recordtype 118) or FT_FSETime (record type 119).

FTP_COMMAND CHAR(4) FTP subcommand (for example STOR, REN, DELE).From SFTPSCMD (record type 118) or FT_FSCmd(record type 119).

FTP_FILE CHAR(4) FTP file type (SEQ, JES, SQL). From SFTPSFTY(record type 118) or FT_FSFType (record type 119).

FTP_ID CHAR(1) FTP ID. This is S for a server. From SFTPSFID (recordtype 118). For compatibility, it is set to S whencollecting record type 119.

FULL_REM_IP_ADDR VARCHAR(46) Fullword remote IP address. From SFTPSRIP (recordtype 118) or FT_FSDRIP (record type 119).

LOCAL_USERID CHAR(8) Local User ID. From SFTPSLUI (record type 118) orFT_FSSUser (record type 119).

MEMBER_PDS_NAME CHAR(8) Member name for PDS. From SFTPSMNM (recordtype 118) or FT_FSM1 (record type 119).

MODE CHAR(1) Mode (S-Stream, B-Block, C-Compressed) FromSFTPSMOD (record type 118) or FT_FSMode (recordtype 119).




REMOTE_PORT_ID INTEGER Remote Port Number. From SFTPSRPN (record type118) or FT_FSDLPort (record type 119).

SECOND_DS_NAME VARCHAR(254) Second data set name, if needed (for example,Rename). From SFTPSSDS (record type 118) orFT_FSFileName2 (record type 119).

SECOND_MEMBER_NAME CHAR(8) Second member name, if needed (for example,Rename). From SFTPSSMN (record type 118) orFT_FSM2 (record type 119).

START_TRANS_TIME TIME Start Time of Transmission. From SFTPSSTT (recordtype 118) or FT_FSSTime (record type 119).

STARTED_TASK_QUAL CHAR(8) Started Task Qualifier. From SFTPSSTQ (record type118) or TI_ASName (record type 119).

STRUCTURE CHAR(1) Structure (F-File) From SFTPSSTR (record type 118) orFT_FSStruct (record type 119).

TCPIP_HOST_NAME VARCHAR(254) TCP/IP host name. From SFTPSHNM (record type118) or FT_FSHostname (record type 119).


TCP_GEN_ICMP_H, _D, _WThis table provides hourly, daily, and weekly TCP/IP statistics for the ICMPsection information in z/OS TCP/IP. Data is based on SMF record type 118(subtype 5) and SMF record type 119 (subtype 5).


TCP_GEN_ICMP_H7 days

TCP_GEN_ICMP_D30 days

TCP_GEN_ICMP_W365 days


DATE K DATE Date when the statistics record was written to SMF.From SMFHDDTE.

TIME K TIME Time when the statistics record was written to SMF.From SMFHDTME. Applies only to the _H table.

MVS_SYSTEM_ID K CHAR(4) MVS system ID. This is the SMF system ID. FromSMFHDSID.

SUB_SYSTEM_ID K CHAR(4) Subsystem identifier. This is the value set by theSUBSYS=option specified in the SMF macros. FromSMFHDSSI.

TCPIP_PROCNAME K CHAR(8) TCP/IP Procname. From SMSUPRNM (record type118). TCP/IP Stack name. From TI_Stack (record type119).

TCPIP_ASID K CHAR(8) TCP/IP Asid. From SMSUASID (record type 118) orTI_ASID (record type 119).




TCPIP_VER K CHAR(4) TCP/IP version. Possible values IPV4 and IPV6.

ICMP_INADDRMASKS REAL In Address Mask Request messages. From ICMPIAM(record type 118) or AP_TSICInAddrMask ifTCPIP_VER=IPV4 (record type 119).

ICMP_INADDRMSKREP REAL In Address Mask Reply messages. From ICMPIAMR(record type 118) or AP_TSICInAddrMRep ifTCPIP_VER=IPV4 (record type 119).

ICMP_INDEST_UNRCH REAL In Destination unreachable. From ICMPINTE (recordtype 118) or AP_TSICInDstUnreac if TCPIP_VER=IPV4(record type 119), or AP_TSC6InDstUnreac ifTCPIP_VER=IPV6 (record type 119).

ICMP_INECHOS REAL In Echo Request messages. From ICMPINEC (recordtype 118) or AP_TSICInEcho if TCPIP_VER=IPV4(record type 119), or AP_TSC6InEcho ifTCPIP_VER=IPV6 (record type 119).

ICMP_INECHOS_REPS REAL In Echo Reply messages. From ICMPIECR (record type118) or AP_TSICInEchoRep if TCPIP_VER=IPV4 (recordtype 119), or AP_TSC6InEchoRep if TCPIP_VER=IPV6(record type 119).

ICMP_INMSGS REAL In ICMP messages. From ICMPINMS (record type 118),or AP_TSICInMsg if TCPIP_VER=IPV4 (record type119), or AP_TSC6InMsg if TCPIP_VER=IPV6 (recordtype 119).

ICMP_INMSGS_ERRS REAL In ICMP messages error. From ICMPINER (record type118), or AP_TSICInError if TCPIP_VER=IPV4 (recordtype 119), or AP_TSC6InError if TCPIP_VER=IPV6(record type 119).

ICMP_INPAR_PRBMSGS REAL In Parameter Problem messages. From ICMPINPP(record type 118) or AP_TSICInParmProb ifTCPIP_VER=IPV4 (record type 119), orAP_TSC6InParmProb if TCPIP_VER=IPV6 (record type119).

ICMP_INREDIRECTS REAL In Redirect messages. From ICMPINRE (record type118), or AP_TSICInRedirect if TCPIP_VER=IPV4 (recordtype 119), or AP_TSC6InRedirect if TCPIP_VER=IPV6(record type 119).

ICMP_INSRC_QUENCHS REAL In Source Quench messages. From ICMPINSQ (recordtype 118) or AP_TSICInSrcQuench if TCPIP_VER=IPV4(record type 119).

ICMP_INTIMESTAMPS REAL In Timestamp Request messages. From ICMPINTM(record type 118) or AP_TSICInTstamp ifTCPIP_VER=IPV4 (record type 119).

ICMP_INTM_EXCMSGS REAL In Time Exceed messages. From ICMPINPP (recordtype 118), or AP_TSICInTimeExcd if TCPIP_VER=IPV4(record type 119), or AP_TSC6InTimeExcd ifTCPIP_VER=IPV6 (record type 119).

ICMP_INTMSTAMPREP REAL In Timestamp Reply messages. From ICMPINTR(record type 118) or AP_TSICInTstampRep ifTCPIP_VER=IPV4 (record type 119).



ICMP_OUTADDRMASKS REAL Out Address Mask Request messages. From ICMPOAM(record type 118) or AP_TSICOutAddrMask ifTCPIP_VER=IPV4 (record type 119).

ICMP_OUTADDRMSKREP REAL Out Address Mask Reply messages. From ICMPOAMR(record type 118) or AP_TSICOutAddrMRep ifTCPIP_VER=IPV4 (record type 119).

ICMP_OUTDEST_UNRCH REAL Out Destination unreachable. From ICMPODUN(record type 118) or AP_TSICOutDstUnrea ifTCPIP_VER=IPV4 (record type 119), orAP_TSC6OutDstUnrch if TCPIP_VER=IPV6 (recordtype 119).

ICMP_OUTECHOS REAL Out Echo Request messages. From ICMPOECH (recordtype 118) or AP_TSICOutEcho if TCPIP_VER=IPV4(record type 119), or AP_TSC6OutEcho ifTCPIP_VER=IPV6 (record type 119).

ICMP_OUTECHOS_REPS REAL Out Echo Reply messages. From ICMPOECR (recordtype 118) or AP_TSICOutEchoRep if TCPIP_VER=IPV4(record type 119), or AP_TSC6OutEchoRep ifTCPIP_VER=IPV6 (record type 119).

ICMP_OUTMSGS REAL Out ICMP messages. From ICMPOMSG (record type118) or AP_TSICOutMsg if TCPIP_VER=IPV4 (recordtype 119), or AP_TSC6OutMsg if TCPIP_VER=IPV6(record type 119).

ICMP_OUTMSGS_ERRS REAL Out ICMP messages error. From ICMPOERR (recordtype 118) or AP_TSICOutError if TCPIP_VER=IPV4(record type 119), or AP_TSC6OutError ifTCPIP_VER=IPV6 (record type 119).

ICMP_OUTPAR_PRBMSG REAL Out Parameter Problem messages. From ICMPOPP(record type 118) or AP_TSICOutParmProb ifTCPIP_VER=IPV4 (record type 119), orAP_TSC6OutParmProb if TCPIP_VER=IPV6 (recordtype 119).

ICMP_OUTREDIRECTS REAL Out Redirect messages. From ICMPORED (record type118) or AP_TSICOutRedirect if TCPIP_VER=IPV4(record type 119), or AP_TSC6OutRedirect ifTCPIP_VER=IPV6 (record type 119).

ICMP_OUTSRC_QUENCH REAL Out Source Quench messages. From ICMPOSQ (recordtype 118) or AP_TSICOutSrcQuenc if TCPIP_VER=IPV4(record type 119).

ICMP_OUTTIMESTAMPS REAL Out Timestamp Request messages. From ICMPOTIM(record type 118) or AP_TSICOutTstamp ifTCPIP_VER=IPV4 (record type 119).

ICMP_OUTTM_EXCMSGS REAL Out Time Exceed messages. From ICMPOTEX (recordtype 118) or AP_TSICOutTimeExcd if TCPIP_VER=IPV4(record type 119), or AP_TSC6OutTimeExcd ifTCPIP_VER=IPV6 (record type 119).

ICMP_OUTTMSTAMPREP REAL Out Timestamp Reply messages. From ICMPOTMR(record type 118) or AP_TSICOutTstampRe ifTCPIP_VER=IPV4 (record type 119).




TCPIP_IDENT_REC CHAR(20) TCP/IP SMF reason. From SMSUREAS (record type118). Possible values are:

Value Meaning

First recordFirst SMF record. Corresponds to X'80'.

SMF Interval recordSMF interval record. Corresponds to X'40'.

Last rec/End StatsLast SMF record at End Stats. Corresponds toX'20'.

Last rec/shutdownLast SMF record at shutdown. Corresponds toX'10'.

FromTI_Reason (record type 119). Possible values are:

Value Meaning

Event recordEvent record. Corresponds to X'08'.

Int. stat. rec. MoreInterval record, more records follow.Corresponds to X'C0'.

Int. stat. rec. LastInterval record, last record in set. Correspondsto X'80'.

End stat. rec. MoreInterval ending stats, more records follow.Corresponds to X'60'.

End stat. rec. LastInterval ending stats, last record in set.Corresponds to X'20'.

Shutdown stat. MoreInterval shutdown stats, more records follow.Corresponds to X'50'.

Shutdown stat. LastInterval shutdown stats, last record in set.Corresponds to X'10'.

TCPIP_START_TOD TIMESTAMP TCP/IP Startup TOD. From SMSUSTOD (record type118 only).

TCP_GEN_IP_H, _D, _WThis table provides hourly, daily, and weekly TCP/IP statistics for the IP sectioninformation in z/OS TCP/IP. Data is based on SMF record type 118 (subtype 5)and SMF record type 119 (subtype 5).


TCP_GEN_IP_H7 days

TCP_GEN_IP_D30 days


TCP_GEN_IP_W365 days






TCPIP_PROCNAME K CHAR(8) TCP/IP Procname. From SMSUPRNM (record type118).

TCP/IP Stack name. From TI_Stack (record type 119).

TCPIP_ASID K CHAR(8) TCP/IP ASID. From SMSUASID (record type 118) orTI_ASID (record type 119).


TCPIP_VER K CHAR(4) TCP/IP version. Possible values are IPV4 and IPV6.

IPMAX_REASS_ACTIVE REAL Maximum active reassemblies. From IMRSMMAX(record type 118) or AP_TSIPMaxRsmb ifTCPIP_VER=IPV4 (record type 119).

IPNUM_DISC_REASSFR REAL Reassembly flags. From IMRSMFUL (record type 118)or AP_TSIPRsmbFlags if TCPIP_VER=IPV4 (recordtype 119).

IPNUM_REASS_ACTIVE REAL Number of active reassemblies. From IMRSMACT(record type 118) or AP_TSIPCurRsmb ifTCPIP_VER=IPV4 (record type 119).

IPTOT_ATT_FWDTGR REAL Total attempts to forward datagrams. FromIMIFWDDG (record type 118), or AP_TSIPAttFwdDataif TCPIP_VER=IPV4 (record type 119), orAP_TSP6AttFwdData if TCPIP_VER=IPV6 (recordtype 119).

IPTOT_DATAGR_FRAGM REAL Total datagrams fragmented. From IMFRAGOK(record type 118), or AP_TSIPRecFgmt ifTCPIP_VER=IPV4 (record type 119), orAP_TSP6RecFgmt if TCPIP_VER=IPV6 (record type119).

IPTOT_DATAGR_REASS REAL Total datagrams reassembled. From IMRSMOK(record type 118), or AP_TSIPRsmb ifTCPIP_VER=IPV4 (record type 119), or AP_TSP6Rsmbif TCPIP_VER=IPV6 (record type 119).

IPTOT_DELIV_DATA REAL Total delivered datagrams. From IMIDELVR (recordtype 118), or AP_TSIPDlvData if TCPIP_VER=IPV4(record type 119), or AP_TSP6DlvData ifTCPIP_VER=IPV6 (record type 119).



IPTOT_DISC_ADDR REAL Total discarded: address errors. From IMIADRER(record type 118), or AP_TSIPDscAddr ifTCPIP_VER=IPV4 (record type 119), orAP_TSP6DscAddr if TCPIP_VER=IPV6 (record type119).

IPTOT_DISC_DATAG REAL Total discarded datagrams. From IMIHDRER (recordtype 118), or AP_TSIPDscData if TCPIP_VER=IPV4(record type 119), or AP_TSP6DscData ifTCPIP_VER=IPV6 (record type 119).

IPTOT_DISC_FRAGM REAL Total discarded: fragmentation failed. FromIMFRGFLD (record type 118), or AP_TSIPDscDFgmt ifTCPIP_VER=IPV4 (record type 119), orAP_TSP6DscDFgmt if TCPIP_VER=IPV6 (record type119).

IPTOT_DISC_OTHER REAL Total discarded: other. From IMIDISC (record type118), or AP_TSIPDscDOth if TCPIP_VER=IPV4 (recordtype 119), or AP_TSP6DscDOth if TCPIP_VER=IPV6(record type 119).

IPTOT_DISC_UNPR REAL Total discarded: unknown protocol. From IMIUNPRT(record type 118), or AP_TSIPDscDUnkPr ifTCPIP_VER=IPV4 (record type 119), orAP_TSP6DscDUnkPr if TCPIP_VER=IPV6 (recordtype 119).

IPTOT_FRAGM_GENER REAL Total fragments generated. From IMFRGCRE (recordtype 118), or AP_TSIPXFgmt if TCPIP_VER=IPV4(record type 119), or AP_TSP6XFgmt ifTCPIP_VER=IPV6 (record type 119).

IPTOT_REASS_FAILED REAL Total datagrams reassembled: failed. FromIMRSMFLD (record type 118), or AP_TSIPFailRsmb ifTCPIP_VER=IPV4 (record type 119), orAP_TSP6FailRsmb if TCPIP_VER=IPV6 (record type119).

IPTOT_REASS_TMOUT REAL Total reassembly timeouts. From IMRSMTOS (recordtype 118), or AP_TSIPTimeouts if TCPIP_VER=IPV4(record type 119), or AP_TSP6Timeouts ifTCPIP_VER=IPV6 (record type 119).

IPTOT_REC_DATAGR REAL Total received datagrams. From IMIRECV (recordtype 118), or AP_TSIPRecData if TCPIP_VER=IPV4(record type 119), or AP_TSP6RecData ifTCPIP_VER=IPV6 (record type 119).

IPTOT_REC_REASSREQ REAL Total received: reassembly required. From IMRSMREQ(record type 118), or AP_TSIPRecDRsbm ifTCPIP_VER=IPV4 (record type 119), orAP_TSP6RecDRsbm if TCPIP_VER=IPV6 (record type119).

IPTOT_ROUT_DISCRDS REAL Total routing discards. From IMRTDISC (record type118), or AP_TSIPRouteDisc if TCPIP_VER=IPV4(record type 119), or AP_TSP6RouteDisc ifTCPIP_VER=IPV6 (record type 119).

IPTOT_SENT_DATA REAL Total sent datagrams. From IMIREQST (record type118), or AP_TSIPXData if TCPIP_VER=IPV4 (recordtype 119), or AP_TSP6XData if TCPIP_VER=IPV6(record type 119).



IPTOT_SENT_DISC REAL Total sent discarded: other. From IMODISC (recordtype 118), or AP_TSIPXDscOth if TCPIP_VER=IPV4(record type 119), or AP_TSP6XDscOth ifTCPIP_VER=IPV6 (record type 119).

IPTOT_SENT_DISNOR REAL Total sent discarded: no route. From IMONORTE(record type 118), or AP_TSIPXDscRoute ifTCPIP_VER=IPV4 (record type 119), orAP_TSP6XDscRoute if TCPIP_VER=IPV6 (record type119).



Value Meaning




Last rec/shutdownLast SMF record at shutdown. Correspondsto X'10'.


Value Meaning



Int. stat. rec. LastInterval record, last record in set.Corresponds to X'80'.







TCP_GEN_TCP_H, _D, _WThis table provides hourly, daily, and weekly TCP/IP statistics for the TCP sectioninformation in z/OS TCP/IP. Data is based on SMF record type 118 (subtype 5)and SMF record type 119 (subtype 5).


TCP_GEN_TCP_H7 days

TCP_GEN_TCP_D30 days

TCP_GEN_TCP_W365 days











TCP_ACTIVE_OPENS REAL Active opens. From ACTVOPEN (record type 118) orAP_TSTCOpenConn (record type 119).

TCP_CURR_EST_NUM REAL Number currently established. From CURESTAB(record type 118) or AP_TSTCEstab (record type 119).

TCP_EST_RESET_NUM REAL Number of resets. From ESTRESET (record type 118)or AP_TSTCConReset (record type 119).

TCP_INPUT_ERR REAL Input errors. From INERRS (record type 118) orAP_TSTCInErrs (record type 119).

TCP_INPUT_SEGM REAL Input segments. From INSEGS (record type 118) orAP_TSTCInSegs (record type 119).

TCP_MAX_CONNECT REAL Maximum connections. From MAXCONN (recordtype 118) or AP_TSTCMxCon (record type 119).

TCP_MAXRETR_TIME REAL Maximum retransmit time (in milliseconds). FromRTOMAX (record type 118) or AP_TSTCMxRet (recordtype 119).



TCP_MINRETR_TIME REAL Minimum retransmit time (in milliseconds). FromRTOMIN (record type 118) or AP_TSTCMinRet(record type 119).

TCP_OPEN_FAILS REAL Open failures. From ATTMFAIL (record type 118) orAP_TSTCOFails (record type 119).

TCP_OUT_RESET_NUM REAL Number of resets. From OUTERRS. (record type 118)or AP_TSTCReset (record type 119)

TCP_OUTPUT_SEGM REAL Output segments. From OUTSEGS (record type 118)or AP_TSTCOSegs (record type 119).

TCP_PASSIVE_OPENS REAL Passive opens. From PASSOPEN (record type 118) orAP_TSTCPassConn (record type 119).

TCP_RETR_ALG REAL Retransmit algorithm. From RTOALGRT (record type118) or AP_TSTCAlg (record type 119).

TCP_RETR_SEM REAL Retransmitted segments. From RETRSEGS (recordtype 118) or AP_TSTCRxSegs (record type 119).




Value Meaning






Value Meaning









TCP_GEN_UDP_H, _D, _WThis table provides hourly, daily, and weekly TCP/IP statistics for the UDP sectioninformation in z/OS TCP/IP. Data is based on SMF record type 118 (subtype 5)and SMF record type 119 (subtype 5).


TCP_GEN_UDP_H7 days

TCP_GEN_UDP_D30 days


TCP_GEN_UDP_W365 days














Value Meaning






Value Meaning









UDP_DATAGR_NOPORT REAL UDP datagrams with no ports. From USNOPRTS(record type 118) or AP_TSUDRecNoPort (record type119).

UDP_DATAGR_NOTREC REAL Other UDP datagrams not received. From USINERRS(record type 118) or AP_TSUDNoRec (record type119).

UDP_DATAGR_SENT REAL UDP datagrams sent. From USOTDGRM (record type118) or AP_TSUDXmtData (record type 119).

UDP_RECV_DATAGR REAL Received UDP datagrams. From USINDGRM (recordtype 118) or AP_TSUDRecData (record type 119).


TCP_INTERFACE_H, _D, _WThis table provides hourly, daily, and weekly TCP/IP statistics about theconnection activity for interfaces. Data is based on SMF record type 119 (subtype6).


TCP_INTERFACE_H7 days

TCP_INTERFACE_D30 days

TCP_INTERFACE_W365 days



TIME K TIME Time when the statistics record was written to SMF.From SMFHDTME.

SYSPLEX_NAME K CHAR(8) Sysplex name from SYSPLEX in COUPLExx. FromTI_SysplexName.



INT_HOME_ADDR K VARCHAR(46) Interface HOME address. From IS_IFLnkHome.

INT_NAME K CHAR(16) Link or Interface name. From IS_IFName.

INBOUND_BYTES FLOAT Inbound byte count. From IS_IFInBytes.

INBOUND_PACKETS FLOAT Inbound packets count (sum of IS_IFInUniC,IS_IFInBroadC, IS_IFInMultiC, IS_IFInDisc,IS_IFInError, IS_IFInUProt).

INT_DESCRIPTION CHAR(18) Interface description (TCPIP PROFILE keyword forLINK or INTERFACE type). Possible values include:

802.3 IPAQENET

ATM IPAQENET6

CDLC MPCPT6

CTC IPAQIDIO

ETHERnetIPAQTR

ETHEROR802.3MPCPTP

FDDI OSAENET

HCH OSAFDDI

IBMTRSAMEHOST

IP Unknown

From IS_IFDesc.



MVS_SYSTEM_NAME CHAR(8) System name from SYSNAME in IEASYSxx. FromTI_SYSName.

OUTBOUND_BYTES FLOAT Outbound byte count. From IS_IFOutBytes.

OUTBOUND_PACKETS FLOAT Outbound packets count. (Sum of IS_IFOutUniC,IS_IFOutBroadC, IS_IFOutMultiC, IS_IFOutDisc,IS_IFOutError).

OUTBOUND_QUEUE FLOAT Outboundqueue length. From IS_IFOQL.


TCP_SERVER_CONN_H, _D, _WThis table provides hourly, daily, and weekly TCP/IP statistics about theconnection activity for servers. Data is based on SMF record type 119 (subtype 2).


TCP_SERVER_CONN_H7 days

TCP_SERVER_CONN_D30 days

TCP_SERVER_CONN_W365 days


DATE K DATE Date of connection establishment. From AP_TTSDate.

TIME K TIME Time of connection establishment. From AP_TTSTime.




LOCAL_IP_ADDR K VARCHAR(46) Local IP address at time of connection close. FromAP_TTLIP.

LOCAL_PORT K INTEGER Local port number at the time when the connectionwas closed. From AP_TTLPort.

CONN_DURATION_AVG FLOAT Average duration time of connections.

CONNECTIONS FLOAT Number of connections in the interval.

INBOUND_BYTES FLOAT Inbound byte count. From AP_TTInBytes.


OUTBOUND_BYTES FLOAT Outbound byte count. From AP_TTOutBytes.

RETRANSMISSIONS FLOAT Number of times that a retransmission was required.From AP_TTXRT.

ROUNDTRIP_TIME_AVG FLOAT Average of Round Trip Time at connections closure, inmilliseconds. From AP_TTRTT.



TCP_TCPSERV_PORT_H, _D, _WThis table provides hourly, daily, and weekly TCP/IP statistics about the portsconnection activity. Data is based on SMF record type 119 (subtype 7).


TCP_TCPSERV_PORT_H7 days

TCP_TCPSERV_PORT_D30 days

TCP_TCPSERV_PORT_W365 days



TIME K TIME Date when the statistics record was written to SMF.From SMFDHTME.



SUB_SYSTEM_ID K CHAR(4) Subsystem ID. This is the value set by theSUBSYS=option specified in the SMF macros. FromSMFHDSSI.

SERV_SOCK_NAME K CHAR(8) Server socket resource name (specified in the PORTreservation statement). From SP_TCRName.

PORT_NUMBER K INTEGER Port number. From SP_TCPort.

CONN_REJECT_BUSY FLOAT Number of connection requests that were rejectedbecause of Server Busy conditions. FromSP_TCBusySrv.

CONN_REJECT_ATTACK FLOAT Number of connection requests that were rejectedbecause of SYN Attack detect conditions. FromSP_TCSynAttack.

CONNECTIONS FLOAT Number of successful connections established. FromSP_TCCon.

IP_ADDRESS VARCHAR(46) For bind-specific port reservations: the local IPaddress. From SP_TCBindIP.

MAX_CONNECTIONS FLOAT Highest number of active TCP connections. FromSP_TCHighwater.



TCP_TN3270_CLNT_T, _H, _D, _WThis table provides detailed, hourly, daily and weekly T3270 client statistics forz/OS TCP/IP. Data is based on SMF record type 118 (subtype 4) and SMF recordtype 119 (subtypes 22 and 23).

The default retention period for these tables are:


TCP_TN3270_CLNT_T1 day

TCP_TN3270_CLNT_H7 days

TCP_TN3270_CLNT_D30 days

TCP_TN3270_CLNT_W365 days


DATE K DATE Date when the statistics record was written to SMF.From SMTNCDTE (record type 118) or SMFHDDTE(record type 119).

TIME K TIME Time when the statistics record was written to SMF.From SMTNCTME (record type 118) or SMFHDTME(record type 119). Applies only to _H and _T.

TIMESTAMP K TIMESTAMP Date and time when the record was written to SMF.SMTNCDTE and SMTNCTME (record type 118) orSMFHDDTE and SMFHDTME (record type 119).Applies only to _T.

MVS_SYSTEM_ID K CHAR(4) MVS system ID. This is the SMF system ID. FromSMTNCSID (record type 118) or SMFHDSID (recordtype 119).

SUB_SYSTEM_ID K CHAR(4) Subsystem identifier. This is the value set by theSUBSYS=option specified in the SMF macros. FromSMTNCSSI (record type 118) or SMFHDSSI (recordtype 119).

LOCAL_IP_ADDR K VARCHAR(46) Fullword local IP address. From SMTNCLIP (recordtype 118) orTN_CILIP (record type 119_22) orTN_CTLIP (record type 119_23).

LOCAL_PORT K INTEGER Local port number. From SMTNCLPN (record type118) or TN_CILPort (record type 119_22) orTN_CTLPort (record type 119_23).

REMOTE_IP_ADDR K VARCHAR(46) Remote IP address. From SMTNCRIP (record type118) or TN_CIRIP (record type 119_22) or TN_CTRIP(record type 119_23).

REMOTE_PORT K INTEGER Remote port number. From SMTNCRPN (record type118) or the TN_CIRPort (record type 119_22) orTN_CTRPort (record type 119_23).

CONNECTION_STAT K CHAR(4) LOGN of LOGF for START/STOP or INIT/TRM.From SMTNCLOG (record type 118) or the valueLOGN (record type 119_22) or the value LOGF(record type 119_23)



NJE_NODE_NAME CHAR(8) Local port number. From SMTNCNJE (record type118) or TN_CTNJENode (record type 119).



STARTED_STASK_QFY CHAR(8) Started Task qualifier name, for example TCP/IP.From SMTNCSTN (record type 118) or TI_ASName(record type 119).


TCP_TN3270_SERV_T, _H, _D, _WThis table provides detailed, hourly, daily, and weekly TN3270 server statistics forz/OS TCP/IP. Data is based on SMF record type 118 (subtype 20) and SMF recordtype 119 (subtypes 20 and 21).


TCP_TN3270_SERV_T1 day

TCP_TN3270_SERV_H7 days

TCP_TN3270_SERV_D30 days

TCP_TN3270_SERV_W365 days


DATE K DATE Date when the statistics record was written to SMF.From SMTNSDTE. From SMTNSDTE (record type118) or SMFHDDTE (record type 119).

TIME K TIME Time when the statistics record was written to SMF.From SMTNSTME (record type 118) or SMFHDTME(record type 119). Applies only to _H and _T.

TIMESTAMP K TIMESTAMP Date and time when the record was written to SMF.SMTNSDTE and SMTNSTME (record type 118) orSMFHDDTE and SMFHDTME (record type 119).Applies only to _T.

MVS_SYSTEM_ID K CHAR(4) MVS system ID. This is the SMF system ID. FromSMTNSSID (record type 118) or SMFHDSID (recordtype 119).

SUB_SYSTEM_ID K CHAR(4) Subsystem identifier. This is the value set by theSUBSYS=option specified in the SMF macros. FromSMTNSSSI(record 118) or SMFHDSSI (record 119).

LOCAL_IP_ADDR K VARCHAR(46) Fullword local IP address. From SMTNSLIP (recordtype 118) or TN_NILIP (record type 119_20) orTN_NTLIP (record type 119_21).

LOCAL_PORT K INTEGER Local port number. From SMTNSLPN or TN_NILPort(record type 119_20) or TN_NTLPort (record type119_21).

LU_NAME K CHAR(8) LU name. From SMTNSLUN (record type 118) orTN_NILU (record type 119_20) or TN_NTLU (recordtype 119_21).

APPLICATION_NAME K CHAR(8) Application name. From SMTNSAPN (record type118) or TN_NIAppl (record type 119_20) orTN_NTAppl (record type 119_21).



CONNECTION_STAT K CHAR(4) LOGN or LOGF for START/STOP or INIT/TRM.From SMTNSLOG (record type 118) or the valueLOGN (record type 119_20) or the value LOGF(record type 119_21).


BYTES_IN REAL IN byte count. From SMTNSINB (record type 118) orTN_NTInByte (record type 119).

BYTES_OUT REAL OUT byte count. From SMTNSOUB (record type 118)or TN_NTOutByte (record type 119).

INTLOGIC_DEVADDR REAL Internal Logical device address. From SMTNSILA(record type 118) or TN_NILdev (record type 119_20)or TN_NTLdev (record type 119_21).

LOGF_DATE DATE Date. From SMTNSLFD (record type 118) orTN_NTtDate (record type 119).

LOGF_TIME REAL Duration time. From SMTNSLFT (record type 118) orTN_NTDur (record type 119).


REMOTE_IP_ADDR VARCHAR(46) Remote IP address. From SMTNSRIP (record type 118)or TN_NIRIP (record type 119_20) or TN_NTRIP(record type 119_21).

REMOTE_PORT INTEGER Remote port number. From SMTNSRPN (record type118) or TN_NIRPort (record type 119_20) orTN_NTRPort (record type 119_21).

STARTED_STASK_QFY CHAR(8) Started Task qualifier name, for example TCP/IP.From SMTNSSTN (record type 118) or TI_ASName(record type 119).

TCPIP_HOST_NAME CHAR(8) TCP/IP host name. From SMTNSHNM (record type118) or TN_NTHostNm (record type 119).


TCP_TNSERV_LOGN_HThis table provides hourly statistics for the active logons to each application on aserver for z/OS TCP/IP. Data comes from the TCP_TN3270_SERV_H data table.

The default retention period for this table is 7 days.


DATE K DATE Date when the statistics record was written to SMF.From SMTNSDTE (record type 118) or SMFHDDTE(record type 119).

TIME K TIME Time when the statistics record was written to SMF.From SMTNSTME (record type 118) or SMFHDTME(record type 119).

MVS_SYSTEM_ID K CHAR(4) MVS system ID. This is the SMF system ID. FromSMTNSSID (record type 118) or SMFHDSID (recordtype 119).



SUB_SYSTEM_ID K CHAR(4) Subsystem identifier. This is the value set by theSUBSYS=option specified in the SMF macros. FromSMTNSSSI (record type 118) or SMFHDSSI (recordtype 119).

LOCAL_IP_ADDR K VARCHAR(46) Fullword local IP address. From SMTNSLIP (recordtype 118) or TN_NILIP (record type 119_20) orTN_NTLIP (record type 119_21).

LOCAL_PORT K INTEGER Local port number. From SMTNSLPN (record type118) or TN_NILPort (record type 119_20) orTN_NTLPort (record type 119_21).

LU_NAME K CHAR(8) LU name. From SMTNSLUN (record type 118) orTN_NILU (record type 119_20) or TN_NTLU (recordtype 119_21).

APPLICATION_NAME K CHAR(8) Application name. From SMTNSAPN (record type118) or TN_NIAppl (record type 119_20) orTN_NTAppl (record type 119_21).


ACTIVE FLOAT The difference between the number of logons andlogoffs, hour by hour.

LOGOFF_NUMBER REAL Number of logoff records hour by hour.

LOGON_NUMBER REAL Number of logon records hour by hour.



TCP_UDP_SOCK_CLO_H, _D, _WThis table provides hourly, daily, and weekly TCP/IP statistics about the UDPsockets. Data is based on SMF record type 119 (subtype 10).


TCP_UDP_SOCK_CLO_H7 days

TCP_UDP_SOCK_CLO_D30 days

TCP_UDP_SOCK_CLO_W365 days


DATE K DATE Date when the sockets closed. From UD_UCCDate.

TIME K TIME Time when the sockets closed. From UD_UCCTime.






UDP_SOCK_NAME K CHAR(8) UDP socket resource name (name of the address spacethat opens this socket). From UD_UCRName.

ABNORMAL_CLOSURES FLOAT Number of sockets with abnormal closure. FromUD_UCReason.

INBOUND_BYTES FLOAT Number of inbound bytes. From UD_UCInBytes.

INBOUND_DATAGRAM FLOAT Number of inbound UDP datagrams. FromUD_UCInDgrams.


NORMAL_CLOSURES FLOAT Number of sockets with normal closure. FromUD_UCReason.

OUTBOUND_BYTES FLOAT Number of outbound bytes. From UD_UCOutBytes.

OUTBOUND_DATAGRAM FLOAT Number of outbound UDP datagrams. FromUD_UCOutDgrams.

SOCKETS_EE FLOAT Number of Enterprise Extender sockets closed in theperiod. From UD_UCType.

SOCKETS_STD FLOAT Number of standard sockets closed in the period.From UD_UCType.


TCP_UDPSERV_PORT_H, _D, _WThis table provides hourly, daily, and weekly TCP/IP statistics about the UDPports traffic. Data is based on SMF record type 119 (subtype 7).


TCP_UDPSERV_PORT_H7 days

TCP_UDPSERV_PORT_D30 days

TCP_UDPSERV_PORT_W365 days



TIME K TIME Time when the statistics record was written to SMF.From SMFDHTME.






SERV_SOCK_NAME K CHAR(8) Server socket resource name (specified in the PORTreservation statement). From SP_UDRName.

PORT_NUMBER K INTEGER Port number. From SP_UDPort.

INBOUND_BYTES FLOAT Number of inbound bytes. From SP_UDIBytes.

INBOUND_DATAGRAM FLOAT Number of inbound UDP datagrams to server port.From SP_UDIDgrams.

IP_ADDRESS VARCHAR(46) For bind-specific port reservations: the local IPaddress. From SP_UDBindIP.


OUTBOUND_BYTES FLOAT Number of outbound bytes. From SP_UDOBytes.

OUTBOUND_DATAGRAM FLOAT Number of outbound UDP datagrams to server port.From SP_UDODgrams.


ReportsThis chapter describes the reports provided with the TCP/IP for z/OS component.

TCP/IP FTP Transmission reportThis report shows statistics on the byte count for FTP functions on a server.

This information identifies the report:

Report ID:TCP04

Report group:TCP/IP for z/OS reports

Source:TCP_FTP_SERVER_T

Attributes:TCPIP, FTP, BYTES, TRANSMISSION

Variables:TO_DATE, FROM_DATE, MVS_SYSTEM_ID, SUB_SYSTEM_ID,LOCAL_IP_ADDR, LOCAL_PORT

TCP/IP FTP Transmission reportMVS_SYSTEM_ID:’MVSN’

LIP_ADDR:’9.67.113.63’ LPORT:621

MVS SUB TOTSYSTEM SYSTEM BYTE

DATE TIME ID ID COUNT---------- -------- ------ ------ ----------1999-09-22 11.00.00 MVSN 6.240E+02

Tivoli Decision Support for z/OS Report:TCP04

Figure 21. Example of TCP/IP FTP Transmission report


The report contains this information:

Date Date of the measurement.

Time Time of the measurement.

MVS System IDSystem ID name.

Subsystem IDName of the subsystem.

Tot byte countTotal number of I/O bytes.

TCP/IP ICMP TCPIPSTATISTICS Input reportThis report shows ICMP for input message flow statistics from the general statisticsobtained by specifying the TCPIPSTATISTICS parameter in the SMFCONFIGstatement. The information is displayed hour by hour on a specified day.


Report ID:TCP09


Source:TCP_GEN_ICMP_H

Attributes:TCPIP, TCPIPSTATISTICS, ICMP, INPUT

Variables:DATE, MVS_SYSTEM_ID, SUB_SYSTEMID, TCPIP_PROCNAME



TCPIP ICMP TCPIPSTATISTICS Input ReportMVS system:’SYS1’ Subsystem:’ ’

Procname:’TCPIP1 ’Date: 2002-06-15

In TimeTCPIP In Msg In Dest exceed In Param

Time Procname In Msg Error Unreach Msgs Probl Msgs-------- -------- ---------- ---------- ---------- ---------- ----------10.14.33 TCPIP1 1.200E+01 1.000E+01 2.300E+01 0.000 2.300E+03

In Source In Addr In AddrQuench In Redirec In Echo In Echo Mask Requs Mask Reply

Msgs Msgs Reqs Msgs Reply Msgs Msgs Msgs--------- ---------- ---------- ---------- ---------- ----------1.300E+03 1.500E+03 1.000E+03 5.000E+04 2.300E+03 1.000E+03

Tivoli Decision Support for z/OS Report: TCP09

Figure 22. Example of a TCP/IP ICMP TCPIPSTATISTICS Input report


TCPIP ProcnameThe name of the TCP/IP procedure name.

In MsgThe number of ICMP messages in input. Calculated as the sum ofICMP_INMSGS.

In Msg ErrorThe number of ICMP error messages in input. Calculated as the sum ofICMP_INMSGS_ERRS.

In Dest UnreachThe number of times that a destination unreachable problem occurred inthe input. Calculated as the sum of ICMP_INDEST_UNRCH.

In Time exceed MsgsThe number of times that a time exceeded input message was issued.Calculated as the sum of ICMP_INTM_EXCMSGS.

In Param Probl MsgsThe number of times that an input parameter problem message was issued.Calculated as the sum of ICMP_INPAR_PRBMSGS.

In Source Quench MsgsThe number of times that an input source quench message was issued.Calculated as the sum of ICMP_INSRC_QUENCHS.

In Redirec MsgsThe number of input redirect messages. Calculated as the sum ofICMP_INREDIRECTS.

In Echo Reqs MsgsThe number of input echo request messages. Calculated as the sum ofICMP_INECHOS.

In Echo Reply MsgsThe number of input echo reply messages. Calculated as the sum ofICMP_INECHOS_REPS.

In Addr Mask Requs MsgsThe number of input address mask request messages. Calculated as thesum of ICMP_INADDRMASKS.

In Addr Mask Reply MsgsThe number of input address mask reply messages. Calculated as the sumof ICMP_INADDRMSKREP.

TCP/IP ICMP TCPIPSTATISTICS Output reportThis report shows ICMP for output message flow statistics from the generalstatistics obtained by specifying the TCPIPSTATISTICS parameter in theSMFCONFIG statement. The information is displayed hour by hour on a specifiedday.


Report ID:TCP10


Source:TCP_GEN_ICMP_H


Attributes:TCPIP, TCPIPSTATISTICS, ICMP, OUTPUT

Variables:DATE, MVS_SYSTEM_ID, SUB_SYSTEMID, TCPIP_PROCNAME




Out MsgThe number of ICMP messages in output. Calculated as the sum ofICMP_OUTMSGS.

Out Msg ErrorThe number of ICMP error messages in output. Calculated as the sum ofICMP_OUTMSGS_ERRS.

Out Dest UnreachThe number of times that a destination unreachable problem occurred inthe output. Calculated as the sum of ICMP_OUTDEST_UNRCH.

Out Time exceed MsgsThe number of times that a time exceeded output message was issued.Calculated as the sum of ICMP_OUTTM_EXCMSGS.

Out Param Probl MsgsThe number of times that an output parameter problem message wasissued. Calculated as the sum of ICMP_OUTPAR_PRBMSGS.

Out Source Quench MsgsThe number of times that an output source quench message was issued.Calculated as the sum of ICMP_OUTSRC_QUENCH.

Out Redirec MsgsThe number of output redirect messages. Calculated as the sum ofICMP_OUTREDIRECTS.

TCPIP ICMP TCPIPSTATISTICS Output ReportMVS system:’SYS1’ Subsystem:’ ’

Procname:’TCPIP1 ’Date: 2003-06-15

Out TimeTCPIP Out Msg Out Dest exceed Out Param

Time Procname Out Msg Error Unreach Msgs Probl Msgs-------- -------- ---------- ---------- ---------- ---------- ----------10.14.33 TCPIP1 3.300E+03 0.000 1.400E+03 1.200E+03 1.000E+03

Out Source Out Addr Out AddrQuench Out Redirec Out Echo Out Echo Mask Requs Mask Reply

Msgs Msgs Reqs Msgs Reply Msgs Msgs Msgs---------- ----------- ---------- ---------- ---------- ----------1.600E+03 1.2000E+03 0.000 1.100E+03 8.000E+04 2.000E+04


Figure 23. Example of a TCP/IP ICMP TCPIPSTATISTICS Output report


Out Echo Reqs MsgsThe number of output echo request messages. Calculated as the sum ofICMP_OUTECHOS.

Out Echo Reply MsgsThe number of output echo reply messages. Calculated as the sum ofICMP_OUTECHOS_REPS.

Out Addr Mask Requs MsgsThe number of output address mask request messages. Calculated as thesum of ICMP_OUTADDRMASKS.

Out Addr Mask Reply MsgsThe number of output address mask reply messages. Calculated as the sumof ICMP_OUTADDRMSKREP.

TCP/IP Interface Statistics reportThis report shows the interfaces usage, in terms of bytes and packets transmittedfor a selected day.


Report ID:TCP15


Source:TCP_INTERFACE_H

Attributes:TCPIP, INTERFACE, STATISTICS, TRAFFIC, DAILY

Variables:DATE, SYSPLEX_NAME, MVS_SYSTEM_ID




Interface NameLink or interface name. From INT_NAME.

Interface DescriptionInterface description (TCP/IP PROFILE keyword for LINK or INTERFACEtype). From INT_DESCRIPTION.

TCP/IP Interface Statistics reportSysplex: ’SYSPLEX1’ System: ’MVS1’

DATE:’2004-01-23’

Interface Interface Inbound Outbound Inbound OutboundDate Time Name Description Bytes Bytes Packets Packets---------- -------- ---------- ----------- ---------- ---------- ------- --------2004-01-23 15:00:00 LMBO2CH24 MPCPTP 6.6704E+04 6.0356E+04 4.6600E+02 4.1600E+022004-01-23 15:00:00 LMBO2FR26 MPCPTP 7.4904E+04 7.4948E+04 4.8000E+02 4.7600E+02

Tivoli Decision Support for z/OS report: TCP15

Figure 24. Example of a TCP/IP Interface Statistics report


Inbound BytesNumber of inbound bytes. From INBOUND_BYTES.

Outbound BytesNumber of outbound bytes. From OUTBOUND_BYTES.

Inbound PacketsNumber of inbound packets. From INBOUND_PACKETS.

Outbound PacketsNumber of outbound packets. From OUTBOUND_PACKETS.

TCP/IP IP TCPIPSTATISTICS Error reportThis report shows IP statistics for failing operations from the general statisticsobtained by specifying the TCPIPSTATISTICS parameter in the SMFCONFIGstatement. The information is displayed hour by hour on a specified day.


Report ID:TCP06


Source:TCP_GEN_IP_H

Attributes:TCPIP, TCPIPSTATISTICS, IP, ERROR

Variables:DATE, MVS_SYSTEM_ID, SUB_SYSTEM_ID, SYSPLEX_NAME,TCPIP_PROCNAME




TCPIP IP TCPIPSTATISTICS Error ReportSysplex: ’$UNKNOWN’

MVS system:’ES88’ Subsystem:’ ’Procname:’TCPIP ’Date: 2003-03-08

TCPIP Discarded Sent Reassembly RoutingTime Procname Datagrams discarded failed discards

-------- -------- ---------- ---------- ---------- ----------21.00.00 TCPIP 0 0 0 022.00.00 TCPIP 68 0 0 023.00.00 TCPIP 9 0 0 0

========== ========== ========== ==========77 0 0 0


Figure 25. Example of a TCP/IP IP TCPIPSTATISTICS Error report


Discarded DatagramsThe number of discarded datagrams. Calculated as the sum ofIPTOT_DISC_DATAGR + IPTOP_DISC_ADDR + IPTOT_DISC_UNPR +IPTOT_DISC_OTHER.

Sent discardedThe number of sent discarded. Calculated as the sum ofIPTOT_SENT_DISC + IPTOT_SENT_DISNOR.

Reassembly failedThe number of reassembly failed. Calculated as the sum ofIPTOT_REASS_FAILED.

Routing discardsThe number of routing discards. Calculated as the sum ofIPTOT_ROUT_DISCRDS.

TCP/IP IP TCPIPSTATISTICS hourly reportThis report shows IP statistics from the general statistics obtained by specifying theTCPIPSTATISTICS parameter in the SMFCONFIG statement. The information isdisplayed hour by hour on a specified day.


Report ID:TCP05


Source:TCP_GEN_IP_H

Attributes:TCPIP, TCPIPSTATISTICS, IP

Variables:DATE, MVS_SYSTEM_ID, SUB_SYSTEM_ID, SYSPLEX_NAME



TCPIP IP TCPIPSTATISTICS ReportSysplex: ’$UNKNOWN’

MVS system:’ES88’ Subsystem:’ ’Date: 2003-03-08

AttemptedTCPIP Received Forward Delivered Sent Reassembled Fragments

Time Procname Datagrams Datagrams Datagrams Datagrams Datagrams Generated-------- -------- ---------- ---------- ---------- ---------- ----------- ----------21.00.00 TCPIP 0 0 0 0 0 022.00.00 TCPIP 39857 0 40264 38478 0 023.00.00 TCPIP 3365 0 3455 3148 0 0


Figure 26. Example of a TCP/IP IP TCPIPSTATISTICS hourly report



Received DatagramsThe number of received datagrams. Calculated as the sum ofIPTOT_REC_DATAGR.

Attempted Forward DatagramsThe number of attempts to forward datagrams. Calculated as the sum ofIPTOT_ATT_FWDTGR.

Delivered DatagramsThe number of delivered datagrams. Calculated as the sum ofIPTOT_DELIV_DATA.

Sent DatagramsThe number of sent datagrams. Calculated as the sum ofIPTOT_SENT_DATA.

Reassembled DatagramsThe number of reassembled datagrams. Calculated as the sum ofIPTOT_DATAGR_REASS.

Fragments GeneratedThe number of generated fragments. Calculated as the sum ofIPTOT_FRAGM_GENER.

TCP/IP IP TCPIPSTATISTICS daily reportThis report shows IP statistics from the general statistics obtained by specifying theTCPIPSTATISTICS parameter in the SMFCONFIG statement. The information isdisplayed daily. This information identifies the report:

Report ID:TCP11


Source:TCP_GEN_IP_D

Attributes:TCPIP, TCPIPSTATISTICS, IP

Variables:MVS_SYSTEM_ID, SUB_SYSTEM_ID, SYSPLEX_NAME





Received DatagramsThe number of received datagrams. Calculated as the sum ofIPTOT_REC_DATAGR.

Attempted Forward DatagramsThe number of attempts to forward datagrams. Calculated as the sum ofIPTOT_ATT_FWDTGR.

Delivered DatagramsThe number of delivered datagrams. Calculated as the sum ofIPTOT_DELIV_DATA.

Sent DatagramsThe number of sent datagrams. Calculated as the sum ofIPTOT_SENT_DATA.

Reassembled DatagramsThe number of reassembled datagrams. Calculated as the sum ofIPTOT_DATAGR_REASS.

Fragments GeneratedThe number of generated fragments. Calculated as the sum ofIPTOT_FRAGM_GENER.

TCP/IP TCP TCPIPSTATISTICS reportThis report shows TCP statistics from the general statistics obtained by specifyingthe TCPIPSTATISTICS parameter in the SMFCONFIG statement. The information isdisplayed hour by hour on a specified day.


Report ID:TCP07


Source:TCP_GEN_TCP_H

TCPIP IP TCPIPSTATISTICS ReportSysplex: ’$UNKNOWN’

MVS system:’ES88’ Subsystem:’ ’

AttemptedTCPIP Received Forward Delivered Sent Reassembled Fragments

Date Procname Datagrams Datagrams Datagrams Datagrams Datagrams Generated-------- -------- ---------- ---------- ---------- ---------- ---------- ----------2000-09-08 TCPIP 2733 0 2785 2696 0 02000-09-09 TCPIP 893378 0 906493 763674 0 0


Figure 27. Example of a TCP/IP TCPIPSTATISTICS Daily report


Attributes:TCPIP, TCPIPSTATISTICS, TCP

Variables:DATE, MVS_SYSTEM_ID, SUB_SYSTEM_ID, TCPIP_PROCNAME




Retransmit algorithmThe number of retransmit algorithms. Calculated as the sum ofTCP_RETR_ALG.

Active OpensThe number of active opens. Calculated as the sum ofTCP_ACTIVE_OPENS.

Passive OpensThe number of passive opens. Calculated as the sum ofTCP_PASSIVE_OPENS.

Open failuresThe number of open failures. Calculated as the sum of TCP_OPEN_FAILS.

Resets The number of resets. Calculated as the sum of TCP_EST_RESET_NUM.

Input errorsThe number of input errors. Calculated as the sum of TCP_INPUT_ERR.

Out ResetsThe number of output resets. Calculated as the sum ofTCP_OUT_RESET_NUM.

TCP/IP TCP Connection Performance reportThis report shows the performance of the connections statistics for a selected serverand port number.


Report ID:TCP13

TCPIP TCP TCPIPSTATISTICS ReportMVS system:’ES88’ Subsystem:’ ’

Procname:’TCPIP ’Date: 2000-03-08

TCPIP Retransmit Active Passive Open Input OutTime Procname algorithm Opens Opens failures Resets Errors Resets

-------- -------- ---------- ---------- ---------- ---------- ---------- ---------- ----------21.00.00 TCPIP 12 0 0 0 0 0 022.00.00 TCPIP 36 53 53 14 20 0 2023.00.00 TCPIP 12 25 25 0 8 0 8


Figure 28. Example of a TCP/IP TCP TCPIPSTATISTICS report



Source:TCP_SERVER_CONN_H

Attributes:TCPIP, CONNECTIONS, SERVER, PORT, PERFORMANCE,THROUGHPUT, WORKLOAD

Variables:FROM_DATE, TO_DATE, SYSPLEX_NAME, MVS_SYSTEM_ID,LOCAL_IP_ADDR, LOCAL_PORT




Number of ConnectionsTotal number of connections in the interval. From CONNECTIONS.

Average Connection DurationAverage duration time of connections. From CONN_DURATION_AVG.



RetransmissionsNumber of times that a retransmission was required. FromRETRANSMISSION.

TCP/IP TCP Server Port Connection Statistics reportThis report shows statistics on the byte count for FTP functions on a server.


Report ID:TCP12


Source:TCP_TCPSERV_PORT_H

TCP/IP TCP Connection Performance reportSysplex: ’PLEX1’ System: ’RUS’

IP Address: All Port: AllDate:’2004-05-05’ to ’2004-05-05’

AverageConnection Inbound Outbound

Date Time Connections Duration Bytes Bytes Retransmissions---------- ----- ----------- ----------- ------- ------- ---------------2004-05-05 02.00.00 2.0000E+00 1.7740E+03 1.4564E+04 2.2683E+05 0.00000000E+00


Figure 29. Example of a TCP/IP TCP Connection Performance report


Attributes:TCPIP, CONNECTIONS, SERVER, PORT

Variables:FROM_DATE, TO_DATE, SYSPLEX_NAME, MVS_SYSTEM_ID,SERV_SOCK_NAME, PORT_NUMBER




Rejected ConnectionsTotal number of TCP connections rejected. FromCONN_REJECT_BUSY+CONN_REJECT_ATTACK.

Accepted ConnectionsNumber of TCP connections accepted. From CONNECTIONS.

Max Active ConnectionsMaximum number of active TCP connections during the period. FromMAX_CONNECTIONS.

TCP/IP TELNET Server Active Logon by Hour reportThis report shows how many logons made to an application on a server are activehour by hour on a specified day.


Report ID:TCP01


Source:TCP_TNSERV_LOGN_H

Attributes:TCPIP, TN3270, SERVER, LOGON, APPLICATION

Variables:DATE, MVS_SYSTEM_ID, SUB_SYSTEM_ID, LOCAL_IP_ADDR,LOCAL_PORT, LU_NAME, APPL_NAME

TCP/IP TCP Server Port Connection Statistics reportSysplex: ’PLEX1’ System: ’RUS’

Server: All Port: AllDATE:’2004-05-07’ to ’2004-05-07’

Date Time Rejected Accepted Max ActiveConnections Connections Connections

---------- -------- ----------- ----------- -------------2004-05-07 02.00.00 0.0000E+00 4.4000E+02 2.4000E+01


Figure 30. Example of a TCP/IP TCP Server Port Connection Statistics report



Time Time of the measurement

Date Date of the measurement

MVS System IDSystem ID name

LU nameName of the LU

Application NameName of the application

Sum activeNumber of active logons to an application hour by hour on the specifiedday

TCP/IP TELNET Server Bytes Traffic reportThis report shows the traffic of bytes (bytes in and bytes out) caused by anapplication on a server in a date interval.


Report ID:TCP02


Source:TCP_TN3270_SERV_T

Attributes:TCPIP, TN3270, SERVER, BYTES, APPLICATION

Variables:FROM_DATE, TO_DATE, MVS_SYSTEM_ID, SUB_SYSTEM_ID,LOCAL_IP_ADDR, LOCAL_PORT, LU_NAME, APPL_NAME

TCPIP TELNET Server Active logon by hour ReportSYSTEM_ID:’8609’ LU:’M0100 ’

IP_ADDR:’9.67.17.83 ’ PORT:LOCAL_PORT’ECHOA01 ’

MVSSYSTEM LU APPLICATION SUM

TIME DATE ID NAME NAME ACTIVE-------- ---------- ------ -------- ----------- ----------16.00.00 1999-10-29 8609 M0100 ECHOA01 0.000E+00

IMS Performance feature Report: TCP01

Figure 31. Example of TCP/IP TELNET Server Active Logon by Hour report




Time Time of the measurement


Subsystem_IDName of the subsystem



Tot Bytes InNumber of input bytes

Tot Bytes OutNumber of output bytes

TCP/IP TELNET AVG Connection Time to Application reportThis report shows TCP/IP TELNET average connection time to an application


Report ID:TCP03


Source:TCP_TN3270_SERV_H

Attributes:TCPIP, CONNECTION, TIME, APPLICATION

Variables:TO_DATE, FROM_DATE, MVS_SYSTEM_ID, SUB_SYSTEM_ID,LOCAL_IP_ADDR, LOCAL_PORT, LU_NAME, APPL_NAME

TCPIP TELNET Server Bytes traffic ReportMVS_SYSTEM_ID:’8609’

LU:’M0100 ’ APPL:’ECHOA01 ’

MVS SUB TOT TOTSYSTEM SYSTEM LU APPLICATION BYTES BYTES

DATE TIME ID ID NAME NAME IN OUT---------- -------- ------ ------ -------- ----------- --------- ----------1999-10-29 16.00.00 8609 M0100 ECHOA01 7.770E+0 6.063E+03

Tivoli Decision Support for z/OS Report:TCP02

Figure 32. Example of TCP/IP TELNET server bytes traffic report





SubSystem IDName of the subsystem



Average Logon TimeAverage time an application was logged on to the specific application.

TCP/IP UDP Sockets Traffic, Daily reportThis report shows the traffic of UDP sockets in a selected day.


Report ID:TCP14


Source:TCP_UDP_SOCK_CLO_D

Attributes:TCPIP, SOCKETS, UDP, TRAFFIC, DAILY

Variables:DATE, SYSPLEX_NAME, MVS_SYSTEM_ID

TCP/IP TELNET AVG Connection Time to ApplicationSYSTEM_ID:’8609’ LU:’M0100 ’

IP_ADDR:’9.67.17.83 ’ PORT:623’ECHOA01 ’

MVS SUB AVERAGESYSTEM SYSTEM LU APPLICATION LOGON

DATE ID ID NAME NAME TIME---------- ------ ------ -------- ----------- ----------1999-10-29 8609 M0100 ECHOA01 6.456E+03


Figure 33. Example of TCP/IP TELNET AVG Connection Time to Application report




UDP Sock NameName of the UDP socket resource (name of the address space that opensthis socket). From UDP_SOCK_NAME.

Sockets StdThe number of standard sockets that were closed during the day. FromSOCKETS_STD.

Sockets EEThe number of Enterprise Extender sockets that were closed during theday. From SOCKETS_EE.



Inbound DatagramsNumber of inbound UDP datagrams. From INBOUND_DATAGRAM.

Outbound DatagramsNumber of outbound UDP datagrams. From OUTBOUND_DATAGRAM.

TCP/IP UDP TCPIPSTATISTICS reportThis report shows UDP statistics from the general statistics obtained by specifyingthe TCPIPSTATISTICS parameter in the SMFCONFIG statement. The information isdisplayed hour by hour on a specified day.


Report ID:TCP08


Source:TCP_GEN_UDP_H

Attributes:TCPIP, TCPIPSTATISTICS, UDP

Variables:DATE, MVS_SYSTEM_ID, SUB_SYSTEM_ID, TCPIP_PROCNAME

TCP/IP UDP Sockets Traffic, Daily Overview reportSysplex: ’PLEX1’ System: ’MVS1’

DATE:’All’

UDP Sock Sockets Sockets Inbound Outbound Inbound OutboundDate Name Std EE Bytes Bytes Datagrams Datagrams----------- --------- ---------- ---------- ---------- ---------- --------- ---------2004-05-05 FTPMVS6 4.7000E+02 0.0000E+00 2.4800E+02 5.1000E+01 1.0000E+00 1.0000E+002004-05-06 POLV3 1.2000E+01 0.0000E+00 1.0440E+03 4.0800E+02 8.0000E+00 8.0000E+00


Figure 34. Example of a TCP/IP UDP Sockets Traffic, Daily report





Received DatagramsThe number of received UDP datagrams. Calculated as the sum ofUDP_RECV_DATAGR.

Datagrams with no portsThe number of UDP datagrams with no port. Calculated as the sum ofUDP_DATAGR_NOPORT.

Other Datagrams not recvThe number of other UDP datagrams not received. Calculated as the sumof UDP_DATAGR_NOTREC.

Datagrams sentThe number of sent datagrams. Calculated as the sum ofUDP_DATAGR_SENT.

HTTP Server for z/OS (ICSS) componentCustomization

Data flow


Data tablesv INTCON_CONFv INTCON_PERF_H, _D, _M

Reportsv ICSS configuration reportv ICSS performance reports

– ICSS performance hourly report– ICSS performance daily report– ICSS performance monthly report

TCPIP UDP TCPIPSTATISTICS ReportMVS system:’ES88’ Subsystem:’ ’;

Procname:’TCPIP ’Date: 2000-03-08

Datagrams OtherTCPIP Received with Datagrams Datagrams

Time Procname Datagrams no ports not recv sent-------- -------- ---------- ---------- ---------- ----------21.00.00 TCPIP 0 0 0 022.00.00 TCPIP 30313 783 1388 3584423.00.00 TCPIP 1719 153 80 2435


Figure 35. Example of a TCP/IP UDP TCPIPSTATISTICS report


CustomizationHTTP Server for z/OS uses SMF logging of configuration and performanceinformation.

Configuration information is collected whenever the server is started, providedthat SMF is set up correctly and the server has been enabled for SMF logging. Thisconfiguration information is saved as SMF record 103, subtype 01.

Performance data is collected periodically according to the SMF interval, providedthat SMF is set up correctly and the server has been enabled for SMF logging. Thisperformance information is saved as SMF record 103, subtype 02.

For details about how to configure HTTP Server for z/OS, refer to the HTTP Serverfor z/OS Planning, Installing, and Using manual.

Data flowThe HTTP Server for z/OS (ICSS) component collects records from the SMF dataset and stores extracted and summarized data in the Tivoli Decision Support forz/OS database. The reporting function extracts data from the database and createsthe reports that you request through the reporting dialogs. The following datashows an overview of the flow of data through the HTTP Server for z/OS (ICSS)component.


Figure 36. HTTP Server for z/OS (ICSS) component data flow


Log and record definitionsThe HTTP Server for z/OS (ICSS) component collects records from the systemmanagement facilities (SMF) log. The HTTP Server for z/OS application writesrecords related to the server configuration and performance.

The HTTP Server for z/OS (ICSS) component collects the following records fromthe SMF log:

Table 1. Table 1. SMF log records collected by HTTP Server for z/OS (ICSS)

SMF record type Subtype

Tivoli DecisionSupport forz/OS recorddefinition Description

103 1 INT_103_1 HTTP Server for z/OS configuration data

103 2 INT_103_2 HTTP Server for z/OS configuration data

For a detailed description of these records, see the HTTP Server for z/OS Planning,Installing, and Using manual.

Data tablesThis section describes the modified Table objects for the HTTP Server for z/OS(ICSS) component.

INTCON_CONFThe following table provides configuration information for ICSS. The source file isin the member DRLTINTE, which is contained in the data set DRLxxx.SDRLDEFS.

The default retention period for INTCON_CONF is 765 days.

Table 2. ICSS table definition for INTCON_CONF

Column Data type Description

DTE K DATE Date when the record was written

TME K TIME Time when the record was written

SYSTEM_ID K CHAR(4) System identifier. From SMF103SID

ENTITY_NAME K CHAR(32) Host name for the server

ENTITY_ADDR K CHAR(16) IP address for the server

ENTITY_PORT K INTEGER Port number being used

SERVER_TYPE INTEGER Server type. It can be 0, 1, and 2 (uninitialized,standalone, and inetd server)

APPL_VERSION CHAR(8) Version of server

SERVER_ROOT CHAR(32) Directory for server_root

DO_DNS_LKUP INTEGER Value of the DNS-lookup directive (0 if off, 1 if on).

MAX_CONT_BUF FLOAT Maxsize setting of the content buffer, in bytes

THREADS_MIN FLOAT Minimum number of threads that the server can have

THREADS_MAX FLOAT Value of the MaxActiveThreads directive

IDLE_THREAD_TO INTEGER Timeout for idle threads

ACL_SETTINGS INTEGER ACL settings, values can be 0, 1, and 2 (always,protect only, and never)


Table 2. ICSS table definition for INTCON_CONF (continued)


USE_META_FILES INTEGER Settings use for meta files directive (0 is off, 1 is on).

DIR_ACCESS INTEGER Directory access flag.

INPUT_TO INTEGER Value of input timeout directive.

OUTPUT_TO INTEGER Value of output timeout directive.

SCRIPT_TO INTEGER Value of script timeout directive.

USE_GMT INTEGER Setting of the LogTime directive (0 if Localtime and 1if GMT).

SERVER_IMBEDS_HTML INTEGER Settings of Imbeds directive (0 if off, 1 if on).

SECURE_TYPE INTEGER Secure type settings. Values can be 1 or 2 (1 if SSLmode is on, 2 if SSL mode is off).

SSL_PORT INTEGER Security (SSL) port.

NORMAL_MODE INTEGER Normal mode flag.

CACHE_OFF INTEGER Setting of the Caching directive. Values can be 1 or 2(1 if off, 0 if on).

CACHE_MAX_K FLOAT Value max k cache.

CACHE_MAX_F FLOAT Value max file to cache.

CACHE_LIMIT_1 FLOAT Value of cache limit 1.

CACHE_LIMIT_2 FLOAT Value of cache limit 2.

CACHE_TIME_MARGIN INTEGER Value of cache time margin

CACHE_LOCK_TIMEOUT INTEGER Value of cache lock timeout.

KEEP_EXP INTEGER Settings of expired cache settings. Values can be 0 or 1(0 if data is deleted, 1 if data is kept).

CACHE_NO_CONNECT INTEGER Cache connect flag.

GC_DISABLED INTEGER Settings of GC directive. Values can be 0 or 1 (0 ifgarbage collection is on, 1 if off).

GC_DAILY_GC INTEGER Value of garbage collection interval.

GC_MEM_USAGE FLOAT Garbage collection memory use.

PROXY_FLAG INTEGER Proxy flag.

INTCON_PERF_H, _D, _MThese tables provide hourly, daily, and monthly performance statistics on ICSSdata. The source file is in the member DRLTINTE, which is contained in the dataset DRLxxx.SDRLDEFS.

The default retention periods are:v 7 days for INTCON_PERF_H

v 30 days for INTCON_PERF_D

v 765 days for INTCON_PERF_M

The data stored in INTCON_PERF_H are cumulative values, whereas the datastored in INTCON_PERF_D and in INTCON_PERF_M are real values.


Table 3. ICSS table definition for INTCON_PERF_H, _D, _M


DTE K DATE Date when the record was written.

The date in the hourly and daily table, first day of thecorresponding month for monthly table.

TME K TIME Time when the record was written.

Not available in the daily and monthly tables.

SYSTEM_ID K CHAR(4) System identifier. From SMF103SID.

ENTITY_NAME K CHAR(32) Host name for the server.

ENTITY_ADDR K CHAR(16) IP address for the server.

ENTITY_PORT K INTEGER Port number being used.

TOTCUR_THREADS INTEGER Number of threads currently used.

TOTCUR_THREADS FLOAT Number of threads currently used

MAX_THREAD FLOAT Max number threads defined.

REQUEST_NUM FLOAT Number of requests received.

REQUEST_ERR FLOAT Number of request errors received

REQUEST_DISC FLOAT Number of requests discarded.

RESPONSES_NUM FLOAT Number of responses sent.

RESPONSES_DISC FLOAT Number of responses discarded.

IN_BYTES FLOAT Number of bytes received.

OUT_BYTES FLOAT Number of bytes sent.

IN_UNKNOWNS_BYTES FLOAT Number of bytes received that were of a typeunknown to the server.

TOTAL_TIMEOUTS FLOAT Number of timeouts since startup

PRXY_CACHE_READ REAL Total number of bytes read from the proxy cache.

PRXY_CACHE_HITS REAL Number of proxy cache hits.

PRXY_CACHE_RAM_USE REAL Number of bytes of proxy cache RAM in use, itrepresents the size of the proxy cache currently in use.

PRXY_CACHE_FILES REAL Number of proxy cached files, it represents thenumber of files currently in the proxy cache.

REQUESTS_GET REAL Number of GET requests.

REQUESTS_HEAD REAL Number of HEAD requests.

REQUESTS_POST REAL Number of POST requests.

REQUESTS_CGI REAL Number of CGI requests.

REQUESTS_CWAPI REAL Number of CWAPI requests.

ERRORS_LEVEL_2XX REAL Number of Error Level 200 (Error 200-299) responses.




ERRORS_TYPE_200 REAL Number of Error 200 responses.




Table 3. ICSS table definition for INTCON_PERF_H, _D, _M (continued)






MEASURESD_SEC REAL Measured interval i seconds.

NUM_CONNECTIONS REAL Number of connections.

RSP_SEC_DSNLKP_MAX FLOAT Maximum DNS lookup response time in seconds, itrepresents the longest response time since Web serverstartup.

RSP_SEC_DSNLKP_MIN FLOAT Minimum DNS lookup response time in seconds, itrepresents the shortest response time since Web serverstart up.

RSP_SEC_DSNLKP_AVG FLOAT Average DNS lookup response time in seconds, itrepresents the average response time since Web serverstartup.

RSP_SEC_SRVCPI_MAX FLOAT Maximum service plugins response time in seconds, itrepresents the longest response time since Web serverstartup.

RSP_SEC_SRVCPI_MIN FLOAT Minimum service plugins response time in seconds, itrepresents the shortest response time since Web serverstartup.

RSP_SEC_SRVCPI_AVG FLOAT Average service plugins response time in seconds, itrepresents the average response time since Web serverstartup.

RSP_SEC_CGI_MAX FLOAT Maximum CGI response time in seconds, it representsthe longest response time since Web server startup.

RSP_SEC_CGI_MIN FLOAT Minimum CGI response time in seconds, it representsthe shortest response time since Web server startup.

RSP_SEC_CGI_AVG FLOAT Average CGI response time in seconds, it representsthe average response time since Web server startup.

RSP_SEC_SSLHS_MAX FLOAT Maximum SSL handshake response time in seconds, itrepresents the longest response time since Web serverstartup.

RSP_SEC_SSLHS_MIN FLOAT Minimum SSL handshake response time in seconds, itrepresents the shortest response time since Web serverstartup.

RSP_SEC_SSLHS_AVG FLOAT Average SSL handshake response time in seconds, itrepresents the average response time since Web serverstartup.

RSP_SEC_PROXY_MAX FLOAT Maximum proxy response time in seconds, itrepresents the longest response time since Web serverstartup.

RSP_SEC_PROXY_MIN FLOAT Minimum proxy response time in seconds, itrepresents the shortest response time since Web serverstartup.

RSP_SEC_PROXY_AVG FLOAT Average proxy response time in seconds, it representsthe average response time since Web server startup.


Table 3. ICSS table definition for INTCON_PERF_H, _D, _M (continued)


JOB_NAME CHAR (8) z/OS job name, the job name may change if the Webserver is restarted.

ReportsThe HTTP Server for z/OS (ICSS) component provides the following reports:v Configuration report:

– ICSS configuration report (INTE01)v Performance reports:

– ICSS performance hourly report (INTE02)– ICSS performance daily report (INTE03)– ICSS performance monthly report (INTE04)

ICSS configuration reportThe following information identifies the report:

Report IDINTE01

Report groupHTTP Server for z/OS (ICSS) configuration reports

SourceINTCON_CONF

AttributesINTERNET, SERVER, OVERVIEW, CONFIGURATION

VariablesDATE, HOST_NAME

ICSS performance reportsThis section describes ICSS performance reports.

ICSS performance hourly report:ICSS performance hourly report


Internet Conn. Secure Server config.

USE VALUE VALUE VALUEMETA DIRECTORY OF OF OF SECURE

ACL FILES ACCESS INPUT OUTPUT SCRIPT LOGTIME IMBEDS TYPESETTINGS SETTINGS FLAG TIMEOUT TIMEOUT TIMEOUT SETTINGS SETTINGS SETTINGS

----------- ----------- ----------- ----------- ----------- ----------- ----------- -------- ---------2 0 0 330 3600 0 0 0 22 0 0 330 3600 0 0 0 2

Report:INTE01

Figure 37. Example of an HTTP Server for z/OS (ICSS) configuration report (partial view)


Report IDINTE02

Report groupHTTP Server for z/OS (ICSS) performance reports

SourceINTCON_PERF_H

AttributesINTERNET, SERVER, OVERVIEW, PERFORMANCE

VariablesDATE, HOST_NAME

ICSS performance daily report:ICSS performance daily report


Report IDINTE03


SourceINTCON_PERF_D


VariablesFROM_DATE, TO_DATE, HOST_NAME

Internet Conn. Secure Server perfor. hourly Report

NUMBER OFTHREADS MAX NUMBER NUMBER OF NUMBER OF NUMBER OF

PORT CURRENTLY OF THREADS REQUESTS REQUESTS REQUESTSNUMBER USED DEFINED RECEIVED IN ERROR DISCARDED------ ----------- ----------- ----------- ----------- -----------

80 0 40 501 6 668000 0 40 0 1 17

80 1 40 502 6 6680 0 40 506 6 6780 0 40 531 6 6780 4 40 538 6 67

8000 0 40 0 1 1980 0 40 1740 22 22180 0 40 1559 28 16780 0 40 2424 42 26480 2 40 841 14 9780 4 40 1715 28 20880 5 40 1761 28 23080 1 40 1783 28 24480 0 40 913 14 12480 0 40 951 14 128

Tivoli Decision Support for z/OS Report:INTE02

Figure 38. Example of an HTTP Server for z/OS (ICSS) performance hourly report (partial view)


ICSS performance monthly report:ICSS performance monthly report


Report IDINTE04


SourceINTCON_PERF_M


VariablesFROM_DATE, TO_DATE, HOST_NAME

Internet Conn. Secure Server perfor. daily Report


PORT CURRENTLY OF THREADS REQUESTS REQUESTS REQUESTSNUMBER USED DEFINED RECEIVED IN ERROR DISCARDED

-------- ----------- ----------- ----------- ----------- ----------80 4 40 467 5 90

8000 0 40 0 1 1080 6 40 7154 75 1033

8000 0 40 0 2 2980 5 40 16265 248 2016

8000 0 40 0 2 368000 0 40 0 3 68

80 5 40 29308 484 468180 4 40 10829 182 2086

8000 0 40 0 1 30


Figure 39. Example of an HTTP Server for z/OS (ICSS) performance daily report (partial view)

Internet Conn. Secure Server perf. monthly Report


PORT CURRENTLY OF THREADS REQUESTS REQUESTS REQUESTSNUMBER USED DEFINED RECEIVED IN ERROR DISCARDED

-------- ----------- ----------- ----------- ----------- ----------80 6 40 64023 994 9906

8000 0 40 0 9 173


Figure 40. Example of an HTTP Server for z/OS (ICSS) performance monthly report (partial view)


EREP componentCustomizationv Making input data availablev Modifying DRLJCOLLv Updating lookup tables

Data flowv Storing the data


Data tables and lookup tablesv Data tables

– EREP_DASD_D, _M– EREP_IPL_T– EREP_VTAM_D, _M

v Lookup tables– EREP_CPU_ID– EREP_DASD_GROUP

Reportsv DASD errors summary reports

– EREP DASD Errors by Device Type, Monthly Trend report– EREP DASD Errors by DASD Group, Monthly Trend report– EREP DASD Errors by Control Unit, Monthly Trend report

v VTAM-controlled device errors summary reports– EREP VTAM Errors by Resource, Monthly Trend report

v IPL system initialization statistics– EREP IPL and Downtime Summary, Daily report

CustomizationBefore you can use the EREP component to collect data and create reports, youmust customize and test the installation. This chapter describes the steps you mustperform to customize the EREP component:1. Making input data available.2. Modifying DRLJCOLL.3. Updating lookup tables.

Making input data availableThe EREP component collects these records from the EREP history file:v Long OBR record (unit check); type = X'30'v Long VTAM® OBR record; type = X'36'v System initialization (IPL) record; type = X'50'

Ensure that EREP generates these records.

The EREP component accepts data from history files generated on either z/OS orz/VM systems. The z/OS EREP history file can be from a single system, or it can


be a sysplex-wide EREP history file generated using the z/OS System Logger. Nochanges are required to Tivoli Decision Support for z/OS to process sysplex-wideEREP history files.

To process EREP history files generated on a z/VM system, you must transfer thefile to the z/OS system on which you are running Tivoli Decision Support forz/OS.

Modifying DRLJCOLLBefore running the Tivoli Decision Support for z/OS collect job, you must updatethe DRLJCOLL member, as described in "Setting up the collect job" in the SystemPerformance Feature Reference Volume I.

Updating lookup tablesThe EREP component uses two lookup tables when updating tables in thedatabase. Using the administration dialog, update these tables with the values tobe used in your installation:

Table name Description Key columns Data columns

EREP_CPU_ID Converts the serial numbers ofprocessors in a multiprocessingenvironment to a system ID.

CPU_SERIAL_NO SYSTEM_ID

EREP_DASD_GROUP Converts processor serial numbersand device addresses to strings andgroups of DASD devices.

CPU_SERIAL_NODEVICE_ADDRESS

DASD_GROUPDASD_STRING

For a complete description of the lookup tables and examples of the table contents,see EREP_CPU_ID and EREP_DASD_GROUP.

For information on using the administration dialog to update lookup tables, referto the System Performance Feature Reference Volume I.

Data flowThe EREP component collects records from the EREP history files created on MVSand VM systems, and stores the data in the Tivoli Decision Support for z/OSdatabase. You can then use the reporting dialog to create reports based on thisdata. The following figure shows an overview of the flow of data through theEREP component.


Figure 41. EREP component data flow


Storing the dataAfter collecting the data, the EREP component stores the data in data tables in theTivoli Decision Support for z/OS database. As it updates the tables, the EREPcomponent uses lookup tables to convert CPU serial numbers to CPU IDs, and toconvert CPU serial numbers and device addresses to group and string names. Thefollowing figure shows which data tables contain values from the lookup tables.

For more information about the data tables the component updates and the lookuptables it uses, see Data tables and lookup tables.

The EREP component also uses the MVSPM_UNIT_TYPE lookup table from thez/OS Performance Management (MVSPM) component to convert z/OS unit codesto a device class and unit type. The EREP_DASD_x and EREP_VTAM_x tables usedata from this lookup table. For a description of this lookup table, see“MVS_UNIT_TYPE” in the System Performance Feature Reference Volume I.

Log and record definitionsEach operating system includes error recovery procedures that write records ontothe system error recording data set (ERDS). In z/OS, the ERDS is theSYS1.LOGREC data set. In z/VM, it is not a data set but the error recording area.You can request that EREP write these records to a history file as it processes them.The EREP component of the System Performance feature collects these recordsfrom the EREP history file. The component processes these records:

Table 4. Input records to the EREP component

EREP record Record definition Description

Long OBR (unit check) type = X'30' EREP_30 Documents a variety of I/Oerrors and statistical data. Itcontains data on permanentunit checks. It is also writtenwhen the dynamic pathingavailability facility encountersan error while changing thestate of a path group.

Long VTAM OBR type = X'36' EREP_36 Describes a permanent ortemporary device failure (unitcheck) on a device supportedby VTAM, if the device ischannel-attached.

Figure 42. EREP lookup table data


Table 4. Input records to the EREP component (continued)

EREP record Record definition Description

System initialization type = X'50' EREP_50 Documents the IPLs that occuron the system. This record isalso generated to provideinformation about power linedisturbances that cause systemtermination.

For complete details on these records, see the EREP User’s Guide and Reference.

Data tables and lookup tablesThis chapter describes the data tables and lookup tables used by the EREPcomponent. For descriptions of common data tables, lookup tables, and controltables used by the System Performance feature, see the Administration Guide andReference.

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

EREP_DASD_D, _M:EREP_DASD_D, _M

These tables provide daily and monthly statistics on DASD errors. They containdata from the EREP history file OBR (EREP type X'30') records.

These tables are updated by the EREP_CPU_ID, EREP_DASD_GROUP, andMVSPM_UNIT_TYPE lookup tables.


EREP_DASD_D30 days

EREP_DASD_M765 days

Note: In the column descriptions, the source fields that do not begin with OBR aredocumented only in the record definitions for these tables.


DATE K DATE Date when the errors occurred. For the _M table, thisis the date of the first day of the month. FromOBRDATE.

SYSTEM_ID K CHAR(8) System ID associated with the processor serialnumber. From SYSTEM_ID in the EREP_CPU_IDlookup table.

DASD_GROUP K CHAR(8) Name of the DASD group. From DASD_GROUP inthe EREP_DASD_GROUP lookup table.

DASD_STRING K CHAR(8) Name of the DASD string. From DASD_STRING inthe EREP_DASD_GROUP lookup table.

CONTROL_UNIT_TYPE K CHAR(4) Control unit type code. From CUTYPE if bit 0 in thefirst byte of CUTYPE is 1; otherwise, this is blank.



DEVICE_TYPE K CHAR(8) Device type. From UNIT_TYPE in theMVSPM_UNIT_TYPE lookup table.

VOLSER K CHAR(6) Volume serial number. From VOLSER.

CONTROL_UNIT_ID K CHAR(2) Subsystem ID or control unit ID. From SSID.

BUS_OUT_ERRORS INTEGER Number of channel bus out parity errors thatoccurred. This is the count of records where bit 2 ofSENSE0 is 1.

CORRECTABLE_ERRORS INTEGER Number of correctable errors that occurred. This is thecount of records where bit 1 of SENSE2 is 1.

INVAL_TRACK_FORMAT INTEGER Number of times invalid track format occurred. Thisis the count of records where bit 1 of SENSE1 is 1.

IO_RETRIES INTEGER Number of I/O retries attempted for the errors thatoccurred. This is the sum of OBRRETRY.

OVERRUNS INTEGER Number of overruns that occurred. This is the countof records where bit 5 of SENSE0 is 1.

PERM_DATA_CHECKS INTEGER Number of permanent data checks that occurred. Thisis the count of records where bit 1 of OBRSW2 is 0and bit 4 of SENSE0 is 1.

PERM_EQUIP_CHECKS INTEGER Number of permanent equipment checks thatoccurred. This is the count of records where bit 1 ofOBRSW2 is 0 and bit 3 of SENSE0 is 1.

TEMP_DATA_CHECKS INTEGER Number of temporary data checks that occurred. Thisis the count of records where bit 1 of OBRSW2 is 1and bit 4 of SENSE0 is 1.

TEMP_EQUIP_CHECKS INTEGER Number of temporary equipment checks thatoccurred. This is the count of records where bit 1 ofOBRSW2 is 1 and bit 3 of SENSE0 is 1.

UNCORR_ERRORS INTEGER Number of uncorrectable errors that occurred. This isthe count of records where bit 1 of SENSE2 is 0.

EREP_IPL_T:EREP_IPL_T

This table provides detailed statistics on IPLs. It contains data from the EREPhistory file IPL (EREP type X'50') records.

This table is updated by the EREP_CPU_ID lookup table.



CPU_SERIAL_NO CHAR(6) Processor serial number. FromIPLSER.

DATE DATE Date when the IPL occurred.From IPLDATE.

DOWN_DATE DATE System down date. This is thedate of the latest activity onthe system before the IPLoccurred. From IPLSDATE.



DOWN_TIME TIME System down time. This is thetime of the latest activity onthe system before the IPLoccurred. From IPLSTIME.

IPL_REASON CHAR(2) Code representing the reasoncode for the IPL. FromIPLREAS.

RELEASE CHAR(1) Release level of the operatingsystem. From the last 4 bits ofIPLKEY2.

SYSTEM CHAR(3) Operating system. From thefirst 3 bits of IPLKEY2.

SYSTEM_ID CHAR(8) System ID associated with theprocessor serial number. FromSYSTEM_ID in theEREP_CPU_ID lookup table.

TIME TIME Time when the IPL occurred.From IPLTIME.

EREP_VTAM_D, _M:EREP_VTAM_D, _M

These tables provide daily and monthly statistics on VTAM errors. They containdata from the EREP history file VTAM long OBR (EREP type X'36') records.

These tables are updated by the EREP_CPU_ID and MVSPM_UNIT_TYPE lookuptables.


EREP_VTAM_D30 days

EREP_VTAM_M765 days

Note: In the column descriptions, the source fields that do not begin with OBR aredocumented only in the record definitions for these tables.


DATE K DATE Date when the errors occurred. For the _M table, thisis the date of the first day of the month. FromOBRDATE.

SYSTEM_ID K CHAR(8) System ID associated with the processor serialnumber. From SYSTEM_ID in the EREP_CPU_IDlookup table.

DEVICE_TYPE K CHAR(4) Device type. From UNIT_TYPE in theMVSPM_UNIT_TYPE lookup table.

DEVICE_ADDRESS K CHAR(4) Device address or device number. From OBRPCUA2.

RESOURCE_NAME K CHAR(8) VTAM resource name. From RESOURCE.



EOD_OVERFLOW_COUNT INTEGER Number of end-of-day or overflow records. This is thecount of records where bit 1 of OBRSW2 is 1 andINSENSE is 1.

IO_RETRIES INTEGER Number of I/O retries attempted for the errors thatoccurred. This is the sum of OBRRETRY.

PERMANENT_ERRORS INTEGER Number of permanent errors that occurred. This is thecount of records where bit 1 of OBRSW2 is 0.

START_IO_COUNT INTEGER Number of start I/O instructions. This is the sum ofSIOCNTR.

TEMPORARY_ERRORS INTEGER Number of temporary errors that occurred. This is thecount of records where bit 1 of OBRSW2 is 1 andINSENSE is not 0.

Lookup tablesThis section describes the lookup tables specific to the EREP component.

EREP_CPU_ID:EREP_CPU_ID

This lookup table converts the serial numbers of processors in a multiprocessingenvironment to a system ID.


CPU_SERIAL_NO K CHAR(6) Serial number of the processor. This cancontain global search characters.

SYSTEM_ID CHAR(8) System ID to be associated to theprocessor serial number.

Example of table contents

CPUSERIAL SYSTEM

NO ID------ --------%12906 SYS1%22906 SYS2•••

EREP_CPU_ID:EREP_CPU_ID

This lookup table converts the serial numbers of processors in a multiprocessingenvironment to a system ID.


CPU_SERIAL_NO K CHAR(6) Serial number of the processor. This cancontain global search characters.

SYSTEM_ID CHAR(8) System ID to be associated to theprocessor serial number.



CPUSERIAL SYSTEM

NO ID------ --------%12906 SYS1%22906 SYS2•••

EREP_DASD_GROUP:EREP_DASD_GROUP

This lookup table converts processor serial numbers and device addresses tostrings and groups of DASD devices.


CPU_SERIAL_NO K CHAR(6) Serial number of the processor. This can containglobal search characters.

DEVICE_ADDRESS K CHAR(4) Device address or device number. This can containglobal search characters.

DASD_GROUP CHAR(8) Name used to identify a group of DASD devices.

DASD_STRING CHAR(8) Name used to identify a string of DASD devices.


CPUSERIAL DEVICE DASD DASD

NO ADDRESS GROUP STRING------ ------- -------- --------%12906 012% GROUP1 STR120%12906 013% GROUP1 STR130%12906 014% GROUP1 STR140%12906 015% GROUP1 STR150%22906 012% GROUP1 STR120%22906 013% GROUP1 STR130%22906 014% GROUP1 STR140%22906 015% GROUP1 STR150%12906 022% GROUP2 STR220%12906 023% GROUP2 STR230%12906 024% GROUP2 STR240%12906 025% GROUP2 STR250%22906 022% GROUP2 STR220%22906 023% GROUP2 STR230%22906 024% GROUP2 STR240%22906 025% GROUP2 STR250•••

EREP_DASD_GROUP:EREP_DASD_GROUP

This lookup table converts processor serial numbers and device addresses tostrings and groups of DASD devices.



CPU_SERIAL_NO K CHAR(6) Serial number of the processor. This can containglobal search characters.

DEVICE_ADDRESS K CHAR(4) Device address or device number. This can containglobal search characters.

DASD_GROUP CHAR(8) Name used to identify a group of DASD devices.

DASD_STRING CHAR(8) Name used to identify a string of DASD devices.


CPUSERIAL DEVICE DASD DASD

NO ADDRESS GROUP STRING------ ------- -------- --------%12906 012% GROUP1 STR120%12906 013% GROUP1 STR130%12906 014% GROUP1 STR140%12906 015% GROUP1 STR150%22906 012% GROUP1 STR120%22906 013% GROUP1 STR130%22906 014% GROUP1 STR140%22906 015% GROUP1 STR150%12906 022% GROUP2 STR220%12906 023% GROUP2 STR230%12906 024% GROUP2 STR240%12906 025% GROUP2 STR250%22906 022% GROUP2 STR220%22906 023% GROUP2 STR230%22906 024% GROUP2 STR240%22906 025% GROUP2 STR250•••

ReportsThe EREP component provides these reports:v DASD errors summary reports

– EREP DASD Errors by Device Type, Monthly Trend report– EREP DASD Errors by DASD Group, Monthly Trend report– EREP DASD Errors by Control Unit, Monthly Trend report

v VTAM-controlled device errors summary report– EREP VTAM Errors by Resource, Monthly Trend report

v IPL system initialization statistics– EREP IPL and Downtime Summary, Daily report

DASD errors summary reportsThe DASD errors summary reports show DASD error statistics by device type,group of DASD devices, and control unit types.

EREP DASD Errors by Device Type, Monthly Trend report:EREP DASD Errors by Device Type, Monthly Trend report

This report shows monthly DASD error statistics by device type.



Report IDEREP01

Report groupEREP reports

SourceEREP_DASD_M

AttributesEREP, Problem, DASD, Monthly, Trend

VariablesFrom_month, To_month, System_ID


Month start dateThe date of the first day of the month of the measurement.

Device typeThe DASD device type.

Bus out errorsThe number of channel bus out parity errors that occurred on the devicetype during the month.

Perm equip checksThe number of permanent equipment checks that occurred on the devicetype during the month.

Temp equip checksThe number of temporary equipment checks that occurred on the devicetype during the month.

Perm data checksThe number of permanent data checks that occurred on the device typeduring the month.

Temp data checksThe number of temporary data checks that occurred on the device typeduring the month.

Total errorsThe total number of errors that occurred on the device type during themonth.

EREP DASD Errors by Device Type, Monthly TrendSystem: ’SYS1’ Month: ’2003-11-01’ to ’2003-12-01’

Month Perm Temp Perm Tempstart Device Bus out equip equip data data Total I/Odate type errors checks checks checks checks errors retries---------- -------- ------- ------- ------- ------- ------- ------- -------2003-11-01 3380-K 0 0 28 0 0 28 02003-12-01 3380-K 0 0 17 0 0 17 0

Tivoli Decision Support for z/OS Report: EREP01

Figure 43. Example of an EREP DASD Errors by Device Type, Monthly Trend report


I/O retriesThe number of I/O retries attempted on the device type during the month.

EREP DASD Errors by DASD Group, Monthly Trend report:EREP DASD Errors by DASD Group, Monthly Trend report

This report shows monthly DASD error statistics by group of DASD devices. Formore information on using this report, refer to the System Performance Feature Guide.


Report IDEREP02


SourceEREP_DASD_M





DASD groupThe name of a group of DASD devices, as defined in theEREP_DASD_GROUP lookup table.

Bus out errorsThe number of channel bus-out parity errors that occurred for the DASDgroup during the month.

Perm equip checksThe number of permanent equipment checks that occurred for the DASDgroup during the month.

EREP DASD Errors by DASD Group, Monthly TrendSystem: ’SYS1’ Month: ’2003-11-01’ to ’2003-12-01’

Month Perm Temp Perm Tempstart DASD Bus out equip equip data data Total I/Odate group errors checks checks checks checks errors retries---------- -------- ------- ------- ------- ------- ------- ------- -------2003-11-01 08C0 0 0 14 0 0 14 02003-11-01 08C1 0 0 14 0 0 14 02003-12-01 08C0 0 0 12 0 0 12 02003-12-01 08C1 0 0 5 0 0 5 0


Figure 44. Example of an EREP DASD Errors by DASD Group, Monthly Trend report


Temp equip checksThe number of temporary equipment checks that occurred for the DASDgroup during the month.

Perm data checksThe number of permanent data checks that occurred for the DASD groupduring the month.

Temp data checksThe number of temporary data checks that occurred for the DASD groupduring the month.

Total errorsThe total number of errors that occurred for the DASD group during themonth.

I/O retriesThe number of I/O retries attempted for the DASD group during themonth.

EREP DASD Errors by Control Unit, Monthly Trend report:EREP DASD Errors by Control Unit, Monthly Trend report

This report shows monthly DASD error statistics by control unit type.


Report IDEREP03


SourceEREP_DASD_M





EREP DASD Errors by Control Unit, Monthly TrendSystem: ’SYS1’ Month: ’2003-11-01’ to ’2003-12-01’

Month Control Perm Temp Perm Tempstart unit Bus out equip equip data data Total I/Odate ID errors checks checks checks checks errors retries---------- --------- ------- ------- ------- ------- ------- ------- -------2003-11-01 06 0 0 28 0 0 28 02003-12-01 06 0 0 17 0 0 17 0


Figure 45. Example of an EREP DASD Errors by Control Unit, Monthly Trend report


Control unit IDThe control unit type.

Bus out errorsThe number of channel bus-out parity errors that occurred for the controlunit during the month.

Perm equip checksThe number of permanent equipment checks that occurred for the controlunit during the month.

Temp equip checksThe number of temporary equipment checks that occurred for the controlunit during the month.

Perm data checksThe number of permanent data checks that occurred for the control unitduring the month.

Temp data checksThe number of temporary data checks that occurred for the control unitduring the month.

Total errorsThe total number of errors that occurred for the control unit during themonth.

I/O retriesThe number of I/O retries for the control unit during the month.

VTAM-controlled device errors summary reportsThese reports show error statistics for channel-attached devices controlled byVTAM.

EREP VTAM Errors by Resource, Monthly Trend report:EREP VTAM Errors by Resource, Monthly Trend report

This report shows monthly error statistics for channel-attached devices controlledby VTAM. For more information on using this report, refer to the SystemPerformance Feature Guide.


Report IDEREP04


SourceEREP_VTAM_M

AttributesEREP, Problem, VTAM, Resource, Monthly, Trend





Device typeThe teleprocessing device type.

Resource nameThe VTAM-controlled resource name.

Perm errorsThe number of permanent errors that occurred during the month.

Temp errorsThe number of temporary errors that occurred during the month.

Total errorsThe total number of errors that occurred during the month.

I/O retriesThe number of I/O retries that occurred during the month.

Start I/O countThe number of start I/O instructions issued during the month.

IPL system initialization statisticsThe IPL system initialization statistics report shows information about each IPLand a downtime summary. It also lists the IPL reason codes and their descriptions.

EREP IPL and Downtime Summary, Daily report:EREP IPL and Downtime Summary, Daily report

This report lists each IPL and provides a downtime summary. For moreinformation on using this report, refer to the System Performance Feature Guide.


Report IDEREP05


SourceEREP_IPL_T

EREP VTAM Errors by Resource, Monthly TrendSystem: ’SYS1’ Month: ’2003-11-01’ to ’2003-12-01’

Month Startstart Device Resource Perm Temp Total I/O I/Odate type name errors errors errors retries count---------- -------- -------- --------- --------- --------- -------- ---------2003-11-01 3270 FS1SL7D2 1 0 1 0 412003-12-01 3270 FS1SL7C8 8 0 8 0 202003-12-01 3270 FS1SL7D2 2 0 2 0 89


Figure 46. Example of an EREP VTAM Errors by Resource, Monthly Trend report


AttributesEREP, Problem, IPL, Daily

VariablesSystem_ID, From_date, To_date


System IDThe name of the system that was IPLed.

Date The date when the IPL was performed.

Time The time when the IPL was performed.

IPL reasonThe IPL reason code.

Downtime (min)The system downtime, in minutes.

Tivoli Information Management for z/OS (INFOMAN) componentCustomizationv Making input data availablev Modifying collect jobv Updating lookup tables




– INFOMAN_CHANGE_D– INFOMAN_PROBLEM_D

v Lookup tables– INFOMAN_OBJECTIVE– INFOMAN_TYPE

EREP IPL and Downtime Summary, DailySystem: SYSTEM_ID Date: ’2003-12-01’ to ’2003-12-15’

System IPL DowntimeID Date Time reason (min)

-------- ---------- ---------- ------ ----------012906 2003-12-02 17:15:17 DF 29

2003-12-02 17:59:47 DF 9----------

Total 38


Figure 47. Example of an EREP IPL and Downtime Summary, Daily report


Reportsv Problem management reports

– INFOMAN Problem Cause, Monthly Overview report– INFOMAN Problems, Monthly Overview report– INFOMAN Problems, Daily Trend report– INFOMAN Problems Closed, Monthly Overview report– INFOMAN Problems Not Closed, Weekly Overview report

v Change management reports– INFOMAN Change Successes, Monthly Overview report– INFOMAN Changes, Monthly Overview report– INFOMAN Changes, Daily Trend report– INFOMAN Changes Closed, Monthly Overview report– INFOMAN Changes Not Closed, Weekly Overview report

v Mixed reports– INFOMAN Problems and Changes, Monthly Trend report

CustomizationBefore you can use the Tivoli Information Management for z/OS (INFOMAN)component to collect data and create useful reports, you must customize and testthe installation. This chapter describes the steps you must perform to customizethe Tivoli Information Management for z/OS (INFOMAN) component:1. Making input data available.2. Modifying collect job.3. Updating lookup tables.

Use the Tivoli Information Management for z/OS (INFOMAN) component as asample. As shipped, it will work correctly only if you are running a default TivoliInformation Management for z/OS system. If you are running a changed system,you must customize the Tivoli Information Management for z/OS (INFOMAN)component as described in this chapter.

Making input data availableTo ensure that the Tivoli Information Management for z/OS (INFOMAN)component collects the right data, perform these steps:1. Check the report format tables (RFT) provided with Tivoli Decision Support for

z/OS to see if the definition maps the Tivoli Information Management for z/OSsystem on which you are running. The RFT, named DRLJRFT2, extractsproblem and change records from the Tivoli Information Management for z/OSdatabase and writes these records to a sequential data set. DRLJRFT2 isautomatically run by the Tivoli Information Management for z/OS collect job.

2. Change the RFT as needed. For detailed information, refer to the TivoliInformation Management for z/OS: Data Reporting User’s Guide.

3. If you change the RFT, check that the provided record definitions are still validand correctly map the log from the Tivoli Information Management for z/OSdatabase (the result of the RFT).You might also need to change the table definitions and the reports.

The following figures show the report format table DRLJRFT2.


/******************************++***************************************//* *//* Licensed Materials - Property of IBM *//* *//* 5698-B06 (C) Copyright IBM Corporation 2001, 2005. *//* See Copyright Instructions. *//* *//***********************************************************************//* *//* Name: DRLJRFT2 *//* *//* Status: Tivoli Decision Support for z/OS 1.7.1 *//* *//* Function: *//* Extract problems and changes from the Tivoli Information *//* Management for z/OS (INFOMAN) database *//* and write them to a sequential file. *//* *//* Data source: *//* The Tivoli Information Management for z/OS (INFOMAN) database *//* *//***********************************************************************/

/***********************************************************************//* Extract problems from the Tivoli Information Management for z/OS *//* (INFOMAN) database and write them to a sequential file *//***********************************************************************/SECTION SEPARATION(0)

SETD IDATE(STARTDAT) VAL(&ZECDATE) OP(-) VAL(400) /*<= Optionally

SETD IDATE(STOPDAT) VAL(&ZECDATE) OP(+) VAL(100) /*<= change extract/* interval here

SEARCH ARG(!S0032 DATO/&STARTDAT -&STOPDAT) /* Search problems

PUT COL(001) VAL(V12) /* Tsd versionPUT COL(004) VAL(P) /* Problem record flag

IF DATA(DATO/.) OP(=) VAL(&ZIFDATA)SETD IDATE(IDATO) DATA(DATO/.) /* Date occurred,IF VAL(&IDATO) FROM(5) FOR(1) OP(=) VAL(’/’)

PUT COL(005) VAL(&IDATO) FROM(6) FOR(2) /* MonthPUT COL(007) VAL(&IDATO) FROM(9) FOR(2) /* DayPUT COL(009) VAL(&IDATO) FROM(3) FOR(2) /* YearPUT COL(013) DATA(TIMO/.) LENGTH(5) /* Time occurred

ELSEIF VAL(&IDATO) FROM(3) FOR(1) OP(=) VAl(’/’)

PUT COL(005) VAL(&IDATO) FROM(4) FOR(2) /* MonthPUT COL(007) VAL(&IDATO) FROM(7) FOR(2) /* DayPUT COL(009) VAL(&IDATO) FROM(1) FOR(2) /* YearPUT COL(013) DATA(TIMO/.) LENGTH(5) /* Time occurred

EIFEIF

EIF

Figure 48. Report format table DRLJRFT2 (Part 1 of 12)


IF DATA(DATA/.) OP(=) VAL(&ZIFDATA)SETD IDATE(IDATA) DATA(DATA/.) /* Date assigned,IF VAL(&IDATA) FROM(5) FOR(1) OP(=) VAL(’/’)

PUT COL(018) VAL(&IDATA) FROM(6) FOR(2) /* MonthPUT COL(020) VAL(&IDATA) FROM(9) FOR(2) /* DayPUT COL(022) VAL(&IDATA) FROM(3) FOR(2) /* YearPUT COL(026) DATA(TIMA/.) LENGTH(5) /* Time occurred

ELSEIF VAL(&IDATA) FROM(3) FOR(1) OP(=) VAl(’/’)

PUT COL(018) VAL(&IDATA) FROM(4) FOR(2) /* MonthPUT COL(020) VAL(&IDATA) FROM(7) FOR(2) /* DayPUT COL(022) VAL(&IDATA) FROM(1) FOR(2) /* YearPUT COL(026) DATA(TIMA/.) LENGTH(5) /* Time occurred

EIFEIF

EIF

IF DATA(DATR/.) OP(=) VAL(&ZIFDATA)SETD IDATE(IDATR) DATA(DATR/.) /* Date closed,IF VAL(&IDATR) FROM(5) FOR(1) OP(=) VAL(’/’)

PUT COL(031) VAL(&IDATR) FROM(6) FOR(2) /* MonthPUT COL(033) VAL(&IDATR) FROM(9) FOR(2) /* DayPUT COL(035) VAL(&IDATR) FROM(3) FOR(2) /* YearPUT COL(039) DATA(TIMR/.) LENGTH(5) /* Time occurred

ELSEIF VAL(&IDATR) FROM(3) FOR(1) OP(=) VAl(’/’)

PUT COL(031) VAL(&IDATR) FROM(4) FOR(2) /* MonthPUT COL(033) VAL(&IDATR) FROM(7) FOR(2) /* DayPUT COL(035) VAL(&IDATR) FROM(1) FOR(2) /* YearPUT COL(039) DATA(TIMR/.) LENGTH(5) /* Time occurred

EIFEIF

EIF

IF DATA(DATE/.) OP(=) VAL(&ZIFDATA)SETD IDATE(IDATE) DATA(DATE/.) /* Date enteredIF VAL(&IDATE) FROM(5) FOR(1) OP(=) VAL(’/’)

PUT COL(044) VAL(&IDATE) FROM(6) FOR(2) /* MonthPUT COL(046) VAL(&IDATE) FROM(9) FOR(2) /* DayPUT COL(048) VAL(&IDATE) FROM(3) FOR(2) /* YearPUT COL(052) DATA(TIME/.) LENGTH(5) /* Time occurred

ELSEIF VAL(&IDATE) FROM(3) FOR(1) OP(=) VAl(’/’)

PUT COL(044) VAL(&IDATE) FROM(4) FOR(2) /* MonthPUT COL(046) VAL(&IDATE) FROM(7) FOR(2) /* DayPUT COL(048) VAL(&IDATE) FROM(1) FOR(2) /* YearPUT COL(052) DATA(TIME/.) LENGTH(5) /* Time occurred

EIFEIF

EIF

IF DATA(DATF/.) OP(=) VAL(&ZIFDATA)SETD IDATE(IDATF) DATA(DATF/.) /* Date finishedIF VAL(&IDATF) FROM(5) FOR(1) OP(=) VAL(’/’)

PUT COL(057) VAL(&IDATF) FROM(6) FOR(2) /* MonthPUT COL(059) VAL(&IDATF) FROM(9) FOR(2) /* DayPUT COL(061) VAL(&IDATF) FROM(3) FOR(2) /* YearPUT COL(065) DATA(TIMF/.) LENGTH(5) /* Time occurred



ELSEIF VAL(&IDATF) FROM(3) FOR(1) OP(=) VAl(’/’)

PUT COL(057) VAL(&IDATF) FROM(4) FOR(2) /* MonthPUT COL(059) VAL(&IDATF) FROM(7) FOR(2) /* DayPUT COL(061) VAL(&IDATF) FROM(1) FOR(2) /* YearPUT COL(065) DATA(TIMF/.) LENGTH(5) /* Time occurred

EIFEIF

EIF

IF DATA(DATD/.) OP(=) VAL(&ZIFDATA)SETD IDATE(IDATD) DATA(DATD/.) /* Date fix req.IF VAL(&IDATD) FROM(5) FOR(1) OP(=) VAL(’/’)

PUT COL(070) VAL(&IDATD) FROM(6) FOR(2) /* MonthPUT COL(072) VAL(&IDATD) FROM(9) FOR(2) /* DayPUT COL(074) VAL(&IDATD) FROM(3) FOR(2) /* YearPUT COL(078) DATA(TIMD/.) LENGTH(5) /* Time occurred

ELSEIF VAL(&IDATD) FROM(3) FOR(1) OP(=) VAl(’/’)

PUT COL(070) VAL(&IDATD) FROM(4) FOR(2) /* MonthPUT COL(072) VAL(&IDATD) FROM(7) FOR(2) /* DayPUT COL(074) VAL(&IDATD) FROM(1) FOR(2) /* YearPUT COL(078) DATA(TIMD/.) LENGTH(5) /* Time occurred

EIFEIF

EIF

IF DATA(DATM/.) OP(=) VAL(&ZIFDATA)SETD IDATE(IDATM) DATA(DATM/.) /* Date last alterIF VAL(&IDATM) FROM(5) FOR(1) OP(=) VAL(’/’)

PUT COL(083) VAL(&IDATM) FROM(6) FOR(2) /* MonthPUT COL(085) VAL(&IDATM) FROM(9) FOR(2) /* DayPUT COL(087) VAL(&IDATM) FROM(3) FOR(2) /* YearPUT COL(091) DATA(TIMM/.) LENGTH(5) /* Time occurred

ELSEIF VAL(&IDATM) FROM(3) FOR(1) OP(=) VAl(’/’)

PUT COL(083) VAL(&IDATM) FROM(4) FOR(2) /* MonthPUT COL(085) VAL(&IDATM) FROM(7) FOR(2) /* DayPUT COL(087) VAL(&IDATM) FROM(1) FOR(2) /* YearPUT COL(091) DATA(TIMM/.) LENGTH(5) /* Time occurred

EIFEIF

EIF

IF DATA(DATRF/.) OP(=) VAL(&ZIFDATA)SETD IDATE(IDATRF) DATA(DATRF/.) /* Date last refr.IF VAL(&IDATRF) FROM(5) FOR(1) OP(=) VAL(’/’)

PUT COL(096) VAL(&IDATRF) FROM(6) FOR(2) /* MonthPUT COL(098) VAL(&IDATRF) FROM(9) FOR(2) /* DayPUT COL(100) VAL(&IDATRF) FROM(3) FOR(2) /* YearPUT COL(104) DATA(TIMRF/.) LENGTH(5) /* Time occurred

ELSEIF VAL(&IDATRF) FROM(3) FOR(1) OP(=) VAl(’/’)

PUT COL(096) VAL(&IDATRF) FROM(4) FOR(2) /* MonthPUT COL(098) VAL(&IDATRF) FROM(7) FOR(2) /* DayPUT COL(100) VAL(&IDATRF) FROM(1) FOR(2) /* YearPUT COL(104) DATA(TIMRF/.) LENGTH(5) /* Time occurred

EIFEIF

EIF



IF DATA(DATX/.) OP(=) VAL(&ZIFDATA)SETD IDATE(IDATX) DATA(DATX/.) /* Date openedIF VAL(&IDATX) FROM(5) FOR(1) OP(=) VAL(’/’)

PUT COL(109) VAL(&IDATX) FROM(6) FOR(2) /* MonthPUT COL(111) VAL(&IDATX) FROM(9) FOR(2) /* DayPUT COL(113) VAL(&IDATX) FROM(3) FOR(2) /* YearPUT COL(117) DATA(TIMX/.) LENGTH(5) /* Time occurred

ELSEIF VAL(&IDATX) FROM(3) FOR(1) OP(=) VAl(’/’)

PUT COL(109) VAL(&IDATX) FROM(4) FOR(2) /* MonthPUT COL(111) VAL(&IDATX) FROM(7) FOR(2) /* DayPUT COL(113) VAL(&IDATX) FROM(1) FOR(2) /* YearPUT COL(117) DATA(TIMX/.) LENGTH(5) /* Time occurred

EIFEIF

EIF

IF DATA(DATN/.) OP(=) VAL(&ZIFDATA)SETD IDATE(IDATN) DATA(DATN/.) /* Date rep. notif.IF VAL(&IDATN) FROM(5) FOR(1) OP(=) VAL(’/’)

PUT COL(122) VAL(&IDATN) FROM(6) FOR(2) /* MonthPUT COL(124) VAL(&IDATN) FROM(9) FOR(2) /* DayPUT COL(126) VAL(&IDATN) FROM(3) FOR(2) /* Year

ELSEIF VAL(&IDATN) FROM(3) FOR(1) OP(=) VAl(’/’)


EIFEIF

EIF

IF DATA(DATB/.) OP(=) VAL(&ZIFDATA)SETD IDATE(IDATB) DATA(DATB/.) /* Date startedIF VAL(&IDATB) FROM(5) FOR(1) OP(=) VAL(’/’)

PUT COL(130) VAL(&IDATB) FROM(6) FOR(2) /* MonthPUT COL(132) VAL(&IDATB) FROM(9) FOR(2) /* DayPUT COL(134) VAL(&IDATB) FROM(3) FOR(2) /* YearPUT COL(138) DATA(TIMB/.) LENGTH(5) /* Time started

ELSEIF VAL(&IDATB) FROM(3) FOR(1) OP(=) VAl(’/’)

PUT COL(130) VAL(&IDATB) FROM(4) FOR(2) /* MonthPUT COL(132) VAL(&IDATB) FROM(7) FOR(2) /* DayPUT COL(134) VAL(&IDATB) FROM(1) FOR(2) /* YearPUT COL(138) DATA(TIMB/.) LENGTH(5) /* Time started

EIFEIF

EIF

IF DATA(DATT/.) OP(=) VAL(&ZIFDATA)SETD IDATE(IDATT) DATA(DATT/.) /* Target dateIF VAL(&IDATT) FROM(5) FOR(1) OP(=) VAL(’/’)

PUT COL(143) VAL(&IDATT) FROM(6) FOR(2) /* MonthPUT COL(145) VAL(&IDATT) FROM(9) FOR(2) /* DayPUT COL(147) VAL(&IDATT) FROM(3) FOR(2) /* Year

ELSEIF VAL(&IDATT) FROM(3) FOR(1) OP(=) VAl(’/’)


EIFEIF

EIF



PUT COL(151) DATA(GROA/.) LENGTH(11) /* Assignee departmentPUT COL(162) DATA(PERA/.) LENGTH(40) /* Assignee namePUT COL(202) DATA(!S0B2E) LENGTH(13) /* Assignee phonePUT COL(215) DATA(COUX/.) LENGTH(3) /* Assignment numberPUT COL(218) DATA(STAA/.) LENGTH(8) /* Assignment statusPUT COL(226) DATA(APAR/.) LENGTH(7) /* APAR numberPUT COL(233) DATA(STAF/.) LENGTH(8) /* APAR/PTF statusPUT COL(241) DATA(MISB/.) LENGTH(3) /* Bypass availablePUT COL(244) DATA(RNCX/.) LENGTH(8) /* Cause change numberPUT COL(252) DATA(CODC/.) LENGTH(8) /* Cause codePUT COL(260) DATA(APPL/.) LENGTH(8) /* Checkout appl. IDPUT COL(268) DATA(!S0D12) LENGTH(8) /* Circuit numberPUT COL(276) DATA(CLSN/.) LENGTH(8) /* Cluster namePUT COL(284) DATA(PIDS/.) LENGTH(11) /* Component aparedPUT COL(295) DATA(!S0D69) LENGTH(11) /* Console outputPUT COL(306) DATA(CODP/.) LENGTH(8) /* Current phasePUT COL(314) DATA(PRIO/.) LENGTH(2) /* Current priorityPUT COL(316) DATA(INTC/.) LENGTH(8) /* Customer PD timePUT COL(324) DATA(DSTN/.) LENGTH(11) /* data set typePUT COL(335) DATA(!S0E0F) LENGTH(45) /* DescriptionPUT COL(380) DATA(IMPD/.) LENGTH(8) /* Device impactPUT COL(388) DATA(COMD/.) LENGTH(8) /* Device namePUT COL(396) DATA(!S0D76) LENGTH(11) /* Diagnostic outputPUT COL(407) DATA(!S0D7A) LENGTH(54) /* Dump data setPUT COL(461) DATA(COUD/.) LENGTH(3) /* Duplicate countPUT COL(464) DATA(CLAE/.) LENGTH(8) /* Entry priv. classPUT COL(472) DATA(CODE/.) LENGTH(8) /* Error codePUT COL(480) DATA(ESCL/.) LENGTH(1) /* Escalation levelPUT COL(481) DATA(LVLS/.) LENGTH(8) /* Ec numberPUT COL(489) DATA(MISX/.) LENGTH(3) /* Fix availablePUT COL(492) DATA(RNCR/.) LENGTH(8) /* Fix change numberPUT COL(500) DATA(GWID/.) LENGTH(9) /* Gateway IDPUT COL(509) DATA(!S0D71) LENGTH(11) /* Graph/log dataPUT COL(520) DATA(PRII/.) LENGTH(2) /* Initial priorityPUT COL(522) DATA(!S0D6B) LENGTH(11) /* Input dataPUT COL(533) DATA(SP01/.) LENGTH(8) /* Interested class 1PUT COL(541) DATA(SP02/.) LENGTH(8) /* Interested class 2PUT COL(549) DATA(SP03/.) LENGTH(8) /* Interested class 3PUT COL(557) DATA(SP04/.) LENGTH(8) /* Interested class 4PUT COL(565) DATA(SP05/.) LENGTH(8) /* Interested class 5PUT COL(573) DATA(SP06/.) LENGTH(8) /* Interested class 6PUT COL(581) DATA(SP07/.) LENGTH(8) /* Interested class 7PUT COL(589) DATA(SP08/.) LENGTH(8) /* Interested class 8PUT COL(597) DATA(SP09/.) LENGTH(8) /* Interested class 9PUT COL(605) DATA(SP10/.) LENGTH(8) /* Interested class 10PUT COL(613) DATA(SP11/.) LENGTH(8) /* Interested class 11PUT COL(621) DATA(SP12/.) LENGTH(8) /* Interested class 12PUT COL(629) DATA(SP13/.) LENGTH(8) /* Interested class 13PUT COL(637) DATA(SP14/.) LENGTH(8) /* Interested class 14PUT COL(645) DATA(SP15/.) LENGTH(8) /* Interested class 15PUT COL(653) DATA(SP16/.) LENGTH(8) /* Interested class 16PUT COL(661) DATA(SP17/.) LENGTH(8) /* Interested class 17PUT COL(669) DATA(SP18/.) LENGTH(8) /* Interested class 18PUT COL(677) DATA(SP19/.) LENGTH(8) /* Interested class 19PUT COL(685) DATA(SP20/.) LENGTH(8) /* Interested class 20PUT COL(693) DATA(SP21/.) LENGTH(8) /* Interested class 21PUT COL(701) DATA(SP22/.) LENGTH(8) /* Interested class 22PUT COL(709) DATA(SP23/.) LENGTH(8) /* Interested class 23PUT COL(717) DATA(SP24/.) LENGTH(8) /* Interested class 24PUT COL(725) DATA(SP25/.) LENGTH(8) /* Interested class 25PUT COL(733) DATA(SP26/.) LENGTH(8) /* Interested class 26



PUT COL(741) DATA(SP27/.) LENGTH(8) /* Interested class 27PUT COL(749) DATA(SP28/.) LENGTH(8) /* Interested class 28PUT COL(757) DATA(!S0D16) LENGTH(8) /* Ipcs record numberPUT COL(765) DATA(COMK/.) LENGTH(8) /* Key item affectedPUT COL(773) DATA(LOCC/.) LENGTH(8) /* Location codePUT COL(781) DATA(IMPN/.) LENGTH(8) /* Network impactPUT COL(789) DATA(COMN/.) LENGTH(8) /* Network namePUT COL(797) DATA(NOTID/.) LENGTH(8) /* Notify user IDPUT COL(805) DATA(!S0D74) LENGTH(11) /* Operator formPUT COL(816) DATA(RNPD/.) LENGTH(8) /* Original prb. nbrPUT COL(824) DATA(INTO/.) LENGTH(8) /* OutagePUT COL(832) DATA(TYPO/.) LENGTH(2) /* Outage typePUT COL(834) DATA(!S0D6A) LENGTH(11) /* Output dataPUT COL(845) DATA(CLAO/.) LENGTH(8) /* Owning classPUT COL(853) DATA(CODM/.) LENGTH(8) /* Probable causePUT COL(861) DATA(RNID/.) LENGTH(8) /* Problem numberPUT COL(869) DATA(STAC/.) LENGTH(7) /* Problem statusPUT COL(876) DATA(TYPE/.) LENGTH(8) /* Problem typePUT COL(884) DATA(IMPP/.) LENGTH(8) /* Program impactPUT COL(892) DATA(COMX/.) LENGTH(8) /* Program namePUT COL(900) DATA(PTFF/.) LENGTH(7) /* Ptf numberPUT COL(907) DATA(!S0D8C) LENGTH(8) /* Repair timePUT COL(915) DATA(PERS/.) LENGTH(40) /* Reported byPUT COL(955) DATA(GROS/.) LENGTH(11) /* Reported departmentPUT COL(966) DATA(!S0B2D) LENGTH(13) /* Reported phonePUT COL(979) DATA(INTR/.) LENGTH(8) /* Rerun timePUT COL(987) DATA(PERR/.) LENGTH(15) /* Resolved byPUT COL(1002) DATA(GROR/.) LENGTH(11) /* Resolver departmentPUT COL(1013) DATA(!S0B2F) LENGTH(13) /* Resolver phonePUT COL(1026) DATA(CLAR/.) LENGTH(8) /* Resolver classPUT COL(1034) DATA(!S0BE2) LENGTH(54) /* Resource namePUT COL(1088) DATA(!S0C12) LENGTH(54) /* Resource typePUT COL(1142) DATA(!S0D89) LENGTH(8) /* Response/trav timePUT COL(1150) DATA(!S0D6E) LENGTH(11) /* Source dataPUT COL(1161) DATA(!S0D6D) LENGTH(11) /* Source listingPUT COL(1172) DATA(IMPS/.) LENGTH(8) /* System impactPUT COL(1180) DATA(NASY/.) LENGTH(8) /* System namePUT COL(1188) DATA(!S0D6F) LENGTH(11) /* SMP listingPUT COL(1199) DATA(TECID/.) LENGTH(20) /* Tec event IDPUT COL(1219) DATA(!S0C93) LENGTH(8) /* Total timePUT COL(1227) DATA(!S0D70) LENGTH(11) /* Trace dataPUT COL(1238) DATA(PERC/.) LENGTH(15) /* Tracked byPUT COL(1253) DATA(GROC/.) LENGTH(11) /* Tracked departmentPUT COL(1264) DATA(!S0B30) LENGTH(13) /* Tracker phonePUT COL(1277) DATA(CLAT/.) LENGTH(8) /* Transfer to classPUT COL(1285) DATA(PMREC/.) LENGTH(15) /* TSD record IDPUT COL(1300) DATA(OSITE/.) LENGTH(6) /* TSD site IDPUT COL(1306) DATA(TUSER/.) LENGTH(15) /* TSD user IDPUT COL(1321) DATA(!S0D14) LENGTH(8) /* User form numberPUT COL(1329) DATA(USER/.) LENGTH(8) /* User last alteredPUT COL(1337) DATA(NUMV/.) LENGTH(11) /* Vendor numberPUT COL(1348) DATA(INTV/.) LENGTH(8) /* Vendor PD timePUT COL(1356) DATA(STAP/.) LENGTH(2) /* Vendor priorityPUT COL(1358) DATA(STAV/.) LENGTH(8) /* Vendor statusPUT COL(1366) DATA(!S05F2) LENGTH(8) /* Vendor PMR status



IF VAL(&ZICDATE) FROM(5) FOR(1) OP(=) VAL(’/’)PUT COL(1374) VAL(&ZICDATE) FROM(6) FOR(2) /* Run Date, MonthPUT COL(1376) VAL(&ZICDATE) FROM(9) FOR(2) /* DayPUT COL(1378) VAL(&ZICDATE) FROM(3) FOR(2) /* YearPUT COL(1382) VAL(&ZCTIME) /* Time of RFT run

ELSEIF VAL(&ZICDATE) FROM(3) FOR(1) OP(=) VAL(’/’)

PUT COL(1374) VAL(&ZICDATE) FROM(4) FOR(2) /* Run Date, MonthPUT COL(1376) VAL(&ZICDATE) FROM(7) FOR(2) /* DayPUT COL(1378) VAL(&ZICDATE) FROM(1) FOR(2) /* YearPUT COL(1382) VAL(&ZCTIME) /* Time of RFT run

EIFEIF

ESEARCHESECTION

/*********************************************************************//* Extract changes from the Tivoli Information Management for z/OS db*//* and append them to the sequential file. *//*********************************************************************/SECTION SEPARATION(0)

SEARCH ARG(!S0B06 DATP/&STARTDAT -&STOPDAT) /* Search changes

PUT COL(001) VAL(V12) /* Tsd versionPUT COL(004) VAL(C) /* Change record flag

IF DATA(DATD/.) OP(=) VAL(&ZIFDATA)SETD IDATE(IDATD) DATA(DATD/.) /* Date required,IF VAL(&IDATD) FROM(5) FOR(1) OP(=) VAL(’/’)

PUT COL(005) VAL(&IDATD) FROM(6) FOR(2) /* MonthPUT COL(007) VAL(&IDATD) FROM(9) FOR(2) /* DayPUT COL(009) VAL(&IDATD) FROM(3) FOR(2) /* Year

ELSEIF VAL(&IDATD) FROM(3) FOR(1) OP(=) VAl(’/’)

PUT COL(005) VAL(&IDATD) FROM(4) FOR(2) /* MonthPUT COL(007) VAL(&IDATD) FROM(7) FOR(2) /* DayPUT COL(009) VAL(&IDATD) FROM(1) FOR(2) /* Year

EIFEIF

EIF

IF DATA(DATB/.) OP(=) VAL(&ZIFDATA)SETD IDATE(IDATB) DATA(DATB/.) /* Date actual startIF VAL(&IDATD) FROM(5) FOR(1) OP(=) VAL(’/’)

PUT COL(013) VAL(&IDATB) FROM(6) FOR(2) /* MonthPUT COL(015) VAL(&IDATB) FROM(9) FOR(2) /* DayPUT COL(017) VAL(&IDATB) FROM(3) FOR(2) /* Year

ELSEIF VAL(&IDATB) FROM(3) FOR(1) OP(=) VAl(’/’)

PUT COL(013) VAL(&IDATB) FROM(4) FOR(2) /* MonthPUT COL(015) VAL(&IDATB) FROM(7) FOR(2) /* DayPUT COL(017) VAL(&IDATB) FROM(1) FOR(2) /* Year

EIFEIF

EIF



IF DATA(DATF/.) OP(=) VAL(&ZIFDATA)SETD IDATE(IDATF) DATA(DATF/.) /* Date completedIF VAL(&IDATF) FROM(5) FOR(1) OP(=) VAL(’/’)

PUT COL(021) VAL(&IDATF) FROM(6) FOR(2) /* MonthPUT COL(023) VAL(&IDATF) FROM(9) FOR(2) /* DayPUT COL(025) VAL(&IDATF) FROM(3) FOR(2) /* Year

ELSEIF VAL(&IDATF) FROM(3) FOR(1) OP(=) VAl(’/’)

PUT COL(021) VAL(&IDATF) FROM(4) FOR(2) /* MonthPUT COL(023) VAL(&IDATF) FROM(7) FOR(2) /* DayPUT COL(025) VAL(&IDATF) FROM(1) FOR(2) /* Year

EIFEIF

EIF

IF DATA(DATA/.) OP(=) VAL(&ZIFDATA)SETD IDATE(IDATA) DATA(DATA/.) /* Date assigned,IF VAL(&IDATA) FROM(5) FOR(1) OP(=) VAL(’/’)

PUT COL(029) VAL(&IDATA) FROM(6) FOR(2) /* MonthPUT COL(031) VAL(&IDATA) FROM(9) FOR(2) /* DayPUT COL(033) VAL(&IDATA) FROM(3) FOR(2) /* Year

ELSEIF VAL(&IDATA) FROM(3) FOR(1) OP(=) VAl(’/’)

PUT COL(029) VAL(&IDATA) FROM(4) FOR(2) /* MonthPUT COL(031) VAL(&IDATA) FROM(7) FOR(2) /* DayPUT COL(033) VAL(&IDATA) FROM(1) FOR(2) /* Year

EIFEIF

EIF

IF DATA(DATE/.) OP(=) VAL(&ZIFDATA)SETD IDATE(IDATE) DATA(DATE/.) /* Date entered,IF VAL(&IDATE) FROM(5) FOR(1) OP(=) VAL(’/’)

PUT COL(037) VAL(&IDATE) FROM(6) FOR(2) /* MonthPUT COL(039) VAL(&IDATE) FROM(9) FOR(2) /* DayPUT COL(041) VAL(&IDATE) FROM(3) FOR(2) /* Year

ELSEIF VAL(&IDATE) FROM(3) FOR(1) OP(=) VAl(’/’)

PUT COL(037) VAL(&IDATE) FROM(4) FOR(2) /* MonthPUT COL(039) VAL(&IDATE) FROM(7) FOR(2) /* DayPUT COL(041) VAL(&IDATE) FROM(1) FOR(2) /* Year

EIFEIF

EIF

IF DATA(DATM/.) OP(=) VAL(&ZIFDATA)SETD IDATE(IDATM) DATA(DATM/.) /* Date last enter.IF VAL(&IDATM) FROM(5) FOR(1) OP(=) VAL(’/’)

PUT COL(045) VAL(&IDATM) FROM(6) FOR(2) /* MonthPUT COL(047) VAL(&IDATM) FROM(9) FOR(2) /* DayPUT COL(049) VAL(&IDATM) FROM(3) FOR(2) /* Year

ELSEIF VAL(&IDATM) FROM(3) FOR(1) OP(=) VAl(’/’)

PUT COL(045) VAL(&IDATM) FROM(4) FOR(2) /* MonthPUT COL(047) VAL(&IDATM) FROM(7) FOR(2) /* DayPUT COL(049) VAL(&IDATM) FROM(1) FOR(2) /* Year

EIFEIF

EIF



IF DATA(DATN/.) OP(=) VAL(&ZIFDATA)SETD IDATE(IDATN) DATA(DATN/.) /* Date request. notif.IF VAL(&IDATN) FROM(5) FOR(1) OP(=) VAL(’/’)


ELSEIF VAL(&IDATN) FROM(3) FOR(1) OP(=) VAl(’/’)


EIFEIF

EIF

IF DATA(DATP/.) OP(=) VAL(&ZIFDATA)SETD IDATE(IDATP) DATA(DATP/.) /* Date planned startIF VAL(&IDATP) FROM(5) FOR(1) OP(=) VAL(’/’)

PUT COL(061) VAL(&IDATP) FROM(6) FOR(2) /* MonthPUT COL(063) VAL(&IDATP) FROM(9) FOR(2) /* DayPUT COL(065) VAL(&IDATP) FROM(3) FOR(2) /* Year

ELSEIF VAL(&IDATP) FROM(3) FOR(1) OP(=) VAl(’/’)

PUT COL(061) VAL(&IDATP) FROM(4) FOR(2) /* MonthPUT COL(063) VAL(&IDATP) FROM(7) FOR(2) /* DayPUT COL(065) VAL(&IDATP) FROM(1) FOR(2) /* Year

EIFEIF

EIF

IF DATA(DATT/.) OP(=) VAL(&ZIFDATA)SETD IDATE(IDATT) DATA(DATT/.) /* Date planned endIF VAL(&IDATT) FROM(5) FOR(1) OP(=) VAL(’/’)


ELSEIF VAL(&IDATP) FROM(3) FOR(1) OP(=) VAl(’/’)


EIFEIF

EIF

PUT COL(077) DATA(INTO/.) LENGTH(8) /* Actual durationPUT COL(085) DATA(EFA/.) LENGTH(4) /* Actual effortPUT COL(089) DATA(IMPA/.) LENGTH(6) /* Actual impactPUT COL(095) DATA(TIMX/.) LENGTH(5) /* Actual start timePUT COL(100) DATA(SP01/.) LENGTH(8) /* Approval pending 1PUT COL(108) DATA(SP02/.) LENGTH(8) /* Approval pending 2PUT COL(116) DATA(SP03/.) LENGTH(8) /* Approval pending 3PUT COL(124) DATA(SP04/.) LENGTH(8) /* Approval pending 4PUT COL(132) DATA(SP05/.) LENGTH(8) /* Approval pending 5PUT COL(140) DATA(SP06/.) LENGTH(8) /* Approval pending 6PUT COL(148) DATA(SP07/.) LENGTH(8) /* Approval pending 7PUT COL(156) DATA(SP08/.) LENGTH(8) /* Approval pending 8PUT COL(164) DATA(SP09/.) LENGTH(8) /* Approval pending 9PUT COL(172) DATA(SP10/.) LENGTH(8) /* Approval pending 10PUT COL(180) DATA(SP11/.) LENGTH(8) /* Approval pending 11PUT COL(188) DATA(SP12/.) LENGTH(8) /* Approval pending 12PUT COL(196) DATA(SP13/.) LENGTH(8) /* Approval pending 13



PUT COL(204) DATA(SP14/.) LENGTH(8) /* Approval pending 14PUT COL(212) DATA(SP15/.) LENGTH(8) /* Approval pending 15PUT COL(220) DATA(SP16/.) LENGTH(8) /* Approval pending 16PUT COL(228) DATA(SP17/.) LENGTH(8) /* Approval pending 17PUT COL(236) DATA(SP18/.) LENGTH(8) /* Approval pending 18PUT COL(244) DATA(SA01/.) LENGTH(8) /* Approval provided 1PUT COL(252) DATA(SA02/.) LENGTH(8) /* Approval provided 2PUT COL(260) DATA(SA03/.) LENGTH(8) /* Approval provided 3PUT COL(268) DATA(SA04/.) LENGTH(8) /* Approval provided 4PUT COL(276) DATA(SA05/.) LENGTH(8) /* Approval provided 5PUT COL(284) DATA(SA06/.) LENGTH(8) /* Approval provided 6PUT COL(292) DATA(SA07/.) LENGTH(8) /* Approval provided 7PUT COL(300) DATA(SA08/.) LENGTH(8) /* Approval provided 8PUT COL(308) DATA(SA09/.) LENGTH(8) /* Approval provided 9PUT COL(316) DATA(SA10/.) LENGTH(8) /* Approval provided 10PUT COL(324) DATA(SA11/.) LENGTH(8) /* Approval provided 11PUT COL(332) DATA(SA12/.) LENGTH(8) /* Approval provided 12PUT COL(340) DATA(SA13/.) LENGTH(8) /* Approval provided 13PUT COL(348) DATA(SA14/.) LENGTH(8) /* Approval provided 14PUT COL(356) DATA(SA15/.) LENGTH(8) /* Approval provided 15PUT COL(364) DATA(SA16/.) LENGTH(8) /* Approval provided 16PUT COL(372) DATA(SA17/.) LENGTH(8) /* Approval provided 17PUT COL(380) DATA(SA18/.) LENGTH(8) /* Approval provided 18PUT COL(388) DATA(SR01/.) LENGTH(8) /* Approval rejected 1PUT COL(396) DATA(SR02/.) LENGTH(8) /* Approval rejected 2PUT COL(404) DATA(SR03/.) LENGTH(8) /* Approval rejected 3PUT COL(412) DATA(SR04/.) LENGTH(8) /* Approval rejected 4PUT COL(420) DATA(SR05/.) LENGTH(8) /* Approval rejected 5PUT COL(428) DATA(SR06/.) LENGTH(8) /* Approval rejected 6PUT COL(436) DATA(SR07/.) LENGTH(8) /* Approval rejected 7PUT COL(444) DATA(SR08/.) LENGTH(8) /* Approval rejected 8PUT COL(452) DATA(SR09/.) LENGTH(8) /* Approval rejected 9PUT COL(460) DATA(SR10/.) LENGTH(8) /* Approval rejected 10PUT COL(468) DATA(SR11/.) LENGTH(8) /* Approval rejected 11PUT COL(476) DATA(SR12/.) LENGTH(8) /* Approval rejected 12PUT COL(484) DATA(SR13/.) LENGTH(8) /* Approval rejected 13PUT COL(492) DATA(SR14/.) LENGTH(8) /* Approval rejected 14PUT COL(500) DATA(SR15/.) LENGTH(8) /* Approval rejected 15PUT COL(508) DATA(SR16/.) LENGTH(8) /* Approval rejected 16PUT COL(516) DATA(SR17/.) LENGTH(8) /* Approval rejected 17PUT COL(524) DATA(SR18/.) LENGTH(8) /* Approval rejected 18PUT COL(532) DATA(STAP/.) LENGTH(8) /* Approval statusPUT COL(540) DATA(CL01/.) LENGTH(8) /* Approver class 1PUT COL(548) DATA(CL02/.) LENGTH(8) /* Approver class 2PUT COL(556) DATA(CL03/.) LENGTH(8) /* Approver class 3PUT COL(564) DATA(CL04/.) LENGTH(8) /* Approver class 4PUT COL(572) DATA(CL05/.) LENGTH(8) /* Approver class 5PUT COL(580) DATA(CL06/.) LENGTH(8) /* Approver class 6PUT COL(588) DATA(CL07/.) LENGTH(8) /* Approver class 7PUT COL(596) DATA(CL08/.) LENGTH(8) /* Approver class 8PUT COL(604) DATA(CL09/.) LENGTH(8) /* Approver class 9PUT COL(612) DATA(CL10/.) LENGTH(8) /* Approver class 10PUT COL(620) DATA(CL11/.) LENGTH(8) /* Approver class 11PUT COL(628) DATA(CL12/.) LENGTH(8) /* Approver class 12PUT COL(636) DATA(CL13/.) LENGTH(8) /* Approver class 13PUT COL(644) DATA(CL14/.) LENGTH(8) /* Approver class 14PUT COL(652) DATA(CL15/.) LENGTH(8) /* Approver class 15PUT COL(660) DATA(CL16/.) LENGTH(8) /* Approver class 16PUT COL(668) DATA(CL17/.) LENGTH(8) /* Approver class 17



PUT COL(676) DATA(CL18/.) LENGTH(8) /* Approver class 18PUT COL(684) DATA(GROA/.) LENGTH(11) /* Assignee departmentPUT COL(695) DATA(PERA/.) LENGTH(40) /* Assignee namePUT COL(735) DATA(!S0B2E) LENGTH(13) /* Assignee phonePUT COL(748) DATA(MISX/.) LENGTH(3) /* Backup plan usedPUT COL(751) DATA(RNID/.) LENGTH(8) /* Change numberPUT COL(759) DATA(CODR/.) LENGTH(8) /* Change reasonPUT COL(767) DATA(STAC/.) LENGTH(7) /* Change statusPUT COL(774) DATA(TYPE/.) LENGTH(8) /* Change typePUT COL(782) DATA(APPL/.) LENGTH(8) /* Checkout appl.IDPUT COL(790) DATA(PERR/.) LENGTH(15) /* Closed byPUT COL(805) DATA(GROR/.) LENGTH(11) /* Closer departmentPUT COL(816) DATA(!S0B2F) LENGTH(13) /* Closer phonePUT COL(829) DATA(CLAR/.) LENGTH(8) /* Closer classPUT COL(837) DATA(RNCC/.) LENGTH(44) /* Co-requisitesPUT COL(881) DATA(CODC/.) LENGTH(8) /* Completition codePUT COL(889) DATA(TIMF/.) LENGTH(5) /* Completition timePUT COL(894) DATA(GROC/.) LENGTH(11) /* Coordinator dep.PUT COL(905) DATA(PERC/.) LENGTH(15) /* Coordinator namePUT COL(920) DATA(!S0B30) LENGTH(13) /* Coordinator phonePUT COL(933) DATA(CODP/.) LENGTH(8) /* Current phasePUT COL(941) DATA(PRIO/.) LENGTH(2) /* Current priorityPUT COL(943) DATA(!S0E0F) LENGTH(45) /* DescriptionPUT COL(988) DATA(COMD/.) LENGTH(8) /* Device namePUT COL(996) DATA(CLAE/.) LENGTH(8) /* Entry classPUT COL(1004) DATA(INTE/.) LENGTH(8) /* Estimated durationPUT COL(1012) DATA(EFE/.) LENGTH(4) /* Estimated effortPUT COL(1016) DATA(GWID/.) LENGTH(9) /* Gateway IDPUT COL(1025) DATA(PRII/.) LENGTH(2) /* Initial priorityPUT COL(1027) DATA(COMK/.) LENGTH(8) /* Key item affectedPUT COL(1035) DATA(LOCC/.) LENGTH(8) /* Location codePUT COL(1043) DATA(COMN/.) LENGTH(8) /* Network namePUT COL(1051) DATA(CLAO/.) LENGTH(8) /* Owning classPUT COL(1059) DATA(TIMT/.) LENGTH(5) /* Planned end datePUT COL(1064) DATA(TIMP/.) LENGTH(5) /* Planned start timePUT COL(1069) DATA(RNCP/.) LENGTH(44) /* PrerequisitesPUT COL(1113) DATA(RNPR/.) LENGTH(8) /* Problem fixedPUT COL(1121) DATA(COMX/.) LENGTH(8) /* Program namePUT COL(1129) DATA(PERS/.) LENGTH(40) /* Requested byPUT COL(1169) DATA(GROS/.) LENGTH(11) /* Requester departmentPUT COL(1180) DATA(!S0B2D) LENGTH(13) /* Requester phonePUT COL(1193) DATA(!S0BB6) LENGTH(8) /* Reviewer class 1PUT COL(1201) DATA(!S0BB7) LENGTH(8) /* Reviewer class 2PUT COL(1209) DATA(!S0BB8) LENGTH(8) /* Reviewer class 3PUT COL(1217) DATA(!S0BB9) LENGTH(8) /* Reviewer class 4PUT COL(1225) DATA(!S0BBA) LENGTH(8) /* Reviewer class 5PUT COL(1233) DATA(!S0BBB) LENGTH(8) /* Reviewer class 6PUT COL(1241) DATA(!S0BBC) LENGTH(8) /* Reviewer class 7PUT COL(1249) DATA(!S0BBD) LENGTH(8) /* Reviewer class 8PUT COL(1257) DATA(!S0BBE) LENGTH(8) /* Reviewer class 9PUT COL(1265) DATA(!S0BBF) LENGTH(8) /* Reviewer class 10PUT COL(1273) DATA(!S0BC0) LENGTH(8) /* Reviewer class 11PUT COL(1281) DATA(!S0BC1) LENGTH(8) /* Reviewer class 12PUT COL(1289) DATA(!S0BC2) LENGTH(8) /* Reviewer class 13PUT COL(1297) DATA(!S0BC3) LENGTH(8) /* Reviewer class 14PUT COL(1305) DATA(!S0BC4) LENGTH(8) /* Reviewer class 15PUT COL(1313) DATA(!S0BC5) LENGTH(8) /* Reviewer class 16PUT COL(1321) DATA(!S0BC6) LENGTH(8) /* Reviewer class 17PUT COL(1329) DATA(!S0BC7) LENGTH(8) /* Reviewer class 18PUT COL(1337) DATA(IMPR/.) LENGTH(6) /* Risk assessmentPUT COL(1343) DATA(NASY/.) LENGTH(8) /* System namePUT COL(1351) DATA(TECID.) LENGTH(20) /* Tec event ID



Modifying collect jobThe Tivoli Information Management for z/OS (INFOMAN) component uses theDRLJCOIN job for collecting problem and change data from the Tivoli InformationManagement for z/OS database. This job performs two steps:1. Runs RFT DRLJRFT22. Runs the collect process

DRLJCOIN is a sample collect job for collecting data from the Tivoli InformationManagement for z/OS database. Figure 60 shows the DRLJCOIN job.

Before running the DRLJCOIN job:1. Change the data set names according to the naming convention of your

installation.2. Allocate a separate ISPPROF data set for step 1 of the DRLJCOIN job.3. Check your DB2 SYSTEM and SYSPREFIX names.

The DRLJCOIN job writes the log data to a temporary data set, which is deletedwhen the job completes. If you want to save the data, change the DRLJCOIN job.

Also note that as the RFT extracts data in the Tivoli Information Management forz/OS database, the DRLJCOIN job deletes the data in the INFOMAN_CHANGE_Dand INFOMAN_PROBLEM_D tables to avoid duplication of data. The DRLJCOINjob deletes the data in these tables just before running the collect step.

PUT COL(1371) DATA(TIMA/.) LENGTH(5) /* Time assignedPUT COL(1376) DATA(TIME/.) LENGTH(5) /* Time enteredPUT COL(1381) DATA(TIMM/.) LENGTH(5) /* Time last alteredPUT COL(1386) DATA(TIMD/.) LENGTH(5) /* Time requiredPUT COL(1391) DATA(CLAT/.) LENGTH(8) /* Transfer to classPUT COL(1399) DATA(MISP/.) LENGTH(3) /* Unexpected problemsPUT COL(1402) DATA(NUMX/.) LENGTH(8) /* User form numberPUT COL(1410) DATA(USER/.) LENGTH(8) /* User last altered

IF VAL(&ZICDATE) FROM(5) FOR(1) OP(=) VAL(’/’)PUT COL(1418) VAL(&ZICDATE) FROM(6) FOR(2) /* Run Date, MonthPUT COL(1420) VAL(&ZICDATE) FROM(9) FOR(2) /* DayPUT COL(1422) VAL(&ZICDATE) FROM(3) FOR(2) /* YearPUT COL(1426) VAL(&ZCTIME) /* Time of RFT run

ELSEIF VAL(&ZICDATE) FROM(3) FOR(1) OP(=) VAL(’/’)

PUT COL(1418) VAL(&ZICDATE) FROM(4) FOR(2) /* Run Date, MonthPUT COL(1420) VAL(&ZICDATE) FROM(7) FOR(2) /* DayPUT COL(1422) VAL(&ZICDATE) FROM(1) FOR(2) /* YearPUT COL(1426) VAL(&ZCTIME) /* Time of RFT run

EIFEIF

ESEARCHESECTION



//DRLJCOIN JOB (ACCT#),’INFOMAN’//***************************************************************//* *//* LICENSED MATERIALS - PROPERTY OF IBM *//* *//* 5698-B06 Copyright IBM Corporation 1992, 2007 *//* SEE COPYRIGHT INSTRUCTIONS. *//* *//***************************************************************//* *//* NAME: DRLJCOIN *//* *//* STATUS: Tivoli Decision Support for zOS 1.8.0 *//* *//* FUNCTION: EXTRACT PROBLEM AND CHANGE DATA FROM THE *//* TIVOLI SERVICE DESK DATABASE AND COLLECT IT *//* INTO THE TDSzOS DATABASE. *//* STEP 1 OF 2: RUN INFOMAN RFT DRLJRFT2 *//* STEP 2 OF 2: RUN TDSzOS COLLECT *//* *//* NOTE(S): 1. CHANGE THE DATASET NAMES ACCORDING TO THE *//* NAMING CONVENTION OF YOUR INSTALLATION. *//* 2. ALLOCATE A SEPARATE ISPPROF DATASET FOR STEP *//* 1 IN THIS JOB. *//* 3. CHECK YOUR DB2 SUBSYSTEM NAME - DEFAULT DSN *//* 4. CHECK YOUR TDSzOS PARAMETERS: *//* SYSPREFIX - DEFAULT DRLSYS *//* &PREFIX - DEFAULT DRL *//* 5. THE JOB STARTS BLGINIT WITHOUT A SESSION *//* PARAMETER WHICH MEANS THAT SESSION 00 WILL *//* BE USED. *//* IF THIS IS NOT VALID FOR YOUR INSTALLATION, *//* ADD SESS(XX) TO THE BLGINIT PARAMETERS. *//* 6. THE USER RUNNING THE JOB MUST BE IDENTIFIED *//* IN AN INFOMAN PRIVILEGE CLASS. YOU CAN SET *//* THE USER ID WITH THE COMMAND *//* PROFILE PREFIX(USERID) *//* BEFORE THE ISPSTART COMMAND. *//* 7. Change the DB2 load library name according to *//* the naming convention of your installation. *//* Default is ’db2loadlibrary’. *//* *//* Change activity: *//* 00 1993-02-03 DMA Created *//* 01 2005-03-18 DZ System Perf. feature comp. renaming *//* replace TSD with INFOMAN DCR026 *//* *//* *//* CHANGE ACTIVITY: *//* CHANGE FLAG TYPE DATE DESCRIPTION *

//* ------------------------------------------------------------*//* $D0=DCR066, TDS180,01/06/07,ADL(SM): Update TDS Version and *//* DB2 dataset names. *//* *//***************************************************************//*//************************************************//* STEP 1 OF 2: RUN INFOMAN RFT//************************************************//INFOBTCH EXEC PGM=IKJEFT01,DYNAMNBR=25//STEPLIB DD DISP=SHR,DSN=xxxx.SBLMMOD1//ISPPLIB DD DISP=SHR,DSN=xxxx.SBLMSAMP(BLGISPFD)//ISPMLIB DD DISP=SHR,DSN=SYS1.ISPMENU//ISPSLIB DD DISP=SHR,DSN=xxxx.SBLMSAMP//ISPTLIB DD DISP=SHR,DSN=xxxx.ISPTLIB// DD DISP=SHR,DSN=SYS1.ISPTENU//ISPPROF DD DISP=SHR,DSN=xxxx.USER.PROFILE(BLG0PROF)//SYSPROC DD DUMMY//RFTDD DD DISP=SHR,DSN=DRLxxx.SDRLCNTL(DRLJRFT2)//RFT2EPDM DD DSN=&&RFT2TEMP,DISP=(NEW,PASS),SPACE=(TRK,(30,10)),// UNIT=SYSDA,DCB=(RECFM=FB,LRECL=300,BLKSIZE=6000)//SYSPRINT DD SYSOUT=*//SYSTSPRT DD SYSOUT=*//SYSTSIN DD *ISPSTART PGM(BLGINIT) +

PARM(IRC(PROFILE,1,7,DDNAME,END,5,3,1,RFT2EPDM,2,999999, +END,END,9,REPORT,8,DRLJRFT2,QUIT))

LOGOFF/*//************************************************//* STEP 2 OF 2: RUN TDSzOS COLLECT//************************************************//IFRC1 IF RC=0 THEN//RUNLOG EXEC PGM=DRLPLC,PARM=(’SYSTEM=DSN’,// ’SYSPREFIX=DRLSYS,&PREFIX=DRL’)//STEPLIB DD DISP=SHR,DSN=DRLxxx.SDRLLOAD// DD DISP=SHR,DSN=db2loadlibrary//DRLOUT DD SYSOUT=*//DRLLOG DD DSN=&&RFT2TEMP,DISP=(OLD,DELETE)//DRLDUMP DD SYSOUT=*//DRLIN DD *

SQL DELETE FROM &PREFIX.INFOMAN_PROBLEM_D;SQL DELETE FROM &PREFIX.INFOMAN_CHANGE_D;SQL COMMIT;COLLECT INFOMAN

REPROCESS;

//IFRC2 ENDIF

Figure 60. DRLJCOIN job for collecting Tivoli Information Management for z/OS data


Updating lookup tablesThe Tivoli Information Management for z/OS (INFOMAN) component uses twolookup tables to provide problem resolution objectives and to standardize problemand change types.

Using the administration dialog, update these lookup tables:


INFOMAN_OBJECTIVE Defines the resolution-time objective(in days) for each problem priority.

PROBLEM_PRIORITY RESOLUTION_OBJ

INFOMAN_TYPE Standardizes problem types andchange types under which problemsand changes will be grouped.

INFOMAN_TYPE STANDARD_TYPE

For a complete description of these lookup tables and an example of their tablecontents, see INFOMAN_OBJECTIVE and INFOMAN_TYPE.

For information on using the administration dialog to update lookup tables, see"Updating lookup tables" in System Performance Feature Reference Volume I.

Data flowThe Tivoli Information Management for z/OS (INFOMAN) component collectssystem problem and change management records and stores the data in the TivoliDecision Support for z/OS database. You can then use the reporting dialog todisplay reports based on this data. The following figure shows an overview of theflow of data from the Tivoli Information Management for z/OS licensed program,through the Tivoli Information Management for z/OS (INFOMAN) component,and finally into reports.


The Tivoli Information Management for z/OS (INFOMAN) component collect job,DRLJCOIN, contains two steps. The first step runs an RFT DRLJRFT2 that extractsdata from the Tivoli Information Management for z/OS database and writes thedata to a data set, called the INFOMAN log.

The second step runs a Tivoli Decision Support for z/OS collect job, which readsthe log and collects data into the INFOMAN_CHANGE_D and

Figure 61. Tivoli Information Management for z/OS (INFOMAN) component data flow


INFOMAN_PROBLEM_D tables. Before the collect is run, Tivoli Decision Supportfor z/OS deletes the data in the two tables to avoid duplicating data.

The collect job DRLJCOIN reads the whole Tivoli Information Management forz/OS database. However, using DRLJRFT2 you can specify that you want changesand problems extracted only for a certain period. You might be extracting andcollecting some data from the Tivoli Information Management for z/OS databasethat you already have from a previous collect. To avoid duplicating data, you mustdelete the old data in the tables. What you collect into your Tivoli DecisionSupport for z/OS tables is a snapshot of how the Tivoli Information Managementfor z/OS database looks at a certain moment (when you run the job).

For information on the search criteria that you can specify in the RFT, see the TivoliInformation Management for z/OS: Data Reporting User’s Guide.

Storing the dataAfter collecting the data, the component stores the data in the Tivoli DecisionSupport for z/OS database. As it updates the tables, the Tivoli InformationManagement for z/OS (INFOMAN) component uses lookup tables to provideresolution objectives (in days) and to provide standardized problem and changetypes. The following figure shows which data tables contain values from thelookup tables.

Log and record definitionsTivoli Information Management for z/OS produces records that containinformation on the kind of problem or change occurring in the system. The TivoliInformation Management for z/OS (INFOMAN) component uses the DRLJCOINjob to extract change and problem records from the Tivoli InformationManagement for z/OS database and creates a log called INFOMAN from therecords in the database. The component processes these records:

Table 5. Input records to the Tivoli Information Management for z/OS (INFOMAN) component

Tivoli Information Management forz/OS record Record definition Description

Change records from theInformation/Management database

INFOMAN_CHANGE Contains change information indicatingany modification made within anorganization, such as equipment orsoftware additions or removals.

Figure 62. Tivoli Information Management for z/OS (INFOMAN) lookup table data


Table 5. Input records to the Tivoli Information Management for z/OS (INFOMAN) component (continued)

Tivoli Information Management forz/OS record Record definition Description

Problem records from theInformation/Management database

INFOMAN_PROBLEM Contains information indicating problemsthat may require additional assessmentand diagnosis.

Change records from the TivoliInformation Management for z/OSdatabase

TSD_CHANGE_V12 Contains change information indicatingany modification made within anorganization, such as equipment orsoftware additions or removals.

Problem records from the TivoliInformation Management for z/OSdatabase

TSD_PROBLEM_V12 Contains information indicating problemsthat may require additional assessmentand diagnosis.

Data tables and lookup tablesThis section describes the data tables and lookup tables used by the TivoliInformation Management for z/OS (INFOMAN) component. For descriptions ofcommon data tables, lookup tables, and control tables used by the SystemPerformance feature, see the Administration Guide and Reference.

Data tablesThis section describes the data tables for the Tivoli Information Management forz/OS (INFOMAN) component.

INFOMAN_CHANGE_D:INFOMAN_CHANGE_D

This table provides daily statistics on changes required or implemented on thesystem. It contains change records from the Tivoli Information Management forz/OS database, extracted by the collect job DRLJCOIN.

This table is updated by the INFOMAN_TYPE lookup table.

Note: Because no purge condition is defined, you are required to purge the tablesbefore running a collect.


DATE K DATE Date when the change was required (when status isnot CLOSED) or when the change was implemented(when status is CLOSED). From INDATD or INDATF.

GROUP_ASSIGNED K CHAR(11) Group that the change was assigned to. FromINGROA.

CHANGE_STATUS K CHAR(8) Status of the change, such as INITIAL, OPEN, andCLOSED. From INSTAC.

CHANGE_TYPE K CHAR(8) Change category, such as SOFTWARE, HARDWAREand APPL. From STANDARD_TYPE in theINFOMAN_TYPE lookup table. If no match is found,this column gets its value from INTYPE.

CHANGE_PRIORITY K CHAR(2) Current priority assigned to the change. This can be01 to 04. From INPRIO.

CHANGE_REASON K CHAR(8) Reason why the change was required or implemented.From INCODR.



BACKUP_USED_COUNT INTEGER Number of times the backup plan was used. This isthe count of times that INMISX was equal to YES.

CHANGE_DAYS FLOAT Actual number of days it took to implement thechange. This is the sum of the difference between thedate the change was started and the date the changewas closed.

CHANGE_HOURS FLOAT Actual number of hours it took to implement thechange. Calculated as the sum of (24*ININTOD +ININTOH + ININTOM/60).

CHANGES INTEGER Number of changes opened or closed. This is thecount of change records (INRNID) collected.

COLLECT_DATE DATE Date when the Tivoli Decision Support for z/OS jobDRLJCOIN was run. From INRFTDATE.

HIGH_IMPACTS INTEGER Number of changes with high impact. This is thecount of times that INIMPA was equal to HIGH.

LOW_IMPACTS INTEGER Number of changes with low impact. This is thecount of times that INIMPA was equal to LOW.

MEDIUM_IMPACTS INTEGER Number of changes with medium impact. This is thecount of times that INIMPA was equal to MEDIUM.

MONTH DATE Date when the change was required (when status isnot CLOSED) or when the change was implemented(when status is CLOSED). This is the date of the firstday of the month. From INDATD or INDATF.

PLANNED_DAYS FLOAT Number of days planned for implementing thechange. This is the sum of the difference between theplanned start date (INDATP) and the planned enddate (INDATT).

SUCCESSFUL_CHANGES INTEGER Number of successful changes implemented. This isthe count of times that INCODC was equal to OK.

UNEXPECT_PROBLEMS INTEGER Number of changes with unexpected problems. Thisis the count of times that INMISP was equal to YES.

INFOMAN_PROBLEM_D:INFOMAN_PROBLEM_D

This table provides daily statistics on problems such as hardware, software, andapplication. It contains problem records from the Tivoli Information Managementfor z/OS database, extracted by the collect job DRLJCOIN.

This table is updated by the INFOMAN_TYPE and INFOMAN_OBJECTIVE lookuptables.

Note: Because no purge condition is defined, you are required to purge the tablesbefore running a collect.


DATE K DATE Date when the problem occurred. From INDATO.

GROUP_ASSIGNED K CHAR(8) Group that the problem was assigned to. FromINGROA.

PROBLEM_STATUS K CHAR(8) Status of the problem. From INSTAC.



PROBLEM_TYPE K CHAR(8) Problem category, such as SOFTWARE, HARDWARE,and APPL. From STANDARD_TYPE in theINFOMAN_TYPE lookup table. If no match is found,this column gets its value from INTYPE.

PROBLEM_PRIORITY K CHAR(2) Current priority assigned to the problem. This can be01 to 04. From INPRIO.

PROBLEM_CAUSE K CHAR(8) Cause of the problem, such as PROGRAM,HARDWARE, and USAGE. From INCODC.

COLLECT_DATE DATE Date when the Tivoli Decision Support for z/OS jobDRLJCOIN was run. From INRFTDATE.

FIX_HOURS FLOAT Number of hours needed to fix the problem. This isthe sum of the difference between the time theproblem occurred and the time the problem wasresolved.

MONTH DATE Month when the problem occurred. This is the date ofthe first day of the month. From INDATO.

OBJECTIVE_EXCEEDS INTEGER Number of times the resolution-time objective wasexceeded. This is the count of records with fix hoursgreater than the resolution objective defined in theINFOMAN_OBJECTIVE lookup table.

PROBLEMS INTEGER Number of problems that occurred. This is the countof problem records (INDATO) collected.

REIPLS INTEGER Number of re-IPLs performed because of unexpectedproblems. This is the count of times that INIMPS wasequal to REIPL.

RERUN_HOURS INTEGER Number of hours spent to rerun applications or jobsbecause of the problems. Calculated as the sum of(24*ININTRD + ININTRH + ININTRM/60).

RESTARTS INTEGER Number of restarts required because of unexpectedproblems. This is the count of times that INIMPS wasequal to RESTART.

Lookup tablesThis section describes the lookup tables specific to the Tivoli InformationManagement for z/OS (INFOMAN) component.

INFOMAN_OBJECTIVE:INFOMAN_OBJECTIVE

This lookup table defines the resolution-time objective (in days) for each problempriority. It updates the INFOMAN_PROBLEM_D table.


PROBLEM_PRIORITY K CHAR(2) Priority for the problem. This is normally 01 to 04.

RESOLUTION_OBJ INTEGER Resolution-time objective for the problem priority.This is the number of days within which the problemshould be resolved.



PROBLEM RESOLUTIONPRIORITY OBJ-------- -----------01 702 1403 21

INFOMAN_OBJECTIVE:INFOMAN_OBJECTIVE

This lookup table defines the resolution-time objective (in days) for each problempriority. It updates the INFOMAN_PROBLEM_D table.


PROBLEM_PRIORITY K CHAR(2) Priority for the problem. This is normally 01 to 04.

RESOLUTION_OBJ INTEGER Resolution-time objective for the problem priority.This is the number of days within which the problemshould be resolved.


PROBLEM RESOLUTIONPRIORITY OBJ-------- -----------01 702 1403 21

INFOMAN_TYPE:INFOMAN_TYPE

This lookup table standardizes Tivoli Information Management for z/OS problemand change types under which problems and changes will be grouped. It updatesthe INFOMAN_PROBLEM_D and INFOMAN_CHANGE_D tables.


INFOMAN_TYPE K CHAR(8) Tivoli Information Management for z/OS problemtype or change type to be converted.

STANDARD_TYPE CHAR(8) Standardized problem type or change type to useinstead of the Tivoli Information Management forz/OS type.


INFOMAN STANDARDTYPE TYPE-------- --------SW SOFTWARESOFT SOFTWARESOFTWARE SOFTWAREHW HARDWAREHARD HARDWAREHARDWARE HARDWARE

INFOMAN_TYPE:


INFOMAN_TYPE

This lookup table standardizes Tivoli Information Management for z/OS problemand change types under which problems and changes will be grouped. It updatesthe INFOMAN_PROBLEM_D and INFOMAN_CHANGE_D tables.


INFOMAN_TYPE K CHAR(8) Tivoli Information Management for z/OS problemtype or change type to be converted.

STANDARD_TYPE CHAR(8) Standardized problem type or change type to useinstead of the Tivoli Information Management forz/OS type.


INFOMAN STANDARDTYPE TYPE-------- --------SW SOFTWARESOFT SOFTWARESOFTWARE SOFTWAREHW HARDWAREHARD HARDWAREHARDWARE HARDWARE

ReportsThe Tivoli Information Management for z/OS (INFOMAN) component providesthese reports:v Problem management reports

– INFOMAN Problem Cause, Monthly Overview report– INFOMAN Problems, Monthly Overview report– INFOMAN Problems, Daily Trend report– INFOMAN Problems Closed, Monthly Overview report– INFOMAN Problems Not Closed, Weekly Overview report

v Change management reports– INFOMAN Change Successes, Monthly Overview report– INFOMAN Changes, Monthly Overview report– INFOMAN Changes, Daily Trend report– INFOMAN Changes Closed, Monthly Overview report– INFOMAN Changes Not Closed, Weekly Overview report

v Mixed report– INFOMAN Problems and Changes, Monthly Trend report

Problem management reportsThe problem management reports show the number of problems, problem causes,and group assignments for a selected time period. These reports also show thenumber of closed problems and the time it takes to fix the problems.

INFOMAN Problem Cause, Monthly Overview report:


INFOMAN Problem Cause, Monthly Overview report

This report shows, for a selected time period, the number of problems per monthand problem cause.


Report IDINFOMAN01

Report groupTivoli Information Management for z/OS (INFOMAN) reports

SourceINFOMAN_PROBLEM_D

AttributesInfoman, Info/man, Problem, Overview, Monthly

VariablesFrom_month, To_month


MonthThe date of the first day of the month during which the problem occurred.

Problem causeThe cause of the problem, such as PROGRAM, HARDWARE, or USAGE.

ProblemsThe number of problems that occurred during the specified month.

INFOMAN Problems, Monthly Overview report:INFOMAN Problems, Monthly Overview report

This report shows, for a selected time period, the number of problems per month,problem type, and group assigned. For more information on using this report, referto the System Performance Feature Guide.


Report IDINFOMAN02



INFOMAN Problem Cause, Monthly OverviewMonth: ’2000-01-01’ to ’2000-06-01’

ProblemMonth cause Problems---------- -------- ----------2000-01-01 HARDWARE 8

PROGRAM 12

Tivoli Decision Support for z/OS Report: INFOMAN01

Figure 63. Example of an INFOMAN Problem Cause, Monthly Overview report






Problem typeThe problem category, such as SOFTWARE, HARDWARE, or APPL.

Group assignedThe group to which the problem was assigned.

ProblemsThe number of problems that occurred during the month.

INFOMAN Problems, Daily Trend report:INFOMAN Problems, Daily Trend report

This report shows, for a selected month, the number of problems per day.


Report IDINFOMAN03



AttributesInfoman, Info/man, Problem, Trend, Daily

VariablesMonth

INFOMAN Problems, Monthly OverviewMonth: ’2000-01-01’ to ’2000-06-01’

Problem GroupMonth type assigned Problems---------- -------- ----------- ----------2000-01-01 HARDWARE DEPT1 16

SOFTWARE DEPT1 20


Figure 64. Example of an INFOMAN Problems, Monthly Overview report



Day The day when the problem occurred.

ProblemsThe number of problems that occurred.

INFOMAN Problems Closed, Monthly Overview report:INFOMAN Problems Closed, Monthly Overview report

This report shows, for a selected time period, the number of closed problems andfix hours per month, problem type, and group assigned.


Report IDINFOMAN04





Figure 65. Example of an INFOMAN Problems, Daily Trend report







Fix hoursThe number of hours needed to fix the problems.

Fix hours per problemThe average number of hours needed to fix a problem. Calculated as:FIX_HOURS / PROBLEMS.

INFOMAN Problems Not Closed, Weekly Overview report:INFOMAN Problems Not Closed, Weekly Overview report

This report shows the age, in weeks, of problems that are not closed.


Report IDINFOMAN05



AttributesInfoman, Info/man, Problem, Overview, Weekly

INFOMAN Problems Closed, Monthly OverviewMonth: ’2000-01-01’ to ’2000-06-01’

Problem Group Fix hoursMonth type assigned Problems Fix hours per problem---------- -------- ----------- ---------- ---------- -----------2000-01-01 HARDWARE DEPT1 10 30 3

DEPT2 5 20 4SOFTWARE DEPT1 7 21 3

DEPT2 5 10 2


Figure 66. Example of an INFOMAN Problems Closed, Monthly Overview report




Problem priorityThe current problem priority in a range from 01 to 04.


Weeks old problemsThe number of problems with an age of n weeks. Calculated as:(COLLECT_DATE - DATE) / 7.

Total problemsThe total number of problems that have not been closed.

Change management reportsThe change management reports show the number of changes, successful changes,and group assignment for a selected time period. The reports also show thenumber of closed changes and the time spent implementing a change.

INFOMAN Change Successes, Monthly Overview report:INFOMAN Change Successes, Monthly Overview report

This report shows, for a selected time period, the number of changes andsuccessful changes, per month and group assigned.


Report IDINFOMAN06


SourceINFOMAN_CHANGE_D

AttributesInfoman, Info/man, Change, Overview, Monthly


INFOMAN Problems Not Closed, Weekly Overview

|<--- Weeks old --->|<-- 0 --> <-- 2 --> < TOTAL >

Problem Problem Group |type priority assigned | Problems Problems Problems

-------- -------- -----------| -------- -------- --------HARDWARE 03 DEPT2 | 2 1 3

04 DEPT1 | 1 1 2SOFTWARE 02 DEPT2 | 1 1 2

| ======== ======== ========| 4 3 7


Figure 67. Example of an INFOMAN Problems Not Closed, Weekly Overview report



MonthThe date of the first day of the month when the change was required(when status is not CLOSED) or when the change was implemented (whenstatus is CLOSED).

Group assignedThe group to which the change was assigned.

ChangesThe number of changes opened or closed.

Successful changes (%)The percentage of successful changes implemented. Calculated as: 100 *SUCCESSFUL_CHANGES / CHANGES.

INFOMAN Changes, Monthly Overview report:INFOMAN Changes, Monthly Overview report

This report shows, for a selected time period, the number of changes per month,change type, and group assigned.


Report IDINFOMAN07





INFOMAN Change Successes, Monthly OverviewMonth: ’2000-01-01’ to ’2000-06-01’

Group SuccessfulMonth assigned Changes changes (%)---------- ----------- ---------- -----------2000-01-01 DEPT11 4 100

DEPT12 3 100


Figure 68. Example of an INFOMAN Change Successes, Monthly Overview report




Change typeThe change category, such as SOFTWARE, HARDWARE or APPL.



INFOMAN Changes, Daily Trend report:INFOMAN Changes, Daily Trend report

This graphic report shows, for a selected month, the number of changes per day.


Report IDINFOMAN08



AttributesInfoman, Info/man, Change, Trend, Daily

VariablesMonth

INFOMAN Changes, Monthly OverviewMonth: ’2000-01-01’ to ’2000-06-01’

Change GroupMonth type assigned Changes---------- -------- ----------- ----------2000-01-01 HARDWARE DEPT1 3

DEPT2 1SOFTWARE DEPT1 1


Figure 69. Example of an INFOMAN Changes, Monthly Overview report



Day The day when the change was required (when status is not CLOSED) orwhen the change was implemented (when status is CLOSED).


INFOMAN Changes Closed, Monthly Overview report:INFOMAN Changes Closed, Monthly Overview report

This report shows, for a selected time period, the number of closed changes andchange hours per month, change type, and group assigned. For more informationon using this report, refer to the System Performance Feature Guide.


Report IDINFOMAN09



Figure 70. Example of an INFOMAN changes, Daily Trend report






Change typeThe change category, such as SOFTWARE, HARDWARE, or APPL.


ChangesThe number of successful changes implemented.

Change hoursThe actual number of hours it took to implement the changes.

Change hours per changeThe average actual hours it took to implement a change. Calculated as:CHANGE_HOURS / CHANGES.

INFOMAN Changes Not Closed, Weekly Overview report:INFOMAN Changes Not Closed, Weekly Overview report

This report shows, for changes that are not closed, the weeks left before a changeis required.


Report IDINFOMAN10



AttributesInfoman, Info/man, Change, Overview, Weekly

INFOMAN Changes Closed, Monthly OverviewMonth: ’2000-01-01’ to ’2000-06-01’

Change Group Change Change hoursMonth type assigned Changes hours per change---------- -------- ----------- ---------- ---------- ------------2000-01-01 HARDWARE DEPT1 3 21 72000-02-01 HARDWARE DEPT1 2 10 5


Figure 71. Example of an INFOMAN Changes Closed, Monthly Overview report



Change typeThe change category, such as SOFTWARE, HARDWARE, or APPL.


Weeks leftThe weeks left before a change is required. Calculated as: (DATE -COLLECT_DATE) / 7.


Mixed reportsThese reports show a combination of changes and problems for a selected timeperiod.

INFOMAN Problems and Changes, Monthly Trend report:INFOMAN Problems and Changes, Monthly Trend report

This report shows, for a selected time period, the number of changes and problemsper month. For more information on using this report, refer to the SystemPerformance Feature Guide.


Report IDINFOMAN11


SourceINFOMAN_PROBLEM_D, INFOMAN_CHANGE_D

AttributesInfoman, Info/man, Change, Problem, Trend, Monthly


INFOMAN Changes Not Closed, Weekly Overview

|<--------- Weeks left --------->|<-- 1 ---> <-- 2 ---> <-- 3 ---> < TOTAL ->

Change Group |type assigned | Changes Changes Changes Changes-------- -----------| ------- ------- ------- -------HARDWARE DEPT1 | 1 1 1 3

DEPT2 | 1 1SOFTWARE DEPT1 | 1 1

| ======= ======= ======= =======| 3 1 1 5


Figure 72. Example of an INFOMAN Changes Not Closed, Weekly Overview report



Month start dateFor problems, the date of the first day of the month when the problemoccurred. For changes, the date of the first day of the month when thechange was required (status is not CLOSED) or when the change wasfinished (status is CLOSED).



IXFP componentCustomizationv IXFP data

Data tablesv IXFP_CHANNEL_H, _D, _Mv IXFP_DDSR_H, _D, _Mv IXFP_DEVICE_H, _D, _M

Figure 73. Example of an INFOMAN Problems and Changes, Monthly Trend report


v IXFP_DRIVE_H, _D, _Mv IXFP_SNAPSHOT_Hv IXFP_SPACE_Hv IXFP_SUBSYSTEM_H, _D, _M

Reportsv IXFP Channel Interface Statistic, Overview reportv IXFP Device Performance per Device ID reportv IXFP Device Performance per VOLSER reportv IXFP Device Utilization, Hourly Trend reportv IXFP Device DASD/Cache Transfer, Daily Trend reportv IXFP Device Performance, Hourly Trend reportv IXFP Device Utilization, Monthly Trend reportv IXFP Drive Utilization, Hourly Trend reportv IXFP Drive Utilization, Daily Trend reportv IXFP Deleted Data Space Release, Daily Trend reportv IXFP Subsystem Space Utilization, Daily Trend reportv IXFP Subsystem Information, Daily Trend reportv IXFP Space Utilization, Hourly Trend report

CustomizationIXFP is the host software that helps you manage the IBM RAMAC® Virtual ArrayStorage. IXFP is a set of utility programs that 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, and about the cacheeffectiveness of certain non-RVA subsystems.

XSA/Reporter is the part of the IXFP that collects data from your RAMAC VirtualArray subsystems and produces reports based upon that data. XSA/Reporter alsoprovides Cache Effectiveness reports for subsystems attached to controllers that arecompatible with the IBM 3390.

For further information about IXFP, refer to:v IXFP Installation for MVS, SC26-7179v IXFP Configuration and Administration, SC26-7178v IXFP Subsystem Reporting, SC26-7184

IXFP dataThe records written in the XSA/Reporter data collection file can be directed toSMF or to a user-managed file. In each instance, a standard header precedes theXSA/Reporter data portion of the record, although it is mainly binary zeros ifoutput is not directed to SMF.

The five XSA/Reporter data collection record subtypes are:v Subtype 1: Subsystem Performancev Subtype 2: Channel Interface Statisticsv Subtype 3: Functional Device Performancev Subtype 4: Drive Module Performancev Subtype 7: Space Utilization.


The other three IXFP SMF record subtypes are:v Subtype 5: Deleted Data Space Release (DDSR) datav Subtypes 6 and 8: SnapShot event data.

To enable SMF to collect IXFP data, you must identify the SMF record type andsubtype for IXFP in the SMFPRMxx member of SYS1.PARMLIB. An example of anSMFPRMxx member, where 250 is the record type selected for IXFP data, andXSA/Reporter, DDSR and space utilization are to be written, is as follows:SYS(TYPE(0:104, 250))SUBSYS(STC,TYPE(0:55, 08:104, 250))SUBPARM(IXFP(250, 2, 5, 7))

By default, Tivoli Decision Support for z/OS assumes that the SMF type for IXFPdata is 250. If you want to change the value, you have to manually modify therecord definitions (DRLRIXFP member) in the IDENTIFIED BY clause(IDENTIFIED BY SMFFARTY = 250 must be changed to IDENTIFIED BYSMFFARTY = xxx, where xxx is the value you require).

Data tablesThis chapter describes the data tables used by the IXFP component. Fordescriptions of common data tables, lookup tables, and control tables used by theIXFP component, refer to the Administration Guide and Reference.

IXFP_CHANNEL_H, _D, _MThese tables provide hourly, daily, and monthly statistics about the IXFP channelinterface based on data from SMF type 50, subtype 2 records.


IXFP_CHANNEL_H10 days

IXFP_CHANNEL_D60 days

IXFP_CHANNEL_M365 days


DATE K DATE Date when the record was written to SMF. FromSMFFADTE.

TIME K TIME Time (rounded down to the nearest hour) when therecord was written to SMF. It applies only to the _Htable. From SMFFATME.

PERIOD_NAME K CHAR(8) Name of the period. This is derived using fieldsSMFFASID, SMFFADTE, and SMFFATME from therecord as parameters in the PERIOD function.

MVS_SYSTEM_ID K CHAR(4) MVS system ID. From SMFFASID.

PARTITION K CHAR(1) The partitions that are active during this collectioninterval. From activPrt.

SUBSYSTEM_ID K CHAR(4) MVS subsystem ID. From SMFFASSI.

CHANNEL_INT_ID K CHAR(1) The channel interface identifier. From intfld.

CHANNEL_INT_NAME CHAR(8) The channel interface identifier. From intName.



CHANNEL_SPEED INTEGER The channel speed (megabytes per second: 3.0, 4.5, or20.0). From chanSped.

DURATION_TIME FLOAT Interval duration time for the subsystem, in seconds.Calculated as the sum of duraTime/1000.

NUMBER_IO FLOAT The number of I/Os. Calculated as the sum ofnumberIo.

SUBSYSTEM_NAME CHAR(8) The name of the MVS subsystem. From subsysName.

TCU_BUSY FLOAT The time control unit busy at channel (in seconds).Calculated as the sum of tiCoBuCh/1000.

IXFP_DDSR_H, _D, _MThese tables provide hourly, daily, and monthly data about IXFP Deleted DataSpace Release (DDSR) based on data from SMF type 50, subtype 5 records.


IXFP_DDSR_H10 days

IXFP_DDSR_D60 days

IXFP_DDSR_M365 days







DEVICE_ADDRESS K CHAR(4) The device address on which space was released.From DEVNUM.

VOLUME_ID K CHAR(6) The volume ID on which space was released. FromVOLID.

RAMAC_FD_ID K CHAR(4) The RAMAC Virtual Array functional device ID. FromFDID.

RAMAC_SSYS_NAME K CHAR(8) The RAMAC Virtual Array subsystem name thatowns the device. From SUBSYS.

RAMAC_SSYS_ID K CHAR(4) The RAMAC Virtual Array subsystem ID. From SSID.

CHANNEL_UA_ID K CHAR(4) The channel unit address ID. From IDID

IO_TIME INTEGER The I/O time for space release, in seconds. Calculatedas the sum of IOTIME.


IXFP_DEVICE_H, _D, _MThese tables provide hourly, daily, and monthly data about IXFP functional deviceperformance based on data from SMF type 50, subtype 3 records.


IXFP_DEVICE_H10 days

IXFP_DEVICE_D60 days

IXFP_DEVICE_M365 days








DEVICE_ID K CHAR(4) The functional device identifier (0-1023). From vdid.

BYP_CACHE_REQ FLOAT Bypass cache requests. Calculated as the sum ofbypCaReq.

BYTES_PER_TRACK FLOAT Bytes per track. From byteTrak.

CACHE_DASD_TR FLOAT Cache to DASD (stages). Calculated as the sum ofcaDasdXf.

CACHE_FW_HITS FLOAT Cache Fast Write hits. Calculated as the sum ofwrCFWhit.

CACHE_FW_REQS FLOAT Cache Fast Write requests. Calculated as the sum ofwrCFWreq.

CACHE_OCCUPANCY FLOAT Cache occupancy (track seconds). Calculated as thesum of caTrkSec/1000.

DASD_CACHE_TR FLOAT DASD to cache transfers (stages). Calculated as thesum of caXfrStg.

DASD_FW_HITS FLOAT DASD Fast Write normal hits. Calculated as the sumof dfwNorHt.

DASD_FW_NORM FLOAT DASD Fast Write normal write requests. Calculated asthe sum of dfwNorWr.

DASD_FW_NVS FLOAT DASD Fast Write NVS constraint count. Calculated asthe sum of dfwNVSct.

DASD_FW_SEQ FLOAT DASD Fast Write sequential write requests. Calculatedas the sum of dfwSeqWr.

DASD_FW_SEQ_HITS FLOAT DASD Fast Write sequential hits. Calculated as thesum of dfwSeqHt.



DEV_NAME CHAR(8) Device name. From vDevName.

DEVICE_ADDRESS CHAR(4) Device address as known to the SCP. From devNum.

DEVICE_AVAIL_TIME FLOAT Device available time (in seconds). Calculated as thesum of availTim/1000.

DEVICE_CONN_TIME FLOAT Device connect time (in seconds). Calculated as thesum of connTime/1000.

DEVICE_UTIL_TIME FLOAT Device utilization time (in seconds). Calculated as thesum of devUtlTi/1000.


FRAME_DEALL_COUNT FLOAT Frame deallocation count. Calculated as the sum offrDealCt.

FRONT_END_READ FLOAT Count of front-end bytes that were transferred forread operations. Calculated as the sum of feBytXfR.

FRONT_END_WRITE FLOAT Count of front-end bytes that were transferred forwrite operations. Calculated as the sum of feBytXfR.

ICEBERG CHAR(1) This is an Iceberg device. From iceberg.

INH_CACHE_LOAD_REQ FLOAT Inhibit cache loading requests. Calculated as the sumof inhCaLrq.

IO_OPERATION FLOAT Number of I/O operations (number of end-of-chainevents). Calculated as the sum of devActiv.

LOW_REF_COUNT FLOAT Low reference count. Calculated as the sum oflowrfCnt.

LOW_REF_COUNT_LRU FLOAT Low reference count due to LRU. Calculated as thesum of lowRfLRU.

PART_MEMB CHAR(1) Partition membership. From partMemb.

PRIM_CAPACITY FLOAT Primary capacity in cylinders. From primCapa.

READ_REQS FLOAT Total read request count. Calculated as the sum ofreadReqs.

SEQ_ACC_READ_REQ FLOAT Sequential-detected sequential access read requests.Calculated as the sum of seqIntAc.

SEQ_DASD_CACHE_TR FLOAT Sequential DASD to cache transfers (stages).Calculated as the sum of caSeqXfr.

SREAD_CACHE_FW_R FLOAT Search or read Cache Fast Write requests. Calculatedas the sum of rdCFWreq.

SREAD_CACHE_FW_W FLOAT Search or read Cache Fast Write hits. Calculated asthe sum of rdCFWhit.

SREAD_HITS FLOAT Search or read normal hits. Calculated as the sum ofrdNorHit.

SREAD_REQS FLOAT Search or read normal request count. Calculated asthe sum of rdNorReq.

SREAD_SEQ_HITS FLOAT Search or read sequential hits. Calculated as the sumof rdSeqHt.

SREAD_SEQ_REQS FLOAT Search or read sequential request count. Calculated asthe sum of dSeqReq.

SUBSYSTEM_NAME CHAR(8) The name of the MVS subsystem. From subsysName.

TRACKS_PER_CYL FLOAT Tracks per cylinder. From trackCyl.



VOLSER CHAR(6) Volume serial number. From volSer.

WRITE_NORM_REQS FLOAT Write normal requests. Calculated as the sum ofwrNorReq.

WRITE_REQS FLOAT Total write request count. Calculated as the sum ofwritReqs.

IXFP_DRIVE_H, _D, _MThese tables provide hourly, daily, and monthly data about IXFP drive moduleperformance based on data from SMF type 50, subtype 4 records.


IXFP_DRIVE_H10 days

IXFP_DRIVE_D60 days

IXFP_DRIVE_M365 days








SUBSYSTEM_NAME K CHAR(8) The name of the MVS subsystem. From subsysName.

PART_MEMB K CHAR(1) Partition membership. From partMemb.

UNIT K CHAR(2) The unit. From unit.

TRAY K CHAR(2) The tray. From tray.

SLOT K CHAR(2) The slot. From slot.

BUSY_TIME FLOAT Busy time for the drive module, in seconds.Calculated as the sum of busyTime/1000.

DURATION_TIME FLOAT Interval duration time for the drive module, inseconds. Calculated as the sum of drvMdTim/1000.

READ_BYTES_TR FLOAT Bytes that were transferred during read operations.Calculated as the sum of readByts.

WRITE_BYTES_TR FLOAT Bytes that were transferred during write operations.Calculated as the sum of wrteByts.


IXFP_SNAPSHOT_HThis table provides hourly data about IXFP SnapShot Events based on data fromSMF type 50, subtype 6 records.




TIME K TIME Time (rounded down to the nearest hour) when therecord was written to SMF. From SMFFATME.




SOURCE_DATASET_ID CHAR(44) The source data set ID. From SRCDSN.

SOURCE_VOLUME_ID CHAR(6) The source volume ID. From SRCVOL.

TARGET_DATASET_ID CHAR(44) The target data set ID. From TRGDSN.

TARGET_VOLUME_ID CHAR(6) The target volume ID. From TRGVOL.

IXFP_SPACE_HThis table provides hourly data about IXFP Space Utilization based on data fromSMF type 50, subtype 7 records.




TIME K TIME Time (rounded down to the nearest hour) when therecord was written to SMF. From SMFFATME.



VDEVNAME K CHAR(9) The name of the functional device. From vDevName.

DEVNUM K CHAR(5) The device address. From devNum.

VOLSER K CHAR(9) The volume serial number. From volSer.

TOTFLAG K SMALLINT The totals record flag. From totflag.

BACKSTOR CHAR(1) If PhCapUse = 0.0 but the value is greater than zerobefore rounding, an asterisk (*) is appended to thePHYS CAP USE field. From backstor.

BEBYTEXT FLOAT The number of back-end bytes. From beByExt.

BEBYTSHR FLOAT The number of shared back-end bytes. From beBytShr.

BEBYTUNQ FLOAT The number of unique back-end bytes. FrombeBytUnq.

BYTETRAK FLOAT The bytes per track. From byteTrak.

CAPNTSTR FLOAT The functional capacity that was not stored. Fromcapntstr.



CAPSTORD FLOAT The capacity that was stored. From capstord, countedas (noTrMapd*byteTrak).

CMPRAT FLOAT The compress ratio. From cmprat.

DATETIME CHAR(25) The date and time that the record was produced.From datetime.

ERRFLAG CHAR(2) The device error flag. If there is a device error,ALLOC fields in the report are changed to V-EER.From errflag.

FALLOC FLOAT The functional capacity that was allocated, inmegabytes. From falloc.

FCAPCITY FLOAT The functional capacity in megabytes. From fcapcity.

FDEVCNT INTEGER The number of functional devices. From fDevCnt.

FNCTCAP FLOAT The functional capacity. From fnctcap, counted as(primCapa*trackCyl*byteTrak).

FNOTSTOR FLOAT The functional capacity that was not stored, inmegabytes. From fnotstor.

FREBECPP FLOAT The free back-end capacity (Production partition).From freBeCpP.

FREBECPT FLOAT The free back-end capacity (Test partition). FromfreBeCpT.

FREBESCP FLOAT The free back-end space that was collected(Production partition). From freBeScP.

FREBESCT FLOAT The free back-end space that was collected (Testpartition). From freBeScT.

FSPCCOLB FLOAT The percentage collected free space (both partitions).From fspccolb.

FSPCCOLP FLOAT The percentage collected free space (Productionpartition). From fspccolp.

FSPCCOLT FLOAT The percentage collected free space (Test partition).From fspccolt.

FSPCUNCB FLOAT The percentage uncollected free space (bothpartitions). From fspcuncb.

FSPCUNCP FLOAT The percentage uncollected free space (Productionpartition). From fspcuncp.

FSPCUNCT FLOAT The percentage uncollected free space (Test partition).From fspcunct.

FSTORED FLOAT The functional capacity that was stored, in megabytes.From fstored.

NCAPLDPB FLOAT The percentage net capacity load (both partitions).From ncapldpb.

NCAPLDPP FLOAT The percentage net capacity load (Productionpartition). From ncapldpp.

NCAPLDPT FLOAT The percentage net capacity load (Test partition).From ncapldpt.

NOTRMAPD FLOAT The number of mapped tracks. From noTrMapd.

NOTRMAPU FLOAT The number of unique tracks that were mapped. FromnoTrMapu.



OFFFLAG CHAR(2) The offline flag. If an asterisk is displayed betweenthe VOLSER and T/P (PARTMEMB) columns in thereport, the volume is offline. From offlag.

PALLOC FLOAT The percentage of functional capacity that wasallocated. From palloc.

PARTMEMB CHAR(2) T/P: Partition membership. From partMemb.

PFUCPNOP FLOAT The percentage functional capacity that was notstored, in megabytes (Production partition). FrompFuCpNoP.

PFUCPNOB FLOAT The percentage functional capacity that was notstored, in megabytes (both partitions). FrompFuCpNoB.

PFUCPNOT FLOAT The percentage functional capacity not stored (in MB)-Test partition. From pFuC.

PFUCPSTB FLOAT The percentage functional capacity that was stored, inmegabytes (both partitions). From pFuCpStB.

PFUCPSTP FLOAT The percentage functional capacity that was stored, inmegabytes (Production partition). From pFuCpStP.

PFUCPSTT FLOAT The percentage functional capacity that was stored, inmegabytes (Test partition). From pFuCpStT.

PHCAPUSE FLOAT The physical capacity that was used, in megabytes.From PhCapUse.

PHCAPUSS FLOAT The shared physical capacity that was used, inmegabytes. From PhCapUsS.

PHCAPUSU FLOAT The unique physical capacity that was used, inmegabytes. From PhCapUsU.

PNOTSTOR FLOAT The percentage of functional capacity that was notstored. From pnotstor.

PRIMCAPA INTEGER The primary capacity in cylinders. From primCapa.

PSTORED FLOAT The percentage of functional capacity that was stored.From pstored.

SPALLOC FLOAT The allocated space (MVS only). From spAlloc.

SUBSNAME CHAR(9) The subsystem name. From subSName.

TBAKSTOB CHAR(1) The flag (in the report, an asterisk (*) to the right ofthe PHYS CAP USED column) to indicate that thephysical capacity of the disk array that was used isgreater than 1.0 (both partitions). From tBakStoB.

TBAKSTOP CHAR(1) The flag (in the report, an asterisk (*) to the right ofthe PHYS CAP USED column) to indicate that thephysical capacity of the disk array that was used isgreater than 1.0 (Production partition). From tBakStoP.

TBAKSTOT CHAR(1) The flag (in the report, an asterisk (*) to the right ofthe PHYS CAP USED column) to indicate that thephysical capacity of the disk array that was used isgreater than 1.0 (Test partition). From tBakStoT.

TCMPRATB FLOAT The compression ratio of disk array (both partitions).From tCmpRatB.

TCMPRATP FLOAT The compression ratio of disk array (Productionpartition). From tCmpRatP.



TCMPRATT FLOAT The compression ratio of disk array (Test partition).From tCmpRatT.

TDEVCNTB INTEGER The total number of functional devices (bothpartitions). From tDevCntB.

TDEVCNTP INTEGER The total number of functional devices (Productionpartition). From tDevCntP.

TDEVCNTT INTEGER The total number of functional devices (Testpartition). From tDevCntT.

TFUNCAPP FLOAT The total functional capacity, in megabytes(Production partition). From tFunCapP.

TFUNCAPT FLOAT The total functional capacity, in megabytes (Testpartition). From tFunCapT.

TFUNCAPB FLOAT The total functional capacity, in megabytes (bothpartitions). From tFunCapB.

TFUCPSTT FLOAT The total functional capacity that was stored, inmegabytes (Production partition). From tFuCpStP.

TFUCPSTP FLOAT The total functional capacity that was stored, inmegabytes (Test partition). From tFuCpStT.

TFUCPSTB FLOAT The total functional capacity that was stored, inmegabytes (both partitions). From tFuCpStB.

TFUCPNOT FLOAT The total functional capacity that was not stored, inmegabytes (Production partition). From tFuCpNoP.

TFUCPNOP FLOAT The total functional capacity that was not stored, inmegabytes (Test partition). From tFuCpNoT.

TFUCPNOB FLOAT The total functional capacity that was not stored, inmegabytes (both partitions). From tFuCpNoB.

TOTBECPP FLOAT The total back-end capacity (Production partition).From totBeCpP.

TOTBECPT FLOAT The total back-end capacity (Test partition). FromtotBeCpT.

TOTLPCAP FLOAT The capacity of disk array, in megabytes. Fromtotlpcap.

TPHCPSRB FLOAT The total shared physical capacity that was used (bothpartitions). From tPhCpSrB.

TPHCPSRP FLOAT The total shared physical capacity that was used(Production partition). From tPhCpSrP.

TPHCPSRT FLOAT The total shared physical capacity that was used (Testpartition). From tPhCpSrT.

TPHCPUNB FLOAT The total unique physical capacity that was used(both partitions). From tPhCpUnB.

TPHCPUNP FLOAT The total unique physical capacity that was used(Production partition). From tPhCpUnP.

TPHCPUNT FLOAT The total unique physical capacity that was used (Testpartition). From tPhCpUnT.

TPHCPUSP FLOAT The total physical capacity of disk array that wasused (Production partition). From tPhCpUsP.

TPHCPUST FLOAT The total physical capacity of disk array that wasused (Test partition). From tPhCpUsT.



TPHCPUSB FLOAT The total physical capacity of disk array that wasused (both partitions). From tPhCpUsB.

TRACKCYL INTEGER The tracks per cylinder. From trackCyl.

VDEVTYPE CHAR(7) The type of virtual device. From vDevType.

IXFP_SUBSYSTEM_H, _D, _MThese tables provide hourly, daily, and monthly data about IXFP subsystemperformance based on data from SMF type 50, subtype 1 records.


IXFP_SUBSYSTEM_H10 days

IXFP_SUBSYSTEM_D60 days

IXFP_SUBSYSTEM_M365 days








SUBSYSTEM_NAME K CHAR(8) The name of the MVS subsystem. From subsysName.


CACHE_SIZE FLOAT The cache size in megabytes. Calculated as the sum ofcustCach.

E_C_BYP_NO_B_SP FLOAT Number of ECAM channel programs that werebypassed because no buffer space was available.Calculated as the sum of ecamNspc.

E_C_BYP_NO_CONF FLOAT Number of ECAM channel programs that werebypassed because no configuration was busy.Calculated as the sum of ecamCfBs.

ECAM_CHAN_PGMS FLOAT Number of ECAM channel programs. Calculated asthe sum of ecamPgms.

ECAM_MSGS FLOAT Count of ECAM messages that were processed.Calculated as the sum of ecamMsgs.

FREE_BE_CAP_PROD FLOAT Free back-end capacity in the Production partition (inbytes). The value includes the capacity reserved forstandard volumes. Calculated as the sum of freBeCpP.



FREE_BE_CAP_TEST FLOAT Free back-end capacity in the Test partition (in bytes).The value includes the capacity reserved for standardvolumes. Calculated as the sum of freBeCpT.

FREE_BE_SPACE FLOAT Free back-end space that was collected. From freBeSct.

FREE_BE_SPACE_PROD FLOAT Free back-end space that was collected in theProduction partition. From freBeScp.

NVS_SIZE FLOAT The NVS size in megabytes. Calculated as the sum ofnvsSize.

OFFLINE_CACHE FLOAT The offline cache in bytes. Calculated as the sum ofoffCach.

PINNED_CACHE FLOAT The pinned cache in bytes. Calculated as the sum ofpindCach.

STD_CAPACITY FLOAT Standard capacity that was defined. From stnDefd.

TOT_BE_CAP_PROD FLOAT Total back-end capacity of the Production partition (inbytes). Calculated as the sum of totBeCpP.

TOT_BE_CAP_TEST FLOAT Total back-end capacity of the Test partition (in bytes).Calculated as the sum of totBeCpT.

TOT_FREE_SP_TEST FLOAT Total amount of free space that was collected in theTest partition. Calculated as the sum of fSpcColT.

TOT_FREE_SP_PROD FLOAT Total amount of free space that was collected in theProduction partition. Calculated as the sum offSpcColP.

TOT_READ_PROD FLOAT Total number of bytes read for free space collection inthe Production partition. Calculated as the sum offSpcBtRP.

TOT_READ_TEST FLOAT Total number of bytes read for free space collection inthe Test partition. Calculated as the sum of fSpcBtRT.

ReportsThis chapter describes the reports provided with the IXFP component.

IXFP Channel Interface Statistic, Overview reportThis report shows an overview of statistics information for IXFP channel interfaces.


Report ID:IXFPC01

Report group:IXFP Reports

Source:IXFP_CHANNEL_D

Attributes:IXFP, Channel, Statistic, Daily

Variables:From_Date, To_Date, MVS_system_ID, Subsystem_name



Date The date of the measurement.

Time The time of the measurement.

IXFP Channel Interface Statistic, OverviewFrom date: ’2003-11-14’ To date: ’2003-11-14’

MVSsystem Subsystem

Date Time ID name Partition---------- -------- ------ ---------- ----------2003-11-14 17.00.00 IXA1 RVA00 Production

Channel Channel TCU No of Durationint int busy No of I/O Channel timeID name (min) I/O (sec) speed (min)------- -------- -------- -------- -------- -------- --------A ABC00000 8 206327 229 20.0 15C 8 211086 235 20.0 15I 8 206218 229 20.0 15K 8 211357 235 20.0 15

-------- -------- -------- -------- --------* 8 208747 232 20.0 15

18.00.00

A ABC00000 5 136246 151 20.0 15C 5 143217 159 20.0 15I 5 136119 151 20.0 15K 5 143302 159 20.0 15

-------- -------- -------- -------- --------* 5 139721 155 20.0 15

19.00.00

A ABC00000 7 200273 223 20.0 15C 7 207449 231 20.0 15I 7 200562 223 20.0 15K 7 207076 230 20.0 15

-------- -------- -------- -------- --------* 7 203840 227 20.0 15

-------- -------- -------- -------- --------* 72 1440969 1601 20.0 15

-------- -------- -------- -------- --------** 21 313567 348 20.0 15

-------- -------- -------- -------- --------*** 21 313567 348 20.0 15

-------- -------- -------- -------- --------**** 21 313567 348 20.0 15

-------- -------- -------- -------- --------***** 21 313567 348 20.0 15

======== ======== ======== ======== ========21 313567 348 20.0 15

Tivoli Decision Support for z/OS Report: IXFPC01

Figure 74. Example of part of an IXFP Channel Interface Statistic, Overview report


MVS system IDThe MVS system ID.

Subsystem nameThe MVS subsystem name.

PartitionThe partition (or partitions) active during the measurement. This can beProduction, Test, or Both.

Channel int IDThe channel interface ID.

Channel int nameThe channel interface name.

TCU busy (min)The average time that the control unit was busy at the channel, in minutes.

No of I/OThe average number of I/Os.

No of I/O (sec)The average number of I/Os per second.

Channel speedThe average channel speed.

Duration time (min)The interval duration time for the subsystem, in minutes.

IXFP Device Performance per Device ID reportThis report shows IXFP functional device performance, on an hourly basis,grouped by Device ID.


Report ID:IXFPD01


Source:IXFP_DEVICE_H

Attributes:IXFP, Device, Performance, ID, Hourly



IXFP Device Performance, by Device IDFrom date: ’2003-11-14’ To date: ’2003-11-14’

MVSsystem Subsystem Dev Dev Tot read

Date Time ID name ID addr Volser Partition reqs---------- -------- ------ --------- ------ ------ ------ ---------- --------------2003-11-14 17.00.00 IXA1 RVA00 00AA 02AA R93171 Production 3851

00AB 02AB WKPRD1 1546900AC 02AC WKPRD2 1558800AD 02AD R93174 385800A8 02A8 R93169 376800A9 02A9 R93170 166310098 0298 O003B1 37650099 0299 O003B2 3765

--------------* 704951

18.00.00 00AA 02AA R93171 8700AB 02AB WKPRD1 2341300AC 02AC WKPRD2 22190

Tot write Front-end Front-end Search/read Search/readreqs I/O opers reads writes reqs hits

------------- ------------- ------------- ------------- ------------- -------------0 4024 857896 0 97 95

4715 18624 54194891 38534486 10823 107774975 18550 60294999 44139536 11088 10993

0 3959 987712 0 104 101

0 3869 536500 0 14 125 16814 17750157 400 10065 100410 3868 536080 0 11 90 3868 536080 0 11 9

------------ ------------- ------------- ------------- ------------- -------------81564 834971 4199652980 1147103020 215633 214333

0 299 360448 0 87 848874 30731 51786084 17909422 21844 218449599 30011 44104636 16827528 20444 20444

Write DASD FW Search/read Search/read Write seq DASD FWreqs hits seq.reqs seq.hits reqs seq.hits

------------- ------------- ------------- ------------- ------------- -------------0 0 3754 3754 0 0

4030 4029 4646 4646 685 6854344 4344 4500 4500 631 631

0 0 3754 3754 0 0

0 0 3754 3754 0 00 0 6566 6557 5 50 0 3754 3754 0 00 0 3754 3754 0 0

------------- ------------- ------------- ------------- ------------- -------------73269 73114 489318 489198 8295 8291

0 0 0 0 0 08019 8019 1569 1569 855 8558596 8596 1746 1746 1003 1003

Tivoli Decision Support for z/OS Report: IXFPD01

Figure 75. Example of part of an IXFP Device Performance per Device ID report







Dev IDThe functional device ID.

Dev AddrThe device address as known to the lost SCP.

Volser The volume serial number.


Tot read ReqsThe total count of read requests.

Tot write ReqsThe total count of write requests.

I/O opersThe number of I/O operations.

Front-end readsThe total count of front-end bytes transferred during read operations.

Front-end writesThe total count of front-end bytes transferred during write operations.

Search/read reqsThe total count of search or read normal requests.

Search/read hitsThe total count of search or read normal hits.

Write reqsThe total count of write normal requests.

DASD FW hitsThe total count of DASD fast-write normal hits.

Search/read seq. reqsThe total count of search or read sequential requests.

Search/read seq. hitsThe total count of search or read sequential hits.

Write seq. reqsThe total count of write sequential requests.

DASD FW seq. hitsThe total count of DASD fast-write sequential hits.

IXFP Device Performance per VOLSER reportThis report shows IXFP functional device performance, on an hourly basis,grouped by Device ID.



Report ID:IXFPD02



Attributes:IXFP, Device, Performance, VOLSER, Hourly









IXFP Device Performance, by VolserFrom date: ’2003-11-14’ To date: ’2003-11-14’

MVSsystem Subsystem Tot read

Date Time ID name Volser Partition reqs---------- -------- ------ --------- ------ ---------- --------------2003-11-14 17.00.00 IXA1 RVA00 Production 0

BUF001 2BUF002 0BUF003 55BUF004 78BUF005 173BUF006 108BUF007 29791BUF008 16BUF009 67BUF010 44

Tot write Front-end Front-end Search/read Search/readreqs I/O opers reads writes reqs hits

------------- ------------- ------------- ------------- ------------- -------------0 0 0 0 0 00 99 280 0 2 20 97 0 0 0 092 177 153792 393496 55 46

309 484 218592 20410472 78 78192 535 54514478 5273099 43 42

0 205 404208 0 108 1074746 37779 2773209360 554655571 59 59339 451 45992 27043589 16 16

1 167 173852 140 67 67

Write DASD FW Search/read Search/read Write seq DASD FWreqs hits seq.reqs seq.hits reqs seq.hits

------------- ------------- ------------- ------------- ------------- -------------0 0 0 0 0 00 0 0 0 0 00 0 0 0 0 092 91 0 0 0 033 33 0 0 276 27619 19 130 63 173 1720 0 0 0 0 019 19 29732 29730 4727 472716 16 0 0 323 3231 1 0 0 0 0

Tivoli Decision Support for z/OS Report:IXFPD02

Figure 76. Example of part of an IXFP Device Performance per Volser report



Tot read ReqsThe total count of read requests.

Tot write ReqsThe total count of write requests.

I/O opersThe number of I/O operations.

Front-end readsThe total count of front-end bytes transferred during read operations.

Front-end writesThe total count of front-end bytes transferred during write operations.

Search/read reqsThe total count of search or read normal requests.

Search/read hitsThe total count of search or read normal hits.

Write reqsThe total count of write normal requests.

DASD FW hitsThe total count of DASD fast-write normal hits.

Search/read seq. reqsThe total count of search or read sequential requests.

Search/read seq. hitsThe total count of search or read sequential hits.

Write seq. reqsThe total count of write sequential requests.

DASD FW seq. hitsThe total count of DASD fast-write sequential hits.

IXFP Device Utilization, Hourly Trend reportThis report shows IXFP device utilization information, on an hourly basis, groupedby Device ID.


Report ID:IXFPD03



Attributes:IXFP, Device, Utilization, Hourly






IXFP Device Utilization, Hourly TrendFrom date: ’2003-11-14’ To date: ’2003-11-14’

MVSsystem Subsystem

Date Time ID name Partition---------- ---------- ------ --------- ----------2003-11-14 17.00.00 IXA1 RVA00 Production

Avail Util Conn Dev Dev DevDev Dev Duration time time time avail util connID addr Volser (min) (min) (sec) (sec) (%) (%) (%)------ ------ ------ -------- ----- ------ ------ ------- ------- -------00AA 02AA R93171 45 45 8 6 100.00 0.31 0.2200AB 02AB WKPRD1 45 45 53 43 100.00 1.96 1.5900AC 02AC WKPRD2 45 45 60 47 100.00 2.20 1.7400AD 02AD R93174 45 45 9 6 100.00 0.32 0.2300AE 02AE R93175 45 45 9 7 100.00 0.35 0.2600AF 02AF O006B9 45 45 17 13 100.00 0.61 0.48

-------- ----- ------ ------ ------- ------- -------* 45 45 9 7 100.00 0.33 0.27

18.00.00

00AA 02AA R93171 60 60 0 0 100.00 0.01 0.0100AB 02AB WKPRD1 60 60 59 48 100.00 1.63 1.3300AC 02AC WKPRD2 60 60 61 49 100.00 1.71 1.3600AD 02AD R93174 60 60 0 0 100.00 0.01 0.0000AE 02AE R93175 60 60 2 2 100.00 0.06 0.0500AF 02AF O006B9 60 60 10 9 100.00 0.27 0.25

0097 0297 O003A9 60 60 19 6 99.95 0.52 0.170098 0298 O003B1 60 60 1 0 99.95 0.03 0.000099 0299 O003B2 60 60 1 0 99.95 0.02 0.00

-------- ----- ------ ------ ------- ------- -------* 60 60 97 67 99.95 2.69 1.86

-------- ----- ------ ------ ------- ------- -------** 58 58 26 20 99.99 0.75 0.56

-------- ----- ------ ------ ------- ------- -------*** 58 58 26 20 99.99 0.75 0.56

-------- ----- ------ ------ ------- ------- -------**** 58 58 26 20 99.99 0.75 0.56

-------- ----- ------ ------ ------- ------- -------***** 58 58 26 20 99.99 0.75 0.56

======== ===== ====== ====== ======= ======= =======58 58 26 20 99.99 0.75 0.56

Tivoli Decision Support for z/OS Report:IXFPD03

Figure 77. Example of part of an IXFP Device Utilization, Hourly Trend report






Dev AddrThe device address as known to the lost SCP.


Duration minThe total interval duration time, in minutes.

Avail time minThe total device available time, in minutes.

Util time minThe total device utilization time, in seconds.

Conn time minThe total device connection time, in seconds.

Dev avail (%)The total device available time as a percentage of the total intervalduration time.

Dev util (%)The total device utilization time as a percentage of the total intervalduration time.

Dev conn (%)The total device connection time as a percentage of the total intervalduration time.

IXFP Device DASD/Cache Transfer, Daily Trend reportThis report shows information on DASD/cache transfers, on a daily basis, groupedby Partition.


Report ID:IXFPD04


Source:IXFP_DEVICE_D

Attributes:IXFP, Device, DASD, Daily








Seq DASD to cacheThe total sequential DASD to cache transfers (stages).

DASD to cacheThe total DASD to cache transfers (stages).

Cache to DASDThe total cache to DASD transfers.

IXFP Device Performance, Hourly Trend reportThis report shows IXFP functional device performance, on an hourly basis.


Report ID:IXFPD05


Figure 78. Example of an IXFP Device DASD/Cache Transfer, Daily Trend report



Attributes:IXFP, Device, Performance, Hourly







IXFP Device Performance, Hourly TrendFrom date: ’2003-11-14’ To date: ’2003-11-14’

MVSsystem Subsystem

Date Time ID name Partition---------- ---------- ------ --------- ----------2003-11-14 17.00.00 IXA1 RVA00 Production

Search/read Search/read BypassDev Dev fast write fast write Cache fast Cache fast Inh.cache cacheID addr Volser reqs hits write reqs write hits loading reqs reqs---- ---- ------ ----------- ------------ ---------- ---------- ------------ ------00AA 02AA R93171 0 0 0 0 0.00 0.0000AB 02AB WKPRD1 0 0 0 0 0.00 0.0000AC 02AC WKPRD2 0 0 0 0 0.00 0.0000AD 02AD R93174 0 0 0 0 0.00 0.0000AE 02AE R93175 0 0 0 0 0.00 0.0000AF 02AF O006B9 0 0 0 0 0.00 0.00

0098 0298 O003B1 0 0 0 0 0.00 0.000099 0299 O003B2 0 0 0 0 0.00 0.00

------------ ----------- ----------- ---------- ------------ ------* 0 0 0 0 0.00 0.00

18.00.00

00AA 02AA R93171 0 0 0 0 0.00 0.0000AB 02AB WKPRD1 0 0 0 0 0.00 0.0000AC 02AC WKPRD2 0 0 0 0 0.00 0.0000AD 02AD R93174 0 0 0 0 0.00 0.00

0098 0298 O003B1 0 0 0 0 0.00 0.000099 0299 O003B2 0 0 0 0 0.00 0.00

------------ ----------- ----------- ---------- ------------ -------* 0 0 0 0 0.00 0.00

------------ ----------- ----------- ---------- ------------ -------** 0 0 0 0 0.00 0.00

------------ ----------- ----------- ---------- ------------ -------*** 0 0 0 0 0.00 0.00

------------ ----------- ----------- ---------- ------------ -------**** 0 0 0 0 0.00 0.00

------------ ----------- ----------- ---------- ------------ -------***** 0 0 0 0 0.00 0.00

============ =========== =========== ========== ============ =======0 0 0 0 0.00 0.00

Tivoli Decision Support for z/OS Report: IXFPD05

Figure 79. Example of part of an IXFP Device Performance, Hourly Trend report





Dev addrThe device address as known to the host SCP.


Search/read fast write reqsThe total number of search or read fast-write requests.

Search/read fast write hitsThe total number of search or read fast-write hits.

Cache fast write reqsThe total number of cache fast-write requests.

Cache fast write hitsThe total number of cache fast-write hits.

Inh. cache loading reqsThe total number of inhibit cache loading requests.

Bypass cache reqsThe total number of bypass cache requests.

IXFP Device Utilization, Monthly Trend reportThis report shows IXFP device utilization information, on a monthly basis, groupedby Device ID.


Report ID:IXFPD06


Source:IXFP_DEVICE_M

Attributes:IXFP, Device, Utilization, Monthly, Trend








Dev avail (%)The average device available time as a percentage of the total intervalduration time.

Dev util (%)The average device utilization time as a percentage of the total intervalduration time.

Dev conn (%)The average device connection time as a percentage of the total intervalduration time.

IXFP Drive Utilization, Hourly Trend reportThis report shows information on drive module utilization, on an hourly basis.


Figure 80. Example of an IXFP Device Utilization, Monthly Trend report


Report ID:IXFPM01


Source:IXFP_DRIVE_H

Attributes:IXFP, Drive, Utilization, Hourly



IXFP Drive Utilization, Hourly TrendFrom date: ’2003-11-14’ To date: ’2003-11-14’

MVSsystem Subsystem

Date Time ID Partition name

---------- -------- ------ ---------- ---------2003-11-14 17.00.00 IXA1 Production RVA00

No of read No of write Busy time DurationUnit Tray Slot (MB) (MB) (min) (min)------- ------ -------- ---------- ----------- ---------- ----------00 00 00 11 86 1 4500 00 01 11 86 1 4500 00 02 9 86 1 4500 00 03 87 195 3 4500 00 04 15 87 1 45

00 03 04 5 87 1 4500 03 05 10 86 1 45---------- ----------- ---------- ----------

* 1547 4139 2 45

18.00.00

00 00 00 8 71 1 6000 00 01 10 71 1 6000 00 02 7 71 1 6000 00 03 78 177 3 6000 00 04 6 66 1 60

00 03 04 6 66 1 6000 03 05 10 71 1 60

---------- ----------- ---------- ----------* 1303 3619 2 60

00 03 04 376 344 14 6000 03 05 351 311 13 60

---------- ----------- ---------- ----------* 15687 13760 18 60

---------- ----------- ---------- ----------** 45523 33862 6 58

---------- ----------- ---------- ----------*** 45523 33862 6 58

---------- ----------- ---------- ----------**** 45523 33862 6 58

---------- ----------- ---------- ----------***** 45523 33862 6 58

========== =========== ========== ==========45523 33862 6 58

Tivoli Decision Support for z/OS Report: IXFPM01

Figure 81. Example of part of an IXFP Drive Utilization, Hourly Trend report







Unit The unit.

Tray The tray.

Slot The slot.

No of read in MBThe total number of megabytes that were transferred during readoperations.

No of write in MBThe total number of megabytes that were transferred during writeoperations.

Busy time in minThe average time that the drive module was busy, in minutes.

Duration in minThe average interval duration time for the drive module, in minutes.

IXFP Drive Utilization, Daily Trend reportThis report shows information on drive module utilization, on a daily basis.


Report ID:IXFPM02


Source:IXFP_DRIVE_D

Attributes:IXFP, Drive, Utilization, Daily








No of read opers MBThe total number of megabytes that were transferred during readoperations.

No of write opers MBThe total number of megabytes that were transferred during writeoperations.

No of opers per intervalThe number of megabytes that were transferred during read and writeoperations, per interval duration.

Busy time in minThe average time that the drive module was busy, in minutes.

Duration in minThe average interval duration time for the drive module, in minutes.

IXFP Drive Utilization, Daily TrendFrom date: ’2003-11-14’ To date: ’2003-11-14’

MVSsystem Subsystem

Date ID Partition name---------- ------ ---------- ---------2003-11-14 IXA1 Production RVA00

No of read No of write Drive moduleopers opers No of opers Busy time Duration utilization(MB) (MB) per interval (min) (min) (%)

-------------- -------------- -------------- ---------- -------- ------------45523 33862 3 43 405 10.70

-------------- -------------- -------------- ---------- -------- ------------* 45523 33862 3 43 405 10.70

-------------- -------------- -------------- ---------- -------- ------------** 45523 33862 3 43 405 10.70

-------------- -------------- -------------- ---------- -------- ------------*** 45523 33862 3 43 405 10.70

============== ============== ============== ========== ======== ============45523 33862 3 43 405 10.70

Tivoli Decision Support for z/OS Report: IXFPM02

Figure 82. Example of an IXFP Drive Utilization, Daily Trend report


Drive module utilization (%)The average time that the drive module was busy as a percentage of theinterval duration time.

IXFP Deleted Data Space Release, Daily Trend reportThis report shows information for IXFP Deleted Data Space Release (DDSR), on adaily basis.


Report ID:IXFPR01


Source:IXFP_DDSR_D

Attributes:IXFP, DDSR, Daily





Period nameThe name of the period.

IXFP Deleted Data Space Release, Daily TrendFrom date: ’2003-11-14’ To date: ’2003-11-14’

MVS RAMAC RAMAC I/OPeriod system subsystem subsystem RAMAC Dev Vol time

Date name ID name ID FDID addr ID (sec)---------- -------- ------ ---------- ---------- ------ ------ ------ ----------2003-11-14 WEEKEND IXA1 RVA00 001A 000A 020A BUF003 24

000C 020C BUF004 1037000E 020E BUF005 220008 0208 BUF001 6001C 021C R93029 52001D 021D R93030 840017 0217 BUF007 40002D 022D R93046 169002E 022E R93047 3810027 0227 R93040 354003E 023E BUF006 847

----------**** 3016

----------*** 3016

----------* 3016

----------** 3016

2003-11-14 WEEKEND RVA00 001B 0062 0262 BUF008 580063 0263 BUF009 85

2003-11-14 WEEKEND RVA00 001D 00C5 02C5 WKPRD4 81741---------

* 81741

----------** 81741

----------*** 81741

----------**** 81741

----------***** 319131

==========319131

Tivoli Decision Support for z/OS Report: IXFPR01

Figure 83. Example of part of an IXFP Deleted Data Space Release, Daily Trend report



RAMAC subsys nameThe subsystem name of the RAMAC Virtual Array.

RAMAC subsys IDThe subsystem ID of the RAMAC Virtual Array.

RAMAC FDIDThe functional device ID of the RAMAC Virtual Array.

Dev addrThe device address on which space was released.

Volid The volume ID on which space was released.

I/O time in secThe I/O time for space release, in seconds.

IXFP Subsystem Space Utilization, Daily Trend reportThis report shows information on IXFP subsystem space utilization, on a dailybasis.


Report ID:IXFPS01


Source:IXFP_SUBSYSTEM_D

Attributes:IXFP, Subsystem, Space, Daily








Standard capacity GBThe defined standard capacity, in gigabytes.

Total back-end capacity GBThe total back-end capacity of the partition, in gigabytes.

Free back-end capacity GBThe total of free back-end capacity in the partition that is available for userdata, in gigabytes.

Total no of read GBThe total number of gigabytes read for free space collection in thepartition.

Total amount of free GBThe total amount of free collected space in the partition, in gigabytes.

Figure 84. Example of an IXFP Subsystem Space Utilization, Daily Trend report


Free collected back-end GBThe total amount of free collected back-end space in the partition, ingigabytes.

IXFP Subsystem Information, Daily Trend reportThis report shows information on IXFP subsystem performance, on a daily basis.


Report ID:IXFPS02


Source:IXFP_SUBSYSTEM_D

Attributes:IXFP, Subsystem, Information, Daily




Period nameThe name of the period.



IXFP Subsystem Information, Daily TrendFrom date: ’2003-11-14’ To date: ’2003-11-14’

MVS Byp.msgsPeriod system Subsystem No of No of ECAM no buffer Byp.msgs

Date name ID name Partition ECAM msgs chnl pgms space no conf---------- ------- ------ --------- ---------- --------- ---------- --------- --------2003-11-14 WEEKEND IXA1 RVA00 Production 27758 26786 0 0

--------- ---------- --------- --------* 27758 26786 0 0

--------- ---------- --------- --------** 27758 26786 0 0

--------- ---------- --------- --------*** 27758 26786 0 0

--------- ---------- --------- --------**** 27758 26786 0 0

========= ========== ========= ========27758 26786 0 0

Tivoli Decision Support for z/OS Report: IXFPS02

Figure 85. Example of an IXFP Subsystem Information, Daily Trend report



No of ECAM msgsThe total number of ECAM messages that were processed.

No of ECAM chnl pgmsThe total number of ECAM channel programs.

Byp.msgs no buffer spaceThe total number of ECAM channel programs that were bypassed becauseno buffer space was available.

Byp.msgs no confThe total number of ECAM channel programs that were bypassed becauseno configuration was busy.

IXFP Space Utilization, Hourly Trend reportThis report shows IXFP space utilization, on an hourly basis.


Report ID:IXFPS03


Source:IXFP_SPACE_H

Attributes:IXFP, Space, Hourly








Device nameThe name of the functional device.

Device numberThe device address.


IXFP Space Utilization, Hourly TrendFrom date: ’2000-03-20’ To date: ’2000-03-20’

MVSSystem Subsystem Device Device Device

Date Time ID ID name number Volser type---------- -------- ------ --------- ------ ------ ------- ------2000-03-20 02.00.00 BAT IXFP 00AA 09AA PR9346 33903

00AB 09AB PR9347 3390300AC 09AC PR9348 3390300AD 09AD PR9349 3390300AE 09AE PR9350 3390300AF 09AF PR9351 3390300A0 09A0 BATPG0 33903

Functional Funct cap Funct cap Funct cap Funct capcapacity allocated stored not stored allocated

Partition (MB) (MB) (MB) (MB) %---------- ---------- ---------- ---------- ---------- ----------Production 2838.0 1665.69 1910.14 927.87 58.69

2838.0 2453.49 2415.76 422.26 86.452838.0 2416.89 2373.71 464.30 85.162838.0 1981.26 1456.89 1381.13 69.812838.0 2132.44 2685.93 152.09 75.142838.0 1427.54 1418.36 1419.66 50.302838.0 2637.43 2637.43 200.59 92.93

Funct cap Funct cap Shared Unique Totalstored not stored cap used cap used cap used Comp

% % (MB) (MB) (MB) ratio---------- ---------- -------- ----------- ---------- -------

67.31 32.69 0.00 301.16 301.16 6.3485.12 14.88 0.00 464.18 464.18 5.2083.64 16.36 0.00 486.39 486.39 4.8851.33 48.67 0.00 191.73 191.73 7.6094.64 5.36 0.00 591.39 591.39 4.5449.98 50.02 0.00 230.15 230.15 6.1692.93 7.07 0.00 431.14 431.14 6.12

Tivoli Decision Support for z/OS Report: IXFPS03

Figure 86. Example of part of an IXFP Space Utilization, Hourly Trend report


Device typeThe type functional device.


Functional capacity (MB)The functional capacity, in megabytes.

Functional cap allocated (MB)The functional capacity that was allocated, in megabytes.

Functional cap stored (MB)The functional capacity that was stored, in megabytes.

Functional cap stored (MB)The functional capacity that was not stored, in megabytes.

Functional cap allocated (%)The percentage of functional capacity that was allocated.

Functional cap stored (%)The percentage of functional capacity that was stored.

Functional cap stored (%)The percentage of functional capacity that was not stored.

Shared cap used (MB)The shared physical capacity that was used, in megabytes.

Unique cap used (MB)The unique physical capacity that was used, in megabytes.

Total cap used (MB)The shared physical capacity that was used, in megabytes.

Comp ratioThe compression ratio.

Message analysis/automation componentCustomizationv Making input data available

– JES2 and JES3 SYSLOG and OPERLOG– NetView

v Modifying DRLJCOLLv Updating lookup tables


Log and record definitionsv Log procedures

Data tables, views, and lookup tablesv Data tables

– MSG_NETVIEW_H, _D, _M– MSG_SYSLOG_H, _D, _M


v Views– MSG_NETVIEW_DV– MSG_NETVIEW_HV– MSG_NETVIEW_MV– MSG_SYSLOG_DV– MSG_SYSLOG_HV– MSG_SYSLOG_MV

v Lookup tables– MSG_ANO_EVENT– MSG_NETVIEW_TYPE– MSG_SYSLOG_ROUTE– MSG_SYSLOG_TYPE

Reportsv SYSLOG reports

– MAA Messages From Commands (JES2), Daily report– MAA Messages by Console ID, Daily report– MAA Most Frequent Messages (JES2), Daily report– MAA Most Frequent Messages (JES3), Daily report– MAA Messages Passed to NetView (JES2), Daily report– MAA Most Frequent Messages With Text, Daily report– MAA Most Frequent Nonsuppressed Messages, Daily report– MAA Most Frequent Messages by Type (JES2), Daily report– MAA Most Frequent Messages by Type (JES3), Daily report– MAA Messages by Route Code (JES2), Daily report– MAA Messages by Route Code (JES3), Daily report– MAA Messages by JES Complex, Daily report– MAA Messages Suppressed, Monthly Trend report

v NetView reports– MAA Most Frequent Messages (NetView), Daily report– MAA Messages Passed via the SSI (NetView), Daily report– MAA Messages by NetView Operator (NetView), Daily report

CustomizationBefore you can use the message analysis/automation component to collect dataand create reports, you must customize and test the installation. This chapterdescribes the steps you must perform to customize the messageanalysis/automation component:1. Making input data available.2. Modifying DRLJCOLL.3. Updating lookup tables.

Making input data availableYou must ensure that the appropriate data is available to Tivoli Decision Supportfor z/OS. The message analysis/automation component collects data from the JES2and JES3 system logs (SYSLOGs) and from the NetView® log. If using SYSLOGsand not the operations log (OPERLOG), you must convert your current VB log to aFB format for the collect to function in the correct manner. You can use many


different utilities for this job but care must be made to strip the leading X'40',which is left after most conversion jobs, or the record is not collected.

JES2 and JES3 SYSLOG and OPERLOG:JES2 and JES3 SYSLOG and OPERLOG

In a sysplex environment, you can collect the OPERLOG instead of collectingindividual JES2 or JES3 SYSLOGs. Tivoli Decision Support for z/OS collects datafrom the OPERLOG using the MVS System Logger subsystem data set interface. Tocollect the OPERLOG, specify a JES2 log in the Tivoli Decision Support for z/OScollect job, and change the DRLLOG dd statement as described in the DRLJCOLLjob example in the System Performance Feature Reference Volume I. See z/OS MVSDiagnosis: Tools and Service Aids for details on Log Stream Subsystem Data Set JCLspecification.

Ensure that the SYSLOG records produced by JES2 or JES3 systems are available toTivoli Decision Support for z/OS and are in the correct format. Perform thesesteps:1. Ensure that RECFM = FB is used for the SYSLOG data set, because the log

procedure assumes that the JES2 or JES3 SYSLOG data set is a fixed-formatdata set.

2. Ensure that there are no printer control characters at position 1 in the records inthe SYSLOG data set.

3. If your SYSLOG records are produced by JES2, the log procedure assumes thatthe JES2 message prefix is either an X'5A' or X'5B' character. Ensure that eitherof these prefix characters is specified in the JES2 initialization parameters.

4. If your SYSLOG records are produced by JES3 and the JES3 release is earlierthan 2.2.0, ensure that the JES3 data contains at least one system loginitialization record. If there is no system log initialization record, the TivoliDecision Support for z/OS log procedure skips the SYSLOG records.

NetView:NetView

Use the NetView DSIPRT utility to print the NetView log to a DASD data set. Themember CNMSJM04 in CNMSAMP contains JCL to do the printing. You mustmodify this JCL to direct the output to a data set.

Modifying DRLJCOLLBefore running the Tivoli Decision Support for z/OS collect job, you must updatethe DRLJCOLL member, as described in "Setting up the collect job" in Volume I.

Updating lookup tablesThe message analysis/automation component uses several lookup tables whenupdating tables in the Tivoli Decision Support for z/OS database. The lookuptables contain a default set of parameters when shipped with the product. Afteryou have been using the message analysis/automation component for a while, youmay want to customize the lookup tables.

Using the administration dialog, update these lookup tables:



MSG_SYSLOG_ROUTE Converts JES2 message route codesto a more readable form. Thisinformation is used to providestatistics on JES2 system logmessages.

ROUTE_CODE ROUTE_CODE_CONVERT

MSG_SYSLOG_TYPE Converts the first three charactersof the message ID to a messagetype.

MESSAGE_ID_PREFIX MESSAGE_TYPE

MSG_NETVIEW_TYPE Converts message types tomeaningful descriptions.

MESSAGE_TYPE MESSAGE_TYPE_DESC

MSG_ANO_EVENT Converts message IDs to eventtypes and descriptions, and givesthe number of the word thatcontains the resource name.

MESSAGE_ID WORD_NUMBEREVENT_TYPEMESSAGE_DESC

For descriptions of these lookup tables and examples of their contents, see Lookuptables.

The message analysis/automation component also uses the DAY_OF_WEEK,PERIOD_PLAN, and SPECIAL_DAY control tables. Ensure that these tables includethe correct information. Refer to the Administration Guide and Reference forinformation on the control tables.

For information on using the administration dialog to update lookup tables, see"Updating lookup tables" in the System Performance Feature Reference Volume I.

Data flowThe message analysis/automation component collects records from the JES2, JES3,and NetView systems, and stores the data in the Tivoli Decision Support for z/OSdatabase. You can then use reporting dialogs to create reports based on this data.Figure 87 shows an overview of the data flow through the messageanalysis/automation component.


Storing the dataAfter collecting the data, the message analysis/automation component stores thedata in tables in the Tivoli Decision Support for z/OS database. As it updates thetables, the component uses lookup tables to convert the first three characters of themessage ID to a message type, convert JES2 route logs, convert message types tomeaningful descriptions, and convert message IDs to event types and descriptions.

In creating the NetView reports, the message analysis/automation component usesthe lookup tables MSG_NETVIEW_TYPE and MSG_ANO_EVENT to convertmessage types to a meaningful description and to convert message IDs to eventtypes and descriptions, and to give the number of the word that contains theresource name. Figure 88 shows which data tables contain values from the lookuptables.

Figure 87. Message analysis/automation component data flow


The message analysis/automation component uses the DAY_OF_WEEK,PERIOD_PLAN, and SPECIAL_DAY control tables to update all hourly tables. Forinformation on the control tables, refer to the Administration Guide and Reference.

For detailed information about the tables updated by the component and thelookup tables it uses, see Data tables, views, and lookup tables.

Log and record definitionsMessages sent to a SYSOUT data set are intended for a programmer. Thesemessages are issued by an assembler or compiler, the linkage editor, the loader,and an application program. If the SYSOUT data set and the MSGCLASSparameter on the JCL JOB statement specify the same class, all messages about aprogram will appear in the same SYSOUT listing. The messageanalysis/automation component processes these records:

Figure 88. Message analysis/automation lookup table data


Table 6. Input records to the message analysis/automation component

SYSLOG or NetView record Record definition Description

JES2 SYSLOG records SYSLOG_JES2_MSG These records contain all messages issued throughWTL macros, messages entered by operator logcommands, usually the hardcopy log, andmessages routed to the system log that are outputby the JES2 system.

JES3 SYSLOG records SYSLOG_JES3_MSG These records contain all messages issued throughWTL macros, messages entered by operator logcommands, the hardcopy log, and messages routedto the system log that are output by the JES3system.

NetView log records NETVIEW_MSG These records contain activity of all NetViewoperator stations, including commands entered andmessages received.

For information on the JES2 and JES3 SYSLOG, see z/OS MVS System Messages.

For information on the NetView log, see NetView Problem Determination andDiagnosis.

Log proceduresThe message analysis/automation component uses three log procedures to processthe input logs:

DRL2MAJ2Reads records from the JES2 SYSLOG and formats and builds an outputrecord with a common format.

DRL2MAJ3Reads records from the JES3 SYSLOG and formats and builds an outputrecord with a common format.

DRL2MANVReads records from the NetView log and formats and builds an outputrecord with a common format.

Note: The log procedures are automatic and run at the time of a log collect. Theyare not procedures that you need to run separately.

Data tables, views, and lookup tablesThis chapter describes the data tables, views, and lookup tables used by themessage analysis/automation component. For descriptions of common data tables,lookup tables, and control tables used by the System Performance featurecomponent, see the Administration Guide and Reference.

Data tablesThis section describes the data tables for the message analysis/automationcomponent.

MSG_NETVIEW_H, _D, _M:MSG_NETVIEW_H, _D, _M

These tables provide hourly, daily, and monthly statistics on NetView logmessages. They contain message data from the NetView log, which is reformattedto a common layout by the log procedure DRL2MANV.


These tables are updated by the MSG_NETVIEW_TYPE and MSG_ANO_EVENTlookup tables.


MSG_NETVIEW_H10 days

MSG_NETVIEW_D30 days

MSG_NETVIEW_M765 days


DATE K DATE Date when the NetView log records were written. Forthe _M table, this is the date of the first day of themonth. From NVDATE.

TIME K TIME Time (rounded down to the nearest hour) when theNetView log records were written. It applies only tothe _H table. From NVTIME.

PERIOD_NAME K CHAR(8) Name of the period. This is derived using fieldsNVDATE and NVTIME from the record as parametersin the PERIOD function.

MVS_SYSTEM_ID K CHAR(8) MVS system ID. This is the name of the MVS systemin which NetView is running. From theSET MVS_SYSTEM_ID='mvs_system_id' statement inthe DRLJCOLL collect JCL.

MESSAGE_ID K CHAR(10) Message ID. From NVMSG.

MESSAGE_CODE K CHAR(2) Message code. From NVINDIC.

MESSAGE_TYPE K CHAR(1) Message type symbol. From NVFLAG.

NETVIEW_DOMAIN K CHAR(5) NetView domain. From NVDOMAIN.

NETVIEW_OPERATOR K CHAR(8) NetView operator. From NVOPERAT.

EVENT_TYPE CHAR(8) Type of event. From EVENT_TYPE in theMSG_ANO_EVENT lookup table.

MESSAGE_DESC CHAR(48) Description for the message ID. FromMESSAGE_DESC in the MSG_ANO_EVENT lookuptable.

MESSAGES_SOLICITED INTEGER VTAM solicited messages. This is the number ofrecords where NVFLAG is blank.

MESSAGES_TOT INTEGER Total number of messages. This is the count ofNVMSG.

MESSAGES_UNSOL INTEGER VTAM unsolicited messages. This is the number ofrecords where NVFLAG is Q.

MESSAGE_TYPE_DESC CHAR(48) Message type description. FromMESSAGE_TYPE_DESC in the MSG_NETVIEW_TYPElookup table.

RESOURCE_NAME CHAR(8) Name of the resource. From NVTEXTxx, where xx isthe word number derived from WORD_NUMBER inthe MSG_ANO_EVENT lookup table using NVMSGas key.

MSG_SYSLOG_H, _D, _M:


MSG_SYSLOG_H, _D, _M

These tables provide hourly, daily, and monthly statistics on JES2 and JES3 systemlog messages. They contain message data from the JES2 and JES3 system logs,which is reformatted to a common layout by the log procedures DRL2MAJ2 andDRL2MAJ3, respectively.

These tables are updated by the MSG_SYSLOG_TYPE and MSG_SYSLOG_ROUTElookup tables.


MSG_SYSLOG_H10 days

MSG_SYSLOG_D30 days

MSG_SYSLOG_M765 days


DATE K DATE Date when the SYSLOG records were written. For the_M table, this is the date of the first day of the month.From S2DATE or S3DATE.

TIME K TIME Time (rounded down to the nearest hour) when theSYSLOG records were written. It applies only to the_H table. From S2TIME or S3TIME.

PERIOD_NAME K CHAR(8) Name of the period. This is derived using fieldsS2DATE and S2TIME, or S3DATE and S3TIME fromthe record as parameters in the PERIOD function.

JES_COMPLEX K CHAR(8) Name of the JES complex. From theSET JES_COMPLEX='jes_complex_name' statement inthe DRLJCOLL collect JCL.

MVS_SYSTEM_ID K CHAR(8) MVS system ID. This is the MVS system name in theSYSLOG record. From S2PRNAME or S3PRNAME.

MESSAGE_ID K CHAR(10) SYSLOG message ID. CCC0000 is the group identifierfor commands. From S2MSGID or S3MSGID.

MESSAGE_TYPE K CHAR(4) Message type. From MESSAGE_TYPE in theMSG_SYSLOG_TYPE lookup table.

CONSOLE_ID K CHAR(2) Console ID for the SYSLOG message. From S2CONIDor S3CONID.

ROUTE_CODE K CHAR(7) SYSLOG message route code. From S2ROUTE orS3ROUTE. For JES2 SYSLOG messages, the route codeis converted in the MSG_SYSLOG_ROUTE lookuptable.

AUTO_MESSAGES INTEGER Number of automation messages. This is the numberof records where position 7 of S2MSGFLG is equal to1 or 9.

COMMAND_RESPONSES INTEGER Number of response messages to commands. This isthe number of records where position 2 of S2ROUTEis equal to R.

CONSOLE_COMMANDS INTEGER Number of commands entered from consoles. This isthe number of records where position 2 of S2ROUTEis equal to C.



INTERNAL_COMMANDS INTEGER Number of commands entered internally. This is thenumber of records where position 2 of S2ROUTE isequal to I.

JES_TYPE CHAR(1) Type of JES subsystem. This is 2 or 3.

MESSAGES_HIGH FLOAT Number of nonsuppressed and suppressed messagesthat arrived during the high interval (0.0 to 1.0 secondafter the previous message).

MESSAGES_LOW FLOAT Number of nonsuppressed and suppressed messagesthat arrived during the low interval (5.0 seconds ormore after the previous message).

MESSAGES_MEDIUM FLOAT Number of nonsuppressed and suppressed messagesthat arrived during the medium interval (1.0 to 5.0seconds after the previous message).

MESSAGES_SUPPR INTEGER Number of suppressed messages. This is the numberof records where position 6 to 9 of S2ROUTE is equalto SUPP.

MESSAGES_TOT INTEGER Total number of messages. This is the count ofS2MSGID or S3MSGID.

MESSAGE_TEXT CHAR(40) First 40 characters of the message text. FromS2MSGTXT or S3MSGTXT.

MULTILINE_LINES FLOAT Number of lines in the multiline messages. This is thesum of S2MLINE.

MULTILINE_MESSAGES FLOAT Number of multiline messages. This is the number ofrecords where S2MLINE is greater than 1.

NONSUPPRESSED_HIGH FLOAT Number of nonsuppressed messages that arrivedduring the high interval (0.0 to 1.0 second after theprevious message).

NONSUPPRESSED_LOW FLOAT Number of nonsuppressed messages that arrivedduring the low interval (5.0 seconds or more after theprevious message.

NONSUPPRESSED_MED FLOAT Number of nonsuppressed messages that arrivedduring the medium interval (1.0 to 5 seconds after theprevious message.

SINGLE_LINE_MSG INTEGER Number of one-line messages. This is the number ofrecords where S2MLINE is equal to 1.

ViewsThis section describes the views for the message analysis/automation component.

MSG_NETVIEW_DV:MSG_NETVIEW_DV

This view provides daily statistics on the total number of NetView log messagesper NetView domain and period name. It is based on the MSG_NETVIEW_D table.


DATE K DATE Date when the NetView log records were written.From NVDATE.





MESSAGES_TOT FLOAT Total number of messages. This is the count ofNVMSG.

MSG_NETVIEW_HV:MSG_NETVIEW_HV

This view provides hourly statistics on the total number of NetView log messagesper NetView domain and period name. It is based on the MSG_NETVIEW_H table.


DATE K DATE Date when the NetView log records were written.From NVDATE.

TIME K TIME Time (rounded down to the nearest hour) when theNetView log records were written. From NVTIME.



MESSAGES_TOT INTEGER Total number of messages. This is the count ofNVMSG.

MSG_NETVIEW_MV:MSG_NETVIEW_MV

This view provides monthly statistics on the total number of NetView logmessages per NetView domain and period name. It is based on theMSG_NETVIEW_M table.


DATE K DATE Date when the NetView log records were written.This is the date of the first day of the month. FromNVDATE.



MESSAGES_TOT FLOAT Total number of messages. This is the count ofNVMSG.

MSG_SYSLOG_DV:MSG_SYSLOG_DV

This view provides daily statistics on the total number of JES2 and JES3 system logmessages per JES complex and period name. It is based on the MSG_SYSLOG_Dtable.



DATE K DATE Date when the SYSLOG records were written. FromS2DATE or S3DATE.


JES_COMPLEX K CHAR(8) Name of the JES complex. From the SETJES_COMP='jes_complex_name' statement in theDRLJCOLL collect JCL.


MSG_SYSLOG_HV:MSG_SYSLOG_HV

This view provides hourly statistics on the total number of JES2 and JES3 systemlog messages per JES complex and period name. It is based on theMSG_SYSLOG_H table.


DATE K DATE Date when the SYSLOG records were written. FromS2DATE or S3DATE.

TIME K TIME Time (rounded down to the nearest hour) when theSYSLOG records were written. From S2TIME orS3TIME.




MSG_SYSLOG_MV:MSG_SYSLOG_MV

This view provides monthly statistics on the total number of JES2 and JES3 systemlog messages per JES complex and period name. It is based on theMSG_SYSLOG_M table.


DATE K DATE Date when the SYSLOG records were written. FromS2DATE or S3DATE. This is the date of the first dayof the month.





MESSAGES_TOT FLOAT Total number of messages. This is the count ofS2MSGID or S3MSGID.

Lookup tablesThis section describes the lookup tables specific to the messageanalysis/automation component.

MSG_ANO_EVENT:MSG_ANO_EVENT

This lookup table converts the automated network operations (ANO) message IDsto event types and descriptive text, and gives the number of the word in the recordthat contains the resource name.


MESSAGE_ID K CHAR(10) Message ID in the log record. From NVMSG.

EVENT_TYPE CHAR(8) Type of event.

MESSAGE_DESC CHAR(48) Description for the message ID.

WORD_NUMBER SMALLINT Position of the word in the record that contains theresource name.


MESSAGE WORD EVENT MESSAGEID NUMBER TYPE DESC

---------- ------ -------- ---------------------------------------IST095A 4 OUTAGE OPTION TO DUMPIST284A 4 OUTAGE OPTION TO RELOADIST727I 4 OUTAGE COMMUNICATION WITH CDRM LOSTIST105I 1 OUTAGE NODE INACTIVEIST400I 6 OUTAGE TERMINATION IN PROGRESSIST619I 3 OUTAGE FAILED - RECOVERY IN PROGRESSIST621I 6 RECOVERY RECOVERY SUCCESSFULIST804I 5 OUTAGE CLOSE IN PROGRESSIST093I 1 RECOVERY ACTIVEEHK504I 3 -OTHER- AVAILABLEEHK509I 3 -OTHER- UNAVAILABLEEHK506I 3 -OTHER- ATTEMPTING RECOVERYEHK507I 3 -OTHER- UNRECOVERABLE FOR NN MINUTESEHK541W 7 -OTHER- ACTIVATION FAILEDEHK501W 6 RECHALT RECOVERY HALTEDEHK502I 6 -OTHER- RECOVERY CONTINUINGEHK503I 5 -OTHER- RECOVERY CONTINUING

MSG_ANO_EVENT:MSG_ANO_EVENT

This lookup table converts the automated network operations (ANO) message IDsto event types and descriptive text, and gives the number of the word in the recordthat contains the resource name.


MESSAGE_ID K CHAR(10) Message ID in the log record. From NVMSG.

EVENT_TYPE CHAR(8) Type of event.



MESSAGE_DESC CHAR(48) Description for the message ID.

WORD_NUMBER SMALLINT Position of the word in the record that contains theresource name.


MESSAGE WORD EVENT MESSAGEID NUMBER TYPE DESC

---------- ------ -------- ---------------------------------------IST095A 4 OUTAGE OPTION TO DUMPIST284A 4 OUTAGE OPTION TO RELOADIST727I 4 OUTAGE COMMUNICATION WITH CDRM LOSTIST105I 1 OUTAGE NODE INACTIVEIST400I 6 OUTAGE TERMINATION IN PROGRESSIST619I 3 OUTAGE FAILED - RECOVERY IN PROGRESSIST621I 6 RECOVERY RECOVERY SUCCESSFULIST804I 5 OUTAGE CLOSE IN PROGRESSIST093I 1 RECOVERY ACTIVEEHK504I 3 -OTHER- AVAILABLEEHK509I 3 -OTHER- UNAVAILABLEEHK506I 3 -OTHER- ATTEMPTING RECOVERYEHK507I 3 -OTHER- UNRECOVERABLE FOR NN MINUTESEHK541W 7 -OTHER- ACTIVATION FAILEDEHK501W 6 RECHALT RECOVERY HALTEDEHK502I 6 -OTHER- RECOVERY CONTINUINGEHK503I 5 -OTHER- RECOVERY CONTINUING

MSG_NETVIEW_TYPE:MSG_NETVIEW_TYPE

This lookup table converts the message type symbol in a NetView log todescriptive text.


MESSAGE_TYPE K CHAR(1) Message type symbol to be converted to descriptivetext. From NVFLAG.

MESSAGE_TYPE_DESC CHAR(48) Descriptive text for the message type symbol.


MESSAGEMESSAGE TYPETYPE DESC------- ------------------------------------------------A MSG AUTOMATED TO DRIVE CMD/CMDLISTC MSG/CMD GENERATED DURING CMDLIST PROCESSINGE EXTERNAL MSGM MSG FROM A MSG CMDQ UNSOLICITED MSG FROM VTAMS MSG TEXT PROVIDED BY USER EXITU MSG FROM USER-WRITTEN CODEV VTAM COMMAND FROM SYSTEM CONSOLEW MSG SATISFYING CMDLIST WAITY VTAM MESSAGE FROM SYSTEM CONSOLEZ MSG FROM DATA SERVICE TASK| CROSS-DOMAIN OR IMMEDIATE CMD MSG! IMMEDIATE COMMAND MSG- NETVIEW MESSAGE


* CMD ECHOSOLICITED MSG FROM VTAM

+ MSG GENERATED BY NON-NETVIEW CMD

MSG_NETVIEW_TYPE:MSG_NETVIEW_TYPE

This lookup table converts the message type symbol in a NetView log todescriptive text.


MESSAGE_TYPE K CHAR(1) Message type symbol to be converted to descriptivetext. From NVFLAG.

MESSAGE_TYPE_DESC CHAR(48) Descriptive text for the message type symbol.


MESSAGEMESSAGE TYPETYPE DESC------- ------------------------------------------------A MSG AUTOMATED TO DRIVE CMD/CMDLISTC MSG/CMD GENERATED DURING CMDLIST PROCESSINGE EXTERNAL MSGM MSG FROM A MSG CMDQ UNSOLICITED MSG FROM VTAMS MSG TEXT PROVIDED BY USER EXITU MSG FROM USER-WRITTEN CODEV VTAM COMMAND FROM SYSTEM CONSOLEW MSG SATISFYING CMDLIST WAITY VTAM MESSAGE FROM SYSTEM CONSOLEZ MSG FROM DATA SERVICE TASK| CROSS-DOMAIN OR IMMEDIATE CMD MSG! IMMEDIATE COMMAND MSG- NETVIEW MESSAGE* CMD ECHO

SOLICITED MSG FROM VTAM+ MSG GENERATED BY NON-NETVIEW CMD

MSG_SYSLOG_ROUTE:MSG_SYSLOG_ROUTE

This lookup table converts the message route code from a JES2 SYSLOG record toa more readable form.


ROUTE_CODE K CHAR(7) SYSLOG message route code to be converted to amore readable form. From S2ROUTE.

ROUTE_CODE_CONVERT CHAR(7) Message route code converted to a more readableform.


ROUTEROUTE CODECODE CONVERT------- -------

SUPP SUPP


C000000 0102C200000 010207FFFFFFF ALL00A0000 09110000000 000004000 140020000 110040000 100060000 10110080000 090100000 080140000 08100200000 070300000 07082000000 032800000 0309

MSG_SYSLOG_ROUTE:MSG_SYSLOG_ROUTE

This lookup table converts the message route code from a JES2 SYSLOG record toa more readable form.


ROUTE_CODE K CHAR(7) SYSLOG message route code to be converted to amore readable form. From S2ROUTE.

ROUTE_CODE_CONVERT CHAR(7) Message route code converted to a more readableform.


ROUTEROUTE CODECODE CONVERT------- -------

SUPP SUPPC000000 0102C200000 010207FFFFFFF ALL00A0000 09110000000 000004000 140020000 110040000 100060000 10110080000 090100000 080140000 08100200000 070300000 07082000000 032800000 0309

MSG_SYSLOG_TYPE:MSG_SYSLOG_TYPE

This lookup table converts the first three characters of the message ID to a messagetype such as CICS, JES3, and so on.



MESSAGE_ID_PREFIX K CHAR(3) SYSLOG message ID. CCC is the group identifier forcommands. From S2MSGID or S3MSGID.

MESSAGE_TYPE CHAR(4) Message type assigned for the first three characters ofthe SYSLOG message ID.


MESSAGEID MESSAGE

PREFIX TYPE------- -------HAS JES2IAT JES3CSV MVSIOS MVSIEC MVSICK MVSICP MVSIRA MVSERB MVSCRE MVSIEF MVSIEA MVSIEE MVSIGF MVSADY MVSARC HSMICT MVSICU MVSIAR MVS

MSG_SYSLOG_TYPE:MSG_SYSLOG_TYPE

This lookup table converts the first three characters of the message ID to a messagetype such as CICS, JES3, and so on.


MESSAGE_ID_PREFIX K CHAR(3) SYSLOG message ID. CCC is the group identifier forcommands. From S2MSGID or S3MSGID.

MESSAGE_TYPE CHAR(4) Message type assigned for the first three characters ofthe SYSLOG message ID.


MESSAGEID MESSAGE

PREFIX TYPE------- -------HAS JES2IAT JES3CSV MVSIOS MVSIEC MVSICK MVSICP MVSIRA MVSERB MVS


CRE MVSIEF MVSIEA MVSIEE MVSIGF MVSADY MVSARC HSMICT MVSICU MVSIAR MVS

ReportsThe message analysis/automation component provides these reports:v SYSLOG reports

– MAA Messages From Commands (JES2), Daily report– MAA Messages by Console ID, Daily report– MAA Most Frequent Messages (JES2), Daily report– MAA Most Frequent Messages (JES3), Daily report– MAA Messages Passed to NetView (JES2), Daily report– MAA Most Frequent Messages With Text, Daily report– MAA Most Frequent Nonsuppressed Messages, Daily report– MAA Most Frequent Messages by Type (JES2), Daily report– MAA Most Frequent Messages by Type (JES3), Daily report– MAA Messages by Route Code (JES2), Daily report– MAA Messages by Route Code (JES3), Daily report– MAA Messages by JES Complex, Daily report– MAA Messages Suppressed, Monthly Trend report

v NetView reports– MAA Most Frequent Messages (NetView), Daily report– MAA Messages Passed via the SSI (NetView), Daily report– MAA Messages by NetView Operator (NetView), Daily report

SYSLOG reportsThese reports help you analyze responses to commands and how different consolesare used. They also show you command and message information such as thenumber of commands in your system and the most frequent messages in JES2 andJES3 systems, grouped by type.

MAA Messages From Commands (JES2), Daily report:MAA Messages From Commands (JES2), Daily report

This report shows you how many commands are entered in your system and helpsyou analyze responses to commands.


Report IDMAA01

Report groupMessage analysis/automation reports

SourceMSG_SYSLOG_D, MSG_SYSLOG_DV


AttributesMessage, Operation, Console, ID, SYSLOG, JES2, Daily

VariablesDate, JES_complex, Period_name


Message IDThe SYSLOG message ID. CCC0000 is the group identifier for commands.

Message countThe number of messages.

Messages of total (%)The percentage of all messages.

Console commandsThe number of commands entered from consoles.

Internal commandsThe number of commands entered internally.

Command responsesThe number of response messages to commands.

Multi line messagesThe number of multiline messages.

Lines per multiline messageThe number of lines per multiline message.

MAA Messages by Console ID, Daily report:MAA Messages by Console ID, Daily report

This report helps you analyze how different consoles are used.


MAA Messages From Commands (JES2), DailyJES Complex: ’JES2COMP’ Period: ’PRIME ’

Date: ’2000-01-15’

Messages Multi Lines perMessage Message of total Console Internal Command line multiline

ID count (%) commands commands responses messages message---------- -------- -------- -------- -------- --------- -------- ---------CCC0000 1427 8.4 1123 304 0 0 0IEF403I 476 2.8 0 0 476 0 0IEF404I 455 2.7 0 0 455 0 0HASP608 273 1.6 0 0 273 0 0IEF125I 262 1.5 0 0 262 0 0HASP880 252 1.5 0 0 252 0 0IEF126I 214 1.3 0 0 214 0 0IKJ574I 133 0.8 0 0 133 0 0IEF450I 33 0.2 0 0 33 33 2AOF570I 32 0.2 0 0 1 0 0

Tivoli Decision Support for z/OS Report: MAA01

Figure 89. Example of an MAA Messages From Commands (JES2), Daily report


Report IDMAA02



AttributesMessage, Operation, Console, ID, SYSLOG, JES2, JES3, Daily

VariablesDate, JES_complex, Period_name


Console IDThe console ID. This is the group identifier for messages not associatedwith any console.



Suppressed messagesThe number of suppressed messages.

Suppressed (%)The percentage of the total number of messages for this console ID thatwere suppressed.

MAA Most Frequent Messages (JES2), Daily report:MAA Most Frequent Messages (JES2), Daily report

This report shows you the most frequent messages in your JES2 system.


Report IDMAA03

MAA Messages by Console ID, DailyJES Complex: ’JES2COMP’ Period: ’PRIME ’

Date: ’2000-01-15’

MessagesConsole Message of total Suppressed Suppressed

ID count (%) messages (%)---------- -------- -------- ---------- ------------ 16955 99.3 12107 71.425 90 0.5 90 100.023 13 0.1 13 100.019 11 0.1 11 100.026 6 0.0 6 100.027 1 0.0 1 100.016 1 0.0 1 100.0


Figure 90. Example of an MAA Messages by Console ID, Daily report





VariablesDate, JES_complex, Period_name, Maxrows






Suppressed (%)The percentage of the total number of messages for this message ID thatwere suppressed.

Single line messagesThe number of one-line messages.



MAA Most Frequent Messages (JES3), Daily report:

MAA Most Frequent Messages (JES2), DailyJES Complex: ’JES2COMP’ Period: ’PRIME ’

Date: ’2000-01-15’

Messages Single Multi Lines perMessage Message of total Suppressed Suppressed line line multiline

ID count (%) messages (%) messages messages message---------- -------- -------- ---------- ---------- -------- -------- ---------SSC105 3140 18.4 3140 100.0 3140 0 0CCC0000 1427 8.4 148 10.4 1427 0 0HASP250 819 4.8 819 100.0 819 0 0HASP100 750 4.4 750 100.0 750 0 0HASP373 738 4.3 738 100.0 738 0 0IEE400I 733 4.3 733 100.0 733 0 0HASP395 710 4.2 710 100.0 710 0 0010/001 536 3.1 0 0.0 536 0 0ICH70001I 477 2.8 477 100.0 477 0 0IEF403I 476 2.8 476 100.0 476 0 0


Figure 91. Example of an MAA Most Frequent Messages (JES2), Daily report


MAA Most Frequent Messages (JES3), Daily report

This report shows you the most frequent messages in your JES3 system.


Report IDMAA04










Suppressed (%)The percentage of the total number of messages for this message ID thatwere suppressed.

MAA Messages Passed to NetView (JES2), Daily report:

MAA Most Frequent Messages (JES3), DailyJES Complex: ’JES3COMP’ Period: ’PRIME ’

Date: ’2000-01-15’

MessagesMessage Message of total Suppressed Suppressed

ID count (%) messages (%)---------- -------- -------- ---------- ----------IAT7450 11515 11.9 11515 100.0IAT7005 9183 9.5 8709 94.8IAT6101 6707 6.9 6707 100.0ICH70001I 6413 6.6 6413 100.0IEF403I 6298 6.5 6298 100.0IEF404I 6288 6.5 6288 100.0CCC0000 5731 5.9 0 0.0IAT9127 4947 5.1 4947 100.0IAT7001 4912 5.1 4640 94.5IAT2003 4770 4.9 4770 100.0


Figure 92. Example of an MAA Most Frequent Messages (JES3), Daily report


MAA Messages Passed to NetView (JES2), Daily report

This report shows the most frequent messages and the first 40 characters from themessage text. These messages are passed to NetView for automation. This reportexists only for JES2 systems because there is no indication in a JES3 SYSLOG that amessage is destined for automation. For more information on using this report,refer to the System Performance Feature Guide.


Report IDMAA05


SourceMSG_SYSLOG_D


VariablesFrom_date, To_date, JES_complex, Period_name, Maxrows


Message IDThe SYSLOG message ID.

Automation message countThe number of messages.

Message textThe first 40 characters from the message text.

MAA Most Frequent Messages With Text, Daily report:

MAA Messages Passed to NetView (JES2), DailyJES Complex: ’JES2COMP’ Period: ’PRIME ’

Date: ’2000-01-15’ to ’2000-01-15’

AutomationMessage message

ID count Message text---------- ---------- -----------------------------------------HASP373 738 $HASP373 SE58186 STARTEDHASP395 710 $HASP395 SE51045L ENDED010/001 536 *010/001 -K -KIS-ENTER PARAMETERS (AUTO=IEF403I 476 IEF403I SE51045B - STARTED - TIME=08.03IEF404I 455 IEF404I SE51045L - ENDED - TIME=08.00.0HASP308 334 $HASP308 VPWPROD ESTIMATED TIME EXCEEDHASP530 329 $HASP530 FI72340 ON L5.ST1 1,0IEF125I 262 IEF125I SE58186 - LOGGED ON - TIME=08.0IEF126I 214 IEF126I SE58186 - LOGGED OFF - TIME=08.EDG6627A 196 *EDG6627A MA M 052B V(K10900) R(K10900)


Figure 93. Example of an MAA Messages Passed to NetView (JES2), Daily report


MAA Most Frequent Messages With Text, Daily report

This report shows the most frequent messages and the first 40 characters from themessage text.


Report IDMAA06


SourceMSG_SYSLOG_D







MAA Most Frequent Nonsuppressed Messages, Daily report:MAA Most Frequent Nonsuppressed Messages, Daily report

This report shows the most frequent nonsuppressed messages and the first 40characters from the message text. For more information on using this report, referto the System Performance Feature Guide.

MAA Most Frequent Messages With Text, DailyJES Complex: ’JES2COMP’ Period: ’PRIME ’

Date: ’2000-01-15’ to ’2000-01-15’

Message MessageID count Message text

---------- ---------- -----------------------------------------SSC105 3140 SSC105 JOBNAME SN STEP PSTEP ELCCC0000 1427 SE ’08.00.03 JOB00038 $HASP165 SE51045LHASP250 819 $HASP250 SE58186 IS PURGEDHASP100 750 $HASP100 SE58186 ON TSOINRDRHASP373 738 $HASP373 SE58186 STARTEDIEE400I 733 IEE400I THESE MESSAGES CANCELED - 06.HASP395 710 $HASP395 SE51045L ENDED010/001 536 *010/001 -K -KIS-ENTER PARAMETERS (AUTO=ICH70001I 477 ICH70001I SE51045 LAST ACCESS AT 07:59IEF403I 476 IEF403I SE51045B - STARTED - TIME=08.03


Figure 94. Example of an MAA Most Frequent Messages With Text, Daily report



Report IDMAA07


SourceMSG_SYSLOG_D







MAA Most Frequent Messages by Type (JES2), Daily report:MAA Most Frequent Messages by Type (JES2), Daily report

This report shows the most frequent messages in your JES2 system grouped bytype (for example CICS, MVS, RACF®).


Report IDMAA08


MAA Most Frequent Nonsuppressed Messages, DailyJES Complex: ’JES2COMP’ Period: ’PRIME’

Date: ’2000-01-15’ to ’2000-01-15’

Message MessageID count Message text

---------- ---------- -----------------------------------------CCC0000 1279 SE ’08.00.03 JOB00038 $HASP165 SE51045L010/001 536 *010/001 -K -KIS-ENTER PARAMETERS (AUTO=IEA989I 471 IEA989I SLIP TRAP ID=X33E MATCHEDHASP308 334 $HASP308 VPWPROD ESTIMATED TIME EXCEEDHASP530 329 $HASP530 FI72340 ON L5.ST1 1,0IEF196I 257 IEF196I IEF237I JES2 ALLOCATED TO SYSLOEDG6627A 196 *EDG6627A MA M 052B V(K10900) R(K10900)IOS000I 188 IOS000I 52B,89,NCA,02,0600,,**,,INIT348EDG6642I 185 EDG6642I VOLUME K10900 LABELLED SUCCESSEDG6622I 183 EDG6622I VOLUME K10900 INITIALIZATION S


Figure 95. Example of an MAA Most Frequent Nonsuppressed Messages, Daily report






Message typeThe message type assigned for the first three characters of the SYSLOGmessage ID.




Suppressed (%)The percentage of the total number of messages for this message type thatwere suppressed.




MAA Most Frequent Messages by Type (JES3), Daily report:MAA Most Frequent Messages by Type (JES3), Daily report

This report shows the most frequent messages in your JES3 system grouped bytype (for example CICS, MVS, RACF).

MAA Most Frequent Messages by Type (JES2), DailyJES Complex: ’JES2COMP’ Period: ’PRIME’

Date: ’2000-01-15’Messages Single Multi Lines per

Message Message of total Suppressed Suppressed line line multilinetype count (%) messages (%) messages messages message

---------- -------- -------- ---------- ---------- -------- -------- ---------JES2 5449 31.9 4724 86.7 5388 61 5? 5227 30.6 3962 75.8 5168 59 4MVS 3460 20.3 2452 70.9 3184 276 5CMD 1427 8.4 148 10.4 1427 0 0RACF 929 5.4 774 83.3 781 148 2VTAM 177 1.0 18 10.2 172 5 4DB2 127 0.7 31 24.4 6 121 4AOC 114 0.7 92 80.7 114 0 0CICS 89 0.5 14 15.7 89 0 0IMS 56 0.3 0 0.0 56 0 0


Figure 96. Example of an MAA Most Frequent Messages by Type (JES2), Daily report



Report IDMAA09






Message typeThe message type assigned for the first three characters of the SYSLOGmessage ID.




Suppressed (%)The percentage of the total number of messages for this message type thatwere suppressed.

MAA Messages by Route Code (JES2), Daily report:

MAA Most Frequent Messages by Type (JES3), DailyJES Complex: ’JES3COMP’ Period: ’PRIME ’

Date: ’2000-01-15’

MessagesMessage Message of total Suppressed Suppressedtype count (%) messages (%)

---------- -------- -------- ---------- ----------JES3 51052 52.6 48094 94.2MVS 18753 19.3 18330 97.7RACF 8142 8.4 8142 100.0IMS 7801 8.0 7165 91.8CMD 5731 5.9 0 0.0? 4910 5.1 2783 56.7VTAM 210 0.2 20 9.5USER 205 0.2 205 100.0HSM 110 0.1 34 30.9CICS 74 0.1 31 41.9DB2 53 0.1 42 79.2NETV 27 0.0 0 0.0ANO 16 0.0 0 0.0


Figure 97. Example of an MAA Most Frequent Messages by Type (JES3), Daily report


MAA Messages by Route Code (JES2), Daily report

This report shows which route codes are used in a JES2 system. For moreinformation on using this report, refer to the System Performance Feature Guide.


Report IDMAA10






Route codeThe SYSLOG message route code. This is a translation of a 7-byte field intoa more readable code. For example 010207, means route codes 01, 02, 07and is a translation of C200000. SUPP is the group identifier for suppressedmessages.




MAA Messages by Route Code (JES2), DailyJES Complex: ’JES2COMP’ Period: ’PRIME ’

Date: 2000-01-15

Messages Single Multi Lines perRoute Message of total line line multilinecode count (%) messages messages message---------- -------- -------- -------- -------- ---------

SUPP 12229 71.6 11855 374 500 2245 13.1 2233 12 908 923 5.4 919 4 2-OTHER- 621 3.6 339 282 303 383 2.2 383 0 00102 355 2.1 355 0 011 135 0.8 135 0 0ALL 94 0.6 94 0 002 35 0.2 34 1 20810 18 0.1 18 0 00208 10 0.1 10 0 00211 8 0.0 8 0 0


Figure 98. Example of an MAA Messages by Route Code (JES2), Daily report




MAA Messages by Route Code (JES3), Daily report:MAA Messages by Route Code (JES3), Daily report

This report shows which route codes are used in a JES3 system.


Report IDMAA11






Route codeThe SYSLOG message route code. SUPP is the group identifier forsuppressed messages.


MAA Messages by Route Code (JES3), DailyJES Complex: ’JES3COMP’ Period: ’PRIME ’

Date: 2000-01-15

MessagesRoute Message of totalcode count (%)---------- -------- --------

SUPP 84846 87.49609 9.9

D9 826 0.9TP 803 0.8M4 323 0.3UR 301 0.3D4 150 0.2M5 86 0.1S32 86 0.1JES 36 0.0D5 11 0.0ALL 5 0.0LOG 2 0.0


Figure 99. Example of an MAA Messages by Route Code (JES3), Daily report



MAA Messages by JES Complex, Daily report:MAA Messages by JES Complex, Daily report

This report shows the total number of messages for each JES complex.


Report IDMAA12


SourceMSG_SYSLOG_D


VariablesFrom_date, To_date, Period_name


JES complexThe name of the JES complex.



Suppressed (%)The percentage of messages that were suppressed.

MAA Messages Suppressed, Monthly Trend report:MAA Messages Suppressed, Monthly Trend report

This report shows a monthly trend for suppressed messages in your system.


Report IDMAA13

MAA Messages by JES Complex, DailyPeriod: ’PRIME ’

Date: ’2000-01-15’ to ’2000-01-15’

JES Message Suppressed Suppressedcomplex count messages (%)---------- -------- ---------- ----------JES3COMP 97084 84846 87.4JES2COMP 17077 12229 71.6


Figure 100. Example of an MAA Messages by JES Complex, Daily report



SourceMSG_SYSLOG_M

AttributesMessage, Operation, Console, ID, SYSLOG, JES2, JES3, Monthly

VariablesFrom_month, To_month, JES_complex, Period_name


MonthThe date of the first day of the month.

Nonsuppressed messages (1000)The number of nonsuppressed messages, in thousands.

Suppressed messages (1000)The number of suppressed messages, in thousands.

NetView reportsThese reports give you NetView message information. The reports includeinformation on the most frequent messages in the NetView log, the messagespassed to NetView through the SSI, and the number of messages generated byeach NetView operator.

MAA Most Frequent Messages (NetView), Daily report:MAA Most Frequent Messages (NetView), Daily report

This report shows the most frequent messages in the NetView log.


Report IDMAA14


SourceMSG_NETVIEW_D, MSG_NETVIEW_DV

AttributesMessage, Operation, Console, ID, Log, Netview, Daily

VariablesDate, Netview_domain, Period_name, Maxrows



Message IDThe message ID for the message in the NetView log.



MAA Messages Passed via the SSI (NetView), Daily report:MAA Messages Passed via the SSI (NetView), Daily report

This report shows the messages passed to NetView through the SSI.


Report IDMAA15





MAA Most Frequent Messages (NetView), DailyNetView Domain: ’FSMZA’ Period: ’PRIME ’

Date: ’2003-08-17’

MessagesMessage Message of total

ID count (%)---------- -------- --------GWREQ 200 6.4CNM493I 195 6.2EVJEAB07 195 6.2HASP308 194 6.2HASP373 146 4.6EXIT 144 4.6HASP395 124 3.9ASSIGN 104 3.3


Figure 101. Example of an MAA Most Frequent Messages (NetView), Daily report



Message IDThe message ID for the message in the NetView log.



MAA Messages by NetView Operator (NetView), Daily report:MAA Messages by NetView Operator (NetView), Daily report

This report shows the number of messages generated by each NetView operator.


Report IDMAA16





MAA Messages Passed via the SSI (NetView), DailyNetView Domain: ’FSMZA’ Period: ’PRIME ’

Date: ’2003-08-17’

MessagesMessage Message of total

ID count (%)---------- -------- --------HASP308 194 6.2HASP373 146 4.6HASP395 124 3.9HASP500 47 1.5HASP530 36 1.1IEF452I 5 0.2HASP301 2 0.1AOF206I 2 0.1AOF256I 2 0.1AOF532I 2 0.1


Figure 102. Example of an MAA Messages Passed via the SSI (NetView), Daily report



NetView operatorThe NetView operator.



Tivoli Workload Scheduler for z/OS (OPC) componentCustomizationv Making input data availablev Modifying DRLJCOLLv Modifying DRLJOPCPv Updating lookup tables



Data tables, views, and lookup tablesv Data tables

– OPC_AUTO_EVENT_D, _M– OPC_CURRENT_PLAN_D, _M– OPC_MCP_D, _M– OPC_MISSED_FB_D, _M– OPC_OPER_EVENT_D, _M– OPC_OPER_EVENT_T

v Views– OPC_OPER_EVENT_DV1

MAA Messages by NetView Operator (NetView), DailyNetView Domain: ’FSMZA’ Period: ’PRIME ’

Date: 2003-08-17

MessagesNetView Message of totaloperator count (%)---------- -------- --------AUTO3 1399 44.5AUTJES 607 19.3GATFSMZA 293 9.3AUTMSG 279 8.9LOG 113 3.6GATFSDZA 91 2.9AUTO2 86 2.7AUTSYS 67 2.1AUTO1 66 2.1AUTMON 40 1.3


Figure 103. Example of an MAA Messages by NetView Operator (NetView), Daily report


– OPC_OPER_EVENT_DV2– OPC_OPER_EVENT_DV3– OPC_OPER_EVENT_MV1– OPC_OPER_EVENT_MV2– OPC_OPER_EVENT_MV3

v Lookup tables– OPC_WORKSTATION

Reportsv OPC operation events summary reports

– OPC Operations Ended-in-error by Workstation report– OPC Operations Ended-in-error by Error Code report– OPC Operation Events by Application Owner ID report

v OPC operation events detail report– OPC Operation Complete/Ended-in-error Events report

v OPC execution history for specific job name report– OPC Operations for Specific Job Name report

v OPC modify current plan events summary reports– OPC Reruns per Application, Worst Case report– OPC Number of Reruns, Monthly Trend report– OPC MCP Events per Caller, Monthly Overview report

v OPC missed-feedback report– OPC Missed-Feedback Operations, in Percent report

v OPC automatic workstation events report– OPC Number of Jobs Processed, Monthly Trend report

v OPC processing and tracking times reports– OPC Tracking Times by Event Type, Daily Trend report

v OPC service-level reports– OPC Missed Deadline by Application Owner ID report– OPC Late-Job Statistics by Application Owner ID report– OPC Reruns by Operation Number, Worst Case report

CustomizationBefore you can use the Tivoli Workload Scheduler for z/OS (OPC) component tocollect data and create useful reports, you must customize and test the installation.This chapter describes the steps you must perform to customize the TivoliWorkload Scheduler for z/OS (OPC) component:1. Making input data available.2. Modifying DRLJCOLL.3. Modifying DRLJOPCP.4. Updating lookup tables.

Making input data availableThe Tivoli Workload Scheduler for z/OS track log is created by the TivoliWorkload Scheduler for z/OS daily planning extend or replan batch jobs. The tracklog should be written to the file EQQTROUT with disposition MOD.


To contain completed and deleted occurrences, type 03 records should be createdwith the option OPCTROUT(CMP), which is specified in the BATCHOPTinitialization statement for the OPC batch job.

Each data table for the OPC component has a column called OPC_SYSTEM_ID.This ID is set with the LOGID parameter of the BATCHOPT initializationstatement. If data from more than one OPC system is to be collected into TivoliDecision Support for z/OS, the LOGID parameter must be set to a unique valuefor each OPC system to differentiate between the logs from the different systems.The default ID is 01.

For more information on the BATCHOPT statement, see the IBM Tivoli WorkloadScheduler for z/OS: Customization and Tuning manual.

Modifying DRLJCOLLBefore running the Tivoli Decision Support for z/OS collect job, you must updatethe DRLJCOLL job (a member in the DRLxxx.SDRLCNTL library) to include thecollection of OPC log data sets. Follow the instructions in the comments section ofthis job to modify the appropriate JCL statements.

Modifying DRLJOPCPBefore running your purge job for the OPC tables, run the OPC componentpurge-preparation job DRLJOPCP (a member in the DRLxxx.SDRLCNTL library).The DRLJOPCP job contains a utility program that flags which rows to purge inthe OPC_OPER_EVENT_T table. For example, in the statement:%DRLEOPCP KEEP=5 OPC_SYSTEM_ID=01 SQLMAX=50000

the KEEP parameter specifies the number of rows for the same event (job) thatshould not be purged. (See also OPC_OPER_EVENT_T for more information.)

Before running DRLJOPCP, you must modify the job statements according to theinstructions in its comments section.

Updating lookup tablesThe OPC component uses one lookup table when updating tables in the TivoliDecision Support for z/OS database. Using the administration dialog, update thistable with the values to be used in your installation:

Table name Description Key column Data column

OPC_WORKSTATION Defines the type of workstation foreach OPC workstation name.

WORKSTATION_NAME WORKSTATION_TYPE

The OPC component also uses the DAY_OF_WEEK, PERIOD_PLAN, andSPECIAL_DAY control tables to update the data tables. Ensure that these tablesinclude the correct information. Refer to the Administration Guide and Reference forinformation on the control tables.

For a complete description of the OPC_WORKSTATION lookup table and anexample of its contents, see OPC_WORKSTATION.



Data flowThe Tivoli Workload Scheduler for z/OS (OPC) component collects TivoliWorkload Scheduler for z/OS track log data and stores the data in the TivoliDecision Support for z/OS database. You can then use the reporting dialog tocreate reports based on this data. Figure 104 shows an overview of the flow of datafrom the Tivoli Workload Scheduler for z/OS licensed program, through the TivoliWorkload Scheduler for z/OS (OPC) component, and finally into reports.

Storing the dataAfter collecting the data, the Tivoli Workload Scheduler for z/OS (OPC)component stores the data in data tables in the Tivoli Decision Support for z/OSdatabase. As it updates the tables, the component uses the OPC_WORKSTATIONlookup table to convert the Tivoli Workload Scheduler for z/OS workstation nameto a workstation type. Figure 105 shows which data tables contain values from thelookup table.

Figure 104. Tivoli Workload Scheduler for z/OS (OPC) component data flow


The Tivoli Workload Scheduler for z/OS (OPC) component uses theDAY_OF_WEEK, PERIOD_PLAN, and SPECIAL_DAY control tables to update thedata tables. For information on the control tables, refer to the Administration Guideand Reference.

For detailed information about the data tables the component updates and thelookup table it uses, see Data tables, views, and lookup tables.

Log and record definitionsThe Tivoli Workload Scheduler for z/OS (OPC) component extracts historicalinformation from the Tivoli Workload Scheduler for z/OS track log. TivoliWorkload Scheduler for z/OS job tracking works correctly only if it receivesinformation about status changes for all jobs or started tasks to be tracked. Jobtracking gets this information from SMF and JES exits.

The Tivoli Workload Scheduler for z/OS (OPC) component processes these TivoliWorkload Scheduler for z/OS track log records:

Table 7. Table 7. Input records to the Tivoli Workload Scheduler for z/OS (OPC) component

Tivoli Workload Scheduler for z/OS record Record definition Description

TRLBDY23 OPC_23 Track-log operation event. Thisjob-tracking record documentsTivoli Workload Scheduler forz/OS operation eventsprocessed at workstations.

TRLBDY24 OPC_24 Track-log modify-current-planevent. This job-tracking recorddocuments Tivoli WorkloadScheduler for z/OS MCPevents that occur atworkstations.

TRLBDY27 OPC_27 Track-log missed-feedbackrecord. This job-tracking recorddocuments Tivoli WorkloadScheduler for z/OSmissed-feedback operationevents.

TRLBDY29 OPC_29 Track-log auto-tracked event.This job-tracking recorddocuments Tivoli WorkloadScheduler for z/OS automaticoperation events and TivoliWorkload Scheduler for z/OSinternal processing andtracking times.

Figure 105. Tivoli Workload Scheduler for z/OS (OPC) lookup table data


Table 7. Table 7. Input records to the Tivoli Workload Scheduler for z/OS (OPC) component (continued)

Tivoli Workload Scheduler for z/OS record Record definition Description

CPLREC3C OPC_03_C Current plan record type 3C(valid only from OPC/ESAversion 2.1), occurrence record.This documents the attempts toprocess an application in theTivoli Workload Scheduler forz/OS current plan.

CPLREC3P OPC_03_P Current plan record type 3P(valid only from OPC/ESAversion 2.1), operation record.This documents each operationin an application in the TivoliWorkload Scheduler for z/OScurrent plan.

CPLREC04 OPC_04 Current plan record type 4(valid only from OPC/ESAversion 2.1), job name table.This documents the job nametable record associated with anoperation in the TivoliWorkload Scheduler for z/OScurrent plan.

For a complete description of these records, see the Tivoli Workload Scheduler forz/OS: Programming Interfaces and Tivoli Workload Scheduler for z/OS: Diagnosis Guideand Reference.

Data tables, views, and lookup tablesThis chapter describes the data tables, views, and lookup table used by the TivoliWorkload Scheduler for z/OS (OPC) component. For descriptions of control tablesused by the Tivoli Workload Scheduler for z/OS (OPC) component, see theAdministration Guide.

Data tablesThis section describes the data tables for the Tivoli Workload Scheduler for z/OS(OPC) component.

OPC_AUTO_EVENT_D, _M:OPC_AUTO_EVENT_D, _M

These tables provide daily and monthly statistics on Tivoli Workload Scheduler forz/OS automatic operation events. They contain data from the Tivoli WorkloadScheduler for z/OS track log record 29, which gives information on TivoliWorkload Scheduler for z/OS internal processing and tracking times.


OPC_AUTO_EVENT_D30 days

OPC_AUTO_EVENT_M765 days



DATE K DATE Date when the automatic operation events wereprocessed. For the _M table, this is the date of thefirst day of the month. From TRLEVDAT.

PERIOD_NAME K CHAR(8) Name of the period. This is derived using fieldsTRLLOGID, TRLEVDAT, and TRLEVTIM from therecord as parameters in the PERIOD function.

OPC_SYSTEM_ID K CHAR(2) ID of the Tivoli Workload Scheduler for z/OS system,which is specified with the LOGID parameter of theBATCHOPT initialization statement for TivoliWorkload Scheduler for z/OS' own batch jobs. FromTRLLOGID.

OPC_NODE K CHAR(8) Tivoli Workload Scheduler for z/OS node name. Thiscan be the VTAM application ID, the XCF membername, or $LOCAL if EQENODE is 0. FromEQERELDD.

AUTO_EVENT_TYPE K CHAR(3) Automatic-event type generated by Tivoli WorkloadScheduler for z/OS for both jobs and started tasks.From EXRTYPE and EXRSTYPE. This can be one ofthese event types:

Event typeDescription

x1 Reader event. A job has entered the JESsystem.

x2 Job start event. A job has started to execute.

x3S Step end event. A job step has finishedexecuting.

x3J Job end event. A job has finished executing.

x3P Job termination event. A job has been addedto the JES output queues.

x4 Print event. A group of SYSOUT data setshas been purged from the JES system.

x5 Purge event. A job has been purged from theJES system.

x (the first byte in the exit record) is A if the eventwas created on a JES 2 system, or B if the event wascreated on a JES 3 system.

EVENT_READER K INTEGER Event reader number. From EQERDRN.

EVENTS INTEGER Number of automatic operation events. This is thecount of TRLEVDAT.

MVS_SYSTEM_ID CHAR(4) The Tivoli Workload Scheduler for z/OS MVS systemID, as indicated in the collect job.

PROCESSING_NODE CHAR(8) Network job entry (NJE) processing node name. Thisis present only for job start events (A2 or B2). FromEXRNNJE.



PROCESS_TOT_SEC FLOAT Total Tivoli Workload Scheduler for z/OS processingtime, in seconds. This is the time that elapsed fromthe time an event was written to an event data set tothe time Tivoli Workload Scheduler for z/OS finishedprocessing the event. This column is valid only if thetwo timestamps used to calculate the process time aretaken from the same processor or if the processorclocks involved are synchronized in a sysplexenvironment. Calculated as the sum of (TRLEVDATand TRLEVTIM) - (EXRDATE and EXRTIME).

TRACK_TOT_SEC FLOAT Total tracking time, in seconds. This is the total timethat elapsed from the time an automatic operationevent occurred to the time the event record waswritten to an event data set. Calculated as the sum of(EXREDATE and EXRETIME) - (EXRDATE andEXRTIME); or (EXRSDATE and EXRSTIME) -(EXRDATE and EXRTIME); or (EXRRDATE andEXRRTIME) - (EXRDATE and EXRTIME).

OPC_CURRENT_PLAN_D, _M:OPC_CURRENT_PLAN_D, _M

These tables provide daily and monthly statistics on application occurrences andoperations in the Tivoli Workload Scheduler for z/OS current plan. It contains datafrom the Tivoli Workload Scheduler for z/OS current-plan record type 3C(CPLREC3C) and type 3P (CPLREC3P), which are valid only from OPC/ESAversion 2.1.

These tables are updated by the OPC_WORKSTATION lookup table.


OPC_CURRENT_PLAN_D30 days

OPC_CURRENT_PLAN_M765 days


DATE K DATE Date when the application occurrences or operationswere processed. For the _M table, this is the date ofthe first day of the month. From CPLIADOC orCPLIADOP.

PERIOD_NAME K CHAR(8) Name of the period. This is derived using fieldsTRLLOGID, CPLIADOC, and CPLIATOC from therecord as parameters in the PERIOD function.


APPL_OWNER_ID K CHAR(16) Application owner ID. This is set to $MISSING foroperations. From CPLOIDOC.

APPLICATION_ID K CHAR(16) Application ID related to the occurrence or operation.From CPLADIOC or CPLADIOP.



PRIORITY K CHAR(1) Priority of the application occurrence or operation.From CPLPRIOC or CPLPRIOP.

EVENT_TYPE K CHAR(1) Application occurrence or operation event type (C orP). From CPLEYE3P or CPLEYE3C.

WORKSTATION_TYPE K CHAR(8) Type of workstation for the operation event. This isset to $MISSING for application occurrences. FromWORKSTATION_TYPE in the OPC_WORKSTATIONlookup table. This is derived using fields TRLLOGIDand CPLWSOP from the record as key.

DEADLINE_MISSES FLOAT Number of application occurrences or operations thatwere late. This is the number of records whereCPLACDOC and CPLACTOC are greater thanCPLDLDOC and CPLDLTOC, or where CPLAEDOPand CPLAETOP are greater than CPLPEDOP andCPLPETOP.

JOBS_DELETED FLOAT Total number of deleted jobs. This is the count of statecode D in CPLCSTOP.

JOBS_FAILED FLOAT Total number of failed jobs. This is the count of statecode E in CPLCSTOP.


OCCUR_TOTAL FLOAT Total number of occurrences or operations. This is thecount of CPLIADOC or CPLIADOP.

OPC_MCP_D, _M:OPC_MCP_D, _M

These tables provide daily and monthly statistics on Tivoli Workload Scheduler forz/OS modify current plan (MCP) events. They contain data from the TivoliWorkload Scheduler for z/OS track log record type 24 (TRLBDY24).


OPC_MCP_D30 days

OPC_MCP_M765 days


DATE K DATE Date when the MCP operation events were processed.For the _M table, this is the date of the first day ofthe month. From TRLEVDAT.



APPLICATION_NAME K CHAR(16) Name of the application. From MT0AID.



MCP_TYPE K CHAR(18) Description of the type of MCP function. FromMT0TYPE. This can be one of these:

DescriptionType code

OCCURRENCE ADD1

OCCURRENCE RERUN2

OCC/OP DATA CHANGE3

OCCURRENCE DELETE4

CHANGE REPORT ATTR6

SET OPER TO WAIT7

SET OPER TO COMP8

VARY WS STATUS9

GROUP MODIFICATIONG

UNKNOWN MCP TYPENot 1-8

JOB_NAME K CHAR(8) Name of the job. If the job name cannot be obtained,this is set to $MISSING. For OCCURRENCE RERUNevents, the job name can only be obtained in somecases. From MTDJOBN.

OPERATION_NO K INTEGER Operation number for OCCURRENCE RERUNevents. For all other events, this is set to 0. FromMTDOPER2.

APPC_CALLS INTEGER Number of APPC subtasks attached by the systemtask, where MT0CALLER is C.

ARC_CALLS INTEGER Number of autorecovery calls to the MCP. This is thenumber of records where MCPCALLER is A.

DLG_CALLS INTEGER Number of dialog calls to the MCP. This is thenumber of records where MCPCALLER is blank ormissing.

ETT_CALLS INTEGER Number of event triggered tracking (ETT) calls to theMCP. This is the number of records whereMCPCALLER is E.

JSCRER_CALLS INTEGER Number of occurrences rerun from JSC, whereMT0CALLER is J.

MCP_EVENTS INTEGER Number of MCP events that occurred. This is thecount of TRLEVDAT.

MVS_SYSTEM_ID CHAR(4) The OPC MVS System ID as indicated in the collectjob.



PIF_CALLS INTEGER Number of program interface (PIF) calls to the MCP.This is the number of records where MCPCALLER isP.

OPC_MISSED_FB_D, _M:OPC_MISSED_FB_D, _M

These tables provide daily and monthly statistics on Tivoli Workload Scheduler forz/OS missed-feedback events by application and workstation. They contain datafrom the Tivoli Workload Scheduler for z/OS track log record type 27 (TRLBDY27).


OPC_MISSED_FB_D30 days

OPC_MISSED_FB_M765 days


DATE K DATE Date when the missed-feedback operation events wereprocessed. For the _M table, this is the date of thefirst day of the month. From TRLEVDAT.



APPLICATION_NAME K CHAR(16) Name of the application. From TRLAID27.

WORKSTATION_NAME K CHAR(4) Name of the workstation. From TRLOID27 (first 4characters).

MISSED_FB_EVENTS INTEGER Number of missed-feedback events. This is the countof TRLEVDAT.


OPER_ABOVE_LIMIT INTEGER Number of operations whose durations were abovethe limit for feedback. This is the count of recordswhere the sum of (TRLEDUH27*60) + TRLEDUM27 isless than the sum of (TRLADUH27*60) +TRLADUM27.

OPER_BELOW_LIMIT INTEGER Number of operations whose durations were belowthe limit for feedback. This is the count of recordswhere the sum of (TRLEDUH27*60) + TRLEDUM27 isgreater than the sum of (TRLADUH27*60) +TRLADUM27.

OPC_OPER_EVENT_D, _M:


OPC_OPER_EVENT_D, _M

These tables provide daily and monthly statistics on Tivoli Workload Scheduler forz/OS operation events processed at workstations. They contain consolidated datafrom the OPC_OPER_EVENT_T table, which contains data from the TivoliWorkload Scheduler for z/OS track log record type 23 (TRLBDY23).


OPC_OPER_EVENT_D30 days

OPC_OPER_EVENT_M765 days


DATE K DATE Date when the operation events were processed. Forthe _M table, this is the date of the first day of themonth. From TRLEVDAT.



APPL_OWNER_ID K CHAR(16) Application owner ID. From TRLOWI23.

WORKSTATION_NAME K CHAR(4) Name of the workstation. From TRLWSN23.

OPERATION_EVENT K CHAR(1) Code for the type of operation event processed. FromTRLEVT23. This can be one of these:

Oper event codeDescription

A Wait for arrival

C Completed

E Ended-in-error

I Interrupted

R Ready

S Started

U Undecided

W Waiting

X Reset

* Rdy prev ws nonrep

Not any of aboveUnknown

ERROR_CODE K CHAR(4) Reported error code for the operation eventprocessed. From TRLERC23.



DURATION_TOT_HOURS FLOAT Total duration of the operation events processed, inhours. Calculated as the sum of TRLDURH23 +TRLDURM23/60, where TRLDURH23 is the first 4characters of TRLDUR23, and TRLDURM23 is the last2 characters of TRLDUR23.

MVS_SYSTEM_ID CHAR(4) The Tivoli Workload Scheduler for z/OS MVS systemID as indicated in the collect job.

OPERATIONS_TOT FLOAT Total number of operation events processed. This isthe count of records where TRLEVT23 is E(Ended-in-error) or C (Completed).

OPC_OPER_EVENT_T:OPC_OPER_EVENT_T

This table provides detailed information about Tivoli Workload Scheduler for z/OSoperation events processed at workstations. It contains data from the TivoliWorkload Scheduler for z/OS track log record type 23 (TRLBDY23).

The default retention periods for this table are:v All operation events are retained for at least 7 days.v All operation events that ended in error are retained for at least 45 days.v The maximum retention period for all operation events is 765 days.v A specified number of rows for the same event (job) is always retained. This is

set by the DRLEOPCP utility program contained in the DRLJOPCPpurge-preparation job.


TIMESTAMP K TIMESTAMP Date and time when the operation event wasprocessed. From TRLEVDAT and TRLEVTIM.



APPLICATION_NAME K CHAR(16) Application name. From TRLADI23.



DURATION_HOURS FLOAT Reported duration of the operation event processed,in hours. Calculated as TRLDURH23 +TRLDURM23/60, where TRLDURH23 is the first 4characters of TRLDUR23, and TRLDURM23 is the last2 characters of TRLDUR23.

ERROR_CODE CHAR(4) Reported error code for the operation eventprocessed. From TRLERC23.

JOB_NAME CHAR(8) Name of the job that was processed. From TRLJBN23.

MVS_SYSTEM_ID CHAR(4) The Tivoli Workload Scheduler for z/OS MVS systemID as indicated in the collect job.



OPERATION_EVENT CHAR(1) Code for the type of Tivoli Workload Scheduler forz/OS operation event processed. From TRLEVT23.This can be one of these:


A Wait for arrival

C Completed

E Ended-in-error

I Interrupted

R Ready

S Started

U Undecided

W Waiting

X Reset



OPER_STATUS_DESCR VARCHAR(18) Description of the code for the operation status(operation event) at the workstation. From TRLEVT23.This can be one of these:

DescriptionOper status code

Wait for arrivalA

CompletedC

Ended-in-errorE

InterruptedI

Ready R

Started S

UndecidedU

WaitingW

Reset X

Rdy prev ws nonrep*

UnknownNot any of above



PURGE_FLAG CHAR(1) Flag for setting the purge condition for this table. Thiscan be 1 or 0 but is initially set to 0. The utilityprogram DRLEOPCP contained in the TivoliWorkload Scheduler for z/OS (OPC) componentpurge-preparation job DRLJOPCP can set this flag to 1for all but the latest specified number of rows for thesame event (job).

ViewsThis section describes the views for the Tivoli Workload Scheduler for z/OS (OPC)component.

OPC_OPER_EVENT_DV1:OPC_OPER_EVENT_DV1

This view provides daily statistics on the total number of Tivoli WorkloadScheduler for z/OS operation events and the total duration hours for these eventsper workstation. It is based on the OPC_OPER_EVENT_D table.


DATE K DATE Date when the operation events were processed. FromTRLEVDAT.


OPC_SYSTEM_ID K CHAR(2) ID of the Tivoli Workload Scheduler for z/OS system,which is specified with the LOGID parameter of theBATCHOPT initialization statement for TivoliWorkload Scheduler for z/OS’ own batch jobs. FromTRLLOGID.


Note: Aside from the key columns described here, this view also contains all thedata columns described in OPC_OPER_EVENT_D, _M.


This view provides daily statistics on the total number of Tivoli WorkloadScheduler for z/OS operation events and the total duration hours for these eventsper workstation and error code. It is based on the OPC_OPER_EVENT_D table.










A Wait for arrival

C Completed

E Ended-in-error

I Interrupted

R Ready

S Started

U Undecided

W Waiting

X Reset



ERROR_CODE K CHAR(4) Reported error code for the operation eventprocessed. From TRLERC23.



This view provides daily statistics on the total number of Tivoli WorkloadScheduler for z/OS operation events and the total duration hours for these events.It is based on the OPC_OPER_EVENT_D table.







OPC_OPER_EVENT_MV1:OPC_OPER_EVENT_MV1

This view provides monthly statistics on the total number of operation events andthe total duration hours for these events per application owner. It is based on theOPC_OPER_EVENT_M table.


DATE K DATE Date when the operation events were processed. Thisis the date of the first day of the month. FromTRLEVDAT.






This view provides monthly statistics on the total number of operation events andthe total duration hours for these events per application owner. It is based on theOPC_OPER_EVENT_M table.











A Wait for arrival

C Completed

E Ended-in-error

I Interrupted

R Ready

S Started

U Undecided

W Waiting

X Reset





This view provides monthly statistics on the total number of operation events andthe total duration hours for these events. It is based on the OPC_OPER_EVENT_Mtable.






Lookup tablesThis section describes the lookup table specific to the Tivoli Workload Schedulerfor z/OS (OPC) component.

OPC_WORKSTATION:


OPC_WORKSTATION

This lookup table defines the type of workstation for each Tivoli WorkloadScheduler for z/OS workstation name. Only workstations of type CPU need to bedefined in this table.

This table updates the OPC_CURRENT_PLAN_D and OPC_CURRENT_PLAN_Mtables.


OPC_SYSTEM_ID K CHAR(2) ID of the Tivoli Workload Scheduler for z/OS system.This can contain global search characters.

WORKSTATION_NAME K CHAR(4) Tivoli Workload Scheduler for z/OS workstationname. This can contain global search characters.

DESCRIPTION VARCHAR(32) Description of the node.

WORKSTATION_TYPE CHAR(8) Tivoli Workload Scheduler for z/OS workstation type.

Example of table contentsOPCSYSTEM WORKSTATION WORKSTATION

ID NAME TYPE DESCRIPTION------ ----------- ------------ --------------------------% _CPU CPU The biggest mainframe% CPU_ CPU Another mainframe% _PRT PRT All printer workstations% % OTHER All other workstations

ReportsThe Tivoli Workload Scheduler for z/OS (OPC) component provides the followingreports:v OPC operation events summary reports

– OPC Operations Ended-in-error by Workstation report– OPC Operations Ended-in-error by Error Code report– OPC Operation Events by Application Owner ID report

v OPC operation events detail report– OPC Operation Complete/Ended-in-error Events report

v OPC execution history for specific job name report– OPC Operations for Specific Job Name report

v OPC modify current plan events summary reports– OPC Reruns per Application, Worst Case report– OPC Reruns by Operation Number, Worst Case report– OPC Number of Reruns, Monthly Trend report– OPC MCP Events per Caller, Monthly Overview report

v OPC missed-feedback report– OPC Missed-Feedback Operations, in Percent report

v OPC automatic workstation events report– OPC Number of Jobs Processed, Monthly Trend report

v OPC processing and tracking times statistics report– OPC Tracking Times by Event Type, Daily Trend report

v OPC service-level reports


– OPC Missed Deadline by Application Owner ID report– OPC Late-Job Statistics by Application Owner ID report

OPC operation events summary reportsThe OPC operation events summary reports show statistics on operations thatended in error and operations that completed.

OPC Operations Ended-in-error by Workstation report:OPC Operations Ended-in-error by Workstation report

This report shows statistics on Tivoli Workload Scheduler for z/OS operationevents that ended in error. It shows the data per day and period, and byworkstation.


Report IDOPC01

Report groupTivoli Workload Scheduler for z/OS (OPC) reports

SourceOPC_OPER_EVENT_D, OPC_OPER_EVENT_DV1

AttributesOPC, Operations, Workstation, Overview

VariablesFrom_date, To_date, Period_name, OPC_system ID, Workstation_name


OPC Operations Ended-in-error by WorkstationOPC System: ’01’

DurationPeriod Work- Operations tot Operations Duration

Date name station tot (hours) (%) (%)---------- -------- -------- ---------- ---------- ---------- --------2003-07-13 NIGHT MBRA 1 0.12 0.9 0.1

MCPU 2 1.72 0.3 4.4MONL 3 2.77 1.9 10.4

PRIME MCPU 8 0.17 4.0 1.4MONL 3 8.48 2.6 76.0

2003-07-14 NIGHT MBRA 2 19.30 1.9 6.1MCPU 2 0.03 0.6 0.2

PRIME MBRA 5 0.27 3.1 0.7MCPU 10 0.35 4.0 3.8

•••

2004-02-17 NIGHT CPU1 4 0.05 6.3 5.1

Tivoli Decision Support for z/OS Report: OPC01

Figure 106. Example of an OPC Operations Ended-in-error by Workstation report


Date The date of the measurement. This is the date when the ended-in-erroroperation events occurred.

Period nameThe name of the period in which the ended-in-error operation eventsoccurred.

WorkstationThe name of the workstation on which the ended-in-error operation eventsoccurred.

Operations totThe total number of ended-in-error operation events processed for theworkstation.

Duration tot (hours)The total duration, in hours, of the ended-in-error operation eventsprocessed for the workstation.

Operations (%)The number of ended-in-error operation events processed for theworkstation, as a percentage of the total number of events that occurred onthis date, period, and workstation.

Duration (%)The duration of the ended-in-error operation events processed for theworkstation, as a percentage of the total duration of all events thatoccurred on this date, period, and workstation.

OPC Operations Ended-in-error by Error Code report:This report shows statistics on Tivoli Workload Scheduler for z/OS operationevents that ended in error. It shows the data per day and period, and by error codeand workstation.


Report IDOPC02


SourceOPC_OPER_EVENT_D, OPC_OPER_EVENT_DV1

AttributesOPC, Operations, Workstation, Error, Code

VariablesFrom_date, To_date, Period_name, OPC_system_ID, Workstation_name



Date The date of the measurement. This is the date when the ended-in-erroroperation events occurred.

Period nameThe name of the period in which the ended-in-error operation eventsoccurred.

WorkstationThe name of the workstation on which the ended-in-error operation eventsoccurred.

Error codeThe error code set by Tivoli Workload Scheduler for z/OS for theended-in-error operation event processed for the workstation.

Operations totThe total number of operation events with this error code that wereprocessed for the workstation.

Duration tot (hours)The total duration, in hours, of the operation events with this error codethat were processed for the workstation.

OPC Operations Ended-in-error by Error CodeOPC System: ’01’

DurationPeriod Work- Error Operations tot Error Duration

Date name station code tot (hours) (%) (%)---------- -------- ------- ----- ---------- -------- ------- --------2000-07-13 NIGHT MBRA 3333 1 0.12 0.9 0.1

MCPU 0012 1 0.35 0.2 0.91000 1 1.37 0.2 3.5

MONL 0009 1 0.02 0.6 0.10012 1 2.73 0.6 10.33333 1 0.02 0.6 0.1

PRIME MCPU SB37 3 0.05 1.5 0.40004 1 0.02 0.5 0.10012 2 0.07 1.0 0.63333 2 0.03 1.0 0.3

MONL U03F 1 0.02 0.9 0.11800 2 8.47 1.7 75.8

2000-07-14 NIGHT MBRA JCL 1 0.02 0.9 0.0S222 1 19.28 0.9 6.1

MCPU JCL 1 0.02 0.3 0.13333 1 0.02 0.3 0.1

•••


Figure 107. Example of an OPC Operations Ended-in-error by Error Code report


Error (%)The number of operation events with this error code that were processedfor this workstation, as a percentage of the total number of events thatoccurred on this date, period, and workstation.

Duration (%)The duration of the operation events with this error code that wereprocessed for the workstation, as a percentage of the total duration of allevents that occurred on this date, period, and workstation.

OPC Operation Events by Application Owner ID report:OPC Operation Events by Application Owner ID report

This report shows statistics on Tivoli Workload Scheduler for z/OS operationevents for a given month and period. It shows the data by application owner andworkstation.


Report IDOPC03


SourceOPC_OPER_EVENT_M, OPC_OPER_EVENT_MV3

AttributesOPC, Operations, Application, Owner, Workstation

VariablesMonth, Period_name, OPC_system_ID, Appl_owner_ID, Workstation_name



Application ownerThe application owner ID associated with the operation events.

WorkstationThe name of the workstation on which the operation events occurred.

Operation eventThe code for the type of operation event processed. This can be C for anoperation event that completed, or E for an operation event that ended inerror.

Operations totThe total number of operation events of this type that were processed forthe workstation and application owner.

Duration tot (hours)The total duration, in hours, of the operation events of this type that wereprocessed for the workstation and application owner.

Operations (%)The number of operation events of this type that were processed for theworkstation and application owner, as a percentage of the total number ofevents that occurred on this month and period.

Duration (%)The duration of the operation events of this type that were processed for

OPC Operation Events by Application Owner IDOPC System: ’01’

Month: ’2000-01-01’ Period: ’PRIME’

DurationApplication Work- Operation Operations tot Operations Duration

owner station event tot (hours) (%) (%)------------ ------- --------- ---------- -------- ---------- --------BMW MBRA C 2 0.22 0.1 0.1

---------- -------- ---------- --------** 2 0.22 0.1 0.1

CICS DUMM C 2 0.00 0.1 0.0MBRA C 17 0.28 0.5 0.1

---------- -------- ---------- --------** 19 0.28 0.5 0.1

ECODEX DUMM C 7 0.00 0.2 0.0MBRA C 4 86.00 0.1 29.8

---------- -------- ---------- --------** 11 86.00 0.3 29.8

STGL DUMM C 1 0.00 0.0 0.0IPOP C 1 0.00 0.0 0.0MBRA C 150 5.72 4.0 2.0

E 4 0.42 0.1 0.1USER C 4 0.00 0.1 0.0

---------- -------- ---------- --------** 160 6.13 4.3 2.1

TAYL MBRA C 2 0.03 0.1 0.0---------- -------- ---------- --------


Figure 108. Example of an OPC Operation Events by Application Owner ID report


the workstation and application owner, as a percentage of the totalduration of all events that occurred on this month and period.

OPC operation events detail reportThe OPC operation events detail report lists the operations that completed orended in error.

OPC Operation Complete/Ended-in-error Events report:OPC Operation Complete/Ended-in-error Events report

This report shows detailed statistics on Tivoli Workload Scheduler for z/OSoperation events that completed or ended in error. It shows the data by date andtime, and gives the workstation, application owner, and job name associated withthe operation event.


Report IDOPC04


SourceOPC_OPER_EVENT_T

AttributesOPC, Operations, Application, Workstation, Detail, Event

VariablesOperation_event, From_date, To_date, Workstation_name, Appl_owner_ID,Job_name, OPC_system_ID, Error_code.

Variables Appl_owner_ID and Job_name can contain global searchcharacters.

OPC Operation Complete/Ended-in-error EventsOPC System: ’01’

Operation Event: OPERATION_EVENT

ApplicationWork- owner Job Duration Error Operation

Date Time station ID name hours code event---------- -------- ------- ---------------- -------- -------- ----- ---------2003-09-07 00.03.04 MCPU 00/791 AB00265C 0.07 0000 C

00.03.04 MCPU 00/791 AC00265C 0.07 0000 C00.03.06 MCPU 01/030 VT03373 0.07 0000 C00.03.06 MCPU 01/030 VJ03373 0.07 0000 C00.14.47 MCPU 00/767 AT04117 0.37 0000 C00.16.19 MCPU 00/791 AJ00069Q 0.03 0000 C00.16.19 MCPU 00/791 AJ00069Q 0.03 0000 C00.16.31 MCPU 00/731 XJ00999 0.02 S0C4 E00.16.31 MCPU 00/731 XJ00999 0.02 S0C4 E00.16.35 MCPU 00/731 MG00901 0.02 0000 C

•••

Tivoli Decision Support for z/OS Report OPC04

Figure 109. Example of an OPC Operation Complete/Ended-in-error Events report



Date The date of the measurement. This is the date when the operation eventsoccurred.

Time The time of the measurement. This is the time when the operation eventoccurred.

WorkstationThe name of the workstation on which the operation event occurred.

Application owner IDThe application owner ID associated with the operation event processed.

Job nameThe name of the job associated with the operation event processed.

Duration hoursThe reported duration of the operation event processed, in hours.

Error codeThe error code set by Tivoli Workload Scheduler for z/OS for the operationevent processed.


OPC execution history for specific job name reportThe OPC execution history for specific job name report shows detailed statistics onoperation events processed for a specific job.

OPC Operations for Specific Job Name report:OPC Operations for Specific Job Name report

This report shows detailed statistics on Tivoli Workload Scheduler for z/OSoperation events for a specific job name. It shows the data by date and time, andgives the workstation and application name associated with the operation event.


Report IDOPC05


SourceOPC_OPER_EVENT_T

AttributesOPC, Operations, Application, Workstation, Jobs

VariablesFrom_date, To_date, Job_name, OPC_system_ID



Date The date of the measurement. This is the date when the operation eventoccurred.

Time The time of the measurement. This is the time when the operation eventoccurred.

WorkstationThe name of the workstation on which the operation event occurred.

Application nameThe name of the application associated with the operation event processed.


Error codeThe error code set by Tivoli Workload Scheduler for z/OS for the operationevent processed.

APPC (%)The number of APPC subtasks attached by the subsystem. Calculated as100 * APPC_CALLS / MCP_EVENTS.

JSCRER (%)The number of occurrences rerun from JSC. Calculated as 100 *JSCRER_CALLS / MCP_EVENTS.

OPC modify current plan events summary reportsThe OPC modify current plan events summary reports show the number of rerunsper application, and an overview of the MCP events processed per caller.

OPC Reruns per Application, Worst Case report:OPC Reruns per Application, Worst Case report

This report shows the number of reruns (from MCP events) that occurred for aselected time period. It shows the number of reruns per application in descendingorder.


Report IDOPC06


OPC Operations for Specific Job NameOPC System: ’01’Jobname: ’$$HKSLO’

Work- Application Operation Error Duration APPC JSCRERDate Time station name event code (hours) (%) (%)---------- -------- ------- ---------------- ---------- ----- ---------- ----- ------2000-07-13 14.10.50 MBRA $$HAKALOHN C 0000 0.15 2.1 1.02000-07-14 14.14.53 MBRA $$HAKALOHN E S214 0.22 0.0 0.02000-07-14 14.28.53 MBRA $$HAKALOHN E JCLI 0.00 0.0 0.0


Figure 110. Example of an OPC Operations for Specific Job Name report


SourceOPC_MCP_D

AttributesOPC, Operations, Worst, Case, Reruns, MCP

VariablesFrom_date, To_date, OPC_system_ID, Maxrows


Application nameThe name of the application on which the reruns were recorded.

RerunsThe number of reruns recorded for the application.

OPC Number of Reruns, Monthly Trend report:This graphic report shows the number of reruns (from MCP events) that occurredfor a selected month.


Report IDOPC07


SourceOPC_MCP_M

AttributesOPC, Graph, Operations, Trend, Reruns, MCP, Monthly

VariablesFrom_month, To_month, OPC_system_ID

OPC Reruns per Application, Worst CaseOPC System: ’01’

From date: ’2000-07-13’ To date: ’2000-07-15’

Applicationname Reruns

---------------- -----------AJEIBQTR 4AJ01462 3AJ02092 2AJ03868 2ICSCOMUPDATE 2SMFE 2


Figure 111. Example of an OPC Reruns per Application, Worst Case report



Month start dateThe date of the measurement. This is the date of the first day of the monthwhen the reruns occurred.

Number of rerunsThe number of reruns that occurred.

OPC MCP Events per Caller, Monthly Overview report:OPC MCP Events per Caller, Monthly Overview report

This report shows the distribution of MCP events per MCP type for a selectedmonth. Because MCP events are changes to the preplanned production, increasingnumbers of MCP events, specially reruns, give an early warning that the planningis not working well.


Report IDOPC08


Figure 112. Example of an OPC Number of Reruns, Monthly Trend report


SourceOPC_MCP_M

AttributesOPC, Operations, MCP, Events, Caller

VariablesFrom_month, To_month, OPC_system_ID


Month start dateThe date of the measurement. This is the date of the first day of the monthwhen the MCP events occurred.

MCP typeThe type of MCP event. This is a descriptive text of the MCP function codederived from the OPC_MCP_TYPE lookup table.

MCP eventsThe number of MCP events that occurred.

DLG (%)The number of dialog calls to the MCP, as a percentage of the number ofMCP events. Calculated as: 100 * DLG_CALLS / MCP_EVENTS.

ETT (%)The number of event triggered tracking calls to the MCP, as a percentageof the number of MCP events. Calculated as: 100 * ETT_CALLS /MCP_EVENTS.

PIF (%)The number of program interface calls to the MCP, as a percentage of thenumber of MCP events. Calculated as: 100 * PIF_CALLS / MCP_EVENTS.

ARC (%)The number of autorecovery calls to the MCP, as a percentage of thenumber of MCP events. Calculated as: 100 * ARC_CALLS /MCP_EVENTS.

OPC missed-feedback reportThe OPC missed-feedback report shows the percentage of missed-feedbackoperations that occurred at each workstation.

OPC Missed-Feedback Operations, in Percent report:

OPC MCP Events per Caller, Monthly OverviewOPC System: ’01’

Month MCP MCP DLG ETT PIF ARCstart date type events (%) (%) (%) (%)---------- ------------------ -------- ------- ------- ------- -------2000-07-01 OCC/OP DATA CHANGE 45 0.0 0.0 0.0 18.1

OCCURRENCE ADD 152 0.0 61.0 0.0 0.0OCCURRENCE DELETE 15 0.4 0.0 6.0 0.0OCCURRENCE RERUN 36 14.5 0.0 0.0 0.0SET OPER. TO COMP 1 0.0 0.0 0.0 0.0


Figure 113. Example of an OPC MCP Events per Caller, Monthly Overview report


OPC Missed-Feedback Operations, in Percent report

This report shows the percentage of missed-feedback operation events thatoccurred at each workstation for a selected day and period. You can use it to givean estimated duration of an operation to Tivoli Workload Scheduler for z/OS withupper and lower limits.


Report IDOPC09


SourceOPC_MISSED_FB_D, OPC_OPER_EVENT_DV2

AttributesOPC, Operations, Missed, Feedback, Overview

VariablesDate, Period_name, OPC_system_ID


Period nameThe name of the period in which the missed-feedback operation eventsoccurred.

WorkstationThe name of the workstation on which the missed-feedback operationevents occurred.

Missed FB (%)The number of missed-feedback operation events, as a percentage of thetotal number of operation events processed on this date, period, andworkstation. Calculated as: 100 * MISSED_FB_EVENTS /OPERATIONS_TOT.

Missed FB above (%)The number of missed-feedback operation events whose durations were

OPC Missed-Feedback Operations, in PercentOPC System: ’01’Date: ’2000-07-15’

Missed MissedMissed FB FB Oper Oper

Period Work- FB above below above below Operationsname station (%) (%) (%) limit limit tot-------- ------- ------- ------- ------- ------- ------- ----------NIGHT MBRA 15.79 10.53 5.26 2 1 19

PRT1 3.70 3.70 0.00 1 0 27MCPU 1.88 1.46 0.42 7 2 478MONL 1.73 0.58 1.16 1 2 173

------- ------- ----------* 11 5 697


Figure 114. Example of an OPC Missed-Feedback Operations, in Percent report


above the limit for feedback, as a percentage of the total number ofoperation events processed on this date, period, and workstation.Calculated as: 100 * OPER_ABOVE_LIMIT / OPERATIONS_TOT.

Missed FB below (%)The number of missed-feedback operation events whose duration timeswere below the limit for feedback, as a percentage of the total number ofoperation events processed on this date, period, and workstation.Calculated as: 100 * OPER_BELOW_LIMIT / OPERATIONS_TOT.

Oper above limitThe number of operation events whose durations were above the limit forfeedback.

Oper below limitThe number of operations events whose durations were below the limit forfeedback.

Operations totThe total number of operation events processed.

OPC automatic workstation events reportThe OPC automatic workstation events report graphically shows the number ofTivoli Workload Scheduler for z/OS-controlled jobs compared to the total numberof jobs processed.

OPC Number of Jobs Processed, Monthly Trend report:This graphic report shows the number of Tivoli Workload Scheduler forz/OS-controlled jobs (automatic operation events) processed in relation to the totalnumber of jobs processed on the system.

Note:

You can create this report only if the MVS component is installed.


Report IDOPC10


SourceMVS_ADDRSPACE_M, OPC_AUTO_EVENT_M

AttributesOPC, Operations, Jobs, Workstation, Graph

VariablesFrom_month, To_month, Processing_node, OPC_system_ID



Month start dateThe date of the measurement. This is date of the first day of the monthwhen the automatic operation events or jobs were processed.

OPC jobsThe number of Tivoli Workload Scheduler for z/OS-controlled jobs(automatic operation events) processed on the system.

Tot jobsThe total number of jobs processed on the system.

OPC processing and tracking times reportsThe OPC processing and tracking times report graphically shows the daily averagetracking times for a specific automatic operation event processed.

OPC Tracking Times by Event Type, Daily Trend report:This graphic report shows the average tracking times (per day on a given timeperiod) for a specified automatic operation event.


Report IDOPC11

Figure 115. Example of an OPC Number of Jobs Processed, Monthly Trend report



SourceOPC_AUTO_EVENT_D

AttributesOPC, Operations, Tracking, Times, Trend

VariablesFrom_date, To_date, OPC_system_ID, OPC_node, Event_reader


Date The date of the measurement. This is the date when the automaticoperation events of this specified type were processed.

Track time (avg)The average tracking time, in seconds. This is the time that elapsed fromthe time the automatic operation event occurred to the time the eventrecord was written to an event data set. Calculated as: TRACK_TOT_SEC /EVENTS.

Figure 116. Example of an OPC Tracking Times by Event Type, Daily Trend report


OPC service-level reportsThe OPC service-level reports show the applications that missed their deadlines,and statistics on late jobs.

OPC Missed Deadline by Application Owner ID report:OPC Missed Deadline by Application Owner ID report

This report shows the applications (or application occurrences in the TivoliWorkload Scheduler for z/OS current plan) that missed their deadlines for a givenmonth.


Report IDOPC12


SourceOPC_CURRENT_PLAN_M

AttributesOPC, Operations, Missed, Application, Worst_Case

VariablesMonth (format YYYY-MM-01), Priority, Maxrows, OPC_system_ID


Application owner IDThe application owner ID that missed the deadline.

PriorityThe priority of the application.

Deadline misses (%)The number of applications (or application occurrences) processed thatmissed the deadline, as a percentage of the the total number of applicationoccurrences processed. Calculated as: 100 * DEADLINE_MISSES /OCCUR_TOTAL.

OPC Missed Deadline by Application Owner IDOPC System: ’01’

Month: ’2003-12-01’

Application Deadlineowner misses DeadlineID Priority (%) misses Occurrences

---------------- -------- -------- -------- -----------CLE 5 100.0 5 5GDT 5 100.0 1 1GLJ 6 100.0 1 1KPN 5 100.0 9 9KPN 6 100.0 1 1KPN 8 100.0 4 4


Figure 117. Example of an OPC Missed Deadline by Application Owner ID report


Deadline missesThe number of applications (or application occurrences) processed thatmissed the deadline.

OccurrencesThe total number of application occurrences processed.

OPC Late-Job Statistics by Application Owner ID report:OPC Late-Job Statistics by Application Owner ID report

This report shows by application owner ID statistics on Tivoli Workload Schedulerfor z/OS late jobs, failed jobs, and deleted jobs for a given month.


Report IDOPC13


SourceOPC_CURRENT_PLAN_M

AttributesOPC, Operations, Late_Jobs, Batch_job

VariablesMonth (format YYYY-MM-01), OPC system ID, Priority



Application owner IDThe application owner ID on which the job statistics were recorded.

PriorityThe priority of the job.

Late jobs (%)The number of late jobs processed for this combination of applicationowner ID/priority as a percentage of the total number of jobs processed.Calculated as: 100 * DEADLINE_MISSES / OCCUR_TOTAL.

Late jobsThe number of late jobs processed for this combination of applicationowner ID/priority.

OPC Late-Job Statistics by Application Owner IDOPC System: ’01’Month: ’2003-09-01’

Application Late jobs Late Total Failed Deletedowner ID Priority (%) jobs jobs jobs jobs

--------------- -------- --------- -------- -------- -------- --------CLE 5 28.6 2 7 0 0

--------- -------- -------- -------- --------* 28.6 2 7 0 0

GDT 5 0.0 0 2 0 0--------- -------- -------- -------- --------

* 0.0 0 2 0 0

GLJ 9 0.0 0 2 0 01 33.3 1 3 0 0

--------- -------- -------- -------- --------* 16.7 1 5 0 0

•••

XPN 9 19.2 5 26 0 08 0.0 0 2 0 05 29.4 30 102 0 02 0.0 0 4 0 01 0.0 0 3 0 0

--------- -------- -------- -------- --------* 9.7 35 137 0 0

YOE747 9 0.0 0 9 0 08 0.0 0 1 0 05 100.0 5 5 0 0

--------- -------- -------- -------- --------* 33.3 5 15 0 0

========= ======== ======== ======== ========39.9 696 1633 137 137


Figure 118. Example of an OPC Missed Deadline by Application Owner ID report


Total jobsThe total number of jobs processed for this combination of applicationowner ID/priority.

Failed jobsThe number of failed jobs processed for this job combination of applicationowner ID/priority.

Deleted jobsThe number of deleted jobs for this job combination of application ownerID/priority.

OPC Reruns by Operation Number, Worst Case report:OPC Reruns by Operation Number, Worst Case report

This report shows the number of reruns (from MCP events) by operation numberand application. The job name is also shown. If the job name cannot bedetermined, it is shown as missing.

Operations with status code R or W are selected. The operation number indicatesfrom where an application is restarted.


Report IDOPC14


SourceOPC_MCP_D

AttributesOPC, Operations, Worst, Case, Reruns, MCP

VariablesFrom date, To date, OPC system ID, Maxrows



Application nameThe name of the application on which the reruns were recorded.

Operation numberThe operation number, which indicates from where an application isrestarted.

JobnameName of the job. $MISSING means that the job name could not bedetermined.

RerunsThe number of reruns recorded for the application.

RACF componentCustomizationv Considering which subcomponents to install

– Evaluating the RACF component– RACF component structure

v Making input data available– Making z/OS SMF data available– Making z/VM SMF data available– Making Database Unload data available

v Reviewing the DRLJCOLL jobv Updating lookup tables

– Updating RACF_EVENT_CODE table– Updating RACF_USER_OWNER and RACF_RES_OWNER tables

Data flow

OPC Reruns by Operation Number, Worst CaseOPC System: ’01’

From date: ’2003-09-06’ To date: ’2003-09-07’

Application Operationname number Jobname Reruns

---------------- ---------- ---------- -----------AVJ034 10 AVJOB12 3AVJFGHT 25 $MISSING 3AX01345 50 $MISSING 2A123P 15 A1JOB17 2AJ02XY0 20 $MISSING 2AJ02ERT 42 $MISSING 1MJHALRTCLENEU 40 $MISSING 1AJ83796 10 $MISSING 1EMIDICD 10 AJOB34 1XYZOSR07 10 $MISSING 1XYDEB2R0 10 $MISSING 1YYJ03050 22 YYJOB322 1YYJLIW33 25 $MISSING 1VJ00757TESTRUNS 30 $MISSING 1YYJRRL23 15 $MISSING 1


Figure 119. Example of an OPC Reruns by Operation Number, Worst Case report


v Storing the data



– 1. RACF Activity– 2. RACF Configuration

v Lookup tables– RACF_EVENT_CODE– RACF_OMVS_AUDCODE– RACF_RES_OWNER– RACF_USER_OWNER

Reportsv RACF Activity reports

– RACF Logon/Job Failures report– RACF Command Failures - Auditor report– RACF SPECIAL User Commands - Auditor report– RACF AUDITOR User Commands - Auditor report– RACF OPERATIONS User Access - Auditor report– RACF Resource Access Failures report– RACF Resource Accesses report– RACF SUPERUSER Security Commands - Auditor report– RACF OpenEdition Resource Accesses report– RACF OpenEdition Resource Accesses Failures report– RACF Initialization report– RACF Class Initialization report– RACF Terminals with Excessive Incorrect Passwords report– RACF Users with Excessive Incorrect Passwords report– RACF All Events for a Specific User report– RACF Data Sets with a Specific Name Access report– RACF Data Sets with Particular Authority report– RACF Resources Accessed Because Installation Exit report– RACF Resources Accessed Because Warning Mode report– RACF Generic Profiles Used for Resource Access report

v RACF Configuration reports– RACF Number of Profiles in the Database report– RACF Group List report– RACF Users with Particular System Privileges report– RACF Users with Particular Group Level Privileges report– RACF Users Currently Revoked report– RACF Users Last Defined report– RACF Users with NOINTERVAL Specified report– RACF Users with Too Many Group Connections report– RACF Users Members of SYS1 Group report


– RACF Dataset Profiles for Each HLQ report– RACF Dataset Profiles with UACC Other than NONE report– RACF Dataset Profiles in WARNING Mode report– RACF Dataset Standard ACL with ID(*) Not NONE report– RACF Dataset Condit. ACL with ID(*) Not NONE report– RACF GR Number of Profiles for Each Class report– RACF GR Discrete Profiles with Wild Characters report– RACF GR Profiles with UACC Other than NONE report– RACF GR Profiles in WARNING Mode report– RACF GR Profiles Standard ACL with ID(*) not NONE report– RACF GR Profiles Condit. ACL with ID(*) Not NONE report

CustomizationBefore you can use the RACF 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 RACF component:1. Considering which subcomponents to install.2. Making input data available.3. Reviewing the DRLJCOLL job.4. Updating lookup tables.

Considering which subcomponents to installYour most critical planning task is determining what kind of information usersneed from the RACF component. Installing only the component parts that areneeded to meet user requirements ensures that the collected data benefits userswhile it minimizes the performance impact caused by data collection andinterpretation activities.

Although Tivoli Decision Support for z/OS can analyze data and produce reportsfor all the information categories, you might not need all that data. Figure 120shows that the RACF component is divided into two subcomponents.


Consider carefully which subcomponent to install. Subcomponents are groups ofTivoli Decision Support for z/OS objects (for example, predefined updatedefinitions, data tables, and reports). If you find that you need reports from asubcomponent that you have not installed, you must install that subcomponentand then wait several days or weeks until enough data has been collected to createreports. However, if you install more subcomponents than you need, TivoliDecision Support for z/OS collects needless data, which takes up disk space anduses processor time.

At this point, you might find it helpful to examine the predefined reports for eachsubcomponent. For more information, see Reports.

Evaluating the RACF component:The RACF component is built up of the following subcomponents:

1. RACF Activity

This subcomponent provides detailed information on the security activity recordedby RACF on SMF records. Data is grouped by commands, logons, resourceaccesses, and RACF intializations.

2. RACF Configuration

This subcomponent provides detailed information about the RACF database setup.Data is grouped by groups, users, data sets, and general resource profiles.

RACF component structure:The following table shows how the Tivoli Decision Support for z/OS data tablesare organized between the RACF subcomponents.

Figure 120. RACF component structure


Table 8. Data tables in the RACF subcomponents

RACF subcomponents Data tables

1. RACF Activity RACF_INIT_T

RACF_INIT_CLASS_T

RACF_COMMAND_T

RACF_LOGON_T

RACF_RESOURCE_T

RACF_OPERATION_T

RACF_OMVS_RES_T

RACF_OMVS_SEC_T

2. RACF Configuration RACF_GROUPS_D

RACF_USERS_D

RACF_USER_CON_D

RACF_DATASETS_D

RACF_DS_ACCESS_D

RACF_DS_CONDACC_D

RACF_GENRES_D

RACF_GR_ACCESS_D

RACF_GR_CONDACC_D

Making input data availableEnsure that the input data records are present in the input logs.

The RACF component accepts RACF logs written in z/OS and z/VM operatingsystems.

Making z/OS SMF data available:Making z/OS SMF data available

To make RACF SMF data available on a z/OS system:1. Check that SMF record types 80 and 81 are not suppressed by any SMF

parameter or exit.2. Ensure that the desired auditing and logging options are activated in RACF, for

the associated resource classes (SETROPTS). Refer to the Resource Access ControlFacility (RACF) Security Administrator’s Guide.

3. Change the installation data field in RACF user and group profiles, so thatreports are directed to the right person or department. This step is optional.All RACF profiles contain an OWNER field. This field establishes the profileownership within RACF. It contains a user ID or a group name. Tivoli DecisionSupport for z/OS uses both the owner and the installation data field in theowner profile to find the responsible user for any resource, user, or group.For all RACF profiles where you want the reports sent to a user or departmentother than the owner of the resource, insert the string RESPUSER=xxxxxxxx


(where xxxxxxxx is the responsible user) in the installation data field in theowner profile or see Updating RACF_USER_OWNER and RACF_RES_OWNERtables.

Note: The term "responsible user" is the name that Tivoli Decision Support forz/OS uses to group information, and need not be the name of any RACFresource.

Making z/VM SMF data available:On a z/VM system, RACF writes SMF records to a CMS file. You must transmitthe CMS file to the z/OS system on which you are running Tivoli DecisionSupport for z/OS.

RACF/VM SMF records must be reformatted with SMFCONV fn ft fm (where fn ftfm is your VM file name, file type, and file mode) to put them in the same formatas the z/OS records.

Making Database Unload data available:The RACF Database Unload utility provides easy access to the informationcontained in the RACF database by enabling you to unload the RACF database toa sequential file, whose contents can be used to do analysis and reporting.

The sequential file is structured in different record types and can be loaded, usingcollect, in the Tivoli Decision Support for z/OS tables.

The Database Unload utility is available on z/Os and z/VM systems:

z/OS systemRun the RACF Database Unload by using the IRRDBU00 utility. Create anunload job, as described in the RACF Security Administrator’s Guide, thenrun a collect job on the output file.

z/VM systemRun the RACFDBU program to unload the database to a CMS file.Transmit the CMS file to the z/OS system where Tivoli Decision Supportfor z/OS is running, then run a collect job on the output file.

Reviewing the DRLJCOLL jobDepending on the RACF subcomponent installed, add the following collectstatements to the DRLJCOLL sample job. For more details about how to reviewDRLJCOLL, see System Performance Feature Reference Volume I.

RACF ActivityCOLLECT SMF;

RACF ConfigurationSET UNLOAD_DATE = 'YYYY-MM-DD';SET SYSTEM_ID = 'MVS1';COLLECT RACFCONF REPROCESS;

Updating lookup tablesThe RACF Activity subcomponent uses several lookup tables to translate user IDs,classes, and resource names to responsible owners and security levels, and RACFevent codes and qualifiers to event descriptions. Using the administration dialog,update the lookup tables to include parameters specific to your installation.



RACF_EVENT_CODE Converts RACF event codes andqualifiers to event descriptions. Youneed not update this table.

EVENT_CODE,EVENT_QUAL

EVENT, EVENT_DESC

RACF_RES_OWNER Converts classes and resource namesto responsible owners and securitylevels.

SYSTEM_ID, CLASS,PROFILE_NAME,GENERIC

RESPONSIBLE_USER,SECLEVEL,SECLEVEL_NAME

RACF_USER_OWNER Converts user IDs to responsibleowners and security levels.

SYSTEM_ID, USER_ID RESPONSIBLE_USER,SECLEVEL,SECLEVEL_NAME


Updating RACF_EVENT_CODE table:You need not change this lookup table, unless you want to change the defaultevent descriptions (for example, to translate them to another language).

For a complete description of this lookup and an example of its contents, seeRACF_EVENT_CODE.

Updating RACF_USER_OWNER and RACF_RES_OWNER tables:These lookup tables provide responsible users for users and resources. Because asystem contains a large number of users and resources, it is not practical tomaintain the tables manually. Tivoli Decision Support for z/OS provides a utilityto extract this information from an unloaded RACF database:1. Run the RACF database unload utility (IRRDBU00). See the Resource Access

Control Facility (RACF) Security Administrator’s Guide for a description of thisutility.

2. Customize and submit the job DRLJRACF (in the SDRLCNTL library). This jobreads the unloaded RACF database and updates the Tivoli Decision Support forz/OS database.

Tivoli Decision Support for z/OS has an algorithm to find the responsible user (seeTable 9). To get better control of this, you can insert the character stringRESPUSER=xxxxxx anywhere in the installation data field of the owner’s userprofile, using standard RACF commands or the RACF dialog. The installation datafield is called DATA, and is in the RACF segment.

The position of this string in the installation data field is not critical. TheRESPUSER parameter is used for sending Tivoli Decision Support for z/OS reportsto the person or department that is responsible for a resource, group, or user. Itdoes not have to be a user ID, it can be any name or code that you find convenientfor grouping reports.

Table 9. Table 9. How RESPUSER works

StepTheowner is

Installationdata field inthe ownerprofilecontains theRESPUSERparameter

Tivoli Decision Support for z/OS sets theresponsible user to

1 A user Yes RESPUSER parameter value


Table 9. Table 9. How RESPUSER works (continued)

StepTheowner is

Installationdata field inthe ownerprofilecontains theRESPUSERparameter

Tivoli Decision Support for z/OS sets theresponsible user to

2 A user No User ID

3 A group Yes RESPUSER parameter value

4 ThegroupSYS1

No Original group

5 A group No Tivoli Decision Support for z/OS looks at the ownerof the group profile and continues at step 1

Note: If the RACF_xxx_OWNER tables are not filled in, the responsible userappears as a question mark (?) in the reports.

The RESPUSER parameter is valid only in user and group profiles.

For a complete description and an example of the contents of theRACF_RES_OWNER lookup table, see RACF_RES_OWNER. For a completedescription and an example of the contents of the RACF_USER_OWNER lookuptable, see RACF_USER_OWNER.

Data flowDepending on the RACF subcomponent you installed, the following flow of datatakes place:

RACF ActivityTivoli Decision Support for z/OS collects the SMF log data recorded byRACF and stores the data in the appropriate tables.

RACF ConfigurationTivoli Decision Support for z/OS collects the RACF Database Unloadutility output and stores the data in the appropriate tables.

Use the reporting dialog to display reports based on the data.

Figure 121 shows an overview of the flow of data from the RACF licensedprogram, through the RACF component, and finally into reports.


Storing the dataAfter collecting data, the RACF component stores the data in the Tivoli DecisionSupport for z/OS database. As it updates tables, the component uses lookup tables

Figure 121. RACF data flow


to convert RACF event codes and qualifiers to event descriptions. The followingfigure shows which data tables contain values from the lookup tables.

For detailed information about the tables updated by RACF and the lookup tablesit uses, see Data tables and lookup tables.

Log and record definitionsThe RACF component processes records from two different logs:

SMF logContains the RACF Activity data. The following record types areprocessed. SMF records 83 are not used, although record mapping isprovided.

Figure 122. RACF lookup table data


Table 10. Input records to the RACF Activity subcomponent

SMF record type Record definition Description

80 SMF_080 This record is written for eachsuccessful or unsuccessfulpartner LU verification, eachunauthorized attempt to enterthe system, and eachauthorized or unauthorizedaccess to RACF-protectedresources or attempts tomodify profiles.

81 SMF_081 RACF writes record type 81 atthe completion of theinitialization of RACF. Itcontains data such as the nameof the RACF database, UADSdata set name, RACF options,and password settings.

RACF Database Unload utilityContains the RACF Configuration data. The following record types areprocessed. For a detailed description of the RACF records, see the RACFMacros and Interfaces manual.

Table 11. Input records to the RACF Configuration subcomponent

IRRDBU00 record type Record definition Description

0100 RACF_100 Group Basic Data. This recorddefines the basic informationabout a group. There is onerecord per group.

0200 RACF_200 User Basic Data. This recorddefines the basic informationabout a user. There is onerecord per user.

0205 RACF_205 User Connect Data. This recorddefines the relationshipsbetween users and groups.There is one record per userconnection.

0400 RACF_400 Data Set Basic Data. Thisrecord defines the basicinformation about a data set.There is one record per dataset profile.

0402 RACF_402 Data Set Conditional Access.This record defines the datasets that have conditionalaccess permissions. There isone record per data set/accesscombination.

0404 RACF_404 Data set Access. This recorddefines the users or groupswho are allowed to accessdata. There is one record perdata set/access combination.


Table 11. Input records to the RACF Configuration subcomponent (continued)

IRRDBU00 record type Record definition Description

0500 RACF_500 General Resource Basic Data.This record defines the basicinformation about a generalresource. There is one recordper general resource profile.

0505 RACF_505 General Resource Access. Thisrecord defines the users orgroups who have specificaccess to general resources.There is one record per generalresource/access combination.

0507 RACF_507 General Resource ConditionalAccess. This record defines theconditional access to a generalresource. There is one recordper general resource/accesscombination.

Data tables and lookup tablesThis chapter describes the data tables and lookup tables used by the RACFcomponent. For descriptions of common data tables, lookup tables, and controltables used by the System Performance feature, see the Administration Guide andReference.

Data tablesAs described in Evaluating the RACF component, the RACF component containstwo subcomponents. This section groups the data tables for the RACF componentby its subcomponents:1. RACF Activity2. RACF Configuration

1. RACF Activity:The data tables described in this section are for the RACF Activity subcomponent,which provides details about the security activity recorded by RACF on SMFrecord.

RACF_COMMAND_T

This table provides details about failed RACF commands and commands issued byusers with the SPECIAL, Group-SPECIAL, AUDITOR, or Group-AUDITORattribute. It contains data from SMF type 80 records with event codes 8 to 25.

This table is updated by the RACF_EVENT_CODE lookup table.



TIMESTAMP K TIMESTAMP Local date and time when the RACF command wasentered. From SMF80DTE and SMF80TME.

SYSTEM_ID K CHAR(4) SMF system ID. From SMF80SID.



USER_ID K CHAR(8) ID of the user for whom the event (failed, special, orauditor command) is recorded. This contains the jobname if the user is not defined to RACF. FromSMF80USR.

AUDITOR CHAR(1) Indicates whether the RACF command was issued bya user with the AUDITOR or Group-AUDITORattribute. This is Y (yes) if bit 3 of SMF80ATH is on;otherwise, N (no).

AUTHORITY_FLAGS CHAR(8) Authorities used for processing commands. FromSMF80ATH.

Bit Meaning when set

0 Normal authority check.

1 SPECIAL attribute.

2 OPERATIONS attribute.

3 AUDITOR attribute.

4 Installation exit processing.

5 Failsoft processing.

6 Bypassed-user ID = *BYPASS*.

7 Trusted attribute.

COMMAND CHAR(8) Name of the RACF command that was used. FromEVENT in the RACF_EVENT_CODE lookup table.This is derived using fields SMF80EVT andSMF80EVQ from the record as key.

EVENT_DESC CHAR(20) Description for the event code qualifier. FromEVENT_DESC in the RACF_EVENT_CODE lookuptable. This is derived using fields SMF80EVT andSMF80EVQ from the record as key.

EVENT_QUAL SMALLINT Event code qualifier. From SMF80EVQ. For detailedinformation on RACF event codes, refer to the RACFMacros and Interfaces manual.

FAILED CHAR(1) Indicates whether the RACF command failed becauseof insufficient authority. This is Y (yes) if SMF80EVQis greater than 0; otherwise, N (no).

RESOURCE_NAME VARCHAR(44) Name of the resource on which the RACF commandwas to operate. Extracted from different parts ofSMF80DTA, where the data type (SMF80DTP) is 6 or9, depending on the event type (SMF80EVT).

SPECIAL CHAR(1) Indicates whether the RACF command was issued bya user with the SPECIAL or Group-SPECIAL attribute.This is Y (yes) if bit 1 of SMF80ATH is on; otherwise,N (no).

TERMINAL_ID CHAR(8) Terminal ID of the foreground user. This is set toblank if the terminal ID is not available. FromSMF80TRM.

RACF_INIT_T

This table provides details about the RACF setting at initialization time. It containsdata from SMF type 81 records.




TIMESTAMP K TIMESTAMP Local date and time when the RACF initialization wasissued. From SMF81DTE and SMF81TME.


AUDIT_FLAG1 CHAR(8) Audit option 1. From SMF81AOP.


0 User class profile changes are being logged.

1 Group class profile changes are being logged.

2 Data set class profile changes are beinglogged.

3 Tape volume class profile changes are beinglogged.

4 DASD volume class profile changes are beinglogged.

5 Terminal class profile changes are beinglogged.

6 RACF command violations are being logged.

7 Special user activity is being logged.

AUDIT_FLAG2 CHAR(8) Audit option 1. From SMF81AO2.


0 Operation user activity.

1 Audit by security level is in effect.

2-7 Reserved.

DB_DSNAME VARCHAR(44) Data set name of the RACF database for this IPL.Blank, if RACF is not active. From SMF81RDS.

DB_UNIT CHAR(3) Unit name of the RACF database. Blank, if RACF isnot active. From SMF81RUN.

DB_VOLUME CHAR(6) Volume identification of the RACF database. Blank, ifRACF is not active. From SMF81RVL.



OPTIONS_FLAG1 CHAR(8) Options Indicator 1. From SMF81OPT.


0 No RACROUTE REQUEST=VERIFY statisticsare recorded.

1 No DATA SET statistics are recorded.

2 RACROUTE REQUEST=VERIFYpre-processing exit routine, ICHRIX01, isactive.

3 RACROUTE REQUEST=AUTHpre-processing exit routine, ICHRCX01, isactive.

4 RACROUTE REQUEST=DEFINEpre-processing exit routine, ICHRDX01, isactive.

5 RACROUTE REQUEST=VERIFYpost-processing exit routine, ICHRIX02, isactive.

6 RACROUTE REQUEST=AUTHpost-processing exit routine, ICHRCX02, isactive.

7 New password exit routine, ICHPWX01, isactive.

OPTIONS_FLAG2 CHAR(8) Options Indicator 2. From SMF81OP2.


0 No tape volume statistics are recorded.

1 No DASD volume statistics are recorded.

2 No terminal statistics are recorded.

3 Command exit routine, ICHCNX00, is active.

4 Command exit routine, ICHCCX00, is active.

5 ADSP is not active.

6 Encryption exit routine, ICHDEX01, is active.

7 Naming convention table, ICHNCV00, ispresent.





0 Tape volume protection is in effect.

1 No duplicate data set names are to bedefined.

2 DASD volume protection is in effect.

3 Record contains version indicator.

4 RACROUTE REQUEST=FASTAUTHpre-processing exit routine, ICHRFX01, isactive.

5 RACROUTE REQUEST=LIST pre andpost-processing exit routine, ICHRLX01, isactive.

6 RACROUTE REQUEST=LIST selection exitroutine, ICHRLX02, is active.

7 RACROUTE REQUEST=DEFINEpost-processing exit routine, ICHRDX02, isactive.



0 TAPEDSN is in effect.

1 PROTECT-ALL is in effect.

2 PROTECT-ALL warning is in effect.

3 ERASE-ON-SCRATCH is in effect.

4 ERASE-ON-SCRATCH by SECLEVEL is ineffect.

5 ERASE-ON-SCRATCH for all data sets is ineffect.

6 Enhanced generic naming is in effect.

7 Record contains a version, release, andmodification number.





0 Access control by program is in effect.

1 ACEE compression/expansion exit,IRRACX01, is active.

2 RACROUTE REQUEST=FASTAUTHpost-processing exit routine, ICHRFX04, isactive.

3 RACROUTE REQUEST=FASTAUTHpre-processing exit routine, ICHRFX03, isactive.

4 SETROPTS NOADDCREATOR is active.

5 IRREVX01 exit is active.

6 ACEE compression/expansion exit,IRRACX02, is active.

7 Password exit routine, ICHDEX11, is active.

PWD_HISTORY SMALLINT The password history value. From SMF81DTA, wheredata type (SMF81DTP) is 32.

PWD_INACTIVE SMALLINT The number of days of inactivity before user isrevoked. From SMF81DTA, where data type(SMF81DTP) is 32.

PWD_INTERVAL SMALLINT The maximum password interval. From SMF81PIV.

PWD_REVOKE SMALLINT The number of incorrect logon passwords after whichuser is revoked. From SMF81DTA, where data type(SMF81DTP) is 32.

PWD_WARNING SMALLINT The number of days before password expirationduring which user receives a warning message. FromSMF81DTA, where data type (SMF81DTP) is 32.

UADS_DSNAME VARCHAR(44) Data set name of the User Attribute Data Set (UADS)for this IPL. From SMF81UDS.

UADS_VOLUME CHAR(6) Volume identification of the User Attribute Data Set(UADS). Blank, if RACF is not active. FromSMF81UVL.

RACF_INIT_CLASS_T

This table provides details about the class setting of RACF at initialization time. Itcontains data from SMF type 81 records.



TIMESTAMP K TIMESTAMP Local date and time when the RACF initialization wasissued. From SMF81DTE and SMF81TME.


CLASS_NAME K CHAR(8) Name of the class. From SMF81DTA, where data type(SMF81DTP) is 21.



CLASS_OPTIONS CHAR(8) Current class options. From SMF81DTA, where datatype (SMF81DTP) is 21.


0 Statistics are in effect.

1 Auditing is in effect.

2 Protection is in effect.

3 Generic profile processing in effect.

4 Generic command is in effect.

5 Global access checking active.

6 RACLIST option in effect.

7 GENLIST option in effect.

LOG_OPTIONS CHAR(9) The LOGOPTIONS for the class. From SMF81DTA,where data type (SMF81DTP) is 21. Valid values are:

v ALWAYS

v NEVER

v SUCCESSES

v FAILURES

v DEFAULT

If the RACF LOGOPTIONS is not set, this column isblank.

RACF_LOGON_T

This table provides details about logon and job violations. It contains data fromSMF type 80 records with event code 1. You can use this table to report onunauthorized attempts to log on to the system or run jobs.




TIMESTAMP K TIMESTAMP Local date and time of the violation. From SMF80DTEand SMF80TME.


USER_ID K CHAR(8) ID of the user for whom the event (logon or jobviolation) is recorded. This contains the job name ifthe user is not defined to RACF. From SMF80USR.

APPLICATION_NAME CHAR(8) Name of the application. From SMF80DTA, wheredata type (SMF80DTP) is 20.

EVENT CHAR(10) Event description. From EVENT in theRACF_EVENT_CODE lookup table. This is derivedusing fields SMF80EVT and SMF80EVQ from therecord as key.

EVENT_DATE DATE Date of the event. From SMF80DTE.




EVENT_QUAL SMALLINT Event code qualifier. From SMF80EVQ. For detailedinformation on RACF event codes, refer to RACFMacros and Interfaces.


RACF_OMVS_RES_T

This table provides audit information about OpenEdition resource access checking .It contains data from the extended relocation section of SMF type 80 records.



TIMESTAMP K TIMESTAMP Local date and time of the event. From SMF80DTEand SMF80TME.


USER_ID K CHAR(8) ID of the user for whom the access or access attemptis recorded. This contains the job name if the user isnot defined to RACF. From SMF80USR.

EVENT_CODE K SMALLINT Event code. From SMF80EVT. For detailedinformation on RACF event codes, refer to RACFMacros and Interfaces.

ACCESS_ALLOWED CHAR(16) Access authority allowed. This can be READ, WRITE,EXECUTE, or SEARCH. From SMF80DA2, where datatype (SMF80TP2) is 269.

ACCESS_REQUESTED CHAR(5) Access authority requested. This can be READ,WRITE, EXECUTE, DIRECTORY SEARCH, or ANY.From SMF80DA2, where data type (SMF80TP2) is 267.

ACCESS_TYPE CHAR(5) Access type used to make access check. This can beOWNER, GROUP, OTHER, or NONE. FromSMF80DA2, where data type (SMF80TP2) is 268.

AUDIT_DESC CHAR(20) OpenEdition audit function description. FromAUDIT_DESC in the RACF_OMVS_AUDCODElookup table. This is derived using field SMF80DA2where data type (SMF80TP2) is 256 as a key.

AUDIT_NAME CHAR(16) OpenEdition audit function name. FromAUDIT_NAME in the RACF_OMVS_AUDCODElookup table. This is derived using field SMF80DA2where data type (SMF80TP2) is 256 as a key.

CLASS CHAR(8) Resource class. From SMF80DTA, where data type(SMF80DTP) is 17.

EFFECTIVE_GID INTEGER The OpenEdition effective GID. From SMF80DA2,where data type (SMF80TP2) is 261.

EFFECTIVE_UID INTEGER The OpenEdition effective UID. From SMF80DA2,where data type (SMF80TP2) is 258.





FILE_OWNER_GID INTEGER The owner GID of OpenEdition file. From SMF80DA2,where data type (SMF80TP2) is 266.

FILE_OWNER_UID INTEGER The owner UID of OpenEdition file. From SMF80DA2,where data type (SMF80TP2) is 265.

FILENAME VARCHAR(64) The OpenEdition file name being checked. FromSMF80DA2, where data type (SMF80TP2) is 298.

REAL_UID INTEGER The OpenEdition real UID. From SMF80DA2, wheredata type (SMF80TP2) is 257.

REAL_GID INTEGER The OpenEdition real GID. From SMF80DA2, wheredata type (SMF80TP2) is 260.

SAVED_GID INTEGER The OpenEdition saved GID. From SMF80DA2, wheredata type (SMF80TP2) is 262.

SAVED_UID INTEGER The OpenEdition saved UID. From SMF80DA2, wheredata type (SMF80TP2) is 259.

SUPERUSER CHAR(1) Indicates whether the OpenEdition services requireSUPERUSER authority. This is Y (yes) if bit 1 ofSMF80AU2 is on; otherwise, N (no).

PATHNAME VARCHAR(254) The OpenEdition requested pathname. FromSMF80DA2, where data type (SMF80TP2) is 263.

RACF_OMVS_SEC_T

This table provides audit information about OpenEdition changes to the securitydata (FSP). It contains data from the extended relocation section of SMF type 80records.







AUD_AUDITOR_EXEC CHAR(8) New auditor audit options for EXECUTE or SEARCHaction. This can be NONE, SUCCESS, FAIL, or ALL.From byte 7 of SMF80DA2, where data type(SMF80TP2) is 294.



AUD_AUDITOR_READ CHAR(8) New auditor audit options for READ action. This canbe NONE, SUCCESS, FAIL, or ALL. From byte 5 ofSMF80DA2, where data type (SMF80TP2) is 294.

AUD_AUDITOR_WRITE CHAR(8) New auditor audit options for WRITE action. This canbe NONE, SUCCESS, FAIL, or ALL. From byte 6 ofSMF80DA2, where data type (SMF80TP2) is 294.

AUD_USER_EXEC CHAR(8) New user audit options for EXECUTE or SEARCHaction. This can be NONE, SUCCESS, FAIL, or ALL.From byte 3 of SMF80DA2, where data type(SMF80TP2) is 294.

AUD_USER_READ CHAR(8) New user audit options for READ action. This can beNONE, SUCCESS, FAIL, or ALL. From byte 1 ofSMF80DA2, where data type (SMF80TP2) is 294.

AUD_USER_WRITE CHAR(8) New user audit options for WRITE action. This can beNONE, SUCCESS, FAIL, or ALL. From byte 2 ofSMF80DA2, where data type (SMF80TP2) is 294.

AUDITOR CHAR(1) Indicates whether the OpenEdition command wasissued by a user with the RACF AUDITOR attribute.This is Y (yes) if bit 3 of SMF80ATH is on; otherwise,N (no).

CHOWN_GID INTEGER The GID input parameter on the CHOWN command.From SMF80DA2, where data type (SMF80TP2) is 281.

CHOWN_UID INTEGER The UID input parameter on the CHOWN command.From SMF80DA2, where data type (SMF80TP2) is 280.


EFFECTIVE_GID INTEGER The OpenEdition effective GID. From SMF80DA2,where data type (SMF80TP2) is 261.

EFFECTIVE_UID INTEGER The OpenEdition effective UID. From SMF80DA2,where data type (SMF80TP2) is 258.




FILE_OWNER_GID INTEGER The owner GID of OpenEdition file. From SMF80DA2,where data type (SMF80TP2) is 266.

FILE_OWNER_UID INTEGER The owner UID of OpenEdition file. From SMF80DA2,where data type (SMF80TP2) is 265.

GROUP_EXEC CHAR(1) Indicates the new mode for group EXEC authority forthe object. This is Y (EXEC on) if bit 29 of SMF80DA2is on, where data type (SMF80TP2) is 290; otherwise,N (no).



GROUP_READ CHAR(1) Indicates the new mode for group READ authority forthe object. This is Y (READ on) if bit 27 of SMF80DA2is on, where data type (SMF80TP2) is 290; otherwise,N (no).

GROUP_WRITE CHAR(1) Indicates the new mode for group WRITE authorityfor the object. This is Y (WRITE on) if bit 28 ofSMF80DA2 is on, where data type (SMF80TP2) is 290;otherwise, N (no).

OTHER_EXEC CHAR(1) Indicates the new mode for other EXEC authority forthe object. This is Y (EXEC on) if bit 32 of SMF80DA2is on, where data type (SMF80TP2) is 290; otherwise,N (no).

OTHER_READ CHAR(1) Indicates the new mode for other READ authority forthe object. This is Y (READ on) if bit 30 of SMF80DA2is on, where data type (SMF80TP2) is 290; otherwise,N (no).

OTHER_WRITE CHAR(1) Indicates the new mode for other WRITE authorityfor the object. This is Y (WRITE on) if bit 31 ofSMF80DA2 is on, where data type (SMF80TP2) is 290;otherwise, N (no).

OWNER_EXEC CHAR(1) Indicates the new mode for owner EXEC authority forthe object. This is Y (EXEC on) if bit 26 of SMF80DA2is on, where data type (SMF80TP2) is 290; otherwise,N (no).

OWNER_WRITE CHAR(1) Indicates the new mode for owner WRITE authorityfor the object. This is Y (WRITE on) if bit 25 ofSMF80DA2 is on, where data type (SMF80TP2) is 290;otherwise, N (no).

OWNER_READ CHAR(1) Indicates the new mode for owner READ authorityfor the object. This is Y (READ on) if bit 24 ofSMF80DA2 is on, where data type (SMF80TP2) is 290;otherwise, N (no).

REAL_UID INTEGER The OpenEdition real UID. From SMF80DA2, wheredata type (SMF80TP2) is 257.

REAL_GID INTEGER The OpenEdition real GID. From SMF80DA2, wheredata type (SMF80TP2) is 260.

S_ISGID CHAR(1) Indicates whether the OpenEdition set-group-ID bit ison for the object. This is Y (yes) if bit 21 ofSMF80DA2 is on, where data type (SMF80TP2) is 290;otherwise, N (no).

S_ISUID CHAR(1) Indicates whether the OpenEdition set-user-ID bit ison for the object. This is Y (yes) if bit 22 ofSMF80DA2 is on, where data type (SMF80TP2) is 290;otherwise, N (no).

S_ISVTX CHAR(1) Indicates whether the OpenEdition sticky bit is on forthe object. This is Y (yes) if bit 23 of SMF80DA2 is on,where data type (SMF80TP2) is 290; otherwise, N (no).

SAVED_GID INTEGER The OpenEdition saved GID. From SMF80DA2, wheredata type (SMF80TP2) is 262.

SAVED_UID INTEGER The OpenEdition saved UID. From SMF80DA2, wheredata type (SMF80TP2) is 259.



SUPERUSER CHAR(1) Indicates whether the OpenEdition services requireSUPERUSER authority. This is Y (yes) if bit 1 ofSMF80AU2 is on; otherwise, N (no).

PATHNAME VARCHAR(254) The OpenEdition requested pathname. FromSMF80DA2, where data type (SMF80TP2) is 263.

RACF_OPERATION_T

This table provides details about resource accesses by users or jobs with theOPERATIONS attribute. Rows with user ID = HSM are excluded. It contains datafrom SMF type 80 records. You can use this table to report on authorized accessesor unauthorized access attempts.






USER_ID K CHAR(8) ID of the user for whom the operation is recorded.This contains the job name if the user is not definedto RACF. From SMF80USR.





GENERIC CHAR(1) Indicates whether the data-set profile is generic. Thiscan be Y (generic) or N (discrete). This is set to Y ifdata type (SMF80DTP) 33 is present.

PROFILE_NAME VARCHAR(44) Generic profile name. This is null if a discrete profileis used. From SMF80DTA, where data type(SMF80DTP) is 33.

RESOURCE_NAME VARCHAR(44) Name of the RACF-protected resource accessed. FromSMF80DTA, where data type (SMF80DTP) is 1.



RACF_RESOURCE_T

This table provides details about access attempts on RACF-protected systemresources. Rows with user ID = HSM are excluded. It contains data from SMF type80 records. You can use this table to report on authorized accesses or unauthorizedattempts to access RACF-protected resources.







ACCESS_ALLOWED CHAR(8) Access authority allowed. This can be ALTER,CONTROL, UPDATE, READ, or NONE. FromSMF80DTA, where data type (SMF80DTP) is 4.

ACCESS_REQUESTED CHAR(8) Access authority requested. This can be ALTER,CONTROL, UPDATE, READ, or NONE. FromSMF80DTA, where data type (SMF80DTP) is 3.

AUTHORITY_FLAGS CHAR(8) Authorities used for accessing resources. FromSMF80ATH.


0 Normal authority check.

1 SPECIAL attribute.

2 OPERATIONS attribute.

3 AUDITOR attribute.

4 Installation exit processing.

5 Failsoft processing.

6 Bypassed-user ID = *BYPASS*.

7 Trusted attribute.


EVENT_DATE DATE Date of the event. From SMF80DTE.

EVENT_DESC CHAR(20) Description for the event code qualifier. FromEVENT_DESC in RACF_EVENT_CODE lookup table.This is derived using fields SMF80EVT andSMF80EVQ from the record as key.


GENERIC CHAR(1) Indicates whether the data-set profile is generic. Thiscan be Y (generic) or N (discrete). This is set to Y ifdata type (SMF80DTP) 33 is present.



PROFILE_NAME VARCHAR(44) Generic profile name. This is null if a discrete profileis used. From SMF80DTA, where data type(SMF80DTP) is 33.

RESOURCE_NAME VARCHAR(44) Name of the RACF-protected resource accessed. FromSMF80DTA, where data type (SMF80DTP) is 1.


2. RACF Configuration:2. RACF Configuration

The data tables described in this section are for the RACF Configurationsubcomponent, which provides detailed information about the RACF databasesetup.

RACF_DATASETS_D

This table provides basic configuration information about each data set profiledefined in the RACF database. It contains data from RACF record type 0400.



DATE K DATE Unload date. This column is derived from the runtimeparameter :UNLOAD_DATE, because RACF logrecords do not contain this data. If it is not specified,the CURRENT DATE is used.

SYSTEM_ID K CHAR(4) System identifier. This column is derived from theruntime parameter :SYSTEM_ID, because the RACFlog records do not contain this data.

DS_NAME K VARCHAR(44) Data set name, as taken from the profile name. FromDSBD_NAME.

VOLUME K CHAR(6) Volume upon which this data set resides. Blank if theprofile is generic, and *MODEL if the profile is amodel profile. From DSBD_VOL.

AUDIT_FAQUAL CHAR(8) The resource-owner-specified failing access auditqualifier. This is set to blank if AUDIT_LEVEL isNONE, otherwise can be set to READ, UPDATE,CONTROL, or ALTER. FromDSBD_AUDIT_FAQUAL.

AUDIT_LEVEL CHAR(8) Indicates the level of resource-owner-specifiedauditing that is performed. Valid values are ALL,SUCCESS, FAIL, and NONE. FromDSBD_AUDIT_LEVEL.

AUDIT_OKQUAL CHAR(8) The resource-owner-specified successful access auditqualifier. This is set to blank if AUDIT_LEVEL isNONE, otherwise can be set to READ, UPDATE,CONTROL, or ALTER. FromDSBD_AUDIT_OKQUAL.

CONGRP_ID CHAR(8) The connect group of the user who created the dataset. From DSBD_GRP_ID.



CREATE_DATE DATE Date when the profile was created. FromDSBD_CREATE_DATE.

DATASET_OPTIONS CHAR(8) Data set profile options.


0 This is a generic profile. FromDSBD_GENERIC.

1 This is a group data set. FromDSBD_GRPDS.

2 WARNING attribute. FromDSBD_WARNING.

3 For a DASD data set, indicates if this data setis scratched when the data set is deleted.From DSBD_ERASE.

4-7 Reserved.

DEVICE_NAME CHAR(8) The EBCDIC name of the device type where the dataset resides. From DSBD_DEVICE_NAME.

DS_ALTER_CNT INTEGER The number of times that the data set was accessedwith ALTER authority. From DSBD_ALTER_CNT.

DS_CONTROL_CNT INTEGER The number of times that the data set was accessedwith CONTROL authority. FromDSBD_CONTROL_CNT.

DS_LEVEL SMALLINT The level of the data set. From DSBD_LEVEL.

DS_READ_CNT INTEGER The number of times that the data set was accessedwith READ authority. From DSBD_READ_CNT.

DS_TYPE CHAR(8) The type of the data set. Valid values are VSAM,NONVSAM, TAPe, and MODEL. FromDSBD_DS_TYPE.

DS_UPDATE_CNT INTEGER The number of times that the data set was accessedwith UPDATE authority. From DSBD_UPDATE_CNT.

GAUDIT_FAQUAL CHAR(8) The auditor-specified failing access audit qualifier.This is set to blank if GAUDIT_LEVEL is NONE,otherwise can be set to READ, UPDATE, CONTROL,or ALTER. From DSBD_GAUDIT_FAQUAL.

GAUDIT_LEVEL CHAR(8) Indicates the level of auditor-specified auditing that isperformed. Valid values are ALL, SUCCESS, FAIL,and NONE. From DSBD_GAUDIT_LEVEL.

GAUDIT_OKQUAL CHAR(8) The auditor-specified successful access audit qualifier.This is set to blank if GAUDIT_LEVEL is NONE,otherwise can be set to READ, UPDATE, CONTROL,or ALTER. From DSBD_GAUDIT_OKQUAL.

INSTALL_DATA VARCHAR(254) Installation-defined data. FromDSBD_INSTALL_DATA.

LASTCHG_DATE DATE Date when the data set was last changed. FromDSBD_LASTCHG_DATE.

LASTREF_DATE DATE Date when the data set was last referenced. FromDSBD_LASTREF_DATE.

NOTIFY_ID CHAR(8) The identifier of the user who is notified whenviolation occurs. From DSBD_NOTIFY_ID.



OWNER_ID CHAR(8) The user ID or group name that owns this profile.From DSBD_OWNER_ID.

SECLABEL CHAR(8) Security label of the data set. From DSBD_SECLABEL.

SECLEVEL SMALLINT Security level of the data set. From DSBD_SECLEVEL.

RETENTION INTEGER Retention period of the data set. FromDSBD_RETENTION.

UACC CHAR(8) The universal access of this data set. Valid values areNONE, EXECUTE, READ, UPDATE, CONTROL, andALTER. From DSBD_UACC.

RACF_DS_ACCESS_D

This table provides configuration information about the data set profiles and theirstandard access lists. It contains data from RACF record type 0404.





DS_NAME K VARCHAR(44) Data set name, as taken from the profile name. FromDSACC_NAME.

VOLUME K CHAR(6) Volume upon which this data set resides. Blank if theprofile is generic, and *MODEL if the profile is amodel profile. From DSACC_VOL.

AUTH_ID K CHAR(8) The user ID or group name that is authorized to thedata set. From DSACC_AUTH_ID.

ACCESS CHAR(8) The access granted to the user. Valid values areNONE, EXECUTE, READ, UPDATE, CONTROL, andALTER. From DSACC_ACCESS.

ACCESS_CNT INTEGER The number of times that the data set was accessed.From DSACC_ACCESS_CNT.

RACF_DS_CONDACC_D

This table provides configuration information about the data set profiles and theirconditional access lists. It contains data from RACF record type 0402.







DS_NAME K VARCHAR(44) Data set name, as taken from the profile name. FromDSCACC_NAME.

VOLUME K CHAR(6) Volume upon which this data set resides. Blank if theprofile is generic, and *MODEL if the profile is amodel profile. From DSCACC_VOL.

COND_TYPE K CHAR(8) The type of conditional access checking that is beingperformed. Valid values are APPCPORT, PROGRAM,CONSOLE, TERMINAL, JESINPUT, and SERVAUTH.From DSCACC_CATYPE.

COND_ELEMENT K CHAR(8) The name of a conditional access element that ispermitted access. From DSCACC_CANAME.

AUTH_ID K CHAR(8) The user ID or group name that is authorized to thedata set. From DSCACC_AUTH_ID.

ACCESS CHAR(8) The access of the conditional access element/usercombination. Valid values are NONE, EXECUTE,READ, UPDATE, CONTROL, and ALTER. FromDSCACC_ACCESS.

ACCESS_CNT INTEGER The number of times that the data set was accessed.From DSCACC_ACCESS_CNT.

NET_ID CHAR(8) The network name when COND_TYPE is APPCPORT.From DSCACC_ACCESS_CNT.

RACF_GENRES_D

This table provides configuration information about each general resource profiledefined in the RACF database. It contains data from RACF record type 0500.





CLASS_NAME K CHAR(8) Data set name, as taken from the profile name. FromDSCACC_NAME.

GR_NAME K VARCHAR(212) General resource name, as taken from the profilename. From GRBD_CLASS_NAME.

CREATE_DATE DATE Date when the profile was created. FromGBRD_CREATE_DATE.

OWNER_ID CHAR(8) The user ID or group name that owns this profile.From GRBD_OWNER_ID.

GR_LEVEL SMALLINT The level of the resource. From GRBD_LEVEL.



GR_OPTIONS CHAR(8) General resource profile options.


0 This is a generic profile. FromGRBD_GENERIC.

1 WARNING attribute. FromGRBD_WARNING.

2 For a TAPEVOL profile, indicates if there isonly one data set on this tape. FromGRBD_SINGLEDS.

3 For a TAPEVOL profile, indicates if theautomatic protection is active. FromGRBD_AUTO.

4 For a TAPEVOL profile, indicates if there is atape volume table of contents on this tape.From GRBD_TVTOC.

5-7 Reserved.

CLASS SMALLINT The class number of the profile. From GRBD_CLASS.

LASTREF_DATE DATE The date when the resource was last referenced. FromGRBD_LASTREF_DATE.

LASTCHG_DATE DATE The date when the resource was last changed. FromGRBD_LASTCHG_DATE.

UACC CHAR(8) The universal access of this resource. For profiles inclasses other than DIGTCERT, the valid values areNONE, READ, EXECUTE, UPDATE, CONTROL, andALTER. For DIFTCERT profiles, the valid values areTRUST, NTRUST, and HIGHTRST. FromGRBD_UACC.

GR_ALTER_CNT INTEGER The number of times that the resource was accessedwith ALTER authority. From GRBD_ALTER_CNT.

GR_CONTROL_CNT INTEGER The number of times that the resource was accessedwith CONTROL authority. FromGRBD_CONTROL_CNT.

GR_UPDATE_CNT INTEGER The number of times that the resource was accessedwith UPDATE authority. From GRBD_UPDATE_CNT.

GR_READ_CNT INTEGER The number of times that the resource was accessedwith READ authority. From GRBD_READ_CNT.

AUDIT_FAQUAL CHAR(8) The resource-owner-specified failing access auditqualifier. This is set to blank if AUDIT_LEVEL isNONE, otherwise can be set to READ, UPDATE,CONTROL, or ALTER. FromGRBD_AUDIT_FAQUAL.

AUDIT_OKQUAL CHAR(8) The resource-owner-specified successful access auditqualifier. This is set to blank if AUDIT_LEVEL isNONE, otherwise can be set to READ, UPDATE,CONTROL, or ALTER. FromGRBD_AUDIT_OKQUAL.

AUDIT_LEVEL CHAR(8) Indicates the level of resource-owner-specifiedauditing that is performed. Valid values are ALL,SUCCESS, FAIL, and NONE. FromGRBD_AUDIT_LEVEL.



GAUDIT_FAQUAL CHAR(8) The auditor-specified failing access audit qualifier.This is set to blank if GAUDIT_LEVEL is NONE,otherwise can be set to READ, UPDATE, CONTROL,or ALTER. From GRBD_GAUDIT_FAQUAL.

GAUDIT_LEVEL CHAR(8) Indicates the level of auditor-specified auditing that isperformed. Valid values are ALL, SUCCESS, FAIL,and NONE. From GRBD_GAUDIT_LEVEL.

GAUDIT_OKQUAL CHAR(8) The auditor-specified successful access audit qualifier.This is set to lank if GAUDIT_LEVEL is NONE,otherwise can be set to READ, UPDATE, CONTROL,or ALTER. From GRBD_GAUDIT_OKQUAL.

SECLABEL CHAR(8) Security label of the general resource. FromGRBD_SECLABEL.

SECLEVEL SMALLINT The security level of the general resource. FromGRBD_SECLEVEL.

NOTIFY_ID CHAR(8) The identifier of the user who is notified whenviolations occur. From GRBD_NOTIFY_ID.

INSTALL_DATA VARCHAR(254) Installation-defined data. FromGRBD_INSTALL_DATA.

APPL_DATA VARCHAR(254) Application-defined data. From GRBD_APPL_DATA.

RACF_GR_ACCESS_D

This table provides configuration information about the general resource profilesand their standard access lists. It contains data from RACF record type 0505.





CLASS_NAME K CHAR(8) Name of the class to which the general resourceprofile belongs. From GRACC_CLASS_NAME.

GR_NAME K VARCHAR(212) General resource name, as taken from the profilename. From GRACC_NAME.

AUTH_ID K CHAR(8) The user ID or group name that is authorized toaccess the general resource. From GRACC_AUTH_ID.

ACCESS CHAR(8) The authority that the user or group has for theresource. Valid values are NONE, READ, UPDATE,CONTROL, and ALTER. From GRACC_ACCESS.

ACCESS_CNT INTEGER The number of times that the resource was accessed.From GRACC_ACCESS_CNT.


RACF_GR_CONDACC_D

This table provides configuration information about the general resource profilesand their conditional access lists. It contains data from RACF record type 0507.





CLASS_NAME K CHAR(8) Name of the class to which the general resourceprofile belongs. From GRCACC_CLASS_NAME.

GR_NAME K VARCHAR(212) General resource name, as taken from the profilename. From GRCACC_NAME.

COND_TYPE K CHAR(8) The type of conditional access checking that is beingperformed. Valid values are CONSOLE, TERMINAL,JESINPUT, SYSID, APPCPORT, SERVAUTH, andPROGRAM. From GRCACC_CATYPE.

COND_ELEMENT K CHAR(8) The name of a conditional access element that ispermitted access. From GRCACC_CANAME.

AUTH_ID K CHAR(8) The user ID or group name that is authorized toaccess the general resource. From GRACC_AUTH_ID.

ACCESS CHAR(8) The authority of the conditional access element/usercombination. Valid values are NONE, READ,UPDATE, CONTROL, and ALTER. FromGRCACC_ACCESS.

ACCESS_CNT INTEGER The number of times that the general resource wasaccessed. From GRCACC_ACCESS_CNT.

NET_ID CHAR(8) The network name when COND_TYPE is APPCPORT. From GRCACC_NET_ID.

RACF_GROUPS_D

This table provides basic configuration information about each group defined inthe RACF database. It contains data from RACF record type 0100.





GROUP_NAME K CHAR(8) Group name. From GPBD_NAME.



CREATE_DATE DATE Date when the group was defined. FromGPBD_CREATE_DATE.

GROUP_OPTIONS CHAR(8) Group options.


0 The group must be specifically authorized touse a particular terminal through the use ofthe PERMIT command. FromGPBD_NOTERMUACC.

1 UNIVERSAL attribute. FromGPBD_UNIVERSAL.

2-7 Reserved.

INSTALL_DATA VARCHAR(254) Installation-defined data. FromGPBD_INSTALL_DATA.

MODEL_DS VARCHAR(44) Data set profile that is used as a model for this group.From GPBD_MODEL.

OWNER_ID CHAR(8) The user identifier or group name that owns thisgroup. From GPBD_OWNER_ID.

SUPGRP_ID CHAR(8) Name of the group superior to this group. FromGPBD_SUPGRP_ID.

UACC CHAR(8) The default universal access. Valid value is NONE forall groups other than the VSAMDSET group, whichhas CREATE. From GPBD_UACC.

RACF_USER_CON_D

This table provides information about the relationship about users and groups. Itcontains data from RACF record type 0205.





USER_ID K CHAR(8) User identifier, as taken from the profile name. FromUSCON_NAME.

GROUP_NAME K CHAR(8) Group name. From USCON_GRP_ID.



CONNECT_OPTIONS CHAR(8) User-group connection options.


0 ADSP attribute. From USCON_GRP_ADSP.

1 GROUP-SPECIAL attribute. FromUSCON_GRP_SPECIAL.

2 GROUP-OPERATIONS attribute. FromUSCON_GRP_OPER.

3 GROUP-AUDITOR attribute. FromUSCON_GRP_AUDIT.

4 GRPACC attribute. From USCON_GRP_ACC.

5 NOTERMUACC attribute. FromUSCON_NOTERMUACC.

6 Indicates if the user is revoked. FromUSCON_REVOKE.

7 Reserved.

CREATE_DATE DATE Date when the user-group connection was created.From USCON_CONNECT_DATE.

INIT_CNT INTEGER The default universal access. Valid value is NONE forall user IDs other than IBMUSER, which has READaccess to the SYS1, SYSCTLG, and VSAMDSETgroups. From USCON_UACC.

LASTCON_DATE DATE Date when the user last connected to this group. FromUSCON_LASTCON_DATE.

LASTCON_TIME TIME Time when the user last connected to this group.From USCON_LASTCON_TIME.

OWNER_ID CHAR(8) The owner of the user-group connection. FromUSCON_OWNER_ID.

RESUME_DATE DATE The date when the user connection to the group willbe resumed. From USCON_RESUME_DATE.

REVOKE_DATE DATE The date when the user connection to the group willbe revoked. From USCON_REVOKE_DATE.

UACC CHAR(8) The default universal access. Valid value is NONE forall user IDs other than IBMUSER, which has READaccess to the SYS1, SYSCTLG, and VSAMDSETgroups. From USCON_UACC.

RACF_USERS_D

This table provides basic configuration information about each user defined in theRACF database. It contains data from RACF record type 0200.







USER_ID K CHAR(8) User identifier, as taken from the profile name. FromUSBD_NAME.

CREATE_DATE DATE Date when the group was defined. FromUSBD_CREATE_DATE.

DEFGRP_ID CHAR(8) The default group associated with the user. FromUSBD_DEFGRP_ID.

END_TIME TIME Time after which the user can no longer log on. FromUSBD_END_TIME.

INSTALL_DATA VARCHAR(254) Installation-defined data. FromUSBD_INSTALL_DATA.

LASTJOB_DATE DATE The date when the user last entered the system. FromUSBD_LASTJOB_DATE.

LASTJOB_TIME TIME The time when the user last entered the system. FromUSBD_LASTJOB_TIME.

OWNER_ID CHAR(8) The user identifier or group name that owns thisprofile. From USBD_OWNER_ID.

PROGRAMMER VARCHAR(20) Name associated with the user ID. FromUSBD_PROGRAMMER.

PWD_GEN SMALLINT The current password generation number. FromUSBD_PWD_GEN.

PWD_INTERVAL SMALLINT The number of days that the user password can beused. From USBD_PWD_DATE.

PWD_DATE DATE The date when the password was last changed. FromUSBD_PWD_DATE.

PWD_NOPWD CHAR(1) Password bypass. From USBD_NOPWD. Possiblevalues are:

Y This user ID can log on without a passwordusing OID card.

N This user must specify a password.

P This is a protected user ID.

RESUME_DATE DATE The date when the user will be resumed. FromUSBD_RESUME_DATE.

REVOKE_CNT SMALLINT The number of unsuccessful logon attempts. FromUSBD_REVOKE_CNT.

REVOKE_DATE DATE The date when the user will be revoked. FromUSBD_REVOKE_DATE.

SECLABEL CHAR(8) The user default security label. FromUSBD_SECLABEL.

SECLEVEL SMALLINT The user security level. From USBD_SECLEVEL.

START_TIME TIME Time after which the user can log on. FromUSBD_START_TIME.



USER_OPTIONS CHAR(8) User options.


0 ADSP attribute. From USBD_ADSP.

1 SPECIAL attribute. From USBD_SPECIAL.

2 OPERATIONS attribute. From USBD_OPER.

3 AUDITOR attribute. From USBD_AUDITOR.

4 GRPACC attribute. From USBD_GRPACC.

5 RESTRICTED attribute. From USBD_ATTIBS.

6 Indicate if the user is revoked. FromUSBD_REVOKE.

7 Logging for RACHECK and RACDEF SVCs.From USBD_UAUDIT.

Lookup tablesThis section describes the lookup tables specific to the RACF component.

RACF_EVENT_CODE:RACF_EVENT_CODE

This lookup table converts RACF event codes and event code qualifiers todescriptions. For detailed information on RACF event codes, refer to RACF Macrosand Interfaces.

This table updates the RACF_COMMAND_T, RACF_LOGON_T,RACF_OPERATION_T, and RACF_RESOURCE_T tables.


EVENT_CODE K SMALLINT RACF event code to be converted to text.

EVENT_QUAL K SMALLINT RACF event code qualifier to be converted to text.

EVENT CHAR(10) Description for the event code.

EVENT_DESC CHAR(20) Description for the event code qualifier.


EVENT EVENT EVENTCODE QUAL EVENT DESC------ ------ ---------- --------------------

1 0 INIT/LOGON SUCCESSFUL INIT1 1 INIT/LOGON INVALID PASSWORD1 2 INIT/LOGON INVALID GROUP1 3 INIT/LOGON INVALID OIDCARD1 4 INIT/LOGON INVALID TERMINAL1 5 INIT/LOGON INVALID APPLICATION1 6 INIT/LOGON USER REVOKED1 7 INIT/LOGON AUTOMATIC REVOKE1 8 INIT/LOGON SUCCESSFUL TERMINATE1 9 INIT/LOGON UNDEFINED USERID1 10 INIT/LOGON INSUFF SECLABEL AUTH1 11 INIT/LOGON NOT AUTH SECLABEL1 12 INIT/LOGON SUCC RACINIT INIT1 13 INIT/LOGON SUCC RACINIT DELETE


1 14 INIT/LOGON MORE AUTHORITY REQ1 15 INIT/LOGON RJE JOB NOT AUTH1 16 INIT/LOGON SURROGAT CLASS INACT1 17 INIT/LOGON SUBMITTER NOT AUTH1 18 INIT/LOGON SUBM NOT AUTH SECLBL1 19 INIT/LOGON USER NOT AUTH TO JOB1 20 INIT/LOGON WARN: SECLABEL AUTH1 21 INIT/LOGON WARN: SECLBL MISSING1 22 INIT/LOGON WARN: SECLABEL AUTH1 23 INIT/LOGON SECLABELS INCOMPATIB1 24 INIT/LOGON WARN: SECLBL INCOMP1 25 INIT/LOGON PASSWORD EXPIRED1 26 INIT/LOGON INVALID NEW PASSWORD1 27 INIT/LOGON VERIFICATION FAILED1 28 INIT/LOGON GROUP ACCESS REVOKED1 29 INIT/LOGON OIDCARD REQUIRED1 30 INIT/LOGON NJE JOB NOT AUTH1 31 INIT/LOGON WARN: UNKNOWN USER1 32 INIT/LOGON SUCCESS PASSTICKET1 33 INIT/LOGON UNSUCCESS PASSTICKET1 34 INIT/LOGON DIFF CLNT/SRV LABELS

2 0 RES ACCESS SUCCESSFUL ACCESS2 1 RES ACCESS INSUFFICIENT AUTH2 2 RES ACCESS PROFILE NOT FOUND2 3 RES ACCESS WARNING MSG ISSUED2 4 RES ACCESS FAILED PROTECTALL2 5 RES ACCESS WARN: PROTECTALL2 6 RES ACCESS INSUFF CATGRY/SECLEV2 7 RES ACCESS INSUFF SECLABEL AUTH2 8 RES ACCESS WARN: SECLBL MISSING2 9 RES ACCESS WARN: INSUFF SECLBL2 10 RES ACCESS WARN: DS NOT CATALOG2 11 RES ACCESS DATA SET NOT CATALOGD2 12 RES ACCESS PROFILE NOT FOUND2 13 RES ACCESS WARN: CATGRY/SECLEV2 14 RES ACCESS WARN: NON-MAIN ENV2 15 RES ACCESS BASIC MODE COND ACC

3 0 ADD/CHGVOL SUCCESSFUL EOV3 1 ADD/CHGVOL INSUFFICIENT AUTH3 2 ADD/CHGVOL INSUFF SECLABEL AUTH3 3 ADD/CHGVOL DIFFERENT SECLABEL

4 0 RENAME DS SUCCESSFUL RENAME4 1 RENAME DS INVALID GROUP4 2 RENAME DS USER NOT IN GROUP4 3 RENAME DS INSUFFICIENT AUTH4 4 RENAME DS RESOURCE ALREADY DEF4 5 RENAME DS USER NOT DEFINED4 6 RENAME DS RESOURCE NOT PROTECT4 7 RENAME DS WARN: RES NOT PROT4 8 RENAME DS USER (2ND) NOT DEF4 9 RENAME DS DIFFERENT SECLABEL4 10 RENAME DS INSUFF SECLABEL AUTH4 11 RENAME DS NOT PROTECT BY SECLB4 12 RENAME DS NEW NAME NOT SECLB4 13 RENAME DS OLD SECLB IN EFFECT4 14 RENAME DS WARN: INS SECLB AUTH4 15 RENAME DS WARN: RES NOT PROT4 16 RENAME DS WARN: NEWN NOT PROT4 17 RENAME DS WARN: OLD SECLB ACT

5 0 DEL RES SUCCESSFUL SCRATCH5 1 DEL RES RESOURCE NOT FOUND5 2 DEL RES INVALID VOLUME IDENT


6 0 DEL 1 VOL SUCCESSFUL DELETE

7 0 DEF RES SUCCESSFUL DEFINE7 1 DEF RES GROUP UNDEFINED7 2 DEF RES USER NOT IN GROUP7 3 DEF RES INSUFFICIENT AUTH7 4 DEF RES RESOURCE ALREADY DEF7 5 DEF RES USER NOT DEFINED7 6 DEF RES RESOURCE NOT PROTECT7 7 DEF RES WARN: RES NOT PROT7 8 DEF RES WARN: SECLBL MISSING7 9 DEF RES WARN: INSUFF SECLBL7 10 DEF RES USER (2ND) NOT DEF7 11 DEF RES INSUFF SECLBL AUTH7 12 DEF RES DIFFERENT SECLBL

8 0 ADDSD SUCCESSFUL AD8 1 ADDSD INSUF AUTH,NO UPDATE8 2 ADDSD INSUF AUTH, PART UPD8 3 ADDSD SUCC (SECLBL CHANGE)8 4 ADDSD ERR (SECLBL CHANGE)

9 0 ADDGROUP SUCCESSFUL AG9 1 ADDGROUP INSUF AUTH,NO UPDATE9 2 ADDGROUP INSUF AUTH, PART UPD

10 0 ADDUSER SUCCESSFUL AU10 1 ADDUSER INSUF AUTH,NO UPDATE10 2 ADDUSER INSUF AUTH, PART UPD

11 0 ALTDSD SUCCESSFUL ALD11 1 ALTDSD INSUF AUTH,NO UPDATE11 2 ALTDSD INSUF AUTH, PART UPD11 3 ALTDSD SUCC (SECLBL CHANGE)11 4 ALTDSD ERR (SECLBL CHANGE)

12 0 ALTGROUP SUCCESSFUL ALG12 1 ALTGROUP INSUF AUTH,NO UPDATE12 2 ALTGROUP INSUF AUTH, PART UPD

13 0 ALTUSER SUCCESSFUL ALU13 1 ALTUSER INSUF AUTH,NO UPDATE13 2 ALTUSER INSUF AUTH, PART UPD

14 0 CONNECT SUCCESSFUL CO14 1 CONNECT INSUF AUTH,NO UPDATE14 2 CONNECT INSUF AUTH, PART UPD

15 0 DELDSD SUCCESSFUL DD15 1 DELDSD INSUF AUTH,NO UPDATE15 2 DELDSD INSUF AUTH, PART UPD15 3 DELDSD SUCC (SECLBL CHANGE)15 4 DELDSD ERR (SECLBL CHANGE)

16 0 DELGROUP SUCCESSFUL DG16 1 DELGROUP INSUF AUTH,NO UPDATE16 2 DELGROUP INSUF AUTH, PART UPD

17 0 DELUSER SUCCESSFUL DU17 1 DELUSER INSUF AUTH,NO UPDATE17 2 DELUSER INSUF AUTH, PART UPD

18 0 PASSWORD SUCCESSFUL PW18 1 PASSWORD INSUF AUTH,NO UPDATE18 2 PASSWORD INSUF AUTH, PART UPD19 0 PERMIT SUCCESSFUL PE19 1 PERMIT INSUF AUTH,NO UPDATE


19 2 PERMIT INSUF AUTH, PART UPD

20 0 RALTER SUCCESSFUL RALT20 1 RALTER INSUF AUTH,NO UPDATE20 2 RALTER INSUF AUTH, PART UPD

21 0 RDEFINE SUCCESSFUL RDEF21 1 RDEFINE INSUF AUTH,NO UPDATE21 2 RDEFINE INSUF AUTH, PART UPD

22 0 RDELETE SUCCESSFUL RDEL22 1 RDELETE INSUF AUTH,NO UPDATE22 2 RDELETE INSUF AUTH, PART UPD

23 0 REMOVE SUCCESSFUL RE23 1 REMOVE INSUF AUTH,NO UPDATE23 2 REMOVE INSUF AUTH, PART UPD

24 0 SETROPTS SUCCESSFUL SETR24 1 SETROPTS INSUF AUTH,NO UPDATE24 2 SETROPTS INSUF AUTH, PART UPD

25 0 RVARY SUCCESSFUL RVARY25 1 RVARY INSUF AUTH,NO UPDATE25 2 RVARY INSUF AUTH, PART UPD

26 0 APPC SESS SUCCESSFUL APPC SESS26 1 APPC SESS NO VERIFICATION26 2 APPC SESS LU KEY WILL EXPIRE26 3 APPC SESS PARTNER ACCESS REVOK26 4 APPC SESS LU KEY MISMATCH26 5 APPC SESS SESSION TERMINATED26 6 APPC SESS SESSION KEY NOT DEF26 7 APPC SESS SECURITY ATTACK26 8 APPC SESS PARTNER KEY NOT DEF26 9 APPC SESS KEY NOT DEF FOR LU26 10 APPC SESS SNA PROTOCOL ERROR26 11 APPC SESS PROFILE CHANGE26 12 APPC SESS EXPIRED SESSION KEY

27 0 GENERAL GEN PURPOSE AUDITING

28 0 DIR SEARCH SUCCESS DIR SEARCH28 1 DIR SEARCH INSUFF AUTH28 2 DIR SEARCH SECURITY LABEL FAIL

29 0 CHECK DIR SUCCESS CHECK DIR29 1 CHECK DIR INSUFF AUTH29 2 CHECK DIR SECURITY LABEL FAIL

30 0 CHECK FILE SUCCESS CHECK FILE30 1 CHECK FILE INSUFF AUTH30 2 CHECK FAIL SECURITY LABEL FAIL

31 0 CHAUDIT SUCC FILE AUDIT CHG31 1 CHAUDIT INSUFF AUTH ON FILE31 2 CHAUDIT INSUFF AUTH ON CMD31 3 CHEAUDIT SECURITY LABEL FAIL

32 0 CHDIR SUCCESS CHANGE DIR

33 0 CHMOD SUCC CHG FILE MODE33 1 CHMOD INSUFF AUTH33 2 CHMOD SECURITY LABEL FAIL

34 0 CHOWN SUCCESS CHG OWNER


34 1 CHOWN INSUFF AUTH34 2 CHOWN SECURITY LABEL FAIL

35 0 CLR SETID SUCCESS CLEAR SETID

36 0 EXEC SETxx SUCC CHG UID AND GID

37 0 GETPSENT ACCESS ALLOWED37 1 GETPSENT INSUFF AUTH

38 0 DUB PROCESS INITIATED38 1 DUB USER NOT DEFINED38 2 DUB UID IN USER PROF38 3 DUB NO GID IN USER PROF

39 0 UNDUB PROCESS COMPLETED

40 0 KILL ACCESS ALLOWED40 1 KILL INSUFF PROCESS AUTH40 2 KILL SECURITY LABEL FAIL

41 0 LINK NEW LINK CREATED

42 0 MKDIR DIRECTORY CREATED

43 0 MKNOD NODE CREATED

44 0 MOUNT HFS SUCCESS MOUNT

45 0 OPEN FILE FILE CREATED

46 0 PTRACE ACCESS46 1 PTRACE INSUFF PROCESS AUTH46 2 PTRACE SECURITY LABEL FAIL

47 0 RENAME RENAME SUCCESSFULL

48 0 RMDIR RMDIR SUCCESSFULL

49 0 SETEGID REAL GID CHANGED49 1 SETEGID INSUFF SETEGID AUTH

50 0 SETEUID REAL UID CHANGED50 1 SETEUID INSUFF SETEUID AUTH

51 0 SETGID GID CHANGED51 1 SETGID INSUFF SETGID AUTH

52 0 SETUID UID CHANGED52 1 SETUID INSUFF SETUID AUTH

53 0 SYMLINK SYMLINK SUCCESSFUL

54 0 UNLINK UNLINK SUCCESSFULL

55 0 UNMOUNT UNMOUNT HFS SUCCESS

56 0 CHK FILE USER IS OWNER56 1 CHK FILE USER IS NOT OWNER56 2 CHK FILE SECURITY LABEL FAIL

57 0 CH_PRIV USER IS AUTHORIZED57 1 CH_PRIV INSUFF AUTH

58 0 OPEN TTY ACCESS ALLOWED58 1 OPEN TTY INSUFF PROCESS AUTH


59 0 RACLINK NO VIOLATION59 1 RACLINK INSUFF AUTH59 2 RACLINK KEYWORD VIOLATION59 3 RACLINK ASSOC. ALREADY DEF.59 4 RACLINK ASSOC. ALREADY APPR.59 5 RACLINK ASSOC. DOESN’T MATCH59 6 RACLINK ASSOC. DOESN’T EXIST59 7 RACLINK INV. PW OR REVOKE ID

60 0 CHK IPC ACCESS ALLOWED60 1 CHK IPC INSUFF AUTH60 2 CHK IPC SECURITY LABEL FAIL

61 0 MAKE ISP ISP SUCCESS CREATED61 1 MAKE ISP SECURITY LABEL FAIL

62 0 R_IPC CTRL ACCESS ALLOWED62 1 R_IPC CTRL INSUFF AUTH62 2 R_IPC CTRL SECURITY LABEL FAIL

63 0 SETGROUPS SUCCESS SETGROUPS63 1 SETGROUPS INSUFF AUTH

64 0 OWN 2 FILE USER IS THE OWNER64 1 OWN 2 FILE USER IS NOT OWNER64 2 OWN 2 FILE SECURITY LABEL FAIL

65 0 R_AUDIT R_AUDIT SUCCESSFULL

66 0 RADCERT SUCCESS RACDCERT66 1 RADCERT INSUFF AUTH

67 0 initACEE CERTIFICATE REG.67 1 initACEE CERTIFICATE DEREG.67 2 initACEE INSUFF REGISTER AUTH67 3 initACEE INSUFF DEREG. AUTH67 4 initACEE NO USERID FOR CERTIF67 5 initACEE CERTIF NOT TRUSTED67 6 initACEE SUCC CERT AUTH REG67 7 initACEE INSUFF AUTH TO REG67 8 initACEE DIFF CLNT/SRV LABELS

68 0 GRANT IKT SUCCESS68 1 GRANT IKT FAILURE

69 0 R_PKI GENC SUCCESSFUL GENCERT69 1 R_PKI GENC INSUFF GENCERT AUTH69 2 R_PKI GENC SUCCESSFUL REQCERT69 3 R_PKI GENC INSUFF REQCERT AUTH69 4 R_PKI GENC SUCCESSFUL GENRENEW69 5 R_PKI GENC INSUFF GENRENEW AUTH69 6 R_PKI GENC SUCCESSFUL REQRENEW69 7 R_PKI GENC INSUFF REQRENEW AUTH

70 0 R_PKI EXP SUCCESSFUL EXPORT70 1 R_PKI EXP INSUFF EXPORT AUTH70 2 R_PKI EXP WRONG EXPORT PASSW

71 0 POLDIR ACC AUTHORIZED71 1 POLDIR ACC WARN BUT PERMITTED71 2 POLDIR ACC WANR ISUFF TRAV AUTH71 3 POLDIR ACC WARN TIMEOFDAY CHECK71 4 POLDIR ACC NOT AUTHORIZED71 5 POLDIR ACC INSUFF TRAVERSE AUTH71 6 POLDIR ACC TIMEOFDAY CHECK

72 0 R_PKI QD V SUCC QUERY / DETAILS


72 1 R_PKI QD V INSUFF AUTH Q OR D72 2 R_PKI QD V SUCCESSFUL VERIFY72 3 R_PKI QD V INSUFF AUTH VERIFY72 4 R_PKI QD V WRONG VERIFY CERT

73 0 R_PKI UPDR SUCCESSFUL UPDATEREQ73 1 R_PKI UPDR INSUF AUTH UPDATEREQ

74 0 R_PKI U R SUCCESSFUL UPDATECERT74 1 R_PKI U R INSUF AUTH UPDATECERT74 2 R_PKI U R SUCCESSFUL REVOKE74 3 R_PKI U R INSUF AUTH REVOKE

75 0 CHG ACL ACL SUCCESSFULLY CHANGED75 1 CHG ACL INSUFF AUTH CHG ACL75 2 CHG ACL SEC LABEL FAILURE

76 0 REMOVE ACL ACL SUCCESSFULLY CHANGED76 1 REMOVE ACL INSUFF AUTH REM ACL76 2 REMOVE ACL SEC LABEL FAILURE

77 0 R_SETFSECL SUCCESS SEC LABEL CHG77 1 R_SETFSECL INSUFF AUTH CHG LAB

78 0 R_WRITPRIV SUCCESSFUL78 1 R_WRITPRIV NOT AUTHORIZED

79 0 CRL PUBL Z/OS CRYPTO SERV

RACF_OMVS_AUDCODE:RACF_OMVS_AUDCODE

This lookup table converts z/OS UNIX audit function codes to descriptions. Fordetailed information about audit function codes, refer to the RACF data area.

This table updates the RACF_OMVS_RES_T table.


AUDIT_CODE K SMALLINT z/OS UNIX System Services audit function codes toconvert in text.

AUDIT_DESC CHAR(20) Description of OS/390 UNIX System Services auditfunction code.

AUDIT_NAME CHAR(20) OS/390 UNIX System Services audit function name.

Example of table contentsAudit code Audit Name Audit descr

---------- ---------- -----------------------1 ACCESS CHECK FILE ACCESS2 CHAUDIT_U CHG USER AUDIT OPT3 CHDIR CHG CURRENT WORK DIR4 CHMOD CHG FILE MODES5 CHOWN CHG OWNER AND GROUP6 DUB INITIALIZE PROCESS7 EXEC EXECUTE A FILE8 FCHAUDIT_U CHG USER AUDIT OPEN9 FCHMOD CHG FILEMODE OPEN10 FCHOWN CHG OWNER GROUP OPEN11 GETCWD GET WORKING DIR12 GETPSENT GET PROCESS ENTRY13 KILL SIGNAL A PROCESS14 LINK LINK TO A FILE15 LSTAT GET FILE STATUS


16 MKDIR MAKE A DIRECTORY17 MKNOD MAKE A FILE NODE18 MOUNT MOUNT A FILE SYSTEM19 OPEN OPEN A FILE20 OPENDIR OPEN A DIRECTORY21 PATHCONF GET PATHNAME VAR22 PTRACE DEBUG A PROCESS23 READLINK READ A SYMBOLIC NAME24 RENAME RENAME A FILE25 RMDIR REMOVE A DIRECTORY26 SETEGID SET EFFECTIVE GID27 SETEUID SET EFFECTIVE UID28 SETGID SET GID29 SETUID SET UID30 STAT GET FILE STATUS31 SYMLINK CRT A SYMBOLIC LINK32 UNLINK REMOVE DIRECTORY33 UNMOUNT UNMOUNT A FILE34 UTIME SET FILE TIME35 UNDUB_EXIT TERMINATE A PROCESS36 WRITE WRITE TO A FILE37 CHAUDIT_A CHG AUD AUDIT OPTS38 FCHAUDIT_A CHG AUD AUD OPT OPEN39 LOOKUP PATHNAME RESOLUTION40 TTYNAME GET TERMINAL PATH41 IOCTL GET PATHNAME42 GETMNT GET MOUNT ENTRY43 QUIESCE QUIESCE A FILE44 UNQUIESCE UNQUIESCE A FILE45 VREGISTER SERVER REGISTRATION46 VRESOLVEPN SERVER RESOLVE PATH47 VLOOKUP SERVER LOOKUP48 VREADWRITE SERVER READ WRITE49 VREADDIR SERVER READ DIR50 SIGACTION CHG OSIGSET ACTION51 VCREATE SERVER CREATE52 VMAKEDIR SERVER MAKE DIR53 VSYMLINK SERVER SYMBOLIC LINK54 VSETATTR SERVER SET FILES55 VLINK SERVER LINK56 VREMOVEDIR SERVER REMOVE DIR57 VREMOVE SERVER REMOVE58 VRENAME SERVER RENAME59 CHATTR CHG FILE ATTRIBUTES60 FCHATTR CHG FILE ATTR. OPEN61 THLMT SET THREAD LIMIT62 MSGCTL MESSAGE CONTROL63 MSGGET MESSAGE OBTAIN64 MSGRCV MESSAGE RECEIVE65 MSGSND MESSAGE SEND66 SEMCTL SEMAPHORE CONTROL67 SEMGET GET SET SEMAPHORE68 SEMOP SEMAPHORE OPERATIONS69 SHMAT SHARED MEMORY ATTACH70 SHMCTL SHARED MEMORY CTRL71 SETREGID SET REAL GID72 SHMGET SHARED MEMORY GET73 WGETIPC QUERY IPC STATUS74 REMOVE REMOVE75 SET_MODE SET MODE76 SET_MSGQB SET MSGQ MAX BYTES77 SET_GID GET SUPPLEMENT GROUP78 PASSWORD VERIFY PASSWORD79 LCHOWN CHG OWNER SYMB LINK80 TRUNCATE TRUNCATE A FILE81 PFSCTL CTRL PHYSICAL FILE82 SETRLIMIT SET MAX CONSUPTIONS


83 SETPRIORITY SET PROCESS PRIORITY84 NICE CHG PRIORITY PROCESS85 SETREUID SET REAL UID86 WRITEV WRITE ON A FILE87 FCHDIR CHG WORKING DIR88 CHROOT CHG ROOT DIR89 REALPATH RESOLVE PATHNAME90 STATVFS GET FILE SYSTEM INF.91 BIND BIND NAME TO SOCKET92 SOCKET CREATE AN ENDPOINT93 THREAD_SEC THREAD LLV SECURITY94 AUTHCHECK AUTHORITY CHECK95 ACC_SEND SEND ACCESS RIGHT96 ACC_RECV RECEIVE ACCESS RIGHT97 ACC_DISC DISCARD ACCESS RIGHT98 NEWGRP NEWGRP SHELL UTILITY99 CONSOLE CONSOLE COMMUNIC.100 SERV_INIT WLM SERVICE CONSOLE101 SPAWN SPAWN102 SWAP_SERV SWAP SERVICES103 WLMC WLM C AND C++104 LOGIN LOGIN SYSTEM CALL105 MOUNT_SETUID MOUNT A FILE SYSTEM106 UNMOUNT_SETUID UNMOUNT FILE SYSTEM107 QUIESCE_SETUID QUIESCE A FILE SYS108 UNQUIESCE_SETUID UNQUIESCE FILE SYS109 CHMOUNT CHGMOUNT FILE SYS110 CHMOUNT_SETUID CHGMOUNT FS SETUID111 SETAFCL ADD ALT DEL ACL112 SHUTDOWN_REG SHUTDOWN REG113 EACCESS CHK EFFECTIVE ACCESS114 SETFSECL SET FILE SET LABEL115 POE PORT OF ENTRY ID116 LCHATTR CHG FILE ATTRIBUTES117 ENDOF_TAB END OF TABLE

RACF_RES_OWNER:RACF_RES_OWNER

This lookup table links the RACF-protected resource to the responsible user of theresource, that is, the receiver of the report. You can load the data of this table froman unloaded RACF database by running the DRLJRACF job. For details, refer toUpdating RACF_USER_OWNER and RACF_RES_OWNER tables.

The information in this table is used only during reporting.


SYSTEM_ID K CHAR(4) System ID.

CLASS K CHAR(8) Resource class.

PROFILE_NAME K VARCHAR(44) Profile name.

GENERIC K CHAR(1) Indicates whether the data set profile is generic. Thiscan be Y (generic) or N (discrete).

RESPONSIBLE_USER CHAR(8) Responsible user. This is the receiver of the report.

SECLEVEL SMALLINT A number designating the security level assigned tothe resource. This is zero if the security level is notdefined.

SECLEVEL_NAME VARCHAR(44) Security-level name describing the numeric securitylevel. This is blank if the security level is not defined.



SYSTEM PROFILE RESPONSIBLE SECLEVELID CLASS NAME GENERIC USER SECLEVEL NAME

------ -------- --------... ------- ----------- -------- --------------...MVS1 DATASET DRL180.* Y STROMBK 50 RESTRICTED USE•••

RACF_USER_OWNER:RACF_USER_OWNER

This lookup table links a RACF-defined user to the responsible user, that is, thereceiver of the report. You can load the data of this table from an unloaded RACFdatabase by running the DRLJRACF job. For details, refer to UpdatingRACF_USER_OWNER and RACF_RES_OWNER tables.

The information in this table is used only during reporting.


SYSTEM_ID K CHAR(4) System ID.

USER_ID K CHAR(8) User ID.

RESPONSIBLE_USER CHAR(8) Responsible user. This is the receiver of the report.

SECLEVEL SMALLINT A number designating the security level assigned tothe user. This is zero if the security level is notdefined.

SECLEVEL_NAME VARCHAR(44) Security-level name describing the numeric securitylevel. This is blank if the security level is not defined.

Example of table contentsSYSTEM USER RESPONSIBLE SECLEVEL

ID ID USER SECLEVEL NAME------ -------- ----------- -------- -----------------MVS1 STROMBK LASZLOM 100 CONFIDENTIAL•••

ReportsAs described in Evaluating the RACF component, the RACF component containstwo subcomponents:1. RACF Activity2. RACF Configuration

The RACF Activity subcomponent provides the following reports:v RACF Logon/Job Failures reportv RACF Command Failures - Auditor reportv RACF SPECIAL User Commands - Auditor reportv RACF AUDITOR User Commands - Auditor reportv RACF OPERATIONS User Access - Auditor reportv RACF Resource Access Failures reportv RACF Resource Accesses report


v RACF SUPERUSER Security Commands - Auditor reportv RACF OpenEdition Resource Accesses reportv RACF OpenEdition Resource Accesses Failures reportv RACF Initialization reportv RACF Class Initialization reportv RACF Terminals with Excessive Incorrect Passwords reportv RACF Users with Excessive Incorrect Passwords reportv RACF All Events for a Specific User reportv RACF Data Sets with a Specific Name Access reportv RACF Data Sets with Particular Authority reportv RACF Resources Accessed Because Installation Exit reportv RACF Resources Accessed Because Warning Mode reportv RACF Generic Profiles Used for Resource Access report

The RACF Configuration subcomponent provides the following reports:v RACF Number of Profiles in the Database reportv RACF Group List reportv RACF Users with Particular System Privileges reportv RACF Users with Particular Group Level Privileges reportv RACF Users Currently Revoked reportv RACF Users Last Defined reportv RACF Users with NOINTERVAL Specified reportv RACF Users with Too Many Group Connections reportv RACF Users Members of SYS1 Group reportv RACF Dataset Profiles for Each HLQ reportv RACF Dataset Profiles with UACC Other than NONE reportv RACF Dataset Profiles in WARNING Mode reportv RACF Dataset Standard ACL with ID(*) Not NONE reportv RACF Dataset Condit. ACL with ID(*) Not NONE reportv RACF GR Number of Profiles for Each Class reportv RACF GR Discrete Profiles with Wild Characters reportv RACF GR Profiles with UACC Other than NONE reportv RACF GR Profiles in WARNING Mode reportv RACF GR Profiles Standard ACL with ID(*) not NONE reportv RACF GR Profiles Condit. ACL with ID(*) Not NONE report

RACF Activity reportsThe reports described in this section are for the RACF Activity subcomponent,which provides details about the security activity recorded by RACF on SMFrecord.

RACF Logon/Job Failures report:This report shows logon and job failures, by responsible user and user ID.


Report IDRACF01


Report groupRACF Activity reports

SourceRACF_LOGON_T,

AttributesRACF, Security, Logon, Job, Exception

VariablesFrom_date, To_date, System_ID


Responsible userThe user responsible for the auditing and follow-up of the event. This is aquestion mark (?) if no match is found in the RACF_USER_OWNERlookup table.

User IDThe ID of the user for whom the event (logon or job violation) wasrecorded. The job name is used if the user is not defined to RACF.

Date The date when the failed logon or job attempt occurred.

Time The time when the failed logon or job attempt occurred.

Terminal IDThe terminal ID (if available) of the foreground user.

Application nameThe name of the application.

Event descThe description for the event code qualifier.

RACF Command Failures - Auditor report:This report shows RACF command failures, by user, command, and resource.


RACF Logon/Job FailuresSystem: ’MVS1’

Date: ’2003-12-08’ to ’2003-12-09’

Responsible User Terminal Application Eventuser ID Date Time ID name desc

----------- -------- ---------- -------- -------- ----------- --------------------? JERRY 2003-12-08 07.37.21 IS1S1815 - INVALID PASSWORD

WILLIAM 2003-12-08 08.12.16 - INVALID PASSWORDWILLIAM 2003-12-08 08.14.03 IS1V9E61 - INVALID PASSWORD

--------------------* 3

====================3

Tivoli Decision Support for z/OS Report: RACF01

Figure 123. Example of a RACF Logon/Job Failures report


Report IDRACF02


SourceRACF_COMMAND_T

AttributesRACF, Security, Command, Exception



User IDThe ID of the user for whom the command failure is recorded.

CommandThe name of the RACF command used.

Resource nameThe name of the resource on which the RACF command was to operate.

Date The date when the user entered the RACF command.

Time The time when the user entered the RACF command.


RACF SPECIAL User Commands - Auditor report:This report shows commands issued by users with the SPECIAL orGroup-SPECIAL attribute, by command and user.


Report IDRACF03


RACF Command Failures - Auditor ReportSystem: ’MVS1’

Date: ’2003-12-08’ to ’2003-12-09’

User ID Command Resource name Date Time Event desc-------- -------- ------------------------------ ---------- -------- --------------------LASZLO ADDGROUP DEV22 2003-12-08 12.51.41 INSUF AUTH,NO UPDATE

PERMIT DEV22 2003-12-08 12.53.09 INSUF AUTH,NO UPDATE--------------------

* 2

====================2


Figure 124. Example of a RACF Command Failures - Auditor report



AttributesRACF, Security, Command, Special, Detail




User IDThe ID of the user for whom the special user command is recorded.




RACF AUDITOR User Commands - Auditor report:This report shows commands issued by users with the AUDITOR orGroup-AUDITOR attribute, by command and user.

For more information on using this report, refer to the System Performance FeatureGuide.


Report IDRACF04



RACF SPECIAL User Commands - Auditor ReportSystem: ’MVS1’

Date: ’2003-12-08’ to ’2003-12-09’

Command User ID Resource name Date Time-------- -------- ------------------------------ ---------- --------ADDSD HLPDESK RICHARD.* 2003-12-08 09.26.22ADDSD HLPDESK SCHRAB.* 2003-12-08 09.24.51ADDUSER HLPDESK RICHARD 2003-12-08 09.26.21ADDUSER HLPDESK SCHRAB 2003-12-08 09.24.49CONNECT HLPDESK EUAPL 2003-12-08 09.28.02CONNECT HLPDESK EUAPL 2003-12-08 09.28.11PERMIT HLPDESK TRANSMIT 2003-12-08 09.36.36PERMIT HLPDESK XMIT 2003-12-08 09.36.12PERMIT HLPDESK XMIT 2003-12-08 09.36.26


Figure 125. Example of a RACF SPECIAL User Commands - Auditor report


AttributesRACF, Security, Command, Auditor, Detail




User IDThe ID of the user for whom the auditor command is recorded.




RACF OPERATIONS User Access - Auditor report:This report shows resource accesses performed by users with the OPERATIONSattribute, by responsible user, user, and resource. All accesses against resourceswith a security level higher than the specified one are included.


Report IDRACF05


SourceRACF_OPERATION_T, RACF_RES_OWNER

AttributesRACF, Security, Access, Operations, Detail


RACF AUDITOR User Commands - Auditor ReportSystem: ’MVS1’

Date: ’2003-12-08’ to ’2003-12-09’

Command User ID Resource name Date Time-------- -------- ------------------------------ ---------- --------SETROPTS SVENNEG - 2003-12-08 08.50.46


Figure 126. Example of a RACF AUDITOR User Commands - Auditor report



Responsible userThe responsible user. This is the receiver of the report and is a questionmark (?) if no match is found in the RACF_USER_OWNER lookup table.

User IDThe ID of the user for whom the operation is recorded. The job name isused if the user is not defined to RACF.

Resource nameThe name of the RACF-protected resource accessed.

SeclevelThe number designating the security level assigned to the resource. This iszero if the security level is not defined or if no match is found in theRACF_RES_OWNER lookup table.

GenericThe character indicating whether the data set profile is generic. This can beY (generic) or N (discrete).

Event The event description.

Date The date of the event.

Time The time of the event.


RACF Resource Access Failures report:This report shows resource access failures, by responsible user, class, resource, anduser. All access against resources with a security level higher than the specified oneare included.

For more information on using this report, refer to the System Performance FeatureGuide.


Report IDRACF06

RACF OPERATIONS User Access - Auditor ReportSystem: ’MVS1’

Date: ’2003-12-08’ to ’2003-12-09’Minimum security level: 0

Responsible User Resource Sec- Gen- Eventuser ID name level eric Event Date Time desc

----------- -------- ------------------------ ----- ---- ---------- ---------- -------- ------------------? OPERATO SYS1.PPCAT 0 Y RES ACCESS 2003-12-08 07.45.01 SUCCESSFUL ACCESS

OPERATO SYS1.PPCAT 0 Y RES ACCESS 2003-12-08 08.33.49 SUCCESSFUL ACCESSOPERATO SYS1.PPCAT 0 Y RES ACCESS 2003-12-08 08.36.55 SUCCESSFUL ACCESSOPERATO SYS1.PPCAT 0 Y RES ACCESS 2003-12-08 08.39.35 SUCCESSFUL ACCESS:PROCUSER ZAWISZA.LOADLIB 0 Y ADD/CHGVOL 2003-12-08 09.28.09 SUCCESSFUL EOVPROCUSER ZAWISZA.PLI.OBJ 0 Y ADD/CHGVOL 2003-12-08 09.26.55 SUCCESSFUL EOV

Tivoli Decision Support for z/OS report: RACF05

Figure 127. Example of a RACF OPERATIONS User Access - Auditor report



SourceRACF_RESOURCE_T, RACF_RES_OWNER

AttributesRACF, Security, Access, Exception



Responsible userThe responsible user. This is the receiver of the report and is a questionmark (?) if no match is found in the RACF_RES_OWNER lookup table.

Class The resource class.




User IDThe ID of the user who attempted to access a RACF-protected resourcesystem.

RACF Resource Access FailuresSystem: ’MVS1’


Responsible Sec- Resource Gen- User Access Access Eventuser Class level name eric ID request allowed Date desc

----------- -------- ----- ------------------ ---- -------- ------- ------- ---------- -------------------? DATASET 0 CCC.BEX.CLIST Y ROGER READ NONE 2003-12-08 WARNING MSG I

DATASET 0 IN.GDDM.SMPACDS Y WILLIAM ALTER READ 2003-12-08 INSUFFICIENT AUTHDATASET 0 MAP.SLVV1R1.PLSV N CORNALE ALTER CONTROL 2003-12-08 INSUFFICIENT AUTHDATASET 0 PS.V3R2.FORMATS Y WIELATH UPDATE READ 2003-12-08 INSUFFICIENT AUTH

-------------------* 4

PRODTEST DATASET 5 PROD.TEST2.LOAD N JERRY READ NONE 2003-12-08 INSUFFICIENT AUTHDATASET 5 PROD.TEST2.LOAD N JERRY READ NONE 2003-12-08 INSUFFICIENT AUTH

-------------------* 2

===================6


Figure 128. Example of a RACF Resource Access Failures report


Access requestThe access authority requested. This can be ALTER, CONTROL, UPDATE,READ, or NONE.

Access allowedThe access authority allowed. This can be ALTER, CONTROL, UPDATE,READ, or NONE.



RACF Resource Accesses report:This report shows resource accesses, by responsible user, class, resource, and user.All accesses against resources with a security level higher than the specified oneare included.


Report IDRACF07


SourceRACF_RESOURCE_T,

AttributesRACF, Security, Access, Detail



RACF Resource AccessesSystem: ’MVS1’


Responsible Sec- Resource Gen- User Access Access Eventuser Class level name eric ID request allowed Date desc

----------- ------- ----- ------------------------------ ---- -------- ------- ------- ---------- ------------------? APPL 0 OPCH N JERRY UPDATE ALTER 2003-12-08 SUCCESSFUL AC

DATASET 0 ACCT.LOGREC Y OPERATO UPDATE ALTER 2003-12-09 SUCCESSFUL ACCESSDATASET 0 ACCT.LOGREC.G0425V00 Y OPERATO ALTER ALTER 2003-12-09 SUCCESSFUL ACCESSDATASET 0 DBL1.DSNDBC.DSNDB04.FLIGHT.I00 Y PROCUSER ALTER ALTER 2003-12-08 SUCCESSFUL ACCESSDATASET 0 DBL1.DSNDBC.DSNDB04.FLIGHT.I00 Y PROCUSER ALTER ALTER 2003-12-08 SUCCESSFUL ACCESS:SURROGAT 0 HLPDESK.MVS N WILLIAM CONTROL CONTROL 2003-12-09 SUCCESSFUL ACCESSSURROGAT 0 OPERATO.MVS N THOMAS CONTROL CONTROL 2003-12-09 SUCCESSFUL ACCESS

-------------------* 12,376

===================12,376


Figure 129. Example of a RACF Resource Accesses report


Responsible userThe responsible user. This is the receiver of the report and is a questionmark (?) if no match is found in the RACF_USER_OWNER lookup table.

Class The resource class.




User IDThe ID of the user who accessed the RACF-protected system resources.

Access requestThe access authority requested. This can be ALTER, CONTROL, UPDATE,READ, or NONE.

Access allowedThe access authority allowed. This can be ALTER, CONTROL, UPDATE,READ, or NONE.



RACF SUPERUSER Security Commands - Auditor report:This report shows OpenEdition security services (CHAUDIT, CHMOD, CHOWN)that required SUPERUSER authority.


Report IDRACF08


SourceRACF_OMVS_SEC_T

AttributesRACF, Security, Command, OMVS, OpenEdition, Superuser




OS/390 Unix security serviceThe OpenEdition security service that was issued.

User IDThe ID of the user with superuser authority.

Date The date when the user invoked OpenEdition services.

Time The time when the user invoked OpenEdition services.

Resource pathnameThe pathname of the resource.

RACF OpenEdition Resource Accesses report:This report shows OpenEdition failures of resource accesses by user.


Report IDRACF09


SourceRACF_OMVS_RES_T

AttributesRACF, Access, OMVS, OpenEdition, EXECEPTION


RACF SUPERUSER Security Commands - Auditor ReportSystem: ’ES38’

Date: ’2003-01-01’ to ’2003-12-01’

OS/390 Unixsecurityservice User ID Date time Resource pathname----------- -------- ---------- -------- -----------------------CHAUDIT ROOT 2003-10-08 11.21.30 /u/user1CHAUDIT ROOT 2003-10-08 11.22.32 /bin/shCHAUDIT ROOT 2003-10-08 11.23.07 /etc/hostsCHMOD ROOT 2003-10-08 11.23.42 /etc/hostsCHMOD ROOT 2003-10-08 11.23.57 /etc/hosts


Figure 130. Example of a RACF SUPERUSER Security Commands - Auditor report



User IDThe ID of the user for whom the operation is recorded.



Class The RACF class used for auditing.

Audit descriptionThe description of the required OpenEdition services.

Event descriptionThe event description.

Access typeType of access. It can be Owner, Group, Other, or None.

Access requestedThe authorization required for OpenEdition service.

Access allowedThe authorization allowed for OpenEdition service.

RACF OpenEdition Resource Accesses ReportSystem: ’ES88’

Date: ’2000-03-01’ to ’2000-03-10’

SuperUser ID user Date Time Class Audit description-------- ----- ---------- -------- -------- --------------------IBMUSER Y 2000-03-09 21.13.00 FSOBJ OPEN A FILE

Y 2000-03-09 21.13.00 FSOBJ OPEN A FILEY 2000-03-09 21.13.00 FSOBJ OPEN A FILEY 2000-03-09 21.13.00 FSOBJ OPEN A FILEN 2000-03-09 21.14.47 DIRACC OPEN A DIRECTORYN 2000-03-09 21.30.35 FSOBJ OPEN A FILEY 2000-03-09 21.30.36 FSOBJ OPEN A FILE

Access Access AccessEvent description type requested allowed-------------------- ------ ---------------- ----------------SUCCESS CHECK FILE NONE EXECUTE EXECUTESUCCESS CHECK FILE NONE READ/WRITE EXECUTESUCCESS CHECK FILE NONE EXECUTE EXECUTESUCCESS CHECK FILE NONE READ/WRITE EXECUTESUCCESS CHECK DIR NONE READ NONESUCCESS CHECK FILE GROUP EXECUTE READ/EXECUTESUCCESS CHECK FILE NONE READ/WRITE EXECUTE

Pathname-------------------------------------------------/bin/fomtlinc/dev/ttyp0000/bin/fomtlinp/dev/ttyp0000./bin/fomtlout/etc/utmpx


Figure 131. Example of a RACF OpenEdition Resource Accesses report


PathnameThe pathname of the resource.

RACF OpenEdition Resource Accesses Failures report:This report shows OpenEdition failures of resource accesses by user.


Report IDRACF10


SourceRACF_OMVS_RES_T

AttributesRACF, Access, OMVS, OpenEdition, Exception



User IDThe ID of the user for whom the operation is recorded.



RACF OpenEdition Resource Accesses Failures ReportSystem: ’ES88’

Date: ’2000-03-01’ to ’2000-03-10’

SuperUser ID user Date Time Class Audit description-------- ----- ---------- -------- -------- --------------------IBMUSER N 2000-03-09 21.14.20 FSOBJ OPEN A FILE

N 2000-03-09 21.17.44 DIRACC RENAME A FILEN 2000-03-09 21.18.01 DIRACC RENAME A FILEN 2000-03-09 21.18.40 DIRACC RENAME A FILE

Access Access AccessEvent description type requested allowed-------------------- ------ ---------------- ----------------INSUFF AUTH GROUP READ/WRITE NONEINSUFF AUTH GROUP WRITE READ/EXECUTEINSUFF AUTH GROUP WRITE READ/EXECUTEINSUFF AUTH GROUP WRITE READ/EXECUTE

Pathname---------------------/.sh_historypgm1pgm2/u/racfid2/who


Figure 132. Example of a RACF OpenEdition Resource Accesses Failures report


Class The RACF class used for auditing.

Audit descriptionThe description of the required OpenEdition services.

Event descriptionThe event description.

Access typeType of access. It can be Owner, Group, Other, or None.

Access requestedThe authorization required for OpenEdition service.

Access allowedThe authorization allowed for OpenEdition service.

PathnameThe pathname of the resource.

RACF Initialization report:This report shows details about the RACF settings at initialization time.


Report IDRACF11


SourceRACF_INIT_T

AttributesRACF, Security, Initialization, Detail



Date The date when the RACF initialization was issued. From TIMESTAMP.

Time The time when the RACF initialization was issued. From TIMESTAMP.

PasswordPassword settings.

IntervalThe maximum password interval. From PWD_INTERVAL.

RACF Initialization ReportSystem: ’MVS1’

Date: ’2004-01-18’ to ’2004-01-30’

---------------- Password ---------------Date Time Interval History Warning Revoke---------- ----- ---------- -------- -------- ---------2005-01-18 17:44:19 30 4 0 4


Figure 133. Example of a RACF Initialization report


HistoryHistory value. From PWD_HISTORY.

WarningNumber of days, before password expiration, during which user receives awarning message. From PWD_WARNING.

RevokeNumber of incorrect logon passwords after which user is revoked. FromPWD_REVOKE.

RACF Class Initialization report:This report shows details about the RACF class settings at initialization time.


Report IDRACF12


SourceRACF_INIT_CLASS_T

AttributesRACF, Security, Class, Initialization, Detail

VariablesFrom_date, To_date, System_ID, Class_name


Date The date when the RACF initialization was issued. From TIMESTAMP.

Time The time when the RACF initialization was issued. From TIMESTAMP.

Class nameThe name of the class. From CLASS_NAME.

Active Indicates if the class is active. From CLASS_OPTIONS.

StatisticsIndicates if the class statistics are in effect. From CLASS_OPTIONS.

RACF Class Initialization ReportSystem: ’MVS1’

Date: ’2005-04-04’ to ’2004-04-30’

Class LogDate Time Name Active Statistics Auditing options---------- -------- --------- -------- ---------- --------- ---------2005-04-04 17:44:19 ACCTNUM Yes No No DEFAULT

ACICSPCT No No No DEFAULTACICSPCT No No No DEFAULTAIMS No No No DEFAULTALCSAUTH No No No DEFAULTAPPCLU No No No DEFAULTAPPCPORT No No No DEFAULTAPPCSI No No No DEFAULT


Figure 134. Example of a RACF Class Initialization report


AuditingIndicates if the auditing is in effect. From CLASS_OPTIONS.

Log optionsLOGOPTIONS value for the class. From CLASS_OPTIONS.

RACF Terminals with Excessive Incorrect Passwords report:This report shows the terminals where logon failed, because incorrect passwordswere entered more times than the maximum allowed in one day.

Use the Max_attempts variable to set the maximum number of valid logonattempts on your system.


Report IDRACF13


SourceRACF_LOGON_T

AttributesRACF, Security, Logon, Terminal, Exceptions

VariablesFrom_date, To_date, System_ID, Max_attempts


Date The date when the failed logon occurred. From TIMESTAMP.

Terminal IDThe terminal ID where incorrect logons were attempted more times thanthe maximum allowed. From TERMINAL_ID.

N.Incorrect PasswordsTotal number of incorrect passwords entered. Calculated as count ofINVALID PASSWORDS events.

RACF Users with Excessive Incorrect Passwords report:This report shows all the users who tried to log on with an incorrect password,more times than the maximum allowed in one day.

RACF Terminals with Excessive Incorrect Passwords ReportSystem: ’MVS1’

Date: ’2005-01-18’ to ’2005-03-18’

Terminal N.IncorrectDate ID passwords---------- -------- ----------2005-03-14 I9PCQ178 32005-03-15 I9PCQ444 32005-03-17 I9PCQ968 3


Figure 135. Example of a RACF Terminals with Excessive Incorrect Passwords report


Use the Max_attempts variable to set the maximum number of valid logonattempts on your system.


Report IDRACF14


SourceRACF_LOGON_T

AttributesRACF, Security, Logon, User, Exceptions

VariablesFrom_date, To_date, System_ID, Max_attempts


Date The date when the failed logon occurred. From TIMESTAMP.

Terminal IDThe identifier of the user who tried to log on with an incorrect passwordmore times than the maximum allowed. From USER_ID.

N.Incorrect PasswordsTotal number of incorrect passwords entered. Calculated as count ofINVALID PASSWORDS events.

RACF All Events for a Specific User report:This report shows all the events that are applicable to a specific user ID.


Report IDRACF15


SourceRACF_LOGON_T, RACF_COMMAND_T, RACF_RESOURCE_T

AttributesRACF, Security, Event, User, All

RACF Users with Excessive Incorrect Passwords ReportSystem: ’MVS1’

Date: ’2005-01-18’ to ’2004-03-18’

User N.IncorrectDate ID passwords---------- -------- ----------2005-03-15 USER01 32005-03-17 USER02 3


Figure 136. Example of a RACF Users with Excessive Incorrect Passwords report


VariablesFrom_date, To_date, System_ID, User_ID


Date The date when the event occurred. From TIMESTAMP.

Time The time when the event occurred. From TIMESTAMP.

Terminal IDThe terminal ID, if available, used by the user. From TERMINAL_ID.

Event Description of the event. From EVENT_DESC.

Result Possible values are SUCCESS and UNSUCCESS. From EVENT_QUAL.

RACF Data Sets with a Specific Name Access report:This report shows all the accesses made to data sets whose names begin with thename specified.


Report IDRACF16


SourceRACF_RESOURCE_T

AttributesRACF, Security, Access, Dataset

VariablesFrom_date, To_date, System_ID, Dataset_prefix

RACF All Events for a Specific User ReportSystem: ’MVS1’

Date: ’2005-04-01’ to ’2005-07-01’User_ID: ’USER01’

TerminalDate Time ID Event Result---------- --------- -------- ----------------- ---------2005-04-01 13:18:01 I9PCQ444 INVALID PASSWORD UNSUCCESS

13:18:03 I9PCQ444 INVALID PASSWORD UNSUCCESS13:47:01 I9PCQ444 SUCCESSFUL ACCESS SUCCESS

*2005-04-02 07:08:22 I9PCQ525 INVALID PASSWORD UNSUCCESS

17:28:33 I9PCQ489 SUCCESSFUL ALU SUCCESS*

2005-04-03 11:14:25 I9PCQ963 FAILED PROTECTALL UNSUCCESS11:14:40 I9PCQ963 FAILED PROTECTALL UNSUCCESS13:17:01 I9PCQ963 FAILED PROTECTALL UNSUCCESS


Figure 137. Example of a RACF All Events for a Specific User report





User IDThe identifier of the user for whom the access to the data set is recorded.From USER_ID.

Data Set NameThe name of the RACF protected data set. From RESOURCE_NAME.

Event Description of the event. From EVENT_DESC.

Result Possible values are SUCCESS and UNSUCCESS. From EVENT_QUAL.

RACF Data Sets with Particular Authority report:This report shows all the resource accesses that were audited because the userassociated with the access had a particular RACF privilege.


Report IDRACF17



AttributesRACF, Security, Access, Resource, Privileges

VariablesFrom_date, To_date, System_ID, Class_name, Resource_name

RACF Data Sets with a Specific Name Access ReportSystem: ’MVS1’

Date: ’2004-04-01’ to ’2004-07-01’Data Set Prefix: ’PR171’

User Data SetDate Time ID Name Event Result---------- -------- -------- ------------------------------- ---------------- ----------2005-04-01 11:14:20 USER01 PR171.ADRLLOAD FAILED PROTECTALL UNSUCCESS2005-04-01 11:17:00 USER01 PR171.SDRLLOAD FAILED PROTECTALL UNSUCCESS2005-04-01 11:18:59 USER01 PR171.MVS.SMF70.LOG FAILED PROTECTALL UNSUCCESS

2005-04-02 17:22:02 USER02 PR171.LOCAL.LOAD SUCCESSFUL ACCESS SUCCESS17:44:56 USER02 PR171.LOCAL.DEFS SUCCESSFUL ACCESS SUCCESS


Figure 138. Example of a RACF Data Sets with a Specific Name Access report





User IDThe identifier of the user for whom the access to the resource is recorded.From USER_ID.

AuthorityAuthority used to access the resource. From AUTHORITY_FLAGS.

Resource NameThe name of the RACF protected resource. From RESOURCE_NAME.

Class NameThe name of the RACF class that protects the resource. From CLASS.

Profile NameThe name of the RACF profile that protects the resource. FromPROFILE_NAME.

RACF Resources Accessed Because Installation Exit report:This report shows all the resource accesses that were granted by an installationexit.


Report IDRACF18



AttributesRACF, Security, Access, Resource, Exit


RACF Resources Accessed with Particular Authority ReportSystem: ’MVS1’

Date: ’2005-02-20’ to ’2005-05-20’

User Resource Class ProfileDate Time ID Authority Name Name Name---------- --------- -------- ---------- --------------------- --------- -----------------2005-02-20 15:47:54 USER03 OPERATIONS TCPIP.SEZAPENU DATASET TCPIP.*

15:47:54 USER03 OPERATIONS TCPIP.SEZAMENU DATASET TCPIP.*18:39:20 USER03 OPERATIONS CATALOG.MVSICF1.VTDS DATASET CATALOG.MVSICF1.V*15:39:44 USER03 OPERATIONS RACFID2.JCL DATASET RACFID2.*


Figure 139. Example of a RACF Data Sets with Particular Authority report





User IDThe identifier of the user for whom the access to the resource is recorded.From USER_ID.




RACF Resources Accessed Because Warning Mode report:This report shows all the resource accesses that were granted because a profile wasin warning mode.


Report IDRACF19



AttributesRACF, Security, Access, Resource, Warning


RACF Resources Accessed Because Installation Exit ReportSystem: ’MVS1’

Date: ’2005-04-01’ to ’2004-07-01’

User Resource Class ProfileDate Time ID Name Name Name---------- --------- -------- ---------------------- --------- --------2005-05-15 15:47:55 USER04 DSN710.LOGCOPY1.DS01 DATASET DSN170.*

15:47:55 USER04 DSN710.LOGCOPY1.DS02 DATASET DSN170.*18:45:09 USER04 DSN710.LOGCOPY1.DS03 DATASET DSN170.*


Figure 140. Example of a RACF Resources Accessed Because Installation Exit report





User IDThe identifier of the user whose access to the resource was audited. FromUSER_ID.




RACF Generic Profiles Used for Resource Access report:This report shows the relationship between the resource names and the genericprofiles that cover them.


Report IDRACF20



AttributesRACF, Security, Access, Resource, Profile


RACF Resources Accessed Because Warning Mode ReportSystem: ’MVS1’

Date: ’2005-04-20’ to ’2004-07-20’

User Resource Class ProfileDate Time ID Name Name Name---------- --------- -------- ------------------------ ------- ---------------2005-04-20 15:47:54 USER04 CPAC.VTAMLST DATASET CPAC.*

15:47:54 USER04 IXGLOGR.SYSPLEX.LOGREC DATASET IXGLOGR.*15:47:54 USER04 TCPIP.SEZAPENU DATASET TCPIP.*


Figure 141. Example of a RACF Resources Accessed Because Warning Mode report







AccessesTotal number of resource accesses, using the indicated profile, in one day.Calculated as count of all resource access events.

RACF Configuration reportsThe reports described in this section are for the RACF Configurationsubcomponent, which provides detailed information about the RACF databasesetup.

RACF Number of Profiles in the Database report:RACF Number of Profiles in the Database report

This report shows the number of RACF profiles (groups, users, data sets, andgeneral resources) in the RACF database.


Report IDRACFC01

Report groupRACF Configuration reports

SourceRACF_GROUPS_D, RACF_USERS_D

AttributesRACF, Security, Configuration, Profile

VariablesDate, System_ID

RACF Generic Profiles Used for Resource Access ReportSystem: ’MVS1’

Date: ’2005-04-01’ to ’2005-07-01’

Resource Class ProfileDate Name Name Name Accesses---------- ------------------------------ -------- ------------------------ --------2005-04-01 CATALOG.MVSICF1.VDB2V7A DATASET CATALOG.MVSICF1.VDB2V7A* 35

CATALOG.MVSICF1.VTDS17A DATASET CATALOG.MVSICF1.VTDS17A* 1CATALOG.MVSICF1.VZOS16P DATASET CATALOG.MVSICF1.VZOS16P* 1SYS1.PARMLIB DATASET SYS1.PARMLIB* 7


Figure 142. Example of a RACF Generic Profiles Used for Resource Access report



Profile TypeThe type of profile. Possible values are GROUP, USER, DATASET,GENRES.

Count The number of profiles in the RACF database. Calculated as count ofentries in each table.

RACF Group List report:This report shows a list of the group profiles defined in the RACF database.


Report IDRACFC02


SourceRACF_GROUPS_D, RACF_USER_CON_D

AttributesRACF, Security, Configuration, Group

VariablesDate, System_ID , Group_Name


Group NameThe name of the group. From GROUP_NAME.

RACF Number of Profiles in the DatabaseDate: ’2005-04-09’ System: ’MVS1’

ProfileType Count---------- --------DATASET 220GENRES 440GROUP 190USEr 125

Tivoli Decision Support for z/OS Report: RACFC01

Figure 143. Example of a RACF Number of Profiles in the Database report

RACF Group ListDate: ’2005-04-09’ System: ’MVS1’

Group Creation MemberName Owner Date Description Count---------- ---------- ----------- ----------- ------SYS1 IBMUSER 1998-12-11 31TCPIP SYS1 2004-02-20 TCP/IP group 2TDS SYS1 2004-12-05 TDS group 10


Figure 144. Example of a RACF Group List report


OwnerThe user ID or group name that owns this group. From OWNER_ID.

Creation DateDate when the group was defined. From CREATE_DATE.

DescriptionInstallation-defined data. From INSTALL_DATA.

Member CountNumber of users connected. Calculated as count of users that have thesame group name.

RACF Users with Particular System Privileges report:This report shows all the user IDs that have particular RACF privileges at systemlevel, such as SPECIAL, OPERATIONS, and AUDITOR.


Report IDRACFC03


SourceRACF_USERS_D

AttributesRACF, Security, Configuration, User, Privileges

VariablesDate, System_ID , User_ID


User IDThe user identifier, as taken from the profile name. From USER_ID.

User NameThe name associated with the user ID. From PROGRAMMER.

PrivilegesThe user privileges. From USER_OPTIONS.

SpecialSPECIAL attribute (Yes or No).

OperationsOPERATIONS attribute (Yes or No).

RACF Users with Particular System PrivilegesDate: ’2005-04-09’ System: ’MVS1’

User User <--------- Privileges --------->ID Name Special Operations Auditor---------- ----------------- --------- ----------- -------User1 User no. 1 Yes No NoUser2 User no. 2 No No NoUser3 User no. 3 No No No


Figure 145. Example of a RACF Users with Particular System Privileges report


AuditorAUDITOR attribute (Yes or No).

RACF Users with Particular Group Level Privileges report:This report shows all the user IDs that have particular RACF privileges at grouplevel, such as SPECIAL, OPERATIONS, and AUDITOR.


Report IDRACFC04


SourceRACF_USER_CON_D, RACF_USERS_D

AttributesRACF, Security, Configuration, User, Privileges

VariablesDate, System_ID , User_ID




Group NameThe name of the group to which the user is connected. FromGROUP_NAME.


SpecialGROUP-SPECIAL attribute (Yes or No).

OperationsGROUP-OPERATIONS attribute (Yes or No).

AuditorGROUP-AUDITOR attribute (Yes or No).

RACF Users Currently Revoked report:

RACF Users with Particular Group Level PrivilegesDate: ’2005-04-09’ System: ’MVS1’

User User Group <-------- Privileges -------->ID Name Name Special Operations Auditor---------- ----------------- --------- -------- ---------- -------User4 User no. 4 GROUP1 Yes No NoUser5 User no. 5 GROUP2 No No YesUser6 User no. 6 No No Yes No


Figure 146. Example of a RACF Users with Particular Group Level Privileges report


This report shows all the user IDs that are currently revoked.


Report IDRACFC05


SourceRACF_USERS_D

AttributesRACF, Security, Configuration, User, Revoked





Last Logon DateThe date when the user last entered the system. From LASTJOB_DATE.

RACF Users Last Defined report:This report shows the user profiles defined as having a threshold date within 90days before the selected date.


Report IDRACFC06


SourceRACF_USERS_D

AttributesRACF, Security, Configuration, User, Last


RACF Users Currently RevokedDate: ’2005-04-09’ System: ’MVS1’

User User Last LogonID Name Date---------- ----------------- ---------User7 User no. 7 1995-01-01ROOT Root user 2005-02-12


Figure 147. Example of a RACF Users Currently Revoked report



Creation DateThe date when the profile was created. From CREATE_DATE.







Last LogonThe last logon of this user ID.

Date The date when the user last logged on the system. FromLASTJOB_DATE.

Term The time when the user last logged on the system. FromLASTJOB_TIME.

RACF Users with NOINTERVAL Specified report:This report shows all the user IDs for which no password interval was specified.


Report IDRACFC07


SourceRACF_USERS_D

AttributesRACF, Security, Configuration, User, Password


RACF Users Last DefinedDate: ’2005-04-09’ System: ’MVS1’

Creation User < Privileges > <--- Last Logon --->Date ID Owner Spec Oper Aud Date Time---------- ------- -------- ---- ---- --- ---------- --------2005-01-17 USER1 RACFID Yes No No 2005-01-01 00:00:002004-12-13 USER2 RACFID No No No 2005-01-01 00:00:002005-01-14 RACFID SYS1 Yes Yes No 2005-01-01 00:00:00


Figure 148. Example of a RACF Users Last Defined report





Creation DateThe date when the profile was created. From CREATE_DATE.





RACF Users with Too Many Group Connections report:This report shows all the user IDs that have more than the maximum number ofvalid group connections. Use the Max_connections variable to set the maximumnumber of valid connections for your system.


Report IDRACFC08


SourceRACF_USERS_CON_D, RACF_USERS_D

AttributesRACF, Security, Configuration, User, Connection

VariablesDate, System_ID, Max_connections

RACF Users with NOINTERVAL SpecifiedDate: ’2005-04-09’ System: ’MVS1’

User Creation <-------- Privileges ------->ID Owner Date Special Operations Auditors

---------- ------- ---------- ------- ---------- --------CBADMIN RACFID 2003-03-20 No No NoIBMUSER IBMUSER 1994-03-05 No No NoWSADMIN SYS1 2002-11-30 No No No


Figure 149. Example of a RACF Users with NOINTERVAL Specified report




User Namethe name associated with the user ID. From PROGRAMMER.

Number of ConnectionsThe number of user-group connections. Calculated as COUNT(*).

RACF Users Members of SYS1 Group report:This report shows all the members belonging to the group SYS1.


Report IDRACFC09


SourceRACF_USER_CON_D, RACF_USERS_D

AttributesRACF, Security, Configuration, User, Connection




RACF Users with Too Many Group ConnectionsDate: ’2005-04-09’ System: ’MVS1’

User User Number ofID Name Connections---------- --------------------- -----------IBMUSER IBMUSER 60RACFID RACF Administrator


Figure 150. Example of a RACF Users with Too Many Group Connections report

RACF Users Members of SYS1 GroupDate: ’2005-11-19’ System: ’ES38’

User < Privileges > Revoke ResumeID Owner Spec Oper Aud Revoked Date Date---------- ------- ---- ---- --- ------- ---------- ----------APPNTM SYS1 No No No No 2000-01-01 2000-05-05APPSWPROC RACFID No No No No 2000-01-01 2000-05-05AUTTCP10 RACFID No No No No 2000-01-01 2000-05-05DSIQTSK SYS1 No No No Yes 2000-01-01 2000-05-05


Figure 151. Example of a RACF Users Members of SYS1 report







RevokedIndicates if the user is revoked (Yes or No). From USER_OPTIONS.

Revoke DateThe date when the user was revoked. From REVOKE_DATE.

Resume DateThe date when the user will be resumed. From RESUME_DATE.

RACF Dataset Profiles for Each HLQ report:This report shows a list of the High Level Qualifiers (HLQ), defined in the RACFdata set profiles, with the highest number of profiles covering them.


Report IDRACFC10


SourceRACF_DATASETS_D

AttributesRACF, Security, Configuration, Dataset, Profiles




HLQ High Level Qualifier (HLQ) extracted from the data set profile name. FromDS_NAME.

Count Number of profiles in the RACF database. Calculated as COUNT(*).

RACF Dataset Profiles with UACC Other than NONE report:This report shows all the data set profiles that have an Universal Access (UACC)other than NONE in the RACF database.


Report IDRACFC11



AttributesRACF, Security, Configuration, Dataset, UACC


RACF Dataset Profiles for Each HLQDate: ’2005-11-19’ System: ’MVS1’

HLQ Count---------- --------ADB 1AHX 1AOP 1BFS 1BSAM 1CANDLE 1CATALOG 48...SYS1 19ZOS15P 1

========220


Figure 152. Example of a RACF Dataset Profiles for Each HLQ report



Dataset Profile NameData set name, as taken from the profile name. From DS_NAME.

VolumeVolume upon which this data set resides. From VOLUME.

GenericIndicates if this is a generic profile. From DATASET_OPTIONS.

OwnerThe user ID or group name that owns this profile. From OWNER_ID.

UACC The universal access of this data set. Possible values are EXECUTE, READ,UPDATE, CONTROL, and ALTER. From UACC.

RACF Dataset Profiles in WARNING Mode report:This report shows all the data set profiles that are in WARNING mode.


Report IDRACFC12



AttributesRACF, Security, Configuration, Dataset, WARNING


RACF Dataset Profiles with UACC Other than NONEDate: ’2005-11-19’ System: ’MVS1’

Dataset ProfileName Volume Generic Owner UACC

------------------------------- ------ ------- -------- -------ADB.* Yes SYS1 ALTERAHX.* Yes SYS1 ALTERANF.* Yes SYS1 READBDT1.* Yes IBMUSER READBFS.* Yes SYS1 ALTERBPA.* Yes RACFID ALTERCANDLE.* Yes SYS1 ALTER...SYS1.VOLCAT.VGENERAL* Yes SYS1 ALTERZOS15.* Yes SYS1 READZOS15A.* Yes IBMUSER READZOS15P.* Yes IBMUSER READ


Figure 153. Example of a RACF Dataset Profiles with UACC Other than NONE report





GenericIndicates if this is a generic profile. From DATASET_OPTIONS.


UACC The universal access of this data set. Possible values are EXECUTE, READ,UPDATE, CONTROL, and ALTER. From UACC.

RACF Dataset Standard ACL with ID(*) Not NONE report:This report shows all the data set profiles whose standard access lists have anasterisk (*) with a level other than NONE.


Report IDRACFC13


SourceRACF_DS_ACCESS_D, RACF_DATASETS_D

AttributesRACF, Security, Configuration, Dataset, Access


RACF Dataset Profiles in WARNING ModeDate: ’2005-01-13’ System: ’MVS1’

Dataset ProfileName Volume Generic Owner UACC

------------------------------- ------ ------- -------- -------CATALOG.MASTER.DRV15P* Yes SYS1 ALTERCATALOG.MASTER.VDRV15Q* Yes SYS1 ALTERCATALOG.MASTER.VM7XSHR* Yes SYS1 READCATALOG.MASTER.VZM7SHR* Yes SYS1 ALTERCATALOG.MVSICFM.VDSK10P* Yes SYS1 UPDATECATALOG.MVSICFM.VDSK28P* Yes SYS1 NONER


Figure 154. Example of a RACF Dataset Profiles in WARNING Mode report






AccessThe access allowed to the user or group. Possible values are EXECUTE,READ, UPDATE, CONTROL, and ALTER. From ACCESS.

RACF Dataset Condit. ACL with ID(*) Not NONE report:This report shows all the data set profiles conditional access lists that have anasterisk (*) with a level other than NONE.


Report IDRACFC14


SourceRACF_DS_CONDACC_D, RACF_DATASETS_D

AttributesRACF, Security, Configuration, Dataset, Access


RACF Dataset Standard ACL with ID(*) Not NONEDate: ’2005-11-19’ System: ’MVS1’

Dataset ProfileName Volume Owner Access

------------------------------- ------ -------- -------NCP.* NCP READNETVIEW.* SYS1 READOMEGA.* SYS1 ALTEROMVS.* SYS1 ALTER


Figure 155. Example of a RACF Dataset Standard ACL with ID(*) Not NONE report

RACF Dataset Condit. ACL with ID(*) Not NONEDate: ’2005-11-19’ System: ’MVS1’

Dataset Profile Access AccessName Volume Owner Access Type Element

------------------------------- ------ -------- ------- -------- -------NPM.* RACFID UPDATE TERMINAL TERM01ZOS15.* RACFID ALTER TERMINAL TERM01


Figure 156. Example of a RACF Dataset Condit. ACL with ID(*) Not NONE report






AccessThe access of the conditional access element/user combination. Possiblevalues are EXECUTE, READ, UPDATE, CONTROL, and ALTER. FromACCESS.

Access TypeThe type of conditional access checking that is being performed. FromCOND_TYPE.

Access ElementThe name of the conditional access element through which the user isgranted access. From COND_ELEMENT.

RACF GR Number of Profiles for Each Class report:This report shows the number of RACF general resource profiles that are logged,for each class, in the RACF database.


Report IDRACFC15


SourceRACF_GENRES_D

AttributesRACF, Security, Configuration, General_Resource

VariablesDate, System_ID, Class_name



Class NameThe name of the class. From CLASS_NAME.

Count Number of profiles. Calculated as count of profiles for each class.

RACF GR Discrete Profiles with Wild Characters report:This report shows all the discrete resource profiles that have wildcard characters (*,%) in their names.


Report IDRACFC16


SourceRACF_GENRES_D

AttributesRACF, Security, Configuration, General_Resource


RACF GR Number of Profiles for Each ClassDate: ’2005-11-19’ System: ’MVS1’

ClassName Count---------- --------ACCTNUM 2CBIND 16CSFSERV 5DASDVOL 27DIGTCERT 17FACILITY 29FIELD 3...TERMINAL 1TSOAUTH 7TSOPROC 27UNIXMAP 73UNIXPRIV 1VTAMAPPL 2


Figure 157. Example of a RACF GR Number of Profiles for Each Class report




Profile NameGeneral resource name, as taken form the profile name. From GR_NAME.

Creation DateDate when the profile was created. From CREATE_DATE.


RACF GR Profiles with UACC Other than NONE report:This report shows all the general resource profiles that have a Universal Access(UACC) other than NONE in the RACF database.


Report IDRACFC17


SourceRACF_GENRES_D

AttributesRACF, Security, Configuration, General_Resource, UACC


RACF GR Discrete Profiles with Wild CharactersDate: ’2005-11-19’ System: ’MVS1’

Class Profile CreationName Name Date Owner---------- -------------------------------------- ---------- ---------PROGRAM * 2000-10-30 RACFIDPROGRAM ** 2000-01-09 RACFID


Figure 158. Example of a RACF GR Discrete Profiles with Wild Characters report




Profile NameGeneral resource name, as taken from the profile name. From GR_NAME.

GenericIndicates if this is a generic profile. From GR_OPTIONS.


UACC The universal access of this resource. Possible values are READ, EXECUTE,UPDATE, CONTROL, and ALTER. For DIGTCERT profiles, valid valuesare TRUST, NOTRUST, and HIGHTRST. From UACC.

RACF GR Profiles in WARNING Mode report:This report shows all the general resource profiles that are in WARNING mode.


Report IDRACFC18


SourceRACF_GENRES_D

AttributesRACF, Security, Configuration, General_resource, WARNING

VariablesDate, System_ID, CLASS_NAME, PROFILE_NAME

RACF GR Profiles with UACC Other than NONEDate: ’2005-03-02’ System: ’MVS1’

Class ProfileName Name Generic Owner UACC------- --------------------------- ------- -------- -------ACCTNUM A0001 No RACFID READ

5 No USER1 READ

CBIND CB.BBO* Yes RACFID READCB.BBOASR1 No RACFID READCB.BBOASR2 No RACFID READCB.BIND.BBO* Yes RACFID READ

...TSOPROC IKJACCNT No RACFID READ

ISPDB2T No PIROSO READISPFDB2 No RACFID READ

UNIXPRIV SUPERUSER.FILESYS.PFSCTL No SYS1 READ


Figure 159. Example of a RACF GR Profiles with UACC Other than NONE report





GenericIndicates if this is a generic profile. From GR_OPTIONS.


UACC The universal access of this data set. Valid values are NONE,READ,EXECUTE, UPDATE, CONTROL, and ALTER. For DIGCERTprofiles, valid values are TRUST, NOTRUST, and HIGHTRST. From UACC.

RACF GR Profiles Standard ACL with ID(*) not NONE report:This report shows all the general resource profiles whose standard access lists havean asterisk (*) with a level other than NONE.


Report IDRACFC19


SourceRACF_GR_ACCESS_D, RACF_GENRES_D

AttributesRACF, Security, Configuration, General_resource, Access

VariablesDate, System_ID, Class_name, Profile_name

RACF GR Profiles in WARNING ModeDate: ’2005-01-22’ System: ’MVS1’

Class ProfileName Name Generic Owner UACC-------- -------------------------------- ------- -------- -------FACILITY $PW.PERMIT_PASSWORD_USAGE No SYS1 READ

AWB.ADMINISTRATION No SYS1 UPDATEAWB.CONFIGURATION No SYS1 UPDATEAWB.OPERATION No SYS1 UPDATEAWB.VIEWER No SYS1 READBPX.DAEMON No RACFID ALTERBPX.DAEMON.HFSCTL No SYS1 UPDATEBPX.FILEATTR.PROGCTL No RACFID UPDATEBPX.FILEATTR.SHARELIB No SYS1 UPDATE


Figure 160. Example of a RACF GR Profiles in WARNING Mode report






AccessThe access allowed to the user or group. Possible values are READ,UPDATE, CONTROL, and ALTER. From ACCESS.

RACF GR Profiles Condit. ACL with ID(*) Not NONE report:This report shows all the general resource profiles whose conditional access listshave an asterisk (*) with a level other than NONE.


Report IDRACFC20


SourceRACF_GR_CONDACC_D, RACF_GENRES_D

AttributesRACF, Security, Configuration, General_Resource, Access

VariablesSystem_ID, Date, Class_Name, Profile_Name

RACF GR Profiles Standard ACL with ID(*) not NONEDate: ’2005-01-22’ System: ’MVS1’

Class ProfileName Name Owner Access-------- -------------------------------- -------- -------SERVER CB.*.BBOASR2 RACFID READ

CB.*.CBDAEMON RACFID READCB.*.CBINTFPR RACFID READCB.*.CBNAMING RACFID READ


Figure 161. Example of a RACF GR Profiles Standard ACL with ID(*) not NONE report






AccessThe access of the conditional access element/user combination. Possiblevalues are EXECUTE, READ, UPDATE, CONTROL, and ALTER. FromACCESS.

Access TypeThe type of conditional access checking that is being performed. FromCOND_TYPE.

Access ElementThe name of the conditional access element through which the user isgranted access. From COND_ELEMENT.

VM accounting componentCustomizationv Making input data availablev Modifying DRLJCOLLv Updating lookup tables

Data flow


Data tablesv Data tables

– VMACCT_SESSION_D, _M

Reportsv VM Accounting Users Grouped by Account Number reportv VM Accounting Users Grouped by CPU Usage reportv VM Accounting Total and Virtual CPU Usage reportv VM Accounting Users Grouped by Group Name reportv VM Accounting Summary Based on Group Name report

RACF Dataset Condit. ACL with ID(*) Not NONEDate: ’2005-11-19’ System: ’MVS1’

Dataset Profile Access AccessName Volume Owner Access Type Element

------------------------------- ------ -------- ------- -------- -------NPM.* RACFID UPDATE TERMINAL TERM01ZOS15.* RACFID ALTER TERMINAL TERM01


Figure 162. Example of a RACF Dataset Condit. ACL with ID(*) Not NONE report


CustomizationBefore you can use the VM accounting component to collect data and create usefulreports, you must customize and test the installation. This chapter describes thesteps you must perform to customize the VM accounting component:1. Making input data available.2. Modifying DRLJCOLL.3. Updating lookup tables.

Making input data availableMake sure the VM accounting component collects accounting data on a daily basis.You must transmit VM accounting data to the z/OS system on which you runTivoli Decision Support for z/OS.

Data in DB2 tables that Tivoli Decision Support for z/OS uses for the VMaccounting component is originally generated by the VM accounting function of az/VM system. VM accounting data includes general resource usage statistics forvirtual machines and the z/VM system. You can use this data for charge back orfor a breakdown of user or user group activity.

Refer to z/VM System Operation for information on generating VM accounting data.Refer to z/VM CP Planning and Administration for complete information on theaccounting data collected by z/VM.

Modifying DRLJCOLLBefore running the Tivoli Decision Support for z/OS collect job, you must updatethe DRLJCOLL member, as described in System Performance Feature Reference VolumeI.

Updating lookup tablesBefore you can create useful reports with the VM accounting component, you mustupdate Tivoli Decision Support for z/OS lookup tables to specify parametersspecific to your installation. The VM accounting component uses the commonlookup table USER_GROUP.

You can use the USER_GROUP lookup table to specify groups for your z/VMusers. For example, all user IDs starting with ENG might belong to the engineeringdepartment, and you might want to make them one group.

For a complete description of this common lookup table and an example of itscontents, refer to the Administration Guide and Reference.


Data flowThe following figure shows an overview of the flow of data from z/VM through tothe Tivoli Decision Support for z/OS reports.


Log and record definitionsVM accounting records are generated by CP to record how virtual machines usesystem resources.

The VM accounting component processes this record:

Figure 163. VM accounting component data flow


Table 12. Table 12. Input records to the VM accounting component

VM accounting record Record definition Description

01 VMACCT_01 A type 01 record is producedwhenever a user logs off orwhenever the ACNT commandis issued.

For complete information on the VM accounting records generated by CP, seez/VM CP Planning and Administration.

Data tablesThis section describes the data tables used by the VM accounting component. Fordescriptions of common data tables, lookup tables, and control tables used by theSystem Performance feature, see the Administration Guide and Reference.

Data tablesThis section describes the data tables specific to the VM accounting component.

VMACCT_SESSION_D, _M:These tables provide daily and monthly statistics on the resources used by users orgroups of users during a z/VM terminal session. They contain data from type 01records created by the accounting function in z/VM.

These tables are updated by the USER_GROUP lookup table.


VMACCT_SESSION_D30 days

VMACCT_SESSION_M765 days


DATE K DATE Date when the sessions were ended. For the _M table,this is the date of the first day of the month. FromACODATE.

VM_SYSTEM_ID K CHAR(8) VM system ID. From the Tivoli Decision Support forz/OS collect job.

ACCOUNT_NUMBER K CHAR(8) VM account number. From ACONUM.

USER_ID K CHAR(8) User ID. From ACOUSER.

USER_GROUP K CHAR(8) Name of the group that the user belongs to. FromGROUP_NAME in the USER_GROUP lookup table; ifno match is found, this column gets its value fromUSER_ID.

For a description of the USER_GROUP lookup table,refer to the Administration Guide and Reference.

CARDS_PUNCHED INTEGER Number of cards spooled to the virtual punch. This isthe sum of ACOPNCH.

CARDS_READ INTEGER Number of cards read from the virtual reader. This isthe sum of ACOCRDS.

CPU_SECONDS FLOAT Processor time used, in seconds. Calculated as thesum of ACOTIME/1000.



IO_COUNT INTEGER Number of virtual machine SIO instructions fornonspooled I/O. This is the sum of ACOIOCT.

LINES_PRINTED INTEGER Number of lines spooled to the virtual printer (thisincludes one line for each carriage control command).This is the sum of ACOLINS.

PAGES_READ INTEGER Number of page reads. This is the sum of ACOPGRD.

PAGES_WRITTEN INTEGER Number of page writes. This is the sum ofACOPGWT.

SESSION_HOURS FLOAT Session time, in hours. This is the number of hoursthe user was connected to the VM system. Calculatedas the sum of ACOCONT/3600.

SESSIONS INTEGER Number of VM logon sessions. This is the count ofaccounting records.

VF_OVERHEAD_SEC FLOAT Vector facility overhead time, in seconds. This is thetotal time spent using the vector facility, includingsupervisor functions, to give service to the virtualmachine. Calculated as the sum of ACOVECTT/1000.

VF_SECONDS FLOAT Vector facility time, in seconds. This is the time thevirtual machine spent using the vector facility to dowork. Calculated as the sum of ACOVECTM/1000.

VIRTUAL_CPU_SEC FLOAT Virtual processor time used, in seconds. Calculated asthe sum of ACOVTIM/1000.

ReportsThe VM accounting component provides these reports:v VM Accounting Users Grouped by Account Number reportv VM Accounting Users Grouped by CPU Usage reportv VM Accounting Total and Virtual CPU Usage reportv VM Accounting Users Grouped by Group Name reportv VM Accounting Summary Based on Group Name report

VM Accounting Users Grouped by Account Number reportThis report shows a summary of resources used by each user on the system for themonths you specify.


Report IDVMACCT01

Report groupVM accounting reports

SourceVMACCT_SESSION_M

AttributesVM, Accounting, Service, CPU, Overview, Monthly

VariablesFrom_month, To_month, VM_system_ID, User_ID, Account_number,User_group



MonthThe date of the first day of the month of the measurement.

Account numberThe VM account number.

User IDThe user ID.

SessionsThe number of VM logon sessions. This is the count of accounting records.VM creates a record when a user logs off the system and for every userlogged on when the operator issues the ACNT command.

Session hoursThe session time, in hours. This is the number of hours the user wasconnected to the VM system.

CPU hoursThe processor time used, in hours. Calculated as: CPU_SECONDS / 3600.

Virtual CPU hoursThe virtual processor time used, in hours. Calculated as:VIRTUAL_CPU_SEC / 3600.

I/O countThe number of virtual machine SIO instructions for nonspooled I/O.

Cards punchedThe number of cards spooled to the virtual punch.

Cards readThe number of cards read from the virtual reader.

Lines printedThe number of lines spooled to the virtual printer. This includes one linefor each carriage control command.

VM Accounting Users Grouped by Account NumberSystem: ’XYZVM ’ User group: CMSUSERS

Month: ’2000-05-01’ to ’2000-05-01’

VirtualAccount User Session CPU CPU I/O Cards Cards Lines

Month number ID Sessions hours hours hours count punched read printed---------- -------- -------- -------- --------- ---------- ---------- ---------- ---------- ----------- -----------2000-05-01 913SYST MMSERV 60 1.9 0.0 0.0 3 480 0 0

CROSSCAL 30 1.0 0.0 0.0 0 0 0 0DISKACNT 30 1.5 0.0 0.0 52 200 0 0 0LOGGAR 30 4.3 1.2 1.1 357 510 0 7 238 760 1 950RACFMAP 30 1.5 0.0 0.0 570 0 0 210RACFSMF 30 0.2 0.1 0.0 27 240 160 200 0 0

-------- --------- ---------- ---------- ---------- ---------- ----------- -----------* 210 10.4 1.3 1.1 441 000 160 200 7 238 760

-------- --------- ---------- ---------- ----------- --------- ----------- -----------** 210 10.4 1.3 1.1 441 000 160 200 7 238

======== ========= ========== ========== =========== ========= =========== ===========210 10.4 1.3 1.1 441 000 160 200 7 238 760 2 160

Tivoli Decision Support for z/OS report: VMACCT01

Figure 164. Example of a VM Accounting Users Grouped by Account Number report


VM Accounting Users Grouped by CPU Usage reportThis report shows the users that put the most load on the system for the specifiedmonths. The report is sorted on CPU hours used.


Report IDVMACCT02



AttributesVM, Accounting, Service, CPU

VariablesFrom_month, To_month, VM_system_ID



User IDThe user ID.



VM Accounting Users Grouped by CPU UsageMonth: ’2000-04-01’ to ’2000-04-01’

System: ’XYZVM ’

VirtualUser CPU CPU Session

Month ID hours hours Sessions hours---------- -------- ---------- ---------- -------- ----------2000-04-01 TREFAS2 9.7 9.0 4 96.0

LX33590 5.9 3.3 2 19.4SYSTEM 4.9 0.0 24 96.0VTAM 3.4 1.7 4 96.0SNAP 2.4 2.1 7 96.0BARSUB4 2.3 2.1 9 95.7RACFMAP 2.1 2.1 13 100.2ZIBMPC 2.1 0.9 4 96.0BARSUB3 2.1 1.8 9 95.7BARSUB6 2.0 1.8 14 56.5BARSUB5 2.0 1.7 9 95.7RSCS 1.6 0.8 5 96.0ZANSLMAC 1.5 1.4 8 95.7ARIASRDR 1.2 1.2 8 86.3

Tivoli Decision Support for z/OS report: VMACCT02

Figure 165. Example of a VM Accounting Users Grouped by CPU Usage report




VM Accounting Total and Virtual CPU Usage reportThis report shows total and virtual CPU usage for the specified days.


Report IDVMACCT03


SourceVMACCT_SESSION_D

AttributesVM, Accounting, Service, CPU, Trend

VariablesFrom_date, To_date, VM_system_ID




Total CPU hoursThe total processor time used, in hours. Calculated as:SUM(CPU_SECONDS) / 3600.

Virtual CPU hoursThe virtual processor time used, in hours. Calculated as:SUM(VIRTUAL_CPU_SEC) / 3600.

VM Accounting Users Grouped by Group Name reportThis report shows a summary of resources used by each user on the system for thespecified months.


Report IDVMACCT04



Figure 166. Example of a VM Accounting Total and Virtual CPU Usage report


AttributesVM, Accounting, Service, CPU, Overview, Monthly




User groupThe group name from the USER_GROUP lookup table.

User IDThe user ID.




VM Accounting Users Grouped by Group NameMonth: ’2000-05-01’ to ’2000-05-01’

System: ’XYZVM ’

VirtualUser User Session CPU CPU I/O Cards Cards Lines

Month group ID Sessions hours hours hours count punched read printed---------- -------- -------- -------- ---------- ---------- ---------- ----------- ----------- ----------- ----------2000-05-01 VMGROUP1 AMMSERV 60 1.9 0.0 0.0 3 480 0 0

ASKTCMD 1 0.3 0.0 0.0 221 0 0 0CROSSCAL 30 1.0 0.0 0.0 0 0 0 0

-------- ---------- ---------- ---------- ----------- ----------- ----------- ----------* 91 3.2 0.0 0.0 3 701 0 0

VMGROUP2 DISKACNT 30 1.5 0.0 0.0 52 200 0 0 0-------- ---------- ---------- ---------- ----------- ----------- ----------- ----------

* 30 1.5 0.0 0.0 52 200 0 0

VMGROUP3 SQLCEA02 1 0.3 0.0 0.0 64 0 0 0-------- ---------- ---------- ---------- ----------- ----------- ----------- ----------

* 1 0.3 0.0 0.0 64 0 0

VMGROUP4 ZCPANAMN 1 0.0 0.0 0.0 0 0 0 0ZEARSRV 1 0.0 0.0 0.0 96 0 0 2ZIDCDSLC 2 0.0 0.0 0.0 308 0 0 0ZRMSMAC 1 0.3 0.0 0.0 108 0 0 0

-------- ---------- ---------- ---------- ----------- ----------- ----------- ----------* 5 0.3 0.0 0.0 512 0 0

-------- ---------- ---------- ---------- ----------- ----------- ----------- ----------** 127 5.3 0.0 0.0 56 477 0

======== ========== ========== ========== =========== =========== =========== ==========127 5.3 0.0 0.0 56 477 0 0 2

Tivoli Decision Support for z/OS report VMACCT04

Figure 167. Example of a VM Accounting Users Grouped by Group Name report



I/O countThe number of virtual machine SIO instructions for nonspooled I/O.

Cards punchedThe number of cards spooled to the virtual punch.

Cards readThe number of cards read from the virtual reader.

Lines printedThe number of lines spooled to the virtual printer. This includes one linefor each carriage control command.

VM Accounting Summary Based on Group Name reportThis report shows a summary of CPU hours and virtual CPU hours grouped bygroup name for the specified months.


Report IDVMACCT05



AttributesVM, Accounting, Service, EXCP, Monthly




User groupThe group name, as defined in the USER_GROUP lookup table.

CPU hoursThe processor time used, in hours. Calculated as: SUM(CPU_SECONDS) /3600.

Virtual CPU hoursThe virtual processor time used, in hours. Calculated as:SUM(VIRTUAL_CPU_SEC) / 3600.

z/VM Performance componentCustomizationv Making input data availablev Modifying DRLJCOLLv Updating lookup tables

Data flow


Figure 168. Example of a VM Accounting Summary Based on Group Name report


Data tables, views, and lookup tablesv Mapping between VMPRF and z/VM Performance Toolkit summary recordsv Data tables

– VMPRF_CONFIG_T– VMPRF_DASD_H, _D, _M– VMPRF_LPARS_H, _D, _M– VMPRF_PROCESSOR_H, _D, _M– VMPRF_SYSTEM_H, _D, _M– VMPRF_USER_H, _D, _M

v Views– VMPRF_LPARS_HV,_DV,_MV

v Lookup tables– VMPRF_MIPS_CPU– VMPRF_TIMEZONES

Reportsv System reports

– z/VM System Processor Usage, Hourly report– z/VM System Busy Distribution, Hourly report– z/VM System Page and Spool Counts, Hourly report– z/VM System Exp Stor and Paging Activity, Hourly report– z/VM System Instruction Rate, Hourly report– z/VM System Instruction Counts, Hourly report– z/VM System MIPS Capacity by LPAR, Daily report

v Processor reports– z/VM Processor Usage Distribution, Hourly report– z/VM Processor Busy Distribution, Hourly report– z/VM Processor Page and Spool Activity, Hourly report– z/VM Processor Storage Activity, Hourly report– z/VM Processor Instruction Rate, Hourly report– z/VM Processor Instruction Counts, Hourly report

v User reports– z/VM User Real and Virt Processor Usage, Monthly report– z/VM User Paging and Spooling, Monthly report– z/VM User IUCV and VMCF Counts, Monthly report– z/VM Heaviest Users of the Processor, Monthly report– z/VM Heaviest Users of DASD, Monthly report– z/VM Heaviest Users of Paging, Monthly report– z/VM Processor Usage by User Class, Monthly report– z/VM Paging by User Class, Monthly report– z/VM IUCV and VMCF Usage by User Class, Monthly report

v DASD reports– z/VM Most-Used DASD by Start Subchannel Rate report– z/VM Slowest DASD by Response Time report– z/VM DASD With Longest Queues report


– z/VM Least Used or not Used DASD Devices report– z/VM Least Used DASD Devices report

v Configuration reports– z/VM Configuration, Level and Storage, Daily report– z/VM Configuration, Level and IPL, Daily report

CustomizationBefore you can use the z/VM Performance component to collect data and createreports, you must customize and test the installation. This chapter describes thesteps you must perform to customize the z/VM Performance component:1. Making input data available.2. Modifying DRLJCOLL.3. Updating lookup tables.

Making input data availableData in DB2 tables that Tivoli Decision Support for z/OS uses for the z/VMPerformance component is originally generated by the VMPRF licensed program orby the z/VM Performance Toolkit. Use VMPRF summary records to collectperformance data on z/VM systems up to version 4.4, use z/VM PerformanceToolkit extended summary records to collect performance data on z/VM systemsversion 5.1, or later.

z/VM Performance Toolkit and VMPRF generate data by analyzing VM monitordata. z/VM Performance Toolkit and VMPRF record many types of monitor data,including virtual machine processor usage and response times, system performancecharacteristics, and system configuration. You can use this data for response-timeanalysis or for a breakdown of user or user group activity.

Note:

Although z/VM Performance Toolkit and VMPRF use the same source to gatherperformance data, they do not necessarily apply the same sets of calculations. Fordetails on the calculations used, refer to the documentation of the specific product.For a mapping between the fields in VMPRF and z/VM Toolkit summary records,refer to

Mapping between VMPRF and z/VM Performance Toolkit summary records

.

To make the data available to Tivoli Decision Support for z/OS, collect monitordata and analyze it with z/VM Performance Toolkit or VMPRF, creating thesummary file. Transmit this summary file to the z/VM system from which you runTivoli Decision Support for z/OS.

These steps describe where the data originates and how it becomes available toTivoli Decision Support for z/OS:1. The VM monitor, which is part of the z/VM operating system, creates monitor

records in a DCSS in central storage.2. The utility program MONWRITE moves the data from the DCSS to tape or,

more commonly, DASD.3. VMPRF and z/VM Performance Toolkit read the monitor data from tape or

DASD and creates summary files.


4. The administrator transfers the summary files from z/VM to the z/OS systemrunning Tivoli Decision Support for z/OS.

5. The collect step reads the summary files and stores the data in the TivoliDecision Support for z/OS database.

See the z/VM Performance Reporting Facility and z/VM Performance Toolkit manualsfor complete information on using VMPRF and z/VM Performance Toolkit, andcreating the summary file used by Tivoli Decision Support for z/OS.

Modifying DRLJCOLLBefore running the collect job, you must update the DRLJCOLL member, asdescribed in "Setting up the collect job" in the System Performance Feature ReferenceVolume I.

Updating lookup tablesThe z/VM Performance component uses the DAY_OF_WEEK and PERIOD_PLANcontrol tables when updating data tables. The component also uses theUSER_GROUP common lookup table. Ensure that these tables specify the days,periods, and user groups you want to report on. For descriptions of these tablesand examples of their contents, see the Administration Guide and Reference.

When collecting logs from the z/VM Performance Toolkit only, the z/VMPerformance component uses the VMPRF_MIPS_CPU and VMPRF_TIMEZONESlookup tables. Ensure that:v The VMPRF_MIPS_CPU table contains the CPU serial number and the

corresponding MIPS. This information will be used when the VMPRF_LPARS_Htable is loaded. For a description of the VMPRF_MIPS_CPU lookup table, seeVMPRF_MIPS_CPU.

v The VMPRF_TIMEZONES table contains the offset, in hours, corresponding tothe timezone of the VM system identifier for which you are collecting data. Thisinformation ensures that data is loaded to the database at the local time of themeasurement, rather than the GMT time. For a description of theVMPRF_TIMEZONES lookup table, see VMPRF_TIMEZONES.

For information about how to use the administration dialog to update lookuptables, see System Performance Feature Reference Volume I.

Data flowThe following figure shows an overview of the flow of data from VM monitor datathrough to the Tivoli Decision Support for z/OS reports.


Note:

The z/VM Performance component uses the DAY_OF_WEEK and PERIOD_PLANcontrol tables when updating all data tables except VMPRF_CONFIG_T. Thecomponent also uses the USER_GROUP common lookup table when updating theVMPRF_USER_x data tables.

Log and record definitionsThe z/VM Performance component includes two log definitions:

VMPRF logsCreated by the VM Performance Reporting Facility (VMPRF). These logfiles are to be used for summary records on z/VM systems up to Version4.4.

VMPERFT logsCreated by the z/VM Performance Toolkit. These log files are to be usedfor extended summary records on z/VM systems version 5.1, or later.

Figure 169. z/VM Performance component data flow


The z/VM Performance component processes the records listed in the following 2tables.

Table 13. Input records to the z/VM Performance component from VMPRF

VMPRF record type Record definition Description

01 (SYSTEM) VMPRF_01 Contains all VM systemperformance data from recordtype 01 records in the VMPRFsummary file.

02 (PROCESSOR) VMPRF_02 Contains all VM processorperformance data from recordtype 02 records in the VMPRFsummary file.

11 (CONFIGURATION) VMPRF_11 Contains all VM systemconfiguration data from recordtype 11 records in the VMPRFsummary file.

41 (USER) VMPRF_41 Contains all VM user datafrom record type 41 records inthe VMPRF summary file.

61 (DASD) VMPRF_61 Contains all DASD data forVM processors and for anyDASD used by VM and othersystems in a shared DASDconfiguration from record type61 records in the VMPRFsummary file.

Table 14. Input records to the z/VM Performance component from z/VM Performance Toolkit

z/VM Performance Toolkit record type Record definition Description

X'FC00' VMPERFT_00 System configuration data.

X'FC01' VMPERFT_01 General system load data.

X'FC02' VMPERFT_02 Processor load data.

X'FC03' VMPERFT_03 Logical processor load data(LPAR only).

X'FC04' VMPERFT_04 Minidisk cache data.

X'FC05' VMPERFT_05 CP services activity data.

X'FC06' VMPERFT_06 Channel busy (HF sampling).

X'FC07' VMPERFT_07 Channel measurement facilitydata.

X'FC08' VMPERFT_08 Extended channelmeasurement facility data.

X'FC3A' VMPERFT_3A Overall user transaction data.

X'FC3C' VMPERFT_3C Shared segments data.

X'FC3E' VMPERFT_3E Shared data spaces.

X'FC41' VMPERFT_41 User resource usage and waitstates.

X'FC42' VMPERFT_42 User class resource usage andwait states (same layout asFC41).


Table 14. Input records to the z/VM Performance component from z/VM Performance Toolkit (continued)

z/VM Performance Toolkit record type Record definition Description

X'FC43' VMPERFT_43 System totals for user resourceusage and wait states (samelayout as FC41).

X'FC44' VMPERFT_44 User transactions and responsetime.

X'FC45' VMPERFT_45 User class transactions andresponse time data (samelayout as FC44).

X'FC46' VMPERFT_46 System totals for usertransactions and response timedata.

X'FC51' VMPERFT_51 I/O processor activity data.

X'FC55' VMPERFT_55 Virtual switch record.

X'FC61' VMPERFT_61 General DASD data.

X'FC65' VMPERFT_65 DASD cache data .

X'FC68' VMPERFT_68 DASD CP owned (systemareas).

X'FC6D' VMPERFT_6D Queued Direct Input Output(QDIO) support.

X'FC6F' VMPERFT_6F SCSI records.

X'FC71' VMPERFT_71 DASD SEEKS data.

X'FCA2' VMPERFT_A2 SFS and BFS server data.

X'FCA4' VMPERFT_A4 Multitasking users data.

X'FCA6' VMPERFT_A6 TCP/IP server data.

X'FCA7' VMPERFT_A7 TCP/IP links data.

X'FCA8' VMPERFT_A8 Reusable server kernelsummary data.

X'FCA9' VMPERFT_A9 Linux application data.

For complete information on the data generated by the z/VM Performance Toolkit,see the z/VM Performance Toolkit manual.

Data tables, views, and lookup tablesThis chapter describes the data tables, views, and lookup tables used by the z/VMPerformance component. For descriptions of common data tables, lookup tables,and control tables used by the System Performance feature, see the AdministrationGuide and Reference.

This chapter also includes some tables that show the mapping between VMPRFand z/VM Toolkit summary records.

Mapping between VMPRF and z/VM Performance Toolkitsummary recordsUse VMPRF summary records to collect performance data on z/VM systems up toVersion 4.4, and use z/VM Performance Toolkit summary records to collectperformance data on z/VM systems version 5.1, or later.


If you upgrade your z/VM system to Version 5.1, you do not need to modify yourTivoli Decision Support for z/OS reports because the old data tables are stillsupported. You only have to move from VMPRF summary records to z/VMPerformance Toolkit extended summary records.

For a mapping between the fields in VMPRF and z/VM Toolkit extended summaryrecords, see the following tables.

Table 15. Mapping between the fields in VMPRF summary record 11 and the fields in z/VM Performance Toolkitsummary records X’FC00’ and X’FC01’

Fields in VMPRF summary record 11

Fields in z/VMPerformanceToolkit summaryrecord X’FC00’

Fields in z/VM PerformanceToolkit summary recordX’FC01’

Date SUMRTOD SUMRTOD

Time SUMRTOD SUMRTOD

System ID SUMRSYID SUMRSYID

System serial number SUMRCSER

Installed xstore H01XSTOR

Non-pageable frames H01NPAG

Offline frames H01MNOFF

Pageable frames H01PGBL

Last abend code H00TRMCD

Real storage size H01MNSTO

Sysgen storage size H01MNGEN

Time of the last IPL H00IPLTD

Time of the last termination H00TRMTD

System release H00VERSN (bytes0-1)

System service level H00VERSN (bytes4-7)

System version H00VERSN (bytes2-3)

V=R free H01VRFRE

V=R size H01VRSIZ








Elapsed time SUMRELT


Machine type SUMRCMDL


Table 16. Mapping between the fields in VMPRF summary record 01 and the fields in z/VM Performance Toolkitsummary records X’FC01’ and X’FC02’ (continued)




Processor online time (D0R2) SUMRELT SUMRELT

Processor wait time H02WAIT

Processor emulation time H02EMTIM

Processor user time H02USTIM

Processor system time H02SYTIM

Vector time H02VFTIM

Vector switching time H02VOTIM

Page reads H02PGRDS

Page writes H02PGWRT

Spool reads H02SPRDS

Spool writes H02SPWRT

SSCHs H01DSSSC

RSCHs H02RSCH

CSCHs H02CSCH

HSCHs H02HSCH

DIAG instructions H02DIACT

Simulated instructions H02PRVCT

External interrupts H02EXTIT

SIGP interrupts H02SIGCT

Fastpath PGINs H02FPGIN

Non-Fastpath PGINs H02FPGINS

PGOUTs H02PGOUT

Interval count (D0R8) SUMRSMP

Logged users H01RSLOG

Dormant users H01RSDOR

Note: An X'FC02'summary record exists for each processor in the system. To obtain the value that applies to thewhole system, calculate the sum of all the X'FC02'summary records.

Table 17. Mapping between the fields in VMPRF summary record 02 and the fields in z/VM Performance Toolkitsummary record X’FC02’


Fields in z/VMPerformance Toolkitsummary record X’FC02’

Date SUMRTOD

Time SUMRTOD



System ID SUMRSYID


Table 17. Mapping between the fields in VMPRF summary record 02 and the fields in z/VM Performance Toolkitsummary record X’FC02’ (continued)



CPU address H02PRCID

Machine type SUMRCMDL

Processor online time (D0R2) SUMRELT

Processor wait time H02WAIT

Processor emulation time H02EMTIM

Processor user time H02USTIM

Processor system time H02SYTIM

Vector time H02VFTIM

Vector switching time H02VOTIM

Page reads H02PGRDS

Page writes H02PGWRT

Spool reads H02SPRDS

Spool writes H02SPWRT

SSCHs H02SSCH

RSCHs H02RSCH

CSCHs H02CSCH

HSCHs H02HSCH

DIAG instructions H02DIACT

Simulated instructions H02PRVCT

External interrupts H02EXTIT

SIGP interrupts H02SIGCT

Fastpath PGINs H02FPGIN

Non-Fastpath PGINs H02PGINS

PGOUTs H02PGOUT








User ID H41USER H44USER

Active time H41TIMAC

Connected time H41TIMLG

User logged time (D4R3) SUMRELT

Total CPU time H41TCPU


Table 18. Mapping between the fields in VMPRF summary record 41 and the fields in z/VM Performance Toolkitsummary records X’FC41’ and X’FC44’ (continued)




Virtual CPU time H41VCPU

Vector time H41VVEC

DASD I/Os H41IODSD

Console I/Os H41IOCON

Unit record I/Os H41IOUR

CTC I/Os H41IOCTC

Other I/Os H41IOOTH

User logged time (D4R4) SUMRELT

Page read I/Os H41PGRD

Page write I/Os H41PGWRT

Pages read into main storage H41XTOMN

Pages written to XSTORE H41MNTOX

Spool read I/Os H44SPRDS

Spool write I/Os H44SPWRT

IUCV data transfers to user H41IURCV

IUCV fails H41IUFAI

IUCV data transfers by user H41IUSND

IUCV send queue H41IUSNQ

VMCF data transfers to user H41VMRCV

VMCF fails H41VMFAI

VMCF data transfers by user H41VMSND




Date SUMRTOD

Time SUMRTOD


System ID SUMRSYID

DASD number H61DEVNO

Device online time SUMRELT

Volser H61VLSER

SSCHs and RSCHs H61SSCH

Connect time H61CONT

Pending time H61FPNT

Disconnect time H61DSCT


Table 19. Mapping between the fields in VMPRF summary record 61 and the fields in z/VM Performance Toolkitsummary record X’FC61’ (continued)



SCM count H61SAMCT or H61SSCH

HF samples H61HFCNT

Queued SSCH H61HFQUD




Date SUMRTOD

Time SUMRTOD



System ID SUMRSYID

Dispatch interval H03DSPIN

Physical processor H03NRPRC


Logical partition name H03NAME

LPAR number H03LPRNR

Data flag H03FLAG

Number of logical processors H03NRLPR

Weight H03WGHT

Wait complete flag H03WFLAG

Total dispatch time H0ACTM

Data tablesThis section describes the data tables for the z/VM Performance component.

The data tables are loaded from the VM Performance Reporting Facility (VMPRF)for summary records coming from z/VM system up to Version 4.4 , and from thez/VM Performance Toolkit for extended summary records coming from z/VMsystems Version 5.1, and later.

Note: The VMPRF_LPARS_H,_D,_M tables are loaded from the z/VMPerformance Toolkit only.

VMPRF_CONFIG_T:This table provides detailed information about the configuration of VM systems. Itcontains data from record type 11 (created by the VM Performance ReportingFacility), or from record types X'FC00'and X'FC01' (created by the z/VMPerformance Toolkit).




DATE K DATE Date when the data about the VM system wascreated. From DATE.

TIME K TIME Time when the data about the VM system wascreated. From TIME.

VM_SYSTEM_ID K CHAR(8) System identifier. From the SYSTEMID parameterspecified in the SETTINGS file or on the VMPRFcommand line. From SUMRSYID in the z/VMPerformance Toolkit record.

CPU_ID CHAR(6) Serial number. This is the system serial numberwithout a processor identifier as the first character.From SYSTEM_SERIAL_NBR in VMPRF record orfrom SUMRCSER in the z/VM Performance Toolkitrecord.

ESTOR_INSTALLED FLOAT Number of expanded storage blocks installed. FromINSTALLED_XSTORE in VMPRF record or fromH01XSTOR in the z/VM Performance Toolkit record.

FRAMES_NONPAGEABLE FLOAT Number of non-pageable frames. This is thenon-pageable storage. From NON_PAGEABLE_FRMin VMPRF record or from H01NPAG in the z/VMPerformance Toolkit record.

FRAMES_OFFLINE FLOAT Number of offline frames. This is the offline storage.From OFFLINE_FRAMES in VMPRF record or fromH01MNOFF in the z/VM Performance Toolkit record.

FRAMES_PAGEABLE FLOAT Number of pageable frames. This is the pageablestorage. From PAGEABLE_FRAMES in VMPRF recordor from H01PGBL in the z/VM Performance Toolkitrecord.

LAST_ABEND_CODE CHAR(8) Abend code of the last termination. FromLAST_ABEND_CODE in VMPRF record or fromH00TRMCD in the z/VM Performance Toolkit record.

STORAGE_REAL FLOAT Size of real storage calculated during systeminitialization, in bytes. From REAL_STORAGE_SIZEin VMPRF record or from H01MNSTO in the z/VMPerformance Toolkit record.

STORAGE_SYSGEN FLOAT Storage size of the real machine as defined duringSYSGEN, in bytes. From SYSGEN_STORAGE_SIZ inVMPRF record or from H01MNGEN in the z/VMPerformance Toolkit record.

TIME_OF_LAST_IPL FLOAT Time of the last IPL that was performed since January1, 1900, 00:00 GMT, in seconds. FromTIME_OF_LAST_IPL in VMPRF record or fromH00IPLTD in the z/VM Performance Toolkit record.

TIME_OF_LAST_TERM FLOAT Time of the last termination that occurred sinceJanuary 1, 1900, 00:00 GMT, in seconds. FromTIME_OF_LAST_TERM in VMPRF record or fromH00TRMTD in the z/VM Performance Toolkit record.

VM_RELEASE CHAR(2) Operating system release number. FromSYSTEM_RELEASE in VMPRF record or fromH01VERSN in the z/VM Performance Toolkit record.

VM_SERVICE_LEVEL CHAR(4) Operating system service level. FromSYSTEM_SERVICE_LVL in VMPRF record or fromH01VERSN in the z/VM Performance Toolkit record.



VM_VERSION CHAR(2) Operating system version. From SYSTEM_VERSIONin VMPRF record or from H01VERSN in the z/VMPerformance Toolkit record.

VR_FREE FLOAT Virtual-equals-real (V=R) reserved free storage, inbytes. From VR_FREE in VMPRF record or fromH01VRFRE in the z/VM Performance Toolkit record.

VR_SIZE FLOAT Size of the virtual-equals-real (V=R) area excludingV=R reserved free storage, in bytes. This is set to thelargest V=R or V=F address. From VR_SIZE inVMPRF record or from H01VRSIZ in the z/VMPerformance Toolkit record.

VMPRF_DASD_H, _D, _M:These tables provide hourly, daily, and monthly statistics on DASD activity on VMsystems. They contain DASD data from record type 61 (created by the VMPerformance Reporting Facility) or from record type X'FC61' (created by the z/VMPerformance Toolkit).


VMPRF_DASD_H10 days

VMPRF_DASD_D30 days

VMPRF_DASD_M765 days


DATE K DATE Date when the data about the VM system wascreated. For the _M table, this is the date of the firstday of the month. From DATE.

PERIOD_NAME K CHAR(8) Name of the period. This is derived using fieldsSYSTEM_ID, DATE, and TIME from the record asparameters in the PERIOD function.

TIME K TIME Time (rounded down to the nearest hour) when thedata about the VM system was created. It applies onlyto the _H table. From TIME.

VM_SYSTEM_ID K CHAR(8) VM system ID. From the SYSTEMID parameterspecified in the SETTINGS file or on the VMPRFcommand line. From H01VRSYID in the z/VMPerformance Toolkit record.

DEVICE_NUMBER K CHAR(4) DASD device number. From DEVICE_NUMBER inVMPRF record or from H61DEVNO in the z/VMPerformance Toolkit record.

VOLSER K CHAR(6) Volume serial number. From VOLSER_NUMBER inVMPRF record or from H61VLSER in the z/VMPerformance Toolkit record.



BUSY_PCT FLOAT Percentage of elapsed time that the device was busy.Calculated as ((PENDING_TIME +DISCONNECT_TIME + CONNECT_TIME)/DEVICE_ONLINE_TIME)*100 from VMPRF record.Calculated as ((H61FPNT + H61DSCT +H61CONT)/(SUMRELT)*100 from z/VM PerformanceToolkit record.

CONNECT_SEC FLOAT Device connect time, in seconds. This is the time thatthe device was logically connected to the channel pathto transfer information between it and the channelsubsystem. This is the sum of CONNECT_TIME inVMPRF record, or the sum of H61CONT in the z/VMPerformance Toolkit record.

CONNECT_MSEC FLOAT Average device connect time, in milliseconds. This isthe time that the device was logically connected to thechannel path to transfer information between it andthe channel subsystem. Calculated as(CONNECT_TIME/SCM_UPDATES)*1000 fromVMPRF record. Calculated as (H61CONT/H61SSCH)*1000 from the z/VM Performance Toolkitrecord.

DEVICE_IO_RATE FLOAT Number of SSCH and RSCH instructions executed persecond for the device while it was online. Calculatedas SSCH_RSCH/DEVICE_ONLINE_TIME from theVMPRF record, or as H61SSCH/SUMRELT from thez/VM Performance Toolkit record.

DEVICE_QUEUE FLOAT Average number of start subchannel requests queuedfor the device, excluding the active requests.Calculated as SSCH_QUEUED/HF_SAMPLES fromthe VMPRF record, or as H61HFQUD/H61HFCNTfrom the z/VM Performance Toolkit record.

DISCONN_MSEC FLOAT Average device disconnect time, in milliseconds. Thisis the time that the device was logically disconnectedfrom the channel subsystem while the subchannel wasactive. Calculated as (DISCONNECT_TIME/SCM_UPDATES)*1000 from the VMPRF record, or asH61DSCT/H61SSCH)*1000 from the z/VMPerformance Toolkit record.

DISCONN_SEC FLOAT Device disconnect time, in seconds. This is the timethat the device was logically disconnected from thechannel subsystem while the subchannel was active.This is the sum of DISCONNECT_TIME from theVMPRF record, or the sum of H61DSCT from thez/VM Performance Toolkit record.

ELAPSED_SEC FLOAT Elapsed time that monitoring was turned on, inseconds. From ELAPSED_TIME in the VMPRF recordor from SUMRELT in the z/VM Performance Toolkitrecord.

HF_SAMPLES FLOAT Number of high-frequency samples. FromHF_SAMPLES in the VMPRF record or fromH61HFCNT in the z/VM Performance Toolkit record.

ONLINE_SEC FLOAT Elapsed time that the device was online, This is thesum of ONLINE_TIME_D6R3 from the VMPRFrecord, or the sum of SUMRELT from the z/VMPerformance Toolkit record.



PENDING_MSEC FLOAT Average device function pending time, inmilliseconds. This can be caused by another systemusing the device in a shared environment. Calculatedas (PENDING_TIME/SCM_UPDATES)*1000 from theVMPRF record, or as H61FPNT/H61SSCH)*1000 fromthe z/VM Performance Toolkit record.

PENDING_SEC FLOAT Device function pending time, in seconds. This can becaused by another system using the device in ashared environment. This is the sum ofPENDING_TIME from the VMPRF record, or the sumof H61FPNT in the z/VM Performance Toolkit record.

RECORDS_COLLECTED FLOAT Number of records collected. This is the count ofrecords with a valid CONNECT_TIME field in theVMPRF record, or with a valid H61CONT field in thez/VM Performance Toolkit record.

SERVICE_MSEC FLOAT Device service time, in milliseconds. Calculated as((CONNECT_TIME + DISCONNECT_TIME +PENDING_TIME)/SCM_UPDATES)*1000 from theVMPRF record. Calculated as ((H61CONT +H61DSCT + H61FPNT)/H61SSCH)*1000 from thez/VM Performance Toolkit record.

SSCH_AND_RSCH FLOAT Number of start subchannel and resume subchannelinstructions performed. This is the sum ofSSCH_AND_RSCH in the VMPRF record, or the sumof H61SSCH in the z/VM Performance Toolkit record.

SSCH_QUEUED FLOAT Number of start subchannel requests queued,excluding the active request. This is the sum ofSSCH_QUEUED in the VMPRF record, or the sum ofH61HFQUD in the z/VM Performance Toolkit record.

VMPRF_LPARS_H, _D, _M:These tables provide hourly, daily, and monthly statistics on logical partitions andprocessor activity in a PR/SM™ environment. They contain data from record typeX'FC03' created by the z/VM Performance Toolkit.

In order to collect data for the MIPS_PROC_SEC, MIPS_SYSTEM_SEC, andMIPS_USED_SEC columns, the VMPRF_MIPS_CPU lookup table must have beencustomized.

Note: The VMPRF_LPARS_H,_D,_M data tables are loaded from the z/VMPerformance Toolkit, only.


VMPRF_LPARS_H10 days

VMPRF_LPARS_D30 days

VMPRF_LPARS_M765 days




PERIOD_NAME K CHAR(8) Name of the period. This is derived using fieldsDATE and TIME as parameters in the PERIODfunction.


VM_SYSTEM_ID K CHAR(8) VM system identifier. From the SUMRSYID field.

LPAR_NAME K CHAR(8) Name of the logical partition. From H03NAME.

COMPLEX_SEC FLOAT Measured time period for all the processors in the CPcomplex, in seconds. Calculated as the sum ofSUMRELT*H03NRPRC.

CPU_DISPATCH_SEC FLOAT Processor dispatch time, in seconds. From H03ACTM.

CPU_MODEL_NO CHAR(8) CPU model number. From VMPRF_MIPS_CPUlookup table. For example 9021-900. $UNKNOWNmeans that the lookup table must be customized forthe corresponding serial number.

CPU_SERIAL_NUMBER CHAR(5) Last 5 digits of the CPU serial number. This is thesystem serial number without a processor identifier asthe first character. From SUMRCSER.

DISPATCH_INTERVAL FLOAT Dispatch interval time, in seconds. A value of 0indicates that the interval was dynamicallydetermined. Calculated as H03DSPIN/!000.

ELAPSED_SEC FLOAT Measured time period for all the processors in theLPAR, in seconds. Equivalent toSUMRELT*H03NRLPR.

FROM_LPAR_FLAG SMALLINT Indicates which LPAR generated the data. FromH03FLAG. The eighth bit is set to 1 if this LPARgenerated the data, otherwise is set to 0.

LOGICAL_PROCESSORS SMALLINT Number of logical processors assigned to the logicalpartition. Set to 0 if the logical partition is not active.From H03NRLPR.

LPAR_NO SMALLINT Number of the logical partition. From H03LPRNR.

LPAR_WEIGHT INTEGER Logical partition processor resource weight factor. It isset to -1 (X'FFFF') for a dedicated physical processor.From H03WGHT.

MEASURED_SEC FLOAT Measured time period, in seconds. This is theduration of the measurement intervals. Calculatedfrom SUMRELT.

MIPS_PROC_SEC FLOAT Total MIPS available to the processors in the CPcomplex multiplied by MEASURED_SEC. Whendivided by MEASURED_SEC, you get the totalcapacity of processors in MIPS. Calculated as the sumof SUMRELT*MIPS_PROCESSOR (the MIPS perphysical processor taken from the lookuptable)*H03NRPRC/H03NRLPR.



MIPS_SYSTEM_SEC FLOAT MIPS available to this LPAR multiplied byMEASURED_SEC, if no contention exists. Whendivided by MEASURED_SEC, you get the capacity ofLPAR in MIPS. Calculated as the sum ofSUMRELT*MIPS_PROCESSOR (the MIPS per physicalprocessor taken from the lookup table).

MIPS_USED_SEC FLOAT MIPS used by this LPAR multiplied byMEASURED_SEC, if no contention exists. Whendivided by MEASURED_SEC, you get the totalcapacity of processors in MIPS used. Calculated as thesum of H03ACTM*MIPS_PROCESSOR (the MIPS perphysical processor taken from the lookup table).

PHYS_PROCESSORS SMALLINT Number of physical processors assigned for use byPR/SM. From H03NRLPRC.

WAIT_COMPLETE_FLAG SMALLINT Set to 1 if wait completion is enabled, otherwise is setto 0. If wait completion is enabled, the LPAR keeps itstime-slice even if it is in a wait state. FromH03WFLAG.

VMPRF_PROCESSOR_H, _D, _M:These tables provide hourly, daily, and monthly statistics on processor activity onVM systems. They contain processor data from record type 02 (created by the VMPerformance Reporting Facility), or from record type X'FC02' (created by the z/VMPerformance Toolkit).


VMPRF_PROCESSOR_H10 days

VMPRF_PROCESSOR_D30 days

VMPRF_PROCESSOR_M765 days





VM_SYSTEM_ID K CHAR(8) VM system ID. From the SYSTEMID parameterspecified in the SETTINGS file or on the VMPRFcommand line. From SUMRSYID in the z/VMPerformance Toolkit record.

CPU_ADDRESS K INTEGER Processor address. From CPU_ADDRESS in theVMPRF record or from H02PRCID in the z/VMPerformance Toolkit record.



BUSY_SYSTEM_PCT FLOAT Processor busy time, as a percentage of the time thesystem is online. Calculated as(PROC_SYSTEM_TIME/PROC_ONLINE_D0R2)*100from the VMPRF record, or as (H02SYTIM/SUMRELT)*100 from the z/VM Performance Toolkitrecord.

BUSY_TOTAL_PCT FLOAT Total busy time, as a percentage of the elapsed timethat the processor is online. Calculated as(PROC_SYSTEM_TIME + PROC_USER_TIME/PROC_ONLINE_D0R2)*100 from the VMPRF record,or as (H02SYTIM + H02USTIM/SUMRELT)*100 fromthe z/VM Performance Toolkit record.

BUSY_USER_PCT FLOAT User busy time, as a percentage of the time theprocessor is online. Calculated as(PROC_USER_TIME/PROC_ONLINE_D0R2)*100from the VMPRF record, or as (H02USTIM/SUMRELT)*100 from the z/VM Performance Toolkitrecord.

BUSY_VECTOR_PCT FLOAT Vector busy time, as a percentage of the elapsed timethe system is online. Calculated as(VECTOR_TIME/PROC_ONLINE_D0R2)*100 from theVMPRF record, or as (H02VFTIM/SUMRELT)*100from the z/VM Performance Toolkit record.

CONNECT_SEC FLOAT Time that the processor was busy, in seconds. This isthe sum of PROC_USER_TIME andPROC_SYSTEM_TIME from the VMPRF record, or thesum of H02USTIM and H02SYTIM from the z/VMPerformance Toolkit record.

CPU_ID CHAR(6) Serial number. This is the system serial numberwithout a processor identifier as the first character.From SYSTEM_SERIAL_NO in the VMPRF record orfrom SUMRCSER in the z/VM Performance Toolkitrecord.

CPU_MODEL_NO CHAR(4) Model number. This is the processor machine type.From MACHINE_TYPE in the VMPRF record or fromSUMRSYID in the z/VM Performance Toolkit record.

CSCH_COUNT FLOAT Number of clear subchannel executions. This is thesum of CSCHS in the VMPRF record, or the sum ofH02CSCH in the z/VM Performance Toolkit record.

DASD_PAGEIN_RATE FLOAT Number of disk reads done for system paging.Calculated as the average of PAGE_READS/ELAPSED_TIME from the VMPRF record, or as theaverage of H02PGRDS/SUMRELT from the z/VMPerformance Toolkit record.

DASD_PAGEOUT_RATE FLOAT Number of disk writes done for system paging.Calculated as the average of PAGE_WRITES/ELAPSED_TIME from the VMPRF record, or as theaverage of H02PGWRT/SUMRELT from the z/VMPerformance Toolkit record.

DIAG_INSTRUCTIONS FLOAT Number of IBM-supplied DIAGNOSE instructionsexecuted. This is the sum of DIAG_INSTRUCTIONSfrom the VMPRF record, or the sum of H02DIACTfrom the z/VM Performance Toolkit record.



ELAPSED_SECONDS FLOAT Elapsed time that the processor was online. FromELAPSED_TIME in the VMPRF record fromSUMRELTin the z/VM Performance Toolkit record.

ESTOR_PAGEIN_RATE FLOAT Number of blocks per second read from expandedstorage. Calculated as the average of(FASTPATH_PGINS + NON_FASTPATH_PGINS)/ELAPSED_TIME from the VMPRF record. Calculatedas the average of (H02FPGIN + H02PGINS)/SUMRELT from the z/VM Performance Toolkitrecord.

ESTOR_PGEOUT_RATE FLOAT Number of blocks per second written to expandedstorage. Calculated as the average ofPGOUTS/ELAPSED_TIME from the VMPRF record,or as the average of H02PGOUT/SUMRELT from thez/VM Performance Toolkit record.

EXTERN_INTERRUPTS FLOAT Number of external interrupts received. This is thesum of EXTERN_INTERRUPTS from the VMPRFrecord, or the sum of H02EXTIT from the z/VMPerformance Toolkit record.

FASTPATH_PERCENT FLOAT Percentage of page reads from expanded storage thatused the fast path. Calculated as (FASTPATH_PGINS/(FASTPATH_PGINS + NON_FASTPATH_PGINS))*100from the VMPRF record. Calculated as (H02FPGIN/(H02FPGIN+H02PGINS)*100 from thez/VM Performance Toolkit record.

HSCH_COUNT FLOAT Number of halt subchannel executions. This is thesum of HSCHS from the VMPRF record, or the sumof H02HSCH from the z/VM Performance Toolkitrecord.

PAGE_READS FLOAT Number of page reads from DASD. This is the sum ofPAGE_READS from the VMPRF record, or the sum ofH02PGRDS from the z/VM Performance Toolkitrecord.

PAGES_READ_TO_MS FLOAT Number of virtual machine pages read (paged in)from expanded storage to main storage. This is thesum of FASTPATH_PGINS andNON_FASTPATH_PGINS from the VMPRF record, orthe sum of H02FPGIN and H02PGINS from the z/VMPerformance Toolkit record.

PAGES_WRIT_TO_ES FLOAT Number of virtual machine pages written (paged out)from main storage to expanded storage. This is thesum of PGOUTS from the VMPRF record, or the sumof H02PGOUT from the z/VM Performance Toolkitrecord.

PAGE_WRITES FLOAT Number of page writes to DASD. This is the sum ofPAGE_WRITES from the VMPRF record, or the sumof H02PGWRT from the z/VM Performance Toolkitrecord.

PROC_EMUL_SEC FLOAT Processor time spent in emulation mode, in seconds.This is the sum of PROC_EMUL_TIME from theVMPRF record, or the sum of H02EMTIM from thez/VM Performance Toolkit record.



PROC_SYSTEM_SEC FLOAT Processor time used by the system, in seconds. Thistime is charged to the system. It includes time that theCP spends on behalf of users doing things such asinstruction simulation and page translation. This isthe sum of PROC_SYSTEM_TIME from the VMPRFrecord, or the sum of H02SYTIM from the z/VMPerformance Toolkit record.

PROC_USER_SEC FLOAT Processor time spent by the user, in seconds. This isthe time charged to the user. It does not include timethat the CP spends on behalf of a user doing thingssuch as instruction simulation or page translation.This is the sum of PROC_USER_TIME from theVMPRF record, or the sum of H02USTIM from thez/VM Performance Toolkit record.

RECORDS_COLLECTED FLOAT Number of records collected. This is the count ofrecords with a valid ELAPSED_TIME field from theVMPRF record, or with a valid SUMRELT field fromthe z/VM Performance Toolkit record.

RSCH_COUNT FLOAT Number of resume subchannel executions. This is thesum of RSCHS from the VMPRF record, or the sum ofH02RSCH from the z/VM Performance Toolkit record.

SIGP_INTERRUPTS FLOAT Number of external SIGPs issued by this system. Thisis the sum of SIGP_INTERRUPTS from the VMPRFrecord, or the sum of H02SIGCT from the z/VMPerformance Toolkit record.

SIMUL_INSTRUCTIONS FLOAT Number of simulated instructions executed. This isthe sum of SIMUL_INSTRUCTIONS from the VMPRFrecord, or the sum of H02PRVCT from the z/VMPerformance Toolkit record.

SPOOL_READS FLOAT Number of I/Os issued for spool read requests. Thisis the sum of SPOOL_READS from the VMPRFrecord, or the sum of H02RSCH from the z/VMPerformance Toolkit record.

SPOOL_WRITES FLOAT Number of I/Os issued for spool write requests. Thisis the sum of SPOOL_WRITES from the VMPRFrecord, or the sum of H02PGWRT from the z/VMPerformance Toolkit record.

SSCH_COUNT FLOAT Number of start subchannel executions. This is thesum of SSCHS from the VMPRF record, or the sum ofH02SSCH from the z/VM Performance Toolkit record.

SYSTEM_ONLINE_SEC FLOAT Elapsed time that the processor was online, inseconds. This is the sum of PROC_ONLINE_D0R2from the VMPRF record, or the sum of SUMRELTfrom the z/VM Performance Toolkit record.

SYSTEM_WAIT_SEC FLOAT System wait time, in seconds. This is the time that thesystem had no work to do. It includes active wait andenabled wait times. This is the sum ofPROC_WAIT_TIME from the VMPRF record, or thesum of H02WAIT from the z/VM Performance Toolkitrecord.



VECTOR_USER_SEC FLOAT Time spent using vector instructions while in SIE, inseconds. This time is included in virtual processortime. This is the sum of VECTOR_TIME from theVMPRF record, or the sum of H02VFTIM from thez/VM Performance Toolkit record.

VF_OVERHEAD_SEC FLOAT Vector facility overhead time, in seconds. This is thetime spent switching vector users. This is the sum ofVECTOR_SWITCH_TIME from the VMPRF record, orthe sum of H02VOTIM from the z/VM PerformanceToolkit record.

WAIT_PCT FLOAT Wait time, as a percentage of the elapsed time thesystem is online. Calculated as (PROC_WAIT_TIME/PROC_ONLINE_D0R2)*100 from the VMPRF record.Calculated as (H02WAIT/SUMRELT)*100 from thez/VM Performance Toolkit record.

VMPRF_SYSTEM_H, _D, _M:These tables provide hourly, daily, and monthly statistics on VM systems. Theycontain system data from record type 01 (created by the VM PerformanceReporting Facility), or from record types X'FC01' and X'FC02' (created by the z/VMPerformance Toolkit).


VMPRF_SYSTEM_H10 days

VMPRF_SYSTEM_D30 days

VMPRF_SYSTEM_M765 days




TIME K TIME Time (rounded down to the nearest hour) when thedata about the VM system was created. This appliesonly to the _H table. From TIME.


BUSY_SYSTEM_PCT FLOAT Processor busy time, as a percentage of the time thesystem is online. Calculated as(PROC_SYSTEM_TIME/PROC_ONLINE_D0R2)*100from the VMPRF record. Calculated as the average of(H02SYTIM/SUMRELT)*100 from the z/VMPerformance Toolkit record.



BUSY_TOTAL_PCT FLOAT Total busy time, as a percentage of the elapsed timethat the processor is online. Calculated as(PROC_SYSTEM_TIME + PROC_USER_TIME/PROC_ONLINE_D0R2)*100 from the VMPRF record.Calculated as the average of (H02SYTIM +H02USTIM/SUMRELT)*100 from the z/VMPerformance Toolkit record.

BUSY_USER_PCT FLOAT User busy time, as a percentage of the time theprocessor is online. Calculated as(PROC_USER_TIME/PROC_ONLINE_D0R2)*100from the VMPRF record. Calculated as the average of(H02USTIM/SUMRELT)*100 from the z/VMPerformance Toolkit record.

BUSY_VECTOR_PCT FLOAT Vector busy time, as a percentage of the elapsed timethe system is online. Calculated as(VECTOR_TIME/PROC_ONLINE_D0R2)*100 from theVMPRF record. Calculated as the average of(H02VFTIM/SUMRELT)*100 from the z/VMPerformance Toolkit record.

CONNECT_SEC FLOAT Time that the processor was busy, in seconds. This isthe sum of PROC_USER_TIME andPROC_SYSTEM_TIME from the VMPRF record, or thesum of H02USTIM and H02SYTIM from the z/VMPerformance Toolkit record.

CPU_ID CHAR(6) Serial number. This is the system serial numberwithout a processor identifier as the first character.From SYSTEM_SERIAL_NO in the VMPRF record, orfrom SUMRCSER in the z/VM Performance Toolkitrecord.

CPU_MODEL_NO CHAR(4) Model number. This is the processor machine type.From MACHINE_TYPE in the VMPRF record, or fromSUMRCMDL in the z/VM Performance Toolkitrecord.

CPU_ONLINE_COUNT FLOAT Number of processors online. Calculated asPROC_ONLINE_D0R2/ELAPSED_TIME from theVMPRF record, or from H002PRCID in the z/VMPerformance Toolkit record.

CSCH_COUNT FLOAT Number of clear subchannel executions. This is thesum of CSCHS in the VMPRF record, or the sum ofH02CSCH in the z/VM Performance Toolkit record.

DASD_PAGEIN_RATE FLOAT Number of disk reads done for system paging.Calculated as the sum of the corresponding column inthe VMPRF_PROCESSOR_H table.

DASD_PAGEOUT_RATE FLOAT Number of disk writes done for system paging.Calculated as the sum of the corresponding column inthe VMPRF_PROCESSOR_H table.

DIAG_INSTRUCTIONS FLOAT Number of IBM-supplied DIAGNOSE instructionsexecuted. This is the sum of DIAG_INSTRUCTIONSfrom the VMPRF record. Calculated as the sum ofH02DIACT from the z/VM Performance Toolkitrecord.



ELAPSED_SECONDS FLOAT Elapsed time that the processor was online. FromELAPSED_TIME in the VMPRF record, or calculatedas the average of SUMRELT from the z/VMPerformance Toolkit record.

ESTOR_PAGEIN_RATE FLOAT Number of blocks per second read from expandedstorage. Calculated as the sum of the correspondingcolumn in the VMPRF_PROCESSOR_H table.

ESTOR_PGEOUT_RATE FLOAT Number of blocks per second written to expandedstorage. Calculated as the sum of the correspondingcolumn in the VMPRF_PROCESSOR_H table.

EXTERN_INTERRUPTS FLOAT Number of external interrupts received. This is thesum of EXTERN_INTERRUPTS in the VMPRF record,or the sum of H02EXTIT in the z/VM PerformanceToolkit record.

FASTPATH_PERCENT FLOAT Percentage of page reads from expanded storage thatused the fast path. Calculated as (FASTPATH_PGINS/(FASTPATH_PGINS + NON_FASTPATH_PGINS))*100from the VMPRF record. Calculated as(H02FPGIN/(H02FPGIN + H02PGINS))*100 from thez/VM Performance Toolkit record.

HSCH_COUNT FLOAT Number of halt subchannel executions. This is thesum of HSCHS from the VMPRF record, or the sumof H02HSCH from the z/VM Performance Toolkitrecord.

PAGE_READS FLOAT Number of page reads from DASD. This is the sum ofPAGE_READS from the VMPRF record, or the sum ofH02PGRDS from the z/VM Performance Toolkitrecord.

PAGES_READ_TO_MS FLOAT Number of virtual machine pages read (paged in)from expanded storage to main storage. This is thesum of FASTPATH_PGINS andNON_FASTPATH_PGINS from the VMPRF record, orthe sum of H02FPGIN and H02PGINS from the z/VMPerformance Toolkit record.

PAGES_WRIT_TO_ES FLOAT Number of virtual machine pages written (paged out)from main storage to expanded storage. This is thesum of PGOUTS from the VMPRF record, or the sumof H02PGOUT from the z/VM Performance Toolkitrecord.

PAGE_WRITES FLOAT Number of page writes to DASD. This is the sum ofPAGE_WRITES from the VMPRF record, or the sumof H02PGWRT from the z/VM Performance Toolkitrecord.

PROC_EMUL_SEC FLOAT Processor time spent in emulation mode, in seconds.This is the sum of PROC_EMUL_TIME from theVMPRF record, or the sum of H02EMTIM from thez/VM Performance Toolkit record.

PROC_SYSTEM_SEC FLOAT Processor time used by the system, in seconds. Thistime is charged to the system. It includes time that theCP spends on behalf of users doing things such asinstruction simulation and page translation. This isthe sum of PROC_SYSTEM_TIME from the VMPRFrecord, or the sum of H02SYTIM from the z/VMPerformance Toolkit record.



PROC_USER_SEC FLOAT Processor time spent by the user, in seconds. This isthe time charged to the user. It does not include timethat the CP spends on behalf of a user doing thingssuch as instruction simulation or page translation.This is the sum of PROC_USER_TIME from theVMPRF record, or the sum of H02USTIM from thez/VM Performance Toolkit record.

REC02_COLLECTED FLOAT Number of processor data records collected. It appliesonly to the _H table, for the record created by thez/VM Performance Toolkit.

RECORDS_COLLECTED FLOAT Number of system data records collected. This is thecount of records with a valid ELAPSED_TIME fieldfrom the VMPRF record, or with a valid SUMRELNfield from the z/VM Performance Toolkit recordX'FC01'.

RSCH_COUNT FLOAT Number of resume subchannel executions. This is thesum of RSCHS from the VMPRF record, or the sum ofH02RSCH from the z/VM Performance Toolkit record.

SIGP_INTERRUPTS FLOAT Number of external SIGPs issued by this system. Thisis the sum of SIGP_INTERRUPTS from the VMPRFrecord, or the sum of H02SIGCT from the z/VMPerformance Toolkit record.

SIMUL_INSTRUCTIONS FLOAT Number of simulated instructions executed. This isthe sum of SIMUL_INSTRUCTIONS from the VMPRFrecord, or the sum of H02PRVCT from the z/VMPerformance Toolkit record.

SPOOL_READS FLOAT Number of I/Os issued for spool read requests. Thisis the sum of SPOOL_READS from the VMPRFrecord, or the sum of H02SPRDS from the z/VMPerformance Toolkit record.

SPOOL_WRITES FLOAT Number of I/Os issued for spool write requests. Thisis the sum of SPOOL_WRITES from the VMPRFrecord, or the sum of H02SPWRT from the z/VMPerformance Toolkit record.

SSCH_COUNT FLOAT Number of start subchannel executions. This is thesum of SSCHS from the VMPRF record, or the sum ofH01DSSSC from the z/VM Performance Toolkitrecord.

SYSTEM_ONLINE_SEC FLOAT Elapsed time that the processor was online, inseconds. This is the sum of PROC_ONLINE_D0R2, orthe sum of SUMRELT from the z/VM PerformanceToolkit record X'FC01'.

SYSTEM_WAIT_SEC FLOAT System wait time, in seconds. This is the time that thesystem had no work to do. It includes active wait andenabled wait times. This is the sum ofPROC_WAIT_TIME from the VMPRF record, or thesum of H02WAIT from the z/VM Performance Toolkitrecord.



USERS_DORMANT FLOAT Number of users in the dormant list. These areinactive users. They might be in a wait state or haveno work pending. This includes users found in SVMwait. Calculated as the average ofDORMANT_USERS/INTERVALS_D0R8 from theVMPRF record. Calculated as the average ofH01RSDOR from the z/VM Performance Toolkitrecord.

USERS_LOGGED FLOAT Number of users logged on to the system. Calculatedas the average of LOGGED_USERS/INTERVALS_D0R8 from the VMPRF record.Calculated as the average of H01RSLOG from thez/VM Performance Toolkit record.

VECTOR_USER_SEC FLOAT Time spent using vector instructions while in SIE, inseconds. This time is included in virtual processortime. This is the sum of VECTOR_TIME from theVMPRF record, or the sum of H02VFTIM from thez/VM Performance Toolkit record.

VF_OVERHEAD_SEC FLOAT Vector facility overhead time, in seconds. This is thetime spent switching vector users. This is the sum ofVECTOR_SWITCH_TIME from the VMPRF record, orthe sum of H02VOTIM from the z/VM PerformanceToolkit record.

WAIT_PCT FLOAT Wait time, as a percentage of the elapsed time thesystem is online. Calculated as (PROC_WAIT_TIME/PROC_ONLINE_D0R2)*100 from the VMPRF record.Calculated as (H02WAIT/SUMRELT)*100 from thez/VM Performance Toolkit record.

VMPRF_USER_H, _D, _M:These tables provide hourly, daily, and monthly statistics on users of VM systems.They contain user data from record type 41 (created by the VM PerformanceReporting Facility), or from record types X'FC41' and X'FC44' (created by the z/VMPerformance Toolkit).

Note:

When you use the z/VM Performance Toolkit, both record types

X'FC41'

and

X'FC44'

are required. To collect data from record types

X'FC44'

, set the EVENT USER parameter in the VM monitor. If record types

X'FC44'


are not found in the log file, the SPOOL_READS and SPOOL_WRITES columns areset to 0.


VMPRF_USER_H10 days

VMPRF_USER_D30 days

VMPRF_USER_M765 days






USER_CLASS K CHAR(8) Name of the group that the user belongs to. FromGROUP_NAME in the USER_GROUP lookup table; ifno match is found, this column gets its value fromUSER_ID.

For a description of the USER_GROUP lookup table,refer to the Administration Guide and Reference.

USER_ID K CHAR(8) User ID. From USER_ID in the VMPRF record, orfrom H41USER in the z/VM Performance Toolkitrecord.

ACTIVE_SEC FLOAT Time that the user was active on the system. Anactive user is one who consumed virtual CPU time oris not in the dormant list at end of the interval. This isthe sum of ACTIVE_TIME in the VMPRF record, orthe sum of H41TIMAC in the z/VM PerformanceToolkit record.

CONNECT_SEC FLOAT Time that the user was connected, in seconds. This isthe sum of CONNECT_TIME in the VMPRF record,or the sum of H41TIMLG in the z/VM PerformanceToolkit record.

CONSOLE_IO FLOAT Number of start requests issued to the virtualmachine console. This is the sum of CONSOLE_IO inthe VMPRF record, or the sum of H41IOCON in thez/VM Performance Toolkit record.



CPU_TOTAL_SEC FLOAT Total processor time spent by the user, in seconds.This includes time that the user spent on doing hisown work, and time that the CP spent doing work onbehalf of the user. This is the sum ofTOTAL_CPU_TIME in the VMPRF record, or the sumof H41TCPU in the z/VM Performance Toolkit record.

CPU_VIRTUAL_SEC FLOAT Virtual processor usage, in seconds. This is the timethe user was running and doing productive work. Itdoes not include time spent on behalf of the userdoing things such as instruction simulation or pagetranslation. From VIRTUAL_CPU_TIME in theVMPRF record, or the sum of H41VCPU in the z/VMPerformance Toolkit record.

CTC_IO FLOAT Number of start requests issued to the virtualmachine channel-to-channel adapters. This is the sumof CTC_IO in the VMPRF record, or the sum ofH41IOCTC in the z/VM Performance Toolkit record.

DASD_IO FLOAT Number of I/O requests the virtual machine issued toDASD devices. This is the sum of DASD_IO in theVMPRF record, or the sum of H41IODSD in thez/VM Performance Toolkit record.

DASD_IO_RATE FLOAT Number of I/O requests per second the virtualmachine issued to DASD_devices. Calculated asDASD_IO/USER_LOGGED_D4R4 from the VMPRFrecord, or as U41IODSD/SUMRELT from the z/VMPerformance Toolkit record.

IUCV_DATA_FAILED FLOAT Number of unsuccessful IUCV data transfers. This isthe sum of IUCV_DATA_FAILED from the VMPRFrecord, or the sum of H41TCPU from the z/VMPerformance Toolkit record.

IUCV_DATA_RECEIVED FLOAT Number of successful IUCV data transfers to thevirtual machine. This is the sum ofIUCV_DATA_RECEIVED in the VMPRF record, or thesum of H41IURCV in the z/VM Performance Toolkitrecord.

IUCV_DATA_SENT FLOAT Number of successful IUCV data transfers from thevirtual machine. This is the sum ofIUCV_DATA_SENT in the VMPRF record, or the sumof H41IUSND in the z/VM Performance Toolkitrecord.

IUCV_MSGQ_SEND FLOAT Number of messages on the IUCV SEND queue. Thisis the sum of IUCV_MSGQ_SEND in the VMPRFrecord, or the sum of H41IUSNQ in the z/VMPerformance Toolkit record.

LOGGED_SEC FLOAT Time that the user was logged on, in seconds. This isthe sum of USER_LOGGED_D4R3 in the VMPRFrecord, or the sum of SUMRELT in the z/VMPerformance Toolkit record.

OTHER_IO FLOAT Number of start requests issued to device for whichno other counter is defined. This is the sum ofOTHER_IO in the VMPRF record, or the sum ofH41IOOTH in the z/VM Performance Toolkit record.



PAGE_IO_RATE FLOAT Number of page reads and writes per second.Calculated as (PAGE_READ_IO +PAGE_WRITE_IO)/USER_LOGGED_D4R4 from theVMPRF record. Calculated as (H41PGRD +H41PGWRT)/SUMRELT from the z/VM PerformanceToolkit record.

PAGE_READS FLOAT Number of page reads from DASD. This is the sum ofPAGE_READ_IO in the VMPRF record, or the sum ofH41PGRD in the z/VM Performance Toolkit record.

PAGES_READ_TO_MS FLOAT Number of virtual machine pages read (paged in)from expanded storage to main storage. This is thesum of PAGES_READ_TO_MS in the VMPRF record,or the sum of H41MNTOX in the z/VM PerformanceToolkit record.

PAGES_WRIT_TO_ES FLOAT Number of virtual machine pages written (paged out)from main storage to expanded storage. This is thesum of PGOUTS in the VMPRF record, or the sum ofH41MNTOX in the z/VM Performance Toolkit record.

PAGE_WRITES FLOAT Number of page writes to DASD. This is the sum ofPAGE_WRITE_IO in the VMPRF record, or the sum ofH41PGWRT in the z/VM Performance Toolkit record.

RECORDS_COLLECTED FLOAT Number of records collected. This is the count ofrecords with a valid ACTIVE_TIME field in theVMPRF record, or the sum of H41TIMAC in thez/VM Performance Toolkit record.

SPOOL_READS FLOAT Number of I/Os issued for spool read requests. Thisis the sum of SPOOL_READ_IO in the VMPRF record,or the sum of H44SPRDS in the z/VM PerformanceToolkit record.

SPOOL_WRITES FLOAT Number of I/Os issued for spool write requests. Thisis the sum of SPOOL_WRITE_IO in the VMPRFrecord, or the sum of H44SPWRT in the z/VMPerformance Toolkit record.

UR_IO FLOAT Number of start requests issued to the virtualmachine unit record devices. This is the sum ofUR_IO in the VMPRF record, or the sum of H41IOURin the z/VM Performance Toolkit record.

VECTOR_USER_SEC FLOAT Time spent using vector instructions while in SIE, inseconds. This is included in CPU_VIRTUAL_SEC.This is the sum of VECTOR_TIME in the VMPRFrecord, or the sum of H41VVEC in the z/VMPerformance Toolkit record.

VMCF_DATA_FAILED FLOAT Number of unsuccessful VMCF data transfers. This isthe sum of VMCF_DATA_FAILED in the VMPRFrecord, or the sum of H41VMFAI in the z/VMPerformance Toolkit record.

VMCF_DATA_RECEIVED FLOAT Number of successful VMCF data transfers to thevirtual machine. This is the sum ofVMCF_DATA_RECEIVED in the VMPRF record, orthe sum of H41VMRCV in the z/VM PerformanceToolkit record.



VMCF_DATA_SENT FLOAT Number of successful VMCF data transfers from thevirtual machine. This is the sum ofVMCF_DATA_SENT in the VMPRF record, or thesum of H41VMSND in the z/VM Performance Toolkitrecord.

ViewsThis section describes the views for the z/VM Performance component.

VMPRF_LPARS_HV,_DV,_MV:These views provide hourly, daily, and monthly statistics on logical partitions andprocessor activity in a PR/SM environment. They are based on theVMPRF_LPARS_H,_D,_M tables.


DATE K DATE Date when the data about the VM system wascreated. For the _MV table, this is the date of the firstday of the month. From DATE.

TIME K TIME Time (rounded down to the nearest hour) when thedata about the VM system was created. It applies onlyto the _HV table. From TIME.

PERIOD_NAME K CHAR(8) Name of the period. This is derived using fieldsDATE and TIME as parameters in the PERIODfunction.

VM_SYSTEM_ID K CHAR(8) VM system identifier. From the SUMRSYID field.

LPAR_NAME K CHAR(8) Name of the logical partition. From H03NAME.

COMPLEX_BUSY_PCT FLOAT Processor busy time percentage for the COMPLEX,calculated as 100*CPU_DISPATCH_SEC/COMPLEX_SEC.

LPAR_BUSY_PCT FLOAT Processor busy time percentage for the LPAR,calculated as 100*CPU_DISPATCH_SEC/ELAPSED_SEC.

MIPS_LPAR FLOAT Capacity of the LPAR in MIPS, calculated asMIPS_PROC_SEC/MEASURED_SEC.

MIPS_PROCESSOR FLOAT Capacity of the processor complex in MIPS, calculatedas MIPS_PROC_SEC/MEASURED_SEC.

MIPS_USED FLOAT MIPS used by the LPAR, calculated asMIPS_USED_SEC/MEASURED_SEC.

Note: As well as from the columns described here, these views also contain all thedata columns described in VMPRF_LPARS_H, _D, _M.

Lookup tablesThis section describes the lookup tables for the z/VM Performance component.

VMPRF_MIPS_CPU:VMPRF_MIPS_CPU

This lookup table provides CPU capacity information (MIPS) for processors thathave been collecting data. It is referenced at collect time when updating theVMPRF_LPAR_H table.



CPU_SERIAL_NO K CHAR(5) Last 5 digits of the CPU serial number. FromSYSTEM_SERIAL_NO.

CPU_COUNT SMALLINT Number of physical processors in the processorcomplex.

CPU_MODEL_NO CHAR(8) CPU model number. From VMPRF_CPU_MODELtable. For example: 9021-900.

CPU_NORM_FACTOR DECIMAL(9,2) Normalization factor. Optional. It can be used forcomparing CPUs in reports.

DESCRIPTION VARCHAR(50) Description or comments about the CPU.

MIPS_PER_CPU FLOAT MIPS per CPU for this processor. This is usually equalto MIPS_PROCESSOR/CPU_COUNT.

MIPS_PROCESSOR DECIMAL(9,2) Rated capacity of this processor in MIPS.

VMPRF_TIMEZONES:This lookup table associates a relative number with each VM system identifier.This number represents the hour difference (negative or positive) with respect toGMT.


VM_SYSTEM_ID K CHAR(8) The VM system identifier.

TIMEOFF SMALLINT Local time offset, in hours, with respect to GMT.

ReportsThe VM Performance component provides these reports:v System reports

– z/VM System Processor Usage, Hourly report– z/VM System Busy Distribution, Hourly report– z/VM System Page and Spool Counts, Hourly report– z/VM System Exp Stor and Paging Activity, Hourly report– z/VM System Instruction Rate, Hourly report– z/VM System Instruction Counts, Hourly report– z/VM System MIPS Capacity by LPAR, Daily report

v Processor reports– z/VM Processor Usage Distribution, Hourly report– z/VM Processor Busy Distribution, Hourly report– z/VM Processor Page and Spool Activity, Hourly report– z/VM Processor Storage Activity, Hourly report– z/VM Processor Instruction Rate, Hourly report– z/VM Processor Instruction Counts, Hourly report

v User reports– z/VM User Real and Virt Processor Usage, Monthly report– z/VM User Paging and Spooling, Monthly report– z/VM User IUCV and VMCF Counts, Monthly report– z/VM Heaviest Users of the Processor, Monthly report– z/VM Heaviest Users of DASD, Monthly report


– z/VM Heaviest Users of Paging, Monthly report– z/VM Processor Usage by User Class, Monthly report– z/VM Paging by User Class, Monthly report– z/VM IUCV and VMCF Usage by User Class, Monthly report

v DASD reports– z/VM Most-Used DASD by Start Subchannel Rate report– z/VM Slowest DASD by Response Time report– z/VM DASD With Longest Queues report– z/VM Least Used or not Used DASD Devices report– z/VM Least Used DASD Devices report

v Configuration reports– z/VM Configuration, Level and Storage, Daily report– z/VM Configuration, Level and IPL, Daily report

System reportsThe system reports show processor usage and distribution, and also system pagingand instruction rates.

z/VM System Processor Usage, Hourly report:This report shows the total percentage usage of all processors in the z/VM system.


Report IDVMPRF_S1

Report groupz/VM Performance reports

SourceVMPRF_SYSTEM_H

AttributesVM, VMPRF, CPU, Hourly, Performance, Trend

VariablesDate, Period_name_list, VM_system_ID, From_time, To_time



Hour The time, rounded down to the hour, of the measurement.

Busy time (%)The total busy time, as a percentage of the elapsed time that the processoris online.

Wait time (%)The wait time, as a percentage of the elapsed time that the processor isonline.

z/VM System Busy Distribution, Hourly report:This report shows how processor time is distributed.


Report IDVMPRF_S2



Figure 170. Example of a z/VM System Processor Usage, Hourly report






User time (sec)The processor time spent by the user, in seconds. This time is charged tothe user. It does not include time that CP spent on behalf of a user doingsuch things as instruction simulation and page translation.

System time (sec)The processor time used by the system, in seconds. This time is charged tothe system. It includes time that CP spent on behalf of a user doing suchthings as instruction simulation and page translation.

Emulator time (sec)The time that the system processors spent in emulation mode, in seconds.

Vector time (sec)The time spent using vector instructions while in start interpretativeexecution (SIE) mode, in seconds. This time is included in virtual processortime.

Figure 171. Example of a VMPRF System Busy Distribution, Hourly report


z/VM System Page and Spool Counts, Hourly report:This report shows paging to DASD and spooling rates.


Report IDVMPRF_S3



AttributesVM, VMPRF, Paging, Hourly, Performance, Trend




Spool writesThe number of writes done for system spooling.

Figure 172. Example of a z/VM System Page and Spool Counts, Hourly report


Spool readsThe number of reads done for system spooling.

Page writesThe number of pages written to DASD.

Page readsThe number of pages read from DASD.

z/VM System Exp Stor and Paging Activity, Hourly report:This report shows paging rates to DASD and to expanded storage.


Report IDVMPRF_S4



AttributesVM, VMPRF, Paging, Hourly, Performance, Storage, Trend





DASD page-outs/secThe number of DASD writes per second done for paging.

DASD page-ins/secThe number of DASD reads per second done for paging.

Expanded page-outs/secThe number of pages per second written to expanded storage.

Expanded page-ins/secThe number of pages per second read from expanded storage.

z/VM System Instruction Rate, Hourly report:This report shows the rates for different types of instruction. For more informationon using this report, refer to the System Performance Feature Guide.


Report IDVMPRF_S5


Figure 173. Example of a z/VM System Exp Stor and Paging Activity, Hourly report







External interrupt rate/secThe number of external interrupts received per second.

SIGP interrupt rate/secThe number of external SIGPs (SIGnal Processor interrupts) issued persecond.

Simulation rate/secThe number of simulated instructions executed per second.

Diagnose rate/secThe number of IBM-supplied DIAGNOSE instructions executed persecond.

Figure 174. Example of a z/VM System Instruction Rate, Hourly report


z/VM System Instruction Counts, Hourly report:This report shows the distribution of different types of instruction.


Report IDVMPRF_S6







External interruptsThe number of external interrupts received.

Figure 175. Example of a z/VM System Instruction Counts, Hourly report


SIGP interruptsThe number of external SIGPs (SIGnal processor interrupts) issued.

SimulationsThe number of simulated instructions executed.

Diagnose instructionsThe number of IBM-supplied DIAGNOSE instructions executed.

z/VM System MIPS Capacity by LPAR, Daily report:This report shows the available MIPS and the daily average used for each availablelogical partition.


Report IDVMPRF_S7


SourceVMPRF_LPARS_DV

AttributesVM, VMPRF, Performance, MIPS, LPAR, CPU, Daily

VariablesFrom_date, To_date, Period_name, Serial_number



Period Name of the period. This is derived using the field Date from the record asparameter in the PERIOD function.

Serial NumberThe last 4 digits of the CPU serial number.

LPAR The name of the Logical Partition.

MIPS UsedThe average amount of MIPS used by LPAR.

MIPS AvailableTotal MIPS available to the LPAR. From MIPS_LPAR.

z/VM System MIPS Capacity by LPAR, DailyFrom date: ’2005-01-10’ To date: ’2005-01-10’

Serial Number: 0106

Serial MIPS MIPS Logical PhysicalDate Period Number LPAR Used Available Weight Processor Processor---------- ------ ------ ----- --------- ---------- ------ --------- ---------2005-01-10 NIGHT 0106 PROD1 0.223E+01 2.800E+02 100 4 10

PROD2 1.870E+01 5.600E+02 400 8 102005-01-10 PRIME 0106 PROD1 0.023E+01 2.800E+02 100 4 10

PROD2 1.512E+01 5.600E+02 400 8 10

Tivoli Decision Support for z/OS Report: VMPRF_S7

Figure 176. Example of a z/VM System MIPS Capacity by LPAR, Daily report


WeightResource Weight factor for the LPAR. From LPAR_WEIGHT.

Logical ProcessorsThe number of logical processors assigned to the LPAR. FromLOGICAL_PROCESSORS.

Physical ProcessorsThe number of physical processors available in the CP Complex. FromPHYSICAL_PROCESSORS.

Processor reportsThe processor reports show processor usage and distribution, and paging andinstruction rates.

z/VM Processor Usage Distribution, Hourly report:The report shows how each processor in the complex is used. For moreinformation on using this report, see the System Performance Feature Guide.


Report IDVMPRF_P1


SourceVMPRF_PROCESSOR_H

AttributesVM, VMPRF, CPU, Hourly, Performance, Detail





Processor addressThe address of the processor in the processor complex.

Busy time (%)The average percentage of time that each processor was busy.

Processor user (sec)The number of seconds charged to users for each processor. It does notinclude time that CP spends on behalf of users doing things such asinstruction simulation and page translation.

Processor emulation (sec)The number of seconds that each processor spent in emulation mode.

Processor system (sec)The number of seconds charged to the system for each processor. Itincludes time that CP spends on behalf of users doing such things asinstruction simulation and page translation. It also includes other systemwork, such as making scheduling decisions.

System wait (sec)The number of seconds that the processor had no work to do. It includesactive wait and enabled CPU wait.

z/VM Processor Busy Distribution, Hourly report:This report shows the distribution of processor work for each processor in thecomplex.

z/VM Processor Usage Distribution, HourlySystem: ’XYZVM ’ Period: (’PRIME’)

Date: ’2000-01-04’

Busy Processor Processor Processor SystemProcessor time user emulation system wait

Hour address (%) (sec) (sec) (sec) (sec)---- --------- ------- ---------- ---------- ---------- ----------

9 0 18.75 610 432 66 28231 29.55 765 370 298 21512 16.65 542 382 58 29103 13.86 453 322 46 30304 10.78 355 253 33 31605 8.82 294 220 23 3242

10 0 18.99 625 447 59 28031 34.26 939 464 295 18692 17.59 581 419 52 28673 14.58 484 351 41 29964 11.44 382 278 30 31285 9.26 311 232 22 3220

11 0 17.42 568 395 59 28651 34.82 955 463 298 18592 15.48 505 349 52 29483 12.65 416 289 40 30704 10.81 361 267 28 31465 7.87 263 193 20 3272

Tivoli Decision Support for z/OS Report: VMPRF_P1

Figure 177. Example of a z/VM Processor Usage Distribution, Hourly report



Report IDVMPRF_P2








Busy total (%)The average percentage of time that each processor was busy.

Busy user (%)The average percentage of time for each processor that is charged to users.It does not include time that CP spends on behalf of users doing thingssuch as instruction simulation and page translation.

z/VM Processor Busy Distribution, HourlySystem: ’XYZVM ’ Period: (’PRIME’)

Date: ’2000-01-04’

Busy Busy Busy BusyProcessor total user system emulation

Hour address (%) (%) (%) (%)---- --------- --------- --------- --------- ---------

13 0 17.45 15.77 1.68 11.101 30.44 22.22 8.23 10.872 15.79 14.30 1.49 10.113 13.09 11.93 1.17 8.514 12.40 11.61 0.79 9.235 8.46 7.89 0.57 6.02

14 0 15.44 13.81 1.63 9.181 31.32 23.11 8.22 11.332 14.02 12.58 1.44 8.403 11.08 10.00 1.08 6.704 9.40 8.70 0.70 6.545 11.51 10.97 0.54 9.39

15 0 17.54 15.81 1.73 11.081 31.28 22.99 8.29 10.962 15.18 13.66 1.52 9.293 12.12 10.93 1.19 7.354 9.95 9.14 0.81 6.565 9.75 9.16 0.59 7.35


Figure 178. Example of a z/VM Processor Busy Distribution, Hourly report


Busy system (%)The average percentage of time for each processor that is charged to thesystem. It includes time that CP spends on behalf of users doing suchthings as instruction simulation and page translation. It also includes othersystem work, such as making scheduling decisions.

Busy emulation (%)The average percentage of time for each processor that was spent inemulation mode. Calculated as: 100 * SUM(PROC_EMUL_SEC) /SUM(ELAPSED_SECONDS).

z/VM Processor Page and Spool Activity, Hourly report:The report shows DASD paging and spooling activity for each processor in thecomplex. For more information on using this report, refer to the System PerformanceFeature Guide.


Report IDVMPRF_P3



AttributesVM, VMPRF, Paging, Hourly, Performance, Detail






Page read (count)The number of DASD reads done for paging, for each processor in thecomplex.

Page write (count)The number of DASD writes done for paging, for each processor in thecomplex.

Spool read (count)The number of spool reads for each processor in the complex.

Spool write (count)The number of spool writes for each processor in the complex.

z/VM Processor Storage Activity, Hourly report:The report shows paging activity for each processor in the complex. For moreinformation on using this report, see the System Performance Feature Guide.


Report IDVMPRF_P4


z/VM Processor Page and Spool Activity, HourlySystem: ’XYZVM ’ Period: (’PRIME’)

Date: ’2000-01-04’

Page Page Spool SpoolProcessor read write read write

Hour address (count) (count) (count) (count)---- --------- ---------- ---------- ---------- ----------

13 0 2975 1 3 01 7099 12325 39765 246682 2440 0 5 03 2382 3 3 04 1694 3 1 05 1642 0 2 0

14 0 5406 0 1 01 10307 45918 40760 263252 3238 2 1 03 3189 1 1 04 2145 0 0 05 2861 2 0 0

15 0 3239 0 0 01 7167 17095 45342 297782 2581 1 0 03 2468 25 4 04 2194 2 0 05 2011 2 1 0


Figure 179. Example of a z/VM Processor Page and Spool Activity, Hourly report



AttributesVM, VMPRF, Storage, Hourly, Performance, Detail





Fastpath (%)The percentage of page-ins from expanded storage that were handled bythe page fault fastpath, for each processor in the complex.

Expanded paging /secThe rate of paging (page-ins and page-outs) to expanded storage, for eachprocessor in the complex. Calculated as: SUM(PAGES_READ_TO_MS +PAGES_WRIT_TO_ES) / SUM(ELAPSED_SECONDS).

Expanded page-ins /secThe rate of page-ins from expanded storage per second, for each processorin the complex. Calculated as: SUM(PAGES_READ_TO_MS) /SUM(ELAPSED_SECONDS).

z/VM Processor Storage Activity, HourlySystem: ’XYZVM ’ Period: (’PRIME’)

Date: ’2000-01-04’

Expanded Expanded Expanded DASD DASDProcessor Fastpath paging page-ins page-out page-ins page-out

Hour address (%) /sec /sec /sec /sec /sec---- --------- -------- -------- -------- -------- -------- --------

13 0 94.95 3.63 2.57 1.06 0.83 0.001 93.33 9.32 2.58 6.74 1.97 3.422 92.38 3.59 2.28 1.31 0.68 0.003 94.75 3.92 1.53 2.39 0.66 0.004 95.25 2.17 1.19 0.98 0.47 0.005 95.63 1.97 0.82 1.16 0.46 0.00

14 0 96.60 5.25 2.55 2.71 1.50 0.001 93.87 15.49 3.46 12.03 2.86 12.762 93.86 3.76 1.87 1.89 0.90 0.003 94.56 2.65 1.65 1.00 0.89 0.004 96.50 1.91 1.12 0.79 0.60 0.005 88.94 1.65 1.13 0.53 0.79 0.00

15 0 94.86 3.90 2.14 1.76 0.90 0.001 93.10 12.38 2.84 9.55 1.99 4.752 94.33 3.73 2.43 1.30 0.72 0.003 94.95 3.04 1.50 1.54 0.69 0.014 96.52 1.99 1.46 0.54 0.61 0.005 94.14 3.35 1.01 2.34 0.56 0.00


Figure 180. Example of a z/VM Processor Storage Activity, Hourly report


Expanded page-outs /secThe rate of page-outs to expanded storage per second, for each processorin the complex. Calculated as: SUM(PAGES_WRIT_TO_ES) /SUM(ELAPSED_SECONDS).

DASD page-ins /secThe rate of page-ins from DASD per second, for each processor in thecomplex. Calculated as: SUM(PAGE_READS) /SUM(ELAPSED_SECONDS).

DASD page-outs /secThe rate of page-outs to DASD per second, for each processor in thecomplex. Calculated as: SUM(PAGE_WRITES) /SUM(ELAPSED_SECONDS).

z/VM Processor Instruction Rate, Hourly report:The report shows the distribution of instructions for each processor in the complex.


Report IDVMPRF_P5









Busy total (%)The average percentage time that each processor is busy.

Diagnose instructions /secThe number of IBM-supplied DIAGNOSE instructions executed persecond. Calculated as: SUM(DIAG_INSTRUCTIONS) /SUM(ELAPSED_SECONDS).

Simulated instructions /secThe number of simulated instructions executed per second. Calculated as:SUM(SIMUL_INSTRUCTIONS) / SUM(ELAPSED_SECONDS).

SIGP interrupts /secThe number of external SIGPs (SIGnal Processor interrupts) issued persecond. Calculated as: SUM(SIGP_INTERRUPTS) /SUM(ELAPSED_SECONDS).

z/VM Processor Instruction Counts, Hourly report:This report shows the distribution of processor instructions for each processor inthe complex.


z/VM Processor Instruction Rate, HourlySystem: ’XYZVM ’ Period: (’PRIME’)

Date: ’2000-01-04’

Busy Diagnose Simulated SIGPProcessor total instructions instructions interrupts

Hour address (%) /sec /sec /sec---- --------- ---------- ------------ ------------ ------------

13 0 17.45 56.24 116.39 376.451 30.44 160.32 234.03 80.212 15.79 50.16 105.41 331.883 13.09 41.95 88.22 248.104 12.40 38.12 71.64 150.085 8.46 24.40 51.65 108.45

14 0 15.44 53.52 111.75 359.891 31.32 176.72 253.54 78.212 14.02 46.78 100.88 316.803 11.08 37.74 81.81 229.454 9.40 30.93 60.88 135.045 11.51 20.66 42.03 86.75

15 0 17.54 58.28 116.25 377.591 31.28 179.44 249.78 83.512 15.18 52.88 108.55 334.873 12.12 45.40 93.29 251.634 9.95 35.65 71.66 160.265 9.75 23.84 49.59 102.90


Figure 181. Example of a z/VM Processor Instruction Rate, Hourly report


Report IDVMPRF_P6








Busy total (%)The average percentage time that each processor is busy.

Diagnose instructionsThe number of IBM-supplied DIAGNOSE instructions executed.

Simulated instructionsThe number of simulated instructions executed.

SIGP interruptsThe number of external SIGPs (SIGnal Processor interrupts) issued.

z/VM Processor Instruction Counts, HourlySystem: ’XYZVM ’ Period: (’PRIME’)

Date: ’2000-01-04’

BusyProcessor total Diagnose Simulated SIGP

Hour address (%) instructions instructions interrupts---- --------- -------- ------------- ------------- -------------

13 0 17.45 202468 419013 13552371 30.44 577170 842510 2887732 15.79 180565 379489 11947763 13.09 151036 317610 8931624 12.40 137236 257910 5402865 8.46 87834 185933 390419

14 0 15.44 192674 402316 12955901 31.32 636179 912748 2815602 14.02 168397 363184 11404643 11.08 135851 294521 8260054 9.40 111341 219165 4861425 11.51 74364 151299 312299

15 0 17.54 209795 418485 13593351 31.28 645990 899211 3006372 15.18 190362 390798 12055423 12.12 163434 335862 905870


Figure 182. Example of a z/VM Processor Instruction Counts, Hourly report


User reportsThe user reports show processor resources used for each user and the pagingactivity for each user. The reports also show IUCV and VMCF activity for eachuser.

z/VM User Real and Virt Processor Usage, Monthly report:This report shows the processor resources used by each user, grouped by userclass. For more information on using this report, refer to the System PerformanceFeature Guide.


Report IDVMPRF_U1


SourceVMPRF_USER_M

AttributesVM, VMPRF, User, Monthly, Performance, CPU, Overview

VariablesPeriod_name_list, VM_system_ID, Month


User classThe user class.

User IDThe user ID.

Busy time (sec)The total processor time spent by the user, in seconds. This includes timethat the user spent doing work, and time that CP spent doing work onbehalf of the user.

z/VM User Real and Virt Processor Usage, MonthlySystem: ’XYZVM ’ Period: (’PRIME’)

Month: ’2000-01-01’

Busy Virtual Capture Active LogonUser User time time ratio time timeclass ID (sec) (sec) (%) (hours) (hours)-------- -------- --------- --------- --------- ---------- ----------ADMIN AABABLD 202 197 97.50 0.73 0.73

AASADMIN 5 3 64.10 0.25 0.25ADCOCK 37 34 91.70 0.07 0.25AHLGREN 15 12 78.86 0.45 0.50ALLMOND 29 26 90.28 0.12 0.25AMMERMAN 33 27 80.75 0.47 0.74ANDERSON 26 21 79.64 0.37 0.50AUTOLINK 555 544 97.98 6.98 7.98AVAIL 9 8 88.61 0.03 0.20

Tivoli Decision Support for z/OS Report: VMPRF_U1

Figure 183. Example of a z/VM User Real and Virt Processor Usage, Monthly report


Virtual time (sec)The virtual processor time spent by the user, in seconds. This is the timespent doing productive work, and does not include time that CP spends onbehalf of the user doing things such as instruction simulation and pagetranslation.

Capture ratio (%)The ratio between virtual and total processor usage, expressed as apercentage. Calculated as: 100 * SUM(CPU_VIRTUAL_SEC) /SUM(CPU_TOTAL_SEC).

Active time (hours)The number of hours that the user was active.

User active time is measured at each monitor interval. If a user was active,the user’s active time for that interval is the elapsed time of the monitorinterval. If a user was not active, the user’s active time for that interval iszero.

A user is considered active if either the user consumed some virtual CPUtime, or the user was not in the dormant list at the end of the monitorinterval. This includes users who are trying to do work, but are getting noservice.

Logon time (hours)The number of hours that the user was logged on.

z/VM User Paging and Spooling, Monthly report:This report shows the paging and spooling used by each user, grouped by userclass. For more information on using this report, see the System Performance FeatureGuide.


Report IDVMPRF_U2


SourceVMPRF_USER_M

AttributesVM, VMPRF, User, Monthly, Performance, Paging, Spooling, Overview





User IDThe user ID.

DASD page readsThe number of I/Os issued for page read requests.

DASD page writesThe number of I/Os issued for page write requests.

Spool readsThe number of I/Os issued for spool read requests.

Spool writesThe number of I/Os issued for spool write requests.

z/VM User IUCV and VMCF Counts, Monthly report:This report shows the IUCV and VMCF activity for each user, grouped by userclass.


Report IDVMPRF_U3


SourceVMPRF_USER_M

AttributesVM, VMPRF, User, Monthly, Performance, VMCF, IUCV, Overview


z/VM User Paging and Spooling, MonthlySystem: ’XYZVM ’ Period: (’PRIME’)

Month: ’2000-01-01’

DASD DASDUser User page page Spool Spoolclass ID reads writes reads writes-------- -------- ------------ ------------ ------------ ------------ADMIN AABABLD 12 0 0 0

AASADMIN 0 0 0 167ADCOCK 0 0 0 7AHLGREN 0 0 1229 499ALLMOND 1 0 237 32AMMERMAN 0 0 1686 32ANDERSON 0 0 5341 530AUTOLINK 176 23 1 6AVAIL 0 0 42 18BASSETT 20 0 86 36


Figure 184. Example of a z/VM User Paging and Spooling, Monthly report




User IDThe user ID.

IUCV receive (count)The number of successful IUCV data transfers to this virtual machine.

IUCV fail (count)The number of unsuccessful IUCV data transfers.

IUCV send (count)The number of successful IUCV data transfers from this virtual machine.

VMCF receive (count)The number of successful VMCF data transfers to this virtual machine.

VMCF fail (count)The number of unsuccessful VMCF data transfers.

VMCF send (count)The number of successful VMCF data transfers from this virtual machine.

z/VM Heaviest Users of the Processor, Monthly report:This report shows the processor resources, DASD I/O, and DASD paging used byeach user. For more information on using this report, see the System PerformanceFeature Guide.


Report IDVMPRF_U4


SourceVMPRF_USER_M

z/VM User IUCV and VMCF Counts, MonthlySystem: ’XYZVM ’ Period: (’PRIME’)

Month: ’2000-01-01’

IUCV IUCV IUCV VMCF VMCF VMCFUser User receive fail send receive fail sendclass ID (count) (count) (count) (count) (count) (count)-------- -------- ---------- ---------- ---------- ---------- ---------- ----------ADMIN AABABLD 0 0 0 0 0 0

AASADMIN 0 0 0 0 0 0ADCOCK 0 0 0 0 0 0AHLGREN 0 0 0 0 0 0ALLMOND 0 0 0 0 0 0AMMERMAN 0 0 0 0 0 0ANDERSON 22 0 11 0 0 0AUTOLINK 7152 0 7152 70 0 0AVAIL 0 0 0 0 0 0BASSETT 0 0 0 0 0 0BOOS 0 0 0 0 0 0


Figure 185. Example of a z/VM User IUCV and VMCF Counts, Monthly report





User IDThe user ID.

Processor usage (%)The processor busy time, as a percentage of the time that the user waslogged on. Calculated as: 100 * SUM(CPU_TOTAL_SEC) /SUM(LOGGED_SEC).



DASD IO (count)The number of I/O requests that this virtual machine issued to DASDdevices.

z/VM Heaviest Users of the Processor, MonthlySystem: ’XYZVM ’ Period: (’PRIME’)

Month: ’2000-01-01’

Processor Busy Virtual DASD DASDUser usage time time IO pagingID (%) (sec) (sec) (count) /sec-------- --------- --------- --------- --------- ----------GARNER 38.29 689 667 37067 0.02CPDOCS 33.21 359 351 13151 0.00PATTONW 12.16 95 73 21274 0.00LAING 11.58 28 27 597 0.00CONSORTI 11.52 623 588 29524 0.05LAPIDUS 10.31 17 9 9086 0.00VTAM 8.06 2888 641 4 0.01AABABLD 7.64 202 197 7087 0.00HARRISL 6.86 58 56 1008 0.00NETVIEW 4.56 1635 646 1638426 0.01DIRMAINT 4.39 472 314 254950 0.00MVSNM1 4.33 3101 1774 89655 0.12TEMP404 4.30 75 44 6583 0.03TRKING 4.23 305 270 32959 0.01NEADE 4.22 76 74 3046 0.00STAMMER 4.20 605 593 3832 0.00ADCOCK 4.10 37 34 1581 0.00NENAA 3.95 36 30 3354 0.02MVSNM2 3.95 2827 1536 28349 0.08SMSSYS 3.88 1390 1221 65521 0.64


Figure 186. Example of a z/VM Heaviest Users of the Processor, Monthly report


DASD paging /secThe number of I/Os issued for page read and write requests, per secondthat this user was logged on. Calculated as: SUM(PAGE_READS +PAGE_WRITES) / SUM(LOGGED_SEC).

z/VM Heaviest Users of DASD, Monthly report:This report shows the processor resource usage, DASD I/O, DASD rate, and DASDpaging for each user.


Report IDVMPRF_U5


SourceVMPRF_USER_M

AttributesVM, VMPRF, User, Monthly, Performance, DASD, Overview



User IDThe user ID.

z/VM Heaviest Users of DASD, MonthlySystem: ’XYZVM ’ Period: (’PRIME’)

Month: ’2000-01-01’

DASDDASD DASD Busy Virtual paging

User IO rate time time rateID (count) /sec (sec) (sec) /sec-------- ----------- ----------- ----------- ----------- -----------NETVIEW 1638426 45.74 1635.1 646.4 0.01TOOLS 268038 8.56 651.2 358.5 0.02DIRMAINT 254950 23.74 471.9 313.9 0.00MVSNM1 89655 1.25 3101.4 1774.1 0.12EQUAL02 82177 4.82 180.4 108.9 0.08SMSSYS 65521 1.83 1389.7 1221.0 0.64GARNER 37067 20.59 689.3 667.4 0.02EUPO 35346 9.98 44.7 11.2 0.01TRKING 32959 4.58 304.7 269.5 0.01GOBEILLE 30215 1.60 346.9 320.2 0.01CONSORTI 29524 5.47 622.5 587.6 0.05MVSNM2 28349 0.40 2827.0 1536.2 0.08PHILZ 24333 2.27 265.9 245.1 0.03EQFAMOSO 23274 8.62 34.1 25.3 0.10PATTONW 21274 27.27 94.9 73.4 0.00MIDDLET 20643 4.59 100.7 80.1 0.03DORN 18057 2.53 159.3 143.7 0.00AUTOLINK 16897 0.59 555.1 543.9 0.01COLEY 16833 2.36 174.7 137.3 0.00


Figure 187. Example of a VMPRF Heaviest Users of DASD, Monthly report


DASD IO (count)The number of I/O requests that this virtual machine issued to DASDdevices.

DASD rate /secThe number of I/O requests that this virtual machine issued to DASDdevices, per second that this user was logged on. Calculated as:SUM(DASD_IO) / SUM(LOGGED_SEC).



DASD paging rate /secThe number of I/Os issued for page read and write requests, per secondthat this user was logged on. Calculated as: SUM(PAGE_READS +PAGE_WRITES) / SUM(LOGGED_SEC).

z/VM Heaviest Users of Paging, Monthly report:This report shows the processor resources usage and paging activities for eachuser.


Report IDVMPRF_U6


SourceVMPRF_USER_M

AttributesVM, VMPRF, User, Monthly, Performance, Paging, Overview




User IDThe user ID.

DASD paging /secThe number of I/Os issued for page read and write requests, per secondthat this user was logged on. Calculated as: SUM(PAGE_READS +PAGE_WRITES) / SUM(LOGGED_SEC).

Expanded paging /secThe number of pages written from main storage to expanded storage, andread from expanded storage to main storage, per second that this user waslogged on. Calculated as: SUM(PAGES_READ_TO_MS +PAGES_WRIT_TO_ES) / SUM(LOGGED_SEC).

DASD page-in (count)The number of I/Os issued for page read requests.

DASD page-out (count)The number of I/Os issued for page write requests.

Busy total (sec)The total processor time spent by the user, in seconds. This includes timethat the user spent doing work, and time that CP spent doing work onbehalf of the user.

Virtual processor (sec)The virtual processor time spent by the user, in seconds. This is the timespent doing productive work, and does not include time that CP spends onbehalf of the user doing things such as instruction simulation and pagetranslation.

z/VM Processor Usage by User Class, Monthly report:This report shows the processor usage, grouped by user class.

z/VM Heaviest Users of Paging, MonthlySystem: ’XYZVM ’ Period: (’PRIME’)

Month: ’2000-01-01’

DASD Expanded DASD DASD Busy VirtualUser paging paging page-in page-out total processorID /sec /sec (count) (count) (sec) (sec)-------- -------- -------- ---------- ---------- ---------- ----------VMSP2SUP 1.45 2.24 500 5947 61 32SMSSYS 0.64 1.57 10770 12009 1390 1221INFOUPDT 0.28 0.00 255 0 14 11EQJEWS 0.17 0.00 150 0 4 3MVSCAC 0.17 0.47 2777 3179 606 496EQNEIGHL 0.16 0.00 145 0 7 5RDMORSE 0.13 0.32 349 0 51 47MVSNM1 0.12 1.69 7080 1606 3101 1774EQFAMOSO 0.10 0.12 208 60 34 25PETERSON 0.09 0.01 78 0 9 5EQUAL02 0.08 0.05 54 1389 180 109CJEWS 0.08 0.08 283 0 35 32MVSNM2 0.08 0.48 2611 2862 2827 1536RTMTSTI 0.07 0.09 124 0 12 7SPRINGS 0.07 0.08 61 0 8 7GLASS 0.07 0.01 117 0 13 11CONSORTI 0.05 0.49 130 130 623 588


Figure 188. Example of a z/VM Heaviest Users of Paging, Monthly report



Report IDVMPRF_U7


SourceVMPRF_USER_M





Busy time (sec)The total processor time spent by this user class, in seconds. This includestime spent doing work, and time that CP spent doing work on behalf ofthe users.

Virtual time (sec)The virtual processor time spent by this user class, in seconds. This is thetime spent doing productive work, and does not include time that CPspends on behalf of the users doing things such as instruction simulationand page translation.

Capture ratio (%)The ratio between virtual and total processor usage, expressed as apercentage. Calculated as: 100 * SUM(CPU_VIRTUAL_SEC) /SUM(CPU_TOTAL_SEC).

Active time (hours)The number of hours that the users in this class were active in the system.An active user is one who consumes processor time, or who is not in thedormant list at the end of the monitoring interval.

Logon time (hours)The number of hours that the users in this class were logged on.

z/VM Paging by User Class, Monthly report:This report shows the paging and spooling activities by user class.

z/VM Processor Usage by User Class, MonthlySystem: ’XYZVM ’ Period: (’PRIME’)

Month: ’2000-01-01’

Busy Virtual Capture Active LogonUser time time ratio time timeclass (sec) (sec) (%) (hours) (hours)-------- ----------- ----------- ----------- ----------- -----------ADMIN 25469 16746 65.75 214.46 246.67


Figure 189. Example of a z/VM Processor Usage by User Class, Monthly report



Report IDVMPRF_U8


SourceVMPRF_USER_M

AttributesVM, VMPRF, User, Monthly, Performance, Paging, Spooling, Overview




DASD page-in (count)The number of I/Os issued for page read requests.

DASD page-out (count)The number of I/Os issued for page write requests.

Spool read (count)The number of I/Os issued for spool read requests.

Spool write (count)The number of I/Os issued for spool write requests.

z/VM IUCV and VMCF Usage by User Class, Monthly report:This report shows the IUCV and VMCF activity by user class. For moreinformation on using this report, refer to the System Performance Feature Guide.


Report IDVMPRF_U9


SourceVMPRF_USER_M

z/VM Paging by User Class, MonthlySystem: ’XYZVM ’ Period: (’PRIME’)

Month: ’2000-01-01’

DASD DASD Spool SpoolUser page-in page-out read writeclass (count) (count) (count) (count)-------- ----------- ----------- ----------- -----------ADMIN 30062 30173 276340 205425


Figure 190. Example of a z/VM Paging by User Class, Monthly report


AttributesVM, VMPRF, User, Monthly, Performance, IUCV, VMCF, Overview




IUCV receive (count)The number of successful IUCV data transfers to virtual machines in theuser class.

IUCV fail (count)The number of unsuccessful IUCV data transfers.

IUCV send (count)The number of successful IUCV data transfers from virtual machines in theuser class.

VMCF receive (count)The number of successful VMCF data transfers to virtual machines in theuser class.

VMCF fail (count)The number of unsuccessful VMCF data transfers.

VMCF send (count)The number of successful VMCF data transfers from virtual machines inthe user class.

DASD reportsThe VMPRF DASD reports show information on the DASD volumes. Thisinformation includes the longest DASD response times and the lowest and highestactivity based on the number of start subchannel and resume subchannelinstruction executions.

z/VM Most-Used DASD by Start Subchannel Rate report:This report shows the DASD volumes having the most start subchannel andresume subchannel executions per second.

Use the Rows variable to set the number of DASD volumes in the report.


z/VM IUCV and VMCF Usage by User Class, MonthlySystem: ’XYZVM ’ Period: (’PRIME’)

Month: ’2000-01-01’

IUCV IUCV IUCV VMCF VMCF VMCFUser receive fail send receive fail sendclass (count) (count) (count) (count) (count) (count)-------- ---------- ---------- ---------- ---------- ---------- ----------ADMIN 671005 35 711225 2049 0 1003


Figure 191. Example of a z/VM IUCV and VMCF Usage by User Class, Monthly report


Report IDVMPRF_D1


SourceVMPRF_DASD_H

AttributesVM, VMPRF, DASD, Performance, SSCHrate

VariablesDate, Period_name_list, VM_system_ID, From_time, To_time, Rows


VOLSERThe DASD volume serial number.

SSCH+RSCH (count)The number of start and resume subchannel instructions.

SSCH queued (count)The number of start subchannel requests queued, excluding the activerequest.

SSCHrate /secondThe average number of start and resume subchannel instructions eachsecond the device was online. Calculated as: SUM(SSCH_AND_RSCH) /SUM(ONLINE_SEC).

Response time (msec)The average time to complete a DASD I/O operation. This is the time inthe queue added to the service time. Calculated as: AVG(1000 *SSCH_QUEUED / HF_SAMPLES * ELAPSED_SEC / SSCH_AND_RSCH +SERVICE_MSEC).

Service time (msec)The average time between a start subchannel being passed to the channelpath and the completion of the input/output.

z/VM Slowest DASD by Response Time report:

z/VM Most-Used DASD by Start Subchannel RateSystem: ’XYZVM ’ Period: (’PRIME’)

Date: ’1999-12-29’Time: ’08.00.00’ to ’20.00.00’

SSCH Response ServiceSSCH+RSCH queued SSCHrate time time

VOLSER (count) (count) /second (msec) (msec)------ --------------- ----------- -------- -------- -------VMX4A6 216513 0 21.9 18.2 18.2MDSK21 682572 29 21.7 14.8 14.7VMX791 153379 0 17.0 16.3 16.3VMX4AF 104235 0 16.5 18.6 18.6VMX4AA 155549 0 15.7 19.3 19.3VMX790 153731 0 15.5 16.4 16.4VMX4AD 223486 0 14.7 21.8 21.8

Tivoli Decision Support for z/OS Report VMPRF_D1

Figure 192. Example of a z/VM Most-Used DASD by Start Subchannel Rate report


This report shows the DASD volumes having the longest response time.



Report IDVMPRF_D2


SourceVMPRF_DASD_H

AttributesVM, VMPRF, DASD, Performance, Response, Worst







Response time (msec)The average time to complete a DASD I/O operation. This is the time in

z/VM Slowest DASD by Response TimeSystem: ’XYZVM ’ Period: (’PRIME’)

Date: ’2003-12-28’Time: ’08.00.00’ to ’20.00.00’


VOLSER (count) (count) /second (msec) (msec)------ --------------- ----------- -------- -------- -------XP2MSC 2525 0 0.4 53.2 53.2VMX24A 163187 0 12.1 50.2 50.2VMX240 101863 132 4.7 48.2 47.0VMPG08 49 0 0.1 46.4 46.4VMX25B 22582 17 1.6 42.4 41.6XP2MSA 11863 2 0.7 41.8 41.5VMX4A2 4240 3 0.4 40.9 40.2VMX24B 18583 0 1.9 40.2 40.2CACAT3 2825 0 0.3 34.3 34.3CP8001 4170 0 0.4 33.7 33.7


Figure 193. Example of a z/VM Slowest DASD by Response Time report


the queue added to the service time. Calculated as: AVG(1000 *SSCH_QUEUED / HF_SAMPLES * ELAPSED_SEC / SSCH_AND_RSCH +SERVICE_MSEC).

Service time (msec)The average time between a start subchannel being passed to the channelpath and the completion of the I/O.

z/VM DASD With Longest Queues report:This report shows the DASD volumes having the most start-subchannelinstructions queued. Use the Rows variable to set the number of DASD volumes inthe report. For more information on using this report, refer to the SystemPerformance Feature Guide.


Report IDVMPRF_D3


SourceVMPRF_DASD_H

AttributesVM, VMPRF, DASD, Performance, Requests, Worst





z/VM DASD With Longest QueuesSystem: ’XYZVM ’ Period: (’PRIME’)

Date: ’2003-12-28’Time: ’08.00.00’ to ’20.00.00’


VOLSER (count) (count) /second (msec) (msec)------ --------------- ----------- -------- -------- -------VMX240 101863 132 4.7 48.2 47.0MNK7A9 15593 83 0.6 22.3 18.3EXPSUP 62379 58 2.3 20.7 19.6MDSK21 652830 34 20.8 14.8 14.7VMXA2R 55907 31 1.8 15.8 14.7EQL002 80128 25 2.5 17.8 17.2MNK7AA 19435 25 0.7 15.0 14.0VMX25B 22582 17 1.6 42.4 41.6EQL001 102132 11 3.3 17.2 17.0MDSK15 19869 7 0.7 22.2 21.7


Figure 194. Example of a z/VM DASD With Longest Queues report




Response time (msec)The average time to complete a DASD input/output operation. This is thetime in the queue added to the service time. Calculated as: AVG(1000 *SSCH_QUEUED / HF_SAMPLES * ELAPSED_SEC / SSCH_AND_RSCH +SERVICE_MSEC).


z/VM Least Used or not Used DASD Devices report:This report shows the DASD volumes having the lowest activity based on thenumber of start subchannel and resume subchannel instructions executed. Use theRows variable to set the number of DASD volumes in the report. For moreinformation on using this report, see the System Performance Feature Guide.


Report IDVMPRF_D4


SourceVMPRF_DASD_H

AttributesVM, VMPRF, DASD, Performance, Worst










z/VM Least Used DASD Devices report:This report shows the DASD volumes having the lowest activity based on thenumber of start subchannel and resume subchannel instructions executed. Volumeswith no subchannel instructions executed are excluded. The devices without anysubchannel instructions are excluded.



Report IDVMPRF_D5


z/VM Least Used or not Used DASD DevicesSystem: ’XYZVM ’ Period: (’PRIME’)

Date: ’2003-12-28’Time: ’08.00.00’ to ’09.00.00’


VOLSER (count) (count) /second (msec) (msec)------ --------------- ----------- -------- -------- -------VMX4AA 28 0 0.0 0.8 0.8VMX4AB 28 0 0.0 0.8 0.8VMX4A1 28 0 0.0 0.8 0.8VMX4A3 28 0 0.0 0.8 0.8VMX4A9 28 0 0.0 0.8 0.8MDSK42 30 0 0.0 20.0 20.0MDSK46 34 0 0.0 16.8 16.8MDSK28 35 0 0.0 19.1 19.1


Figure 195. Example of a z/VM Least Used or not Used DASD Devices report


SourceVMPRF_DASD_H

AttributesVM, VMPRF, DASD, Performance, Worst

VariablesDate, Period_name-list, VM_system_ID, From_time, To_time, Rows








Configuration reportsThe configuration reports show VM system levels, storage configuration data, andthe date of the last IPL.

z/VM Configuration, Level and Storage, Daily report:

z/VM Least Used DASD DevicesSystem: ’XYZVM ’ Period: (’PRIME’)

Date: ’2003-12-28’Time: ’08.00.00’ to ’17.00.00’


VOLSER (count) (count) /second (msec) (msec)------ --------------- ----------- -------- -------- -------VMX4AA 28 0 0.0 0.8 0.8VMX4A3 28 0 0.0 0.8 0.8MDSK46 34 0 0.0 16.8 16.8MDSK05 44 0 0.0 22.7 22.7MDSK47 46 0 0.1 21.3 21.3VMPG08 49 0 0.1 46.4 46.4VMX4AC 58 0 0.0 0.8 0.8VMX4A4 58 0 0.0 0.8 0.8


Figure 196. Example of a z/VM Least Used DASD Devices report


This report shows the z/VM system level and storage configuration. The z/VMmonitor writes this data each time it is started.


Report IDVMPRF_C1


SourceVMPRF_CONFIG_T

AttributesVM, VMPRF, Configuration, Daily, Detail





VM levelThe version, release number, and service level of the VM system. This is aconcatenation of VM_VERSION, VM_RELEASE, andVM_SERVICE_LEVEL, separated by periods.

Storage real (MB)The size of real storage calculated during system initialization. Calculatedas: STORAGE_REAL / 1048576.

Storage sysgen (MB)The storage size of the real machine as defined during SYSGEN. Calculatedas: STORAGE_SYSGEN / 1048576.

Storage V=R (MB)The size of the virtual-equals-real (V=R) area excluding virtual-equals-real

z/VM VM Configuration, Level and Storage, DailySystem: ’XYZVM ’

Date: ’2002-12-28’ to ’2003-01-08’

<--------------- Storage ---------------->VM real sysgen V=R expanded

Date Time level (MB) (MB) (MB) (blocks)---------- -------- ---------- --------- --------- -------- ----------2002-12-28 08.00.11 21.00.0215 331.0 331.0 0.0 4075522002-12-29 08.00.12 21.00.0215 331.0 331.0 0.0 4075522002-12-30 08.00.12 21.00.0215 331.0 331.0 0.0 4075522002-12-30 17.39.14 21.00.0215 331.0 331.0 0.0 4075522003-01-01 08.00.11 21.00.0215 331.0 331.0 0.0 4075522003-01-04 08.00.12 21.00.0215 331.0 331.0 0.0 4075522003-01-04 16.31.14 21.00.0215 331.0 331.0 0.0 4075522003-01-05 08.00.12 21.00.0215 331.0 331.0 0.0 4075522003-01-07 08.00.11 21.00.0215 331.0 331.0 0.0 4075522003-01-08 08.00.12 21.00.0215 331.0 331.0 0.0 407552

Tivoli Decision Support for z/OS Report VMPRF_C1

Figure 197. Example of a z/VM Configuration, Level and Storage, Daily report


reserved free storage. This is set to the largest V=R or V=F address. It is setto 0 when there is no preferred guest defined or when thevirtual-equals-real area is unlocked after all preferred guests have loggedoff. Calculated as: VR_SIZE / 1048576.

Storage expanded (blocks)The number of expanded storage blocks installed.

z/VM Configuration, Level and IPL, Daily report:This report shows the VM system level, last IPL, and termination dates, and theabend code from the last termination. The VM monitor writes this data each time itis started.


Report IDVMPRF_C2


SourceVMPRF_CONFIG_T

AttributesVM, VMPRF, Configuration, Daily, Detail





VM levelThe version, release number, and service level of the VM system. This is aconcatenation of VM_VERSION, VM_RELEASE, andVM_SERVICE_LEVEL, separated by periods.

z/VM Configuration, Level and IPL, DailySystem: ’XYZVM ’

Date: ’2000-12-28’ to ’2001-01-08’

<------- Date -------->VM last last Abend

Date Time level IPL termination code---------- -------- ---------- ---------- ----------- --------2000-12-28 08.00.11 21.00.0215 2000-12-172000-12-29 08.00.12 21.00.0215 2000-12-172000-12-30 08.00.12 21.00.0215 2000-12-172000-12-30 17.39.14 21.00.0215 2000-12-172001-01-01 08.00.11 21.00.0215 2000-12-172001-01-04 08.00.12 21.00.0215 2000-12-172001-01-04 16.31.14 21.00.0215 2000-12-172001-01-05 08.00.12 21.00.0215 2000-12-172001-01-07 08.00.11 21.00.0215 2001-01-072001-01-08 08.00.12 21.00.0215 2001-01-07

Tivoli Decision Support for z/OS Report VMPRF_C2

Figure 198. Example of a z/VM Configuration, Level and IPL, Daily report


Date last IPLThe date of the last IPL that was performed.

Date last terminationThe date of the last termination. When there is no termination information,the field is blank.

Abend codeThe abend code at the last termination. When there is no terminationinformation, the field is blank.

Linux on zSeries componentCustomizationv Overviewv Making input data available

– Step 1: Checking zLinux requirements– Step 2: Transferring Tivoli Decision Support for z/OS feature code to zLinux– Step 3: Creating log files– Step 4 (optional): Defining the receiver of Linux on zSeries component log

data files– Step 5: Customizing the drl.cfg parameter file– Step 6: Starting the drlperfd daemon agent and related programs

v Modifying DRLJCOLL

Data flow


– ZLINUX_CONFIG_HW_D– ZLINUX_CONFIG_SW_D– ZLINUX_CPU_H,_D,_M– ZLINUX_CPUTIME_D– ZLINUX_DISK_INFO_D,_M– ZLINUX_DISKIO_H,_D,_M– ZLINUX_FILESYS_H– ZLINUX_FILESYS_D, _M– ZLINUX_MEM_H– ZLINUX_MEM_D, _M– ZLINUX_PAGING_H,_D,_M– ZLINUX_PROCESS_H– ZLINUX_PROCESS_D, _M– ZLINUX_USERS_H– ZLINUX_USERS _D, _M– ZLINUX_USR_CMD_D,_M– ZLINUX_WTMP_INFO_D,_M

v Lookup tables– ZLINUX_CONNECT_TYP– ZLINUX_NODE_NAME


Reportsv zLinux Filesystem Usage Daily Trendv zLinux Processes Daily Breakdownv zLinux Acct Resource by User, Daily Overviewv zLinux Acct User Connect Info, Daily Overviewv zLinux Perf Statistics All Systems, Daily Overviewv zLinux Perf Disk I/O for System, Daily Overviewv zLinux Hardware Configuration, Daily Overviewv zLinux Software Configuration, Daily Overview

CustomizationThis chapter describes the steps to customize the Linux on zSeries® component:v Overview.v Making input data available.v Modifying DRLJCOLL.

OverviewData for the Linux on zSeries component is collected by scripts and the drlperfddaemon, and combined into a single log file by the drlgather script.

Figure 199 describes how information is gathered for the Linux on zSeriescomponent.

1. The scripts (scriptdf, scriptpi, scriptww, and scriptto) collect data which isstored in /var/tds/logs/lnxlog.txt. These scripts are scheduled by the cronscheduler.

2. The drlperfd daemon collects data continually (once activated) and writes towork files tagged by date in the /var/tds directory at the end of the processingday.

3. The drlgather process combines the data produced by the scripts and thedrlperfd daemon to create the log that is transferred to Tivoli Decision Supportfor z/OS.

4. The merged log is then transferred to Tivoli Decision Support for z/OS forcollection in the Linux on zSeries component.

The scripts and drlgather process are run under the control of the cron scheduler.It is recommended that the scripts be scheduled to run every hour between 08:00a.m. and 08:00 p.m and the drlgather process at 02:00 a.m. The drlgather scriptmerges the previous day’s data from drlperfd with the /var/tds/logs/lnxlog.txtfile.

For more information about how to set up the cron, see Step 3: Creating log files.

Figure 199. Linux on zSeries overview


Making input data availableThe following sections describe the steps you must perform to make Linux onzSeries component data available.

Installing Linux:

For information about installing Linux (as opposed to zLinux that is contained inthis chapter), see "Installing the Linux Performance component on your Linuxnodes" in the Tivoli Decision Support for z/OS Distributed Systems Performance FeatureGuide and Reference.

Step 1: Checking zLinux requirements:This section describes zLinux requirements:v Disk space requirementsv Software requirements

Disk space requirements

You need the following approximate disk space on each zLinux node:

Table 21. Disk space requirements on each zLinux node

Installation task Disk space (approximate)

Programs in the file system /usr/lpp/tds 1 MB

Work files for logs gathering in the file system /var/tds (approximate calculation basedon normal work of 10 users)

100 MB

Software requirements

The Linux on zSeries component requires one of the following distributions:v RHEL 4 for zSeries, or later.v SUSE 10.1 for zSeries, or later.

Note: Ensure that the SYSSTAT and PROCINFO packages are installed on yourzLinux system.

Step 2: Transferring Tivoli Decision Support for z/OS feature code to zLinux:

About this task

The Linux on zSeries component programs are distributed in theDRLxxx.SDLRWS(DRLLNSC) library member.

Download the drllnsc file as follows:

Procedure

1. Log in as root user on your zLinux node.2. Check that the /usr/lpp directory exists; if not, create it by entering the

command mkdir /usr/lpp.3. Enter the commands:

mkdir /usr/lpp/tdscd /usr/lpp/tds

4. Start an ftp session to your z/OS host and receive the file from the z/OS userwhere you installed Tivoli Decision Support for z/OS.


Note:

a. You are required to specify the IP name or IP address of the z/OS systemwhere Tivoli Decision Support for z/OS is installed and where the tar fileis located.

b. You are required to specify the TSO user ID that has read access to the tarfile.

c. Perform the ftp as binary. It is recommended that the file is downloaded asdrllnsc.tar

5. After receiving the drllnsc file, unpack the Linux on zSeries componentprograms.To do this, run the following command from the /usr/lpp/tar directory:tar -xvf drllnsc.tar

Three sub directories are created:v binv etcv libOptionally, you can remove the tar file with the rm command.

6. Create the working directories /var/tds and /var/tds/logs by running thedrlinstall program that is located in the /usr/lpp/tds/bin directory.This program also creates the required symbolic links to programs andlibraries.

7. To verify that the new directory has been created, enter:ls /var/tds

To verify that the symbolic links have been created, enter:ls -l /usr/bin/drl* /usr/bin/zcc*

8. The drl.cfg parameter file is stored in the /usr/lpp/tds/etc directory.The drlinstall program automatically copies the parameter file to/etc/drl.cfg.

9. Optional: To gather accounting information data, start your zLinux Accountingprocess by entering:accton /var/account/pacct

Step 3: Creating log files:To gather log files, include the drlgather program in the cron file of the zLinuxenvironment. You can schedule the creation of the log files by entering thefollowing command:/usr/lpp/tds/bin/drlgather -c conf_day data_type

where:

conf_dayIs used only for configuration log files. Specifies the day the configurationlog files are to be created. By default, the creation of these files occurs onthe first day of each month. In the following example, the log files will becreated on day 5, 10, and 13 of the month:-c"5 10 13"

data_typeSpecifies the type of data to be gathered. It can be one or more of thefollowing:

perf Performance data


acct Accounting data from pacct and wtmp files

conf Configuration data

All Performance, accounting, and configuration data

Edit the cron file by entering:crontab -e

In the cron file, insert the following lines:# Run 0 minutes after 8 am each hour# every working day from 8 am to 8 pm00 8-20/1 * * 1-5 /usr/lpp/tds/bin/scriptpi00 8-20/1 * * 1-5 /usr/lpp/tds/bin/scriptdf00 8-20/1 * * 1-5 /usr/lpp/tds/bin/scriptww00 8-20/1 * * 1-5 /usr/lpp/tds/bin/scriptto

Each line describes the name of the script to be run and when to run it. Thisinformation will be managed by the drlgather program. In detail:

00 The script is started 0 minutes after the hour.

8-20/1 The script is run every hour from 8 a.m. to 8 p.m.

* * The script is run every day and every month

1-5 The script is run every day and every month, from Monday to Friday only.

The following example shows how to automatically schedule the creation of logdata files for all data types:0 2 * * * /usr/lpp/tds/bin/drlgather -c1 perf acct conf

The following example shows how to automatically schedule the creation of logdata files for performance data only:0 2 * * * /usr/lpp/tds/bin/drlgather -c1 perf

An example of a cron setting can be found in /usr/lpp/tds/etc/drlcron.

To display the settings that you specified, enter:crontab -l

Step 4 (optional): Defining the receiver of Linux on zSeries component log datafiles:

1. To automatically send the log data files to the z/OS system, in the .netrc filelocated in the home directory of root user, insert the following line:machine zos_system login zos_userid password pwd

where:

zos_systemThe z/OS system where the files are to be sent.

zos_useridThe z/OS TSO user ID.

pwd The password associated with the z/OS TSO user ID specified.2. After editing the .netrc file, check that the file has private read/write

permission only. If not, change the permission as follows:chmod 600 .netrc


3. In the drlgather program, include the following statement to perform anautomatic ftp. ftp uses the .netrc file when performing the file transfer, eachnight.0 2 * * * /usr/lpp/tds/bin/drlgather -c1 perf acct conf ftp

4. Use the command ping -c5 zos_system to check that the communication withthe z/OS system is up. If the command fails, verify that the settings for theTCP/IP are correct.

Step 5: Customizing the drl.cfg parameter file:Edit the /etc/drl.cfg parameter file to change the default values supplied by theLinux on zSeries component to those for the installation. Some of these parameterscannot be customized, as indicated in the parameter file. The following tableexplains the parameters that you can customize.

Table 22. Parameters that you can customize in drl.cfg

Parameter Description Example

tdsHost Host name (TCP node name or TCP/IP address) of the z/OS hostthat is to receive the log data file. Optional.

yourzos.yourdomain.com

tdsPrefix z/OS log data set prefix. TDS171

sysName The name of the system where the zLinux environment is located. SYS1

site z/OS data set characteristics of the data file sent by using ftp. bl=10204 lr=255 rec=vb cypri=1 sec=5

maxRetries When the log data file is to be automatically transferred to z/OS,the communication might be broken for some reason. If this is thecase, the drlsend program re-attempts the file transfer of the logdata file for a number of times given by this parameter. Using thedefault value for maxRetries, and with the retInterval set at itsdefault of 30 minutes, the file transfer retry period covers 1 day.Optional.

48

retInterval Interval, in minutes, between the ftp retries. Optional. 30

perfInterval The drlperfd program issues the vmstat and iostat commands,which contain the perfInterval value as the interval parameter. Thedefault interval between samples is 60 seconds.

60

perfCount The drlperfd program samples the vmstat and iostat data. Thisdata is temporary saved in the file /var/tds/node_name.perf.workand, finally, in the file /var/tds/node_name.perf.dyymmdd.1. Thedefault is 10 times.

10

diskInterval The drlperfd program issues the df command and saves temporaryfile space usage in the file /var/tds/node_name.disk.work and,finally, in the file /var/tds/node_name.disk.dyymmdd.1. The defaultinterval between samples is 10 minutes.

10

iostatPrefix The prefix for the iostat command. The actual command is builtfrom the prefix, arguments and postfix. For instance, using theexamples in this table results in the command: iostat -dkx 60 10 |awk 'NF=12{print \$1" "\$6" "\$7" " \$12}NF!=12{print}' Thenumbers to use are the columns with Device, rKB/s, wKB/s and%util from the iostat -dkx 2 2 command.

iostat -dkx

iostatPostfix The iostat postfix. | awk 'NF==14{print \$1""\$8" "\$9" " \$14}NF!=14{print}'

vmstatPrefix The vmstat prefix. Built in the same manner as iostat. The numbersto use are the columns with free, si, so, us and sy from the vmstatcommand.

vmstat


Table 22. Parameters that you can customize in drl.cfg (continued)

Parameter Description Example

vmstatPostfix The vmstat postfix. | awk 'NF=16{print \$4" "\$7""\$8" " \$13" "\$14}NF!=14{print}'

Step 6: Starting the drlperfd daemon agent and related programs:

About this task

The processes that collect performance and disk space data during the day areinitiated by the drlperfd program. You now perform the following steps:

Procedure

1. Start the drlperfd daemon, which gathers performance and disk space data, byrunning the drlactperfd program from the command line.If you run this program with no parameters, both the performance and diskdata are collected. To collect either disk or performance data, enter thecommand:

For disk and volume space informationdrlactperfd disk

For performance informationdrlactperfd perf

2. From the command line, run the drlpsperfd command to display the status ofthe activated processes:drlpsperfdThe following drlperfd processes are running

USER COMMAND PID PPIDroot drlperfd 10200 1root drlperfd 11735 10200root drlvmstat 17153 11735root drliostat 19970 11735

The performance and disk data is written in the following files, located in/var/tds:

Working files:iostat.tmp

vmstat.tmp

node_name.perf.work

node_name.disk.work

node_name.perfio.work

node_name.perfvm.work

Final log data file:node_name.tds.dyymmdd.1

The file node_name.drlperfd.errorlog contains possible error messages. Thisfile remains empty if the drlperfd daemon runs successfully.The file node_name.drlperfd.log contains general information messages for theuser.

3. Stop the drlperfd daemon by running the drldeactperfd program.


If you restart the drlperfd daemon without removing the working filespreviously gathered, data is appended to the same files.

Modifying DRLJCOLLBefore running the Tivoli Decision Support for z/OS collect job, you must updatethe DRLJCOLL member with one of the following collect statements, asappropriate:COLLECT LINUX;COLLECT ZLINUX;

v The LINUX collect processes performance and disk space created by the drlperfddaemon.

v The ZLINUX collect processes system statistics, file system disk usage, userinformation, and process information produced by the scripts scriptpi,scriptdf, scriptww, and scriptto.

For details about how to update the DRLJCOLL job, see the System PerformanceFeature Reference Volume I.

Data flowThe following figure shows an overview of the flow of Linux on zSeries data.


Data tables and lookup tablesThis chapter describes the data tables used by the Linux on zSeries component.

Data tablesThis section describes the data tables for the Linux on zSeries component.

ZLINUX_CONFIG_HW_D:

Figure 200. Linux on zSeries data flow


This table provides daily zLinux hardware configuration data. It contains hardwareconfiguration data from the ZLINUX_HARDCONF record with record type CONFand subtype HW.



DATE K DATE Date when the record was written. From DATE.

NODE_NAME K CHAR(16) Node name identifier. From NODE_NAME.

SYSTEM_NAME K CHAR(16) System name. From SYSTEM_NAME.

TOTAL_CPU INTEGER Total number of CPU configured for zLinux node.From TOTAL_CPU.

MIPS_PER_CPU FLOAT Number of MIPS per CPU. Based on zLinuxBogoMIPS measure. From MIPS_PER_CPU.

TOTAL_MEMORY FLOAT Total memory available for zLinux node, in KB. FromTOTAL_MEMORY.

VM_CONTROL_PGR CHAR(20) Name and version of z/VM control program. FromVM_CONTROL_PGR.

ZLINUX_CONFIG_SW_D:This table provides daily zLinux software configuration data for the packages used.It contains software configuration data from the ZLINUX_SOFTCONF record withrecord type CONF and subtype SW.



DATE K DATE Date when the record was written. From DATE.

NODE_NAME K CHAR(16) Node name identifier. From NODE_NAME.


PACKAGE_NAME K CHAR(50) The name of the package used on the system. FromPACKAGE_NAME.

SOFTWARE_VERSION K CHAR(20) The software version of the package installed on thesystem. From SOFTWARE_VERSION.

INST_TIMESTAMP CHAR(12) The timestamp of software installation. FromINST_TIMESTAMP.

ZLINUX_CPU_H,_D,_M:These tables provide hourly, daily, and monthly statistics on zLinux usage. Theycontain CPU and memory usage, paging rate, and number of users and processesfrom the ZLINUX_CPU record with record type PERF and subtype VM.


ZLINUX_CPU_H7 days

ZLINUX_CPU_D30 days

ZLINUX_CPU_M765 days



DATE K DATE Date when the records were written. For the _M table,this is the first day of the month. From DATE.

TIME K TIME Time, rounded down to the nearest hour, when therecord was written. From TIME. It only applies to the_H table.

NODE_NAME K CHAR(16) Node name. From NODE_NAME.


PERIOD_NAME K CHAR(8) Name of the period. This is derived using fieldsNODE_NAME, DATE, and TIME from the record asparameters in the PERIOD function.

CPU_USAGE_PCT_AVG FLOAT Average CPU usage, in percentage. This is the averageof CPU_AVG.

CPU_USAGE_PCT_MAX FLOAT Maximum CPU usage, in percentage. This is themaximum of CPU_MAX.

CPU_USAGE_PCT_MIN FLOAT Minimum CPU usage, in percentage. This is theaverage of CPU_MIN.

MEASURED_SEC FLOAT Total measured time interval, in seconds. Amount oftime, in seconds, between each read. This is the sumof INTERVAL*60.

MEM_FREE_PAGES_AVG FLOAT Average number of free memory pages, in KB. This isthe average of MEMORY_AVG.

MEM_FREE_PAGES_MAX FLOAT Maximum number of free memory pages, in KB. Thisis the maximum of MEMORY_MAX.

MEM_FREE_PAGES_MIN FLOAT Minimum number of free memory pages, in KB. Thisis the minimum of MEMORY_MIN.

PAGING_RATE_AVG FLOAT Average number of pages paged IN/OUT, per second.This is the average of PAGING_AVG.

PAGING_RATE_MAX FLOAT Maximum number of pages paged IN/OUT, persecond. This is the maximum of PAGING_MAX.

PAGING_RATE_MIN FLOAT Minimum number of pages paged IN/OUT, persecond. This is the minimum of PAGING_MIN.

PROCESSES_AVG FLOAT Average number of processes. This is the average ofPROCESSES.

PROCESSES_MAX FLOAT Maximum number of processes. This is the maximumof PROCESSES.

PROCESSES_MIN FLOAT Minimum number of processes. This is the minimumof PROCESSES.

RECORDS_COLLECTED FLOAT Total number of records. This is the count ofRECORDS.

USERS_AVG FLOAT Average number of users. This is the average ofUSERS.

USERS_MAX FLOAT Maximum number of users. This is the maximum ofUSERS.

USERS_MIN FLOAT Minimum number of users. This is the minimum ofUSERS.

ZLINUX_CPUTIME_D:


This table provides daily statistics on the CPU usage of zLinux. It contains datafrom the summary report of the TOP command, which is reformatted to a commonlayout by the zLinux script.



DATE K DATE Date when the output from the TOP command isgathered. From LNXDATE.

OP_SYSNAME K CHAR(5) Name of the operating system, usually Linux. FromLNXOPSY.

HOST_NAME K CHAR(8) Name of the host system on which OP_SYSNAME isrunning. From LNXHNAM.

TIME_USER_PCT DECIMAL(4,1) Percentage of time spent running jobs in the userspace. From PIUSRJOB.

TIME_NICE_PCT DECIMAL(4,1) Percentage of time spent running nice jobs in the userspace. From PINICJOB.

TIME_SYST_PCT DECIMAL(4,1) Percentage of time spent running in the kernel space(not including interrupts). From PISYSJOB.

TIME_IDLE_PCT DECIMAL(4,1) Percentage of time spent idle. From PIIDLJOB.

ZLINUX_DISK_INFO_D,_M:These tables provide daily and monthly statistics on zLinux disk usage. Theycontain disk performance data from the ZLINUX_DISK_FS record with record typePERF and subtype FS.


ZLINUX_DISK_INFO_D30 days

ZLINUX_DISK_INFO_M765 days





FILE_SYSTEM K CHAR(20) File system name. From DEVICE_NAME.

FREE_SPACE_KB FLOAT Free space on file system, in KB. FromFREE_SPACE_KB.

TOTAL_SPACE_KB FLOAT Total space on file system, in KB. FromTOTAL_SPACE_KB.

ZLINUX_DISKIO_H,_D,_M:These tables provide hourly, daily, and monthly statistics on zLinux disk I/O. Theycontain I/O performance data from the ZLINUX_DISKIO record with record typePERF and subtype IO.



ZLINUX_DISKIO_H7 days

ZLINUX_DISKIO_D30 days

ZLINUX_DISKIO_M765 days






PERIOD_NAME K CHAR(8) Name of the period. This is derived using fieldNODE_NAME, DATE, and TIME from the record asparameters in the PERIOD function.

DISK K CHAR(20) Physical disk name. From DISK.

DISK_BUSY_PCT_AVG FLOAT Average disk busy, in percentage. This is the averageof BUSY.

DISK_BUSY_PCT_MAX FLOAT Maximum disk busy, in percentage. This is themaximum of BUSY.

MEASURED_SEC INTEGER Total measured time interval, in seconds. Amount oftime, in seconds, between each read. This is the sumof INTERVAL*60.

READ_KB_TOTAL FLOAT Amount of data read, in KB. This is the sum ofTOTREAD.

READ_MAXRATE FLOAT Maximum amount of data read, in KB per second.Calculated as the maximum of TOTREAD/(INTERVAL*60.0).

RECORDS_COLLECTED FLOAT Number of records. This is the count of records.

RW_KB_TOTAL FLOAT Amount of data read/written, in KB. This is the sumof TOTRW.

RW_MAXRATE FLOAT Maximum amount of data read/written, in KB persecond. Calculated as the maximum ofTOTRW/(INTERVAL*60.0).

WRITE_KB_TOTAL FLOAT Amount of data written, in KB. This is the sum ofTOTWRITE.

WRITE_MAXRATE FLOAT Maximum amount of data written, in KB per second.Calculated as the maximum of TOTWRITE/(INTERVAL*60.0).

ZLINUX_FILESYS_H:This table provides hourly statistics on the disk space usage on the file systems ofzLinux. It contains data from the DF command, which is reformatted to a commonlayout by the zLinux scripts.




DATE K DATE Date when the output from DF command is gathered.From LNXDATE.

TIME K TIME Time, rounded down to the nearest hour, when theoutput from the DF command is gathered. FromLNXTIME.



FILESYS_NAME K CHAR(20) Name of the currently mounted file system. FromDFFISYST.

FILESYS_ALLOC FLOAT Amount of disk space allocated to the file system, inMegabytes. From DFBLOCKS.

FILESYS_AVAIL FLOAT Amount of disk space not used and available to thefile system. From DFMEMFRE.

FILESYS_MOUNT CHAR(10) Name of the mount point of the current file system.From DFMOUNTO.

FILESYS_USE FLOAT Amount of disk space in use by the file system, inMegabytes. From DFMEMUSE.

FILESYS_USEP FLOAT Percentage of disk space in use by the file system.From DFMEMUSP.

ZLINUX_FILESYS_D, _M:These tables provide daily and monthly statistics on the disk space usage on thefile systems of zLinux. They contain data from the DF command, which isreformatted to a common layout by the zLinux scripts.


ZLINUX_FILESYS_D30 days

ZLINUX_FILESYS_M765 days


DATE K DATE Date when the output from the DF command isgathered. For _M, this is the first day of the month.From LNXDATE.



FILESYS_NAME K CHAR(20) Name of the currently mounted file system. FromDFFISYST.

FILESYS_ALLOC FLOAT Amount of disk space allocated to the file system, inMegabytes. From DFBLOCKS.

FILESYS_AVL_AVG FLOAT Average amount of disk space not used and availableto the file system. From DFMEMFRE.

FILESYS_AVL_MAX FLOAT Maximum amount of disk space not used andavailable to the file system. From DFMEMFRE.



FILESYS_AVL_MIN FLOAT Minimum amount of disk space not used andavailable to the file system. From DFMEMFRE.

FILESYS_MOUNT CHAR(10) Name of the mount point of the current file system.From DFMOUNTO.

FILESYS_USE_AVG FLOAT Average amount of disk space in use by the filesystem, in Megabytes. From DFMEMUSE.

FILESYS_USE_MAX FLOAT Maximum amount of disk space in use by the filesystem, in Megabytes. From DFMEMUSE.

FILESYS_USE_MIN FLOAT Minimum amount of disk space in use by the filesystem, in Megabytes. From DFMEMUSE.

FILESYS_USEP_AVG FLOAT Average percentage of disk space in use by the filesystem. From DFMEMUSP.

FILESYS_USEP_MAX FLOAT Maximum percentage of disk space in use by the filesystem. From DFMEMUSP.

FILESYS_USEP_MIN FLOAT Minimum percentage of disk space in use by the filesystem. From DFMEMUSP.

SAMPLES FLOAT Total number of records. This is the count of theFILESYS_NAME field.

ZLINUX_MEM_H:This table provides hourly statistics on the memory usage of zLinux. It containsdata from the PI command, which is reformatted to a common layout by thezLinux scripts.



DATE K DATE Date when the output from the PI command isgathered. From LNXDATE.

TIME K TIME Time, rounded down to the nearest hour, when theoutput from the PI command is gathered. FromLNXTIME.



CONTEXT_SWITCH FLOAT Total number of context switches since booting up.From PIUPTCON.

MEM_BUFFER FLOAT Amount of buffers memory used by the kernel, inkilobytes. From PIMEMBUF.

MEM_CACHED FLOAT Amount of cached memory used by the kernel, inkilobytes. From PIMEMCCH.

MEM_FREE FLOAT Amount of free physical memory, in kilobytes. FromPIMEMFRE.

MEM_SHARED FLOAT Amount of shared memory used by the kernel, inkilobytes. From PIMEMSHR.

MEM_TOTAL FLOAT Total amount of physical memory in the system, inkilobytes. From PIMEMTOT.



MEM_USED FLOAT Amount of used physical memory, in kilobytes. FromPIMEMUSE.

PAGE_IN FLOAT Amount of disk blocks paged from disk, where ablock is 1 kilobyte. From PIUSRPIN.

PAGE_OUT FLOAT Amount of disk blocks paged to disk. FromPINICPOU.

SWAP_FREE FLOAT Amount of free swap memory, in kilobytes. FromPISWAFRE.

SWAP_IN FLOAT Number of memory pages paged in from swapspace.From PISYSSIN.

SWAP_OUT FLOAT Number of memory pages paged out to swapspace.From PISYSSOU.

SWAP_TOTAL FLOAT Total amount of swap memory in the system, inkilobytes. From PISWATOT.

SWAP_USED FLOAT Amount of used swap memory, in kilobytes. FromPISWAUSE.

ZLINUX_MEM_D, _M:These tables provide daily and monthly statistics on the memory usage of zLinux.They contain data from the PI command, which is reformatted to a common layoutby the zLinux scripts.


ZLINUX_MEM_D30 days

ZLINUX_MEM_M765 days


DATE K DATE Date when the output from the PI command isgathered. For _M, this is the first day of the month.From LNXDATE.



CONTEXT_SWITCH FLOAT Total number of context switches since booting up.From PIUPTCON.

MEM_BUFFER FLOAT Amount of buffers memory used by the kernel, inkilobytes. From PIMEMBUF.

MEM_BUFFER_AVG FLOAT Average amount of buffer memory used by thekernel, in kilobytes. From PIMEMBUF.

MEM_BUFFER_MAX FLOAT Maximum amount of buffer memory used by thekernel, in kilobytes. From PIMEMBUF.

MEM_BUFFER_MIN FLOAT Minimum amount of buffer memory used by thekernel, in kilobytes. From PIMEMBUF.

MEM_CACHED FLOAT Amount of cached memory used by the kernel, inkilobytes. From PIMEMCCH.



MEM_CACHED_AVG FLOAT Average amount of cached memory used by thekernel, in kilobytes. From PIMEMCCH.

MEM_CACHED_MAX FLOAT Maximum amount of cached memory used by thekernel, in kilobytes. From PIMEMCCH.

MEM_CACHED_MIN FLOAT Minimum amount of cached memory used by thekernel, in kilobytes. From PIMEMCCH.

MEM_FREE FLOAT Amount of free physical memory, in kilobytes. FromPIMEMFRE.

MEM_SHARED FLOAT Amount of shared memory used by the kernel, inkilobytes. From PIMEMSHR.

MEM_SHARED_AVG FLOAT Average amount of shared memory used by thekernel, in kilobytes. From PIMEMSHR.

MEM_SHARED_MAX FLOAT Maximum amount of shared memory used by thekernel, in kilobytes. From PIMEMSHR.

MEM_SHARED_MIN FLOAT Minimum amount of shared memory used by thekernel, in kilobytes. From PIMEMSHR.

MEM_TOTAL FLOAT Total amount of physical memory in the system, inkilobytes. From PIMEMTOT.

MEM_USED FLOAT Amount of used physical memory, in kilobytes. FromPIMEMUSE.

MEM_USED_AVG FLOAT Average amount of physical memory used, inkilobytes. From PIMEMUSE.

MEM_USED_MAX FLOAT Maximum amount of physical memory used, inkilobytes. From PIMEMUSE.

MEM_USED_MIN FLOAT Minimum amount of physical memory used, inkilobytes. From PIMEMUSE.

MEM_USED_PCT DECIMAL (4,1) Percentage of physical memory used, in kilobytes.From PIMEMUSE.

PAGE_IN FLOAT Amount of disk blocks paged from disk, where ablock is 1 kilobyte. From PIUSRPIN.

PAGE_OUT FLOAT Amount of disk blocks paged to disk. FromPINICPOU.

SAMPLES FLOAT Total number of records. This is the count of the fieldDATE.

SWAP_FREE FLOAT Amount of free swap memory, in kilobytes. FromPISWAFRE.

SWAP_IN FLOAT Number of memory pages paged in from swapspace.From PISYSSIN.

SWAP_OUT FLOAT Number of memory pages paged out to swapspace.From PISYSSOU.

SWAP_TOTAL FLOAT Total amount of swap memory in the system, inkilobytes. From PISWATOT.

SWAP_USED FLOAT Amount of used swap memory, in kilobytes. FromPISWAUSE.

SWAP_USED_AVG FLOAT Average amount of used swap memory, in kilobytes.From PISWAUSE.

SWAP_USED_MAX FLOAT Maximum amount of used swap memory, inkilobytes. From PISWAUSE.



SWAP_USED_MIN FLOAT Minimum amount of used swap memory, in kilobytes.From PISWAUSE.

SWAP_USED_PCT DECIMAL (4,1) Percentage of used swap memory, in kilobytes. FromPISWAUSE.

ZLINUX_PAGING_H,_D,_M:These tables provide hourly, daily, and monthly statistics on zLinux page space.They contain page space performance data from ZLINUX_PAGING record withrecord type PERF and subtype PS.


ZLINUX_PAGING_H7 days

ZLINUX_PAGING_D30 days

ZLINUX_PAGING_M765 days






PERIOD_NAME K CHAR(8) Name of the period. This is derived using fieldNODE_NAME, DATE, and TIME from the record asparameters in the PERIOD function.

DISK K CHAR(20) Physical disk name. From DISK.

PAGE_SPACE K CHAR(20) Page space name. From PAGE_SPACE.

PS_SIZE_MAX_KB FLOAT Maximum page space size, in KB. This is themaximum of PSSIZE.

PS_SIZE_AVG_KB FLOAT Average page space size, in KB. This is the average ofPSSIZE.

PS_USED_MAX_KB FLOAT Maximum page space used, in KB. This is themaximum of PSUSE.

PS_USED_AVG_KB FLOAT Average page space used, in KB. This is the averageof PSUSE.

RECORDS_COLLECTED FLOAT Number of records. This is the count of records.

ZLINUX_PROCESS_H:This table provides hourly statistics on zLinux processes. It contains data from thesummary report of the TOP command, which is reformatted to a common layoutby the zLinux script.

The retention period for this table is 10 days.



DATE K DATE Date when the output from the TOP command isgathered. From LNXDATE.

TIME K TIME Time, rounded down to the nearest hour, when theoutput from the TOP command is gathered. FromLNXTIME.



PROCESS_RUN FLOAT Number of RUNNING processes among the total.From TOPROCR.

PROCESS_SLE FLOAT Number of SLEEPING processes among the total.From TOPROCS.

PROCESS_STO FLOAT Number of STOPPED processes on the system at thetime of the last update. From TOPPROCA.

PROCESS_TOT FLOAT Total number of processes on the system at the timeof the last update. From TOPPROCT.

PROCESS_ZOM FLOAT Number of ZOMBIE processes among the total. FromTOPROCZ.

ZLINUX_PROCESS_D, _M:These tables provide daily and monthly statistics on zLinux processes. Theycontain data from the summary report of the TOP command, which is reformattedto a common layout by the zLinux script.


ZLINUX_PROCESS_D30 days

ZLINUX_PROCESS_M765 days


DATE K DATE Date when the output from the TOP command isgathered. For the _M table, this is the first day of themonth. From LNXDATE.



PROCESS_RUN_AVG FLOAT Average number of RUNNING processes. FromTOPROCR.

PROCESS_RUN_MAX FLOAT Maximum number of RUNNING processes. FromTOPROCR.

PROCESS_RUN_MIN FLOAT Minimum number of RUNNING processes. FromTOPROCR.

PROCESS_SLE_AVG FLOAT Average number of SLEEPING processes among thetotal. From TOPROCS.

PROCESS_SLE_MAX FLOAT Maximum number of SLEEPING processes among thetotal. From TOPROCS.



PROCESS_SLE_MIN FLOAT Minimum number of SLEEPING processes among thetotal. From TOPROCS.

PROCESS_STO_AVG FLOAT Average number of STOPPED processes. FromTOPPROCA.

PROCESS_STO_MAX FLOAT Maximum number of STOPPED processes. FromTOPPROCA.

PROCESS_STO_MIN FLOAT Minimum number of STOPPED processes. FromTOPPROCA.

PROCESS_TOT_AVG FLOAT Average number of total processes. From TOPPROCT.

PROCESS_TOT_MAX FLOAT Maximum number of total processes on the system.From TOPPROCT.

PROCESS_TOT_MIN FLOAT Minimum number of total processes on the system.From TOPPROCT.

PROCESS_ZOM_AVG FLOAT Average number of ZOMBIE processes. FromTOPROCZ.

PROCESS_ZOM_MAX FLOAT Maximum number of ZOMBIE processes. FromTOPROCZ.

PROCESS_ZOM_MIN FLOAT Minimum number of ZOMBIE processes. FromTOPROCZ.

SAMPLES FLOAT Total number of records. This is the count of the fieldPROCESS_TOT.

ZLINUX_USERS_H:This table provides hourly statistics on the CPU usage by users. It contains datafrom the W command, which is reformatted to a common layout by the zLinuxscripts.

The retention period for this table is 10 days.


DATE K DATE Date when the output from the W command isgathered. From LNXDATE.

TIME K TIME Time, rounded down to the nearest hour, when theoutput from the W command is gathered. FromLNXTIME.



USER_NAME K CHAR(8) Login name of the currently logged in user. FromWWUSER.

TTY_NAME K CHAR(8) Name of TTY used. From WWTTY.

REMOTE_HOST CHAR(16) Name of the remote host. From WWRHOSTN.

CPU_IDLE FLOAT Amount of time that the system has been idle, inseconds. From WWIDLE.

CPU_J FLOAT Amount of time used by all processes attached to theTTY, in seconds. From WWJCPU.



CPU_P FLOAT Amount of time used by the currently runningprocess, in seconds. From WWPCPU.

ZLINUX_USERS _D, _M:These tables provide daily and monthly statistics on the CPU usage by users. Theycontain data from the W command, which is reformatted to a common layout bythe zLinux scripts.


ZLINUX_USERS_D30 days

ZLINUX_USERS_M765 days


DATE K DATE Date when the output from the W command isgathered. For the _M table, this is the first day of themonth. From LNXDATE.



USER_NAME K CHAR(8) Login name of the currently logged in user. FromWWUSER.

TTY_NAME K CHAR(8) Name of TTY used. From WWTTY.

CPU_IDLE FLOAT Amount of time that the system has been idle, inseconds. From WWIDLE.

CPU_J_AVG FLOAT Average amount of time used by all processesattached to the TTY, in seconds. From WWJCPU.

CPU_J_MAX FLOAT Maximum amount of time used by all processesattached to the TTY, in seconds. From WWJCPU.

CPU_J_MIN FLOAT Minimum amount of time used by all processesattached to the TTY, in seconds. From WWJCPU.

CPU_J_TOT FLOAT Total amount of time used by all processes attached tothe TTY, in seconds. From WWJCPU.

CPU_P_AVG FLOAT Average amount of time used by the currentlyrunning process, in seconds. From WWPCPU.

CPU_P_MAX FLOAT Maximum amount of time used by the currentlyrunning process, in seconds. From WWPCPU.

CPU_P_MIN FLOAT Minimum amount of time used by the currentlyrunning process, in seconds. From WWPCPU.

REMOTE_HOST CHAR(16) Name of the remote host. From WWRHOSTN.

SAMPLES FLOAT Total number of records. This is the count of theTTY_NAME field.

ZLINUX_USR_CMD_D,_M:


These tables provide daily and monthly statistics on zLinux commands andresource consumption. They contain command accounting data from theZLINUX_USR_CMD record with record type PACCT.


ZLINUX_USR_CMD_D30 days

ZLINUX_USR_CMD_M765 days





USER_GROUP K CHAR(8) Group name. From AC_GID.

NODE_GROUP K CHAR(16) Node group. From ACCOUNTING_GROUP in theZLINUX_NODE_NAME lookup table. This is derivedusing field NODE_NAME form the record as key. Ifno match is found, this column is set to a questionmark (?).

USER_NAME K CHAR(8) User name. From AC_UID.

COMMANDS INTEGER Total number of commands. This is the count ofrecords.

ELAPSED_SEC FLOAT Total elapsed time, in seconds. Calculated as the sumof AC_ETIME/64.0.

IO_CHARS FLOAT Total characters transferred. This is the sum of AC_IO.

MEMORY_USAGE FLOAT Total memory usage, in KB. This value should bedivided by COMMANDS to get the average memoryusage. This is the sum of AC_MEM/1024.

RW_BLOCKS FLOAT Total blocks read/written. This is the sum of AC/RW.

SYSTEM_SEC FLOAT Total system time, in seconds. Calculated as the sumof AC_STIME/64.0.

USER_SEC FLOAT Total user time, in seconds. Calculated as the sum ofAC_UTIME/64.0.

ZLINUX_WTMP_INFO_D,_M:These tables provide daily and monthly statistics on zLinux users and theirconnections. They contain connect information accounting data fromZLINUX_WTMP_INFO record with record type WTMP.


ZLINUX_WTMP_INFO_D30 days

ZLINUX_WTMP_INFO_M765 days







PROCESS_ID K CHAR(6) The process identifier. From PROCESS_ID.

USER_LOG K CHAR(8) User login name. From USER_LOG_NAME.

CONNECT_DESC CHAR(16) Connect type description. From theZLINUX_CONNECT_TYP lookup table.

NODE_NAME_SYS CHAR(50) Connection node. From NODE_NAME_SYS.

Lookup tablesThis section describes the lookup tables for the Linux on zSeries component.

ZLINUX_CONNECT_TYP:This lookup table contains the descriptions of the connect types.


CONNECT_TYPE K CHAR(2) Connect type code.

CONNECT_DESC CHAR(16) Connect type description.

Example of table contentsConnect_Type Connect_Desc------------ ------------00 EMPTY01 RUN_LVL02 BOOT_TIME.. ..

ZLINUX_CONNECT_TYP:This lookup table contains the descriptions of the connect types.


CONNECT_TYPE K CHAR(2) Connect type code.

CONNECT_DESC CHAR(16) Connect type description.

Example of table contentsConnect_Type Connect_Desc------------ ------------00 EMPTY01 RUN_LVL02 BOOT_TIME.. ..

ZLINUX_NODE_NAME:This lookup table contains the node names and their associated accounting groups,period plans, and TCP/IP address.


NODE_NAME K CHAR(16) Node name. This is an alias name for the node. It cancontain global search characters.

ACCOUNTING_GROUP CHAR(16) Accounting group.

IP_ADDRESS CHAR(15) IP address. It can contain global search characters.



PERIOD_PLAN CHAR(8) Period plan. This value can be used as a parameterwhen using the PERIOD function.

Example of table contentsNode_Name Accounting_Group IP_Address Period_Plan--------- ---------------- ---------- -----------node1 group1 9.50.20.70 BASEnode2 group2 9.50.20.71 PLAN1node3 group3 9.50.20.72 PLAN2% DEFAULT 99.99.99.99 DEFAULT.. .. .. ..

ZLINUX_NODE_NAME:This lookup table contains the node names and their associated accounting groups,period plans, and TCP/IP address.


NODE_NAME K CHAR(16) Node name. This is an alias name for the node. It cancontain global search characters.

ACCOUNTING_GROUP CHAR(16) Accounting group.

IP_ADDRESS CHAR(15) IP address. It can contain global search characters.

PERIOD_PLAN CHAR(8) Period plan. This value can be used as a parameterwhen using the PERIOD function.

Example of table contentsNode_Name Accounting_Group IP_Address Period_Plan--------- ---------------- ---------- -----------node1 group1 9.50.20.70 BASEnode2 group2 9.50.20.71 PLAN1node3 group3 9.50.20.72 PLAN2% DEFAULT 99.99.99.99 DEFAULT.. .. .. ..

ReportsThis chapter describes the reports provided with the Linux on zSeries component.

zLinux Filesystem Usage Daily TrendThis report shows the daily trend for zLinux file system usage.


Report ID:ZLNX001

Report group:Linux on zSeries reports

Source:ZLINUX_FILESYS_D

Attributes:MVS, TREND, DAILY, AVAILABILITY, ZLINUX

Variables:FROM_DATE, TO_DATE, OP_SYSNAME, HOST_NAME, FILESYS_NAME



DATE Date of the measurement.

OP SYSNAMEName of the operating system.

HOST NAMEName of the host system on which the operating system is running.

FILESYS NAMEName of the currently mounted file system.

FILESYS USEP MAXMaximum amount of disk space in use by the file system , in MB.

FILESYS USEP MINMinimum amount of disk space in use by the file system, in MB.

zLinux Processes Daily BreakdownThis report shows the daily breakdown for zLinux processes.


Report ID:ZLNX002


Source:ZLINUX_PROCESS_D

Attributes:MVS, TREND, DAILY, ZLINUX

Variables:FROM_DATE, TO_DATE, OP_SYSNAME, HOST_NAME

zLinux Filesystem Usage Daily Trend: ’/dev/dasdt1’

FILESYS FILESYSOP HOST FILESYS USEP USEP

DATE SYSNAME NAME NAME MAX MIN---------- ------- -------- -------------------- ---------- ----------2001-10-19 Linux lnxsused /dev/dasdt1 4.000E+01 3.000E+012001-10-20 Linux lnxsused /dev/dasdt1 6.000E+01 5.000E+012001-10-21 Linux lnxsused /dev/dasdt1 8.000E+01 2.000E+012001-10-22 Linux lnxsused /dev/dasdt1 6.000E+01 4.000E+01

Tivoli Decision Support for z/OS Report: ZLNX001

Figure 201. Example of a zLinux Filesystem Usage Daily Trend report



DATE Date of the measurement.

OP SYSNAMEName of the operating system.

HOST NAMEName of the host system on which the operating system is running.

PROCESS TOT AVGAverage number of processes on the system at the time of the last update.

PROCESS SLE AVGAverage number of SLEEPING processes.

PROCESS RUN AVGAverage number of RUNNING processes.

PROCESS ZOM AVGAverage number of ZOMBIE processes.

zLinux Acct Resource by User, Daily OverviewFor a specific zLinux node and system, this report provides daily overviewinformation about the resource consumption by user name and total number ofcommands run.


Report ID:ZACCT01


Source:ZLINUX_USR_CMD_D

Attributes:ZLINUX, ACCT, ACCOUNTING, RESOURCE, DAILY, OVERVIEW, USER

Variables:DATE, NODE_NAME, SYSTEM_NAME, USER_NAME

zLinux Processes Daily Breakdown

PROCESS PROCESS PROCESS PROCESSOP HOST TOT SLE RUN ZOM

DATE SYSNAME NAME AVG AVG AVG AVG---------- ------- -------- ---------- ---------- ---------- ----------2001-10-12 Linux lnxsused 1.310E+02 1.200E+02 2.000E+00 0.000E+002001-10-13 Linux lnxsused 3.100E+01 3.000E+01 1.000E+00 0.000E+002001-10-19 Linux lnxsused 3.600E+01 3.050E+01 1.000E+00 4.500E+00

Tivoli Decision Support for z/OS Report: ZLNX002

Figure 202. Example of a zLinux Processes Daily Breakdown report



User nameName of the user who used this node.

Commands (count)The number of times the user entered this command.

Elapsed time (hour)The elapsed time, in hours, used by this user, entering this command.Calculated as ELAPSED_SEC/3600.

System time (sec)The system time, in seconds, used by this user, entering this command.

User time (sec)The user time, in seconds, used by this user, entering this command.

Cmd mem avg (KB)The average memory (in KB) used by this user entering this command.Calculated as MEMORY_BYTES/(1024*COMMANDS).

IO (KB)Characters (in KB) that were transferred by this user, using this command.Calculated as IO_CHARS/1024.

RW blocks (count)The number of blocks that were read and written by this user, entering thiscommand.

zLinux Acct User Connect Info, Daily OverviewFor a specific zLinux node and system, this report provides daily overviewinformation about the users and their connections.


Report ID:ZACCT02


Source:ZLINUX_WTMP_INFO_D

zLinux Acct Resource by User, Daily OverviewDate: ’2005-02-01’ User name: ’root’

Node name: ’zlinux1’ System name: ’SYS1’

! Elapsed System UserUser ! Commands time time time Cmd mem IO RW blocksname ! (count) (hour) (sec) (sec) avg (KB) (KB) (count)-------- ! -------- --------- --------- -------- --------- ------ ---------root ! 9 .02 0.09 3 0.23 7 3

! 9 .23 0.49 13 0.32 27 53! - - - - - - -! - - - - - - -! - - - - - - -! ======== ========= ========= ======== ========= ======= ========

Total ! 18 0.25 0.58 16 0.55 34 56

Tivoli Decision Support for z/OS Report: ZACCT01

Figure 203. Example of a zLinux Acct Resource by User, Daily Overview report


Attributes:ZLINUX, ACCT, ACCOUNTING, WTMP, USER, DAILY, OVERVIEW

Variables:DATE, NODE_NAME, SYSTEM_NAME


Date The date when the information was collected.

User loginUser login name.

Connect DescConnect type description.

Process IDThe process identifier.

Connect NodeConnection node name.

zLinux Perf Statistics All Systems, Daily OverviewFor all zLinux nodes and systems, this report provides daily overview informationabout processor usage, pages of memory, paging rate, processes, and users. Thereport is produced by period name (PRIME or NIGHT).


Report ID:ZPERF01


Source:ZLINUX_CPU_D

Attributes:ZLINUX, PERF, PERFORMANCE, SYSTEM, USAGE, DAILY, OVERVIEW

Variables:DATE, PERIOD_NAME

zLinux Acct User Connect Info, Daily OverviewDate: ’2005-01-01’

Node name: ’zlinux1’ System name: ’SYS1’

Date User Connect Process ConnectLogin Desc ID Node

---------- --------- -------- ----------- ---------2005-01-01 root BOOT 000002 node12005-01-01 login RUN_LVL 000003 node22005-01-01 user1 RUN_LVL 000004 node32005-01-01 user2 RUN_LVL 000005 node4

Tivoli Decision Support for z/OS Report: ZACCT02

Figure 204. Example of a zLinux Acct User Connect Info, Daily Overview report



Node nameThe name of the zLinux node.

System nameThe name of the system.

CPU usage avg (%)The average processor usage, in percentage.

CPU usage max (%)The maximum processor usage, in percentage.

Mem free pages avgThe average number of free pages of memory.

Mem free pages minThe minimum number of free pages of memory.

Paging rate avgThe average paging rate per second.

Paging rate maxThe maximum paging rate per second.

Processes avgThe average number of processes.

Processes maxThe maximum number of processes.

Users avgThe average number of users for this node.

Users maxThe maximum number of users for this node.

zLinux Perf Disk I/O for System, Daily OverviewFor a specific zLinux node and system, this report provides daily overviewinformation about disk usage: the average and maximum percentage of busy times,the average and maximum read and write amounts. The report is produced byperiod name (PRIME or NIGHT).


Report ID:ZPERF02


zLinux Perf Statistics All Systems, Daily OverviewDate: ’2004-12-23’ Period: ’PRIME’

! CPU CPU Mem free Mem free Paging PagingNode System ! usage usage pages pages rate rate Processes Processes Users Usersname name ! avg (%) max (%) avg min avg max avg max avg max------- ------ ! ------- ------- -------- -------- ------ ------ --------- --------- ----- -----zlinux1 SYS1 ! 2.0 15 35587 30272 0.90 5 6 10 1 2zlinux1 SYS1 ! 6.2 25 51663 51312 0.00 0 7 11 2 3

Tivoli Decision Support for z/OS Report: ZPERF01

Figure 205. Example of a zLinux Perf Statistics All Systems, Daily Overview report


Source:ZLINUX_DISKIO_D

Attributes:ZLINUX, PERF, PERFORMANCE, DISK, I/O, DAILY, OVERVIEW

Variables:DATE, NODE_NAME, SYSTEM_NAME, PERIOD_NAME


Disk nameThe name of the physical disk.

Busy avg (%)The average time the disk was busy, in percentage.

Busy max (%)The maximum time the disk was busy, in percentage.

Read avg (KB/sec)The average amount of disk that was read per second, in KB.

Read max (KB/sec)The maximum amount of disk that was read per second, in KB.

Write avg (KB/sec)The average amount of disk that was written per second, in KB.

Write max (KB/sec)The maximum amount of disk that was written per second, in KB.

R/W avg (KB/sec)The average amount of disk that was read and written per second, in KB.

R/W max (KB/sec)The maximum amount of disk that was read and written per second, inKB.

zLinux Hardware Configuration, Daily OverviewFor a specific zLinux node and system, this report provides daily overviewinformation about the hardware configuration.


Report ID:ZCONF01

zLinux Perf Statistics All Systems, Daily OverviewDate:’2005-05-31’ Period:’PRIME’

Node name:’zlinux1’ System name:’SYS1’

! Busy avg Busy max Read avg Read max Write avg Write max RW avg RW maxDisk name ! (%) (%) (KB/sec) (KB/sec) (KB/sec) (KB/sec) (KB/sec) (KB/sec)--------- ! -------- --------- -------- -------- --------- --------- -------- --------

hdisk0 ! 10.5 12.0 1.0 2.0 11.2 15.1 10.1 12.1hdisk1 ! 15.2 14.0 2.0 4.0 13.2 18.1 13.1 16.1

======== ========= ======== ======== ========= ========= ======== ========vg/max 12.1 13.2 1.5 3.0 12.1 17.3 12.3 14.5

Tivoli Decision Support for z/OS Report: ZPERF02

Figure 206. Example of a zLinux Perf Disk I/O for System, Daily Overview report



Source:ZLINUX_CONFIG_HW_D

Attributes:ZLINUX, CONFIGURATION, CONF, HARDWARE, HW, DAILY,OVERVIEW



Date The date when the configuration data was gathered.



Total CPUsTotal number of CPUs configured for the environment.

MIPS CPUNumber of MIPS per single CPU. Based on BogoMIPS measure.

Total memoryTotal memory available for environment.

VM controlName and version of z/VM control program.

zLinux Software Configuration, Daily OverviewFor a specific zLinux node and system, this report provides daily overviewinformation about the software configuration.


Report ID:ZCONF02


zLinux Hardware Configuration, Daily OverviewDate:’2005-01-01’ Node name:’all’

System name: ’SYS1’

Date Node System Total MIPS Total VMname name CPUs CPU memory control

---------- --------- ------- ------ ----- ------- ---------2005-01-01 zlinux1 SYS1 6 560 500 z/VM 4.42005-01-01 zlinux1 SYS1 2 321 1000 z/VM 4.42005-01-01 zlinux1 SYS1 1 230 500 z/VM 4.4

Tivoli Decision Support for z/OS Report: ZCONF01

Figure 207. Example of a zLinux Hardware Configuration, Daily Overview report


Source:ZLINUX_CONFIG_SW_D

Attributes:ZLINUX, CONFIGURATION, CONF, SOFTWARE, SW, DAILY, OVERVIEW



Date The date when the configuration data was gathered.



Package nameThe name of the package.

Software versionSoftware version of the package installed.

Lotus Domino for z/OS componentCustomizationv Making input data availablev Reviewing the DRLJCOLL job

Data flow


Data tables and lookup tablev Data tables

– DOMINO_DB_ACT_H, _D– DOMINO_DB_CACHE_H, _D– DOMINO_PORT_ACT_H, _D– DOMINO_SERVER_H, _D, _M– DOMINO_TRANS_H, _D– DOMINO_USER_ACT_H

zLinux Software Configuration, Daily OverviewDate: ’2005-01-01’ Node name: ’zlinux1’

System name: ’SYS1’

Date Node System Package Softwarename name name version

---------- --------- ------ ------- ---------2005-01-01 zlinux1 SYS1 anacron 2.12005-01-01 zlinux1 SYS1 asm 3.02005-01-01 zlinux1 SYS1 at 1.0

Tivoli Decision Support for z/OS Report: ZCONF02

Figure 208. Example of a zLinux Software Configuration, Daily Overview report


v Lookup table– DOMINO_TRANS_TYPE

Reportsv Domino I/O & Access Statistics, Hourly reportv Domino Messages Statistics, Daily reportv Domino Transaction Statistics, Hourly reportv Domino Server DB Cache and Buffer Pool Statistics, Daily reportv Domino General Server Statistics, Daily report

CustomizationBefore you can use the Lotus® Domino® for z/OS component to collect data andcreate reports, you must customize the component by making input data available.You must perform the following steps to customize the Lotus Domino for z/OScomponent:1. Making input data available.2. Reviewing the DRLJCOLL job.

Making input data availableSMF Type 108 records are generated using the 'C' language function 'smf_record'that is a part of the z/OS extensions to the language. Records are generated at theexpiration of the SMF Global Interval (a combination of the INTVAL and theSYNCVAL parameters in the SMFPRMxx PARMLIB member). To enable thegeneration of these records, include SYS(TYPE(108) in the SMFPRMxx PARMLIBmember. The Lotus Domino for z/OS server user ID must also have READ accessto the BPX.SMF Facility class. The generated invocation results in an environmentthat equates to:

Macro SMFTWM (SVC level interface) -- record exit = IEFU83

Mode Task

Storage Residency31-bit

SUBSYS'STC'

Security NoticeBecause the processing that generates these records is using the 'C'language interface, some security setup must be done to enable theserecords to be generated. The RACF commands (or their equivalent) mustbe issued before these records can be generated:v RDEFINE FACILITY BPX.SMF UACC(NONE) – may have already been

donev PERMIT BPX.SMF CLASS(FACILITY) ID(<server>) ACCESS(READ) –

allow accessv SETROPTS RACLIST(FACILITY) REFRESH – refresh in-core tables

Reviewing the DRLJCOLL jobBefore running the Tivoli Decision Support for z/OS collect job, you must updatethe DRLJCOLL job (a member in the DRLxxx.SDRLCNTL library) to include thecollection of Lotus Domino for z/OS log data sets. Follow the instructions in thecomments section of this job to modify the appropriate JCL statements.


Data flowThe Lotus Domino for z/OS component collects records from the SMF data set andstores extracted and summarized data in the Tivoli Decision Support for z/OSdatabase. The reporting function extracts data from the database and creates thereports that you request through the reporting dialogs. The following figure showsan overview of the flow of data through the Lotus Domino for z/OS component.


Figure 209. Lotus Domino for z/OS component data flow


Log and record definitionsThe Lotus Domino for z/OS component collects records from the systemmanagement facility (SMF) logs.

This record type presents data for a Lotus Notes® Domino Server running on anz/OS system. The specific type of data that is being reported is defined by thesubtype field on the record (SMF108STP) in the standard record header.

SMF_108_01 (subtype 1: Server Load)Contains counts of activity of the server running on the z/OS system.

SMF_108_02 (subtype 2: User Activity)Reports Lotus Domino for z/OS user activity for the different protocolsthat Lotus Domino for z/OS supports.

SMF_108_03 (subtype 3: Monitoring and Tuning)Monitors some statistics and certain configuration parameters used by theserver.

SMF_108_06 (subtype 6: Database Activity)Reports Lotus Domino for z/OS specific data for Lotus Domino for z/OSdatabases.

Data tables and lookup tableThis chapter describes the data tables and lookup table used by the Lotus Dominofor z/OS component.

Data tablesThis section describes the data tables for the Lotus Domino for z/OS component.

DOMINO_DB_ACT_H, _D:These tables provide hourly and daily data for the Lotus Domino for z/OSdatabases activity. They contain data from the SMF record type 108, subtype 6.


DOMINO_DB_ACT_H10 days

DOMINO_DB_ACT_D45 days


DATE K DATE Date when the collection interval expires. FromSMF108PRIENDT.

TIME K TIME Time when the collection interval expires. FromSMF108PRIENDT. Applies only to _H.

PERIOD_NAME K CHAR(8) Name of the period. This is derived using fieldsSMF108PRIENDT and SM108SID from the record asparameters in the PERIOD function.


SYSPLEX_NAME K CHAR(8) Sysplex name. From SMF108PRSPN.

SERVER_NAME K CHAR(32) Server name. From SMF108PRSVN.

DATABASE_NAME K CHAR(64) Last 64 characters of the database name. FromSMF108DBNAME.



MEASURED_SEC INTEGER Measured time period, in seconds. This is theduration of the Lotus Domino for z/OS measurementintervals. Calculated as the sum of interval differencesbetween SMF108PRIENDT and SMF108PRISTARTTfields.

INPUT_RECORDS SMALLINT Number of input records collected from the input log.

DB_INDEXES INTEGER Number of indexing operations started on thisdatabase by the server. Calculated as the sum ofSMF108DBINDEX.

DB_REPLICATIONS INTEGER Number of replications on this database initiated bythis server. Calculated as the sum of SMF108DBREPS.

DB_DOCUMENTS_ADD INTEGER Number of documents added to this database.Calculated as the sum of SMF108DBDOCADDS.

DB_DOCUMENTS_DEL INTEGER Number of documents deleted from this database.Calculated as the sum of SMF108DBDOCDELS.

DOMINO_DB_CACHE_H, _D:These tables contain hourly and daily statistics for tuning the Lotus Domino forz/OS server database cache and buffer pool. They contain data from the SMFrecord type 108, subtype 3.


DOMINO_DB_CACHE_H10 days

DOMINO_DB_CACHE_D45 days










DB_CACHE_STATUS CHAR(8) Database cache status possible value, enabled ordisabled. Last occurrences of SMF108MTDBCENAB.

DB_CACHE_MAX INTEGER Maximum number of database cache entries.Calculated as the maximum of SMF108MTDBCMAXE.



DB_CACHE_CURRENT INTEGER Number of db cache (current entries). Calculated asthe last occurrence of SMF108MTDBCCE. Appliesonly to _H.

DB_CACHE_AVG REAL Average number of database cache entries. Calculatedas the average of SMF108MTDBCMAXE.

DB_CACHE_INIT_OPEN INTEGER Number of database cache (initial database opens).Calculated as the sum of SMF108MTDBCIDBO.

DB_CACHE_OVCR_REJ INTEGER Number of database cache (overcrowding rejections).Calculated as the sum of SMF108MTDBCOCR.

DB_CACHE_HITS INTEGER Number of database cache (hits). Calculated as thesum of SMF108MTDBCHITS.

DB_CACHE_HIGH_W_M INTEGER Database cache (high water mark). Calculated as themaximum of SMF108MTDBCHWM.

NIFPOOL_SIZE_MIN REAL Minimum Database.NIFPool.Size (in bytes).Calculated as the minimum of SMF108MTNIFS.

NIFPOOL_SIZE_MAX REAL Maximum Database.NIFPool.Size (in bytes).Calculated as the maximum of SMF108MTNIFS.

NIFPOOL_USED_MIN REAL Minimum Database.NIFPool.Used (in bytes).Calculated as the minimum of SMF108MTNIFN.

NIFPOOL_USED_MAX REAL Maximum Database.NIFPool.Used (in bytes).Calculated as the maximum of SMF108MTNIFN.

NSFPOOL_SIZE_MIN REAL Minimum Database.NSFPool.Size (in bytes).Calculated as the minimum of SMF108MTNSFS.

NSFPOOL_SIZE_MAX REAL Maximum Database.NSFPool.Size (in bytes).Calculated as the maximum of SMF108MTNSFS.

NSFPOOL_USED_MIN REAL Minimum Database.NSFPool.Used (in bytes).Calculated as the minimum of SMF108MTNSFN.

NSFPOOL_USED_MAX REAL Maximum Database.NSFPool.Used (in bytes).Calculated as the maximum of SMF108MTNSFN.

DB_BUFPOOL_READ REAL Number of Database.BufferPool reads. Calculated asthe sum of SMF108MTDBPR.

DB_BUFPOOL_WRITE REAL Number of Database.BufferPool writes. Calculated asthe sum of SMF108MTDBPW.

DOMINO_PORT_ACT_H, _D:These tables contain hourly and daily data that is being reported for each TCP/IPport to which the server has connection. They contain data extracted from the SMFrecord type 108, subtype 1.


DOMINO_PORT_ACT_H10 days

DOMINO_PORT_ACT_D45 days










TCPIP_PORT K CHAR(8) First eight bytes of the TCP/IP port. FromSMF108PTNAME.



SESSIONS_IN INTEGER Number of incoming sessions processed during theinterval (client to server connection). Calculated as thesum of SMF108PTNWSESIN.

KBYTES_RECEIVED INTEGER Total number of kilobytes received for this portduring the interval. Calculated as the sum ofSMF108PTNWBR.

BYTES_RECV_SEC REAL Average number of bytes/second received for thisport. Calculated as the average of the ratio betweenSMF108PTNWBR and collection interval.

SESSIONS_OUT INTEGER Number of outgoing sessions processed during theinterval (client to server connection). Calculated as thesum of SMF108PTNWSESOUT.

KBYTES_SENT INTEGER Total number of kilobytes sent for this port during theinterval. Calculated as the sum of SMF108PTNWBS.

BYTES_SENT_SEC REAL Average number of bytes/second sent for this port.Calculated as the average of the ratio betweenSMF108PTNWBS and collection interval.

DOMINO_SERVER_H, _D, _M:These tables contain hourly, daily, and monthly information on global activity atthe server level and statistics for tuning the Lotus Domino for z/OS server. Theycontain data extracted from the SMF record type 108, subtype 1 and subtype 3.


DOMINO_SERVER_H10 days

DOMINO_SERVER_D45 days

DOMINO_SERVER_M548 days











MAX_NUMBER_USERS INTEGER Maximum number of users. This is the maximum ofSMF108MTMAXUSERS.

USERS_CONNECTED INTEGER Current number of users. This is the last occurrence ofSMF108SLCU.

USERS_CONNECT_AVG REAL Average number of users. Calculated as the averageof SMF108SLCU.

USERS_CONNECT_MAX INTEGER Maximum number of users. Calculated as themaximum of SMF108SLCU.

USERS_ACT_CURRENT INTEGER Number of currently connected users that arecurrently active. This is the last occurrence ofSMF108SLUA.

USERS_ACT_AVG REAL Average number of connected users that are currentlyactive. Calculated as the average of SMF108SLUA.

USERS_ACT_MAX INTEGER Maximum number of connected users that arecurrently active. Calculated as the maximum ofSMF108SLUA.

USERS_ACT_LAST_1M INTEGER Number of currently connected users that have beenactive within the last minute. This is the lastoccurrence of SMF108SLUA1M.

USERS_ACT_LAST_3M INTEGER Number of currently connected users that have beenactive within the last three minutes. This is the lastoccurrence of SMF108SLUA3M.

USERS_ACT_LAST_5M INTEGER Number of currently connected users that have beenactive within the last five minutes. This is the lastoccurrence of SMF108SLUA5M.

USERS_ACT_LAST_15M INTEGER Number of currently connected users that have beenactive within the last 15 minutes. This is the lastoccurrence of SMF108SLUA15M.

USERS_ACT_LAST_30M INTEGER Number of currently connected users that have beenactive within the last 30 minutes. This is the lastoccurrence of SMF108SLUA30M.

TASKS_USE_CURRENT SMALLINT Number of tasks currently in use. This is the lastoccurrence of SMF108SLTASKS.



TASKS_USE_AVG REAL Average number of tasks in use during the interval.Calculated as the average of SMF108SLTASKS.

TASKS_USE_MAX SMALLINT Maximum number of tasks in use during the interval.This is the maximum of SMF108SLTASKSMAX.

TASKS_UPDATES_MAX SMALLINT Maximum number of concurrent update tasks.Calculated as the maximum of SMF108MTUPMAX.

PHY_THREAD_TOTAL SMALLINT Total number of physical thread pool threads forserver_pool_tasks. This is the last occurrence ofSMF108SLTT.

PHY_THREAD_USE_CUR SMALLINT Number of physical thread pool threads currently inuse. This is the last occurrence of SMF108SLPTIU.

PHY_THREAD_USE_AVG REAL Average number of physical thread pool threads inuse during the interval. Calculated as the average ofSMF108SLPTIU.

PHY_THREAD_USE_MAX SMALLINT Maximum number of physical thread pool threads inuse during the interval. This is the maximum ofSMF108SLPTIUMAX.

VIR_THREAD_USE_CUR SMALLINT Number of virtual thread pool threads currently inuse. This is the last occurrence of SMF108SLVTIU.

VIR_THREAD_USE_AVG REAL Average number of virtual thread pool threads in useduring the interval. Calculated as the average ofSMF108SLVTIU.

VIR_THREAD_USE_MAX SMALLINT Maximum number of virtual thread pool threads inuse during the interval. This is the maximum ofSMF108SLVTIUMAX.

TRD_MAIL_SENT_MAX SMALLINT Maximum number of mail transfer threads.Calculated as the maximum of SMF108MTMMXFER.

TRD_MAIL_DELIV_MAX SMALLINT Maximum number of mail delivery threads.Calculated as the maximum of SMF108MTMMXDLV.

TRD_MAIL_CONCU_MAX SMALLINT Maximum number of concurrent mail transferthreads. Calculated as the maximum ofSMF108MTMMXCONXFR.

ASYNC_IO_READ INTEGER Number of asynchronous I/O reads during interval.Calculated as the sum of SMF108SLAIOR.

ASYNC_IO_WRITE INTEGER Number of asynchronous I/O writes during interval.Calculated as the sum of SMF108SLAIOW.

HTTP_READS INTEGER Number of HTTP reads during interval. Calculated asthe sum of SMF108SLHTTPR.

HTTP_WRITE INTEGER Number of HTTP writes during interval. Calculatedas the sum of SMF108SLHTTPW.

POP3_READS INTEGER Number of POP3 reads during interval. Calculated asthe sum of SMF108SLPOP3.

IMAP_READS INTEGER Number of IMAP reads during interval. Calculated asthe sum of SMF108SLIMAPR.

MAIL_MSGS_DELIV INTEGER Number of Lotus Domino for z/OS mail messagesrouted. Calculated as the sum ofSMF108SLDMSENTL.

MAIL_MSGS_DELI_AKB REAL Average size of Lotus Domino for z/OS mail andSMTP messages delivered, in kilobytes. Calculated asthe average of SMF108SLDMSENTLAS.



MAIL_MSGS_SENT INTEGER Number of Lotus Domino for z/OS mail and SMTPmessages transferred. Calculated as the sum ofSMF108SLDMSENTR.

MAIL_MSGS_SENT_AKB REAL Average size of Lotus Domino for z/OS mailmessages transferred, in kilobytes. Calculated as theaverage of SMF108SLDMSENTRAS.

MAILBOXES_MAX SMALLINT Maximum number of mail.boxes. Calculated as themaximum of SMF108MTMAILBOXEs.

SMTP_MSGS_RECV INTEGER Number of SMTP messages received from otherservers during interval. Calculated as the sum ofSMF108SLSMREC.

SMTP_MSGS_RECV_AKB REAL Average size of SMTP messages received from otherservers during interval, in kilobytes. Calculated as thesum of SMF108SLSMRECAS.

SMTP_MSGS_SENT INTEGER Number of SMTP messages sent to other serversduring interval. Calculated as the sum ofSMF108SLSMSENT.

SMTP_MSGS_SENT_AKB REAL Average size of SMTP messages sent to other serversduring interval, in kilobytes. Calculated as the sum ofSMF108SLSMSENTAS.

SERVER_TRANSACTION INTEGER Total number of transactions processed duringinterval. Calculated as the sum of SMF108SLTRANS.

LIMIT_CONCUR_TRANS REAL Limit for number of concurrent transactions. This isthe last occurrence of SMF108MTMAXCONTR.

SESSION_CONCUR_MAX INTEGER Maximum number of sessions to run concurrently.Calculated as the maximum ofSMF108MTMAXCONSES.

SERVER_REPLICATION INTEGER Number of replications initiated by this server.Calculated as the sum of SMF108SLSVREPL.

REPLICA_CONCUR_MAX SMALLINT Maximum number of concurrent replicators.Calculated as the maximum of SMF108MTREPMAX.

TIMEOUTS_MNUTE INTEGER Number of minutes in timeout. This is the lastoccurrence of SMF108MTSESTIMEOUT.

NSF_BFPOOL_MAX_4KB INTEGER Maximum size of NSF buffer pool, in kilobytes.Calculated as the maximum of SMF108MTNSFPOOL.

NSF_BFPOOL_USED INTEGER Number of bytes being used in the NSF buffer pool.This is the last occurrence of SMF108MTNSFPOOLIU.

SERVER_AVAIL_THRD INTEGER Server availability threshold. A threshold set todetermine when a server is considered busy. This isthe last occurrence of SMF108MTSATH.

SERVER_AVAIL_INDEX INTEGER Server availability index. This is the last occurrence ofSMF108MTSAX.

NUM_CACHE_COMMAND INTEGER The actual number of commands that the commandcache contains. Calculated as last occurrence ofSMF108SLDMNCCHCMD.

MAX_CACHE_COMMAND INTEGER The maximum number of commands that thecommand cache contained during the interval.Calculated as max occurrence ofSMF108SLDMNCCHCMD.



MIN_CACHE_COMMAND INTEGER The minimum number of commands that thecommand cache contained during the interval.Calculated as min occurrence ofSMF108SLDMNCCHCMD.

NUM_CACHE_DESIGN INTEGER The actual number of designs that the design cachecontains. Calculated as last occurrence ofSMF108SLDMNCCHDSG.

MIN_CACHE_DESIGN INTEGER The minimum number of designs that the designcache contains. Calculated as min occurrence ofSMF108SLDMNCCHDSG.

MAX_CACHE_DESIGN INTEGER The maximum number of designs that the designcache contains. Calculated as max occurrence ofSMF108SLDMNCCHDSG.

NUM_CACHE_SESSION INTEGER The actual number of sessions that the session cachecontains. Calculated as last occurrence ofSMF108SLDMNCCHSSN.

MIN_CACHE_SESSION INTEGER The minimum number of sessions that the sessioncache contains. Calculated as minimum occurrence ofSMF108SLDMNCCHSSN.

MAX_CACHE_SESSION INTEGER The maximum number of sessions that the sessioncache contains. Calculated as maximum occurrence ofSMF108SLDMNCCHSSN.

NUM_CACHE_USER INTEGER The actual number of users that the user cachecontains. Calculated as last occurrence ofSMF108SLDMNCCHUSR.

MIN_CACHE_USER INTEGER The minimum number of users that the user cachecontains. Calculated as min occurrence ofSMF108SLDMNCCHUSR.

MAX_CACHE_USER INTEGER The maximum number of users that the user cachecontains. Calculated as max occurrence ofSMF108SLDMNCCHUSR.

TOTAL_REQUESTS REAL Total number of Lotus Domino for z/OS requestsduring the interval. Calculated as sum ofSMF108SLDMNRQSTST.

DOMINO_TRANS_H, _D:These tables provide hourly and daily data for Lotus Domino for z/OStransactions response time. They contain data from the SMF record type 108,subtype 1.


DOMINO_TRANS_H10 days

DOMINO_TRANS_D45 days










TRANSACTION_TYPE K VARCHAR(40) Transaction types. From DOMINO_TRANS_TYPElookup table.



TRANSACTIONS REAL Total number of transactions of type processed duringthe interval. Calculated as the sum ofSMF108TRTYPENP.

RESPONSE_TIME REAL Total accumulated response time, in seconds, for alltransactions of type that completed during theinterval. Calculated as the sum ofSMF108TRTYPETA/1000.

HOST_TIME REAL Total accumulated host time, in seconds, for alltransactions of type that completed during theinterval. Calculated as the sum of the differencebetween SMF108TRTYPETA and SMF108TRTYPENW.

NET_TIME REAL Total accumulated net wait time, in seconds, for alltransactions of type that completed during theinterval. This is the time that the server has beenwaiting for clients to respond. Calculated as the sumof SMF108TRTYPENW.

TRANSAC_RATE_MIN REAL Minimum number of transactions of type processed ina second. Calculated as the minimum of(SMF108TRTYPENP/collection interval).

TRANSAC_RATE_AVG REAL Average number of transactions of type processed in asecond. Calculated as the average of(SMF108TRTYPENP/collection interval).

TRANSAC_RATE_MAX REAL Maximum number of transactions of type processedin a second. Calculated as the maximum of(SMF108TRTYPENP/collection interval).

RESP_TIME_RATE_MIN REAL Minimum response time rate, in seconds, for alltransactions of type that completed during theinterval. Calculated as the minimum of(SMF108TRTYPETA/SMF108TRTYPENP/1000).

RESP_TYPE_RATE_AVG REAL Average response time rate, in seconds, for alltransactions of type that completed during theinterval. Calculated as the average of(SMF108TRTYPENP/collection interval).



RESP_TIME_RATE_MAX REAL Maximum response time rate, in seconds, for alltransactions of type that completed during theinterval. Calculated as the maximum of(SMF108TRTYPETA/SMF108TRTYPENP/1000).

HOST_TIME_RATE_MIN REAL Minimum host time rate, in seconds, for alltransactions of type that completed during theinterval. Calculated as the minimum of the differencebetween SMF108TRTYPETA and(SMF108TRTYPENW/SMF108TRTYPENP).

HOST_TIME_RATE_AVG REAL Average host time rate, in seconds, for all transactionsof type that completed during the interval. Calculatedas the average of the difference betweenSMF108TRTYPETA and (SMF108TRTYPENW/SMF108TRTYPENP).

HOST_TIME_RATE_MAX REAL Maximum host time rate, in seconds, for alltransactions of type that completed during theinterval. Calculated as the maximum of the differencebetween SMF108TRTYPETA and(SMF108TRTYPENW/SMF108TRTYPENP).

NET_TIME_RATE_MIN REAL Minimum net time rate, in seconds, for alltransactions of type that completed during theinterval. Calculated as the minimum of the ratiobetween SMF108TRTYPENW and SMF108TRTYPENP.

NET_TIME_RATE_AVG REAL Average net time rate, in seconds, for all transactionsof type that completed during the interval. Calculatedas the average of the ratio betweenSMF108TRTYPENW and SMF108TRTYPENP.

NET_TIME_RATE_MAX REAL Maximum net time rate, in seconds, for alltransactions of type that completed during theinterval. Calculated as the maximum of the ratiobetween SMF108TRTYPENW and SMF108TRTYPENP.

DOMINO_USER_ACT_H:This table provides hourly data for the Lotus Domino for z/OS user activity by IPaddress for different connection types. It contains data from the SMF record type108, subtype 2.











IP_ADDRESS K CHAR(16) IP address presenting the request for service. FromSMF108UIPA.

CONNECTION_TYPE K CHAR(4) Type of connection to the Lotus Domino for z/OSserver. From SMF108UTYPE.



NOTES_USER_NAME CHAR(36) Notes user name for NNRP clients. FromSMF108UNAME.

USER_CPU_TIME REAL CPU time in seconds used by this user. FromSMF108UCPU.

BYTES_READ REAL Number of bytes read in this interval. FromSMF108UBR.

BYTES_WRITE REAL Number of bytes written in this interval. FromSMF108UBW.

Lookup tableThis section describes the lookup table specific to the Lotus Domino for z/OScomponent.

DOMINO_TRANS_TYPE:This lookup table defines the Lotus Domino for z/OS transaction types.


TRAN_TYPE K INTEGER The Lotus Domino for z/OS transaction type.

TRAN_DESC VARCHAR The description of the transaction type.

ReportsThis chapter describes the reports provided with the Lotus Domino for z/OScomponent.

Domino I/O & Access Statistics, Hourly reportThis report shows the hourly statistics for Lotus Domino for z/OS I/O and access.


Report ID:DOM01

Report group:Lotus Domino for z/OS reports

Source:DOMINO_SERVER_H

Attributes:DOMINO, I/O, HOURLY

Variables:DATE, SYSTEM-ID, SYSPLEX-NAME



TIME The time when the collection interval expires.

PERIOD NAMEName of the period.

SERVER NAMEServer name.

ASYNC IO READNumber of asynchronous I/O reads during interval.

ASYNC IO WRITENumber of asynchronous I/O writes during interval.

HTTP READSNumber of HTTP reads during interval.

HTTP WRITENumber of HTTP writes during interval.

POP3 READSNumber of POP3 reads during interval.

IMAP READSNumber of IMAP reads during interval.

Domino Messages Statistics, Daily reportThis report shows the daily statistics for Lotus Domino for z/OS and SMTPmessages.


Report ID:DOM02


Domino I/O & Access Statistics, HourlySysplex: All System: All

Date: 2001-02-19

ASYNC ASYNCPERIOD SERVER IO IO

TIME NAME NAME READ WRITE-------- -------- ------------------------------ ----------- ----------23.00.00 NIGHT SUT1/COCPOK 451547 32996422.00.00 NIGHT SUT1/COCPOK 1230876 55710921.00.00 NIGHT SUT1/COCPOK 762275 408052

HTTP HTTP POP3 IMAPREADS WRITE READS READS

----------- ----------- ----------- -----------0 0 0 00 0 0 00 0 0 0

Tivoli Decision Support for z/OS Report: DOM01

Figure 210. Example of a Domino I/O &Access Statistics, Hourly Report


Source:DOMINO_SERVER_D

Attributes:DOMINO, MESSAGES, HOURLY

Variables:FROM_DATE, TO_DATE, SYSTEM_ID, SYSPLEX_NAME


DATE The date when the collection interval expires.


Domino Messages Statistics, DailySysplex: All System: All

DominoMail

SERVER SYSTEM SYSPLEX MessagesDATE NAME ID NAME Routed---------- -------------------------------- ------ -------- -----------2000-01-30 BLUED1/BIGBLUE LN21 PLEX21 1584352000-01-21 NEPTUNE/ATLANTIS LN4 PLEXLN2 02000-03-22 SUT1/COCPOK LN20 PLEXLN20 987972000-03-23 SUT1/COCPOK LN20 PLEXLN20 1146332000-03-24 SUT1/COCPOK METD METPLEX 2792962000-03-25 SUT1/COCPOK METD METPLEX 95432

AvgDomino Domino Avg Avg

& mail size sizeSMTP & Domino SMTPmsgs SMTP mail SMTP msgs SMTPsize msgs transferred messages received messages(KB) transferred (KB) received (KB) sent

---------- ----------- ----------- ----------- ---------- -----------4.115E+00 0 0.0000E+00 0 0.000E+00 00.000E+00 0 0.0000E+00 0 0.000E+00 03.675E+00 10096 3.4200E+00 0 0.000E+00 04.000E+00 11944 2.7544E+00 0 0.000E+00 03.732E+00 28762 3.2931E+00 0 0.000E+00 04.000E+00 9642 3.0104E+00 0 0.000E+00 0

Avg sizeSMTPmsgs Numbersent of(KB) Transaction

---------- -----------0.000E+00 32291030.000E+00 00.000E+00 25919980.000E+00 15942740.000E+00 38602350.000E+00 1186632


Figure 211. Example of a Domino Messages Statistics, Daily Report


SYSTEM IDSystem identifier.

SYSPLEX NAMESysplex name.

Domino Mail Messages RoutedNumber of Lotus Domino for z/OS mail messages routed.

Avg Domino & SMTP msgs size (KB)Average size of Lotus Domino for z/OS mail and SMTP messagesdelivered, in kilobytes.

Domino mail & SMTP msgs transferredNumber of Lotus Domino for z/OS mail and SMTP messages transferred.

Avg size Domino mail transferred (KB)Average size of Lotus Domino for z/OS mail messages transferred, inkilobytes.

STMP messages receivedNumber of SMTP messages received from other servers during interval.

Avg size SMTP msgs received (KB)Average size of SMTP messages received from other servers duringinterval, in kilobytes.

SMTP messages sentNumber of SMTP messages sent to other servers during interval.

Avg size SMTP msgs sent (KB)Average size of SMTP messages sent to other servers during interval, inkilobytes.

Number of TransactionTotal number of transactions processed during interval.

Domino Transaction Statistics, Hourly reportThis report shows the hourly statistics for response time of Lotus Domino for z/OStransactions.


Report ID:DOM03


Source:DOMINO_TRANS_H

Attributes:DOMINO, TRANSACTIONS, HOURLY

Variables:DATE, SERVER_NAME, PERIOD_NAME, TRANSACTION_TYPE



TIME The time when the collection interval expires.


TRANSACTION TYPETransaction types.

TRANSACTIONSTotal number of of transactions of type processed during interval.

Domino Transaction Statistics, HourlySysplex Name: All System Id: All

Transaction type: AllDate: 2001-02-23 Server Name: ’BLUED1/BIGBLUE’

PERIOD TRANSACTIONTIME NAME TYPE TRANSACTIONS-------- -------- ---------------------------------------- ------------16.00.00 WEEKEND DB_REPLINFO_GET_RQST 150016.00.00 WEEKEND OPEN_DB_RQST 187116.00.00 WEEKEND GET_MODIFIED_NOTES_RQST 105116.00.00 WEEKEND UPDATE_NOTE_RQST_ALT 93116.00.00 WEEKEND OPEN_NOTE_RQST 35216.00.00 WEEKEND START_SERVER_RQST 150016.00.00 WEEKEND UPDATE_FOLDER_RQST 10416.00.00 WEEKEND NAME_LOOKUP_RQST 1816.00.00 WEEKEND UPDATE_FILTERS_RQST 208

RESP RESP RESPTRANSAC TRANSAC TRANSAC TIME TIME TIMERATE RATE RATE RATE RATE RATEMIN AVG MAX MIN AVG MAX

---------- ---------- ---------- ---------- ---------- ----------1.160E+00 1.731E+00 2.827E+00 4.233E-04 4.595E-04 5.000E-041.160E+00 2.143E+00 2.863E+00 8.038E-02 1.296E-01 1.548E-011.100E-01 1.752E+00 3.393E+00 5.029E-04 5.090E-04 5.152E-047.333E-02 1.552E+00 3.030E+00 1.736E-02 1.990E-02 2.244E-023.667E-02 5.867E-01 1.137E+00 2.645E-02 2.688E-02 2.730E-021.160E+00 1.731E+00 2.830E+00 3.201E-02 7.981E+01 2.394E+023.467E-01 3.467E-01 3.467E-01 3.252E-02 3.252E-02 3.252E-026.000E-02 6.000E-02 6.000E-02 2.131E-01 2.131E-01 2.131E-016.933E-01 6.933E-01 6.933E-01 5.048E-04 5.048E-04 5.048E-04

HOST HOST HOST NET NET NETTIME TIME TIME TIME TIME TIMERATE RATE RATE RATE RATE RATEMIN AVG MAX MIN AVG MAX

---------- ---------- ---------- ---------- ---------- ----------4.233E-04 4.595E-04 5.000E-04 0.000E+00 0.000E+00 0.000E+008.038E-02 1.296E-01 1.548E-01 0.000E+00 0.000E+00 0.000E+005.029E-04 5.090E-04 5.152E-04 0.000E+00 0.000E+00 0.000E+001.736E-02 1.990E-02 2.244E-02 0.000E+00 0.000E+00 0.000E+002.645E-02 2.688E-02 2.730E-02 0.000E+00 0.000E+00 0.000E+003.141E-02 7.981E+01 2.394E+02 5.517E-04 9.105E-04 1.579E-033.252E-02 3.252E-02 3.252E-02 0.000E+00 0.000E+00 0.000E+002.131E-01 2.131E-01 2.131E-01 0.000E+00 0.000E+00 0.000E+005.048E-04 5.048E-04 5.048E-04 0.000E+00 0.000E+00 0.000E+00


Figure 212. Example of a Domino Transaction Statistics, Hourly Report


TRANSAC RATE MINMinimum number of transactions of type processed in a second.

TRANSAC RATE AVGAverage number of transactions of type processed in a second.

TRANSAC RATE MAXMaximum number of transactions of type processed in a second.

RESP TIME RATE MINMinimum response time rate, in seconds, for all transactions of type thatcompleted during the interval.

RESP TIME RATE AVGAverage response time rate, in seconds, for all transactions of type thatcompleted during the interval.

RESP TIME RATE MAXMaximum response time rate, in seconds, for all transactions of type thatcompleted during the interval.

HOST TIME RATE MINMinimum host time rate, in seconds, for all transactions of type thatcompleted during the interval.

HOST TIME RATE AVGAverage host time rate, in seconds, for all transactions of type thatcompleted during the interval.

HOST TIME RATE MAXMaximum host time rate, in seconds, for all transactions of type thatcompleted during the interval.

NET TIME RATE MINMinimum net time rate, in seconds, for all transactions of type thatcompleted during the interval.

NET TIME RATE AVGAverage net time rate, in seconds, for all transactions of type thatcompleted during the interval.

NET TIME RATE MAXMaximum net time rate, in seconds, for all transactions of type thatcompleted during the interval.

Domino Server DB Cache and Buffer Pool Statistics, Daily reportThis report shows the daily statistics for counters related to buffer pool.


Report ID:DOM04


Source:DOMINO_DB_CACHE_D

Attributes:DOMINO, SERVER, CACHE, BUFFERPOOL

Variables:FROM-DATE, TO-DATE, SYSTEM-ID, SERVER-NAME



DB CACHE MAXMaximum number of DB cache entries.

DB CACHE AVGAverage number of DB cache entries.

DB CACHE INIT OPENNumber of DB cache (initial DB opens).

DB CACHE OVCR REJNumber of DB cache (overcrowding rejections).

DB CACHE HITSNumber of DB cache (hits).

DB CACHE HIGH W MDB cache (high water mark).

NIFPOOL SIZE MINMinimum Database.NIFPool.Size, in bytes.

NIFPOOL SIZE MAXMaximum Database.NIFPool.Size, in bytes.

NIFPOOL USED MINMinimum Database.NIFPool.Used, in bytes.

NIFPOOL USED MAXMaximum Database.NIFPool.Used, in bytes.

NSFPOOL SIZE MINMinimum Database.NSFPool.Size, in bytes.

Domino Server DB Cache and Buffer Pool StatisticsMVS ID =’LN20’ SERVER NAME =’SUT1/COCPOK’

DATE: ’2000-01-21’ TO ’2000-03-25’

DBDB DB CACHE

DB DB CACHE CACHE DB HIGHCACHE CACHE INIT OVCR CACHE WMAX AVG OPEN REJ HITS M

---------- ---------- ---------- ---------- ---------- ----------5.160E+02 2.758E+02 1.317E+05 1.606E+03 1.073E+05 7.740E+02

NIFPOOL NIFPOOL NIFPOOL NIFPOOL NSFPOOL NSFPOOLSIZE SIZE USED USED SIZE SIZEMIN MAX MIN MAX MIN MAX

---------- ---------- ---------- ---------- ---------- ----------1.049E+06 2.097E+07 2.280E+05 1.530E+07 3.146E+06 2.726E+07

NSFPOOL NSFPOOL DB DBUSED USED BUFPOOL BUFPOOLMIN MAX READ WRITE

---------- ---------- ---------- ----------2.750E+06 2.304E+07 9.000E+02 3.660E+02


Figure 213. Example of a Domino Server DB Cache and Buffer Pool Statistics Report


NSFPOOL SIZE MAXMaximum Database.NSFPool.Size, in bytes.

NSFPOOL USED MINMinimum Database.NSFPool.Used, in bytes.

NSFPOOL USED MAXMaximum Database.NSFPool.Used, in bytes.

DB BUFPOOL READNumber of Database.BufferPool reads.

DB BUFPOOL WRITENumber of Database.BufferPool writes.

Domino General Server Statistics, Daily reportThis report shows the daily general server statistics for the NSF buffer pool.


Report ID:DOM05


Source:DOMINO_SERVER_D

Attributes:DOMINO, SERVER, DAILY

Variables:FROM-DATE, TO-DATE, SYSTEM-ID, SYSPLEX-NAME



DATE The date when the collection interval expires.


SYSTEM IDSystem identifier.

Domino General Server Statistics, DailySysplex: All System: All

AverageNumber

SERVER SYSTEM SYSPLEX ConnectedDATE NAME ID NAME Users---------- -------------------------------- ------ -------- -----------2000-01-30 BLUED1/BIGBLUE LN21 PLEX21 4.865E+032000-01-21 NEPTUNE/ATLANTIS LN4 PLEXLN2 0.000E+002000-03-22 SUT1/COCPOK LN20 PLEXLN20 1.829E+03

Maximum Average Maximum Average MaximumNumber Number Number Number Number TotalConnected Active Active Task Task Physical

Users Users Users Used Used Thread--------- ---------- ---------- ---------- ---------- ----------

8001 3.442E+01 1932 4.978E+03 8119 1000 0.000E+00 0 1.170E+02 117 100

2914 1.084E+02 498 1.926E+03 3078 100

Average Maximum Average MaximumPhysical Physical Virtual Virtual Maximum MaximumThread Thread Thread Thread Number TasksUsed Used Used Used Users Updates

---------- ---------- ---------- ---------- ---------- ----------8.240E+00 100 4.865E+03 8006 0 00.000E+00 0 0.000E+00 0 0 01.701E+01 100 1.812E+03 2964 0 0

Maximum Maximum MaximumThread Thread Thread Limit MaximumMail Mail Mail Maximum Concurrent ConcurrentSent Delivered Concurrent Mailboxes Transaction Sessions

---------- ---------- ---------- ---------- ----------- ----------9 8 3 3 - 655350 0 0 4 - 100000 0 0 1 - 65535

NSF NSFMaximum Buffer Buffer Server Server

Concurrent Pool Pool Availability AvailabilityReplication Timeouts 4KB Used Threshold Index----------- ---------- ---------- ---------- ------------ ------------

0 4.893E+04 32768 0 0 1000 4.893E+04 131072 0 0 950 6.374E+04 44032 0 0 99


Figure 214. Example of a Domino General Server Statistics, Daily Report



Average Number Connected UsersAverage number of users.

Maximum Number Connected UsersMaximum number of users.

Average Number Active UsersAverage number of connected users that are currently active.

Maximum Number Active UsersMaximum number of connected users that are currently active.

Average Number Task UsedAverage number of tasks in use during the interval.

Maximum Number Task UsedMaximum number of tasks in use during the interval.

Total Physical ThreadTotal number of server_pool_tasks for physical thread pool threads.

Average Physical Thread UsedAverage number of physical thread pool threads in use during the interval.

Maximum Physical Thread UsedMaximum number of physical thread pool threads in use during theinterval.

Average Virtual Thread UsedAverage number of virtual thread pool threads in use during the interval.

Maximum Virtual Thread UsedMaximum number of virtual thread pool threads in use during theinterval.

Maximum Number UsersMaximum number of users.

Maximum Tasks UpdatesMaximum number of concurrent update tasks.

Maximum Thread Mail SentMaximum number of mail transfer threads.

Maximum Thread Mail DeliveredMaximum number of mail delivery threads.

Maximum Thread Mail ConcurrentMaximum number of concurrent mail transfer threads.

Maximum MailboxesMaximum number of mail.boxes.

Limit Concurrent TransactionLimit for number of concurrent transactions.

Maximum Concurrent SessionsMaximum number of sessions to run concurrently.

Maximum Concurrent ReplicationsMaximum number of concurrent replicators.


TimeoutsNumber of minutes in timeout.

NSF Buffer Pool 4KBMaximum size of NSF buffer pool, in kilobytes.

NSF Buffer Pool UsedNumber of bytes that are being used in the NSF buffer pool.

Server Availability ThresholdServer availability threshold. The threshold that is set to determine when aserver is considered busy.

Server Availability IndexServer availability index.

WebSphere Application Server traditional componentCustomizationv Making input data availablev Using the System Management User Interface Administrator applicationv Editing the SMFPRMxx parmlib memberv Writing records to DASD


Implementing the WebSphere Application Server componentv Planning the implementation processv Considering which components to installv Evaluating the WebSphere Interval componentv Evaluating WebSphere Application Server Activity componentv Installing the components

Data flowv Processing data in unusual formatsv Cross-reference data among parallel repeated sectionsv Mapping between record field names before and after WebSphere Application

Server Version 5.1

Data tables and viewsv WebSphere Application Server Interval component tables and views

– 1. Server Interval subcomponent tables and views– 2. Container Interval subcomponent tables– 3. J2EE & WEB Container Interval subcomponent tables

v WebSphere Application Server Activity component tables and views– WAS_CONNECT_ACTID– 1. Server Activity subcomponent tables and views– 2. Container Activity subcomponent tables and views– 3. J2EE & WEB Container Activity subcomponent tables and views– 4. Request Activity subcomponent tables and views

Reports


v WebSphere Application Server Statistics, Daily Trend reportv WebSphere Application Server Session Statistics, Daily Trend reportv WebSphere Application Server Workload Statistics, Daily Trend reportv WebSphere Application Server JVM Heap Statistics, Daily Trend reportv WebSphere Application Server User Credentials Statistics reportv WebSphere Application Server Web Application Statistics, Daily Trend reportv WebSphere Application Server HTTP Statistics, Daily Trend reportv WebSphere J2EE Container Statistics, Daily Trend report

CustomizationBefore you can use the WebSphere Application Server component to collect dataand create reports, you must customize the component by making input dataavailable.

Making input data availableThis section describes what you have to do to enable SMF recording. EnablingSMF recording for the WebSphere Application Server can be achieved byperforming the following steps:v Using the Server Definition of the System Management User Interface

Administrator applicationv Editing the SMFPRMxx parmlib member.

Using the System Management User Interface Administratorapplication

About this task

Before you begin please ensure you the necessary authorization to theAdministration application. Follow these steps to enable SMF recording:

Procedure1. Open the Administration application and start a new conversation.2. Select the server for which you want to enable SMF recording.3. Select one or more check boxes for SMF recording. The available choices are the

following:

Server activity record.Check the checkbox titled "Write Server Activity SMF Records..."

Container activity record.Check the checkbox titled "Write Container Activity SMF Records..."

Server interval record.Check the checkbox titled "Write Server Interval SMF Records..."

Container interval record.Check the checkbox titled "Write Container Interval SMF Records..."

J2EE Container activity record.Check the checkbox titled "Write Container activity SMF Records...inthe J2EE Server properties definition"

J2EE Container interval record.Check the checkbox titled "Write Container interval SMF Records...inthe J2EE Server properties definition"


WebContainer activity record.WebContainer activity records are automatically enabled with theenabling of J2EE Container activity records

WebContainer interval record.WebContainer interval records are automatically enabled with theenabling of J2EE Container interval records.

Request Activity Record.You can activate this record through the administrative console bysetting server_SMF_request_activity_enabled=1 (orserver_SMF_request_activity_enabled=true).

If you do not want these records to be generated, you can setserver_SMF_request_activity_enabled=0 (orserver_SMF_request_activity_enabled=false), which turns off thecreation of this SMF record type. This is the default value for thisproperty.

4. Set the interval length.5. Save the server definition.6. Validate the new conversation.7. Mark all tasks completed.8. Activate the new conversation.

Results

The steps for using the System Management User Interface Administrationapplication are completed when the new conversation is successfully activated.

Note: For additional information on enabling SMF recording for WebSphereApplication Server through the Server Definition of the System Management UserInterface Administrator application, see WebSphere Application Server for z/OS andOS/390: System Management User Interface, SA22-7838 or following ones.

Editing the SMFPRMxx parmlib member

About this task

Before you begin please make a working copy of the sample PARMLIB memberSMFPRMYL. Follow these steps to edit the SMFPRMxx parmlib member andenable SMF recording for WebSphere Application Server:

Procedure1. Insert a statement to indicate SMF recording.

See the z/OS MVS Initialization and Tuning Guide, SA22-7591.2. Insert a SYS statement to indicate the types of SMF records you want the

system to create.Use SYS(TYPE(120:120)) to select WebSphere Application Server type 120records only.

Note: Try to keep the number of selected record types small to minimize theperformance impact.

3. If an interval length was not defined on the server definition through theAdministration application, then specify the interval in which you want theinterval records to be created.


4. The server and container interval records will use either:v The value specified in the server/container definition as specified in the SM

User Interfacev The interval specified in the SMF parmlib member (from the SMF product

settings) if you specify length 0.You can specify the interval in which you want the server and containersinterval records created in the SMFPRMxx parmlib member, if no interval wasspecified by the SM EUI for the server or containers definition. The defaultSMF recording interval is 30 minutes. For more details, see WebSphereApplication Server for z/OS and OS/390: System Management User Interface.

Writing records to DASDBefore you begin please make sure you have your modified PARMLIB memberSMFPRMxx. Follow this step to start writing records to DASD:v Launch the following command:

t smf=xx

where xx is the suffix of the SMF parmlib member (SMFPRMxx)

Note: For more information, see z/OS MVS System Management Facilities (SMF),SA22-7630. Writing records to DASD has been completed successfully when thedata is recorded in the data set which is specified in the SMFPRMxx.

Log and record definitionsThe WebSphere Application Server components collect records from the systemmanagement facility (SMF) logs. WebSphere Application Server writes two generaltypes of SMF records:

Activity recordsThese consist of data gathered as each activity within a server iscompleted. An activity is a logical unit of business function. It can be aserver or user-initiated transaction. These records can be used to performbasic charge-back, application profiling and, problem determination. Theyare useful both in the development environment and for problemdetermination purposes.

Table 23. Input records to the WebSphere Application Server Activity component


120.1 SMF_120_1 The server activity SMF recordis used to record the activitythat is running on aWebSphere for z/OSApplication Server. A singlerecord is created for eachactivity that is run either on aserver or on a server instance.If the activity runs on multipleservers, then a record iswritten for each server. Youcan activate this recordthrough the server definition ofthe System Management UserInterface by checking the WriteServer Activity SMF Recordscheck box.


Table 23. Input records to the WebSphere Application Server Activity component (continued)


120.2 SMF_120_2 The purpose of the containeractivity SMF record is to recordactivity that is running inside acontainer located on aWebSphere transaction Server.A single record is created foreach activity that is run insidea container located in aWebSphere transaction server.If the activity runs on multipleservers, then multiple recordsare written for the activity. Youcan activate this recordthrough the server definition ofthe System Management UserInterface by checking the WriteContainer Activity SMFRecords check box.

120.5 SMF_120_5 The purpose of the J2EEcontainer activity SMF recordis to record activity within aJ2EE container that is locatedon a WebSphere transactionserver. A single record iscreated for each activity that isrun within a J2EE containerlocated on a WebSpheretransaction server. You canactivate this record through theserver definition of the SystemsManagement User Interface bychecking the Write ContainerActivity SMF Records checkbox.




120.7 SMF_120_7 The purpose of theWebContainer activity SMFrecord is to record activitywithin a Web containerrunning on a WebSphere forz/OS transaction server. TheWeb container is deployedwithin an EJB and runs withinthe EJB container. The Webcontainer acts as a Web serverhandling HTTP Sessions andServlets. The EJB container isnot aware of the work the Webcontainer does.

Instead, the EJB container onlyrecords that the EJB hasdispatched. Meanwhile, theWeb container gathers thedetailed information, such asHttpSessions, Servlets and theirrespective performance data. Asingle WebContainer Activityrecord is created for eachactivity that is run within aWebContainer. WebContainerSMF recording is activated anddeactivated along with theactivation and deactivation ofSMF recording for the J2EEcontainer.




120.9 SMF_120_9 The purpose of the RequestActivity SMF record is torecord activity that is runninginside the product. This recordis produced whenever a serverreceives a request.

When you do capacityplanning, you need to look atthe costs that are involved inrunning requests and howmany requests you processover a set period of time. Youcan use the SMF Subtype 9record to monitor whichrequests are associated withwhich applications, how manyrequests you get, and howmuch resource each requestuses. You can also use thisrecord to identify theapplication involved, and theCPU time that the requestconsumes. Because a newrecord is created for eachrequest, you can determine thenumber of requests that youget over a specific length oftime.

Interval recordsThese consist of data gathered at installation-specified intervals andprovide reliability information. They are useful in the productionenvironment.


Table 24. Input records to the WebSphere Application Server Interval component


120.3 SMF_120_3 The purpose of the serverinterval SMF record is torecord activity that is runningon a WebSphere for z/OSapplication server. This recordis produced at regular intervalsand is an aggregation of thework that runs on the serverinstance during the interval. Asingle record is created foreach server instance that hasinterval recording activityduring the interval. If a serverhas multiple server instances,then a record for each serverinstance is written and therecords must be merged afterprocessing to get a completeview of the work that runs onthe server. You can activate thisrecord through the serverdefinition of the SystemsManagement User Interface bychecking the Write ServerInterval SMF Records checkbox.

120.4 SMF_120_4 The purpose of the containerinterval SMF record is torecord activity that is runninginside a container locatedinside the WebSpheretransaction server. This recordis produced at regular intervalsand is an aggregation of theactivities running inside acontainer during the interval.A single record is created foreach active container located ina WebSphere transaction serverwithin the interval beingrecorded. If there is more thanone server instance associatedwith a server, there will be arecord for the container fromeach server instance. To get acommon view of the workrunning in the containerduring the interval, you mustmerge the records afterprocessing. You can activatethis record through the serverdefinition of the SystemsManagement User Interface bychecking the Write ContainerInterval SMF Records checkbox.


Table 24. Input records to the WebSphere Application Server Interval component (continued)


120.6 SMF_120_6 The purpose of the J2EEcontainer interval SMF recordis to record the activity withina J2EE container that is locatedon the WebSphere transactionserver. This record is producedat regular intervals and is anaggregation of the activitiesrunning inside a J2EE containerduring the interval. A singlerecord is created for eachactive J2EE container locatedon a WebSphere transactionserver within the interval beingrecorded. If there is more thanone server instance associatedwith a server, a record for thecontainer will exist for eachserver instance. To get acommon view of the workrunning in the J2EE containerduring the interval, you haveto merge the records afterprocessing. You can activatethis record through the J2EEserver definition of the SystemsManagement User Interface bychecking the Write ContainerInterval SMF Records checkbox.


Table 24. Input records to the WebSphere Application Server Interval component (continued)


120.8 SMF_120_8 The purpose of theWebContainer interval SMFrecord is to record activitywithin a Web Containerrunning on a WebSphereApplication Server for z/Ostransaction server. The Webcontainer run environmentconsists of an EJB that isdeployed into the EJBcontainer. The Web containeracts as a Web Server handlingHTTP Sessions and Servlets.The EJB container is not awareof the purpose of the WebContainer activity record and itonly records that the EJB hasbeen dispatched, but does notgather any of the detailedinformation, such as HTTPsessions, Servlets, and theirrespective performance data.

A single WebContainer recordis created for eachWebContainer. In addition todata that is associated with anindividual activity, there aresome cases of Web Containerwork that are performedoutside the scope of anindividual request. Forexample, some instances ofHTTP session finalization andHTTP session invalidation areperformed asynchronously. Insuch a case a WebContainerinterval record would recorddata. WebContainer SMFrecording is activated anddeactivated along withactivation and deactivation ofSMF recording for the J2EEcontainer.

Implementing the WebSphere Application Server componentThis chapter describes how to plan for and set up the WebSphere ApplicationServer component. It supplements the procedure in the Administration Guide forinstalling a component with information specific to the WebSphere feature.

Planning the implementation processBefore installing the WebSphere Application Server component, you must followthese steps to plan the implementation process:v Describe user’s tasks. And, then determine what data the WebSphere

Application Server component must gather to help users accomplish those tasks.


v Determine which components you must install to meet the user’s needsv Determine the administration tasks you must perform for the selected

components and make any decisions required by these tasks. These tasks helpyou customize Tivoli Decision Support for z/OS and the WebSphere ApplicationServer component to work efficiently and effectively with your computersystem.

v For each selected component, determine the tasks you must perform tocustomize the supported products to work with Tivoli Decision Support forz/OS and with the WebSphere Application Server component.

If this is your first exercise in implementation planning, follow all these steps toensure that the WebSphere Application Server component implementation isconsistent. If you are reading this chapter to acquire information to modify yoursystem, you might not need to perform all of these tasks. Use the planning processto prepare for these main customization tasks:v Customizing WebSphere Application Server to gather the performance data that

is written to SMF log files. You customize this product to generate the datarequired by the components you install.

v Defining environment data, which is all the information (besides the input data)that the WebSphere Application Server component needs to create reports.Environment data controls the data collection process and provides moreinformation in the reports.

Considering which components to installYour most critical planning task is determining what kind of information usersneed from the WebSphere Application Server component. For example, users maybe interested only in Server statistics data or Web Application response time.Installing only those parts of the needed feature to meet the user requirementsensures that the feature benefits users while it minimizes the performance impactcaused by data collection and interpretation activities. The WebSphere ApplicationServer component uses these information categories to select the information forcomponents:v Interval

It consists of data gathered at installation-specified intervals and providescapacity planning and reliability information. It is suitable for a productionenvironment.

v Activity

Each activity within a server is completed. An activity is a logical unit ofbusiness function. It can be a server or use-initiated transaction. This data can beused to perform basic charge-back, application profiling and, problemdetermination . It is suitable for development-test environment.

WebSphere Application Server SMF type 120 records are generated fromWebSphere Application Server servers where SMF recording is enabled. They canbe as detailed as one record per transaction (although this could harmperformance). They are mainly used to gather application statistics rather thancharge- back (for example, CPU time is not recorded in an SMF type 120 records).Type 120 SMF records contain information about both the WebSphere ApplicationServer and Containers performance and usage. If you wish to record activity at theapplication level on your WebSphere Application Server server, type 120 SMFrecords are a primary source of information.

As stated earlier, the general recommendation is not to request specific SMFrecords unless you are actually going to use them. If knowledge of WebSphere


application performance is important, we recommend that you enable therecording of type 120 SMF records. You may find that running with SMF type 120interval records in production is appropriate, since these records give informationspecific to WebSphere applications such as response time for J2EE artifacts, bytestransferred, and so forth.

If you do choose to run with SMF type 120 records enabled, we recommend thatyou use Interval SMF records rather than Activity records. Although TivoliDecision Support for z/OS can process data for all these information categories,you might not need all the data.

The WebSphere Application Server component is divided into two maincomponents and each component is further divided into three subcomponents.Components and subcomponents provide support for specific subsystems.Consider carefully which components to install. Components are groups of TivoliDecision Support for z/OS objects (for example, predefined update definitions,data tables, and reports).

If you find that you need reports from a component that you have not installed,you must install that component and then wait several days or weeks until enoughdata has been collected to create reports. However, if you install more componentsthan you need, Tivoli Decision Support for z/OS collects needless data, whichtakes up disk space and uses processor time.

Evaluating the WebSphere Interval componentThe WebSphere Interval Component, particularly suitable for a productionenvironment, provides the performance data from Interval records and containsthree subcomponents.

Server Interval subcomponentThis subcomponent contains the Tivoli Decision Support for z/OS objectsnecessary to summarize activity that is running on a WebSphereApplication Server for z/OS application server and an aggregation of thework that runs on the server instance during the interval.

MOFW Container Interval subcomponentThis subcomponent contains the Tivoli Decision Support for z/OS objectsnecessary to summarize activity that is running on a MOFW containerlocated on the WebSphere transaction server during the interval.

J2EE & WebContainer Interval subcomponentThis subcomponent contains the Tivoli Decision Support for z/OS objectsnecessary to summarize activity within J2EE and Web Containers that arelocated on the WebSphere transaction server. This is an aggregation of theactivities running inside a J2EE and Web containers during the interval.J2EE and WebContainer have been grouped together because theWebContainer SMF recording activation is totally dependent on theactivation of SMF recording for the J2EE container.

Evaluating WebSphere Application Server Activity componentThe WebSphere Application Server Activity Component provides the performancedata from Activity records and contains four subcomponents:

Server Activity subcomponentThis subcomponent contains the Tivoli Decision Support for z/OS objectsnecessary to report activity that is running on a WebSphere for z/OSApplication Server. A single entry is created for each activity that runs on aserver or server instance.


MOFW Container Activity subcomponentThis subcomponent contains the Tivoli Decision Support for z/OS objectsnecessary to report activity that is running inside a MOFW containerlocated on the WebSphere transaction Server. A single entry is created foreach activity that runs on a container located in a WebSphere transactionServer.

J2EE & WebContainer Activity subcomponentThis subcomponent contains the Tivoli Decision Support for z/OS objectsnecessary to report activity that is running inside J2EE and Web containerslocated on the WebSphere transaction server. A single entry is created foreach activity that is run inside a container located on a WebSpheretransaction server. J2EE and WebContainer have been grouped togetherbecause the WebContainer SMF recording activation/deactivation is totallydependent on the activation/deactivation of SMF recording for the J2EEcontainer.

Request Activity SubcomponentThis subcomponent contains the Tivoli Decision Support for z/OS objectsnecessary to report request activity that is running inside the product. Theactivity is summarized at an hourly, daily and monthly level by Controllerand Application. Views provide averages for the requests at each level.

Installing the componentsAfter the systems programmer has successfully installed the Tivoli DecisionSupport for z/OS base and features, you can choose whether to load any featurecomponents and subcomponents. Tivoli Decision Support for z/OS installs thenecessary log and record definitions, record procedures, and update definitions forTivoli Decision Support for z/OS system tables. The product also installs thepredefined tables (described in Data tables and views) and reports (described inReports). Each component and subcomponent of the WebSphere Application Servercomponent is optional.

Data flowThe log collector initiates SMF type 120 record processing according to WebSphereApplication Server record definitions. The log collector uses one of eight recorddefinitions to map data in the SMF log. It selects the appropriate definitionsaccording to the type of data recorded by WebSphere.

Processing data in unusual formatsUnicode Format

The WebSphere Application Server SMF type 120 subtypes 5, 6, 7 and 8records introduce the utilization of fields in Unicode format that coexistwith EBCIDIC format fields in the same record sections. Unicode is auniversal encoding scheme for written characters and text that enables theexchange of data internationally. It provides a character set standard thatcan be used all over the world. It uses a 16-bit encoding that provides codepoints for more than 65,000 characters and an extension called UTF-16 thatallows as many as a million more characters to be encoded.

WebSphere Application Server uses an extension mechanism calledUTF-16BE.

Unfortunately the basic symbols of the Tivoli Decision Support for z/OSlog collector language are single-byte EBCDIC characters. Within somelanguage elements, you can also enter sequences of double-byte characters.Each such sequence must be enclosed between (single-byte) shift-out x’0E’


and shift-in x’0F’ characters. Unless otherwise stated, all characters namedbelow are single-byte EBCDIC characters.

A letter is one of the characters A through Z and a through z, or any of thethree alphabetical extenders for national languages. (The three alphabeticalextenders are X’5B’, X’7B’ and X’7C’. Using code pages 37 and 500, theydisplay as $, # and @ respectively). A digit is any of the characters 0through 9. Currently, the Tivoli Decision Support for z/OS log collectordoes not support the Unicode format fields.

Currently, the WebSphere Application Server component record proceduresare able to handle only the Unicode Version 3.0 of the Unicode Standardbased on ISO 8859-1 ( Basic Latin and Latin 1 Supplement: Range0000-00FF) Unicode Character (ISO 8859-1 is the unique standard extensionthat includes a number of European alphabetical characters and it is usedby HTTP and some operating systems) and to translate a character stringfrom Unicode to EBCDIC.

Java™ Epoch Time FormatSome WebSphere Application Server SMF record fields (for exampleSM120WJ3 or SM120WAU) use the Epoch time format (number ofmilliseconds from 01/01/1970) not supported by Tivoli Decision Supportfor z/OS log collector. This time format represents:

loadedSince...:Timestamp from System.currentTimeMillis() when theservlets was loaded, in EBCDIC Hexadecimal format.

For example: The data as it appears in the record could have the formate7ef7c577c, which needs to be converted to a Java long: 996155348860. TheJava long digits can be converted to java.util.Date:Thu Jul. 26 15:49:08GMT+02:00 2001.

The Tivoli Decision Support for z/OS log collector will look (consideringthe example provided) something like the following:

x’40404040404085F78586F83F5F7F783’

Basically the Epoch time format is expressed in Hexadecimal using acombination of hexadecimal EBCDIC value corresponding to the alphabeticand numeric signs

(0, 1, 2, 3, 4, 5, 6, 7, 8, 9, a, b, c, d, e, f)

The number from 0 to 9 and the first six lower case letters.

The Tivoli Decision Support for z/OS WebSphere Application Servercomponent record procedures convert this date/time format intoYYYYDDDF format for the date and TIME (1/100s) hundredths of secondspast midnight.

Cross-reference data among parallel repeated sectionsAnother distinctive feature of the WebSphere Application Server component is thatthe SMF type 120 records contain data in unusual format, in particular the massiveutilization of repeated section containing triplets referring to same kind of repeatedsection should be highlighted. Exit routines that access SMF records withsub-sections are coded using triplets (offset to xxx section, number of xxx sections,length of xxx section) rather than coding the exit to access fields directly. Aninstallation can use the triplets to calculate the location of each section. Recordsthat contain sections are a common occurrence. In many records, sections arerepeated.


A repeated section is a section that occurs more than once in a record. The numberof times a section appears in the record can be fixed, or it can be specified by datawithin the record. From the Tivoli Decision Support for z/OS point of view tospecify a repeated section is similar to specifying a section that is not repeated. Toidentify the section, use the SECTION clause. The value contained in theOffset_expression field specifies the offset of the first occurrence of this section.

The value in length_expression specifies the length of each occurrence and thenumber_expression the number of occurrences of the section. Unfortunately thisWebSphere SMF structure is not currently supported by the Tivoli DecisionSupport for z/OS log collector (for more details, refer to Language Guide andReference .

The following table shows the new record procedures introduced with theWebSphere Application Server component.

SMF Record in Input

Cross-reference databetween parallelrepeated sections

Fields in unusualFormats Record Procedure SMF Record Output

SMF_120_5 Yes Yes DRL2SA05 SMF_120_5_X

SMF_120_6 Yes Yes DRL2SI06 SMF_120_6_X

SMF_120_7 Yes Yes DRL2SA07 SMF_120_7_X

SMF_120_8 Yes Yes DRL2SI08 SMF_120_8_X

With the WebSphere Application Server component installed, Tivoli DecisionSupport for z/OS has system tables information that allows the log collector to:v Map the different subtypes of SMF type 120 records through its record

definitionsv Create intermediate records (prefix=_X) of various types through its record

proceduresv Store data in tables through its update definitions.

The log collector uses log and record definitions, record procedures, and updatedefinitions to move data from an SMF type 120 record into Tivoli Decision Supportfor z/OS tables. The log collector uses a record definition to identify an SMF type120 record and to map its data according to the record subtype. When the logcollector finds an SMF type record, it uses the WebSphere Application Servercomponent record definitions to map the data for further processing. Some recorddefinitions cause the log collector to use record procedures that create intermediaterecords.

Because the WebSphere Application Server record procedure conversion is basedon ISO 8859-1 (C0 Controls-Basic Latin and C1 Controls and Latin-1 Supplement,Range x’0000-x’00FF) Unicode Character, the record procedures handle any errorsof Unicode characters having the first byte different from zero. By replacing theincorrect unicode character with blank x’40’ and letting you choose one, theprogram proceeds.

You can do this by specifying the SET statement in the Tivoli Decision Supportcollect job, and setting the CONVERSION_ERROR variable to one of values shownin the following table.

SET CONVERSION_ERROR =’conversion error value’;


CONVERSION ERROR VALUERECORD PROCEDURERESPONSE

IGNORE Ignore the error and builtthe record.

WARNING Write Error Message andbuilt the record.

ERROR Write Error Message andSkip the record

SEVERE Write Error Message andTerminate Processing

If a value specified is different from one of those reported in the above list than anerror message is issued in the DRLOUT dataset

Recordproc_name: Error. The PARM value parm_value passed to procedure isinvalid

A default value (ERROR) is provided using the PARM expression in the definerecordproc statement

DEFINE RECORDPROC recordproc_name

FOR record_ name

PARM VALUE (: CONVERSION_ERROR, ’ERROR’);

If a conversion error is encountered and CONVERSION_ERROR is differentfrom’IGNORE’ then an error message is issued in the DRLOUT data set:

Recordproc_name: A Unicode to EBCDIC Conversion error occurred

Similarly any error due to WebSphere Application Server while recording the datein Epoch format or Tivoli Decision Support for z/OS to convert it will be handledwith the same logic as for Unicode-EBCDIC conversion. If theCONVERSION_ERROR parameter is different from’IGNORE’, then an errormessage is issued in the DRLOUT data set:

Recordproc_name: A Wrong Epoch format time found in record

And the record will be handled according to your choice ofCONVERSION_ERROR value, while the first byte of the converted field is set to’I’(Invalid) in order to avoid to be used in the UPDATE object in case the record isnot skipped.

Mapping between record field names before and afterWebSphere Application Server Version 5.1For a mapping between the name of record fields before and after WebSphereApplication Server Version 5.1, see the following table.


Table 25. Mapping between record field names before and after WebSphere 5.1

Record Name andMember Record Section

Field Name prior to WebSphereApplication Server 5.1

Field Name from WebSphereApplication Server 5.1

SMF_120_1DRLRS121

Server activity SM120SNMSM120SINSM120SNRSM120STY

SM120SNASM120INASM120SNMSM120J2E

JVM heap SM120JSRSM120JHTSM120JGCSM120JFSSM120JTS

SM120JHASM120JHHSM120JHCSM120JHFSM120JHT

SMF_120_3DRLRS123

Server interval SM120HNMSM120SNMSM120SIN1SM120NGTSM120NLTSM120STYSM120CELSM12NOD

SM120HN2SM120SNISM120INISM120NG2SM120NL2SM1200J2SM120CL1SM120ND1

Server servant SM120SRASM120NHISM120HTSSM120HTLSM120HTN

SM120SSASM120SNTSM120SSOSM120SSLSM120SSN

Heap ID SM120HIDSM120TGCSM120ITSSM120XTSSM120ATSSM120IFSSM120XFSSM120AFS

SM120HIHSM120HICSM120HI1SM120HI2SM120HI3SM120HI4SM120HI5SM120HI6

SMF_120_5DRLRSJWA

J2EE containeractivity

SM120CELSM120NOD

SM120CL2SM120ND2

SMF_120_6DRLRSJWI

J2EE containerinterval

SM120CELSM120NOD

SM120CL3SM120ND3

SMF_120_7DRLRSJWA

Web container activity SM120CELSM120NOD

SM120CL4SM120ND4

SMF_120_8DRLRSJWI

Web containerinterval

SM120CELSM120NOD

SM120CL5SM120ND5

Data tables and viewsThis chapter describes data tables and views used by WebSphere ApplicationServer for z/OS Version 4 and Version 5 components. It also explains the relationsof tables and views with records, updates, and tablespaces. All the Tivoli DecisionSupport for z/OS WebSphere objects are defined and initialized in the DRLIWASmember.

Depending on the WebSphere Application Server for z/OS version, different fieldsand tables are used. For example, CELL_NAME and NODE_NAME fields are used


with WebSphere Application Server for z/OS Version 5; their value becomes N/Awith WebSphere Application Server for z/OS Version 4.

Component Subcomponent DB2 Tables and Views

WebSphere ApplicationServer Interval

Server Interval See 1. Server Interval subcomponent tables and views.

Container Interval See 2. Container Interval subcomponent tables.

J2EE and Web ContainerInterval

See 3. J2EE & WEB Container Interval subcomponenttables.

WebSphere ApplicationServer Activity

See WebSphere Application Server Activity componenttables and views.

Server Activity See 1. Server Activity subcomponent tables and views.

Container Activity See 2. Container Activity subcomponent tables andviews.

J2EE and Web ContainerActivity

See 3. J2EE & WEB Container Activity subcomponenttables and views.

Request Activity See 4. Request Activity subcomponent tables and views.

Note: In the descriptions of tables and views, WebSphere Application Server forz/OS is referred to as WebSphere for z/OS.

WebSphere Application Server Interval component tables andviewsThis section describes the tables and views of the WebSphere Application ServerInterval subcomponents.

Table 26. Data tables and views in the WebSphere Application Server Interval subcomponents

WebSphere Application Server Interval subcomponents Data tables

1. Server Interval WAS_INT_HEAP_H,_DWAS_INT_SERVER_H,_D,_MWAS_INT_SERVER_HV,_DV,_MV

2. Container Interval WAS_INT_METHOD_HWAS_INT_CLASS_H,_DWAS_INT_CONTAIN_H,_D,_M

3. J2EE & Web Container Interval WAS_INT_SERVLETS_HWAS_INT_WEBAPPL_H,_DWAS_INT_HTTPSESS_H,_D,_MWAS_INT_BEANMTHD_HWAS_INT_J2EECNT_H,_D,_W

1. Server Interval subcomponent tables and views:This section describes the tables and views of the Server Interval subcomponent.

WAS_INT_HEAP_H,_D

These tables provide hourly (daily) statistics on Java Virtual Machine whereWebSphere Application Server for z/OS Version 5 is running. From recordSMF_120_3.

The default retention period for these tables is:

WAS_INT_HEAP_H10 days


WAS_INT_HEAP_D45 days

Column name Data Type Description

DATE K DATE Date of the mid measurement. From SM120SST andSM120SET.

TIME K TIME Time of the mid measurement. From SM120SST andSM120SET.

CELL_NAME K CHAR(8) WebSphere for z/OS transaction server cell name.From SM120CL1 (prior to WebSphere ApplicationServer Version 5.1, this field was named SM120CEL).

NODE_NAME K CHAR(8) WebSphere for z/OS transaction server node name.From SM120ND1 (prior to WebSphere ApplicationServer Version 5.1, this field was named SM120NOD).

WEB_SER_NAME K CHAR(8) WebSphere for z/OS cluster name. From SM120SNI(prior to WebSphere Application Server Version 5.1,this field was named SM120SNM).

WEB_SER_INSTA_NAME K CHAR(8) WebSphere for z/OS transaction server instance name.From SM120SINI (prior to WebSphere ApplicationServer Version 5.1, this field was named SM120IN1).

MVS_SYSTEM_ID K CHAR(4) System identification (from the SMFPRMxx SIDparameter). From SM120SID.

SYSPLEX_NAME K CHAR(8) Sysplex Name. From SM120HN2 (prior to WebSphereApplication Server Version 5.1, this field was namedSM120HNM).

SUBSYSTEM_ID K CHAR(4) Subsystem identifier from the SUBSYS parameter.From SM120SSI.

PERIOD K CHAR(8) Name of the period. This is derived using fieldsSM120SST and SMF120SET from the record asparameters in the PERIOD function.

HEAP_ID K INTEGER Heap ID. From SM120HIH (prior to WebSphereApplication Server Version 5.1, this field was namedSM120HID).

AVG_FRE_STORAGE_KB REAL Average free storage in KBytes. Calculated as Averageof SM120HI6/1024 (prior to WebSphere ApplicationServer Version 5.1, this field was named SM120AFS).

AVG_TOT_STORAGE_KB REAL Average total storage in KBytes. Calculated asAverage of SM120HI3/1024 (prior to WebSphereApplication Server Version 5.1, this field was namedSM120ATS).

GARBAGE_COLLECTION REAL Total garbage collection count. Calculated as SUM ofSM120HIC (prior to WebSphere Application ServerVersion 5.1, this field was named SM120TGC).

MAX_FRE_STORAGE_KB REAL Maximum free storage in KBytes. Calculated asMaximum occurrence of SM120HI5/1024 (prior toWebSphere Application Server Version 5.1, this fieldwas named SM120XFS).

MAX_TOT_STORAGE_KB REAL Maximum total storage in KBytes. Calculated asMaximum occurrence of SM120HI2/1024 (prior toWebSphere Application Server Version 5.1, this fieldwas named SM120XTS).

MEASURED_SEC REAL Polling interval in seconds. Calculated as the SUM ofdifferences between SM120SET and SM120SST.



MIN_FRE_STORAGE_KB REAL Minimum free storage in KBytes. Calculated asMinimum occurrence of SM120HI4/1024 (prior toWebSphere Application Server Version 5.1, this fieldwas named SM120IFS).

MIN_TOT_STORAGE_KB REAL Minimum total storage in KBytes. Calculated asMinimum occurrence of SM120HI1/1024 (prior toWebSphere Application Server Version 5.1, this fieldwas named SM120ITS).

WAS_INT_SERVER_H,_D,_M

These tables provide hourly, daily, and monthly statistics on activity that isrunning on a WebSphere Application Server for z/OS and is the aggregate of thework that ran inside a server instance during the interval.


WAS_INT_SERVER_H10 days

WAS_INT_SERVER_D45 days

WAS_INT_SERVER_M475 days

Column Name Data Type Description


TIME K TIME Time of the mid measurement. From SM120SST andSM120SET. Valid only for hourly table.


NODE_NAME k CHAR(8) WebSphere for z/OS transaction server node name.From SM120ND1 (prior to WebSphere ApplicationServer Version 5.1, this field was named SM120NOD).

WEB_SER_NAME K CHAR (8) WebSphere for z/OS transaction server name. FromSM120SNI (prior to WebSphere Application ServerVersion 5.1, this field was named SM120SNM).

WEB_SER_INSTA_NAME K CHAR (8) WebSphere for z/OS transaction server instance name.From SM120INI (prior to WebSphere ApplicationServer Version 5.1, this field was named SM120SIN1).

MVS_SYSTEM_ID K CHAR (4) System identifier (from the SMFPRMxx SIDparameter). From SM120SID.

SYSPLEX_NAME K CHAR (8) Sysplex Name. From SM120HN2 (prior to WebSphereApplication Server Version 5.1, this field was namedSM120HNM).

SUBSYSTEM_ID K CHAR (4) Subsystem identifier from SUBSYS parameter. FromSM120SSI.

PERIOD K CHAR (8) Name of the period. This is derived using fieldsSM120SST and SMF120SET from the record asparameters in the PERIOD function.



HTTP_ACTIVE_SESS REAL Number of HTTP communication sessions that havebeen attached and active within the server instanceduring the interval. Calculated as SUM ofSM120NHA.

HTTP_EXIST_SES REAL Number of HTTP communication sessions that existat the end of the interval. Calculated as LASToccurrence of SM120NHS. No longer significant forWebSphere Application Server Version 5.1, and later.

HTTPCLNT_SERVER_KB FLOAT Number of Kbytes that have been transferred fromthe server to all HTTP attached clients.

v Calculated as SUM of SM120IFH/1024 ifSM120BFH=’FFFFFFFF’X.

v From SM120BFH/1024 if SM120BFH other than’FFFFFFFF’X.

v From SM120BFH/1024 prior to WebSphereApplication Server Version 6.

KB_RCVD_GCLIENTS FLOAT Number of KBytes that have been transferred to theserver from all attached clients. Calculated as SUM of

v SM120ITS/1024 if SM120BTS=’FFFFFFFF’X.

v From SM120BTS/1024 if SM120BTS other than’FFFFFFFF’X.

v From SM120BTS/1024 prior to WebSphereApplication Server Version 6.

KB_RCVD_LCLIENTS FLOAT Number of KBytes that have been transferred to theserver from all locally attached clients.

v Calculated as SUM of SM120ITL/1024 ifSM120BTL=’FFFFFFFF’X.

v From SM120BTL/1024 if SM120BTL other than’FFFFFFFF’X.

v From SM120BTL/1024 prior to WebSphereApplication Server Version 6.

KB_SENT_GCLIENTS FLOAT Number of KBytes that have been sent from theserver to all the attached clients.

v Calculated as SUM of SM120IFS/1024 ifSM120BFS=’FFFFFFFF’X.

v From SM120BFS/1024 if SM120BFS other than’FFFFFFFF’X.

v From SM120BFS/1024 prior to WebSphereApplication Server Version 6.

KB_SENT_LCLIENTS FLOAT Number of KBytes that have been sent from theserver to all locally attached clients.

v Calculated as SUM of SM120IFL/1024 ifSM120BFL=’FFFFFFFF’X.

v From SM120BFL/1024 if SM120BFL other than’FFFFFFFF’X.

v From SM120BFL/1024 prior to WebSphereApplication Server Version 6.



KB_SENT_RCLIENTS FLOAT Number of KBytes that have been sent from theserver to all remotely attached clients.

v Calculated as SUM of SM120IFR/1024 ifSM120BFR=’FFFFFFFF’X.

v From SM120BFR/1024 if SM120BFR other than’FFFFFFFF’X.

v From SM120BFR/1024 prior to WebSphereApplication Server Version 6.

KB_RCVD_RCLIENTS FLOAT Number of KBytes that have been transferred to theserver from all remotely attached clients.

v Calculated as SUM of SM120ITR/1024 ifSM120BTR=’FFFFFFFF’X.

v From SM120BTR/1024 if SM120BTR other than’FFFFFFFF’X.

v From SM120BTR/1024 prior to WebSphereApplication Server Version 6.

MAX_GCOM_ACTIV_SES REAL Maximum number of communications sessions thathave been active during interval. Calculated as MAXof SM120NCA.

MAX_GCOM_EXIST_SES REAL Maximum number of communications sessions thatexist at the end of the interval. Calculated as MAX ofSM120NCS. No longer significant for WebSphereApplication Server Version 5.1, and later.

MAX_LCOM_ACTIV_SES REAL Maximum number of active local communicationsthat have been attached and active within the serverinstance during the interval. Calculated as MAX ofSM120NLA.

MAX_LCOM_EXIT_SES REAL Maximum number of local communication sessionsthat exist at the end of the interval. Calculated asMAX of SM120NLS. No longer significant forWebSphere Application Server Version 5.1, and later.

MAX_RCOM_ACTIV_SES REAL Maximum number of active remote communicationssessions that have been attached and active within theserver instance during the interval. Calculated asMAX of SM120NRA.

MAX_RCOM_EXIST_SES REAL Maximum number of remote communicationssessions that exist at the end of the interval.Calculated as MAX of SM120NRS. No longersignificant for WebSphere Application Server Version5.1, and later.


MIN_GCOM_ACTIV_SES REAL Minimum number of communications sessions thathave been active during interval. Calculated as MINof SM120NCA.

MIN_GCOM_EXIST_SES REAL Minimum number of communications sessions thatexist at the end of the interval. Calculated as MIN ofSM120NCS. No longer significant for WebSphereApplication Server Version 5.1, and later.



MIN_LCOM_ACTIV_SES REAL Minimum number of active local communicationssessions that have been attached and active within theserver instance during during the interval. Calculatedas MIN of SM120NLA.

MIN_LCOM_EXIST_SES REAL Minimum number of local communications sessionsthat exist at the end of the interval. Calculated asMIN of SM120NLS. No longer significant forWebSphere Application Server Version 5.1, and later.

MIN_RCROM_EXIST_SES REAL Minimum number of remote communications sessionsthat exist at the end of the interval. Calculated asMIN occurrence of SM120NRS. No longer significantfor WebSphere Application Server Version 5.1, andlater.

NUM_GCOM_EXIST_SES REAL Number of communications sessions that exist at theend of the interval. Calculated as LAST occurrenceSM120NCS. No longer significant for WebSphereApplication Server Version 5.1, and later.

NUM_GLOBAL_TRANS REAL Number of global transactions that have run throughthe server instance during the interval that have beeninitiated by the server instance during the interval.Calculated as SUM of SM120NG2 (prior to WebSphereApplication Server Version 5.1, this field was namedSM120NGT).

NUM_HTTP_SESSIONS FLOAT Number of HTTP communication sessions that havebeen attached and active within the server instanceduring the interval. From SM120NPA.

NUM_LCOM_EXIST_SES REAL Number of local communications sessions that exist atthe end of the interval. Calculated as LAST occurrenceSM120NLS. No longer significant for WebSphereApplication Server Version 5.1, and later.

NUM_LOCAL_TRANS REAL Number of local transactions that have been initiatedby the server instance during the interval. Calculatedas SUM of SM120NL2 (prior to WebSphereApplication Server Version 5.1, this field was namedSM120NLT).

NUM_RCOM_EXIST_SES REAL Number of remote communications sessions that existat the end of the interval. Calculated as LASToccurrence SM120NRS. No longer significant forWebSphere Application Server Version 5.1, and later.

SERVER_HTTPCLNT_KB REAL Number of Kbytes that have been transferred to theserver from all HTTP attached clients.

v Calculated as SUM of SM120ITH/1024 ifSM120BTH=’FFFFFFFF’X.

v From SM120BTH/1024 if SM120BTH other than’FFFFFFFF’X.

v From SM120BTH/1024 prior to WebSphereApplication Server Version 6.

SERVER_SIPCLNT_KB FLOAT Number of Kbytes that have been transferred to theserver from all SIP attached clients. From SM120ITP ifSM120BTP is FFFFFFFF(X), else SM120BTP.



SERVER_TYPE CHAR (4) WebSphere for z/OS server type. Possible value areMOFW (WebSphere V4 only) and J2EE. From SM120J2(prior to WebSphere Application Server Version 5.1,this field was named SM120STY).

SIPCLNT_SERVER_KB FLOAT Number of Kbytes that have been transferred fromthe server to all SIP attached clients. From SM120IFPif SM120BFP is FFFFFFFF(X), else SM120BFP.

TOT_CPUSEC_WLM_ENC REAL Total CPU time accumulated by the WLM enclaves.Calculated as SUM of SM120TEC.

WAS_INT_SERVER_HV,_DV,_MV

These views provide hourly, daily, and monthly statistics on activity that isrunning on a WebSphere Application Server for z/OS and is the aggregate of thework that runs on the server during the interval. If a server has multiple serverinstances, then a row for each server instance is present.

Note: As well as the calculated columns described here, these views also containall the data columns described in WAS_INT_SERVER_H,_D,_M tables.




CELL_NAME K CHAR(8) WebSphere for z/OS transaction server cell name.From SM120CEL.

NODE_NAME K CHAR(8) WebSphere for z/OS transaction server node name.From SM120NOD.

WEB_SER_NAME K CHAR(8) v Transaction server name (WebSphere for z/OSVersion 4)

v Cluster name (WebSphere for z/OS Version 5)

From SM120SNM.

WEB_SER_INSTA_NAME K CHAR(8) WebSphere for z/OS transaction server instance name.From SM120SIN1.

MVS_SYSTEM_ID K CHAR(4) System identifier (from the SMFPRMxx SIDparameter). From SM120SID.

SYSPLEX_NAME K CHAR(8) Sysplex Name. From SM120SNM.

SUBSYSTEM_ID K CHAR(4) Subsystem identifier from SUBSYS parameter. FromSM120SSI.


CPU_BUSY_PCT REAL Percentage of the enclave Workload Manager CPUtime on the total. Calculated asTOT_CPUSEC_WLM_ENC/MEASURED_SEC.

GLOBAL_TRAN_RATE REAL Number of global transactions that have run throughthe server instance per second. Calculated asNUM_GLOBAL_TRANS/MEASURED_SEC.



HTTP_ACTIVE_SESS REAL Number of HTTP communication sessions that havebeen attached and active within the server instanceduring the interval. Calculated as SUM ofSM120NHA.

HTTP_EXIST_SES REAL Number of HTTP communication sessions that existat the end of the interval. Calculated as LASToccurrence of SM120NHS

HTTPCLNT_SERVER_KB REAL Number of Kbytes that have been transferred fromthe server to all HTTP attached clients. Calculated asthe SUM of SM120BFH/1024.

KB_HTTP_RCVD_RATE REAL Number of total Kbytes received by the server fromall HTTP clients in a second. Calculated asHTTPCLNT_SERVER_KB /MEASURED_SEC.

KB_HTTP_SENT_RATE REAL Number of total Kbytes sent from the server to allHTTP clients in a second. Calculated asSERVER_HTTPCLNT_KB /MEASURED_SEC.

KB_RECEIVED_RATE REAL Number of total kbytes received by server from allclients in a second. Calculated as:KB_RCVD_GCLIENTS/MEASURED_SEC;

KB_SENT_RATE REAL Number of total kbytes sent from server to all clientsin a second. Calculated as: KB_SENT_GCLIENTS/MEASURED_SEC;

LCOM_EXIST_SES_PCT REAL Percentage of the local communications sessions onthe total. Calculated as 100*NUM_LCOM_EXIST_SES/ NUM_GCOM_EXIST_SES.

LOCAL_TRAN_RATE REAL Number of local transactions that have run throughthe server instance per second. Calculated asNUM_LOCAL_TRANS/MEASURED_SEC.

NUM_HTTP_SESSIONS FLOAT Number of HTTP communication sessions that havebeen attached and active within the server instanceduring the interval. From SM120NPA.

RCOM_EXIST_SES_PCT REAL Percentage of the remote communications sessions onthe total. Calculated as100*NUM_RCOM_EXIST_SES/NUM_GCOM_EXIST_SES.

SERVER_HTTPCLNT_KB REAL Number of Kbytes that have been transferred to theserver from all HTTP attached clients. Calculated asthe SUM of SM120BTH/1024.

SERVER_SIPCLNT_KB FLOAT Number of Kbytes that have been transferred to theserver from all SIP attached clients. From SM120ITP ifSM120BTP is FFFFFFFF(X), else SM120BTP.

SIPCLNT_SERVER_KB FLOAT Number of Kbytes that have been transferred fromthe server to all SIP attached clients. From SM120IFPif SM120BFP is FFFFFFFF(X), else SM120BFP.

TOT_CPUSEC_WLM_ENC REAL Total CPU time accumulated by the WLM enclaves.Calculated as SUM of SM120TEC.

2. Container Interval subcomponent tables:This section describes the tables of the Container Interval subcomponent availableonly in WebSphere Application Server for z/OS Version 4. The tables are empty inWebSphere Application Server later versions.


WAS_INT_METHOD_H

This table is available only in WebSphere Application Server for z/OS Version 4. Itprovides hourly statistics on all methods involved in MOFW Container activity.From SMF record SMF_120_4.







From SM120SNM.

WEB_SER_INSTA_NAME K CHAR(8) WebSphere for z/OS transaction server instance name.From SM120SIN.


SYSPLEX_NAME K CHAR(8) Sysplex name. From SM120HNM.


CONTAINER_NAME K VARCHAR(64) WebSphere for z/OS Container Name. FromSM120CNM.

CLASS_NAME K VARCHAR(64) Name of the class activated by container. FromSM120CLN.

METHOD_NAME K VARCHAR(64) Name of method. From SM120MNM.

AVG_RESPONSE_TIME REAL Maximum response time in seconds. Calculated as theAVG of SM120ART.

MAX_RESPONSE_TIME REAL Maximum response time in seconds. Calculated as theMAX occurrence of SM120MRT.


NUM_INVOCATIONS REAL Number of time the method was invoked duringinterval.Calculated as the SUM of SM120NMI.

NUM_NONFRMWRK_EXC REAL Number of non-framework exceptions that weredetected by container. Calculated as the SUM ofSM120NEX.

WAS_INT_CLASS_H,_D

These tables are available only in WebSphere Application Server for z/OS Version4. They provide hourly and daily statistics on all classes involved in MOFWContainer activity. From SMF record SMF_120_4.


WAS_INT_CLASS_H10 days


WAS_INT_CLASS_D45 days






From SM120SNM.



SYSPLEX_NAME K CHAR(8) Sysplex Name. From SM120HNM.




IST_CLASS_ACTIVATE INTEGER Number of instances of the class that were activated.Calculated as SUM of SM120NIA.

IST_CLASS_CREATED INTEGER Number of instances of this class that were created.Calculated as SUM of SM120NIC.

IST_CLASS_PASSIVAT INTEGER Number of instances of this class that werepassivated. Calculated as SUM of SM120NIP.

IST_CLASS_REMOVED INTEGER Number of instances of this class that were removed(deleted). Calculated as SUM of SM120NIR.


NUMBER_METHODS INTEGER Number of different methods invoked. Calculated asSUM of SM120MN.

WAS_INT_CONTAIN_H,_D,_M

These tables are available only in WebSphere Application Server for z/OS Version4. They provide hourly, daily, and weekly statistics of activities running inside acontainer located inside a WebSphere MOFW server. From SMF record SMF_120_4.


WAS_INT_CONTAIN_H10 days

WAS_INT_CONTAIN_D45 days

WAS_INT_CONTAIN_M365 days







From SM120SNM.







TRANSACTION_POLICY K CHAR(34) Container Transaction Policy. Possible value:TRANSACTION_REQUIREDSAME_SERVER_HYBRID_GLOBALHYBRID_GLOBALSUPPORTS_SAME_SERVER_HYBRID_GLOBAL

MEASURED_SEC REAL Interval in seconds. Calculated as the SUM ofdifferences between SM120SET and SM120SST.

NUM_CLASS_CREATED INTEGER Number of classes that were created. Calculated asSUM of SM120NIC.

NUM_CLASS_ACTIVAT INTEGER Number of classes that were activated. Calculated asSUM of SM120NIA.

NUM_CLASS_REMOVED INTEGER Number of classes that were removed (deleted).Calculated as SUM of SM120NIR.

NUM_CLASS_PASSIVAT INTEGER Number of classes that were passivated. Calculated asSUM of SM120NIP.

NUMBER_METHODS INTEGER Number of methods invoked. Calculated as SUM ofSM120MN.

3. J2EE & WEB Container Interval subcomponent tables:This section describes the tables of the J2EE & Web Container Intervalsubcomponent.

WAS_INT_SERVLETS_H

This table contains hourly information about each servlet associated with WebApplications during the interval. It is populated by SMF record SMF_120_8_X(built by Tivoli Decision Support for z/OS record procedure DRL2SI08).




DATE K DATE Date of the mid measurement. From SM120WID andSM120WIE.

TIME K TIME Time of the mid measurement. From SM120WID andSM120WIE.





From SM120WIB.

WEB_SER_INSTA_NAME K CHAR(8) WebSphere for z/OS transaction server instance name.From SM120WIC.


SYSPLEX_NAME K CHAR(8) Sysplex Name. From SM120WIA.


WEB_APPL_NAME K VARCHAR(70) The Web Application name. If you are monitoringservlets from multiple Web applications, this valuehelps you distinguish the servlets from one another.From SM120WIQ.

SERVLET_NAME K VARCHAR(70) Indicates the servlet instance being monitored. FromSM120WIW.

PERIOD K CHAR(8) Name of the period. This is derived using fieldsSM120WID and SMF120WIE from the record asparameters in the PERIOD function.

CPU_SEC_AVG REAL Average CPU time in seconds. Calculated as AVG ofSM120WJ4/1000000.

CPU_SEC_MAX REAL Maximum CPU time in seconds. Calculated as MAXof SM120WJ6/1000000.

CPU_SEC_MIN REAL Minimum CPU time in seconds. Calculated as MIN ofSM120WJ5/1000000.

DATE_LOADED_SINCE DATE Indicates the date at which the class file for the servletinstance was most recently loaded. The value is 0 ifthe servlet class is not currently loaded. Calculated asLAST occurrence of Load Date.

MEASURED_SEC REAL Polling interval in seconds. Calculated as the SUM ofdifferences between SM120WID and SM120WIE.

NUMBER_ERRORS REAL Indicates the number of errors associated with thisservlet instance as measured during the interval.Calculated as LAST of SM120WJ2.

REQUEST_RATE REAL Indicates the average number of requests per secondfor the servlet instance, as measured during theinterval. Calculated as AVG SM120WIX.



RESPONSE_TIME_AVG REAL Indicates the average time (in seconds) the servletinstance spent performing services such as service(),do Get(), or do Post(), as measured during theinterval. Calculated as AVG of SM120WIY.

RESPONSE_TIME_MAX REAL Indicates the maximum time (in seconds) the servletinstance spent performing services such as service(),do Get(), or do Post() as measured during theinterval. Calculated as MAX of SM120WJ1.

RESPONSE_TIME_MIN REAL Indicates the minimum time (in seconds) the servletinstance spent performing services such as service(),do Get(), or do Post() as measured during theinterval. Calculated as MIN of SM120WIZ.

SERVLET_UP_TIME REAL Indicates the number of consecutive seconds that theservlet was up. Calculated as LAST occurrence of theINTERVAL function applied to Load Date & LoadTime and SM120WIE.

TIME_LOADED_SINCE TIME Indicates the time at which the class file for theservlet instance was most recently loaded. The valueis 0 if the servlet class is not currently loaded.Calculated as LAST occurrence of Load Time.

TOTAL_REQUESTS REAL Indicates the number of requests this instance of theservlet handled during the interval. Calculated asSUM of SM120WIX.

WAS_INT_WEBAPPL_H,_D

These tables contain hourly and daily information about all Web Applicationsduring the interval. They are populated by the WAS_INT_SERVLET_H table.


WAS_INT_WEBAPPL_H10 days

WAS_INT_WEBAPPL_D45 days




CELL_NAME K CHAR(8) WebSphere for z/OS transaction server cell name.From SM120CL5 (prior to WebSphere Version 5.1, thisfield was named SM120CEL).




From SM120WIB.







WEB_APPL_NAME K VARCHAR(70) The Web Application name. If you are monitoringservlets from multiple Web applications, this valuehelps you distinguish the servlets from one another.From SM120WIQ.

PERIOD K CHAR(8) Name of the period. This is derived using fieldsSM120WID and SMF120WIE from the record asparameters in the PERIOD function.

CPU_SEC_AVG REAL Average CPU time used by a Web Application servlet(in seconds). Calculated as AVG ofSM120WJ4/1000000.

CPU_SEC_MAX REAL Maximum CPU time used by a Web Applicationservlet (in seconds). Calculated as MAX ofSM120WJ6/1000000.

CPU_SEC_MIN REAL Minimum CPU time used by a Web Applicationservlet (in seconds). Calculated as MIN ofSM120WJ5/1000000.


NUMBER_ERRORS REAL Indicates the total number of errors associated withthis Web Application, as measured during theinterval. Calculated as LAST of SM120WJ2.

NUM_LOADED_SERVLET INTEGER Number of Servlets that were loaded. Calculated asCount of Servlet sections.

RESPONSE_TIME_AVG REAL Indicates the average time (in seconds) that a WebApplication servlet spent performing services such asservice(), do Get(), or do Post() as measured duringthe interval. Calculated as AVG of SM120WIY.

RESPONSE_TIME_MAX REAL Indicates the maximum time (in seconds) that a WebApplication servlet spent performing services such asservice(), do Get(), or do Post as measured during theinterval. Calculated as MAX of SM120WJ1.

RESPONSE_TIME_MIN REAL Indicates the minimum time (in seconds) that a Webapplication servlet spent performing services such asservice(), do Get(), or do Post ()as measured duringthe interval. Calculated as MIN of SM120WIZ.

TOTAL_REQUESTS REAL Indicates the total number of requests all servletshandled during the interval. Calculated as SUM ofSM120WIX.

WAS_INT_HTTPSESS_H,_D,_M

These tables contain hourly, daily, and monthly information about all HTTPsessions during the interval. They are populated by SMF record SMF_120_8.



WAS_INT_HTTPSESS_H10 days

WAS_INT_HTTPSESS_D45 days

WAS_INT_HTTPSESS_M547 days




CELL_NAME K CHAR(8) WebSphere for z/OS transaction server cell name.From SM120CCL5 (prior to WebSphere ApplicationServer Version 5.1, this field was named SM120CEL).

NODE_NAME K CHAR(8) WebSphere for z/OS transaction server node name.From SM120NND5 (prior to WebSphere ApplicationServer Version 5.1, this field was named SM120NOD).



From SM120WIB.





PERIOD K CHAR(8) Name of the period. This is derived using fieldsSM120WID and SM120WIE from the record asparameters in the PERIOD function

ACTIVE_SESSIONS INTEGER Current number of http sessions that are activelyreferenced in the server at the end of the interval.Calculated as LAST occurrence of SM120WIH.

CREATED_SESSIONS REAL Indicates the number of sessions created during theinterval. This includes sessions that were available,active, or invalidated. Calculated as SUM ofSM120WIF.

CREATED_SESS_RATE REAL Indicates the average number of sessions created persecond during the interval. Calculated as AVG ofSM120WIF.

FINALIZED_SESSIONS INTEGER Number of sessions that were finalized. Calculated asLAST occurrence of SM120WIM.

INVALID_SESS_RATE REAL Indicates the average number of sessions invalidated(removed from available or active state) per secondduring the interval. This value is valid only in termsof in-memory sessions, not persistent sessions.Calculated as the AVG of SM120WIG.



INVALID_SESSIONS REAL Indicates the number of sessions invalidated (removedfrom available or active state) during the interval.This value is valid only in terms of in-memorysessions, not persistent sessions. Calculated as SUM ofSM120WIG.

INVAL_TIME_SESSION REAL Average time in seconds that was required to processthe invalidation http sessions as measured during theinterval. Calculated as AVG of SMF120WIL/1000.

LIVE_SESSIONS REAL Total number of http sessions being tracked by theserver at the end of the interval. This includes bothactive and inactive sessions. Calculated as LASToccurrence of SM120WIN.

LIFE_TIME_SESSION INTEGER Indicates the average time in seconds of invalidatedHTTP sessions have remained alive in memory. asmeasured during the interval. The value is valid onlyin terms of in-memory sessions, not persistentsessions. Currently valid sessions are not included inthe calculation because their life spans are not yetknown. Calculated as AVG of SM120WIK/1000.

MAX_ACT_SESSIONS INTEGER Maximum number of HTTP sessions that are activelyreferenced in the server during the interval.Calculated as MAX of SM120WIJ.

MAX_LIVE_SESSIONS REAL Maximum number of live HTTP sessions during theinterval. Calculated as MAX of SM120WIP


MIN_ACT_SESSIONS INTEGER Minimum number of HTTP sessions that are activelyreferenced in the server during the interval.Calculated as MIN of SM120WII.

MIN_LIVE_SESSIONS REAL Minimum number of live HTTP sessions during theinterval. Calculated as MIN of SM120WIO

WAS_INT_BEANMTHD_H

This table contains hourly information about each BEAN METHOD associatedwith J2EE container during the interval. It is populated by SMF recordSMF_120_6_X (built by Tivoli Decision Support for z/OS record procedureDRL2SI06).



DATE K DATE Date of the mid measurement. From SM120JI8 andSM120JI9.

TIME K TIME Time of the mid measurement. From SM120JI8 andSM120JI9.







From SM120JI5.

WEB_SER_INSTA_NAME K CHAR(8) WebSphere for z/OS transaction server instance name.From SM120JI6.


SYSPLEX_NAME K CHAR(8) Sysplex Name. From SM120JI4.


WEB_J2EE_CONTAINER K VARCHAR(8) The WebSphere for z/OS container name. This ishardcoded to "Default" for the 4.0.1 time frame.FromSM120JI7.

BEAN_AMC_NAME K VARCHAR(66) AMCName of the bean activated by the container.Truncated to the first right most 66 bytes. FromSM120JB1.

METHOD_NAME K VARCHAR(66) The name of the method including its signature in itsexternalized, human readable form. If the length ofthe method exceeds 66 bytes in EBCDIC format, theleft most 66 characters are recorded. From SM120Jm1.

PERIOD K CHAR(8) Name of the period. This is derived using fieldsSM120JI8 and SM120JI9 from the record as parametersin the PERIOD function.

ACT_EXEC_TIME REAL Indicates the average number of seconds theenterprise bean's container activated (retrieved fromsecondary storage) the enterprise bean as measuredduring the interval Calculated AVG of SM120JML.

ACT_EXEC_TIME_MAX REAL Indicates the maximum number of seconds theenterprise bean's container activated (retrieved fromsecondary storage) the enterprise bean. Calculated asMAX occurrence of SM120JMM.

ACT_INVOCATIONS REAL EJBActivation number of invocations. Indicates thenumber of times the enterprise bean's containeractivated (retrieved from secondary storage) theenterprise bean, as measured during the interval.Note, because stateless session beans are neveractivated, this data point is not applicable to them.Calculated as SUM of SM120JMK.

BEAN_TYPE CHAR(20) The type of bean. From SM120JB3. Possible values are'CMP entity', 'BMP entity', ' Stateless session', 'Stateful session', and 'Message Driven'.

CPU_SEC_AVG REAL Average CPU time in seconds. Calculated as AVG ofSM120JMQ/1000000

CPU_SEC_MAX REAL Maximum CPU time in seconds. Calculated as MAXof SM120JMS/1000000.

CPU_SEC_MIN REAL Minimum CPU time in seconds. Calculated as MIN ofSM120JMQ/1000000.



LOAD_EXEC_TIME REAL Indicates the average number of seconds theenterprise bean has required to load information fromthe database into themselves as measured during theinterval Calculated as AVG of SM120JMF.

LOAD_EXEC_TIME_MAX REAL Indicates the maximum number of seconds theenterprise bean has required to load information fromthe database into themselves as measured during theinterval. Calculated as MAX occurrence ofSM120JMG.

MEASURED_SEC REAL Polling interval in seconds. Calculated as the SUM ofdifferences between SM120JI9 and SM120JI8.

METHOD_INVOCATION REAL The number of times the method was invoked duringthe interval. Calculated as SUM of SM120JM2.

PASS_EXEC_TIME REAL Indicates the average number of seconds theenterprise bean's container passivated (transferred tosecondary storage) the bean as measured during theinterval. Calculated as AVG of SM120JMO.

PASS_EXEC_TIME_MAX REAL Indicates the maximum number of seconds theenterprise bean's container passivated (transferred tosecondary storage) the as measured during theinterval. Calculated as MAX occurrence of SM120JMP.

PASS_INVOCATIONS REAL EJBPassivation number of passivations. Indicates thenumber of times the enterprise bean's containerpassivated (transferred to secondary storage) the bean,as measured during the interval. Note, becausestateless session beans are never passivated, they arenot included in the total. Calculated as SUM ofSM120JMN.

REENTRANCE_POLICY CHAR(3) The reentrance policy for the bean. Possible valuesare:

NO Not reentrant within transactions

YES Reentrant within transactionFrom SM120JB7.

RESPONSE_TIME_AVG REAL Average response time in seconds. Calculated as AVGof SM120JM3.

RESPONSE_TIME_MAX REAL Maximum response time in seconds. Calculated asMAX of SM120JM4.

STORE_EXEC_TME REAL Indicates the average number of seconds the entitybean persisted its state in the database as measuredduring the interval Calculated as AVG of SM120JMI.

STORE_EXEC_TME_MAX REAL Indicates the maximum number of seconds the entitybean persisted its state in the database as measuredduring the interval Calculated as MAX occurrence ofSM120JMJ.

STORE_INVOCATIONS REAL EJBStore number of invocations. Indicates the numberof times an entity bean persisted its state in thedatabase during the interval. Calculated as SUM ofS120JMH.



TRANSACTION_POLICY CHAR(16) The transaction policy for the bean method. Valuesfrom com.ibm.WebSphere for z/OS.csi.TransactionAttribute.java possible value:TX_NOT_SUPPORTEDTX_BEAN_MANAGEDTX_REQUIREDTX_SUPPORTSTX_REQUIRES_NEWTX_MANDATORYTX_NEVER

WAS_INT_J2EECNT_H,_D,_W

These tables contain hourly, daily, and weekly information about the J2EEcontainer during the interval. It is populated by SMF record SMF_120_6_X (builtby Tivoli Decision Support for z/OS record procedure DRL2SI06).


WAS_INT_J2EECNT_H10 days

WAS_INT_J2EECNT_D45 days

WAS_INT_J2EECNT_W365 days


DATE K DATE Date of the mid measurement. From SM120JI8 andSM120JI9.

TIME K TIME Time of the mid measurement. From SM120JI8 andSM120JI9.





From SM120JI5.

WEB_SER_INSTA_NAME K CHAR(8) WebSphere for z/OS transaction server instance name.From SM120JI6.


SYSPLEX_NAME K CHAR(8) Sysplex Name. From SM120JI4.




WEB_J2EE_CONTAINER K VARCHAR(8) The WebSphere for z/OS container name. This ishardcoded to "Default" for the 4.0.1 timeframe.FromSM120JI7.

PERIOD K CHAR(8) Name of the period. This is derived using fieldsSM120JI8 and SM120JI9 from the record as parametersin the PERIOD function.

ENTITY_ACTIV REAL Indicates the number of times the enterprise beancontainers activated (retrieved from secondarystorage) the enterprise beans during the interval.Calculated as SUM of SM120JMK, where SM120JB3=0,1, 4, or 5.

ENTITY_CREATE REAL Indicates the number of entity bean objects that werecreated by the server during the interval. Calculatedas SUM of SM120JM2 for SM120JM1='create()' or'create:', where SM120JB3=0, 1, 4, or 5.

ENTITY_LOAD REAL Indicates the number of times entity beans loadedinformation from the database into themselves duringthe interval. Calculated as SUM of SM120JME.

ENTITY_PASSIVATE REAL Indicates the number of times the enterprise beancontainers passivated (transferred to secondarystorage) the enterprise beans during the interval.Calculated as SUM of SM120JMN, where SM120JB3=0,1, 4, or 5.

ENTITY_REMOVE REAL Indicates the number of times entity bean instanceswere removed during interval. The enterprise beaninstance might have been removed by the remove()method. Calculated as SUM of SM120JM2 forSM120JM1='remove()' or 'remove:', whereSM120JB3=0, 1, 4, or 5.

ENTITY_STORE REAL Indicates the number of times entity beans storedinformation in the database during the interval.Calculated as SUM of SM120JMH.

MEASURED_SEC REAL Polling interval in seconds. Calculated as the SUM ofdifferences between SM120JI9 and SM120JI8.

MESSAGE_DRIVEN REAL Indicates the total number of times an onMessagemethod was invoked against the listed session beans,as measured during the activity. Calculated as SUM ofSM120JM2 for SM120JM1='onMessage()' or'onMessage:', where SM120JB3=6.

METHOD_INVOCATION REAL Total number of times the methods were invokedduring the interval. Calculated as SUM of SM120JM2.

RESPONSE_TIME_AVG REAL Average response time in seconds. Calculated as AVGof SM120JM3.

RESPONSE_TIME_MAX REAL Maximum response time in seconds. Calculated asMAX of SM120JM4.

STATEFUL_ACTIV REAL Indicates the number of times the stateful sessionbean containers activated (retrieved from secondarystorage) the enterprise beans during the interval.Calculated as SUM of SM120JMK, where SM120JB3=3.



STATEFUL_CREATE REAL Indicates the total number of times the create()method was invoked against the listed state fullsession beans, as measured during the interval.Calculated as SUM of SM120JM2 forSM120JM1='create()' or 'create:', where SM120jb3=3.

STATEFUL_REMOVE Indicates the total number of times the remove()method was invoked against the listed stateful sessionbeans, as measured during the interval. Calculated asSUM of SM120JM2 for SM120JM1='remove()' or'remove:', where SM120jb3=3.

STATEFUL_PASSIVATE REAL Indicates the number of times the stateful sessionbean containers passivated (transferred to secondarystorage) the enterprise beans during the interval.Calculated as SUM of SM120JMN, where SM120JB3=3.

STATELESS_CREATE REAL Indicates the total number of times the create()method was invoked against the listed statelesssession beans, as measured during the interval.Calculated as SUM of SM120JM2 forSM120JM1='create()' or 'create:', where SM120JB3=2.

WebSphere Application Server Activity component tables andviewsThis section describes the tables and views of the WebSphere Application ServerActivity subcomponents.

Independently of which WebSphere Application Server Activity subcomponent isinstalled, the following WAS_CONNECT_ACTID table is installed to guarantee thecompleteness of information with WebSphere Application Server for z/OS data.

Table 27. Data tables and views in the WebSphere Application Server Activity subcomponents

WebSphere Application Server Activity subcomponents Data tables

None WAS_CONNECT_ACTID

1. Server Activity WAS_ACT_SERVERWAS_ACT_SERV_HEAPWAS_ACT_USR_HWAS_ACT_USR_D,_MWAS_ACT_USR_DV

2. Container Interval WAS_ACT_METHODWAS_ACT_CLASSWAS_ACT_CONTAINWAS_ACT_METHOD_VWAS_ACT_CLASS_VWAS_ACT_CONTAIN_V

3. J2EE & WEB Container Activity WAS_ACT_SERVLETSWAS_ACT_WEBAPPLWAS_ACT_HTTPSESSWAS_ACT_BEANMTHDWAS_ACT_J2EECNTWAS_ACT_BEANMTHD_VWAS_ACT_J2EECNT_V


Table 27. Data tables and views in the WebSphere Application Server Activity subcomponents (continued)

WebSphere Application Server Activity subcomponents Data tables

4. Request Activity WASACT_REQAPPL_DWASACT_REQAPPL_HWASACT_REQAPPL_MWASACT_REQCONT_DWASACT_REQCONT_HWASACT_REQCONT_MWASACT_REQAPPL_DVWASACT_REQAPPL_HVWASACT_REQAPPL_MVWASACT_REQCONT_DVWASACT_REQCONT_HVWASACT_REQCONT_MVWASACT_OUTCONT_DWASACT_OUTCONT_HWASACT_OUTCONT_MWASACT_OUTSERV_DWASACT_OUTSERV_HWASACT_OUTSERV_MWASACT_OUTCONT_DVWASACT_OUTCONT_HVWASACT_OUTCONT_MVWASACT_OUTSERV_DVWASACT_OUTSERV_HVWASACT_OUTSERV_MV

WAS_CONNECT_ACTID:This table provides the stop activity time to all the other tables populated byWebSphere Application Server activity records not containing this value. FromSMF_120_1 record.



ACTIVITY_START_TME K TIMESTAMP Activity start time. From SM120AID.

STOKEN K CHAR(16) It is set to ASSBSTKN which is the address token ofthe address space which created the new activity.From SM120AID.

IP_HOST_ADDRESS K CHAR(16) IP Server address. From SM120AID.



ACTIVITY_STOP_TIME TIMESTAMP Activity end time. From SM120AET.

1. Server Activity subcomponent tables and views:This section describes the tables and views for the WebSphere Application ServerActivity subcomponent.

WAS_ACT_SERVER

This table provides data on the activity that is running on a WebSphereApplication Server for z/OS. It could be used to perform basic charge-back


accounting. A single entry is created for each activity that is run on a server orserver instance. Populated from SMF record SMF_120_1.

The default retention period for this table is 3days.


ACTIVITY_START_TME K TIMESTAMP Activity start time. From SM120AST.


IP_HOST_ADDRESS K CHAR(16) IP client address or job name. From SM120CSA.



COM_SESSION_ADDR1 K CHAR(8) Client IP address or Job name. From SM120CSA.

COM_SESSION_ADDR2 K CHAR(4) Port Number or job asid. From SM120CSA.

COM_SESSION_HANDLE K CHAR(16) Communication session handle. From SM120CSH.

ACTIVITY_STOP_TIME TIMESTAMP Activity end time. From SM120AET.

ASID1 INTEGER First server region address space ID involved toprocess this activity. From SM120SR1.

ASID2 INTEGER Second server region address space ID involved toprocess this activity. From SM120SR2.

ASID3 INTEGER Third server region address space ID involved toprocess this activity. From SM120SR3.

ASID4 INTEGER Fourth server region address space ID involved toprocess this activity. From SM120SR4.

ASID5 INTEGER Fifth server region address space ID involved toprocess this activity. From SM120SR5.

BYTES_RECEIVED FLOAT Number of bytes received by the server.

v From SM120CDR if SM120SDR=’FFFFFFFF’X.

v From SM120SDR if SM120SDR other than’FFFFFFFF’X.

v From SM120SDR prior to WebSphere ApplicationServer Version 6.

BYTES_TRANSMITTED FLOAT Number of bytes transmitted by server back to theclient.

v From SM120CDT if SM120SDT=’FFFFFFFF’X.

v From SM120SDT if SM120SDT other than’FFFFFFFF’X.

v From SM120SDT prior to WebSphere ApplicationServer Version 6.

CELL_NAME CHAR(8) WebSphere for z/OS transaction server cell name.From SM120CEL.

COM_SESSION_TYPE CHAR(3) Communication session optimization. FromSM120CSO

GLOBAL_TRANSACTION INTEGER Number of global transactions that were started in theserver region. From SM120NGT.

LOCAL_TRANSACTION INTEGER Number of local transactions that were started in theserver region. From SM120NLT.



NODE_NAME CHAR(8) WebSphere for z/OS transaction server node name.From SM120NOD.

NUM_SERVER_REGIONS INTEGER Total number of server regions that were involved toprocess this activity. If applicable, up to the first fiveserver region address. From SM120SNR (prior toWebSphere Application Server Version 5.1, this fieldwas named SM120SNR).

NUMBER_METHODS INTEGER Number of input methods. From SM120NIM.

SERVER_TYPE CHAR(4) WebSphere for z/OS server type. Possible values areMOFW (WAS V4 only) and J2EE. From SM120J2E(prior to WebSphere Application Server Version 5.1,this field was named SM120STY).

SUBSYSTEM_ID CHAR(4) Subsystem identifier from SUBSYS parameter. FromSM120SSI.

TOT_CPUSEC_WLM_ENC REAL Total CPU time accumulated by the WLM enclaves.Calculated from SM120WCP.

WEB_SER_INSTA_NAME CHAR(8) Transaction server instance name. From SM120INA(prior to WebSphere Application Server Version 5.1,this field was named SM120SIN).

WEB_SER_NAME CHAR(8) Transaction server name. From SM120SNA (prior toWebSphere Application Server Version 5.1, this fieldwas named SM120SNM).

WLM_ENCLAVE_TOKEN CHAR(16) The WLM enclave token. From SM120WLM.

WAS_ACT_SERV_HEAP

This table provides JVM heap data for the activities running on WebSphereApplication Server for z/OS. For each activity, entries are created specifying theserver region address space ID and the heap type. From record SMF_120_1.





IP_HOST_ADDRESS K CHAR(16) IP Server address. From last 4 bytes of SM120AID.

MVS_SYSTEM_ID K CHAR(4)) System identifier (from the SMFPRMxx SIDparameter). From SM120SID.


ASID K INTEGER Server region address space ID involved. FromSM120JHA (prior to WebSphere Application ServerVersion 5.1, this field was named SM120JSR).

JNI_GCQRY_HEAP_TYP K CHAR(10) Heap type as defined in the QueryGCStatus() JNIfunction. Possible values are TRANSIENT,MIDDLEWARE, NURSERY, MATURE, andSHARED_MEM. From SM120JHH (prior toWebSphere Application Server Version 5.1, this fieldwas named SM120JHT).



ACTIVITY_STOP_TIME TIMESTAMP Activity stop time. From SM120AET.

FREE_STORAGE REAL Free Storage. From SM120JHF (prior to WebSphereApplication Server Version 5.1, this field was namedSM120JFS).

GARBAGE_COLL_COUNT INTEGER Garbage Collection Count. From SM120JHC (prior toWebSphere Application Server Version 5.1, this fieldwas named SM120JGC).

TOTAL_STORAGE REAL Total Storage. From SM120JHT (prior to WebSphereApplication Server Version 5.1, this field was namedSM120JTS).

WAS_ACT_USR_H

This table provides hourly accounting data for the activities running on WebSphereApplication Server for z/OS. For each user credentials, a record is createdspecifying the bytes sent and received and the CPU usage for the activities, startedin one hour. From record SMF_120_1

The default retention periods for this table is 10 days.


DATE K DATE Activity start date. From SM120AST.

TIME K TIME Activity start time. From SM120AST.


COMM_SESSION_ADDR1 K CHAR(16) It could be an IP client address or job name. FromSM120CSA.

USER_CREDENTIALS K CHAR(8) The user credentials under which the activity began.







BYTES_TRANSMITTED FLOAT Number of bytes transmitted by the server back to theclient.




PERIOD CHAR(8) Name of the period. This is derived using fieldsSM120WID and SM120WIE from the record, asparameters in the PERIOD function.

TOT_CPUSEC REAL Total CPU time, in seconds, accumulated.




WAS_ACT_USR_D,_M

These tables provide daily and monthly accounting data for the activities runningon WebSphere Application Server for z/OS. For each user credentials, a record iscreated specifying the bytes sent and received and the CPU usage in one day (ormonth).


WAS_ACT_USR_D45 days

WAS_ACT_USR_M547 days


DATE K DATE Activity start date. From SM120AST

PERIOD K CHAR(8) Name of the period. This is derived using fieldsSM120WID and SM120WIE from the record, asparameters in the PERIOD function.

IP_HOST_ADDRESS K CHAR(16) IP Server address. From last 4 bytes of SM120AID

COMM_SESSION_ADDR1 K CHAR(16) It could be an IP client address or job name. FromSM120CSA


MVS_SYSTEM_ID K CHAR(4) System identifier (from the SMFPRMxx SIDparameter). From SM120SID

SYSPLEX_NAME K CHAR(8) Sysplex Name. From SM120HNM

BYTES_RECEIVED FLOAT Number of bytes received by server.




BYTES_TRANSMITTED FLOAT Number of bytes transmitted by server back to theclient.







WAS_ ACT_USR_DV

This view provides accounting data for the activities running on WebSphereApplication Server for z/OS. For each user credentials, a record is createdspecifying the bytes sent and received and the CPU usage in one day (or month).


DATE K DATE Activity start date. From SM120AST


COMM_SESSION_ADDR1 K CHAR(16) It could be an IP client address or job name. FromSM120CSA


MVS_SYSTEM_ID K CHAR(4) System identifier (from the SMFPRMxx SIDparameter). From SM120SID

SYSPLEX_NAME K CHAR(8) Sysplex name. From SM120HNM





BYTES_TRANSMITTED FLOAT Number of bytes transmitted by the server back to theclient.






2. Container Activity subcomponent tables and views:This section describes the tables and views for the WebSphere Application ServerContainer Activity subcomponent available only in WebSphere Application Serverfor z/OS Version 4. The tables and views are empty in WebSphere ApplicationServer later versions.

WAS_ACT_METHOD

This table is available only in WebSphere Application Server for z/OS Version 4. Itprovides data for each method involved in the activity. From SMF recordSMF_120_2.










CONTAINER_NAME K VARCHAR(64) WebSphere for z/OS Container Name. FromSM120CNM

CLASS_NAME K VARCHAR(64) Name of the class activated by container. FromSM120CLN

ASID K INTEGER Server region address space ID involved to processthis activity. From SM120ASR.


AVG_RESPONSE_TIME REAL Average response time in seconds. Calculated as theLAST of SM120MRT.


NUM_INVOCATIONS REAL Number of time the method was invoked duringinterval. Calculated as LAST occurrence of theactivity.

NUM_NONFRMWRK_EXC REAL Number of non-framework exceptions that weredetected by container. Calculated as LAST occurrenceof SM120ART.


WEB_SER_INSTA_NAME CHAR(8) WebSphere for z/OS transaction server instance name.From SM120SIN

WEB_SER_NAME CHAR(8) v Transaction server name (WebSphere for z/OSVersion 4)


From SM120SNM.


WAS_ACT_CLASS

This table is available only in WebSphere Application Server for z/OS Version 4. Itprovides data from SMF record SMF_120_4.













IST_CLASS_ACTIVATY INTEGER Number of instances of the class that were activated.Calculated as SUM of SM120NIA






WEB_SER_INSTA_NAME CHAR(8) WebSphere for z/OS transaction server instance name.From SM120SIN.



From SM120SNM.


WAS_ACT_CONTAIN

This table is available only in WebSphere Application Server for z/OS Version 4. Itprovides data from SMF record SMF_120_2.




ASID K INTEGER Server region address space ID involved to processthis activity. From SM120ASR














TRANSACTION_POLICY CHAR(34) Container Transaction Policy. Possible value:TRANSACTION_REQUIREDSAME_SERVER_HYBRID_GLOBALHYBRID_GLOBALSUPPORTS_SAME_SERVER_HYBRID_GLOBAL




From SM120SNM.


WAS_ACT_METHOD_V

This view is available only in WebSphere Application Server for z/OS Version 4. Itprovides statistics on all methods involved in an activity. It is based on theWAS_ACT_METHOD table, and its data comes from SMF record SMF_120_2.

Note:

As well as the calculated columns described here, this view also contains all thedata columns described for the source table.










CLASS_NAME K VARCHAR(64) Name of the class activated by container. FromSM120CLN



ACTIVITY_STOP_TIME TIMESTAMP Activity stop time. From TABLEWAS_CONNECT_ACTID

AVG_RESPONSE_TIME REAL Average response time in seconds. Calculated as theLAST of SM120MRT.


NUM_INVOCATIONS REAL Number of time the method was invoked duringinterval. Calculated as LAST occurrence of theactivity.

NUM_NONFRMWRK_EXC REAL Number of non-framework exceptions that weredetected by container. Calculated as LAST occurrenceof SM120ART.





From SM120SNM.


WAS_ACT_CLASS_V

This view is available only in WebSphere Application Server for z/OS Version 4. Itprovides statistics on all classes involved in an activity. It is based on theWAS_ACT_CLASS table, and its data comes from SMF record SMF_120_2.

Note:

As well as the calculated columns described here, this view also contains all thedata columns described for the source table.


ACTIVITY_START_TME K TIMESTAMP Activity start time. From SM120ASR.


IP_HOST_ADDRESS K CHAR(16) IP Server address. From last 4 bytes SM120AID








IST_CLASS_ACTIVAT INTEGER Number of instances of the class that were activated.Calculated as SUM of SM120NIA.




ACTIVITY_STOP_TIME TIMESTAMP Activity stop time. From WAS_CONNECT_ACTIDtable.






From SM120SNM.


WAS_ACT_CONTAIN_V

This view is available only in WebSphere Application Server for z/OS Version 4. Itprovides data from SMF record SMF_120_2.


ASID K INTEGER Server region address space ID involved to processthis activity. From SM120ASR









ACTIVITY_STOP_TIME TIMESTAMP Activity stop time. From TABLEWAS_CONNECT_ACTID.






TRANSACTION_POLICY CHAR(34) Container Transaction Policy.


WEB_SER_NAME CHAR(8) From SM120SNM.


3. J2EE & WEB Container Activity subcomponent tables and views:This section describes the tables and views for the WebSphere J2EE &WebContainer Activity subcomponent.

WAS_ACT_SERVLETS

This table contains information about servlets involved in the activity. It ispopulated by SMF record SMF_120_7_X (built by Tivoli Decision Support for z/OSrecord procedure DRL2SI07).



ACTIVITY_START_TME K TIMESTAMP Activity start time. From SM120WAF.

STOKEN K CHAR(16) It is set to ASSBSTKN which is the address token ofthe address space which created the new activity.From SM120WAE

IP_HOST_ADDRESS K CHAR(16) IP Server address. From last 4 bytes of SM120WAE.


SYSPLEX_NAME K CHAR(8) Sysplex Name. From SM120WAA.

WEB_APPL_NAME K VARCHAR(70) The Web Application name. If you are monitoringservlets from multiple Web applications, this valuehelps you distinguish the servlets from one another.From SM120WAL.

SERVLET_NAME K VARCHAR(70) SERVLET_NAME

ACTIVITY_STOP_TIME TIMESTAMP Activity stop time. From SM120WAG.

ACTIVITY_TIME REAL Activity time duration in seconds. Calculated as thedifferences between SM120WAF and SM120WAG.



CELL_NAME CHAR(8) WebSphere for z/OS transaction server cell name.From SM120CL4 (prior to WebSphere ApplicationServer Version 5.1, this field was named SM120CEL).

DATE_LOADED_SINCE DATE Indicates the date at which the class file for the servletinstance was most recently loaded. The value is 0 ifthe servlet class is not currently loaded. Calculated asLAST occurrence of Load Date.

NODE_NAME CHAR(8) WebSphere for z/OS transaction server node name.From SM120ND4 (prior to WebSphere ApplicationServer Version 5.1, this field was named SM120NOD).

NUMBER_ERRORS REAL Indicates the number of errors that were encounteredduring the servlet execution. From SM120WAS.

RESPONSE_TIME REAL Indicates the response time (in seconds) the servletinstance spent performing services such as service(),do Get(), or do Post(), as measured during theactivity. From SM120WAR.

STATUS_FOR_REQUEST CHAR(8) Possible values: 'LOADED' 'UNLOADED' FromSM120WAT.


TIME_LOADED_SINCE TIME Indicates the time at which the class file for theservlet instance was most recently loaded. The valueis 0 if the servlet class is not currently loaded.Calculated as LAST occurrence of Load Time.

TOT_CPUSEC_SERVLET REAL Total CPU time accumulated by the servlet.Calculated from SM120CPU.

WEB_SER_INSTA_NAME CHAR(8) WEB_SER_INSTA_NAME



From SM120WAB.

WLM_ENCLAVE_TOKEN CHAR(16) The WLM enclave token. From SM120WAD.

WAS_ACT_WEBAPPL

This table contains information about all Web Applications involved in the activity.It is populated by the WAS_ACT_SERVLETS table.










WEB_APPL_NAME K VARCHAR(70) The Web Application name. If you are monitoringservlets from multiple Web applications, this valuehelps you distinguish the servlets from one another.From SM120WAL.





NUM_SERVLET_LOADED REAL Indicates the total number of servlets loaded duringthe execution of this activity. Calculated as the sum ofall occurrences having SM120WAT='1'.


TOTAL_ERRORS REAL Indicates the total number of errors that wereencountered during the servlets execution during thisactivity. Calculated as the SUM of SM120WAS.

TOTAL_RESPONSE_TME REAL Indicates the total response time (in seconds) theservlets instance spent performing services such asservice(), do Get(), or do Post(), as measured duringthe activity. Calculated as SUM SM120WAR.

TOT_CPUSEC_WEBAPPL REAL Total CPU time accumulated by the Web application.Calculated as SUM of TOT_CPUSEC_SERVLET.


WEB_SER_INSTA_NAME CHAR(8) WebSphere for z/OS transaction server instance name.From SM120WAC.



From SM120WAB.

WAS_ACT_HTTPSESS

This table contains information about all HTTP sessions involved in the activity. Itis populated by SMF record SMF_120_7.










ACTIVE_SESSIONS REAL Number of http sessions that are actively referencedduring this activity. From SM120WAJ.




CREATED_SESSIONS REAL Indicates the number of http sessions created duringthe activity. This includes sessions that were available,active, or invalidated. From SM120WAH.

INVAL_TIME_SESSION REAL Indicates the average life time in seconds that wasrequired to process the invalidation http sessions asmeasured during the activity. From SM120WAK/1000when SM120WAI>0.

INVALIDAT_SESSIONS REAL Indicates the number of sessions invalidated (removedfrom available or active state) during the activity. Thisvalue is valid only in terms of in-memory sessions,not persistent sessions. From SM120WAI.

LIFE_TIME_SESSION REAL Indicates the http session life time in seconds duringthe activity. From SM120WAK/1000 whenSM120WAI=0



WEB_SER_INSTA_NAME CHAR(8) WebSphere for z/OS transaction server instance name.From SM120WAC.



From SM120WAB.


WAS_ACT_BEANMTHD

This table contains information about each METHOD associated with the J2EEcontainer involved in the activity. It is populated by SMF record SMF_120_5_X(built by Tivoli Decision Support for z/OS record procedure DRL2SA05).



ACTIVITY_START_TME K TIMESTAMP Activity start time. From SM120JAB.



ASID K INTEGER Server region address space ID involved to processthis activity from SM120ASR.

STOKEN K CHAR(16) It is set to ASSBSTKN which is the address token ofthe address space which created the new activity.From SM120JAB.

IP_HOST_ADDRESS K CHAR(16) IP Server address. From last 4 bytes of SM120JAB.


SYSPLEX_NAME K CHAR(8) Sysplex Name. From SM120JA4.

BEAN_TYPE K CHAR(20) The type of bean. Possible values are 'CMP entity','BMP entity', ' Stateless session', ' Stateful session', and' Message Driven'. From SM120JB3.

ACT_EXEC_TIME REAL Indicates the average number of seconds theenterprise bean container activated (retrieved fromsecondary storage) the enterprise bean during theactivity.From SM120JML.

ACT_EXEC_TIME_MAX REAL Indicates the maximum number of seconds theenterprise bean container activated (retrieved fromsecondary storage) the enterprise bean during theactivity. From SM120JMM.

ACT_INVOCATIONS REAL EJBActivation number of invocations. Indicates thenumber of times the enterprise bean's containeractivated(retrieved from secondary storage) theenterprise bean, during the activity. Note, becausestateless session beans are never activated, this datapoint is not applicable to them. From SM120JMK.

BEAN_AMC_NAME VARcHAR(66) AMCName of the bean activated by the container.Truncated to the first right most 66 bytes. FromSM120JB1.


CPU_SEC_AVG REAL Average CPU time in seconds. Calculated as AVG ofSM120JMQ/1000000.


CPU_SEC_MIN REAL Minimum CPU time in seconds. Calculated as MIN ofSM120JMR/1000000.

LOAD_EXEC_TIME REAL Indicates the average number of seconds theenterprise bean has required to load information fromthe database into themselves during the activity. FromSM120JMF.

LOAD_EXEC_TIME_MAX REAL Indicates the maximum number of seconds theenterprise bean has required to load information fromthe database into themselves during the activity. FromSM120JMG.

LOAD_INVOCATIONS REAL EJB Load number of invocations. Indicates thenumber of times entity beans loaded information fromthe database into themselves. From SM120JME.

METHOD_INVOCATION REAL The number of times a method was invoked duringthe activity. From SM120JM2.



METHOD_NAME VARCHAR(66) The name of the method including its signature in itsexternalized, human readable form. If the length ofthe method exceeds 66 bytes in EBCDIC format, theleft most 66 characters are recorded. From SM120JM1.


PASS_EXEC_TIME REAL EJBPassivation number of passivations. Indicates thenumber of times the enterprise bean's containerpassivated (transferred to secondary storage) the bean,during the activity. Note, because stateless sessionbeans are never passivated, they are not included inthe total.From SM120JMN.

PASS_EXEC_TIME_MAX REAL Indicates the average number of seconds theenterprise bean's container passivated (transferred tosecondary storage) the bean during the activity. FromSM120JMO.

PASS_INVOCATIONS REAL EJBPassivation number of passivations. Indicates thenumber of times the enterprise bean's containerpassivated (transferred to secondary storage) the bean,during the activity. Note, because stateless sessionbeans are never passivated, they are not included inthe total.From SM120JMN.

REENTRANCE_POLICY CHAR(3) The bean's reentrance policy. Possible value:'NO' Notreentrant within transactions' Reentrant withintransaction.From SM120JB7.

RESPONSE_TIME_AVG REAL Average response time in seconds. From SM120JM3.

RESPONSE_TIME_MAX REAL Maximum response time in seconds. From SM120JM4.

STORE_EXEC_TIME REAL Indicates the average number of seconds the entitybean persisted its state in the database during theactivity. From SM120JMI.

STORE_EXEC_TIME_MAX REAL Indicates the maximum number of seconds the entitybean persisted its state in the database as measuredduring the activity. From SM120JMJ.

STORE_INVOCATIONS REAL EJBStore number of invocations. Indicates the numberof times an entity bean persisted its state in thedatabase during the activity. From S120SMH.


TRANSACTION_POLICY CHAR(16) The bean method transaction policy. Values fromcom.ibm.WebSphere for z/OS.csi.TransactionAttribute.java possible values:TX_NOT_SUPPORTEDTX_BEAN_MANAGEDTX_REQUIREDTX_SUPPORTSTX_REQUIRES_NEWTX_MANDATORYTX_NEVER

WEB_J2EE_CONTAINER VARCHAR(8) The WebSphere for z/OS container name. This ishardcoded to "Default" for the 4.0.1 timeframe. FromSM120JA8.



WEB_SER_INSTA_NAME CHAR(8) WebSphere for z/OS transaction server instance name.From SM120JA6.



From SM120JA5.

WLM_ENCLAVE_TOKEN CHAR(16) The WLM enclave token. From SM120JA9.

WAS_ACT_J2EECNT

This table contains information about J2EE container during the activity. It ispopulated by SMF record SMF_120_5_X (built by Tivoli Decision Support for z/OSrecord procedure DRL2SA05).





IP_HOST_ADDRESS K CHAR(16) IP Server address. From last 4 bytes of SM120WAF.

ASID K INTEGER Server region address space ID involved to processthis activity. From SM120WAE.




DISTINCT_MTHDS_INV REAL Number of distinct methods invocation during theactivity. Calculated as COUNT() of bean methodsection occurrences.

ENTITY_ACTIV REAL Indicates the number of times the enterprise beancontainers activated (retrieved from secondarystorage) the enterprise beans during the activity.Calculated as SUM of SM120JMK, where SM120JB3=0,1, 4, or 5.

ENTITY_CREATE REAL Indicates the number of entity bean objects created bythe server during the activity. Calculated as SUM ofSM120JM2 for SM120JM1='create()' or 'create:', whereSM120JB3=0, 1, 4 or 5.

ENTITY_LOAD REAL Indicates the number of times entity beans loadedinformation from the database into themselves duringthe interval. Calculated as SUM of sm120JME.

ENTITY_PASSIVATE REAL Indicates the number of times the enterprise beancontainers passivated (transferred to secondarystorage) the enterprise beans during the activity.Calculated as SUM of SM120JMN, where SM120JB3=0,1, 4, or 5.



ENTITY_REMOVE REAL Indicates the number of times entity bean instanceswere removed during the activity. The enterprise beaninstance might have been removed by the remove()method. Calculated as SUM of SM120JM2 forSM120JM1='remove()' or 'remove:', where sm120jb3=0,1, 4, or 5.

ENTITY_STORE REAL Indicates the number of times entity beans storedinformation in the database during the activity.Calculated as SUM of SM120JMH.

MESSAGE_DRIVEN REAL Indicates the total number of times an onMessagemethod was invoked against the listed session beans,as measured during the activity. Calculated as SUM ofSM120JM2 for SM120JM1='onMessage()' or'onMessage:', where SM120JB3=6.

METHOD_INVOCATION REAL The number of methods invocation during theactivity. Calculated as SUM of SM120JM2.


RESPONSE_TIME_AVG REAL Average response time in seconds during the activity.Calculated as AVG of SM120JM3 withDISTINCT_MTHDS_ INV.

RESPONSE_TIME_MAX REAL Maximum response time in seconds during theactivity. Calculated as MAX of SM120JM4.

STATEFUL_ACTIV REAL Indicates the number of times the stateful sessionbean containers activated (retrieved from secondarystorage) the enterprise beans during the activity.Calculated as SUM of sm120jmk, where sm120jb3=3.

STATEFUL_CREATE REAL Indicates the total number of times the create()method was invoked against the listed stateful sessionbeans during the activity. Calculated as SUM ofSM120JM2 for SM120JM1='create()' or 'create:', whereSM120JB3=3.

STATEFUL_PASSIVATE REAL Indicates the number of times the stateful sessionbean containers passivated (transferred to secondarystorage) the enterprise beans during the activity.Calculated as SUM of SM120JMN, where SM120JB3=3.

STATEFUL_REMOVE REAL Indicates the total number of times the remove()method was invoked against the listed stateful sessionbeans, as measured during the activity. Calculated asSUM of SM120JM2 for SM120JM1='remove()' or'remove:', where SM120JB3=3.

STATELESS_CREATE REAL Indicates the total number of times the create()method was invoked against the listed statelesssession beans during the activity. Calculated as SUMof SM120JM2 for SM120JM1='create()' or 'create:',where SM120JB3=2.


WEB_J2EE_CONTAINER VARCHAR(8) The WebSphere for z/OS container name. This ishardcoded to “Default” for the 4.0.1 timeframe.FromSM120JA8.



WEB_SER_INSTA_NAME CHAR(8) WebSphere for z/OS transaction server instance name.From SM120JA6.



From SM120JA5.

WLM_ENCLAVE_TOKEN CHAR(16) The WLM enclave token. From SM120JA9.

WAS_ACT_BEANMTHD_V

This view contains information about each bean method associated with the J2EEcontainer involved in the activity. It is based on the WAS_ACT_BEANMTHD tableand its data comes from SMF_120_5.

Note:

As well as the calculated columns described here, this view also contains all thedata columns described in the source table.





ASID K INTEGER Server region address space ID involved to processthis activity. From SM120JA7.


SYSPLEX_NAME K CHAR(8) Sysplex Name. From SM120JA4.

WEB_J2EE_CONTAINER K VARCHAR(8) The WebSphere for z/OS container name. This ishardcoded to "Default" for the 4.0.1 timeframe. FromSM120JA8.

BEAN_AMC_NAME K VARCHAR(66) BEAN_AMC_NAME

METHOD_NAME K VARCHAR(66) The name of the method including its signature in itsexternalized, human readable form. If the length ofthe method exceeds 66 bytes in EBCDIC format, theleft most 66 characters are recorded. From SM120Jm1.


CELL_NAME CHAR(8) WebSphere for z/OS transaction server cell name.From SM120CEL

CPU_SEC_AVG REAL Average CPU time in seconds. Calculated as AVG ofSM120JMQ/1000000.


CPU_SEC_MIN REAL Minimum CPU time in seconds. Calculated as MIN ofSM120JMR/1000000



NODE_NAME CHAR(8) WebSphere for z/OS transaction server node name.From SM120NOD

WAS_ACT_J2EECNT_V

This view contains information about the J2EE container during the activity. It isbased on the WAS_ACT_J2EECNT table and its data comes from SMF_120_5.

Note:

As well as the calculated columns described here, this view also contains all thedata columns described in the source table.


ASID K INTEGER server region address space ID involved to processthis activity. From SM120JA7.





SYSPLEX_NAME K CHAR(8) Sysplex Name. From SM120JA4

WEB_J2EE_CONTAINER K VARCHAR(8) The WebSphere for z/OS container name. This ishardcoded to "Default" for the 4.0.1 timeframe. FromSM120JA8.

CELL_NAME CHAR(8) WebSphere for z/OS transaction server cell name.From SM120CEL

NODE_NAME CHAR(8) WebSphere for z/OS transaction server node name.From SM120NOD


4. Request Activity subcomponent tables and views:This section describes the tables and views for the WebSphere Request Activitysubcomponent.

WASACT_REQAPPL_H, _D, _M

The Application Request Activity tables provide statistics on requests for a givenapplication. From record SMF_120_9.


DATE K DATE Date when the record was moved into the SMF buffer.From SM120DTE.

TIME K TIME Time when the record was moved into the smf buffer.From SM120TME



MVS_SYSTEM_ID K CHAR(4) The name of the system on which the product isrunning. From SM1209BR.

SYSPLEX_NAME K CHAR(8) The name of the sysplex on which the product isrunning. From SM1209BS.

CONTROLLER_JOBNAME K CHAR(8) The job name for the controller. From SM1209BT.

REQUEST_TYPE K CHAR(8) The type of request that was processed: 0 - Notknown1 - IIOP2 - HTTP3 - HTTPS4 - MDB plan "A"5 - MDB plan "B"6 - MDB plan "C"7 - SIP8 - SIPS9 - MBEAN10 - OTS11 - Internal From SM1209CK.

APPLICATION K CHAR(128) The name of the application. From SM1209EO, IfSM1209EM is 1.

NO_REQUESTS INTEGER The number of requests in this period.

CPU_DISPATCH_SEC FLOAT The total amount of CPU time, in seconds, that isused by dispatch TCB. From SM1209CI.

REQUEST_PROC_SEC FLOAT The total interval, in seconds, between the time thatthe request was received, and the time the controllerfinished processing the request response. FromSM1209CM and SM1209CQ.

NONSTD_CPU_SEC FLOAT The total amount of CPU time that was spent onnon-standard CPS, such as the System Z ApplicationAssist Processor (ZAAP) and Z9 IntegratedInformation Processor (ZIIP), In seconds. FromSM1209CX.

REQUEST_ENCL_SEC FLOAT The total enclave CPU time at the end of the dispatch.In seconds. From SM1209DA.

ZAAP_ENCL_SEC FLOAT The total enclave ZAAP CPU time at the end of thedispatch, in seconds. this is normalized to the speedof regular CPS. From SM1209DB*SM1209DG/256.

ZAAP_ELIG_CPU FLOAT The total CPU time at the end of the dispatch of thisrequest spent on a regular CP that could have beenrun on a ZAAP, but the ZAAP was not available. Thevalue is normalized and in seconds. FromSM1209DC*SM1209DG/256.

ZIIP_ENCL_SEC FLOAT The total ZIIP enclave that is on the CPU at the endof the dispatch of this request, in seconds. The time isnormalized to standard processor speed. FromSM1209DD.

ZIIP_QUALITY_ENCL FLOAT The total ZIIP quality time enclave that was on theCPU at the end of the dispatch of this request, inseconds. The time is normalized to standard processorspeed. From SM1209DE.



ZIIP_ELIG_ENCL FLOAT The total eligible ZIIP enclave that is on the CPU atthe end of the dispatch of this request, in seconds.The time is normalized to standard processor speed.From SM1209DF.

ENCL_SEC FLOAT The total amount of CPU time that was used by theenclave,in seconds. From SM1209DH.

ENCL_DEL_ZAAP FLOAT The total delete ZAAP CPU enclave, in seconds. FromSM1209DI.

ENCL_DEL_ZIIP FLOAT The total enclave delete ZIIP time accumulated by theenclave, in seconds. From SM1209DK.

ENCL_DEL_ZIIP_SRV FLOAT The total enclave delete ZIIP service accumulated bythe enclave, in seconds. From SM1209DL.

ENCL_DEL_ZAAP_SRV FLOAT The total enclave delete ZAAP service accumulatedby the enclave, in seconds. From SM1209DM.

ENCL_DEL_SRV FLOAT The total enclave delete CPU service accumulated bythe enclave, in seconds. From SM1209DN.

CXCOUNT INTEGER A counter used to measure how many SM1209CXfields had a value greater than -1 used in the view tocalculate an average.

DICOUNT INTEGER A counter used to measure how many SM1209DIfields had a value greater than 0. Used in the view tocalculate an average.

DKCOUNT INTEGER A counter used to measure how many SM1209DKfields had a value greater than 0. Used in the view tocalculate an average.

DLCOUNT INTEGER A counter used to measure how many SM1209DLfields had a value greater than 0. Used in the view tocalculate an average.

DMCOUNT INTEGER A counter used to measure how many SM1209DMfields had a value greater than 0. Used in the view tocalculate an average.

DNCOUNT INTEGER A counter used to measure how many SM1209DNfields had a value greater than 0. Used in the view tocalculate an average.

WASACT_REQCONT__H, _D, _M

The Application Request Activity tables provide statistics on requests for acontroller. From record SMF_120_9.


DATE K DATE Date when the record was moved into the smf buffer.From SM120DTE.

TIME K TIME Time when the record was moved into the smf buffer.From SM120TME.








CPU_DISPATCH_SEC FLOAT The total amount of CPU time, in seconds, that isused by dispatch TCB. From SM1209CI.

REQUEST_PROC_SEC FLOAT The total interval, in seconds, between the time thatthe request was received, and the time the controllerfinished processing the request response. FromSM1209CM and SM1209CQ.

NONSTD_CPU_SEC FLOAT The total amount of CPU time that was spent onnon-standard CPS, such as the System Z ApplicationAssist Processor (ZAAP) and Z9 IntegratedInformation Processor (ZIIP), in seconds. FromSM1209CX.

REQUEST_ENCL_SEC FLOAT The total enclave CPU time at the end of the dispatch,in SECONDS. From SM1209DA.

ZAAP_ENCL_SEC FLOAT The total enclave ZAAP CPU time at the end of thedispatch, in seconds. This is normalized to the speedof regular CPS. From SM1209DB*SM1209DG/256.

ZAAP_ELIG_CPU FLOAT The total CPU time at the end of the dispatch of thisrequest spent on a regular CP that could have beenrun on a ZAAP, but the ZAAP was not available. Thevalue is normalized and in seconds. FromSM1209DC*SM1209DG/256.

ZIIP_ENCL_SEC FLOAT The total ZIIP enclave that is on the CPU at the endof the dispatch of this request, in seconds. The time isnormalized to standard processor speed. FromSM1209DD.

ZIIP_QUALITY_ENCL FLOAT The total ZIIP quality time enclave that was on theCPU at the end of the dispatch of this request, inseconds. The time is normalized to standard processorspeed. From SM1209DE.

ZIIP_ELIG_ENCL FLOAT The total eligible ZIIP enclave that is on the CPU atthe end of the dispatch of this request, in seconds.The time is normalized to standard processor speed.From SM1209DF.

ENCL_SEC FLOAT The total amount of CPU time that was used by theenclave,in seconds. From SM1209DH.

ENCL_DEL_ZAAP FLOAT The total delete ZAAP CPU enclave, in seconds. FromSM1209DI.

ENCL_DEL_ZIIP FLOAT The total enclave delete ZIIP time accumulated by theenclave, in seconds. From SM1209DK.



ENCL_DEL_ZIIP_SRV FLOAT The total enclave delete ZIIP service accumulated bythe enclave, in seconds. From SM1209DL.

ENCL_DEL_ZAAP_SRV FLOAT The total enclave delete ZAAP service accumulatedby the enclave, in seconds. From SM1209DM.

ENCL_DEL_SRV FLOAT The total enclave delete CPU service accumulated bythe enclave, in seconds. From SM1209DN.

CXCOUNT INTEGER A counter used to measure how many sm1209cxfields had a value greater than -1 used in the view tocalculate an average.

DICOUNT INTEGER A counter used to measure how many SM1209DIfields had a value greater than 0. Used in the view tocalculate an average.

DKCOUNT INTEGER A counter used to measure how many SM1209DKfields had a value greater than 0. Used in the view tocalculate an average.

DLCOUNT INTEGER A counter used to measure how many SM1209DLfields had a value greater than 0. Used in the view tocalculate an average.

DMCOUNT INTEGER A counter used to measure how many SM1209DMfields had a value greater than 0. Used in the view tocalculate an average.

DNCOUNT INTEGER A counter used to measure how many SM1209DNfields had a value greater than 0. Used in the view tocalculate an average.

WASACT_REQAPPL_HV, _DV, _MV

The Application Request Activity Views provide averages on the requests for agiven application. From record SMF_120_9.










APPLICATION K CHAR(128) The name of the application. From SM1209EO, IfSM1209EM is 1.


CPU_DISPATCH_SEC FLOAT The average amount of CPU time, in seconds, that isused by dispatch TCB. From SM1209CI.

REQUEST_PROC_SEC FLOAT The average interval, in seconds, between the timethat the request was received, and the time thecontroller finished processing the request response.From SM1209CM and SM1209CQ.

NONSTD_CPU_SEC FLOAT The average amount of CPU time that was spent onnon-standard CPS, such as the System Z ApplicationAssist Processor (ZAAP) and Z9 IntegratedInformation Processor (ZIIP), in seconds. FromSM1209CX.

REQUEST_ENCL_SEC FLOAT The average enclave CPU time at the end of thedispatch, in seconds. From SM1209DA.

ZAAP_ENCL_SEC FLOAT The average enclave ZAAP CPU time at the end ofthe dispatch, in seconds.This is normalized to thespeed of regular CPS. From SM1209DB*SM1209DG/256.

ZAAP_ELIG_CPU FLOAT The average CPU time at the end of the dispatch ofthis request spent on a regular CP that could havebeen run on a ZAAP, but the ZAAP was notavailable. the value is normalized and in seconds.From SM1209DC*SM1209DG/256.

ZIIP_ENCL_SEC FLOAT The average ZIIP enclave that is on the CPU at theend of the dispatch of this request, in seconds. thetime is normalized to standard processor speed. FromSM1209DD.

ZIIP_QUALITY_ENCL FLOAT The average ZIIP quality time enclave that was on theCPU at the end of the dispatch of this request, inseconds. The time is normalized to standard processorspeed. From SM1209DE.

ZIIP_ELIG_ENCL FLOAT The average eligible ZIIP enclave that is on the CPUat the end of the dispatch of this request, in seconds.The time is normalized to standard processor speed.From SM1209DF.

ENCL_SEC FLOAT The average amount of CPU time that was used bythe enclave,in seconds. From SM1209DH.



ENCL_DEL_ZAAP FLOAT The average delete ZAAP CPU enclave, in seconds.From SM1209DI.

ENCL_DEL_ZIIP FLOAT The average enclave delete ZIIP time accumulated bythe enclave, in seconds. From SM1209DK.

ENCL_DEL_ZIIP_SRV FLOAT The average enclave delete ZIIP service accumulatedby the enclave, in seconds. From SM1209DL.

ENCL_DEL_ZAAP_SRV FLOAT The average enclave delete ZAAP serviceaccumulated by the enclave, in seconds. FromSM1209DM.

ENCL_DEL_SRV FLOAT The average enclave delete CPU service accumulatedby the enclave, in seconds. From SM1209DN.

WASACT_REQCONT_H, _D, _M

The Application Request Activity Views provide averages on the requests for acontroller. From record SMF_120_9.









CPU_DISPATCH_SEC FLOAT The average amount of CPU time, in seconds, that isused by dispatch TCB. From SM1209CI.

REQUEST_PROC_SEC FLOAT The average interval, in seconds, between the timethat the request was received, and the time thecontroller finished processing the request response.From SM1209CM and SM1209CQ.



NONSTD_CPU_SEC FLOAT The average amount of CPU time that was spent onnon-standard CPS, such as the System Z ApplicationAssist Processor (ZAAP) and Z9 IntegratedInformation Processor (ZIIP), in seconds. FromSM1209CX.

REQUEST_ENCL_SEC FLOAT The average enclave CPU time at the end of thedispatch, in seconds. From SM1209DA.

ZAAP_ENCL_SEC FLOAT The average enclave ZAAP CPU time at the end ofthe dispatch, in seconds. this is normalized to thespeed of regular CPS. From SM1209DB*SM1209DG/256.

ZAAP_ELIG_CPU FLOAT The average CPU time at the end of the dispatch ofthis request spent on a regular CP that could havebeen run on a ZAAP, but the ZAAP was notavailable. The value is normalized and in seconds.From SM1209DC*SM1209DG/256.

ZIIP_ENCL_SEC FLOAT The average ZIIP enclave that is on the CPU at theend of the dispatch of this request, in seconds. Thetime is normalized to standard processor speed. FromSM1209DD.

ZIIP_QUALITY_ENCL FLOAT The average ZIIP quality time enclave that was on theCPU at the end of the dispatch of this request, inseconds. the time is normalized to standard processorspeed. From SM1209DE.

ZIIP_ELIG_ENCL FLOAT The average eligible ZIIP enclave that is on the CPUat the end of the dispatch of this request, in seconds.the time is normalized to standard processor speed.From SM1209DF.

ENCL_SEC FLOAT The average amount of CPU time that was used bythe enclave,in seconds. From SM1209DH.

ENCL_DEL_ZAAP FLOAT The average delete ZAAP CPU enclave, in seconds.From SM1209DI.

ENCL_DEL_ZIIP FLOAT The average enclave delete ZIIP time accumulated bythe enclave, in seconds. From SM1209DK.

ENCL_DEL_ZIIP_SRV FLOAT The average enclave delete ZIIP service accumulatedby the enclave, in seconds. From SM1209DL.

ENCL_DEL_ZAAP_SRV FLOAT The average enclave delete ZAAP serviceaccumulated by the enclave, in seconds. FromSM1209DM.

ENCL_DEL_SRV FLOAT The average enclave delete CPU service accumulatedby the enclave, in seconds. From SM1209DN.

WASACT_OUTCONT_H, _D, _M

The Outbound Request tables provide statistics on requests for a controller. Fromrecord SMF_120_10.





TIME K TIME Time when the record was moved into the SMFbuffer. From SM120TME.Note: This column only exists in tableWASACT_OUTCONT_H .

MVS_SYSTEM_ID K CHAR(8) The name of the system on which the product isrunning. From SM120ABR.

SYSPLEX_NAME K CHAR(8) The name of the sysplex on which the product isrunning. From SM120ABS.

CONTROLLER_JOBNAME K CHAR(8) The job name for the controller. From SM120ABT.

REQUEST_TYPE K CHAR(8) Outbound request type:

v 0 - Unknown

v 1 - WOLA

v 2 - OTMA

From SM120ACK.

REGISTER_NAME K CHAR(12) The register name the outbound request is going to.From SM120AD6, if SM120ACK is 1; FromSM120ADK, if SM120ACK is 2.

SERVICE_NAME K VARCHAR (64) The service name the outbound request is going to.From SM120AD7, if SM120ACK is 1; FromSM120ADL, if SM120ACK is 2.


BYTES_SENT FLOAT The total number of bytes sent per controller. FromSM120AD1.

BYTES_RECEIVED FLOAT The total number of response bytes per controller.From SM120AD2.

RESPONSE_SEC FLOAT The total amount of the outbound request responsetime. From SM120AD4 minus SM120AD3.

WASACT_OUTCONT_HV, _DV, _MV

The Outbound Request views provide averages on requests for a controller. It isbased on the table WASACT_OUTCONT and its data comes from recordSMF_120_10.



TIME K TIME Time when the record was moved into the SMFbuffer. From SM120TME.Note: This column only exists in tableWASACT_OUTCONT_HV.







v 0 - Unknown

v 1 - WOLA

v 2 - OTMA

From SM120ACK.




AVG_BYTES_SENT FLOAT The average number of bytes sent per controller. FromSM120AD1.

AVG_BYTES_RECEIVED FLOAT The average number of response bytes per controller.From SM120AD2.

AVG_RESPONSE_SEC FLOAT The average amount of the outbound requestresponse time. From SM120AD4 minus SM120AD3.

WASACT_OUTSERV_H, _D, _M

The Outbound Request tables provide statistics on requests for a servant. Fromrecord SMF_120_10.



TIME K TIME Time when the record was moved into the SMFbuffer. From SM120TME.Note: This column only exists in tableWASACT_OUTSERV_H.




SERVANT_JOBNAME K CHAR(8) The job name for the dispatch servant. FromSM120ACR.


v 0 - Unknown

v 1 - WOLA

v 2 - OTMA

From SM120ACK.






BYTES_SENT FLOAT The total number of bytes sent per controller. FromSM120AD1.

BYTES_RECEIVED FLOAT The total number of response bytes per controller.From SM120AD2.

RESPONSE_SEC FLOAT The total amount of the outbound request responsetime. From SM120AD4 minus SM120AD3.

WASACT_OUTSERV_HV, _DV, _MV

The Outbound Request views provide averages on requests for a servant. It isbased on the table WASACT_OUTSERV and its data comes from recordSMF_120_10.



TIME K TIME Time when the record was moved into the SMFbuffer. From SM120TME.Note: This column only exists in tableWASACT_OUTSERV_HV.




SERVANT_JOBNAME K CHAR(8) The job name for the dispatch servant. FromSM120ACR.


v 0 - Unknown

v 1 - WOLA

v 2 - OTMA

From SM120ACK.




AVG_BYTES_SENT FLOAT The average number of bytes sent per controller. FromSM120AD1.

AVG_BYTES_RECEIVED FLOAT The average number of response bytes per controller.From SM120AD2.



AVG_RESPONSE_SEC FLOAT The average amount of the outbound requestresponse time. From SM120AD4 minus SM120AD3.

ReportsThe reporting function produces reports based on the data in the Tivoli DecisionSupport for z/OS database. Reports can show data from tables or from views. Youcan request reports online or by submitting batch jobs. Typically, you use onlinereporting for reports that you use once, and batch reporting for regularly requiredreports. This chapter gives examples of reports that belong to the WebSphereApplication Server component.

WebSphere Application Server Statistics, Daily Trend reportThis report is supplied with the Server Interval Subcomponent, and shows anoverview of WebSphere Application Server server workload by day.


Report ID:WASSI01

Report group:WebSphere reports

Source:WAS_INT_SERVER_D

Attributes:WEBSPHERE, SERVER, DAILY

Variables:DATE, WEB_SER_NAME, MVS_SYSTEM_ID, SYSPLEX_NAME, PERIOD


DATE The date of the day for the measurement.

WEB SERVER NAMEWebSphere Application Server for z/OS transaction server name.

PERIODName of the period.

WebSphere Server statistics, Daily TrendSYSPLEX NAME:’UTCPLXBS’MVS SYSTEM:’S1E ’CELL NAME: ’S1E ’NODE NAME: ’S1E ’SERVER NAME: All

WEB GLOBALSERVER SERVER GLOBAL LOCAL EXIST

DATE NAME PERIOD TYPE TRANSACTIONS TRANSACTIONS SESSIONS---------- -------- -------- ------ ------------ ------------ ----------2002-12-18 IBWJSR2 NIGHT J2EE 2.21670E+04 3.21540E+04 0.000E+00

Tivoli Decision Support for z/OS: WASSI01

Figure 215. Example of a WebSphere Application Server Statistics, Daily Trend report (partial view)


SERVER TYPEWebSphere Application Server for z/OS server type.

GLOBAL TRANSACTIONSNumber of global transactions that were started in the server region.

LOCAL TRANSACTIONSNumber of local transactions that were started in the server region.

GLOBAL EXIST SESSIONSNumber of communications sessions that exist. No longer significant forWebSphere Application Server Version 5.1, and later.

LOCAL EXIST SESSIONSNumber of local communications sessions that exist. No longer significantfor WebSphere Application Server Version 5.1, and later.

REMOTE EXIST SESSIONSNumber of remote communications sessions that exist. No longersignificant for WebSphere Application Server Version 5.1, and later.

GLOBAL CLIENT RECEIVEDNumber of KBytes that have been transferred to the server from allattached clients.

GLOBAL CLIENT SENT KBNumber of KBytes that have been sent from the server to all attachedclients.

LOCAL CLIENT RECEIVED KBNumber of KBytes that have been transferred to the server from all locallyattached clients.

LOCAL CLIENT SENT KBNumber of KBytes that have been sent from the server to all locallyattached clients.

REMOTE CLIENT RECEIVED KBNumber of KBytes that have been transferred to the server from allremotely attached clients.

REMOTE CLIENT SENT KBNumber of KBytes that have been sent from the server to all remotelyattached clients.

WebSphere Application Server Session Statistics, Daily TrendreportThis report is supplied with the Server Interval subcomponent, and shows asummary overview of WebSphere Application Server session statistics by day.


Report ID:WASSI02


Source:WAS_INT_SERVER_D

Attributes:WEBSPHERE, SERVER, SESSIONS, DAILY


Variables:DATE, CELL_NAME, NODE_NAME, WEB_SER_NAME,MVS_SYSTEM_ID, SYSPLEX_NAME, PERIOD


Date The date of the day for the measurement.

Web Server NameWebSphere Application Server for z/OS transaction server name.

Period Name of the period.

Global Exist SessionsNumber of communication sessions that exist at the end of the interval. Nolonger significant for WebSphere Application Server Version 5.1, and later.

Global Active SessionsMaximum number of active communication sessions that have been activeduring the interval.

Local Exist SessionsNumber of local communication sessions that exist at the end of theinterval. No longer significant for WebSphere Application Server Version5.1, and later.

Local Active SessionsMaximum number of active communications that have been attachedwithin the server instance during the interval.

Remote Exist SessionsNumber of remote communication sessions that exist at the end of theinterval. No longer significant for WebSphere Application Server Version5.1, and later.

Remote Active SessionsMaximum number of active remote communication sessions that have beenattached within the server instance.

HTTP Exist SessionsNumber of HTTP communication sessions that exist at the end of theinterval. No longer significant for WebSphere Application Server Version5.1, and later.

WebSphere Sessions Statistics, Daily TrendSYSPLEX NAME:’BOSS0153’

MVS SYSTEM: ’SY1’CELL NAME: ’SY1’NODE NAME: ’SY1’

SERVER NAME: ’BBOC001’

Web Global Global Local LocalServer Exist Active Exist Active

Date Name Period Sessionsb Sessions Sessions Sessions---------- -------- ------- -------- -------- -------- --------2005-03-03 BBOC001 PRIME 0.000 1.000 0.000 0.000


Figure 216. Example of a WebSphere Application Server Session Statistics, Daily Trend (partial view)


HTTP Active SessionsNumber of HTTP communication sessions that have been attached andactive within the server instance during the interval.

WebSphere Application Server Workload Statistics, Daily TrendreportThis report is supplied with the Server Interval subcomponent, and shows a shortsummary overview of WebSphere Application Server workload statistics by day.


Report ID:WASSI03


Source:WAS_INT_SERVER_DV

Attributes:WEBSPHERE, SERVER, WORKLOAD, DAILY

Variables:DATE, SYSPLEX_NAME, MVS_SYSTEM_ID, CELL_NAME,NODE_NAME, WEB_SER_NAME, PERIOD





Received KBytes rateNumber of total KB received by the server from all clients in a second.

Sent KBytes rateNumber of total KB sent from the server to all clients in a second.

HTTP Received KBytes rateNumber of total KB received by the server from all HTTP clients in asecond.

WebSphere Workload Statistics, Daily TrendSYSPLEX NAME:’BOSS0153’MVS SYSTEM: ’SY1’CELL NAME: ’SY1’NODE NAME: ’SY1’


HTTP HTTPWeb Received Sent Received Sent CPUServer Kbytes Kbytes Kbytes Kbytes busy

Date Name Period rate rate rate rate percentage---------- -------- ------ -------- ------- -------- ------ ----------2005-03-03 BBOC001 PRIME 0.002 0.002 0.002 0.002 5.669E-02


Figure 217. Example of a WebSphere Application Server Workload Statistics, Daily Trend (partial view)


HTTP Sent KBytes rateNumber of total KB sent from the server to all HTTP clients in a second.

CPU Busy PercentagePercentage of enclave Workload Manager CPU time on the total.

WebSphere Application Server JVM Heap Statistics, Daily TrendreportThis report is supplied with the Server Interval subcomponent, and shows asummary overview of WebSphere Application Server JVM Heap statistics by day.


Report ID:WASSI04


Source:WAS_INT_HEAP_D

Attributes:WEBSPHERE, SERVER, DAILY, JVM, HEAP

Variables:DATE, MVS_SYSTEM_ID, SYSPLEX_NAME, CELL_NAME,NODE_NAME, WEB_SER_NAME, WEB_SER_INST_NAME, PERIOD,HEAP_ID


Date The date of the day for the measurement.


Web Server Instance NameWebSphere Application Server for z/OS transaction server instance name.


Heap IdHeap identifier.

WebSphere JVM Heap Statistics, Daily TrendSYSPLEX NAME:’BOSS0153’

MVS SYSTEM: ’SY1’CELL NAME: ’SY1’NODE NAME: ’SY1’


Web MinimumWeb Server Garbage TotalServer Instance Heap Collection Storage

Date Name Name Period Id Count Kbytes---------- -------- -------- ------ ---------- ---------- ----------2005-03-03 BBOC001 BBOC001 PRIME 00000002 8.000 1.956E+05


Figure 218. Example of a WebSphere Application Server JVM Heap Statistics, Daily Trend (partial view)


Garbage Collection CountTotal garbage collection count.

Minimum Total Storage KbytesMinimum total storage, in KB.

Maximum Total Storage KbytesMaximum total storage, in KB.

Average Total Storage KbytesAverage total storage, in KB.

Minimum Free Storage KbytesMinimum free storage, in KB.

Maximum Free Storage KbytesMaximum free storage, in KB.

Average Free Storage KbytesAverage free storage, in KB.

WebSphere Application Server User Credentials Statistics reportThis report is supplied with the Server Activity subcomponent and is availableonly in WebSphere Application Server Version 5. It shows the monthly usage ofbytes received/transmitted and CPU usage for a user identified by his credentials.


Report ID:WASSA01


Source:WAS_ACT_USR_M

Attributes:WEBSPHERE, USER, MONTHLY

Variables:DATE, WEB_SER_NAME, USER_CREDENTIALS, CLIENT_IP_ADDRESS,MVS_SYSTEM_ID, SYSPLEX_NAME, PERIOD


Date First day of the month for the statistics.


WebSphere User Credentials Statistics

IP Client WebHOST IP User Server

Date Period Address Address Credentials Name---------- ------ ---------- ---------- ----------- -------2005-08-01 PRIME 9.38.48.55 9.38.48.55 IBMUSER BBOC0012005-08-01 NIGHT 9.38.48.55 9.38.48.55 IBMUSER BBOC0012005-09-01 PRIME 9.38.48.55 9.38.48.55 IBMUSER BBOC001

Tivoli Decision Support for z/OS: WASSA01

Figure 219. Example of a WebSphere Application Server User Credentials Statistics report (partial view)


IP HOST addressThe IP address of the transaction server.

Client IP addressThe IP address of the client (or job name).

User CredentialsThe credentials under which the user started the activities.

Web Server NameWebSphere of z/OS transaction server name.

MVS System IDMVS system identifier.

Sysplex NameThe Sysplex name.

Bytes receivedBytes received by the transaction server.

Bytes transmittedBytes transmitted from the transaction server

Total CPU secondsSeconds of CPU used.

WebSphere Application Server Web Application Statistics, DailyTrend reportThis report is supplied with the J2EE and Web Interval subcomponent, and showsa summary overview of WebSphere Application Server Web Applicationperformance by day.


Report ID:WASWI01


Source:WAS_INT_WEBAPPL_D

Attributes:WEBSPHERE, WEBAPPL, DAILY

Variables:DATE, WEB_APPL_NAME, WEB_SER_NAME, MVS_SYSTEM_ID,SYSPLEX_NAME, PERIOD




WEB SERVER NAMEWebSphere for z/OS transaction server name.

MVS SYSTEM IDMVS system identifier.



WEB APPL NAMEThe WEB Application name.

TOTAL REQUESTSThe number of requests handled.

NUMBER LOADED SERVLETThe number of Servlets loaded.

AVERAGE RESPONSE TIMEThe average time (in seconds) that a Web Application servlets spentperforming services.

MINIMUM RESPONSE TIMEThe minimum time (in seconds) that a Web Application servlet spentperforming services.

MAXIMUM RESPONSE TIMEThe maximum time (in seconds) that a Web Application servlet spentperforming services.

NUMBER ERRORSTotal number of errors.

WebSphere Application Server HTTP Statistics, Daily TrendreportThis report is supplied with the J2EE and Web Interval subcomponent, and showsa summary overview of WebSphere Application Server HTTP session statistics byday.

WEB MVS WEBSERVER SYSTEM SYSPLEX APPL

DATE NAME ID NAME NAME---------- -------- ------ -------- -------------------------------------2002-12-18 IBWJSR2 S1E UTCPLXBS eRWWPriceChangeHTTPSession_262002-12-18 IBWJSR2 S1E UTCPLXBS WebERWWjmsPRR_252002-12-18 IBWJSR2 S1E UTCPLXBS WebERWWDelivery_202002-12-18 IBWJSR2 S1E UTCPLXBS WebERWWJustPC_142002-12-18 IBWJSR2 S1E UTCPLXBS WebERWWNO_192002-12-18 IBWJSR2 S1E UTCPLXBS WebERWWOS_152002-12-18 IBWJSR2 S1E UTCPLXBS WebERWWPay_242002-12-18 IBWJSR2 S1E UTCPLXBS WebERWWPC_212002-12-18 IBWJSR2 S1E UTCPLXBS WebERWWPQ_162002-12-18 IBWJSR2 S1E UTCPLXBS WebERWWSL_17

Tivoli Decision Support for z/OS: WASWI01

Figure 220. Example of a WebSphere Application Server Web Application statistics, Daily Trend report (partial view)



Report ID:WASWI02


Source:WAS_INT_HTTPSESS_D

Attributes:WEBSPHERE, SERVER, DAILY

Variables:DATE, WEB_SER_NAME, WEB_SER_INSTA_NAME, MVS_SYSTEM_ID,SYSPLEX_NAME, PERIOD


DATE First day of the month for the statistics.

CELL NAMEWebSphere Application Server for z/OS transaction server cell name.

NODE NAMEWebSphere for z/OS transaction server node name.


WEB SERVER INSTANCEWebSphere Application Server for z/OS transaction server instance name.


MVS SYSTEM IDMVS system identifier.

SYSPLEX NAMEThe sysplex name.

CREATED SESSIONSThe number of sessions created during the interval. This includes sessionsthat were available, active, or invalidated.

INVALIDATED SESSIONSThe number of sessions invalidated (removed from available or activestate) during the interval.

WEBWEB SERVER MVS

CELL NODE SERVER INSTANCE SYSTEM SYSPLEXDATE NAME NAME NAME NAME ID NAME PERIOD---------- ---- ---- -------- -------- ------ -------- --------2002-12-18 S1E S1E IBWJSR2 IBWJSR2A S1E SYSPLEX1 NIGHT2002-12-18 S1E S1E IBWJSR2 IBWJSR2A S1E SYSPLEX1 PRIME

Tivoli Decision Support for z/OS: WASWI02

Figure 221. Example of WebSphere Application Server HTTP Statistics, Daily Trend (partial view)


ACTIVE SESSIONSCurrent number of HTTP sessions that are actively referenced in the serverat the end of the interval.

MINIMUM ACTIVE SESSIONSMinimum number of HTTP sessions that are actively referenced in theserver at the end of the interval.

MAXIMUM ACTIVE SESSIONSMaximum number of HTTP sessions that are actively referenced in theserver at the end of the interval.

LIFE TIME SESSIONSAverage time, in seconds, of invalidated HTTP sessions remained alive inmemory.

INVALIDATED TIME SESSIONSAverage time, in seconds, that was required to process invalidation ofHTTP sessions, as measured during the interval.

FINALIZED SESSIONSNumber of sessions that were finalized.

LIVE SESSIONSTotal number of HTTP sessions being tracked by the server at the end ofthe interval. This includes both active and inactive sessions.

MINIMUM LIVE SESSIONSMinimum number of live HTTP sessions during the interval.

MAXIMUM LIVE SESSIONSMaximum number of live HTTP sessions during the interval.

WebSphere J2EE Container Statistics, Daily Trend reportThis report is supplied with the J2EE and Web Interval subcomponent, and showsa summary overview of WebSphere J2EE container statistics by day.


Report ID:WASWI03


Source:WAS_INT_J2EECNT_D

Attributes:WEBSPHERE, J2EE, DAILY

Variables:DATE, WEB_SER_NAME, MVS_SYSTEM_ID, SYSPLEX_NAME, PERIOD


The report contains the following information



CELL NAMEWebSphere for z/OS transaction server cell name.

NODE NAMEWebSphere for z/OS transaction server node name.


MVS SYSTEM IDMVS System identifier.

METHOD INVOCATIONTotal number of times the methods were invoked.

AVERAGE RESPONSE TIMEBean Method average response time in seconds.

MAXIMUM RESPONSE TIMEBean Method maximum response time in second.

STATELESS CREATEDTotal number of times the create() method was invoked against the listedstateless session beans.

STATEFUL CREATEDTotal number of times the create() method was invoked against the listedstate full session beans.

ENTITY CREATEDTotal number of entity bean objects created.

STATEFUL REMOVEDTotal number of times the remove() method was invoked against the listedstate full session beans.

ENTITY REMOVEDTotal number of times entity bean instances were removed.

STATEFUL ACTIVATEDTotal number of times the state full session bean containers activated(retrieved from secondary storage) the enterprise beans.

WebSphere J2EE container statistics, Daily TrendSYSPLEX NAME:’UTCPLXBS’

MVS SYSTEM:’S1E ’

WEB AVERAGE MAXIMUMCELL NODE SERVER METHOD RESPONSE RESPONSE STATELESS

DATE PERIOD NAME NAME NAME INVOCATION TIME TIME CREATED---------- -------- ---- ---- -------- ---------- ---------- ---------- ----------2002-12-18 NIGHT S1E S1E IBWJSR2 1.695E+06 5.461E-01 4.420E+02 1.616E+04

PRIME S1E S1E IBWJSR2 6.779E+05 3.141E-01 1.580E+02 6.606E+03Tivoli Decision Support for z/OS: WASWI03

Figure 222. Example of a WebSphere J2EE Container Statistics, Daily Trend report


ENTITY ACTIVATEDTotal number of times the enterprise bean containers activated (retrievedfrom secondary storage) the enterprise beans.

STATEFUL PASSIVATEDTotal number of times the state full session bean containers passivated(transferred to secondary storage) the enterprise beans.

ENTITY PASSIVATEDTotal number of times the enterprise bean containers activated (transferredto secondary storage) the enterprise beans.

ENTITY LOADEDTotal number of times entity beans loaded information from the databaseinto themselves.

ENTITY STOREDTotal number of times entity beans stored information from the databaseinto themselves.

WebSphere Application Server Liberty component

CustomizationBefore you can use the WebSphere® Application Server Liberty component tocollect data, you must customize the component by making input data available.

Making input data availableThis section describes what you have to do to enable SMF recording.

To archive the enabling system management facility (SMF) recording for theWebSphere Application Server Liberty, perform the following steps:1. Enable Liberty SMF recording.2. Edit the SMFPRMxx parmlib member.

Enable Liberty SMF recording:

To enable either of the Liberty system management facility (SMF) recordings(SMF_120_11 and SMF_120_12), see the following procedures accordingly:v Enable SMF_120_11 recordingv Enable SMF_120_12 recording

Enable SMF_120_11 recording:

The z/OS® Request Logging feature, zosRequestLogging-1.0, collects informationabout HTTP requests and records the information to the z/OS SMF data store.When the z/OS Request Logging feature is activated and RACF® is set upcorrectly, SMF type 120 subtype 11 version 2 records are generated.

About this task

To enable SMF_120_11 recording, perform the following steps:

Procedure

1. Enable request logging by adding the zosRequestLogging-1.0 feature in thefeatureManager element of the server.xml configuration file.<feature>zosRequestLogging-1.0</feature>


2. Configure RACF to write the SMF records by issuing the following commands:RDEFINE FACILITY BPX.SMF UACC(NONE)PERMIT BPX.SMF ID(MSTONE1) ACCESS(READ) CLASS(FACILITY)SETROPTS GENERIC(FACILITY) REFRESHSETROPTS RACLIST(FACILITY) REFRESH

3. Optional: Add user data to the SMF records by implementing the UserData APIin your servlets.A servlet can use the UserData add method to add its own request-specific datato the SMF 120, subtype 11, version 2 record that gets written for the HTTPrequest. The UserData interface is in the com.ibm.websphere.zos.request.loggingpackage. The following example shows how a servlet can add its ownrequest-specific data to the SMF record:InitialContext ic = new InitialContext();

try {UserData userData = (UserData) ic.lookup("com/ibm/websphere

/zos/request/logging/UserData");int rc = userData.add(65535,"My request-specific data");

} catch (NamingException e) {}

Enable SMF_120_12 recording:

The z/OS® Java batch SMF logging feature collects information about Java™ batchjobs and records the information to the z/OS SMF data store. When the z/OS Javabatch SMF logging feature is activated and RACF is configured correctly, SMFtype 120, subtype 12, version 1 records are generated.

About this task

To enable SMF_120_12 recording, perform the following steps:

Procedure

1. To enable the z/OS Java batch SMF logging feature, add thebatchSMFLogging-1.0 feature to the server.xml file.<feature> batchSMFLogging-1.0</feature>

2. You must issue RACF commands to authorize the server runtime to create SMFrecording entries into the SMF framework before SMF records are written. Thefollowing example illustrates the RACF commands that you must issue:RDEFINE FACILITY BPX.SMF UACC(NONE)PERMIT BPX.SMF ID(MSTONE1) ACCESS(READ) CLASS(FACILITY)SETROPTS GENERIC(FACILITY) REFRESHSETROPTS RACLIST(FACILITY) REFRESH

Edit the SMFPRMxx parmlib member:

Before you begin, please make a working copy of the sample PARMLIB memberSMFPRMYL. Edit the SMFPRMxx parmlib member, and enable SMF recording forWebSphere Application Server Liberty by selecting type 120 records only in theinserted SYS statement.


The WebSphere Application Server Liberty components collect records from thesystem management facility (SMF) logs. Two records are supported currently:


https://www.ibm.com/support/knowledgecenter/SS7K4U_liberty/com.ibm.websphere.javadoc.liberty.doc/com.ibm.websphere.appserver.api.zosRequestLogging_1.0-javadoc/com/ibm/websphere/zos/request/logging/package-summary.html

Table 28. Input records to WebSphere Application Server Liberty component.


120.11 SMF_120_11 This record consists ofinformation about HTTPrequests.

120.12 SMF_120_12 This record consists ofinformation about Java batchjobs.

Data flow

The log collector initiates SMF type 120 record processing based on WebSphereApplication Server Liberty record definitions. The log collector uses one of tworecord definitions to map data in the SMF log. It selects the appropriate definitionsbased on the type of data that is recorded by WebSphere Application ServerLiberty.

The following Figure shows an overview of the flow of data from the WebSphereApplication Server Liberty via the WebSphere Liberty component of Tivoli DecisionSupport for z/OS:


Figure 223. WebSphere Application Server Liberty component data flow


Data tables and viewsThis chapter describes data tables and views that are used by WebSphereApplication Server Liberty component. It also explains the relations of tables andviews with records, updates, and tablespaces. All the Tivoli® Decision Support forz/OS WebSphere Liberty objects are defined and initialized in the DRLIWASLmember.

WASLBT_REQ_H,_D,_M

The Request Activity tables provide statistics on requests for the server job. Fromrecord SMF_120_11.

The default retention periods for these tables are as follows:v WASLBT_REQ_H: 10 daysv WASLBT_REQ_D: 90 daysv WASLBT_REQ_M: 765 days


DATE K DATE Date when the record was moved intothe SMF buffer. From SMF120DTE.

TIME K TIME Time when the record was moved intothe smf buffer. From SM120TME.Note: This column only exists in tableWASLBT_REQ_H.

MVS_SYSTEM_ID K CHAR(4) The name of the system on which theproduct is running. From SM120BAM.

SYSPLEX_NAME K CHAR(8) The name of the sysplex on which theproduct is running. From SM120BAN.

SERVER_JOBID K CHAR(8) The JES job ID of the server. FromSM120BAO.

SERVER_JOBNAME K CHAR(8) The JES job name of the Sever. FromSM120BAP.

NUM_REQUEST INTEGER The number of requests in this period.

REQUEST_RESP_SEC FLOAT The total interval, in seconds, betweenthe time that the request started, and thetime the request ended. FromSM120BBW and SM120BBX.

CPU_TIME_SEC FLOAT The total interval, in seconds, betweenthe CPU time at the start of the request,and the CPU time at the end of therequest. From SM120BBZ andSM120BCA.

ENCL_DEL_ZIIP FLOAT The total enclave delete ZIIP timeaccumulated by the enclave, in seconds.From SM120BCF.

ENCL_DEL_ZIIP_SRV FLOAT The total enclave delete ZIIP serviceaccumulated by the enclave, in seconds.From SM120BCG.

ENCL_DEL_ZAAP FLOAT The total enclave delete ZAAP timeaccumulated by the enclave, in seconds.From SM120BCD.



ENCL_DEL_ZAAP_SRV FLOAT The total enclave delete ZAAP serviceaccumulated by the enclave, in seconds.From SM120BCE.

ENCL_DEL_CPU FLOAT The total enclave delete CPU timeaccumulated by the enclave, in seconds.From SM120BCB.

ENCL_DEL_CPU_SRV FLOAT The total enclave delete CPU serviceaccumulated by the enclave, in seconds.From SM120BCC.

CDCOUNT INTEGER A counter used to measure how manySM120BCD fields had a value greaterthan 0. Used in the view to calculate anaverage.

CFCOUNT INTEGER A counter used to measure how manySM120BCF fields had a value greaterthan 0. Used in the view to calculate anaverage.

CBCOUNT INTEGER A counter used to measure how manySM120BCB fields had a value greaterthan 0. Used in the view to calculate anaverage.

CGCOUNT INTEGER A counter used to measure how manySM120BCG fields had a value greaterthan 0. Used in the view to calculate anaverage.

CECOUNT INTEGER A counter used to measure how manySM120BCE fields had a value greaterthan 0. Used in the view to calculate anaverage.

CCCOUNT INTEGER A counter used to measure how manySM120BCC fields had a value greaterthan 0. Used in the view to calculate anaverage.

WASLBT_REQ_HV,_DV,MV

The Request Activity views provide average statistics on requests for the serverjob. From record SMF_120_11.



TIME K TIME Time when the record was moved intothe smf buffer. From SM120TME.Note: This column only exists in tableWASLBT_REQ_HV.

MVS_SYSTEM_ID K CHAR(4) The name of the system on which theproduct is running. From SM120BAM.

SYSPLEX_NAME K CHAR(8) The name of the sysplex on which theproduct is running. From SM120BAN.

SERVER_JOBID K CHAR(8) The JES job ID of the server. FromSM120BAO.



SERVER_JOBNAME K CHAR(8) The JES job name of the Sever. FromSM120BAP.

NUM_REQUEST INTEGER The number of requests in this period.

REQUEST_RESP_SEC FLOAT The total interval, in seconds, betweenthe time that the request started, and thetime the request ended. FromSM120BBW and SM120BBX.

CPU_TIME_SEC FLOAT The total interval, in seconds, betweenthe CPU time at the start of the request,and the CPU time at the end of therequest. From SM120BBZ andSM120BCA.

ENCL_DEL_ZIIP FLOAT The total enclave delete ZIIP timeaccumulated by the enclave, in seconds.From SM120BCF.

ENCL_DEL_ZIIP_SRV FLOAT The total enclave delete ZIIP serviceaccumulated by the enclave, in seconds.From SM120BCG.

ENCL_DEL_ZAAP FLOAT The total enclave delete ZAAP timeaccumulated by the enclave, in seconds.From SM120BCD.

ENCL_DEL_ZAAP_SRV FLOAT The total enclave delete ZAAP serviceaccumulated by the enclave, in seconds.From SM120BCE.

ENCL_DEL_CPU FLOAT The total enclave delete CPU timeaccumulated by the enclave, in seconds.From SM120BCB.

ENCL_DEL_CPU_SRV FLOAT The total enclave delete CPU serviceaccumulated by the enclave, in seconds.From SM120BCC.

WASLBT_JBAT_COMPSTAT_D,M

These tables provide daily and monthly statistics on job completion on Libertyserver. From record SMF_120_12.

The default retention periods for these tables are as follows:v WASL_JBAT_COMP_D: 90 daysv WASL_JBAT_COMP_M: 765 days



MVS_SYSTEM_NAME K CHAR(4) The name of the system on which theproduct is running. From SM120CBF.

SYSPLEX_NAME K CHAR(8) The name of the sysplex on which theproduct is running. From SM120CBG.

SERVER_JOBNAME K CHAR(8) The job name for the Sever. FromSM120CBK.



BATCH_STATUS K INTEGER The value of the batch status. FromSM120CCK.

NUM_JOB INTEGER The number of job. This counting ofeach batch status.

WASL_JBAT_JOB_T

This table provides detailed statistics for each execution of one job. From recordSMF_120_12.

The default retention period for this table is as follows:v WASL_JBAT_JOB_T: 7 days


DATE K DATE Date when the record was moved into the SMFbuffer. From SMF120DTE.

TIME K TIME Time when the record was moved into the smfbuffer. From SM120TME.

MVS_SYSTEM_NAME K CHAR(4) The name of the system on which the product isrunning. From SM120CBF.

SYSPLEX_NAME K CHAR(8) The name of the sysplex on which the product isrunning. From SM120CBG.

SERVER_JOBNAME K CHAR(8) The job name for the Sever. From SM120CBK.

JOB_STORE_ID K CHAR(16) The Job Store Reference ID which pointing toanother element that contains information pointingto the actual database and tables to use for therepository. From SM120CDX.

JOB_INST_ID K FLOAT The job instance identifier. From SM120CBQ.

JOB_EXEC_ID K FLOAT The job execution identifier. From SM120CBR.

JOB_EXEC_NUM FLOAT The job execution number, it always starts with zerofor any job instance, and increases each time the jobinstance is restarted. From SM120CBS.

JOB_NAME CHAR(32) The name for the submitted job. From SM120CBV.

APPL_NAME CHAR(32) The application name for the job. From SM120CBW.

XML_NAME CHAR(32) The XML file name if the XML came from within theapplication. From SM120CBX.

SUBMITTER CHAR(32) The user id that was used to submit the job. FromSM120CCE.

STEP_NUM INTEGER The number of steps for this job execution. Thoughcounting SM120CBY.

STEP_NAME CHAR(32) The name of the last step for this job execution.From SM120CBY.

TOTAL_CPU_SEC FLOAT The total interval, in seconds, between the CPU timeat the start of the job execution, and the CPU time atthe end of the job execution. From SM120CCY andSM120CCZ.


WASL_JBAT_WKLD_H,D,M

These tables provide hourly, daily, and monthly statistics on jobs workload. Fromrecord SMF_120_12.

The default retention period for this table is as follows:v WASL_JBAT_ WKLD _H: 45 daysv WASL_JBAT_ WKLD _D: 45 daysv WASL_JBAT_ WKLD _M: 765 days



TIME K TIME Time when the record was moved intothe smf buffer. From SM120TME.Note: This column only exists in tableWASL_JBAT_ WKLD _H.

MVS_SYSTEM_NAME K CHAR(4) The name of the system on which theproduct is running. From SM120CBF.

SYSPLEX_NAME K CHAR(8) The name of the sysplex on which theproduct is running. From SM120CBG.

SERVER_JOBNAME K CHAR(8) The job name for the Sever. FromSM120CBK.

NUM_JOB INTEGER The number of jobs in this period.

TOTAL_CPU_SEC FLOAT The total interval, in seconds, betweenthe CPU time at the start of the jobs, andthe CPU time at the end of the jobs.From SM120CCY and SM120CCZ.

TOTAL_CP_SEC FLOAT The total interval, in seconds, betweenthe CP time at the start of the jobs,Formatted: Font: (Default) Palatino-Boldand the CP time at the end of the jobs.From SM120CDA and SM120CDB.

TOTAL_OFLCPU_SEC FLOAT The total interval, in seconds, betweenthe OFFLOAD CPU time at the start ofthe jobs, and the OFFLOAD CPU time atthe end of the jobs. From SM120CDCand SM120CDD.

TOTAL_OFLCP_SEC FLOAT The total interval, in seconds, betweenthe OFFLOAD CP time at the start of thejobs, and the OFFLOAD CP time at theend of the jobs. From SM120CDE andSM120CDF.

z/OS Interval Job/Step Accounting componentCustomization

Data flow

Data tables, views, and lookup tablesv Data Tables


– MVSAC_JOBADDR1_T,_H,_D,_M– MVSAC_JOBADDR2_T,_H,_D,_M– MVSAC_JOBSTEP_T

v Lookup tables– MVSAC_STEP_SLA_LK– MVSAC_SYSID_LK

v Views– MVSAC_JOBADDR_TV– MVSAC_JOBADDR1_TV– MVSAC_JOBSTEP_TV

Reportsv Job Daily Resource Consumption reportv Job Step Duration and CPU Consumption reportv Job Running Resource Consumption, Daily report

CustomizationThe z/OS Interval Job/Step Accounting component manages SMF30 subtyperecords in a way that accounting information is consistently available.

The type 30 record can be used with subtype selectivity function. There are sixsubtype records available, which provide address space level accountinginformation.

The SMF 30 subtypes are:

Subtype 1Job start or start of other work unit

Subtype 2Activity since previous interval ended

Subtype 3Activity for the last interval before step termination

Subtype 4Step total

Subtype 5Job termination or termination of other work unit

Subtype 6System address space

A brief explanation of the SMF 30 record subtypes flow follows:v A work unit (such as a TSO/E session, APPC/MVS transaction program, started

task, or batch job) starts. This subtype 1 record identifies the work unit butcontains no resource data.

v An SMF interval ends, if you requested interval accounting. If this is the firstinterval since the work unit started, then this subtype 2 record contains the totalresources used from the start of the work unit until the end of the currentinterval. For other intervals, this subtype 2 record contains the total resourcesused from the end of the previous interval until the end of the current interval.


For system address spaces that do not go through full function start, SMFgenerates a subtype 6 record that contains the total resources used since the startof the address space. Note that the data in the subtype 6 record is cumulative,unlike the subtype 2 record.

v A work unit (such as a TSO/E session, APPC/MVS transaction program, startedtask, or batch job) completes. If you requested interval accounting, SMFgenerates a subtype 3 record that contains the total resources used from the endof the previous recording interval until the end of the work unit.

v For a job step, SMF generates a subtype 4 record that contains the total resourcesused from the time when the job step started until the time when the job stepcompleted. If you requested interval recording, then this subtype 4 recordgenerally contains the accumulated totals of the data in the interval subtype 2and subtype 3 records that were generated for the step.

v For a job, SMF generates a subtype 5 record that contains the total resourcesused from the time when the job started until the time when the job completed.This subtype 5 record generally contains the accumulated totals of the data inthe step total subtype 4 records that were generated for the job.

Data flowThe z/OS Interval Job/Step Accounting component consists of:v Log and Record definitionsv Tables with the corresponding update definitionsv A table view and lookup tablev Reports

The following figure shows an overview of the flow of data from the SMF log,through the z/OS Interval Job/Step Accounting component of Tivoli Decision


Support for z/OS, and finally into reports.

Note: Most of the fields present in the tables listed above are updated fromdifferent SMF 30 record subtypes; some table columns might not be filled in, if theneeded SMF 30 record subtype is not present in the collected log or if it does notcontain the needed data section.

Data tables, views, and lookup tablesThis chapter describes the data tables, views, and lookup tables used by the z/OSInterval Job/Step Accounting component.

Note:

Figure 224. z/OS Interval Job/Step Accounting Data Flow


Because the MVSAC_JOBADDR1_T, MVSAC_JOBADDR2_T, andMVSAC_JOBSTEP_T data tables provides timely data, they may easily becomepopulated with a great amount of information. Hence, to prevent space andperformance problems, the default retention period has been reduced to 3 days. Ifyou need to maintain the data for a longer period of time, modify the Purgecondition for each table.

Data TablesThis section describes the data tables for the z/OS Interval Job/Step Accountingcomponent.

MVSAC_JOBADDR1_T,_H,_D,_M:MVSAC_JOBADDR1_T,_H,_D,_M

This table provides timely, hourly, daily, and monthly accounting statistics onaddress spaces and jobs. They contain data from SMF type 30.


MVSAC_JOBADDR1_T3 days

MVSAC_JOBADDR1_H7 days

MVSAC_JOBADDR1_D15 days

MVSAC_JOBADDR1_M365 days


DATE K DATE Date when the activity occurred. It is the date whenthe reader recognized the JOB card for this job. FromSMF30RSD.

TIME K TIME Time when the activity occurred. It applies only to the_T and _H tables. It is the time when the readerrecognized the JOB card for this job. From SMF30RST.

TIMESTAMP K TIMESTAMP Date and time when the activity occurred. It appliesonly to the _T table. It is the date and time when thereader recognized the JOB card for this job. FromSMF30RSD and SMF30RST.

MVS_SYSTEM_ID K CHAR(4) MVS system ID. This is the SMF system ID. FromSMF30SID.

JOB_NAME K CHAR(8) Name of the job. From SMF30JBN.

JOB_SAMPLING_DATE K DATE Date when the job was still running. From SMF30IDTor SMF30DTE.

PERIOD_NAME K CHAR(8) Name of the period. This is derived by using fieldsSMF30SID, SMF30IDT, SMF30IST, SMF30DTE, andSMF30TME as parameters of the PERIOD function.

ACCOUNT_FIELD1 VARCHAR(60) First accounting field. First sect of SMF30ACT.

ACCOUNT_FIELD2 VARCHAR(60) Second accounting field. First sect of SMF30ACT.

ACCOUNT_FIELD3 VARCHAR(60) Third accounting field. First sect of SMF30ACT.

ACCOUNT_FIELD4 VARCHAR(60) Fourth accounting field. First sect of SMF30ACT.

ACCOUNT_FIELD5 VARCHAR(60) Fifth accounting field. First sect of SMF30ACT.



ACCOUNT_FIELD6 VARCHAR(60) Sixth accounting field. First sect of SMF30ACT.

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 pagedin 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 Total number of blocks transferred. This is theaccumulated EXCP counts. This is the sum ofSMF30TEP.

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, inbytes. This is the sum of SMF30DAT.

CARDS_READ FLOAT Number of card-image records in DD DATA and DD *data sets read by the reader. This is the sum ofSMF30INP.

CONNECT_INVALID CHAR(1) Indicates that the device connect time(CONNECT_MSEC) might be not valid. It is set to 1 ifthe device connect time might be not valid. This is themaximum of bit 0 in SMF30DCF.

CONNECT_MSEC FLOAT Total device connect time for the address space, inmilliseconds. This is the sum of SMF30TCN*0.128.

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, both currently activeand deallocated, associated with the transactionprogram ID. This is the sum of SMF30CN.

CPU_ENQ_PROMOT_INT FLOAT CPU time consumed for an A/S or Job while enqueuepromoted. 1.024 milliseconds unit Unlike SMF30CEP,for interval records, this field contains only the timeconsumed during the interval itself. Valid where bit 7of SMF30TF2 is 0.

CPU_HIPER_SECONDS FLOAT Processor time used to support data transfer to andfrom a hiperspace backed by expanded storage, inseconds. Calculated as the sum of SMF30HPT/100 forrecords where bit 0 or bit 10 of SMF30TFL is 0.

CPU_INTR_SECONDS FLOAT Processor time used to process I/O interrupts, inseconds. Calculated as the sum of SMF30IIP/100 forrecords where bit 0 or bit 9 of SMF30TFL is 0.

CPU_PAGE_SECONDS FLOAT Number of processor page seconds for the addressspace, in page seconds units. Calculated as the sum ofSMF30PSC*0.001.

CPU_RCT_SECONDS FLOAT Processor time used by the region control task, inseconds. Calculated as the sum of SMF30RCT/100 forrecords where 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 timesNote: It includes the time consumed by IFA-eligiblework running on standard CP, but it does not includeCPU time of IFA or IIP processors.

CS_FRAME_SECONDS FLOAT Active frame time for frames in central storage, inseconds. Calculated as the sum ofSMF30RES*SMF30PSC*1024/ (SMF30CPT* 10 000000).

DASD_BLOCKS FLOAT Number of blocks transferred to and from diskdevices. This is the sum of SMF30BLK, whereSMF30DEV =X'20'.

DIVISION_ID CHAR(4) Division ID from SMF30_SYSID_LK lookup.

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 orbit 13 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 caller(within caller’s address space). Calculated as the sumof SMF30CSC.

IFA_CPU_SECONDS FLOAT CPU time spent on IFA (including enclave time), inseconds. Calculated as the sum of(SMF30_TIFA*SM30ZNF/256)/100, for records wherebit 1 of SMF30TF2 is 0.

IFA_CPU_ON_CP_SEC FLOAT CPU time spent running IFA eligible work on astandard CP (including enclave time), in seconds. Thisvalue is also included in TCB_STEP_SECONDS.Calculated as the sum of SMF30_TIFC/100 for recordswhere bit 4 of SMF30TF2 is 0.

IFA_DEP_ENC_CPSEC FLOAT Dependent enclave IFA time spent on CP in seconds.Calculated as the sum of SMF30_DETIFC/100 forrecords where bit 6 of SMF30TF2 is 0.

IFA_DEP_ENC_SEC FLOAT Dependent enclave time spent on IFA in seconds.Calculated as the sum of SMF30_DETIFA/100 forrecords where bit 3 of SMF30TF2 is 0.

IFA_ENCLAVE_SEC FLOAT Enclave time spent on IFA, in seconds. This value isalso included in IFA_CPU_SECONDS. Calculated asthe sum of (SMF30_ETIFA*SM30ZNF/256)/100, forrecords where bit 2 of SMF30TF2 is 0.

IFA_ENCL_ON_CP_SEC FLOAT IFA enclave time spent on a standard CP, in seconds.This value is also included in IFA_CPU_ON_CP_SEC.Calculated as the sum of SMF30_ETIFC/100 forrecords where bit 5 of SMF30TF2 is 0.

JOB_CLASS CHAR(1) Job class. From SMF30CLS. Blank if SMF30WID isSTC or ASCH or OMVS.

JOB_CPU_SECONDS FLOAT Job CPU consumption. It is calculated as sum ofSMF30ICU, SMF30ISB, SMF30CPT, SMF30TFL,SMF30IIP, SMF30RCT and SMF30HPT.



JOB_DASD_BLOCKS FLOAT Count of blocks issued for the DASD against the dataset. From SMF30BLK.

JOB_DURATION_SECS INTEGER Job duration, in seconds.

JOB_DURATION_TIME TIME Elapsed time, in the format HH:MM:SS. Calculatedfrom the job start-time and job end-time.

JOB_END_CHECK CHAR(1) Specifies whether SMF30 subtype 5 record (jobtermination) has been processed for this addressspace. It is Y if subtype 5 has been processed,otherwise is N.

JOB_END_DATE DATE Date when the record was moved to the SMF buffer.From field SMF30DTE.

JOB_END_TIME TIME Time when the record was moved to the SMF buffer.From field SMF30TME.

JOB_INIT_CHECK CHAR(1) Specifies whether SMF30 subtype 1 record (jobinitiation) has been processed for this address space.It can be set to one of the following:

Y Subtype 1 has been processed.

n The first subtype processed (either 2 or 3,meaning subtype 2 or subtype 3)

N All the other cases. This is the default.

JOB_IO_COUNT INTEGER Total blocks transferred. From SMF30TEP.

JOB_NUMBER CHAR(8) JES job identifier. From SMF30JNM.

JOB_RETURN_CODE INTEGER Job completion code. From SMF30SCC. This columncould contain a return code or an abend code (seecolumn JOB_RETURN_TYPE). Zero indicates normalcompletion, or that the last step was flushed.Note: SMF30SCC can hold values > 4095 for stepswhich completed successfully. However, the joboutput will only display return code values between 0and 4095, and therefore the remainder of the returncode (when divided by 4096) is displayed in the joblog. Therefore, for return codes > 4095, TDSz sets thiscolumn to the remainder, when divided by 4096.

JOB_RETURN_TYPE CHAR(1) Job return type. Based on SMF30STI. Possible valuesare:

N Normal completion.

A An abend occurred in the job.

JOB_START_DATE DATE Date when the initiator selected this step or job. Fromfirst job field SMF30STD.

JOB_START_TIME TIME Time when the initiator selected this step or job. Fromfirst job field SMF30SIT.

JOB_TAPE_BLOCKS FLOAT Count of blocks issued for the tape against the dataset. From SMF30BLK.

JOB_TAPE_MOUNTS FLOAT Number of specific and non-specific tape mounts.From SMF30PTM and SMF30TPR.

PA_GT16MB_BYTES FLOAT Maximum private area size above 16 megabytes, inbytes. This is the maximum of SMF30ERG.

PA_LT16MB_BYTES FLOAT Maximum private area size below 16 megabytes, inbytes. This is the maximum of SMF30RGB.



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). Thisis the sum of SMF30CPI.

PAGEINS_HIPER FLOAT Number of hiperspace page-ins from auxiliary toprocessor storage. This is the sum of SMF30HPI.

PAGEINS_LPA FLOAT Number of LPA page-ins. This is the sum ofSMF30LPI.

PAGEINS_SHARED FLOAT Number of IARVSERV shared pages that were pagedin from auxiliary storage in this address space. This isthe sum of SMF30PAI.

PAGEINS_SHARED_ES FLOAT Number of IARVSERV shared pages that were pagedin from expanded storage in this address space. Thisis the sum of SMF30PEI.

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

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 auxiliary toprocessor 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_STOLEN FLOAT Number of pages stolen from the address space. Thisis the 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.

PERF_GROUP_NO CHAR(3) Job performance group number. This field onlyapplies when the system is running in workloadmanagement compatibility mode. It is 0 if the systemis running in work management goal mode. FromSMF30PGN.

RACF_USER_ID CHAR(8) RACF user ID. Blank means that RACF is not active.

RECEIVE_CALLS FLOAT Number of times the transaction program issued areceive call. This is the sum of SMF30REC.



REGION_SIZE_MAX_KB FLOAT Maximum region size established, in kilobytes. This isthe maximum of SMF30RGN.

REPORT_CLASS CHAR(8) Report class name. This field is blank when inworkload management compatibility mode. FromSMF30RCN.

SEND_CLASS FLOAT Number of times the transaction program issued asend call. This is the sum of SMF30SEN.

SERVICE_CLASS CHAR(8) Service class name. This field is blank when inworkload management compatibility mode. FromSMF30SCN.

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

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 IARVSERVshared central storage frames in use by this addressspace, in page second units. This is the sum ofSMF30PSF*0.001.

SRB_INIT_SECONDS FLOAT Initiator processor time under SRB, in seconds.Calculated as the sum of SMF30ISB/100 for recordswhere bit 0 or bit 5 of SMF30TFL is 0.

SRB_PREEMP_SECONDS FLOAT Additional CPU time accumulated by the preemptableSRBs and client SRBs for this job, in seconds.Calculated as the sum of SMF30ASR/100 for recordswhere bit 0 or bit 12 of SMF30TFL is 0.

SRB_STEPS_SECONDS FLOAT Step processor time under SRB, in seconds. Calculatedas the sum of SMF30CPS/100 for records where bit 0or bit 2 of SMF30TFL is 0.

STOR_PRIV_BOT_KB INTEGER Largest amount of storage used from the bottom ofthe private 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 Name of the subsystem. From SMF30WID.

SWAP_SEQUENCES FLOAT Number of address space swap sequences. This is thesum of SMF30NSW.

TAPE_BLOCKS FLOAT Number of blocks transferred to and from tapedevices. This is the sum of SMF30BLK, whereSMF30DEV=X'80'.

TCB_INIT_SECONDS FLOAT Initiator processor time under TCB, in seconds.Calculated as the sum of SMF30ICU/100 for recordswhere bit 0 or bit 6 of SMF30TFL is 0.



TCB_STEP_SECONDS FLOAT Step processor time under TCB, in seconds.Calculated as the sum of SMF30CPT/100 for recordswhere bit 0 or bit 1 of SMF30TFL is 0.Note: It includes the time consumed by IFA-eligiblework running on standard CP, but it does not includeCPU time of IFA or IIP processors.

TGET_COUNT FLOAT Number of TGETs for a TSO session. This is the sumof SMF30TGT.

TPUT_COUNT FLOAT Number of TPUTs for a TSO session. This is the sumof SMF30TPT.

TRAN_ACTIVE_SEC FLOAT SRM transaction active time, in seconds. Calculated asthe sum of SMF30TAT*0.001 024.

TRAN_PROGRAMS FLOAT Number of APPC/MVS transaction programsscheduled by the APPC/MVS transaction scheduler(ASCH). This is the sum of SMF30ATR.

TRAN_RESIDENT_SEC FLOAT SRM transaction residency time, in seconds.Calculated as the sum of SMF30RES*0.001 024.

TRANSACTIONS FLOAT Number of SRM transactions. This is the sum ofSMF30TRS.

TRANSACTIONS_ENCL FLOAT Enclave transaction count. This is the sum ofSMF30ETC.

VA_INIT_SECONDS FLOAT Initiator vector affinity time, in seconds. Calculated asthe sum of SMF30IVA/100 for records where bit 0 orbit 8 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 4of SMF30TFL is 0.

VIO_RECLAIMS FLOAT Number of VIO reclaims. This is the sum ofSMF30VPR.

VS_LSQA_SWA_GT16MB FLOAT Maximum virtual storage above 16 megabytesallocated from the LSQA and SWA subpools, in bytes.This is the maximum of SMF30EAR.

VS_LSQA_SWA_LT16MB FLOAT Maximum virtual storage below 16 megabytesallocated from the LSQA and SWA subpools, in bytes.This is the maximum of SMF30ARB.

VS_USER_GT16MB FLOAT Maximum virtual storage above 16 megabytesallocated by the user subpools, in bytes. This is themaximum of SMF30EUR.

VS_USER_LT16MB FLOAT Maximum virtual storage below 16 megabytesallocated by the user subpools, in bytes. This is themaximum of SMF30URB.

VU_INIT_SECONDS FLOAT Initiator vector usage time, in seconds. Calculated asthe sum of SMF30IVU/100 for records where bit 0 orbit 7 of SMF30TFL is 0.

VU_STEP_SECONDS FLOAT Initiator vector usage time, in seconds. Calculated asthe sum of SMF30JVU/100 for records where bit 0 orbit 3 of SMF30TFL is 0.

WORKLOAD_GROUP CHAR(8) Workload name. From SMF30WLM.



ZIIP_CPU_ON_CP_SEC FLOAT zIIP CPU time spent on CP in seconds includingenclave time. Calculated as the sum ofSMF30_ZIIP_CP/100 records where bit 4 of SMF30T32is 0.

ZIIP_CPU_SECONDS FLOAT Time spent on zIIP in seconds including enclave time.Calculated as the sum of SMF30_ZIIP/100 for recordswhere bit 1 of SMF30T32 is 0.

ZIIP_DEP_ENC_CPSEC FLOAT zIIP dependent enclave time spent on CP in seconds.Calculated as the sum of SMF30_DEP_ZIIP_CP/100records where bit 6 of SMF30T32 is 0.

ZIIP_DEP_ENC_NORM FLOAT Normalized dependent enclave time spent on zIIP inseconds. Calculated as the sum ofSMF30_DEP_ZIIP_Q/100 records where bit 2 ofSMF30T33 is 0.

ZIIP_DEP_ENC_SEC FLOAT Dependent enclave time spent on zIIP in seconds.Calculated as the sum of SMF30_DEP_ZIIP/100records where bit 3 of SMF30T32 is 0.

ZIIP_ENC_NORM FLOAT Normalized enclave time spent on zIIP in seconds.Calculated as the sum of SMF30_ENC_ZIIP_Q/100records where bit 1 of SMF30T33 is 0.

ZIIP_ENC_ON_CP_SEC FLOAT zIIP enclave time spent on CP in seconds. Calculatedas the sum of SMF30_ENC_ZIIP_CP/100 recordswhere bit 5 of SMF30T32 is 0.

ZIIP_ENCLAVE_SEC FLOAT Enclave time spent on zIIP in seconds. Calculated asthe sum of SMF30_ENC_ZIIP/100 for records wherebit 2 of SMF30T32 is 0.

MVSAC_JOBADDR2_T,_H,_D,_M:This table provides timely, hourly, daily, and monthly accounting information atjob level. They contain data from SMF types 6, 14, 15, and 64.


MVSAC_JOBADDR2_T3 days

MVSAC_JOBADDR2_H7 days

MVSAC_JOBADDR2_D15 days

MVSAC_JOBADDR2_M365 days


DATE K DATE Date when the activity occurred. It is the date whenthe reader recognized the JOB card for this job.

TIME K TIME Time when the activity occurred. It applies only to the_T and _H tables. It is the time when the readerrecognized the JOB card for this job.

TIMESTAMP K TIMESTAMP Date and time when the activity occurred. It appliesonly to the _T table. It is the date and time when thereader recognized the JOB card for this job.



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

JOB_NAME K CHAR(8) Name of the job.

JOB_DASD_TRKS_IN INTEGER Number of input tracks allocated on the DASD. FromSMF14NTA.

JOB_DASD_TRKS_OUT INTEGER Number of output tracks allocated on the DASD.From SMF15NTA.

JOB_DASD_TRKS_REL INTEGER Number of tracks released by the DASDM routine.From SMF15NTR.

JOB_LINES_PRINTED INTEGER Number of logical records written by the writer, byform number and class (this field includes JOBLOGinformation and data set copies). From SMF6LNR.

JOB_PAGES_PRINTED INTEGER Approximate page count (printer only). FromSMF6PGE.

JOB_TEMP_TRKS_IN INTEGER Number of temporary input tracks allocated on theDASD. From SMF14NTA.

JOB_TEMP_TRKS_OUT INTEGER Number of temporary output tracks allocated on theDASD. From SMF14NTA.

JOB_TEMP_TRKS_REL INTEGER Number of temporary tracks released by the DASDMroutine. From SMF15NTR.

JOB_VIO_TRKS_IN INTEGER Number of input tracks allocated for VIO data setaccess. From SMF15NTA.

JOB_VIO_TRKS_OUT INTEGER Number of output tracks allocated for VIO data setaccess. From SMF15NTA.

JOB_VSAM_TRKS_IN INTEGER VSAM input tracks allocated tracks. Calculated asdifference of SMF64TCC and SMF64FCC.

JOB_VSAM_TRKS_OUT INTEGER VSAM output tracks allocated tracks. Calculated asdifference of SMF64TCC and SMF64FCC.

MVSAC_JOBSTEP_T:This table provides timely detailed jobstep level statistics from SMF30 data.



RDR_TIMESTAMP K TIMESTAMP Timestamp when the activity occurred. It is the dateand time that the reader recognized the JOB card (forthis job). From SMF30RSD and SMF30RST.

JOB_NAME K CHAR(8) Name of job. From SMF30JBN.


STEP_NUMBER K SMALLINT Step Number. From SMF30STN.

END_MARGIN TIME Time delta SLA end criteria met or missed.

END_MARGIN_SIGN CHAR(1) End margin sign + or -, before or after.

JOB_NUMBER CHAR(8) Job Number. From SMF30JNM.

PERIOD_NAME CHAR(8) Name of the period. This is derived using fieldsSMF30SID, SMF30IDT, SMF30IST, SMF30DTE, andSMF30TME as parameters in the PERIOD function.



PROC_STEP_NAME CHAR(8) The name of the step that invoked the procedure.From SMF30PSN.

PROGRAM_NAME CHAR(8) Program name. From SMF30PGM.

RACF_USER_ID CHAR(8) RACF user id. From SMF30RUD.

SLA_DESCRIPTION CHAR(16) Service Level Agreement Description.FromMVSAC_STEP_SLA_LK lookup table.

SLA_DURATION_TIME TIME SLA Expected Duration Time.

SLA_END_TIME TIME SLA Expected End Time.

SLA_GROUP_NAME CHAR(16) Service Level Agreement Group Name. FromMVSAC_STEP_SLA_LK lookup table.

SLA_LEVEL_NUMBER SMALLINT Service Level Agreement Level Number. FromMVSAC_STEP_SLA_LK lookup table.

SLA_MET CHAR(1) SLA Flag: Y to indicate the SLA has been meet. N ifnot, blank otherwise.

SLA_START_TIME TIME SLA Expected Start Time.

SLA_THRESHOLD CHAR(2) SLA compliance value blank=OK, CO-concerned,CR-critical.

SLA_TYPE CHAR(1) SLA base type: T=clock-time D=duration.

START_MARGIN TIME Time delta SLA start criteria met or missed.

START_MARGIN_SIGN CHAR(1) Start margin sign + or -, before or after

STEP_CPU_SECONDS FLOAT Step CPU consumption in seconds.

STEP_DASD_BLOCKS INTEGER Number of blocks transferred to and from diskdevices for the current step. From SMF30BLK.

STEP_DURATION_SEC INTEGER Step duration in seconds.

STEP_DURATION_TIME TIME Step duration time. SMF30SIT-SMF30TME.

STEP_END_DATE DATE Date the record was moved to the SMF buffer. FromSMF30DTE.

STEP_END_TIME TIME Time the record was moved to the SMF buffer. FromSMF30TME.

STEP_IO_COUNT INTEGER Step Total blocks transferred. From SMF30TEP orSMF30TEX if SMF30TEP is flagged invalid(SMF30DCF bit 2 is on).

STEP_NAME CHAR(8) Step name. From SMF30STM.

STEP_RETURN_CODE SMALLINT Step completion code. From SMF30SCC. This columncould contain a return code or an abend code (seecolumn STEP_RETURN_TYPE). Zero indicates normalcompletion, or that the step was flushed.Note: SMF30SCC can hold values > 4095 for stepswhich completed successfully. However, the joboutput will only display return code values between 0and 4095, and therefore the remainder of the returncode (when divided by 4096) is displayed in the joblog. Therefore, for return codes > 4095, TDSz sets thiscolumn to the remainder, when divided by 4096.



STEP_RETURN_TYPE CHAR(1) Step return type. Based on SMF30STI. Possible valuesare:

N Normal completion.

U User abend.

S System abend.

F Step was flushed.

STEP_START_DATE DATE Initiator start date. From SMF30STD.

STEP_START_TIME TIME Initiator start time. From SMF30SIT.

STEP_TAPE_BLOCKS INTEGER Number of blocks transferred to and from tapedevices for the current step. From SMF30BLK.

SUBSYSTEM_ID CHAR Name of the subsystem. From SMF30WID.

Lookup tablesThis section describes the lookup tables specific to the z/OS Interval Job/StepAccounting component.

MVSAC_STEP_SLA_LK:This lookup table contains the Service Level Agreement (SLA) time(s) for clientSLA reporting.




PROC_STEP_NAME K CHAR(8) The name of the step that invoked the procedure.From SMF30PSN.

STEP_NAME K CHAR(8) Step name. From SMF30STM.

SLA_GROUP_NAME CHAR(16) Service Level Agreement Group Name.

SLA_DESCRIPTION CHAR(16) Service Level Agreement Description.

SLA_LEVEL_NUMBER INTEGER Service Level Agreement Level Number.

SLA_TYPE CHAR(1) SLA base type: T=clock-time D=duration.

SLA_START_TIME TIME SLA Expected Start Time.

SLA_END_TIME TIME SLA Expected End Time.

SLA_CONCERNED_TIME TIME Time delta to consider Concerned the SLA.

SLA_CRITICAL_TIME TIME Time delta to consider Critical the SLA.

SLA_DURATION_TIME TIME SLA Expected Duration Time.

SLA_DOCUMENT VARCHAR(100)

SLA Documentation

MVSAC_SYSID_LK:This table converts the system ID of the data into valid accounting information.


SYSID K CHAR(4) System ID associated with the resource.

DIVISION_ID CHAR(4) Division ID to associate with the resource used.


ViewsThis section describes the views for the z/OS Interval Job/Step Accountingcomponent.

MVSAC_JOBADDR_TV:This view provides detailed accounting statistics on address spaces and jobs. Itcontains data from SMF type 30, subtypes 2 and 3 records and accounting info atjob level from SMF types 6, 14, 15, qnd 30, subtypes 1 and 5. It is based on theMVSAC_JOBADDR1_TV view and MVSAC_JOBADDR2_T table.



TIME K TIME Time when the activity occurred. It is the time whenthe reader recognized the JOB card for this job.

TIMESTAMP K TIMESTAMP Date and time when the activity occurred. It is thedate and time when the reader recognized the JOBcard for this job.



Note: As well as the key columns described here, this view also contains the datacolumns described in MVSAC_JOBADDR1_TV (see MVSAC_JOBADDR1_TV) andMVSAC_JOBADDR2_T (see MVSAC_JOBADDR2_T,_H,_D,_M).

MVSAC_JOBADDR1_TV:This view provides detailed accounting statistics on address spaces and jobs. Itpropagates accounting info of SMF type 30, subtype 1, to the other SMF type 30subtypes. This view contains step data from SMF type 30 for all subtypes andaccounting info at job level, from SMF subtypes 1 and 5. It is based on theMVSAC_JOBADDR1_T table.



TIME K TIME Time when the activity occurred. It is the time whenthe reader recognized the JOB card for this job.

TIMESTAMP K TIMESTAMP Date and time when the activity occurred. It is thedate and time when the reader recognized the JOBcard for this job.



Note: As well as the key columns described here, this view also contains the datacolumns described in MVSAC_JOBADDR1_T (seeMVSAC_JOBADDR1_T,_H,_D,_M).

MVSAC_JOBSTEP_TV:


This view provides timely job step accounting statistics. It contains step data fromSMF type 30, subtypes 2 and 3. It is based on the MVSAC_JOBSTEP_T andMVSAC_STEP_SLA_LK tables, and on the MVSAC_JOBADDR1_TV view.


RDR_TIMESTAMP K TIMESTAMP Timestamp when the activity occurred. It is the dateand time that the reader recognized the JOB card (forthis job). From SMF30RSD and SMF30RST.



STEP_IO_COUNT INTEGER Step Total blocks transferred. From SMF30TEP orSMF30TEX if SMF30TEP is flagged invalid(SMF30DCF bit 2 is on).

Note: In addition to the key columns described here, this view also contains thedata columns described in MVSAC_JOBSTEP_T (see MVSAC_JOBSTEP_T),MVSAC_JOBADDR1_T (see MVSAC_JOBADDR1_T,_H,_D,_M), andMVSAC_STEP_SLA_LK (see MVSAC_STEP_SLA_LK).

ReportsThe z/OS Interval Job/Step Accounting component provides the following reports.

Job Daily Resource Consumption reportThis report shows the daily CPU resource consumed by each job and RACF ID.


Report IDMVSACAS1

Report groupz/OS Interval Job/Step Accounting reports

SourceMVSAC_JOBADDR1_D

AttributesMVS, Batch, TSO, Address_Space

VariablesFrom_Date, To_Date, MVS_System_ID, Subsystem_ID, Job_Name


The columns in this report contain this information:

DATE Date when the activity occurred. It is the date that the reader recognizedthe JOB card for this job.

MVS SYSTEM IDMVS system ID. This is the SMF system ID.

SUBSYSTEM IDName of the MVS subsystem.

JOB NAMEName of the job.

SERVICE UNITS CPUCPU service units.

SERVICE UNITS SRBSRB service units.

SERVICE UNITS IOI/O service units.

SERVICE UNITS MSOMSO service units.

RACF USER IDRACF user ID (if RACF is active).

Job Step Duration and CPU Consumption reportThis report shows the timely Job Step Duration and CPU Consumption.


Report IDMVSACT1


Job Daily Resource ConsumptionFROM: ’2003-01-27’ TO: ’2003-02-12’

MVS SERVICE SERVICE SERVICE SERVICESYSTEM SUBSYSTEM JOB UNITS UNITS UNITS UNITS

DATE ID ID NAME CPU SRB IO MSO---------- ------ --------- -------- ---------- ---------- ---------- ---------2003-01-27 ESJ4 STC IOSAS 1.156E+05 4.611E+04 0.000E+00 1.805E+052003-01-27 ESJ4 STC IRL7PROC 0.000E+00 1.057E+07 0.000E+00 1.180E+042003-01-27 ESJ4 STC IXGLOGR 2.723E+05 2.368E+05 0.000E+00 4.781E+062003-01-27 ESJ4 STC JESXCF 2.202E+06 1.020E+06 0.000E+00 7.067E+062003-01-27 ESJ4 STC JES2 1.105E+08 1.285E+07 6.859E+06 1.694E+092003-01-27 ESJ4 STC MSTJCL00 1.277E+07 3.305E+08 2.871E+05 7.313E+072003-01-27 ESJ4 STC MVSNFSC 9.710E+04 1.580E+04 0.000E+00 2.963E+062003-01-27 ESJ4 STC NETJ4 9.063E+06 4.788E+06 1.150E+03 1.374E+082003-01-27 ESJ4 STC OMVS 2.603E+06 1.005E+06 0.000E+00 7.088E+072003-01-27 ESJ4 STC RACF 8.196E+05 3.373E+05 0.000E+00 2.264E+062003-01-27 ESJ4 STC RMF 1.192E+08 9.054E+06 2.698E+05 3.303E+082003-01-27 ESJ4 STC RRS 5.393E+06 3.792E+05 0.000E+00 6.041E+072003-01-27 ESJ4 STC SMF 2.621E+05 1.636E+06 4.500E+03 3.719E+072003-01-27 ESJ4 STC SMS 1.929E+07 5.688E+05 3.508E+06 3.690E+07

Tivoli Decision Support for z/OS Report: MVSACAS1

Figure 225. Example of a Job Daily Resource Consumption report (partial view)


SourceMVSAC_JOBADDR1_T, MVSAC_JOBSTEP_T


VariablesFrom_Date, To_Date, From_Time, To_Time, MVS_System_ID,Subsystem_ID, Job_Name


DATE Date when the activity occurred. It is the date that the reader recognizedthe JOB card for this job.

TIME Time when the activity occurred. It is the time that the reader recognizedthe JOB card for this job.




JOB DURATION SECSJob duration in seconds.

JOB CPU SECONDSJob total CPU consumption.

STEP NUMBERStep number.

STEP NAMEStep name.

SLA METFlag to indicate if the SLA has been meet.

PROC STEP NAMEThe name of the step that invoked the procedure.

STEP DURAT. SECStep duration in seconds.

STEP CPU SECStep CPU consumption in seconds.

MVS JOB JOB PROC STEP STEPSYSTEM SUBSYSTEM JOB DURATION CPU STEP STEP SLA STEP DURAT. CPU

DATE TIME ID ID NAME SECS SECONDS NUMBER NAME MET NAME SEC SEC--------- -------- ------ ---------- ------ -------- -------- ------ -------- ----- ---- ------ --------2003-02-11 16.46.11 ESJ4 JES2 TDSINSTL 668 1 SCAN 2 1.550E+00

2 RUNLOG 625 4.303E+013 RUNRDEF 33 5.750E+004 UPDSTAT 1 1.100E-015 COPYMSG 5 3.550E+00

Tivoli Decision Support for z/OS Report: MVSACST1

Figure 226. Example of a Job Step Duration and CPU Consumption report


Job Running Resource Consumption, Daily reportThis report shows the daily CPU resource consumed by each job already runningor not.


Report IDMVSACAS2


SourceMVSAC_JOBADDR1_D


VariablesFrom_Date, To_Date, MVS_System_ID, Subsystem_ID, Job_Name


JOB SAMPLING DATEDate when the job is still run.





Job Running Resource Consumption, Daily reportFROM: ’2003-09-27’ TO: ’2003-10-12’

JOB MVS SERVICE SERVICE SERVICE SERVICESAMPLING SYSTEM SUBSYSTEM JOB PERIOD UNITS UNITS UNITS UNITSDATE ID ID NAME NAME CPU SRB IO MSO---------- ------ --------- -------- ------ --------- ---------- ---------- ---------2003-01-27 ESJ4 STC IOSAS PRIME 1.156E+05 4.611E+04 0.000E+00 1.805E+052003-01-27 ESJ4 STC IRL7PROC PRIME 0.000E+00 1.057E+07 0.000E+00 1.180E+042003-01-27 ESJ4 STC IXGLOGR PRIME 2.723E+05 2.368E+05 0.000E+00 4.781E+062003-01-27 ESJ4 STC JESXCF PRIME 2.202E+06 1.020E+06 0.000E+00 7.067E+062003-01-27 ESJ4 STC JES2 PRIME 1.105E+08 1.285E+07 6.859E+06 1.694E+092003-01-27 ESJ4 STC MSTJCL00 PRIME 1.277E+07 3.305E+08 2.871E+05 7.313E+072003-01-27 ESJ4 STC MVSNFSC PRIME 9.710E+04 1.580E+04 0.000E+00 2.963E+062003-01-27 ESJ4 STC NETJ4 PRIME 9.063E+06 4.788E+06 1.150E+03 1.374E+082003-01-27 ESJ4 STC OMVS PRIME 2.603E+06 1.005E+06 0.000E+00 7.088E+072003-01-27 ESJ4 STC RACF PRIME 8.196E+05 3.373E+05 0.000E+00 2.264E+062003-01-27 ESJ4 STC RMF PRIME 1.192E+08 9.054E+06 2.698E+05 3.303E+082003-01-27 ESJ4 STC RRS PRIME 5.393E+06 3.792E+05 0.000E+00 6.041E+072003-01-27 ESJ4 STC SMF PRIME 2.621E+05 1.636E+06 4.500E+03 3.719E+072003-01-27 ESJ4 STC SMS PRIME 1.929E+07 5.688E+05 3.508E+06 3.690E+07

Tivoli Decision Support for z/OS Report: MVSACAS2

Figure 227. Example of a Job Running Resource Consumption, Daily report (partial view)


SERVICE UNITS CPUCPU service units.

SERVICE UNITS SRBSRB service units.

SERVICE UNITS IOI/O service units.

SERVICE UNITS MSOMSO service units.

SERVICE USER IDRACF user ID (if RACF is active).

Tivoli Performance Modeler for z/OS componentCustomizationv Making input data available

Data flow

Data tablesv TPM_LPAR_Tv TPM_WORKLOAD_T

TPM Extract function

CustomizationThe Tivoli Performance Modeler for z/OS component is a substitute for theExtraction process in Tivoli Performance Modeler(TPM). The extract function inTPM is used to extract key performance metrics from RMF reports, the CPUActivity Report and the Workload Activity Report. TDS collects the same metricsbut from the SMF records. The two record types used are SMF 070 and SMF 072.

Making input data availableEnsure that the appropriate SMF record types are not suppressed by SMF or any ofits exits. For example, RMF monitor I must be active to produce SMF type 70, 71,and 72 records.

Data flowThe Tivoli Performance Modeler for z/OS component collects records from theSMF data set and stores extracted and summarized data in the Tivoli DecisionSupport for z/OS database.


*-------------------------------------------------------------*| *-----------* || | z/OS | || *-----*-----* || | || V || *-----*-----* || | SMF | || *-----*-----* || V || *-----------------------+-------------------------------* || | Tivoli Decision Support for z/OS | || | V | || | *---------------------+-----------------------------* | || | | | Collect | | || | | V | | || | | *-------*-------* | | || | | | Record | | | || | | | Definition | | | || | | *---------------* | | || | | | SMF_070 | | | || | | | SMF_072 | | | || | | *-------*-------* | | || | | V | | || | | *-------*-------* | | || | | | Data | | | || | | | Tables | | | || | | *---------------* | | || | | | TPM_LPAR_T | | | || | | | TPM_WORKLOAD_T| | | || | | *---------------* | | || | | | | || | | | | || | *---------------------------------------------------* | || | | || *-------------------------------------------------------* || |*-------------------------------------------------------------*

Data tablesThis chapter describes the data tables used by the Tivoli Performance Modeler forz/OS component.

TPM_LPAR_TThis table provides timestamp based statistics on processor activity. The statisticsare based on data from SMF type 70 records.


Column name Key Data type Comment

DATE K DATE Date record written. From SMF70DTE.

TIME K TIME Time record written. From SMF70IST.

MVS_SYSTEM_ID K CHAR(4) MVS system ID. From SMF70SID.

LPAR_NAME K CHAR(8) Name of the logical partition. From SMF70LPM.

PROCESSOR_TYPE K CHAR(4) Name of the logical processor type. Possible valuesare CP, ICF+(includes IFA, IFL, ICF), IFA, IFL, ICF, IIP.From SMF70CIX.

LPAR_WEIGHT INTEGER Logical partition processor resource weight factor.This column is set to zero if weight factor is X'FFFF'.From SMF70BPS.

CAPPING CHAR(1) Partition capping is enabled. From SMF70VPF.



PHY_PROCESSORS_CP SMALLINT Total number of CP physical processors assigned foruse by PR/SM. From TOTCPPRO.

PHY_PROCESSORS_ICF SMALLINT Total number of ICF pool physical processorsassigned for use by PR/SM. From TOTICFPRO.

PHY_PROC_SPP_IFA SMALLINT Total number of IFA physical processors assigned foruse by PR/SM. From TOT_SPP_IFA_PRO.

PHY_PROC_SPP_IFL SMALLINT Total number of IFL physical processors assigned foruse by PR/SM. From TOT_SPP_IFL_PRO.

PHY_PROC_SPP_ICF SMALLINT Total number of ICF physical processors assigned foruse by PR/SM. From TOT_SPP_ICF_PRO.

LOGICAL_PROC_TOT INTEGER Total number of logical processor assigned to thepartition for all occurrences of lproc shared. Eachprocessor type is considered separately.

PHY_PROC_SPP_IIP SMALLINT Total number of IIP physical processors assigned foruse by PR/SM. From TOT_SPP_IIP_PRO.

CPU_BUSY_SEC FLOAT Processor busy time for all CP processors, in seconds.This is calculated as the sum of (SMF70INT/1000) -(SMF70WAT*0.000001/4096), or (SMF70PDT*0.000001)- (SMF70WAT*0.000001/4096), or SMF70PDT*0.000001.

CPU_ONLINE_SEC FLOAT Sum of the measured time periods times the numberof online CP processors, in seconds. This is the sum ofSMF70INT.

CPU_MODEL_NO INTEGER CPU model number. From SMF70MOD.

CPU_MODEL_ID CHAR(16) CPC model identifier. From SMF70MDL.

CPU_MODEL_HW CHAR(16) CPC physical model identifier. From SMF70HWM.

TPM_WORKLOAD_TThis table provides timestamp based statistics on service and report classes definedin the active service policy. It includes the goals and the actual measured values forthis class. The statistics are based on data from SMF 72 records.



DATE K DATE Date record written. From SMF72DTE.

TIME K TIME Time record written. From SMF72IST.

MVS_SYSTEM_ID K CHAR(4) MVS system identification. From SMF72SID.

POLICY K CHAR(8) Service policy name. From R723MNSP.

WORKLOAD_GROUP K CHAR(8) Workload group name. From R723MWNM.

SERVICE_CLASS K CHAR(8) Service or report class name. From R723MCNM.

SERV_CLASS_PERIOD K INTEGER Service or report class period number. FromR723CPER.

SERV_CLASS_TYPE K CHAR(1) Service class (SC) type. This can be C for control, or Rfor reporting.

PRIORITY INTEGER A number that indicates the relative importance ofthis workload as seen by workload manager.

LOGICAL_CP_BUSY FLOAT Percent of the time the workload is executing.



POTENTIAL_ZAAP FLOAT This field represents the percent of the generalpurpose CPS that was used by this workload and wasalso capable of running on a ZAAP CP.

TRUE_ZAAP FLOAT This represents ZAAP eligible code which executedon a ZAAP CP.

POTENTIAL_ZIIP FLOAT This field represents the percent of the generalpurpose CPS that was used by this workload and wasalso capable of running on a ZIIP CP.

TRUE_ZIIP FLOAT This field represents the percent of the specialpurpose ZIIP CPS that was used by this workload.This represents ZIIP eligible code which executed on aZIIP CP.

WORKLOAD_MPL FLOAT The average number of transactions resident in centralstorage.

WORKLOAD_TRAN_RATE FLOAT Transaction rate (trans per second) for this workload.

VELOCITY FLOAT The execution velocity measures the portion of theacceptable processor and storage delays relative to thetotal execution time.

PERFORMANCE_INDEX FLOAT The performance index for a period represents howclose a period came to reaching the goal (PI is 1.0 ifgoal is reached), and how much this period sufferedversus its goal.

PI_FLAG CHAR(1) Indicates whether the performance index is applicablefor this goal type: Y - PI is applicable.N - PI is not applicable.F - PI is applicable. Sum of buckets 1 to 13 is less thangoal percentile.

GOAL FLOAT The goal specified in the WLM service policy for aservice class period.

SSCH_RATE FLOAT Number of start subchannels ssch per second in thereported interval.

IO_RESPONSE_TIME FLOAT Average dasd response time (in milliseconds) of thetransactions in this group.

WGL_ID CHAR(13) An identifier which begins with an A, followed by thepriority, the service class and finally the period.

TPM Extract functionThe TPM Extract function extracts data from the TPM_LPAR_T andTPM_WORKLOAD_T data tables and writes it to output files. The extracted datais used as input to the Tivoli Performance Modeler Model Build function. The datais written in a format that can be easily imported into spreadsheet programs.

To execute the TPM Extract, select the Utilities dialog option from theAdministration panel. The TPM Extract panel has the following fields that are usedto filter the data.

From/To DateThe dates the extract is to be done for.

From/To TimeThe time the extract is to start and end.


System IDMVS System ID

Number of CP ProcessorsThis is the number of general purpose CPUs available on this processor.

Number of zIIP/zAAP ProcessorsThe number of CPUs that can be allocated as zIIP or zAAP CPs.

Once all fields have been entered, and Enter is pressed, the extract function willretrieve the data for the criteria entered on the Extract panel. This data is retrievedfrom the TPM_LPAR_T and TPM WORKLOAD_T tables. The extract will allocateand write the data to the following files:

prefix.DRLLPAR.LPR

prefix.DRLZIIP.LPR

prefix.DRLZAAP.LPR

prefix.DRLLPAR.RPT

prefix.DRLZIIP.RPT

prefix.DRLZAAP.RPT

prefix.DRLWGL.RPT

These files can then be downloaded to your PC and used as input to the BuildModel function within Tivoli Performance Modeler.

Appendixes

Appendix. Support informationIf you have a problem with your IBM software, you want to resolve it quickly. Thissection describes the following options for obtaining support for IBM softwareproducts:v Searching knowledge basesv Obtaining fixesv Receiving weekly support updatesv Contacting IBM Software Support

Searching knowledge basesYou can search the available knowledge bases to determine whether your problemwas already encountered and is already documented.

Searching the information center:IBM provides extensive documentation that can be installed on your localcomputer or on an intranet server. You can use the search function of thisinformation center to query conceptual information, instructions for completingtasks, and reference information.

Searching the Internet:


If you cannot find an answer to your question in the information center, search theInternet for the latest, most complete information that might help you resolve yourproblem.

To search multiple Internet resources for your product, use the Web search topic inyour information center. In the navigation frame, click Troubleshooting andsupport > Searching knowledge bases and select Web search. From this topic, youcan search a variety of resources, including the following:v IBM technotesv IBM downloadsv IBM developerWorks®

v Forums and newsgroupsv Google

Obtaining fixesA product fix might be available to resolve your problem. To determine what fixesare available for your IBM software product, follow these steps:1. Go to the IBM Software Support Web site at http://www.ibm.com/software/

support/.2. Click Downloads and drivers in the Support topics section.3. Select the Software category.4. Select a product in the Sub-category list.5. In the Find downloads and drivers by product section, select one software

category from the Category list.6. Select one product from the Sub-category list.7. Type more search terms in the Search within results if you want to refine your

search.8. Click Search.9. From the list of downloads returned by your search, click the name of a fix to

read the description of the fix and to optionally download the fix.

For more information about the types of fixes that are available, see the IBMSoftware Support Handbook at http://techsupport.services.ibm.com/guides/handbook.html.

Receiving weekly support updatesTo receive weekly e-mail notifications about fixes and other software support news,follow these steps:1. Go to the IBM Software Support Web site at http://www.ibm.com/support/

us/.2. Click My support in the upper right corner of the page.3. If you have already registered for My support, sign in and skip to the next

step. If you have not registered, click register now. Complete the registrationform using your e-mail address as your IBM ID and click Submit.

4. Click Edit profile.5. In the Products list, select Software. A second list is displayed.6. In the second list, select a product segment, for example, Application servers.

A third list is displayed.7. In the third list, select a product sub-segment, for example, Distributed

Application & Web Servers. A list of applicable products is displayed.


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


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

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



8. Select the products for which you want to receive updates, for example, IBMHTTP Server and WebSphere® Application Server.

9. Click Add products.10. After selecting all products that are of interest to you, click Subscribe to email

on the Edit profile tab.11. Select Please send these documents by weekly email.12. Update your e-mail address as needed.13. In the Documents list, select Software.14. Select the types of documents that you want to receive information about.15. Click Update.

If you experience problems with the My support feature, you can obtain help inone of the following ways:

OnlineSend an e-mail message to [email protected], describing your problem.

By phoneCall 1-800-IBM-4You (1-800-426-4968).

Contacting IBM Software SupportIBM Software Support provides assistance with product defects.

Before contacting IBM Software Support, your company must have an active IBMsoftware maintenance contract, and you must be authorized to submit problems toIBM. The type of software maintenance contract that you need depends on thetype of product you have:v For IBM distributed software products (including, but not limited to, Tivoli,

Lotus®, and Rational® products, as well as DB2 and WebSphere® products thatrun on Windows, or UNIX operating systems), enroll in Passport Advantage® inone of the following ways:

OnlineGo to the Passport Advantage Web site at http://www.lotus.com/services/passport.nsf/ WebDocs/Passport_Advantage_Home and clickHow to Enroll.

By phoneFor the phone number to call in your country, go to the IBM SoftwareSupport Web site at http://techsupport.services.ibm.com/guides/contacts.html and click the name of your geographic region.

v For customers with Subscription and Support (S & S) contracts, go to theSoftware Service Request Web site at https://techsupport.services.ibm.com/ssr/login.

v For customers with IBMLink™, CATIA, Linux, S/390®, iSeries®, pSeries®,zSeries®, and other support agreements, go to the IBM Support Line Web site athttp://www.ibm.com/services/us/index.wss/so/its/a1000030/dt006.

v For IBM eServer™ software products (including, but not limited to, DB2® andWebSphere products that run in zSeries, pSeries, and iSeries environments), youcan purchase a software maintenance agreement by working directly with anIBM sales representative or an IBM Business Partner. For more informationabout support for eServer software products, go to the IBM Technical SupportAdvantage Web site at http://www.ibm.com/servers/eserver/techsupport.html.


http://www.ibm.com/software/sw-lotus/services/cwepassport.nsf/wdocs/passporthome/

http://www.ibm.com/software/sw-lotus/services/cwepassport.nsf/wdocs/passporthome/

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


https://techsupport.services.ibm.com/ssr/login

https://techsupport.services.ibm.com/ssr/login

http://www.ibm.com/services/us/index.wss/so/its/a1000030/dt006

http://www.ibm.com/servers/eserver/techsupport.html

If you are not sure what type of software maintenance contract you need, call1-800-IBMSERV (1-800-426-7378) in the United States. From other countries, go tothe contacts page of the IBM Software Support Handbook on the Web athttp://techsupport.services.ibm.com/guides/contacts.html and click the name ofyour geographic region for phone numbers of people who provide support foryour location.

To contact IBM Software support, follow these steps:1. Determining the business impact2. Describing problems and gathering information3. Submitting problems

Determining the business impact:When you report a problem to IBM, you are asked to supply a severity level.Therefore, you need to understand and assess the business impact of the problemthat you are reporting. Use the following criteria:

Severity 1The problem has a critical business impact. You are unable to use theprogram, resulting in a critical impact on operations. This conditionrequires an immediate solution.

Severity 2The problem has a significant business impact. The program is usable, butit is severely limited.

Severity 3The problem has some business impact. The program is usable, but lesssignificant features (not critical to operations) are unavailable.

Severity 4The problem has minimal business impact. The problem causes little impacton operations, or a reasonable circumvention to the problem wasimplemented.

Describing problems and gathering information:When describing a problem to IBM, be as specific as possible. Include all relevantbackground information so that IBM Software Support specialists can help yousolve the problem efficiently. To save time, know the answers to these questions:v What software versions were you running when the problem occurred?v Do you have logs, traces, and messages that are related to the problem

symptoms? IBM Software Support is likely to ask for this information.v Can you re-create the problem? If so, what steps were performed to re-create the

problem?v Did you make any changes to the system? For example, did you make changes

to the hardware, operating system, networking software, and so on.v Are you currently using a workaround for the problem? If so, be prepared to

explain the workaround when you report the problem.

Submitting problems:You can submit your problem to IBM Software Support in one of two ways:

OnlineClick Submit and track problems on the IBM Software Support site athttp://www.ibm.com/software/support/probsub.html. Type yourinformation into the appropriate problem submission form.



http://www.ibm.com/software/support/probsub.html

By phoneFor the phone number to call in your country, go to the contacts page ofthe IBM Software Support Handbook at http://techsupport.services.ibm.com/guides/contacts.html, and click the name of your geographic region.

If the problem you submit is for a software defect or for missing or inaccuratedocumentation, IBM Software Support creates an Authorized Program AnalysisReport (APAR). The APAR describes the problem in detail. Whenever possible,IBM Software Support provides a workaround that you can implement until theAPAR is resolved and a fix is delivered. IBM publishes resolved APARs on theSoftware Support Web site daily, so that other users who experience the sameproblem can benefit from the same resolution.

NoticesThis 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 Licensing

IBM Corporation

North Castle Drive

Armonk, NY 10504-1785 U.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 Corporation

Licensing

2-31 Roppongi 3-chome, Minato-ku

Tokyo 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 improvements andchanges in the product(s) and/or the program(s) described in this publication atany 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.

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 Corporation

2Z4A/101

11400 Burnet Road

Austin, TX 78758 U.S.A.

Such information may be available, subject to appropriate terms and conditions,including in some cases payment of a fee.

The licensed program described in this 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.

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

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

All statements regarding IBM’s future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only.


All IBM prices shown are IBM's suggested retail prices, are current and are subjectto change without notice. Dealer prices may vary.

This information is for planning purposes only. The information herein is subject tochange before the products described become available.

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.

If you are viewing this information in softcopy form, the photographs and colorillustrations might not display.

TrademarksListed below are trademarks or registered trademarks of International BusinessMachines Corporation in the United States, other countries, or both.

IBMIBM logoibm.comAIXAS/400CICSDB2developerWorksDominoeServerGDDMIBMLinkIMSiSeriesLotusLotus NotesMQSeriesMVS

NetViewOS/390Passport AdvantagePR/SMpSeriesRACFRAMACRationalRMFS/390TivoliVSE/ESAVTAMWebSpherez/OSz/VMzSeries

Adobe, the Adobe logo, PostScript, and the PostScript logo are either registeredtrademarks or trademarks of Adobe Systems Incorporated in the United States,and/or other countries.


Java and all Java-based trademarks and logosare trademarks or registered trademarks ofSun Microsystems, Inc. in the United States,other countries, or both.

Linux is a registered trademark of Linus Torvalds in the United States, othercountries, or both.

Microsoft, Windows and the Windows logo are trademarks of MicrosoftCorporation 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.

Bibliography

TDS publicationsv Administration Guide and Reference, SH19-6816v Resource Accounting for z/OS, SH19-4495v AS/400 System Performance Feature Guide and Reference, SH19-4019v CICS Performance Feature Guide and Reference, SH19-6820v Distributed Systems Performance Feature Guide and Reference, SH19-4018v Guide to Reporting, SH19-6842v IMS Performance Feature Guide and Reference, SH19-6825v Language Guide and Reference, SH19-6817v Messages and Problem Determination, SH19-6902v Network Performance Feature Installation and Administration, SH19-6901v Network Performance Feature Reference, SH19-6822v Network Performance Feature Reports, SH19-6821v System Performance Feature Guide, SH19-6818v System Performance Feature Reference Volume I, SH19-6819v System Performance Feature Reference Volume II, SH19-4494v Usage and Accounting Collector User Guide, SC23-7966

IXFP publicationsv IXFP Configuration and Administration Version 2 Release 1, SC26-7178-05v IXFP Subsystem Reporting Version 2 Release 1, SC26-7184-05v IXFP Installation for MVS Version 2 Release 1, SC26-7179-04


GlossaryA

administrationA Tivoli Decision Support for z/OS task that includes maintaining thedatabase, updating environment information, and ensuring the accuracy ofdata collected.

administration dialogA set of host windows used to administer Tivoli Decision Support forz/OS.

C

collect A process used by Tivoli Decision Support for z/OS to read data frominput log data sets, interpret records in the data set, and store the data inDB2 tables in the Tivoli Decision Support for z/OS database.

componentAn optionally installable part of the Tivoli Decision Support for z/OSfeature. Specifically in Tivoli Decision Support for z/OS, a componentrefers to a logical group of objects used to collect log data from a specificsource, to update the Tivoli Decision Support for z/OS database using thatdata, and to create reports from data in the database.

control tableA predefined Tivoli Decision Support for z/OS table that controls resultsreturned by some log collector functions.

D

data tableA Tivoli Decision Support for z/OS table that contains performance dataused to create reports.

DFSMS/MVSData Facility Storage Management Subsystem/MVS. An IBM licensedprogram that consists of DFSMSdfp, DFSMSdss, and DFSMShsm.

E

environment informationAll of the information that is added to the log data to create reports. Thisinformation can include data such as performance groups, shift periods,installation definitions, and so on.

H

host The MVS system where Tivoli Decision Support for z/OS runs collect andwhere the TTivoli Decision Support for z/OS database is installed.

K

key columnsThe columns of a DB2 table that together constitute the key.

L

log collectorA Tivoli Decision Support for z/OS program that processes log data setsand provides other Tivoli Decision Support for z/OS services.


log data setAny sequential data set that is used as input to Tivoli Decision Support forz/OS.

log definitionThe description of a log data set processed by the log collector.

log procedureA program module that is used to process all record types in certain logdata sets.

lookup tableA Tivoli Decision Support for z/OS DB2 table that contains grouping,conversion, or substitution information.

P

purge conditionInstruction for purging old data from the Tivoli Decision Support for z/OSdatabase.

R

record definitionThe description of a record type contained in the log data sets used byTivoli Decision Support for z/OS, including detailed record layout anddata formats.

record typeThe classification of records in a log data set.

report groupA collection of Tivoli Decision Support for z/OS reports that can bereferred to by a single name.

reporting dialogA set of host or workstation windows used to request reports.

resource groupA collection of network resources that are identified as belonging to aparticular department or division. Resources are organized into groups toreflect the structure of an organization.

S

sectionA structure within a record that contains one or more fields and maycontain other sections.

source In an update definition, the record or DB2 table that contains the data usedto update a Tivoli Decision Support for z/OS DB2 table.

sysplexA set of MVS systems communicating and cooperating with each otherthrough certain multisystem hardware components and software servicesto process customer workloads.

system tableA DB2 table that stores information that controls log collector processing,Tivoli Decision Support for z/OS dialogs, and reporting.


T

target In an update definition, the DB2 table in which Tivoli Decision Support forz/OS stores data from the source record or table.

thresholdThe maximum or minimum acceptable level of usage. Usage measurementsare compared with threshold levels.

Tivoli Decision Support for z/OS databaseA set of DB2 tables that includes data tables, lookup tables, system tables,and control tables.

U

update definitionInstructions for entering data into DB2 tables from records of differenttypes or from other DB2 tables.

V

view An alternative representation of data from one or more tables. A view caninclude all or some of the columns contained in the table on which it isdefined.

W

workstationFor LAN purposes, a workstation is either a client or a LAN server.


��

Program Number: 5698-B06

Printed in USA

SH19-4494-09

Spineinformation:

IBM

Tivo

liTi

voli

Deci

sion

Supp

ortf

orz/

OSVe

rsio

n1.

8.1

Syst

emPe

rform

ance

Feat

ure

Refe

renc

eVo

l.II

��

�

T l Tivoli Decision Support for z/OS - IBM...Figures 1. W ebSpher e MQ for z/OS (MQSeries) component...

Documents

Transcript of T l Tivoli Decision Support for z/OS - IBM...Figures 1. W ebSpher e MQ for z/OS (MQSeries) component...